SqlFuzzer issues

Hi,
I wanted to use your solution in a project I am working on and I noticed that the sqlfuzzer sometimes doesn't produce the valid SQL so I wanted to double check if someone else had the same issues and if my assumptions are correct

In the comment_rewriting method, when it is rewriting multiline comments in this payload
select */**/ from mytable        (select * command with added comments)
the method identifies the first occurrence of */ as end of the multiline comment and generates invalid SQL
select blah*/**/ from mytable

Method swap_keywords, when selecting mapping "OR" => [" OR ", "||"] in payload with WAITFOR sql command in it will transform it to WAITF OR.
(Of course that is not an issue if we don't use WAITFOR in the payload or if the used sql dialect is not supporting it)

#9 fixed the problems reported in this issue.
Anyway, I would wait for the merging of #12 that fixes some issue introduces in the changes of #9.

Closing since #12 was merged :pray:


[EPIC] OAuth Provider & Login

What should be done
The "hard" part of this work is described here :
https://rattle-llama-7da.notion.site/OAuth-Provider-c43ec6d6f23e47c6939166c3d594d698

[ ] lenra-io/kubernetes#91
[ ] lenra-io/server#369
[ ] lenra-io/server#370
[ ] lenra-io/server#372
[ ] lenra-io/server#373
[ ] lenra-io/server#374
[ ] lenra-io/server#375
[ ] lenra-io/client-common#82
[ ] lenra-io/client#67
[ ] lenra-io/backoffice#91
[ ] lenra-io/server#376
[ ] lenra-io/server#377
[ ] lenra-io/server#378
[ ] lenra-io/docs#98

What can be done additionally

[ ] [Server/Client] Add the 2FA Authentication using One-Time Passcode ? (OTP)
[ ] Add the Webauthn protocol

Technical recommandation
Most of the complexity is handled by Ory Hydra. We will add some applications and library once to simplify the system overhaul.
Most of the security concerns are handled by Ory Hydra. Be careful with the Ory Hydra configuration to only expose specific port(s).

@taorepoara i've created the subtask for this Epic with some description of the work that must be done.
Some of the task need some discussions and decisions about the design and/or features.
Depending of the decisions made, some other task will be created.

This epic can be closed. The remaining tasks will be managed later


Absorption probabilities slowdown

The time it took to compute absorption probabilities on the lung used to be about 1.5 min in rc0. In rc4, it suddenly increased to 3.5 min. Any ideas what's going on?

It may be related to the fact that I'm solving a different problem in rc4 becasue the transition matrix is different. We really need to figure out why we deviate from the old transition matrix, even when using the deterministic mode!

Did you change anything else in the code that could have caused this slowdown? When I call the function without any arguments, it takes 3.5 min to run. If I set use_petsc=True and solver="gmres", then it does not even finish in 10min. This is a bit upsetting, as this was really a solved problem!

By default, you compute also the mean time until absorption, which solves 1 more linear system. Could you try running it as (..., absorption_time_moments=None)? It should be back to speed.
If that's the case, I will set the default to None.

P.S. Since I haven't tested the speed on the Lung (crashed on my PC still and I needed a break from servers), could you please test absorption_time_moment="second"?

@Marius1311
By default, you compute also the mean time until absorption, which solves 1 more linear system. Could you try running it as (..., absorption_time_moments=None)? It should be back to speed.
If that's the case, I will set the default to None.

Setting absorption time moments to None in face reduces the computations time to 1min 55sec. It was at 1min 44 sec before, but this does not really matter and could be random chance. So this is fixed and I would indeed use None as the default value here.

P.S. Since I haven't tested the speed on the Lung (crashed on my PC still and I needed a break from servers), could you please test absorption_time_moment="second"?

Hi Mike, I'm just running the second order computation on my mac and it's been running for over 20min already. I looked into the code and saw that you're doing an explicit matrix inversion. I remember we talked about this - please try to re-formulate this as a linear solve, I'm fairly sure this is possible. This can be a nice little maths exercise for you. We can talk about it tomorrow in case you get stuck.

Ok, will look into it.


Ability to set sourceAddressPrefix and sourcePortRange for incoming SSH and TLS connections

I have a use case to limit the sourceAddressPrefix and sourcePortRange for incoming connections to the created NSG. For this case, I would like to be able to define this in the cluster configuration file to parameterize these changes.
@bearrito

Our need for this is driven by NETSEC requirements.
We would like to limit 22 access to our bastion box and/or limit 443 access to our set of static corporate ips

I'm guessing this isn't high on the ACS team radar today. So if you want the feature we would need to have a design discussion here and if we can agree then you or someone else in the community could pick up the work to push this into ACS Engine

That works out for me. The initial design I propose would be adding additional properties to the cluster definitions for configuring  sourceAddressPrefix and sourcePortRange in the masterProfile for the available protocols in DC/OS and Kubernetes. Where sourceAddressPrefix and sourcePortRange would be valid values per the constraints set for these in NSGs.
{
    "masterProfile": {
      "count": 1,
      "dnsPrefix": "",
      "vmSize": "Standard_D2_v2",
      "securityRules": {
          "ssh": {
               "sourceAddressPrefix": "",
               "sourcePortRange": ""
          },
          "tls": {
               "sourceAddressPrefix": "",
               "sourcePortRange": ""
          },
          "rdp": {
               "sourceAddressPrefix": "",
               "sourcePortRange": ""
          }
      }
    }
}

For where we are today this feels to niche to make it into our API model. So we won't be taking this change at this time. The way I would do this would be to add the rules myself after deployment. then to remove the NSG from the template anytime I was updating the cluster.

That is the approach we took.  It's unfortunate because it adds to operator overhead.
I'm quite sure others work in audited environments were exposing important parts of the management api to the Internet isn't allowed and so everyone will have to replicate the above steps.


Webapp work on top of IPFS api directly

Offline: You can also run the application locally by cloning the project and start webserver of choice, serving the root folder. python -m SimpleHTTPServer is a handy command for serving from current folder.

Why need server? why not just access it on the IPFS daemon's api directly? (with proper CORS setup)
(once https://github.com/ipfs/go-ipfs/pull/1886 is merged, we wont even need that)

Good question! Looked into why and this is why.
Some API methods in js-ipfs-api gets different responses depending on where they run, ipfs.add seems to be one of them. When running via my local gateway, http://localhost:5001/ipfs/QmURTVk4xWXXNHE5xBTDojSmLJr9BvJXeHqVNr63XJ2fzC, it returns a array of objects that has the hash. But, when running from ipfsbin.xyz, it instead returns an object directly. Probably/Maybe has to do with https://github.com/ipfs/js-ipfs-api/issues/79 or https://github.com/ipfs/js-ipfs-api/issues/76

https://github.com/ipfs/go-ipfs/pull/1886 is merged as part of 0.3.9 release.

Now just waiting for https://github.com/ipfs/infrastructure/issues/105 then I'll enable writing to the public gateway by default, falling back to ipfsbin.xyz if not working.

Sounds good. Though 0.3.9 means you no longer need the private API, can do everything through the public Gateway/API now.


docker.cmd.test assumes an image name

The docker.cmd.test label requires you to pass an absolute image name. The image being tested might be under a different name or tag.
A much more useful label for me would be a path to an executable inside the container to run. This would be portable across runtimes, and allow the consumer of the label to easily pass their own options, etc.

I like the idea of being able to specify these cmd.* labels in a runtime-portable way. Would it work to have cmd, cmd.test, cmd.help etc that just have the path to the executable (and no options)? If you need to pass in particular options you'd need to specify docker.cmd., but if no options are required (or the label consumer knows what they are somehow) you could just use a vanilla cmd.. Wdyt?

That sounds like it'd work!


Render to html string

How do you render a node to raw html? I would want to h1("hello world") parsed to
<h1>Hello World </h1>

and bound to a variable of my choosing

Well this will be tricky. Patchwork nodes represent the DOM which are in many ways different from the HTML markup, there is no way to convert to HTML without losing at least some information.

Hi shashi,
This looks like a cool package and I had the same question as stanonyime.
I'm not an HTML expert, but I've played around quite a bit with d3 for manipulating the DOM and I don't understand your response. I would think that you should be able to start with a DOM representation and generate an HTML document that would render that DOM. What am I missing? If there is information in Patchwork that would be lost in constructing an HTML document, what kind of info would that be and is that info necessary for rendering a page or would it be more about interactivity, signals, etc.?
If I understand, your build.js is based on node.js, but I am interested in using Patchwork directly with a Julia server and I thought writing a Patchwork DOM to HTML might be a good way to go.
Any thoughts? Thanks :)

I would think that you should be able to start with a DOM representation and generate an HTML document that would render that DOM.

That is not true because you can only write "attributes" in HTML but not DOM properties http://stackoverflow.com/questions/258469/what-is-the-difference-between-attribute-and-property
For your purpose you should consider using Hiccup and Mux

Hi shashi,
Thanks for the quick reply and for correcting me on the HTML (I said I wasn't an expert :)).
Not giving up, to set properties when writing an HTML document from Patchwork, in principle, could you generate embedded d3 (or jQuery) scripts to set those properties?
Thanks also for the reference to Hiccup and Mux. I am familiar with Mux, but decided to work directly with HttpServer.jl, but not familiar with Hiccup so will check it out :+1:


Brazilia Portuguese should ignore special characters

Since when programming we don't use special characters like "ç" and accents even when coding in portuguese the spell checking should ignore these characters when correcting a word, or add a feature like programming mode so we can turn off special character checking

this isssue is solved here
https://github.com/streetsidesoftware/vscode-cspell-dict-extensions/issues/12


Release 0.15.1 checklist

Before final release

[x] Backport any bugs
[x] Update release date in changelog
[x] Bump version to X.Y.Z in:

README.md
__init__.py
Sphinx conf.py

[x] Check that docs badges and URLs point to appropriate tag (replace vX.Yb1 by vX.Y.Z)
[x] Commit
[ ] Generate sdist and bdist_wheel
[ ] twine upload dist/* --repository-url https://test.pypi.org/legacy/
[ ] Tag

Final release

[ ] Push tag to GitHub
[ ] Upload sdist and bdist_wheel to PyPI - this step cannot be undone if the release is removed! twine upload dist/* --repository-url https://upload.pypi.org/legacy/
[ ] Check Read the Docs
[ ] Create GitHub release
[ ] Add Zenodo badge to GitHub release
[ ] Send announcement email with subject "ANN: poliastro X.Y.Z released 🚀"
[ ] Cherry pick release date to master
[ ] Close milestone

This ended up being 0.15.2 because I messed up the PyPI upload. Will send an announcement later on this week. Closing!


Remove runtime dependency on Build controller

With this change, TaskRuns are translated to Builds in the TaskRun controller (as today), then translated from Builds to Pods using the same vendored code from the knative/build repo that the Build controller uses.
The TaskRun controller then watches Pods for updates, instead of Builds, and when it sees a Pod update, it translates that PodStatus to a BuildStatus (as the Build controller does today), then translates the BuildStatus to a TaskRunStatus (as the Pod controller does today).
As a result, there is no runtime dependency on the Build controller, and no Build CRD resources are created at any point.
This is Phase 1 below:

As a next step, we can remove the code dependency on the Build type, and the duplicate type translation, by simply translating TaskRuns directly to Pods, and PodStatus directly to TaskRunStatus.

/test pull-knative-build-pipeline-go-coverage

Great PR, this will be a huge step for moving the pipeline crd project forward 👍🚀
/lgtm


DeviceIdentifier r1.1 (v0.1.0-alpha.1) release review

Release PR or issue to review

https://github.com/camaraproject/DeviceIdentifier/pull/85
Review actions
Assign this issue to yourself and follow the below list.
For any review action, review the file(s) in the issue/PR listed above.
Put comments in the above issue or PR if they concern non-changed files/text.
Put a short summary of the main review result here into the review issue.

[ ] API definition files (YAML) (check version in info & servers objects)
[ ] test file(s) availability
[ ] changelog updated
[ ] readme updated (enforce correct release number / API version naming)
[ ] API readiness checklist(s)

Release actions
Assign this issue to yourself or another RM team member and follow the below list.
When done, tick the box in this issue.

[ ] API release tracker available on wiki
[ ] Review comments addressed (by Sub Project)
[ ] Release PR approved (on behalf of Release Management)
[ ] PR merged (by Sub Project codeowner)
[ ] Release created within GitHub (by Sub Project codeowner)
[ ] Release Tracker updated (with creation date of the release and the release tag link)

Additional comments

Proposed API version is 0.2.0-alpha.1. Device Identifier already has a 0.1.0 initial release.

Updated the release tracker, issue can be closed.
cc: @eric-murray @tanjadegroot


Polyfill request: integrate web-animations-js

Since there is no MY_POLYFILLS array i opened an issue about this.
https://www.npmjs.com/package/web-animations-js should be added because the animations api is not cross browser compatible

Hmm, not sure if I should add this as many apps might not use the animations api. I mean there are about 3 options for it right now, you could:

Use CDN: https://github.com/qdouble/angular-webpack2-starter/tree/master/src
Install and put in COPY_FOLDER array: https://github.com/qdouble/angular-webpack2-starter/blob/master/constants.js#L53
Install and put in the polyfill files like this one: https://github.com/qdouble/angular-webpack2-starter/blob/master/src/polyfills.browser.ts

Alright, i went with the 3rd option.
I also add here? https://github.com/qdouble/angular-webpack2-starter/blob/master/webpack.config.ts#L236

@tsm91 yeah, I'll probably add a constant for that though

@tsm91 added a constant for it in this commit: https://github.com/qdouble/angular-webpack2-starter/commit/e5bb2b2c8932e7207bfc98c493e990933bec6312


Unable to implement custom provider

Is your feature request related to a problem? Please describe.
Mostly as an exercise to understand Riverpod internals better but also to reduce boilerplate, I have tried to create my own type of provider.  I may well be taking the wrong approach; however, at the moment I feel that I am blocked by Riverpod not exporting the abstract ProviderStateBase class.
I have a number of providers for accessing API service classes that all need to be passed in an HTTP client object.  The type of the HTTP object isn't important, just that they all need it.  All of the API service classes extend a common base API class.
final httpProvider = Provider<CustomHttpClient>(
  (ref) => CustomHttpClient(...),
);

final userApiProvider = Provider<UserApi>((ref) {
  final http = ref.watch(httpProvider);
  return UserApi(http);
});

final searchApiProvider = Provider<SearchApi>((ref) {
  final http = ref.watch(httpProvider);
  return SearchApi(http);
});

// And so on for each of the dozen or so API classes...

Describe the solution you'd like
I'd like to implement my own ApiProvider that reduces the boilerplate so that I can instead use the following syntax:
final httpProvider = Provider<CustomHttpClient>(
  (ref) => CustomHttpClient(...),
);

final userApiProvider = ApiProvider((ref, http) => UserApi(http));

final searchApiProvider = ApiProvider((ref, http) => SearchApi(http));

To do this, I tried to model ApiProvider on Provider, ignoring the autoDispose and family capabilities.
typedef CreateApi<API extends MyApi> = API Function(ProviderReference ref, CustomHttpClient http);

@sealed
class ApiProvider<API extends MyApi> extends AlwaysAliveProviderBase<API, API> {
  ApiProvider(CreateApi createApi) : super(_create(createApi), null);

  // Returns a provider-compatible [Create] function that internally watches the HTTP
  // client and then calls the passed-in function to create the API service object.
  static Create _create(CreateApi create) {
    return (ref) {
      final http = ref.watch(httpProvider).state;
      return create(ref, http);
    };
  }

  @override
  _ApiProviderState<API> createState() => _ApiProviderState();
}

@sealed
class _ApiProviderState<API> = ProviderStateBase<API, API> with _ApiProviderStateMixin<API>;

mixin _ApiProviderStateMixin<API> on ProviderStateBase<API, API> {
  @override
  void valueChanged({API previous}) {
    if (createdValue != exposedValue) {
      exposedValue = createdValue;
    }
  }
}

This approach doesn't seem to be possible as the createState method must return a ProviderStateBase but that class is not exported by Riverpod.
Is there any documentation for how to implement a custom provider type?  Apologies if I have missed this.

Maybe you looking for that? own StateNotifier

Thanks @iamarnas.  I don't think so – these classes don't encapsulate any state and so making them StateNotifier's feels, to me, to be the wrong approach.
I also don't see how that would let me avoid duplication of passing through the HTTP dependency unless the StateNotifier subclass were to pass the ProviderReference to the API superclass.

Whilst I'm still curious about implementing a custom provider type, for this specific example, I've decided it's easier just to use a function as a pseudo-provider class.
Provider<API> ApiProvider<API extends MyApi>(API Function (CustomHttpClient http) create) {
  return Provider<API>((ref) {
    final http = ref.watch(httpProvider);
    return create(http);
  });
}

As said on Discord, there is no official way to make custom providers at the moment.
Mainly because I don't understand the problem yet. So I do not want to expose a half baked API, as changing it in the future is difficult
As you found yourself, in general, my recommendation would be to instead compose providers, using functions
If you want to implement the entire spectrum of features (family/autoDispose), there's a bit more work. But you can do that using extension methods


Not able to create containers with volumes in rancher-nfs without having to set nfs version.

Rancher sever version - v1.2.2-rc2
Setup has Ubuntu 16.04.1 LTS (4.4.0) with docker 1.12.5
On cattle environment , deploy rancher-nfs (rancher/storage-nfs:v0.6.0)
Create a service volume in  rancher-nfs.
Container fails to start with the following exception:
 Activating (Expected state running but got error: Error response from daemon: VolumeDriver.Mount: Failed mount <IP_ADDRESS>:/var/nfs1/hello1 /var/lib/rancher/volumes/rancher-nfs/hello1: Running in chroot, ignoring request. mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: mounting <IP_ADDRESS>:/var/nfs1/hello1 failed, reason given by server: No such file or directory)
Seems like we defaulted to nfsv3 client.
To workaroud the issue , I had to manually set MOUNT_OPTS: nfsvers=4 when deploying rancher-nfs.

Since our containerized nfsv3 client didn't work, we dropped support for it. Since that is the case, we need to hard-code the nfsvers=4 parameter to ensure we never attempt an nfsv3 mount.

Fix in v1.3.0-rc3 branch of rancher-catalog
Please also test setting nfsvers=3 in mount options, and observe that the value is ignored.

Tested with v1.3.0-rc3 branch of rancher-catalog using rancher-server - v1.3.0-rc2.
nfsversion needs to be explicitly set now (can only be set to 4 now) and is a required parameter.

Has anyone seen this post 1.3 ? I'm seeing this exact behavior in 1.3.2 using rancher-nfs. Just curious if there was a possible regression.

disregard, I figured out what needs to be done.


Trace helper modification

Trace helper was pulling in rtos bits which we may hamper
if we were to drop rtos for memory constrained platforms.

@hasnainvirk Does this mean tracing is disabled on non-RTOS platforms now?

@janjongboom Hmmm, the mutex should actually be PlatformMutex so that we don't worry about RTOS/Non-RTOS. I will send a patch.


#216  Stats page for community/protocol

Description of the change
Hi. This is the PR for issue #216. I finally complete adding all charts. Please review and merge my PR!
The charts may be a little difficult to read, but I think the design should be improved in the future.

Screenshots

Checklist
I agree to the following :-

[x] Added description of the change
[x] I've read the contributing guidelines
[x] Search previous suggestions before making a new PR, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Notes (optional):

Hi @osaguild, thanks for your contributions. Please submit your work here to count your contributions: https://app.dework.xyz/devprotocol/community-builders-1?taskId=6dd1ffe4-b7b6-4ae8-b355-adedb6f0c9a3

See this @aggre

Super! Of course LGTM!

@osaguild The mainnet chart looks like a cliff, but that is due to bulk migration of MVP users. So, it would make more sense to make the starting point the value of this edge. What do you think?

@osaguild The mainnet chart looks like a cliff, but that is due to bulk migration of MVP users. So, it would make more sense to make the starting point the value of this edge. What do you think?

I agree, I fix it.

Hi @aggre,  I fixed.

@aggre How about PR? let me know if you have any requests. I think the content is out of date and may need to be updated.

@aggre How about PR? let me know if you have any requests. I think the content is out of date and may need to be updated.

Awwwww sorry I didn't notice it, and this PR is great!

@aggre How about PR? let me know if you have any requests. I think the content is out of date and may need to be updated.

Awwwww sorry I didn't notice it, and this PR is great!

Should I merge this now?

Yeah its great 👍


Sample JSON is incorrect as SMS payload is an array. Updated JSON inside.

SMSReceivened event payload is an array format. The sample JSON given is incorrect and returns this error, at least in power platform:
[
  {
    "message": "Invalid type. Expected Object but got Array.",
    "lineNumber": 0,
    "linePosition": 0,
    "path": "",
    "schemaId": "#",
    "errorType": "type",
    "childErrors": []
  }
]

I created a new valid JSON to handle the array that works in either format:
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "id": {
        "type": "string"
      },
      "topic": {
        "type": "string"
      },
      "subject": {
        "type": "string"
      },
      "data": {
        "type": "object",
        "properties": {
          "messageId": {
            "type": "string"
          },
          "from": {
            "type": "string"
          },
          "to": {
            "type": "string"
          },
          "message": {
            "type": "string"
          },
          "receivedTimestamp": {
            "type": "string",
            "format": "date-time"
          }
        },
        "required": [
          "messageId",
          "from",
          "to",
          "message",
          "receivedTimestamp"
        ]
      },
      "eventType": {
        "type": "string"
      },
      "dataVersion": {
        "type": "string"
      },
      "metadataVersion": {
        "type": "string"
      },
      "eventTime": {
        "type": "string",
        "format": "date-time"
      }
    },
    "required": [
      "id",
      "topic",
      "subject",
      "data",
      "eventType",
      "dataVersion",
      "metadataVersion",
      "eventTime"
    ]
  }
}

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

ID: 52b04127-06f9-0dea-d179-15b3adbdcc05
Version Independent ID: 9f9843d9-a9ea-bf52-363c-ac96a578aa62
Content: Quickstart - Receive and Reply to SMS - Azure Communication Services
Content Source: articles/communication-services/quickstarts/sms/receive-sms.md
Service: azure-communication-services
Sub-service: sms
GitHub Login: @tophpalmer
Microsoft Alias: chpalm

@mk11232
Thanks for your feedback! We will investigate and update as appropriate.

@mk11232 Thanks for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate.


JuiceShop docker container crashes when scanning[🐛]

Using JS 13.1 and 13.2, the docker container crashes when scanning with an automated DAST scanner.  Unfortunaley I dont know which requests are causing the issue.   Here is the log output just before it crashes:
info: Solved 6-star continueCodeChallenge (Imaginary Challenge)
info: Cheat score for continueCodeChallenge solved in 0min (expected ~12min) with hints allowed: 0.9923152777777777

/juice-shop/build/routes/updateProductReviews.js:20

            utils.solveIf(challenges.forgedReviewChallenge, () => { return (user === null || user === void 0 ? void 0 : user.data) && result.original[0].author !== user.data.email && result.modified === 1; }); // vuln-code-snippet hide-line                                                                                ^
TypeError: Cannot read properties of undefined (reading 'author')
    at /juice-shop/build/routes/updateProductReviews.js:20:154
    at Object.exports.solveIf (/juice-shop/build/lib/utils.js:107:38)
    at /juice-shop/build/routes/updateProductReviews.js:20:19
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm notice
npm notice New minor version of npm available! 8.1.2 -> 8.4.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.4.0>
npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
npm notice

It seems to be this request that causes JS to crash.
PUT http://localhost:3000/rest/products/1/reviews HTTP/1.1
Host: localhost:3000
User-Agent: frisby/2.1.3 (+https://github.com/vlucas/frisby)
Content-Length: 44
Accept: */*
Cache-Control: no-cache
Connection: close
Content-Type: application/json
Cookie: token=eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJzdGF0dXMiOiJzdWNjZXNzIiwiZGF0YSI6eyJpZCI6MjEsInVzZXJuYW1lIjoiIiwiZW1haWwiOiJmb29vb28xQGJhci5jb20iLCJwYXNzd29yZCI6ImUxMGFkYzM5NDliYTU5YWJiZTU2ZTA1N2YyMGY4ODNlIiwicm9sZSI6ImN1c3RvbWVyIiwiZGVsdXhlVG9rZW4iOiIiLCJsYXN0TG9naW5JcCI6IjAuMC4wLjAiLCJwcm9maWxlSW1hZ2UiOiIvYXNzZXRzL3B1YmxpYy9pbWFnZXMvdXBsb2Fkcy9kZWZhdWx0LnN2ZyIsInRvdHBTZWNyZXQiOiIiLCJpc0FjdGl2ZSI6dHJ1ZSwiY3JlYXRlZEF0IjoiMjAyMi0wMS0yOCAxNjoxODoxNi4xNDAgKzAwOjAwIiwidXBkYXRlZEF0IjoiMjAyMi0wMS0yOCAxNjoxODoxNi4xNDAgKzAwOjAwIiwiZGVsZXRlZEF0IjpudWxsfSwiaWF0IjoxNjQzMzg2NzIzLCJleHAiOjE2NDM0MDQ3MjN9.PQIswXcOQ3aXcQfspiSPyR_XlsAThuQt5AscsWLmTQSiPXbBlFgaeACryy2YzX6WDx8_lsm244sF0i03PiVDog6dJTeF4L2Iz0KcXpSLLZYrld9XiRXE7vAMa33XlUMYptnOknoHGwSx4cNGhAugTNekbfrqPzixoyFMYJGCI0c; continueCode=e1ZwBLrKqWXamDEzyO9RgGmMT6CrfyUMHpWc44Go2M36xjVQbJvklN87pPY4
Accept-Encoding: gzip

{"message":"798482723","author":"Anonymous"}

Seems that the access to result.original[0].author failed because result.original[0] was undefined. I will add a safety check there so it at least doesn't crash.

When https://github.com/juice-shop/juice-shop/actions/runs/1768786692 is finished feel free to test if the problem is gone with the snapshot Docker image containing Juice Shop v13.3.0-SNAPSHOT or later.


try installing ncdf4 from CRAN?

Most debian binaries haven't been rebuilt yet for R 3.5.0.  Better to install from CRAN?
Let's see what travis thinks...

I was about to type: "Oh, I didn't know you could do that on Linux w/o extra work" and then the build failed due to not having the right deps.

😛   yeah, I saw libnetcdf-dev in there and figured "oh good, the libs are already there', but of course ncdf4 is one of those weird packages that doesn't just bind the existing libs. let's try with the ncdf binaries as well....

Looks like things settle down when I moved ncdf4 and other non-required packages to Suggests and turn off R CMD CHECK's _R_CHECK_FORCE_SUGGESTS which is a super weird default

ncdf4 appears to be installing on my second attempt wtih netcdf-bin included; if you want to keep the suggests.
I think  _R_CHECK_FORCE_SUGGESTS default makes sense because suggests are often used precisely for things that are needed for check (i.e. testthat, covr) but are not needed by the end user.  I rarely list something in SUGGESTS unless it is needed by a vignette or a test.

Ah, that actually makes a ton of sense.
I incorporated your changes with my changes that reduce the number of Depends
https://travis-ci.org/NCEAS/arcticdatautils/builds/377504630
let's see how this goes! Thanks


make ReviewLog objects JSON-serializable

I made ReviewLog objects JSON-serializable so that these logs can be easily stored in databases. The changes are very similar to the changes made in #33 for Card objects.
Changes:

Added .to_dict() method to ReviewLog for serialization
Added static .from_dict() method for deserialization
Added a new test: test_ReviewLog_serialize to test the serialization
Bumped from version 2.2.1 -> 2.3.0

Thanks for your contributions! I want to invite you join our organization and assign the maintainer role to you.

Sure! Sounds good to me


Add API for checking credential status.

Needs test with simple mocked status check.

Rebase on master.  (will pull in linting action, etc)

Rebased on master.


Add usage with hooks to documentation

Pull Request Test Coverage Report for Build 19

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 16:
0.0%

Covered Lines:
1

Relevant Lines:
1

💛  - Coveralls


[move-prover] Misc fixes.

This PR fixes a number of issues, most of them related to the problems Junkil found when specifiying libra account:

The reporting of aborts had regressed. Now boogie_wrapper again finds aborts agains and reports them in a more meaningful way. Closes #2979.
The boogie conditions for aborts has been split into parts such that we get a more precise error. The ensures (P1 || .. || Pn) <=> abort_flag doesn't work well as boogie only reports failures for the whole ensures, but not for individual parts. Now we generate ensures P1 ==> abort_flag; ...; ensures Pn ==> abort_flag which gives as a good error if the function should fail but doesn't; as well as ensures abort_flag ==> (P1 || .. || Pn) which covers the case where the function aborts but has no aborts_if.
A bug was fixed in module invariants which weren't correctly assumed in all cases when a module is called from the outside. This lead to failures in libra_account calling libra with David's new global specs. Also the schemas there now use invariant module instead of invariant.
Type assumptions for vectors are strengthened. If we know the element type of a vector, it will be assumed for all elements. This wasn't an issue in this case but resulted as a side-effect from debugging.

Moreover, the prover now detects deps which are not introduced by a use in Move but use absolute references in code. This previously lead to a failure with missing Testnet declaration in one of the stdlib sources.
Libra account still has a bug around create_account and save_account. Instead of holding this PR up on this one, I decided to move forward with this and submit, and fixing this in a followup.
Motivation
Fixing bugs.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Updated baselines.
Related PRs
NA

@bors-libra r=junkil-park

:pushpin: Commit 2a0cc6b has been approved by junkil-park

:hourglass: Testing commit 2a0cc6be31cc2fb69bf302c517bcfce27671fd0b with merge 798ca841330a833d3950af7578684cd1ab35489d...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: junkil-park
Pushing 798ca841330a833d3950af7578684cd1ab35489d to master...


Enable SLF001 for src

Fixes #154

Enable SLF001, forbidding private member access in src directory.
Per discussion in #154, ignore private member access violations in tests directory
Add test proving that ruff flags the violations

This looks fine, but I will reserved judgement until @evalott100 has applied it to ophyd-async (which should be soon)


DeviceLab mac 31 & mac 33 are causing test flakes

Manually quarantined the bot: https://chromium-swarm.appspot.com/bot?id=flutter-devicelab-mac-31
Mac31 failed builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android hybrid_android_views_integration_test/3315/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android hybrid_android_views_integration_test/3313/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android hybrid_android_views_integration_test/3307/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android embedded_android_views_integration_test/3306/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android embedded_android_views_integration_test/3297/overview
Mac33 failed build:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android complex_layout_scroll_perf__memory/3267/overview
[embedded_android_views_integration_test] [STDOUT] stderr: [        ] VMServiceFlutterDriver: Attempting to resume isolate
[embedded_android_views_integration_test] [STDOUT] stderr: [+3923 ms] VMServiceFlutterDriver: Connected to Flutter application.
[embedded_android_views_integration_test] [STDOUT] stdout: [   +4 ms] 00:04 +0: MotionEvent recomposition
[embedded_android_views_integration_test] [STDOUT] stdout: [+1424 ms] I/flutter (31173): replaying 67 motion events
[embedded_android_views_integration_test] [STDOUT] stdout: [+2754 ms] 00:08 +1: WindowManager (setUpAll)
[embedded_android_views_integration_test] [STDOUT] stdout: [ +567 ms] 00:09 +1: WindowManager AlertDialog from platform view context
[embedded_android_views_integration_test] [STDOUT] stderr: [+5834 ms] VMServiceFlutterDriver: tap message is taking a long time to complete...

These two bots have been moved to staging.


CardModule' does not appear to be an NgModule class

Hello,
I am getting the following error on importing the CardModule in imports in one of my modules:
CardModule' does not appear to be an NgModule class.(-996002)
module.d.ts(1, 22): This likely means that the library (ngx-card/ngx-card) which declares CardModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

Environment:
@angular-devkit/architect       0.1400.4
@angular-devkit/build-angular   14.0.4
@angular-devkit/core            14.0.4
@angular-devkit/schematics      13.3.6
@nguniversal/builders           14.0.2
@nguniversal/express-engine     14.0.2
@schematics/angular             14.0.4
rxjs                            7.5.5
typescript                      4.7.4
webpack                         5.73.0

Please advise

Any progress with this? I'm experiencing the same issue with a custom stencil library

I managed to get a bit further ahead by adding this to my Angular consumer project (my custom library remains unchanged)
Inside angular.json, locate buildOptimizer and set it to false, then below it add "aot": false,


az cli get log alerts - canadacentral

i am trying to get all log alerts from a resource group in canade central.
i have tried az monitor scheduled-query list -g {my rg} but this returns nothing []
i have tried az monitor scheduled-query show -g {my rg} -n {name} but i get this error:
NoRegisteredProviderFound - No registered resource provider found for location 'canadacentral' and API version '2020-05-01-preview' for type 'scheduledqueryrules'. The supported api-versions are '2020-05-01-preview, 2018-04-16, 2017-09-01-preview'. The supported locations are 'westcentralus, australiaeast, centralus, eastus, eastus2, francecentral, japaneast, northeurope, southafricanorth, southeastasia, uksouth, westeurope, westus2, centralindia, canadacentral, australiasoutheast, southcentralus, australiacentral, koreacentral, eastasia, westus, northcentralus, brazilsouth, ukwest, switzerlandnorth, switzerlandwest, uaecentral, germanywestcentral, australiacentral2, brazilsoutheast, norwayeast'.
is there a planned time this will be available for Canada Central and or Canada East?

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

ID: 445d2458-1e27-7cf4-8a04-95ec798ebdc1
Version Independent ID: 3f80ed4a-d3c4-d15c-3e5d-50a48e0eb72c
Content: az monitor scheduled-query
Content Source: latest/docs-ref-autogen/ext/scheduled-query/monitor/scheduled-query.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

monitor

Hi @Mexicoder, canadacentral is already supported. That issue means you didn't have that resource in your resource group. You should create one scheduled-query first.


Question: can generate outputs for all files on npm start only, and not every time a file is edited?

I have close to 50 blog posts in my Hylia site currently. When I write a new blog post, I first launch the development server with npm start, which takes some time to build the whole site... that is ok. However, it also builds the whole site whenever I edit the blog post, making the experience a bit slow.
I understand that different pages may be affected (such as if I add a new tag) and they need be rebuilt, but I really don't care about those other pages, only about the blog post being edited.
So, is it possible to tell Hylia to only regenerate the page that has changed? (Even if the state of the site will be inconsistent... I don't care about that, it's my local setup, and I can always run npm start again)
Thanks

I reckon you should look into the --incremental flag which only builds the file you edited (I think). Maybe update your serve task to: cross-env ELEVENTY_ENV=development npx eleventy --serve --incremental

Thanks Andy.
I did as you said, and it works but it doesn't: even though it didn't regenerate all the other pages, the time it takes to reload the browser was actually the same!
Check the log. With the normal behavior, it takes 8.44 seconds to do a change:
[3] Watching...
[3] [Browsersync] Access URLs:
[3]  ------------------------------------
[3]        Local: http://localhost:8080
[3]     External: http://<IP_ADDRESS>:8080
[3]  ------------------------------------
[3]           UI: http://localhost:3001
[3]  UI External: http://localhost:3001
[3]  ------------------------------------
[3] [Browsersync] Serving files from: dist
[3] File changed: src/posts/registering-gutenberg-block-for-cpt-only.md
[3] Writing dist/admin/index.html from ./src/admin.njk.
[3] Writing dist/feed.xml from ./src/feed.njk.
[3] Writing dist/service-worker.js from ./src/service-worker.njk.
[3] Writing dist/tags/pop/index.html from ./src/tags.njk.
[3] Writing dist/styleguide/index.html from ./src/styleguide.njk.
[3] Writing dist/tags/api/index.html from ./src/tags.njk.
[3] Writing dist/tags/graphql/index.html from ./src/tags.njk.
[3] Writing dist/tags/wordpress/index.html from ./src/tags.njk.
[3] Writing dist/tags/gutenberg/index.html from ./src/tags.njk.
[3] Writing dist/tags/cope/index.html from ./src/tags.njk.
[3] Writing dist/tags/smashing/index.html from ./src/tags.njk.
[3] Writing dist/tags/development/index.html from ./src/tags.njk.
[3] Writing dist/tags/directives/index.html from ./src/tags.njk.
[3] Writing dist/tags/composer/index.html from ./src/tags.njk.
[3] Writing dist/tags/wp-cli/index.html from ./src/tags.njk.
[3] Writing dist/tags/guide/index.html from ./src/tags.njk.
[3] Writing dist/tags/writing/index.html from ./src/tags.njk.
[3] Writing dist/tags/components/index.html from ./src/tags.njk.
[3] Writing dist/tags/back-end/index.html from ./src/tags.njk.
[3] Writing dist/tags/front-end/index.html from ./src/tags.njk.
[3] Writing dist/tags/full-stack/index.html from ./src/tags.njk.
[3] Writing dist/tags/php/index.html from ./src/tags.njk.
[3] Writing dist/tags/schema/index.html from ./src/tags.njk.
[3] Writing dist/tags/server/index.html from ./src/tags.njk.
[3] Writing dist/tags/conference/index.html from ./src/tags.njk.
[3] Writing dist/tags/proposal/index.html from ./src/tags.njk.
[3] Writing dist/tags/speaking/index.html from ./src/tags.njk.
[3] Writing dist/tags/laravel/index.html from ./src/tags.njk.
[3] Writing dist/tags/symfony/index.html from ./src/tags.njk.
[3] Writing dist/tags/cms/index.html from ./src/tags.njk.
[3] Writing dist/tags/concept/index.html from ./src/tags.njk.
[3] Writing dist/tags/design/index.html from ./src/tags.njk.
[3] Writing dist/tags/implementation/index.html from ./src/tags.njk.
[3] Writing dist/tags/github/index.html from ./src/tags.njk.
[3] Writing dist/tags/project/index.html from ./src/tags.njk.
[3] Writing dist/tags/mobile/index.html from ./src/tags.njk.
[3] Writing dist/tags/voyager/index.html from ./src/tags.njk.
[3] Writing dist/tags/query/index.html from ./src/tags.njk.
[3] Writing dist/tags/syntax/index.html from ./src/tags.njk.
[3] Writing dist/tags/hylia/index.html from ./src/tags.njk.
[3] Writing dist/tags/eleventy/index.html from ./src/tags.njk.
[3] Writing dist/tags/jamstack/index.html from ./src/tags.njk.
[3] Writing dist/tags/blog/index.html from ./src/tags.njk.
[3] Writing dist/tags/indieweb/index.html from ./src/tags.njk.
[3] Writing dist/tags/data/index.html from ./src/tags.njk.
[3] Writing dist/tags/lando/index.html from ./src/tags.njk.
[3] Writing dist/tags/vapor/index.html from ./src/tags.njk.
[3] Writing dist/tags/serverless/index.html from ./src/tags.njk.
[3] Writing dist/tags/plugin/index.html from ./src/tags.njk.
[3] Writing dist/tags/block/index.html from ./src/tags.njk.
[3] Writing dist/tags/content/index.html from ./src/tags.njk.
[3] Writing dist/tags/spec/index.html from ./src/tags.njk.
[3] Writing dist/tags/rest/index.html from ./src/tags.njk.
[3] Writing dist/tags/bootstrap/index.html from ./src/tags.njk.
[3] Writing dist/tags/wordcamp/index.html from ./src/tags.njk.
[3] Writing dist/tags/singapore/index.html from ./src/tags.njk.
[3] Writing dist/index.html from ./src/index.md.
[3] Writing dist/posts/index.html from ./src/posts.md.
[3] Writing dist/contact/index.html from ./src/contact.md.
[3] Writing dist/work/index.html from ./src/work.md.
[3] Writing dist/thank-you/index.html from ./src/thank-you.md.
[3] Writing dist/404.html from ./src/404.md.
[3] Writing dist/speaking/index.html from ./src/speaking.md.
[3] Writing dist/writing/index.html from ./src/writing.md.
[3] Writing dist/posts/added-namespaces-to-graphql-by-pop/index.html from ./src/posts/added-namespaces-to-graphql-by-pop.md.
[3] Writing dist/posts/backstage-to-cope-with-wp/index.html from ./src/posts/backstage-to-cope-with-wp.md.
[3] Writing dist/posts/cache-and-logtime-directives/index.html from ./src/posts/cache-and-logtime-directives.md.
[3] Writing dist/posts/bootstrapping-wordpress-projects-with-composer-and-wp-cli/index.html from ./src/posts/bootstrapping-wordpress-projects-with-composer-and-wp-cli.md.
[3] Writing dist/posts/appropriate-content/index.html from ./src/posts/appropriate-content.md.
[3] Writing dist/posts/components-on-the-backend/index.html from ./src/posts/components-on-the-backend.md.
[3] Writing dist/posts/bettering-graphql-through-components/index.html from ./src/posts/bettering-graphql-through-components.md.
[3] Writing dist/posts/code-first-vs-schema-first-development-graphql/index.html from ./src/posts/code-first-vs-schema-first-development-graphql.md.
[3] Writing dist/posts/confoo-9-proposals/index.html from ./src/posts/confoo-9-proposals.md.
[3] Writing dist/posts/decoupling-pop-from-wp/index.html from ./src/posts/decoupling-pop-from-wp.md.
[3] Writing dist/posts/demonstrating-pop-api-graphql-on-steroids/index.html from ./src/posts/demonstrating-pop-api-graphql-on-steroids.md.
[3] Writing dist/posts/designing-graphql-server-for-optimal-performance/index.html from ./src/posts/designing-graphql-server-for-optimal-performance.md.
[3] Writing dist/posts/documentation-site/index.html from ./src/posts/documentation-site.md.
[3] Writing dist/posts/doing-the-writing/index.html from ./src/posts/doing-the-writing.md.
[3] Writing dist/posts/env-constants-instead-of-config/index.html from ./src/posts/env-constants-instead-of-config.md.
[3] Writing dist/posts/export-directive/index.html from ./src/posts/export-directive.md.
[3] Writing dist/posts/exposing-gutenberg-metadata/index.html from ./src/posts/exposing-gutenberg-metadata.md.
[3] Writing dist/posts/field-directive-versioning/index.html from ./src/posts/field-directive-versioning.md.
[3] Writing dist/posts/graphql-api-for-wordpress-video-custom-endpoints/index.html from ./src/posts/graphql-api-for-wordpress-video-custom-endpoints.md.
[3] Writing dist/posts/graphql-api-for-wordpress-video-persisted-queries/index.html from ./src/posts/graphql-api-for-wordpress-video-persisted-queries.md.
[3] Writing dist/posts/graphql-api-for-wordpress-slides/index.html from ./src/posts/graphql-api-for-wordpress-slides.md.
[3] Writing dist/posts/graphql-api-for-wordpress-video/index.html from ./src/posts/graphql-api-for-wordpress-video.md.
[3] Writing dist/posts/deciding-topic-of-article/index.html from ./src/posts/deciding-topic-of-article.md.
[3] Writing dist/posts/graphql-interactive/index.html from ./src/posts/graphql-interactive.md.
[3] Writing dist/posts/graphql-directives-are-underrated/index.html from ./src/posts/graphql-directives-are-underrated.md.
[3] Writing dist/posts/graphql-slides/index.html from ./src/posts/graphql-slides.md.
[3] Writing dist/posts/graphql-query-in-a-single-line/index.html from ./src/posts/graphql-query-in-a-single-line.md.
[3] Writing dist/posts/hylia-rocks/index.html from ./src/posts/hylia-rocks.md.
[3] Writing dist/posts/hello-world/index.html from ./src/posts/hello-world.md.
[3] Writing dist/posts/implementing-a-data-layer-with-backend-components/index.html from ./src/posts/implementing-a-data-layer-with-backend-components.md.
[3] Writing dist/posts/lando-symlinks/index.html from ./src/posts/lando-symlinks.md.
[3] Writing dist/posts/making-wp-vapor/index.html from ./src/posts/making-wp-vapor.md.
[3] Writing dist/posts/mandatory-directives/index.html from ./src/posts/mandatory-directives.md.
[3] Writing dist/posts/merge-composer/index.html from ./src/posts/merge-composer.md.
[3] Writing dist/posts/personal-motivations-for-writing-for-smashing/index.html from ./src/posts/personal-motivations-for-writing-for-smashing.md.
[3] Writing dist/posts/personal-reflexions-on-writing/index.html from ./src/posts/personal-reflexions-on-writing.md.
[3] Writing dist/posts/my-1st-wp-plugin/index.html from ./src/posts/my-1st-wp-plugin.md.
[3] Writing dist/posts/intro-to-schemaless-graphql-api-for-pop/index.html from ./src/posts/intro-to-schemaless-graphql-api-for-pop.md.
[3] Writing dist/posts/pointing-to-local-composer-packages/index.html from ./src/posts/pointing-to-local-composer-packages.md.
[3] Writing dist/posts/pop-api-features/index.html from ./src/posts/pop-api-features.md.
[3] Writing dist/posts/pop-api-now-features-http-caching/index.html from ./src/posts/pop-api-now-features-http-caching.md.
[3] Writing dist/posts/pop-is-now-hundred-percent-compliant-with-graphql/index.html from ./src/posts/pop-is-now-hundred-percent-compliant-with-graphql.md.
[3] Writing dist/posts/pop-api-now-fully-supports-graphql/index.html from ./src/posts/pop-api-now-fully-supports-graphql.md.
[3] Writing dist/posts/requirements-for-writing/index.html from ./src/posts/requirements-for-writing.md.
[3] Writing dist/posts/registering-gutenberg-block-for-cpt-only/index.html from ./src/posts/registering-gutenberg-block-for-cpt-only.md.
[3] Writing dist/posts/remove-if-null-directive/index.html from ./src/posts/remove-if-null-directive.md.
[3] Writing dist/posts/schema-field-directive-versioning/index.html from ./src/posts/schema-field-directive-versioning.md.
[3] Writing dist/posts/simplifying-the-graphql-data-model/index.html from ./src/posts/simplifying-the-graphql-data-model.md.
[3] Writing dist/posts/smashing-person-of-the-week/index.html from ./src/posts/smashing-person-of-the-week.md.
[3] Writing dist/posts/schemaless-graphql-slides/index.html from ./src/posts/schemaless-graphql-slides.md.
[3] Writing dist/posts/submitting-my-1st-rfcs-to-graphql-spec/index.html from ./src/posts/submitting-my-1st-rfcs-to-graphql-spec.md.
[3] Writing dist/posts/what-makes-good-writing-10-smashing-cases/index.html from ./src/posts/what-makes-good-writing-10-smashing-cases.md.
[3] Writing dist/posts/webinar-on-schemaless-graphql/index.html from ./src/posts/webinar-on-schemaless-graphql.md.
[3] Writing dist/posts/why-the-pop-api-can-improve-wp-rest-api/index.html from ./src/posts/why-the-pop-api-can-improve-wp-rest-api.md.
[3] Writing dist/posts/wp-install/index.html from ./src/posts/wp-install.md.
[3] Writing dist/posts/wordcamp-singapore-2019/index.html from ./src/posts/wordcamp-singapore-2019.md.
[3] Copied 8 items / Wrote 120 files in 8.44 seconds (70.3ms each, v0.10.0)
[3] Watching...
[3] [Browsersync] Reloading Browsers...

Using --incremental, all the lines with "Writing" now say "Skipping", but the process still took 8.31 seconds:
[3] Watching...
[3] [Browsersync] Access URLs:
[3]  ------------------------------------
[3]        Local: http://localhost:8080
[3]     External: http://<IP_ADDRESS>:8080
[3]  ------------------------------------
[3]           UI: http://localhost:3001
[3]  UI External: http://localhost:3001
[3]  ------------------------------------
[3] [Browsersync] Serving files from: dist
[3] File changed: src/posts/registering-gutenberg-block-for-cpt-only.md
[3] Skipping dist/feed.xml from ./src/feed.njk.
[3] Skipping dist/admin/index.html from ./src/admin.njk.
[3] Skipping dist/service-worker.js from ./src/service-worker.njk.
[3] Skipping dist/tags/pop/index.html from ./src/tags.njk.
[3] Skipping dist/styleguide/index.html from ./src/styleguide.njk.
[3] Skipping dist/tags/api/index.html from ./src/tags.njk.
[3] Skipping dist/tags/graphql/index.html from ./src/tags.njk.
[3] Skipping dist/tags/schema/index.html from ./src/tags.njk.
[3] Skipping dist/tags/wordpress/index.html from ./src/tags.njk.
[3] Skipping dist/tags/gutenberg/index.html from ./src/tags.njk.
[3] Skipping dist/tags/cope/index.html from ./src/tags.njk.
[3] Skipping dist/tags/smashing/index.html from ./src/tags.njk.
[3] Skipping dist/tags/writing/index.html from ./src/tags.njk.
[3] Skipping dist/tags/composer/index.html from ./src/tags.njk.
[3] Skipping dist/tags/wp-cli/index.html from ./src/tags.njk.
[3] Skipping dist/tags/guide/index.html from ./src/tags.njk.
[3] Skipping dist/tags/components/index.html from ./src/tags.njk.
[3] Skipping dist/tags/back-end/index.html from ./src/tags.njk.
[3] Skipping dist/tags/front-end/index.html from ./src/tags.njk.
[3] Skipping dist/tags/full-stack/index.html from ./src/tags.njk.
[3] Skipping dist/tags/php/index.html from ./src/tags.njk.
[3] Skipping dist/tags/server/index.html from ./src/tags.njk.
[3] Skipping dist/tags/development/index.html from ./src/tags.njk.
[3] Skipping dist/tags/directives/index.html from ./src/tags.njk.
[3] Skipping dist/tags/conference/index.html from ./src/tags.njk.
[3] Skipping dist/tags/proposal/index.html from ./src/tags.njk.
[3] Skipping dist/tags/speaking/index.html from ./src/tags.njk.
[3] Skipping dist/tags/laravel/index.html from ./src/tags.njk.
[3] Skipping dist/tags/symfony/index.html from ./src/tags.njk.
[3] Skipping dist/tags/cms/index.html from ./src/tags.njk.
[3] Skipping dist/tags/concept/index.html from ./src/tags.njk.
[3] Skipping dist/tags/design/index.html from ./src/tags.njk.
[3] Skipping dist/tags/implementation/index.html from ./src/tags.njk.
[3] Skipping dist/tags/github/index.html from ./src/tags.njk.
[3] Skipping dist/tags/project/index.html from ./src/tags.njk.
[3] Skipping dist/tags/mobile/index.html from ./src/tags.njk.
[3] Skipping dist/tags/voyager/index.html from ./src/tags.njk.
[3] Skipping dist/tags/query/index.html from ./src/tags.njk.
[3] Skipping dist/tags/syntax/index.html from ./src/tags.njk.
[3] Skipping dist/tags/blog/index.html from ./src/tags.njk.
[3] Skipping dist/tags/vapor/index.html from ./src/tags.njk.
[3] Skipping dist/tags/serverless/index.html from ./src/tags.njk.
[3] Skipping dist/tags/hylia/index.html from ./src/tags.njk.
[3] Skipping dist/tags/eleventy/index.html from ./src/tags.njk.
[3] Skipping dist/tags/jamstack/index.html from ./src/tags.njk.
[3] Skipping dist/tags/indieweb/index.html from ./src/tags.njk.
[3] Skipping dist/tags/lando/index.html from ./src/tags.njk.
[3] Skipping dist/tags/data/index.html from ./src/tags.njk.
[3] Skipping dist/tags/plugin/index.html from ./src/tags.njk.
[3] Skipping dist/tags/block/index.html from ./src/tags.njk.
[3] Skipping dist/tags/content/index.html from ./src/tags.njk.
[3] Skipping dist/tags/spec/index.html from ./src/tags.njk.
[3] Skipping dist/tags/rest/index.html from ./src/tags.njk.
[3] Skipping dist/tags/bootstrap/index.html from ./src/tags.njk.
[3] Skipping dist/tags/wordcamp/index.html from ./src/tags.njk.
[3] Skipping dist/tags/singapore/index.html from ./src/tags.njk.
[3] Skipping dist/404.html from ./src/404.md.
[3] Skipping dist/speaking/index.html from ./src/speaking.md.
[3] Skipping dist/contact/index.html from ./src/contact.md.
[3] Skipping dist/work/index.html from ./src/work.md.
[3] Skipping dist/thank-you/index.html from ./src/thank-you.md.
[3] Skipping dist/index.html from ./src/index.md.
[3] Skipping dist/posts/index.html from ./src/posts.md.
[3] Skipping dist/writing/index.html from ./src/writing.md.
[3] Skipping dist/posts/bettering-graphql-through-components/index.html from ./src/posts/bettering-graphql-through-components.md.
[3] Skipping dist/posts/backstage-to-cope-with-wp/index.html from ./src/posts/backstage-to-cope-with-wp.md.
[3] Skipping dist/posts/added-namespaces-to-graphql-by-pop/index.html from ./src/posts/added-namespaces-to-graphql-by-pop.md.
[3] Skipping dist/posts/appropriate-content/index.html from ./src/posts/appropriate-content.md.
[3] Skipping dist/posts/bootstrapping-wordpress-projects-with-composer-and-wp-cli/index.html from ./src/posts/bootstrapping-wordpress-projects-with-composer-and-wp-cli.md.
[3] Skipping dist/posts/components-on-the-backend/index.html from ./src/posts/components-on-the-backend.md.
[3] Skipping dist/posts/code-first-vs-schema-first-development-graphql/index.html from ./src/posts/code-first-vs-schema-first-development-graphql.md.
[3] Skipping dist/posts/deciding-topic-of-article/index.html from ./src/posts/deciding-topic-of-article.md.
[3] Skipping dist/posts/cache-and-logtime-directives/index.html from ./src/posts/cache-and-logtime-directives.md.
[3] Skipping dist/posts/confoo-9-proposals/index.html from ./src/posts/confoo-9-proposals.md.
[3] Skipping dist/posts/decoupling-pop-from-wp/index.html from ./src/posts/decoupling-pop-from-wp.md.
[3] Skipping dist/posts/designing-graphql-server-for-optimal-performance/index.html from ./src/posts/designing-graphql-server-for-optimal-performance.md.
[3] Skipping dist/posts/documentation-site/index.html from ./src/posts/documentation-site.md.
[3] Skipping dist/posts/env-constants-instead-of-config/index.html from ./src/posts/env-constants-instead-of-config.md.
[3] Skipping dist/posts/doing-the-writing/index.html from ./src/posts/doing-the-writing.md.
[3] Skipping dist/posts/demonstrating-pop-api-graphql-on-steroids/index.html from ./src/posts/demonstrating-pop-api-graphql-on-steroids.md.
[3] Skipping dist/posts/export-directive/index.html from ./src/posts/export-directive.md.
[3] Skipping dist/posts/graphql-api-for-wordpress-video-custom-endpoints/index.html from ./src/posts/graphql-api-for-wordpress-video-custom-endpoints.md.
[3] Skipping dist/posts/graphql-api-for-wordpress-slides/index.html from ./src/posts/graphql-api-for-wordpress-slides.md.
[3] Skipping dist/posts/exposing-gutenberg-metadata/index.html from ./src/posts/exposing-gutenberg-metadata.md.
[3] Skipping dist/posts/graphql-interactive/index.html from ./src/posts/graphql-interactive.md.
[3] Skipping dist/posts/graphql-api-for-wordpress-video-persisted-queries/index.html from ./src/posts/graphql-api-for-wordpress-video-persisted-queries.md.
[3] Skipping dist/posts/graphql-directives-are-underrated/index.html from ./src/posts/graphql-directives-are-underrated.md.
[3] Skipping dist/posts/graphql-query-in-a-single-line/index.html from ./src/posts/graphql-query-in-a-single-line.md.
[3] Skipping dist/posts/graphql-api-for-wordpress-video/index.html from ./src/posts/graphql-api-for-wordpress-video.md.
[3] Skipping dist/posts/graphql-slides/index.html from ./src/posts/graphql-slides.md.
[3] Skipping dist/posts/hello-world/index.html from ./src/posts/hello-world.md.
[3] Skipping dist/posts/making-wp-vapor/index.html from ./src/posts/making-wp-vapor.md.
[3] Skipping dist/posts/hylia-rocks/index.html from ./src/posts/hylia-rocks.md.
[3] Skipping dist/posts/merge-composer/index.html from ./src/posts/merge-composer.md.
[3] Skipping dist/posts/lando-symlinks/index.html from ./src/posts/lando-symlinks.md.
[3] Skipping dist/posts/implementing-a-data-layer-with-backend-components/index.html from ./src/posts/implementing-a-data-layer-with-backend-components.md.
[3] Skipping dist/posts/my-1st-wp-plugin/index.html from ./src/posts/my-1st-wp-plugin.md.
[3] Skipping dist/posts/intro-to-schemaless-graphql-api-for-pop/index.html from ./src/posts/intro-to-schemaless-graphql-api-for-pop.md.
[3] Skipping dist/posts/personal-reflexions-on-writing/index.html from ./src/posts/personal-reflexions-on-writing.md.
[3] Skipping dist/posts/field-directive-versioning/index.html from ./src/posts/field-directive-versioning.md.
[3] Skipping dist/posts/pointing-to-local-composer-packages/index.html from ./src/posts/pointing-to-local-composer-packages.md.
[3] Skipping dist/posts/pop-api-features/index.html from ./src/posts/pop-api-features.md.
[3] Writing dist/posts/registering-gutenberg-block-for-cpt-only/index.html from ./src/posts/registering-gutenberg-block-for-cpt-only.md.
[3] Skipping dist/posts/pop-api-now-features-http-caching/index.html from ./src/posts/pop-api-now-features-http-caching.md.
[3] Skipping dist/posts/pop-api-now-fully-supports-graphql/index.html from ./src/posts/pop-api-now-fully-supports-graphql.md.
[3] Skipping dist/posts/pop-is-now-hundred-percent-compliant-with-graphql/index.html from ./src/posts/pop-is-now-hundred-percent-compliant-with-graphql.md.
[3] Skipping dist/posts/remove-if-null-directive/index.html from ./src/posts/remove-if-null-directive.md.
[3] Skipping dist/posts/requirements-for-writing/index.html from ./src/posts/requirements-for-writing.md.
[3] Skipping dist/posts/schema-field-directive-versioning/index.html from ./src/posts/schema-field-directive-versioning.md.
[3] Skipping dist/posts/schemaless-graphql-slides/index.html from ./src/posts/schemaless-graphql-slides.md.
[3] Skipping dist/posts/submitting-my-1st-rfcs-to-graphql-spec/index.html from ./src/posts/submitting-my-1st-rfcs-to-graphql-spec.md.
[3] Skipping dist/posts/webinar-on-schemaless-graphql/index.html from ./src/posts/webinar-on-schemaless-graphql.md.
[3] Skipping dist/posts/smashing-person-of-the-week/index.html from ./src/posts/smashing-person-of-the-week.md.
[3] Skipping dist/posts/what-makes-good-writing-10-smashing-cases/index.html from ./src/posts/what-makes-good-writing-10-smashing-cases.md.
[3] Skipping dist/posts/why-the-pop-api-can-improve-wp-rest-api/index.html from ./src/posts/why-the-pop-api-can-improve-wp-rest-api.md.
[3] Skipping dist/posts/simplifying-the-graphql-data-model/index.html from ./src/posts/simplifying-the-graphql-data-model.md.
[3] Skipping dist/posts/wp-install/index.html from ./src/posts/wp-install.md.
[3] Skipping dist/posts/wordcamp-singapore-2019/index.html from ./src/posts/wordcamp-singapore-2019.md.
[3] Skipping dist/posts/mandatory-directives/index.html from ./src/posts/mandatory-directives.md.
[3] Skipping dist/posts/personal-motivations-for-writing-for-smashing/index.html from ./src/posts/personal-motivations-for-writing-for-smashing.md.
[3] Wrote 1 file (skipped 119) in 8.31 seconds (v0.10.0)
[3] Watching...
[3] [Browsersync] Reloading Browsers...

Any idea?


Error: Trying to access array offset on value of type null :: Router.php:286

A clean install, and I get this error.
{"error":"Error: Trying to access array offset on value of type null. File: \/usr\/local\/apache2\/api\/site\/modules\/RestApi\/Router.php:286"}
Strange because I have used this same version of the module before, without any problems.
Can you please help me, of give a direction to debug it myself?

Diggin into this, it seems like the module is not yet php 7.4 compatible.
This fixes it, but I'm not sure if this is right...
  public static function handleFatalError() {     if (error_get_last()!==null){       $last_error = error_get_last();         if ($last_error['type'] === E_ERROR) {           // fatal error           self::handleError(E_ERROR, $last_error['message'], $last_error['file'], $last_error['line']);         }       }   }

I did a similar fix for PHP 7.4
changed
if ($last_error['type'] === E_ERROR) {
to
if ($last_error && $last_error['type'] === E_ERROR) {
Is the Module still in active development @thomasaull  ? Its a great API-Starter for sure! If you need contributions please let us know

Hey @spoetnik, @csaggo
thanks for your issue and solving the problem. I just released v0.0.7 which contains the fix by @csaggo.
Regarding your question: Yes in theory the module is still in active development, my resources over the last year have been kind of limited though. I try my best to offer support and provide fixes for critical things like this issue. However there are two interesting PRs laying around for quite some time now, which I haven't had time to look into (#3 is adding basic-auth by @flydev-fr, #5 adds a lot of new functionality (better jwt-handling, multiple api keys and much more) by @Sebiworld). It's a pity theses aren't integrated yet. So if anyone of you guys have time to do a first code review of those I'd be very thankful :)

I'm going to close this issue for now, feel free to re-open if there's any problems with the new release!


Typos, grammar and naming conventions

Fixed some typos and grammar mistakes. Also made a few changes according to standards and made fixed the wording on signals to be more technically correct.

Thanks!


how to create a recursive component use render function?

What problem does this feature solve?
I want to create a NestedTable component use iview2 tables,  iview table define the columns that can use render function, but i want to render a NestTable in that render function. but I don't know how to do it. I think maybe vue.js can render a recursive component use render function, but I can't find anything for it.
What does the proposed API look like?
<template>
    <Table :columns="columns" :data="data"></Table>
</template>
<script>
export default {
  name: 'NestedTable',
  props: ['data'],
  data() {
    return {
      columns: [
        {
          type: "expand",
          width: 50,
          render: (h, params) => {
            let row = params.row;
            return (
               <NestedTable data={params.row.children}></NestedTable>
            );
          }
        }
      ]
    };
  }
};
}
</script>

Recursive functions need stop conditions, but it looks like you have none.

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server, gitter or StackOverflow.


use std::mem::MaybeUninit::uninit().assume_init() instead of deprecated std::mem::uninitialized().

Small update, the glutin rework is on 1.36.0 minimum Rust version now, since that has been adopted by most distros now and it was causing some build failures.
I want to merge that in the near future for a broader testing audience, so I think we can get on this again after that.

I've decided to add the 1.36.0 update to the latest master separate from the glutin PR. So it should be possible to rebase this on the latest master and fix outstanding issues now @matthiaskrgr.


Issue 11 Use filepath.Join to avoid hardcoded path separators

This should solve #11 . I did not change example_test.go however since /opt/GoCA/CA as a path is a pretty heavy unixism to begin with and would need more than just  filepath.Join to fix.
I also did not change the hardcoded check in caPathInit for ".//" as that seems to be for testing not normal operation.
I did try to extend the storage functions to take variadic parameters where possible so you can for example call LoadFile("dir1", "dir2", "file.pem") instead of LoadFile(filepath.Join("dir1", "dir2", "file.pem"))
Something I did notice however is there is a lot of use of os.Stat(); os.IsNotExist() for example in CheckCertExists This is a bit of an anti pattern it would be better to attempt to open the file and check os.IsNotExist if opening the file returns an error.

@jacobalberty I think the Unix specific path behavior in the test suite, both in caPathInit() and goca_test.go will be a separate issue since that is broader scope than what was originally described in #11 although meets a higher level intent to have Windows compatibility. Good catch.
Could you elaborate on os.Stat(); os.IsNotExist() vs opening the file first and then checking os.IsNotExist? Is the concern a perf hit accessing the disk twice when once is sufficient to do the needed checks? Or, something else?

@necheffa on the os.Stat() thing. It's a race condition. It's entirely possible for it to use os.Stat() and then the file get removed, or created before the results of os.Stat are used.
It's better to use os.OpenFile() and use the error code of that to determine if the file exists, you can use os.O_RDWR|os.O_CREATE|os.O_EXCL as the flags for that call to create the file if it doesnt exist but you want it to. This change would require  adding a file handle to the File struct and using that file handle in calls like LoadFile. This would be a much bigger lift than just moving to filepath.Join though, it's just something I noticed that could be done to make the code more robust in the future.

@jacobalberty I see what you mean. Although, I don't think skipping os.Stat() totally fixes us. If there is a race between os.Stat() and os.IsNotExist(), there are just races in all the public facing storage routines generally.
Another good catch; I'll submit another issue to track this.


Support old browsers

How to let oidc-client-ts work on Chrome 83? We need our production run on old mobile phones.

It does support. Sorry, close the issue.


Make sure AuthenticatorsConfigController is following the How-To-Write-Controllers guide

Currently the AuthenticatorsConfigController is not fully following the How-To-Write-Controllers guide. This needs to be fixed.

I'm taking this, if there's no problem.

Ok, great!

Fixed in #600


Unreachable node cleanup in a cluster

With two nodes in a cluster, if one of the node falls off the network, we see that, after about 60 secs it is shown as false in the cluster status. But can we configure it to fall off the cluster automatically after some time? Is that possible/ configurable? Or do we need to make it leave the cluster ourselves?

Cluster leave is on operation that has important consequences and it's therefore not automatic, see also http://vernemq.com/docs/clustering/. So yes, you need to issue the cluster leave command yourselves to get out of a netsplit situation.

That's great, thanks for the quick response!


Added details on installing Qiskit Terra from Source

Summary
Added Details on how to install Qiskit Terra from source to the file CONTRIBUTING.md and removed the broken link
Details and comments
Fixes #2907

I'll fix that


Changed the description

Checklist:

[ x ] I have read and followed the contribution guidelines.
[ x ] I have read and followed the how to open a pull request guide.
[ x ] My pull request targets the main branch of freeCodeCamp.
[ x ] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

changed in previous pr


fix crash under Android 9

Google freeze apache:http-client after Android 6 and delete it on Android 9.
So on Android 9, this lib works.
But on Android 6 - 8, it will have duplicate http-client lib and the app will crash.
so to solve it just replace the http-client to "cz.msebera.android:httpclient:4.5.8"

Thank you for your contribution. But I realized the dependency might be a bit big for the use I do of it. I also wanted to fix #2.


URL.createObjectURL(MediaStream)

This feature will be abandoned shortly. Do you already anticipate upgrading to resolve this?

Merged: https://github.com/jhuckaby/webcamjs/pull/258
Version 1.0.24 released.


high number of postgis connections / connection pooling

I'm running a tegola seeding run where the data comes from three different databases on the same postgresql server. I've configured tegola with max_connections = 50 and while checking the postgresql performance with pghero it complained about the high number of connections:
High Number of Connections

133 connections

Use connection pooling for better performance. PgBouncer is a solid option.

So I was wondering why we don't use connection pooling, it seems to me cheaper to not create multiple database connections

@stvno tegola does use connection pooling right now. The high number of connections is due to the pool expanding to that max_connections value and keeping the connections open. You can always lower the max_connections value which is helpful if you're scaling horizontally.

ah ok, thanks for the explanation

ah ok, thanks for the explanation


4.2.1 Square link goes to a list of records for the same species at the selected square.

Note: the selected square page is part of Deliverable 3, so we'll have to make it clear that the page isn't functioning correctly yet, either on the page itself or by removing the link.

Have added a landing page for the selected square page, so closing this issue.


The variable X is assigned but never

VSCode Version:1.36.0
OS Version:Windows_NT x64 10.0.17763

Steps to Reproduce:
1.Create function
function test
{
$Something = $Null
$SomeArray = @("a","b","c","d","e","f","g","h","i","j","k","l","m","n","o","p","q","r","s","t","u","v","w","x","y","z")
Get-Random $SomeArray -count 50 | ForEach-Object{[string]$Something += $_}
return $Something
}
You will get:
The variable 'Something' is assigned but never used.PSScriptAnalyzer(PSUseDeclaredVarsMoreThanAssignments) but the function does return the value

Does this issue occur when all extensions are disabled?: No

Please file against the PowerShell extension.


feat(app): add responsive utility attributes

Short description of what this resolves:
Adds responsive attributes for text alignment, transforms, and float.
Changes proposed in this pull request:

moves breakpoint mixins to the ionic.mixins file
adds responsive attributes for text alignment, transform, and
floating elements
adds ability to turn these off so they don’t get added to the css
file using sass variables

Ionic Version: 3.x
Fixes: #10567

👍

@brandyscarney
I am getting error when i am creating new project in ionic 2 on window 10 operating system.
i am use following version of ionic 2,node ,cordova and nmp.
Please help me.
C:\Users\Android>cordova -v
6.5.0
C:\Users\Android>ionic -v
2.2.2
C:\Users\Android>node -v
v7.8.0
C:\Users\Android>npm -v
4.5.0
Your system information:
ordova CLI: 6.5.0
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v7.8.0
Xcode version: Not installed

My Error:
E:\Ionic Data\Demo>ionic start --skippnpm
Starting Ionic Project wizard...
Using directory as root: E:\Ionic Data\Demo
√ Running start wizard:  http://localhost:8900/
Creating an Ionic 2.x app in E:\Ionic Data\Demo\Io2MyApp based on the tabs template.
Downloading: https://github.com/driftyco/ionic2-app-base/archive/master.zip
Downloading: https://github.com/driftyco/ionic2-starter-tabs/archive/master.zip
Installing npm packages (may take a minute or two)...
Error with start undefined
Error Initializing app: There was an error with the spawned command: npminstall
There was an error with the spawned command: npminstall
Creating an Ionic 2.x app in E:\Ionic Data\Demo\Io2MyApp1 based on the tabs template.

@anilthummar this isn't really the place for this kind of support help. Please use the ionic forum or public slack channel. Thanks!

@mhartington
Ok i will use ionic forum and public slack and Thanks for the reply.


Upgrade to hof 13 & hof-theme-govuk 4.0.0: fixes the issue of session timeout page not going back to start

hof 13 upgrades hof-middleware 2.0.0. This changes the locals of startLink to the baseUrl or / if there is no baseUrl. This is used in the error template
The error template is found in hof-template-partials which is a dependency of hof-theme-govuk NOT hof . hof-template-partials has also been updated to 4.0.0. Remove / from startlink of the template, it'll be passed in by locals from hof-middleware.

superceded by this PR https://github.com/UKHomeOffice/right-to-rent-check/pull/53/ so no need for this PR anymore


Which rule should to get error for React is not defined

export default function Test(props) {
  return (

Test

  );
}

I want to get ESlint error on above code that React is not defined.
Which rule should I use?

react/jsx-uses-react

I solved my issue using -
react/react-in-jsx-scope

Looks like both rules are good here :-)


Typescript support for Create React App Samples

Hi, This project really helped to start with a react app for the graph MSAL library, however working through it found that it is missing typescript which is my preference. Hence, updated my copy to Typescript and is working now.  I am interested to make a contribution to this project with the typescript version of the code. I already have the code updated into my git fork, if Ok, will submit a PR. Please let me know

@AsishP thanks for the pull request. I actually refactored the structure of this repo and recreated the project from scratch using TypeScript. See #37

Is the non-typescript version of this tutorial/source code available somewhere? Not everybody uses Typescript...

@ajzeigert thanks for the feedback. Older versions of this tutorial are JS/JSX, but there are no plans to maintain a non-TypeScript version going forward. The last commit that was not TypeScript is here: https://github.com/microsoftgraph/msgraph-training-reactspa/tree/ccbd448e221209103e8c78ebdf8171e5631d22f4
We do have non-React JavaScript tutorial at https://docs.microsoft.com/graph/tutorials/javascript which shows doing these same actions using the Graph SDK from JavaScript.


feat: Scan classes in js/ts files or enable adding classes by hand

I want to add classes to an element using string. For example, Vue3 program below:
<template>
  <div :class="[a]"></div>
</template>

<script setup lang="ts">
import { ref } from 'vue'

let a = ref('i-logos-vue')
</script>

It seems that such won't work in UnoCSS for UnoCSS only add classes that can be scanned. Certainly that string won't be scanned.
So if I want such code to work, we should either enable users to add classes that will be included in the final uno.css file by hand, or scan strings in js/ts files (but I think you won't like the latter, because unexpected problems might happen, although including useless classes won't cause anything).

We already support this usage. From your code block, if you want use dynamic class(change value of a), i suggest you put the changed value of a into the safelist, then you can use dynamic class successfully.

Um sorry I didn't look at the document carefully. Thank you for help me with that!
Issue closed.


Add correct get5 gamestate to get5_status

This updates the gamestate, returned in the get5_status command.
It is implemented in a very rough format, piecing together the information from booleans and methods that I could guess me to, had the correct information.
With that said, it is tested through multiple CS2 matches (loaded from URL, and not practices, scrum, etc.), to work correctly.
The Get5 command get5_status still misses some elements, to be "in spec", to what Get5 respond with.
The spec for Get5 can be seen at: https://splewis.github.io/get5/latest/commands/#get5_status
I can look into making another PR for some of the other information, to try to bring this into spec, with Get5.
The gamestate is changed from an int to a string, due to Get5 using this for their latest stable version.
Why I have made this update:
Even though there exist Get5 web panels, I have made my own.
This web panel is built upon the use of RCON directly to the server. Using already exposed systems, and making the panel a drop-in replacement, without having to look into the API plugin.
That said, I will at some point look into the Get5API. Until then, I would like to use RCON to interact with the system.
With this update, I will be able to run matches through the system.
As this is my first PR to this repo, and work with C#, there may be bugs, improvements or other areas, which does not live up to expected standards.
Please let me know, if any changes have to be made, to incorporate this.

Hey!
Thanks a lot for this PR, it was in my TODO list for a while :D
I'll merge and test it in a day or two, I'll be releasing the new version soon
Thanks!

I have started work on the remaining spec.
This might be another update. But I wanted to start on it. Haven't tested it yet.
https://github.com/The0mikkel/MatchZy/pull/1


Create Related Record item action for Entity List is not displayed when rendered using Liquid

Create Related Record item action for Entity List is not displayed when the list is rendered on web page using Liquid, i.e. {% include "entity_list" key: "My Entity List" %}.
The same action displays fine on the same list when that list is displayed via association with a web page.

I'm curious if you've verified whther the liquid template works as expected in the SaaS version of Dynamics 365 portals? If it doesn't work there we'd probably want to see if it will get fixed there before fixing it here.

Please test if it works in the online portals. If it works there then we can look into this.

I've tested this and it appears to work. If you're still having issues please provide screenshots of the portal and the configuration for the entity list and entity permission records.


Update content security policy

After a scan, we can do some improvements to our content security policy. Take a look at the report, where you can find details to the five medium risks. Implement these changes on the storybook documentation.
### Medium criticality
- [x] CSP: Wildcard Directive
- [x] CSP: script-src unsafe-inline
- [x] CSP: style-src unsafe-inline
- [x] CSP header not set
- [x] Missing anti clickjacking header

### Low criticality, optional
- [ ] TCP Timestamps Information disclosure
- [ ] Server leaks version information via "server" HTTP response header field
- [x] X-Content-Type-Options header missing
- [ ] Open TCP Port: 80 (http)
- [ ] Open TCP Port: 443 (https)

owasp zap hostedscan report 2024-02-27.pdf

@gfellerph what is meant by "Open TCP Port: 80 (http)" and "Open TCP Port: 443 (https)" ?

@steffstefferson these ports are open on the server. Not too sure what to do about it.


Update recipes for L4T R36.3.0 GA

Closing since @madisongh updated a bunch of deb packages as well


CIF-1153 - Generic related product component

added component proxy

Relates to https://github.com/adobe/aem-core-cif-components/pull/164


chore: drop storage lock early

dont hold lock when fetching from fork

right, must have opened this before my first coffee...


Decorator calls unexpected method or is it intentional?

This may be a possible duplicate of issue #757
Even if a decorated instance has #trust method (which overrides Object#trust), a decorator calls Object#trust instead of decorated instance's one.
Here is an example:
class Contract
  def trust
    'I TRUST YOU'
  end
end

class ContractDecorator < Draper::Decorator
  delegate_all
end

contract = Contract.new
ContractDecorator.decorate(contract).trust # =>  #<ContractDecorator:0x00557ae72f6040 @object=#<Contract:0x00557ae7315648>, @context={}>

Is it intentional or not?

@kakipo Sorry it took me so long to respond. I was unable to reproduce this issue. I tried to reproduce the original issue to no avail as well. Is there anyway you can create a sample app that reproduces the issue?


Refactor logging

User description
Goals

divide the log levels into a simple info/debug levels

log every relevant detail from a run, to ensure each run can be properly debugged, in an easy and accessible way:

relevant configuration
input patches
AI prompt
AI text response
AI response extra details
prev and new labels
actual answer sent back to github
more

avoid generic log messages without actual data, to reduce clutter

Type
enhancement, documentation

Description

Enhanced logging across various modules and tools for better debugging and traceability.
Introduced debug logging for AI handlers, PR processing, and tools to capture detailed information.
Configuration changes include setting up logger level via environment variable and adding new configuration section for PR Help tool.

Changes walkthrough
Relevant filesEnhancement11 files

litellm_ai_handler.pyEnhance AI Handler Logging for Better Debugging

pr_agent/algo/ai_handlers/litellm_ai_handler.py
Added debug logging for system and user prompts.  Changed AI response logging to debug level with full response included.

+7/-3

pr_processing.pyEnhance PR Processing Logging for Improved Traceability

pr_agent/algo/pr_processing.py
Added info logging for filtered files, PR main languages, and token counts.  Added debug logging for the final diff after pruning.

+26/-7

git_provider.pyImprove User Description Handling and Logging

pr_agent/git_providers/git_provider.py
Added handling for user_description caching.  Changed existing description logging to debug level.

+5/-1

utils.pyImprove Logging for Repo Settings Application

pr_agent/git_providers/utils.py

Enhanced repo settings application logging.

+1/-1

__init__.pyRefine Logging Setup Conditions

pr_agent/log/init.py

Adjusted JSON logging condition and console logging setup.

+3/-2

pr_code_suggestions.pyRefactor PR Code Suggestions Tool Logging

pr_agent/tools/pr_code_suggestions.py
Added debug logging for relevant configurations and PR diff.  Removed redundant logging statements.

+38/-46

pr_description.pyRefactor PR Description Tool Logging for Clarity

pr_agent/tools/pr_description.py
Added debug logging for relevant configurations, PR title, and body.  Removed redundant logging and added error logging for AI prediction failure.

+22/-39

pr_help_message.pyAdd Debug Logging for PR Help Message Tool Configurations

pr_agent/tools/pr_help_message.py

Added debug logging for relevant configurations.

+4/-0

pr_questions.pyEnhance Logging in PR Questions Tool for Better Debugging

pr_agent/tools/pr_questions.py
Added debug logging for relevant configurations and final PR comment.  Added error logging for PR diff retrieval failure.

+13/-9

pr_reviewer.pyEnhance PR Reviewer Logging for Improved Debugging and Traceability

pr_agent/tools/pr_reviewer.py
Added debug logging for relevant configurations and final PR review.  Added debug logging for AI response.

+12/-25

pr_update_changelog.pyEnhance Logging in PR Update Changelog Tool for Better Clarity

pr_agent/tools/pr_update_changelog.py
Added debug logging for relevant configurations and changelog update answer.  Added error logging for PR diff retrieval failure.

+14/-14

Configuration changes2 files

cli.pyConfigure Logging Level via Environment Variable

pr_agent/cli.py

Modified logger setup to use LOG_LEVEL environment variable.

+2/-1

configuration.tomlAdd Configuration Section for PR Help Tool

pr_agent/settings/configuration.toml

Added a new section for PR Help tool configuration.

+1/-0

✨ PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

/describe

/describe

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

PR Description updated to latest commit (https://github.com/Codium-ai/pr-agent/commit/7dcbdffe3ade9dd9a95956ceb036fb52373b856d)

Preparing PR description...

PR Description updated to latest commit (https://github.com/Codium-ai/pr-agent/commit/7dcbdffe3ade9dd9a95956ceb036fb52373b856d)

/improve

Preparing PR description...

PR Description updated to latest commit (https://github.com/Codium-ai/pr-agent/commit/ba96e147c7874aab0d47299c8877983491bd8be8)

Preparing PR description...

PR Description updated to latest commit (https://github.com/Codium-ai/pr-agent/commit/877796b539c1616521e461cfc1911154ddecd9b1)

Generating PR code suggestions
Work in progress ...

Generating PR code suggestions
Work in progress ...

Generating PR code suggestions
Work in progress ...

Generating PR code suggestions
Work in progress ...


bug: Highlight dissapearing after few ms

Did you check docs and existing issues?

[X] I have read all the todo-comments.nvim docs
[X] I have searched the existing issues of todo-comments.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.0 Build type: RelWithDebInfo LuaJIT 2.1.1713484068
Operating system/version
Linux
Describe the bug
Grabación de pantalla desde 2024-06-04 18-13-58.webm
Steps To Reproduce
This in plugins table
	"folke/todo-comments.nvim",
	dependencies = "nvim-lua/plenary.nvim",
	lazy = true, --optional
	event = { "BufReadPost", "BufWritePost", "BufNewFile" },
	config = function()
		require("todo-comments").setup {
			-- your configuration comes here
			-- or leave it empty to use the default settings
			-- refer to the configuration section below
		}
	end

I can also reproduce it using the Repro.lua file

Expected Behavior
I'd love if the keywords were shown as the image in the repo, with bright colors and colored following text
Repro
-- Reproduced with this file

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/todo-comments.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

This is not a bug. -- TODO is not supposed to be highlighted here since the default the highlight pattern is .*<(KEYWORDS)\s*:. Should close.

exactly

Ahh. How silly. Thank you!

And just so you know, those highlights your see for a split second are not how the ones from todo-comments look like

Yeah, I've no idea where the others came from. Doing keyword: works just fine though :smile:


Fix SendDatagram

SendDatagram returned wrong PeerMaxDatagramFrameSize value

I found that there is already a test there
https://github.com/quic-go/quic-go/blob/7b9d21fbe6b96aa4942703df89fb93acc1ea77a9/integrationtests/self/datagram_test.go#L66.
But MatchError always returns true because DatagramTooLargeError implements Is(error)
func (matcher *MatchErrorMatcher) Match(actual any) (success bool, err error) {
                ...

		// first try the built-in errors.Is
		if errors.Is(actualErr, expected.(error)) {
			return true, nil
		}

https://github.com/quic-go/quic-go/blob/7b9d21fbe6b96aa4942703df89fb93acc1ea77a9/errors.go#L70-L73

It almost passed. There is a race, but it doesn't seem to be related to my changes.

That might be a separate issue. Please don't change the error implementation in this PR.

@nekohasekai Are you still working on this PR? Would be nice to get the fix into the v0.43 release.


Question on evaluation metric choices and meaning

Hi Christian,
I have a shallow background on ML and Data Science, and I have a noob question.
When I evaluate my model, I could not choose evaluation metrics, as there's only a default 'NormalError'.
May I know what does NormalError means? Is the the same as Standard Error, SE = Std.d/ sqrt(n)?
Thank you.

Hi,
Thanks for raising.
This is indeed not a very helpful message, I've updated this to print Normal-NLL and so on for other distributions. Here, NLL is the negative log likelihood of a given distribution. Meaning that, for a given feature vector X, we aim to find the parameters of the distribution (for a normal distribution the mean and std) which best fit the target y, i.e. which minimises the negative log likelihood. This is currently the only supported loss for the distributions.
Hope this helps!


Clean up front-end codes

Check css details

Can one of the admins verify this patch?

no more commit?

yes. it would be enough in this PR

LGTM


release time

you've told you'll release it in one week in LA live video, but ... :)

:(

Seems he didn't released thetool :) ###

Now it is!

@fransr Any reason you didn't publish to the Chrome Web Store? Is it just a matter of creating the required image assets?


Allow configure an expectation to match only when a given parameter is not in the request

That is, if I create two expectations:
Expectation A matches a request with path=/test and no parameters
Expectation B matches a request with path=/test and parameter 'param'='some value'
I want expectation A to not match and expectation B to match, when a request with path=/test and parameter 'param'='some value' is received.
In other words, I want to be able to create an expectation and configure it to match a request where a given parameter is not provided.

One option could be to use a regex matcher for 'param' that matches anything except 'some value'.
However I do agree it could be a good idea to support not behaviour to be able to specify match for anything except a specific value.  I'll leave this issue open and add support for not semantics.

I am not convinced I can use a regexp to achieve the same result.
Let me give you an example:
url1 (with no param): http://path/to
url2 (with param): http://path/to?param=value2
url3 (with param): http://path/to?param=value3
How do I define an expectation to match url1, but not url2 and url3? Please take into account that, when defining the first expectation, I don't always know what value2 and value3 are.

So if you don't the value up front I agree that the only sensible way to match this would be using a not operator.  However do you realise that the order of matching is always in the same order that the expectation are setup.  Therefor if you setup the expectation with the param parameter first then it will be match first for any request to http://path/to.  Basically if you setup the expectations with the most specific requirements first then they'll be matched against first and only if a request does match one of the more specific expectations will it be matched against a less specific expectation.

Thanks for the explanation, James.

Thank you, James. I am looking forward to using the new 'not' operation.


Adding nvidia-docker v2 support

Status
PRODUCTION, safe for the "optional" todos mentioned below.
Description
Adding nvidia docker v2 support as discussed in issue #1161 .
Todos

I'd like to leave these up to the Autoware maintainers.

[ ] I think these new images should become the standard (as Autoware assumes or even needs an nvidia GPU to run on, right?) You can consider renaming current images to something like "-legacy", rather than suffixing these new images with "-nvidia".
[ ] Documentation could be checked on all old references to the old nvidia-docker run command (which is docker run --runtime nvidia these days).

Steps to Test or Reproduce
See #1161.
Make sure to install nvidia-docker v2 and see if the old image works for your (should not work. Opening RVIZ would crash for example). Then try again with the new image and see if it works.

@koenlek this needs to point to develop branch. Can you change the target please?
Thanks

@yk-fujii can you also please check this one?

@koenlek Are the line 7 and 9 in the file build.sh commented on purpose?

Well spotted, I removed the comments, my bad. It now points to develop. I merged upstream develop in my branch and resolved two small merge conflicts that arose from that.

@messi49 : can you make sure this MR is reviewed & merged?

@messi49 Please review :)

@koenlek Thanks for this contribution!  I've tried it myself and I can confirm that it successfully builds a docker image containing Autoware using nvidia-docker2.
I don't think we should maintain support for nvidia-docker (v1) any more.  All (or at least most) of Nvidia's documentation now refers to version 2. We're just making life harder for ourselves by trying to support multiple setups.  On that basis I would remove the second argument 'nvidia' to the run.sh and build.sh files.
I'm also doubtful that we should be compiling the Autoware source code into the docker image that we build.  In most other projects the docker image only serves to provide a consistent set of dependencies. After that it's common for the build script to mount the code in the newly created image and run build commands.

@bdholt1, I agree on both that you should ditch nvidia-docker v1 and that it would be better to exclude source code from the docker image. That is how we use docker at our company too.
The docker image should provide you with a development environment in which you can compile the autoware code (i.e. with all compile-time dependencies available). You can also make a runtime image which contains all the compiled software, but I would advice you to look into catkin install targets to make the deployed filesystem cleaner. When using the install targets you specify a file structure which contains only the files that need to be deployed (e.g. the binaries, launch files, param files, but not the src/header files). Just take a look at any official ros package github repo (e.g. https://github.com/ros-planning/navigation) for an example.
Some recommendations:

figure out catkin install targets, to more cleanly deploy the code.
consider switching to catkin_tools, rather than catkin_make. In my opinion, it is faster (especially for large catkin workspaces), cleaner, and more user friendly. It is created and maintained by the people behind ROS, but for some odd reason, it was never pushed as the official recommended successor of catkin_make (probably to avoid the migration troubles/frustrations that it would enforce to all ROS users). When switching you probably run into some cmake issues (as catkin_tools has no "cmake crosstalk" and thus is a bit more strict on your catkin correctness, i.e. the CMakeLists.xtx and package.xml). With catkin tools, just run catkin config --install (somewhat similar to catkin_make install) to enable the install space. Note that in ROS2, install targets will become obligatory (the devel workspace disappears in favor of the install workspace)..
make two images (check e.g. apollo images too https://hub.docker.com/r/apolloauto/apollo/tags/):

autoware-dev-<version> -> no code, no actual autoware
autoware-release-<version> -> containing deployed autoware code (no code, only binaries and "share" files like params / launch)

for each, you need to make an nvidia and a non nvidia version (the patch I provided will make opengl apps such as rviz work for nvidia, but then its broken on intel integrated graphics...). e.g.

autoware-dev-<version>-nvidia and autoware-dev-<version>

We have a check_nvidia bash function that automatically can 'patch' a docker run command to take care, see this example:
check_nvidia(){
  if nvidia-smi &> /dev/null; then
    export NV_RUN="--runtime=nvidia"
    export NV_TAG_SUFFIX="-nvidia"
  else
    export NV_RUN=""
    export NV_TAG_SUFFIX=""
  fi
}

# adds GUI support and few other tricks
export DOCKER_COMMON_ARGS="--env=DISPLAY \
                           --env=XDG_RUNTIME_DIR \
                           --env=QT_X11_NO_MITSHM=1 \
                           --device=/dev/dri:/dev/dri \
                           -v /tmp/.X11-unix:/tmp/.X11-unix:rw \
                           -v /etc/localtime:/etc/localtime:ro"

xhost +local:docker
check_nvidia
docker run ${NV_RUN} ${DOCKER_COMMON_ARGS:?} -it --rm \
   --name="autoware" \
   -v /dev/bus/usb:/dev/bus/usb \
   -v /home/$USER/.Xauthority:/home/autoware/.Xauthority \
   -v "$HOME/docker_shared:/home/autoware/docker_shared" \
   -v autoware_home:/home/autoware \
   -v /media:/media \
   --net=host  \
   --add-host autoware:<IP_ADDRESS> \
   --hostname=autoware \
   --privileged \
   autoware/autoware:1.7.0-kinetic${NV_TAG_SUFFIX}

Feel free to do with this advice whatever you like. I suggest you take it over from here from me and make some issues (stories) out of it if you like.

@koenlek I completely agree with your comments.  I'd love to take over here but this is a fairly substantial chunk of work so I'm going to suggest that @esteve looks into it.

@koenlek thanks for your contributing, I'll take over from here.

Closing this PR, I'm working on this at #1416 Thanks @koenlek