Rescanning "all your notes"

The approach of the plugin is fantastic. I loved the old one and from what I see, your new version is going to improve it a lot. Thanks again for that!
One thing I always got annoyed by: I use a lot the option to "Download images locally for all your notes".
There are two griefs I have with that:

It takes AGES with my vault as I have a lot of content with images and schematics.
Some articles "hang" for a long time, I can see them stalling in the little progress window.

Now I wonder:
Is there any way to exclude notes that have not changed since the last download?
This would save so much time.
All the best!

Yes , I thought about that too. Note that I would  recommend to use command for all notes with caution on 0.14.5, since some parsing issues were found after release, and some notes may lost some images.
In version 0.14.6 I tried to improve parsing  as much as I can.


Arangodb cluster options

My Environment

ArangoDB Version:        3.6.7-1
Storage Engine:             RocksDB
Deployment Mode:       Cluster
Deployment Strategy:   ArangoDB Starter
Configuration:               3 servers - Agent, Coordinator, DBserver roles on each node

Question:
I need to change such Arangodb server options for cluster:
query.memory-limit
query.max-runtime
rocksdb.block-cache-size
rocksdb.total-write-buffer-size
cache.size
Am I right that it should be done in coordinator configs - arangod.conf (on each node) ?
Did not find explicit instructions on where to do this.
https://www.arangodb.com/docs/stable/programs-arangod-options.html

Hi @TuminD,
The easiest way to specify ArangoDB server (arangod) options with the starter (arangodb) is via pass through options.
Unfortunately not all options in the stated documentation state whether these options should be applied on an Agent, Coordinator or DBserver.
You can use --coordinators... for options:

query.memory-limit
query.max-runtime

and --dbservers... for options:

rocksdb.block-cache-size
rocksdb.total-write-buffer-size
cache.size

Hi @TuminD, did you have a chance to try the pass-through option?

Hi @Simran-B
I've tried to specify ArangoDB server options with the starter via pass through options and also via arangod conf file (arangod.conf)
are these alternative ways to setup server options ?
I've check Coordinator's running configuration via arangosh utility:
https://www.arangodb.com/docs/stable/administration-configuration.html#fetch-current-configuration-options
But could not check DBserver running configuration via arangosh:
arangosh --server.endpoint tcp://<IP_ADDRESS>:8530 --server.database _system
Got Error message: 'not authorized to execute this request'
How to check DBserver running configuration?

Hi @maxkernbach
maybe can you help with these questions (above) ?

Hi @TuminD,
Let me explain this with the following a example. A local 3 node cluster is deployed with the starter (arangodb) command below:
arangodb --starter.local --coordinators.query.max-runtime=20

Internally 9 arangod processes are started: 3 nodes and one dbserver, coordinator and agent per node.
One of the 9 arangod processes (in this case a coordinator):
/usr/sbin/arangod -c /home/max/Documents/starter/cluster/local-slave-2/coordinator8549/arangod.conf --database.directory /home/max/Documents/starter/cluster/local-slave-2/coordinator8549/data --javascript.startup-directory /usr/share/arangodb3/js --javascript.app-path /home/max/Documents/starter/cluster/local-slave-2/coordinator8549/apps --log.file /home/max/Documents/starter/cluster/local-slave-2/coordinator8549/arangod.log --log.force-direct false --javascript.copy-installation true --cluster.my-address tcp://localhost:8549 --cluster.my-role COORDINATOR --foxx.queues true --server.statistics true --cluster.agency-endpoint tcp://localhost:8531 --cluster.agency-endpoint tcp://localhost:8541 --cluster.agency-endpoint tcp://localhost:8551 --query.max-runtime 20

As you can see in the command, the starter created a configuration file for this coordinator in the directory /home/max/Documents/starter/cluster/local-slave-2/coordinator8549/arangod.conf, which is used for this arangod process. In addition the option --query.max-runtime 20 is attached.
So, as shown above, the starter pass through option is not directly written into the config file that the starter (arangodb) creates, but rather attached to the single arangod process command.

How to check DBserver running configuration?

Unfortunately, this is not possible. You can connect to a DBserver when specifying a JWT secret with arangosh --server.jwt-secret-keyfile <path/to/secret>, but can't retrieve the running configuration as within coordinators since JavaScript transactions are not available on a DBserver.

Hi @maxkernbach
Thanks for your detailed explanation

So, as shown above, the starter pass through option is not directly written into the config file that the starter (arangodb) creates, but rather attached to the single arangod process command.

Ок, for example:
Am I right that I can specify Coordinator (or other role) configuration options in two ways?:

via pass through options: --coordinators.query.max-runtime=20
via arangod conf file (arangod.conf):

[query]
max-runtime = 20

And both ways are lead to identical Coordinator configuration?
Or second way is wrong\not recommended?

Hi @TuminD,

Am I right that I can specify Coordinator (or other role) configuration options in two ways?

Yes, it is correct that these are both viable options to change the configuration. You just have to make sure to modify the correct configuration files (created by the starter) and specify pass-through-options on every execution of the starter (arangodb).


Retail/pos rename

Background
Partly resolves https://github.com/Shopify/pos-next-react-native/issues/23232
Solution
Basically copy-paste retail-ui-extensions to pos-ui-extensions and retail-ui-extensions-react to pos-ui-extensions-react, then update supporting files.
NB: I ran into a typescript problem while building for the first time. Since -react depends on non-react, I had to add the non-react package first, then yarn build, then add the -react package, then yarn build again. Is this expected? Will it cause problems with other folks first builds?
🎩
yarn build and verify that the new pos-ui-extensions(-react) packages build.
Checklist

[X] I have :tophat:'d these changes
[X] I have updated relevant documentation

If you merge this, don't deploy it yet. We might need to include a few minor fixes before we cut the GA version. I got a few reports from partners.


Headers for increased clarity of install options

Fixes #2651
This improves readability for users scanning the install page.
cc @thesuperzapper @castrojo @shannonbradshaw @Bobgy

/lgtm
Thank you! Agree this PR made it more readable


Android - In rules, in max. expense age field, user able to type 6th digit briefly

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

Version Number: V9. 0.65-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Issue reported by: Applause Internal Team
Action Performed:

Launch hybrid app
Tap profile icon -- workspaces -- workspace
Tap more features - Enable rules
Tap on the rules
Tap maximum expense age

Expected Result:
In rules, in max. expense age field, only 5digits must be allowed to type.
Actual Result:
Describe what actually happenedIn rules, in max. expense age field, user able to type 6th digit briefly.
Workaround:
Unknown
Platforms:

[x] Android: Standalone
[x] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/fd4e4227-0f6c-4ab2-953e-0b387ca40c25

View all open jobs on GitHub

@joekaufmanexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Proposal
Please re-state the problem that we are trying to solve in this issue.
Android - In rules, in max. expense age field, user able to type 6th digit briefly
What is the root cause of that problem?
On RulesMaxExpenseAgePage, we don't add maxLength props to Input
What changes do you think we should make in order to solve the problem?
Adding maxLength is 5
What alternative solutions did you explore? (Optional)

Proposal
Please re-state the problem that we are trying to solve in this issue.
Android - In rules, in max. expense age field, user able to type 6th digit briefly
What is the root cause of that problem?
On RulesMaxExpenseAgePage, we don't add maxLength props to Input
https://github.com/Expensify/App/blob/44f5c5c9ad416bab2914f77e270319b97afaf156/src/pages/workspace/rules/RulesMaxExpenseAgePage.tsx#L73
What changes do you think we should make in order to solve the problem?
Adding maxLength is 5
Also should do with other pages: RulesAutoPayReportsUnderPage, RulesAutoApproveReportsUnderPage, RulesMaxExpenseAmountPage, RulesReceiptRequiredAmountPage
What alternative solutions did you explore? (Optional)


How to add lighting when a stl file is displayed using mplot3d?

Hi,
Is there a way to add lighting when displaying an stl file with mplot3d?
In mplot3d, lighting is added for a surface plot in this manner.
rgb = np.ones((Z.shape[0], Z.shape[1], 3))
illuminated_surface = light.shade_rgb(rgb, Z)
ax = Axes3D(plt.figure())
ax.plot_surface(X, Y, Z, rstride=1, cstride=1, linewidth=0, antialiased=False,
                facecolors=illuminated_surface)

but I'm not sure how to pass the parameters in
ax.add_collection3d(mplot3d.art3d.Poly3DCollection(new_mesh.vectors))
appreciate any help

Perhaps with the lightsource parameter to plot_surface? I'm not really sure, I don't know too much about matplotlib :)

This is the function I use.  It sometimes does some weird things where faces that should be hidden peek through faces that are in the front.  I'm not sure if that's a bug in matplotlib or my code or what; if anyone has any suggestions on how to fix that, I'd be happy to hear.
import numpy
from stl import mesh
from mpl_toolkits import mplot3d
from matplotlib import pyplot
from matplotlib.colors import LightSource

def plotSTL(filename):
    # Create a new plot
    figure = pyplot.figure()
    axes = mplot3d.Axes3D(figure)

    # Load the STL mesh
    stlmesh = mesh.Mesh.from_file(filename)
    polymesh = mplot3d.art3d.Poly3DCollection(stlmesh.vectors)

    # Create light source
    ls = LightSource(azdeg=225, altdeg=45)

    # Darkest shadowed surface, in rgba
    dk = numpy.array([0.2, 0.0, 0.0, 1])
    # Brightest lit surface, in rgba
    lt = numpy.array([0.7, 0.7, 1.0, 1])
    # Interpolate between the two, based on face normal
    shade = lambda s: (lt-dk) * s + dk

    # Set face colors
    sns = ls.shade_normals(stlmesh.get_unit_normals(), fraction=1.0)
    rgba = numpy.array([shade(s) for s in sns])
    polymesh.set_facecolor(rgba)

    axes.add_collection3d(polymesh)

    # Adjust limits of axes to fill the mesh, but keep 1:1:1 aspect ratio
    pts = stlmesh.points.reshape(-1,3)
    ptp = max(numpy.ptp(pts, 0))/2
    ctrs = [(min(pts[:,i]) + max(pts[:,i]))/2 for i in range(3)]
    lims = [[ctrs[i] - ptp, ctrs[i] + ptp] for i in range(3)]
    axes.auto_scale_xyz(*lims)

    pyplot.show()

I landed here looking for the same thing, after getting really close to the sample function shown. Is there a good way to do this using solely LightSource and Poly3DCollection? I can get rid of edges, but shading facets (and culling invisible ones) is a major pain.


Append reference topic to shortened document title

This PR is related to #187 and responds to the comment there from @trych that it would be preferable for reference titles to drop the 'reference' part when displaying help on a method, constant, class or variable, as shown in the following screen grab.

I have made this a separate pull request rather than adjusting the previous one so that you can choose the one that best suits your needs.

Just a note - I've been trying to understand a bit better where the documentation files come from. And I think I understand now that I should have made these changes in the p5.js repository, not the p5js-website repository. Specifically the pageView.js and itemView.js files. These are generated as part of the documentation build process and copied in to this repo.
I'll cancel the pull request.


Placeholder for minor refactoring tasks

[ ] Remove the final keyword from method arguments and local variables. Of course keep the static finals as is.
[ ] private static instead of static private.
[ ] keep the fields of a class at the top of the class definition, not at the bottom.
[ ] Define inner classes such as CustomCollectionEditor with a class definition, as opposed to anonymously. This improves readability during debug. Otherwise the type is simply shown as e.g. ShippingController$1.
[ ] write idToItemMapping = new TreeMap<>(); as opposed to idToItemMapping = new TreeMap<Long, VolumeCountPair>();
[ ] com.nkwebapps.shipit.repository.RoleRepository: Missing white space before class definition opening bracket.
[ ] com.nkwebapps.shipit.service.StorageItemService: Missing white space between keyword if and opening bracket, in method changeStorageItemCount.
[ ] com.nkwebapps.shipit.service.ShippingService: Missing white space between keyword for and opening bracket, in method getShippings.

I will mark 4th subtask as "Invalid", becasue even if it helps during debugging, it reduces code readability. Overall first priority is to write human-readable code, not debug-readable.


Have a standard interface to use LLMs to extract entities and information from narratives to fill-in multiple questions in the interview

Something like:

Define a list of fields with some context around them (unfortunately, this doesn't come "free" with the way Docassemble defines questions, but we could do a Quine (parse the YAML that the interview is running on to get the list of questions)
Send the user's narrative response along with the list of fields and ask GPT-3 which fields have been defined by the narrative response
Have a standard way for the user to check our responses. Perhaps just showing all of the questions as usual but with some answers filled in with default values that can be easily adjusted.

Perhaps this should also allow the user to upload relevant documents, we ask GPT-3 to extract the names of people and addresses, and then we ask the user to match the names and addresses to different objects in the interview. Since understanding who the user is vs other parties may not be simple.

Also see: #695

The idea here is that sometimes the user will naturally provide a long narrative description of their problem before they start an interview. For example, it might be the description that they provided to SPOT. It might be an intake that they've already performed with a case handler who then directed them to use our guided interview.
Rarely, we might ask a user who has already selected our interview to give us a narrative before we ask guided questions. But this is less likely to be a good user experience (it's likely that the user will add a lot of irrelevant information to their narrative so it won't be efficient of the user's time)

Maybe the first way to experiment with this feature is a generic "upload case notes" feature that is just for case handlers to use.


Exclude NSX segments

Hello,
I've tested this against a vCenter bound to NSX and with some NSX-managed overlay segments. They seem to be read as regular portgroups/VLANs, however attempts to create or modify them on Netbox fails as their VLAN ID is unset.
rest.go:132         DEBUG   (vcenter-test): Creating objects.Vlan with path /api/ipam/vlans/ with data: Vlan{ID: 0, Name: NSX-TEST, Vid: 0, Status: active}
main.go:101         ERROR   (vcenter-test): unexpected status code: 400: {"vid":["This field is required."]}
main.go:120         INFO    (main): Skipping removing orphaned objects...
main.go:130         INFO    (main): ⚠ syncing of source cor-vvc-10-p-ar failed

I'm not sure what additional information I can provide.

Hello, thanks for opening the issue. Currently, there isn't any specific logic implemented yet to handle NSX segments. I am also not particularly familiar with this feature, but I will take a look into it. I see that the problem in the above example is that the VID is set to 0, which is then not sent to API because of the omitempty (which could be the issue).
In the meantime, if you are maybe familiar with go, the code for handling networks can be found here and here. Also if you could provide longer debug output, or vsphere network api values that would be great.

I'll try to produce some, unfortunately I have not had sufficient time to dedicate to this.

This has been solved in #129. Reopen if needed.


Help needed with updating reposerver and making kbld work

I  followed this tutorial
I am trying to use kbld for argocd application.  But I am getting error.
Ran below steps on minikube on Mac m1 air
minikube version
minikube version: v1.31.1
commit: fd3f3801765d093a485d255043149f92ec0a695f

helm repo add argo https://argoproj.github.io/argo-helm
helm upgrade -i  my-argo-cd argo/argo-cd --version 4.5.4 -f argocd-values.yaml

Values file(argocd-values.yaml) contain following
dex:
  enabled: false
notifications:
  enabled: false
applicationSet:
  enabled: false
server:
  extraArgs:
    - --insecure
  config:
    configManagementPlugins: |
      - name: kbld
        generate:
          command: ["bash", "-c"]
          args: ['helm template --release-name "$ARGOCD_APP_NAME" -f <(echo "$HELM_VALUES") . > kbld.yaml && kbld -f kbld.yaml >> final.yaml && cat final.yaml']
repoServer:
  initContainers:
    - name: download-tools
      image: busybox:1.35.0
      command: [ sh, -c ]
      env:
        - name: KBLD_VERSION
          value: "0.33.0"
      args:
        - wget -q https://github.com/vmware-tanzu/carvel-kbld/releases/download/v${KBLD_VERSION}/kbld-linux-amd64 &&
          mv kbld-linux-amd64 /custom-tools/kbld &&
          chmod +x /custom-tools/kbld
      volumeMounts:
        - mountPath: /custom-tools
          name: custom-tools
  volumes:
    - name: custom-tools
      emptyDir: { }
  volumeMounts:
    - mountPath: /usr/local/bin/kbld
      name: custom-tools
      subPath: kbld

Following is the pod log
k describe pod my-argo-cd-argocd-repo-server-6676b45448-l2lvg
Name:             my-argo-cd-argocd-repo-server-6676b45448-l2lvg
Namespace:        default
Priority:         0
Service Account:  my-argo-cd-argocd-repo-server
Node:             minikube/<IP_ADDRESS>
Start Time:       Mon, 24 Jun 2024 00:06:45 +0530
Labels:           app.kubernetes.io/component=repo-server
                  app.kubernetes.io/instance=my-argo-cd
                  app.kubernetes.io/managed-by=Helm
                  app.kubernetes.io/name=argocd-repo-server
                  app.kubernetes.io/part-of=argocd
                  app.kubernetes.io/version=v2.3.3
                  helm.sh/chart=argo-cd-4.5.4
                  pod-template-hash=6676b45448
Annotations:      <none>
Status:           Pending
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/my-argo-cd-argocd-repo-server-6676b45448
Init Containers:
  copyutil:
    Container ID:  docker://0e6ac7e96fa727354e2d5243fd9b5c4150b4db31bd16971d8f75630230bfb086
    Image:         quay.io/argoproj/argocd:v2.3.3
    Image ID:      docker-pullable://quay.io/argoproj/argocd@sha256:dd738f234fcdb0aac8631a0fd1aafbbcd86f936480b06e8377b033ef7a764f71
    Port:          <none>
    Host Port:     <none>
    Command:
      cp
      -n
      /usr/local/bin/argocd
      /var/run/argocd/argocd-cmp-server
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Mon, 24 Jun 2024 00:06:46 +0530
      Finished:     Mon, 24 Jun 2024 00:06:46 +0530
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/argocd from var-files (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-whmmz (ro)
  download-tools:
    Container ID:  docker://6ebd3624491c23302f2fa7ecb4f8b307e88cf96a8ee682eae5bda2a1a9cd7585
    Image:         busybox:1.35.0
    Image ID:      docker-pullable://busybox@sha256:5be7104a4306abe768359a5379e6050ef69a29e9a5f99fcf7f46d5f7e9ba29a2
    Port:          <none>
    Host Port:     <none>
    Command:
      sh
      -c
    Args:
      wget -q https://github.com/vmware-tanzu/carvel-kbld/releases/download/v${KBLD_VERSION}/kbld-linux-amd64 && mv kbld-linux-amd64 /custom-tools/kbld && chmod +x /custom-tools/kbld
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Mon, 24 Jun 2024 00:12:41 +0530
      Finished:     Mon, 24 Jun 2024 00:12:42 +0530
    Ready:          False
    Restart Count:  6
    Environment:
      KBLD_VERSION:  0.33.0
    Mounts:
      /custom-tools from custom-tools (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-whmmz (ro)
Containers:
  repo-server:
    Container ID:
    Image:         quay.io/argoproj/argocd:v2.3.3
    Image ID:
    Port:          8081/TCP
    Host Port:     0/TCP
    Command:
      entrypoint.sh
    Args:
      argocd-repo-server
      --redis
      my-argo-cd-argocd-redis:6379
      --logformat
      text
      --loglevel
      info
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Liveness:       tcp-socket :8081 delay=10s timeout=1s period=10s #success=1 #failure=3
    Readiness:      tcp-socket :8081 delay=10s timeout=1s period=10s #success=1 #failure=3
    Environment:
      HELM_CACHE_HOME:   /helm-working-dir
      HELM_CONFIG_HOME:  /helm-working-dir
      HELM_DATA_HOME:    /helm-working-dir
    Mounts:
      /app/config/gpg/keys from gpg-keyring (rw)
      /app/config/gpg/source from gpg-keys (rw)
      /app/config/reposerver/tls from argocd-repo-server-tls (rw)
      /app/config/ssh from ssh-known-hosts (rw)
      /app/config/tls from tls-certs (rw)
      /helm-working-dir from helm-working-dir (rw)
      /home/argocd/cmp-server/plugins from plugins (rw)
      /tmp from tmp-dir (rw)
      /usr/local/bin/kbld from custom-tools (rw,path="kbld")
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-whmmz (ro)
Conditions:
  Type              Status
  Initialized       False
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  custom-tools:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  gpg-keys:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      argocd-gpg-keys-cm
    Optional:  false
  gpg-keyring:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  ssh-known-hosts:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      argocd-ssh-known-hosts-cm
    Optional:  false
  tls-certs:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      argocd-tls-certs-cm
    Optional:  false
  helm-working-dir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  argocd-repo-server-tls:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  argocd-repo-server-tls
    Optional:    true
  tmp-dir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  var-files:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  plugins:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  kube-api-access-whmmz:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                     From               Message
  ----     ------     ----                    ----               -------
  Normal   Scheduled  7m49s                   default-scheduler  Successfully assigned default/my-argo-cd-argocd-repo-server-6676b45448-l2lvg to minikube
  Normal   Pulled     7m48s                   kubelet            Container image "quay.io/argoproj/argocd:v2.3.3" already present on machine
  Normal   Created    7m48s                   kubelet            Created container copyutil
  Normal   Started    7m48s                   kubelet            Started container copyutil
  Normal   Started    7m3s (x4 over 7m47s)    kubelet            Started container download-tools
  Normal   Pulled     6m11s (x5 over 7m47s)   kubelet            Container image "busybox:1.35.0" already present on machine
  Normal   Created    6m11s (x5 over 7m47s)   kubelet            Created container download-tools
  Warning  BackOff    2m46s (x25 over 7m45s)  kubelet            Back-off restarting failed container download-tools in pod my-argo-cd-argocd-repo-server-6676b45448-l2lvg_default(5cbd789a-a1a2-4cc0-a082-26a6ab66127d)

From a cursory look, I could not see any error in your output. Can you check what error you are getting?
Also, the URL was changed to https://github.com/carvel-dev/kbld/ instead of tanzu-vmware. Not sure if that affects something because there will be a redirect.

Back-off restarting failed container

Hmm, I need more information. What is the error that you get inside the container? Something is happening inside the container that is causing this container to fail, and we need first to understand that before we can better diagnose the problem


npm install -g ?

Is it possible to wrap this as a shell script? very handy if so!

Yes, see #33 #37
I added support for it today, it needs a version bump, an update sent to NPM and a mention in the README.

@Illyism feel free to put what you put in https://github.com/purifycss/purifycss/pull/37 in the README (without the screen shot). Put it below the 'callback' section and above the 'at build time' section


Make package search paths part of the +Mirth resource and add a CLI argument to add to it

Replaces the existing PACKAGE_SEARCH_PATH variable with a field in the +Mirth resource and adds the -P command line flag to add items to it, without any package search path flags it defaults to lib. This also replaces the couple data definitions related to +Mirth with the struct syntax sugar, but that's easy to undo separately from the rest of the changes if not wanted.

Great, thanks!


Add deep-link capture for Sign-in (https://world.openfoodfacts.org/cgi/session.pl)

What

Add deep-link capture for Sign-in (https://world.openfoodfacts.org/cgi/session.pl)

Part of

#4016

I'm not sure of the added value to add deep links for account management.
If I'm on the website, I certainly don't want to be redirected to the app


Processing of extra command line arguments with docker containers

Extra command line arguments in a request to a docker container do not seem to be supported with the current implementation of the SingularityMesosTaskBuilder.
Assume the following the definition of a deployment:
{
  "deploy": {
        "requestId": "myrequest",
        "id": "12",
        "command": "r",
        "containerInfo": {
            "type": "DOCKER",
            "docker": {
                "image": "rocker/r-base",
                "portMappings": []
            }
        },
        "resources": {
            "cpus": 0.1,
            "memoryMb": 128,
            "numPorts": 0
        }
    }
}

For completeness here is the definition of the associated (on-demand) request:
{
    "request": {
        "id": "myrequest",
        "owners": [
<EMAIL_ADDRESS>        ],
        "daemon": false
    },
    "state": "ACTIVE",
    "requestDeployState": {
        "requestId": "myrequest",
        "activeDeploy": {
            "requestId": "myrequest",
            "deployId": "12",
            "timestamp":<PHONE_NUMBER>919
        }
    },
    "instances": 1,
    "hasMoreThanOneInstance": false,
    "canBeScaled": false
}

When POSTing -e "print('hello world')" to http://hostname:7099/singularity/api/requests/request/myrequest/run I would expect the following command to be run on the above specified docker container: r -e "print('hello world')"
This seems to be pretty close according to the /var/log/mesos/mesos-slave.INFO log file:
E1229 20:16:54.056499  3232 slave.cpp:2787] Container 'a286e452-2afe-4410-9785-ea15b8bbcbbd' for executor 'myrequest-12-1419880613593-1-falcon-DEFAULT' of framework 'Singularity' failed to start: Failed to 'docker run -d -c 102 -m 134217728 -e INSTANCE_NO=1 -e TASK_HOST=falcon -e TASK_REQUEST_ID=myrequest -e TASK_DEPLOY_ID=12 -e ESTIMATED_INSTANCE_COUNT=1 -e MESOS_SANDBOX=/mnt/mesos/sandbox -v /tmp/mesos/slaves/20141229-201537-16842879-5050-3183-S0/frameworks/Singularity/executors/myrequest-12-1419880613593-1-falcon-DEFAULT/runs/a286e452-2afe-4410-9785-ea15b8bbcbbd:/mnt/mesos/sandbox --net host --name mesos-a286e452-2afe-4410-9785-ea15b8bbcbbd rocker/r-base r -e "print('hello world')"': exit status = exited with status 1 stderr = 2014/12/29 20:16:54 Error response from daemon: Cannot start container 3ec96d9866a86bb337f142560fb92fbd47e0f7a8799e7907965df2940141b0a2: exec: "r -e \"print('hello world')\"": executable file not found in $PATH

The problem, however, is, that with the call to docker, docker seems to be believe that r -e "print('hello world')" is a single executable. There might be two issues here:

"maybeCmdLineArgs" for a SingularityPendingTask is a single String rather than e.g. a List like the field 'extraCmdLineArgs' in  ExecutorData

The processing of the command and the 'maybeCmdLineArgs' in the SingularityMesosTaskBuilder builds a compound command leading to the behavior shown above (see also the processing of the CommandInfo on the mesos side). Rather, it seems like the 'maybeCmdLineArgs' should be processed similar to the deploy arguments as seen here

See also the following post on Google Groups.

Great. Should be easy to make the API / taskBuilder change. We can open another issue for processing the field in the UI.

Great. Should be easy to make the API / taskBuilder change. We can open another issue for processing the field in the UI.

Just looking at this and not yet sure the best way to change all of our JSON models to maximize compatibility.

See #415


Fixed 'cloneMethod' option casing and clarified anonym() documentation

The Collection constructor references options.clonemethod (lower case) and options.cloneMethod (camel case), I'm assuming both references should be options.cloneMethod
The anonym() method documentation indicates that you can pass in an indexes array, but the indexesArray is being passed as the Collection constructor 'options' parameter, so I changed the documentation to match, rather than changing the behavior

Good job! Thanks, @TeamworkGuy2.


Returning non-JSON serializable data types results in messed up typing

If non-JSON serializable data types are returned by a route (i.e. Date, Set, undefined, etc), the client would not detect this.
Eden fetch/treaty would both happily claim that the returned data is of type Set/Date/etc yet they are not. This will break the program eventually, as soon as you try to access properties or call methods on them.
I would suggest to allow users to plug in more potent transformers (such as superjson or devalue) or to make the client "know" about the broken types by returning never or unknown or any other fallback type.
But letting the user think the API would be type-safety while it is only to some extend is dangerous imo.

I this also the case for Eden Fn btw? Would it also detect types wrongly?

Seems related: https://github.com/elysiajs/elysia/issues/175

I use this to serialize non-JSON types. It works for me temporarily but a few ifs are missing.
export const elysiaApp = new Elysia()
	.onAfterHandle(({ response }) => {
		if (response && typeof response === 'object') {
			if (ELYSIA_RESPONSE in response) {
				return;
			}
			return new Response(SuperJSON.stringify(response));
		}
	});
export const eden = treaty<ElysiaApp>('localhost:3334', {
	fetch: {
		credentials: 'include',
	},
	async onResponse(response) {
		return SuperJSON.parse(await response.text());
	},
});

Closing as not going to implement in the core of Elysia.
You can easily create a adapter for Superjson natively as describe here.

I use this to serialize non-JSON types. It works for me temporarily but a few ifs are missing.
export const elysiaApp = new Elysia()
	.onAfterHandle(({ response }) => {
		if (response && typeof response === 'object') {
			if (ELYSIA_RESPONSE in response) {
				return;
			}
			return new Response(SuperJSON.stringify(response));
		}
	});
export const eden = treaty<ElysiaApp>('localhost:3334', {
	fetch: {
		credentials: 'include',
	},
	async onResponse(response) {
		return SuperJSON.parse(await response.text());
	},
});

@SaltyAom Thanks for responding. If this isn't implemented in Elysia itself, isn't it somewhat of a bug though?
Consider this code:
import { Elysia } from 'elysia';
import { treaty } from '@elysiajs/eden'

const elysiaApp = new Elysia()
	.get('/foo', () => {
        return {
            // Let's return a Date object from our handler...
            bar: new Date()
        }
    })
    .listen(3000);

const app = treaty<typeof elysiaApp>('localhost:3000');

// TypeScript types this as {data: {bar: Date}}
const {data} = await app.foo.get();

// But when you actually look at the type, this prints `string`
console.log(typeof data?.bar);

Elysia is doing the right thing and coverting Date objects to strings already, but it doesn't set the right type for them. Adding superjson feels a bit like overkill to me, as it's going to add a layer of complexity (+ a performance hit) just to fix the wrong type being returned.
Personally, the solution I've been using myself is to assert the type in the handler, ie.
.get('/foo', () => {
    return {
        // Ugly type assertion here
        bar: new Date() as unknown as string
    }
})

Which is messy, but at least it allows the rest of the code downstream to have the correct type set.

@SaltyAom Thanks for responding. If this isn't implemented in Elysia itself, isn't it somewhat of a bug though?
Consider this code:
import { Elysia } from 'elysia';
import { treaty } from '@elysiajs/eden'

const elysiaApp = new Elysia()
	.get('/foo', () => {
        return {
            // Let's return a Date object from our handler...
            bar: new Date()
        }
    })
    .listen(3000);

const app = treaty<typeof elysiaApp>('localhost:3000');

// TypeScript types this as {data: {bar: Date}}
const {data} = await app.foo.get();

// But when you actually look at the type, this prints `string`
console.log(typeof data?.bar);

Elysia is doing the right thing and coverting Date objects to strings already, but it doesn't set the right type for them. Adding superjson feels a bit like overkill to me, as it's going to add a layer of complexity (+ a performance hit) just to fix the wrong type being returned.
Personally, the solution I've been using myself is to assert the type in the handler, ie.
.get('/foo', () => {
    return {
        // Ugly type assertion here
        bar: new Date() as unknown as string
    }
})

Which is messy, but at least it allows the rest of the code downstream to have the correct type set.

Just add response schema

Just add response schema

True, that would address this as well. I still think the current behavior is a bug. The types do not match the actual data being returned. Having to add type assertions, or a response schema feels like a workaround, rather than a conscious design choice.

Just add response schema

True, that would address this as well. I still think the current behavior is a bug. The types do not match the actual data being returned. Having to add type assertions, or a response schema feels like a workaround, rather than a conscious design choice.

it is really complex if elysia tries to remap non-json serializable data types i guess
types will be more slower


Unsupported brand channel name when joining a server

I am using a list of proxies and it sometimes it says  - Unsupported brand channel name. None of my bots can log in

Is it a vanilla/paper server?


Disabled on MenuItems inside SimpleMenu not working

<!---
** PLEASE READ THIS BEFORE FILING AN ISSUE **

## RMWC or MDC?

I'm pretty sure its RMWC

- What RMWC Version are you using [major.minor.patch]:

5.7.2

- Name your build system [Webpack, Rollup...]:

Webpack

- Describe the bug with as much detail as possible:
I have a SimpleMenu component that renders a list of options. the options are being served as an array of MenuItem, where every MenuItem receives a disabled boolean as a prop.
For some reason, the items act normally no matter if they're disabled or not

- What happened, and what was supposed to happen:
Items on the menu should be unclickable (disabled), but they can be clicked and change the menu value.

Code Example: * I've made sure 100% that the 'disabled' prop the Dropdown components gets and passes down to menu item has the current value. and I've also tried inserting values manually to the the ItemMenu disabled prop.

```
const Dropdown = (props) => {
  const {
    options, selected, placeholder, disabled, onChange,
  } = props;
  let title = placeholder;
  const dropDownOptions = options.map((elem) => {
    if (selected === elem.value) {
      ({ title } = elem);
    }
    return {elem.title};
  });

  return (
     onChange({ value: e.detail.index + 1 })}
      handle={

{title}

        }
    >
      {dropDownOptions}

  );
};
```

Cannot reproduce. Please reopen with a codesandbox and more description of the issue.


Ignore failing tests from bad gas limit config

Not very important, but in the resulting test_pass_state CSV file from running the plonky2_runner, a lot of "Failed" results happen to arise from tests which we cannot verify because of the design choice of supporting only 32-bit gas limits.
As such, I'm proposing to have a dedicated TestPass variant called Ignored purposedly for this failure case, to trim the number of false negatives.

For the record, I'm also running the whole suite against the latest main and the changes from this branch, to make sure those ignored tests wouldn't reveal some failing edge cases.

Yeah this seems like a reasonable way to handle this. I think it might be slightly cleaner to filter these out in the parser instead when we parse the test *.json --> .cbor, but this is more than fine. Thanks for adding this!


compare only time differences of same direction edges

Like suggested, only take differences of same-direction edges. "succ" is now an absolute value, needs no reset. Only keep one minimum, which now has double value/resolution.
Value-dependent tolerances are not done here.

Thanks for this. It makes sense to measure minimum edge interval, not minimum width because we could not expect same signal transition in reality as you remarked. I'd like to add some comments on suggested code.

In fact I had more comments in my working version, took them out for the commit in order to have a minimum diff. Shall I add them?

I made confuse you. I meant my review comments.

Weird. I did it from mobile. I'll check how they look from PC later.

Now I hope you can see my comments.

great! Is it okay for you if I squash your commits into one when merge?

Done. Or do you want a reduced commit message?

 I do merge.


makefile: speed up test runs startup time

The Makefile has many places where it needlessly invokes a sub-make instead of declaring the dependencies correctly. This is causing slowdowns on startup, and especially noticeable during test runs (make check) where each time a sub-make is invoked it regenerates make_config.mk and that takes a long time. Rework the dependency graph so that at least running tests doesn't involve invoking make three times.

QA passed


Gh pages update git url and package/groupId

Update git url from https://github.com/nflabs/zeppelin to https://github.com/apache/incubator-zeppelin
Update package/groupId from com.nflabs to org.apache
Add hive as default interpreter
Remove docs/current file to run jekyll

LGTM


Track pathways viewed per task

We currently provide a counter for content tagged, e.g., "4 pathways remaining". In cases like Under Construction, it's often appropriate to complete the task and leave 4 pathways with the tag. It would be nice to improve the counter to also track pathways viewed (or yet to be reviewed), e.g., "3 of 4 remaining pathway to be reviewed".
Not sure how to implement this with current load/display/count logic...

This will not be relevant with the site and new PR system for QA protocol. Closing.


XP drops

The Building Block in quarry mode dropx massive amounts of XP. This is very annoying, bacause it slows my client down until it reaches 1fps.
Is there a config option to disable this? Or can you add one?
Minecraft 1.12.2, newest forge, newest RF tools

Hmm, pretty hard... Not sure how I would go about doing that. Have to think about it

Oh, I thought you were dropping the XP, because they drop out of your machine
maybe add an internal XP buffer (mob_grinding_utils can store XP for example). But your internal XP buffer can be voided

No, the drops are from the blocks that are being harvested and the problem is that when I harvest a block these XP orbs are generated out of my control

A workaround would be to destroy all EntityXPOrb in a certain area


Name of open document is not shown on the title bar

Previously name of the currently active notebook/file was shown on title bar and reported to OS. It is not there anymore. This makes switching tabs difficult when multiple JupyterLab Desktop instances are open because everything is just "JupyterLab".

this is fixed now with v3.5.1-1


MudBlazor Table with pagination and filter not working on Blazor Server App

Bug type
Component
Component name
Table
What happened?
I guess there is a bug with the MudBlazor Table when pagination and filtering are enabled...
If I use the template found in here at the section "Table with pagination and filtering", in my solution the filtering works fine until I click on any row inside the table. Then it stops working, and I don't understand why. The function private bool FilterFunc(Element element, string searchString) is not anymore triggered (simply put a breakpoint to see).
I tested it on a fresh new Blazor Server App with only the template from the MudBlazor website implemented, and doesn't work either (so I assume my code is not interfering).
I am not adding any code, because it is just the one anyone can find on the official website. See the Reproduction Steps for more info.
P.S. I uploaded the test I made on a clean Blazor solution on github at this link, in case you want to avoid going through the (very) simple reproduction steps.
Many thanks.
Expected behavior
The filter function should keep working also after clicking on the table rows
Reproduction link
https://github.com/supertrip86/DELETE
Reproduction steps

Create a new Blazor Server App with .NET 5.0 in Visual Studio
Install MudBlazor (in my case version 5.2.0)
Follow the steps to setup MudBlazor in here
Add the line services.AddHttpClient(); in ConfigureServices in Startup.cs to register the HTTP client
Go to https://mudblazor.com/components/table#table-with-pagination-and-filtering and copy and paste the code example for the Table with pagination and filter (section: "Table with pagination and filtering") in your solution, for example in Pages/Index.razor
In the page you chose (e.g. Pages/Index.razor) replace the line Elements = await httpClient.GetFromJsonAsync<List<Element>>("webapi/periodictable"); with Elements = await httpClient.GetFromJsonAsync<List<Element>>("https://try.mudblazor.com/webapi/periodictable");
Add the MudBlazor.Examples.Data.Models anywhere in your solution. Create a new C# class anywhere, and copy and paste the following code inside:

`
using System.Collections.Generic;
using System.Text.Json.Serialization;
namespace MudBlazor.Examples.Data.Models
{
      public class Element
      {
          public string Group { get; set; }
          public int Position { get; set; }
          public string Name { get; set; }
          public int Number { get; set; }

          [JsonPropertyName("small")]
          public string Sign { get; set; }
          public double Molar { get; set; }
          public IList<int> Electrons { get; set; }

          public override string ToString()
          {
              return $"{Sign} - {Name}";
          }
      }
  }

`
Relevant log output
No response
Version (bug)
5.2.0
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Turns out this is a bug only related to v5.2.0.
It is not present in the previous version v5.1.5 nor in the subsequent.


refactor(consensus): state machine returns VecDeque instead of Vec

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2168
#2167  👈
#2166
#2161
#2160
#2159
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @matan-starkware and the rest of your teammates on  Graphite


etcd2 cluster in AWS auto-scaling group configuration - not working

I am following the culster-discovery to setup an etcd2 cluster with 3 machines in auto-scaling group. All 3 machines are configured with the same configuration using the same discovery token. Cluster size is 3. The initial new cluster started as expected, no any issues.
In order to test auto-scaling,  I terminated one of the 3 machines. AWS auto-scaling policy  started an new instance.
However the new instance (with the cloud-config), cannot join the cluster. I have waited many hours.
On  the new instance:
core@ip-10-0-2-116 ~ $ etcdctl member list
329a33449d3bb66e: name=59b0ca34f5794ab487bfed84fcc8b6e9 peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:2379
580214ba0e1f72e5: name=b3b39e5158a546f489af32a28613de32 peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:2379
5a849f7b5adf207b: name=6ca7c06784414be886efa8c38c354e9d peerURLs=http://<IP_ADDRESS>:2380 clientURLs=http://<IP_ADDRESS>:2379

core@ip-10-0-2-116 ~ $ etcdctl cluster-health
cluster is healthy
member 329a33449d3bb66e is unhealthy
member 580214ba0e1f72e5 is healthy
member 5a849f7b5adf207b is healthy

The <IP_ADDRESS> instance was the original one that I terminated in order test auto-scaling. The new instance is <IP_ADDRESS>, which is not on the list.
And here is the systemd log:
core@ip-10-0-2-116 ~ $ systemctl status etcd2
● etcd2.service - etcd2
   Loaded: loaded (/usr/lib64/systemd/system/etcd2.service; static; vendor preset: disabled)
  Drop-In: /run/systemd/system/etcd2.service.d
           └─10-oem.conf, 20-cloudinit.conf
   Active: active (running) since Fri 2015-06-12 00:57:07 UTC; 2h 7min ago
 Main PID: 610 (etcd2)
   Memory: 13.4M
   CGroup: /system.slice/etcd2.service
           └─610 /usr/bin/etcd2

Jun 12 03:04:26 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:26 proxy: zero endpoints currently available
Jun 12 03:04:26 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:26 proxy: marked endpoint http://<IP_ADDRESS>:2379 available
Jun 12 03:04:26 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:26 proxy: marked endpoint http://<IP_ADDRESS>:2379 available
Jun 12 03:04:30 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:30 proxy: marked endpoint http://<IP_ADDRESS>:2379 available
Jun 12 03:04:32 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:32 proxy: failed to direct request to http://<IP_ADDRESS>:2379: net/http: request canceled while waiting for connection
Jun 12 03:04:32 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:32 proxy: marked endpoint http://<IP_ADDRESS>:2379 unavailable
Jun 12 03:04:37 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:37 proxy: marked endpoint http://<IP_ADDRESS>:2379 available
<bold>Jun 12 03:04:37 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:37 proxy: failed to direct request to http://<IP_ADDRESS>:2379: dial tcp <IP_ADDRESS>:2379: no route to host</bold>
Jun 12 03:04:37 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:37 proxy: marked endpoint http://<IP_ADDRESS>:2379 unavailable
Jun 12 03:04:42 ip-10-0-2-116.us-west-2.compute.internal etcd2[610]: 2015/06/12 03:04:42 proxy: marked endpoint http://<IP_ADDRESS>:2379 available

So somehow the etcd2 is trying to act in proxy mode and talking to the dead http://<IP_ADDRESS>:2379 endpoint.
To try to get the new instance in the cluster, I tried:

Delete the dead node using etcdctl member <remove>
Add new node using etcdctl member add <name>  http://<IP_ADDRESS>:2380
Restart etcd2 on all of them

I still could not get the new node to join the cluster.
The last thing I tried is to stop etcd2 on the new instance, remove  /var/lib/etcd2/proxy directory and start the etcd2 again. Still cannot join the cluster. I am getting  etcd: discovery cluster full, falling back to proxy. See logs below.
ip-10-0-2-116 etcd2 # systemctl start  etcd2
ip-10-0-2-116 etcd2 # systemctl status  etcd2
● etcd2.service - etcd2
   Loaded: loaded (/usr/lib64/systemd/system/etcd2.service; static; vendor preset: disabled)
  Drop-In: /run/systemd/system/etcd2.service.d
           └─10-oem.conf, 20-cloudinit.conf
   Active: active (running) since Fri 2015-06-12 04:11:13 UTC; 3s ago
 Main PID: 17904 (etcd2)
   Memory: 2.8M
   CGroup: /system.slice/etcd2.service
           └─17904 /usr/bin/etcd2

Jun 12 04:11:13 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:13 etcdserver: datadir is valid for the 2.0.1 format
Jun 12 04:11:14 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:14 etcd: stopping listening for client requests on http://<IP_ADDRESS>:4001
Jun 12 04:11:14 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:14 etcd: stopping listening for client requests on http://<IP_ADDRESS>:2379
Jun 12 04:11:14 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:14 etcd: stopping listening for peers on http://<IP_ADDRESS>:7001
Jun 12 04:11:14 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:14 etcd: stopping listening for peers on http://<IP_ADDRESS>:2380
Jun 12 04:11:14 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:14 etcd: discovery cluster full, falling back to proxy
Jun 12 04:11:14 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:14 proxy: using peer urls [http://<IP_ADDRESS>:2380 http://<IP_ADDRESS>:2380 http:...83:2380]
Jun 12 04:11:14 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:14 proxy: updated peer urls in cluster file from [http://<IP_ADDRESS>:2380 http...55:2380]
Jun 12 04:11:14 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:14 proxy: listening for client requests on <IP_ADDRESS>:2379
Jun 12 04:11:14 ip-10-0-2-116.us-west-2.compute.internal etcd2[17904]: 2015/06/12 04:11:14 proxy: listening for client requests on <IP_ADDRESS>:4001

It seems that, if an instance in an auto-scaling group dies, the replacement instance cannot join the cluster automatically, and I am also having trouble to fix it manually.
I have been using static IP for etcd cluster for awhile, but would like to use auto-scaling group with discovery token to achieve further automation.
Here is system information it it  helps:
ip-10-0-2-116 etcd2 # docker info
Containers: 0
Images: 18
Storage Driver: overlay
 Backing Filesystem: extfs
Execution Driver: native-0.2
Kernel Version: 4.0.3
Operating System: CoreOS 695.0.0

Cloud-config:
#cloud-config
coreos:
  etcd2:
    # generate a new token for each unique cluster from https://discovery.etcd.io/new?size=3
    discovery: https://discovery.etcd.io/84f89c6680532f1c3e97ea520764ab48
    # multi-region and multi-cloud deployments need to use $public_ipv4
    advertise-client-urls: http://$private_ipv4:2379
    initial-advertise-peer-urls: http://$private_ipv4:2380
    # listen on both the official ports and the legacy ports
    # legacy ports can be omitted if your application doesn't depend on them
    listen-client-urls: http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:4001
    listen-peer-urls: http://$private_ipv4:2380,http://$private_ipv4:7001
  fleet:
    metadata: disk=ssd,env=itlab,platform=ec2,provider=aws,region=us-west-2,role=etcd2
    public-ip: $private_ipv4

Another question, when using CoreOS cloud-config to bootstrap a cluster and when the cluster is fully functional, under what condition one needs to use etcdctl to add/remove members manually? Shouldn't the new machine join the cluster automatically if it has the same discovery token?

Answer my own questions. I managed to manually add the new instance to the cluster.

etcdctl member add testme http://<IP_ADDRESS>:2380
edit the /run/systemd/system/etcd2.service.d/20-cloudinit.conf file like so:

# /run/systemd/system/etcd2.service.d/20-cloudinit.conf
[Service]
Environment="ETCD_ADVERTISE_CLIENT_URLS=http://<IP_ADDRESS>:2379"
#Environment="ETCD_DISCOVERY=https://discovery.etcd.io/84f89c6680532f1c3e97ea520764ab48"
#Environment="ETCD_INITIAL_ADVERTISE_PEER_URLS=http://<IP_ADDRESS>:2380"
Environment="ETCD_LISTEN_CLIENT_URLS=http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:4001"
Environment="ETCD_LISTEN_PEER_URLS=http://<IP_ADDRESS>:2380,http://<IP_ADDRESS>:7001"
Environment="ETCD_NAME=testme"
Environment="ETCD_INITIAL_CLUSTER=testme=http://<IP_ADDRESS>:2380,b3b39e5158a546f489af32a28613de32=http://<IP_ADDRESS>:2380,6ca7c06784414be886efa8c38c354e9d=http://<IP_ADDRESS>:2380"
Environment="ETCD_INITIAL_CLUSTER_STATE=existing"

Note that I commented out ETCD_DISCOVERY and ETCD_INITIAL_ADVERTISE_PEER_URLS,   added the rest of the cluster information based on the etcd runtime-configuration doc.
3. systemctl stop etcd2; systemctl daemon-reload; systemctl start etcd2
So I think, in auto-scaling case, a new instance won't join the cluster automatically.  See run time configuration.

@xueshanf Yes. You are right. You need to use new configuration for joining existing cluster. You can build a tine wrapper around etcd to do that too.


fixed typos in code

The error seems intentional to me. @DanielRosenwasser  thoughts?

Yes, that's the goal - sorry if you missed the intent @grzegorz-zur .


fix: template tweaks

Includes

@alexcg1 changes of typos and links
@aga11313 changes to the structure and verbosity of the example

@alexcg1 could you re-review please if possible so we can merge this and the other open PRs?

LGTM :+1:


Switch to official date lib repo for date.h

Codecov Report

Merging #3128 into develop will increase coverage by 1.24%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #3128      +/-   ##
===========================================
+ Coverage    68.95%   70.19%   +1.24%
===========================================
  Files          688      687       -1
  Lines        55690    54107    -1583
===========================================
- Hits         38403    37983     -420
+ Misses       17287    16124    -1163

Impacted Files
Coverage Δ

src/ripple/app/misc/impl/ValidatorList.cpp
89.18% <ø> (ø)
:arrow_up:

src/ripple/app/ledger/impl/LedgerToJson.cpp
90.69% <ø> (ø)
:arrow_up:

src/ripple/beast/insight/Event.h
100% <ø> (ø)
:arrow_up:

src/ripple/core/impl/LoadMonitor.cpp
90.27% <ø> (ø)
:arrow_up:

src/ripple/beast/clock/basic_seconds_clock.h
96.77% <ø> (ø)
:arrow_up:

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 41b2c80...7e6c4f8. Read the comment docs.


Invalid server url is not catched by error callback.

AndroidRuntime: java.lang.IllegalArgumentException
AndroidRuntime:  at org.eclipse.paho.client.mqttv3.MqttConnectOptions.validateURI(MqttConnectOptions.java:473)

What is the url you were using??
The format of the url should be as follows
tcp://
Do not add port in your url. Add it separately in the port value.
Hence your config looks like
{
url: tcp://test.mosquitto.org,
port:1886
}

Thanks.
Congratulations for the great work.

@arcoirislabs Excuse me，How do I upload data stream to my mqtt server？

@arcoirislabs Excuse me，How do I upload data stream to my mqtt server？Can I only upload topic?

@arcoirislabs ，Hello，can you View the picture addresses and help me,very thanks!


submitting pogom to pypi (pip install)

Checklist

[ x ] I have read the FAQ
[ x ] I have checked if this issue already exists (both open and closed issues)
[ x ] I am using the most recent version of pogom from the master branch
[ ] If this is an installation issue, I am posting my OS, OS version, python version, pip version
[ ] I'm posting the complete log
[ x ] I'm using a descriptive title for this issue

My Issue
Could we implement the pypi installation? cloning the repo every time it's time consuming and complicated, with pypi should as easy as writing:
pip install -upgrade pogom
here is how to do it, a contributo or the repo must do it
http://peterdowns.com/posts/first-time-with-pypi.html

what's wrong with git pull?

@nborrmann using the pip command is more user friendly than using git. However I don't think it's necessary because if you don't want to install git you can just download a zip file of the master branch.


Ability to remove new invoker skin

Is there any ability to make default invoker? This item from compendium is kinda imbalanced because of you can't rapidly hit his hitboxes in fights due to reduced size of invo's model (his new model is almost like the circle beneath the hero in size).

There is a note in the no-bling-filters list about this. You can restore the model of standard invoker, but the sounds will remain.
// restore kidvoker since orbs attachment is bugged volvooo
  "models/heroes/invoker_kid/invoker_kid.vmdl"  "-"
  "models/heroes/invoker_kid/invoker_kid_cape.vmdl"  "-"
  "models/heroes/invoker_kid/invoker_kid_hair.vmdl"  "-"
  "models/heroes/invoker_kid/invoker_kid_sleeves.vmdl"  "-"
  // to replace kidvoker with default model anyway, comment above 4 lines and uncomment the following 3
  //"models/heroes/invoker_kid/invoker_kid_cape.vmdl"  "models/heroes/invoker/invoker_shoulder.vmdl"
  //"models/heroes/invoker_kid/invoker_kid_hair.vmdl"  "models/heroes/invoker/invoker_head.vmdl"
  //"models/heroes/invoker_kid/invoker_kid_sleeves.vmdl"  "models/heroes/invoker/invoker_dress.vmdl"

Thanks a lot, it helped!


Group Formats Not Displaying In Chat

I am currently using Luckperms, ExpansionLuckPerms, and LuckPermsHook.
My Group Formats are coming from the Spigot plugin "CMI".
This is what I have in CMI's configuration file:
GroupFormat:
'1': '%luckperms_prefix% &8{DISPLAYNAME} &8&l> &a{MESSAGE}'
'2': '{prefix_vault}&f{displayName}&7 > &r{message}'
'3': '{prefix_vault}&f{displayName}&8 > &r{message}'

And what exactly isn’t working? You gave a detailed explanation of your setup but not the issue itself (not working isn’t an issue description)

My group prefixes aren't displaying in chat, all it shows is

In the screenshot above it shows that I have a prefix but it's not showing up when I type in chat.

You need a chat plugin for the prefixes to show

You need a chat plugin for the prefixes to show

CMI plug-in can show prefixes, but it looks like it does not work with placeholder

It looks like CMI isn’t even formatting the chat. As that is the default vanilla chat. LuckPerms itself does no formatting whatsoever. So it looks like you need to properly configure the CMI Chat. How that is done should be documented on the CMI pages/docs/wiki.


Update this documentation

https://github.com/Oteemo/charts/blob/629c93fe78671a61bb759807ab95f5a8c7b6d70f/charts/sonarqube/values.yaml#L187
Hi,
This line should read
# postgresqlServer: ""
rather than
# postgresServer: ""
Thanks!

Documentation seems to be updated on the master branch and most recent release. Let me know if you need anything else.


Publish fat APK in GitHub releases?

Hey 👋 thanks for open-sourcing this project! Love it.
It'd be cool if we could download fat APKs directly from GitHub releases.
(Same goes for the iOS simulator builds when the iOS app becomes available)

Thanks for the suggestion! We'll discuss as a team and let you know if we decide to do so.
Nonetheless, cloning the project currently and building should allow you to generate the full APK yourself for the time being (./gradlew :app:assembleRelease should do the trick).

Hey, no need to discuss:D I did it in #148. I'll be grateful for a review.

Thanks @bartekpacia! Will review shortly and let you know of any feedback.


Provide a front page to list containers marked as "public"

This was spun out of a comment on #9 .

I'll add this to my ui / frontend to-dos.

and I'll coordinate backend changes to track as a label and convey back to the UI via the ContainerSummary of  GET /api/containers

To summarize what we spoke about on Gitter:
Right now, we are working at the solar system level. For example, if you create your own Carina account and deploy MCCY to a cluster on that account, you have created your own solar system. You can then create worlds (i.e. containers) in that solar system that can be public or private.
This issue #13 states that we want people who go to said cluster (e.g. http://mccy.itzg.me) to be able to see the public container / worlds. Those who login at will be able to see all the worlds.
I have to think now how we want to break up the three views: public; public + private; and public + private + administration.

Ok. Given that this is at the solar system level, I think it'd work to have something like the following:

The landing page would then be at the galaxy level. I think this will work since it's KISS.

And landing page version 1 would allow UFOs (Unauthenticated uses) to see only worlds that were declared public in that solar system.

I like @itzg idea of using carousel to switch between public list and login form. Default would be it starts with the public list.

I'm working on this in a new branch. Right now, I have something just slapped together. I'm not sure if it works yet and it doesn't look nice yet.

Hm. It looks like I broke something when I tried to merge master into my branch. Careful. I'm going to rm the branch and then push it again.

No problem. I hadn't pulled the branch yet.

Ok. What I have now sort of works. On my local machine without docker containers the login screen / public game list flashes.
When you get the chance, could you update feature/public branch?


How far the chats are delivered when translating?

Hi there,
On this page you do not describe how the translate is handled. E.g. if we are in EU and want to keep our data in EU only. Does this means that out chats are translated within EU?

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

ID: 19e91f77-0c01-5d38-0bd4-65ee44aab5cb
Version Independent ID: 08ea83b3-c241-979c-3afb-3355ab322489
Content: Turn on inline message translation - Microsoft Teams
Content Source: Teams/inline-message-translation-teams.md
Service: msteams
GitHub Login: @chuckedmonson
Microsoft Alias: chucked

@Petri-X Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

Again it is odd, that I need to open support case and paid on that to get Microsoft's own documentation improved. I still believe you have all available connections to get this clarified better. But looks like I need to continue my investigation :)


Prisma extensions: typescript error while filter operations

Bug description
The problem was discussed here:
https://github.com/prisma/prisma/discussions/20053#discussioncomment-6544286
It looks like there is no way to avoid duplicated code in this case.
How to reproduce
This is the repo to reproduce the bug:
https://github.com/meotimdihia/bug-prisma-typescript-extensions-filter-operations

Expected behavior
No response
Prisma information
// Add your code using Prisma Client

const prisma = new PrismaClient({ log: ["query"] }).$extends({
  query: {
    post: {
      async $allOperations({ args, query, operation, model }) {
        if (operation != "create" && operation != "update") {
          return await query(args);
        }
        // works fine but duplicated code
        if (operation == "create") {
          const cur = await query(args);
          await prisma.post.update({
            data: {
              title: "abcedf",
            },
            where: {
              id: cur.id,
            },
          });
        }

        // works fine but duplicated code
        if (operation == "update") {
          const cur = await query(args);
          await prisma.post.update({
            data: {
              title: "abcedf",
            },
            where: {
              id: cur.id,
            },
          });
        }
        if (operation == "create" || operation == "update") {
          const cur = await query(args);
          // doesn't work, we need a solution for this problem
          await prisma.post.update({
            data: {
              title: "abcedf",
            },
            where: {
              id: cur.id, // Property 'id' does not exist on type 'number | PayloadToResult<PostPayload<DefaultArgs>, RenameAndNestPayloadKeys<PostPayload<DefaultArgs>>> | ... 4 more ... | Optional<...>'.
              // Property 'id' does not exist on type 'number'.ts(2339)
            },
          });
        }
      },
    },
  },
});

Environment & setup

OS: macOS
Database: Sqllite
Node.js version: 18

Prisma Version
prisma                  : 5.0.0
@prisma/client          : 5.0.0
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 6b0aef69b7cdfc787f822ecd7cdc76d5f1991584 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 6b0aef69b7cdfc787f822ecd7cdc76d5f1991584 (at node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 4.17.0-26.6b0aef69b7cdfc787f822ecd7cdc76d5f1991584
Default Engines Hash    : 6b0aef69b7cdfc787f822ecd7cdc76d5f1991584
Studio                  : 0.487.0

(Internal thread)

On our end this issue has not been prioritized, you maybe have to keep code duplicated for now.


BSP_I2C

Removed most of the content from the original version of the BSP_I2C. Trying to move it over to the simple HAL commands in the documentation.

Planning on utilizing a queue with structs containing the metadata, device address, and data length for each transmit call that cannot be immediately serviced. Created two prototypes but have not started the interrupt routine.
I need to check if the data buffer passed into the HAL receive command automatically gets inserted with the data or if our interrupt handler must do this. Considering using the memory address interrupt-based send/receives if this functionality is also desired.

Also; change the target branch to main since this will get merged directly there

Also; change the target branch to main since this will get merged directly there

I'll modify this branch to branch off the main branch instead before switching this PR to merge with main.

can you check to see if the queue is full (for adding) or empty (for popping) before you do any queue accesses.

can you check to see if the queue is full (for adding) or empty (for popping) before you do any queue accesses.

An empty queue should already be accounted for. What is the desired behavior for a full queue? Should I just return a Error status instead of a "okay" or "busy" status?

Yeah full queue we just drop the message and return error. @Lakshay983 I'm pretty sure the xQueueSend returns an error if the queue access fails, so we can just check the return condition (see https://www.freertos.org/Documentation/02-Kernel/04-API-references/06-Queues/04-xQueueSendFromISR)


cursor in /claimable_balances not validated

What version are you using?
1.9.0
What did you do?
Request /claimable_balances with invalid cursor value. Ex: https://horizon-testnet.stellar.org/claimable_balances?cursor=1003529-00000043d380c38a2f2cac46ab63674064c56fdce6b977fdef1a278ad50e1a7e6a5e18 (hex-encoded balance id is malformed).
What did you expect to see?
400 Bad Request response.
What did you see instead?
500 Internal Server Error response.

Fixed in #3088


2 fix for case when height is more than width but height factor is less

Still doesn't fit in the screen on some devices

Still doesn't fit in the screen on some devices


[Feature]: When using templates, allow "Read Only" env variables to be overwritten by manually set secrets

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
For templates: Ensure variables set in SECRETS take precedence over non-editable template variables
Why should this be worked on?
Some templates have ENV variables that are not editable by the user (See Appwrite _APP_DOMAIN as example)
We should allow the user to overwrite these variables by setting them in the Secrets.
When building the container, first load the pre-set config, then overwrite with any manually set secrets
This will enable users to set manual custom config that would otherwise be locked by non editable env variables

I'm closing this issue, because tracking features will be moved to GitHub discussions. Github issues will be only for bugs.
Version 4 is in full focus. v3 related issues will be closed, if it is not a critical bug.
Thanks for your understanding.


fix: add semver to container builds

The container builds are missing semver versioning. This should fix it up for you :)

@tjbck Easy one for you :)

LGTM, Thanks!

Didn't work. Check the currently building Docker image's metadata. We've been struggling with this one for a bit and @Lanhild and I feel we can best solve this by completely overhauling the Release/Build workflows, please see:

#878

Didn't work. Check the currently building Docker image's metadata:

We've been struggling with this one for a bit and @Lanhild and I feel we can best solve this by completely overhauling the Release/Build workflows, please see:

infra: Enhance releases workflow and integration #878

It will work once you publish a new release with a new tag.

One way to find out 😄

Not meaning to sound smug, but I did try this before in my own branch before. We've got larger issues with our workflow that are known and being considered.

@justinh-rahb It looks like these versions are being created by a github action itself; which may be the reason it's not pushing out the builds correctly. Is there a reason it's like this?

When using GITHUB_TOKEN to perform tasks, other workflows would not be triggered to "prevent recursive workflow runs". The recommended workaround is to use a Personal Access Token instead. See https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#triggering-a-workflow-from-a-workflow.
In this case, we would need to replace the token here which is used to create tags:
https://github.com/open-webui/open-webui/blob/6c70d0f770ce4b0acf8d2a33eb7c0f27ffbed631/.github/workflows/build-release.yml#L32


Incremental Training inside Rasa Open Source

Proposed changes:

Closes https://github.com/RasaHQ/rasa/issues/6971
Adds the ability to load NLU components and Core policies in finetune mode which means they are initialized with a previously trained model and can be further trained on a mix of old and new training data.

Individual PRs:

Changes to CLI - https://github.com/RasaHQ/rasa/issues/6971
Applying constraints for finetuning - https://github.com/RasaHQ/rasa/pull/7427

Configuration of base model is exactly the same as configuration for finetuning except the number of epochs.
No new labels(intents, actions, entities and intent_response_keys) are added to the training data. New training examples for each of these can still be added.
Base model is trained with MINIMUM_COMPATIBLE_VERSION of currently installed Rasa Open Source version.

Load NLU(https://github.com/RasaHQ/rasa/pull/7456) and Core(https://github.com/RasaHQ/rasa/pull/7458) pipelines in finetune mode.
Loading NLU components and Core policies in finetune mode - https://github.com/RasaHQ/rasa/pull/7419 This PR includes running model regression tests to verify that performance of current models are not hurt by the extra featurization we do.
Docs (https://github.com/RasaHQ/rasa/pull/7469)

Status (please check what you already did):

[x] added some tests for the functionality
[x] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

Okay, so this turned out to be a large PR as well but all the smaller PRs were peer reviewed between @joejuzl @wochinge and @dakshvar22. Additionally, PR for changes to the ML components(https://github.com/RasaHQ/rasa/pull/7419) was reviewed by Tanja as well.
@alwx Can you please review the following files - rasa/cli/..., rasa/core/agent.py, rasa/core/train.py, rasa/model.py, rasa/nlu/model.py, rasa/nlu/train.py, rasa/telemetry.py, rasa/train.py, tests/cli/test_rasa_train.py, tests/conftest.py, tests/core/conftest.py, tests/core/test_agent.py, tests/core/test_ensemble.py, tests/test_train.py? These are the engineering bits of the PR.

A final run of model regression tests before merge is running here


Our site is not building

Hello, our project ( Hashkat ) documentation is hosted on Github
http://docs.hashkat.org/en/latest/
https://github.com/hashkat/hashkat
Recently our documentation build broke when we attempted to add a new tab and reorganize the tab order (in the sidebar)
this is the build that did not happen:
hashkat/hashkat@5457592
The commits to the main github site appear to have gone fine, it is just the read the docs part We are reluctant to revert on Github because there have been several commits (tho not to documentation) .
Could you please tell us what we did wrong and how we can fix it?
Thank you.
Linda Kettle
<EMAIL_ADDRESS>416-833-3676

Closing as duplicate.


Add tests for transactions

See https://github.com/trinodb/trino-go-client/issues/32#issuecomment-1004694778
This will probably require a connector that supports transactions if we want to test this end-to-end.

I wonder if anything from this PR would be useful: https://github.com/prestodb/presto-go-client/pull/66


Canvas zoom control

Resolves #2321 and makes #2420 redundant.
Changes

Added zoom control in the bottom right corner for graph and resource views.
Zoom is disabled (and the control is hidden) when there is no content displayed.
The zoom control is automatically managed within ZoomableCanvas.

Note

I had some problems running this with local service-ui proxying, as ~rc-slider/dist/rc-slider.css wouldn't be found from in Service UI. Running npm install rc-slider inside the service-ui/client folder did it for me, but I wonder why this dependency wasn't pulled from the local Scope's package.json. Maybe it has to do with Webpack 2 vs. Webpack 1 (@foot had a similar issue with xterm). @jpellizzari I tried fixing this but couldn't figure it out - do you have any ideas what might be causing the issue?

@fbarl Re: CSS not being proxied: you stumbled on one of the limitations of our LocalModuleProxy. It only works if all dependencies are present in the service-ui. I haven't checked to see if webpack 2 exposes any new APIs that we can use to make that a nicer integration.


Format output

Hi
I found interesting your project and use it.
Thank you.
I made some changes that were necessary for me.
If you find these changes helpful, can be used.
List of changes:

Assembling the docker container via Makefile
Change the location of the configuration file by default to config/config.yaml
In the configuration file add parameters listen_addr and debug_bot
Fixed crash the application when you send a message
Added message formatting

Hi @StereoRu!
Looks like your PR conflicts with previous one (#7).

Change the location of the configuration file by default to config/config.yaml

Changing defaults is a bad practice I'd like to avoid here.

Added message formatting

Seem to be implemented in #7.

In the configuration file add parameters listen_addr and debug_bot

And removed command line option, that could break already running deployments. Please keep command line option in place with a higher priority to the one in configuration file. Both should be optional.

Fixed crash the application when you send a message

Can you provide some more details? What I can see in your code is that bot no longer reports chat ID to telegram, that's a good functionality that should be kept.

Sorry, this (#7) really more helpful.


Multiple ProducesResponseType For 200

Hi,
I have a question. In one of the project I am working on, we have action methods
that can return different types based on a header value. while this might seems crazy
to some, we wanted customers to have for example a dedicated endpoint where they
can for example load a customer object. For example a call to api/customers/1 would return a
customer lite object, containing a subset of the actual record. If they then want to load
a more detailed object, they can for example add in a header called transform, with a value such as
lite, detailed or expanded.
We felt it was better than adding multiple endpoints such as:
api/customer/1
api/customer/1/detailed
api/customer/1/expanded
Due to the amount of exposed types in the system, going with the route that we have chosen, we have spared almost 300 extra endpoints that would have been required to implement it in the url fashion.
Based on this, is there a way in which we can make use of this package and support such scenarios?

To start off i want to say that this is an API design i see from time to time and its a natural impulse to not oversubscribe when you are fetching data from a service. It is very much against the spirt of REST. That being said I work in two teams right now and one of them continues to think its important to have this 'flexibility' so you are not alone. you could save the same number of endpoints by only exposing the largest type and implementing caching if it proves to be too slow.
The question is not if you can use Swashbuckle. its the swagger spec and client generation you are going to have trouble with. There is not a great way to describe this header interaction in swagger 2.0. This means generated clients will have a hard time discovering your API.
each operation has one definition per status code. so when you have multiple definitions that are actually available based on header you can either:

list the broadest definition as the response type: this only works when this broadest definition is a proper superset of all of the other definitions.
Make a custom filter: you could build a custom filter that make a single endpoint appear as multiple endpoints, with a definition for each. This would be a little complicated and would still have a discoverability problem
Use non-standard HTTP status codes normally only one code 200 is 'OK'. you could always list other codes as these other definitions. Its messy and client generation might not work but all of the definitions will show up in the output.

@erendrake Thank you for your quick and detailed response.
I should have written my specific use case which perhaps would have helped a bit.
We build and ship clients for our endpoints built directly from source, so the intention with
Swashbuckle is not to enable automatic client generation.
Our clients would merely find it great to be able to use the ui that it generates to get an overview
of the endpoints and to be able to "play" around with it before heading straight for the code.
Our reasons behind this api design, was to minimize data across the wire by default, thus all our endpoints by default return the smallest useful form of the type in question. This is true for getting single values as well as paged results. The caller has to opt in to get a larger data object to work with. With the system. The defaults work well with the more common tasks, such as drop downs, lists etc. When a specific record is sought after they can then add the appropriate header  and get the results they are after. We found this very useful in an attempt to manage what some might call big data.
I will experiment with your ideas a bit and see which could work best before considering a forked version to play with.
Thanks again.

As per @erendrake's comments, the constraint here is going to be the Swagger specification and not Swashbuckle. So, I'm going to close this issue.
My two cents on the API design, I would always favor explicit URL's over overloaded ones. The closer you can tie a resource / URI to a specific use-case, the better as it allows you


Log level always "LOG" for every severity on metro bundler for React native

I'm using<EMAIL_ADDRESS>and the logs does not have the same severity.

I've talked too early. Just got eye on mapConsoleTransport.


Microsoft Store - allow downloading old versions

Description of the new feature / enhancement
Hello, please add the ability to list and install old versions of Microsoft Store packages, there are many reasons on one may need to use an older version of an MS Store package, to combat a bug in a newer version, to use removed features, or a business wanting to only use certified versions of software. This is a Microsoft Store API problem, meaning Microsoft Store APIs only allow you to download the latest version, and a few other for some packages, but both WinGet and Microsoft Store API needs to support downloading any old version of an app. The only way to access old versions of an app as of now is to get in contact with someone with the version you want of the app dumping it, and manually installing it, or downloading the package from an open source release if it is open source. Other than that there is NO way to obtain the older versions of MS Store packaged, which is really inconvenient. WinGet would be the perfect place to have older versions of apps downloadable, as opposed to the Microsoft Store GUI.
Proposed technical implementation details
N/A

This generally seems like a good idea. I do not know if this team has the contacts necessary to reach this goal. I'm not entirely sure, but I believe the WinGet package manager only uses the MSStore as an additional REST Source for package lookup and install, and that otherwise the teams don't have a formal relationship within the company.

@upintheairsheep
The Microsoft Store is designed to only distribute the latest versions of Apps across the matrix of supported OS and locale. If this changes, WinGet would have the ability to retrieve earlier versions, but this is completely driven by the Microsoft Store policies.

@upintheairsheep
The Microsoft Store is designed to only distribute the latest versions of Apps across the matrix of supported OS and locale. If this changes, WinGet would have the ability to retrieve earlier versions, but this is completely driven by the Microsoft Store policies.

Reopen this, I know this is related to the MS Store API and requires collaboration between the WinGet and MS Store teams, and this would be a great feature as there is no other way to do this.


Icons have shrunk on iOS 17 / Xcode 15

Icons were working perfectly prior to upgrading to Xcode 15 and iOS 17. Below is a before and after of what our icons looked like:

BEFORE
AFTER

implementation:
import { Icon } from '@ntwrk1/design-system';
import React from 'react';
import { Pressable, StyleSheet, Text } from 'react-native';

import { PrimaryColorPalette } from 'assets/colors';
import * as DropdownMenu from 'zeego/dropdown-menu';

export default function CompletedShowMenu({
  onDelete,
}: {
  onDelete: () => void;
}) {
  return (
    <DropdownMenu.Root>
      <DropdownMenu.Trigger action="press">
        <Pressable style={styles.triggerButton}>
          <Icon color={PrimaryColorPalette.MAIN_1} variant="MoreVertical" />
        </Pressable>
      </DropdownMenu.Trigger>

      <DropdownMenu.Content>
        <DropdownMenu.Item
          destructive
          key="remove"
          onSelect={onDelete}
          textValue="Remove"
        >
          <DropdownMenu.ItemTitle>
            <Text>Remove</Text>
          </DropdownMenu.ItemTitle>
          <DropdownMenu.ItemIcon
            ios={{
              name: 'trash',
              pointSize: 5,
              weight: 'semibold',
              scale: 'default',
            }}
          />
        </DropdownMenu.Item>
      </DropdownMenu.Content>
    </DropdownMenu.Root>
  );
}

const styles = StyleSheet.create({
  triggerButton: {
    height: 28,
    width: 28,
    justifyContent: 'center',
    alignItems: 'center',
    borderRadius: 50,
    borderColor: PrimaryColorPalette.MAIN_5,
    borderWidth: 1,
    transform: [{ rotate: '90deg' }],
  },
});

Xcode version 15.0
Simulator: iPhone 15 Pro

that’s not good. can you open an issue on the upstream ios library?

We are investigating this issue over the next few days.

This hasn't happened on our app for iOS 17, but I'm also on an iPhone 13 so that may be why.

Cannot reproduce on iPhone 14 Pro 17.0.3 - real device
Also not seeing it on Simulator - iPhone 14 Pro 17.0

Same, all of this works for me. Could you provide a reproduction? Going to close otherwise.


[docs] Fix syntax error in migration-v3-fr.md

[ ] I have followed (at least) the PR section of the contributing guide.

Translated docs are handled in crowdin.


Fix client-go libraries bug

What type of PR is this?
/kind bug
What this PR does / why we need it:
The client-go libraries for the Cluster scope, such as ClusterQueue, don't work fine since the libraries are generated for the Namespaced scope resources.
So, I fixed markers for the code-generator so that we can generate proper libraries.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
When we use the current client-go libraries, we will face the following errors:
an empty namespace may not be set when a resource name is provided

Does this PR introduce a user-facing change?

Fix client-go libraries bug that can not operate clusterScoped resources like ClusterQueue and ResourceFlavor.

/assign @trasc

/cherry-pick release-0.5


Reduce container vulnerabilities

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: mbaciu-gpsw:x: bbouleanu-gpsw


Check if Sentence is Pangram.cpp

Description
Solve Check if Sentence is Pangram using C++.
Fixes #1537
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[ ] My code follows the style guidelines(Clean Code) of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@harshita9621 comment out the test case

@Ayush7614 Kindly review this PR.

@harshita9621 I said to comment out the output


Use direct connection between ESP32 and Flatpack serial

Hi taHC81
Not an issue, just a suggestion  :)
What do you think about the use a direct connection between and ESP32-S3 models to eltek serial port, and removing CAN-TTL IC ??
Once ESP32 is externally programmed , then remove CAN adapter on Flatpack PCB andnd solder directly to PCB serial TTL, then control directly via WIFI of BT by ESPhome ??
ThankU

Hi, I do not rely on CAN, feel free to modify and use like it fits you best ;) My goal was to NOT modify Flatpack at all.

OK, thankU
It is just to try to use remote monitoring to Home Assistant  :)
Just removing Infineon TLE6250PG CAN ic and install directly a small ESP module to serial
Will try and use your code to monitor  ;)


python-Cython: fix source location

Motivation for this change
Fix for #16218
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

I'm building with it now, but it's slow-going; I figure if it fails I can report back, but it seems unlikely.

Duplicate of #16219. I've done the same fix two minutes earlier ;)

Doh!  I looked, just obviously wasn't quick enough on the draw.


Add skywalking agent deployment docs

Add skywalking agent deployment docs

@dailidong @CalvinKirs

good job, I will merge this PR when 1.3.6 released

There is no preview here? ...

There is no preview here? ...


[QUERY] CosmosQuery offset parameter

Question
Why doesn't com.azure.spring.data.cosmos.core.query.CosmosQuery provide offset parameter?
Setup

com.azure:azure-spring-data-cosmos:3.1.0

@mbhaskar  - please take a look at this issue.

You can use annotated queries to specify offset/limit. Please find documentation here https://docs.microsoft.com/en-us/azure/developer/java/spring-framework/how-to-guides-spring-data-cosmosdb#custom-query-execution


Make #lang cur vs #lang cur/base

For accessibility, #lang cur should probably import most of the things by default, and other #langs can be provided more restricted imports.
#lang cur should include:

[ ] sugar
[ ] ntac, auto
[ ] basic data types: nat, list, equality, prop
[ ] reflection stuff
[ ] racket + syntax-parse at phase1

#lang cur/curnel should include:

[ ] CiC
[ ] reflection
[ ] racket + syntax-parse at phase1

Agree. Do you want to make the lists of what goes in what lang?

Sure, started list above.

Ok u want me to submit pr?

Sure if you want to do it :)


Possibly leverage code from other open source project to read .pdn files

Description
Pinta is on its way to become a great replacement for Paint.NET for Windows users (and thereby enabling them to leave Windows).
However, there is a hurdle for taking the leap: Last I tried, Pinta could not import pi.pdn files created by Paint. NET.
This makes migration hard for users with many previously created files in Paint.NET.
Request
Would it be possible to look into this as part of the roadmap for Pinta?
Additional context

This is one I found that could be useful: https://github.com/drAshcroft/SciImage (have not tested, as I am not a programmer)

Another Open Source Application called LazPaint (written in Lazarus Pascal) has implemented an import/open .pdn file function that works flawlessly. Their libraries are found at https://github.com/bgrabitmap/
("Why not use LazPaint instead, if it is so great" you might ask. It has not been updated since 2022-08...)

I have also found this: https://github.com/addisonElliott/pypdn (have not tested, as I am not a programmer myself... and also not updated in a while)

See also https://github.com/PintaProject/Pinta/discussions/827  for a related discussion - there was a community addin for Pinta 1.x which could load pdn files, so this might be possible to resurrect for Pinta 2.2

@cameronwhite that's a great point! The addins are sorely missed in Pinta 2.


Freezing on datacube export to imzML [BUG]

Describe the bug
It is desirable to export a ROI of a imzML directly to a new imzML for separate processing without any preprocessing or peak picking. Currently, when doing direct export to imzML, MATLAB freezes for a long time and there is no visual confirmation that anything is actually happening. The export is usually successful after some time but this is not clear to the user as it appears frozen.
To Reproduce
Steps to reproduce the behaviour:

import a imzML on disk.
Create a region of interest
Click data reduction > datacube
Select "export at location" and "imzML"
Select output destination and start export

Expected behaviour
Spectral analysis to be usable during export or feedback to user that export is in progress and when complete
Desirable: Progress bar showing export
Software version

NPL X:/SpectralAnalysis
Source code

If using source code, MATLAB version (please complete the following information):

e.g. MATLAB R2019a

Desktop (please complete the following information):

OS: Windows
Version Windows 10

Further to this the output imzML's include blank pixels - sometimes to the size of the original dataset, but this does not seem consistent.
The expected behaviour would for there to be no empty pixels - only the selected ROI to be included.

It looks like the excess area on export is solved in the current SA version. The freezing while exporting is still present.

Hi Adam,
Thanks for this. The progress bar should be working again for exporting to imzML in 20932a81a61f4e734ea1300a4b800ac2d14c06d9.
Previously the size of the output was dependent on the minimum size of all regions selected. This is now done per region, with an option included in the interface to keep original pixel locations.
Alan


CI: add GCC 11

Coverage remained the same at 58.663% when pulling 2ddb1b2525551be82611df38804288de3099e771 on feature/ci-add-gcc11 into 469931933b0de3de1225680e09bcdad341fee514 on master.


Make ResourceLoader lazy

It will be great if S3 ResourceLoader will fetch meta-data, may be optional, only if told to so, eg calling exists(), contentLenth() and etc methods.

Hello @gschukin is there any particular situation where this has an user impact ?

Hi @aemruli
Actual S3 resource may be unavailable upon creation of Resource, but may be available later and vice versa.
Current implementation assume that S3 resource state (available, not available) can't be changed.

@aemruli
Unfortunately commit doesn't fix an issue when S3 resource were available but not available anymore.


Add test_flufl.py from Cpython v3.11.2

NOTE: This was an April Fools Day prank back in the day.

Yup, unsure if this should be added too, doubt we'll ever special case that import.


[medInria 3.1.1] Vtk not smart4 port

Port for 3.1.1 the PR of medInria 4.0:
"2 Volume VR & LUT #657"

already redone by @nbaraka


Typescript crashes over and over

Issue Type: Bug
Open a large codebase, and sometimes typescript just exits and restarts over and over.  I don't have a ton of insight into why.  I do think it is slighly more likely if you switch branches.
This only started to happen recently (last 2 weeks?), but I'm not sure if that's to do with the size of our codebase, an update to visual studio, or what.  We are on Typescript 4.1.5 (and telling VS Code to use that version).

Also does it happen with the latest TS version (4.2.3)?

@mjbvz Sorry just saw your message now; github didn't make the notification very prominent.  Anyway I will test on Friday with Insiders and 4.2, don't really have time to try prior to that.

Closing this as not actionable without more information. Please let us know if you see this on insiders with all extensions disabled


In Execute JDBC query page, you see "No datasources found in jmsRealms"

Describe the bug
With the Frank!Runner I have an instance with only one configuration. The configuration has no  tag. When I go to the Execute JDBC query page, I cannot select a datasource. The datasources list is filled with the message "No datasources found in jmsRealms".
Category

Frank Console

To Reproduce
Steps to reproduce the behavior:

Create an instance of the Frank!Framework: A parent directory with "configurations" and "tests" subdirectories.
Ensure that only one configuration is deployed, and ensure the configuration does not have a  tag.
Start the Frank!Runner.
Browse to http://localhost.
Go to "Execute JDBC query".

Expected behavior
When the instance name is Frank2Manual, there should be a datasource named "jdbc/frank2manual" in the drop-down list of datasources.
Screenshots

Environment:

Frank!Runner
Firefox
IAF Version 7.6-20200317-120259

Additional context
When I include "" in my configuration, the problem disappears.

When I include "", the problem disappears.

Sorry, GitHub compromises my message. When I add the standard jmsRealm tag, then the problem disappears.

I tested it. The issue has been fixed for the newest release of the FF!


Remaintime

add remain time when bot gets list request

Hey @SangJoKim are you still interested in trying to merge this? (Generally this PR looks good, though I'm kind of wondering how you think about a resource "status.")