Adds initial ability to see the fixture in mepo

This is an attempt to get mepo to see the fixture repo as well as all the subrepos. To do so, additional changes are needed for the components.yaml. For example, for GEOSgcm:
GEOSgcm:
   fixture: true
   develop: main

Only one of the entries in components.yaml is allowed to be a fixture: True and the only keys allowed for a fixture are fixture: and develop: since the actual git clone of the fixture is what provides the branch/tag.

Currently a draft PR as I want to be doubly sure this is still backward compatible.

Hum,
I just added
GEOSadas:
fixture: true
develop: main
tried doing a mepo status and still nothing changes ... I also tried using the mepo under your account:
/home/mathomp4/MepoDevelopment/mepo status
but still it doesn't seem to show my changes in the fixture.
I'm sure I am missing something from what you are doing.
Thx

@rtodling The version of mepo in my home directory on discover was not yet updated to this branch. I was doing local tests on my laptop for ease of testing (i.e., much faster disks). I have updated ~mathomp4/MepoDevelopment/mepo to now be on the new branch.
Now, in order for mepo to see the fixture, mepo needs to be initialized with knowledge of the fixture (chicken and egg problem). But for testing, you can try the following:
$ mkdir GEOSadas-with-mepo-fixture
$ cd GEOSadas-with-mepo-fixture
$ git clone -b feature/rtodling/migrate-to-geosadas5271  git@github.com:GEOS-ESM/GEOSadas.git
$ cd GEOSadas

This gets just the fixture. Now, add:
GEOSadas:
  fixture: true
  develop: main

to (the top of) components.yaml. Now if you run:
$ /home/mathomp4/MepoDevelopment/mepo clone
Initializing mepo using components.yaml
env                    | (b) origin/feature/bmauer/updates-from-geosadas5_27_0
cmake                  | (t) v1.0.11
ecbuild                | (t) geos/v1.0.0
...
$ /home/mathomp4/MepoDevelopment/mepo status
Checking status...
GEOSadas               | (b) feature/rtodling/migrate-to-geosadas5271
   | components.yaml: modified, not staged
env                    | (b) feature/bmauer/updates-from-geosadas5_27_0 (DH)
cmake                  | (t) v1.0.11 (DH)
ecbuild                | (t) geos/v1.0.0 (DH)
...

You'll see that it now shows you have a modified file, components.yaml, in the fixture GEOSadas.
As a test, I committed that change to a (temporary) branch of GEOSadas off of yours and then tried it all in one.
First, I will alias mepo to the development version for this just to cut down on extra text:
$ alias mepo=/home/mathomp4/MepoDevelopment/mepo
$ source /home/mathomp4/MepoDevelopment/etc/mepo-cd.bash

Now let's clone my test branch from scratch:
$ mkdir GEOSadas-with-mepo-fixture-in-repo
$ cd GEOSadas-with-mepo-fixture-in-repo
$ mepo clone -b feature/mathomp4/mepo-fixture-testing git@github.com:GEOS-ESM/GEOSadas.git
Initializing mepo using components.yaml
env                    | (b) origin/feature/bmauer/updates-from-geosadas5_27_0
cmake                  | (t) v1.0.11
ecbuild                | (t) geos/v1.0.0
...
$ cd GEOSadas
$ mepo status
Checking status...
GEOSadas               | (b) feature/mathomp4/mepo-fixture-testing
env                    | (b) feature/bmauer/updates-from-geosadas5_27_0 (DH)
cmake                  | (t) v1.0.11 (DH)
...

So the fixture is seen. Now we'll move up the tree, but do things in the fixture to make sure we are tracking it correctly:
$ mepo-cd GEOSana_GridComp
$ pwd
/discover/swdev/mathomp4/Models/GEOSadas-with-mepo-fixture-in-repo/GEOSadas/src/Components/@GEOSana_GridComp
$ mepo whereis
GEOSadas               | ../../..
env                    | ../../../@env
cmake                  | ../../../@cmake
...
$ mepo checkout -b my-awesome-new-feature GEOSadas
+ GEOSadas: my-awesome-new-feature
$ mepo compare
Repo                   | Original                                            | Current
---------------------- | --------------------------------------------------- | -------
GEOSadas               | (b) feature/mathomp4/mepo-fixture-testing (DH)      | (b) my-awesome-new-feature
env                    | (b) feature/bmauer/updates-from-geosadas5_27_0 (DH) | (b) feature/bmauer/updates-from-geosadas5_27_0 (DH)
cmake                  | (t) v1.0.11 (DH)                                    | (t) v1.0.11 (DH)
...
$ /home/mathomp4/MepoDevelopment/mepo branch list GEOSadas
GEOSadas |   feature/mathomp4/mepo-fixture-testing
         | * my-awesome-new-feature

The new branch is seen, let's make a change:
$ echo "This is a new line" >> $(mepo whereis GEOSadas)/README.md
$ mepo status
Checking status...
GEOSadas               | (b) my-awesome-new-feature
   | README.md: modified, not staged
env                    | (b) feature/bmauer/updates-from-geosadas5_27_0 (DH)
cmake                  | (t) v1.0.11 (DH)
...
$ mepo diff
Diffing...
GEOSadas (location: ../../..):

diff --git a/README.md b/README.md
index 3065294..792630d 100644
--- a/README.md
+++ b/README.md
@@ -188,3 +188,4 @@ cd install/bin
 ### Run the ADAS

 Like the AGCM step above, the ADAS setup scripts are also `install/bin/`
+This is a new line
$ mepo-cd
$ git status
On branch my-awesome-new-feature
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   README.md

no changes added to commit (use "git add" and/or "git commit -a")

NOTE 1: That the fixture monitoring of mepo only works with this (testing for now) version of mepo. You can't use an older mepo with it just because older mepo had some very strong restrictions that I had to relax in the case for fixtures.
NOTE 2: I suggest putting the GEOSadas: bit at the top of components.yaml just because mepo initializes in the order of components.yaml. You could put it anywhere in the file, I just think the top is best.
If you could test this, that would be good. I am fairly certain with my testing that this new version is backward compatible (i.e., it works just fine with components.yaml without the fixture bits), but I want to consult with @tclune to make sure I get the SemVer right for a release. I am 99% certain it's a minor release ("MINOR version when you add functionality in a backwards compatible manner"), but I'd like his opinion.

I am pulling this into a release just so I can do further work exploring it. All my tests show it to be backwards compatible.


chore: unused code?

ok this doens't work but I'm confused by this function. maybe something to discuss during a daily dev.


request crawler error

when using request_crawler, it always shows out the error:
UnhandledPromiseRejectionWarning: TypeError: fRequest.getRequestKey is not a function, and the result in request_data.json has no any _postData

same

Has it been solved? How


latte-dock: use postInstall instead of fixupPhase

Description of changes
latte-dock currently sets fixupPhase to perform extra installation steps. This is incorrect, and prevents wrapQtAppsHook from running, which in turn breaks Wayland support:
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Aborted (core dumped)

This PR changes it to use postInstall instead.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Even after this change, it still doesn't seem to work on Wayland, though it no longer crashes...

Even after this change, it still doesn't seem to work on Wayland, though it no longer crashes...

latte-dock seems to be broken on Nvidia Wayland, including on other distros. With software rendering it works fine.


different sealed class with data class + data object cannot compile [Question]

@Serializable sealed class ScrGraphs(
    val route: String,
    @DrawableRes val iconRes: Int? = null,
    @StringRes val title: Int? = null,
    @StringRes val description: Int? = null,
    val usesAuth: Boolean,
    val usesTopBar: Boolean
) {
    /**
     * Companion Object
     */
    @GenSealedEnum(generateEnum = true)
    companion object {
        fun screenWithTopAppBar() = ScrGraphs.sealedEnum.values.filter { it.usesTopBar }
        .map { it.route }.toSet()
    }

    @Serializable data class A(val id: Int = 1): ScrGraphs(
        route = "",
        usesAuth = true,
        usesTopBar = false
    )

    /**
     * Initial
     */
    @Serializable data object Initial: ScrGraphs(
        route = "r_initial",
        usesAuth = false,
        usesTopBar = false
    )
    @Serializable data object Initialization: ScrGraphs(
        route = "r_initialization",
        usesAuth = false,
        usesTopBar = false
    )
}

returned error during compile time:
ScrGraphs.kt:26: Annotated sealed class has a non-object subclass
I need those sealed class structure for Screen Graph (navigation compose) but it won't compile, am I doing it wrong?

The compiler error is expected due to the data class A, since there can be many different instances of A with different arguments. For that reason, it would be confusing to have one specific instance of A in the values list from an enum perspective.
For your use case, it looks like you're trying to infer something about the "type" of screen, of which there would only be 3 distinct types, but there can be an arbitrary number of different instances of some type of screen.
You could try something along the lines of this:
sealed class ScrGraphsType(
    val route: String,
    val usesAuth: Boolean,
    val usesTopBar: Boolean
) {
    @GenSealedEnum(generateEnum = true)
    companion object {
        fun screenTypeWithTopAppBar() = ScrGraphsType.sealedEnum.values.filter { it.usesTopBar }
        .map { it.route }.toSet()
    }

    data object A: ScrGraphsType(
        route = "",
        usesAuth = true,
        usesTopBar = false
    )
    data object Initial: ScrGraphsType(
        route = "r_initial",
        usesAuth = false,
        usesTopBar = false
    )
    data object Initialization: ScrGraphsType(
        route = "r_initialization",
        usesAuth = false,
        usesTopBar = false
    )
}

@Serializable
sealed class ScrGraphs(
    val type: SrcGraphsType,
) {
    @Serializable data class A(val id: Int = 1): ScrGraphs(
        ScrGraphsType.A
    )
    @Serializable data object Initial: ScrGraphs(
        ScrGraphsType.Initial
    )
    @Serializable data object Initialization: ScrGraphs(
        ScrGraphsType.Initialization
    )
}

By making a explicit SrcGraphsType, you can create a enumeration of all different types of screens, and then your specific screen instances have a reference to what Type they represent.


BoneJ reqs

with @rimadoma and @alessandrofelder

[ ] display axes for moments of inertia (https://github.com/imagej/imagej-ops/blob/78ff2373ccc3db101104d279940d15ee3a94318e/src/main/java/net/imagej/ops/geom/geom3d/DefaultInertiaTensor3DMesh.java)
[ ] face coloring by arbitrary features
[x] tree view needs to have child objects (e.g. axes, bounding boxes) that can toggle show/hide
[ ] render ellipsoid factor

scenerygraphics/sciview#92
of that checklist 2 that i'd reprompt about 2:
a Node for axes (e.g. something in between the BoundingBox and Compass)
per-face coloring (one use case was coloring faces based on triangle area)

@mdoube I'm pointing out that this issue exists.


rename "Alpaka" to "Heterogeneous"

After merging the open PRs, I would propose to rename classes/structs/usings from Alpaka to Heterogeneous:
BeamSpotAlpaka
BeamSpotToAlpaka
CAHitNtupletAlpaka
PixelTrackAlpaka
PixelTrackSoAFromAlpaka
PixelVertexProducerAlpaka
PixelVertexSoAFromAlpaka
SiPixelClustersAlpaka
SiPixelDigiErrorsAlpaka
SiPixelDigisAlpaka
SiPixelRecHitAlpaka
TrackingRecHit2DAlpaka
ZVertexAlpaka

Or maybe Portable ?

@makortel what do you think ?

I'm going to think out loud separately the data formats
BeamSpotAlpaka
PixelTrackAlpaka
SiPixelClustersAlpaka
SiPixelDigiErrorsAlpaka
SiPixelDigisAlpaka
SiPixelRecHitAlpaka
TrackingRecHit2DAlpaka
ZVertexAlpaka

and modules
BeamSpotToAlpaka
CAHitNtupletAlpaka
PixelTrackSoAFromAlpaka
PixelVertexProducerAlpaka
PixelVertexSoAFromAlpaka

For data formats the Alpaka postfix would certainly become misleading, because they should become generic-enough to not have a direct dependence on Alpaka. I would maybe try to emphasize their SoA nature.
For modules, the Alpaka postfix is not technically needed because the classes go to Alpaka-specific namespaces anyway. In light of possibly using some other portability technology later, having a generic postfix could be easier ("could avoid configuration changes") or more confusing ("e.g. during migration period half of the modules in a job use Alpaka and other half use something else leading the two sub-DAGs to not talk to each other via device memory"). I suppose I don't have a strong preference to either way.
On Heterogeneous vs. Portable I find the latter more clear, because we seem to be (currently) aiming for portable modules that do all/majority of their work on one "device" (except for the interaction with the framework, launching the work, etc) rather than trying to orchestrate their work to be run on many "devices" concurrently. (i.e. something along "while the full application would be heterogeneous, the modules are portable")

On Heterogeneous vs. Portable I find the latter more clear [...]

... and easier to spell :-)

For data formats the Alpaka postfix would certainly become misleading, because they should become generic-enough to not have a direct dependence on Alpaka. I would maybe try to emphasize their SoA nature.

Here is a breakdown of what we currently have in pixeltrack-standalone:
BeamSpotAlpaka

BeamSpotPOD is the basic type
BeamSpotAlpaka is a wrapper that contains an AlpakaDeviceBuf<BeamSpotPOD>

SiPixelDigisAlpaka

SiPixelDigisAlpaka is a SoA, and uses explicitly AlpakaDeviceBuf<T> for each column

SiPixelDigiErrorsAlpaka

SiPixelDigiErrorsAlpaka is a SoA, and uses explicitly AlpakaDeviceBuf<T> for the data, and AlpakaDeviceBuf/AlpakaHostBuf for the SimpleVector wrapper

SiPixelClustersAlpaka

SiPixelClustersAlpaka is a SoA, and uses explicitly AlpakaDeviceBuf<T> for each column

TrackingRecHit2DAlpaka

TrackingRecHit2DAlpaka is a SoA, and uses explicitly AlpakaDeviceBuf<T> for each column, and AlpakaDeviceBuf/AlpakaHostBuf for the "view"

PixelTrackAlpaka

pixelTrack::TrackSoA is the underlying SoA
using PixelTrackAlpaka = AlpakaDeviceBuf<pixelTrack::TrackSoA>
using PixelTrackHost = AlpakaHostBuf<pixelTrack::TrackSoA>

ZVertexAlpaka

ZVertexSoA is a SoA
using ZVertexAlpaka = AlpakaDeviceBuf<ZVertexSoA>
using ZVertexHost = AlpakaHostBuf<ZVertexSoA>

Looks like migrating to a common approach should be quite high on our TO DO list :-(


Fails if text would not extend to more than one line

Fails if the text is too short and would fit on a single line and doesn't contain any line breaks. Should be fixable with an early return.
Reproduce: Change the provided text to "This is short text" without changing anything else.

Fixed with an early return in the event that the string_to_lines method returns only the string, which has its own early return for this scenario. Failure was in textbox main method which did not handle this string return.


[doc][openai-rest] fix broken link

the old branch looks gone.

API change check
API changes are not detected in this pull request.


Verify docker service commands with the volume plugin

Docker 1.12 and 1.12.1 added up docker service command to create, scale and manage services via docker. We need to verify the volume plugin works seamlessly (especially the --mount option with type=volume) in any of the use cases that docker service is used.

From last week, ran docker engine in swarm mode on two VMs and created a service that uses a persistent volume with single replica, two replicas and in global mode. The single replica works fine with the volume getting created as part of defining the service via "docker service create".
The two replicas scenario also works fine with the two running on the same node.
Global mode is a bit mixed up where one docker host (VM) gets to mount the volume and the second seems to be using a local docker volume. Ideally it would be correct to have the volume plugin create a snap of the persistent volume and each replica uses a snap of the single volume. The plugin needs to be supporting such an interface (Docker needs to define that). The attach_as attribute should allow a non-persistent mode which should allow creating a snap when a service instance runs.
Will update more on the global mode as I investigate this.

Besides not being able to share volumes on container instances across VMs we can showcase using the VMDK driver for cases where a service can migrate across hosts and VMs and still be able to access its data, like this one - https://github.com/codedellemc/labs/tree/master/demo-persistence-with-minecraft-docker.
cc @asomaiah

Created a two seperate swarm setup of three nodes - one master and two worker nodes.
Docker version: 1.12.1
Setup:

All three VMs are on the same host and shared-vmfs datastore.
All three VMs are on the same host and vsan datastore.

Performed following steps across both the setups so that we cover  both vsan and vmfs datastores :
Steps for testing docker service commands:

Created a thin provisioned volume from master vm
Created a service with replica 1
command: docker service create --replicas 1 --name SrvcOnThinVolm --mount type=volume,source=volXXX,target=/vol,volume-driver=vmdk busybox tail -f /dev/null
Verified from VC and ESX - volume was successfully attached to the worker-1
Scaled the replica to 2
Stopped the service on worker-1. Checked in VC and ESX, volume got attached to worker-2 and worker-1 no longer had volume attached.
Tried deleting the volume, but failed as volume was still being used.
Deleted the service running in swarm. Volume was no longer attached to any node.
Removed the volume successfully.

Did the same steps for volumes of different disk-format types: zeroedthick and eagerzeroedthick

For vmfs/vsan datastores, if we deploy a service to the swarm with multiple replicas (--replicas) and --mount flag with type=volume, there will be only one instance of container with state as 'Running' and other instances will be in 'Ready' state.
If the currently running container instance stops or is stopped, another container instance will move from 'Ready' state to 'Running' state since a volume can be attached to only one container at any particular time.

Can you please add output of these commands for e.g. showing nodes, state etc. Please refer to github markdown for formatting console output in comments.

Created a swarm of three nodes - one master and two worker nodes. All three VMs are on the same host and shared-vmfs datastore

root@photon-TX4FfW2ET [ ~ ]# docker node ls
ID                           HOSTNAME          STATUS  AVAILABILITY  MANAGER STATUS
0nu5ndv8jfmby8896nm8v39j4    photon-TX4FfW2ET  Ready   Active
5s7maij1jjybdetc1xed9w2ke    photon-TX4FfW2ET  Ready   Active
azjys9qqaln1nmb9l2et7zoau *  photon-TX4FfW2ET  Ready   Active        Leader

Created a thin provisioned volume from master vm. Volume is detached currently.

[root@sc2-rdops-vm02-dhcp-90-19:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Volume  Datastore     Created By VM  Created                   Attached To VM (name/uuid)  Policy  Capacity  Used  Disk Format  Filesystem Type  Access      Attach As
------  ------------  -------------  ------------------------  --------------------------  ------  --------  ----  -----------  ---------------  ----------  ----------------------
volXXX  sharedVmfs-0  Master-VM-19   Fri Feb 24 19:00:22 2017  detached                    N/A     100MB     13MB  thin         ext4             read-write  independent_persistent

Created a service with replica 1.

root@photon-TX4FfW2ET [ ~ ]# docker service create --replicas 1 --name bb --mount type=volume,source=volXXX,target=/vol,volume-driver=vmdk busybox tail -f /dev/e98bixgk3y3r1pf5a7wevl8u7
root@photon-TX4FfW2ET [ ~ ]# docker service ps bb
ID                         NAME  IMAGE    NODE              DESIRED STATE  CURRENT STATE          ERROR
ccafihmdu3lltohufum0oztms  bb.1  busybox  photon-TX4FfW2ET  Running        Running 2 minutes ago
root@photon-TX4FfW2ET [ ~ ]# docker service inspect --pretty bb
ID:             e98bixgk3y3r1pf5a7wevl8u7
Name:           bb
Mode:           Replicated
 Replicas:      1
Placement:
UpdateConfig:
 Parallelism:   1
 On failure:    pause
ContainerSpec:
 Image:         busybox
 Args:          tail -f /dev/null
 Mounts:
  Target = /vol
  Source = volXXX
  ReadOnly = false
  Type = volume
Resources:

Worker-2 showed a container running. Checked in the VC and ESX, volume was successfully attached to the worker-2.

root@photon-TX4FfW2ET [ ~ ]# docker ps
CONTAINER ID        IMAGE               COMMAND               CREATED             STATUS              PORTS               NAMES
bba78126b92c        busybox:latest      "tail -f /dev/null"   5 minutes ago       Up 5 minutes                            bb.1.ccafihmdu3lltohufum0oztms

From ESX:
[root@sc2-rdops-vm02-dhcp-90-19:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Volume  Datastore     Created By VM  Created                   Attached To VM (name/uuid)  Policy  Capacity  Used  Disk Format  Filesystem Type  Access      Attach As
------  ------------  -------------  ------------------------  --------------------------  ------  --------  ----  -----------  ---------------  ----------  ----------------------
volXXX  sharedVmfs-0  Master-VM-19   Fri Feb 24 19:00:22 2017  Worker-2                    N/A     100MB     15MB  thin         ext4             read-write  independent_persistent

Scaled the replica to 2

root@photon-TX4FfW2ET [ ~ ]# docker service scale bb=2
bb scaled to 2
root@photon-TX4FfW2ET [ ~ ]# docker service inspect --pretty bb
ID:             e98bixgk3y3r1pf5a7wevl8u7
Name:           bb
Mode:           Replicated
 Replicas:      2
Placement:
UpdateConfig:
 Parallelism:   1
 On failure:    pause
ContainerSpec:
 Image:         busybox
 Args:          tail -f /dev/null
 Mounts:
  Target = /vol
  Source = volXXX
  ReadOnly = false
  Type = volume
Resources:

To see the nodes running the service:
root@photon-TX4FfW2ET [ ~ ]# docker service ps bb
ID                         NAME      IMAGE    NODE              DESIRED STATE  CURRENT STATE            ERROR
ccafihmdu3lltohufum0oztms  bb.1      busybox  photon-TX4FfW2ET  Running        Running 7 minutes ago
7xah6o6k80zx7w3opjbubi6um  bb.2      busybox  photon-TX4FfW2ET  Ready          Preparing 1 seconds ago
4p0opkgk3wap01zopnojuc2kz   \_ bb.2  busybox  photon-TX4FfW2ET  Shutdown       Failed 1 seconds ago     "starting container failed: Vo…"
5n0nifwxi8w7b56lf6dsjreir   \_ bb.2  busybox  photon-TX4FfW2ET  Shutdown       Failed 6 seconds ago     "starting container failed: Vo…"
carvjus2thbvekveeob8gxaxb   \_ bb.2  busybox  photon-TX4FfW2ET  Shutdown       Failed 12 seconds ago    "starting container failed: Vo…"
c18z9fbphjlu29ko1247k7qjl   \_ bb.2  busybox  photon-TX4FfW2ET  Shutdown       Failed 18 seconds ago    "starting container failed: Vo…"
root@photon-TX4FfW2ET [ ~ ]#

Stopped the service on worker-2.

root@photon-TX4FfW2ET [ ~ ]# docker ps
CONTAINER ID        IMAGE               COMMAND               CREATED             STATUS              PORTS               NAMES
bba78126b92c        busybox:latest      "tail -f /dev/null"   10 minutes ago      Up 10 minutes                           bb.1.ccafihmdu3lltohufum0oztms
root@photon-TX4FfW2ET [ ~ ]# docker stop bb.1.ccafihmdu3lltohufum0oztms
bb.1.ccafihmdu3lltohufum0oztms

Checked in VC and ESX, volume got attached to worker-1. Worker-2 no longer had volume attached.

[root@sc2-rdops-vm02-dhcp-90-19:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Volume  Datastore     Created By VM  Created                   Attached To VM (name/uuid)  Policy  Capacity  Used  Disk Format  Filesystem Type  Access      Attach As
------  ------------  -------------  ------------------------  --------------------------  ------  --------  ----  -----------  ---------------  ----------  ----------------------
volXXX  sharedVmfs-0  Master-VM-19   Fri Feb 24 19:00:22 2017  Worker-1                    N/A     100MB     15MB  thin         ext4             read-write  independent_persistent

From Master-vm:
root@photon-TX4FfW2ET [ ~ ]# docker service ps bb
ID                         NAME      IMAGE    NODE              DESIRED STATE  CURRENT STATE          ERROR
00abzwlg63vxya0xc9wf5tfyl  bb.1      busybox  photon-TX4FfW2ET  Ready          Ready 2 seconds ago
a1mmdla9etnb89mhxnv4lmqwj   \_ bb.1  busybox  photon-TX4FfW2ET  Shutdown       Failed 4 seconds ago   "starting container failed: Vo…"
750qom1gqcbfhgsi6tqrv8hn8   \_ bb.1  busybox  photon-TX4FfW2ET  Shutdown       Failed 9 seconds ago   "starting container failed: Vo…"
9kzggmo8qgvgjzfkhw8h03w8w   \_ bb.1  busybox  photon-TX4FfW2ET  Shutdown       Failed 15 seconds ago  "starting container failed: Vo…"
eisdpt61yvkz64j50twxablz1   \_ bb.1  busybox  photon-TX4FfW2ET  Shutdown       Failed 20 seconds ago  "starting container failed: Vo…"
4g7y1zb8dl9g3cq74idszsy5d  bb.2      busybox  photon-TX4FfW2ET  Running        Running 2 minutes ago
b98pp7n8xlm3ol1fbpwsg81nf   \_ bb.2  busybox  photon-TX4FfW2ET  Shutdown       Failed 2 minutes ago   "starting container failed: Vo…"
2ea65s9jpqze6ay2dtg7i32tt   \_ bb.2  busybox  photon-TX4FfW2ET  Shutdown       Failed 2 minutes ago   "starting container failed: Vo…"
1x69defsmcy1w9lqky92cpjq4   \_ bb.2  busybox  photon-TX4FfW2ET  Shutdown       Failed 2 minutes ago   "starting container failed: Vo…"
90bl4e2vid78cs7ki1xukrboq   \_ bb.2  busybox  photon-TX4FfW2ET  Shutdown       Failed 3 minutes ago   "starting container failed: Vo…"

Tried deleting the volume, failed as volume was still being used.

root@photon-TX4FfW2ET [ ~ ]# docker volume rm volXXX
Error response from daemon: Unable to remove volume, volume still in use: remove volXXX: volume is in use - [95ade549b9f10c0cdd075488d94a5b4d7e1140504e1e947c1f9e76e6dcd65669, 6bd806eaaa79e12c75928261ed05046bd48c850345a499322ec4200b01e27c01, 7e8d1c5ac5a5a31abc50be1fa06d7242c10e7dabbcfc231880dee78e96b4696d, 0223476e4446da0f7b58be7381d9956aec79c09d3d862f1fca413a6032c4aa36]
root@photon-TX4FfW2ET [ ~ ]#

Deleted the service running in swarm.

root@photon-TX4FfW2ET [ ~ ]# docker service rm bb
bb
root@photon-TX4FfW2ET [ ~ ]# docker service ps bb
Error: No such service: bb

Volume was no longer attached to any node. Verified from VC and ESX.

[root@sc2-rdops-vm02-dhcp-90-19:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Volume  Datastore     Created By VM  Created                   Attached To VM (name/uuid)  Policy  Capacity  Used  Disk Format  Filesystem Type  Access      Attach As
------  ------------  -------------  ------------------------  --------------------------  ------  --------  ----  -----------  ---------------  ----------  ----------------------
volXXX  sharedVmfs-0  Master-VM-19   Fri Feb 24 19:00:22 2017  detached                    N/A     100MB     15MB  thin         ext4             read-write  independent_persistent

Removed the volume

root@photon-TX4FfW2ET [ ~ ]# docker volume rm volXXX
volXXX

@pdhamdhere, Do you have any more comments on this or can this be closed?

Thanks @ashahi1
Added test-needed label to add test.

@ashahi1
The --replica option in swarm is not used to scale a stateful application. Instead, it should used to scale a stateless application. So why do we try to add the test with --replica 2 here? Any specific reason? @ashahi1

@lipingxue I added --replica as I wanted to test fail-over condition. Basically checking if service starts running the second instance if the first one goes down.

As @lipingxue pointed out, the scaled-replicas feature should not be used for stateful applications. Please refer to https://github.com/moby/moby/issues/24089
However, we discussed and agreed that it still makes sense to keep this test scenario. Basically, #927 will focus on failover across different swarm nodes, while this test will focus on failover across different swarm service replicas, even though the volume cannot be attached to two service replicas at same time.


MINOR - Allow pre filled form fields via url params

Allows to pre fill form fields by passing url params with the name of the field

...


Support Optional(...) in Typed List

Hi, I'm implementing this feature. Don't need to review right now.
I have already achieved some kinds of initial success for supporting this feature (see the testcase test_optional_in_python(self), it has already worked, although still flawed).
But I do have a question about _gen_getitem. Why do we need to wrap a not-none item type into an optional type?
https://github.com/numba/numba/blob/c91070592448ebc2243442677f5358988f5feb62/numba/typed/listobject.py#L689-L700
It does confuse me. From the git history, perhaps @stuartarchibald can give me some tips? Indeed, I want to remove this wrapper logic, since I'm trying to support optional item_type natively.

But I do have a question about _gen_getitem. Why do we need to wrap a not-none item type into an optional type?

Optional type is used here as an equivalent to returning nothing (e.g. like return NULL in C).  It can be restructured to make it less confusing when the element type is already an optional type.

Sry, I haven't focused on this feature for more than half a year, thus I will close this. If anyone is interested, maybe you can get some hints from this unfinished draft.


First ugly working implementation

Test plan

Changelog

#5137  👈
main

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

Join @RXminuS and the rest of your teammates on  Graphite


[Bug] Incompatibility with optifine render regions solution?

This bug is already known, but it possible to fix? or should I request oprifabric auto-detects if immersive portals is enabled and disable render regions if the mod is present

It's just fixed https://github.com/qouteall/ImmersivePortalsMod/releases/tag/v0.57-1.16

It's just fixed https://github.com/qouteall/ImmersivePortalsMod/releases/tag/v0.57-1.16


Full text search in python

Hi!
I am wondering if there is a way to do the full text search as described here? https://supabase.com/docs/guides/database/full-text-search?language=js&example-view=sql
Note I am fine on creating the fts column in the table I am searching, just when I am trying to do the actual search.
Note I am trying to use this:
initial_query = initial_query.filter('fts', 'plfts', keyword_query)
Where the keyword_query is either one word or a few strung together by |
If I attempt the same query in the sql in supabase itself it works, but it doesnt work if I try and use .filter and I am not sure what else to use (eg textsearch does not exist on it).
How can I get this to work?
I have considered:

Perhaps there is a different way to format it so I get the actual results here that i have just missed
Perhaps there is a way to send the sql statement directly? (this is in python so all in the back end)

Unsure how to get this to work
Thanks in advance!

You would perform a full text search using the .text_search method.
client.table("movies").select("*").text_search("title", "'The Aveng'").execute()

This has now been documented in the reference docs https://supabase.com/docs/reference/python/textsearch


db/migrate files needs cleanup

On first install I can run db:migrate, but then wanted to make changes to the models and cannot rollback any of monlogues' migrations.
I think on a fresh install it should have a cleaner list of migrate files and possibly an upgrade rake command. What do you think? If you have a good idea on how to separate the upgrade migrations I'm happy to submit a PR...

Or better yet, forget the upgrades, didnt realize how old those files are...

I agree. We could safely start from a clean slate at that stage
On Wed, Mar 1, 2017, 7:44 AM Omri Cohen<EMAIL_ADDRESS>wrote:

Or better yet, forget the upgrades, didnt realize how old those files
are...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jipiboily/monologue/issues/311#issuecomment-283330371,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_jVeMigLoz6F_lTEICOPGLOEVrFHfCks5rhWglgaJpZM4MPmkM
.

I submitted a PR on this, not passing tests for some reason, but feel free to take a look https://github.com/jipiboily/monologue/pull/312


Additional documentation for the HQ camera?

The advanced recipes page section 6.16 could be improved if it has details on the HQ camera.

I'd add the changes to support the HQ camera should probably be finished.
https://github.com/waveform80/picamera/commit/258120a0e917c9d4faead4707e69ebc72f859e5e
Could this perhaps be release 1.14?


Referencing the Handsontable instance hot in hot

Description
Hello,
I'm using "@handsontable/vue": "^4.0.0".
In the Handsontable cell editor, I need to call afterScrollVertically function to load more data from the server.
Meanwhile, I need to reference the Handsontable as a cell editor in Handsontable or reference the Vue instance.
Is there any way to do that?
Steps to reproduce

<div id="example1" class="hot">
  <hot-table ref="hotTableComponent" :settings="hotSettings"></hot-table>
</div>

  import Vue from 'vue';
  import { HotTable } from '@handsontable/vue';
  import Handsontable from 'handsontable';
  let i=0
  new Vue({
    el: '#example1',
    data: function() {
      return {
        hotSettings: {
        	licenseKey: 'non-commercial-and-evaluation',
          data: Handsontable.helper.createSpreadsheetData(4, 4),
          colHeaders: true,
          columns: [
          {
            data: 'serial_number',
            type: 'handsontable',
            handsontable: {
              colHeaders: ['serial_number','name'],
              autoColumnSize: true,
              width: 600,
              height: 220,
              // rowHeights: 33,
              data: [
              	{serial_number:'123',name:'Tommy'},
                {serial_number:'456',name:'Tom'},
                {serial_number:'78',name:'Jane'},
                {serial_number:'786',name:'Roy'},
                {serial_number:'4537',name:'Jhone'},
                {serial_number:'453678',name:'Tiffany'},
                {serial_number:'768',name:'Paggy'},
                {serial_number:'786',name:'Stormy'},
                {serial_number:'115323',name:'Alice'},
                {serial_number:'124563',name:'Sophie'}
              ],
              getValue: function() {
                const selection = this.getSelectedLast()
                console.log(this.getSourceDataAtRow(selection[0]))
                return this.getSourceDataAtRow(selection[0]).serial_number
              },
              // 1、CAN NOT reference vue instance
              afterScrollVertically: function() {
                this.selectCell(i, 0)
                i++
                 if (this.getSelected()[0][0] === 9) {
                 	// CAN NOT reference vue instance
                  this.getData()
                  this.updateSettings({
                  	// CAN NOT reference vue instance
                    data: this.newData
                  })
                }
              },
              // 2、CAN NOT reference handsontable instance
              afterScrollVertically2: () => {
                // CAN NOT reference handsontable instance
                this.selectCell(i, 0)
                i++
                // CAN NOT reference handsontable instance
                if (this.getSelected()[0][0] === 9) {
                  this.getData()
                  this.updateSettings({
                    data: newData
                  })
                }
              }
            }
          }
        ],
        },
        newData: [{serial_number:'new',name:'data'}]
      }
    },
    created() {
    	this.getData()
  	},
    methods: {
      getData() {
        // Some Ajax request
        // this.newData = response
        console.log('GET NEW DATA!')
      }
    },
    components: {
      HotTable
    }
  });

Demo

https://jsfiddle.net/Even6868/51tskngp/65/
Your environment

Vue wrapper version:
Handsontable version: @handsontable/vue": "^4.0.0
Browser Name and version:
Operating System:

Hey @Even-Lau
here's an example https://codepen.io/anon/pen/QVKBLZ?editors=1010 that refers to the instance - in your case, it is this.$refs.hotTableComponent.table

Hi, @AMBudnik
I mean I want to reference the handsontable that triggered by the  Handsontable cell editor or reference the vue instance in the afterScrollVertically  of it. Not the handsontable that shows up when the page initialize.

My problem not solved yet, tag it unsolved, please!

Hi,@AMBudnik
My problem not solved yet. Looking forward to your reply

Hi @Even-Lau
if you have some urgent cases please send the messages directly to<EMAIL_ADDRESS>As far as I understand it right we need to save vue instance first and then we can use it within the app.
In this case, we need to use vueInstance to get access to Vue instance.
The afterScrollVertically2 doesn't exist in handsontable, that it's why we CAN NOT reference the handsontable instance.
https://jsfiddle.net/eco1fv95/

Thanks a lot.

Thanks a lot
hi , i have same problem . do you solve it ?

getActiveEditor().htEditor may be usefull


Custom BIOS file and faster processer

It would be nice to choose a custom BIOS instead of SeaBIOS. It could make it possible for an OS to boot in UEFI mode.
Also, you might need to use a faster processor to run Windows 11 or some other EFI OS.
(please do not use an i386 processer as it is slow)

You can select a bios here: https://github.com/copy/v86/blob/master/examples/basic.html#L15-L20
The processor has no effect on performance. v86 runs instructions as fast as it can.


Storm 2124 show requested cpu mem for each component

Work done by @jerrypeng at Yahoo. I tweaked the UI a bit. Most of the change is in the generated thrift code.
Provides extra columns per component showing requested memory and cpu.

Travis CI terminated because of exceeding the maximum time limit for jobs.
https://travis-ci.org/apache/storm/jobs/162370376
We need to find alternative way to run Integration test.
@raghavgautam I'll disable the integration test now. Please find the way to run integration test in parallel.

@HeartSaVioR I have started a conversation with travis-ci support, to see what we can do. I will update you on the progress.

My tests look good I am +1 once the docs are updated.

Did some manual testing with the UI and everything looks good
+1

@revans2 I added docs and filled in docs for topology and component endpoints.

+1

I merged this into master.  The test failures are unrelated.


Maintenace/tabs to spaces

Hey Chris!
Check out the 2.0 branch-- it's been a little slow coming, but the tabs-to-spaces are already in there. If you'd like to add a caching feature, it should definitely be against that branch as only critical bugfixes are happening against 1.x right now.

Sorry that PR was meant to be opened against a fork. Will try to open a PR against 2.0 after we've done some changes and tested everything properly.


[wip] Add cache for PGVector memory adapter

What does this PR do?
Add cache to the following memory adapters:

[ ] PGVector

[ ] Chroma

[ ] Weaviate

[x] Addresses issue (#455)

Test Plan
Please describe:

tests you ran to verify your changes with result summaries.
provide instructions so it can be reproduced.

Before submitting

[x] Ran pre-commit to handle lint / formatting issues.
[x] Read the contributor guideline,
Pull Request section?
[ ] Updated relevant documentation.
[x] Wrote necessary unit or integration tests.

Closing as implemented in #489


update ingress.md apuVersion of Ingress

The apiVersion of Ingress is update to extensions/v1beta1

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Remember to delete this note before submitting your pull request.
For pull requests on 1.15 Features: set Milestone to 1.15 and Base Branch to dev-1.15
For pull requests on Chinese localization, set Base Branch to release-1.14
For pull requests on Korean Localization: set Base Branch to dev-1.14-ko.<latest team milestone>
If you need Help on editing and submitting pull requests, visit:
https://kubernetes.io/docs/contribute/start/#improve-existing-content.
If you need Help on choosing which branch to use, visit:
https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

hello @farmer-hutao . Just checking if this PR is still in progress? It looks like the current version of the Ingress API is v1beta1 networking.k8s-io. Correct?
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.16/#ingress-v1beta1-networking-k8s-io
Page preview:
https://deploy-preview-16080--kubernetes-io-master-staging.netlify.com/docs/concepts/services-networking/ingress/

@farmer-hutao @kbhawkey Yes, it looks to me like the current version is v1beta1 networkin.k8s.io.

Closing this PR as the current version of the Ingress API is v1beta1 networking.k8s.io.
You can reopen this PR if needed.
/close


variants screen loads and updates correctly

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/63/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/64/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/65/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/66/
Test PASSed.

Merged build finished. Test PASSed.


Country names differ between nomenclature and Scenario explorer

Hi,
when working with the nomenclature and the IIASA scenario explorer, I noticed that when using the nomenclature to convert ISO codes to country names, SK is converted to Slovakia and NL to The Netherlands. However, when the trying to upload the data to the scenario explorer one gets an error since the scenario explorer expects Slovak Republicand Netherlands.

In my dataset I had the countries of the EU28, Norway and Switzerland.
I don't know if there are similiar issues with other countries.

(it would be good if the Scenario Explorer supported ISO codes and automatically transformed them). @danielhuppmann - is there a public repo for the Scenario Explorer I could make an issue on?

Thanks @HauHe for spotting this inconsistency, I'll fix this.
@willu47, we're working on an easily configurable "rename-during-upload" feature, which can then be configured as part of this repo (so that a modeling team can specify "we upload ISO, please rename to full country name and also aggregate from national to EU, ..."). This is to be deployed this month.
We can also work on a feature to display alternative region names in a Scenario Explorer instance, I'll put that on our internal to-do list (and there is a Feedback button in every Scenario Explorer instance for these kind of suggestions).

@HauHe, I fixed the names of the two country in the ECEMF-internal database backend - luckily, this was not an inconsistency in this repo required.
I also re-triggered your failed upload from yesterday (impersonating your user, so you should have received two notifications from our scenario processing service).

Thanks for fixing this @danielhuppmann !
Yes, I got the notifications.


ci: run github work flow only for pull request

currently, GitHub actions are getting triggered for both pull and push request, this commits removes the
action for push events.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

@mergifyio refresh

GitHub App like Mergify are not allowed to merge pull request where .github/workflows is changed.

manually merging the PR as the bot cannot merge it.


Testing

This project is about creating test cases for the tic tac toe game, ensuring all public methods are functioning as they should.

Thanks for the review


chore: bump munit to 1.0.0

Motivation:
Bump munit to 1.0.0

I was waiting for scala-steward to do this :) just to see if it works

You can trigger the action too, as: https://github.com/apache/pekko/blob/main/.github/workflows/scala-steward.yml

Done in #80


a positive feedback..

One of the best article i have ever come across, flawless, thank you..

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

ID: 64575e7c-664c-4d6b-a440-24c91e93def5
Version Independent ID: 17d9481c-a75b-bbfd-1f9a-76fc3d6b2930
Content: Quickstart create an Azure IoT Edge device on Windows
Content Source: articles/iot-edge/quickstart.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

Kudos. Closed


Excess corner window padding

Version: 1.0.132
Platform: darwin 20.3.0
Plugins: none
OS: Big Sur 11.2
There is an unsightly border / excess padding between the terminal and the app window at all 4 corners.

It drives me nuts 😂


simple mysql pool

Always happy about contributions, but I see this ticket got closed immediately so I'll will mark this as invalid for now. We also created a new ticket regarding the "MySQL connection pool" in the meantime, so check out #175 if you'd like to look further into this topic :)


Support CIS 1.6

Waiting for kube-bench to support CIS 1.6:  https://github.com/aquasecurity/kube-bench/issues/666

From the CIS 1.6 requirements meeting:

[ ] Add 1.6 upstream profile

[ ] Add 1.6 for RKE permissive/hardened

Available to test with https://github.com/mrajashree/charts/tree/cis16
Create new clusterRepo with repo https://github.com/mrajashree/charts and branch cis16, it has the new tags for security-scan and cis-operator images

On 2.5-head - latest

Installed repo - https://github.com/mrajashree/charts branch: cis16
Run CIS 1.6 on a hardened cluster and the results are : In a permissive cis 1.6 scan, 7 tests are additionally marked Warn and N/a when compared to hardened profile scan run.

@mrajashree If some scans which pass in hardened scan run pass, they should be marked N/A in a permissive scan run and not warn ?

Hardened scan run

Scan reports:
Scan runs.zip

On 2.5-head - commit id: baf4867

Using cis v2 app v- 1.0.3 and  security-scan RC v0.2.2-rc3
Deploy CIS v2
The following tests are marked "Automated" in the text on a hardened scan report and are marked "manual" in a permissive scan run

4.2.10
4.2.12
5.2.2
5.2.3
5.2.4
5.2.5

@mrajashree why is there this discrepancy ?

@sowmyav27 those tests were original manual and are skipped in the permissive profile because they don't pass on a non-hardened cluster. Hence I didn't add the automation test audit configs to them so they were left manual

@sowmyav27  those tests were originally manual in the upstream profiles. The RKE hardened profile has automated tests for them and they pass on hardened clusters. But they won’t pass on non-hardened clusters. So I didn’t see any point in adding the same automation tests there and then skipping them. Even if we add the same automation test here and change the text from Manual to Automated, their type will still be “skip”

On 2.5-hed - commit id: 182e3de71

using cis v 1.0.3 - and security-scan - v0.2.2-rc4
On a cis 1.5 hardened cluster:


Tags on the local player don't work

Whenever you get targeted in chat messages with things like <t> or <me> the message gets garbled.
For example this is what I get when using prefix <me> suffix

There used to be a checkmark to not include yourself in tagging to workaround this issue but it's gone now, even with "Show for self" property unchecked I get something like this

Ah yes, I've fixed that bug today for v1.7.4.
There is a pull request for the update but not merged yet. Probably get merged today or latest tomorrow. https://github.com/goatcorp/DalamudPluginsD17/pull/532


Malformed Event(s) JSON using 1.10.2 SDK

Expected Behavior
Generated events JSON should be valid
Current Behavior
Generated events JSON is invalid
Malformed JSON string #1
[{
"event_type": "[Amplitude] Deep Link Opened",
"user_id": "vqC3pq54Tj6Od096jMqr7w",
"device_id": "6a974754-0c50-4af7-af7f-3f6bc2b984e5",
"time":<PHONE_NUMBER>413,
"event_properties": {
	"[Amplitude] Link Referrer": "android-app:\/\/org.myapp.app"
},
"user_properties": {},
"groups": {},
"group_properties": {},
"platform": "Android",
"os_name": "android",
"os_version": "13",
"device_brand": "google",
"device_manufacturer": "Google",
"device_model": "sdk_gphone64_arm64",
"carrier": "T-Mobile",
"language": "en",
"ip": "$remote",
"version_name": "local",
"adid": "94d655e5-cd08-41b5-be5c-0f2348d09c39",
"event_id": 69,
"session_id":<PHONE_NUMBER>211,
"insert_id": "a2582cf2-b330-491f-80c1-5f994d0d98e2",
"library": "amplitude-analytics-android\/1.10.2"
}, {
"event_type": "[Amplitude] Deep Link Opened",
"user_id": "vqC3pq54Tj6Od096jMqr7w",
"device_id": "6a974754-0c50-4af7-af7f-3f6bc2b984e5",
"time":<PHONE_NUMBER>414,
"event_properties": {
	"[Amplitude] Link Referrer": "android-app:\/\/org.myapp.app"
},
"user_properties": {},
"groups": {},
"group_properties": {},
"platform": "Android",
"os_name": "android",
"os_version": "13",
"device_brand": "google",
"device_manufacturer": "Google",
"device_model": "sdk_gphone64_arm64",
"carrier": "T-Mobile",
"language": "en",
"ip": "$remote",
"version_name": "local",
"adid": "94d655e5-cd08-41b5-be5c-0f2348d09c39",
"event_id": 37,
"session_id":<PHONE_NUMBER>211,
"insert_id": "e847b4d5-a8db-4f96-bad8-f22b2a83a790",
"library": "amplitude-analytics-android\/1.10.2"
}, {
"event_type": "[Amplitude] Screen Viewed",
"user_id": "vqC3pq54Tj6Od096jMqr7w",
"device_id": "6a974754-0c50-4af7-af7f-3f6bc2b984e5",
"time":<PHONE_NUMBER>510,
"event_properties": {
	"[Amplitude] Screen Name": "Settings"
},
"user_properties": {},
"groups": {},
"group_properties": {},
"platform": "Android",
"os_name": "android",
"os_version": "13",
"device_brand": "google",
"device_manufacturer": "Google",
"device_model": "sdk_gphone64_arm64",
"carrier": "T-Mobile",
"language": "en",
"ip": "$remote",
"version_name": "local",
"adid": "94d655e5-cd08-41b5-be5c-0f2348d09c39",
"event_id": 70,
"session_id":<PHONE_NUMBER>211,
"insert_id": "7c018ed5-ef84-49ec-9edb-36273a4f894b",
"library": "amplitude-analytics-android\/1.10.2"
}, {
"event_type": "[Amplitude] Screen Viewed",
"user_id": "vqC3pq54Tj6Od096jMqr7w",
"device_id": "6a974754-0c50-4af7-af7f-3f6bc2b984e5",
"time":<PHONE_NUMBER>510,
"event_properties": {
	"[Amplitude] Screen Name": "Settings"
},
"user_properties": {},
"groups": {},
"group_properties": {},
"platform": "Android",
"os_name": "android",
"os_version": "13",
"device_brand": "google",
"device_manufacturer": "Google",
"device_model": "sdk_gphone64_arm64",
"carrier": "T-Mobile",
"language": "en",
"ip": "$remote",
"version_name": "local",
"adid": "94d655e5-cd08-41b5-be5c-0f2348d09c39",
"event_id": 38,
"session_id":<PHONE_NUMBER>211,
"insert_id": "82b03424-333b-4e27-9026-717abfbed5a8",
"library": "amplitude-analytics-android\/1.10.2"
}]]

Malformed JSON string example #2
[{
"event_type": "[Amplitude] Screen Viewed",
"user_id": "vqC3pq54Tj6Od096jMqr7w",
"device_id": "6a974754-0c50-4af7-af7f-3f6bc2b984e5",
"time":<PHONE_NUMBER>037,
"event_properties": {
	"[Amplitude] Screen Name": "Screen Name"
},
"user_properties": {},
"groups": {},
"group_properties": {},
"platform": "Android",
"os_name": "android",
"os_version": "13",
"device_brand": "google",
"device_manufacturer": "Google",
"device_model": "sdk_gphone64_arm64",
"carrier": "T-Mobile",
"language": "en",
"ip": "$remote",
"version_name": "local",
"adid": "94d655e5-cd08-41b5-be5c-0f2348d09c39",
"event_id": 72,
"session_id":<PHONE_NUMBER>211,
"insert_id": "20bedb1a-b5bc-4c9e-b58b-fd4ae430878a",
"library": "amplitude-analytics-android\/1.10.2"
}, {
"event_type": "[Amplitude] Screen Viewed",
"user_id": "vqC3pq54Tj6Od096jMqr7w",
"device_id": "6a974754-0c50-4af7-af7f-3f6bc2b984e5",
"time":<PHONE_NUMBER>038,
"event_properties": {
	"[Amplitude] Screen Name": "Screen name"
},
"user_properties": {},
"groups": {},
"group_properties": {},
"platform": "Android",
"os_name": "android",
"os_version": "13",
"device_brand": "google",
"device_manufacturer": "Google",
"device_model": "sdk_gphone64_arm64",
"carrier": "T-Mobile",
"language": "en",
"ip": "$remote",
"version_name": "local",
"adid": "94d655e5-cd08-41b5-be5c-0f2348d09c39",
"event_id": 40,
"session_id":<PHONE_NUMBER>211,
"insert_id": "dca283f0-d4b2-4973-8437-16d42feb2605",
"library": "amplitude-analytics-android\/1.10.2"
}]]

Possible Solution

extra ']' is inserted at the end of the event JSON Array should be removed
Issue seems to be only reproducing with com.amplitude.android.utilities.AndroidStorage implementation

Steps to Reproduce

Setup Amplitude Client

Amplitude(
            Configuration(
                context = context.applicationContext,
                apiKey = AMPLITUDE_API_KEY,
                trackingSessionEvents = true,
                defaultTracking = DefaultTrackingOptions.ALL,
            )
        )

Log events + deep links + screen views
Observe stored events JSON string and sent HTTP payloads

Environment

Device: Android Emulator sdk_gphone64_arm64
Device OS and Version: Android OS 13

Thank you for choosing Amplitude. We are actively addressing this issue and will keep you updated on any progress.

Hi @mariusgherman, did you have this issue with earlier versions or it starts happening after 1.10.2? I set up a local example and send several events. All events were sent successfully. Not sure how you observe stored events JSON string and sent HTTP payloads. Could you elaborate on it?

@Mercy811 unfortunately i have only used the 1.10.2 (i will try with earlier versions to confirm and post my findings).
For HTTP content i setup a localhost simple server that does JSON payload validation and payload logging.
I used it as the SDK Configuration#serverUrl and posted events to it.

@Mercy811 i've just tried with SDK version 1.10.1. I'm not seeing anymore malformed events in the server logs.
However, i've set up a SDK Logger using Configuration#loggerProvider and i'm seeing a few error messages Error when upload event: End of input at character 0 of

Hi @mariusgherman, thanks for your clarification and confirmation. I will investigate more.

Hi @mariusgherman, would like to keep you updated. v1.20.2 starts migrating legacy data. So it’s likely that something wrong in this PR.

Error when upload event: End of input at character 0 of
It is probably caused by getEventsString returning an invalid JSON string.

Thanks for the info you provided. They really help me narrow the bug down. I will continue working on this.

@mariusgherman Did you use the legacy SDK on the same device?

Hi @mariusgherman is it possible you are creating/using multiple instances of the Amplitude()? We noticed the event_id's are out of order 69,37,70,38 which makes us think there could be 2 instances of Amplitude sharing the same storage.

Hi @mariusgherman is it possible you are creating/using multiple instances of the Amplitude()? We noticed the event_id's are out of order 69,37,70,38 which makes us think there could be 2 instances of Amplitude sharing the same storage.

Not the case. We are ensuring that we have a single instance of the Amplitude though usage of Dagger injection scoping.

Thanks @mariusgherman.

logging multiple events at the same time from different threads

I don't think this is the case the provided output. A single instance should maintain a single "latestEvenId" that is used to increate the event_id's. So I think in the multithread case both would read the same value latestEvenId, and the last set lastEventId would win vs having multiple intermixed eventIds.
We noticed each pair has the same event_type, event_properties, timestamp (+/- 1 millisecond), new library, etc - except insert_id. I think, it is highly unlikely that events 37, 38, 40 were migrated from old SDK - in this case they would have legacy library and old timestamps.
Can you please share the Dagger configuration you are using to enforce the single instance of Amplitude?
We also notice a difference in casing (Screen Name/ Screen name) in event_properties for events 72/40, maybe that can help locate where each is being tracked.

@justin-fiedler
these are the relevant files where we have declared the analytics instance and the dagger module where we provide the Amplitude single instance wrapper
class AmplitudeAnalyticsProvider(
    context: Context,
    private val amplitudeConfigProvider: AmplitudeConfigProvider,
    coroutineDispatcher: CoroutineDispatcher
) {
    private val coroutineScope = CoroutineScope(coroutineDispatcher + SupervisorJob())
    private val coroutineExceptionHandler = CoroutineExceptionHandler { _, throwable ->
        Log.w("Amplitude Config", "Failed to configure device id for amplitude analytics", throwable)
    }

    internal val amplitudeClient by lazy {
        Amplitude(
            Configuration(
                context = context.applicationContext,
                apiKey = amplitudeConfigProvider.getKeyValue(),
                serverUrl = amplitudeConfigProvider.getServerUrl(),
                trackingSessionEvents = true,
                defaultTracking = DefaultTrackingOptions.ALL,
                loggerProvider = object : LoggerProvider {
                    override fun getLogger(amplitude: com.amplitude.core.Amplitude): Logger =
                        AmplitudeLogger(if (BuildConfig.DEBUG) Logger.LogMode.DEBUG else Logger.LogMode.INFO)
                }
            )
        )
    }

    fun initialize() {
        coroutineScope.launch(coroutineExceptionHandler) {
            val deviceId = amplitudeConfigProvider.getDeviceId()
            amplitudeClient.setDeviceId(deviceId)
        }
    }

    fun reset() {
        amplitudeClient.reset()
    }

    fun setUserId(userId: String?) {
        amplitudeClient.setUserId(userId)
    }

    fun identify(userProperties: Map<String, Any?>) {
        amplitudeClient.identify(userProperties)
    }

    fun setGroup(groupType: String, groupName: String, groupProperties: Map<String, Any?> = mutableMapOf()) {
        amplitudeClient.groupIdentify(groupType, groupName, groupProperties)
    }
}

class AmplitudeLogger(override var logMode: Logger.LogMode) : Logger {
    override fun debug(message: String) {
        Log.d(TAG, message)
    }

    override fun error(message: String) {
        Log.e(TAG, message)
    }

    override fun info(message: String) {
        Log.i(TAG, message)
    }

    override fun warn(message: String) {
        Log.w(TAG, message)
    }
}

@Module
class AnalyticsModule {

    @ApplicationScope
    @Provides
    fun providesAmplitudeAnalyticsProvider(
        context: Context,
        amplitudeConfigProvider: AmplitudeConfigProvider,
        coroutineDispatcher: Dispatchers.Default
    ): AmplitudeAnalyticsProvider {
        return AmplitudeAnalyticsProvider(context, amplitudeConfigProvider, coroutineDispatcher)
    }
    ...
}

Thanks @mariusgherman, could you add some logging to confirm that only a single instance is created?
internal val amplitudeClient by lazy {
        // LOG 1
        Amplitude(
            Configuration(
                context = context.applicationContext,
                apiKey = amplitudeConfigProvider.getKeyValue(),
                serverUrl = amplitudeConfigProvider.getServerUrl(),
                trackingSessionEvents = true,
                defaultTracking = DefaultTrackingOptions.ALL,
                loggerProvider = object : LoggerProvider {
                    override fun getLogger(amplitude: com.amplitude.core.Amplitude): Logger =
                        AmplitudeLogger(if (BuildConfig.DEBUG) Logger.LogMode.DEBUG else Logger.LogMode.INFO)
                }
            )
        )
    }

    @ApplicationScope
    @Provides
    fun providesAmplitudeAnalyticsProvider(
        context: Context,
        amplitudeConfigProvider: AmplitudeConfigProvider,
        coroutineDispatcher: Dispatchers.Default
    ): AmplitudeAnalyticsProvider {
        // LOG 2
        return AmplitudeAnalyticsProvider(context, amplitudeConfigProvider, coroutineDispatcher)
    }

@justin-fiedler sorry for the late reply
so the code looks now like this
class AmplitudeAnalyticsProvider(
    context: Context,
    private val amplitudeConfigProvider: AmplitudeConfigProvider,
    coroutineDispatcher: CoroutineDispatcher
) {
    private val coroutineScope = CoroutineScope(coroutineDispatcher + SupervisorJob())
    private val coroutineExceptionHandler = CoroutineExceptionHandler { _, throwable ->
        Log.w("Amplitude Config", "Failed to configure device id for amplitude analytics", throwable)
    }

    init {
        Log.w("AMPLITUDE_TAG", "Wrapper instance init hashcode ${this@AmplitudeAnalyticsProvider.hashCode()}")
    }

    internal val amplitudeClient by lazy {
        Log.w("AMPLITUDE_TAG", "Wrapper instance lazy hashcode ${this@AmplitudeAnalyticsProvider.hashCode()}")
        val client = Amplitude(
            Configuration(
                context = context.applicationContext,
                apiKey = amplitudeConfigProvider.getKeyValue(),
                trackingSessionEvents = true,
                defaultTracking = DefaultTrackingOptions.ALL,
                loggerProvider = object : LoggerProvider {
                    override fun getLogger(amplitude: Amplitude): Logger =
                        AmplitudeLogger(if (BuildConfig.DEBUG) Logger.LogMode.DEBUG else Logger.LogMode.INFO)
                }
            )
        )
        client
    }

@ApplicationScope
    @Provides
    fun providesAmplitudeAnalyticsProvider(
        context: Context,
        amplitudeConfigProvider: AmplitudeConfigProvider,
        coroutineDispatcher: Dispatchers.Default
    ): AmplitudeAnalyticsProvider {
        val amplitudeAnalyticsProvider = AmplitudeAnalyticsProvider(context, amplitudeConfigProvider, coroutineDispatcher)
        Log.w("AMPLITUDE_TAG", "Wrapper instance dagger hashcode ${amplitudeAnalyticsProvider.hashCode()}")
        return amplitudeAnalyticsProvider
    }

and here is the logcat output

Hey @justin-fiedler @yuhao900914 @Mercy811 Are there any updates regarding this. I'm facing this issue on 1.10.4 as well and it is impacting our customers.
I don't see any updates on the release notes regarding this fix either.
Will updating the SDK help with this issue?

Alternatively it would be great if we could have an option in the SDK to ignore very old events or even clear the old events from the system. If there already is, could you please let me know, it would be greatly appreciated

@ajay-nagarajan this issue is fixed in our newer SDK versions. We validate the data to make sure its a valid json before we send it over to Amplitude. So this should no longer be happening.


Installation Bitbucket

Flux is not working as described in the docs, I'm trying the command:
flux bootstrap git \
<EMAIL_ADDRESS>\
  --branch=master \
  --path=./

That command is supposed to:
The above command will generate an SSH key (defaults to RSA 2048 but can be changed with --ssh-key-algorithm), and it will prompt you to add the SSH public key as a deploy key to your repository.

It is not generating any ssh public key or at least is not telling me where it is being stored and is not prompting me to add the public key to my repository, this is the response I get after running the command:
► cloning branch "master" from Git repository<EMAIL_ADDRESS>✗ failed to clone repository: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

flux bootstrap git uses SSH agent, is your private key loaded in there? Does the key have access to the repo?

@stefanprodan I had my ssh keys generated and I was using them regularly to connect to my repos, but it seems that you have to use  ssh-add <Path/to/key> in order to get flux to work, thanks for your answer Stefan. Should this be added to the docs? If it wasn't for your answer I wouldn't have been able to fix it because there is no info related to this on forums, I don't understand how I'm the first with this issue.

ssh-add is how you load keys into SSH agent, if you haven't done that, then I guess you type the passphrase at every git push?

Maybe because I've never used passphrases when creating my ssh keys, that's why I've never used ssh-add ...

https://fluxcd.io/docs/installation/#generic-git-server
https://fluxcd.io/docs/cmd/flux_bootstrap_git/

Both of these docs mention an SSH Agent but do not mention the SSH client's default search path.
I think that's clear, but I was still surprised by all of this behavior. I think users generally have the expectation that when an SSH agent is absent, the SSH key search path of the SSH client will be used. (Those are normal expectations, but I'm not saying Flux should implement all this... only that we should probably dispel that expectation somewhere else in the docs.)
Of course Flux never says it will follow a search path, the doc says we use keys if they are available through the SSH agent.
Flux also uses ssh keys with no passphrase (because the key will be stored in the cluster, where there is no human operator to answer a passphrase challenge) – so the documentation should reflect that users may have done this elsewhere also. I'm not sure if the passphrase matters, because the problem is only that the key isn't loaded into the agent.
I wouldn't suggest changing Flux's behavior, as who knows what rabbit other holes are beyond that phrase "the SSH key search path of the SSH client"
Still seems like there is something we can do here to make this less fraught. Glad you have this issue sorted out!
(Should we reopen this, or open a new issue to update the doc?)

Flux also uses ssh keys with no passphrase (because the key will be stored in the cluster, where there is no human operator to answer a passphrase challenge)

We don't use SSH agent in the cluster and we do accept a passphrase, it can be set in the same secret as the SSH key, docs here: https://fluxcd.io/docs/components/source/gitrepositories/#ssh-authentication
We also support passphrase at bootstrap time when you don't use SSH agent, docs here: https://fluxcd.io/docs/installation/#generic-git-server


ToggleGroup.Item asChild does not work for custom components missing ref forwarding

Bug report
Using ToggleGroup.Item and padding a custom component will result in a TypeError when focusing to ToggleGroup with the keyboard.
TypeError: Cannot read properties of null (reading 'focus')
Current Behavior
Here is a stackblitz with the issue. Using tab to focus the first ToggleGroup works fine, but the second ToggleGroup results in a TypeError. All ToggleGroup.Item components use the asChild prop. The first group has a <button /> element as the child, and the second group items have a custom component as a child.
https://user-images.githubusercontent.com/33156025/166530302-29947a41-70c8-431d-8f48-61d60a8a41ae.mov
Expected behavior
I would like to be able to use custom components as children to the ToggleGroup.Item component with the asChild prop.
Reproducible example
stackblitz. In the repro, I use the Styled in the component names to represent custom components that are likely to be used in a production application. Yes, they are missing custom styles, but this is the same component hierarchy used in prod apps. Thanks for understanding!
Suggested solution
Haven't looked too deeply into the source code surrounding this issue. Right now the only workaround is to not use asChild.
Additional context
N/A. Please request if needed. Happy to help.
Your environment
Local env. Different from stackblitz. Issue is in both envs.

Software
Name(s)
Version

Radix Package(s)
react-toggle-group
0.1.5

React
n/a
17.0.2

Browser
Chrome
100.0.4896.127

Assistive tech
n/a

Node
n/a

npm/yarn
npm
8.1.3

Operating System
macOS Monterey
12.3.1

Thanks for the awesome work!

Alright, I looked at the source code for @radix-ui/react-collection, and found that adding refForwarding is needed to solve my initial issue.
I've updated the stackblitz to include the reforwarding. This isn't a bug with the code, but the documentation I believe. What's the best way to update the documentation? Probably on the components that use roving focus. I'd be willing to make a PR. Thanks!

Hi @charkour,
It looks like you resolved your issue.
It's always a good idea with any leaf react component to forward all props and forward ref as they should act transparently like any native element.
With regards to the docs, we are tracking this here: https://github.com/radix-ui/website/issues/269. We're planning to create a dedicated page for asChild where we'll explain more about why you need to forward props/ref (which isn't different from using as prop btw).
Worth pointing out also, asChild is a replacement for as, so it's a bit strange to create your own As and use them both together.

Hi @benoitgrelard,
Thanks for the quick reply. The issue you linked I think would have helped me debug the issue. I'll be sure to ref forward when using the asChild prop.
One thing to note about how my team is using the components: we use asChild in this context to simplify the DOM tree and we use the as prop to programmatically set the semantic element of the custom react component that is a child of the Radix component. We do this because we want to re-use the logic defined in the custom react component, but change the semantic meaning depending on the context it is used in. Is this an incorrect way to use the library? Seems like a clean solution for my team.
Thanks for all the great work!

asChild can be used to change the semantic element too.
I guess it's probably a preference thing, effectively you want this:
<StyledItem As={MyStyledButton}>One</StyledItem>

over this:
<ToggleGroup.Item asChild>
  <MyStyledButton>One</MyStyledButton>
</ToggleGroup.Item>

They both work, I'm just not sure how much the extra abstraction is warranted.
With the extra StyledItem, it's an extra component you need to remember to forward props/ref.
Perhaps this is also a contrived example and in reality your StyledItem is more than what I see here too.
✌

Thanks! I see what you're saying. And yes, my team right now prefers to use that first API. We'll see how the other one fairs.
Thanks again for taking the time to thoroughly review this non-issue. Cheers!


update numpy to v1.22.3

Snyk is reporting v1.22.0 to have a vulnerability.

thank you. requirements.txt has been changed.


Plugin configuration via console command

Description
For automated integration tests it would be good to have a console command to set the plugin configuration. Shopware 5 used to have that (sw:plugin:config:set)
Example
could look like this:
./bin/console plugin:config:set bundleName.config.name someValue

Hello,
thank you for creating this issue.
I have opened a ticket on our Issue Tracker for you. See the ticket link: https://issues.shopware.com/issues/NEXT-6858
Please use this ticket to track the state of your issue.

fixed with https://github.com/shopware/platform/pull/657
will be available in Shopware 6.3


jQuery is not defined after migrating to Laravel 5.4

Laravel Version: 5.4.6
PHP Version: 7.0.13

Description:
After migrating to Laravel 5.4 => javascript bug => ReferenceError: jQuery is not defined
(With Elixir in 5.3 everything works fine.)
This variable is defined in asset/js/bootstrap.js
window.$ = window.jQuery = require('jquery');
in javascript console, i see "$" is correctly defined and a variable name jQuery311052537473254022181 is define...
Seem to be a suffix added ... A bug of wepack config of laravel.mix ???
Steps To Reproduce:
Make a simple javascript closure like
function()({  ... })(jQuery);
then compile assets with command "npm run dev" (same thing with npm run production).
When you try the javascript closure => jQuery is not defined.

Thanks @tabirkeland, that did it for me! I'm no JavaScript wizard, could you explain why $ would be available globally but not jQuery, even though they are both being assigned to window?

I also had this same problem and the above fixed.

I am having the same issue with Framework 5.4.15, but the above fix does not work.

Same issue. Fix does not work =(

Same error in my fresh 5.4.21, I fixed it using:

delete window.$ = window.jQuery = require('jquery') in bootstrap.js;
in webpack.mix.js add
mix.webpackConfig({
resolve: {
alias: {
jquery: "jquery/src/jquery"
}
}
});

This issue is not yet resolved. Not sure why this was closed?

If this is happening inside a child vue component you can add this to that component script and it will work
window.$ = window.jQuery = require('jquery');

@mhulu solution solved my issue.

@tabirkeland not work for me :(
@mhulu please mention file location ? where we add this code.
No idea about this file location.

tabirkeland solution did not work for me either.  I researched Laravel Mix a bit, but didn't want to head down that road just yet.
I found the file /public/js/app.js which appears to contain all of the required js, including jquery.
This appears to be built from /resources/assets/js/app.js by Laravel Mix webpack.mix.js:
mix.js('resources/assets/js/app.js', 'public/js')
.sass('resources/assets/sass/app.scss', 'public/css');
I noticed that in /resources/views/layouts/app.blade.php the
was the last tag in the  tag.
I moved this

All, Mix has been updated extensively since my solution was posted.  I would suggest going with @mhulu solution by modifying your webpack.mix.js and aliasing JQuery.

Yo all. I've just been playing about with this. My problem disappeared when I stopped trying to extract bootstrap's into the vendor's.js.
I'm no js Supremo, but I'm guessing that's where a lot of people's problems might be coming from, it's an obvious file to want to extract, It still looks like a bug to me, but hopefully that'll help someone track it down a bit more accurately.

Yes @Sam-WWHC! When i stopped of try extract the jquery from node_modules path the problem disappeared! Thanks!

You can extract, but you'll need to autoload as well if you're using any scripts that expect it to be available globally.
https://github.com/JeffreyWay/laravel-mix/blob/master/docs/autoloading.md
Be sure to only call autoload once and include everything you need autoloaded. Subsequent calls to autoload seem to overwrite previous calls.

thanks @devcircus ! after adding 'jQuery' to the autoload the extraction works as expected again.
after some recompilations the autoload directive randomly suddenly seemed to make a difference. threw some other errors before that - does webpack cache so hard that it needs several recompilations?
the order in which the extractions are defined doesn't matter, right?
mix.js('resources/assets/js/app.js', 'public/js')
    .extract([
        'axios',
        'blazy',
        'bootstrap',
        'd3',
        'jquery',
        'js-cookie',
        'laravel-echo',
        'localforage',
        'localforage-startswith',
        'moment',
        'nvd3',
        'responsive-toolkit',
        'socket.io-client',
        'vue',
        'vue-echo',
        'vue-moment',
        'vue-strap',
        'vuedraggable'
    ])
    .autoload({
        jquery: ['$', 'window.jQuery', 'jQuery'],
    });

@muhulu
you save my life

Laravel 5.5
@UniquelySimilar  thanks your solution works, it's not good to move js file in the header but it fixed my issue.
The issue is "app.js" loaded at the end of the file and I need some jquery code in register view so I was getting jquery undefined.
I used @mhulu  solution but after changing mentioned files and after refresh the folder not worked maybe I need to rebuild app.js again, I don't know how to rebuild app.js :)

@shahzadthathal just to clarify, I suggested moving the script tag to the top of the body tag, not into the head tag.
However, opinions of where to place script tags can vary, like many other ideas in the programming world:
https://stackoverflow.com/questions/3531314/should-i-write-script-in-the-body-or-the-head-of-the-html
I'm not interested in starting a discussion or debate, as it is off the subject of this issue.  Whatever works for a specific situation.

I found a solution for me with something similar to what you wrote. @UniquelySimilar but i didn't put the script tag for app/js on top of body, i put it at the end. Whatever works.

@RPJ18 thanks for the update.  I recently started working with Vue.js and WebPack, and if doing it again would probably try to resolve this issue with Laravel Mix/WebPack rather than moving the script tag, but it worked for me at the time.

I have been experiencing this issue as well and I found myself the cause of the problem was "defer" attribute in script addition of app.js

this "defer" tag was forcing script to load only after page was loaded. So I simply put the same attribute to the other js file addition as well where I needed jQuery and of course put it below the app.js addition.
This way both script loaded after page has completed loading and as app.js came before, it made jQuery available to my other script.
Maybe helps someone.

None of the above worked for me. I solved this issue by adding the following:
mix.webpackConfig(webpack => {
  return {
	        plugins: [
	            new webpack.ProvidePlugin({
	                $: 'jquery',
	                jQuery: 'jquery',
	                jquery: 'jquery',
	               'window.jQuery': 'jquery'
	        })
	    ]
      };
  })

mix.autoload is supposed to do the same internally but it somehow isn't working as expected for me. This is the only way I could extract Bootstrap without getting jQuery is not defined error.
P.S. found this here: https://stackoverflow.com/questions/49351415/laravel-mix-uncaught-referenceerror-jquery-is-not-defined

I was having the same problem in laravel 5.7, I tried some solution above did not work,
For me adding type="text/javascript" solved the problem.
Before <script src="{{ asset('js/app.js') }}"></script>  did not work.
Now <script src="{{ asset('js/app.js') }}" type="text/javascript"></script> this solved my day, but I don't know why.

Faced the same problem. For me, it was defer loading app.js in the header was creating the issue.
Moved to the footer, removed defer, and added inline script below that. It worked :-)
<script src="{{ asset('js/admin.js') }}"></script>
@yield('local_script')

I fixed by just removing "defer" from script tag.
My laravel 5.7 installation included  <--- this tag, so i removed the defer as i mentioned before by just leaving  like that... It fixed now =)

@steve5287 I too was able to solve the $ reference error by removing defer however, I now have an error about Vue not being able to find #app
Did you run into this same issue?
Also, what is the underlying issue here? It seems rather odd that a vanilla Laravel app would have such difficulty using jQuery in a Blade template.

@steve5287 I too was able to solve the $ reference error by removing defer however, I now have an error about Vue not being able to find #app
Did you run into this same issue?
UPDATE: Just moving things around, and putting <script src="{{ asset('js/app.js') }}"></script> at the end of my layout Blade, before the scripts section has solved both issues. Would still like to know how to get this working without modifying the vanilla templates, if possible.
Also, what is the underlying issue here? It seems rather odd that a vanilla Laravel app would have such difficulty using jQuery in a Blade template.

I also moved the app.js tag at the end of the blade template. Don't know why they put it at the top "head" tag. Still having problems?

None of these solutions work for me :(

Please re-check if you have added defer in your app script or not.
If you have used laravel-mix and added jQuery there make sure your app.js dont have a defer attribute

using Laravel 8 in Dec 2020, same issue here.
I could solve with @tuhin-paul solution
putting
mix.webpackConfig(webpack => {     return {         plugins: [             new webpack.ProvidePlugin({                 $: 'jquery',                 jQuery: 'jquery',                 jquery: 'jquery',                 'window.jQuery': 'jquery'             })         ]
in webpack.mix.js, then npm run watch (or dev).
Also removing "defer" in app.js raw in blade, and moving all of my js after it.

Using Laravel 8, 19-Jan 2021.
tried all of these methods and nothing seem to work. I added @tuhin-paul code to all 4 of my webpack.mix.js and run 'npm run watch' but the error is still there.
I have no idea what to do next. https://ibb.co/ccvjR6n

Using Laravel 8, 19-Jan 2021.
tried all of these methods and nothing seem to work. I added @tuhin-paul code to all 4 of my webpack.mix.js and run 'npm run watch' but the error is still there.
I have no idea what to do next. https://ibb.co/ccvjR6n

This could help!
var ready = (callback) => {
if (document.readyState != "loading") callback();
else document.addEventListener("DOMContentLoaded", callback);
}
then use this function like this
ready( () => {
( function() {
'use strict';
})(jQuery);
});
works perfectly for me


Vesting accounts: Add to existing account

Summary
Allow vesting coins and schedules to be added to an existing account.
Problem Definition
As the recipient of vesting funds, I want them added to my existing account so that I don't have to maintain as many accounts/keys/secrets.
Currently, a new account must be created as a vesting account in order to have vesting coins/schedule. This is problematic because:

The account should be owned by the recipient, but must be created by the granter. This requires the recipient to create new keys and communicate the fresh address to the granter each time a grant is to be made.
A recipient that has multiple vesting grants must manage the keys for all of them which can become cumbersome.

Proposal
Make an enhancement to our fork of Cosmos-SDK that will allow the addition of vesting coin/schedules to existing accounts. This should allow adding vesting coin/schedules to an account that doesn't yet have vesting coin/schedules. This should also allow adding extra vesting coin/schedules to an account that already has vesting coin/schedules. If an account already has vesting coin/schedules, the existing vesting coin/schedules should not be changed when adding the new coin/schedules.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

We should consider using a hold module/encumbrance model for this.

The SDK has some changes coming related to vesting accounts. I think they're renaming them to "locked" accounts (or something like that). But that combined with the changes to the x/auth module, and creation of x/accounts should help us with this issue.


sokol_imgui.h, sokol_nuklear.h: add an image/sampler pair resource type.

The separate image/sampler update in sokol_gfx.h led to a regression for user images in sokol_imgui.h and sokol_nuklear.h: since the respective image handles may only be 32 bits, it's not possible to stash an sg_image handle and sg_sampler handle in there.
Solution is to create an 'image/sample pair object' both in sokol_imgui.h and sokol_nuklear.h, which can then be referenced with a 32-bit handle, for instance in sokol_imgui.h:
simgui_image simgui_make_image(sg_image img, sg_sampler smp);
void simgui_destroy_image(simgui_image);
void* simgui_imtextureid(simgui_image img);

Fixed.


Default reporter results not visible in iTerm2

On iTerm2, the reporter results aren't immediately visible, as shown below.

However, if I highlight the results, this appears.

Not sure if this is an issue with the default reporter, or iTerm, but figured I'd report it.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27488860-default-reporter-results-not-visible-in-iterm2?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github).

Sounds like an issue with the color scheme you are using (probably solarized). You can change the contrast in iTerm as a workaround for now.


translate: rebrand

Fixes #1884

RE: module and method name changes, I don't believe so, because of this part of #1884:

This does not impact the method names but the URLbase as well as readmes, samples and comments.

@stephenplusplus I assumed when they mentioned method names that was for the translate module. For the umbrella package we have a method specifically named translate which is what I'm wondering about

That's funny, I thought it may have meant the reverse, since his note specifically mentioned "method names" and gcloud.translate is one :) But enough guessing, @danoscarmike, can you help us find some clarity on this:

do we change the module name? npm install google-cloud/translate OR npm install google-cloud/translation

do we change the method name? require('google-cloud').translate(...) OR require('google-cloud').translation(...)

@callmehiphop sounds like we're keeping the names. Let's merge this 🐶 ?


Understand how fancy-profiles works with named servers

Named servers save some state about the started server. What happens if we stop and start the named server, but using fancy profiles? What happens using regular profiles?

Currently, you can use various options to start (and that works), but then as soon as they stop, they are 'forgotten'. I had kinda assumed that the options_form code in jupyterhub would somehow 'save' that in state and restore, but I think it does not. Needs investigation to primarily answer the following questions:

When options from profile form are posted, are they saved anywhere?
If they are saved, are they restored somewhere?


addon-jest - Tests not being found

Tests are not being found within the jest-test-results.json file
The issue seems to be this commit https://github.com/storybooks/storybook/commit/7aa23d42f2d185a4996cec37225ba3112f04f4fe#r31119578
Where Storybook is creating a regex structure such as MyTest.((\.specs?)|(\.tests?))?(\.js)?$, however that is then used to test against a path string using includes which will never work.
Expected behavior
Tests to be returned.
Reverting it back to the version of using a RegExp test works as expected.

Duplicate to #4497


Partial Python 2.7 support

Add backports, and implement isprintable
Fixes https://github.com/Ousret/charset_normalizer/issues/1

There are quite a few more py2 str/unicode problems, but this at least gets most of the tests working

I've limited the scope to not include the str/bytes/unicode problem.
My hacks are in https://github.com/jayvdb/charset_normalizer/tree/py2-decoding and tests are at https://travis-ci.org/jayvdb/charset_normalizer/jobs/577912355 - a lot more needs to be done to get that working properly.

ping @Ousret . If you are going to keep Python 2 on the TODO list, I'm happy to keep chipping away at the problem.

Python 2.7 EOL Scheduled January 1st, 2020.
1 Million package dl python 2 as of today but decreasing

So I am going to close that. #1

Fair enough ;-)
We can always revisit this if someone needs py2.


Revert "Added absl::Status support to grpc_closure.error"

Reverts grpc/grpc#27308
Let's not do this before a long weekend.

@ctiller Is this just in case? or do we have an actual breakage by this? I'm fine with either, though.

This is just in case - we've got actual fixes that need to go in, and this seems risky to import at the same time.

Suggest relanding this after the first import on Monday.
@apolcyn can coordinate.


juho/fix practical info

Fixed the link for removing accounts. Before that reformatted lines to 80 chars for easier change tracking.

Thanks Juho!


Error when deploying deploy-azure-mgmt-services/rgWithAzureMgmt

Trying to deploy rgWithAzureMgmt, I get the following error:
400 Client Error: Bad Request for url: https://management.azure.com/subscriptions/...
I am deploying from azcli using:
az deployment create --subscription  --name ASCDeployment2 --template-file .\rgWithAzureMgmt.json --location eastus --verbose
I have tried it specifying --parameters using either one of the two files as well...
Let me know if I can provide more information!
Thanks,
Dave

It appears your cmdlet is incorrect.
Using azcli, the syntax is:
az deployment create --name  --location  --template-file <path to template file. Ie., you should not have --subscription as part of the cmdlet.
Can you retry and let me know that solves the issue?

I have tried it both ways, and it does not. Using subscription has no impact on this at all.

az deployment create --name MSPTestDeployment --location eastus  --template-file .\rgWithAzureMgmt.json
Please provide string value for 'workspaceName' (? for help): msptest
Please provide string value for 'workspaceLocation' (? for help): eastus
Please provide string value for 'automationAccountName' (? for help): shiautotest
Please provide string value for 'automationLocation' (? for help): eastus
Please provide string value for 'rgName' (? for help): msp-rg
Please provide string value for 'rgLocation' (? for help): eastus
400 Client Error: Bad Request for url: https://management.azure.com/subscriptions/subscriptionidremoved/providers/Microsoft.Resources/deployments/MSPTestDeployment?api-version=2018-05-01

I am not able to reproduce the error here, using both latest version of Az modules for both PowerShell and AzureCLI. Can you check that you have the latest version installer, or perhaps try to deploy from CloudShell directly (which should be updated).

Hello!
Apologies for the delay - just got time to pick this up again.
even after uploading the files, and running this from Cloud Shell I am getting the same error.
Using a PowerShell cloud shell (tried it last week with Bash, too)
I am doing this:
Uploaded the files
PS Azure:\> ls
clouddrive  mspDashboard.json  omsWorkspace.json  rgWithAzureMgmt.json

Files are there, set subscription
az account set -s <subscriptionid of test subscription/tenant>
Create deployment:
PS Azure:\> az deployment create --name MSPTestDeployment --location eastus --template-file rgWithAzureMgmt.json
Please provide string value for 'workspaceName' (? for help): MSPTestUFPCLOUD
Please provide string value for 'workspaceLocation' (? for help): eastus
Please provide string value for 'automationAccountName' (? for help): MSPTestUFPAuto
Please provide string value for 'automationLocation' (? for help): eastus
Please provide string value for 'rgName' (? for help): msp-rg
Please provide string value for 'rgLocation' (? for help): eastus

AND - Get error:
400 Client Error: Bad Request for url: https://management.azure.com/subscriptions/subscriptionidremoved/providers/Microsoft.Resources/deployments/MSPTestDeployment?api-version=2018-05-01
Azure:/
PS Azure:\>

Not sure what i'm doing wrong? Any advice?
I did a git clone about 10 minutes before I ran this, so I should have the latest version of the code
I truly appreciate any help you can provide here

OK... Getting a little further. I decided to use --template-uri and point it to the raw JSON on github, and it did not immediately error. I'll give this a shot and report back

...and that did it.
Closing ticket


feat: run doctest as part of running tests, which collects doctests from both the package’s doc strings and the package documentation

So far we’ve had doctest support somewhat configured, but it wasn’t actually used because doctest didn’t run. This PR adds full support for running doctest on both

Python package docstrings, and
.rst files in the documentation.

Tasks to discuss and (maybe) to add to this PR:

[ ] Should doctests contribute to the overall code coverage? If so, we’d probably have to combine/append the results of both coverage runs (docs) for a final report; not sure how this is integrated into pytest (docs).
[ ] We may want to mention doctest support in the README?

Should doctests contribute to the overall code coverage? If so, we’d probably have to combine/append the results of both coverage runs (docs) for a final report; not sure how this is integrated into pytest (docs).

Yes, that would  be a good idea but not sure how to do it neither :thinking:


Fixed console multiline behavior

Fixed the annoying behavior of booish.exe when a command spills on multiple line, i've tested it with delete, history, autocompletion, indent, key arrows and insert.

This definitely looks useful, but at the moment it fails to build under Travis.  Can you double-check and see why?

Hi, it seems a problem with the travis.yml build script, the one i got with the checkout is trying to do a

wget "http://hivelocity.dl.sourceforge.net/project/mono.mirror/MonoFramework-MDK-${MONO_VER}.macos10.xamarin.x86.pkg"

That is failing because hivelocity.dl.sourceforge.net is not available anymore, i'll just do a merge with the actual boo master branch and it should go away.
Anyway i've another issue: at that time i was definitely not a git expert (neither i am right now btw) so while waiting for the pull request to be accepted i added another feature in master (the collectable one referred in commits) and therefore right now i would like to split this pull request in two.
I'll try to see in the weekend what's the best way to proceed, feel free to suggest me one if you have ideas ;)

Closed because contains also different changes, reopened as #141


fix calls to browser stats implementations

this commit fixes #253
also adds example of calling getPeerStatistics to the simple audio/visual demo

Hello @provstevi thanks for pull request.
Can you Rebase to beta or do a new push request.
Beta contain a new build system using grunt.
Thanks again I will review and merge as soon as pull request target beta.

Closing b/c the issue was already fixed in the beta branch.


[release-1.21] support for disabling metrics endpoint from outside of pod

Manual cherrypick required.
#50728 failed to apply on top of branch "release-1.21":
Applying: support for disabling metrics endpoint from outside of pod
Using index info to reconstruct a base tree...
M	pilot/cmd/pilot-agent/status/server.go
M	pilot/pkg/features/pilot.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/features/pilot.go
CONFLICT (content): Merge conflict in pilot/pkg/features/pilot.go
Auto-merging pilot/cmd/pilot-agent/status/server.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 support for disabling metrics endpoint from outside of pod
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

new feature should not cherrypick


remove shortcut aliases?

Hi all? What to do you think about making more strong API with removing aliases (root and d for rootDir, u for use)? In first 2-3 months we can just add warning message of using deprecated options.

Done: 2.0.0

Congrats!


The method 'AddressSearchField' isn't defined for the class '_MapedState'.

Hi, i'm having a problem with this module
    lib/Screens/Delivery/widget/map.dart:1045:58: Error: **'AddressPoint' isn't a type.**
                                (BuildContext dialogContext, AddressPoint point) {
                                                             ^^^^^^^^^^^^
    lib/Screens/Delivery/widget/map.dart:1010:30: Error: **The method 'AddressSearchField' isn't defined for the class '_MapedState'.**
     - '_MapedState' is from 'package:bellava/Screens/Delivery/widget/map.dart' ('lib/Screens/Delivery/widget/map.dart').
    Try correcting the name to the name of an existing method, or defining a method named 'AddressSearchField'.
                          child: AddressSearchField(

It happens when I try to do the flutter build ios
It would be really helpful for me if u can give me any advice

Hi, are you specifing the plugin version in your pubspec.yaml file?
AddressPoint is a type from 1.4.2 version, from 2.0.0 it just uses Address as type.
You can specify the plugin version in 1.4.2 to continue using their types or update to the actual 3.0.3+1 version but it has breaking changes.

Thanks for helping me! This problem got me in trouble since weeks ago
Specifying 1.4.2 version solved the type problem, now AddressPoint is a valid type
But I have this problem now, as I had some time ago too
    /Users/macbook/Documents/developer/bellava/ios/Runner/GeneratedPluginRegistrant.m:10:9: fatal error: module 'address_search_field' not found     @import address_search_field;
It's in GeneratedPluginRegistrant.m, Runner folder:
`#import "GeneratedPluginRegistrant.h"
#if __has_include(<address_search_field/AddressSearchFieldPlugin.h>)
#import <address_search_field/AddressSearchFieldPlugin.h>
#else
@import address_search_field;
#endif`

Mmm i'm pretty sure it happends 'cause you still have the new plugin version in your GeneratedPluginRegistrant.m file.
I have had this problem before, but i don't remember how to solve it, you should try doing a flutter clean or search how to update the ios pod, it's something like run pod install command in ios/ folder.

Yes, that one may be the problem, the plugin version in that file, sure.
I've tested both alternatives (flutter clean and pod install) you gave me but it still doesn't work.
I'll keep on trying with other alternatives.
Thanks for the help, and please tell me then if you remember how u solved it haha

It's a problem in your project with the ios part, the path is from your project and not from the plugin hosted in pub-cache.
Time ago i have had a problem like this and i used flutter clean and pod install and other commands but i can remember that i finally created a new project with the same name and copy and paste all my code 'cause is very hard for me solve issues with gradle (android) and pod (ios).
I know it's not the most professional solve but... it's easy hehe.

Thank you JosLuna98!
I’m gonna test that and I’m pretty sure it’ll solve it.