Customizations & AccountNotFoundException

AFT Version: 1.7.0
Bug Description
When applying Step Functions (aft-invoke-customizations) with all account specified i encountered the following error
"type": "all"
{
    "time_stamp": "2023-01-03 10:45:09,527",
    "log_level": "ERROR",
    "log_message": {
        "FILE": "aft_customizations_identify_targets.py",
        "METHOD": "lambda_handler",
        "EXCEPTION": "An error occurred (AccountNotFoundException) when calling the DescribeAccount operation: You specified an account that doesn't exist."
    }
}
Traceback (most recent call last):
  File "/var/task/aft_customizations_identify_targets.py", line 64, in lambda_handler
    account_email = orgs_agent.get_account_email_from_id(account_id)
  File "/opt/python/lib/python3.8/site-packages/aft_common/organizations.py", line 247, in get_account_email_from_id
    response: DescribeAccountResponseTypeDef = self.orgs_client.describe_account(
  File "/opt/python/lib/python3.8/site-packages/botocore/client.py", line 508, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/opt/python/lib/python3.8/site-packages/botocore/client.py", line 915, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.AccountNotFoundException: An error occurred (AccountNotFoundException) when calling the DescribeAccount operation: You specified an account that doesn't exist.

On the log before the error i have the "Getting details for xxxxxxxxxx" but that account is existing
I'm not sure but it seems to be a deactivated account
how to handle this case ?
Thanks

Hi @Menahem1,
Thanks for the report. This could be caused by trying to describe a suspended account - are there any records in the aft-request-metadata DynamoDB table for suspended accounts?

Hi @stumins
Thanks for your reply !
On aft-request-metadata all the account's are in status "active"

We just released AFT 1.8.0 which includes a fix to ignore suspended accounts when invoking customizations.
Please upgrade to 1.8.0 and let us know if it resolves this issue.

Thanks @stumins it's better now !


concurrent or paralle data processing for  tables dynamically loading  react bootstrap table2

Hi Allen,
This is  Suresh. I am using  your component  and managed  all the scenarios. One scenario, I got  stucked. I am explaining the issue. I have   huge amount  of  data array json  with contains  different users..while I was click on the  button , it was loadded no of tables based on the user name..   suppose  user 1 has  500 records, user2 has 300 records..at the moment I manged the code  using map arrays as a faster  inserting the data in tables ..    chrome is fine to be loading.. good performance.. Issue with IE11, it will take long  time running script.. around 50 sec to be loadded  all the data.. Now I stucked with  performance lacking..   just  I  remeber you.. do you have suggetion to be using parallel processing or concurrent process using your plugin.. if there  any feature to be insert the  data dynamically to different table at a same time?
my json  array is
[{
{user1: data..
user2:data...
}]

if you have any suggetion , please  welcome.. really I am sdpending lot of times...  and that too I am not using react hooks.. old way existing applciation we are using..

I guess the better way to handle this is just render content only in viewport and lazy load/render when user scroll the view. I can be a feature for react-bootstrap-table2 but I really need some time to handle this. So PR is welcome.
However, I have no idea why IE11 is so slow than chrome. maybe you can try to profiling the page to find the root cause. thanks


Update patches for rekt images 1.2

Adding a correct version rekt test image replacement patch
MAKE RELEASE  (does revert FIPS, on purpose).

Next: do a better FIPS patch

1.2.1 for eventing core , which is this image
there is no 1.2.3 version of that image
On Mon 9. May 2022 at 17:02, Pierangelo Di Pilato @.***>
wrote:

@.**** commented on this pull request.
In openshift/patches/override-rekt-images.patch
https://github.com/openshift-knative/eventing-kafka-broker/pull/247#discussion_r868114706
:

-+      image: registry.ci.openshift.org/openshift/knative-v1.2.3:knative-eventing-test-event-flaker
++      image: registry.ci.openshift.org/openshift/knative-v1.2.1:knative-eventing-test-event-flaker

promotion version is 1.2.3
—
Reply to this email directly, view it on GitHub
https://github.com/openshift-knative/eventing-kafka-broker/pull/247#pullrequestreview-966299236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABGPTRL3WMDTMSPYW553NDVJESG7ANCNFSM5VOSCQTA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

--
Sent from Gmail Mobile

We already build these images
https://github.com/openshift/release/blob/8ad723db0fd5ba76a2f685b0fc1bdbdfd2ed9e84/ci-operator/config/openshift-knative/eventing-kafka-broker/openshift-knative-eventing-kafka-broker-release-v1.2__410.yaml#L56-L63

ok, yeah - they should have been used there too.
I will update the correct coordinates, not just the version
Thanks

Once this all is in... Will do same for 1.3


add editor.exclude config for Fuzzy Finder

Add support for editor.exclude in config.js to affect Fuzzy Finder.  Default is still **/node_modules/**.  This works great outside of git repositories and I'm pretty sure it works within git repositories.  The exclude list for git-ls only applies to untracked files and I'm still including --exclude-standard which includes the whole .gitignore file so I don't have too many files left to try excluding.

Awesome! Thanks @keforbes !


GVA: Create a Gallery container UI

Added the Gallery container UI
MOB-2404

I think we should define a new theme for a gallery in Unified UI. Gallery has title and image which are not exist in Persistent button card.

@DavDo Yes. Will implement it with https://glia.atlassian.net/browse/MOB-2405


support overriding the log level in tests

Haven't 100% tested this yet, but this PR should make it much easier to bump up log verbosity when diagnosing things.
/cc @ssalinas @jhaber

tested this out as well, worked well for me 👍


updated makemkv (1.9.8)

Thank you for the contribution. It was merged directly as 8b375837214b7440a385436ad1eb7f234e894c50 to keep commit history cleaner. Your contribution is still credited to you.


Fix bug in subquery join filters referencing outer query

Which issue does this PR close?

Closes https://github.com/apache/arrow-datafusion/issues/2415
Rationale for this change

Fixes a bug.
What changes are included in this PR?

The issue was that the SQL parser was delegating to the LogicalPlanBuilder to build a filter expression and the LogicalPlanBuilder is not aware of subqueries and outer query schemas, so it failed to resolve the join expression that referenced the outer query schema.
The SQL planner now just creates the Filter expression directly.
Are there any user-facing changes?

No

@alamb @Dandandan @yjshen This is ready for review. I'm not sure why we're normalizing column names when building the logical plan rather than during optimization but this is the approach that the logical plan builder was already taking so I just kept things consistent to avoid any test regressions.

I'm not sure why we're normalizing column names when building the logical plan rather than during optimization but this is the approach that the logical plan builder was already taking so I just kept things consistent to avoid any test regressions.

I think this was part of @houqp 's work (maybe in  https://github.com/apache/arrow-datafusion/pull/1023) to properly handle multiple relations in a query


Workbook Conditional Access - Unprotected application - False positive

This workbook can show us which application was used without the CA policy. In my example, the workbook shows me that a user (who uses Teams Web) signed in through an unprotected app.
This user has switched organization (Azure portal, Web Teams, ...) and this successful login log are generated

This SignIn will appear as an unprotected signin but that's normal because you don't pass through your CA but through the CA of the resource tenant ID.

The request should not be like this:
SigninLogs
| project
AppDisplayName,
UserDisplayName,
ConditionalAccessStatus,
Status,
ResultType,
TimeGenerated,
CorrelationId,
OperatingSystem = tostring(DeviceDetail.operatingSystem),
HomeTenantId,
ResourceTenantId
| where ResultType == 0 // sign-in was successful
| where ConditionalAccessStatus == "notApplied"
| where Status.additionalDetails != "MFA requirement satisfied by claim in the token" and Status.additionalDetails != "MFA requirement skipped due to remembered device" // Sign-in was not strong auth
| where HomeTenantId == ResourceTenantId
| project TimeGenerated, CorrelationId, OperatingSystem
Thanks

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

ID: 4992b1c9-ec34-0a76-c3a8-44053881cf48
Version Independent ID: 63858d21-669c-1995-21d6-ec94da5e5715
Content: Conditional access gap analyzer workbook in  Azure AD - Microsoft Entra
Content Source: articles/active-directory/reports-monitoring/workbook-conditional-access-gap-analyzer.md
Service: active-directory
Sub-service: report-monitor
GitHub Login: @MarkusVi
Microsoft Alias: markvi

Hi @MathiasMSFT , were you hoping to leave feedback about a particular document that should be modified, or were you hoping to relay feedback to the product team?

Hi @MarileeTurscak-MSFT , yes my comment is to this article: https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory/reports-monitoring/workbook-conditional-access-gap-analyzer.md

Thanks! Could you clarify if you would like something updated in the document itself?

Hi @MarileeTurscak-MSFT. I changed the description, it's better ?

Thanks for clarifying. Closing this out to move this to the intake form or PR as discussed.


feat: support double click to select scaffold

Preview:

Codecov Report

Merging #895 (232352e) into release/1.2.1 (bb3ff8b) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release/1.2.1     #895   +/-   ##
==============================================
  Coverage          57.14%   57.14%
==============================================
  Files                  1        1
  Lines                 70       70
  Branches              15       15
==============================================
  Hits                  40       40
  Misses                30       30

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 bb3ff8b...232352e. Read the comment docs.


Process hosting the camera service has died unexpectedly

android.hardware.camera2.CameraAccessException: Process hosting the camera service has died unexpectedly
at android.hardware.camera2.utils.CameraBinderDecorator$CameraBinderDecoratorListener.onCatchException(CameraBinderDecorator.java:81)
at android.hardware.camera2.utils.Decorator.invoke(Decorator.java:84)
at java.lang.reflect.Proxy.invoke(Proxy.java:393)
at $Proxy1.cancelRequest(Unknown Source)
at android.hardware.camera2.impl.CameraDeviceImpl.stopRepeating(CameraDeviceImpl.java:926)
at android.hardware.camera2.impl.CameraCaptureSessionImpl.close(CameraCaptureSessionImpl.java:378)
at com.example.android.camera2basic.Camera2BasicFragment.closeCamera(Camera2BasicFragment.java:633)
at com.example.android.camera2basic.Camera2BasicFragment.onPause(Camera2BasicFragment.java:460)

This sample has been migrated to a new location where we can accept Pull Requests (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.
If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!


This is not true. It goes through the same event handler. Just tested it. Not sure what you ran into.


TestMutualTlsReachability is failing in post-submit

https://prow.k8s.io/view/gcs/istio-prow/logs/istio-integ-k8s-tests/6144
--- FAIL: TestMutualTlsReachability (103.08s)
	mtls_test.go:48: Applying policies from "global-mtls-on.yaml".
	mtls_test.go:41: Tearing down policy "global-mtls-on.yaml".
	mtls_test.go:48: Applying policies from "global-mtls-permissive.yaml".
	mtls_test.go:41: Tearing down policy "global-mtls-permissive.yaml".
	mtls_test.go:48: Applying policies from "global-mtls-off.yaml".
	mtls_test.go:41: Tearing down policy "global-mtls-off.yaml".
	mtls_test.go:48: Applying policies from "single-port-mtls-on.yaml".
	mtls_test.go:41: Tearing down policy "single-port-mtls-on.yaml".
	testcontext.go:162: error scope cleanup: 3 errors occurred:

		* exit status 1: Error from server (NotFound): error when deleting "/logs/artifacts/reachability-test-c920ee78aa074/_suite_context/env-kube-522986965/istio-kube-accessor-282214095/accessor_921230794": serviceaccounts "c" not found
		Error from server (NotFound): error when deleting "/logs/artifacts/reachability-test-c920ee78aa074/_suite_context/env-kube-522986965/istio-kube-accessor-282214095/accessor_921230794": services "c" not found
		Error from server (NotFound): error when stopping "/logs/artifacts/reachability-test-c920ee78aa074/_suite_context/env-kube-522986965/istio-kube-accessor-282214095/accessor_921230794": deployments.extensions "c-v2" not found

		* exit status 1: Error from server (NotFound): error when deleting "/logs/artifacts/reachability-test-c920ee78aa074/_suite_context/env-kube-522986965/istio-kube-accessor-282214095/accessor_210967201": serviceaccounts "d" not found
		Error from server (NotFound): error when deleting "/logs/artifacts/reachability-test-c920ee78aa074/_suite_context/env-kube-522986965/istio-kube-accessor-282214095/accessor_210967201": services "d" not found
		Error from server (NotFound): error when stopping "/logs/artifacts/reachability-test-c920ee78aa074/_suite_context/env-kube-522986965/istio-kube-accessor-282214095/accessor_210967201": deployments.extensions "d" not found

		* exit status 1: Error from server (NotFound): error when deleting "/logs/artifacts/reachability-test-c920ee78aa074/_suite_context/env-kube-522986965/istio-kube-accessor-282214095/accessor_581595020": serviceaccounts "headless" not found
		Error from server (NotFound): error when deleting "/logs/artifacts/reachability-test-c920ee78aa074/_suite_context/env-kube-522986965/istio-kube-accessor-282214095/accessor_581595020": services "headless" not found
		Error from server (NotFound): error when stopping "/logs/artifacts/reachability-test-c920ee78aa074/_suite_context/env-kube-522986965/istio-kube-accessor-282214095/accessor_581595020": deployments.extensions "headless" not found

It seems that the test fail at tear down step. I don't know exactly how it was handled. Do you have any hint?

Looks like it doesn't take into account the namespace when deleting resources, just resources were not found.

@diemtvu are you working on this?

I am trying, but probably need some helps from @nmittler or @ozevren.

PR I linked seems to fix this, but I think it is more covering the issue rather than fixing the root cause

Agreed. Get your patch in, but let's not close this yet.

This test has since been renamed to TestReachability and is now green on testgrid. Closing for now.


⚠ Fetchers has degraded performance

In 41d33e6, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 2202 ms

Resolved: Fetchers performance has improved in dcbce8a.


Add support for spaced values

fixes #12

hi @lennartkoopmann @joschi mind taking a look? 🙏

Closed via 38d8d8e80eb91be4b1de03214b7bdcf150453f0c


Locations not avalable

It appears that most locations are not available, we ether have to increase cost or settle for less.

We have found a suitable location, although not ideal.


Integrate with google/oss-fuzz for continuous fuzz-testing?

Hey I'd like to suggest adding littlefs to google/oss-fuzz. If you aren't familiar with fuzz testing, here is a bit of a run down (from Wikipedia);

In programming and software development, fuzzing or fuzz testing is an automated software testing technique that involves providing invalid, unexpected, or random data as inputs to a computer program. The program is then monitored for exceptions such as crashes, failing built-in code assertions, or potential memory leaks.

Google offers a free continuous fuzzing service called OSS-fuzz. If littlefs is integrated into oss-fuzz, the fuzz tests under littlefs will be built and then run once a day, to search for bugs and vulnerabilities in littlefs. This service can be integrated with the CI for littlefs, so that the fuzz tests are run for 10min or so for every pull request, preventing buggy code from being merged.
I've opened up a pull request to add a basic fuzz-testing harness here https://github.com/littlefs-project/littlefs/pull/1029. If you are keen on adding littlefs to oss-fuzz I'd be happy to champion the integration :)

Hi @silvergasp, thanks for creating an issue and volunteering on this. I think it would be quite neat to seem something like this integrated eventually.
Unfortunately the timing is a bit rough. There's a large body of unreleased work in progress, and until that lands I'm not sure it makes sense prioritization wise to aggressively search out bugs in the current codebase. That is unless you're also volunteering to fix them :)
That being said, I think this idea is a good idea eventually, that eventually just not being now unfortunately...

Though there are still interesting things to discuss related to fuzz testing.

If littlefs is integrated into oss-fuzz, the fuzz tests under littlefs will be built and then run once a day, to search for bugs and vulnerabilities in littlefs.

This seems very useful, eventually, when time can be allocated on bug fixing.

This service can be integrated with the CI for littlefs, so that the fuzz tests are run for 10min or so for every pull request, preventing buggy code from being merged.

So this is quite an interesting topic. Fuzz tests on PRs seem like a good idea initially, but are actually a nightmare for contributors in practice.
Quite a bit of effort actually went in to making sure the current test runner/tests are strictly deterministic, so any CI failure is a result of, and only a result of, changes in the given PR.
This doesn't rule out randomness testing, and I've been using quite a bit of it in the above-mentioned body of work, but any randomness testing on PRs needs to be derived from a reproducible seed that was also tested on master.

Ah it looks like there is already some fuzzing or something similar done through littlefs-fuse?

Ah, not really. Describing that as "fuzz-like" is probably inaccurate. It's "fuzz-like" in that it's not fuzz testing. It's just a very high-level test (compiling/simulating littlefs on littlefs via fuse) that is high-level enough you no longer know exactly what is being tested, similar to fuzz testing. Still, it did find a number of unknown bugs during initial development.

Unfortunately the timing is a bit rough. There's a large body of unreleased work in progress, and until that lands I'm not sure it makes sense prioritization wise to aggressively search out bugs in the current codebase. That is unless you're also volunteering to fix them :)

What are your thoughts on me re-targeting this fuzzing effort onto the unreleased work? I imagine that it'd be useful in stabilising the unreleased work. I've personally found fuzzing pretty useful in day-to-day development as it will often quickly find edge cases I hadn't thought about. I've often found security vulnerabilities e.g. buffer overflows etc. in my own work before I released it.
I'm happy to contribute fixes, although I only have a surface level familiarity with the littlefs codebase.

So this is quite an interesting topic. Fuzz tests on PRs seem like a good idea initially, but are actually a nightmare for contributors in practice.

Quite a bit of effort actually went in to making sure the current test runner/tests are strictly deterministic, so any CI failure is a result of, and only a result of, changes in the given PR.

Yeah that's a reasonable stance, the PR based CI integration is entirely optional and not a prerequisite for integration into oss-fuzz.

This doesn't rule out randomness testing, and I've been using quite a bit of it in the above-mentioned body of work, but any randomness testing on PRs needs to be derived from a reproducible seed that was also tested on master.

It is possible to configure libfuzzer to be deterministic via the "-seed" command line option. It's worth noting that I would be using clusterfuzz lite for PR based fuzzing which does upload the artifacts to github i.e. the fuzzing input that triggered a bug. So it is easy enough to reproduce a bug even if the CI isn't deterministic. e.g. it would look something like this.
# download fuzz input from github action artifacts.

# Run the fuzz harness with a single input.  It looks like it would require fairly minimal modifications to port your fuzz tests over to libfuzzer which would significantly improve the speed and performance of fuzzing.  Then it picks the input that produced the most code coverage and randomly mutates the input to create new inputs. This process is repeated in such a way that the "goal" of the fuzzer becomes to maximise code-coverage in a closed-loop system.
Black box fuzzing (existing)
This approach to fuzzing is considered to be open-loop and does not use feedback to improve future results.
flowchart LR
    A[Random Input] --> B[Fuzz Harness]
    B --> A

With black-box fuzzing the probability of finding a bug does not change over time.
Grey box fuzzing (libfuzzer)
This approach to fuzzing is considered to be closed-loop and does use feedback to improve future results.
flowchart LR
    A[Random Input] --> B[Fuzz Harness]
    B --> C[Collect code coverage information]
    C -->  D[Mutate orgional input to maximize coverage]
    D --> B

The probability of finding a bug in a closed-loop system like this increases over time.

What are your thoughts on me re-targeting this fuzzing effort onto the unreleased work? I imagine that it'd be useful in stabilising the unreleased work. I've personally found fuzzing pretty useful in day-to-day development as it will often quickly find edge cases I hadn't thought about. I've often found security vulnerabilities e.g. buffer overflows etc. in my own work before I released it.

Oh, that's not a bad idea.
I guess the only problem is that this work is still in flux and likely to change. I don't think I will have the bandwidth to respond to bug reports until this work enters the stabilization phase. Though at that point fuzz testing work like this would be very useful.

It's worth noting that I would be using clusterfuzz lite for PR based fuzzing which does upload the artifacts to github i.e. the fuzzing input that triggered a bug. So it is easy enough to reproduce a bug even if the CI isn't deterministic.

It's not so much the reproducibility, though that is neat, as much as it's trying to prevent new contributers/PRs from finding bugs they are not responsible for and are unlikely to know how to deal with.

After a bit of a look into your existing random/fuzz testing it looks like you are doing something like open-loop fuzzing. It looks like it would require fairly minimal modifications to port your fuzz tests over to libfuzzer which would significantly improve the speed and performance of fuzzing.

Ah yes, let me be the first to admit that the fuzz testing in the test_runner is naive. But the flipside of this is that it's also simple. Writing tests involves almost as much debugging of the tests as the filesystem itself, so I'm a bit hesitant to add external dependencies to the test_runner core.
But that doesn't prevent having additional testing to run afterwards.
It would be interesting if clusterfuzz/oss-fuzz could generate a test case in littlefs's test toml format, so we could easily compile previously found bugs into a suite of small regression-preventing tests.

I guess the only problem is that this work is still in flux and likely to change. I don't think I will have the bandwidth to respond to bug reports until this work enters the stabilization phase. Though at that point fuzz testing work like this would be very useful.

No worries it seems like now isn't necessarily great timing. But if down the line you are nearing stabilisation and you want to go "hey please fuzz-test this part of the API" feel free to ping me and I'll have a crack at it.

It's not so much the reproducibility, though that is neat, as much as it's trying to prevent new contributers/PRs from finding bugs they are not responsible for and are unlikely to know how to deal with.

Yeah, that seems reasonable. Perhaps this might be more useful when oss-fuzz hasn't found a new bug in a month or two. Then the probability of the PR fuzzer finding something that a contributor isn't responsible for would be fairly low. Especially given that oss-fuzz runs every night for a few hours on a distributed cluster. Whereas the CI fuzzer would be running on a single core for 5-10min in github actions.

Ah yes, let me be the first to admit that the fuzz testing in the test_runner is naive. But the flipside of this is that it's also simple. Writing tests involves almost as much debugging of the tests as the filesystem itself, so I'm a bit hesitant to add external dependencies to the test_runner core.

I think the fuzz testing harnesses themselves seem to be quite extensive and pretty far from naive. But perhaps the method of driving the harnesses could be improved by switching to a coverage driven fuzzing framework like libfuzzer.
It's worth noting that libfuzzer is shipped as a component of llvm/clang. So while it is true that it does add a dependency it's largely covered by just switching from gcc->clang.

It would be interesting if clusterfuzz/oss-fuzz could generate a test case in littlefs's test toml format, so we could easily compile previously found bugs into a suite of small regression-preventing tests.

Hmm I think it would be possible, although I'd have to do a bit more of a deep dive into your existing testing infrastructure to be sure. There is some work going into structure-aware fuzzing but that does require additional dependencies on protobuf for example. It might look something like toml->protobuf->fuzzing_seed_corpus. So it seems possible, but maybe a little complicated for a first pass.
Another option for this might be to use google/fuzztest for the harnesses which will generate googletest regression harnesses when it finds a failure. google/fuzztest also has compatibility layers for libfuzzer and integrates nicely into oss-fuzz. But it does add a couple third-party dependencies and additional build complexity.


www.findthemasks.com should redirect to findthemasks.com

This should help reduce likelihood of duplicated content. Also ensure everyone is linking to the same URL's. The redirect should be a perm redirect (301) and should retain the request URI (i.e. if you go to https://www.findthemasks.com/give.html?state=ca it should redirect you to https://findthemasks.com/give.html?state=ca).

Hi, I don't think this is necessary. I have dreamhost set up to allow both www. and bare, and the content is the same. no duplication.

If you disagree please explain more thoroughly

It's just a best practice to ensure only one domain is in use; see more here: https://support.google.com/webmasters/answer/66359?hl=en
Alternatively, you could "canonicalize" with the appropriate meta tags, see: https://moz.com/learn/seo/canonicalization, e.g.
<link rel="canonical" href="https://findthemasks.com/" />

Unfortunately that would need to be done for every single page (with the appropriate URL plugged in). Usually it's just easier to do the domain redirect 😄

Closing; not really worthwhile, considering the testing/validation effort 😄


As a CS student, I can add my peers’ preferred tech stacks

... so that I can find people to work with for tech projects and hackathons.

This can be done with tags.


Is it possible to pass in parallelism via the command line?

Is it possible to pass in parallelism via the command line?
I tried to setup a parameter to do this, but got an error about the value not being a number.
Failed to parse workflow:
error unmarshaling JSON: while decoding JSON: json:
cannot unmarshal string into Go struct field WorkflowSpec.parallelism of type int64

If it's not possible by default to set this for the workflow from the command line, is there a way of coercing a string containing a number into a number?
Edit: Do you have anything like an int filter? I heard you were using Jinja but I can't find it within the codebase.

Is it possible to pass in parallelism via the command line?

Currently not possible.

Do you have anything like an int filter? I heard you were using Jinja but I can't find it within the codebase.

Not as far as I know.

If it's not possible by default to set this for the workflow from the command line, is there a way of coercing a string containing a number into a number?

Could you elaborate a bit on this? Are you trying to run dynamically generated Workflows?

If it's not possible by default to set this for the workflow from the command line, is there a way of coercing a string containing a number into a number?

Could you elaborate a bit on this? Are you trying to run dynamically generated Workflows?

I tried this at one point, but it doesn't work:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: global-parallelism-parameter-
spec:
  entrypoint: entrypoint-name
  arguments:
    parameters:
    - name: parallelism
      value: 10
  parallelism: "{{workflow.parameters.parallelism}}"

I'm not trying to run dynamicly generated workflows. I just wanted to be able to configure the level of parallelism a workflow should be run by at the point of submission.

I see. I don't think we currently support a way to pass in parameters to the Workflow object... only to Template objects within a workflow.
A workaround suggestion I could give you would be to use sed to replace the placeholder value before submitting. Something like this:
$ cat workflow.yaml | sed 's/"{{workflow.parameters.parallelism}}"/10/g' | argo submit --watch -

I'm also running into this issue when trying to have parallelism be a parameter of a workflow template

I don't think any information is needed? The label was removed not added.
I think the solution executed in #3610 could work here too.
Would anyone be interested in submitting a PR?

I can try working on this and create a PR

Hi, any plan to support this soon? I was expecting at least one of these to work:

parallelism: "{{ workflow.parameters.parallelism }}"
parallelism: "{{=asInt(workflow.parameters.parallelism)}}"

I was surprised asInt() didn't fix this casting error, shouldn't it work in all spec levels?

I was surprised asInt() didn't fix this casting error, shouldn't it work in all spec levels?

I believe this is because it's quoted. As mentioned above, #3610 made some fields able to parse those into ints, but not all fields.

Hi @sasagarw, Do you have any updates on this? Thanks

Hi @alexec,
This would be a great feature and would leverage the strengths of Argo Workflows to loop / iterate over Lists and be able to use simpler templates and control the parallelism of those via workflow variables or generated variables / values out of steps.
Is there much missing or is it just an issue with linting the string as an integer?

Is there much missing or is it just an issue with linting the string as an integer?

It was mentioned above that the same approach as #3610 could be used here. Right now the spec expects an int, for this feature it would need to also allow a string (which it can convert to an int)

It would be nice to be able to set parallelism to a variable {{input.parameters.parallelism}}. Especially when trying to set parallelism to a workflow input parameter.
Tested: parallelism: {{=asInt(workflow.parameters.parallelism)}} it doesn't work.


visible: 'false', not working

I took this addlayer example
with the mentioned js and css.
fitted a line
			visible: 'false',
and the code is
    overlayGroup.getLayers().push(         new ol.layer.Image({             title: 'Countries', 			visible: 'false',             minResolution: 500,             maxResolution: 5000,             source: new ol.source.ImageArcGISRest({                 ratio: 1,                 params: {'LAYERS': 'show:0'},                 url: "https://ons-inspire.esriuk.com/arcgis/rest/services/Administrative_Boundaries/Countries_December_2016_Boundaries/MapServer"             })         })     );
I expected the Countries image overlay as unchecked.
But I got this, checked

As mentioned in:
ol/layer/Image API
visible | boolean |  | true | Visibility.

Hi, try:
visible: false
In JavaScript 'false' is a non-empty string which will evaluate to true.

Thanks !! Your right.


First and last bars do not display correctly on bar chart with time axis

The first and last bars in bar chart with a time-axis do not display properly.  The first bar overlaps and covers the y-axis.  The last bar is half the width when compared to the other bars.
https://codesandbox.io/s/quizzical-hooks-4dpmy

I'm seeing this as well.

same here! Y axes are being are being croped, even using line,
in my case its line, not bar,
it acquires when ordinal is use:
const axes = React.useMemo(
    () => [
      { primary: true, type: '**ordinal**', position: 'bottom' },
      { position: 'left', type: 'linear', stacked: true },
    ],
    []
  );
  );

its ok when linear is use:
  const axes = React.useMemo(
    () => [
      { primary: true, type: 'linear', position: 'bottom' },
      { position: 'left', type: 'linear', stacked: true },
    ],
    []
  );

wierd result if I change time to linear:

Hello, Team.
I am also having this issue.
Isn't there any workaround?

Due to a massive overhaul and rewrite of React Charts to TypeScript and a massively upgraded public API, this issue is being bulk closed for triage. The latest version can be tested via the react-charts@beta tag. Documentation is in the process of being upgraded, but thankfully, everything is fully typed now, so you can explore the API that way for now.
If, after testing or playing with the v3 beta, you believe your issue is still not addressed or relevant, feel free to open a new issue.


AutoSPInstallerModule.psm1 Fails to make SQL alias correctly if WFE name is similar to SQL host name.

Unusual environment has discovered an edge case!
The WFE host is "NMS-SPUAT" the SQL Host is "NMS-SPUATSQL".
in AutoSPInstallerModule.psm1 Function Add-SQLAlias () line 7256:

If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\"))) {
        $protocol = "dbmslpcn" # Shared Memory
        }
    else {
        $protocol = "DBMSSOCN" # TCP/IP
    }

Match computer name is returning a false positive as this is supposed to be checking if the SQL host is the same machine as the sharepoint host and using named pipes instead of TCP/IP.
The cliconfig entry also gets really odd...

Changing it to:
If (($SQLInstance -eq $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +""))) {
May fix it, I'll leave it to your team to fix it the best way possible


scorecard creation and edit pages

Currently, the only way to create a scorecard is via the rest api. The ability to create and edit scorecards is a major component of CubScout.

Blocked by #4, #3


DashProducts xml

After the migration the Prestashop modules are replaced by their Thirty Bees equivalents. In the case of Dash Products it looks like that doesn't happen completely: the config.xml afterwards still says that the author is Prestashop while in the dashproducts.php file the author is thirtybees.
I know this is a small thing. But if this happens to one file it may happen to other too...

Thanks for the report. That's a bit surprising, because updating a module should delete it's entire folder, then unpack the new version. This should also delete config.xml, which gets re-created automatically.

This isn't a problem of the migration module, but of thirty bees module update code. Tracked in https://github.com/thirtybees/thirtybees/issues/1025


Use evented dataclass for grid

Description
This PR follows on from #1910, #1911, #1912 by using an evented dataclass for the grid. Note this PR drops the grid.events.update event, which can be replaced by connecting grid.events directly.
This should be reviewed after the other mentioned PRs
Type of change

[x] Refactor (non-breaking change which fixes an issue)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

This PR has been updated from master and is now ready for review @jni Note it no longer breaks anything as the grid.update event was already dropped in #1926. This PR also no longer contains the changes of #1912 and so can be merged independently.


New features in LIS for GVF DA and SMAP_E_OPL soil moisture DA

Description
Codes for VIIRS GVF, CDFS GVF, and SMAP_E_OPL soil moisture DA have been added in LIS
Testcase
SMAP_E_OPL DA: /discover/nobackup/projects/usaf_lis/ykwon/SoilMoisture_DA/testcases/noah39/noah39_CONUS_10km/DA_MCDF_SMAP_E_OPL
VIIRS GVF DA:
/discover/nobackup/projects/usaf_lis/ykwon/SoilMoisture_DA/testcases/noahmp401/noahmp401_CONUS_10km_dynamic/DA_VIIRS_GVF
CDFS GVF DA:
/discover/nobackup/projects/usaf_lis/ykwon/SoilMoisture_DA/testcases/noahmp401/noahmp401_CONUS_10km_dynamic/DA_CDFS_GVF

Hi @yhkwon81
I dusted off this pull request, and am having problems accessing the first test case.  Can you please open up:
/discover/nobackup/projects/usaf_lis/ykwon/SMAP_E_OPL/testcases/TEST_02_historical_L1B/SM_retrieval
?

Hi @yhkwon81
I tried running the VIIRS DA test case, and I notice the GVF names expected by LIS are different from what are in your test directory.  LIS expects:
GVF-WKL-GLB_v2r3_npp_e20210102.nc
But your directory (/discover/nobackup/projects/usaf_lis/ykwon/SoilMoisture_DA/testcases/noahmp401/noahmp401_CONUS_10km_dynamic/DA_VIIRS_GVF/VIIRS_GVF/2021/) has
GVF-WKL-GLB_v2r3_j01_e20210102.nc
So the LIS executable is not reading the VIIRS data.  I don't see anything in the lis.config file that would explain this.

Disregard last message about reading VIIRS data.  I made a mistake in creating a symbolic link.  Data is being read now.

I changed the permission. Thanks.
From: Eric Kemp @.>
Reply-To: NASA-LIS/LISF @.>
Date: Friday, July 29, 2022 at 3:40 PM
To: NASA-LIS/LISF @.>
Cc: "Kwon, Yonghwan (GSFC-617.0)[UNIVERSITY OF MARYLAND]" @.>, Mention @.***>
Subject: [EXTERNAL] Re: [NASA-LIS/LISF] New features in LIS for GVF DA and SMAP_E_OPL soil moisture DA (PR #1111)
Hi @yhkwon81https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fyhkwon81&data=05|01|yonghwan.kwon%40nasa.gov|f3168414b961487490e008da719a3e1b|7005d45845be48ae8140d43da96dd17b|0|0|637947204531644894|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=mEPvn8hAo2ab70rAEjD%2FjbiF%2FMmDaK5dLO%2Bpre%2B%2Fas4%3D&reserved=0
I dusted off this pull request, and am having problems accessing the first test case. Can you please open up:
/discover/nobackup/projects/usaf_lis/ykwon/SMAP_E_OPL/testcases/TEST_02_historical_L1B/SM_retrieval
?
—
Reply to this email directly, view it on GitHubhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNASA-LIS%2FLISF%2Fpull%2F1111%23issuecomment-1199888360&data=05|01|yonghwan.kwon%40nasa.gov|f3168414b961487490e008da719a3e1b|7005d45845be48ae8140d43da96dd17b|0|0|637947204531644894|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=B%2F5JrSnyd6CqpwP3b8fOTGWURiuZudpKqKahnGzYx0o%3D&reserved=0, or unsubscribehttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMAPSH3KOUB25HCTHG466VDVWQXT5ANCNFSM5YDTGQLA&data=05|01|yonghwan.kwon%40nasa.gov|f3168414b961487490e008da719a3e1b|7005d45845be48ae8140d43da96dd17b|0|0|637947204531644894|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=aLuqnevmlR9%2BXGdDtofJdTEAdRi3pcDxICVTjof1sHw%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

Thanks @yhkwon81.  I'm running the SMAP DA test case now.

Hi @yhkwon81
Can you open up read permissions in /discover/nobackup/projects/usaf_lis/ykwon/SoilMoisture_DA/testcases/noah39/noah39_CONUS_10km/DA_MCDF_SMAP_E_OPL/OUTPUT so I can compare my results with yours?
Thanks.

I changed the permission for the OUTPUT directory. Please try again.
Thanks.
From: Eric Kemp @.>
Reply-To: NASA-LIS/LISF @.>
Date: Monday, August 1, 2022 at 10:02 AM
To: NASA-LIS/LISF @.>
Cc: "Kwon, Yonghwan (GSFC-617.0)[UNIVERSITY OF MARYLAND]" @.>, Mention @.***>
Subject: [EXTERNAL] Re: [NASA-LIS/LISF] New features in LIS for GVF DA and SMAP_E_OPL soil moisture DA (PR #1111)
Hi @yhkwon81https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fyhkwon81&data=05|01|yonghwan.kwon%40nasa.gov|23b7daa710954763096008da73c66a93|7005d45845be48ae8140d43da96dd17b|0|0|637949593277361371|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Yla3ImpKVxn0RwufjiqDx7nYWHomJHJTMuvgnLckMUY%3D&reserved=0
Can you open up read permissions in /discover/nobackup/projects/usaf_lis/ykwon/SoilMoisture_DA/testcases/noah39/noah39_CONUS_10km/DA_MCDF_SMAP_E_OPL/OUTPUT so I can compare my results with yours?
Thanks.
—
Reply to this email directly, view it on GitHubhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNASA-LIS%2FLISF%2Fpull%2F1111%23issuecomment-1201247041&data=05|01|yonghwan.kwon%40nasa.gov|23b7daa710954763096008da73c66a93|7005d45845be48ae8140d43da96dd17b|0|0|637949593277518368|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=kOkY1J9o24NvYWPcXuD87H%2FhtJg2sptGBsMmBuKdl0U%3D&reserved=0, or unsubscribehttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMAPSH5UU4E2B5WH56K3TILVW7KFNANCNFSM5YDTGQLA&data=05|01|yonghwan.kwon%40nasa.gov|23b7daa710954763096008da73c66a93|7005d45845be48ae8140d43da96dd17b|0|0|637949593277518368|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2BuxvU%2B%2FosQWn4v1EdRK98Ywcl0av2jh58pUehgMOwQA%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @yhkwon81
Apologies, but I don't have read permissions for the subdirectories in /discover/nobackup/projects/usaf_lis/ykwon/SoilMoisture_DA/testcases/noah39/noah39_CONUS_10km/DA_MCDF_SMAP_E_OPL/OUTPUT/SURFACEMODEL.  Can you please run chmod again, and make sure all subdirectories and their contents are readable?

I changed the permission. Please try to access the directory again.
From: Eric Kemp @.>
Reply-To: NASA-LIS/LISF @.>
Date: Tuesday, August 16, 2022 at 3:54 PM
To: NASA-LIS/LISF @.>
Cc: "Kwon, Yonghwan (GSFC-617.0)[UNIVERSITY OF MARYLAND]" @.>, Mention @.***>
Subject: [EXTERNAL] Re: [NASA-LIS/LISF] New features in LIS for GVF DA and SMAP_E_OPL soil moisture DA (PR #1111)
Hi @yhkwon81https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fyhkwon81&data=05|01|yonghwan.kwon%40nasa.gov|67004cbbe60b4b21625608da7fc11f29|7005d45845be48ae8140d43da96dd17b|0|0|637962764673009915|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=CCKEpuFyh31qkdnImxTJRRNxA%2FNmbTy6yEOBEd0ss4Q%3D&reserved=0
Apologies, but I don't have read permissions for the subdirectories in /discover/nobackup/projects/usaf_lis/ykwon/SoilMoisture_DA/testcases/noah39/noah39_CONUS_10km/DA_MCDF_SMAP_E_OPL/OUTPUT/SURFACEMODEL. Can you please run chmod again, and make sure all subdirectories and their contents are readable?
—
Reply to this email directly, view it on GitHubhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNASA-LIS%2FLISF%2Fpull%2F1111%23issuecomment-1217095381&data=05|01|yonghwan.kwon%40nasa.gov|67004cbbe60b4b21625608da7fc11f29|7005d45845be48ae8140d43da96dd17b|0|0|637962764673009915|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=m6qdDPqBlsHnnFA5NPtckHEhFi9frO2SGb6v1%2F%2F8SEI%3D&reserved=0, or unsubscribehttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMAPSH62M5UNDFTQ6LMAZ43VZPWW3ANCNFSM5YDTGQLA&data=05|01|yonghwan.kwon%40nasa.gov|67004cbbe60b4b21625608da7fc11f29|7005d45845be48ae8140d43da96dd17b|0|0|637962764673009915|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=0ne%2Bhf34SmWkSkrKjGs%2BeRbGVc4v1mNkJkPPptFU%2BgU%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

Thanks @yhkwon81.  I'm satisfied that my results reproduce yours.  I need to coordinate with @jvgeiger about your test cases before I accept this pull request.

Actually, I spoke to soon.  You need to add documentation for the new VIIRS GVF, SMAP_E_OPL, and CDFS GVF entries in the lis.config file before we can proceed.

I copied my test input and output files to /discover/nobackup/projects/lis/PR_TESTCASES/1110.  I will go ahead and approve this pull request.


persist cluster-enabled status in RocksDB

To close #1410 .

@git-hulk Please help review :)

@chrisxu333 Please, run ./x.py format to format the codebase and CI will be happy :)

Hi @git-hulk could you also help diagnose why test is failed? It was successful when I did locally.

Hi @git-hulk could you also help diagnose why the newly introduced testcase is failed? It was successful when I did locally.

perhaps you can have a try at debug yourself, and I will also take a look while I'm free.


ci: merge travis matrix, add salt-lint & rubocop to lint job

Semi-automated using https://github.com/myii/ssf-formula/pull/60

:tada: This PR is included in version 0.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


deep-link

Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: deep-link
Document link: deep-link.md
My Issue/Suggestion

For the Headline of Chapter 3.4: Instead of "3.4 Adding the Configuration Overview Snippet the Custom Admin Page"
would not "3.4 Adding the Configuration Overview Snippet to Custom Admin Page" be more correct?

Hi @Larvi77,
Nice catch! I just corrected it, and the right version will be online soon. Thanks!
Kind regards,
Yiyun


Vulnerability: Issue description can lead to forged site

I just edited https://github.com/polarsource/polar/issues/986.
The link to fund now leads to my polar page.
I wonder: If I can setup a forged site, especially in your case, nobody would expect that this is not the original site.

A possible solution might be to create a chat bot that answers to the issue. I don't know!

Hey. While this might be confusing, it's not a vulnerability. As clicking the link doesn't do anything.
While the polar github app could look for and replace invalid polar-embeds, there is nothing we can do against someone embedding other images or links.


node['nexus3']['path'] is incorrect

node['nexus3']['path'] has default value of "/opt" on linux, rather than the documented value of "/opt/sonatype". This causes problems on both install (chown -R nexus:nexus /opt) and on uninstall (rm -fr /opt).

This must have changed in 3.2 and the tests missed it. Where is this documented, so I can update home and data attributes?  If you want to submit a PR for this, that would be welcomed as well.
default['nexus3']['home'] = "#{node['nexus3']['path']}/nexus3"
default['nexus3']['data'] = "#{node['nexus3']['path']}/sonatype-work/nexus3"

README.md documents the default value of node['nexus3']['path'] to be "Default Linux: /opt/sonatype Windows: #{ENV['SYSTEMDRIVE']}/sonatype." However, the actual default value defined in attributes/default.rb is
default['nexus3']['path'] = '/opt'

This was changed in the latest commit, from prior value of '/opt/sonatype'
The needed fix is to revert the value of this setting. The work-around is to just override the default setting.

When migrating from 3.0 to 3.1, nexus changed the install and configuration which wasn't backwards compatible.  I bumped the major version from 1 to 2 to comply with semver.  The current install follows the documention referenced here: https://books.sonatype.com/nexus-book/reference3/install.html#installation-archive.
I guess the readme attributes were not updated to reflect this.  I will update the readme to reflect the change.  Sorry about the confusion.
I would just update the attribute to be node.override['nexus3']['path'] = '/opt/sonatype' to get to what you are wanting.

This cookbook has been adopted: https://github.com/criteo-cookbooks/nexus3


Add keyboard mapping.

Dear Team,
Would it be possible to implement EUA International Keyboard?
On android when placing this type of keyboard, the right ALT is responsible for accentuating the Latin characters.
right ALT + e = é
right ALT + i = í
right ALT + , = ç
But i`m using Uperfect X lapdock (SIPODEV USB) when right ALT change language.
With the EUA International Keyboard I could use the accent like in the other OS. (would be next to Greek 220 and 319 Latin)
' + e = é
' + i = í
' + c = ç
Best Regards

If de Greek Latin add options:
' + a = á
' + e = é
' + i = í
' + o = ó
' + u = ú
' + c = ç
This is a perfect correspondences


we need to clean branches

deleting stale branches with CI and maybe using another contribution workflow

maybe using this https://github.com/actions/stale ?

some of these ones are from previous PRs https://github.com/aristanetworks/openmgmt/branches/active

we can use this https://github.com/actions/stale to automate this


How to not allow swipe the cell, when the swipe button is selected

i am going to develop the function, when i click on the swipe button, it will hide automatically and not allow to swipe the cell again.
if orientation == .right && (testingArray[indexPath.row] == false) {
let btnTakethis = SwipeAction(style: .default, title: "TAKE THIS") { action, indexPath in
self.testingArray[indexPath.row] = true
}
btnTakethis.hidesWhenSelected = true
let image : UIImage = UIImage(named: "btn_menu")!
btnTakethis.font = UIFont.boldSystemFont(ofSize: 12.0)
btnTakethis.backgroundColor = #colorLiteral(red: 0.996206224, green: 0.781045258, blue: 0.1831639111, alpha: 1)
return [btnTakethis]
}
Here is my part of code, it is work perfectly to not allow the cell swipe again if the SwipeState is center. When i click the button, it will close with an animation, but it is still can swipe until the state is center

Its not clear to me what you are trying to do. Please post a sample app or a screenshots of what you are trying to accomplish. Closing this issue for now. Thanks.


Restructure forking cheatcodes reference

Addresses https://github.com/foundry-rs/book/issues/454
Overview of changes:

Create individual reference pages for each of the 5 forking-related cheatcodes
(Attempt to) explain holistically both approaches to fork testing in overview page (forking mode/CLI vs. forking cheatcodes/Solidity)
Make note of soon-to-change storage behavior (coming with https://github.com/foundry-rs/foundry/pull/2301) in overview page
Rename and move fork testing overview page to Advanced Testing section
Make note of cheatcode-based approach in Forking Mode tutorial

Shoutout to @mattsse who I believe did most of this work 🙌 the forking cheatcodes are super powerful! My PR is mostly just reorganizing the docs and trying to simplify/clarify in some places.

@onbjerg made few updates to reflect your feedback. Thank you for the review! 🙏

Thanks for this! :smile: @all-contributors add @neodaoist for docs


feat: luarocks support

as requested :smile:

ty!

🤔 needs further investigation: https://github.com/nvimtools/none-ls-extras.nvim/actions/runs/8528941209/job/23363638627

seems -scm tags are only available on the dev package index.

about the semver problem: can we use a version number like 0.0.0-20240403?

seems -scm tags are only available on the dev package index.

luarocks can install dev packages with the --dev flag. rocks.nvim\s :Rocks install command will automatically add that flag if the version is dev or scm. And it will prompt to search the dev manifest if no release version is found.

about the semver problem: can we use a version number like 0.0.0-20240403?

That would be a valid luarocks specrev, but it isn't currently supported by the luarocks-tag-release workflow (it has it hardcoded as 1 for non-PR workflow runs).
When it comes to setting dependency version bounds in a rockspec, I don't think you can use the specrev.

🤔 needs further investigation: https://github.com/nvimtools/none-ls-extras.nvim/actions/runs/8528941209/job/23363638627

I've created https://github.com/nvim-neorocks/luarocks-tag-release/issues/404 and will fix it after work today.


Added lang_only as new langTagResolver

Added possibility to be able to get only the lang tag as result, in order to limit the language files to one for each language, i.e. locale-de.json, locale-en.json. Especially useful when using the staticFilesLoader.

@ThinklabsGbR
Thank you for contribution. Please follow https://github.com/angular-translate/angular-translate/blob/master/CONTRIBUTING.md which contains some notes about contribution steps in this project.
Particular in this case, I remark the followings:

apply a proper commit message (see in guideline about conventional changelog)
add a test (for the other resolvers they are included, just search for bcp47 in translate.determineLocale.spec.js)
please rename the resolver name: lang_only => iso639-1
the new option should be mentioned in the list of available (incl. an example, i.e. same as in test?): $translateProvider.uniformLanguageTag

Superseeded by 1e037ec


authors are twice

ex: https://impactu.colav.co/app/affiliation?type=group&id=65fb545d3f94c992f874709c&section=research&tab=products

fixed pr #283


langchain-community[major]: Upgrade community to pydantic 2

This PR upgrades langchain-community to pydantic 2.

Most of this PR was auto-generated using code mods with gritql (https://github.com/eyurtsev/migrate-pydantic/tree/main)
Subsequently, some code was fixed manually due to accommodate differences between pydantic 1 and 2

Breaking Changes:

Use TEXTEMBED_API_KEY and TEXTEMBEB_API_URL for env variables for text embed integrations:  https://github.com/langchain-ai/langchain/pull/26011/commits/cbea780492b7afde84b06f9780cdaeaa7770b2a7

Other changes:

Added pydantic_settings as a required dependency for community. This may be removed if we have enough time to convert the dependency into an optional one.

This PR passes unit tests and extended tests across both python versions for langchain-community.
There are still (many) type checking issues that we will investigate separately.


Update dask dependencies according to requirements.txt

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Modin version (modin.__version__):
Python version:
Code we can use to reproduce:

Describe the problem

Source code / logs

Closed via #2325


do the dataprocess

when i  run the  data_processing  of  self-dpdn  first,then i run the data_processs of secondpose  second,then i meet this problem!can you give me some help?where the detection  i can download?

Hi, The detection folder is just the segmentation results. I suggest to add a soft link in the data folder from the folder segmentation_results to detection.

hello!when i start train,i alwalys meet the problem like this:

Hi, The detection folder is just the segmentation results. I suggest to add a soft link in the data folder from the folder segmentation_results to detection.

hello,When I start training, I always encounter the following problems：
Epoch 1 :
2024-01-02 10:11:41,480 - [1/60][0/4999][0] Train - loss: 17.91323      vp_loss: 0.17252  ip_loss: 0.66172  rho_acc: 0.00000  phi_acc: 2.08333residual_angle_loss: 124.16344  5d_loss: 0.00000  lr: 0.000001      T_data: 11.999    T_forward: 5.742  T_backward: 0.558
2024-01-02 10:12:11,450 - [1/60][50/4999][50] Train - loss: 15.46198    vp_loss: 0.14857  ip_loss: 0.60527  rho_acc: 4.00000  phi_acc: 5.25000residual_angle_loss: 111.86561  5d_loss: 0.00000  lr: 0.000014      T_data: 0.074     T_forward: 0.283  T_backward: 0.241
2024-01-02 10:12:47,679 - [1/60][100/4999][100] Train - loss: 8.56143   vp_loss: 0.08075  ip_loss: 0.48615  rho_acc: 6.54167  phi_acc: 6.41667residual_angle_loss: 86.32484   5d_loss: 0.00000  lr: 0.000039      T_data: 0.170     T_forward: 0.314  T_backward: 0.240
2024-01-02 10:13:27,278 - [1/60][150/4999][150] Train - loss: 4.74307   vp_loss: 0.04347  ip_loss: 0.39627  rho_acc: 10.16667 phi_acc: 8.66667residual_angle_loss: 69.64372   5d_loss: 0.00208  lr: 0.000064      T_data: 0.239     T_forward: 0.308  T_backward: 0.244
libpng error: Read Error
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/01215/0005_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/05483/0004_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/06223/0002_color.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/real/train/scene_1/0520_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/22504/0006_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/16628/0009_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/25396/0008_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/04380/0001_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/12581/0008_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/real/train/scene_4/0440_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/05071/0009_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/21895/0002_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/25711/0006_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/19343/0000_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/16666/0002_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/16102/0006_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/04881/0007_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/camera/train/10406/0008_depth.png'): can't open/read file: check file path/integrity
[<EMAIL_ADDRESS>global /io/opencv/modules/imgcodecs/src/loadsave.cpp (239) findDecoder imread_('/media/ailab/DJ/data/real/train/scene_4/0485_depth.png'): can't open/read file: check file path/integrity
Traceback (most recent call last):
File "/data2/dj/SecondPose-main/train_geodino.py", line 142, in
Trainer.solve()
File "/data2/dj/SecondPose-main/utils/solver_category.py", line 50, in solve
dict_info_train = self.train()
File "/data2/dj/SecondPose-main/utils/solver_category.py", line 76, in train
for i, data in enumerate(self.dataloaders["train"]):
File "/home/ailab/anaconda3/envs/Secpose/lib/python3.9/site-packages/torch/utils/data/dataloader.py", line 628, in next
data = self._next_data()
File "/home/ailab/anaconda3/envs/Secpose/lib/python3.9/site-packages/torch/utils/data/dataloader.py", line 1333, in _next_data
return self._process_data(data)
File "/home/ailab/anaconda3/envs/Secpose/lib/python3.9/site-packages/torch/utils/data/dataloader.py", line 1359, in _process_data
data.reraise()
File "/home/ailab/anaconda3/envs/Secpose/lib/python3.9/site-packages/torch/_utils.py", line 543, in reraise
raise exception
AttributeError: Caught AttributeError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/home/ailab/anaconda3/envs/Secpose/lib/python3.9/site-packages/torch/utils/data/_utils/worker.py", line 302, in _worker_loop
data = fetcher.fetch(index)
File "/home/ailab/anaconda3/envs/Secpose/lib/python3.9/site-packages/torch/utils/data/_utils/fetch.py", line 58, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/ailab/anaconda3/envs/Secpose/lib/python3.9/site-packages/torch/utils/data/_utils/fetch.py", line 58, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/data2/dj/SecondPose-main/provider/dataset_category.py", line 274, in getitem
data_dict = self._read_instance_cat(index, cat)
File "/data2/dj/SecondPose-main/provider/dataset_category.py", line 296, in _read_instance_cat
tuple = get_data(index)
File "/data2/dj/SecondPose-main/provider/dataset_category.py", line 293, in get_data
return self._load_data(img_path,
File "/data2/dj/SecondPose-main/provider/dataset_category.py", line 473, in _load_data
depth = load_composed_depth(img_path)
File "/data2/dj/SecondPose-main/utils/data_utils.py", line 32, in load_composed_depth
if len(depth.shape) == 3:
AttributeError: 'NoneType' object has no attribute 'shape'
I can guarantee that my data set is fine, I have completed some preparatory work, can you give me guidance？

That's quite strange error, it seems to be a problem with the data folder, not related to this repository. The same dataset is also used in VI-Net(https://github.com/JiehongLin/VI-Net) I would suggest to try running the code of VI-Net to check if the error is still there. If that's the case your might need to check what's wrong with your data folder.(possibly some files are damaged?)

@NOrangeeroli
Thank you for your previous explanation, I'm sorry to bother you again, I want to ask where the file in the picture below is, can you provide the .npy file？

@NOrangeeroli Thank you for your previous explanation, I'm sorry to bother you again, I want to ask where the file in the picture below is, can you provide the .npy file？

Hi,
Thanks for pointing out the issue, that file is no longer needed for current version of our code. I've cleaned it. Please check out the latest code. Sorry for the inconvenience!
Best,
Yamei


Use Custom User model for admin panel

Hello, I am using custom User model which isn't inherited from AbstractUser.
Is it possible to use my custom User model for both my app and admin panel login?
If so, how can I get it working?

You can custom login provider, see example


Create new nickel patch to customise new navigation scrubber

The navigation scrubber is new in 4.17 so there aren't any existing patches. I am planning to add one. I have found the relevant nickel CSS code.
Like issue 26, it will be of most use to users whose language is not officially supported by Kobo, e.g. Russian, where the default Avenir font is pretty hopeless and the fallback CJK font even worse.

@geek1011,
Added new patch to nickel.yaml/jackie_w.yaml ready for next release.


Would there be a native support for macOS?

Hi, a great idea and I hope it lands well.
Currently HotA requires wine / parallels to run on non-windows platforms. Is this going to be finally fixed in this project?
Thanks for the work you are doing

@smnbbrv  I have no testing macOS machine, but current master should compile for Linux and Windows. And run. and play.
So no real reason for no macOS support except proper testing + bunch of build scripts linke bundle installation and so on. If you have macOS developer setup, you can check out what am I missing in CMake atm.
Nothing really platfrom-specific in my project - except windows registry lookup to find HotA installation on Windows host (that is optional and just for convenience).

And HotA conparison is unfair (as it has not source code etc), fair is comparison to https://github.com/vcmi/ (and VCMI project is far ahead of FH, except HotA support probablty. And good RMG. That's it)


Create Valet aliases

https://laravel.com/docs/5.5/valet is an amazing, lightweight dev tool for building Laravel/PHP sites.

Hi there, thanks for this. Could you provide a README file in this directory, too?

I'll get you one asap
On Nov 4, 2017 1:42 PM, "Robby Russell"<EMAIL_ADDRESS>wrote:

Hi there, thanks for this. Could you provide a README file in this
directory, too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/robbyrussell/oh-my-zsh/pull/6379#issuecomment-341915854,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AChkMhDj3Id6oshjf9cbxWNwSOwzB0Rqks5szKHygaJpZM4QNQH0
.

Closed due to inactivity.


[QUESTION] - I cannot connect with multiple user when cloned and built locally

I created a room from one tab and tried to join as 2nd users in another tab. On both tabs, the connection gets closed with error Peer connection closed.

I don't think you can really run this locally very well 🤔

You should be able to debug webrtc connection issues by opening your browser's webrtc tabs:

about:webrtc in Firefox
chrome://webrtc-internals in Chrome

if you're not connected to a local network or a firewall is blocking communication to computers on network (e.g. guest network) then local negotiations won't work since <IP_ADDRESS> is not used to find other peers.

So, multiple tabs on same browser or different browsers for different participants on same computer (IP with <IP_ADDRESS>) wouldn't work?

I tried it on LAN and still got the same issue on different device

The README.MD in the repo has configuration instructions. I'm not able to provide installation support via GitHub due to the nuances of different WebRTC browser implementations, configuration options, hosting providers and firewall setups. You might also need to run a TURN/STUN server. If you're able to reproduce the issue on peercalls.com I can look into it

How can I run TURN/STUN server locally? I see the issue is related to stun:
DOMException: Failed to construct 'RTCPeerConnection': 'stun:global.stun.twilio.com:3478?transport=udp' is not a valid stun or turn URL.
    at new p (http://localhost:3000/static/index.js?v0.0.0:2:466536)
    at http://localhost:3000/static/index.js?v0.0.0:2:632730
    at http://localhost:3000/static/index.js?v0.0.0:2:633426
    at Array.forEach (<anonymous>)
    at i.<anonymous> (http://localhost:3000/static/index.js?v0.0.0:2:632377)
    at i.emit (http://localhost:3000/static/index.js?v0.0.0:2:162396)


TFCNs

I recently read your paper, I feel that the method is very novel, you have made the code public, I tried to run your code, the parameters are according to the paper, but the run out of the index is far from your paper, I do not know where the problem, I want to ask you where the problem arises, but also want to trouble you to give you the training of the weight file, that file, very Thank you
I look forward to hearing from you!

Please clarify your question?


[PROPOSAL] Contributing - Docker-Setup for the development of Laravel-excel

Prerequisites
Versions

PHP version:
Laravel version:
Package version:

Description
As I had some trouble getting started Contributing to this Repo. I would suggest adding a Docker-option for local development. As this is what I did in the end.
Example
I already implemented a Basic Docker-Setup to run the tests locally.
As this is copied from different other Projects I could not just PR it.
But if interested I could create a PR for it some time in the coming Weeks.
Additional Information

Personally don't use docker for this package, but I don't mind having it for other people to be able to contribute easier. Feel free to PR it!


Change :protocol on already locally cloned repo not updating in remotes

What's wrong
Trying to get a fork for a :host github :repo "other/repo.el", which is pulled using https, to come from my own fork using ssh.
straight-host-usernames is set. When doing :fork t, the https is correctly fetched, but I cannot get it to use git.
Version information

Emacs version: 27.2
Operating system: Mac

ok, narrowed it down. It works when the repo is not yet cloned. Whenever the repo is already on disk, it is not changed (neither with normalize-package nor fetch-package).

Please provide a reproduction case with straight-bug-report if possible.

(straight-bug-report

  :post-bootstrap

  ;; regular repo
  (straight-use-package 'which-key)

  ;; let's clone
  ;; normally by updating init.el and reload it
  ;; - not clear how to emulate that here
  ;; - instead: Warning (straight): Two different recipes given ...
  (straight-use-package '(which-key
			  :fork (:host github :repo "hans-d")))

  ;; oops, want git
  ;; normally by updating init.el and reload it
  ;; - not clear how to emulate that here
  ;; - instead: Warning (straight): Two different recipes given ...
  (straight-use-package '(which-key
			  :fork (:host github :repo "hans-d"
				       :protocol ssh)))
  ;;:preserve t
  )


How is TinyEmitter.changeCount used?

In https://github.com/phetsims/axon/issues/317#issuecomment-674294227 @zepumph said

This is likely a question for @jonathanolson, but I don't see changeCount ever used, only set and documented. Can you please tell me where changeCount is accessed or used?

I searched for this token and didn't see any usages either.

@zepumph can this issue be closed? Those listeners are called like so:
this.changeCount && this.changeCount( 1 );


ProtonVPN: URL for dmg cannot be extracted anymore

ProtonVPN: URL for dmg cannot be extracted anymore.
The current download URL is https://protonvpn.com/download/ProtonVPN_mac_v4.0.0.dmg, but that is not listed in the HTML under https://protonvpn.com/download

There is a PR here https://github.com/Installomator/Installomator/pull/1283

Believe fixed in Installomator 10.6


[idea] new Op: Conv2DWithBiasActivation for Backends that Support Higher Level Op

This is a repost of the comment here:
Along the lines of MklConv2DWithBias, I suggest defining a new primitive Op, Conv2DWithBiasActivation that can be used to define kernels on platforms that support a higher level primitive conv-bias-acitivation unit.
As far as the (new) fused Conv2D Op that I am using for my BNNS implementation, I used the MKL Conv2D Op as a predicate. In that case Intel has defined a new Op that includes both the convolution Op and the BiasAdd Op. My Conv Op actually isn't pulling in just the activation function, rather, my Op and the MKL both have the bias add has been fused as well.
I understand that the primitive Conv2D op in TF does not currently handle activations or bias addition, but this op may be "too primitive". In fact cuDNN is now moving in the direction of fusing these three into one kernel (see: https://github.com/tensorflow/tensorflow/issues/8828). Perhaps, a different FusedConv2D Op should be added that can be used by not just BNNS but also cuDNN v6 and any other underlying platform implementations that can take advantage of doing all three ops together. This would be  along the lines of batch norm, which now offers a fused version of the Op to reduce the number of primitive Ops used.
Addendum
There are even more implementations that can benefit from fusing Conv-Bias-Activation. Others include:

Metal Performance Shaders (https://github.com/tensorflow/tensorflow/issues/7958). Here it might be extra extra important because of 1. avoiding extra copies back and forth from GPU memory (ie using the tuned MPSTemporaryImage and 2. because MPS uses a very weird memory layout and ideally transposing to this only needs to be done once.
MKL (as linked above, perhaps the MKL specific Op (MklConv2DWithBias) can be unified with this new Op.
cuDNN v6

/CC @drpngx @petewarden @flx42 @gunan

Assigning @petewarden but feel free to bounce.

We're going to be working on fusing ops like this as part of TF Lite, so I don't think this change will make it into the main code base. Closing, but please reopen if you strongly feel the fused ops should exist at this level.

I don't know what TF Lite is, but I guess I do think this would be valuable for TF main.


Consider using "final".

Just food for thought: overriding state properties of controls hardly makes sense, which is the reason why most JavaFX controls use "final" to prevent overriding methods.

I know, did that for Enzo but there have been situations where it would have been nice to be able to override methods which was the reason for not using final everywhere :)


sails no-frontend creates EJS warning

I was running a Sails application using --no-frontend. Upon startup, this message occurs:
Could not find module: ejs in path: /opt/wx-api/node_modules

I updated the config/views.js as follows to supress:
engine: { ext : 'null', fn : function(){} },

Everything works fine just questioning if there is another way.
Also, when running Mocha using sails.lift() from within tests, the application complains that it can't find Grunt.  I installed as a devDependency but would like to remove if I can.

var Sails = require('sails');

process.chdir(APPLICATION_PATH);

before(function(done){

   this.timeout(5000);

   Sails.lift({
       port : 12345,
       log: {
           level: 'error'
       }

   }, function(err, app) {

       sails = app;

       if (err) return done(err);

       done(err, sails);
   });
});

Update: I just added
hooks : { grunt : false }

to Sails.lift(options) and was able to remove

@crh3675 re: grunt-- spot on.  You can also stick that in your .sailsrc file or configure it via env variables (e.g. sails_hooks__grunt=false sails lift).
re: views, what version of NPM and Sails are you using?  We were relying on the nested node_modules structure prior to NPM 3 (i.e. to symlink the ejs dep in sails so you don't have to npm install when running sails new).  The latest 0.12 rc just sticks copies the dependency down, but I'm curious if there's a bug there that's only showing itself when the no-frontend option is enabled.
Thanks!

This issue was moved to balderdashy/sails-generate-new#21

sails-generate-new has no "issues", has it ?

I confirm, created a project with --no-frontend, the .sailsrc gets:
{   "hooks": {     "grunt": false   } }
but the error persists. Sails 0.12.8, npm 3.5.2. Any workaround for this?

I have the same problem, but I don't know how solve it


Build basic python package

To allow integration with downstream methods such as bio_embeddings, I've added configuration files to install PLUS as python package. For this I also had to rename src to plus. If you're satisfied with these changes, would it be possible to publish this on pypi?

Hi Konstin,
Chris told me about the project, and I'm happy to be a part of it!
If you have any issues that I can contribute, please let me know!

Hi Seonwoo,
thank you for the embedding example in #2! Based on this code I've added PLUS as a method in bio_embeddings. Could you please have a look at https://github.com/sacdallago/bio_embeddings/blob/develop/bio_embeddings/embed/plus_rnn_embedder.py and confirm that it's implemented correctly? Could you please also tell me whether bio_embeddings should use d_h or d_z (line 74-78)?

Hi @konstin,
Thank you for integrating PLUS into bio_embeddings!
Yes, I have checked outputs from the original PLUS and bio_embeddings. The results were almost identical.
I think it's better to use d_h as default for the bio_embeddings, so the current implementation seems great.


Gradient Tape (tf.GradientTape) Returning All 0 Values in GradCam

System information

Have I written custom code (as opposed to using a stock example script
provided in TensorFlow): Yes (Custom Loss + GradCam)
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): CentOS Linux 7
TensorFlow installed from (source or binary): PIP
TensorFlow version (use command below): 2.9.0
Python version: 3.7.0
CUDA/cuDNN version:  11.6
GPU model and memory: Nvidia RTX 2080Ti

Describe the problem
I have trained 2 FCN segmentation models, with the same custom loss.
Model 1 ------>  Trained of 256x512 images, on TF==1.15.
Model 2 ------> Trained on 512x1024 images, on TF==2.9.0.
The same GradCam Script works fine on Model 1, but returns 0 (and eventually NaN) for Model 2.
Model1.summary():
 Layer (type)                   Output Shape         Param #     Connected to
==================================================================================================
 input_1 (InputLayer)           [(None, 256, 512, 3  0           []
                                )]

 block1_conv2 (Conv2D)          (None, 256, 512, 64  1792        ['input_1[0][0]']
                                )

 block1_pool (MaxPooling2D)     (None, 128, 256, 64  0           ['block1_conv2[0][0]']
                                )

 block2_conv1 (Conv2D)          (None, 128, 256, 12  73856       ['block1_pool[0][0]']
                                8)

 block2_conv2 (Conv2D)          (None, 128, 256, 12  147584      ['block2_conv1[0][0]']
                                8)

 block2_pool (MaxPooling2D)     (None, 64, 128, 128  0           ['block2_conv2[0][0]']
                                )

 block3_conv1 (Conv2D)          (None, 64, 128, 256  295168      ['block2_pool[0][0]']
                                )

 block3_conv2 (Conv2D)          (None, 64, 128, 256  590080      ['block3_conv1[0][0]']
                                )

 block3_conv3 (Conv2D)          (None, 64, 128, 256  590080      ['block3_conv2[0][0]']
                                )

 block3_conv4 (Conv2D)          (None, 64, 128, 256  590080      ['block3_conv3[0][0]']
                                )

 block3_pool (MaxPooling2D)     (None, 32, 64, 256)  0           ['block3_conv4[0][0]']

 block4_conv1 (Conv2D)          (None, 32, 64,<PHONE_NUMBER>     ['block3_pool[0][0]']

 block4_conv2 (Conv2D)          (None, 32, 64,<PHONE_NUMBER>     ['block4_conv1[0][0]']

 block4_conv3 (Conv2D)          (None, 32, 64,<PHONE_NUMBER>     ['block4_conv2[0][0]']

 block4_conv4 (Conv2D)          (None, 32, 64,<PHONE_NUMBER>     ['block4_conv3[0][0]']

 block4_pool (MaxPooling2D)     (None, 16, 32, 512)  0           ['block4_conv4[0][0]']

 block5_conv1 (Conv2D)          (None, 16, 32,<PHONE_NUMBER>     ['block4_pool[0][0]']

 block5_conv2 (Conv2D)          (None, 16, 32,<PHONE_NUMBER>     ['block5_conv1[0][0]']

 block5_conv3 (Conv2D)          (None, 16, 32,<PHONE_NUMBER>     ['block5_conv2[0][0]']

 block5_conv4 (Conv2D)          (None, 16, 32,<PHONE_NUMBER>     ['block5_conv3[0][0]']

 block5_pool (MaxPooling2D)     (None, 8, 16, 512)   0           ['block5_conv4[0][0]']

 conv2d (Conv2D)                (None, 8, 16, 4096)  102764544   ['block5_pool[0][0]']

 re_lu (ReLU)                   (None, 8, 16, 4096)  0           ['conv2d[0][0]']

 dropout (Dropout)              (None, 8, 16, 4096)  0           ['re_lu[0][0]']

 conv2d_1 (Conv2D)              (None, 8, 16, 4096)  16781312    ['dropout[0][0]']

 re_lu_1 (ReLU)                 (None, 8, 16, 4096)  0           ['conv2d_1[0][0]']

 dropout_1 (Dropout)            (None, 8, 16, 4096)  0           ['re_lu_1[0][0]']

 conv2d_2 (Conv2D)              (None, 8, 16, 2)     8194        ['dropout_1[0][0]']

 conv2d_transpose (Conv2DTransp  (None, 16, 32, 2)   66          ['conv2d_2[0][0]']
 ose)

 conv2d_3 (Conv2D)              (None, 16, 32, 2)    1026        ['block4_pool[0][0]']

 add (Add)                      (None, 16, 32, 2)    0           ['conv2d_transpose[0][0]',
                                                                  'conv2d_3[0][0]']

 conv2d_transpose_1 (Conv2DTran  (None, 32, 64, 2)   66          ['add[0][0]']
 spose)

 conv2d_4 (Conv2D)              (None, 32, 64, 2)    514         ['block3_pool[0][0]']

 add_1 (Add)                    (None, 32, 64, 2)    0           ['conv2d_transpose_1[0][0]',
                                                                  'conv2d_4[0][0]']

 conv2d_transpose_2 (Conv2DTran  (None, 256, 512, 2)  1026       ['add_1[0][0]']
 spose)

==================================================================================================
Total params: 139,544,204
Trainable params: 139,544,204
Non-trainable params: 0

Model2.summary():
Layer (type)                   Output Shape         Param #     Connected to
==================================================================================================
 input_1 (InputLayer)           [(None, 512, 1024,   0           []
                                3)]

 block1_conv1 (Conv2D)          (None, 512, 1024, 6  1792        ['input_1[0][0]']
                                4)

 block1_conv2 (Conv2D)          (None, 512, 1024, 6  36928       ['block1_conv1[0][0]']
                                4)

 block1_pool (MaxPooling2D)     (None, 256, 512, 64  0           ['block1_conv2[0][0]']
                                )

 block2_conv1 (Conv2D)          (None, 256, 512, 12  73856       ['block1_pool[0][0]']
                                8)

 block2_conv2 (Conv2D)          (None, 256, 512, 12  147584      ['block2_conv1[0][0]']
                                8)

 block2_pool (MaxPooling2D)     (None, 128, 256, 12  0           ['block2_conv2[0][0]']
                                8)

 block3_conv1 (Conv2D)          (None, 128, 256, 25  295168      ['block2_pool[0][0]']
                                6)

 block3_conv2 (Conv2D)          (None, 128, 256, 25  590080      ['block3_conv1[0][0]']
                                6)

 block3_conv3 (Conv2D)          (None, 128, 256, 25  590080      ['block3_conv2[0][0]']
                                6)

 block3_conv4 (Conv2D)          (None, 128, 256, 25  590080      ['block3_conv3[0][0]']
                                6)

 block3_pool (MaxPooling2D)     (None, 64, 128, 256  0           ['block3_conv4[0][0]']
                                )

 block4_conv1 (Conv2D)          (None, 64, 128,<PHONE_NUMBER>     ['block3_pool[0][0]']
                                )

 block4_conv2 (Conv2D)          (None, 64, 128,<PHONE_NUMBER>     ['block4_conv1[0][0]']
                                )

 block4_conv3 (Conv2D)          (None, 64, 128,<PHONE_NUMBER>     ['block4_conv2[0][0]']
                                )

 block4_conv4 (Conv2D)          (None, 64, 128,<PHONE_NUMBER>     ['block4_conv3[0][0]']
                                )

 block4_pool (MaxPooling2D)     (None, 32, 64, 512)  0           ['block4_conv4[0][0]']

 block5_conv1 (Conv2D)          (None, 32, 64,<PHONE_NUMBER>     ['block4_pool[0][0]']

 block5_conv2 (Conv2D)          (None, 32, 64,<PHONE_NUMBER>     ['block5_conv1[0][0]']

 block5_conv3 (Conv2D)          (None, 32, 64,<PHONE_NUMBER>     ['block5_conv2[0][0]']

 block5_conv4 (Conv2D)          (None, 32, 64,<PHONE_NUMBER>     ['block5_conv3[0][0]']

 block5_pool (MaxPooling2D)     (None, 16, 32, 512)  0           ['block5_conv4[0][0]']

 conv2d (Conv2D)                (None, 16, 32, 4096  102764544   ['block5_pool[0][0]']
                                )

 re_lu (ReLU)                   (None, 16, 32, 4096  0           ['conv2d[0][0]']
                                )

 dropout (Dropout)              (None, 16, 32, 4096  0           ['re_lu[0][0]']
                                )

 conv2d_1 (Conv2D)              (None, 16, 32, 4096  16781312    ['dropout[0][0]']
                                )

 re_lu_1 (ReLU)                 (None, 16, 32, 4096  0           ['conv2d_1[0][0]']
                                )

 dropout_1 (Dropout)            (None, 16, 32, 4096  0           ['re_lu_1[0][0]']
                                )

 conv2d_2 (Conv2D)              (None, 16, 32, 2)    8194        ['dropout_1[0][0]']

 conv2d_transpose (Conv2DTransp  (None, 32, 64, 2)   66          ['conv2d_2[0][0]']
 ose)

 conv2d_3 (Conv2D)              (None, 32, 64, 2)    1026        ['block4_pool[0][0]']

 add (Add)                      (None, 32, 64, 2)    0           ['conv2d_transpose[0][0]',
                                                                  'conv2d_3[0][0]']

 conv2d_transpose_1 (Conv2DTran  (None, 64, 128, 2)  66          ['add[0][0]']
 spose)

 conv2d_4 (Conv2D)              (None, 64, 128, 2)   514         ['block3_pool[0][0]']

 add_1 (Add)                    (None, 64, 128, 2)   0           ['conv2d_transpose_1[0][0]',
                                                                  'conv2d_4[0][0]']

 conv2d_transpose_2 (Conv2DTran  (None, 512, 1024, 2  1026       ['add_1[0][0]']
 spose)                         )

==================================================================================================
Total params: 139,581,132
Trainable params: 139,581,132
Non-trainable params: 0

Source code / logs
Custom Loss (common for both models)
def self_balanced_focal_loss(alpha=3, gamma=2.0):
    def loss(y_true, y_pred):
        # cross entropy loss
        y_pred = backend.softmax(y_pred, -1)
        cross_entropy = backend.categorical_crossentropy(y_true, y_pred)

        # sample weights
        sample_weights = backend.max(backend.pow(1.0 - y_pred, gamma) * y_true, axis=-1)

        # class weights
        pixel_rate = backend.sum(y_true, axis=[1, 2], keepdims=True) / backend.sum(backend.ones_like(y_true),
                                                                                axis=[1, 2], keepdims=True)
        class_weights = backend.max(backend.pow(backend.ones_like(y_true) * alpha, pixel_rate) * y_true, axis=-1)

        # final loss
        final_loss = class_weights * sample_weights * cross_entropy
        return backend.mean(backend.sum(final_loss, axis=[1, 2]))

    return loss

GradCam Script (Common for both models)
def get_img_array(img_path, size):
    img = keras.preprocessing.image.load_img(img_path, target_size=size)
    array = keras.preprocessing.image.img_to_array(img)
    array = np.expand_dims(array, axis=0)
    return array

def make_gradcam_heatmap(img_array, model, last_conv_layer_name,idx1,idx2):
    # First, we create a model that maps the input image to the activations
    # of the last conv layer as well as the output predictions
    grad_model = tf.keras.models.Model(
        [model.inputs], [model.get_layer(last_conv_layer_name).output, model.output]
    )
   print(grad_model.outputs)
    # Then, we compute the gradient of the top predicted class for our input image
    # with respect to the activations of the last conv layer
    with tf.GradientTape() as tape:
        last_conv_layer_output, preds = grad_model(img_array)
        class_channel = preds[0][idx1][idx2][1]
        print("CLASS CHANNEL", class_channel)

    # This is the gradient of the output neuron (top predicted or chosen)
    # with regard to the output feature map of the last conv layer
    grads = tape.gradient(class_channel, last_conv_layer_output)
    print("GRADS", grads)

    # This is a vector where each entry is the mean intensity of the gradient
    # over a specific feature map channel
    pooled_grads = tf.reduce_mean(grads, axis=(0, 1, 2))

    # We multiply each channel in the feature map array
    # by "how important this channel is" with regard to the top predicted class
    # then sum all the channels to obtain the heatmap class activation
    last_conv_layer_output = last_conv_layer_output[0]
    heatmap = last_conv_layer_output @ pooled_grads[..., tf.newaxis]
    heatmap = tf.squeeze(heatmap)

    # For visualization purpose, we will also normalize the heatmap between 0 & 1
    heatmap = tf.maximum(heatmap, 0) / tf.math.reduce_max(heatmap)
    return heatmap.numpy()

Predictions from both the model yield useful results. However, the heatmap generated via the gradcam script for Model 2 returns 0's, and anything/max(zeros)=NaN
In Model 2, there are no other changes, except minor ones, required to make the code compatible with TF>2, from TF==1.X. Why is it that the tf.GradientTape() is resulting in 0 values regardless of the image input, when the model (on the same images) is able to generate good predictions?
Kindly advise and help,
Thanks.
Edit 01
Kindly check a difference I noticed in the GradCam results of the two models.
Model 1 (Working Gradcam)
  [<KerasTensor: shape=(None, 16, 32, 512) dtype=float32 (created by layer 'block5_conv4')>, <KerasTensor: shape=(None, 256, 512, 2) dtype=float32 (created by layer 'conv2d_transpose_2')>]
CLASS CHANNEL tf.Tensor(0.26052475, shape=(), dtype=float32)
GRADS [-0.02966771 -0.02644881 -0.02611654 ...  0.01653964  0.01702563
  0.01976959]

Model 2 (NaN/0 heatmap)
[<KerasTensor: shape=(None, 32, 64, 512) dtype=float32 (created by layer 'block5_conv4')>, <KerasTensor: shape=(None, 512, 1024, 2) dtype=float32 (created by layer 'conv2d_transpose_2')>]
CLASS CHANNEL tf.Tensor(-0.15865403, shape=(), dtype=float32)
GRADS [-0.00172401 -0.00150979 -0.00142616 ...  0.00059308  0.00060482
  0.00060655]

Thus, the major difference seems to be in the 'class_channel' variable ---> positive in Model 1.

@varungupta31,
I ran the code shared and face a different error, please find the gist here and share all dependencies to replicate the issue or share a colab gist with the reported error. Thank you!

@tilakrayal Hey!
To run the code, you'll need to model file, which I can't share as of now.
Here is a complete gist containing relevant outputs and reported error (NaNs).

@varungupta31,
I ran the code and faced a different error, please find the gist here and share all dependencies to replicate the issue. Thank you!

@varungupta31,
Without the required code, it would be difficult for us to debug the issue. In order to expedite the trouble-shooting process, could you please provide a complete code and the dependencies. Thank you!


Open Source - webstyleguide.baloise.com: technical artifacts

The idea has now again been risen in the context of the IT lead exchange; we could think about actually estimating the steps and effort to do this.

Do you really mean webcomponents? Our angular components are not really web components, they won't be usable outside of an angular application.
Neutral default theming would require a large amount of work, as all the components are not themable at the moment. We could have a theme for a couple of colors - if that's what you think of theming.

Sorry for the name clash: no it does not necessarily have to be web components.
A simple way of theming / having a neutral usage of e.g. colors and logos would be completely sufficient. The idea would be to avoid providing a set of components that would easily support fraud cases for e.g. our corporate identity.
Whereas we're already providing a detailed, non-technical (e.g. consumable angular artifacts) of our style-guide here: https://webstyleguide.baloise.com
IMHO it'd be useful also having technical artifacts / repos being linked here.

@hirsch88 : IIRC this is part of https://github.com/baloise/baloise.github.io/issues/11


Consider changing the default behavior of on_cancelled()

Currently the implementation of BtActionNode::on_cancelled() returns BT::NodeStatus::SUCCESS.  I have found this to be counter-intuitive, as the goal has (by definition) not been successfully completed, and may often require overriding to return a failure.
I would like to get @fmrico's opinion on changing the default behavior to BT::NodeStatus::FAILURE to better reflect what is actually happening.

If I understand correctly, it would not be better in this case to return BT::NodeStatus::IDLE?

Well, the current semantic is BtActionNode::on_cancelled() returns  BT::NodeStatus::SUCCESS if the action could be succesfully cancelled. I think it is reasonable, isn't it?


Missing S3 FIPS endpoints

There are S3 FIPS missing endpoints, see: https://aws.amazon.com/compliance/fips/.

Expected behaviour: minio-go uses the provided S3 FIPS endpoint.
Actual behaviour: minio-go replaces the provided S3 FIPS endpount with the non-FIPS URL in makeTargetURL...

Here's the PR to include missing S3 FIPS endpoints: https://github.com/minio/minio-go/pull/1032

@lucasmrod Thanks for sending in a PR for this issue.

Closing this issue as #1032 is already merged


fixing frontend pagination typo from '1-10 on 15' to '1-10 of 15'

I noticed what I believe to be a typo in the text on the frontend which specifies what items are being shown and the total amount of items. Currently the pagination area reads something like "1-10 on 15" when I think it should be "1-10 of 15." I updated the frontend code and the testing files to this effect.

Thanks!


It also seems that you can get revived after the timeout but you don't get "proper revived", this could be a problem on their end.

Minecraft Version: 1.19.2
YIGD Version: 1.4.6
Hardcore Revival: 9.0.1

Hope you can get a compat for this mod!

 Because that currently has a bug with the charm of keeping, voiding items instead of keeping them. So it could be your armor is voided because twilight thinks it should be kept (charm of keeping 1). I will try and look into the hardcore revival mod however, and see if there's anything I need to do to provide compat

No, not playing with any mod that adds that kind of items. I need to re-test this, think it only happens when reviving after the timeout which isn't supposed to happen. But still, only lose the armor, not the rest. Thanks :)

I finally have proper time to work on this now. But I can't quite get the hardcore revival mod to work fully. Do I have to use it on a server for it to take effect? It didn't work when I tested on a LAN world (by working I mean it didn't say how long I could be rescued for and such. It was the normal death screen which I would assume the mod changes. It didn't look the way the image on the mod's curseforge page did anyway)

I managed to get the mod working, but I could not reproduce the issue. Is this consistant for you?

Ok that's good to know. For anyone who would find a way to consitently reproduce the issue however I'd still like to resolve the issue with hardcore revival mod. Incapacitate mod might be a workaround but I still want to fix the issue


Deprecate, refactor, or scrap old source code in favor of the new sparse implementation.

The new sparse implementation is awesome!  There's a bunch of heritage code that can probably be scrapped as we move towards supporting just the sparse implementation.  In particular the multiorder module is largely deprecated but has a few useful parts: Chebyshev coefficients and some hard-coded attributes, such as speed of light, n_pix, etc.
We should completely remove read_native_PHOENIX_model now that we've migrated to gollum-based inputs.

All done, these codes are currently in a deprecated/ subfolder, we can just delete them someday.


Added an index page, made some css updates as well as various changes to other pages

@zeroSteiner

Just landed this @guitarmanj thanks! I made some minor changes in commit c9e9c29e9dbe5a2deacd21bc47ab1bf900f5c21b to remove a word, some white space and change "Calendar" to "Calendar_Invite" for the email template. Definitely my favorite template combination now.


help pls

https://github.com/JaydenDev/randmsg/issues/1
@webdev03
@hello-smile6

hey @JaydenDev did you stop searchocean?

@webdev03 none, this is literally a basic web page that redirects to a search engine.


Is JOB randomly generated in a WORKER?

I have 2 WORKER with 8 GPU.I want to create 3 jobs.Job 1 and job 2 need 4 GPU,job 3 need 6 GPU.If job 1 is in WORKER 1 and job 2 is in WORKER 2,job 3 can not be created.But it is ok if job 1 and job2 is also in WORKER 1.
So, what can i do to control which WORKER is the job specifically located.
Thanks

the scheduler will do such packing by default. If not, please wait for our 0.16.y release, which includes the HiveD scheduler that support node reservation. https://github.com/microsoft/pai/tree/master/subprojects/GOPATH/src/github.com/microsoft/hivedscheduler


keepalived 1.X: required bump

Issue description
1.45 was released.

1.4.5 since 8302338, though I expect we should default to 2.x now.  Anyway, there's probably little sense in keeping this open.