Example CRUD using Codable and Alamofire

I need an example code of a CRUD using Codable and Alamofire. Because the support documentation has simples examples and I would like to know the best practices for this implementation.

Hey @gfvilela, we made an example of CRUD operations with Japx on our repository
with commonly used code.
Feel free to clone and check the rest of our repo :)

This should be resolved.
Closing for now.


Integrate K8up Helm chart into this repository

Summary
As developer
I want to maintain the K8up Helm chart in this repository
So that I don't have to maintain the deployment config with Kustomize and in an external Helm repo.
As K8up Admin
I want to install a K8up Helm chart version that redistributes the K8up CRDs
So that I don't have to select the K8up version that is included in the Chart separately
Context
This is about migrating the K8up Helm chart into this repository.
We should make a new major release to clearly communicate the switch to another repository.
These are basically the things to do:

Integrate the existing K8up Chart into this repository
Copy the GitHub automation from https://github.com/vshn/appcat-service-postgresql
Add labels as required in https://vshn.github.io/appcat-service-postgresql/appcat-service-postgresql/how-tos/create-releases.html
Release the chart as v3.0.0 with "upgrade" documentation
Deprecate the chart in appuio org (https://github.com/appuio/charts/tree/master/appuio/k8up) with redirection notice to this repo.
Get rid of the Kustomize setup, or more precise: Make it so that generated artifacts are able to be integrated into the chart (see https://github.com/vshn/appcat-service-postgresql/blob/8b9c15adeb1097c568eb172bec44c9e1b5f9a6ca/charts/provider-postgresql/Makefile as example)
Ensure the e2e tests work with the Helm chart after getting rid of Kustomize method.
Update installation docs in https://k8up.io/k8up/how-tos/installation.html (Remove the installation steps there and link to the chart README, Remove Kustomize option)

Out of Scope

Migrating existing Helm chart releases

Further links

Reason why we don't ship CRDs in the Helm chart
Idea to include K8up CRDs into GitHub release of Helm chart: https://github.com/appuio/charts/issues/419
K8up Helm chart

Acceptance Criteria

Given master branch in the K8up repository, when I browse the contents then there is a fully-documented Helm chart available that installs K8up operator (without CRDs) and the Kustomize setup is deleted.
Given master branch of the K8up repository, when I run make e2e-test then the operator is installed with the local chart instead of Kustomize.
Given master branch of the K8up repository, when I run make generate then the RBAC roles and rules are generated in the Helm templates directory and enriched with Helm labeling functions.
Given K8up repository, when I want to make breaking changes to the chart, then I don't need to bump K8up (operator) major version
Given K8up documentation, when I want to release K8up, then I can look up a documented release process.
Given I want to make changes to the Helm chart, when I create a PR, then a PR job ensures that the chart is following quality standards (for example documentation with helm-docs).
Release documentation is updated here: https://k8up.io/k8up/2.2/explanations/release.html

Implementation Ideas

when I push a vX.Y.Z Git tag, then K8up (operator) is released with changelog excluding changes to the K8up chart.
when I push a chart-X.Y.Z Git tag, then K8up chart is released with changelog containing only changes to the K8up chart and the release contains the CRDs corresponding to the K8up version.

Note: In https://github.com/vshn/appcat-service-postgresql/pull/39 (and some commits afterwards) we have already engineered the automation for this type of repo and releasing. I also ironed out some issues that came up with such a design.
I'm going to reword the acceptance criteria to match it.

this is actually done


fix(Tooltip): use trigger's ownerDocument to track pointermove

In Popup windows, the tooltip content wasn't closing after moving from the area, only after going back to the original window and moving the pointer there.
https://github.com/user-attachments/assets/45f94c06-1b27-469c-9b95-b21d7fd9075a

Hey @zernonia, is there a timeframe on the next release date? Or is that delayed until the v2 release?


Error in opening problems

Thanks for implementing this good plugin!
I'm using this under Ubuntu 18.04 and Neovim.
I was able to sign-in and see menus ad lists.
However, when I tried to open a problem, an error occurs saying
Error detected while processing function <SNR>137_HandleProblemListCR[51]..<SNR>137_ProblemIdFromNr:
line    6:
E117: Unknown function: trim
E15: Invalid expression: trim(items[1], ' ')
line    7:
E121: Undefined variable: strid
E15: Invalid expression: strid
Error detected while processing function <SNR>137_HandleProblemListCR:
line   53:
E716: Key not present in Dictionary: slug
E15: Invalid expression: problem['slug']

I tried several problems but it happened all the time. I don't think it's a keyring thing.
What am I missing here?

Ah, sorry!
I was using neovim 0.2.2 (default apt install in Ubuntu 18.04). I upgraded it to neovim 0.4.2. (latest stable), and it worked well!
Solved.

Thanks for implementing this good plugin!
I'm using this under Ubuntu 18.04 and Neovim.
I was able to sign-in and see menus ad lists.
However, when I tried to open a problem, an error occurs saying
Error detected while processing function <SNR>137_HandleProblemListCR[51]..<SNR>137_ProblemIdFromNr:
line    6:
E117: Unknown function: trim
E15: Invalid expression: trim(items[1], ' ')
line    7:
E121: Undefined variable: strid
E15: Invalid expression: strid
Error detected while processing function <SNR>137_HandleProblemListCR:
line   53:
E716: Key not present in Dictionary: slug
E15: Invalid expression: problem['slug']

I tried several problems but it happened all the time. I don't think it's a keyring thing.
What am I missing here?

I see the same problem with vim version 8.0.1453 (not neovim).

nevermind, found the problem.  The default version with ubuntu is not a high enough version.  I upgraded to vim 8.2, and can now use the functionality.


[IOTDB-2305]Library anomaly

Description
Add Anomaly Detection of UDF functions through Library-anomaly.

Coverage decreased (-0.03%) to 68.064% when pulling f8388533019967d7e19203d0a4b017eebd4c3d41 on trin1t:library-anomaly into 001490bbd734eab37ee4dcc5530b0dac33603870 on apache:master.


ERROR: for nginx  Cannot start service nginx: driver failed programming external connectivity on  and ERROR: for mysql  Cannot start service mysql: driver failed programming external connectivity on endpoint laradock_mysql_1

ERROR: for nginx  Cannot start service nginx: driver failed programming external connectivity on endpoint laradock_nginx_1
(70abb55c6fea0fad18be272bec05c124f70585a5d5da79d781e1608c5d847b0e): Bind for <IP_ADDRESS>:443 failed: port is already allocated  ERROR: for mysql  Cannot start service mysql: driver failed programming external connectivity on endpoint laradock_mysql_1 (7223c8ffa61a6f82de0f37f9e9ac5d8bfd7087626426c5eda3ff7e4d1efba1e0): Error starting userland proxy: listen tcp <IP_ADDRESS>:3306: bind: address already in use

@sagarjethi apparently your ports (443 and 3306) are already in use, either change them in the .env file or see where those ports are used in your machine and turn them off.


fix task metric types in statsd emitter

except success and failure stats, task count metrics should all be
gauges, since they represent the current state and not some aggregate
counter over time.

test failures are unrelated
[ERROR]   Run 1: KafkaIndexTaskTest.testRunTransactionModeRollback:2434 expected:<2> but was:<3>

test failures are unrelated
[ERROR]   Run 1: KafkaIndexTaskTest.testRunTransactionModeRollback:2434 expected:<2> but was:<3>


Add webxr platform

XRTK - Mixed Reality Toolkit Pull Request
Overview

Adds WebXR platform to the core project

Still looks good, but don't we need the WebXR platform to build and run first?

@SimonDarksideJ it is already running builds against WebXR

PR does have a module and submodule for WebXR, but the build reports is as a failure and cannot build?


Build Error occurs after installing ember-bootstrap-4

Hi,
Recently installed the ember-bootstrap-4, encountered build error,  Not sure what exactly the reason, tried clearing cache from root node of app, again ran npm i.
File to import not found or unreadable: ember-cli-bootstrap-4/bootstrap
Parent style sheet: W:/src_veekshan/veekshan/veekshan-ui-app/tmp/sass_compiler-input_base_path-gtqX9elz.tmp/app/styles/app.scss

You are on the wrong repo here, this is the ember-bootstrap package, but your error comes from ember-cli-bootstrap-4: https://github.com/kaermorchen/ember-cli-bootstrap-4


ci(*): update publish/deploy to use ghcr.io; untrack static/data.json

Updates publish/deploy logic to use an OCI registry (first choice: ghcr.io).  In doing so, we generate the search index (static/data.json) at time of publishing, removing the need to track in version control.  (Ref https://github.com/fermyon/developer/issues/369)
Placing in Draft for now as there is one blocker:  Getting errors attempting to push this Developer website Spin app to ghcr.io (see https://github.com/vdice/developer/actions/runs/4326339883/jobs/7553631989).  An auth error is produced which is odd/unexpected as I can publish other Spin apps to ghcr.io with the same flow.  Additionally, this Developer site can be published to docker.io/DockerHub.  Need to investigate.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[ ] The title, template, and date` are all set
[ ] Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
[ ] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[ ] Has passed bart check
[ ] Has run npm run build-index
[ ] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
[ ] Headings are using Title Case
[ ] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[ ] Have tested with npm run test and resolved all errors

Does the action have write permissions to the package API? IIRC you need to add the following to your job metadata:
jobs:
  publish:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write

https://docs.github.com/en/actions/publishing-packages/publishing-docker-images#publishing-images-to-github-packages

@bacongobbler I could reproduce this issue from my local CLI as well. I am able to push other packages but this one fails. So I am not entirely sure that it is a permissions issue.

I see the same thing as @karthik2804 - from my local machine:

I can push "hello world" applications to ghcr
I can push the developer docs site to my localhost registry
But pushing the developer docs to ghcr fails with 401 Unauthorized

I did wonder if it could be a size issue, as it takes a long time to upload, but the developer docs package looks to be about 35MB, which doesn't seem unreasonable.  And of course it would be very rude to report that as "authentication required" anyway.
@radu-matei, I think you probably know more about OCI than the rest of us - any insight into what might cause this behaviour and response, or how to diagnose it?

Superseded by https://github.com/fermyon/developer/pull/588


Ability to set last-modified of s3 keys

with the current S3 API it's impossible to set the last-modified time of an S3 key, however this is very useful for testing.
I found a hacky way of doing this via:
key = self._moto_svc._main_app.app_instances['s3'].view_functions['ResponseObject.key_response'].callback.__self__.backend.buckets[BUCKET_NAME].keys[KEY_NAME]
key.last_modified = LAST_MODIFIED

however it would be really useful if there was a better way to access the underlying bucket to be able to set properties like this.

Not a lot nicer, but you should be able to do the same thing with:
key = moto.s3.models.s3_backend.buckets[BUCKET_NAME].keys[KEY_NAME]

I'm open to ideas on this, but would probably be against creating an entirely separate API. Any other thoughts?

@spulec seems straightforward. Since FakeKey.last_modified is public API, someone can easily change it for testing. I would suggest that you create something like a contrib package in the project and contributors can add there any utility functions that wrap useful operations. What do you think?

Cool. If that works feel free to close this. Would be nice to be documented.

Got it, I have some ideas for this going forward.

@spulec any hope of getting a way to do this in standalone server mode? I'm using moto with a Rails app and test suite, and we're depending on last-modified logic for some tests I'd love to do in moto.

FYI, in newer versions you have to use:
key = moto.s3.models.s3_backends["123456789012"]["global"].buckets[BUCKET_NAME].keys[KEY_NAME]


ffcv imagenet won't start

Hi! I am training a resnet50 using ffcv imagenet here is my config

I am having trouble getting it to start as shown here

It won't start at 0. I checked CUDA is working fine. Please help! Thanks a lot!

I set some debug point and it turns out there is nothing yield in the for loop of a ffcv loader:
for ix, (images, target) in enumerate(train_loader): .....
I define the train_loader as follows:
def create_train_loader(self, train_dataset, num_workers, batch_size,
                            distributed, in_memory):
        this_device = f'cuda:{self.gpu}'
        train_path = Path(train_dataset)
        assert train_path.is_file()

        res = self.get_resolution(epoch=0)
        self.decoder = RandomResizedCropRGBImageDecoder((res, res))
        gaussian_kernel_size = 5
        sigma = 2
        image_pipeline: List[Operation] = [
            self.decoder,
            RandomHorizontalFlip(),
            ToTensor(),
            transforms.RandomApply([transforms.GaussianBlur(gaussian_kernel_size, sigma)], p=0.5),
            ToDevice(ch.device(this_device), non_blocking=True),
            ToTorchImage(),
            NormalizeImage(IMAGENET_MEAN, IMAGENET_STD, np.float16)
        ]

        label_pipeline: List[Operation] = [
            IntDecoder(),
            ToTensor(),
            Squeeze(),
            ToDevice(ch.device(this_device), non_blocking=True)
        ]

        order = OrderOption.RANDOM if distributed else OrderOption.QUASI_RANDOM
        loader = Loader(train_dataset,
                        batch_size=batch_size,
                        num_workers=num_workers,
                        order=order,
                        os_cache=in_memory,
                        drop_last=True,
                        pipelines={
                            'image': image_pipeline,
                            'label': label_pipeline
                        },
                        distributed=distributed)

        print("loader: ", loader)

        return loader

Could really use some insights!!!


.Net: Utbose/open api/fix/default value for params

Motivation and Context

Why is this change required?
This change will help assign default values that is specified in openAPI schema to parameter objects if no arguments are provided from the caller. Without this change we wont be able to support urls which has default query parameters.
What problem does it solve?
Currently if the caller does not set any arguments for the query parameters, the RestApiOperation.BuildQueryString() does not assign any value to the query parameter objects even though they have default value specified in the openAPI spec.
What scenario does it contribute to?
Executing REST API using openAPI spec.
If it fixes an open issue, please link to the issue here.

Description
Making changes in code to ensure if the query parameters cannot be populated from the caller provided arguments, then just use default values (if specified in openAPI spec) to populate them instead of dropping of the query parameter all together.
Created a new issue: https://github.com/microsoft/semantic-kernel/issues/5864
Contribution Checklist

[*] The code builds clean without any errors or warnings
[*] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[*] All unit tests pass, and I have added new tests where possible
[*] I didn't break anyone :smile:

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree company="Microsoft"

Closing the PR because a workable solution for using and accessing default values of parameters has been provided. See the https://github.com/microsoft/semantic-kernel/issues/5864 issue for more details.


PoC refactoring using React Context for passing down the config in co…

…mponents

How would we access the config in helper functions? They'd have to be refactored and passed a config registry, I believe?

We also use settings in the server module.

@tiberiuichim I have the faith that if we remove the requirement from the components alone, it would be enough to cut the chain. The others can still work as before with the direct imports.
Anyways, I still think that we should separate the registry from the core config.

Closed, we now have the config registry.


":" expected

I'm getting this message when I try to compile my SWELFOOP
":" expected
Here's the file:
[(https://github.com/jggames/trs80mc10/blob/master/quicktype/Puzzle/SwelFoop/SWELFOOPcompiler8.TXT]
I've gone though it looking for anomalous code, but can't find anything obvious.

The compiler doesn't yet parse the "^" operator.
> mcbasic swelfoop.bas
Compiling swelfoop.bas...
swelfoop.bas(75): 2200 SC=SC+(YD-2)^2:GOTO1700
                                   ^
":" expected

I hadn't added EXP and LOG until this morning, so I suppose that explains that "^" doesn't quite work yet.  I'll tweak it so that a parse error properly emits the offending line, and add an optimization when it sees an integer exponent.

The compiler doesn't yet parse the "^" operator.
> mcbasic swelfoop.bas
Compiling swelfoop.bas...
swelfoop.bas(75): 2200 SC=SC+(YD-2)^2:GOTO1700
                                   ^
":" expected

I hadn't added EXP and LOG until this morning, so I suppose that explains that "^" doesn't quite work yet.  I'll tweak it so that a parse error properly emits the offending line, and add an optimization when it sees an integer exponent.

I've added support for the ^ operator, compiled and run swelfoop.
It's added to the examples directory now.

I've added support for the ^ operator, compiled and run swelfoop.
It's added to the examples directory now.

Hadn't noticed that ^ wasn't supported.  Thanks for getting adding that!

Hadn't noticed that ^ wasn't supported.  Thanks for getting adding that!


Preparation for art v3_15_00

This PR is a companion to Offline PR 1257.  The two can be merged independently.
Make changes to that are required for art suite v3_15_00 that upgrades root to v6_30_06. The submitted code builds with both the new art suite and the with the current art suite v3_14_03.   I have not yet run-time tested the REve changes.
In most cases the problem was that fhicl code was exposed to dictionary makers because of people having includes that were either unneeded or were in the .hh file rather than the .cc file, where they belonged. I don't understand the details of what in fhicl is causing the problem but there is no reason for fhicl code to be exposed to dictionary makers.
The one special case was  inc/CollectionFiller.hh.  In this case I used #ifndef __ROOTCLING__ to hide the offending code from root.
There is one more commit coming about dealing with the movement of some classes from ROOT::Experimental to ROOt:: . I am still working on it and this will be in draft status until it is resolved.

@sophiemiddleton when you get a chance, please to a test merge in your own area and verify that my use of  #ifndef __ROOTCLING__ in  inc/CollectionFiller.hh did not break anything.  I am not sure how to test it.  I expect that it will be OK.

Yes I will do that before merging

@sophiemiddleton  The CollectionFiller class is included in classes_def.xml and classes.h.  I am curious why it needs to be.  Do you call it from the GUI or command line?

Its used to pass in the arguments from fcl

Its used to pass in the arguments from fcl

Perhaps I am missing something really simply.  What functionality exists that requires that CollectionFiller be visible to genreflex?   Is there a way to change values inside of the instance that lives in REveEventDisplay_module from the root command line or the GUI?

My updates to the PR are in.  Modulo responding to comments and requests, this is done.   The most recent changes are

Revert the use of ROOTCLING and instead remove CollectionFiller from classes.h and classes_def.xml.  I don't see why they would be needed there.
I added code to src/SConstruct to define the C preprocessor variable NUMERIC_ROOT_VERION that holds the UPS root version transformed into a pure number.  This is passed into make_mainlib and make_plugins.  I don't think it's needed in make_dict_and_map.
I added a test in REveEventDisplay_module.cc to choose the correct namespace for RWebWindowsManager depending on the the ROOT version encoded in the c preprocessor varaible.

You need to put the test of  NUMERIC_ROOT_VERION after the #include to defines the class.  I suggest putting it after all includes.  A corollary is that we cannot make one file with all of the usings - we need to put them in files as needed.  If it's only needed in a .cc file, put it there, not in the .hh.  Of course there will be times when it is needed in the .hh
Sophie: please do a test merge and check if everything behaves as expected.

@rlcee Please have a look at the machinery of  NUMERIC_ROOT_VERION  .  Is this a viable solution moving forward?  Can we do it better?

@kutschke this is currently a draft, let me know when it moves to a real PR

@kutschke this is currently a draft, let me know when it moves to a real PR

It's ready to do.  I just un-drafted it.

I see there are conflicts - I will look into it after the meeting

I rebased on top of the new HEAD of main.  This overwrote the commit history in the commit tab above.
To push to my fork I had to add the --force-with-lease option to my push command.
This PR builds with both art v3_14_03 and v3_15_00 on SL7.


Cleanup extracted awscli in isolated regions

Fixes https://github.com/awslabs/amazon-eks-ami/issues/1326
Issue #, if available:
#1326
Description of changes:
Cleanup extracted awscli in isolated regions
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Testing Done
Cleanup command executes successfully.
Proposed changes are not relevant to EKS operation.

@bartmanus this should be solved more generally in https://github.com/awslabs/amazon-eks-ami/pull/1231, let me know if you disagree.


Fixes a typo in inspecti usage

Found a typo while writing out a feature for kubeadm using crictl and wanted to fix it!
Signed-off-by: Chuck Ha<EMAIL_ADDRESS>

LGTM


Artifacts that are already taken as a ghost role still show up as a ghost role

Description
Sentient artifact ghost role still shows up in ghost roles even though it is taken already. When you click the request button after the mini countdown timer telling you about the role it will not do anything. It just becomes a button. This may be triggered after the artifact triggers it's node.

Hello!
Bumping the post as I ran into this today. This can probably go on low priority.


Registries report which commands they support.

In the config.json of each registry's index, that registry can report
which commands it supports, under which versions. For example, crates.io's
config.json should look like:
{
    "api": "https://crates.io/",
    "dl": "https://crates.io/api/v1/crates",
    "commands": {
        "publish": ["v1"],
        "yank": ["v1"],
        "owner": ["v1"],
        "search": ["v1"],
        "login": ["v1"]
    }
}

Currently, these five commands only have one version, "v1," but this allows us
to release new, breaking changes to these commands' interface with crates.io
without disrupting the operation of any alternative registry.
Before this is merged, crates.io's config.json will need to be updated, and we
should make an effort to inform known maintainers of alternative registries
that they need to update their indices as well.
This also involved rewriting the initial stage of the cargo login flow to be a
bit more clear.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

:umbrella: The latest upstream changes (presumably #5939) made this pull request unmergeable. Please resolve the merge conflicts.

LGTM other than making sure that cargo login --registry foo --token bar works even if the registry doesn't support the login endpoint.

@sfackler why should that work? If the registry doesn't support the v1 login flow, that wouldn't be meaningful. If they do support it, they should report that they do.
Imagine that we implement a new login flow in which --token is not meaningful, and the registry only supports that flow. Wouldn't we want that to error?

What's the scope of the v1 login flow? Part of the v1 publish flow is that an Authorization header containing the auth token will be sent along with the request. Even if your custom registry server doesn't expose a /login or /me endpoint it can still support publishing. For example, the auth for our internal publishes is granted to individual builds so they know up front what token to use without any explicit login flow. We use cargo login --registry foo --token $MY_CREDENTIALS as a nicer form of echo "[registry.foo]\ntoken = $MY_CREDENTIALS" >> ~/.cargo/credentials.

That's a good question, and I see why you would think your registry doesn't support the v1 flow. I do just think it means storing an API token and passing it with the Authorization header, which is why for registries other than crates.io the message printed to stdout is modified to be less certain about the /me endpoint:

please paste the API Token below (you may be able to obtain your token by visiting https://$URL/me)

This feature is blocking custom registries landing, which is unfortunate. The main blocker on the PR has been that I have a lot of difficulty understanding how to cargo's test suite actually sets up the environment, so I've never been able to get CI to pass.

@withoutboats sorry for the late reply, but could I help out perhaps with getting cargo test working locally for you? Do you have some example error logs which I could help debug?

Closing per discussion in #6442.


nuttx/uorb: Fix build error

Summary
New member added to struct sensor_ops_s, and type changed, but not update all existed code, for details, please see "Related change" below.

Error 1:

  1153  Building NuttX...
  1154Error: sensors/bme680_uorb.c:428:3: error: initialization of 'int (*)(struct sensor_lowerhalf_s *, struct file *, long unsigned int)' from incompatible pointer type 'int (*)(struct sensor_lowerhalf_s *, struct file *, int,  long unsigned int)' [-Werror=incompatible-pointer-types]
  1155  428 |   bme680_control    /* control */
  1156      |   ^~~~~~~~~~~~~~

Error 2:

      Error: sensors/ms56xx_uorb.c:145:20: error: initialization of 'int (*)(struct sensor_lowerhalf_s *, struct file *, uint32_t *)' {aka 'int (*)(struct sensor_lowerhalf_s *, struct file *, unsigned int *)'} from incompatible pointer type 'int (*)(struct sensor_lowerhalf_s *, struct file *, long unsigned int *)' [-Werror=incompatible-pointer-types]
        145 |   .set_interval  = ms56xx_set_interval,
            |                    ^~~~~~~~~~~~~~~~~~~
      sensors/ms56xx_uorb.c:145:20: note: (near initialization for 'g_sensor_ops.set_interval')
      cc1: all warnings being treated as errors

Related change:

.flush    : 403469336f27568e64a04bbab8c9a1bb68e61f75
.get_info : 703bb7e7b3a1207951bf4f10dfab34c263c18fd9
unsigned log => uint32_t : b17c074a18834f2f69e465b354948f04a4b80d78

Impact
drivers/sensors
Testing
Not tested, not have the relevant boards/peripherals, will be verified by CI compilation.

[Experimental Bot, please feedback here]
Squash The Commits: This PR contains 2 Commits. Please Squash the Multiple Commits into a Single Commit.
NuttX PR Requirements Review
This PR appears incomplete and does not meet the NuttX requirements. Here's why:
Summary:

While the summary describes the technical changes, it lacks a clear explanation of why these changes are necessary. What problem does this solve?
The summary mentions errors encountered but doesn't elaborate on the root cause.
It's unclear what "existed code" wasn't updated and why.

Impact:

Incomplete: The impact section only mentions "drivers/sensors" but needs a more detailed analysis.
User Impact:  Will users need to modify their applications due to the type changes?
Build Impact: The errors indicate a build impact. The description should explain how the build process is affected and if any specific configurations are impacted.
Hardware Impact: Are there any specific architectures, boards, or drivers affected by these changes?
Documentation: Is documentation impacted? If so, has it been updated?
Other impacts (Security, Compatibility):  These are not addressed and should be analyzed.

Testing:

Insufficient: The PR acknowledges a lack of testing due to unavailable hardware. While CI compilation is helpful, it doesn't replace actual functional testing.
Missing Logs: The "Testing logs before change" and "Testing logs after change" sections are empty.

Recommendations:

Explain the "Why":  Clearly articulate the reason and benefits of these changes.
Root Cause Analysis:  Explain why the existing code wasn't updated and the challenges involved.
Complete Impact Analysis: Thoroughly analyze and document the impact on all aspects (users, build, hardware, documentation, security, compatibility).
Testing Plan:  If hardware is unavailable, outline a testing plan for when it's accessible. Consider alternative testing methods like simulation or mocking.
Provide Context:  Give enough information for reviewers to understand the changes without needing to look at the linked commits.

By addressing these points, you'll significantly improve the PR's quality and facilitate a smoother review process.


Adding Items to .gitignore on first launch/fresh repository crashes GittyUp

So I started a fresh project, created a repository and while making the first commit I decided to add a few items to .gitignore so the repository remains clean. All 3 tries crashed Gittyup.
After making a single commit, and adding to .gitignore after that, it no longer crashed.
Occurred on 1.20

How did you ignore? Context menu from the treeview on the right?
Might be the same problem as in #349 .

Yep, right clicked the unstaged file and pressed ignore.

Ok. Patch is already ready :)

This is now in the latest development version


grafana dashboard or collectd-compatible metrics

Is there an existing Grafana dashboard compatible with this exporter's metrics?
If not, I believe the way to go is to try to match collectd plugin metrics export to avoid dashboard fragmentation: https://grafana.com/dashboards?search=apache

Does not work for me: no graph data for the node (although available and selected in the dashboard).
Maybe related to the fact that my target is an IPv6 (I can see that, contrary to node-exporter, the target's IP in grafana dashboard target <select> shows only the first 4 bytes of the IPv6, but I don't know on which side the bug lays).
[but issue is maybe unrelated]
In any case I also additionally have a parse error at char 13: unknown function with name \"count_scalar\"" specific to Apache "up/down status" (@rfrail3 ?)

https://grafana.com/dashboards/3894 - works for me
I got the same "count_scalar" error but if you just edit the panel and hide that query it works fine
Re IPv6 - I am using ipv4 but with hostnames for the targets and not having any problems.  You may need to change the regex for the variables in the panel if it is truncating IPv6 addresses


click.confirm after click.get_text_stream aborts application

Bug: simple application using click.get_text_stream and then later trying to use click.confirm (or click.prompt) automatically aborts application silently.
Expected : no abord, content of stdin is fetched and click.confirm does the confirm job as expected
Demo code:
# demo_code.py
import click

@click.command()
def my_cli():
    s = click.get_text_stream('stdin').read()
    if click.confirm('testing confirm after get_text_stream'):
        print s

if __name__ == '__main__':
    my_cli()

and then call with :
echo "bleh" | python demo_code.py

#304 related?

I don't even see how it's possible to reuse stdin.
will use file argument instead. Closing!


sample correlated SBM

Example:
require(igraph)
gg <- rg.sample.SBM.correlated(n = 100, B = matrix(c(0.5,0.5,0.2,0.5), nrow = 2), rho = c(0.4,0.6), sigma = 0.2)
summary(gg$adjacency$A)
IGRAPH c77bf6c U--- 100 2424 --
summary(gg$adjacency$B)
IGRAPH 3ccfb0c U--- 100 2039 --
cor(as.vector(gg$adjacency$A[]), as.vector(gg$adjacency$B[]))
[1] 0.1494246
Correlated ER
rg.sample.correlated.gnp <- function(P,sigma){
require(igraph)
n <-  nrow(P)
U <- matrix(0, nrow = n, ncol = n)
U[col(U) > row(U)] <- runif(n*(n-1)/2)
U <- (U + t(U))
diag(U) <- runif(n)
A <- (U < P) + 0 ;
diag(A) <- 0
avec <- A[col(A) > row(A)]
pvec <- P[col(P) > row(P)]
bvec <- numeric(n*(n-1)/2)
uvec <- runif(n*(n-1)/2)
idx1 <- which(avec == 1)
idx0 <- which(avec == 0)
bvec[idx1] <- (uvec[idx1] < (sigma + (1 - sigma)*pvec[idx1])) + 0
bvec[idx0] <- (uvec[idx0] < (1 - sigma)*pvec[idx0]) + 0
B <- matrix(0, nrow = n, ncol = n)
B[col(B) > row(B)] <- bvec
B <- B + t(B)
diag(B) <- 0
return(list(A = graph.adjacency(A,"undirected"), B = graph.adjacency(B,"undirected")))
}
non-igraph version of correlated SBM
#gg <- rg.sample.SBM.correlated(n = 100, B = matrix(c(0.5,0.5,0.2,0.5), nrow = 2), rho = c(0.4,0.6), sigma = 0.2)
#cor(as.vector(gg$adjacency$A[]), as.vector(gg$adjacency$B[]))
rg.sample.SBM.correlated <- function(n, B, rho, sigma, conditional = FALSE){
if(!conditional){
tau <- sample(c(1:length(rho)), n, replace = TRUE, prob = rho)
}
else{
tau <- unlist(lapply(1:2,function(k) rep(k, rho[k]*n)))
}
P <- B[tau,tau]
return(list(adjacency=rg.sample.correlated.gnp(P, sigma),tau=tau))
}

@bvarjavand couple things we need to figure out

[ ] how to verify that the rho-sbm implementation is correct

[ ] how to generate rho-sbm with different marginal probabilities

correct
On Fri, Feb 1, 2019 at 7:42 PM Junhao Xiong<EMAIL_ADDRESS>wrote:

@bvarjavand https://github.com/bvarjavand couple things we need to
figure out

how to verify that the rho-sbm implementation is correct
how to generate rho-sbm with different marginal probabilities
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/graspy/issues/66#issuecomment-459915808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACjcn2WtfJFCnxMOEUbDEoD5ryzMR-lks5vJN7fgaJpZM4Yw0Cf
.

--
the glass is all full:  half water, half air.
neurodata.io

@junhaobearxiong Will there be a PR for rhoER and rhoSBM sampling methods?

sure! I can do that once I finish the current set of experiments I'm running.


Support Django 4

Hello. Do you plan to support Django 4 anytime soon? Thank you.

We don't constrain the Django version in wagtail-footnotes.
So it should work. If you're seeing issues with that, please provide more context, tracebacks etc

Apologies, I think I meant to say Wagtail 4 as opposed to Django 4.
When I install Wagtail, version: 3.0.3 is fetched. So I tried installing via<EMAIL_ADDRESS>but I get the following error:
ERROR: Cannot install -r /app/requirements/base.txt (line 11), -r /app/requirements/base.txt (line 6), -r /app/requirements/base.txt (line 9) and wagtail 4.0 (from<EMAIL_ADDRESS>because these package versions have conflicting dependencies.

The conflict is caused by:
     The user requested wagtail 4.0 (from<EMAIL_ADDRESS>     wagtail-footnotes 0.8.1 depends on wagtail<4.0 and >=2.15
     The user requested wagtail 4.0 (from<EMAIL_ADDRESS>     wagtail-footnotes 0.7.0 depends on wagtail<3 and >=2.5
     The user requested wagtail 4.0 (from<EMAIL_ADDRESS>     wagtail-footnotes 0.6.0 depends on wagtail<3 and >=2.5
     django-tailwind 3.1.1 depends on django>=2.2.25
     wagtail 4.0 depends on Django<4.2 and >=3.2
     wagtail-footnotes 0.5.0 depends on Django<3.2 and >=2.2
     django-tailwind 3.1.1 depends on django>=2.2.25
     wagtail 4.0 depends on Django<4.2 and >=3.2
     wagtail-footnotes 0.4.1 depends on Django<3.2 and >=2.2
     django-tailwind 3.1.1 depends on django>=2.2.25
     wagtail 4.0 depends on Django<4.2 and >=3.2
     wagtail-footnotes 0.4.0 depends on Django<3.2 and >=2.2
     django-tailwind 3.1.1 depends on django>=2.2.25
     wagtail 4.0 depends on Django<4.2 and >=3.2
     wagtail-footnotes 0.3.1 depends on Django<3.2 and >=2.2
     The user requested wagtail 4.0 (from<EMAIL_ADDRESS>     wagtail-footnotes 0.3.0 depends on wagtail<2.10 and >=2.5
     The user requested wagtail 4.0 (from<EMAIL_ADDRESS>     wagtail-footnotes 0.2.0 depends on wagtail<2.10 and >=2.5

My requirements file is as follows:
boto3
cookiecutter
crispy-tailwind
django-cors-headers
django-storages
django-tailwind==3.1.1
Pillow
sentry-sdk
# wagtail
<EMAIL_ADDRESS>wagtail-footnotes
wagtail-metadata
wagtailcodeblock
wagtailmedia
wagtailfontawesome
Wand

There are multiple issues here. your requirements.txt should specify versions, or version constraints.
For example: having just wagtail means whenever there is big new version you will get that. and things will likely break because of various deprecations. Case in point, you mention Wagtail 3.0.3, but the log shows clearly it tries to install Wagtail 4.0, but there's a clash with wagtail-footnotes as it is currently constrained to <4.0

So I tried installing via<EMAIL_ADDRESS>oh, I missed that you went specifically for Wagtail 4.

#39 bumps the Wagtail version restriction. In theory could specify<EMAIL_ADDRESS>and test it and perhaps report any issues

#39 bumps the Wagtail version restriction. In theory could specify<EMAIL_ADDRESS>and test it and perhaps report any issues

This worked nicely, thank you!

@2qxtx I'm sorry if you were relying on my branch which I just deleted. I didn't see this closed thread before deleting it. My fork was not sufficient as you probably noticed when you submitted #43. I'll do my best to review #42 and do what I can to contribute to a releasable fix, since this is impacting a project of mine as well.

@jsma. No worries and thanks for letting me know. I'm using Wagtail 4 and, as you say, I was relying on your branch. I now find myself in a bit of a pickle as I can't run my project in development without pip installing your branch, nor can I downgrade to an earlier versions of wagtail-footnotes as they rely on Wagtail 3 and below. Do you know how I can remove references to wagtail footnotes (e.g., in my migration files which import wagtail_footnotes.blocks), without affecting other data held in RichTextBlocks? So basically, I would like to revert back to using Wagtail's native RichTextBlocks for the time being.

We're running #42 in production and so far we haven't had any issues. You can install that branch by adding this to your requirements, while we wait for a proper release:
wagtail-footnotes @ git+https://github.com/torchbox/wagtail-footnotes@93131b4b230ea59c5357476576d3551dffe8f20d

Thank you. That solved my problem nicely!

@2qxtx @jsma https://github.com/torchbox/wagtail-footnotes/releases/tag/0.9.0 is out with the full Wagtail 4 support


Canvas: Dragging with middle mouse button lags the canvas

I think this is caused by the scroll code activating at the same time as the drag code? Not sure.

Closed with 356c2362d1af00252c300f496ee6f694da932836


avoid infinite loop

I have a test case with an infinite loop that I cannot break:
local a = string.find(("a"):rep(1e4), ".-.-.-.-b$" )
With debug.sethook I can include an instruction counter, but it doesn't work here.
Any suggestions how I can avoid this?
Thanks

Does set a timeout when initializing wasmoon solves your problem?
const lua = await factory.createEngine()
lua.global.setTimeout(Date.now() + 1000)
// ... run lua

I guess a timeout function would solve the problem - it tried it: an infinite loop is stopped after n ms, but the string.find example is not stopped. Also I think it clashes with my lua internal debug.sethook settings, but that would be solvable.
But thanks for the hint.


Equivilant of RemoteAddr on all Channels.

Is your feature request related to a problem? Please describe.
I need to be able to tell where an Activity is from. There are any number of reasons, almost anything an existing website does with RemoteAddr would apply. Throttling, Tailoring, Tracking etc. but one example is we'd like to be able to reverse geolocate the user to make sure to use the QnA thats specific for their country. If the location cant be identified then a generic QnA is used.
Describe the solution you'd like
Dependent on which Channel is being used the Azure "Web App Bot" must have specific information about the requester. In the WebChannel for example Azure "Web App Bot" has the RemoteAddr Header. Presumably other channels have similar info. This info should be passed along in the ChannelData property of the Activity to the Bot App Service.
Describe alternatives you've considered
At first glance ServiceUrl appears to provide this information but once the bot is deployed to Azure ServiceUrl always returns as  “https://directline.botframework.com/” which is presumably the direct upstream service IE the Azure "Web App Bot".
Additional context
There is a Stackoverflow from back in 2017 that describes a work around. Unfortunately this only works for the WebChannel.
https://stackoverflow.com/questions/42825048/bot-framework-get-the-serviceurl-of-embedded-chat-control-page
[enhancement]

@DavidStrickland0 We don't have any currently planned work in this area. If you describe your scenario in more detail, me may be able to provide suggestions for a specific workaround.

Not sure how else to describe it. If someones attaching to my Bot via any channel that allows anonymous connection I need to have some way to identify them. GeoLocate them, Track them, Store Data about them, make educated guesses about who they are and what they need. On a website you do that using their IP Address and or the Referrer and whatever other headers you have on the HttpRequest. If the user talked directly to my Bot I'd have all that by looking at those http headers. With the Microsoft Azure Web App Bot in between me and my user performing pass through I can't get any header information. Relying on the bot consumer to write their WebClient in such a way as to send me that info in Events isnt reliable. Most of the channels are authenticated channels but any channel that allows anonymous connections your going to want \ need as much info as you can get about the incoming connection. You don't have a user context so you have to fall back on the data that you do have …. which at the moment is none at all.

Perhaps our biggest concern atm is Scraping. On our websites its a constant war between the data scrapers and the site administrators. If we create a bot that allows via dialog access to the same data we have on the site its a new frontline in the war. Currently we are constantly analysing traffic. Blocking \ Throttling or misinforming requests we Identify as performing questionable activity while at the same time attempting to keep channels open for legitimate users. We need as much data about the incoming request as we can get to segregate legitimate bot users from automated data scrapers.
On the other side of the equation we want our Bot to be as intelligent as possible. We want to feed as much data as we can into our AI Models so we can to get an intuitive bot that can predict what the user wants. The more data we have about the incoming request the better we can predict what the user needs. In this case browser version\ OS Version  would even be of value any and ever data feature we can feed into the model may well prove to be the key data point. Knowing that the  Microsoft Azure Web App Bot is swallowing that data and not passing it through to the Bot is very frustrating.

@garypretty, any update on this?

@DavidStrickland0 Are you able to provide me with the different anonymous channels that you are currently / planning to use?  It's also not clear to me if you have control of the web chat implementations for your bot - can you clarify?

@garypretty At this point the only anonymous channel we are offering is the Web Channel that however will change as our clients request additional avenues of engagement. If there is another Anonymous channel that Microsoft supports out of the box I'm fairly certain we'll end up having to support it eventually.
As for control of the Web Chat Implementations given its an open platform that anyone can write a WebChat Implementation for it's not something I can say yes to. Granted we have a web chat implementation that our UI team has created which we plan to offer. However as a backend developer I never trust the source and have to assume that every scraper that wants to automate the bot and pull data and eventually every consumer is going to use their own custom implementation. They may start using what we offer but it wont stay that way for long when they realize they can customize it and write their own. We've got security by obscurity at the moment. I doubt it will last.

@DavidStrickland0 just so I am clear, you have created the bot, but then are allowing other developers to implement their own web chat interface to talk to the bot?  If you are building your own web chat interface then you should be able to secure this so that only your web chat implementation can communicate with the bot.  Are you using the token API approach?  You can find the links to doc for that and the web chat authentication at https://docs.microsoft.com/en-us/azure/azure-monitor/app/overview-dashboard#troubleshooting

At the end of the day every web channel bot is an API sitting behind an Api at
https://directline.botframework.com/v3/directline/conversations.
Not certain how a Token Api Approach will help. We are using it but that really just gives us tracking. If an Anonymous user can get a token all it does is add one more step in the process of gaining access... Get the token then access the bot. We can put some control on how many tokens we issue etc. But in those cases all I have is the Token Request not what is happening in the bot using that token...... or is there a way to see the Token from withen the bot code so I can aggregate that data back to the Token Request?
IMHO: Every Bot Developer should be assuming that any Client can access their bot. Once the Microsoft Bot Framework goes live I'm sure we'll start seeing Bot Compilation Sites and Universal Bot Apps that aggregate Multiple bots into a single interface. You just add a Bot ID to your Contact List and by providing the Bot Id it gets added to a Universal bot phone book thats crowd sourced. And of course 101 other Unexpected applications no ones even thinking of at the moment.

Having confirmed with other members of the team internally, right now you will only receive the information received via the HTTP request, which is going to vary between channel / networking. You can, as you mentioned, use the extensibility options of the latest web chat control to send additional information along on the incoming activity. You could also use something like the HTML5 capabilities within the browser to get the user's location and send that too, but this would still depend on the user agreeing to provide their location when asked.  This is going to be the same situation with other channels too - for example, if you are using Facebook, then you can explicitly request location using built in Facebook capabilities. Again though, this relies on the user agreeing to provide it.
For most of the channels, other than web chat, you will get some sort of UUID from the channel (even if it doesn't identify the user explicitly). Ultimately, if users are using your bot anonymously, then the only way to be sure that they are a 'valid' user would be to authenticate them in some way, which obviously is not feasible / possible in every case.
I would definitely recommend you look into using the web chat extensibility, as I said. You can find a sample of piggybacking data on the back of outgoing activities at https://github.com/microsoft/BotFramework-WebChat/tree/master/samples/04.api/b.piggyback-on-outgoing-activities
We really appreciate your feature request in this area, but right now we have no plans to implement anything additional within this area.  I am going to close out this issue now, but if you are struggling to implement any of the additional features for your web chat implementation, then please raise an issue in the webchat repo (https://github.com/microsoft/BotFramework-WebChat).

Gary thanks for looking at this.
After looking again at the docs for webchat Authentication https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-direct-line-3-0-authentication?view=azure-bot-service-4.0#security-considerations
I realized I was missing the fact that the Token Request returns both a token and a ConversationID. This presumably will allow me to tie the conversation back to the token request which will let me have access to any data that posted with the TokenRequest which would include then the RemoteAddr that the token request came from. Read right past this several times before I realized what it potentially means. Figured I'd post it up in case someone else stumbles on this later.
Thanks Again
Dave


Support multiple compose files, refactor compose commands

The Problem:
To facilitate #121, we decided to support users providing multiple docker-compose files for extending and overriding services. We have also been wanting to rework a lot of our compose command code for a while, so this provided a good opportunity to do so.
The Fix:
This PR introduces the functionality necessary to support multiple compose files within the .ddev directory. The functionality will find any docker-compose files and process them into the -f FILE arguments for docker-compose.
This PR additionally updates the docker compose service name definitions, so that they are consistent across projects. This will help facilitate the end goal of users being able to drop in extension files for their project.
Per #129, we are trying to avoid shelling out commands. I did attempt to implement libcompose to replace compose commands, but unfortunately I was not able to get this to a working state within a reasonable time. I suspect this change is more involved than what I was attempting to implement, but there is also a lacking in documentation, and libcompose is still considered an experimental library. I also tried to implement exec using go-dockerclient, and while I was able to get this working at a surface level, I wasn't able to resolve unexpected behavior with interactive exec and lack of error code return on non-interactive commands. I do hope to follow up both of these issue in the future, but for now I think it's best to clean up and improve the existing compose command shell outs.
Remaining Items
This is still WIP, but its at a point where it can be tested and have initial reviews. Items to still address:

[x] New test cases
[x] Cleanup/rework logs command - The changes made so far do not provide multipe compose files, so it can not yet be used for services defined outside the main compose file.
To really make drop-in and spin up possible, we need a way to discover exposed ports from custom compose files and update the router exposed ports accordingly.

Docs, but I will open a separate PR for that so it can be reviewed  #independently.

The Test:
To test this functionality, create additional compose files in the .ddev folder of a project. https://github.com/drud/ddev/issues/121#issuecomment-297839323 contains a docker-compose.solr.yaml example. This should be a working sample (w/ exception to exposing custom ports on the router), so you should be able to save that file in your project, start the project, and have an additional solr container successfully provisioned as part of the project.
Another file to test would be a docker-compose.override.yaml file. We ensure this is the last file provided, so as to provide a way for users to override the main compose file, or any of the configuration from other compose files like docker-compose.solr.yaml. A simple way to test this would be to create this example override file, and run a docker inspect on the db container to verify the test env var is present:
version: '2'

services:
  db:
    environment:
      - TEST_ITEM_OVERRIDE=foo

If you want to test even further, you can reference https://docs.docker.com/compose/extends/ for what should be possible with multiple extending/overriding files.
Automation Overview:

Existing tests have been updated for these changes. Additional tests have been added for the new app Exec, ComposeCmd, and FindFiles
Related Issue Link(s):
#121 ability to use custom containers
Release/Deployment notes:

This should be in good shape at this point. As discussed in standup, the concern for exposing ports on the router will be addressed separately from this PR.

I haven't yet tested this manually yet, that is still to come.


Validate UnsignedByteArray's .equals method

If two UnsignedByteArray references are not equal, we should check the list references, and if those aren't equal, then do a deep compare to check for equality (the current implementation leaves this comparison up to the implementation, which might cause unintended consequences).

I created https://github.com/XRPLF/xrpl4j/issues/248 which is slightly related to this issue.


Control GUI - Error during read servo position

Hi guys,
I am experiencing the following error when read_ServoPos method is called (located within controlGUI.py file):
INFO: Connecting to PiArm on Port /dev/ttyS0 & baudrate 115200..
INFO: PiArm is Initialized
DEBUG: write: b'UU\x01\x04\x1f\x01\xda'
DEBUG: notification: Serial Device Connected
DEBUG: write: b'UU\x01\x03\x1c\xdf'
DEBUG: response: [b'U', b'U', b'\x7f', b'~', b'\\', b'\x00']
Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python3.7/tkinter/__init__.py", line 1705, in __call__
    return self.func(*args)
  File "/home/pi/PiArm/controlGUI.py", line 279, in read_ServoPos
    pos = int.from_bytes(response[5]+response[6], byteorder='little')
IndexError: list index out of range

The code is in accordance with Servo Communication Protocol.pdf specification. Based on DEBUG logs, received array has only 6 items, so with zero-indexed array, there is no response[6] element.
When I "workaround" the error with pos = int.from_bytes(response[4], byteorder='little') on line 279, the console output is as follows:
INFO: Connecting to PiArm on Port /dev/ttyS0 & baudrate 115200..
INFO: PiArm is Initialized
DEBUG: write: b'UU\x01\x03\x1c\xdf'
DEBUG: response: [b'U', b'U', b'\x7f', b'~', b'\\', b'\x00']
DEBUG: write: b'UU\x02\x03\x1c\xde'
DEBUG: response: [b'U', b'U', b'\xbf', b'\xc7', b'C']
DEBUG: write: b'UU\x03\x03\x1c\xdd'
DEBUG: response: [b'U', b'U', b'~', b'~', b'\\', b'\x04']
DEBUG: write: b'UU\x04\x03\x1c\xdc'
DEBUG: response: [b'U', b'U', b'_', b'\xc7', b'G']
DEBUG: write: b'UU\x05\x03\x1c\xdb'
DEBUG: response: [b'U', b'U', b'}', b'~', b'\\', b'\x02']
DEBUG: write: b'UU\x06\x03\x1c\xda'
DEBUG: response: [b'U', b'U', b'\xbe', b'\xc7', b'K']

Please note that responses from servos 1,3,5 have 6 items while responses from servos 2,4,6 have 5 items only.
When I move with arm manually and read the values again, they remain the same.
Moreover, writes to servos return no error, but no servo is moved.
My setup is as follows:

Raspberry Pi 4 8GB, Raspberry Pi OS (32-bit) with desktop and recommended software
PiArm Basic Kit (purchased recently)
Servo Shield connected via GPIO
Arm connected via JST connector type 1 (number 14 in your lesson 1); number 7 has the same behavior
LED on servos are blinking a 7 color sequence + turned off (does it mean something?)
powered by included AC adapter
servos are daisy-chained - wire from servo below going into left socket, then wire from right socket to next servo up; as described in MagPi review; wiring based on you tutorial where motors 3 and 2 are wired differently makes no change in behavior

Where else should I look for the error reason? Is it something wrong with the shield? Is it Raspberry Pi 4?
Please help.
Regards,
Jan

I am solving the issue with support via other channel. I'll put here the solution once it'll be known...

For now, the only working solution is connecting the shield via USB - everything works as expected. Except the buzzer beeps for some unknown reason, but it can be turned off by removing jumper (marked by number 1 in lesson 1)
I'll post updates, when new information will come...


Removed max compile errors flag

PR Summary
For #315 , this removes fmax-errors=3 from the singularity-eos build flags. I had put this in when debugging a build, but forgot to remove it later.

[x] After creating a pull request, note it in the CHANGELOG.md file

Thanks for the quick fix, @mauneyc-LANL . This is trivial enough I'm going to skip the changelog.

too late


Bug: User settings page layout shift

Describe the bug
The left section of the user settings page gets squeezed up because of the right section of the page is taking more space.

PS: Ignore the color differences on some of the elements in the above GIF.
Steps to reproduce

Go to users settings page
And you will notice the layout shift. Because the right section "Delete Account" takes up the space.

Browsers
No response
Additional context (Is this in dev or production?)
Beta
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[X] I agree to follow this project's Contribution Docs

I have made some changes which will fix this issue.

When does this occur @sourabpramanik? It seems fine to me. What operating system are you using?

I am using windows. I tested in Chrome and Firefox as well and got the same result


Rename activity param to newActivity

What does this pull request do?
Renames activity param to newActivity
What is the intent behind these changes?
To more clearly indicate that activities can only be added to an action
plan, rather than edited or deleted.

Has a member of @ministryofjustice/interventions-service okayed this?

Has a member of @ministryofjustice/interventions-service okayed this?

yeh this came out of a discussion between rajiv and george i think


Fix #8015

See #8015

This also fixed https://github.com/concrete5/concrete5/issues/6983 (which #8015 is a duplicate of.)
Thanks!


stage haskell cabal file so direnv works

I noticed I have to manually git add the new cabal file, so I spent ten minutes reading the source to see how I might fix that.
I dunno if this is the right way, but it appears to work after testing with nix run github:shapr/templates/stage-cabal-file
If there's a better way, let me know and I'll improve this pull request.

This will fix #31 , I hope


Release v0.23

Closes https://github.com/PistonDevelopers/piston/milestones/v0.23
This release makes it easier to create and hide multiple windows within
the same application without using the underlying window API. Some extra fields were added
to WindowSettings, and the docs for pistoncore-window was improved.

Changed BuildFromWindowSettings::build_from_window_settings to take
&WindowSettings instead of WindowSettings
Derive Clone on WindowSettings
Added missing methods on WindowSettings
Added "resizable", "decorated" and "controllers" to WindowSettings
Improved docs for pistoncore-window
Handle input before rendering in event loop to fix panic when closing
window
Added "position", "show" and "hide" to AdvancedWindow

Travis CI failing because it can't get the source from crates.io.
Merging.

Seems crates.io is having trouble. Will publish tomorrow if it's fixed by then.


Use native equivalent of lodash.debounce

Refs: https://github.com/bluesky-social/social-app/issues/6471
Docs: https://you-dont-need.github.io/You-Dont-Need-Lodash-Underscore/#/?id=_debounce

While I know how to write a debounce, is there any benefit to this? The Lodash one works fine.

I think it's fine not to do this.


Add a getting started document

In addition to that, move docs to the docs folder, which is the standard github location for github pages.
It includes two static html files that will help create a heckler app.
There are also some config updates to give it better defaults.

Includes all commits from https://github.com/braintree/heckler/pull/15 and it's parents.


Adds intellij setup docs

Todo:

[ ] maybe prevent external links for checkstyle.xml etc.

I think we should shrink these files:

docs/developer-guide/graphics/copyright-profile-new.png
docs/developer-guide/graphics/formatting-copyright-new.png

The seem to originate from a Mac with Reitina display, therefore the resoution is very high, causing larger images and longer page loading times.


Databases storing

Databases (provided by mothulity_dbaser and used by mothulity in analysis) could be by default stored in mothulity directory.

Nice.
Could you update README to support current solution?

New features are briefly described in the README file. Please see and review v1.4.1 release.


Added Danish translation

Added danish translation of texts.

[x] Make sure you follow Element's Contributing Guide.
[x] Rebase before creating a PR to keep commit history clear.
[x] Add some descriptions and refer relative issues for you PR.

Thanks for contributing!

@Leopoldthecoder Thanks. And thank you for creating this great toolkit. Really impressive work.


fix: handle gaxios 401 when getting drive ID

Description
Happens when oauth tokens are revoked.
We should put the connector in error, which is automatically done by throwing ExternalOAuthTokenError
Risk

Deploy Plan

LGTM 👍


HPA specs with quantities causes install errors.

Bug description
Setting quantities in the IstioOperator CR causes unmarshalling errors.
2020-06-19T14:57:34.491412Z	error	k8s.io/client-go@v0.18.0/tools/cache/reflector.go:125: Failed to list *v1alpha1.IstioOperator: v1alpha1.IstioOperatorList.Items: []v1alpha1.IstioOperator: v1alpha1.IstioOperator.Status: Spec: unmarshalerDecoder: json: cannot unmarshal number into Go value of type map[string]json.RawMessage, error found in #10 byte of ...|d":true}}},"status":|..., bigger context ...|emo","values":{"pilot":{"autoscaleEnabled":true}}},"status":{"componentStatus":{"AddonComponents":{"|...

[ ] Configuration Infrastructure
[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
To be able to install when setting quantities in the HPA spec
Steps to reproduce the bug
Create the below CR. It appears this is only quantities because if I change targetAverageValue: 1000 to targetAverageUtilization: 1000 then this works. The difference here is the latter is of type integer not Quantity
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  namespace: istio-system
  name: example-istiocontrolplane
spec:
  values:
    pilot:
      autoscaleEnabled: true
  profile: demo
  components:
    pilot:
      k8s:
        hpaSpec:
          scaleTargetRef:
            apiVersion: extensions/v1beta1
            kind: Deployment
            name: istiod
          minReplicas: 1
          maxReplicas: 5
          metrics:
          - type: Resource
            resource:
              name: cpu
              targetAverageValue: 1000

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
client version: 1.6.3
control plane version: 1.6.1
data plane version: 1.6.1 (12 proxies)

I tried with targetAverageValue: 1000 and in my case with 1.6.3. Instead of throwing unmarshal error it completely ignored installing CR in istio-system.
The same CR works with targetAverageUtilization: 1000 and installs it into istio-system namespace.
$ istioctl version
client version: 1.6.3
control plane version: 1.6.3
data plane version: 1.6.3 (2 proxies)

That's interesting, did you mean it created the CR in kube but the operator completely ignored it? or did it just not let you create the CR?

CR created successfully without any error with targetAverageValue: 1000, but I think the operator ignored it. When I run
$ kubectl get pods -n istio-system
No resources found in istio-system namespace.

But when I use targetAverageUtilization: 1000 and run get pods it shows demo profile created after some time.
$ kubectl get pods -n istio-system
NAME                                    READY   STATUS    RESTARTS   AGE
grafana-b54bb57b9-8k9ml                 1/1     Running   0          4m22s
istio-egressgateway-77c7d594c5-wbgmp    1/1     Running   0          4m25s
istio-ingressgateway-766c84dfdc-pbvnl   1/1     Running   0          4m25s
istio-tracing-9dd6c4f7c-fmbb9           1/1     Running   0          4m22s
istiod-7b69ff6f8c-49gh2                 1/1     Running   0          4m30s
kiali-d45468dc4-8xstf                   0/1     Running   0          4m22s
prometheus-5fdfc44fb7-gplg8             2/2     Running   0          4m22s

I have the same issue with Istio 1.6.4. Config is targetAverageValue: 400m

Error: 1 error occurred:
* IstioOperator/istio-system/: could not unmarshal: json: cannot unmarshal string into Go value of type map[string]json.RawMessage

I also get the same error when passing whole core value to cpu, e.g. cpu: 1. Instead I have to pass it with an unit cpu: 1000m

Could you try it with quotes around ""?
@ostromart I think the issue may be that Kube's marshalling relies on strings being wrapped in quotation marks. This isn't always true in YAML. I have a fix for a similar issue we had internally, do you want me to add something similar in the API repo?
func (intstrpb *IntOrString) UnmarshalJSONPB(_ *jsonpb.Unmarshaler, value []byte) error {
	// If its a string that isnt wrapped in quotes add them to appease kubernetes unmarshal
	if _, err := strconv.Atoi(string(value)); err != nil && len(value) > 0 && value[0] != '"' {
		value = append([]byte{'"'}, value...)
		value = append(value, '"')
	}
	return intstrpb.UnmarshalJSON(value)
}

Quotes fixed the first case cpu: "1", but the average value problem persists.


Version selector not yet showing on readthedocs?

This is an awesome theme, thanks a lot! Can you comment on the version selector support? It seems like it is implemented, but when rendering on readthedocs, it is not displayed currently.

Hi Johannes! Indeed, no selector is available from the current version of the docs. As a temporary workaround, older versions of the Snakemake documentation can be found here:
https://readthedocs.org/projects/snakemake/

This theme is not ready for reuse yet, please don't try using it for now.

It works pretty well for our use case, and I am happy to contribute fixes. It is also fine if you just give me a pointer and I will try to fix it myself.

Well, I have found an alternative theme that works as well and is similar in terms of the optical properties (sphinxawesome-theme). We will use that for now. Nevertheless congrats for the great work here and I will keep an eye on it for maybe switching to it in the future!


Appstudio update test-component-pac-umbq

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-umbq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
appstudio-init

✅ Succeeded
24 seconds
clone-repository

✅ Succeeded
15 seconds
appstudio-configure-build

✅ Succeeded
36 seconds
build-container

✅ Succeeded
20 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
2 minutes
clair-scan

✅ Succeeded
50 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
10 seconds
sanity-optional-label-check

✅ Succeeded
9 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-umbq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
appstudio-init

✅ Succeeded
24 seconds
clone-repository

✅ Succeeded
15 seconds
appstudio-configure-build

✅ Succeeded
36 seconds
build-container

✅ Succeeded
20 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
2 minutes
clair-scan

✅ Succeeded
50 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
10 seconds
sanity-optional-label-check

✅ Succeeded
9 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-umbq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
appstudio-init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
17 seconds
appstudio-configure-build

✅ Succeeded
36 seconds
build-container

✅ Succeeded
1 minute
deprecated-base-image-check

✅ Succeeded
11 seconds
sanity-inspect-image

✅ Succeeded
42 seconds
clamav-scan

✅ Succeeded
10 seconds
clair-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
10 seconds
sanity-optional-label-check

✅ Succeeded
11 seconds
sanity-label-check

✅ Succeeded
7 seconds
show-summary


.beadignore instead of temp/ folder

To bead save large and complex folders, it would be important to flexibly set which files to ignore. Currently, only files inside temp/ are ignored.
Introduce a .beadignore file with the same syntax as .gitignore to set ignore patterns. (This could live inside .bead-meta, but keeping it in root would be more similar to the git model.)
bead new could create a .beadignore with only temp/ in it. This way the default behavior would remain the same, but advanced users could customize.

I like the backward compatible implementation proposal, but I do not see your use case.
bead's main purpose is to approximate reproducibility of computations.  Reproducibility is approximated via transparency: by capturing as much as possible from inputs, code/documentation, and outputs of the computation.  Ignoring some files work against this transparency, so it is discouraged.  However using temporary files during computations is sometimes very convenient, therefore one explicit directory - temp - is there whose content is ignored. I would not like to widen the blind spot temp already made possible, unless it is really necessary.
bead is intended to capture simple computations - data transformations/merges/calculations.
Where simple means, that program code is maximum 100-200 lines, and there is human manageable (< 7) number of input sources, and only a couple of outputs.
While nothing prevents more code/complex structures, they will cause problems - I propose to separate the complex ones to smaller component beads.
If the computation is really complex and it is very hard to split up, I am sure it is a bad idea to selectively hide some parts of it from the future.
I am willing to reopen this ticket if you have a problem still in scope:reproducibility, that I have not covered above.


fixes issue #110

 Please review it

@geetika005 can you please add a little bit of left margin

Is it ok now

Please put a screenshot

Great work :) @geetika005


Add check for writable when copying the CNI

This prevents the daemon from erroring out when running on RHCOS (e.g. /opt is not writeable)

/cc @bn222

/override ci/prow/e2e-dpu-operator-tests

/lgtm


co.chatsdk.core.handlers.PushHandler co.chatsdk.core.base.BaseNetworkAdapter.push' on a null object reference

Is the bug present in the demo Chat SDK project?

What modifications have you made to the Chat SDK? Noting

Android Version: Android 6, Android 7

Steps taken to reproduce the problem:

Expected result:

Actual result:

Comments:

There are lot of crashes reported in firebase console.
Fatal Exception: java.lang.RuntimeException
Unable to start receiver co.chatsdk.core.push.DefaultBroadcastReceiver: java.lang.NullPointerException: Attempt to read from field 'co.chatsdk.core.handlers.PushHandler co.chatsdk.core.base.BaseNetworkAdapter.push' on a null object reference
Fatal Exception: java.lang.RuntimeException: Unable to start receiver co.chatsdk.core.push.DefaultBroadcastReceiver: java.lang.NullPointerException: Attempt to read from field 'co.chatsdk.core.handlers.PushHandler co.chatsdk.core.base.BaseNetworkAdapter.push' on a null object reference
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2917)
at android.app.ActivityThread.-wrap14(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1565)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5728)
at

java.lang.reflect.Method.invoke(Method.java)

   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)

Caused by java.lang.NullPointerException
Attempt to read from field 'co.chatsdk.core.handlers.PushHandler co.chatsdk.core.base.BaseNetworkAdapter.push' on a null object reference
Caused by java.lang.NullPointerException: Attempt to read from field 'co.chatsdk.core.handlers.PushHandler co.chatsdk.core.base.BaseNetworkAdapter.push' on a null object reference
at co.chatsdk.core.session.ChatSDK.push(ChatSDK.java:226)
at co.chatsdk.core.push.DefaultBroadcastReceiver.onReceive(DefaultBroadcastReceiver.java:16)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2910)
at android.app.ActivityThread.-wrap14(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1565)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5728)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
What is causing this issue, any would be really appreciated

@bensmiley

@bensmiley

@mwaqassatti you need to have a push handler enabled. The reason why you are getting an issue is because it's not setup.

@mwaqassatti you need to have a push handler enabled. The reason why you are getting an issue is because it's not setup.

.addModule(FirebasePushModule.shared())

.addModule(FirebasePushModule.shared())

@bensmiley Thanks for your quick response. But what's minimum version to use .addModule()?
Currently we are using FirebasePushModule.activate() by using version 4.8.9.

@bensmiley Thanks for your quick response. But what's minimum version to use .addModule()?
Currently we are using FirebasePushModule.activate() by using version 4.8.9.


eks-distro-base: split al22 presubmits into job for each image

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


show project download info at UI

What type of PR is this?
show project download info at UI
What does does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #3508
How to test changes / Special notes to the reviewer:
odo create  --starter nodejs

/retest
/approve

Also, the output seems incorrect? The URL is straight from GitHub's CDN rather than the actual repo which would be: https://github.com/odo-devfiles/nodejs-ex
~/openshift/f3
▶ odo create --starter nodejs
Experimental mode is enabled, use at your own risk

Validation
 ✓  Checking devfile existence [155676ns]
 ✓  Checking devfile compatibility [452063ns]
 ✓  Creating a devfile component from registry: DefaultDevfileRegistry [323241ns]
 ✓  Validating devfile component [357302ns]
Project
 ✓  Downloading project from https://codeload.github.com/odo-devfiles/nodejs-ex/legacy.zip/master [294ms]

Please use `odo push` command to create the component with source deployed

Also, the output seems incorrect? The URL is straight from GitHub's CDN rather than the actual repo which would be: https://github.com/odo-devfiles/nodejs-ex
~/openshift/f3
▶ odo create --starter nodejs
Experimental mode is enabled, use at your own risk

Validation
 ✓  Checking devfile existence [155676ns]
 ✓  Checking devfile compatibility [452063ns]
 ✓  Creating a devfile component from registry: DefaultDevfileRegistry [323241ns]
 ✓  Validating devfile component [357302ns]
Project
 ✓  Downloading project from https://codeload.github.com/odo-devfiles/nodejs-ex/legacy.zip/master [294ms]

Please use `odo push` command to create the component with source deployed

will use a follow up to check why this is using legacy code ..

ping @cdrage can you help to check above comment? THanks

Hey @jichenjc the preference would be the GitHub repo URL / name. Having the CDN / zip file location I think would be a bad idea.

Hey @jichenjc the preference would be the GitHub repo URL / name. Having the CDN / zip file location I think would be a bad idea.

works for me :)

]$ odo create --starter nodejs
Experimental mode is enabled, use at your own risk

Validation
 ✓  Creating a devfile component from devfile path: /home/jichen/t/devfile.yaml [88426ns]
 ✓  Validating devfile component [112528ns]

Project
 ✓  Downloading project from https://github.com/odo-devfiles/nodejs-ex.git [497ms]

Please use `odo push` command to create the component with source deployed

@cdrage updated to this , thanks for your comments

/test v4.5-integration-e2e

/test v4.5-integration-e2e

ping @cdrage ,can you help another review? Thanks


As the title says. Is this intentional or is it a bug?

Messages you send are private to your browser. I don't think it is a bug

Sending messages doesn't require browser information. Only reading does.
Imo this seems counterintuitive.  End-to-end messaging should relay solely on the keys.

Unfortunately this is by design. When you send a message you encrypt it with the other user's public key so only they can read it.

It makes sense, my node sent this message using the /api/v0/send-message-stateless endpoint. But why wouldn't the recipient be able to decrypt it? The message is already associated with his public key.
I can send you more screenshots if you want. Interestingly, some people can read these messages and some can't.
(@maebeam sorry for the tag)


Add Update Command

Add yard update . which will update all remotes in the yard.yaml file to their latest commit and validate/print if any module paths are no longer found.

Implemented in https://github.com/mcmah309/containeryard/commit/a09944787e7adbed45caf080090ab4802808a87c


[FLINK-7933][metrics] Improve PrometheusReporter tests

What is the purpose of the change
This PR resolves the test instabilities of the prometheus reporter.
Brief change log

use a port range instead of a single hard-coded port

required the exposure of the bound port by the reporter

move registry/reporter initialization into an @Before method (guarantees execution order)
shutdown registry in PrometheusReporterTest

Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Thanks, looks good, +1 to merge


Add support for timeout option

Based on #328 and #411.
Unfortunately it seems that php-ssh doesn't support timeout - Herzult/php-ssh#46

Cool! Need to code review and test it.
@deployphp/maintainer please, help!

Cool!
I think it is better if support:
localServer($name, $timeout = 300);
// and
server($name, $host, $port = 22, $timeout =300);

@oanhnn Well, I made it like this because @elfet said that it would be better (https://github.com/deployphp/deployer/pull/328#discussion_r32095173). If I understand correctly

@elfet What do you think?
@davidkudera Can you write docs and create a PR to https://github.com/deployphp/docs

@oanhnn sure, I'll do that right after you'll decide which version is better (method or argument)

@elfet Do you decide which version is better (method or argument).
server(...)
    ->timeout(300)

or
server('dev', <IP_ADDRESS>, 22, 300)

or both :smile:

I dont think what is good to setup this server wide. Its better to specify timeout on run:
run(‘…’, 360);

@elfet yes that is only logical since runLocally also has it. Actually I was thinking about it too, but I didn't want to do that in my first PR because it worked just for local server and it would mean to change implementation of ServerInterface. Also I made just the changes mentioned in the second PR.
But what if we'll change ServerInterface::run() but keep global server configuration too? If user provide second argument at run method, we'll use that, othervise we'll use value from server configuration. And for people using ssh we can throw some NotImplementedException for example.
What do you think?

I think global config here is bad decision.

Ok, so should I change it? @elfet @oanhnn

I think yes :)

@elfet ok, I'll force push these changes. Unfortunately right now I don't have time, but I should be back home maybe at sunday

@elfet @oanhnn what do you think now guys?

ping @elfet @oanhnn

rebased to master

Timeout is not supported in ssh connection.

WE really need to figure out how to implement this in ssh2 ext. Otherwise timeout with be really strange functionality.

Yeah, but do we know if ssh2 is still developed? Last commit was 5 months ago..

@elfet , @davidkudera SSH wrapper library use stream blocking. It's easy to refactor code to imlement not blocking implementation with callback:
https://github.com/Herzult/php-ssh/blob/d569d15483a5f9218700313cd21c50090aa93351/src/Ssh/Exec.php#L26
But I'm still wonder about use cases of this timeout. @davidkudera can you please provide some examples of use cases? Specialy for me. I'm just curious.

Or another idea is to wrap command with some shell timeout function.
Windows: http://stackoverflow.com/questions/12394338/windows-batch-analogue-for-timeout-command
Linux: http://man7.org/linux/man-pages/man1/timeout.1.html
Without any magic :)

@torinaki sure, for example we were developing new version of our website for more than half of a year (without touching 1st version). My deploy process failed almost immediatelly - to be more specific at database migrations. On my PC with linux it runs for about 15 minutes and I wasn't even brave enough to try it on Windows :grinning:

@davidkudera for what exact task you suppose to use timeout? Database migrations?

Yes, for now only for database migrations, but maybe there will be some other tasks too.

I just noticed that this PR is still open. Is there anything I can do now to make it merged?
The problem with SSH is unfortunate but I think that the solution proposed in this PR is still much better than the current state of deployer.

Ok, i'll test this PR to merge. Need some time.

Still open, @elfet When does it get merged?

@elfet from my point of view it is important that following comment should be addressed before merge:
https://github.com/deployphp/deployer/pull/415#discussion_r37126085
otherwise deployer will silently stop task in case when it wil reaches timeout.

+1


Use emptyDir for Temporal configuration mount path

What was changed
This change codifies the suggestion in the following issue/comment:
https://github.com/temporalio/helm-charts/issues/225#issuecomment-932263282
Using an empty directory here is a chart/app version agnostic fix.
Why?
Details in https://github.com/temporalio/helm-charts/issues/225.
Checklist

Closes #225

How was this tested: we're using a custom version of the Helm chart with this change and it behaves as expected.

Any docs updates needed? Unlikely, this should be expected behavior.

appreciate the contrib and appears that @krousey solved it upstream. pls reopen if mistaken.


All Raids Wireframe

Creating the wireframe for the "All Raids" screen
https://www.figma.com/file/oOFsQ2ecdyYjnK91yOKPDR/Raid-Guild-Site-Planning?node-id=27%3A0

If you sign-up for a Figma account, you can view much more information than anonymous mode.

If you sign-up for a Figma account, you can view much more information than anonymous mode.

Wireframe should be done now

Wireframe should be done now


Question about retriever..

A silly question about the retriever part:
I was trying to index the Wikipedia dump in paragraph-level as you did. And in the paper, you mentioned that you got 29.5M paragraphs, but instead I got 33.3M paragraphs. So, I would like to ask if you did some special filter setting when you split the article into paragraphs or just easily split them by article.split("\n")
Thanks

Hi, we use "\n\n"to split the paragraphs. And we use 2016-12-21 Wikipedia dump and follow the preprocess here.

Hi, we use "\n\n"to split the paragraphs. And we use 2016-12-21 Wikipedia dump and follow the preprocess here.

Exactly what I am looking for. Thanks a lot.


Merge import

This branch adds a new dialog to import and merge piskel or image files in the current piskel.
It replaces the current "image import" dialog.
It is triggered when trying to import either an image or a piskel file.
For now, opening a local save or restoring a previous session does not trigger the merge UI.

This change is

Should at least select one of the newly created layers after the merge.


Create Gift screens updation

A user is creating a gift (not the satscard flow). If he creates one gift, the button should be "Create Gift". But in case he goes into Advanced option, selects multiple gifts, and comes back to the create gift tab, the button should change to "Create Gifts" (Gift to Gifts - Plural)

The "I have a satscard" button should go away if the user has selected multiple gifts.

Resolved

Completed


Add opensearch promotion workflow and jenkins libs for tar

Signed-off-by: Peter Zhu<EMAIL_ADDRESS>Description
Add opensearch promotion workflow and jenkins libs for tar
Issues Resolved
#1332
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1354 (cfc4ce1) into main (ea5a964) will decrease coverage by 19.94%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main    #1354       +/-   ##
=============================================
- Coverage     94.02%   74.07%   -19.95%
  Complexity       11       11
=============================================
  Files           136       17      -119
  Lines          3011       81     -2930
  Branches          8        8
=============================================
- Hits           2831       60     -2771
+ Misses          172       13      -159
  Partials          8        8

Impacted Files
Coverage Δ

src/test_workflow/test_recorder/test_recorder.py

src/manifests/build_manifest.py

src/ci_workflow/ci_input_manifest.py

src/build_workflow/build_target.py

src/test_workflow/dependency_installer.py

.../ci_workflow/ci_check_gradle_properties_version.py

...orkflow/ci_check_gradle_dependencies_opensearch.py

src/manifests_workflow/component.py

...orkflow/integ_test/integ_test_runner_opensearch.py

src/ci_workflow/ci_target.py

... and 109 more

Continue to review full report at Codecov.

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

Add a test for the new function in vars and this looks good to me.

@dblock @peternied @gaiksaya here is the improvement issue for this task: https://github.com/opensearch-project/opensearch-build/issues/1355
Please review again so we can unblock this and merge.
Thanks.


[now dev] Send the NO_STATUS_CODE_FROM_LAMBDA upon lambda error

Codecov Report

Merging #2037 into canary will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           canary   #2037      +/-   ##
=========================================
- Coverage    6.18%   6.15%   -0.04%
=========================================
  Files          86      86
  Lines        4072    4079       +7
=========================================
- Hits          252     251       -1
- Misses       3820    3828       +8

Impacted Files
Coverage Δ

src/util/get-project-name.js
90.9% <0%> (-9.1%)
:arrow_down:

src/util/get-files.js
91.53% <0%> (-5.37%)
:arrow_down:

src/util/read-metadata.js
100% <0%> (ø)
:arrow_up:

src/util/hash.js
100% <0%> (ø)
:arrow_up:

src/util/error.js
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Can you add a test for this?


Update Klaxon for compatibility with gradle 7.x

When updating the build to gradle 7.x I get the following error:  Could not find com.beust:klaxon:5.2.
It seems to be related to the deprecation of jcenter repository. The availability of the klaxon library in plugins.gradle.org starts with version 5.4. Could klaxon be updated to at least version 5.4?

Hey @sideisra thanks for bringing it up :) Could you test version 0.0.62?

@klg71 I don't see a version 0.0.62. The latest version seems to be 0.0.61,

Sry typo its the  0.0.61

Does version 0.0.61 need java 17?

It is build with java 17 but I did hope it would work with lower versions too.


Unable to finetune the model ->llama-2-7bn-hf with the dataset of format (prompt,instruction,input, response)

Following error keeps popping up.. Please help immediately..
......

ERROR   train has failed due to an exception:
ERROR   Traceback (most recent call last):
File "/opt/conda/lib/python3.8/site-packages/autotrain/utils.py", line 280, in wrapper
return func(*args, **kwargs)
File "/opt/conda/lib/python3.8/site-packages/autotrain/trainers/clm/main.py", line 304, in train
trainer.train()
File "/opt/conda/lib/python3.8/site-packages/transformers/trainer.py", line 1591, in train
return inner_training_loop(
File "/opt/conda/lib/python3.8/site-packages/transformers/trainer.py", line 1870, in _inner_training_loop
for step, inputs in enumerate(epoch_iterator):
File "/opt/conda/lib/python3.8/site-packages/accelerate/data_loader.py", line 560, in iter
next_batch, next_batch_info = self._fetch_batches(main_iterator)
File "/opt/conda/lib/python3.8/site-packages/accelerate/data_loader.py", line 523, in _fetch_batches
batches.append(next(iterator))
File "/opt/conda/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 633, in next
data = self._next_data()
File "/opt/conda/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 677, in _next_data
data = self._dataset_fetcher.fetch(index)  # may raise StopIteration
File "/opt/conda/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 32, in fetch
data.append(next(self.dataset_iter))
File "/opt/conda/lib/python3.8/site-packages/trl/trainer/utils.py", line 482, in iter
buffer.append(self.formatting_func(next(iterator)))
File "/opt/conda/lib/python3.8/site-packages/trl/trainer/utils.py", line 458, in
self.formatting_func = lambda x: x[dataset_text_field]
KeyError: 'text'

.....

It needs to be in the alpaca format to work (if you're training llama2)

Yes, the data is format into alpaca format and feeded to model for finetuning.. I see the same key error raised by other as well, in the issues repo.
Please help..

does the data format change for others models, e.g. Mistral?

You have to go to HuggingFace and check out the Mistral model page and then check out the Dataset it was trained on. Once there you will see where you can check the format of the dataset itself. Then you can format your dataset just like it. Also, autotrain is not that great imo. I have not gotten it to work properly on Colab and the cost to do it on the platform can get quite costly. But that's just my opinion

@KabaTubare What's better in your opinion?

here is a sample dataset: https://huggingface.co/datasets/timdettmers/openassistant-guanaco. the problem is probably you didnt specify --text-column manually and it fell back to text as default column. Having the dataset in the format specified above wont cause any issues.


Publish 03/18/2022, 10:30 AM

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

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteSwap.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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


"Dobrin" , "Deleni" , "Doba" , "Naimon" , "Sâncraiu Silvaniei" , "Verveghiu" are listed in the drop-down menu

Description:
When user writes "Dobrin" , "Deleni" , "Doba" , "Naimon" , "Sâncraiu Silvaniei" , "Verveghiu" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Dobrin"

Expected results
The location appears in the drop-down menu as "Sat Dobrin, SĂLAJ (Dobrin)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Deleni"

Expected results
The location appears in the drop-down menu as "Sat Deleni, SĂLAJ (Dobrin)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Doba"

Expected results
The location appears in the drop-down menu as "Sat Doba, SĂLAJ (Dobrin)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Naimon"

Expected results
The location appears in the drop-down menu as "Sat Naimon, SĂLAJ (Dobrin)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Write in the search bar "Sâncraiu Silvaniei"

Expected results
The location appears in the drop-down menu as "Sat Sâncraiu Silvaniei, SĂLAJ (Dobrin)".

Step 11
Write in the search bar "Verveghiu"

Expected results
The location appears in the drop-down menu as "Sat Verveghiu, SĂLAJ (Dobrin)".


feat: export mods

Signed-off-by: MrCroxx<EMAIL_ADDRESS>

Codecov Report

Merging #37 (f1aad1e) into main (ad3f125) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #37   +/-   ##
=======================================
  Coverage   41.02%   41.02%
=======================================
  Files          33       33
  Lines        3481     3481
=======================================
  Hits         1428     1428
  Misses       2053     2053

Impacted Files
Coverage Δ

foyer/src/lib.rs
25.00% <ø> (ø)


Make Clients as dynamic in strapi

Make Clients as dynamic in strapi

Completed the development and deployed on server, then it is working as expected.


Demo project missing Maven binaries

Describe the bug
According to Getting started with the Firely SDK CQL repository, building the Demo project is all that is necessary to get going.  In particular, a full install of Maven should be present in the repository, and there is a build task called Download CQL to ELM CLI via Maven.
However, the bin folder in the path Demo\Cql\Build\apache-maven-3.8.8\bin\mvn of the build task is not present in the repo.  So upon attempting to build, the following error occurs:

To Reproduce
Confirm the Build\apache-maven-3.8.8\bin folder is missing in the repo.
Expected behavior
Add the bin folder to the repo so that a build error does not occur.
Alternatively, list Java (the build task already implicitly assumes java is installed with a correct %PATH%) and Maven as external prerequisites and change the build task to use mvn relying on the %PATH% having been set in the user's operating system.  In other words,

Change <Exec Command="Build\apache-maven-3.8.8\bin\mvn -f Build\pom.xml dependency:copy-dependencies"></Exec> to <Exec Command="mvn -f Build\pom.xml dependency:copy-dependencies"></Exec>
Remove the Demo\Cql\Build\apache-maven-3.8.8 folder and rely on the user to install Maven correctly with %PATH% already set.

Just read through #61 and looks like same root cause as first bullet in that issue.
However, in my case, I am using a Windows machine.

Yes, this stuff was not checked into the repo in the end due to the git config ;-)

And it's a pain to get to work on a Mac.

Fixed in #86.
But not the slashes.

We'll pick the rest up in #61.