Question for Explaination for this Feature

Dear all,
I just wonder about two things. First of all, if I set the -EnableTranscriptionProfanityMasking to $true on Global it does not work by default as I check that the users do not have Global assigned by default. There is another CSOnlineVoicemailPolicy that is tagged "default" which is not editable. Now in an environment with >100k users how do I can enable TranscriptionProfanityMasking for everyone? Or specifically asked which policy works by default and how to adjust it?
Thanks in advance.
BR Martin

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

ID: 718d3732-5ffd-0420-da3a-d4abd979d644
Version Independent ID: 0050302b-0849-7f3c-32a0-5f751ac1d721
Content: Get-CsOnlineVoicemailPolicy (skype)
Content Source: skype/skype-ps/skype/Get-CsOnlineVoicemailPolicy.md
Service: skypeforbusiness-powershell
GitHub Login: @tomkau
Microsoft Alias: tomkau

@officedocsbot assign @yogkumgit

Hello @lordmafi Martin, how are you? :)
Did some tests in my lab and this is what I got:
Users by default show no value for OnlineVoicemailPolicy:

DisplayName  OnlineVoicemailPolicy
-----------  ---------------------
Debra Berger

But, is this the Global or the Default predefined Voice Mail policies?
I could assign this demo user the Default one:

DisplayName  OnlineVoicemailPolicy
-----------  ---------------------
Debra Berger Default

So that lead me to think that all users by default receive the global one, If I remove the assignment:
Grant-CsOnlineVoicemailPolicy -Identity<EMAIL_ADDRESS>-PolicyName $null

DisplayName  OnlineVoicemailPolicy
-----------  ---------------------
Debra Berger

So based on my tests users receive the Global policy by default.
It is true that the "Tag:Default" voice mail policy isn't editable.
It is also true that the "Global" has EnableTranscriptionProfanityMasking as false but it is editable.
did you observe something different?
Thanks

@lordmafi Martin, have you seen my comment? Otherwise we will need to close this one, thanks!

@get-itips Thank you very much for the contribution and digging deep into it.  @lordmafi We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if you see an improvement is required in the specific area of this documentation. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

I am just wondering does the Profanity Masking only works with Exchange Online? We have Hybrid in place and activated it for on-prem mailboxes which is not working after waiting even a week for replication/activation.

It would be nice to have more clearity on this if there are any requirements to the mailbox.

The issue stays also how to assign it in huge enviroments as a default other than going through a script everytime someone onboards

I am just wondering does the Profanity Masking only works with Exchange Online? We have Hybrid in place and activated it for on-prem mailboxes which is not working after waiting even a week for replication/activation.

Hello @lordmafi Martin, how are you?
According to this, the transcription is also applied on an hybrid scenario:

Unanswered calls are handled as follows:

For users homed in Skype for Business 2019 on premises, unanswered calls are sent by the on-premises Skype for Business Server to the online Cloud Voicemail service.
The service processes the voicemail, including transcription.
The service then deposits the voicemail in the Exchange mailbox of the user, whether the mailbox is on-premises or online.
Users can access their voicemail from either their Skype for Business or Outlook client.

However, Is this your scenario?
Also, I found more information about the default state of profanity masking here https://docs.microsoft.com/es-es/microsoftteams/set-up-phone-system-voicemail#setting-voicemail-policies-in-your-organization
Hope this information helps you.

Hi @get-itips Andres,
thanks for quick response, that was what I thought also. I did assign two user-based policies (Tag: TranscriptionProfanityMaskingEnabled) to me and another user and we did some testing, even after days it was still using bad words in the transcription. So I was wondering why it does not work if applied, only explanation I could think of, is that it is not working with on-prem mailboxes. I will set the global setting and test again.

Hi @get-itips Andres,
thanks for quick response, that was what I thought also. I did assign two user-based policies (Tag: TranscriptionProfanityMaskingEnabled) to me and another user and we did some testing, even after days it was still using bad words in the transcription. So I was wondering why it does not work if applied, only explanation I could think of, is that it is not working with on-prem mailboxes. I will set the global setting and test again.

Ok looking forward to the results of that test, and also what are the software versions you have on-premises for sfb and Exchange ?

Exchange 2016 latest CU and sfb is online only. The user-based policies are not working I think we will create a ticket for it. Just will test the global setting.

Exchange 2016 latest CU and sfb is online only. The user-based policies are not working I think we will create a ticket for it. Just will test the global setting.

Martin, yes, I think it will be the best in this case, I will be very happy if you can share the outcome or resolution with us. I'll update the documentation with that valuable information if it is needed.
Thanks for taking out some time to open the issue.

@lordmafi Thanks for your conversation, please share your findings that can help improving this documentation. We are waiting to resolve this issues.

@get-itips  Thank you very much for the contribution and digging deep into it.  @lordmafi We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if you see an improvement is required in the specific area of this documentation. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


rust-analyzer: fix root pattern for multi-crate projects

Closes  #310
This will prefer git directory > rust-project.json > cargo.toml

@csmoe @geigerzaehler I believe this is the correct thing to do. Can you forsee any scenarios where it wouldn't be?

@csmoe @geigerzaehler I believe this is the correct thing to do. Can you forsee any scenarios where it wouldn't be?

I'm okay with this 👍

I'm okay with this 👍

I'm like 99% sure this is what people really want haha, so hopefully it didn't/doesn't break anything for anyone.

I'm like 99% sure this is what people really want haha, so hopefully it didn't/doesn't break anything for anyone.

I'm like 99% sure this is what people really want haha, so hopefully it didn't/doesn't break anything for anyone.

I could easily think of a scenario where a company is using a polyglot monorepo where this wouldn't make sense. Either because the sub-projects aren't related, or because there's nothing useful in the root of the repo (e.g. just folders and a readme).

I'm like 99% sure this is what people really want haha, so hopefully it didn't/doesn't break anything for anyone.

I could easily think of a scenario where a company is using a polyglot monorepo where this wouldn't make sense. Either because the sub-projects aren't related, or because there's nothing useful in the root of the repo (e.g. just folders and a readme).

I could easily think of a scenario where a company is using a polyglot monorepo where this wouldn't make sense. Either because the sub-projects aren't related, or because there's nothing useful in the root of the repo (e.g. just folders and a readme).

This is the main counter example. Unfortunately, I don't think there is an automated way that will support both options, and this covers the more common scenario of having multiple crate submodules. I added a note in the wiki on project local configuration, so you can just hardcode your root_dir for a complex polyglot project for each language server (as you'd probably have to).
If enough people complain, I can switch it back, but it's also easy enough for them to override.

I could easily think of a scenario where a company is using a polyglot monorepo where this wouldn't make sense. Either because the sub-projects aren't related, or because there's nothing useful in the root of the repo (e.g. just folders and a readme).

This is the main counter example. Unfortunately, I don't think there is an automated way that will support both options, and this covers the more common scenario of having multiple crate submodules. I added a note in the wiki on project local configuration, so you can just hardcode your root_dir for a complex polyglot project for each language server (as you'd probably have to).
If enough people complain, I can switch it back, but it's also easy enough for them to override.

I know nothing about lua, can we check whether the Cargo.toml contains a workspace section?
[workspace]
members= [ ... ]

I know nothing about lua, can we check whether the Cargo.toml contains a workspace section?
[workspace]
members= [ ... ]

I wonder if we can use the cargo command itself to figure out the workspace root? Supposedly there's a workspace_root field in the cargo metadata output (see https://github.com/rust-lang/cargo/pull/4938).
$ cargo metadata --format-version 1 | jq -r .workspace_root

I wonder if we can use the cargo command itself to figure out the workspace root? Supposedly there's a workspace_root field in the cargo metadata output (see https://github.com/rust-lang/cargo/pull/4938).
$ cargo metadata --format-version 1 | jq -r .workspace_root

Will workspace_root always point to the correct top level workspace for multi-crate projects? We could parse the file in lua pretty easily

Will workspace_root always point to the correct top level workspace for multi-crate projects? We could parse the file in lua pretty easily

Seems like it does. I just tested on the ripgrep repo which contains a handful of sub-crates.
$ find . -name Cargo.toml
./Cargo.toml
./crates/searcher/Cargo.toml
./crates/globset/Cargo.toml
./crates/ignore/Cargo.toml
./crates/printer/Cargo.toml
./crates/cli/Cargo.toml
./crates/regex/Cargo.toml
./crates/matcher/Cargo.toml
./crates/grep/Cargo.toml
./crates/pcre2/Cargo.toml
$ cd crates/grep
$ cargo metadata --format-version 1 | jq -r .workspace_root
  Downloaded encoding_rs_io v0.1.7
  Downloaded pcre2 v0.2.3
  Downloaded pcre2-sys v0.2.5
  Downloaded crossbeam-channel v0.5.0
  Downloaded bytecount v0.6.0
  Downloaded 5 crates (2.3 MB) in 1.08s (largest was `pcre2-sys` at 2.2 MB)
  Downloaded jemalloc-sys v0.3.2
  Downloaded jemallocator v0.3.2
  Downloaded 2 crates (1.4 MB) in 0.43s (largest was `jemalloc-sys` at 1.3 MB)
/Users/peter/Workspace/tmp/ripgrep

Seems like it does. I just tested on the ripgrep repo which contains a handful of sub-crates.
$ find . -name Cargo.toml
./Cargo.toml
./crates/searcher/Cargo.toml
./crates/globset/Cargo.toml
./crates/ignore/Cargo.toml
./crates/printer/Cargo.toml
./crates/cli/Cargo.toml
./crates/regex/Cargo.toml
./crates/matcher/Cargo.toml
./crates/grep/Cargo.toml
./crates/pcre2/Cargo.toml
$ cd crates/grep
$ cargo metadata --format-version 1 | jq -r .workspace_root
  Downloaded encoding_rs_io v0.1.7
  Downloaded pcre2 v0.2.3
  Downloaded pcre2-sys v0.2.5
  Downloaded crossbeam-channel v0.5.0
  Downloaded bytecount v0.6.0
  Downloaded 5 crates (2.3 MB) in 1.08s (largest was `pcre2-sys` at 2.2 MB)
  Downloaded jemalloc-sys v0.3.2
  Downloaded jemallocator v0.3.2
  Downloaded 2 crates (1.4 MB) in 0.43s (largest was `jemalloc-sys` at 1.3 MB)
/Users/peter/Workspace/tmp/ripgrep

Will workspace_root always point to the correct top level workspace for multi-crate projects?
yes, multiple workspace roots in the same workspace is not allowed in cargo, in other words, there will be only one workspace_root in a project.

Will workspace_root always point to the correct top level workspace for multi-crate projects?
yes, multiple workspace roots in the same workspace is not allowed in cargo, in other words, there will be only one workspace_root in a project.

This makes me wonder though. If we don't send a root dir, will rust-analyzer figure this out? Seems like it would be better fit to do this.

This makes me wonder though. If we don't send a root dir, will rust-analyzer figure this out? Seems like it would be better fit to do this.

@lithammer ra seems already do that. cc https://github.com/rust-analyzer/rust-analyzer/blob/4ddf075673c4a8e3b5b0be5a2f085cdefe3993ef/crates/project_model/src/workspace.rs#L1

@lithammer ra seems already do that. cc https://github.com/rust-analyzer/rust-analyzer/blob/4ddf075673c4a8e3b5b0be5a2f085cdefe3993ef/crates/project_model/src/workspace.rs#L1

Given we can performantly parse a json, we should be able to read the metadata from cargo. We rely on knowing the root directory internally for other things (keeping track of root_dir), so I think it's best we compute it ourselves.
PR incoming.

Given we can performantly parse a json, we should be able to read the metadata from cargo. We rely on knowing the root directory internally for other things (keeping track of root_dir), so I think it's best we compute it ourselves.
PR incoming.


[FEATURE] Any plans to add a MultiBlocPresentationListener?

Something similar to MultiBlocListener to avoid nesting in case of multiple cubit/bloc:
MultiBlocPresentationListener(
 listeners: [
     BlocPresentationListener<BlocA, BlocAEvent>(
       listener: (context, event) {},
     ),
     BlocPresentationListener<BlocB, BlocBEvent>(
       listener: (context, event) {},
     ),
     BlocPresentationListener<BlocC, BlocCEvent>(
       listener: (context, event) {},
     ),
   ],
   child: ChildA(),
 )

Sorry for the very late reply:
BlocPresentationListener implements the nested interfaces. So have a multi listener version it is enough that you use the Nested widget from package:nested:
Nested(
  children: [
    BlocPresentationListener<BlocA, BlocAEvent>(
      listener: (context, event) {},
    ),
    BlocPresentationListener<BlocB, BlocBEvent>(
      listener: (context, event) {},
    ),
    BlocPresentationListener<BlocC, BlocCEvent>(
      listener: (context, event) {},
    ),
  ],
  child: ChildA(),
)

In fact, this is exactly what package:flutter_bloc does. Except it provides a new type for this: https://github.com/felangel/bloc/blob/ac6ac74c306ea00ae1e263a714de8768c9662304/packages/flutter_bloc/lib/src/multi_bloc_listener.dart#L51 (it extends MultiProvider, but if you check what MultiProvider is, you will find it is a wrapper for Nested). IMO this is just a duplication of the API for no reason: you can use Nested for all nested-compliant classes. Thus please use Nested, I am not keen on adding MultiBlocPresentationListener as it does nothing as state above.


[WIP] Use USS (unique set size) instead of PSS for all the things

DO NOT MERGE
Builds on top of https://github.com/ManageIQ/manageiq/pull/16569

Change worker validation to check USS not PSS
Show USS instead of PSS in rake evm:status
Also log the server/worker unique set size (USS)

The first bullet point should alleviate the false positives where a large server process was causing new forked workers to exceed PSS memory thresholds very quickly.  If the server process grows over time, that's a separate problem.  We shouldn't flag and kill workers that inherited a large shared memory, only ones that grow beyond the thresholds on their own.

@miq-bot add_label gaprindashvili/yes
@miq-bot add_label performance
@miq-bot add_label core/workers

@gtanzillo @Fryguy this is now ready for review with the prior PR merged cc @dmetzger57 @NickLaMuro

Good point, let me put a BZ link @carbonin

Gaprindashvili backport details:
$ git log -1
commit 0c79e86b72da95bde62b998f274d3080080f0f58
Author: Nick Carboni<EMAIL_ADDRESS>Date:   Fri Dec 15 17:20:56 2017 -0500

    Merge pull request #16570 from jrafanie/USS_all_the_things

    Use USS (unique set size) instead of PSS for all the things
    (cherry picked from commit eee05705f47ca91d3785dc4caed3fd7188f5817c)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1527093


Update browser version.

Should run any signed URLs given the proper format.
For example:
track type=bam db=hg38 name=exampleCRAM bigDataUrl=http://s3.amazonaws.com/1000genomes/data/NA21144/alignment/NA21144.alt_bwamem_GRCh38DH.20150718.GIH.low_coverage.cram bigDataIndex=http://s3.amazonaws.com/1000genomes/data/NA21144/alignment/NA21144.alt_bwamem_GRCh38DH.20150718.GIH.low_coverage.cram.crai

Superseded by #30 .


cmd/cue: regression: field X not allowed when definition used as list type

What version of CUE are you using (cue version)?

$ cue version
cue version +4ecec98 linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
I'm unclear whether this is the same underlying cause as https://github.com/cuelang/cue/issues/471
package x

#Prestep: {
	Args: *null | _
}

#PrestepNewUser: #Prestep & {
	Args: #NewUser
}

#NewUser: {
	Repos: [...#Repo]
}

#Repo: {
	Var:     string
	Pattern: *"*" | string
}

x: [...#Repo]
x: [{
	Var: "REPO1"
}]

y: #Repo & {
	Var: "REPO1"
}

z: #PrestepNewUser & {
	Args: {
		Repos: [ {
			Var: "REPO1"
		}]
	}
}

Run:
cue def

What did you expect to see?
What I see with v0.2.2.:
package x

x: [#Repo & {
        Var: "REPO1"
}]
y: #Repo & {
        Var: "REPO1"
}
#Prestep: {
        Args: *null | _
}
#PrestepNewUser: #Prestep & {
        Args: #NewUser
}
#NewUser: {
        Repos: [...#Repo]
}
#Repo: {
        Var:     string
        Pattern: *"*" | string
}
z: #PrestepNewUser & {
        Args: Repos: [{
                Var: "REPO1"
        }]
}

What did you see instead?
z.Args.Repos.0: field `Pattern` not allowed:
    ./x.cue:12:2
    ./x.cue:15:8
    ./x.cue:31:3
    ./x.cue:31:12

Notice that if z is commented out, what remains work:
package x

#Prestep: {
        Args: *null | _
}
#PrestepNewUser: {
        #Prestep
        Args: #NewUser
}
#NewUser: {
        Repos: [...#Repo]
}
#Repo: {
        Var:     string
        Pattern: *"*" | string
}
x: [...#Repo] & [{
        Var: "REPO1"
}]
y: {
        #Repo
        Var: "REPO1"
}

This issue has been migrated to https://github.com/cue-lang/cue/issues/491.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Replace '.client' with '.socket' as the former was deprecated in 2.2.0.

Actually, it's not only deprecated, checking it with .hasOwnProperty('client') is broken in 2.2.0, but that's going to be fixed in 2.2.1.
See https://github.com/nodejs/io.js/pull/1572 https://github.com/nodejs/io.js/issues/1850 nodejs/io.js#1852/files

Travis errors exactly because it has version 2.2.0 that runs npm install that in turn uses request that is atm not compatible with 2.2.0.

that in turn uses request that is atm not compatible with 2.2.0

This is backwards – it's io.js that has introduced a breaking change in a minor version and is now incompatible with request, npm, and any other package that uses request's strictSSL checking.
This patch shouldn't be accepted until and unless it adds support for .client as well as .socket, because it's going to go from a situation where request (and npm) are broken for io.js 2.2.0 to a situation where request (and npm) are broken for io.js and Node.js everywhere else. While it's at it, somebody should figure out if using .hasOwnProperty() is absolutely necessary for this to work and replace it with a simple property presence test otherwise – .hasOwnProperty() seems unnecessarily stringent and is part of what made this bug so severe and unpredictable in the first place.

if using .hasOwnProperty() is absolutely necessary for this to work

Exactly what I had in my mind too.

Yep both properties should be supported, and that should be implemented by simply converting the property to the one or the other before it's been used for the first time, in any of the contexts where it's used.

@othiym23 .socket is there from nodejs 0.1.90.

This is backwards – it's io.js that has introduced a breaking change in a minor version and is now incompatible with request, npm, and any other package that uses request's strictSSL checking.

That is indeed a bug and will be fixed in 2.2.1, as I already mentioned. But it would stil emit a deprecation warning.

@ChALkeR
res.client = res.client || res.socket

@simov Why? Just why? .client and .socket are there from nodejs version 0.1.90 and they were always the same object.

To summarize my discussion with @ChALkeR on IRC: my initial comment about just swapping the property names being insufficient was in error: since client is an alias for connection, the suggested change is fine and will fix request with<EMAIL_ADDRESS>It shouldn't be necessary, though, because there's no compelling reason to have removed this property from the object in the first place (and any further discussion along those lines should probably be had over in nodejs/io.js anyway, as this point isn't really related to request). As such I'm +0 on this PR.

Thanks for pointing that out @othiym23 I was wondering if I'm missing out something, while I was catching up with the issue.

The deprecation was completely reverted in 2.2.1. When I was filing this PR, I assumed that the deprecation would be fixed instead (as https://github.com/nodejs/io.js/pull/1852 was doing at that moment).
With this, there is actual reason to merge this, except for using a documented property instead of a non-documented one. If you want to merge this, I could change the commit message. If not, just close it.

doh I just saw that request is a bundled dependency in npm .. anyway 2.57 is out

Thanks.


checking file format of input files

Hi Brad,
Just a quick question. I noticed that when we start a new run, the compressed fastq files we use as input are decompressed and then recompressed in bgzip format. This takes about 20 min per file.
However, the input files we use are already in bgzip format. Do you suppose it would be possible to check the compression format before recompressing the files? This would save a lot of time when a lot of samples need to be processed.
I think this is something a lot of users will benefit from, since bcl2fastq by illumina outputs bgzf by default.
Thanks
M

Bcbio should already do that; at least there is logic that is supposed to check the format.

Right, just went through the source code quickly. Turns out re-bgzipping everything is default because of some issue with grabix here.
I'll see if I can re-evaluate this approach and perhaps we can save some time.

Seems this issue was already metioned in arq5x/grabix#17, but is still without a fix. I suppose we'll have to wait this one out then. Closing!
M

Matthias;
Thanks for bumping this. I had been working on this on the side and have a reproducible test case so finalized that and added it to the grabix issue you identified. It would be great to have this fixed as we do potentially waste a lot of time here since we don't have a way to reliably detect what is correctly bgzipped so need to re-prep everything. I'll re-open this to track progress, thanks again for pushing the issue.

The latest development version of bcbio now re-instates this checking to coincide with a fixed grabix tool that handles Illumina bgzip inputs. Please let us know if you run into any issues at all.


[Systemctl service won't start]

Hello Benn,
When trying to start a custome service, the service won't start :

My service looks like this:

But the bash command is working on my terminal.
This behavior is happening for all my customs services.
This is my customize script:
sdm --customize \ --extend --xmb 512 \ --plugin network:"netman=dhcpcd|wifissid=Livebox-49F7|wifipassword=********|wificountry=FR" \ --plugin copyfile:"filelist=/home/camanalytics/camanalytics/LampCam/images/base/files|mkdirif=yes" \ --plugin user:"adduser=pi" \ --plugin user:"setpassword=pi|password=pi" \ --plugin runatboot:"script=/home/camanalytics/camanalytics/LampCam/images/base/ref_files_v2/runatboot.sh|output=/home/pi/firsboot.log" \ --plugin raspiconfig:"spi=1" \ --plugin apps:"apps=@myapps|name=myapps" \ 2023-05-03-raspios-bullseye-arm64-lite_base.img
I'm running v11.4
Am I'm missing something with the system plugin ?
Thank you

Found the solution, by stopping userconfig.service
sudo systemctl stop userconfig.service
The service was stopping all other services that wanted to use multi-user.target

Try NOT stopping/disabling the userconfig service, but instead use --plugin disables:piwiz. This will disable the userconfig service and a few other things that you don't need.
Also, a couple of other things:

It doesn't hurt anything, but RasPiOS comes with the pi user already in /etc/passwd (but with no password set), so you don't need to adduser=pi. It doesn't hurt, of course, to leave it there
In your camanalytics.service file, since you have specified User=root you don't need the sudo on the ExecStart

Closing as resolved.


Service stops on friend support select screen when custom supports are preferred.

I have been running FGA on my Bluestacks for a week or three now without issues. However, I recently downloaded the latest release (I updated from 1.15.0) and ran into a bug. Whenever I have a skill setup with one or more custom preferred servants or CEs set, the service will stop itself on the support select screen. Everything else works fine, even the custom image maker, or the support select screen when my preferred servant or CE is one of the built-in ones (as demonstrated in the video below). All of the fine tune settings are at their defaults (I even set the swipes and updates to their default values just in case).
If I try to enable the service again after the second crash, it tells me to enable accessibility (also demonstrated). Turning it off and on again fixes that.
I made a video to demonstrate the bug: https://streamable.com/habsqe
The custom support image was a new one I generated specifically for the test.
(After having typed this up I tried a full reinstall of the app, just in case. Didn't help)
Edited to change 'Friend select' to 'support select'.

Do a few things, please:

Install https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Follow this guide https://stackoverflow.com/a/55804751/5971497
After adb connect, run adb logcat *:E > C:\logcat.log
Look at the log entries around the time the app crashes and see if you can find anything about an exception being thrown

The best I can find is an error:

07-27 02:03:51.788  4355  4435 E cv::error(): OpenCV(4.4.0) Error: Unspecified error (> Invalid number of channels in input image:
07-27 02:03:51.788  4355  4435 E cv::error(): >     'VScn::contains(scn)'
07-27 02:03:51.788  4355  4435 E cv::error(): > where
07-27 02:03:51.788  4355  4435 E cv::error(): >     'scn' is 1
07-27 02:03:51.788  4355  4435 E cv::error(): ) in cv::impl::(anonymous namespace)::CvtHelper<cv::impl::(anonymous namespace)::Set<3, 4, -1>, cv::impl::(anonymous namespace)::Set<1, -1, -1>, cv::impl::(anonymous namespace)::Set<0, 2, 5>, cv::impl::(anonymous namespace)::NONE>::CvtHelper(cv::InputArray, cv::OutputArray, int) [VScn = cv::impl::(anonymous namespace)::Set<3, 4, -1>, VDcn = cv::impl::(anonymous namespace)::Set<1, -1, -1>, VDepth = cv::impl::(anonymous namespace)::Set<0, 2, 5>, sizePolicy = cv::impl::(anonymous namespace)::NONE], file /build/master_pack-android/opencv/modules/imgproc/src/color.simd_helpers.hpp, line 92

Followed by this exception

No pending exception expected: java.lang.ClassNotFoundException: Didn't find class "org.opencv.core.CvException" on path: DexPathList[[zip file "/data/app/com.mathewsachin.fategrandautomata-2/base.apk"],nativeLibraryDirectories=[/data/app/com.mathewsachin.fategrandautomata-2/lib/arm, /data/app/com.mathewsachin.fategrandautomata-2/base.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib, /data/downloads, /data/priv-downloads]]

The same exception is thrown again later just before it seems the whole process gets terminated.
I'll include the log itself as well, since I'm not sure what exactly I'm looking for.
logcat.log

@MathewSachin is this maybe related to the cvtColor method here? https://github.com/MathewSachin/Fate-Grand-Automata/commit/a704a511bab68b74eab08258ed4632fc6ba5b621#diff-9d6bcbd675a451c34373f6eb042c8f98R34
My guess is that matching greyscale templates doesn't work anymore.

I understood the problem from the logs. Just saw this in the middle of the night. I'll push a fix when I wake up tomorrow.
The problem should have appeared with the Story Skip fix where I kind of assumed that the loaded image will be RGBA, while images made by support image maker are gray-scale. And since I didn't use custom support images this event, I didn't notice this.

Lol, that timing.

Yeah. If you're up, can you push a fix. Just have to add an if around that line checking that number of channels is not 1.

Lying in bed trying to fall asleep

I'll wake up in 4-5 hrs and push the fix then. Lol

The thing about CvException missing in the apk seems suspicious too.

Seems like this is needed for the exception: https://developer.android.com/studio/build/multidex#keep

Yeah, I knew that a proguard keep rule would solve the CVException missing problem, but was so sleepy that didn't feel like typing it.

I've released a fix. Try v0.17.0.


there content can be improved for winter camp 1.0

in winter camp 1.0 , the content of your's can be crisp and short reflecting same meaning and also the hovering of the last section of sending and contacting is also not there i can do that . Please assign me this issue

in winter camp 1.0 , the content of your's can be crisp and short reflecting same meaning and also the hovering of the last section of sending and contacting is also not there i can do that . Please assign me this issue


Issue/fix 6691

Description
Fix bug introduced in https://github.com/inmanta/inmanta-core/pull/6808
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

I'll retrigger the container builds once this is merged

Processing this pull request

Merged into branches master in 024a7b204d5ef7a7aba72bd2931c35586d45bf18


Support for operation windows_file.template?

Is your feature request related to a problem? Please describe
Perusing the code it appears the windows_file module does not implement the template function, which might be the most immediately useful part of pyinfra for me right off the bat. Am I mistaken and is there a way to use this feature since seemingly the windows_file.put operation just needs to be invoked instead of the file.put at the end of the templating logic?
Describe the solution you'd like
Support template in windows_file operations

YES this is 100% needed!


Update airmail-beta to 3.2.6,426,296

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Oops, already a pull request for this cask.


Not receiving ENS bid refund?

Hello, I have recently revealed some bids however my refund is not showing up in my wallet. Can someone please help me understand how I can verify if everything is working correctly? Where would I see the transaction of the refund in etherscan?
For example, last night I bid 1.01 ETH on Lamborghini using public address 0x1AFf1E0f1D5F76f92145a278D8C31AF9aDe783dd and I lost the bid because someone else bid much more. I revealed my bid in time (tx hash 0xe49ebce337dd097f1e449483344693710f0eebd3d0967a5af7b078b1df9f926f) however I am not seeing the refund in my wallet. I have waited many hours so I don't think its because it hasn't confirmed yet.
I now realize this may have happened many times and I am afraid I may have lost more ETH than just this one transaction. Can anyone help explain the situation?
Thanks so much.

The transaction you linked is for startAuctionsAndBid, not unsealBid.
Once you have the actual reveal tx, go to etherscan and check that transaction's "Internal Transactions" and "Event Logs" tabs.
You're probably confused due to the same reason I outlined in a comment to another issue.

Suggest closing as invalid.


feat: Make instrumentator work with just Starlette

What does this do?
This PR removes FastAPI and uses Starlette instead (which FastAPI extends).
Why do we need it?
This means that non-FastAPI projects don't have to install all it's dependencies.
Who is this for?
Non-FastAPI users
Linked issues
Fixes #280
Reviewer notes
--

Hi, thanks for proposing and implementing this
Note that it is not possible to remove any trace of FastAPI from the instrumentator, as the expose() method relies on FastAPI-specific parameters. I could remove it, but I would prefer to keep it backwards compatible.
Nevertheless I managed to remove the dependency on the fastapi package by dynamically checking if the app is Starlette or FastAPI instance and only importing fastapi, if it is a FastAPI app. I added the changes to your PR.
It should be backwards compatible

Nice, awesome work @trallnag!


PP-5984 Fix validation parity on user entered reference

Current validation on payment link reference doesn't make sense, there
is both client and server side validation (with useful error messages)
for some validation -- there appears to be no client side validation for
length; the max-length HTML attribute is used which won't allow the
user to enter something too long but will also not give any meaningful
feedback (instead just truncating whatever is entered).

Remove max length assertion - allow the server side
validation to provide the user with a meaningful message
Reduce the max length to 50, the Products database stores this in
reference_number which is currently restricted to VARCHAR(50)
https://github.com/alphagov/pay-products/blob/master/src/main/resources/migrations/00029_alter_column_reference_number_length_payments.sql#L4

Note Connector allows references of up to 250 characters VARCHAR(250)
https://github.com/alphagov/pay-connector/blob/master/src/main/resources/migrations.xml#L68,
there doesn't seem to be a reason Connector should support this and
Products shouldn't. These database columns should and related
validations should be brought into parity with each other.

TL;DR client side validation for length doesn't exist, remove this. Products database
is currently configured to VARCHAR(50), initially limit reference to 50 characters.

@alexbishop1 thanks, agreed! We'll need both this change and the db migration to get the validation user experience right. Addressed comments https://github.com/alphagov/pay-products-ui/pull/699/commits/1692021a1558cd269811e984af18a26c8311a3a9


WIP: Fit models with observer effects

What's our status on this at the moment @davharris?

@ethanwhite Should be just about ready to go as soon as I figure out why HiperGator is complaining about memory usage...

Figured it out.  Was trying to store two gazillion MCMC samples on each core instead of two thousand 😵

That would do it. When you've got the final tweaks working and in you can pull the WIP and ping me and I'll give it a read through and get it in.

Looks like it's finally working.  This branch is really messy, though (38 commits, 13 changed files).
So I'm going to split the PR into two or three pieces: one for #61 (observer effects), one for #88, and possibly a third one with the remaining models.
Should be ready for review before our meeting on Monday.  Have a good weekend!

Superseded by #92 and #93


getContext("2d") with reactFauxDom

Hi,
I want to use ReadtFauxDom with chartJS, but the chartJS doesn't render anything(FauxDom is empty), I think this pb is due to the fact that ReactFauxDOM.element('canvas').getContext('2d') doesn't existe (I am not sure)
What do you think ?
here the code:

var Chart = require('chart.js');
class BarReact extends React.Component {
    constructor() {
        super()
    }
    componentWillMount() {
        var ctx = new ReactFauxDOM.Element('canvas');

        var myChart = new Chart(ctx, {

            type: 'bar',
            data: {
                labels: ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
                datasets: [{
                    label: '# of Votes',
                    data: [12, 19, 3, 5, 2, 3],
                    backgroundColor: [
                        'rgba(255, 99, 132, 0.2)',
                        'rgba(54, 162, 235, 0.2)',
                        'rgba(255, 206, 86, 0.2)',
                        'rgba(75, 192, 192, 0.2)',
                        'rgba(153, 102, 255, 0.2)',
                        'rgba(255, 159, 64, 0.2)'
                    ],
                    borderColor: [
                        'rgba(255,99,132,1)',
                        'rgba(54, 162, 235, 1)',
                        'rgba(255, 206, 86, 1)',
                        'rgba(75, 192, 192, 1)',
                        'rgba(153, 102, 255, 1)',
                        'rgba(255, 159, 64, 1)'
                    ],
                    borderWidth: 1
                }]
            },
            options: {
                scales: {
                    yAxes: [{
                        ticks: {
                            beginAtZero: true
                        }
                    }]
                }
            }
        });
        this.setState({ chart: ctx })
    }

    render() {

        return (

                        {this.state.chart.toReact()}

        )
    }
}

NB: I'm using
"chart.js": "^2.5.0",
"react-faux-dom": "^3.0.1"

If what you're working with is using a canvas, I'm afraid it won't work. There is no support for that in this library, it's just a lightweight DOM shim really. Sorry about that!

Thank you for your reply, but I found another solution without react faux dom,
Here's the solution for person who faced the same issue (To avoid asking the same question)
import React from 'react';
import Chart from 'chart.js';
import ReactDOM from 'react-dom';

class ChartComponent extends React.Component {
    componentDidMount() {
        this.initializeChart(this.props.config);
    }
    initializeChart(options) {
        let el = ReactDOM.findDOMNode(this.refs.chart);
        let ctx = el.getContext("2d");
        let chart = new Chart(ctx, options);
    }
    render() {
        return (<canvas ref="chart" height="400px" />);
    }
}

```export default ChartComponent;


Use a custom validation method to validate the uniqueness of name

Use a custom validation method to validate the uniqueness of name
The intention of this change is to address the the following deprecation seen on Rails 6:
DEPRECATION WARNING: Uniqueness validator will no longer enforce
case sensitive comparison in Rails 6.1. To continue case sensitive
comparison on the :name attribute in ActsAsTaggableOn::Tag model,
pass `case_sensitive: true` option explicitly to the uniqueness
validator.

Since there is the complexity of the config ActsAsTaggableOn.strict_case_match, we can't just explicitly set case_sensitive option as suggested in the deprecation warning.
The tests are quite blargh to deal with since the test database has the collation set to case-insensitive and has an uniqueness index, which is not realistic. To deal with the tests, I used a similar approach as in cb8d6e65cbb65a02a05f3deb28c12d5439d745af. In cases where case sensitivity matters, we alter the collation on name column, run the test, then alter the collation back.
This PR tries to solve the same problem mentioned in #1005, but since the author of #1005 hasn't responded, I'm trying my luck here.
This change has also adopted @graaff's suggestion

Any idea if this would get noticed soon?

Any idea if this would get noticed soon?

@FunnyHector , can you rebase this PR. It good to merge.

Hi @seuros , I have rebased this change onto the latest master. There was some conflict with this line in #1013.
Could you please have another look?
Sorry for late response. Somehow I must have missed the ping.

@FunnyHector Do you mind merging master back into the PR again?

@alto  the only issue left here is the non i18n error message.

@seuros Yeah, the one in name_is_unique. I agree. 👍🏻  /cc @FunnyHector

Hiya, sorry I haven't really worked on any project that used i18n :p, that often slips my mind.
I'll try to make a fix to use i18n, and rebase this work. I'm a little busy this week but hopefully I can get it done by the end of this week. Will ping you when I'm done.

@seuros @alto I've rebased this work to resolve the conflicts. I've also added a new commit to use I18n error message. Please have another look. Sorry I haven't found time to look at this until now.


fix: fix android placeholders

Summary
The <<androidCxxLibName>>Package.java has the image component package at the very top but instead should be the placeholder.
Also we can add loading the c++ library with the placeholder

perfect, thank you!


add notification plumbing for a verified email address

grab the new email.verified notification (see https://github.com/keybase/keybase/pull/3572) and plumb it up to the front end.
this depends on that server-side PR (i.e. one test failure is expected)

also we will be able to send a notification like "email.changed" if someone adds/removes an email, so frontend can refresh as well. this is cool!


"operation:" construct is not recognized by parser

Hi guys,
First of all, thank you for this tool. I am starting to learn how it works with the objective of using it for DevOps applications. Going through your documentation here: http://www.openscore.io/#/docs I was trying your hello world example and it I was getting the following error:
Command failed java.lang.RuntimeException: java.lang.RuntimeException: There was
 a problem parsing the YAML source: print.sl.
Cannot create property=operation for JavaBean=org.openscore.lang.compiler.model.
ParsedSlang@18e8eab
 in 'string', line 2, column 1:
    operation:
    ^

I then went through some of the examples you have under slang/content directory and none of them use operation: rather they use operations: and create a list for each operation. My resulting hello world ran after I had it like this:
# hello_world.sl
namespace: ricardo
imports:
  ops: ricardo

flow:
  name: hello_world
  # inputs:
  workflow:
    sayHi:
      do:
        ops.print:
          - text: "'Hello, World!'"

# print.sl
namespace: ricardo

operations:
  - print:
      inputs:
        - text
      action:
        python_script: print text
      results:
        - SUCCESS

Do you think I am doing something wrong? I am using version 0.1.229.
Thanks!
Ricardo

Hi Ricardo,
Due to our renaming issue, some of the docs are out of sync with the website version .
You can download the latest version from here (where the docs are synced with):
https://github.com/openscore/score-language/releases/tag/slang_travis_upload_test_V0.93
Thanks!
And let us know your feedback on our project!
Meir Wahnon
score team
<EMAIL_ADDRESS>From: Ricardo Quintana<EMAIL_ADDRESS>Sent: יום ו 13 מרץ 2015 21:16
To: openscore/score-language
Subject: [score-language] "operation:" construct is not recognized by parser (#162)
Hi guys,
First of all, thank you for this tool. I am starting to learn how it works with the objective of using it for DevOps applications. Going through your documentation here: http://www.openscore.io/#/docs I was trying your hello worldhttp://www.openscore.io/#/docs#hello-world-example example and it I was getting the following error:
Command failed java.lang.RuntimeException: java.lang.RuntimeException: There was
a problem parsing the YAML source: print.sl.
Cannot create property=operation for JavaBean=org.openscore.lang.compiler.model.
ParsedSlang@18e8eab
in 'string', line 2, column 1:
operation:

^

I then went through some of the examples you have under slang/content directory and none of them use operation: rather they use operations: and create a list for each operation. My resulting hello world ran after I had it like this:
hello_world.sl
namespace: ricardo
imports:
ops: ricardo
flow:
name: hello_world
inputs:
workflow:
sayHi:

  do:

    ops.print:

      - text: "'Hello, World!'"

print.sl
namespace: ricardo
operations:

print:
inputs:
- text

action:
python_script: print text

results:
- SUCCESS

Do you think I am doing something wrong? I am using version 0.1.229.
Thanks!
Ricardo
—
Reply to this email directly or view it on GitHubhttps://github.com/openscore/score-language/issues/162.

Just to make sure I understand correctly, that new version is in sync with the docs that are on the website?

yes

Hi @rqc , we have renamed the project as you see (to CloudSlang)
We just launched our new website : http://www.cloudslang.io/
So docs and CLI should be synched now.
Let us know if you see any other issue!

@meirwah Thanks for the heads up. I will reference the new website from now on.


Update filtering-and-searching-issues-and-pull-requests.md

Adding additional information about querying Pull Requests with is:merged and is:unmerged filters

Why:
Closes: https://github.com/github/docs/issues/33906
What's being changed (if available, include any code snippets, screenshots, or gifs):
small but valuable  update - only one line added
Filter issues by state of merging: is:merged or is:unmerged
it's a small but valuable update: adding is:merged and is:unmerged filters for Pull Requests queries
It can help with combining with other filters such as is:closed
Check off the following:

[ ] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ] For content changes, I have completed the self-review checklist.

@ko23 Thanks so much for opening a PR! ✨ I noticed you added the new line under

For issues, you can also use search to:

Do you think it might make more sense to add the new line under the following section, since the new line adds content relevant to PRs?

For pull requests, you can also use search to:

It would also make sense to update the line to read "Filter pull requests by state of merging..." (as it currently reads "Filter issues by state of merging..."
Let me know what you think! 💛

@nguyenalex836

thank you for super-fast and valuable review
"Do you think it might make more sense to add the new line under the following section, since the new line adds content relevant to PRs?" -> yes it can be good idea
"It would also make sense to update the line to read "Filter pull requests by state of merging..." (as it currently reads "Filter issues by state of merging..." " -> ok, your proposal is better

Do you want to make changes by myself to this particular Pull Request or it should be done in other way?

@ko23 No problem at all! 💛  Feel free to make the changes yourself, and let me know whenever you are ready for me to review again!

@nguyenalex836

I've just moved line to the Pull Request Section, as suggested (and I changed Filter issues to Filter Pull Requests
I've also added link to About pull request merges for better navigation

@ko23 These changes look wonderful! I'll update the branch and get this merged once tests are passing 🍏


typo: Double word "the"

@nschonni : Thanks for your contribution! The author, @goraco, has been notified to review your proposed change.

Verified typo corrections. @nschonni Thank you.


Add io.Reader support

Hey @nekrassov01,
First of all, your project is dope!
I used to utilize with gonx before, because it was easy to work with. The smooth transformation of $label format into regEx made it super user-friendly.
Any chance you could add support for io.Reader to pull in log Data? Or maybe introduce a new API for ParseStdin?
I'm thinking of revamping teler IDS using this library, and I've already started reworking it from scratch^1.
Thanks!
dw1

Thank you.
Yes, I knew it would be nice to have the ability to parse logs in real time, and I was planning on doing that eventually.
I haven't figured out how I'm going to design it yet, but I'm going to get to it in between other projects.

@dwisiswant0
A new version of this module is almost complete.
Most of my concerns have been revamped.
However, there are a number of changes to method signatures.
Also, the Parse method now assumes stream processing.
If it looks OK after using it for a while, I will merge it.

@dwisiswant0
I've been making quite a few changes for a while, but I've found a compromise and have merged them into main and released 0.0.18.
I would be happy to have my code incorporated, so please use it!

Thank you for your efforts in getting my request done, @nekrassov01 - I really appreciate it!


Add verification of more pod during rhods install

https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhods-ci-pr-test/1859/console


ENH: Move overview selector to toolbar

The only missing thing I think is to make a proper icon. @hoechenberger did you help with that / can you make one here and push?
This also gives an easy way to remove the bar because you can just deselect:
https://user-images.githubusercontent.com/2365790/161298432-0a6d1089-07b1-40d3-95ea-af9d920a33fa.mp4
Closes #86

... also I think we should get rid of the "fullscreen" button, modern UIs should provide this functionality I think.

Wait, can you select more than one mode? +1 for removing the fullscreen button.

No, you cannot select more than one.
Also, I think the toolbar is more standard and looks better without labels:

The hover still shows you the full name, and I think the icons are clear enough that once you've done it once or twice you know what the buttons do.

(I can push a commit for this if others agree it's better)

Here is the equivalent text-beside-icon mode:

Okay I found a decent icon from here called "view quilt":

Ready for review/merge from my end!

I prefer no text, but this could also be a user-configurable setting.
If only one option is selectable, you should use radio buttons. Not sure how to deal with disabling the bar then, I'd go for a combobox instead.

If only one option is selectable, you should use radio buttons.

I would, except 1) checkboxes are more standard in menus in my experience, and 2) no option is also an option. So checkboxes where at most 1 (but can be 0) are selectable is fine here I think.
I'd rather not use a combobox because then the text shows up, which I think is a waste of space (as it is for the other buttons). Which mode you're in is usually very obvious anyway from the actual display

I would, except 1) checkboxes are more standard in menus in my experience, and 2) no option is also an option. So checkboxes where at most 1 (but can be 0) are selectable is fine here I think.

I've never seen checkboxes where only 0 or 1 are selectable. Checkboxes are used for an arbitrary number of selections. I would use radio buttons and add a "None" (or "Hide"/"Off") option if you don't want a combobox.

I've never seen checkboxes where only 0 or 1 are selectable.

I think I've seen this in menus before at some point (and I don't think I've ever seen combo boxes), but I'm not positive. Most things I went looking for online suggested a checkbox-with-exclusivity approach for menus, too. Even though the combobox approach involved a bit more complexity, I can ultimately live with it though (pushed now; the flickering is just some peek bug, it doesn't happen during actual interaction):
https://user-images.githubusercontent.com/2365790/161318271-4fec5922-9fa5-491a-a7ba-b87ed7326b4c.mp4

I think this is now very nice! I like it!

BTW, does the overview bar show annotations and/or events?

Not sure, feel free to check

works great !


Loading spinner ring is wobbly

It's tricky to tell, but I don't think it's an optical illusion.

You're right — I've noticed this too, it's definitely not an optical illusion. I wasn't sure if it was a style choice or just something wrong with the dimensions.

Marking as "good first issue" with the hope that a fix will be as straightforward as adjusting the dimensions of the image.

It's not an illusion - the image resource itself is misaligned.
Bottom:

A gap of 6 squares to the boundary.
Top:

A gap of 2 squares. to boundary.
*square!=pixel, it's a dynamic image-editor thing.

Wow, @ray-kraesig, you managed to record a perfectly looping GIF! :tada:


use tox-lsr 2.2.0

Upgrade to tox-lsr 2.2.0 to pick up fix for improving collection
testing to get rid of black.

@sergio-correia can you check out these test failures?


Wraps set min/max dates later so they get fired correctly.

Before this change, if you have calendars A and B on the same screen and update the min/max date on B by changing the date value on A, the property gets updated correctly, but the pikaday calendar in the DOM does not.
I attempted to reproduce this in the pikaday-input integration test, but wasn't able to.

@patrickberkeley this currently breaks all tests, could you investigate? IIRC this has to do with the Ember runloop not being executed in tests.

@duizendnegen Yup I will take a look.

@duizendnegen tests are passing now.

Sweet - thanks


Create Posts “janvier-en-vrac”

Automatically generated by Netlify CMS

👷 Deploy Preview for shiny-babka-998c7e processing.

Name
Link

🔨 Latest commit
fa1b574f6cfc7f961bda0f36344af114077f0005

🔍 Latest deploy log
https://app.netlify.com/sites/shiny-babka-998c7e/deploys/63d7c7080772e90008c70c1e


Serverless creating a "null" folder upon deploying

When deploying the service to AWS lambda, serverless uploads a zip, as expected, to S3.
The size of the lambda was unusualy big, resulting in a failed deployment, so i decided to download the zip file.
Error thrown by serverless:
Resource handler returned message: "Unzipped size must be smaller than 262144000 bytes (Service: Lambda, Status Code: 400
Upon downloading and expanding the zip, I found that there is a folder called "null" that is 342MB big

This folder is quite big and contains yarn for some reason?
Inside of the 'serverless-python-requirements' folder are 2 sub folders:

a 51MB folder called "downloadCacheslspyc"
a 150MB folder with my poetry dependencies

There is also a .Cache folder of 60MB that I dont know how it got there.
Because the zip is so big, the deployment keeps failing.
I tried adding more ignores to the package patterns, but with no luck so far.
Could this be due to this plugin or should I report this to the main serverless repo?
All guidance is apreciated.
My package.json:
{
  "name": "api",
  "license": "Unlicense",
  "description": "",
  "version": "0.1.0",
  "devDependencies": {
    "serverless": "^3.7.2",
    "serverless-domain-manager": "^6.0.2",
    "serverless-newrelic-lambda-layers": "^3.0.0",
    "serverless-plugin-warmup": "^7.1.0",
    "serverless-python-requirements": "^5.1.1"
  }
}

My serverless.json:
{
    "service": "api",
    "frameworkVersion": "3",
    "provider": {
      "name": "aws",
      "stage": "${opt:stage}",
      "runtime": "python3.9",
      "iam": {
        "role": {
          "statements": [
            {
              "Effect": "Allow",
              "Action": ["lambda:InvokeFunction", "dynamodb:*"],
              "Resource": "*"
            }
          ]
        }
      }
    },
    "functions": {
      "main": {
        "handler": "src/main.handler",
        "events": [
          {
            "http": "ANY /"
          },
          {
            "http": {
              "path": "/{proxy+}",
              "method": "any",
              "cors": true
            }
          }
        ],
        "timeout": 30,
        "warmup": {
          "default": {
            "enabled": true
          }
        }
      }
    },
    "package": {
      "patterns": [
        "!venv",
        "!*.Jenkinsfile",
        "!node_modules",
        "!src/tests",
        "!Dockerfile",
        "!terraform",
        "!config"
      ]
    },
    "plugins": [
      "serverless-domain-manager",
      "serverless-plugin-warmup",
      "serverless-python-requirements"
    ],
    "custom": {
     "pythonRequirements": {
        "usePoetry": true,
        "usePipenv": false,
        "slim": true
      },
      "stage": "${opt:stage}",
      "warmup": {
        "default": {
          "enabled": true
        }
      }
    }
  }

Hello @ToneVDB - are you able to provide a small reproducible example that I could run on my side to check if the problem happens? I didn't enounter anything like this so far. Additionally, could you verify that you're using the latest version of the plugin?

Hi @pgrzesik ,
We believe to have found the issue.
Localy the packaging and deploying was running fine, the issue persisted in a CICD pipline on jenkins using a specific docker agent for that step.
We decided to run the deploy command with the --verbose flag resulting in the following output:
Generating requirements.txt from "pyproject.toml"
Parsed requirements.txt from pyproject.toml in /tmp/jenkins/workspace/api_feature_h2o-795/.serverless/requirements.txt
Installing requirements from "null/.cache/serverless-python-requirements/a5abf46136cbf8a77486507148e5e30f4eb9af0c7db22e9a9131f88f64ea313b_x86_64_slspyc/requirements.txt"
Using download cache directory null/.cache/serverless-python-requirements/downloadCacheslspyc

We suspect that the null value comes from the appdirectory library not being able to cope.
After setting useDownloadCache and useStaticCache to false, behaviour is back to normal.
Verbose now outputs:
Generating requirements.txt from "pyproject.toml"
Parsed requirements.txt from pyproject.toml in /tmp/jenkins/workspace/api_feature_h2o-795/.serverless/requirements.txt
Installing requirements from "/tmp/jenkins/workspace/api_feature_h2o-795/.serverless/requirements/requirements.txt"

Dropping the cache statements.
The outputted zip file on s3 now looks as expected:

Without setting the cacheLocation it seems to resolve itself to null on our build agent.
It seems like the appdirectory package is at fault here.
Seeing as it is deprecated, a potential fix could be to replace this package.
A quick and dirty fix could be to try to catch the null value as it gets returned from the package and refrain from using any cache at all at this point.
Looking forward to your feedback, let me know if you would like more detail somewhere!

Thanks a lot for sharing the details @ToneVDB 🙇 As for the appdirectory package - did you found the root cause in that package by any chance or is that just a suspicion due to the fact that this library is long deprecated? I'm assuming the reproduction steps for this issue are not trivial as it only happens on your Jenkins CI/CD pipeline? Locally it's working fine?

No problem @pgrzesik :)
Reproducing the issue is indeed a bit of a pain.
I'll try to describe the details a bit more below, hoping it might make the issue more easy to reproduce.
We had a jenkinsfile that defined an agent per stage
pipeline{
   agent none
   ...
   stages{
      stage('a'){
         agent {dockerfile}
         ....
      }
      stage('b'){
         agent {some-other-agent}
         ....
      }
      stage('a'){
         agent {dockerfile}
         ....
      }
   }
}

In stage a we do a yarn install of serverless and all the sub-dependencies.
Stage b does some terraform stuff.
Stage c runs the serverless deploy/package command
Stage c still finds serverless as it is installed, but the agent got re-build/ initialized in a different location, resulting in either:

a permission issue when accessing the cache location
the cache location not existing anymore

This is what we think in the end results in the appdirectory package outputting a null value, resulting in the above described issue.
The quick fix here is to just to turn off the 2 cache parameters in serverless.json as descirbed above.
Another potential fix we found is on the jenkins side: If you define a 'global' agent the issue also disappears with the cache parameters set to true. This supports the tought path that it is a permission or access issue, as the agent is initialized/created once and continues to run for the entire pipeline in one go.
example jenkinsfile:
pipeline{
   agent {dockerfile}
   ...
   stages{
      stage('a'){
         ....
      }
      stage('b'){
         ....
      }
      stage('a'){
         ....
      }
   }
}

I havent tested it localy, but I suppose by either removing the existing cache location or changing the permissions on the cache folder, the issue should become reproducable.
Let me know if my train of tought makes sense to you 🤔

Hey @pgrzesik ! no problem, everyone is super bussy lately as far as i can tell ;)
I am sorry but I havent found any replacement libraries as well.
Seems like, in this repo, it is only used in one place thow but I am unfamiliar with the code.
A workaround for now could be to check if the path that is outputted by the function getUserCachePath starts with null/ or even more specific : if the dirs.userCache() does that.
That means that the result is invalid and should be discarded (disabling further use of the cache directory for that run)
It feels a bit wrong to me to do it this way, but apart from re-writing the appdirectory package and finding a replacement library, this seems to me like the next best thing, but I am not convinced...


Feature Request: Personalized Messages

It would be great to be able to write personalized messages, like
Hello {name of the owner of the ad}
The logs show a name. Is it any way to use it in the message?

Hey, i've added the feature yesterday and will send a pull request soon :)

Is there any update about it? Does it already work?


Playbook should be able to manage multiple installs on the same platform

Currently, the playbook does not have the ability to manage multiple installs on the same platform, which can lead to instability when using the same orchestration host across different workflows
The core issue is that the playbook has hardcoded directories in which it stores run specific information like terraform state metadata, kubeconfig, and openshift install logs. For instance, the playbook will always put those things at playbook_dir/scale-ci-aws whenever installing in AWS.
However, if you have two pipelines using the same orchestration host and also installing into AWS (i.e. PerfScale CI runs AWS and AWS OVN as separate pipelines) then this can easily start to break things, as both pipelines would be fighting over that directory and cleanups could easily remove the wrong cluster.
This could be solved if the directory was parameterized by either (1) a user/system-supplied variable or (2) a randomly generated string outputted in the playbook logs. The openshift installer does generate a unique infraID which I think we should add as a subdirectory underneath the platform level directory. That would mean that all related files for a run would go under scale-ci-deploy/scale-ci-$platform/$infraID/

I like the idea of parameterized. It could be randomly generated, like :
$platform-$sdn-unix_timestamp
Or we could prefix the timestamp... I do like the concept, this would also help us with reusing worker nodes.

Linking PR https://github.com/cloud-bulldozer/scale-ci-deploy/pull/126

Linking PR https://github.com/cloud-bulldozer/scale-ci-deploy/pull/126


UP-4371 wrap Cobertura  in .

UP-4371: As documented, the <excludes> Cobertura configuration ought to be wrapped in an <instrumentation>.

Trivial technical fix.  Invoking Lazy Consensus.  Unless otherwise actioned, mergeable without further discussion on 2015-01-05.

Merged per Lazy Consensus.


”Tarna Mare”, ”Bocicău”, ”Valea Seacă”, ”Văgaș” are listed in the drop-down menu

Description:
When user writes ”Tarna Mare”, ”Bocicău”, ”Valea Seacă”, ”Văgaș” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Tarna Mare"

Expected results
The location appears in the drop-down menu as "Sat Tarna Mare, SATU MARE (Tarna Mare)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Bocicău"

Expected results
The location appears in the drop-down menu as "Sat Bocicău, SATU MARE (Tarna Mare)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Valea Seacă"

Expected results
The location appears in the drop-down menu as "Sat Valea Seacă, SATU MARE (Tarna Mare)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Văgaș"

Expected results
The location appears in the drop-down menu as "Sat Văgaș, SATU MARE (Tarna Mare)".


404: Please make sure Strapi Server is correctly running

Hi, I was following this tutorial (https://blog.strapi.io/building-a-static-website-using-jekyll-and-strapi/) and everything was working fine until the "Posts List" step. Once I added the _layouts/home.html file and restarted the jekyll server (bundle exec jekyll serve), I ended up with an error message:
Liquid Exception: The Strapi server sent a error with the following status: 404. Please make sure it is correctly running. in /_layouts/home.html
jekyll 3.8.5 | Error:  The Strapi server sent a error with the following status: 404. Please make sure it is correctly running.
Thing is, the strapi server IS RUNNING... I have access to the the strapi admin backend and I can access and view the Posts object by visiting: http://localhost:1337/posts.
I'm not actually too sure what is going on and how I can fix this.
Anyone else got this issue?

If you are running the http://localhost:1337/posts request with Postman fir example, did you have data or a 404 error ?

Same error here following the blog instructions and code from the github repo.
Looking at the logs the Strapi API is getting a  404 because it attempts to fetch /post which does not exist. The trick is to update to /posts in Jekyll _config.yml.
https://github.com/strapi/strapi-examples/blob/6891762c9c9d627afaa2c793479a7cd242401c14/jekyll-strapi-tutorial/blog/_config.yml#L55
Then another templating error arise

Liquid Exception: Can't convert Integer into String. in /_layouts/home.html

Please can you answer to my question with Postman it will help me to understand the issue.

Sorry I dont use Postman but wget or curl works just fine

@lauriejim Hi Jim, sorry for the late response on my part, I am really busy on a huge project at the moment. I don't have Postman but i could try to test it Advanced REST Client app, which i guess is similar. I might have a bit of downtime soonish or this weekend to test this out. Thank you for reaching out, i appreciate.

regarding Can't convert Integer into String. in /_layouts/home.html
article suggests to configure the permalink (_config.yml) (therein lies the error)
IF you don't configure it, (idem comment it) it should "work"
IF you do configure it, you expect your document to contain a slug property (which you need to define as a string from your admin pannel/content-types)
IF you do configure it but select the :id instead (so you don't have to modify the content-type since strapi already serves it by default) you still get the error (for me in /var/lib/gems/2.3.0/gems/jekyll-strapi-0.1.2/lib/jekyll/strapi/site.rb::strapi_link_resolver). Apparently, you need to convert the document.id to document.id.to_s from
        :placeholders => {
          :id => document.id.to_s,
          :uid => document.uid,

@mpech aahhhh interesting, good catch. will definitely try this out. thanks

BUMP! @lauriejim @mpech
So sorry, for the humongous delay... I was in a huge project that took all my time away. I finally found the time to dive back in this small learning tutorial.
and...
I finally got it working... I ended up updating jekyll-strapi to lastest version 0.1.2, and jekyll to version 3.8.5.
I already add the gem jekyll-strapi installed, so to update it, I did in a Terminal:
gem install jekyll-strapi
This ensure that you have the newest latest version with bug fixes.
Next, your gemfile should be configured like this:
gem "jekyll", "~> 3.8.5"
[...]
group :jekyll_plugins do
  gem "jekyll-feed", "~> 0.12"
  gem 'jekyll-strapi', github: 'strapi/jekyll-strapi'
end

The "github: 'strapi/jekyll-strapi'" parameter will make sure you have the latest fix for the infamous bug: "Liquid Exception: Can't convert Integer into String"
One more thing, in blog/_config.yml, instead of "type: post"
strapi:
  collections:
    posts:
      type: post

YOU NEED TO make 'post' plural. So, you will end up with:
strapi:
  collections:
    posts:
      type: posts

If you don't you will end up with this error: "Liquid Exception: The Strapi server sent a error with the following status: 404. Please make sure it is correctly running. in /_layouts/home.html"
I hope it helps someone else struggling with this tutorial. With gems and frameworks moving and updating fast, some online tutorial become dated and out of synch with the latest builds.


[DOCFIX] Translate use cases

What changes are proposed in this pull request?
[DOCFIX] Update cn version of Use-Cases doc
Why are the changes needed?
The Chinese overview/Use-Cases doc is not updated with the latest changes,
this PR synchronizes these updates.
Does this PR introduce any user facing changes?
Developers can get to know Alluxio in Chinese easily.

@zhezhidashi can you sign the CLA form here, so that we are able to merge this PR

LocalCacheManager test timeout

alluxio-bot, merge this please


Downloaded height map is solid black.  The preview looks correct.

This happens both on your live demo and this demo.

Never mind it was my problem. lol

Yes, for anyone else that sees this, the preview is a standard RGB image, the downloaded image is single-band 16 bit (useful for heightmaps in stuff like the Unreal Engine but renders that way in many image viewers/editors).


You can not run suite correctly

HtmlTestRunner version:
Python version:
Operating System:

Description
suite = unittest.TestSuite()
# suite = unittest.Suit()
suite.addTest(KeyPageStage2("test_TradeListLoad"))
runner = HTMLTestRunner(output='test')
What I Did
Generating HTML reports...
Traceback (most recent call last):
  File "D:/03_pycharmProject/04_appiumPO/TestCase/Test_owner_SmokingTest.py", line 369, in <module>
    unittest.main(testRunner=HtmlTestRunner.HTMLTestRunner(output='example_dir'))
  File "C:\Python27\lib\unittest\main.py", line 95, in __init__
    self.runTests()
  File "C:\Python27\lib\unittest\main.py", line 232, in runTests
    self.result = testRunner.run(self.test)
  File "C:\Python27\lib\site-packages\HtmlTestRunner\runner.py", line 95, in run
    result.generate_reports(self)
  File "C:\Python27\lib\site-packages\HtmlTestRunner\result.py", line 340, in generate_reports
    tests)
  File "C:\Python27\lib\site-packages\HtmlTestRunner\result.py", line 350, in generate_file
    report_file.write(report)
TypeError: expected a string or other character buffer object

Hi @wangrocky i cannot replicate you error, could you please provide a complete example.

Hi @wangrocky,
Update here, I was able to replicate this error and it's already fixed, I make a bug fix release so if you upgrade to 1.1.1 you shouldn't have this issue anymore. Thanks for submitting this, if any other occur please let me know, also test with the new release and let me know if you're no longer getting this error.

thanks and I will try it, btw, nice report framework and i'm enjoying it :)

I'm glad to hear that:p


Deprecation's error notice

Description
Indicate that all deprecations of v3.0 will be reported as an error in v3.1.
Checklist

[ ] Update deprecations.
[ ] See in the documentation.
[ ] Update Work in progress section in changelog.

This is useless at this stage...


Should timecode maxes out at 30FPS?

With the changes made to ST 331 this past year (try DuckDuckGo as a search engine and search for "SMPTE ST 331 Amendment 1") it's possible for the SDTI-CP to support up to 120FPS. I don't know of anyone who's shooting at that rate for virtual production, but still. Should we make provision for other than "classic" SMPTE ST 12-1 timecode?

Agreed - I will fix in my current PR

Resolved in https://github.com/SMPTE/ris-osvp-metadata-camdkit/pull/125


feat: populate Programmed condition for KongConsumerGroup

What this PR does / why we need it:
Populates Programmed condition for KongConsumerGroup and prints an additional column PROGRAMMED for this CRD as introduced in https://github.com/Kong/kubernetes-ingress-controller/pull/4425 for others.

Which issue this PR fixes:
Part of https://github.com/Kong/kubernetes-ingress-controller/issues/3728

Special notes for your reviewer:
Something to discuss - I decided to check in the integration test if the condition is populated correctly because the duration of this check is ~3 seconds, hence it's negligible for an overall length of execution ~2.5%. Unfortunately, it has been written in this verbose way, because https://github.com/stretchr/testify/issues/1391 hasn't been resolved yet.

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

Can you please add KongConsumerGroup to the list of CRDs extended with Programmed condition in the last two changelog entries?

Good point @czeslavo, I've enhanced those entries


[Request] Sluggify modName to improve usability of certain commands

Commands that work with currently installed mods in the pack do not always succeed in finding the mod specified. This is especially apparent if mods contain spaces or special characters.
An example of this is packwiz rm <modname> where a modname like Fabric API would result in an error "accepts 1 arg(s), received 2" or a modname "Reese's Sodium Options" would result in a message "You don't have this mod installed".
Improving this might also require looking at multiple arguments in the command to include any spaces or instead inform the user to use quotation marks (").
Note: I tried to look at the code to educate my answer, but I'm both new to GO and did not have enough time to fully understand everything. I would be open to implementing this myself and making a PR when I have the time. I mostly encountered this with the packwiz rm command, if you know of any other similar instances please mention this in a comment as well.

Also see https://github.com/packwiz/packwiz/issues/18


bot 启动报错 TypeError: Cannot create a consistent method resolution

`Traceback (most recent call last):
  File "bot.py", line 3, in <module>
    from graia.application import GraiaMiraiApplication, Session
  File "/qqbot/PixivBot/pixiv_venv/lib/python3.7/site-packages/graia/application/__init__.py", line 17, in <module>
    from graia.application.event.lifecycle import (  # for init lifecycle events
  File "/qqbot/PixivBot/pixiv_venv/lib/python3.7/site-packages/graia/application/event/lifecycle.py", line 6, in <module>
    class ApplicationLaunched(BaseModel, BaseEvent):
  File "/qqbot/PixivBot/pixiv_venv/lib/python3.7/site-packages/graia/broadcast/entities/event.py", line 27, in __new__
    **kwargs
  File "pydantic/main.py", line 324, in pydantic.main.ModelMetaclass.__new__
  File "/www/server/panel/pyenv/lib/python3.7/abc.py", line 126, in __new__
    cls = super().__new__(mcls, name, bases, namespace, **kwargs)
TypeError: Cannot create a consistent method resolution
order (MRO) for bases BaseModel, BaseEvent
`

已修复，请更新后重新安装依赖

已修复，请更新后重新安装依赖


Distinct entries

I want to fetch distinct entries from the field. Is there any option where I can avoid duplicate entries?

@sarita-dc BTW using Array.filter can help.


Google Maps API -Research

User Story: As a developer, I want to research the Google Maps API, so that I can understand how to integrate interactive maps into WanderCast.
Acceptance Criteria:

Find official documentation and tutorials for the Google Maps API.
Identify key features such as map rendering, adding markers, and handling user interactions.
Document findings and provide code examples for basic map integration.

Obtain API Key

Task: Understand the process to obtain an API key and set up a Google Cloud project.
Resource: Get Started with Google Maps Platform

Documentation has been reviewed and a API created for our Wander Cast App


Self-hosted px-operator does not take into account TLS certificate

Describe the bug
I followed the self-hosted steps to install Pixie instance. The cloud_deps and cloud deployed fine - all pods running. I installed the self-signed certificate in my MacOS System keychain and I can login to the web page and create password. The problem is when I px deploy.
To Reproduce
Edit this script to add my custom domain and run it:
./scripts/create_cloud_secrets.sh
Use kustomize to create cloud_deps.yaml and cloud.yaml
kustomize build k8s/cloud_deps/public/ > cloud_deps.yaml
kustomize build k8s/cloud/public/ > cloud.yaml
Create plc namespace and apply the two yamls:
kubectl create ns plc
kubectl apply -f cloud_deps.yaml --namespace=plc
kubectl apply -f cloud.yaml --namespace=plc
Run dev_dns_updater:
sudo ./dev_dns_updater --domain-name="< my-custom-domain >"  --kubeconfig=$KUBECONFIG --n plc
kubectl log create-admin-job-<pod_string> -n plc
Login to  and create the admin password.
export PL_CLOUD_ADDR=< my-custom-domain >
bash -c "$(curl -fsSL https://< my-custom-domain >/install.sh)"
px deploy-key create
px deploy -k < the key from above > -y
Expected behavior
Now I should see my cluster deployed and instrumented but I see an error:
FATA[0361] Timed out waiting for cluster ID assignment
When I look at the logs of vizier-operator-84c7b99594-bvwpx in the px-operator namespace I see this error:
time="2021-09-11T20:53:14Z" level=info msg="Failed to update Vizier instance" error="rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority""
It seems that the certificate that was created by the ./scripts/create_cloud_secrets.sh script is not the one vizier-operator trusts.
Logs
I tried running 'px collect-logs' but it prints and error probably because deployment is not successful:
Cannot find running Vizier instance
App information (please complete the following information):
px version - 0.6.6+Distribution.de1f118.20210904032616.1
k8s version - v1.20.7

Hi,
Thanks for filing. For self-hosted Pixie, you will need to put the dev_cloud_namespace flag (see https://docs.px.dev/installing-pixie/install-guides/self-hosted-pixie/#3.-deploy-pixie).
px deploy --dev_cloud_namespace plc

For more context scripts/create_cloud_secrets.sh creates a CA and cert and installs the CA on your system trust. However this generated CA isn't passed into the cluster. So the pods in you cluster don't trust this CA.
Using dev_cloud_namespace tells vizier to use the cluster local addresses instead and bypasses this CA check.
If you want to use a non cluster local address for vizier<->cloud communication then we recommend using a DNS for a domain you control and getting actual SSL certs using LetsEncrypt or something similar.


Add environment variable to disable version check entirely

As someone who has Github notification enabled, I find version checking quite useless, and there is also Github's API rate limit to be concerned. I know it only triggers with --help and --version flags, and also caches the result, but I'm an airhead that hits the help command every 1-2 minutes.
This simple commit introduces MANGAL_DISABLE_VERSION_CHECK environment variable, which a user can set to any non-empty values to have a peace of mind.

Hi!
Thank you for the pull request,
That's a nice idea, but I think it would be better to make it a config key like new_version_notify in the https://github.com/metafates/mangal/blob/main/key/keys.go which will make it available as env variable and file based config field at once.
I'll add it a bit later

Sorry for the late response as I've been quite busy lately. I didn't notice the mangal env command so wasn't aware all the configurations can be set as env var.
I changed the PR to add cli.version_check option (new_version_notify sounds quite mouthful in my opinion). If you object I can change the option name the way you prefer.

Oh, thank you! That's exactly what I wanted to do. Agree, your naming is better 😄


Hook own GH generator dist to own Milgraphics repo

Here is setup for local:

Here is setup for local:


feat(transformData): refinementList + menu implementation

Adds transformData parameter to the menu and refinementList widgets for review before implementing everywhere.
See #116 .

LGTM :+1:

Have to admit my comment abt identity is driven by the fact I would want to avoid using lodash where we can bc with our current setup we have all es5 and es6 features which are covering some good code from lodash.
And lodash is quite big unfortunately

Well about using lodash, don't we have it as dependency already? All the goodness from babel won't bring us any of the API from lodash. And we're only scratching what we can get from it...

Well about using lodash, don't we have it as dependency already?

It's true, babel does bring us the basics, merge (not deep), all ES5 and ES6 array methods but it's still way lower than lodash I do agree.
Still lodash is HUGE! And I fear that sometimes we can be lazy on the data structure we design because we know we can just use find({prop}, collection), that's another discussion.

LGTM

@vvo @bobylito I've committed a version without lodash. I have no preference, you?

I'm still thinking about another naming than transformData but cannot find better right now; so LGTM.

I have no preference, you?

me neither :)

If we don't use lodash, it's totally fine with me :)
LGTM too


Scale disk graph in IoT Edge device details.

This solves the problem of to fine granular disk space usage graph in the azure edge hub device details workbook.
Since the amount of data is dynamic (it depends on the number of disks and not only on the sampling frequency) the current strategy of bining just to the sampling frequency can lead to "too many points" errors.

This can be avoided by choosing the max_of({timeRange:grain}, time(\"{samplingFrequency}\")) and not only the samplingFrequency.
The maxOf avoids the generation of too fine grained bins (smaller than the sampling rate) and the grain increases the bin-size if large time frames are used. The data isn't distorted since the max-value is chosen for aggregation - so huger bin's do no harm.
Please let me know if I was unclear or you need further details. Thanks in advance for considering this change.

Just to add the math behind it - at a sampling rate of 5 minutes you generate around ~ 2000 data-points per week. With logical volumes we have usually have 7 "disks" - so without further scaling we end up with ~ 14000 data-points for seven days - giving the mentioned error.


add support for native es modules in Node

name: "\U0001F41B Bug fix or new feature"
about: Fixing a problem with Redux
PR Type
Does this PR add a new feature, or fix a bug?
Why should this PR be included?
Checklist

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Is there an existing issue for this PR?

https://github.com/reduxjs/redux/issues/3860

[x] Have the files been linted and formatted?
[x] Have the docs been updated to match the changes in the PR?
[x] Have the tests been updated to match the changes in the PR?
[x] Have you run the tests locally to confirm they pass?

New Features
What new capabilities does this PR add?
What docs changes are needed to explain this?
Bug Fixes
What is the current behavior, and the steps to reproduce the issue?
What is the expected behavior?
How does this PR fix the problem?

Thanks, but the .cjs thing is going to be an issue for a number of tools and apps that we use (outside of this repo) for a while. I get that is a requirement for a dual mode module right now, but I'm not entirely happy with it. I'd rather wait until Node improves the transition to this module format.


Sticky Component is not working

Hii,
I have a ad page which has sticky form.
in react native base it is working fine but when i am integrating the nextjs (solito) then it is not working.
i searched alot but nothing found.

following is my code for ad sticky  form which was working.
 <ScrollView stickyHeaderIndices={[0]} ref={scrollViewRef}>         <Hidden till="md">           <View>             <AdForm               name={name}               email={email}               phone={phone}               error={error}             />           </View>         </Hidden>         </ScrollView>
    the above code was working fine just with react native base but with nextjs solito not working

Please help me
thanks

Did you read the docs for scroll views? https://solito.dev/recipes/scroll-view
You likely need to wrap your ScrollView like this:
<View style={{ flex: 1 }}>
  <ScrollView />
</View>

No that is not working.

I moved the sticky form out of scrollview and added it in view and that worked
<View
position="sticky"
top={'2'}
right="30"
width={'100%'}
zIndex={9999999999999}
>


docs: update toc version

Description

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

:tada: This PR is included in version 7.1.0 :tada:
The release is available on:

GitHub release
v7.1.0

Your semantic-release bot :package::rocket:


Revert "Revert "Merge _staging into main""

Reverts usdigitalresponse/usdr-gost#523

BEGIN;

alter table tenants drop column uses_spoc_process;

/* verify that the column is dropped */
select * from tenants;

/* if previous query looks good go ahead and commit */
commit;

I will be running this statement prior to running migrations.


HTML report does not show states from hidden (and perhaps other elements)

Given the following proposition and queries, only the appContent's textContent shows in HTML reports (even when some of the other predicates are the responsible parties for the failure). I suspect it has to do with the div#console_xxx divs being "hidden"; i.e., having an attribute "hidden: 1" on them.
proposition :: Boolean
proposition =
  let
    initial = isJust loginTitle
    login = initial && next usingApp
    usingApp = not $ String.null $ fromMaybe "" appContent
    errorFree = Array.null allErrors
    logout = usingApp && next login
  in initial && always ( login || usingApp || logout ) && always errorFree

loginTitle :: Maybe String
loginTitle = _.textContent <$> queryOne "div#login-container .login-form-title.o-form-head" { textContent}

appContent :: Maybe String
appContent = _.textContent <$> queryOne "#main-app" { textContent }

pageTitle :: Maybe String
pageTitle = _.textContent <$> queryOne ".page-title" { textContent }

type LogEntry = { content :: Maybe String, timestamp :: Maybe String }

consoleErrors :: Array LogEntry
consoleErrors =
  queryAll "div#console_error > div > div" { content: attribute (SProxy :: SProxy "data-content"),
                                             timestamp: attribute (SProxy :: SProxy "data-timestamp") }

consoleDebugs :: Array LogEntry
consoleDebugs =
  queryAll "div#console_debug > div > div" { content: attribute (SProxy :: SProxy "data-content"),
                                             timestamp: attribute (SProxy :: SProxy "data-timestamp") }

consoleWarnings :: Array LogEntry
consoleWarnings =
  queryAll "div#console_warn > div > div" { content: attribute (SProxy :: SProxy "data-content"),
                                            timestamp: attribute (SProxy :: SProxy "data-timestamp") }

consoleInfos :: Array LogEntry
consoleInfos =
  queryAll "div#console_info > div > div" { content: attribute (SProxy :: SProxy "data-content"),
                                            timestamp: attribute (SProxy :: SProxy "data-timestamp") }

beginsWith :: Pattern -> String -> Boolean
beginsWith p s = take (length (unwrap p)) s == (unwrap p)

cljSpecFailStr = Pattern "did not conform to spec."

cljSpecFailures :: Array LogEntry
cljSpecFailures = filter (\e -> contains cljSpecFailStr (fromMaybe "non-match" e.content)) consoleInfos

uncaughtInfos :: Array LogEntry
uncaughtInfos = filter (\e -> beginsWith (Pattern "Uncaught") (fromMaybe "non-match" e.content)) consoleInfos

infoErrors :: Array LogEntry
infoErrors = filter (\e -> beginsWith (Pattern "Error") (fromMaybe "non-match" e.content)) consoleInfos

validationFailures :: Array LogEntry
validationFailures =
  filter (\e -> beginsWith (Pattern "Validation failed") (fromMaybe "non-match" e.content)) consoleWarnings

allErrors :: Array LogEntry
allErrors = infoErrors <> validationFailures <> uncaughtInfos <> cljSpecFailures <> consoleErrors

Ah, yeah that might be problematic for hidden elements. I'll add a detailed table of queries and matched elements with states below the screenshots. Doesn't make much sense to try overlaying hidden elements on the screenshots even some position could be retrieved.

Awesome. Thank you!

Draft here: https://github.com/quickstrom/quickstrom/pull/85
Can you try it using that branch and see if it works with your spec?

Tried and it works. Thank you!

OK, merging the PR then. Thanks!


add prerender bot

Not sure this is how it's supposed to be done, but I tried 😄

Apparently this really isn't how to. @JayBizzle can you assist?

Thanks!


Return created type from Archetype#apply, Fixes #1423

SpongeAPI | SpongeCommon
A small change to allow a plugin to access the newly created type from applying an archetype.

Small but yet breaking...

@liach Yes, thats why this is bleeding and not stable.


[WIP][SPARK-40540][SQL] Migrate execution errors onto error classes: _LEGACY_ERROR_TEMP_2026-2050

What changes were proposed in this pull request?

This PR proposes to migrate 26 execution errors onto temporary error classes with the prefix _LEGACY_ERROR_TEMP_2026 to _LEGACY_ERROR_TEMP_2050.
The error classes are prefixed with _LEGACY_ERROR_TEMP_ indicates the dev-facing error messages, and won't be exposed to end users.
Why are the changes needed?

To speed-up the error class migration.
The migration on temporary error classes allow us to analyze the errors, so we can detect the most popular error classes.
Does this PR introduce any user-facing change?

No
How was this patch tested?
$ build/sbt "sql/testOnly org.apache.spark.sql.SQLQueryTestSuite"
$ build/sbt "test:testOnly *SQLQuerySuite"

@itholic Please, resolve conflicts.

Merging to master. Thank you, @itholic.


primitive caps of size 1nF are not getting generated

Primitive generator takes very long time (>30 min) for generating 1nF cap in sc_dc_dc_converter.  Can't generate these caps using common centroid methodology also.

max cap size is ~10pF

@kkunal1408 This needs a discussion: whether that big single cap is used (generally unit cells are connected to implement a larger cap; PDKs does not support)

@arvuce22 sure. Then can we have a parameter from PDK layers.json on what size it is supported?

@kkunal1408 yes, we can add max size for caps and resistance (similar to we have for nfins: "max_nfin_mos")

the max_* parameters can be used as a check (throw an assertion if something higher arrives) but this should be a task handled by the person writing the netlist.
If any automatic breaking up is needed, should be done as a netlist pre-processing step.


Each menu has same items in it.

Both menus are using the same InventoryProvider that takes in a list of items and a menu name, but each menu shows the same amount of items.
Farming Menu:

Mining Menu:

Creating a menu:
This is called once for Farming and once for mining, collectionList is the items that the menu should set.

can you show your class that implements inventory provider

you should override update(InventoryContents) method in the class that implements inventory provided

you can also re-run the init method, it will update the inventory too

Can I just put init(); inside the update() method, or is that inconvinient?

i guess no, it's no problem.

That doesnt seem to work

trying this now

where you want to update your items?

show the full code, i can't understand what you are trying to do

Change variables

on all items in the list

change and update placeholders on items*

just create i new icon.

where?

where you want to update the inventory.

should I do it in the update() or init()?

and when does update() gets called

when you use notifyUpdate method in inventory contents or smart inventory classes

so I should call notifyUpdate in the beginning of init or...

or call notifyUpdate() if player is already a part of inventory contents?

when you run the notify update method it will run the update method for all player that opens the page. so if a player part of an inventory contents the update method will run for the player

I see, let me try it out

cant get it to work
these values a suppose to update, but they dont, not even when I relog from the server.

update method:

init method:

How I open menus:

i did some doc. here
https://github.com/portlek/SmartInventory
it may help.

You have a Page.parent but that doesnt exist

and theres is no pagination tutorial. And can you make an example of a functional pagination page with parent pages :)

use 2.5.2

added pagination example in it

I still have this issue, pagination items doesnt update :/

between InventoryProviders

I am creating 2 of the same inventoryproviders which are using pagination to.

is there a method to find how many free slots the menu has ?

I can put items into the menu ?

When using fill border, some slots are not filled

you should make the pagination override setting as false.

SlotIterator#allowOverride(boolean)

There is no option for that

it's in the slot iterator class, not pagination.

Oh I need to create a new SlotIterator instance

actually no, pagination has a new iterator method, and it's creating the instance actually, just separate it as a field or method field like
final SlotIterator it = pagination.newIterator(....)
.allowOverride(false);

It doesnt let me

oh wait, its in the inventory contents

aah thank you

I am still able to put items inside the menu

can you test the pagination example in the readme as independent from other stuff.


Tabs iussue

After going to the tab page if i want to come back to the page with no-tab ; Tabs still shows up in both this.navCtrl.push() and this.navCtrl.setRoot() method .

Hello! While we appreciate you opening an issue with us i am going to close this issue and ask that you open a new one that has the issue template filled out please. Thanks for using Ionic!


Effective Method Naming

just an fyi, according to https://golang.org/doc/effective_go.html#Getters you can drop the Get in getters i.e. GetCount() becomes Count()
Thanks for the package!

Thanks dude, will take care of it in the morning :D

is there a way i can reach you via private msg?

I sent you a mail, you can figure out mail addresses by inspecting commits with git log :)


Some time we need to show the value and unit instead of percentage

parameterize the unit of value, and enable to show the value in some case instead of percentage

@vietanh85 Can you describe your use case a little more? Displaying a raw value with a unit other than % makes no sense with this component - it would still calculate the filled portion of the ring based on val/max (or val/100 if no max is provided). I would recommend checking out the px-kpi component, which may be better suited for your needs.


Add a MAINTAINERS entry for release notes

Add a MAINTAINERS entry so we get the release notes tag on release notes PRs, should make a bit easier to manage release notes review close to release time. Had to fix a couple bugs in the set assignees script as well while testing.

Changed the MAINTAINERS entry to "maintained" and pointed it to @laurenmurphyx64 and @stephanosio.


HTTP client/server test

adds an HTTP client -> server distributed trace propagation test; closer to replacing root span "Trace" interface with single Layer interface.

Coverage decreased (-0.1%) to 99.878% when pulling 1cde58afdc7c4a241ea3a5f4cdb8215b059f87ab on http_client into de95783c98acde6db00f3000a6184596f135b715 on master.

Coverage remained the same at 100.0% when pulling bc3d1457ee8a4f3b8c8896dd511e07594b376dba on http_client into de95783c98acde6db00f3000a6184596f135b715 on master.

Coverage remained the same at 100.0% when pulling 33e90105f4391f9546d300a182bd155adf1bb00a on http_client into de95783c98acde6db00f3000a6184596f135b715 on master.

LGTM


Produce a smaller artifact for ease of use

For example, an artifact for uulm-quickstart.zip? Which contains only the theme, the demo-file, and the logos?

In case this is relevant, please create an issue here: https://github.com/SEatUPB/FancyBeamer/issues/new