The public folder is not accessible at root of server with Cloudflare Pages

Environment
Using Nuxt 3.0.0; Node.js 16.13.1
Reproduction
Create a blank project with Nuxt 3, add images to "public/" and publish to Cloudflare Pages using environment variables "NITRO_PRESET=cloudflare_pages".
Describe the bug
The files added to public/ will not be accessible from the server root.
Additional context
No response
Logs
No response

I'm trying using ".output/public" as a root directory, it may be the issue.

It was just a configuration error, without using Wrangler and using Git Connect, this parameter has to be set correctly !

@luzzardik I set it the same as you, but functions don't work for me.

@YankeeTube
Make sure you have such settings:
BUILDS & DEPLOYMENTS
Build command - npm run build
Build output directory - /.output/public
Root directory - /
ENVIRONMENT VARIABLES
NITRO_PRESET = cloudflare_pages
NODE_VERSION = 16.13.1 (seems to be the only one to work on Pages)


HBASE-23085 Network and Data related Actions; ADDENDUM

Fix percentage in String.format

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

+1 :green_heart:
mvninstall
6m 12s
master passed

+1 :green_heart:
compile
0m 28s
master passed

+1 :green_heart:
checkstyle
0m 19s
master passed

+1 :green_heart:
shadedjars
4m 35s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 16s
master passed

+0 :ok:
spotbugs
4m 54s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m  0s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m  2s
the patch passed

+1 :green_heart:
compile
0m 29s
the patch passed

+1 :green_heart:
javac
0m 29s
the patch passed

+1 :green_heart:
checkstyle
0m 18s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
4m 40s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
15m 38s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
javadoc
0m 15s
the patch passed

+1 :green_heart:
findbugs
0m  0s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 51s
hbase-it in the patch passed.

+1 :green_heart:
asflicense
0m 14s
The patch does not generate ASF License warnings.

46m 32s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-871/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/871

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux c80a92d09182 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-871/out/precommit/personality/provided.sh

git revision
master / 3b0c276aa3

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-871/1/testReport/

Max. process+thread count
402 (vs. ulimit of 10000)

modules
C: hbase-it U: hbase-it

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-871/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Need delete check for new dhe_context in libspdm_try_send_receive_key_exchange

Need delete check for new dhe_context in libspdm_try_send_receive_key_exchange  to enhance the code performance.
The follow check need be deleted, because the NULL dhe_context will cause the libspdm_secured_message_dhe_generate_key fail.
We can just check the libspdm_secured_message_dhe_generate_key result.
    if (dhe_context == NULL) {
        libspdm_release_sender_buffer (spdm_context);
        return LIBSPDM_STATUS_CRYPTO_ERROR;
    }

https://github.com/DMTF/libspdm/blob/f1ffe7e094b3b7daf85c4fae2fae6b9d98212d11/library/spdm_requester_lib/libspdm_req_key_exchange.c#L361-L377

I will check it.

I dont understand why we need it.
Whenever you talk about "performance", please show me the data - how many seconds you have saved?

The security reviewers will also wonder why libspdm_secured_message_dhe_new isn't checked.

Thanks. I will close the issue and PR. And I have submitted a new issue:  https://github.com/DMTF/libspdm/issues/1624 to add check in responder lib.


Support map Caps Lock to Escape

Support map Caps Lock key to Escape key on hardware keyboard.
I use vim as my favorite editor, It's easy to map CapsLock to Escape on windows or linux, But on Android, It seems impossible. So I add this feature to help somebody like me.
Maybe someone use CapsLock key like Control key, Maybe support that later.
This is my first PR on github, If did something wrong, Please tell me, I'll fix it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


verify_expiration no longer supported by pyJWT

This line likely needs to be changed: https://github.com/GetBlimp/django-rest-framework-jwt/blob/96eb5d9838967a88dfc7d92acfd21ba7481bf50b/rest_framework_jwt/utils.py#L54
perhaps options={'verify_exp': XXX} should be used.
see: https://github.com/jpadilla/pyjwt/issues/147

I'm running into issues with JWT_VERIFY_EXPIRATION set to False, basically it seems to have no effect at all. I guess it depends on this.

Checking this out right now

Downgrading to PyJWT 1.0.1 seems to work until a new version of django-rest-framework-jwt and/or PyJWT is issued.


Add require line to example in readme

Add a require of grape_logging to the example.

Thanks for noticing! :)


Upgrading to latest version gives syntax error

** Before reporting this bug, please...**

Check the latest documentation: https://docs.nativebase.io/
Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
For discussion purpose make use of NativeBase discord: https://discord.gg/TSgCw2UPmb

Describe the bug
A clear and concise description of what the bug is.
The real bug was that the tabs overlapped each other. I came to know it will be solved by updating the library.
So , I updated the library and found a different error now.
To Reproduce
Steps to reproduce the behaviour:
As soon as the app opens, it shows the error in the screenshot attached.
Expected behaviour
It should work smooth and the tabs should not overlap each other.
Screenshots

Platform

NativeBase version : Before it was 2.13.8, now it is 3.0.6
Device: Android shows overlapped tabs whereas, iOS continuosly moves the tabs vigorously
React Native version [e.g. 0.64] 0.61.3
node [e.g. 14.16.1]  12.6.0

@Ruzen1 you need to update to version - 2.15.2 instead of 3.0.6 . Please downgrade to version 2.15.2 . v3 doesn't support Tabs right now.

@rayan1810 Thank you very much. Now I see.


PLEASE update master with 4.19.2

from my point of view master should have to latest release, means you released 4.19.2 officially and then master should have rev. from 4.19.2

A bit of background as to how we are currently structuring our branches in the uaa:

develop has our latest commits
we run our develop commits in CI
assuming they pass CI, when we want to cut a new release, we perform the following:
3.1) we cut a new release from develop. (This involves creating a github release, and updating the version file)
3.2) we fast forward master to develop
3.3) we create a tag pointing to the commit that we released on
3.4) we create a prerelease/vM.m.x branch pointing to the tag that we released
3.5) on develop; we bump the versions file to the next version (snapshot)

On develop future commits are made. When/IF a cve arrises, we make a commit on the prerelease/vM.m.x branch. and perform a patch release off that branch. From our perspective, the develop and master branch have diverged from the 'prerelease/vM.m.x' branch.
Also we think that the master branch should only provide a 'stable' view on develop. In this case it points to a commit that has gone through CI, and also happens to be the latest point release (not the patch).
I think we need to improve the discoverability of what the latest uaa release is. for example, the latest github release is not showing 4.19.2 as the latest release and is instead showing 4.12.2. Github uses the tag timestamp to sort release versions. We might be able to improve that so that github releases shows 4.19.2 as the latest.
I personally think we should remove the master branch. I think it is causing confusion. I think we should use a single branch (the develop branch). And continue the 'train line' branch/tag model we currently use for patch releases.
I also don't think that we should merge the latest patch release (e.g. 4.19.2) to master. As discussed above: the commits made to the 4.19 minor release, are to fix issues on that branch, and thus don't necessarily have to be on either master or develop. The release branches fork off master and develop.
Lastly, I think this is what we used to do in the scary past (at a time we had manual release scripts):

Release 4.19.0
push a feature commit
push a chore commit
fix a CVE
Release 4.20.0 with all these commits to fix the CVE

The issue with this is that we are releasing 2 commits earlier that we wanted to (the ones from 2) and 3)), all we really wanted to release to fix the CVE was the commit 4). This is why we fork off the 4.19.0 tag, cherry pick the commit 4), and release from there. We should be waiting for our next minor release to publish all new feature commits, and not be forced to do it at a moment we might not be ready to do so.

I support many of your thought, however I thing.
develop should always contain the lastest fixes from a CVE. Releasing for a separate branch but not providing this to develop will increase confusion.
If you argue master is a stable view on develop, then you should also commit CVE fixed which are in develop also to master, e.g.
compare yourself server/src/main/java/org/cloudfoundry/identity/uaa/oauth/UaaTokenServices.java between develop and master.
You may remove master, but github requires a default branch and the default branch is the branch everybody from outside will have a look first.
And again this default branch should be a stable (and secure branch) means your latest CVE fixes should be in into such a default branch.
You can omit many things if you have only one version, but with this parallel versions uaa supports, a so call master branch is what its name says: it is the master.
Finally: if you have numeric versions, then from human understanding the greatest number is the latest version and also master has a version, but this is lower then another branch has and this might be confusion for all outside developers. because they simple clone the default branch and assume that is the latest version.
So may be we can close this if you release 4.20.0 from develop soon..

If the CVE is also on develop, develop always contains the CVE fix. Our typical way of doing this is to fix the issue on develop, and then cherry-pick the commits to the impacted release branches. For completeness sake, if for some reason develop does not have the issue from the CVE, for example because a new feature got rid of it, we obviously won't have the CVE fix on develop. So develop does not always contain the latest CVE fix commits.
Now after that, what do we do with master as we are creating multiple CVE-related releases? Well, we can either leave it where it is, or fast-forward it to the top of develop where the CVE fixes are. But that is not a release. The release is from the previous patch branch. I don't want to also cherry-pick the CVE fixes to the master branch.
If we delete the master branch, develop will become our default branch, which contains fixes to all CVEs and bugs that we are aware of, as soon as we have worked on them.
 If you want to find a patched release, you should be looking at the tagged release commits. And if you want to submit a PR, the correct thing is to work off of the develop branch. So we think master currently should not be used for either consuming the UAA or developing the UAA.
What is the use case where you need to consume a "stable branch" that is not a tagged release? The commits we have tagged as releases are the only ones we are confident telling people in the open source community to deploy in their environments.

you may first define then develop as default branch so that git clone git@github.com:cloudfoundry/uaa.git sync this branch and not master.
The use case is the first entry to uaa repo. If you sync first you get master because this is defined as default. but currently this branch does not contain the latest CVEs correction, so it is not a stable branch any newbies should use

@strehle We have made develop the default branch.


⚠ Bofrost.lu has degraded performance

In b7a292b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1272 ms

Resolved: Bofrost.lu performance has improved in 8bc596b after 6 minutes.


Where is it shown in a running server which build type is running?

This article omits any information about determining what build type is running.

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

ID: e1712291-4cb2-7a3f-1298-9c68cb05625d
Version Independent ID: 41defd10-d145-c65c-1145-b936bc10913a
Content: Checked and Free Build Differences - Windows drivers
Content Source: windows-driver-docs-pr/devtest/checked-and-free-build-differences.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @EliotSeattle
Microsoft Alias: eliotgra

https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/installing-just-the-checked-operating-system-and-hal--for-windows-vist#step-4---restart-the-computer

Thanks for the Issue, @arfyness
Added the final paragraph in https://docs.microsoft.com/windows-hardware/drivers/devtest/checked-and-free-build-differences#feedback that directs to the info about discovering which version is used.


Added: Endware functionality

For some use cases, the server may want to perform actions after the user's request has been serviced. Examples include:

logging the request
performing maintenance on resources
error handling
auditing
metrics
anything, really

For these purposes, I have added Endware as a solution. Endware is a http.Handler alias that allows alice users to create "after the fact" middleware in a similar way to how they create regular middleware. Endware is executed after all constructors and handlers have been invoked by Then(h)/ThenFunc(h).
Using endware is simple:
chain := alice.New(m1, m2)
becomes
chainWithEndware := alice.New(m1, m2).Finally(e1, e2)
This leads the flow of
chainWithEndware.Then(h)
to be
m1 -> m2 -> h -> e1 -> e2
The Append() functionality has been mirrored in AppendEndware(), as well as Extend being augmented to also extend endware. AfterFuncs() and AppendEndwareFuncs() are convenience method for those not dealing with http.Handlers directly.
This is still a WIP, just wanted to open it so you could take a look at your leisure.
Sorry in advance if this is not the way you are supposed to contribute code

Hi @protometheus and thank you for contributing.
Have you considered that any middleware as-is can run actions after the handler has served? Consider this:
func log(h http.Handler) http.Handler {
    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        h.ServeHTTP(w, r)
        log.Println("A request has been served")
    })
}

fn main() {
    chain := alice.New(log).Then(myHandler)
}

The message will be printed out after myHandler has served.

Hey @justinas thanks for getting back so quickly! You are definitely correct that you can use the middleware as-is to represent endware. The only difference is that it is not clear from the Chain what the actual order of execution would be. So given:
func log1(h http.Handler) http.Handler {
    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        h.ServeHTTP(w, r)
        log.Println("log1")
    })
}

func log2(h http.Handler) http.Handler {
    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        h.ServeHTTP(w, r)
        log.Println("log2")
    })
}

func log3(h http.Handler) http.Handler {
    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        log.Println("log3")
        h.ServeHTTP(w, r)
    })
}

func main() {
    chain := alice.New(log1, log2).Then(myHandler)
}

will do myHandler -> log2 -> log1. But
func main() {
    chain := alice.New(log1, log3).Then(myHandler)
}

will do log3 -> myHandler -> log1.
My intent was it more obvious the order of execution without having to actually look into the individual middleware to determine what the order is.

Preface: Ignore this if im not adding any value here ;P
@justinas i agree with @protometheus on this. Came here specifically to see if I could use alice to chain middleware on a high level and use middleware composition to distribute business logic across the different routes of an app efficiently (preferably without having to repeat business logic in multiple places). This has to work without having to know the inner execution order of the middleware itself.
I think the main reason why this would be valuable is imo that, in simple HTTP services, I expect middleware to block execution on failed conditions (e.g. custom authz middleware for different nested routers). When using alice in a production codebase, I would highly advise against performing calculations or creating side effects in middleware after next is invoked. It just simply doesnt make sense to introduce side effects into a flow that is quite functional to begin with.
Yes technically people can make their middleware execute next handlers in any order they want, but moving to a declarative middleware makes the experience of using Go's built in routing assets much easier to manipulate in my humble opinion. I believe alice solves this, though this addition would really make it a no brainer.


Use same executable for spawn as the current process

When starting a react-script from a node process which is not in the
path, the scripts would spawn the wrong node executable, or even fail.
This can happen when starting node with an absolute path, for instance
in a Bazel build.
Changes verified by both creating a new project, building and running it, and
also by applying the same changes in another internal project -- this fixed
our Bazel build issue.

Out of curiosity do you have an example of bazel build configs for building js? Are you using
@build_bazel_rules_nodejs//:defs.bzl?
I recently attempted calling react-scripts build using nodejs_binary but it didn't work out.

@bugzpodder No, we have something homegrown, very minimal. As such, I cannot comment oon any build_bazel_rules_nodejs issues.

I cannot be certain, but the travis build error seems like flaky tests to me. All errors are caused by "timeout exceeded", seemingly not related to the changed node path in the scripts.

@gaearon Is there any specific reason why this PR is rejected?

@gimpf this was done when they did the branch cut from next to master.  feel free to change the target branch.


chore(deps): update dependency eslint to v8.36.0

This PR contains the following updates:

Package
Type
Update
Change

eslint (source)
devDependencies
minor
8.35.0 -> 8.36.0

@types/eslint (source)
devDependencies
patch
8.21.1 -> 8.21.2

Release Notes

eslint/eslint
v8.36.0
Compare Source
Features

c89a485 feat: Add checkJSDoc option to multiline-comment-style (#16807) (Laurent Cozic)
f5f5e11 feat: Serialize parsers/processors in flat config (#16944) (Nicholas C. Zakas)
4799297 feat: use @eslint-community dependencies (#16784) (Michaël De Boey)

Bug Fixes

92c1943 fix: correctly iterate files matched by glob patterns (#16831) (Nitin Kumar)

Documentation

b98fdd4 docs: Update README (GitHub Actions Bot)
caf08ce docs: fix estree link in custom formatters docs (#16967) (Milos Djermanovic)
3398431 docs: Custom Parsers cleanup/expansion (#16887) (Ben Perlmutter)
19d3531 docs: Update README (GitHub Actions Bot)
b09a512 docs: detect and fix broken links (#16837) (Nitin Kumar)

Chores

602b111 chore: upgrade<EMAIL_ADDRESS>(#16978) (Milos Djermanovic)
43c2345 chore: package.json update for @eslint/js release (ESLint Jenkins)
00afb84 chore: upgrade<EMAIL_ADDRESS>(#16977) (Milos Djermanovic)
698c5aa chore: upgrade<EMAIL_ADDRESS>(#16976) (Milos Djermanovic)
75acdd2 chore: lint more js files in docs (#16964) (Milos Djermanovic)
89d9844 ci: bump actions/add-to-project from 0.4.0 to 0.4.1 (#16943) (dependabot[bot])

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

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

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: yarn.lock
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.24/images/create?fromImage=renovate%2Fsidecar&tag=latest: dial unix /var/run/docker.sock: connect: permission denied


[FEATURE] Support another technology to define and orchestrate the image creation inside a pod

Is there an existing feature request for this?

[X] I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.
A use-case.
We want to explore the possibility of supporting another stack for delegating the image build inside a Pod. Most prominent example would be Argo Workflows.
Describe the solution that you would like.
A SHIP that can shed some light into this topic, using Argo Workflows. The SHIP besides providing a deep understanding of what aspects of the controller would need to be extended, should provide a concise explanation on why this is beneficial for our end users.
Describe alternatives you have considered.
None. We can explore other technologies besides Argo. But looking at the relevance, features and adoption from Argo, its definitely a good starting point.
Anything else?
In a nutshell, this could provide a proposal on how we can opt-in for another backend technology besides Tekton Pipelines.

/assign @ayushsatyam146

/assign @MaheshRKumawat


Fix link to company announcement in README

Change Summary
The link in the readme about the company announcement is actually simply a link to the blog/announcement page of pydantic's website, and it is not immediately clear that this isn't a broken link, added to the fact that people have to search for the actual page that was referred to. This PR modifies it to point directly to the actual announcement.
Related issue number

Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[x] Unit tests for the changes exist
[x] Tests pass on CI
[x] Documentation reflects the changes where applicable
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

The release notes test fails, but this PR shouldn't have have any release note as it is a trivial readme change.

Thanks @adamency


Microsoft Azure Load Test (MALT) Integration

This PR (re-)introduces support for Microsoft Azure Load Test (MALT).
MALT will be added as a secondary load testing framework next to the existing Locust implementation. The main use-case for MALT is the embedded load testing in E2E. It's embedded into the E2E pipeline and can be selected at pipeline execution:

Embedded load testing can be enabled / disabled by checking / unchecking "Run load testing" the load testing framework is selected via "Select load testing framework".

The selection made here also applies to "Run Chaos testing" which also contains a load test run while executing chaos experiments.
The load test is using a JMX file stored in /src/testing/loadtest-azure/scripts/catalogue-test.jmx as well as some load test-related parameters loaded from:
https://github.com/Azure/Mission-Critical-Online/blob/fdba4f9edf67e9468c4f25e5797032dc2220122c/.ado/pipelines/config/configuration.yaml#L57-L67
Environment-specific parameters like the Front Door FQDN are set via parameters. The MALT service resource is deployed via Terraform, the pipeline implementation uses PowerShell-based wrapper scripts to interact with the MALT data plane API.

Terraform: /src/testing/loadtest-azure/infra
Wrapper Scripts: /src/testing/loadtest-azure/scripts

Merged into feature/chaos-may-22. Closed.


Compatible with higher version 3.0 ?

➜  ~ tmux
[exited]
➜  ~ 62;4c

Can confirm, not working with tmux 3.0

See #254


Run #myTraceFile has not been completed successfully.

Run #myTraceFile has not been completed successfully.
This is all that I can get to show up in default.html after starting/stopping.
Can you please add the source code for the JS files found in:
\sqlcc-master\SQLCC.Impl.HtmlCodeHighlighter\sqlcc_output.zip
several of these JS files are "minified", and I don't see those anywhere else in this repository.

i still have the same issue

somehow its not working even for me...
I am making my own :)

Please let me know if this issue is still open.


Fix Trip Page to show delivery address

Fix the trip page so that delivery addresses are shown.  This means the ability to load all delivery addresses owned by a fleet, or owned by a fleet that the current user has access to.  Remove duplicates.

Done.


feat(workflow): add workflow to push 'dev' tag

Marking this as draft as we need to have a discussion about this.

closing this as we don't really need this for now


qa_crowbarsetup: enable wickedd-nanny

because nanny was enabled in /etc/wicked/common.xml of the SP2 image
and without the daemon, network cannot be started or reconfigured

@rsalevsky updated the commit message

actually a lot of things are working without nanny, but in the new ECP deployment I found that the network remained a /24 (which was the initial static setup done in onadmin_prepareinstallcrowbar)
but I wanted it to be a /21 and even an wicked ifreload broke the network then

actually, I'm not sure. I did have a cloud that did not have wickedd-nanny running for some reason, but I also see it running in a virtual cloud env without this patch.

let's close for now until I get an opportunity to better debug such a setup again


Change reference assemblies link to Microsoft Docs

Because there's now an article about reference assemblies in .NET Guide, better to link there instead of Github.

@MSDN-WhiteKnight : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Hotfix/0.0.10

Fix issue #10

Thank you. I couldn't reproduce the issue, so I hope your fix works. :-)


BUILD-1081: Support Hermetic Builds

Konflux currently does not support compiling k8s 1.30 dependencies, which reqiures go 1.22 and proper workspace configuration setup for k8s.io/* dependencies. Since we don't need k8s.io 1.30 APIs right now, the direct dependencies for k8s.io were downgraded to v0.29.7.
Following that, the minimum golang version in go.mod was downgraded to 1.21, and the Dockerfile was updated to remove the go toolchain override. Use of vendored code (in vendor directory) replaced go mod download.

@ramessesii2 I added most of your PR logic from #55 here. It needed the golang and k8s downgrades to work. PTAL.

looks good to me.


python38Packages.tinydb: 4.5.0 -> 4.5.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.tinydb is: "Lightweight document oriented database written in Python"
meta.homepage for python38Packages.tinydb is: "https://tinydb.readthedocs.org/"
meta.changelog for python38Packages.tinydb is: "https://tinydb.readthedocs.io/en/latest/changelog.html"
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 4.5.1 with grep in /nix/store/7f91mjhk08ixd5wwfqqzilbn3pmf6cz1-python3.8-tinydb-4.5.1

found 4.5.1 in filename of file in /nix/store/7f91mjhk08ixd5wwfqqzilbn3pmf6cz1-python3.8-tinydb-4.5.1

directory tree listing: https://gist.github.com/8efc78adf03fa1bd13aba61fab2156fe

du listing: https://gist.github.com/c29cee295fe6d10d0c6ad0b826334939

Rebuild report (if merged into master) (click to expand)

12 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
archivy
python38Packages.tinydb
python39Packages.tinydb

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7f91mjhk08ixd5wwfqqzilbn3pmf6cz1-python3.8-tinydb-4.5.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.tinydb https://github.com/r-ryantm/nixpkgs/archive/42183d1c8842d4984f4dc774a9650f3074bb6e21.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7f91mjhk08ixd5wwfqqzilbn3pmf6cz1-python3.8-tinydb-4.5.1
ls -la /nix/store/7f91mjhk08ixd5wwfqqzilbn3pmf6cz1-python3.8-tinydb-4.5.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

archivy
python38Packages.tinydb
python39Packages.tinydb

Maintainer pings
cc @marcus7070 for testing.

Result of nixpkgs-review pr 135364 at 42183d1c run on aarch64-linux 1

3 packages built successfully:

archivy
python38Packages.tinydb
python39Packages.tinydb


Glutin updated to 0.8

Glutin has updated to 0.8 about 16 hours ago, and it changes how windows are created. Instead of each window controlling it's own event loop, you now create a separate event loop and pass it into the window when it's first created. It apparently fixes some issues on macos, ( https://github.com/tomaka/winit/pull/132 ), so we should try and update the glutin backend soonish. See https://github.com/tomaka/winit/pull/126 for additional information

@keringar Sweet, I've been waiting for glutin to adopt the new winit API for a while now. Nice to hear it's finally landed!

We will need to update all examples, but the old fashion poll_events() method exists on EventLoop quite similar to before.

This has just been done in #1251, closing


Refactor editor extract.py

Fixes #59271.
extract.py previously used string operations to manage extracted message information. It was quite hard to extend reliably.
This PR makes extracted message a dictionary of Message objects and serialize them at the end of operation.
It takes almost the same time and produces the same editor.pot as before the refactoring. (Relies on dictionaries being ordered, which is true since Python 3.6. Using previous versions won't produce the exact same text file, but still logically the same.)

Thanks!


blabla

sorry

Turnover on the project may be slow but there is no way it can be classified as "no more developed and maintained".
There is an equally long list of issues in Notepad3, including a major one I raised more than a month ago which has not received any acknowledgement yet. Both projects can be considered largely feature-complete save for a few bugs that need to be fixed.
Unless you are ready to contribute to either of the projects, I think you should cease and desist from this behaviour.

blubb, why do you think do XhmikosR say nothing any more and give no support any more ?
since year when he did no answering any more !
If you're too lazy for reading behind, you lead others into the wrong..
https://github.com/XhmikosR/notepad2-mod/issues/143
https://github.com/XhmikosR/notepad2-mod/issues/144
https://github.com/XhmikosR/notepad2-mod/issues/148
https://github.com/XhmikosR/notepad2-mod/pull/172
https://github.com/XhmikosR/notepad2-mod/pull/179
https://github.com/XhmikosR/notepad2-mod/issues/191
@XhmikosR should ma by say by self what's going on ? :)
best regards
Blacky

In fact, as of the time of writing this post, the last commit (06f5999) is just about a day old and it is pull request #182 which fixes issue #37.
Note that this is a clearly reproducible error which has been fixed in a well-documented pull request. Contrast this with #179 which was closed by the owner or #172 which ended with some abusive language.
My therefore point is, until @XhmikosR or any of the other contributors post that this project has been discontinued, or stops accepting well-documented pull requests, this project cannot be described as "no more developed and maintained". If, though, for one reason or the other, you feel like this project doesn't suit your needs, please move on to your preferred fork and stop littering this repo as @XhmikosR asked you to.

upps.. oky...

https://www.essential-freebies.de/board/viewtopic.php?f=11&t=6507&p=141180#p141180

That anyone reading this thread in future may know what was truly discussed before blackcrack vandalised his posts, I post here the original messages based on entries from the email notifications I received for this thread.

blackcrack@20170731T0252Z

notepad2-mod it is no more developed and maintained ..
please go to notepad3, because
https://github.com/rizonesoft/Notepad3
it is maintained and developing
best regards
Blacky

Source<EMAIL_ADDRESS>
blackcrack@20170806T0016Z

blubb, why do you think do XhmikosR say nothing any more and give no support any more ?
since year when he did no answering any more !
 You are resentful ?
should i be it also ?
hey if i do a mistake and i clouse the issue, should you also stop it, because i have see, i have do a fail, but if you want start a War in the net ? huhh.. all the other see what for a Carackter you have..
soooooo, you mailserver have the ip <IP_ADDRESS> ..  gmailaccound .. humm franzalex
oookeyyy....

No, I have no grudge against you. Neither am I resentful. It is up to you though to decide how you want to react.
The objective of my action was solely to allow anyone coming across this later to know what was discussed since you decided, for reasons best known to you, to alter your initial messages in such a way that the rest of the conversation did not make sense any more. My intention is not to start 'a War in the net' [sic].
PS: Besides refreshing the IP addresses every few hours, my ISP masks the true IP addresses of their clients so you'll not have any reliable way of knowing it unless I explicitly provide it. In short:

Do not even bother using the IP in the EML files posted.

Please, guys, there's no gain in continuing this discussion.
@blackcrack: you should NOT have done what you did, editing your posts. And even you shouldn't have made the issue in the first place. You could have asked me via email. It's at least unethical what you did.
I'm just one person. And besides, the main reason I made this, was because back in 2009 Kai Liu didn't maintain his patches any more. So, lack of knowledge (I never claimed to be a C developer), work and personal life don't allow me to spend almost any time on this project. That is why I have asked for help years ago. No serious proposition so far.

Thank you, @XhmikosR for your moderation on this issue.

I'm not even sure at this point what I want to merge and what not.
In the past I kept the notepad2 branch with upstream code and master with custom one.
So anyway, the project just needs some people willing to take care of maintenance and who know what open source is meaning nothing should go in without discussing/reviewing it with the others.


Update compliance-processes.md

@frachkid : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Re-Check on Issue/Comment content change if things have changed in between

Feature Description
currently if you edit an issue or comment, we use the value we got on init load of the page and then submit as new state whatever is in the editor as new value.
If you have some other person edit something in between this, it will get overwritten without even being noticed.
we could either add some lock mechansim that only allow one to edit, but we then have to add a lot of complexity e.g. when to timeout ...
... or we could add an optionall parameter on the save proggess that submits the content hash of the old value, witch the backend can check on an update. if it does not macht we can show an error to the user and not save it ...
... the user then can either force update or reload and edit new ...
... instead of an content hash we could also add version number to issue/comment content that can be checked and are itterated
the second proposal only need to update the WebUI and the update functions...
Screenshots
No response

well just shows that I'm currently not up to date to all issues/pulls :/
but thanks nice :tada:


Examples don't work

Hi gus，I tried to debug the examples, But found it didn't  work.
steps：

cd examples
npm install
npm start

After entering the page, some examples do not work properly.
Hope to get some advice

oh, When I use yarn, it works. I will close this issue


pathway_errorbar() : The 'method' column in the 'daa_results_df' data frame contains more than one method. Please filter it to contain only one method.

Describe the Bug
Hello. I'm still new to this field, so I'm studying it little by little and referring to it often.The reason I'm commenting like this is because I had a problem with the error bar plotting part while following the code.
Reproducible Example
I used example data from QIIME2 "Moving picture Tutorial". After that, for the count of KO pathway I used PICRUSt2 and got "pred_metagenome_unstart.tsv". After running ALDEx2 through pathway_daa(), I just left with the results of the "ALDEx2_Wilcoxon rank test".  Group data was used by "gut" and "tounge" in 'metadata$body.site'.
p <- pathway_errorbar(abundance = kegg_abundance_t30,
                      daa_results_df = Top30,
                      Group = metadata$body.site,
                      ko_to_kegg = T,
                      p_values_threshold = 0.05,
                      order = "pathway_class",
                      select = NULL,
                      p_value_bar = T,
                      colors = NULL,
                      x_lab = NULL)

Expected Behavior
I was expecting to get Error bar plot with 30 lowest adjusted p-value.
Actual Behavior
I got a error below.
The 'method' column in the 'daa_results_df' data frame contains more than one method. Please filter it to contain only one method.
The 'group1' or 'group2' column in the 'daa_results_df' data frame contains more than one group. Please filter each to contain only one group.
Error in pathway_errorbar(abundance = kegg_abundance_t30, daa_results_df = Top30,  :
  Visualization with 'pathway_errorbar' cannot be performed because there are no features with statistical significance. For possible solutions, please check the FAQ section of the tutorial.

Even I have adjusted p values under 0.05, why does error says there's no statistical significance? Is there more caculation inside the code?
Environment Information:

Operating System: Windows & RStudio
R Version: 4.2.3
Package Version: 1.7.3

Additional Context
I got the same error with MetaCyc too.

Hello,
Thank you for reaching out and providing a detailed description of the issue you're facing with the error bar plotting in our package. It seems like there might be a specific issue with the dataset or the way the script is handling the data.
To assist you better, could you please send me the dataset you're using (in this case, the "pred_metagenome_unstart.tsv" file) as well as the entire script that you're running? This will help me to reproduce the error on my end and investigate the cause more thoroughly.
You can attach the files in your response or share a link to where they are hosted. Once I have these files, I'll be able to provide more targeted assistance.
Looking forward to your response.
Best regards,
Chen YANG

Thanks for your response.
Here's my dataset and code script. Dataset.
To explain my dataset,
I first used the code with My_data dataset by MetaCyc. But there was no significance in adjusted p-values. So I was wondering if there is a way to use p-value rather than adjusted p-value in errorbar.
For that, I was practicing with Example dataset by KO. Although it had significant pathways in adjusted p-value, unlike My_data, it had the same error.
So I want to know what was the matter of my data or code. And if it's okay, I want to ask if I can use p-value instead of adjusted p-value in the code.
Thanks,
Kris

I also got the same error.


Minor update to travis.yml.

Reviewed 1 of 1 files at r1.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from the review on Reviewable.io


Please make a decompile file also

Please make a decompile file that can decompile marshal py3 2.1 and 2.7 all python 2,3 msrshal . You are working well that's why I'm requesting you to please make a decompile tool for marshal. That cannot have any error. Like bad marshal data etc.
Thank you

Yes Please also make a decompile of Deobfuscate of this


Implied readonly fix

Fixes #20
Added test for implied readonly.
Fixed HttpCache to imply readonly for a write state of 'prompt' (in addition to 'denied').

Closing as per the discussion in the original issue.


[ROCm] Fix some kernels failed unit tests

This pull request is to fix some of the failed unit tests in ROCm platform, specifically,

adjusted tests in test_activation.py, test_attention.py , test_pos_encoding.py and test_cache.py in tests/kernels to fix the failed tests
refactored the code to get default atol and rtol values for use in torch.allclose

Tests:
To run the associated tests on ROCm platform, first we need to be inside the docker container with ROCm pytorch and vllm install, and then copy the tests directory to the vllm installed location, and then run the test using pytest.
Use the environment variable PYTORCH_TEST_WITH_ROCM=1 if inside the ROCm 5.7 docker image as shown in the below example:
This environment variable is already set inside the ROCm 6.0 docker image.
root@xxx:/opt/conda/envs/py_3.10/lib/python3.10/site-packages/vllm-0.2.7+rocm573-py3.10-linux-x86_64.egg/vllm/tests/kernels# PYTORCH_TEST_WITH_ROCM=1 pytest test_activation.py
====================================================================================== test session starts ======================================================================================
platform linux -- Python 3.10.13, pytest-7.4.2, pluggy-1.3.0
rootdir: /opt/conda/envs/py_3.10/lib/python3.10/site-packages/vllm-0.2.7+rocm573-py3.10-linux-x86_64.egg/vllm/tests/kernels
plugins: shard-0.1.2, xdoctest-1.1.0, xdist-3.3.1, flakefinder-1.1.0, rerunfailures-12.0, hypothesis-5.35.1, anyio-3.7.1
collected 216 items
Running 216 items in this shard

test_activation.py ...................................................................................................................................................................... [ 76%]
..................................................                                                                                [100%]

======================================================================================= warnings summary ========================================================================================
../../../../torch/cuda/__init__.py:546
  /opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/cuda/__init__.py:546: UserWarning: Can't initialize NVML
    warnings.warn("Can't initialize NVML")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
================================================================================ 216 passed, 1 warning in 1.82s =================================================================================

cc @tjtanaa

Hmmm it seems some of the tests are failing due to allclose.
https://buildkite.com/vllm/ci/builds/495#018d323c-6fa7-47ed-a078-04a2bc14f21c/51-7825
We are soft-failing kernel test due to GPU memory, but it shouldn't have any other error than CUDAOutOfMemory.

Hmmm it seems some of the tests are failing due to allclose.
https://buildkite.com/vllm/ci/builds/495#018d323c-6fa7-47ed-a078-04a2bc14f21c/51-7825
We are soft-failing kernel test due to GPU memory, but it shouldn't have any other error than CUDAOutOfMemory.

Will check the failed ones. May be the message below of "All checks have passed" can be "improved"?

Yeah i'm trying to figure that out sorry.

Yeah i'm trying to figure that out sorry.

@simon-mo Can this pull request be merged now? The longer it stays, more potential conflict will occur.


How to point duffle on windows to remote docker engine?

Like the title says, I'm attempting to perform a basic duffle build from the examples, but I'm unsure how to point duffle to a non-local docker engine.
Use case is we'd like to package our deployment and require as little pre-work as possible with as simple of an execution process as we can make it. Having our clients need to install a docker engine to be able to run our package would be a bit much.

I don't have access to a Windows machine right now, but I think you can use the default Docker environment variable DOCKER_HOST to point to the daemon.
set DOCKER_HOST=tcp://<ip-of-docker-daemon>:2376

It is conventional to use port 2375 for un-encrypted, and port 2376 for encrypted communication with the daemon. (see https://docs.docker.com/engine/reference/commandline/cli/)

Let me know if this works for you.


AppCompat dependency?

Hi! Thank you for sharing this library. I was looking through your code and stumbled upon the AppCompat dependency on :bottomsheet module that doesn't appear to be used anywhere.
Since the AppCompat itself is relatively heavy, I was wondering is there a reason for you to have it as dependency?

Thanks for pointing out. Yes, it seems we should remove it. Feel free to open PR or I'll fix it later.

Thanks for pointing out. Yes, it seems we should remove it. Feel free to open PR or I'll fix it later.

Here's a PR: #21


update(plugins): generate fresh changelogs and readmes

What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
/area plugins
What this PR does / why we need it:
Changelogs and readmes haven't been updated since a while.
Which issue(s) this PR fixes:
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Adding Darkmatter to User based on Cronjob

Hi again! Hopefully this is last issue question for a while.
I was looking at the cronjob classes and saw that you already do what I want to do with curl TrackingCronjob.class.php and I have to ask
Is it possible to check to see if user has been logged in within the past 24 hours and if so give him a arbitrary sum of darkmatter?
And then run the cron job at 0 UTC time?
The arbitrary sum will be based on a curl on another website which I already have setup.
But as the user won't be logged into the cronjob php, I'm assuming the if(isset($hash_balance)) { $USER[$resource[921]]		+= $hash_balance; } unless we define the user in the cron job class?
Or can i use the global $USER and then set $USER['id'] manually?
On top of that, I'd need to get a list of the users and do a loop checking each their last login status.
So doing that... Whats the best way to get a list of all the users and their last login time in the cron php and then using the global variables to add DM to their accounts?

Look at the InactiveMailCronjob i check the last online time there.
You can do it with one sql query like UPDATE users SET darkmatter = darkmatter + X WHERE onlinetime < time - 24h

Thank you! I got it working!


Removed an unneeded space

Spotted this while reading a doc, figured a PR was faster than explaining.

Learn Build status updates of commit 4593629:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

business-central/warehouse-how-to-move-items-ad-hoc-in-basic-warehousing.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Thanks for this. However, this file is part of a project to update the warehouse management content as a whole. I checked, and the same edit was made there. Closing this PR to avoid conflicts. Thanks again.


[1.1.0] make package wrong version 0.0.0-0

Describe the bug
when building sysmon with newly release 1.1.0 code (git commit edc74fc41301d78ad9c9bedcc73f384cff2f7900), make package use a non-matching version aka 0.0.0-0 instead of 1.1.0-1.
previously worked as 1.0.0-1 (commit 9bca3734721a01cb2ac6e2e3adc40ecdcad3151e)
To Reproduce
following https://github.com/Sysinternals/SysmonForLinux/blob/main/BUILD.md#make-packages
make
make packages

Sysmon version
edc74fc41301d78ad9c9bedcc73f384cff2f7900
Distro/kernel version
tested on ubuntu 22.04 and 20.04
Sysmon configuration
N/A
Logs
(ubuntu 22.04)
https://github.com/juju4/ansible-sysmon/actions/runs/4456447238/jobs/7826904245#step:7:11077
  changed: [instance] => (item={'c': 'make packages', 'chdir': '/var/_install/sysmon/build', 't': '/var/_install/sysmon/build/deb/sysmonforlinux_<IP_ADDRESS>-1_amd64.deb'}) => {
      "ansible_loop_var": "item",
      "changed": true,
      "cmd": [
          "make",
          "packages"
      ],
      "delta": "0:00:04.141773",
      "end": "2023-03-18 17:18:57.896421",
      "invocation": {
          "module_args": {
              "_raw_params": "make packages",
              "_uses_shell": false,
              "argv": null,
              "chdir": "/var/_install/sysmon/build",
              "creates": "/var/_install/sysmon/build/deb/sysmonforlinux_<IP_ADDRESS>-1_amd64.deb",
              "executable": null,
              "removes": null,
              "stdin": null,
              "stdin_add_newline": true,
              "strip_empty_ends": true
          }
      },
      "item": {
          "c": "make packages",
          "chdir": "/var/_install/sysmon/build",
          "t": "/var/_install/sysmon/build/deb/sysmonforlinux_<IP_ADDRESS>-1_amd64.deb"
      },
      "msg": "",
      "rc": 0,
      "start": "2023-03-18 17:18:53.754648",
      "stderr": "",
      "stderr_lines": [],
      "stdout": "[  2%] Built target checkEBPFsizes\n[ 17%] Built target sysmonLogView\n[ 18%] Checking sysmonEBPFkern4.15_core.o\n\n[100%] Built target sysmon\ndpkg-deb: building package 'sysmonforlinux' in 'sysmonforlinux_0.0.0-0_amd64.deb'.\nNo rpmbuild found\n[100%] Built target packages",
      "stdout_lines": [
          "[  2%] Built target checkEBPFsizes",
          "[ 17%] Built target sysmonLogView",
          "[ 18%] Checking sysmonEBPFkern4.15_core.o",
          "",
          "[100%] Built target sysmon",
          "dpkg-deb: building package 'sysmonforlinux' in 'sysmonforlinux_0.0.0-0_amd64.deb'.",
          "No rpmbuild found",
          "[100%] Built target packages"
      ]
  }

note that t is a for expected resulting file to be and from ansible role, not related to the build itself.
same on ubuntu 20.04: https://github.com/juju4/ansible-sysmon/actions/runs/4456447238/jobs/7826904285#step:7:14781
Expected behavior
build for current version or above, else could lead to mismatch from package manager

Hi - You can set env variable VERSION= and it will be respected in our build scripts. Does that work for you?

Does not seem so. still 0.0.0
https://github.com/juju4/ansible-sysmon/actions/runs/4519184319/jobs/7959525720#step:7:4929
like previously
https://github.com/juju4/ansible-sysmon/actions/runs/4463993537/jobs/7839727245#step:7:4935
note that I didn't change sysmon_build_version variable but only used for install of resulting package and ansible play's idempotence.

Still in an issue here
https://github.com/juju4/ansible-sysmon/actions/runs/6284397818/job/17065732603#step:7:5131
       "stdout": "Consolidate compiler generated dependencies of target checkEBPFsizes\n[  2%] Built target checkEBPFsizes\nConsolidate compiler generated dependencies of target sysmonLogView\n[ 17%] Built target sysmonLogView\n[ 18%] Checking sysmonEBPFkern4.15_core.o\n\nConsolidate compiler generated dependencies of target sysmon\n[100%] Built target sysmon\ndpkg-deb: building package 'sysmonforlinux' in 'sysmonforlinux_0.0.0-0_amd64.deb'.\nNo rpmbuild found\n[100%] Built target packages",
      "stdout_lines": [
          "Consolidate compiler generated dependencies of target checkEBPFsizes",
          "[  2%] Built target checkEBPFsizes",
          "Consolidate compiler generated dependencies of target sysmonLogView",
          "[ 17%] Built target sysmonLogView",
          "[ 18%] Checking sysmonEBPFkern4.15_core.o",
          "",
          "Consolidate compiler generated dependencies of target sysmon",
          "[100%] Built target sysmon",
          "dpkg-deb: building package 'sysmonforlinux' in 'sysmonforlinux_0.0.0-0_amd64.deb'.",
          "No rpmbuild found",
          "[100%] Built target packages"
      ]

Not sure if there is something specific to Ansible but I just did the following which worked just fine:
~/SysmonForLinux$ rm -rf build
~/SysmonForLinux$ mkdir build
~/SysmonForLinux$ cd build/
~/SysmonForLinux/build$ export VERSION=**<IP_ADDRESS>**
~/SysmonForLinux/build$ cmake ..
~/SysmonForLinux/build$ make
...
...
...
[ 91%] Building C object CMakeFiles/sysmonUnitTests.dir/sysmonmsgop.c.o
[ 92%] Linking CXX executable sysmonUnitTests
[100%] Built target sysmonUnitTests
Scanning dependencies of target sysmonEBPFkern4.16
[100%] Built target sysmonEBPFkern4.16
Scanning dependencies of target sysmonEBPFkern5.6-
[100%] Built target sysmonEBPFkern5.6-
~/SysmonForLinux/build$ make packages
dpkg-deb: building package 'sysmonforlinux' in 'sysmonforlinux_**1.2.3-4**_amd64.deb'.


Cross domain, with 3rd party cookies blocked.

Hello,
So it seems this does not work when users block 3rd party tracking - is there any proposed workarounds?
I actually have my SDK on two web domains and need for them to share a state - any suggestions?

It seems that this is not possible. But I would like to know if there is some workaround. I have similar project sysend.js, and have the same issue. Cross-Domain don't work on Safari when 3rd party tracking is blocking is enabled.

@ydennisy Sorry this is now just being addressed.  @jcubic You're correct.  This will not work when 3rd party tracking is blocked and unfortunately it is blocked by default on Safari.  I am not aware of a workaround.  Thanks for responding @jcubic .  I'm going to close this.  If either of you would like this be be re-opened, please let me know.

I've just added a note in Readme so anyone knows that this doesn't work in Safari. Found this in some other project that uses LS (found link on StackOverflow).


Wink climate component does not create cool_on attribute

Home Assistant release with the issue:

0.67.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

https://www.home-assistant.io/components/climate.wink/
Description of problem:
cool_on attribute does not get created.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:
in wink.py should return self.wink.cool_on() not heat_on().
@property
def cool_on(self):
"""Return whether or not the heat is actually heating."""
return self.wink.heat_on()

Thank you! I can now see this in my entity attributes.


Properly generates the url to a Middleware Manager Provider.

Topology links to a Middleware provider were wrong, this PR fixes the link.
Changes https://localhost/ems_middleware/show/2
to https://localhost/ems_middleware/2
Fixes #12498

@miq-bot add_label providers/hawkular, bug

@Jiri-Kremser could you take a look?

LGTM

@miq-bot assign @bronaghs

@miq-bot assign @dclarizio
cc @martinpovolny @h-kataria


WIP: Feature/locations newsletter

Done:

In location.js (template), add Newsletter component & image with temporary text
Newsletter shows when !location.isOpen (as a starter, to avoid adding further checks on Contentful that could be forgotten/misinterpreted)
In contentful: add check newsletterActive to Contentful in case location doesn't want a newsletter displayed and newsletterLink (for Action Link in Newsletter Form)
Create strings in en.json and de.json for title, subtitle, First Name and Email labels and placeholders, privacy agreement and subscribe button
Pass ActionLink as a prop from the location page to the newsletter

To do:

Ask Luca about Mailchimp link (right now link is hardcoded in newsletter.js)
Create Notion Page with documentation on how to implement a newsletter for the location (WIP: https://www.notion.so/techlabs/WIP-How-to-implement-a-location-newsletter-b4a1dbd0a9b54b5bb93fd489d6afc16d)

Info:
For now, CodeAtHome action link stays hardcoded as a prop to the newsletter component in program/remote.js - should it be added to Contentful as well?

The Newsletter Link should be added through contentful I guess 🤔

The Newsletter Link should be added through contentful I guess 🤔

Yes, I thought the same - there is a field in Contentful/locationPage to add it! I'll check where can the locations get this link to add it to the guide on Notion :)

Yes, I thought the same - there is a field in Contentful/locationPage to add it! I'll check where can the locations get this link to add it to the guide on Notion :)


Test pr

Checklist before submitting

[ ] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

Codecov Report

Merging #127 (12df599) into main (eaab827) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #127   +/-   ##
=======================================
  Coverage   96.20%   96.20%
=======================================
  Files          23       23
  Lines        2106     2106
=======================================
  Hits         2026     2026
  Misses         80       80

Flag
Coverage Δ

unittests
96.20% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Allow per-path exceptions

The .nsprc file currently lets me completely turn off an advisory.  Usually, I just want to turn off an advisory for one error.  For example, today I ran into advisory https://nodesecurity.io/advisories/39 for path:
grunt-google-cdn > google-cdn > bower > bower > handlebars > uglify-js
In this case, the problem is that module bower needs to update module handlebars (which has already done the work of updating uglify.js to version that has a fix.)  However, adding this advisory to .nsprc would turn off the warning for all occurrences of uglify.js, of which there could be many others independent of bower.  Rather than a simple array of advisories in .nsprc, the structure could be:
{
  "exceptions": [
     "https://nodesecurity.io/advisories/39": [
        "grunt-google-cdn > google-cdn > bower > bower > handlebars > uglify-js",
        "other > path"
      ]
     "https://nodesecurity.io/advisories/31": [ other paths...]
   ]
}

@plynchnlm Yes that's a good point and we have discussed this current limitation before and want to make it better. I'm sure we could offer a few ways to specify exceptions, my biggest concern is making it easy for you to actually create and manage those. (although on the one hand I'm not sure exceptions should be easy as it makes it less painful to make potential issues to go away :)
@nlf any concerns with the format above?

I just ran into a case where this would be especially helpful.  Maintainers of package bower decided to close a request to update bower's handlebars dependency to a version that did not depend on a vulnerable version of uglify.js, because they are not using the part of handlebars than runs uglify.  However, nsp will continue to report bower as containing a vulnerable uglify.js.  If I use the current exception mechanism and exclude that vulnerability report, then I might miss cases of other packages which also use a vulnerable uglify.js but unlike bower really are affected by it.

@plynchnlm Thanks for the example. This is certainly something on our plate. Not sure when we will get to it but it's certainly on the list.

I think it might be better to list all of the advisories for one path, rather than all of the paths for one advisory:
{
  "path-exceptions": {
    "grunt-google-cdn > google-cdn > bower > bower > handlebars > uglify-js": [
      "https://nodesecurity.io/advisories/39",
      "https://nodesecurity.io/advisories/48"
    ],
    "other > path": [ other advisories... ]
  }
}

This way when a dependency is upgraded you can delete an entire block from the file, rather than having to chase up and down in the file for all of the advisories that mention that particular path.

I don't care too much as long as there is a way to do it, but I'm not convinced that is better.  If ugliify-js is used in 5 different paths, then when it is updated with a fix to a particular vulnerability, with the approach suggested by @wolfgang42 you will still have to go to multiple places in the file to remove the exceptions.  Maybe it depends on the scenario as to which structure is better, and I'm not sure which scenario would be more common.  Perhaps nsp could support both-- though supporting just either one would be a nice improvement.

I just started using NSP and I agree, this an issue for us.  I have one package that uses a vulnerable module in an optional component we don't use. The same advisory affects other modules and I do care about it.
Also, you should be able to specify both the module and the package version. Then as the package version changes you're forced to re-evaluate your exceptions.
This all seems straightforward enough, I'd be up for submitting a pull request but I'd like the maintainers to bless a solution/format etc so it's not a waste of effort.

this is something that we have plans for in the works. thanks for the offer, though! we're making lots of changes to both incoming and outgoing data when performing a check that will allow us to do things like this in a more friendly way.

I had the same requirement and wrote this wrapper script which allows to filter out vulnerabilities based on path packages:
#!/usr/bin/env node

'use strict'

const path = require('path')
const nsp = require('nsp')
const stdout = process.stdout

const payload = {
  shrinkwrap: path.join(__dirname, '/npm-shrinkwrap.json'),
  package: path.join(__dirname, '/package.json')
}

// Filters nsp reports based on nspIgnoreDependencies array in package.json
function filterReports (reports) {
  if (!reports || !reports.length) return []
  const ignoreDeps = require(payload.package).nspIgnoreDependencies || []
  const filteredReports = []
  reportLoop: // eslint-disable-line no-labels
    for (let report of reports) {
      for (let dependency of ignoreDeps) {
        if (report.path.includes(dependency)) {
          continue reportLoop // eslint-disable-line no-labels
        }
      }
      filteredReports.push(report)
    }
  return filteredReports
}

nsp.check(payload, function (err, data) {
  const reports = filterReports(data)
  stdout.write(nsp.formatters.default(err, reports) + '\n')
  if (reports.length || err) process.exit(1)
})

The script makes use of a nspIgnoreDependencies array in package.json that uses the same format as the path components for its items, e.g.:
{
  "nspIgnoreDependencies": [
<EMAIL_ADDRESS>  ]
}

I hope it's of some use to someone. :relaxed:


Recyclerview in running activity showdata but in pdf not showing data

Hi @akumakhalibagas  sorry for the late reply , Please check my demonstration here. If you face stuck then knock me by comment here and if possible then please post here your code also. I think you are putting the only xml into the pdf generator not the view instance. If anyone wants to set dynamic view in pdf generation then he had to put the view instance into it. Thank you

Hi @akumakhalibagas
Thank you all for the support. Please kindly star and fork and send me the app links you all are using it. If there is no confidentiality then I will list them in my readme.md file.


It isn't possible to set FloatingIPs to the resource-configuration of the ERT (OpenStack) is it?

Hi there!
I configured my director and the ERT with your OM tool and everything works fine except setting an exisiting FloatingIP to the resource configuration of the ERT.
Neither with the official OpsMan-Api nor with your tool I am able to set FloatingIPs...
Is this "feature" on your roadmap or do I have to set those floatingips afterwards via the openstack cli?
Cheers

@staynerzone - apologies for the delay in response! Could you actually point me to the spot in the ops-manager API that allows you to configure this?

@zachgersh - no problem at all :) I'm able to set the FloatingIPs only over the OpsMan GUI (https://{{ OPSMAN_IP }}/products/{{ ERT_UUID }}/resources/edit). There is a column named "FloatingIPs" which seems not to be configureable through the API :(
Why do I want to use this feature? I'm setting up an PoC installation of PCF where I use haproxies instead of an external LB. And those haproxies do need a floating_ip...
I found an ugly workaround with decrypting the /var/tempest/workspaces/default/installation.yml, sed the floating_ips into it and encrypt the whole yml back again.
I'm looking forward to find the "right" way of doing this :)
Could you help or isn't this possible 'cause the official OpsMan API do not support setting floating_ips?
Greetz

@staynerzone is this "FloatingIP" a job in the ERT?  it'd be helpful if you can include a screenshot showing that field, if that's ok.

@madamkiwi
I don't think so. It's just a yaml entry in the bosh cf-deployment manifest (floating_ips: <IP_ADDRESS>) and should associate an existing floating-ip with the given instance through the cpi.

As you can see the right column lets you type in a comma-seperated string of floating_ips to bind those to the job instances.

And for further "debugging" I inspected that field and noticed the attribute "floating_ips".
All the other attributes ("instances", "instance_type", "elb_names"...) are well documented in the official API docs.
Hope that might help :)

thanks! and what version of ops manager are you using? @staynerzone

@madamkiwi
OpsMan: 1.10.6
ERT: 1.10.8
Thanks for your help
Greetz

yeah @staynerzone - this is going to be an ops-manager feature that they will need to add to their API. I can put a feature request in for you and we'll leave this open until they can get to implementing it. Appreciate all the detail!

@zachgersh - this would be great! Thanks a lot for your help! :)

This was implemented here: https://github.com/pivotal-cf/om/pull/111


Prefix number for generated ID's

Fixes #33
Signed-off-by: Gary O'Neall<EMAIL_ADDRESS>

Note: This PR will not pass the CI until the SPDX Java Library version 1.1 is released


Encountered an error while using aki. start_game

Summary
Encountered an error while using aki. start_game
Reproduction Steps
Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/aiohttp/web_protocol.py", line 452, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.9/dist-packages/aiohttp/web_app.py", line 543, in _handle
    resp = await handler(request)
  File "/app/app.py", line 48, in handle_request
    q = await aki.start_game(language=lang)
  File "/usr/local/lib/python3.9/dist-packages/akinator/async_aki/async_akinator.py", line 168, in start_game
    region_info = await self._auto_get_region(get_lang_and_theme(language)["lang"], get_lang_and_theme(language)["theme"])
  File "/usr/local/lib/python3.9/dist-packages/akinator/async_aki/async_akinator.py", line 114, in _auto_get_region
    parsed = json.loads(match.group().split("'arrUrlThemesToPlay', ")[-1])
AttributeError: 'NoneType' object has no attribute 'group'
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7f819fc90670>
Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7f819fa81a60>, 5245086.969)]']
connector: <aiohttp.connector.TCPConnector object at 0x7f819fc905e0>

Minimal Reproducible Code
The problem can be reproduced 100% by only allowing the code in [ examples/async_aki.py ] to be run.
I'm pretty sure that the first time this error would have occurred would have been within five minutes before UTC/GMT: 2024-04-02 06:10:00 , and I think it's likely that akinator officially, probably at 6:00, changed something.

Expected Results
No errors
Actual Results
An error has occurred
System Information
Ubuntu 20.04.5 LTS (GNU/Linux 5.4.0-28-generic x86_64)
Checklist

[X] I have searched open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have made sure that this issue is valid.

Additional Context
No response

The problem has been resolved and appears to have been caused by aki's own network fluctuations, which have now recovered on their own.

hi man, did you get it to work? It'd help me a lot as I'm also working on it :D

Yes, aki's official website has changed significantly, and I just spent 2 hours completely refactoring the asynchronous portion of the project's code, but it's not quite finished yet. :)

hi man, did you get it to work? It'd help me a lot as I'm also working on it :D

Yes, there have been major changes to aki's official website, I just spent 2 hours completely refactoring the asynchronous portion of the project's code and it's working, but it's not quite finished yet. :)
I'll have to sleep and get up and do the rest.
Also I found that the new official version doesn't seem to support custom aki.progression custom values and calling ... /list to force an answer to a question, this interface is no longer officially provided, do you have a solution for this?

Nah bro, haven't found a way around it yet.... AND I really need to 😆
Any updates?

hi man, did you get it to work? It'd help me a lot as I'm also working on it :D

Yes, there have been major changes to aki's official website, I just spent 2 hours completely refactoring the asynchronous portion of the project's code and it's working, but it's not quite finished yet. :)
I'll have to sleep and get up and do the rest.
Also I found that the new official version doesn't seem to support custom aki.progression custom values and calling ... /list to force an answer to a question, this interface is no longer officially provided, do you have a solution for this?

yoyo, any updates yet?

this issue still persists
https://github.com/codewarnab/akinatorbot in this repo i am currenlty facing this issue
aki_play_cmd_handler
    q = aki.start_game(language=None, child_mode=False)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: Akinator.start_game() got an unexpected keyword argument 'language'

most probably this is due to some api changes

Yup, I'm facing this issue currently as well. Haven't checkout Akinator library in a while yet.
I'll probably try to debug it form my end and see what can be done.
Also @Container-Zero please let me know what you're working on to fix this issue? I assume the problem is because things have changed or restructured in the Akinator official site right ?

I was able to reproduce this error through debugging.
The problem is the regex pattern is not matching with the HTML text output from requests object.
https://github.com/Ombucha/akinator.py/blob/323d05a7422adafe1423e027eace70aee09adc5f/akinator/akinator.py#L106-L118
I assume there is a change in the Akinator site structure or the regex pattern is not valid anymore.
I was using Python 3.12.

Okay, it seems like they have made changes to the API a lot.

Are there any hotfixes we can apply on our end to patch it temporarily until there is a full update, or has the API changed too much to apply a few fixes?

Are there any hotfixes we can apply on our end to patch it temporarily until there is a full update, or has the API changed too much to apply a few fixes?

I've actually created the same library from scratch with new changes to the API. It is working fine now. But there are a lot of things that is missing currently in mine. I followed the same code structure as this wrapper to make sure I get the same end interface because I use this wrapper as a dependency in other projects. You can probably check out the below link.
https://github.com/advnpzn/akipy

Are there any hotfixes we can apply on our end to patch it temporarily until there is a full update, or has the API changed too much to apply a few fixes?

I've actually created the same library from scratch with new changes to the API. It is working fine now. But there are a lot of things that is missing currently in mine. I followed the same code structure as this wrapper to make sure I get the similar end interface because I use this wrapper as a dependency in other projects. You can probably check out the below link.
https://github.com/advnpzn/akipy

Looks like it's already functioning partially! I'm about to graduate soon, but once I'm done with school I'll definitely try to help with some stuff like docs since I relied on this library for a Discord bot I maintain.


Allow PHP 8 usage

Currently when installing via composer on a PHP 8 machine, this throws an error due to the PHP 7 requirement currently in place.

This seems right.

phpunit/phpunit:8.5 is not compatible with PHP 8.0, need to add 8.5|9.5 to the dependency for this to work

phpunit/phpunit:8.5 is not compatible with PHP 8.0, need to add 8.5|9.5 to the dependency for this to work

Like that?

the command:
 composer create-project slim/slim-skeleton:dev-master .

result:
[InvalidArgumentException]
Could not find package slim/slim-skeleton with version dev-master in a version installable using your PHP version, PHP extensions and Composer version.

The command:
 composer create-project slim/slim-skeleton:dev-master . ^4.*

result:
Your requirements could not be resolved to an installable set of packages.
  Problem 1
    - Root composer.json requires slim/psr7 ^0.5 -> satisfiable by slim/psr7[0.5.0].
    - slim/psr7 0.5.0 requires php ^7.1 -> your php version (8.0.3) does not satisfy that requirement.
  Problem 2
    - phpunit/phpunit[7.5.0, ..., 7.5.20] require php ^7.1 -> your php version (8.0.3) does not satisfy that requirement.
    - Root composer.json requires phpunit/phpunit ^7.5 -> satisfiable by phpunit/phpunit[7.5.0, ..., 7.5.20].

The slim/psr7 v1.3.0 is autoinstalled with slim/slim so why is in composer.json?
and the phputit with php 8.0 version is 9.5. need to be instaled manualy

To install with php8:

download the skeleton archive
install vendor with: composer install --ignore-platform-reqs

Here is the release:
https://github.com/slimphp/Slim-Skeleton/releases/tag/4.3.0


New article - Data binding - overview

This article is merging of three sources: Overview (link, link, link)
Preview - link

@adegeo Acrolinx score for the article - 99. Kind request to review PR - https://github.com/dotnet/docs-desktop/pull/1373


Legion: Weak scaling S3D without tracing

We've spent time improving the performance of the visualization branch of S3D. During these experiments we've found that S3D no longer weak scales without tracing. I ran the same case on both the nscbc branch and the visualization branch and the results looks similar, so that proves that the image compositor is not the issue.
nscbc: http://sapling2.stanford.edu/~seshu/viz/nscbc/average_21to30_iteration.html
visualization: http://sapling2.stanford.edu/~seshu/viz/average_21to30_iteration.html
We can't use tracing due to #1442.
There are profiles available here: http://sapling2.stanford.edu/~seshu/viz/

You're going to need to be more specific than that. Look at the profiles. See what changes and then report your theory for what you think the source of the performance problem is. Is it because the utility processors get more busy? If so, specifically which meta-tasks are there more of or that take longer to run as you scale? If copies are getting slower, which copies and which task or operation generated them? All this information is in the profile, and as the application developer, you are more likely to notice the patterns and anomalies than anyone else so it is your job to figure out what specifically we should look at. Be specific in your diagnosis as to the performance problem and give exact time ranges across multiple profiles that illustrate the changing behavior.


updated left notebooks

Hy, @colah
I've completed my rest work.
ISSUE: https://github.com/tensorflow/lucid/issues/236
I've done the changes in all of the notebook if by mistake I left any of the notebooks then feel free to mention it here. I'll fix them.

Hey, @shancarter  would you please review my pull request.

@abhinavsp0730 sorry for the delay and thanks so much for your work on this! The diff looks great on reviewNB (https://app.reviewnb.com/tensorflow/lucid/pull/245), so I'd be happy to finally merge these.
Unfortunately it looks like there's a typo in the %tensorflow_version 1.x line; it's missing an 's':

Did you prepare these changes programmatically and can easily redo them? No worries if not, just let me know and I'll see if I can fix them myself. :-) Thanks again for your willingness to help, and sorry again for not reacting earlier.


Upgrade to React 15

React 15 has been officially released. Most of the breaking changes do not affect any Mortar components. However we rely on react-router 1.0.1 (specifically the named-routes functionality). In order to complete the upgrade react-router or create our own lightweight router.

Passing in single JSX elements into Form and Row like:
<Br.Form key={this.formKey} formKey={this.formKey} bindResource={this.state.includeRelations}>
    <Br.Row>
	<Br.Column grid="lg" size="12">
	    {this.buildRelationsCheckboxes(relations)}
        </Br.Column>
    </Br.Row>
</Br.Form>

Produces these errors:
warning.js?8a56:44 Warning: Failed propType: Invalid prop children of type object supplied FormRow, expected array. Check the render method of YourComponent
warning.js?8a56:44 Warning: Failed propType: Invalid prop children of type object supplied to Form, expected array. Check the render method of YourComponent
Form and Row should accept the React.PropTypes.object type for children

@SimantovYousoufov This is related to #14

We are now fully supporting React 15.
React Router was also upgraded in the Playground.


Fix: Set the end featurename with the conventional name with "Gate" word

What this PR does
Before this PR: just change the typo to respect the "conventional name" with the Gate word in the end of each feature
After this PR: /

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made: just change the typo to respect the "conventional name" with the Gate word in the end of each feature
The following alternatives were considered: leave it like that
Links to places where the discussion took place: https://github.com/kubevirt/user-guide/pull/780
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ X ] Design: A design document was considered and is present (link) or not required
[ X ] PR: The PR description is expressive enough and will help future contributors
[ X] Code: Write code that humans can understand and Keep it simple
[ X ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ X ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ X ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ X ] Community: Announcement to kubevirt-dev was considered

Release note

Thanks for the PR. What about CPUManager / CPUManagerGate?

Sorry I forget this one. ;) thanks

/test all

@Davidffry please have a look at the failures. you can run make locally in order to see what is wrong


Clean-up the code that stored and passes the SILSerializeAll flag around

SILSerializeAll flag is now stored in the SILOptions and passed around as part of it
Explicit SILSerializeAll/wholeModuleSerialized/makeModuleFragile API parameters are removed in many places

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


docs: broken link from SingleAxisTracker to PVSystem

Describe the bug
https://pvlib-python.readthedocs.io/en/latest/api.html#singleaxistracker

Inherits the PV modeling methods from :ref:PVSystem:.

link isn't rendering , not sure why, there is a document called _pvsystemdoc with a subsection called "pvsytem" but maybe there are too many "pvsystem" references? or maybe it's case sensitive?
Or was this link supposed to be to the API class definition, that seems more likely to me.

Or was this link supposed to be to the API class definition, that seems more likely to me.

this.


Can't specify default grub entry

According to https://github.com/rancher-sandbox/elemental/blob/main/config.yaml.example and by following https://rancher-sandbox.github.io/cOS-toolkit/docs/customizing/general_configuration/  I've tried to run an install with the following elemental config file:
cosign: false
verify: false
install:
  grub-entry-name: "c3os"
  system:
    size: 2000
  recovery-system:
    size: 2000
upgrade:
  grub-entry-name: "c3os"
  recovery-system:
    size: 2000
  system:
    size: 2000
reset:
  grub-entry-name: "c3os"
  system:
    size: 2000

After install, the grub entry name wasn't applied, and indeed I could confirm that the grub env populated is with the default values:
cat /run/initramfs/cos-state/grub_oem_env
# GRUB Environment Block
# WARNING: Do not edit this file by tools other than grub2-editenv!!!
default_menu_entry=cOS

By running upgrade with --debug can be seen that no string was loaded in the config.
Reproducible @ https://github.com/c3os-io/c3os/tree/updates

mmm I'm trying to do few experiments here with a unit test... but looks also cosign and verify aren't read at all? I'm a bit confused. Although the size of images seems to be read correctly

Fixed as https://github.com/rancher-sandbox/elemental/pull/224


Add CRO uninstallation

JIRA: https://issues.redhat.com/browse/RHODS-1622
Signed-off-by: Anish Asthana<EMAIL_ADDRESS>

/retest

Successfully tested with odh-deployer #138.


Deploying to Heroku

Is there anyone else getting build error on Heroku?
 !     LoadError: Could not open library 'libseabolt17': libseabolt17: cannot open shared object file: No such file or directory.
 !     Could not open library 'libseabolt17.so': libseabolt17.so: cannot open shared object file: No such file or directory

Am I missing a buildpack or something?
The app is a Rails <IP_ADDRESS> application with:
gem 'neo4j-rake_tasks'
gem 'activegraph', '~> 10.0.1'
gem 'neo4j-ruby-driver', '~> 1.7.0'

If you tested your application locally you must have followed the neo4j-ruby-driver README.

Solved.
heroku buildpacks:add --index 1 heroku-community/apt --app YOUR_APPLICATION

Create an Aptfile in project root:
libssl1.0.0
https://github.com/neo4j-drivers/seabolt/releases/download/v1.7.4/seabolt-1.7.4-Linux-ubuntu-18.04.deb

Set an environment variable:
LD_LIBRARY_PATH=./.apt/usr/local/lib

Deploy your application...


Checkout all CI onboarding info

We're seeing an error when attempting to merge:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1401686&view=logs&j=dc056dfc-c0cf-5958-c8c4-8da4f91a3739&t=fd4e3270-b8e3-5fbf-e599-e8f3c9d442f6
git add -A
The following paths and/or pathspecs matched paths that exist
outside of your sparse-checkout definition, so will not be
updated in the index:
ci-configs/packages-latest.json.log
hint: If you intend to update such entries, try one of the following:
hint: * Use the --sparse option.
hint: * Disable or modify the sparsity rules.
hint: Disable this message with "git config advice.updateSparsePath false"
Write-Error: /home/vsts/work/_temp/431f548d-6670-48ee-889f-e8e402ec4c27.ps1:2
Line |
   2 |  . '/home/vsts/work/1/s/eng/common/scripts/git-branch-push.ps1' -PRBra …
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Unable to git add LASTEXITCODE=1, see command output above.

In this case the sparse checkout includes only the specified json files and not other files. If we attempt to check in changes to these files which were not checked out git-branch-push.ps1 will skip committing the changes when it gets a nonzero exit code from git add -A ... This results in the changes not making into the target branch. (Issue opened here: https://github.com/Azure/azure-sdk-tools/issues/2839)
Successful run of docindex: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1403768&view=logs&j=dc056dfc-c0cf-5958-c8c4-8da4f91a3739&t=588802d7-11b0-50c0-c9bd-117cec8e7d8c

Thanks for full information about this.
Could you please point out which is the file actually caused the failure? I thought we only care these three json files(package-latest, package-preview, package-legacy)


Build time got too high after upgrade versions

Operating System: Linux Ubuntu 16.04
Node Version: v8.6.0
NPM Version: 5.5.1
webpack Version: 3.8.1
webpack-dev-server Version: 2.9.4

[ ] This is a bug
[ ] This is a feature request
[x] This is a modification request

Expected Behavior
When we downgrade to the versions:
"typescript": "2.5.1"
"webpack-dev-server": "2.6.1"
"webpack": "3.4.1"
The build time back to normal which in our case is approximately 7 minutes.
Actual Behavior
After upgrading to the versions:
"typescript": "2.6.1"
"webpack-dev-server": "2.9.4",
"webpack": "3.8.1"
The build time got very high and in our project it took about 20 minutes to finish.
For Features; What is the motivation and/or use-case for the feature?
The build time is too high, please consider to review this problem.

Same issue here. Compilation 4 times slower after upgrading from Typescript 2.5.3 to 2.6.1.
webpack: 3.8.1
awesome-typescript-loader: 3.2.3
OS: Windows 10

You should report this to typescript or the typescript loaders when it happens for a typescript upgrade...

I allready opened an issue at awesome-typescript-loader

I don't know it is breaking change or what, but awesome-typescript-loader returns undefined if file exists but empty. So new typescript mark the file as missing and can not reuse cache
if (oldProgram.getMissingFilePaths().some(missingFilePath => host.fileExists(missingFilePath))) {
                return oldProgram.structureIsReused = StructureIsReused.SafeModules;
            }

Compilation performance issue is fixed and closed by  awesome-typescript-loader.

cool :1st_place_medal:


Trim white margins

Codecov Report

Merging #22 (8082c87) into master (25b80c6) will decrease coverage by 0.05%.
The diff coverage is 82.60%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
- Coverage   89.32%   89.26%   -0.06%
==========================================
  Files          81       81
  Lines        2558     2581      +23
==========================================
+ Hits         2285     2304      +19
- Misses        273      277       +4

Flag
Coverage Δ

unittests
89.26% <82.60%> (-0.06%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

xfuse/convert/st.py
59.57% <50.00%> (-0.90%)
:arrow_down:

xfuse/convert/visium.py
78.57% <50.00%> (-4.77%)
:arrow_down:

xfuse/convert/utility.py
92.15% <100.00%> (+1.35%)
:arrow_up:

Continue to review full report at Codecov.

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


Decaffeinate!

This PR migrates the codebase from CoffeeScript to JavaScript.
Here's what I did:

Changed name in package.json from liquid-node to liquid
I ran npx decaffeinate test to convert all the test files from .coffee to .js
I tried to use decaffeinate to also convert the source code in src too, but it didn't really work out. The files converted without issue, but the changes caused over 100 tests to fail. So instead I backed out that change and ran npm run compile to compile the CoffeeScript to JavaScript.
I removed the src directory and all the coffescript
I took the lib directory out of gitignore so it's part of the repo
I added standard as a dev dependency and used standard --fix to clean up lots of issues in the compiled lib/**/*.js files.
I manually cleaned up oddities from the coffee-generated code, one at a time, making sure to keep the test suite green.

There's more to be done before the code in the lib directory is super-nice and free of all coffee remnants, but it works and the existing test suite is still passing. 💅
I'd be in favor of doing the following:

[ ] land this PR
[ ] publish it to GitHub and npm as a new major version liquid@2
[ ] run `npm deprecate liquid-node@"*" "'liquid-node' has been renamed to 'liquid'"
[ ] continue to make improvements to the source code and documentation in followup PRs.

@sirlantis @sarahs how does that sound?
Resolves https://github.com/sirlantis/liquid-node/issues/70

Forgot to mention: I also updated the Travis config to run on Node 8 and 10

And updated engines.node to >=8

🤔 Maybe we should actually publish liquid@4, which would make more sense as a followup to liquid-node@3
$ npm show liquid-node dist-tags
{ latest: '3.0.0' }

We should also probably publish a final version of liquid-node as 3.0.1 with a README update mentioning the rename. Otherwise anyone who visits the old package on the npm website won't easily discover that the package has been renamed.

@sarahs to be sure these changes work on our internal project, I ran npm uninstall liquid-node && npm install zeke/liquid-node#decaffeinate && npm test, changed the require('liquid-node') to require('liquid'), and all tests are still passing!


fix: add shippingtoggleselector nullcheck

1. Why is this change necessary?
src/Storefront/Resources/app/storefront/src/plugin/offcanvas-cart/offcanvas-cart.plugin.js has null checks almost everywhere, but missing in the querySelector for the shippingToggleSelector. This leads to a console error when the class .js-toggle-shipping-selection is removed from the DOM i.e. in a custom Twig template.
2. What does this change do, exactly?
Adds a nullcheck after the querySelector.
3. Describe each step to reproduce the issue or behaviour.
Add a custom Twig template for shopware/storefront/Resources/views/storefront/component/checkout/offcanvas-cart-summary.html.twig and remove the small-tag with class="js-toggle-shipping-selection".
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-23961
Please use this issue to track the state of your pull request.


fixed markdown issue and promises .then() issue

Added spacing to properly markdown Mongoose Cheatsheet. Also added missing closing brace from Promises .then() example.

@sahat


gRPC protocol head for Cadence frontend handler

Currently Cadence defines frontend API as thrift and uses yarpc over tchannel for communication between external clients and Cadence service.  This issue is to expose gRPC protocol head for the public API and define protobuff definitions for all public API.  Initially this API implementation could just proxy API calls to thrift API handlers.

Does this mean that Cadence workers will be able to communicate with the frontend over gRPC?
We need this to be able to run workers outside of the Cadence cluster.

@BartXZX Yes. The workers are going to talk to the cluster through gRPC.

Good day,
Do you have an update on the ETA for this?
Thanks in advance

We ETA is within two weeks for the alpha release.

Just curious about this.

Looking forward to this!

Hi any updates on this ?

We ETA is within two weeks for the alpha release.

Hey Maxim is there any updates on the migration to grpc? Thanks!

@tonyabracadabra Temporal V1 was released last month with grpc support: https://docs.temporal.io/blog/temporal-v1-announcement

@tonyabracadabra Temporal V1 was released last month with grpc support: https://docs.temporal.io/blog/temporal-v1-announcement

Thanks! Is temporal a complete replacement for cadence right now?

Temporal is Open Source with MIT license.  Please refer to stackoverflow post for a more complete comparison between the two open source projects.


Ability to import client-side library via package management

Is your feature request related to a problem?
If the library I'd like to import has document operation, qwik will give me this error:
[vite] Internal server error: document is not defined
Describe the solution you'd like
For pure client-side library, we have have a "client-side" folder in src, all the files inside should be preloaded to the html document (hydration).
Describe alternatives you've considered
Use solid.js
Additional context
No response

thanks @aeroxy !
Can you give a specific example of a client side script you're loading and where do you try to load them?
(a repro-repo using https://qwik.new will be awesome)
Thanks!

thanks @aeroxy !
Can you give a specific example of a client side script you're loading and where do you try to load them?
(a repro-repo using https://qwik.new will be awesome)
Thanks!

It's our internal core SDK for Shopee. I will need to make a minimal example, which might take a while.

I encountered such problems some times, different result like window is not defined, self is not definbed or document is not defined. I wonder if import modules is working on server, if so, how can we import client side modules. Now I have two alternative methods, binding event on window:onload or useClientEffect$(), and I use dynamic import to load modules. But it's really not so convenient.

@manucorporat  i saw in issue #1315 that inlining is not recommended. It works for me in dev but not in production unless i change the entry strategy of the qwikVite plugin to "hook" (which is probably not optimal). I'm using leaflet and some leaflet plugins that when imported regularly will throw window is not defined, forcing me to inline the imports in useVisibleTask$. What is the correct way to handle this?