Iot edge devices runtime status showing error

After deploying the simulation script successfully, I have found the IoT Edge devices/modules not going to running status.
Could you please clarify whether how to solve this or is there anything I have missed any steps?

Hi @sg33452, the root cert has expired and I m working on updating them. Because of that the installation of IoT Edge runtime fails. Stay tuned for an update!

Certs are now fixed. So you can redeploy and issue should go away.


2049bbs twitter 挂了

My God!!!
On Mon, Jun 3, 2019, 22:16 TerminusBot<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Terminus2049/Terminus2049.github.io/issues/413?email_source=notifications&email_token=AC2QRP7MJGBYPXUW3ZLRNC3PYURVVA5CNFSM4HSIQLJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GXJPSFA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC2QRPYVCTWOJ243RLHYSS3PYURVVANCNFSM4HSIQLJA
.

@daidai 准确说是ifttt to twitter 挂了……


Updating the GHPages release process

PR Summary
Part 1 of the work in #215 to refactor the release process.
This work;

splits the GHPages publish workflow to 2 workflow files that are separately triggered.
removes the compiled ARM json from the repo
stops storing the ARM json in the repo as part of the BicepBuild action

The next PR will focus on the release element, which unfortunately is hard to test until we create the workflow stub for that workflow action in main.

PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] This PR is ready to merge and is not Work in Progress
[x] Link to a filed issue

/release 0.5.10


Mas12517/stream layer

Sample
Stream Layer Sample
Summary
Stream Layer sample for Unreal Engine (not including UI)
To be merged into feature branch and then work on UI to begin after
Tests
Windows
ArcGIS Maps SDK Version
UE 5.0 w/ Maps SDK 1.3

Not seeing any airplanes show up when running the sample. Am I missing a step for seeing data come in from the stream layer?

Yeah I just checked and it's down again. I'm not sure what to do at this point. It is never going to get merged at this rate.

I do see a number of planes get spawned in the Outliner window, and I checked most of these planes and they seem to be updating their positions in terms of Long and Lat. I assume more work w/ the camera and UI will be next once this is merged into the feature branch?

Yes, moving the camera behind the plane will come with the UI.

A few suggestions (some of which can be combined with future UI work)

Add Esri copyright to all .cpp and .h
Build lighting in the scene
Rotate the planes to align with travel direction
(optional) move the planes smoothly between points instead of jumps
Once UI is working, remove the OnScreenDebugMessage and show a message or icon in the UI


Grid options as background

When working with with opacity and blur settings on components it can be difficult to judge if they are working correctly.  Allowing the grid to be set to a vivid pattern can help check this

Also option for an inverted grid could help identify the boundaries of components - possibly lead to testing components when browser in dark-mode


Make Void an alias for !

Since rust-lang/rust#35162 was merged, ! is now a first-class type (albeit only in Nightly). For compatibility it would be nice if Void is redefined to be an alias for !.

Before stabilisation, it can be a Cargo feature.


[Proposal] Splitting the Infra installation from the Stack

Problem.
Currently, Infra components are installed together in the Stack, which can cause problems with #204. We plan to split the installation of Infra components from the current Stack; the Infra installation process is responsible for installing Infra components and the Stack only generates the application framework source code and Deploy repository.
Option 1.
Split the Stack into an Infra Stack and an Application Stack, with the Infra Stack being used exclusively for installing Infra components and making the necessary configurations to dynamically install the necessary Infra components based on the incoming parameters. When executing hln up, the Installation Infra Stack is executed first, followed by the Application Stack (e.g. gin-next), and we first support these Infra components:

Split Stack(include Argocd) to Infra Stack and an Application Stack @vgjm

Infra Stack can run independently, install them by input some env, and record configmap into cluster for Application Stack use it.

update Infra Stack(Prometheus) and enhance  Application Stack make them can multiplexing between different applications in the same cluster  @92hackers
update Infra Stack(Loki) and enhance  Application Stack make them can multiplexing between different applications in the same cluster @92hackers
update Infra Stack(Dapr) and enhance  Application Stack make them can multiplexing between different applications in the same cluster @92hackers
update Infra Stack(Nocalhost) and enhance  Application Stack make them can multiplexing between different applications in the same cluster @yuyicai
update Infra Stack(Argocd) and enhance  Application Stack make them can multiplexing between different applications in the same cluster @yuyicai
update Infra Stack(SealedSecrets) and enhance  Application Stack make them can multiplexing between different applications in the same cluster @yuyicai
update Infra Stack(Jeager) and enhance  Application Stack make them can multiplexing between different applications in the same cluster @lyzhang1999
update Infra Stack(Istio) and enhance  Application Stack make them can multiplexing between different applications in the same cluster @lyzhang1999
hln init && up && down && hln status...... @hongchaodeng

Results.
When hln up is executed, if the Infra component is not installed, it is installed automatically. If it is installed, it is skipped and execute the Application Stack installation.
When a new application is created in the same cluster, the Infra component will remain intact and only application related content will be created, solving the problem of #204.
hln
Enhance hln init command, install infra first, then hln up will run application stack.

infra stack and application stack.md


Restructure top level folders

TODO:

[x] READMEs for every top level folder
[ ] fix tests that test top level scripts (@dakinggg I could use your help)
[x] fix any documentation and MCLI yamls whose paths have changed
[x] look into if there is a cleaner presentation than having assets, tests/, bunch of other files at toplevel (@alextrott16)
[ ] ~figure out what to do about data/finetuning/tasks.py~

For best viewing experience, I recommend looking at the branch in Github UI: https://github.com/mosaicml/llm-foundry/tree/abhi/restruct

Moved scripts to a scripts/ folder. Fixed a lot of references but probably not all of them. Will leave to tomorrow's bug bash (and relevant owners) to fix READMEs for each subfolder

Merged as it's getting late, and the pytest-cpu tests are all passing, just something wrong with tests/conftest.py


Responsive Aspect Ratio Adjustment

Problem:
Currently, the page does not adapt its aspect ratio when opened on devices with different screen aspect ratios. This can lead to a suboptimal user experience, with content appearing distorted or not fully utilizing the available screen space.
Proposed Solution:
Implement a responsive design that adjusts the aspect ratio of the page based on the screen dimensions of the device. This will ensure that the content is displayed in an optimal and visually pleasing manner, regardless of the device's aspect ratio.
Steps to Reproduce:
Open the page on a device with a different aspect ratio.
Observe any distortion or suboptimal use of screen space.
Expected Behavior:
The page should dynamically adapt its aspect ratio to suit the screen dimensions of the device, maintaining an aesthetically pleasing and user-friendly layout.
Additional Information:
Consideration for common aspect ratios across devices.
Any specific design or layout preferences.
Potential impact on performance or existing functionality.
Screenshots/Attachments:
Include screenshots or additional information to illustrate the issue and demonstrate the expected behavior.
Environment:
Browser: [e.g., Chrome, Firefox]
Operating System: [e.g., Windows, macOS]
Device: [e.g., Desktop, Laptop, Tablet, Mobile]
Feel free to share your insights and suggestions on how best to achieve responsive aspect ratio adjustment. Collaboration on this issue is encouraged! 🌐📱

As a KWOC Contributor, I  would want to work on this issue.

As a KWOC Contributor, I would want to work on this issue. i think i can solve it

The Issue has been Assigned >_<

As a KWOC Contributor, I would like to hear the progress on this issue.
If it has not been fixed, please assign it to me.

As a KWOC Contributor, I would want to work on this issue. i can solve it

Hey @Aarsh30 for what screen size are you adjusting ratio? I am styling for max:768px, it will be collaborative if you can contribute tablet size screens.

Hey @KrishGaur1354 I an unable to contribute on this. Kindly unassign

Hey @KrishGaur1354 I an unable to contribute on this. Kindly unassign


Imported Repo topics are sometimes undefined (in TypeScript)

Hello!

Vote on this issue by adding a 👍 reaction
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details
When importing repos using a resources json doc, we're finding that the list of topics on the (Typescript) generated repo does not always match the actual topics on GitHub. For example, the [cucumber/cucumber-js] repo has three topics (javascript, typescript and cucumber) but the imported TypeScript representation in this commit shows
    topics: [
        undefined,
        "javascript",
        "cucumber",
    ],

This is non-deterministic. Sometimes, the list of topics is correct, and sometimes it contains these undefined values. We can't figure out a reason why it happens.
Steps to reproduce
pulumi import github:index/repository:Repository cucumber/cucumber-js cucumber-js --yes --out foo.ts
cat foo.ts

Sometimes one of the topics is undefined. Right now, my colleague (running the command in France, where is the afternoon, on Linux) is experiencing it, and I (running the command in Canada, where it is the morning, on an M1 Mac) am not experiencing it. I have, however, seen it before on this machine, just not right now. 🤯
Expected:
import * as pulumi from "@pulumi/pulumi";
import * as github from "@pulumi/github";

const cucumber_cucumber_js = new github.Repository("cucumber/cucumber-js", {
    allowAutoMerge: false,
    allowMergeCommit: false,
    allowRebaseMerge: false,
    allowSquashMerge: true,
    archived: false,
    deleteBranchOnMerge: true,
    description: "Cucumber for JavaScript",
    hasDownloads: true,
    hasIssues: true,
    hasProjects: true,
    homepageUrl: "https://cucumber.io",
    name: "cucumber-js",
    pages: {
        source: {
            branch: "gh-pages",
        },
    },
    topics: [
        "javascript",
        "typescript",
        "cucumber",
    ],
    vulnerabilityAlerts: true,
}, {
    protect: true,
});

Actual:
import * as pulumi from "@pulumi/pulumi";
import * as github from "@pulumi/github";

const cucumber_cucumber_js = new github.Repository("cucumber/cucumber-js", {
    allowAutoMerge: false,
    allowMergeCommit: false,
    allowRebaseMerge: false,
    allowSquashMerge: true,
    archived: false,
    deleteBranchOnMerge: true,
    description: "Cucumber for JavaScript",
    hasDownloads: true,
    hasIssues: true,
    hasProjects: true,
    homepageUrl: "https://cucumber.io",
    name: "cucumber-js",
    pages: {
        source: {
            branch: "gh-pages",
        },
    },
    topics: [
        undefined,
        "typescript",
        "cucumber",
    ],
    vulnerabilityAlerts: true,
}, {
    protect: true,
});

Any thoughts on what is causing this? We're only at a proof-of-concept stage with adopting Pulumi at the moment and honestly it's causing some of us to question whether we can rely on this tool.
If there are any pointers where we could look to help troubleshoot or fix this, we'd be happy to help.

Unfortunately, it looks like this issue hasn't seen any updates in a while. If you're still encountering this problem, could you leave a quick comment to let us know so we can prioritize it?


Text for Payment Means (BT-82) is bugged?

Hi @josemmo!
it seems setMeansText is generating a wrong xml node:
$payment = new Payment();
$payment->setMeansCode(31);
$payment->setMeansText("Payment Text");

this generates the following xml:
<cac:PaymentMeans>
    <cbc:PaymentMeansCode name="Payment Text">31</cbc:PaymentMeansCode>
</cac:PaymentMeans>

instead of:
<cac:PaymentMeans>
    <cbc:PaymentMeansCode>31</cbc:PaymentMeansCode>
    <cbc:InstructionNote>Payment Text</cbc:InstructionNote>
</cac:PaymentMeans>

BT-82 is the InstructionNote, in regards to the documentations.

Hi, @andras-minicrm!
According to the Peppol BIS specification, that's how BT-81 (payment means type code) and BT-82 (payment means text) should be encoded.
Is this different for another CIUS/extension?

Hi @josemmo!
Probably you are right! I'm working from a document which is based on UBL 2.1.
Based on this validator https://ecosio.com/en/peppol-and-xml-document-validator/

UBL Invoice 2.1 ruleset both of versions are valid.
(eg) 16931 option choosed it shows warnings.

I think I've worked from a wrong document.

Yes, EN16931 is the European electronic invoicing specification (which is what this library implements).
UBL was chosen as a language for representing EN16931 invoices in XML, but not all UBL documents are EN16931-compliant.
In this you have more information: https://josemmo.github.io/einvoicing/getting-started/eu-einvoicing-concepts/


swiper-pagination-bullets

Not an issue, just a question
I used swiper inside the wrapper of component and I am trying to set swiper-pagination-bullets outside the swiper-wraper but inside the component wraper.  Also, I am trying to change the color of swiper-pagination-bullets

Here is an example: https://stackblitz.com/edit/github-swiper-custom-pagination


Added My Data

Good job @abhishekrd
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in ClueLess Website .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


artifacts on certain apple devices when using premultiply = true

Hi! In order to get the best image quality on my StageGL I activate the 'antialias' flag for images smoothening and 'premultiply' flag to avoid weird colors arround edges.
This works fine on windows/android, but on certain iPhones/Macbook, some weird artifacts appear in areas with alpha set to 0 (they are shown as black):

I also tried playing with 'transparent' and 'preserveBuffer' flags. With no changes.
I'm not sure if this is actually a bug of certain apple devices. As it seemed to work nice on other apple devices.
Devices with problems:
iPhone 6s
iOS 10.3.2  (latest)
AppleWebkit: 603.2.4
MacBook:
Safari 9.1.1
MacOS 10.11.15 (Capitán)
Webkit 601.6.17
Devices that worked OK
Mac Mini
Safari 10.1
MacOS 10.12.4

I've seen this before and I added a flag to the main shader to account for it, odd that it's showing up for you. Should be an easy fix once I track down what's causing it to occur.
I'll look into this and see if there's something I can do. Do you have a minimum replication scenario I could play about with? Are you doing anything like caching, specifying an opaque clear color, applying filters?

Hi!
find attached a minimum project that replicate the errror. It is basically a text with a transparent background that shows the frames per second.
The code is in "production\sample\sample.js". It looks a bit weird because it is transpiled from another language, but is small enough to understand (about 30 lines of code :-) )
The background is shown black on an IPhone6S
I just tried also on an IPhone6 (not S) and also looks fine. It seems that something device specific. Weird
SampleThatFails.zip

Latest NEXT build should have this fixed. Turns out GLSL division by 0 is an undefined behavior and some browser/hardware combos handle it differently. I added a check to bypass that problem. Should be good to go.

Closing for now. Feel free to reopen if problem persists. Thanks for the report!!


Mechanism To Print Warning From Non-Path Dependency

Problem
By default Rust targets a very portable / conservative x86 target. For most use-cases this isn't all that critical, but in the arrow project we provide vectorised compute kernels, for which correct vectorisation has significant orders-of-magnitude performance implications.
We would like to be able to provide some hint to users that they should consider compiling with a more specific target-cpu - see https://github.com/apache/arrow-rs/issues/3485.
Currently all warnings from non-path dependencies are assumed to be the responsibility of that crate, and not relevant to the end-user, unless that crate fails to compile. This is not necessarily the case, especially where the warning relates to the build context which is under the users control.
Examples of this:

Warning that support for a given architecture or endianess is experimental / not validated
Warning that the build is falling back to a vendored build dependency - prost-build moved away from vendoring protoc and caused significant continuing ecosystem pain, a warning might have been a nicer way to handle this
Warning that some property of the environment is resulting in a sub-optimal fallback, e.g. non-SIMD kernels

Whilst these cases could error, this feels a little heavy-handed for what should be a very strong suggestion.
Proposed Solution
I would like println!("cargo:user-warning={msg}") to always print msg as a warning even if the build does not fail. @alexcrichton previously wrote on a similar proposal in https://github.com/rust-lang/cargo/issues/3777

Typically when you check out a C project and run ./configure && make you're sprayed with megabytes of output that you don't really know how to parse anyway. Cargo strives to avoid this by having the output be meaningful to the user (any user) at the time and not have a bunch of superfluous information.

I think this is still consistent with this, it avoids unconstrained log spam, whilst explicitly only surfacing information that is user-facing.
Notes

It's reasonable for Cargo to provide a transition mechanism for the whole ecosystem. However, the compilation is pipelined and usually interleaved. Print them all out without buffering might still be scary to some users. Even with a proper buffering, people might still feel overwhelmed and exhausted. npm has experienced a period of library maintainers advertising themselves via postinstall hook^1. Cargo should be cautious to that situation.
After that, I believe npm introduced a new command npm-fund for library maintainers leaving message to users. Since Cargo already stores stderr for build script, we could have a hint telling users to run with cargo report some-new-command if they want to read those messages. For example,
note: 3 warnings emitted during running the custom build for `foo v0.5.0 ([CWD])`
    Run `cargo report replay-message -p foo` to read messages from `foo`.

(Even with npm fund, people still don't love that single line hint 😆.^2)

Other related issues:

New build script instruction may require to use a new synax, e.g. :: in cargo::SOMETHING_NEW=X.
https://github.com/rust-lang/cargo/issues/11461
panic! doesn't help at this moment, since the error message is currently a bit too verbose.
https://github.com/rust-lang/cargo/issues/10159

Since Cargo already stores stderr for build script, we could have a hint telling users to run with cargo report some-new-command if they want to read those messages.

This seems good to me, and would not require new build directives, avoiding #11461
I presume this wouldn't pick up normal warnings, i.e. if compiling the build script produced a warning it wouldn't be included? The only inclusions would be from cargo:warning={msg}?

One of the technical difficuties of my proposal is that Cargo doesn't really have the knowledge of the arguments of your previous build, so it might be hard to determine the right output to display.

I presume this wouldn't pick up normal warnings, i.e. if compiling the build script produced a warning it wouldn't be included? The only inclusions would be from cargo:warning={msg}?

Cargo stores stdout/stderr of the build script execution under target/debug/build/<crate>. For compiling crates, messages from rustc are put under target/debug/.fingerprint/<crate>/output-<something>. See API doc cargo::core::compiler::layout for more. Note that this layout is not stable and subject to change.


add: custom sidebar + react spectrum update

Description
Use custom styles for sidebar Nav
Update React spectrum to 3.3.0
Related Issue
Fix #93
Motivation and Context
Side bar uses list item element which is not a page nav
How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@rajarju Can you post a screen-shot or better yet, a gif of the changes so we can see it without having to install and test ourselves?

@purplecabbage


amplify-cli no prompt for MFA token

Describe the bug
I'm using an AWS profile to assume a role as per the following configuration...
[profile amplify-staging]
mfa_serial=<arn>
source_profile=jamie-amplify
role_arn=<arn>
region=us-east-1

When running amplify push I am not prompted for an MFA token.
Amplify CLI Version
$ amplify -v
4.40.1

To Reproduce
Running amplify push
 $  amplify push
⠋ Fetching updates to backend environment: staging from the cloud.Profile amplify-staging is configured to assume role
  <role_arn>
It requires MFA authentication. The MFA device is
  <mfa_serial>

There is no prompt for an MFA token, however, I eventually noticed that the prompt is just not visible, i.e. is still waiting for input. However, it can take several attempts for the cli to register the input...
 $  amplify push
⠋ Fetching updates to backend environment: staging from the cloud.Profile amplify-staging is configured to assume role
 <role_arn>
It requires MFA authentication. The MFA device is
  <mfa_serial>
? Enter the MFA token code: 752983
⠏ Fetching updates to backend environment: staging from the cloud.Profile amplify-staging is configured to assume role
  <role_arn>
It requires MFA authentication. The MFA device is
  <mfa_serial>
? Enter the MFA token code: 879594
✔ Successfully pulled backend environment staging from the cloud.

Current Environment: staging

Expected behavior
Prompt for MFA token and proceed with deployment.
Desktop (please complete the following information):

OS: Mac (MacOS Catalina 10.15.7)
Node Version:

$ node -v
v12.19.0

Update
If there are pending changes in your environment, you're prompted to select whether or not you want to continue with the deployment. It seems you need to provide another auth token after this...
? Are you sure you want to continue? Yes
⠸ Updating resources in the cloud. This may take a few minutes...Profile amplify-staging is configured to assume role
  <role_arn>
It requires MFA authentication. The MFA device is
  <mfa_serial>
? Enter the MFA token code: <token>
⠙ Updating resources in the cloud. This may take a few minutes

Not sure if the credentials are being cached correctly? after a successful auth the cache file appears like so...
{
    "<role_arn>": {}
}

Got the same issue. Added Storage to a new project and im not able to push it. Need to go around the long way and deploy it via the console.

Got the same issue. Added Storage to a new project and im not able to push it. Need to go around the long way and deploy it via the console.

Still got the same issue, using Version 4.41.1
amplify push
⠋ Fetching updates to backend environment: dev from the cloud.Profile test is configured to assume role
  arn:aws:iam:xxxxxxxx:role/xxxxxxx-role
It requires MFA authentication. The MFA device is
  arn:aws:iam::xxxxxxx:mfa/xxxxxxx

⠦ Fetching updates to backend environment: dev from the cloud.

Still got the same issue, using Version 4.41.1
amplify push
⠋ Fetching updates to backend environment: dev from the cloud.Profile test is configured to assume role
  arn:aws:iam:xxxxxxxx:role/xxxxxxx-role
It requires MFA authentication. The MFA device is
  arn:aws:iam::xxxxxxx:mfa/xxxxxxx

⠦ Fetching updates to backend environment: dev from the cloud.

I can confirm the same issue. It took us quite some time to figure it out... It would be awesome if this could get fixed! Many thanks!
node -v
v14.15.1

amplify version
4.41.2

cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"


Internal Server Error inside dialog of Metadata component inside 1.5 version (AEM 6.3 + SP2)

Do you have the full stacktrace?

@anoopkumargarg Can you provide more information on this? Have you created your own Computed Properties at all? Can you get the full stacktrace?


Android devices are released a long period of time after a job aborting

Android devices are released a long period of time after a job aborting. The time of waiting (when devices will be available) is about 40 minutes. This issue was appeared when video recording and screenshots were enabled.
Device/OS: all android devices;
Appium version: 1.13.0.
It's look like Carina doesn't understand that devices are available, and think that somebody use them.

set of fixes are available in overall appium-device container to make it more stable. Also provided recommendation for private listeners howto minimize risks of the occupied devices


How to convert settings.stylecop to stylecop.json?

Is there a tool to convert settings.stylecop to stylecop.json? Or do we have to start from scratch?

I would say it's best to start from scratch. The actual work to set things up is pretty simple (not many options are exposed to the user, and enabling rules is just check boxes). The main difficulties with automating this are:

Configuration in StyleCop Analyzers is split between rule set files and stylecop.json.
The options we do expose in stylecop.json do not exactly match the options in Settings.StyleCop.

So what happen if I want to add some 'recognized words' from the Spelling tab in the old Settings.StyleCop file? As well as the culture in the option tab.

@microkarl The spell checking functionality was intentionally omitted from StyleCop Analyzers. See KnownChanges.md for details.
Currently there is no ability to set/override the culture. There are a few open issues regarding this but no decisions have been made yet.


Incorrect MAC address

Hi,
on my raspberry pi 4b (linux debian 11) i get the loopback mac address 00:00:00:00:00:00 from get_mac_address() which is undesirable/useless
on my windows 11 machine it works without a problem but in wsl (linux debian 11 inside windows) i have the same problem
sadly i have to revert to the upstream crate as long as this fork has this bug with non-windows machines
i used the following code for checking:
Cargo.toml
[package]
name = "test_mac"
version = "0.1.0"
edition = "2021"

[dependencies]
mac_address = "1.1.4"
mac_address2 = "2.0.0"

src/main.rs
use mac_address::get_mac_address;
use mac_address2::get_mac_address as get_mac_address2;

fn main() {
    match get_mac_address() {
        Ok(Some(ma)) => {
            println!("mac => {}", ma);
            println!("bytes => {:?}", ma.bytes());
        }
        Ok(None) => println!("No MAC address found."),
        Err(e) => println!("{:?}", e),
    }
    match get_mac_address2() {
        Ok(Some(ma)) => {
            println!("mac2 => {}", ma);
            println!("bytes2 => {:?}", ma.bytes());
        }
        Ok(None) => println!("No MAC address found."),
        Err(e) => println!("{:?}", e),
    }
}

Output (censored but the issue is visible):
mac => 00:15:5D:XX:XX:XX
bytes => [0, 21, 93, x, x, x]
mac2 => 00:00:00:00:00:00
bytes2 => [0, 0, 0, 0, 0, 0]

upstream (mac_address) doesn't seem to have the same problem (even tho there is a similar open issue which i cannot reproduce)
for me only this fork (mac_address2) seems to be affected
related : https://github.com/repnop/mac_address/issues/33

Check the version 2.0.2 please. If there's still the same problem, feel free to reopen.


Making custom inferences

Thank you for sharing your code. I am trying to reproduce and understand it.
It will be of great help if you could kindly provide some information on how to get custom inferences, i.e., providing an image, query, and dialog; and generating the answer. Thank you.

Hi @puneet-kr, thank you for your interest.
General procedures for inference are as follows:

load the pre-trained model
embed inputs to vector (image, query, dialog history, answer candidates)
feed the embeddings to the model
transform the model output to human readable output

If you need to get custom inferences, pre-processing steps for embedding vector are required !
Embedding for image inputs --> Faster R-CNN
Embedding for text inputs --> word tokens to pre-defined numbers using word to index dictionary


Proposed solution

We already know the size of each sponsor image max-height: 80px;   max-width: 150px; which can be scaled before CSSOM generation.

Help Link
https://www.npmjs.com/package/node-image-resize

@aayusharora I would like to work on this.

I am working on this. First tried using "sharp" module with sponsor images, it is working but the only issue is that it is cropping the images instead of resizing in resolution.
Here is the commit https://github.com/poush/open-event-webapp/commit/bc8720ab32264a6fed261a62363c32a2f26f7ff1 of it.
About that module "node-image"resize", it is not updated since 3 years supporting old version of nodejs.
I will look into it more tonight.


Fixed LoRA conversion for kohya_ss

diffusers have recently replaced Conv2d and Linear layers with LoraCompatibleConv and LoraCompatibleLinear.
This pull request fixes wrong conversion of kohya_ss trained LoRAs. It should be better to determine whether module is Linear or Conv2d block based on class inheritance, not based on its name.
@BenjaminBossan @pacman100 your review is kindly appreciated.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

@BenjaminBossan hi!
I am not quite sure whether this case can be covered by some sort of test (also, from the perspective that it's just an example, not a full part of the library). I have run this script in an environment with one of the recent versions of diffusers and after conversion succeeded, I've discovered that the results seemed to differ from what I was getting in webui.
So, what I've found out during investigation is that now Linear and Conv layers are not processed properly and that 20-30% of LoRAs files were lost.

@BenjaminBossan sounds like a great idea, I'll provide all the details soon.
Also, do you need my help in terms of modifying GH actions?

I'll provide all the details soon!

Fantastic.

Also, do you need my help in terms of modifying GH actions?

As you wish. We can also add it in a separate PR later.

@BenjaminBossan hi!
Here is a sample notebook which shows the loss of weights size when converting with the old script and the results after fix.
It can be used as some sort of reference for writing test.
Would you mind if I'll work on this test in a separate PR later? I have some plans on heavily refactoring this script for proper support of other models and would like to do it in a separate PR.

It can be used as some sort of reference for writing test.

Sounds good.

Would you mind if I'll work on this test in a separate PR later? I have some plans on heavily refactoring this script for proper support of other models and would like to do it in a separate PR.

Yeah, we can add it later.
Let me ping @pacman100 or @younesbelkada for a potential second review, but I think this should be good to go.


Error in Documentation

In the usage section, you have the following:
var regex = require('regex-utc-date');
Shouldn't it be?:
var regex = require('regex-email ');

Where?

There:
https://www.npmjs.com/package/regex-email

It's because the package hasn't been published since the README was updated.

Ok, I'll send an email to the maintainer of the npm repo.
Thanks for a ridiculously quick feedback.

Just ping him here, @tunnckoCore, could you do a patch relase?

Just ping him here, @tunnckoCore

K, I'll contact him there.

could you do a patch relase?

Do you mean a new npm repo with the right doc? Sounds wasteful if the original publisher of the npm repo can simply patch his release.

@Magnitus-, that's what I meant :).

Ok, I'll give him a reasonable amount of time to update and if that hasn't happened by then, then I'll patch.

@Magnitus-, you don't need to. Just wait.

Released as 1.0.2. Didn't receive an email by the way :cry:

Sorry, the mailer-daemon gave up ;)


error: overlapping duplicate transcript feature with Stringtie 1.3.3b

Hi there,
I read over the last thread from 2016 that dealt with this issue already, but I am using Stringtie 1.3.3b (which has an updated GFF parser since the bug from back then), and get the following error:
GFF Error: overlapping duplicate transcript feature (ID=FBgn0013687)
My command:
$STRINGTIE -p $CPUS -G $GTF -o $BASEDIR/assembled/$b.gtf $BASEDIR/BAM/$b
($b is a loop variable, which is the name of a BAM file)
I am not running --merge, I am getting this error for assembly.
grep 'FBgn0013687' 'Drosophila_melanogaster.BDGP6.91.gtf' returns:
mitochondrion_genome	FlyBase	gene	14917	19524	.	+	.	gene_id "FBgn0013687"; gene_name "mt:ori"; gene_source "FlyBase"; gene_biotype "pseudogene";
mitochondrion_genome	FlyBase	transcript	14917	19524	.	+	.	gene_id "FBgn0013687"; transcript_id "FBgn0013687"; gene_name "mt:ori"; gene_source "FlyBase"; gene_biotype "pseudogene"; transcript_source "FlyBase"; transcript_biotype "pseudogene";
mitochondrion_genome	FlyBase	exon	14917	19524	.	+	.	gene_id "FBgn0013687"; transcript_id "FBgn0013687"; exon_number "1"; gene_name "mt:ori"; gene_source "FlyBase"; gene_biotype "pseudogene"; transcript_source "FlyBase"; transcript_biotype "pseudogene"; exon_id "FBgn0013687-E1";
-bash-4.1$ grep 'FBgn0013687' Drosophila_melanogaster.BDGP6.91.gtf
mitochondrion_genome	FlyBase	gene	14917	19524	.	+	.	gene_id "FBgn0013687"; gene_name "mt:ori"; gene_source "FlyBase"; gene_biotype "pseudogene";
mitochondrion_genome	FlyBase	transcript	14917	19524	.	+	.	gene_id "FBgn0013687"; transcript_id "FBgn0013687"; gene_name "mt:ori"; gene_source "FlyBase"; gene_biotype "pseudogene"; transcript_source "FlyBase"; transcript_biotype "pseudogene";
mitochondrion_genome	FlyBase	exon	14917	19524	.	+	.	gene_id "FBgn0013687"; transcript_id "FBgn0013687"; exon_number "1"; gene_name "mt:ori"; gene_source "FlyBase"; gene_biotype "pseudogene"; transcript_source "FlyBase"; transcript_biotype "pseudogene"; exon_id "FBgn0013687-E1";

It seems that gene, exon, and transcript all overlap. Is this a known issue, and do you have an idea about how to solve it?
Thanks a lot in advance.
Best,
Patrick

Indeed, the fact that the  gene and transcript features have the same ID caused the problem there (gene_id is taken as the ID for the gene feature). Thanks FlyBase for generating malformed GTF files once again.. :). The GFF3 version of this file would have exposed the problem even more glaringly (the same ID cannot be user for different features).
Anyway, I was just adjusting a few more things in/around GFF/GTF parsing, again.. I think I fixed this special case too. Please get the pre-release version 1.3.4a (that means: "alpha") and give it a whirl..  (fetch it from:  http://ccb.jhu.edu/software/stringtie/#install )
This version should no longer stumble while parsing that GTF, but please let me know if you encounter any other problems.

Thanks a lot for your quick reply, I will give 1.3.4alpha a go soon and let you know how it went. :) Again, really appreciate the quick response and help!

Works! Using the 1.3.4 version fixed this issue. Thanks!


Update app-only-auth-powershell-v2.md

Docs Build status updates of commit d3eb1bf:
:clock10: Full build: the average full build time is 17 min(s) 31 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit d3eb1bf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 620faa8:
:clock10: Full build: the average full build time is 17 min(s) 31 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 620faa8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 912d686:
:clock10: Full build: the average full build time is 17 min(s) 31 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 912d686:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Unable to display the output.

Hi I am trying to run the code on google colab, but at the end I am unable to get the final output.
2023-02-27 08:39:09.639300: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F AVX512_VNNI FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-02-27 08:39:09.769144: I tensorflow/core/util/port.cc:104] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2023-02-27 08:39:10.469656: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/lib64-nvidia
2023-02-27 08:39:10.469742: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/lib64-nvidia
2023-02-27 08:39:10.469758: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
Serving TensorBoard on localhost; to expose to the network, use a proxy or pass --bind_all
TensorBoard 2.11.2 at http://localhost:6006/ (Press CTRL+C to quit)

It looks like it fails to load some dynamic libraries. Not sure what causes this error, but it is unrelated to the code itself. Please check your colab settings.

Grapher]$ tensorboard --logdir output
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint32 = np.dtype([("qint32", np.int32, 1)])
/cm/shared/public/apps/miniconda/3.7/lib/python3.7/site-packages/tensorflow/python/framework/dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
/home/sgudati/.local/lib/python3.7/site-packages/tensorboard_data_server/bin/server: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /home/sgudati/.local/lib/python3.7/site-packages/tensorboard_data_server/bin/server)
Serving TensorBoard on localhost; to expose to the network, use a proxy or pass --bind_all
TensorBoard 2.11.2 at http://localhost:6006/ (Press CTRL+C to quit)
Unable to visualize the final output. Is it the version that I need to update?

i found this type of error :-
NOTE: Using experimental fast data loading logic. To disable, pass
"--load_fast=false" and report issues on GitHub. More details:
https://github.com/tensorflow/tensorboard/issues/4784
Traceback (most recent call last):
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/bin/tensorboard", line 8, in
sys.exit(run_main())
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/main.py", line 46, in run_main
app.run(tensorboard.main, flags_parser=tensorboard.configure)
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/absl/app.py", line 308, in run
_run_main(main, args)
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/absl/app.py", line 254, in _run_main
sys.exit(main(argv))
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/program.py", line 276, in main
return runner(self.flags) or 0
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/program.py", line 292, in _run_serve_subcommand
server = self._make_server()
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/program.py", line 472, in _make_server
deprecated_multiplexer,
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/backend/application.py", line 146, in TensorBoardWSGIApp
experimental_middlewares,
File "/DATA/chatterjee2/anaconda3/envs/rajnishgrapher1/lib/python3.7/site-packages/tensorboard/backend/application.py", line 254, in init
"Duplicate plugins for name %s" % plugin.plugin_name
ValueError: Duplicate plugins for name projector
please help me.

another error :-
2024-04-13 14:42:19.440814: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-04-13 14:42:19.736572: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory
2024-04-13 14:42:19.736635: I tensorflow/compiler/xla/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
2024-04-13 14:42:20.742295: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory
2024-04-13 14:42:20.742429: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory
2024-04-13 14:42:20.742448: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2024-04-13 14:42:21.987385: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.987526: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcublas.so.11'; dlerror: libcublas.so.11: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.987597: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcublasLt.so.11'; dlerror: libcublasLt.so.11: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.991509: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcusolver.so.11'; dlerror: libcusolver.so.11: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.991631: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcusparse.so.11'; dlerror: libcusparse.so.11: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.991703: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudnn.so.8'; dlerror: libcudnn.so.8: cannot open shared object file: No such file or directory
2024-04-13 14:42:21.991732: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1934] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
NOTE: Using experimental fast data loading logic. To disable, pass
"--load_fast=false" and report issues on GitHub. More details:
https://github.com/tensorflow/tensorboard/issues/4784
Serving TensorBoard on localhost; to expose to the network, use a proxy or pass --bind_all
TensorBoard 2.11.2 at http://localhost:6006/ (Press CTRL+C to quit)
but it doesn't give any output in this localhost.    , please help me


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1688

Questions ?
Please refer to the Backport tool documentation


Typos on Volunteer page

I found some typos on the volunteer page at http://shescoding.org/volunteer
Here are the issues with my suggested solutions:
Under Events > Code-a-thon Organizer - Update "Set up 2-month schedule (kick-off, wid-way, demo day)" to say "mid-way" instead of "wid-way"
Under Open Source Development > Engineering Manager - change "Make sure project master is in healthy state" to "Make sure project master is in a healthy state" (added a before healthy state)
Under Organization > Volunteer Coordinator
Change "Do reach out to find volunteers" to "Reach out to find volunteers"
It sounds better to me when it doesn't start with Do

@natsteinmetz Can you please confirm these should be fixed. I'm pretty sure the first two should, but maybe the "Do" is intentional in the third one?


Integrate SATZilla 2024 into Sparkle

The new version of SATZilla is now published https://github.com/hadarshavit/revisiting_satzilla.
Integrate it into sparkle instead of the old version.

Will happen after the paper linked to the repo is published


Failed to query but invoke is okay

Hi,
Deployed successfully the BlueMix tutorial "learn-chaincode" program to BlueMix (the program is compiled successfully) also successfully ran the 'invoke' but failed at 'query' request.  The error message shown was
{
"jsonrpc": "2.0",
"error": {
"code": -32003,
"message": "Query failure",
"data": "Error when querying chaincode: Error:Failed to launch chaincode spec(Error starting container: API error (500): Error: image library/f6eebcc6-5d8c-4dfa-b168-22d407ea8eb7-vp1-2aea9fb4994a013f958f69563279f44d191bf0cfa68a1df68a7c8279103378d538b4fe895512d27f86bb4b16242ba6f7b1d4eaffe6a1f6ec7f3020bb3b240bda not found\n)"
},
"id": 4
}
Here are some of the peer log =
ERR - 20:57:27.743 [peer] SendMessage -> DEBU 256f28 Sending message to stream of type: DISC_GET_PEERS
ERR - 20:57:27.744 [consensus/handler] HandleMessage -> DEBU 256f29 Did not handle message of type DISC_PEERS, passing on to next MessageHandler
ERR - 20:57:27.744 [peer] HandleMessage -> DEBU 256f2a Handling Message of type: DISC_PEERS
ERR - 20:57:27.744 [peer] beforePeers -> DEBU 256f2b Received DISC_PEERS, grabbing peers message
ERR - 20:57:27.744 [peer] beforePeers -> DEBU 256f2c Received PeersMessage with Peers: peers:<ID:<name:"vp0" > address:"f6eebcc6-5d8c-4dfa-b168-22d407ea8eb7_vp0.us.blockchain.ibm.com:30303" type:VALIDATOR pkiID:"\3461\026\362\242\224\340\227\274\204\313\225a\317m\003\261=\221\232\n\354=\260-\246\214\365\225\267 " > peers:<ID:<name:"vp2" > address:"f6eebcc6-5d8c-4dfa-b168-22d407ea8eb7_vp2.us.blockchain.ibm.com:30303" type:VALIDATOR pkiID:"\211B ?\236|\323g\371\3050\220\277\037\311\002\217\256\311\204\210r\001:\313\222>\001\314\276<\205" > peers:<ID:<name:"vp1" > address:"f6eebcc6-5d8c-4dfa-b168-22d407ea8eb7_vp1.us.blockchain.ibm.com:30303" type:VALIDATOR pkiID:"|=G\261\343\267\303\221\230\275\327\312\017\260\224\230~d\357\343\207\354#h<LR$0\202W" >
ERR - 20:57:27.783 [consensus/handler] HandleMessage -> DEBU 256f2d Did not handle message of type DISC_GET_PEERS, passing on to next

Look for peer logs with the tags container, chaincode, or dockercontroller.  These will indicate what happened during the deployment process.

Hi,
I search all 4 peer logs but couldn't find container, chaincode and dockercontroller in the logs.
Do advise what to do next

Should have specified this in the original comment, sorry.  The peer logs are actually rotating, so it's likely that the logs from your previous deployment are probably gone already.  Try deploying the chaincode while watching the logs and see if you can spot these tags.

closing, issue seems abandoned

Got this error when trying to do deploy the chaincode usind node sdk
using the tutorial at https://new-console.ng.bluemix.net/docs/services/blockchain/etn_sdk.html#nodesample
data": "Error when querying chaincode: Error:Failed to launch chaincode spec(Error starting container: API error (500): Error: image library/72eaffaf-7ad5-4d8e-8ab3-4131c6a11d17-vp1-b07fe2bc5f79dbf4f1f38bb8272e98a2dc70340323e93892804f820c6d58a4c8 not found\n)"
},
I tried to redeploy it but getting same error again.
I see lot of people faced the same issue. Any fix??


Move tests

Coverage remained the same at 95.492% when pulling fab14bb17f824dd1b5dd256af6670f40c1877f6a on move-tests into ebd6539b1d09c5704d05290fe0c06c45773040e5 on master.


JS Capstone: Setup the Kanban Board

Description
We used a Kanban board with filled-in tasks that have categories and time estimations to assign work in our group.
https://github.com/OkoyeCharles/js-capstone
Note:

There are three people on my team.

Hi Team,
Good job so far! 👍🏻
There are some issues that you still need to work on to go to the next project but you are almost there!

Required Changes ♻

[ ] Please make sure to assign all tasks to team members, as per this requirement.

Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

@ShadyShawkat please could you describe how we are required to do so, can it be done on Github's UI, because we have already assigned ourselves an ID (ie. Student A, Student B, Student C).
I would love it if you could explain further.
Thanks.
Charles.

Hi @OkoyeCharles,
You can assign members to tasks in the GitHub UI.
First, you need to select all of the tasks you'd like to assign to a member from the checkbox on the left of each task.

Then you can click on the "Assignee" drop-down list. and click on the team member- or members- you'd like to assign to the tasks.

After you choose the team members from the assignee list, you can just click off the drop-down list and the page will refresh and show the updated tasks with the assigned tasks.
I hope this helps.

**STATUS: APPROVED  🟢 **

Hi team,
Great work on making the changes requested by a previous reviewer 👏🏻
Your project is complete! 💯🌟

Cheers and Happy coding! :clap: :clap: :clap:
Feel free to leave any questions or comments in the PR thread by mentioning my Github username if something is not 100% clear.

As described in the Code reviews limits policy you have  limited number of  reviews per this project. If you think that the code review was not fair, you can request a second opinion using this form.


Feature request: Starred/ Pinned experiments

Thanks again for this great product.
Is there a way to star favorite experiments or to short list some or even to pin to top? I find myself scrolling down in the list to reach the experiment I want to compare to.
Thanks again!

Hi @majdzr ,
For creating a multi-experiment comparison - once you select (mark the checkbox) an experiment, the selection holds regardless of the current view, so you can use column filters or the top search bar to quickly get to the additional experiments you want to select (as long as they're all within the same project scope).
Or, does your use case go beyond selecting experiments such as any of the following:

"Forcing" a set of experiments to be shown in adjacent rows regardless of the rest of the table order?
Creating a custom "quick filter" to easily return to the same set of experiments (Note you can use such a similar "Star" functionality by applying your own custom tag to the experiments of interest and then filtering on it).

What makes the most sense to you?

Hey, thanks for the quick reply.
Indeed, I'm already using this, but I also think these two options might
even make the process easier. Or even a simpler solution of creating a
starred/master experiment(s) that always show in the comparison, regardless
of the filter or being selected.
What do you think?
On Wed, Jul 15, 2020, 10:05 PM Noam Wasersprung<EMAIL_ADDRESS>wrote:

Hi @majdzr https://github.com/majdzr ,
For creating a multi-experiment comparison - once you select (mark the
checkbox) an experiment, the selection holds regardless of the current
view, so you can use column filters or the top search bar to quickly get to
the additional experiments you want to select (as long as they're all
within the same project scope).
Or, does your use case go beyond selecting experiments such as any of the
following:

"Forcing" a set of experiments to be shown in adjacent rows
regardless of the rest of the table order?
Creating a custom "quick filter" to easily return to the same set of
experiments (Note you can use such a similar "Star" functionality by
applying your own custom tag to the experiments of interest and then
filtering on it).

What makes the most sense to you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/allegroai/trains/issues/169#issuecomment-658980255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADU6DBPWPMVC7DSJDOL7ZJLR3YDXBANCNFSM4O2NKTMA
.

@majdzr So it sounds like we're discussing several possible features - From your latest comment I understand that your compelling need is for a comparison template (notice I'm distinguishing between what's seen in the experiment table, and the members in the comparison) to which you can repeatedly add additional experiments?
Notice, that within the existing capabilities, you can have your browser bookmark a specific comparison (or, use the "share" button, to get the comparison URL), and then start of from this saved comparison and use "add experiment" for additional experiments.

@ainoam Yes, you can see it as a comparison template, containing several ("pinned"/"starred") experiments, that can be removed (unpinned or unstarred) easily.


Bedrockify support

Bedrockify has that interesting feature called «Screen safe area» which moves the hotbar up. Would like to use it with this mod.

I'll look into it!

I looked hard into bedrockify's code, and didn't find any reasonably simple way to inject into it.
segmented supports raised (https://modrinth.com/mod/raised), so if you want this functionality, it's available through that mod.


QueryBus with FinalizeGuard enabled returns null

Hi, I am lost with FinalizeGuard and how to set it up properly. I am not sure if this relates to Laravel package or to MessageBus core.

I have my query and corresponding finder. On success it resolves Deferred like this:

class QueryFinder {
    function __invoke($query, Deferred $deferred = null): void
    {
        //...
        $deferred->resolve($query_result);
    }
}

I enabled FinalizeGuard in prooph.php config file.

But the result of the query returns null.

// I use facade
$query_result = QueryBus::resultFrom($query);
// $query_result is null now

If I disable the FinalizeGuard then query returns valid result. So it led me into looking inside of the FinalizeGuard code.

Looking at 48 line: https://github.com/prooph/service-bus/blob/c239acfd43cf8eec577e30ce0aa7da86d87b6191/src/Plugin/Guard/FinalizeGuard.php#L48
It creates a new Promise and here it losts resolved result.

It seems that I misuse QueryBus. Can you suggest the right way of resolving Deferred object inside my QueryFinder which works with FinalizeGuard?

It seems that I misuse QueryBus

Why you think you misuse the query bus?
$this->queryBus
            ->dispatch(
                (new GetCustomer(['customer_id' => ...]))
            )
            ->done(function (QueryResult $result) use (&$dto) {
                $dto = $result->data();
            });

This works for me with FinalizeGuard enabled

Hmm, can you show how you resolve deferred promise inside the finder class?

    public function getCustomer(GetCustomer $query, Deferred $deferred): void
    {
        /** @var Customer $customer */
        if ($customer = $this->entityManager->getRepository(Customer::class)->find($query->customerId())) {
            $customerDTO = CustomerDTO::fromEntity($customer, $query->included());

            $deferred->resolve(JsonApiQueryResult::with($customerDTO, [], new EncodingParameters($query->included())));
        } else {
            $deferred->reject(new DomainException('Not found', 404));
        }
    }

Ok, the problem persists.
I have created a new project from scratch with laravel-package: https://github.com/lezhnev74/prooph-query-test

I have installed prooph and configured it here: https://github.com/lezhnev74/prooph-query-test/blob/master/config/prooph.php
If I comment out the line 45 tests pass, if I uncomment it, tests fail:

45: \Prooph\ServiceBus\Plugin\Guard\FinalizeGuard::class

This test runs a query and validates result is not null:
https://github.com/lezhnev74/prooph-query-test/blob/master/tests/Component/Account/Query/FindAccountByEmail/FindAccountByEmailHandlerTest.php
it can be run like this: vendor/bin/phpunit --testsuite=Components

Can you tell if I configured prooph wrong or something is not right?
Composer says I have these versions:
prooph/common                         v4.2.1  Common classes used across prooph packages
prooph/event-sourcing                 v5.3.0  PHP EventSourcing library
prooph/event-store                    v7.3.1  PHP EventStore Implementation
prooph/event-store-bus-bridge         v3.1.0  Marry CQRS with Event Sourcing
prooph/laravel-package                v0.4    Laravel package for prooph components to get started out of the box with message bus, CQRS, event sou...
prooph/pdo-event-store                v1.6.0  Prooph PDO EventStore
prooph/pdo-snapshot-store             v1.4.0  PDO Snapshot Store Implementation
prooph/service-bus                    v6.2.0  PHP Enterprise Service Bus Implementation supporting CQRS and DDD
prooph/snapshot-store                 v1.3.0  Prooph Snapshot Store

P.s. I use a standalone router which maps directly command(query) to it's handler so routes config is empty.
P.p.s I will try to install prooph fresh with no laravel dependency and try it in another branch of that repo.

I have removed everything and included just bare message bus and implemented this test:
https://github.com/lezhnev74/prooph-query-test/blob/prooph-bare/tests/QueryTest.php
It has 3 tests:

executing query with no guards [pass]
executing query with RouteGuard [pass]
executing query with FinalizeGuard [fail]

This is not about Laravel packag I'd say, so I am closing this issue.
The issue in message bus hub: https://github.com/prooph/service-bus/issues/177


Port the Usage instructions

Please port the Ruby usage instructions to Python: https://github.com/quicksprout/naas-api-client-ruby/blob/master/USAGE.md

In Progress.

@stevecox - The usage instructions were ported. I'll add other documentation for the new models.


localStorage is no longer being store correctly in hammer head

What is your Test Scenario?

localStorage is persisted when going to a new tab  via the hammerhead-storages mechanism
What is the Current behavior?

When going to a new tab in TestCafe v1.0.0 or above, local storage data is no longer available once window.open(url, '_blank') occurs whereas it happened previously.  It looks llike hammerhead|storages-sandbox-temp is not being transferred to hammerhead|storage-wrapper| as it was in TestCafe v0.23.3 and below
What is the Expected behavior?

Data in localStorage is persisted in a new link.
What is your web application and your TestCafe test code?

I am trying to make a reproducible demo as I cannot share the actual test because it is not a public site.  It is difficult to reproduce since it seems to only happen in one particular use case while it worked in others (it worked previously in Test Cafe versions <= 0.23.3).  When a link is clicked to open a new tab the localStorage mechanism doesn't work properly. The hammerhead|storages-sandbox-temp value becomes the key of the value pair it had (so if hammerhead|storages-sandbox-temp  was foo: {bar: 'baz'}  then it becomes foo.  At this point ordinarily the foo: {bar: 'baz'} would be put into the hammerhead|storage-wrapper| property in localStorage but this doesn't happen for some reason.

Execute this command...
See the error...

Your Environment details:

testcafe version:     1.1.0
node.js version:          8.10.0
command-line arguments:  chrome -e
browser name and version: chrome
platform and version:   Windows 10
other:

I've checked the behavior in a sample project and it works as expected. Please see the following example:
ls.html:
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title></title>

Open link

<button onclick="redirect()">Click button</button>

ls2.html
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title></title>

Tests
import { Selector } from 'testcafe';

fixture`fixture`
    .page`../pages/ls.html`;

test(`test1`, async t => {
    await t.expect(Selector('#result').innerText).eql('Felix');

    await t.click('a');

    await t.expect(Selector('#result').innerText).eql('Tom');
});

test(`test2`, async t => {
    await t.expect(Selector('#result').innerText).eql('Felix');

    await t.click('button');

    await t.expect(Selector('#result').innerText).eql('Tom');
});

I would really appreciate it if you reproduce the issue in a simple project. If you cannot share your project for security reasons, you can send all the details at<EMAIL_ADDRESS>


Removing jQuery dependency for Bloodhound

I removed jQuery as a dependency for Bloodhound.
Implementation details

I replaced $.error(s) with  new Error(s)
I replaced $.deferred with simply-deferred, which introduces a Deferred object that has an API that's compatible with $.deferred
I replaced $.ajax with a custom implementation that partially implements the API of $.ajax and returns a Deferred object
I replaced $.extend, $.noop, $.param and a few other methods with equivalent methods in common/utils that have the same API and the same behavior (at least in the contexts required by Bloodhound & Typeahead) but don't use jQuery as a dependency
I replaced all util methods in common/utils that used jQuery as a dependency with equivalent methods that have the same API and the same behavior but don't use jQuery as a dependency

Caveats

Unit tests still use $.ajax instead of _.ajax because ajax mocking in unit tests relies on jasmine-ajax v1.3.1, which only supports Ajax calls that use jQuery.
Although no unit tests are failing, I'm using Array.isArray quite a few instances, and this requires at least IE9. I suggest adding a polyfill if you really really want to keep IE8 compatibility, but I recommend dropping IE8 support as the current market share of IE8 is only 0.26% and dropping IE8 support would allow for the removal of more cruft.

Notes
The filesize of bloodhound.js increased from 33.8 KB to 52 KB and the filesize of bloodhound.min.js increased from 13.3 KB to 18.8 KB, as a consequence of replacing $.deferred, $.ajax, $.noop, $.param and other methods with equivalent implementations that don't rely on jQuery. However, there may still be some baby fat in these methods that could be trimmed (for example, unnecessary method & properties could be removed from Deferred). Nevertheless, for the time being I believe adding 5KB to bloodhound.min.js is a sacrifice worth being able to use Bloodhound without jQuery in all supported browsers.
I would recommend replacing Deferred with an implementation based on the native Promise object at some point in the future, but I don't think it's a good idea to do this as long as you plan on supporting any version of IE, since IE is lacking native Promise support and you'd need a polyfill anyway. So, at the moment, I don't believe replacing Deferred with a Promises/A+ compliant implementation is really worth the effort.

Update

I replaced this with _ in common/utils
I removed occurances of Array.isArray with _.isArray and reïmplemented that as function(obj) { return Object.prototype.toString.call(obj) === '[object Array]'; }

As far as I can tell, my code is now again compatible with IE8 and up, although I haven't tested on IE8.

any idea when this will be merged?

Any @corejavascript/collaborators have time to review this? I've changed employers and no longer use this project on a daily basis, so I can't justify taking on-the-clock time for maintenance like I used to.

I'm around, but don't have time either.
I think the first priority should be getting the integration tests working again.
@Grummfy @jslegers interested in becoming maintainers?

@mhluska :

Nice work. One question: why doesn't this PR remove jquery from package.json?

After my refactoring, Bloodhound no longer has jQuery as a dependency. However, Typeahead still does.
So, if you can to use Bloodhound without Typeahead, you no longer need jQuery.
If you want to use Typeahead, you'll still need jQuery.

@Grummfy @jslegers interested in becoming maintainers?

If I had more time...

@jslegers is there any chance to publish this as a standalone NPM package? I would love to use this in my project without committing the dist.min.js file to my repo (and without having jquery in my dependency tree).

@mhluska
If I ever get some time for it, I sure would consider giving it a try.
In the meantime, @ anyone reading this : feel free to fork my fork and create your own standalone Bloodhound repo based on it.

Damn I wish we could implement this sooner rather than later.
Perhaps leverage axios to handle the requests..

@jslegers is there a reason why you didn't removed jQuery from typeahead? or was it simply lack of time?

@jslegers is there a reason why you didn't removed jQuery from typeahead? or was it simply lack of time?

There's several reasons I only removed jQuery from Bloodhound and not from Typeahead :

Typeahead is a lot more tightly coupled with jQuery than Bloodhound. This makes it harder to de-couple & would require API changes.

The project I was working on only required Typeahead

I did not have the time to experiment with trying to de-couple jQuery from Typeahead, neither at my employer's nor after hours.


Documentation on using middlewares

What should we add or change to make your life better?
From looking at the source code I can see that you can add custom middlewares to the reverse proxy pipeline but I dont see any documentation outlining how to do it.
Why is this important to you?
I think many of the people looking at the project is because they need to do some customization at the pipeline level and they want to avoid having to do it in another language like Lua in the case of Kong. Having this documentation would be very useful.

We'll certainly need docs for the whole project. The pipeline feature was just added last week :grin:. You can find an example here: https://github.com/microsoft/reverse-proxy/blob/00c4e7c77059b7c4a9912a4c89c9a05026d55628/samples/ReverseProxy.Sample/Startup.cs#L49-L60
And here's a middleware. It's a normal ASP.NET Core middleware with the addition of proxy features like BackendInfo and IAvailableBackendEndpointsFeature:
https://github.com/microsoft/reverse-proxy/blob/00c4e7c77059b7c4a9912a4c89c9a05026d55628/src/ReverseProxy.Core/Middleware/LoadBalancingMiddleware.cs#L38-L61
Did you have a specific scenario in mind?

Thanks for the reply. Yeah the scenario I was specifically looking at is doing request transformations before passing it on to the backend. The reason we have this usecase is because we have legacy applications which are costly to modify, and in order to avoid being limited by them we use proxies to transform old request format into the new request format.

Makes sense. We're designing transforms as a first class feature over at https://github.com/microsoft/reverse-proxy/issues/21.

thank u actually I really don't understand what you saying I'm just brainstorming cos I'm a kind of human being never stop learning


Fix not found error codes to return an empty row if the queried resource is not found. Closes #11

Example query results

Results
Add example SQL query results here (please include the input queries as well)

@Subhajit97 do we have any docs that enlist the not found error codes for the APIs?

@misraved Unfortunately, no. I didn't find any proper documentation that listed the error codes for an API. I got these error codes while testing the APIs.


extract interfaces

extract all interfaces and structs into his own repository and use them.
extract all logic like parsercolored.go . they should also use this new repo

repository https://github.com/swaros/outinject

changes are merged #3


Parse error in mdx files

Hi, I'm reporting here too, because I realized an issue I originally reported at babel-plugin-module-resolver might not be specific to that resolver. Please read it for more information.
As I commented there, I also get parse errors when using the default node resolver, but on a different import.
import:
import styled from "styled-components";

Error:
21:20  error    Parse errors in imported module 'styled-components': parser.parse is not a function (undefined:undefined)  import/namespace
21:20  error    Parse errors in imported module 'styled-components': parser.parse is not a function (undefined:undefined)  import/default
21:20  warning  Parse errors in imported module 'styled-components': parser.parse is not a function (undefined:undefined)  import/no-named-as-default
21:20  warning  Parse errors in imported module 'styled-components': parser.parse is not a function (undefined:undefined)  import/no-named-as-default-member

Please try<EMAIL_ADDRESS>Notice about these new rules: https://github.com/rx-ts/eslint-plugin-mdx#rules

i have no idea what mdx is, but it’s not JavaScript, or supported by node, or Babel, so you’d definitely need your own eslint parser.

It would be better to support parseForESLint at https://github.com/benmosher/eslint-plugin-import/blob/master/utils/parse.js#L45, I can make a PR for it.

I'm not sure what you mean.
That particular utility is for parsing ES Modules or CJS modules (which are files, one module per file) - it's not meant to parse anything else.

@ljharb .mdx is handlered by @rxts/eslint-plugin-mdx, which exported a parseForESLint method without parse method, it should be supported by ESLint.
Reference: https://eslint.org/docs/developer-guide/working-with-custom-parsers

Gotcha - in that case, I agree with your suggestion, and a PR would be great. Thanks!

@cdfa Please take a look at #1435

I updated to<EMAIL_ADDRESS>and I'm getting a lot less errors, but still some. Please checkout my repo at https://github.com/cdfa/react-turn-reveal/tree/81bcee9cd3a34fdd18904f181c04fc9d5138a56e. The npm script to run eslint on MDX files is lint:mdx:eslint. You can also check out the CI job.

@cdfa please add a separated issue to @rxts/eslint-plugin-mdx repository.


RuntimeError: CUDA error: unspecified launch failure

Hello,
Great job! I encountered an issue when using PyTorch 1.12.0; it displayed the error "ecfp = ecfp.to(self.device) RuntimeError: CUDA error: unspecified launch failure. CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect. For debugging, consider passing CUDA_LAUNCH_BLOCKING=1." However, when I reverted to PyTorch 1.10.0, it worked. Due to certain reasons, I need to use PyTorch 1.12.0. Can you help me solve this problem?

Apologies for the delayed response.
In my opinion, this error may be related to your python environment or NVIDIA driver. Could you please verify whether other codes run properly with the PyTorch 1.12.0 environment?


stream=true requests cause "Object of type Stream is not JSON serializable" error

When sending a stream=true request to optiLLM, the service encounters the following error:
{"error":"Object of type Stream is not JSON serializable"}
This error suggests that optiLLM is not properly handling streamed responses from liteLLM or OpenAI GPT-4o. Instead of processing the stream incrementally, it attempts to serialize the raw stream object directly into JSON, which causes the serialization failure.
Steps to Reproduce:
Send a POST request to optiLLM with the following payload:
{
    "model": "gpt-4o",
    "messages": [
        { "role": "system", "content": "You are a helpful assistant." },
        { "role": "user", "content": "Write a Python program to build an RL model using only numpy." }
    ],
    "max_tokens": 1000,
    "stream": true
}

Observe the error response:
{"error":"Object of type Stream is not JSON serializable"}
Expected Behavior:
The optiLLM service should handle streamed responses by:

Iterating through the stream of chunks from liteLLM or OpenAI.
Processing each chunk incrementally and forwarding it to the next layer (e.g., AnythingLLM).

Additional Context:

The following pipeline works properly: User -> AnythingLLM -> liteLLM -> openai/gpt-4o
The problem seems specific to how optiLLM handles the streamed response from liteLLM.

Severity:
High - This issue blocks the usage of stream=true functionality, which is critical for incremental responses in real-time applications.

Most of the approaches require the full output and multiple calls to the LLM so we cannot stream the responses to the next layer as they come. We could handle it in optillm by waiting for the full stream to finish but the effect would be similar to using the underlying LLM without streaming.

Also encountered this while integrating OptiLLM.
A good middle ground for the LLM proxies is to stream what's possible. Every approach will have some portions that can be send back to the client for either traceability or as additional data even before the final response. In another proxy (don't want to link it) we called that "Intermediate outputs" and it can be toggled on/off based on the user preference.
However, this specific problem with OptiLLM break its compatibility with downstream services, for example - Open WebUI, which enabled streaming by default. If a full streaming support is not planned (understandably, it's a big undertake) - a reasonable workaround is to imitate streaming interface and simply send the whole response in a single chunk when the workflow is finished.

However, this specific problem with OptiLLM break its compatibility with downstream services, for example - Open WebUI, which enables streaming by default. If a full streaming support is not planned (understandably, it's a big undertake) - a reasonable workaround is to imitate streaming interface and simply send the whole response in a single chunk when the workflow is finished.

This is already done, the request here is to enable streaming inputs from the inference server. I can add am similar workaround as well to the inputs from inference server so as to not break anything. Good suggestion.

Yes, found the commit now, likely the streaming workaround is not fully compatible with Open WebUI due to some reason, thank you!


Usage question: how to force saved model to use GPU for predictions?

I trained an xgboost model using GPU (I verified using nvidia-smi)
I then saved it to disk as a pickle file
Later I load the pickle model to  query and make predictions. But now it always uses CPU. How do I make use of GPU for a pre-saved model build on GPU?

For now, you can set the parameter predictor to gpu_predictor. (we might change that after 2.0, but this should unblock your work).

I am using the github version 2.0.0.dev. Seems this did not really make any difference
xgb_model_from_disk.predictor = 'gpu_predictor'

Are you using the scikit learn interface? If so, then you need to call the set_params method

Yes scikit interface. If I use set_params. I get a different error
xgb_model_from_disk = pickle.load(open(outputfilename, "rb"))
xgb_model_from_disk.set_param({"predictor": "gpu_predictor"})

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Input In [8], in <cell line: 2>()
      1 #xgb_model_from_disk.predictor = "gpu_predictor"
----> 2 xgb_model_from_disk.set_param({"predictor": "gpu_predictor"})

AttributeError: 'XGBClassifier' object has no attribute 'set_param'

set_params vs set_param.  It's a standard scikit-learn function. To set the predictor: model.set_params(predictor="gpu_predictor")

Thank you so much. This helped. I can now see GPU utilization on predict


tortoise_models.zip wont download

Well i have a big problem becouse every time i download about 80-90% it says "connection error"
this is where i download it: https://drive.google.com/file/d/1yAoG1cl5gEwa1thcTi-Mwma5AIaWCQxN/view
and i have an idea that if someone have the file please upload it on MEGA and send me link on discord (jura GD#6768)
thanks for help and have a nice day

Be sure to indeed have a stable wifi connection while downloading these files.


minecraft: multiverse error while creating a new world ,

/mv create paradise normal -g ParadiseLand:Eden  < the command i use
plugins i have: mutliverse core, paradiseland
what happend:
I did the command , says in console creating 1% 4 % and so on until it stays on 65%-97%
and then the server crashes, restarting the server after the crash, trying to /mvtp paradise
wont work says unloaded, but i can also do /mv import paradise i did that , and then I noticed the scuffed generated world, screnshoots at the bottom,
im using server.pro as a hosting , on 2 gigabyte and 3+ hz , version 1.13.2
also tried few times - always the same end result but the precentage is always changing from 65% to 97 %
screenshoots of the new world that was created:

Duplicate of https://github.com/Multiverse/Multiverse-Core/issues/2005


Incorrect syntax highlight for javascript object literal vs ternary operator

ViM appears to be confused by colons in object literal vs. colons in ternary operator, it seems to think that {a: b?"C":"D"} means something like {a: (b?"C"): "D"} or maybe {(a:b?"C"): "D"} when it's really {a: (b?"C":"D")}.
:set ft
  filetype=javascript.jsx

I think it's pretty recent that it's showing syntax like this...
:version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 23 2019 15:11:20)
macOS version
Included patches: 1-2200
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl               +channel           +cscope            +ex_extra          -hangul_input      +lispindent        -mouse_gpm         +netbeans_intg     +python3           +startuptime       +terminfo          +virtualedit       -xfontset
+arabic            +cindent           +cursorbind        +extra_search      +iconv             +listcmds          -mouse_jsbterm     +num64             +quickfix          +statusline        +termresponse      +visual            -xim
+autocmd           -clientserver      +cursorshape       -farsi             +insert_expand     +localmap          +mouse_netterm     +packages          +reltime           -sun_workshop      +textobjects       +visualextra       -xpm
+autochdir         +clipboard         +dialog_con        +file_in_path      +job               +lua               +mouse_sgr         +path_extra        +rightleft         +syntax            +textprop          +viminfo           -xsmp
-autoservername    +cmdline_compl     +diff              +find_in_path      +jumplist          +menu              -mouse_sysmouse    +perl              +ruby              +tag_binary        +timers            +vreplace          -xterm_clipboard
-balloon_eval      +cmdline_hist      +digraphs          +float             +keymap            +mksession         +mouse_urxvt       +persistent_undo   +scrollbind        -tag_old_static    +title             +wildignore        -xterm_save
+balloon_eval_term +cmdline_info      -dnd               +folding           +lambda            +modify_fname      +mouse_xterm       +postscript        +signs             -tag_any_white     -toolbar           +wildmenu
-browse            +comments          -ebcdic            -footer            +langmap           +mouse             +multi_byte        +printer           +smartindent       -tcl               +user_commands     +windows
++builtin_terms    +conceal           +emacs_tags        +fork()            +libcall           -mouseshape        +multi_lang        +profile           -sound             +termguicolors     +vartabs           +writebackup
+byte_offset       +cryptv            +eval              +gettext           +linebreak         +mouse_dec         -mzscheme          -python            +spell             +terminal          +vertsplit         -X11
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X -DMACOS_X_DARWIN  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang   -L. -fstack-protector-strong -L/usr/local/lib -L/usr/local/opt/libyaml/lib<EMAIL_ADDRESS>-L/usr/local/opt/readline/lib  -L/usr/local/lib -o vim        -lncurses -liconv -lintl -framework AppKit  -L/usr/local/opt
/lua/lib -llua5.3 -mmacosx-version-min=10.15 -fstack-protector-strong -L/usr/local/lib  -L/usr/local/Cellar/perl/5.30.0/lib/perl5/5.30.0/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc  -L/usr/local/opt/python/Frameworks/Python.framework/Ver
sions/3.7/lib/python3.7/config-3.7m-darwin -lpython3.7m -framework CoreFoundation  -lruby.2.6

filetype=javascript.jsx

Does it make a difference, if jsx is not present in your filetype?

filetype=javascript.jsx

Does it make a difference, if jsx is not present in your filetype?

Nope, no difference, same with ft=javascript.

Hm, syntax/javascript.vim does not seem to be very well maintained. There was however just a recent update: https://github.com/vim/vim/commit/5be4ceecea5520265066eac972460ebb1cdf05e7#diff-83f2183b969b67eb8e03572e7824caa3
You might try, if reverting that part fixes the issue for you. Normally I would say, you should contact the maintainer, but I think Claudio is not active anymore.

hm, but that only adds await and the async keywords. That should not cause this.

I have just gone through my config and I've noticed that I have vim-jsx installed, which now has this warning its homepage:
IMPORTANT: This package is deprecated! It apparently broke following changes to the pangloss/vim-javascript JavaScript syntax package circa early 2019.
There's a good chance that's the source of my troubles!

okay, so first please try to reproduce the issue with a plain Vim without any packages loaded. Try starting vim --clean  and check with :scriptnames, that the vim-jsx package is not loaded. If this solves your problem, then the vim-jsx package was indeed your problem and we can close this here.

Solved by --clean indeed 🤦♂
I'll post an update when I get proper js+jsx setup working and tell what that is :)


Debugging of kubectl notification check test

Signed-off-by: Ondrej Dockal<EMAIL_ADDRESS>

Codecov Report
Base: 74.53% // Head: 74.69% // Increases project coverage by +0.16% :tada:

Coverage data is based on head (a07d78d) compared to base (e08f76d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #302      +/-   ##
==========================================
+ Coverage   74.53%   74.69%   +0.16%
==========================================
  Files          89       89
  Lines        3730     3730
  Branches      634      634
==========================================
+ Hits         2780     2786       +6
+ Misses        950      944       -6

Impacted Files
Coverage Δ

src/util/platform.ts
100.00% <0.00%> (+11.76%)
:arrow_up:

src/util/watch.ts
96.66% <0.00%> (+13.33%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Analyzer Feedback from IntelliJ

Version information

IDEA AI-202.76<IP_ADDRESS>51085
2.14.0-48.0.dev
AI-202.76<IP_ADDRESS>51085, JRE 11.0.8+10-b944.6842174x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1600x900

Thanks for filing an issue! The description contains no information so we're going to close this one. Please include details when filing a bug report.


Consumer get stucked in compacted topic

When replaying a compacted topic, with 20 partitions, the consumer get stucked in 5 partitions at some offsets, and don't succeed to read any more messages. All the other partitions were successully replayed...
I succeeded to fix this by manually increasing the consumer group offset for the problematic partitions, after I saw that it was stucked in an offset that was compacted and there was no messages for it in kafka.
Example:

offset
status
remark

1
read
message present

2
read
message present

3
read
message present

4
stucked here
deleted by kafka compaction

5

deleted by kafka compaction

6

deleted by kafka compaction

7

message present

So it works only after I moved the offset of the consumer group to 7.
Some remarks:

There is other offsets that was compacted by kafka and there was no issue there
The kafka console consumer succeeded to consume these messages continuously without any issue
I tried all kind of configuration changes on socket_timeout, connect_timeout and max_wait_time., but it did not help.

Version of Ruby: 2.3.5
Version of Kafka: <IP_ADDRESS>
Version of ruby-kafka: 0.5.4

Code of the consumer
require "kafka"

kafka = Kafka.new(["kafka1:9092", "kafka2:9092"])
consumer = kafka.consumer(group_id: "my-consumer")
consumer.subscribe("greetings")
trap("TERM") { consumer.stop }

consumer.each_message do |message|
  puts message.topic, message.partition
  puts message.offset, message.key, message.value
end

@Elyahou Hi, did the fix in https://github.com/zendesk/ruby-kafka/pull/625 work, or you still face this issue?

Thanks @nguyenquangminh0711 I tested against 0.7.3 version of ruby-kafka, and the bug was fixed :)

Thanks @nguyenquangminh0711 I tested against 0.7.3 version of ruby-kafka, and the bug was fixed :)

Thanks @nguyenquangminh0711 I tested against 0.7.3 version, and it seems this is now fixed :)


feat(API): Get CellxGene schema version this released is based on

This can be done using the CXGSchema class


CartoDB -> CARTO

Changes

to

Please CR carefully, this is a dangerous change! @gfiorav

Just kidding, 📦 it


GUI: Graphical Anomalies on Channel Selection

With version 0.1.4, I've noticed a couple of graphical anomalies.

Whenever you click on the "Chats" section to the left, it improperly clears the contents of the actively selected channel and also scrolls the channel to the top.  When you scroll the channel list back down, you can see the originally selected channel is still selected, but you have to click on the channel to get the contents back anyway
Whenever you click on a second channel and click back on the original channel when that original channel is full of content, it does some type of extremely distracting top-to-bottom wipe transition animation

I've attached a screen grab of both points, although it might be a little bit hard to follow due to the obfuscation I added for privacy purposes.  The key points are that I'm starting with the "random" channel selected which required scrolling the channel list down to bring it into view.  Then I click on "Chats" and you can see both the content disappear as well as the channel list automatically scroll back to the top.  Then, I scroll back down to show "random" is still highlighted followed by clicking on the "random" channel again to bring the contents back.  Finally, I click on the "bisonrelay" channel and click back on the "random" channel to show the aforementioned strange transition animation.

I've been able to fix the first issue pretty easily, though the second issue is causing a bit more an issue.  While we can retain scroll position between clicks, I'm struggling to figure out a good way to avoid seeing the scroll to position animation.

I believe what is causing it is that it appears to be reloading the text widget with all of the content and then setting its position to the bottom.
I highly suspect this because I noticed on the huge utf-8 test that I did in the bisonrelay channel means that every time I click on that channel in the GUI, it takes quite a while (as in several seconds) to load everything before it finally jumps to the bottom.
Also, I've noticed that as the amount of data in each channel grows, the effect becomes much more pronounced.
Given that, I expect a good fix (and one I've seen used in other chat-style software) is to only load a fixed amount of history and dynamically load more as the user scrolls up to the top until there is no more to load.


Don't use zip_release

I noticed the 0.3.0b2 release has a faulty zip asset.
There doesn't seem to be a point in using this format anyway.
Is there anything I missed? Do you add anything in there that's not in the repo?

Sorry to hear that the b2 release was faulty. I started to use the zip archive because when I started to develop this integration, I took a look at other integrations and the majority of the ones I took a look at had this included.
I simply didn't know that leaving it out is the better way to do it. Let me check how the release is working then :)

So I took a look at the integration_blueprint mentioned in the official HACS documentation. They also do zip releases there, but I saw that the release.yaml workflow looks different than mine.
The 0.3.0b2 release failed in the pipeline, and I uploaded the zip myself. So I know now that this doesn't work :D.
Is there any bigger advantage not using zip releases?
Currently I would go with adjusting the release.yaml workflow, and would test it out in the current dev branch.

I confirmed with Ludeeus (dev of HACS) what the advantage/benefit is for using zipped releases. His answer was "Nothing really". If not using it, it's as simple as creating a release/tagging a version. For things as minimum required version HACS uses the hacs.json from the tag that is being downloaded anyway.

I also think #12 is related to this. While probably a bug in HACS itself, it tried to download the zip for the main branch instead of the latest release (and accompanying tag). Of course a branch cannot have release assets like https://github.com/samuelspagl/ha_samsung_soundbar/releases/download/main/samsung_soundbar.zip.

I also think https://github.com/samuelspagl/ha_samsung_soundbar/issues/12 is related to this. While probably a bug in HACS itself, it tried to download the zip for the main branch instead of the latest release (and accompanying tag). Of course a branch cannot have release assets like https://github.com/samuelspagl/ha_samsung_soundbar/releases/download/main/samsung_soundbar.zip.

Yeah I also think that that happened.
But so first of all, thanks for speaking to Ludeeus and clarifying this! Just for my understanding, when changing this, I would just do a release, without attaching an additional .zip archive to it, and HACS is just doing all the magic. Right?
If the experimental version is safer, we can also already use that one.

Yes, release makes a tag, custom_components gets pulled for the tag ref. Another idea Ludeeus had was because there was no official release yet (a pre-release doesn't count) at the time users added your custom repo. In that case it would also fail to find the latest release and pull it. The experimental version is up to the user, nothing a publisher can do about it.

Okay so from my point of view, we can try that out.
Could you please add a Changelog entry and bump the version? I would merge it afterwards.