Broken cursor support when accessibility is enabled

Testing the multi-touch example.

@jessegreenberg, can you review my fix, and ensure it doesn't break accessibility?

You can test before the commit by building Scenery (npm install, grunt) then viewing the multi-touch example (scenery/examples/multi-touch.html). pointer: cursor didn't seem to be applied.
Looks like the FocusOverlay was "in front", and prevented the cursor from being applied.

Looks good @jonathanolson, thanks for fixing this!  I verified and observed the issue by going through the steps in https://github.com/phetsims/scenery/issues/532#issuecomment-193621877, and the commit above fixes this without breaking anything related to accessibility.  Closing.


After latest update no more FormsPlot.mouseCoordinates method available

Hello!
The latest nuget update broke one of my code part:
private void formsPlot1_MouseClicked(object sender, MouseEventArgs e)
        {
            toolStripTextBox1.Text = $"X: {Math.Round(formsPlot1.mouseCoordinates.X)}, Y: {Math.Round(formsPlot1.mouseCoordinates.Y)}";
        }

Error	CS1061	'FormsPlot' does not contain a definition for 'mouseCoordinates' and no accessible extension method 'mouseCoordinates' accepting a first argument of type 'FormsPlot' could be found (are you missing a using directive or an assembly reference?)

@bukkideme thanks for noting this!
The last update refactored how mouse tracking is accomplished and removal of this line is what broke your code:
https://github.com/swharden/ScottPlot/blob/d12189309d7ca40ea9881e830e3af3ab2e7fc43b/src/ScottPlot.WinForms/FormsPlot.cs#L96
I'll add this back in. In the mean time, you could get your code working by changing your line to:
var coord = formsPlot1.plt.CoordinateFromPixel(e.Location);
toolStripTextBox1.Text = $"X: {Math.Round(coord.X)}, Y: {Math.Round(coord.Y)}";

Just released ScottPlot 4.0.17 on NuGet. It should be live shortly! Let me know if this doesn't do the trick. Thanks again @bukkideme

Thanks it works again!


Missing dependency: react-native-masked-text

I see react-native-masked-text used in AnimatedInput/index.js but not declared in package.json. This is prevents the project from building.
Installation was done using yarn perhaps it's a part of the issue?

I was able to resolve this issue on my end by adding "react-native-masked-text": "^1.13.0" as a dependency for my project. However, I think it makes more sense for this project to include the dependency itself.

Hey man, you're right! Sorry for that! Pushing a new version with the fix :)


apply_styles method on sheet

In my gem SpreadsheetArchitect I have the ability to create axlsx sheets individually. I was wondering if we can get the workbook.apply_styles to also be available as sheet.apply_styles so that I can apply the styling before returning the sheet.

If you work with vanilla axlsx, you probably still need to call axlsx.serialize <my_workbook> when you're done with the whole workbook (all the worksheets included) to have it processed and saved as .xlsx file.  If I understand it correctly, axlsx sets styles on the entire workbook, which is something I can't change.
As far as axlsx_styler goes, I think there's an opportunity to hide the call workbook.apply_styles from the end user. Would it solve your problem? Fell free to use examples to help me understand where your problem is.

I think hiding that might solve the issue. How would it work though?

It's possible that we can patch axlsx.serialize, but I don't know for sure yet.

I like that idea. Make sure to also patch the to_stream method. I use this method instead of serialize so that I don't have to save to a file.

We could do it like this:
module AxlsxStyler
  module Axlsx
    module Package

      original_serialize = instance_method(:serialize)

      define_method :serialize do
        @workbook.apply_styles
        old_serialize.bind(self).()
      end

      original_to_stream = instance_method(:to_stream)

      define_method :to_stream do
        @workbook.apply_styles
        original_to_stream.bind(self).()
      end

    end
  end
end

I read this method of patching from this stackoverflow post http://stackoverflow.com/questions/4470108/when-monkey-patching-a-method-can-you-call-the-overridden-method-from-the-new-i

Thanks for the example. I will look at it some time next week.
In the meantime it would be great to know what is the root cause of your problems. workbook.apply_styles should work, as all styles (even in the original axlsx) are defined on the workbook, not on its worksheets.

Sorry I should have mentioned that its not an issue. I was just wondering if that method could possibly done on the sheet level but you say that's not possible so that's okay with me.

Ah, good. I'm just going to close this one then.

Are you still going to try and hide the call to apply_styles?

I thought to slack away for a bit, but you're puting me on the spot :smile:
Could you please review this change?

Also, if you want to make your own PR, please feel free to do so.


[New Port Request] litehtml

Library name: litehtml
Library description: Fast and lightweight HTML/CSS rendering engine
Source repository URL: https://github.com/litehtml/litehtml
Project homepage (if different from the source repository): http://www.litehtml.com/
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

Please be aware that qttools needs a dependency on litehtml and remove the vendoring of the dependency.

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


sokol_gfx: Clamp to border option for sg_image

Hello, I'd like to discuss possibility of adding clamp-to-border wrap mode and border-color option to sg_image_desc in sokol_gfx. Is this planned? Should I attempt to add it?
I generally use it to render geometric primitives with white border and UV set to -1, -1. It bypasses the need for having a white pixel in texture and simplifies the drawing code.
By my lousy research it seems that WebGL, OpenGL, DirectX and Metal all do support it.

I can't find support in WebGL (there's an GLES2 extension but that doesn't seem to exist for WebGL).
But we can implement it as an optional feature, so:

add a feature bit "image_border_color" (or a better name) to the sg_features struct
add a SG_CLAMP_TO_BORDER enum to sg_wrap enum
add a "float border_color[4]" to sg_image_desc

A PR would be welcome (also if you just implement for a single backend, I can then take over for the others).

What's the strategy for testing the new features? I'm now using only DirectX, and tested it there with my own code. However, so far I have no code running for OpenGL, and Metal is out of my comfort zone. Do we add a sample testing the feature out?

Yes, a simple sample for testing/visualizing the texture addressing modes would be nice, nothing fancy.
Just implement the things you want, and then I can take over.

See: https://github.com/floooh/sokol/pull/209 and https://github.com/floooh/sokol-samples/pull/46
I'll update the documentation and READMEs next (tomorrow or so) and then I think it's ready for merging.

This has now been merged to master.


Tweak tombstones related settings

tombstone_compaction_interval = ttl ?
tombstone_threshold > 0.5 ?

Useless, TWCS and DTCS don't need that


(feat): Linear GENOT

We add two main new classes here:

GENOTLinSolver wraps the underlying OTT-Jax solver in a moscot-usable way
GENOTLinProblem at the next level of abstraction up, allowing users to work with AnnData objects directly while also using other parts of the moscot API like policies

To run this PR, simply do pip install -e . as it points directly at the corresponding OTT-JAX branch.
TODOs:

[x] Finalize status with OTT-Jax PR
[x] Remove more dead code as this was based on the ICNN implementation (if there is any)
[x] Maybe add more tests for certain things that I did not cover?  I will need to look this over
[x] Maybe a small notebook?
[x] Figure out how to squash all these commits.  It should be clear where I picked up and the ICNN branch stopped but in any case...would be nice on the eyes.  And we definitely want to squash this PR when merged

https://github.com/theislab/moscot/actions/runs/9221997646/job/25372233453?pr=662 complains that it can't find diffrax with the minimum version from ott-jax[neural] on python 3.8, and I'm not sure what to make of that since ott-jax tests against 3.8.  That being said, diffrax at the minimum version does not support 3.8 it seems: https://github.com/patrick-kidger/diffrax/blob/v0.4.1/setup.py
Thoughts on this from the Kleins? @MUCDK @michalk8

https://github.com/theislab/moscot/actions/runs/9221997646/job/25372233453?pr=662 complains that it can't find diffrax with the minimum version from ott-jax[neural] on python 3.8, and I'm not sure what to make of that since ott-jax tests against 3.8. That being said, diffrax at the minimum version does not support 3.8 it seems: https://github.com/patrick-kidger/diffrax/blob/v0.4.1/setup.py
Thoughts on this from the Kleins? @MUCDK @michalk8
I may be missing something from the testing setup for ott-jax, like it doesn't run neural against 3.8. But figured it would be quicker to ask.

what about deprecating python 3.8 , also @giovp ?

yes lets deprecate!

ok @MUCDK !

@MUCDK do you think GENOT code in ottjax is final? My version in my thesis project is very different from the one in ottjax . If you like maybe we can first discuss possible changes there. Depends on what you want to prioritize.

@MUCDK do you think GENOT code in ottjax is final? My version in my thesis project is very different from the one in ottjax . If you like maybe we can first discuss possible changes there. Depends on what you want to prioritize.

Yeah it's not super final but I wouuld prefer to have the merges more incremental as we have been workin gon this PR for almost 2 years.
Let's talk next week in person.

Greatl, let's wait for @ilan-gold 's response, and then merge.


ALC292 codec support --LayoutID set error

There is a error in ALC292 codec support ,the error  is layoutID in file AppleALC / Resources / ALC292 / Layout12.xml.zlib

Sorry. But i don't understand where is this error. What do you mean?

In file AppleALC / Resources / ALC292 / layout12.xml.zlib, the number LayoutID should be 12 instead of 1.

Layout-id in layout.xml.zlib doesn't matters. AppleALC don't use this data at all. Resource Converter does his job very well)))
I also know about unused pathmaps)))) It is not errors - it is unfinished optimizations)))) Thanks.


Vacuum not handling YAML anchors correctly

Consider the two attached OpenAPI docs. One is a yaml document with anchors and the other is the same document that I have just inlined the anchors by doing a roundtrip through https://github.com/go-yaml/yaml
The below reproducible code shows that the document with anchors returns incorrect yaml nodes when present (specifically I am getting a node with no content).
package main

import (
	"fmt"
	"log"
	"os"

	"github.com/daveshanley/vacuum/model"
	"github.com/daveshanley/vacuum/motor"
	"github.com/daveshanley/vacuum/rulesets"
	"github.com/pb33f/libopenapi"
	"github.com/pb33f/libopenapi/datamodel"
	libopenapiUtils "github.com/pb33f/libopenapi/utils"
	"gopkg.in/yaml.v3"
)

type testRule struct{}

func (r *testRule) GetSchema() model.RuleFunctionSchema {
	return model.RuleFunctionSchema{
		Name: "test",
	}
}

func (r *testRule) RunRule(nodes []*yaml.Node,
	context model.RuleFunctionContext,
) []model.RuleFunctionResult {
	results := []model.RuleFunctionResult{}

	for _, schema := range context.Index.GetAllSchemas() {
		for _, nodeType := range []string{"anyOf", "allOf", "oneOf"} {
			keyNode, valNode := libopenapiUtils.FindKeyNode(nodeType, schema.Node.Content)
			if valNode == nil {
				continue
			}

			if len(valNode.Content) == 0 {
				results = append(results, model.RuleFunctionResult{
					Message:      "empty keyword found",
					Path:         schema.Path + "." + nodeType,
					RuleId:       context.Rule.Id,
					StartNode:    keyNode,
					EndNode:      valNode,
					RuleSeverity: context.Rule.Severity,
				})
			}
		}
	}

	return results
}

func (r *testRule) GetCategory() string {
	return "validation"
}

func main() {
	docConf := &datamodel.DocumentConfiguration{
		AllowRemoteReferences:               true,
		AllowFileReferences:                 true,
		IgnorePolymorphicCircularReferences: true,
		IgnoreArrayCircularReferences:       true,
		ExtractRefsSequentially:             true,
	}

	// data, err := os.ReadFile("openapi.yaml")
	data, err := os.ReadFile("openapi-inlined.yaml")
	if err != nil {
		log.Fatalf("error: %v", err)
	}

	d, err := libopenapi.NewDocumentWithConfiguration(data, docConf)
	if err != nil {
		log.Fatalf("error: %v", err)
	}

	ex := &motor.RuleSetExecution{
		RuleSet: &rulesets.RuleSet{
			Rules: map[string]*model.Rule{
				"test": {
					Name:         "test",
					Id:           "test",
					Given:        "$",
					Resolved:     false,
					Severity:     "error",
					Formats:      model.OAS3AllFormat,
					RuleCategory: model.RuleCategories[model.CategoryValidation],
					Type:         rulesets.Validation,
					Then: model.RuleAction{
						Function: "test",
					},
				},
			},
		},
		Document: d,
		PanicFunction: func(err any) {
			log.Fatalf("error: %v", err)
		},
		CustomFunctions: map[string]model.RuleFunction{
			"test": &testRule{},
		},
		AllowLookup: true,
	}

	results := motor.ApplyRulesToRuleSet(ex)

	for _, result := range results.Results {
		log.Printf("result: %v", result)
	}

	if len(results.Results) > 0 {
		log.Fatalf("errors found")
	}

	fmt.Println("done")
}

The code returns errors found in the version with anchors and just returns done in the inlined version
openapi.zip

This bug makes vacuum unusable for any real world use cases. Here's another example:
Given file:
openapi: 3.0.3

x-a: &anchor
  important-field: true

x-b:
  <<: *anchor

and rule set
rules:
  test-rule:
    description: Important field must be defined on all levels
    message: "important-field must be defined"
    severity: error
    given: $.x-b
    then:
      field: important-field
      function: defined

Spectral works as expected
$ spectral lint config.yaml --ruleset ruleset.yaml
No results with a severity of 'error' found!

Vacuum does not:
$ vacuum -r ruleset.yaml lint routes-openapi-proposal-1.yaml -d
Location                           | Severity | Message                         | Rule      | Category   | Path
routes-openapi-proposal-1.yaml:7:3 | error    | important-field must be defined | test-rule | Validation | $.x-b

This bug makes vacuum unusable for any real world use cases. Here's another example:

Not quite sure how to respond to this. The 1m+ downloads tells me otherwise.

This bug makes vacuum unusable for any real world use cases. Here's another example:

Not quite sure how to respond to this. The 1m+ downloads tells me otherwise.

Sorry about the choice of words and the tone it left 🙇 I should've said "for our use cases". We were attempting to migrate to vacuum for its superior performance but ran into the issue with the anchors on most of our files. Overall the project is very promising, excited to retry it later ❤

The issue has been fixed with the latest release of libopenapi all merge nodes, anchors and aliases are handled correctly. vacuum and libopenapi will be updated soon.

FYI: https://github.com/pb33f/libopenapi/commit/d1d998a79d8aa63b9aef9c6e9a8e96fe802c9e21

This has been fixed in v0.11.1
Anchors, Aliases and Merge Nodes are supported in lower level lookups in libopenapi now.
@Jakousa using your same example, the following output is now rendered:


Add addr_housenumber points

We're only capturing a minority of addresses from OSM when they are attached to a building shape. Most OSM addresses are separate points with the addr_housenumber tag. These should probably go into the buildings layer.

@bcamper will including addr_housenumber points in the building layer cause any downstream problems in Tangram?

Nope! Just makes the tiles a bit heavier, but better to have the data IMO.

Do we want to try to interpolate house number lines as well?

I tend to think no, but tell me more about what the result would look like. Are the features generated guaranteed to match ground truth in terms of position & count (would there be more of them generated than there are in fact)?

I don't think the individual addr:housenumber points are guaranteed to match ground truth in terms of position and count - there will be plenty which are out of position or missing, especially if they were imported.
As for interpolation lines; it depends where they came from. The ones I've entered have always been "full" and probably accurate enough (assuming buildings in a terrace are equal width, which they approximately are). Ones which have come in as block interpolations (e.g: from TIGER) will probably run the full X00-X99 regardless of how many houses are there.
We have a few options:

Don't include any interpolated stuff.
Include the interpolation lines.
Break the interpolation lines into points.
Break the interpolation lines into points, but mark them as having been interpolated.

I agree that the TIGER-style block interpolations are pretty useless from a display standpoint, but would think that they might come in handy for other users of the data, particularly delivery-oriented apps.

Yeah, let's skip the line interpolation for now. Side note: Pelias doesn't do any line interpolation for addresses now, so we're not the odd kid out here. I fee like routing to an interpolated address is fine, but I'm nervous about showing them on a map if they are likely to not be in the right spot.
The PR was merged. Closing this one out.


HQRM tests support Pester 5

This PR make it possible for repos to move over to Pester 5 by supporting HQRM tests in Pester 5. A repo must opt-in to running test in Pester 5 by changing the build configuration (see comment below), or run each test individually in their own pipeline. The task that is introduced here is made to work with Sampler.
Added

Added build task Invoke_HQRM_Tests and Fail_Build_If_HQRM_Tests_Failed.
Added meta build task Invoke_HQRM_Tests_Stop_On_Fail that runs both
build tasks Invoke_HQRM_Tests and Fail_Build_If_HQRM_Tests_Failed
in correct order.
New QA (HQRM) tests for Pester 5 was added that will only run if Pester 5.1
is used by the test pipeline.
Added (converted) HQRM test for Pester 5

Added Changelog.common.v5.Tests.ps1
Added ExampleFiles.common.v5.Tests.ps1
Added FileFormatting.common.v5.Tests.ps1

The individual test for checking BOM on markdown files was remove
and replaced by a test that checks for BOM on all text files (code,
configuration, and markdown). That also replaced the Pester 4 tests
ModuleFiles.common.v4.Tests.ps1 (that only checked for BOM on
.psm1files), and ScriptFiles.common.v4.Tests.ps1 (that only
checked for BOM on .ps1 files). No changes were made to the
Pester 4 tests, just the Pester 5 tests.

Added MarkdownLinks.common.v5.Tests.ps1
Added ModuleManifest.common.v5.Tests.ps1
Added ModuleScriptFiles.common.v5.Tests.ps1

Contain the converted Pester 4 tests from Psm1Parsing.common.v4.Tests.ps1.

Added PSSAResource.common.v5.Tests.ps1

Any test that is excluded by using Pester ExcludeTag under the key
DscTest: will now be silently excluded due to how Pester does Discovery.

Added PublishExampleFiles.v5.Tests.ps1
Added ResourceSchema.common.v5.Tests.ps1

Changed

Renamed all existing QA (HQRM) tests to *.v4.Tests.ps1* and made
them not run if test pipeline is using Pester 5.
The function Get-TextFilesList can now take an optional parameter
FileExtension to only return those files, e.g. @('.psm1'). This
makes the function Get-Psm1FileList obsolete.

This change is

Send in draft to get feedback. Will do the rest of the tests before I take this out of draft.

Send in draft to get feedback. Will do the rest of the tests before I take this out of draft.

A repo can opt-in to run HQRM test in Pester 5 by changing the build configuration. An example below, but this need to be documented,
BuildWorkflow:
  '.':
    - build
    - test

  hqrmtest:
    - Invoke_HQRM_Tests_Stop_On_Fail

DscTest:
  Pester:
    Configuration:
      Filter:
        Tag:
        ExcludeTag:
          - Common Tests - New Error-Level Script Analyzer Rules
      Output:
        Verbosity: Detailed
  Script:
    ExcludeSourceFile:
      - output
    ExcludeModuleFile:
      - Modules/DscResource.Common
    MainGitBranch: main

A repo can opt-in to run HQRM test in Pester 5 by changing the build configuration. An example below, but this need to be documented,
BuildWorkflow:
  '.':
    - build
    - test

  hqrmtest:
    - Invoke_HQRM_Tests_Stop_On_Fail

DscTest:
  Pester:
    Configuration:
      Filter:
        Tag:
        ExcludeTag:
          - Common Tests - New Error-Level Script Analyzer Rules
      Output:
        Verbosity: Detailed
  Script:
    ExcludeSourceFile:
      - output
    ExcludeModuleFile:
      - Modules/DscResource.Common
    MainGitBranch: main

If this PR is approved I will update the documentation on how the build task works, what to configure in build configuration, documentation how to run tests individually, and required and optional parameters in scripts.

If this PR is approved I will update the documentation on how the build task works, what to configure in build configuration, documentation how to run tests individually, and required and optional parameters in scripts.

Run in the Pester 5 tests for SqlServerDsc (in WPS):
Tests completed in 302.48s
Tests Passed: 8157, Failed: 4, Skipped: 0 NotRun: 76

Failed tests are required rules that now are correctly run for Pester 5 but not for Pester 4 (issue #95).

Run in the Pester 5 tests for SqlServerDsc (in WPS):
Tests completed in 302.48s
Tests Passed: 8157, Failed: 4, Skipped: 0 NotRun: 76

Failed tests are required rules that now are correctly run for Pester 5 but not for Pester 4 (issue #95).

@gaelcolas this is ready for review again.

What is left now is the fix for Aliases. Aliases are currently not exported correctly.

yeah, we can rework the aliases in another PR, I don't think there's any quick fix we can do here.

WOrking on a quick fix now. Give me an hour.


About TCP sumcheck in GTP

Hello @ivan4th,
This NOT issue but question.
If  the checksum in TCP header is invalid value, does upf drop it?
(TCP header is included into GTP)
Best Regards

I have not checked it, but my gut response would be: "No, why should it?"
A UPF is a middle box that forwards IP packets. Checking the checksum of the IP fragments makes sense, but looking at the higher layer checksums is IMHO not a task for a middle box.

Hello, Andreas-san,
Thank for your response!
I have checked that a upg-vpp(UPF) does not check TCP checksum by using debug tool .
Best Regards

This is OK. And I totally agree with Andreas-san's opinion.
Thank you very much!


neovim exits when current buffer is killed

Firstly, thank you for this plugin, I've been using it a lot!
Description
If you have no-neck-pain enabled, and you kill an active buffer (e.g. using :bd) it exits neovim completely.
Steps to reproduce

Load at least two buffers
:NoNeckPain
:bd
neovim exits

Expected behavior
I would expect for it to show the other loaded buffer instead of exiting (like it does when no-neck-pain is not used).
Environment

Neovim version: v0.10.0
no-neck-pain.nvim version: 1.14.0

Hey, thanks for using the plugin, glad you like it :)
You should not see the issue anymore after setting fallbackOnBufferDelete = true, this will be defaulted to true in the next major version

Sorry for a late response,
I tried setting fallbackOnBufferDelete = true. Now it does not exit neovim, but opens a new empty buffer instead of any other loaded buffers. Maybe there is a setting to disable this too?

Is this potentially related to #370 ?

It is happening to me as well.
nvim 0.10
no-neck-pain 1.14.1
using telescope
Steps:

nvim in a directory
fzf to file
fzf to another file
x to close the last buffer (vim.cmd.bw)

And it quit nvim
Anyway for your plugin, it is helping me a lot with my neck, but also to my eyes.

For folks waiting for fix:
-- my keymap function for reference
local keymap = function(mode, lhs, rhs, desc)
	vim.keymap.set(mode, lhs, rhs, { noremap = true, silent = true, desc = desc })
end

...

keymap("n", "<S-x>", ":NoNeckPain<cr> :sleep 1m<cr> :bdelete<cr> :NoNeckPain<cr>", "")

Toggle NNP, sleep 1 milisecond, delete the buffer, toggle NNP back.

Hey there, sorry for the huge delay on the response, just got a baby few months ago, which takes as much time as tweaking my nvim config D:
I think the issue should be fixed with #375, if anyone has time, don't hesitate to confirm by testing on main :)
Thanks again for using the plugin!!

Hi, this issue still persists for me in 1.16.1 with the default config.
The behavior is the same as said before:

I tried setting fallbackOnBufferDelete = true. Now it does not exit neovim, but opens a new empty buffer instead of any other loaded buffers. Maybe there is a setting to disable this too?

Please ping me if you need testing.

Hey, I think I have a final fix for this on the next branch, in case you want to try it :)
(There should be no breaking changes)

Okay, so it will work properly, but won't close Neovim when closing the last buffer. After testing with my config*, I narrowed it down to:

skipEnteringNoNeckPainBuffer = true autocmd will close the current buffer and will send Neovim straight into purgatory, where it won't take any input (doesn't matter if it's the only option or among others),
fallbackOnBufferDelete needs to be true, otherwise it will close Neovim (of course the skipEnteringNoNeckPainBuffer needs to be false or not present), but when true then it won't close Neovim when closing the last buffer.

*My config for 1.16.1 for reference
width = 100,
fallbackOnBufferDelete = false, -- because of my custom close behavior
buffers = {
    right = {
        enabled = false,
    },
    scratchPad = {
        -- set to `false` to disable auto-saving
        enabled = false,
        location = nil,
        -- set to `nil` to default to current working directory
    },
    bo = {
        filetype = "md",
    },
    wo = {
        fillchars = "eob: ",
    },
},
autocmds = {
    enableOnVimEnter = true,
    skipEnteringNoNeckPainBuffer = true,
},

Hope it helps!

thanks @bogdan-the-great !! indeed I also flagged a clash with skipEnteringNoNeckPainBuffer, will resolve that too and we should be good :D

should be fixed on the last commit of next: https://github.com/shortcuts/no-neck-pain.nvim/pull/384/commits/db44bfdc44dc64a71aadc356adf21668caeb8bd8

Now skipEnteringNoNeckPainBuffer = true doesn't hang Neovim, but the fallbackOnBufferDelete behaves the same way as before:

fallbackOnBufferDelete needs to be true, otherwise it will close Neovim (of course the skipEnteringNoNeckPainBuffer needs to be false or not present), but when true then it won't close Neovim when closing the last buffer.

Tested with minimal config (only lazy.nvim and NNP).

Thanks for doing further testing @bogdan-the-great, would you mind describing which steps you are doing?
Here's what I'm trying out:
with skipEnteringNoNeckPainBuffer and fallbackOnBufferDelete to true:

open at least 2 buffers
open nnp
:bd

close the window, and the buffer focused
open a new window, with the other opened buffer in it

open only 1 buffer
open nnp
:bd

close the window, and the buffer focused
open a new window, with an empty buffer

without fallback, if there's only one window, quit nvim


[feature] Implement tidyselect

Column names should also support functions along with strings:
df.select(['a', 'b', 'c']) # regular
df.select(['a', 'b', starts_with('c'), ends_with('d'), contains('some_regex')])
tidyselect should power all the methods that take column_names as the input.

Also, replace_na, should be changed to accept list of columns and/or column selector in the key of the dictionary being passed.
Also, is the value appropriate argument name in replace_na?

IMHO, value should be a single value for simplicity. If we allow a list of values to be passed, then we implicitly already the columns to be renamed right?
my suggestion:
df.replace_na({ends_with("width"): 0}) and not df.replace_na({ends_with("width"): [0, 1]})
as in latter case, usually we might not know how many columns get selected.

To expand tidyselect for following methods
count
add_count
nest_by
expand
complete
Summarise -> in by
Mutate -> in by

Is there is an easy way to filter using tidyselect. Like:
df.filter(starts_with("x") < 10)


Resulting stream is not an instance of Readable

The resulting stream uses a custom variant of streams instead of the node default implementations.
This makes it difficult to combine this transform with interfaces that use/expect the default stream implementation of node.

No. Transform stream is one of the default implementations.

@call-a3 what is the real life problem you encounter?

I'm using this package to mutate filestreams before passing them on to the next layer in my project. This underlying layer accepts streams but also strings and specifically-formed objects. It performs caching of a stream if necessary/possible. To determine this, it detects whether the input is I Readable from the default stream API (I'm using node v6). The streams outputted by this package don't pass that test

If we drop Node v0.x support, we can safely use core Stream instead of readable-stream npm package.

Eventually, we will. But there are many other packages that use readable-stream. So it won't solve your problem @call-a3  https://r.va.gg/2014/06/why-i-dont-use-nodes-core-stream-module.html

https://r.va.gg/2014/06/why-i-dont-use-nodes-core-stream-module.html

Yeah, I should have refer to that blog post. That is why we use readable-stream in this package.
@call-a3 Temporary solutions:

https://github.com/rvagg/isstream
https://github.com/sindresorhus/is-stream

Thanks for those references. Guess I'll have to go with an is-readable-stream implementation.


Server Error after submitting API token

Affected page

Your code

Expected behavior

Screenshots

System

Device: [e.g. iPhone6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.4]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]

Additional context

for word in list' error

Hello there,
As this issue does not contain enough information for us to debug or help, it is invalid. Therefore, I am closing this issue.
If you accidentally opened this, then there is not need to do anything. However, if you still are encountering an issue, then please edit your description to include useful information such as:

What you are trying to accomplish
What the expected behaviour is
What the actual behaviour is
What tools you are using (OS specific information)
Any relevant links (CodePen, User profile...)

Once that is updated, we can reopen this issue. Thank you.


I'm so nice, I'm listed twice! <3

I changed my git and/or github display name at some point, so I'm listed under both "Carol Nichols" and "Carol (Nichols || Goulding)". I'd prefer the latter. I'm pretty sure my git emails match.

We should investigate fixing this in rust's mailmap 👍 then it'll get pulled into here.
On Jan 26, 2017, 17:14 -0500, Carol (Nichols || Goulding<EMAIL_ADDRESS>wrote:

I changed my git and/or github display name at some point, so I'm listed under both "Carol Nichols" and "Carol (Nichols || Goulding)". I'd prefer the latter. I'm pretty sure my git emails match.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (https://github.com/rust-lang-nursery/thanks/issues/45), or mute the thread (https://github.com/notifications/unsubscribe-auth/AABsijNqHotzZzRU15HDTDDvAFhtERZbks5rWRrTgaJpZM4LvNWM).

rustlang PR was merged, so I'm going to give this a close. This will be fixed on its own before thursday. Thanks!


Broken/wrong link

In the introduction. the link to "firebase for flutter" is broken and can't be found.

Thanks for reporting! I'm carving some time to address a bunch of issues with this codelab (using an older version of flutterfire, some links breaking, etc...)
In the meantime, try this one by @domesticmouse, it's newer and should be more up to date with what Flutter and Firebase are now!
https://firebase.google.com/codelabs/firebase-get-to-know-flutter#0


Support srcSet for Img

Be nice to suspend on srcSet: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#attr-srcset
e.g.
<Img src={pathToPNG} srcSet={`${pathToPNG_2x} 2x`} />

Feel free to submit a PR!

@jaredpalmer would this work? https://github.com/palmerhq/the-platform/pull/47


Module not found: Can't resolve 'module'

Try to use cosmiconfig
const cosmiconfig = require('cosmiconfig')

and get error

./node_modules/resolve-from/index.js
Module not found: Can't resolve 'module' in '<project_path>/node_modules/resolve-from'

cosmiconfig: 5.0.7,
node: 8.12.0

I create branch that reproduce issue

git clone https://github.com/ravecat/mendeleev.git --single-branch --branch cosmiconfig-issue
yarn

I have code in src/common/Media/responsive/index.js
/* eslint-disable */
import { css } from "styled-components";
const cosmiconfig = require('cosmiconfig')

const responsive = (property, resolution) => {
  // TODO Here I want to get config
  return css`
    @media (max-width: ${resolution}px) {
      ${property};
    }
  `;
}

export default responsive;

In same folder I also exist .sctrc file

Pardon for interrupt, solved in referenced issue above


Remove support for assigning None to a SplitField

This behavior wasn't documented and didn't fully work: it breaks as soon as you try to save a model with a None value.
I think removing None support is better than making it work:

to make it work properly, it would have to respect the null constructor argument both in the implementation and in the type checking, which is a lot of work
the Django docs recommend against using null=True for text fields, so the value of the feature is questionable

As it was an undocumented feature that only partially worked, I think this change doesn't break backwards compatibility, so I didn't add it to the ChangeLog.

With 73,057 Downloads last day* you are at least breaking someones code. But since it is undocumented and not working properly I'm not against it.
*https://pypistats.org/packages/django-model-utils

Does that mean the PR is fine as it is or should I add a line to the ChangeLog?

That is up to you, I don't have an opinion on this one.


chore: fix MSRV build

This PR

had to increase the MSRC version to 1.71.1, because of mockall and tokio

@prnam it always depends, we try to support the lowest possible version, but now 2 dependencies need a higher one, so it seems for me to be a good time to increase the minimum supported version.

@prnam it always depends, we try to support the lowest possible version, but now 2 dependencies need a higher one, so it seems for me to be a good time to increase the minimum supported version.

I strongly agree that the versions of the dependencies (compiler version included) needs to be kept up-to-date to prevent the project from decaying.
I do not mind upgrading the compiler version at all...
Good work @gruebel :+1:


Sequence Autoencoder with Small Loss

I'm trying to get the thought vector described in some papers using an autoencoder, to be able to get more meaningful vectors then Doc2Vec (since it doesn't work well in small sentences).
But when I train my model, I'm getting an incredible small loss (loss: 9.5479e-05 - val_loss: 9.6238e-05) on the first epoch and so on. I don't know if that's correct or I have some problem with my implementation.
To represent the text, I'm using one-hot encoding (as you see in my code) and using Mean-Squared Error as loss function.
# Settings
number_of_samples   = 1000
max_length          = 20
nb_words            = 10000
latent_dim          = 100

# Create the Dataset
X_train, X_test, (index_to_word, word_to_index) = create_dataset(number_of_samples=number_of_samples, max_length=max_length)

# Create the Autoencoder Model
inputs = Input(shape=(max_length, nb_words), name='main_input')

# Codification
encoded = LSTM(latent_dim)(inputs)

decoded = RepeatVector(max_length)(encoded)
decoded = LSTM(latent_dim, return_sequences=True)(decoded)
decoded = TimeDistributed(Dense(nb_words))(decoded)

# Models
autoencoder = Model(inputs, decoded)
encoder     = Model(inputs, encoded)

# Compile
autoencoder.compile(optimizer='rmsprop', loss='mse')

I'm adding a Gist with all the code, and how the data is generated (this can be useful for someone later): https://gist.github.com/brunoalano/ddb041338a486648b7730ed567840818

What's the dimensionality of your data, nb_words? With enough hidden parameters, its totally possible that the network learns something close to the identity function to encode inputs. Theoretically, you can easily represent your 100-dimensional data with no loss in 100 hidden dimensions if it is one word per timestep. Your network does not predict the next timestep, right? You only encode and decode one word at a time?
Another likely explanation might be that the network learns to memorize your data, i.e. it overtrains. You only have 1000 samples of length 20, that's not a lot.


Updated cookbook custom http status code section

Codecov Report

Merging #300 into master will decrease coverage by 5.88%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #300      +/-   ##
==========================================
- Coverage   38.47%   32.58%   -5.89%
==========================================
  Files          88       95       +7
  Lines        2773     3759     +986
  Branches        6        6
==========================================
+ Hits         1067     1225     +158
- Misses       1706     2534     +828

Requested changes are done.


Why is ObjectCollection::setClassName() a getter ...

This is not a bug really, just a break of naming convention.
here:
https://github.com/bruli/php-value-objects/blob/master/src/PhpValueObjects/Collection/ObjectCollection.php#L32
and in your testable object here:
https://github.com/bruli/php-value-objects/blob/master/src/PhpValueObjects/Tests/Collection/Collection.php#L12
your useing setClassName() to return a classname ... why did you name it setClassName() ?

Any sugestion?

getClassName() ? ;-)

I'm closing this as it has been over a year and it does not seem to matter ... it is just very odd, but i'm not using this library anyway so..


Release v2.2

This has been a FIXME in my stack.yamls for a while now... I'm happy to release this, but I don't have the permissions on Hackage (and I haven't actually released something before so I'm unsure how to do it).

I'm looking into this but ran into a few problems building the package w/ the latest nightly:

Unable to parse cabal file: FromString "This package requires at least Cabal version 2.0" Nothing

What snapshot version are you trying to use this with?
I'll keep trying to fix it, but if  you have time to attempt to build it against the latest nightly, that would help. Thanks!

I'm happy to do it tomorrow, or if I don't get to it will do so Saturday morning!

I'm using this with 9.13, and it's compiling as an extra-dep (building from source) in my stack.yaml

With 9.13, it's building successfully for me. However, I get the error I posted when I use the latest nightly. Were you able to build successfully with that? If so, we can enable it in the stackage build-constraints.yaml.

Unable to parse cabal file: FromString "This package requires at least Cabal version 2.0" Nothing

I was able to build successfully with both 9.13 and nightly. I am building on macOS High Sierra with Stack version 1.5.1.
I found this article that mentions you probably need to use 1.5.1.

Tagged: https://github.com/creichert/wai-middleware-throttle/releases
Uploaded version: https://hackage.haskell.org/package/wai-middleware-throttle
Can you double-check my work? Also, I can add you as a Hackage maintainer if you shoot me your username.

One issue is the ./scripts directory which raises several package exceptions. I'm not exactly sure what to do with that package, but it might be a good idea to use the stack script interpreter:
Getting file list for /home/christopher/dev/haskell/wai-middleware-throttle/script/
Building sdist tarball for /home/christopher/dev/haskell/wai-middleware-throttle/script/
Warning: These files are outside of the package directory, and will be omitted from the tarball: ["../LICENSE"]
Checking package 'script' for common mistakes
Package check reported the following warnings:
No 'category' field.
'ghc-options: -Wall -Werror' makes the package very easy to break with future GHC versions because new GHC versions often add new warnings. Use just 'ghc-options: -Wall' instead.
'ghc-options: -O2' is rarely needed. Check that it is giving a real benefit and not just imposing longer compile times on your users.
The 'license-file' field refers to the file '../LICENSE' which does not exist.
Package check reported the following errors:
No 'synopsis' or 'description' field.
The dependency 'build-depends: base' does not specify an upper bound on the version number. Each major release of the 'base' package changes the API in various ways and most packages will need some changes to compile with it. The recommended practise is to specify an upper bound on the version of the 'base' package. This ensures your package will continue to build when a new major version of the 'base' package is released. If you are not sure what upper bound to use then use the next  major version. For example if you have tested your package with 'base' version 2 and 3 then use 'build-depends: base >= 2 && < 4'.
The package is missing a Setup.hs or Setup.lhs script.

Also, the existence of the ./scripts directory in the main stack.yaml incurs a large number of dependencies that the package wouldn't otherwise need since most users likely won't be running the benchmarks.
We could use a script interpreter and build/run it during CI. Let me know what you think.

Oh yes, I agree, shouldn't be distributed. Running it as part of CI is definitely a good idea, though it's obviously more diagnostic than a "test case".
The tag looks good.
When I go to the hackage page, I see "Distributions" as having the old version (<IP_ADDRESS>). I also can't click on docs for Network.Wai.Middleware.Throttle - do they need to be uploaded as well somehow?

Oh and my hackage username is dfithian

I added you as a Hackage maintainer

The documentation builds can take a bit but they will popup

I just created a PR on stackage https://github.com/fpco/stackage/pull/3036


make error on macOS Monterey

I'm getting this error when i try to compile and i havent found any similiar issue posted here:
Making all in tools   CCLD     xrdp-xcon ld: warning: ignoring file /usr/X11/lib/libX11.dylib, missing required architecture arm64 in file /usr/X11/lib/libX11.dylib (2 slices) Undefined symbols for architecture arm64:   "_XConnectionNumber", referenced from:       _main in xcon.o   "_XNextEvent", referenced from:       _main in xcon.o   "_XOpenDisplay", referenced from:       _main in xcon.o ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[3]: *** [xrdp-xcon] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2

We don't really support MacOS (see the wiki), but this looks to me like you're missing some development files.
A quick search pulled up a few hits which might be useful to fix this.


expose index args on community methods

not sure whats up with these failures yet. It appears to have something to do with the cleanup step on windows. All the tests pass
=========== 49 passed, 6 skipped, 88 warnings in 472.96s (0:07:52) ============
Fatal error condition occurred in D:\bld\aws-c-io_1633633258269\work\source\event_loop.c:74: aws_thread_launch(&cleanup_thread, s_event_loop_destroy_async_thread_fn, el_group, &thread_options) == AWS_OP_SUCCESS
Exiting Application
at 0x7FFD5B424380: aws_backtrace_print
at 0x7FFD5B413560: aws_fatal_assert
at 0x7FFD5B315F10: aws_event_loop_wait_for_stop_completion
at 0x7FFD5B421470: aws_ref_count_release
at 0x7FFD5B313D80: aws_server_bootstrap_set_alpn_callback
at 0x7FFD5B421470: aws_ref_count_release
at 0x7FFD5B313760: aws_client_bootstrap_release
at 0x7FFD5B4776F0: Aws::Crt::Io::ClientBootstrap::~ClientBootstrap
at 0x7FFD5B7EEB40: Aws::Utils::Stream::SimpleStreamBuf::xsputn
at 0x7FFD9E2F1BA0: execute_onexit_table
at 0x7FFD9E2F1BA0: execute_onexit_table
at 0x7FFD9E2F1BA0: execute_onexit_table
at 0x7FFD5B7EEB40: Aws::Utils::Stream::SimpleStreamBuf::xsputn
at 0x7FFD5B7EEB40: Aws::Utils::Stream::SimpleStreamBuf::xsputn
at 0x7FFDA1485AA0: RtlAnsiStringToUnicodeString
at 0x7FFDA14890F0: LdrShutdownProcess
at 0x7FFDA14CCAB0: RtlExitUserProcess
at 0x7FFDA06FD620: ExitProcess
at 0x7FFD9E300C50: exit
at 0x7FFD9E300C50: exit
at 0x7FFD6D83A5A0: Py_Exit
at 0x7FFD6D85F430: Py_HandleSystemExit
at 0x7FFD6D85E410: PyRun_InteractiveOneFlags
at 0x7FFD6D85EBC0: PyRun_SimpleFileExFlags
at 0x7FFD6D67E120: Py_hashtable_copy
at 0x7FFD6D67E120: Py_hashtable_copy
at 0x7FFD6D688440: Py_RunMain
at 0x7FFD6D689080: Py_Main
at 0x7FF672FC1160: OPENSSL_Applink
at 0x7FFDA06F7960: BaseThreadInitThunk
at 0x7FFDA14BA2D0: RtlUserThreadStart
Error: Process completed with exit code 1.

error appers to be caused by https://github.com/conda-forge/arrow-cpp-feedstock/issues/567


Deprecate Arcfour

It's now an internet standard:
https://www.rfc-editor.org/authors/rfc8758.html
There was a PR about this:
https://github.com/mscdex/ssh2-streams/pull/125
Would it be an appropriate time to revisit this PR ?

@mscdex What do you think ?

RC4 already isn't in the default cipher list so someone would have to explicitly enable it to use it.


error message when using amplify push && amplify codegen models "@auth directive with 'userPools' provider found, but the project has no Cognito User Pools authentication provider configured."

Describe the bug
When trying to build a graphql API that will allow authenticated fields as well as a publicly accessible fields in order to populate a public web page (e.g., blog posts);
Amplify CLI Version
4.22.0
To Reproduce
Steps to reproduce the behavior or terminal output if applicable

$> amplify init

? Enter a name for the project sample_project
? Enter a name for the environment dev
? Choose your default editor: Atom Editor
? Choose the type of app that you're building javascript
Please tell us about your project
? What javascript framework are you using angular
? Source Directory Path:  src
? Distribution Directory Path: dist
? Build Command:  npm run-script build
? Start Command: ng serve
Using default provider  awscloudformation

$> amplify push
$> amplify add auth

$> amplify add auth
Using service: Cognito, provided by: awscloudformation

The current configured provider is Amazon Cognito.

Do you want to use the default authentication and security configuration? Manual configuration
Select the authentication/authorization services that you want to use: User Sign-Up, Sign-In, connected with AWS IAM controls (Enables per-user Storage features for images or other content, Analytics, and more)
Please provide a friendly name for your resource that will be used to label this category in the project: testdef8faa7def8faa7
Please enter a name for your identity pool. testdef8faa7_identitypool_def8faa7
Allow unauthenticated logins? (Provides scoped down permissions that you can control via AWS IAM) Yes
Do you want to enable 3rd party authentication providers in your identity pool? No
Please provide a name for your user pool: testdef8faa7_userpool_def8faa7
Warning: you will not be able to edit these selections.
How do you want users to be able to sign in? Email
Do you want to add User Pool Groups? Yes
? Provide a name for your user pool group: test_group
? Do you want to add another User Pool Group No
✔ Sort the user pool groups in order of preference · test_group
 Do you want to add an admin queries API? No
 Multifactor authentication (MFA) user login options: OFF
 Email based user registration/forgot password: Enabled (Requires per-user email entry at registration)
 Please specify an email verification subject: Your verification code
 Please specify an email verification message: Your verification code is {####}
 Do you want to override the default password policy for this User Pool? No
 Warning: you will not be able to edit these selections.
 What attributes are required for signing up? Email
 Specify the app's refresh token expiration period (in days): 30
 Do you want to specify the user attributes this app can read and write? No
 Do you want to enable any of the following capabilities?
 Do you want to use an OAuth flow? No
? Do you want to configure Lambda Triggers for Cognito? No
Successfully added resource testdef8faa7def8faa7 locally

$> amplify push - Cloudformation succeeded
$> amplify add api w/IAM

$> amplify add api
? Please select from one of the below mentioned services: GraphQL
? Provide API name: sample_project
? Choose the default authorization type for the API IAM
? Do you want to configure advanced settings for the GraphQL API Yes, I want to make some additional changes.
? Configure additional auth types? No
? Configure conflict detection? No
? Do you have an annotated GraphQL schema? No
? Do you want a guided schema creation? Yes
? What best describes your project: Single object with fields (e.g., “Todo” with ID, name, description)
? Do you want to edit the schema now? No

The following types do not have '@auth' enabled. Consider using @auth with @model
         - Todo
Learn more about @auth here: https://docs.amplify.aws/cli/graphql-transformer/directives#auth

GraphQL schema compiled successfully.

$> amplify push

? Do you want to update code for your updated GraphQL API Yes
? Do you want to generate GraphQL statements (queries, mutations and subscription) based on your schema types?
This will overwrite your current graphql queries, mutations and subscriptions Yes
⠏ Updating resources in the cloud. This may take a few minutes...

$> amplify update api w/ IAM && UserPools

? Please select from one of the below mentioned services: GraphQL
? Select from the options below Walkthrough all configurations
? Choose the default authorization type for the API IAM
? Do you want to configure advanced settings for the GraphQL API Yes, I want to make some additional changes.
? Configure additional auth types? Yes
? Choose the additional authorization types you want to configure for the API
? Configure conflict detection? No

The following types do not have '@auth' enabled. Consider using @auth with @model
         - Todo
Learn more about @auth here: https://docs.amplify.aws/cli/graphql-transformer/directives#auth

GraphQL schema compiled successfully.

add @auth block to schema.graphql

type Todo @model
@auth( rules: [
  { allow: owner },
  { allow: public, operations: [read], provider: iam }
])
{
  id: ID!
  name: String!
  description: String
}

$> amplify push

✔ Successfully pulled backend environment dev from the cloud.

Current Environment: dev

| Category | Resource name              | Operation | Provider plugin   |
| -------- | -------------------------- | --------- | ----------------- |
| Api      | sample_project                 | Update    | awscloudformation |
| Auth     | userPoolGroups             | No Change | awscloudformation |
| Auth     | testdef8faa7def8faa7 | No Change | awscloudformation |
? Are you sure you want to continue? Yes
✖ An error occurred when pushing the resources to the cloud

@auth directive with 'userPools' provider found, but the project has no Cognito User Pools authentication provider configured.

Expected behavior
Expect for defined IAM and Cognito User Pools to be setup and available for deployment; successful push of new scheme with valid IAM and Cognito auth methods;
Desktop (please complete the following information):
Ubuntu

Node Version: v10.19.0

Additional context
After replicating steps, amplify/backend/amplify-meta.json is missing any entries in the additionalAuthenticationProviders:
"api": {
        "sample_project": {
            "service": "AppSync",
            "providerPlugin": "awscloudformation",
            "output": {
                "authConfig": {
                    "additionalAuthenticationProviders": [],
                    "defaultAuthentication": {
                        "authenticationType": "AWS_IAM"
                    }
                },
                "GraphQLAPIIdOutput": "fodkrejm2vgdzkecgmkoyrz2tm",
                "GraphQLAPIEndpointOutput": "https://owbys52sqvd4zj57tgfpsz6ste.appsync-api.us-east-1.amazonaws.com/graphql"
            },
            "providerMetadata": {
                "s3TemplateURL": "https://s3.amazonaws.com/amplify-sample-dev-151849-deployment/amplify-cfn-templates/api/cloudformation-template.json",
                "logicalId": "apisample"
            },
            "lastPushTimeStamp": "2020-07-02T20:50:38.938Z",
            "lastPushDirHash": "jSvBewBN3ApZZxGVJfYrlbRiN+I="
        }
    }

manually adding:
{
"authenticationType": "AMAZON_COGNITO_USER_POOLS",
	"userPoolConfig": {
		"userPoolId": "us-east-1_CNhehjx0O"
	}
}

to the amplify-meta.json - API -> output -> authConfig -> additionalAuthenticationProviders section results in a successful build and push;

@jasimmonsv you could also update the API using amplify update api command and add additional auth type to your API.

@yuth Step 7 is amplify update api; please reopen this ticket

Sorry I missed that part
When choosing additional auth type, you will have to select Amazon Congnito User Pool by pressing <space bar> and then <return>, pressing <return> key does not select the any values.

son of a.... :facepalm:
thank you @yuth...  this whole time

This worked for me. Thank you! I just encountered this.

Sorry I missed that part
When choosing additional auth type, you will have to select Amazon Congnito User Pool by pressing <space bar> and then <return>, pressing <return> key does not select the any values.

Holy sh*t! 1h Wasted on this!

Ran into this as well! Having to press <space bar> and then <return> was def not obvious! Thanks for posting!

Ran into this as well! Having to press <space bar> and then <return> was def not obvious! Thanks for posting!

This is a life saver. NOT INTUITIVE AT ALL :(

This is a life saver. NOT INTUITIVE AT ALL :(

OMG! At least 8 hours wasted on that. Space bar to the rescue!

OMG! At least 8 hours wasted on that. Space bar to the rescue!

@vitaliikravets i spent around the same time. Thank you for saying that, I was a bit embarrassed to admit it 😬

@vitaliikravets i spent around the same time. Thank you for saying that, I was a bit embarrassed to admit it 😬

hero @yuth


Non-deterministic mean and sum reduction

I'm running Tensorflow 0.9.0 installed from wheel on Python 2.7 on a K40 with CUDA 7.0.
The following test case attempts to minimize the mean of a vector through gradient descent. The script finds that the vectors are equal at all steps, but the means are not. I believe the vectors being equal at all steps is pure numerical luck, since non-deterministic loss likely means non-deterministic gradient which means non-deterministic/reproducible iterative optimization. I've observed cases where training results in different final losses where the only source of non-determinism is from reduce_mean.
import numpy as np
import tensorflow as tf

n_dims = 1000
n_steps = 50

np.random.seed(2016)

vec = tf.Variable(np.random.randn(n_dims).astype(np.float32))
mean = tf.reduce_mean(vec)

optimizer = tf.train.GradientDescentOptimizer(0.01)
train_step = optimizer.minimize(mean)

def generate():
    data = []
    with tf.Session() as sess:
        sess.run(tf.initialize_all_variables())

        for _ in xrange(n_steps):
            _vec, _mean, _ = sess.run([vec, mean, train_step])
            data.append((_vec, _mean))

    return [np.array([f[i] for f in data]) for i in xrange(2)]

first_vec, first_mean = generate()
second_vec, second_mean = generate()
print 'vecs equal:', np.all(first_vec == second_vec)

print 'mean equal:', np.all(first_mean == second_mean)
print 'means not equal at idxs:', np.nonzero(first_mean != second_mean)[0]

Example output:
vecs equal: True
mean equal: False
means not equal at idxs: [ 4  5 11 18 34 38 44 49]

From looking through the code, it appears the GPU mean reduction is implemented with GPU sum reduction: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/reduction_ops_gpu.cu.cc#L43
I've confirmed my test case still triggers when I replace "reduce_mean" with "reduce_sum".
The GPU sum reduction appears to be implemented using CUDA's atomicAdd: https://bitbucket.org/eigen/eigen/src/241472d2a52142e23b0b2ba5c301c6c146298fa9/unsupported/Eigen/CXX11/src/Tensor/TensorReductionCuda.h?at=default&fileviewer=file-view-default#TensorReductionCuda.h-97
Atomic floating point adds on GPU are the problem. Having floating point adds to the same address in an undefined order is inherently non-deterministic due to non-associativity of floating point arithmetic.
This issue could be solved (and reduction performance improved) by using some sort of reduction tree to reduce within blocks, and then launching a second kernel (or doing some manual block synchronization tricks) to reduce across blocks.

I created a smaller test case.
import numpy as np
import tensorflow as tf

np.random.seed(2016)
data = np.random.randn(100000).astype(np.float32)

vec = tf.placeholder(tf.float32, data.shape)
avg = tf.reduce_mean(vec)

avgs = []
with tf.Session() as sess:
    for _ in xrange(100):
        avgs.append(sess.run(avg, feed_dict={vec: data}))

print min(avgs) == max(avgs)
print max(avgs) - min(avgs)

with output
False
6.98492e-10

@lightcatcher as you point out, our current implementation of sum reduction (and the various ops that depend on it) is not deterministic on either GPU or multi-threaded CPUs. It is primarily a speed/accuracy trade-off and if we could get comparable speed from one of the approaches you mention, we would be happy to switch the implementation. In short, this is working as intended for now, but contributions for a more accurate or even deterministic sum reduction (possibly as a separate op) would certainly be welcomed.

I'm closing this as "working as intended".

Which other ops are non-deterministic that are not non-deterministic by nature?

@TimZaman Unless something has changed in the recent months, some of the cuDNN code is non-deterministic, for instance cudnn.SpatialConvolution. So, I guess that some of the CNN-related stuff in tensorflow may be non-reproducible (if run on GPU). Would probably be a bit of work, but it would be nice to have a flag or note in the TF docstrings of the affected functions.

As @zheng-xq mentioned earlier, anything using cuda atomics is non-deterministic, so a way to narrow it down is to see which CuDNN algorithms use CUDA atomics. For CPU ops, the way to check might be to track down parallel ops (see which ops use tensorflow/core/util/work_sharder.cc) and check that result is independent of the order in which individual work shards complete

Are reductions still non-determinstic by default on GPU? If so, can this issue be re-opened? Determinstic computation is critical for reproducibility, and reductions are a critical part of neural nets.
Finally:
Several comments on this issue and other linked issues mention that "reductions are non-determinstic for performance". This is not the case. A reduction tree is both determinstic and generally faster than using atomic adds (which cause non-determinism). https://devblogs.nvidia.com/faster-parallel-reductions-kepler/ describes reduction trees, shows that reduction tree + very limited use of atomic add is the fastest option, but that reduction trees (determinstic) is only marginally slower.
Last I checked (quite a while ago), the TF reduction implementation exclusively used atomics and no reduction tree, so a switch to a reduction tree only implementation would provide a performance boost. My guess is that atomics were used for the TF implementation not for performance but because the implementation with atomics is somewhat simpler to write.

I believe there's been some work to make reductions deterministic

@yaroslavvb
I just re-ran my initial examples on TF 1.5.0 and found that that reduce_mean call produced consistent results across 10K trials with the mean kernel running on a K80 GPU. This observation agrees with @ahmedhosny 's observation.
I dug through the source a little bit and I think the reduction logic happens in https://github.com/eigenteam/eigen-git-mirror/blob/master/unsupported/Eigen/CXX11/src/Tensor/TensorReduction.h . This (and the TensorReductionGpu.h file) are new since I opened this issue in 2016 and contain reduction tree logic. However, they also still contain atomic floating point adds. I think these are to reduce the values between the different GPU blocks.
This file has been recently modified by @rmlarsen . @rmlarsen , do you have any insight on how deterministic these reductions are? When is atomic floating point add used?

maybe it's num of cpu related.
test with tf2, with docker, as:
docker run -it --rm --cpuset-cpus="0-7" ...

different cpus will get results, different with the last two digits
testing code
import tensorflow as tf

x = tf.constant(0.6931, shape=[32, 100, 79804], dtype=tf.float32)
y = tf.reduce_mean(x)
print(y)


Minor logging bug with multiple inserts of "What subreddit would you like to download? You may submit multiple separated by commas (no spaces)."

Validating that all posts were downloaded...
Still downloading posts from pics... (26/10)
Still downloading posts from pics... (27/10)
🎉 All done downloading posts from pics!
What subreddit would you like to download? You may submit multiple separated by commas (no spaces).
         🎉 All done downloading posts from !
What subreddit would you like to download? You may submit multiple separated by commas (no spaces).

I believe this was fixed with #59, closing. If anyone else faces this, we can reopen.


fail fast when handling incompatible package

Is your feature request related to a problem? Please describe.
zarf package deploying a package that was zarf package created with a version of zarf that uses/used a different packaging format, can cause deploy-time errors related to the breaking schema change. These sorts of indirect errors can be some of the hardest to diagnose. This feature request aims to save users/developers time by catching these earlier and providing explicit clear feedback.
Describe the solution you'd like
As early as possible, zarf package deploy pkg.zst will glean the zarf version used to create pkg.zst, compare that to the running zarf version, and if the delta includes known breaking schema change(s), emit an informative ERROR and exit 1 immediately.
This presupposes that zarf release process uses something like semver, which makes it trivial to check for a breaking transition using arithmetic. If this is not the case, perhaps now would be the time to better define its versioning scheme and compatibility guarantees.
Describe alternatives you've considered
Since we found this in CI originally, we considered implementing this check ourselves in the pipeline steps.
Additional context
@lucasrod16 discovered this to be the cause of some errors UDS team was seeing in zarf-package-big-bang CI. Specifically, our deploy pipeline was using 0.26.4 to deploy a package built with v0.27.0. The 0.27.0 release notes clearly highlight the breaking change:

Internal package structure changes will require packages built with v0.27.0 to be deployed with v0.27.0 or higher by @Noxsios in https://github.com/defenseunicorns/zarf/pull/1469 and by @Racer159 https://github.com/defenseunicorns/zarf/pull/1696
Previously built packages are still compatible with v0.27.0, only newly created packages will require the higher version

We would love to have seen zarf deploy instead fail fast with something like:
ERROR: `zarf` v0.26.4 cannot `deploy` a package created with `zarf` v0.27.0 due to a breaking change.

...perhaps followed with some guidance and a built-in reminder about zarf's versioning scheme and compatibility guarantees:
Zarf uses a variant of semver and cannot guarantee inter-operability between instances with different major or minor versions.

..or whatever is appropriate for the actual versioning/compatibility contract zarf prescribes.

Added the ga label to this
Right now we do breakages on minors even though that is not part of semver because we are not yet GA.  We could add a warning when a minor version bump is detected though minors are not guaranteed at this time to have breaking changes (see v0.23.x -> v0.24.x).
What may be a better solution for now is to add a "minimumVersion" field to the build information that Zarf can check and fail on if it is less than that version.


SSR Cache RFC

Create RFC for SSR cache

I'm generally a fan of allowing cache hooks in SSR, and I'm excited to see this proposal. Thanks for it!
I'm a bit concerned about the level of the API, though. I tend to think that a component author is the best authority on whether or not a component can be cached, rather than the developer who is calling renderToString, so I would prefer a standardized lifecycle method, perhaps like your getCacheKey example.
I understand that getCacheKey can be implemented in user space with this proposal through cache strategies, but I think that's a recipe for getting multiple, incompatible new lifecycle methods defined by different cache strategy authors. What happens if I'm using component A from library A which expects a cache strategy with a getCacheKey lifecycle method at the same time I'm using component B from library B which expects a cache strategy with a componentWillCache lifecycle method?

Could components do this instead?
For example, what if components had optional static hooks like getCachedRenderedString() and saveRenderedStringToCache()? (Naming is strawman)
If getCachedRenderedString() exists, it gets called with props. If it returns a string, that string is used instead of rendering the component. Otherwise, component is rendered, and saveRenderedStringToCache() is called with the props and the string.
Am I fundamentally misunderstanding the problem?

Alternatively there could be a <CachingBoundary> component.
<CachingBoundary hash={hash} saveToCache={...} loadFromCache={...}>
  <RouteHandler />
</CachingBoundary>

On the client it would just render the children, on the server it would be treated specially.

This is not exactly related to this PR, but to SSR in general. Would be nice to have React natively support async data fetching on the server side, something like what react-resolver does.

The discussion on data fetching is a very complex one and I ask to refrain from it from this RFC, or it will get completely derailed. :-)

For example, what if components had optional static hooks like getCachedRenderedString() and saveRenderedStringToCache()? (Naming is strawman)

If getCachedRenderedString() exists, it gets called with props. If it returns a string, that string is used instead of rendering the component. Otherwise, component is rendered, and saveRenderedStringToCache() is called with the props and the string.

This is very close to what I'm proposing but slightly different. I think there are two important concerns here which need to be separate because they will be decided by different people:

Is one rendering of ComponentA that happened in the past the same as the rendering of ComponentA that we are about to do and should we therefore reuse the markup from last time?
We just rendered ComponentA and need to somehow store the results so that we can use it next time.

I think concern 1 is the domain of the component author. It is almost identical to the answer that componentShouldUpdate answers when rendering to DOM (or Native, etc.): is this new render different from the last?
I think concern 2 is the domain of the web app author: should I put the cache in memory on each web server? Or maybe a shared Redis cluster? Or in DynamoDB? MS Access?
The straw man you proposed (getCachedRenderedString() and saveRenderedStringToCache()) conflates these two concerns, I think, and requires the component author to think about how the cache is stored and persisted. I would prefer a method like getCacheKey(props) that returns a string to lookup in the cache and use for adding to the cache. Then I would advocate for a CacheStrategy object that is passed into renderToString that has events for adding to and looking up from the cache. This could be implemented for many different backends (memory, Redis, etc).
Full disclosure: I implemented something like this in react-dom-stream as an experiment: https://www.npmjs.com/package/react-dom-stream#experimental-feature-component-caching
My proposal wouldn't allow for the template feature that @adam-26 wants. I am not as excited by that particular use case, to be frank, but I may not be understanding why it's awesome, so I'm more than happy to hear more about it.

The discussion on data fetching is a very complex one and I ask to refrain from it from this RFC, or it will get completely derailed. :-)

100% agreed. I think that discussion, while important, is totally unrelated to the decisions we make here.

@aickin, I like the concept of introducing a new lifecycle method to get a cache key for a component, it makes adding caching to an application really simple. And clearly separating the responsibilities of rendering and caching definitely reduces complexity. From an implementation perspective, I'm guessing this would be a simpler version of what @gaearon suggested, a single static hook static getCacheKey(props) {...}? No need to create a component instance if its cached.
The original motivation behind the <Template> was to support the ability to inject dynamic content into cached content. A simple example would be, rendering a cached  component and injecting the currently authenticated users <Avatar>. I find that when adding cache to an application its often simpler (in terms of deciding what to cache) to cache with exceptions.
I'm not sure what your opinions on such an approach are, but I think this could be supported with a getCacheKey() static hook method by supporting nested cached components, and it would be much simpler than attempting to use the Template approach. For this to succeed, the following would be required:

when the parent component is rendering to be cached, the unmasked context of the parent and child component would need to be compared to ensure the context has not been changed - if the context has changed then nested component caching can not be supported, display a warning.
returning false from the child components getCacheKey() static hook method prevents the component from being cached (in which case its rendered on every request)
The props to be passed to the nested cache component would also need to be cached with the parent component cache - and passed to the nested component on future renders (when rendering from the cache). There may need to be some restrictions on what PropTypes are supported in this scenario.. I'll need to spend some more time thinking about this - it's probably the most complicated requirement of nested caching.

If you'd like me to provide a more detailed explanation of these points, please let me know.
This may be a little off topic as its regarding implementation specifics, but for requests that use multiple cached components for rendering, I would prefer that cache keys are batched and only a single request is made to the cache provider.
Looking forward to your feedback.

User Space Solution
import React from 'react'
import PropTypes from 'prop-types'

let getHtml
if (!process.browser) {
  const ReactDOMServer = require('react-dom/server')
  const cache = require('lru-cache')({
    max: 1000 * 1000 * 200, // 200mb
    length: d => d.length
  })

  getHtml = (key, children) => {
    if (cache.has(key)) {
      return cache.get(key)
    }
    const html = ReactDOMServer.renderToStaticMarkup(children())
    cache.set(key, html)
    return html
  }
}

const SSRCachingBoundary = ({cacheKey, children}) => getHtml
  ?

  :
{children()}

SSRCachingBoundary.propTypes = {
  cacheKey: PropTypes.string.isRequired,
  children: PropTypes.func.isRequired
}

export default SSRCachingBoundary

Usage
export default ({data}) => (
  <Frame>
    <Loader loading={data.loading} error={data.error} render={() => (
      <SSRCachingBoundary cacheKey={data.article.hash}>
        {() => renderBigTree(data.article)}
      </SSRCachingBoundary>
    )} />
  </Frame>
)

real world example
draw backs

an extra div
no (automatic) context
dynamic requires need to be excluded from webpack with externals

Maybe the solution could be improved upon by passing the cache and a render to html function via context on the server side? Is there something like unstable_renderSubtreeIntoContainer or portals that could be used easily on the server?

I have a few questions related to this RFC and my particular use case which, I think, could add to this discussion. To start, I'll add a quick explanation of my use case. You can skip it if necessary, but I think it explains better what I would like to achieve from a caching standpoint using this RFC.
Basically, I am currently building a page builder using React. I compile the react structure to JSON, save it inside my database and reload it through a GraphQl API on the frontend for rendering.
With this system, I allow the users to create a template (Like a master page in ASP), widgets (Reusable components) and pages. These three component may contain DataSource, which links to the API or the Redux store.
To simplify some of the processes, we have made some considerations :

Unless data has changed (In which case we will invalidate the Redis cache for that specific data), we can consider that, for the same query, the API will always return the same data.
Redux will only be used to keep the general state of the application (If a modal is opened, the offset of a paginated list...) and as hooks to our monitoring strategies.
There will be no statefull components (Except third-party ones)

This keeps the rendering simple and predictable and I can easily cache queries.
To get back to the RFC, I am very interested in the capabilities of templates and how they could allow me to cache the renderer structure. Since my users can pretty much do anything, I need an easy way to cache on a per component basis and inject data in them.
Currently, I use a bunch of HOC to hydrate my components with data from various sources and connect them with their props. Since I don't know what my structure may look like, it's easier to use these than try to create logic in all my available components.
Using templates, how would I be able to know if a children is templated and cached? For example, I have a connectToDataSource HOC that gives a data prop to the children who can then read from it and replace templated props (String literals) with the data there. How would the child get access to that data prop if it is templated so that it can render itself using these templates?
Again with templates, my dataSource component can render the same child(ren) multiple times depending on the data, for example if I had three children with six data entries, it would render this :

Child 1 (Entry 1)
Child 2 (Entry 2)
Child 3 (Entry 3)
Child 1 (Entry 4)
Child 2 (Entry 5)
Child 3 (Entry 6)

How would that be handled with templates? Each of these children would be cached with a template and I would need to choose and hydrate each of them. Would I use a {children} template string that receives the children cached string? (In that case, would the rendering go from leaf to root rather than root to leaf? (I am unsure which one it is right now))
One of my strategies for cache was to cache queries. In my query components, I would use the props as indexes in my redis store and check if an entry less than 24 hours old exists and if yes, take that entry instead. If using an apollo graphQL query, apollo already exposes a function that fetches the data from the API before going to renderToStream, so its fine there. That would probably get into conflict with the caching due to the async nature of queries and cache only "loading" components. Would I need to patch the apollo function that runs through the structure and fetch all data before caching or could this be handled with some kind of wait mechanism to cache loaded components?
Finally, how would caching strategies that need to fetch the cached data from an async location be handled using this method? I could hardly see the rendering wait for the cache to resolve or huge cache be loaded in memory for that (Like in my case where I would be able to cache an theoretically infinite amount of components).
In any case, I can't wait to see where this RFC will go.

I'm very interested in this RFC. Is this topic still active? Recently I'm working on a migration from using ejs template rendering to using React server-side rendering. The overall performance is what I'm concerned about most. A caching strategy could be a great solution.

The problem itself is definitely still of interests. But quite a few things changed in the landscape which make this RFC pretty outdated. We moved to Hooks as the primary API. The SSR is significantly redesigned to support true streaming (waiting for data to load). Server Components (https://github.com/reactjs/rfcs/pull/188) become an important architectural consideration. The exact way they are layered with new SSR is still a question and there is further research needed there. The data fetching story has first-class support for IO sources like disk, databases, etc, built with Suspense adapters. A cache would need to be integrated with these since there would need to be a way to specify what invalidates it (e.g. disk change, timestamp change, and so on). To reiterate, this is an important design area that we're interested in, but the landscape has changed so much that this proposal does not satisfy the needs.


Cannot add DSN connection via a correct DSN string

Description
The error cannot open connection: only DSN connections supported is thrown
Reproduction steps

Click on Connections
Insert metadata for connection
Go to “Data access layer configuration and connection parameters”
Insert
postgres://corteza:corteza@localhost:5432/d1?sslmode=disable
Or
postgres://corteza:*********@corteza_db:5432/testfest?sslmode=disable

Expected behavior
There should be a different error string if the database is unreachable OR the connections should be successfully added.
Screenshots/Videos

Tested on
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/111.0
Version
2023.3.0-dev.5

for today: update ticker with plan and start executing it

for today: update ticket with plan and start executing it


CLEANUP: Read over the changes and tidy small things

"Cleanup" sounds ominous, but its mainly two things:

Names for many constants
No updates inside of Draw() calls

YOLO

(Can't comment on the specific lines as on my mobile)
Is it worth using an SFX_DEFAULT_CHANNEL = 3 rather than redefining channel 3 for each separate effect?

Is it worth using an SFX_DEFAULT_CHANNEL = 3 rather than redefining channel 3 for each separate effect?

Probably? I also thought about putting all the sound channel constants in cart.go so we could manage allocations in one place. It's also probably fine to just leave it for now and worry if we start getting clashes.


Update backend APIs to cast SQL results back to Java record then to Json

backend APIs related to MetadataChangeEvent will cast the Mysql query results Map<String, Object> to corresponding Java Record, then serialize the record to Json and send to REST reply. This way, the post and get Json format is consistent.
This is for better debugging and easier frontend usage.
Also correct the multiple escape characters in return Json string issue.

This change is needed to keep the JSON payload easy to consume.
Ship it!


Configuring github authentification in Spring

Since we don't really need to wait for #3 to configure our authentication. We might as well set that up before closing #3.

We did not get to implement this one, so I will close it.


Images as Data URLs

Since we don't support IE8-, I would like to bring up images Data URL topic again (#979).
We can use rollup-plugin-url to import images and convert them to data URLs.
Pros:

get rid of all magic related to images path detecting
it will work properly in any build environment (webpack/browserify/rollup etc.)
no need to include images folder into dist
supported in IE8+ MDN docs

Cons:

increased js file size (from 38Kb to ~47Kb)
all images will be included regardless of images are used or not

We could also use data URLs only for marker icons & shadow and leave layers images as is (in CSS).

Hi,
In the cons I would add the higher performance penalty issue when there are lot of markers with inlined image v.s. standard image, as profiled by @perliedman.

We could […] leave layers images as is (in CSS).

Sounds very reasonable to me in any case, since the Layers Control images use a very standard CSS url() that does not depend on the Leaflet path detection magic. Therefore it is in the standard usage that build tools expect (typically webpack).

Hi,
thanks for commenting.
Performance and size are crucial here, so I think it isn't worth it.
Also, I noticed that we still support IE 7 ;)


PHP imported navigation bar overlaps header

http://opensprites.x10.mx/live/alpha/

Setting the padding of #pagetable to >35 causes it to not overlap.

It works now, thanks.


Reading vcf failed

Hello,
I received a Outlook generated vCard file (see listing down, can't attach a file to this issue).  The file was generated and not modified manually. This file is a small export of a large Outlook database. vcard-json isn't able to read this file.
But:

Windows 7 (without Office) isn't able to open this file (error message: does not seem to be a valid vcard file)
Mac OS can open this file, but can't find any vCard inside

Do you think, that this file can be managed by vcard-json?
###################
BEGIN:VCARD
VERSION:3.0
N:Mustermann;Hubert;;;
FN:Mustermann Hubert
TEL;type=HOME;type=pref:069123456
<EMAIL_ADDRESS>END:VCARD
###################
Tobias

Hey Tobias, I just tested the sample you posted and it worked fine. Do you have a sample output that is failing?

Hi,
Could it be an encoding orline break issue? Unfortunatelly, I can't attach the file (even as txt) to this issue.
the exception happens in line "_.each(attributes, function(attribute){" :
2015-09-28 11:17:59.060  - error: TypeError: Cannot set property 'fullname' of undefined
at EventEmitter.attributeMatched (c:\Program Files\ioBroker\node_modules\iobroker.vCard\node_modules\vcard-json\lib\vcard-json.js:72:24)
at EventEmitter.emit (events.js:118:17)
at c:\Program Files\ioBroker\node_modules\iobroker.vCard\node_modules\vcard-json\lib\vcard-json.js:45:12
at Function..each..forEach (c:\Program Files\ioBroker\node_modules\iobroker.vCard\node_modules\vcard-json\node_modules\underscore\underscore.js:158:9)
at c:\Program Files\ioBroker\node_modules\iobroker.vCard\node_modules\vcard-json\lib\vcard-json.js:40:7
at Function..each..forEach (c:\Program Files\ioBroker\node_modules\iobroker.vCard\node_modules\vcard-json\node_modules\underscore\underscore.js:153:9)
at parseVcard (c:\Program Files\ioBroker\node_modules\iobroker.vCard\node_modules\vcard-json\lib\vcard-json.js:23:5)
at c:\Program Files\ioBroker\node_modules\iobroker.vCard\node_modules\vcard-json\lib\vcard-json.js:61:26
at fs.js:334:14
at FSReqWrap.oncomplete (fs.js:95:15)

It could be a line break issue, but it's hard to say for certain without having a test case. The actual error is from line:72 due to the contact object being undefined:
contact.fullname = s(line.slice(3)).clean().value();
This means it's not recognizing the start of the file where it declares the beginning of the vcard:
BEGIN:VCARD
I should clean that up but that won't solve your current problem.
Did you try dragging the text file directly into this comments section?

Hi,
sending per github comment didn’t work. I’ll try it in this way
Tobias

Am 29.09.2015 um 06:26 schrieb Steven Elliott<EMAIL_ADDRESS>It could be a line break issue, but it's hard to say for certain without having a test case. The actual error is from line:72 due to the contact object being undefined:
contact.fullname = s(line.slice(3)).clean().value();
This means it's not recognizing the start of the file where it declares the beginning of the vcard:
BEGIN:VCARD
I should clean that up but that won't solve your current problem.
Did you try dragging the text file directly into this comments section?
—
Reply to this email directly or view it on GitHub https://github.com/steven-elliott/vcard-json/issues/2#issuecomment-143940644.

Not seeing anything. You can find my contact info here and send the text via email - http://stevenelliott.me/

Fixed in v0.4.1


4.x Refactor AppTest To Use Prophecy

This is a continuation of migrating towards the usage of phpspec/prophecy.

Prophesized PSR-7 Object Interfaces
Prophesized ContainerInterface
Prophesized MiddlewareInterface
No more deprecated $this->assertAttributeEquals() calls!

@bnf and @akrabat please review!

Coverage decreased (-0.2%) to 98.336% when pulling 630bd99631365b5e3b964577b9d3843b2b26ef0d on l0gicgate:4.x-RefactorAppTestProphecy into df28dcc3d813769d3b583b913f1aa72b7a2cf891 on slimphp:4.x.

@bnf please re-review. Just fixed all the requested changes!


Trying to fix this sharp issue

Hello! I don't know what is happening here. When running npm start on my repo, it is giving me an error:
Eleventy fatal error: (more in DEBUG output)

Error in your Eleventy config file '/Users/carlosdiazplaza/11ty-netlifycms-templateforclients/.eleventy.js'.

EleventyConfigError was thrown

Something went wrong installing the "sharp" module

dlopen(/Users/carlosdiazplaza/11ty-netlifycms-templateforclients/node_modules/eleventy-plugin-lazyimages/node_modules/sharp/build/Release/sharp.node, 0x0001): symbol not found in flat namespace '__ZTVN4vips7VOptionE'

Remove the "node_modules/sharp" directory then run
"npm install --ignore-scripts=false --verbose" and look for errors
Consult the installation documentation at https://sharp.pixelplumbing.com/install
Search for this error at https://github.com/lovell/sharp/issues

Error was thrown:
Error:
Something went wrong installing the "sharp" module
dlopen(/Users/carlosdiazplaza/11ty-netlifycms-templateforclients/node_modules/eleventy-plugin-lazyimages/node_modules/sharp/build/Release/sharp.node, 0x0001): symbol not found in flat namespace '__ZTVN4vips7VOptionE'

- Remove the "node_modules/sharp" directory then run
  "npm install --ignore-scripts=false --verbose" and look for errors
- Consult the installation documentation at https://sharp.pixelplumbing.com/install
- Search for this error at https://github.com/lovell/sharp/issues

    at Object.<anonymous> (/Users/carlosdiazplaza/11ty-netlifycms-templateforclients/node_modules/eleventy-plugin-lazyimages/node_modules/sharp/lib/constructor.js:34:9)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/Users/carlosdiazplaza/11ty-netlifycms-templateforclients/node_modules/eleventy-plugin-lazyimages/node_modules/sharp/lib/index.js:3:15)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)

carlosdiazplaza@Carloss-MacBook-Pro 11ty-netlifycms-templateforclients %
I don't know what is happening. Anyone can help me out? Thanks! Here is my repo URL: https://github.com/talmax1124/11ty-netlifycms-templateforclients

Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?
What is the complete output of running npm install --verbose sharp?
What is the output of running npx envinfo --binaries --system?

[Log.docx](https://github.com/lovell/sharp/files/7613224/Log.docx)
Here is the output.
@lovell

It looks like eleventy-plugin-lazyimages relies on an older version of sharp that does not support Apple M1.
https://github.com/liamfiddler/eleventy-plugin-lazyimages/blob/08c0624d7aa95f71ff3b4597ce84c3f67aeca759/package.json#L30
https://sharp.pixelplumbing.com/install#apple-m1

Ok, thanks! Let me try it now!

Hello! This worked! Thanks!

Great, perhaps you could submit a pull request to the https://github.com/liamfiddler/eleventy-plugin-lazyimages repo that upgrades sharp and helps prevent others running into the same problem.

Well, i just removed the plugin.

What version specifically supports the M1? @lovell

https://sharp.pixelplumbing.com/install#apple-m1
If you're upgrading, please upgrade to the latest.


ServiceRequest.requester 0..1 versus zib requester 0..*

In our current modelling, we have mapped the zib Procedure concept 'Requester::HealthProfessional' on ServiceRequest.requester. However, the cardinality does not match.

In addition, Procedure.extension:procedureMethod has a cardinality of 0..1, which doesn't match with ProcedureMethod from the zib, which has a cardinality of 0..*.

The CIM has 0..* for requester and then says "The healthcare provider who requested the procedure."
In the HL7 Validation Team we were unable to come up with a situation where more than 1 requester is applicable. Suggest to file a CIM-ticket for this and ask if 0..* is a typo

Zib issue created: https://bits.nictiz.nl/browse/ZIB-1488

Since there's a preliminary answer and so far, there seems to be agreement that the cardinality of the zib is too wide, this issue can be closed.


Update Get-MailDetailATPReport.md

Issue #7631

Docs Build status updates of commit 7bf908b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-MailDetailATPReport.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Nuget packaging

Nuget package restore was enabled (for the whole solution, but actually used only for Tests project)
DataAnnotationsValidator assembly was signed with a strong name key file
Nuspec file was added for packaging nuget package
Automatic build was added on a public TeamCity continuous integration server: http://teamcity.codebetter.com/viewType.html?buildTypeId=TeamCityZen_DataAnnotationsValidatorRecursive_DataAnnotationsValidatorRecursiveD
Package was published using the automatic build to nuget: https://www.nuget.org/packages/DataAnnotationsValidator/

Thanks @borismod


How to choose 300k images from these datasets?

Hi, thanks for your excellent work.
I collected the 6 face datasets you mentioned and attempted to train the model by myself, but result was worse than yours. can you provide your datalist and let me know how to choose 300k images?

Hi has this issue been addressed? I'm struggling with the same problem. I have all datasets except IJB-A (Now known as IJB-C). The dataset that I have right now is well over 300K images for me, maybe even 500K, but the trained model is somehow worse than the original.


Aging work table: When an aging cutoff is in use, make that visible and obvious

It isn't obvious enough today why items don't show in the report. Perhaps a black dividing line or a label.

Done


Fix Date: headers... again.

Seems that GMail thinks it knows better and demotes our finely-crafted Date: header and replaces it with its inferior version (reported by @gitster himself).
 Actually, I guess it would be something like this:
function sleep(ms: number) {
    return new Promise( resolve => setTimeout(resolve, ms) );
}

Was this fixed by the GMT to +0000 change in PR #125?  Not really sure what the sleep was going to do.

Was this fixed by the GMT to +0000 change in PR #125?

Yes!
Thank you for your diligence!

Not really sure what the sleep was going to do.

This was my ugly workaround (because I missed @tgummerer's excellent analysis) to force the GMail-generated Date: header to show subsequent timestamps.
I am so happy that I don't have to resort to that!


Expanded Docs for Query Language After Middle-Level API is Merged

This is a follow up to https://github.com/hatchet/hatchet/pull/336.
It expands the documentation added in that PR to include new query language features, such as the compound query operators and middle-level API.
Also, at @pearce8's request, I've added a table of query language features. This table will show what API levels have what features.

From June 7, 2021:
Here's screenshot of the table that @pearce8 requested

This PR is defunct given various changes in terminology and presentation made in preparation for the Query Language paper. I'm leaving it open for reference until we can start a better documentation PR.
Please do not merge.

Replaced by #90


Enhancement: Centralize page for hostname definition

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

What page(s) or areas on docs.getdbt.com are affected?
The purpose of this issue is to have a separate page that explains what a hostname means for MT and ST instances in more detail, and can serve as the centralized page that lays out hostname and its meanings for different regions. This issue is indirectly related to PR #783
Resources
Affected pages:

https://docs.getdbt.com/docs/dbt-cloud/dbt-cloud-enterprise/setting-up-sso-with-saml-2.0
https://docs.getdbt.com/docs/dbt-cloud/cloud-configuring-dbt-cloud/connecting-your-database

Proposal
The hostname field can live here potentially and include the following information:

instance/hostname IP address
instance/hostname URL
region where the instance is hosted,
dbt Cloud account number example (ST instances have a combination of numbers and letters)

What changes are you suggesting?
Changes are being suggested to have a centralized location of the definition of hostname. This is important as dbt Cloud multi-tenant scales to other regions and will also allow users/docs team to link out to that definition page, where appropriate. This keeps content aligned and centralized, and if any changes need to be made, they are made in one page.
Additional information
No response

I think this page resolves this issue, but feel free to open, Mirna, if I'm wrong.


application-plugin: Make the wrapper scripts REUSE compliant

Context
The Free Software Foundation's REUSE tool 1 ensures that all files in a repository have license and copyright information declared. Gradle projects that have the wrapper committed and want to be REUSE compliant so far needed to explicitly declare the license for the scripts as part of the .reuse/dep5 file. Avoid that need by adding SPDX identifier tags to the wrapper scripts, see 2.
Contributor Checklist

[x] Review Contribution Guidelines.
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
[ ] Provide unit tests (under <subproject>/src/test) to verify logic.
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
[x] Ensure that tests pass sanity check: ./gradlew sanityCheck.
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

Thank you for your contribution!
This PR is complete and simple enough, it will be merged immediately.

The merge queue build has failed. Click here to see all failures.

gradle-wrapper.properties should also get appropriate SPDX-FileCopyrightText and SPDX-License-Identifier comment entries.

The merge queue build has failed. Click here to see all failures.

gradle-wrapper.properties should also get appropriate SPDX-FileCopyrightText and SPDX-License-Identifier comment entries.

You're probably right. Unfortunately, that's a bit more work as WrapperGenerator.writeProperties() calls PropertiesUtils.store() which overwrites any existing file contents, so simply adding a header to gradle-wrapper.properties before properties get written would not work.


Plugin incompatible with Gradle 8.0

What kind of issue is this?

[ ] Question. This issue tracker is not the place for questions. If you want to ask how to do
something, or to understand why something isn't working the way you expect it to, use Stack
Overflow with the android-groovy tag.

[ ] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests
get fixed. See here
for some example tests.

[x] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.

Hello, I recently updated my project to Gradle 7 and found out I still get deprecation warnings. After running my build with --warning-mode all I have seen:

The AbstractCompile.destinationDir property has been deprecated. This is scheduled to be removed in Gradle 8.0. Please use the destinationDirectory property instead. Consult the upgrading guide for further information: https://docs.gradle.org/7.3.3/userguide/upgrading_version_7.html#compile_task_wiring

Which may be caused by usage of destinationDir in groovy-android-gradle-plugin. Apparently Gradle has deprecated destinationDir in compile task.
The feature request would be to make the plugin use Gradle 7 for build and being compatible with Gradle 8.

邮件我已经收到