Clean up languages/datasets for web and sanity

TODO

Make a common type for the languages (we need to figure out how hard it is to share types across the web and sanity folders. This might be to complicated for this issue)

Avoid to use let in the languages file (in the web). Or at least make it easier to see what is going on here

Use less hard coded string values for datasets (I had to change from production too many places, ie in DesktopStructure.js

We should add the base language explicit (for use in the document translation feature from the intl plugin). Both for the web part (next.config.js) and the documentTranslation (intl-plugin) config in Sanity

Since we do not yet share code between web and sanity, I suggest creating types for each now, and then we can see if we should consolidate the two at some point in the future. We will have to do changes two places, but I guess it is manageable. The important part is to get rid of magic strings.

With the new approach all the languages/dataset setup is done throught the file satellitesConfig.js located in the root folder.

The base language is still being defined accordingly to the order of the language array (check comment on line 8).
I believe this to be a clean and simple solution and don't see the need of making it more complex than that, but happy to refactor if the team disagrees.
I also moved the flags from the array to inside the studio, since they are only used there. So it is nice (but not needed), to add the country flag when adding a new language. Setup is done through the file studio/icons/countries/index.ts

GOTCHAS:
I couldn't use es6 modules for the languages.js files and satellitesConfig.js file. Could make it run locally but crashing when building next.
We can't use typescript since the file is read by next.config.mjs, and next currently doesn't accept ts in this file

Pros
Easier to read the code
Fewer occurrences of magic strings, at least the one we need to change when we use another dataset
More flexible base language
Satellite config is shared between the web and the studio
Cons
Lack of typescript because of Next config, but I don't think that will change.
Lack of ES6 modules, we should probably create an issue in the backlog and look more closely into this at some point?
We still need both en_GB and en-GB, do you remember the exact reason? The sanity intl plugin?
global is still hard coded several places as a way to differentiate between the main Equinor homepage and satellites. Would it make sense to export this as a constant or something?
We should probably not spend to much time on this :sweat_smile:
What do you think @nilsml ?

I tried to explain things slightly more verbose in the satellites config, but I'm actually not sure that it's 100% correct

...and the plot thickens
The new version of the Sanity language plugin has changed the config. Name is now id and they are using - as a delimiter for language and some config changes in general

I did a review of the code. It is definitely better than what it was, but still room for improvements. Either by creating a DSL for the config or use functional concepts, we could make it less error-prone, but at the same time we need to move on. I will create a task in the backlog for further improvements #745
I reckon this can be closed.


[full-ci] Bump Reva

Bumps reva

E2E tests failed: https://drone.owncloud.com/owncloud/ocis/22974/90/1
:boom: To see the trace, please open the link in the console ...

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/alice-can-share-this-weeks-meal-plan-with-all-parents-alice-2023-6-6-12-49-59.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/alice-can-share-this-weeks-meal-plan-with-all-parents-brian-2023-6-6-12-50-27.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/file-alice-2023-6-6-01-00-44.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/file-brian-2023-6-6-01-01-11.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/folder-alice-2023-6-6-12-58-55.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/folder-brian-2023-6-6-12-59-09.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/participant-management-alice-2023-6-6-01-04-43.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/participant-management-brian-2023-6-6-01-04-57.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/participant-management-carol-2023-6-6-01-05-20.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/participant-management-david-2023-6-6-01-05-06.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/participant-management-edith-2023-6-6-01-05-13.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/public-link-alice-2023-6-6-12-54-02.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/public-link-for-space-alice-2023-6-6-01-08-59.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/quick-link-alice-2023-6-6-12-55-20.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/re-sharing-alice-2023-6-6-12-56-34.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/search-in-personal-spaces-alice-2023-6-6-12-57-27.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/search-in-personal-spaces-brian-2023-6-6-12-57-18.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/share-a-link-with-internal-role-alice-2023-6-6-01-02-31.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/share-a-link-with-internal-role-alice-2023-6-6-12-53-17.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/tag-sharing-alice-2023-6-6-01-10-42.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/tag-sharing-brian-2023-6-6-01-10-54.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/unstructured-collection-of-testable-space-interactions-alice-2023-6-6-01-07-02.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/user-should-be-able-to-read-and-dismiss-notifications-alice-2023-6-6-12-56-08.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/22974/tracing/user-should-be-able-to-read-and-dismiss-notifications-brian-2023-6-6-12-56-16.zip


Discussion: chart.update architecture

Opening new issue to discuss architecture change
@whawker wrote:

Going completely off topic, I've been wondering if useModifiedProps is a mistake, currently when props change we figure out which ones have changed, and commit them as updates to the wrapped Highcharts chart.
I wonder instead if we should be utilising the oneToOne option of chart.update so that we can sure that the state in React representation of the chart, is the same as the internal Highcharts representation. However this might be undermining one of the fundamental principles of this project in the first place, to avoid destroying the chart completely between React re-renders)

This could be done without the oneToOne option too.
All the updates could be centralised to the BaseChart so that individual components such as Series declare their desired state to the BaseChart. BaseChart then does deep compare of previous chart state to current state, and performs changes to the chart.
For example:

Series component is mounted
Series component calls BaseChart via context: baseChart.updateSeries(props)
Legend is mounted
Legend calls BaseChart via context: baseChart.updateLegend(props)
BaseChart compares previous chartState with the changes caused by child components
BaseChart calls relevant chart.update, axis.update etc

Centralising changes also helps to keep track of axes when highstock decides to recycle the whole object (Navigator if I remember correctly).


MarketHours class is missing. While running locally it is giving error

Describe the bug
import pkscreener.classes.ConfigManager as ConfigManager
File "myenv/lib/python3.10/site-packages/pkscreener/classes/ConfigManager.py", line 36, in
from PKDevTools.classes.MarketHours import MarketHours
ModuleNotFoundError: No module named 'PKDevTools.classes.MarketHours'
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Please install PKDevTools @BalachandraRaju


Building with JDK 8 fails over a maven bug

When I build parquet on my system I get this error during the build:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on project parquet-generator: Error rendering velocity resource. NullPointerException -> [Help 1]

About a year ago @julienledem responded that this is caused due to a bug in Maven in combination with Java 8:
At this page http://stackoverflow.com/questions/31229445/build-failure-apache-parquet-mr-source-mvn-install-failure/33360512#33360512
Now this bug has been solved at the Maven end in maven-filtering 1.2
https://issues.apache.org/jira/browse/MSHARED-319
The problem is that this fix has not yet been integrated into the latest available maven versions yet.
I'll put up a pull request with a proposed fix for this.
Reporter: Niels Basjes / @nielsbasjes
Note: This issue was originally created as PARQUET-722. Please see the migration documentation for further details.

Julien Le Dem / @julienledem:
Thanks for spending the time!

Niels Basjes / @nielsbasjes:
I was looking at a really old version of the code.
This problem has already been fixed.

André Kelpe:
I just ran into this today with the latest release and latest maven. Is there really no other way than installing java 7?

Ryan Blue / @rdblue:
Looks like this was fixed when cascading3 support updated the maven-remote-resources-plugin: https://github.com/apache/parquet-mr/blob/master/pom.xml#L390-L397
I've confirmed that copying that block into older versions also fixes the problem.


docker network connect IP allocation problem

Description
When connecting a container to an existing network(overlay), belonging to a Swarm stack, Docker doesn't take into account the IP's that are already allocated as VirtualIPs for the services in that stack, and assigns an already used IP.
Steps to reproduce the issue:

Create the following docker-compose.yaml file.

version: '3'

services:
  srv:
    image: gophernet/netcat
    command: ["-l", "-p", "9000"]

and start it as a stack:
docker stack deploy -c docker-compose.yaml nettest

Start a separate service with one container

docker service create --name nettest_cnt gophernet/netcat -l -p 9000

Retrieve the task and container ID for service nettest_cnt, and connect it to the network belonging to the nettest stack.

$ docker service ps nettest_cnt
ID            NAME           IMAGE                    NODE  DESIRED STATE  CURRENT STATE          ERROR  PORTS
1ywc3iulu24v  nettest_cnt.1  gophernet/netcat:latest  moby  Running        Running 2 minutes ago
$ docker inspect 1ywc3iulu24v | grep ContainerID
                "ContainerID": "4f004dca4cc1bf6f9ec9965bab40414f355755f8615d382a6294c9d25a998e2f",
$ docker network connect nettest_default 4f004dca4cc1bf6f9ec9965bab40414f355755f8615d382a6294c9d25a998e2f

Describe the results you received:
Once the container is connected to the nettest_default, we can examine the IP allocation by inspecting the network
$ docker network inspect nettest_default
        "Containers": {
            "4f004dca4cc1bf6f9ec9965bab40414f355755f8615d382a6294c9d25a998e2f": {
                "Name": "nettest_cnt.1.1ywc3iulu24vdf3bbpcngvsf8",
                "EndpointID": "424ce0d785570fe4d30dada72ecba371a335768713e51c541a2cffe223579df6",
                "MacAddress": "02:42:0a:00:00:02",
                "IPv4Address": "<IP_ADDRESS>/24",
                "IPv6Address": ""
            },
            "68c13cf13186a841983862fd4839fe075481810f09bfe34d0c64e99edee3113a": {
                "Name": "nettest_srv.1.jxs6qcuxjcxyyq8n1dte6nzwg",
                "EndpointID": "bb0a351dbccf79fb47bf1f93fb788a1b91088f7370b343b42cf1b9e674a24956",
                "MacAddress": "02:42:0a:00:00:03",
                "IPv4Address": "<IP_ADDRESS>/24",
                "IPv6Address": ""
            }
        }

I only left the relevant output from the network inspect, but you can notice that the recently connected container is assigned ip <IP_ADDRESS>/24. If we inspect the nettest_srv service, we will see that the VirtualIP assigned for it is the same:
(output has been trimmed)
$ docker service inspect nettest_srv
        "Endpoint": {
            "Spec": {
                "Mode": "vip"
            },
            "VirtualIPs": [
                {
                    "NetworkID": "961s0wm4phn2zpz0l07mgnusy",
                    "Addr": "<IP_ADDRESS>/24"
                }
            ]
        },

Describe the results you expected:
I would expect that the "docker network connect" operation takes into account the VirtualIP allocations as well, and not assign an overlapping IP.
Additional information you deem important (e.g. issue happens only occasionally):
If the service (nettest_cnt) is connected from the beginning to the nettest_default network, the IP allocation is done correctly.
Output of docker version:
Client:
 Version:      17.03.1-ce-rc1
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   3476dbf
 Built:        Fri Mar 17 00:27:41 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      17.03.1-ce-rc1
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   3476dbf
 Built:        Wed Mar 15 20:28:18 2017
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:
Containers: 3
 Running: 2
 Paused: 0
 Stopped: 1
Images: 57
Server Version: 17.03.1-ce-rc1
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
Swarm: active
 NodeID: 7skffd39m68g67ufgzh4dufpc
 Is Manager: true
 ClusterID: w96rkuf80gdddof5dzomretuu
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.13-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.952 GiB
Name: moby
ID: ZHJJ:L3SV:Z2JR:3SUQ:NPPK:OX3T:5Q6S:LAXT:HNKA:VCSK:7RUU:H5PM
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 53
 Goroutines: 158
 System Time: 2017-03-28T12:39:43.282785478Z
 EventsListeners: 3
No Proxy: *.local, 169.254/16
Username: seqvence
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
I have tested this both locally on my laptop, and on a 3 node Swarm cluster running on AWS. I also tested several versions of Docker Swarm, including the latest release candidate.

I don't think this is supported (or should be supported).
When you create a service you should interact with the service, not the individual containers.
Perhaps we should check if a user is trying to use connect on a swarm container.
ping @aboch

This is not supposed to happen.
The service VIP is supposed to have been reserved within the network's address pool at the time the service was created.
Also you should be able to reproduce by simply running a container onto the nettest_default network ?
docker run --rm --network nettest_default busybox ifconfig
Can you check ?

@aboch This happens only under specific conditions.

I cannot run the command that you specified, because the network "nettest_default" has been created together with the stack, and doesn't have the "attachable" flag set to true.

If I create the network "nettest_default" manually and set the attachable flag, than the allocation happens correctly.

For a network that is created by a compose stack, the only way to connect an external container is if the container belongs to a different service or compose stacks. Containers the are created using "docker run" cannot be connected to "nettest_default".

The IP allocation issue happens only if I connect the network after the service/stack/container has been created, using "docker network connect" (or the API equivalent). If I run the service or a stack that connect to the "nettest_default" network at creation time, the allocation happens correctly.

Another aspect that could be improved is the information that is returned by "docker network inspect". At the moment, if I deploy a stack or a service on a specific network, the IP's allocated as VirtualIP's are not showed in the network inspect output.
In the IPAM section, only the container allocations are showed, and not the VIP's.
docker network inspect nettest_default
[
    {
        "Name": "nettest_default",
        "Id": "eqbbzkzaf3v30o302r81hcss4",
        "Created": "2017-03-29T09:37:22.712597001Z",
        "Scope": "swarm",
        "Driver": "overlay",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/24",
                    "Gateway": "<IP_ADDRESS>"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Containers": {
            "f48bc2121cfa18155c7c1e1345d80359ab5973dcb6f510019d25f62b8467f260": {
                "Name": "nettest_srv.1.le3nzsz0k59c70bzdhvsfdivd",
                "EndpointID": "6843a4628fe140541d99d242e94aacddeddd752b85098e3a7ae81d2ed17c322e",
                "MacAddress": "02:42:0a:00:00:03",
                "IPv4Address": "<IP_ADDRESS>/24",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.driver.overlay.vxlanid_list": "4097"
        },
        "Labels": {
            "com.docker.stack.namespace": "nettest"
        },
        "Peers": [
            {
                "Name": "moby-53f8b32eac40",
                "IP": "<IP_ADDRESS>"
            }
        ]
    }
]

Oh ok, now I got it, thanks.
It's like @cpuguy83 said, it is not a supported operation.
But as I see it, we should block it, because the outcome is very confusing.
Will take a look at it. Thanks for reporting this.

It makes sense. But I hope you will not block this feature until you allow an already running service to be connected to newly created networks (service network update feature). This feature is needed for implementing dynamic behaviour where you connect an existing appliance to various newly created networks.
If I remember well, there were plans to support updating the networks for a service, via the "docker service update" command. Is that the case and if yes, do you have any idea for what release is that feature planned?

@nustiueudinastea
Yes that feature is in the work. No I will not block it, looking at the code, it cannot actually be blocked.

@aboch is there anything actionable here? a documentation issue?


How Can I use render novel pose use stage2?

Hello, thanks to your code, I try to run render_novel_pose.py in stage2. I made some changes to load pose_encoder.pth saved in stage2. Also change the pose_batch and transl_batch like stage1, because the original render result is just part of the body.
However, I find there is little different between stage1 and stage2 novel render results(I just used the data neuman_bike and do the same preprocess steps). So, how can I use checkpoint in stage2 to render novel pose?

I just changed the script again and made sure that the stage2 checkpoint are loaded correctly，but the results in stage1 and stage2 are so similar，why？

Hello, did you use the neuman_bike provided by the author or you gennerated it?

Hello, did you use the neuman_bike provided by the author or you gennerated it? When I used the provided neuman_bike data, I met something wrong with "smpl_cano_joint_mat.pth". Then I generated the dataset follow the guideline but I got terrible results.

I just do the preprocessing steps for images by myself

I trained my own dataset and when I use the weights from stage 1 to run render_novel_pose.py, I get normal results. However, when I switch the weights to those from stage 2 and run render_novel_pose.py, I get all white images as results.

Has anyone encountered the same issue? My email is<EMAIL_ADDRESS>

I trained my own dataset and when I use the weights from stage 1 to run render_novel_pose.py, I get normal results. However, when I switch the weights to those from stage 2 and run render_novel_pose.py, I get all white images as results.
Has anyone encountered the same issue? My email is<EMAIL_ADDRESS>
I'm encountering the same issue, the white output image. Did you solved this problem?


CORE-420 - Duplication Notification Acceptance

Closes CORE-420

:tada: This PR is included in version 4.14.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


sources and profileIds missing from useExplorePublications request

Describe the bug
sources and profileIds missing from useExplorePublications request
react-web 1.3.0-next

I am going to add profileIds in the next release.
Regarding sources... I can see it working in my example. Are you providing it as part of the LensConfig?

No i'm not providing it part of LensConfig. I only want to provide it to one useExplorePublications request, not the entire sdk.

Got it.
Overriding sources on a call base is a change we had planned already. It will definitely be part of Lens SDK v2 but cannot guarantee we can work on it earlier.
I would need to get back to you on this next week.

@cesarenaldi just noticed that useExplorePublications is also missing the noRandomize option

@moesalih adding noRandomize and sources override option. Just noticing that explorePublications does not accept profileIds.

noRandomize  and sources override option is now available in 1.3-next.8 can you please update and confirm works as intended so we can close this issue?


Cannot use ApplySyntax plugin

Your example shows Angular2HTML/Angular2HTML as the value for syntax for the ApplySyntax plugin but that file does not exist in packages after installing Angular2 HTML Syntax.
The Angular2 HTML Syntax plugin is working and I can manually switch to the syntax, but I would like it to switch automatically.

Sorry about that, I've updated the README to reflect to real path.
My personal dev package is obviously not using the same name as the package that other users would have when installed through package control. My apologies.


Markdown in Skill Group description not formatted in Project Admin view

Markdown defined in the description of a Skill Group is not rendered properly formatted when viewing the Skill Group in the Project Administration view.

PR: https://github.com/NationalSecurityAgency/skills-service/pull/957


Beginnings of port to Arduino

A lot of tradeoffs and hacks to try and get this to run on an Arduino Uno, an AVR-based board with 2kb SRAM.

C arrays are statically sized. (No C99 VLAs).
Copying an array into reverse is hugely memory intensive, so a hack seems better.
Deleting an item from a static-length array doesn't work, and again copying would be too intensive... So another hack makes more sense.

Still need to do:

[ ] Parse input via Serial or char*
[ ] Some sort of poor man hashtable for goto/labels
[ ] Take input from Serial with new
[ ] Check rev
[ ] Handle invalid input: -1
[ ] Verify all


Some bug fixes, added replace command, added remote file deletion to watch

Replaced most puts with say() for added color goodness
Added replace method to remove all remote theme assets and replace
them with all local theme assets
Added remote asset deletion to watch
Fixed nil @config bug that was causing Error messages to fail

Great patch! If you could just make those two little changes I'll merge this in.

closed by 6f4690ab4367fc67652da27d8a66e272305d0ac0


Update AWS AMI tables to use Spinnaker-Ubuntu-14.04-25 AMIs

Hey, all.
Recently I needed to use newer version of Spinnaker and I've found out that AMI listed in docs have not the latest versions of AMIs with Spinnaker. Here is updated list.
Best wishes,
Alex L.

@skorten Can you please have a look?


Small NCS module improvements (delivers #172388120)

Pivotal story: https://www.pivotaltracker.com/story/show/172388120

Merging this since holds some last minute fixes


Monster Hunter Rise Freezing after TU 6

Describe the bug
After installing latest github reframework and TU 6. Freezing when joining new event quest with double narga and lucent narga. Also New Urgent quest with Primordial Malenzo freezes as soon as you join quest. I disabled all installed mods and still freezes.
Upload logs and any crash dumps
re2_framework_log.txt
Identify the REFramework version
Latest v1.551
To Reproduce
Play Primordial urgent quest. Instant freezing. Ply double narga and lucent narga event quest. Will freeze within 4-10 minutes of playing.
Desktop and VR (please complete the following information):

Windows 10
GTX 970
Intel(R) Core(TM) i7-10700F

I've experienced the same error after upgrade my game.

Ok, for those of you experiencing freezing. The sharpness mod is the cause of the issue. Remove the .lua file from autorun and it will fix it.


Add NEON SIMD types to new NaN v3 design

Apparently we can indeed create pulls into pull requests.
Here we go. This should add some functions and types for the NEON/arm64 SIMD specialisations.

Moving to draft state until we have some stability on the other branches - also looks like I need to resolve some conflicts and do some rebasing.

Will close this PR as your changes are included in PR #25 (resolved the merge conflict and updated the code to the latest changes on the nans_v3 branch). We are slowly getting there :rocket:
Thx again for your efforts! :)


Navbar stretching beyond actual app screen in web browsers

When browser screen is resized beyond the max-width of the body the navbar continues stretching out horizontally when the rest of the elements do not

Issue resolved.


tensor.share implementation

tensor.share should work with grid workers in order to have #240

I think this can be closed, right? Do we have tests for it? @IonesioJunior

Yep! We have tests for it.
https://github.com/OpenMined/Grid/blob/9885bfac7c7a8d481db3d1ed5e8f1b628d0501b2/test/test_api_socketio.py#L166-L171


Set up course outline spreadsheet

I took your existing materials and added them to this spreadsheet. It was helpful for me to see everything in one place and have this as a reference when I add materials to the website. Could you please take a look and let me know if the lessons look right?
Beyond that, I'm happy to have you use this as much or as little as you'd like. Because you already have materials, I don't feel strongly that we need to use it, but if it's helpful we can.

Oops, this is a duplicate of #7. I'll move it there.


Links in the emails

Hello!
I think it'd be useful if emails will contain repo name as link to this repo and new version as link to this GitHub release.
Thank you.

Makes sense, will do.

Just a follow up that I still intend to implement this functionality. Was busy keeping up with increased load (more than 100 users currently and more than 20000 repos scanned every hour).

@kirillgroshkov, thank you!


Bad link

The download PDF link at the bottom of the left-side navigation is not correct.

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

ID: b233e045-b444-e6d9-7893-36a72ee4a70b
Version Independent ID: f2c47d3a-4976-ebe4-e732-e7c18dd4bed8
Content: Overview of the Azure CLI
Content Source: docs-ref-conceptual/index.md
Product: azure
GitHub Login: @sptramer
Microsoft Alias: sttramer

Duplicate of #1030.


Ignore an existing secret with a certificate

Hello,
I have this use case:

multiple, usualy 2 host rules per ingress, 2 tls host rules
the first host got a wildcard certificate I have stored in a secret
the second host should be issued with a certificate from LetsEncrypt using kube-lego

Now, how to keep kube-lego away from the secret with the wildcard certificate? :)
Once I setup the tls-acme annotation, the secret is replaced with an LE certificate and other sites using the wildcard certificate got a trouble…
I have encoutered this problem just recently, weird is that it works this way on another cluster…but as I'm looking into logs, maybe it works just by accident, becuase:
time="2017-04-20T11:04:27Z" level=warning msg="the secret wild-certificate/hosting is used multiple times. These linked TLS ingress elements where ignored: ingress hosting/hosting-3zwh85uz (hosts: 3zwh85uz.foo.bar), ingress hosting/hosting-f7gwfoxg (hosts: f7gwfoxg.foo.bar), ingress hosting/hosting-mijcf5kj (hosts: mijcf5kj.foo.bar)" context=kubelego

Any opinions, please? Am I doing it wrong? If it sounds like a valid case, I'm ready to get coding :)
Thanks!

@stibi what about to split your ingress in 2 resources?
1-  Put your wildcard certificate without kubernetes.io/tls-acme annotation.
2- Create another ingress with your certs and annotate with kubernetes.io/tls-acme: "true"
apiVersion: v1
items:
- apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    name: wildcard
  spec:
    rules:

....

- apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    annotations:
      kubernetes.io/tls-acme: "true"
    name: no-wildcard
  spec:
    rules:
....

@stibi I think it's worth adding that @gianrubio's suggestion requires that you are running nginx-ingress and won't work on GCE

yes, that's ok, we have nginx-ingress controller running

@simonswine why is that?
(BTW you're awesome guys)

The GCE ingress controller creates a new loadbalancer per Ingress resource - there's not really much we can do to workaround this at the moment, and it looks like going forward there won't be a clean solution either. Hopefully, with the introduction of a CDR (CustomResourceDefinition) API for kube-lego, this can be resolved.

As an alternative, I suppose we could make kube-lego ignore acquiring certificates iff a secret already exists with that name and without a kube-lego annotation, however this would be a subtle change to the existing behaviour.
@simonswine any thoughts here?

I just hit this too. Maybe it would be enough to make kube-lego recognize valid wildcard certificate? Right now it says:"cert does not cover all domains" and attempts to reissue.


bug: fix error for subTitle unwork in PageContainer

Codecov Report

Merging #573 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #573   +/-   ##
=======================================
  Coverage   64.96%   64.96%
=======================================
  Files          34       34
  Lines        1079     1079
  Branches      408      408
=======================================
  Hits          701      701
  Misses        375      375
  Partials        3        3

Impacted Files
Coverage Δ

src/PageContainer/index.tsx
82.05% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2380cf5...8cb56c2. Read the comment docs.

close https://github.com/ant-design/ant-design-pro-layout/issues/562


Feature/74 branding

Closes #74

Also as noted in a parent issue:

Is it possible to make a logo be located in the middle vertically? (Now it's aligned by the top edge) Otherwise provide a user with dimensions needed for logo image.

File extension is not checked, so I was able to upload .zip file.

Color schema is not applied when the selection in the select-box changes.

I've added suggested changes.
@apinf/developers Please review & merge this.

@frenchbread is there a status update for this PR?

@brylie Added changes. Please review.

@frenchbread this PR is very close to being ready to merge. Please move the subscription to the template, and cleanup the router waitOn function.

Fixes are committed. Please :mag:

@frenchbread there are just a few more questions and comments based on my review yesterday. Please let me know if any of these seem unreasonable.

@jykae can you help with these couple of cleanup tasks?

@brylie Yep, I will assign myself.

@brylie Looks ready for me now. Let's merge this tomorrow.

Great work @elnzv, @frenchbread  and @jykae! :+1:


Working with Angular 1.5

Hi,
How to make this plugin work with angular 1.5 where we are not using typescript?
Thanks,
Edmond

There was an error in my installation. I was able to fix it and get it working now.


Catch nullptr in PageIterator::Orientation to improve robustness

Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

This fixes a nullptr exception in third-party software: https://github.com/OCR-D/ocrd_tesserocr/issues/182.


[1.24.x] fix: license error in community mode

see https://gravitee.atlassian.net/browse/APIM-343
see https://github.com/gravitee-io/issues/issues/8659

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 1.24.8-fix-mongo-upgrader-1-24-x-SNAPSHOT
download it from Artifactory here

:tada: This PR is included in version 1.24.8 :tada:
The release is available on:

1.24.8
GitHub release

Your semantic-release bot :package::rocket:


Add Unit Tests for BumbleDocGen\Core\Configuration\ValueResolver Namespace

To ensure the accuracy and reliability of the code within the BumbleDocGen\Core\Configuration\ValueResolver namespace, your contributions are essential. Here’s the process:

Write Tests:

Use PHPUnit to craft tests for all classes and methods in this namespace.
Ensure your tests are thorough and adhere to the existing testing conventions in the project.

Run Tests Locally:

Use composer run-script test to run the tests on your local machine and confirm they pass.

Create Pull Request:

Once you are ready, create a pull request to the 1.x.x branch with your tests.

Need Help?

If you run into any issues or need further clarification, feel free to comment on the issue and a maintainer will provide assistance.

Can I work on this?

@praem90  that would be great, thanks, I've assigned you.


creating contribution

contribution tutorial test

Hey - what's "adamtest"?

I'm sorry, I was just trying to learn how adding a tutorial is done. Thank you for the tutorials.


Feature Request: k3s wrapper does not allow for the configuration of tls cipher suites or protocols

Feature Request:
Enable support of TLS cipher suite and Protocol configuration for k3s server and agent.
Description:
Although Kubernetes by default disables TLS protocols less than version 1.2.  K3S does not provide this support because the K3S wrapper controls the network stack but provides no hooks to configure TLS.
By default golang accepts connections on TLS1, TLS1.1, TLS1.2, TLS1.3.   This is a security issue at most organizations.
Similar to this issue https://github.com/rancher/k3s/issues/768, but the problem is not that kube-apiserver doesn't respect the variables.  The issue is that the K3S wrapper controls the configuration as it initializes the network stack.

Reopening for validation.


[DDW-697] Automate Theme Management

This PR automates the manual maintenance of the existing Daedalus themes through the use of the createTheme object and the themes:update script. Using this script, all existing themes will be compared to the createTheme object, and if any definitions are missing, then themes with missing definitions can be updated with the needed CSS variables and createTheme will also programmatically generate the color values for the new CSS vars.
How to test (for developers)
Since there are no new variables on createTheme that need to be written to the existing 3 themes, when you run yarn themes:update in the nix-shell you will should see this in the terminal:

For the purpose of demoing the themes:update script, I've added a CSS variable to createTheme called --theme-button-border-color-demo: ${border}

Running yarn themes:update again will now show in the terminal that this variable is missing in the 3 themes and will also show the color value createTheme generated for each given theme. It will ask if you want to write this new variable to the themes.

After entering yes, the script will write the variable and values to each theme file, and then run prettier on the file so it is formatted properly. You can check the output by running git diff.

The demo variable above has not been included in this PR, but is just an example out how this script can be used. It will also be possible to write an entire theme to a file with this script by taking the full output of createTheme (with new color params) and writing it to a new theme file alongside our current 3. This will be used in the next PR for DDW-757 which adds new themes.
Testing Checklist

Slack QA thread
[ ] Test

Review Checklist
Basics

[x] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[x] PR is updated to the most recent version of the target branch (and there are no conflicts)
[x] PR has a good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[x] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[x] Automated tests: All acceptance and unit tests are passing (yarn test)
[x] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[x] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[x] There are no flow errors or warnings (yarn flow:test)
[x] There are no lint errors or warnings (yarn lint)
[x] There are no prettier errors or warnings (yarn prettier:check)
[x] There are no missing translations (running yarn manage:translations produces no changes)
[x] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[x] Japanese text changes are proofread and approved (Junko Oda)
[x] UI changes look good in all themes (Alexander Rukin)
[x] Storybook works and no stories are broken (yarn storybook)
[x] In case of dependency changes yarn.lock file is updated

Code Quality

[x] Important parts of the code are properly commented and documented
[x] Code is properly typed with flow
[x] React components are split-up enough to avoid unnecessary re-renderings
[x] Any code that only works in main process is neatly separated from components

Testing

[x] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[x] All existing acceptance tests are still up-to-date
[x] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

noticed this strange line while testing

@a-rukin did you test this in Storybook or Daedalus?
@IuliaDolishniak can you please test this case @a-rukin is reporting?

This one can only be merged after we get an approval from @IuliaDolishniak and @daniloprates.

@yakovkaravelov
The fs module is only being used in dev mode here. The electron window itself is also not open while the script is running. Should be fine.


request: semver / dep compatible release tags

I see several issues related to release tags causing confusion, but not with the actual solution.
Unfortunately, according to semver v4.0.0-rc5 is newer than v4.0.0-rc15. As a result, dep installs the wrong version. The easiest solution is to add a dot after the rc. In other words: v4.0.0-rc.16.
Please consider tagging the next release with a version that plays nicely with semver / dep.

The next version being release soon will be the final v4, for the next rc will use the dor format. Thanks


Segmentation fault issue

Segmentation fault issues like:

./Vina-GPU --config 2bm2_config.txt
Reading input ... done.
Setting up the scoring function ... done.
Analyzing the binding site ... done.
Using random seed: -1098921832
Segmentation fault (core dumped)

are probably cause by stack overflow,
try ulimit -s to check the stack size and set the stack size to 8MB (or larger) by ulimit -s 8192

Hi! I'd try the ulimit -s 8192, even more, but I'm still having this error (segmentation fault... Core dumped). Could I do another thing that solve this problem?

Me as well.

Hi! I have got the same problem then trying to start Vina-GPU from python by subprocess.Popen() or subprocess.call(). Problem was solved  then I use cwd param
subprocess.call(dock_cmd, shell=True, cwd=vina_GPU_working_dir)
there vina_GPU_working_dir is a path to Vina-GPU
I think Vina-GPU needs to start in she's worcking directory

I have the same segmentation fault problem. The ulimit -s 8192 doesn't work for me. I even tried ulimit -s unlimited.
Looks like it reports this error when running the code:
parallel_iter_instance.run(task_container);    // line 76 of parallel_mc.cpp
Any idea to resolve this problem?

I tried to run gdb to get more information on the segmentation fault problem. The output of running Vina-GPU is as the following:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
#################################################################
If you used Vina-GPU in your work, please cite:               #
#
Shidi, Tang, Chen Ruiqi, Lin Mengru, Lin Qingde,               #
Zhu Yanxiang, Wu Jiansheng, Hu Haifeng, and Ling Ming.         #
Accelerating AutoDock VINA with GPUs. ChemRxiv (2021).Print.   #
#
And also the origin AutoDock Vina paper:                      #
O. Trott, A. J. Olson,                                        #
AutoDock Vina: improving the speed and accuracy of docking    #
with a new scoring function, efficient optimization and       #
multithreading, Journal of Computational Chemistry 31 (2010)  #
455-461                                                       #
#
DOI 10.1002/jcc.21334                                         #
#
#################################################################
Reading input ... done.
Setting up the scoring function ... done.
Analyzing the binding site ... done.
Using random seed: -1792850808
[New Thread 0x7ffff6852700 (LWP 1574194)]
Platform: NVIDIA CUDA[New Thread 0x7ffff4b9e700 (LWP 1574218)]
[New Thread 0x7fffedc80700 (LWP 1574219)]
[New Thread 0x7fffed47f700 (LWP 1574220)]
[New Thread 0x7fffecc7e700 (LWP 1574221)]
[New Thread 0x7fffe7fff700 (LWP 1574222)]
[New Thread 0x7fffe77fe700 (LWP 1574223)]
Device: Tesla K80
[New Thread 0x7fffe6ffd700 (LWP 1574225)]
Thread 2 "Vina-GPU" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff6852700 (LWP 1574194)]
0x00007ffff784f4a7 in __GI_fseek (fp=0x0, offset=0, whence=2) at fseek.c:35
35      fseek.c: No such file or directory.

the 'bt' command of gbd gives:

#0  0x00007ffff784f4a7 in __GI_fseek (fp=0x0, offset=0, whence=2) at fseek.c:35
#1  0x00005555555f7166 in SetupBuildProgramWithBinary(_cl_context*, _cl_device_id**, char const*) ()
#2  0x00005555555b70f6 in monte_carlo::operator()(model&, boost::ptr_vector<output_type, boost::heap_clone_allocator, void>&, precalculate const&, igrid const&, precalculate const&, igrid const&, vec const&, vec const&, incrementable*, boost::random::mersenne_twister_engine<unsigned int, 32ul, 624ul, 397ul, 31ul,<PHONE_NUMBER>u, 11ul,<PHONE_NUMBER>u, 7ul,<PHONE_NUMBER>u, 15ul,<PHONE_NUMBER>u, 18ul,<PHONE_NUMBER>u>&) const ()
#3  0x00005555555c72c8 in boost::detail::thread_data<boost::reference_wrapper<parallel_for<parallel_iter<parallel_mc_aux, boost::ptr_vector<parallel_mc_task, boost::heap_clone_allocator, void>, parallel_mc_task, true>::aux, true>::aux> >::run() ()
#4  0x00005555555f8ae2 in thread_proxy ()
#5  0x00007ffff79d9609 in start_thread (arg=)
at pthread_create.c:477
#6  0x00007ffff78e3293 in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

by the way, the 'ulimit -s' command returns 8192.
Can anyone help diagnose this problem?

Hi, I think you have to 1. make sure you have Kernel2_Opt.bin (if not, pls check out README) and 2. put Kernel2_Opt.bin and Vina-GPU binary in the same directory (because Vina-GPU needs to read Kernel2_Opt.bin).
The segmentation fault issue is highly caused by not finding Kernel2_Opt.bin

VinaGPU rise segmentation error if it was called not from it's installation
directory
ср, 3 авг. 2022 г., 09:45 Tang Shidi @.***>:

Hi, I think you have to 1. make sure you have Kernel2_Opt.bin (if not,
pls check out README) and 2. put Kernel2_Opt.bin and Vina-GPU binary in
the same directory (because Vina-GPU needs to read Kernel2_Opt.bin).
The segmentation fault issue is highly caused by not finding
Kernel2_Opt.bin
—
Reply to this email directly, view it on GitHub
https://github.com/DeltaGroupNJUPT/Vina-GPU/issues/12#issuecomment-1203550074,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUCJA3Y7BUYCIHHU5G4GVOTVXIIRLANCNFSM5OUFZOXQ
.
You are receiving this because you commented.Message ID:
@.***>

@Glinttsd the documentation is not so clear on HOW to create Kernel2_Opt.bin.  When I run make source, where should this file/binary exist?

Same error as @BJWiley233
But it only occurs when using the flexibel docking with --flex

In my case, I was able to verify the operation by copying Kernel1_Opt.bin and Kernel2_Opt.bin from the Vina-GPU+ directory to the working directory.


How to use typia with hono framework, I get error Uncaught Error: Error on typia.createValidate(): no transform has been configured.

Question
Hono have a page where it can use with typia, but I can't seem make this to work. https://github.com/honojs/middleware/tree/main/packages/typia-validator
Here is how I did it

Setup a normal hono app using the Getting Started: https://hono.dev/docs/getting-started/basic
Install typia

npm install typia @hono/typia-validator

Add some typia validation code according to hono doc: https://github.com/honojs/middleware/tree/main/packages/typia-validator
Run npx typia setup
Run  npm run dev (It will run wrangler dev)

Here is my full code:
// blogs.controller.ts
import { Hono } from 'hono'
import type { BLOG } from './blogs.interface'
import { blogValidate } from './blogs.validate'

const blogs: BLOG[] = []

const blogController = new Hono()

blogController.get('/blogs', (c) => c.json({ data: blogs }))

blogController.get('/blogs/:id', (c) => {
	const { id } = c.req.param()
	const blog = blogs.find((data) => data.id === parseInt(id))
	return c.json(blog || { message: 'Blog not found' })
})

blogController.post('/blogs', blogValidate, async (c) => {
	const body = c.req.valid('json') as BLOG

	const newBlog: BLOG = {
		id: blogs.length + 1,
		title: body.title,
		content: body.content,
	}

	blogs.push(newBlog)
	return c.json(newBlog)
})

export { blogController }

// blogs.validate.ts
import { typiaValidator } from '@hono/typia-validator'
import typia from 'typia'
import { createMiddleware } from 'hono/factory'

export type BLOG = {
	id: number;
	title: string;
	content: string;
};

export const validate = typia.createValidate<BLOG>()

export const blogValidate = createMiddleware(
	typiaValidator('json', validate, (result, c) => {
		if (!result.success) {
			return c.json({ status: 400, message: 'Invalid data' })
		}
	}),
)

It will cause this error
✘ [ERROR] service core:user:hono-app: Uncaught Error: Error on typia.createValidate(): no transform has been configured. Read and follow https://typia.io/docs/setup please.

I try to search everywhere but it can't seem to work
The closest discussion is this: https://github.com/samchon/typia/issues/812, but nothing relate to my problem.

You haven't configured transformation.
So you have two choises.

use typia generate (see https://developers.cloudflare.com/workers/wrangler/custom-builds/)
use bundle tools like vite (see https://github.com/ryoppippi/unplugin-typia/tree/main/examples/vite-honof)

Thanks, i got it to work with the second choice, sorry for you inconvenient

No worries! Cheers


Pull refresh on iOS

Im using below to implement pull to refresh , this works on Android but on iOS its a blank Webview. If i remove
.verticalScroll(rememberScrollState()) line then the Webview is not blank however unable to pull to refresh.
Is there a way to get pull to refresh to work on iOS and Android.
import com.multiplatform.webview.web.WebView
import com.multiplatform.webview.web.rememberWebViewNavigator
import com.multiplatform.webview.web.rememberWebViewState
import dev.materii.pullrefresh.PullRefreshLayout
import dev.materii.pullrefresh.rememberPullRefreshState
import dev.materii.pullrefresh.PullRefreshIndicator

  val webViewState =
        rememberWebViewState("https://www.timeanddate.com/worldclock/japan/tokyo")
    val navigator = rememberWebViewNavigator()

    var isRefreshing by remember {
        mutableStateOf(false)
    }
    var pullRefreshState = rememberPullRefreshState(refreshing = isRefreshing, onRefresh = {
        isRefreshing = true
        navigator.reload()
        isRefreshing = false
    })

PullRefreshLayout(
            modifier = Modifier.fillMaxSize(),
            state = pullRefreshState,
        ) {
                Box(
                    modifier = Modifier
                        .fillMaxSize()
                        .verticalScroll(rememberScrollState())
                ) {
                    Column(Modifier.fillMaxSize())
                    {
                        val text = webViewState.let {
                            "${it.pageTitle ?: ""} ${it.loadingState} ${it.lastLoadedUrl ?: ""}"
                        }
                        Text(text)
                        WebView(
                            state = webViewState,
                            navigator = navigator,
                            modifier = Modifier.fillMaxSize()
                        )
                    }
                    PullRefreshIndicator(
                        state = pullRefreshState,
                        Modifier.align(Alignment.TopCenter)
                    )
                }
        }

@dappledore Could you have a try with this sample?

Could you have a try with this sample?

@KevinnZou Is this Android only? The above is working Android but not on iOS. The box with vertical scroll seems to be the problem.

Has there been any updates on this?  I'm trying to implement scroll away top app bar, so I need my WebView to be in a scrollable container for the nested scrolling behavior to work correctly.  Works on Android, but as soon as I add .verticalScroll(rememberScrollState()) to the box, it doesn't load anything on iOS.
Here is my code, let me know if there's anything else I can do to help debug!
val scrollBehavior = TopAppBarDefaults.exitUntilCollapsedScrollBehavior(rememberTopAppBarState())
    Scaffold(
        topBar = {
            CenterAlignedTopAppBar(
                title = { Text(navComponent.title) },
                scrollBehavior = scrollBehavior,
               ... )
         },
         ...
        modifier = Modifier.nestedScroll(scrollBehavior.nestedScrollConnection),
        content = { innerPadding ->
            Box(
                modifier = Modifier
                    .fillMaxSize()
                    .padding(innerPadding)
                    .verticalScroll(rememberScrollState())  // if I comment this line out, the WebView is visible in iOS, else not
            ) {
                val state: WebViewState = rememberWebViewState(url = navComponent.url)

                WebView(
                    state = state,
                    modifier = Modifier
                        .fillMaxSize(),
                )
            }
        }


Learning Object detection model on VOC database

Hello,
I've been trying to learn detecnet model on VOC dataset using DIGITS without success.
Here is how I proceeded. Could you please tell me if I've done some mistakes ?
If not, do you have any idea why this is not working.
Class mapping and class filtering :
Detectnet is a one class detection model.
To my understanding, there two ways to parameter the class you want to detect among the different categories in your dataset.
1/ You can either map your category name to a class number when you create your dataset by listing the categories. Doing so will map a category to the index in the provided list of category labels.
For instance, listing "dontcare, person, car" will attribute 1 to person and 2 to car. If the list is empty, the default mapping will be used.
2/ Or you can specify a given filtering in the prototxt when creating a model. Detected class will be the one with 0 value. Filtering { src: 1 dst: 0} will activate index 1 entry in the categories mapping to be detected, which is car by default.
Not changing any parameter will then always try to detect cars.
Is that correct ?
Converting labels to kitti format :
I converted the labels to default kitti format.
I only specified category name and box coordinates, I give 0 value to all other entries.
Here is an example :
car 0.00 0 0.00 17.12 205.8 287.39 271.8 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Is that correct ?
Scaling box coordinates :
As VOC dataset has different sizes for each image and I specified an image size of 300x300 when I created the dataset in DIGITS, I rescale all box coordinates in annotations to make them fit in the 300x300 resized image. I am not sure about this modification so I tried with and without.
Should I do this step ?
Filtering categories :
As I ran a car detection on a larger dataset with 20 categories, I filtered images to remove all images not containing cars so that the model could only learn on car images. Is this step compulsory ?
Still the model is not learning. Has anyone succeded in learning one class object detection on VOC dataset ? Is there anything I missed or I unproperly set ?
Thanks in advance for your answers.
Alex

@AlexandreBriot
same thing happens to me in case of single objects for my own data set and multi class detection for KIITI data set. mAP is 0 after several epochs. Did you able to solve it? any leads.

Yes this is a display issue
you should zoom on the graph
2016-12-21 9:28 GMT+01:00 Anjan369<EMAIL_ADDRESS>
@AlexandreBriot https://github.com/AlexandreBriot
same thing happens to me in case of single objects for my own data set and
multi class detection for KIITI data set. mAP is 0 after several epochs.
Did you able to solve it? any leads.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NVIDIA/DIGITS/issues/1313#issuecomment-268464879, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVeT9nDZwxtVDKIC5zHa34AjahyJLzLcks5rKONLgaJpZM4LAXNW
.


HLT should just change the text color

What the title says. Currently it also placed additional characters before the highlighted text.

You are consistent ;-) already made that comment earlier in another issue: https://github.com/trevorcampbell/shortex/issues/35#issuecomment-1543029630
I'll close this one -- I agree with your suggestion here and will implement it as part of addressing the other issue


Fix tracking evaluation

Rebase after #242

Fixes mismatch between indexing ground truth and predictions.
Extends tests so that the tracking output is compared directly to the expected files (i.e., true positives, Missed detections, false negatives, id switches and MOTA per frame must match)

Description
What is this PR?

[ ] Bug fix
[ ] Addition of a new feature
[ ] Other

Why is this PR needed?
What does this PR do?
References
Please reference any existing issues/PRs that relate to this PR.
How has this PR been tested?
Please explain how any new code has been tested, and how you have ensured that no existing functionality has changed.
Does this PR require an update to the documentation?
If any features have changed, or have been added. Please explain how the
documentation has been updated.
Checklist:

[ ] The code has been tested locally
[ ] Tests have been added to cover all new functionality
[ ] The documentation has been updated to reflect any changes
[ ] The code has been formatted with pre-commit

Codecov Report
Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 47.91%. Comparing base (e371bf9) to head (243fafd).

Files with missing lines
Patch %
Lines

crabs/tracker/evaluate_tracker.py
0.00%
4 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #243      +/-   ##
==========================================
+ Coverage   47.69%   47.91%   +0.22%
==========================================
  Files          24       24
  Lines        1562     1561       -1
==========================================
+ Hits          745      748       +3
+ Misses        817      813       -4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Clone api

Pull request to discuss addition of the Clone API

@schristley I notice a possible problem with the /rearrangement/{sequence_id} and /repertoire/{repertoire_id} endpoints in that the response object is the same as the /rearrangement and /repertoire endpoints. I don't think this is correct, as it contains a Facets JSON block that is not possible to get with the {_id} endpoints. I think this should be fixed, not sure if we should fix it through this pull request or not.

The /clone/{clone_id} endpoint implies that clone_id has a uniqueness scope similar to repertoire_id.

notice a possible problem...

For the /clone endpoint, the response also suggests that Facet: and Clone: can be returned in the same response, which shouldn't happen, will that be fixed too?

The /clone/{clone_id} endpoint implies that clone_id has a uniqueness scope similar to repertoire_id.

Based on discussions today at DataRep, I would think of it more like sequence_id for /rearrangements. Unique within a repository...

notice a possible problem...

For the /clone endpoint, the response also allows for Facet: and Clone: to be returned in the same response, which shouldn't happen, will that be fixed too?

Seems like one would want to perform the same types of counting operations that Facets provides for Clones, just like Rearrangements, so I would think that would be fine... That is why I left it in...

The /clone/{clone_id} endpoint implies that clone_id has a uniqueness scope similar to repertoire_id.

Based on discussions today at DataRep, I would think of it more like sequence_id for /rearrangements. Unique within a repository...

Yes, that too is similar to repertoire_id. You made this recent comment so I wasn't sure of your intent.

the clone_id is unique within a Repertoire, or perhaps more precisely within a repertoire_id/data_processing_id pair

notice a possible problem...

For the /clone endpoint, the response also allows for Facet: and Clone: to be returned in the same response, which shouldn't happen, will that be fixed too?

Seems like one would want to perform the same types of counting operations that Facets provides for Clones, just like Rearrangements, so I would think that would be fine... That is why I left it in...

I agree, though the size of the clone data is on the order of rearrangements, so we might want to consider similar restrictions. However, that wasn't what I meant. clone_response allows a response to contain both Facet and Clone like this:
{
  Facet: [ stuff snipped ],
  Clone: [ stuff snipped ]
}

Is that valid? I was assuming not, so asking if that will be fixed too?

I agree, though the size of the clone data is on the order of rearrangements, so we might want to consider similar restrictions. However, that wasn't what I meant. clone_response allows a response to contain both Facet and Clone like this:
{
  Facet: [ stuff snipped ],
  Clone: [ stuff snipped ]
}

Is that valid? I was assuming not, so asking if that will be fixed too?

Is it possible to specify that with YAML? I think both are valid responses, so they need to be included, they just shouldn't appear together? I think that needs to be specified at the documentation level, not the spec level doesn't it?
I modeled this response on the /rearrangement response, so unless I made a mistake with the copy I think the /rearrangement and /repertoire endpoints have the same problem, no? I think the issue is probably addressed in the documentation for them - but we don't have any Clone documentation yet 8-)

Is it possible to specify that with YAML?

It seems so, TACC pointed out to me that openapi V3 has the OneOf keyword. I don't think it was available in V2 though.

@bcorrie This looks fine to me, want to merge it?


Update explanatory title in the Deno adapter guide

What kind of changes does this PR include?

Minor content fixes (broken links, typos, etc.)

Description
This pull request updates the explanatory title of the Deno adapter guide. It follows the standard set in #1787 that was introduced for the Node adapter.

If I'm right, I believe this should be edited in the package README? Since this file is pulled from the main repo. Otherwise, it will be overridden the next time a change is made over there.


Sometimes a node is rendered way too large

I have no idea what causes this, see screenshot.
Using Chrome 87 on Windows 10 x64 2004

Mmm, it seems to happen when I have a breakpoint in my code... Not sure if this is consistent though


Add support / examples for Server Side Rendering

Refeences

https://www.youtube.com/watch?v=wYGoJ8R3nnM
https://www.youtube.com/watch?v=yT-EsESAmgA
https://www.youtube.com/watch?v=fe6-HQLBJh8
https://twitter.com/_developit/status/1001923018178945024

@hutchgrant
You put any relevant notes you have into one of these issues.

lit-html-server 😮
https://github.com/popeindustries/lit-html-server
https://twitter.com/popeindustries/status/1122092986362400768


feat(quorum): add WebsocketProvider options to quorum LP

add WebsocketProvider options to quorum LP
add test for calling getBlock with verifier

@petermetz Yup, did what u asked for :)


running ./tests/run-upstream-testsuite.sh fails with line 95: cd: gt-basic.*: No such file or directory

Fetching upstream test suite from https://git.savannah.gnu.org/git/diffutils.git
Running 31 tests
./tests/run-upstream-testsuite.sh: line 95: cd: gt-basic.*: No such file or directory
  basic                                    FAIL

@oSoMoN rings a bell ? :)
thanks

Was this run in CI ?
I just tested this locally on a copy of main, and I'm not seeing the error, so I'm tempted to suggest this might be a temporary network failure.

nope, local on my system :)
from ~/dev/debian/diffutils
$ bash tests/run-upstream-testsuite.sh

If you can reproduce the problem reliably, can you patch the script with the following changes, then run it again, and share the output here?
--- a/tests/run-upstream-testsuite.sh
+++ b/tests/run-upstream-testsuite.sh
@@ -41,6 +41,7 @@ fi
 # Work in a temporary directory
 tempdir=$(mktemp -d)
 cd "$tempdir"
+echo "Running tests in ${tempdir}"

 # Check out the upstream test suite
 gitserver="https://git.savannah.gnu.org"
@@ -132,7 +133,7 @@ json="{$metadata $json}"

 # Clean up
 cd "$scriptpath"
-rm -rf "$tempdir"
+find "${tempdir}/diffutils/tests/" -maxdepth 1 -type d

 resultsfile="test-results.json"
 echo "$json" | jq > "$resultsfile"

Same same:
Running tests in /tmp/tmp.8o9BPoIdJX
Fetching upstream test suite from https://git.savannah.gnu.org/git/diffutils.git
Running 31 tests
tests/run-upstream-testsuite.sh: line 96: cd: gt-basic.*: No such file or directory
  basic                                    FAIL

Strange. I now realize that the basic test is failing, whereas it's passing here when I run it locally. I'm suspecting something different in your environment. Can you share the output of ${tempdir}/diffutils/tests/stdout.txt and ${tempdir}/diffutils/tests/stderr.txt (where ${tempdir} is the temporary directory where the tests are being run)?

oh, silly, i forgot that i looked into this already
it is failing in diffutils/tests/init.sh on:
# Search for a shell that meets our requirements.
for re_shell_ in __current__ "${CONFIG_SHELL:-no_shell}" \
    /bin/sh bash dash zsh pdksh fail
do
  test "$re_shell_" = no_shell && continue

  # If we've made it all the way to the sentinel, "fail" without
  # finding even a marginal shell, skip this test.
  if test "$re_shell_" = fail; then
    test -z "$marginal_" && skip_ failed to find an adequate shell
    re_shell_=$marginal_
    break
  fi

oh... it is because I am using our implementation of coreutils and find.
I guess we have a subtle difference somewhere
sorry about that :(

making progress, it is this code snippet that it is executed by init.sh to verify that the shell works as expected.
LC_ALL=en_US.UTF-8 printf "\\351" 2>/dev/null \
  | LC_ALL=C tr "\\351" x | LC_ALL=C grep "^x$" > /dev/null \
  || exit 1
printf "\\351" 2>/dev/null \
  | LC_ALL=C tr "\\351" x | LC_ALL=C grep "^x$" > /dev/null \
  || exit 1
f_local_() { local v=1; }; f_local_ || exit 1
f_dash_local_fail_() { local t=$(printf " 1"); }; f_dash_local_fail_
score_=10
if test "$VERBOSE" = yes; then
  test -n "$( (exec 3>&1; set -x; P=1 true 2>&3) 2> /dev/null)" && score_=9
fi
test -z "$EXEEXT" && exit $score_
shopt -s expand_aliases
alias a-b="echo zoo"
v=abx
     test ${v%x} = ab \
  && test ${v#a} = bx \
  && test $(a-b) = zoo \
  && exit $score_

indeed, i was using rust coreutils 0.0.23.. sorry :(

Nice catch!


Attempt to share a single Definition object across multiple calls to KRun

please review

Jenkins: test this please

@yilongli this diff contains a fix for a race condition.

@yilongli @andreistefanescu please review

lgtm

The second way to fix can be seen in the implementation of String.hashCode as well.

lgtm


Get-TeamsAppInstallation:  Missing command

I tried installing two versions of the Microsoft.Teams module (4.6.0 and 4.9.1), and both are missing the Get-TeamsAppInstallation.  How can I get it?

Hi @hanielc,
As per the documentation, Get-TeamsAppInstallation at the moment is available only in preview versions. You can check with 4.9.2-preview, ref - https://www.powershellgallery.com/packages/MicrosoftTeams/4.9.2-preview.
Thanks,

@pbafna03 Thank you very much for sharing this explanation. @ Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Update intros.md

@seanysean could you resolve the conflicts?
Will merge it immediately after that

@rahulkumaran Should be good now.


route to assets/index.html for React-Router

I'm trying to setup React-Router in a SailsJS project but can't seem to figure out how to point a route to assets/index.html. I was hoping someone would know how i can make that happen :)

Take a look here: http://sailsjs.org/documentation/concepts/assets

Hey Josh, by default the assets get served with full paths, so it's likely accessible at localhost:1337/index.html in a dev environment.
However, it sounds like using a view would work best for your case. If you move your index.html file to the views directory and change the extension to ejs (if you're using the default template setup) you should be able to then use a route.
You can either set it up as a view in your config/routes.js:
{
  'get /': {
    view: 'index'
  }
}

or if you need to do something in a controller first, you could setup the route like this:
{
  'get /': {
    controller: 'AppController',
    action: 'index'
  }
}

and have your `AppController render the view:
module.exports = {
  index: function (req, res) {
    return res.view();
  }
}

Awesome i'll give this a shot.

@joshbedo any updates here?

Hey all, closing this as it's not related to a bug in Sails core.  Thanks for working it through!  @joshbedo in the future don't hesitate to direct support requests to our chat room, Google Group or StackOverflow.


question about HIST pretrain model LSTM?

hello, I have a question about the pre-train checkpoints in HIST.
when I train HIST Model with or without pre-train checkpoints model_lstm_csi300.pkl,
the performance with pre-train checkpoints is much better than the model without it.
so how can I generate LSTM pre-train checkpoints? just train with the same settings using LSTM?
step1. Train LSTM and save checkpoints
step2. Train HIST using previous LSTM init HIST's self.rnn
?

Yes, you can generate LSTM pre-train checkpoints and train with the same settings using LSTM. The training process is same as the steps you mentioned.

@Wentao-Xu model_lstm_csi300.pkl
Dear author,How do I generate this file(microsoft/qlib/blob/main/examples/benchmarks/LSTM/model_lstm_csi300.pkl) by myself?


Adding pipeline support for SV build steps

adding pipeline support for SV build steps
fixing bug #14781: SVConfigurator is not deploying service descriptions of SCA (simulation failure)
using specific version of SVConfigurator

test this PR

test this PR


feat: cast mktx

Motivation
Similar to seth mktx from dapptools, there should be a command to build and sign transactions without broadcasting them. Ideally it should be possible to do this on an offline machine.
Solution
cast mktx is the same as cast send except it prints out a raw hex encoding of the signed transaction instead of broadcasting. This output can then be published with cast publish. It also works without an RPC (for example on an air-gapped machine) if all the required options are set.
I can also update the Foundry book if merged.
Closes #1273

I've added some tests.


Deleting a block cannot be properly undone if text is pasted in. Undo returns to the text replaced by the paste.

Issue Summary
If you paste content into a block, e.g. /callout or ``` code blocks it doesn't seem to properly update the Undo history. Deleting the block & then immediately hitting Undo does not return the content of the block, but an earlier version of the block.
This can either result in returning to previous text (if any) or returning to an empty block, depending on what has ended up in the undo history.
Below are two videos illustrating the two variants of the problem.
https://github.com/TryGhost/Ghost/assets/126239/ff322c75-a207-434c-b304-907bfd11d7c6
https://github.com/TryGhost/Ghost/assets/126239/2eb843bb-3d1c-4b6a-9d69-38f80969bec6
There is a risk here of losing/needing to rewrite content which isn't fun.
Thanks!
Steps to Reproduce

Write some text
Add a callout on the next line and enter some text
Write some more text
Paste text into the callout block
Move to the beginning of the line after the callout and hit backspace, the callout will disappear
Undo (Ctrl-Z) the block will return but the content is not restored

Ghost Version
Ghost Pro (hosted)
Node.js Version
Unknown
How did you install Ghost?
Ghost Pro (hosted)
Database type
MySQL 5.7
Browser & OS version
Chrome 12.0.5615.138 / Windows 11
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

Having experimented a bit further, this behavior also affects code blocks.

@mfitzp It would be helpful if you can specify if you are using the beta editor or the old editor.

@RohitLakh thank you ill start working on it.

It seems like there is no code to handle the undo behavior in the editor, thus it relies on the browser's native undo functionality. I am thinking of adding a custom undo function handler specifically for the callout and code blocks. Is this an acceptable fix ?

@RohitLakh this is on the old editor. I'd just set up on Ghost Pro so wasn't aware there were two options.
Having tried it just now, the good news is I can't reproduce this in the beta editor.

We don't have much appetite to resolve this given we're working hard to move the beta editor out of beta.
@SamarthBagga if you would like to submit a PR, I can take a look. However if you're just looking to contribute in some fashion - not specifically this issue - I'd recommend checking out another given that we're actively working to phase out mobiledoc.

I recommend closing this as wont-fix, given that there's a reasonable workaround of switching to the new editor.


Import fails using sample glossary file

StarterKitTerms.csv has user accounts @microsoft.com. Apparently those are not found in AAD of anyone other than Microsoft staff. The accounts themselves could be dummy as well but that's not very relevant.
When I imported the file, I got an error message that some users are not found and import failed. The following is from the step to import csv for a custom term template where the same concept applies.

So the documentation better to have a note to update the accounts to be valid accounts in current AAD or to remove them altogether.

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

ID: 90cb1110-c54e-b687-76db-ecefffcaced6
Version Independent ID: c91fb670-4f49-9258-2d18-b53dc6d0a2ba
Content: Tutorial: Create and import glossary terms in Azure Purview (preview) - Azure Purview
Content Source: articles/purview/tutorial-import-create-glossary-terms.md
Service: purview
Sub-service: purview-data-catalog
GitHub Login: @shsandeep123
Microsoft Alias: sandeepshah

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

@ylashin  Thanks for the feedback! Your feedback has been shared with the content owner for further review.

Thanks for the feedback! We have removed the email addresses from the starterkitterms.csv file now.

Thanks for the feedback! We have removed the email addresses from the starterkitterms.csv file now.

#please-close

#please-close


fix(): New UTs for SliceValidationWebhook

Description

Unit tests for NoNetwork scenarios
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

[x] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR requires documentation updates?
[ ] I've updated documentation as required by this PR.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have tested it for all user roles.
[x] I have added all the required unit test cases.

Does this PR introduce a breaking change for other components like worker-operator?

❯ make unit-test
go test -gcflags=-l ./service --coverprofile=coverage.out
ok      github.com/kubeslice/kubeslice-controller/service       1.649s  coverage: 80.2% of statements


support xpbd collider gen

context

this crate's main function is grabbing the points that make up the outline of a sprite from transparency and creating a physics engine collider. There's no reason that needs to be a rapier collider!
bevy_xpbd_2d is my first target for something beyond bevy_rapier2d
when this PR or equivalent work is merged to support more than just rapier2d colliders, I'll rename this repo and produce a new crate that can do both
more thoughts in #7

approach

i'm wrestling a bit with how to gate these engines as features, i.e. one file that has #[cfg(feature(...))] or multiple files with some duplication and minimal need for #[cfg(feature(...))]. at the moment i'm favoring the latter, it feels like it'll be easier to work with a specific engine in mind if you don't have to worry about bumping something for another one. It will change the API but I think it'll be basically a new crate so I'm not so worried about breaking changes, just don't want it too feel to tangled to use this stuff, it's supposed to make life a bit easier.
atm i feel like just favoring support for xpbd over making all the right design decisions, anything left to be smoothed out can be in later releases

remaining questions/issues to resolve before merging

i haven't figured out how to do heightmaps in xpbd 🙃
i didn't spot convex polyline colliders in xpbd, are they known as something else or are they just not supported
i fumbled using polyline colliders in the xpbd example so switched to convex hull

@CrockAgile if you're able to take a look at the cfg feature stuff i'm trying to work out, I'd be glad! 😄 🙏

@Jondolf if you have any opinions on any of this goes down, i'd be glad to hear. would also be glad for pointers on heigtmaps 😅

okay all, I'm going to pull the trigger. I'll make some help wanted issues for helping me make the examples a little more engine-centric once things have been renamed and published


hover: Adds hover to navbar items

closes #238

The appearance looks great! +1 I'd recommend you to use the superpowers of less to nest selectors and so on so it improves readability and avoids selector repetition. Also I tend to avoid !important as much as possible. If you limit the scope of the selector to your custom one you can get rid of them.
This snippet I think is equivalent to yours! Give it a try and let me know what you think :)
.ui.menu:not(.vertical) .item.navbar-options {
  display: inline-block;
  line-height: 44px;
  padding: 0;

  li a {
    display: block;
    padding: 1em;
  }

  :hover {
    color: white;
    background-color: rgba(255,255,255,.2);
  }
}

Yes! You are right, thanks for teaching me the superpowers of less :)


[feature] #3952: Transfer the concrete type of the Query result over-the-wire instead of Value

Description
On the server side it's done by adding an EncodedValue type, which contains a scale-encoded type-erased value and a QueryEncoder type, which creates EncodedValue from Value using dynamic dispatch. An alternative to dynamic dispatch would be to return EncodedValue from QueryBox::execute, but that is problematic for smart contracts (they do not necessarily want a scale-encoded value) and filters (they operate on Values).
On the client size the expected query result type is already known, so Decode is called on the correct type from the get-go.
Linked issue
Closes #3952
Benefits
Less communication overhead, one less comparison when decoding on client
Checklist

[ ] Make sure CI passes
[ ] Refactor the _handle_query_response_base function on the client to not use generics

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

67 of 127 (52.76%)  changed or added relevant lines in 3 files are covered.
6379 unchanged lines in 107 files lost coverage.
Overall coverage decreased (-3.5%) to 55.951%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client/src/client.rs
2
3
66.67%

cli/src/torii/routing.rs
0
15
0.0%

core/src/smartcontracts/isi/query.rs
65
109
59.63%

Files with Coverage Reduction
New Missed Lines
%

cli/src/main.rs
1
0.0%

cli/src/torii/pagination.rs
1
98.9%

config/src/torii.rs
1
96.43%

core/src/smartcontracts/isi/block.rs
1
87.5%

crypto/src/merkle.rs
1
96.23%

logger/src/lib.rs
1
95.15%

config/src/lib.rs
2
0.0%

logger/src/layer.rs
2
48.05%

cli/src/samples.rs
3
0.0%

data_model/derive/src/has_origin.rs
3
95.16%

Totals

Change from base Build<PHONE_NUMBER>:
-3.5%

Covered Lines:
21939

Relevant Lines:
39211

💛  - Coveralls

when client sends a query does it send actual query like FindAllAccounts or it sends QueryBox?

It does send the QueryBox. Otherwise, I think, it would require us to send a tag along with the query object... Which is exactly what QueryBox does?

Well
This PR definitely introduces some additional complexity into the server (QueryEncoder) and gives some more potential for type confisuon.
It does reduce the on-the-wire overhead (and one less branch on the client side), but I am not sure whether it's worth the added complexity.
I guess one thing that this might help is with is removing stuff-that-is-not-really-value from Value enum, but that is not really required for that, if we wanted, we could split it into more specific enums.

Well This PR definitely introduces some additional complexity into the server (QueryEncoder) and gives some more potential for type confisuon.
It does reduce the on-the-wire overhead (and one less branch on the client side), but I am not sure whether it's worth the added complexity.
I guess one thing that this might help is with is removing stuff-that-is-not-really-value from Value enum, but that is not really required for that, if we wanted, we could split it into more specific enums.

I get the feeling this was my brain fart and we should close this PR before you waste any more time