add basic plotting utilities

This PR will allow plot(enmap) to behave properly, with some reasonable defaults. It also includes a planck colorscheme taken from pixell. Since it is a well isolated part of the package, I made it a submodule.

Codecov Report

Merging #14 (7548877) into main (4f203a8) will decrease coverage by 7.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
- Coverage   67.94%   60.91%   -7.03%
==========================================
  Files           2        3       +1
  Lines         234      261      +27
==========================================
  Hits          159      159
- Misses         75      102      +27

Impacted Files
Coverage Δ

src/plot.jl
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

Once this is merged, I will put this package on the Julia package registry and tag 0.1. I want this as a dep for XGPaint to make some foreground maps!

sorry it took me a while to get it merged...

@guanyilun this is great, the plots look amazing!
using Pixell, Plots
shape, wcs = fullsky_geometry(π/180)
m = Enmap(randn(shape), wcs)
plot(m)

Thanks! For future reference, to use the planck colormap as we often do, use
register_colors!()
plot(m, color=:planck)


Support for number of event streams

Fixes #7515
I started creating a unit test for it and noticed some steps have this attribute set to None (I was expecting it to be 0..) so this is a non-working version.
BTW, @ericvaandering I didn't notice you started implementing it at CMSSW level in #7603.
I'll have a look at your PR, and then we can merge that and rebase this one and resume this coding.

My tests haven't finished yet because there seems to be a problem with the ITB pool. Nonetheless, the specs look fine and it's ready for a review (I'm updating two templates in the other PR).


Perform state reads synchronously, avoid transactional writes

Motivation
Metrics revealed that after introducing the state component, it became the bottleneck for checkpointed sync:

Using perf + inferno revealed that we spend a lot of time on locking:

However, we already use an actor model with message passing for state queries, so all queries are processed in one thread and the only reason writes have to be transactional is that we defer reads to returned futures.
Solution
Perform reads synchronously and remove use of the transactional sled API, significantly improving performance.

(The legend in the second panel of the grafana screenshot is cut off, but it's 10s windows instead of 1s windows.  Notice that the rates line up, indicating that we propagate backpressure properly)

Testing the intermediate commit suggests that the observed slowdown was related to contention, not to use of the transactional API.  So let's keep the transactional semantics, which give us other guarantees that we care about (like better integrity in case of crashes, etc).


The filter menu does not scroll on the mobile device

On mobile devise I can't scroll till the search button.
Expected behavior
Scroll all of the filter menu
Screenshots

iPhone xs
Browser Brave, Chrome
Version: latest

Gemfile
   arctic_admin (4.2.3)
   activeadmin (2.14.0)

i know this bug since a long time but i don't know how to fix it

@cprodhomme could you check it? https://github.com/cprodhomme/arctic_admin/pull/114

i have done a new version with this fix : https://rubygems.org/gems/arctic_admin/versions/4.2.5


Fix up the docs for external contributors

As it stands the contributions docs are 1) slightly outdated and 2) entirely focused on internal contributors. I guess we should fix that

@muursh Almost forgotten

"almost"


Implement $addFields/$set aggregation pipeline stages

After #2590 and #2165

There are references to this issue in both tests and documentation


unable to find history of mac_address in cattle

While debugging a networking problem when an ARP entry seemed to flap for few minutes, I wanted to find out which container had the MAC address. But I couldn't find this information in the database. The NIC table had purged entries but the MAC address was set to NULL.
Storing this historical information is important both for audit and debugging purposes.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


How to return an authority response

Hello,
I am trying to use dnsd to return authority (SOA) record, based on the host in the question.
For example, if, the query is for host in *.sub.domain.com, and local dnsd serves domain.com, I want to redirect the client to another dnsd instance, which serves sub.domain.com.
Tried several ways, like:
type: "SOA",
data:{ 'mname': "ns1.sub.domain.com"
, 'rname': "info.domain.com"
, 'serial':<PHONE_NUMBER>
, 'refresh': 10000
, 'retry'  : 100
, 'expire' : 100
, 'ttl'    : 300
},
or
res.authority.push(["ns1.sub.domain.com","info.domain.com",<PHONE_NUMBER> ,10000, 100, 100, 300]);
In the first case I got a valid response, but the Authority section is empty, in the second I get an error:
Error processing request:TypeError: Cannot read property 'replace' of undefined
Any help will be highly appreciated.
Best,
Kiril.

Getting the same error. Any updates on this?


Web Chat not working: 404 NotFound issues

After a successful deployment the Web Chat says "not sent" below every message. The Web Chat channel shows issues with message: "There was an error sending this message to your bot: HTTP status code NotFound".
App Service is running and log streams shows the 404.
After some time I noticed the ".deployment" file that is created with command "az bot prepare-deploy". I changed the property "Copy to Output Directory" value to "Copy Always" for this file in Visual Studio, built, zipped, deployed and everything is working.
Just leaving this here in case someone runs into the same issue.

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

ID: 9d5bd35d-3178-42cd-2893-3b6a4b7a94ce
Version Independent ID: 1545fd44-d471-d947-f94d-4b5e8d6e853f
Content: Tutorial to create and deploy a basic bot - Bot Service
Content Source: articles/v4sdk/bot-builder-tutorial-basic-deploy.md
Service: bot-service
Sub-service: sdk
GitHub Login: @ivorb
Microsoft Alias: v-ivorb

Also having the same issue after deploying. Messages I send in the Web Chat result in  "couldn't sent. retry" and I get the same error message as @andreschort: "There was an error sending this message to your bot: HTTP status code NotFound". I used the JS / yeoman generator, and I don't have a .deployment file at all in my project...

@samanthagmccormick @waqarghani @andreschort - I have asked one of the testers to look into it.

Thank you so much :)

@samanthagmccormick @waqarghani @andreschort - Which version of Azure CLI are you using? ( Make sure you have 2.0.64 version).
If the version being used is 2.064 and still facing the issue, please specify more details about the error.
@samanthagmccormick - When you use the command prepare-deploy, after pointing to the right directory(in cmd), you will find web.config file created at the location you have pointed. ( For C# it is .deployment file. For JS and TS it is web.config tha gets created)

@samanthagmccormick - When you use the command prepare-deploy, after pointing to the right directory(in cmd), you will find web.config file created at the location you have pointed. ( For C# it is .deployment file. For JS and TS it is web.config tha gets created)

@nstejaswini here is some more info if it helps. I was  finally able to get everything to work after trying the deployment steps for the 4th time and making 2 changes.
My az cli version is 2.0.64. Yesterday, I was using node version 8.11.3, and today tried switching node versions to 10.14.1 after combing through the template-with-new-rg.json file and noticing that it uses 10.14.1:

I also made another change based on this section:

Yesterday, I took the project folder containing index.js, zipped it up, and then ran the az webapp deployment ...  script from outside of the project folder. This to me is a normal way to go about it and maybe others did this same thing. But, I re-read the section above another time today and decided to go into the project folder, select all its contents and zip those, then make sure I ran the command from inside the project folder where the zipped folder was,  rather than outside it. I think that might be what the section above asks for, but it wasn't intuitive for me to do it that way, even having read the above section.
So -- I'm not sure if either upgrading to node 10.14.1 solved the problem OR changing where I zipped
and ran the deployment command, but one of those  fixed it for me and I am finally able to test chat from inside my bot's Test Web Chat in the Azure Portal.

@samanthagmccormick That's what the document says. The project file with all the components (make sure that the  index.js/ .csproj  and web.config/.deployment file are present) should be zipped together. Your were facing the error because of this only. The node version was not the problem. Because I have tested it with the node version 8.12.0, it worked fine.

I've added another detail to explain that in the note referenced above - it appears to not be due to the node version, and instead due to the location of zipping. Hope that makes it clearer!


[buck-yeh-bux] Update to 1.6.6

[New] C_UnicodeIn::encoding()
[Change] Pass std::basic_string_view<T> arguments by value, not by reference, to ctor of bux::C_MBCStr
[Change] Rehaul bux::fittestType() in C++20 - concept lite & if constexpr
[Change] Add code page 951 (Big5 with HKSCS-2001) as one of encoding candidates to test in bux::C_UnicodeIn
[Change] Forbid r-value string instance as ctor parameter of bux::C_IMemStreamT<>

What does your PR fix?
Nothing

Which triplets are supported/not supported? Have you updated the CI baseline?
Supported

x64-windows
x64-windows-static
x64-windows-static-md
x86-windows
x86-windows-static
x86-windows-static-md

No

Does your PR follow the maintainer guide?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

@buck-yeh Is this PR ready to merge?

Yes, definitely
Frank @.***> 於 2022年6月16日 週四 上午10:43 寫道：

@buck-yeh https://github.com/buck-yeh Is this PR ready to merge?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vcpkg/pull/25254#issuecomment-1157170124,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACL7ZGGXYGIQJTM47QNUK3VPKIENANCNFSM5Y4CJMAA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Change arguments, return values

Is it possible to change arguments/return values using this framework?

Hi,
at the moment Anathema doesn't support that specific feature. In the next release I can implement the possibility to replace the method with a specific one, but I'm not able to give you a date for the release.
If you are in a hurry, you can try to have a look at the Harmony project, which behaves similar to Anathema with the difference that it places a memory hook instead of modifying the MSIL code to compile.


Change error message for over 18 checkbox not being selected

From #302

@krand7 Here's a temporary fix for formatting the error messages for the user:
              - resource.errors.messages.each do |key, msg|
                - if key == :over_eighteen
                  %li= msg.join(", ")
                - else
                  %li= "#{key.to_s.titleize} #{msg.join(", ")}"

Rails, by default, appends the name of the field to the beginning of the message in errors.full_messages, even for custom messages.
Our definition:  user.validates :over_eighteen, inclusion: { in: [true], message: "You must be over 18 years of age to sign up." }),
was still causing "Over eighteen" to be appended to beginning of this message.
This is something to keep in mind when we make a consolidated solution for displaying form validation errors.


Publish docker image to public registry

Would you consider publishing the docker image publicly?
Or is that something you don't like and rule out in advance?
e.g. GitHub's ghcr.io (Working with the Container registry) or somewhere else..
Your effort is highly appreciated. Thank you for your work on this amazing relay :rocket:

I try to keep the DockerHub repository up-to-date here: https://hub.docker.com/r/scsibug/nostr-rs-relay (there is a link in the README as well).
Is that what you are looking for, or are there other hosting repos like GHCR that would make sense to publish as well?

I try to keep the DockerHub repository up-to-date here: https://hub.docker.com/r/scsibug/nostr-rs-relay (there is a link in the README as well).

Damn.. I don't know how I could have missed that.. please excuse my sloppiness.

Is that what you are looking for, or are there other hosting repos like GHCR that would make sense to publish as well?

No.. not worth the extra effort, I think. DockerHub is perfectly fine.


Change JSON endpoint for google/cloud/storage.

The endpoint needs to change from www.googleapis.com/storage/v1 to storage.googleapis.com/storage/v1.
Note that this is currently blocked because the new endpoint is not available yet.

@manish-qlogic this is the bug I was talking about today, would be a good task after you finish the current one.

A more complete description of this change:

OLD
NEW

www.googleapis.com/storage
storage.googleapis.com/storage

www.googleapis.com/upload/storage
storage.googleapis.com/upload/storage

www.googleapis.com/download/storage
storage.googleapis.com/download/storage

www.googleapis.com/batch/storage
storage.googleapis.com/batch/storage

www.googleapis.com/resumable/upload/storage
storage.googleapis.com/resumable/upload/storage


[jasmine-enzymye]: Matcher calls generate runtime errors in Typescript project

Description
After installing the jasmine-enzyme module and @types/jasmine-enzyme into an existing
project using Karma I'm running in to the following error when the tests are run:

Here is the stack in Chrome Dev Tools:

Steps to reproduce

git clone git@github.com:medington/jasmine-enzyme-ts.git
cd jasmine-enzyme-ts
npm install
npm run test

Additional Notes

That is a bare bones project with just the test module and what is needed to run it installed.
The git history has the stages of stuff that works (raw Jasmine, Enzyme only).
Interestingly enough, I have this working using more or less the same version of all the packages in a project that was created using:

create-react-app react-enzyme-test --scripts-version=react-scripts-ts

I've tried to narrow down what is different between that project and this one but no luck so far.

This may not be related, but when I setup the project I was initially getting an error on an import statement in the test when using the  the default tsconfig.json with the "esModuleInterop": true  option enabled.
import * as Adapter from "enzyme-adapter-react-16";
searching on that error led me to this Typescript issue: --esModuleInterop changes meaning of declaration. When I changed the import to instead be:
import Adapter = require("enzyme-adapter-react-16");

That changed the error to be a little different:

Again, probably not related, but the esModuleInterop option is one of the defaults when using tsc init to initialize a new config file.

That error in the last comment means you tried to pass a not-enzyme object to an enzyme-matcher assertion.
Something like expect({foo: 'bar'}).toHaveState('foo', 'bar) would throw an error like that. What is happening  in your src/index.spec.tsx:57 ?

Hi @blainekasten thanks for the message. There is no line 57 in the file, I believe that's number corresponds to a file output by webpack. The test is as simple as I could make it, the file is:
https://github.com/medington/jasmine-enzyme-ts/blob/master/src/index.spec.tsx
It's the original issue I'm more concerned with getting resolved though. That one prevents me from using the enzyme matchers with typescript.

@medington I'll try to be as helpful as I can but I don't use jasmine or ts in my day job. Does this comment and export give you any guidance?
https://github.com/FormidableLabs/enzyme-matchers/blob/master/packages/jasmine-enzyme/src/index.js#L74-L80

@medington -- I cloned your repo and straight up master works on my machine with:
  Jasmine/Enzyme Sanity Tests
    ✓ says hello via mount with matcher
    ✓ says hello via renderIntoDocument
    ✓ says hello via mount

Chrome 64.0.3282 (Mac OS X 10.12.6): Executed 3 of 3 SUCCESS (0.039 secs / 0 secs)
TOTAL: 3 SUCCESS

I made this modification because I think it's closer to what you want:
diff --git a/src/index.spec.tsx b/src/index.spec.tsx
index 9b7b86a..a2f3247 100644
--- a/src/index.spec.tsx
+++ b/src/index.spec.tsx
@@ -4,7 +4,7 @@ import * as TestUtils from "react-dom/test-utils";
 import * as Enzyme from "enzyme";
 // See the note in the tsconfig.json file about this import
 // import * as Adapter from "enzyme-adapter-react-16";
-import Adapter = require("enzyme-adapter-react-16");
+import {default as Adapter} from "enzyme-adapter-react-16";
 import jasmineEnzyme from "jasmine-enzyme";

 Enzyme.configure({ adapter: new Adapter() });

And that also passes.
Also, side note -- is "cheap-module-eval-source-map" recommended in Karma tests? Source maps are notoriously fickle, and that one in particular seems weird to place in a test because real code doesn't go in your test, instead a bug eval(REAL_CODE_AS_STIRNG) is outputted IIRC.
Hope that helps!

@blainekasten Thanks. I got my test to work.  Your tip about the 2nd error I posted was because my code was incorrect:
  it('says hello via mount with matcher', () => {	   it('says hello via mount with matcher', () => {
     jasmineEnzyme();	     jasmineEnzyme();
     const hello = Enzyme.mount(<Hello/>);	     const hello = Enzyme.mount(<Hello/>);
    expect(hello.text()).toHaveText('hello');	+    expect(hello).toHaveText('hello');
   });

The last line should have been just expect(hello) and not expect(hello.text()). However I wasn't seeing that error initially as the "TypeError: jasmine_enzyme_1.default is not a function" function error was preventing that call from ever being made.
For anyone else following this, I pushed updates to my test project here with comments:
https://github.com/medington/jasmine-enzyme-ts/commit/42d88664211764e5dfbef5ce3ad3a28ee2c55f9f
At this point my feeling is that the documentation here:
https://github.com/airbnb/enzyme/blob/master/docs/guides/migration-from-2-to-3.md
Needs to either be updated or include a note regarding the way the adapter is imported when using Typescript the documentation I pointed at in my earlier message. Should I log an issue with the project?

@medington -- actually, I just tried:
import Adapter from "enzyme-adapter-react-16";

and that worked fine too. Are there any problems import-wise still on your end, or just with the assertions/substantive code at this point?

Hi @ryan-roemer - Thank you very much for looking into this issue!

@medington -- I cloned your repo and straight up master works on my machine with:

That's because I had just pushed changes to fix it. If you checkout the "failure" tag or clone that directly it will fail (I updated my steps to reproduce to indicate this).
Just reverting the import to:
import Adapter from "enzyme-adapter-react-16";
at the head of master will also work because the tsconfig.json entry is in there:
"esModuleInterop": true,
If you comment that out and try again you should see the error. Better yet, checkout the "failure" tag.

Also, side note -- is "cheap-module-eval-source-map" recommended in Karma tests? Source maps are notoriously fickle, and that one in particular seems weird to place in a test because real code doesn't go in your test, instead a bug eval(REAL_CODE_AS_STIRNG) is outputted IIRC.

Tell me about it. I've struggled mightily with different source type maps. I've experimented with most all of the different types haven't found any type that works as well with unit tests as I would like. I think that one works when I debug a unit test in Chrome Dev Tools but if you can suggest a better setting to use I'd love to hear it!
I'm still thinking that there needs to be some sort of documentation change made regarding the adapter import syntax. If you read the Typescript Module Docs it states:

When importing a module using export =, TypeScript-specific import module = require("module") must be used to import the module.

For reference, the react 16 adapter index.d.ts contains this:
// Type definitions for enzyme-adapter-react-16 1.0
// Project: https://github.com/airbnb/enzyme
// Definitions by: Tanguy Krotoff <https://github.com/tkrotoff>
// Definitions: https://github.com/DefinitelyTyped/DefinitelyTyped
// TypeScript Version: 2.6

import { EnzymeAdapter } from 'enzyme';

declare class ReactSixteenAdapter extends EnzymeAdapter {
}

declare namespace ReactSixteenAdapter {
}

export = ReactSixteenAdapter;

This issue should probably be closed. If there is any change to be made it's to the documentation for the Jasmine enzyme docs.


fix(component) keep-alive

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[x] Other, please describe: optimize performance, reduce unnecessary attribute traversal

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[ ] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
Object.keys(data) // ["key"]
data['key'] = null
Object.keys(data) // ["key"]
delete data['key'] // Reduce unnecessary attribute traversal
Object.keys(data) // []

这些 key 很可能被再次创建，设为 null 更合理，避免频繁更改底层数据结构。


Fails at first token

Error @ 'applicationCollection
usage = ['Generic Desktop', 'Gamepad']

    applicationCollection' (L0) WAR99F361C9: Invalid token.

I get this error in the last 4 versions trying any sample. Haven't found a version that works yet

What are your console parameters?  Was the gamepad.wara file modified or transformed with a different encoding?
My output with latest binaries
Z:\Waratah-Published>WaratahCmd.exe -s gamepad.wara
Reading from file 'Z:\Waratah-Published\gamepad.wara'
Creating output file 'Z:\Waratah-Published\gamepad.h'
Successfully created output file 'Z:\Waratah-Published\gamepad.h'
Successfully generated descriptor file 'Z:\Waratah-Published\gamepad.h'

HID Usage Tables: 1.4.0
Descriptor size: 48 (bytes)
+----------+-------+-------------------+
| ReportId | Kind  | ReportSizeInBytes |
+----------+-------+-------------------+
|        1 | Input |                 2 |
+----------+-------+-------------------+

It was not modified, but it must be a different encoding, because when I download gamepad.wara it works. It also works copied from github copy button into notepad and saved. It fails when saved from vim with git bash tested on Windows 11. If I don't create the file with vim in git bash, but go in the existing one and save, it also works. What steps can I take to get more information for you to figure out what's going on?

Sounds like doing a binary diff of the two files (working, non-working) would reveal the encoding differences.  I don't have a better suggestion for you :(


Allow using YAML configuration file with run_docker

This will allow using scripts like this:
#!/usr/bin/env bash

# Uncomment for debugging
# set -o xtrace

set -eo pipefail  # Exit the script if any statement returns error.

SCRIPT_DIR="$( dirname "$(readlink -f "$0")" )"

export CONTAINER_NAME="aries_issuer"
export NETWORK_NAME="aries-mediator-service_mediator-network"
export PORTS="8002 11002"
export ARG_FILE="${SCRIPT_DIR}/cfg_issuer.yml"

../aries-cloudagent-python/scripts/run_docker start

I find working with yaml files easier/faster than very, very long command line when testing and debugging (because I can simply comment out some configs and uncomment others at the same time).

Can someone investigate and comment on the integration test failures? Solar flares?

Can someone investigate and comment on the integration test failures? Solar flares?

I'm guessing some kind of environment issue, I've restarted the integration tests to be sure.
There aren't any changes in this PR that should affect any of the tests


DetermineProjectsToBuild action

Separate calculating AL-Go projects to build and project dependencies into a separate action, DetermineProjectsToBuild (please comment on the name).
Calculate buildDimensions to use in the Build job. The current dimensions are AL-Go project and build mode. This allows to have build modes per project.
Fix issue with thisBuild artifacts

Pending:

[x] Tests (there are some, but need to add more )
[x] Propagate template changes to AL-Go-AppSource and other workflows
[x] Address CalculateArtifactsNames usage in NextMinor, NextMajor and Current workflow

Maybe some release notes?

Two issues I have encountered.
The Pull Request Build after updating AL-Go System Files doesn't build anything (when multiproject)
https://github.com/BusinessCentralApps/buildorder/actions/runs/4348567214
When single-project - it does.
https://github.com/BusinessCentralApps/BingMaps.PTE/actions/runs/4351096290
Since the PR Build runs on target - then nothing actually changed, so that is probably correct - maybe we should detect this in pregate check or maybe when detecting that no projects are to be build in initialize, we could add a build summary step explaining that no projects are changed - skipping all builds.
On the PR build above on single project, no BuildOutput artifacts was created.
Testing whether BuildOutput artifacts are created by a Multi-project PR build here:
https://github.com/BusinessCentralApps/buildorder/actions/runs/4351407874

The Pull Request Build after updating AL-Go System Files doesn't build anything (when multiproject) https://github.com/BusinessCentralApps/buildorder/actions/runs/4348567214

Can I see the PR itself? Is it this one
I am asking because the PR adds new action in the Initialization job, Determine Projects To Build.

But in this case, no projects were picked up because the of the modified files:

5 modified file(s): .github/workflows/CICD.yaml, .github/workflows/Current.yaml, .github/workflows/NextMajor.yaml, .github/workflows/NextMinor.yaml, .github/workflows/PullRequestHandler.yaml

So, this was the "follow-up" PR.

When single-project - it does.
https://github.com/BusinessCentralApps/BingMaps.PTE/actions/runs/4351096290

Based on the time, I assume the PR is this one
The PR changes the template and the worfklows, but the workflows will run from the main branch. Hence, the result.
It is interesting, because the somehow it detects changes in the workflow but it doesn't run them:

Based on the time, I assume the PR is this one

Yes, you can also see the PR build # and the PR # in the list:

But in this case, no projects were picked up because the of the modified files:

But wouldn't you expect that if CICD.yaml (when running CI/CD), PullRequestHandler.yaml (when running PR Build) and/or AL-Go-Settings.json was changed - we should re-build all?

But wouldn't you expect that if CICD.yaml (when running CI/CD), PullRequestHandler.yaml (when running PR Build) and/or AL-Go-Settings.json was changed - we should re-build all?

I would, but in this case only workflow files were modified:

5 modified file(s): .github/workflows/CICD.yaml, .github/workflows/Current.yaml, .github/workflows/NextMajor.yaml, .github/workflows/NextMinor.yaml, .github/workflows/PullRequestHandler.yaml
(I assume that's because even if we run the build, it will run without the changes anyway.)

A project is built only if there are modified files in its .AL-Go folder or any of the app folders.
All projects are built is there are modified files, matching .github/*.json.
There are other cases but none of the criteria is met, so technically there are no projects to build.

But wouldn't you expect that if CICD.yaml (when running CI/CD), PullRequestHandler.yaml (when running PR Build) and/or AL-Go-Settings.json was changed - we should re-build all?

I would, but in this case only workflow files were modified:

5 modified file(s): .github/workflows/CICD.yaml, .github/workflows/Current.yaml, .github/workflows/NextMajor.yaml, .github/workflows/NextMinor.yaml, .github/workflows/PullRequestHandler.yaml
(I assume that's because even if we run the build, it will run without the changes anyway.)

A project is built only if there are modified files in its .AL-Go folder or any of the app folders. All projects are built is there are modified files, matching .github/*.json. There are other cases but none of the criteria is met, so technically there are no projects to build.

Got it - but shouldn't we add a criteria to build all if cicd.yaml and/or pullrequesthandler.yaml was changed?

Got it - but shouldn't we add a criteria to build all if cicd.yaml and/or pullrequesthandler.yaml was changed?

We can, but even if these files are changed, the build would pick up the old ones in the case of a PR (target branch). So not much value here.
In any other case (CICD, Current, etc.) all projects are built anyway.
If we ever change the trigger on "Pull Request Build" to be pull_request (not pull_request_target) then a build-all is a must, if pullrequesthandler.yaml is modified in a PR.
What should we settle on?


[Flaky CI] [rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system] VM Live Migration with a live-migrate eviction strategy set [ref_id:2293] with a VMI running with an eviction strategy set with node tainted during node drain [test_id:2222] should migrate a VMI when custom taint key is configured

/triage build-officer
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4067/pull-kubevirt-e2e-k8s-1.18/1300469284215984128

Same failure seen again
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4236/pull-kubevirt-e2e-k8s-1.18/1309183957866123264


But, can we get at least the start of a docs/live-migration.md ? Some docs on how dirtying works, when it's cleared, client/API user expectations etc?

Sure, can I do it as a separate issue?

sure

sure

https://github.com/nutanix/libvfio-user/issues/557

@jlevon addressed your comments, please take another look.


tx

I can take this up

Hi @varun-doshi are you still working on it ?
If not, can I work on it  @tdelabro ?

@varun-doshi is focussed on #65 for new. It takes most of his time


The problem of shoebill

Hi. I was using Shoebill  for about a year and really like it. However, I personally think that the project is unnecessarily too complex, there are a lot of sub-projects, dependencies, documentation, and it is really hard to get started with the plugin.
My idea is to simplify the project on a single github repo, and offer it as a standard Java library published on the maven central or in gtaup repo as well, so all you need is to add a dependency to maven/gradle or the shoebill jar to classpath.
So, for example, imagine a repo at github/Shoebill/Shoebill:
plugin/ -- The plugin code
api/ -- A single maven project
Then, the documentation could be in a single README.md, DOC.md, or even on /wiki.
All issues on /issues, or add /releases where you could download Shoebill/Shoebill.dll and all needed folders. So, to get started you will have to:

Install JDK
Add to your java project a 'net.gtaun:shoebill:1.0' or download the raw jar
Put your gamemode jar on shoebill/jars or use the existing maven support
Run startup.sh or link your PATH to the JDK directory

This way will make the project much easier to understand, to contribute, to maintain and to get started.
Of course I dont want to rewrite shoebill from scratch. But to merge all projects (shoebill-util, shoebill-api, shoebill-runtime, etc...) into a single "core" project. And, start simplifying/refactoring all the existing codebase if necessary.
There are a growing number of people interested in writting gamemodes for Java, C#, PHP, JS, etc.. because PAWN simply isn't that powerfull. So, this project can grow a lot.
Of course this is a personally mean, I would like to know your opinion Marvin.

Hi,
thanks for your suggestions. I think most of your ideas make sense and I will keep them in mind for future updates. It might be too late to make such a radical change and maybe even impossible due to Shoebill's current architecture and how things are internally handled. And I am not sure if it is worth making such modifications, since SA:MP is not really extremely active anymore.
If I have any more questions, I will ask you here.
Thanks.


nullptr problem

Cloned 374664b and tried to build Box2D but I got the following compile error:
"error: ‘nullptr’ was not declared in this scope"
I then run cmake enabling c++11 (-DCMAKE_CXX_FLAGS=-std=c++11) and the problem was fixed.

Yes, it seems this was reported elsewhere recently too, over at issue #414. Pull request #412 seems to fix this issue, it's currently pending. Could you apply #412 and see if this fixed your problem? One search through the Box2D source shows that the patch at #412 removes the only instance of nullptr.

I'm planning to use other C++11 features, such as override.


Fix/form validation

Fixes Bug #97
This PR fixes the following issues:

Sending Empty Form on Clicking Send/(submit) Button.

Changes proposed

Added states to store name, email, message values using 'onChange' eventListener.
Added dynamic form messege below send button (Earlier it displayed only success message, now it displays both
success and error message.)

Here comes all the changes proposed through this PR

Check List (Check all the boxes which are applicable)

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

Screenshots and video
https://github.com/NSCC-BPIT/NSCC-BPIT-Website/assets/53823257/83e57253-16d5-4ff5-a0d9-8006225879e5

Hi,
I haven't checklisted few options because:

I don't have much knowledge about tests, i simply did npm test and the outcome was No tests found related to files changed since last commit. (so, i am not sure)
I havn't changed/updated any documentation, because i didn't find any thing important to be changed. Please tell if needed.

Thanks


Windows vm detect vis 'port connector'

In windows you can use powershell/wmi to get 'ports'
On bare metal:
--- CODE -- (as is not formatting very well)
PS C:\Users\admin> powershell -Command "Get-WmiObject Win32_PortConnector"
Tag                         : Port Connector 0
ConnectorType               : {61}
SerialNumber                :
ExternalReferenceDesignator : PS2Mouse
PortType                    : 14
--- CODE --
On VM this return empty value

I really like this idea, I'm quite busy today but I'll definitely try to implement this whenever I have the time. Thanks! :)

Hey just wanted to make my contribution as for my windows 10 installation on port 0 i get the value of 0 whilst not being in a vm or any altercations to make it look like one
C:\Users\Monket>powershell -Command "Get-WmiObject Win32_PortConnector"                                                                                Tag         : Port Connector 0
ConnectorType               : {0}
SerialNumber                :
ExternalReferenceDesignator : HDMI1_DP
PortType                    : 0
Please could you share some system info unusual-suspect

Hey just wanted to make my contribution as for my windows 10 installation on port 0 i get the value of 0 whilst not being in a vm or any altercations to make it look like one
C:\Users\Monket>powershell -Command "Get-WmiObject Win32_PortConnector" Tag : Port Connector 0 ConnectorType : {0} SerialNumber : ExternalReferenceDesignator : HDMI1_DP PortType : 0
Please could you share some system info unusual-suspect

@unusual-aspect

In windows you can use powershell/wmi to get 'ports'
On bare metal:
--- CODE -- (as is not formatting very well) PS C:\Users\admin> powershell -Command "Get-WmiObject Win32_PortConnector"
Tag : Port Connector 0 ConnectorType : {61} SerialNumber : ExternalReferenceDesignator : PS2Mouse PortType : 14 --- CODE --
On VM this return empty value

Thanks a lot for your contribution, @unusual-aspect !
We have verified that your technique can be used as an indication of a VM and have added it under the ‘connection_ports’ function, in the commit https://github.com/kernelwernel/VMAware/commit/3117cd5fc82a66b858e9d3abff231b16d1a9c994, giving you credits. We have modified your technique a bit to use the Windows Management Instrumentation API directly instead of invoking it through PowerShell for performance results.
Thank you very much, I proceed to close this issue


Broken link for help

Steps to reproduce

Open menu Help -> Online help
or:

Press F1

Expected result
Help page opens
Actual result
Page not found.
Note: the URL is https://poedit.net/trac/wiki/Doc?fromVersion=3.5.2

This is website update gone bad, now fixed. Thanks for alerting me!


Inheritance & IndexerMeta + (Filename, ID and timestamp) & Content-Type

open GeoRocket verticles for inheritance
add filename, id and timestamp as IndexMeta data
read the content type on post and use it to make a decision between the import format

add a fallback for the content type if the client forget to send one, the type will be guessed by the file magic number and the file content

extract start / stop methods from the indexer indexing and deleting methods

Many changes in just one PR. Can you split it up maybe?


Add Visual Studio code flatpak as dependency

I am going to get into Unreal but it fails to see the Visual Studio code flatpak.
I need the flatpak to work with the editor.
Native binary works but not the desired use.

The intention is to develop for windows and be able to use the C++ project template on Linux, here is the link  to prepare the build for this.


Prevent sending messages to an non NEO-address

https://github.com/kokahunter/neochat-local/pull/11


Adding travis.yml

This change is

This PR is on hold until the ast2json refactorings are merged in


Racer doesn't discover Vec::contains

fn main() {
    let v: Vec<u64> = Vec::new();
    v.
}

Racer doesn't discover the .contains method here.

#334 ?
From libcollections/vec.rs
impl<T> ops::Deref for Vec<T> {
    type Target = [T];
    fn deref(&self) -> &[T] {
        ...


Support for Styled-Components

I wonder if there is support for styled-components or there are plans to support it.
I'd be amazing to use themeProvider with NativeBase!

thank you for response! When can I found development branch?

@himanshu-satija Hi Did you add support of styled compoennt for nativebase
native-base version  : 2.3.1
When I use
const NavbarRightView = styled.Segment`
  flex:0.2;
`

It is throwing error

@swaroopa94 try this
const NavbarRightView = styled(Segment)`
  flex:0.2;
`


Dear friend ,  I have a question

When I upload ipa to appstore ，fastlane always show “Does the Preview on path './fastlane/Preview.html' look okay for you?” and let me to select.
hhhh ,  it let me can't take it easy to go to the toilet .
so , how can i automatic skip or let let it remember me before choice.
thanks very much .

Hi, @Wbqqqq
Please check #10078 for more information
You can set the param force=true if you are using delivery
Doc: https://docs.fastlane.tools/actions/deliver/

@Wbqqqq Please change the issue title to something more explicit and related with the issue.

thanks , @marksiu .


bug on google colabs code

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
Fine-tune model via Command Line
I didnt do anything  change , just tried as it is

/content/LLaMA-Factory
2024-05-18 12:35:28.953301: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-05-18 12:35:28.953353: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-05-18 12:35:28.954649: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-05-18 12:35:30.175448: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
05/18/2024 12:35:33 - WARNING - llamafactory.hparams.parser - We recommend enable `upcast_layernorm` in quantized training.
05/18/2024 12:35:33 - INFO - llamafactory.hparams.parser - Process rank: 0, device: cuda:0, n_gpu: 1, distributed training: False, compute dtype: torch.float16
/usr/local/lib/python3.10/dist-packages/huggingface_hub/file_download.py:1132: FutureWarning: `resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.
  warnings.warn(
tokenizer_config.json: 100% 51.1k/51.1k [00:00<00:00, 66.3MB/s]
tokenizer.json: 100% 9.09M/9.09M [00:01<00:00, 6.23MB/s]
special_tokens_map.json: 100% 459/459 [00:00<00:00, 2.69MB/s]
[INFO|tokenization_utils_base.py:2087] 2024-05-18 12:35:37,198 >> loading file tokenizer.json from cache at /root/.cache/huggingface/hub/models--unsloth--llama-3-8b-Instruct-bnb-4bit/snapshots/2950abc9d0b34ddd43fd52bbf0d7dca82807ce96/tokenizer.json
[INFO|tokenization_utils_base.py:2087] 2024-05-18 12:35:37,198 >> loading file added_tokens.json from cache at None
[INFO|tokenization_utils_base.py:2087] 2024-05-18 12:35:37,198 >> loading file special_tokens_map.json from cache at /root/.cache/huggingface/hub/models--unsloth--llama-3-8b-Instruct-bnb-4bit/snapshots/2950abc9d0b34ddd43fd52bbf0d7dca82807ce96/special_tokens_map.json
[INFO|tokenization_utils_base.py:2087] 2024-05-18 12:35:37,198 >> loading file tokenizer_config.json from cache at /root/.cache/huggingface/hub/models--unsloth--llama-3-8b-Instruct-bnb-4bit/snapshots/2950abc9d0b34ddd43fd52bbf0d7dca82807ce96/tokenizer_config.json
[WARNING|logging.py:314] 2024-05-18 12:35:37,601 >> Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
05/18/2024 12:35:37 - INFO - llamafactory.data.template - Replace eos token: <|eot_id|>
05/18/2024 12:35:37 - INFO - llamafactory.data.loader - Loading dataset identity.json...
Generating train split: 91 examples [00:00, 5377.99 examples/s]
Converting format of dataset: 100% 91/91 [00:00<00:00, 7138.91 examples/s]
05/18/2024 12:35:38 - INFO - llamafactory.data.loader - Loading dataset llamafactory/alpaca_gpt4_en...
 I am Llama-3, an AI assistant developed by LLaMA Factory. How can I assist you today?<|eot_id|>
label_ids:
[-100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, -100, 9906, 0, 358, 1097, 445, 81101, 12, 18, 11, 459, 15592, 18328, 8040, 555, 445, 8921, 4940, 17367, 13, 2650, 649, 358, 7945, 499, 3432, 30, 128009]
labels:
Hello! I am Llama-3, an AI assistant developed by LLaMA Factory. How can I assist you today?<|eot_id|>
config.json: 100% 1.15k/1.15k [00:00<00:00, 6.70MB/s]
[INFO|configuration_utils.py:726] 2024-05-18 12:35:49,628 >> loading configuration file config.json from cache at /root/.cache/huggingface/hub/models--unsloth--llama-3-8b-Instruct-bnb-4bit/snapshots/2950abc9d0b34ddd43fd52bbf0d7dca82807ce96/config.json
[INFO|configuration_utils.py:789] 2024-05-18 12:35:49,629 >> Model config LlamaConfig {
  "_name_or_path": "unsloth/llama-3-8b-Instruct-bnb-4bit",
  "architectures": [
    "LlamaForCausalLM"
  ],
  "attention_bias": false,
  "attention_dropout": 0.0,
  "bos_token_id": 128000,
  "eos_token_id": 128009,
  "hidden_act": "silu",
  "hidden_size": 4096,
  "initializer_range": 0.02,
  "intermediate_size": 14336,
  "max_position_embeddings": 8192,
  "model_type": "llama",
  "num_attention_heads": 32,
  "num_hidden_layers": 32,
  "num_key_value_heads": 8,
  "pretraining_tp": 1,
  "quantization_config": {
    "_load_in_4bit": true,
    "_load_in_8bit": false,
    "bnb_4bit_compute_dtype": "bfloat16",
    "bnb_4bit_quant_type": "nf4",
    "bnb_4bit_use_double_quant": true,
    "llm_int8_enable_fp32_cpu_offload": false,
    "llm_int8_has_fp16_weight": false,
    "llm_int8_skip_modules": null,
    "llm_int8_threshold": 6.0,
    "load_in_4bit": true,
    "load_in_8bit": false,
    "quant_method": "bitsandbytes"
  },
  "rms_norm_eps": 1e-05,
  "rope_scaling": null,
  "rope_theta": 500000.0,
  "tie_word_embeddings": false,
  "torch_dtype": "bfloat16",
  "transformers_version": "4.40.2",
  "use_cache": true,
  "vocab_size": 128256
}

05/18/2024 12:35:49 - INFO - llamafactory.model.utils.quantization - Loading ?-bit BITSANDBYTES-quantized model.
🦥 Unsloth: Will patch your computer to enable 2x faster free finetuning.
Traceback (most recent call last):
  File "/usr/local/bin/llamafactory-cli", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.10/dist-packages/llamafactory/cli.py", line 65, in main
    run_exp()
  File "/usr/local/lib/python3.10/dist-packages/llamafactory/train/tuner.py", line 34, in run_exp
    run_sft(model_args, data_args, training_args, finetuning_args, generating_args, callbacks)
  File "/usr/local/lib/python3.10/dist-packages/llamafactory/train/sft/workflow.py", line 34, in run_sft
    model = load_model(tokenizer, model_args, finetuning_args, training_args.do_train)
  File "/usr/local/lib/python3.10/dist-packages/llamafactory/model/loader.py", line 124, in load_model
    model = load_unsloth_pretrained_model(config, model_args)
  File "/usr/local/lib/python3.10/dist-packages/llamafactory/model/utils/unsloth.py", line 39, in load_unsloth_pretrained_model
    from unsloth import FastLanguageModel
  File "/usr/local/lib/python3.10/dist-packages/unsloth/__init__.py", line 113, in <module>
    from .models import *
  File "/usr/local/lib/python3.10/dist-packages/unsloth/models/__init__.py", line 15, in <module>
    from .loader  import FastLanguageModel
  File "/usr/local/lib/python3.10/dist-packages/unsloth/models/loader.py", line 15, in <module>
    from .llama import FastLlamaModel, logger
  File "/usr/local/lib/python3.10/dist-packages/unsloth/models/llama.py", line 27, in <module>
    from ._utils import *
  File "/usr/local/lib/python3.10/dist-packages/unsloth/models/_utils.py", line 60, in <module>
    import xformers.ops.fmha as xformers
ModuleNotFoundError: No module named 'xformers'

Expected behavior
No response
System Info
No response
Others
No response

Hi, even I too encountered this issue but I thought it was a local one but it seems you too have faced the same error. My best guess to why this might be occurring is due to this line
!pip install --no-deps xformers<0.0.26

as the logs suggests this
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
spacy 3.7.4 requires typer<0.10.0,>=0.3.0, but you have typer 0.12.3 which is incompatible.
weasel 0.3.4 requires typer<0.10.0,>=0.3.0, but you have typer 0.12.3 which is incompatible.

atleast that's the thing in colab for command line one but the Llama board one works fine.

i think its conflict with another package , i tried  !pip install  xformers

Traceback (most recent call last):
File "C:\Users\krafi\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Users\krafi\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 87, in run_code
exec(code, run_globals)
File "C:\Users\krafi\AppData\Local\Programs\Python\Python39\Scripts\llamafactory-cli.exe_main.py", line 4, in
ModuleNotFoundError: No module named 'llmtuner'

i see !pip install --no-deps xformers<0.0.26 this line exists on the colabs ,, still for me it didnt fix, i dont know what changed,, please someone check in , just run all ... close the GUI ,, run command line

right now i test this on a new browser with another google account didnt work,,, i used colab this code last week it worked at that time.. maybe somekind of update issue on github code

You can consider using the latest notebook: https://colab.research.google.com/drive/1eRTPn37ltBbYsISy9Aw2NuI2Aq5CQrD9?usp=sharing

yes.. it worked .. check my project to create custom private dataset using llama3 offline.
https://gitlab.com/krafi/tuna-asyncio-with-llama.git
it worked.. thanks a lot for your support .


Hierarchy

Hey guys,
is there any way to create hierarchical tags like eg a tag "Colors" and then the subtags "Red", "Blue", "Green"? I have django-taggit installed already and would prefer to use it instead of coming up with a new solution or adding another tagging solution.
Thanks for any thoughts and help.

Does anyone found a way to solve this? I'am trying to do a simple hierarchy relationship with a depth level equals to one...

custom tags might be part of your answer here. You could add (for example) a django-mptt field to your tags and then have some system for organizing them. This lib solves the tagging part but creating those tags might be a bit tricky (not to mention the UI....).
A hacky way might be around using some sort of symbol in the name....

custom tags might be part of your answer here. You could add (for example) a django-mptt field to your tags and then have some system for organizing them. This lib solves the tagging part but creating those tags might be a bit tricky (not to mention the UI....).
A hacky way might be around using some sort of symbol in the name....

Whould be really nice to have hierarchy from the box. Or at least to have opportunity to switch on it.

@mihalt Could you describe your usecase a bit? I don't disagree that having something out of the box is nice. Just would want to understand the contours of the "something"

custom tags might be part of your answer here. You could add (for example) a django-mptt field to your tags and then have some system for organizing them. This lib solves the tagging part but creating those tags might be a bit tricky (not to mention the UI....).
A hacky way might be around using some sort of symbol in the name....

Whould be really nice to have hierarchy from the box. Or at least to have opportunity to switch on it.

is there any way to create hierarchical tags like eg a tag "Colors" and then the subtags "Red", "Blue", "Green"?

You have good example in the main topic. And "Color" can be subtag of "Physics", "Painting" for example. And "Physics" is subtag of "Science" and so on.


Extension doesn't work on Ubuntu 23.10

The install.sh script doesn't produce any error. But extension state is ERROR:
$ gnome-extensions info<EMAIL_ADDRESS><EMAIL_ADDRESS>  Name: Bottom Bar
  Description: Move GNOME Top Bar to the bottom of the screen.
  Path<EMAIL_ADDRESS>  State: ERROR

Ubuntu 23.10 uses GNOME 45.1, but the extension metadata.json file declares support of version 42 only.
$ gnome-extensions --version
45.1

The Looking Glass (Alt+F2, lg) shows the following error:
import declarations may only appear at top level of a module


⚠ ClamAV has degraded performance

In 01b6558, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 49 ms

Resolved: ClamAV performance has improved in 738ea0d after 14 minutes.


Catch all deserializing errors

I have added a try/catch in deserializable to ensure that all errors are caught and returned as fuel errors

Actually, Result has this capability built-in by using Result.of. @markGilchrist can you try that out instead?

@kittinunf  I have looked at that but Result.of has a fn signature of
fun <V : Any> of(f: () -> V): Result<V, Exception>
and what I need is
fun <V : Any> of(f: () -> V): Result<V, FuelError>

will merge in about 8 hours after work

I have raised #394 to improve on this

Let's merge this to close the issue. 😉


Caught IOException during write loop, shutting down

Hi Mr. Pedro,
I am using your library and sometimes I get the following error:
E/RtmpConnection: Caught IOException during write loop, shutting down: Write error: ssl=0x7379a9bd00: I/O error during system call, Broken pipe
I would like to know if you have knowledge to which this could be due.
I must admit that I am not making use of the latest version of your library. I promise to update it in the project but I need to make a big change. I'll try soon in the next few days.
But my question is oriented to know if you have an idea of what might be happening. Why is this due? Does it have to do with the connection to the internet? Or could it be due to an error in the url? or is it something else?
It's weird. Sometimes connects, sometimes dont. When it dont, then, could show me the error or just it fail with onConnectionFailedRtmp. If the second one happen there is no problem because there is a reason. In the first one IDK what is happening because there is no trace.

This means that server close connection.
https://stackoverflow.com/questions/38016109/javax-net-ssl-sslexception-write-error-ssl-0x7f70604080-i-o-error-during-syst
Library line:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/blob/master/rtmp/src/main/java/com/github/faucamp/simplertmp/io/RtmpConnection.java#L509
You should receive this in onConnectionFailed callback. If you are not receiving it. Update library version.

I am updating right now the library. I will tell you how it's going.

I received this exception when device turned offline, onConnectionFailedRtmp only thrown when SocketException happened, so I didn’t receive any callback, it just stuck there.

I received this exception(SSLException) when device turned offline, onConnectionFailedRtmp only thrown when SocketException happened, so I didn’t receive any callback, it just stuck there.

What version of the library are you using?

@denebchorny I always use latest version, you could see the code
SSLException not belongs to SocketException, so it only be ignored.


Invoking multi-cycle components broken

The following program returns the wrong results:
import "primitives/std.lib";
component main() -> () {
  cells {
    x = prim std_reg(32);
    y = prim std_reg(32);
    mult_pipe0 = prim std_mult_pipe(32);
  }
  wires {
    group let3<"static"=4> {
      mult_pipe0.left = 32'd10;
      mult_pipe0.right = 32'd20;
      mult_pipe0.go = !mult_pipe0.done ? 1'd1;

      x.in = mult_pipe0.out;
      x.write_en = mult_pipe0.done;

      let3[done] = x.done;
    }
    group let4<"static"=4> {
      mult_pipe0.left = 32'd30;
      mult_pipe0.right = 32'd40;
      mult_pipe0.go = !mult_pipe0.done ? 1'd1;

      y.in = mult_pipe0.out;
      y.write_en = mult_pipe0.done;

      let4[done] = y.done;
    }
  }
  control {
    seq {
      let3;
      let4;
    }
  }
}

The offending lines are the guards to the go signals of the mult_pipe0
units. Since the guards say:
mult_pipe0.go = !mult_pipe0.done ? 1'd1;

The go signal is set to one cycle after the done is raised.
Normally, this is not a problem because the group usually finishes executing.
However, in this case, we assign the value in the multiplier to a
register which causes the group to take one extra cycle and re-enables the
multiplier.
Next, when the let4 group executes, the multiplier's go signal has already
been high for one cycle.
This means that the done signal for the multiplier is prematurely raised
in let4 causing the incorrect value to be written to y.
We didn't catch this issue because the Dahlia frontend never shares
multipliers.
It was uncovered by the resource sharing pass.
In general, this is going to be a problem for groups that enable multi-cycle
components (even FuTIL) ones since the group usually doesn't make sure that
the component only runs once.
One possible solution is changing the frontends to generate additional
registers to make sure that the go signal is only raised once in the
execution of the group but that feels somewhat unclean.

RFC from @sampsyo @sgpthomas

Just wanted to let you know that I have seen this ping & added it to my queue but I am light-years behind during this crazy week and it will take me a bit to get to having useful thoughts! I will probably need to think more to understand what this means:

However, in this case, we assign the value in the multiplier to a
register which causes the group to take one extra cycle and re-enables the
multiplier.
Next, when the let4 group executes, the multiplier's go signal has already
been high for one cycle.
This means that the done signal for the multiplier is prematurely raised
in let4 causing the incorrect value to be written to y.

I don't yet understand why this is the case but this is due to my deadline-addled brain not being able to focus on things this week.

Sounds good. Here is one more attempt to explain what's going on. In both let3 and let4, we do the following:

cycle 0: read some values and set mult_pipe0 = 1 (!mult_pipe0.done == 0)
cycle 0..3: Get the value from mult_pipe0 and set mult_pipe0.go = 0 (!mult_pipe0.done == 1).
cycle 3..4: Save the value from mult_pipe0 into a register.
: (Undesired behavior) Set mult_pipe0.go = 1 (!mult_pipe0.done == 0) by mistake!!

Since let3 and let4 run in sequence, the mistaken mult_pipe0.go = 1 in let3 causes let4 to see the wrong values.

Ah, I finally understand! Thank you for this helpful breakdown! The insight I was missing is that the offending assignment is firing because our “protocol” for how to “invoke” components fails to account for time spent after the invoked component completes—because its done signal only stays high for a moment, the group observes it becoming low again, and then says, “aha, it must be time to re-invoke this component!!”
One thing I would like to ponder is whether this problem also exists in code generated from lowering seq... that is, if we had code like this:
seq {
  seq { mult ; save_in_x };
  seq { mult ; save_in_y }
}

(assuming maybe-obvious definitions of the groups involved), and we compiled the inner seqs, we would generate code that has this issue, right?

This will be fixed #305.

This means that the done signal for the multiplier is prematurely raised in let4 causing the incorrect value to be written to y.
This diagnosis was wrong—the done signal is clobbered when go is 0 for one or more cycles. The actual problem was that the static timing pass was generating the wrong FSM transition for the first state.


⚠ Fortnite has degraded performance

In a7e7054, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1515 ms

Resolved: Fortnite performance has improved in c2e768e.


feat: restrict edtech startups

Description

Added edtech startups in restricted words.
Added multiple entries of the words so it can't be used in the channels/server.

Fixes #106

Check List (mark all applicable checkboxes)

[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] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots (if applicable)

Original
Updated

original screenshot
updated screenshot

Let me know what other ways are there of writing edtech startups, I will add them.

Let me know what other ways are there of writing edtech startups, I will add them.


Web Flexbox api like widget to have responsive ui design with little boilerplate code

Use case
I recently wrote a fine wrapper widget around  Column Row and Flexible in order to have items laid out side by side specified by axis count which on changing to different numeric values allowed me to have n items in each row and rest of the widgets gets wrapped down allowing me to have n number of items in every row based on different responsive breakpoints
allowing me to build responsive forms
Usage
  FlexWrap( children:[
  Text('1'),
  Text('2'),
  Text('3'),
  Text('4'),
  ], axisCount:2,
  columnPadding:EdgeInsects.symetric(horizontal:5))

Implementation
    class FlexWrap extends StatelessWidget {
  const FlexWrap(
      {Key? key,
      required this.children,
      required this.axisCount,
      this.columnCrossAlignment,
       this.columnPadding,
      this.columnMainAlignment,
      this.rowPadding})
      : super(key: key);
  final List<Widget> children;
  final int axisCount;
  final MainAxisAlignment? columnMainAlignment;
  final CrossAxisAlignment? columnCrossAlignment;
  final EdgeInsets? rowPadding;
  final EdgeInsets? columnPadding;

  @override
  Widget build(BuildContext context) {
    List<List<Widget>> rows = [];
    int temp = 0;
    for (int i = 0; i <= children.length ~/ axisCount; i++) {
      if (temp + axisCount >= children.length) {
        rows.add(children.sublist(temp));
      } else {
        rows.add(children.sublist(temp, temp + axisCount));
      }
      temp = temp + axisCount;
    }
    return Column(
      mainAxisSize: MainAxisSize.max,
      mainAxisAlignment: columnMainAlignment ?? MainAxisAlignment.start,
      crossAxisAlignment: columnCrossAlignment ?? CrossAxisAlignment.start,
      children: rows
          .map((e) => Padding(
              padding: rowPadding ?? EdgeInsets.zero,
              child: Row(
                mainAxisSize: MainAxisSize.max,
                children: e.map((e) => Flexible(child: Padding(
                    padding: columnPadding??EdgeInsets.zero,
                    child: e))).toList(),
              )))
          .toList(),
    );
  }
}

Proposal
Is it possible to have something of this sort in flutter? if so what else improvements i can do or expect from this code?

@shivanshtalwar0
You can probably create a plugin that offers this kind of widget, because I am not sure if this is feasible to be integrated in the framework. If that's a custom widget, I believe, a plugin is your best bet. Once you have a plugin and feedback from user, you can update it based on it which if in framework, can't be done so frequently.
I am going ahead and closing this as not-feasible. You can ask the same question on support channels like StackOverflow to get more response from community.
Thanks.


[flink] add time type for mysql cdc action

(Please specify the module before the PR name: [core] ... or [flink] ...)
Purpose
*issue https://github.com/apache/incubator-paimon/issues/966 *
Tests
org.apache.paimon.flink.action.cdc.mysql.MySqlSyncTableActionITCase
API and Format
(Does this change affect API or storage format)
Documentation
(Does this change introduce a new feature)

Hi @zhangjun0x01 can you take a look to https://github.com/apache/incubator-paimon/pull/1012 , orc can support time too


Problems running Keras imdb_cnn.py example with Theano

Hello,
I recently tried to run Keras imdb_cnn.py example (https://github.com/fchollet/keras/blob/master/examples/imdb_cnn.py):
I have noticed that it returns the following error message:
AttributeError: module 'theano.tensor.nnet' has no attribute 'relu'
I solved this error by defining my RELU function like this and by calling it when needed:
import theano.tensor as T

def my_relu(x):
    return T.switch(x<0, 0, x)

That problem has been solved, but now it returns a new error message:
TypeError: max_pool_2d() got an unexpected keyword argument 'mode'
I am using Keras 0.3.1 with Theano 0.7.0.
Could you help me with this problem?
Thank you!

Do you have the bleeding edge version of Theano. If not, it seems you should update to the latest Theano development version using:
pip install --upgrade --no-deps git+git://github.com/Theano/Theano.git

Now it works. Thanks!


Ignore availability for block level rules against the origin site/RSE

Fixes #10030
Status
not-tested
Description
These block level rules are created to lock data that is getting produced at a given "origin" site/RSE. Which means, data is already available at the storage. So, ignore RSEs tagged as unavailable/downtime and make sure our block level rules can get created through the ignore_availability=True.
Is it backward compatible (if not, which system it affects?)
yes
Related PRs
none
External dependencies / deployment changes
none

Thanks Todor!


Job hangs for a good amount of time after finishing file copy.

Note
I have a repository in Azure DevOps, pipeline of this repos copy the generated tar file to a remote server. Every step of the pipeline works very smooth. But, CopyFilesOverSSH task keeps waiting for the finish for good 30 minutes.
I have checked on the server that file is fully copied in 5 minutes, but the task is still showing Copying file ****
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: CopyFilesOverSSH
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment

Server - Azure Pipelines or TFS on-premises?

If using TFS on-premises, provide the version:

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name:

If using private agent, provide the OS of the machine running the agent and the agent version:

Issue Description
[Include task name(s), screenshots and any other relevant details]
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Insert error from the logs here for a quick overview]

@vsd-codesode Can you please provide information about size of the file that you copied?

File size is around 530mb.

Reproduced a delay after finishing copy process depending on source file size. This behavior is caused by the scp2 library used by CopyFilesOverSSH task. Created https://github.com/microsoft/azure-pipelines-tasks/issues/13048 for future investigations.

Hi @sdobrodeev ,
I could help you in doing the code change. Let me know; if your process allows.

It was fixed in https://github.com/microsoft/azure-pipelines-tasks/pull/13084 PR. Tested on 500Mb and 1Gb files. Delay after copying now no longer occurs.

Reopened it at the moment due to reverted changes - https://github.com/microsoft/azure-pipelines-tasks/pull/13298, we are going to proceed on it further


feat(package): Update babel-plugin-module-resolver.

Coverage remained the same at 100.0% when pulling 2a5bfa8cb9742611da414bb278265cc9848b2bcb on update-babel-plugin-module-resolver into 912221321ed58cbc847c96e8c868a11f1f86529f on master.

Coverage remained the same at 100.0% when pulling 2a5bfa8cb9742611da414bb278265cc9848b2bcb on update-babel-plugin-module-resolver into 912221321ed58cbc847c96e8c868a11f1f86529f on master.

Coverage remained the same at 100.0% when pulling dec14757a60d49889feffaee9358f0325c5ec6d2 on update-babel-plugin-module-resolver into 912221321ed58cbc847c96e8c868a11f1f86529f on master.


connected_chest compatibility changes

We have recently changed the connected_chest and facedeer hopper (https://github.com/minetest-mods/hopper/) mods to make them compatible with each other. (This compatibility between connected_chest and hopper currently only works with facedeer's version and not TenPlus1's version.)
Maybe hopper_compat needs to be changed now, too.

So, the very messy code in this mod for that compatability is no longer required? Well, that is actually a relief because it needs to be cleaned up anyway, and I didn't really feel like doing that at the moment. I suppose I should make it work for tenplus1's version then? Unless you are already working on it?
Anyway, thanks for letting me know, I appreciate it.

Sorry for the late response.
I'm not working on hopper compatibility (except code reviews at my mods). If tenplus1's version should be supported, too, it may be easier to adopt the Pull Request from facedeer hopper to tenplus1's hopper mod than to edit the hopper_compat mod if the code of both hopper mods is similar enough.

Good point, I was getting ready to start adding the compatibility for tenplus1's hopper mod but if just opening a similar pr to tenplus1's version is easier than I will consider doing that instead.
I reviewed the changes to facedeer's hopper mod, and I agree that it is unnecessary and have removed it.
Don't worry about the late response. I'd rather have a late on rather than none at all.


Update Timestamp for correct spec.

Timestamp and Duration have differing specs for what constitute valid
values. A Timestamp always has nanos in [0, 999999999), whereas a
Duration generally has nanos with signs that match seconds. The behavior
for Timestamp was clearly copied from Duration and this fixes that. The
tests were testing the wrong thing.
I'd like to add more tests.
https://github.com/apple/swift-protobuf/issues/207

Re more tests, I think we can actually upstream something to the conformance tests.  Send in a json strings that is negative, and then ensure the proto that comes back is correct.  That has the advantage of getting all the languages covered also.  I'd likely do both timestamp and duration to ensure both behaviors are covered.

fyi - I'd suggest doing reindents in a sep PR so looking at the combined diff on github is doable.  I ended up going per commit to try and figure out the changes.

I removed the re-indent.

Are you doing that followup on this PR, or did you want to land this and then do the follow up?

@thomasvl I ported the followup into a commit here--happy to do on this PR if it looks OK to you.

Might as well finish it out here.  I'll let @allevato comment on that part, since he's the better voice on Swift style for this stuff.

@allevato In response to "I still see the old version here" -- you're talking about the String formatting? I guess just let me fold in the String.init(format:_:) code that I have if we want to change this for this PR. BRB.

PTAL

Hold off a moment--I'm testing.

Ok, validated on Linux (for the string formatting concerns). Ready to merge. @allevato


Pre-update of backing applications

The update service flow is now:

pre-update backing applications
update backing services
update backing applications

The Cloud Foundry implementation has a pre-update step which applies
backing application environment updates. This allows the following
backing services update step to read the updated app environment, which
is required for correct operation of some services where a rebind is
performed on update. The final update backing applications step performs
a rolling redeployment as before to ensure both environment changes and
any credential updates resulting from a rebind are propagated to the
backing apps.

Thanks for the review @LittleBaiBai 👍

Thanks for the review @LittleBaiBai 👍


NIFI-12411: Update PublishAMQP to read AMQP headers value from FlowFile attributes and amq$headers string

Summary
NIFI-12411
Processor can now also create message headers using attributes matching the given Regex property. The name of the attribute is used as header key. In addition to that it can read values from two sources i.e. attributes matching Regex and the headers present in amq$headers string. In case of key duplication in both sources, the precedence property decide which value will be used.
AMQP attributes keys are now set as constants strings and reused where needed.
Added onScheduled to PublishAMQP and ConsumeAMQP to read all properties which don't change during running state.
Test cases added for PublishAMQP headers source changes.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21

Licensing

[x] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[x] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

@umarhussain15 Can you please rebase and consider the feedback shared from @exceptionfactory ?
Thanks

Hi @joewitt @exceptionfactory,
I have reverted the changes of making class level variables based on processor properties.
Also, the branch is rebased on latest changes from main

@exceptionfactory @joewitt
I have added one more change, which will allow users to set amqp processor's password via env variables.
I think this will be helpful in cases where we use AMQP processors in multiple NiFI instances. Instead of copying and pasting different passwords in processor properties, we can reference the env variable via its name.
Let me know your thoughts on it.
Thanks.

@exceptionfactory @joewitt
I have added one more change, which will allow users to set amqp processor's password via env variables. I think this will be helpful in cases where we use AMQP processors in multiple NiFI instances. Instead of copying and pasting different passwords in processor properties, we can reference the env variable via its name. Let me know your thoughts on it. Thanks.

Thanks for calling out this particular change @umarhussain15. Given the scope of the current pull request, I recommend considering that change separately.
In general, sensitive properties such as passwords do not support reading from environment variables. The reason is that environment variables are also accessible through Expression Language, so they are not necessarily secure. The use case is still supported through Parameter Contexts and Parameter Providers, where the Environment Variable Parameter Provider can be used. This is an additional layer of indirection, but it follows the general convention for other sensitive properties.

Thanks for the explanation, @exceptionfactory. I will revert the change here then.

Checkstyle reported issues fixed

Hi @exceptionfactory,
I have applied your suggestions and also removed the precedence option from the processor.
I have also updated the additional documentation to describe the headers source setting of the processor.


Gradle install problem

when I run the shell after sometimes it just  stoped
here is the screen shot
please let me know where is the problem.

How long did you wait before canceling?  The script takes a variable amount of time depending on your internet, system specs, ect.


Edits for JOSS Reviewer Recommendation Notebook

I have edited my notebook to address the issues #1635 and #1636.

Noted that the paper number needs to be changed in cell 2 where xxxxx is.
Added a progress bar to the JOSS papers cell, and notes the estimated time
Added in the reviewer information for the last quarter, year, and total reviews.

:zap: thanks @elizabeth-pugliese!


RRule is missing next occurrence

Reporting an issue
I have an RRule setup to daily recurrence, but somehow when getting the next occurrence it skips the correct one and gives me the one after. My code sample is here
const { RRule } = require("rrule");
const { DateTime } = require("luxon");

function getRrule() {
    rruleObject = null;

    rruleObject = {
                "_cache": {
                    "all": false,
                    "after": [],
                    "before": [],
                    "between": []
                },
                "options": {
                    "freq": 3,
                    "tzid": null,
                    "wkst": 0,
                    "count": 15,
                    "byhour": [
                        19
                    ],
                    "bymonth": null,
                    "dtstart": "2024-03-08T23:50:59.000Z",
                    "byeaster": null,
                    "byminute": [
                        50
                    ],
                    "bysecond": [
                        59
                    ],
                    "bysetpos": null,
                    "byweekno": null,
                    "interval": 1,
                    "byweekday": null,
                    "byyearday": null,
                    "bymonthday": [],
                    "bynweekday": null,
                    "bynmonthday": []
                },
                "origOptions": {
                    "freq": 3,
                    "count": 15,
                    "dtstart": "2024-03-08T23:50:59.000Z",
                    "interval": 1
                }
            };

    console.log("start date raw: ", new Date(rruleObject.options.dtstart));

    rruleObject.options.dtstart = DateTime.fromISO(rruleObject.options.dtstart).toUTC().toJSDate();

    console.log("start date from Luxon: ", rruleObject.options.dtstart);

    const rrule = new RRule(rruleObject.options);

    const currentDate = DateTime.fromJSDate(new Date())
                                .toUTC()
                                .setZone('local', { keepLocalTime: true })
                                .toJSDate();
    console.log("current date from Luxon: ", currentDate);
    console.log("current date from JS: ", new Date());

    nextOccurrence = rrule.after(currentDate);
    return nextOccurrence;
}

 function main() {
    const nextOccurrence =  getRrule();

    const s = DateTime.fromJSDate(nextOccurrence)
                                .toUTC()
                                .setZone('local', { keepLocalTime: true })
                                .toJSDate();
    console.log("Next Occurrence raw: ",nextOccurrence);
    console.log("Next Occurrence from Luxon: ",s);

}

main();

Expected
Next occurrence should be March 20 at 23:50
Actual
Occurrence is coming as March 21
RRule version
2.8.1
OS
Macos
Timezone
EDT

You have the same issue as I do, RRule seems to convert the EDT to UTC, therefore your next occurence is March 21st 03:50 instead of March 20th... I cannot find a solution to this :'(


Error fetching data

Hello. I have default yaml file with tapo_p100_control installed  (but not working though)
And it is almost impossible to use because of the huge switch lag and constant errors with my six p100 plugs.
What is going on?

Logger: custom_components.tapo
Source: helpers/update_coordinator.py:219
Integration: Tapo Controller (documentation, issues)
First occurred: 4:47:09 (14 occurrences)
Last logged: 4:48:40
Error fetching tapo data:

2021-09-23 04:46:52 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration sleep_as_android which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-23 04:46:52 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration xiaomi_gateway3 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-23 04:46:52 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-23 04:46:52 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration tapo_p100_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-23 04:46:52 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-23 04:47:08 WARNING (MainThread) [homeassistant.setup] Setup of input_text is taking over 10 seconds.
2021-09-23 04:47:08 WARNING (MainThread) [homeassistant.setup] Setup of zone is taking over 10 seconds.
2021-09-23 04:47:08 WARNING (MainThread) [homeassistant.setup] Setup of input_select is taking over 10 seconds.
2021-09-23 04:47:08 WARNING (MainThread) [homeassistant.setup] Setup of timer is taking over 10 seconds.
2021-09-23 04:47:09 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:47:09 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Living Room' for tapo integration not ready yet: None; Retrying in background
2021-09-23 04:47:11 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:47:11 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Hall' for tapo integration not ready yet: None; Retrying in background
2021-09-23 04:47:11 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:47:11 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Kitchen' for tapo integration not ready yet: None; Retrying in background
2021-09-23 04:47:12 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:47:12 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Office' for tapo integration not ready yet: None; Retrying in background
2021-09-23 04:47:15 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:47:15 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Living Room' for tapo integration not ready yet: None; Retrying in background
2021-09-23 04:47:15 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:47:15 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Bedroom' for tapo integration not ready yet: None; Retrying in background
2021-09-23 04:47:19 ERROR (MainThread) [custom_components.xiaomi_gateway3.core.xiaomi_cloud] Timeout while requesting MIoT api /home/device_list
2021-09-23 04:47:30 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:47:51 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:48:21 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:48:40 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:48:40 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:48:40 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:48:40 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:48:40 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:49:11 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:49:50 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:49:50 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:50:28 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:50:28 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:50:28 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:50:41 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:52:08 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:52:11 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:52:18 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:52:18 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:52:18 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:
2021-09-23 04:52:19 ERROR (MainThread) [custom_components.tapo] Error fetching tapo data:

also this
Logger: homeassistant.core
Source: custom_components/tapo/tapo_entity.py:33
Integration: Tapo Controller (documentation, issues)
First occurred: 20:11:47 (1 occurrences)
Last logged: 20:11:47

Error executing service: <ServiceCall switch.turn_off (c:b331df49929bcc1b5ce8c273872eaaeb): entity_id=['switch.hall', 'switch.kitchen', 'switch.living', 'switch.living2']>
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/connector.py", line 969, in _wrap_create_connection
    return await self._loop.create_connection(*args, **kwargs)  # type: ignore  # noqa
  File "/usr/lib/python3.9/asyncio/base_events.py", line 1056, in create_connection
    raise exceptions[0]
  File "/usr/lib/python3.9/asyncio/base_events.py", line 1041, in create_connection
    sock = await self._connect_sock(
  File "/usr/lib/python3.9/asyncio/base_events.py", line 955, in _connect_sock
    await self.sock_connect(sock, address)
  File "/usr/lib/python3.9/asyncio/selector_events.py", line 502, in sock_connect
    return await fut
  File "/usr/lib/python3.9/asyncio/selector_events.py", line 537, in _sock_connect_cb
    raise OSError(err, f'Connect call failed {address}')
TimeoutError: [Errno 110] Connect call failed ('<IP_ADDRESS>', 80)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/core.py", line 1508, in catch_exceptions
    await coro_or_task
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/core.py", line 1527, in _execute_service
    await handler.job.target(service_call)
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/entity_component.py", line 213, in handle_service
    await self.hass.helpers.service.entity_service_call(
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/service.py", line 658, in entity_service_call
    future.result()  # pop exception if have
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/entity.py", line 843, in async_request_call
    await coro
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/service.py", line 695, in _handle_entity_call
    await result
  File "/home/homeassistant/.homeassistant/custom_components/tapo/switch.py", line 30, in async_turn_off
    await self._execute_with_fallback(self._tapo_coordinator.api.off)
  File "/home/homeassistant/.homeassistant/custom_components/tapo/tapo_entity.py", line 33, in _execute_with_fallback
    await self.coordinator.api.login()
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/client.py", line 520, in _request
    conn = await self._connector.connect(
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/connector.py", line 535, in connect
    proto = await self._create_connection(req, traces, timeout)
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/connector.py", line 892, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/connector.py", line 1051, in _create_direct_connection
    raise last_exc
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/connector.py", line 1020, in _create_direct_connection
    transp, proto = await self._wrap_create_connection(
  File "/srv/homeassistant/lib/python3.9/site-packages/aiohttp/connector.py", line 975, in _wrap_create_connection
    raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]

I have default yaml file with tapo_p100_control installed (but not working though)

This integration, actually, doesn't support configuration via yaml file. You can add your tapo devices through UI.
Yaml configuration will be available as soon as possible in 1.1.5 (https://github.com/petretiandrea/home-assistant-tapo-p100/milestone/1)

Yes, i know, i tried both versions. Neither of them not working properly - not yours with adding every plug through UI, nor tapo_p100_control through yaml file, they both lagging and disconnecting from plugs with errors i described above

well, after day of waiting, tapo_p100 starts to work without problem
looks like that while you configuring new setup with big amount of plugs you somehow exceeding some connection limit
but if switch plugs quite rare, it's all ok


Can create invalid namespace

Example:
namespace Foo-Bar
{
public class newclass
{
}

}

I assume your path is /Projects/Foo-Bar ?
What should the namespace be in that situation?

IIRC Visual Studio replaces "-" with "_"

If you can confirm I'll make the change :)
On 17 October 2016 at 09:13, Florian Hötzinger<EMAIL_ADDRESS>wrote:

IIRC Visual Studio replaces "-" with "_"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jchannon/csharpextensions/issues/7#issuecomment-254141428,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapiD1Se33hNqw_rNPW3f_6SMIEZ3kks5q0y4-gaJpZM4KYVuy
.

Confirmed.

FWIW this is the spec :)
https://msdn.microsoft.com/en-us/library/aa664670.aspx

How's this?
Ooh a spec, will take a look, thanks

:shipit:

🚢 'ed

Thanks for the report


Bugfix/issue 18 model becomes invisible

Fixes #18

Coverage increased (+0.1%) to 94.544% when pulling e94179fc1ebbd6622e36c0730ddf01297f040c11 on bugfix/ISSUE-18-model-becomes-invisible into c43801df128f37393e406da3c4d89db765bfc656 on develop.


Muse Webpage Down

Hi, seems like the webpage for the Demo is not working https://lightning.ai/muse

It is working again 🚀


Consider renaming frame to stream

What do you think @stheppi  @garyfrost

@Antwnis too

Won't be confusing with the collection Stream?

Yes. But no one uses them. Open to othee names :) or not changing it.
On 18 Feb 2016 10:28, "Stefan"<EMAIL_ADDRESS>wrote:

Won't be confusing with the collection Stream?
—
Reply to this email directly or view it on GitHub
https://github.com/eel-sdk/eel/issues/62#issuecomment-185643536.

Stream it is then 😊

You think its better than Frame? Frame is growing on me...
On 18 February 2016 at 12:53, Stefan<EMAIL_ADDRESS>wrote:

Stream it is then 😊
—
Reply to this email directly or view it on GitHub
https://github.com/eel-sdk/eel/issues/62#issuecomment-185707573.

Let's grow the entropy in this thread :8ball:
Let's call them MiniFrame
So we have DataFrame on spark - or MiniFrame on eel :+1:

And we define MiniFrame as anything from a few records up to a few 10's of millions or records

Ok so MiniFrame and Stream currently.
On 18 February 2016 at 18:35, Antonios Chalkiopoulos <
<EMAIL_ADDRESS>wrote:

And we define MiniFrame as anything from a few records up to a few 10's
of millions or records
—
Reply to this email directly or view it on GitHub
https://github.com/eel-sdk/eel/issues/62#issuecomment-185850997.

Dataset is another
Or River.


some issue in the script

When I click download, a prompt like this pops up.

I would check later

I fixed it in v0.2.20.
If the issue happens again, please let me know thanks.

thx!The script can run now！


Fails with multiline environment variables (TRAVIS_CMD)

https://travis-ci.org/antocuni/pdb/builds/532855282#L478:
% env
TRAVIS_CMD=if [[ "$TOXENV" != checkqa ]]; then
    env
    bash <(curl -s https://codecov.io/bash) -Z -X gcov -X coveragepy -X search -X xcode -X gcovout -X fix -f coverage.xml -n "${TRAVIS_PYTHON_VERSION}"
  fi

This causes codecov-bash to fail then:
  _____          _
 / ____|        | |
| |     ___   __| | ___  ___ _____   __
| |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
| |___| (_) | (_| |  __/ (_| (_) \ V /
 \_____\___/ \__,_|\___|\___\___/ \_/
                              Bash-8a28df4
==> Travis CI detected.
    project root: .
    Fixing merge commit SHA
    Yaml not found, that's ok! Learn more at http://docs.codecov.io/docs/codecov-yaml
    -> Found 1 reports
==> Detecting git/mercurial file structure
==> Appending build variables
    + TRAVIS_OS_NAME
    + bash
    + <(curl
/dev/fd/63: eval: line 1256: unexpected EOF while looking for matching `)'
/dev/fd/63: eval: line 1257: syntax error: unexpected end of file

It happens because I include "TRAVIS_PYTHON_VERSION" in the command itself.
Here is output with set -x and typeset -p: https://travis-ci.org/antocuni/pdb/builds/532863006#L740

Duplicate of https://github.com/codecov/codecov-bash/issues/133.