awseb-logs-nginx-proxy

When launching this example config, the following error occurs:
Service:AmazonECS, Code:ClientException, Message:Unknown volume 'awseb-logs-nginx-proxy'., Class:com.amazonaws.services.ecs.model.ClientException

Could you post on the EB forum at http://bit.ly/aws_eb_forum. Please include the environment ID and region where you encountered this error

I am also seeing this. I am trying to simply re-deploy my already existing application to my eb environment based on the "Configuration
64bit Amazon Linux 2015.03 v2.0.0 running Multi-container Docker 1.6.2 (Generic)" stack. Service:AmazonECS, Code:ClientException, Message:Unknown volume 'null'., Class:com.amazonaws.services.ecs.model.ClientException

I added this to volumes to get past the issue...
"volumes": [
      ...,
        {
            "name": "awseb-logs-nginx-proxy",
            "host": {
                "sourcePath": "/var/log/nginx"
            }
        }
    ],

I'm not certain it is the correct fix, but mapping the containers logs to the host's logs seemed like a good start.


More work to remove ExternalParser dependency. Test if ExternalParser…

… is called.

👎
DO not merge need to make pom correct


Feasibility of Upgrading Cryptography?

This request was originally added as an issue under the 'element-web' repo (/vector-im/element-web); they advised that it should be moved here

Original Request URL - https://github.com/vector-im/element-web/issues/19835
Going to republish my original request below for convenience.
Upgrading Cryptographic Scheme for Matrix - Feasibility?
Recently, the NSA deprecated 128-bit strength cryptography (secp256k1 specifically; I think the NIST SP reference still recommends ed25519).
This isn't something that I believe is an impending security issue but it does fall in line with the overall ethos of Matrix, which is to provide an unprecedented and unrivaled level of security in their chat app.
First Proposal - Intermediate Upgrade
At some point in the not so distant future, it is expected that there will be a mass migration to some of the quantum-resistant ciphers we saw appear in the NIST's PQC competition (now in its 3rd round). Putting speculation about quantum computers to the side, there have been many other advances in cryptanalysis and computing in general that seem to put 128-bit security in question in the longer-term.
The most recent Suite B published by NSA dropped sha256 and secp256k1. While ed25519 is not secp256k1, the removal of sha256 alongside the latter led me to wonder if the NSA felt that 128-bit strength cryptography was no longer sufficient to secure data & communications vs. simply having misgivings about secp256k1. I am aware that there are properties specific to the secp256k1 algorithm that make it uniquely susceptible to cryptanalytic attacks (i.e., 'nonce leakage'), in a way that ed25519 is not. However, this is not the case with sha256.
Its hard for me to justify that the deprecation of sha256 was done in preparation for quantum-capable computers in the near term or future since there is no perceptible advantage quantum computers will have when it comes to attempting to 'crack' the hash (the biggest fear comes from the potential destruction of ecdh + pki schemes).
This Has to be Done at Some Point Anyway
Its obviously up for debate whether this must be done now. Many would likely argue that there is no impending risk at this very point in time. But there is a virtual unanimous consensus that these cryptographic schemes will need to be swapped out at some point in the not so distant future (likely before the end of the decade, if not sooner).
When its too late, its too late obviously. That statement isn't meant to fearmonger at all but rather emphasize the greater point that even if this is done prematurely, it won't be for naught. Also, getting the ball rolling on this earlier will allow time for proper testing, feedback, further ideas etc.; nobody wants to be swapping out cryptographic algorithms with a gun to their heads, so to speak.
Willing to Work on This Implementation Independently
If the team feels this proposal is interested but is swamped with work, I'd be more than happy to give this a swing under appropriate guidance.
Please advise whenever you all get a chance. Great job with this project overall though - Matrix is something we needed in the open source community & hopefully it is here to stay for a very long time.

There are two areas that i can remember that use encryption at it's core; Server-signing keys, and E2EE keys.
Both are (to a degree) designed to swap to other implementations if the need requires, server keys names are prefixed with ed25519:<NAME>, so any server could easily switch on that (once implementation lands), however, a future MSC which could possibly switch to hash-based names (which i remembered there was talk about) should take this switching possibility into account.
E2EE is governed by the m.room.encryption state event, which has a content like follows;
{
    "algorithm": "m.megolm.v1.aes-sha2"
}

If possible, a new algorithm could be added here that addresses your concerns. However, switching encryption algorithms in the middle of a room is an as-of-yet undefined behaviour, so that has to be specced as well.

Note that i am not a cryptography expert, and only know some bits and bobs about the spec.
@uhoreg is the SCT member which knows all about encryption, and he'd be able to tell you some more about this.

My knowledge of crypto isnt the best but if my google search is not incorrect NIST are looking for Public Key Crypto but we also need something that is Symetric most likely. Like SIDH is as far as i understand one of the promising canditates in this space especially since it would mean we keep our PFS assuming SIDH gets proven to be secure enough. (Plus key sizes are still resonable and not absolutely massive)
Now as for upgrading the crypto in a room well that is a can of worms because downgrade attacks have to be avoided and all the things like that.

https://github.com/matrix-org/matrix-doc/issues/2458 is a very-related issue, and my response to that issue applies to this issue as well, at least as far as end-to-end encryption goes.  We also use ed25519 for signatures from servers, and sha256 in various things, such as constructing event IDs.  Switching event IDs to be based on, say, sha512 or sha-3 would require a new room version.

I also meant to say, it's not clear whether we should switch to ed448/x448 soon, and then switch again to something post-quantum, or if we should wait until there's a clear post-quantum algorithm to switch to and only switch once.

I think that we should only switch once one of these 2 conditions are met. There is a strong enougth desire or need to justify swapping multiple times potentially or theres a solid standard established so the switch is only done once.
Situation 1 can happen if we say in theory Quantum computers evolve way faster than our post-quantum algorithms do as an example of a situation.
Situation 2 is well simple once there are clear standards for what is best for matrix then its a nobrainer from my prespective to start the process of migrating.
Assuming that standards get made quick enough and matrix adopts them quickly enough we should have ample time to migrate before attacking the previous systems becomes a practical real world concern from non nation state actors. Nation state actors are expected to be a concern quite earlier than other parties due to the amount of resources they are usually willing to spend on an attack.


delete all my data twice

Issue Type: Bug
the last two edtion, after auto update, all my user data and extensions was delete , what's the matter?
VS Code version: Code - Exploration 1.42.0-exploration (15d77c6ee6bf204cb4dc8e199d3db852263ccfb0, 2019-12-17T09:53:04.711Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz (4 x 1796)

GPU Status
2d_canvas: unavailable_softwareflash_3d: disabled_softwareflash_stage3d: disabled_softwareflash_stage3d_baseline: disabled_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: disabled_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: disabled_softwareviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: unavailable_softwarewebgl2: unavailable_software

Load (avg)
undefined

Memory (System)
7.90GB (3.31GB free)

Process Argv
--user-data-dir data --extensions-dir data\extensions

Screen Reader
no

VM
0%

Extensions: none

@helloyan where did you store your user data and extensions ?

@bpasero User seems to be using the exploration build.

Yes, please use insiders or stable for production quality.


Session fixation in Auth0's "Cross Origin Authentication"

Feel free to generate some image, fill in missing information etcetera.

hi @LabanSkollerSentor, this is currently out of scope of this database, since it isn't directly related to a cloud service provider. however, if at any point in this future we expand this project to include vulnerabilities affecting other service providers as well, then we will be sure to include this submission.


GitHub authority

Lego I'm back

Hello,
It looks like this issue does not currently contain any questions or problems. If there is a specific issue you're running into with the code samples in this repository, please reopen this issue with more information (code snippets, stack traces, etc.).
Thank you!


Change so as to use gaussian noise by default

Also moved test from the test_gpr I created into the test_gpr that was pre-existing under learning/Gaussian_process/tests/test_gpr.py and changed it so that it also tests for noise by default.

Hello @SoManyUsernamesTaken! Thanks for submitting the PR.

In the file skopt/learning/gaussian_process/tests/test_gpr.py, following are the PEP8 issues :

Line 125:1: W293 blank line contains whitespace

It seems that on the contrary there are existing tests in place to ensure that the default behaviour is to make sure that noise is not included by default. I leave this up to you.

Any thoughts @MechCoder and @glouppe on changing this default?
We'd have to change the tests that check that by default no noise is included. They are doing their job of detecting that we are changing the defaults ;)

Now we already have noise="gaussian" by default. Feel free to reopen this if there is anything missing.


fix: top view visibility in lifetime select component

fixes #229
Increased the z-index for the lifetime select component to be more than the Quill component's z-index (1000)

Thank you @m4-droid! Hm, this works, of course maybe it would have been better adjusting quill, but, I do not think it matters in this case as we do not have many elements with different z index.


1.9.2 release

Depends on #901 , #906, #898

LGTM, #898 will be released in the next version

requirements.txt were updated, is anything else left? @themarpe


cross-env pkg blocked iopay desktop build

it was fixed by adding cross-dev to packages. https://github.com/iotexproject/iotex-explorer/commit/b3d2bdcd9f4098df9de7d0dd269c4ce9a5935aaa
but it seems only needed in dev mode.
todo here: see how to remove the dep from production build of iopay desktop.

still not able to build.

also removed cross-env in electron build:
https://github.com/iotexproject/iotex-explorer/commit/d4e48c32f4f9150881ed6dc991cf4a1abe4866ee

still not able to build.

try replace cross-env  to npx cross-env xxx


Add "OnError" handling

Please resolve this, old, like the world, problem.
In some situations new session after "reached end of stream" not started. It happens, when OnError not catches.
See attachment with stacktrace, please

Should be fixed with https://github.com/badoualy/kotlogram/commit/65c96ce2862b29425dcfcf26da39f776f57d1253

Please tell, when will be the release fix this commit?

No plan yet,
use
compile 'com.github.badoualy.kotlogram:api:65c96ce'

in the mean time

Thanks, I will try today

handle works, but my connections not up.... 2 of 3 broken in 2 minutes after start =(

see #33 for this issue

I already seen it and post my screenshots there
Connections are drops every time on some of pool clients.
I need to reboot my server side every 5 minutes :(

Yeah, I have no clue why it's doing this sadly ...
Seems worse after removing the KEEP_ALIVE. I'll revert this change.

Please? when do you can to do it?

5f8590d5e1

https://github.com/badoualy/kotlogram/commit/5f8590d5e198362a54b4ad867e877793006b3a11
did not help

I just reverted the changes on KEEP_ALIVE which seems to have make things worse.
Please take further discussion about end-of-stream issues in #33
As I said there, I'm clueless as why this happens, and am pretty much stuck.


Running profiler from Juno REPL gives wrong result.

Please search existing issues to avoid duplicates.
Details

Atom version: 1.33.0
Julia version: 1.0.2
OS: MacOS Mojave
Package versions:

Atom.jl: 0.7.11
julia-client: 0.7.11
ink: 0.9.13

Steps to reproduce
run @profile MyPackage.my_function() in command line REPL and in Juno REPL

In the image, the top half is profiler running from the command line, and the bottom half is the profiler running in the Juno REPL. Running @profiler (instead of profile) also shows an incorrect output.
One additional symptom is that the profiler complains about the buffer being full when run in Juno, but not on the command line.

Does this happen when you use inline evaluation in an editor?

Ok, so I was playing around with this a bit and the main difference is that Juno runs multithreaded by default whereas the REPL does not. With JULIA_NUM_THREADS=12 julia things look pretty similar all in all.
Can you try the "global" option in the julia-client settings? There should be no major differences anymore I think.
Juno's profile viewer is also a bit different from ProfileView.jl in the sense that it hides stackframes with only one child and instead displays the child directly.

Should be fixed on master, where we filter profile traces much better.


Not setting Context:useCache causes an UnderflowError

This might be the wrong repo almost so I'll try to flesh this out later, but the gist is that a seeming fresh instance of Druid if called with an empty context object will throw an error called JavaUnderflowException.
Given we set useCache to null this occurs on some calls. Oddly the error seems to have vanished now I made a single request with the useCache value set.

Apologies for the late response - This repo is a .NET Druid client. It sounds like you're using a Java client such as this: https://github.com/zapr-oss/druidry

For context. by wrong repo I meant I might have found an issue with Druid itself rather than the .NET Client.


How to use onClick and onDrag together?

I'm using react-use-gesture and react-spring to create moveable divs like so: https://codesandbox.io/s/xmqwz
import React, { useState } from 'react'
import { render } from 'react-dom'
import { useGesture } from 'react-use-gesture'
import { useSprings, animated } from 'react-spring'
import './styles.css'

const addVectors = (v1, v2) => [v1[0] + v2[0], v1[1] + v2[1]]

const Moveables = ({ items }) => {
  const [selectedItems, setSelectedItems] = useState([])

  const toggleSelectedItem = item => {
    const { id } = item
    if (selectedItems.some(item => item.id === id)) {
      setSelectedItems(selectedItems.filter(item => item.id !== id))
    } else {
      setSelectedItems(oldState => [...oldState, item])
    }
  }

  const [springs, setSprings] = useSprings(items.length, index => ({
    xy: items[index].position,
    zIndex: 0
  }))

  const binds = useGesture({
    onDrag: ({ args: [itemIndex], delta, temp = springs[itemIndex].xy.getValue() }) => {
      const selectedItemIndexes = []
      items.forEach(({ id }, index) => {
        if (selectedItems.some(item => item.id === id)) {
          selectedItemIndexes.push(index)
        }
      })

      setSprings(index => {
        const animationValues = selectedItemIndexes.includes(index)
          ? {
              xy: addVectors(delta, temp),
              zIndex: 1
            }
          : undefined
        return animationValues
      })
      return temp
    }
  })

  return (
    <div className="content">
      {springs.map(({ xy, zIndex }, index) => {
        const item = items[index]
        const { id } = item
        return (
          <animated.div
            key={id}
            style={{
              zIndex,
              transform: xy.interpolate((x, y) => `translate3d(${x}px, ${y}px, 0)`),
              border: selectedItems.some(item => item.id === id) ? '4px solid lightgreen' : '0'
            }}
            {...binds(index)}
            onDoubleClick={() => toggleSelectedItem(item)}>
            {id}
          </animated.div>
        )
      })}
    </div>
  )
}

render(
  <Moveables
    items={[
      {
        id: 0,
        position: [0, 100]
      },
      {
        id: 1,
        position: [0, 200]
      },
      {
        id: 2,
        position: [0, 0]
      }
    ]}
  />,
  document.getElementById('root')
)

When double-clicking on a div, it will become selected. When dragging, all selected divs should move at the same time.
This already works great - except after selecting one div so that it's draggable, double-clicking on any other div in an attempt to select it will cause the first already-selected div to move.
How can I set this up so that click events don't trigger the onDrag gesture?

Hey, thanks for reporting the issue. Do you mind creating a functional (simplified?) codesandbox reproducing the problem?

No problem, here is the codesandbox showing the issue. Try double-clicking to select two divs and move them both at the same time. Selecting the second div is difficult: https://codesandbox.io/s/xmqwz
I've noticed that setting a different top value for each .content > div in the CSS and zeroing out the initial xy values will somewhat alleviate the issue, as you can see here: https://codesandbox.io/s/blazing-resonance-gw9pj
I suppose one solution is calculating the offset for each div based on the height (or size) - kind of like the draggable list example.
However, what I'd really like is some way to maintain the offsets of all the divs relative to each other. Imagine selecting multiple icons to drag/drop on the desktop, those icons keep their relative distance to one another while dragging. I think my issue is that the drag is trigger on click, so when clicking to select the second div, the first selected div is dragged towards the second one.

Hey, thanks for putting up the codesandbox!
Is that what you want to achieve? https://codesandbox.io/s/awesome-surf-414f1
I'm pretty sure this can be further simplified, but let me know if this works as is?

Yes, that's exactly what I wanted, and I don't think I would've figured that out on my own! It looks like the main trick is mapping the temp value? I'm sure I'll use this much more in the future, thanks very much for taking the time to help and teach.

Yes, that’s the main trick. Essentially, useGesture keeps track of just one state, which is relative to pointer coordinates. What you usually want to do is move objects based on the mouse movement (ie the delta value). But you need to know the origin position of each objects prior to the mouse movement so that you can add it to the delta value.
Note that in a simple case where you only have one object without needing to enable / disable drag, this is exactly what the local attribute is designed for.

@dbismut I've been playing around with the library more, and have come across a situation or two where it would still be useful to differentiate between a click and a drag event. Is there some way to do this, using the previous example in this thread? Thank you for your time!

That’s a bit trickier, as drag gesture is currently triggered by onMouseDown, so at the moment a click event would inevitably trigger a drag gesture. One way to solve this would be to only trigger a drag event when the pointer actually moves or after a short delay. I’ll see if I can do this without generating regressions.

I thought that might be the case - and I had the same thought about triggering a click only if the pointer has moved, but I thought that might tend to trigger false clicks if someone was intending to drag but just hadn't decided where to move yet. Even with the delay, it doesn't sound like a concretely reliable solution, but it would likely be better than nothing.
I was wondering if it might be possible to initiate dragging on DragStart or Drag event, but I know from having implemented custom dnd solutions in the past that there are a lot of caveats and knock-on effects to consider. I need to take a closer look at the useGesture source and get a better understanding of what would be possible.

Just to clarify the idea would be to trigger a drag to the earliest condition:

after a short delay following a mousedown event
whenever the pointer moves after a mousedown

I think this is the logic adopted by hammerjs. Unfortunately I’m not sure there is a perfect alternative.

I agree, there is likely no perfect solution. I think what you've proposed is probably as good as it gets, and I think it would work well enough in the vast majority of situations.

onDragStart would require to make the element draggable right (ie attribute draggable set to true)? That means conflicting with the native draggable api, we’ve tried that before and it’s a tough battle.

Yes, that's right. The native api absolutely leaves a lot to be desired. I've created one implementation in the past that goes this route, within React, and worked on the web as well as across all native devices that we tested with (at a big agency, so pretty extensive iOS/Android testing) - but it absolutely involved fighting against the native implementation. I might play around with this idea in a different branch. The implementation would be pretty extensive (probably too extensive to be merged back, perhaps a fork would be better), and there may be issues I'm overlooking. I think your initial suggestion is much more immediately useful and workable.

Hey @codypersinger I have something working where drag only happens after a short delay or the mouse moving, but I just have one question: what's the difference between a drag and a click in your use case? The question is a bit silly, but is it the fact that the pointer should not move during a click, or is it that the click is supposed to be short?

Awesome! I'm still playing around with the native API implementation, making slow progress. It's not a silly question at all. For pretty much all the use cases I can think of, the click being short is the more important and reliable factor.

Maybe there's no need for what I was mentioning above then:
https://codesandbox.io/s/awesome-surf-414f1
It's a bit silly, but I think this is more or less what you want isn't it?

It does more or less achieve the effect. It's fairly easy to both drag and click with quick gestures, which is not ideal behavior in the example codepen - I think making sure the pointer hasn't moved would take care of that. It would be nice to have an onClick binding abstraction which is configurable with props like duration and allowMovement, so that click-based logic doesn't have to live in "onDrag" - but I understand that those events are necessarily intertwined, and it may not jive with the goals of this library which seem drag-focused. What are your thoughts?

I've just published it on npm with the next tag. yarn add react-use-gesture@next should do it.

I'm not noticing any difference in when react-use-gesture's onDrag is triggering in regards to either delay or cursor position after upgrading to 5.2.0-beta.1, but perhaps I'm doing something wrong? I have to run to a meeting now but I'll knock together a codepen ASAP

I haven’t tested it myself except locally tbh so maybe there’s something wrong!

I'd be happy to take a look sometime tonight, if there's somewhere I can see the commits / history for that release? Thanks for all your time and effort on this so far, I truly appreciate it.

Have left my computer at work :) will push the branch tomorrow morning CET time.

Smart choice! That sounds great, no rush. :v:

Hey, so I just pushed the code on the next branch (tests are failing but that's expected).
Have a look at: https://codesandbox.io/s/dazzling-vaughan-4j8dd
I've set the time threshold to 1 second so that the lag is noticeable.

If you just briefly click on the pink square, only the click counter should increment.
If you mouse down for 1 second or more without moving your mouse, the drag status should show drag started.
If you release your mouse while hovering the pink square, the  the drag status should show drag ended and the click counter should increment
If you mouse down and then move your mouse right after it should trigger a drag right away, without waiting for 1 second

All of this is expected in the way I've implemented the logic. Note that the click handler is untouched, so it behaves exactly like it should.
PS: after looking at Hammer JS code, they actually trigger a drag only after the pointer moves past a threshold (default is 10px).

Very nice, this works extremely well. The only issue I've noticed is with immeditate: true when calling set, the click counter is incremented when the drag ends. Other than that, this looks flawless from my admittedly limited testing.

Well yes... as I was saying, if you release your mouse over the dragged element it’s still considered as a click by the browser. immediate:true pretty much guarantees that the dragged element follows your mouse so that’s why the click counter increments. Theres not much we can do about this.

I see what you mean, my mistake.

Is it possible to optionally prevent the click from being triggered if you are actively dragging and release the mouse over the pink square?

It is, but not natively in the lib. You can use the same trick from my sandbox above:
https://codesandbox.io/s/awesome-surf-414f1

That makes sense. Here's a simple example for anyone that sees this in the future: https://codesandbox.io/s/exciting-surf-89ncy

Looks like this never made it out of beta... anyone have a solution to this issue?  Trying to use onDrag from react-use-gesture and onDblClick from konvajs and I always get a drag triggered for every double click

Hey @dmcmorris, indeed drag is triggered as soon as the user mouses down. Unless proven otherwise, I’ve found difficult to accurately predict whenever a drag should actually be triggered, this depends on the usecase.
It shouldn’t be a big deal in your case though, nothing forces you to update your UI when the drag handler triggers. A double click generally happens with no mouse movement, so you could only update your UI in onDrag when first or last are false. If you actually need something specific to happen when the user starts or ends dragging, you could use a ref. I can explain this in greater details if you provide me with a concrete use case.

@dmcmorris The solution can be seen here  - you need to use first and last in useGesture's onDrag, and store the drag delta time in a ref.
onDrag:
	if (first && time) {
		// Drag started, no click triggered
		dragDeltaTime.current = time;
	}
	else if (last && time) {
		// Drag ended, no click triggered
		dragDeltaTime.current = time - dragDeltaTime.current;
	}

onClick:
	event.stopPropagation();

	if (dragDeltaTime.current < 60) {
		// Click started, no drag triggered
	}

	dragDeltaTime.current = 0;

thanks @codynova  and @dbismut, I had not fully explored all of the attributes available in onDrag.  For my purposes I used distance to filter/control the UI update and ignore drags:
onDrag:
        if (distance < minDragDist) {  //minDragDist = 10
          return memo;
        }

The quick replies are much appreciated... awesomely powerful library.

Just be careful with distance as dragging might start but then if you get back to your point of origin without releasing your drag, distance might pass under the threshold and your UI will not be updated.

Unless proven otherwise, I’ve found difficult to accurately predict whenever a drag should actually be triggered, this depends on the use case.

@dbismut For the record, using the click speed/delta time solution has been extremely accurate in my experience - although perhaps it depends on the use case, as you said. However this has been my go-to solution for complex UIs that strongly differentiate between clicking and dragging on the same element and it has always seemed perfectly accurate in my experience, I have never seen a false-positive.

I'm using a ref to track if the drag has passed the distance threshold or not, I need that to filter other events/logic anyways.  I have some momentum scrolling using spring on this element and longpress events, so time based initiation of the drag was more problematic for me:
const dragInfo = React.useRef({ isDragging: false });

...

onDrag: ({
        active,
        movement,
        velocity,
        direction,
        distance,
        first,
        last,
        memo = position.getValue()
      }) => {

...
        if (!dragInfo.current.isDragging && distance < minDragDist) {
          return memo;
        }

        dragInfo.current.isDragging = true;

        if (last) {
          dragInfo.current.isDragging = false;
        }
...

       return memo;
  }
);

I'll try to throw a simple sandbox together and share later.  Thanks again for the concise and helpful suggestions.

@codynova that’s good to know and I think I’ll add your sandbox to examples / FAQ. However native click events don’t depend on time or movement (I think they’re triggered as long as the target is still under the mouse when it’s released).

@dmcmorris that’s perfect indeed. No need for a sandbox ;)

@dbismut I made a second sandbox that's a bit clearer, and shows drag/click/double-click all working together. https://codesandbox.io/s/elated-cori-45z3q
What do you mean exactly in regards to native events? Can you describe the effect that would have on the sandbox?

@dbismut one thing to point out, the {time: 1000} param doesn't seem to do anything with any versions of react-use-gesture but 5.0.2_beta1

@dmcmorris Good point. I'm not sure whether that is will actually make it into the library at some point, but it is not necessary for the solution.

You’d just have to ask, I don’t have anything against it 🙃 it would be set to 0 by default.

Sorry if that sounded rude! I realized my comment can be read two different ways - and I definitely didn't intend to throw shade 😅
Honestly I don't have an immediate use case for it, and I don't want to suggest adding a lot of clutter to the API - but I do feel like it could be useful, and I appreciate having access to parameters that allow edge-case solutions.
As far as a name, assuming it effects all gesture types, maybe something like gestureDelay?

Oh no don’t worry, I was joking! I’m not sure what other gestures would make sense to have that feature, so for now I think I’ll just make it work for drag (dragDelay it should be).
It’s not that much of an edge case, being able to distinguish a click from a drag should be pretty common and if this avoids hacks or refs its a good thing to have!

There, v6.0.4 is out with dragDelay as an option (set to false by default, you can set it to true and will take a default value of 180ms but you can set any value you want).

Awesome! I've updated that sandbox. That demo still uses refs to determine click and double-click, and uses dragDelay to allow initiating a drag event without moving the mouse (by holding in click for dragDelay milliseconds).
I suppose it would also be nice to have an example that only uses dragDelay without refs. I'm a bit busy right this second but can try to throw something together soon

@dbismut Just doing some testing and there seems to be a significant difference in behavior between 5.2.0-beta.1 time and 6.0.4 dragDelay? Here are some example codepens to illustrate the difference:
5.2.0-beta.1 no time config. This setup triggers a drag event very soon after the mouse click is held.
5.2.0-beta.1 with time config. This setup triggers a drag event after the mouse click is held for time milliseconds. In this case, 1000ms.
6.0.4 with dragDelay config. I would expect with to behave the same as 5.2.0-beta.1 with time config, but dragging no longer seems to work properly.

@dbismut Please disregard my last comment. My example sandbox breaks when updated to 6.0.4, and I initially thought it was due to the dragDelay setting, but now I can see that's not the problem. Here's the original sandbox, and that same sandbox updated to 6.0.4. Can you help me understand the difference in the drag behavior between the two?

@codynova yep that's an easy one, v6 labels things in a better / more conventional way.

Value
v5.x
v6.x

delta between current and previous event
N/A
delta

last gesture offset (xy - initial)
delta
movement

offset since first gesture
local
offset

So you just need to replace delta with movement and you should be good ;)

@dbismut Thanks very much for the speedy reply, I've made the change as suggested - but things still don't seem to be working as I'd expect.
5.2.0-beta.1 sandbox with time configured to 1000ms (using delta instead of movement). With this setup, you can click, double-click, and click-and-drag without delay. You can also click-and-hold for 1000ms to initiate a drag.
6.0.4 sandbox with dragDelay configured to 1000ms (using movement instead of delta). With this setup, you can click and double-click, but click-and-drag is not working properly. You can, however, still click-and-hold for 1000ms to initiate a drag, which works as I'd expect.

Yeah in 6.0.4 I haven't made so that the drag is initiated as soon as the mouse moves (it really waits for the 1000ms). I can fix this in 6.0.5, I'll see what I can do now :)

Awesome. Hopefully the update in 6.0.5 won't make dragDelay confusing for consumers of the API. I suppose it might be possible to have a second parameter instantDragOnMove or dragDelayOnMove or something, which would allow utilizing dragDelay in either the 6.0.4 or 6.0.5 fashion. Honestly without foreseeing exact use-cases, I think it's kind of hard to say whether it would be useful. Thank you very much for the great and speedy work on this lib!

Yeah dragDelay is optin and pretty sure people will stumble upon this thread if they have any questions ;) 6.0.5 is now out, let me know if it works better for you!

Love it. https://codesandbox.io/s/trusting-pine-jpqi5
I cleaned things up a bunch, and I think this is the best solution I can come up with. I'll be replacing the logic in my current projects with the logic from this sandbox. It requires three different refs, but it's working extremely well in my testing.
Rather than tracking drag delta time, we only use a timestamp ref for tracking the time of the last click, and we use boolean refs for tracking current drag and double-click status. And instead of using onClick and onDoubleClick both (and duplicating click delta time logic), we put the double click logic inside the onClick handler.
I tried simply using the dragStatus value to eliminate the need for the two boolean refs, but it was not nearly as accurate/performant as using the refs.
With this setup, it is (intentionally) not possible to trigger two double-clicks in a row. Clicking fast enough to be within the DOUBLE_CLICK_TIME_THRESHOLD will simply trigger a regular click, in the previous click was a double-click. If one would like to allow triggering simultaneous double-clicks, remove the isDoubleClicked ref and relevant logic.

Hey @codynova I've found a bug with dragDelay this morning: in 6.0.6 if you moused down, moved and dragged longer than dragDelay, the square would go back to its origin position (I had forgotten to clear a timeout). This is now fixed in 6.0.7.
I've copied your sandbox here and made a few tweaks, mainly moving to react-spring v9 which simplifies styling attributes: https://codesandbox.io/s/hardcore-kowalevski-kepmr
Also I think you can use performance.now() without using window, it should be better in case you ever move to SSR where window is undefined.

For anyone looking to implement dragDelay option from this thread, it has been renamed in release 7.0.0
https://github.com/react-spring/react-use-gesture/blob/fa6dd05957c34450533445224a42fdc89852be68/CHANGELOG.md#breaking-changes

Is there any example with v.10 regarding this?
Can't get @dbismut sandbox example above to work with latest versions of react-gesture and react-spring.
Even after changing dragDelay to delay 🤔


Add documentation to readme on how to use with sass-loader

Just use sass-loader before (so after in the loader definition). This should not need any specific doc.

Sorry postcss-loader can’t have a docs for every webpack loader.
I can change my mind if this issue will be popular.

@MoOx Yea, I tried that autoprefixer, and it doesn't seem to work. Here's my config:
var webpack = require('webpack');
var path = require('path');
var ExtractTextPlugin = require("extract-text-webpack-plugin");
var autoprefixer = require('autoprefixer');
var precss = require('precss');

module.exports = {
  context: __dirname,

  output: {
    path: path.join(__dirname, 'build'),
    filename: '[name].js'
  },

  entry: {
    app: './js/app.js'
  },

  module: {
    loaders: [
      {
        test: /\.(scss|sass)$/,
        loader: ExtractTextPlugin.extract('style-loader', 'css-loader', 'postcss-loader', 'sass-loader')}
    ]
  },

  postcss: function() {
    return [autoprefixer, precss];
  },

  sassLoader: {
    includePaths: [path.join(__dirname, 'scss')]
  },

  plugins: [
    new ExtractTextPlugin('styles.css')
  ]
}

Here's the sass file:
.banner {
  background-color: green;
  font-size: 48px;
  text-align: center;
  color: white;
  border-radius: 4px;
  box-shadow: black 1px 1px 1px;
  transform: rotate(7deg);
}

And the output file:
.banner {
  background-color: green;
  font-size: 48px;
  text-align: center;
  color: white;
  border-radius: 4px;
  box-shadow: black 1px 1px 1px;
  transform: rotate(7deg);
}

@ai Using this loader with sass or less is an extremely common use-case -- no one in practice is writing plain-vanilla CSS. I think it would be very useful to have a concrete example of how to use these tools together.

I am open for PR. But try to suggest some compact changes. We already have too many config for different cases.

@ajsharp I think you are not using ExtractTextPlugin the right way.
You should use loader: ExtractTextPlugin.extract('style-loader', ['css-loader', 'postcss-loader', 'sass-loader'])} (an array for the default loaders you want to use, the first parameter is used when extracttextplugin is disabled (so optional).

@MoOx Ah, that was it :smile: Thanks very much for the help.

+1

@MoOx this saved my life

In the .scss file, use the Chinese comments,
will complain ‘Unknown word’,
I have used in scss the @charset 'utf-8'

@MoOx Ah +1

@MoOx gooood job!

@MoOx Thanks!!

Using auto prefixer as last 2 versions of browser doesn't add prefixes but if I remove 'last 2 versions' then it works fine. Can someone tell me how does this happen?
postcss: function () {
    return [autoprefixer({browsers: ['last 2 versions']})];
},

@MoOx
Also, can you please tell me what do you mean by "an array for the default loaders you want to use, the first parameter is used when extracttextplugin is disabled (so optional)."
I mean, by your 'first parameter is optional' will my style-loader be ignored?
loader: ExtractTextPlugin.extract('style-loader', ['css-loader', 'postcss-loader', 'sass-loader'])

@aseem2625 It's because last 2 versions of browsers don't need any prefix. :p

Not related but this is somehow top Google result. Here is my Stylus, PostCSS, Webpack config if someone needs.

I just used it like so loader: 'style-loader!css-loader!postcss-loader!sass-loader' and it works with me, is this may generate any other issue?

@ai I think It should reopen!

@IamManchanda I am not a maintainer anymore =^_^= ask @michael-ciniawsky


Disconnect after sending few request

I am connecting to my openshift cluster using below command
sudo kubefwd services -n <nameSpace>

After sending few requests, I am getting the error  lost connection to pod.

Did you check the pod? is it in a crash loop?
Also, have you tried to kubectl port-forward to a similar pod and if so is that stable?


⚠ ClamAV has degraded performance

In 8cde62d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 82 ms

Resolved: ClamAV performance has improved in 77b61e4.


[WIP] staging: add custom pipelines to run tests

Summary of the PR
Let's use custom pipelines to run tests in the nested worskpace.
Closes #478
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:

[x] All commits in this PR are signed (with git commit -s), and the commit
message has max 60 characters for the summary and max 75 characters for each
description line.
[x] All added/changed functionality has a corresponding unit/integration
test.
[x] All added/changed public-facing functionality has entries in the "Upcoming
Release" section of CHANGELOG.md (if no such section exists, please create one).
[x] Any newly added unsafe code is properly documented.

@stefano-garzarella Can we run full tests suite? Like the normal case here ?

@vireshk yep, this is just a draft to understand how it works ;-)
I'm trying to check if soft_fail works as expected, then I will copy all the tests.

@vireshk can you take a look at the CI report?
For example staging: clippy is failing, but the whole CI is green.
WDYT?

@vireshk can you take a look at the CI report? For example staging: clippy is failing, but the whole CI is green.
WDYT?

I wonder if that will end up making us miss the failures. Maybe skip the softfail part and merge stuff forcefully anyway, which I think we can do.. Or since this is just staging stuff, we can live with such failures for now.

@vireshk can you take a look at the CI report? For example staging: clippy is failing, but the whole CI is green.
WDYT?

I wonder if that will end up making us miss the failures. Maybe skip the softfail part and merge stuff forcefully anyway, which I think we can do..

mmm, I don't think it is a good idea, also for the contributors, seeing the red CI makes you worry.

Or since this is just staging stuff, we can live with such failures for now.

I think this is better, when we have PR for staging, we have to better control that the CI is green for staging as well.
I would have preferred an orange CI, but I don't know how to do it.
@stsquad WDYT?

@stsquad your turn to approve it now, if you agree :)


[BUG] Redirect for frontend request.

Request from the frontend:

https://github.com/SELab-2/OSOC-3/blob/4cf6ff7e3a6338c270f210d13512c889f2db6b12/frontend/src/utils/api/users/admins.ts#L11
https://github.com/SELab-2/OSOC-3/blob/4cf6ff7e3a6338c270f210d13512c889f2db6b12/frontend/src/utils/api/users/admins.ts#L14

Result in a redirect from the backend to /users/?page=...
Do we want to use /users/ or /users

I've also noticed this, not sure if there's anything in the backend that we can change to fix this. It's only for some specific types of requests as well, not all of them. Very strange. I'd say /users/? is kinda ugly & the slash should go.


Change price based on selected variant.

I am working with products that have different prices for different variants, small: $6, medium $9, large $12.
Would be nice to have the price displayed on the product page change depending on the selected variant instead of the highest price.
When the medium variant is selected, the price changes to it's respective price: $9.

This would be an awesome thing to add in your own application, but we do not plan on updating the template for this at this time 🙏


Remove global apiSdk variable in test and make it a local constant

Description
Removed the global let apiSdk: ApiSdk and made it local for every test scenerio to make the tests more atomic.

Related Issue
Resolves https://github.com/bandada-infra/bandada/issues/583

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Hey @jaykayudo could you run yarn prettier:write in the project root and push the changes if only the test file is modified?


draft version of Map.to_list()

not expecting to merge as-is, interested to see if the "default mapping function to pairs" approach can yield fruit

excellent work


Access to the description of the saved objects

save(
    rf, "rf", sample_data=X, description="Random Forest Classifier",
)

It is not clear what happens with the value of the description key. I was expecting to see the description when running mlem list; but it is not the case.

We removed description and labels from MLEM, hence I'm closing this.


Update requirements on manifest

Too many prerequisites. Especially access to all sites that is not necessary

linked to Pull request #41

Dev done.  Will be included in 1.1 version


chore: migrate to cli-table3

Thanks for the PR 🍻
We'll get our CI sorted and merge once ready.

Bump. This is still relevant.

This package has been moved to https://github.com/RobertWHurst/Milieu. I'd create an issue, or update the readme but unfortunately I don't have permission as I don't work for FinTechDev any more.

You're issue has been fixed and I've published a new release.
The version is now 1.7.4


[Error] { StatusCodeError: 429 - {"errors":[{"message":"Rate limit exceeded","code":88}]}

[Error] { StatusCodeError: 429 - {"errors":[{"message":"Rate limit exceeded","code":88}]}
This error way too often???

Hi @sebflex , well, that's bc the Twitter API limits requests. Can't do much about it. You can increase the timeout so it will try less often


[OpenAPI] OAuth

Add OAuth endpoints to the OpenAPI spec.
This is different than the current spec and should be updated
Partially implements: #48

You don't want a callback with the provider also in the url??

You don't want a callback with the provider also in the url??

If you are talking about the {provider} part in the url, thats just as a placeholder. I didn't want to write the same spec for different providers.

Yeah but in the callback url you left out the provider meaning for ex. github and zeus oauth will both end up at the/oauth/callback url. If that's intentional then it's okay but I was wondering if it was.

It was like that in the original backend. With a provider is fine as well, whatever you prefer.

We'll do it with. That way you can still choose to handle them differently if you want to.


Is there a Standard Folder for the models ?

Do the vst3 expect the models to be placed in a certain folder, so I don't have to look for them all the time I'm adding one of your vst3s?
Greetings Peter.

@Petervos2018 thanks for reaching out, the first time you load SmartPedal it will look on the Desktop by default. You can then use the "Load Model" button to select a new default folder for that instance of the plugin. It should save this location if you save your DAW session.  If you copy and paste that instance of the plugin it should also keep that same folder location. If you load a new session with a new instance of SmartPedal you'll have to set the folder again.  Currently there is a bug where if the GUI isn't opened and you load a save DAW session it won't load the folder, but will load once you view the plugin.  This is on my to-do list to fix.
Hope that helps, perhaps in a future version I'll have it look in a more convenient default location, something like ~/Documents/GuitarML/SmartPedal like I do with NeuralPi.


Fix #118, will not return deleted info anymore

Originally try to fix with channel, thinking maybe there leftover in there. But is good to have it to prevent later issue. https://github.com/futurewei-cloud/merak/blob/82e613d13f902b22bbf8fd064cd56db6c2ccc198/services/merak-network/grpc/service/service.go#L78
Now the actual bug was in the network create, a global var was never cleared. That's fixed in this PR.
Have been tested locally, a new image was build yesterday for the .77 env. If that image perform as expected then this PR can be merged.

@yanmo96 Please verify it on .77

@yanmo96 in line#203: sgId := utils.GenUUID(), why you need to generate uuid for sg? why not just let Alcor create one for you?

@yanmo96 in line#219: err := doAttachRouter(routerId, subnetCiderIdMap[subnet], projectId), why you need to use subnet_cider to map subnet_id? I remember the input from scenario manager for router is subnet_gw.
Also, why the router didn't append to the returnMessage?

I will double check if Alcor will give one or not

doAttachRouter

It use the subnet cider to find the subnet id from the map. Then use the subnet id to attach it to router

Will have a new PR to add the router info and gateway info into it

@yanmo96 in line#203: sgId := utils.GenUUID(), why you need to generate uuid for sg? why not just let Alcor create one for you?

I tried to create a security group without an ID, it returned to me without assign a UUID to it. Bellow is the return:
{
    "id": "",
    "project_id": "123456789",
    "tenant_id": "123456789",
    "name": "YM_sample_sg",
    "description": "sg Description",
    "security_group_rules": [
        {
            "id": "8f01055a-eea5-407f-85a1-e1fcee5680e4",
            "project_id": "",
            "tenant_id": "123456789",
            "name": "",
            "description": "",
            "security_group_id": "",
            "remote_group_id": null,
            "direction": "egress",
            "remote_ip_prefix": null,
            "protocol": null,
            "port_range_max": null,
            "port_range_min": null,
            "ethertype": "IPv4"
        },
        {
            "id": "cfbb758a-224d-42fc-8099-fa0e9df30969",
            "project_id": "",
            "tenant_id": "123456789",
            "name": "",
            "description": "",
            "security_group_id": "",
            "remote_group_id": null,
            "direction": "egress",
            "remote_ip_prefix": null,
            "protocol": null,
            "port_range_max": null,
            "port_range_min": null,
            "ethertype": "IPv6"
        }
    ],
    "create_at": "2022-09-19 23:13:58",
    "update_at": "2022-09-19 23:13:58"
}

@yanmo96 in line#203: sgId := utils.GenUUID(), why you need to generate uuid for sg? why not just let Alcor create one for you?

I tried to create a security group without an ID, it returned to me without assign a UUID to it.  The issue earlier was, I didn't specify an ID for it, but ID is a field in the struct, so it put "" as the ID. Will put a fix to it. Thanks

@cj-chung SG ID is not assigned anymore, and the above mention of cleaning the code has been done, with similar cleaning in other places too. Please take a look. Thanks


fix(deps): update module github.com/tubenhirn/dagger-ci-modules/v5 to v5.1.0

This PR contains the following updates:

Package
Type
Update
Change

github.com/tubenhirn/dagger-ci-modules/v5
require
minor
v5.0.1 -> v5.1.0

Release Notes

tubenhirn/dagger-ci-modules (github.com/tubenhirn/dagger-ci-modules/v5)
v5.1.0
Compare Source
Features

use renovate slim image (9d4682b)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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


Create edit command for Consultations

Edit command i.e "edit-consult"

Low priority, will not be implemented. Closing.


Nn translator

Let's merge this so we can quickly move forward with training the net. @torinfs, if you want these changes in the future (also curious about the reason for input.txt), you can open an issue so that we don't lose track of these


west: Update hal_stm32 module for stm32f1 series cube update

Update Cube version for STM32F1XX series
from version: V1.6.1
to version: V1.7.0
Requires zephyrproject-rtos/hal_stm32#5
Signed-off-by: Erwan Gouriou<EMAIL_ADDRESS>

recheck

Shippable failed due to qemu.
Will launch again tomorrow morning

recheck

Superseded by #16984


[CropperJS] Edit the cropper image

Hi everyone, I need to crop my image based on my file input, but the cropper is not allowing me to edit the image. I want to know if it is possible to do something like this to update the cropper:
import { Controller } from '@hotwired/stimulus';
import Cropper from 'cropperjs';
import CropEvent = Cropper.CropEvent;

export default class CropperController extends Controller {
    declare readonly publicUrlValue: string;
    declare readonly optionsValue: object;
    declare img: HTMLImageElement;
    declare cropper: Cropper;

    static values = {
        publicUrl: String,
        options: Object,
        img: HTMLImageElement,
        cropper: Cropper
    };

    connect() {
        this.initializeCropper();
    }

    initializeCropper() {
        // Remove any existing cropper image and instance before initializing
        if (this.img) {
            this.img.remove();
        }
        if (this.cropper) {
            this.cropper.destroy();
        }

        // Create image view
        this.img = document.createElement('img');
        this.img.classList.add('cropperjs-image');
        this.img.src = this.publicUrlValue; // The current image URL value

        const parent = this.element.parentNode;
        if (!parent) {
            throw new Error('Missing parent node for Cropperjs');
        }

        parent.appendChild(this.img);

        // Options for the cropper instance
        const options = this.optionsValue;

        // Dispatch pre-connect event
        this.dispatchEvent('pre-connect', { options, img: this.img });

        // Build the cropper with the given image and options
        this.cropper = new Cropper(this.img, options);

        // Event listener to update the input value on crop
        this.img.addEventListener('crop', (event) => {
            (this.element as HTMLInputElement).value = JSON.stringify((event as CropEvent).detail);
        });

        // Dispatch connect event
        this.dispatchEvent('connect', { cropper: this.cropper, options, img: this.img });
    }

    // Method to update the image URL and reinitialize the cropper
    updateImage(newImageUrl) {
        this.img.src = newImageUrl; // Update the public URL value
        this.initializeCropper(); // Reinitialize the cropper with the new image
    }

    disconnect() {
        if (this.cropper) {
            this.cropper.destroy();
        }
        if (this.img) {
            this.img.remove();
        }
    }

    // Helper method to dispatch events
    private dispatchEvent(name: string, payload: any) {
        this.dispatch(name, { detail: payload, prefix: 'cropperjs' });
    }
}

I’m not entirely sure about the expected behavior you’re aiming for.
The current CropperJS implementation is designed to crop an existing image, and adapting it to work with non-uploaded images would require quite a few changes to its code. :/
    // Method to update the image URL and reinitialize the cropper
    updateImage(newImageUrl) {
        this.img.src = newImageUrl; // Update the public URL value
        this.initializeCropper(); // Reinitialize the cropper with the new image
    }

This snippet wouldn’t work as expected because this.img gets reset right after the line // Create image view. I suppose you meant to reference this.publicUrl instead?
If you need this kind of behavior, one possible solution could be to set the initial HTML inside a <template> tag and dynamically create the <div> whenever you have a new imageUrl.
Alternatively, maybe consider a custom controller? You could use the various events dispatched by the UX controller?


Don't hardcode project name for system tests

Currently hardcoded to cloud-python-runtime-qa in the Dockerfile.

#67


Docker build still failing

Recent changes have not fixed the docker build issues. Need some more attention on this.

@SchrodingersGat seems to work now

Yeah, adding a step to update setuptools within the docker container got it to work. Idk why, but at least now it works.


Status panel is not shown in v0.19.2-alpha1

Are you requesting a feature or reporting a bug?
Bug
What is the current behavior?
Status panel is not show in both regular and debugging modes
What is the expected behavior?
Status panel must be visible
How would you reproduce the current behavior (if this is a bug)?
Run any test
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code

Specify your

operating system: Windows 10
testcafe version: 0.19.2-alpha1
node.js version:

I'm working on this

It seems it works properly

Just for reference, reinstalling of node_modules is required.

on my side it worked without reinstalling. It seems it depends


Receiving Events in the Background on Android

Thanks so much for your great library @MrHertal!
Running on Android 11 with Firebase Messaging configured, I can receive FCM notifications in the background from an incoming call and answer this call as well. I see the following message on logcat as the call is received:
 D/TwilioPhone: Call did connect
However, this event is not received in the event listener in my App.tsx file (I've defined the listeners as you have in your example project). The events are received as expected in App.tsx if the incoming call is initialed while the app is in the foreground. Any thoughts as to why this event is not sent back through the React context and to the JS listener while the app is in the background?

Hi @hsandhu, thanks for your message!
This is normal behavior because when app is in background, code is executed independently of React context.
When you are calling handleBackgroundState, messaging().setBackgroundMessageHandler is registering a headless JS task. The task code is independent and has no access to React context (this context does not even exist since app is in background).
But you can still listen to CallConnected event within that function. You could copy handleBackgroundState and write something like:
import messaging from '@react-native-firebase/messaging';
import { AppRegistry, Platform } from 'react-native';
import RNCallKeep from 'react-native-callkeep';
import {
  RNTwilioPhone,
  TwilioPhone,
  twilioPhoneEmitter,
} from 'react-native-twilio-phone';
import { name as appName } from './app.json';
import { App } from './src/App';

function handleBackgroundState() {
  if (Platform.OS !== 'android') {
    return;
  }

  messaging().setBackgroundMessageHandler(async (remoteMessage) => {
    if (!remoteMessage.data) {
      return;
    }

    RNCallKeep.registerPhoneAccount();
    RNCallKeep.registerAndroidEvents();
    RNCallKeep.setAvailable(true);

    RNTwilioPhone.listenTwilioPhone(); // Listen to events after this line because listeners are removed here
    RNTwilioPhone.listenCallKeep();

    // Here you can listen to events and do what you want
    twilioPhoneEmitter.addListener('CallConnected', (data) => {
      console.log(data);
    })

    TwilioPhone.handleMessage(remoteMessage.data);
  });
}

handleBackgroundState();

AppRegistry.registerComponent(appName, () => App);

@MrHertal this is really help and makes sense, thank you!


Hover for annotated explorer entry shows up in wrong spot

I did rename a file that was under git control.

Can't repro. Can you consistently?

We closed this issue because we are unable to reproduce the problem with the steps you describe. Chances are we've already fixed your problem in a recent version of VS Code. If not, please ask us to reopen the issue and provide us with more detail. Our issue reporting guidelines might help you with that.
Happy Coding!

Sorry, but this still reproduces for me, is there something I can add as logs?

Ideally I would need exact steps starting from a clean repository up to seeing the bug. It's very hard to tell how this problem could be caused.

I think it's being caused by "explorer.experimental.hover": true. Can you remove it and see if it is still the case? If so, we can close this issue as the plan is to remove that setting.

@benibenj yes you are right! I forgot that I had configured it, why are we still carrying around an extra custom hover for the explorer?

I thought it was going to be removed but I can do it now #205061


Add Depth Offset property to BaseMaterial3D and fix collision shape gizmo flicker

Follow-up to https://github.com/godotengine/godot/pull/90644.

This has several use cases:

Prevent collision shape gizmos that overlap with geometry from Z-fighting, which causes flickering in motion.
Draw meshes that overlap other meshes without Z-fighting, which is useful for mesh-based decals (without needing to offset them from the surface manually).

This paves the way for implementing https://github.com/godotengine/godot-proposals/issues/1000.
This closes https://github.com/godotengine/godot/issues/99184.

Testing project: test_depth_offset.zip
Preview
Debug collisions
Without depth offset

With depth offset

Debug collisions (supersampled)
2.0 render scale + 8x MSAA 3D.
Without depth offset

With depth offset

Debug collisions in motion
Without depth offset
https://github.com/user-attachments/assets/47b6d731-592c-4108-85b4-20f49b20844c
With depth offset
https://github.com/user-attachments/assets/815a81ec-3cb8-4c53-8055-9c3536d19afa
CSG node gizmos
Without depth offset

With depth offset

Mesh-based decal
Both planes are at the same height as the box they're resting on (no offset is applied to the mesh's vertices).
Without depth offset
Z-fighting occurs and is most visible when the camera moves or rotates.

With depth offset
No more Z-fighting.

The test scene seems broken in the Compatibility renderer:
https://github.com/user-attachments/assets/f86cb8a1-518c-488e-af0d-df55347b5010
However, it only seems to happen when MeshInstance3D3's Depth Offset Amount is something small and negative, like the current -0.005, but stops happening with large negative values.

I don't see justification for why this feature is modifying the depth offset in the fragment function when this NDC z manipulation can be done in vertex with minimal performance overhead
Writing to DEPTH is very performance heavy since it disables early-z optimization. Any option with a hidden performance cost ought to be justified and explained to the user, assuming it is even desirable in the first place.

Enabling depth offset forces the material to go through the transparent pipeline

Why? It does not write to alpha. If writing to DEPTH changes the transparency mode, that sounds like a renderer bug. In my opinion, Opaque vs transparent pipeline should be an explicit choice and not left up to seemingly opaque logic that relates to whether or not half a dozen variables are referenced in the code.

If writing to DEPTH changes the transparency mode, that sounds like a renderer bug.

It doesn't, but the depth prepass will introduce random black pixels (or make the material fully black if you push pixels away from the camera).


nixos/hadoop: Add HA services and HTTPFS

Motivation for this change
The PR makes it possible to deploy a highly available HDFS/YARN cluster with automatic failover

Add HTTPFS module for webHDFS
Add HDFS journalnode and ZKFC services for HA deployments
Update tests for new services

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)
[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/629

@lovesegfault while the openfirewall description change you suggested is not a convention seen in nixpkgs, it did bring a few copy-paste errors around firewall configs to my attention. Thanks!


Load large DICOM series issue

Large DICOM series can't be loaded correctly. I have a dataset of 1000 x 1000 x 1000 pixels, but AMI can render only half of the slices, while the others are not rendered. This is the error shown in the console:

If you need a large dataset to test this issue I can share it with you.

AMI: v0.0.22
THREEJS: v87

Have the same errors on AMI 0.0.23dev

I think if requiredTextures from this line is higher than
(new THREE.WebGLRenderer()).capabilities.maxTextures
then we got this warning

Now maximum 7 textures is used, however (new THREE.WebGLRenderer()).capabilities.maxTextures equals to 16 on my PC.
So if I changed in this line 7 to 15 and add similar lines here then number of frames AMI can show increases.

Thank you for the hint! Anyway, I don't see any improvements also with your changes. I have a 1000x1000x1000 stack.

@NicolasRannou here is the download link: https://wetransfer.com/downloads/5c2ce2217b9d8502b86ef54676ad30d120180406075934/83894508ab17d9e93bc0be6a4dd5587120180406075934/b93d5c. This is a 512x512x512 multiframe series. If you need the 1000x1000x1000 stack I'll share that too, but you can see the same issue also here.

FYI - I narrowed down the issue and we can fix 2 different levels:

Increase texture size
Increase number of textures

Increasing the texture size should be pretty straightforward but I ran into some precision issues in the fragment shaders that need to be figured out.
Increasing the number of texture is easier in the sense it will work for sure but the build system must be adjusted to support a variable number of textures.
in any case, to display 1000x1000x1000 voxels (assuming 16bits per voxel), we need to perform both improvements. Just bumping the texture size is almost but not quite good enough.
1000 x 1000 x 1000 =<PHONE_NUMBER> voxels
8192 x 8192 x 7 x 2 =  939524096 voxels

Unfortunately, I don't have any CT with 10001000 dimensions (512512 up to 3500 frames will work fine).
Right now I have only one US which doesn't fit into limit, but it can't be anonymized.
However, you can enable multiframe US merging info one series and it will be easy to find testing sample.


Install Error (PowerShell)

Describe the bug
When I put the command to install the program, Windows PS gives me an error.
To Reproduce
Steps to reproduce the behavior:

Go to Windows PowerShell
Paste iwr -useb https://christitus.com/win | iex
Execute the command
See error

Expected behavior
No install error
Screenshots

Additional context
I executed PS as administrator and It still doesnt work.

Help?

try using this for the URL
https://raw.githubusercontent.com/ChrisTitusTech/winutil/main/winutil.ps1

You can see your solution in read.me line 22.
If you are having TLS 1.2 Issues or You cannot find or resolve christitus.com/win then run with the following command:
[Net.ServicePointManager]::SecurityProtocol=[Net.SecurityProtocolType]::Tls12;iex(New-Object Net.WebClient).DownloadString('https://raw.githubusercontent.com/ChrisTitusTech/winutil/main/winutil.ps1')

Thank you so much for the help! It finally worked :D


CKG unauthorized login

Hi,
First of all, congratulation for the CKG paper release. We have set up the docker image of the CKG app in our lab but we encounter a issue at the step where we want to create our personnal account in the Admin tab of the web browser access CKG app.
We have filled all the requested field for new account creation and a new user ID was created. However, when we want to log in our account, we use the same new user ID for ID and password because I have read that for our first log the ID/PW are identical but it says that one or the other is invalid and therefore prevent us to connect in our new account.
Can you help me with this point?
Thanks for your help.
Best regards
KR

Hi,
I could not reproduce the error. It would be great if you could detail a bit more the steps you followed and also if you could access the log files in the docker image:
$ docker exec -it ckgapp bash

Then navigate to /CKG/log and check the report_manager.log and graphdb_builder.log files to see if there was an error. You could provide the files if you need help.
Check #70 first to make sure the graph structure is correct.

Hi @albsantosdel,
For the user creation, I have followed the step here :
https://ckg.readthedocs.io/en/latest/intro/getting-started-with-docker.html#ckg-docker-container
After logged in with the user/PW provide in the previous link (test_user), I went to the admin page and followed steps of this link: https://ckg.readthedocs.io/en/latest/intro/create-new-user.html  ("From an CKG’s app:" part).

Then, a message told me that a new user was successfully created and I used the user name provided to log in again using the same name for ID and PW and told me that username or password was invalid.
In docker desktop, in the Image tab, it is written that the image is already in use and the container is running.
When a try the following command:
$ docker exec -it ckgapp bash
I get the folllowing message :

I don't see any log in the CKG path below: CKG: /CKG/log

Here is all the files/folder present in my CKG folder:

Sorry I am a little bit new with git bash, I'm probably doing something wrong. How can I have access to the log with the above command ?
Thanks for your help.
Best.
KR

Can you check the content of report_manager.log, and graphdb_builder.log? If there was an error when creating the user, it may be in there.

How can I do that in the Bash session ? Because I only see the log files in the Bash session when I do ls after cd CKG/log. I don't even have a folder named "log" in CKG/log path in the clone repository. Are those different things ? What I see in the Bash session and what I see in the github cloned repository ?
Thanks for tour help

Hi,
With docker exec -it ckgapp bash you open a command line session in the container. You can then navigate to CKG/log with cd CKG/log and read the content of the log files using for instance cat:
cat report_manager.log
cat graphdb_builder.log
You can then look at the last entries in those files to see if there is any error when creating the user. It may be that we are not capturing the error properly and that's why we don't see it in the interface.

Hi,
Thanks for your reply. I just did what you say in your reply and here is what I get:

I check the same log files with cat during a new creation of a user profile but the log never get updated, they always show some info about matplotlib dependency.
I have also try to create again a new profile using the exact same info that I used in the first time and I get this message:

– Error creating new user: Email already registered –

So the profile already exists. As a remainder, in order to log in for the first time I used the same user ID that is display after creating a new profile and same for password but I have the following message:

Invalid user name or password

Do you think that it might be possible to have a issue with the minimal update ?
I have also read #72 and I was wondering if I had every dependencies in the requirements.txt file so I have attached this file also.
requirements.txt
Thanks again for your help.


bump requirements

Is it too late to include a fresh release of spreg? Yesterday @pedrovma asked me to cut a new one. After some infrastructure updates in pysal/spreg#99 it will be ready to go.

I think we should hold off as we want to stick with the policy of freeze july 1?

I think we should hold off as we want to stick with the policy of freeze july 1?

Ah! I got my months confused. I thought it was an August 1st freeze :face_in_clouds:

Thank you so much, @jGaboardi ! My bad.


[Feature] Add hard drive temperature

Description of the feature
Can you add the hard disk temperature to the storage module, thank you.
Additional context
No response

Hi there. How would you envision this feature? Like, where could the extra data be displayed for both the single drive view, and the multi-drive view?
Also, honestly, I don't even know if that data is even readable from within Docker - could you maybe send me an output of the following command:
docker container run -it --rm -v /:/mnt/host:ro --privileged mauricenino/dashdot yarn cli raw-data --storage

Thanks for your reply, If possible, add a few more lines to the list of data on the left to show the temperature data for each drive.
but it looks like it is not possible to get the temperature data within docker.

const disks =  [
{
device: '/dev/nvme0n1',
type: 'NVMe',
name: 'SKHynix_HFS512GDE9X084N                 ',
vendor: '',
size:<PHONE_NUMBER>92,
bytesPerSector: null,
totalCylinders: null,
totalHeads: null,
totalSectors: null,
totalTracks: null,
tracksPerCylinder: null,
sectorsPerTrack: null,
firmwareRevision: '',
serialNum: 'CSA3N627111003H2C',
interfaceType: 'PCIe',
smartStatus: 'unknown',
temperature: null
}

Hi I think you can use smartctl.
You can pass the volume path to the container using the -v option: docker run -v /path/to/volume:/data my-image
You will need to Install the smartmontools package inside the Docker container

I found can use lm-sensors directly within docker to get nvme temperature, so maybe can develop from that.
/app # sensors
nvme-pci-0600
Adapter: PCI adapter
Composite:    +43.9°C  (low  =  -0.1°C, high = +82.8°C)
(crit = +83.8°C)
Sensor 1:     +36.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +38.9°C  (low  = -273.1°C, high = +65261.8°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +110.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +41.0°C  (high = +105.0°C, crit = +105.0°C)
Core 0:        +38.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:        +39.0°C  (high = +105.0°C, crit = +105.0°C)
Core 2:        +38.0°C  (high = +105.0°C, crit = +105.0°C)
Core 3:        +42.0°C  (high = +105.0°C, crit = +105.0°C)
nvme-pci-0100
Adapter: PCI adapter
Composite:    +39.9°C  (low  =  -0.1°C, high = +74.8°C)
(crit = +89.8°C)


Support test

contract-utils is too old, it seems a backport of an cep47 contract otherwise getting
bridge-casper-smart-contracts/utils/contract-utils/src/contract_storage.rs:2:11
  |
2 | use core::lazy::OnceCell;
  |           ^^^^ could not find `lazy` in `core`

error[E0152]: duplicate lang item in crate `std`: `panic_impl

remove this contract utils if possible to update all the libraries further

also this seemed to work out of the box
[dependencies]
casper-contract = "1.4.4"
casper-types = "1.5.0"
contract-utils = { path = "../utils/contract-utils" }
# k256 = "0.13.0"

secp256k1 = "*"


draft a caption text & title

@jiwalker-usgs added this description:
Water use data has been collected and compiled by the USGS since 1950.  This data has changed over time in terms of how it was categorized and at what spatial scale it was summarized to.  This visualization shows that change over time as this dataset has become more powerful, and attempts to illustrate where the data can go in the future to be a more useful dataset going forward.

thought it would be a nice place to start

related vizzies:

CA drought
CO drought


Add TaskSetDefinition as required configuration for ECS deployment

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #2011
Does this PR introduce a user-facing change?:

NONE

Nice
/lgtm

/approve


Precision fails when using negative ignored index

🐛 Bug
When setting ignore_index=-1 accuracy can be computed, but precision fails with the following error:
Traceback (most recent call last):
  File "/home/ubuntu/.pyenv/versions/3.9.12/lib/python3.9/code.py", line 90, in runcode
    exec(code, self.locals)
  File "<input>", line 18, in <module>
  File "/home/ubuntu/pycharm/projects/ai-models/venv/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/ubuntu/pycharm/projects/ai-models/venv/lib/python3.9/site-packages/torchmetrics/metric.py", line 248, in forward
    self.update(*args, **kwargs)
  File "/home/ubuntu/pycharm/projects/ai-models/venv/lib/python3.9/site-packages/torchmetrics/metric.py", line 312, in wrapped_func
    update(*args, **kwargs)
  File "/home/ubuntu/pycharm/projects/ai-models/venv/lib/python3.9/site-packages/torchmetrics/classification/stat_scores.py", line 185, in update
    tp, fp, tn, fn = _stat_scores_update(
  File "/home/ubuntu/pycharm/projects/ai-models/venv/lib/python3.9/site-packages/torchmetrics/functional/classification/stat_scores.py", line 154, in _stat_scores_update
    preds, target, _ = _input_format_classification(
  File "/home/ubuntu/pycharm/projects/ai-models/venv/lib/python3.9/site-packages/torchmetrics/utilities/checks.py", line 432, in _input_format_classification
    target = to_onehot(target, max(2, num_classes))  # type: ignore
  File "/home/ubuntu/pycharm/projects/ai-models/venv/lib/python3.9/site-packages/torchmetrics/utilities/data.py", line 99, in to_onehot
    return tensor_onehot.scatter_(1, index, 1.0)
RuntimeError: index -1 is out of bounds for dimension 1 with size 2

I also tried to use a positive number, say 1000 and I get an error for Accuracy too:
ValueError: The highest label in `target` should be smaller than the size of the `C` dimension of `preds`.

To Reproduce
import torch
import torchmetrics

print('torch', torch.__version__) #  1.11.0+cu102
print('torchmetrics', torchmetrics.__version__) # 0.8.1

accuracy = torchmetrics.Accuracy(ignore_index=-1)
precision = torchmetrics.Precision(ignore_index=-1)

preds = torch.Tensor([
    [0.2, 0.3],
    [0.8, 0.7],
])
target = torch.IntTensor([-1, 0])

print('accuracy', accuracy(preds, target))  #  tensor(1.)
print('precision', precision(preds, target))  # error (see above)

Expected behavior
Precision ignores the index -1.
Environment

TorchMetrics version 0.8.1
Python & PyTorch Version (e.g., 1.0): 1.11.0+cu102

If the error above is really a bug and you can to point to the proper place where the ignored labels should be handled, I'll be happy to work on a fix.

Hi @mfoglio,
We are fully aware of this issue that our classification metrics does not out of the box support negative index. We will make this part of a greater refactor of the classification package (this issue #1001) in the upcoming weeks.

Issue will be fixed by classification refactor: see this issue https://github.com/Lightning-AI/metrics/issues/1001 and this PR https://github.com/Lightning-AI/metrics/pull/1195 for all changes
Small recap: This issue ask for support that ignore_index can be outside the [0, num_classes] range for precision metric. After the refactor, all new classification metrics support this. Here is an example for precision:
from torchmetrics.functional import binary_precision
import torch

preds = torch.tensor([0.2, 0.7, 0.6, 0.3])
target = torch.tensor([1, 1, 0, 0, -1])

binary_precision(preds_prob, target_prob, ignore_index=-1)  # tensor(0.5000)

Issue will be closed when https://github.com/Lightning-AI/metrics/pull/1195 is merged.

Fantastic! Thank you!


replace promise to 프라미스

You can merge pr by yourself, if encount permission issue just @ me.

okay! thank you :)


Fix for Ruby 3.2.0

➜ ./username-anarchy -i test-names.txt
./username-anarchy:238:in `load_names_list': undefined method `exists?' for File:Class (NoMethodError)

        raise "#{filename}: No such file" unless File.exists?(filename)
                                                     ^^^^^^^^
Did you mean?  exist?
        from ./username-anarchy:606:in `<main>'

Starting in Ruby 3.2.0 the exists? (pluralized) alias for exist? seems to has been removed.
Fixed it by renaming File.exists to File.exist on line 238.

Thanks pwnter


Add custom_data option

Use this option to store non-Attributor-related metadata about an attribute. This data must be a hash; apart from that, there is no validation.

@blanquer I haven't added 'signed-off-by' or 'closes' to the commit yet because I'm not sure if there's more to #113 than the simple change I've made here.

looks good to me @smcgivern !
For completeness, though, I would add 2 things:
1- A very simple test case in the ".describe" part of the attribute spec, that checks that an attribute with custom_data options ends up appearing in the description output (very similar to this one: https://github.com/rightscale/attributor/blob/master/spec/attribute_spec.rb#L56-L63 )
2- Add a line to the changelog (next section) about the addition.

Commit amended :+1:

LGTM


Should copy from static/* instead of static/

I am not sure about this, but I think when building for production (via npm run build), the script should copy from "static/*" (note extra asterisk) instead of "static/". Please correct me if I am wrong.

@anishkny Is the current version not working for you?

@chrisvfritz yes.
If I have a file in static folder say static/1.jpg which I reference in a component template using src="static/1.jpg", and then I execute npm run build, the dist folder contains:
$ find dist  dist dist/index.html dist/static dist/static/css dist/static/css/app.25ce96f5916d7c45284405632fc01fda.css dist/static/css/app.25ce96f5916d7c45284405632fc01fda.css.map dist/static/js dist/static/js/app.74fbd7b2bb622359ef08.js dist/static/js/app.74fbd7b2bb622359ef08.js.map dist/static/js/manifest.361d103eeea14378fca7.js dist/static/js/manifest.361d103eeea14378fca7.js.map dist/static/js/vendor.d51411e26c162045089b.js dist/static/js/vendor.d51411e26c162045089b.js.map dist/static/static dist/static/static/.gitkeep dist/static/static/1.jpg        <----- causes 404 in prod version
This change seems to fix it without breaking anything else. New dist folder contents:
$ find dist dist dist/index.html dist/static dist/static/1.jpg                 <------- good! dist/static/css dist/static/css/app.25ce96f5916d7c45284405632fc01fda.css dist/static/css/app.25ce96f5916d7c45284405632fc01fda.css.map dist/static/js dist/static/js/app.d208067752c7dcaa01c8.js dist/static/js/app.d208067752c7dcaa01c8.js.map dist/static/js/manifest.a871c5db51318bf613a4.js dist/static/js/manifest.a871c5db51318bf613a4.js.map dist/static/js/vendor.d51411e26c162045089b.js dist/static/js/vendor.d51411e26c162045089b.js.map

Thanks for the explanation!


Fix rtapp calibration

This is a simple series which should fix RTApp calibration on systems with Android >=N as well as add some sanity checks on calibration values computed on big/LITTLE systems.

LGTM, there are just some misspellings in the second commit message. If you could correct those, I'm happy to merge this.
First line: s/alwasy/always/
Second line: s/It/If/


Feature/add support for rabbitmq 6 0 0 and switch to netstandard2 0

Upgraded to rabbitmq 6.0.0 and netstandard 2.0 thanks to @niwrA and @Samuron

Removing LGTM


Put name as hyperref into Xing/LinkedIn instead of the profile-identification to the profile page

Hi,
just want to add a little thing here:
When using i.e. \xing{} or \linkedin{} it had as an argument the specific profile identification on the corresponding page (Xing, or LinkedIn). Simply copying what was already done for googlescholar ID in the awesome-cv.cls gives the name with the Xing/LinkedIn symbol as a hyperlink to the profile, instead of the profile-identification of the corresponding profile.
Just added (You can do this for each other linked profile, that you want):
\newcommand*{\linkedin}[2]{%
  \def\@linkedinid{#1}%
  \ifthenelse{\equal{#2}{}}{%
    \def\@linkedinname{\@firstname~\@lastname}%
  }{%
    \def\@linkedinname{#2}%
  }%
}

\ifthenelse{\isundefined{\@linkedinid}}%
        {}%
        {%
          \ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
          \href{https://www.linkedin.com/in/\@linkedinid}{\faLinkedinSquare\acvHeaderIconSep\@linkedinname}%
        }%

linkedinid is the your former used profile-specification, that is leading to your profile on LinkedIn.

Thanks @CodingChristoph, I was looking for this.
Strict copy paste of your solution crashed compilation. Looks like "faLinkedinSquare" was undefined on my side. Fixed like this :

 \ifthenelse{\isundefined{\@linkedin}}%
        {}%
        {%
          \ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
          \href{https://www.linkedin.com/in/\@linkedin}{\faLinkedin\acvHeaderIconSep\@linkedin}%
        }%
\ifthenelse{\isundefined{\@linkedinid}}%
        {}%
        {%
          \ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
          \href{https://www.linkedin.com/in/\@linkedinid}{\faLinkedin\acvHeaderIconSep\@linkedinname}%
        }%

```use as` \linkedin{linkedinid}{desired name to appear on pdf}`

Thanks again !

Thanks to you both!
@videlc 's Version worked for me for the cover letter template, but not the CV itself.
I removed the acvHeaderIconSep and changed the headersocialsep command.
The CV version that worked for me was:

⚠ Full disclosure: I don't know Latex, I just changed the commands around until the error disappeared. ⚠

     \ifthenelse{\isundefined{\@linkedin}}%
            {}%
            {%
              \ifbool{isstart}{\setbool{isstart}{false}}{\@headersocialsep}%
              \href{https://www.linkedin.com/in/\@linkedin}{\faLinkedinSquare\@linkedin}%
            }%
    \ifthenelse{\isundefined{\@linkedinid}}%
            {}%
            {%
              \ifbool{isstart}{\setbool{isstart}{false}}{\@headersocialsep}%
              \href{https://www.linkedin.com/in/\@linkedinid}{\faLinkedinSquare\@linkedinname}%
            }%


playback stopped working in new version of pf2[ISSUE]

Describe the bug
in the latest version of pf2 the playback and the shortcut for rolls have stopped working. there was some major refactoring in the new version of the system which i think has affected the mod.
To Reproduce
Steps to reproduce the behavior:

Go to have a playlist
Click on play
no sound happens.
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Version Information

Quick Combat:
FoundryVTT:
System:
Other Modules:

Additional context
Add any other context about the problem here.

so I took a look at it, and I was one PF2E version 4.6.6 and wasn't able to recreate the error, can you give me the specific error message you are seeing?

yeh ive checked it recently and it does work but the playback is disjointed not sure if its anything to do with the mod.  something happened between then and the update that made it work.

so I made some major changes on how everything works with this mod, and "hopefully" your issues are now fixed can you give it a shot and let me know if you find anything

so I made some major changes on how everything works with this mod, and "hopefully" your issues are now fixed can you give it a shot and let me know if you find anything

thanks i really hope the intiative thing is sorted also, so it requests from players when players are selected and there was an issue of npc tokens not rolling initative either. i really look forward to the fix!

is this still causing you issues?

yes id love to show you as its not working fully

issue was with another Mod blocking combat from starting with unrolled initiatives Monk's Little Details. Will add a note and possibly a popup warning.


Unity scene generates only partial map

Opening the scene and pressing play generates only partial level and the player drops through the world:

Should I do some preparation in Unity with maybe the "Create module data" or "Initialize" buttons or is the scene somehow broken?
Thanks a lot for creating this beautiful project!

Sorry you're having problems. You don't need to use any buttons. I just cloned the project from scratch, opened the scene, pressed Play and it worked.
Did you get any warnings or errors when you opened the project?
Can you check if any of the children of the Prototypes node have MeshRenderers with missing meshes?
Do you have Blender installed on your PC?

I just had the same problem, the MeshRenderers had missing meshes, could fix it via:

open Assets\blocks.blend in Blender 2.79
disable all "eyes" in the hierarchy (only three nodes for the tower clock)
save it (ctrl+c and mouse click)
Unity should reload the blend file
press play
should work

I don't know if disabling the visibility is needed or just the "save blend file" to trigger Unity to reimport

That did the trick kungfooman!
I just installed Blender, opened blocks.blend and saved the file and that was it.
A big thank you to both of you :)

Even after saving in Blender, I see the same 'partial' map issue:

It definitely seems like certain pieces of the mesh are simply not visible - the player seems to collide with invisible boundaries when moving around, and you can see the slots assembling on multiple vertical levels:

Any guesses or intuition about what other reasons might cause this would be greatly appreciated!

What do you see in the Prototypes scene? I assume that some prototypes have meshes while others dont't. Can you confirm this?
There was a problem that looked like your screenshot, but it was fixed a while ago. Can you confirm that you're on the latest commit (it doesn't matter if you pulled the changes from today).
The invisible walls appear because the colliders are created directly in Unity and are thus imported correctly. Only the visual mesh is missing, everything else is there.
Please do the following:

Delete all project files
Use git clone to download the project again
Open blocks.blend in Blender and save it (like you did to get the screenshot above)
Open the project in Unity and check if this solved it

If the problem persists, you can do this:

Open the Prototypes scene
Edit the Prototypes prefab
Look for modules with missing meshes. In the MeshFilter component, it should say something like "Interior door (missing)". Click on the circle next to it, search for the name (like "Interior door") and select the mesh.

If you can fix the meshes like this, they will appear in the game again.

Apologies for the slow response - back on the grid and looking to work with your project again! FWIW, it seems that manually updating MeshFilter assignments in the Prototype scene works, but I switched over to a Windows machine and everything works perfectly there, so going to proceed on that tact!
Thanks again for your thorough help and advice.


When a new node is registered the central admin gets info and enables

Registering a node should:

Create a file /registrations/disabled/{nodeid} with domain or IP, node ID, email, username, application text ("hi, I am just a normal person who wants to create a node")
If node ID is added to list /registrations/enabled/nodes then the site is enabled.

I would not use files - all data related to nodes can be stored in the central database

This will be on the NODE page here:
https://github.com/mreider/koto/issues/48
I will add another story of the things you can do on the node page.

I am not sure this is finished. It looks like normal users get the approve buttons?


!pool page is corrupted

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/-pool
YAML Front matter is not parsed.

Thanks again, @nitoyon, for your eagle eye.  This is fixed, and we have identified ~10 other instances of this problem that will be fixed soon.

Thank you for the quick fix!


Notebooks - Language attribute in kernelspec metadata gone

VS Code Version: 1.61.0-insider
OS Version: Windows

Steps to Reproduce (in both VS Code and Jupyer):

Create new notebook
Save

VS Code Jupyter Notebook

Jupyter Notebook

Not having the language attribute breaks tools like papermill

Could it be that this again is not working? (VSCode 1.63.2)


Testing Notifications

Create a script to anonymize the db from beta (prod) -> dev (avoid mistakenly sending emails to users, among other things), can just reuse Elise's script to create a db sample here
Add a "SEND_ALL_MAIL_TO" flag in order to redirect emails to the tester's account
Add a "MAIL_FREQUENCY_MIN" env variable that will be set to 60 for prod (and by default) but can be set to e.g. 1 for speed of testing
Add unit tests to the CP notifications

Test notifications for

Mention in comments (make a comment mentioning a few users)
Resolution (Resolve a question I predicted on)
Significant movement on predicted question (artificially add 100 forecasts of 0 to a question that's ~1 that I predicted on)
Follow a question and test:
Notifications for every 3 new comments
Warn on small CP changes
Artifically advance lifetime and check milestone notification
Check specific time notification for e.g. 2 minutes from now

@George3d6
Missing:

Status change on question I follow (e.g. in-review→upcoming or open→close).
Question opens in tournament I follow.

Ok, will do those 2 as well :)
Curious how easy I'd be to automate all of these as part of the integration tests but my hunch if "pretty hard"

Comment notifications work

Open/Close/Resolve work
CP change works
New comments on followed questions don't send notifications.
New questions in followed tournaments don't send notifications.

@hlibowski I don't see a very easy fix/solution for:

Notifications being sent on posts you follow when a certain nr of unread comments appear
Notifications being sent when a new post is opened in a tournament you follow

Could you look into these 2 + add unit tests for them ?


feat(denommetadata): wire the denommetadata ibc middleware

Description
ssee https://github.com/dymensionxyz/dymension-rdk/pull/455/files
Closes #282
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.
PR review checkboxes:
I have...

[ ]  Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ]  Targeted PR against the correct branch
[ ]  included the correct type prefix in the PR title
[ ]  Linked to the GitHub issue with discussion and accepted design
[ ]  Targets only one GitHub issue
[ ]  Wrote unit and integration tests
[ ]  Wrote relevant migration scripts if necessary
[ ]  All CI checks have passed
[ ]  Added relevant godoc comments
[ ]  Updated the scripts for local run, e.g genesis_config_commands.sh if the PR changes parameters
[ ]  Add an issue in the e2e-tests repo if necessary

SDK Checklist

[ ] Import/Export Genesis
[ ] Registered Invariants
[ ] Registered Events
[ ] Updated openapi.yaml
[ ] No usage of go map
[ ] No usage of time.Now()
[ ] Used fixed point arithmetic and not float arithmetic
[ ] Avoid panicking in Begin/End block as much as possible
[ ] No unexpected math Overflow
[ ] Used sendCoin and not SendCoins
[ ] Out-of-block compute is bounded
[ ] No serialized ID at the end of store keys
[ ] UInt to byte conversion should use BigEndian

Full security checklist here
----;
For Reviewer:

[ ]  Confirmed the correct type prefix in the PR title
[ ]  Reviewers assigned
[ ]  Confirmed all author checklist items have been addressed

---;
After reviewer approval:

[ ]  In case the PR targets the main branch, PR should not be squash merge in order to keep meaningful git history.
[ ]  In case the PR targets a release branch, PR must be rebased.

@zale144 why did we remove the authz and feegrant module?

@zale144 why did we remove the authz and feegrant module?

bad merge. I'll fix it


Install dependencies using Composer

Oops sorry, looks like I previously submitted a PR that was rejected.  I'll go ahead and close this.