Error in DisableSharingForNonOwners description.

[Enter feedback here]
There's an error on the description when applying the property of DisableSharingForNonOwners.
It specifies that only the site won't be shared by nonOwners, but it really prevents nonOwners from sharing files and folders.
Regards,

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

ID: a453f6db-c1b0-3769-9972-d948616982df
Version Independent ID: d9e27a2c-8408-95ba-6d88-46e63fe878a1
Content: Set-PnPSite (SharePointPnPPowerShell)
Content Source: sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSite.md
GitHub Login: @Techwriter40
Microsoft Alias: kirks

Hello @marcjornet
how are you?
Even though the PnP documentation articles are on this repository, I need to kindly redirect you to open PnP cmdlets issues here, in that repository, where a member of the PnP community will be able to correct the article with your feedback.
The documentation for PnP cmdlets is then sync from that repo into this one.
Thank you!

@get-itips Thank you very much for the contribution and sharing this explanation. @marcjornet Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Strip away parts of Polypy to leave the code applicable to this lab course

MSD.py is now ready and fairly simple. I don't think they need any other analysis from it. Density and regional MSD calcs are not needed in my opinion.
I will close this now. If you want to tweak MSD.py please feel free to do so.


[RFC] Documentation sections

After @rosylilly's great enhancements to the API docs, many things still remain.
One of them is that all the types in the left are just listed alphabetically. Maybe it would be nice to group them in sections. For example: "Core" (Object, Bool, Char, etc.), "Containers" (Array, Hash, Set, BitArray, etc.), "IO", "Networking" (Socket, HTTP::Client, etc.), "File formats" (Ini, JSON, XML), "Spec" (Spec), etc.
One idea is to put this section in the docs themselves, for example:
# :section: Networking
#
# The HTTP module blah blah blah...
module HTTP
end

Sections could be nested, for example :section: Networking / HTTP. The documentation generator would read the first line of a type's docs to determine the section, and from all the sections it could build the left navigation.
This idea was suggested by @waj. At first I though this might only make sense for the standard library, but it's true that big libraries (frameworks) might provide many functionalities and it would be nice to have classes with related functionality grouped in the docs.

:+1: sounds like a good idea. Yard does that even on the class level listing / method with @!group.

From experience so far in searching the API documentation, I find it more useful to use the search box. Perhaps instead of using a hierarchical approach like with sections, would it make more sense to have keyword metadata like below? The search bar could then filter through the list of modules for any that match either the name or one of the keywords.
# :keywords: Networking | HTTP | REST | API | Web
#
#
module HTTP
  # [...]
end

It might make more sense in a different context, such as with channels. Keywords like Concurrent, Concurrency, Thread, Fork, and so on would be relevant to the channels API, enough to point people in the right direction.

To expand on this: having the different constructs grouped in their own sections too by default (i.e. modules, classes, structs, etc). I was recently trying to search for a specific annotation in the standard library, but there was no sane way to do that...

Grouping is definitely very nice feature and is needed not only in stdlib
Right now grouping is possible using modules:

# This module includes everything about networks...
module Networking
  # The HTTP module blah blah blah...
  module HTTP
  end
end
include Networking # so API won't change

and i am actually using this way.
Pro:

you can also add description to the entire section

Contra:

changing a source to make documentation cleaner doesn't feel right.

The other con is that it can lead to longer type names, but top level shorter alias can be a good workaround.


Error in ESM about no extensionless imports does not occur for import with only specifier

Bug Report
Doing import "./other"; will not raise a Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './other.mjs'? error.
🔎 Search Terms
import specifier only side effects
🕗 Version & Regression Information
5.0.0-dev.20230110
⏯ Playground Link
Here's a repo: https://github.com/dsherret/tsc-issues/tree/importOnlySpecifier
💻 Code
{
  "compilerOptions": {
    "moduleResolution": "NodeNext",
    "target": "ESNext",
    "module": "NodeNext",
    "declaration": true,
    "emitDeclarationOnly": true,
    "traceResolution": true
  }
}

// main.mts
import "./other";

// other.mts
export class Test {}

🙁 Actual behavior
Does not error unless I change the import to have a default, namespace, or named import. Output will fail at runtime.
======== Resolving module './other' from 'V:/tsc-issues/main.mts'. ========
Explicitly specified module resolution kind: 'NodeNext'.
Resolving in ESM mode with conditions 'node', 'import', 'types'.
Loading module as file / folder, candidate module location 'V:/tsc-issues/other', target file types: TypeScript, JavaScript, Declaration.
Directory 'V:/tsc-issues/other' does not exist, skipping all lookups in it.
======== Module name './other' was not resolved. ========
File 'V:/tsc-issues/node_modules/typescript/lib/package.json' does not exist.
Found 'package.json' at 'V:/tsc-issues/node_modules/typescript/package.json'.
File 'V:/tsc-issues/node_modules/typescript/lib/package.json' does not exist according to earlier cached lookups.
File 'V:/tsc-issues/node_modules/typescript/package.json' exists according to earlier cached lookups.
...etc...

🙂 Expected behavior
Should error because no extension used.

Side-effect imports like this have never been checked that they resolve whatsoever. @DanielRosenwasser and I briefly discussed whether we could change this, but I don’t know if there was a consensus. It would definitely be a breaking change.

Interesting. Well overall it's not really that big of a deal since people will get an immediate error when running the code and people rarely write these kind of imports.

Duplicate of https://github.com/microsoft/TypeScript/issues/50394

Yeah, I should have search for "side-effects" 😅

Added some new discussion in #50394


Adds MS Edge support for Blazor Wasm debugging

Summary of the changes (Less than 80 chars)
Checks the browser to see if edge chromium and gives steps based on that.
Addresses #10163

Thanks @jbomhold3. I'm merging your change as part of https://github.com/aspnet/AspNetCore/pull/15176/files


datasets.json

@constantinpape
Could you do me a favour and rename default to defaultDataset:
{
  "datasets": [
    "10spd",
    "10spdbaf"
  ],
  "defaultDataset": "10spdbaf"
}

default is reserved in Java and cannot be used as a variable name.

No problem, will change it in a sec.

Done.


-H flag doesn't exist anymore

A lot of things in the README are no longer valid. E.g., the -H flag doesn't exist.

I think it wasn't intentional to remove -H. When just typing micro it will give this output:
☁  deployer [master] ⚡ ./node_modules/.bin/micro

> Error! Please supply a file.

  Usage: micro [options] [command]

  Commands:

    help  Display help

  Options:

    -h, --help          Output usage information
    -h, --host [value]  Host to listen on
    -n, --no-babel      Skip Babel transformation
    -p, --port <n>      Port to listen on
    -v, --version       Output the version number

--host and --help are clashing (both are -h).

I corrected the title accordingly. Some other things in the docs are out of date, too, though.

@onbjerg you are right, a new version needs to be published to npm, ping @rauchg

Done


comment does not show in pages

Environment informations

Minimal Mistakes version: 4.4.1
github-pages or jekyll gem version: 3.6
Operating system:  mac

Expected behavior
show comment on pages
Steps to reproduce the behavior
The disqus comment works fine in post, but does not show in pages.
btw, I have add the comments= true in YAML in pages/about.md.
Here is the About Page
Here is my Jekyll Repo
Thanks!

Looking at your repo you don't have pages: true in it's YAML Front Matter. That's why comments are not displaying.
This is what you have.
---
title: 关于
permalink: /about/
date: 2015-07-23
---

Thanks, my bad... forget to push local repo to live repo.
Get fixed!


ft/pinned-documents

Description
This PR implements the ability to pin some documents at the top
Fixes #462
Type of change
Please delete options that are not relevant.

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

Screenshots

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Is the UI design for this ready @kelvinkipruto?

@kilemensi No update in Figma yet.

@kilemensi Now Ready


chore(repo): Major tech debt

Improvements:

[x] introduce pond workers, move jobs to operate on the a producer consumer software design pattern.
[x] introduce metrics
[x] Decouple job package from worker package, generic should help. Then pass in type at instantiation. (in baseapp / jm)
[x] Standardize job interfaces.
[ ] Move JobManager out of the baseapp? Maybe?
[x] Handle all jobs using new producer consumer pattern.
[ ] Refactor subscription based jobs to abstract away chan usage and decouple from go-ethereum
[ ] Improve cmd package, handle config management better. It's too hard to use rn, very opinionated.
[ ] Introduce core package? standardize interfaces.
[x] Standardize Template App
[ ] Document Architecture

@calbera do we wanna merge this and then just continue to cleanup / iterate? Or keep it open until all is good?

you can merge idrc, just we shouldn't update bts until this is fully good

it's stable, just not all things cleaned up. external APIs won't change much. But whatever you guys think is best for bts

@ocnc @calbera @transmissions12


AttributeError on opentelemetry when initializing Chroma from documents

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.

Example Code
from langchain_community.vectorstores import Chroma
from langchain_openai import OpenAIEmbeddings
from chromadb.config import Settings

db = Chroma.from_documents(texts, OpenAIEmbeddings(disallowed_special=()), client_settings= Settings( anonymized_telemetry=False))
retriever = db.as_retriever(
    search_type="mmr",  # Also test "similarity"
    search_kwargs={"k": 8},
)

Error Message and Stack Trace (if applicable)
Traceback (most recent call last):
File "lchain.py", line 26, in
from chromadb.config import Settings
File "/home/duarte/.local/lib/python3.8/site-packages/chromadb/init.py", line 5, in
from chromadb.auth.token import TokenTransportHeader
File "/home/duarte/.local/lib/python3.8/site-packages/chromadb/auth/token/init.py", line 26, in
from chromadb.telemetry.opentelemetry import (
File "/home/duarte/.local/lib/python3.8/site-packages/chromadb/telemetry/opentelemetry/init.py", line 11, in
from opentelemetry.exporter.otlp.proto.grpc.trace_exporter import OTLPSpanExporter
File "/home/duarte/.local/lib/python3.8/site-packages/opentelemetry/exporter/otlp/proto/grpc/trace_exporter/init.py", line 24, in
from opentelemetry.exporter.otlp.proto.common.trace_encoder import (
File "/home/duarte/.local/lib/python3.8/site-packages/opentelemetry/exporter/otlp/proto/common/trace_encoder.py", line 16, in
from opentelemetry.exporter.otlp.proto.common._internal.trace_encoder import (
File "/home/duarte/.local/lib/python3.8/site-packages/opentelemetry/exporter/otlp/proto/common/_internal/trace_encoder/init.py", line 44, in
SpanKind.INTERNAL: PB2SPan.SpanKind.SPAN_KIND_INTERNAL,
AttributeError: 'EnumTypeWrapper' object has no attribute 'SPAN_KIND_INTERNAL'
Description
Trying to follow the Code understanding tutorial (https://python.langchain.com/docs/use_cases/code_understanding#use-case), find myself with an AttributeError related to opentelemetry. Tried reinstall the appropriate packages and turning off the usage of telemetry when initializing chroma but the issue persists.
System Info
System Information

OS:  Linux
OS Version:  #1 SMP Fri Apr 2 22:23:49 UTC 2021
Python Version:  3.8.10 (default, Nov 22 2023, 10:22:35)
[GCC 9.4.0]

Package Information

langchain_core: 0.1.26
langchain: 0.1.9
langchain_community: 0.0.24
langsmith: 0.1.7
langchain_openai: 0.0.7

Packages not installed (Not Necessarily a Problem)
The following packages were not found:

langgraph
langserve

What version of opentelemetry

@liugddx i have the same issue i have opentelemetry-sdk version 1.23.0

I am running the very first notebook of your tutorial - https://github.com/langchain-ai/rag-from-scratch/blob/main/rag_from_scratch_1_to_4.ipynb

AttributeError: 'EnumTypeWrapper' object has no attribute 'SPAN_KIND_INTERNAL'

this fixed it for me:
pip install opentelemetry-exporter-otlp --upgrade


Install addons-validator and configure it's path. Fixes #881

The failing travis test is from my accidentally pushed branch to olympia repo directly.

r+wc. Such excitement, wow addons-validator, much happiness!


Dev documentation search feature isn't working

https://fluent.docs.pyansys.com/version/dev/search.html
Could be related to:
https://github.com/ansys/pyfluent/pull/2040
https://github.com/ansys/pyfluent/pull/2024
Nightly dev doc build is failing:
https://github.com/ansys/pyfluent/actions/workflows/nightly-dev-doc-build.yml
File "/home/runner/.local/lib/python3.10/site-packages/ansys/tools/meilisearch/templates/__init__.py", line 79, in render_template
    if "localhost" in urls[0]:
IndexError: list index out of range

That issue was fixed, but a new one cropped up:
 Traceback
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 857, in _runCallbacks
    current.result = callback(  # type: ignore[misc]
  File "/home/runner/.local/lib/python3.10/site-packages/scraper/src/documentation_spider.py", line 178, in parse_from_start_url
    self.add_records(response, from_sitemap=False)
  File "/home/runner/.local/lib/python3.10/site-packages/scraper/src/documentation_spider.py", line 152, in add_records
    self.meilisearch_helper.add_records(records, response.url, from_sitemap)
  File "/home/runner/.local/lib/python3.10/site-packages/scraper/src/meilisearch_helper.py", line 123, in add_records
    self.meilisearch_index.add_documents(cleaned_records)
  File "/home/runner/.local/lib/python3.10/site-packages/meilisearch/index.py", line 381, in add_documents
    add_document_task = self.http.post(url, documents)
  File "/home/runner/.local/lib/python3.10/site-packages/meilisearch/_httprequests.py", line 73, in post
    return self.send_request(requests.post, path, body, content_type)
  File "/home/runner/.local/lib/python3.10/site-packages/meilisearch/_httprequests.py", line 57, in send_request
    return self.__validate(request)
  File "/home/runner/.local/lib/python3.10/site-packages/meilisearch/_httprequests.py", line 110, in __validate
    raise MeilisearchApiError(str(err), request) from err
meilisearch.errors.MeilisearchApiError: MeilisearchApiError. Error code: internal. Error message: MDB_PANIC: Update of meta page failed or environment had fatal error Error documentation: https://docs.meilisearch.com/errors#internal Error type: internal
<IP_ADDRESS> - - [17/Oct/2023 07:49:55] "GET /api/solver/_autosummary/settings/print_thread_clusters.html HTTP/1.1" 200 -
2023-10-17 07:49:56 [scrapy.core.scraper] ERROR: Spider error processing <GET http://localhost:8000/api/solver/_autosummary/settings/maximum_allowed_effctive_relaxation.html> (referer: None)
Traceback (most recent call last):
  File "/home/runner/.local/lib/python3.10/site-packages/meilisearch/_httprequests.py", line 107, in __validate
    request.raise_for_status()
  File "/home/runner/.local/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://backend.search.pyansys.com/indexes/pyfluent-vdev/documents

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 857, in _runCallbacks
    current.result = callback(  # type: ignore[misc]
  File "/home/runner/.local/lib/python3.10/site-packages/scraper/src/documentation_spider.py", line 178, in parse_from_start_url
    self.add_records(response, from_sitemap=False)
  File "/home/runner/.local/lib/python3.10/site-packages/scraper/src/documentation_spider.py", line 152, in add_records
    self.meilisearch_helper.add_records(records, response.url, from_sitemap)
  File "/home/runner/.local/lib/python3.10/site-packages/scraper/src/meilisearch_helper.py", line 123, in add_records
    self.meilisearch_index.add_documents(cleaned_records)
  File "/home/runner/.local/lib/python3.10/site-packages/meilisearch/index.py", line 381, in add_documents
    add_document_task = self.http.post(url, documents)
  File "/home/runner/.local/

Now causing issues for nightly and 0.18 release:
Nightly Development Documentation Build
Release Documentation Build

https://github.com/ansys/pyfluent/actions/runs/6556026309 the dev docs is working fine from my side today.

So nothing was changed but a re-build passed? Can confirm dev doc search now works as well
Good old "just reboot and try it again" :)
Waiting to see if the release docs now work as well, before closing the issues

The release docs build passed, but now neither dev docs nor release docs meilisearch works:

The search results appear if I wait for a few seconds after entering the search string. I checked pyaedt docs behaves in the same way. Also, building the index takes more than 4 hours.
@Revathyvenugopal162 Can anything be done for both slowness?

Thanks @mkundu1, you're absolutely right. From some quick tests it seems it can take 6-10+ seconds sometimes, you have to not click or do anything and just wait after typing the search string. If you press enter or click elsewhere then it doesn't work as you can see in my GIF above.
Exact same issues in the PyAEDT docs search:
https://aedt.docs.pyansys.com/version/stable/index.html
This looks like a straight downgrade from the search function we had before, for example see:
https://fluent.docs.pyansys.com/version/0.17/search.html which works great in my opinion.
Pressing enter to get the results immediately feels better to me than having to wait without clicking anything.

Thanks @mkundu1, you're absolutely right. From some quick tests it seems it can take several seconds sometimes, you have to not click or do anything and just wait after typing the search string. If you press enter or click elsewhere then it doesn't work as in my GIF above.
As Mainak noted, exact same issues in the PyAEDT docs search: https://aedt.docs.pyansys.com/version/stable/index.html
This looks like a straight downgrade from the search function we had before, for example see: https://fluent.docs.pyansys.com/version/0.17/search.html which works great in my opinion and is always pretty much instant.
Pressing enter to get the results immediately feels better to me than having to wait without clicking anything.
Also, why is there this dropbox:  Is this going to be integrated with other PyAnsys repos?
Update: given the issues and slowness described above, the plan for now is to revert to the previous search methodology, and try pymeilisearch again later.

yes, it is slow because pyfluent have lots of document to search. We are looking for the solution to make it fast. We will update to you . pinging @jorgepiloto

Thanks for the explanation @Revathyvenugopal162, note it is not only slow in PyFluent, it is also somewhat slow in PyAEDT https://aedt.docs.pyansys.com/ (at least the first time you use it)
And if you press enter or click anywhere else before results show up, then the search breaks, as in my GIF above, same issue for both repositories: https://github.com/ansys/pyfluent/issues/2093#issuecomment-1769221964

Working correctly now:
https://fluent.docs.pyansys.com/version/dev/search.html
https://fluent.docs.pyansys.com/version/stable/search.html
We can try the new search features again in the future


No Documentation

It'd be great if I new what any of the code did, and how I could modify/install/use/whatever your CMS.

yes this is a meaningless issue to get your attention.

@ChilliByte Hi! I will add some docs very soon. PS, I edited your comment, to add some exclamation marks.

:D :+1:


Agent does not display "No more private agent slots available" error

When an xplat agent is registered against an account that does not have enough private agent slots purchased, it simply shows a 400 Bad Request error and does not log out the exception message.

fixed


Proposal: New cmdlet for generating passwords

Proposal summary
How about adding a Cmdlet to generate a random password? 🔑
Think of the name as New-Password, for example.
Background
In the .NET Framework, We can use the static method [System.Web.Security.Membership]::GeneratePassword().
However, this method is not implemented in .NET Core. We need to consider alternative method.
Of course, it is not very difficult to implement our own, but I think it is convenient if it is provided as a standard Cmdlet.
Proposed usage
I want to implement some parameters so that we can use it flexibly.

Generates a random password string as specified length

New-Password -Length 10
# RyP5!P%Kx6

Generates a random password string with some common conditions

New-Password -Length 10 -MinNumberOfNumbers 1 -MinNumberOfUppercaseLetters 1 -MinNumberOfLowercaseLetters 1 -MinNumberOfSpecialCharacters 1

Generates a random password string using the specified character set.

New-Password -Length 10 -CharacterSet ('a'..'z')
# xrhupiqbcg

Generates a random password as [SecureString]

New-Password -Length 10 -AsSecureString
# Type of output to be [SecureString]

Proof of concept
PowerShell implementation for proof of concept. Most parameters are not implemented and no error checking is performed.
function New-Password {
    [CmdletBinding()]
    [OutputType([String])]
    param (
        [Parameter(Mandatory, Position = 0)]
        [ValidateRange(1, 128)]
        [int]$Length,

        [Parameter()]
        [char[]]$CharacterSets
    )

    if (-not ($PSBoundParameters.ContainsKey('CharacterSets'))) {
        $CharacterSets = [char[]]'0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ!@#$%^&*()_-+=[{]};:<>|./?'
    }

    -join ((1..$Length) | ForEach-Object { Get-Random -InputObject $CharacterSets })
}

It can contain all visible characters of utf8?
Provide basic ASCII characters by default, add extended options.

Hi @he852100
I think it's possible to extract a random string from all UTF8 characters, but the UTF8 character set is so enormous that it feels somewhat exaggerated considering the use of this Cmdlet. I don't know if it will be useful.
But the idea of adding an option to allow non-Latin characters to be included in the output would be interesting. 😄

No need to include any characters in the cmdlet。
As long as you know the number of characters, you can generate a few random numbers in it, and you can get the characters by random numbers

What I wanted to say is that if we want to include all UTF8 chars in the output, we need to consider emoji, IVS, etc., which may make the implementation more complicated than necessary.
I suggest that the characters output by default be in the range of ASCII printable characters. The user can extend the range of output characters from U+0000 to U+FFFF by using -CharacterSet parameter if necessary.
$AllChars = [char]0x0000..[char]0xffff
New-Password -Length 10 -CharacterSet $AllChars

There's a number of password generating modules on PowerShellGallery already, perhaps we don't need one with PowerShell?

The GetPassword module by Simon Wåhlin does what I want with flexible password generation, and it also works with PowerShell 7.
https://www.powershellgallery.com/packages/GetPassword/<IP_ADDRESS>
I would like to introduce this module and close this Issue.
Thank you very much.


Receiving "Invalid reference token: bundled" in CI

Context
We've been seemingly spurious errors in CI with Invalid reference token: __bundled__. This is happening here:
https://github.com/openai/openai-python/actions/runs/10010129012/job/27670617482
Current Behavior
[4:35:54 PM] › [HTTP SERVER] post /threads/string/messages ✖  error     Request terminated with error: Error: Invalid reference token: __bundled__

Expected Behavior
I wouldn't expect the prism server to have a fatal error here
Steps to Reproduce
npm exec  --package=<EMAIL_ADDRESS>-- \
      prism mock https://storage.googleapis.com/stainless-sdk-openapi-specs/openai-518ca6c60061d3e8bc0971facf40d752f2aea62e3522cc168ad29a1f29cab3dd.yml

curl -L localhost:4010/threads/string/messages -X POST \
            -H 'Authorization: Bearer xxx' \
            -H 'Content-Type: application/json' \
            --data '{"content":"hello","role":"user"}'

Strangely this does not happen after cloning the repo, then running the cli through (cd packages/cli && yarn cli mock https://storage.googleapis.com/stainless-sdk-openapi-specs/openai-518ca6c60061d3e8bc0971facf40d752f2aea62e3522cc168ad29a1f29cab3dd.yml)
Environment

Versions: 5.8.3, 5.8.2, 5.7.0
OS: MacOS 13.4 (but also in CI)

Removing yarn.lock and running (cd packages/cli && yarn cli mock https://storage.googleapis.com/stainless-sdk-openapi-specs/openai-518ca6c60061d3e8bc0971facf40d752f2aea62e3522cc168ad29a1f29cab3dd.yml) seems to reproduce the issue actually, so it may just be a package version bump.

After some bisecting it seems like upgrading from
<EMAIL_ADDRESS>to
<EMAIL_ADDRESS>
causes a breakage, which breaks on the consumer end of the library.

Note that short of forking to pin the @stoplight/json dependency we aren't aware of any workarounds

Should be fixed by: https://github.com/stoplightio/json/pull/141

@mnaumanali94 We are seeing this issue again.
https://github.com/openai/openai-go/actions/runs/10322573838/job/28578086104?pr=7

@mnaumanali94 this time I think it's because prism-http

yup it looks like pinning these deps fixes it https://github.com/stainless-api/prism/commit/335f8a829e65a9777beed654dc57f1598be55e86


artistpic and albumart don't show image properly anymore

Getting a downloadable .jpeg instead of an embedded image back, on the albumart and artistpic commands (at least)

Discord desktop client for Windows:
Stable 126213 (75b3f22) Host 1.0.9004 Windows 10 64-Bit (10.0.19044)
Bot does have permissions: Send Messages, Embed Links, Attach Files, Use Application Commands

After a quick glance it seems like the discord API changed something so that messages need to actually specify that they want to embed an image I think. https://discordjs.guide/popular-topics/embeds.html#using-the-embed-constructor
@dantco mentioned wanting to take a look at this so I may leave it to them

also - are you embedding the image URL to the discogs site, or embedding a (resized) copy of the JPG/PNG?


Fi 444 try multiple values in search

This will make the generator look for fixed values and value set info when creating the first search of a sequence. The first search will search on all the possible values until it finds something. This also updates the capability statement to include new diagnostic_report searches.
Here are the list of sequences that this applies to:
Careplan
Careteam
Smoking Status
Lab Results
Pediatric Weight Height
Pediatric BMI Age
DiagnosticReport Lab
DiagnosticReport Note
Pulse Oximetry
You can verify that this is working by running one of the above sequences and looking at the requests for the first search. You can use patient SMART-1288992 on https://api.logicahealth.org/czhour4/open. There should now be a MedicationRequest with an intent of 'Order'. You should see three MedicationRequest requests before it hits the order search.
Submitter:

[X] This pull request describes why these changes were made
[X] Internal ticket for this PR: https://oncprojectracking.healthit.gov/support/browse/FI-444
[X] Internal ticket links to this PR
[X] Internal ticket is properly labeled (Community/Program)
[X] Internal ticket has a justification for its Community/Program label
[X] Code diff has been reviewed for extraneous/missing code
[ ] Tests are included and test edge cases
[X] Tests/code quality metrics have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure
where appropriate, and accomplishes the task's purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure
where appropriate, and accomplishes the task's purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Could you give a patient id and server and resource that shows this running?
I'm using patientid SMART-1288992 on your open server but that doesn't have MedicationRequests, which seems to be what this applies to.

Updated the PR description with more testing info.

I think this is good once it's rebased.


Update email.html

Just added an escape for the quote, since its easy to just copy, paste and modify right away for a simple clean responsive mail template.

This doesn't seem like it would work in, say, a web-based email client - the "single-quote" entity code is ' or ', whereas HTML would just render \' as-is.


Changed format of override from  to  in en and in other translations

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #10844

Description

I've changed the format of "override" in the description from <code> to <em>. Also changed the same for other translations as well.
Though there was another PR already submitted, I'm going ahead and submitting as I've taken care of the translations as well, if its any worth.
Sorry for the delay as this was my first time ever open source contribution. Though the fix itself was so small, it took a while to setup freecodecamp and figure out the process.

I missed to rebase before I started to make the fix. I'm going to redo the PR, hence closing this one.


Cannot select multiple files on Mac

For some reason on a Mac, you can only select one file at a time, even though ideally you should be allowed to upload multiple.
This might be my fault, as I lazily made "count" equal to 1 on all dialogs since the number didn't seem to do anything on Windows.  Perhaps this number really does matter, so I should change it to see if it is the problem.  Without a Mac to test on, though, it is going to be hard to debug.

The "count" field has nothing to do with file selection limits.  It is actually used to determine the number of possible extensions available.
The Mac problem is related to the systools library invoking the wrong kind of dialog.  Apparently on Macs, opening a file limits it to one file.
The only solution it seems without delving deep into Objective C is to allow the selection of a folder rather than a file.


link type (System.LinkTypes.Dependency) does not exist in project

Describe the problem
A clear and concise description of what the problem/bug is.
Getting error:
[I][15:57:11] Processing 121/57276 - wi '62192', jira 'US-3469, rev 2'.
[E][15:57:11] '[Added] US-3469/62192->US-3470/62193 [System.LinkTypes.Dependency]' - link type (System.LinkTypes.Dependency) does not exist in project
[W][15:57:11] ''US-3469', rev 2' - not all changes were saved.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

run wi-import
Tool version

Version of the jira-azuredevops-migrator tool [e.g. 2.3.117]
3.0.139

Attachments
Please attach the following files:

config.json
jira-export-log.txt
wi-import-log.txt
US-3470 - Copy.json.txt

US-3469 - Copy.json.txt
jira-export-log-230721-143348.txt
wi-import-log-230721-155604.txt
config-agile_SMS3 - Copy.json.txt
Screenshots
If applicable, add screenshots to help explain your problem.

Issue is exactly what the error message is saying. :)


[GSSoC'23] [Docs] Adding a small Licenses section to the readme and a MIT Licenses badge

Is your feature request related to a problem? Please describe.
The readme doesn't have any info about Licenses,
Describe the solution you'd like
I can add a small Licenses section
and a MIT badge as well

Describe alternatives you've considered
No response
Additional context
Please assign me this issue under GSSoC'23
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Please assign me this issue under GSSoC'23

We don't need this for now.


increased susceptiblity to malignant hyperthermia - typo

From Monika:
MP:0020214 increased susceptiblity to malignant hyperthermia is spelled incorrectly. Susceptiblity needs to be changed to susceptibility.

Typo has been corrected (changed to "susceptibility").


Improve logging usage

I will copy the commit message from first commit here, since it got lost.
Improve logging usage
The structured logger is good for producing comprehensive logs, however it is
not that good for being used directly in the code.  Let's introduce some
changes that:

Make the code shorter, so it's easier to read.
Make the logging lines shorter, so the logging messages can be read without
horizontal scrolling.
Reduce the chain of method calls so one can see easily also code other than
logging in editors highlighting method calls.
Reduce code duplication.

To not make logging too messy, methods for setting message levels are turned
into terminal methods.  Those methods are almost always used, so they can be
used as such rather than using extra Msg method call.  In rare cases when we
don't want to use typical logging patterns, new Level method can be used.
It would be nice to access logging methods from objects being logged.
However due to Go limitations we can't do that easily, so we have to use
something like vm.Log().Info' rather than simply vm.Info'.

I like this patch. The logging is now more readable and shorter to write.

retest this please

David Vossel<EMAIL_ADDRESS>writes:

The only thing that caught my eye was the VM object's log function. I'm not sure that's a pattern we want to start using.
I'd be okay with still having to specify Object() to avoid adding Log() functions for each cluster object we work with.

It's not necessary to add Log() to each cluster object, just to those
that are worth it (i.e. define once, use many times) – the rest can use
Object().  I don't know whether there are already some ideas about using
different loggers, but if we like to use separate loggers for some
objects then object Log() functions will help with that.  And Log()
implementation is trivial, so it's not a big deal.
Despite that I'm not particularly happy with it too, it lacks some
elegance.  But it's IMO still better to use o.Log() than let's say
logging.Object(o), for the reasons mentioned in the commit message.
Maybe somebody has a better idea?

In pkg/logging/logging_test.go:

@@ -297,8 +323,8 @@ func TestObject(t *testing.T) {
setUp()
log := MakeLogger(MockLogger{})
log.SetLogLevel(DEBUG)

vm := v1.VirtualMachine{}
log.Object(&vm).Log("test", "message")

vm := newVM()

why change this?

To avoid circular package references.

Despite that I'm not particularly happy with it too, it lacks some
elegance.  But it's IMO still better to use o.Log() than let's say
logging.Object(o), for the reasons mentioned in the commit message.

I agree that it o.Log() looks nicer than logging.Object(o). I don't feel good about making our logging package a dependency for things like /pkg/api/v1 now though. That's what we have to do in order to get this functionality. It's also why you had to work around the circular dependency.

I can understand the desire to make the logging lines a little bit shorter, however, I am also not very happy with the changes here.
We are using a structured logger, and I like that with the builder we have clearly structured way on what logs what. E.g. the .Object(vm), logs object information. If we later on also want to log the controller, we can simply do something like .Controller(migration).Object(vm), or .Object(vm).ManagedBy(migration). I also explicitly like the separation of .Reason() and .Msg(), because it also corresponds to what will be logged in which fields.
Some thoughts on how to make the lines a little bit shorter:

Having a the logging.DefaultLogger() is very long. Renaming logging to e.g. log and have a global Log variable which is set to logging. DefaultLogger().
Since V() only makes sense in combination with Info(), let's combine it

The outcome would be:
log.Log.Info().With("costm_key", "custom_val" ).Msg("whatever") # defaults to InfoV(1)
log.Log.InfoV(3).With("costm_key", "custom_val" ).Msg("whatever")
log.Log.Error().Reason(err).Msg("lala") # reason is not a must, but msg is.

It can be made even shorter by having a log.Error(), log.Info(), ... global method for the default logger in the log package.
If it is confusing for people, that .Msg() or .Msgf() are the the last ones executed, renaming it to .Log() or .Logf() would also be an option for me.

Since V() only makes sense in combination with Info(), let's combine it

Please let's keep at least some consistency in the Go universe and keep V() a function.
As for the logging itself, if we really want structured logging (which I'm not fan of, not with the code burden that glog doesn't carry) AND a bit of consistency with kube*, I could imagine getting rid of message and making Info, Error, Warning etc. terminals in the builder. That would lead to logging lines such as
logging.DefaultLogger().Object(VM).Reason(Err).Error("VM isn't running")
The advantage of that is if you remove the structured part, you'll arrive to a point where the line looks similarly to other logging frameworks:
logging.DefaultLogger. ... .Error("VM isn't running")
---------------------/
imagine this being *log

logging.DefaultLogger().Object(VM).Reason(Err).Error("VM isn't running")

+1

As for the logging itself, if we really want structured logging (which I'm not fan of, not with the code burden that glog doesn't carry)

I really want to use structured logging.

David Vossel<EMAIL_ADDRESS>writes:

I agree that it o.Log() looks nicer than logging.Object(o). I don't
feel good about making our logging package a dependency for things
like /pkg/api/v1 now though. That's what we have to do in order to get
this functionality.

OK, I can omit that in the patch and we can look for better ways to
express it in future patches (again: suggestions welcome).

Changing logging.DefaultLogger() to log.Log.

Works for me

Making Info(), Error(), etc. terminals.

Works for me

Nobody has protested against using additional arguments for formatted
strings so I can think I can keep that too.

I would suggest Error() and Errorf() if that is what you mean.

I believe I made all the agreed changes in the updated version of the patch.

It sounds like we're in agreement this should go in.
Since this touches so many files, we should merge this immediately once it is rebased.

Rebased and updated.

ok to test


Tracking appVersion bug fix

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1172
Originally created by @derek-knox on 2019-10-22 17:46:37

appVersion is apparently Beta. GA responded with 200 success on our tracking pings even though we were able to confirm an issue via prepending https://www.google-analytics.com/debug/ to a Google Analytics ping request which resulted in:
{
  "hitParsingResult": [ {
    "valid": false,
    "parserMessage": [ {
      "messageType": "ERROR",
      "description": "A value is required for parameter 'an'. Please see http://goo.gl/a8d4RP#an for details.",
      "messageCode": "VALUE_REQUIRED",
      "parameter": "an"
    } ],
    "hit": "/debug/collect?v=1\u0026_v=j79\u0026a=350108828\u0026t=pageview\u0026_s=3\u0026dl=http%3A%2F%2F<IP_ADDRESS>%2Fpipeline%2Fextract%2F\u0026dp=[Customers/Users](https://github.com/meltano/meltano/milestone/2)Fmodel\u0026ul=en-us\u0026de=UTF-8\u0026dt=Meltano%3A%20Model\u0026sd=24-bit\u0026sr=3840x1080\u0026vp=1125x978\u0026je=0\u0026av=1.2.0\u0026_u=SACAAEABE~\u0026jid=\u0026gjid=\u0026cid=534750961.1571760055\u0026tid=UA-132758957-2\u0026_gid=1765455882.1571760055\u0026cd1=652b6956-08cb-49a3-8bbf-2945986475b2\u0026z=1211946417"
  } ],
  "parserMessage": [ {
    "messageType": "INFO",
    "description": "Found 1 hit in the request."
  } ]
}

The solution will to just use a custom dimension for our app version. One liner.

View 3 previous comments from the original issue on GitLab


Unable to change the "OK" button color and hover color

@AstheriusLC
Fixed with the new version, now you can change all the parameters. Please refer the new docs.


Rare bug. Confusing error Unexpected EOF line 2 when file doesn't end with a '\n'

Describe the bug
When Norminette process a file that don't end with a '\n' it will display the error ```Unexpected EOF line 2````. There are times that the user has set the editor not to add '\n' automatically at the end of the file. If the last line of the file contains no newline, but instead it ends with whitespace character like ' 'or '\t' then norminette will give this error.
Erroneous code
int main(void)
{
}
'\t' <-- the file ends with a tab instead of a '\n' character.

Additional infos

OS: ubuntu
python --version: 3.8.6
norminette -v: 3.3

Additional context
This bug won't appear often because in general the editors will add a '\n' at the end of a file automatically unless it is told not to. But it can be a little bit confusing for people who are not aware of it. My first instinct was to look at line 2 of my c-file.

Hello,
I've changed the error message to be more specific, but I can't really let the norminette run after finding this, so raise is the best solution. Will push with the next update


Publish 07/16/2021, 10:30 AM

Docs Build status updates of commit cbf77d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

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

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

exchange/exchange-ps/exchange/New-LabelPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-LabelPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-SafeAttachmentPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

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


Prompting generates 'event.js' error

Crashes with the code from the doc 😞
    var done = this.async();
    this.prompt({
      type    : 'input',
      name    : 'name',
      message : 'Your project name',
      default : this.appname // Default to current folder name
    }, function (answers) {
      this.log(answers.name);
      done();
    }.bind(this));

Any help appreciated ! See screenshot below, cheers!

You need to update yo: npm -g update yo

Thanks for the quick comeback! Did it already and it keeps crashing... Should I rollback to a prior version of the generator ?

So you're using generator-angular2-application-scaffolder? I'll check what's up later today.

Thank you !!

So, I didn't see that's your generator.
yeoman-generator v0.23 contains a breaking change regarding the this.prompt API. It now returns a promise and doesn't take a callback. You could've see this in our release notes https://github.com/yeoman/generator/releases/tag/v0.23.0
My guess is after updating yo you ran into the API error which was different than the first one you posted here. If the first one persist, then try uninstalling/reinstalling yo.

I haven't checked the change log. That's great, thanks!
Le jeu. 5 mai 2016 à 08:40, Simon Boudrias<EMAIL_ADDRESS>a
écrit :

So, I didn't see that's your generator.
yeoman-generator v0.23 contains a breaking change regarding the
this.prompt API. It now returns a promise and doesn't take a callback.
You could've see this in our release notes
https://github.com/yeoman/generator/releases/tag/v0.23.0
My guess is after updating yo you ran into the API error which was
different than the first one you posted here. If the first one persist,
then try uninstalling/reinstalling yo.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/yeoman/yo/issues/427#issuecomment-217087138


Update doc for helm 3.x.x issue

--service-account not available with Helm 3.x.x

This PR should no longer be needed as we've refactored docs to show using Helm 3

Closing this issue because the docs were updated for Helm 3


docs: Adding instructinon for switching to the right namespace

What does this PR do?
docs: Adding instruction for switching to the right project
What issues does this PR fix or reference?
Is it tested? How?

PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

/test v8-devworkspace-operator-e2e


Upgrading to entities package 13

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

Description
Upgrading the entities package to latest.
Tests
tested it locally. No errors, everything works as expected
Documentation
updated docs
Primary reviewers
If your change will take a long time to review, you can name at most two primary reviewers who are ultimately responsible for reviewing this request. @ mention them.

Burst and IncrementalCompiler dependencies can move out of Core and into project Manifest.

Actually.. ignore what I said.. leave the dependencies


Resize filter not working on woocommerce product tease page

Expected behavior
I want to resize thumbnail on woocommerce product tease view.
Actual behavior
Nothing happens, crop image not created.
Steps to reproduce behavior
<img src="{{ TimberImage(post._thumbnail_id).src | resize(250, 250, '#FFFFFF') }}" />
What version of WordPress, PHP and Timber are you using?
WordPress 4.7.3, PHP 5.6, Timber 1.2.4
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
Upgraded to newest version via plugin updater in WordPress dashboard

@boochamoocha Does it still not work or was it resolved in https://gitter.im/timber/timber?at=58d256d16701410e5862fee4?

Closing this. The problem seems to have been solved in the Gitter channel.


x808 file uploader

User Story
As a TS (Katy) I would like to upload a file and associate it with a worknumber, to reflect and record the work performed out of STAN and to allow customers easier access to them.
Acceptance
Select worknumber from dropdown list
Upload file(s)
*to rewrite over file with the same name (warning appear you are doing this)
be able to retrieve/roll back database
How much space does this need? roughly ~5mb month = 56.18mb per year round up to 60-75mb per year

@khelwood @seenanair the feature is working well for excels but not for pdfs, I keep getting an error but it doesn't say what the error is
file manager PDF error.pptx

@khelwood I got the error for pdf while I tested locally now - 'http://localhost:3000/files?workNumber=SGP8 500 (Internal Server Error)'

@khelwood  I will check why the server error message is not displayed in ui

@KatyTudor  I have increased the filename limit to 100.


elide Task.FromResult asyncs

given these are not actual state machines, there is no dependability concerns

@erdembayar sorry, not using any analyzers. but i will do a pass on the .editorconfig and see if i can suggest some improvements that will help keep the code cleaner


Two errors when running

I'm getting the following two errors when running this program on a Mac command line:
Error: Not able to read a 3 byte int.
Failed test on line 167 in /tmp/CiFbuild/Source/ichatReader.c.

Yep, similar error Failed test on line 221 in /tmp/CiFbuild/Source/ichatReader.c.


Add test for drawing delay with CSS-only zoom

This commit adds a test for 0603d1ac1843bc4098d74382beda6cc511350ccd. Before the fix the test fails with 11 pagerendered events, while after the fix it passes.

I know that you are trying to move away from waitForTimeout, but I don't know how else to test this. I cannot simply wait for an event to be emitted, because I am testing that it is not emitted.

Ok I think I can remove the waitForTimeouts

/botio integrationtest

Oh windows, I'll check what it is about.

Isn't the problem that the first page can already be done rendering before the promise in the test is awaited because we already register the event handler in beforeEach and increment the counter there? Unless I'm mistaken the beforeEach handler can already eat the first pagerendered event before createPromiseForFirstPageRendered is called and then we basically attach to the event bus too late.

I noticed that pagerendered events have a timestamp, so I rewrote the test to instead measure that the timestamp is at least drawingDelayms after I called increaseScale/decreaseScale.

/botio integrationtest

Thank you for implementing this test!


Redis 2.8.19 BGREWRITEAOF - Failure Permission Denied

Hi,
We currently have a Redis 2.8.19 on Win 2012 STD.
The box has 256GB Mem and the DB is eating around 187GB
Due to the DB using so much memory we have opted to use AOF to store the data rather than the rdb file due to the memory requirements of doing BGSAVE on the Windows version of Redis.
Each night we run 'BGREWRITEAOF' to regenerate the aof file so its more efficient if it has to reload the dataset.
This morning the process failed in the error logs we see
"EndForkOperation: 0x00000005 - EndForkOperation: Killing forked process failed.: permission denied"
This is a bit of a mystery the new aof file has been generated but still showing the temp file name, the original aof file is still in place. Now the new aof file looks the correct size (~43GB) like its been fully generated.
I'm under the assumption that when the aof file is generated, redis tries to delete the old aof file then renames the new aof file to the correct file name. Again I'm assuming the delete option failed but I could be wrong.
I thought this might have been related to the AV software however the entire drive holding the redis data is excluded from both real-time and manual scanning (the drive holds nothing other than redis)
What doesn't make sense is why the failure killed the entire redis-server process. The idea of the BGREWRITEAOF process is that if it fails the redis-server process should not die. So in our case we had to wait 2.5hrs for the server to re-load the dataset.
Unfortunately the permission denied error doesn't explain what it couldn't do.

Thank you for reporting this issue. Two pieces of information would be helpful in determining the cause:

The redis log file. Could you upload it somewhere and share a link?
Information from Windows Error Reporting. In the Event Viewer, under Application, look for events with source "Windows Error Reporting" around the time of the crash.

Hi,
The redis event log can be grabbed from http://chrisdaley.net/redislog.zip I don't think its going to be much help to be honest
Nothing in the Application or System logs, all we get is "The Redis service terminated unexpectedly."
We had the service set to automatic recovery, 5min delay between restart however this has highlighted another weird problem. Sometimes when it loads the data into memory the logical drive where the AOF and Heap files are stored goes into meltdown essentially file browsing access in explorer is next to impossible, redis slows to a crawl when loading the data etc. Only way to recover is to manually kill the process in task manager (doesn't always kill it though). Nothing wrong with the drives, new batch of 8x Intel DC S3700 SSD's, Raid 6 array on a Dell PERC H720P Controller.
From a normal boot you get 1-2 days where Redis works and the 'BGREWRITEAOF' process functions correctly. Then on the next day it will fail and usually loading the dataset will go badly (as described above). Reboot the box and it will function correctly for another 1-2 days.
Totally removed the AV software however the problem persists so I don't believe that is the cause.

We have managed to get a bit further with identifying the cause, redis doesn't like it when MSSQL is installed on the same box it appears. We setup a clean box just W2012R2 with Redis installed it ran 100% stable for 7 days straight, BGREWRITEAOF worked perfectly each day.
Installed SQL Server 2014 Web x64, first rewrite worked which was 24hrs after install, the second failed in the same way as it did on the original W2012 server.
Based on the logs and the source code its failing somewhere in the cleanup routine, I have added some additional logging to see if we can identify which stage it fails at.

Interesting. It's possible that SQL Server and Redis are competing for memory resources. What are your memory configuration options in SQL Server? https://msdn.microsoft.com/en-us/library/ms178067.aspx
If you have the option of running them on separate machine, I would recommend that as a workaround.
To ensure that crash dumps are collected, please go to Control Panel\System and Security\Action Center\Problem Reporting Settings and make sure that "Automatically check for solutions and send additional report data, if needed".
I would normally recommend to also enable full memory dumps. But in your case, since Redis is using so much RAM, this might not be practcal.

As the ultimate troubleshooting aid, you could also enable collection of full-memory dumps.The instructions are here: https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).aspx . You can configure it for redis-server.exe only (the article explains how to do so).

We have found a possible cause for this random bug, we'll release a fix asap.

Hi @chrisd88,
we fixed some issues that may have caused the problem you reported.
Please upgrade to 2.8.2101.
Thank you.
The new 2.8.2101 release is available here.
This is an incremental release from 2.8.21 containing only fixes for Windows-specific bugs.
Note: we don't have yet a date for the availability of the new release through the nuget/chocolatey package managers.


remove Flag alias

Nice, toggled. Please mind the build failure (looks like whitespace).

BTW, should be Flag, Yes, and No be imported publicly?

@9il not necessarily - the functions involving those may be not used or have popular defaults.

Auto-merge toggled on

Why is this a good change? It significantly complicates the method signature. Is this to conditionalize the import of Flag?


Clean install on up-to-date Quest 2 crashes on start up

I’ve just installed Open Brush on Quest 2 and it constantly crashes on start up

Installed via App Lab

We can't reproduce this and as far as I'm aware nobody else has reported it. I know that's not very comforting for you but it's hard to know how to progress this.

My bad - although not my fault, directly - as this was an Oculus for Business Quest 2 headset, but hadn't been commisioned for that special (and very restricted) OS. Therefore, it wouldn't update past v29 firmware (as it wasn't on the list of 'commercial' devices). As O4B is being discontinued now, all these Q2s have been redesignated as normal headsets, and can now be updated. Open Brush now works fine, thankfully.


Bug when using density=True with chunks_to_segments=True

I think there is a bug when using density=True with chunks_to_segments=True. This can be demonstrated by testing Parseval's theorem for the case of chunked arrays.
For an unchunked array, the integral of the psd matches the variance:
import numpy as np
import xarray as xr
from xrft.xrft import power_spectrum

data = xr.DataArray(np.random.normal(0, 1, size=1000),
                    dims=['t'],
                    coords=[range(0,1000)])

psd = power_spectrum(data, dim=['t'])

print(f"Integral of psd: {psd.integrate('freq_t').values}")
print(f"Variance: {(data.std()**2).values}")

Integral of psd: 0.9578122989216458
Variance: 0.9577984563349068

However, if we chunk the array into more than one chunk, the integrals of the psd for each segment do not match the corresponding variances:
data_chunked = data.chunk({'t': 500})

psd = power_spectrum(data_chunked, dim=['t'],
                     chunks_to_segments=True)

print(f"Integral of psd: {psd.integrate('freq_t').values}")
print(f"Variance: {[(data[:500].std()**2).item(), (data[500:].std()**2).item()]}")

Integral of psd: [0.2404514 0.2382441]
Variance: [0.958114994451872, 0.9466505378063875]

This is because the N used in the normalisation with density=True is computed from the dimension sizes of the input array rather than from the chunk sizes (so in the example above, the powers are off by a factor of (1000/500)**2 = 4).

Hi Dougie! Thanks so much for this clear bug report.
I agree with your characterization of the bug. We would welcome a pull request to fix this. Is that something you would be interested in taking on?

Sure - I could have a stab

Ready for review @rabernat


Issue in package.json, Minify command does not work

Hola David,
Thanks for this great "quickstart example" on publishing node_modules. I am currently using it to publish a project on my local repository. In doing so I found out an issue.
It goes like,

<EMAIL_ADDRESS>minify D:\Angular_POC\angular-npm-module-seed-master
./node_modules/uglify-js/bin/uglifyjs dist/bundles/npm-module-seed.umd.js --screw-ie8 --compress --mangle --comments --output dist/bundles/npm-module-seed.umd.min.js

'.' is not recognized as an internal or external command,
operable program or batch file.

This is basically because of following line
"minify": "./node_modules/uglify-js/bin/uglifyjs dist/bundles/npm-machao-component.umd.js --screw-ie8 --compress --mangle --comments --output dist/bundles/npm-machao-component.umd.min.js",
My OS: Windows 7 64bit
Node -v: 6.10.2
Let me know if you have a workaround for the same. I will look at it as well when all my publish is successful.
Also,
It would be great if you include "how do we use published components/module in the target location" in the documentation as well.
Cheers,
Sudeep Rane

Probably just removing the "./" in Win systems would do the trick...

I tried this but no luck. I even tried following code,
"minify": "uglifyjs dist/bundles/npm-module-seed.umd.js --o dist/bundles/npm-module-seed.umd.min.js",
But that didnt work either, gave me parser errors.  So I am going to keep minification on hold for a while. :)

@BaamAadmi  Try "minify": "node ./node_modules/uglify-js/bin/uglifyjs dist/bundles/npm-machao-component.umd.js --screw-ie8 --compress --mangle --comments --output dist/bundles/npm-machao-component.umd.min.js"

@nipuna777 That did the trick, thank you


v6.2 JavaScript does not play nice with Angular

We upgraded our Angular app to use Foundation v6.2. The styling and positioning of the reveal modal is a lot better. However, Angular inside of the reveal modals doesn't execute anymore. It was working fine with Foundation v6.1.2. The browser console shows no errors, it just acts as though the Angular code is plain HTML. Angular doesn't execute inside the reveal modals at all. Our team has spent hours trying to figure it out, but with no luck. Ideas? Help?
BTW, we are using Angular v1.3.15.

Other than reworking the positioning logic, the other change we made to Reveal in 6.2 is moving the HTML of the modal to be inside the overlay element in the DOM. Before, the modal sat wherever it was in the document originally, which created a lot of issues with scrolling and positioning.
The issue might be related to the modal's HTML being moved.

@gakimball Is the reveal modal documentation (http://foundation.zurb.com/sites/docs/reveal.html) updated with the latest recommended markup?

Yes, the markup hasn't changed.

@gakimball Would you be able to look at our testing environment? Maybe there's something you'll see that I'm not saying. The link is below. Just scroll to the bottom of the left panel and then click "View results on other sites." Then enter a zip code in the search box and hit magnifying glass button. It's just refreshing the page instead of submitting the form.
https://platform-homie-dev.azurewebsites.net/

Is it possible the HTML is being moved after Angular initializes?

Depends on when you call $(document).foundation(). I would assume you have to call that after the complete Angular view has been initialized, so that the DOM is in place for Foundation plugins to attach to.
With that in mind, it's possible you need to listen for when the modal is done initializing, and then add some extra logic to account for it.
$('#modal').on('init', function() {
  // ...
});

I see the issue you described in the page you linked. You might need to set up that Angular logic after the modal is moved, if possible.

It doesn't appear to be just Angular. I am building an app using React and found out that my onClick handlers inside the Reveal markup are no longer firing after upgrading from 6.1.2 to 6.2.
Here's a sample of the code I am trying:

Log in

            Username:
            <input type="text" name="username" />

            Password:
            <input type="password" name="password" />

            <button className="button" type="button">Log in</button>

          <button className="close-button" type="button" onClick={this.handleCloseModalClick}>
            ×
          </button>

It seems like relocating the modal causes Angular/React bindings to fail because they're no longer nested within their mount node. Both Angular and React applications require you to define a parent element where your application with live. Relocating the modal essentially moves the node outside of that parent and it no longer becomes part of the application.

I don't suppose anyone has had any luck with this?

Unfortunately I just had to roll back.

click handlers also stopped working for me in angular 1.5. Since I obviously need the correct reveal positioning what am I supposed to do now?

This might help: http://circlingthesun.github.io/angular-foundation-6/

I think @circlingthesun's approach is correct.  Angular and React both operate under the assumption that they have complete control of the DOM, so interacting with Foundation 6's javascript plugins directly is always going to be a bit hit or miss.
It looks like a similar project for react is here: https://github.com/aruberto/react-foundation-components


Running OpenRadar on linux?

First, thank you guys for this amazing project.
I am trying to use radar on linux. However, it seems that we need mmwave studio in order to use OpenRadar. Since TI only have mmwave studio for windows, so currently we cannot use OpenRadar on linux. Is this correct?

Were you able to use OpenRadar on linux in the meantime? I'm facing the same issue right now. Maybe there is a way to control the DCA using the onboard switches, but from my understanding you would also need to start the radar module separately.

I have been trying to achieve this as well and I finally figured out how to do it. For my setup, I am using a IWR6843ISK with a MMWAVEICBOOST and DCA1000EVM. On the Software side I have written my own code to config the IWR6843ISK board and using the DCA1000EVM CLI interface to control the DCA board. This is how the switches on the board are set

Credit:  zigang Yang
Steps:

Flash the antenna with the out of the box demo binary

Generate a configuration using TI mmWave Demo Visualizer and update the lvdsStreamCfg parameter to enable data streaming, I am setting it to -1 0 1 0 to disable header bytes and disable point cloud to transfer through LVDS.

Send this configuration to the antenna board using PySerial. (I have written my own code for this, but one can use OpenRadar as well)

Reset the AR device using the CLI tool (for this purpose, I am launching the tool as a subprocess in my code)
subprocess.Popen(shlex.split('./DCA1000EVM_CLI_Control reset_ar_device  config.json'), cwd=cli_path)

Configure the DCA1000EVM FPGA
subprocess.Popen(shlex.split('./DCA1000EVM_CLI_Control fpga config.json'), cwd=cli_path)

Configure the DCA1000EVM recoding
subprocess.Popen(shlex.split('./DCA1000EVM_CLI_Control record config.json'), cwd=cli_path)

Start the antenna by sending "sensorStart 0\n" to the sensor
serial_port.write("sensorStart 0\n".encode())

Trigger the DCA1000EVM board. This will start the UDP data stream and save it using the CLI interface as if it was done using TI mmWaveStudio
subprocess.Popen(shlex.split('./DCA1000EVM_CLI_Control start_record config.json'), cwd=cli_path)

Stop the UDP stream
subprocess.Popen(shlex.split('./DCA1000EVM_CLI_Control stop_record config.json'), cwd=cli_path)

Stop the sensor
serial_port.write("sensorStop\n".encode())

I am trying a similar thing and I am fed up with developting with windows and Mmwavestudio, would you be so kind to share? I have a similar setup but with only the DCA1000 and a iwr6843isk board.

I am trying a similar thing and I am fed up with developting with windows and Mmwavestudio, would you be so kind to share? I have a similar setup but with only the DCA1000 and a iwr6843isk board.

We developed two ROS2 packages in order to use the sensor and board under linux. Maybe you can look into our code and test it out (it was initially developed as a python script). In case something is unclear, feel free to message me. Here is the link to the DCA1000EVM_CLI_ROS2 package.
Maybe in January I will try to implement our solution in OpenRadar and open a pull request.

Hey @3473f, could you update the link?
I'm very interested in using radars with Linux as well 👀

I am trying a similar thing and I am fed up with developting with windows and Mmwavestudio, would you be so kind to share? I have a similar setup but with only the DCA1000 and a iwr6843isk board.

We developed two ROS2 packages in order to use the sensor and board under linux. Maybe you can look into our code and test it out (it was initially developed as a python script so it should be easy to modify it). In case something is unclear, feel free to message me. Here is the link to the DCA1000EVM_CLI_ROS2 package.
Maybe in January I will try to implement our solution in OpenRadar and open a pull request.

Is the ROS2 Package still around? I'm basically trying to replicate the same thing right now, it would be very helpful.

I am trying a similar thing and I am fed up with developting with windows and Mmwavestudio, would you be so kind to share? I have a similar setup but with only the DCA1000 and a iwr6843isk board.

We developed two ROS2 packages in order to use the sensor and board under linux. Maybe you can look into our code and test it out (it was initially developed as a python script so it should be easy to modify it). In case something is unclear, feel free to message me. Here is the link to the DCA1000EVM_CLI_ROS2 package.
Maybe in January I will try to implement our solution in OpenRadar and open a pull request.

Is the ROS2 Package still around? I'm basically trying to replicate the same thing right now, it would be very helpful.

I sadly had to take it down due to my current employer being strict about opensourcing our work, but as descriped in my earlier comment, I am simply launching the CLI from TI as a subprocess in my python code.


Obtaining ground-truth focal length

Hello,
Upon reading your paper, in order to generate the training samples for the PCM, on the fly you perturb the focal length by some delta, then generate the point cloud. It seems that the diverse depth dataset does not have the focal length in the annotations. Is this information not yet released?
Thanks

Hi,
The released DiverseDepth dataset is for DiverseDepth project. Please see the paper "Virtual Normal: Enforcing Geometric Constraints for Accurate and Robust Depth Prediction" and "diversedepth: affine-invariant depth prediction using diverse data" for details. If you want to get more details of PCM module, please see the paper "Learning to recover 3D scene shape from a single image".


Very large data

Hi @jarrodmillman @rossbar
Data for each subject is ~7 GBs. This is the result of me concatenating all 8 runs together. Also, note that when I load in the original data the values in the 4D array are integers. When I convert the 4D array to floats the size of the array jumps to 30 GBs. Does this sound right? To get this all working I'm running the code on an amazon machine with 120 GBs of memory. I want to confirm that you will be able to run our code on a machine with sufficient capabilities as implied earlier in the semester.
Do you have suggestions for how in our analysis we can trim the size of the entire array (maybe averaging values of neighboring voxels and creating a new 4D array of lower spatial resolution) or ways I can compress this object?
Thank you,
Alon

Just out of curiosity, what is the type of the original data? I'm surprised that converting to floats essentially quadruples the size of the array; the only way that makes sense is if the data is originally 16-bit integers and you're converting to 64-bit floats (np.float defaults to 64-bit floats on 64-bit machines I believe; at least on all my machines).
I believe I have access to a server that should be sufficient to run your project.

The original data comes in as 16-bit integers. I think your right that it is converting to 64-bit floats. What do you think is safe to convert to: 16-bit floats or 32-bit floats?

You should be able to use 32-bit floats

OK - thank you


Jenkins collector does not support folders which will significantly reduce the usability of the collector. The collector is a preferred method over the Jenkins plugin for large deployments as the plugin requires modifying every job

The Jenkins collector is unable to traverse within folders so it is unable to see any jobs within a folder. It marks the folder as a job within the Hygieia UI.

Are the jobs not being collected? Or are the folder organization is messed up?

It does not seem as though folders are working, but I'll get more details.

Send me the details when you get a chance.

@camillone Can you please send me more details on this?

I have the similar problem. The Jenkins collector picks up the list of jobs which are at the top level. For instance, if I have got JobA, JobB, FolderA/AnotherJobA and FolderB/AnotherJobB then the Jenkins collector shows JobA, JobB, FolderA and FolderB in the list when configuring the widget.

From what I can see the jenkins collector doesn't support recursive folder search. You can kind of work around this by creating multiple entries in the configuration, BUT we have an issue with this on our setup.
So, you could do this in the properties file
jenkins.servers[0]=http://jenkins.company.com/
jenkins.servers[1]=http://jenkins.company.com/FolderA
jenkins.servers[2]=http://jenkins.company.com/FolderB
You'll then get a list of jobs that are at the root, and in FolderA and Folder B.
A couple of issues with this tho. In our case the jobs are named the same...
jenkins.servers[0]=http://jenkins.company.com
jenkins.servers[0]=http://jenkins.company.com

I am aware that team target has enhanced the collector and will do a PR soon.

@tabladrum any update on this one?

See this PR -> https://github.com/capitalone/Hygieia/pull/1038


Bump to appliance_console 7.2.1 for the ipaclient fix

https://github.com/ManageIQ/manageiq-appliance_console/pull/211

Backported to petrosian in commit 157cc81e9e370b74d39bbd2b06167b53297d4b07.
commit 157cc81e9e370b74d39bbd2b06167b53297d4b07
Author: Jason Frey<EMAIL_ADDRESS>Date:   Thu May 4 12:47:21 2023 -0400

    Merge pull request #22495 from jrafanie/bump_appliance_console_7_2_1

    Bump to appliance_console 7.2.1 for the ipaclient fix

    (cherry picked from commit 9dec0c4de7d0e37ec5d115bc5cc6f300c8875ac2)


file open crash in Reaper Linux

System: Linux Mint 19 cinnamon, latest Reaper.
Error:
xxx vstrack_plugin: effEditGetRect: (0; 0; 820; 1272)
lglw:loc_eventProc: xev ButtonPress
lglw:loc_eventProc: xev ButtonRelease
xxx osdialog_file: 1
(reaper:13841): GLib-GObject-WARNING **: 11:16:34.131: cannot register existing type 'GdkWindow'
(reaper:13841): GLib-GObject-CRITICAL **: 11:16:34.132: g_param_spec_object: assertion 'g_type_is_a (object_type, G_TYPE_OBJECT)' failed
(reaper:13841): GLib-GObject-CRITICAL **: 11:16:34.132: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
xxx osdialog_file: 2
xxx osdialog_file: 3
xxx osdialog_file: 4
xxx osdialog_file: 5
xxx osdialog_file: 6
xxx osdialog_file: 7
(reaper:13841): GLib-GObject-WARNING **: 11:16:34.285: cannot register existing type 'GdkScreen'
(reaper:13841): GLib-CRITICAL **: 11:16:34.285: g_once_init_leave: assertion 'result != 0' failed
(reaper:13841): Gdk-CRITICAL **: 11:16:34.285: IA__gdk_screen_get_default_colormap: assertion 'GDK_IS_SCREEN (screen)' failed
(reaper:13841): Gdk-CRITICAL **: 11:16:34.285: IA__gdk_colormap_get_visual: assertion 'GDK_IS_COLORMAP (colormap)' failed
=======================================================
EDIT:
Note: instantiating modules, connecting wires, turning knobs etc all work.  Only the file dialog seems to be a problem.
My use case is weird. I'm writing the rpp directly.
I would use the open dialog to load a patch once. Save the rpp and then analyze the chunk to figure out how to replace the path.  From that point on I don't need the dialog.
Is the path easy to get to in the decoded chunk?  Do you have an rpp that you could send?
Also, thank you so much for this project! The standalone didn't work for my use case and I was eating my heart out: https://github.com/VCVRack/Rack/issues/924

Can you post your GTK and GLib version? Did you use the released binary or build it yourself? Also, if VCVRack works, did you use a release of that or build it yourself?

Downloaded binaries of both.  The file dialog works in VCVRack.
ldd (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
GTK 3.22.30
no gtk+ 2 or 1 found

Is it possible for you to build it for yourself? You'll probably need to find and download the necessary VST2 headers, which as of recently have been removed from their source (!), and tweak setenv_linux.sh for the directory locations. Assuming you have the dependencies, first run . /setenv_linux.sh (note the dot and space at the beginning) then a make -f makefile.linux vst should work after that. Unfortunately, that's not the easiest build, so perhaps I can look into providing a build for your setup later.
I think that the owner built the release from a VM with XFCE, so I'm assuming that there's a GTK and/or GLib mismatch that would cause this. Even though my machine has parts of XFCE and a mix of GTK2 and GTK3, my own builds show the dialog in GTK2. I have a feeling that a local build for you would fix this (by using GTK3), or perhaps installing libraries that ldd cannot find, like GTK2. For example, here's some of the related lines for my ldd:
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0
libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0

Notice how they're referencing the GTK2 versions of the libraries, even though I have both installed:
local/gtk2 2.24.32-1
local/gtk3 3.24.1+8+g220f77d8c1-1

I tried the GTK2.0 path -- no such luck.
I'm about to embark on the build process.
Would you able to test 'open' on the latest linux Reaper, in case it's Reaper specific?  My build backstory is a black cloud of thunderstruck nights -- maniacal laughter and thrashing corpses.
This is the build I'm using: https://www.landoleet.org/reaper5963+dev1128_linux_x86_64.tar.xz
xxx vstrack_plugin: effEditGetRect: (0; 0; 820; 1272)
lglw:loc_eventProc: xev ButtonPress
lglw:loc_eventProc: xev ButtonRelease
xxx osdialog_file: 1

(reaper:29549): GLib-GObject-WARNING **: 16:59:56.396: cannot register existing type 'GdkWindow'

(reaper:29549): GLib-GObject-CRITICAL **: 16:59:56.396: g_param_spec_object: assertion 'g_type_is_a (object_type, G_TYPE_OBJECT)' failed

(reaper:29549): GLib-GObject-CRITICAL **: 16:59:56.396: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
xxx osdialog_file: 2
xxx osdialog_file: 3
xxx osdialog_file: 4
xxx osdialog_file: 5
xxx osdialog_file: 6
xxx osdialog_file: 7

(reaper:29549): GLib-GObject-WARNING **: 16:59:56.533: cannot register existing type 'GdkScreen'

(reaper:29549): GLib-CRITICAL **: 16:59:56.533: g_once_init_leave: assertion 'result != 0' failed

(reaper:29549): Gdk-CRITICAL **: 16:59:56.533: IA__gdk_screen_get_default_colormap: assertion 'GDK_IS_SCREEN (screen)' failed

(reaper:29549): Gdk-CRITICAL **: 16:59:56.533: IA__gdk_colormap_get_visual: assertion 'GDK_IS_COLORMAP (colormap)' failed

Hm, now I doubt the local build will fix this as I see the same thing on Reaper.
(reaper:15290): GLib-GObject-WARNING **: 20:22:28.808: cannot register existing type 'GdkWindow'
(reaper:15290): GLib-GObject-CRITICAL **: 20:22:28.808: g_param_spec_object: assertion 'g_type_is_a (object_type, G_TYPE_OBJECT)' failed
(reaper:15290): GLib-GObject-CRITICAL **: 20:22:28.808: validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
(reaper:15290): GLib-GObject-WARNING **: 20:22:28.850: cannot register existing type 'GdkScreen'
(reaper:15290): GLib-CRITICAL **: 20:22:28.850: g_once_init_leave: assertion 'result != 0' failed
(reaper:15290): Gdk-CRITICAL **: 20:22:28.850: IA__gdk_screen_get_default_colormap: assertion 'GDK_IS_SCREEN (screen)' failed
(reaper:15290): Gdk-CRITICAL **: 20:22:28.850: IA__gdk_colormap_get_visual: assertion 'GDK_IS_COLORMAP (colormap)' failed

Note that it happens with any GTK dialogs, for example the New button which would prompt about clearing the current patch.
Based on the GUI, I wouldn't think Reaper is using GTK. Using different versions of GTK within the same process would surely cause issues. I checked reaper and its included libraries and didn't see it linked to GTK. Perhaps there's something interesting about its sandboxing that causes this.
Considering this same build works on Bitwig, Ardour, and Renoise, it's looking like a Reaper-specific issue. AFAIK, the GTK dialog portion of this repo is as-is from the original VCV Rack code. I tried the U-he plugins since they do something interesting with the dialogs: they put them into their own executable that the plugin calls in a separate process when necessary. These of course do not crash.

I don't fully understand what you're trying to do there, but I didn't try as it seemed like a workaround to fixing the GTK issue. The VST chunk data is the JSON patch; I don't think it's base64 encoded (Reaper does that).

The default json saved with the project and a fresh rpp looks like its enough to work with, even if all else fails.

The issue here is quite clear to me, as we had to deal with this several times in Linux hosts and system toolkits.
Reaper on Linux uses GDK3 for handling Windows and events.
The file dialog used in VCVRack uses GTK2 (and thus GDK2), which leads to symbol clashes among other nasty things.
We (linux audio devs) keep repeating this message to plugin developers: do not use big system libraries or frameworks in plugins, make them self-contained!
A hacky fix to make this work under Reaper would be to use GTK3 on the file dialog, but then you will break hosts that use GTK2 like Ardour.
The only solution is to stop using GTK (or Qt, FLTK and similar) for plugin UIs.
If you need a file dialog, consider using this project https://github.com/x42/sofd, or perhaps roll your own.

Keep in mind that this project is based on VCV Rack, so it inherits certain design decisions / implementations.
Cameron and I already swapped out GLFW for something more lightweight (and less problematic for use in a plugin library).
I don't think that re-inventing something basic as a file dialog would be a good idea.
The plan was to use Zenity for GTK based dialogs (via popen() (also see here).
It simply hasn't been implemented it, yet. Maybe I'll write a little C wrapper for it next weekend.

done (replaced osdialog_gtk2 with osdialog_zenity)

Greetings!
First, Many thanks to the devs: bsp2, cameronleger, and falkTX (I know falkTX is not a "dev" for this project, but I use many of his KXStudio ports). Thanks you so much for supporting Linux!
I just wanted to report that this fine project works well on Reaper v6.13 on Ubuntu 19.10. I have not tested everything (that will take a very long time), but it loads, plays and saves patches perfectly.
Also, while testing the Wide Stereo Lead patch, I connected the output of the LFO-1 to the FM inputs of both VCO-1s. I then saved and reloaded the modified patch. Using Reaper's parameter assign function, I was able to assign the mod wheel (MIDI input) to the FM-CV inputs of both VCO-1s to produce an intense mod wheel vibrato. I also assigned MIDI pitch bend to both VCO-1's FREQ input to do pitch bend.
I then saved this configuration as a Reaper "FX chain". I successfully reloaded the modified VCV preset and the Reaper pitch bend and mod wheel assignments. So presets can be edited, saved and recalled, and Reaper parameter routings can be configured, saved and recalled. Using Reaper's parameter routing, I should be able to assign any knob, fader or switch whose value I can change in the GUI, to a MIDI CC.
This is first day testing... I downloaded and installed this amazing software 2 or 3 hours ago. So far, it's amazing!
I love the simple install; expand the zip file, and put the folder in the .vst folder. Patches and everything are right there, no digging around in /usr/share where you need sudo privileges...
The sound is amazing! I could spend days and weeks modifying the presets.
Many, many thanks to everyone involved!


Move @dollarshaveclub/node-fetch into this repo

Move @dollarshaveclub/node-fetch into cloudworker. It's only used by cloudworker and doesn't belong in a separate repo IMO.

I also agree with this


Popup bad positioning on 2nd show

When initializing a popup like below then its position is off on 2nd show if a custom .hidden css class is defined.
.hidden {
    display: none !important;
}

$('.activating.element').popup({ on: 'click', lastResort: 'right center', position: 'right center' });

Might be related: https://github.com/Semantic-Org/Semantic-UI/issues/614#issuecomment-40208095
Workaround:
.hidden:not(.popup) {
    display: none !important;
}

Hi, please provide a test case as per our contributing guidelines; you can fork this JSFiddle.

See http://jsfiddle.net/jusjaogp/


Column toggle change event emitter

Summary
I've created a column toggle settings save component, which is almost fully functional:
https://stackblitz.com/edit/clr-column-settings-save
To make it more user friendly, I need an event emitter from clr-dg-column-toggle component to catch the selection change event (when the user changes the checkbox selection).
Use case
With this event emitter I can determine whether a selection change happened and there is dirty data, and then I could enable the save button on update cases only when dirty data presents:
https://stackblitz.com/edit/clr-column-settings-save
Server logic can be added too, we save the settings in json object into the database per user, settings are filtered in the json object per grid, so you can use this for multiple grids (gridId field). Server logic can be implemented in various ways.
Integration
Can this ColumnToggleSettingsComponent  be added into the main @clr/angular package?
This feature can be useful for other users too.

This looks like a duplicate of #2117 to me. It's a known request, but it's not in our short-term priorities at the moment. Please follow that issue for future updates.

@youdz  Yeah, it seems it's a duplicate. And what about the component, have you checked? Don't you need it?

It does seem very specific, which is something we try to avoid with Clarity. Being a small team with limited resources, we cannot implement or even accept already implemented features at will (like other libraries do) because the maintenance cost would be too high for us. It also helps us keep the documentation small and the learning overhead to a minimum.

Sounds reasonable. I'll leave you alone, I know it's release day :)


test: test checkout@v2

Test PR to test checkout v2.

This PR was created to test a solution. Since the fix PR has been merged now so closing this one out.


Issue with root user

I am getting following error when try to use vi for root user:
# vi /etc/network/interfaces
syntastic: error: exception running system('uname'): Vim(let):E484: Cannot open file /tmp/vNHo9Ic/0
Error detected while processing function syntastic#util#system:
line   19:
E121: Undefined variable: g:_SYNTASTIC_DEBUG_CHECKERS
E116: Invalid arguments for function syntastic#log#debug

It's ok with non privilege users.

Any update on this? I am also getting the same exact issue.

Me too. I'm getting the same, from some days ago.

Please report this on https://github.com/vim-syntastic/syntastic

I'm having the same issue. Tested in all my centos 7 servers.
syntastic: error: exception running system('uname'): Vim(let):E484: Can't open file /tmp/v0jsoLf/0
Error detected while processing function syntastic#util#system:
line   19:
E121: Undefined variable: g:_SYNTASTIC_DEBUG_CHECKERS
E116: Invalid arguments for function syntastic#log#debug
Press ENTER or type command to continue

The problem is with syntastic, but vimrc should not ship broken code anyways. This plugin should be removed temporarily until syntastic fix the issue.

If you're using fish as your shell, this is a relevant (documented) issue in the syntastic repo: https://github.com/vim-syntastic/syntastic/issues/2013

@lukasschwab You got me, that's right I use fish as shell. Thank you.
So based on that, my permanent solution is just to add this line into my config file:
~/.vim_runtime/my_configs.vim
let g:syntastic_shell = "/usr/bin/bash"

:+1:

I had this problem earlier. I tried fixing it by updating vim. But somehow it said I had no space left in /var/cache/apt/archives. I even tried downloading ncdu to figure out what was eating up memory, but I didn't have enough space to install ncdu (even after removing some files on Desktop). So then I removed a few conda virtual environments, and this fixed the problem.


Questions

Hey, i have 2 questions about this TDL.

There is way to "manually" implement SEH to work with driverless drivers ? It is possible to do that? If yes, can u provide some good documentations?
It's possible to bypass PsSetCreateProcessNotifyRoutine (needs /INTEGRITYCHECK)

Regards,
TheAifam5

Nothing from this are TDL issues. 1) No 2) PsSetCreateProcessNotifyRoutine does not need integrity check.

so, maybe u know why on TDL PsSetCreateProcessNotifyRoutine returns 0xC0000022?


Correction for raw affiliation IHRIM, UMR 5317 (CERPHI)

Correction needed for raw affiliation IHRIM, UMR 5317 (CERPHI)
raw_affiliation_name: IHRIM, UMR 5317 (CERPHI)
new_rors: ;02wmc6m46
previous_rors:
works_examples: W2562642121
contact: c7e3c10ecfe7c2ca079bc9d8eeebd8c1:f5e58d7b5ffbad7ec7588b558944 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


Compat with more geodes reforged?

Hello!
There is a mod called more geodes, that adds geodes for other ores, mainly diamond,emerald and lapis, and it would be amazing if your mods silk touch was compatible with those "budding" block variants too.
https://modrinth.com/mod/more-geodes-reforged
I'm playing on 1.20.1 with purpurpacks-silk-touch-budding-amethyst-1.3 and more-geodes-reforged-1.2.2
Thanks!

Supporting modded content is not within the scope of the project.


How to get selected rowIds from table to custom buttons?

Summary of problem or feature request

Using datatable select plugins.
How to get the selected rowIds from datatable in DataTable class controller
Code snippet of problem

System details

Operating System MacOS High Serria
PHP Version 7.1
Laravel Version 5.5
Laravel-Datatables Version latest

On controller? Maybe see the example on the library docs. https://datatables.net/examples/server_side/select_rows.html

Sorry, maybe i wasn't clear on my objective. I have created a custom buttons (delete selected) which will delete the selected rows from the datatable
I was wonder how do i get the array of selected rowsId from the datatable to perform my logic in the custom button function in my class UserDataTable extends DataTable
Below are my datatable declaration:

return $this->builder()
->columns($this->getColumns())
->minifiedAjax()
->addAction(['width' => '80px'])
->parameters([
'dom'     => 'Bfrtip',
'order'   => [[0, 'desc']],
'select' => [
'style' => 'multi'
],
'deferRender' => true,
'rowId' => 'id',
'buttons' => [
'selectAll',
'selectNone',
'create',
'deleteSelected',
'export',
'print',
'reload',
],
]);

    public function deleteSelected()     {       // TODO: Delete Logic HERE      // Get selected rowId here????     }

I think this question is important @yajra, I meant the package provides adding checkbox using addCheckbox, but what's the point of it if it cannot be processed in custom action inside DataTable.
If there is a way to get and pass from the client side as query string to the custom action URL it would be helpful, should this package do that automatically when addCheckbox is used?

You would have to implement manually using the example from the official datatables.net website. addCheckbox is just a helper to lessen the configuration needed just to add a standard checkbox column of dataTable.

I have been able to implement it. I just curious if this feature -- collecting and sending selected row id to custom action-- would make to the package, I don't know if it's good or bad idea.
Anyway, thank you.


Angular breaks when trying to inject deviceDetector

I added "ng.deviceDetector" to the controller params...
.controller('viewSupplyASNController', ['$scope', '$http', 'BBGlobals', 'dmSupplyAsn', '$location', '$stateParams', 'ng.deviceDetector', '$state', function...
and it caused all of my binding to break. The error in the console says...
angular.js:13236 Error: [$injector:unpr] http://errors.angularjs.org/1.5.0/$injector/unpr?p0=ng.deviceDetectorProvider%20%3C-%20ng.deviceDetector%20%3C-%20viewSupplyASNController     at http://localhost:1024/bower_components/angular/angular.min.js:6:416     at http://localhost:1024/bower_components/angular/angular.min.js:43:7     at Object.d [as get] (http://localhost:1024/bower_components/angular/angular.min.js:40:270)     at http://localhost:1024/bower_components/angular/angular.min.js:43:69     at d (http://localhost:1024/bower_components/angular/angular.min.js:40:270)     at e (http://localhost:1024/bower_components/angular/angular.min.js:41:1)     at Object.instantiate (http://localhost:1024/bower_components/angular/angular.min.js:41:364)     at http://localhost:1024/bower_components/angular/angular.min.js:87:42     at http://localhost:1024/bower_components/angular-ui-router/release/angular-ui-router.min.js:7:23742     at ka (http://localhost:1024/bower_components/angular/angular.min.js:79:16) <div ui-view="" class="ng-scope">
Do you possibly know what is happening?

Sorry for the delay.
Could you create a CodePen or anyother way for me to reproduce the problem?

Hi,
We went another route. Sorry to waste your time. Thank you for the response though!


Prevent crash when getting dynamic properties

Since args is a string, the Popen constructor interprets "/usr/bin/python myscript.py" as a path to an executable instead of "/usr/bin/python" with argument "myscript.py".
Adding shell=True makes this behave as expected.
Fix #584

The shell variable be configurable by the user rather than blanket set to True. There's some existing config available for controlling whether or not things are invoked with shell. Checkout the config here

That may be true but the preceding line assumes that target is a string, so it must be executed with shell. Perhaps target should be an array instead?
https://github.com/chriskiehl/Gooey/blob/56a2b8526fadedf2ad7aa8acc543c74f256a7c83/gooey/gui/seeder.py#L14

Additionally, you'll need to update this to target the release branch

There are multiple release branches, and it’s not clear which is the “current release branch” per  https://github.com/chriskiehl/Gooey/blob/master/CONTRIBUTING.md#pull-request-process. Maybe the repo default branch should be changed to whichever you want PRs against https://docs.github.com/en/github/administering-a-repository/setting-the-default-branch

Thanks for pointing out the confusion with the release branches.
I've updated the contributing guidelines to explicitly point at the target branch. Additionally, I've added a PR Template, which'll hopefully clear up any remaining confusion with people opening PRs.
It'd be nice if Github had a way of specifying branch semantics beyond just default. The problem with setting the default branch to an active dev one is that people cloning the project would be grabbing a potentially unstable code base. I prefer master to be a stable mirror of the latest release.
For the shell=[configurable] thing, I don't recall at the top of my head the specific issues which led to the main processor being configurable. Some quick testing on win/osx shows this to be ok, though. How Popen works falls out of my head the second I stop staring at it.
Can you target this to 1.0.5 so we can merge?
Thanks!

Thanks! I usually expect master to be semi-stable. Anyone who expects a stable release is probably going to be installing off of PyPI instead of via git. I would expect a branch with "release" in the name to be more stable than master, rather than less.

For the shell=[configurable] thing, I don't recall at the top of my head the specific issues which led to the main processor being configurable. Some quick testing on win/osx shows this to be ok, though. How Popen works falls out of my head the second I stop staring at it.

I suspect using shell=False in gooey is broken in other ways, though without the reason for its existence, I'm not sure why it exists.


added image plugin and my details json

Also formatted the code, that's why so many additions are showing.

LGTM
Thanks :tada: