Error when converting frontend.Variable to Field

Hello,
I'm fairly new to writing circuits directly using gnark, and I am currently facing an issue that I'm unable to resolve on my own. I've written a circuit to calculate the cosine similarity between two vectors within the circuit. Here is the code for my circuit using the nonnative library on the std/math/emulated package:
package main

import (
	"github.com/consensys/gnark/frontend"
	"github.com/consensys/gnark/std/math/emulated"
)

const VectorSize = 2 // Define the size of your vectors

type CosineSimilarityCircuit struct {
	A              [VectorSize]frontend.Variable
	B              [VectorSize]frontend.Variable
	CS             frontend.Variable
	SqrtMagnitudeA frontend.Variable
	SqrtMagnitudeB frontend.Variable
}

func (c *CosineSimilarityCircuit) Define(curve frontend.API) error {
	// Calculate the dot product of vectors A and B
	dotProduct := curve.Mul(c.A[0], c.B[0])
	for i := 1; i < VectorSize; i++ {
		dotProduct = curve.Add(dotProduct, curve.Mul(c.A[i], c.B[i]))
	}

	// Calculate the magnitude of vectors A and B
	magnitudeA := curve.Mul(c.A[0], c.A[0])
	for i := 1; i < VectorSize; i++ {
		magnitudeA = curve.Add(magnitudeA, curve.Mul(c.A[i], c.A[i]))
	}

	magnitudeB := curve.Mul(c.B[0], c.B[0])
	for i := 1; i < VectorSize; i++ {
		magnitudeB = curve.Add(magnitudeB, curve.Mul(c.B[i], c.B[i]))
	}

	curve.Println("magnitudeA", magnitudeA)
	curve.Println("magnitudeB", magnitudeB)

	secp256k1, _ := emulated.NewField[emulated.Secp256k1Fp](curve)
	sqrtedMgA := secp256k1.Sqrt(secp256k1.NewElement(magnitudeA))
	sqrtedMgB := secp256k1.Sqrt(secp256k1.NewElement(magnitudeB))

	dotProductToElement := secp256k1.NewElement(dotProduct)
	denominator := secp256k1.Mul(sqrtedMgA, sqrtedMgB)
	curve.Println("denominator", denominator)

	cosineSimilarity := secp256k1.Div(dotProductToElement, denominator)
	curve.Println("cosineSimilarity", cosineSimilarity)

	curve.AssertIsEqual(cosineSimilarity, c.CS)

	return nil
}

package main

import (
	"github.com/consensys/gnark/frontend"
	"github.com/consensys/gnark/test"
	"math"
	"testing"
)

func TestCosineSimilarity(t *testing.T) {
	assert := test.NewAssert(t)

	var cosineCircuit CosineSimilarityCircuit

	// Define your vectors
	A := [VectorSize]float64{1, 2}
	B := [VectorSize]float64{2, 2}

	// Calculate the square roots of the magnitudes
	sqrtMagnitudeA := math.Sqrt(A[0]*A[0] + A[1]*A[1])
	sqrtMagnitudeB := math.Sqrt(B[0]*B[0] + B[1]*B[1])

	// Calculate the cosine similarity
	dotProduct := A[0]*B[0] + A[1]*B[1]
	cosineSimilarity := dotProduct / (sqrtMagnitudeA * sqrtMagnitudeB)

	// Scale factor
	scaleFactor := 10.0

	witness := &CosineSimilarityCircuit{
		A:              [VectorSize]frontend.Variable{frontend.Variable(int64(A[0] * scaleFactor)), frontend.Variable(int64(A[1] * scaleFactor))},
		B:              [VectorSize]frontend.Variable{frontend.Variable(int64(B[0] * scaleFactor)), frontend.Variable(int64(B[1] * scaleFactor))},
		CS:             frontend.Variable(int64(cosineSimilarity * scaleFactor)),
		SqrtMagnitudeA: frontend.Variable(int64(sqrtMagnitudeA * scaleFactor)),
		SqrtMagnitudeB: frontend.Variable(int64(sqrtMagnitudeB * scaleFactor)),
	}

	assert.ProverSucceeded(&cosineCircuit, witness)
}

I am using emulated.NewField and emulated.NewElement to work with the secp256k1 curve, and when I try to run my circuit, I receive the following error:
Error: plonk(bn254): parse circuit: enforcing modulus width element with inexact number of limbs
frontend.parseCircuit.func2
compile.go:118
emulated.(*Field[...]).enforceWidth

From my understanding, this error arises because the number of limbs of my Element structure (which is 1) does not match the number of limbs required by the Field (which is 4). However, I'm unsure about how to properly adjust my code to resolve this issue.
Could you please provide some guidance or suggestions on how to handle this error? Any insights into why this error occurs and how to prevent similar issues in the future would also be greatly appreciated. Since I haven't fully grasped the implementation concept of the library, please feel free to modify the circuit's logic completely, if deemed necessary.
Thank you for your help.

I would close this issue since declaring the variable with the emulated Field type directly would be the way.
Please refer to the following.
type CosineSimilarityCircuit struct {
	A_X            emulated.Element[emulated.Secp256k1Fp]
	A_Y            emulated.Element[emulated.Secp256k1Fp]
	B_X            emulated.Element[emulated.Secp256k1Fp]
	B_Y            emulated.Element[emulated.Secp256k1Fp]
	CS             emulated.Element[emulated.Secp256k1Fp]
	SqrtMagnitudeA emulated.Element[emulated.Secp256k1Fp]
	SqrtMagnitudeB emulated.Element[emulated.Secp256k1Fp]
	Epsilon        emulated.Element[emulated.Secp256k1Fp]
}

I post the new issue to resolve the problem related to this issue.
https://github.com/ConsenSys/gnark/issues/687


Case insensitive prefix search, data is case sensitive.

Hi,
I admit, i haven't tried it. But looking at the code it seems to be doing case-sensitive searching.
Imagine i put a bunch of files paths in the trie with structures like:
/home/a/Desktop
/home/a/Downloads
/home/a/Pictures

I'm guessing a prefix search of:
tsl::htrie_set<char> set = {"/home/a/Desktop", "/home/a/Downloads", "/home/a/Pictures"};
set.equal_prefix_range("/home/a/d");

note the lowercase d in the equal_prefix_range call, it will probably not match "/home/a/Desktop" and "/home/a/Downloads" while that would be desirable. Just lowercase everything would fix this, but then the data does not represent the actual paths anymore (both pats could exists in a linux/unix world as it is case sensitive). Using a map and have a lowercase -> uppercase mapping could potentially be a solution as well, but that also doubles the data usage (at the very least) thus kinda defeating the point of using a nice HAT trie in the first place (in terms of memory efficiency).
I do realize that there is a bit of trouble in making the equal_prefix_range case-insensitive (ideally optional, case-sensitive and case-insensitive). You don't know the type i'm putting in as string. It might be a std::string, might be a std::string_view, a byte array, a QString.. You just don't know therefore can't expect a call on a character (like toLowercase() for example) to exist.
So i have a bit of a request. Could you add a function that allows me to set how to compare a prefix?
I'm thinking of a:
tsl::htrie_set::set_character_compare(...);

Then in the compare functions you use whatever is set by the user.
Again, i could be completely wrong and it's already possible, but it doesn't look like that from reading the code ;)
I'm curious about your opinion!
Best regards,
Mark

Hi,
Yes currently only case-sensitive lookups are supported.
I would like to add something like the Traits template parameter in std::string, but it's difficult.
The main problem is that when I go down the trie, I do down byte by byte and not character by character. It's the same for a simple ASCII alphabet but different for multi-bytes UTF-8 characters. So even if I provide a way for the user to use a custom comparator (through in my implementation I don't directly compare two bytes, I convert a char to an unsigned int which will be used as position in the array of children), the user would only be able to compare two bytes and not two characters.
Also if I allow the trie to be case sensitive while providing case insensitive lookups, it means that lookups will have to go in different branches of the trie (possible but more complicate to implement).
I would like to add this feature but I don't really know what would be the best way to proceed to keep an intuitive interface that support UTF-8 strings.

Hi,
It sounds like the current way (casting char to int ad using that as array index) is a way that has to go if you want to consider case insensitive as well (or rather, any for of compare). What would that do for performance?

I tried with and boost::flat_map<char, node*>  a couple months ago and the performances weren't really good (but I don't have the number any more unfortunately)
But it's possible to work that out, instead of converting the char to int you try both to_upper(char) -> int and to_lower(char) -> int paths. The main problem is really multi-bytes UTF-8 strings.

Yeah, trying both would work. But that will cripple your performance of this nice trie container :) (or cut it in half at most i suppose)

Yeah, trying both would work. But that will cripple your performance of this nice trie container :) (or cut it in half at most i suppose)

This should not be a problem, as long as it is implemented in a separate function.

I tried with and boost::flat_map<char, node*> a couple months ago and the performances weren't really good (but I don't have the number any more unfortunately)
But it's possible to work that out, instead of converting the char to int you try both to_upper(char) -> int and to_lower(char) -> int paths. The main problem is really multi-bytes UTF-8 strings.

UTF-8 is a mess to work with. For example, a single accented letter like "á" can be represented in at least two ways: by a single codepoint (U+00E1) or by two codepoints (U+0061 and U+0301).
It will be HARD!


HV-1255 Removing obsolete plug-in configuration

https://hibernate.atlassian.net/browse/HV-1255

Rebased and merged. Thanks.


Add .pyi file for python type hinting.

Added a first version of a python .pyi file.
Want to add some more docstrings and potentially specify the type of the Dataframs more precisely. But is already ready for a first review.

Thanks


Ensure valid HTML with darkModeThemes

Clear and concise description of the problem
This is an example of markdown-it's default internal output for fenced code blocks:

    ...

When using markdown-it-shiki with darkModeThemes like so:
theme: {
  dark: "min-dark",
  light: "min-light",
}

...the result looks like this right now:

        ...

        ...

The reason for this is that markdown-it will only skip it's internal
 wrapper for fenced code blocks if the top-level element of what the highlight function returns is a
 element. From their documentation:

// Highlighter function. Should return escaped HTML,
// or '' if the source string is not changed and should be escaped externaly.
// If result starts with <pre... internal wrapper is skipped.
highlight: function (/str, lang/) { return ''; }

...so since markdown-it-shiki wraps the two
 elements in  a div, we get nested, redundant and invalid HTML as a result.
 tags inside a
 tag, a (block)
 tag inside an (inline)  tag.
Suggested solution
I would propose this markup instead:

  ...
  ...

Maybe it would also make sense to add the language-x class to the pre.shiki-container itself?
My concern is that this could break the styling of consumer's implementations. So maybe worth a major version?
What do you think? If you like this idea, I would gladly prepare a PR for that.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Ok, I ran some tests. This converts the result from Shiki as proposed above (quick and dirty):
if (darkModeThemes) {
  const dark = highlightCode(code, lang, darkModeThemes.dark, lineOptions)
    .replace('', '').replace('<\/code>', '')
    .replace('<pre class="shiki ', `<code class="shiki shiki-dark language-${lang} `)
    .replace('<\/pre>', '')
  const light = highlightCode(code, lang, darkModeThemes.light, lineOptions)
    .replace('', '').replace('<\/code>', '')
    .replace('<pre class="shiki ', `<code class="shiki shiki-light language-${lang} `)
    .replace('<\/pre>', '')
  return `<pre class="shiki-container">${dark}${light}</pre>`
}

The problem with this is that the  elements are inline and will look weird without applying display: block to them via CSS. But I found a much simpler solution: Just don't wrap the results in a div.shiki-container:
if (darkModeThemes) {
  const dark = highlightCode(code, lang, darkModeThemes.dark, lineOptions)
    .replace('<pre class="shiki ', '<pre class="shiki shiki-dark ')
  const light = highlightCode(code, lang || 'text', darkModeThemes.light, lineOptions)
    .replace('<pre class="shiki ', '<pre class="shiki shiki-light ')
  return `${dark}${light}`
}

This results in perfectly valid HTML:

  ...

  ...

One thing I noticed: Shiki adds a class with the theme to it's output. This caused this line to not add the shiki-dark class:
.replace('<pre class="shiki"', '<pre class="shiki shiki-dark"')

Fixed it by replacing the trailing " with a whitespace:
.replace('<pre class="shiki ', '<pre class="shiki shiki-dark ')

To make this package's output completely symmetrical with markdown-it's default output, the language should be added to the  element as a class. This produced the results as I would like them:
if (darkModeThemes) {
  const dark = highlightCode(code, lang, darkModeThemes.dark, lineOptions)
    .replace('<pre class="shiki ', '<pre class="shiki shiki-dark ')
    .replace('', `<code class="language-${lang}">`)
  const light = highlightCode(code, lang, darkModeThemes.light, lineOptions)
    .replace('<pre class="shiki ', '<pre class="shiki shiki-light ')
    .replace('', `<code class="language-${lang}">`)
  return `${dark}${light}`
}

Hi there! This issue is about something else than the the PR I created. Would you mind re-opening it? Should I create another PR for this issue?

Sorry for that. Using a pre for shiki-container sounds good to me. We might need to add some guide of the changes needed for migrating the CSS.

Thanks for reopening! :) What do you think of completely omitting the container, as proposed in my second comment?

For my use case, I prefer to have the container, but I am ok with making it configurable.

Great! I'll create a PR tomorrow.

I decided to first try and fix the root of this problem over at markdown-it: https://github.com/markdown-it/markdown-it/pull/927

No response from the markdown-it team. I think it might be easier to fix this here. We can still roll back anytime should there be some news from them.


Normalized comment on ListAllReleasesWithDetail  Fixes #312

Ⅰ. Describe what this PR does
Normalize comments on func ListAllReleasesWithDetail (pkg/utils/helm/utils.go)
Ⅱ. Does this pull request fix one issue?

fixes #312
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

@1250658183 thanks for your contributions!


chore(deps): update terraform terraform-ibm-modules/icd-postgresql/ibm to v3.17.8

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/icd-postgresql/ibm (source)
module
patch
3.17.7 -> 3.17.8

Release Notes

terraform-ibm-modules/terraform-ibm-icd-postgresql (terraform-ibm-modules/icd-postgresql/ibm)
v3.17.8
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/kms-all-inclusive/ibm to v4.15.12 (#494) (2e997c9)

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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

/run pipeline

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


Add ArtifactHub packages to website

As part of our ongoing efforts in encouraging better developer experience across different CNCF projects, we figured it would be nice for projects to showcase their packages hosted on ArtifactHub by embedding directly on the website.
To embed all the necessary project-related packages, kindly follow this guide. You can as well view some examples:

Keptn integration
Keda

Hey @thisisobate should i work on it ?

Sure. But we don't need the whole embedded widget, we just need a link in the header bar. That should be enough for us since we only really need to advertise this package: https://artifacthub.io/packages/helm/lifecycle-toolkit/keptn


Refactor to replace WebDriverEventListener and EventFiringWebDriver

WebDriverEventListener and EventFiringWebDriver are deprecated in selenium 4. It is necessary to refactor the code using EventFiringDecorator and WebDriverListener instead

Test on the following configuration:
carina: 8.0.0-SNAPSHOT
carina-demo branch: carina-8.x

For QA: Run Mobile tests and check that logs of, for example, typing and clicks, are visible


Navigation joystick in VR

Hi! I am doing a project and I have a question. Would it be possible for the user when entering VR to use the navigation joystick instead of teleportation?

Yes, I would say in that situation, listen for the user to push forward on the joystick then move the cameraRig in the direction the user is facing.
I personally think teleporting is a better user experience but you do you I'm not a cop

Thanks for replying so quickly!
I understand what you're saying, but I don't know how to get to that solution, I'm new to a-frame. Could you tell me how to do it? If it's posible.
I appreciate a lot your help.

This solution is for my AFrame Library rather than the AFrame controllers.
You need to make a component that listens for thumbstickmoved events.
https://aframe.io/docs/1.3.0/introduction/writing-a-component.html
this.el.addEventListener('thumbstickmoved', this.handleThumbstickAxis)

When the event fires moves the cameraRig in the direction the camera is facing according to event.detail.y (the y coordinate of the thumbstick)
use this code to get the camera's orientation VR
this.el.sceneEl.renderer.xr.getCameraPose().transform.orientation

Probably something like:
init() {
  this.q = new THREE.Quaternion();
  this.offset =  new THREE.Vector3;
  this.speed = 0;
  this.el.addEventListener('thumbstickmoved', e => this.speed = e.detail.y)
},
tick (time,delta) {
  const pose = this.el.sceneEl.renderer.xr.getCameraPose();
  if (!pose) return;
  const orientation = this.q.copy(pose.transform.orientation);
  const offset = this.offset.set(0,0,-3 * delta * this.speed);
  offset.applyQuaternion(orientation);
  offset.y = 0; // don't move camera up or down if user looks up or down
  cameraRig.position.add(offset);
}

That is just a best guess of where I would start from the top of my head, that code probably has mistakes and doesn't run, so don't use it verbatim but should give you an idea of how to do it.
Once you've made the component stick onto any part of the various hands probably on one of the handy-controls elements with data-left="grip" data-right="grip" data-none="grip" elements.

@WarlordCheru I've got a very basic smooth locomotion implementation here if you'd like to check it out: https://msub2.github.io/webxr-showcase/2/?content=A-Frame

Thanks for the reply @msub2

here is one more A-Frame boilerplate, which is using joystick as a controller in vr
https://github.com/inplayo-com/aframe-boilerplate


SSR status

Hello, my statement is more a question than an issue but i didn't know how to reach you so please, forgive me if you find this entry too much intrusive.
Basically, i can't understand the current status of your SSR effect. I mean, i've seen the other repository which at the moment seems to be deprecated due to an incompatibility with the last version of three.js.
At the moment, is the SSR effect implemented in you SSGI code? I've seen the SSR quote in the realism-effects description page but there is no description and so for me is a little bit misleading...
Anyway, thanks for your work, i really appreciate it!

Hey, all fine - thanks for the comment and sorry for the late reply!
Unfortunately there isn't much progress in this repository right now as I'm quite busy with other things and don't have as much time as I'd need to focus and work on realism-effects.
So regarding your question: this repository is focused a lot on SSGI which approximates global illumination in screen-space. The way it works is by calculating the diffuse and specular lighting in the scene. SSR calculates the specular lighting in the scene (the reflections). So SSGI is pretty much just SSR with diffuse lighting calculated as well.
So the idea is to have SSGI be an extension of SSR where it also calculates diffiuse ligthing in the scene.
This is also why there aren't many mentions of SSR in the code - SSR is just SSGI but with an extra parameter that says that we want to calculate only specular lighting.
Hope that clears that up. Although I also think I should highlight SSR more. There's also plans in optimizing it and making it more light-weight like the first version from the now deprecated repository.

Thanks for you reply, now it's clear. I'll definitely give to SSGI a try then, it seems to be what i need!
Have a nice day


StopIteration: Unsupported BMP compression (1)

While training dataset with keras i am facing following error
StopIteration: Unsupported BMP compression (1)
I checked all my images, i don't have any corrupt or bmp image, all images are eithe jpg/jpeg.
print(keras.__version__)
2.2.2

Epoch 1/1
17/18 [===========================>..] - ETA: 0s - loss: 1.2433 - acc: 0.5616 Traceback (most recent call last):

  File "<ipython-input-3-45790852014e>", line 1, in <module>
    classifier.fit_generator(trainingData, samples_per_epoch=600, nb_epoch=1, validation_data=testingData, nb_val_samples=133)

  File "C:\Users\dell\Anaconda3\lib\site-packages\keras\legacy\interfaces.py", line 91, in wrapper
    return func(*args, **kwargs)

  File "C:\Users\dell\Anaconda3\lib\site-packages\keras\engine\training.py", line 1415, in fit_generator
    initial_epoch=initial_epoch)

  File "C:\Users\dell\Anaconda3\lib\site-packages\keras\engine\training_generator.py", line 230, in fit_generator
    workers=0)

  File "C:\Users\dell\Anaconda3\lib\site-packages\keras\legacy\interfaces.py", line 91, in wrapper
    return func(*args, **kwargs)

  File "C:\Users\dell\Anaconda3\lib\site-packages\keras\engine\training.py", line 1469, in evaluate_generator
    verbose=verbose)

  File "C:\Users\dell\Anaconda3\lib\site-packages\keras\engine\training_generator.py", line 327, in evaluate_generator
    generator_output = next(output_generator)

  File "C:\Users\dell\Anaconda3\lib\site-packages\keras\utils\data_utils.py", line 584, in get
    six.raise_from(StopIteration(e), e)

  File "<string>", line 3, in raise_from

StopIteration: Unsupported BMP compression (1)

This issue resolved, when i verified all the training images using PIL image processing lib in separate python script, actually there was one corrupt picture in validation data which caused this issue.
now training working perfectly.
Thanks.


Can I use fetch-blob replace React Native Image uri ?

<Image
   style={{width: 100, height: 100}}
   source={{uri: 'https://192.168.x.x.png'}}  // or  source={fetch blob result}
/>

return RNFetchBlob.config({
      trusty : true
    })
    .fetch(
      'GET',
      `https://192.168.x.x.png`,
      {
        'Content-Type': 'application/x-www-form-urlencoded' //I'm not sure to use this
      }
    )
    .then(response => {
    })
    .catch(error => {
    });

I use React Blob trusty props ,but React Native Image uri does not support trusty, how do I use React Blob access to the image and stored in React Image ?

@eggeggeg , if you're going to use an image in storage be sure to add file:// prefix on Android (ios does not need the prefix).

@wkh237
My image is from the network, because the server certificate is private, so the default Image uri will be blocked off
My final solution is to convert the image to base64
http://stackoverflow.com/questions/29380265/does-react-native-support-base64-encoded-images
Thanks you


Order Cancellation: Should prevent user from being able to select the same item to cancel again

Environment Details
Spartacus: epic/order-return-cancel branch
Browser: Chrome
Device: mac
Happens on: http://dev-com-10.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD
Steps to Reproduce

Login
Place an order
Go to Order History
Click on the order placed
Cancel an item from the order
Now from the Order History page, click on the order again
You'll see that the QTY to cancel is still the same as before.
Try to cancel the same item

Actual Result
It's good that it displays an error preventing the user to cancel the same item twice.
But perhaps the order data should be refreshed faster (maybe backend is not fast enough). Then perhaps we should prevent the user to even be able to select that same item to cancel again from the frontend?

not sure this is fixable, let us know

I tested it in our old accelerator. The order is updated immediately after cancel request submitted. But, in OCC, there is several seconds delay for the order update. There is nothing we can do from SPA side. But, it's better we create a OCC ticket for the backend.

created https://jira.hybris.com/browse/RAY-541


status of LDAP user profile

what its the status? or if are leave it, some app similar?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

close due staled and this its only a question


[PR][CLOSED] Fixed clang format file to check coding style

 Issue by geunsik-lim
Tuesday Jun 12, 2018 at 08:24 GMT
Originally opened as https://github.sec.samsung.net/STAR/TAOS-CI/pull/22

This PR is to fix incorrect check routine of clang format to
inspect a coding style.
Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
geunsik-lim included the following code: https://github.sec.samsung.net/STAR/TAOS-CI/pull/22/commits

:octocat: cibot: Thank you for posting issue #39. The person in charge will reply soon.


Trying to fix the error with docker in travisci

So we'll see when Travis gets back, but I don't know if this will actually fix it. Travis and Docker is incredibly finicky. I've tried looking at a few alternatives, but haven't really found anything.

Not fixed it.
I think (very high level of guesswork here) that it may have to do with changes to Docker's API in the latest versions (hints here https://github.com/ContainX/docker-volume-netshare/issues/13).
J

These issues aren't related to how Docker is installed.
Go doesn't have a 1st party versioning for dependencies. They feel like they don't need it or whatever, and it's the dumbest thing ever. But one of the dependencies of this plugin keeps introducing breaking changes and so you can't build the binary. That's what's happening here.
So your PR is irrelevant, as it's trying to fix something that's not broken.

By the way, this was fixed in https://github.com/CWSpear/local-persist/commit/d5af6478ccfa3b74c24fdbf43abdbeb6e0b5b011


first commit

👷 Deploy Preview for shaileshthakur processing.

Name
Link

🔨 Latest commit
4a1f2c3fe6db1440f8d8e189b275801f55af9bb3

🔍 Latest deploy log
https://app.netlify.com/sites/shaileshthakur/deploys/64858dd5675da600089af36d


why clear before keystrokes?

Hi @andreptb
I am trying to send text to an element (in my case a static field in a native GUI element with my custom MacOS web driver  - it could be a SPAN on an HTML page) but I have noticed that your fixture insists on calling CLEAR first. The other web-drivers I have used (Xebium, hsac) do not do this.
Is it possible to at least turn this off from the table? setAutoClearBeforeTyping(bool) for example?
Thanks!

Hi @sglebs
According to Selenium reference documentation the type command should set the value, so the content should indeed be replaced. I've found a few different ways to do it, and the most compatible way seemed to be:
element.clear();
element.sendKeys("Some text here");

So if you need to append some text without clearing it first you can use the send keys action, check here to see how it works.


[columnar] Adds columnar.vacuum() and columnar.stats()

Adds two new UDF's:

columnar.vacuum()
columnar.stats()

The vacuum does an in-place vacuum, combining stripes and moving them to the beginning of the table space.  This builds off of work done by @mkaruza.
The stats are useful for testing and getting information about the current state of the table and its stripes.
Note, this includes fixing an issue that @mkaruza found, as it affected this as well.  As such, it changed the results of the columnar_vacuum test.
Given that this makes modifications to stripe data and metadata, as well as a change to an existing test, it needs a thorough review.

Deferring to @mkaruza for review.


[privacy] Implement privacy decrypt support in message layer

Issue Being Resolved

Fixes #19547 for Incoming Messages
Superset to #22769

Change overview
Adds support for privacy decryption of group messages per spec.
Includes unit test to verify the feature.

This is likely not going to go into the v1.0 branch. How exactly are new clients that want to send privacy-encrypted group messages to older servers running  going to be able to discover which of those servers support this feature vs. which don't?
This seems like it needs a new 'message layer revision' support of sorts.

This has wire format changes not tested in SVE/SVE2, and not covered by test plans.

The PR includes tests.  SVE and SVE2 had broken behavior with regard to privacy (was setting the Pflag yet not applying privacy).

Adding this late in the game is a risk to future compatibility.

This change actually provides a path to future compatibility whereas the current behavior is not spec compliant.  This patch should be expedited and merged into master ASAP so 1.0 nodes based on the SDK can properly decrypt group messages with privacy enabled.

[ ]  Justification for why this is added now, and description of mitigations and integration tests to be done are required before this can be merged even in master.

The PR includes unit tests for properly parsing and decrypting messages both with the privacy flag enabled and disabled.  The PR was posted sometime ago but was blocking on SiLabs platform CI tests which were fixed/merged 2 days ago: #22920.

This should be discussed, as we can’t break compatibility with what has shipped

The set of go forward options in my view are:

Defer this feature as provisional.
Deprecate to original 0x80 mask P flag.
Define a new 0x40 mask Pr flag as part of spec 1.0 errata and post-1.0 provisional work.
Extend Group Key Management cluster:
- Add FeatureFlag to signal support of Pr flag by a node.
- Add flag to Group Security Policy to signal use of Pr flag is enabled for a group.
Add these changes to SDK and Spec as errata.
Spec also needs errata to keep Message Extensions (MX) length as plain text and not privacy process extensions.

Toss the Privacy feature altogether.  Remove it from the 1.0 spec as errata.
Remove extra code paths for calculating privacy keys, etc.

Add this privacy parsing support to v1.0 branch as a spec compliance change before v1.0-branch is cut or soon after and encourage device makers that intend to use groupcast to deploy with v1.0-branch.  (This was my original hope and understanding when posting this PR, but the delays and elevation of SVE2 as production have dashed this path as impractical.)

So, given SVE2 is the golden reference, our choice is between path (1) and (2).  Path (1) requires clarity on the process for implementing provisional features. Thoughts?

Added CHIP_CONFIG_PRIVACY_ACCEPT_NONSPEC_SVE2 option for support of the erroneous pre-SVE2 senders.
Added many unit tests for the various permutations of group messages, including negative test cases.
This adds the ability to privacy decrypt on the receiver side per specification so we can rollout privacy encrypted senders at some future date. @bzbarsky-apple @tennessee-google please take a look.


Instance initialization improved

Love the addition of a custom initializer!
If you don't get to the docs, tutorial and example changes don't worry. Let me know and I will take care of that.
My main blocker for merging right now is the interface of the InjectionInitializer and the function1 refactoring.

Sorry for the delay. We are busy with the improvements of Hunt-Framework which depends on poodinis heavily. Can you merge this at first and release a beta version. Thanks.

Sorry for the delay. We are busy with the improvements of Hunt-Framework which depends on poodinis heavily. Can you merge this at first and release a beta version. Thanks.

Sure thing! Expect version 8.1.0-beta to be available soon

Release with v8.1.0-beta
https://github.com/mbierlee/poodinis/releases/tag/v8.1.0-beta

By the way you could've also used application contexts, see https://github.com/mbierlee/poodinis/blob/master/example/applicationcontext/app.d
usage of UDA @Component
I'll keep this in for those who don't want to set-up the ApplicationContext boilerplate

By the way you could've also used application contexts, see https://github.com/mbierlee/poodinis/blob/master/example/applicationcontext/app.d
usage of UDA @Component
I'll keep this in for those who don't want to set-up the ApplicationContext boilerplate

Yes, the ApplicationContext does somthing alike. We just follow the rule of laravel, see https://laravel.com/docs/5.6/providers.

Released with v8.1.0-beta
https://github.com/mbierlee/poodinis/releases/tag/v8.1.0-beta

Thanks.


Support Cabal 2.2 and 2.4

Might want to update this custom-setup stanza
https://github.com/tmcgilchrist/mafia/blob/master/mafia.cabal#L23-L28

Using Cabal 2.2 and 2.4 fails the Chaos test here.
Deliberately not merging this branch until we get to the bottom of it.


[Docs]Generate Docs on how models and CRDs are being generated using the mesheryctl generate command

Current State
No docs related to this.
Desired State
Create Docs for the same.
Steps:

Reference Meshery Integration spreadsheet and using that run the mesheryctl registry generate command thus generating models, components and relationship.
Then make meseheryctl registry publish.

This is intial steps feel free to tag me on slack if you taking up this issue.

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I have started to work on the issue. Please assign the issue to me.

I have started to work on the issue. Please assign the issue to me.

Have you worked with mesheryctl registry generate command?
If not I would advise you to familiarize yourself with it.

From where I can get to know more about this ?

Step 1: Generate GCP Token

Install Google Cloud SDK
Initialize SDK
Generate Access Token

Step 2: Export Meshery Integration Page as CSV

Access Meshery Dashboard
Navigate to Integration Page
Export Data to CSV

Step 3: Encode Service Account Credentials

Create/Select Service Account
Download JSON Key
Base64 Encode JSON Key

Step 4: Run mesheryctl Command

Which project to select in GCP ?

Which project to select in GCP ?

https://layer5io.slack.com/archives/CDM0ACDM5/p1718106890243109?thread_ts=1718074768.423849&cid=CDM0ACDM5


Playlist video download error exists entire process

In my case I have a playlist that contains some deleted, private and country blocked videos. If one of them fails, the entire process is closed without downloading a single video.
Another strange thing is that in the logs sometimes it says that a video is blocked in my country, but when accessing the link is totally fine.
Is there any way to skip the videos that cause an error?

I guess you could try using the exec function and calling it with the -i flag to ignore errors

@arobert93
i can confirm that the hints from @DiegoFleitas should solve your issue. Please give it a try and report back.
Good luck.

I was using the -i arg in conjunction with --print-json. If one video as part of the playlist/channel is unavailable, it will error and the output variable will be null. Which sucks, because the other videos download just fine.
There is a workaround for this that I wanted to mention: the error actually contains the JSON object I was interested in, see my code below:
youtubedl.exec(sub.url, downloadConfig, {}, function(err, output) {
        logger.verbose('Subscription: finished check for ' + sub.name);
        if (err && !output) {
            logger.error(err.stderr);
            # check if it errored because of an unavailable video. if so, get the JSON from err.stdout
            if (err.stderr.includes('This video is unavailable')) {
                logger.info('An error was encountered with at least one video, backup method will be used.')
                try {
                    # here's the important part, where we get the output through err.stdout
                    # the problem video is also missing from this list, which is good!
                    # NOTE: the output needs to be split by the new line character as it's an otherwise invalid JSON
                    const outputs = err.stdout.split(/\r\n|\r|\n/);
                    for (let i = 0; i < outputs.length; i++) {
                        const output = JSON.parse(outputs[i]);
                        handleOutputJSON(sub, sub_db, output, i === 0)
                        if (err.stderr.includes(output['id'])) {
                            // we found a video that errored! add it to the archive to prevent future errors
                            fs.appendFileSync(archive_path, output['id']);
                        }
                    }
                } catch(e) {
                    logger.error('Backup method failed. See error below:');
                    logger.error(e);
                }
            }
            resolve(false);
        } else if (output) {
          # if all videos in the playlist/channel are downloadable, this will run instead
          ...
        }

I have the same problem, if a video in a playlist is not accesible or for example set to be premiering, it crashes, even with -i.
@Tzahi12345 approach works for me


Add hot reloading back into project using the new React Hot Loader

The new React Hot Loader 3 beta is out and is intended as a replacement for both the original as well as React Transform. I've been testing it out, and hot reloading now works with pure functional components.
If you guys agree it should be put in, I'd like to make a pull request for it. Let me know.

Definitely :+1:

Yep that was the idea! Go with PR, it is most welcomed!

I started on this last night, and I got it working, but I have a few questions before submitting the PR.
In devServer.js, where it pulls in the express app from a separate file ("import app from 'server/app';")
I believe that for hot reloading to work correctly the app.use calls for applying the webpack-dev-middleware and webpack-hot-middleware must come before the app.use calls that set the static assets route & root route of the app. Right now, the middleware is coming after all of that, because it's being set in the devServer.js after the server/app.js express app is imported, and that server/app.js file is where the routes are set.
How would you all like to change this to allow getting everything occurring in the necessary order? I don't want to change the project structure too much without getting your input.
Also, other than that, I'm not sure yet how the included react-transform & redbox-react will interact with the new react-hot-loader. I think it may be possible to remove react-transform and get red-box-react working with react-hot-loader 3, but not 100% sure.

Try submit PR, then we can test it and give you more feedback ;-) You can write checklist into it...

Exciting! =)

Sorry for the delay, guys. Was having some issues and also have been extremely busy. Will try to submit a PR as soon as I can.

Don't worry :-) Give time to do it well, can take a while

@joshburgess are you working on a forked repo? Would love to see how you got this to working! I'm struggling a bit to get it working properly...

=)

@ads1018 As of now, I have used react-hot-loader 3 in other projects with functional component hot reloading working successfully in two different ways... first, using a simple webpack-dev-server, and, then, using the more advanced webpack-dev-middleware & webpack-hot-middleware method. Both work and were pretty easy to setup. I do not have anything hosted currently, but I can chat and point you to some examples if you want.
However, these projects weren't Universal JS projects (no server-side pre-rendering), so the complexity level isn't quite the same compared to this boilerplate. I had some issues with things not working correctly when I first tried to implement the same things I did in my own client-side only SPA projects in this boilerplate... However, I don't think it's anything that can't be figured out. I've just been really busy with my day job & getting started with co-organizing a React meetup.com group for my city with two other guys (preparing our first meetup, planning things, etc.). I hope to get back to it soon. Hopefully this weekend.
The good news is that it looks like we can completely strip out react-transform and keep redbox-react working in the project, which will be nice as it will simplify the boilerplate further. Other than that, I THINK we just have to move some of the isolated files around a little to be able to get the middleware loading in the proper order for hot reloading to fully work...

However, these projects weren't Universal JS projects (no server-side pre-rendering), so the complexity level isn't quite the same compared to this boilerplate.

That's why there are two different Webpack configs. =)

I'm able to get hot reloading working :) The only problem I'm running into is that when I refresh the page react throws a checksum error because the server is serving the old state of the component. Any idea on how to get around that?

I was running into the same issue, only my hot reloading was not fully
working... changes were triggering rebuilds and the console would say the
component is up to date afterwards but the changes weren't being rendered.
Same exact deal with the checksum though. Would you like to chat on Twitter
or Slack and compare projects?
On Fri, May 20, 2016, 7:17 PM Adam Soffer<EMAIL_ADDRESS>wrote:

I'm able to get hot reloading working :) The only problem I'm running into
is that when I refresh the page react throws a checksum error because the
server is serving the old state of the component. Any idea on how to get
around that?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/cloverfield-tools/universal-react-boilerplate/issues/97#issuecomment-220740311

Definitely. Just followed you back on Twitter. I think starting a Gitter chat for this repo is a great idea...

False alarm, guys. Looks like Adam was still using react-transform and not using functional components. I've pushed where I'm at right now to my fork if any of you want to take a look at what I've done so far and have any ideas about what I'm missing: https://github.com/joshburgess/universal-react-boilerplate

Yeah sorry for the false alarm guys. After upgrading to the new React Hot Reloader and switching to functional components I get the same exact errors as Josh.

What’s the state of this work? Just wondering if I should go rogue and spend the next day or two trying to get it working myself, or if anyone else has made any headway.

I've yet to figure it out...

I posted where I left off with it up above. It's a good starting point. I wasn't able to figure out why it wasn't working and haven't had free time to keep going with it. Maybe, fork it and see what I'm not doing correctly? I left some of the original code in and commented out to make it easier for someone to look it over.
https://github.com/joshburgess/universal-react-boilerplate


Setup TypeScript project references

Closes #376

@vilic seems you had an outdated base .. can you please resolve the conflicts?

@Apollon77 Done. :D


Disable WiFi powersave on AC, enable on BAT

See if there's a way to do this. There are reports saying there's a significant speed improvement when WiFi is taken out of powersave with a corresponding power consumption increase. Try to see if there's anything built-in that can toggle powersave depending on AC/BAT state.

Not managing power with TLP anymore in 22.04.


feat(angular): Improvement in data fetching and updated readme

Reference pr: https://github.com/matschik/component-party/pull/85.
In the last pr I made there was an improvement to be made: get rid of the bloat in the user.d.ts and keep just the properties that are used in the project, and that's what this pr is for.
I've also updated the readme to show the actual progress of Angular.

Thank you !
You can update the README via the command node scripts/progress.js


trained dream block

How to get the pretrained DREAM block to apply to our recognition model after training? Can we apply this after getting the embeddings from our model i.e second network which get inputs from the output of the original recognition model?

You can have a try to use the pretrained DREAM block provided by us to apply on your own model.
But I suggest re-training the DREAM block with your own model and data.


How to use gltfio::animator with WebGL

Is your feature request related to a problem? Please describe.
I want to display a model of glTF animation in filament.
However, I can't find a sample, so I don't know what code to write to animate the model.
Describe the solution you'd like
I would like a sample to do glTF animation with WebGL.

Describe alternatives you've considered
I tried the following code: There was no error, but it was not animated.
render(timestamp) {
    if (!start) start = timestamp;
    var progress = timestamp - start;
    var animator = this.asset.getAnimator();
    animator.applyAnimation(0, progress);
    animator.updateBoneMatrices();
    this.renderer.render(this.swapChain, this.view);
    window.requestAnimationFrame(this.render);
}

OS and backend

OS : Windows 10
Browser : Chrome 76
Backend : ANGLE (WebGL)

Hm, that looks correct.  (One gotcha is that you should not call releaseSourceData before getting the animator object.)
I'll add a JavaScript sample, maybe that'll help.

Isn't this missing begin/endFrame?

The render utility in JavaScript does begin / end for you.

I'm sorry I used it wrong. Now it works.
Animations can now be made by calling the render loop after the model has been loaded.
filament + BoxAnimated.gltf result:
filament + RiggedSimple.gltf result:

Nice!  I'll close this bug and make a note to myself to provide an animated example.  I'll probably just replace the existing Helmet demo with BusterDrone.


Add search for new man page service

https://man.archlinux.org/
https://archlinux.org/news/manual-pages-indexing-service/

Waiting for the review queue https://addons.mozilla.org/en-US/developers/addon/archlinux-manual-pages-search/

Waiting for the review queue https://addons.mozilla.org/en-US/developers/addon/archlinux-manual-pages-search/


Sams branch updates

A whole bunch of design updates as per tickets 367 366 and 363

@samjiangweb I'm working on points 1 and 4 from #367 like you asked me to. You haven't covered that right? Just making sure our work is not overlapping. I'm also working on #362.


Allow connectivity-proxy-reconciler to remove secrets it created

Description
Changes proposed in this pull request:

Add separate subchart for connectivity-proxy-reconciler to allow clean-up secrets

Related issue(s)
https://github.com/kyma-incubator/reconciler/issues/676

/retest


Can columns of a table be dynamic in Presto ?

Does Presto support dynamic columns in Tables, (for example, data stores which contain JSON documents, where new properties can be added in a JSON doc residing in an index/type) ?
In the Example connector, all the columns are hardcoded in 'example-metadata.json'. what if new columns are added in the csv doc ? How to handle these newly added columns in the csv (or new properties in JSON docs in elasticsearch indices) without restarting the Presto server every time a new column is added in a table ? Can this be handled by Presto at all ? Any suggestions will be of great help.
Thanks.

What is the efficient way to return the current set of columns ?
For eg: if the data store contains JSON documents, and each JSON property is a column in the table, is it not very time consuming, to search all the docs for finding all the properties (columns) ?
As this method 'ConnectorMetadata.listTableColumns()' is called for every query, can this time consuming search be done to return the set of columns.
Does any other connector do this dynamic listing of columns ? If yes, can anybody tell me, how they do it efficiently ?

Sumanth -- I believe this was discussed on the mailing list so if you're satisfied with the suggestions given from the other other members could you go ahead and close this?

For reference, the discussion being referred to is https://groups.google.com/forum/#!searchin/presto-users/dynamic$20columns/presto-users/8jJwgAEJ5U0/TBu7JfDUHpEJ


More details needed

Show better example of hashtable for property matching and include what permissions are required in order to run this cmdlet

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

ID: 3d731745-680b-fe7d-78fc-6757460f67b3
Version Independent ID: 17045452-597a-b77e-897d-8af47dfae727
Content: New-PnPUPABulkImportJob (sharepoint-pnp)
Content Source: sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPUPABulkImportJob.md
GitHub Login: @techwriter40
Microsoft Alias: kirks

@officedocsbot assign @yogkumgit

Hello @danmyhre Dan, How are you?
Thanks for your feedback.
I need to kindly redirect you to open PnP cmdlets issues here, a member of the PnP community will handle your request there.
Thank you!

@get-itips Thank you very much for the contribution and sharing this explanation. @danmyhre Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

The docs page shouldn't allow comments then

The docs page shouldn't allow comments then..this was a request for documentation updates

The Documentation for PnP cmdlets is inside the PnP cmdlets source code, on the repo I referenced, that is the reason I am redirecting you there, once a suggestion is added to the cmdlets source code (also documentation) a process later syncs it in this repo.
Hope this clarifies it to you, thank you!


Use Support library for better integration

From what I've gathered here and here, even when targetting 15+ sdk version, one should stick with support library instead of direct API (fragment, activity, etc.).
Few reasons from this SO post, but not limited to, are:

Future features may be added and backported, and then you'd need to rewrite to use them
Consistency. The support library works to make sure support fragments always work the same. Whereas the native fragments may have subtle differences between versions.
The support library can contain bug fixes to the platform and can be updated much more frequently.

Furthermore it would ease a lot integration within apps which target older API versions. WDYT?

Hi @bagage
We have been refactoring the project for a new major update. When it is released, you will find that we have updated a few facets of the UI. One of the improvements is exactly this, but not just for fragments. Moving forward, the SDK is using the support library as often as possible.
-- Kyle

Hi @kykrueger,
Cool, this is great news! Can't wait to test this new version then! Any ETA for it?
Feel free to close the issue anytime.

Fixed in v4.0.


Removes unused createStaticConfigProvider

Commit Message: Removes unused createStaticConfigProvider
Additional Description:
Previously, a variant of createStaticConfigProvider taking Protobuf::Message as a first param was not used, and that was one reason for the low test coverage of envoy/config package. This removes it, and potentially allows the package to be removed from the coverage exception.
Risk Level: low
Testing: done
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/retest


Performance differs with added disabled actuators/groups

Hi, I've just started testing using actuatorgroupdisable to allow my model to switch between position and intvelocity control. However, I've noticed that it changes the performance of the model.

With just one group of actuators, the model behaves as expected and gets to the setpoint nicely.

If I add a second group of actuators to the XML (e.g. velocity control), and then deactivate them, I now find that the model overshoots the setpoint a bit before settling. I would expect performance to be the same, as the only enabled actuators are exactly the same as in the first example, same gain parameters etc. I do NOT have both groups of actuators enabled at the same time, and I disable them under the Physics panel as well as under the Group Activation panel (Group Activation panel makes no difference).

Interestingly, this behaviour goes away when I decrease the timestep from 0.002 to 0.001 - the model performs like the first example again.

I don't fully understand it but seems like the extra unused actuators are perhaps slowing down/changing the simulation calculations in some way. Is this expected behaviour?
I can provide a minimal example if you'd like.

Yes please, a minimal example would be much appreciated.

I've just been comparing by loading the models directly into the GUI and playing with the controls. Here are a couple of videos so you can see the (subtle) overshoot when it changes position. Model files attached below.
One actuator group (baseline):

Two actuator groups:

mujoco_actuator_test.zip

This is a bug!
Thanks, will fix shortly.


Created a CONTRIBUTING.md file for this repository

With reference to #24, I have prepared a detailed guide for contributing to this repository which if followed step-by-step, merge conflicts between multiple pull requests can be avoided. Hope this sorts out everything.

Thank You 😃


[BUG/ISSUE] Wingetui 2.0.1 while starting not passing Starting Daemons

Before submitting the issue

[X ] I have checked that the bug is not a duplicate or, if it is, it needs to be reopened
[X ] I have checked that I am running the latest version of WingetUI
[X ] I have tried resetting and reinstalling WingetUI and the issue persisted or happened again
[X ] I have checked the FAQ section for solutions
[X ] I have read the contributing guidelines and I agree with the Code of Conduct

Describe the bug
While starting Wingetui 2.0.1 (also previous versions) I don't get pass the Starting Daemons.
To Reproduce
Start Wingetui
Waiting on Starting Daemons
Stuck Here? skip initialization
I click on that and the program starts
Expected behaviour
I would like it starts automatically without user input
Additional context
I choose Dutch, System Language, English as languages on 3 different machines. 2x Windows 10 Pro 22H2 Build 19045.3086 and 1x Windows 11 Pro 22H2 Build 22621.1848 all updates installed and newest version (2.0.1) till that moment, I have this since the first version I tried.

Hello,
can you please share your WingetUI log?

2023-06-20 Wingetui log Win11.txt
This is the logfile from my Win11 machine. If you also need the Win10 machine, please let me know. Thanks for looking into this issue.

I see in the log file something with scoop. I disabled scoop and now it's working. Is this meant to work like this? Do I need extra settings for scoop?

can you please run scoop -v and scoop update on a console and post here the output?

Should I leave this open or close it?

open, this shouldn't happen

+1, this happened to me and a google search brought me here and the solution fixed it (which was installing scoop)

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser # Optional: Needed to run a remote script the first time
irm get.scoop.sh | iex

This also fixed it for me installing scoop


systemd journal transport

A transport to log to systemd's journal, using https://www.github.com/systemd/node-systemd/.

Who were you, DenverCoder9? What did you see?!
 If you find yourself here, you're probably looking for the syslog transport.


The Future of Next.js Commerce

When we first released Next.js Commerce to the public in our first Next.js Conf, we wanted to have a real e-commerce app that worked with BigCommerce and Next.js, as we we're building it we realized we could do much more and started doing a "core" framework that could be used by more commerce providers, or else we would need to repeat the same work for every provider out there (and there are a lot of them).
After the Next.js Conf was done we started working on adding more and more providers to the repo, we currently have 7 providers and more on the way. A lot of the work has been done by our e-commerce partners themselves while we focused on getting the core framework into a better state.
As of today the core of Next.js Commerce is missing features, structure changes, and more, but we are more committed than ever to keep working on it as we aim towards our goal: An open source commerce framework that works with anything you throw at it.
In order to achieve our goal we have to stabilize our core data types, improve tooling, add documentation, and create npm packages for the core and every provider, allowing it to work outside of our demo in any other Next.js (and react) application, subsequently allowing us to have a marketplace of themes under the same core, with a one click switch between e-commerce providers.
And the above is just the start! In the issues below you can see our live roadmap to V1:

[x] #513
[x] #429
[ ] #368
[x] #367

We're also investing into new features and enhancements:

[ ] #476
[x] #516
[ ] #514

Update: We (the Solutions Team at Vercel) were very busy working on the Next.js Conf and haven't had the time to put more work into Commerce, and we're currently looking on expanding the team to have more hands that can help us improve Next.js Commerce

Understandable! We appreciate the work you and the team put into Commerce.

Is the plan to eventually continue on the 7 roadmap items listed above? Would you welcome community contributions toward that goal, or should the community sit tight until this thread is updated?

Hello!
We are planning to build a provider for Solidus and Next.js Commerce but there seem to be very few activities here, especially in terms of allowing new providers to be added.
I read that adding new providers is on hold until there's a new API for commerce, which seems to be merged, but as outlined in this other issue, it's not clear what should happen now, considering that, reading this issue, there seem to be still some items to complete before release V1.
That said, we are considering using Next.js Commerce as the default Next.js solution when people want to use our platform with some JS framework, but it's not clear if this is a good moment for the project to add new providers.
On a side note, with some direction, we are probably able to contribute to the project if needed.
Can someone help us understand the plans for the project in order for us to take an informed decision? Thanks in advance! 🙏

any updates?

Can somebody tell if that project has a future at all?
Because what I see is a kind of an abandoned issue queue. The maintainer is just updating statuses at the Kanban without actually taking part in discussion (example). Some pull requests stay without review very long time until they become outdated.
I mean is there a sense to develop plugins for the Next.js Commerce because the task does not look like as a trivial one overall.

@drugan Like you can see in a previous comment, the team was busy with other internal things, like the Next.js Conf, providing many examples you can find in the Vercel Examples repo. Meanwhile, the project migrated to Turborepo, and there was a decision to make the core more solid and future-proof for accepting PR & new providers to address and avoid precisely what you mentioned. Also, there are fixes  & improvements for the things you said also.

@cond0r you've done an impressive work but in my mind some members of you team might be more responsive on the issue queue. At least to leave some short description when they create an issue or update the Kanban status. So we all know what is going on.
Thanks again for your work, I do greatly appreciate it!

is now a good moment to pick up this discussion? or is there maybe a better place to do this? we are currently looking into Vercel Commerce for a custom provider implementation

Update: We have decided to take Next.js Commerce in a new direction and will be closing out current PRs and issues due to this change. Please see this PR for more details: https://github.com/vercel/commerce/pull/966


Unwrap call

handles[method]?();

Appears to be fixed https://github.com/buzz-language/buzz/blob/main/tests/038-fibers.buzz#L76


"About Products" page is missing a / in the s3:// protocol

Pages like this: https://explorer.dev.digitalearth.africa/audit/storage
Have a location like this: s3:/deafrica-input-datasets/alos_palsar_mosaic/2018
I think it should be like this s3://deafrica-input-datasets/alos_palsar_mosaic/2018

Fixed in 2.8.1


YAML errors

With this file:
PASSWORDIWONTTELLYOU
---
user: username
autotype: [user, :tab, pass]

I get this error message.
Failed parsing yaml of entry 'foo.bar.baz':
---
user: username
autotype: [user, :tab, pass]
(<unknown>): did not find expected node content while parsing a flow node at line 3 column 18
/usr/bin/autopass:205:in `entry_from': undefined method `merge' for nil:NilClass (NoMethodError)
        from /usr/bin/autopass:224:in `block in update_cache'
        from /usr/bin/autopass:222:in `each'
        from /usr/bin/autopass:222:in `update_cache'
        from /usr/bin/autopass:161:in `initialize'
        from /usr/bin/autopass:251:in `new'
        from /usr/bin/autopass:251:in `<main>'

This isn't valid yaml. The problem is the colon in front of tab. If i remember correctly this used to work and would have returned the array ["user", ":tab", "pass"]. I might be wrong though.
To fix the issue you have two options:

Use the syntax autotype: user :tab pass (whitespace delimited string)
Use the syntax `autotype: [user, ':tab', pass]

Will close the issue as soon as I've updated the readme


hostPort settings get lost when using "Redeploy" on a workload

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Create the following deployment :
apiVersion: apps/v1beta2
kind: DaemonSet
metadata:
  annotations:
  labels:
    app: test
  name: test
  namespace: kube-system
spec:
  selector:
    matchLabels:
      app: test
  template:
    metadata:
      labels:
        app: test
        name: test
    spec:
      containers:
      - name: nginx
        image: nginx
        ports:
        - containerPort: 80
          hostPort: 8123
          name: http
          protocol: TCP
  updateStrategy:
    rollingUpdate:
      maxUnavailable: 1
    type: RollingUpdate

Klick "redeploy" on the test workload in the rancher UI
Result:
The setting "hostPort: 8123" is missing after redeploy. The container is not listening anymore on this host port.
Other details that may be helpful:
Environment information
Rancher | v2.1.3
User Interface | v2.1.17
Helm | v2.10.0-rancher5
Machine | v0.15.0-rancher1-1
(Single-Node Rancher)
Cluster information

Cluster type Custom
Machine type metal
Kubernetes version (use kubectl version): v1.12.3

I've noticed this also happens when upgrading a container via Workloads > Edit > Upgrade.

I just figured out that a workaround is to include the field.cattle.io/ports annotation.  So in your example it would be:
apiVersion: apps/v1beta2
kind: DaemonSet
metadata:
  annotations:
  labels:
    app: test
  name: test
  namespace: kube-system
spec:
  selector:
    matchLabels:
      app: test
  template:
    metadata:
      annotations:
        field.cattle.io/ports: '[[{"containerPort":80,"hostPort":8123,"kind":"HostPort","name":"http","protocol":"TCP","sourcePort":8123}]]'
      labels:
        app: test
        name: test
    spec:
      containers:
      - name: nginx
        image: nginx
        ports:
        - containerPort: 80
          hostPort: 8123
          name: http
          protocol: TCP
  updateStrategy:
    rollingUpdate:
      maxUnavailable: 1
    type: RollingUpdate

That appears to survive upgrades and redeploys.

D'oh, I just realized that workaround will cause the DaemonSet to only run on a single node.  It seems to work fine with multiple Deployment replicas, though.

Hello,
is there a particular reason that it's unscheduled? I is IMO a serious issue because it breaks things.

Will keep track of the issue in https://github.com/rancher/rancher/issues/23375. @micw we are going to prioritize the fix

@alena1108 I'd say its two different issues. This one was about loosing the hostPort on redeploy. Loosing it on editing the yaml is newly introduced. It worked, when I filed this issue.


merge

Is projec good
Pada tanggal 11 Feb 2018 12.37, "shiwk"<EMAIL_ADDRESS>menulis:

Merged #50 https://github.com/AElfProject/AElf/pull/50.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AElfProject/AElf/pull/50#event-1468300687, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AiqEmPJrMJIVtunUkB_BtaR5WyyoCk5Sks5tTnyXgaJpZM4SBNr0
.


Update the theme instructions

Pull request #3 is a significant change in the mkdocs-material-dib theme.

Requires updating to mkdocs 1.0
Requires syntax changes in mkdocs.yml (strict, pages, nav)

The README needs to be updated to reflect those changes, by mentioning the mkdocs version, and updating the sample mkdocs.yml file.

closed by db1d419


Allow some symbolic constants in place of dissolve delay seconds

fixes #24

I'll document these in the README when I'm making the README changes for the Nix stuff.


Support 1.20.3+

In version 1.20.3 they changed the achievements again and now to get display you need to access "c" again
Object display = NMSUtil.getObject(nmsAdv, IS_19_4 && !IS_20_3 ? "d" : "c");

Sorry for the late response, having personal issues. I'll update it this month. Thanks for reporting

Please update to 3.0


Mood classifier

Mood classifier for songs #46

LGTM :+1:

Can be merged.

Yes, this is ready to be merged, as @Azkle already is working on tests. LGTM


Handling of data credits in the application

Hi all,
More of a comment than an issue. I noticed that you tend to keep track of data credits higher up in the user application. This is fine, but I'm wondering if it would be better to let the driver handle credits and take that burden away from the user? For example, you have a queue system implemented that has 4 slots for transmitting commands to the nRF8001. In the current implementation, the queue would never be able to queue more than 2 commands that rely on credits. Therefore, it's up to the higher application to track the credits and wait for credits to free up if none are available. But there's no reason why these
Instead, you could have the queue track the credits. Then the higher application only needs to concerned about whether or not there is room in the queue and anything that is in the queue that relies on credits can wait until credits are available.
This is what I've done in my implementation and it works very well. Any events that arrive that increase the number of available credits are not added to the rx queue. Instead, they are handled immediately to ensure that the tx queue doesn't get jammed up.

I agree - it would seem far more sensible to have the "Credits" managed within the driver than by the Application.


image contents

IMAGE

![image](https://github.com/KimDoubleB/news/assets/37873745/47aa6394-323b-48f3-b5c0-2a1cebc42831)


[BUG]

What is the bug?
BetterTeams won't allow you to leave your team.
Expected Behaviour
BetterTeams was supposed to make the player leave the team when they did /team leave.
How to Reproduce

Get BetterTeams from their SpigotMC page.
Bob1 creates a team.
Bob2 joins the team.
Bob2 wants to leave the team.
Bob2 can't leave the team.

Error message
[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: java.lang.IllegalStateException: Unregistered scoreboard component

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at org.bukkit.craftbukkit.v1_19_R2.scoreboard.CraftTeam.checkState(CraftTeam.java:403)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at org.bukkit.craftbukkit.v1_19_R2.scoreboard.CraftTeam.removeEntry(CraftTeam.java:261)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.events.MCTeamManagement.remove(MCTeamManagement.java:110)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.events.MCTeamManagement.remove(MCTeamManagement.java:91)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.team.MemberListComponent.remove(MemberListComponent.java:63)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.Team.removePlayer(Team.java:662)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.Team.removePlayer(Team.java:648)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.commands.team.LeaveCommand.onCommand(LeaveCommand.java:26)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.commands.presets.TeamSubCommand.onCommand(TeamSubCommand.java:39)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.commands.ParentCommand.onCommand(ParentCommand.java:135)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.BooksawCommand.runExecution(BooksawCommand.java:72)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at BetterTeams.jar//com.booksaw.betterTeams.BooksawCommand.lambda$execute$0(BooksawCommand.java:59)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at org.bukkit.craftbukkit.v1_19_R2.scheduler.CraftTask.run(CraftTask.java:101)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at org.bukkit.craftbukkit.v1_19_R2.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:57)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)

[14:46:02] [Craft Scheduler Thread - 73 - BetterTeams/WARN]: at java.base/java.lang.Thread.run(Thread.java:833)

Output of /teama version
Sorage Method: com.booksaw.betterTeams.team.storage.storageManager.SeperatedYamlStorageManager
Minecraft Version: git-Paper-448 (MC: 1.19.3)
Language Selected: messages
Current plugin version 4.6.5
Additional Information
No response

This bug has been fixed and the patch will be included in the next update. Thank you for reporting.


allow untrusted workspaces to be debugged

Per "guidance for debug extensions" as noted in the Workspace Trust Extension Guide.

Rechecked - no need to adjust the dependency version, just add the cababilities.untrustedWorkspaces and everything is fine.

this allows arbitrary code execution because the launch.json can input any executable path for the debugger path that the extension will unconditionally launch. This puts the user at a risk, thus this will not be merged like this.

Thanks for the quick answer. That's an interesting point. Do you think they did not considered that when writing the "Workspace Trust Extension Guide" (or did I miss something there)?

I've guessed the point is that the user would have to manually click on "run" so there's already a "second step" to code execution, but this is what they say:

What is the guidance for debug extensions?
VS Code will prevent debugging in an untrusted workspace. For this reason, generally, debugging extensions do not need to additionally require trust and should select true for the supported property. However, if your extension provides additional functionality, commands, or settings that are not part of the built-in debugging flow, you should use 'limited' and the above guidance.

The point form above is: debugging is disabled in an untrusted workspace in any case. Isn't that the case any more?
Hm, maybe that's outdated?

oh right sorry I didn't check that link - in that case I think it's ok to merge

I guess everything is done now? If not: feel free to just commit yourself and I'll learn from inspecting, no need for any credit or anything else.


Add frontmatter to contributor docs

I found a few files in the contributor docs that were not included in the website.

/lgtm


Component lifecycle methods

This PR adds component lifecycle methods onAddComponent() and onRemoveComponent, which replaces the component hooks. As such, this PR also removes component hooks.
Discussion of this change can be found in issue #103.
The TL;DR of #103 is that lifecycle methods have are just a better developer experience over component hooks, with next to no performance hit.
Tests and code documentation have also been updated.
The removal of component hooks has resulted in slightly uglier tests, and I've pointed these out.

Thank you for your contribution! I have one minor remark about the test with the callback as system constructor argument. Should be possible to restructure the tests without using that.
Please have a look and then we are ready to merge 😁

Replaced it with a much nicer getter in the test itself 👍

Cool, great stuff! I will make the SNAPSHOT release on maven tomorrow. And with that I will close the 2.4 features as well. I will do some testing on the weekend and if nothing crazy pops up, then we are good to go for the next stable release!
Thank you again for the support 🙏


Http Client with axios

Create a service object with axios that provides an interface to make http requests

done #60


Add layers to visualize shortage by HUC

Probably a few different visualizations would be most helpful. The two I have thought of are average percent shorted per HUC (how severe the shortages are) and some version of number of users shorted per HUC normalized by total of number of users in the HUC (how many are being shorted).

@qjhart There are two issues here.

The HUC layer is currently hosted on Google Maps Engine (https://mapsengine.google.com/) which is due to be shutdown on 1/29/2016.  So a new hosting service will need to be found.

Assuming server side computation, we need to be able to compress the vectors and send those along as well.

@jrmerz, here is the idea for this.  When we have a watershed, we get back a set of points that show the individual shortages.  What we'd like is to see this at the aggregated level.  Each of these means aggregating the points on their HUC12 designation, and then attaching that to the exsiting HUC12 map (that is already in the legend).

riparian For all riparian and pre-1914 users, we calculate the weighted average of delivery (or shortage), and show that delivery (or shortage) using the same legend as for the points.
delivery = \sum_{points} allocation_i  / \su_{points} demand_i.
shortage = \sum_{points} demand_i - allocation_i / \sum_{points} demand_i;

appropriative For Appropriative, we show the fraction of users that get their demand filled/shorted

filled = num_allocated / num_demands
shorted  = num_demand-num_allocated / num_demands

total  the total delivery/short combines these.  Same equations as riparian but over all water rights.

First, 'Assuming CLIENT side computation'.  My bad.
So the HUC 12 layer is a raster layer.  I can't do anything to the layer or render a new region.  I can show a table of with the HUC 12 id, but nothing geographic, no 'attaching'.
Also, what sudo language are you writing in?  I can't read it :/

Ok, how about we make the HUCs available something as in https://github.com/ucd-cws/usbr-water-districts, then you pull the data in (via our as yet unmade gis-bower) or just via the release, and we verify we can make it more simple, and then we render it on the client?
Regarding lang:
http://latex.codecogs.com/gif.latex?delivery&space;=&space;\sum_{points}&space;allocation_i&space;/&space;\sum_{points}&space;demand_i

OK, I like where you are going with this.  Simplified geojson as part of the app and stored in the usbr-water-districts repo I like.  I think a raster service is still best for visualization of entire layer... Don't we have a watersheds arcgis server now?  seems like both watersheds and huc boundries are great candidates.

Yes, we absolutely do (or should), however the colors need to change on every new data upload, so I don't see how the service would help.  I will however nudge up the HUC development.

Not sure if you answered your own comment or not.  But to respond, yes the colored hucs would be svg overlays, but we would also need a basemap of all hucs, for browser performance reasons.  we will also be limited in the number of rendered hucs we will be able to show.

I have added a function to the public view for fetching simplified HUC geometry by id.  I am still play around with how small I can make the geometry and still have it presentable.
Ex:  http://watershed.ice.ucdavis.edu/vizsource/rest?view=get_huc_by_id('180101100103')&tq=SELECT *&tqx=reqId%3A1

Ok, I have added a simple overlay for HUC 12 data.  It currently just renders the average percent demand for that HUC's.  It only loads HUC's that have data.  The rendering as shortage vs demand met is tied to the same toggle as the nodes.  There is a new checkbox for disabling the HUC 12 averages.
Here is an ex: http://watershed.ice.ucdavis.edu/drought/#date=2014-04-28&river=EEL RIVER&zoom=9&ll=40.19880596447519%2C-122.958984375
Note.  HUC latency is due to network requests.  There is some work that can be done here to improve things but wanted to get this up so you can see where I am going.


update doc comments per TSDoc standard

This PR follows the TSDoc standard to update the doc comments, providing better intellisense.

optimize for type SettingSelector, adding comments for keyFilter and labelFilter respectively.
using @remarks tag

E.g. for keyFilter previously the description is bound with type SettingSelector and won't show up directly on keyFilter property as below:

now it's more helpful:


existing-arrikto: Update config to v0.7.1

/cc @sarahmaddox
Signed-off-by: Yannis Zarkadas<EMAIL_ADDRESS>

This change is

/assign

This LGTM, but we haven't yet released v0.7.1 - do you want to hold off on this change until the release happens?
https://github.com/kubeflow/kubeflow/releases

@sarahmaddox thanks for the review!
It should be ready now.

Thanks @yanniszark! I have a question about the fact that we haven't released a binary with a matching version number - please see the discussion on https://github.com/kubeflow/website/pull/1466

@sarahmaddox that's a good question, now that kfctl lives in a different repo, it has its own distinct versioning.
In this PR, I'm more concerned about the fixes contained regarding the authentication part.
It solves this issue which is hitting a lot of users: https://github.com/arrikto/oidc-authservice/issues/2
So, it would be nice if we could get it in asap while we discuss the versioning story.

@sarahmaddox that's a good question, now that kfctl lives in a different repo, it has its own distinct versioning.
In this PR, I'm more concerned about the fixes contained regarding the authentication part.
It solves this issue which is hitting a lot of users: arrikto/oidc-authservice#2
So, it would be nice if we could get it in asap while we discuss the versioning story.

Sounds good!
/lgtm
/approve


concurrent unsafety of gojay.Marshal is not clearly documented

Hello,
I think that the fact that gojay.Marshal is not safe for concurrent usage from multiple goroutines should be explicitly mentioned both in the readme and godoc.
Now it is stated that Marshal borrows an encoder and releases it back no matter what. While an attentive reader will have realised that it introduces a race (because same encoder could be reused by another goroutine and the buffer will get corrupted), the race is easily overseen problem as everything seems to be working most of the time, so it should be mentioned (may be even in bold and with some exclamation marks).
Example program that shows the race exists:
package main

import (
	"log"
	"strconv"
	"time"

	"github.com/francoispqt/gojay"
)

func proeb(num int) {
	for {
		b, err := gojay.Marshal(num)
		if err != nil {
			log.Fatal(err)
		}

		s := string(b)
		if n, err := strconv.Atoi(s); err != nil || n != num {
			log.Printf("caught race: %v %v", s, num)
		}
	}
}

func main() {
	for i := 0; i < 100; i++ {
		go proeb(i)
	}
	time.Sleep(100 * time.Second)
}

This is correct, I have just pushed a fix to master which effectively creates a new buffer when borrowing. Previously it was doing enc.buf = enc.buf[:0] which is wrong. I am patching versions with the fix.
If the fix works for you, please close the issue.

I thought it was the intended behaviour, just not documented.
Thanks for the fix!


Passing service_yaml to config gen command

Necessary change now that https://github.com/googleapis/toolkit/commit/0ccd187ba9074bf2a0161d793f18400d243ab87c is submitted.

LGTM after updating the baseline tests

Current coverage is 77.20% (diff: 100%)

Merging #62 into master will increase coverage by 0.02%

@@             master        #62   diff @@
==========================================
  Files            33         33
  Lines          1065       1066     +1
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            822        823     +1
  Misses          243        243
  Partials          0          0

Powered by Codecov. Last update e365222...4782f8e


[Feature] Integration with beberlei/assert library

Integration with @beberlei's assert library can give a nice tool for writing DbC conditions and assertions, see https://github.com/beberlei/assert#list-of-assertions. For example,
    /**
     * Deposits fixed amount of money to the account
     *
     * @param float $amount
     *
     * @Contract\Ensure("Assert\Assertion::integer($this->balance)")
     */
    public function deposit($amount)
    {
        $this->balance += $amount;
    }

@lisachenko
Good idea, I will create pull request with integration soon.

@pdaw Thanks for contribution! Released tag 0.3.0 with minor changes in your code.


Better docs for altair-fastify-plugin

Is your feature request related to a problem? Please describe.
The readme for altair-fastify-plugin could use more depth.
Describe the solution you'd like
For instance:
app.register(AltairFastify, {
  /**
   * All these are the defaults.
   */
  path: '/altair',
  baseURL: '/altair/',
  endpointURL: '/graphql',
});

Why is path and baseURL the same path? What is the endpointURL for? If I start a server with these defaults what path do I navigate to to get to the Altair interface?

These are documented in the code https://github.com/altair-graphql/altair/blob/master/packages/altair-fastify-plugin/src/index.ts#L8-L25
I'd not want to have the documentation also in the README as that can get out of sync easily. We could consider using a tool to automatically generate the docs from the code, if this is necessary.

Maybe we could write it down in the Altair Docs integrations page? https://altairgraphql.dev/docs/integrations/
I could do a PR if it is straithg forward enough :)


Double splash screen on android devices

On android devices splash screen shows twice with a flash in between

Issue resolved.


Backport/optional log fill attr from profiles [6740]

This PR is linked with ros2/rmw_fastrtps 355 PR. It has been done so that the RMW layer does not show log errors when a profile is not found.

Add an optional parameter log_error for only logging the error when user specifies on member functions:

XMLProfileManager::fillParticipantAttributes
XMLProfileManager::fillPublisherAttributes
XMLProfileManager::fillSubscriberAttributes

Style compliance on:

XMLProfileManager.h
XMLProfileManager.cpp

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows


Error when using GPU

Hi, I just try to use your demo to run mediapipe holistic.
First, I modify the graph to "holistic_tracking_cpu.pbtxt", modify InputStream, OutputStream,  get_landmarks function, and it worked.
Second, because cpu speed is too slow, I want to use gpu instead.
But when I run libmp_example, this error happened
WARNING: Logging before InitGoogleLogging() is written to STDERR
I20230111 18:46:09.639328 74859 libmp_impl.cpp:31] Successfully initialized LibMP graph
I20230111 18:46:09.641311 74859 libmp_impl.cpp:47] Failed to start calculator graph
Input video ../1.mp4
I20230111 18:46:09.982609 74859 libmp_impl.cpp:73] Failed to add packet to input stream. Call m_graph.WaitUntilDone() to see error (or destroy LibMP object)
Process() failed!
I20230111 18:46:10.000988 74859 libmp_impl.cpp:15] Shutting down.
I20230111 18:46:10.001063 74859 libmp_impl.cpp:23] Error in CloseInputStream(): INTERNAL:

Because no more log for this error, I can't figure out how to fix it, it seem that happen when initializing the mediapipe calculator, Have u met this error before?

Hi, @deathcrow - thank you for using LibMP! Unfortunately, I have only used the CPU and haven't tried using the GPU myself.
From this page, it looks like MediaPipe only supports GPU inference on Linux desktops. What system are you using?


Netcdf separate loadsave

This "just" splits the iris.fileformats.netcdf module into separate sourcefiles for load + save code.
There's very little talk between the two, and this should makes it much easier for devs to find their way around.
Note that I haven't forced the split upon the user : All the public API is exported in the parent module, so everything there is as it was.
~TODO: in draft while I test with Cirrus-Ci memory hacks, just to run the tests.~

Status update :
doing sort-of OK
various tests to sort, largely Mock issues

Rebased following #4503 / #4809
Expecting various fixes still needed...

Hi @trexfeathers I think this is now ready.
No pressure, but ... I hope we can nail this before it needs rebasing again, because it has proved rather awkward for that.

Brilliant thanks @jamesp .
Busy elsewhere but will respond in a bit ...
I think this might possibly help with a number of awkward outstanding desired features relating to netcdf :

load chunks control : https://github.com/SciTools/iris/issues/3333
precise formatting round-trips : https://github.com/SciTools/iris/discussions/4215
lazy saving : https://github.com/SciTools/iris/issues/4190
output "append" mode : https://github.com/SciTools/iris/issues/565

Context : things this can be used for ?
In addition to just "fixing data a bit" on either load or save,
I think this might possibly help with a number of awkward outstanding desired features relating to netcdf :

load chunks control : https://github.com/SciTools/iris/issues/3333
precise formatting round-trips : https://github.com/SciTools/iris/discussions/4215
lazy saving : https://github.com/SciTools/iris/issues/4190
output "append" mode : https://github.com/SciTools/iris/issues/565

Thanks @trexfeathers .
I think I finally have it working now (after several tries at fixing the import problem!)
Can you re-review ?

Please also shout if merging this now is going to cause any problems with the Split cube-attrs project. Perhaps it's worth the problems sweat_smile

Good thought, but should be nothing serious I think -- this has only moved things, not reorganised.

I've been re-running some missed benchmarks. FWIW you would have seen this (predictable I suppose!):
       before           after         ratio
     [e96a0536]       [d8f8dac7]
-         646±5μs          130±1μs     0.20  import_iris.Iris.time_fileformats_netcdf


Link to example file in README

What are you trying to accomplish with this PR?
Improve README.
How is this accomplished?
Make test/fixtures/hello-cloud/unmanaged-pod-1.yml.erb clickable and also reflect that it is no longer called unmanaged-pod.yml.erb, but unmanaged-pod-1.yml.erb.
What could go wrong?
Hopefully nothing -- it is just README.md update.

Thanks for the README fix!


Support custom variant resolution mechanism

I have a project where I need to pick the variant based on a strict set of the available fields.
Today I have the untagged container attribute to work with. While flexible, it's unable to disambiguate which variant to use in cases like these:
#[serde(untagged)]
enum Untagged {
    A {
        a: string,
    }
    B {
        b: string,
    }
    C {
        a: string,
        b: string,
    }
}

I require deserialization to happen strictly based on the presence of a set of required fields which might overlap with required fields in other variants. This can be accomplished by looking at a strict set of available fields names at once, instead of only firing of a sequence of deserialization attempts.
Option 1: Support another container attribute
Support another container attribute which is specialized towards only matching a set of required fields.
#[serde(required_fields)]
enum Untagged {
    A {
        a: string,
        other: Option<String>,
    }
    B {
        b: string,
        other: Option<String>,
    }
    C {
        a: string,
        b: string,
        other: Option<String>,
    }
}

This requires that each variant is also validated to not contain any optional fields. E.g. variant A would not be permitted to have an optional field b.
This approach could be considered overly specialized for a single use-case.
Solution 2: Provide the user with hooks to implement a custom variant resolution mechanism
One somewhat hacky option could be to permit the specification of a custom variant resolver through a custom function:
#[serde(untagged(variant_names = "UntaggedNames", variant_resolution = "Untagged::solve_variant"))]
enum Untagged {
    A {
        a: string,
    }
    B {
        b: string,
    }
    C {
        a: string,
        b: string,
    }
}

impl Untagged {
    fn solve_variant<'de, D, V>(deserializer: D, deserialize_variant: V) -> Result<Untagged, D::Error>
        where V: FnOnce(UntaggedNames) -> Result<Untagged, D::Error>
    {
        deserialize_variant(UntaggedNames::A)
    }
}

Because I'm not overly familiar with the internals of serde, I currently don't know how viable this approach would be.

You could either use the existing deny_unknown_fields attribute:
#[derive(Deserialize)]
#[serde(untagged, deny_unknown_fields)]
enum Untagged {
    A {
        a: String,
    },
    AB {
        a: String,
        b: String,
    },
}

or order the variants such that any variant with a superset of the fields of a different variant always appears earlier:
#[derive(Deserialize)]
#[serde(untagged)]
enum Untagged {
    AB {
        a: String,
        b: String,
    },
    A {
        a: String,
    },
}

depending on whether you want unrecognized fields to error out or select the maximally matched variant (respectively).
Beyond that, you could lose the #[derive(Deserialize)] and emit your own Deserialize trait implementation to perform variant resolution in whatever way you want.

The solution with deny_unknown_fields is neat, and I believe does everything I need. It was not obvious to me that this was a solution, so I appreciate the pointer!
Now, I'm curious if it would valuable to have an option to untagged that causes it to solely discriminate based on the presence of fields to improve error reporting*? Committing to one of the variants would improve diagnostics where that is possible. It could be a step towards improving on #773.
*: https://play.rust-lang.org/?gist=61b91ff79ddd3ad4bb014c1378a28c5b&version=stable

I would prefer to solve #773 without introducing another attribute.


PINCache's Carthage seems does not support watchOS

Hi.
I'm the maintainer of SDWebImage, and I'd like to provide a custom cache integration plugin of PINCache into SD's cache system.
The plugin is here: https://github.com/SDWebImage/SDWebImagePINPlugin
However, although the readme point the PINCache support watchOS, and the CocoaPods one support as well. For Carthage, it does not support watchOS. Because of the Xcode scheme does have any configuration for watchOS, even no any target.
See log:
➜  SDWebImagePINPlugin git:(master) ✗ carthage update --no-use-binaries --platform watchos
*** Fetching SDWebImage
*** Fetching PINCache
*** Fetching PINOperation
*** Checking out SDWebImage at "5.7.2"
*** Checking out PINCache at "3.0.1-beta.8"
*** Checking out PINOperation at "1.1.2"
*** xcodebuild output can be found in /var/folders/y4/_98b424x3jv54_1tbfvswjpm0000gn/T/carthage-xcodebuild.lY4DVH.log
*** Skipped building PINOperation due to the error:
Dependency "PINOperation" has no shared framework schemes for any of the platforms: watchOS

@kinarobin Hi. Can you provide some feedback to the team member, or are there any user who maintain the issue lists and PRs ?
If so, I can create a PR for this Carthage watchOS fix.

Seems the PINCache already merge the Carthage support. Once they release new version, I'll update this PR.

Seems PINOperation does not release new version. PINCache's WatchOS target still broken. @garrettmoon

Seems...PINCache does not have a watchOS target?


[MRG] [FIX] Regression introduced by #4936

assert_allclose(data1, data2)
see
https://github.com/mne-tools/mne-python/pull/5591#issuecomment-427772424

looks good to me ...

When did the old _strip_to_integer function fail?

@cbrnr it is not that the _strip_to_integer failed (perse) is that some of the functionality in read_events_{eeglab|brainvsion|xxx} drop events. This right now is taken care by event_id_func so _strip_to_integer alone cannot take care of it.
I know, the naming right now is far from ideal. But this PR is just a hotfix, needed in #5591. Once we don't use deprecation code, I intend to improve a bit whatever is left. And review all the namings (and deprecate the old ones) once the behavior of all readers is more or less unified.
So, if you think that its good enough. Please merge.


Add better subscriptions support

Following the GraphQL Subscriptions RFC, simple subscriptions queries should be possible using altair. Although there are several push mechanisms that could be used, altair should be able to function with the web socket mechanism.
https://github.com/facebook/graphql/blob/master/rfcs/Subscriptions.md

This feature has been implemented. Still requires extensive testing though.


Update nightly toolchain

Updates the nightly toolchain to the most recent one.
Uses the new prelude functions that came with 1.80.
Use LazyLock instead of lazy_static.
Remove unused features.
Update used features that changed.
Removed unneeded "allow(suspicious_auto_trait_impls)".
Synced the order of attributes between all crates.

Thank you!
There seems to be a regression in the newer version of rustfmt, but it's not a problem :+1:


Thanks for pointing this out! Would you create a pull request for the 2.x branch to add folder creation?

I keep getting this problem. The script init-letsencrypt.sh is not working.

ng01        | 2019/11/30 16:49:08 [emerg] 1#1: unexpected end of file, expecting ";" or "}" in /etc/letsencrypt/options-ssl-nginx.conf:2
ng01        | nginx: [emerg] unexpected end of file, expecting ";" or "}" in /etc/letsencrypt/options-ssl-nginx.conf:2
@wmnnd Tried to use v.2.x, but got this error

There is the case that you have to make a few small changes to the init-letsencrypt.sh file in case that you are not using a single docker-compose.yml file. If you are using multiple docker-compose files you have to pass the file names to any docker-compose command. for example instead of:
docker-compose run ...
to replace it with the:
docker-compose -f docker-compose.yml -f docker-compose.production.yml run ...
There have to be done 5 replacements.

Same problem. Have any solution?

I think you may have to make changes to the init-letsencrypt.sh. Just adapt it to your needs (you can see a change in docker-compose commands in my previous post)


MF-1435 - Fix fetching user members of an empty group

Signed-off-by: Burak Sekili<EMAIL_ADDRESS>What does this do?
This PR prevents fetching all user members from empty groups while using /groups/<group_id> endpoint of the users package.
Which issue(s) does this PR fix/relate to?
Resolves #1435
List any changes that modify/break current functionality
I updated users/postgres/users_test.go
Have you included tests for your changes?
Yes
Did you document any new/modified functionality?
No
Notes

Codecov Report

Merging #1436 (7738ecd) into master (68af0e3) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1436      +/-   ##
==========================================
+ Coverage   69.26%   69.29%   +0.02%
==========================================
  Files         123      123
  Lines        8454     8461       +7
==========================================
+ Hits         5856     5863       +7
  Misses       2072     2072
  Partials      526      526

Impacted Files
Coverage Δ

users/postgres/users.go
54.97% <100.00%> (+1.92%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 68af0e3...7738ecd. Read the comment docs.

Great fix, thanks @buraksekili


Don't discard non-special tokens in macro invocations

vec![Foo::bar()];
baz![?];

The :: and ? are not included in the syntax tree. I think this is because _non_special_token is matching these with a regular expression, unlike e.g. as.
https://github.com/tree-sitter/tree-sitter-rust/blob/cc7bdd3e6d14677e8aa77da64f6a3f57b6f8b00a/grammar.js#L193-L198
This is causing issues for difftastic, where Foo::bar() preserves the :: but vec![Foo::bar()] does not.

Related: https://github.com/tree-sitter/tree-sitter/issues/1151

I'm hoping this is fixed on master, try it out!
But a good idea might be to just inject Rust inside a macro's token tree