Add SpaceportRemapTitle and fix SpaceportRemapDescription/ SpaceportRemapKey

Add support for SpaceportRemapTitle and fix up SpaceportRemapDescription/ SpaceportRemapKey for the remaps screen.

Thanks for the PR!
I just added a change that allows titles to be SpaceportWord's instead of plain strings (something I should have done a while ago, I was just too lazy to do it until necessary). Most of the other changes look really good especially the new name screen you put up. If there's any other changes you would like to make, let me know, otherwise I will merge this tomorrow.

yeah there's not really support for doing icons or anything like that right now, so i might have to make a few additions to some areas to improve that but i havent really figured that out yet. so if you could wait a few days before trying to implement that, that would be great!

I would like to give my proposal for a solution, feel free to shoot it down if you already have something else implemented or if you simply don't like it.
My idea is to add opts for something like titles and icons, something like this (init.lua)
local opts = {
-- ...
    titles = {
        Remaps = "Remaps",
        Pinned = "Pinned",
        Today = "Today",
        Yesterday = "Yesterday",
        Week = "Past Week",
        Month = "Past Month",
        Long = "A long time ago",
    },
    icons = {
        File = "",
        Dir = ""
    },
-- ...
}

And using a get function like sections is doing (init.lua):
---@return string
---@param title string
function M._getTitle(title)
    -- M.log(opts.titles[title])
    if opts.titles[title] then return opts.titles[title] else return title end
end

---@return string
---@param icon string
function M._getIcon(icon)
    -- M.log(opts.icons[icon])
    if opts.icons[icon] then return opts.icons[icon] else return icon end
end

After this screens like recent or remaps can call these functions to get the values associated with the opts, as an example of how this can be used in recent for pinned:
-- ...
    if #pinned > 0 then
        lines = {
            "",
            { { require("spaceport")._getTitle("Pinned"), colorOpts = { _name = "SpaceportRecentsTitle" } } },
        }
        for _, v in ipairs(pinned) do
            linesToDir[#lines + 1] = i
            local prefix = require("spaceport")._getIcon("File")
            if v.isDir then prefix = require("spaceport")._getIcon("Dir") end
            ---@type SpaceportWord[]
            local words = {
                { prefix .. " " .. v.prettyDir, colorOpts = { _name = "SpaceportRecentsProject" } },
                { i .. "",     colorOpts = { _name = "SpaceportRecentsCount" } },
            }
            table.insert(lines, require("spaceport.screen").setWidthWords(words, largestLen))
            i = i + 1
        end
    end
-- ...

By doing it like this there should not be any breaking changes while still giving the user the options for icons and custom naming. By not including icons with the defaults there is no need to depend on specific icon packs.
As an example of how the user config could looks like:
require("spaceport").setup({
	sections = { "_global_remaps", "name_blue", "remaps", "recents" },
	titles = {
		Remaps = " Remaps",
		Pinned = " Pinned",
		Today = " Today",
		Yesterday = " Yesterday",
		Week = " Week",
		Month = " Month",
		Long = " Longer",
	},
	icons = {
		File = "",
		Dir = "",
	},
})

I really like your idea to have file and directory icons. I think we could provide some default nerdfonts that can just be set via something like icons = true and icons can be disabled via icons = false. Then they could specialize them with icons = { ... } like you have right now.
I am not as much a fan of your way of changing the titles. It feels a little to non-generalized for me which makes me feel like it would become a pain point in the future. Preferably, I could provide a way of overriding the configuration of a section. Probably something like:
sections = {
  {
    "remaps",
    title = " Remaps",
  },
  "name_blue"
}

This would also allow users to change remaps and descriptions and custom configurations for each section.
One thing I would really like to do is split up the recents section into multiple sections (eg pinned, today...). The only reason it's not like that right now is because when I tried to do it a while back, it was really ugly.
Anyway, I would like to know your thoughts on these ideas, and I might push a few changes along theses lines.

I think we could provide some default nerdfonts that can just be set via something like icons = true and icons can be disabled via icons = false. Then they could specialize them with icons = { ... } like you have right now.

I think if we also have icons set to a non-false value we can override the titles of sections to include icons

Using a config property would definitely be better, this is way less clunky than my title idea and allows for easier expansion in the future. I'm still quite new to plugin design principles so thanks for bearing with me.
I also like the idea of merging the name screens, as this will also prevent clutter in case more logos are added.
Regarding the documentation of the config property, I'll think a short description under the Customization header will do (with the example above it updated accordingly), for eq:

name: This section displays an ascii art "Spaceport" logo

style: Set a predefined style, choices: hash
gradient:  Set a predefined gradiant, choices: white, blue, blue_blue

Regarding splitting up the recent section, I see what you're getting at but don't think that's a good idea as it does increase complexity quite a lot.  This would also need consideration of which the month section should include the last week as the week section should cover this but might not be picked by the user.
Maybe an option for selectively enabling/ disabling the titles in some way would do the trick if a single big list is desired, maybe like this although it isn't very pretty:
sections = {
  {
    "recent",
    config = {
      titles = {
       today = true,
       week = false,
       month = true,
       long = false
      }
  }
}

At last, I'll get the commit for the icons ready, It will come when it's ready.

I think we could provide some default nerdfonts that can just be set via something like icons = true and icons can be disabled via icons = false. Then they could specialize them with icons = { ... } like you have right now.

I think if we also have icons set to a non-false value we can override the titles of sections to include icons

If I'm getting this right do you mean in a sense that icons can be configured like:
require("spaceport").setup({
	icons = {
		File = "",
		Dir = "",
		Remaps = "",
		Pinned = "",
		Today = "",
		Yesterday = "",
		Week = "",
		Month = "",
		Long = "",
	},
})

And that the _getIcon() function can be used to prefix the titles?
Or do you mean that instead of prefixing the icon value can be used to completely replace the title?
I'm guessing you mean prefix.

If I'm getting this right do you mean in a sense that icons can be configured like:
require("spaceport").setup({
	icons = {
		File = "",
		Dir = "",
		Remaps = "",
		Pinned = "",
		Today = "",
		Yesterday = "",
		Week = "",
		Month = "",
		Long = "",
	},
})

And that the _getIcon() function can be used to prefix the titles?
Or do you mean that instead of prefixing the icon value can be used to completely replace the title?
I'm guessing you mean prefix.

Yeah, we should add prefixes for the other title options as well. Also, could we not have the keys for the icons table to be capitalized

I changed the icons to be non-capitalized, as that is just my personal preference. I also simplified the getIcons function to be a little easier to read

I also just added the ability to modify the name screen (and also moved the name_blue_green and name_blue into the name screen)

yeah, sorry about the formatting issues. I never use tabs, so idk how they got in there. I added a .editorconfig, so you should just be able to vim.lsp.buf.format() and it should all work now. I would rather not remove name_blue and name_blue_green right now just in case anyone is using it.
Also, what highlight group are you linking to for the titles? or are you just using specific colors for your title highlights? I would like some good default colors for items besides just linking everything to the Normal hl group.
Anyways, unless you have some other changes you would like to suggest, I feel like this PR is ready to merge right now

Currently, I run this config (Lazy)
return {
	{
		-- "CWood-sdf/spaceport.nvim",
		dir = "/home/handygold75/Repos/spaceport.nvim",
		name = "spaceport",
		lazy = false,
		config = function()
			local _local_remaps = {
				lines = {},
				topBuffer = 0,
				title = nil,
				remaps = {
					{ mode = "n", key = "h", description = " Home", action = function() require("spaceport.data").cd({ dir = "~/", isDir = true }) end },
					{ mode = "n", key = "df", description = " DotFiles", action = function() require("spaceport.data").cd({ dir = "~/.dotfiles/", isDir = true }) end },
					{ mode = "n", key = "l", description = "󰒲 Lazy", action = ":Lazy<CR>" },
					{ mode = "n", key = "m", description = " Mason", action = ":Mason<CR>" },
				},
			}

			vim.api.nvim_set_hl(0, "SpaceportRemapTitle", {
				fg = "#9999FF",
			})
			vim.api.nvim_set_hl(0, "SpaceportRecentsTitle", {
				fg = "#9999FF",
			})

			require("spaceport").setup({
				projectEntry = "NvimTreeOpen",
				replaceHome = true,
				lastViewTime = "pastMonth",
				sections = {
					{ "name", config = { style = "lite", gradient = "blue" } },
					"remaps",
					"recents",
					_local_remaps,
				},
			})
		end,
		keys = {
			{ "<leader>sp", ":Spaceport<CR>", { "n" }, desc = "[s]pace[p]ort" },
		},
	},
}

Which results in these visuals

I'm not familiar with highlighting groups at all so I just bound them to specific colors that work with my color scheme, this would be a bad default IMO. Maybe if you want to include some parts as examples but that is up to you.
Feel free to merge the PR for the moment I'm through my ideas on improvements.

yeah that makes sense. anyway, thanks for all your help on this PR!


expose metrics

Is it possible to expose all metrics in serenade for test, when doing hyper param optimization.
(MRR@20, HR@20, COV@20, POP@20, P@20, R@20)

The new version v0.2.6 contains an extra application 'evaluator'
This application can evaluate a testset and reports the prediction metrics and the prediction latency.
Please download the latest release and the updated 'example.zip' file in order to use it.


Can not sign up using the desktop app ("Please wait a bit, we are still getting your account ready.")

Can not sign up using the desktop app on MacOS. I get "Please wait a bit, we are still getting your account ready." combined with "Failed to fetch." each time I click the "Sign Up" button after I have filled in email and password. I also get the same message ("Please wait"...) each time I try to follow someone (when using without being signed in). Watching videos, boosting, tipping and reposting still works fine and I have some LRBY in my balance.
LBRY 0.51.2

Interesting. I just tried on the alpha.9 rc - signed up, signed out, signed in again and it seemed to work.
Not saying you're crazy but maybe apis were down at the time.

closing for now - reopen if it happens more.

Actually I have concluded the issue is probably my ancient version of MacOS. I'll re-open if it turns out to not be the case once I upgrade. Thank you.


Can we have a B2C example added to this page

[Enter feedback here]

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

ID: d0da2144-3730-f8ef-1d16-a89f11fd6198
Version Independent ID: 6d8f5bc8-8f5c-ba13-b7f2-0366eac46f81
Content: Authentication and authorization in ASP.NET Core SignalR
Content Source: aspnetcore/signalr/authn-and-authz.md
Product: aspnet-core
Technology: aspnetcore-signalr
GitHub Login: @bradygaster
Microsoft Alias: bradyg

@bradygaster, Do we already have an example somewhere that would be appropriate?  Thoughts on priority?


5975 box integration

This closes #5975. Integration code is similar to GDrive and Dropbox ones. Box specifics:

Refresh token is one use only.
Search is broader.

@Kartones CR this, please.

Tests passed

:+1:  Nice small refactor of BaseOAuth stuff plus the unexpected work of backporting Box api to 1.9.3.


problem with react 17

your scrollbar is not compatible with react 17 can you fix that

@malte-wessel could you give 1 other person write permissions to maintain the library. Or archive it if you don't want to do that either?

@malte-wessel ping

bump

bump


import  OnMyLocationClickListener fails, cannot resolve

hi,
tried the sample but the line
import com.google.android.gms.maps.GoogleMap.OnMyLocationClickListener; gives me a unresolved error, how can i fix it and what causes it?

it seems the latest version is needed but not available in android studio:
Failed to resolve: com.google.android.gms:play-services:11.4.0

just deleted the class MyLocationClickListener, i guess it's not supported.
and in the gradle file:
use this dependency:
compile 'com.google.android.gms:play-services-maps:11.0.4'
instead of this:
compile 'com.google.android.gms:play-services-maps:11.4.0'
(it's version number: 11.0.4 and not 11.4.0)

You can solve this putting GoogleMaven in build.gradle
allprojects {
    repositories {
        mavenLocal()
        jcenter()
        maven {
            url 'https://maven.google.com/'
            name 'Google'
        }
    }
}

This has been fixed in pull request #79


[Issue]: gfx1100  is invalid or not supported by Flash-Attention

Problem Description
gfx1100  is invalid or not supported by Flash-Attention
Operating System
ubuntu22.04
CPU
Intel(R) Xeon(R) w5-3435X
GPU
Radeon RX 7900 XTX
ROCm Version
ROCm 6.2.3
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response

https://github.com/ROCm/flash-attention/issues/88#issuecomment-2441852581


Upgrade to sbt-site-1.2.1

Fixes #1247
See https://github.com/sbt/sbt-site/commit/9f66884090c2a559914e3a1bcf391ed5f87a1250

Score 1 For the Good Guys! Nice Catch on the easier fix Ross.

Yeah, this bit me a couple weeks ago at work.  It looked familiar.  :)


Added C# Multiplication Table

Why:
Closes #630
What's being changed:
Added a C# Multiplication Table
Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Hey @Dentyr
Thanks for contributing to this project 😃
This PR will be reviewed and merged shortly


UI: Nephio branding support

Branding is now supported in the Config as Data UI. This has been completed with https://github.com/GoogleContainerTools/kpt-backstage-plugins/pull/206 where the UI can be themed via configuration.

Config as Data UI App Configuration for Nephio Branding:
    backend:
      # Content Security Policy
      csp:
        # Allows images to be pulled from GitHub and Nepio
        img-src: ["'self'", 'data:', 'https://raw.githubusercontent.com', 'https://nephio.org']

  configAsData:
      # Nephio branding customizations
      branding:
        title: Nephio
        header:
          logoUrl: https://raw.githubusercontent.com/nephio-project/one-summit-22-workshop/main/images/nephio_logo_colorwhite_horizontal.svg
          backgroundImageUrl: https://nephio.org/wp-content/uploads/sites/6/2022/04/Hero-1.png


GPflow2: Fix behaviour of likelihood quadrature tests

For now, this is the MWE for #1082

The equivalent changes to develop (GPflow 1) in #1081 pass (the is_analytic in there was correct, but also only tested for predict_density having been overwritten)

So turns out the bug was that the Y used for testing the likelihoods was random-normal values, but some likelihoods (e.g. Gamma, Exponential) can only handle positive values and others have further restrictions (e.g. Beta). I've now copied over the corresponding randomness choices from develop, and now all tests pass.
Caveat: there were some issues with the MultiClass likelihood. I've for now marked those tests as skipped - I think it's better to have that as an open issue & deal with later but merge this PR.

@st-- , you need to fix your editor to 100 chars per line (GPflow always used 100 lines) ;)

@awav all my changes are <100 character lines? I even fixed one line that had more beforehand. If you have any issue with any line in particular please let me know!

@st-- , why this changes with formatting happened then? Can you revert them back, it is actually distracting :(

@awav I have no idea what formatting changes you're talking about, and I can't revert what I don't know. It'd be more helpful if you added a comment to the code you are referring to, not here!


README Screenshots

Need to add screenshots to the README file once the CSS is finalized.

Added screenshots and reference information to the README.


Support more filenames in link-to-changelog-file

LINKED ISSUES: Closes #3999

TEST URLS:

CHANGELOG.md
CHANGELOG.rst
CHANGES
news
HISTORY.md
note: for every URL, there are two things to test:

going directly to the release page
going to the repo root (with a cleared cache), then to the release page

repository() {
	  object(expression: "HEAD:") {
		  ...on Tree {
			  entries {
				  name
			  }
		  }
	  }
}

This grabs both files and folders. Should we add type under entries and check that it's "blob" (and not "tree")?

repository() {
	  object(expression: "HEAD:") {
		  ...on Tree {
			  entries {
				  name
			  }
		  }
	  }
}

This grabs both files and folders. Should we add type under entries and check that it's "blob" (and not "tree")?

Dont think so. I though about it when I made the feature. @fregante thoughts?

https://github.com/sindresorhus/refined-github/issues/3930#issuecomment-782605909
Can you check this out?


windows-bindgen should only optionally depend on rayon

Suggestion
This is only used for generating packages - windows and windows-sys - and is otherwise unnecessary.

It greatly speeds up generation of such crates and making it an optional dependency complicates things more than I'd like. I'll probably find a lighter replacement at some point but for now it can just stay as is.


Configuring Jest to work with Haul

I wanted to share how I was able to get jest tests running in a compatible way with Haul. I ran into some issues at first, if we think it's worth while I'd be glad to contribute to documentation.
The first issue I ran into was this:
 FAIL  app/__tests__/App.test.js
  ● Test suite failed to run

    The name `react-native` was looked up in the Haste module map. It cannot be resolved, because there exists several different files, or packages, that provide a module for that particular name and platform. The platform is generic (no extension). You must delete or blacklist files until there remains only one of these:

      * `/Users/joltdev/jolt/code/universal/node_modules/haul/src/utils/__tests__/fixtures/node_modules/react-native/package.json` (package)
      * `/Users/joltdev/jolt/code/universal/node_modules/react-native/package.json` (package)

      at ModuleMap._assertNoDuplicates (node_modules/jest-runtime/node_modules/jest-haste-map/build/module_map.js:128:11)
      at Object.<anonymous> (app/App.js:2:18)

Jest does not use Haul or Webpack to actually transpile your code, so it runs into haste module issues.  You can resolve this by configuring Jest to ignore Haul's test version of react native in your package.json. Add the "modulePathIgnorePatterns" option to your Jest config like so:
"jest": {
    "modulePathIgnorePatterns": ["<rootDir>/node_modules/haul/src/utils/__tests__/fixtures/node_modules/react-native/package.json"]
}

Now your tests will not fail for components that try to import react-native
The second issue I ran into was getting tests to resolve modules in the way I had configured in Haul.  I have a root "app" directory that I added to the resolve modules so that I could conveniently import anything in that directory (such as components)
Here is my webpack.haul.js:
module.exports = function getHaulWebpackConfig(options, defaults) {
  return {
    entry: './index.js',
    module: {
      ...defaults.module,
    },
    resolve: {
      ...defaults.resolve,
      modules: ['app', 'node_modules'],
    },
  };
};

In order for Jest to also respect this module resolution, you need to add it to the config in your package json.  Add the "moduleDirectories" option like so:
"jest": {
    "moduleDirectories": [
      "app",
      "node_modules"
    ]
}

I hope this is helpful, I wonder if it would be worth documenting some tips like this to get Haul and Jest tests working better together.

You should be good with just:
"jest": {
  "modulePathIgnorePatterns": ["haul/.*/__tests__/.*"]
}

Can you confirm? We're going to move these test fixtures anyway, so we can use them as an example to test end to end.

@thymikee This config works for me.

Actually, we shouldn't publish tests and fixtures, so I'd treat it as a bug currently.

@thymikee Oh yes that is a much simpler ignore pattern that works great!  Glad to hear the text fixtures will be un-published


No valid audio data received. You may be using a device that can't record audio.

No valid audio data received. You may be using a device that can't record audio.

C:\Users\Admin\Documents\IM\node_modules\react-native\Libraries\BatchedBridge\NativeModules.js:80:57
__invokeCallback
C:\Users\Admin\Documents\IM\node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:354:19

C:\Users\Admin\Documents\IM\node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:129:28
__guard
C:\Users\Admin\Documents\IM\node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:269:6
invokeCallbackAndReturnFlushedQueue
C:\Users\Admin\Documents\IM\node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:128:17

Please provide more details - closing for now

I came across this issue when calling the recording and then the stop recording functions too quickly on android.
In my application, I have a button where you press down to record, and release to stop recording. If you tap too quickly, this occurs. Does not happen on IOS.

I have the same issue with you. Do not know if there is a solution?

I ended up using setTimeout, so that it waits a minimum of 100 ms, before the stop recording function can be called.

Does it work for iOS simulator?

Any solution for this?

Any solution for this?


CurveAnimation doesn't flip its curve when its parent goes from reverse to forward or vice versa without going through the dismissed/complete state first.

because of this code in CurvedAnimation, CurveAnimation doesn't flip its curve (from forward to reverse) when its parent goes from reverse to forward or vice versa without going through the dismissed/complete state first:
  void _updateCurveDirection(AnimationStatus status) {
    switch (status) {
      case AnimationStatus.dismissed:
      case AnimationStatus.completed:
        _curveDirection = null;
        break;
      case AnimationStatus.forward:
        _curveDirection ??= AnimationStatus.forward;
        break;
      case AnimationStatus.reverse:
        _curveDirection ??= AnimationStatus.reverse;
        break;
    }
  }

@apwilson
Could you provide us a complete code sample that shows the issue you described ?
Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


keymap.lua: Fix duplicate keymap detection

'listen' has some code in it to try to not re-set a map for an existing mapping, by checking the 'desc' of the table returned from 'get_map'. Since 'desc' was never included in the table returned from 'get_map', I'm assuming my changes here were always the intention.
This change seems to fix an issue I was seeing (with cmp-nvim-ultisnips at least) where every time I'd enter and leave Insert mode, seemingly another <Tab> handler was getting registered, overtime causing <Tab> in Insert mode to get slower and slower.

thank you. It was my silly mistake.


Slack notification preview problem.

Discussed in https://github.com/test-results-reporter/testbeats/discussions/125

Originally posted by kartal-huseyin March 28, 2023
Since our report includes just inputs as an attachment. I think we requrie to send a text with the report. How to put a text in to report.

Yes, I have the same issue, please include something like Results: 26 / 38 Passed (68%) in the fallback.


Issue-Fixes footer styling

Automated Review Comments
Issues in src/components/App.tsx:

(2, 'Hardcoded string found')
(3, 'Hardcoded string found')
(7, 'Line exceeds 80 characters')
(12, 'Hardcoded string found')
(15, 'Hardcoded string found')
(16, 'Hardcoded string found')
(28, 'Line exceeds 80 characters')
(29, 'Line exceeds 80 characters')
(32, 'Hardcoded string found')
(35, 'Hardcoded string found')
(38, 'Hardcoded string found')
(39, 'Hardcoded string found')
(51, 'Line exceeds 80 characters')
(52, 'Line exceeds 80 characters')
(55, 'Hardcoded string found')

I got it.


[v1.15.x] CNI related fixes

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets

License
Apache 2.0

What's in this PR?

CNI component related fixes to properly support multiple CNI daemonsets for each control plane on one cluster.

[x] Implementation tested

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Workflows: Revisit release.yml

The release.yml that we add to a scaffolded plugin is a bit outdated.

[ ] Update the instructions in the final step (Publish to Grafana.com) to match the current workflow
[ ] Caching strategy of yarn and node modules looks outdated. (https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#caching-packages-data)
[ ] Make sure action versions are up to date

Gonna close this in favour of #115 as it is already in progress and requires changes to release workflow


Issues for synchronizing cost data

Describe the bug

To Reproduce
Steps to reproduce the behavior:

Add a Kubernetes cluster and enable Finops.
Create some services and wait for cost data synchronization.
Logs of the first synchronization.

2023-08-10T07:00:00.006Z	D	cost	collect cost for connector: k5
2023-08-10T07:00:00.008Z	D	cost	collect cost for connector: k18
2023-08-10T07:00:00.011Z	D	task.service-relationship-check	processed in 7.894703ms
2023-08-10T07:00:00.011Z	D	task	executed task: service-relationship-check
2023-08-10T07:00:00.015Z	D	cost	collect cost for connector: k18
2023-08-10T07:00:00.015Z	D	cost	connector: k4, current sync costs within 2023-06-05 12:00:00 +0000 UTC, 2023-08-10 07:00:00 +0000 UTC
2023-08-10T07:00:00.015Z	D	cost	connector: k4, step sync within 2023-06-05 12:00:00 +0000 UTC, 2023-06-06 12:00:00 +0000 UTC
2023-08-10T07:00:00.016Z	D	cost	connector: k5, current sync costs within 2023-06-05 12:00:00 +0000 UTC, 2023-08-10 07:00:00 +0000 UTC
2023-08-10T07:00:00.016Z	D	cost	connector: k5, step sync within 2023-06-05 12:00:00 +0000 UTC, 2023-06-06 12:00:00 +0000 UTC

But each subsequent synchronization starts at 2023-08-10 12:00:00 +0000 UTC.

2023-08-10T10:58:28.306Z	D	cost	collect cost for connector: k5
2023-08-10T10:58:28.310Z	D	cost	connector: k5, current sync costs within 2023-08-10 12:00:00 +0000 UTC, 2023-08-10 10:00:00 +0000 UTC
2023-08-10T10:58:28.313Z	D	api	204 | HTTP/2.0 |      895 B |     16 EiB |   14.425748ms |   <IP_ADDRESS> | POST    /v1/connectors/473320063517065218/sync-cost-data

Check the database. No more data synchronization after 2023-08-10-7:00 to 2023-08-10-8:00 (UTC ).  And there are only 5 min data for 7:00-8:00.

No new data after creating  services.

Expected behavior

Environment

Seal version:<PHONE_NUMBER>f6f6ba511c842b466ae843cc94e775

Additional context
Add any other context about the problem here.

No more valid in the latest version


Textures are saved as .asset files

Textures are saved as .asset files instead of ex. PNG
(CLI / Console version)

GUI saves texture2d as png.

Is it possible for the Console Version to export it as a .PNG too?

no, gui uses external libraries to convert assets in common format


Add Indonesian guide translation

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
no

Fixing URL & updated README.md in indonesian guide translation.
Translate "Working with Forms" guide.

@mdmunir

Merged. Thanks!

Thanks @samdark


Add helpers to generate various authentication header types

Add support for:

Basic Auth
Bearer Auth (OAuth)

I'm trying to make a POST request which requires a Basic Auth authorization. But it's not working, I wonder if it's impossible at this moment. Do you know what could be? Has something to do with the support you intend to implement on this Issue?

Hey, just appedning "Username:Password" is not enough. You need to encode that as Base64. That was the missing part here.
See: https://en.wikipedia.org/wiki/Basic_access_authentication#Protocol
I am planning to make some updates to Fetch this week. I will make sure to do this too.

Thank you! I would appreciate very much if you do this update. I bought you plugin because it's much more well documented than the other one on the marketplace. But only this issue is preventing me to achieve my goal.
But actually, what is your plan to adress this issue? Do you intend to create a Base64 Encode node so we can manually encode our string before adding it to the array? Or something else?

@juninholiveira I will create a simple helper function to add the username & password & it'll create the whole auth header. I will ping you when it's available on the marketplace.

@arunoda Amazing! Better than what I imagined. I will wait patiently.

@juninholiveira I just added support for this. Will available on the marketplace soon.


How should I build this project?

I found yudb doesn't provide a CMake file to build tests after I cloned this repository.  I would appreciate it if you could provide build tools

I'm glad to receive your issues. I will add CMake to build it as soon as possible.

Any chance for a bazel build file also?

@dentiny I apologize, but I am not familiar with Bazel, so I can only add CMake as the build tool for the project.


Alloc free big.Int decoding

Depends on https://github.com/holiman/uint256/pull/177

Upstream PR merged, waiting for release to be cut.


fix: release table_entry with the move operator and add default constructor for table_entry

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area plugin-sdk

/area tests

What this PR does / why we need it:
The table_entry class was missing the default constructor.
The table_entry move operator didn't clean up the left hand side table_entry when moving
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: therealbobo
Once this PR has been reviewed and has the lgtm label, please assign leodido for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mstemm, therealbobo
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mstemm]

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

LGTM label has been added.  Git tree hash: 5e974c99c30e68c93fee1bf92ae6b10390768deb


Document the Grunt tasks

It would be nice to describe what the tasks are doing so others can modify/tweak this repo for their own projects. For example in the Workflow section of the readme, step three says:

grunt vendor – Pulls in Bower components.

This is good enough for the readme but there needs to be further explanation. For example this task also routes vendor assets for you, concatenates all of the cf components, rewrites img and font asset locations, etc. This is useful information to know and documented on our docs site.
Ideas for explaining the tasks

bower-install
Downloads dependencies and routes dependency assets that are flagged in the exportsOverride section of bower.json into the demo folder.
concat
Concatenates dependency styles.
copy
Copies dependency assets that have been routed to the demo folder during the bower-install task into the docs folder.

...

That diagram is incredibly helpful. Related to #151.

It's probably out of date

@himedlooff Is there a source AI file for that diagram somewhere?

Download this XML file https://gist.github.com/himedlooff/118c0f3895607fbbf900
Go to https://www.draw.io/
Choose "Save diagrams to: Device"
Choose "Open existing diagram"
Choose the XML file

Neato!

We've switched to gulp but this is still a good idea

gulp --tasks sort of covers this, and we document build and test in https://github.com/cfpb/capital-framework/blob/canary/CONTRIBUTING.md


[Web Portal] Remove Github PAT related code from web portal

#2772 [Web Portal] [User management] Remove Github PAT
Synced with Yifan that we don't save github PAT, so we need remove related UI.

@abuccts The link to change PAT in github-throttled.js should be removed too as we discussed.

Coverage increased (+0.02%) to 53.356% when pulling 0cee4152b9bf4caa6e93db02916f9525ad806565 on lchao/removePAT into 3722f9705e9a66ef43fc0f6f1fd7dbadffd016fd on master.

Coverage increased (+0.02%) to 53.356% when pulling 0cee4152b9bf4caa6e93db02916f9525ad806565 on lchao/removePAT into 3722f9705e9a66ef43fc0f6f1fd7dbadffd016fd on master.


Update to Bevy 0.14.0-rc.3

Minor changes for updating to 0.14.0
I'm not sure of the exact process but I think this is fine to stay as a PR until they actually release 0.14 and then I can change the exact versions to be ^0.14.0? Not sure

Bevy 0.14 is released. Let's get this PR merged?

@nicopap since Bevy 0.14 has been released (https://bevyengine.org/news/bevy-0-14/), is it possible to have this merged and released? :)

Can someone get this merged?

I added this locally, works great. Thanks @stargazing-dino for the 0.14 update and @nicopap for the original.


⚠ T:Riza Community Forum has degraded performance

In 34ba6fd, T:Riza Community Forum (https://community.triza.dev) experienced degraded performance:

HTTP code: 200
Response time: 7017 ms

Resolved: T:Riza Community Forum performance has improved in abbbc52.


Gizmo is clipped by the UI area instead of the viewport

I'm migrating from egui-gizmo to transform-gizmo-egui. One of the surprises is that the gizmo is only drawing within the UI area:

This was not the case with "egui-gizmo".
In the viewport argument, I tried passing Rect::EVERYTHING or the actual window dimensions - doesn't help.
Finally, the gizmo is reacting to manipulation even if it's not visible. This makes the issue even more confusing to the user.

For comparison, screenshot from egui-gizmo:

This should now be fixed in main and will be included in the next release


Fix indentation

The indentation of three sibling child items in the ParameterGroup was different, making it look like the first and third were parenting the second.
Also the rest of the file uses two spaces for XML indentation, not four.

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

#sign-off


API Management can not import API definition

Hello,
I have a really simple api hosted as app service. The definition is available here: https://orderapi20191219014441.azurewebsites.net/swagger/v1/swagger.json
This is also configured in the app in API definition: https://orderapi20191219014441.azurewebsites.net/swagger/v1/swagger.json
When I try to import this API, I receive an error in API management: Unable to download OpenAPI specification for this App Service.
Is there something missing in the example?
Thank you.

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

ID: 574b6ae8-8902-fbee-d4a3-f819701b777a
Version Independent ID: 7e4b8d50-2281-02a1-bf5f-794b9e59ad17
Content: Import an API App as an API with the Azure portal
Content Source: articles/api-management/import-api-app-as-api.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

@harry12345678910 APIM requests for the swagger definition from the URL that you've configured. But it looks like you have authentication enabled on that endpoint, hence the problem.

@harry12345678910 Just following up here... Did you get a chance to try without authentication enabled?

I tried it. Without authentication it works.  Removing authentication is definitely not the recommendation here.
You could consider downloading the OpenAPI spec manually and importing that instead of using the convenience option of importing the API App. It essentially does the same..
Since there is no doc update required here, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


How to anntotate my own dataset as the form of hciodet?

Nice work!
But I wonder how to make my own dataset  as the form of hciodet?

Hi @Zhanyi0923,
You can try the annotation tools released by the authors.

Hi @Zhanyi0923,
You can try the annotation tools released by the authors. https://github.com/ywchao/hoi-det-ui.
Fred.


Fix link to reference

Coverage remained the same at 100.0% when pulling 53e442ec786b01f6f9bbceb9cf9f81e5e616f75e on fix-cdk-watchful-link into 55ca5686a548c763040fc2a05c6fc67c28282bb0 on main.


Change the order of the expression.

Although ignore missing not working
{% include 'demo.html' ignore missing with {'foo': 'bar'} only %}

not
{% include ignore missing 'demo.html' with {'foo': 'bar'} only %}

We don't bundle src/ in npm, that is for the final package distribution, so if you could revert that, and your change to package.json I can take another look. Thanks!

I have restored the package.json and .npmignore

Do you think you could add a test case that fails before your changes and works after your changes? This helps us make sure we don't break the thing you fixed in the future!

Was fixed in https://github.com/twigjs/twig.js/pull/424


Rocketchat Desktop turns grey when accessing certain Chats

My Setup

Operating System: Ubuntu 16.04
App Version: 3.0.3 and 3.0.4
Installation type: .deb

[x ] I have tested with the latest version
[x ] I can simulate the issue easily

Description
The Client turns grey when clicking on certain Chats, reloading Server is needed to access other chats.
Screenshot found here: https://imgur.com/a/ayPFhJo
Current Behavior
The Client turns grey when clicking on certain Chats, reloading Server is needed to access other chats.
Expected Behavior
Access chats without client getting grey and needs reloading

Same here:
Operating System: Manjaro
App Version: 3.0.4
Installation type: AUR / .deb
Happens when I start or participate in a Jitsi Call (in new window).

Same as @dasfreak , it happen after starting/joining a Jitsi Call (also new window).
Installation type: Docker
RocketChat Server: 3.7.1
RocketChat Client: Rocket Chat Electron 3.0.4 (Windows 10)
Sometimes also the Jitsi popup gives the same behavior (grey window).

Same problem with Mac App Version 3.0.3


pls run jsck with necessary files

git submodule update --init && npm install && coffee benchmarks/

There is no cofffescript in for running these benchmarks. It's a completely new benchmark adapted from the benchmarks in themis.


error when i saveworld

Hello every time when i enter arkmanager saveworld @all it says
root@vmd24450:~# arkmanager rconcmd saveworld
No instances supplied for command rconcmd  saveworld
Do you wish to run this command for all instances?y
Fuehre Befehl 'rconcmd' fuer die Instanz 'ragna' aus
Authentication failed at -e line 23.
when i saveworld
arkmanager saveworld @all
Fuehre Befehl 'saveworld' fuer die Instanz 'ragna' aus
Authentication failed at -e line 23.

my password contains big letters lower cases and numbers
no special characters

Does the password you have set work when used from the client - i.e. do executing the following commands (replacing {password} with the admin password) from the client bring up the ARK admin manager:
EnableCheats {password}
ShowMyAdminManager


licenses: add EUPL v1.1 license

Motivation for this change
Add EUPL v1.1 license.
Things done

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

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I unified it with the rest in 15219fe15e6.
Note: if you change the contents of your branch, including force-pushing etc., the corresponding pull request gets updated, so you don't need to close and reopen.


[ALS-5042] Add google tag manager and cookie preferences popup

@Luke-Sikina idk what I did to get this commit history


Update data-collection-rule-view.md

Duplicated image linked to media/data-collection-rule-overview/view-data-collection-rules.png is used in section View DCRs and add associations.
Removed duplications, linked image to existing media/data-collection-rule-view/data-collection-rule-overview.png, and added a new data-collection-rule-resources.png.
Link to markdown file: data-collection-rule-view.md
Link to doc: Manage data collection rules (DCRs) and associations in Azure Monitor

@microsoft-github-policy-service agree

@Kat-nya
Thank you for contributing to this Azure documentation. Unfortunately, changes to Azure Monitor content can't be accepted this week. The Skilling Content group is migrating this content to a new repository: azure-monitor-docs.
In the meantime, we are closing this PR and tagging it so that when the content is available in the new repo, we can follow up with new location information.
#label:"migrate-followup"
#please-close

@kat-nya We’re happy to share that contributions to azure-monitor, advisor, chaos-studio, service-health are once again possible at azure-monitor-docs. We appreciated your patience during this migration.
Find the article in the new repository and make the changes there (or copy/paste the raw markdown from your changed file) and open a new PR.


Investigate on how to mark NetBird network as Private on Windows

On Windows Device the Network created by the NetApp is labeled as a Public network.
Workaround for now:
PowerShell: Set-NetConnectionProfile -InterfaceAlias 'wt0' -NetworkCategory 'Private'

or :
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
Change "Category" from 0 to 1

We plan to use Windows Packet Filter integration to do this automatically.

I'm the person who send this msg,
The problem is that ON windows
wireguard doesn't set Default Gateway, the network is labeled Public.
This is a bit complicated becuase it doesn't let the firewall work as expected, since i use netbird as a "local network" vpn
This is a problem derived from Wireguard implementation, so is not directly your fault.
But it will affect windows users

The WireGuard Tunnel network adapter is set to 'public' by default on windows, leading to issue when trying to quickconfig winrm (Error number: -2144108183 0x80338169) (winrm firewall exception):

@braginini
Setting the NetConnectionProfile via Powershell or changing the category in NetworkList\Profiles as suggested works for now. But lately there were several new releases of the netbird app within a short time span. Everytime I update the app to the latest version on windows, it creates a new profile in the networklist, filling up my windows registry with new guid's*:
(*as the 'ProfileName' also reads, counting up to nowhere)

Is this the expected behaviour?


⚠ PrivateHD has degraded performance

In 002a131, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2482 ms

Resolved: PrivateHD performance has improved in 55dbf51.


chore(deps): update semantic-release-base-image to v4.1.9

This PR contains the following updates:

Package
Update
Change

tubenhirn/semantic-release-azdo
patch
v4.1.8 -> v4.1.9

tubenhirn/semantic-release-git
patch
v4.1.8 -> v4.1.9

tubenhirn/semantic-release-github
patch
v4.1.8 -> v4.1.9

tubenhirn/semantic-release-gitlab
patch
v4.1.8 -> v4.1.9

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 5.3.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix: Sparce Tensor wrong exeption Message when passing argument with wrong Type

resolves #37640

@rushabh-v Can you please check build failures. Thanks!

Can you take a look again, please? @gbaned

@rushabh-v Can you please check reviewer comments and keep us posted. Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@rushabh-v Any update on this PR, please. Thanks!

I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen!


Allow TCP connection to host machine without wifi or ethernet network.

Is your feature request related to a problem? Please describe
Without direct access to host machine files, my application must use Samba. It works fine using the name of the host machine. Unfortunately if the host machine does not have a network connection when WSA first starts, then the connection is not possible.
Describe the solution you'd like
I would like the Hyper-V network to allow connection to the host machine without a network connection.
Describe alternatives you've considered
Alternatively, I would prefer WSA to allow direct access to the host machine's filesystem.
Please specify the version of Windows Subsystem for Android
2208.40000.5.0

Hi, this is something on our radar already for new feature requests, we appreciate the feedback here.

Awesome, I can't wait to test the new version.


mgmt, retry on 404 in service principal create code, for eventual consistency

Changes:

narrow the error check for retry

for MSGraph, 404 with code=Request_ResourceNotFound
for Microsoft.Authorization, 400 with code=PrincipalNotFound

move retry on "PrincipalNotFound" for Microsoft.Authorization out of its create code, to code in service principal create code (when need to assign RBAC) <-- reverted but keep the change on retry implementation, it happens to user-assigned or system-assigned MSI as well, e.g. withSystemAssignedManagedServiceIdentity
add retry logic for service principal create code (3 APIs, create service principal API if app is created inline, add password API, get service principal API).

Live test via disabling the code that create the service principal (so following API call does not get the service principal). Manually check retry in work.
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

all recording is due to different logic on retry in RoleAssignementImpl.
previously retry happens after 1, 2, 3, ..., 30 seconds (30 times, very long, but initially retry very quick).
new retry happens after 10, 20, 40 seconds (3 times).

/azp run


Error Auth Basic (since 2.12.2)

This error appears since last version (my code works with 2.11, 2.9 etc...)
 File "C:\Users\vqmg0203\Desktop\app\core\models\database.py", line 211, in update_infos
   r = self.request_get(self.user_url)
 File "C:\Users\vqmg0203\Desktop\app\core\handlers\http.py", line 30, in wrapped
   return f(self, *args, **kwargs)
 File "C:\Users\vqmg0203\Desktop\app\core\handlers\http.py", line 130, in request_get
   allow_redirects=False)
 File "C:\Python27\lib\site-packages\requests\sessions.py", line 501, in get
   return self.request('GET', url, **kwargs)
 File "C:\Python27\lib\site-packages\requests\sessions.py", line 474, in request
   prep = self.prepare_request(req)
 File "C:\Python27\lib\site-packages\requests\sessions.py", line 407, in prepare_request
   hooks=merge_hooks(request.hooks, self.hooks),
 File "C:\Python27\lib\site-packages\requests\models.py", line 306, in prepare
   self.prepare_auth(auth, url)
 File "C:\Python27\lib\site-packages\requests\models.py", line 527, in prepare_auth
   r = auth(self)
 File "C:\Python27\lib\site-packages\requests\auth.py", line 68, in __call__
   r.headers['Authorization'] = _basic_auth_str(self.username, self.password)
 File "C:\Python27\lib\site-packages\requests\auth.py", line 38, in _basic_auth_str
   b64encode(b':'.join((username, password))).strip()
TypeError: sequence item 1: expected string, NoneType found

You cannot pass None as an entry to basic auth. This never worked sensibly: we ended up just putting the literal string "None" into the basic auth header.

In the future, please search closed and open issues before creating new ones that are duplicates.
This is a duplicate of two other issues: #3750 and #3736

Sorry for the duplicate :(
Thanks for the explanation


Black screen with tutorial on sway

I wanted to get started with the Rust book you wrote, thank you very much for this btw. :heart: Unfortunately I cannot seem to get it to display anything, it simply shows a black screen.

I assume this has something to do with me using Sway which uses Wayland? As you can see in the screenshot, it has some weird behaviour with regards to that padding. Strange, but I can let it slide. I would love to help, but I was trying to learn some more Rust so I don't think I'll be able to help much besides providing all of the information I can. Let me know if you need any more information.
Rust version: 1.42.0
Rltk version: 0.7.0

Can confirm this is also happening to me with my own project, also on Sway. Rendering with Vulkan and Curses works fine, so this seems to be a problem with just OpenGL on Sway/Wayland. I'm not entirely sure where to start troubleshooting from there, though.

Can confirm this is also happening to me with my own project, also on Sway. Rendering with Vulkan and Curses works fine, so this seems to be a problem with just OpenGL on Sway/Wayland. I'm not entirely sure where to start troubleshooting from there, though.

Afaik I'm using Vulkan atm though.
Forcing it to use XWayland does fix the problem. You can do this by passing WINIT_UNIX_BACKEND=x11.

I've had no end of problems with Wayland support, mostly relating to scaling. winit seems to have issues with it; stuff has been randomly breaking on the last few releases. :-( Unfortunately, Googling around I mostly find other people with the same problems.
I'll add a workaround to force Wayland to use the X11 back-end without needing to set environment variables.

With the fix applied, it seems to work on Sway in a VM for me:

That fixed it for me. Thanks!

This should be fine for now. However this will cause scaling problems for hidpi displays in Sway because Sway does not fix scaling for XWayland apps unfortunately and the maintainer refuses to make a workaround for it.

Sadly, there's not a lot I can do about that. Wayland scaling via winit is a mess also. Wayland supports scaling like 1.25 - but it's an integer in the winit code!

I'm glad I'm not using any hidpi displays except at work, but luckily working from home in these times.


Enhance election and survey reveal settings and reveal stage, and disable experiment modification by non-creators.

Fixes #104 #274 #273 #230

Survey rendering:

Updated version: https://github.com/PAIR-code/deliberate-lab/pull/279


[AKS] Added support for update azure rbac feature in aks

Added update azure rbac support in cli
This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

@Anumita can you resolve the conflicts as another PR for aks-preview is merged? You can still put the version as 0.5.12. I will release the changes in the 2 PRs together.

/azp run


Make it more obvious that progress only goes up

While it's possible to trace the code and verify that progress can only
move upward, making the progress reporting code check too makes this
easier to convey to others. The hope is that it will be easier to defend
fwup in the future the next time someone thinks that its progress
reports went down.
In case it happens again and this commit message is seen, the cause of
progress reports "going down" was due to a UI re-sorting a device
listing that had several devices updating simultaneously. Visually, two
or more rows switched order and it looked as if one device's progress
was going down. However, on closer inspection, it was clear that device
ordering was changing and that update progress never went the wrong way.

@connorrigby - this is for you. 😄

Coverage remained the same at ?% when pulling ca368371d079788690eb681a16812423281cdd4a on always-positive-updates into 2fe303a2849d9d9a80ec21c9d3adc74d73b4ae4f on master.


Correct mapping in NoAliasFunctionsFixer

These were added recently, but are incorrectly mapping the function to the alias.

Thanks for your good fix!
Sadly I messed up the PR when trying to add unit tests. For some reason I cannot get it reopened.
I've made a new one https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/5989 with you as author of the fix.

@SpacePossum thanks! 😃


cilium-dbg: Add "bpf ipcache delete/update"

https://github.com/cilium/cilium/pull/35231 will use two new ipcache cmd to temporarily delete ipcache entries for strict mode encryption test.
Suggested-by: Timo Beckers<EMAIL_ADDRESS>

/test

/test

/test


Module not found: Error: Cannot resolve 'file' or 'directory'

hello
there is my webpack.config
 `var path = require('path');
  var ExtractTextPlugin = require("extract-text-webpack-plugin");
  var extractCSS = new ExtractTextPlugin('bundle.css');

 module.exports = {
entry: {
    index: ['./src/main/js/index.js']
},
output: {
    path: './grails-app/assets/javascripts',
    publicPath: '/assets/',
    filename: 'bundle.js'
},
module: {
    loaders: [
        {
            test: /\.jsx?$/,
            loader: 'babel',
            exclude: /node_modules/,
        },
        {
            test: /\.css$/,
            loaders:  extractCSS.extract(['css'])
        }
    ]
},
plugin: [
    extractCSS
]

};
`
and i have i error log
ERROR in ./src/main/js/component/test.js
Module not found: Error: Cannot resolve 'file' or 'directory' /home/tetar/grails-reactjs-master/src/main/js/component
resolve file
/home/tetar/grails-reactjs-master/src/main/js/component/undefined doesn't exist
/home/tetar/grails-reactjs-master/src/main/js/component/undefined.webpack-loader.js doesn't exist
/home/tetar/grails-reactjs-master/src/main/js/component/undefined.web-loader.js doesn't exist
/home/tetar/grails-reactjs-master/src/main/js/component/undefined.loader.js doesn't exist
/home/tetar/grails-reactjs-master/src/main/js/component/undefined.js doesn't exist
resolve directory
/home/tetar/grails-reactjs-master/src/main/js/component/undefined doesn't exist (directory default file)
/home/tetar/grails-reactjs-master/src/main/js/component/undefined/package.json doesn't exist (directory description file)
[/home/tetar/grails-reactjs-master/src/main/js/component/undefined]
[/home/tetar/grails-reactjs-master/src/main/js/component/undefined.webpack-loader.js]
[/home/tetar/grails-reactjs-master/src/main/js/component/undefined.web-loader.js]
[/home/tetar/grails-reactjs-master/src/main/js/component/undefined.loader.js]
[/home/tetar/grails-reactjs-master/src/main/js/component/undefined.js]
any idea?

Do you want to request a feature or report a bug?

What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Prettify the config...
entry: './src/main/js/index.js',
output: {
    path: path.resolve(__dirname, 'grails-app/assets/javascripts'),
    publicPath: '/assets/',
    filename: 'bundle.js'
}

Make sure that you properly require the test module which isnt found on the path:
./src/main/js/component/test.js
that could be in your index.js file.

It looks like you just deleted/ignored our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.


Initial support for https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters plugin

Add support for Build Status filter
Add support for Job Status filter
Add support for Job Type filter
Add support for SCM Type filter
Add support for other view filter
Add support for most recent Jobs filter
Add support for unclassified jobs filter
Add support for secured jobs filter
Add support for regex filter
Add support for upstream/downstream filter

Does not include support for these types of filters offered by plugin: build duration, build trend, user relevance, parameterized jobs, user permissions

Support for jobFilters has already been merged. Currently status and regex filters are supported. If you want to add support for more filters, please create a new pull request based on current master.


Bi-Directional Patching

What happened?
I'm trying to create an RDS with a vanity DNS, but it's not working. Docs seem to be vague about it
How can we reproduce it?
apiVersion: apiextensions.crossplane.io/v1
kind: Composition
metadata:
  name: mariadb
  labels:
    crossplane.io/xrd: xinstances.database.example.org
    provider: aws-provider
spec:
  writeConnectionSecretsToNamespace: crossplane-system
  compositeTypeRef:
    apiVersion: database.example.org/v1alpha1
    kind: XDBInstance
  resources:
  - name: rdsinstance
    base:
      apiVersion: database.aws.crossplane.io/v1beta1
      kind: RDSInstance
      spec:
        providerConfigRef:
          name: aws-provider
        forProvider:
          region: eu-west-1
          masterUsername: example
          maxAllocatedStorage: 1
          allowMajorVersionUpgrade: false
          applyModificationsImmediately: true
          autoMinorVersionUpgrade: false
          backupRetentionPeriod: 7
          skipFinalSnapshotBeforeDeletion: true
          dbInstanceClass: xsize
          engine: xenige
          engineVersion: x
          preferredBackupWindow: 02:30-03:00
          preferredMaintenanceWindow: tue:03:30-tue:04:30
    patches:
      - fromFieldPath: RDSInstance.status.atProvider.endpoint.address
        toFieldPath: composite.status.atProvider.endpoint.address
        type: ToCompositeFieldPath
        transforms:
        - type: string
          string:
            fmt: "%s"
  - name: route53record
    base:
      apiVersion: route53.aws.crossplane.io/v1alpha1
      kind: ResourceRecordSet
      metadata:
        name: mydns
        annotations:
          crossplane.io/external-name: mydns.example.org
      spec:
        providerConfigRef:
          name: aws-provider
        forProvider:
          region: eu-west-1
          type: CNAME
          ttl: 60
          zoneId: xxxxxxxx
          zoneIdRef:
            name: example.org
          setIdentifier: "dev"
    patches:
        - fromFieldPath: composite.status.atProvider.endpoint.address
          toFieldPath: ResourceRecordSet.spec.forProvider.resourceRecords[0].value
          type: FromCompositeFieldPath

What environment did it happen in?
Crossplane version: 1.9.0

Cloud provider: AWS
Kubernetes version: 1.23
Kubernetes distribution: EKS

Your patches should be:
  - fromFieldPath: status.atProvider.endpoint.address
    toFieldPath: status.atProvider.endpoint.address
    type: ToCompositeFieldPath
    transforms:
    - type: string
      string:
        fmt: "%s"

and
    - fromFieldPath: status.atProvider.endpoint.address
      toFieldPath: spec.forProvider.resourceRecords[0].value
      type: FromCompositeFieldPath

Also the transform is not required - it will be copied as a string by default

Documentation is here:
https://crossplane.io/docs/v1.9/reference/composition.html#patch-types
and
https://crossplane.io/docs/v1.9/reference/composition.html#patching-from-one-composed-resource-to-another


Deleted the deprecated variable from the import state

Codecov Report

Merging #571 (a3eff4d) into develop (6afcc94) will increase coverage by 0.03%.
The diff coverage is 75.00%.

@@             Coverage Diff             @@
##           develop     #571      +/-   ##
===========================================
+ Coverage    46.31%   46.34%   +0.03%
===========================================
  Files           24       24
  Lines         3947     3953       +6
===========================================
+ Hits          1828     1832       +4
- Misses        1836     1837       +1
- Partials       283      284       +1

Impacted Files
Coverage Δ

idb/postgres/postgres.go
39.16% <ø> (ø)

idb/postgres/postgres_migrations.go
73.02% <75.00%> (-0.15%)
:arrow_down:

Continue to review full report at Codecov.

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


Go back to using regular Pygments package

Now Pygments latest releases supports Lean 3, we don't need to use the prerelease version any more 🙂

Thanks!


Joint with hole is not rendered correctly in babylon.js

See model 09
https://github.com/stevk/glTF-Asset-Generator/tree/skins/Output/Animation_Skin

Looking at the model again, The vertexes where the hole in the joints is have weights of zero, which is causing this issue.


strconv: Unquote example looks like a unit test instead of an example

The Unquote example (https://golang.org/pkg/strconv/#Unquote) looks like a unit test instead of an example.
That is a sea of backslashes and quotes. I think we could make a more readable example.

I can submit the CL if this is ok: https://play.golang.org/p/1n5phD85F--

Already had a CL to submit. I published it now here


ModuleNotFoundError: No module named 'faiss'

/content/Retrieval-based-Voice-Conversion-WebUI
Traceback (most recent call last):
File "/content/Retrieval-based-Voice-Conversion-WebUI/infer-web.py", line 7, in
import faiss
ModuleNotFoundError: No module named 'faiss'

pip3 install faiss-cpu==1.7.2
Environmental Dependence: https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI/blob/main/requirements.txt

cpu

how can install it??????? vedio pleas

after i install this
pip3 install faiss-cpu==1.7.2
Environmental Dependence: https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI/blob/main/requirements.txt
New error
/content/Retrieval-based-Voice-Conversion-WebUI
Traceback (most recent call last):
File "/content/Retrieval-based-Voice-Conversion-WebUI/infer-web.py", line 21, in
import ffmpeg
ModuleNotFoundError: No module named 'ffmpeg'

try
apt install ffmpeg
or
1-download ffmpeg(linux version) from https://github.com/BtbN/FFmpeg-Builds/releases
2-chmod the ffmpeg file to 777
3-modify "ffmpeg" to "path/of/ffmpeg" from https://github.com/RVC-Project/Retrieval-based-Voice-Conversion-WebUI/blob/main/lib/audio.py#L16


Unable to parse emails from outlook

I am unable to parse emails from outlook. This is the stack trace for the corresponding.
Error: Unexpected space at the beginning of line 51         at parseHeaders (/home/example/node_modules/letterparser/lib/parser.js:95:23)         at Object.parseBody (/home/example/node_modules/letterparser/lib/parser.js:135:21)         at parse (/home/example/node_modules/letterparser/lib/index.js:32:30)

Could you, please, share an example of such message?

 Can I send it over mail?

Got it! Thanks. Will work on the issue tomorrow.

ok cool. Thanks a ton.

Since headers are failed to being passed sometimes, this could be a good strategy if the existing logic ends in an error. If a header name is found on a specific line and the header value condition check fails, search the immediate next line for a value and capture that as the header value, otherwise throw any error.

Patch published with version 0.0.4.

Tried 0.0.4 version. Getting the same error still. It fails to parse the below lines.
Date: Fri, 30 Oct 2020 19:28:52 +0000
Message-ID:
<EMAIL_ADDRESS>References:
<EMAIL_ADDRESS>In-Reply-To:
<EMAIL_ADDRESS>

I can see that there is a space before the three keys on the new line as well.

The raw email you've sent me parses just fine on 0.0.4. (Saved it to file, read using readFileSync and parsed using letterparser.parse()).

Still failing with the below error. "err":{"message":"Unexpected space at the beginning of line 51","name":"Error","stack":"Error: Unexpected space at the beginning of line 51\n    at parseHeaders (/root/workspace/vidwaan-api/node_modules/letterparser/lib/parser.js:95:23)\n    at Object.parseBody (/root/workspace/vidwaan-api/node_modules/letterparser/lib/parser.js:135:21)\n    at parse (/root/workspace/vidwaan-api/node_modules/letterparser/lib/index.js:32:30)\n


Cannot Clone the repository and install with npm

Having issues getting GRUNT to comile the FoundationPress files. I have latest versions of node and npm installed and I was able to clone this GIT repo on my computer but as soon as I try running the "npm install" command on the downloaded directory - I come across heaps of errors that tell me that there is nothing wrong with the npm command but rather an issue with a problem with the foundationpress package. Is there something that I am missing here? Is the package still OK?
Is there any other method of compiling SASS files into CSS?
Thanks

I have seen that there are some who have had problems with npm install lately. The errors seems to be casued by permission issues on the postinstall scripts. Do you have administrator privileges on your account? I have no problems with npm install on my OSX 10.11 running the latest version of Node.js. I'm currently quite busy with another project, but I'll check into this when I get time. There must be a solution to this, so that anyone can install without problems.

Thanks for your quick reply Fredrik.
I have admin privileges as its my own personal MacBook Pro. Perhaps I forgot to run it with sudo or something. Have latest versions of node and npm.
BTW I am running OSX Yosemite if that helps.
Regards,
Ryan Archer

On 12 Oct 2015, at 5:10 PM, Ole Fredrik Lie<EMAIL_ADDRESS>wrote:
I have seen that there are some who have had problems with npm install lately. The errors seems to be casued by permission issues on the postinstall scripts. Do you have administrator privileges on your account? I have no problems with npm install on my OSX 10.11 running the latest version of Node.js. I'm currently quite busy with another project, but I'll check into this when I get time. There must be a solution to this, so that anyone can install without problems.
—
Reply to this email directly or view it on GitHub.

Hmm. It shouldn't really be necessary to run npm install with sudo. I'm not. And it just works. But you're not the only one experiencing this, so we must find out what is causing the error. The whole purpose of this project is to offer a quick way to get started on new projects. So if you're going to waste a lot of time on installation, that's not good. Let me see what I can find out. If someone else knows how this can be resolved, please share the solution in this thread.

@stefanjudis : Is there a possibility that you may have some insight into why npm install fails on post install scripts? I'm running the most recent OSX with the latest version of Node, and experience no problems. But there are certain others who reports an error during installation. https://github.com/olefredrik/FoundationPress/issues/501
I thought maybe you could help, since you helped us to remove global dependencies and introduce postinstall scritps initially. https://github.com/olefredrik/FoundationPress/issues/274

@coolwebs
Can you please provide your node and npm version?
Also the folder structure inside of your node_module might help.
There shouldn't be any case to run it with sudo. :bowtie:

I've got same issue on Debian.

@bpinet
Then same here - can you please provide node and npm versions and maybe the logfile? :bowtie:

Node v0.12.7
NPM 2.11.3
I get this info:
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node scripts/install.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/install.js

@bpinet
But that's a different error. I assume npm install node-sass is failing in any folder?
Can you please confirm?
@coolwebs
ja what should I say. Working fine here.
https://gist.github.com/stefanjudis/c22f0128e62cb5f1946a
Can you please confirm that you're got grunt and bower on first level inside of your node_modules folder?
And also that the execution srcipts are included in node_modules/.bin?

node: v4.1.2
npm: v2.14.4
Within the node_modules folder within the 'FoundationPress' installed folder I can see the 'grunt' and 'bower' folders.
All I can seen in the node_modules/.bin folder is a grunt shortcut.
I cannot see where the log file is. My terminal tells me to look for a file called 'npm-debug.log' but I can't find this file anywhere.
I have attached a screenshot of my dir.

@stefanjudis
npm install node-sass works fine in other folder.
Here's full log for npm install in FoundationPress folder.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'install' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose node symlink /usr/bin/node
5 verbose readDependencies loading dependencies from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/package.json
6 verbose install where, deps [ '/var/www/ekspresysaeco/wp-content/themes/FoundationPress',
6 verbose install   [ 'bower',
6 verbose install     'grunt',
6 verbose install     'grunt-cli',
6 verbose install     'grunt-contrib-compress',
6 verbose install     'grunt-contrib-concat',
6 verbose install     'grunt-contrib-copy',
6 verbose install     'grunt-contrib-uglify',
6 verbose install     'grunt-contrib-watch',
6 verbose install     'grunt-sass',
6 verbose install     'grunt-string-replace',
6 verbose install     'node-sass',
6 verbose install     'time-grunt' ] ]
7 verbose install where, peers [ '/var/www/ekspresysaeco/wp-content/themes/FoundationPress',
7 verbose install   [] ]
8 verbose installManyTop reading for lifecycle /var/www/ekspresysaeco/wp-content/themes/FoundationPress/package.json
9 info preinstall<EMAIL_ADDRESS>10 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/bower/package.json
11 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt/package.json
12 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-cli/package.json
13 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-compress/package.json
14 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-concat/package.json
15 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-copy/package.json
16 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-uglify/package.json
17 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-watch/package.json
18 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-sass/package.json
19 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-string-replace/package.json
20 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/node-sass/package.json
21 verbose installManyTop reading scoped package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/time-grunt/package.json
22 info package.json<EMAIL_ADDRESS>No license field.
23 info package.json<EMAIL_ADDRESS>No license field.
24 info package.json<EMAIL_ADDRESS>No license field.
25 info package.json<EMAIL_ADDRESS>No license field.
26 info package.json<EMAIL_ADDRESS>No license field.
27 info package.json<EMAIL_ADDRESS>No license field.
28 info package.json<EMAIL_ADDRESS>No license field.
29 info package.json<EMAIL_ADDRESS>No license field.
30 info package.json<EMAIL_ADDRESS>No license field.
31 verbose readDependencies loading dependencies from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/package.json
32 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/bower/package.json
33 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt/package.json
34 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-cli/package.json
35 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-compress/package.json
36 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-concat/package.json
37 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-copy/package.json
38 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-uglify/package.json
39 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-contrib-watch/package.json
40 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-sass/package.json
41 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/grunt-string-replace/package.json
42 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/node-sass/package.json
43 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/time-grunt/package.json
44 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/.bin/bower/package.json
45 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/.bin/bower.cmd/package.json
46 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/.bin/grunt/package.json
47 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/.bin/grunt-string-replace/package.json
48 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/.bin/grunt-string-replace.cmd/package.json
49 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/.bin/grunt.cmd/package.json
50 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/.bin/node-sass/package.json
51 verbose targetResolver reading package data from /var/www/ekspresysaeco/wp-content/themes/FoundationPress/node_modules/.bin/node-sass.cmd/package.json
52 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
53 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
54 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
55 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
56 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
57 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
58 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
59 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
60 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
61 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
62 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
63 verbose already installed skipping<EMAIL_ADDRESS>/var/www/ekspresysaeco/wp-content/themes/FoundationPress
64 silly install resolved []
65 info build /var/www/ekspresysaeco/wp-content/themes/FoundationPress
66 info linkStuff<EMAIL_ADDRESS>67 silly linkStuff<EMAIL_ADDRESS>has /var/www/ekspresysaeco/wp-content/themes as its parent node_modules
68 verbose linkBins<EMAIL_ADDRESS>69 verbose linkMans<EMAIL_ADDRESS>70 verbose rebuildBundles<EMAIL_ADDRESS>71 verbose rebuildBundles [ '.bin',
71 verbose rebuildBundles   'bower',
71 verbose rebuildBundles   'grunt',
71 verbose rebuildBundles   'grunt-cli',
71 verbose rebuildBundles   'grunt-contrib-compress',
71 verbose rebuildBundles   'grunt-contrib-concat',
71 verbose rebuildBundles   'grunt-contrib-copy',
71 verbose rebuildBundles   'grunt-contrib-uglify',
71 verbose rebuildBundles   'grunt-contrib-watch',
71 verbose rebuildBundles   'grunt-sass',
71 verbose rebuildBundles   'grunt-string-replace',
71 verbose rebuildBundles   'node-sass',
71 verbose rebuildBundles   'time-grunt' ]
72 info install<EMAIL_ADDRESS>73 info postinstall<EMAIL_ADDRESS>74 verbose unsafe-perm in lifecycle true
75 info<EMAIL_ADDRESS>Failed to exec postinstall script
76 verbose stack Error<EMAIL_ADDRESS>postinstall: `bower install && grunt build`
76 verbose stack Exit status 3
76 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:213:16)
76 verbose stack     at EventEmitter.emit (events.js:110:17)
76 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
76 verbose stack     at ChildProcess.emit (events.js:110:17)
76 verbose stack     at maybeClose (child_process.js:1015:16)
76 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
77 verbose pkgid<EMAIL_ADDRESS>78 verbose cwd /var/www/ekspresysaeco/wp-content/themes/FoundationPress
79 error Linux 3.2.0-4-amd64
80 error argv "/usr/bin/node" "/usr/bin/npm" "install"
81 error node v0.12.7
82 error npm  v2.11.3
83 error code ELIFECYCLE
84 error<EMAIL_ADDRESS>postinstall: `bower install && grunt build`
84 error Exit status 3
85 error Failed at the<EMAIL_ADDRESS>postinstall script 'bower install && grunt build'.
85 error This is most likely a problem with the foundationpress package,
85 error not with npm itself.
85 error Tell the author that this fails on your system:
85 error     bower install && grunt build
85 error You can get their info via:
85 error     npm owner ls foundationpress
85 error There is likely additional logging output above.
86 verbose exit [ 1, true ]

@bpinet @coolwebs Can you please try the same with the latest npm 2.x version 2.4.17?
It's the latest release bfore 3.x which should only include fixes.
Honestly I've got no idea what's going on.
Everybody running npm install should have a grunt and bower folder on first level + the depending executable in .bin. This is what they promise. :)

I've used this commend to update npm curl -L https://npmjs.com/install.sh | sh
Now I have 3.3.6.
I got this warning, but it  looks like it worked just fine.
npm WARN lifecycle<EMAIL_ADDRESS>cannot run in wd %s %s (wd=%s<EMAIL_ADDRESS>bower install && grunt build /var/www/ekspresysaeco/wp-content/themes/FoundationPress
<EMAIL_ADDRESS>node_modules/grunt-contrib-watch/node_modules/tiny-lr/node_modules/noptify/node_modules/nopt/node_modules/abbrev -> node_modules/abbrev
<EMAIL_ADDRESS>node_modules/grunt-contrib-watch/node_modules/tiny-lr/node_modules/noptify/node_modules/nopt -> node_modules/nopt

I've used this commend to update npm curl -L https://npmjs.com/install.sh | sh

no need for that ( it works though ;) )... when you once have npm installed you can easily jump between version with:
npm install -g npm // latest one
npm install -g<EMAIL_ADDRESS>// specific version

Can you maybe check the 2.4.17 version? So that we can figure out, if they fixed it in one of the fix-releases in 2.x?

@stefanjudis - are you sure that npm version is right. My most up to date version was v2.14.4.
I tried using that line to install v2.4.17 and then I tried v2.17.4. I dunno, now that its failed my complete npm package is screwed. How can I uninstall it and reinstall it again? I am trying the instructions here https://docs.npmjs.com/misc/removing-npm but it tells me that access is denied and I can't install a clean npm version as it says "command not found"

Fu... Sorry to hear that. :(
https://github.com/npm/npm/releases points out that v2.4.17 is the latest stable 2.x release.
v2.17.4 is no release.  :(

Thanks for following up with me @stefanjudis - lets just say this isn't the first time I've had issues with node. Mucking around with ionic and phonegap CLI forced me to do clean uninstall/reinstall several times.
I don't want to get node via the installer again so I completely cleaned out the junk and did it with Homebrew (not before having to repair Homebrew as well!) So yeah now I have node v0.10.28 and npm v3.3.8, so it seems I've done a jump like @bpinet (maybe he used brew as well).
So I got much further this time but still ran into errors and still could not successfully run npm build to get the SASS files to write css - good news is that I found a log file this time which I have attached.
Scratch that, cannot attach a log file or a txt file in GITHUB, so here is a link to it http://coolwebs.com.au/npm-debug.txt

Ok, so I got tired of doing it on a mac so I have it a go on my work PC which is still running the version of node and npm that i stated earlier. One thing I noticed is that the instructions on the .MD file state to run npm install but @bpinet said he runs the command npm install node-sass - which did have a much better result and did not throw an error!
However, I can't run the npm run build, it fails. I can however fun npm run watch but as soon as I change a file and it tries to compile, it throws the same error as the build command.
I have attached a screenshot from CMD

Man I'm through with trying to compile sass, @olefredrik - do you have a version of FoundationPress that just uses CSS and not SASS? I can reverse engineer it into SASS later and use Compass to do all the compiling/watching. The CLI way keeps telling me that it has issues with Bower and Grunt and keeps blaming your package.
I just want to get the theme into a WP installation so I can have a play with it. I'm hoping for a time in the future that browsers will just read SASS files instead of CSS but that's probably quite some time away...

I had hoped that we could find out what was the core of the problem here. I'm not getting any of the errors that you get, so that makes it all a bit more difficult to troubleshoot.
This is essentially a starter-theme which is heavily based on a workflow using Sass and Grunt. So if you just want to hack on the CSS, I would recommend that you take a look at JointsWP, which offers a package for both Sass and CSS. Out of curiosity, you can test if you're able to run Sass on JointsWP?

Yes Fredrik, I did come across JointsWP today and i sent Stefan an email asking how much different it was from FoundationPress. I'm not sure what's going on.

I give up. I've switched to 2.5.0 and it didn't work. After going back to 3.3.6 it does not work anymore. Same error every time.

I just found out about FoundationPress and wanted to start using it today. I didn't came any further, as I am still struggling to get it up and running. I have tried upgrading/reinstalling node, using sudo and anything I thought would make some sense, but to no avail.
It looks like I'm having the same issue @coolwebs stated earlier. It seems that line 4 of foundation.scss is causing the error, as it is trying to compile the scss using a non-existing reference to ../components/foundation/scss/normalize. I can not find this directory (or any /components/foundation/ directory) in the cloned folder.
I hope this is of any help. OS used is Mac OS X 10.11.1 (El Capitan), node and npm versions are found in log below.
MacBook:FoundationPress didel$ npm run build
><EMAIL_ADDRESS>build /Applications/MAMP/htdocs/wp-content/themes/FoundationPress
> grunt build
Running "copy:scripts" (copy) task
Running "copy:iconfonts" (copy) task
Running "string-replace:fontawesome" (string-replace) task
Running "sass:dist" (sass) task
>> file to import not found or unreadable: ../components/foundation/scss/normalize
>> Current dir: /Applications/MAMP/htdocs/wp-content/themes/FoundationPress/assets/scss/
>>   Line 4  Column 9  assets/scss/foundation.scss
Warning:  Use --force to continue.
Aborted due to warnings.

Execution Time (2015-10-30 00:37:40 UTC)
loading tasks               273ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 94%
copy:scripts                  5ms  ▇ 2%
string-replace:fontawesome    3ms  ▇ 1%
sass:dist                     6ms  ▇ 2%
Total 290ms

npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: `grunt build`
npm ERR! Exit status 6
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'grunt build'.
npm ERR! This is most likely a problem with the foundationpress package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     grunt build
npm ERR! You can get their info via:
npm ERR!     npm owner ls foundationpress
npm ERR! There is likely additional logging output above.
npm ERR! Darwin 15.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! path npm-debug.log.8d0f1362c3d07127fc992c5ac59e43eb
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall open

npm ERR! Error: EACCES: permission denied, open 'npm-debug.log.8d0f1362c3d07127fc992c5ac59e43eb'
npm ERR!     at Error (native)
npm ERR!  { [Error: EACCES: permission denied, open 'npm-debug.log.8d0f1362c3d07127fc992c5ac59e43eb']
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'open',
npm ERR!   path: 'npm-debug.log.8d0f1362c3d07127fc992c5ac59e43eb' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     /Applications/MAMP/htdocs/wp-content/themes/FoundationPress/npm-debug.log

@Didel
so you're running
node v4.2.1
npm  v2.14.7

?
And the initial npm i process succeeded. We already figured out, that the problem is connected to bower.
I assume that you don't have node_module/.bin/bower available in your project root?
@olefredrik I have still no idea what's going on. :( I'm so sorry about that.
Maybe we want to switch back to global installation advices?
I just tried the same setup - node v4.2.1 and npm v2.14.7. And it's running all smoothly. :(

I can not understand what's causing these errors, since it runs smoothly on my machine. OSX El Capitan, Node v.4.1.1, NPM v.2.14.4.
Basically, I believe that it is still a good idea to drop global dependencies. But if people experience showstopper errors on installation, it' maybe a relevant question whether we should roll back to global installation of bower. What do you think, @stefanjudis ?

@olefredrik
Honestly i'm fine with rolling back - I don't like it though.
But the fact that I was not able to reproduce the problem at all ( and I tried really several node&npm combinations ), makes it impossible to debug or solve. :(
Also there should be an npm issue filed about it.

@stefanjudis Correct, node -v returns v4.2.1 and npm -v returns 2.14.7.
However, file node_modules/.bin/bower exists and is not empty. The same goes for node-modules/.bin/grunt, node-modules/.bin/grunt-string-replace and node-modules/.bin/node-sass.
I'm running the latest version of OS X El Capitan (10.11.1). I just have tried again, and indeed exact the same errors occur when I try to run npm run build. If I can do/test/run anything else I'd be glad to hear.

I have two macbooks, both running OSX El Capitan. I've installed Node v4.2.1 and npm 2.14.7 on both machines. With a fresh clone of FoundationPress, I experience no issues at all with npm install or npm run build. Since I am unable to reproduce the error with the same setup as you, it becomes very difficult to troubleshoot.

@Didel : Is it right that you don't have a components/foundation/ directory in your cloned folder, after npm install? When the repo is cloned, you will not have these files. They should, however, be generated on npm install.

@olefredrik @stefanjudis Weird. I decided this morning to remove the entire FoundationPress folder and start all over again. After a git clone, npm install and npm build everything works as expected and I can use the FoundationPress theme.
The previous time I cloned the project I got all different kinds of errors, so I did all kinds of things in a desperate try to fix the problem. For example, I updated and upgraded all the npm packages and npm and node itself. I happend to have quite an old version of node (0.12) and apparently lots of things have changed since then, so I installed my current node version. So effectively I first cloned the project, then updated and upgraded everything, while apparently doing the other way around is the right way to go. Maybe this won't happen to users who have a relatively fresh install of node and/or npm, and only affects users who could have outdated copies of any of the above? Could it help to include update/upgrade instructions in the installation manual? And could it help to require a minimal node-version? I remember to have read somewhere that as of node 3.4 (or 3.2, I don't remember exactly) something has changed which fixes a lot of things... Just dropping my thoughts on the problem, I'm glad I can start working on the theme today :smile:

@Didel : Woho! I'm happy it worked out, finally! It's a good idea to include the required minimal node version in the readme. I removed it from the quickstart because I was not 100% sure which version is required. But I'll run a manual test with nvm and check that.

@coolwebs : Are you still experiencing npm install issues with a fresh clone using node v.4.2.1 and npm v.2.14.7?

A wild guess is that a lot of the weird, hard-to-reproduce problems are cause by old versions of FoundationPress used with the new way of doing things.
FoundationPress really isn't upgradeable at all (unless you carefully do it manually) and neither is the workflow, since so much have changed. That could be a problem if you have various FoundationPress-based sites based on different checkouts of the code over the last year(s). It does not help that node, npm, lib-sass etc have had their own compatibility issues as well, on top of everything else.

@olefredrik, In all honesty I have not been playing with it lately. I had a website to build and decided to get up and running with JointsWP and just use CSS overrides agains the core Foundation CSS. From what I can see, Foundation based themes are quite robust and really made me appreciate how commercial themes (like from ThemeForest) can just needlessly way down a Wordpress website with tonnes of features that you never use and a ‘glut’ of code to process on every page load.
I will revisit FoundationPress at a later time I hope. Can you tell me in what key ways that it differs from JointsWP?

On 2 Nov 2015, at 9:16 PM, Ole Fredrik Lie<EMAIL_ADDRESS>wrote:
@coolwebs https://github.com/coolwebs : Are you still experiencing npm install issues with a fresh clone using node v.4.2.1 and npm v.2.14.7?
—
Reply to this email directly or view it on GitHub https://github.com/olefredrik/FoundationPress/issues/510#issuecomment-152990934.

Ryan Archer | Web Designer & Developer
Coolwebs Web Design
Email<EMAIL_ADDRESS>Phone: 0468 417 387
Website: http://www.coolwebs.com.au http://www.coolwebs.com.au/

@coolwebs : :+1:  To be honest, I haven't used JointsWP myself. But I guess it's pretty much the same, with a few variations in workflow and build settings (grunt vs build etc). They are both built on Foundation 5, so the available components will be the same for both.
@Aetles : It is true that is's not necessarily straight forward to upgrade a FoundationPress installation. The idea is to start with the latest version when starting a new project, and take it from there. Have tried to make it easier to see what's new by introducing a changelog and release archive. Earlier versions will always be downloadable under releases. So you're free to choose whether you will jump on the latest version, or use an earlier version. Or use a JointsWP or another theme, for that matter.