Documentation

Hi,
Where is the documentation ?
Thank you

OK I looked at your code and it's pretty empty :-) I thought your plugin was doing more things.... At least I didn't really understand what xPosition and yPosition were for...


Update use of page_limit to pagination_request

Description of this PR:
Update use of page_limit to pagination_request in engine.py
Scope:
Bug fix

'track_list()' was returning the error:
{'command_error_message': 'pagination_request', 'is_warning': False, 'command_error_type': 'PT_UnknownError'}
This was caused by 'page_limit' being deprecated since Pro Tools 2023::9
I've updated engine.py to use 'pagination_request' instead for get_file_location & track_list.

Great, thanks!

@StephenMachete if you want to merge this into your PR that might make the most sense.

This has been addressed in another merge but just addressed it permanently here. Thank you!


how to use V1Volume, V1Toleration etc?

Description
I am trying to convert one of our workflow yamls into DSL, which uses few things like volumeClaimTemplates, volumes, volumeMounts, tolerations etc. I can't find any examples for that which explains how can I pass all those configs into V1Container?, any example with DSL would be really helpful.

I think I found out how to use those, this is an example below, but it seems to have a lot of nested classes which needs to be initiated just to set Affinity. Am I doing it correctly?
from argo.workflows.client import V1alpha1Api

from argo.workflows.dsl import Workflow
from argo.workflows.dsl.tasks import *
from argo.workflows.dsl.templates import *
from kubernetes.client.models import V1Toleration, V1Affinity, V1NodeAffinity, V1NodeSelector, \
    V1NodeSelectorTerm

class TestWorkflow(Workflow):
    service_account_name = 'argo-workflow'

    node_selector = V1NodeSelector(
        node_selector_terms=[
            V1NodeSelectorTerm(
                match_expressions={"key": "app", "operator": "In", "values": ["job"]}),
            V1NodeSelectorTerm(
                match_expressions={"key": "worker", "operator": "In", "values": ["default"]}),
        ])

    node_affnity = V1NodeAffinity(required_during_scheduling_ignored_during_execution=node_selector)

    affinity = V1Affinity(node_affnity)

    tolerations = [V1Toleration(
        key="app",
        operator="Equal",
        value="job",
        effect="NoSchedule"
    )]

@brtasavpatel tolerations and affinity should go to top level workflow spec
see https://github.com/CermakM/argo-client-python/blob/0caa743442d37f2f2e3b30867398ed2708c1bf4d/argo/workflows/client/models/v1alpha1_workflow_spec.py#L59

@yxue-kabam whatever is set as a property to the Workflow becomes part of the WorkflowSpec if that property is valid according to the OpenAPI specification of WorkflowSpec. That being said, @brtasavpatel 's approach is correct, setting affinity property of the Workflow makes part of the workflow.spec.affinity.
Unfortunately, that particular property is really annoyingly nested :/ not much we can do here, tho, as this is the specification of it.


Is this project still in use/active?

Looks like this project hasn't had any updated since the end of 2013.
Is it still being used or maintained? The README.md says its being actively maintained...

we've done a bit of work on our fork https://github.com/unicredit/hpaste


Change colour of bodies on drag

Hello,
the goal is for each body to change colour to green on "startdrag" and return back to the original colour on "enddrag".
now works on one element only, no matter which body is dragged
Here is the demo (line 246)
https://codepen.io/fogseller/pen/qBxBYrQ
Any assistance you can provide would be greatly appreciated. Thank you 😉

You need to pass in all the bodies you wish to search for when using Query.point.
I've just returned all the bodies in the world using Matter.Composite.allBodies(world), but if you wanted to restrict it to just a few then you could just pass them into the query as so [body1, body2, body3].
`// START DRAG
Matter.Events.on(mouseConstraint, 'startdrag', function (event) {
const bodies = Matter.Query.point(Matter.Composite.allBodies(world), event.mouse.position);
bodies.forEach(b => {
b.render.fillStyle = '#b6fa00';
})
});
// END DRAG
Matter.Events.on(mouseConstraint, 'enddrag', function (event) {
const bodies = Matter.Query.point(Matter.Composite.allBodies(world), event.mouse.position);
bodies.forEach(b => {
b.render.fillStyle = '#8E8E8E';
})
});`

hey @grantjenkins ! thank you so much for the explanation and solution. works great. 👍 thank you!

Thanks @grantjenkins, it depends on specifics but the other way to try is checking mouseConstraint.body or mouseConstraint.constraint.bodyB.


Update PrivilegedAccountPermissionsChanged.yaml

Added AssignedRoles has "Admin" for more accurate extraction of admin users
Required items, please complete
Change(s):

See guidance below

Reason for Change(s):Added the usage of BlastRadius for more accurate extraction of admin users

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

Hello @praveenthepro, Thanks for raising this PR. This PR will be investigated and will update you about the same before 07 December, 2023.

Hello @praveenthepro, I forced push the master branch into this PR. Can you please confirm once if the file is as it was when you committed it.

@v-prasadboke i pushed another commit now, Kindly please checkout and go with the latest commit,


Improve indexing to support table behavior

This is a major overhaul of the model interface to better support Table-like indexing behavior, most importantly through setindex.
The basic idea is that AbstractModels should allow Cartesian indexing, i.e. m[i,j] for both setindex! as well as getindex in order to really act like a table.
This PR refactors the existing implementations of getindex and setindex! to accomplish this, and in the process, expands the functionality of setindex! (and Base.setindex for the immutable case) to permit row indices.
The implementations of update/update! are simplified to be simple wrappers around setindex. In addition, update now provides an additional dispatch which permits the application of filtering rules to generate row indices via do syntax:
updated_m = update(m, p -> p.somefield == somevalue) do p
    # generate values here;
    # returning a scalar will apply the new values to the :val field;
    # returning a row vector, NamedTuple, or any Tables.jl compatible type will update all columns in the table.
    p.val * 2.0
end

This allows the user to apply filters to only update subsets of parameters. This is also possible via setindex! using row indices:
mask = map(p -> p.somefield == somevalue, params(m))
m[mask, :val] = x # x must match in size

~This is a draft PR at the moment. More clean up needs to be done and docstrings added at the minimum. There are also some behavioral issues that need to  be addressed, like how to handle broadcasting.~
Current limitations:

Multi-column indexing for getindex is not supported, since it's not clear what the return value should be (named tuples?). It is supported by setindex, however.
getindex/setindex on subsets of rows are not in general type stable or allocation free. I think this is acceptable for now given the likely use cases.

Resolves #41
Resolves #21

Codecov Report

Merging #44 (5664d5a) into master (b87e148) will decrease coverage by 6.76%.
The diff coverage is 70.11%.

@@            Coverage Diff             @@
##           master      #44      +/-   ##
==========================================
- Coverage   79.88%   73.11%   -6.77%
==========================================
  Files           4        3       -1
  Lines         174      186      +12
==========================================
- Hits          139      136       -3
- Misses         35       50      +15

Impacted Files
Coverage Δ

src/param.jl
84.61% <0.00%> (-2.23%)
:arrow_down:

src/tables.jl
77.77% <0.00%> (ø)

src/model.jl
69.56% <71.76%> (-8.22%)
:arrow_down:

src/ModelParameters.jl

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 b87e148...5664d5a. Read the comment docs.

@rafaqz This is ready for feedback.

The allocation test that is failing on CI passes on my system (Julia 1.6), so it must be a compiler version issue.

@rafaqz Do you have any thoughts on what to do about this version-dependent test failure?

So its allocating on 1.3 but not 1.6?
You can put that test in a version specific conditional, or we can stop supporting 1.3

I like the version-specific conditional idea. Let's see if it works now.

Also, since this changes indexing behavior (although should be non-breaking for most things...?), we should probably bump the minor version.

Finally all green! Let me know when you've looked at it, @rafaqz . I'm not 100% happy with the way it turned out... I think the dispatch graph for setindex/getindex could probably be a bit cleaner. But it's probably OK for now so long as it works.

Ok I'll try to have a look tonight.

At the moment, there are no breaking changes. The syntax question is really whether or not it's worth it to make such a breaking change in order to be consistent with other table interfaces. The performance issue is low priority, at least for my use case.

It doesn't look that easy to me, but maybe I am missing something. In any case, if you already know how to improve it, please feel free to suggest a solution.

Just use map instead of a loop and themices tuple should be type stable

No. There is a loop there for a reason. As I pointed out in the other comment, it iteratively reconstructs m for each column. It's not a map-like operation. There is almost certainly a better way to do it, but I am quite sure it's not that simple. To use map, you would need to come up with a way to merge all of the reconstructed Models (for each column).

That's a fold.... foldl should also be type stable.

Ok, I'll try foldl.

It makes it type stable but does not have any substantial impact on performance, at least on this test case that I tried:
m = Model(s1)
xs = Tables.columns([(val=5.0,bounds=nothing),(val=4.0,bounds=nothing)])
idxs = [1,2]
cols = (:val,:bounds)
@btime Base.setindex($m, $xs, $idxs, $cols)
# before: 26.140 μs (404 allocations: 23.39 KiB)
@code_warntype Base.setindex($m, $xs, $idxs, $cols)
# after: 25.525 μs (404 allocations: 23.39 KiB)

It's also worth noting that indexing tables with Tuple is not standard practice. I don't think Matrix or DataFrames support it.

Ah right, maybe we should remove it instead.

I just started using this branch in my "real world" use case and it's.... not good. Like almost a full minute to compile on a deeply nested model with about 50 parameters. This is with several calls to setindex/update.

Yeah... the type stability is probably more important for that than for runtime speed. Have a look with @snoop_compile there might be some easy wins.

It's probably going to be reconstruct :(

I guess we should come back to this at some point.... I am no longer convinced that there is a strong enough use case for type-stable table updates that is worth the insanely high compilation cost. Maybe we should just accept type instability here?


[2.0_beta] powershell/management/spawnas throws [!] Exception: 'launcher_bat'

Empire Version
Empire 2.0_beta, fresh pull
OS Information (Linux flavor, Python version)
Kali rolling, freshly updated
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
Attempting to spawn a new Empire agent as another user using management/spawnas fails with an exception.
Screenshot of error, embedded text output, or Pastebin link to the error

(Empire: RU8GM9SA) > usemodule management/spawnas
(Empire: powershell/management/spawnas) > options
          Name: Invoke-SpawnAs
        Module: powershell/management/spawnas
    NeedsAdmin: False
     OpsecSafe: False
      Language: powershell

MinLanguageVersion: 2
Background: False
OutputExtension: None
Authors:
rvrsh3ll (@424f424f)
@harmj0y
Description:
Spawn an agent with the specified logon credentials.
Comments:
https://github.com/rvrsh3ll/Misc-Powershell-
Scripts/blob/master/RunAs.ps1
Options:
Name       Required    Value                     Description

UserName   False                                 Username to run the command as.
CredID     False                                 CredID from the store to use.
Domain     False                                 Optional domain.
Proxy      False       default                   Proxy to use for request (default, none,
or other).
Listener   True                                  Listener to use.
ProxyCreds False       default                   Proxy credentials
([domain]username:password) to use for
request (default, none, or other).
UserAgent  False       default                   User-agent string to use for the staging
request (default, none, or other).
Password   False                                 Password for the specified username.
Agent      True        RU8GM9SA                  Agent to run module on.
(Empire: powershell/management/spawnas) > set UserName domainadmin
(Empire: powershell/management/spawnas) > set Domain TESTNET
(Empire: powershell/management/spawnas) > set Password P@SSw0rd
(Empire: powershell/management/spawnas) > set Listener https
(Empire: powershell/management/spawnas) > run
[>] Module is not opsec safe, run? [y/N] y
[!] Exception: 'launcher_bat'

Any additional information

This was due to the incorrect key being used to generate the launcher. Fixed in the 2.0_beta branch.


Provide more configuration options for customizing the translation process

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Description
It would be helpful to provide users with more control over the translation process by adding specific features like:

The ability to skip image translation.
The option to select folders or files to exclude from the translation process.
The ability to adjust the criteria or rules when verifying translations for accuracy.

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Once the plan is more concrete, I intend to break this issue down into separate issues for each feature (e.g., skipping image translation, folder exclusion, and adjustable translation verification criteria).
Thank you, @Shardakaur2624, for providing feedback on this issue!

Create separate issues for each feature, as outlined above.
Assign priority levels to each issue based on user needs and technical complexity.
Begin gathering requirements and technical details for each issue.
Develop a plan for implementing each feature, including timelines and resource allocation.

Hi @Shardakaur2624,
As you suggested, I'm going to create sub-issues within this main issue to address each specific feature - skip image translation, customization of folder exclusion, and customization of translation validation criteria.
Prioritizing these issues is definitely a good idea. I'm considering looking at other open source projects for best practices that can guide us in discussing concrete solutions going forward.
Creating a detailed implementation plan is crucial, especially to get this project to a solid 1.0.0 release. We'll need to systematically outline the required features and their implementation steps to ensure that we support all target languages flawlessly.
I look forward to working on these steps to take this project to the next level.
Thanks again for your insightful feedback!


When will 0.17.0 be released?

The documentation on GitHub Pages documents version 0.17.0 which contains features we could already use. However, the releases on ansible are still on 0.16.3 (galaxy). Do you have a date when 0.17.0 will be released?

Thanks for the reminder, it looks like we had a bunch of stuff stacked up waiting for the release button.


JS Benchmark - Keyed Version

Hey. I noticed simulacra is listed as 'non-keyed' in the benchmarks test by JS Performance Benchmarks. They define the classification:

Keyed implementations create an association between the domain data and a dom element by assigning a ‘key’. If data changes the dom element with that key will be updated. This feature might be necessary when integrating with 3rd-party libraries, transitions or when the DOM keeps some state. Non-keyed implementations are free to reuse the existing dom nodes in whatever way they like and thus might be faster, but may cause issues if there’s a dependency on the particular dom nodes.

Here is an overview of the classification and potential problems.
This is out of my scope, but if I am understanding correctly from the readme section on safety-checks, simulacra is keyed by default. The benchmark includes a test that is supposed to check if a library is keyed or not, which I'm assuming classified simulacra as non-keyed.
If simulacra is keyed or can be configured to be, I'd like to see how performance is effected. It scores very high in the current test, as it stands.
Is simulacra keyed by their standards described above? If not, is there a reason why safety checks to prevent the potential problems tracking DOM nodes mentioned were not included or shouldn't be added?  Thanks.

Hi there, sorry for the late reply, I was on vacation.
I think I could implement a "keyed" version but I don't see the motivation. If you look at the difference between vanilla keyed vs non-keyed, non-keyed performs faster in certain operations like replacing rows, because it is allowed to make optimizations that aren't possible with keyed implementations.


Github Actions Testing Issues

Issue with Github testing for pytest files in Bot

Fixed by changing conftest to work off the current directory rather than the os directory, pytest properly finds the cogs directory and loads cogs from it now. Also moved conftest to the root directory and renamed bottest to test_bot

fixed and closed


No. of objects in the predictions are more than the actual number

Hi, Daniel. I have trained Yolact for my custom model and while the predictions are very accurate, there are redundant masks that are being generated. Suppose, I have 7 objects in an image, the no. of predictions are sometimes 7 or 8 or 9 i.e. two masks overlap for a single object. Is there any parameter in Yolact that I could use to remove the non-maximum suppression.

Yup, you can. There are 3 config settings that control NMS:
    # Top_k examples to consider for NMS
    'nms_top_k': 200,
    # Examples with confidence less than this are not considered by NMS
    'nms_conf_thresh': 0.05,
    # Boxes with IoU overlap greater than this threshold will be culled during NMS
    'nms_thresh': 0.5,

You can try changing nms_thresh to something lower that suits your data.

@dbolya Thanks for this. I will try it out and see. One more question. Is it possible to parallelize the prediction process instead of sequentially reading the images one by one and then performing prediction?

There is, but it's complicated. See evalvideo in eval.py for details. It's for video, but you could replace the cv2 vid object with something that returns images from disks, and replace the cv2.imshow with saving the image to the disk.

@dbolya Thanks, Daniel. I will check that out. As you said, the evalvideo() looks complicated indeed. I am closing this issue now.


WSO2 3.0.0 Gateay Error:OAuthAuthenticator Swagger is missing in the gateway for JWT authentication

While performing JWT authentication we are facing below issue in gateway components.
OAuthAuthenticator Swagger is missing in the gateway. Therefore, JWT authentication cannot be performed .

Is this behavior observed for all APIs? Did the APIs migrated from a lower version or the APIs created in 3.0.0 environment?

It was working earlier,but we changed the hostname and then issue
started.we have 2 gateway nodes.
On Thu, 26 Mar 2020, 18:41 Vithursa<EMAIL_ADDRESS>wrote:

Is this behavior observed for all APIs? Did the APIs migrated from a lower
version or the APIs created in 3.0.0 environment?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wso2/product-apim/issues/7831#issuecomment-604422504,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALB7TWK3QH3TIMS7PXCI7STRJNIBFANCNFSM4LUEMVUA
.

Can you re-publish the API and see whether it works?

Hi,
We have re-published the APIs from scratch, but still facing the same
issue.One gateway working fine but another gateway throwing this exception.
On Fri, 27 Mar 2020, 10:07 Vithursa<EMAIL_ADDRESS>wrote:

Can you re-publish the API and see whether it works?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wso2/product-apim/issues/7831#issuecomment-604810570,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALB7TWPPRY5QB7XMR64N6M3RJQUQZANCNFSM4LUEMVUA
.

Hi @arun-1983 ,
How does the artifact synchronization happens in deployment?
Can you check Product-home/repository/deployment/server/synapse-configs/default/local-entries folder contains the local entry file which related to the API.

Hi.
Yes,after investigation i found swagger files are not been synced under
local entries but api been synced.
On Sat, 28 Mar 2020, 21:28 Tharindu Dasun Dharmarathna, <
<EMAIL_ADDRESS>wrote:

Hi @arun-1983 https://github.com/arun-1983 ,
How does the artifact synchronization happens in deployment?
Can you check
Product-home/repository/deployment/server/synapse-configs/default/local-entries
folder contains the local entry file which related to the API.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wso2/product-apim/issues/7831#issuecomment-605466383,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALB7TWJIJL3FCREOJ3HE4ALRJYNDBANCNFSM4LUEMVUA
.


drivers: gpio: Add reading port/pin in both direction

These changes modify the fuction of reading port/pin,
fuction return logical sum of input pin value and
output pin values for a given port. It is now possible
to read the status of pins set as output.
Signed-off-by: Kamil Gawor<EMAIL_ADDRESS>

Codecov Report

Merging #11392 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11392   +/-   ##
=======================================
  Coverage   48.37%   48.37%
=======================================
  Files         265      265
  Lines       42188    42188
  Branches    10137    10137
=======================================
  Hits        20408    20408
  Misses      17703    17703
  Partials     4077     4077

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 f2d8d93...0cefe13. Read the comment docs.

@anangl  @jarz-nordic please review.

Before this change it was not possible to get state of an output PIN and as result PIN toggling was a bit problematic.


dashboard is not reached

Current k3d version:
$ k3d version
k3d version v1.7.0
k3s version v1.17.3-k3s1

My creation command:
$ k3d create --name k3s-traefik-v2 \
    --workers 2 \
    --publish "80:80" --publish "443:443" --publish "9000:9000" \
    --server-arg "--no-deploy=traefik"

After that, I've installed last version of traefik, 2.2:
$ helm install traefik traefik/traefik -f traefik-values.yaml

where traefik-values.yaml is:
dashboard:
        ingressRoute: true
ports:
        traefik:
                expose: true

After that, traefik is deployed:
$ kubectl get pods
NAME                                      READY   STATUS    RESTARTS   AGE
metrics-server-6d684c7b5-98vrm            1/1     Running   0          15m
local-path-provisioner-58fb86bdfd-qhnvp   1/1     Running   0          15m
coredns-d798c9dd-9vl6m                    1/1     Running   0          15m
svclb-traefik-n8bxh                       2/2     Running   0          12m
svclb-traefik-8slds                       2/2     Running   0          12m
svclb-traefik-wjgcm                       2/2     Running   0          12m
traefik-5f64679b8c-fbgrn                  1/1     Running   0          12m

And traefik ingress crd is:
$ kubectl get ingressroutes.traefik.containo.us traefik-dashboard -o yaml
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  annotations:
    helm.sh/hook: post-install,post-upgrade
  creationTimestamp: "2020-04-09T07:28:10Z"
  generation: 1
  labels:
    app.kubernetes.io/instance: traefik
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: traefik
    helm.sh/chart: traefik-8.0.0
  name: traefik-dashboard
  namespace: kube-system
  resourceVersion: "632"
  selfLink: /apis/traefik.containo.us/v1alpha1/namespaces/kube-system/ingressroutes/traefik-dashboard
  uid: a038f336-dc3e-4f17-8a4e-fa42ac81c94c
spec:
  entryPoints:
  - traefik
  routes:
  - kind: Rule
    match: PathPrefix(`/dashboard`) || PathPrefix(`/api`)
    services:
    - kind: TraefikService
      name: api@internal

As you can see, entrypoint is traefik, which is listening to port 9000 (see service bellow).
My traefik service:
$ kubectl get service traefik -o yaml
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2020-04-09T08:24:58Z"
  labels:
    app.kubernetes.io/instance: traefik
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: traefik
    helm.sh/chart: traefik-8.0.0
  name: traefik
  namespace: kube-system
  resourceVersion: "640"
  selfLink: /api/v1/namespaces/kube-system/services/traefik
  uid: 9c2dca77-85b0-4dd4-97d2-5e32fbcbd026
spec:
  clusterIP: <IP_ADDRESS>
  externalTrafficPolicy: Cluster
  ports:
  - name: traefik
    nodePort: 32138
    port: 9000
    protocol: TCP
    targetPort: traefik
  - name: web
    nodePort: 32304
    port: 80
    protocol: TCP
    targetPort: web
  - name: websecure
    nodePort: 32650
    port: 443
    protocol: TCP
    targetPort: websecure
  selector:
    app.kubernetes.io/instance: traefik
    app.kubernetes.io/name: traefik
  sessionAffinity: None
  type: LoadBalancer
status:
  loadBalancer:
    ingress:
    - ip: <IP_ADDRESS>

However, when I'm trying to get access to dashboard:
$ curl localhost/dashboard
404 page not found

Running containers:
$ docker container ls
CONTAINER ID        IMAGE                      COMMAND                  CREATED             STATUS              PORTS                                                                                NAMES
6960365854cf        rancher/k3s:v1.17.3-k3s1   "/bin/k3s agent"         About an hour ago   Up About an hour                                                                                k3d-k3s-traefik-v2-worker-1
cb8e8331012c        rancher/k3s:v1.17.3-k3s1   "/bin/k3s agent"         About an hour ago   Up About an hour                                                                                k3d-k3s-traefik-v2-worker-0
b65663efd21b        rancher/k3s:v1.17.3-k3s1   "/bin/k3s server --h…"   About an hour ago   Up About an hour    <IP_ADDRESS>:80->80/tcp, <IP_ADDRESS>:443->443/tcp, <IP_ADDRESS>:6443->6443/tcp, <IP_ADDRESS>:9000->9000/tcp   k3d-k3s-traefik-v2-server

I've also checked:
$ kubectl get traefikservices.traefik.containo.us
No resources found in kube-system namespace.

Any ideas?

I have the same issue :)

@jeusdi
If you want to expose the dashboard on port 9000
you have to use the following values.yaml:
dashboard:
  ingressRoute: true
ports:
  traefik:
    expose: true

additionalArguments:
  - "--api.insecure"

By default the dashboard is not exposed for security reason.
To access it you have to use the following command:
kubectl port-forward $(kubectl get pods --selector "app.kubernetes.io/name=traefik" --output=name) 9000:9000

I will close this issue because I think your question is answered


runtime: Support async-std

Aside one for tokio, better to have a runtime support for async-std.

Another strategy is runtime-agnostic way like hyper does.
Agnostik is a library for this purpose but it unfortunately seems unmaintained.

https://www.reddit.com/r/rust/comments/fo98kc/announcing_agnostik_executor_agnostic_runtime/
I learned there is an alternative of agnostik called async_executors. This one looks more maintained and supports more runtimes including glommio.

In async-executors, API is not provided to use the current global Tokio runtime.
The discussion is here

Unlike tokio one, JoinHandle in async-executors doesn't have abort method but we could use Abortable to cancel the request.

Experimental branch is here https://github.com/akiradeveloper/norpc/tree/generic-runtime

done.


[AUTO-CHERRYPICK] Added CredScan exception for doc and test sample secrets. - branch main

This is an auto-generated pull request to cherry-pick commit c402d8b00e6888251728742a59cb819a616e9882 to main. Original PR: #6697

Closing, duplicate of #6696.


Vue Devtools not showing fields with getters

Version
4.1.4
Browser and OS info
Chrome 66 / Windows
Steps to reproduce
Create simplest class with:
get myValue ()
Add new instance to data, so it can be visible in DevTools.
myValue is not shown on the list of properties.
What is expected?
Should be shown with (...) to execute the getter
What is actually happening?
It is not shown

This is becoming a significant problem for me as well. I set some custom convenience properties (that do boilerplate lookups) and I can't tell if they're actually working due to not being able to see them.

After doing more investigation, the problem is because JSON.stringify (used internally to pass the state to the devtools) ignores any non-enumerable properties. Of course, defineProperty defaults to non-enumerable, so they're omitted! So a quick fix is marking the property as enumerable on creation. Then it does show up in devtools, but with caveats:

Property must be marked as enumerable, but enumerable defaults to false (way to go JS!)
Properties are eagerly evaluated so eg lazy properties won't be handled "right".

Number 1 is fixable by a note in the documentation reminding users to mark their properties as enumerable, IMO.
Number 2 is less easy to resolve. Because Vue makes such heavy use of properties, requiring the user to manually invoke each one is going to create a headache for the 99.9% of devs who don't care about the properties being eagerly evaluated. Any method of evaluating properties on-demand is going to require custom flags and a way to invoke functions/properties from the devtools - not something that seems to be supported currently.
Just as an idea of how this could be handled, devs could set a lazy flag on the property itself. Then, the devtools would create a dummy value for all lazy properties when capturing the state, similar to how functions are currently handled. On the display side, this property would be displayed as a link (...) that, when clicked, would trigger the devtools backend to re-serialize the state but not replacing that property for that instance only. A per-instance record of which lazy properties have already been evaluated would also be required. At this point, you might as well add support for function evaluations since it'll probably require much of the same support.
This is a huge amount of work for something that (as far as I can see) would impact almost no-one, so I personally don't see the value in working further on it.
A note in the docs would be nice, though.


Pint 1842

Proposed changes
Added documentation for Airship's Destination Action
Merge timing

ASAP once approved?

Hi @jumpingGrendel ,
Thanks for getting this PR raised!
Our docs team will pick it up and review, however I did have a quick read and left a couple of comments.
Cheers,
Joe

@jumpingGrendel @joe-ayoub-segment @tcgilbert I'm going to close this PR out as I created an editable version here: #4946


update zh-tw language

update zh-tw language
Please make sure your PR is ready to be merged !

[ok ] You added the changes in CHANGELOG.md
[ok ] You choose the right repository branch to make the PR
[ok ] You described the PR as below

Fixes #XXXX
Changes :

Related to (put here the others PR in other repositories)

update done
https://poeditor.com/projects/po_edit?id=71139&id_language=188


ng build issue with docker

After migration 11 to 12.
ng build works fine locally
but fail with docker.
/app/src/app/register/register.component.scss - Error: /app/src/app/register/register.component.scss from Css Minimizer
#15 113.9 Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at minify (/app/node_modules/@angular-devkit/build-angular/src/webpack/configs/styles.js:276:58)
#15 113.9     at minify (/app/node_modules/css-minimizer-webpack-plugin/dist/minify.js:15:32)
#15 113.9     at /app/node_modules/css-minimizer-webpack-plugin/dist/index.js:262:128
#15 113.9     at /app/node_modules/css-minimizer-webpack-plugin/node_modules/p-limit/index.js:23:31
#15 113.9     at run (/app/node_modules/css-minimizer-webpack-plugin/node_modules/p-limit/index.js:23:43)
#15 113.9     at /app/node_modules/css-minimizer-webpack-plugin/node_modules/p-limit/index.js:45:20
#15 113.9 Error: Optimization error [157.js]: Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at default_1 (/app/node_modules/@angular-devkit/build-angular/src/webpack/plugins/javascript-optimizer-worker.js:18:43)
#15 113.9     at /app/node_modules/piscina/dist/src/worker.js:141:32
#15 113.9
#15 113.9 Error: Optimization error [358.js]: Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at default_1 (/app/node_modules/@angular-devkit/build-angular/src/webpack/plugins/javascript-optimizer-worker.js:18:43)
#15 113.9     at /app/node_modules/piscina/dist/src/worker.js:141:32
#15 113.9
#15 113.9 Error: Optimization error [polyfills.js]: Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at default_1 (/app/node_modules/@angular-devkit/build-angular/src/webpack/plugins/javascript-optimizer-worker.js:18:43)
#15 113.9     at /app/node_modules/piscina/dist/src/worker.js:141:32
#15 113.9
#15 113.9 Error: Optimization error [574.js]: Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at default_1 (/app/node_modules/@angular-devkit/build-angular/src/webpack/plugins/javascript-optimizer-worker.js:18:43)
#15 113.9     at /app/node_modules/piscina/dist/src/worker.js:141:32
#15 113.9
#15 113.9 Error: Optimization error [947.js]: Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at default_1 (/app/node_modules/@angular-devkit/build-angular/src/webpack/plugins/javascript-optimizer-worker.js:18:43)
#15 113.9     at /app/node_modules/piscina/dist/src/worker.js:141:32
#15 113.9
#15 113.9 Error: Optimization error [171.js]: Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at default_1 (/app/node_modules/@angular-devkit/build-angular/src/webpack/plugins/javascript-optimizer-worker.js:18:43)
#15 113.9     at /app/node_modules/piscina/dist/src/worker.js:141:32
#15 113.9
#15 113.9 Error: Optimization error [935.js]: Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at default_1 (/app/node_modules/@angular-devkit/build-angular/src/webpack/plugins/javascript-optimizer-worker.js:18:43)
#15 113.9     at /app/node_modules/piscina/dist/src/worker.js:141:32
#15 113.9
#15 113.9 Error: Optimization error [main.js]: Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at default_1 (/app/node_modules/@angular-devkit/build-angular/src/webpack/plugins/javascript-optimizer-worker.js:18:43)
#15 113.9     at /app/node_modules/piscina/dist/src/worker.js:141:32
#15 113.9
#15 113.9 Error: Optimization error [runtime.js]: Error: spawn Unknown system error -8
#15 113.9     at ChildProcess.spawn (node:internal/child_process:412:11)
#15 113.9     at Object.spawn (node:child_process:698:9)
#15 113.9     at ensureServiceIsRunning (/app/node_modules/esbuild/lib/main.js:1718:29)
#15 113.9     at Object.transform (/app/node_modules/esbuild/lib/main.js:1633:37)
#15 113.9     at default_1 (/app/node_modules/@angular-devkit/build-angular/src/webpack/plugins/javascript-optimizer-worker.js:18:43)
#15 113.9     at /app/node_modules/piscina/dist/src/worker.js:141:32
Please feel free to check and let me know what the problem is.

Can you please provide the output of ng version?

"@angular-devkit/build-angular": "^12.2.2",
"@angular/cli": "^12.2.2",
"@angular/compiler-cli": "~12.2.2",

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

Is the node modules directory shared between the host machine and the docker image?
If so, are the two operating systems different?

@clydin I came here with the same problem and your comment helped me to fix this. Building application with Angular 12 on Windows for docker container - when added node_modules directory to .dockerignore the issue disappeared and optimization works fine!

Closing as per above comment.


Tuning for m2

Use this PR to run the tuning process for M2.
Search Space:
enc_conv_c: tune.grid_search([10, 15, 20, 25]),
enc_kern: tune.grid_search([3]),
enc_hidden: tune.grid_search([64, 128, 192, 256]),
lr: tune.loguniform(1e-5, 1e-2),
weight_decay: tune.loguniform(1e-6, 1e-3)
Config: m2
Number of epochs: 200

Current best space is
Best config: {'enc_conv_c': 25, 'enc_kern': 3, 'enc_hidden': 256, 'lr': 0.0023728538449271077, 'weight_decay': 4.8380692551037007e-05}

Current best space is
Best config: {'enc_conv_c': 25, 'enc_kern': 3, 'enc_hidden': 256, 'lr': 0.0023728538449271077, 'weight_decay': 4.8380692551037007e-05}

Really interesting! Would you report the true positive rate (TPR) and positive predictive value (PPV) with the best settings? There's code for computing those two summary statistics here:
https://github.com/prob-ml/bliss/blob/849e5a1ffa1ce4cd0ea0ac44acbd926c6764f1c9/bliss/datasets/sdss.py#L176-L186

Are we expecting /bin/tuning.py to be used with several different architectures with different parameter spaces at the same time, or is this only going to be used with the latest architecture?
I think this is especially important for designing our new config layout for tuning. I imagine this can be done in at least two ways.

Include relevant search space for each model, dataset, optimizer in its own config file. For example, the adam.yaml would include a range for learning rate and weight decay. Add another stand-alone tuning config file that includes generic settings such num_gpu_for_tuning, max_epoch_to_search. This might be a good approach when used with several different architectures.
Have only one config file for tuning with all the settings included. Whenever there is an architecture change, we update the config content in parallel with the possible search space accepted by our model. This might be easier if we only need /bin/tuning.py to work with the latest architecture at hand. This might be easier to manage as our model evolves since I suppose part of the architecture design is based on the previous tuning run.

Are we expecting /bin/tuning.py to be used with several different architectures with different parameter spaces at the same time, or is this only going to be used with the latest architecture?
I think this is especially important for designing our new config layout for tuning. I imagine this can be done in at least two ways.

Include relevant search space for each model, dataset, optimizer in its own config file. For example, the adam.yaml would include a range for learning rate and weight decay. Add another stand-alone tuning config file that includes generic settings such num_gpu_for_tuning, max_epoch_to_search. This might be a good approach when used with several different architectures.
Have only one config file for tuning with all the settings included. Whenever there is an architecture change, we update the config content in parallel with the possible search space accepted by our model. This might be easier if we only need /bin/tuning.py to work with the latest architecture at hand. This might be easier to manage as our model evolves since I suppose part of the architecture design is based on the previous tuning run.

Good question, I hadn't thought about that. If it's simpler to suppose there's just one architecture, I'd start with that, and make it more complicated later if it turns out to be necessary

PR looks great, please merge when ready

PR looks great, please merge when ready

PR looks great, please merge when ready

Other than #164, I have finished most of what I had planned. Ready to merge on my end.
@zzhaozhe-profolio

PR looks great, please merge when ready

Other than #164, I have finished most of what I had planned. Ready to merge on my end.
@zzhaozhe-profolio


Proper params for geocoding formatter

We should change the internal API definition of the params for geocoding so that we avoid unneeded parsing, transformations and guessing in both front and back ends.
There are limitations in the format of the formatter itself because it is impossible to tell apart what is what from the order of the "atoms" of the formatter string (street, state/province, country, additional information) despite the user is providing that information explicitly.
Proposal:
{
  "input": {
    "address": {
      "type": "column",
      "value": "direccion"
    },
    "province": {
      "type": "column",
      "value": "provincia"
    },
    "state": {
      "type": "freetext",
      "value": "es"
    },
    "additional": null
  }
}

(we can keep the current formatter for backwards compatibility)
cc/ @javisantana

is this blocker for gmaps geocoding or is a good to have?

No, it is not. It will improve accuracy.

Let's remove it from the next sprint and revisit later. I realized it would require more effort on both street-level geocoders to make a difference, apart from passing/transforming parameters.

bump! just in case you want to prioritize this. I'll add it to my list of "things I would do"

@viddo is "redoing" the geocoding dialog, I encourage you to talk with him, or if you need help we could fix a meeting.

FYI, for now I'm implementing the existing behavior

Let me close this ticket, geocoding is now an analysis in the new builder, so probably it doesn't make any sense now :).

okey dokey :+1:


Documentation Missing: DisplayAs

Describe the bug
There is no real documentation on the DisplayAs functionality which was discussed at https://github.com/dotnet/interactive/issues/1983#issuecomment-1169491522 . It's really useful so I think it should at least be mentioned somewhere 😊

Closing as a duplicate of #2078.


Possible bug with the storybook library

This issue concerns the storybook section in the front-end guide.
I failed to reproduce the outcome described in the guide for the front-end elements.  While the code was executed (npm run dev), the following codes weren't display on the storybook server (localhosts:3001) - Neither by their url, nor do they appear on the side-menu.
a. OnClick state of the button and the Button.data.js. didn't work for me.
NB- the button itself is created and displayed on storybook server, but I cannot click on it.
b. Other components that were created with the same code, but under a different component name could not be displayed, pass to the stroybook server.
c. Building a container - I tried under WordPageCount.js as well as other titles. I could not observe it on storybook.
I verified it couple of times, and to my best observation the code was copied exactly as described, including related files.

Hi @DBonbon and thanks for the bug report. I went through your different scenarios, here are some comments/questions on each scenario:

a. OnClick state of the button and the Button.data.js. didn't work for me

I just tested this and cannot recreate the error.
I followed the following steps:

First i ran npm run new Button

Modified the Button component according to https://github.com/Frojd/Wagtail-Pipit/blob/main/docs/frontend-developer-guide.md#writing-the-javascriptjsx

Modified Button.data.js with:

export default {
    'text': 'Button text',
    'onClick': function() {console.log('clicked');}
};

Then then opened storybook, opened "Button With Data" clicked on the button and could see instructions and I see the "clicked" string in my web browser inspector under the tab console.

b. Other components that were created with the same code, but under a different component name could not be displayed, pass to the stroybook server.

Not sure how what to test or recreate, could you provide more context here? Such as the commands you tried to run. I ran  npm run new Box just to make sure generating a component with another name works and it did.

c. Building a container - I tried under WordPageCount.js as well as other titles. I could not observe it on storybook.

Cannot recreate the error. I ran npm run new:container WordCountPage and observed the container appear in storybook.

I'm closing this issue due to inactivity. Feel free to open if problem still exist.


Error: write EPROTO

I'm using
ip-192-168-1-52:api loretoparisi$ node --version
v12.13.1
ip-192-168-1-52:api loretoparisi$ npm --version
6.12.1

Error: write EPROTO<PHONE_NUMBER>:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

    at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:87:16) {
  errno: 'EPROTO',
  code: 'EPROTO',
  syscall: 'write'
}
 [Wed Nov 20 2019 17:40:30 GMT+0100 (Central European Standard Time)] RequestGetP error:{
  "errno": "EPROTO",
  "code": "EPROTO",
  "syscall": "write"
}
Error: write EPROTO<PHONE_NUMBER>:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

    at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:87:16)
Error: write EPROTO<PHONE_NUMBER>:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

    at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:87:16)

I had the same problem and solved it by using agent option
agent: new Agent({ rejectUnauthorized: false })

Agent is from https module.
import { Agent } from 'https';

I hope it works for you, too.

thank you @9w!

just had a similar problem,
my dev machine had a v10.15.3 NODE installed
and in the remove i installed the latest version v12.x atm
going back to v10.15.3 quick fixed it for me

@9w Hello.. Can you tell me where exactly should this modification be applied ?

@ucfmohamed  Just add it to the options in your request like this.
const options = {
  url: 'https://api.github.com/repos/request/request',
  method: 'POST',
  ...,
  agent: new Agent({ rejectUnauthorized: false })
};

function callback(error, response, body) {
  ...
}

request(options, callback);

I have the same problem like this.
but I don't know the reason why it works?


Can't use self.log as an instance variable in a Callback

Bug description
The log attribute of the callback seems to be replaced at some point.
Not sure if this is expected (to me it's weird).
Below is the simplest code to reproduce this behavior.
What version are you seeing the problem on?
v2.1, v2.2
How to reproduce the bug
class MyCallBack(Callback):
    def __init__(self) -> None:
        super().__init__()
        self.log = 123
        print("------------------", self.log) #123

    def on_train_start(self, trainer: Trainer, pl_module: LightningModule) -> None:
        super().on_train_start(trainer, pl_module)
        print("------------------", self.log) #expect to print "123" ,got "<bound method LightningModule.log of MyModel(..."

if __name__ == "__main__":
    model = MyModel()
    trainer = Trainer(
        max_epochs=3,
        callbacks=[
            MyCallBack(),
        ],
    )
    trainer.fit(model)

Error messages and logs
print message:
------------------ <bound method LightningModule.log of MyModel(
  (fc): Linear(in_features=1, out_features=1, bias=True)
  (criterion): MSELoss()
)>

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response
cc @awaelchli @carmocca

Hey @blackwint3r
self.log is a reserved name for the logging method on the callback. You can call self.log("name", value) in the Callback just like you would in the LightningModule. Therefore, you can't use it as a variable. Please consider using a different name.

OK I got it, thanks for your explanation.


(PUP-7526) Adds pip2 provider

Fresh pull request for master branch per comment https://github.com/puppetlabs/puppet/pull/8300#issuecomment-686322452

Can one of the admins verify this patch?


Drop support for 2014-era Linux.

Merging pytorch (6aa1f4e) caused

OSError: dlopen: cannot load any more object with static TLS

on Debian 8 and Ubuntu Trusty ( caught by #2690  :) ).

This is a known issue with pytorch, see e.g.
https://github.com/pytorch/pytorch/issues/2083
https://github.com/scikit-learn/scikit-learn/issues/14485
https://github.com/pytorch/pytorch/issues/2575
https://stackoverflow.com/questions/14892101/cannot-load-any-more-object-with-static-tls
Apparently there might be a workaround involving reordering import statements, but I think the root issue is that pytorch doesn't get testing on "obscure" platforms. Including pytorch means we can't reliably support them.

An alternate fix would be to try to reorder the import statements until this works for the old Linux. I'm not sure what we want to do.

Note: Travis passing on this PR isn't going to mean it's actually fixed, because it's specifically failing on the extra platforms that aren't tested on every PR. I'm pretty confident I didn't make any typos, however.


Undefined class 'ThreadSafeArray'

I have to choose between PM-NG and Customies-NG. It doesn't make sense!

pthreads not work with new version of PM-NG

[ERROR] Selected PHP binary does not satisfy some requirements.
Unable to find the pmmpthread (pmmpthread) extension.

pmmpthread not work with Customies-NG

pmmp\thread\NonThreadSafeValueError: "Closures with non-thread-safe $this cannot be made thread-safe" (EXCEPTION) in "plugins/Customies-NG-pm5/src/task/AsyncRegisterBlocksTask" at line 31

you need pmmpthread for both to work

Closures with non-thread-safe $this cannot be made thread-safe

like I said in the previous issue, it's caused by your plugin. #3


fix: f233464 applied only to compiled lldebugger.lua

The previous PR (commit f233464dfcee21a3de9bd9655ebdf054b3bfe0d6) did not apply the patch to the source debugger.ts file, so the change would be lost in subsequent releases and in fact also during publish, which is why the last version, had no real change.
This PR simply adopts the intended change for the debugger.ts file.
@Ismoh could you please explain the steps to me for publishing a new version? I believe this PR would make a perfect example.

Everytime a new tag is pushed, GitHub action workflow publish a new version.
I've created some vscode tasks to generate all necessary files, but looks like there is something missing?
Let me double check locally.

Yea found it. You need to modify *.ts files and then run npm run bundle or VSCode task Bundle.
I've messed up your PR, but cleaned it up already. There is a task to create new releases, but you have to run it locally in VSCode: Create new release. Don't forget to update the version in package.json and also update CHANGELOG.md


Fix duplicate tags in student form

Need to investigate how this happened:

This seems to only happen when you have multiple schools selected on the form.
To reproduce:

Edit a student application and select 2 schools
Select a tag

The tag will show as selected once, but two entries will be added in the pivot for it. This effect also seems to multiply when you select and deselect more tags.

I'm looking into this as well. It looks like the duplication doesn't occur until the application form gets submitted... At least in for what I've seen.

@betsyecastro I figured it out and fixed it. Deployed and manually fixed that one student that had all the duplicate tags.


implement BGP discover for equinix_metal_project

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description
Equinix Metal projects provide a number of BGP settings. These are exposed in Terraform through a few resources, but are initiated by equinix_metal_project.
One of the resources of the Metal API that has not been exposed in Terraform is the ability to force a sync or discover over BGP neighbors in the project (POST /projects/{id}/bgp/discover).
Create a method to signal this API endpoint via Terraform.

New or Affected Resource(s)

equinix_metal_project

Potential Terraform Configuration

resource "equinix_metal_project" "foo" {
  ...
  bgp_discover_since = "<date>"
  #  the diff would be based on desired date (bgp_discover_since) > observed state
  #  (determined by updated_dt or finding a matching event).

  # computed field could also be added, but perhaps not necessary?
  # would be named bgp_discovered bgp_last_discovered ?
}

I don't think bgp_config should be used because the API path for projects/{id}/bgp/config is separate.
https://registry.terraform.io/providers/equinix/equinix/latest/docs/resources/equinix_metal_project#example-with-bgp-config
References

Depends on https://github.com/packethost/packngo/issues/316

Alternatively, or perhaps in addition, whenever the Terraform provider performs BGP-affecting actions, a BGP discover call could be made (equivalent to the "Update Now" button on the BGP Networking panel in the Metal console). This may be a little magical for TF, so if implemented this should be behind a behavior flag in the resource or the provider.


Reduce allocations in getAllExprents

This PR improves Exprent#getAllExprents by making it not allocate more than once. Previously, every single exprent in the tree would allocate it's own arraylist, which means a lot of unused arraylists were allocated, as the lists are only used to add onto the existing list.

From SuperCoder on discord
Before

after

Honestly this could use some more testing and better numbers, but meh its simple enough change.


Move a work item to another project resets all states

Under the section https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/remove-delete-work-items?view=azure-devops&tabs=browser#move-a-work-item-to-another-project
It says: "Also, the system automatically resets the State and Reason fields to the default initial values for the work item type that you move"
This behavior should be made optional (at least for State) to be able to preserve state of work items when moving them to another project.

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

ID: 0e9f02cb-f094-d6bc-ca7b-973db9de0082
Version Independent ID: 1af6a7f5-9e99-ec99-081d-c0bf9e7ac5f5
Content: Move, change, and delete work items - Azure Boards
Content Source: docs/boards/backlogs/remove-delete-work-items.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@thomasvehus - Thank you for your feedback. Since this is a proposed change to a feature, please make your suggestion at our Developer Community page.


NY - Promote to production

Problem statement
NY needs to be set up in the production environment to receive via REST.
Acceptance criteria

[x] Receiver filters allow data for NY
[x] REST transport is operational
[ ] NY verifies that feed is working as expected

To do

[x] Add REST transport information to receiver
[x] add secrets to Azure

SUCCESS!!! Need to verify with NY but our log shows a REST send success.


⚠ ClamAV has degraded performance

In 0474e32, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in dc40eb0 after 5 minutes.


Organize all protos in mapping in a single folder.

Following the structure of the other subfolders in this repo, this PR moves all protos into a proto subfolder underneath mapping.

After this goes in, there might be some empty (untracked) folders in your checkout tree. To clean them up you can run:
git clean -fd

@wally-the-cartographer merge


Internal admin page secured by check on user roles

Changes in this PR

add new page /admin
add new User scope analysts

Screenshots of UI changes

 Internal admin page secured by check on user roles


Set views and static content to have 1hr cache headers

We configure Whitenoise for the assets and set up a middleware for the cache headers.
1 hour value based on legislation.gov.uk -- do we want s-maxage and no-transform?

 Cache headers in PUI


Naming of multiple VM's goes wrong..

Hi guys,
There is an issue with the deployment of VM's. If you choose 2 or 3 zones and name the VM's MyVm1, MyVm2, MyVm3, the result is that after deployments all VM's have the same name, the name of the last VM (MyVm3).
<EMAIL_ADDRESS>
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0662764d-dc84-9a95-f25b-ca254fe725b1
Version Independent ID: 9b6dda82-0732-e40f-adc1-19bfbc6650ed
Content: Create zonal VMs with the Azure portal - Azure Virtual Machines
Content Source: articles/virtual-machines/create-portal-availability-zone.md
Service: virtual-machines
GitHub Login: @mimckitt
Microsoft Alias: *mimckitt

Thanks for bringing this to our attention. We are actively investigating and will get back to you soon.

Thanks for bringing this to our attention. We are actively investigating and will get back to you soon.

@aramsmith
Thanks for reporting this, and sharing the details. From the screenshots shared the VM names are all different, but the computer names are identical.
I am checking with internal team on this and will keep you posted.

#assign: @mimckitt

#assign: @arushisharma27

The following users don't have valid GitHub IDs, or are not collaborators on this repo: arushisharma27

@aramsmith  Since you are an FTE, I am going to close this issue and add you to the internal thread.
#please-close


[CELEBORN-599] Consolidate calculation of mount point

What changes were proposed in this pull request?
Currently DeviceInfo#getMountPoint match the longest string to determine which mount point a directory attached. May get wrong judges in some scenarios.
Assume mount points are /, /data,and dir is /data1. /data1 will attach to /data(should be /), and actually create shuffle dir in /.
Why are the changes needed?
Improve usage, and avoid filling the wrong mount point
Does this PR introduce any user-facing change?
No
How was this patch tested?
UT and cluster test

Thanks, merged to main for 0.3


[FEATURE] add salutation select to the register form

Describe how this feature will help us improve

Add a possibility of selecting the salutation during the registration progress
Is your proposal related to a problem?

Describe the solution you'd considered

TODO:

add appropriate service/method in shopware-api-client package - to get the list of available salutations for current sales channel (GET https://shopware-2.vuestorefront.io/sales-channel-api/v1/salutation)

add select to the registration form

use chosen salutationId withing the register request

consider implementing it on "my account" edit forms.

Acceptance criteria

[x] the code is 100% covered by tests
[x] there is select with available salutations which can be chosen
[x] user can be registered with the selected salutation

nice to have:

[ ] at least one e2e test is implemented, let's say: only for seeing the select with possible salutations

related issue: #360

user  Error is not defined in register form


[yml/spaced-comment] Rule detected problems

The rule defined in here: https://github.com/ota-meshi/eslint-plugin-yml/blob/master/src/rules/spaced-comment.ts
Has at least, IMO one regex problem.
This is considered an error:
## comment

Because it states it should be:
# # comment

From what I understand from this rule, it should only validate if there are spaces in between the comment "char" and the actual string itself. I understand if everything after the first # is interpreted as the comment itself, but shouldn't the same char (#) of making comments be supported? 🤔
I'm thinking of comments such as:
##########
# HEADING #
##########

That will break because of this rule. (to whom it might concern, in my case the ## is fine 😆)

You can set the rule options to accept your favorite comment style.
https://ota-meshi.github.io/eslint-plugin-yml/rules/spaced-comment.html#options
https://ota-meshi.github.io/eslint-plugin-yml/playground/#eJxdjLEKwyAQQH/lOIcslu5ugYa2S3+gZhBzQ0DP4FnaIP577FTo2x4PXkWfFkKDCkjCygX2GM6yOU/LyacYiYuBJ+WcsgYX3m4XDRXo42kra2LpdVDDDA1my5bVjy5wm8bL/XEF9Ve6Tt+nZdSYX4EETW3tAOBPK9M=
https://ota-meshi.github.io/eslint-plugin-yml/playground/#eJwtyzsKwzAQRdGtPEaFG4X06r0K24WQpgjWx8w4BCG0d8ch5eVyOoUamRwZsKZXOdFyeurhA8dHqDlzOR0WFqli4dPHN7XoyF52Fv2uyUwbBra1rMUY/M2v5luRJXknVnJ9jAtI6iYJ


upcoming: [M3-8077] - Add Distribution Icon to Image Select v2

Description 📝

Adds the distribution icon to the new ImageSelect on the new Linode Create flow 🖼
Add unit test to ensure Icon renders

Preview 📷

Before
After

How to test 🧪
Prerequisites

Turn on the Linode Create v2 flag using local dev tool

Verification steps

Verify you see the distro icon of the selected distribution 👀
Compare styles to production make make sure they look very similar

As an Author I have considered 🤔

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[ ] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

Working on this! Seems that Safari handles it a bit different than Chrome 😵💫


[BUG] Fix faster animation when app send to background and gains focus again

Added observers to notification center to control app status to stop/start animation when send to back/gains focus.

I've committed again using iOS macro only because I can't test this code with watchOS and tvOS.

Thanks for it!


Removing vector from group throws an error

Describe the bug
Removing an ol/layer/Vector from an ol/layer/Group generates a js error when no listeners keys are associated to that specific layer
To Reproduce
Steps to reproduce the behavior:

Push an ol/layer/Vector to a group group.getLayers().getArray().push(vector);
Remove the same layer groupLayer.getLayers().remove(vector);
function handleLayersRemove_ goes in error due to undefined listeners for the given layer

Expected behavior
It should remove the layer from the group without throwing the error
Temporary fix
Checking if the listeners key for the given layer are defined
e.prototype.handleLayersRemove_ = function(t) {
  var e = o(t.element);
if (typeof this.listenerKeys_[e] !== "undefined")
   this.listenerKeys_[e].forEach(H),delete this.listenerKeys_[e], this.changed() }

You should use group.getLayers().push(vector); otherwise the ol/Collection won't fire the necessary events / update its length.


Unhide inversesqrt() function in mx_math.metal

inversesqrt() is currently inside of a #ifdef __DECL_GL_MATH_FUNCTIONS__ guard, which means it is not visible inside of OpenUSD's Storm hdMetal backend.
This PR moves it outside of the guard, and renames the function to mx_inversesqrt() to avoid possible name conflicts in other shader generators.

Aren't we going to need a corresponding definition of mx_inversesqrt() in genglsl/lib/mx_math.glsl?

Just for my own understanding, what is different about inversesqrt() here versus the other functions inside the #ifdef __DECL_GL_MATH_FUNCTIONS__ guard? I'm guessing it has something to do with where it's being used, but that's not clear to me.

TL;DR - I think inversesqrt is not currently defined by other shader code added by hydra - but it may be added in the future.
I don't claim to fully understand the backstory here - but the MaterialX code generator in Hydra storm for Metal does not set __DECL_GL_MATH_FUNCTIONS__.  It also introduces other shader pre-amble before the materialX code generation.  There was a previous case (mod I think) where functions were being defined both in the preamble and by the shader code generated by MaterialX, so there the path forwards was to give the function a MaterialX specific prefix.  I'm actually wondering if we should do that for all the functions inside of the __DECL_GL_MATH_FUNCTIONS__ guard, and then that means not using the builtin GLSL versions of those functions but instead calling the mx_ prefixed wrappers.
@jstone-lucasfilm - what do you think?  Should we refactor the guard away completely, and just move to using mx_ prefixed function calls that wrap the GLSL and MSL implementations, where they differ?

@ld-kerley I believe the current design choice, using the __DECL_GL_MATH_FUNCTIONS__ guard around MSL implementation of common GLSL functions, was part of the original implementation from @Morteeza of Metal support in MaterialX.
If Storm is not currently setting this flag in Metal builds, then I can imagine two potential paths forward:

Update Storm to consistently set __DECL_GL_MATH_FUNCTIONS__ in Metal builds.
Remove this guard entirely from MaterialX, defining mx prefixed helper methods that are implemented in both GLSL and MSL.

How challenging would it be to implement approach (1), where the guard is set in Storm?  If that's not a practical solution, then I'm completely fine with pivoting to approach (2).

I don't think it would be terribly hard to do (1), though getting the PR merged with Pixar can take some time sometimes.
I think I'd vote for (2) though, as it will isolate us from potential future conflicts.  Like the previous mod() conflict here.
I think it would be good to merge this PR for now, so that anyone who happens to be trying to render OpenPBR, with Metal in Storm will get the fix, and I can put up another PR soon refactoring out __DECL_GL_MATH_FUNCTIONS__.


update BDD

update BDD

IBM Cloud toolchain: Delivery Pipeline deployed customers to dev, including commit b53eb12a6406edd723126c7b60e00ff1ae44c62e

IBM Cloud toolchain: Delivery Pipeline deployed customers to prod, including commit b53eb12a6406edd723126c7b60e00ff1ae44c62e


feat(TezosNodeWriter): Allow users to override the default (gas_limit and storage_limit) when estimating operations costs

This commit will allow users to override the default (gas_limit and storage_limit) when estimating operations costs.
Why is this change necessary?
hard_storage_limit_per_operation constant seems to have changed from 60000 to 32768 to  in Hangzhou proposal.
_Mainnet:_ "hard_storage_limit_per_operation":"60000"
_Hangzhounet:_ "hard_storage_limit_per_operation":"32768"

Currently, it is not possible to use estimateOperation method when using Hangzhounet because ConseilJS enforces the old constant value of 60000. Defined by TezosConstants.OperationStorageCap.
(permanent: proto.011-PtHangzH.storage_limit_too_high)

indeed. granada constants vs
hangzhou constants.


Fix/swap profitability

Implements a selection mechanism to the Optimus agent to bridge/swap assets only if transaction fees are lower than the transacted amount and the amount exceeds a set threshold.

Not to be merged before the launch


Return captured barcode image

I would like to be able to obtain the photo the which was used to read the barcode. The changes in this pull request allow this to happen. The image returned in the result is optional and off by default. When off does not change the behaviour.

missing file?


⚠ Bofrost.at has degraded performance

In 7c02838, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1691 ms

Resolved: Bofrost.at performance has improved in c600497 after 13 minutes.


getting ready for rails 6

i'm currently preparing for migration to rails-6 beta1.
the test-suite is running https://github.com/penseo/acts_as_paranoid/pull/1
since i do not have any idea what i'm doing here, please gimme some help.
cheers!

Got my hopes up but this fork has nothing to do with Rails 6....

Latest should work with rails 6!

For me it works with rails 6.0.0.rc2. However when I change rails version to 6.0.0, I get the following error on bundle update/install:
Bundler could not find compatible versions for gem "activerecord":
  In snapshot (Gemfile.lock):
    activerecord (= 6.0.0)

  In Gemfile:
    acts_as_paranoid (~> 0.6.0) was resolved to 0.6.0, which depends on
      activerecord (>= 4.2, < 6.0)

    rails (~> 6.0) was resolved to 6.0.0, which depends on
      activerecord (= 6.0.0)

Is it just me?

@vakrolme the latest gem release (0.6.0) does not support Rails 6 (I think @phoet means latest master).
However, I'm preparing release 0.6.1 right now, which will include Rails 6 support :rocket:.

... and released it is.


Feat/lyne link button

Preflight Checklist

[ ] I have read the Contributing Guidelines for this project.
[ ] I agree to follow the Code of Conduct that this project adheres to.
[ ] I have searched the pull request tracker for a Pull Request (PR) that matches the one I want to submit, without success.

Issue
This PR Closes #
Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Build (npm run build) was run locally and any changes were pushed
[ ] Lint (npm run lint) has passed locally and any fixes were made for failures

Changes
Changes in this pull request:

Browsers
I tested the build on the following browsers:

[ ] Firefox Desktop
[ ] Chrome Desktop
[ ] Safari Desktop
[ ] Firefox Mobile
[ ] Chrome Mobile
[ ] Safari Mobile
[ ] Opera
[ ] Brave

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

Mentions

@lyne-design-system/core

Was originally based on the lyne-link PR. Will have to re-work that part, once the lyne-link PR is merged.

Codecov Report

Merging #836 (85b4e1a) into master (bfa3e0f) will increase coverage by 1.98%.
The diff coverage is 93.33%.

:exclamation: Current head 85b4e1a differs from pull request most recent head c0188d3. Consider uploading reports for the commit c0188d3 to get more accurate results

@@            Coverage Diff             @@
##           master     #836      +/-   ##
==========================================
+ Coverage   47.77%   49.76%   +1.98%
==========================================
  Files          15       16       +1
  Lines         607      633      +26
  Branches      142      147       +5
==========================================
+ Hits          290      315      +25
- Misses        294      295       +1
  Partials       23       23

Impacted Files
Coverage Δ

...c/components/lyne-link-button/lyne-link-button.tsx
92.85% <92.85%> (ø)

src/components/lyne-link/lyne-link.tsx
93.33% <100.00%> (+2.70%)
: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 d79b84f...c0188d3. Read the comment docs.


Change account requests do not have the no-cache header

This causes the account to not change on some browsers or when using cloudflare.
Solution:
add
$this->oHttp->ServerNoCache();
to ServiceChange() in ServiceActions.php
this should also be added to ServiceInfo(), or the phpinfo page could be accessible even when admin is not logged in.

Thanks


Macos alt activator

Description
This changes the semantics of supplying alt: true to CharacterActivator on macOS and iOS only so that specifying alt: true means to compare the supplied character with the characterWithoutModifiers field on the raw key data as opposed to the character.  This is because on these platforms, the Option (a.k.a. Alt) key modifies the character produced from the keyboard.  The expands the usefulness of the CharacterActivator so that you can, for instance, detect the ß character directly (so that pressing "option-s" on a US QWERTY keyboard, or pressing 'ß' on a German keyboard triggers it), or you can insist that the key be a combination of the Option key and the 's' key, so it only matches the US keystroke, but not the German one.
The need to support this comes from needing to support accelerator keys in menus drawn by Flutter. Since accelerators are derived from the characters in the localized label, but operate only when the option key is down, there needs to be a way to look for the unmodified character from the label while the option key is down. Otherwise it's impossible to, for instance, define an accelerator that triggers on an "s" keypress (where the "s" comes from the letter after the "&" in a label), since having the Option key down will cause it to produce a "ß" instead.
In order to simulate these key presses in tests, I had to add an additional parameter to the key simulation functions to pass the unmodified character. I cried a little when I did this, because I know that there is no equivalent for unmodified characters in ui.KeyData key events. We eventually will need to add some way to handle transmitting unmodified characters there, but I didn't address that with this PR.
Related Issues

https://github.com/flutter/flutter/issues/23600

Tests

Added tests for option key handling on macOS and iOS.

I'm deeply concerned how this change (and the CharacterActivator::alt change as a whole) should pan out as we transition into KeyEvent, which will not provide detailed characters and charactersWithoutModifiers but only logicalKey and character.
IIRC, on macOS, Option-S produces logicalKey: .keyS and character: 'ß'. Should we revert CharacterActivator::alt and make all Alt-LetterKey shortcuts use SingleActivator instead?

Yep, I'm concerned too, but I don't see an alternative yet.

Should we revert CharacterActivator::alt and make all Alt-LetterKey shortcuts use SingleActivator instead?

I can't: there's no mapping from a character to a LogicalKeyboardKey, and the accelerator triggers need to come from localized strings, where the translators have no knowledge of Dart or Flutter.

After talking with Hans, we decided that we just won't support menu accelerators on macOS. The native menus don't support it, so it would be odd anyhow. Instead users will press "Ctrl-F2" to focus the menu, and then navigate with arrow keys after that. So, I could just close this, but...
It is a little weird on macOS to use the alt:: to use it is kind of redundant with the character produced. (e.g. CharacterActivator('ß', alt: true) is the same as CharacterActivator('ß'), and CharacteActivator('s', alt: true) will never fire). So we may still need something like this PR.
We still need support for alt: on other platforms, regardless.

I just realized I haven't followed up on this PR yet. Sorry for the delay.
LGTM.

I'm going to close this until we can get some consensus, and a clearer use case shows itself.


Horizontal scroll in mobile view

https://adobe.enterprise.slack.com/files/W4RRL6DDY/F05AC602R7Y/screen_recording_2023-06-01_at_10.01.51_pm.mov

should be fixed by #31


[Feature] Remove required dependency on Microsoft.Azure.Core.NewtonsoftJson from Management SDK

It would be great if the Management SDK did not have a dependency on Microsoft.Azure.Core.NewtonsoftJson
Instead, most other Azure/MS packages will ask you to add Microsoft.Azure.Core.NewtonsoftJson only when you need it, so that you can then supply an instance of NewtonsoftJsonObjectSerializer.
Could you remove it as default and then update your documentation?

As we have supported Newtonsoft.Json as serialization library for transient mode at first, it is a breaking change to remove the support as default, and we don't have a plan to upgrade the major version. Users can always override the Microsoft.Azure.Core.NewtonsoftJson version by declaring the dependency in their csproj files, and we also always suggest users adding the dependency explicitly in documentation. Do you encounter any problems following the doc?
Considering removing the dependency on Microsoft.Azure.Core.NewtonsoftJson without breaking users' code, I think what we can do here is to copy the source code of Microsoft.Azure.Core.NewtonsoftJson which only contains 2 files to Management SDK, thus we don't have the dependency on Microsoft.Azure.Core.NewtonsoftJson, but Newtonsoft.Json is still depended. Please let us know if the solution really makes a difference to you.


Add instructions configuring VS2015 to compile sln

Solution name updated!  Should we include instructions about removing the sdk.version from global.json before opening in VS?  I couldn't find any info anywhere on how to install 1.0.0-preview3-003161, just .NET Core Tooling preview 2 which seemed to be able to compile the project adequately.
BTW, Thanks for contributing the project.  Looks very useful!

Thanks!
I guess we could pull the script out from appveyor.yml and use that for instructions? As you probably know, those tools are still not yet 1.0 stable, so we expect the specific versions to change in the coming weeks

Thanks for merging!
I think it's good for now.  When the tooling reaches RTM we can update if necessary.


Mobile app- Drag and drop files in this box is not working in client folder

Mobile app- Drags and drop files in this box is not working in client folder
files goes to file manager not in document folder


fix(load): allow function to be exported (as docs say)

What: closes #88
Why: Because we document that you can export a function that returns
a configuration, but it doesn't actually work.
How: Add some logic to loadConfig in src/bin-utils/index.js to
handle the case when the config is a function. Also, we need to pass the
input along, so I had to make a few other changes as well. Also added
fixtures and tests for this.
This also adds @erikfox to the contributors table for reporting the bug! Thanks!

Codecov Report

Merging #98 into master will not impact coverage.

@@          Coverage Diff          @@
##           master    #98   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          11     14    +3
  Lines         260    273   +13
=====================================
+ Hits          260    273   +13

Impacted Files
Coverage Δ

src/bin-utils/fixtures/bad-data-type-config.js
100% <100%> (ø)

src/bin-utils/fixtures/function-config.js
100% <100%> (ø)

src/bin-utils/index.js
100% <100%> (ø)
:white_check_mark:

...in-utils/fixtures/bad-function-data-type-config.js
100% <100%> (ø)

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 033bbda...e57497f. Read the comment docs.

Anyone wanna review this really quick?


Revert "New version of update-template branch"

Reverts hmcts/cnp-module-action-group#15

What's wrong with it? might be better to fix forward?

Nothing is wrong with this module, div-perftest is not allowing the TF upgrade, and now wants the old modules available before it will do the tf update. I think perftest is very neglected. I'm hoping this branch helps it through. Will close the PR/branch once its not required.


Add the team entity to Slack if it doesn't exists and return it in pr…

Automatically creates and returns the team entity in Slack, in case user scopes exist in the auth flow.
If there is no user scopes provided, it just creates the team entity.

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in<EMAIL_ADDRESS>:rocket:


Records passed to externals can complain about field never being read

Use case: Defining things like configuration objects that are only intended to be passed into externals.
type config = {size: int}
type something

@module("something") @val
external makeSomething: config => something = "create"

@live
let something = makeSomething({size: 5})

reanalyze complains that size in config is never used to read a value. The intention however isn't to ever read from the record, only construct it and pass it into the external.
Adding @live to the field alleviates the problem, and with the new "suppress warning for a full type", maybe the best solution is to use that. However, if it could be inferred that the record is in fact passed into an external, that'd be pretty slick. I worry a bit that having to annotate things you do often becomes noisy. What do you think?

Closing this as it's now possible to annotate a full record with @live, and that solves this issue.


How does browser swap in the new module?

Hey guys, does anyone understand how ES Module's HMR works under-the-hood (for example in Vite or React Fast Refresh)? i.e. How is it able to swap out a modified module at runtime?
Usually, every time you change a module, browser will refetch that module via HTTP.
But after that, how does the browser replace the old module, and have the new code take into effect?
The only thing I found is https://itnext.io/hot-reloading-native-es2015-modules-dc54cd8cca01, is this the solution we're taking?

https://github.com/snowpackjs/esm-hmr/blob/152fffe555e9281822553b495edbc95ccb6a41b2/src/client.ts#L131-L137
It uses module versioning and dynamic imports to "reload" modules without deleting the module cache. The loaded content is then passed to import.meta.hot.accept for consumption.
Also, commenting this for my own future reference


Type of expression is ambiguous without more context

Can someone help me why i am getting this error message at compile time.
import SwiftyUserDefaults

extension DefaultsKeys {

    static let latestProjects = DefaultsKey<[[String: AnyObject]]?>("latestProjects")

}

// Error: Type of expression is ambiguous without more context
Defaults[.latestProjects] = projectsJson

The problem is with your definition of the key type. Is there a reason why you have two square brackets? You need an array of dictionary?
When you get this error it's because the compiler can't assume the type is correct.

Yes the problem is only with [[String: AnyObject]]. Other types are working fine. Could you tell me what is the problem as i need to store array of dictionaries. Am i doing something wrong ?

Not sure, I've played around a bit, it seems like a compiler issue.

I just got that error too. I assume the library doesn't support multidimensional arrays?

DefaultsKey<[String: Bool, String: Bool]> also can't do this or this: [Bool, Bool]

I just got that error too. I assume the library doesn't support multidimensional arrays?

No, it doesn't. Until Swift becomes more powerful, you can only define and use DefaultsKey on one of the supported types. You can, however, quite easily extend NSUserDefaults and add support for a given DefaultsKey type.


affilateEmail

hjuik

This PR was automatically closed and added to a release PR: https://github.com/suvikram/apex-recipes/pull/41


Put shadow to Accordion component

How can I put a box-shadow to an Accordion?
I have the next code but no shadow in
export default function Accordion() {
	return (
		<View style={{
			shadowColor: '#000',
			shadowOffset: { width: 0, height: 2, },
			shadowOpacity: 0.25,
			shadowRadius: 3.84,
			elevation: 5
		}}>
			<Accordion dataArray={array} expanded={0}/>
		</View>
	);
}

Hi @Pmz94 , on which platform you are working on Android or iOS?

HI @Pmz94 , closing for now due to inactivity. Please let know us know if the issue still persists with more details.
Thanks


bug found on website

Discussed in https://github.com/sanjay-kv/Open-source-Practice/discussions/1145

Originally posted by singhabhinendra October 14, 2024
In Headline

Elaborate the bug

If this is not yet done please assign me this @sanjay-kv

i dont think there is any website for this repo


Snakemake profile parameter in API

Is your feature request related to a problem? Please describe.
Not sure if I miss something, but using the snakemake API does not allow to pass a profile file path. I assumed that I could pass a profile just like a Snakefile or cores as arguments in command line, but also as parameters in a python call.
So,
snakemake --profile slurm

would work, but this won't:
import snakemake
snakemake.snakemake(profile = "slurm")

Is this intended?
Describe the solution you'd like
Ideally, the API allows profile as parameter.
Describe alternatives you've considered
Alternatively, a system call within python would do the job or setting the environment variable SNAKEMAKE_PROFILE.

Profiles are interpreted using the cli parser, the code for which is found in snakemake.main() (in snakemake/__init__.py. snakemake.snakemake() doesn't have a profile parameter because the profile should already be parsed by the time it's called. I doubt including profile as a parameter would ever be supported. If anything, the parser could be isolated as a separate callable returning some class (e.g. SnakemakeArgs) that could then be passed into snakemake.snakemake. But this would involve a fair amount of refactoring.
The best workaround currently is to call snakemake.main(["arg1", "arg2", etc...]), passing all your options as CLI strings. It's not so clean from an API perspective, but it's better than a subprocess call.

Hi @pvandyken, thank you for the response!
Totally agree and thanks for the snakemake.main() pointer, I was not aware of this.


Filter Conventions

Striped the "Named" part of the covnention and currently work on the filter visitor convention

@michaelstaib  build is boken


Not working with images requiring headers

Hi,
imagine you have an image which needs auth headers to be downloaded.
Because you are trying to get the image size from the url with Image.getSize, this fails and the image is not showed.
You can have a look to Image.getSizeWithHeaders to allow fetching the sizes in this common use case.
Same can be said for Image.prefetch, but here it seems that RN does not yet support something like Image.prefetchWithHeaders.
Currently the only workaround I've found is to disable preload and provide width and height ahead of time.

Does this help?
https://github.com/ascoders/react-native-image-viewer/issues/169

Nope. As you have written there, Image.getSizeWithHeaders should be used and to support also preload a similar prefetch method should be used (and maybe created too)


MDCard border_radius property not working

I tried to give border_ radius property to my MDCard but it is not working so I ended up using RoundedRectangle to achieve that (it will be very nice if you guys fix it)

People advise to use canvas its OK, but it increase your coding and make it very complex. Just go to the Kivymd>uix>card.py line 631 change the default from 3dp to for example 20dp or whatever you want. then go back to your code and type radius: [] and insert your desire number from 20 to 0. Done!!!

People advise to use canvas its OK, but it increase your coding and make it very complex. Just go to the Kivymd>uix>card.py line 631 change the default from 3dp to for example 20dp or whatever you want. then go back to your code and type radius: [] and insert your desire number from 20 to 0. Done!!!

Thanks man

@kengoon Do not close questions marked "type improvement." This shortcut is intended for developers so that they can make improvements related to this issue.

Ok... Never saw that

@kengoon
MDCard:
    radius: [15,]


Unable to start service matrix-coturn.service

Error

Hello! I'm having trouble running the command ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start in my code, and I get this error.

Did you try seeing what went wrong? It states clearly to see more information to use the command 'journalctl -xe' for more info.

journalctl -fu matrix-coturn.service

also, close this and continue in #4


p-autocomplete with dropdown true

Hi,
Today I'm testing the p-autocomplete with dropdown and I can't show the items when you click in the button.  I detected that open and close the overlay at the same time and disnt't appear any error message.
I tried to remove the shadowDom and works fine. I'm not sure what it's happened and why the overlay open and close at the same time with shadowDom activated.
Is possible to add a fix for use the p-autocomplete with priming-shadowdom-directives?
Thank a lot!

Hi,
Finally i fixed it. My code:
  hostEl.bindDocumentClickListener = () => {     if (!hostEl.documentClickListener) {         const documentTarget: any = hostEl.el ?          hostEl.el.nativeElement.ownerDocument.activeElement.shadowRoot         ?hostEl.el.nativeElement.ownerDocument.activeElement.shadowRoot:         hostEl.el.nativeElement.ownerDocument         : 'document';         hostEl.documentClickListener = hostEl.renderer.listen(documentTarget, 'click', (event) => {             if (event.which === 3) {                 return;             }             if (!hostEl.inputClick && !hostEl.isDropdownClick(event)) {               hostEl.hide();             }             hostEl.inputClick = false;             hostEl.cd.markForCheck();         });       }     }   } }
If you want to add to autocomplete.ts, could fix the dropdown overlay in p-autocomplete.
You can close this issue.
Regards

Hi, please upgrade to v0.2.1 I fixed the issue. Commit
The reason for this is: in the case we render autocomplete in multiple nested shadow Root, it always find the very top level shadow root, but instead it should find in its current shadow root only


openjfx15: fix build by pulling required gtk2 depend

Without the change build fails as:
> Configure project :
Package gtk+-2.0 was not found in the pkg-config search path.

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 287444 run on x86_64-linux 1

1 package built:

openjfx15 (javaPackages.openjfx15)


Handle quality from Next

At the moment it appears the only values passed on to a custom imageBuilder is width and originalImageDimensions, but Next/Image allows for setting quality as well in a loader.
I know I'd find this valuable

Hi RyKilleen, thanks for sharing the proposal. I noticed that this was an oversight from my side. Adding the quality by default would however potentially cause a breaking change in existing usages.
I will add the functionality somewhere next week and release a 2.0 version of the library. If you want, you can also send in a PR so we can get this integrated

Sorry for the delay in the new release, this functionality is now available in the 2.0.0 version (which has just been released on npm). The documentation has been updated as well, i would be glad to hear if this solves your use case!

Awesome, thank you for the update! Excited to check it out


refactor(link): refactor link props

Based on our team's decision, we no longer require approval of the refactoring pull request. Instead, we will review and approve the refactoring once all changes related to a specific component have been completed.
I have standardized the rendering of links in the footer to match the style used in the header.
Furthermore, I've implemented a new component called Link that replaces the previous Link component and the getLinkAttributes function. This new component allows for the merging of either a Material-UI (MUI) component / a custom component with a Material-UI Link / a Gatsby Link. The purpose is to eliminate duplicated code and improve code organization.