Term query not issued when value is empty

I am trying to filter out empty strings from my query in order to have a cardinality aggregation not include them. But when I say a NOT term query it is always stripped out before issuing to elasticsearch.
The query I am trying to do is similar to below.
var results = _client.Search<typeParent>
(
    s => s
        .Index(_aliasName)
        .Type("")
        .Query(q =>
            DefaultQueryString(query, op)
            &&
            !q.Term("type", "") //is always removed
            &&
            q.HasChild<typeChild>(et => et
                .Type(EsEventChildTime.GetShortTypeName())
                .Query(q1 => RangeFilter(from, to))
            )
        )
        .Aggregations(aggs => aggs.Cardinality("base_aggs",
            summary => summary.Field(type.ToLowerInvariant())))
        .Take(0)
);

This results in the following query
{
  "size": 0,
  "aggs": {
    "base_aggs": {
      "cardinality": {
        "field": "a.original"
      }
    }
  },
  "query": {
    "bool": {
      "must": [
        {
          "query_string": {
            "query": "*",
            "fields": [
              "a",
              "b",
              "c",
              "d",
              "e"
            ],
            "default_operator": "and",
            "allow_leading_wildcard": true,
            "lowercase_expanded_terms": true
          }
        },
        {
          "has_child": {
            "type": "childType",
            "query": {
              "filtered": {
                "filter": {
                  "range": {
                    "d": {
                      "lte": "2016-02-01T23:59:59Z",
                      "gte": "2016-01-02T00:00:00Z"
                    }
                  }
                }
              }
            }
          }
        }
      ]
    }
  }
}

When it should actually be, or at least my understanding of it should be.
{
  "size": 0,
  "aggs": {
    "base_aggs": {
      "cardinality": {
        "field": "u.original"
      }
    }
  },
  "query": {
    "bool": {
      "must": [
        {
          "query_string": {
            "query": "rm",
            "fields": [
              "a",
              "b",
              "c",
              "d",
              "e"
            ],
            "default_operator": "and",
            "allow_leading_wildcard": true,
            "lowercase_expanded_terms": true
          }
        },
        {
          "has_child": {
            "type": "childType",
            "query": {
              "filtered": {
                "filter": {
                  "range": {
                    "d": {
                      "lte": "2016-02-01T23:59:59Z",
                      "gte": "2016-01-02T00:00:00Z"
                    }
                  }
                }
              }
            }
          }
        }
      ],
      "must_not": [
        {
          "term": {
            "a": {
              "value": ""
            }
          }
        }
      ]
    }
  }
}

Is this expected behavior, if so how do I tell it not to remove empty terms. Or is there another way in which I can do this type of query that I am missing.
I am using the following versions.
Versions
ES: 1.5.2
NEST: 1.5.0

This is by design (see #1264).  An empty value in a term query will trigger the conditionless behavior to kick in.  You can set IsStrict() on the query to disable this feature.

Thanks @gmarz.
I am guessing using Verbatim() does the same thing?

Verbatim() is the right answer here :) Strict() will throw if a query becomes conditionless, Verbatim() sends the conditonless params as is.

Ah, right.  My bad.

@gmarz and @Mpdreamz thanks for the help.
Makes sense, was just in case it was something that I was doing completely wrong.


Remove path module from webpack config on eject.

Fixes #1174

Let's move it right after other imports instead?

Thanks!


Saving and loading wizards showing up

Why are they there???

what does this issue refer to?

clarified the issue with @AlmnoA, if anyone could find steps to reproduce this issue that would be amazing (i cannot).

Thing manager on item prefabs were enemies.


PSF errors with Directory enumeration operator ++

In certain badly formed packages that are using the PSF using VFS pathing, the PsfLauncher might crash with a complaint about directory enumeration with operator ++.
There are three possible cases that need to be addressed:

when finding the config.json file
when finding PsfRuntime.dl
when finding fixup dlls.

I have fixes for this.  A PR will be issued once PR#125 is handled.

Addressed in PR#132

Addressed in replacement PR#137


Error while running rcsfexcitation

I need to make calculations for heavy atoms, so decided to go through examples first.
When I run "rcsfexcitation",  at the step >> Give orbital set, I enter what is in the GraspManual, for example 1 it's 2s, 2p, however, I get the following "Orbitals should be right justified and occupy three positions, redo!
Give orbital set".
Can I overcome it, or that's a bug?

I was not putting a space before 2s, 2p, so it's not an issue anymore and I successfully ran the example 1 as described in the manual.


Optimize ansistrano so sharded paths are used instead of explicit linking in hooks

The problem here is that that would require us to start namespacing files in shared, so .env would be src/.env etc, this along with the fact that we only symlink three files/dirs, makes me think that this is not really a problem. Lets address it when it becomes one. Closing.


Cluster type label

Stories
-As a cluster admin, I want to label clusters based on their type, CAPI or Vintage, in order to use the same alert rules for both CAPI and Vintage clusters by taking their type into consideration.
-As a cluster admin, I want to label clusters based on their type, CAPI or Vintage, in order to automate the creation of client certificates based on the cluster type.
Background
At the moment, there isn't an easy way to identify if a cluster is CAPI or Vintage.
The configuration of CAPI clusters is slightly different than the Vintage ones, for example, the legacy components are not running on CAPI clusters.
The creation of client certificates is different depending on the cluster type, CAPI or Vintage.

Should we be able to use CAPI watch-filter label for this purpose? It will be set only on CAPI clusters.

Which label do we set exactly for the watch-filter?

Questions from @giantswarm/team-rocket

would it not be easier to only label the vintage clusters? This way this does not need to be cleaned up once we migrated fully to capi.

As @nprokopic mentioned earlier, we already label CAPI clusters on AWS and Azure with the watch filter label cluster.x-k8s.io/watch-filter: capi. I also believe we are labeling CAPI clusters with cluster-apps-operator.giantswarm.io/watching so that they work with cluster-apps-operator. So I'd say we already have a way to know if a Cluster is CAPI or not.

we (@giantswarm/team-rocket ) currently don't set the watch-filter label on CAPO clusters
apiVersion: cluster.x-k8s.io/v1beta1
kind: Cluster
metadata:
  annotations:
    cluster.giantswarm.io/description: <CLUSTERNAME> mc cluster
    meta.helm.sh/release-name: <CLUSTERNAME>-cluster
    meta.helm.sh/release-namespace: org-giantswarm
  finalizers:
  - cluster.cluster.x-k8s.io
  - operatorkit.giantswarm.io/prometheus-meta-operator-cluster-api-controller
  - operatorkit.giantswarm.io/cluster-apps-operator-cluster-controller
  generation: 2
  labels:
    app: cluster-openstack
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/version: 0.10.1
    application.giantswarm.io/team: rocket
    cluster-apps-operator.giantswarm.io/watching: ""
    cluster.x-k8s.io/cluster-name: <CLUSTERNAME>
    giantswarm.io/cluster: <CLUSTERNAME>
    giantswarm.io/organization: ""
    helm.sh/chart: cluster-openstack-0.10.1
  name: gario
  namespace: org-giantswarm

why not setting cluster.x-k8s.io/cluster-name as label to identify if it's a CAPI managed cluster or not? This label already exist everywhere as CAPI use this label internally as well.

why not setting cluster.x-k8s.io/cluster-name as label to identify if it's a CAPI managed cluster or not? This label already exist everywhere as CAPI use this label internally as well.

We use that label on vintage clusters as well.

At least on AWS and Azure, I'm not sure about other providers

KVM is always vintage and CAPO, CAPV, CAPVCD are always CAPI.

Nothing to do on this one, as discussed during the KaaS Sync.

@alex-dabija The starting point of this discussion was that it is not easy to template prometheus rules for all CAPI clusters. The idea was

Add a common label to cluster object
Add a new metric based on that
Use that metric in templates

My understanding is that we already have 1 but what about 2? Do we have an item for that?

We re-discussed the topic in the KaaS Sync and we came to the conclusion that this is an issue only for AWS and Azure because it's the only providers where we have the problem. Phoenix is going to update the alert rules based on information we already have for vintage clusters.


Precompiled binaries

... would shorten install time drastically.

I think I can reuse part of the configuration I wrote to compile libui binaries on travis & appveyor.

How are different node versions handled?

How would different node versions get handled?

I'll install (or hopefully it's already installed) nvm and I'll use that to switch node version and build binaries on every version of the node API we support.
I think there are some tools that can help in the process...
New node versions will be included as they are published, we'll have to trigger the CI build doing some commits...

N-API (pronounced N as in the letter, followed by API) is an API for building native Addons. It is independent from the underlying JavaScript runtime (ex V8) and is maintained as part of Node.js itself. This API will be Application Binary Interface (ABI) stable across versions of Node.js. It is intended to insulate Addons from changes in the underlying JavaScript engine and allow modules compiled for one version to run on later versions of Node.js without recompilation. (https://nodejs.org/api/n-api.html)

Not sure if nbind allows that or how N-API is supported by older node versions.

Yes, that would be awesome because it would solve the node version problem, but nbind unfortunately does not support it.  We can try to ask for the feature, but I think it would be really a big job.
Also, I started months ago to do some experiments building a tool similar to nbind but that uses NAPI instead of NAN. But the tool is very rough ATM. If you want to give it a look, I can add you to the private repo where I'm keeping it.
This tool could probably be simplified by only implement features needed by libui-node.
Another advantage (but that will add even more work to do) is that using N-API allows to bind directly to C functions, so we can avoid the C++ wrappers at all, and implement a public API directly in JavaScript.

Related: https://github.com/parro-it/libui-download/issues/3

I start to experiment with a N-API version of the library here: https://github.com/parro-it/libui-napi
There, I setup prebuilt binaries using Travis & AppVeyor. You could see a first release on the repo.
If you try to install the package, the binaries get download and they should not be compiled every time. The same binaries works on Node 9 & 10, and I tested them only on macOS High Sierra.
There is still a problem on CI: when you push a new tag, the publish phase is triggered, and if the build for other commits trigger to early, it try to download partially built binaries and fails.
I'm also rewriting documentation using same tools as proton-native, and add tests using screenshot-tester.
The idea is to continue the experiment implementing windows, multiline entries and boxes,
and then compare this version with a stripped down version of libui-node that only implement the same widgets. I'll compare them based on:

compilation speed
binaries size
memory consumption
easy of development

Until now, I already find some benefits of using N-API

Compilation is really fast.
We have full control on memory management.

The same binaries works on Node 9 & 10, and I tested them only on macOS High Sierra.

Also node 8 & Sierra!


[1.0.0-alpha.1] First element in dropdown always highlighted

Expected Behavior

Normally, items in a drop-down menu are only highlighted when the mouse is over.

Current Behavior

Currently, in a dropdown menu, the first item in the list is constantly highlighted, even when the mouse is hovering other items in the list.

Steps to Reproduce (for bugs)

This bug can be seen in the documentation by clicking "Drop me!" button : http://next.materializecss.com/dropdown.html
Your Environment

Version used: 1.0.0-alpha.1
Browser Name and version: Chrome Beta
Operating System and version (desktop or mobile): Windows 10 Fall creator update

Yes, this is a problem. If we want to use the dropdown to create a submenu element this is a nuisance.

I concur, its frustrating.

This goes into my materialize-css-hacks.scss.
.dropdown-content li:focus:not(:hover) {
    background-color: transparent;
}

Enjoy.

Fixed in 2084239b0d6c247ce01a65997cf449f6b5a0cbc7


Why is @EnableFeignClients needed in spring boot?

Hi,
May i enquire why @EnableFeignClients need to be explicitly added in spring boot in order to use it, since spring boot should be able to detect the presence of the feign dependencies, and  automatically enable it.
This is akin to spring MVC where developer doesn't need to explicitly add @EnableWebMvc in spring boot

There may be performance impact.

Using the annotation allows a more fine-grained control, including allowing to specify only certain clients to be enabled.


Properly send ICMP

This is a bit difficult to do, but in general we should be able to send some decent ICMP packets to the tun interface if something goes wrong. This includes no route to host in case we try to send to some unknown address.

The main thing we want to do here is No route to host and TTL expired. These need special handling, since they are generated by hosts which act as hops usually. Icmp defines that (part of) the original packet is included in the icmp body, but since that packet is encrypted, the intermediate can't send the actual data. Instead it could send the encrypted data, and then the receiver needs to decrypt the data and reassemble the packet.
A basic test shows that TTL based tools such as traceroute/tracepath can work partially by not setting a body and injecting the packet in the regular L3 stream. The problem is that intermediate hops are not properly shown. For this, we will probably need to implement the solution described above.

Currently traceroute works out of the box, though the implementation needs to be cleaned up a lot (right now it's hacked in there as a POC). The main problem is we can't truncate packets which are too large, so in this case we'll have to return just the ICMP with no data. this is not according to spec, but the best we can do as we can't access the raw intermediate data.

Current state: mechanism to support this is done, Time exceeded is implemented. No route to host is still left to do


pod not support Xcode 9

Xcode 9 is not able to migrate swift 2.3

Not sure what you meant. Try updating to the latest Hero if you are using swift 4. Or fallback to 0.3.6 if you are using swift 3.


fetch plugin version from Vis version

hi @felixhayashi ,
please consider this bit of additional automation to your wonderful build script

Hi @kixam,
thanks. for this addition.
Greetings & Best wishes
Felix


The particle emitter can encounter undefined particles which casues it to choke and break

Using version 5.0.7"
I'm afraid I don't have a clean reproduction case for this, but my situation is that I sometimes destroy and remove a particle emitter and construct a new one. At times during this process when a new emitter is first constructed, it can encounter an update loop in the ticker where some particle is undefined. I don't know why the particle is undefined, but the issue shows up starting in the following loop:
for (let particle = this._activeParticlesFirst, next; particle; particle = next)
{

in cases that particle is undefined - the loop eventually crashes at:
if (this.updateBehaviors[i].updateParticle(particle, delta))

Sorry this isn't much to go on, I hope you might have a theory upon seeing this report. Let me know if I can provide any further detail that would be helpful.

So it isn't particle that is null, but particle.transform (inside the particle.scale getter), due to the particle having been destroyed (normally inside destroying the emitter). Because Emitter.destroy() pretty thoroughly clears both the particle references and the behaviors that would allow Emitter.update() to do anything when it runs, it seems that somehow a particle that belongs to a running emitter is getting destroyed rather than a destroyed emitter continuing to run. The other possibility of a destroyed particle finding its way to a new emitter seems less likely, as Emitters do not pool particles at all.
I hope this gives you enough direction to look for a cause within your code. I'm not completely ruling out a bug in the library in some rare condition, but if that is the case it isn't something that I can suss out without a running example.

Hi @andrewstart I was able to identify the problem and resolve it. I was toggling off the emit property for each emitter and later destroying them - but there was a timing issue where I was calling ParticleEmitter#destroy after a parent PIXI container was called with destroy({children: true}). Sorry for the false alarm.


mrc-4400 proxy outpack_server

All GET or POST requests made to routes of the form /outpack/** will get passed straight throught to outpack_server and the response returned. However this has unearthed a bug with the file POST-ing in outpack_server - I think the issue is that when running in docker it can't rename the file on disk as it tries to do here: https://github.com/mrc-ide/outpack_server/blob/main/src/store.rs#L43

LGTM - obviously there's no unit tests for the controller or service, but for something like this where it's all about integration, those are probably of limited usefulness!

Yeah unit tests felt a bit pointless here!


Typechecking of implicit arguments

It's known that implicits are typechecked (after solving) in the static typing environment for them, causing an example such as this one to fail:
module C

assume val p : int -> Type0
let pint = x:int{p x}

assume val f : x:pint -> squash (p x)

let lem () : squash (p 5) =
    (* let x : squash (p 5) = magic () in  *)
    assume (p 5);
    f _

while if we use 5 instead of _, or uncomment the let instead of using the assume, we succeed.
There's also another issue (potentially different, yet I'm not completely sure), which restricts the type of inferred arguments. Take this example, noted by @aseemr and described in Slack and in #57.
assume val req (r:int) :Type0
assume val ens (r:int{req r}) :Type0

assume val foo (r:int) :Lemma (requires (req r)) (ensures (ens r))

let move_requires (#a:Type) (#p:a -> Type) (#q:(x:a{p x}) -> Type)
  ($f:x:a -> Lemma (requires (p x)) (ensures (q x))) (x:a)
  : Lemma (p x ==> q x) = admit () // we can prove this, but it doesn't matter here

let baz () :unit =
  let _ = move_requires #_ #_ #_ foo in
  ()

This fails in the third implicit in baz with error:
./A.fst(6,63-6,64): (Error) Failed to verify implicit argument: Subtyping check failed; expected type (r:Prims.int{ A.req r }); got type Prims.int (see also ./A.fst(4,22-4,27))

This is due to that implicit being inferred #(fun (r:Prims.int) -> A.ens r) which fails since ens's domain requires a x:int{req x} and not just any int. But if we annotate that argument with ens, that is
[...]
  let _ = move_requires #_ #_ #ens foo in
[...]

the thing succeeds.
Is there any way to make the implicit solution take the refined int type instead of just int? That would probably fix this.

Huh, maybe this is just a duplicate of #580..

The first example does seem to be a duplicate of #580 (and it succeeds with the 2-phase checker). The second example is different and seems to be a unification bug. Instead of inferring fun (r:int) -> ens r for q, the unifier could just unify it to ens.


Help when building storybook and deploying on Vercel

I'm pretty new to Storybook, and hope you can help me out here.
I have msw-storybook-addon installed version 1.10.0,  working fine running locally on my machine.
When I try to build the storybook with the storybook build command, everything also seems to work on Vercel. However, when I visit the environment I get this error:
[MSW] Failed to register a Service Worker for scope ('https://ui-seven-kappa.vercel.app/') with script ('https://ui-seven-kappa.vercel.app/mockServiceWorker.js'): Service Worker script does not exist at the given path.

Did you forget to run "npx msw init <PUBLIC_DIR>"?

Learn more about creating the Service Worker script: https://mswjs.io/docs/cli/init

I tried adding
"msw": {
  "workerDirectory": "public"
}

But that did not seem to help.
On Vercel I'm using the Storybook framework preset, that lists storybook-static  as "Output directory".
What is wrong with the above configuration 🧐?

I'm also having same issue when deploying to GitLab pages. Everything works when I build locally and run through http server, or the live server plugin in VsCode. I can download the build file from the pipeline, and run it the same way. but won't run in GitLab pages.  Never had issues with storybook 6.5 and this plugin. But we upgraded to sb7 and now can't get this to deploy properly.

also, my Vite has a base url, that might be causing issue. www.example.com/mockServiceWorker.js will show mock service worker route, but www.example.com/my-app/mockServiceWorker.js wont. @alexbjorlig do you have something like this in your  vite.config setup?

Hi @jimsheen , I troed adding staticDirs: ['../public'] to .storybook/main.js, but this just gives me this error at built-time in Vercel:
Error: Failed to load static files, no such directory: /vercel/path0/public

@alexbjorlig What version of Storybook are you running?

@alexbjorlig @ben-hamel
adding this to .storybook/main.js worked for me
  staticDirs: ['../public'],

https://storybook.js.org/docs/7.4/configure/images-and-assets
I believe you can also do this in package.json scripts, although I didn't try
"storybook": "storybook dev -p 6006 -s ../public"
Hope that helps!

Yeah, it works, but then it breaks custom fonts to work.
We have the following setup derived from this issue:
staticDirs: [
    {
      from: "../public",
      to: "/public",
    },
    { from: "../public/fonts", to: "/fonts" },
  ],

With this, Storybook is unable to find the mockServiceWorker.js file.
So, let's try:
staticDirs: [
  "../public",
    { from: "../public/fonts", to: "/fonts" },
  ],

It does not work.
If we use   staticDirs: ["../public"], , mock service worker works, but font's does not work!!!
What can we do here?

@alexbjorlig
The following works for mocks, but does not work for fonts :') :
  staticDirs: [
    {
      from: "../public",
      to: "/",
    },
    { from: "../public/fonts", to: "fonts" },
  ],

This addon always look the mock on the URL root.

Haven't tried for Vercel but I was getting the same issue in my Docker container. The following setup helped.
// preview.tsx
initialize({
    serviceWorker: {
        url: './mockServiceWorker.js',
    },
});

// main.ts
    staticDirs: [
        { from: '../public', to: 'public' },
        { from: '../public/mockServiceWorker.js', to: 'mockServiceWorker.js' },
        { from: '../assets/fonts', to: 'assets/fonts' }, // Local fonts
    ],

Hey there! I actually publish a Storybook for a personal project in both Vercel and Netlify and I have no issues with MSW there.
First of all, you need to make sure MSW is available via staticDirs in Storybook's config:
import { StorybookConfig } from '@storybook/react-vite'

const config: StorybookConfig = {
  // ...
  staticDirs: ['../public'], // this must match where your MSW file is at
}
export default config

Vercel
I deploy the app in https://mealdrop.vercel.app and Storybook in https://mealdrop.vercel.app/storybook, and the configuration I use is:
// ./vercel.json

{
  "redirects": [
    {
      "source": "/storybook",
      "destination": "/storybook/"
    }
  ],
  "rewrites": [
    {
      "source": "/storybook",
      "destination": "/storybook"
    },
    {
      "source": "/(.*)",
      "destination": "/"
    }
  ],
  "github": {
    "silent": true
  }
}

Netlify
I deploy the app in https://mealdrop.netlify.app and Storybook in https://mealdrop.netlify.app/storybook, and the configuration I use is:
// ./public/_redirects

/storybook /storybook 200
/* /index.html 200


Feature request: Custom libraries

Hi and thanks for providing this very useful plugin!
I have a feature request: Could you include the possibility of adding custom libraries? This is currently not possible at all. We use some custom elements in our projects, so this would be very handy.
The solution in hediet's VS Code plugin is great, where one can configure custom libraries that are available in all diagrams via "more shapes". Settings.json snippet:
  "hediet.vscode-drawio.customLibraries": [
    {
      "file": "somefile.xml",
      "libName": "some name"
    }
  ]

In IntelliJ, this would maybe fit to the plugin configuration in settings?
Kind regards,
Johannes

+1


data:SohamG934

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Thank you for the suggestion, I have updated the concerned icon
On Tue, 7 Feb 2023 at 19:12, Swagata Roy @.***> wrote:

@.**** commented on this pull request.
Sorry to not have mentioned this earlier. Can you please change the
Hashnode icon to SiHashnode, as FaHashnode is not available. Thank You!
In data/SohamG934.json
https://github.com/EddieHubCommunity/LinkFree/pull/4562#discussion_r1098672547
:

"icon": "FaTwitter"

},

       {

"name": "Follow me on LinkedIn",

"url": "https://www.linkedin.com/in/soham-ghadge-17bb18245/",

"icon": "FaLinkedIn"

},

       {

"name": "Follow me on GitHub",

"url": "https://www.github.com/SohamG934",

"icon": "FaGithub"

},

     {

"name": "Follow my blogs on hashnode",

"url": "https://www.sohamghadge.hashnode.dev/",

"icon": "FaHashnode"

⬇ Suggested change

"icon": "FaHashnode"

"icon": "SiHashnode"

In data/SohamG934.json
https://github.com/EddieHubCommunity/LinkFree/pull/4562#discussion_r1098672699
:

"icon": "FaTwitter"

},

       {

"name": "Follow me on LinkedIn",

"url": "https://www.linkedin.com/in/soham-ghadge-17bb18245/",

"icon": "FaLinkedIn"

},

       {

"name": "Follow me on GitHub",

"url": "https://www.github.com/SohamG934",

"icon": "FaGithub"

},

     {

"name": "Follow my blogs on hashnode",

"url": "https://www.sohamghadge.hashnode.dev/",

"icon": "FaHashnode"

⬇ Suggested change

"icon": "FaHashnode"

"icon": "SiHashnode"

—
Reply to this email directly, view it on GitHub
https://github.com/EddieHubCommunity/LinkFree/pull/4562#pullrequestreview-1287121609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX3DW7X7S7MDXUDEGXSQ6I3WWJGMPANCNFSM6AAAAAAUTPV37A
.
You are receiving this because you were mentioned.Message ID:
@.***>


Configurability bugfixes

@wvmitchell I assume these fixes were made to get adminsimple to work with rails 4.x?

Yup, looks like it

did you ever get it running with rails 4?

Ya, the whole project was migrated to rails 4
On Mon, Jun 29, 2015 at 11:10 AM, Jed Schneider<EMAIL_ADDRESS>wrote:

did you ever get it running with rails 4?
—
Reply to this email directly or view it on GitHub
https://github.com/modeset/adminsimple/pull/3#issuecomment-116763763.

--
Will Mitchell
WVM Development
www.wvm-dev.com


Your Environment

Version used: latest
Environment name and version (e.g. PHP 5.4 on nginx 1.9.1):
Server type and version:
Operating System and version: OSX
Link to your project: https://circleci.com/gh/0xProject/0x-monorepo/8193 Unfold the build step

My bad


Port MPI/OpenMP experiments cross-compilation

Before, we'd hold code to cross-compile the workloads for OpenMP and MPI experiments in the respective experiment repositories. This also meant that we had to create a new docker image (inheriting from cpp-sysroot) and add the tasks to build the code there. This leads to a lot of duplication and unnecessary complexity, and also makes it harder to reap the benefits of the improvements we may make to the toolchain (e.g. if we re-introduce SIMD).
In this PR, I move the LAMMPS, Kernels, and LULESH experiments to be submodules of this repository, and add tasks to cross-compile them.

IIRC we split things because:

The original experiments repo was too bloated
The original cpp repo was too bloated
Every experiment requires slightly different build parameters and configuration
Old experiments would break, and we didn't need to maintain them (e.g. the SGD stuff)
Experiment code is not part of the core Faasm platform or toolchain, and has different quality/maintenance requirements

This seems like a step backwards and will end up losing the benefits of splitting. If we carry on down this path, the cpp repo used by anyone who wants to build a C++ function for Faasm, will clone a load of experiment-specific repos for some large projects.
IMO, the solution is to reduce duplication by making the stuff in this cpp repo more reusable. I think the base image is still a good idea, as it allows the toolchain to be reused. However, the configuration around it is still trapped in Python code in this repo. To solve this, we could make faasmtools into an installable pypi package. This means each experiment would have cpp as a submodule, and do pip install -d third-party/cpp/faasmtools.
The experiment builds could then import the build params from faasmtools and edit them as needed.

Yes I agree with you that this is bloating up the CPP repo, that is meant to be only the C/C++ cross-compilation toolchain for Faasm users. At the same time, the current set up makes it hard to track changes/make sure all cross-compiled projects are working and benefit from the latest toolchain config. Also IMO maintaining old experiments is not a big deal if the set up is easy enough to use. As long as we are trying to evaluate Faasm, the more applications we have running the better
Thinking about it, I think the problem with the current set up is that the experiment code is not separated from the cross-compilation code. What about the following:

We create a new repository faasm/sample-applications with the following structure:

README.md
Dockerfile
cpp/
python/
tasks/
    |- lammps.py
    |- lulesh.py
    |- ...
<LAMMPS Submodule>
<LULESH Submodule>

The repository can be used as a standalone project to create .wasm files from a project submodule.
We add a GHA file to cross-compile every project.
In the faasm/cpp repo we add a task to checkout faasm/sample-applications@main and build and install all the projects.
We run this task as part of faasm/cpps GHA and faasm/faasm cpp-funcs job in GHA.
We keep the current ported_libs tests in Faasm, as they don't bloat images. The only difference is that the functions to minimally run ported libraries are not built.

I'm still thinking about this but would like to know your take on it.


Use our version of protoc in the grpc plugin

https://github.com/grpc/grpc/issues/8172

Uh, I suppose? :shipit:

no, nobody really decided more like so far


1.0.4

I'll tag this later this afternoon, @marjan-georgiev is fixing the css then I think it will be a good cut.


[Bug report]: Cannot claim SMR Staking rewards

Platform
Desktop
Version
2.1.4
Description
When claiming SMR rewards in latest firefly shimmer release via Recovery Phrase, the process gets stuck in claiming rewards screen. No error message shown. Followed the guide multiple times, tried from different systems and networks.

Expected behaviour
successful claiming of tokens
Actual behaviour
claiming process is stuck forever
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
No response
Operating System
Windows
Diagnostics
No response
Developer Profile
No
Profile Type
Software (Stronghold)
Staking
Actively staking
Crash Status
Infinite loading symbol
Error Messages
No response
Error Logs
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

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

We apologize for the trouble, this is a known bug. We already have the fix merged https://github.com/iotaledger/firefly/pull/7279 and will be integrated in our next release

you need more acc to reproduced? I have the same bug. Can't clame my shimmer reward too. Waitig for the nex´t release.

you may want to try the beta 2.1.5, worked for me

yes 2.1.5. worked for mee too


Adding source code button for documentation.

Adding an option in sphinx to generate page with source code. It solves the issue: #379

Thanks 🙏 @bruAristimunha
The ci failures are I think unrelated. Would you have time to look into it ? 🙏

Yes professor @agramfort, I can look!

Hello @agramfort!
I looked into the code. One error was related to a small difference in the numeric precision. It probably has been caused by the difference between OS or a macro updated in PyTorch or another library. I increased the threshold from 0.1E-3 to 0.5E-2.
The second and third errors involve implementing a filter bank in the module preprocessing.
In the line 469 there is an overwriting of the info values of a mne object. This action tries to preserve the value of the high and low bands. This type of access is not allowed anymore, according to the documentation of the mne.

I recreated all the information from the data object and redefined the value.

@bruAristimunha I let you investigate the CI issues. 🙏

@agramfort, I think everything works.

Thanks for the effort @bruAristimunha , @gemeinl  what do you think about comment above? If we think it's fine we could merge I guess?

Thanks for the effort @bruAristimunha , @gemeinl what do you think about comment above? If we think it's fine we could merge I guess?

I thank you for the library. If there's anything I can do to contribute more seriously to the library, I'm super available!

@bruAristimunha what is your status? are you currently a student?

I am a second year PhD student in Computer Science, I would love to collaborate with the library and the projects.

Thx @bruAristimunha
Your next PRs will be more than welcome too 🙏

Great thanks so much @bruAristimunha :)


vue-clipboards v1.2.3 text is not allowed to be falsy

Description

Given that the text to be copied is initially an empty string, e.g. (from an  element),
or the value passed to v-clipboard directive is 0, it will throw an invalid value error.

Uncaught (in promise) Error: [vue-clipboards] Invalid value. Please use a valid value.

Repro

https://github.com/FerrielMelarpis/repro-vue-clipboards/pull/1

all right, I get it...😂

It's not fixed


actool: need some functional tests

Major things we would want to test out:

[ ] build
[ ] cat-manifest
[ ] discover
[ ] patch-manifest (many different options (exec, manifest, isolators, ports, volumes, ...)
[ ] validate

I really want to move most of this functionality into https://github.com/appc/acbuild and leave actool as a minimal validator.

@jonboulle Thanks for heading up, will take a look.


Make export types configurable in typescript-graphql-files-modules

I recently started migrating from @apollo/client to react-query, and instead of using a package like graphql-request, I am planning to simply use a fetch wrapper similar to this: https://github.com/tannerlinsley/react-query/discussions/301#discussioncomment-74886
For that, I would like to generate types for named exports from my .gql files. The plugin
@graphql-codegen/typescript-graphql-files-modules almost makes it possible, but it can only output DocumentNode types. I added a config option, to make it possible to use strings as types.
The feature can be expanded/generalized if there is demand for it. I am open for discussion.
Here is a link where I try to explain the problem a bit better:
https://stackoverflow.com/questions/64050929/named-export-multiple-graphql-operation-from-gql-files
A link to a GitHub gist with code example:
https://gist.github.com/balazsorban44/352d5295f604fb4274bfc934937737a1

Great, thank you @balazsorban44 !


A few parser additions

I really wanted to be able to break out of loops and discovered none of it was implemented. When I got to the interpreter for ops and found todo! I gave up for now. I'll probably wait until you sketch out how an op is interpreted.
In the meantime here is parsing for loop, true, false, ==, <, and >. I just followed the patterns in the parser to hopefully get the precedence right for the ops.

There is no test, but that's ok, it would probably fail to get through later phases

bors r+


Disable login button while user is logging in

This makes the login button disabled (and its message changes to "Logging you in...")  while the user is being logged in.
A UI enhancement and prevents this error that can occur if torii attempts to log a user in while they are already logging in (double-clicking the login button will cause this, for example)

(edited to fix gif above)
cc @sandersonet
I'll merge this in when the tests pass.

Awesome.


Don't do console.log.apply(this, ...).

Fixes #255.

Could we re-ping this to trigger the CI?

This looks good, but I'd like to verify that it passes the CI before merging. Perhaps we can rebase off master once #267 is merged (since the log() function uses console.error in that PR)?
Aside from that, I expect this to work on both Windows and *nix.

@ariporad if the merge conflicts can be resolved, I can merge this :+1:

@nfisher: there are none. Merging

I think the only issue is that I changed a console.log to a console.error. Should be an easy fix.

@nfischer: Fixed. git refork to the rescue!

@ariporad Awesome! I'll merge.


finding by association doesn't work

User.js
attributes: {
 groups: {
  collection: 'userGroup',
 }
}

UserGroup.js
attributes: {
 name: {
  type: 'STRING',
 }
}

when i try something like:
User
.find()
.where({groups: [1,2]})
.exec(function(err, user) {
 if (err) {
  res.json({ error: err }, 500);
 } else {
  res.json(user);
 }
});

it gives error:

-error: {
 error: "E_UNKNOWN"
 status: 500
 summary: "Encountered an unexpected error"
-raw: {
 code: "ER_BAD_FIELD_ERROR"
 errno: 1054
 sqlState: "42S22"
 index: 0
}
}

however, i do really need to search via blueprints like posting this to find method of the user controller:
{
 "where": {
   "groups": [1,2]
 }
}

it also gives server error 500 without details.
according to sails issue 124 which was the post about associations, the examples about finding through collections was like that: https://github.com/balderdashy/sails/issues/124#issuecomment-21690561
sorry if this is a sails issue and i posted this to wrong place.
using sails v0.10-rc7 and waterline-v0.10-rc13
bug or error on my side ?
thanks

it still doesn't work for me

This isn't working for me either in Sails v0.11.0
Is this a verified bug? Or just an unimplemented feature?

@mkeremguc, @AnalogJ, which adapters are you using?
Regarding .where({groups: [1,2]}), are 1 and 2 primary keys?

@dmarcelino, mysql and mongo
and yes, primary keys

@dmarcelino I'm using postgres

I'm just thinking... I'm not sure this functionality is in the spec, at least I don't recall it when I implemented sails-orientdb and I don't remember seeing it in the docs. Can someone PR a test to waterline-adapter-tests? That would help towards figuring out which adapters are broken/don't implement this and then we could work on getting it fixed/spec'ed.

there are lotsa features that is not in the docs either. however, that feature may not be implemented as @dmarcelino said. i was just referencing https://github.com/balderdashy/sails/issues/124#issuecomment-21690561 at the time.
even though it not be implemented yet, i would still ask how you search/find/filter by association values ? custom in-memory functions would not be efficient for large data sets.
btw, it gives empty array via blueprint at the moment.

This often relies on using native (mongo adapter) or query (sql adapters) adapter methods, which allows you to make queries directly through the database wrapper.

I believe for something like this to work (without resorting to .native() or .query()) we'll need the .populateKeys() feature being discussed in https://github.com/balderdashy/waterline/issues/532#issuecomment-97515874 or wait for #266.

Closing this as duplicate of #266, please re-open if you believe this is a different feature.


Alacritty crashes if the mouse is placed where the window will open.

Hyprland Version
Hyprland, built from branch  at commit ed3d5053b23d2b725cda507cb5fcc9e9a2f35ba9
Bug or Regression?
Bug
Description
I usually use wezterm, but it broke a few days ago due to a change in Hyprland that supposedly was done to make the latter more compliant with the spec. Since I know jack about that I decided to use alacritty in the meantime until wezterm could get fixed.
But I get a strange crash if I attempt to start alacritty. I've attached the crash report with RUST_BACKTRACE=1.
I saw that a new bug report was filed because of the wezterm crash, and speculations that these could be related to fractional scaling. Judging by the crash error I got that might be the case? I hope this is to any help.
What's really weird is that I actually can start alacritty if I move my mouse over to the edge of the screen where I have gaps. As long as my cursor isn't placed where the alacritty terminal will spawn it appears to run fine o_o
I'm running Nixos unstable is that is useful to know.
How to reproduce
Try to start alacritty via wofi or from another terminal such as kitty. If the mouse is placed where alacritty will spawn it will crash. If you move the cursor aside it appears to spawn fine.
 It stopped working at all for a bit regardless of where I positioned my mouse, and now after moving it to other workspaces and focusing other windows for a bit I could spawn alacritty even if my mouse was over the place it would spawn. Then after doing the same little dance it started crashing again.

 I'll leave it open for a while for visibility in case the information is useful to the maintainers.

that's an alacritty thing, not an error and unrelated


[P1] Pass in correct ApiVersion to xxxRestClient

Different xxxRestClient may have different api versions, need to figure out long term solution.

fixed.


Bug in network connectivity inference sequence

Network paths are constructed from logical segments, each of which represents a subpath between two subnets through a single gateway device. These segments come in different types, which embody routing restrictions in the set up, and depend on whether the gateway just connects to the subnets, or provides one or both subnets.
Where a device provides a subnet, the asserted relationship is Subnet-providedBy-Gateway, so there is no Gateway-connectedTo-Subnet relationship. This is added by construction pattern HprLS+c, and used in subsequent patterns that create the segments. Then later on, the network path construction sequence uses these segments, but doesn't create paths where the segment is of a type that normally doesn't allow connections to be routed through the gateway.
Most logical segments are created by a series of patterns that take into account where the subnets on each side of the gateway may be accessible. This ensures that we don't get segments connecting two subnets via a mobile device (e.g., a laptop) if the laptop cannot access both subnets from the same physical location. The only exception to this is if one of the subnets is the Internet, which is assumed to be accessible from anywhere.
This creates a problem for logical segment generation between a cellular network backhaul (the core network that connects cells together) and other networks to which it is connected. The problem arises because the core router and backhaul network aren't in any location that is likely to be represented in the system model. The reason is that these assets are inferred to exist to support the cellular network, and in most situations we don't need to worry about attacks on them or controls to counter those attacks. (At least for public cellular networks, where they are secured by the cellular network operator - see issue #152).
Because it has no location, the usual patterns won't find logical segments for routes to or from the backhaul network. To handle this, the construction sequence that creates the inferred backhaul network, base stations and radio access networks (cells) associated with each asserted cellular network also includes segment creation patterns. The problem is that two of these (L3cCrC+OSg, CrCcL3+NSg) depend on Gateway-connectedTo-Subnet relationships added by construction pattern HprLS+c, but it is part of the later sequence.
Result: we don't get logical segments for routes into and out of the backhaul network, except from/to the Internet.

Strictly not related to this is the fact that the existing patterns for constructing cellular network backbone and access networks do not handle the possibility that the system modeller user may have included them explicitly in their model. In that situation, routers within the cellular network do have locations, so the normal segment generation patterns should work correctly.
This should be taken into account when fixing the logical segment generation sequence, or we may get duplicate segments where the user has included any of the infrastructure explicitly (as asserted assets). This implies we should also fix the patterns that create the backbone and access networks so they are not triggered if those assets are asserted.

First step in solving #151 is to create a set of test cases.
Issue #152 affects routing from external networks via the backbone router and thence via base stations into RANs. In issue #151 we are interested in other devices connected to the RAN that are themselves providing other networks. Tests for issue #151 can therefore be based on one of the test cases for #152, but with an extra subnet connected via one of the phones or base stations.
Issue-152-Test-01c: has a public cellular network '5G' covering Spaces 1 and 2 (plus the World), with an asserted router in Space 3 connected to the Internet and providing the backbone network, and an asserted base station in Space2 providing the RAN there. In Space 1 there is a phone connected to 5G, and in Space 2 there are two such phones. There is a laptop connected to the Internet in the global public space 'World'. The devices run clients and services whose connections lead to modelling errors if no network path exists between their hosts, providing a convenient means to detect which network paths exist and support connections.
Test cases for issue #151 are based on this:

Issue-151-Test-01d: same as Issue 152-Test01c, but with a WiFi subnet provided by a another router in Space 1. The phone there is connected to the WiFi, as is another laptop running an extra client and service.
Issue-151-Test-01e: same as Issue 151-Test01d, but with an asserted base station in Space 1 providing the WiFi and the 5G RAN in Space 1, instead of having a separate router providing the WiFi.
Issue-151-Test-01f: same as Issue 151-Test01d, but with the WiFi subnet in Space 1 provided by the phone there, instead of a separate router.
Issue-151-Test-01g: same as Issue 152-Test01d, but with no WiFi and router in Space 1. Instead, the laptop in Space 1 is paired with the phone via bluetooth.
Issue-151-Test-02d: same as Issue-151-Test-01d, but the cellular network is private rather than public, with asserted coverage of spaces Space 1 and Space 2.
Issue-151-Test-02e: same as Issue-151-Test-01e, but with a private cellular network and asserted coverage.
Issue-151-Test-02f: same as Issue-151-Test-01e, but with a private cellular network and asserted coverage.
Issue-151-Test-02g: same as Issue-151-Test-01e, but with a private cellular network and asserted coverage.

Initial test results with code incorporating fixes for issues #152 and #154 reveal two problems:

an oversight in the fixes for issue #152: the fix includes a construction pattern sequence generating logical path segments via the backbone router into and out of the backbone network, and via base stations into and out of the RANs, but not via devices on the RAN and other subnets they may provide or be connected to.
the known problems arising from issue #151.

Construction pattern resequenced, and this took care of the problems arrising from this issue #151.
Unfortunately, the resequencing introduced some new problems which then had to be fixed:

[x] Bugs in the original patterns to insert routes from one device through a paired device via their USB/Bluetooth connection to another network (issue #157).
[x] Interference between patterns to deduce network accessibility and those for inserting localised WiFi hotspot subnets (issue #161).

These are now also fixed.
There are still some outstanding concerns related to our assumptions about cellular networks (issue #152), and assumptions about network accessibility (issue #155, which are not fully addressed by fixes for #161). However, these are unrelated to the construction pattern sequencing issue raised here, so this issue can now be closed.


Unique Summary Config ID

Add a UUID to each summary config. Prevents warnings about duplicate keys and enables reordering code.

Giving the configuration for each report summary a unique ID eliminates duplicate key warnings Vue was printing due using the report ID. Reordering the report summary cards will also require a stable ID, because the array index will be changing as the card moves.


pkeys are immutable on OpenSSL 3.0

When trying to use the cli tool with create-cluster, I get the following error:
Waiting for server msostream-cpx11-master1 to be up...
#<Thread:0x00007f00a1bf54c0 /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/k3s/cluster.rb:577 run> terminated with exception (report_on_exception is true):
/usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/kex/ecdh_sha2_nistp256.rb:21:in `generate_key!': pkeys are immutable on OpenSSL 3.0 (OpenSSL::PKey::PKeyError)
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/kex/ecdh_sha2_nistp256.rb:21:in `generate_key'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/kex/abstract.rb:32:in `initialize'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/algorithms.rb:437:in `new'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/algorithms.rb:437:in `exchange_keys'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/algorithms.rb:245:in `proceed!'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/algorithms.rb:184:in `accept_kexinit'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:210:in `block in poll_message'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:190:in `loop'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:190:in `poll_message'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:225:in `block in wait'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:223:in `loop'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:223:in `wait'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:90:in `initialize'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh.rb:251:in `new'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh.rb:251:in `start'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:79:in `ssh'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:58:in `block (2 levels) in wait_for_ssh'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:57:in `loop'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:57:in `block in wait_for_ssh'
	from /usr/share/ruby/timeout.rb:107:in `block in timeout'
	from /usr/share/ruby/timeout.rb:36:in `block in catch'
	from /usr/share/ruby/timeout.rb:36:in `catch'
	from /usr/share/ruby/timeout.rb:36:in `catch'
	from /usr/share/ruby/timeout.rb:123:in `timeout'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:52:in `wait_for_ssh'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/k3s/cluster.rb:577:in `block (2 levels) in wait_for_servers'
/usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/kex/ecdh_sha2_nistp256.rb:21:in `generate_key!': pkeys are immutable on OpenSSL 3.0 (OpenSSL::PKey::PKeyError)
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/kex/ecdh_sha2_nistp256.rb:21:in `generate_key'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/kex/abstract.rb:32:in `initialize'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/algorithms.rb:437:in `new'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/algorithms.rb:437:in `exchange_keys'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/algorithms.rb:245:in `proceed!'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/algorithms.rb:184:in `accept_kexinit'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:210:in `block in poll_message'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:190:in `loop'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:190:in `poll_message'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:225:in `block in wait'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:223:in `loop'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:223:in `wait'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh/transport/session.rb:90:in `initialize'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh.rb:251:in `new'
	from /usr/share/gems/gems/net-ssh-6.1.0/lib/net/ssh.rb:251:in `start'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:79:in `ssh'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:58:in `block (2 levels) in wait_for_ssh'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:57:in `loop'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:57:in `block in wait_for_ssh'
	from /usr/share/ruby/timeout.rb:107:in `block in timeout'
	from /usr/share/ruby/timeout.rb:36:in `block in catch'
	from /usr/share/ruby/timeout.rb:36:in `catch'
	from /usr/share/ruby/timeout.rb:36:in `catch'
	from /usr/share/ruby/timeout.rb:123:in `timeout'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/utils.rb:52:in `wait_for_ssh'
	from /home/fgaertn/.local/share/gem/ruby/gems/hetzner-k3s-0.5.6/lib/hetzner/k3s/cluster.rb:577:in `block (2 levels) in wait_for_servers'

I use version 0.5.6.

Hi, I am not sure about this with OpenSSL 3.0. I haven't come across it. I'll take a look when I have time. In the meantime you can use the Docker image so you don't need to worry about the Ruby setup.

Hi, can you please add more details on how you set up Ruby?

I installed CRuby with the official Fedora instructions https://developer.fedoraproject.org/tech/languages/ruby/ruby-installation.html

@vitobotta BTW while using you image in podman as workaround we often face it hangs while servers all up:

Interrupting and restarting it helps as all server are up and can continue with deploying k3s to first master.

Are you consistently able to reproduce this issue? Sorry for the long delay, I have been busy with work.

@vitobotta Yes we did. As a workaround using currently podman with your image.
But love to return to Gem installation on Ubuntu 22.04 LTS with OpenSSL 3.0.
We saw other projects shifting to GnuTLS. But it's a refactoring either way.
Let us know via PM if we can assist you on your awesome work :smile:

Hi @krauthosting, yesterday I released a new version (v0.6.1) with new standalone binaries that can be used directly on macOS and Linux without having to set up a Ruby environment or use the Docker image, so I suggest using those binaries moving forward as it's easier to use the tool this way. I am closing this one for that reason but feel free to reopen if you have comments about it.

@vitobotta Couldn't fully test it yet due to #103 but simplifies dealing with dependencies a lot :+1:

Yeah I will be looking into that issue as soon as I can.


Downloads and popup panels font size too large

It's me again haha. Love the theme! But something I noticed a few days ago is the downloads popup font size is huge on my Mac. See screenshot

Bigger is better though, right?!?!?
I based the dimensions on the Material list spec (see two-line list) but I suppose it is a bit on the large side compared to everything else. If it were a pure Material website it would look fine but because it's part of the browser it's inconsistently sized compared to the rest of the UI.
It's 72px tall at the moment. I can shrink this down to say, 48px and reduce the font size to match.

Ha! I think that'd be perfecto 👌

Decided to go ahead and adjust the layout code substantially - uses flex layout over -moz-box to make it easier to force element sizes and centre elements without hacking margins. Height is reduced to 48px, font size is reduced from 120% and 100% to 100% and 85%, and padding has been adjusted.

Beautiful, it looks great. Thanks, @muckSponge !

No problem, thanks for your input!


Docs

In /docs subfolder, I'll include it into our Gitbook collection

Just pushed the commits - done. Live at https://docs.boltz.exchange/v/boltz-btcpay-plugin


Agents clip into obstacles when image rotation is enabled

While custom obstacle avoidance behaviour can be implemented by querying the Obstacle Intersections API, introduced in 13ecfde0b858c66b42807bc324424f1cbe25f92b, the built-in wandering behaviour currently still utilises a broken obstacle avoidance algorithm.
To avoid sharing the bonus solution for assignment 0, this bug will be fixed in a subsequent v0.2.2 release this Friday.

Turns out that a flocking-inspired obstacle avoidance system (utilising the Obstacle Intersections API) comes with quite a big performance hit. As obstacle avoidance isn't required for the Aggregation and Fox-Rabbit assignments, the automatic obstacle avoidance implementation will be delayed for a future release.

For anyone wanting to experiment with a better obstacle avoiding implementation, feel free to replace the built-in change_position method with the following code:
def change_position(self):
    prng = self.shared.prng_move
    rand_x = prng.uniform(-5, 5)
    rand_y = prng.uniform(-5, 5)

    # Return immediately if we're not supposed to move.
    if not self._moving:
        return

    # Pac-Man-style teleport to the other side of the window if needed.
    self.there_is_no_escape()

    steer = Vector2(0, 0)

    # Feel free to experiment with the "scale" option.
    for pos in self.obstacle_intersections(scale=5):
        difference = pos - self.pos
        steer += -difference.normalize()

    # Apply the obstacle avoidance steering vector
    self.move += steer

    # Apply the random movement steering vector
    # Feel free to experiment with the weight
    self.move += Vector2(rand_x, rand_y) * 0.1

    # Finally, cap the movement speed if we're trying to go to fast.
    length = self.move.length()
    if length > self.config.movement_speed:
        self.move = self.move.normalize() * self.config.movement_speed


Vote resolver allows for multiple votes if you submit too many requests in a short time

The current vote resolver checks the database whether you've already voted on something, and if you have, cancels your vote, which changes the score of the item you are voting on. If you vote again before the database operation completes, then the resolver is going to cancel your vote twice, which means that the score decreases by twice your voting power. This allows you to arbitrarily manipulate the scores of various items. This seems quite bad and we probably want to fix that.

Can you specify how to recreate the bug? Is it just by clicking the upvote button rapidly?

 You can take a
look at our Vulcan fork to figure out the differences in implementation:
https://github.com/LessWrong2/Vulcan
On Fri, Oct 19, 2018 at 11:33 AM James Wrubel<EMAIL_ADDRESS>wrote:

There's definitely something going on with the vote module but I'm not
seeing the behaviour as described in this issue. When I take a fresh
install of example-forum, create an account, and upvote a post, even though
the code seems to indicate that my vote should be canceled if I try to
upvote a post, the application appears to just count upvotes indefinitely:
https://cl.ly/7155215d0564
I've traced out the code and I can't determine exactly where or how this
is happening due (I assume due to my unfamiliarity with graphQL) but what I
think I am seeing is on the second click of the upvote button,
currentUserVotes
https://github.com/VulcanJS/Vulcan/blob/devel/packages/vulcan-voting/lib/modules/vote.js#L140
is being correctly emptied, but the mutation to add a vote is still running
which causes the client data to be overwritten by new props passed down.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/VulcanJS/Vulcan-Starter/issues/31#issuecomment-431455062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIq25fFXT4txO7hZvjNUSRB1ULRgE58Dks5umhk6gaJpZM4SSbdV
.

Likely related to this: https://vulcanjs.slack.com/archives/C02L990AF/p1538612081000100

In particular, vote.js has a call to:
await Connectors.delete(Votes, {documentId: document._id, userId: user._id});
But that breaks now, because that gets translated to
{ userId: <userId>, _id: <documentId> }
Which is importantly different, and basically breaks all the clearVote functionality

@Discordius I was able to extract what I needed from your repo and I got voting working correctly - thank you! It was quite a lot of changes and they're in the voting package, not Vulcan-Starter. Still I have what I changed in a single commit so I'm happy to add it as a PR, even if it's just for someone to take a look at and re-implement properly.

@jwrubel Could you send a link to your commit (if it’s public)?

Good idea - there's no reason not to make it public so I just opened it. I had originally started trying to keep individual commits but that got too hard, so these four commits should be enough to correct voting functionality: 1 2 3 4 . That last one is the big one. To be honest I haven't really traced through all of these changes to understand how they work; It is definitely possible some of these are not needed. But I can confirm these worked  in my implementation. I'm happy to try and assist if you run in to issues implementing these changes, to the extent I'm able.

Quote from Halima Olapade on Slack that might explain this issue:
"I think i figured out why the inbuilt voting is breaking. It's cause the Vote collection schema has a field called "documentId" but "documentId" seems to be some kind of reserved identifier. As a result this query always fails: https://github.com/VulcanJS/Vulcan/blob/devel/packages/vulcan-voting/lib/modules/vote.js#L52 so the system can't tell that there's a previous upvote that should be annulled""


Support iOS 13's new lifecycle paradigm

iOS 13 introduces a new lifecycle paradigm with iOS 13.
According to @DavidPhillipOster, a full iOS 13 app will just get the UIScene lifecycle notifications, running on either iPhone or iPad. Before iOS 13, it will just get the UIApplication lifecycle notifications,  but if it has a SceneDelegate, but does not have the dictionary in its Info.plist it will get both sets of notifications on iOS 13.
In GDT, getting multiple background/foregrounding calls is ok, so I'm solving it with #3520
Other resources:
https://stackoverflow.com/a/56508769/361918
Reach out to me (haneym@) for additional context and example fixes if needed.

NOTES:

adopting of background/foreground calls for auth should be pretty straightforward
auth will have to adopt new way of handling open URL actions using UISceneDelegate which implies implementation of UISceneDelegate swizzling.


fix: some vim plugins get disabled by mistake

This commit addresses a few regressions introduced by #1340:

The tutor plugin was accidentally disabled.
netrw, along with its configuration, was mistakenly disabled.
EditorConfig is now being implicitly disabled, which wasn't intended before #1340.

EditorConfig is not disabled currently.

i thought we use nvim-tree as netrw, no?
or it's necessary to load builtin netrw?

I don't use editorconfig, so I can't judge if it works for fine.
And as the readme of nvim-tree said, disabling netrw is strongly advised.

Sorry for the late reply! I've had a lot to sort through over the past few days lol

EditorConfig is not disabled currently

Oops, that was enabled by mistake. Sorry for the extra noise introduced with this PR! I somehow forgot we already have sleuth.vim lmao

i thought we use nvim-tree as netrw, no?
or it's necessary to load builtin netrw?

nvim-tree isn't actually hijacking netrw during startup cuz it's intended to be loaded on demand. So if we disable netrw, users might encounter issues when trying to open directories with neovim at startup. Alternatively, we could configure nvim-tree to hijack netrw, but that would likely cause a noticeable increase in startup time[^1].

And as the readme of nvim-tree said, disabling netrw is strongly advised.

Hmm, I think this ultimately comes down to personal preference cuz afaiu netrw is generally useful for opening a directory with neovim (like nvim .) at startup, which is significantly faster than using nvim-tree[^1] and doesn't come with a huge deficit in features compared to nvim-tree. In most other cases, nvim-tree handles things well.
[^1]: That's what happens on my devices, tho I'm not sure if it's different with other software and hardware combos.

https://github.com/ayamir/nvimdots/pull/1341/commits/0b6dc571dbde61f4d1f2e1c3e7c50e2f30aaf7ec reintroduces load_distribution_plugins and adds a warning about enabling editorconfig.lua:
Sleuth.vim already includes all the features provided by this plugin.
Do NOT enable both at the same time, or you risk breaking the entire detection system.

I've kept netrw enabled for now, but I'm open to changing that whenever lol

Fine for me.

tested with builtin editorconfig seems to work (as I don't use sleuth.vim).

we can't disable builtin editorconfig via global options, if we use lazy.nvim.
we can only get a valid disable via lazy.nvim.

tbh, i think don't we need vim-sleuth since we now have a builtin editorconfig.
how do u guys think? @ayamir @Jint-lzxy @aarnphm

sgtm. always +1 when removing plugins.

tbh, i think we don't need vim-sleuth since we now have a builtin editorconfig.

vim-sleuth is useful for me b/c I don't use editorconfig lol

ok lol
then i think it's ready to merge.


[TASK] Add flag in input file to switch between CSV and NetCDF for Outter/Inner

Issue Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Sometimes it would be nice to determine which kind of data digestion we'll use in a RAVEN run.
Describe the solution you'd like
A clear and concise description of what you want to happen.
A flag in the input file that lets users specify CSV or NetCDF
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Approved to close via #149


Puppeteer.LaunchAsync hangs every once in a while waiting for a page to open

Description
Puppeteer.LaunchAsync hangs occasionally - perhaps once every thousand calls (not sure of the exact frequency).
Complete minimal example reproducing the issue
I could try writing sample code to launch the browser repeatedly, haven't done that yet.
Expected behavior:
Puppeteer.LaunchAsync should return (or at least throw an exception).
Actual behavior:
Puppeteer.LaunchAsync never returns. It appears from examining the process tree that Chrome launches successfully, but PuppeteerSharp never completes the connection process. Downloads are not a factor here since we're launching a preinstalled binary.
Versions

Which version of PuppeteerSharp are you using? 9.1.0
Which .NET runtime and version are you targeting? 7.0

Additional Information
I've experienced this issue only in an Ubuntu container, but since I haven't tried running PuppeteerSharp heavily on Windows, I'm not sure whether the OS is a factor.
If I exec into the container and kill the Chrome process, Puppeteer throws the following exception:
PuppeteerSharp.ProcessException: Failed to create connection  ---> System.TimeoutException: Timeout of 30000 ms exceeded
    at PuppeteerSharp.Helpers.TaskHelper.WithTimeout[T](Task`1 task, TimeSpan timeout, Func`2 exceptionFactory) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Helpers/TaskHelper.cs:line 180
    at PuppeteerSharp.Browser.WaitForTargetAsync(Func`2 predicate, WaitForOptions options) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Browser.cs:line 235
    at PuppeteerSharp.Launcher.LaunchAsync(LaunchOptions options) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Launcher.cs:line 83
    --- End of inner exception stack trace ---
    at PuppeteerSharp.Launcher.LaunchAsync(LaunchOptions options) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Launcher.cs:line 89
    at PuppeteerSharp.Launcher.LaunchAsync(LaunchOptions options) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Launcher.cs:line 95

So it seems that PuppeteerSharp is hanging waiting for a page to open, and the timeout it sets isn't actually being triggered. If it's possible to fix this so that the timeout actually throws, that would be a great start, since it's not a big deal to me if PuppeteerSharp fails to launch every once in a while.
Just reviewing Browser.WaitForTargetAsync without knowing much about the PuppeteerSharp internals it seems like there is the potential for a race condition if the TargetCreated event is fired just after Targets() is called on line 224 and just before the event handler is attached on line 232. However, I'm not sure why the timeout isn't eventually throwing in that case. If that is the issue, it seems like it would be easy to reproduce by inserting a Task.Delay between lines 224 and 232.

I confirm this also happens on Windows systems. Tried with Puppeteer v10.0.0 and different version of Chrome (109, 112, 113). Puppeteer.LaunchAsync hangs (not respecting the timeout set) maybe 3-4 times in 1.000 tries.

Upon further debugging (I completely removed this next line), it seems that the problem is not:
await browser.WaitForTargetAsync(t => t.Type == TargetType.Page).ConfigureAwait(false);
Puppeteer hangs on one of the following lines:
                    connection = await Connection
                        .Create(Process.EndPoint, options, _loggerFactory)
                        .ConfigureAwait(false);

                    var browser = await Browser
                        .CreateAsync(
                            options.Product,
                            connection,
                            Array.Empty<string>(),
                            options.IgnoreHTTPSErrors,
                            options.DefaultViewport,
                            Process,
                            null,
                            options.TargetFilter)
                        .ConfigureAwait(false);

I will try to debug further.

After 10k test runs, managed to narrow it down to the following line of code in ChromeTargetManager.cs:
await _initializeCompletionSource.Task.ConfigureAwait(false);
(from public async Task InitializeAsync() method)
Does anyone know why would this hang and how could we make it timeout somehow?

Nice work @tom2williams! That task is completed here, so I'm guessing that this line of code is never executed:
https://github.com/hardkoded/puppeteer-sharp/blob/56d0f7c37ec796ebb09b7e3f7982b9a5ea27543e/lib/PuppeteerSharp/ChromeTargetManager.cs#L336

@tom2williams could you share how you're reproducing this? I tried calling Puppeteer.LaunchAsync 1000 times, awaiting in between each call, and didn't get any hangs.

@leonardo-fernandes I am running Puppeteer in a heavily used production environment. There are, at any given time, at least 3-4 instances of Puppeteer already running and calls keep coming. I was not able to reproduce this into a separate app unfortunately. I can add more traces to the code. Just let me know what should I check.
@danports Indeed, that line of code is not execute, but since the method is executed, it means that _targetsIdsForInit.Count is not 0 (when this hangs). What does that mean?

I was able to replicate this fairly consistently with a Main code like the following:
Task<IBrowser>[] browserPromises = new Task<IBrowser>[1000];
for (var i = 0; i < browserPromises.Length; i++)
{
    browserPromises[i] = Puppeteer.LaunchAsync(new LaunchOptions() { Product = Product.Chrome, Headless = true }, null);

    if (i >= 5)
    {
        var browser = browserPromises[i - 5].GetAwaiter().GetResult();
        browser.DisposeAsync().GetAwaiter().GetResult();
    }
}

for (var i = 0; i < browserPromises.Length; i++)
{
    var browser = browserPromises[i].GetAwaiter().GetResult();
    browser.DisposeAsync().GetAwaiter().GetResult();
}

It launches up to 5 browsers at once. When CPU stays constant at 0%, I pause the debugger and inspect the remaining threads.
I have narrowed it down to a race condition between _targetsIdsForInit.Remove(target.TargetId); inside OnAttachedToTarget and  _targetsIdsForInit.Add(kv.Key); inside StoreExistingTargetsForInit. It seems that these two methods run in separate threads, and the following sequencing of steps causes the browser to hang:

Thread 2 executes _targetsIdsForInit.Remove(target.TargetId) - note, the Remove happens before the Add
Thread 1 executes _targetsIdsForInit.Add(kv.Key);
Thread 2 continues execution and calls FinishInitializationIfReady();, however the condition _targetsIdsForInit.Count == 0 is not satisfied and _initializeCompletionSource is never set.

Awesome @leonardo-fernandes! Thanks for the detailed analysis and the PR!


Is the library compatible with Redis sentinel?

Quoting  the documentation:
You need Sentinel support in your clients. Popular client libraries have Sentinel support, but not all.

You might have to try it, I don't think anyone has yet


I can not clone git repo

1. Apply either the bug or feature-request label
Bug
2. Describe the bug or feature
I can not clone git repo
3. If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Try and clone the repo as suggested in the example page here
https://github.com/Shopify/draggable/tree/master/examples
git clone git@github.com:Shopify/draggable.git
Cloning into 'draggable'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.
4. Please tell us about your environment:
OSX Mojave

hi @turigeza, this seems like you're having a general problem with your ssh or github setup and not related to this repository. I'm guessing you don't have your ssh key added to your github account, quick google search shows some solutions that should help:

https://help.github.com/en/articles/adding-a-new-ssh-key-to-your-github-account
https://help.github.com/en/articles/error-permission-denied-publickey
https://stackoverflow.com/questions/2643502/how-to-solve-permission-denied-publickey-error-when-using-git
https://gist.github.com/adamjohnson/5682757

Please try solving the issue with the help of those links or google and stackoverflow, there is a lot of other resources about this error on the internet - this issue can be closed

ok thanks sorry to bother you I forked it and got it that way anyway
On Wed, 22 May 2019 at 20:49, Daniel Marchuk<EMAIL_ADDRESS>wrote:

hi @turigeza https://github.com/turigeza, this seems like you're having
a general problem with your ssh or github setup and not related to this
repository. I'm guessing you don't have your ssh key added to your github
account, quick google search shows some solutions that should help:

https://help.github.com/en/articles/adding-a-new-ssh-key-to-your-github-account

https://help.github.com/en/articles/error-permission-denied-publickey

https://stackoverflow.com/questions/2643502/how-to-solve-permission-denied-publickey-error-when-using-git

https://gist.github.com/adamjohnson/5682757

Please try solving the issue with the help of those links or google and
stackoverflow, there is a lot of other resources about this error on the
internet - this issue can be closed
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Shopify/draggable/issues/337?email_source=notifications&email_token=ACHHHPAIFKBFYED5XBSZ2DTPWWPWNA5CNFSM4HOV7NO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWAEAJY#issuecomment-494944295,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACHHHPCXNQTB7NBD4AHPAWTPWWPWNANCNFSM4HOV7NOQ
.


Is it possible to support scss files?

Hey, this is an amazing library.  I'm trying to find all uses of a particular library. I noticed in your demo you suggested it found a css file. I'm am trying to find imports in scss files.
const files = [
  'src/**/*.{js,jsx,scss}',
  '!src/lib/*.*',
];

const results = findImports(files, {
  absoluteImports: true,
  relativeImports: true,
  flatten: true,
});

Sadly this outputs Error in `undefined`: SyntaxError: /Users/ccheshire/Development/work/app-qa/src/css/_action-buttons.scss: Unexpected token (1:0)
The action-buttons file itself only includes a few css classes.
Is this because the scss file isn't javascript and therefore the syntax isn't valid?

This library is purposed to find all import statements in JavaScript files, it cannot parse .css, .less, .scss, or .styl files. In your case, you need to use node-glob and some regular expressions to parse @import statements in .scss files, like so:
var glob = require('glob');

glob('**/*.scss', { /* options */ }, function(err, files) {
    // files is an array of filenames.
    files.forEach(function(file) {
        // Use regular expression to match @import statements
        //     :  :   :
    });
});

Check out code below for my regular expressions:
https://github.com/cheton/browserify-css/blob/master/css-transform.js#L218-L239

Thank you, that’s most helpful. Yesterday I played with something similar to your suggestion.
Thanks for the suggestion and the rapid response :)
I’ll close this now.


建议为 auto-complete 组件新增追加模式

Clear and concise description of the problem
现有的 auto-complete 组件会在select选中后直接覆盖输入框中的内容，且无法通过 on-select 进行hack
Suggested solution
建议给 auto-complete 组件新增一个选项，用以控制 select 选中后是直接覆盖，还是追加内容
Alternative
No response
Additional context
No response
Validations

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

This issue should have been fixed in the new version


String exports aren't resolved on wildcard imports

Describe the bug
JS allows you to export/import as arbitrary strings. However, in vitest, wildcard imports do not import these string-exports.
// file-1.js
const something = "Something"
export { something as "arbitrary string" };

// file-2.js
import * as T from "./file-1.js"
console.log(T["arbitrary string"]) // expected: log "Something"

If this is executed via node it works as expected. If that same code is executed via vitest undefined is logged instead.

vite bundles this code correctly

Reproduction
https://github.com/LorisSigrist/vitest-string-exports-wildcard-reproduction (basically the code example above)
System Info
System:
    OS: macOS 14.4.1
    CPU: (14) arm64 Apple M3 Max
    Memory: 2.54 GB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.2.0 - /opt/homebrew/bin/node
    npm: 10.7.0 - /opt/homebrew/bin/npm
    pnpm: 9.1.4 - /opt/homebrew/bin/pnpm
    bun: 1.1.8 - /opt/homebrew/bin/bun
  Browsers:
    Safari: 17.4.1
  npmPackages:
    vitest: ^1.6.0 => 1.6.0

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Thanks for the reproduction! This looks like an issue in Vite SSR, so I reported to there by adjusting your code

https://github.com/vitejs/vite/issues/17426

The fix was merged in https://github.com/vitejs/vite/pull/17446 as part of 5.3.0, so if you update your Vite version manually or revalidate the lockfile, it should work.


Unable to change the color with changes in config.toml

Hello!
Thank you for this simple yet pretty theme. :) I was wondering if I could get some help about changing the color of background and foreground?
I tried putting the following block in [params] section but it does not come into the effect. There is also no error as specified in the README.
   [params.colors]
        background = "#3f1c66"
        foreground = "#d8d517"
        hover = "#e9dafa"

However, I do get the following warnings on running the server. Are these related to my issue?
WARN 2021/07/05 12:49:23 found no layout file for "HTML" for kind "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2021/07/05 12:49:23 found no layout file for "HTML" for kind "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2021/07/05 12:49:23 found no layout file for "HTML" for kind "page": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2021/07/05 12:49:23 found no layout file for "HTML" for kind "section": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.

Thank you very much!

Thanks for your kind words!
On first sight, the settings in config.toml look correct. Do you have a repository that I can clone so that I can have a look?

Thanks for your kind words!
On first sight, the settings in config.toml look correct. Do you have a repository that I can clone so that I can have a look?

Thank you so much, @EmielH ! This is the repo: https://github.com/inashivb/test-webpage

I don't have time today, I'll have a look soon!

I don't have time today, I'll have a look soon!

No problem at all. Please take your time! Have a good day! :)

Hi @inashivb - apologies for the delay.
I cloned your repository and tried changing the colours in the config file. Everything works perfectly for me. I see a purple background and yellow letters. Also the colours update automatically when hugo serve is running and I change the config file.
I also see the warnings but these shouldn't be related to this issue. I'll see if there's something I can do in the theme to get rid of the warnings.
Could you please try again?

Hi @EmielH !
Major apologies for getting back so late. I still do not see the changes but since the issue is unrelated to the theme and a "does not work on my machine" kind, I'll close this.
Thank you very much for taking out time to assist!


self issued: first name and last name inversion

self issued credential : the firstname and lastname label are mixed (not the same as the screen of personal screen)

@hawkbee1
Do you mean Where we display self-issued credential cards???
Or Where?

Yes, when we display the self issued credential.

thanks,
fixed