Using SOM and deep learning to predict credit card frauds.

Credit card frauds are quite common lately, this is a small contribution from my side in this direction to create a SOM which protects users from credit card frauds even with minimal data.

Hi @mmujtabah I am currently working on this can you assign this issue to be under the hacktoberfest accepted label?
Thanks.

@Rohit-Sharma-RS I appreciate your idea. By adding this challenge to the repository, will it be a friendly challenge for beginners?
Will Neural Networks and Self-Organizing Maps be an easy challenge for beginners who are new in programming?

Hi @alizaincodes
No this might not be a beginner friendly project unless there is some understanding of machine learning(especially K Means clustering algorithm) and at least basic knowledge on artificial neural networks.

The dataset has around 1000 rows planning to train them over 50-70 epochs

Hi @alizaincodes No this might not be a beginner friendly project unless there is some understanding of machine learning(especially K Means clustering algorithm) and at least basic knowledge on artificial neural networks.

We could introduce separate sections for beginners and advanced users, placing this project in the advanced section. That way, those with foundational knowledge can still explore and contribute at their own pace.
Great idea, by the way! I’ll definitely look forward to contributing as soon as I find some free time.

@mmujtabah This would be nice as users have to go to their respective folders(beginner or advanced). This will make it easy to find and categorize challenges.

@mmujtabah This would be nice as users have to go to their respective folders(beginner or advanced). This will make it easy to find and categorize challenges.

Absolutely! Feel free to add an advanced section after all, it’s an open-source repo, and every contribution counts. Your efforts will definitely make it more organized and easier for users to find relevant challenges.

The project was added please review it.
I created a separate advanced section to add the project into.


Javascript console error if Message data is a string

The sanitize method will throw an error if a Message event data  is a string.
Specifically it looks like when you use the webpack dev server in development this happens when a hot deploy occurs. I assume this is how webpack informs the browser what has changed.
postmate.js?2a8e:80 Uncaught TypeError: Cannot use 'in' operator to search for 'postmate' in webpackHotUpdateb6875338fa40f73def8f
    at sanitize (postmate.js?2a8e:80)
    at reply (postmate.js?2a8e:322)

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/in_operator_no_object

Actually looking at the current source it looks like this error has been fixed but it has not reached NPM yet.
Any chance on a release?

Resolved in #141


Added device file for Multi Leaf DY-107 Thermostat

First of all, thank you for your hard work!
I created a config file for a thermostat which is from Tuya...
Other names I found are:
Lupum Dy-107
Wholesale Dy-107
Avatto Dy-107
More information about product:
https://www.electricvalvefactory.com/product/thermostat/dy107-floor-heating-thermostat.html

DPs according this HowTo:
https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html#_8-find-your-data-point
Datapoints:
{"1":"Switch","2":"Mode","10":"Frost protection","16":"Set temperature","19":"Set temperature ceiling","24":"Current temperature","26":"The lower limit of temperature","27":"Temperature correction","30":"Weekly procedure (working day)","31":"Working day setting","36":"State of the valve","39":"Factory data reset","40":"Child lock","43":"Sensor selection","44":"Backlight brightness","45":"Fault alarm"}

Base data used for the implementation:
{
  "result": {
    "properties": [
      {
        "code": "switch",
        "custom_name": "",
        "dp_id": 1,
        "time":<PHONE_NUMBER>644,
        "value": true
      },
      {
        "code": "mode",
        "custom_name": "",
        "dp_id": 2,
        "time":<PHONE_NUMBER>710,
        "value": "manual"
      },
      {
        "code": "frost",
        "custom_name": "",
        "dp_id": 10,
        "time":<PHONE_NUMBER>285,
        "value": true
      },
      {
        "code": "temp_set",
        "custom_name": "",
        "dp_id": 16,
        "time":<PHONE_NUMBER>787,
        "value": 15
      },
      {
        "code": "upper_temp",
        "custom_name": "",
        "dp_id": 19,
        "time":<PHONE_NUMBER>785,
        "value": 40
      },
      {
        "code": "temp_current",
        "custom_name": "",
        "dp_id": 24,
        "time":<PHONE_NUMBER>183,
        "value": 19
      },
      {
        "code": "lower_temp",
        "custom_name": "",
        "dp_id": 26,
        "time":<PHONE_NUMBER>779,
        "value": 10
      },
      {
        "code": "temp_correction",
        "custom_name": "",
        "dp_id": 27,
        "time":<PHONE_NUMBER>276,
        "value": -5
      },
      {
        "code": "week_program3",
        "custom_name": "",
        "dp_id": 30,
        "time":<PHONE_NUMBER>159,
        "value": "BgAAFAgAAA8LHgAPDB4ADxEAABYWAAAPCAAAFhcAAA8="
      },
      {
        "code": "work_days",
        "custom_name": "",
        "dp_id": 31,
        "time":<PHONE_NUMBER>370,
        "value": "5_2"
      },
      {
        "code": "valve_state",
        "custom_name": "",
        "dp_id": 36,
        "time":<PHONE_NUMBER>208,
        "value": "close"
      },
      {
        "code": "factory_reset",
        "custom_name": "",
        "dp_id": 39,
        "time":<PHONE_NUMBER>869,
        "value": false
      },
      {
        "code": "child_lock",
        "custom_name": "",
        "dp_id": 40,
        "time":<PHONE_NUMBER>372,
        "value": false
      },
      {
        "code": "sensor_choose",
        "custom_name": "",
        "dp_id": 43,
        "time":<PHONE_NUMBER>864,
        "value": "in"
      },
      {
        "code": "backlight",
        "custom_name": "",
        "dp_id": 44,
        "time":<PHONE_NUMBER>778,
        "value": 3
      },
      {
        "code": "fault",
        "custom_name": "",
        "dp_id": 45,
        "time":<PHONE_NUMBER>278,
        "value": 0
      }
    ]
  },
  "success": true,
  "t":<PHONE_NUMBER>858,
  "tid": "5d809cefdc7011eeb8e44adb5c011a40"
}

Screenshot of UI:

          - dps_val: null
            value_redirect: alt

?
I Just copied one of the existing device files as a template and adjusted it with the Datapoints I posted above.
Works for me...

The value_redirect: alt that you copied is for handling two slightly different devices from the same config.  You should remove those two lines from the mapping, since you do not have an alt dp to redirect to, and this config is only for one device.


Feature Request: Support DENSEL to switch high density mode on F1

For the F1 version, I want to be able to support high density drives such that I am able to arbitrarily switch the density mode using DENSEL (PB9 on F1, Pin 2 on the drive connector).
Looking at the firmware code, PB9 is not addressed at all. So I was wondering what the default state of that Pin is.
Reasoning: My only remaining DD floppy drive broke, so I have to go on using HD drives reading DD disks now. So far I was unable to read any data from them, so I was wondering if the DENSEL output is by default setting (PB9 state) at HD mode instead of DD.
Could this please be implemented and a switch in the hosttools be provided?
Thanks,
Clark

Plenty of drives don't accept density select on pin 2. Leaving it to be explicitly set, as currently, is fine.


dotnet tool install stopped working on Ubuntu 20.04 version 20220619.1

Description
I have an Azure Pipelines system on the ubuntu-latest image that used to work reliably. With the latest image I now get this error consistently:
/opt/hostedtoolcache/dotnet/dotnet tool install --global GitVersion.Tool --version 5.5.0
error NU3028: Package 'GitVersion.Tool 5.5.0' from source 'https://api.nuget.org/v3/index.json': The repository primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain
error NU3037: Package 'GitVersion.Tool 5.5.0' from source 'https://api.nuget.org/v3/index.json': The repository primary signature validity period has expired.
The tool package could not be restored.

This is on version 3.1.420 of the .NET Core SDK. The identical command works on the windows-latest image, and it worked in the 20220529.1 image.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions

Virtual environments affected

[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Version: 20220529.1
Build link: here
Is it regression?
Yes. Worked on 20220529.1
Expected behavior
Tool installs.
Actual behavior
No install.
Repro steps
Set up .NET Core SDK 3.1.x, then this Azure Pipelines YAML:
      - task: DotNetCoreCLI@2
        displayName: 'Install GitVersion'
        inputs:
          command: 'custom'
          custom: 'tool'
          arguments: 'install --global GitVersion.Tool --version 5.5.0'

@pkgw, Is it possible to update Use .Net task version? After I have bumped .dotnet version to the latest one a build starts working for me.
Use .NET Core sdk 3.x

Use .NET Core sdk 5.x

Unfortunately I don't believe that we're able to upgrade the SDK right now.
If I update the version of GitVersion.Tool to 5.10.3, that specific error goes away, but then I get many more similar errors deeper in the build process. E.g.:
2022-06-23T17:15:49.4485198Z ##[error]src/WWT.PlateFiles/WWT.PlateFiles.csproj(0,0): Error NU3028: Package 'NETStandard.Library 2.0.3' from source 'https://api.nuget.org/v3/index.json': The repository primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain
2022-06-23T17:15:49.4579035Z /home/vsts/work/1/s/src/WWT.PlateFiles/WWT.PlateFiles.csproj : error NU3028: Package 'NETStandard.Library 2.0.3' from source 'https://api.nuget.org/v3/index.json': The repository primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain [/home/vsts/work/1/s/wwt-website-net5.slnf]
2022-06-23T17:15:49.4584465Z ##[error]src/WWT.PlateFiles/WWT.PlateFiles.csproj(0,0): Error NU3028: Package 'System.Runtime.CompilerServices.Unsafe 4.5.3' from source 'https://api.nuget.org/v3/index.json': The author primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain
2022-06-23T17:15:49.4587275Z /home/vsts/work/1/s/src/WWT.PlateFiles/WWT.PlateFiles.csproj : error NU3028: Package 'System.Runtime.CompilerServices.Unsafe 4.5.3' from source 'https://api.nuget.org/v3/index.json': The author primary signature's timestamp found a chain building issue: UntrustedRoot: self signed certificate in certificate chain [/home/vsts/work/1/s/wwt-website-net5.slnf]
2022-06-23T17:15:49.4606022Z ##[error]src/WWT.PlateFiles/WWT.PlateFiles.csproj(0,0): Error NU3037: Package 'System.Runtime.CompilerServices.Unsafe 4.5.3' from source 'https://api.nuget.org/v3/index.json': The author primary signature validity period has expired.
2022-06-23T17:15:49.4608865Z /home/vsts/work/1/s/src/WWT.PlateFiles/WWT.PlateFiles.csproj : error NU3037: Package 'System.Runtime.CompilerServices.Unsafe 4.5.3' from source 'https://api.nuget.org/v3/index.json': The author primary signature validity period has expired. [/home/vsts/work/1/s/wwt-website-net5.slnf]

But it is curious to me that bumping the version fixed the GitVersion.Tool problem. Do I have to update many/most/all of my dependencies to pick up newer packages with updated signatures, or something?

@pkgw, Could we bump .Net 3.x and 5.x versions just for test?

I have created a fork for the https://github.com/WorldWideTelescope/wwt-website repo and updated the global.json config to:
{
  "sdk": {
    "version": "5.0.408",
    "rollForward": "feature"
  }
}

I do not understand why, but your change indeed fixes my problem! Thank you! I will close this, although I would love to understand what is going on here.

I'd also like to know what resolved this issue.
@dtivel

Looks like - https://github.com/NuGet/Home/issues/10491#issuecomment-827161752

I agree that it looks like that. @dvitel and I worked on that issue. It shouldn't affect the .NET versions being used. That's a surprise to us.


Fix date to string conversion

This fixes #39 and also related https://github.com/paulhodel/jexcel/issues/1031.

Thanks ;)


Fixes #4277

Fixes #4277.

Pull Request Test Coverage Report for Build 1705

0 of 13 (0.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.175%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

shardingsphere-sql-parser/shardingsphere-sql-parser-mysql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/MySQLVisitor.java
0
2
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-postgresql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/PostgreSQLVisitor.java
0
2
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-postgresql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/impl/PostgreSQLDDLVisitor.java
0
4
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-postgresql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/impl/PostgreSQLDCLVisitor.java
0
5
0.0%

Totals

Change from base Build 836:
0.0%

Covered Lines:
11026

Relevant Lines:
17453

💛  - Coveralls

Codecov Report

Merging #4279 into master will not change coverage.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #4279   +/-   ##
=========================================
  Coverage     59.37%   59.37%
  Complexity      352      352
=========================================
  Files          1016     1016
  Lines         17453    17453
  Branches       3112     3112
=========================================
  Hits          10362    10362
  Misses         6438     6438
  Partials        653      653

Impacted Files
Coverage Δ
Complexity Δ

...ngsphere/sql/parser/visitor/PostgreSQLVisitor.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...hardingsphere/sql/parser/visitor/MySQLVisitor.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../sql/parser/visitor/impl/PostgreSQLDDLVisitor.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../sql/parser/visitor/impl/PostgreSQLDCLVisitor.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

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 f10a097...68fa13e. Read the comment docs.


Remove automatic setting of binary media types header

The binaryMediaTypes property of the 'Api' resource of the RestAPI component would get overriden because of a default applied to an amazon header: "x-amazon-apigateway-binary-media-types": ["*/*"].
This PR gets rid of it and adds a regression test, as well as upgrade tests in order to make sure we don't replace any resources in the process.
See comment here: https://github.com/pulumi/pulumi-aws-apigateway/issues/118#issuecomment-1850035758
Fixes: #118

Is this not going to break anyone who's currently expecting the binary media types to be set automatically?

No because we're setting it here by default: https://github.com/pulumi/pulumi-aws-apigateway/blob/main/provider/cmd/pulumi-resource-aws-apigateway/apigateway/api.ts#L661 But this one <- was being overwritten by the swagger body if you updated the routes array.

Yup, I verified it here: https://github.com/pulumi/pulumi-aws-apigateway/actions/runs/7247196392/job/19740649953 and then restored the fix in the next commit.

Note that users who previously specified binaryMediaTypes would get replacements after upgrading to this change.
This is probably fine since the resource wouldn't have worked correctly for them before and the resources are stateless.


Altcoins Update

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@Thegillie This article had been flagged as plagiarism.


error running the visual studio project

Error creating skillset: Invalid URI: The hostname could not be parsed.

Hi hinda00,
Were you able to resolve this problem?  I have never seen this issue myself when running the code from exactly what is given on github, so it could be because you made some customizations that caused it to break?  Did you ensure that the ARM template deployment was a complete success (with no failed resources) before running the JfkInitializer?
If neither of the above are the case, I would recommend deleting your resource group and trying again, making sure to follow the instructions exactly as they are to produce the expected results, as it could just be a transient issue that you saw.
-Carey MacDonald

I am having the same issue. When I dig into it, it looks like the credentials for the function app do not allow access. I am getting a 401 error. I got around it for the time being by pasting the url into the browser and hard-coding the json into the app.

Closing as this seems to have been resolved and has not had discussion in several months.


o11y: add Prometheus metric for scaledObject condition array

Proposal
The scaledObject object has a condition attribute that shows an array of conditions the object has passed through. An example:
status:
  conditions:
  - message: ScaledObject is defined correctly and is ready for scaling
    reason: ScaledObjectReady
    status: "True"
    type: Ready
  - message: Scaling is performed because triggers are active
    reason: ScalerActive
    status: "True"
    type: Active
  - message: No fallbacks are active on this scaled object
    reason: NoFallbackFound
    status: "False"
    type: Fallback

I would like to add a Prometheus metric for this which in the core is very similar to the HPA condition metric kube_horizontalpodautoscaler_status_condition (here).
What do you guys think? I am happy to pick this one up when it receives positive feedback from the community.
Use-Case
Show health of scaledObjects and alerting
Anything else?
No response

That's OK for me, @zroubalik @JorTurFer?

Agree

I like this idea as well.

Let's do it @erikkn! Thanks for picking it up.


Set guess_sample_buffer_bytes and preview_sample_buffer_bytes from Embulk System Properties

Rivisits #1379 and #1414.
#1414 was once reverted in #1449 because of the constructor parameters of FileInputRunner from Ruby.
This pull request includes a fix for that case in file_input_plugin.rb, which is available because it is after the Guice removal.

Thanks!


Any colored hydra fails due to authentication error.

Might be neovim regression and/or breaking change, see https://neovim.io/doc/user/news.html:
LUA
API functions now consistently return an empty dictionary as [vim.empty_dict()](https://neovim.io/doc/user/lua.html#vim.empty_dict()). Earlier, a [lua-special-tbl](https://neovim.io/doc/user/lua.html#lua-special-tbl) was sometimes used.

Minimal reproduction inspired by gitsigns bug tracker:
for name, url in pairs{
  hydralink = 'https://github.com/nvimtools/hydra.nvim',
} do
  local install_path = vim.fn.fnamemodify('hydra_issue/'..name, ':p')
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
  vim.opt.runtimepath:append(install_path)
end

local Hydra = require('hydra')

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE

Hydra {
  name = 'Side scroll',
  config = {
    color = 'pink', -- without color pink it works
    -- invoke_on_body = true, -- does not matter if inside or not.
  },
  mode = 'n',
  body = 'z',
  heads = {
    { 'h', '5zh' },
    { 'l', '5zl', { desc = '←/→' } },
    { 'H', 'zH' },
    { 'L', 'zL', { desc = 'half screen ←/→' } },
  },
}

Error:
Fehler beim Ausführen von "/home/misterspoon/dev/try/trylua/minhydra.lua":
E5113: Error while calling lua chunk: vim/shared.lua:0: s: expected string, got number (1)
stack traceback:
        [C]: in function 'error'
        vim/shared.lua: in function 'validate'
        vim/shared.lua: in function 'startswith'
        vim/_init_packages.lua: in function '__index'
        vim/shared.lua: in function 'islist'
        vim/shared.lua: in function ''
        vim/shared.lua: in function 'tbl_deep_extend'
        ...y/trylua/hydra_issue/hydralink//lua/hydra/layer/init.lua:116: in function 'initialize'
        ...ry/trylua/hydra_issue/hydralink//lua/hydra/lib/class.lua:14: in function 'Layer'
        ...dev/try/trylua/hydra_issue/hydralink//lua/hydra/init.lua:440: in function '_setup_pink_hydra'
        ...dev/try/trylua/hydra_issue/hydralink//lua/hydra/init.lua:282: in function 'initialize'
        ...ry/trylua/hydra_issue/hydralink//lua/hydra/lib/class.lua:14: in function 'Hydra'
        /home/misterspoon/dev/try/trylua/minhydra.lua:15: in main chunk

Please provide the version of neovim you are running.
This smells like nightly, in which case, see #47  for details on why we aren't addressing these issues yet.

I have edited the issue text to include the version information and yes, that is on nightly.

Thanks :) Ya for the time being we are not addressing nightly issues. At least not until the vim.table work is stabilized.

I haven't looked at nightly in a bit, but unfortunately the answer currently is "don't use nightly" or "don't use hydra".
We will not be maintaining multiple branches of this plugin, so until vim.table stabilizes (something that probably wont happen until the next stable release), IMO we are best off just waiting.


4 ether scan links

This is a sorta big PR, so I recommend reviewing each commit. I tried to make them easy to follow.
I created a new slice to manage "action" transations, which can be mint, claim or burn to target.
The slice also manages errors.
The addTransaction saga will first add the transaction hash to state, the ui can then show the etherscan link.
Then it will wait for the transaction to finish using snxJSConnector.utils.waitForTransaction.
If everything went well it will call fetchDelegateWalletInfoRequest
If there's an error that will also be handled.
I made it so you can do multiple transactions just like you can in mintr.
This should solve #2, #4 and #5. But it was a little hard to test, would love some help with that.

Elipsis for long links:

Thanks for the feedback, all fixed!


Bring ABC size for RuboCop down to 17

This change addresses a number of offenses to bring the ABC size down to 17, mostly through the extraction of named methods and classes. There is still potential for improvement in some of the offense locations, which we can revisit if we attempt 17 to 16.

Before submitting the PR make sure the following are checked:

[X] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[X] Feature branch is up-to-date with master (if not - rebase it).
[X] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[X] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[X] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

Nice work! 🙇


An introduction to last branch records

https://lwn.net/Articles/680985/

from the spec, vol3, chapter 17

信息源筛选

https://mobaxterm.mobatek.net/plugins.html

ZSH_THEME="ys"

1WOTgIBz25oV


Move "KFServing" to "Components"

We should ensure all core Kubeflow components live directly under the Components section.
Currently, "KFServing" lives underComponents / Tools for Serving (along with many other docs for serving tools which are not part of Kubeflow).
I think we should move it directly under Components, otherwise it sends some mixed messages about what is officially part of Kubeflow.

@RFMVasconcelos what are your thoughts?

/cc @kubeflow/wg-serving-leads

Thank you @thesuperzapper for starting this. I fully agree! KFServing is a great tool by the community and should have more emphasis!
Happy to make a PR

I highly doubt there would be any conflict from others if you made a PR.
Also, I think we should split up the components, as proposed in https://github.com/kubeflow/website/issues/2536

Sounds good! I'll give it a go

The PR for this has been merged! 🎉
/close


Kibana Opendistro + AWS Elasticsearch (with access policy)

Hi,
I'm trying to connect Kibana Opendistro with AWS Elasticsearch service, but my AWS ES has an access policy that allows an IAM Role.
It's possible to use in Kibana the AWS credentials or the token role to get access to ES ?
For example for Logstash there is a plugin https://github.com/awslabs/logstash-output-amazon_es

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).
If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.
Thanks!


project title update:  include ruby and gem?

currently the project title is just:
   Loads environment variables from `.env`.

After hitting a few repos (and issuing the wrong one) with nearly identical titles - perhaps something like:
  Ruby gem to load environment variables from `.env`

might be nicer?
(I'd PR it, but you can't PR that part to my knowledge...)

If you are searching in GitHub then there is a "language" badge for most repositories.

Thanks for the suggestion. The description has been updated.


no margin and padding

it's good libarary but it does not have padding and margin classes .

Second that. Will be useful


feat: Make it possible to have a shared env var for srvice and tap

fixes #335

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

6 of 7 (85.71%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 70.546%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

config/src/config.rs
6
7
85.71%

Files with Coverage Reduction
New Missed Lines
%

common/src/tap/checks/deny_list_check.rs
1
98.21%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.02%

Covered Lines:
4558

Relevant Lines:
6461

💛  - Coveralls


Ready-to-use IDE based on containers and VSIX

/cc @carlosedp @mithro @cmarqu @mgielda @PiotrZierhoffer @kgugala @qarlosalberto @smgl9 @Nic30 @pepijndevos @drom @cavearr @juanmard @olofk @gojimmypi @ghuntley @mickaelistria @trabucayre @Paebbels
A tweet from @carlosedp (https://twitter.com/carlosedp/status/1432708143067377665) triggered some interesting dialogues about IDEs and supporting easy integration with EDA tool(chains).
This is a compendium of ideas as a result of those dialogues, in the hope that we can find synergies and slowly bring isolated projects together.
Introduction to the Electronic Design Automation (EDA) industry
Some participants are familiar with containers and IDEs, but not with the specifics of EDA tooling. Let this be a rough introduction:
Hardware is inherently parallel. Unlike software (read von Neumann paradigm), there is no central unit orchestrating/serialising the execution. Some authors use the terms "computing in time" and "computing in space", to make it explicit that hardware designs have a physical 2D/3D layout, below the "program/application logic". As a result, there is an unavoidable friction between text based design workflows and GUI/block/diagram based workflows.
Hardware was designed almost exclusively by drawings until the late 80s, mid 90s. There was almost no distinction between ASICs (chips) and PCBs (boards) with regard to the user input. Then, so-called Hardware Description Languages (HDL) stepped in. HDLs are in fact software programming languages, with certain patterns that some specific compilers (named synthesis tools) can use for inferring (say guessing) the corresponding hardware blocks. In parallel to HDLs, devices named FPGAs were invented. FPGAs sit between an Application Specific Integrated Circuit (ASIC) and a CPU (software programmable). FPGAs are configurable (programmable at the hardware level) and also programmable at the software level.
NOTE: Verilog is based on C. VHDL is based on Ada. The fact that both VHDL and (System) Verilog can be compiled to executable binaries through LLVM/GCC as if they were C/Ada has further implications, but let's keep those aside.
At first, FPGAs were used for prototyping ASICs only. However, nowadays FPGAs are found in products, as much as CPUs or ASICs. So, HDLs are "the programming languages of FPGAs" and there is a whole industry of "module" designers in the "IP core" subset of the EDA market. As a result, modern workflows for designing chips are becoming closer to mainstream software development practices, almost overlapping. However, the EDA industry is ~20 years behind the software industry, and the hardware/software developer ratio is somewhere around 1/10. There is so much to learn, so much work to do, but few human resources (in comparison to software projects). This GitHub organisation and the multiple projects mentioned below are distributed efforts to bring the "hardware designer" experience closer to "software development".
There are four main challenges for building an open source EDA IDE:

Lack of maturity of most projects. Open Source started stepping into hardware in the early-mid 2000s, it started to really kick-off in the early 2010s, and it's rocketing to the stars in the last 5 years. So many monoliths were built in the last decade. Now it's time to polish them, take the best, package them, and reuse them in integrated solutions. That's more of a communication / community building challenge, than a technical one. The knowledge is there, we need to be able to put it together.

Dependency on GUI tools. HDL designers need waveform visualisation for debugging. ASIC designers need 2D/3D layout viewers. PCB design is almost exclusively GUI based. Unlike software development, visualising graphs/diagrams is necesary for hardware development, not optional.

Size of the tools. While most simulation / early development / verification tools are very lightweight, implementation is astonishingly heavy. Vendor IDEs require 10-50GB. Part of that is useless stuff, but a significant portion corresponds to the databases of the FPGA devices or the PDK in case of ASICs.

Connection to the boards. Similarly to writing firmware for embedded microcontrollers, testing FPGA designs requires programming the boards at some point.

Similarly to "IP cores" at the FPGA/HDL level, reusable modules exist at the ASIC level. Those are named "chiplets". In fact, Google is pushing hard towards an open source hands-free HDL to chiplet solution. Tim @mithro is the visible lead of those efforts, under the umbrella of SymbiFlow, and in tight collaboration with Antmicro, efabless, SkyWater, etc. Some of the repositories in this organisation are precisely maintained by people from either Google or Antmicro (see bazel and conda repos).
Packaging and distribution
In the context of this issue, we will set the scope to all-in-one containers, as the ones maintained in this repository.
That is, a single container image containing all the tools/dependencies expected to be used by an IDE.
That is not desirable for CI purposes (that's why fine-grained images are provided as well), however, it's the most reasonable for newcomers, students, etc.
We don't care about how are the container images built, as long as the EDA tools are available in the PATH. It's ok to use the all-in-one containers from this repo, or any other. In other words, we will not address the lack of maturity with regard to how are tools built and installed. That's to be discussed in hdl/packages.
Local execution
x11docker/runx
When containers are executed locally, either through docker or podman, x11docker and runx can be used for starting an X server and sharing it with the container.
That allows running GUI tools without installing any additional software in the container images.
That is showcased in the UG of this repo: https://hdl.github.io/containers/ug/index.html#_tools_with_gui.
x11docker works on GNU/Linux hosts, and also on Windows (through runx).
GTK3 Broadway
GTK3 has a built-in HTML "frontend" named Broadway (see https://developer.gnome.org/gtk3/stable/gtk-broadway.html). Hence, tools which use the GTK3 toolkit can be accessed through a web browser. That does not require any modification to the container images, apart from starting the broadway server (see https://github.com/ghdl/docker/blob/master/broadway.sh).
See, for instance, GTKWave in image ghdl/ext:broadway.
IIRC the future of Broadway in GTK4 is uncertain.
VSCode Docker extension
Microsoft's VSCode's Docker Extension provides some interesting features for starting containers (optionally using x11docker): microsoft/vscode-docker#1496. It's been a while since I last had time to tinker with that. Nevertheless, I've always had very good communication and feedback from the maintainers of the extension. I was very gratefully surprised by how responsive and proactive they were.
VSCode and Remote - Containers or Remote - WSL
I don't find the Remote - Containers and Remote - WSL appealing, mostly because AFAIAA they contain non open source pieces. On the one hand, the HyperV version provides easier resource management. On the other hand, by configuring the Docker Extension tasks, I don't find need to start VSCode instances inside the container.
Nevertheless, I do sometimes use the Remote - Containers feature on Windows. Since Microsoft refuses to support MSYS2 in VSCode, all git features are broken. Running VSCode attached to a container fixes that, because it's on a GNU/Linux environment, so git works. However, credentials need to be shared, which is cumbersome.
Overall, Remote - Containers and Remote - WSL are the most similar local experience to the solution provided by Gitpod or Eclipse Che.
USB boards
As explained in https://hdl.github.io/containers/ug/index.html#_usbip_protocol_support_for_docker_desktop, programming boards through USB from containers is not straightforward. On GNU/Linux, the devices can be shared; however, on Windows containers run on a Virtual Machine which does not support access to arbitrary USB devices. USB/IP allows working around that limitation by using a TCP/IP port. Yet, we are lacking an open source implementation of USB/IP on Windows.
Extensions
There are multiple extensions for VSCode related to HDL|EDA already: https://github.com/dbhi/vsc-hdl#references.
@ghuntley mentioned an open source VSIX extension marketplace gifted to the Eclipse Foundation by Gitpod/TypeFox (https://twitter.com/GeoffreyHuntley/status/1433035049524346887): https://open-vsx.org/. It would be interesting to have HDL|EDA related extensions published there.
Probably the most complete open source extension is TerosHDL. TerosHDL wraps some of the most used VHDL and Verilog projects, such as cocotb, VUnit, GHDL, wavedrom, VHDL formatter, Yosys... It is sensible to join forces around TerosHDL. As a matter of fact, a previous version of TerosHDL was based on Atom, instead of VSCode (see https://www.youtube.com/watch?v=_wxTjOSO5oY). apio-ide was a similar approach, unfortunately unmaintained before being mature.
Sigasi does have several features similar to TerosHDL and it is now provided as a VSCode extension as well. However, it's not open source.
Diagrams
GHDL and/or Yosys allow generating diagrams of synthesisable HDL sources (see https://umarcor.github.io/osvb/apis/project/DocGen.html#diagrams). In fact, TerosHDL uses some of those features already.
It also allows generating dependency tree diagrams.
Sigasi provides a similar solution in the XPRT tier: https://insights.sigasi.com/manual/views/#block-diagram-view. Yet, that is not open source.
On the other hand, there is no mature project for web technology based block-diagram input yet, but there are some interesting proofs of concept:

d3-hwschematic
logidrom
Icestudio: FPGAwars, juanmard
SymbiFlow/ideas#41

It would be interesting to evaluate whether any of those can be used as a VSCode extension.
There are some other nice projects not based on web technologies: https://umarcor.github.io/hwstudio/doc/#_references.
I'm not experienced on the analog and ASIC side of "drawings". I know @pepijndevos is working on NyanCAD, which uses web technologies as a frontend (see NyanCAD/Mosaic). I believe that Mosaic might be provided as a VSIX extension.
Waveforms
The most used web technology based waveform viewer is probably wavedrom (see also zoom and vcdrom). In fact, there is a VSCode extension: https://marketplace.visualstudio.com/items?itemName=bmpenuelas.waveform-render.
However, there are other solutions:

d3-wave
fliplot

impulse.vscode is particularly interesting, but it's not open source.
A common limitation of most waveform visualisation projects based on web technologies is that waveform formats other than VCD are typically not supported. As explained in https://umarcor.github.io/osvb/apis/logging.html#waveforms, VCD cannot handle certain types from the VHDL language.
Gitpod
Gitpod can be particularly useful in learning/teaching environments, as it allows easy to setup workspaces which are ready-to-use by unexperienced users (see https://www.gitpod.io/blog/workshops-as-code). It is mostly based on creating a container, having a repository cloned in it and attaching a web editor using VSCode or Theia.
Since everything is executed remotely, using GUI tools is apparently limited. The most straightforward solution seems to be gitpod/workspace-full-vnc, which is based on gitpod/workspace-full, which is based on gitpod/workspace-base... That is used in cocotb and umarcor/SIEAV.
On the one hand, @ghuntley suggested not to use the gitpod/workspace* images, but to build our own (see https://twitter.com/GeoffreyHuntley/status/1433083202705387525). That is sensible indeed. However, since there is so much content in the workspace-base, workspace-full and workspace-full-vnc images/layers, it's not straightforward to guess which are actual dependencies and which optional/convenient features. I'm thinking about Apache2, NGINX, PHP, Homebrew, Go, etc. In Custom Docker Image, steps to customise an image are explained, but there is no explicit reference to dependencies. Are there no dependencies at all? That is, is Gitpod expected to work on a debian:bullseye-slim (as the VSCode attach feature)?
On the other hand, in order to use GUI tools, alternatives to VNC might be evaluated. Precisely, x11docker provides several solutions, either local or remote. Among those, xpra might be the most interesting to test in Gitpod. By running the xpra client on the host, users can have "native" windows, while still using the in-browser and remote VSCode/Theia frontend of Gitpod.
It would be interesting to test GTK's broadway as well. However, that's more of a fancy test, rather than usable for most HDL/EDA tools.
Overall, in the context of this repository, it would be interesting to have a debian-bullseye/gitpod.dockerfile, which we could use on top of any of the existing images in collection debian/bullseye. That should be relatively straightforward, once we clarify the minimal requirements and the best approach for a good user experience when using GTKWave, KLayout, etc.
Eclipse Che
When I tried Che some years ago, I think it was still independent from Theia. Compared to Gitpod and in analogy to docker, Che felt like creating stacks of containers through compose, while Gitpod is for running a single container. It felt to me that the strength of Che was user management, groups, permissions, access to shared projects, etc. In fact, it is now advertised as "The Kubernetes-Native IDE for Developer Teams". portainer.io provides some overlapping features in that regard. As a result, a Che instance is not lightweight and it requires some good knowledge in order to deploy and (mostly) maintain. While I see the value within organisations/companies, it was/is out of my scope because I don't have the infrastructure for running it as a service.
On the other hand, the architecture of Che feels to be a better fit for using fine-grained containers. Instead of having all the tools/dependencies in a single image, Che allows/expects the container running the editor to be different from the ones doing the heavy work. That fits nicely with the conception of a toolkit/API than can execute commands either locally or in sibling containers. Therefore, in the mid term it might make sense to find synergies between Che and the distributed runner aspect of https://umarcor.github.io/osvb/apis/tool.html.
OpenAPI
There is work-in-progress in edaa-org for defining a set of abstraction models, which might then be wrapped in an OpenAPI (see https://umarcor.github.io/hwstudio/doc/#_structure). That would allow reusing the tool management backends regardless of the frontend. As a proof of concept, https://github.com/umarcor/hwstudio showcases how to host a web frontend in GitHub Pages, and use it with a Python backend executed locally.
In fact, having an API that allows a remote frontend to communicate with a local backend is a requirement in order to program the boards. Gitpod and/or Che can be used for simulation, synthesis, implementation, etc. but they cannot program the bitstreams into the boards by themselves, because they are connected to the user's computer. There are three possible solutions:

There is some experimental support in Google Chrome for accessing USB devices from the browser. That is used in https://beta.webfpga.io/dashboard. It might be possible to write an VSIX extension that works for some boards, as long as Gitpod/Che are executed on Chrome.
Using USB/IP, as commented above.
A (EDAA based) custom backend which implements the OpenAPI and has local access to the board.

Note that some vendors (such as Xilinx) provide a "Hardware manager" (named Vivado Lab Solutions) as a "compact, and standalone" package that users can install on their workstations with multiple FPGA boards to use them remotely. Overall, we should head towards providing an equivalent solution for open source boards/workflows, probably based on openFPGALoader.
As soon as we can support programming boards from Gitpod/Che, we should provide those options in fomu-workshop.

@umarcor thank you, really nice introduction. In the Waveforms section I think that you could add vcdrom (https://github.com/wavedrom/vcdrom), the new waveform viewer of @drom
It looks really nice! https://github.com/wavedrom/vcd-samples
We plan to integrate it in TerosHDL.

@qarlosalberto it's mentioned, indeed:

The most used web technology based waveform viewer is probably wavedrom (see also zoom and vcdrom). In fact, there is a VSCode extension: https://marketplace.visualstudio.com/items?itemName=bmpenuelas.waveform-render.

However, I added it after sending the initial message, so it maybe it was not shown in your e-mail/notification.


Update stable version in repo from 0.0.0 to 0.1.5

Think about adding version 0.1.5 to stable repository.
Version: stable=0.0.0 (0 days old) => latest=0.1.5 (30 days old)
Installs: stable=0 (0%), latest=158 (95.18%), total=166
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 0.1.5 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

Is there any reason to delay updating stable any longer?
Please drop a commit if you know any reason to refrain from updating.
If there is no response until 6.6.2024 we could decide to add anyway.

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 0.1.5 but the current stable version is already 0.1.5.
So this issue should be closed.
@mcm1957 for evidence


Bug: id is undefined in the response when posting a quote

bugreport
Hi @oanhgle,
Thanks for making this project, I'm going to use it for a school assigment. I found a bug when posting a quote, the "id" in the response is undefined.  I added screenshot below.

Keep going nice work 💜

Thanks for reporting! Issue has been fixed in d256791


[WIP] Fix closure issue when using transaction blocks

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #17288
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Closing this.
Will send a separate to the 1.0.x branch with all the fixes.


Option for not hiding player details when player has no offer

I like to have all the player details always visible. So an option for not hiding player details when player has no offer would be awesome.

Doublet of #39


Get rust-crypto to build after io changes in nightly.

Thanks! I think you missed one final instance where io needs to be replaced with old_id in the fortuna tests. I'll make that change in a subsequent PR.


Set up conversation flow in API

The whatsapp controller will be the 1 central point where all whatsapp messages will be routed to.
A whatsapp request comes through FormCollection (name/value pairs) and is of the following format, TwimlResponse should be returned (as application/xml) and will be the message that the sender gets back
MediaContentType0:image/jpeg
SmsMessageSid:MM<redacted>
SmsSid:MM<redacted>
SmsStatus:received
To:whatsapp%3A%2B<redacted>
MessageSid:MM<redacted>
AccountSid:AC<redacted>
From:whatsapp%3A%2B<redacted>
ApiVersion:2010-04-01
NumMedia:1
Body:Hello from Arcus API
MediaUrl0:https%3A%2F%2Fapi.twilio.com%2F2010-04-01%2F.<redacted>

The following parameters are 'image/photo'-related: MediaContentType0, NumMedia and MediaUrl0, where the properties ending with 0 are incremented when having multiple images in a message.
The entire conversation flow (that should ideally be done and implemented by a bot, but might be easier to implement through interface/dependency injection and classes, just using hardcoded classes and gradually replacing throughout the weekend?) should look like this:

When phone number is new, and for the first time, we should welcome and ask for name

Incoming message: First hello message:
Initial state: In this message, the user (by phone number) will normally not be known (to be checked on every incoming request).
Final state: Before returning, the number should be stored and the state of the conversation should be set to awaiting_name
Return message: Welkom bij deze app, wat is uw naam, aub?

When the phone number is already saved, we should expect that the incoming message is the name of the user, conversation state should be 'awaiting_name'

Incoming message: Firstname Lastname
Initial state: In this message, the user (by phone number) will normally be available in the user store.
Business logic: Validate the message to check and verify that it is a name (optional: NLP to extract name from statements like 'Ik ben Sam', 'Mijn naam is Jos'...)
Final state: Before returning, the name should be added to the UserStore together with the phonenumber and the state of the conversation should be set to awaiting_activation
Return message: Welkom, {username}, als je een client wil connecteren, gelieve dan de activatiecode te sturen

When the user is already saved, and the conversation state is 'awaiting_activation', we should expect the user wants to link to a specific tenant

Incoming message: {activationcode}
Initial state: In this message, the user (name + phone number) will normally be available in the user store.
Business logic:

Validate the message to check and verify that it is an activation code (optional: NLP to extract the code from statements like 'De code is XXX'...)
Check if the activation code belongs to a tenant already.  If the code belongs to a tenant, link the user to the tenant in the UserStore
If the tenant was not yet activated, set the state to be activated so that the tv-app will get images as from then.

Final state: Before returning, the user should be linked to the tenant and the tenant should be activated.  The state of the conversation should be set to complete
Return message:

In case the tenant was activated for the first time: Dank je wel, de TV app is klaar om foto's en berichten te ontvangen
In case the tenant has already been activated: Dank je wel, je mag foto's en berichten sturen naar de app nu

When the user is known and is already linked to a saved tenant, the message should be parsed and data should be stored in the right tenant store

Incoming message: regular whatsapp message
Initial state: In this message, the user (name + phone number) will be linked to a tenant that is activated.
Business logic:

Already implemented: parse message for media or text messages.  Save message and or images in the right tenant store.

Final state: Before returning, the message content should be saved
Return message:

In case of a message: Dank je, jouw bericht werd doorgestuurd
In case of an image: Dank je wil, we hebben jouw foto opgeslagen in de app
In case of multiple images: Dank je wil, we hebben jouw {fotocount} foto's opgeslagen in de app

Thanks for Specs, ideally all of this is done sync I guess?

I have created some harness code (parsing of whatsapp message and empty logic): pushed to branch admin-chat-conversation - you can start from there
and yes: sync, I'd say for now

conversation flow implemented - the actual service implementations obviously still have to happen (tenant store, user store, media service providers...)


Merge pull request #129 from Bonface-Osoro/main

Merge pull request #128 from Bonface-Osoro/emissions

done

final changes


Add neutral mutations to the simulation using a rate map

I need to add the neutral mutations with a rate map.
This will speed up the computations.
I need to see if these mutations can be labeled.

See this note from Aaron on how to do this,


Chef cookbook sets Embedded to false, as a default.

It might be handy for new adopters of the Sensu cookbook that  /etc/default/sensu  sets the embedded variable to false by default (matching the standard rpm default).
Side subject:  Do most people using Sensu manage their own ruby install, or just use the omnibus version?  Would be interesting if there's data around that.
Created pull request with this small documentation change:  https://github.com/sensu/sensu-chef/pull/334

I like the embedded ruby. This allows us to have three rubys without conflicts.

sensu ruby
chef ruby
system ruby

@runningman84 @xyntrix the danger is that if you install sensu gems for the embedded, you could break sensu from running itself if I'm correct.

Given that Sensu 0.21 now defaults EMBEDDED_RUBY to true, I think this cookbook default attribute needs to change as well. We'll consider this for a future enhancement.

+1 for embedded ruby to default of true for the reasons outlined above regarding ruby namespacing. Additionally as pointed out about the change as of 0.21 the cookbook should mirror the sensu defaults and recommended configuration.

:+1: for true
I'm torn on whether or not this merits a major version bump. On the one hand, by flipping that we're maintaining the default behavior of the sensu package (e.g. non-breaking in terms of intent), on the other hand, we're switching the cookbook behavior.
Having written that out, I'm leaning towards major bump. Other thoughts?

definitely understand the conflict, I would however say that it does merit a major version bump to prevent it from breaking existing installs.

yes, major bump please :warning:

:+1:


GetCredentials if matched the host name

This PR will be imported into Gerrit with the title and first
comment (this text) used to generate the subject and body of
the Gerrit change.
Please ensure you adhere to every item in this list.
More info can be found at https://github.com/golang/go/wiki/CommitMessage

The PR title is formatted as follows: net/http: frob the quux before blarfing

The package name goes before the colon
The part after the colon uses the verb tense + phrase that completes the blank in,
"This change modifies Go to ___________"
Lowercase verb after the colon
No trailing period
Keep the title as short as possible. ideally under 76 characters or shorter

No Markdown
The first PR comment (this one) is wrapped at 76 characters, unless it's
really needed (ASCII art, table, or long link)
If there is a corresponding issue, add either Fixes #1234 or Updates #1234
(the latter if this is not a complete fix) to this comment
If referring to a repo other than golang/go you can use the
owner/repo#issue_number syntax: Fixes golang/tools#1234
We do not use Signed-off-by lines in Go. Please don't add them.
Our Gerrit server & GitHub bots enforce CLA compliance instead.
Delete these instructions once you have read and applied them

I see the proposal https://github.com/golang/go/issues/50649 was posted and retracted, so I'm going to close the PR. Thanks!

Closing.


[SPARK-15569] Reduce frequency of updateBytesWritten function in Disk…

What changes were proposed in this pull request?
Profiling a Spark job spilling large amount of intermediate data we found that significant portion of time is being spent in DiskObjectWriter.updateBytesWritten function. Looking at the code, we see that the function is being called too frequently to update the number of bytes written to disk. We should reduce the frequency to avoid this.
How was this patch tested?
Tested by running the job on cluster and saw 20% CPU gain  by this change.

Can one of the admins verify this patch?

Jenkins add to whitelist

Jenkins test this please

Test build #59409 has started for PR 13332 at commit 454e6b6.

Test build #59409 has finished for PR 13332 at commit 454e6b6.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59409/
Test FAILed.

Some test cases need to be updated.

fixed the tests.

Test build #59462 has started for PR 13332 at commit 5169e36.

Test build #59462 has finished for PR 13332 at commit 5169e36.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59462/
Test FAILed.

Jenkins retest this please

Test build #59492 has started for PR 13332 at commit 5169e36.

Test build #59492 has finished for PR 13332 at commit 5169e36.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59492/
Test PASSed.

OK, looks good. Merging into master 2.0


cherry-pick to V4.9: Storage: fix snapshot resources

Storage: fix snapshot resources
Restore status complete and snapshot status readyToUse are not enough to determine that the restore/snapshot are done. Added a function that takes the VM status in consideration as well

Short description:
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

!cherry-pick v4.8

!cherry-pick v4.8


Support for UWP

Hi,
I tried using the library with UWP app as I wanted to create an Universal app to run on my raspberry pi board but it is failing to install through Nuget. Any possibilities for this?
Any help would be highly appreciated.
Thanks,
Pooja

It might be possible, but there are some challenges, the first one is getting the native TensorFlow library to compile under UWP, if you can get that compiled, then we can move on to the next stage which would be to try this out.
In the meantime, you could try TensorFlow + Raspberri on Linux


Ignore unranked players in ladder "trend" icon

Took a very quick look at this one, chucked it in the too hard basket

Hahah yeah the code is a bit of a sty - and still not entirely sure it's the unranked players that are causing it (or if it's even an issue anymore tbh)


Lambda Function CreateLogStream Fails with ResourceAlreadyExistsException, Causing Infinite Trigger Loop in Instance Scheduler v3.0.0

Describe the bug
A Lambda function, instance-scheduler-dev-schedulingRequestHandlerLam, is repeatedly failing with the error message:
"errorCode": "ResourceAlreadyExistsException",
"errorMessage": "The specified log stream already exists"

This issue began late Friday evening, causing the Lambda function to be triggered infinitely, with each execution failing with the same error.
To Reproduce

Deploy Instance Scheduler v3.0.0 in the ap-southeast-2 region.
Monitor the Lambda function instance-scheduler-dev-schedulingRequestHandlerLam.
Observe the CloudTrail logs to see multiple CreateLogStream calls by instance-scheduler-dev-schedulingRequestHandlerLam. Check the details of these logs, and you will see the error indicating that the log stream already exists.

Expected behavior
The Lambda function should create a new log stream or write to an existing one without errors, and it should not enter an infinite loop of execution.
Please complete the following information about the solution:

[x] Version: v3.0.0
[x] Region: ap-southeast-2
[ ] Was the solution modified from the version published on this repository? No
[ ] If the answer to the previous question was yes, are the changes available on GitHub? N/A
[x] Have you checked your service quotas for the services this solution uses? Yes
[x] Were there any errors in the CloudWatch Logs? Yes
Troubleshooting

Screenshots
N/A
Additional context
The issue was not present immediately after upgrading to v3.0.0. It started occurring approximately 25 days later, suggesting that it may be related to a change or update on the AWS side. We have not made any modifications to the solution since upgrading.

Thanks for reporting this issue! Has this error been ongoing for multiple days or just one day? the log stream used by scheduling logic is supposed to be recreated every day with the logic checking if the stream already exists.
Also, is this error causing the lambda to fail, or are you just seeing the warning in cloud trail but not observing any impact to the solution itself? Within the logging code used by instance scheduler (https://github.com/aws-solutions/instance-scheduler-on-aws/blob/main/source/app/instance_scheduler/util/logger.py#L160-L165) there is an intentional write that is expected to raise a resource-already-exists exception as part of the normal flow of solution logging.

Thanks for getting back.
We noticed this error on late Friday. When I reviewed the logs from a few days prior, I noticed the same error was being triggered every few seconds.
I don't think this error is impacting the solution but got a bit concerned looking at the number of cloud trail events.
I've attached a screenshot showing the number of error events captured in CloudTrail.


Release 1.5.0

Please approve the release of 1.5.0

Coverage: 31.517% (+0.006%) from 31.511% when pulling adc9514b2224619ddf6cadc577d608eadf11025a on release_1.5.0 into ae916ca4937e2a92fbd295e66d0fdf3134cb26b3 on master.

Was just a demo of the release - closing


TitleElement.Title not works for ToggleButton

Describe the bug
TitleElement.Title not works for ToggleButton.
Environment (please complete the following information):

.net: .net 5
IDE vs2019
Version <IP_ADDRESS>

Hi @GF-Huang
This Attached Property is only available on some controls Unfortunately, toggle button is not one of them
@NaBian , will this feature be added to this control in the future?

@ghost1372 no, only for some input elements


Make it easier to build debug or release variants

Description
The make tooling right now just builds debug versions of stuff, and making a release version requires a bunch of manual steps.  Would be great to support both debug and release variants "easily".

See also: discussion of LTO in #131


Alphabetize process list

@nnpcYvIVl : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


woocommerce_product_gallery_attachment_ids filter used in src/Hyyan/WPI/Media.php is deprecated

PHP Notice:  The woocommerce_product_gallery_attachment_ids filter is deprecated since version 2.7! Use woocommerce_product_get_gallery_image_ids instead.

Solved

it just kills me, if you solved, why not to share it with other webmasters?))


Support for WKWebView Engine with http server

Problem
I've been doing some tests to see if it is possible to replace the Telerik WkWebview with the official WkWebviewEngine w/local webserver.
For all of our other plugins, this works well. The change enables us to run the latest Cordova iOS release, rather than being stuck on version 3.9.2 – which in turn has lead to better performance and faster app startups.
However, the webserver approach does not seem to work with hot-code-push. URLs are not being intercepted, so only content within the /www folder is actually served.
Steps to reproduce

Install the wkwebview-engine-localhost plugin.

Update your config.xml:

<content src="http://localhost:8080" />
...

<allow-navigation href="gap://ready" />
<allow-navigation href="http://localhost:*" />
...

<feature name="CDVWKWebViewEngine">
    <param name="ios-package" value="CDVWKWebViewEngine" />
</feature>
<preference name="CordovaWebViewEngine" value="CDVWKWebViewEngine" />

Install the app and push a CHCP update.

Relaunch the app twice. The update will not be available on the device and CHCP version info will stay the same as on initial app launch.

This would work well with the Telerik WkWebview and the telerik-wkwebview-fix branch.

Haven't tried that, but will. Thank you for the guide on how to reproduce it. I'm afraid that this will require some dirty hacks... Can't you use cordova-plugin-wkwebview-engine instead? :)

@nikDemyankov Thanks for looking into it!
With regard to your question. Here is a bit of backstory:
cordova-plugin-wkwebview-engine runs straight off the filesystem, which causes a metric ton of issues (no access to resources outside the app bundle, CORS issues and much much more). In short, the webview isn't usable in applications that do network requests or attempt to do things on the file system.
Due to of these limitations, both Telerik and Ionic have built their own WkWebview plugins which attempts to circumvent these issues.
In my opinion, Telerik has followed the correct approach by using a local webserver, but the plugin is not well maintained and built for Cordova iOS 3.9.2 and lower (It is basically a huge and impressive hack to drop in a WkWebview into Cordova when Cordova itself was not designed for the WkWebview). This plugin works, but prevents upgrades to Cordova 4 and retains an empty UIWebView which consumes a fair bit of RAM. In addtition, Cordova iOS 4 and newer has 'native' support for pluggable webviews, which makes a lot of the Telerik code obsolete.
Ionic's plugin is built for Cordiva iOS4 and newer. Their approach was to fork the cordova-plugin-wkwebview-engine and attempt to bridge the mentioned issues with a javascript polyfill. This polyfill is far from complete and doesn't resolve the filesystem issues of WkWebview. In addition, the polyfill is brittle and don't play well with libraries that builds on top of XHR.
We're working on an alternative to these two plugins that builds on wkwebview-engine-localhost. It should work similar to Teleriks view by using a local webserver, but without the drawbacks mentioned above. We're in the early testing stages, but it seems to work well for all the plugins we've tested so far except this one.

Cool, thank you for the info!

@nikDemyankov Hey! The Ionic team pivoted and added local HTTP server to their project which has resolved a lot of the issues mentioned above. We're going to transition from our internal beta project to theirs, as we think their project will be the 'go-to' WkWebview project in the future.
Hot code push doesn't currently play nice with their project tho. The issue is described here. In short, when accessing files via the inonic fork, one must drop the file:// protocol in the URL for the server bridge to pick up and redirect the request properly.
It would be really nice if you guys could support this WkWebview project, as both yours and their project are 'bread-and-butter' to the cordova community.

@kristfal any work around to fix the issue you mentioned. I'm having the same problem here.
Thanks!

@nikDemyankov , any updates on this? We'd like to switch to WKWebView in our project and this is issue is a blocker for us.

i am also stuck now, have to either disable this plugin or https://github.com/ionic-team/cordova-plugin-wkwebview-engine
@nikDemyankov do you intend to do a fix or does this look more like a longterm-incompatibility to you?

As a temporary workaround i wrote a wrapper function for XHR requests that figures out the correct HCP-Http-URL (if necessary) directly:
function getCompatUrl(url: string): Observable<string> {
    // on iOS WkWebview we need to XHR-access local files via http://localhost - which our
    // HCP - Plugin doesn't do, so we help it out here
    return Observable.create((observer: any) => {
        if (
            typeof window.cordova === 'undefined' ||
            typeof device === 'undefined' ||
            window.cordova.platformId !== 'ios' || // the problem is restricted to iOS WkWebView
            device.version.substr(0, 1) === '8' || // iOS 8 is using UIWebView which doesnt have this problem
            url.substr(0, 7) === 'http://' ||
            url.substr(0, 8) === 'https://' ||
            url.substr(0, 1) === '/'
        ) {
            // the request is not a local request on WkWebView > return the unchanged URL
            observer.next(url);
            observer.complete();
        } else {
            if (url.substr(0, 2) === './') url = url.substr(2);

            chcp.getVersionInfo((_, data) => {
                // if there is no previous version we have to load straigt from the filesystem
                const baseDir = data.previousWebVersion
                    ? cordova.file.applicationStorageDirectory.substr(7) +
                      'Library/Application Support/YOUR-APP-ID/cordova-hot-code-push-plugin/' +
                      data.currentWebVersion +
                      '/'
                    : cordova.file.applicationDirectory.substr(7);
                observer.next('http://localhost:8080' + baseDir + 'www/' + url);
                observer.complete();
            });
        }
   });
}

Of course you need to change YOUR-APP-ID

@chriswep It seems like the code you posted was integrated into your app to re-write every URL link if necessary. It would be easier to maintain (and implement) if there is a fix for this issue from the plugin end.

@seme1 of course this should be better implemented on the plugin side. Since apparently neither Nordnet nor Microsoft can't update their respective plugin easily, i decided to create a temporary workaround. However i just need to do this for XHR requests, all other request are working just fine (using the wkwebview plugin from ionic-team) - at least for my setup this is a maintainable solution since there are only very few code changes involved.

@chriswep Cheers and thanks for the workaround. I expect a lot of people want to use some kind of code push along with the (ionic) wkwebview, so your contribution is really great. Could you elaborate a bit on how you use your workaround?
– Does this workaround work with Microsoft's code push plugin?
– Do you manually wrap all your URLs or change the XHR prototype?
– How do you launch the app from the correct/code-pushed index.html?
– How do you use this for loading code-pushed assets via CSS (if you do that at all)?

– Does this workaround work with Microsoft's code push plugin?

My implementation uses features of the JS-Api that the nordnet plugin provides. However the concept should be the same: figure out where the hcp plugin puts its data (might be more difficult or even impossible with the MS plugin - can't say) and access the resource directly from the app via http://localhost:8080/FILESYSTEMPATH

– Do you manually wrap all your URLs or change the XHR prototype?

Since i only have one or two local XHR requests i just wrapped the URLs. Implementing an interceptor, middleware, service wrapper or even XHR prototype (depending on the framework you use or don't use) shouldn't be a problem though.

How do you launch the app from the correct/code-pushed index.html?

With my current setup (wkwebview from ionic-team) that works just as it always did. The HCP Plugin loads the correct file directly from file:// - which works fine (at least for my setup). Only when using XHR there is a problem.

– How do you use this for loading code-pushed assets via CSS (if you do that at all)?

Not sure if i know what you mean. CSS is working as well as media that is referenced in CSS.


Enumeration

Resolve #252
Related to https://github.com/SeaQL/sea-query/issues/131
Depends on SeaQL/sea-query#170

Btw... I will try to document all newly added types starting from this PR. Plz check the docs and give me some feedback on it @tyt2y3

Ready for review and merge @tyt2y3

Sorry for creating conflict

No worries, I will resolve it

I think we are pretty much done
https://github.com/SeaQL/sea-orm/blob/bb78a1d7097be2fc6cecceb547580ff8fd47250b/tests/common/features/active_enum.rs#L1-L43
https://github.com/SeaQL/sea-orm/blob/bb78a1d7097be2fc6cecceb547580ff8fd47250b/tests/active_enum_tests.rs#L1-L68
@Acidic9 @nicoulaj request for comment 👀

Ooh I really like the look of this. I had a bried look at the linked code snippets you shared @tyt2y3 and it looks really explicit. I like how you can use an enum as an integer too!

Just tried it on a complex project and it mostly worked flawlessly, awesome work !
Two things I noticed:

When using database enum, ColumnTrait::eq does not seem to cast the value, it generates WHERE mycol = ? and the query is invalid as a consequence
The new macros generate code with use sea_query instead of use sea_orm::sea_query, forcing users to add an explicit dependency on sea-query

The new macros generate code with use sea_query instead of use sea_orm::sea_query, forcing users to add an explicit dependency on sea-query

Nice catch! Fixed on f64f1e9216eaee57822ef2071960ff27072d06ec

When using database enum, ColumnTrait::eq does not seem to cast the value, it generates WHERE mycol = ? and the query is invalid as a consequence

That's bad. See da9f3ea60ca8b56013270dff07bfee5eed4fd9c4. Thanks!! @nicoulaj

After second thought, it only make sense to cast string to enum type inside = & != comparison. See 10f3de0f9da0738903c6cb962d11e371f1d2f278


~/.vim/tools//shell/bash/update-idutils.sh: line 15: mkid: command not found

When I use exVim and try to excute ':Update' command. I get the following error: "~/.vim/tools//shell/bash/update-idutils.sh: line 15: mkid: command not found"
How can I fix it?
I run it on Mac OS X 10.9

Hey I guess the brew package name is wrong, I occurred the same error but got worked exVim via the following command:
$ brew install idutils

Just let others know this :)

thanks @yorkie , corrected.


feat: 10/15/30 min grain to Pinot

SUMMARY

Adding new time grains to Pinot
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Verified new grains are working! 🥳


Unable to package, annotation problem

when running mvn package on  commit e7c879ed3abe10e446ff103887ad665ca6acf04e
ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project spring-petclinic: Compilation failure: Compilation failure:  [ERROR] /tmp/spring-petclinic/src/main/java/org/springframework/samples/petclinic/system/CacheConfiguration.java:[31,16] cannot find symbol [ERROR]   symbol:   method proxyBeanMethods() [ERROR]   location: @interface org.springframework.context.annotation.Configuration [ERROR] /tmp/spring-petclinic/src/main/java/org/springframework/samples/petclinic/PetClinicApplication.java:[28,24] cannot find symbol [ERROR]   symbol:   method proxyBeanMethods() [ERROR]   location: @interface org.springframework.boot.autoconfigure.SpringBootApplication [ERROR] -> [Help 1]

javax.validation was missing in pom.xml ; must add it
See PR 763


Required string property definitions become "string | undefined" when imported

When a string property foo is required, Volar sees it as foo: string, but when the exact same property definition is imported to define baz, Volar sees it as baz?: string | undefined:
// component-js.vue
<script lang="ts">
import { defineComponent } from 'vue'
import { StringRequired } from './my-props';

export default defineComponent({
  props: {
    foo: {
        type: String,
        required: true,
    },
    bar: StringRequired,
  },
  data() {
      return {
        foo: this.foo, // (property) foo: string
        bar: this.bar, // (property) baz?: string | undefined
    };
  }
})
</script>

// my-props.ts
export const StringRequired = {
	type: Symbol,
	required: true,
}

This happens with every other type except Boolean properties.

Please try
export const StringRequired = {
	type: Symbol,
	required: true,
} as const

or
export const StringRequired = {
	type: Symbol,
	required: true as const,
}


bump version

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.08%. Comparing base (1c6246f) to head (266a731).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #162   +/-   ##
=======================================
  Coverage   95.08%   95.08%
=======================================
  Files          28       28
  Lines        2951     2951
  Branches      395      395
=======================================
  Hits         2806     2806
  Misses        144      144
  Partials        1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update blocks.md

The 'Searching Blocks by Date' incorrectly referred to spam reports instead of blocks.

oy, copypasta


DEPS.xwalk: Roll ozone-wayland (a64feb1 -> 5d7baa9).

5d7baa9 Rename WindowTree*Wayland as WindowManagerWayland.
9c19d69 Move WindowTreeHostDelegateWindow to platform/

These two commits are backports from ozone-wayland master and removes a
dependency across shared libraries on a class that is not exported and
was causing problems when building Crosswalk with
component=shared_library.

@darktears

LGTM


transports/rabbitmq: add timeout option (updated)

This is a duplicate of pull request #253, but updated to be mergable with master again. It adds a timeout option to rabbitmq, since pika defaults to .25 seconds, which can lead to problems when a lot of clients are connecting at the same time.
This solves a practical problem for us, where hundreds of clients can simply overwhelm a rabbitmq server at connection time, so it cannot respond within the .25 seconds. This patch increases the timeout to 2 seconds, which solves the problem for us. It also makes it a setting.

My vote: leave the default but make it configurable.
-Jeremy
--
Insert PGP signature here.

On Sep 10, 2015, at 9:22 AM, Tim Stoop<EMAIL_ADDRESS>wrote:
This is a duplicate of pull request #253, but updated to be mergable with master again. It adds a timeout option to rabbitmq, since pika defaults to .25 seconds, which can lead to problems when a lot of clients are connecting at the same time.
This solves a practical problem for us, where hundreds of clients can simply overwhelm a rabbitmq server at connection time, so it cannot respond within the .25 seconds. This patch increases the timeout to 2 seconds, which solves the problem for us. It also makes it a setting.
You can view, comment on, or merge this pull request online at:
https://github.com/josegonzalez/python-beaver/pull/345
Commit Summary
Pieter's patch for rabbitmq timeout.
File Changes
M beaver/config.py (2)
M beaver/transports/rabbitmq_transport.py (5)
M docs/user/usage.rst (1)
Patch Links:
https://github.com/josegonzalez/python-beaver/pull/345.patch
https://github.com/josegonzalez/python-beaver/pull/345.diff
—
Reply to this email directly or view it on GitHub.

Can you look into the failing tests? I'll buy you a beer :) (or hot chocolate, if that's your thing).

Settings need to be integers, apparently. So instead of trying to change that, I decided on a middle ground with a 1 second default. Hope that alright?


data-bgset not auto-sizing to parent container

I'm having trouble getting this to work, and assume that I'm doing something wrong,
In a case such as below - is this the correct specification for data-bgset?
Basically, I want to to choose the first image large enough to cover the parent with, without upscaling.
I also want it to reselect the image if the viewport size changes, hence changing the width of the parent container.
In practice, it always gets the last image for the largest resolution, which is much larger than necessary to meet the parent width.

Some more testing indicates that it's selecting the image based on the viewport width, rather than the parent width.
I have data-sizes="auto" and the css setting  background-size:cover - which I thought were the triggers for parent sizing ??

without a test case it is impossible to check what is going wrong. (follow: https://github.com/aFarkas/lazysizes/blob/gh-pages/.github/ISSUE_TEMPLATE/bug_report.md)
bgset is deprecated for the use of background-size cover.
you are using sizes with art direction which does not make any sense.

Please read an article about how to properly use responsive image (until you understand what I mean with point 3). If you still fail, create a test case and re-open.

Thanks.
Actually, I think I understand #3 and I had tried using resolution switching:
data-bgset="/image270.jpg 270w, /image320.jpg 320w, /image480.jpg 480w, /image640.jpg 640w, /image768.jpg 768w /image992.jpg 992w, /image1920.jpg"
But it was likewise always falling through to the last image, so I tried using art-direction thinking that perhaps the plugin(s) used that as a guide for the parent size.
So are you saying that data-bgset will not support background-size:cover for data-sizes="auto" and hence the fall-through ?
This is problematic for me, as the images are not consistently sized, which is why I needed 'cover' sizing.
Is there any way around this?

in case of resolution switching especially with chrome. Chrome always takes last if this image is already in cache.
no data-bgset would support cover also with data-sizes="auto" in case of art direction you won't need sizes though.

But I would urge you to use object-fit on the image itself. It's basically the same thing but much better without any custom syntax and better performance. In case you need to support old browser use either this lazysizes only one
https://github.com/aFarkas/lazysizes/tree/gh-pages/plugins/object-fit or the other most used one.
3. to help you concrete I still need test case.


Fix typescript overload

https://www.typescriptlang.org/docs/handbook/functions.html#overloads
TS overloads are basically syntax sugar for function(x : TypeOne | TypeTwo). So there should be no problem when allowing them.
For that we need to ignore funciton declarations.
function pickCard(x: {suit: string; card: number; }[]): number; // ignore
function pickCard(x: number): {suit: string; card: number; };   // ignore
function pickCard(x): any {                                     // transpire only functions with body
    // Body....
}

Done in #128


x/website: doc/install has outdated filename for linux

There is a command on doc/install page that uses an outdated filename that is being shown as an example of how to install go for Linux:
tar -C /usr/local -xzf go1.14.3.linux-amd64.tar.gz
What did you expect to see?
tar -C /usr/local -xzf command should use the latest archive filename for the current go version
What did you see instead?
go1.14.3.linux-amd64.tar.gz filename is statically defined in the markup.

Thanks. I searched for x/website since that's the issue that's created for the "Report an issue" on the website.


Multiple issues with the grammar

Preface:
I have installed the mermaid TS module using the TSInstall command provided by the Neovim Tree-Sitter Plugin. After a quick google search for "Tree-Sitter Mermaid" I could only find this repository, so I assume that the Tree-Sitter Plugin installed the mermaid module from here. Should that not be the case I apologize for the inconvenience.
As you can tell from the following screenshot, I have been experiencing a couple of issues with the Mermaid Grammar.
Specifically the following is quite obvious:

The module doesnt know about Multiline Strings
The module treats lines following a single - weirdly
Under certain circumstances, the only one which I know of being the use of a - in a node name, the module highlights the character o white

The code used:
flowchart TD
    First-Task -- Error ---> SomeTask
    SomeTask["Multiline
        String with Task Name"] -- Success --> Node

flowchart TD
    First-Task -- Error ---> SomeTask
    SomeTask["Multiline
        String with Task Name"] -- Success --> Node

I'm working on a language support extension for Zed, and also getting some issue with the grammar.

⛔ tree-sitter-mermaid
  ✅ tmLanguage

zed-mermaid grammar reference
vscode-mermaid-syntax-highlight grammar reference

Having similar issues here:

the letter 'o' in the middle of words is highlighted
the 'as' in Database is highlighted

Minor issue: the syntax highlighting did not work until I added a %%{ init: [...]}%% line below  ```mermaid, but now that it is working, I can remove the init line and the highlighting remains.


eventbased or periodical data transfer

The Python script cyclically reads data from a MQTT Broker and publishes information on the dbus, using the service name com.victronenergy.grid. This makes the Venus OS work as if you had a physical Victron Grid Meter installed.

Is that the case? It seems as if this is event driven? Just had a quick look and thought I'd ask the creator really quick

Today I got some time to check everything and the mqtt part is event driven, the dbus part is loop driven (cyclic).
By reducing the dbus invervall to 100ms I could significantly improve the power control of my multiplus 2 with a ET340 SmartMeter. Very nice!


CLI delete images command fails

Description:
After the syntax changes to metadata.json cellery delete command fails. A list of existing cell images is returned to during this command and metadata.json of each cells are being read. Hence due to the new changes in metadata.json cellery delete command is failing.
Affected Product Version:
Latest sdk.
Steps to reproduce:

Build a cell image using cellery build command.
Delete a cell image using cellery delete command.

This issue is not related to the structs and the structs had already been properly updated before this issue occurred.
This issue occurred when there are old images present in the repository. This is the expected behavior as the metadata structures were completely changed after the last release.
Therefore, this is not an actual issue and is only the expected behavior.


[commonjs--resolver] Failed to resolve entry for package without explicit main

Describe the bug
I got the following error: [commonjs--resolver] Failed to resolve entry for package "transform-spread-iterable". The package may have incorrect main/module/exports specified in its package.json., but running the script natively in Node does not produce an error.
Reproduction
https://stackblitz.com/edit/vitejs-vite-4yjmx8?file=main.js
Steps to reproduce
(This describes a standalone repro.)

yarn add vite transform-spread-iterable
Add test.js:

import t from "transform-spread-iterable";

console.log(t);

vite.config.js:

import { resolve } from "path";
import { defineConfig } from "vite";

export default defineConfig({
  build: {
    lib: {
      entry: resolve(__dirname, "test.js"),
      name: "MyLib",
      fileName: "my-lib",
    },
  },
});

yarn vite build
Run node test.js (with "type": "module" set in package.json). There's no error.

FYI, transform-spread-iterable looks like this:
$ tree node_modules/transform-spread-iterable
node_modules/transform-spread-iterable
├── example.js
├── index.js
├── license
├── package.json
└── readme.md

Object.keys(JSON.parse(require('fs').readFileSync('node_modules/transform-spread-iterable/package.json', 'utf-8')))
[
  'name',
  'version',
  'description',
  'scripts',
  'keywords',
  'author',
  'license',
  'dependencies',
  'files',
  'tonicExampleFilename',
  'babel',
  'jsnext:main',
  'devDependencies',
  'repository'
]

System Info
System:
    OS: macOS 13.6
    CPU: (8) arm64 Apple M1
    Memory: 66.30 MB / 16.00 GB
    Shell: 5.2.15 - /opt/homebrew/bin/bash
  Binaries:
    Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node
    Yarn: 1.22.15 - /usr/local/bin/yarn
    npm: 8.12.1 - /opt/homebrew/bin/npm
    pnpm: 7.28.0 - ~/Library/pnpm/pnpm
    bun: 1.0.6 - ~/.bun/bin/bun
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Browsers:
    Chrome: 119.0.6045.105
    Chrome Canary: 121.0.6113.0
    Firefox Nightly: 118.0a1
    Safari: 17.0
    Safari Technology Preview: 17.4
  npmPackages:
    vite: ^4.5.0 => 4.5.0

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hmm, actually, adding "main": "index.js", to node_modules/transform-spread-iterable/package.json does not help either. I wonder what's going on.


Some ApplePay amounts may be wrong in some locales.

Regarding the use of NSDecimalNumber in https://github.com/google-pay/flutter-plugin/blob/main/pay_ios/ios/Classes/PaymentHandler.swift#L125, please read the Discussion section in https://developer.apple.com/documentation/foundation/nsdecimalnumber/1409902-init.
Should amounts really be strings? What are the odds of users of this plugin will convert their amounts to string correctly? It should always be with a . as decimal separator, right?

ACK @kristoffer-zliide. Thank you for bringing it up.
My suggestion, for consistency reasons would be to use the decimal point element for all prices. It seems that Double does not account for the locale at instantiation.
I'm suggesting the following:
NSDecimalNumber(value: Double(item["amount"] as! String)!)

There's the more explicit alternative to use a number formatter, though I don't think the extra overhead justifies the marginal  added clarity.
Did you have other ideas in mind?

I don't really know anything about Apple's APIs, sorry. I just thought that since you're representing decimal numbers as strings, there must be bugs in there, and, lo and behold, there was.
Next up are all the bugs people using this plugin will make converting their decimal amounts to strings to pass them to this plugin. How to fix those? I can't help thinking the right way to go is using double for amounts in the API. Then pass it as-is to Apple Pay and take care of using the correct formatting that Google Pay expects (. and exactly two decimal places?)
Note that these bugs probably won't be caught during regular QA, as this issue also demonstrates, since all test devices use a locale where it works, so bugs that cause payment to fail sometimes for some people will be released to the public.

This is indeed a situation where there's going to be discrepancies between platforms (Apple Pay using NSDecimalNumber and Google Pay using a String), and hence, there's the opportunity to pick what's more convenient. I personally see reasons for and against for approaches:

String: The price is used for display purposes only on both platforms, so the numeric value is irrelevant. Strings are univocal (when conversions aren't required).
Number: It's more intuitive to think of a price as a number. Said so, types holding numbers have limitations in size, precision and rounding.

Looking at it from the eyes of this plugin, choosing either of them would require converting to/from the types on one of the platforms, so another question to ask is whether it's preferable to convert from a number to a string on Android, or from a string to a number on iOS. They seem equivalent to me.
All in all, it mostly comes down to dev preference on whether to work with numbers or strings when defining a price amount for an item. To me, both options are equally reasonable.
For now, I'll add a PR to take localization out of the equation when converting amounts on iOS. In the meantime, it's worthwhile considering opening up a new discussion on the topic to gather general thoughts/preferences from users of the library.

Just to be clear, the String used in the API is not the string used for display right? The API string needs to be English, whereas the display strings are in the phone's locale. That might lead to more confusion.

Your assumption is correct.
For now, the API has been updated to remove ambiguity and unexpected results.
With that, I feel that the API can benefit from using univocal representations of amounts like cents, or base 10 decimal numbers, so I suggest leaving this thread open for now, and considering taking it to a formal discussion.


Create sip-draft_360avgcom.md

This SIP proposal is about increasing the number of blocks that the Average Commitment is calculated over from 24 to 360, with a potential of a smaller number also being suitable.

There is a reason for this, if you increase too much the filter moving average window you give the opportunity for an attacker that just starts mining with a lot of commitment to mine many blocks without increasing the average commitment. This way such attacker will be benefited for a longer period of time than it would be now.
These fluctuations, although undesirable, have shown to be stable, do not change the average, and do not impact the average (expected) mining returns.

Would the be a value in-between that may address both concerns then? Any increase will smooth it out. 24 send to be very prone to noise. What do you feel is the max number of blocks it should take for the commitment to adjust to sustained increase in commitment?

Any updates on this...?
@jjos2372  - if not closing

I think with the idea of shorter blocks and a different behavior of the miners - e.g. mining only every fifth block - the problem will not exist anymore

Good to close
On Tue, Apr 4, 2023, 9:53 PM frankTheTank72 @.***>
wrote:

I think with the idea of shorter blocks and a different behavior of the
miners - e.g. mining only every fifth block - the problem will not exist
anymore
—
Reply to this email directly, view it on GitHub
https://github.com/signum-network/SIPs/pull/62#issuecomment-1495842386,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4UN7WGMBLMHVVAGTCDSXDW7QDUJANCNFSM6AAAAAAQ22WYWU
.
You are receiving this because you authored the thread.Message ID:
@.***>

ok. thanks all. closing


Changed box colors on index

closes #107

Looks good. Could you run a PNPM update to Latest? it's been a while since we last updated our dependencies.

Done! I've also included pnpm-lock.yaml in the .gitignore

That's good. Any new errors or warnings in the build logs? If not, this is ready to merge.


auth_session document clean up

This pr resolves #424
This makes use of MongoDB's TTL index which will delete expired entries https://www.mongodb.com/docs/manual/tutorial/expire-data/ .
In this case we set the TTL based on CONTROLLER_PRESENTATION_EXPIRE_TIME as well as a new CONTROLLER_PRESENTATION_BUFFER_TIME which is used to ensure that we do not delete an auth session too soon before the UI can update.
As of now we have a TTL index that will delete expired, failed, and abandoned auth_sessions.
Note that the expireAfterSeconds does guarantee that it will be deleted after that many seconds. Instead that it will not be deleted before the given number of seconds have passed.

Will we leave verified state permanently? Or should that be flagged for deletion as well?

Will we leave verified state permanently (someone scans and shares successfully)? Or should that be flagged for deletion as well?

This is the point of the config file. I am open to suggestions on how we could make it more configurable than the file. I considered making at a REST API endpoint which was why I stuck with a json object.

@loneil @esune I realized a limitation of moving to a single ttl index is that since we can only assign one expiration time per index we can't have a different expiration time for each proof_status. aka expired, aborted, failed, etc can only expire at one time unless we make multiple indexes.
To me multiple indexes seems like the best option as long as we want to support multiple expiration times for each state.

I have now updated this to support the following

[X] updating indexes

[X] Create if it does not exist
[X] Update if it does
[X] If not in config delete it

[X] Support restarting the service
[X] Make the path to the config file an environment variable
[-] Make the config file mountable

[X] https://github.com/bcgov/vc-authn-oidc/blob/18af14e939843454db6e1211e4f6c073a7b73a07/docker/docker-compose.yaml#L124

[X] Add friendly defaults if the file can not be found

best default is to maybe not delete anything?

The only thing I was unsure of was how to reflect this mountable file in the helm charts.

The following changes have taken place

[X] single index for ttl
[X] notify the user of the need to manually delete the index
[X] no longer drop all indexes

@Gavinok changes look good, but the tests are still failing - it seems like a linting error currently.


Document how to ignore changes to desiredSize of managed node group

Based on looking at:
https://www.pulumi.com/docs/reference/pkg/aws/eks/nodegroup/
There is a section for https://www.pulumi.com/docs/reference/pkg/aws/eks/nodegroup/#ignoring-changes-to-desired-size that doesn't seem to actually demonstrate how to make this work.
If you have something running in the EKS cluster like cluster-autoscaler, the desiredSize will be changed for you and be marked as a diff.

Thanks for pointing the error in the example out. In case you didn't find this in the documentation, the way to do this is use the ignoreChanges resource option: https://www.pulumi.com/docs/intro/concepts/programming-model/#ignorechanges

The previous link has gone stale. Here's a new one: https://www.pulumi.com/docs/intro/concepts/resources/options/ignorechanges/

Closing this as documented at https://www.pulumi.com/docs/intro/concepts/resources/options/ignorechanges/, but if there's still something to be done here, feel free to reopen with details. Thanks!


Option to show descriptions above/below inputs

Hi,
I noticed that currently the descriptions are only rendered in the tooltips. I think it would be nice to have the option to show them in the UI permanently so they are easier to discover.
Would you be interested in another PR for such a feature?

Yes, I am absolutely open to this. I think it would be good to enable/disable this via a show_description parameter to the Form.__init__.

Implemented in #88


fix renovate rules to prevent it from lumping hbase & spark together

Renovate PR #6847 intended to only upgrade hbase in the bigtable/spark example. But it seems to have also accidentally upgraded spark as well. This caused the example to break since it bumped spark to a nonexistent version

It's not clear how the Renovate config caused this: https://github.com/GoogleCloudPlatform/java-docs-samples/blob/main/renovate.json

This PR confirms this is no longer an issue https://github.com/GoogleCloudPlatform/java-docs-samples/pull/7721/files


Mention Empty Field Bounds for Recursion

Please excuse my stupidity. This corrects #451

I would rather explain why this sometimes works rather than simply saying to set it to "", because that is not a magic bullet for recursion and will not work in many cases.

Also it will be made unnecessary sometime in the next few days for 0.8.0 once I fix #436.

Closing because this is no longer necessary as of #456. I will revert the other commit.

Thanks, @dtolnay! :)