Build Error

When building DMOD NGEN image from scratch, image fails to complete.
Current behavior
When cloning a fresh DMOD repo, the docker/main/ngen/Dockerfile doesn't build.
Expected behavior
Building the docker/main/ngen/Dockerfile should be possible on a fresh install with some basic bash steps on the local host.

Screenshots

Note that the error message in the unmodified dockerfile seems to point to:
#30 2.769 Collecting fiona>=1.8
#30 2.826   Downloading Fiona-1.8.22.tar.gz (1.4 MB)
#30 2.900      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.4/1.4 MB 21.6 MB/s eta 0:00:00
#30 3.007   Preparing metadata (setup.py): started
#30 3.462   Preparing metadata (setup.py): finished with status 'error'
#30 3.467   error: subprocess-exited-with-error
#30 3.467
#30 3.467   × python setup.py egg_info did not run successfully.
#30 3.467   │ exit code: 1
#30 3.467   ╰─> [2 lines of output]
#30 3.467       Failed to get options via gdal-config: [Errno 2] No such file or directory: 'gdal-config'
#30 3.467       A GDAL API version must be specified. Provide a path to gdal-config using a GDAL_CONFIG environment variable or use a GDAL_VERSION environment variable.
#30 3.467       [end of output]
#30 3.467

@ZacharyWills, I have been unable to reproduce the error on two separate machines.

On the first, I didn't do a fresh clone, but I confirmed the Dockerfile was consistent with a fresh clone and that no image stages were used from the Docker build cache (i.e., they were all freshly built).
On the second, except for the name of the local repo directory, I followed the above steps exactly.   Again, I confirmed all the stages were built fresh and not taken from the build cache.

One thing we haven't eliminated is a possible difference in our rockylinux:8.5 images, if the tag was ever reused.  All the ngen build stages are either based on that image or one of the earlier stages.  Assuming no build caching, identical Dockerfiles, and identical behavior of Docker itself, I can't think of anywhere else a discrepancy could be.
The only way I know off the top of my head to get details for that is to run docker pull rockylinux:8.5, then find the Digest and the image id .  For mine, these were (on both environments):
Digest: sha256:5fed5497b568bcf7a90a00965987fc099edbcf44b1179a5ef6d4b47758281ca5
Image id: 210996f98b85

Confirmed the digests matched (there was an old rockylinux:8.5 as well, but I hadn't been building with it recently). A few things I did notice:

Looks like Rocky Linux is getting away from this ambiguous tagging pattern towards some with date tags. In the future when we move to 9.X it might be worth considering using a more specific version, since they do seem to reuse tags.
I am going to try next setting some new ENVs since it's almost always related to this gdal-config issue.

There isn't any chance that there's an ARG or ENV that's set with the control script that wouldn't be when run with ht e normal build right? I don't think there is but it's something I hadn't compared.
(all images here were shown with the run command docker build --no-cache -f Dockerfile -t local/ngen_dmod .

I have found some success with this over the weekend:
Need to have your memory set to probably 14GB at a minimum (16GB is preferred). I also had about 1/3 builds fail when I use the default docker build command, however when using docker buildx build -f Dockerfile -t local/dmod_ngen . it works every time.
At the moment there's an image at docker pull zwills/dmod_ngen, it won't work out of the box but I'm working on getting the standalone working now that it's compiled and ready to go, I should be able to rearrange the files for standalone use. Looking forwards to integrating with https://github.com/NOAA-OWP/DMOD/issues/234 to ensure that the image works for standalone runs, on-demand serial runs etc.


[FEAT] Links previews

It'll be closed when https://github.com/adiwajshing/Baileys/pull/2677 is merged

fixed


Allow to run FluxCD per tenant

We want the Flux checkbox right next to etcd, ingress, monitoring
This would allow to move FluxCD to system applications so it will have a packaged Helm-chart to install from

Probably locked by https://github.com/controlplaneio-fluxcd/flux-operator/issues/55

The design of Flux multi-tenancy is orthogonal from the notion of sharding, or multiple flux instances per cluster.
Sharding was added as a last resort for users who need tens of thousands of HelmReleases per cluster, it is a scaling consideration now more than an accommodation for tenancy.
While it has been considered that you can use it for other purposes like flux-per-tenant (especially where secrets need to be mounted into to the controller eg. AWS IRSA or vault for secrets) those ideas are not really well explored in documentation or tests, there is no support for multi-tenant sharding today.
Yes, the CRDs have some strong guarantees for backwards compatibility, but it doesn't cancel out this coordination issue.
Users of Flux need to have a flux CLI that matches their deployed controllers & CRDs one-to-one. If it doesn't match, you get strange errors now and then - with the extent of the mismatch and the changes between versions, the issues will vary.
So it is a coordination issue. If users on the same cluster are tenants, they should not be expected to coordinate with each other in any way. The idea of a FluxCD per tenant implies that a tenant can choose when to do this upgrade. When one tenant upgrades, they will install CRDs from the next release, all other tenants must either upgrade or suffer the mismatch.
If flux-operator always installs the latest Flux instance, that solves the coordination issue, but that tenants get to decide their own upgrade cadence and are not bound to each other seems like it would be a fundamental purpose of this kind of implementation. And it's unfortunately not as simple as a version skew policy like kubectl, the Flux docs are (or at least should be) quite explicit that the CLI version and distribution installed need to match. You can have situations where from one version to the next, new CLI will not work with the CRDs from the prior version because of APIVersion mismatches.

we will have the same issue with the tenant cluster versions and compatibility between kubectl utility and tenants clusters...

Not exactly, kubectl supports a version skew policy of plus-or-minus one:
https://kubernetes.io/releases/version-skew-policy/#kubectl
So you are guaranteed that kubectl 1.29 works with kubelet + api server 1.30
There's no transitional skew guarantee like that for Flux. When you download your new Flux CLI, the next step is bootstrap upgrade and alert your colleagues that it's time to upgrade their CLIs.
The CRD backwards compatibility guarantees of Flux I can't explain in detail right now, but they are based on alpha/beta support guarantees from Kubernetes upstream. Eg. when an API is promoted from alpha to beta, it's considered production ready, and automatic upgrades are supported for one or more versions, until the deprecated API version can be removed.
All Flux APIs are currently beta or later, so those guarantees are in place.
An example where you can have trouble, Flux 2.3 CLI can't work with Flux 2.2 because some deprecated versions are finally removed after years.  On one hand this does not happen very often, (on the other hand it is long in advance predictable that it happens, it does happen, and it will probably happen again.)

Flux 2.3 CLI can't work with Flux 2.2 because some deprecated versions are finally removed after years.

it is totally not understandable, because kubectl works (!)


kubelet-wrapper needs to mount /var/log

The kubelet-wrapper needs to include /var/log among its mount points, since kubelet puts container logs in /var/log/containers. I've confirmed this by modifying kubelet-wrapper myself.

@aknuds1 check out #320
We are going to ship the logging components as cluster add-ons in the near future, at which point we will have the rkt kubelet host-mount it's container log files. Until then, just add an Environment entry for RKT_OPTS in kubelet.service, which defines the addtional mount flags for /var/log/container

OK, cool. Keep me posted. You should've mounted /var/log/containers from the get-go though, as it breaks kubelet.

@aknuds1 curious what breaks in the kubelet?

@aaronlevy As I state in the issue description, Kubelet isn't able to place logs in /var/log/containers, meaning that in turn fluentd can't collect container logs. So basically, the Kubernetes logging stack (Fluentd/Elasticsearch/Kibana) doesn't work as a result.

Right. Just wanted to make sure there wasn't some other breakage I was missing.
FWIW, the kubelet is still collecting the logs, but just inside the chroot of the kubelet container (not the host /var/log/containers). So the kubelet should function normally, but you're correct that external logging applications would not have access to this data.
As @chom mentioned, you can add this mount using Environment=RKT_OPTS= in the kubelet unit file.
The original intention was to keep the kubelet-wrapper script as a simple starting point, but we may need to add more to the defaults. I'll leave this issue open to track this feature request.

Hi guys.
How we can mount /var/log/containers to rkt via RKT_OPTS?
I try to add Environment=RKT_OPTS=--volume var-log-container,kind=host,source=/var/log/containers --mount volume=log,target=/var/log/containers to the kubelet unit but i have error in the log:
[/etc/systemd/system/kubelet.service:5] Invalid environment assignment, ignoring: RKT_OPTS=--volume var-log-container,kind=host,source=/var/log/containers    --mount volume=log,target=/var/log/containers
....
Mar 28 12:39:19 az1 kubelet-wrapper[3530]: Error: invalid argument "--stage1-path=/usr/share/rkt/stage1-fly.aci" for --volume: invalid value in --volume flag "--stage1-path=/usr/s

Also I tried env to EnviroumentFile but nothing changed

Can you try adding quotes:
Environment="RKT_OPTS=..."

Thank you for your reply.
We run kubelet without rkt due to an error https://github.com/coreos/coreos-kubernetes/issues/357
Now I can't check this but I will try after return to rkt.

The above workaround works for me. Here is the complete working line:
Environment="RKT_OPTS=--volume container,kind=host,source=/var/log/containers,readOnly=false --mount volume=container,target=/var/log/containers"

Though you can't use _ in volume name. rkt doesn't like it. And I have to manually create directory /var/log/containers and chmod 777 /var/log/containers. Otherwise, I got permission denied when starting kube-wrapper

For other folk, as @xcompass mentioned, you do need to create some directories, and additionally, no one's mentioned anything about the fluentd cursor file which gets stored in /var/log in the upstream kubernetes logging addon. Having the cursor files in the volume is particularly important because if fluentd restarts for any reason, the container file system containing the cursor files will go away. This means that upon starting back up, fluentd would re-ingest all log files it can find starting from the beginning again, leading to extra work, and duplicated log messages.
I'm including an example of something that should work with the upstream logging addon, however I'm not completely happy with this being the solution.
Modify your kubelet.service to include the following:
ExecStartPre=/usr/bin/mkdir -p /var/log/containers
Environment="RKT_OPTS=--volume var-log,kind=host,source=/var/log --mount volume=var-log,target=/var/log"

I'm not particularly fond of mounting in the entire /var/log directory into the container, but this container is already somewhat privileged and in upstream is run outside of a container entirely. It might be worth asking upstream to put position files in /var/log/container-position-files or something but this should work. I don't think you necessarily need any chmoding since it should be writable and readable by root, which system runs the rkt kubelet container as, and the kubelet itself runs as root.

Just to testify that I did as @chancez explained and that fixed my problem; I was having trouble getting cluster level logging to work properly.

@chancez thanks for the answer. Worker for me.
CoreOs 1010.3

@robszumski why this settings are not configured by default?

@AlmogBaku Good question, this is being addressed in https://github.com/coreos/coreos-kubernetes/issues/650. I agree with you that it should be

👍 to defaulting it.

This is broken, because /var/log/containers only contains symlinks to /var/lib/docker. I am using CoreOS CL 1235.9.0 with Kubernetes 1.5.2_coreos.2.


[CLOUD-429] Update vendored cookbooks

Update embedded enterprise cookbook to 0.11.0 to fix runsvdir with
Upstart

cc @chef/chef-server-maintainers


TypeError: 'NoneType' object is not subscriptable error during pytest

First of all I congratulate you on your awesome project. I am running Ubuntu 16.04 32 bit platform. I followed the instructions in readme page, but I got the below errors.
  uname -a ; python --version; pip show universe gym tensorflow numpy go-vncdriver Pillow
Linux kenn 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 i686 i686 i686 GNU/Linux
Python 2.7.12
Name: universe
Version: 0.21.5
Summary: Universe: a software platform for measuring and training an AI's general intelligence across the world's supply of games, websites and other applications.
Home-page: https://github.com/openai/universe
Author: OpenAI
Author-email<EMAIL_ADDRESS>License: UNKNOWN
Location: /home/trabzonspor/CODING-RELOADED/universe
Requires: autobahn, docker-py, docker-pycreds, fastzbarlight, go-vncdriver, gym, Pillow, PyYAML, six, twisted, ujson
---
Name: gym
Version: 0.9.3
Summary: The OpenAI Gym: A toolkit for developing and comparing your reinforcement learning agents.
Home-page: https://github.com/openai/gym
Author: OpenAI
Author-email<EMAIL_ADDRESS>License: UNKNOWN
Location: /usr/local/lib/python3.5/dist-packages
Requires: six, numpy, pyglet, requests
---
Name: numpy
Version: 1.13.1
Summary: NumPy: array processing for numbers, strings, records, and objects.
Home-page: http://www.numpy.org
Author: NumPy Developers
Author-email<EMAIL_ADDRESS>License: BSD
Location: /usr/local/lib/python3.5/dist-packages
Requires:
---
Name: go-vncdriver
Version: 0.4.19
Summary: UNKNOWN
Home-page: UNKNOWN
Author: UNKNOWN
Author-email: UNKNOWN
License: UNKNOWN
Location: /usr/local/lib/python3.5/dist-packages
Requires: numpy
---
Name: Pillow
Version: 4.2.1
Summary: Python Imaging Library (Fork)
Home-page: https://python-pillow.org
Author: Alex Clark (Fork Author)
Author-email<EMAIL_ADDRESS>License: Standard PIL License
Location: /usr/local/lib/python3.5/dist-packages
Requires: olefile

$ docker run --privileged --rm -e DOCKER_NET_HOST=<IP_ADDRESS> -v /var/run/docker.sock:/var/run/docker.sock universe pytest
==================== 6 failed, 16 passed in 110.71 seconds =====================
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/gym/utils/closer.py", line 67, in close
    closeable.close()
  File "/usr/local/lib/python3.5/dist-packages/gym/core.py", line 164, in close
    self.render(close=True)
  File "/usr/local/lib/python3.5/dist-packages/gym/core.py", line 150, in render
    return self._render(mode=mode, close=close)
  File "/usr/local/universe/universe/vectorized/multiprocessing_env.py", line 310, in _render
    return render_n(self.worker_n, mode=mode, close=close)
  File "/usr/local/universe/universe/vectorized/multiprocessing_env.py", line 230, in render_n
    worker_n = worker_n[0:]
TypeError: 'NoneType' object is not subscriptable
Exception ignored in: <bound method Env.__del__ of <universe.vectorized.multiprocessing_env.MultiprocessingEnv object at 0x82029bec>>
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/gym/core.py", line 203, in __del__
    self.close()
  File "/usr/local/lib/python3.5/dist-packages/gym/core.py", line 164, in close
    self.render(close=True)
  File "/usr/local/lib/python3.5/dist-packages/gym/core.py", line 150, in render
    return self._render(mode=mode, close=close)
  File "/usr/local/universe/universe/vectorized/multiprocessing_env.py", line 310, in _render
    return render_n(self.worker_n, mode=mode, close=close)
  File "/usr/local/universe/universe/vectorized/multiprocessing_env.py", line 230, in render_n
    worker_n = worker_n[0:]
TypeError: 'NoneType' object is not subscriptable

Any help please.
Regards.
Kenn

same error here,  I read that other got it too.  At first sight it seems worker_n[0:] is nonetype.  it is in close() function, so why not try   if nonetype skip the line that make the error, or assign to 0


Considered this as a native plugin feature in Webpack

Is there a reason you haven't submitted this parallel file loading as a feature or plugin into webpack? @sokra @jhnns and I were talking about way to have faster webpack builds and this has the potential with a bit of cleanup. Have you considered submitting this plugin for a PR. We are also looking into a strategy that caches the dependency AST as loaders run and persisting them for chained loaders tied to it etc.

To be honest, I don't know where the performance improvements of happypack come from. Webpack already invokes loaders in parallel. And when a loader sets the cacheable() flag (which all popular loaders do), webpack cache's the loader's output as well.
However, I really appreciate this effort and I think every performance improvement should be merged into core.

I did mention it around the time HappyPack was made public in https://github.com/webpack/webpack/issues/1810 but it never really garnered much interest so I didn't push it.
What would the benefits be if we choose to push this to core and not use a plugin?
My concern with trying to add this to core is that, with webpack's current design, we will never have full support for all loader APIs since not everything can be shared cross processes. In particular, I'm talking about hooking into compilation and compiler instance states from loaders. Since this is currently a plugin, it's ok for us to say "well, this won't work if your loaders use X or Y" but it's a different story if webpack itself tries to provide this functionality - then it is bereft of that freedom.
@jhnns IIRC webpack uses async to apply loaders in parallel but that's still bound to the same node process (and the same event loop) which isn't the same as launching multiple processes which is what HappyPack does. Does that make sense?

What would the benefits be if we choose to push this to core and not use a plugin?

Everyone should benefit from performance improvements 😁

My concern with trying to add this to core is that, with webpack's current design, we will never have full support for all loader APIs since not everything can be shared cross processes. In particular, I'm talking about hooking into compilation and compiler instance states from loaders. Since this is currently a plugin, it's ok for us to say "well, this won't work if your loaders use X or Y" but it's a different story if webpack itself tries to provide this functionality - then it is bereft of that freedom.

That might be a problem. However, a loader has no official access to the compilation by design and I don't know any popular loader that does this. So this should be no problem. We could also add a getter to the _compilation and _compiler property to warn the user that a loader is trying to access them.

webpack uses async to apply loaders in parallel but that's still bound to the same node process (and the same event loop) which isn't the same as launching multiple processes which is what HappyPack does. Does that make sense?

Not really. Node's concept is based on the assumption that a single process with an event loop handles IO more efficiently than multiple processes. As long as you're not doing synchronous stuff (which means that the process is waiting for a single result without doing anything else) I would expect a single process to be at least as fast as multiple processes.

Edit: also, re the cacheable() flag, that is still bound to the process, it won't persist on subsequent runs (which is OK since it's meant to make incremental builds faster, but happypack caches to disk which takes things one step further.)

This increases the initial build time indeed. But what if you've updated a loader or plugin in the meantime? Do you track dependencies as well? We already had a long discussion about this and we haven't found a good way yet.
I'll try HappyPack in my projects to check if there is a performance improvement and maybe to find out, where the improvement is coming from. Thanks for your hard work! 👍

That might be a problem. However, a loader has no official access to the compilation by design and I don't know any popular loader that does this. So this should be no problem. We could also add a getter to the _compilation and _compiler property to warn the user that a loader is trying to access them.

Hacky access still gave people access so they use it :grin: - the typescript loaders all seem to rely on compilation and compiler hooks which is making it hard to support them in this architecture.
But all in all, I think webpack would benefit from the modularity if we can isolate the application of loaders from the core process (like what's happening here) if for anything but the separation of concerns. I also wish that we converge on a single loader application implementation, because right now happypack tries to re-do what webpack already does (see https://github.com/amireh/happypack/blob/master/lib/applyLoaders.js) in terms of how it applies the loaders. (If I'm not mistaken, I saw that sokra was making a library for this which may end up being used in webpack but it was still tied to webpack internals and made some assumptions that makes it inapplicable on a distributed architecture..)

Not really. Node's concept is based on the assumption that a single process with an event loop handles IO more efficiently than multiple processes. As long as you're not doing synchronous stuff (which means that the process is waiting for a single result without doing anything else) I would expect a single process to be at least as fast as multiple processes.

I believe that's really it. In our own use case, babel transformations were taking most of the time and those (presumably) are synchronous. This seems to also be the case for any loader that performs some form of AST analysis which tend to be slow (cpu and not IO-bound).

But what if you've updated a loader or plugin in the meantime? Do you track dependencies as well?

I didn't try to solve that, instead, I just made it easy to nuke the entire cache when you know it's gone bad (just do an rm -r .happypack) and then you can also specify some variables that constitute a cache "context", which if changes between builds, the cache will considered to be invalid (useful for environment variables and such). It is silly and perhaps a little irresponsible, I know! But it works for most use cases and reaps some nice benefits when it does work so :smile:
It's funny reading through that thread you linked, because at some point in the past I had my own take at making a serializable cache for webpack, which did work to some extent, but then I found the (de)hydration costs to be too high to make it feasible. I was probably caching some unnecessary information. However, it's cool to see that others have been working on this, I hope it is solved one day!
Thanks for the work on webpack.. it's one beast of a software! xD

Hacky access still gave people access so they use it 😁 - the typescript loaders all seem to rely on compilation and compiler hooks which is making it hard to support them in this architecture.

Yeah, I wish sokra had not added it... . Didn't know about the typescript-loader, though.

But all in all, I think webpack would benefit from the modularity if we can isolate the application of loaders from the core process (like what's happening here) if for anything but the separation of concerns

Definitely.

I believe that's really it. In our own use case, babel transformations were taking most of the time and those (presumably) are synchronous. This seems to also be the case for any loader that performs some form of AST analysis which tend to be slow (cpu and not IO-bound).

Yeah, I think multi-core CPUs are important here because then you can lift the heavy JS work on multiple cores. Maybe that's the cause. In this case, however, you cannot benefit from cached FS access. But I don't know, maybe the OS FS cache is sufficient here.

I didn't try to solve that, instead, I just made it easy to nuke the entire cache when you know it's gone bad

That's ok, but I think it should be opt-in. When you don't know about caching, this can bite you.

That's ok, but I think it should be opt-in. When you don't know about caching, this can bite you.

It is on by default, although you can totally disable the cache if you want. We can probably make it a bit more sophisticated to catch some common scenarios (like updating node modules) or just have the documentation state this and leave it up to the user like it is now. In practice, the caching bit is not the main gain from happypack, and it would still be a big improvement to use it with caching disabled altogether.
Anyway, let us know when you try it out and how you think we should proceed. I'd be happy to help.

+1, would love to see this as a native component in webpack. It's almost mandatory for large project, and much easier to setup than DLLs.

I think finding a creative API for execution is a strong interest to me.

Trying to tidy things up around here so I'll be closing this, thanks all! :) (FWIW caching has been removed as of v4, this is now only concerned with parallelism)


Update javascript.md

@jemmycodes please fix the sorting in alphabetical order: Created a section for E and move Eloquent Javascript... up to that section:
Example:
### E
- [Eloquent Jav...](link)

do the same for each addition
💪🏾

Yes please, that would be nice @jemmycodes

@jemmycodes are those google drive links public? Please ensure anyone can access them. Thanks

@jemmycodes are those google drive links public? Please ensure anyone can access them. Thanks

sure! i've given anyone with the link access to the books


Add min/max with default keyword (added in Python 3.4)

Closes #315

@benjaminp not sure why Python 3.3 is failing. Looks like it has nothing to do with my change. Can you check this PR?

Closing out since i don't see a path to merge.


Remove library option in prototype

Hey team! Please add your planning poker estimate with ZenHub @isabellamoak @vstevens14


Suggestion

I was asked if I could put the cmd window or processes running BCUninstaller in hidden or minimized, when uninstall.
Only if you can.
Take it as a suggestion, so that it looks better.

Do you mean the uninstall windows? I already have plans to hide at least some of them, but it's difficult so it's taking a while.

Only if you can put it in hidden mode. But still working as usual.
Just a suggestion, do not take it as something mandatory.

This is exactly what #88 is about. It's a temporary interface useful for debugging that I was too lazy to change :)

Ok, thanks for your attention, very good software.


Bug: Multiselect doesn't work with open items with single click on

Description
With the commit #11017 for improved multiselect it still doesn't work with single click mode on. As it will just select the File/Folder and double clicking will trigger the go up directory function.
Steps To Reproduce

Enable the option in Files settings > Folders > Open items > Open items with single click.
Enable the option in Files settings > Folders > Show selection checkbox next to files name.
Try open a folder/file.

Steps to fix

Make click region for multiselect on the check box only.

Files Version
Dev build on commit 985d66e
Windows Version
10.0.22621.1105
Relevant Assets/Logs
debug.log

How does it work in File Explorer?

Single click mode in file explorer will select the file then clicking again opens it. Otherwise you have to select the checkbox.


vcpkg packages build failure with Visual Studio 2022 + MSVC v142

Host Environment

OS: Windows 10 21H1
Compiler: MSVC v142
Visual Studio 2022 preview 2.1

To Reproduce
Steps to reproduce the behavior:
./vcpkg install glfw3
Failure logs
.\vcpkg.exe install glfw3
Computing installation plan...
The following packages will be built and installed:
glfw3[core]:x86-windows -> 3.3.4
No suitable Visual Studio instances were found

Fixed by installing MSVC v142 v14.29 instead of latest


Sentry.replayIntegration is not a function

Environment
What version are you running? Etc.
"@capacitor/android": "^6.1.0",
"@capacitor/cli": "^6.1.0",
"@capacitor/core": "^6.1.0",
"@capacitor/ios": "^6.1.0",
"@sentry/capacitor": "^0.18.0",
"@sentry/vue": "^7.114.0",
"vue": "^3.4.29"

Steps to Reproduce
Set up a Vue application and then add capacitor to it. The main.js looks like this:
import './assets/main.css'
import { createApp } from 'vue'
import App from './App.vue'
import * as Sentry from "@sentry/capacitor";
import * as SentryVue from "@sentry/vue";

Sentry.init(
    {
        dsn: "DSN HERE",

        // Set your release version, such as<EMAIL_ADDRESS>        release: "my-project-name@<release-name>",
        // Set your dist version, such as "1"
        dist: "<dist>",
        integrations: [
            // Registers and configures the Tracing integration,
            // which automatically instruments your application to monitor its
            // performance, including custom Angular routing instrumentation
            SentryVue.browserTracingIntegration(),
            // Registers the Replay integration,
            // which automatically captures Session Replays
            Sentry.replayIntegration(),
        ],

        // Set tracesSampleRate to 1.0 to capture 100%
        // of transactions for tracing.
        // We recommend adjusting this value in production
        tracesSampleRate: 1.0,

        // Set `tracePropagationTargets` to control for which URLs distributed tracing should be enabled
        tracePropagationTargets: ["localhost", /^https:\/\/yourserver\.io\/api/],

        // Capture Replay for 10% of all sessions,
        // plus for 100% of sessions with an error
        replaysSessionSampleRate: 1.0,
        replaysOnErrorSampleRate: 1.0,
    },
    // Forward the init method from @sentry/angular
    SentryVue.init
);

createApp(App).mount('#app')

Then just run the app. I ran it in development.
Expected Result
The app runs normally.
Actual Result
We get the following error in the browser console:

If we change Sentry.replayIntegration(), to SentryVue.replayIntegration(),, the error goes away and the application works normally.
However, the Sentry docs indicate that we should be able to use Sentry.replayIntegration(), here.

Hi and sorry for the confusion,   the docs are pointing to the documentation for the next release :(
For this version, you need to initialize the following Integrations as shown on the below snippet
import './assets/main.css'
import { createApp } from 'vue'
import App from './App.vue'
import * as Sentry from "@sentry/capacitor";
import * as SentryVue from "@sentry/vue";

Sentry.init(
    {
        dsn: "DSN HERE",

        // Set your release version, such as<EMAIL_ADDRESS>        release: "my-project-name@<release-name>",
        // Set your dist version, such as "1"
        dist: "<dist>",
        integrations: [
            // Registers and configures the Tracing integration,
            // which automatically instruments your application to monitor its
            // performance, including custom Angular routing instrumentation
            new SentryVue.BrowserTracing(),
            // Registers the Replay integration,
            // which automatically captures Session Replays
            new SentryVue.Replay(),
        ],

        // Set tracesSampleRate to 1.0 to capture 100%
        // of transactions for tracing.
        // We recommend adjusting this value in production
        tracesSampleRate: 1.0,

        // Set `tracePropagationTargets` to control for which URLs distributed tracing should be enabled
        tracePropagationTargets: ["localhost", /^https:\/\/yourserver\.io\/api/],

        // Capture Replay for 10% of all sessions,
        // plus for 100% of sessions with an error
        replaysSessionSampleRate: 1.0,
        replaysOnErrorSampleRate: 1.0,
    },
    // Forward the init method from @sentry/angular
    SentryVue.init
);

createApp(App).mount('#app')

Hi, I'm trying to get kind of the same configuration running but with @sentry/vue=^8.14.0 but unfortunately my IDE complains about the integrations.
This is my setup:
import { createApp } from 'vue'
import App from './App.vue'
import router from '@/router';
import * as Sentry from "@sentry/capacitor";
import * as SentryVue from "@sentry/vue";

const vueApp = createApp(App)

Sentry.init(
    {
        app: vueApp,
        dsn: import.meta.env.VITE_SENTRY_DSN,
        release: "my-project-name@<release-name>",
        dist: import.meta.env.VITE_SENTRY_DIST,,
        integrations: [
           SentryVue.browserTracing({ router }),
           SentryVue.replay(),
        ],
    },
    SentryVue.init
);

vueApp.mount('#app')

But with this I get the error:
Type '(Integration | Replay)[]' is not assignable to type '((Integration[] | ((integrations: Integration[]) => Integration[])) & (Integration[] | ((integrations: Integration[]) => Integration[]))) | undefined'.
  Type '(Integration | Replay)[]' is not assignable to type '((integrations: Integration[]) => Integration[]) & Integration[]'.
    Type '(Integration | Replay)[]' is not assignable to type '(integrations: Integration[]) => Integration[]'.
      Type '(Integration | Replay)[]' provides no match for the signature '(integrations: Integration[]): Integration[]'.ts(2322)
options.d.ts(274, 5): The expected type comes from property 'integrations' which is declared here on type 'CapacitorOptions & Partial<Omit<Options, "tracingOptions"> & { tracingOptions: Partial<TracingOptions>; }>'

Hi, I'm trying to get kind of the same configuration running but with capacitor v6 and @sentry/capacitor": "^0.18.0 but with @sentry/vue=^8.14.0, but unfortunately my IDE complains about the integrations.
This is my setup:
import { createApp } from 'vue'
import App from './App.vue'
import router from '@/router';
import * as Sentry from "@sentry/capacitor";
import * as SentryVue from "@sentry/vue";

const vueApp = createApp(App)

Sentry.init(
    {
        app: vueApp,
        dsn: import.meta.env.VITE_SENTRY_DSN,
        release: "my-project-name@<release-name>",
        dist: import.meta.env.VITE_SENTRY_DIST,,
        integrations: [
           SentryVue.browserTracing({ router }),
           SentryVue.replay(),
        ],
    },
    SentryVue.init
);

vueApp.mount('#app')

But with this I get the error in the IDE:
Type '(Integration | Replay)[]' is not assignable to type '((Integration[] | ((integrations: Integration[]) => Integration[])) & (Integration[] | ((integrations: Integration[]) => Integration[]))) | undefined'.
  Type '(Integration | Replay)[]' is not assignable to type '((integrations: Integration[]) => Integration[]) & Integration[]'.
    Type '(Integration | Replay)[]' is not assignable to type '(integrations: Integration[]) => Integration[]'.
      Type '(Integration | Replay)[]' provides no match for the signature '(integrations: Integration[]): Integration[]'.ts(2322)
options.d.ts(274, 5): The expected type comes from property 'integrations' which is declared here on type 'CapacitorOptions & Partial<Omit<Options, "tracingOptions"> & { tracingOptions: Partial<TracingOptions>; }>'

and this error if I run it:
TypeError: addGlobalEventProcessor2 is not a function
    at _SdkInfo.setupOnce (@sentry_capacitor.js?v=3e1dce11:25303:5)
    at setupIntegration (@sentry_vue.js?v=3e1dce11:4884:17)
    at @sentry_vue.js?v=3e1dce11:4865:7
    at Array.forEach (<anonymous>)
    at setupIntegrations (@sentry_vue.js?v=3e1dce11:4863:16)
    at BrowserClient._setupIntegrations (@sentry_vue.js?v=3e1dce11:5167:26)
    at BrowserClient.init (@sentry_vue.js?v=3e1dce11:5079:12)
    at initAndBind (@sentry_vue.js?v=3e1dce11:5481:10)
    at init (@sentry_vue.js?v=3e1dce11:13691:18)
    at init2 (@sentry_vue.js?v=3e1dce11:29587:10)
    at Module.init2 (@sentry_capacitor.js?v=3e1dce11:25583:3)

Hi, for the time being Sentry Capacitor is only compatible with Sentry vue V7, so I would recommend for now to use @sentry/vue on version 7.114.0

Hi, thanks for the hint. It's working with v7 even though it's not very intuitive with the use of those deprecated functions. :-)
One error that remains is that the use of SentryVue.init somehow leads to the error Expected 0-1 arguments, but got 2 (in VScode) but the project nevertheless starts without any complains.
This repo is a minimal reproduction of this case.

One error that remains is that the use of SentryVue.init somehow leads to the error Expected 0-1 arguments, but got 2 (in VScode) but the project nevertheless starts without any complains.
This repo is a minimal reproduction of this case.
I just saw this is related to a false import which was my bad. :-)


Output transform int8 output procedure

I have implemented a bconv2d with int8 output for the xcore. When doing so I had to implement the output transform:
https://github.com/larq/compute-engine/blob/e0683a7cb2ce1c2e15f6c59bb140f7d6f8da6a9b/larq_compute_engine/core/bconv2d/output_transform.h#L136
My questions are:

what is the shift left for? is there a reason not to absorb it into the multiplication?
why clamp after the initial shift left(before the multiplication)?
is there ever a case where both of these operations cannot be absorbed into the linear transformation given that there is going to be final clamp? i.e. could you ever want an activation with two clamped sections

Thanks

Ah yes this is kind of ugly.

what is the shift left for? is there a reason not to absorb it into the multiplication?
why clamp after the initial shift left(before the multiplication)?

The left shift is essentially part of the back transformation, which converts the accumulator value to the actual output value. The back transformation has the form filter_height * filter_width * input_channels - 2 * accum, so a multiplication by (minus) 2 and a constant offset. Conceptually, after the back-transformation we then do clamping for the activation function, and then do the batch-norm linear transformation. In #490, we 'fused' the back-transformation constant offset into the linear transformation at the end, by 'pushing it through' the clamping. However, we can't 'push through' the multiplication by two because it risks introducing error.
E.g. if filter_height = filter_width = 3 and input_channels = 1, then this represents a binary convolution with a min/max output value of -9 / +9. Importantly, each output value (prior to the fused activation/linear transformation) will always be an odd number, because it's a sum of an odd number of +1/-1 values. However, if there is a fused ReLU, we clamp these outputs to [0, 9]. If we perform clamping before doing the left shift, then this forces the effective clamped range to be a multiple of two, so the best we can do is clamp to [-1, 9] or [1, 9]. The same issue can arise if the back-transformation constant offset is even and we want to clamp to an odd value.
So, in essence, we do back-transformation-left-shift → clamp → linear-transformation-fused-with-backtransformation-offset because it's slightly more efficient than back-transformation-shift-and-offset → clamp → linear-transformation.

is there ever a case where both of these operations cannot be absorbed into the linear transformation given that there is going to be final clamp? i.e. could you ever want an activation with two clamped sections

In the case of an int8 output transformation, you could indeed do a single clamp right at the end, without the clamping in the middle. In that scenario, you could then fuse the left-shift into the linear transformation. However, the clamping at the end would then (I'm pretty sure) have to be channel-wise, because after 'pushing through' the per-channel linear transformation you would end up with a per-channel clamp.

Thank you for your quick response.  Am I correct in assuming that clamp_max and clamp_min are defined in the same space as the input i.e. a = sum(w * x) as opposed to the xor_popcount space? If this is correct then odd clamp values are essentially unused as the result of the product of the weights and the data can only be even values. This would mean that dividing the clamp_max and clamp_min that are used in implementation would be safe as this is in xor_popcount space.

On the tensorflow side, the inputs and weights are all in {-1.0 , +1.0}. When n = filter_height * filter_width * input_channels is even, then the result of this "-1,+1 innerproduct" will be always even. When that value n is odd, the innerproduct will always be odd.
In the actual implementation, we have a "0,1 innerproduct" and then use n - 2 * popcount to go back from "0,1 space" to "-1,1 space".
However that n has been fused into the other linear transform after the clamp but the 2 has not.
With those definitions in place I can answer your question:

Am I correct in assuming that clamp_max and clamp_min are defined in the same space as the input i.e. a = sum(w * x) as opposed to the xor_popcount space?

The clamp_min and clamp_max values in the OutputTransform are inbetween the "0,1" space and the "-1,1" space, as they are after the multiplication by 2 but before the n - ..

If this is correct then odd clamp values are essentially unused as the result of the product of the weights and the data can only be even values.

The activation function (e.g. ReLu) is applied in "-1,1 space". It therefore defines clamp values in "-1,1 space" which can then be converted to however the implementation likes it.
The activation function "Relu1" will have odd clamp values in "-1,1 space", but will probably never be used in binary convolutions.
The most common activation functions, "None" and "Relu", will only have 0 as clamp value in "-1,1 space".
That means when n is even, this will nicely translate to a clamp value on the popcount.
But when n is odd then it will not: n-2*popcount == 0 means popcount == n/2.
I would say that you can safely assume that the number of input channels in any realistic network is always even (you can probably assume its always a multiple of 32) so it'd be fine to make this assumption in your kernels and only support that case.


WIP: Initial implementation in progress

You should use MONAI instead of PyTorch.
S

Sent via phone.

aylward> You should use MONAI instead of PyTorch.
One purpose of this module is to supply PyTorchImage as a C++ template available for those using ITK in C++.  I am implementing the PyTorchImage template using the libtorch C++ interface.

It is intended that this module will integrate with MONAI.  If there are MONAI C++ bindings that I should be aware of, please let me know.  Or, if the approach of a creating a PyTorchImage< TPixelType, VNumberOfDimensions > template that publicly inherits from  the Image<TPixelType, VNumberOfDimensions > template is going to create incompatibilities with MONAI, please let me know.

@aylward thanks for sharing the awesome thoughts! Good integration with MONAI is certainly a priority, and the best way to do that will be informed and evolve according to suggestions from experts like yourself and @hjmjohnson 's suggestions.
I created this issue to track and collect ideas related to Jupyter notebooks and MONAI: https://github.com/InsightSoftwareConsortium/ITKPyTorch/issues/2

I do think this is a great direction to head!  Sorry if my suggestions are
off mark, but my limited understanding of this work suggests that perhaps
two specific considerations regarding MONAI:

You and others created some nice python helper functions for ITK (e.g.,
ITKExtras.py) that help with using ITK from numpy, accessing spacing
information, etc.   I wonder if something similar should be done in this
module for MONAI.
MONAI is using python dictionaries for managing spacing etc.   Seems
like those dictionaries could be created and populated by this toolkit as
well.  Yes, MONAI doesn't provide a custom C++ library for those
dictionaries, but does it need to in order to access them from C++?

Again, perhaps I am way off base, and I will drop it for now.  However, if
this helps with the proper handling of medical images by pytorch/monai,
then perhaps these additional investigations are worth it.
On Mon, Jul 20, 2020 at 10:05 AM Matt McCormick<EMAIL_ADDRESS>wrote:

@aylward https://github.com/aylward thanks for sharing the awesome
thoughts! Good integration with MONAI is certainly a priority, and the best
way to do that will be informed and evolve according to suggestions from
experts like yourself and @hjmjohnson https://github.com/hjmjohnson 's
suggestions.
I created this issue to track and collect ideas related to Jupyter
notebooks and MONAI: #2
https://github.com/InsightSoftwareConsortium/ITKPyTorch/issues/2
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/InsightSoftwareConsortium/ITKPyTorch/pull/1#issuecomment-661060851,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACEJL4GEN7CJVVLCMI76QDR4RFKBANCNFSM4O436SZQ
.

--
Stephen R. Aylward, Ph.D.
Senior Director of Strategic Initiatives
Kitware: Advancing the frontiers of understanding
by developing innovative open-source software platforms
and integrating them into research, processes, and products.

@aylward definitely! Tracked in https://github.com/InsightSoftwareConsortium/ITKPyTorch/issues/3

@Leengit looking good.
While ITKPyTorch and PyTorch are good names for the module, I think the class names should have a Torch instead of PyTorch prefix. This will result in shorter names more consistent with the API in PyTorch itself, i.e. torch in the Python filter names.

Done.


Research: Increase calldata limit on eth_estimateGas

Problem
There are some cases where calling eth_estimateGas with calldata more than 24KB fails in the archive node. This is due to limitation, which is far larger in the etereum world. Becase of this reason, in some scenarios call is failing.
User Stories

As a user, I'd like to be able to deploy a factory contract, which accepts init bytocode for another contract as parameter. This fails, if the bytecode is larger than 24KB

@isavov we bumped to 25kb https://github.com/hashgraph/hedera-mirror-node/pull/7795, do you know if this issue is resolved or does the scenario require a higher limit.
If so what size in kb?


Allow agents to register for available percepts

In #28, we implemented a mechanism to allow agents to receive BLOCKED percepts outside of BDI actions. This should be extended to allow agents to register for any available percept, including CONGESTION.

Available since cf55531 athough there is no dedicated test for it yet. /cc @chambul


phpipam_first_free_subnet: Error: Subnet either missing or multiple results returned by reading subnet after creation

Hi,
we are using the latest version of the provider (1.3.6) and are facing a similiar issue as described here #43
In our case it happens for the resource phpipam_first_free_subnet
The error is the same:
Error: Subnet either missing or multiple results returned by reading subnet after creation
We are using PHPIPam to manage secondary IP Ranges for Google Kubernetes Engine clusters.
Each environment is a separate section in PHPIPAM and each one contains the same Parent Subnet Range, where we can dynamically allocate new subnets from.
From a technical perspective its desired to re-use the same IP Ranges in different stages, hence the separate sections.
The creation of the next free subnet seems to work, as i can see it in PHPIPAM, however as with #43 the answer back with the result contains all subnets across all sections that have the very same range.
I tried to provide the section_id parameter to the resource, but that returns the error:
Error: "section_id": this field cannot be set
Happy to provide more details if required.

I looked into it myself and from my point of view a very easy fix is to add the section_id parameter to the phpipam_first_free_subnet resource.
This is in-line with the phpipam_subnet resource, which also has that parameter set as required.
The fix for creating the same subnet in different section that was added as part of #43 then also works for the phpipam_first_free_subnet resource.


Bot prefix causes errors if set to <

If the bot prefix is set to <, it interprets users being mentioned (when at the beginning of the message) as commands to be executed, which yields the obvious Command Not Found error.

As discussed in discord this isnt actually a bug with clembot but more just a result of how discord internally represents mentions, we should just disallow this prefix entirely to prevent it

As discussed in discord this isnt actually a bug with clembot but more just a result of how discord internally represents mentions, we should just disallow this prefix entirely to prevent it

Completed via #871


Fixes invalid values for 'port' in AddServerPopup

This fix applies .trim() to the text to ignore trailing whitespaces.
The 'port' value in the AddServerPopup can end up invalid due to
whitespaces, such as newline characters (\n). This will disable the OK button and the user cannot add a new server.

I'm wondering whether there is a more complex bug in the background that the text in the text widget can end up having newline characters which cannot be deleted...
@Cervator did you encounter anything like that before?

Thanks @skaldarnar! Since @jdrueckert has kindly confirmed that the changes fix the issue, I'll go ahead and merge.


only run crypt keys if we have a conv for user changed handler CORE-4439

Use the local copy of the inbox to check to see if the user we encounter in chat's user changed handler is involved in any conversations we have.

👍, no need to clear the DB cache as per our discussion, since it's not used to cache failures, and that's the case you need a cache bust.
But I do think it makes sense to not reidentify if triggered from the identify loop

@maxtaco PTAL

Sure
On Fri, Jan 20, 2017 at 3:09 PM, Maxwell Krohn<EMAIL_ADDRESS>wrote:

@maxtaco commented on this pull request.
In go/chat/identify.go
https://github.com/keybase/client/pull/5486#pullrequestreview-17754820:

  }

}
h.Debug(ctx, "no conversation found for update for uid: %s", uid)

return "", errNoConvForUser

return "", nil, errNoConvForUser
+}

+func (h *IdentifyChangedHandler) BackgroundIdentifyChanged(job engine.IdentifyJob) {

notifier := NewIdentifyNotifier(h.G())
ctx := context.Background()

can you pass this in from the BGIDentifier?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/pull/5486#pullrequestreview-17754820,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMUCsNTN5eBMvcVf-Oe0uB4nfmthydUks5rURRrgaJpZM4Loro_
.

The whole thing is only for testing, its in sender_test.go
On Fri, Jan 20, 2017 at 3:15 PM, Maxwell Krohn<EMAIL_ADDRESS>wrote:

@maxtaco commented on this pull request.
In go/chat/identify_test.go
https://github.com/keybase/client/pull/5486#pullrequestreview-17756219:

})

t.Logf("new error job in inbox")
job := engine.NewIdentifyJob(u.User.GetUID(), errors.New("AHHHHHHH"), nil)
go func() { handler.BackgroundIdentifyChanged(job) }()
select {
case update := <-listener.identifyUpdate:

require.Equal(t, update.CanonicalName.String(), tlfName, "wrong tlf name")

require.NotZero(t, len(update.Breaks.Breaks), "no breaks")

case <-time.After(20 * time.Second):

require.Fail(t, "no identify update received")

}

t.Logf("new error job not in inbox")
job = engine.NewIdentifyJob(u1.User.GetUID(), errors.New("AHHHHHHH"), nil)
handler.BackgroundIdentifyChanged(job)

doesn't this need to be in a goroutine?
In go/chat/identify_test.go
https://github.com/keybase/client/pull/5486#pullrequestreview-17756219:

}

conv := chat1.Conversation{

Metadata: chat1.ConversationMetadata{

	ActiveList: []gregor1.UID{u.User.GetUID().ToBytes()},

},

MaxMsgs: []chat1.MessageBoxed{msg},

}
require.NoError(t, inbox.Merge(context.TODO(), 1, []chat1.Conversation{conv}, nil, nil))

handler := NewIdentifyChangedHandler(tc.G, func() keybase1.TlfInterface {

return kbtest.NewTlfMock(world)

})

t.Logf("new error job in inbox")
job := engine.NewIdentifyJob(u.User.GetUID(), errors.New("AHHHHHHH"), nil)
go func() { handler.BackgroundIdentifyChanged(job) }()

go handler.BackgroundIdentifyChanged(job); can do the job
In go/chat/sender_test.go
https://github.com/keybase/client/pull/5486#pullrequestreview-17756219:

"github.com/stretchr/testify/require"

"golang.org/x/net/context"
)
type chatListener struct {
sync.Mutex

obids    []chat1.OutboxID
incoming chan int
failing  chan []chat1.OutboxID

obids          []chat1.OutboxID
incoming       chan int
failing        chan []chat1.OutboxID
identifyUpdate chan keybase1.CanonicalTLFNameAndIDWithBreaks

is this only for testing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/pull/5486#pullrequestreview-17756219,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMUCsg5RMYKlje8iJWUXryDlXblBIk7ks5rURX8gaJpZM4Loro_
.


Deprecate and reduce instrumenter usage internally

Unclear currently how this is going to work in a backwards compat way

@sl0thentr0py, I think it is okay for us to drop instrumenter without deprecating it first and without making the change backwards compatible, since we already document instrumenter as being "for internal use only."
Ideally, we would remove the instrumenter in the Phase 1 major release; however, I would argue that since instrumenter is explicitly mentioned as being for internal use, we can safely remove it even in a minor version.

We cannot remove the top level option though if someone is setting it in their init since that's breaking. We can remove all internal references but the init options has to be deprecated and stay till the major.
That being said, we will probably do a major anyway so let's see.

Fair enough @sl0thentr0py. Although, I would imagine that few, if any, users set a custom instrumenter in their init, since we don't seem to document this functionality anywhere, as far as I can tell (e.g., instrumenter is missing from this page).
Worst case, I think we can get away with emitting a DeprecationWarning when instrumenter is set and otherwise ignoring the parameter's value (perhaps technically breaking, but it at least won't break people's apps).

it is required while using our span processor so far and is documented here
https://docs.sentry.io/platforms/python/tracing/instrumentation/opentelemetry/#usage
side note: while searching for docs usages, it is better as a dev to grep for a keyword in the docs repo rather than looking through the website to find something

We have decided to split this task as follows:

Clarifying that instrumenter parameters (except to init) are internal-only (#3299)
Fully deprecating instrumenter option (https://github.com/getsentry/sentry-python/pull/3308), to be merged in last 2.x version
Removing the instrumenter option in the POTel base branch

Closing in favor of #3320 and #3321.


scroll to top automatically on each page transition

For most mean applications, scrolling to top on each page transition should look natural.
This change would save time of many developers (like me.)
How do you guys think?

I don't think this solution would be good enough.  Something like this is a guarantee.  https://github.com/meanjs/mean/pull/639/files#diff-dea85680b1eef2a8f98fdf282b8158e5R9

@rhutchison So is this issue addressed in #639?


Add industry as a dimension

There have been some requests to add INDUSTRY as one of the dimensions (columns).
If so, does anyone have a recommended list of industries to categorize by?

@nicjansma I would like this contribute to this, it is a fantastic idea.


Volume compatibility with SELinux-enabled systems

Make use of volume tags to avoid problems with SELinux. Not setting these tags results in permission errors when trying to access the volumes within the running container.
https://docs.docker.com/engine/tutorials/dockervolumes/#/volume-labels

Thank you!


Delete mutations not working properly

Bug description
I have a Prisma, GraphQL-Nexus, Apollo, and React app that does not execute delete mutations properly.
There's a couple weird things happening:
1.) If I go to the frontend of the app and click on the delete button twice then refresh the page, the record gets deleted from the database. But If I click It once, then refresh, It's still there in the database. Also, the rest of the function doesn't execute (refetchQueries).
2.) If I go into the Apollo sandbox I can delete a record by ID only running the mutation once, but it still prints out the same error indicating it didn't work, but if I go to fetch the users again, the user has been deleted and the mutation worked. Same error message on both front and backend.
Error:
Uncaught (in promise) Error:
Invalid `context.db.user.delete()` invocation in
/home/eric/DEV/Junk/nexus-prisma-app/api/graphql/User.ts:84:44`
An operation failed because it depends on one or more records that were required but not found. Record to delete does not exist.

VS Code syntax error:
Type '(_root: {}, args: { id: string; }, context: Context) => Promise<User>' is not assignable to type 'FieldResolver<"Mutation", "deleteUser">'.
  Type 'Promise<User>' is not assignable to type 'MaybePromise<({ email?: string | null | undefined; id?: string | null | undefined; name?: string | null | undefined; username?: string | null | undefined; } | null)[]> | MaybePromise<...>'.
    Type 'Promise<User>' is not assignable to type 'PromiseLike<MaybePromise<{ email?: string | null | undefined; id?: string | null | undefined; name?: string | null | undefined; username?: string | null | undefined; } | null>[]>'.
      Types of property 'then' are incompatible.
        Type '<TResult1 = User, TResult2 = never>(onfulfilled?: ((value: User) => TResult1 | PromiseLike<TResult1>) | null | undefined, onrejected?: ((reason: any) => TResult2 | PromiseLike<...>) | null | undefined) => Promise<...>' is not assignable to type '<TResult1 = MaybePromise<{ email?: string | null | undefined; id?: string | null | undefined; name?: string | null | undefined; username?: string | null | undefined; } | null>[], TResult2 = never>(onfulfilled?: ((value: MaybePromise<...>[]) => TResult1 | PromiseLike<...>) | ... 1 more ... | undefined, onrejected?: (...'.
          Types of parameters 'onfulfilled' and 'onfulfilled' are incompatible.
            Types of parameters 'value' and 'value' are incompatible.
              Type 'User' is missing the following properties from type 'MaybePromise<{ email?: string | null | undefined; id?: string | null | undefined; name?: string | null | undefined; username?: string | null | undefined; } | null>[]': length, pop, push, concat, and 29 more.

I made a the repository public so you can see the entirety of the code :
https://github.com/EricPezzulo/Nexus-GraphQL-boilerplate
How to reproduce
./api/graphql/User.ts:
import { extendType, nonNull, objectType, stringArg } from "nexus";

export const User = objectType({
  name: "User",
  definition(t) {
    t.string("id");
    t.string("name");
    t.string("username");
    t.string("email");
  },
});

export const GetUsersQuery = extendType({
  type: "Query",
  definition(t) {
    t.nonNull.list.field("users", {
      type: "User",
      resolve(_root, _args, context) {
        return context.db.user.findMany();
      },
    });
  },
});

export const UserMutations = extendType({
  type: "Mutation",
  definition(t) {
    t.field("createUser", {
      type: "User",
      args: {
        name: nonNull(stringArg()),
        username: nonNull(stringArg()),
        email: nonNull(stringArg()),
      },
      resolve(_root, args, context) {
        const newUser = {
          name: args.name,
          username: args.username,
          email: args.email,
        };
        return context.db.user.create({ data: newUser });
      },
    });
    t.nonNull.list.field("findUser", {
      type: "User",
      args: {
        email: nonNull(stringArg()),
      },
      resolve(_root, args, context) {
        console.log(args);
        return context.db.user.findMany({
          where: {
            email: args.email,
          },
        });
      },
    });
  },
});

export const DeleteUserMutation = extendType({
  type: "Mutation",
  definition(t) {
    t.nonNull.list.field("deleteUser", {
      type: "User",
      args: {
        id: nonNull(stringArg()),
      },
      async resolve(_root, args, context) {
        console.log(args.id);
        return await context.db.user.delete({
          where: {
            id: args.id,
          },
        });
      },
    });
  },
});

Expected behavior
The delete mutation is supposed to run with no errors, and then re-fetch the data without refreshing the webpage.
Prisma information
./prisma/schema.prisma :
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id          String         @id @default(cuid())
  name        String
  username    String
  email       String         @unique
}

Environment & setup

OS: Arch Linux
Database: PostgreSQL
Node.js version: 17.3.0

Prisma Version
"prisma": "^3.8.1",

You are trying to return a list where you are returning the a single object. Please make the following change in order to fix this:
export const DeleteUserMutation = extendType({
  type: "Mutation",
  definition(t) {
-   t.nonNull.list.field("deleteUser", {
+.  t.nonNull.field("deleteUser",{
      type: "User",
      args: {
        id: nonNull(stringArg()),
      },
      async resolve(_root, args, context) {
        console.log(args.id);
        return await context.db.user.delete({
          where: {
            id: args.id,
          },
        });
      },
    });
  },
});


How to hidden Week View's Day Time Show

Clear and concise description of the problem

For big data, I think the data in the red frame is useless and messy!
I want to know if there is a props to **HIDDEN** this
Suggested solution
Now I can only use CSS to hide it
Alternative
No response
Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Would you like to open a PR for this feature?

[ ] I'm willing to open a PR

@zangguojun I'm afraid your question is unclear. You just want to hide the week view? Or you don't want the week view to be a time grid? (and, if that is the case, what else would it be?)

@zangguojun I'm afraid your question is unclear. You just want to hide the week view? Or you don't want the week view to be a time grid? (and, if that is the case, what else would it be?)

Sry, I may not say clearly.
emmm, I only want to hidden the bottom time grid (2222 part), and heighten the top(11111 part)

Then you may want to write your own custom Week view component


[Docbug][BuildAdaptiveCard-samplecode][3886]

Added code sample. Please review.

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/tabs/how-to/build-adaptive-card-tabs.md
95
7
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit ae8c5ce:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/tabs/how-to/build-adaptive-card-tabs.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Configure Lambda@Edge deployment package without user interaction

This pull request resolves issue #38 with additional feature of providing configuration using command line arguments.

Hi - any update available on this PR?


Feature/functional

added extra argument in compare and callback (so you can use arrow functions)

Coverage remained the same at 100.0% when pulling 2799de6944a8765f073e9182a292cf424887568c on feature/functional into 1c20088938aa0ac5fcc6e8634b9f8514ab1d2070 on master.

Coverage remained the same at 100.0% when pulling 305a634b99cc1f0febf22ddccfcedb73f47f20a7 on feature/functional into 1c20088938aa0ac5fcc6e8634b9f8514ab1d2070 on master.

Coverage remained the same at 100.0% when pulling d9407274fac67bbd4b46e6c2b0daf6f454414f45 on feature/functional into 1c20088938aa0ac5fcc6e8634b9f8514ab1d2070 on master.

Coverage remained the same at 100.0% when pulling faec25c4fd3d56cb4777892923c51ee490da675f on feature/functional into 1c20088938aa0ac5fcc6e8634b9f8514ab1d2070 on master.

Coverage remained the same at 100.0% when pulling faec25c4fd3d56cb4777892923c51ee490da675f on feature/functional into 1c20088938aa0ac5fcc6e8634b9f8514ab1d2070 on master.

Coverage remained the same at 100.0% when pulling faec25c4fd3d56cb4777892923c51ee490da675f on feature/functional into 1c20088938aa0ac5fcc6e8634b9f8514ab1d2070 on master.


Add expected answers to DataFrame method examples

I feel it would benefit understanding for Dataframe methods if we also include the expected answer of calling the method in datafusion/core/src/dataframe/mod.rs
Currently we have a usage example and it would be great adding the expected answer
Originally posted by @comphead in https://github.com/apache/datafusion/pull/12520#discussion_r1765376444

Hi, I haven't contribute here before and would like to take this issue.

I have added expected result in my fork.
Could I also change doctest data to make methods' usage more apparent?


Intellisense suggestion doesn't remember my snippet preference.

Hi,
I want to report a situation which I face after upgraded to 1.20.1.
The situation is the intellisense suggestion feature doesn't keep my snippets priority.
For example,
I have two snippets, one created by myself and another one by an extension, both triggered by typing "log".  The first one is always not my preferred, even I've chosen the second one for many times.
In addition, I've set my perference as ""editor.snippetSuggestions": "top"" already.

VSCode Version: 1.20.1
OS Version: Mac OS

Does this issue occur when all extensions are disabled?: No

The first one is always not my preferred, even I've chosen the second one for many times.

Yeah, we do store only the label and the suggestion type which isn't enough in this case...


It's possible to get x, y and z from touching on screen?

Hi Tiago, I'm facing a problem with x, y and z. I have 360 img using expo-gl, react-three/fiber and your lib.
The o onChange event has 3 coordinates but It's possible to get this by touching on the image?
{"target": {"camera": [Object], "dampingFactor": 0.05, "enablePan": true, "enableRotate": true, "enableZoom": false, "enabled": true, "ignoreQuickPress": false, "maxAzimuthAngle": Infinity, "maxPolarAngle": 3.141592653589793, "maxZoom": Infinity, "minAzimuthAngle": -Infinity, "minPolarAngle": 0, "minZoom": 0, "onChange": [Function onChange], "panSpeed": 1, "rotateSpeed": 1, "target": {"x": -0.384156060231433, "y": 0.08967214502665298, "z": 1.8325161061520638}, "zoomSpeed": 1}}

Hi @daviseares!
Let me see if I understood the problem correctly, you would like to have the target information of onChange without any changes?
If the answer is yes, I believe you can create a state that will be updated with onChange, or, to prevent re-rendering, update the value of a variable that lives out of the component with onChange and then use it in the onClick event.

@daviseares I'm closing this now, please re-open it if the solution I suggested doesn't work.

@daviseares I'm closing this now, please re-open it if the solution I suggested doesn't work.

I'm not working on this project anymore. Unfortunately I'm out of the company. But thanks for your help, mate!


(Suggestion) Add a feature to set a cost for town creation

I think a town creation cost is very important since it works like a filter for players that join the server create a town, play a few minutes and leave forever, this will avoid having hundreds of abandoned towns in the pl storage.

Yeah I mean, sure, though it may also have the opposite effect if players can't make a town and decide to leave. I'd like to have some sort of automatic pruning feature available in the future.

Agree, but I think setting a low value that makes the player grind like 8-10 minutes to get enough money is the best of both worlds.

I like this idea, and also gives a use for the money requirements for Level 1 in the levels.yml


PR10000?

wow, What an amazing achievement!

Reynold is just claiming all the good numbers for himself.

:)

Now I gotta think hard about what I should submit using this branch when I reopen the pull request.

Streaming DataFrames? I think this is a very significant feature!


fixed protocol async issue to show protocol logs   #39-refactoring

Working as expected, thenceforth merging.


Update team members

Description

How Has This Been Tested?

Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

cc @VaishnaviHire @LaVLaS


Question about per-user configs

Sorry for opening multiple issues at once
I just want to make sure that it's completely fine to make new classes of the ChatGPTClient for each user who uses it, I want to customize the chatgpt label per user.. or are there better ways of doing this?
EDIT: Also wondering about how I can keep the current date in the promptPrefix updated 🤔
My current thinking is that I'd make a gptClient for each user who uses it - each time they use it, I don't know how else I'd keep it updated

CLIENT.userLabel = INSERT_USER_NAME
^ the issue with this is if multiple users uses it at the same time
though I think a way of unique userlabels would be to make the user label something unique like "USER1"
and then just change it after text completion, but that might mess with
I noticed when I just used a generic name, it would reply as if that name is the user who talks to it ( makes sense )
but if it's something like "user" then it uses that in the context that there's multiple users for example..
this is just an example of how it uses the label in context

Correct, the best way to do it right now is to create a new client instance for every user. If you want to provide dynamic info for the promptPrefix, I guess you can even create a new client instance for every message?


Account Gateway, SimpleAPI, Legacy Service, TotemDB, Demo scene

I've moved all the links to the services.env file. Made a .html response file for the socials login (for possible future improvement). But decided to keep the error messages in the coresponding files, since it's bascly jsut a flawor text and the error it self is in the www.error


style:create map to allocate space

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Codecov Report

Merging #358 (2dc553e) into develop (0de5a04) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop     #358   +/-   ##
========================================
  Coverage    39.66%   39.66%
========================================
  Files           52       52
  Lines         3061     3061
========================================
  Hits          1214     1214
  Misses        1717     1717
  Partials       130      130

Impacted Files
Coverage Δ

pkg/filter/ratelimit/exact.go
100.00% <100.00%> (ø)

pkg/filter/ratelimit/regex.go
100.00% <100.00%> (ø)

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 0de5a04...2dc553e. Read the comment docs.


bug: Update to latest API

Sunpower changed their API about 2 years ago.
After that, their API was kinda flakey and not super reliable.
As of May 2020, things look reasonably stable, so I got around to
finxing this.

I really ought to set up some tests aside from "does it work on my HASS box..."


Improve Array BinaryAdd Method for object[]

PR Summary
Use Array.Resize when doing += on an array type. This is more efficient than the default BinaryAdd done on other enumerable types. As adding to an array is a common operation done by people new to PowerShell this should reduce some of the issues which come with that type of code.
An example of dramatic difference this can make is reflected by this code
$s = [gc]::GetTotalAllocatedBytes($true)

Measure-Command {
    & {
        $val = @()
        for ($i = 0; $i -lt 20000; $i++) {
            $val += $i
        }
    }
}

$e = [gc]::GetTotalAllocatedBytes($true);

Write-Host "Allocated Bytes $($e-$s)"

When run with the new code (TEST=true) you can see it is 8 seconds faster and requires less memory to allocate. As the arrays get larger the differences are even more profound.
jborean:~/dev/PowerShell$ TEST=true debug/pwsh -File jordan.ps1

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 0
Milliseconds      : 795
Ticks             : 7950790
TotalDays         : 9.20230324074074E-06
TotalHours        : 0.000220855277777778
TotalMinutes      : 0.0132513166666667
TotalSeconds      : 0.795079
TotalMilliseconds : 795.079

Allocated Bytes<PHONE_NUMBER>
jborean:~/dev/PowerShell$ debug/pwsh -File jordan.ps1

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 9
Milliseconds      : 145
Ticks             : 91453429
TotalDays         : 0.000105848876157407
TotalHours        : 0.00254037302777778
TotalMinutes      : 0.152422381666667
TotalSeconds      : 9.1453429
TotalMilliseconds : 9145.3429

Allocated Bytes<PHONE_NUMBER>

This doesn't negate the existing performance impacts of adding to an array, it just removes extra work that wasn't needed in the first place (which was pretty inefficient) making it slower than it has to. People should still use an alternative like capturing the output from the pipeline or use List<T>.
PR Context
Partially Fixes: https://github.com/PowerShell/PowerShell/issues/23899
PR Checklist

[X] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[X] Summarized changes
[X] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[X] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[X] Not Applicable
OR
[ ] Documentation needed
- [ ] Issue filed:

Testing - New and feature

[X] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[X] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

People should still use an alternative like capturing the output from the pipeline or use List<T>.

In scripts/functions yes, but if this really reduces time spent on += by 90% I'll likely never care in interactive sessions anymore. Wow 🙌

The Engine WG discussed this and agree with the change, and it is ready to be reviewed.

nit: interesting, have we such issues with Collection, List (and others IEnumarable-s?

Somewhat yes, at least the known size types (not IEnumerable) could be improved by providing the capacity on the newly generated list but that's somewhat unrelated to fixing arrays. I didn't touch the code for other IList types because I was unsure whether it was safe to do IList.Count to get the capacity needed.

I didn't touch the code for other IList types because I was unsure whether it was safe to do IList.Count to get the capacity needed.

I would lean toward "maybe, but out of scope for this PR" just to get the most common use case settled quickly.

People should still use an alternative like capturing the output from the pipeline or use List<T>.

In scripts/functions yes, but if this really reduces time spent on += by 90% I'll likely never bother using lists in interactive sessions anymore. Wow 🙌

To be fair, interactively it's really hard to beat statement capture (e.g. $a = foreach ($b in $c) { $b }). Super easy, and still pretty performant

To be fair, interactively it's really hard to beat statement capture (e.g. $a = foreach ($b in $c) { $b }). Super easy, and still pretty performant

True, but I'm usually a few foreach-loops deep or splitting into multiple arrays when I need += or List at all. In those cases it's easier to manage imo.
Either way. Looking forward to this.

This is a great improvement to PowerShell 🎉.
Btw. a similar issue exists for using the increase assignment operator (+=) to build a string. (see: https://stackoverflow.com/a/70093215/1701026)
I wonder if it be possible to do something similar there by first translating the (fixed) string into a StringBuilder object, add the strings, and rebuild the string (.ToString()) at the moment the variable is retrieved?

This is a great improvement to PowerShell 🎉.
Btw. a similar issue exists for using the increase assignment operator (+=) to build a string. (see: https://stackoverflow.com/a/70093215/1701026)
I wonder if it be possible to do something similar there by first translating the (fixed) string into a StringBuilder object, add the strings, and rebuild the string (.ToString()) at the moment the variable is retrieved?


WorkQueue: convert PNN to PSN for pileup location

Fixes #12012
Superseeds https://github.com/dmwm/WMCore/pull/12015
Status
ready
Description
This PR will map the PNNs/RSEs retrieved from MSPileup to their actual PSNs, before persisting those locations in:

fresh new workqueue elements
and pileup location update thread

Is it backward compatible (if not, which system it affects?)
YES
Related PRs
None
External dependencies / deployment changes
None

I have this patch applied to cmsweb-testbed and both logs and the WQE are sound to me. Example for:
https://cmsweb-testbed.cern.ch/couchdb/workqueue/_design/WorkQueue/_rewrite/element/f503ce70a057c896b58ed97b83e5f9ab
    "PileupData": {
      "/RelValMinBias_14TeV/CMSSW_11_2_0_pre8-112X_mcRun3_2024_realistic_v10_forTrk-v1/GEN-SIM": [
        "T2_CH_CERN_HLT",
        "T2_CH_CERN",
        "T2_CH_CERN_P5"
      ],
      "/Neutrino_E-10_gun/RunIISummer20ULPrePremix-UL16_106X_mcRun2_asymptotic_v13-v1/PREMIX": [
        "T1_US_FNAL",
        "T2_CH_CERN",
        "T2_CH_CERN_HLT",
        "T2_CH_CERN_P5",
        "T3_US_FNALLPC"
      ]
    },

Thank you for the review, Andrea.
I suspect this will have to be applied to the agents as well, so I am later today cutting a new WMAgent patch release (after backporting it).

Thank you for the hot fix @amaltaro . Do we want to create an issue to report that we should need to spot similar issues in the rest of WMCore code?


Put proper alignments in the Header

i will reduce the height of navbar and align the icons and options in a proper length so it will look good.

Alright! Great, assigning to you.


[Documentation]: Updated documentation based on the latest release of v0.8.0

Is there an existing issue for this?

[X] I have searched the existing issues

What kind of documentation would you like added or changed?
During the reading of the documentation, I found that the content of the recently released v0.8.0 was missing from the README.
In order for more people to understand and use the latest version of Towhee, we should probably improve this content.

[x] Content related to v0.8.0 in the EN document https://github.com/towhee-io/towhee/pull/1759
[x] Content related to v0.8.0 in the CN document https://github.com/towhee-io/towhee/pull/1763
[x] update content in model docs with towhee v0.8.0 https://github.com/towhee-io/towhee/pull/1773

Why is this needed?
No response
Anything else?
No response

Now, I can see that the documents that should be updated are kept up to date, and this issue should be closed.


Convert Backface Carousel to Vue

[x] Convert base logic to Vue
[x] Convert styles to be extendable through Vue
[x] Create altered description

Implemented in https://github.com/YuraVolk/Js-Library/commit/1070abf8dcc20fcdd591cae21b66a524a30dc887.


Feature #5 Receiving build status from travis ci

Updated README.md badge url from local to travis ci badge.
Removed local build badge status

Still need to add code coverage badge. Since no unit testcase exist for current utility, so keeping in "On Hold" for now


Snap-to-grid failing sometimes without Drag Ruler enabled

https://ptb.discord.com/channels/915186263609454632/1107502968179273778/1151887419113742479

Fixed in v0.6.10.


VS Code - "Go to 'Object' Definition" vs "Go to 'Variable Declaration' definition"

When developing in C/SIDE, the 'Go to Definition' on variables with a complex datatype (pages, tables, codeunits, ...) always opened the 'object'. It didn't point to the variable declaration (globals / locals)
Working in AL with the 'Go to Definition' always navigates / points to the variable declaration first, from where we need to click a second time on the datatype to actually open the object / file.
Is there any option is VSCode (or by means of a 3rd party extension) to allow direct navigation / Go to 'object' definition, the same way it was implemented in C/AL?
recCustomer : Record Customer;
recMyISVTable: Record "MY ISV Table"
...
recCustomer.MODIFY; >> Alternative would be appreciated to open the 'Customer' table when
right-clicking on the recCustomer.
recMyISVTable.whatever; >> Alternative would be appreciated to open the 'MY ISV Table' table when right-clicking on the recMyISVTable.

Hi @fvet, this behavior is by design. Goes to definition moves you to the variable declaration first and from there you can see the actual object declaration.
Considering introducing a new command to go to the object declaration like C/SIDE was doing, you should look on https://aka.ms/BusinessCentralideas if something similar is already logged and vote for it, or log a new idea there if was not. We're monitoring top Ideas and will consider them for a future release.

https://experience.dynamics.com/ideas/idea/?ideaid=ec9e4af6-f060-e911-b047-0003ff68a0b2


[Regression] Segfault when running two instances

Describe the bug
Running wry twice it segfaults
Steps To Reproduce
cargo run --example hello_world & cargo run --example hello_world
Expected behavior
Two instances should start
LOG
(process:246998): Gtk-CRITICAL **: 09:57:30.630: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed

(process:246998): Gtk-CRITICAL **: 09:57:30.632: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed

(process:246998): Gtk-CRITICAL **: 09:57:30.632: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
Wry has started!
[1]  + 246998 segmentation fault (core dumped)  cargo run --example hello_world

Platform and Versions (please complete the following information):
OS: Linux
Rustc: 1.53.0-nightly (42816d61e 2021-04-24) also on stable
Would you assign yourself to resolve this bug?

[ ] Yes
[x] No

Additional context
This is a regressing, 0.8.0 works fine

Thanks for the report!
Tested it and found this is caused by fixed application id introduced in v0.9
I'll make it None for now and maybe expose a method for users to set it.


Support @JsonKey for EnumerationCodec

I'd like it if I could have an enum codec like this:
sealed trait ApiResultStatus
object ApiResultStatus {
  @JsonKey("SUCCESS")
  case object Success extends ApiResultStatus

  @JsonKey("NOT_FOUND")
  case object NotFound extends ApiResultStatus

  implicit val encoder = deriveEnumerationDecoder[ApiResultStatus]
}

// Success.asJson = "SUCCESS".asJson, etc

Have you looked at Enumeratum? I think it supports something like this.
In my view users should just write out instances for these cases:
import io.circe.{Decoder, Encoder}, io.circe.syntax._

implicit val encodeApiResultStatus: Encoder[ApiResultStatus] = {
  case ApiResultStatus.Success => "SUCCESS".asJson
  case ApiResultStatus.NotFound => "NOT_FOUND".asJson
}

implicit val decodeApiResultStatus: Decoder[ApiResultStatus] = Decoder[String].emap {
  case "SUCCESS" => Right(ApiResultStatus.Success)
  case "NOT_FOUND" => Right(ApiResultStatus.NotFound)
  case other => Left(s"Invalid ApiResultStatus: $other")
}

I'm happy to have this issue stay open, and will happily review PRs, but I won't have time to work on it myself.

In my view users should just write out instances for these cases

That's what I'm currently doing. I don't see a reason not to support @JsonKey while it exists in the library though. If I have some time I'll see about a PR for it - I think it should be relatively straightforward

@Daenyth can I work on this fix? Can you elaborate more on the issue/enhancement


Resolved Bug 647 : Design System > Enhancements in Dropdown Element

Description

Resolve the issues select list select:

Select List
Dropdown List With Search

Added Dropdown List With Search elements

Screenshots :

Checklist:

[x] My code follows the style guidelines of this project
[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 made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@prakashmhaske  please resolved conflicts

@kaushikgokhale @trivenikulkarni this PR is created for POC purposes, so there is no need to merge in dev.


ISPN-11257 Indexed queries should automatically be broadcasted

https://issues.redhat.com/browse/ISPN-11257

I've fixed some more small ws issues and merged. Thanks @gustavonalle !