Is lazy loading supported

You could load data by ajax on a trigger as you like (scroll, dom loaded, ...) and on data loaded you could init treesize.

Close as inactive. A not popular feature, we can use a workaround to use lazy loading.


Grouping

Please implement prompt grouping. Since the thread yeilded only ignorance, I am making an issue.
Desired syntax:
{cat, blue fur} {dog, red fur, wearing a golden collar}

or
{cat, blue fur; dog, red fur, wearing a golden collar}

Named groups would also be great:
{cat: cat, blue fur} {dog: dog, red fur, wearing a golden collar}, hairless {&cat}, {&dog} wearing a cap

is this feature in? @adieyal

please respond, is this feature in or not yet?


release as v2.0.1

bump version
update dist file

@neraliu/@albertyu, please review and merge. thx


Sparkle maintenance failed due to unknown datetime string format (MMM/DD/YYY)

Frankly, I'm not entirely sure if this classifies as bug or feature request.
Sparkle started sending us maintenance notifications with this datetime format: MMM/DD/YYYY HH:mm UTC. For example: Jan/27/2023 03:00 UTC.
Currently circuit-maintenance-parser doesn't support this format and it's not a common/standard format. However, it can very much be parsed:
Python 3.10.9 (main, Dec 15 2022, 17:11:09) [Clang 14.0.0 (clang-14<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import arrow
>>> a = "Jan/27/2023 03:00 UTC"
>>> arrow.get(a)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/tdo/Documents/dev/MNA/lib/python3.10/site-packages/arrow/api.py", line 91, in get
    return _factory.get(*args, **kwargs)
  File "/Users/tdo/Documents/dev/MNA/lib/python3.10/site-packages/arrow/factory.py", line 254, in get
    dt = parser.DateTimeParser(locale).parse_iso(arg, normalize_whitespace)
  File "/Users/tdo/Documents/dev/MNA/lib/python3.10/site-packages/arrow/parser.py", line 208, in parse_iso
    raise ParserError(
arrow.parser.ParserError: Expected an ISO 8601-like string, but was given 'Jan/27/2023 03:00 UTC'. Try passing in a format string to resolve this.
>>> arrow.get(a, 'MMM/DD/YYYY HH:mm UTC')
<Arrow [2023-01-27T03:00:00+00:00]>

Environment

Python version: 3.8
circuit_maintenance_parser version: 2.2.2

Expected Behavior
We expected a successfully parsed Maintenance object.
Observed Behavior
We get an error as shown here:
(CMP) tdo@PlayStation [16:02:13] [~]
-> % circuit-maintenance-parser --data-file ~/Downloads/NETENG-22869.eml --data-type email --provider-type sparkle
Provider processing failed: Failed creating Maintenance notification for Sparkle.
Details:
- Processor CombinedProcessor from Sparkle failed due to: Unknown string format: Jan/27/202303:00 UTC

Steps to Reproduce

unzip sparkle-email.zip
circuit-maintenance-parser --data-file /path/to/sparkle.eml --data-type email --provider-type sparkle

@chadell just a quick follow up to see if there's any traction with this issue?

Hi @csessh , I have not seen any PR for it yet, but as I see you already have a workaround, could you contribute it back?


compatible with the timestamp

Please make sure these boxes are checked before submitting your PR, thank you!
#10433

Why is this change necessary. Time panel will never get non Date or non-null/undefined value

If your backend uses timestamp, you should use value-format='timestamp'.


Update @context URLs, add response contentType workaround

This PR updates the @context URLs included in the directory's TM/TD in anticipation of https://github.com/w3c/wot-discovery/pull/471 and applies the workaround added in https://github.com/w3c/wot-discovery/pull/469 to the ThingDescriptionBuilderService by inserting application/x-empty as a contentType for response objects where the field absent.
Combined, these changes result in a TD for the Directory that passes validation against the latest JSON Schema document provided in the TD repository :)

Needed to update two dependencies and create another workaround in 8f0b128 to get the TD instantiation to actually work again. Seems to me like a bug has appeared in the td-tools package that modifies the input TM, which apparently has not happened before 🤔

Hi Cristiano, thank you for the feedback! Sure, I will check again and try to narrow down the changes :)

With the latest push, I managed to trim down the changes in the package-lock.json a lot. However, for some reason, the tests are now failing since the td-tools apparently does not include the latest fixes for the TM JSON schema 🤔 We may need to put this PR on hold then until version 0.8.6 of the td-tools package with the updated schema has been released.

Ok, in my understanding we are going to release 0.8.6 very soon. I'll check if we get the green light once it will be published!

The new td-tools release actually solved the problem 🎉

I am now wondering: Should we wait for https://github.com/w3c/wot-discovery/pull/471? Or would it be fine to already merge this PR?

Talked offline with @hyperloris, he was a little bit uncomfortable with merging a PR with TODOs in it. I agree but those TODOs are reasonable and they can be tracked in issues (as suggested by @hyperloris  himself). Therefore, I'm forcing the merging of the PR without waiting for his formal approval. Later on, I'll open the tracking issues.


Account and IP forwarding compatibility fixes.

Default interface should be the value of dev.
User should be the last parameter of user account commands.
All files created should have restorecon run on them.

LGTM


Eliminate the need to write :host ::content instead of just ::content

While keeping the same processing under the hood.
I've also removed workaround from tests and they don't fail, which is good.

Thanks for the PR - apologies for the delay on feedback. To make it a little easier to discuss the impetus and reasoning behind the change, would you be able to create an issue that goes over the reasoning and then link to it from this PR?

It was already created and linked back: https://github.com/Polymer/polymer/issues/1727

Just rebased this against master to resolve conflicts and did some small improvements.
Merge this small fix soon, please. It is almost 2 months old already.

Rebased against master once again. Really simple fix, sad to see it is not merged months later :-1:

LGTM. Sorry for the delay and thanks for the effort!


JS clipboard button

Introduce buttons like on 1339.cf

notes:
https://hacks.mozilla.org/2015/09/flash-free-clipboard-for-the-web/
http://stackoverflow.com/a/30810322

^implemented with @alucard0134's permission :stuck_out_tongue:

added in 4a869e4e0e1368baf5aa4e1a4144e0d31f633782


Update arrow icons in code snippets

Currently the arrows for expanding a code snippet in the UI are v for unexpanded and ^ for expanded. This usage matches the UX for opening and closing an expandable section, as we do in our error dialog, because the down arrow says "click for more info" and the up arrow says "hide more info." For code snippets the expanded section is more like subsection. As such it would make more sense for unexpanded content to use > and expanded content to use v this would match how the git extension handled its expandable sections.

I'm interested in working on this, if no one else is.

go ahead, it's a small change, should just be updating the css vars to use the different direction arrows from lab.

Looks like we should wait till the jupyterlab 2.0 code is merged in as it is very different to do the icons compared to copying in new ones now and code-snippets isn't in that branch currently. Also found that the error dialog has the icons in the wrong way to, so we can fix those up at the same time too.

@kjdoyle @ajbozarth if i am not mistaken, i believe this has just been addressed in https://github.com/elyra-ai/elyra/pull/439

@vabarbosa yep I snuck it in there while I was already having to update the arrow vars. I will be updating it further in #443 when I update code snippets to use LabIcons. So we can close this after either one is merged


[Feature request] vuepress-plugin-demo-code > vuepress next support version update

Feature request
vuepress-plugin-demo-code > vuepress next version update.
Description
vuepress-plugin-demo-code > vuepress next version update.
now vuepress-plugin-demo-code      "vuepress": "^1.8.2" dependency
we need vuepress next dependency update
Proposed Solution
Only one source code
Foldable code
Support online editing
✔ Codepen
✔ JSFiddle
✔ CodeSandbox
Designed for long code
Sticky fold button
Auto scroll to top when you fold code

https://github.com/BuptStEve/vuepress-plugin-demo-code

becauseI want vuepress next support


Build docker build image for c3.11.13 / c4.0.4

What this PR does:
Rebuilds Docker build image needed by Stargate GCB CI.
Which issue(s) this PR fixes:
Last part of #1920
Checklist

[x] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[x] CLA Signed: DataStax CLA

Having some issues with Docker build, hoping to resolve today.

/gcbrun

Need to wait for runs to complete but images exist and hoping this can be merged soon.


Add Calamares: A distribution independent installer framework.

The PR adapts boost lib as well, so it probably expensive to merge.

The idea is to maybe build a graphical installer for NixOS with calamares.

The PR builds locally for me, and the changes to boost lib should be fairly easy to verify.

@copumpkin, thanks for the review! I've updated boost lib accordingly.

@copumpkin, could you maybe have another look at that PR, please?

@copumpkin, could you maybe have a look at this PR again, please? Or, should I ask someone else to merge the PR? I just don't want the PR to be forgotten. Many thanks!

I assume if updating Boost will cause an expensive rebuild, we should put it into staging.

Given that manu boost updates break some packages, adding a new version in master as non-default is a reasonable option.
-------- Original Message --------
From: Austin Seipp<EMAIL_ADDRESS>Sent: March 11, 2015 10:17:28 PM EET
To: NixOS/nixpkgs<EMAIL_ADDRESS>Subject: Re: [nixpkgs] Add Calamares: A distribution independent installer framework. (#6285)
I assume if updating Boost will cause an expensive rebuild, we should put it into staging.

Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/6285#issuecomment-78349684

@thoughtpolice, does that mean I have to open a PR against the staging branch?
@7c6f434c, I don't expect the change to break any packages. Either, they use python2 so far, in which case the change is transparent, or they use python3, in which case boost doesn't compile so far.


Handle unavailable and deprecated symbols in code-completion

What's in this pull request?

This merge fixes two issues in Swift3, both covered by rdar://problem/26335424.

Unavailable symbols incorrectly show up in unresolved-member code-completions like "foo(.)"
Deprecated symbols are not being marked "not recommended"

These are particularly egregious after API renaming, where we end up showing both the old names, the new names, and sometimes also a deprecated old name.
Resolved bug number: (SR-)

rdar://problem/26335424

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci test

@swift-ci smoke test os x platform

@swift-ci test


Feature Request/ Implementation question| hooking driver creation method

Feature Request
I'm looking for a guidelines or help implementing retry mechanism for driver creation.
It's really useful and important for testing remote real devices while retrieve one from a pool of devices.

Reasons for adopting new feature:
Remote testing could fail sometimes when trying to retrieve a device because the device already in use or unavailable.
I would like to prevent this by retry in X sec later or by getting a different device.

Is this a breaking change? (How will this affect existing functionality)
Not sure.

Could you flesh out what this might look like with some pseudocode? I'm not familiar with remote device testing

Hi @NickTomlin,
What @daniel4x means is the following. Some cloudproviders don't have automatic queueing like Sauce Labs has. For example, you request 10 instances of Chrome, you only have 5, so 5 are queued.
Cloudproviders like for example Perfecto (who has physical devices and browsers) can't queue. The will give back a "error"-message saying that the driver could not be created because they are (all) busy.
In protractor we can't "hook" onto the instantiation of the driver with (get)multi-capabilities. It would be nice that the "error"/"info"-message could be processed with a custom script with some kind of hook or something, like this:
// calling with
multicapabilities:[{
        browserName:chrome
    }, {
        browserName: firefox
}],

// when error message of driver
onDriverError: (message){
    // process the message and trigger the driver start again for x times, this can be done by the script
    // user is responsible of handling the amount of retries and so on
}

Hope this makes is more clear.
Grtz
Wim

Hi @NickTomlin
Did you had time to check this?

I think this seems like a valid use case; I personally won't be able to get to it but i'd welcome a PR.
I'm trying to think of the best way to handle this, do you have an example integration with perfecto? It seems like it might be something that best fits into an additional method for a driver provider that could negotiate this on behalf of the user (I'm open to exposing this via the root config if necessary as well).

Tnx @NickTomlin
@daniel4x will look at it and create a PR

@wswebcreation sure! Feel free to use this thread as a place to discuss options. Thanks!

Hi @NickTomlin,
@wswebcreation and I came up with an idea for implementation of this feature.
It requires from us to extend the driver creation logic and enable the driver creation async.
The selection between the different driver creation methods will be controlled from the Protractor configuration file. The actual creation logic will be extracted to a separate method that will be used for both scenarios (For preventing code duplication).
In addition to the above, we would like to add Perfecto as a connection partner, in order to provide perfecto users out of the box retry functionality which described before and some additional Perfecto functionalities such as connection to Perfecto reports.
Thanks!

@NickTomlin
Did you had some time for the questions of @daniel4x ?
Tnx in advance

@wswebcreation @daniel4x
Sounds great! Do you have branch with this I could look at? Or do you mind showing some code examples?
I think doing this in two parts would be excellent:

Pull request driver creation logic
Pull request Perfecto driver

Let me know if there's any additional questions. Thanks!

@NickTomlin
Tnx for the reply, we'll start working on it and keep you updated

@NickTomlin  Hey,
Please see the following pull request: https://github.com/angular/protractor/pull/4166
Added a async driver creation & retry mechanism.


Replace {} with any

Hey! I've got another bug in the TS typings that's waiting to be fixed. :)
{} does not represent a 'plain object' in TS. This leads to problems using state.router.result.someProperty, because TS asserts that someProperty doesn't exist, when in fact, it does. any is the right type to be used here.

Good catch @NeoLegends! I'd still like to make some sort of contract saying that these need to be objects. Perhaps we could use index signatures, similar to how we do with the Routes interface? Let me know your thoughts on this. Something like:
interface ObjLiteral {
    [key: string]: any;
}

I've never been truly certain on how to deal with objects of unknown shape in TS. any is a great escape hatch if we need it, but would like to use something a bit safer if possible. Thanks!

@NeoLegends this looks good to me, finally had some time to review and all seems to be going smoothly. Please pull latest from master into your branch and then push to this PR and I can merge. cc @ryan-roemer @tptee We can cut a patch release later this week to pull in these updated defs.

🚢

🤟🏻

@parkerziegler @ryan-roemer @tptee Any chance of getting this released, please?

Thanks for pinging us @davidgruar! Meant to cut another release after these got merged but forgot.
@ryan-roemer @tptee I'm happy to cut a new release later today, how do we want to do versioning (major/minor/patch). IIRC, the diff is just changes to TS defs.

@davidgruar v15.1.1 is published to npm. Let us know if you encounter anything funny!

Thank you! It would be worth mentioning #280 in the release notes - it resolves the same issue as #282 but for Typescript (and is actually what I most needed this release for).

Good call out, it's been added!


Added questions to deep learning and dojos

I have added questions to 2 files deep learning and dojos.
Please add “HACKTOBERFEST”  or  “HACKTOBERFEST-ACCEPTED” labels to the pr since i am participating in hacktoberfest

Hi @Divyansh200102  I will check very soon, thank you for your work


FileSystem list action truncates timezone from modification date/time

❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗
Describe the issue
When using a list action of a FileSystemPipe/Sender, timezone information is truncated. This can lead to wrong values/comparisons if the files are on a server with a different timezone compared to the application.
https://github.com/ibissource/iaf/blob/master/core/src/main/java/nl/nn/adapterframework/filesystem/FileSystemActor.java#L405
https://github.com/ibissource/iaf/blob/master/core/src/main/java/nl/nn/adapterframework/filesystem/FileSystemUtils.java#L348
FileSystemListener are not affected as those compare using ms since 1-1-1970.
Reporter
Ricardo

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Configuration
Please provide the configuration of the Pipe or Receiver with the problem.

Input
Please provide an example of the input message.
Alternatively, provide a Ladybug report.

Environment
Please go to the console of your Frank, click on 'Information' and copy-paste the results here.

Additional Environment

DBMS: [e.g. Oracle, MSSQL, MariaDB, MySql, PostgreSQL]
Browser: [e.g. Chrome, Safari, Edge, Firefox]

Additional Context
Add any other context about the problem here. (f.e. ladybug report / test adapter with larva test)

ModificationDate and Time are converted to server timezone, so no issue.


ARTEMIS-903 Add documentation for updating Artemis to newer versions

Currently there is no documentation about updating ActiveMQ Artemis in the Artemis user manual. This commit adds a brief description of the steps necessary to update Artemis to newer versions.

Happy new year, Clebert :)

Happy new year, Clebert :)

IMO the redundant information should be removed and the new information (i.e. the bit about changing the profile to point to the new version) should be added to a new section in the "Using the Server" chapter rather than creating an entire new chapter for 1 paragraph.
If that's not amenable then at the very least the redundant information needs to be removed, the chapter needs to be moved from the very bottom of the chapter list to immediately below "User the Server" so it's easy to find, and the two commits need to be squashed into one.


router flux not showing camera component

Version
Tell us which versions you are using:

react-native-router-flux v3.43
-react-native-camera v0.12
react-native v0.49.5

Expected behaviour
Open the camera when calling the component QrScanner
Actual behaviour
Showing a blank screen, I was able to tell it was my component because i've conditioned my render with some state variables
Steps to reproduce

new project, install router-flux and react-native camera
Create three components: Login, Menu and QrScanner
Routing:
from Login to Menu and from Menu to QrScanner

PS. I've tested rendering just the QrScanner component before installing router-flux and worked fine so I assume it's not an issue with the component.

You are using version 3.43, which is not supported.
Also, steps to reproduce are too generic. Without specific code example (like one created using https://snack.expo.io/) you will probably not get any help.


Identity - support for client certificates in formats other than PEM

When users wish to use the Identity SDK for Python in conjunction with Azure Batch, they need to implement extra logic to convert their certificate from .pfx/.cer to .pem. Can we add logic so that the Identity SDK supports other certificate formats innately?
Azure Batch documentation on certificates: https://docs.microsoft.com/en-us/azure/batch/batch-certificates
Suspected code where the current restriction for PEM-only certificates is implemented: https://github.com/Azure/azure-sdk-for-python/blob/eea845a56aa792f5b03b9188cd0180d42a3de4bb/sdk/identity/azure-identity/azure/identity/_internal/aadclient_certificate.py#L19
Python SDK reference describing the PEM-only restriction: https://azuresdkdocs.blob.core.windows.net/$web/python/azure-identity/1.4.0/index.html#environment-variables

Thanks for opening this issue. I've put it on our backlog until we decide where it could fit into our roadmap. Until then, if you're reading this and this feature is important to you, please +1 the top comment to help us prioritize.

@chlowell By when can we expect support for PKCS12 certs to be available in the azure-identity library

#16384 will be in 1.7.0b4, which we plan to release September 8


Support for Next.js 13 with experimental appDir enabled

As referenced in #194, if the experimental option appDir option is enabled on Next.js, it will break the editor, with the following error:

And on the console a lot of warnings including the one referenced on the other issue
If you disable the appDir option, the editor renders without the error
Here's a sandbox with the reproduction: https://codesandbox.io/p/sandbox/festive-dijkstra-z45mi4

Something went wrong.

Moved it to a repo: https://github.com/p13lgst/Easy-email-Next-13-appDir-bug

Sorry, we don't have much time to check this bug at the moment.

Perhaps rendering multiple HTML tags in the same page caused this error, which is not compliant with the standards. Wrapping EditEmailPreview with the react-frame-component package may resolve this issue.

Perhaps rendering multiple HTML tags in the same page caused this error, which is not compliant with the standards. Wrapping EditEmailPreview with the react-frame-component package may resolve this issue.

However, doing this requires passing down the new document and window objects, which might be a bit cumbersome.

@m-Ryan @p13lgst I am working on making the editor work with Next's new app directory, I removed the html tag(I changed to to <!DOCTYPE html>

 from here: https://github.com/zalify/easy-email/blob/27e6fcabe6bbe83b1ba00e19366261371463a98d/packages/easy-email-editor/src/components/UI/SyncScrollIframeComponent/index.tsx#L116
However, I still see the html tag in the preview? I am I editing the correct place?

Perhaps rendering multiple HTML tags in the same page caused this error, which is not compliant with the standards. Wrapping EditEmailPreview with the react-frame-component package may resolve this issue.

However, doing this requires passing down the new document and window objects, which might be a bit cumbersome.

Hello, do you have a working example?

@willopez Did you get it working on next js app dir ? i'm facing the same issue right now. I'd appreciate the help.

Any luck with this?


Max open files set to 1024

ulimit is not set on MySQL server, so they start with the default "Max open files" == 1024.
It's a problem when we try to use open_files_limit or innodb_open_files and set it to a higher limit.
EDIT
one could launch docker with --ulimit option. Maybe this could just be documented ?

Sorry for the super long tail. :bowing_man:
This is a general issue with running anything in a Docker container.  With the limited space for text on the Docker Hub, I'd rather not document general Docker issues on a specific image; the Docker Docs are fairly comprehensive and there is also the Docker Community Forums, the Docker Community Slack, or Stack Overflow.


Some links in the User Guide don't show up correctly

Section
How to Contribute to the Logging Roads Initiative
@BKessle  can you verify?

fixed


yaml in, yaml out?

So I have a simple decorator controller with a simple sync hook. Now I haven't messed with this in a while, but I swear you can do more than just attachments.
The goal is take a pod, and force resource limits.
---
apiVersion: v1
data:
  sync.py: |-
    from typing import Optional
    import logging
    import typing
    import json
    import copy
    from pprint import pformat

    from fastapi import FastAPI, Request
    from fastapi.encoders import jsonable_encoder
    from fastapi.responses import JSONResponse

    logging.basicConfig(level=logging.DEBUG)
    LOGGER = logging.getLogger(__name__)
    LOGGER.info("started")

    app = FastAPI()

    @app.api_route("/{anything:path}", methods=["GET", "POST"])
    async def catch_all(anything: str, request: Request):
        body = await request.json()
        pod = body['object']
        LOGGER.info({"Method": request.method,
                "URL": request.url,
                "Headers": dict(request.headers.items()),
                "Query Parameters": dict(request.query_params.items()),
                "Path Parameters": request.path_params,
                "Client": request.client.host})
        for i in range(0, len(body['object']['spec']['containers'])):
          LOGGER.info(json.dumps(body['object']['spec']['containers'][i]['resources']))
          pod['spec']['containers'][i]['resources'] = {'limits': {'cpu': '10m', 'memory': '10Mi'}, 'requests': {'cpu': '10m', 'memory': '10Mi'}}
        LOGGER.info(json.dumps(pod))
        json_compatible_item_data = jsonable_encoder(pod)
        return JSONResponse(content=json_compatible_item_data)
kind: ConfigMap
metadata:
  creationTimestamp: null
  name: resource-setter
  namespace: metacontroller
---
apiVersion: metacontroller.k8s.io/v1alpha1
kind: DecoratorController
metadata:
  name: resource-setter
spec:
  resources:
  - apiVersion: v1
    resource: pods
    labelSelector:
      matchLabels:
        meta: test
  hooks:
    sync:
      webhook:
        url: http://resource-setter.metacontroller/sync-resource-setter
        timeout: 10s
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: resource-setter
  namespace: metacontroller
spec:
  replicas: 1
  selector:
    matchLabels:
      app: resource-setter
  template:
    metadata:
      labels:
        app: resource-setter
    spec:
      containers:
      - name: controller
        image: "tiangolo/uvicorn-gunicorn-fastapi:latest"
        workingDir: /hooks
        command: ["uvicorn", "sync:app", "--reload", "--port", "80", "--host", "<IP_ADDRESS>", "--log-level", "trace"]
        volumeMounts:
        - name: hooks
          mountPath: /hooks
      volumes:
      - name: hooks
        configMap:
          name: resource-setter
---
apiVersion: v1
kind: Service
metadata:
  name: resource-setter
  namespace: metacontroller
spec:
  selector:
    app: resource-setter
  ports:
  - port: 80
    targetPort: 80

The Nginx pod:
apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  labels:
    meta: test
    run: nginx
  name: nginx
  namespace: metacontroller
spec:
  containers:
  - image: nginx
    name: nginx
    resources:
      requests:
        memory: "100Mi"
        cpu: "100m"
      limits:
        memory: "100Mi"
        cpu: "100m"
  dnsPolicy: ClusterFirst
  restartPolicy: Always
status: {}

Now metacontroller sees it, but does not recreate the returned pod object. Is this not a use case?

@ns-rlewkowicz this is now what metacontroller does, metacontroller can generate additional objects for the pod.
What you want is actually a mutating webhook like kyvero, to mutate the pod - https://kyverno.io/policies/other/add_default_resources/add-default-resources/


BuildStream is not reporting element-path in the startup summary

See original issue on GitLab
In GitLab by [Gitlab user @sstriker] on May 10, 2018, 00:23
In the case that example.bst actually exists under element-path, it is unclear from the output that a specific element-path was used as it is not reported in the summary.
In the case that example.bst doesn't exist under element-path, no partially parsed pipeline is printed at all (e.g. the configuration of element-path).  This then results in
# bst build example.bst
[--:--:--][][] START   Build
[--:--:--][][] START   Loading pipeline
[00:00:00][][] FAILURE Loading pipeline

Error loading pipeline: Could not find file at /src/elements/example.bst

It is not clear were 'elements' above came from.

In GitLab by [Gitlab user @tristanvb] on May 10, 2018, 08:16
Indeed this is a confusing error:

Error loading pipeline: Could not find file at /src/elements/example.bst

I feel that a better jargon for the error would be:

Error loading pipeline: No element named 'example.bst' found in project at '/src'

An adage in the indented "detail" portion of the error could also mention something like:

"Searched element path at '/src/elements' but could not find '/src/elements/example.bst'

In GitLab by [Gitlab user @cs-shadow] on Jun 6, 2018, 18:55
mentioned in commit e2e1d00a7d5524b7b7aa60125ad35bb9a9ab7c82

In GitLab by [Gitlab user @cs-shadow] on Jun 6, 2018, 18:57
mentioned in merge request !486

In GitLab by [Gitlab user @cs-shadow] on Jun 6, 2018, 20:25
mentioned in commit 502ab25a19897984adbdff72338955444b68f8f7

In GitLab by [Gitlab user @cs-shadow] on Jun 6, 2018, 22:27
mentioned in commit 7df956547696092cb07082bc4f6ec12f6585cdd0

In GitLab by [Gitlab user @tristanvb] on Jun 6, 2018, 23:10
closed via merge request !486


Disable unintended "pull down to dismiss" for sign-in modal view

To prevent the user from bypassing the sign-in/account creation process and jumping straight into the “Scheudle” page without an account signed in by dragging the sign-in modal view down and dismissing it.
Disable "pull down to dismiss" for sign-in modal view
:recycle: Current situation & Problem

Since TemplateOnboardingFlow uses a ModalView/sheet to display the onboarding/account-sign-in/creation process, the user can swipe down on the modal sheet to dismiss the process anytime during the process and enter the app's main interact without an account sign-ed in (effectively the same as using the launch argument --skipOnboarding).

:bulb: Proposed solution

Added modifier .interactiveDismissDisabled(true) to make the Modal View un-dismissible until the intended end of the onboarding flow.

Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

@Lucas-ZX-W Would be great if you can verify that the error still persists after #11 and #12 have been merged into the main project. You might need to update your fork/repo with the latest changes by creating a PR from this main branch to your main branch to get all the latest improvements.


pacparser: 1.4.0 -> 1.4.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/manugarg/pacparser/releases.
meta.description for pacparser is: A library to parse proxy auto-config (PAC) files
meta.homepage for pacparser is: https://pacparser.manugarg.com/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.4.1 in filename of file in /nix/store/hciqlk2vv9nzkqj9gjjlv1x3qb1b1dmv-pacparser-1.4.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pacparser

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hciqlk2vv9nzkqj9gjjlv1x3qb1b1dmv-pacparser-1.4.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hciqlk2vv9nzkqj9gjjlv1x3qb1b1dmv-pacparser-1.4.1
ls -la /nix/store/hciqlk2vv9nzkqj9gjjlv1x3qb1b1dmv-pacparser-1.4.1/bin

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

1 package built:

pacparser

Maintainer pings
cc @abbradar for testing.

Result of nixpkgs-review pr 219464 run on aarch64-linux 1

1 package built:

pacparser


convert camelcase model names to underscore for DB

Creating a scaffold for DocumentType creates a migration that generates a documenttypes table, but Laravel expects document_types. This fixes that, also changes the suggested route from documenttypes to document_type, may not be preferred, but it's a scaffold.

+1


type: date, time, or utc?

Currently, if a field in options is a temporal field, the type is date. For example:
var stackedBarOpts = {
    showFields: [
      {
        field: "month_date",
        fieldTitle: "Month",
        type: "date", // right now we use "date", but it can be "time" or "utc"
        format: "month"
      },
      {
        field: "weather",
        fieldTitle: "Weather"
      },
      {
        field: "count",
        fieldTitle: "Count"
      }
    ]
  };

Vega axes formatType uses "time" and "utc"

We use 'time' for for formatType. Reasons:

Tooltip format can be used to express year, month, day, date, hour, minute etc. 'time' is a more general term to describe the type of the format
We use d3.time.format() to do the formatting work
Vega scale type for dates and times are either 'time' or 'utc'


20211201 add artifacts

This isn't really the way to go about this, see comments in the original PR, thanks.


Convert to go modules

converting to go modules for easier time managing dependencies.  Upgraded to support 1.15 at same time to make it easier to manage the gen-tool.

/azp run

/azp run


fix(Input): transparent input padding off

Steps to Reproduce

Include transparent prop in an <Input /> component. The <Input /> text isn't centered vertically as a normal <Input /> would be (relative). To understand more closely, put two  <Input /> components next to one another and make one transparent and put text in both.

Expected
The vertical alignment should be the same for transparent vs non-transparent <Input /> components. The same goes with the text inside <Button /> etc. The text of a non-transparent input lines up with a button component's text, but not a transparent input and button (or anything else for that matter).
Result
The Input is not properly aligned.

@protzman can you provide a codepen to illustrate what you are experiencing?
If this ends up being CSS issue, those issues should be reported and discussed at the main repo. There are no styles included in the React project: https://github.com/semantic-org/semantic-ui/
If there are classes being applied or markup being generated incorrectly relative to the main project from the SUIR components, we would want to know about them and fix them here.

Sure. Here is a codepen. I've listed a few examples and kind of pinpointed the behavior a bit. From poking around in the code I found adding
.ui.transparent.input input {
    padding: .67857143em 1em !important;
}

to my css fixes the issue while the transparent input is in a <Grid /> component or <Form.Group /> component.

@protzman Thanks for putting that together. Just checked it out and the markup being generated by the SUIR components is indeed correct as per SUI markup: https://semantic-ui.com/elements/input.html#transparent
This is an issue with styles, not SUIR. The good news is, you can compile the SUI styles with your own theme if you would prefer to not remove that padding on transparent inputs (There are cases where I've done it myself in projects).
Take a look at the theming instructions in the main SUI repository to learn how to compile your own styles to use with your project: https://semantic-ui.com/usage/theming.html
If you still have questions on creating and compiling your own theme using Gulp/Less, you should direct those questions to the main SUI repo or Stack Overflow.

That's cool. I understand now that it is with just the SUI css and I can manage with the addition to the css I've included in my project. I am just curious though as what defines correct and what looks correct. Is that just at the discretion of the creators?

@protzman It's definitely intentional. There are separate variables in the library for defining the transparent inputs differently. The beauty of SUI proper is you can add themes globally or to individual elements if you prefer something else. If you want more direct answers on the design decisions, you'd have to ask there.

As this issue is CSS only, I close it. @brianespinosa thanks for replies :+1:


robots.txt files for draft.ocw.mit.edu, live-qa and draft-qa servers

User Story
Users don't want to get search results from google for live-qa.ocw.mit.edu or any of the other qa and draft servers
Acceptance Criteria

[ ] Don't break the robots.txt file for https://ocw.mit.edu
[ ] Write a github action to test the contents of https://ocw.mit.edu/robots.txt -- it should always include Allow: / and Sitemap: https://ocw.mit.edu/sitemap.xml
[ ] https://live-qa.ocw.mit.edu/robots.txt should be set to deny all
[ ] https://draft-qa.ocw.mit.edu/robots.txt should be set to deny all
[ ] https://draft.ocw.mit.edu/robots.txt should be set to deny all (currently it returns a 503 error)

@pdpinch is this issue still needed, or has it been completed?

Still needed.
https://draft.ocw.mit.edu/robots.txt returns 404
https://draft-qa.ocw.mit.edu/robots.txt returns 404
https://live-qa.ocw.mit.edu/robots.txt returns 404
https://ocw.mit.edu/robots.txt also returns 404, which is OK although perhaps not ideal.

@pdpinch @blarghmatey
Would you kindly guide me a bit on where extacly to add the robot.txt, are there any reference PRs I could take a look ?

@blarghmatey I'm pretty sure that https://ocw.mit.edu/robots.txt worked at some point, but it's returning a 404 now. Did we ever have the vcl code committed for creating these robots.txt responses?
Is fastly vcl still the right place to do this?

The fastly VCL is still the right place. @shaidar can help point you at the right place to make the changes.

This is resolved now by https://github.com/mitodl/ol-infrastructure/commit/0d9724450ba6b7f62124ec5370186d75289c7fae
The TL;DR is that the wrong condition was being attached to the robots.txt response so it was never triggered.

That commit didn't end up resolving the issue as expected. The reason the robots.txt isn't being loaded is because of errors in the logic for how Pulumi/Terraform maps the request conditions to the synthetic responses. This will likely require pulling some of that logic directly into VCL instead of relying on the cache conditions and response object parameters in the ServiceVCL definition.


bug: no latest tag released

Description
GetVersionForImageTag() will lead to latest tag when at dev branch.
It is used to fetch tensorchord/envd-sshd-from-scratch, docker.io/%s/python-cache:envd-%s-cuda-%s-cudnn-%s" and docker.io/%s/python-cache:envd-%s", but all of them have no latest tag at all.
https://github.com/tensorchord/envd/blob/5e42b0a6039be75c2fa13c2b33799789966c40b7/pkg/version/version.go#L68
Reproduction
checkout main branch
envd build
Additional Info
https://hub.docker.com/r/tensorchord/python-cache/tags?page=1&name=latest
https://hub.docker.com/r/tensorchord/envd-sshd-from-scratch/tags?page=1&name=latest
latest tag should be released in
https://github.com/tensorchord/envd/blob/5e42b0a6039be75c2fa13c2b33799789966c40b7/base-images/remote-cache/build-and-push-remote-cache.sh#L29
and
https://github.com/tensorchord/envd/blob/5e42b0a6039be75c2fa13c2b33799789966c40b7/.goreleaser.yaml#L79

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

It's not a bug. It's a ~feature~.
This happens to lots of developers. Mainly because they don't have all the git tags locally.
You can try to fetch all the tags and test with make && ./bin/envd version

But I agree that the current versioning mechanics is unfriendly to new developers.
Not sure if we can refactor it to a more convenient way.


blocklist peer on retrieval timeout

This PR implements blocklisting i retrieval when the retrieval times out by a peer.
Also, it passes a context in message exchange where it was missing currently for correctness.

/beekeeper

testing if this comment will trigger pipeline

Yes, please!  This will hopefully stop (or at least slow down) the endless requesting of chunks that I sometimes see in my clients.
I'm not great at reading diff listings on the commit, but how long does the peer remain blocklisted?

Can/should we do this also in the pusher when it gets a stream-reset?
time="2020-10-09T10:17:45-04:00" level=debug msg="pusher: error while sending chunk 49795cb965cbacd7a11bdf9678bff60f86fbf1ca84ec40e75d2b063a04d8e3f4 or receiving receipt: receive receipt from peer 7b8dcf3cc74795801ca6f6ef8c90c49ac82af0348eae1e2c18338cdccca55476: stream reset"
This is the other loop I see my clients going into.  This one is actually worse from a bandwidth perspective because it pushes the entire chunk out instead of just a CID on a retrieval.

But then again, now that I've written it down, disconnecting and blocklisting the peer might be too extreme as this loop seems to be CID-related and not generally something that the specific peer is "doing bad".  But right now, the pusher cannot tell what the issue was with the pushed-to-target because it doesn't return errors, but simply resets the stream.

Here's a graphical image of why I'm commenting on the pusher.  This is my network bandwidth (outbound is positive) with a local peer looping on a bunch of chunks that all are resulting in a stream reset from 1 or 2 upstream peers.
https://gateway.ethswarm.org/files/1e6f979c6402b889a99ddf0f2fa7d2a7d9a9fe1c9e343637bbcb435e15d32afc

@ldeffenb

I'm not great at reading diff listings on the commit, but how long does the peer remain blocklisted?

Currently only 1 minute. This is completely my subjective estimation.

Can/should we do this also in the pusher when it gets a stream-reset?

As you already stated the problems, there should be a way to identify conditions when blocklisting should happen in pushsync as well. This would improve the protocol effectiveness for sure.

/beekeeper

/beekeeper

/beekeeper


Get rid of GMP dependency

It should be possible to get rid of the GMP dependency completely. There are very few components of the low-level GMP library that we currently rely on, so we could implement these functions ourselves.
An alternative is to limit ourselves not to support arbitrary precision arithmetic at all. I know @oscargus is very keen on this idea. I think that supporting multi-precision arithmetic can be useful. This can be discussed further.
This is an exhaustive list of functions that would need to be implemented ourselves to get rid of the GMP dependency (not very long):

mpn_lshift
mpn_rshift
mpn_add_n
mpn_sub_n
mpn_mul or mpn_mul_n
mpn_tdiv_qr
These are all the low-level functions that do what their name implies on a contiguous chunk of memory.

Of course, finding a nice clean way to install GMP on Windows could also be a solution.
vcpkg might be an option here. It can be used to install GMP it seems.


Google api error: replacingBundleWithApk

Question Checklist

[x ] Updated fastlane to the latest version
[x ] I read the Contribution Guidelines
[ x] I read docs.fastlane.tools
[ ]x I searched for existing GitHub issues

Question Subject
trying to upload my signed apk file to google play as an internal release and I get this error:
replacingBundleWithApk: You cannot insert a bundle with the same version code as an APK in the edit. - You cannot insert a bundle with the same version code as an APK in the edit.
this is all I'm doing:
lane :internal do
  upload_to_play_store(
    track: 'internal',
    apk: './app/release/app-release.apk'
  )
end

Question Description

I guess what this error means to say is that you already uploaded a bundle with the same version code. Make sure to increase the version code of your app for every upload.


Contact installations@emf and let them know about the project?

Not needed as the blanket will be hosted in a village and does not need a lot of space


feat: upgrading syntax-highlighter to support Lua and Solidity

Fixes RM-2916

🧰 Changes

[x] Upgrades @readme/syntax-highlighter to the latest release to add support for highlighting Lua and Solidity.

🧬 QA & Testing
Highlighting in action on the local dev server:

I'm not sure how to update the browser snapshots to work again because they work just fine locally. 🥺

This PR was released!
🚀 Changes included in v6.36.0-next.1

This PR was released!
🚀 Changes included in v6.36.0


Re-added tasers to arsenal research but nerfed

About the PR

Adds tasers back as a tier 3 research.
Nerfes tasers to only shoot 2 times before needing a recharge, instead of 5.
Adjusted the taser sprites accordingly.

Why / Balance

Tasers were removed in #22361 for being too busted. Despite being a tier 3 research and having a fairly appropriate fab cost they were agreeably kinda busted once you had them because of the relatively high capacity.
That said they were kinda cool and added variety to the security arsenal. With this PR I'm hoping they can be added back with nerfs. If this gets merged tasers will only have two shots instead of five. If anyone still thinks this is too busted then maybe we could try adding more nerfs like a higher mat cost or maybe even making them only shoot once.
But at least consider giving tasers another chance! if #23051 (disabler SMG) also gets merged then we would have the whole stun weapon spectrum for secoffs to choose from!
Technical details

None.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: Added tasers back as a tier 3 research, but nerfed.

I still think the tasers too busted even with just 2 shots since you can still stack them and the fact they insta stun. I think it would be better if they just got reworked entirely because in any scenario, insta stun is too op imo. I think stun resistance would remedy this since at the moment tasing a geared to the teeth nukie has the same outcome as tasing a random greytide in the short term.

That's a valid point, what if instead of stunning it did 99 stamina damage or something like that?

nukie has the same outcome as tasing a random greytide

This applies to disablers too. And consider that it is a tier 3 research so unless the nukies take a very long time to prepare they wouldn't often have to worry about tasers.

im fine with this

That's a valid point, what if instead of stunning it did 99 stamina damage or only had one shot instead of two? (No matter how low the capacity is it still takes the same amount of time to charge).

How about 80 stam damage, it makes the person drop whatever their holding and also makes them start taking shock damage for 3 seconds that makes them have short falls like when eating Electron soup or whatever its called. Then you can at least manage to use a grenade or something when you get shot instead of an instant loss.

That's a valid point, what if instead of stunning it did 99 stamina damage or only had one shot instead of two? (No matter how low the capacity is it still takes the same amount of time to charge).

How about 80 stam damage, it makes the person drop whatever their holding and also makes them start taking shock damage for 3 seconds that makes them have short falls like when eating Electron soup or whatever its called. Then you can at least manage to use a grenade or something when you get shot instead of an instant loss.

That sound pretty fair, I'll try that.

Okay i changed it, the bolts don't inta-stun anymore. They deal 80 stamina damage which is enough to slow and also makes them do sporadic shortfalls that aren't long enough to cuff.

we need this 👍

More sec content is good, actually
But right now it seems tricky to use (don't miss either shot) yet too punishing when it hits (no range limit, injecting licoxide and repeating small stuns over time without counterplay except the usual hardcountering eshield)
Some ideas:

Remove the licoxide component, this wasn't in original taser and makes it busted in other ways, and replace with slowdown
Add some inaccuracy like the disabler or a range limit
Add a 'wind-up' mechanic where the taser whirrs for one second with an audible noise (payday 2 taser) and you're slowed to walk before releasing trigger to fire (mouse click and hold, one second passes, then you can fire by mouse release)

Now it just does 4 seconds of slowdown.
While testing I noticed the effect stacks so best case scenario you land both shots and have like 2 seconds to get your baton out or something.

If it just does slowdown, thats not really worth being tier 3 since you could just use a disabler to get similar results

If it just does slowdown, thats not really worth being tier 3 since you could just use a disabler to get similar results

It takes like three disabler shots to slowdown someone this much, taser does it instantly. Having a taser and a gun would give you a better chance at a 1v1 than a disabler and a gun. Though for just arresting someone the disabler might yield around the same results.

definitely change it so it doesn't slow down as much and give it 3 shots.

Done.

No clue why its failing the one test but to recap this is what the taser does now ;

Has 3 shots per charge
Incurs a 4s long stack-able 50% movement slowdown (NOT via stamina damage)
Incapable of stunning/disarming

No clue why its failing the one test but to recap this is what the taser does now ;
* Has 3 shots per charge (sprite adjusted)

* Incurs a 4s long stack-able 50% movement slowdown (NOT via stamina damage)

* Incapable of stunning/disarming

I tested again and the slowdown is still way too slow.
I'm also noticing that the stacking can be busted.
Comboing with itself makes it extremely hard to escape security, and then comboing it with either a disabler or a disabler SMG makes sec effectively a one man army.
These are the latest changes:

Decrease the slowdown so it's not as slow. It should honestly have less slowdown than a bola.
The slowdown should reapply if shot again, but it should not stack with itself.

I tested again and the slowdown is still way too slow.
I'm also noticing that the stacking can be busted.

I understand making it slowdown less since it stacks, but if its any less slow than a bola (0.7x) AND doesn't stack, then what you end up with is a tier 3 arsenal research that effectively gives you like two bolas without the stun.

Can we compromise at a little weaker than bola slowdown and keep stacking? Otherwise it's practically useless considering it's very hard to land all your shots in the heat of the moment and that it's a T3.

I tested again and the slowdown is still way too slow.
I'm also noticing that the stacking can be busted.

I understand making it slowdown less since it stacks, but if its any less slow than a bola (0.7x) AND doesn't stack, then what you end up with is a tier 3 arsenal research that effectively gives you like two bolas without the stun.

Can we compromise at a little weaker than bola slowdown (x0.75) and keep stacking? Otherwise it's practically useless as a T3, also every other weapon stacks (bola, disabler, normal weapons in a sense,) why wouldn't the taser?

My issue with this is more point blank applications. With the speed as is, especially the stacking, you can get a slowdown shot in + baton hits in and basically auto win a fight.
You can't put x2 bola on one person, but you can shoot people with the taser multiple times. So it's better for it to reapply the debuff rather than stack it.

You can't put x2 bola on one person, but you can shoot people with the taser multiple times.

After at least 78,000 research points in arsenal. Would you be willing to settle on halving the firerate and making it only slow for 3s instead of 4s? Then its much harder to stack.

Curious why this was closed?

Curious why this was closed?

Started to get the feeling this wasn't actually gonna get merged.

Curious why this was closed?

Started to get the feeling this wasn't actually gonna get merged.

Seemed like at least some of the maintainers were on board. I feel like you should open it back up and let them make the decision. Seemed like some good changes, imo.


Fixes to profile builder

In list mode recursively scan the specified imports; this will simplify
updating the list for new module major versions.  It also removes
redundant paths and found some missing *api packages.
Limit the number of concurrent calls to parser.ParseDir() to avoid
running out of file handles on some platforms.

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] The PR targets the latest branch.
[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] Apache v2 license headers are included in each file.

Can one of the admins verify this patch?


adds a very basic pyvisa-sim yaml for the Keithley 2600

Just a convenience feature. Its at least good enough to instantiate the instrument without warnings
about failed snapshots.
Changes proposed in this pull request:

Will allow users to instantiate the (new, channelized) Keithley 2600 driver without the physical instrument.

@astafan8

I allowed myself to add the minimal test_Keithley_26xx.py that uses the yaml sim file myself. Once the CI passes, i'm going to merge. Is this OK for you @StefanD986 ?

I allowed myself to add the minimal test_Keithley_26xx.py that uses the yaml sim file myself. Once the CI passes, i'm going to merge. Is this OK for you @StefanD986 ?

Yes, of course. Sorry I didn't yet get around to add the test myself, so thanks a lot.


Firebase realtime equalTo

Hello
i have a problem when i want to get a specific data form firebase realtime so i used the function equalTo(...) for return the data that i want, but i all the cases this return a query which containe the first element in my firebase
the code :

This would be more appropriate in https://github.com/FirebaseExtended/flutterfire

thank you that help me a lot


When a multisig has already been named on another network, we don't display the name and rather override it

Description
I create a multisig M1 on Polkadot, give it a name "M1-name"
I create a multisig on Kusama, with the same signatories, the process asks me for a name, it's "M2-name".
--> we've effectively overriden M1-name with M2-name without our user knowing.
Solution
At multisig creation, we should check whether the public key was already stored and if there's a name for the multisig. If there is, we should proceed and pre-fill the field with this name.

@Tbaut  can I work on this?

Sure

hi @Tbaut i have cloned the repo can you guide me for to the rule for pushing me changes? like should i make fork and work on it or just make a branch nad work on it..
also in which file should i look for to start working.

I've tackled this issue in #516, you can take a look.


Add Release to this process

jb build mybookname/ --builder latex
Build the latex files as well and then include that in the release.

#4


Migrate to react 0.14

Only one change: getDOMNode is deprecated in 0.14, and is replaced with findDOMNode(this).
https://facebook.github.io/react/blog/2015/07/03/react-v0.14-beta-1.html#dom-node-refs

Hmm, I guess this is tricky, because we also need react-dom as a peerDependency ... but not if we're supporting 0.13.x. So maybe a clear cut is necessary.

Errr ... I guess React.findDOMNode will be kept as an alias (with warnings) until React 0.15.


Is there a way to control the path of the NPC vehicle？

Is there a method to control the path of the NPC vehicle, set the starting and ending coordinates, and drive the NPC vehicle at the specified speed? I see that Agent can do this，but I can‘t find any guide in the new release，is there a new method to do this now？

Hi,
It is possible using automatic_control.py and the Behavior agent, but I don't think it's well documented. You might have to look into the code, it should be enough to check the flags of the script.

Thank you！ I find that agent in PythonAPI can control the path but I can‘t find some guide for this. Also It's kind of diffcult for me to modify the automatic_control.py. I just want to get some document to guide me.

            agent = BehaviorAgent(world.player, behavior=args.behavior)

            spawn_points = world.map.get_spawn_points()
            random.shuffle(spawn_points)

            if spawn_points[0].location != agent.vehicle.get_location():
                destination = spawn_points[0].location
            else:
                destination = spawn_points[1].location

            agent.set_destination(agent.vehicle.get_location(), destination, clean=True)

I'm pretty sure it's enough to change the value of destination to where you want the vehicle to arrive.
            if not self.map.get_spawn_points():
                print('There are no spawn points available in your map/town.')
                print('Please add some Vehicle Spawn Point to your UE4 scene.')
                sys.exit(1)
            spawn_points = self.map.get_spawn_points()
            spawn_point = random.choice(spawn_points) if spawn_points else carla.Transform()
            self.player = self.world.try_spawn_actor(blueprint, spawn_point)

And here if you change the value of spawn_point you can choose where the vehicle will be created.

Thank you so much ! I will try this!

How can I import  BehaviorAgent into my code? I have problem to do this. My code can only run in /PythonAPI/examples now.  I don't know how to use  BehaviorAgent.

from agents.navigation.behavior_agent import BehaviorAgent
I am closing this issue since it's not an issue. Check the code of automatic_control.py further to understand how to run your own code.
If you need more help feel free to contact us on Discord at this link.

ok, thank you so much!

@jackbart94 I tried changing the spawn point using 0.9.11 but it does not work
        if not self.map.get_spawn_points():
            print('There are no spawn points available in your map/town.')
            print('Please add some Vehicle Spawn Point to your UE4 scene.')
            sys.exit(1)
        spawn_points = self.map.get_spawn_points()
        current_location = carla.Location(x=-2.419356, y=204.005676, z=0.001191)
        spawn_point = carla.Transform(current_location, carla.Rotation())
        self.player = self.world.try_spawn_actor(blueprint, spawn_point)

I tried the above code and it just stays in the while loop and never comes out of it


Different namespaces in operator.yaml

https://github.com/rook/cassandra/blob/acc9f9697631729988057232daddcf177d61cef6/cluster/examples/kubernetes/cassandra/operator.yaml#L95
Should it not be using the rook-cassandra-system namespace like the resources declared above?

Yes, looks like this was an unintentional change in v1.7.3 with #23.

Many thanks :)


[Improvement][Metrics] Switch to use tags to indicate task / workflow execution status for metrics

Purpose of the pull request

This PR closes: #10867
related: #9324

Brief change log

Use tags instead of names to indicate task / workflow instance execution state / status for metrics.
Will update docs / grafana-demos in following commits.

Verify this pull request

Verified by manual tests.

Codecov Report

Merging #11128 (9dd91b8) into dev (71cf7e1) will decrease coverage by 0.07%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##                dev   #11128      +/-   ##
============================================
- Coverage     40.37%   40.29%   -0.08%
+ Complexity     4873     4871       -2
============================================
  Files           950      950
  Lines         37187    37113      -74
  Branches       4079     4075       -4
============================================
- Hits          15014    14956      -58
+ Misses        20662    20645      -17
- Partials       1511     1512       +1

Impacted Files
Coverage Δ

...erver/master/event/TaskRetryStateEventHandler.java
0.00% <0.00%> (ø)

...ler/server/master/event/TaskStateEventHandler.java
0.00% <0.00%> (ø)

...ver/master/event/TaskTimeoutStateEventHandler.java
0.00% <0.00%> (ø)

...server/master/event/WorkflowStartEventHandler.java
0.00% <0.00%> (ø)

...server/master/event/WorkflowStateEventHandler.java
0.00% <0.00%> (ø)

...master/event/WorkflowTimeoutStateEventHandler.java
0.00% <0.00%> (ø)

.../server/master/runner/WorkflowExecuteRunnable.java
7.79% <0.00%> (ø)

.../server/master/metrics/ProcessInstanceMetrics.java
57.57% <100.00%> (-1.80%)
:arrow_down:

...inscheduler/server/master/metrics/TaskMetrics.java
77.14% <100.00%> (+7.69%)
:arrow_up:

...r/server/master/service/MasterFailoverService.java
56.77% <100.00%> (ø)

... and 13 more

Help us with your feedback. Take ten seconds to tell us how you rate us.


Consistently spell it like "metadata" throughout the code base

The "metadata" spelling seems to be way more common than "meta data" or
"meta-data".
Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

Note that for yet more consistency this would require to also rename classes, functions and properties like isMetaDataOnly, but I'm not doing that here as it would break existing curations.

Note that for yet more consistency this would require to also rename classes, functions and properties like isMetaDataOnly, but I'm not doing that here as it would break existing curations.

You could use @JsonAlias to make it backward compatible.

You could use @JsonAlias to make it backward compatible.

Right, but that would not work e.g. for rules using the isMetaDataOnly rule matcher. While I really like consistency, I'm not sure it's worth a breaking change here, and I also do not want to introduce a new isMetadataOnly rule matcher and deprecated the old one.
More opinions?

More opinions?

I'm fine with leaving isMetaDataOnly as-is.
I've found one more occurence of meta-data in getting-started.md.
That could be fixed as well.

I've found one more occurence of meta-data in getting-started.md.
That could be fixed as well.

Done, I've found even some more occurrences in non-code places.

Merging despite the unrelated failure.


Error: iCloud Passwords failed to response in time

Anyone knows how to solve it?

Hi, which operating system are you using and which version do you have?
Only macOS Sonoma (14.0) is supported right now

ahhhhh, my bad, thought it was for windows

I'm running firefox for Windows and iCloud keychain doesn't have an extension for Firefox.
I'm assuming it doesn't support Windows.

Windows support is planned but not a priority to be honest
Progress will be tracked in #18

I'll be looking for it when it's launched, but ofc dont rush it, there is no need.
PD: keep the good work!


Fix linting issues revealed by Go 1.11

Go 1.11 is stricter, and compilation will fail, revealing these issues;
agent/agent_test.go:120: *github.com/docker/swarmkit/api.WeightedPeer composite literal uses unkeyed fields
agent/agent_test.go:125: *github.com/docker/swarmkit/api.WeightedPeer composite literal uses unkeyed fields
agent/agent_test.go:130: *github.com/docker/swarmkit/api.WeightedPeer composite literal uses unkeyed fields
agent/agent_test.go:135: *github.com/docker/swarmkit/api.WeightedPeer composite literal uses unkeyed fields
agent/agent_test.go:140: *github.com/docker/swarmkit/api.WeightedPeer composite literal uses unkeyed fields
manager/dispatcher/dispatcher.go:426: Entry.Info call has possible formatting directive %s
manager/dispatcher/dispatcher.go:547: Entry.Debug call has possible formatting directive %s
make: *** [vet] Error 1

LGTM, let's ship it.


⚠ Fortnite has degraded performance

In b90ac83, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1542 ms

Resolved: Fortnite performance has improved in 5ae8bef.


Minor fixes for isolation

What changed?

Reload sticky tasklists if isolation config is changed
Fix sticky tasklists' lookback window
Fix nil pointer for isolation group state

Why?
fix bugs

How did you test it?
existing tests

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 01886f0f-f06b-4f9d-ba3c-4a95bad031f8

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
81 unchanged lines in 20 files lost coverage.
Overall coverage decreased (-0.009%) to 57.221%

Files with Coverage Reduction
New Missed Lines
%

common/task/weightedRoundRobinTaskScheduler.go
1
89.64%

service/history/queue/timer_queue_processor_base.go
1
78.15%

client/history/client.go
2
38.1%

client/history/metricClient.go
2
45.3%

common/cache/lru.go
2
92.2%

common/persistence/historyManager.go
2
66.67%

common/util.go
2
53.73%

service/history/execution/mutable_state_util.go
2
35.95%

service/history/task/transfer_standby_task_executor.go
2
86.93%

service/matching/matcher.go
2
90.29%

Totals

Change from base Build 01886e63-76a1-4ebc-8d24-651122402e0c:
-0.009%

Covered Lines:
86954

Relevant Lines:
151962

💛  - Coveralls


Updated to Grafana 6.0.0

Updated to Grafana version 6.0.0.
http://docs.grafana.org/guides/whats-new-in-v6-0/

I'll have a look at this later tonight and run some tests before merging, thanks for the contribution!

I already updated my Grafana, and it works like a charm.
And thank you for creating this amazing project.

I've been bitten in the past when existing configurations would work but new ones would not.
No problem either way tested and all good to go.
Also you should thank @stefanprodan he did all the hard work :).


Expand summary widget and detail view to show data provenance logo or icon

In the classic version of the Platform, private instances were able to display a logo or icon beside custom data.
To coincide with ongoing work to support partner instances of the Platform, can we please expand the summary widget and detail view component to show a data provenance icon (e.g. corporate logo, Font Awesome icon)?
Further details and design specification TBC for the 21.09 (September 2021) release.

@andrewhercules is this relevant to do?

Ticket closed as Partner Preview Platform contains lock icon and this can be used by other Platform instances to highlight custom internal data


This plugin genuinely just isn't working at all.

I've tried restarting MusicBee, using a fresh copy of MusicBee, restarting MusicBee and tuna, running obs as admin, reinstalling tuna regularly and from zip, and running MusicBee as admin
and this plugin has not worked.
No error log is generated. I don't know what the problem could be.

I stand corrected, It's sending covers and nothing else I'm pretty sure.

Is your music tagged? I read the tags and send them to OBS-Tuna.
What did you try to display the song information?
When OBS is running and MusicBee is running, check in your Browser http://localhost:1608/
1608 has to be the OBS-Tuna port. You should get a JSON response with all the information MusicBee has sent to OBS-Tuna.
In OBS-Tuna Settings, did you select Web browser as Music Source?

You should put on the plugin page and github that you have to put it on web browser. It's working perfectly now

It is updated here, but on the plugin page it seems to take a while for the change to become visible


CSRF Protection

Since the library handles both client and server, I think it would be very helpful to have first class CSRF protection. The Echo framework provides middleware that has a good solution: https://echo.labstack.com/middleware/csrf
Basically: Backend generates a secure token and stores it in a cookie. All frontend requests from then on send the cookie in the header. The backend only accepts requests that contain the correct token in the header.
It works because although the cookie itself will always get sent during an attempted attack, only the intended client can read the cookie and place it in the header, so as long as the server is verifying the header for each request, session hijacking is not possible. Using secure, samesite strict, and httponly helps provide further security.

@GiraffeKey Sounds like a great idea, I'll take a look! If you feel like trying to implement it, I'm happy to merge!

Here is a good article about how it's done in Flask. Quite interesting read I think.
https://testdriven.io/blog/csrf-flask/


feat: add no-js support

Adds no-js support to the docs site, based on the same model as public website:

add html.no-js to the default layout
remove it again in a script block in the head
add some error handling in the main js file

Nice! A side question - does the component_example.erb also need no-js support (not sure how this works when it's an iframe)

I think we're ok, because:

the components are rendered in the iframe view and they should be build to handle the absence of JS anyway, if they need to (eg target content and disclosure just appear open
the ComponentExample component is OK because it uses components (🤯) that are already fine without JS

LMK if I've misunderstood tho and we can have a chat - I'll wait till you get back to me 🙂

I think we need to check this for every component that uses js - I just found that on-this-page with nested links doesn't show the nested links if js is disabled. Targeted content is a nice example as it doesn't rely on .no-js in the scss. The ones that do, if added as an iframe (which I don't know how much we'll do) or when open in a new tab will not work so smoothly without .no-js.

For the component iframe / new window I think mirroring the same no-js scripts in https://github.com/citizensadvice/design-system/blob/72188ce0f0c5194b7096252621a6604d73e34c10/design-system-docs/src/_layouts/component_example.erb would cover us there.

I think we need to check this for every component that uses js - I just found that on-this-page with nested links doesn't show the nested links if js is disabled. Targeted content is a nice example as it doesn't rely on .no-js in the scss. The ones that do, if added as an iframe (which I don't know how much we'll do) or when open in a new tab will not work so smoothly without .no-js.

Ah - gotcha! Yup I'll add no-js to the layout for the iframe view as @davidrapson suggests.
For on this page, my recollection is that not showing the nested links was a conscious decision since:

they are displayed hidden by default
showing all of them at the same time would be too much
the core behaviour is seeing the main links and the show/hide is a nice sprinkle of prog enhancement on top