Gradle dependency not working

Hello,
I am adding this compile compile 'com.github.ronaldsmartin:Material-ViewPagerIndicator:1.0.2' dependency to my gradle file. But its throwing an error Failed to resolve: com.github.ronaldsmartin:Material-ViewPagerIndicator:1.0.2

Hi,
Did you add jitpack as a maven repository in your Gradle file first?
You may have seen it already, but the full install instructions for v1.0.2 are available here.

Also:
Even if you have correctly added Jitpack as a repository, you may still run into issues installing dependencies through Jitpack if your Gradle version is not up-to-date.
As you can see in this Jitpack issue, a number of people had trouble using Jitpack dependencies with Gradle v2.10 and resolved them by updating to 2.11+.

The first one worked. Thank you.


Speculate actual status of timeout action and persist old file id if necessary

This patch causes a timeout when the timeout is not reached.

Good job! The problem is solved. Thanks for @PHILO-HE's powerful support.

Good job! The problem is solved. Thanks for @PHILO-HE's powerful support.

I just pushed a bit changes in another commit with no impact on the test. Will commit the patch soon.

I just pushed a bit changes in another commit with no impact on the test. Will commit the patch soon.


Added verification for server config

Related Issue/Addition to code

Fixes #17, Fixes #83, Fixes #84

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed Changes

Added yup to validate server configuration changes
Added a blacklist of values to be not allowed to be change ['server-port', 'server-ip]';
Modified client server configuration form in order to replace string inputs when needed
Fixed multiple bad paths in agent
Replace node-fetch due to ESM being incompatible. Link problem
Fixed user password not being hashed
Remove unused files


Publish v1.1.0 in Docker Hub

[x] Migrate to workspaces and yarn4
[x] Public v1.1.0 in Docker Hub

#41


Running demo.py in colab results in

Hi!
Thanks a lot for the model.
I try to run AVSR model in colab using demo.py. I'm using asr_trlrwlrs2lrs3vox2avsp_base.pth and I've specified the modality as 'audiovisual'. I'm getting this error:
Error executing job with overrides: ['data.modality=[audiovisual]', 'pretrained_model_path=[/content/asr_trlrwlrs2lrs3vox2avsp_base.pth]', 'file_path=[/content/de0fe3b3380fcc9575a8193b43226e51.mp4]']
Traceback (most recent call last):
  File "/content/auto_avsr/demo.py", line 77, in main
    pipeline = InferencePipeline(cfg)
  File "/content/auto_avsr/demo.py", line 30, in __init__
    self.modelmodule = ModelModule(cfg)
  File "/content/auto_avsr/lightning.py", line 29, in __init__
    self.model = E2E(len(self.token_list), self.backbone_args)
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1614, in __getattr__
    raise AttributeError("'{}' object has no attribute '{}'".format(
AttributeError: 'ModelModule' object has no attribute 'backbone_args'

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.

I tried also specifying ['audio', 'video'] but that doesn't seem right.

Hi @nastia-lado, can you please share the colab code with me so I can reproduce the error you have?

Here is the link to colab:
https://colab.research.google.com/drive/1SScL2-8IwnGtjqNnwmr3jSDqWc-Hx4-t?usp=sharing
But I didn't change anything in the lines that you recommend for demo. I just included ! to run it from colab.

Hi @nastia-lado, thank you for sharing. I can reproduce the issue. The issue can be fixed by replace data.modality=['audio'] to data.modality='audio'. Please let me know if there are any issues.

Thanks a lot!
I read that there is a plan to release audiovisual models, and I saw the option to select it in the code. But as far as I understood the model is still not available, right?

Thanks a lot!

hello @mpc001 , a small typo, in https://github.com/mpc001/auto_avsr/blob/main/demo.py#L30, you may want to change visual to video. Thanks!


Add firmware info from Netgear DM200 version <IP_ADDRESS>

Beside the ADSL Annex B firmware these are the most recent versions so far.

thanks!


Product management

Under warehouses, when adding a new warehouse, I noticed that there were no address fields to the warehouse. I believe it would be more useful to have that kind of information when creating a new warehouse instance.

The Description field serves the purpose of adding in any additional information re the warehouse


fresh 042 for BL updater

It's been a very long time since the last update,, so I want to do a little bit of manual testing before shipping new bits, especially in light of things like 99335f90c1d01f6305712a2bd5a6ffa05b6708d8


observable() signature

Hi, am struggling with your example project: mobservable-react-typescript
Typescript is complaining about the signature of this part of the example:
"Invalid arguments, expected 2..3":
var timerState = observable({
  secondsPassed: 0
});

your core.d.ts file declares the observable declaration thus:
export declare function observable(target: Object, key: string, baseDescriptor?: PropertyDescriptor): any;
The api makes no mention of additional parameters:
http://mweststrate.github.io/mobservable/refguide/observable.html
Dave

Hi David, observable is both a decorator and a function. As function it always has only one argument, but as decorator it has three params. Not that you need to specify those, it's just the compiler signature of any decorator. So you can use it like
var state =  observable({ a: b}) or like class X { @observable a = b }`. See also http://mweststrate.github.io/mobservable/best/syntax.html

problem is that Webstorm IDE's typechecking complains about the missing parameter, so I've been using it like this:
var timerState = observable({
  secondsPassed: 0
}, null);

I'm surprised though, that a library written in Typescript, with t.ds files autogenerated, should have this issue.
Dave

Hmm, is the experimentDecorators compiler option enabled? This can be passed as flag to tsc or defined in the tsconfig.json file (recommended)


phosphor buttons: Enable Delayed/Fast Power Off

The current Power Button behavior is to power On or Off host with a
short press. The power Off behaviour on FSP-based platforms is
different, and is follows:
Initial 4 seconds: do nothing
Delayed Power Off Initiated: With this, 10 seconds countdown begins.
If Button is released during this interval and not pressed again,
normal shutdown - equivalent to 'obmcutil poweroff' - starts and
the host goes to Off state. If the Button is released and pressed
again during this interval OR button is held down beyond this interval,
Fast Power Off is initiated with 10 seconds countdown, and the host is
shutdown - equivalent of 'obmcutil chassisoff'.
This commit changes the behavior on p10bmc platforms similar to
FSP-based platforms.
The following tests were performed using simulator signals and
power button on rainier system:

Power On host (push/release button)
Verified: host in 'Running' state
Power Off (Release Button within 4s)
Verified: No change
Power Off (Release Button somewhere between 5-9s)
Verified: host in 'Off' state
Power Off (Release Button after 6s, and press/release again)
Verified: host in 'Off' state
Power Off (Release Button after 6s, press and hold it down 15s)
Verified: host in 'Off' state
Power Off (Release after 30s)
Verified: host in 'Off' state

Signed-off-by: Shantappa Teekappanavar<EMAIL_ADDRESS>Change-Id: Ie52d1fd598971776c085e7ba9ce9e5264bd9d508

Looks pretty good to me!
Any need for any more field traces?
I'd like to get at least one other reviewer before approving.

Removed some of the DEBUG traces, but the rest I would like to keep just in case if we end-up debugging an issue in the future - but can be deleted once we have the SRC codes directed to Op-panel.


InMemory context is empty in TestServer after upgrade to EF Core 2

I'm writing my integration tests in such way:
[Test]
public async Task Test() {
var options = new DbContextOptionsBuilder()
            .UseInMemoryDatabase(nameof(MyContext))
            .Options;
using (var db = new MyContext(options))
{
   db.SeedSingleUserLogin();
   db.SaveChanges();
}

var response = await _client.GetAsync("/api/xxx", );

// assert
}

Base class for tests contains:
var builder = new WebHostBuilder()
            .UseContentRoot(contentRoot)
            .ConfigureServices(OverrideServices)
            .UseEnvironment("Development")
            .UseStartup(typeof(WebApp.Tests.Startup))
            ;

        _server = new TestServer(builder);

        _client = _server.CreateClient();

WebApp.Tests.Startup:
services.AddDbContext<MyContext>(x => x.UseInMemoryDatabase(nameof(MyContext))
                .ConfigureWarnings(z => z.Ignore(InMemoryEventId.TransactionIgnoredWarning))
                .EnableSensitiveDataLogging());

In controller there should be same DbContext because I use same string (nameof(MyContext)), but all its DbSets are empty.
EF Core 2.0.0 / VS 15.3.0

@sm-g A few questions to help us understand what might be going on:

Are you creating instances of MyContext with new in all places that it is use?
Do you call UseInternalServiceProvider anywhere?
Do you have the same configuration for your context options in some places? For example, it looks like you are configuring warnings and using sensitive data logging in one place, but not the other. Do things start to work if you make sure the ConfigureWarnings and EnableSensitiveDataLogging are called consistently in both places?

Are you creating instances of MyContext with new in all places that it is use?
only to seed initial state at beginning of test, other code receive it via DI

Do you call UseInternalServiceProvider anywhere?
no

Do things start to work if you make sure the ConfigureWarnings and EnableSensitiveDataLogging are called consistently in both places?
I set same options, but nothing changed.

@sm-g I thought it might be #9613, but given it still happens when both contexts have the same options it can't be that. I have been unable to reproduce this so far. Would it be possible to put together a full code listing or project that reproduces what you are seeing?

@ajcvickers https://github.com/sm-g/EFCoreInMemorySample

@ajcvickers Hello
I'm experiencing the same issue with my scenario after upgrade only to .NET Core 2
Here is my project:
https://github.com/msmolka/ZNetCS.AspNetCore.Logging.EntityFrameworkCore

Looks like this is the same underlying cause as #9613. In this case, it is AddDbContext  that sets an option (ApplicationServiceProvider) that later causes two service providers to be created.
Closing as a duplicate of #9613, since that details the root cause. I will look into workarounds/options for fixing this tomorrow.

Hi @sm-g, @msmolka. We are gathering information on the use of EF Core pre-release builds. You reported this issue shortly after the release of 2.0.0 RTM. It would be really helpful if you could let us know:

Did you consider testing your code against the pre-release builds?
Was there anything blocking you from using pre-release builds?
What do you think could make it easier for you to use pre-release builds in the future?

Thanks in advance for any feedback. Hopefully this will help us to increase the value of pre-release builds going forward.

@ajcvickers l'm currently AFK. So will test after available again in 2 weeks

@ajcvickers I finally made some tests, with latest provider and memory root. And it looks working


Separate publication date and online date

The current conversion of dates simply adds the elements fields publication-date and online-publication-date into the vivo:dateTimeValue field.  This isn't great because citeproc knows the difference between these dates.  However, bibo is deficient in this category, so we'll just add the citationstyles (cite:issued and cite:available) as new parts of citation.
Two examples are works 1434606 and 1442407.

Because of the update to cdl-elements, we can do a very quick test using the two publications above.  I'm using the standard rp deployment, w version v.1.7.0, but I'm using our test branch harvest, and ephemeral ports: ie
diff --git a/docker-compose.yaml b/docker-compose.yaml
index b755e85..574b5b2 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -16,10 +16,11 @@ services:
     volumes:
       - fuseki-data:/fuseki
     ports: # still exposed for admin access
-      - ${FUSEKI_HOST_PORT:-8081}:3030
+      - 3030

   harvest:
-    image: gcr.io/ucdlib-pubreg/rp-ucd-harvest:v1.7.0
+    image: local-dev/rp-ucd-harvest:multi-dates
+#    image: gcr.io/ucdlib-pubreg/rp-ucd-harvest:v1.7.0
     env_file:
       - .env
     volumes:
@@ -76,7 +77,7 @@ services:
     env_file:
       - .env
     ports:
-      - ${HOST_PORT:-8080}:3000
+      - 3000
     restart: on-failure

   auth:
@@ -103,8 +104,8 @@ services:
     image: gcr.io/ucdlib-pubreg/rp-ucd-es-indexer:v1.7.0
     env_file:
       - .env
-    ports:
-      - ${INDEXER_HOST_PORT:-8082}:3000
+#    ports:
+#      - ${INDEXER_HOST_PORT:-8082}:3000
     restart: on-failure

   status:
@@ -117,8 +118,8 @@ services:
     image: gcr.io/ucdlib-pubreg/rp-ucd-es-models:v1.7.0
     env_file:
       - .env
-    ports:
-      - ${MODELS_HOST_PORT:-8084}:3000
+#    ports:
+#      - ${MODELS_HOST_PORT:-8084}:3000
     restart: on-failure

 volumes:

Then, we can create our database for testing:
tmp=$(dc exec harvest harvest db new)
fport=$(dc ps --format=json fuseki | jq '.[].Publishers[0].PublishedPort')

and add some publications
cdl-elements --data=http://locahost:${fport}/${tmp}/data publications 1434606 1442407

Then we can run our publicaton translation

In my iteration of converting data from vivo to citationstyles, I made this separation, in this publication.rq query


add Probot auto-merge [wip]

What does this PR do?
experimental config for adding auto merging, pls see description - https://github.com/bobvanderlinden/probot-auto-merge
Alternatives:

https://github.com/palantir/bulldozer
https://github.com/marketplace/actions/merge-pull-requests
https://github.com/mergeability/mergeable

Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?
Make sure you had fun coding 🙃

wait a bit and shall we use github native PR auto-merge?
https://github.blog/2020-12-08-new-from-universe-2020-dark-mode-github-sponsors-for-companies-and-more/#pull-request-auto-merge

seems that the requiredChecks is missing https://github.com/bobvanderlinden/probot-auto-merge/issues/312#issuecomment-745311656

wait a bit and shall we use github native PR auto-merge?
https://github.blog/2020-12-08-new-from-universe-2020-dark-mode-github-sponsors-for-companies-and-more/#pull-request-auto-merge

can you pls check for some more details about the configuration and if we van set it in an extra file (outside GitHub UI)

wait a bit and shall we use github native PR auto-merge?
https://github.blog/2020-12-08-new-from-universe-2020-dark-mode-github-sponsors-for-companies-and-more/#pull-request-auto-merge

can you pls check for some more details about the configuration and if we van set it in an extra file (outside GitHub UI)

as far as I found out, it can only be set via github UI

let's try native GH auto-merge and eventually resume this one...


Initial Login developement. Can login in and out with Google Account.

Features:

Implements Login using oAUth Sign-in / Log-in Component for React (react-google-login).

Note
The login feature will not work on deployed GCP project unless the OAuth 2.0 Client ID is the same as the project.
Example:

To deploy properly on sopa-capstone-step-2020, you need to provide its Client ID, which is:

962122785123-r4ps71sg5eobh9riec89s9kas6dpvraj.apps.googleusercontent.com

If you deploy on mauroguerrero-step2020, using the same Client ID as above, the LOGIN WILL NOT WORK.

When testing the logging feature, I create my own OAuth 2.0 Client ID.


feat(Probability/Distributions): add result on convolution of Poisson PMFs

Add result that the convolution of Poisson PMFs is itself a Poisson PMF. This result is used in the proof that the sum of independent Poisson random variables also follows a Poisson distribution.

@blfang I'm very sorry, I forgot all about this review request and most likely don't have time for it in the next few weeks. If you intend to finish it or need some pointers, perhaps you can bring it back under attention on Zulip?

@blfang Are you planning to continue working on this PR? If so, please start a discussion on Zulip about how to prove the sorries in your PR. If not, please feel free to close it, or label it with please-adopt.


Lecture 6: Locally consistent marginals, factor model figure 3

Hey,
i struggle to correctly read the probabilities over certain configurations in the factor graph in the lecture 6:

It says that

However, I thought that if one considers P(s_1, s_2, s_3) as P(0, s_2, 1) the probability is given in b_31(0, 1) = 0.49 which is not 0.01. What do I misapprehend?
Thank you very much
Leon

Thanks for spotting this! There was a typo in the notes, I just uploaded a corrected version.
In the case of b31(s3,s1), we should have taken b31(0,0) and b31(1,1), so that we get the last 2 remaining configuration P(0,0,0) and P(1,1,1), as all the other 6 configurations where already estimated using b12 and b23. Hence, we the now corrected notes contain P(0,0,0), P(0,1,0) (i.e. s1=s3=0, and s2 varies in {0,1})  and P(1,0,1), P(1,1,1) (i.e. again, s2 varies while s1=s3=1).
I hope this clarifies

Ah, I see - yes this clarifies!
Thank you


TimeDimensionDisplay DST day conversion fix

Checklist

[x] Manual verification
[ ] Unit test coverage
[ ] E2E test coverage
[x] Needs manual QA?

Summary
Issue addressed:

https://github.com/rilldata/rill/issues/3560#issuecomment-1881384653
Details:

Steps to Verify

Open 311 Operational Metrics dashboard.
Set first_day_of_week: 7
In Chrome Developer Tools -> Sensors modify Location to America/New_York Timezone ID.
Drill into Median Time to Resolve Ticket (Hours) from main dashboard view
Adjust date range to Oct 29 - Nov 30 and make sure that metric trends is set to week
Check that the column header in the TDD shows Nov 5 (Sun) as first day of week.
Select time subrange ending with Nov 5 by dragging the mouse over the chart.
Check the subrange control shows Nov 5.

The issue is more complex than I expected @djbarnwal is going to take a look

@djbarnwal I wonder if there're any updates?

Closing as stale. We can reopen if there are further developments.


updating FATA string comparison to convert the error we get back from scorecard test

Fixes: #355
operator-sdk does not treat context deadline errors the same as other errors, ie they do not call log.Fatal() for them they just return fmt.Errorf("error running tests %w", err) see code here

Below are preflight.log entries from testing this by manually setting --waittime 5s
12-15T12:09:06-07:00" level=error msg="stdout: "
time="2021-12-15T12:09:07-07:00" level=error msg="stderr: time=\"2021-12-15T12:08:56-07:00\" level=debug msg=\"Debug logging is set\"\nError: error running tests context deadline exceeded\nUsage:\n  operator-sdk scorecard [flags]\n\nFlags:\n  -c, --config string            path to scorecard config file\n  -h, --help                     help for scorecard\n      --kubeconfig string        kubeconfig path\n  -L, --list                     Option to enable listing which tests are run\n  -n, --namespace string         namespace to run the test images in\n  -o, --output string            Output format for results. Valid values: text, json, xunit (default \"text\")\n  -l, --selector string          label selector to determine which tests are run\n  -s, --service-account string   Service account to use for tests (default \"default\")\n  -x, --skip-cleanup             Disable resource cleanup after tests are run\n  -b, --storage-image string     Storage image to be used by the Scorecard pod (default \"docker.io/library/busybox@sha256:c71cb4f7e8ececaffb34037c2637dc86820e4185100e18b4d02d613a9bd772af\")\n  -t, --test-output string       Test output directory. (default \"test-output\")\n  -u, --untar-image string       Untar image to be used by the Scorecard pod (default \"registry.access.redhat.com/ubi8@sha256:910f6bc0b5ae9b555eb91b88d28d568099b060088616eba2867b07ab6ea457c7\")\n  -w, --wait-time duration       seconds to wait for tests to complete. Example: 35s (default 30s)\n\nGlobal Flags:\n      --plugins strings   plugin keys to be used for this subcommand execution\n      --verbose           Enable verbose logging\n\ntime=\"2021-12-15T12:09:01-07:00\" level=fatal msg=\"error running tests context deadline exceeded\"\n"
time="2021-12-15T12:09:10-07:00" level=error msg="stderr: operator-sdk scorecard failed to run properly. Please review the /Users/acornett/go/src/github.com/acornett21/openshift-preflight/artifacts/operator_bundle_scorecard_OlmSuiteCheck.json file for more information. "

Signed-off-by: Adam D. Cornett<EMAIL_ADDRESS>

@komish Yeah this is really confusing. I had to look at the logs that were in the issue and the SDK code to see what is what. For your points:

It does catch the error because the entire stderr stream has fatal in the message, even though the error isn't log.Fatal() (will past entire log below)
The log file for this check does get populated (which is what DCI requested). I'm not sure we can cleanup our logs until OperatorSDK implements our ask for exit code 1 vs exit code 0, but might be missing cases where we could do a better job.
I thought about opening a bug, but like the issue we already raised, would they implement it? and how should it be raised? I'm unsure. I think if the implemented 1 vs 0 like above, this wouldn't even be an issue and we wouldn't have to look/poke around in stderr/stout

Logs that get written to operator_bundle_scorecard_BasicSpecCheck.json
time="2021-12-17T13:54:30-07:00" level=debug msg="Debug logging is set"
Error: error running tests error creating ConfigMap Unauthorized
Usage:
  operator-sdk scorecard [flags]

Flags:
  -c, --config string            path to scorecard config file
  -h, --help                     help for scorecard
      --kubeconfig string        kubeconfig path
  -L, --list                     Option to enable listing which tests are run
  -n, --namespace string         namespace to run the test images in
  -o, --output string            Output format for results. Valid values: text, json, xunit (default "text")
  -l, --selector string          label selector to determine which tests are run
  -s, --service-account string   Service account to use for tests (default "default")
  -x, --skip-cleanup             Disable resource cleanup after tests are run
  -b, --storage-image string     Storage image to be used by the Scorecard pod (default "docker.io/library/busybox@sha256:c71cb4f7e8ececaffb34037c2637dc86820e4185100e18b4d02d613a9bd772af")
  -t, --test-output string       Test output directory. (default "test-output")
  -u, --untar-image string       Untar image to be used by the Scorecard pod (default "registry.access.redhat.com/ubi8@sha256:910f6bc0b5ae9b555eb91b88d28d568099b060088616eba2867b07ab6ea457c7")
  -w, --wait-time duration       seconds to wait for tests to complete. Example: 35s (default 30s)

Global Flags:
      --plugins strings   plugin keys to be used for this subcommand execution
      --verbose           Enable verbose logging

time="2021-12-17T13:54:30-07:00" level=fatal msg="error running tests error creating ConfigMap Unauthorized"

these are the same logs that would get written by OperatorSDK that DCI mentioned in the issue.

@komish FYI: I put some code links from the SDK in the issue when I started looking at this.

Understood. I think there are a couple of challenges here, then.

We probably don't want to write non-JSON to the operator_bundle_scorecard_BasicSpecCheck.json file.

I'm uncertain if the log line time="2021-12-17T13:54:30-07:00" level=fatal msg="error running tests error creating ConfigMap Unauthorized" is coming from OperatorSDK, or coming from preflight itself. The only reason I mention this is because the code you linked doesn't seem to return Fatal, at least not in the code you linked. To that end, if we (preflight) are emitting that error, we don't want to fail a test based on our own error handling. This probably just needs some more investigation.

Overall, it just sounds like we're crossing some error handling streams here and it's causing some confusion. To point #2 - I do still think that we might benefit from being more clear, such that users of preflight would know to look at preflight.log in the event that the check errors (instead of fails because it doesn't meet our failure criteria).
I don't think we have to solve all of those problems here, but I do think at least the first two bullets would need to be addressed to resolve this issue.

I don't think this is how we want to handle this. The "FATA" (which is just abbreviated) is a very specific exit when log.Fatal() is used. I don't think we want to mix up this particular error case with something else. If we have another way of detecting whatever error you are trying to detect here, I would rather see it that way.

@komish I pasted the wrong error from testing another operator. I fixed the above for this scenario/code fix.
@bcrochet I felt you might say that, this is another option that works ie adding an or condition
stderr.Len() != 0 && (strings.Contains(stderr.String(), "FATA") || strings.Contains(stderr.String(), "error running tests"))
``

if we want this in a separate block `if` block with a separate comment, that's fine too. We could also jump on a call and we can debug in real time and get either of your thoughts on this.


Missing versions and no XE on https://container-registry.oracle.com (Oracle Database)

Hi,
For Dev, I am using the containers for the Enterprise and Standard editions of Oracle Database found on your container registry: https://container-registry.oracle.com
There are:
container-registry.oracle.com/database/enterprise:<IP_ADDRESS>
container-registry.oracle.com/database/standard:<IP_ADDRESS>
container-registry.oracle.com/database/instantclient:<IP_ADDRESS>
Where is the Express Edition (XE)?  Can you guys upload it to the registry please?
Also, it would be nice to fill in all versions, that way we can use the right container in dev to match the version of Oracle Database that we run in production. For example, please also create tags for EE and SE 12.2.01, and Instant Client <IP_ADDRESS>.
thanks!

The Database team will not be publishing the XE image, nor are they planning to release older versions of products. We will only be publishing newer versions moving forward.

Why no XE?  I'm just curious... It is a lesss heavy on the cpu/memory to run on older laptops than EE...

I'll let @gvenzl answer that one.

So still no images 2 years later? Will there be new images in the official registry?


Macros should have an operator type

 Issue by darkf
Thursday Aug 29, 2013 at 11:55 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/8853
This issue was labelled with: A-syntaxext, I-enhancement in the Rust repository

AFAIK there is currently no way to quote an operator such as + or /,  and this would be useful to reduce code duplication.
Something like:
macro_rules! foo(
    ($oper:op) => 10i $oper 20i
)

fn main() {
    printfln!("%d", foo!(+));
    printfln!("%d", foo!(*));
}

+1, this is really useful and would avoid a lot of boilerplate especially in operator overloading on simple structs

tt can be used for passing a single token.
macro_rules! foo {
    ($oper:tt) => (10 $oper 20)
}

fn main() {
    println!("{}", foo!(+));
    println!("{}", foo!(*));
}

It won't reject non-operators though.

tt can be used for passing a single token.

That doesn't work in all places an operator can exist, unfortunately, since eg expr can't be followed by tt:
macro_rules! example {
    ($lhs:expr $op:tt $rhs:expr) => {}
}

error: `$lhs:expr` is followed by `$op:tt`, which is not allowed for `expr` fragments
 --> src/main.rs:7:16
  |
7 |     ($lhs:expr $op:tt $rhs:expr) => {}
  |                ^^^^^^ not allowed after `expr` fragments
  |
  = note: allowed there are: `=>`, `,` or `;`

$:expr can't be followed by a +, let alone any binary operator.
error: `$lhs:expr` is followed by `+`, which is not allowed for `expr` fragments
 --> src/lib.rs:2:16
  |
2 |     ($lhs:expr + $rhs:expr) => {}
  |                ^ not allowed after `expr` fragments
  |
  = note: allowed there are: `=>`, `,` or `;`

oh wow, ok. Probably a separate rfc for that, in that case

there is no way to fix this because example!(1 + 2 + 3 + 4) is a thing.


Use addTag and removeTag to modify tags of existing tasks

Modifying tags doesn't work for existing tasks.
https://asana.com/developers/api-reference/tasks#tags

Fixed this in this commit: https://github.com/manishrjain/asanawarrior/commit/3b31d83f04b7f64dacff787597f5f4bf634f2b5a
However, this causes another issue, which is that Asana doesn't update the task modification time, and therefore Taskwarrior stays ahead of Asana in terms of modification. An overwrite to TW doesn't jump it's modification ts back. So, Asanawarrior continues to try to attempt an update to Asana, instead of acknowledging a sync.


Merge pull request #2 from rienafairefr/master

merged last changes

Coverage remained the same at 46.468% when pulling 6e0f1aaa794d55dbf41f163dff43b20faaeddaff on tovolkmar:master into 3d16e7a93cd7deea7ab5548338d1838762da5e91 on rienafairefr:master.

Coverage remained the same at 46.468% when pulling 6e0f1aaa794d55dbf41f163dff43b20faaeddaff on tovolkmar:master into 3d16e7a93cd7deea7ab5548338d1838762da5e91 on rienafairefr:master.


How to get JSON in hubconnection.on()?

I have tried below code:
connection.on(method: "EventData") { response in
self.handleMessage(response)
}
but getting error:
error: Invoking client hub method EventData failed due to: typeMismatch(Swift.String, Swift.DecodingError.Context(codingPath: [_JSONKey(stringValue: "Index 0", intValue: 0)], debugDescription: "Expected to decode String but found a dictionary instead.", underlyingError: nil))

Getting below error when I pass parameter in self.handleMessage() of type Dictionary<String, AnyObject> instead of String.
'Cannot convert value of type 'ArgumentExtractor' to expected argument type 'Dictionary<String, AnyObject>'

I got the solution by creating custom class with the properties(same name with response JSON keys) of response JSON, passed same class instance in callback to receive the same type.
connection.on(method: "EventData") { response in
self.handleResponse(response)
}
private func handleResponse(_ dataObject: EventDetails) {
// Do something with the object.
}
EventDetails is my custom class with properties same name as your response JSON keys.
class EventDetails: NSObject, Codable{
var eventId: Int?
var eventName: String?
var eventDescription: String?
var eventDate: String?
var eventPlace: String?
var eventOrganizedBy: String?
}
Hope it may help you.

This is the right way to go. You need to create a type on the client that matches what server sends so that Codable magic can do its work - just like you did.


update: instructions configuration template to imx8qm

as there is currently no other configuration, let's use imx8qm-config.nix instead of abstract template config.  It's easier for users to copy-paste to shell.

Generic comments for improving the documentation from user perspective.

Better instruct user with commands that user can just copy-paste to reproduce the image.
When we have more configs, I'd prefer table for the explicit build commands for supported configs instead of
flake.nix with different targets - like nix build .#imx8qm would be be preferred development. The dependency repositories can be included inside the flake.nix and make the build reproducible. And more simple from the user perspective.
FYI @jenninikko @remimimimimi

@vilvo please check my latest push to the PR#3
Particularly this: https://github.com/tiiuae/build-configurations/pull/3/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R22

I agree that the build instructions should be possible to copy-paste from the instructions to the command line. If there are more than one configuration available, explanatory heading or text before each complete copy-pasteable command can be added.

@vilvo please check my latest push to the PR#3 Particularly this: https://github.com/tiiuae/build-configurations/pull/3/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R22

https://github.com/tiiuae/build-configurations/pull/3/files#r1046710175

@unbel13ver @tervis-unikie ping for review


Block requests do not exceed MAX_REQUEST_BLOCKS.

What was wrong?
Block requests were not being made to recently connected peers on Altona, since the number of blocks needed to sync exceeded the maximum amount blocks that can be requested.
How was it fixed?
The chain is synced by making multiple consecutive requests of size <= MAX_REQUEST_BLOCKS.
Note: Under abnormal network condition or after some rounds of BeaconBlocksByRange requests, the client might need to send Status request again to learn if the peer has a higher head. Implementers are free to implement such behavior in their own way.
^ the issue of re-exchanging statuses after having finally synced to the peers head is not resolved in this PR. It may be worth revisiting later, once we're at a point where we can sync blocks fast enough to catch the initial head.
To-Do

[x] Clean up commit history

[ ] Add entry to the release notes

Cute Animal Picture

^ the issue of re-exchanging statuses after having finally synced to the peers head is not resolved in this PR. It may be worth revisiting later, once we're at a point where we can sync blocks fast enough to catch the initial head.

yeah in my mind clients should just regularly check some (even all?) of their peers for their latest head to have as wide a view of the network state as possible. we could imagine the final step to an initial sync is to "double-check" that the peer reports their head as ours -- want to move this to an issue so we can track it?

Added :+1:


[BUTTON IDEA]: Pinterest Login/Share Button

1. Name of button:  Login With Pinterest/ Share To Pinterest
2. Description:  A button for the Pinterest community with #E60023 as background-color
3. Button Type (Animated, Special, etc...): Social Button
4. Will you work on it?: Yes

Hi, thank you for another idea! I don't think there's a necessity login button for Pinterest, but we can add a share button. Usually, for Pinterest, instead it would be a "Save" button or a button with the pin icon.
I'll assign you this issue.

Ok. I will start working on it


validation_split-Parameter in model.fit() with GPU-accelerated LSTMs leads to severe crashes due to enormous stacktrace

System information

Have I written custom code (as opposed to using a stock
example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g.,
Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if
the issue happens on mobile device: No
TensorFlow installed from (source or binary): Installed from Pypi (Python Packaging Index), Version 2.1.0
TensorFlow version (use command below): v2.1.0-rc2-17-ge5bf8de410 2.1.0
Python version: 3.7.6
Bazel version (if compiling from source): -
GCC/Compiler version (if compiling from source): -
CUDA/cuDNN version: nvcc -V: release 10.1, V10.1.105
GPU model and memory: GTX 1060, 6 GB

Describe the current behavior
I created the following model and I am using it in a jupyter notebook to learn some data:
model = Sequential()
model.add(LSTM(100, input_shape=input_shape, return_sequences=True))
model.add(LSTM(100, return_sequences=True))
model.add(LSTM(100))
model.add(Dense(number_of_classes, activation='softmax'))

model.compile(optimizer=Adam(lr=0.001),
              loss='categorical_crossentropy',
              metrics=['acc'])

history = model.fit(x=[MODEL_DATA['DATA_TRAIN_PADDED_NORMALIZED']],
                    y=[MODEL_DATA['DATA_LABELS_OHC']],
                    validation_split=0.2,
                    epochs=500,
                    verbose=1)

When I imported all layers from the keras-package, the code works successfully on the CPU. Yet I would like to use the GPU-accelerated LSTMs (formerly known as CuDNNLSTM, but they are merged in TF 2.1 into LSTM).
To train my model, I am using a jupyter notebook. Sadly, once I changed my imports from the old keras-packages to tensorflow.keras and thus to the GPU-accelerated LSTMs, I suffered from sudden major crashes. And by "major" I mean a crashing jupyter-server that crashes my Firefox as well. When using pycharm with the jupyter notebook plugin, pycharm crashes too.
So I wondered why I had those massive problems across different processes on my machines that occured when I executed tensorflow and my notebook.
As it turns out, I could trace the problem to the following line [0]. It appears that as part of raising the ValueError, x is returned in its constructor in the str.format()-call. Here, x is my complete training data set. This resulted in a dump of 262 MB of text into stderr as part of the stacktrace that then lead to the consequences (crashing jupyter server, crashing browser via websocket-connection to localhost). I found that out by piping the stream to a file, as the exception's message has a len() of 275168064 characters!
Next, I wondered if the bug is still present in the newest version of tensorflow. I could see in git that the corresponding lines of code do not exist anymore when installing tf-nightly (version: v1.12.1-27849-g9278bbfc24 2.2.0-dev20200323 ) as the whole file, training_v2.py, does not exist anymore. Subsequently, I re-ran my code with the current tf-nightly from PyPI. First, I got this error [1], as I did not provide a numpy array.
After changing my model.fit() to the following:
history = model.fit(x=np.array([MODEL_DATA['DATA_TRAIN_PADDED_NORMALIZED']]),
                    y=np.array([MODEL_DATA['DATA_LABELS_OHC']]),
                    validation_split=0.2,
                    epochs=500,
                    verbose=1)

... I ran into the following error [2]:
Traceback (most recent call last):
  File "C:\Users\Joo\AppData\Local\Programs\Python\Python37\lib\contextlib.py", line 130, in __exit__
    self.gen.throw(type, value, traceback)
  File "C:\[...]\venv\lib\site-packages\tensorflow\python\ops\variable_scope.py", line 2805, in variable_creator_scope
    yield
  File "C:\[...]\venv\lib\site-packages\tensorflow\python\keras\engine\training.py", line 854, in fit
    epoch_logs = copy.copy(logs)
UnboundLocalError: local variable 'logs' referenced before assignment

It appears, that logs does not exist here [2].
Not using validation_split as part of model.fit() solved all my problems for tf 2.1.0, but I had to find it out the hard way. 🙁  Moreover, I could not resolve the problem for tf-nightly at all, even when omitting the parameter as other exceptions popped up.
Thanks in advance for checking the code and improving tensorflow.
[0] https://github.com/tensorflow/tensorflow/blob/f270180a6caa8693f2b2888ac7e6b8e69c4feaa8/tensorflow/python/keras/engine/training_v2.py#L539
[1] https://github.com/tensorflow/tensorflow/blob/e7bbb424808eb7ebbeb959b993496adafd024609/tensorflow/python/keras/engine/data_adapter.py#L1386
[2] https://github.com/tensorflow/tensorflow/blob/c45d13f92b921dae044a5639f8b1bc560fe9b71c/tensorflow/python/keras/engine/training.py#L857
Describe the expected behavior
I would expect an exception that does not return over 260 MB of text as part of the stack trace. The important part of the stack trace (in the beginning of the message) is also not shown (i. e., that validation_split cannot be used), as the 260 MB of x overfill the non-infinite buffer of my IDE in a split second, thus omitting the whole stack trace with my training data.

@jliebers
please provide us with complete simple stand alone code for us to replicate the issue faced by you in our local, gist of code shared is

Hi @Saduf2019 ,
thank you for your quick response. 🙂 🚀
Please check out this gist: https://gist.github.com/jliebers/b9a285ac97607916a10cb091b860fa48
For the tf-nightly problem, please check the output from above. As described it justs ends in a local variable not being assigned without any large problems.
For the tensorflow==2.1.0 problem, that resulted in major crashes of jupyter and my browser, please check this gist: https://gist.github.com/jliebers/42a3d787aea2595219e48e2abea6c7cf
(Please note the empty output of the last cell. Apparently colab does not execute it at all, but it causes major crashes on my offline-setup with jupyter and firefox)
By moving my code into this example that can be reproduced I found some obvious flaws which on the other hand still should not cause such massive problems. I think the biggest problem is that I did not use numpy but sticked to the standard iterable data structures of python.
To be fair, in my real project I stick to numpy, but since my real notebook became huge I apparently altered some types by mistake in the middle of it, resulting in standard python data structures. (i.e., DATA_NORMALIZED being a list of lists of tuples and LABELS_OHC being a list of lists).

Thank you in advance for your consideration.

I guess this is training issue rather than a LSTM issue, the training logic has been updated recently. Adding @omalleyt12.

Hi @qlzh727 ,
thank you and thank you all for your consideration. 🙂 👍
I just would quickly like to clarify, that the main reason for me to open this issue is, that the raised Exception in tf-2.1.0 contains a string which includes the whole training x (262 MB of text data), thus leading to crashes and such. The tf-nightly issue is of course also a problem but from my perspective way less severe.
Thank you and thank you all for the good work!

Thanks  for the report. Will submit the fix very soon.

Should be fixed now. Btw, your code is not providing a correct input data to the model. The np.array([list]) will make the a numpy array with shape [1, ?, ?], and instead, you should do np.array(list).


chore: hello-4-1 to 0.0.3

chore: Promote hello-4-1 to version 0.0.3

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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

@mathieucasse: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

promotion-build
b2cf7b0143282a6ff7b8c1cd4eee8a407e4268ad
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Route history with ID

Currently I can't set an ID in the history, so I can't return to routes that require an ID. I'm thinking that each history item could be an object
{
  routeName: "user",
  id: 10
}

rather than just a routeName, then I could return to that route with the right ID and maintain state.

Hey,
I don't really have the time to implement this right now but feel free to send me a pull request with the improvement!

Sent one through, let me know what you think.


Improve confidence for Node.js stack?

my blog is running with ghost blog, and self hosted, but the nodejs stack is always 0% sure 😰, any improvements?

i have a same result

It's strange because Ghost should implied Nodejs
https://github.com/AliasIO/Wappalyzer/blob/master/src/apps.json#L3019


Fix typo for main script

A similar PR may already be submitted!
Please search among the Pull request before creating one.
Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
Summary

This PR fixes/implements the following bugs/features

[x] Fixes the build script for the main field in the wnfs package to match the module field.

I was getting the following error when trying to use the webnative package:
Error: Cannot find module '/Users/dvargas/developer/samepage.network/node_modules/wnfs/wasm_wnfs.js'. Please verify that the package.json has a valid "main" entry

Test plan (required)
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
The change is a straight-forward edit to the build script, but I could set up a standalone repo to test it if need be.
After Merge

[ ] Does this change invalidate any docs or tutorials? If so ensure the changes needed are either made or recorded

no

[ ] Does this change require a release to be made? Is so please create and deploy the release

I don't think so?

Thanks for fixing this!

Yes, thank you @dvargas92495!


Monitor items support Custem Sort

after add more than 50 items of Monitor, i think maybe it can support custem Sort will make thing more Accessible.
for now, the sort item use update time, last updat at the front, this make things like odd.

let me know did star a monitor item will help you? we plan to do it.


Contact address to use in Help pages

as contact address in help pages, use<EMAIL_ADDRESS>

done


Cop idea: check descriptions for accidental spaces

I'm actually a bit surprised that not only is this not already a rule, I can't find any mention of anything close to it in any issue or PR - so I could be missing something really big, but in case I'm not here goes nothing...
Over in eslint-plugin-jest we have a rule called valid-title which does checks against it/test and describe descriptions (jest doesn't have context) for things like blank titles (similar to RSpec/ExampleWithoutDescription), duplicate titles (similar to RSpec/RepeatedExampleGroupDescription), and prefixing titles with the test method name (similar to RSpec/ExampleWording)
However, it also checks for accidental spaces in titles, which there doesn't seem to be any cop for!
Specifically, the rule looks for leading and trailing whitespace, and provides an autofix to remove them when found.
I can't think of a situation where you'd want to have this space, and so think this could a good addition for rubocop-rspec; maybe RSpec/ExampleSpacing, or as an extension to the existing RSpec/ExampleWording?
I actually think it would be fair to check for double spaces in titles too, but I think there's slightly higher chance of valid titles having that? (but tbh my go-to example of something like it 'treats "  " as valid' would probably be better written as it 'treats multiple spaces as valid' anyway).
I'm happy to have a go at implementing this if people think it'd make a good cop :)

Do you mean something like?
it " has  excessive   spacing  " do

This should apply to example group, shared group and example wording, right? I don't think that "docstring" is a commonly-used name for it, but AFAIR it is how RSpec calls it internally [1, 2]. Maybe RSpec/ExcessiveDocstringSpacing? See https://github.com/rubocop/rubocop/issues/7077 for cop naming guidelines and practices.
If you're up for it - sure, a PR is welcome.


Chore/staging ACN to local

Proposed changes
changed staging ACN to local node. I only changed agents/registration_start_up/aea-config.yaml, not the other aea-config files. That is because these e2e tests do not use the ACN Docker image either. Meaning both that:

p2p_libp2p_client.is_abstract: true in aea-config.yaml and
models.params.args.share_tm_config_on_startup: false in all skill.yaml files.

relates to issue https://github.com/valory-xyz/open-autonomy/issues/1287
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

I observe this (and more of it) in e2e logs:
2022-09-16T01:37:40.0577317Z ============================ 34 deselected in 0.10s ============================
2022-09-16T01:37:40.0577506Z Could not collect tests for for safe_deployment_abci of type skill
2022-09-16T01:37:40.0577671Z Running tests for apy_estimation_abci of type skill
2022-09-16T01:37:40.0577822Z ============================= test session starts ==============================
2022-09-16T01:37:40.0578075Z platform linux -- Python 3.10.6, pytest-7.0.0, pluggy-1.0.0
2022-09-16T01:37:40.0578755Z cachedir: .tox/packages-py3.10-linux/.pytest_cache
2022-09-16T01:37:40.0579094Z Using --randomly-seed=3877257141
2022-09-16T01:37:40.0579685Z rootdir: /home/runner/work/open-autonomy/open-autonomy, configfile: pytest.ini
2022-09-16T01:37:40.0580024Z plugins: cov-3.0.0, rerunfailures-10.0, web3-5.25.0, randomly-3.11.0, asyncio-0.18.0
2022-09-16T01:37:40.0580143Z asyncio: mode=legacy
2022-09-16T01:37:40.0580378Z collected 252 items / 252 deselected


docs: describe design and structure of hole punching in iroh

@ramfox's notion doc is an excellent starting point: https://number-zero.notion.site/Iroh-Hole-Punching-b9a38cc228fb47328a73e71d10520418


Investigate why SMG is unable to receive Salesforce Platform Events

Investigation
Description
SMG reported that some of their flows are not receiving SF platform events. Other flows are successful at capturing PEs.
The main problem is that two of their flows stop receiving Salesforce platform events. There could be a few reasons:

There were no new events from Salesforce, which is not the case because after restarting the flow it will work.
There are some problems with their Salesforce instance, we are unable to investigate it since we don't have access.
Lost connection to the Salesforce. We deployed a new version which contains a fix but looks like it is not working.

RE-SF-User flow regularly produces Client is offline errors. Logs contain multiple Client is online messages instead of a single one.
[2023-09-26 16:19:04.423]: Subscription is still running, waiting for new messages
[2023-09-26 16:21:42.791]: Client is offline
[2023-09-26 16:21:42.791]: Lets call processTrigger one more time
[2023-09-26 16:21:42.791]: Starting Subscribe to platform events Trigger
[2023-09-26 16:21:42.802]: Client is offline
[2023-09-26 16:21:42.802]: Lets call processTrigger one more time
[2023-09-26 16:21:42.802]: Starting Subscribe to platform events Trigger
[2023-09-26 16:21:42.949]: Client is online
[2023-09-26 16:21:42.983]: Client is online
[2023-09-26 16:21:43.021]: Streaming client created and ready
[2023-09-26 16:21:43.021]: Subscribed to PushTopic successfully
[2023-09-26 16:21:43.053]: Streaming client created and ready
[2023-09-26 16:21:43.053]: Subscribed to PushTopic successfully
[2023-09-26 16:21:47.863]: Client is online
[2023-09-26 16:21:47.880]: Client is online

RE-SF-User
PEs of this flow are generated less frequently than other flows, in low numbers. F.e. if there are new hires in a week, there can be 10 platform events for those 10 new users. For another week, there can be no events.
RE-SF-Campaign_Member_RE
PEs of this flow are generated less frequently than other flows, in high numbers. F.e. once a week, 3000 PEs in the same minute.

Previous improvements: https://github.com/elasticio/salesforce-component-v2/issues/68.

Link to a .txt file with SMG Salesforce limits.
Link to the Intercom conversation.

Component Version
2.7.1
Workaround(s)
Use the Get Updated Objects Polling  trigger instead of Subscribe to platform events. Since they should also get when a Campaign Member Object is deleted - meaning that a Contact is removed from the Campaign. Get Updated Objects Polling  trigger can't be used in RE-SF-Campaign_Member_RE flow.

checked basic network activity for first steps for the following flows:

questionable 6491a7b326a06000129029e6 and 6491a6ec26a06000128ff18e
normal one 64c7d4e8f85e7600124ebb31

for the normal one:
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 <IP_ADDRESS>:39584       ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:53238       ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:42206       ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:35184       ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:35870       ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:39146       ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:39144       ec2-18-170-131-54:https ESTABLISHED

for the first questionable:
tcp        0      0 <IP_ADDRESS>:47228       ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:60232       ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:35878       ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:57272       ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:53040       ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:42054       ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:38528       ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:55294       ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:48928       ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:39858       ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:60442       ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:46408       ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:36660       ec2-13-41-16-236.:https ESTABLISHED

for the second questionable:
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 <IP_ADDRESS>:58264        ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:37036        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:57590        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:50510        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:59068        ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:56960        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:50604        ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:45548        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:51314        ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:47500        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:51286        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:50020        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:53948        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:57534        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:50018        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:39198        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:49624        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:53942        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:55130        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:50896        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:45810        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:50124        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:40298        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:45534        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:59602        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:47512        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:35110        ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:36450        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:45544        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:57474        ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:43188        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:53558        ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:39764        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:35236        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:59082        ec2-18-170-131-54:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:54450        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:45822        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:57528        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:36440        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:43172        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:59418        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:43204        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:49622        ec2-18-170-190-12:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:51576        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:40806        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:40280        ec2-13-41-16-236.:https ESTABLISHED
tcp        0      0 <IP_ADDRESS>:36442        ec2-18-170-190-12:https ESTABLISHED

the only pattern I see - working one definitely has less established connections
maybe, just maybe we have an issue with rate-limiting or stuck connections

Krombacher noticed the duplicate PE messages after the first error appeared in their flows with v2.7.1. They will wait and update their flows to the latest version when we fix this. I'll keep them posted.
Link to the Intercom conversation.

Many thanks to @if0s, @HannaTrotsenko ! We have positive feedback from SMG:
I deployed the new component version on all flows on October 9th evening.
On October 10th, 11:36, 1170 add messages integrated successfully.
On October 10th, 11:26, 4585 add messages integrated successfully.
On October 16th, 09:04, 4278 add messages integrated successfully.
We can see that the flow was sleeping for almost 6 days but it didn't die out.
So I deduce that the bugfix is successful.
I shared these findings internally and with the customer as well.
So once again, thanks for your tight follow-up and thanks to the product team!
I think we achieved an important fix for every party!

Let's wait for feedback from Krombacher to be sure that it works for them too.

Resolved

@MykytaDuniashev pls don't close such issues - I didn't add it into changelod btcause it closed.

https://github.com/elasticio/salesforce-component-v2/releases/tag/2.7.2

The ticket reopened since the confirmation that the issue has been fixed came too early, the colleague confirmed it is no longer working.

We still experience issues with the flows that are dependent on the Salesforce Platform Events. My former colleague Ardan is no longer working for us (valantic), therefore I can not access his support ticket history.
Problem description:
Basically, the issue is the same as last time. We are using the Salesforce Platform Event connector to subscribe to Platform events coming from Salesforce. If such an Elastic flow has not been triggered for a longer time (approximately a few days), the flow “dies”. So, when a new Platform Event is coming from Salesforce, the Elastic flow is not triggered anymore. This has led to data inconsistencies between Salesforce and Bloomreach.
You can find an example of such a flow here: https://app-smg.elastic.io/c/648056e5f8e19300120b43bb/w/648059af2ae0600012320ec9/designer/648068f9be39e400129c4e67/v/latest

@if0s Looks like our fix is not working

Fixed in #76


Adding horizontal text scroll

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
adding horizontal text scroll on the website landing page
Use Case
It improves the UX of the website
Benefits
It improves the UX of the website
Add ScreenShots
Uploading horizontaltextscroll.mp4…
Priority
High
Record

[X] I have read the Contributing Guidelines
[ ] I'm a GSSOC'24 contributor
[X] I'm a VSOC'24 contributor
[X] I have starred the repository

Hey @itsekta I would like to work under VSOC and not GSSOc can please relabel the issue

@KavyaBS123 U CAN START WORKING

Suree

@KavyaBS123  as VSOC time period is over , I am closing this issue


[Bug] Retention period message and output mismatch

Describe the bug

To Reproduce

tctl namespace desc

Name: default
...
RetentionInDays: 72h0m0s

The message RetentionInDays doesn't align with the output format
Expected behavior
Fix the message, possibly make format more readable

Screenshots/Terminal output

Versions

OS: [e.g. Mac, Windows, Linux]
Temporal Version [e.g. 1.7.0?]
Are you using Docker or Kubernetes or building Temporal from source?

Additional context

addressed in v1.17.0:
State                                                     Registered
WorkflowExecutionRetentionTtl           24h0m0s
ActiveClusterName                              active


Update for Harvest

Hello! Do u have Procurement for Harvest version?

Are you referring to some specific Harvest-related features that need to be added?  The image on the login page is for a previous league, but that's just for appearances and won't impact the functionality.
I know we could add item filters for seeds and the new items introduced (like the new uber lab keys?), but I'm not aware of any major new features.  Or is there something else I'm not aware of?

Are you referring to some specific Harvest-related features that need to be added? The image on the login page is for a previous league, but that's just for appearances and won't impact the functionality.
I know we could add item filters for seeds and the new items introduced (like the new uber lab keys?), but I'm not aware of any major new features. Or is there something else I'm not aware of?

No no,
I just ask about some new version. didn't know how to ask if I had a new version of the procurement for Harvest.
Do u can give me the download link? B'cuz my procurement is not work for me.

Ah, I see what you mean.  There hasn't be an official release in a while, but there have been Cloudflare changes which have caused a problem with Procurement.  I have been maintaining a patched version to fix this that is available in #1093, and there is another pull request that other users have said works that is available in #1114 .

Are you referring to some specific Harvest-related features that need to be added? The image on the login page is for a previous league, but that's just for appearances and won't impact the functionality.
I know we could add item filters for seeds and the new items introduced (like the new uber lab keys?), but I'm not aware of any major new features. Or is there something else I'm not aware of?

No no,
I just ask about some new version. didn't know how to ask if I had a new version of the procurement for Harvest.
Do u can give me the download link? B'cuz my procurement is not work for me.

Thank you!

I'm sorry. I'm not a coder. How do I download the files need to fixe the program?


[PowerToys Run] limit to existing windows, a la Window Walker

Summary of the new feature/enhancement
Currently PowerToys Run operates as a universal search. The original implementation (as Window Walker) appears to be an alt-tab system for those with many many many windows open.
Proposed technical implementation details (optional)
Can we have an option to limit searches to open windows/tabs? Or should I just install Window Walker?

hi @jonpratt12, we have a number of issues regarding changing the Window Walker integration

An option to let running programs be first in the results list - #3169
Explicitly start new program instance with modifier key - #3884
Rethink integration of window walker into launcher - #3357

closing this as a duplicate, feel free to open if the other issues don't cover your suggestions!


IPv6

'By default, a container will have an IP address assigned automatically out of the pool of available IP addresses: <IP_ADDRESS> - <IP_ADDRESS>. Once a container is recreated, it may receive different IP address. A container does not change an IP address if it is restarted.' I know it's docker's fault as well, but ew.

I think that would not be possible without the support from weavenet. And I believe they would not consider to add this feature because these are the IP addresses of the cluster's VPN maintained by weavenet. It has got enough big IP range for the largest deployments in the world :) Could you please elaborate more on the motivation for this feature?

I agree, I don't need this, the larger installations probably want something like k8s anyway.
Closing as wontfix until upstream does something.
Main reason being:

Waiting for the this ticket resolved: https://github.com/weaveworks/weave/issues/19


Generate annotation scripts for GHIDRA

It would be great if floss supported generating annotation scripts for Ghidra.

Done!
https://github.com/fireeye/flare-floss/pull/378

Thanks @pinksawtooth


How can I debug compilation?

This is less an issue but a request for advice. I try to change the way code for namespaces is emitted.
Currently the typescript code
namespace A{
	var x = 42;
}

is  emitted as
var A;
(function (A) {
    var x = 42;
})(A || (A = {}));

which I want to change to be emitted as
    var A_x = 42;

Obviously, all references to x also need to become A_x .
I walkted through emitter.ts and declarationEmitter.ts but without being able to stepping through the compilation with a debugger it is hard to fully understand the pieces. So my question:
How can I debug compilation ?
Hints on my namespace hack are also appreciated.

If you're on Windows with a program that can use the script debugging interface (e.g. Visual Studio), you can use cscript with with /X flag to signal that it should stop on the first statement.
If you want to make it faster, use the Chakra engine using something like the flag /E:{16d51579-a30b-4c8b-a276-0ff4dc41e755}.
If you don't have that privilege, you can use node-inspector and run the compiler with node --debug-brk build/local/tsc.js.
As a word of caution, if you're intending on sending this out as a PR, I don't think we're inclined to accept something like that (or at least, we'd need a proposal to consider first). If it's for your own personal purposes, I fully encourage you to learn about the compiler and experiment. I'd look into getGeneratedNameForIdentifier and emitIdentifier.

Thank you so much Daniel, this was very helpful.
No PR indended, pure private hack for some very specific reasons.


fix(sync-charts): wrong index in chart name building

When changing logic about protocol handling for registryUrl, forgot to test the impact on  the chart name.
This PR fixes this and allow to have a good name in Chart

Hello, have you a detail of your change ?

Yes sorry, I edited my PR description to give a little more context :see_no_evil:


Using a VPN Solution in a docker swarm encrypted overlay network

Hey @kylemanna,
maybe you have an idea. We want to vpn into a docker swarm overlay network and found your conteinered solution. Unfortunately docker swarm doesnt allow any --privileged mode and probably won't in near future (https://github.com/docker/docker/pull/26849#issuecomment-252704844).
Due to the encryption its also not possible to add a service in normal docker run mode to the overlay network (https://docs.docker.com/engine/userguide/networking/overlay-security-model/).
Is there any possibility to run the vpn service without priviliged capabilities?
thanks a lot

The server used to use --privileged flag, but with modern versions of docker with more granular control it works just fine with --cap-add=NET_ADMIN.  I don't think there is anyway around the NET_ADMIN capability as it's creating a userspace network interface and manipulating the network interface.

ah. damn. but thanks for the fast reply.

Same boat as Quork, it seems the guys from weave figured a hack to do this: https://github.com/weaveworks/scope-global-swarm-service

I am not 100% that the approach of a jump container is applicable to openvpn though

@tlvenn don think this will work. It only allows the container to execute docker commands in behalf of the host system but won allow access to the hosts devices.

Ya indeed it would not work sadly.

With attachable swarm networks, you might get a chance to run a docker outside swarm with all necessary flags but still being able to have one leg inside swarm: http://blog.alexellis.io/docker-stacks-attachable-networks/

after 2 years, still now way that it work?
im reading now 24hours through all possible openvpn clients that i found and try out to find a solution... i have a swarm, and i have somehow get it stack deployed that other containers can use the openvpn network i still couldn't find a way to solve this

@Shinoby1992 if you find please update this issue... I am in the same situation.
Thanks!

Yes also looking for something like this...

Has anyone ever achieved something like this with Docker Swarm? I'd like to have a VPN in my Swarm cluster to access private services, so as not to expose them via host bindings nor a reverse proxy.


Reason for closure of pull request :
I don't use Python now and many parts
of the code have changed since then, sorry.
/*
Newbie's forgotton codes from the previous year
Hello, nice to meet you Wiznet everyone!
Maybe changed only adafruit_wiznet5k.py
For details, refer my forked repository.
(About : Available transfer data more than 2KB on the webserver)
*/

Yesterday, I uploaded Circuit Python 7.0 to my picoboard and tested the latest library from this repository from 3 months ago by directly Ctrl+C V, but it was also not successful. Next, I was roll back to CPython 6.2 version, it works fine.  If nothing else happens, I will release the older version of the guide that will be posted on my video channel.

Ok, The basic Webserver now works well,
but there seems to be some compatibility issue with Python7 and file IO


Specify colors manually in a summaryplot for each class

Not sure if this is already present,But what does the color parameter in a summary_plot used for? Can it resolve my issue?

Yep the defaults are filled in like:
https://github.com/slundberg/shap/blob/0c608c5d38e1e2e32d757c7759eee217d0f24af4/shap/plots/summary.py#L56-L63
So you can pass your own color set using the color parameter.

Thanks for the quick response. I was actually wondering if we could manually set color for each class.
For example if i have 3 classes A,B,C i want A to be Red, B to be Blue and C to be Green  in my summary plot.
The reason is, I am generating two summaryplots on the same data trained using two different models.To compare them, it would be easier if i can have each class with same color in both the plots.

@Sriharika1395
Hi!
If you figured out how to fix the colors of the classes for each plot, please share how you managed to do that. I have the same issue.

Some solutions are described under this issue


wot-author stories

Get some stories going. Not hooked up. ~Looks like garbage on mobile~, but I would find it helpful for someone to look for structural issues in parallel with debugging mobile.

^ is this behavior and the "other" behavior part of a different ticket or this one?
TBD but they are not part of this PR.

Now with mobile support and a small radio-button change.

merging over golang test failure. Might regret this.


Add bastion sg to inbound rules for both efs volumes.

This will allow us to use the bastion to connect to the EFS volumes.
There have been a few times recently where we've needed to so this
removes the need to manually fiddle with the security groups.

I think that having a bastion to access EFS is a good idea, thanks.
There are a few security questions I think it would be good to think about and discuss with David: https://national-archives.atlassian.net/browse/TDR-1319 It's things like whether it should be a separate bastion (so we're not spinning up an instance that has access to everything every time) and whether it's possible to make a read-only connection using a separate mount point.

We're going to separate these permissions out into two roles which will be attached to the bastion separately depending on what we're using it for. Or we'll have two separate  bastions. Either way, the role changes will be different so this can be closed.


Audit diagnostic settings parameter info

Azure customers are finding the Audit diagnostic setting for selected resource types build in policy difficult to use holistically, as there isn't a well-defined way to populate the listOfResourceTypes parameter for all supported resourceTypes.
This change includes a bash script to help with this. Would be happy to do a PowerShell equivalent too if useful?

Do not merge. Closing PR.
#please-close

Do not merge. This content is generated from source code and can't be edited.

Hi David, thanks for the info.
Is there another way I can contribute this info to make the policies easier to use?


SSUI : Self service login page shows "The page you were looking for doesn't exist."

Version-Release number of selected component (if applicable):
master.20170104131727_8bda79e
How reproducible:
Steps to Reproduce:

Login http://IP/self_service
"The page you were looking for doesn't exist." is shown. See screenshot
===================================

Logs
[----] I, [2017-01-04T14:36:59.569459 #2882:f43094]  INFO -- : Started GET "/self_service" for <IP_ADDRESS> at 2017-01-04 14:36:59 -0500
[----] F, [2017-01-04T14:36:59.573885 #2882:f43094] FATAL -- :
[----] F, [2017-01-04T14:36:59.573994 #2882:f43094] FATAL -- : ActionController::RoutingError (No route matches [GET] "/self_service"):
[----] F, [2017-01-04T14:36:59.574061 #2882:f43094] FATAL -- :
[----] F, [2017-01-04T14:36:59.574113 #2882:f43094] FATAL -- : actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/debug_exceptions.rb:53:in call' [----] F, [2017-01-04T14:36:59.574163 #2882:f43094] FATAL -- : actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/show_exceptions.rb:31:in call'
[----] F, [2017-01-04T14:36:59.574251 #2882:f43094] FATAL -- : railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:36:in call_app' [----] F, [2017-01-04T14:36:59.574306 #2882:f43094] FATAL -- : railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:26:in call'
[----] F, [2017-01-04T14:36:59.574378 #2882:f43094] FATAL -- : request_store (1.3.1) lib/request_store/middleware.rb:9:in call' [----] F, [2017-01-04T14:36:59.574484 #2882:f43094] FATAL -- : actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/request_id.rb:24:in call'
[----] F, [2017-01-04T14:36:59.574554 #2882:f43094] FATAL -- : rack (2.0.1) lib/rack/method_override.rb:22:in call' [----] F, [2017-01-04T14:36:59.574624 #2882:f43094] FATAL -- : rack (2.0.1) lib/rack/runtime.rb:22:in call'
[----] F, [2017-01-04T14:36:59.574669 #2882:f43094] FATAL -- : activesupport (<IP_ADDRESS>) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in call' [----] F, [2017-01-04T14:36:59.574709 #2882:f43094] FATAL -- : actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/executor.rb:12:in call'
[----] F, [2017-01-04T14:36:59.574759 #2882:f43094] FATAL -- : rack (2.0.1) lib/rack/sendfile.rb:111:in call' [----] F, [2017-01-04T14:36:59.574799 #2882:f43094] FATAL -- : railties (<IP_ADDRESS>) lib/rails/engine.rb:522:in call'
[----] F, [2017-01-04T14:36:59.574835 #2882:f43094] FATAL -- : puma (3.3.0) lib/puma/configuration.rb:224:in call' [----] F, [2017-01-04T14:36:59.574884 #2882:f43094] FATAL -- : puma (3.3.0) lib/puma/server.rb:561:in handle_request'
[----] F, [2017-01-04T14:36:59.574926 #2882:f43094] FATAL -- : puma (3.3.0) lib/puma/server.rb:406:in process_client' [----] F, [2017-01-04T14:36:59.574964 #2882:f43094] FATAL -- : puma (3.3.0) lib/puma/server.rb:271:in block in run'
[----] F, [2017-01-04T14:36:59.575000 #2882:f43094] FATAL -- : puma (3.3.0) lib/puma/thread_pool.rb:111:in `block in spawn_thread'

That is not the correct URL.  It should be http://IP/ui/service

Also, this is not the correct location for SUI tickets.

https://IP/ui/service link also shows blank page

Can you please try without the https and use http

Opened a ticket on Pivotal board. closing this one


Linked List cheatsheet

Please merge this PR under hacktoberfest 2022

Please have a look @PrasadCoding and merge this under hactoberfest 2022

@TKirtan Please have a look and merge this PR


Stuck on "There's more to Discover" screen

Using "BingGPT-0.3.4-win32-x64" installer.
When I opened application today it only shows the set of screens with no option to close it (images 1-3).
Tried clicking on any links it didn't change anything.
Once I pressed "Share feedback" screen came back but stretched (see image 4). Closing application and opening didn't help.
Uninstalling didn't help, after I opened the installer it brought me back to same set of images 1-3.

Update: issue disappears when using a VPN. So most likely it's because previous IP is from a country where Bing Chat is not supported.

I have the same problem on macOS x64. I use ExpressVPN, proxy in every country show "There's more to Discover" screen. I can't use this app at all, it's crazy!

I also ran into this screen. Meanwhile, chat in Microsoft Edge browser works well.

The same problem occur today in my mac, also, I can visit new bing in edge through Clash, but the AI can't load in the software.

I have also been experiencing the same issue. Works in Edge browser but not in this application.

Stuck on this screen too. The application is stuck on these three screens with no way to close or exit it. Tried opening in Edge and it works fine.

Update to 0.35, the problem will be solved
Sent from my iPhone
------------------ Original ------------------
From: Emby @.>
Date: Mon, May 15, 2023 0:47 PM
To: dice2o/BingGPT @.>
Cc: GeekHank @.>, Comment @.>
Subject: Re: [dice2o/BingGPT] Stuck on "There's more to Discover" screen(Issue #197)
Stuck on this screen too. The application is stuck on these three screens with no way to close or exit it. Tried opening in Edge and it works fine.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Update to 0.35, the problem will be solved

Can confirm that after upgrading to v0.35, this problem is solved.

I'm on 0.3.7 - issue still there

I'm on 0.3.7 - issue still there Even US Vpn doesn't help Tried 0.3.5 - didn't work as well only Edge is working

I have the same issue and tried both the ways you mentioned and still nothing


Source all endpoint names from app.config closes #158

Fixes #158

@adamralph Iv'e rebased and pushed, hope this will be ok now.

Done


Cannot set parameter Motion Sensor Sensitivity for device NAS-PD07Z

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
NPM
Z-Wave JS UI version
9.17.0
ZwaveJS version
13.2.0
Describe the bug
When I try to change parameter 5 "Motion Sensor Sensitivity " of device NAS-PD07Z I get "Unable to write ... : Fail" for any value other than 0 or 1. (theorically until 15 is good)
To Reproduce
try to change the value other than 0 or 1 (theorically until 15 is good)
Expected behavior
the value is changed without error
Additional context
I suspect that I have a wrong config file, with a wrong parameter type.
My device is installed as device ID "0x0258 0x0010-0x0720" and I see there is another config file for the same device with a different ID "0x0258 0x0020-0x0720", perhaps I have the wrong config file ?
How can I change the device manufacturer ID in zwave-js-ui ?

It's entirely possible that the config file we have is wrong. Those Shenzhen Neo devices sometimes even ship with the wrong manual, so it doesn't get noticed until someone uses the paramters like you did.
Could you check whether the parameters mentioned in https://github.com/zwave-js/node-zwave-js/files/6758340/motion.5in1.manual.20200602.1.docx match your device? The manual is supposed to be for the 0x0020 variant, but maybe the parameters also fit for the 0x0010 one.

OK I made some tests, this is very odd.
I test field ID 5 named "Motion Sensor Sensitivity " in UI, but it interact exactly as the field "Binary Sensor Report Enable" in your documentation : value 0 OR 1, and device send actually binary report or not.
This would indicate that you are right the device is the 0x0020 variant.
BUT :
I also test the field ID 13 "Motion Clear Time" and it works as intended for the variant 0x0010. (i test 30 sec and 15 sec value and it actualy works)
At the end, I dont know, it seems a mix of 0x0010 and 0x0020 variant.
But the only parameter that interest me now is the "sensor sensitivity" and i cannot find it. (not 5 nor 6)
Perhaps another variant ?

Do you have a paper manual for that device by any chance?

This would be of course too easy and not fun =)
More seriously, no manual inside box.
Is it possible to change the variant ID manually ? Actually zwjsui detect it automatically as "0x0010" but it would be interesting to test it as "0x0020" variant. (I have 2 of these devices, both with same problem)

The solution would be to correct the config file for the 0x0010 variant, so you get offered the correct parameters for your device. Which is why I'm trying to figure out the correct parameters here.
I guess we can start by correcting parameter 5 to be Enable/Disable instead of the 0-15 range.


Update akka-actor, akka-slf4j, akka-stream to 2.6.18

Updates

com.typesafe.akka:akka-actor
com.typesafe.akka:akka-slf4j
com.typesafe.akka:akka-stream

from 2.6.17 to 2.6.18.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Done in #110


ddev crashes with SIGILL: illegal instruction PC=0x1063790 m=0 sigcode=1 on MacOS Catalina

Describe the bug
After setup the environment like explained in the manuals (1. Docker, 2. Homebrew, 3. DDEV), I tried to run ddev --version to see if it's working.
Could you please provide the output of

which ddev
brew link ddev

I would recommend brew uninstall ddev and then brew install ddev just for grins.

Could you please provide the output of

devMBP3:~ developer$ which ddev
/usr/local/bin/ddev

devMBP3:~ developer$ which link ddev
/bin/link
/usr/local/bin/ddev

I would recommend brew uninstall ddev and then brew install ddev just for grins.

Thanks for your fast response. I did reinstall ddev but the issue persists. During the reinstall I saw that it loads *sierra.bottle.tar.gz also my OS is Catalina, is this expected behavior?
devMBP3:~ developer$ brew uninstall ddev
Uninstalling /usr/local/Cellar/ddev/1.14.2... (5 files, 24MB)

devMBP3:~ developer$ brew install ddev
==> Installing ddev from drud/ddev
==> Downloading https://github.com/drud/ddev/releases/download/v1.14.2//ddev-1.14.2.sierra.bottle.tar.gz
Already downloaded: /Users/developer/Library/Caches/Homebrew/downloads/7b5223babced0f490e6af942d193a060eeabff3d65350134a016024eee285d03--ddev-1.14.2.sierra.bottle.tar.gz
==> Pouring ddev-1.14.2.sierra.bottle.tar.gz
==> Caveats
Make sure to do a `mkcert -install` if you haven't done it before, it may require your sudo password.

ddev requires docker and docker-compose.
Docker installation instructions at https://ddev.readthedocs.io/en/stable/users/docker_installation/

Bash completion has been installed to:
  /usr/local/etc/bash_completion.d
==> Summary
🍺  /usr/local/Cellar/ddev/1.14.2: 5 files, 24MB

devMBP3:~ developer$ ddev --version
SIGILL: illegal instruction
PC=0x1063790 m=0 sigcode=1
...

Ok... Updating to 10.15.5…!
Thanks

Just remembered this issue with "Cylance" from long ago, https://github.com/drud/ddev/issues/513

I updated to 10.15.5 and can't recreate the issue.
I have to confess I had no idea you could run Catalina on a 2010 machine.
Oh, as a matter of fact they say you can't... https://support.apple.com/kb/SP803?locale=en_US

the oldest supported hardware for an MBP on Catalina is mid-2012.

So what's up with that?

I have to confess I had no idea you could run Catalina on a 2010 machine.
A friend refurnished this Mac and used a patch tool to install it (http://dosdude1.com/catalina/).

Everything is working super smooth, Wifi, Cam, Audio, all hardware, also other software like Docker, Adobe etc. So I'm wondering why DDEV is not, as it is based on Docker I thought. But maybe you're right and this is the issue here... which would be really sad.

Yes, whats why I was wondering, Docker seems to run, at least the hello-world image... so strange :-(
devMBP3:~ developer$ docker --version
Docker version 19.03.8, build afacb8b
devMBP3:~ developer$ docker run hello-world

Hello from Docker!
This message shows that your installation appears to be working correctly.
[...]

If you want to be ambitious you can try to build this yourself. All it requires is golang (brew install golang).  Then https://github.com/drud/ddev/blob/master/docs/developers/building-contributing.md
It would be interesting to see.
It still looks more like a virus checker or something killing it. I did look at mac hardware history, and all macs switched to 64-bit in like 2007, I had been wondering if your computer was 32-bit.
It would be super interesting to see if an earlier OS would work better for you.  The ddev binary has to be signed and notarized. Those are new to Catalina, and that might be something different about other binaries you are looking at.
Just for interest sake, I put an unsigned, un-notarized binary at https://ln2.sync.com/dl/6bbab5c50/e6ph6r9f-miez8ug9-u5w4a6hh-u7ru6dgz
But I'm not sure Catalina will let you run it...

If you want to be ambitious you can try to build this yourself. All it requires is golang (brew install golang). Then https://github.com/drud/ddev/blob/master/docs/developers/building-contributing.md

Dude, I highly appreciate your help!
From this experience, I was expecting something similar, but now I'm super happy to see how easy it can be: after installing golang and run make, it compiles without a single line of warning/error/problem or whatever :-D And even more important:
devMBP3:darwin_amd64 developer$ ./ddev --version
ddev version v1.15-alpha3

It's working! I tried it also with a real project, all web and DB server images are downloaded, installed and started like expected! Super great, thanks a lot!
So, does this can help you in any form, or should we just let it documented here in case others run into the same issue? I am happy with this solution and don't mind to recompile it myself for the next stable release :)
Here is what I did to install it:

Copy the compiled artifact to /usr/local/MyVendor/ddev/1.15-alpha3/bin
Changed symlink of /usr/local/bin/ddev pointing to the self compiled artifact

Or do you recommend something else to do it better? Probably this manual change will break things during future interactings with brew!?
Another question: In the original installation folder exists a etc/bash_completion.d file. Do I need this, and if so, can I just copy the original one e.g. from ddev/1.14.2/etc/bash_completion.d to my own folder?

That's amazing. It probably means that you did somehow get a bad binary from homebrew, but that's hard to do, but maybe it happened.
What I would do for right now is brew unlink ddev and cp .gotmp/bin/darwin_amd64/ddev /usr/local/bin. Then you just have your binary in /usr/local/bin.
You can put your bash completions anywhere you want that bash completions work.
I notice that you were using the stable channel of homebrew before. At some point I'd appreciate it if you'd rm /usr/local/bin/ddev && brew tap drud/ddev-edge && brew install drud/ddev-edge/ddev just to see if you get a working ddev that way.

I notice that you were using the stable channel of homebrew before. At some point I'd appreciate it if you'd rm /usr/local/bin/ddev && brew tap drud/ddev-edge && brew install drud/ddev-edge/ddev just to see if you get a working ddev that way.

This seems to help too! Brew installed the same version (1.15-alpha3) from the edge channel and this works also like expected. Maybe there have been some code changes between 1.14 and 1.15 related to the above described issue?! Anyway, it looks like the problem is solved than, thanks again :)

Again, glad it's working. But not a code change. I know you'll keep me up to date with future results. I think something odd went on with homebrew; we should have captured the result.


Expose MutateShoppingItem

Proposed Changes
Expose another model required for integration
Related Issues
N/A

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.64%. Comparing base (0441873) to head (f903ec8).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #178   +/-   ##
=======================================
  Coverage   99.64%   99.64%
=======================================
  Files           4        4
  Lines         280      280
  Branches       29       29
=======================================
  Hits          279      279
  Misses          1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


feature negotiate while using virtio_mmio

Hello, and thank you for your course! I'm learning with the code in code/s008/virtio-mmio.c, specifically the virtio_mmio_set_guest_features function. Here's the relevant section of the code: code here,
void virtio_mmio_set_guest_features(u64 features)
{
    u32 f0 = features & 0xFFFFFFFF;
    u32 f1 = (features >> 32) & 0xFFFFFFFF;

    VTMO_REG(VIRTIO_MMIO_HOST_FEATURES_SEL) = 0;
    dsb();
    VTMO_REG(VIRTIO_MMIO_GUEST_FEATURES) = f0;

    VTMO_REG(VIRTIO_MMIO_HOST_FEATURES_SEL) = 1;
    dsb();
    VTMO_REG(VIRTIO_MMIO_GUEST_FEATURES) = f1;
}

I suspect there might be a need to use the VIRTIO_MMIO_GUEST_FEATURES_SEL register instead of VIRTIO_MMIO_HOST_FEATURES_SEL, but I haven't found any functional errors in s009. When I tried to read the VIRTIO_MMIO_GUEST_FEATURES after setting it, the value was 0. The spec doesn't seem to clarify whether VIRTIO_MMIO_GUEST_FEATURES is readable or not. Additionally, setting it to zero in virtio_mmio_set_guest_features didn't affect the rng-device's functionality. Could you provide any insights on how to verify whether the driver registers have been correctly set? Thank you!

我最近也在学习这个代码，我查看了virtio-v1.2-csd01.pdf规范文档，修改DeviceFeatures，确实需要修改DeviceFeaturesSel寄存器。

我尝试打印了代码修改features时寄存器存储的值的变化，确实没有发生改变。

后来我在规范中查到，无法从只写寄存器中读取数据，这应该就是读取始终为0的原因。

此外，在virtio_mmio_set_guest_features中将其设置为零不会影响 rng-device 的功能，应该是因为rng写入的驱动特性位都是在低32位，此时DeviceFeaturesSel因为未被修改，默认为零，恰好能够写入。

Thank you very much for your sincere answer!   @wusskk


[iOS] white space in iphone X

const { height, width } = Dimensions.get('window');
<YouTube
   ...
   style={{ alignSelf: 'stretch', height: height, width: width }}
</YouTube>

Trying to streatch the video to fit the screen size in iphone X. But its not working.

@bitshadow I am having this bug as well, have you found any solution?

@bitshadow I am having this bug as well, Did you find any solution?

https://github.com/up-inside/react-native-youtube-sdk
@rafaelsorto @bitshadow

@rafaelsorto can you give more context?


Improve incremental tasks documentation

There was some additional feedback on #8940.

@pledbrook Thank you for your review! I merged the changes.


Keep npm published versions up to date

I’d like to use the new https://github.com/Stranger6667/css-inline/issues/265 feature for dark mode email media query styles, but npm is on 0.11.2 while github releases is on 0.13.1

The package migrated to @css-inline/css-inline, probably I need to add some migration guide or visible note on that. or maybe update that old package with a note

Added a deprecation message, hopefully it could help to avoid confusion.

Perfect!  Thank you @Stranger6667


Adds missing pieces to documentation

Service specific credentials not specified in some places. Fixes some
other inconsistencies in docs.

This is ready for a new review.


Feature: Use MultiStage Docker Image

A multi stage docker image affords us the ability to compile prometheus
the same way regardless of host.  The alternative is cross compiling to
linux/amd64 prior to running make docker.
This PR closes #3109
@discordianfish

Nice, LGTM @sdurrheimer What do you think?

Need to really think about this, it seriously affect the build process (binary in the image not exactly the same as the one in the release page, etc.).

Changes to the build process should be proposed in https://github.com/prometheus/promu/


feature: allow URI to use shorthand syntax with additional options

(This is an alternative to PR #546 )
This allows to combine the shorthand syntax by using URI with additional arguments:
CPMAddPackage(URI<EMAIL_ADDRESS>OPTIONS "JSON_BUildTests OFF")

This is much shorter than the longer syntax way of writing:
CPMAddPackage (
  NAME nlohmann_json
  VERSION 3.9.1
  GITHUB_REPOSITORY nlohmann/json
  OPTIONS
    "JSON_BuildTests OFF"
)

Important difference to #546, it does not set EXCLUDE_FROM_ALL;YES;SYSTEM;YES;

Can you elaborate what the advantage is?

I think I found the answer in the other PR:

Harder to document. Currently we have two cases: 1. normal usage, 2. shorthand syntax. With URI we kind of have to split the 'normal usage' into two cases. I don't see how this can be documented in any understandable way. (Assuming we don't delete the 2. shorthand syntax)

I see your concern, though I feel it's quite easy to understand in the docs:

All packages added using the shorthand syntax will be added using the EXCLUDE_FROM_ALL and SYSTEM flag.
...
Additionally, the shorthand syntax can be combined with the other options from above[ using the URI argument]:

PR #546 basic idea was, take the "short hand" syntax and allow extended options.
This PR took the standard approach and added a URI which is a short from for repo, name and version.
That is why I didn't touch EXCLUDE_FROM_ALL and SYSTEM.
But from what I understand, you would prefer a URI which allows a short form of repo, name and version + also sets EXCLUDE_FROM_ALL and SYSTEM.
I will adjust this PR accordingly

This new version automatically sets EXCLUDE_FROM_ALL and SYSTEM. I made sure that this can be overridden by setting EXCLUDE_FROM_ALL OFF or SYSTEM OFF. (And added a unit/integration test for this case).
I added another note below the CPMAddPackage(....) description noting the behavior of URI.