Dynamic Deferral Intervals

Is there currently a way to adjust the launch agent so that intervals between deferrals can be changed as you get closer to the required installation date? For instance, having the launch agent logic mimic the refresh rates and window times that are set in your configuration profile?

No. That's not how launch agents work. You'd have to build something custom for that.


Add Prometheus metrics for RPC endpoints

Issue summary
Each RPC endpoint hit should be reflected in Forest metrics.
At the end of the day, we want to have dashboards showing how often is a given RPC method called.
Ideally, all methods would go through a single method that increases the counter on its, e.g., RPC name label.
Other information and links

It looks like axum supports middleware.
Here's an example: https://github.com/tokio-rs/axum/blob/main/examples/consume-body-in-extractor-or-middleware/src/main.rs, there probably is a better one. I'm happy to take this on.

Another metric that should be included in the RPC endpoints monitoring is duration, so that it's easily verifiable how long given endpoints take to process.

Constant space quantiles: https://docs.rs/average/latest/average/struct.Quantile.html Can be used to report how long it took to execute 50% of calls, 80% of calls, 99% of calls, etc.

Constant space quantiles: https://docs.rs/average/latest/average/struct.Quantile.html Can be used to report how long it took to execute 50% of calls, 80% of calls, 99% of calls, etc.

@lemmih not sure if it's needed given, e.g., https://prometheus.io/docs/concepts/metric_types/#summary or some other in-built histogram. Some more investigation is needed in that regard.


[Wasm] Disable use of returnaddress in exclusivity diagnostics

Function calls and returns in Wasm are protected by Wasm runtime
and there is no way to get or control return address.

@swift-ci Please test

@compnerd Thank you :)


Issue with parcel build

Trying to bundle face-api.js for an SPA, similar setup to this:
https://github.com/tensorflow/tfjs-examples/blob/master/addition-rnn/package.json#L17
We're trying to do this:
import * as faceapi from 'face-api.js';

Getting this error on the Parcel build:
~/workspace/project/node_modules/face-api.js/build/tinyYolov2/TinyYolov2.js:1:25: Cannot resolve dependency 'tslib'
> 1 | import * as tslib_1 from "tslib";
    |                          ^
  2 | import { TinyYolov2 as TinyYolov2Base } from 'tfjs-tiny-yolov2';
  3 | import { FaceDetection } from '../classes';
  4 | import { BOX_ANCHORS, BOX_ANCHORS_SEPARABLE, DEFAULT_MODEL_NAME, DEFAULT_MODEL_NAME_SEPARABLE_CONV, IOU_THRESHOLD, MEAN_RGB_SEPARABLE, } from './const';

I looked at the package.json, and it seems like tslib should be in dependencies, not devDependencies.
We're working around currently by doing this:
import * as faceapi from 'face-api.js/dist/face-api'

Seems hacky. The other option is setting main to the dist file.

Probably because the build output is still using es6 imports, I think the output should be commonjs again, not sure atm why I changed that.

@justadudewhohacks Not sure why ES6 modules would cause this issue... The issue is being able to refer to node_modules/tslib. It's in devDependencies, which means that it will never be installed when we are consuming face-api.js.
Tensorflow.js uses ES6 modules, and it builds fine:
https://github.com/tensorflow/tfjs/blob/master/src/index.ts

@justadudewhohacks Not sure why ES6 modules would cause this issue... The issue is being able to refer to node_modules/tslib. It's in devDependencies, which means that it will never be installed when we are consuming face-api.js.

Yep you are absolutely right. Sorry for the confusion here.
Besides moving tslib fron devDependencies to dependencies, I think the output should still be commonjs instead of es6, but that's another story.


No fallback function in Fee.sol

Suggest to add a fallback function in the Fee.sol

Great suggestion! Could you please add a couple of words to explain how someone could benefit from having such function?

We can place a event log in the fallback function. If someone send ETH to this contract accidentally, it emits an event log recording who send his ETH and how many. Then we can send the ETH back if we want.

Even better, have a function () { revert(); } so not only we don't have to write logs, we don't to give anything back.


"detected yanked crate" for yanked-and-then-unyanked crate

Describe the bug
Running cargo deny check against a crate with a dependency on anyhow = "1", with 1.0.60 locked in Cargo.lock, I get:
error[A005]: detected yanked crate
  ┌─ /workspace/source/Cargo.lock:6:1
  │
6 │ anyhow 1.0.60 registry+https://github.com/rust-lang/crates.io-index
  │ ------------------------------------------------------------------- yanked version
  │
  = anyhow v1.0.60

This version was yanked but then was unyanked. I didn't know that "unyanked" was a thing, but apparently it is.
To Reproduce
Steps to reproduce the behavior:

Add a dependency on anyhow = "1" and run cargo update.
Run cargo deny check.

Expected behavior
Checks pass, since the crate is no longer yanked.

Ah, this appears to be caused by our CI running cargo deny check before running cargo build, and cargo deny check doesn't update the crates.io index (which is cached), so doesn't notice that the package is unyanked. Sorry for the noise.


cdc crash when upgrade if per-table-memory-quota configured

What did you do?

TiDB cluster with per-table-memory-quota configured.
Upgrade to latest mast er

What did you expect to see?
CDC shoult not crash
What did you see instead?
CDC crashes
Versions of the cluster
[root@maincluster-ticdc-1 /]# /cdc version
Release Version: v8.0.0-alpha
Git Commit Hash: 833943f79c051d0ae7a0fd157e65f1f07b779348
Git Branch: heads/refs/tags/v8.0.0-alpha
UTC Build Time: 2024-02-23 11:38:20
Go Version: go version go1.21.6 linux/amd64
Failpoint Build: false

/severity major

/remove-label may-affects-5.4

/remove-label may-affects-6.1
/remove-label may-affects-6.5
/remove-label may-affects-7.1
/remove-label may-affects-7.5


Poor UI for Search/Replace

Type: Feature Request
Search/Replace has a poor UI, inconsistent behavior, and hidden features.
For reference, the best S/R UI I have used is from the discontinued product Expression Web 4.  If modeled after EW4, VSC's S/R would be much better.
I present a few poor behaviors here.

If a selection is made in code and Ctrl+F or Ctrl+H is pressed, the selected text is not always automatically inserted into the find field automatically. It should be.

When using Replace, tabbing between the search and replace fields should highlight the entire field.

I only recently came to the realization that VSC was remembering previous search and replace strings. That's because the UI has no intuitive controls for moving between them. Instead of choosing specific keystrokes to move up and down, the up- and down-arrows were overloaded, a poor practice. EW4 provides a dropdown for both the S&R fields that displays the last 15 strings for each.

You can examine EW4's S/R UI by downloading EW4 from https://www.oldergeeks.com/downloads/file.php?id=3571 or finding it at its last resting place on the WayBack machine.
Here is what the EW4 dialog looks like.

VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.19045
Modes:

whst more, triggering "find/replace in selection" is also an unwieldy path

select whole text
ctri + f (then enter iguess? will confirm tomorrow)
press alt + l
presh ctrl + f again
type text
press ctrl + h
... proceed

the selected text is not always automatically inserted into the find field automatically

check your editor.find.seedSearchStringFromSelection setting. If setting that to always doesn't always seed the find widget, please open a bug.
Dropdown for search history is covered in https://github.com/microsoft/vscode/issues/23099
And here is a related request to revamp the UI https://github.com/microsoft/vscode/issues/116827

New information after experimentation: If the search text selected for find/replace contains a newline, the text will not be inserted into the find field. Otherwise, it will.


feat: Support Env Var Types in Shellable

Adds support for different environment variable types in scriptable
environment. This allows referencing ssm parameters and secrets manager
values as environment variables.
Bump cdk version dependencies to latest. Had to bump to >=v1.20 for access to codebuild.BuildEnvironmentVariableType.SECRETS_MANAGER.
This is needed for accessing our github access token as an environment variable in @jsii/integ-tests module.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: d19b8eda4331148b8dc3ac2d2aad782efb28e481
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 619e3ff79ac39a4f3d8579cc38a8d3bfce2fb108
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: c7f11befa5d0d778c401158045a5d0905b258d51
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 85595dbd4c0079fdb3879cd89c1c211e6a741c85
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 85595dbd4c0079fdb3879cd89c1c211e6a741c85
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubPipelineAutoBuildProj-eNGjrh4O6eRH
Commit ID: 114ae8890cf75c18ad499d913fbde2deeb8b162b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

pipeline-diff output of note.
Resources
[~] AWS::KMS::Key GitHubPipeline/BuildPipeline/ArtifactsBucketEncryptionKey GitHubPipelineBuildPipelineArtifactsBucketEncryptionKeyFED13A11
 └─ [~] KeyPolicy
     └─ [~] .Statement:
         └─ @@ -13,7 +13,9 @@
            [ ]   "kms:Delete*",
            [ ]   "kms:ScheduleKeyDeletion",
            [ ]   "kms:CancelKeyDeletion",
            [-]   "kms:GenerateDataKey"
            [+]   "kms:GenerateDataKey",
            [+]   "kms:TagResource",
            [+]   "kms:UntagResource"
            [ ] ],
            [ ] "Effect": "Allow",
            [ ] "Principal": {
[~] AWS::S3::Bucket GitHubPipeline/BuildPipeline/ArtifactsBucket GitHubPipelineBuildPipelineArtifactsBucket60481C14
 └─ [+] PublicAccessBlockConfiguration
     └─ {"BlockPublicAcls":true,"BlockPublicPolicy":true,"IgnorePublicAcls":true,"RestrictPublicBuckets":true}
[~] AWS::Lambda::Function SingletonLambda0f4a3ee0692e4249932fa46a833886d8 SingletonLambda0f4a3ee0692e4249932fa46a833886d8CE9FA488
 └─ [~] Code
     └─ [~] .ZipFile:
                   .....


Move Login/Register to react form hook

Description
Previously, these components were checked manually, but since suggestion-book we are using React hook form. So I changed Login/Register to use these. The result is a lot cleaner IMO.

Codecov Report

Merging #13 into suggest-book will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           suggest-book      #13   +/-   ##
=============================================
  Coverage         97.10%   97.10%
=============================================
  Files                 9        9
  Lines               276      276
=============================================
  Hits                268      268
  Misses                8        8

Continue to review full report at Codecov.

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


3 bugfixes and 2 features

Bugfixes:

New GitHub node package changes getting combined status API from 'getCombinedStatus' to 'getCombinedStatusForRef

When the input is undefined or null, hasNextPage() API of GitHub node package will throw an error. Then admin homepage will not show anything.

For those contributors don't have cached pull request, we should validate not only the repo pull request but also validate to shared gist repos/orgs accordingly.

Small features:

Add config settings to allow only need the submitter to sign instead of all the committers of a pull request.

When user change name, we should also identify their previous signature.

Coverage decreased (-0.4%) to 90.852% when pulling dcf9b046ee86a89c2c18b3949da1912b226d8c3a on Microsoft:master into 8b5b11dfa03f6005c1e2e42c685baa5563591da2 on cla-assistant:master.

Coverage decreased (-0.2%) to 91.06% when pulling 86703b5059c50c13ef51896a97a5221649b00e19 on Microsoft:master into 8b5b11dfa03f6005c1e2e42c685baa5563591da2 on cla-assistant:master.

Coverage decreased (-0.1%) to 91.123% when pulling 2c48c039ceb700d0c2e347c3abafc07d3a293b10 on Microsoft:master into 8b5b11dfa03f6005c1e2e42c685baa5563591da2 on cla-assistant:master.

Coverage increased (+0.3%) to 91.54% when pulling 93229fbb67d8b2701cbd1cb6b6878dc0b8f434a1 on Microsoft:master into 8b5b11dfa03f6005c1e2e42c685baa5563591da2 on cla-assistant:master.

Coverage increased (+0.3%) to 91.557% when pulling df9502c16f869cd1c56239486c5dd1c05b14051c on Microsoft:master into f33940d1efd1651ab2ae28cca9a86f8775d38ce0 on cla-assistant:master.


The documentation should describe the require change to get the token

The AUTHORITY value should be changed to replace the common value for Tenant ID.

@gabriel-rcpereira The sample should work with the common endpoint ("https://login.microsoftonline.com/common/"). You don't have to (although you can) replace "common" with your tenant id. Is that not the case for you?

@sangonzal Yes, it was my case but the README doesn't describe this detail. I opened a PR to help other developers.

@sangonzal Now I understood what you wanted mean. That approach didn't work for me, what did I wrong ? I could complete the flow to get the token only after I switched the common resource by <tenant id>.

@gabriel-rcpereira What was the error that you got when you tried using common?

I'm closing the issue. The time expired.


possible node lost in route table

when adding multiple node at a same time, is it possible that flannel may loss some of them? I'm encountering a strange problem recently, I added 10 nodes at a same time, and I found one node got wrong route table.
I traced the adding process, and I'm not sure is it a problem of flanneld
here's my guessing
1、flannel get all of nodes and update route table
2、a new node added to cluster
3、flannel set watching on etcd's Node
is it possible for flannel losing the node after fetched all nodes but before setup watching?
I found flannel get all nodes before watching for new subnet leases, but I'm not sure the whole process of flannel building route table.
Expected Behavior

when adding node flannel should update route table correctly

Current Behavior

one node lost in route table

Possible Solution

maybe update whole route table every 5 minutes? or setup watching before fetching all node to build route table?

Steps to Reproduce (for bugs)

add 10 node at a same time using aws or aliyun's image

Context

I'm trying to scale out 10 or more machine using image quickly in cloud

Your Environment

Flannel version: 0.11
Backend used (e.g. vxlan or udp): vxlan
Etcd version: 2
Kubernetes version (if used): 1.14.1
Operating System and version: CentOS 7
Link to your project (optional):

#1034 is a related one

I think I've figured it out. I found a default bridge cni config in /etc/cni/net.d on the missing machine, which prevent other node discovery it...


Bump SDKs

@ollie-stytch I think some of these changes are overriden by Nikhil's recent merge, and I've gotta look at the authenticateJWT stuff in consumer so can handle porting it to B2B, too. Is this PR good to just close? Or is there something else included that I'm missing?


Website

In this branch of the project, I implemented the following functions.

I created a Navbar to navigate through the page.
2.I created 3 pages(Home, calculator and Quotes).
I used routers to implement navigation
I added little css styling.

Thank you
Sent from Yahoo Mail on Android
On Wed, Mar 1, 2023 at 12:58 AM, @.***> wrote:
@alexander16108 approved this pull request.
Hi @Divinity-dev ,
Your project is complete! There is nothing else to say other than... it's time to merge it
Congratulations! 🎉
Highlights
✔ No linter errors
✔ Gitflow was correctly used
✔ Good PR and Description
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding! 👏 👏 👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


[tool] HttpException: HttpException: Connection closed before full header was received, uri = http://localhost:50094/devtools/page/3036A94908353E86E183B6A40F54104B

Represents 12.01% of CLI tool crashes on 3.24.0 as of 8/11/24. This has existed since 3.22.3 (and probably prior), but it had roughly 20-25% of the number of affected clients throughout the lifetime of that version.
Observed from flutter run, flutter run -d chrome, flutter run -d chrome --machine (e.g. run --machine --start-paused -d chrome --devtools-server-address http://<IP_ADDRESS>:9100/ --target /<path to project>/lib/main.dart). Non-exhaustive list.
We don't get stack traces here due to https://github.com/dart-lang/sdk/issues/44994. This is all we get:
HttpException: Connection closed before full header was received, uri = http://localhost:50558/devtools/page/31E436435F75FDDC3F156C20242E9ECD

cc @bkonyi @DanTup in case any one has ideas on how to even begin to troubleshoot this. This crash appears to have become much more common on 3.24.0 (4x-5x compared to 3.23.3 to-date).

cc @kenzieschmoll

A DevTools extension request would have 'devtools_extensions' in the path, so this doesn't look related to DevTools extensions. Usually requests with devtools in the path occur when DevTools is served from DDS.

A DevTools extension request would have 'devtools_extensions' in the path, so this doesn't look related to DevTools extensions. Usually requests with devtools in the path occur when DevTools is served from DDS.

What would result in us making a request to page/3036A94908353E86E183B6A40F54104B then?

@andrewkolos do we have any information about whether users were experiencing this error when using an IDE (VS Code, Android Studio, etc.) or when running flutter commands from the CLI? DevTools is served differently in each of these use cases so that would help us narrow down the source of the crash.

@andrewkolos do we have any information about whether users were experiencing this error when using an IDE (VS Code, Android Studio, etc.) or when running flutter commands from the CLI? DevTools is served differently in each of these use cases so that would help us narrow down the source of the crash.

I don't think so, unfortunately. All we really have is the command itself (which I listed a few of in the description). I see some bare flutter runs and some flutter run --machine, so I assume it's happening in both contexts.

This is most likely a bug in ResidentWebRunner.run. Notice that it does not list HttpException among exceptions it handles and just rethrows it. The exception itself most likely originates in attach which calls ChromeTab.connect which establishes WebSocket connection to the Chrome DevTools protocol: see  ChromeTab.connect which calls WipConnection.connect which calls WebSocket.connect. The URL used for the connection is webSocketDebuggerUrl which has the following comment:
  /// Ex. `ws://localhost:1234/devtools/page/4F98236D-4EB0-7C6C-5DD1-AF9B6BE4BC71`.
  String get webSocketDebuggerUrl => _map['webSocketDebuggerUrl'] as String;

Matches[^1] the format we see in the log.
WebSocket.connect will throw this sort of exception if connection terminates abruptly. (maybe there is some sort of race or browser crashes?).
Looking at this code I also noticed that ResidentWebRunner neglects to pass onError callback to ChromeTab.connect. This seems like an oversight (and honestly a questionable API design on the webkit_inspection_protocol.dart package). This callback is used as an onError callback on the WebSocket stream once connection is established. Not passing onError means that all exceptions which occur later (after connection was established and upgraded to WebSocket) are going to be uncaught and will crash Flutter tool as well.
[^1]: That's how I located that package to begin with: did GitHub codesearch for devtools/page, then went backwards into Flutter tool to see how the package is used.

Thanks @mraleph!

This is most likely a bug in ResidentWebRunner.run. Notice that it does not list HttpException among exceptions it handles and just rethrows it

Interesting, judging by the other exceptions handled, I do feel like HttpException should be handled here, so I will probably patch this.

WebSocket.connect will throw this sort of exception if connection terminates abruptly. (maybe there is some sort of race or browser crashes?).

I still find this crash becoming much more common 3.24.0 to be concerning. @yjbanov, do you happen to be aware of any 3.24.0 regressions in flutter web that could have potentially aggravated whatever underlying issue might exist here?

This appears to still be happening on 3.24.1.

If anyone that is experiencing this crash happens to be reading this, please let us know if you are able to consistently reproduce this.

This appears to still be happening on 3.24.1.

I failed to realize this initially, but the error message being reported now is different: HttpException: Connection closed before full header was received, uri = http://localhost:52097/json. Maybe this should be a different issue.

Filed https://github.com/flutter/flutter/issues/153972.


INTMDB-263: Added Private_link_endpoint_adl resource to go-client

Description
Added PrivateLinkEndpointADL resource to go-client to manage DataLake and Online Archive private link endpoints
Link to any related issue(s): INTMDB-263
Type of change:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Required Checklist:

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added any necessary documentation (if appropriate)
[x] I have run make fmt and formatted my code

Further comments

@gssbzn I cannot merge due my access level, can you merge it, please?


update docker-compose image to latest horti fix

@nomulex thanks! Can you merge too? I don't have access.


bump EXPECTED_GO_VERSION to 1.19.4 and generate updated protos

Description
https://github.com/stackrox/stackrox/pull/4658 started the bump from go1.18.4 to 1.19.4, but it missed EXPECTED_GO_VERSION and generating new proto files which were re-styled due to the version bump. This PR hopefully completes the update to go1.19.4.
Checklist

[x] Investigated and inspected CI test results
~[ ] Unit test and regression tests added~
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

Testing Performed
CI
I updated EXPECTED_GO_VERSION and then ran both make proto-generated-srcs and gogen .

https://github.com/openshift/release/blob/master/ci-operator/config/stackrox/stackrox/stackrox-stackrox-master.yaml#L26 will need to be updated for this to work

/test grouped-static-checks

Fixes ROX-12582.


Feature request: editing JSON files instead Markdown for content

How hard would it be to support editing JSON files instead of only Markdown?
For a portfolio for example, I would have only 1 JSON file containing all my portfolio entries instead of all the separate markdown files.

The CMS already has this, actually, just needs to be documented. For an example, check out the settings collection in the repo example, where a json file and a yaml file are both set up to be edited through the CMS:
- name: "settings"
    label: "Settings"
    files:
      - name: "general"
        label: "Site Settings"
        file: "_data/settings.json"
        description: "General Site Settings"
        fields:
          - {label: "Global title", name: "site_title", widget: "string"}
          - label: "Post Settings"
            name: posts
            widget: "object"
            fields:
              - {label: "Number of posts on frontpage", name: front_limit, widget: number}
              - {label: "Default Author", name: author, widget: string}
              - {label: "Default Thumbnail", name: thumb, widget: image, class: "thumb"}

      - name: "authors"
        label: "Authors"
        file: "_data/authors.yml"
        description: "Author descriptions"
        fields:
          - name: authors
            label: Authors
            widget: list
            fields:
              - {label: "Name", name: "name", widget: "string"}
              - {label: "Description", name: "description", widget: "markdown"}

@MarcCoet closing for now, please comment if this doesn't address your question.


Delete files not using

Hi @kheiakiyama, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@kheiakiyama, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

:1


Set default Node.js version to 6.5.0

I would wait until v6 enters LTS before bumping up the default. 3 weeks left

@NitroGhost It is currently set to 6.4.0. So...

That is true, but the node team have 3 weeks to finalise v6 for LTS. Once
it's in LTS, it will only be changing version when there's security
patches. Between now and when it's in LTS, it might change version a lot.
It makes more sense to wait so that the maintainer isn't bumping the
version regularly
On 8 Sep 2016 12:27 p.m., "Gocho Mugo"<EMAIL_ADDRESS>wrote:

@NitroGhost https://github.com/NitroGhost It is currently set to 6.4.0.
So...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/icflorescu/openshift-cartridge-nodejs/pull/67#issuecomment-245569066,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgRY1qEppSKJbxK9JVfG_0E_FU5FMIBks5qn_EbgaJpZM4Jzh5J
.

@NitroGhost That's where the actual default version is defined: https://github.com/icflorescu/openshift-cartridge-nodejs/blob/master/lib/util#L9 (ie. it resolves to 6.5.0 already and PR is just for documentation).
The reasoning for "unstable" is here: https://github.com/icflorescu/openshift-cartridge-nodejs/issues/48#issuecomment-228767440 (ie. semver.io "stable" is heavily opinionated by Heroku staff).

@apihlaja when v6 lands in LTS, wouldn't the unstable start revolving to v7? still makes sense to wait 3 weeks to change the version because we know for sure that it's all changing on the 1st October

@NitroGhost semver.io resolves node "stable" to 5.11.1 at the moment, which is neither lastest nor LTS. For me, it looks pretty random... They have year old issue about updating to new node.js versioning scheme but nothing has happened. I'd call whole site dead at this point.. I'd bet @icflorescu wouldn't mind to see PR removing semver.io ties but obviously, no one wants to spend much time for current gen Openshift when future is unknown.

Sorry for not pulling this earlier, but I'm currently in a long awaited trekking holiday with sporadic Internet connectivity :-)

Totally agree about semver's random definition of "stable" vs "unstable". That's why we have the option to force/lock the cartridge to a specific version.


Ethernet shield W5500 reset

I'm trying to make a sketch to perform a hardware reset of the W5500 ethernet shield. I need this to recover the status of hide which in some cases is the shield. I inserted a pinout on arduino and connected this to the shield of the W5500. So far everything is fine the card will reset and I can again ping from the network. After the reset, however, the MySQL connector is no longer able to connect to the server. Can you help me? I put the sketch I am using for the tests on my repository. In the repository I have also inserted the output of the serial monitor with debugging at the maximum level.
The repository is: https://github.com/gianfry60/MySQL_MariaDB_Generic_Reset_ETH
Thank you

After the reset, however, the MySQL connector is no longer able to connect to the server.

You have to reset the board, not just the Ethernet. I also don't understand why you need to do that. If you're afraid of board hanging, just write some kind of WDT to reset the whole board.

The MySQL_MariaDB_Generic needs complicated authentication between server and client before every successful connection. You can not just reset the Ethernet board, destroying all stored authentication data and expect normal working scenario.
You certainly can achieve that unnecessary ETH reset by rewriting the library (Ethernet as well as this library), but I suggest not to and I won't spend time to do that.


ORSP - Project Generation && New Consent Group generation

The ORSP team would like to re-configure some of their current intake forms for generating new projects, as well as adding intake forms which determine the type of project, and confirm the project's GDPR compliance.
https://broadinstitute.atlassian.net/browse/BTRX-282
The ORSP team would like to re-configure some of their current intake forms for generating new Consent Group and confirm the project's GDPR compliance.
https://broadinstitute.atlassian.net/browse/BTRX-473

[ ] Submitter: Verify all tests go green, including CI tests
[ ] Submitter: Get a thumb from @rushtong
[ ] Submitter: Merge to develop using github's "Squash and Merge" feature
[ ] Submitter: Delete branch after merge

@rushtong we worked on your feedback. Please let us know if you have any other comment. Thanks!!


Attempt 2 which addresses presented concerns in pr#64

This is a second attempt to reorganize this project so that it both can lazily load responses for interacting with the database using asynchronous requests and maintain the same api reference.
Something I've realized is that there are a lot of cases where the simplest way to organize the project for development diverges with the existing api, which is intended to be concise for use. So I've tried splitting up the two through creation of the arango_internals package. This passes all the original tests without changing imports at all. The changes which existed in the last pr to user management and async jobs still exist.
All of the changes suggested in the original pr, with the exception of the relative imports in init.py files which I believe are not an issue, have been implemented.
Thoughts?

Coverage increased (+0.9%) to 100.0% when pulling 066a7d05eab1b2a3a14e595b0bca2e0c5937b69d on dancollins34:dev-3 into 31c356e68bb217432d2bbd250d8adf1e09052578 on joowani:dev.


Trouble with Shiny App

Hi, I attempted to run the code for creating shot charts but all I am getting is a blank window.  There doesn't seem to be any error messages to help.  When I hit "Stop" I get the following:
Warning: Error in curl::curl_fetch_memory: Operation was aborted by an application callback
59: curl::curl_fetch_memory
58: request_fetch.write_memory
56: request_perform
55: GET
Can you help?  Thanks

Hi and thanks, this should be fixed by https://github.com/toddwschneider/ballr/commit/10213269e2b491935e60b7d23703c6f335998a0e


input benthos_lab option multipart:false doesn't appear to make a difference

Hi,
I have a  text file that I want to process each line individually in a pipeline. I expected input type benthos_lab to work similar to 'file' input, in that by default each individual input line would be treated as a single message.
That doesn't appear to be the case as I had to nest my pipeline in a for_each to get it to work properly.
I tried adding "multipart: false" but the results are the same.
I then ran the same config directly under benthos, after changing the input type to 'file'.
In my test directly on benthos,  changing the input file to multipart: true caused it to behave like input benthos_lab does (e.g. incorrectly for my use-case)
That makes me think benthos_lab input defaults to multipart: true, and cannot be changed to multipart: false.

Hey @bkcsfi, right now you have two options:

Input data is read as batches, where each line is a message of a batch, and you can insert blank lines between messages to split the batches
Input data is read as a single message (containing all the content including line breaks)

It sounds like what you want can either be solved by inserting blank lines between each line (which is lame) or I can add a third option where each line is a single message batch, similar to the file and stdin inputs.
I'll mark this ticket as an enhancement for implementing the third option, but obviously I won't get mad if you just decide to add blank lines.

Hi, thanks for the quick response.
I've watched all your videos and was using the labs version to setup a pipeline that can handle both plain text and json as input similar to your "intro to labs" video. It was confusing because the settings were set to "each line is a message".
Would it be clearer if this option was named "each line is a message in a multi-part batch"  vs what I was really looking for which is "each  line is a message in a single part batch".
Perhaps the phrasing is wrong, I'm still learning..

Yeah I like that idea, I've I changed the names to try and make it clearer. We now have three options:

each line is a message of a batch
each line is a single message batch
single message

Implemented: https://github.com/benthosdev/benthos-lab/commit/d7893fe38363032fc5b69ff62a8b52d32368d616
Released: https://github.com/benthosdev/benthos-lab/releases/tag/v0.7.1
Currently upgrading the production deployment.


Documentation

Documentation for how to use project.

is there anything else I can add for the developer doc section/make another markdown for that?


Debian Azure CLI Repository Error

As of today, the Azure CLI debian software repository seems to have an error, since there seems to be a file size (or checksum?) mismatch. This error seems to be related to the new release (v 2.0.79), since last week everything was working fine.
The error message reads:
Failed to fetch https://packages.microsoft.com/repos/azure-cli/dists/bionic/main/binary-amd64/Packages.bz2  File has unexpected size (7745 != 7578)
Occurence of the error when executing either one of the commands in an Ubuntu (bionic) environment:

curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
AZ_REPO=$(lsb_release -cs)
echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPO main" |
sudo tee /etc/apt/sources.list.d/azure-cli.list
sudo apt-get update

Has anyone else experienced the same error? Are there any workarounds?
Thanks
Issue has been resolved by Microsoft

@InitionsJulius Glad to know that the issue is resolved. Thanks for the update.
For the benefit of broader audience who might face similar issue, do you mind sharing information on what was done to resolve the issue. Thanks.

The problem was resolved by Microsoft developers upon contacting them.


Implement node publish-subscribe protocol

DEPENDS:

https://github.com/thenewboston-developers/thenewboston-node/issues/415

TODO:

REST API calls to nodes to deliver the message
Get list of nodes from the blockchain

this is described in details in other tasks


Support getblock with verbosity=1

Motivation
To workaround a lightwalletd issue related to V5 TXIDs, it was recently changed to get the transactions IDs using a getblock call with verbose=1.
That was the cause of one of the issues found during ZecWallet Lite + lightwalletd + Zebra tests on Testnet, so we might want to support that so we can test it further.
Specifications

Designs
Add support for verbose=1. Note that we just need the tx field (the list of TXIDs) for now.
Testing:

Add a snapshot test for verbose=1.
Manually run zcash-rpc-diff with verbose=1

Related Work

I added:
Testing:

Add a snapshot test for verbose=1.
Manually run zcash-rpc-diff with verbose=1


Fix crowbar distance to work on adjacent tiles

This limits crowbar to work on adjacent tiles only.
I assume here that adjacent are not more than 1.5 tiles far away.
Do you propose this code to be moved to some other place? Or is there already some code that calculates this distance?

@PJB3005 Thanks for the review, changes done.


Update _index.md

Moved up the latest Helm release instructions and removed redundant instructions.

done, thanks!

done, thanks!


shadowView super (of ID 415) not found

Issue Description
ExceptionsManager.js:76 Exception 'shadowView super (of ID 415) not found' was thrown while invoking replaceExistingNonRootView on target RCTUIManager with params (
415,
427
)
Steps to Reproduce / Code Snippets
_renderTabView() {
    const {sorts, loadingSort} = this.props;
    let content;
    if (sorts.length > 0 && !loadingSort) {
        content = <ScrollableTabView
            style={styles.category}
            initialPage={0}
            renderTabBar={()=><ScrollableTabBar style={{borderWidth: 0}} inactiveTextColor='#fff'/>}>
            {sorts.map((sort)=>this._renderTab(sort))}
        </ScrollableTabView>
    }
    return content;
}

_renderTab(sort) {
    const {merchants, isRefreshing} = this.props;
    const dataSource = this.state.dataSource.cloneWithRows(merchants[sort.sortid] === undefined ? [] : merchants[sort.sortid]);
    return <View key={sort.sortid} tabLabel={sort.sortname}>
        <YYListView
            dataSource={dataSource}
            renderRow={this._renderRow.bind(this) }
        />
    </View>;
}`

 _renderRow(row) {
        <View>......</View>
    }

export default class YYListView extends Component {
    // 构造
    constructor(props) {
        super(props);
    }

render() {
    const {dataSource, renderRow, onEndReached, renderFooter, refreshing, onRefresh} = this.props;
    let view;
    if(!refreshing && dataSource.getRowCount() === 0){
        view = <Status titleIcon={require('../../image/no-data.png')}/>;
    }else{
        view = <ListView
            dataSource={dataSource}
            renderRow={renderRow}
            enableEmptySections={true}
            onEndReached={onEndReached}
            onEndReachedThreshold={0}
            renderFooter={renderFooter}
            refreshControl={
          <RefreshControl
            refreshing={refreshing}
            onRefresh={onRefresh}
            tintColor="#ffffff"
            title="加载中..."
            titleColor="#ffffff"
            main="#ffffff"
            progressBackgroundColor="#ffffff"
            />}
        />
    }
    return (view)
}
}
YYListView.propTypes = {
    dataSource: PropTypes.any.isRequired,
    renderRow:  PropTypes.func.isRequired,
    refreshing: PropTypes.bool.isRequired,
    onEndReached: PropTypes.func,
    renderFooter: PropTypes.func,
    onRefresh: PropTypes.func
}'

Additional Information

React Native version:
"react": "15.2.1",
"react-native": "0.31.0",
Platform(s) (iOS, Android, or both?): IOS , and not run is Android yet.
Operating System (macOS, Linux, or Windows?): MACOS

I forgot a return in [_renderRow] ....

I also have this problem and my code looks fine. These error messages are really horrible!

had same problem

{media.map ((elem)=> (
<View key={${id}}>...
))}

turns out id's definition was missing...

I just ran into this same error when I had an exception being thrown in my mapStateToProps. So just one more place to look for anyone else encountering this.

@kkamperschroer thank you

I've got this after I eslint'ed the entire project, by the way.
So many possibilities...

Strangely I can repro this by adding a double-slash comment in between two rendered React Native items.  Changing the comment to correct style {/* My comment */} fixes the issue.
Seems like a fairly strange error message for this issue!  The linter also does not pick this up.
<Text>...</Text>
// Invalid comment style
<Text>...</Text>

Full error message:
Exception 'shadowView super (of ID 46) not found' was thrown while invoking replaceExistingNonViewRoot on target UIManager with params (
  46,
  120
)

RCTFatal

I have the exact same isssue

Exception 'shadowView super (of ID 46) not found' was thrown while invoking replaceExistingNonViewRoot on target UIManager with params (
49,
56
)
RCTFatal

But I don't have any comments between the components in my code. It started to happen after upgrading to (0.46.4), it's pretty tough to track down where it comes from.

I've seen this today when trying to implement Native Base Picker as well, without any bogus comments.
React Native may be showing this error message in a variety of cases now, which seems like a bug.

Update:
It appears that this error was shown to me because of react-navigation update. There were some breaking changes in there and I had to update my codebase to fix them, after that, there was no more shadowView error.

@brzezinskip Can you provide a few details?  We're using react-navigation as well.

@lukecwilliams We were using such syntax for navigationOptions:
    public static navigationOptions = {
        header: {
            visible: false,
        },
    };

which has been changed to
    public static navigationOptions = {
        header: null,
    };

and
    public static navigationOptions = {
        title: ({ state }) => state.params.title,
        header: {
            visible: false,
        },
    };

which has been changed to
    public static navigationOptions =
        ({ navigation }) => ({
            title: navigation.state.params.title,
            header: null,
        })

might not be the case for you though.

@brzezinskip Not our case, but thanks for pointing those out.


Doesn't install cleanly using Homebrew

I think the symlinks created by the installer are pointing to the old directory. The git-* binaries are in src now. Check this and address if broken.

This can be closed


[Accessibility]A11y_VSCode_ColorTheme_ColorContrast:Color contrast ratio is less than 4.5:1 for the Red colored content when not focused.

Environment Details:
VSCode Version : 1.24.0
OS Version : Win10
Additional Details:
MAS Violated : MAS 1.4.3
Tools Used : Color Contrast Analyzer
Repro Steps:
1)Navigate to Settings-->Select color theme -->Select solarized light
2)Check color contrast ratio for the Explorer content on the screen.
Actual:
Color contrast ratio is less than 4.5:1 for the Red colored content when not focused.
Similar issue is observed in following themes:
Dark visual studio
Dark Default dark
Kimbie dark
Monokai
Monokai Dimmed
Red
Solarized dark
Tomorrow night blue
Expected:
Color contrast ratio should be more than 4.5:1 for the content on a screen.
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx

User Impact:
The low vision/visually impaired users will not be able to view the content properly.
MAS Reference:
MAS 1.4.3 - [https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={a73546c7-765f-489c-b18f-afb659fe99e6}
](url)
Attachment For Reference:

Dup of https://github.com/Microsoft/vscode/issues/56785#event-1796883659


self.model(img, augment=False) does not work

Hi, Thanks for the repo. Whenever I am running it, I am getting an error on the self.model command. It seems it does not output pred and logits but a single tensor when given a tensor. Not sure how this line could be updated.
Traceback (most recent call last):
File "C:\Users\kusari\Documents\Camera_error_sources\yolov5-gradcam\main.py", line 124, in
main(args.img_path)
File "C:\Users\kusari\Documents\Camera_error_sources\yolov5-gradcam\main.py", line 67, in main
saliency_method = YOLOV5GradCAM(model=model, layer_name=args.target_layer, img_size=input_size)
File "C:\Users\kusari\Documents\Camera_error_sources\yolov5-gradcam\models\gradcam.py", line 44, in init
self.model(torch.zeros(1, 3, *img_size, device=device))
File "C:\Users\kusari\AppData\Local\Programs\Python\Python39\lib\site-packages\torch\nn\modules\module.py", line 1102, in _call_impl
return forward_call(*input, **kwargs)
File "C:\Users\kusari\Documents\Camera_error_sources\yolov5-gradcam\models\yolo_v5_object_detector.py", line 167, in forward
prediction, logits, _ = self.model(img, augment=False)
ValueError: not enough values to unpack (expected 3, got 2)

May I ask if your problem has been resolved? I have also encountered the same problem
Traceback (most recent call last):
File "D:\jupyter\pythonProject\yolov5-gradcam-master\main.py", line 124, in
main(args.img_path)
File "D:\jupyter\pythonProject\yolov5-gradcam-master\main.py", line 67, in main
saliency_method = YOLOV5GradCAM(model=model, layer_name=args.target_layer, img_size=input_size)
File "D:\jupyter\pythonProject\yolov5-gradcam-master\models\gradcam.py", line 44, in init
self.model(torch.zeros(1, 3, *img_size, device=device))
File "C:\Users\y\AppData\Roaming\Python\Python39\site-packages\torch\nn\modules\module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "D:\jupyter\pythonProject\yolov5-gradcam-master\models\yolo_v5_object_detector.py", line 167, in forward
prediction, logits, _ = self.model(img, augment=False)
ValueError: not enough values to unpack (expected 3, got 2)

Waiting for your reply


Refactor StrongboxAuthenticationFilter extend Spring's AuthenticationFilter interface and related re-workings

Pull Request Description
This pull request makes progress on #1552
This satisfies the following

[x] Make org.carlspring.strongbox.security.authentication.StrongboxAuthenticationFilter extend the org.springframework.security.web.authentication.AuthenticationFilter
[x] Re-work AuthenticationSupplier implementations to AuthenticationConverter implementations
[x] Re-work AuthenticationSuppliers implementation to DelegatingAuthenticationConverter (it should delegate to first AuthenticationConverter that will return not null Authentication object)
[x] Check that new StrongboxAuthenticationFilter implementation consistent with logic that we currently have
[x] Provide unit tests that check different authentication scenarios with few mocked AuthenticationConverter implementations

Acceptance Test

[x] Building the code with mvn clean install -Dintegration.tests still works.
[x] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[ ] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[ ] The tests in the strongbox-web-integration-tests still run properly.

Questions

Does this pull request break backward compatibility?

[ ] Yes
[ ] No

Does this pull request require other pull requests to be merged first?

[ ] Yes, please see #...
[x] No

Does this require an update of the documentation?

[ ] Yes, please see strongbox/strongbox-docs#{PR_NUMBER}
[x] No

Did you rebase this PR? Somehow there are changes which shouldn't be there like
https://github.com/strongbox/strongbox/pull/1866/files/a26dca2e112895b2d26919a5d0b43b26a9f22e4d..f2e141beedb63b8c9d8aae95312b312daeca361a#diff-04c6e90faac2675aa89e2176d2eec7d8R98
The link was already correct.

@soapdogg ,
How are things going with this pull request? Is it clear for you what still needs to be done?

@carlspring
Hi,
Not necessarily -- it does seem like some of the comments on the pull request are contradicting to what is in the task description so it's unclear what direction needs to be taken with this.
Feel free to unassign the task from me if someone else wants to take a look.


babili with browserify + babelify error on production build

This is my browserify configuration in package.json.
"browserify": {
  "extensions": [
    ".js",
    ".jsx"
  ],
  "transform": [
    [
      "babelify",
      {
        "presets": [
          "es2015",
          "react"
        ],
        "env": {
          "production": {
            "presets": [
              "babili"
            ]
          }
        },
        "plugins": [
          "transform-class-properties",
          "transform-async-to-generator",
          "transform-object-rest-spread",
          "transform-runtime",
          "../../../lib/utils/babelRelayPlugin"
        ]
      }
    ],
    [
      "envify"
    ]
  ]
}

But whenever I do a production build, I get the following error:
TypeErrorr /home/computer/project/lib/app/views/components/ArticleHeader.jsx: Property expressions[0] of SequenceExpression expected node to be of a type ["Expression"] but instead got undefined
    at validate (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-types/lib/definitions/index.js:109:13)
    at validator (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-types/lib/definitions/index.js:57:7)
    at Object.validate (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-types/lib/definitions/index.js:190:10)
    at validate (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-types/lib/index.js:505:9)
    at Object.builder (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-types/lib/index.js:466:7)
    at bail (/home/computer/project/node_modules/babel-preset-babili/node_modules/babel-plugin-minify-simplify/node_modules/babel-helper-to-multiple-sequence-expressions/lib/index.js:40:21)
    at _loop (/home/computer/project/node_modules/babel-preset-babili/node_modules/babel-plugin-minify-simplify/node_modules/babel-helper-to-multiple-sequence-expressions/lib/index.js:96:16)
    at convert (/home/computer/project/node_modules/babel-preset-babili/node_modules/babel-plugin-minify-simplify/node_modules/babel-helper-to-multiple-sequence-expressions/lib/index.js:102:20)
    at toMultipleSequenceExpressions (/home/computer/project/node_modules/babel-preset-babili/node_modules/babel-plugin-minify-simplify/node_modules/babel-helper-to-multiple-sequence-expressions/lib/index.js:10:17)
    at PluginPass.enter (/home/computer/project/node_modules/babel-preset-babili/node_modules/babel-plugin-minify-simplify/lib/index.js:557:39)
    at newFn (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-traverse/lib/visitors.js:276:21)
    at NodePath._call (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-traverse/lib/path/context.js:76:18)
    at NodePath.call (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-traverse/lib/path/context.js:48:17)
    at NodePath.visit (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-traverse/lib/path/context.js:105:12)
    at TraversalContext.visitQueue (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-traverse/lib/context.js:150:16)
    at TraversalContext.visitSingle (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-traverse/lib/context.js:108:19)
    at TraversalContext.visit (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-traverse/lib/context.js:192:19)
    at Function.traverse.node (/home/computer/project/node_modules/babelify/node_modules/babel-core/node_modules/babel-traverse/lib/index.js:114:17)

I made sure to update babelify in order to have<EMAIL_ADDRESS>

It would be great to get a minimal code snippet since we don't have enough information to reproduce with this

Sure thing, what kind of code snippet would help?

I would reduce /home/computer/project/lib/app/views/components/ArticleHeader.jsx so that it still reproduces the error if that's possible

Yep, let me see if I can do just that. May take a few.

So the offending code seems to be in the render method of that component, where we have:
...some jsx...
{/* eslint-disable react/no-danger */}
...some jsx that uses dangerouslySetInnerHTML...
{/* eslint-disable react/no-danger */}
...some more jsx...

If I remove the blocks with eslint-disable comments, the build completes without issue. Which kind of makes sense considering the error:
Property expressions[0] of SequenceExpression expected node to be of a type ["Expression"] but instead got undefined

As those blocks in the render method have only got comments, and if evaluated as expressions would evaluate to undefined.

If those comments are moved out of the expression blocks, the file seems parseable. Closing, thanks for getting this on the right path, @hzoo!

I think it's still weird - must be a combination of things though since it's fine in the repl

I'm having a problem like that one when I activate the Minify, here the repl
I'm seeing "repl: Unexpected JSXIdentifier. Expected an Identifier", any clue?

@ryanez Probably related to #158

Thanks already looked into that one, and after hours of no success switched to es2015 + uglifyJS


Bootstrap 5 modal {show: true} fail?

Unless I have misunderstood, shouldn't a modal show immediately when instantiated from JS?
var myModal = new bootstrap.Modal(document.getElementById('myModal'), {show: true});
According the docs, {show: true} is default anyway.
https://v5.getbootstrap.com/docs/5.0/components/modal/
Yet the modal does not show unless one triggers myModal.show():
var myModal = new bootstrap.Modal(document.getElementById('exampleModal'), {show:true});
myModal.show(); // <- required
Codepen
https://codepen.io/mjau-mjau/pen/OJNPGYB

Hi @mjau-mjau you're right the behavior changed thanks 👍

This is still the behavior if you instantiate modal using jQuery tho: https://github.com/twbs/bootstrap/blob/a3f27c67e8e3041858e18ac201a384332be14303/js/src/modal.js#L560

The only modal was a component in bootstrap that could be shown automatically when it is constructed. All other components require the show() method to be called on the instance. So to keep the consistency this change is fine IMO even it was not intended (Now modal also require the show() to be called) @Johann-S
So now the updates are required only in the docs and jQueryInterface 🤔


MOB-M-3: iOS Application Caches HTTPS Requests/Responses

Vulnerability Summary
iOS stores application HTTP requests and responses on disk in an unencrypted format by default. These requests may contain sensitive data, such that the user has been diagnosed with Covid-19.
Analysis of the Attack
Blackberry noted that the iOS application does not prevent HTTP requests and responses from being cached.
Requests made using ‘NSURLRequest’ will cache responses in the Cache.db file within the applications container. This cache file is kept unencrypted within the applications container directory on disk. Sensitive HTTP requests made through the application may indicate that the user has been diagnosed with Covid-19.
An adversary would have to compromise the device to retrieve the snapshots. However, there is scope for diagnosis information to be consider personal health information (PHI) and therefore it should be afforded with industry recommended security protections.
Recommendation
• Set the ‘cachePolicy’ property of ‘NSURLRequest’ to disable the caching of HTTP/S requests and responses
• (NSCachedURLResponse)connection:(NSURLConnection)connection
willCacheResponse:(NSCachedURLResponse *)cachedResponse { return nil;
• Follow offical Apple guidance provided at https://developer.apple.com/documentation/foundation/url_loading_system/accessing_cache d_data

Looking to see if there's a React-Native solution for this, or if the solution needs to be iOS specific.
fetch does allow for headers to be set, and can use {cache:'no-store}.

Re-opening since the PR was reverted.

Reopening as this was only fixed in RN.fetch , dropping to lowpri and removing v1launch until we can adequately confirm whether we want to cache the specific data being downloaded, which I believe is only downloaded diagnosis keys currently.
tangent: caching these keys would allow for potential interesting 'multi-jurisdisction exposure checks with different exposureconfiguration elements'.


Add RUST_LOG to .env and help text

RUST_LOG=info,ghp_server=debug
See #79

Might be worth reduce /health feedback, or if there is a way to target remove health logging. Once the basic is setup an running, it is a little noisy.

All endpoint accesses are logged, so we must either

not log /health at all
reduce the ping frequency from health check tools.

It should be fairly easy to filter out these lines from grafana if it's too noisy, but not logging at all feels like overkill.


Having issues passing in strings to sc.login()

I'm having trouble passing in a pair of strings as the username, password combo. I am using variables I read in from a file so I do not have to store the password in the script. A snippet of my code:
sc = SecurityCenter5('fullyqualified.domain.name')
with open('/Users/<username>/security_center_automation/scManager.txt') as f:
	credentials=f.readlines()
	user = (credentials[0])
	passwd = (credentials[1])
	sc.login(user, passwd)

I am getting for an error:

Traceback (most recent call last):
File "/Users//security_center_automation/importAssets.py", line 23, in
sc.login(user, passwd)
File "/Library/Python/2.7/site-packages/securitycenter/sc5.py", line 44, in login
resp = self.post('token', json={'username': user, 'password': passwd})
File "/Library/Python/2.7/site-packages/securitycenter/base.py", line 91, in post
return self._resp_error_check(resp)
File "/Library/Python/2.7/site-packages/securitycenter/sc5.py", line 31, in _resp_error_check
raise APIError(d['error_code'], d['error_msg'])
securitycenter.base.APIError: u'[161]: Invalid login credentials\n'
[Finished in 1.0s with exit code 1]
[shell_cmd: python -u "/Users//security_center_automation/importAssets.py"]
[dir: /Users//security_center_automation]
[path: /usr/bin:/bin:/usr/sbin:/sbin]

Edit: Security Center 5.3.2. And yes these credentials are correct and are of type string

Apologies, I didnt notice that I had a newline at the end of both my username and password. A simple .rstrip() took care of that

Thought I had closed it already


Fix flaky dependency version retrieval

Expected Behavior

Dependency workflow version retrieval should work seamlessly.
Current Behavior

The retrieval step fails every few days with a flake, see #336, and the passes again.
It would be great if we could figure out what the issue is and make that code more resilient so we have less toil associated with dependency workflow failures

This appears to be a common issue across almost all of the repos that retrieve from GitHub. We aren't using an API token when we make the request and so in some cases we get rate-limited.

the second failure mode seems entirely consistent with rate-limiting. The first might be unrelated - just a bad response

I think the first case shows up in instances where we aren't checking the status code, so we don't error on a 403 and then try to unmarshal a JSON response that doesn't match our struct and error out.

Also related: https://github.com/paketo-buildpacks/github-config/issues/653
That issue won't cover buildpack-specific dependency code, but it does cover the same types of failure modes in the common tooling.

Also https://github.com/joshuatcasey/libdependency/pull/25 will fix this issue for buildpacks that use libdependency (e.g. passenger)


feat: add initial transform API

Here is a suggestion of the transform API, it was implemented based on css-transform-1 spec but i noticed that there is a newer version css-transform-2 spec that has some additions/changes.
From the first version of the spec, only the matrix() function is not implemented.
I dispose myself to update the current implementation to css-transform-2 after review of the API status, but would like to know if it is preferable to do it in this PR or create a new one.

Having None inlined with  TransformFunction would permit an API like:
sketch.transform([
  transform.none(),
  transform.rotateX(size.px(2.))
])

IMO an invalid state should not be representable, but it is a tradeoff. Maybe accept it and add documentation can be a workaround.
An alternative suggestion for the API is to expose two functions:
transform: Transform -> Style
transforms: List(Transform) -> Style

But the problem with inlining None would still exists. WDYT?

Hmm, I did not thought about this… What about the empty list of transform functions? Isn't it the case of none?

This can be a valid solution, but IMO transform.list([]) is not transparent/explicit but documentation can fix it, i will implement it this way and we can discuss in the future other solutions

To start, sorry for being missing so long & thanks a lot for your changes! I'd like the subject to advance before I make any change to Sketch in future, because I'm excited to get transform with a better API! 😁
I don't understand why there's so much noise in your patch set. It looks like your repo is not up-to-date with main branch. Could you try an other rebase to see if it removes the noise? Apart from this, one quick remark: there's no more transform function in sketch.gleam. I'd be happy to have transform(String) -> Style and transform_(List(Transform)) -> Style. Maybe with a comment (because it breaks Sketch conventions) "transform will be turned into transform_ in 4.0.0, and vice-versa. Meanwhile, it let you enjoy a better typed API through transform_!"?

Done!

Thanks a lot!


Improve CI pipeline

This PR focus on shortening the CI pipeline runtime and avoiding conflicts writes for the job jars. Specifically:

Upload jars in a shared location for all the spark jobs so that each individual test won't have to upload its own jars
Shorten databricks test run time by using a databricks pool
parallel test runs (currently concurrency is 4)

Could you document the behaviour in dev guide?
For Upload jars in a shared location for all the spark jobs so that each individual test won't have to upload its own jars, what if there are multiple jobs that uploading the jar? What's the behaviour to differenciate them?


[7.x.x] Bump Dependencies #5269132590

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/5269132590

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add GLib.Variant unpacking methods

Hello,
This PR adds the definitions for the unpack methods available to GLib.Variant instances.
Their behaviour is described here:
https://gjs.guide/guides/glib/gvariant.html#unpacking-variants
They are not present in the gir, due to being gjs specific:
https://gitlab.gnome.org/GNOME/gjs/-/blob/1.72.0/modules/core/overrides/GLib.js#L301-313

Merged you PR. Thanks for reviewing and improving the code. Next time I'll try to implement examples for new type definitions.

Perfect, thank you!


Subject mapping transforms for Streams

https://github.com/nats-io/nats-architecture-and-design/issues/201

Completed with https://github.com/nats-io/nats.java/pull/982


editor.renderLineHighlight for all selected lines

VSCode Version: 1.13.1
OS Version: Windows 10 Version 1703 Build 15063.413

Steps to Reproduce:

Open file
Hold ctrl or alt key
Click on lines

How this looks in Sublime Text 3 for instance:

Now in VSCode:

My request is about enable render line highlight to all selected lines (like in Sublime Text 3).

Question: why all, except first, cursors (I mean blink) have different color (in VSCode)?

@Zx-EvM this is a good question, I believe it's only because it's not implemented yet.

@weblancaster I edit my question. In question (after request) I mean blink cursor color (that's looks different).

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!


Update Spanish translation

Cleans up some duplicated msgids for messages changed in patches
8.2.4890 and 8.2.4933.
It seems that make es has wrapped long message strings differently to the
original file.  I can undo that if it's a problem but I don't think it makes
much sense to fight what make and msgmerge generates here.
@victorhck

Thanks, I'll include it.
No idea how to control the line wrapping...


How to use AddTransition in two different TStateId based by enum?

Use an example from the wik.
enum PlayerStates {
    MOVE, JUMP
}

enum MoveStates {
    WALK, DASH
}

enum JumpStates {
    JUMP,FALL
}

enum Events {
    ON_DAMAGE, ON_WIN
}

var fsm = new StateMachine<PlayerStates, Events>();
var moveFsm = new StateMachine<PlayerStates, MoveStates, Events>();
var jumpFsm = new StateMachine<PlayerStates, JumpStates, Events>();

fsm.AddState(PlayerStates.MOVE, moveFsm);
fsm.AddState(PlayerStates.JUMP, jumpFsm);

moveFsm.AddState(MoveStates.WALK);
moveFsm.AddState(MoveStates.DASH);
moveFsm.AddTransition(new Transition<MoveStates>(MoveStates.WALK, MoveStates.DASH));

jumpFsm.AddState(JumpStates.JUMP);
jumpFsm.AddState(JumpStates.FALL);
jumpFsm.AddTransition(new Transition<JumpStates>(JumpStates.JUMP, JumpStates.FALL));

//It will get an error.
moveFsm.AddTransition(MoveStates.DASH,JumpStates.FALL);

I'm new to coding,I only know a compromise that fsm.AddTransition(PlayerStates.MOVE,PlayerStates.JUMP) and then jumpFsm.SetStartState(JumpStates.FALL).

You can't transition from one enum type to another within the same StateMachine. You're trying to transition from a MoveState to a JumpState, but moveFsm was defined as a StateMachine<PlayerStates, MoveStates, Events>, with the second T parameter, MoveStates, showing that moveFsm will only allow transitions between MoveStates. The first T there, PlayerStates, is only applicable if you're nesting the state machines.
See on the line fsm.AddState(PlayerStates.MOVE, moveFsm);
They're adding moveFsm to fsm as a nested state machine. This is possible because moveFsm had  as its first parameter, meaning that you're allowed to nest it under fsm which transitions between PlayerStates.


Add attributes as a name to the v4 blacklist for DSL definitions

Environment

Ubuntu
SitePrism v3.6
Using RSpec and Cucumber

Issue
When defining a new class inheriting from SitePrism::Page which defines a :attributes section, the default helper have_attributes from RSpec gets overwritten.
Steps to reproduce
Here is a RSpec test to showcase the issue:
RSpec.describe "have_attributes" do
  let(:struct) { Struct.new(:a, :b, :c) }

  it "checks that the object has the listed attributes" do
    expect(struct.new(1, 2, 3)).to have_attributes(a: 1, b: 2, c: 3)
  end
end

RSpec.describe "a Page implementing an attributes section" do
  let(:struct) { Struct.new(:a, :b, :c) }

  context "when it is defined" do
    let!(:page) do
      Class.new(SitePrism::Page) do
        section :attributes, '.foo' do
          element :unused_element, '.btn'
        end
      end
    end

    it "breaks `have_attributes`" do
      expect(struct.new(1, 2, 3)).to have_attributes(a: 1, b: 2, c: 3)
    end
  end

  context "after it has been defined once" do
    it "breaks `have_attributes`" do
      expect(struct.new(1, 2, 3)).to have_attributes(a: 1, b: 2, c: 3)
    end
  end
end

The matcher for have_attributes should be: https://relishapp.com/rspec/rspec-expectations/v/3-9/docs/built-in-matchers/have-attributes-matcher.
From what I saw in the docs and in the code, SitePrism::RSpecMatchers seems to define new have_* matchers. Is this still necessary since RSpec already have the have_xxx matcher?

This is an intractable problem and solved by your load order being incorrect.
the RSpec defined matchers allow us to use our metaprogrammed matchers inside RSpecs metaprogrammed assertion logic.
I would look at your stack and see if you can isolate your logic. Or failing that control your load order more succinctly. You are encountering the same issue as anyone else would when overwriting any protected method name

@luke-hill First, thanks for coming back on this and taking the time to look into this! :)
However, I don't think this is a loading issue.
SitePrism can override the default RSpec matcher for have_attributes which breaks tests that have nothing to do with SitePrism. Once the class is loaded, and the matcher setup, it is not possible to go back to the previous behaviour.
I'm not sure why SitePrism defines its own matchers at all since I would expect the have_ default matchers to just work as expected in the current implementation. SitePrism defines has_ methods on the page object and should already plug nicely with RSpec.
Maybe I'm just missing a piece here on why these are necessary... Do you know why that would be?

I'm not going to lie, that area has changed a lot recently. So if you're having problems, I need you to perhaps dig a bit deeper into it as I don't have time at the moment.
If memory serves me right, this was to allow us to do complex matching. and also to add a negative matcher (Which is needed to be custom, as it deviates from RSpecs default ! behaviour).
It seems as though what you're proposing is to remove the positive matcher. Now if this has no adverse effects, and you can reconcile the unit tests / feature tests (I'm aware we have 2 failing ones on old firefox). Then I'm not against some changes being made.
I hope that helps. I'll leave this open for some discussion if needed.

If memory serves me right, this was to allow us to do complex matching. and also to add a negative matcher (Which is needed to be custom, as it deviates from RSpecs default ! behaviour).

Are you speaking of the have_no_* matchers? I know that Capybara has the right behaviour when using negations but I probably would need to crosscheck how that is implemented and if it would work as expected with SitePrism.
Reference:
https://github.com/teamcapybara/capybara/blame/f43b6499ecb2721dd97b63a7fe31ff2518b89b4c/README.md#L805-L811

Any thoughts on this @kouno
At the moment I'm spending a lot of time tackling some internal tech debt around capybara restrictions. Once that is finished I need to cut a stable v1 of the all_there gem. So that's gonna keep me tied up for a while.

@luke-hill I don't think there is much urgency to fix this bug yet so feel free to leave on the side for now.
I'll make a PR when I'm ready and have gotten cucumber tests running locally.

So re-reading this now we have 2 avenues.

Add attributes to the blacklist (We are creating one), that will be released in v4. I personally think it's a very weird name for a section.
Somehow Scope the RSpec matchers. I don't believe this is possible, so #1 looks like the only solution. For v3 we can add a deprecator in. I would probably make it passive (As I plan on cutting v4 soon). So it would be soft-deprecated in v3, and hard deprecated in v4.

I do plan on committing a bit more time to work on this where time allows. I'm also pushing a bit on the funding route now, as I've seen how it can help from other avenues.

@kouno Having spent some time off recently, I've come back to this. I think the best thing is add this to the blacklist. Which whilst masking the issue I think is probably the best one. As it'll also allow us to be stricter with other names we don't want in the blacklist (Such as special characters e.t.c.)

Released in v4.0.beta - Initially disabled as a configurable option
cc/ @kouno


Declare a VM at comptime

it is probably possible to declare a VM and build it at comptime with executor and lookup table

this is a bit "macros-core"


[moor_ffi] Filter for Boolean fields is not properly translated on armeabi-v7a devices

Hello,
Finally, I have found a problem after acquiring armeabi-v7a device (Alcatel 1B) to test weird behavior on these specific devices.
Not sure if this is strictly moor_ffi package issue or dart.
Filters on Boolean fields seem to be not translated to 0/1 integers on armeabi-v7a devices in RELEASE, all other architectures work fine.
Debug works fine, but RELEASE provides errors.
Table:
class MenuTable extends AppTable {
  IntColumn get id => integer().autoIncrement()();
  TextColumn get title => text().nullable()();
  TextColumn get category => text().nullable()();
  BoolColumn get active => boolean().nullable()();
  TextColumn get subtitle => text().nullable()();
  TextColumn get path => text().nullable()();
  TextColumn get object => text().nullable()();
  TextColumn get route => text().nullable()();
  TextColumn get tabs => text().map(const ListConverter()).nullable()();
  TextColumn get data => text().map(const MapConverter()).nullable()();

  @override
  Set<Column> get primaryKey => {id};
}

Snippet:
    final test = await (select(menuTable).get());
    print('all menus: ' + test.length.toString());

    final data = await (select(menuTable)
      ..where((table) => table.active.equals(true))).get();

    print('filtered menus: ' + data.length.toString());

Results (armeabi-v7a -> RELEASE):
I/flutter ( 7153): all menus: 140
I/flutter ( 7153): filtered menus: 0

Results (armeabi-v7a -> DEBUG, or any other architectures (i.e. arm64-v8a)):
I/flutter ( 7153): all menus: 140
I/flutter ( 7153): filtered menus: 137

The database:

Doctor:
[√] Flutter (Channel stable, v1.17.5, on Microsoft Windows [Version 10.0.18363.900], locale en-US)
    • Flutter version 1.17.5 at e:\SDK\flutter
    • Framework revision 8af6b2f038 (18 hours ago), 2020-06-30 12:53:55 -0700
    • Engine revision ee76268252
    • Dart version 2.8.4

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\mariu\AppData\Local\Android\sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code, 64-bit edition (version 1.46.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.12.0

[√] Connected device (1 available)
    • 5002D EEA • e89e0665 • android-arm • Android 10 (API 29)

• No issues found!

This is a bug in the Dart compiler (https://github.com/flutter/flutter/issues/54948). We bind booleans as 64-bit ints. For those, Flutter apps built on Windows mistakenly switch the upper and lower 32 bits when targeting armv7 devices. So when we want to write true = 0x1, we actually write 0x1 0000 0000, which causes the error.
I'll close this as a duplicate of #446. It should work when you build your app on another OS or use a non-stable Flutter channel. If that still doesn't work, please comment on the Flutter issue to share your setup.


Do not sleep in tests

Change time.Sleep to busy waiting for bundle to complete.

Tests on Windows fails due to race. It looks like this whole code is buggy. At first I thought only Running and Errors may be problematic but other filed are also updated (Status). I need to figure out how to fix it. Probably the best option is to extract state from DiagnosticJob and allow it's modification via synchronized methods or channels.
@klueska @philipnrmn  What do you think?

I run this tests 100 times on Linux and could not reproduce the problem
TRIES=100
COMMAND="GOCACHE=off go test ./api -race "
n=0
until [ $n -ge $TRIES ]
do
  eval ${COMMAND} || break
  n=$[$n+1]
done

Trigger windows tests


fix ReferenceError: pref_custom is not defined

I often meet this error on Firefox. Try to fix it

Thanks! Let me finish the code off.

As it turned out, a typo caused the issue. The bug should have been fixed. Thanks for your work.


orocos_kinematics_dynamics: 1.3.0-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository orocos_kinematics_dynamics to 1.3.0-0:

upstream repository: https://github.com/orocos/orocos_kinematics_dynamics.git
release repository: https://github.com/smits/orocos-kdl-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.5.21
previous version for package: null

No doc entry?

Copying jade: https://github.com/ros/rosdistro/blob/master/jade/distribution.yaml#L3288 I assume @smits chose this for a reason.
@smits FYI here's the kinetic release of orocos_kinematics_dynamics

Indigo has a doc entry so the other distros should have too.


Render Govspeak Synchronously for HtmlAttachments

Currently, the Govspeak on an HtmlAttachment is rendered within a Sidekiq worker some time ~10 seconds after the attachment has been saved (here). We need it before then when sending the HtmlAttachment to the Publishing API.
This PR calls #render_govspeak! within the constructor of the PublishingApiPresenters::HtmlAttachment to ensure that we have the HTML when the payload is sent. The presenter is instantiated within a Sidekiq worker so any performance issues are still mitigated and nothing will be blocked should there be a particularly large body.
This effectively makes the GovspeakContentWorker redundant as any changes to the HtmlAttachment will be sent to the Publishing API and the HTML will be generated. The original reason for the delayed queue should no longer be an issue as the events that cause the Publishing API update are fired after the parent Edition is committed to the DB. My only concern is that this step will now be 'hidden' within the presenter where it is much less obvious/explicit than it currently is. I'll remove the GovspeakContentWorker in a subsequent PR unless anybody has any better ideas.
This is part of the ongoing work for trello

👍


There's a problem with the MDC component that makes it too heavy and ruins your website's performance (blocking resource)

I don't know what is the exact problem but there's something wrong for sure because it doesn't happens with the nuxt/content module.
 WARN                                                                                20:26:55
(!) Some chunks are larger than 500 kBs after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.

Not sure, what exactly causes this, but #93 (with nuxt/content#2422) might be related?

I have found the same issue. The MDC script is over 60% in size of the client bundle and seems to render client side. Which makes little to no sense to me.

I'm not sure if this is related, but I just opened an issue concerning the remark-emoji dependency, which is quite heavy #187
And I agree that is a bit weird that this is client-side.

I have managed to write a composable that uses MDC to render an HTML object and then returns this as a string. This renders server side and in my test repo, i have seen a block time decrease from 1270ms to just 420ms on mobile (Lighthouse).
Im pretty sure it can be written more effeciently, but it does the job!
Here's the composable:
https://github.com/Sfolkerts89/Nuxt3-starter__Decap-cms/blob/main/composables/mdToHtml.js
And here is the component i use to mount/ render:
https://github.com/Sfolkerts89/Nuxt3-starter__Decap-cms/blob/main/components/misc/ParseMarkdown.vue

I have managed to write a composable that uses MDC to render an HTML object and then returns this as a string. This renders server side and in my test repo, i have seen a block time decrease from 1270ms to just 420ms on mobile (Lighthouse).
Im pretty sure it can be written more effeciently, but it does the job!
EDIT:
It still seems to bundle the MDC script, but the performance is already major
Here's the composable:
https://github.com/Sfolkerts89/Nuxt3-starter__Decap-cms/blob/main/composables/mdToHtml.js
And here is the component i use to mount/ render:
https://github.com/Sfolkerts89/Nuxt3-starter__Decap-cms/blob/main/components/misc/ParseMarkdown.vue


ViewModel and Iron Router problems

Are there known incompatibility issues with iron:router? I'm having errors everywhere using it with viewmodel.

I use it all the time with IR...
On Jun 28, 2015 10:52 PM, "santiagopuentep"<EMAIL_ADDRESS>wrote:

Are there known incompatibility issues with iron:router? I'm having errors
everywhere using it with viewmodel.
—
Reply to this email directly or view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/71.

Here's an example of one of the problems.
If I comment the #if statement in the template the back button is visible. If I uncomment it it's not. Very strange. The onBackClick handler doesn't work, but in certain cases (with the more complex app) it does, sometimes it doesn't. All these problems started with iron router installed.
This is the code:
I have this template:
<template name="desk">
    // comment this #if and the data-bind stops/starts working
	{{#if currentUser}}
	    back
    {{/if}}
</template>

With this viewmodel:
Template['desk'].viewmodel(
    function (data) {
	    return {
	    	isNotInRoot: false,
    		onBackClick: function (e) {
    			e.preventDefault();
    			console.log('back clicked!');
			}
		}
	},
	['root']
);

And this router:
Router.configure({
    layoutTemplate: 'layout',
    waitOn: function () {
        	Meteor.subscribe('items');
    }
});

Router.route('item', function () {
		this.render('desk');
	},
	{
		path: '/:_id',
	}
);

Check out the faq on the board site...
On Jun 28, 2015 11:22 PM, "santiagopuentep"<EMAIL_ADDRESS>wrote:

Here's an example of one of the problems.
If I comment the #if statement in the template the back button is visible.
If I uncomment it it's not. Very strange. The onBackClick handler doesn't
work, but in certain cases (with the more complex app) it does, sometimes
it doesn't. All these problems started with iron router installed.
This is the code:
I have this template:

With this viewmodel:
Template['desk'].viewmodel(
function (data) {
return {
isNotInRoot: false,
onBackClick: function (e) {
e.preventDefault();
console.log('back clicked!');
}
}
},
['root']
);
And this router:
Router.configure({
layoutTemplate: 'layout',
waitOn: function () {
Meteor.subscribe('items');
}
});
Router.route('item', function () {
this.render('desk');
},
{
path: '/:_id',
}
);
—
Reply to this email directly or view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/71#issuecomment-116438630
.

Sorry, board site?

Found it: http://viewmodelboard.meteor.com/posts/rrpagb6DnciFQde8J
Thanks! Problem one fixed.

I'm still having problems with this. I was using IronRouter and I changed to FlowRouter but the problem is the same, one part of my template is in a #with statement that renders an item template and doesn't get re-rendered when the data context changes (root helper). This is the code:
<template name="desk">
	back

		{{#with root}}
			{{> item}}
		{{/with}}

</template>

Template['desk'].viewmodel(
	function (data) {
		return {
			root: function() {
				var item;

				var itemId = FlowRouter.getParam("_id");
				if (itemId) {
					item = ItemsList.findOne(itemId);
				}

				return item;
			},
			onBackClick: function (e) {
				e.preventDefault();

				var itemId = FlowRouter.getParam("_id");;

				if (itemId) {
					// finds an id to other item (the parent of the current one)
					var parent = ItemsList.findOne({children: itemId});
				}

				if (parent) {
					FlowRouter.go('/' + parent._id);
				} else {
					FlowRouter.go('/');
				}
			}
		}
	},
	['root']
);

FlowRouter.route('/', {
	subscriptions: function (params, queryparams) {
		this.register('items', Meteor.subscribe('items'));
	},
	action: function (params, queryparams) {
		FlowLayout.render('layout');
	}
});

FlowRouter.route('/:_id', {
	subscriptions: function (params, queryParams) {
		this.register('items', Meteor.subscribe('items'));
	},
	action: function (params, queryParams) {
		FlowLayout.render('layout');
	}
});

When I press the back button FlowRouter.go() is called, the root helper is called but the template inside the #with statement doesn't change.


[2d81c] Update kustomization images

This Pull request aims to update the kustomization images

@r00ta sooooo.. this will deploy my MC_xxx change to dev now?


giphy images

Closes #https://github.com/carbon-design-system/carbon-website/issues/3961
Adding the GifPlayer component on gifs
Changelog
Changed

Screenshots or recreation for static images of the gifs that need this component.

Reviewing this testing environment. Not ready for design/dev review yet


[Feature Request] Support multiple LLMs using litellm

Hi Team,
Not sure if you can support different LLMs in your app?
https://github.com/BerriAI/litellm
Thanks.

I'm the maintainer of LiteLLM - will make a PR

@SanderVUMC https://github.com/yoheinakajima/instagraph/pull/53


Adding a chatbot

🚀 Feature
The ChatBot will provide the user- information about different types of music and will also provide them with resources to learn music.

@niloysikdar I am still training the chatbot. May I get 1 day more?

Try to complete it asap @namratadas1


Feature request: use llama_index to read pdf, md, docx, epub, ppt and so on

Please add support for various text file readers as in llama-index.

i added support for pdf


【NOTIFICATION】 STOP UPDATING TEMPORARILY 暂停更新通知

Dear RemixIcon users,
Thank you for all your love of Remixicon. We've received much feedback and praise in the past years. And many users expressed their recognition of our efforts by donations. It really means a lot to us.
But we are very sorry to say that we have to suspend the update of RemixIcon for several months.
I‘ve just changed my job a month ago and came to a team full of passion. I was getting so busy with my work in the past month and I will be busy too in the future about months. I love my new job and the stuff I am working on which took most of my spare time and almost all energy.
As you know, in order to ensure the quality of each icon, in the past period of time, almost all the icons were drawn by myself in my spare time. Besides, a lot of things should be done for updating the website and GitHub repo. Over the past period, RemixIcon has maintained an average of 6 weekly updates. But this time, I have to make the decision to suspend the update of RemixIcon.
You can still submit new icon requests and suggestions for improvement by issues and I will deal with these issues in my spare time as soon as I can. Don't worry, our official website will always on serve in the future.
We are also planning the next big version of RemixIcon, most of the part is to optimize the update process.
Thank you again for your love of our work.
Best regards, Jimmy.

亲爱的小伙伴们，
非常感谢你们对 RemixIcon 的支持和喜爱。过去一年里，RemixIcon 在没有经过正儿八经宣传的情况下，用户量呈现了指数上升，许多设计师和开发者将 RemixIcon 推荐给了自己的同事和朋友。RemixIcon 的官网也在大家的建议下新增了很多实用的图标和功能。还有非常多的小伙伴通过打赏的方式表达对我们工作的认可和感激，虽然大部分都是海外用户，但在国内「你懂的」的免费产品环境下能收到这么多的支持，我和小伙伴真的非常感动，让我们一次又一次充满干劲。
但是，我们不得不通知大家，RemixIcon 在未来的小几个月里将会暂停内容更新。
原因是我前段时间刚刚换了工作，新的团队充满了激情，大家虽然工作时间都超饱和但每个人都很拼。而我也非常喜欢现在做的事，几乎每天都加班到很晚，大部分空闲时间和激情都投入到了工作当中，难以抽出更多的时间（主要是精力）去完善图标库的更新工作。每天晚上回到家稍微放松下（羞耻得打两把王者荣耀）就跑去睡觉了，也更加珍惜周末的时光，会陪陪家人，有时加加班，还有准备工作考试等内容。
不少小伙伴都知道，为了保证图标质量，之前的 2000 多枚图标都是我业余时间一人绘制完成的，除了绘制图标，每次更新我还需要做矢量导出、代码清洗、生成字体、写更新日志、添加搜索关键词、完成网站构建、同步更新 Github 等一系列的工作。过去小两年里，我们也一直保持着大概平均一个半月一次的更新频率，不过这一次我不得不决定暂停内容的更新，原谅我的任性和逃避。
但是大家不要担心，官网将会持续为大家提供免费服务，而且大家依然可以通过 issue 等方式提新的图标请求或者改进建议，我们会尽快逐步完成大家的图标请求和功能改进建议。
目前我们也正在计划下一个大版本的更新，尤其是内容更新流程的改进，顺利的话，以后的更新频率会更加平滑平稳，而不是像过去这样，攒一段时间才集中更新。
再次感谢大家的支持和热爱，尤其是曾经通过建议、功能探讨和打赏等途径支持过我们的人，还有不少小伙伴用 RemixIcon 制作了第三方的 Figma、React、Vue 组件或插件，帮助我们将这一产品体不算完善，让我们觉得「开源」真好！
别急，我们消失一段时间就回来~

Sad and happy feeling. Hope we will get more minimalist and clear icons same as now in the future too.😊

感谢作者！真的很谢谢你！祝你顺利

反正我也不是图花样多，慢慢更新吧

加油，顺便发个自制的2.5.0版本Auxre元件库，下载地址，提取码：pvv8

@xiaochunjimmy
We hope so you will start to work on a new update as soon as possible. We are very excited about the upcoming release.

感谢作者的制作，请务必注意身体w

求分享下figma链接哈哈哈

感谢作者

这个库真的好棒!大佬加油!

@xiaochunjimmy thanks for your effort to make this available for free and open-source, very much appreciate.
Can you please make a brief checklist/guideline for those who want to add their own icons that are compatible with Remix Icon for the time being? For example if I need an icon that is not in RI yet, I would like to make a temporary version of the icon, make a PR and hope that when time permits you can review/edit the icon and accept it?

UEDART & Remix 联合打造全系列图标库
目前支持sketch、Axure、XD等常见的设计软件使用
访问网址
http://uedart.com/remix.html

感谢作者的无私奉献，身体是革命的根本，热爱/享受生活，才能更好的工作！

时隔一年才后知后觉的得知暂停更新的消息。可以毫不夸张的说，这是所有我使用过的图标库顶流！作者加油！早日复更！若开发出Pro版，开启知识付费模式。我会支持你的。

感谢作者❤

虽然还没有用上，但是感受到你的认真和才华，感谢你的贡献，我的朋友，微信为你支持了5rmb，加油！！！

Hello, first of all a big thank you for this superb library! I see that the suspension dates from 2020, has there been any news from the author since?

I'm also looking forward to the update. @xiaochunjimmy project has been on pause for over a year. Could you please share your plans to keep us more engaged in this project? We'd like to hear some sound from you.

Hello, first of all a big thank you for this superb library! I see that the suspension dates from 2020, has there been any news from the author since?

@ga-devfront @iamrishishah
Sorry we disappeared for so long.
We've experienced a lot in the past period of time, which consume a lot of energy and makes it difficult for us to balance our works, life and side project.
Anyway we're back now and are designing the next version (although planned for a long time and intermittently). The core purpose of the next version is to reduce the release process witch would make our future releases smoother and less burdensome. With a simpler release process, we could avoid long periods of not updating.

🙏 感谢贡献，祝大佬生10个胖小子。

@ga-devfront @iamrishishah Sorry we disappeared for so long.
We've experienced a lot in the past period of time, which consume a lot of energy and makes it difficult for us to balance our works, life and side project.
Anyway we're back now and are designing the next version (although planned for a long time and intermittently). The core purpose of the next version is to reduce the release process witch would make our future releases smoother and less burdensome. With a simpler release process, we could avoid long periods of not updating.

@xiaochunjimmy Is there a specific date or month for the next big release?

使用 RemixICON 制作了一个 Axure 元件库，感谢作者设计了这么多精美图标。
说明链接：https://www.y3pm.com/post/remix_icon_2.5/
下载链接: https://pan.baidu.com/s/10mhzpV-BgDGXgg_T-DIj8w?pwd=Y3PM 提取码: Y3PM

这个库永远停更了吗？

 Today is April Fool's Day, but I am not fooling 😋

铁子们，RemixIcon 终于恢复更新了，今天是愚人节，但我是认真的 😋； Hey boys, RemixIcon has finally resumed updates. Today is April Fool's Day, but I am not fooling 😋

回来啦，谢谢大佬的付出！！！

@ga-devfront @iamrishishah Sorry we disappeared for so long.
We've experienced a lot in the past period of time, which consume a lot of energy and makes it difficult for us to balance our works, life and side project.
Anyway we're back now and are designing the next version (although planned for a long time and intermittently). The core purpose of the next version is to reduce the release process witch would make our future releases smoother and less burdensome. With a simpler release process, we could avoid long periods of not updating.

@xiaochunjimmy Is there a specific date or month for the next big release?

Remix Icon is Back with V3.0.0 on April Fool's Day. No fooling, we rolling. 😜

哇哦，他回来了，呱唧呱唧

Y3PM

你好，能不能补一个网盘链接呀？


Release 2.5.2

Hello folks,
Thanks for the bundle, it seems really useful!
I wanted to try it but encountered an issue with random_compat 9.99. I saw the commit https://github.com/nelmio/NelmioSecurityBundle/commit/fdd8a68f8eabe04cafab7ae30d1667d81d01f292 fixed it. Is a 2.5.2 release possible so that I can install the bundle in stable :) ?
Thanks by advance!

2.6.0 has been released


Translate specifics/ets.md page to Portuguese - issue #123

ets.md page translated to Portugues.
@pragmaticivan review please

@psantos10 just updated with some changes. Thanks you so much! o/

By the way, I wrote a post in Portuguese about Open Source Contribution<EMAIL_ADDRESS>

@pragmaticivan I am done with this, I think. You can merge.

@psantos10 please squash the commits

@pragmaticivan Done!

Thanks @psantos10 ! o/


Avellenada reservation price is frequently slow to update

Describe the bug
Avellenada bot often falls into a state where it fails to update the Reservation Price on a highly liquid kucoin pair. This results in a series of rapid, sequential buys or sells all within a tight price range when the midprice moves away from the Reservation Price.
Restarting the bot refreshes the reservation price.
This may be related to (or perhaps identical) to the behavior where it frequently takes 5-10 minutes for the bot to begin trading after it's finished filling its buffers.
Steps To Reproduce
Trade a liquid pair, such as LUNA-USDT on kucoin and monitor Reservation price using "status --live". After some period of time, the reservation price will stop being recalculated.
The bug is somewhat intermittent (but occurs several times a day).

t3.micro instance (EC2) - upgraded because CPU was constantly at 100%. This is still the case.
Docker

Screenshots
Example: currently sitting at 100% inventory. The MidPrice has dropped steadily yet the Reservation Price is still unchanged and sitting well above. This causes buy orders to be placed right at the spread.

Release version

Development branch - dev-1.0.0

Attachments
logs_conf_avellaneda_market_making_1.log
conf_avellaneda_market_making_1.zip
Discord: optiontrader1138

I've chased this down a bit more and found that the problem lies in trading_intensity.pyx. It appears that alpha is updated frequently but it sometimes takes many ticks for kappa to be non-zero.
This occurs both at startup as well as during trading. The latter is quite serious as the reservation price is not updated when kappa is 0, so a price move frequently results in either the bid or ask getting hit in rapid succession as the reservation price drifts further away from the mid price.
This line of code may be related but I cannot find any documentation on this indicator.
            params = curve_fit(lambda t, a, b: a*np.exp(-b*t),                                price_levels,                                lambdas_adj,                                p0=(self._alpha, self._kappa),                                method='dogbox',                                bounds=([0, 0], [np.inf, np.inf]))


Fixed crash if discogs servers respond with html

Hey there,
Thanks for writing disconnect. It's very useful and elegantly built.
I did run into a problem when Discogs went into maintenance mode which was causing my app to crash every time it got a response from the server.
I looked into it and it's because you were running JSON.parse() on html.
My change is a simple amendment to the if statement after the server response to make sure it's not an html page.
Cheers and thanks again for this awesome module!

You're welcome :) Just out of curiosity (Discogs downtime was at night in my timezone), what kind of HTML did the Discogs API return during downtime? I would have expected an empty response or some generic json formatted message with matching HTTP headers...

I didn't check the HTTP response directly myself or read the full response (before their servers came up), but what I got was the beginning of an html doc...I am guessing a 404 page? I've encountered this with PayPal's API before when they're having technical problems.
Here's the fragment thrown by Node's exception:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/

Ah ok, thanks for checking. Probably just the load balancer sending a generic html 404 page. Thanks for the notification and fix. A new release with this fix + some other minor things has been published.


Support for container layers >500MB

Cloudflare / R2 would be the best choice for hosting large (30GB+) AI/ML container images for serverless inference (RunPod, Modal, etc.), because R2 is fast (ECR is painfully slow), and 30GB container pulls will rapidly grow bandwidth bills.
But a 500MB layer size limit is a significant handicap.
The best solution I see is to implement the necessary multipart upload process via a container push feature in Cloudflare Wrangler.

Can you see if the following issue thread  https://github.com/cloudflare/serverless-registry/issues/42#issuecomment-2366997382 or https://github.com/cloudflare/serverless-registry/tree/main/push works for you?

I will be closing this down. Please re-open if any of the alternatives do not work for you!