Wrong quoting for local-data TXT records

Hi,
There is a problem with the qouting in the unbound.conf file for TXT records in the local-data field. Since TXT records can contain whitespaces double quotes are needed around the rdata part of the local-data set. Hence the local-data entry has to be single quoted. This is explicitly described in the unbound.conf man page:

For record types such as TXT,  use  single  quotes,  as  in
local-data: 'example. TXT "text"'.

I would suggest to use single quotes for all local-data entries. This is not explicitly allowed in the unbound.conf manual, but it works on my unbound installation flawless.
Kind regards
Count Sudoku

Sorry, I was wrong! The quoting can be set by the caller for arrays.

Not a worry, glad you sorted it out.

I stumbled on the same problem and I don't understand what you were meaning by:

The quoting can be set by the caller for arrays.

As far as I can see, the double quotes are hardcoded in the erb template:
https://github.com/voxpupuli/puppet-unbound/blob/e1b498d458004b2cabd6b163f0bcaea01e6bb55e/templates/local_zone.erb#L9
So how do you handle TXT records containing double quotes and spaces (like DKIM records) ?
Thanks in advance for your help.

My comment  above

Sorry, I was wrong! The quoting can be set by the caller for arrays.

was for the local-data part in the templates/unbound.conf.erb:
https://github.com/voxpupuli/puppet-unbound/blob/e1b498d458004b2cabd6b163f0bcaea01e6bb55e/templates/unbound.conf.erb#L192
If you hand over something like this:
$local_data = [
    "'mail._domainkey.example.com 14400 IN TXT \"v=DKIM1;h=sha256;k=rsa;\"\"p=DKIM_KEY_PART_1\"\"DKIM_KEY_PART_2\"'"
]

to the unbound class:
class { '::unbound':
    …,
    local_data => $local_data,
    …,
}

you will get, what you want.
For the quoting in templates/local_zone.erb you are absolutely right. So my comment above was right by accident:

I would suggest to use single quotes for all local-data entries.

Thanks a lot for your answer. I identified two ways to insert local-data (local_zone and record) but I missed the third one :-)
May be I will propose a pull request to automatically single quote TXT records and split them into pieces of 255 characters.


Update to circe 0.12.0-RC2

Codecov Report

Merging #92 into master will not change coverage.
The diff coverage is 80%.

@@           Coverage Diff           @@
##           master      #92   +/-   ##
=======================================
  Coverage   91.05%   91.05%
=======================================
  Files           8        8
  Lines         123      123
  Branches        7        6    -1
=======================================
  Hits          112      112
  Misses         11       11

Impacted Files
Coverage Δ

...n/scala/io/circe/jackson/CirceJsonSerializer.scala
95% <80%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add basic site analytics

Google Analytics might be a little heavy here, and I'm not sure if it's free, but we should have something similar on the site, at least so we can see traffic metrics and Referrer values.
Resources listing the best web analytics tools out there:

Hotjar: Top 20 web analytics tools from our survey of 2000+ experts
First Site Guide: The top 10 most popular web analytics tools
Simplilearn: 20 Best Web Analytics Tools: How to Make the Most of it?
Leadfeeder: 25 Best Website Analytics Tools for 2022
Wix: 11 Best Web Analytics Tools to Boost Your Business
Elementor: 10 Leading Web Analytics Tools for 2022 [Free and Paid]
MonsterInsights: 9 Best Web Analytics Tools for 2022 (Free and Paid)
Blogging Wizard: 11 Best Web Analytics Tools For 2022: Get Meaningful Website Insights

Based on the above resources, the tools with the most recommendations (in desc order) were:

Google Analytics (7)
Matomo (7)
Kissmetrics (7)
Hotjar (6)

So these are the ones I took the time to dig into on this comparison spreadsheet on Google Drive. I looked at cost, .... It ultimately boils down to what we're willing to pay for, because different services are more worthwhile at different cost tiers. I can't imagine we'll ever have more than a few hundred monthly visitors, so I don't really want a recurring monthly fee for this small use case. Based on the above research the best free tier service (which would be my vote) seems to be:
TBD

@asdkiller and I will discuss and close this issue once we reach a decision.

Until I hear otherwise, we are moving forward with Google Analytics.


Metadata editor support for optional dropdown/enum is broken

Describe the issue
Update a schema 9e.g. runtime) to add a new optional field, either a:

a dropdown

        "engine": {
          "title": "Kubeflow Pipelines engine",
          "description": "The Kubeflow Pipelines engine in use (Argo or Tekton)",
          "type": "string",
          "uihints": {
            "field_type": "dropdown",
            "default_choices": ["Argo", "Tekton"]
          }
        },

enum

        "engine": {
          "title": "Kubeflow Pipelines engine",
          "description": "The Kubeflow Pipelines engine in use (Argo or Tekton)",
          "type": "string",
          "enum": ["Argo", "Tekton"],
          "default": "Argo",
          "uihints": {
            "field_type": "dropdown",
            "default_choices": ["Argo", "Tekton"]
          }
        },

Now try to open an existing metadata document where this field was not populated (e.g. old doc with a new schema with the optional field)
Exception:
MetadataEditor.tsx:347 Uncaught (in promise) TypeError: Cannot read property 'toLowerCase' of undefined
    at MetadataEditor.tsx:347
    at find (index.es6.js:2266)
    at MetadataEditor.getDefaultChoices (MetadataEditor.tsx:344)
    at MetadataEditor.renderField (MetadataEditor.tsx:460)
    at MetadataEditor.render (MetadataEditor.tsx:522)
    at vdom.js:53
    at new Promise (<anonymous>)
    at MetadataEditor.renderDOM (vdom.js:52)
    at MetadataEditor.onUpdateRequest (vdom.js:30)
    at MetadataEditor.onUpdateRequest (MetadataEditor.tsx:302)

Also, in the case of enums, getDefaultChoices should not look into the values of existing metadata documents as it does not support other values except the enum ones.

Also, what are my options for enums, do I need to set "default_choices": ["Argo", "Tekton"] on ui-hints?

Also, what are my options for enums, do I need to set "default_choices": ["Argo", "Tekton"] on ui-hints?

The issue is coming from the dropdown field dynamically creating the default choices. It starts with the default_choices from ui-hints. The issue is arising when it appends the value of that field in all other metadata instances for that schema (and assumes that all other metadata have a value for that field, which isn't true in this case).
I can put up a quick PR to fix this (or I could just push straight to this PR?), but @lresende or @kevin-bates how should make enum and default_choices work? If both are present, should it merge them? Or go with enum by default? Let me know and I can get this up this afternoon.

The issue is coming from the dropdown field dynamically creating the default choices. It starts with the default_choices from ui-hints. The issue is arising when it appends the value of that field in all other metadata instances for that schema (and assumes that all other metadata have a value for that field, which isn't true in this case).
I can put up a quick PR to fix this (or I could just push straight to this PR?), but @lresende or @kevin-bates how should make enum and default_choices work? If both are present, should it merge them? Or go with enum by default? Let me know and I can get this up this afternoon.

The issue is coming from the dropdown field dynamically creating the default choices. It starts with the default_choices from ui-hints. The issue is arising when it appends the value of that field (here it's engine) from all other metadata instances for that schema (and assumes that all other metadata have a value for that field, which isn't true in this case).

I thought that as well, but then why I have a similar issue if I manually edit the runtime and add the engine field? If you add it manually is the issue gone?

I can put up a quick PR to fix this, but @lresende or @kevin-bates how should make enum and default_choices work? If both are present, should it merge them? Or go with enum by default? Let me know and I can get this up this afternoon.

So, from @kevin-bates point this morning, when the field is an enum, it should not consider anything else other than the values from the enum (e.g. users cannot enter their own new values)

The issue is coming from the dropdown field dynamically creating the default choices. It starts with the default_choices from ui-hints. The issue is arising when it appends the value of that field (here it's engine) from all other metadata instances for that schema (and assumes that all other metadata have a value for that field, which isn't true in this case).

I thought that as well, but then why I have a similar issue if I manually edit the runtime and add the engine field? If you add it manually is the issue gone?

I can put up a quick PR to fix this, but @lresende or @kevin-bates how should make enum and default_choices work? If both are present, should it merge them? Or go with enum by default? Let me know and I can get this up this afternoon.

So, from @kevin-bates point this morning, when the field is an enum, it should not consider anything else other than the values from the enum (e.g. users cannot enter their own new values)


Automatically configure after a configuration preset has been selected

This change addresses item #2958
This changes visible behavior when selecting a configuration preset.
The following changes are proposed:

Automatically configure after a configuration preset has been selected

The purpose of this change
Remove the need of manually configuring every time a different configure preset is selected.
Other Notes/Information
This is a very simple implementation of my feature request.
A few people use it successfully for a while now, however I am not sure if this is the proper way of doing it.
We only used it for single root projects so far.

Thanks for the PR.  We'll evaluate if this is the best place to insert the reconfigure.  I know that there is already a check deeper in the code that will clean the binaryDir if it is reused across multiple presets.  I just want to make sure we don't double-configure.
Another thing that we'll want for this is a setting that turns this feature on and off.  Some developers have projects that take a very long time to configure and they may not want to auto-configure when changing the preset.  (for similar reasons we have a configureOnOpen setting).  I haven't evaluated whether we should have a similar feature for the non-presets case when changing the active Kit, so maybe we should add a cmake.automaticReconfigure setting.  The description can explain that it reconfigures the project when a Kit or configurePreset changes.

IMO this should be optional. Enabled by default is OK but I'd like to be able to turn it off.

I added a cmake.automaticReconfigure setting to control this feature.
I phrased it only for preset selection, but it can always be adjusted to also cover kit changes.
I also added a German translation of the description, although I don’t really know yet how i18n is handled here.

I know that there is already a check deeper in the code that will clean the binaryDir if it is reused across multiple presets. I just want to make sure we don't double-configure.

I found two places where this is checked:

https://github.com/microsoft/vscode-cmake-tools/blob/main/src/drivers/cmakeDriver.ts#L489
https://github.com/microsoft/vscode-cmake-tools/blob/main/src/drivers/cmakeDriver.ts#L580

As far as I can tell, only old configuration files are cleared, but no reconfiguration happens in either case.
I actually tried to test the shared binaryDir with different presets and saw, that there has to be a generator change between the presets (https://github.com/microsoft/vscode-cmake-tools/blob/main/src/preset.ts#L1631).
I created two presets with same binaryDir and different generators, but to my surprise not even the old configuration gets cleared. When I configure the project afterwards, CMake gives an error that CMakeCache has a different generator specified.

@maxmitti, thanks again for the PR.  I re-enabled the feature by default and added some logic to avoid a configuration if the Kit did not actually change.  This also fixed a bug with the Kit logic because the active kit was already changed by the time you did the check so the configure wasn't happening.  I also added logic to Variant changes.  It turns out we were already doing automatic configure for those and now that behavior will respond to the setting as well.

@bobbrow thanks for your support. I’m glad we found a good solution.


Getting Stacktrace as ".CallSite.Target" when logging is done in Catch in MVC controller class.

Hi,
I am getting ".CallSite.Target" as stacktrace while logging in a Catch statement. I am calling a service to authenticate the user and when the authentication failed then Service throw exception like ProxyException was caught. When I try to NLog it from Catch in Controller, then I didn't get proper Stacktrace. I get
Layout
"${gdc:UserName}  ||||  ${date:universalTime=true} ||||  ${level}  ||||  ${stacktrace} ||||  ${message}" />
NoUser  ||||  06/26/2014 11:29:15 ||||  Error  ||||  .CallSite.Target => Log.Error => NLogLogger.Error ||||  Identification/Authorization failed: Please verify user account or contact administrator.
Then I tried DetailedFlat format of Stacktrace. I get
NoUser  ||||  06/26/2014 11:27:27 ||||  Error  ||||  [Void CallSite.Target(System.Runtime.CompilerServices.Closure, System.Runtime.CompilerServices.CallSite, Mdrx.CommonComponents.EPCS.RxArchive.Logging.ILogger, System.Object, System.Exception)] => [Void Error(System.String, System.Exception)] => [Void Error(System.String, System.Exception)] ||||  Identification/Authorization failed: Please verify user account or contact administrator.
Then I used Raw format of Stacktrace, I get
NoUser  ||||  06/26/2014 11:53:35 ||||  Error  ||||  CallSite.Target at offset 354 in file:line:column :0:0
Error at offset 66 in file:line:column :0:0
Error at offset 66 in file:line:column :0:0
||||  Identification/Authorization failed: Please verify user account or contact administrator.
The whole scenario is working if the authentication is successful and I Log in try only but when its done in Catch after the exception occurs, the stacktrace it is lost.
Thanks,
Navjot

@ernavjotsingh2  if this is still a problem, please submit the requested info and re-open this issue.


Replace JSNExt by Module / Add ES2015 transpiled Files

We have to change JSNext by Module (it seems to be deprecated)
But the target of module has to be a Trapiled ES2015 file, not a common JS or a TS file. I think we have to dig deeper with Aymeric about that.

Maybe do the fix into 2.0.0 when all components will be migrated to Typescript ?

Update: the issue with the style wasn't actually that the file isnt present, but that when you use modules, the import for files is supposed to be
const logo = new URL(
<EMAIL_ADDRESS>  import.meta.url
).href;

But that syntax doesn't work when building for es2015 :(
Sooooo, 2 solutions:

Don't build for cjs
Use a bundler like rollup/snowpack or whatever for the packages using images (just the footer actually)

A WIP branch is available here for testing

The solution found is to add a declaration file into include prop of tsconfig with
declare module *.svg

So any more compiler error and I think it's do the trick


Introductions

Hello fellow team members!
My name is Bruno Grande. I'm a PhD candidate in Molecular Biology and Biochemistry working in cancer genomics at Simon Fraser University in the Vancouver area. If the name sounds familiar, it's because I'm the one who proposed this project, "Developing advanced R tutorials for genomic data analysis". While that technically makes me team leader, I want this project to be a collaboration between people with similar interests in R and genomics. It's great to see that the idea of creating high-quality R tutorials focused on genomics sparked interest in quite a few of you, especially among remote participants.
To start us off, how about we all introduce ourselves to one another with the following?

Your name
Your position (e.g. PhD, MSc, postdoc, staff)
Institutional affiliation
Whether you will be a in-person or remote participant
If you're a remote participant, where will you be joining us from (city and time zone)?
What motivated you to work on this project?

I'll kick off other discussions soon in preparation for Hackseq, which is starting in less than two days! Feel free to include any questions you may have in your reply.

Hi gang!
I'm Anna, I'm a second-year Masters student at UBC, also in Vancouver. I'll be participating in person and I'm extremely excited for the food. I decided to work on this because I need it for my own research - I'm trying to document a possible role for a methyltransferase in DNA repair - and it would be beneficial to develop more in depth knowledge of tools for this as well as to speak to people in similar and disparate fields to network and get to know each other!
Looking forward to meeting the rest of you nerds
Anna

Hello, @all and special thanks to our captain @brunogrande.
My name is Yisong Zhen and I am staff scientist at Fuwai hospital in China. Fuwai hospital is a leading and specialized in cardiovascular diseases, like Montreal Heart Institute in Canada.
I might have to re-clock my bedding time in the coming three days, I am in Beijing. So I have to ask the captain the assigned task before embarking.  If I do not need or few times to re-schedule my time table, this is definitely great and convenient for me. However, I have been in this hospital when/since I completed my doctoral studies; I know that medical doctors are duty-on-call and we are used to wait for the emergence at any time. -:)
I recently have read the book by Robert C. Martin (The Clean Coder ) and John Sonmez (The Complete Software Developer's Career Guide). Now I accept their sayings in this community are to share my knowledge (if I have). Be humble and be hungry.
Z

Hello,
I'm Florian Privé, a PhD student in predictive human genetics in Grenoble, France.
I'm attending remotely, so my typical day with you will be 6pm-2am.
I've recently submitted a paper about two R packages for efficient management and analysis of large-scale genome-wide data.
Basically, I love R(cpp) and I want to do all my analysis workflow within R.

@privefl I think you use C++ to touch the low layer and R is called and used as the interface to perform biology task? I thought this group would be three members only. Below the mean (108/9).

I think I'll be reassigned to this team because Project 7 has been cancelled.
@zhenyisong Yes, I use some C++ code to perform specific operations more quickly, but the interface is all in R.

Hi All,
I'm Peter Zhang.  I am a post-doctoral fellow at Genome Sciences Centre.  My current projects involve doing genomic analyses on microarray & sequencing data from Cancer and normal tissues.  I will be attending Hackseq in person.
Nice to meet you all!
Peter


How to remove a pipeline from a channel

Hi I can remove subscriptions easily, but there doesn't seem to be a way to remove a pipeline from a channel...

@miles1302 Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation.
Here are a few options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot

Also, please refer to documentation on Channels.


"Exception: SystemStackError: stack level too deep" on big schema trees

This can be reproduced by trying to validate any valid JSON against Azure's ARM JSON Schema at:
https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json
The call:
JSON::Validator.validate!(ARM_SCHEMA, json)

Will end with:
Exception: SystemStackError: stack level too deep
--
0: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `=~'
1: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `!~'
2: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `scheme='
3: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:799:in `block in initialize'
4: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2355:in `call'
5: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2355:in `defer_validation'
6: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:796:in `initialize'
7: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2228:in `new'
8: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2228:in `dup'
9: .../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/util/uri.rb:65:in `parse'

Debugging it a bit I counted 926 different URIs this ARM templates include in their subtree before the failure.
They might include cycles making the validator loop or recurse forever, or it might just be too many, but the fact is that the validator chokes on this input ALWAYS when trying to duplicate yet another re-visited URI.
In my tests this happens after the 926 different URIs seems to be a stable number, so no other new templates are being found yet the validator keeps on running, until it blows up the stack.

Thanks for the detailed bug report. Would it be possible for you to post in a longer stack trace? Stack level too deep errors are usually formed by unterminated recursion, but it's hard to see where that's occurring.
If you don't have the stack trace to hand then I'll try to reproduce using the instructions you gave above

I was using wtf! and could not figure out how to get more lines, that is the 10 I got. Forgive me, but I am a Ruby newbye and there might be a better way I don't know about.
I found that even as json-schema was correctly discriminating already visited URIs from new ones, BUT it would still do a dup to clone the URI object and that would call the schema checking method in which the "stack level too deep" error is always triggered from. I assume it could be that the validator or reader keeps visiting already processed URIs and thus never finishing the processing.
I still have a branch to try this if you need me to, but I think it will be useful that you try to reproduce on your side with a clean minimal sample. If that does NOT fail for you I'd like to see that code.

Ok no worries, I'll try to reproduce and see if I get the same result for your example.
Could you possibly give me some sample json to test against that schema? (Will make it easier for me to reproduce the problem)

aha! As I suspected a simple empty json "{}" doe sthe trick as this happens on schema loading, validation of the json data is not even started...
[1] pry(main)> json = '{}'
=> "{}"
[2] pry(main)> require 'json-schema'
=> true
[3] pry(main)> ARM_SCHEMA="https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json"
=> "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json"
[4] pry(main)> JSON::Validator.validate!(ARM_SCHEMA, json)
SystemStackError: stack level too deep
from .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `=~'
[5] pry(main)> wtf!
Exception: SystemStackError: stack level too deep
--
0: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `=~'
1: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `!~'
2: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `scheme='
3: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:799:in `block in initialize'
4: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2355:in `call'
5: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2355:in `defer_validation'
6: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:796:in `initialize'
7: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2228:in `new'
8: .../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2228:in `dup'
9: .../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:217:in `handle_schema'

Ok great, that's helpful, thanks

A colleague hinted me to use _ex_.backtrace instead, and that worked beatifully:
[8] pry(main)> _ex_.backtrace
=> [".../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `=~'",
 ".../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `!~'",
 ".../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:873:in `scheme='",
 ".../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:799:in `block in initialize'",
 ".../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2355:in `call'",
 ".../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2355:in `defer_validation'",
 ".../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:796:in `initialize'",
 ".../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2228:in `new'",
 ".../ruby/gems/2.2.0/gems/addressable-2.5.1/lib/addressable/uri.rb:2228:in `dup'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:217:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:193:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:193:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:193:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:203:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:202:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:202:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:179:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:142:in `load_ref_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:151:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:193:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:179:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:179:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:142:in `load_ref_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:151:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:193:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:179:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:179:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:179:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:179:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:142:in `load_ref_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:151:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:193:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:192:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:190:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:179:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:222:in `handle_schema'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:179:in `block (2 levels) in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:178:in `block in build_schemas'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `each'",
 ".../ruby/gems/2.2.0/gems/json-schema-2.8.0/lib/json-schema/validator.rb:176:in `build_schemas'"
...

Let me know if you need more lines of traces.

So, this is a really interesting issue. What's happening here is that deploymentTemplate.json includes several $refs that refer to Microsoft.Sql.json (eg. here). Microsoft.Sql.json in turn has a lot of refs that refer back to deploymentTemplate.json (eg. (here)[https://github.com/Azure/azure-resource-manager-schemas/blob/master/schemas/2014-04-01/Microsoft.Sql.json#L35]). The json-schema gem is naively trying to follow these refs and falls into an infinitely loop.
Normally I'd say this is a bug in the json-schema gem, but strangely enough the json-schema spec explicitly forbids this kind of thing. If you look at the official spec it says that:

A schema MUST NOT be run into an infinite loop against a schema.. Schemas SHOULD NOT make use of infinite recursive nesting... the behavior is undefined.

I'll see if I can raise an issue with Microsoft about this.

I guess then there are here 2 separate issues:

json_schema should protect itself against cycles, if an URI reference is mentioned again on the same branch, it should then raise an error such as "Invalid Schema tree, can't have reference cycles!" and probably show the cycle or at least mention the repeated reference.

Azure must eventually fix their schemas to be compliant and not have cycles, if they want to use them properly. So yes, an issue raised to them as well seems proper.

What do you think?

Yes that sounds like a good plan. json-schema does already have some protection against cyclic refs but not in this particular case.


Vagrant doesn't recognize variables in configuration section

Issue Type

Bug report

Molecule and Ansible details
molecule, version 2.20.2
ansible 2.8.5
Molecule installation method (one of):

pip

Ansible installation method (one of):

OS package (dnf)

Detail any linters or test runners used:
Desired Behavior
When using a scenario that utilizes vagrant as a driver, boxes are spun up by vagrant through molecule.
Actual Behaviour
When running a test with a vagrant driven scenario, vagrant sends an error that:
Vagrant:
* Unknown configuration section 'synched_folder='.

That error is found in the error log for the box that failed to start (i.e. /tmp/molecule/{{ project_name }}/{{ scenario }}/vagrant-{{ box_name }}.err).  This is after manually copying the create.yml file to the scenario from the master branch.  For what it's worth, I also needed to manually copy over the destroy.yml file, but that one did not throw any errors.
Relevant output of molecule --debug test -s vagrant:
    TASK [Create molecule instance(s)] *********************************************
    task path: /home/ddean/Projects/ansible_role_devdocs/molecule/vagrant/create.yml:8
    <<IP_ADDRESS>> ESTABLISH LOCAL CONNECTION FOR USER: ddean
    <<IP_ADDRESS>> EXEC /bin/sh -c 'echo ~ddean && sleep 0'
    <<IP_ADDRESS>> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/ddean/.ansible/tmp/ansible-tmp-1570225634.7371259-39034765997832 `" && echo ansible-tmp-1570225634.7371259-39034765997832="` echo /home/ddean/.ansible/tmp/ansible-tmp-1570225634.7371259-39034765997832 `" ) && sleep 0'
    Using module file /home/ddean/.python_venv/molecule/lib/python3.7/site-packages/molecule/provisioner/ansible/plugins/libraries/molecule_vagrant.py
    <<IP_ADDRESS>> PUT /home/ddean/.ansible/tmp/ansible-local-18412bvh4qgzu/tmp1dgyfyiy TO /home/ddean/.ansible/tmp/ansible-tmp-1570225634.7371259-39034765997832/AnsiballZ_molecule_vagrant.py
    <<IP_ADDRESS>> EXEC /bin/sh -c 'chmod u+x /home/ddean/.ansible/tmp/ansible-tmp-1570225634.7371259-39034765997832/ /home/ddean/.ansible/tmp/ansible-tmp-1570225634.7371259-39034765997832/AnsiballZ_molecule_vagrant.py && sleep 0'
    <<IP_ADDRESS>> EXEC /bin/sh -c '/home/ddean/.python_venv/molecule/bin/python3 /home/ddean/.ansible/tmp/ansible-tmp-1570225634.7371259-39034765997832/AnsiballZ_molecule_vagrant.py && sleep 0'
    <<IP_ADDRESS>> EXEC /bin/sh -c 'rm -f -r /home/ddean/.ansible/tmp/ansible-tmp-1570225634.7371259-39034765997832/ > /dev/null 2>&1 && sleep 0'
    failed: [localhost] (item=ubuntu) => {
        "ansible_loop_var": "item",
        "changed": false,
        "invocation": {
            "module_args": {
                "config_options": {
                    "synched_folder": true
                },
                "force_stop": false,
                "instance_interfaces": [
                    {
                        "auto_config": true,
                        "network_name": "private_network",
                        "type": "dhcp"
                    }
                ],
                "instance_name": "ubuntu",
                "instance_raw_config_args": [
                    "vm.network 'forwarded_port', guest: 80, host:8080"
                ],
                "platform_box": "generic/ubuntu1804",
                "platform_box_url": null,
                "platform_box_version": null,
                "provider_cpus": 2,
                "provider_memory": 1024,
                "provider_name": "libvirt",
                "provider_options": {},
                "provider_override_args": null,
                "provider_raw_config_args": null,
                "provision": true,
                "state": "up"
            }
        },
        "item": {
            "box": "generic/ubuntu1804",
            "config_options": {
                "synched_folder": true
            },
            "cpus": 2,
            "instance_raw_config_args": [
                "vm.network 'forwarded_port', guest: 80, host:8080"
            ],
            "interfaces": [
                {
                    "auto_config": true,
                    "network_name": "private_network",
                    "type": "dhcp"
                }
            ],
            "memory": 1024,
            "name": "ubuntu",
            "provision": true
        },
        "msg": "ERROR: See log file '/tmp/molecule/ansible_role_devdocs/vagrant/vagrant-ubuntu.err'"
    }

    PLAY RECAP *********************************************************************
    localhost                  : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

ERROR:
An error occurred during the test sequence action: 'create'. Cleaning up.
--> Scenario: 'vagrant'
--> Action: 'destroy'

@nuk380y - I think the issue is in the name of the configuration param that you're using.
synched_folder should be synced_folder
Give that a shot and see if it works as expected.

Molecule Vagrant driver was moved to https://github.com/pycontribs/molecule-vagrant/issues and if this issue is still valid, please raise a ticket there. Thanks.


server connection issue

i have a server connection issue, alot of riot version update but the problem is still there
if i ping matrix.org is everything ok, so my phone reach the server, but riot just show the load bar or circle, loading nothing
is even not about server load because my friends do not have that issue
i'll send you a bug report from riot, i hope you could fix it asap, because this bug make riot unusable

edit: i've made some trials, i've noticed, when i start the program for the first time everything work as should, if i disconnect my wifi/mobile data and after a while i connect them back riot do not connect to the server, if in the menu i tap quit then i reopen, everything work again
then the issue appear when i disconnect my data connection, when i connect it again riot do not connect back to the server, i think he try, but for some reason do not work till i quit and restart the app

dup of #2125 - I'm also suffering from this and it's really annoying :/


Bump dependencies to latest idb-schema and idb-range

Keen to get 0.6 work back underway and in the process of testing 0.6 RC2 in our environment I identified these out of date dependencies.
Not sure if any additional work needs to be done here as there's no release notes for either idb-schema or idb-range so not sure if there's been any API breakages in their respective 3.x major releases.
Also npm test is reporting 0 tests for so not sure if I've broken something there or not?

0 tests are actually not good :)
3.x releases have some breaking changes and the main intention is to move to ES6. So for 0.6 RC2 dep update is not necessary. I'm working on the next release, but there're still some things to do.

0 tests are actually not good :)

Ok cool there must be something broken then, will dig in and have a look.

So for 0.6 RC2 dep update is not necessary.

There are some bug fixes in the 3.x releases though (e.g. the fix to MS Edge/IE support) that I wanted to get. Everything else in our application is working fine on 0.6 RC2.

I'm working on the next release, but there're still some things to do.

How can I help :)?

How can I help :)?

Nice to hear, I think a Skype call will be faster, I'm alekseys.kulikov.

with this pull request, the main problem, that since 3.x it's not possible to call Schema without new, so the fix should be:
exports.schema = function() { return new Schema() }

Struggling to figure out the unit test failure:
Database #on "error"
    ✘ done() called multiple times

The reason it calls 2 times, because<EMAIL_ADDRESS>fixes onerror callback, but treo-websql, still polyfills it https://github.com/treojs/treo-websql/blob/master/lib/index.js#L71
Good news: I'm eventually finishing 0.6.0 and will release it in the end of this week or on next week. Main changes with 0.6.0-rc2:

remove Transaction object (for now). It brings too much inconsistency between browsers, and can't be used really anywhere except chrome
full rewrite with ES6 and CI testing in Saucelabs, that applies to all treo's family modules, for example https://github.com/treojs/idb-schema
remove support for bower and component, now it supports only npm and standalone builds
dependencies upgrade (I close this PR)
treo-polyfill, which fixes all Safari issues, improves IndexedDBShim and fixes IE.

I also defined a goal of the project. The goal of treo is to make IndexedDB mainstream by giving consistent API across all modern browsers.
As usual I need help with documentation and feedback.
I have excited plans for 1.0.0, which should come a couple weeks after 0.6.0.


Implement API key storage via keyring

Implements a really simple API key storage solution so that no keys are committed on accident. This uses python bindings to GNOME keyring which is a pretty standard method of storing secrets.
Opted to use keyring instead of environment or configuration files as keyring supports encryption.
Due to this, we could also store robot credentials using keyring, preventing us from having to specify usernames/passwords or hard-code them. This is on my TODO list.

@Saketspradhan what do you think of this for storing API keys?

Yeah, this is a really good way to manage any keys that we would be using, so as to mitigate any future mishaps from happening

@dcolli23 Do you wanna merge and close it, or should I do it?

Thanks for taking the time to do this @dcolli23! Really appreciate it!

No problem! Happy that it'll be useful. I'll go ahead and squash and merge


Renaming this Repository

In preparation for the release of GEDCOM Version 7 we would like to use the FamilySearch/gedcom repository which is now being used for code relating to parsing GEDCOM.   I have the names and emails of all the contributors so they can be notified of the change 30 days before it happens.   Jimmy Z. suggested naming it GEDCOM5-parsers so that GEDCOM is available for a public version of the next version of GEDCOM and beyond.  Please share thoughts.

I letter was sent to all collaborators that we had emails for that said:
"GEDCOM Parsing Collaborators.
In preparation for the next release of GEDCOM we would like to use the FamilySearch/gedcom repository which is now being used for code relating to parsing GEDCOM 5.5.1.  We will be renaming the repository GEDCOM5-parsers so that GEDCOM is available for a public version of the next version of GEDCOM and beyond. This will be still searchable in GITHUB with the string of “gedcom”. There will also be a note in the readme when the new gedcom repository is created that explains that the repository formally named “gedcom” is now named gedcom5-parsers.

The name FamilySearch/gedcom5-parsers seems consistent with other FamilySearch repositories.


Demo with gridstack in ng-repeat

Demo showing gridstack-angular can't be wrapped in ng-repeat, DND across gridstack container create some bug, (ghost node in Gridstack.nodes)

This ng-repeat implementation will break the column layout


feat: Add features list translations

Description
This PR adds the translations for the homepage's features section.

Cypress tests are updated to pass

Related issue(s)

part of #2039

//cc @magicmatatjahu 🚀

/rtm


Install the Visual c++ 2015 Redistributable in all VMs in the Github Repo

Feature request is to install the Visual c++ 2015 Redistributable in all VMs in the Github Repo.
ASAN has a dependency on the C++ 2015 redist. That means if you run a binary built with ASAN it will look for specific binaries from that redist. Since this impacts every user that uses ASAN it makes more sense to have this done at an instance or github repo level instead of a per-job level.
The reason jobs work today is that OneFuzz fuzzing tasks are ran inside a debugger which has access to those binaries so they work. If you RDP to a VM and try and run a fuzzer from the CMD it will fail to find the required binaries. Adding this to all VMs will improve the user debugging experience if they ever need to RDP into VM along with reducing the number of binaries that need to be shipped with every job.

This should work like Install-LLVM:
https://github.com/microsoft/onefuzz/blob/e2e44ace8a722d70dfe09fb45c9908d10ef15394/src/runtime-tools/win64/onefuzz.ps1#L114-L122

Should we install the x86 or x64 version of the redistributable and where should we get the installer? I used the web portal to get a URI but I'm concerned it could change and we don't want the setup script to fail just because the redistributable URI is not accessible, right?
From: https://www.microsoft.com/en-us/download/details.aspx?id=52685
Got the x64 version URI: https://www.microsoft.com/en-us/download/confirmation.aspx?id=52685&6B49FDFB-8E5B-4B07-BC31-15695C5A2143
Thoughts?

Probably both.
Note, choco installs these via a more stable URLs, seen here and here

This has now been completed.


Test 2024 01 03

rework of unit tests... after 1billion commits lol.
Program install details by @KonTy
more microwin fixes by @CodingWonders

@ChrisTitusTech  Let's go!!!

#1384, winutil line 931
Write-Host "File copied to Ventoy drive $($volume.DriveLette)"
probably missing a letter in volume.DriveLetter ?

#1384, winutil line 931 Write-Host "File copied to Ventoy drive $($volume.DriveLette)" probably missing a letter in volume.DriveLetter ?

There. Fixed. Also, why in this PR (from 2 months ago), and not in a normal issue?

#1384, winutil line 931 Write-Host "File copied to Ventoy drive $($volume.DriveLette)" probably missing a letter in volume.DriveLetter ?

There. Fixed. Also, why in this PR (from 2 months ago), and not in a normal issue?

im sorry, im not familiar with github 😅


Relax comparison of websocket URI in WebSocketServerProtocolHandshakeHandler

With https://github.com/netty/netty/commit/68bbd4e9669aab4c29dcc1d23ef331aaa2aee333 a change was introduced, to verify the URI of the request in order to determine if an handshake should be tried.
This does however not work with requests containing a query string. Would it be possible to replace the equals with a startsWith, as this would permit to have individual query strings in the request URI (which is what we do). (I'm talking about WebSocketServerProtocolHandshakeHandler.java:58)

Yes... can you provide a pr?

Am 11.10.2016 um 11:29 schrieb Andreas Haufler<EMAIL_ADDRESS>With 68bbd4e a change was introduced, to verify the URI of the request in order to determine if an handshake should be tried.
This does however not work with requests containing a query string. Would it be possible to replace the equals with a startsWith, as this would permit to have individual query strings in the request URI (which is what we do). (I'm talking about WebSocketServerProtocolHandshakeHandler.java:58)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Awesome, thx for the fast feedback! Sure...give me a minute...

@andyHa thanks! Please be sure to sign the ICLA and use our commit message template:
http://netty.io/icla
http://netty.io/wiki/writing-a-commit-message.html

Hm, now that I'm having a close look I'm not sure if that'd be the right approach. If I change it to startsWith "/websocket" would also match "/websocket/something" - which might be quite suprising...
So there would be three choices:

Use startsWith anyway
Extract the "real URI" e.g. everything before ? or "#" and compare that
Don't change anything and call setUri on the request being passed to the handshaker (which is my workwaround anyway)


Developer console system

I added a full developer console system (ported from Mega Man X++) with support for concommands and convars, autocompletion, as well as some useful example commands. Integration example with fullscreen option on menu. Access with ~. I also simplified the (seemingly unused?) function transferProperties.

I could not figure out how to port the give (spawn entity) command with your entity system, you may want to implement that yourself as it can be very useful.

Interesting, I'll merge if there's nothing else important to change. Also, "transferProperties" was a remnant of a very old version of this engine. It's not used anymore.


multiprocessing.Pool related tests occasionally fail in github actions

For now, they are:

tests.test_multiprocess.TestMultiprocessing.test_multiprocess_pool
tests.test_regression.TestIssue58.test_issue58

I can't reproduce this locally. It's probably a racing issue somewhere. We have not gotten any bug report from the users yet and I've put some efforts in fixing it but failed(I think I improved it a bit).
Anyone is welcome to give it another try, but if you found your tests failed on these tests, it's okay, that's not introduced by your changes.

This is because of https://github.com/python/cpython/issues/101975. It's fixed in 3.12 and we had a work around in #315.


chore(deps): bump https://github.com/jenkins-x/jx-cli to 3.0.212

Update jenkins-x/jx-cli to 3.0.212
Command run was ./promote/main

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jenkins-x-labs-bot
You can assign the PR to them by writing /assign @jenkins-x-labs-bot in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gke
6c74e3c2fac5f57e2ef822bfa07da560c6b6e218
link
/test gke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Example oneview_id_pools_ipv4_range.yml does not work

Scenario/Intent
The example oneview_id_pools_ipv4_range.yml does not work with definition of startAddress and endAddress.
To make it work, you have to replace it with:
startStopFragments:
- {
startAddress:             <IP_ADDRESS> ,
endAddress:               <IP_ADDRESS> ,
fragmentType:             FREE
}
Environment Details
Module Version: 5.9.0
Ansible Version: 2.9
OneView Appliance Version: 5.4
OneView Client API Version: 2000
Python Version: 2.7
python-hpOneView SDK Version: 5.5.0
Platform: Linux distribution
Steps to Reproduce
Use the example
Expected Result
ip range created
Actual Result
error in ip range

Hi @DungKHoang, Currently we are not supporting "oneview_id_pools_ipv4_range" resource for latest API versions.
The existing example is not expected to work since it is validated only till API300.
The user have to modify the example file accordingly with recent changes to make it work.
Please refer to below provided support matrix.
https://github.com/HewlettPackard/oneview-ansible/blob/master/endpoints-support.md

We will take this as an enhancement request and will fix it in next release.

id_pools_ipv4_range resource is refactored and also updated examples are merged to master. Please pull the master branch.


DrawIO Diagrams

This isn't really a feature request, the idea works out of the box. This is just a prompt to say if you would like to promote it within the template as a feature. It is VSCode specific though.
Typically the workflow for building diagrams is as follows, go into an external tool/website modify a proprietary format like XML then export into the image format needed for visualising on the web. This is tedious and repetitive work and requires storing two versions of essentially the same thing which can get out of sync.
Solution
DrawIO VSCode Extension
By using the above extension you can edit .drawio.svg files and save them which creates a valid SVG file which the image component can load and display correctly.
This is how I've integrated it so far.
<Image alt="HeaderImage" src="/static/diagrams/map-reduce.drawio.svg" width={350} height={120} />

I also wanted to say this project is fantastic thank you for your work on it!

This is a very handy integration, will be using it for subsequent projects. Much better than modifying and exporting from the drawio. Thanks for sharing!


HoodieRealtimeInputFormat does not apply application specific merge hooks

HoodieCompactedLogRecordScanner scans all the logs and creates a compacted lookup map for compaction and record reader.
Today it just replaces newer records with older records and does not apply the application specific preCombine, today the payload is assumed to be HoodieAvroPayload (which does the replace on preCombine).
cc @vinothchandar

@n3nash I think it does now.. Can you confirm and close this?

At the moment we get full change logs so even no precombine works fine : https://github.com/uber/hudi/blob/master/hoodie-hadoop-mr/src/main/java/com/uber/hoodie/hadoop/realtime/RealtimeCompactedRecordReader.java#L104 but this issue still exists.

Moved to https://issues.apache.org/jira/browse/HUDI-71


[New Port Request] Version 6.2.5 of Qt

Library name
Qt (all open source modules)
Library description
No response
Source repository URL
https://download.qt.io/official_releases/qt/6.2/6.2.5/single/
Project homepage (if different from the source repository)
https://qt.io
Anything else that is useful to know when adding (such as optional features the library may have that should be included)
Add version 6.2.5 of all available open source Qt modules.

Qt is at 6.5.2. vcpkg won't backfill commercial LTS versions of Qt.

@Neumann-A FYI - jom 1.1.4 was officially released by Qt Company.
https://download.qt.io/official_releases/jom/
https://mirrors.ukfast.co.uk/sites/qt.io/official_releases/jom/changelog.txt


Personabar is missing after installing dnnsharp AF

Description of bug
Provide a clear and concise description of the bug.
Steps to reproduce
List the precise steps to reproduce the bug:

start with a dnn804 install
upgraded to dnn950rc1
looks fine, can add content, install open content module, add pages: No problems
install AF DnnSharp.ActionForm-05.01.03-Install.Hotfixes.

After this installation the personabar was no longer visible with the following errors:

Affected version

[X ] 9.5.0 rc1 build

Affected browser

[x ] Chrome

@bogdan-litescu @dimarobert Do you have a version of Action Form available that @schotman can test on the DNN 9.5.0 RC1?  Or, @dimarobert, does #3544 need to land before DNN Sharp modules can work?

Tested an internal build of AF against the nightly build of DNNplatform.
This worked, that is, some basic tested showed no problems with the module (apart from a package install error, IIS, see screenshot).
The nightly build contains the pull request from @dimarobert which made it work I suppose.

@schotman
DNN 9.5.0 has been released yesterday, please test against this version.

solved


Using a package name that starts with volto causes plone/generator-volto to fail

@SaiRev0 it looks like this error happens when the package name starts with volto. I also saw this error:
/tmp/voltonew$ yarn start
Internal Error: voltonew@workspace:.: This package doesn't seem to be present in your lockfile; run "yarn install" to update the lockfile
    at OR.getCandidates (/tmp/voltonew/.yarn/releases/yarn-3.2.3.cjs:435:5209)
    at Bd.getCandidates (/tmp/voltonew/.yarn/releases/yarn-3.2.3.cjs:391:1281)
    at /tmp/voltonew/.yarn/releases/yarn-3.2.3.cjs:439:7764
    at Tg (/tmp/voltonew/.yarn/releases/yarn-3.2.3.cjs:390:11154)
    at ce (/tmp/voltonew/.yarn/releases/yarn-3.2.3.cjs:439:7744)

Really in this situation, when running yarn install, it starts to work.
Until the issue is fixed we need to warn users on https://training.plone.org/volto/bootstrap.html with the following:
"Do not name your project starting with volto, as this will cause plone/generator-volto to fail."
Originally posted by @wesleybl in https://github.com/plone/training/issues/715#issuecomment-1448126874

It's nice we found out a bug, we need to fix this issue. What according to you I causing this error??
I will also try to find the cause of the error

@stevepiercy For the time being we should add a note as you said. So I am making a pr for adding that note

We should add that note between these 2 lines.
Will that be good?

@SaiRev0 please read https://meta.stackoverflow.com/questions/285551/why-should-i-not-upload-images-of-code-data-errors applies to any text as image.
I absolutely refuse to respond to any text as image for those and other reasons. Instead submit a text-only suggestion, or better yet, a PR with your proposed change. Thank you!


Use worker for asset size migration

In 16e323e we added a rake task to set the size field for all
existing assets. When we ran the task in integration however, we
estimated that it would take around 12 hours to complete. This runs
the risk of the rake task being killed and leaving the database in a
somewhat inconsistent state.
This PR moves the work of the rake task into a worker. Hopefully
this will improve the run time as the workers run with concurrency,
and the rake task that queues up the jobs will complete more quickly.

Thanks @floehopper - I've addressed your two suggestions in two new commits, thank you!


you should remove removeObserver

in  SKSplashIcon
-(void)dealloc
{
[[NSNotificationCenter defaultCenter]removeObserver:self];
}

Nice catch, thanks for letting me know. I just pushed a commit that fixes this.

Does the version 0.1.2 implements it? because I don't see it there :cry:


Make AU_SI_RESOLUTIONS type a single literal type w/ two options

This allows typing.get_args to return ("25", "12"). This gets used in the seaice_ecdr.

This is one of those tricky questions.  I see three considerations:

I could be wrong, but my experience is that if we hard-type these as exactly "25" and "12", then we can't pass a variable for this parameter.  Instead, it has to be the string "25" or "12".  There are workarounds for this, but...everything I've used is rather clumsy.
Frustratingly, the "actual" resolutions for these grids are "25km" and "12.5km".  But...the convention they adopted is to drop the fractional part of the grid resolution.  I suppose this is more of a problem for the EASE2 grid where both a 12.5km and a 12.0km are used.  But it's still a bit maddening.
In general, we will want the pm_icecon repository to be able to use all of the AU_SI grids.  And in addition to the 25 and the 12(.5), there is also a 6(.25) km grid.  Perhaps it is best to allow that as a possible source here?

This is one of those tricky questions. I see three considerations:
1. I could be wrong, but my experience is that if we hard-type these as exactly "25" and "12", then we can't pass a variable for this parameter.  Instead, it has to be the string "25" or "12".  There are workarounds for this, but...everything I've used is rather clumsy.

All tests are passing right now. This is more of a safety feature to ensure that our code isn't passing unexpected strings around.

2. Frustratingly, the "actual" resolutions for these grids are "25km" and "12.5km".  But...the convention they adopted is to drop the fractional part of the grid resolution.  I suppose this is more of a problem for the EASE2 grid where both a 12.5km and a 12.0km are used.  But it's still a bit maddening.

Yeah, understood. Ultimately we need a better way to represent the selection of a grid of a given size. I expect this to evolve/change.

3. In general, we will want the pm_icecon repository to be able to use all of the AU_SI grids.  And in addition to the 25 and the 12(.5), there is also a 6(.25) km grid.  Perhaps it is best to allow that as a possible source here?

Right, currently we don't support a 6.25 km grid, but eventually we should be able to.
For now, this was necessary to get unblocked on work in seaice_ecdr. We can address this more holistically later!


Provide the number of organization users in the dataset and builder pages

In order to avoid an unnecessary request to users endpoint.
Changes in frontend and backend, I feel. 💋

@nobuti What exactly do we need here? Just a single integer with the number of users the vis has been shared with (including though groups and/or the whole org)?

@javitonino Right now, we are making a call to api/v1/organization/3c7255dd-1eae-4ec8-b8e8-0698248070c6/users in order to get the total_user_entries. I guess that data will be enough, because even we are holding the entire structure, we are using only that data.

I was experimenting a bit with this and groups. We are also doing a request per group to get the number of users (get the user list and remove duplicates).
What about going an step further and giving you the number of users the visualization is shared with, all aggregated. This way you don't have to request the groups when loading the builder (I think). But this may complicate things too much when changing the permissions, as you may have to request the groups there in order to keep the count current.
As you know how hard could it be to implement, do you think it might be worth it? Anyway, doing the easy part (what is describe in this ticket) for now.

I think it would be great, at least we can defer the request until the permission changes. But as you said, we can do it in another issue I think.


Vaulty is not loading in the new expansion....

The Lua error reports that you may have been using a deprecated call for loading a WoW interface/AddOn.
Here is what the error text reads:
1x Vaulty/vaulty.lua:1: attempt to index global 'C_Addons' (a nil value)
[string "@Vaulty/vaulty.lua"]:1: in main chunk
Locals:
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index global 'C_Addons' (a nil value)"

@avrosati Sorry for the delay here, I haven't played Retail in a while. I wasn't able to replicate the C_Addons error you're getting, but I was getting a very similar error for LoadAddOn which has been deprecated in the new expansion. I updated it to use C_AddOns which has fixed the error for me and I'm expecting it will resolve what you're seeing as well.
https://github.com/himea-saito/Vaulty/releases/tag/1.4-release


Feat: node merge part 2

Description of change
Notes from the doc https://hackmd.io/qwysqfJrQvmCzJg2HbWjRg addressed here.

MQTT not addressed for the moment.
Changed ComputeFoundryId  to take an AliasId

todo:

[x] Changelog
[x] Python plugin_fetch

Links to any relevant issues
Type of change

Bug fix (a non-breaking change which fixes an issue)
Enhancement (a non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Documentation Fix

How the change has been tested
Describe the tests that you ran to verify your changes.
Make sure to provide instructions for the maintainer as well as any relevant configurations.
Change checklist
Tick the boxes that are relevant to your changes, and delete any items that are not.

[ ] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that new and existing unit tests pass locally with my changes

Some export error currently while yarn build in bindings/wasm
out/lib/types/wallet/prepared-mint-token-transaction.ts:4:19 - error TS2724: '"../.."' has no exported member named 'PreparedMintTokenTransactionData'. Did you mean 'PreparedTransactionData'?

4 import { Account, PreparedMintTokenTransactionData } from '../..';
                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  out/lib/types/client/prepared-transaction-data.ts:16:14
    16 export class PreparedTransactionData {
                    ~~~~~~~~~~~~~~~~~~~~~~~
    'PreparedTransactionData' is declared here.

Found 1 error in out/lib/types/wallet/prepared-mint-token-transaction.ts:4

Some export error currently while yarn build in bindings/wasm
out/lib/types/wallet/prepared-mint-token-transaction.ts:4:19 - error TS2724: '"../.."' has no exported member named 'PreparedMintTokenTransactionData'. Did you mean 'PreparedTransactionData'?

4 import { Account, PreparedMintTokenTransactionData } from '../..';
                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  out/lib/types/client/prepared-transaction-data.ts:16:14
    16 export class PreparedTransactionData {
                    ~~~~~~~~~~~~~~~~~~~~~~~
    'PreparedTransactionData' is declared here.

Found 1 error in out/lib/types/wallet/prepared-mint-token-transaction.ts:4

Could not replicate this btw, maybe you gotta clean your /out folder?


Emit last received log event as normal event, after flush_interval has passed?

Currently the last log lines which are in the buffer are emitted as error event after the flush_interval has passed. This results in the fact that i need to place log handling also in the @ERROR label to handle the last message.
If the flush_interval has passed can the last log event be processed as a normal log line?
An example scenario:

an application boots up and is just waiting to do something, then the last log line will be emitted as error event. But this is not a real error. It is just doing nothing.

You can get timeout errors in your scenario when you use only multiline_start_regexp
But you can use both multiline_start_regexp and multiline_end_regexp if you know what format is your logs.
I will implement timeout events as an arbitrary label, when I understand how to emit such a event.

In the current case it is very difficult to determine what the last log line would be, we know for sure what the first line would be. So currently we have setup up a multiline_start_regexp that is always consistent. We catch all information between the start lines
Example:
2014-03-05 10:57:51.112  INFO 45469 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet Engine: Apache Tomcat/7.0.52
2014-03-05 10:57:51.253  INFO 45469 --- [ost-startStop-1] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2014-03-05 10:57:51.253  INFO 45469 --- [ost-startStop-1] o.s.web.context.ContextLoader            : Root WebApplicationContext: initialization completed in 1358 ms
2014-03-05 10:57:51.698  INFO 45469 --- [ost-startStop-1] o.s.b.c.e.ServletRegistrationBean        : Mapping servlet: 'dispatcherServlet' to [/]

It would be nice if at certain moment the last log line would be emitted as normal event instead of an error.

I've added timeout_label option at d8c433102
@mpas could you try it using master HEAD?
For example,
<source>
  @type forward
</source>

<filter docker.*>
  @type concat
  key log
  stream_identity_key container_id
  flush_interval 5s
  n_lines 2
  timeout_label @TIMEOUT
</filter>

# handle errors
<label @ERROR>
  <match docker.*>
    @type stdout
  </match>
</label>

# handle timeout events
<label @TIMEOUT>
  <match docker.*>
    @type file
    path /tmp/timeout.log
  </match>
</label>

# in normal case
<match docker.*>
  @type stdout
</match>

I tested the fix and it seems to work! Thanks for the modification. Please let me know when this gets into a final release.

Released v0.5.0


"Using nginx snippets" notification could have improved formatting

Is there an existing issue for this?

[X] I have searched the existing issues

Output of ddev debug test
NA
Expected Behavior
ddev could report nginx snippets in a more readable fashion (?):
Using nginx snippets: [
  /Users/diego/some-project/.ddev/nginx/some.conf,
  /Users/diego/some-project/.ddev/nginx/some-other.conf
]
Custom configuration, including snippets, is only updated on project restart.
Run `ddev restart` if you do not see your configuration in effect.

Of course, the above could be smarter about other snippets or servers. I'm not familiar with other setups.
Actual Behavior
ddev reports nginx snippets like:
Using nginx snippets: [/Users/diego/some-project/.ddev/nginx/some.conf /Users/diego/some-project/.ddev/nginx/some-other.conf]
Custom configuration is updated on restart.
If you don't see your custom configuration taking effect, run 'ddev restart'.

Steps To Reproduce

Use a snippet in .ddev/nginx
Restart the project
Message is printed in hard to read format

Anything else?
See: https://github.com/ddev/ddev/blob/master/pkg/ddevapp/config.go#L613

A PR is welcome. Snippets are little-used and were scheduled for removal, but people liked them so they're still around.
If you aren't interested in doing a PR I doubt this will be addressed.


refactor(storagenode): clarify comments of proto/snpb.LogStreamCommitResult and internal/storage.CommitContext

What this PR does
This patch clarifies comments of proto/snpb.LogStreamCommitResult and
internal/storage.CommitContext.

Current dependencies on/for this PR:

main

PR #329   👈

This comment was auto-generated by Graphite.

Codecov Report
Base: 63.22% // Head: 63.27% // Increases project coverage by +0.05% :tada:

Coverage data is based on head (f9f95a5) compared to base (de25143).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #329      +/-   ##
==========================================
+ Coverage   63.22%   63.27%   +0.05%
==========================================
  Files         130      130
  Lines       17456    17456
==========================================
+ Hits        11036    11046      +10
+ Misses       5868     5859       -9
+ Partials      552      551       -1

Impacted Files
Coverage Δ

internal/storage/commit_context.go
100.00% <ø> (ø)

internal/metarepos/report_collector.go
77.42% <0.00%> (ø)

internal/metarepos/storage.go
80.08% <0.00%> (+0.29%)
:arrow_up:

internal/storagenode/logstream/executor.go
79.67% <0.00%> (+1.20%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Hurricane Sandy Inundation DEM

https://www.ngdc.noaa.gov/mgg/inundation/sandy/sandy_geoc.html
I was looking around NOAA's site for bathymetry and found some interesting, recent, high-res data taken after hurricane Sandy. Seemed like a quick thing to get and would let us practice ordering/priority on data that has equivalent resolution.

Listing files
curl -s https://www.ngdc.noaa.gov/mgg/inundation/sandy/data/tiles/zip19/ | \
    grep -o '<a href=['"'"'"][^"'"'"']*['"'"'"]' | \
    sed -e 's/^ mgg_inundation_sandy_listing.txt

Mirroring files
cat mgg_inundation_sandy_listing.txt \
    | xargs \
      -I {} \
      -P 24 \
      -n 1 \
      sh -c 'export f="{}"; export s3="s3://elevation-sources-prod/mgg_inundation_sandy/`basename $f`"; curl -s $f | AWS_DEFAULT_PROFILE=openterrain aws s3 cp - $s3; echo $s3' \
    tee mgg_inundation_sandy_s3_objects.txt

Transcoding files
cat mgg_inundation_sandy_s3_objects.txt | \
while read filename; do
    bn=$(basename $filename)
   make submit-job job=aws/transcode-job.json.hbs input=${filename} output=s3://elevation-sources-transcoded/mgg_inundation_sandy/$(sed 's/\.tif//' <<< $bn) name=$(sed 's/\./_/' <<< $bn)
done

Done transcoding, footprints inserted into database.

Neat! Are these bare earth? Or do they include building and tree shapes?

On Jun 10, 2017, at 05:32, Ian Dees<EMAIL_ADDRESS>wrote:
Done transcoding, footprints inserted into database.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

When I was looking at it in QGIS it looked like bare-earth, but in hillshade it looks like they didn't do a great job removing buildings in Manhattan:

Beautiful data, but we'll probably need to remove this else it conflicts with our general "bare earth" policy?

If it gets prioritized beneath NED 1/9 (and that doesn't include bathy), it could potentially get used as bathymetry only by being masked.

So if the algorithm says "below NED 1/9th" then keep it in, else we either need to manually curate it below NED 1/9th or remove it?


Access to Slack workspace

Catch 22. From the registration email message:

We are using Slack for system access questions and password issues:
Click this link to add yourself to the Open Mainframe Project Slack workspace. Within this workspace, add the cobol-programming-course channel.

But that link takes you here. What do you do if you don't have an email address at any of the four domains named in the "If you have ... you can create an account" instructions?

At this link you have to enter your email and than you can sin up for the slack https://slack.openmainframeproject.org/

Thanks. Unfortunate that the link in the registration email message doesn't take you to that page. :


node-sass compilation fails on Windows - node_version.h not found

NPM version (npm -v): 6.14.5
Node version (node -v): 14.4.0
Node Process (node -p process.versions): 14.4.0
Node Platform (node -p process.platform):  win32
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"): ^5.0 (trying to install, latest)
npm node-sass versions (npm ls node-sass): ^5.0 (trying to install, latest)

So, I installed Windows build tools, and set npm config (nodedir (node_headers) and msvs_version=2019).
node_version.h is available in "nodedir", however I get this error:
"c:\development\luci\luci\node_modules\node-sass\build\binding.sln" (default target) (1) ->
"c:\development\luci\luci\node_modules\node-sass\build\binding.vcxproj.metaproj" (default target) (2) ->
"c:\development\luci\luci\node_modules\node-sass\build\binding.vcxproj" (default target) (4) ->
(ClCompile target) ->
  c:\development\luci\luci\node_modules\nan\nan.h(24,10): fatal error C1083: Cannot open include file: 'node_version.h': No such file or directory [c:\development\luci\luci\node_modules\node-sass\build\binding
.vcxproj]
    48 Warning(s)
    1 Error(s)

It should be able to pull down the pre-built binaries? If you're trying to do something "offline", it's probably the same as https://github.com/sass/node-sass/issues/2097

It should be able to pull down the pre-built binaries? If you're trying to do something "offline", it's probably the same as https://github.com/sass/node-sass/issues/2097

Can you show how did you exactly did that: "set npm config (nodedir (node_headers) and msvs_version=2019)." ? How does your npm configuration look like now?

Hi,
Sorry, cannot recall what I eventually did. I had to fix our TFS pipeline, and use NPM instead of git clone, what we used before.
You know the thrill, in the middle of the heat a lot of things were going wrong, and I needed to sort out a lot of things.
I believe in the end I installed the NPM headers via vs_buildtools, which solved it, and I forgot to close the issue.
Indeed we cannot get the pre-built binaries, since we are behind a firewall.


Plan Quint Learning Session for Polymer team

[x] Gather input on current problems async
[x] #27
[x] Hold sync preliminary input session
[ ] Refine planned curriculum from input

Polymer would like to have their session next quarter, which we will be pleased to support.


How to build a great autocomplete / autosuggest ?

Autosuggest using the index.match and how to use the nGramLength when adding documents to get more words for the autosuggest.

Link to resource trade-off on nGramLength.
Doc already exists, but is removed from readme.md because it's not finished.


State Registration Memory Consumption

When working with many state definitions (1000+) we're noticing huge memory consumption caused by UI Router.
For example, modifying stateSpec.js to include an additional 10000 simple states causes the memory to balloon considerably. This is a problem for larger applications that have very large test suites.
$stateProvider.state('root.sub2', {url: '/2?param2' });

for( var i = 0; i < 10000; i ++) {
  $stateProvider.state('iState' + i, {url: '/Statei' + i});
}

$provide.value('AppInjectable', AppInjectable);

Memory consumed continues to climb past 3 GB

Could someone help me understand why UI Router is allocating so much memory?
Tested against:
Node 4.4.7 & Node 5.10.0
Karma 0.12.37
UI Router 0.3.1 (haven't been able to build the master branch successfully, perhaps someone can test there)
Possibly related to #545

(haven't been able to build the master branch successfully, perhaps someone can test there)

run ./scripts/package.sh ng1 and find the package built in ./build_packages/ng1/

Thanks @christopherthielen, the problem seems worse in the master branch.
I had to reduce the sample size to 1000 states instead of 10000. With the latter, the test suite would simply crash after a second or two and disconnect. With 1000, memory continues to grow into the several GBs.
Any thoughts as to why this is happening?

No I'm not sure why registering a state would take up so much memory. I'll try to look into it when I have some time.
Have you tried finding what's taking the memory using dev tools profiler, etc?

+1

@christopherthielen any progress on this, we are finding the same issues

For example, modifying stateSpec.js to include an additional 10000 simple states causes the memory to balloon considerably.

@danielneri @jkevinburton Are you finding this bloat in production apps, or only during unit testing?
Each run of a unit tests, creates a new angular execution context and a new ui-router instance.  The router, all registered states (and likely all of angular) are probably being retained in some way by karma.
Running a simple test in the browser shows that each state takes up about 5k, which is a reasonable amount: http://plnkr.co/edit/LqZ6OwzXXJaGg42XLeyn?p=preview
I started a profiler, clicked "add 1000 states" a few times.  Each purple vertical line represents memory allocation of 1000 states, which is a bit over 5MB:

By selecting a section of the timeline, we can isolate the memory allocation of a batch of 1000 states.  Each state takes up about 5,000 bytes:

I have a same issue. @danielneri-accesso have you found some workaround this in unit tests?

It seems that router leaks memory because lot of their classes keep reference to each other and it never gets cleaned, probably some circular references get created. This seems to help A LOT:
var clearAllMembers = function(obj, depth) {
	depth = depth || 0;
	if (depth > 10) {
		return;
	}
	var prefix = '';
	for (var j = 0; j < 4 * depth; j++) {
		prefix += ' ';
	}
	for (var i in obj) {
		if (obj.hasOwnProperty(i)) {
			//console.log(prefix + String(i) + '(' + typeof(obj[i]) + '): ', obj[i]);
			if (typeof(obj[i]) == 'object') {
				clearAllMembers(obj[i], ++depth);
				if (obj && obj[i]) {
					if (obj[i] instanceof Array && obj[i].length) {
						obj[i].splice(0);
					}
					delete obj[i];
				}
			}
		}
	}
}

$rootScope.$on('$destroy', function() {
	clearAllMembers($stateRegistry);
	clearAllMembers($urlRouter);
	clearAllMembers($urlService);
	clearAllMembers($state);
});


Obtuse Error in Test Reporting

Affected Workflow Run
We've run into an odd bug when trying to report a passing test. Judging by the error trace, it's failing when trying to compare to previous runs? See the full PR.
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/logging/__init__.py", line 1697, in isEnabledFor
    return self._cache[level]
KeyError: 10
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/action/publish_unit_test_results.py", line 386, in <module>
    settings = get_settings(options, gha)
  File "/action/publish_unit_test_results.py", line 331, in get_settings
    commit=get_var('COMMIT', options) or get_commit_sha(event, event_name, options),
  File "/action/publish_unit_test_results.py", line 165, in get_commit_sha
    logger.debug(f"action triggered by '{event_name}' event")
  File "/usr/local/lib/python3.8/logging/__init__.py", line 1433, in debug
    if self.isEnabledFor(DEBUG):
  File "/usr/local/lib/python3.8/logging/__init__.py", line 1705, in isEnabledFor
    level >= self.getEffectiveLevel()
TypeError: '>=' not supported between instances of 'int' and 'str'

Using these settings
  with:
    files: ./tests-smoke-report.xml
    github_token: ***
    check_name: EVM Smoke Test Results
    comment_mode: always
    github_retries: 10
    fail_on: test failures
    time_unit: seconds
    ignore_runs: false
    hide_comments: all but latest
    job_summary: true
    compare_to_earlier_commit: true
    pull_request_build: merge
    check_run_annotations: all tests, skipped tests
    seconds_between_github_reads: 0.25
    seconds_between_github_writes: 2.0
    json_thousands_separator:
  env:
    AWS_DEFAULT_REGION: ***
    AWS_REGION: ***
    AWS_ACCESS_KEY_ID: ***
    AWS_SECRET_ACCESS_KEY: ***
    AWS_SESSION_TOKEN: ***
    KUBECONFIG: /home/runner/work/_temp/kubeconfig_1656612353469
    CHAINLINK_COMMIT_SHA: 8846d5c50eaf1cbb0b1580a144112c40fb125dd1
    CHAINLINK_ENV_USER: kalverra
    TEST_TRIGGERED_BY: core-CI
    LOG_LEVEL: debug

Yes, log levels are case sensitive, it should be DEBUG. I have fixed the case-sensitivity and improved the error message. Should be fixed in next release.


Add note on diff's n differing from pandas

This surprised me so I thought worth calling out.
Ref https://github.com/pydata/xarray/pull/3800

I guess pandas now calls this periods? https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.diff.html

Oh good spot @dcherian . I'll add that to the note

Updated

Thanks @max-sixty

Ended up being more from you than me @dcherian :)


when using ./release/dataTable.js there is still babelHelpers is not defined

Uncaught ReferenceError: babelHelpers is not defined
(anonymous function) @ dataTable.js:81
(anonymous function) @ dataTable.js:143
(anonymous function) @ dataTable.js:16
(anonymous function) @ dataTable.js:19

duplicate of #111

This issue is not a duplicate of #111.
When we add your dependency to our projects, regardless of the browser, we have this error.
You are using the babel helpers in your code, but somehow it is still present in the release file.

You don't have to use the babel compiled version../release/dataTable.es6.js - Raw ES6 Version.

Well, the purpose of Babel is to compile ES6 syntax into a JavaScript we can use write now.
I tried to use the ES6 instead of the compiled version and the browser doesn't recognize the syntax.
So yes, we have to use the compiled version.
We shouldn't have this error, it comes out of the box when you install the dependency via bower.
Do you have any idea how to fix it?


Altair client can not upload an image to Strapi

Current Behavior

I use Altair client to upload an image to my collection type in Strapi as GraphQL Playground currently does not support file upload. I inserted correct GraphQL query on Altair client but somehow the loading process took very long (not succeed until now).
Loading process takes very long and I am unable to upload an image to Strapi :

I retried on another occasion but the result was same.
You can see this issue happening on minute 34:44 on my YouTube Video.

Steps to Reproduce (for bugs)

Install the Altair graphql client latest version on Ubuntu 20.04 using snap install altair.
Double click the app and open.
Run Strapi on terminal using yarn develop. Then Strapi will be running on http://localhost:1337.
Set http://localhost:1337/graphql as URI.
Insert mutation query based on docs on Altair client, provided by Strapi.

The documentation on Altair client, provided by Strapi :

This is the mutation query to upload :

Choose an image to upload.
Set Headers (JWT)

This is the header I set :

Send request to Strapi ( http://localhost:1337/graphql ).

Although I have set Public role to be able to upload to Strapi (no need to set headers for authorization), I still can not upload to Strapi.
Whole Image of my Altair client :

Environment

Application Type : Altair GraphQL Client (Desktop) v2.4.11
OS : Ubuntu 20.04
Strapi : v3.0.1
Node : v14.6.0

Hey @kevinadhiguna, I went through the video you sent. I don't use strapi personally so can only comment with reference to Altair itself. It's not very clear what happened when it kept loading. I would suggest the following approach to debugging this:

open up the developer tools in Altair first before sending the requests (so all the logs are captured)
after sending the request, check the Network tab in the developer tools for the request being sent. My first suspect to the issue is that the request sent never gets resolved and so Altair keeps waiting (loading).
if the network request gets resolved (or no network request was sent in the first place), the next suspect would be a runtime error while sending the request. You can check the Console tab for any new error logs that appeared after sending the request.

Hope that helps.

Closing this issue, as it appears to have been solved.

Since you using Strapi, can i ask a question ? im have a mutation createUser with username, name, email, password and images as input. But when im trying to run mutation, images always returning null. Here the documents and mutation, HiinhAnh is images with type UploadFile

@akiiii29 Hello, sorry for late reply. I think  that is because you are missing Upload!.
I made a video tutorial about how to upload :

an image to a single field in Strapi
multiple images to a single field in Strapi

using Altair client. Kindly watch it if you don't mind.


docs(example): add an example of using useMatches to access loader data across your application

Creating a useful example for the examples collection. It showcases the usage of useMatches to access loader data across the Remix application.
Motivation: With Remix, you don't need global React contexts anymore to access your
React state. Instead, you can use the useMatches hook to access the loader
data across your application.
PS: Remix rocks!

You can review this example in codesandbox: https://codesandbox.io/s/usematches-loader-data-2h798

@kentcdodds please review this and merge if you like it or request changes :)


README: fix image paths

Fix typos in the image paths

Thanks for the pull request.
I'd rather see a fix of the file name typo than an introduction of another typo.

@keyboardsurfer Thanks! I have made the required changes :smiley:

Oops, I just came here to pull request my fork fixing the same little issue 😄 .
Ping to get this checked on in.


Add support for formatting value as arg to resource string

I often find that I have an observable value and the action is to format the value using a string resource and set a text view's text with the formatted text. I usually do a map to do the formatting and then subscribe with an RxTextView.text action. But wondering if it would be valuable to support this officially with a single action method in RxTextView as in:
public static Action1<? super Object> textFormat(@NonNull final TextView view, @StringRes int format) {
	return new Action1<Object>() {
		@Override public void call(Object value) {
			view.setText(view.getContext().getString(format, value));
		}
	};
}

I can see valid arguments against it (do you also do it for other text actions? What about if value is an array that represents multiple args?), but thought I should at least propose it for discussion.
Perhaps a better alternative is just a creator of a function for map to do formatting something like this:
myObservable
    .map(RxContext.format(this, R.string.myFormat))
    .subscribe(RxTextView.text(myTextView));

I think this is out of the scope of this project. RxBinding is bindings for ui widgets/components, whereas this is more of something that would be appropriate for a sort of hypothetical "RxResources".

Your arguments against it are also mine. I would like to see it experimented with in a standalone project since it has uses beyond just with RxBinding's text actions. Plus it lets the implementation evolve more rapidly to potentially correct those problems (and other unforeseen one).
If you do give it a shot, put a link here so I can look. Otherwise I don't think it belongs in the library since it's purely resource focused and has uses aside from just directly binding to one of the provided actions.


slot "noResult" is not working

hi,
When I'm using "noResult" slot with ":taggable: "true" then it's not showing the template inside the noResult slot.
I'm not sure why it's not working with taggable while in rest of the cases it works fine.
Can anyone have a workaround for this?

Is it showing default List is empty text?
If so, try using noOptions slot instead.

this issue still exists
@ravipatel2293  Have you solve this issue?

As @kyrsquir said, i have used noOptions slot to achieve desired outcome.

<VueMultiselect v-model="departmans" :options="optionsdata" :multiple="true" group-values="libs" group-label="tumunusec" :group-select="true" placeholder="Type to search" track-by="isim" label="isim">New text</VueMultiselect>
this is not working.

I need to translate the content of "noResult" but it isnt working.

I have the same problem. The slots noResult and noOptions do not seem overridable.

It looks like the original issue of the noResult slot not working has been 'fixed' by using noOptions instead.
@pasamsin To use a named slot, you will need to use a v-slot attribute, ideally on a template element, for example:
<VueMultiselect>    <template v-slot:noResult>       New Text    </template> </VueMultiselect>
Feel free to check out this guide about how to use named slots: https://v2.vuejs.org/v2/guide/components-slots.html#Named-Slots
The other queries are a bit hard to troubleshoot and assist as there aren't many details to go on. I'm going to close this issue, but if anyone has more issues, feel free to open a new issue with a reproducible link - you can use this as a template: https://jsfiddle.net/mattelen/8cyt3hrn/3/


haskell.gtk2hs packages: fix Darwin build

Motivation for this change
The gtk2hs packages (gtk, cairo, pango, glib, gio) currently fail on Darwin. This change includes two layered fixes for these:

a point-in-time override for the current version of all these tools (that can hopefully be backed out after there's a new release and nixpkgs pulls this in)
an additional override for gtk that likely wants to remain indefinitely

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Edit: correct the gtk2hs issue referenced in the commit message

Great, thanks for fixing this up! LGTM.

@GrahamcOfBorg build haskellPackages.gtk
@GrahamcOfBorg build haskellPackages.gtk3
@GrahamcOfBorg build haskellPackages.cairo
@GrahamcOfBorg build haskellPackages.pango
@GrahamcOfBorg build haskellPackages.glib
@GrahamcOfBorg build haskellPackages.gio

Looks like everything built successfully on darwin, thanks for fixing this up!


Integrate Control Plane UI into API Gateway automatically

duplicate of #116

would be a venue API gateway, not the "Unity" api gateway

On venue statup, the control plane needs to hit the API gateway for egress before other pieces of software are available


init plugin before call init()

Is there any way to embed a plugin before run webdriverio init() method through gulp?
I want to init this plugin (https://github.com/chmanie/webdriverajax) before start browser

@ayxos you can use that plugin. Just add it to the plugin object as described here

Does not work. i have include it inside wdio.conf.js but Cannot read property 'expectRequest' of undefined


restrict permissions on files generated by LCA for IBU

/cc @donpenney

I think all we need to do here is make sure the directories we create are 0700 perms and the files are 0600. ie. Just change the permissions for the existing calls

/lgtm

/test integration


[bug]: Lost funds after force close the channel from remote side

Background
I wanted to open a channel from the Hydranode to the Kappa node. Unfortunately, I entered too low a fee and it looked like the transaction would be confirmed at infinity. When I found this out, I tried to delete the transaction from the mempool, but unfortunately, it only deleted the "pending channel" information from the LND on Hydranode. I am now in a state where the transaction https://mempool.space/cs/tx/47b157b734c4ed624c4c378331c484a92c924b6dbb3659dea657ade7256269a3 were confirmed (I have done acceleration of it in cooperation with mempool.space) and I did ask the operator of Kappa (Aaron LRoS - WoS<EMAIL_ADDRESS>to force close the channel from his side. After this step, the fund moved to https://mempool.space/cs/address/bc1qk7tvtq92nc0h2swtfhf9afkjuvk5djyj5dcqk2zxj5tr2nfm9p5st8qpjv, but I can't see it in our LND node wallet. I did rescan the wallet but that step had no effect.
I did try to cancel this channel by command "lncli abandonchannel ...".
Your environment

version of lnd
lnd version 0.18.1-beta commit=v0.18.1-beta
which operating system (uname -a on *Nix)
Linux HYDRAnode 5.10.0-32-amd64 #1 SMP Debian 5.10.223-1 (2024-08-10) x86_64 GNU/Linux
version of btcd, bitcoind, or other backend
Bitcoin Core version v27.1.0

You should never call the cmd abandonchannel if you are not sure!
So I think the only way to recover in your case is the chantools command:
https://github.com/lightninglabs/chantools/blob/master/doc/chantools_sweepremoteclosed.md
because your SCB does not contain the channel anymore, so thats why a recovery via SCB does not work.