"jq: cannot iterate over null" error when sending /api/show request

According to composer.json Schema the only required parameters are description and name. Given they're both present in my library' composer.json I'm wondering where this error is coming from
Response I get:
jq: error (at <stdin>:140): Cannot iterate over null (null)
Package: vendor/package
Description:
Authors:
Releases: 1.0.0, 1.0.1, dev-master
Homepage: https://gitlab.xyz/vendor/package
Last built: Fri Oct 13 10:02:02 2017

composer.json of package I'm querying for:
{
    "name": "vendor/package",
    "description": "",
    "license": "proprietary",
    "homepage": "https://gitlab.xyz/vendor/package",
    "type": "library",
    "keywords": ["abc", "def", "ghi"],
    "repositories": [
        {
            "type": "composer",
            "url": "https://composer.xyz"
        }
    ],
    "require": {
        "symfony/http-foundation": "^2.6|^3.0",
        "symfony/http-kernel": "^2.6|^3.0",
        "symfony/config": "^2.6|^3.0",
        "symfony/dependency-injection": "^2.6|^3.0"
    },
    "require-dev": {
        "phpspec/phpspec": "~3.4",
        "phpunit/phpunit": "~5.7",
        "symfony/framework-bundle": "^2.6|^3.0"
    },
    "minimum-stability": "stable"
}

released under latest docker tag

released under latest docker tag


Fix indentations and remove invisibles

Fix indentations from 2 to 4 spaces, remove invisibles and tabs
Motivation:
To have a consistent code style
Modifications:

Indentations with 2 spaces changed to 4 spaces.
Invisibles removed
Tabs replaced with spaces

Result:
Code style more consistent (I might have missed some around)

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

Thanks for the cleanup.  My only concern with this is the effect it has on git annotate etc.  Also, I think there is now a .swiftformat rule file for SwiftPM, which should include taking care of this whitespace, so would it make sense to apply that on a file-by-file basis when they are touched rather than wholesale?

Thanks for the cleanup.  My only concern with this is the effect it has on git annotate etc.  Also, I think there is now a .swiftformat rule file for SwiftPM, which should include taking care of this whitespace, so would it make sense to apply that on a file-by-file basis when they are touched rather than wholesale?

@abertelrud I personally don't see an issue on either ways.  I am wondering what changed from the previous approval of the same PR.

@abertelrud I personally don't see an issue on either ways.  I am wondering what changed from the previous approval of the same PR.

I'm not disapproving it, but raising an alternate suggestion after thinking about it some more.  I'd be curious to hear what @neonichu and @tomerd think.

I'm not disapproving it, but raising an alternate suggestion after thinking about it some more.  I'd be curious to hear what @neonichu and @tomerd think.

closing due to age. I think we should reformat the project using swiftformat tho


Add OE support like PCA9635

See - https://github.com/RobTillaart/PCA9635/issues/20
Might take time to stabilize.

0.2.6


Ability to attach custom headers in the RPC requests

Use case I need this for is user RPC authentification. The user would pass an AuthorizationToken:  in the headers to authenticate with RPC.

@chefsale do we have that functionality on the JSON RPC side?
Can you please elaborate a bit with the use case, because I'm not sure if it's something that will play well with the existing concept of JSON RPC, private keys, view calls etc.
cc @frol

You can extend the provider and specify it when you create a connection: https://github.com/near/near-api-js/blob/master/src/connection.ts#L40
That extended provider can just extend the JsonRpcProvider class, and override sendJsonRpc which is used by all the rest methods

However, it might be a good idea to have this use-case covered in near-api-js natively since it might need to be integrated in near-cli

@frol Yes, i think just adding an additional parameter header which is empty by default to the provider would be a way to go. In the end the JSON-RPC is still again using HTTP if this is what you mean by natively?

Yes, that is what I meant


Question: Accessing parsed command-line arguments in configureAPI method

Is there a way to access the command-line arguments parsed by the server (e.g. Server.TLSHost) inside configureAPI method?

no but you can access it in the main and from there on generate code with --exclude-main


Fixes

Splitting each line on spaces was not a good idea. Now the selection is split only on line breaks, so multiple links on a single line won't be processed anymore. Closes #64.

Closes #68


Refresh/Reload a single filing data in DB

How can I refresh a single filing data as in DB in 'filings' table 'errors' field shows I/O error with certain XXXXXXX-XX-XXXXXXXX.zip file.
So how can I redownload the one single filing and refresh the filing data in DB?

Recomputing selective filings and updating the DB can be accomplished by specifying the --recompute and --cik options with the build_secdb.py script.
First, please update build_secdb.py from the Altova github repository (as we have found a bug during testing)! Then, the database can be updated for a given company with the following steps:

Delete the zip archive from the filings/20YY-MM/ sub-directory
Re-download it with raptorxmlxbrl script scripts/download_filings.py feeds/xbrlrss-20YY-MM.xml
Update the database with raptorxmlxbrl scripts/build_secdb.py --recompute --cik=123456 --db=... --log=... feeds/xbrlrss-20YY-MM.xml


External 3rd party tools

After looking through #129 and seeing that people are finally using toybox as a building block for multicall binaries that incorporate external projects, I wonder if toybox should address this inevitability.
It seems like devs just need to add/symlink  a directory in ./toys with a README and properly formed app.c file.
Not sure on the best way of adding additional CFLAGS/LDFLAGS for extra dependencies or how to handle license differences (#129 used lua which is MIT for instance)
This could be a great tool for devs, I used it in an experimental build with xfbdev/xvesa, minimal xinit, terminal and jwm to get a ~1mb compressed kernel with a built-in initramfs for qemu.  Obviously those are way outside the scope of the project, but if there was an official way to do things like this, it might stir up interest.

This could be a great tool for devs

why? unless you're reusing the toybox infrastructure, what's the advantage? (and don't forget that linking in all those extra libraries will slow down toybox startup.)

"Add one self-contained file and you get a command" is the design idea, yes.
You can set CFLAGS and LDFLAGS in the file "configure" at the top level.
Statically link the libraries and they shouldn't slow startup. (Dynamic linking is expensive, and for a multicall binary has less benefit.)
Toybox is 0BSD, a public domain equivalent license. That means you can add code under any other license you like, and the license of the resulting project is just the license of the other code. (You can stutter your license and retain 0BSD if you like, but are not required to by the 0BSD license terms. From a legal standpoint 0BSD remains the only permission statement allowing you to use the copyrighted upstream toybox code, but that's true whether you get a copy or not, and we don't require third parties to give out copies of information that's on our website. Nothing in the 0BSD license terms should conflict with any other license, it imposes no obligations. We disclaim warantee, but that's us doing that. You're welcome to offer all the implicit or explicit warantees you like. Go nuts.)

nothing obviously actionable here.


[DISCUSSION] deprecate / remove old internal drop stats?

@Andreagit97 opening a dedicated issue to discuss https://github.com/falcosecurity/libs/pull/1433#issuecomment-1807694658

I saw that in Falco (and I imagine also in other consumers) we use the get_capture_stats method to obtain the number of drops/events. On the other hand, with stats_v2 we are using an agnostic approach, where the final consumer receives a vector of metrics already populated by sinsp. My question here is, do we want scap_stats_v2 to replace the old scap_stats? If yes, how do we obtain the specific number of drops/events from this agnostic approach? Do we want to keep these specific numbers or the final goal is to expose a set of metrics with a Prometheus endpoint?

First and foremost we are talking about https://github.com/falcosecurity/falco/blob/master/userspace/falco/event_drops.cpp aka Falco internal: syscall event drop that we will call "old drop stats" versus the new metrics Falco option that is also capable of creating an internal rule Falco internal: metrics snapshot containing not just the drop counters but also more metrics.
@leogr starting to summarize a few shortcomings of the old stats from my perspective. At the same time I would be honoring that some adopters prefer to keep the old stats around for longer. Therfore I would be fine keeping it, but also willing to help work out a transition plan.
Cons old drop stats:

Old stats report the number of drops within a 1s time frame window which may be a less transparent or intuitive metric versus being able to define your deltas based on what you think has the most meaning (the new metrics framework snapshots the current drop counts at an interval you choose and subsequently you can derive your own deltas the way you prefer)
Can generate an unpredictable high amount of logs
By default only reports drops when drop percentage is above 10%
Enabled by default
Not intuitive to customize or even turn off other than adjusting a logging level for Falco rules

Pros old drop stats:

Not bound to a fixed metrics interval to send the first alert of drops occurring

yeah we need to explore a little bit all the usages of these old drops stats in Falco, to understand if we really need them or if we can just replace them with the new ones

When I asked on slack no one seems to be urgently still needing this.
In the last 3+ debugging sessions I have been involved, we always found the newer metrics feature to provide more actionable insights.
Proposing to introduce a deprecation warning for Falco 0.38 or Falco 0.37 and then follow the formal deprecation cycle?
WDYT @falcosecurity/falco-maintainers?
Besides the pros and cons I listed above it will help communicate easier to follow debugging steps and reduce the config surface, effectively making space for new configs that will move the needle in terms of improving Falco's performance and capabilities.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

/assign
added to my backlog :angel:
Tentatively for
/milestone 0.38.0

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale


Updated doc

Moved App category mapping table at the bottom of the document as a new section. Please review.

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

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:white_check_mark:Succeeded
View

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


fix code coverage

fix code coverage report generate

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6c7ac49). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #25   +/-   ##
=========================================
  Coverage          ?   57.65%
=========================================
  Files             ?       13
  Lines             ?      196
  Branches          ?       19
=========================================
  Hits              ?      113
  Misses            ?       68
  Partials          ?       15

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 6c7ac49...2944c54. Read the comment docs.


feat!: add eslint-plugin-promise support

closes #14

Thanks 🙏
I mistakenly pushed another change directly to main rather than as a PR: https://github.com/neostandard/neostandard/commit/26b472b52b32d704f60f12bfb228692f2f74b2f6
Thoughts on that? Can we extend that change with this plugin as well?

Thoughts on that? Can we extend that change with this plugin as well?

I will align the PR changes with export feature shortly after. And ping for review.

Updated title to reflect that this is a breaking change :)

@voxpelli how would this be breaking?

@mcollina it adds linting rules, so it's as breaking as when we added back TS style linting


add 'inv install-tools' to otel collector github action

What does this PR do?
adds inv install-tools to make sure go tools like modvendor are installed when github actions runs collector update/generate/license and PR
Motivation
failed action run: https://github.com/DataDog/datadog-agent/actions/runs/12282289444
Describe how you validated your changes
ran in forked repo: https://github.com/jackgopack4/datadog-agent/actions/runs/12283061236/job/34275666982

Possible Drawbacks / Trade-offs
Additional Notes
opened in place of #32061 since pipelines wouldn't run on external branch

/merge


CLN API deprecation causes amount issue with swap-outs

CLN at 85992e6e48a6131afee9b24d8b8f99ecd268d73e
PeerSwap at 19aaf19f868a874be5c9a16f3cb0143b647cb4b8
When initiating a swap-out while running CLN with allow-deprecated-apis=false, the amount check is off by 1000.
$ lightning-cli peerswap-swap-out 140490x1x0 100000000 lbtc
{
   "code": -1,
   "message": "swap amount is<PHONE_NUMBER>00: need to enable option '--large-channels' to swap amounts larger than 2^32 msat"
}

From the LND side of the channel:
$ ./builds/peerswap/out/pscli swapin --channel_id<PHONE_NUMBER>86315776 --sat_amt 50000000 --asset lbtc
2023/06/13 15:25:56 rpc error: code = Unknown desc = from the CLN peer: swap amount is<PHONE_NUMBER>0: need to enable option '--large-channels' to swap amounts larger than 2^32 msat


Fix flow error in Flow error in NavigationError/NavigationHeaderTitle

Summary:
Fixes the "Unused suppression" error in NavigationHeaderTitle.
This closes https://github.com/facebook/react-native/issues/9058

@flegall updated the pull request.

@flegall updated the pull request.

@facebook-github-bot shipit

Thank you for the PR.

Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.


Display markers for the required fields in the template form when creating a resource definition

Is your enhancement related to a problem? Please describe.

Because the form in the resource definition doesn't require validation, there are no markers displayed for the required fields.

Describe the solution you'd like

Display markers for the required fields in the template form when creating a resource definition. Make it clear to users which fields are required
Describe alternatives you've considered

Additional context

Walrus version: v0.5.0

Environment

Walrus version: main eb8e29d68c15d16e0fe6b1bc95dca3bdab96a454
UI version: dev-bb86dbc

Test Result: pass


Implement new persister

Implement new persister for robustness tests. The existing persister stores metadata for all snapshots in one data structure that is flushed to the Kopia repository. Instead, this new persister implementation immediately pushes and pulls metadata to and from the Kopia repo.

Codecov Report

Merging #202 (f6b4245) into robustness-client (a909ef2) will decrease coverage by 0.12%.
The diff coverage is n/a.

@@                  Coverage Diff                  @@
##           robustness-client     #202      +/-   ##
=====================================================
- Coverage              62.77%   62.64%   -0.13%
=====================================================
  Files                    348      334      -14
  Lines                  17377    16539     -838
=====================================================
- Hits                   10908    10361     -547
+ Misses                  4984     4789     -195
+ Partials                1485     1389      -96

Impacted Files
Coverage Δ

internal/blobtesting/faulty.go

internal/testutil/tmpdir.go

internal/blobtesting/map.go

internal/blobtesting/eventually_consistent.go

internal/blobtesting/verify.go

internal/blobtesting/concurrent.go

internal/blobtesting/asserts.go

internal/repotesting/repotesting.go

internal/fshasher/fshasher.go

internal/testlogging/ctx.go

... and 6 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 a909ef2...f6b4245. Read the comment docs.


Reference latest SharpSploit as submodule

Removed the hard-coded SharpSploit and added it as a submodule.
SharpGen.cs has been updated to support the latest version of SharpSploit.
README.md updated to include the command to initially retrieve the SharpSploit source code

This is a great idea! Sorry I haven't gotten around to merging yet @fastlorenzo . Will do so ASAP


Disable logging for authenticated static asset serving

You can disable logging in a phoenix router scope like this:
scope "/health_check", log: false do
  forward "/", HealthCheck
end

This doesn't do what I thought it did; it doesn't disable the actual request logging.


Fix misc bugs

Fixed bugs with storage for different entities
Fixed disenrol command not deleting assessment
Fixed mark and unmark command

Codecov Report

Merging #156 (2cc4db6) into master (eab9a91) will decrease coverage by 0.30%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #156      +/-   ##
============================================
- Coverage     29.97%   29.66%   -0.31%
  Complexity      409      409
============================================
  Files           141      141
  Lines          3069     3101      +32
  Branches        369      372       +3
============================================
  Hits            920      920
- Misses         2084     2116      +32
  Partials         65       65

Impacted Files
Coverage Δ

.../seedu/address/logic/commands/DisenrolCommand.java
0.00% <0.00%> (ø)

...ava/seedu/address/logic/commands/GradeCommand.java
0.00% <0.00%> (ø)

...java/seedu/address/logic/commands/MarkCommand.java
0.00% <0.00%> (ø)

...va/seedu/address/logic/commands/UnmarkCommand.java
0.00% <0.00%> (ø)

...seedu/address/logic/parser/GradeCommandParser.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/model/Model.java
0.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
13.33% <0.00%> (-0.46%)
:arrow_down:

src/main/java/seedu/address/model/TAssist.java
33.69% <0.00%> (-1.54%)
:arrow_down:

...ava/seedu/address/model/assessment/Assessment.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/model/lesson/Lesson.java
0.00% <0.00%> (ø)

... and 6 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 eab9a91...2cc4db6. Read the comment docs.


Setup oracle account, Add CLI commands to report oracle values

Description
This adds a new account type that can have its private key and account address derived from the mnemonic. This price oracle account gets funded in the genesis block to cover the fees of its transactions.
The other component of this PR is two new CLI commands. One of them reports the exchange rate between a specified token (currently just StableToken) and CeloGold. The other gets the currently reported rates. This one I added to easily check if the reporting was working, and figured it might be useful enough to keep.
Tested
The oracle account's inclusion in the genesis block and ability to act as an oracle was tested manually by spinning up a testnet and running the added CLI commands. Report transactions sent from the oracle account were successful and ones sent from other accounts were not.
Other changes
In the code-comments documentation for SortedOracles.report, the denominator param was missing. I added an explanation of what it is.
Related issues

part of #981

I split this up into multiple PRs


Memory leak questions

My team uses Ractive as our UI library, and have extended it quite a bit for our own purposes. We've recently noticed that we are leaking memory related to Ractive - perhaps related to our additions to it - and we're not sure where to start looking. Does anyone have thoughts on what a good place to start would be?

A good start would be to get a profile of your running code. Dev tools would be your greatest friend, especially Chrome's https://developer.chrome.com/devtools/docs/javascript-memory-profiling.
Also, try out the 0.8 (edge) branch. It's packed full with optimizations.

for us, we had the following:

external event sources whch we needed to unsubscribe from onteardown (emitter.off(this.alistener))
if you're listening or observing something in a parent component you'll need to remove that onteardown also
if you use external client libraries to make effects or something, remember to clean them too. they can maintain references to deleted dom nodes without you even knowing it.

use the chrome debugger and look at memory allocations. to use it effectively, make a set of tests which do something then it cleans up. look at what's left in memory after cleanup and you'll see where your memory leaks are.

My 2 cents: try to isolate it by means of small examples


Availability on F-Droid?

Thanks a lot for this useful application! Have you considered publishing it on F-Droid as well?

I'll take a look at what is required to get it into f-droid when I have some time.

Fdroid PR: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/8686

Are you still considering this?
The PR at F-Droid is about to expire in 2 weeks due to inactivity.
It seems to me that only a link for the Changelog needs to be added to Metadata and they ask for an answer if you could apply fastlane structure (which is not mandatory as it seems to me).
It would be great to see this in F-Droid! :) Thanks for your work.

At least it's available in the IzzyOnAndroid repo for now until Peter decides to officially support the main F-Droid repo.

Someone just needs to shepherd the pr through f-droid's process. That person doesn't need to be me.

Basically somebody needs to follow this doc https://gitlab.com/-/snippets/1895688 to add fastlane/ dir to this repo with metadata needed for F-Droid.


cursorAt option

Moves the sorting element or helper so the cursor always appears to drag from the same position.
This is useful when you need to detach the cursor outside the ghost element to allow mouseover/out during drag, specially in fallback mode.
usage (as sortable option) :
cursorAt : {
    top : -10,
    left : -10
}

only top/left supported
don't work on IE with native drag but you can use the forceFallback=true option to switch mode

Update your PR and run grunt jshint.


missing AWS::CloudFront::MonitoringSubscription resource type

CloudFormation Lint Version
0.71.0
What operating system are you using?
Ubuntu
Describe the bug
Hello, i noticed resource type AWS::CloudFront::MonitoringSubscription is missing.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudfront-monitoringsubscription.html
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/viewing-cloudfront-metrics.html#enable-metrics
Looks like this resource has been added September 29, 2022.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/ReleaseHistory.html
Expected behavior
Resource type AWS::CloudFront::MonitoringSubscription should be accepted.
Reproduction template
AWSTemplateFormatVersion: 2010-09-09
Resources:
  CloudFrontDistributionMonitoringSubscription:
    Type: AWS::CloudFront::MonitoringSubscription
    Properties:
      DistributionId: !Ref CloudFrontDistribution
      MonitoringSubscription:
        RealtimeMetricsSubscriptionConfig:
          RealtimeMetricsSubscriptionStatus: Enabled

Sorry, but it seems there must have been some mixup with vscode extension or something.. after re-opening the vscode workspace cfn-lint started to accept this resource type.

Good news @hoonoh thanks for closing the issue and let us know if you have any more issues.


REB-19 Remove compilation dep from kpe-admin to kpsr-codegen

REB-19 spin-off

Just rename the PR so that in the git log it appears as "Update header comments" or something correctly describing the change :)


0.7.0

@jonhlee

@audax-shreyaspurohit

@egprentice the akka-construct library I updated for us to use.

@patrick-bohan you might be interested in this for actor constructor injection. It allows you to redirect how the constructing actor gets, provides encapsulated and type-safe actor constructors (similar to passing a function that constructs an ActorRef, but without all the hassle of managing type-parameters), and it gives the constructor logic access to the ActorRefFactory as well as the constructing actor.

@chrissalij-r this might be of use to you as well.

@rcmurphy since you wrote the awesome https://github.com/AudaxHealthInc/lib-akka-guice
This is less conventional to Guice based projects, but it provides a convention for performing the work at compile time for non-Guice projects.


Text field clear label issue

The text field label when is clear isn't centered.

Hi, none of the labels (i.e. floating label, counter label) is supposed to be centered.


Enable operator operation without kubernetes.

Hi, latelly I've been working on setting up cilium with nomad, instead of kubernetes. By following some advices from @joestringer at https://github.com/cilium/cilium/issues/18334, and inspecting some documentation and guidance on howto setup cilium with docker, I've been able to integrate cilium agent, CNI & docker plugins to nomad.
However, the only component not working out of the box is the operator (actually the generic operator). This is due to some code paths assuming kubernetes availability, and failing (obviously) when no k8s apiserver that can be contacted.
This PR addresses this issues by adding a new command argument (--disable-k8s-services, w/ false as default), which enables basic usage of the operator (lease cleanup, ipam address gc, etc.), but disables any k8s-specific code/features.
There are some more missing pieces/features which I would like to add to operator in future PRs, like being able to provide/distribute policy statements to agents from kvstore, instead of using kubernetes CRDs, etc. But this is the bare initial support for operator w/o kubernetes.
PD: For nomad users interested on this, this github issue is the actual place where using cilium w/ nomad is being handled (https://github.com/hashicorp/nomad/issues/12120)

Updated branch w/ changes and rebased against current master.

Fixed cli help reference, rebased and squashed changes.

The tests failed because the autogenerated docs need to be updated. Please be sure to build the binaries locally and then run 'make -C Documentation update-cmdref', amend the commit to include the latest changes, and re-push the PR.

Using update-cmdref fails on my local (probably due to using osx), so I've
been trying to match it by hand.. I'll try again or move the development to
a docker environment.
On Mon, Sep 26, 2022 at 8:10 PM Joe Stringer @.***>
wrote:

The tests failed because the autogenerated docs need to be updated. Please
be sure to build the binaries locally and then run 'make -C Documentation
update-cmdref', amend the commit to include the latest changes, and re-push
the PR.
—
Reply to this email directly, view it on GitHub
https://github.com/cilium/cilium/pull/21344#issuecomment-1258422768, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABOV6JRQAT7FWQOCKQGPWTWAHRKHANCNFSM6AAAAAAQOY2EC4
.
You are receiving this because you authored the thread.Message ID:
@.***>

/test

/mlh new-flake Cilium-PR-K8s-1.25-kernel-net-next

Testing is passing, just looking for one more reviewer on the operator side. I think that the main concern this will draw over time is whether we can better structure the operator to support enabling these sorts of functionalities in a more modular manner, rather than scattering conditional checks around the code. At the same time, I'm not sure if we've got to a point where the necessary abstractions are clear so I don't have strong opinions about whether we should try to address that now as we begin these steps or whether we can just address that over time. Hopefully someone with a better familiarity with that part of the codebase could provide some thoughts in that regard.

Sorry, looks like something else went into the tree that caused a conflict. Can you rebase against the latest master branch?

This seems like it's got the necessary approvals, can you rebase against master? After that we can trigger CI and hopefully merge.

@joestringer  I'll try, but this is getting a bit too much overhead to get merged. I understand each project has it's own mechanics.. but this is likely the fifth time I have to rebase this, everytime with additional overhead in order to fix conflicts. :(

Rebased, and tested locally (w/o k8s), let's hope CI tests finish ok. :?

Github infrastructure appears to be having some trouble at the moment, causing image CI builds to fail. I'll try closing/reopening the PR to re-kick it.

@pruiz I understand, thanks for bearing with us in this process. I'll keep an eye out for CI but unless something broke during the recent rebase I expect this should be OK to merge.

@pruiz I understand, thanks for bearing with us in this process. I'll keep an eye out for CI but unless something broke during the recent rebase I expect this should be OK to merge.

understood.. I'll try to keep an eye. Thnks

k8s-1.23-kernel-5.4 workflow hit known flaky issue #21735, no need to block this PR on the failure.

That was the only failure, reviews are in, this looks good to merge. Thanks for your contribution! :tada:

Nice! many thnks Joe!
On Thu, Oct 20, 2022 at 6:07 PM Joe Stringer @.***>
wrote:

Merged #21344 https://github.com/cilium/cilium/pull/21344 into master.
—
Reply to this email directly, view it on GitHub
https://github.com/cilium/cilium/pull/21344#event-7632797018, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABOV6IO2GVS54Q5O52Y67LWEFU3TANCNFSM6AAAAAAQOY2EC4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Fixed recursive call in getFontManager()

Fixed recursive call in getFontManager()
Added res folder

Not seeing a Fixed recursive call in getFontManager() change?

Nicolas! You're alive!

This was my mistake. Sorry. Please, delete this pull request.


Signature mismatch

Hello. Apologies for the dumb question. I'm trying to run the atacama example in the bench folder by running dune build and I get this error:
> $ dune build
Entering directory '/Users/wilson/projects/github/leostera/atacama'
File "atacama/transport.ml", lines 43-52, characters 20-3:
43 | ....................struct
44 |   let listen = Net.Socket.listen
45 |   let connect = Net.Socket.connect
46 |   let accept = Net.Socket.accept
47 |   let close = Net.Socket.close
48 |   let controlling_process = Net.Socket.controlling_process
49 |   let receive = Net.Socket.receive
50 |   let send = Net.Socket.send
51 |   let handshake _socket = Ok ()
52 | end
Error: Signature mismatch:
       ...
       Values do not match:
         val receive :
           ?timeout:Net.Socket.timeout ->
           len:int ->
           Net.Socket.stream_socket ->
           (Bigstringaf.t,
            [> `Closed | `Timeout | `Unix_error of Unix.error ])
           result
       is not included in
         val receive :
           ?timeout:Net.Socket.timeout ->
           buf:Bigstringaf.t ->
           Net.Socket.stream_socket ->
           (Bigstringaf.t,
            [> `Closed | `Timeout | `Unix_error of Unix.error ])
           result
       The type
         ?timeout:Net.Socket.timeout ->
         len:int ->
         Net.Socket.stream_socket ->
         (Bigstringaf.t, [> `Closed | `Timeout | `Unix_error of Unix.error ])
         result
       is not compatible with the type
         ?timeout:Net.Socket.timeout ->
         buf:Bigstringaf.t ->
         Net.Socket.stream_socket ->
         (Bigstringaf.t, [> `Closed | `Timeout | `Unix_error of Unix.error ])
         result
       Type
         len:int ->
         Net.Socket.stream_socket ->
         (Bigstringaf.t, [> `Closed | `Timeout | `Unix_error of Unix.error ])
         result
       is not compatible with type
         buf:Bigstringaf.t ->
         Net.Socket.stream_socket ->
         (Bigstringaf.t, [> `Closed | `Timeout | `Unix_error of Unix.error ])
         result
       File "atacama/transport.ml", lines 28-32, characters 2-62:
         Expected declaration
       File "atacama/transport.ml", line 49, characters 6-13:
         Actual declaration

I have never used OCaml before. Perhaps there's a better way to do this? In Go there's go run, in Rust there's cargo run and in Elixir there's just elixir.

Hi @wilsonsilva! 👋🏼 thanks for opening the PR.
At the moment the main branch of Atacama relies on the main branch of Riot, so you have to pin this repository if you're using opam+dune.
Riot 0.0.6 will be submitted soon and then Atacama will be buildable on its own 🚀

This should be fixed in the upcoming 0.0.4 release. If you're working from sources you'll have to keep Riot pinned. Closing for now :) please reopen if the issue appears again!


fix: fixed deprecated package usage in config_test.go

Fixes #632.

hi @gozeloglu , thank you for your contribution


Add follow amount for follow_users #1055

#1055

Codecov Report

Merging #1071 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1071      +/-   ##
==========================================
+ Coverage   42.42%   42.44%   +0.01%
==========================================
  Files          29       29
  Lines        3359     3360       +1
  Branches      549      549
==========================================
+ Hits         1425     1426       +1
+ Misses       1795     1794       -1
- Partials      139      140       +1

Impacted Files
Coverage Δ

instabot/bot/bot.py
74.12% <100%> (ø)
:arrow_up:

instabot/bot/bot_follow.py
37.03% <100%> (+0.58%)
:arrow_up:

instabot/bot/bot_get.py
61.56% <0%> (ø)
: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 e004de8...275b8a8. Read the comment docs.

Great! Thanks!


Bug: Hover over the open contextmenu button

After hovering over the button, I noticed that the image-Information can't be folded.

In addition, an error log is displayed in the console, which might be the reason why the image-Information doesn't change when navigating to the next image. Here is the error message:
index-a67778ed.js:1 DOMException: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.
    at insert (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:55943)
    at b (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:38657)
    at m (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:38280)
    at k (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:40850)
    at I (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:40196)
    at S (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:38982)
    at m (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:38381)
    at Vu.te [as fn] (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:42269)
    at Vu.run (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:5680)
    at R.P.update (http://<IP_ADDRESS>:7860/infinite_image_browsing/fe-static/assets/index-a67778ed.js:1:42986)

Already fixed


[BUG]

searches on bing can take hours to complete sometimes taking an hour for one to happen.

did you turn off the headless and see which page it is stuck in?

how do i run in headless mode @Eugene-Tong

you can turn the headless = False when calling the function, I think there are 2 functions to change line 771 and 811

i ran it in headless mode it didnt get stuck on any page it kept serching but my points didnt go up and neither did the progress in the command prompt @Eugene-Tong

searches on bing can take hours to complete sometimes taking an hour for one to happen.

Agreed, is there any way we can make this faster?

someone re created the bot https://github.com/MehdiRtal/MicrosoftRewardsBot.git

Fixed with v3.0 #188


Pixel shift in test dataset

I found that there is a pixel shift between the low-resolution and high-resolution images. For instance, when I use MATLAB to upsample car05_001/input4/1000.png and compare with car05_001/truth/1000.png, I found that there is a non-negligible pixel shift.
May I ask how do you compute the PSNR of bicubic interpolation?

We consider the top-left pixel location as (0,0).
When doing super-resolution, it will be enlarged to (0,0).
This setting is consistent with many previous work, which contains a pixel shift compared to MATLAB and opencv.
I have just included a modified resize here

@jiangsutx Hi, could you tell me how to crop a GT frame in order to match the SR result(640x480)? When I compute the PSNR, I find the result is very poor. Would you like to do me a favor?

Sorry for the inconvenience for this size problem, caused by static graph of tensorflow.
In our demo code, we only process the top-left corner or input LR images. So you need to crop the top-left corner of the GT frame to calculate psnr.
We will rewrite the code and release pytorch version soon.

Thanks for replying. I certainly crop the corner of the GT frame, but get a poor PSNR value. the following is a part of the code for calculating the PSNR value.
           for idx_im = 1:length(filepaths)
                %count = count + 1
                name_HR = filepaths(idx_im).name;
                name_SR = strrep(name_HR, 'HR', methods{idx_method});
                im_HR = imread(fullfile(HR_path, dataset{idx_set}, dataDir(i).name, name_HR));
                %%%SPMC
                im_HR = im_HR(1:480,1:640,:);
                im_SR = imread(fullfile(SR_path,  dataset{idx_set}, dataDir(i).name, name_SR));
                % change channel for evaluation
                % %%%%%%%%%%%%%%%%%%%%%%%change for RGB or YCbCr
                %compute in y channel
                if 3 == size(im_HR, 3)
                    im_HR_YCbCr = single(rgb2ycbcr(im2double(im_HR)));
                    im_HR_Y = im_HR_YCbCr(:,:,1);
                    im_SR_YCbCr = single(rgb2ycbcr(im2double(im_SR)));
                    im_SR_Y = im_SR_YCbCr(:,:,1);

                else
                    im_HR_Y = single(im2double(im_HR));
                    im_HR_Y = im_HR_Y(1:size(im_SR,1),1:size(im_SR,2),:);
                    im_SR_Y = single(im2double(im_SR));

                end
                % calculate PSNR, SSIM
                [PSNR_all(idx_im), SSIM_all(idx_im)] = Cal_Y_PSNRSSIM(im_HR_Y*255, im_SR_Y*255, 0, 0);
                fprintf(results, 'x%d %d %s: PSNR= %f SSIM= %f\n', 4, idx_im, name_SR, PSNR_all(idx_im), SSIM_all(idx_im));
                fprintf('x%d %d %s: PSNR= %f SSIM= %f\n', 4, idx_im, name_SR, PSNR_all(idx_im), SSIM_all(idx_im));
            end

Can you give me some suggestions for getting accurate PSNR value? Thanks a lot!

OK you use MATLAB psnr() function.
I remember that, this psnr() function will automatically decide max data range based on value type.
If your input image is float or double type, it will consider the max value is 1.0. If your input is uint8, it will consider max value as 255.
This max value will make great change to final results. I guess may be you can pass double-type image within range [0.0, 1.0] to test.
Moreover, you can also open output and GT images in two windows and overlap them. And then switch between these two images to see if they align well without any shift, as shifting will cause psnr to decrease very much.

OK, thank you so much. I will try these methods and give feedback.


MIP-424 handle node's rabbitmq being down or going down during algorithm execution

When the broker (rabbitmq) is down a call to apply_async(..) (which queues a task, like delay(..) ) will raise an OperationalError or a ConnectionResetError. The same goes when calling the get(..) method on an AsyncResult (which returns the actual result of the task)
Concerning the node_tasks_handler_celery.py these exceptions are caught and then raise a (custom) ClosedBrokerConnectionError which contains a message with info about which task failed to be executed because of the closed connection to the broker and on which node. The ClosedBrokerConnectionError is propagated to the AlgorithmExecutor which terminates the execution of the current algorithm. The AlgorithmExcecutor catches the ClosedBrokerConnectionError  and raises an AlgorithmExecutionException which is then caught by the webapi exception handler module (error_handlers.py) and returns an ALGORITHM_EXUCUTION_ERROR along with a special HTTPStatusCode signaling that the algorithm execution failed, but without internal information about which node caused the problem or any other detail, just that the algorithm execution failed.
Concerning the NodeRegistry, a node with its broker down is just not returned as an active node in the system until its broker comes back up.

Forgot to add that the test_node_tasks_handler_celery tests should follow the logic of the udf_gen tests where a database instance is launched and then removed (https://github.com/madgik/MIP-Engine/blob/0adf530f9d6018330d0d0aad161345360c3e6a96/tests/conftest.py#L18)
If in the future we fix parallel execution, these tests will never be able to run in parallel since it's closing and opening the rabbitmq containers of the main setup. You are closing and opening rabbitmq containers anyway, why not use a container created in the test?


Dropdowns shouldn't be able to have same object selected

E.g. target and baseline shouldn't both be able to have same name

Fixed this by not allowing operations when the same object is selected


Use concrete vCPU structs instead of trait objects

In https://github.com/hermitcore/uhyve/pull/164, I implement additional traits for UhyveCPU on linux, but not on macos.
To be able to use the trait impls, this makes the vCPU structs concrete instead of using trait objects.

Nice!
bors r+


fix failing tests

@ryanflorence this fixes #1957

I think the bug goes a bit deeper than this. Looking into it now.

thanks @mjackson


Simplify using "contains" function

Is your feature request related to a problem? Please describe.
I'm a bit frustrated when I need to use contains function to first check if property on an object exists and then - if true - I can safely use it or use a default value.
It usually looks like this:
var resources = [
{
 name: res1
 optionalProp1: true
}
{
 name: res1
 optionalProp2: 'the value'
}
]

resource res 'RP/Res@version' = [for item in resources: {
name: item.name
properties: {
 prop1: contains(item, 'optionalProp1') && optionalProp1
 prop2: contains(item, 'optionalProp2') ? item.optionalProp2 : ''
}
}

This is a bit error prone as I need to use property name twice - and one is not a symbolic name but it's a plain string.
Describe the solution you'd like
I'd like to have easier way of saying to bicep "use this property if it exists on object and if not - use this value". The ?? operator is taken by coalesce function, so it might not be a good idea however the flow is similar, soo....
My proposal - use a question mark on the end of the property - and then chain with existing coalesce:
var x = item.optionalProp1? ?? 'value'

Which in bicep be equivalent of existing:
var x = (contains(item, 'optionalProp1') ? item.optionalProp1 : null) ?? 'value'

Which could be converted to ARM:
variables: {
"x": "[coalesce(if(contains(item, 'optionalProp1'), item.optionalProp1, null), 'value')]"
}

Open question:

can we make a runtime change to return null for non-existent runtime properties?
otherwise, can we have a new operator to clean up using contains() as is being done above?

One problem with silently returning null would be that typos would no longer produce an error message at runtime and would propagate nulls which could produce some strange or unexpected messages.

I see now a problem with using ? as operator for 'if not contains return null' operator. In other issue we've discussed using null propagation operator similar to C#: ?.. Using ? at the end of a property might lead to clash with this operator, i.e.:
var obj = {
requiredProp = {
optionalProp1 : value
}
}
var x = obj.requiredProp?.optionalProp ?? null //we don't know if we want to check for existence of required prop or propagate null

So ? is not a good choice.

One problem with silently returning null would be that typos would no longer produce an error message at runtime and would propagate nulls which could produce some strange or unexpected messages.
That's a good point. I think we should go with some operator, but not ? or have methods that would be invoked on the property (i.e. item.optionalProp.exists() and item.optionalProp.getValueOrDefault())

one additional thing that can also be simplified with contains() is case insensitivity. When you check a string contains is case-sensitive so when you use it you have to do something like:
var something = contains(toLower(param1), 'test')

If possible I think it is best if toLower() is not used in bicep or at least used in some rare cases. If this is implemented in arm code should look like this:
"variables" : {
  "something": "[contains(toLower(parameters('param1')), toLower('test'))]"
}

One big obstacle I see is that contains can be used for arrays and objects. For them the function is case insensitive but not every time you will know if the passed value is string, array or object.

similar to #8807

circling back to the issue, I think the main question we need to answer, both here and with #387 is whether we treat null as no property set or we differentiate.


Add the FNCS_VOLTTRON_Bridge application

This branch contains the FNCS_VOLTTRON_Bridge application files as well as a README for how to use

This change is

Wow. I guess gedit was set up for dos line endings or something when I wrote this file. It's been fixed. I also added a note about FNCS needing to be compiled with the same version of ZeroMQ that is packaged with VOLTTRON.


Use Hash lookup for MiqTask.human_status

Just a minor refactoring of MiqTask.human_status to make it allocate less objects and take less time to execute.
Steps for Testing/QA
Test passing should be sufficient.

@miq-bot add_label refactoring

@NickLaMuro looks good to me, want to freeze that hash though?

@carbonin Thanks for looking!  Honestly wasn't expecting much with this since it was just a small thing I noticed.
Anyway, yeah, I can updated it to use .freeze on the hash.  Couldn't hurt.


fix: unify how observables are consumed in different places

Closes https://github.com/graphql/graphiql/issues/1638

thanks for this! most of the implementation out there are like this, so can we introduce backwards compatibility somehow?

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/length
We could make an assumption based on the number of arguments, that however would fail if the observable implementation uses rest or default parameters.
Other than that I would not know any solution despite dealing with it in username in the fetcher function.

This change would not break subscriptions-transport-ws (https://github.com/graphql/graphiql/issues/1638#issuecomment-673376897)

Hey @acao, I guess you closed this due to lacking feedback from me. We already talked about AsyncIterables being the future for the fetcher prop but I think we should still address/tackle this issue. It is now back on my radar after having seen https://github.com/enisdenjo/graphql-ws/issues/93
So the conclusion was that all major observable implementation support both the
A
type Observable {
  subscribe(next: function, complete: function, error: function):an any
}

and
B
type Observable {
  subscribe(args: {
    next: function;
    complete: function;
   error: function;
  }): any
}

signatures. I only see concerns for users that do not use any of those libraries that are ALSO mix and match both call signatures in their custom fetcher implementation. So IMHO it is pretty safe to simply unify the call signatures within GraphiQL to either use A and B in order to avoid workarounds like the following: https://github.com/enisdenjo/graphql-ws/issues/93#issuecomment-758625106

Hey @acao, I guess you closed this due to lacking feedback from me. We already talked about AsyncIterables being the future for the fetcher prop but I think we should still address/tackle this issue. It is now back on my radar after having seen https://github.com/enisdenjo/graphql-ws/issues/93
So the conclusion was that all major observable implementation support both the
A
type Observable {
  subscribe(next: function, complete: function, error: function):an any
}

and
B
type Observable {
  subscribe(args: {
    next: function;
    complete: function;
   error: function;
  }): any
}

signatures. I only see concerns for users that do not use any of those libraries that are ALSO mix and match both call signatures in their custom fetcher implementation. So IMHO it is pretty safe to simply unify the call signatures within GraphiQL to either use A and B in order to avoid workarounds like the following: https://github.com/enisdenjo/graphql-ws/issues/93#issuecomment-758625106

it wont let me reopen this PR for some reason?

it wont let me reopen this PR for some reason?

oh because theres no 1.0.0 branch anymore that’s why

oh because theres no 1.0.0 branch anymore that’s why

I could send a new pr

I could send a new pr


Add GetPerspectiveTransform and WarpPerspective

I wrote tests for both functions as well, comparing against results that I know are correct from the Python version.
From what I've seen, everything seems to work correctly, but let me know if you find any issues

Thanks for your effort!


Feature/minsulee2/more log infos

Added more logs for p2p communication
Updates:

Add logging for new peer list
Add logging for updating node info in a tracker side
Add logging for recording all node info in a tracker side

Thanks for the review! merging now !


Getting errors on local schema file with custom built directives

I have a custom directive declared in my local schema file, and it is throwing validation errors when used in this file.
[GraphQL: Validation] Unknown directive "withAuth"

Maybe it's a bug?
Maybe we can have an option in the settings for the extension to declare our own directives or maybe to ignore such errors.

@andres-gr : Thanks for reporting the issue, I think that extension is not activated for you for some reason as the directive syntax highlighting is not working.
I was not able to reproduce this and it works for me.
Do you see a plug symbol with graphql in your status bar? This signifies that extension is in play.

If yes, can you please share a sample repository where this behavior can be observed.
Thanks!

@divyenduz thanks for the feedback, I guess I did have something wrong in my .graphqlconfig file as it is now working after doing some changes to that file.
I guess you can close this issue.

Hello @divyenduz
I got the same bug, even if the plugin is running well

Is the plugin works only with Schema directives (and not directiveResolvers ?)
My actual code follow this example: https://github.com/LawJolla/prisma-auth0-example
Thanks,

I have the same issue. The output tab in VS Code showed some weird errors, and I realized it's because of using a project name with a hyphen:
projects:
  my-project:
    [...]


Continue to use a patched version of html agility pack?

In Issue 77 you say
Turns out that using HtmlDocument.OptionFixNestedTags = true solves this issue without needing the patched version.
But if I install HAP V 1.4.9 via Nuget,  I got compil error in InitializeHtmlAgilityPackDocument()
Line hapDoc.OptionMaxNestedChildNodes = 5000;//did not make this an externally configurable property since it is really an internal issue to hap
Does replace this line by hapDoc.OptionFixNestedTags = true;?

I'm not sure what I was talking about at the end of the post. I still use the patched version in Abot and AbotX because the last time I checked, ~8 months ago, my patch was still needed. Not sure what I was trying to say or if it was a mistake.


Media uploads to central library only work if upload from central site?

When uploading from other sites, the uploads appear to be stored per site. Only uploads from the central site are stored in the central media library. Is the correct? or is the something wrong with my setting?

Uploads should be stored on the central media site regardless of which site you upload them from.
Do you have any other plugins on your site which might alter the way that media works on your site?
Anything unusual about your installation?

It's a new installation, haven't changed much. Only other plugin is SMTP, which has been disabled.
I think this is the problem:
The package I installed from

composer require humanmade/network-media-library

has a "network-media-library" folder, but inside it is multisite-global- media.php and its asssets

Not sure what's going on there. I'd try deleting the plugin and pulling it in again.


feat: switch codemirror to prism

Should be lighter, definitely has more control, lets see.
Comes with json, bash, js, and css pre-loaded. Then the rest of the languages are auto loaded on the fly
@cameronrohani we should probably make our own css file which ingests the theme vars exposed some css classes so we can theme the code as well

Great work! I’d be tempted to rename the component to CodeBlock. In HTML, Markdown and rich text code refers to inline code. Wdyt?

Sounds like a good plan. Or even code highlight or something


Added Consistency.

You can see the changes I made in the request, i personally think that the method should not be called "scl" but I don't want to be repsonsible for a refactor like that. Anyways, just fixed some O.C.D things in the GitHub editor. I didn't actually change any functionality so no worries there.

I don't see how these changes are useful.

Agreed. Also, we don't merge changes made via the web editor.
On Tuesday, May 5, 2015, Nathan Sweet<EMAIL_ADDRESS>wrote:

I don't see how these changes are useful.
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/pull/3089#issuecomment-99176706.

How come? @badlogic
And @NathanSweet as I stated it does not change any functionality, only adds coding consistency which is a better practice.

Merging changes made in the web editor generally breaks the build, so as a general rule we try to avoid them.

Thomas, appreciate the thought, but we are closing this out now.
On Tuesday, May 5, 2015, Justin Shapcott<EMAIL_ADDRESS>wrote:

Merging changes made in the web editor generally breaks the build, so as a
general rule we try to avoid them.
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/pull/3089#issuecomment-99180576.

Alright @MobiDevelop , I will try this again in IntelliJ. I was just trying to be lazy w/ the editor.

Please don't bother redoing this in IDEA, we'll not merge it.

this. is only needed to remove ambiguity between a field and local. x vs scalarXdoesn't tell me anything more aboutx. Vector2 v, while a single letter is usually not a great name, is not improved by calling it Vector2 vector2`.
Submitting PRs are great, but these changes are not useful. They only serve to waste time for us to review.


Use countByTeamIdAndTenantId for counting instead of select all

In SelectDataJdbc#getDashboardStats it's better to use count query instead of select all to get number of rows

Thanks for taking a look


fix(core): prevent removing a trailing slash

closes #154

@pmstss I don't think this is our case. The trailing slashes after the domain name don’t matter:
https://ahrefs.com/blog/trailing-slash/#:~:text=A trailing slash is a,are guidelines and not requirements.
https://developers.google.com/search/blog/2010/04/to-slash-or-not-to-slash


carry nicknames in offer/answer if config.nick is set

if config.nick is, this will be available on the remote side (in the videoAdded/videoRemoved) event on the peer.
@xdumaine @legastero?

+1

Nice!


Packaging questions

Hi, I'm looking into packaging this as a Debian package in Cryptoanarchy Debian Repository. From the first look it seems mostly easy but there are some unresolved questions:

Is it possible to configure port number or, if not, could you add it (I guess should be easy)?
Would it be possible to have configurable root path? (e.g. example.com/donate, example.com/stream...)
How hard would it be to move Streamlabs token configuration from CLI to GUI? Is it something you'd be willing to do?
(Optional) would it be possible to configure the application using a configuration file (or even better parts directory - in the spirit of run-parts) instead of environment variables?

Edit, forgot to ask:

What kind of authentication into the administration interface does this use? Would it be possible to have ThunderHub-style SSO?
Does this project have a unique icon/logo?

Note that I'm not committing into packaging it right now, just want to research this option.

Hi Martin, I appreciate your interest. Answers to your questions are below.

Yes, you can set port number in two ways. The simplest is probably using an argument (in the start script) or in the configuration file.
It is not possible to configure base path now but can be implemented pretty easily.
Move Streamlabs configuration to GUI is a little bit tricky. You called it Streamlabs token but this is not accurate enough. The Streamlabs access token (used to post donate alert) is automatically stored in the database after each user connects his Streamlabs account. Thus by a user action in GUI. The configuration which you mean identifies the application registered on Streamlabs platform and is a prerequisite of possible function of the application as a whole. So you can't simply move this configuration to GUI, without extending all use cases about missing this configuration.
The application uses appsettings.json configuration file, where you can configure everything. Usage of environment variables is just a secondary solution, easy to use with Docker.
The application uses to authenticate users default cookies based implementation of ASP.NET Core. The same implementation as BtcPayServer uses, in fact. I don't know ThunderHub well, so I can't confirm that for sure, but it would be possible, I suppose.
No, this project doesn't have a unique logo. I'm a graphic illiterate.


refactor: [M3-7178] - Refactor Cypress test setup, cache API account request, maybe fix hanging

Description 📝
This is a first pass at fixing some tests that have been flaky recently by restoring the account request mock using real API data. One Jenkins test account is consistently taking 30+ seconds to make requests to the /account endpoint which is causing random failures and making it hard to pinpoint flake caused by more specific issues.
Additionally, this attempts to fix the recent Cypress test hanging by disabling Chrome's new headless implementation (see Cypress Issue #27264 for more context). It may take several runs to confirm whether or not this is really resolved.
I plan to follow up with a more comprehensive PR containing more targeted fixes for the rescue, config, and resize test flake we've been seeing (I originally intended for that to be this PR), but want to prioritize this fix since it'll go a long way towards getting our Jenkins queue under control.
Major Changes 🔄

Add missing clean up to some domains tests to resolve resource accumulation issues
Attempt to fix hanging by forcing Chrome's old headless implementation
Restore account request mocking by using real account response data rather than factory data

This should improve performance without causing subtle and hard-to-troubleshoot issues like what cropped up during the DBaaS EOS changes

Refactor code to set up Cypress tests (adding commands, setting up request tracking, etc.), moving much of that code into a new support/setup dir
Merge OAuth tests into a single spec

How to test 🧪
This is targeting a CI-specific issue, so we will have to rely on the Jenkins run to see if this makes any impact. Specifically, one runner is consistently taking 45+ minutes even when all of the tests pass; we can validate that this PR resolves that issue by confirming that all 4 runners run in a reasonable length of time (~20-25 mins)

Since the most recent commit, we've had two runs against this branch that have finished without hanging (runs #5 and #9). 5 had a failure from a test that's been flaky lately which is OK.
Runs 6, 7, and 8 can be disregarded -- I kicked those off to test an unrelated pipeline change.
Going to continue running this to build more confidence that the hanging issue is actually resolved, but I like what I'm seeing so far.

yarn cy:debug worked for me but I can't run the test headless. Is this just an issue on my end?
Screen.Recording.2023-10-06.at.9.47.47.AM.mov

Looking into this now! I've never seen that before -- are you connected to the VPN by any chance? I just noticed that navigating to baker is suddenly giving me ERR_CONNECTION_CLOSED and I'm wondering if there may be some larger issue with the VPN that might be causing this too.

yarn cy:run against develop works fine 😟 Let me debug some more

yarn cy:run against develop works fine 😟 Let me debug some more

Thanks @bnussman-akamai! I'll keep trying to reproduce as well -- I'd definitely feel better fixing (or at least understanding) this before going forward.

Turns out launchOptions.args.push('--headless=old'); is causing my chrome to crash. DEBUG=cypress:* yarn cy:run was super helpful. Not sure why my chrome is crashing with that launch flag. I updated my chrome and now it works 🎉

Yeah, sounds like it! @jdamore-linode

@dwiley-akamai I would wager that your MANAGER_OAUTH PAT is expired/revoked/invalid/etc. I'm pretty sure that MANAGER_OAUTH is only consumed by Cypress, so I don't think you would see any issues stemming from having a bad MANAGER_OAUTH value during regular development.

Yup, that was it (I actually forgot to change it after you updated it a while back for me), thanks! I was able to run yarn cy:run locally and got failures for the following:
account/betas.spec.ts
account/security-questions.spec.ts
account/service-transfer.spec.ts
general/smoke-deep-link.spec.ts
kubernetes/smoke-lke-create.spec.ts
linodes/backup-linode.spec.ts
linodes/migrate-linode.spec.ts
volumes/create-volume.spec.ts

It also took a total of 1:21:17 to run. Are those tests flaky and the failures expected, and is that run time normal?
Still no luck on the Baker front but if others were able to get in and confirmed the runners look good, and the above results are normal, I can go ahead and approve.

Wow! An hour and a half isn't too farfetched with that many specs failing, but I'd definitely like to get to the bottom of what's causing all those failures. I suppose it could be a combination of the following:

Running the tests with yarn dev instead of yarn build && yarn start:manager:ci

For some reason Vite's dev server does not play nicely with Cypress and causes the tests to run a lot slower than normal
This is also probably responsible for the betas.spec.ts failure since the dev tools button overlaps the betas nav item and causes Cypress to fail when trying to navigate to the betas landing page

Banners that need to be dismissed from within Cypress via yarn cy:debug obscuring some navigation elements
Lots of existing resources on the test account that might cause Cypress to fail when it expects new resources to appear in a landing page
Managed being enabled? (I know that backup-linode.spec.ts fails when Managed is enabled)
Other account-specific issues, like tags that might impact the behavior of certain tests? (No specific ideas come to mind here)

@jdamore-linode Used yarn build && yarn start:manager:ci instead and that shaved a lot of time off, this time it completed in 45:39. Had these failures:
account/security-questions.spec.ts
account/service-transfer.spec.ts
linodes/backup-linode.spec.ts
objectStorage/object-storage.e2e.spec.ts

Managed is enabled on the account so that accounts for backup-linode.spec.ts at least.
I can see Baker now so I'll take a look when the current run finishes 👍

We've got 10 runs in a row now that have finished without hanging -- at this point I'm pretty satisfied that --headless=old resolves or at least seriously improves the situation with our stuck builds!


Calling bottle :unneeded is deprecated

Description
Warning: Calling bottle :unneeded is deprecated! There is no replacement.
Please report this issue to the kwilczynski/pkenv tap (not Homebrew/brew or Homebrew/core):
  /usr/local/Homebrew/Library/Taps/kwilczynski/homebrew-pkenv/Formula/pkenv.rb:8

Image for reference:

Context and Logs

Parameter
Value

macOS version:
12.0.1

Homebrew version:
3.3.2-31-g7ee64d9

Hi @bennesp,
Sorry for the delay!
Thank you for the report and sorry that this caused you some troubles! Also, thank you so much for sending a Pull Request to fix the problem. I appreciate that!
Krzysztof

Hi @bennesp,
All merged! Thank you again! I also updated the formula so that it would install pkenv version 0.5.3 as per the upstream release, as per: https://github.com/kwilczynski/homebrew-pkenv/commit/6d88867099c6c9fb1fae46d450a40d1953854e38
Krzysztof

Thank you very much Krzysztof, I really appreciate your work

Hi @bennesp,

Thank you very much Krzysztof, I really appreciate your work

My pleasure! There might have been a small hiccup to update the tap/formula, since I moved to main as the main repository branch name. You might have had to run brew tap --repair. Sorry about this!
Krzysztof


RemoteObject and Listeners on Opretion level - workaround

Generated Js code when define listeners at operation level not working
mailing list thread :
http://apache-royale-development.20373.n8.nabble.com/RemoteObject-and-Listeners-on-Opretion-level-workaround-tp9534.html

This is (currently) a "fact-of-life" for Royale.  RemoteObject is a Proxy so that it can have properties that are the names of the operations (like 'getText').  The compiler cannot know what the type of a Proxy property is for JS output, so it assumes the type of the property is also a Proxy (in order to handle nested ObjectProxy trees).
I suppose the compiler could output lots of code or call a function that tests the value returned and then knows how to properly access the results, but that could be heavy and slow.
In Flash/AIR the runtime knows the type and determines how to access the property.
So at least for now, Royale code may occasionally need more explicit type-casting, mainly when handling XML and Proxy, but also other dynamic objects including dynamic access obj[propName].
So your code will need to explicitly type the Operation so instead of just:
remoteObject.getText.addEventListener(ResultEvent.RESULT,  getdataResultHandler);
which works just fine in SWF, your code will need to be:
(remoteObject.getText as Operation).addEventListener(ResultEvent.RESULT,  getdataResultHandler);
You can use ASDoc comment directives for the method
/**
 * @royaleignorecoercion mx.rpc.remoting.Operation
 */

to suppress the call to Language.as()


RFC: Investigate a "postgres target" rust compiler target

I'd like to see what it would look like to design (develop?) and otherwise maintain a custom rust compilation target for Postgres that could give us a nearly "safe" (as Rust defines it) and "trusted" (as Postgres defines a procedural language) plrust.
As I know very little about this topic, please take these points with a grain of salt, but I suppose we need:

x86_64 support
aarch64 support
Linux only (for now)
to disallow most (all?) access to the host operating system (ie, no disk or socket I/O, etc, etc), mainly no filesystem access
to disallow directly calling into the active postmaster process (ie, no ability to reach into Postgres' memory space, despite us running in it)
strictly not WASM... we'd still be wanting to build CPU-native shared libraries

And some other points of consideration:

how to gracefully handle rust panics and have them interoperate with Postgres' transaction system
memory allocation (do we just use malloc/free or can we instead use Postgres' palloc/pfree` functions?

Please feel free to add other ideas here.

Postgres' definition of "TRUSTED" is here:  https://www.postgresql.org/docs/14/xplang-install.html
The optional key word TRUSTED specifies that the language does not grant access to data that the user would not otherwise have. Trusted languages are designed for ordinary database users (those without superuser privilege) and allows them to safely create functions and procedures. Since PL functions are executed inside the database server, the TRUSTED flag should only be given for languages that do not allow access to database server internals or the file system. The languages PL/pgSQL, PL/Tcl, and PL/Perl are considered trusted; the languages PL/TclU, PL/PerlU, and PL/PythonU are designed to provide unlimited functionality and should not be marked trusted.

I see little reason for us to go beyond that and inventing our own definition.
Like, to me, this says that network access is just fine.  Perhaps even the sound card and GPU.

I will refer to these hypothetical targets
x86_64-unknown-linux-postgres
aarch64-unknown-linux-postgres
This follows the established convention of using the last term in the target tuple to define the ABI and necessary runtime support (usually libc functions) of the target. The fundamental question to answer is, "Is it possible to compile Rust code to a target that uses Postgres's own functions for allocation and the like at the core of its runtime support, thus eliminating the impedance mismatch between Rust's runtime and Postgres's runtime?"

What about postgres versions? Their headers differ somewhat dramatically at times.

x86_64-unknown-linux-postgres-10
x86_64-unknown-linux-postgres-11
x86_64-unknown-linux-postgres-12
x86_64-unknown-linux-postgres-13
x86_64-unknown-linux-postgres-14

I am going to focus on trying to get the latest Postgres working and pretend that doesn't happen in ways that actually impact the extent of alloc/std we want to support, but yes, something like that might need to happen when I stop pretending.

Since trying to stuff Rust fully "into" the Postgres server's allocation and error handling logic is the main goal for this, I spent a fair amount of time studying Postgres's memory contexts for allocation and the like, how it handles memory allocations and pointers and aborts, how stuff gets added to the loop, the ereport mechanism, and PGX's integration with it, and going over old Rust RFCs and details on how unsafe code should be handled, before jumping in. I have a few in-progress branches off PGX that tweak the way PGX handles some of those for correctness and such (and hopefully also performance, as some functions wrangle more overhead than they need to) and will hopefully make things a bit easier to refactor in the future.
I didn't see anything that will prove to be a blocker and altogether I think it may actually wind up proving even easier than I thought, by, in the crate that PL/Rust code gets compiled into

[ ] override the #[panic_handler] with logic to eventually ereport
[ ] override the #[global allocator] to call into Rust code wrapping palloc/pfree
[ ] mark the crate as #![no_std] but with extern alloc bringing in normal Rust collections, that, since they default to the global allocator, now call into Postgres' palloc.

This likely means we wind up with a postgres-alloc and/or a postgres-panic crate in a workspace somewhere. And if necessary, recompiling std to guarantee it offers this interface and only this interface can be done.

Destructors are not guaranteed to be run.

True.  And in practice I don't know that they'll even come up as "necessary" within the confines of a single pl/rust function.
However, if we override the global allocator to use Postgres, it's important to point out that we'll lose the ability to do threading.  Postgres is strictly not thread-safe, most especially its MemoryContext system.
You might think, "well, we could wrap the global allocator functions in a Mutex", but the overhead aside, we can't control what the main thread does as it's Postgres proper and won't be routed through Rust's global allocator.

We lose it twice, actually:
Rust's libcore doesn't have std::thread, so #![no_std] means no threads.
It might be possible to do something clever to recover this ability.

So... @Hoverbear showed me some "hack" examples where you can still pull in std:: directly, even with the "no std" thing is.  And we can't control what external crates do -- or can we?

Alright, there were several delays due to... various points of confusion, some of them entertaining, most of them not, but I have now managed to get a global allocator override working. It's enormously crude as I just directly inject the allocator's code and the #![no_std] annotations into the compiled code, But Hey, It Works, and it's not really that far from what PL/Rust currently looks like anyways.
What I haven't done is successfully ungluing and overriding the panic handler... that requires more digging into PGX, because PL/Rust uses PGX to build code for obvious reasons... which means it links in PGX's panic handling code already, which does not play excellently with trying to override the panic handler a second time, causing linking errors. However, this is just solved by taking a hacksaw to PGX and telling it to not ALWAYS add code at various points, so as to make its panic handler modular, which is easily enough done. PL/Rust code does run already with these changes, it's just now in the awkward position of doing needless work.

As far as pulling in std in spite of the crate being #![no_std]: I am not entirely sure how #![no_std] is circumvented here if you directly annotate the crate, but I am very interested in hearing the details of the hack.
The way to get around that would be to use a "bare metal" target that corresponds to "use the current platform's binary object format, but without the platform's C runtime". That way, the contents of std that require runtime support beyond just an allocator would be empty, as one expects. This would be the x86_64-unknown-linux-none and a possible aarch64-unknown-linux-none target that is not a builtin Rust target but I expect would be easily specified.
That would then bring things within striking distance of "actually for real we're just implementing our own std now and using Postgres as the OS".

Knock yourself out:
#![no_std]
extern crate std;

fn main() {
    let s = std::string::String::from("hi");
    std::eprintln!("{s}")
}

https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=241f0043175eadfbe65b946599350262

Oh yeah, extern crate std. Yeah, I am pretty sure that's resoluble by just specifying std again, using rustc --extern to control the mapping, since PL/Rust implies some kind of compiler control, or the unstable -Zbuild-std at worst. The baseline could be an empty std that merely reexports alloc.

I assume this would also prevent other 3rd party crates that might re-export std from exporting the real std and would instead use ours?

Correct. I confirmed last night that we have to build a "full-fledged" new std instead of a "mere" override, as a --extern itself doesn't do enough. So -Zbuild-std it is.

Currently blocked on https://github.com/tcdi/plrust/pull/49 which requires a PR to PGX which I had been drafting. Likely need to toggle a feature based on inclusion of the Postgres allocator or not.

That was unblocked (mostly) and also I got everything building for postgrestd and just need to document and push everything up properly now. This will depend on several forked crates for the first version probably.

As of https://github.com/tcdi/plrust/pull/56 a preliminary x86_64-postgres-linux-gnu tuple works on GNU/Linux with Postgres 14, and it passes build/test cycles on that (though I... somehow managed to break macOS in CI, even without postgrestd???)
The main tradeoff things ran up against is that while I was researching things, it proved untenable to actually carve out entire modules of Rust code at compile time (which was discussed out-of-band as a possible desirable), and I was instead eventually forced to shift towards a strategy of using stubs instead (that can still return failure, success, or whatever based on the implementation).

Yesterday I realized and implemented everything that had to happen to effectuate a new version of the Rust target-specific std::sys implementation that has most of the security properties we're looking for. It should be relatively resilient when ported to different Unix-y systems, or indeed new versions of the Rust compiler, though it is in and of itself largely self-contained.
I haven't explored all the benefits and costs of this implementation yet but it should basically eliminate any questions about safety from Safe Rust while also minimizing the number of forked dependencies needed in the future.

Main insight from spending a bit of time investigating it today: Aside from blocking off std::fs from doing anything of interest, the new variant + the changes in pgx in https://github.com/tcdi/pgx/pull/607 means no longer having to juggle any more forked dependencies just for basic user crates! No guarantee random ecosystem crates won't break, still.

Even libc also no longer requires forking with the revised approach!
As panic handling currently more or less Just Works (well, after I fixed a few cases which surfaced inadequacies in pgx), I have been spending more time on examining the general concern with regard to unsafe code and preventing calling directly into the postmaster process in ways we don't want. This will likely require extending PL/Rust and/or PGX a fair amount with capabilities for analyzing code, or at least doing more interesting build steps.

I still want to modularize the existing panic handler code but it does appear to work, and everything seems to work with aarch64 support as well.


Unclear what happens when a job does not exist

Please specify what will be returned if a job with the given job id does not exist. Will it return null or an exception?

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

ID: 6d288cdf-ad13-52bc-195c-1f103324b78c
Version Independent ID: 1524bf6d-f7fa-f8d8-69c9-5e754583f402
Content: JobOperations.GetJobAsync(String, DetailLevel, IEnumerable<BatchClientBehavior>, CancellationToken) Method (Microsoft.Azure.Batch) - Azure for .NET Developers
Content Source: xml/Microsoft.Azure.Batch/JobOperations.xml
Service: batch
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Batch:0.3822471,Managed Identity:0.12841803,Event Hubs:0.117382236'

@marcelvb Thank you for reaching out, we are looking into it.

@marcelvb You will get "BatchErrorException: Operation returned an invalid status code 'NotFound'" exception.

Thanks for the information. I was expecting the information to be added in the docs at https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.batch.joboperations.getjobasync?view=azure-dotnet.


Initial setup

Initial setup of ssspy.
In this PR, time-domain ICA will be implemented.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@b5e6e3f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop       #1   +/-   ##
==========================================
  Coverage           ?   92.52%
==========================================
  Files              ?        2
  Lines              ?      107
  Branches           ?        0
==========================================
  Hits               ?       99
  Misses             ?        8
  Partials           ?        0

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 b5e6e3f...b33bd4b. Read the comment docs.


fix: regenerate crd manifests to support kubernetes 1.22

Signed-off-by: ankitm123<EMAIL_ADDRESS>The crd manifests were generated by running make manifests in the jx-api repo.

one last thing, I noticed this today and wondered if it affect the work in this PR as on first glance it mentions similar fields https://mail.google.com/mail/u/0/#search/kubernetes/FMfcgzGmtXMhWvHJbHMTPdwXPJpcVqKh

Cant load in gmail ... but is it about the crd bug in 1.23.1 and 1.23.2?

 I think this does not break things.

/lgtm


Is it available to get last time step with return_sequences=True?

As title, is it available to access last time step when recurrent layer's option,'return_sequences=True'?
(As following picture, since deep recurrent need each time step, 'g' need only last time step)
ref: http://arxiv.org/pdf/1506.03340v3.pdf

Besides,
can keras merge 2D shape(ex: (None,300)) and 3D shape(ex: (None,10,300)) do column-wise cosine similarity? That is, I'll get output_shape = (None,10)

you just use a lambda layer:
Lambda(lambda x: return x[:,-1,:])

 a) I tried to use Lambda layer, but I have output_shape error, that is I have the same output_shape as first layer (though ndim is 2)
 b) If I just use `first_layer_recurrent[:,-1,:]` to next layer input, then I have Exception error as following
```Exception: You tried to call layer "dropout_10". This layer has no information about its expected input shape, and thus cannot be built. You can build it manually via: `layer.build(batch_input_shape)` ```
2.
I tried to use mode='dot' to get cosine similarity because mode='cos' used in 3D shape is not better than I expected. (which means its output_shape is (None,1) ).


.deb packaging

what for Debian Gnu/Linux deb?

Sure, that would be nice.
Could you submit a PR? An easy solution would be to use cargo-deb.

I'm not sorry!!!


setValue Error: XML-RPC fault: Generic error (UNREACH)

Hi!
After updating RedMatic to version 7.2.1 I have this issue with my ccu nodes. I have a value node

I want to set the HmIP-BROLL to 60%, i.e. 0.6. The error in the node red debug window is

The corresponding config node for the ccu is

I'm not sure what this "UNREACH" means. Abd the message string in the debug window is
"    < HmIP-RF setValue Error: XML-RPC fault: Generic error (UNREACH)"
Is there something missing in front of the "<"?
What about the authentication? As far as I remember that was not present in the previous version... What do I have to fill in there? The login information from the web interface?
What about the RaspberryMatic firewall? I set it to

The ports I found somewhere in the internet, but they should not be neccessary for local access, right?
If I can help with additional infos, please don't hesitate to ask! I'm grateful for every hint, thanks in advance!

XML-RPC fault: Generic error (UNREACH) is an error returned by eQ-3s interface process. Please try if this is really a Redmatic-specific problem by trying if you can operate that device from eQ-3s Web UI.
CCU firewall and authentication settings are irrelevant for node-red-contrib-ccu when running on the ccu itself (what RedMatic does).

 The update was on the day I moved the RaspberryMatic to another room. Now one BROLL is out of reach, it was exactly the one I used for testing. I didn't even think of trying another one, don't know why :-(
I'm sorry, it was all my fault! Think I need some kind of range extender...


Obtain data from Pavlo where metabolomics and transcriptomics was measured in the same conditions

We want 1 metadata file, that explains what experimental design parameters uniquely identify each condition.
And a datafile that contains metabolites x conditions and expression x conditions, where metabolites are bigg ids, and expression is gene ids that match the model. if not, then we need another datafile that maps metabolite ids to model metabolite ids and data gene ids to model gene ids.


add teaser image min size

fix safari mac tag issue

@projectmushroom :+1:  just a suggestion to add padding on the bottom so that the tags are not too tight


Incorrect results while using Translatable + 'order by'

The incorrect result seem to come from the fact that all the values are stored in plain text and sorting text column is entirely different world than sorting integer column.
Example:
id | title | sort_order
1  | a     | 5
2  | a     | 28
Query: select.. order by sort_order DESC, title ASC
While checking the results you will notice that the item 1 is before item 2, which would mean that the sort_order is higher, which is not the case.

@dinamic the sorting is not done by the PHP code but by the database. So open an issue to MySQL/SQLite/PgSQL/...

the fact that the value of integer is stored in string @stof this cannot be solved using this model of translatable. or having a database specific casts executed would solve it partially


Feature: mention prominent users of scorecard in readme

We should mention, in dedicated section:

sos.dev
deps.dev
metrics.openssf.org

@olivekl can you take care of this?

Sure, will do. Thanks for the suggestion!

FWIW sos.dev looks like a publicity stunt to me (like the great mfa project https://github.com/ossf/great-mfa-project/issues/52) so I'm not sure scorecard should associate itself with it (even though all those projects are under the OpenSSF umbrella) :-)
Just to clarify, I think scorecard is the only OpenSSF project I think is thought-out and useful.


Compilation Errors Incomplete

It seems as if phpdoc automatically generates the  "No summary was found for this file" error for PHP files that have syntax errors.
If there is an error in the PHP file,  I see "No summary was found for this file" in the list of compilation errors. This is the only error displayed, and it's very confusing because the file absolutely does have a summary file. It's even more confusing when the PHP file executes as expected (e.g. when the true syntax error appears in a place of rarely-reached code).
Here is a screenshot of the Compilation Error for the file:

Here is a screenshot of the top of my file, so you can see there is, in fact, a file summary:

I only made the connection between a parsing error and this incorrect error message because I noticed something when I ran the phpdoc command (trying to get the invalid error to go away):

To be clear, the error is this:
Parse Error: Syntax error, unexpected '[', expecting ',' or ')' on line 1064

Yet the compilation error stored is "No summary was found for this file."
This is output from the command-line, and as my project is very large, this reporting is often lost on me completely. The only reason I was about to see this file was that it came later in the project filenames, leaving it visible on my console screen. While it is visible (many other files are not -- my console only keeps so much output), it's not easy to spot.
Is there a reason that the Compilation Errors page doesn't include the actual Parse Error that phpdoc reported? I wouldn't mind if the "No summary was found for this file" error was there so long as the actual parsing error was also there to direct me to the real issue.
(In case you're wondering, the actual culprit for this issue was a ternary statement that had a missing $ on a variable. The line number for the error was dead on.)

This is resolved in v3.0.0-alpha1. Console output will report syntax errors now.


User flow

description
Currently, when a user goes back from the encounter details to the encounters list, the users position in the list is not saved. This means the user has to rescroll through all of the previous months data in order till they reach the intended encounter.
We want to change this so that the users state is stored when they return back to the encounters list.
Outcomes
Discover how to implement saving user state
Acceptance Criteria
Given User has list of Encounters
When user Clicks on the Load Previous Month button
AND Clicks on an Encounter from previous month
AND Clicks on return to encounter list
Then User can see the previously loaded months Encounters

Going to implement the dropdown approach as shown [https://drive.google.com/drive/folders/1OX70kyanz3mJQbTY7uqaddHyxfIW_rbT](Link to wireframes)


patch: update stripbuildinfo.patch

ACK b4b202a792b03bea141a6052ff800c78b4df4947
Tested that updated patch applied cleanly to current Bitcoin Core master. Did not build, but changes look sane.


Display albums in original list order in addition to grouping by artist

Reposting from forum.

Is there any way to display the albums without grouping by artist? So in a similar way as in the Bandcamp web interface: all the albums in purchase order.

bump! Is there a chance to show the albums in a flat list. I mean without grouping by artist.

Not too difficult, and I'd like this feature as well. Am thinking of putting the all-album view as default for both collection and wishlist, and adding an item at the top "group by artist".

Resolved in 4a981d05b21b39652b36358d28f40430e5be0e74


Collections matchers should work with Iterables

It's reasonable to want to use any of the unittest collections matchers with generic iterables, not just collections.

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


HtmlEditorExtender stripes out pre tag

Hello. I have coded my own quoting system since HtmlEditorExtender does not have a quote system. Or does it have?
for quote, i am using pre tag. However, the latest HtmlEditorExtender in version 16.1.0 stripes out the pre tag. It just removes the part that contains pre tag.
I mean like

CeFurkan: Wrote
dsfsdfs

This is removed at the client side before posting to the server. How can i allow this tag?
I also tried with span class="myClass" and it removes class tag this time
my settings are
code behind
htmlEditorExtender1.EnableSanitization = true;
front code
<ajaxToolkit:HtmlEditorExtender ID="htmlEditorExtender1" TargetControlID="txtMessageBody"
                   runat="server" DisplaySourceTab="True">
                   <Toolbar>
                       <ajaxToolkit:Undo />
                       <ajaxToolkit:Redo />
                       <ajaxToolkit:Bold />
                       <ajaxToolkit:Italic />
                       <ajaxToolkit:Underline />
                       <ajaxToolkit:StrikeThrough />
                       <ajaxToolkit:Subscript />
                       <ajaxToolkit:Superscript />
                       <ajaxToolkit:JustifyLeft />
                       <ajaxToolkit:JustifyCenter />
                       <ajaxToolkit:JustifyRight />
                       <ajaxToolkit:JustifyFull />
                       <ajaxToolkit:InsertOrderedList />
                       <ajaxToolkit:InsertUnorderedList />
                       <ajaxToolkit:CreateLink />
                       <ajaxToolkit:UnLink />
                       <ajaxToolkit:RemoveFormat />
                       <ajaxToolkit:SelectAll />
                       <ajaxToolkit:UnSelect />
                       <ajaxToolkit:Delete />
                       <ajaxToolkit:Cut />
                       <ajaxToolkit:Copy />
                       <ajaxToolkit:Paste />
                       <ajaxToolkit:BackgroundColorSelector />
                       <ajaxToolkit:ForeColorSelector />
                       <ajaxToolkit:FontNameSelector />
                       <ajaxToolkit:FontSizeSelector />
                       <ajaxToolkit:Indent />
                       <ajaxToolkit:Outdent />
                       <ajaxToolkit:InsertHorizontalRule />
                       <ajaxToolkit:HorizontalSeparator />
                   </Toolbar>
               </ajaxToolkit:HtmlEditorExtender>

And web config
<ajaxControlToolkit useStaticResources="true" renderStyleLinks="false" htmlSanitizer="AjaxControlToolkit.HtmlEditor.Sanitizer.DefaultHtmlSanitizer, AjaxControlToolkit.HtmlEditor.Sanitizer" />

By the  way it was working at my previous version which was <IP_ADDRESS>
Also when we enable  EnableSanitization it does check at the server side too right?

someone else proposed this solution and it seems like working
what do you think @MikhailTymchukDX  ?
http://stackoverflow.com/questions/37715579/htmleditorextender-stripes-out-pre-tag/37723213?noredirect=1#comment62920527_37723213

The
 tag is designed for pre-formatted text blocks like program code, etc. Pre-formatted text saves newlines and whitespace sequences as is. HtmlEditorExtender cannot work with such blocks now - it saves text only, but collapses a whitespace symbol sequence into a single whitespace.

We recommend you use the
 tag for quoting instead of
, because it is specially designed for quoting and is supported by the extender.

By the way it was working at my previous version which was <IP_ADDRESS>

We checked this version and found that sanitization was broken at that time, so keeping
 tag was actually a bug.

Also when we enable EnableSanitization it does check at the server side too right?

Yes, that’s right.

someone else proposed this solution and it seems like working

This is another way of solving the problem. However, custom sanitizer implementation can affect your site security, so make sure it prevents XSS attacks.

oh ty let me try blockquote tag for quote system


landscape.io

@astagi
Please add nanpy to https://landscape.io/ . I added nanpy but it wasn't refreshed so I removed it.
It may work with your administrator rights.

Added with my account! But it looks that in README the badge points to a valid url that shows Nanpy... dunno what I have to do now :)

Ok it works! :) :)