ignore undefined properties

This PR allow properties to be undefined, as we do not always have control on what is given, removing the undefined props from user code would be cumbersome.

Thanks for your contribution to the VanJS project! Could you describe the primary use cases of this feature?

In the following  simplified example which attempt to implement an input component, the id property may be undefined.
import { css } from "goober";

export default function (context, options = {}) {
  const { theme, van } = context;
  const { palette, shape, shadows } = theme;
  const { div, input, label } = van.tags;
  const style = {
    base: css`
      position: relative;
      display: inline-block;
      font-size: 1rem;
      min-height: 3rem;
    `,
  };

  return (props) => {
    const {
      name,
      id,
      disabled,
      label: labelValue = "",
      error = "",
      ...otherProps
    } = props;
    return div(
      {
        class: `${style.base}`,
      },
      input({
        id,
        name,
        type: "text",
        required: true,
        disabled,
        ...otherProps,
      }),
      label({ htmlFor: id }, labelValue)
    );
  };
}

I'm not fully onboard with adding this complexity to VanJS library for this feature.
For the use case you described, there is a relatively simple workaround:
input({
  id ?? "",  // `id` can be undefined
  name,
  type: "text",
  required: true,
  disabled,
  ...otherProps,
})

which can serve your need despite being slightly more verbose. This is indeed similar to #16.
I have to admit that compared to other users in VanJS community, I might value much more the simplicity of library and the symbolic value of being the smallest reactive UI framework in the world. Probably this is because I have put so much heart and soul into optimizing the bundle size, byte-by-byte, thus I might be picky about the additions to the core library. That being said, I might change my mind if I see very compelling reason about the usefulness of this feature.

On one hand it add a few bytes on the lib, on the other side, it adds more code and hassle on the client's code, making the overall bundle size bigger.
It was bitten by the same issue  #16, allowing null or undefined in children makes our code much simple and safer.

After thinking through this feature and some related issues, my current thought is probably it's better to leave the current behavior as-is. The problem of this feature is:
For DOM node, the value of a property can be a primitive, a state, or a state-derived property. If we define that the property should be ignored for a primitive undefined, what should be the behavior for a state-valued property whose val is undefined? For the sake of consistency, a property value with a state whose val is undefined would mean the property shouldn't exist. Thus let's consider the example below:
const id = van.state("1")
const dom = div({id})
id.val = undefined // expecting `id` of `dom` to be deleted. However it's hard to do.

In practice, it's hard to find a consistent way to "delete" a property of a DOM element. delete dom.id wouldn't work as the statement will simply be ignored in DOM. dom.removeAttribute("id") would work for this case but there are certain properties dom.setAttribute(...) and dom.removeAttribute(...) are not the right behavior, such as value or checked properties.
I guess for your use case, maybe the best way is to provide a default value for id:
const {
  name,
  id = "",
  disabled,
  label: labelValue = "",
  error = "",
  ...otherProps
} = props;

At the moment, passing a null or an undefined property value results in a crash, IMHO, this is not acceptable as a library must be bullet proof whatever the input.

I am not aware not any scenario where VanJS could crash the web page (if you have an example, please let me know). If by "crash", you mean an error being thrown, I think that is a common practice among JS frameworks. For instance, the following jQuery code will result an error being thrown:
$('div').click("unknown")

Additionally, if you're using van-{VERSION}.debug.js, you will get a very readable error message when the error is thrown:
Invalid property value for id: Only string, number, boolean, bigint are valid prop value types

Using van-{VERSION}.debug.js is recommended during development whenever an error or anything unexpected occurs.
Hope that addresses your concerns.

By crash, I meant a blank screen, which happened for both #39  and #40

If an exception happens before the rendering process, which means none of rendering code will be executed, the blank screen is working as intended, which is not a crash.
Per current version of VanJS, undefined property value is not supported. This is documented in the API reference. A type error will arise if you're using TypeScript, and an error message will pop up right upon using it if van-{VERSION}.debug.js is being used.
Right now I'm quite open to extend the VanJS API to support undefined property value. My current struggle is how to handle state and non-state objects consistently. If you discover a good way to handle it, please let me know. That will effectively unblock this feature.

The blank screen happens for these 2 use cases:
div({ a: undefined })
div(undefined)

The stack trace is:
van.js:54 Uncaught TypeError: Cannot convert undefined or null to object
    at getPrototypeOf (<anonymous>)
    at van.js:54:9
    at Array.forEach (<anonymous>)
    at van.js:52:22
    at App (main.js?t=1685653953858:28:5)
    at main.js?t=1685653953858:32:21

A example of such code can be found at https://github.com/FredericHeem/van-playground

A third way to get a blank screen in the following condition:
const inputState = van.state(undefined);
and
p({ id: inputState })

Thanks @FredericHeem for providing the examples!
I would like to summarize the current status of the discussion. In general 2 issues are being discussed in this thread:
1. Whether VanJS should support undefined as property value in tag function? (A related question is: whether VanJS should support null or undefined as child DOM node in tag function?)
For this question, my general feeling is, as mentioned in https://github.com/vanjs-org/van/pull/39#issuecomment-1570749303, there should be more benefit than drawback to support undefined property values. It makes users' life easier and will most-likely generate a smaller overall bundle side (combining VanJS code and users' client code).
On the other hand, the main blocker of implementing this feature is what was discussed in https://github.com/vanjs-org/van/pull/39#issuecomment-1571314602/. That is, generally the behavior of state-valued property and primitive-valued property should be consistent. If we define undefined property value as the absence of the property, for the sake of consistency, changing the val of a state-valued property to undefined should have the same effect of constructing a DOM element with undefined as the property value. In other words, the code below:
const id = van.state("some_id")
van.add(document.body, div({id}))
id.val = undefined

should produce the same result as:
van.add(document.body, div({id: undefined}))

but based on the current implementation of this PR, the first piece of code will produce

 while the second piece of code will produce

.
Based on my current understanding of the DOM model, it seems hard to align the behavior between undefined-valued property and state-valued property whose val has been changed to undefined. This is because in DOM, I haven't found a universal way to delete a property. For id property, probably a good way is assigning an empty string to the id property (or calling removeAttribute("id")). But for on... event handlers, the suitable way is assigning null to the on... property. So that is essentially the blocker of this PR. If we can find a good way to resolve the blocker, that will effectively unblock this PR.
2. Given the current version of VanJS, where undefined is not supported as a valid property value, is the current behavior in VanJS (which throws an exception upon calling to tag function) appropriate?
IMHO, I believe the behavior in VanJS is appropriate. A library can define the interface of its API, which defines what contract the client code needs to follow. Since undefined property value is not supported in the current version of VanJS, calling a tag function with undefined property is undefined behavior by definition, and the library can choose the behavior that is convenient. Indeed, the current behavior in VanJS (throwing an exception) is not a bad one. It lets users know that they're not using the API in a right way at the earliest point, rather than silencing the buggy code. Since usually tag functions are called before the DOM elements being added to document tree via van.add, throwing exceptions in tag functions usually means no change will be reflected in the DOM tree, which means having a blank screen is an intended behavior if the exception is thrown at the page loading time.
On the other hand, VanJS has tried its best to instruct its users that undefined property is not supported in the current version. The API reference of tag function clearly defines what can be accepted as property values, where undefined is not one of them. Users will get type errors if they work with VanJS in TypeScript. And van-{VERSION}.debug.js will print an unambiguous error message to highlight the problem whenever the tag function is being called this way.

Thanks @FredericHeem for providing the examples!
I would like to summarize the current status of the discussion. In general 2 issues are being discussed in this thread:
1. Whether VanJS should support undefined as property value in tag function? (A related question is: whether VanJS should support null or undefined as child DOM node in tag function?)
For this question, my general feeling is, as mentioned in https://github.com/vanjs-org/van/pull/39#issuecomment-1570749303, there should be more benefit than drawback to support undefined property values. It makes users' life easier and will most-likely generate a smaller overall bundle side (combining VanJS code and users' client code).
On the other hand, the main blocker of implementing this feature is what was discussed in https://github.com/vanjs-org/van/pull/39#issuecomment-1571314602/. That is, generally the behavior of state-valued property and primitive-valued property should be consistent. If we define undefined property value as the absence of the property, for the sake of consistency, changing the val of a state-valued property to undefined should have the same effect of constructing a DOM element with undefined as the property value. In other words, the code below:
const id = van.state("some_id")
van.add(document.body, div({id}))
id.val = undefined

should produce the same result as:
van.add(document.body, div({id: undefined}))

but based on the current implementation of this PR, the first piece of code will produce

 while the second piece of code will produce

.
Based on my current understanding of the DOM model, it seems hard to align the behavior between undefined-valued property and state-valued property whose val has been changed to undefined. This is because in DOM, I haven't found a universal way to delete a property. For id property, probably a good way is assigning an empty string to the id property (or calling removeAttribute("id")). But for on... event handlers, the suitable way is assigning null to the on... property. So that is essentially the blocker of this PR. If we can find a good way to resolve the blocker, that will effectively unblock this PR.
2. Given the current version of VanJS, where undefined is not supported as a valid property value, is the current behavior in VanJS (which throws an exception upon calling to tag function) appropriate?
IMHO, I believe the behavior in VanJS is appropriate. A library can define the interface of its API, which defines what contract the client code needs to follow. Since undefined property value is not supported in the current version of VanJS, calling a tag function with undefined property is undefined behavior by definition, and the library can choose the behavior that is convenient. Indeed, the current behavior in VanJS (throwing an exception) is not a bad one. It lets users know that they're not using the API in a right way at the earliest point, rather than silencing the buggy code. Since usually tag functions are called before the DOM elements being added to document tree via van.add, throwing exceptions in tag functions usually means no change will be reflected in the DOM tree, which means having a blank screen is an intended behavior if the exception is thrown at the page loading time.
On the other hand, VanJS has tried its best to instruct its users that undefined property is not supported in the current version. The API reference of tag function clearly defines what can be accepted as property values, where undefined is not one of them. Users will get type errors if they work with VanJS in TypeScript. And van-{VERSION}.debug.js will print an unambiguous error message to highlight the problem whenever the tag function is being called this way.

With the 1.0.0 release, div({id: undefined}, "Text") will produce
Text
 instead of throwing an error.

I filed https://github.com/vanjs-org/mini-van/issues/6 & will move my comments here.
The types should allow undefined even if undefined is ignored in the implementation. If a component has an optional prop, then it's value is undefined.
function MyComponent({ id, text }: { id?: string, text: string }) {
  return div({ id, class: 'MyComponent' }, text)
}

With the current implementation, I'm forced to work around the type check.
function MyComponent({ id, text }: { id?: string, text: string }) {
  return div({ ...(id === undefined ? {} : { id }), class: 'MyComponent' }, text)
}

Thanks @btakita for your remark!
I think there could be personal opinions regarding this issue. I think there are multiple things to trade-off:

The consistent behavior regarding undefined. Ideally:

div({id: undefined})

const id = van.state(undefined)
div({id})

and
const id = van.state("id")
div({id})
id.val = "undefined"

should produce the same result.

The little bit convenience on the user code. i.e.: the ability to write

div({id})

instead of
div({...(id ? {id} : {})})

My personal opinion is: 1 is more important than 2. Thus without a good solution on 1, it's probably better to settle on a few more characters of code to handle the absence of the properties.

Perhaps a helper function would be a way to get around the impasse?
function cleanProps(props:Object) {
  for (const key of Object.keys(props)) {
    if (props[key] === undefined) props.delete(key)
  }
  return props
}

I am open to this. It's unclear to me at the moment whether it's worthwhile to add it into the official VanJS or VanX package. The function is quite easy to implement on the user side for whoever wants it. I will wait to see if there a universal need from the public for this helper function before deciding whether to include it in official packages.

Sounds good. At least we have a viable solution posted. I'm probably going to use a wrapper Proxy around the van object with various helpers for now.


add grpc gw http listener

see https://github.com/opiproject/opi-smbios-bridge/pull/174

resolved in https://github.com/opiproject/opi-spdk-bridge/pull/635


Implement network interfaces logging at exit

Signed-off-by: Taiki Ono<EMAIL_ADDRESS>Fixes https://github.com/tetratelabs/getenvoy/issues/40
Interfaces() is just a wrapper of golang std's Interfaces() and it safely picks up interfaces. https://github.com/shirou/gopsutil/blob/v2.19.8/net/net.go#L212 And we can use JSON format to log interfaces at that time safely https://github.com/shirou/gopsutil/blob/v2.19.8/net/net.go#L193.
Output example:
[{"mtu":65536,"name":"lo","hardwareaddr":"","flags":["up","loopback"],"addrs":[{"addr":"<IP_ADDRESS>/8"},{"addr":"::1/128"}]} {"mtu":1500,"name":"eno1","hardwareaddr":"","flags":["up","broadcast","multicast"],"addrs":[{"addr":"<IP_ADDRESS>/24"},{"addr":""},{"addr":""},{"addr":""}]} {"mtu":1500,"name":"docker0","hardwareaddr":"","flags":["up","broadcast","multicast"],"addrs":[{"addr":"<IP_ADDRESS>/16"}]}]

@liamawhite Good catch, updated the PR description.

@taiki45 FYI, that output example isn't valid JSON. The array elements are missing trailing commas.

@liamawhite ah, I filtered hardware addresses and v6 addresses, so it's just my mistake. updated.


Express Action Bar

@GarthDB  is going to review the CSS for Action Bar to confirm that it looks good.
synced to jira: https://jira.corp.adobe.com/browse/CSS-16

Checked and looks good until Design provides updated UI Kits for Express.


Favorites and Presets load but do not play

I have this awesome setup working for most things, however when I tell Sonos "Alexa, tell Sonos to play favorite "MY Favorite" in the Living Room" it loads up the favorite in the Sonos app but does not start playing.  Same thing happens with presets.  Please help!

I have noticed that playlists that have a single word e.g. 'Genesis' have no issue playing. However, two word descriptors such as 'Boy's Favorites' with a space between the words do not. Changing the descriptor to 'Boysfaves' fixed the issue for me. This is just my own experience. I am sure it wasn't meant to work like this and my British accent has sometimes caused other issues with Alexa!.

Single word presets/playlists do not work for me either.  Really does a good job changing to the station but just queues it, still have to press play in the songs app.

I'll take a look this week when I have a few kid-free minutes at home.  I'm guessing this will be as simple as sending a /play command after favorite and playlist requests

Thanks. Also, a huge thank you for putting this skill together.
Sent from my mobile device.

On Feb 6, 2016, at 6:55 PM, Ryan Graciano<EMAIL_ADDRESS>wrote:
I'll take a look this week when I have a few kid-free minutes at home. I'm guessing this will be as simple as sending a /play command after favorite and playlist requests
—
Reply to this email directly or view it on GitHub.

Jumping into the thread, same issue here, seems I have to actually hit Play in the sonos app when changing favorites.  Doesn't matter if it is one word or multiple word favorites.  Thanks for any help!

Has anyone been able to resolve this issue?  Much appreciation for everyones help!

@rwupson - I put together a small fix for this issue, but I'm out skiing this week so I can't actually test it :) If you want to be a bleeding edge adopter, then here are the instructions to test it yourself:
Add this function at the bottom of index.js:
/** Handles playlists and favorites */
function playlistHandler(roomValue, presetValue, skillName, response) {
var room = encodeURIComponent(roomValue);
var playlist = encodeURIComponent(presetValue);
options.path = '/' + room + '/' + skillName + '/' + playlist;
httpreq(options, function() {});

options.path = '/' + room + '/play';
httpreq(options, function() {
    response.tell("Queued and started " + playlist);
});

}
Delete the functions for PlaylistIntent and FavoriteIntent elsewhere in index.js. Replace them with:
PlaylistIntent: function (intent, session, response) {
    console.log("PlaylistIntent received");
    playlistHandler(intent.slots.Room.value, intent.slots.Preset.value, 'playlist', response);
},

FavoriteIntent: function (intent, session, response) {
    console.log("FavoriteIntent received");
    playlistHandler(intent.slots.Room.value, intent.slots.Preset.value, 'favorite', response);
},

And that's it - zip up the stuff in lambda's src/ folder including your new index.js, upload to Lambda, and see if it works.

No luck here...the echo did say "Queued and started PLAYLIST" but then nothing unfortunately!! I have 3 devices, trying this one on the Master Bedroom, anyone else have any luck?  Thanks!!

I pushed a fix today and verified it's working on my local setup.  The quick patch I'd hacked out here wasn't using actOnCoordinator, but the new version does and seems to be reliable.
Note that I saw some weird behavior with actOnCoordinator before I upgraded node-sonos-http-api to the latest version, so if you have any trouble, give that a try first.

Note: to upgrade, upload index.js to Lambda.  The new index.js also merges a pull request from someone who added room functionality to pause/resume, so you should update utterances and intents in the Alexa Skills Kit while you're at it, if you want those features to continue working.

Thanks very much Ryan. Great product.
From: Ryan Graciano<EMAIL_ADDRESS>Sent: Sunday, February 14, 2016 11:35 AM
To: rgraciano/echo-sonos<EMAIL_ADDRESS>Cc: BarriePike<EMAIL_ADDRESS>Subject: Re: [echo-sonos] Favorites and Presets load but do not play (#17)
I pushed a fix today and verified it's working on my local setup. The quick patch I'd hacked out here wasn't using actOnCoordinator, but the new version does and seems to be reliable.
Note that I saw some weird behavior with actOnCoordinator before I upgraded node-sonos-http-api to the latest version, so if you have any trouble, give that a try first.
—
Reply to this email directly or view it on GitHub https://github.com/rgraciano/echo-sonos/issues/17#issuecomment-183933929 .

Awesome - I am going to try it now - Thanks very much - agreed, great product!


[GC] s3 client ignores Hadoop AWS configuration

S3 java client only works with AssumedRoleCredentialProvider, and should also work with DefaultAWSCredentialsProviderChain in order to get credentials from spark configurations.

Sorry about this! Definitely exists in code I wrote; May also have existed prior to adding support for assumed roles.
It (probably...) ends up leading a default AWS configuration, so I expect it will work with aws environment variables, instance profiles, etc. Just not with the easiest configuration.

We tried it with aws environment variables and it did work. :)


add company: Mia-Platform

Hi @akelity, please follow the contribution guidelines when submitting a PR. Thanks

Sorry for the mistake, I applied the changes.


#payroll icon

Resolves: #3

I can't marge because of rebase conflict. Let me look into it.

All right, I got it in with ad906dd75d6148300dde5cf4a742370d42058f61, thanks for your help!


AbstractCompilationAnalyzer: log each compilation's VName [phab:D1677]

Created by schroederc at 2017-05-26 18:44:27:

fromberger accepted this revision at 2017-05-26 18:48:30

schroederc closed via commit 276d4ecc906629ed2980ec8caa04ac1ae111777c at 2017-05-26 18:52:28


Google Play Store rejection - malware/uploading contacts

We use contacts locally on the device for a legitimate reason, and DO NOT upload them to any server but keep getting rejected. We have our Privacy policy linked both from the store listing, the sign up page in the app and the settings page. Yet, we get robotic rejection emails claiming that:
During review, we found that your app violates the Malware policy. We don’t allow apps with any code that could put a user, a user’s data, or a device at risk. You can read through the Malware policy page and review the User Data policy for more details.
For example, your app is uploading users' Contact List information to [our api url] without posting a privacy policy in both the designated field in the Play Developer Console and from within the Play distributed app itself.
I get the feeling that some automated code tests that Google run is triggering 'something', as this is a completely legitimate use of an official API and we are complying with the Privacy policy part. Have been trying to resolve this for two weeks now without success, super frustrating.
Have other people experienced this and if so how did you get past the reviews?
(We use v0.4.6)

I just had my app removed this morning for similar reasons, and we also absolutely do not upload the contacts from the device.
In our case, it's for an "invite" form, where someone can enter an email, or choose a contact, and we read the email from that. As exepcted, the appeal to Google is going nowhere so far..
@danielnordh Did you ever get a resolution to this, or do I have to remove this plugin?

I did eventually get the app approved, but not in a way that made sense.
After trying to communicate with the Google review people (by using their dispute system) and getting nowhere, I submitted a new version WITHOUT the contacts package. This release was approved.
I then submitted a new release WITH the contacts package back in. This was also approved.
No idea why this worked, but it did for me. I'd say this is on Google.

@danielnordh yeah this would be on Google's automated review process (false positive malware flag)


Add Mac and Windows to CI

Summary
This PR adds Windows and Mac to the full test suite run during CI. We now have 9 jobs running in CI (Python 3.8, 3.9 and 3.10 for Ubuntu, Windows and Mac).
All core functionalities are working, however a couple little issues remain, opened for later work: making outputs of SciPy fully consistent between OS due to floating point considerations, making Sphinx work on all OS, and making PROJ work on Windows to use proj-data grids.
In details
This PR:

Unsets the PROJ_LIB variable during CI to allow rasterio to import correctly, otherwise failing on Windows. This fix is recommended by https://rasterio.readthedocs.io/en/latest/faq.html#why-can-t-rasterio-find-proj-db-rasterio-from-pypi-versions-1-2-0. Curiously, this is not needed in GeoUtils' CI, I couldn't figure why it fails in xDEM exactly (similar environments);
Performs rounding of the results of scipy.optimize.least_squares after setting a lower xtol to ensure the optimized parameters found are the same between OSs. This works to get the exact same output of NuthKaab() co-registration on Windows and Linux, but somehow still differs on Mac... Added a comment on this in issue #310.
Tries to do the same rounding operation for scipy.optimize.basin_hopping but the xtol parameter does not exist as such, we would need to derive the tolerance of the parameter from the scipy method and ftol or gtol parameters, opened issue #310;
Skips tests related to grids stored by proj-data in test_dem.py on Windows, that currently can't be found, opened issue #311;
Skips the building of the documentation with Sphinx that fails on both Mac and Windows with the same TypeError: 'module' object is not callable when xdem.examples.get_path() is called, notably in examples/*/plot_*.py scripts for sphinx-gallery, opened #316.

Unrelated but needed to fix bugs related to package updates, this PR:

Forces the version of openh264 in environment.yml at 2.3.0 (on which opencv depends), as it started failing with 2.3.1 on 24.09.22 (probably an erroneous release from them...), opened #317;
Upgrades pre-commit hooks to solve a mypy issue with the latest Python 3.10 version: https://github.com/python/mypy/issues/13627;
Updates the regex pattern to catch RuntimeWarning with true_divide, as those can be simply called divide now.

Resolves #126

Haha, I see some failure on Windows 😆

One issue closed, four open! But at least now we know that all the important stuff works as intended on all OSs! :partying_face:
Ready to merge, then I'll add the cache in xDEM to speed up CI, that can take up to 30min right now...

Merging as there's only two comments added since last approval


update for newly release  Java mgmt packages in csv

Emm, broken link again... why file:///home?
'file:///home/vsts/work/1/s/azure-sdk/_site/releases/2021-02/ios.html' has 1 broken link(s):
  ***-for-ios/blob/master/CHANGELOG.md
'file:///home/vsts/work/1/s/azure-sdk/_site/releases/2021-03/ios.html' has 1 broken link(s):
  ***-for-ios/blob/master/CHANGELOG.md
'file:///home/vsts/work/1/s/azure-sdk/_site/releases/2021-01/ios.html' has 1 broken link(s):
  ***-for-ios/blob/master/CHANGELOG.md
'file:///home/vsts/work/1/s/azure-sdk/_site/releases/2020-10/ios.html' has 1 broken link(s):
  ***-for-ios/blob/master/CHANGELOG.md
'file:///home/vsts/work/1/s/azure-sdk/_site/releases/2020-11/ios.html' has 1 broken link(s):
  ***-for-ios/blob/master/CHANGELOG.md

broken links fixed with https://github.com/Azure/azure-sdk/pull/2752


How to install extra components like image-reflector-controller,image-automation-controller using Fluxv2 Terraform module?

I use the following Terraform Fluxv2 provider
provider "registry.terraform.io/fluxcd/flux" {
version     = "0.12.2"
...
Looking at flux-system namespace there are no deployments for image-reflector-controller and/or image-automation-controller. At the moment I see no option to customize using the TF resourcs flux_install  . Is this a point for development or am I missing an option here?

Please see https://github.com/fluxcd/terraform-provider-flux/blob/main/pkg/provider/data_install.go#L80

Sorry for that and thank you for the fast response. Really forgot to look at doc: https://registry.terraform.io/providers/fluxcd/flux/latest/docs/data-sources/install#components_extra


No module named 'pyarrow._plasma'

I am having problem in using pandarallel package which uses pyarrow. I have Windows 10, and  pyarrow installed without any issue.
from pandarallel import pandarallel
File "C:\Anaconda3\lib\site-packages\pandarallel_init_.py", line 3, in
from .pandarallel import pandarallel
File "C:\Anaconda3\lib\site-packages\pandarallel\pandarallel.py", line 2, in
import pyarrow.plasma as plasma
File "C:\Anaconda3\lib\site-packages\pyarrow\plasma.py", line 29, in
from pyarrow._plasma import (ObjectID, ObjectNotAvailable, # noqa
ModuleNotFoundError: No module named 'pyarrow._plasma'

Thanks for the feedback! Unfortunately plasma doesn't currently work on Windows :(
We are starting some renewed efforts to port it, but I can't provide guarantees or a timeline on it presently.


Recommend replacement list for some incompatible ops in TFLite

Hi TensorFlow Lite Authors,
It's glad to hear that there are some workaround for incompatible ops, such as ResizeOp, in TFLite. Would you mind share something like recommend replacement list for some of these bad ops? It will take us away from some troubles on early stage, the design stage, not the model deployment stage that things all are embarrassed to developers.
Looking for your reply,
Sun Aries.

@liyunlu0618

@liyunlu0618

Some context. During the cn-sig group discussion about MOT, user asked about incompatible ops like ResizeNearestNeighbor and Renjie mentioned it could be replaced with other TFLite compatible ops. This request is for us to provide a list with such examples as guidance.

Some context. During the cn-sig group discussion about MOT, user asked about incompatible ops like ResizeNearestNeighbor and Renjie mentioned it could be replaced with other TFLite compatible ops. This request is for us to provide a list with such examples as guidance.

Hi @SunAriesCN !
Attached list of  built in ops and select ops .  You can also register a custom operator in cpu and gpu kernel now.
Can the above pointers be considered as  answer to your query?
Thank you!
To disable quantization and debug your lite model, You can use tfl.quantization_debugger


Strange behavior when clicking on switch orgs menu

When clicking Switch Orgs, sometimes the menu disappears.
The desired behavior is:

the menu should not disappear when clicking switch orgs
the menu should not remain with the list of orgs after it is closed.

@russorat I've also observed clicking switch orgs sometimes causes the menu to close. In the above it looks like that eventually happened too after enough clicks.


[BUG]  unexpected CORS error on loading/opening map with cached layers

Bug Description
when opening/restoring layers from cache the GeoHub map is encountering CORS errors
Bug Reproduction
click on map
Bug Impact
No response
Bug Screenshots

Bug References
No response
Bug System Information

OS: [e.g. Windows 10]
Browser: [e.g. Google Chrome, Firefox]

┆Issue is synchronized with this Wrike task by Unito

let me close it


toggle in light is not working anymore  with logitech harmony bind with hue core

Description
since last update 0.3.0 im not able to use short press twice to toggle on and off and i could only long press to turn off from harmony hub remote (ive created a custom light with toggle as toggle action to reach this goal and it was working perfectly before)
prise1:
turn_on:
service: switch.toggle
entity_id: switch.ewelink_sa_003_zigbee_9ad66b22_on_off
turn_off:
service: switch.turn_off
entity_id: switch.ewelink_sa_003_zigbee_9ad66b22_on_off
Expected behavior
the goal here is to use a single press on my harmony remote linked with the virtual hue bridge to turn on and off the custom created light (that should turn on and of the switch)
Reproduction steps
create a custom light  device with turn_on : to call toggle switch service
Relevant log output
none

Operating system
HassOS
Install method
HassOS Addon
Version
0.3.0
Dev Version
No response
Any other information that may be helpful
No response

Can you please provide more details like logs and full reproduction steps? This information is not sufficient to say anything about the issue.

sure
here is the verbose output and it seems no input is occuring when i short pushed again after the first pushed remote button linked to the custom light (switch)... the last 2 inputs  are when i long pressed the logitech harmony remote button linked to the custom switch so it is not working has a toggle button as it used to be before...anyway thx again all  for this great addon
2023-02-01 13:18:03,396 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/10/state
2023-02-01 13:18:03,397 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:05,226 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/9/state
2023-02-01 13:18:05,230 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:06,319 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/10/state
2023-02-01 13:18:06,322 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:08,873 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/9/state
2023-02-01 13:18:08,876 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:10,207 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/10/state
2023-02-01 13:18:10,208 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:13,254 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/9/state
2023-02-01 13:18:13,258 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:14,082 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/10/state
2023-02-01 13:18:14,088 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:15,314 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/9/state
2023-02-01 13:18:15,315 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:15,879 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/10/state
2023-02-01 13:18:15,884 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:16,600 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/9/state
2023-02-01 13:18:16,604 DEBUG emulated_hue.apiv1 -- {"xy":[0,0],"on":true,"bri":0}
2023-02-01 13:18:28,106 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/10/state
2023-02-01 13:18:28,112 DEBUG emulated_hue.apiv1 -- {"on":false}
2023-02-01 13:18:29,813 DEBUG emulated_hue.apiv1 -- [<IP_ADDRESS>] PUT /api/MiPbTkSpULmNUR0xEJNzhqhTS7mMC3Ruzd64tZnd/lights/9/state
2023-02-01 13:18:29,818 DEBUG emulated_hue.apiv1 -- {"on":false}

It might be easier for you to simple create a new issue and follow the entire issue template so there is sufficient information there. Please ensure that you completely fill out the entire template including step by step reproduction steps from a clean fresh install as well as logs detailing the results and what you expect.


Clean up code style and pseudo-private member usage in passes/cmds/select.cc

Also adds a contains() member function to ObjRange in kernel/rtlil.h.
I think a benchmark comparison with and without this PR must be done before merging.  My concern is that in the original code, it has the RTLIL::IdString local, next to the RTLIL::Module * in memory.  In the new code that uses the ObjRange accessor functions, the name that is passed to many functions no longer local.  Instead, it's an indirect jump away, at e.g. wire->name.

@eddiehung would you mind running the benchmark suite on this?  Or, alternatively, could you point me to where I can download it?

My concern is that in the original code, it has the RTLIL::IdString local, next to the RTLIL::Module * in memory...

I'm not sure what you mean by this. Can you elaborate? As it stands, I don't see any performance concern.

@eddiehung would you mind running the benchmark suite on this? Or, alternatively, could you point me to where I can download it?

Unfortunately, we don't really have a decent benchmark suite for measuring runtime, we have a repository for benchmarks at github.com/YosysHQ/yosys-bench, but not any decent infrastructure to run it. I just run a few ad-hoc ones locally (if that) which is far from rigorous. @mithro to the rescue?

I mean that iterating over dict<RTLIL::IdString, RTLIL::Cell*> cells_ might be more performant for code that mostly passes that IdString and Cell* to other helper functions.  Maybe I'm wrong, but I would guess that the IdString and Cell* are close to each other in memory, maybe even on the same cache line.  If instead that IdString needs to be obtained by dereferencing that Cell*, that indirect memory access could take a relatively long time.

we have a repository for benchmarks at YosysHQ/yosys-bench, but not any decent infrastructure to run it.

Got it.  I'll check it out and hack something together just to see if there's any impact.

I mean that iterating over dict<RTLIL::IdString, RTLIL::Cell*> cells_ might be more performant for code that mostly passes that IdString and Cell* to other helper functions. Maybe I'm wrong, but I would guess that the IdString and Cell* are close to each other in memory, maybe even on the same cache line. If instead that IdString needs to be obtained by dereferencing that Cell*, that indirect memory access could take a relatively long time.

Sorry, still not following. If you want to lookup a Cell* from its IdString-name, then that's O(1). Can you give an example where IdString and Cell* are passed to a helper function?

OK, I looked over the changes and I can't find any instance of what I feared.  All new ->name accesses don't seem to incur any additional indirect memory access that wasn't already there.  So this probably won't have a big impact on performance.

OK, I looked over the changes and I can't find any instance of what I feared. All new ->name accesses don't seem to incur any additional indirect memory access that wasn't already there. So this probably won't have a big impact on performance.

Okay, I think I'm getting what you mean now. For https://github.com/YosysHQ/yosys/pull/1769/files#diff-8f49103b623e40720504e1f73fb0f31aL155-R157 it was previously returning a std::pair<> containing the IdString name as well as a Module*. Doing std::pair<>.first is arguably cheaper than (Module*)->name but I doubt you could get measure anything unless you had a truly humongous select benchmark, and I think it is superseded by cleaner more meaningful code.


Bug: Overridden configMaps remain in hanging state if deleted from base deployment template

📜 Description
Overridden configMaps remain in a hanging state if deleted from the base deployment template. This happens only in the case of cloned applications.
👟 Reproduction steps

Create an application let's say app1
Create a configMap in the base deployment template.
Override the configMap in env overrides.
Create an application let's say app2 cloned from app1
Delete the configMap from the base deployment template.
The configMap in environment overrides remains in an inheriting state and can not be deleted. It remains hanging.

👍 Expected behavior
The configMap's state should have been env rather than inheriting. And the option to delete the overridden configMap should have been present.
👎 Actual Behavior
The configMap in environment overrides remains in inheriting state and can not be deleted. It remains hanging.
☸ Kubernetes version
NA
Cloud provider

NA

🌍 Browser
Chrome
🧱 Your Environment
NA
✅ Proposed Solution
NA
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#5313

This was a production bug, when we clone an application with global cmcs and when it's overriden in an env, so when we delete the parent global cmcs, the env cmcs from which it was overriden, it should now be tagged as ENV not inheriting in cloned applications, now the default state for global variable for a cmcs is set as true(in case of cloned app), but in db by default it's stored as false, whether a cmcs is global or not we handle it with some logic at service layer. Hence in this case when we delete the global cmcs in the cloned app, since the global = true and overriden= false, it persists in inheriting state since front-end provides inheriting tag when global = true and overriden=false. but in normal application when we delete the global cmcs the fetch api in env section of cmcs has global=false and overriden=false which is correct.


Feature: Change copilot auth

Description
I recently switched which github account is tied to my copilot license (from personal to work account). There doesn't seem to be a way to change the account from the plugin's perspective.
I get this in the neovim console since my current account no longer has the association: RPC[Error] code_name = unknown, code = 1000, message = "Not authenticated: NotAuthorized"
When I use :Copilot auth in this state I get this popup:

When I hit "Copilot Settings", nothing seems to happen.
Possible Solution
A :Copilot command option that allows you to change the github account associated with copilot

I just found: https://github.com/zbirenbaum/copilot.lua/discussions/122#discussioncomment-4961665
Which points out the :Copilot auth signout option. This worked for me. Perhaps this should be added to the help docs?


⚠ ClamAV has degraded performance

In 674e47d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 465 ms

Resolved: ClamAV performance has improved in bf2ff27.


Add slash screen

There are some more options added can you add them as well

and add some screenshots from mobile view


chore: add sass build command

I did figure out how to get the development env setup but for some reason the checkboxes refused to cooperate..... anyway maybe you'll have better luck. I am currently in the process of moving over to logseq but I might give this another shot if I move back to obsidian.

Thanks for the PR! I'll look over the changes soon and get back to you!


Can't create machine with 'vmwarefusion' driver

Hello,
currently there is not way to create 'vmarefusion' machine.
I checked it on boot2docker versions:

v18.03.0
v18.04.0-ce-rc2

with docker-machine:

0.14.0
0.13.0 (it works with this version - see description below)

Here's the log without 'debug' enabled
docker-machine create --driver vmwarefusion --vmwarefusion-boot2docker-url https://github.com/boot2docker/boot2docker/releases/download/v18.04.0-ce-rc2/boot2docker.iso default1

Running pre-create checks...
(default1) Boot2Docker URL was explicitly set to "https://github.com/boot2docker/boot2docker/releases/download/v18.04.0-ce-rc2/boot2docker.iso" at create time, so Docker Machine cannot upgrade this machine to the latest version.
Creating machine...
(default1) Boot2Docker URL was explicitly set to "https://github.com/boot2docker/boot2docker/releases/download/v18.04.0-ce-rc2/boot2docker.iso" at create time, so Docker Machine cannot upgrade this machine to the latest version.
(default1) Downloading /Users/kamil/.docker/machine/cache/boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v18.04.0-ce-rc2/boot2docker.iso...
(default1) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
(default1) Creating SSH key...
(default1) Creating VM...
(default1) Creating disk '/Users/kamil/.docker/machine/machines/default1/default1.vmdk'
(default1) Virtual disk creation successful.
(default1) Starting default1...
(default1) Waiting for VM to come online...
Error creating machine: Error in driver during machine creation: exit status 255

Here are last few and essential lines from output with 'debug' enabled
[...]
(default1) DBG | executing: /Applications/VMware Fusion.app/Contents/Library/vmrun -gu docker -gp tcuser CopyFileFromHostToGuest /Users/kamil/.docker/machine/machines/default1/default1.vmx /Users/kamil/.docker/machine/machines/default1/userdata.tar /home/docker/userdata.tar
(default1) DBG | executing: /Applications/VMware Fusion.app/Contents/Library/vmrun -gu docker -gp tcuser runScriptInGuest /Users/kamil/.docker/machine/machines/default1/default1.vmx /bin/sh sudo sh -c "tar xvf /home/docker/userdata.tar -C /home/docker > /var/log/userdata.log 2>&1 && chown -R docker:staff /home/docker"
(default1) DBG | executing: /Applications/VMware Fusion.app/Contents/Library/vmrun -gu docker -gp tcuser runScriptInGuest /Users/kamil/.docker/machine/machines/default1/default1.vmx /bin/sh sudo /bin/mv /home/docker/userdata.tar /var/lib/boot2docker/userdata.tar
(default1) DBG | executing: /Applications/VMware Fusion.app/Contents/Library/vmrun -gu docker -gp tcuser enableSharedFolders /Users/kamil/.docker/machine/machines/default1/default1.vmx
Error creating machine: Error in driver during machine creation: exit status 255
notifying bugsnag: [Error creating machine: Error in driver during machine creation: exit status 255]

From what i found out, this issue could be present for a very long time. With docker-machine upgrade from 0.13.0 to 0.14.0 they started checking for errors from command outputs, so previously this issue might have popped up, but was ignored.
I'm able to reproduce it, so if you have any further request please let me know.
This might be related: https://github.com/wplib/wplib-box/issues/98#issuecomment-229820096

cc @frapposelli 😇

Good to know that there is a working solution, thanks!
Have you looked at the link i included at the end of my report? Maybe this issue can be fixed by installing newer open-vm-tools? (newest version is 10.2.5-8068406 vs currently used v10.0.0-3000743 from August 2015)
If there is some easy way for me to check it, please let me know. There's no manual on how to do it, but i guess that .iso file can be built, by running Dockerfile?

i'm experiencing this issue which i think is related: https://github.com/docker/machine/issues/4479

I have had the same issue but I was able to resolve it by regenerating the certs for my docker-machine that failed in the creation process. docker-machine regenerate-certs [NAME OF THE FAILED Docker Machine], I am running it on 2015 Mac OS Mojave hope this helps.

are you saying that regenerating the certs successfully enables shared folders?

my problem seem to resolve after regenerate-certs as what mraligorithm stated.  Please see this link
https://github.com/sparkfabrik/sparkdock/issues/14

@koksin i don't know if what you referenced is the same problem unless some how regenerating the certs causes mounting of the volume to some how be successful.
sad that there hasn't been any movement on this issue either way.

Closing since this is really a bug in docker-machine's built-in vmwarefusion driver, not boot2docker.
(See https://github.com/boot2docker/boot2docker/issues/1340 and https://github.com/boot2docker/boot2docker/pull/1350 for a more recent VMware-related issue that will be fixed in the next ISO release.)

Ok noted.
Sent from Mail for Windows 10
From: Tianon Gravi
Sent: Thursday, November 22, 2018 9:35 AM
To: boot2docker/boot2docker
Cc: koksin; Mention
Subject: Re: [boot2docker/boot2docker] Can't create machine with'vmwarefusion' driver (#1315)
Closing since this is really a bug in docker-machine's built-in vmwarefusion driver, not boot2docker.
(See #1340 and #1350 for a more recent VMware-related issue that will be fixed in the next ISO release.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@mraligorithm thanks a lot! That's a viable solution!


💡 [Feature]: move img to Image tag from next/image

Is your feature request related to a problem? Please describe.
We should use <Image /> from next/image in place of img element.
Describe the solution you'd like
Using Next.js image helps us in lazy loading, image optimization and serves the image as .webp format
I don't know if there was some reason for using img element in the first place

Hi @niteshseram, picking this one! PR coming soon :rocket:

@rehan-sattar Thanks for taking up the issue. But I would like to wait for a reply from @atapas to see if this feature is needed or not. Don't yet start, let him confirm and assign you

Oh, Thanks for informing me! Waiting :smiley:

Not fixing


Add documentation about localTs and expectOnly option

The CLI accepts these options (localTs and expectOnly) but they're not documented anywhere. I have to look through the issues to realize they exist.
--localTs - https://github.com/microsoft/dtslint/issues/231#issuecomment-515769378
--expectOnly - https://github.com/microsoft/dtslint/issues/208#issuecomment-467977621
I think it'd be very helpful if this information could be found on the readme as well.

Updated the description. Could you please take a look?


Update Generic Pages “contact”

Automatically generated by Netlify CMS

👷 Deploy Preview for strong-beijinho-c4d917 processing.

Name
Link

🔨 Latest commit
e8b1d9496bd4771c6b1e5287f6b9aa1907d2a035

🔍 Latest deploy log
https://app.netlify.com/sites/strong-beijinho-c4d917/deploys/65eab487251f2b0007424b9d


feat: increase AWS scan rate

AP-2560 Increase scan rate of Cloud Connector Unified client
Changes:

Add worker pool
AWS concurrency at the account + region level
aws_endpoint_url setting
add max proc setting
test scan_all pool fix
add AwsScanContext
make get_aws_client use new scan context

TODO:

fix the pool unit tests (can't use a pool in self.pool that gets pickled into the workers)
ignored_tags
find an easier way to manage scan context & get aws client

Branch worker-pool-v4.0 will track this work as a feature branch until AWS, Azure, & GCP are all converted. Then worker-pool-v4.0 will be merged into main.


About license

Thanks for the excellent work. I just see the license for the project is https://github.com/salesforce/BLIP/blob/main/LICENSE.txt. I want to know whether the license for the released models is also the same? Thanks

Yes the model follows the same license.

Thanks


app is crashing on start android 10 uniherthz titan

Launching first time it show for me to set permission.
After setting it via adb through : adb shell pm grant com.draco.buoy android.permission.WRITE_SECURE_SETTINGS
the app restarted but then crashed. I restared phone, but app is crashing everytime i launch it
Using titan with android 10 (by titan) with a lot of default apps and bloatware disabled via adb commands
Any suggestion on how to be able to run your app. At least 2 other people reported the same n google f**cK play store

Anyway this app does not work, any changes on your setting does not affect anything. Apps are still standby.


Add a way to run REST tests separately

We should create a new image to run REST tests (instead of running them for every language), or provide a flag to run them.
# something like this
RUN_REST_TESTS=1 bash testing/run_test_suite.sh
# or this
bash testing/run_test_suite.sh --with-rest

fixed in #925


Investigate why builds on itch.io still show info! logs

Per Cargo.toml, we should only see logs for release builds that are at least warn, i.e. only warn and error.
[dependencies.log]
version = "*"
# Disable low-severity logs at compile time for performance.
features = ["max_level_debug", "release_max_level_warn"]

see the relevant documentation:

However, opening the console in https://the-bevy-flock.itch.io/bevy-quickstart shows that we receive info logs:

Relevant line in log crate source code: https://github.com/rust-lang/log/blob/d5ba2cfee9b3b4ca1fcad911b7f59dc79eeee022/src/lib.rs#L1528

Do we have debug_assertions enabled in release builds?

@benfrankel we do not. Try this snippet to confirm:
#[cfg(not(debug_assertions))]
compile_error!("We are running in release mode!");

Does the log dependency have debug_assertions enabled when our crate is in release mode? I highly doubt it but IDK how this is possible.

Per @mockersf:

you're setting the feature on the log crate, but I'm pretty sure Bevy doesn't use it as a backend on the web to be able to log on the console. you should set the log level features on the tracing crate instead


camera.flyToBoundingSphere should always use range when it's supplied

Fixes #2519
I also tweaked distanceToBoundingSphere2D because it was giving incorrect results on my machine.
@bagnell you'll probably want to double check the logic here, but I think the updated code does what was originally intended (always use a user-supplied range if it is given and non-zero).
We should try and get this into 1.7.

Labeled as a show stopper so we remember to look at it.  We can pass if it is too much work.


[Build] Exclude cuda etc. source files from RAF_CXX_SOURCE_FILES

Description
Including all .cc and then exclude cuda etc. source files from RAF_CXX_SOURCE_FILES.
Just make it easier for internal repository to add extra source file directory (e.g., src/amazon)
Checklist

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

cc @comaniac @awslabs/raf-reviewer

Thanks @comaniac


Header issue #1319 solved

this is how it looks after this PR

before

there were problems in the size of the components of header

Conflicting files
index.html
@vaibhavrajharsh  Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch.

Conflicting files
assets/css/style.css
index.html
@vaibhavrajharsh Please resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


update names and links after moving to a separate GitHub org

Codecov Report

Merging #203 (a110463) into master (69f92c2) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #203   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           18        18
  Lines          150       150
  Branches        22        22
=========================================
  Hits           150       150

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 69f92c2...a110463. Read the comment docs.


Flashing of unstyled HTML in extract-text-webpack-plugin, reconsider setting allChunks: true?

Although setting allChunks: false in the configuration of extract-text-webpack-plugin increases the initial page load, it has the consequence of flashing unstyled HTML as the user moves between uncached chunks, since the page renders before addStyles can do its magic. So far it's been the only customization I need and I'd love to not have to eject.
This was originally discussed in #408 but the unstyled flashing wasn't mentioned which I feel is a dealbreaker. If this isn't up for continued debate than you can just close it.

We currently don't have the time to look into this, but I'll tag it for later review. Thanks!

I didn't know this was a problem. Is this a known issue in webpack? Is it even possible to fix?
I'm okay with allChunks: true I guess.

Can you provide a project reproducing this?

It sounds like this has been reproduced and the consensus is to set allChunks: true. I’d love to see this fixed soon, would you accept a PR?

currently doing this via patch package. I feel this is an opinionated solve but not sure any practical alternatives exist? At the very least this is a big gotcha for code splitting with CRA

What's the status on this one? I'm experiencing this issue as well.

Hey guys, this should be fixed with the mini-css-extract-plugin which we've added as part of webpack 4 in the next branch.  I don't believe there will be any more releases for CRA 1.x.  Please test the CRA2 release if possible, and open a new issue if you see something wrong.


make JSON output compatible with jq (for action:get among others)

Is your feature request related to a problem? Please describe.
When you action:get, you get the action's name printed before the JSON API response.
> ./bin/run runtime:action:get foo
foo
 { ... }

This makes the output incompatible with jq to project some subset of the values of interest. Since aio here diverges from wsk's output of "ok: got action foo", perhaps do it better by dropping the action name that's currently prefixing the JSON response.
Describe the solution you'd like
> ./bin/run runtime:action:get foo
 {
  "annotations": [
    {
      "key": "exec",
      "value": "nodejs:10"
    }
  ],
  "exec": {
    "kind": "nodejs:10",
    "binary": false
  },
  "limits": {
    "concurrency": 1,
    "logs": 10,
    "memory": 256,
    "timeout": 60000
  },
  "name": "foo",
  "namespace": "guest",
  "parameters": [],
  "publish": false,
  "version": "0.0.1"
}

Describe alternatives you've considered
Wrap the cli with another bash script.

Hints for the hackathon:

The action:get code is this nested file: https://github.com/adobe/aio-cli-plugin-runtime/blob/master/src/commands/runtime/action/get.js#L74
The code that prints out that line is here: https://github.com/adobe/aio-cli-plugin-runtime/blob/2319ae92665bc42d8cb69fc1892c405915fa4af0/src/commands/runtime/action/get.js#L74


Sileo sources randomly dissapear.

i go to install a tweak and then randomly all my sources are gone except fir chimera. I add them all bacj and then later the day they dissapear again.
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.

This is a Sileo issue, not a jailbreak issue.


Added some instructions and modified some code

Some necessary changes are done rn.

Can you please add hacktober-accepted label and submit. Thankss!!

Hey @anuj-glitch you did a nice job with the project. Just merge this I added the instruction for the database in README.md

Hey @anuj-glitch you did a nice job with the project. Just merge this I added the instruction for the database in README.md


Instructions for manually cherry-picking are incorrect as they do not skip merge commits

Describe the bug
When the automatic backport fails due to conflicts in cherry-picking individual commits it will helpfully give instructions on how to manually do the cherry-pick:
git fetch origin branch/2.3.x
git worktree add -d .worktree/backport-574-to-branch/2.3.x origin/branch/2.3.x
cd .worktree/backport-574-to-branch/2.3.x
git checkout -b backport-574-to-branch/2.3.x
ancref=$(git merge-base 83b3365bbc12a9db248b67c22052413d41fae97e 9e9fb70b712a6799791997d3c70db6a28a71af72)
git cherry-pick -x $ancref..9e9fb70b712a6799791997d3c70db6a28a71af72

However, these instructions aren't correct if the PR contains merge commits as it omits the logic for filtering out merge commits.
To Reproduce
Steps to reproduce the behavior:

Create and merge a pull request with merge commits that also will have merge conflicts on the target branch
Trigger the backport workflow
Backport fails and comments instructions on manual cherry-picking

Expected behavior
The instructions should include how to filter out merge commits.
Workflow run logs
https://github.com/NVIDIA/cccl/actions/runs/6750303904/job/18352417643

Fixed in v2.1.1


python312Packages.aioairq: 0.4.2 -> 0.4.3

Diff: https://github.com/CorantGmbH/aioairq/compare/refs/tags/v0.4.2...v0.4.3

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 357778

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.airq
python311Packages.aioairq
python311Packages.aioairq.dist
python312Packages.aioairq
python312Packages.aioairq.dist


Edited the Web App Homepage

Initialize the conversion of the react vite template to the Figma prototype. Changed the background color and added description to the webpage

Everything looks good.


yamllint requires pathspec

While yamllint is available from conda-forge, one of its dependencies pathspec is not. Nor is it available in any recent form from any channel. I was able to pip install pathspec to avoid a traceback like this:
  File "/Users/downes/miniconda3/bin/yamllint", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/Users/downes/miniconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3098, in <module>
    @_call_aside
  File "/Users/downes/miniconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3082, in _call_aside
    f(*args, **kwargs)
  File "/Users/downes/miniconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3111, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/Users/downes/miniconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 573, in _build_master
    ws.require(__requires__)
  File "/Users/downes/miniconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 891, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/Users/downes/miniconda3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 777, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pathspec>=0.5.3' distribution was not found and is required by yamllint

At some point, I'd like to teach myself how to create a feedstock, but I'm creating this issue to record the issue. If you have an interest in taking it up, please do.

@tpdownes thanks for making this issue, saved me hunting about too much! Hopefully https://github.com/conda-forge/staged-recipes/pull/7775 can be merged in short order: it's definitely worth a hack at making a feedstock: starting from recipes/example/meta.yaml is pretty easy... especially for python packages!


AttributeError: 'NoneType' object has no attribute 'llama_batch_free'

This is my code

This is the error that occur when i try to execute the file.

I've noticed this as well. It seems to be an issue with how certain objects are garbage collected at system. I think it happens when llamacpp gets garbage collected before the actual model does -- does adding del model to the end of your file remove the error? (not a real fix, just a question whose answer may help debug this)

I think the underlying issue is this line in llama_cpp:
https://github.com/abetlen/llama-cpp-python/blob/08e910f7a7e3657cf210ab8633a6994e1bde7164/llama_cpp/llama_cpp.py#L121
Executed in:
https://github.com/abetlen/llama-cpp-python/blob/08e910f7a7e3657cf210ab8633a6994e1bde7164/llama_cpp/llama_cpp.py#L1684-L1687
Python gives no guarantees on process shutdown regarding the order that objects are destructed.  When it destructs objects, it changes any existing references to be 'None'.  So, if the lib object above happens to be destructed first, then the call to getattr will pass in None for the lib parameter.  The error message you get in a call to getattr(None, "llama_batch_free") matches the error observed in this issue: AttributeError: 'NoneType' object has no attribute 'llama_batch_free'.
I haven't verified this, but I will submit a PR to llama-cpp if it checks out.

@Fahmie23, what version do you get when you do:
import llama_cpp
print(llama_cpp.__version__)

I know I've seen an exception similar to what you reported on an older version of llama_cpp, but I'm not getting it to repo now on newer versions.  I would expect this error to occur fairly randomly though, so I can't be sure if that's because it's been fixed or if I'm just not happening to see it due to randomness.

I believe PR https://github.com/guidance-ai/guidance/pull/734 should resolve this issue, but I wasn't getting the error in the first place, so I can't confirm.  Closing this issue for now, but if anyone continues to see it in the next release, please re-open this issue.


Also check sockets bind to tcp6 and fail on all closed sockets

Also parse /proc/net/tcp6 because go will bind to it (too) on Listen()  if TCP v6 is enabled on the system, and then the socket will only show on /proc/net/tcp6. This fixes #821.

Fail on all kinds of closed sockets, even if they were closed correctly, before the query completion, thus ensuring that the query is cancelled.

Two explicit channel closings to ensure the goroutines exit ASAP.

@juanjux remember to sign de DCO

@erizocosmico yep, that's what happen when you commit code from VMs or other people machines without all your git/gpg config scaffolding :/

On linux system,if TCP v6 is  disabled on the system, open /proc/net/tcp6 will produce the error /proc/net/tcp6: No such file or directory.
How to slove this bug？
func tcpSocks(accept AcceptFn) ([]sockTabEntry, error) {
	paths := [2]string{pathTCP4Tab, pathTCP6Tab}
	var allTabs []sockTabEntry
	for _, p := range paths {
		f, err := os.Open(p)
		defer func() {
			_ = f.Close()
		}()
		if err != nil {
			return nil, err
		}

		t, err := parseSocktab(f, accept)
		if err != nil {
			return nil, err
		}
		allTabs = append(allTabs, t...)

	}
	extractProcInfo(allTabs)
	return allTabs, nil
}

On linux system,if TCP v6 is  disabled on the system, open /proc/net/tcp6 will produce the error /proc/net/tcp6: No such file or directory.
How to slove this bug？
func tcpSocks(accept AcceptFn) ([]sockTabEntry, error) {
	paths := [2]string{pathTCP4Tab, pathTCP6Tab}
	var allTabs []sockTabEntry
	for _, p := range paths {
		f, err := os.Open(p)
		defer func() {
			_ = f.Close()
		}()
		if err != nil {
			return nil, err
		}

		t, err := parseSocktab(f, accept)
		if err != nil {
			return nil, err
		}
		allTabs = append(allTabs, t...)

	}
	extractProcInfo(allTabs)
	return allTabs, nil
}

@TheWinds this project is no longer maintained, you can report this on it's new home: https://github.com/dolthub/go-mysql-server

@TheWinds this project is no longer maintained, you can report this on it's new home: https://github.com/dolthub/go-mysql-server


Graphite-Web compatibility map?

Hi @lomik I'm really surprised with this project , I would like to test it , but I need to know first if has been tested with both current graphite-web branches.

master (0.10.X) ?
0.9.x  ?

I need also test with my currently working whisper files, can go-carbon work with  already created files with original whisper python tools?

I am not the author, but AFAIK whisper format didn't change between graphite versions, therefore go-carbon should be fully compatible

I can confirm this works in my environment as I bake in graphite-web &
go-carbon in our internal docker image.
On Wed, Jun 22, 2016 at 10:54 AM, Maxim Ivanov<EMAIL_ADDRESS>wrote:

I am not the author, but AFAIK whisper format didn't change between
graphite versions, therefore go-carbon should be fully compatible
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lomik/go-carbon/issues/55#issuecomment-227789336, or mute
the thread
https://github.com/notifications/unsubscribe/ABJFZUAz3t7mOJ-I-R3n7Rebj5kx1h94ks5qOVq1gaJpZM4I7kN2
.

Fully compatible with all recent graphite-web versions.
Graphite older 0.9.10 (released 5/31/12) had another carbonlink protocol.


Annotate methods that do io work accordingly

@vRallev Is this open? Can I work on it?

Yes, I'd be happy about a PR. Start with JobManager and only annotate methods that involve a file operation. Thanks!

Closing this issue. It's recommended to use WorkManager instead of this library these days and I don't want to add any new features.


Remove imports from root __init__.py

#32 follow up PR to address https://github.com/leap-stc/leap-data-management-utils/pull/32#issuecomment-2097041379

Cc @jbusecke for visibility. this will likely break some of your workflows


Add app commands to list apps and read config

Get the type of the app in a given project/environment (if 1 app):
platform app:config -p p43m25zns6k2c -e master --property type


Run database migrations from distributed binary

Summary
Problem
Unless I'm mistaken, we currently need a clone of the repo / source to run the diesel migrations. It looks, though, like we're embedding the migrations in the binary - but I can't see any way to trigger them.
Impact
Need source to run migrations (can't just use the distributed binary).
Solution
I don't know enough about diesel, but it looks like automigrations are a possibility (should be the simplest, near term solution).

We already run migrations inside the binary for test purposes (because they're stood up on-the-fly), here:
https://github.com/fission-codes/fission-server/blob/53ffd0c1012e605341ed559c64c47b52d5ddfb69/fission-server/src/test_utils/ephermeral_db.rs#L22-L29
We need to make that code invokable from the binary CLI, too.
I'm pretty sure that actually embeds the migrations in the binary, given this:
https://github.com/fission-codes/fission-server/blob/53ffd0c1012e605341ed559c64c47b52d5ddfb69/fission-server/src/db/mod.rs#L9-L12
So I'm 90% sure that's an easy task.


Refactor to enable log context

Closes #317

Codecov Report

Merging #331 into master will increase coverage by 1.68%.
The diff coverage is 56.9%.

@@            Coverage Diff             @@
##           master     #331      +/-   ##
==========================================
+ Coverage   76.43%   78.12%   +1.68%
==========================================
  Files          22       24       +2
  Lines        1494     1504      +10
  Branches      257      255       -2
==========================================
+ Hits         1142     1175      +33
+ Misses        352      329      -23

Impacted Files
Coverage Δ

lib/renovate.js
0% <ø> (ø)
:arrow_up:

lib/helpers/changelog.js
100% <100%> (ø)
:arrow_up:

lib/workers/package-file.js
98.97% <100%> (ø)

lib/helpers/logger/index.js
100% <100%> (ø)

lib/helpers/npm.js
100% <100%> (ø)
:arrow_up:

lib/helpers/versions.js
100% <100%> (ø)
:arrow_up:

lib/config/file.js
100% <100%> (ø)
:arrow_up:

lib/helpers/package-json.js
100% <100%> (ø)
:arrow_up:

lib/helpers/logger/config-serializer.js
100% <100%> (ø)

lib/helpers/github-app.js
100% <100%> (ø)
:arrow_up:

... and 17 more

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 4ccc561...11da65b. Read the comment docs.


[ZEPPELIN-3545] save all tables to ResourcePool

What is this PR for?
Now if paragraph's output contains more than one table in ResourcePool saves only last table.
It would be desirable that in ResoursePool stores all tables.
What type of PR is it?
Improvement
What is the Jira issue?
ZEPPELIN-3545
Screenshots

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

Thanks @Savalek for this contribution, but I think putting all tables into ResourcePool doesn't make sense. As it would occupy lots of memory. I plan to introduce paragraph level properties (ZEPPELIN-3348), so that user can control whether to put the interpreter result into ResourcePool.

@zjffdu thank you about ResourcePool impoving.
Share please your vision how it would be. For example, a paragraph has 5 table results. How user will define which of them would be added into ResourcePool?

@zjffdu
I support adding only selected table results to Resource Pool.
As paragraph can have multiple results than I propose to add result level properties.

@mebelousov There're many options for how to specify which result to be stored into resource pool.
e.g.
%spark(saveToResourcePool=1,2,4)

Or
%spark(1.saveToResourcePool=true, 2.saveToResourcePool=true, 4.saveToResourcePool=true)

We can discuss more about which is the best approach, the key point here is to allow user to customize it via paragraph levle properties.


Use setuptools_scm for version and remove VERSION file.

Please make a tag before merging in otherwise the package version will be something like 0.0. There are commits that updated the VERSION file so I think they are good ones to tag. Just the latest tag will be enough to build the latest package with correct version. Thanks.

Would you mind resolving the conflict that was created by d1bb024 and updating the PR?


Keep track of how many downloads each Pub package gets

Although the packages themselves are served from cloud storage, we can still count the number of times we redirect.

This issue has been moved to dart-lang/pub#194.


Blurry Icons via Base64

I'm currently using base64 encoded PNGs. My icons in the customizable commands look very blurry compared to the rest of the commands. I was wondering if anything could be used to solve this issue since the constraint is set to 16x16px for the "iconImageUrl" property.
If not, is there a way to use the Office UI Fabric Icons directly without any sacrifice in quality?

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

ID: 38ba7b1f-b77a-0076-ed6c-dd84bbc104ea
Version Independent ID: d7cc472b-1c5b-fd7b-f7dc-6add54dd0886
Content: Configure extension icon in SharePoint Framework (SPFx) Extensions
Content Source: docs/spfx/extensions/basics/configure-extension-icon.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Solved the issue by using SVG base-64 encoded images.


sample rate module missing?

Describe the bug
sample rate error with anaconda?
To Reproduce
Steps to reproduce the behavior:

Selected settings: 'normal settings, HPE kareokee'
See error

Expected behavior
get two audio files
Screenshots

Desktop (please complete the following information):

OS: [windows 11]

update: reinstalling pytorch and the other dependencies seemingly fixed this issue, maybe i had an outdated version installed.
FIXED!


[BUG] when trying for the first time

Error when trying the get started code.
2023-12-19 08:02:29,059 INFO Your selenium-driver-updater library is up to date.
2023-12-19 08:02:32,419 INFO Current version of chromedriver: 120.0.6099.109
2023-12-19 08:02:33,762 INFO Latest version of chromedriver: 120.0.6099.109
2023-12-19 08:02:33,762 INFO Your existing chromedriver is up to date. current_version: 120.0.6099.109 latest_version: 120.0.6099.109
Traceback (most recent call last):
File "C:\Users\Engineer\AppData\Local\Programs\Python\Python312\Lib\site-packages\selenium\webdriver\common\driver_finder.py", line 38, in get_path
path = SeleniumManager().driver_location(options) if path is None else path
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Engineer\AppData\Local\Programs\Python\Python312\Lib\site-packages\selenium\webdriver\common\selenium_manager.py", line 84, in driver_location
browser = options.capabilities["browserName"]
^^^^^^^^^^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'capabilities'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\Engineer\register-chrome-driver-path.py", line 9, in
driver = webdriver.Chrome(filename)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Engineer\AppData\Local\Programs\Python\Python312\Lib\site-packages\selenium\webdriver\chrome\webdriver.py", line 45, in init
super().init(
File "C:\Users\Engineer\AppData\Local\Programs\Python\Python312\Lib\site-packages\selenium\webdriver\chromium\webdriver.py", line 49, in init
self.service.path = DriverFinder.get_path(self.service, options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Engineer\AppData\Local\Programs\Python\Python312\Lib\site-packages\selenium\webdriver\common\driver_finder.py", line 40, in get_path
msg = f"Unable to obtain driver for {options.capabilities['browserName']} using Selenium Manager."
^^^^^^^^^^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'capabilities'

OS: Windows10
Driver chromedriver

Hello, thanks for the issue, but it seems that this error is in SeleniumManager, not in selenium_driver_updater


add failing tests for #393

I've attempted to create a test that would pass if the desired behavior in #393 is implemented.

i'll build the autocast against this test, thx a lot.

This is now merged, thanks!


Please add simple use case on README.md

Hi, found this from a search. Please add the 4 line usage. I expect something like this:
LOCK_FILE = ...
LOCK = InterprocessLock(LOCK_FILE)

def foo():
    with LOCK:
        do_something()

Thanks

It's already available within the official documentation linked from the reaadme https://py-filelock.readthedocs.io/en/latest/index.html#filelock

Why not just copy and paste this snippet
from filelock import Timeout, FileLock

lock = FileLock("high_ground.txt.lock")
with lock:
    with open("high_ground.txt", "a") as f:
        f.write("You were the chosen one.")

Into the readme? The documentation link is great, but I can't find a link to it from the github/docs. This little snippet would answer the question that every single new user has when they visit the product: "how does this work?"

Because we don't want to duplicate information, and the README is not documentation. The Readme has a direct link to the actual documentation. Users should only consult the documentation to find the answer, and is accessible from the readme via the link to it.

The readme is special, because it is pushed all the way to the pypi page where people are browsing for solutions like what you have.

I think we'll need to agree to disagree on this.

I did update the documentation link in the readme to point from the API page to the index page - https://github.com/tox-dev/py-filelock/commit/4730a40b87cc4b094330b2af7723658428323d60

Ah i see. Thanks


Leaderboard Layout

Without too much concern for the functionality of the components go ahead and stub out the layout as best you can.
Create a component that someone can fill in with the leaderboard list and duplicate packages/nextjs/components/impact-vector/ImpactVectorGraph.tsx to a new location and import that component as a stand in for the graph.
https://www.figma.com/design/SuY5W6zRajPNOrmeCSTvAq/Onchain-Impact-Dashboard?node-id=28-36453&t=A6kTe3hIhRieL0JU-4

I'll work on this

@blahkheart what is the status of this? I can take care if you don't have time

@Franpastoragusti I'm actually rounding up with it.. I've just been facing a weird blocker but I'm actively working on it


Adding Minecraft PC Launcher

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

Minecraft was previously removed because the devs don't plan on releasing version URLs and they don't think the Minecraft Launcher should be a package in WinGet.
https://github.com/microsoft/winget-pkgs/pull/1544


Can't login

When trying to login, it opens google gemini in browser instead.

@muznyo Hello, good morning (afternoon or night), I realized this yesterday when I entered the website, the problem comes from the bard google website, which is now called gemini google, the login button started to work differently, now the website opens another tab. For that, I am looking at how to solve it, although this project is based on another, the other one has no problems because it uses chatgpt, and Google's is the one that works differently on the web. I'll see what I can do, thanks for letting me know.

@muznyo I already updated the package and it solved the problem, if you have another problem using this plasmoid, please let me know.

Now i can login, only problem is light scrollbars when using dark mode, but its probably google's issue?

@muznyo You are correct, it is a web problem.


Small change to allow easy support of multiple providers

This is a small change that allows configuring multiple oauth providers and serving them from the same location.
here is a sample
# initialize common oauth configuration
set $oauth_config_prefix '';
set $oauth_redirect_uri '_/oauth/callback';
set $oauth_success_uri '/';

# # google oauth configuration
set $google_redirect_uri "${oauth_redirect_uri}?provider=google";
set $google_success_uri "${oauth_success_uri}";
set $google_client_id '...';
set $google_client_secret '...';
set $google_authorization_url '...';
set $google_token_url '...';
set $google_userinfo_url '...';
set $google_scope '...';

# github oauth configuration
set $github_redirect_uri "${oauth_redirect_uri}?provider=github";
set $github_success_uri "${oauth_success_uri}";
set $github_client_id '...';
set $github_client_secret '...';
set $github_authorization_url '...';
set $github_token_url '...';
set $github_userinfo_url '...';
set $github_scope '...';

location /_oauth/login {
    set $oauth_config_prefix "${arg_provider}_";
    content_by_lua_file '../luajit/share/lua/5.1/ngx-oauth-login.lua';
}

PS: if you decide to merge this, please "squash" the commits for a cleaner history.
Thank you

just noticed the config is loaded only on the first request, then it's being cached (looking into it)

just noticed the config is loaded only on the first request, then it's being cached (looking into it)


Benchmarking script changes for Sean

Submisison Checklist

[x] Run tests: ./runCmdStanTests.py src/test
[x] Declare copyright holder and open-source license: see below

Summary:
Some edits to scripts to make benchmarking easier, written with @seantalts
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Thanks again!


Idea suggestion : Load in Prepare Carefully made characters for drop in multiplayer.

I think it would be a nice suggestion to have it so that people can load in already made characters from prepare carefully so that a drop-in multiplayer person could quickly load a custom colonist in instead of having to pre-plan out ahead of time what somebody would like.
It would be, I think, a nice touch for people who want to join in on a colony without having to share or deal with completely random starting colonists. I know part of the point of the game is that you have to deal with the RNG and it even makes it more fun, but if you want that personal touch like I do with starter people I think the ability to simply load in characters saved via prepare carefully would be pretty nice.
It shouldn't be overly hard to implement, but I wouldn't know exactly.

what if restricted on the point system,
does the extra colonist replace one of the previous or add in another one?
what colony does it go to?
how do we make sure that people cant grief using this system?
implement a possible approval system for the host to do to add in a new colonist
what happens to that colonist when that player leaves?

This would probably mean looking through the joining users PrepareCarefully colonists, and importing them into the hosts game. It could be potentially griefable by making mentally unstable colonists and bringing them in, so maybe a GUI for the host with a basic overview of their stats could be used. In the meantime, if both players are using Prepare Carefully before they start a multiplayer game, couldn't the other players just send the host their presets for colonists?

@SweptWasTaken I think the point is that a player that hot joins needs to be able to provide their own colonist. When the host starts a game, they don't know who will join, so they cannot take colonists requests from people.


Fix analyze issues in gRPC ObjC lib

Fixes analyze issues in Objective-C layer.
Partial fix of #16451.

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,961,111      Total (>)      1,961,099

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,883,610      Total (<)     10,883,615

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,961,111      Total (>)      1,961,099

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,883,610      Total (>)     10,883,609

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,965,565      Total (>)      1,965,327

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,888,291      Total (>)     10,888,230

 No significant differences in binary sizes


Commands

[ ] !help

Print all commands available to user

Filter printed list based on role(members, mods, and me)

Aliases:
Usage:
Cooldown:
guildOnly:

[ ] !prune

Remove last X messages (mod only)
Aliases:
Usage:
Cooldown:
guildOnly:

[ ] !server

Display server info (mod only)

Member count
Name

Aliases:
Usage:
Cooldown:
guildOnly:

[ ] !leaderboard

List of users and their current ranking
Aliases:
Usage:
Cooldown:
guildOnly:

[ ] !schedule

Display my Twitch stream schedule
Aliases:
Usage:
Cooldown:
guildOnly:

[ ] !whois

Get user info (mod only)
Aliases:
Usage:
Cooldown:
guildOnly:

[ ] !emotes

Gets a list of server emotes
Aliases:
Usage:
Cooldown:
guildOnly:

Separated each command into its own task under the Commands Epic


Adds support for running background processes on the same version of …

When you have multiple versions installed PHP on the server, it may happen that the default version of PHP is different with which you are running Jobby.
In my case for example, the installed default server PHP version is 4.4 and I run Jobby with 5.5, but when you run the BackgroundJob these are executed with the default verion and not the version that is currently running Jobby.
This change fixes the problem.

Interesting! Thanks, should be in next release.


No login screen, immediately logged in as anonymous

To repoduce:

Start dev server
Open localhost:3000

ER:

Login screen is displayed.
After logging in entity messages are requested from server.

AR:

Immediately logged in as anonymous:

After logging out and logging in as a valid user, entity messages are not requested. Page reload will trigger requesting the entity messages.

Fixed in graphql


Highlight that routes.json should contain an array

We've just got a bit foxed trying to enable authentication because we'd just put one route property on the object in the routes.json file, which validated OK in the build pipeline but didn't have an effect because, of course, as shown in the example routes.json file, there should be a routes property, which is an array of route objects.
I think this means that the documentation is not very clear, as it immediately jumps into talking about route objects rather than first showing the general structure of the routes.json file?

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

ID: ac225b59-6d75-1c98-3bd5-9483a818c8d4
Version Independent ID: 40e9a5f6-4461-b926-427b-ee889b2c3754
Content: Routes in Azure Static Web Apps
Content Source: articles/static-web-apps/routes.md
Service: static-web-apps
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@ellispritchard Thanks for the feedback! We are taking a look into this and will get back to you soon.

@ellispritchard Thanks again for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate.

You make a good point about emphasizing the routes array. The routes.json file is deprecated, but I have made these changes to the configuration article in the routes section. (Note: I just pushed the change, so it may take a few hours to go live)
#please-close


Missing libwallet-crypto.a

Hi there,
I am struggling to build the library on my Apple M1 (I managed to build on Linux, Apple Intel, and using buildx of docker). I had to make some tweaks to build monero statically (tip from https://github.com/monero-project/monero/issues/8332) but, I can't find why the library libwallet-crypto.a wasn't built by monero.
Tried to upload the monero compilation logs somewhere but it was too big. Let me know if you need an specific part of it.
monero-cpp compilation:
-- The C compiler identification is Clang 14.0.6
-- The CXX compiler identification is Clang 14.0.6
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /opt/homebrew/opt/llvm/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /opt/homebrew/opt/llvm/bin/clang - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- EXTERNAL_LIBS_DIR:/Users/aquila.freitas/Projects/Personal/Monero/monero-cpp/external-libs
-- EXTRA_LIBRARIES:/Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/System/Library/Frameworks/IOKit.framework/Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/System/Library/Frameworks/CoreFoundation.framework/Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/System/Library/Frameworks/AppKit.framework
-- Found Protobuf: /opt/homebrew/lib/libprotobuf.dylib (found version "3.21.2")
-- Protobuf lib: /opt/homebrew/lib/libprotobuf.dylib, inc: /opt/homebrew/include, protoc: /opt/homebrew/bin/protoc
-- Using Boost include dir at /opt/homebrew/include
-- Using OpenSSL found at /opt/homebrew/opt/openssl@3
-- Found OpenSSL<EMAIL_ADDRESS>(found version "3.0.5")
-- Using OpenSSL include dir at /opt/homebrew/opt/openssl@3/include
-- Using libsodium library at /opt/homebrew/lib/libsodium.dylib
-- Found HIDAPI: /opt/homebrew/lib/libhidapi.dylib
-- Using HIDAPI include dir at /opt/homebrew/include/hidapi
-- Using monero-project build:/Users/aquila.freitas/Projects/Personal/Monero/monero-cpp/external/monero-project/build/release
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/aquila.freitas/Projects/Personal/Monero/monero-cpp/build
[ 12%] Building CXX object CMakeFiles/monero-cpp.dir/src/utils/gen_utils.cpp.o
[ 25%] Building CXX object CMakeFiles/monero-cpp.dir/src/utils/monero_utils.cpp.o
[ 37%] Building CXX object CMakeFiles/monero-cpp.dir/src/daemon/monero_daemon_model.cpp.o
[ 50%] Building CXX object CMakeFiles/monero-cpp.dir/src/daemon/monero_daemon.cpp.o
[ 62%] Building CXX object CMakeFiles/monero-cpp.dir/src/wallet/monero_wallet_model.cpp.o
[ 75%] Building CXX object CMakeFiles/monero-cpp.dir/src/wallet/monero_wallet_keys.cpp.o
[ 87%] Building CXX object CMakeFiles/monero-cpp.dir/src/wallet/monero_wallet_full.cpp.o
In file included from /Users/aquila.freitas/Projects/Personal/Monero/monero-cpp/src/wallet/monero_wallet_full.cpp:60:
/Users/aquila.freitas/Projects/Personal/Monero/monero-cpp/external/monero-project/src/wallet/wallet_rpc_server_commands_defs.h:51:9: warning: 'WALLET_RPC_VERSION_MINOR' macro redefined [-Wmacro-redefined]
#define WALLET_RPC_VERSION_MINOR 24
        ^
/Users/aquila.freitas/Projects/Personal/Monero/monero-cpp/external/monero-project/src/wallet/wallet_rpc_server_commands_defs.h:50:9: note: previous definition is here
#define WALLET_RPC_VERSION_MINOR 22
        ^
1 warning generated.
gmake[2]: *** No rule to make target '../external/monero-project/build/release/src/crypto/wallet/libwallet-crypto.a', needed by 'libmonero-cpp.dylib'.  Stop.
gmake[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/monero-cpp.dir/all] Error 2
gmake: *** [Makefile:91: all] Error 2

libwallet-crypto.a is built as part of monero-project, which is built separately from this project, so that's the first step to solve.
monero-project is included as an external project in monero-cpp.
You should be able to manually cd $MONERO_CPP/external/monero-project && make release-static -j8 && make release-static -j8 and confirm that the build completes. If there are any build errors, then the *.a files won't be created, so we just need to work through the build errors until that finishes.
After that, the file should be built at ../external/monero-project/build/release/src/crypto/wallet/libwallet-crypto.a, and this library can be built.

Also, libwallet-crypto.a is only built on *nix systems, not Windows.

You should be able to manually cd $MONERO_CPP/external/monero-project && make release-static -j8 && make release-static -j8 and confirm that the build completes.

I can confirm the build completes successfully. Only libwallet-crypto.a missing.

Also, libwallet-crypto.a is only built on *nix systems, not Windows.

I am on a Mac. I did test on an Intel based Mac and the lib exists there. Could libwallet-crypto.a also not be built on M1? I do get the CMake files:

Could libwallet-crypto.a also not be built on M1?

I couldn't tell you. It's good to know it worked on Intel as a baseline. Sounds like something needs updated for the new hardware.

A new version of this library is released, v0.7.2, which updates the dependencies for monero-project v<IP_ADDRESS> (for example, libwallet_merged.a had been completely removed). Please let me know if you continue to have problems with this new version. Thanks.

I am still missing the libwallet-crypto.a on v<IP_ADDRESS>. I will ask someone on monero-project about this. Quick question, as libwallet_merged.a have been removed, do we still need to double make release-static?

I found out that libwallet-crypto.a is only built on x86_64 systems to provide asm for some wallet functions.
https://github.com/monero-ecosystem/monero-cpp/pull/18 imports that library only if it exists, and should hopefully resolve this issue.
No need to make release-static twice anymore. Good catch, I'll update the docs. :)

Just tested fix_libwallet_crypto and that did go through, thanks!
I just got stuck with some epee dependencies now: build.txt
Have you seen these errors before?

Looks like it can't find SSL libs.
Running ./bin/build_libmonero_cpp.sh ought to locate your environment's SSL package and print output like Using OpenSSL at /usr/local/opt/openssl@3. Does it? I don't see anything about it in your build log, but it looks like you used a modified command.

Good point, I did make some modifications and forgot to revert. Just to let you know, it's possible to compile monero-cpp on M1 by replacing -march=x86-64 with -mcpu=native. Monero Project needs this change to build statically on M1 though.
Feel free close the issue one #18 goes through. Appreciate your help and congrats for the good work.

Looks like it can't find SSL libs.
Running ./bin/build_libmonero_cpp.sh ought to locate your environment's SSL package and print output like Using OpenSSL at /usr/local/opt/openssl@3. Does it? I don't see anything about it in your build log, but it looks like you used a modified command.
Somehow we need to modify SSL import in CMakeLists.txt to import your system's SSL.

Install brew install<EMAIL_ADDRESS>uninstall openssl@3

I also had success by modifying EXECUTE_PROCESS(COMMAND brew --prefix openssl to EXECUTE_PROCESS(COMMAND brew --prefix<EMAIL_ADDRESS>

Fixed with https://github.com/monero-ecosystem/monero-cpp/commit/7d6e456cc4d266df8348db5b9d4b76924eebac4e.


Update to v0.14.1 and rerender

Minor bugfix to allow pyplot.savefig with bbox_inches='tight'.

Hi! This is the friendly conda-forge-admin automated user.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Phew! You're too fast @ocefpaf!

Phew! You're too fast @ocefpaf!

Saving you from doing boring bolirplate stuff. (The more free time you get the more Cartopy/Iris I get :wink:)


Possible false positive for CORE-000213 (CG0536)

When working on a study for a customer, and using CORE (v.0.6.3) I got violations for CORE-000213 (CG0536) which I think are false positives, as the values for "EPOCH" are different.
Can someone have a look?
Screenshots attached.

With test data 02 this gives a positive result