feat(card-group): modify to allow Card link design pattern

Related Ticket(s)
DDS Consulting Issue: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/6876
HC JIRA Ticket: https://jsw.ibm.com/browse/HC-2138
Description

This PR is a follow-up based on the discussion mentioned in this PR - https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/6826

Design & Functional Specs

https://github.com/carbon-design-system/carbon-for-ibm-dotcom-website/wiki/Tabs-extended#22-orientation
https://github.com/carbon-design-system/carbon-for-ibm-dotcom-website/wiki/Card-link

Changelog
New Components/Props

pattern-background - this prop/attribute is used when the card group item has the same background color as the pattern container.
<dds-card-link-heading> - a component extended from <dds-card-heading> that captures the proper expressive heading styling for the Card Link UI component.

Removed

N/A

HTML (with Card Link)
<dds-card-group grid-mode="narrow">
  <dds-card-group-item href="https://example.com" pattern-background>
    <dds-card-link-heading slot="heading">IBM Developer - Card 01</dds-card-link-heading>

Learn, code and connect with your community

    <dds-card-cta-footer slot="footer">
      <svg slot="icon" focusable="false" preserveAspectRatio="xMidYMid meet" xmlns="http://www.w3.org/2000/svg" fill="currentColor" aria-hidden="true" width="20" height="20" viewBox="0 0 20 20">
        <path d="M11.8 2.8L10.8 3.8 16.2 9.3 1 9.3 1 10.7 16.2 10.7 10.8 16.2 11.8 17.2 19 10z"></path>
      </svg>
    </dds-card-cta-footer>
  </dds-card-group-item>
</dds-card-group>

Testing Instructions

Visit the Card Group with Card Links layout component - /?path=/story/components-card-group--with-card-links
Ensure that the Card links look good within the Card group layout component in all breakpoints.
Visit the Tab Extended with Card Group Card Links layout component - /?path=/story/components-tabs-extended--with-card-group-card-links
Ensure that the "Vertical" tabs component matches with the design specs for all breakpoints.

@ariellalgilmore Thanks! I just pushed up a commit that fixes some of the typos.

Hey gonna bring the discussion here to loop in @ariellalgilmore and @photodow , I'm trying to figure out if this is the best approach. This PR exposed some spacing issues we should definitely look into - but before that, for allow Card links in Card group, should we fix this bug on CTA instead of doing it through this PR?
I'm worried about adding this to Card group would make it deviate from intended functional spec, and also would the Card links here still get the CTA functions (video, download, etc)?

Hey gonna bring the discussion here to loop in @ariellalgilmore and @photodow , I'm trying to figure out if this is the best approach. This PR exposed some spacing issues we should definitely look into - but before that, for allow Card links in Card group, should we fix this bug on CTA instead of doing it through this PR?
I'm worried about adding this to Card group would make it deviate from intended functional spec, and also would the Card links here still get the CTA functions (video, download, etc)?

ohh hmm yeah i think it would make sense to create the dds-cta-card-link.  Then in card-group we could create a new sub-component dds-card-group-card-link-item. The fix for #5740 would allow dds-cta-card-linkto have the different CTA functions. Let me know if that makes sense @proeung.

Just pushed up a commit that adds in the new dds-cta-card-link and dds-card-group-card-link-item elements. My apologies for the delay in getting these changes in, it's been a couple of days.


Exclude jars from deployables

We have some maven projects that use maven-assembly and maven-shade plugins to produce a fat jar with some modifications. I was recently working on performing those with bazel, and it turned out that the SingleJar utility already supported most of the scenarios we need. So a combination of producing a deployable.jar + jar_jar can get us very far.
The only thing that is missing is the ability to filter our (exclude) certain jars from being included in the deployable.
To make things easier, I propose adding an additional parameter to scala_library, called exclude_for_deployment (or similar), which would accept a list of targets to exclude. Those targets will not be included in the final deployable.jar, and everything will "just work".
@johnynek WDYT?
@ittaiz

Discussion continues on 1402 issue of bazel itself.
Essentially what we need is provided scope but our current suggestion is an
intermediate step to have provided only for deploy jars
On Mon, 16 Jul 2018 at 18:26 P. Oscar Boykin<EMAIL_ADDRESS>wrote:

the java rules have a parameter called neverlink which we don't support
currently. Would that work for you? I know that the neverlink case is on a
node for its downstream, vs what you are deploying is looking upstream.
I'm concerned about making a custom thing that works differently than the
java rules when in fact, the problem is the same.
Can you say anything about your use case? i.e. why doesn't jarjar being
run on the deploy jar meet your needs? Why neverlink can't meet your needs?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/560#issuecomment-405285719,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIFwI135lTwPnw3jSRKAR2wHwsnOPqks5uHLClgaJpZM4VQmZB
.

Closing in favor of #576


managedRPCSettings() can deadlock

I've seen managedRPCSettings() deadlock with master (fda4e228); and probably also with the 0.5.1 release. (On linux). The problem is seems to be that managedRPCSettings() takes a read lock on h.mu, and then calls h.Settings() which in turn also takes a read lock. The deadlock happens if a second goroutine attempts to take a write lock during in the interval between the two read locks; the write lock and the second read lock both start waiting.

Good catch! The read lock in managedRPCSettings is unnecessary and should be removed.


0.2.4 Update loop

Did something forget to get tagged properly?  After installing 0.2.4 from the updater it constantly tells me I'm on 0.2.3 and there's an update available.

Hi @barrettj, I pushed the new release and for maybe 5-10 minutes I forgot to update a file that I immediately fixed. I wonder if you updated in that small time window. If you log into OctoPrint, what version of OctoPod plugin do you see installed? Is it 0.2.3 or 0.2.4?
If you see 0.2.3 then a quick troubleshooting idea would be to uninstall the plugin and install it again. If you changed the plugin settings then take notes of your setup before uninstalling the plugin. Let me know if this helped. I'm at work now so have limited support. :(
Thanks,
Gaston

It still shows as 0.2.3 - I think it's because the zip it's downloading (https://github.com/gdombiak/OctoPrint-OctoPod/archive/0.2.4.zip) in setup.py lists the version as 0.2.3 but I really don't know what I'm doing with plugins on this system.

Gotcha. I will update that file then. I thought it was using https://github.com/gdombiak/OctoPrint-OctoPod/archive/master.zip.
Will let you know once done

Done. https://github.com/gdombiak/OctoPrint-OctoPod/archive/0.2.4.zip now has the proper version number.
Let me know if issue is solved. Thanks for letting me know this.
Gaston

Looks like that fixed it - thanks!


feat: support eslint ^9

feat: support eslint ^9

I'm not a maintainer here, but this doesn't seem to be enough - see the comments on issue #3699

Sorry, I didn't notice that there was already an issue here, I closed this PR.

Oh, sorry, I don't think you have to close it, but it does seem there's a bit more work than just bumping the compatible versions.

I believe this was obsoleted by #3759.


Documentation mistake in batch queries

"params:" is missing

you mean client.batch()? I do not think there's params prop

this: https://github.com/algolia/algoliasearch-client-js/tree/develop#batch-writes ? (develop branch)

Yes sorry, did the issue a bit in a hurry,
So it is in section : Multiple queries => Line 756

Right!


Copy input image as separate "current file"

This gets us ability to modify the displayed image on-the-fly.
Also, increased robustness against external file system operations.

Using variable App.image_tmp_filename

Decoupling the logical image (which lives somewhere on the file system) from the displayed image.


Add a vertical guideline option and 'besideAxis' positioner for tooltip

When tooltip is visible, a vertical guide line is also visible. This vertical guid line let users read current position very easily when the line chart is complex.
Example:
https://codepen.io/anon/pen/JOgQaY

@etimberg

I updated the code that uses helpers.aliasPixel.
I gave a little more thought about the horizontal guide line and I think it not that useful as a vertical guideline with a tooltip. Because the current tooltip shows the details of data points on certain x-axis value. If there is tooltip that shows details of data points on certain y-axis value, the horizontal guide might be worthy but it's currently not. What do you think?

A few feedback about the API:

should we call it guide or cursor since we use the term cursor in the docs?
it should handle both orientations automatically:

display vertical if tooltip.axis == 'x' or tooltip.mode == 'x'
display horizontal if tooltip.axis == 'y' or tooltip.mode == 'y'
display both if tooltip.axis == 'xy'

I would simplify the options for:

guideColor (or cursorColor) instead of verticalGuideBorderColor
guideWidth (or cursorWidth) instead of verticalGuideBorderWidth
position: 'guide' (or 'cursor') instead of position: 'besideAxis'

Then I would add the following option to override the automatic orientation

guideAxis: 'x'|'y'|'xy'|'auto': if undefined, equivalent to 'auto' (auto: select proper orientation based on tooltip.axis and tooltip.mode (see above)

@etimberg don't you think that this feature should be dissociated from the tooltip? (Could even be a new plugin, maybe). I'm pretty sure we will get requested to be able to display these guides without tooltip and I think it make sense to separate the implementation and options.
What do you guys think?

@simonbrunel I kinda like the idea of having a plugin that does it (could be internal). That way we could have things like follow the mouse, etc.
I think it could be fairly easy be done. @yjiq150 would you be interested in trying that?

Thank you for the suggestions. I agree that it's better to be independent from tooltip. I took the shortest path to implement and apply it to my personal project. I will try implementing it as you suggested, however it might take a while.

Closing due to inactivity


Is it possible to add listener to pasted img?

Is it possible to view a photo in popup using draft-js? I mean if Editor is in readOnly mode I wish I could add a click listener to my image and then show the picture as popup on whole page. So far, unfortunately, I have not found a solution on how to do it. If not, maybe feature?

e.target.src may be useful to you

@sos1ck did it solved your problem or did you found another solution ?


Inline Rename doesn't work for members

ref #3462
This is really just the old part of that issue
// Learn more about F# at http://fsharp.org
// See the 'F# Tutorial' project for more help.

open TestCS

type C() =
    member val ThisIsAProperty = 12 with get, set

[<EntryPoint>]
let main argv =
    let c = C()
    c.ThisIsAProperty <- 0
    0 // return an integer exit code

Rename on ThisIsAProperty only works at the declaration site.

Fixed by #3762


Merge volume flags implementation

Merge the implementations of --mount, --volume, --volumes-from, --tmpfs, the mount portion of --init, and image volumes together into one unified API. Conflicting volumes and superceding volume priorities should be handled correctly here.
As part of this, move all volume-handling code into a single file in pkg/spec, storage.go.
Also, add a fresh API entrypoint for generating everything necessary to create a Libpod container out of a CreateConfig, and start making many things in pkg/spec private. A single unified entrypoint lets us do extensive refactoring of the package and still not break any users, because the API remains the same.
There are still a lot of WIPs left in the code, but I will hopefully hit them all tomorrow.

Note to self: this needs testing, especially around where the volume flags interact.

Goconst and I are having some disagreements here, evidently

Alright, existing unit tests are moved over. I'm going to start writing new ones, plus some integration tests, then this should be good to merge.

Alright, this PR is unwieldly enough as it is.
I'm going to strip the WIP off and stop adding code now, with the exception of fixing tests.

@vrothberg @rhatdan @baude @TomSweeneyRedHat PTAL. I've created a real monster here, but the end result seems a lot more understandable and maintainable than existing code.

LGTM.

Alright, tests should go green now.
@rhatdan @vrothberg @giuseppe @TomSweeneyRedHat anyone want to give this a second LGTM?

It's green
@rhatdan @baude @TomSweeneyRedHat @vrothberg Someone want to push this one over the finish line?

LGTM, I'll push and we can adjust if necessary.

/lgtm


Update dev version following the patch release

As per title, following 1.6.1

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Return error in seccomp_filter

If a manifest's seccomp part contains an unknown syscall we now return an error to the runtime instead of disabling seccomp.

Agreed. Alternatively, we could use global string constants for those message.


Refactoring Stapfen::Worker - Logger, Config

After discussions, it was determined we should make a breaking
change which will address a few logging and configuration issues

Moved general logging to use ::Stapfen.logger

This is what the Stapfen gem should use for logging

Added the ability to specify a logger for every Stapfen::Worker
instance via the configuration block
Modified the configuration block to pass the worker instance
which allows flexibility with configuration but also uniformity
by putting all configuration in one place.
Modified the consume method to accept optional configuration
overrides so that client-specific settings can be passed or
changed
Unified the configuration for Stapfen clients and their
subscriptions
Refactored tests to be more readable and more easily processed
Added tests for all of Stapfen::Worker methods
Modified existing tests to pass with the new changes
Removed Stapfen::Logger, as Ruby's logger is now default

Bump the version for a breaking change?

@lsb @rtyler @jamescway Updated based on feedback

:+1:

I'm going to merge this, we can do little fixes here and there in followup commits before we release 3.0.0


piston-cli: 1.2.2 -> 1.3.0

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 121448 run on x86_64-linux 1

1 package built:

piston-cli


zigHook probably shouldn't rely on -Dcpu=baseline

Describe the bug
https://github.com/NixOS/nixpkgs/pull/242397 introduced the zigHook.
Currently, it aims for reproducibility by passing the -Dcpu=baseline flag, as shown here:
https://github.com/NixOS/nixpkgs/blob/a85a699e40708b452d36c70725396ff67dc48e66/pkgs/development/compilers/zig/setup-hook.sh#L23
With the current zigHook, I have two concerns:

Is it possible to cross-compile Zig packages using Nix?

Cross-compiling poop:
$ git describe
22.05-pre-177775-ga157ed02d34
$ nix build .#pkgsCross.aarch64-multiplatform.poop
error: builder for '/nix/store/9zzp86jir6bc64vv3b9h7i69ams4kaix-poop-aarch64-unknown-linux-gnu-0.4.0.drv' failed with exit code 1;
       last 10 log lines:
       > Hunk #6 succeeded at 530 (offset -8 lines).
       > Hunk #7 succeeded at 647 (offset -8 lines).
       > patching file src/progress.zig
       > updateAutotoolsGnuConfigScriptsPhase
       > updateAutotoolsGnuConfigScriptsPhase
       > configuring
       > no configure script, doing nothing
       > building
       > build flags: -Doptimize=ReleaseSafe -Dcpu=baseline
       > error: AccessDenied
       For full logs, run 'nix log /nix/store/9zzp86jir6bc64vv3b9h7i69ams4kaix-poop-aarch64-unknown-linux-gnu-0.4.0.drv'.

I chose poop as it's a small and pure Zig project maintained by one of the Zig members. waylock might also make a good candidate for a package that makes use of C interop. Not too sure if this build issue is caused by the current behaviour of zigHook, however.

Can users pass arbitrary targets to Zig packages built with Nix, or would the default flag cause a compile error?

Example of passing a new baseline to a build system on top of an existing one:
$ zig init-exe
info: Created build.zig
info: Created src/main.zig
info: Next, try `zig build --help` or `zig build run`
$ zig build -Dcpu=baseline -Dcpu=x86_64_v4
error: Expected -Dcpu to be a string, but received a list.
<omitted>

Expected behavior
I'll quote @andrewrk's comment at https://github.com/NixOS/nixpkgs/issues/185665#issuecomment-1416592467:

I think a better way would be accessing the desired target architecture, operating system along with minimum/maximum OS version, and ABI, along with potentially the glibc version, from nix, and then specifying these via the standard -Dtarget option. I'm happy to assist in getting this working.

Additional context
I think the following Guix patch by ekaitz is a great example: https://issues.guix.gnu.org/60889.
In the future, https://github.com/ziglang/zig/issues/14281#issuecomment-1624220653 should be implemented so one can pass --override-host-target <target> and --override-host-cpu <cpu> instead.
Notify maintainers
@AndersonTorres for writing the hook?

As far as I remember, many of those things were documented on the huge comment I wrote - including the links you are citing.
What is exactly the matter?

Ah, sorry, I must have missed the comment here:
https://github.com/NixOS/nixpkgs/blob/6acf0bf645f8826940bc7aca9efd46fbdae69eae/pkgs/development/compilers/zig/setup-hook.sh#L3-L21

Hopefully they [the necessary features] will be implemented in future releases of Zig. When this happens, this flagset should be revisited accordingly.

With this in mind, I guess my issue is kind of meaningless because it's true that the code will have to change in the foreseeable future and people can worry about it then.
But sure, let me rephrase what I was trying to say. I think it would still be more preferable to properly pass a target triple than relying on -Dcpu=baseline. I'm not quite sure how cross-compilation works on Nix (still trying to figure out https://nixos.org/manual/nixpkgs/stable/#chap-cross), but wouldn't -Dcpu=baseline cross-compile use the buildPlatform instead of the hostPlatform as the target and thus always fail?

Indeed I need to look at this cross-compilation issue too, because I don't remember if there is an explicit setting like -Dhost-cpu and -Dtarget-cpu.
There is the issue of reproducibility too. This set of default flags fixed some nasty miscompilations, as explained in the links.

Assuming that cross-compilation is broken (like I said, I'm not completely sure but it seems like it?), the way to fix it would be make sure the correct target is provided such that compiling to Aarch64 Linux would make the hook pass -Dtarget=aarch64-linux. Always specifying the correct -Dtarget value would remove the assumption that the host is always the same as build platform.
Guix's zig-build-system (mentioned above) does this and I think it looks great.
And if one wants to be more specific (say, targeting a dev board using A53 cores), one can just do -Dtarget=aarch64-linux -Dcpu=cortex_a53.
Also, just found https://github.com/flyx/Zicross and they also seem to use -Dtarget for cross compilation.

Zig author recommends passing -target over -mcpu=baseline here as well
https://ziggit.dev/t/exe-files-not-interchangeable-among-identical-linux-systems/2708/6?u=cloudef

I ended up replacing nixpkgs hook here https://github.com/Cloudef/zig2nix/commit/fd7931adc3e12e5458204d28ece7b2d38173c0a0
The default flags are also problematic as you can't override them. For zig it seems to be a error to pass multiple -Doptimize so you can't build package with a different release mode for example.

Still broken?


qtpass: 1.1.0 -> 1.1.1

Things done

[x] Tested using sandboxing (nix-build --option build-use-sandbox true or nix.useSandbox on NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

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

Updates qtpass and fixes the current installation method. It further installs the desktop file and application icon.

@hrdinka could you explain what you'd like the make install to do differently?
Thanks in advance. .

@annejan make install currently only copies the qtpass binary to $PREFIX/qtpass. It would be great if it could create a FHS structure below $PREFIX and include auxiliary files like qtpass.desktop and the icon files. Just like this nix derivation does:
qtpass -> $PREFIX/bin/qtpass
qtpass.desktop -> $PREFIX/share/applications/qtpass.desktop
artwork/icon.svg -> $PREFIX/share/icons/hicolor/scalable/apps/qtpass-icon.svg # better call it qtpass.svg and change the name in the desktop file as well

I don't use the package but it looks okay to me; if you have tested it, feel free to merge I guess.


All CTD cards for the example gene set do not produce any results

We need to coordinate with exRNA to find an example set of genes that works for most DCCs


GH-38860: [C++][Parquet] Using length to optimize bloom filter read

Rationale for this change

Parquet supports a bloom_filter_length in 2.10[1]. We'd like to using this length for read.
The current implemention [2] using the code below:

Using a "guessed" header length to read the header. The header is likely to be 40B, but we use a larger value to avoid it evolves
From the header, we get the bloom filter length, and load it from input.

Now, we can directly load the whole bloom-filter, without reading twice. We shouldn't remove the stale code because we need to read the stale file.
We also need to generate a new parquet-testing file ( I can do this ASAP )
[1] https://github.com/apache/parquet-format/blob/master/src/main/thrift/parquet.thrift#L824
[2] https://github.com/apache/arrow/blob/main/cpp/src/parquet/bloom_filter.cc#L117
What changes are included in this PR?

[x] Support Basic read with bloom_filter_length
[x] Enhance the JsonPrinter
[x] testing

Are these changes tested?

[x] testing using parquet-testing

Are there any user-facing changes?

Closes: #38860

Also cc @emkornfield

@pitrou I've resolved the comments, would you mind take a look?


Add parameter trackBy on form type select.

With this feature, it's now possible to set like value an object in titleMap and add its property what we want too.
trackBy parameter used to specify the fields on which we want to compare this the model.
Ex:
scope.thing = { id: 2, a: 1, b: 2 };

scope.schema = {
  "type": "object",
  "properties": {
    "thing": {
      "title": "Thing"
    }
  }
};

scope.form = [{
  key: "thing",
  type: 'select',
  titleMap: [{
    id: 1, name: 'abc', value: { id: 1 }
  },{
    id: 2, name: 'def', value: { id: 2 }
  },{
    id: 3, name: 'ghi', value: { id: 3 }
  }],
  trackBy: 'id'
}];

Coverage increased (+0.1%) to 70.91% when pulling 09bd5312f0a324fae77dc89f5e53edc2f401c9c8 on Fridus:feature-select-options-trackBy into e2734c8ffe75fe6ac3e12a5bd48c0bb96f11d998 on Textalk:development.

Hi @Fridus, nice PR! Thank you for that :+1: Always nice to see tests as well :)

@davidlgj :) When will you make a new release ?

Hmmm... the plan was to get one out by mid august. The thing is that I have begun working on a new "builder". So it's a big rewrite, but it will make it a lot better. But on the same hand it's been a long time since last release.
So I actually don't what to do. The new "builder" stuff in development branch isn't finished yet, but its supposed to be backwards compatible so in theory  it should work, but I don't have enough test to be confident it does. Maybe I could try to make a beta release soonish and if that works make a proper release...

I ask you this because I need this feature fairly rapidly for a project :)

@Fridus just made a release! hope it works for you.

Hi @Fridus, I had to revert you commit. It broke the select when not using trackBy, see #462, #471, #473
It looks like using select as in combo with trackBy is not supported. Also I now noticed that two of the tests lacked a done callback, so they seem to work but in fact fail. I didn't have time to fix it so I did a revert.

Hi @davidlgj , I'll work on it when I have a little more time ;)

:+1:
mån 13 jul 2015 10:55 Florent<EMAIL_ADDRESS>skrev:

Hi @davidlgj https://github.com/davidlgj , I'll work on it when I have
a little more time ;)
—
Reply to this email directly or view it on GitHub
https://github.com/Textalk/angular-schema-form/pull/418#issuecomment-120855584
.


When are characters billed? At export? In tuning?

I can't find an answer to this.  When are characters actually billed?  I'm mainly using Speech Studio, and I'm worried that every time I modify and then play back my tuning adjustments (like to fix incorrect pronunciations, pitch, etc.) I'll be billed.  And will I be billed for the entire TXT file I'm working on for each play, or just the characters I'm playing? The pricing documentation doesn't address this at all.

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

ID: e873515a-55f7-ecdf-37dd-9b5dbb13c211
Version Independent ID: f8b9132b-c867-cd3a-c772-eaa87108711b
Content: Text-to-speech overview - Speech service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/text-to-speech.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @eric-urban
Microsoft Alias: eur

@sharonhuston
Thanks for your feedback! We will investigate and update as appropriate.

@sharonhuston
Based on the services you utilise, you get billed. You are charged for the Speech service based on how many transactions or characters you utilise. Depending on the pricing tier you are using, you may be charged for a certain number of transactions or characters. For instance, the free pricing tier for real-time API only permits 20 transactions every 60 seconds, whereas the standard pricing tier permits 200 transactions every second.
Regarding your worry that you would be charged each time you edit and replay your tuning modifications in Speech Studio, it is unclear from the documentation whether you will be charged for every play or simply the characters you are portraying.
I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1

@sharonhuston
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


German or other another language series can not be played.

Hi I have tested the app yesterday briefly and could determine that some series could not be played. Mainly German or French albums can not be played, English or original series could be played. Maybe there is a conflict because the series with their respective language are packed in subfolders but this is just a pure guess.
Not playable means in the case it comes to a loading screen or the jump to the consequence but after that a black screen occurs and this remains even after several minutes waiting. The episodes that can be played also go normally in the jump to the episode, but these can be played.
I hope I could help.

the error is in the crunchyroll api, only the vod sub, and dub eng work... I'm going to try to migrate from the api to the new version that uses the new crunchyroll page,
Maybe it will take a few days.

okay thx for your help :)


Time to upgrade to netty 4.0?

Netty 4.0 has been out for a while. And I actually built traccar against it and everything appears ok. You might want to consider upgrading to take advantage of the new features/fixes.

Can you send me a pull request? What are the new features? As for bug fixes, many big projects are using Netty 3 and it's still supported.
There is also Netty 5. Does it makes sense to upgrade straight to 5?

You are right. I actually just tried 5.0.0.Alpha2 and it worked too. Here are the noteworthy changes:http://netty.io/wiki/new-and-noteworthy.html I guess some traccar code can be refactored simplier with the new version (without refactoring, the current code is still compatible though).
Big projects might be more tied to old versions for that it naturally use more APIs making it more risky to upgrade.
I don't have a clean fork to create a pull request but the changes are only 2 lines in  traccar/pom.xml
:
    <dependency>
        <groupId>io.netty</groupId>
        <artifactId>netty-all</artifactId>
        <version>5.0.0.Alpha2</version>
    </dependency>

I take that back. My previous build against netty 4 was not clean.
Now I've cleaned and rebuilt it, if failed. Most of the failures look like related to package name change, and ChannelBuffer class name change in netty 4.
This doesn't look trivial so I'll leave it with netty 3, unless someone takes on the upgrade.

I plan to update eventually, but I want to wait till stable version of Netty 5 is out.

Traccar has been migrated to Netty 4.1.


Reuse the endpoint of the checkpointed container when restore

Docker-DCO-1.1-Signed-off-by: Hui Kang<EMAIL_ADDRESS>

@boucher This PR fixes the network endpoint problem when restoring a container. The endpoint should be reused by a checkpointed container so that the network resources (e.g., iptable rule) will not be changed after restoring. Please review if it fits into your branch. Thanks.

If I run this code, and then checkpoint and restore a container, it still can't access the network. I believe this is related to the issue I filed here: https://github.com/docker/docker/issues/14027
(To test, I just exec'd into the restored container and tried ping'ing google.com) Are you actually able to use the network after a restore?

@boucher Update the patch for 1.8.0-dev, but the problem you described still exists. I will look into this issue these days.


add sequence doc for 0.8

What type of PR is this?

[ ] Enhancement
[ ] Displaying
[ ] Typo
[x] Doc Request

Which issue(s) this PR fixes:
issue #
https://github.com/matrixorigin/matrixone/issues/6590
What this PR does / why we need it:

fixed

Fix lint


Matplotlib musllinux aarch64 wheel

Hello, can anyone do the matplotlib python 12 wheel?

Hi there @dobakszilard 👋
I think this is a question for the matplotlib project?
Please note, peeking at pypi, they already publish quite a lot of wheels.
../Frenck


Increase test coverage

This is my intent (choose one)

[x] I want to provide or change a feature

The problem
Not all Hops packages are thoroughly tested.
Proposed solution
Add tests for:

build
build-config
cli
express
lambda
pwa
redux

We now have a basic set of integration tests for these packages and will add more when time permits.


Don't strip the OSX CLI binary

Once stripped, the binary will fail to run, giving immediate segfaults

retest this please


Trouble running simv and verilator

I am two facing two issues:

I am able to generate program.hex, iccm.hex, dccm.hex and mailbox.hex but when I run the simv, the simulation hangs indefinitely. I have copied the ecdsa_secp384r1.exe and doe_test_gen.py files from [https://github.com/chipsalliance/caliptra-rtl/issues/120]. I get warnings that are in the attached file below . Please let me know if i am missing any files. I am running this command from CALIPTRA/caliptra-rtl-main/run
sim.log

The command has generated empty iccm.hex and mailbox.hex. The dccm.hex files are however different from the ones generated from https://github.com/chipsalliance/caliptra-rtl/blob/48012ef7c254308052a6d90918abb800d635e1da/src/integration/test_suites/iccm_lock/dccm.hex. I have attached the dccm.hex file that's generated from my environment.
dccm.txt (uplaoding it is .txt as .hex is not supported )

I am not build any verilator related build files after using command make -C ${CALIPTRA_WORKSPACE}/scratch/agurram/verilator/06302023/run -f ${CALIPTRA_ROOT}/tools/scripts/Makefile TESTNAME=${iccm_lock} debug=1 verilator > verilate.log
I have attached the logs :verilate.log
I am running this command from /CALIPTRA/scratch/agurram/verilator/06302023/run

I have also attached the tree to show which directories I'm running from: tree.log
My paths for ROOT , WORKSPACE and PATH are  :
export W_ROOT=pwd
export PATH=$PATH:/ax_tools/Others/toolchain/riscv/bin
export PATH=$PATH:/usr/bin
export PATH=$PATH:/ax_tools/Others/gcc/8.2.0/bin
export PATH=$PATH:/usr/bin/verilator
export CALIPTRA_WORKSPACE=$W_ROOT/
export CALIPTRA_ROOT=$W_ROOT/caliptra-rtl-main/
Please let me know if i need provide any more details.

In regards to (2), we have CI running with verilator
Here's a link to a github runner: https://github.com/chipsalliance/caliptra-rtl/actions/runs/5533741342/jobs/10097868907
Here's a link to the github runner commands: https://github.com/chipsalliance/caliptra-rtl/blob/main/.github/workflows/build-test-verilator.yml
As a first pass, can you run the smoke tests provided to make sure the environment is setup properly before trying to use other hex files?  Hopefully this will help ensure that the tooling and environment variables are all setup properly before trying to use different hex files

Will try that Howard.
We also another issue when integrating ICCM and DCCM  SRAMs to Caliptra.

Do we use the el2_mem_export interface from Caliptra top module port declaration or that port is only for tb.
If el2_mem_export is the one using which we should integrate the iccm and dccm memory can we refer the caliptra_veer_sram_export.sv as is to integrate the srams.

If point 2 is valid then on integrating the iccm and dccm sram in similar fashion we are getting the following error:
Error-[SE] Syntax error   Following verilog source has syntax error :     /svc/test/riscv_core/veer_el2/rtl/el2_param.vh",   18: token is 'pt'   parameter el2_param_t pt = '{
^

Yes, use the el2_mem_export interface.  the caliptra_top_tb_services.sv has some functions that help preload all the hex files into the proper memory structures.
The srams are here: https://github.com/chipsalliance/caliptra-rtl/blob/61fb5bd9eff399947f6e8621bdb1de03ff06e1b8/src/integration/tb/caliptra_top_tb_services.sv#L1040-L1043

The defines to all srams are here: https://github.com/chipsalliance/caliptra-rtl/blob/61fb5bd9eff399947f6e8621bdb1de03ff06e1b8/src/integration/tb/caliptra_top_tb_services.sv#L1225-L1232
Preloading is done here: https://github.com/chipsalliance/caliptra-rtl/blob/61fb5bd9eff399947f6e8621bdb1de03ff06e1b8/src/integration/tb/caliptra_top_tb_services.sv#L996-L998

So that error looks familiar - I filed this a while back: https://github.com/chipsalliance/caliptra-rtl/issues/33, and this should have made it in: https://github.com/chipsalliance/caliptra-rtl/commit/a5fb21b3fde3e2f6c03e1a640e29b9a0bade7339

Can you confirm if you're using the latest from main?
Basically can you confirm if there is a import el2_pkg::*; prior to el2_param
See: https://github.com/chipsalliance/caliptra-rtl/blob/main/src/riscv_core/veer_el2/rtl/el2_veer.sv#L24-L26

will double check that. Thanks
Can you please look into the issue [1] from the top. Regarding simv getting hung indefinitely. I have added the sim.log in the issue above.

I'm not 100% familiar with that test, but from the logs I see:
No argument provided for CLP_MAX_CYCLES, defaulting to    20000000
DCCM pre-load from 50000000 to 5001ffff
DCCM pre-load completed
ICCM pre-load from 40000000 to 4001ffff
ICCM pre-load completed
MBOX pre-load from 00000000 to 00008000
MBOX pre-load completed

Warning-[STASKW_CO] Cannot open file
/User_data/home/agurram/Desktop/CALIPTRA/caliptra-rtl-main//src/integration/tb/caliptra_top_tb_services.sv, 529
  The file 'doe_test_vector.txt' could not be opened. No such file or
  directory.
  Please ensure that the file exists with proper permissions.

Taking a look at caliptra_top_tb_services.sv, 529
https://github.com/chipsalliance/caliptra-rtl/blob/61fb5bd9eff399947f6e8621bdb1de03ff06e1b8/src/integration/tb/caliptra_top_tb_services.sv#L521-L529
This seems to imply that python  doe_test_gen.py needs to run to generate doe_test_vector.txt
Now, looking at @calebofearth comment in https://github.com/chipsalliance/caliptra-rtl/issues/120#issuecomment-1619126000

If you are running the simulation in a tool other than verilator, you should also copy doe_test_gen.py and ecdsa_secp384r1.exe into the test run directory.

I do see that you mentioned

I have copied the ecdsa_secp384r1.exe and doe_test_gen.py files

@ax-ag16 : can you confirm where these files are copied to?
It would also be good if you can add a line prior to the python script to check what it thinks the working directory is
+         $system("pwd");
         $system("python doe_test_gen.py");

If these directories are different, then move it to the one that pwd prints out and see what happens

I pulled the latest RTL and I'm getting these syntax errors when running the simv.
**Error-[DPI-DIFNF] DPI import function not found
/User_data/home/agurram/Desktop/CALIPTRA/caliptra-hw//src/integration/test_suites/libs/jtagdpi/jtagdpi.sv, 34
The definition of DPI import function/task 'jtagdpi_create' does not exist.
Please check the stated DPI import function/task is defined, and its
definition is either passed in a source file at compile-time, or provided in
a shared library specified using the LRM Annex-J options at run-time.
Error-[DPI-DIFNF] DPI import function not found
/User_data/home/agurram/Desktop/CALIPTRA/caliptra-hw//src/integration/test_suites/libs/jtagdpi/jtagdpi.sv, 38
The definition of DPI import function/task 'jtagdpi_close' does not exist.
Please check the stated DPI import function/task is defined, and its
definition is either passed in a source file at compile-time, or provided in
a shared library specified using the LRM Annex-J options at run-time.**
Do I need any tool for use  DPI functions?

@ax-ag16 - You'll need to pull in https://github.com/chipsalliance/caliptra-rtl/blob/61fb5bd9eff399947f6e8621bdb1de03ff06e1b8/src/integration/test_suites/libs/jtagdpi/jtagdpi.c
In parallel, @mkurc-ant - can you take a look at this?
i see that jtagdpi is called out under verilator, but not for vcs
https://github.com/chipsalliance/caliptra-rtl/blob/61fb5bd9eff399947f6e8621bdb1de03ff06e1b8/tools/scripts/Makefile#L169-L171

I pulled the filed you had mentioned but the libs/jtagdpi in test_suites has jtagdpi.c, jtagdpi.sv, jtagdpi.h files. Its still giving me the same error.

I'm not an expert in dpi, but just double checking - did you make sure the object was built and linked properly?
@calebofearth - did you by chance run into this with internal regression testing?

I already had the said jtagdpi.* files when i created the object files.
I added the jtagdpi and tcp_server to COMP_LIB_NAMES in Makefile and when tried to recompile.. got another compile error that it couldn't find
#include <svdpi.h>
Please let me know if i need any files. Thank you!

I'm not an expert in dpi, but just double checking - did you make sure the object was built and linked properly?
@calebofearth - did you by chance run into this with internal regression testing?

I have not gotten the interactive JTAG debugger test (openOCD) working in our internal flow, but I was able to get it compiling on our internal VCS flow by adding:
https://github.com/chipsalliance/caliptra-rtl/blob/e40aae85b50bd54a732c65da1d8aa49c98d46369/src/integration/config/compile.yml#L77-L93
In the background, this produces a gcc command:

gcc -m64 -fPIC -Wall -g  -Wno-unused-variable -Wno-unused-function -DVCS
-I/mypath/Caliptra/src/integration/test_suites/libs/tcp_server
-I/mypath/Caliptra/src/integration/test_suites/libs/jtagdpi
-I/mypath/synopsys/vcs-mx/2020.12-SP2-7/linux64/include
-shared
-c /mypath/Caliptra/src/integration/test_suites/libs/tcp_server/tcp_server.h
/mypath/Caliptra/src/integration/test_suites/libs/tcp_server/tcp_server.c
/mypath/Caliptra/src/integration/test_suites/libs/jtagdpi/jtagdpi.h
/mypath/Caliptra/src/integration/test_suites/libs/jtagdpi/jtagdpi.c
gcc -m64 -fPIC -shared   -o /mypath/scratch/cwhitehead/libs/vcs/R-2020.12-SP2-7_Full64/integration_lib/caliptra_top_tb/dpi/lib_dpi.so
/mypath/scratch/cwhitehead/libs/vcs/R-2020.12-SP2-7_Full64/integration_lib/caliptra_top_tb/dpi/tcp_server.o
/mypath/scratch/cwhitehead/libs/vcs/R-2020.12-SP2-7_Full64/integration_lib/caliptra_top_tb/dpi/jtagdpi.o

@calebofearth
The first error i got while generating simv is

I commented out the IFDEF CALIPTRA_DEBUG_UNLOCKED for compiling purposes, but I got this error

Please let me know if there is any mode to set to get past this JTAG error?

The fix for your first issue was merged to main as part of https://github.com/chipsalliance/caliptra-rtl/pull/154 (commit https://github.com/chipsalliance/caliptra-rtl/commit/807de2b19b9a799e1063bdd3b96fcf480f473017 specifically has this fix).
For more context, take a look at https://github.com/chipsalliance/caliptra-rtl/issues/147
For your second issue, have you tried running the gcc commands I posted above to compile the DPI library?
If that does not work, you can always get the system to compile by just commenting out the jtagdpi:
https://github.com/chipsalliance/caliptra-rtl/blob/e40aae85b50bd54a732c65da1d8aa49c98d46369/src/integration/tb/caliptra_top_tb.sv#L1026-L1039
Eventually you should try to get the DPI running in your system though.

I pulled the latest version and i am still facing the first issue.

Please let me know if i should be setting any mode to enable/disable DEBUG_UNLOCKED ?

Hi, I see what happened, the fix (made in MSFT internal repo) didn't sync back to the dev-msft branch correctly.
I have a fix pending: #158

Hi, I am able to get past errors and compile simv but when run ./simv , my simulation still hangs after pre-loading DCCM, ICCM, MBOX files. I have attached the log file .
sim.log . I am able to generate doe_test_vectors_all.txt and doe_test_vector.txt. Can you please help us get past this point?

This sim.log doesn't show much useful debug info - probably need to look at waves to diagnose.
Which firmware test is used to build program.hex for this run?
Is the clock alive?
Does the VeeR core come out of reset?
Are there any register accesses on the AHB bus?Instruction accesses on the IFU interface? Is there an NMI (You can find the mcause/mscause registers inside the VeeR hierarchy - what is their value?)

Are there any more updates on this? We will close the issue soon due to inactivity unless there are further questions.


Env variable interpolation with DATABASE_URL does not work

Setup
Versions

Rust: rustc 1.61.0-nightly
Diesel: v1.4.8
Database: Postgresql
Operating System Pop!_OS 22.04

Feature Flags

diesel: cargo install diesel_cli --no-default-features --features postgres

Problem Description
What are you trying to accomplish?
Trying to interpolate environment variables for the DATABASE_URL:
# .env

POSTGRES_USER=username
POSTGRES_PASSWORD=password
POSTGRES_DB=engine

DATABASE_URL="postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@localhost/${POSTGRES_DB}"

What is the expected output?
Using the dotenvy crate (v0.15.1) the output is:
use dotenvy::dotenv;
use std::env;

fn main() {
    dotenv().ok();
    println!("DATABASE_URL={}", env::var("DATABASE_URL").unwrap());
}

DATABASE_URL=postgres://username:password@localhost/engine

What is the actual output?
Running diesel setup doesn't work:
Creating database: $%7BPOSTGRES_DB%7D
connection to server at "localhost" (::1), port 5432 failed: FATAL:  password authentication failed for user "${POSTGRES_USER}"

Checklist

[x] I have already looked over the issue tracker  and the disussion forum  for similar possible closed issues.

[x] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)
[ ] This issue can be reproduced without requiring a third party crate

Thanks for opening this issue. As your code snippet does not contain any diesel related code I would like to understand why you filled this issue here instead of in the dotenvy issue tracker?

Hi @weiznich,
Thanks for answering my issue. I am using Diesel 1.4.8, what do you mean by using a version "compiled from the master branch"?
Also I first tried interpolating variables with the dotenv crate then I saw that you were using the most recent dotenvy so I modified my post according to that and it seems to work.
I just saw that the diesel_cli v1.4.1 uses dotenv instead of dotenvy: https://crates.io/crates/diesel_cli/1.4.1/dependencies is it normal?

As you already noticed does the master branch contain many changes compared to the 1.4.1 release. This is expected as development needs to happen somewhere. These changes include the switch from dotenv to dotenvy. That's why I'm asking if that also happens with either a diesel-cli version compiled from the master branch via cargo install diesel_cli --git https://github.com/diesel-rs/diesel or by installing the 2.0.0-rc.0 version by crates.io

All right thanks I understand now (didn't know you could install directly from git).
It works with diesel 2.0.0-rc.0!

Thanks for reporting back


Crashs whenever I click the fake rate button.

Please fix this issue.
On Android.

send crashlog

Likely a duplicate of #4


Redemptions not trigger

Chat Connected, Tested with a message. Triggered
Tested against redemption, not triggered.

Update:
I ran the trigger test by redeeming something in chat. Didn't work
Tested it with transmitter.html, worked
Retested it with trigger by redeeming in chat again, worked.
No idea why. Leaving issue open in case of actual problem.


@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/105307
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" ba47df8a8861063c252a721c54962123d262bca3
git push origin v0.3.0

Also, note the warning: This looks like a new registration that registers version 0.3.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.


How to authorize the relations controller?

What part of relations are public? Are all relations public (not really sure there's any security risk returning related IDs?) Of course if a relation is for a member, you'll just get an ID and then you'll need to request the member info from the members endpoint - for which you'd need to be authorized to get.
So ... should the relations controller just be public?

is anything in the rest api public? - imo it is all behind Auth  - if you mean who can see relations - then yeah everyone could see the IDs of the related items and the auth would kick on the individual controller

Yup that's what i means. I'm changing the auth, but i guess with auth policies it will be up to the user to decide who has access to what.
The other part of the relation auth is that different users have access to different sections, etc... Currently that auth isn't enforced on the REST API but it will be, so for relations API, it will continue by default to just auth any authenticated user but if that user attempts to access member data (for example), they will need to have access to member data.

Sounds good - can we include that info in the error message? - so the user can tell that is why the call is failing - due to the user not having access to certain data - or is it simply the generic "not-allowed" response?

adding that info to the response is a security no-no. It will simply give a 401 unauthorized response


need a setup script to run krustlet on a virtual machine

For demos/workshops, it would be great if we had a simple setup script to run krustlet in a VM similar to how kubernetes had its own vagrant VM for development environments. Bonus points if we could emulate kind/minikube, but a setup script would be a good first step.

https://github.com/bacongobbler/krustlet-on-azure is a good starting point. After the user generates an SSH key and a Service Principal, they only need to click a button to create a cluster with Krustlet installed.

https://github.com/deislabs/krustlet/tree/master/contrib/azure

https://github.com/deislabs/krustlet/tree/master/contrib/azure


UnicodeEncodeError: 'latin-1' codec can't encode character '\u2713' in position 0: ordinal not in range(256)

This issue can be fixed by prepending the babs-check-setup command with:
export LC_ALL=en_US.UTF-8
set PYTHONIOENCODING=utf-8
(/dartfs-hpc/rc/home/j/f003z4j/miniconda3/envs/physio/babs) [f003z4j@n09 my_BABS_project]$ babs-check-setup \

--project-root ${PWD} \
--job-test

Will check setups of BABS project located at: /dartfs-hpc/rc/home/j/f003z4j/babs_demo2/my_BABS_project
Will submit a test job for testing; will take longer time.
Below is the configuration information saved during babs-init in file 'analysis/code/babs_proj_config.yaml':
type_session: multi-ses
type_system: slurm
input_ds:
$INPUT_DATASET_#1:
name: BIDS
path_in: https://osf.io/w2nu3/
path_data_rel: inputs/data/BIDS
is_zipped: false
container:
name: toybidsapp-0-0-7
path_in: /dartfs-hpc/rc/home/j/f003z4j/babs_demo2/toybidsapp-container
Checking the BABS project itself...
Traceback (most recent call last):
File "/dartfs-hpc/rc/home/j/f003z4j/miniconda3/envs/physio/babs/bin/babs-check-setup", line 8, in
sys.exit(babs_check_setup_main())
File "/dartfs-hpc/rc/home/j/f003z4j/miniconda3/envs/physio/babs/lib/python3.9/site-packages/babs/cli.py", line 296, in babs_check_setup_main
babs_proj.babs_check_setup(input_ds, args.job_test)
File "/dartfs-hpc/rc/home/j/f003z4j/miniconda3/envs/physio/babs/lib/python3.9/site-packages/babs/babs.py", line 666, in babs_check_setup
print(CHECK_MARK + " All good!")
UnicodeEncodeError: 'latin-1' codec can't encode character '\u2713' in position 0: ordinal not in range(256)

Thank you Michael for reporting this issue + suggested way to get around it! I'll add to the docs (example walkthrough + babs-check-setup)


Lets Talk About a Place for CanComponents

This is a good Example for a Can Component that is usefull for many People we should create a Community Place for listing such Components
my suggestion is lets do a awsome list

https://github.com/sindresorhus/awesome

I don’t think we’ll take on maintaining a list, but if you want to contribute to that project, go for it!


End to end tests

This adds a single end-to-end test for user login. It also updates several of the scripts-to-rule-them-all, including test and update.
Travis integration to come.

Oh, this depends on this one. We'll need to merge that first.

@briandds yup, fixed.


Help - layout and features descriptions

Available layouts aren’t the same as those in Help (when ? is clicked). Specifically help refers to CoSE coming from chilay (the server side) but I don’t see any layouts that would be produced by that library.

Again in Help under expand-collapse, explanation should be changed to use “complexes” instead of “compound-nodes” since complexes are the only compound node type that is expanded and collapsed (not compartments). Btw, I don’t understand when compartments aren’t allowed to be collapsed.

updated in c4a0e23cd9ba493430d3a50a818a445176b9eeda


auto action mail - add variables to subject

Swedavia is requesting that the subject in auto generated mail contains: resourcename, alert rule and ticketID. Similar to the resolved alert mail which is
Alert Resolved for entity: "resourcename", Alert Rule 'Alert rule name', Ticket: '11111'
In the short run maybe default subject would be similar to the above and can be overruled while creating the auto action and in the long run there is a set of varibles that can be used while creating the auto action.

Hi @Jarnstrom - Thank you for your feedback. Since this channel is more for driving improvements towards MS Docs, could you provide us with a URL of the documentation that your feedback is most applicable to? That way, we're able to locate the right team that's better suited to address your feedback.


ARROW-2342: [Python] Allow pickling more types

Several types (bool, timestamp with a non-None timezone, floats) were unpicklable.
Based on PR #1778.

Appveyor build: https://ci.appveyor.com/project/pitrou/arrow/build/1.0.218


Add provider lookup tracing category to our TRACE api

One area that the TRACE api (available via the enable-trace option) has a gap in it.  Specifically it does not currently trace provider lookup events, which, as a complex syntax is somewhat ripe for enhancement.
The request here is to:

Add a new trace category name PROVIDER
Augment the provider lookup path to output trace information when parsing provider query strings and illustrating what provider they resolve to.

This is in pursuit of aiding the debugability of creating new providers.
This should be useable during any provider creation, and may benefit from being implemented as a stacked provider (or perhaps a shim between the provider call out functions

may benefit from being implemented as a stacked provider

Can you please provide a pointer to documentation of this feature (what is a stacked provider, how to register, use, implement it), @nhorman ?
Second question: Does this pertain only to lookup operations or any provider interaction? The latter would be required to debug into provider-triggered problems. Without this complete tracing capability, a provider will always have to add its own tracing capabilities, like for example in oqsprovider.

There is no documentation as such.  by stacked provider the only thing I mean to say is that a provider implementation could be created to act as a pass through to the real provider such that it logged a trace message, then called the underlying provider implementation.  That may be overkill however.
It would be useful if you could enumerate specific events you would like to see logged in pursuit of this

a provider implementation could be created to act as a pass through to the real provider such that it logged a trace message, then called the underlying provider implementation.

This is a good idea. Just not sure how to implement that, given all providers are treated "equally", i.e. loaded when listed in openssl.conf. This somehow would mean the tracing provider would be the only one listed and it would need to be passed a parameter what other provider it should load in turn. On UNIX'ish systems I'd have an idea how to do that; no idea on Windows, let alone statically built systems, though... Another topic where @levitte may have suggestions (?)

yeah, I think actually creating a "real" tracing provider is probably more effort than its worth.  more likely what I would look to do (my opinion only) would be to, in provider_init, allocate two provider structs when tracing was in use, and repoint all the provider functions to the "tracing" functions, which do nothing but but print a tracing message that is informative, and then calls  the "real" provider function

yeah, I think actually creating a "real" tracing provider is probably more effort than its worth. more likely what I would look to do (my opinion only) would be to, in provider_init, allocate two provider structs when tracing was in use, and repoint all the provider functions to the "tracing" functions, which do nothing but but print a tracing message that is informative, and then calls the "real" provider function

That'd be very good (and generic). Even better would be output of the return code/value, too. Is there a file containing all these calls so I may try to do this? Or are these calls split into different locations? Arguably much better than putting tracing in all provider(s)...

call assignment is handled in a huge case statement in the provider_init function if you would like to look.  I've been investigating this as well, so i'm happy to lend a hand here

i'm happy to lend a hand here

That'd be great! My own "spot check" investigation led me to some very sad result, namely that the calls into these provider function(array)s are "all over the place", see e.g., for gen_settable_params (and we've got dozens of these functions). Thus, indeed if there'd be a single place (e.g., in init) where they all could be replaced/wrapped with "tracing" variants) in one go would be perfect -- but still, it's many (26 for key management alone; 13 for KEM; 32 for sigs; etc.)

the calls themselves are indeed all over the place, and so we should not implement tracing at the call sites.  instead, what we should do, given that the calls are made through function pointers, is to replace the "real" functions they point to with "shim" functions that do the trace output, then call the providers "real" function pointers.  That way we only have to assign the trace functions once at assignment time (in provider_init) rather than spam trace code throughout the code base


Customize Option

Hi,
I'm just wondering how to add a cancel button in option. Can i customize option something like in the screenshot?

The option take only text and it is wrapped inside a <Test /> component.
https://github.com/gs-akhan/react-native-chooser/blob/master/lib/option.js#L23
If you pass a <Text /> and style it. you can do it.


Adding some more ehcache unit tests

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Shiro-pr/177/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Shiro-pr-jdk11/6/Failed Tests: 1Shiro-pr-jdk11/org.apache.shiro:shiro-web: 1org.apache.shiro.web.filter.authz.AuthorizationFilterTest.testUserOnAccessDeniedWithResponseError

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Shiro-pr-jdk11/7/Failed Tests: 1Shiro-pr-jdk11/org.apache.shiro:shiro-web: 1org.apache.shiro.web.filter.authz.AuthorizationFilterTest.testUserOnAccessDeniedWithResponseError

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Shiro-pr/178/


Youtube-dl doesn´t extract from RTP play

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2020.09.20
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verobse log:
youtube-dl -v https://www.rtp.pt/play/p7636/e492820/os-durrell
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.rtp.pt/play/p7636/e492820/os-durrell']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2020.09.20
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.18362
[debug] exe versions: ffmpeg 2020-09-20-git-ef29e5bf42-essentials_build-www.gyan.dev, ffprobe 2020-09-20-git-ef29e5bf42-essentials_build-www.gyan.dev
[debug] Proxy map: {}
[RTP] e492820: Downloading webpage
ERROR: Unable to extract player config; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpksi3o1r1\build\youtube_dl\YoutubeDL.py", line 797, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpksi3o1r1\build\youtube_dl\extractor\common.py", line 532, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpksi3o1r1\build\youtube_dl\extractor\rtp.py", line 37, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpksi3o1r1\build\youtube_dl\extractor\common.py", line 1010, in _search_regex
youtube_dl.utils.RegexNotFoundError: Unable to extract player config; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
When I run youtube-dl and I tried to download, for example, from this link

youtube-dl https://www.rtp.pt/play/p7636/e492820/os-durrell
this is what appears to me:
[RTP] e492820: Downloading webpage
ERROR: Unable to extract player config; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
#23707 and hopefully fixed by #23877.

I've read the previous reports concerning youtube-dl and RTP Play, but since RTP play seems to have been changed in some way on sept 14th, perhaps youtube-dl needs some kind of upgrade.
Thank very much for the helping.
Best regards.

@vallovic 's repository supposedly deals correctly with the new changes. However, with them, I am still seeing this (which, I suppose, might mean they made even more changes in the meantime):
$ python3 -m youtube_dl https://www.rtp.pt/play/p7488/a-biblioteca-do-futuro --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.rtp.pt/play/p7488/a-biblioteca-do-futuro', '--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2020.09.14
[debug] Git HEAD: 81fe8e386
[debug] Python version 3.7.5 (CPython) - Linux-5.3.0-64-generic-x86_64-with-Ubuntu-19.10-eoan
[debug] exe versions: ffmpeg 4.1.4-1build2, ffprobe 4.1.4-1build2, phantomjs 2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[RTP] a-biblioteca-do-futuro: Downloading webpage
ERROR: Unable to extract player config; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/home/marado/github/youtube-dl/youtube_dl/YoutubeDL.py", line 797, in extract_info
    ie_result = ie.extract(url)
  File "/home/marado/github/youtube-dl/youtube_dl/extractor/common.py", line 531, in extract
    ie_result = self._real_extract(url)
  File "/home/marado/github/youtube-dl/youtube_dl/extractor/rtp.py", line 36, in _real_extract
    'player config'), video_id, js_to_json)
  File "/home/marado/github/youtube-dl/youtube_dl/extractor/common.py", line 1009, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract player config; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

@marado You're right, they changed something in the meantime: they inserted an extra space where it wasn't supposed to. I've fixed it and already pushed the change to my repo.

Hi, I was trying to fix this (with my rather limited knowledge of youtube-dl) before seeing this issue and @vallovic 's repository, but still, here's a possible fix (rtp.py and patch): https://gist.github.com/loucurapt/15e5b5cba1111195075ea0ec89c3fb3b
It has a workaround for that js_to_json bug. I simply remove lines that start with "//" from the JSON before sending it to self._parse_json().
It seems to download videos fine.
Anyone, feel free to use it and push it to youtube-dl!
I just want to see youtube-dl working for RTP Play. 😄

@vallovic's fix being mentioned is better refered to in #23877 .


Update DG about FreeSchedule

Codecov Report

Merging #109 (4730f8f) into master (bf2b86a) will decrease coverage by 1.23%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #109      +/-   ##
============================================
- Coverage     70.41%   69.17%   -1.24%
  Complexity      583      583
============================================
  Files            96       98       +2
  Lines          2011     2047      +36
  Branches        248      251       +3
============================================
  Hits           1416     1416
- Misses          507      543      +36
  Partials         88       88

Impacted Files
Coverage Δ

.../seedu/address/logic/parser/AddressBookParser.java
66.66% <0.00%> (-2.90%)
:arrow_down:

...ess/logic/parser/schedule/ExportCommandParser.java
0.00% <0.00%> (ø)

...address/logic/commands/schedule/ExportCommand.java
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


feat: Integrate ROCKs to charm and servers

Integrate ROCKs to charm and servers
Update tf-serving test results due to canonical/seldonio-rocks#86. We can see that tensorflow
test that also uses the updated ROCK didn't need any change.

Closes #224

Awesome work @orfeas-k !!


feat(gaze): Add gaze.from_numpy and gaze.from_pandas

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (863d7d5) 100.00% compared to head (9f41154) 100.00%.

:exclamation: Current head 9f41154 differs from pull request most recent head 7b840ab. Consider uploading reports for the commit 7b840ab to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #334   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           42        44    +2
  Lines         1603      1624   +21
  Branches       354       354
=========================================
+ Hits          1603      1624   +21

Impacted Files
Coverage Δ

src/pymovements/gaze/__init__.py
100.00% <100.00%> (ø)

src/pymovements/gaze/from_numpy.py
100.00% <100.00%> (ø)

src/pymovements/gaze/from_pandas.py
100.00% <100.00%> (ø)

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


Fixed error messages for React 15.6

Added e.persist() in scroll events for React 15.6 v.

I've had to manually implement the same fix in vendor files. This really needs to get merged. Thanks guys!

https://github.com/BosNaufal/react-scrollbar/pull/25#issuecomment-403067688


Updated some major packages

I personally don't have time to maintain this repo. If you'd like to carry the torch I can link your fork in the README.

I personally don't have time to maintain this repo. If you'd like to carry the torch I can link your fork in the README.

looks ok to me


Update waas-quick-start.md

Link added under Learn More. Resolves https://github.com/MicrosoftDocs/windows-itpro-docs/issues/1576

@jaimeo - Can you please assist to check, approve and merge the content of this PR based on issue #1576?
Thank you.


Dialog: a need to customize compiler parameter orders

Hi! Compiling a default dialog project results in game where you are bound to some initial location and cannot change it:

I believe it has to do with it the order of library inclusion:

Maybe an option to select which order to place the inclusions? Sometimes it might be beneficial to add it before the system library, other times not.

You can change the order of included files in the file manager by clicking on the arrows next to the file name. They appear on mouse hover or on mobile with a long press on the file name.

You're right that the files should be in the correct order from the start, so I'll leave the issue open until that's fixed.

Thanks! I Clearly missed that one!


Android 11-12: No activity found to handle Intent { act=android.intent.action.PICK typ=image/* } [🐛]

Description
When I call launchImageLibrary at android 11-12 devices res.errorMessage gives me this message:
No activity found to handle Intent { act=android.intent.action.PICK typ=image/* }
How to repeat issue and example
By using these options:
const options: CameraOptions | ImageLibraryOptions = {
  mediaType: 'photo',
  includeBase64: false,
  includeExtra: false,
  quality: 0.5,
}

By the way, it works when I add: selectionLimit: 0. However, I need single select.
Solution
Have no solution yet.
Additional Information

Image Picker version: 5.3.1
React Native version: 0.70.6
Platform: Android 11-12
Development Operating System: On both mac and windows
Dev tools: Android API 30 - 31 on real devices only. Emulator is working.

Any update on it?
Here I have the issue on Android <= 10.
Just tested on Android 12 and 13 and it works fine.


test: adds negative scenario outline for jwt credential offer

Description:
Adds negative scenario outline for jwt credential offer
Checklist:

[ ] My PR follows the contribution guidelines of this project
[ ] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked the PR title to follow the conventional commit specification

coverage: 48.848%. remained the same
when pulling 7f841820a57fbffbd83d9f9b7ca3b8051db8a477 on test/jwt-offer
into 01f0eb7681335f556cbb4a39e2edf1d669a441d8 on main.


Can we remove this console.log?

https://github.com/KevCJones/ngx-simple-modal/blob/5c91e25da94eb1a3cf74fa280a282d40318eaefe/src/simple-modal/simple-modal-wrapper.component.ts#L65
Can we remove this console.log please?

Yeah, if you can make a PR to master, I'll appreciate it. I can do a
release later on
On Thu, 8 Aug 2019, 16:20 kameelyan<EMAIL_ADDRESS>wrote:

https://github.com/KevCJones/ngx-simple-modal/blob/5c91e25da94eb1a3cf74fa280a282d40318eaefe/src/simple-modal/simple-modal-wrapper.component.ts#L65
Can we remove this console.log please?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/KevCJones/ngx-simple-modal/issues/55?email_source=notifications&email_token=AAFJ54DBKTMQJQ74WNC74P3QDQ2TZA5CNFSM4IKLSZ22YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HEF44JA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFJ54FNFVTBBLS6QO6IYILQDQ2TZANCNFSM4IKLSZ2Q
.

https://github.com/KevCJones/ngx-simple-modal/pull/56

Ta will bump  version today
On Thu, 8 Aug 2019, 23:30 kameelyan<EMAIL_ADDRESS>wrote:

#56 https://github.com/KevCJones/ngx-simple-modal/pull/56
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KevCJones/ngx-simple-modal/issues/55?email_source=notifications&email_token=AAFJ54B5YSRYIBA65EMKB7DQDSNADA5CNFSM4IKLSZ22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD35CQRI#issuecomment-519710789,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFJ54DBSKADILOWIOS5ZEDQDSNADANCNFSM4IKLSZ2Q
.

Release 1.3.24


Type fixes for Pint >= 0.19.3 and attrs fixes for Python 3.11.

See:
https://github.com/python-attrs/attrs/pull/969
https://github.com/hgrecco/pint/issues/1642

Codecov Report

Merging #25 (9b0f817) into main (07f28ed) will increase coverage by 0.02%.
The diff coverage is 96.55%.

@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
+ Coverage   73.16%   73.19%   +0.02%
==========================================
  Files          14       14
  Lines        1994     1996       +2
==========================================
+ Hits         1459     1461       +2
  Misses        535      535

Impacted Files
Coverage Δ

src/alhambra_mixes/actions.py
85.52% <92.30%> (ø)

src/alhambra_mixes/units.py
75.22% <95.83%> (+0.46%)
:arrow_up:

src/alhambra_mixes/components.py
89.37% <100.00%> (ø)

src/alhambra_mixes/dictstructure.py
61.53% <100.00%> (ø)

src/alhambra_mixes/experiments.py
100.00% <100.00%> (ø)

src/alhambra_mixes/printing.py
60.58% <100.00%> (ø)

src/alhambra_mixes/quantitate.py
53.97% <100.00%> (ø)

src/alhambra_mixes/references.py
66.02% <100.00%> (ø)

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

I actually can't find documentation for PlainQuantity in pint. What is it? Do you have a link to a description of it?

I actually can't find documentation for PlainQuantity in pint. What is it? Do you have a link to a description of it?

In general the pint API seems incomplete: https://pint.readthedocs.io/en/stable/api/specific.html
For instance, there's another module pint.testing, but I don't see it mentioned in the link above.
Is that site out of date and their real documentation is elsewhere?

This is confusing overall.  After discussion on the pint issue, I've mostly switched back to Quantity instead of PlainQuantity, except where it is actually needed for mypy to stop complaining.  PlainQuantity appears to be a new addition that isn't supposed to usually be necessary, but in adding it, the generic for the magnitude type for Quantity was removed.  I'm hoping that will be added back at some point.


Contribution on video part of Impact of Java on internet

Impact of Java on Internet📜
Submitting the video

)

[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Java_Domain

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@AkMo3


Show vulnerability id

is it possible to show the concrete CVE record, e.g

I don't think all vulnerabilities will have a CVE (for example, if you configure Kubernetes with anonymous access and RBAC wide open, the cluster is vulnerable to attack but not because of a software vulnerability. But I agree we should report CVE numbers where they are available.

We do now show CVE numbers for specific CVE vulnerabiltiies


New config options for Rspamd plugin

Also fixes:
improper port in example config
not adding headers when 'reject' was ignored(?)

Coverage remained the same at 16.67% when pulling c6fdd031eedb775f76a74d3b782849b66428ea98 on fatalbanana:master into 9ab2bfa401c6ddc1d706a876d2c0d3de10948ea4 on msimerson:rspamd.

Coverage remained the same at 16.67% when pulling c6fdd031eedb775f76a74d3b782849b66428ea98 on fatalbanana:master into 9ab2bfa401c6ddc1d706a876d2c0d3de10948ea4 on msimerson:rspamd.

Hmm this is bad. :(

why bad?


Too many excludes are silently ignored

Hello @allinurl !
I see you liked my excludes generator in https://github.com/allinurl/goaccess/issues/700#issuecomment-296378428
For example only using Pingdom's IP-s goaccess silently ignores the end of the list
-e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS> -e <IP_ADDRESS>
but not the option (-f) after excludes, so it is not a command line problem.
Is there a limit to the number of excludes?
I've trying with 901 IP-s/ranges.

Ooops! It is 64 😢
https://github.com/allinurl/goaccess/blob/8dbfef26aa0a19c2edd93d5909534f9019a649c0/src/settings.h#L38
Should I recompile goaccess to raise it?

Could we get a warning on exceeding this limit?

That's right, you certainly need to bump up the limit and recompile. Note that the size of the list is proportional to the run time, which could make this pretty slow though.
I like the idea of having a warning, I currently push excludes to the list under options.c.

Thanks.

Note that the size of the list is proportional to the run time, which could make this pretty slow though.

Do you think 1024 is a big value?

I think 1024 is not that bad, but I'd give it a shot and see how it performs for you from 64 to 1024. If you feel it's not bad, you could bump it up even more. However, using ranges as much as possible might be a better choice.

Wooooorks! :)

Per this commit, the debug warning has been added.
Closing this. Thanks!


Update kubernetes.md

Added how to configure configmap in k8s 1.16
Description
Type of fix - documentation
Will help future users upgrading to kubernetes 1.16 adjust flannel
Release Note

None required

We don't plan to support older kubernetes versions (< 1.15) from flannel v0.13.0, and the current code already has the correct CNI version in the kube-flannel.yml
Closing this PR. Please re-open if needed.


nodePackages.generator-code: init at 1.5.5

Motivation for this change
VS Code Extension generator
https://www.npmjs.com/package/generator-code
https://github.com/Microsoft/vscode-generator-code
Things done

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

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Notice: this package is not out of the box.
According to code https://github.com/yeoman/yo/blob/v4.3.0/lib/cli.js#L130 and https://github.com/yeoman/environment/blob/v3.5.1/lib/environment.js#L106,
you may want to link the lib folder out to use yo cli.

Notice: this package is not out of the box. According to code https://github.com/yeoman/yo/blob/v4.3.0/lib/cli.js#L130 and https://github.com/yeoman/environment/blob/v3.5.1/lib/environment.js#L106, you may want to link the lib folder out to use yo cli.

How should I do that? which path should be linked?
also can it be defaulted (I guess no one use it for any-other purpose rather than with yo)


Visualize multiple observables at the same time

Hello!
Thank you for this great tool, it's really amazing!
However, it would be nice if we could be able to visualize multiple observables on a single screen in parallel.
Having this example:
const { interval } = Rx;
const { map, take, filter } = RxOperators;

const numbers = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10];

const numbers$ = interval(500).pipe(
  take(10),
  map(index => numbers[index])
);

const oddNumbers$ = numbers$.pipe(filter(number => number % 2 === 1));
const evenNumbers$ = numbers$.pipe(filter(number => number % 2 === 0));

[numbers$, oddNumbers$, evenNumbers$];

We should be able to visualize all three observables. This would be great to see how different transformations work (like in marble diagrams).

@slavafomin, hello. 🙂
I think it's still possible to do it. In your case the only thing you need is to trigger all three at the same time. You can use from operator for it. But it might not look the way you expect it to look, I guess, because you will still see the very first stream completion visualization.
I made a little change to your code here:
const { from, interval } = Rx;
const { map, take, filter } = RxOperators;

const numbers = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10];

const numbers$ = interval(500).pipe(
  take(10),
  map(index => numbers[index])
);

const oddNumbers$ = numbers$.pipe(filter(number => number % 2 === 1));
const evenNumbers$ = numbers$.pipe(filter(number => number % 2 === 0));

from([numbers$, oddNumbers$, evenNumbers$]);

Please note from operator.
And here is the link to see the change in action: https://rxviz.com/v/9J9PZQqO.


Testing suite setup

I'm using jest as test runner so I notice that lottie-react-native isn't transpiled; which is more or less normal. The solution that I found is to tell jest to transform this package along with react-native, jest and your source code.
At package.json the jest config:
"transformIgnorePatterns": [
   "node_modules/(?!(jest-)?react-native|lottie-react-native)"
],

Tho, do you think lottie-react-native shall be distributed transpiled?

?

Any update on this?


How to test the pictures provided by myself

Hello, your idea is great. I want to use it for my own test pictures. What should I do? We look forward to your reply.

So u have a dataset right? Your own dataset?

Yes, I want to use the model directly for testing, not training.

Ok, so u should walk through from main_texture file mentioned in the readme. Then go to the file it redirects, there u will find a bunch of methods like one for dtd, kth datasets etc. so create your own method, then probably u need to provide the names of ur own labels for textures and the labels for imagenet will be same as mentioned for other datasets and please run then.
Its been a long time since i developed this code.

I developed each module from scratch, one thing i would suggest is to use a good backbone like resnet 50 for feature extraction for the common part, u will see better results.


[SPARK-20459][SQL] JdbcUtils throws IllegalStateException: Cause already initialized after getting SQLException

What changes were proposed in this pull request?
Avoid failing to initCause on JDBC exception with cause initialized to null
How was this patch tested?
Existing tests

Test build #76265 has started for PR 17800 at commit ad38533.

Test build #76265 has finished for PR 17800 at commit ad38533.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76265/
Test PASSed.

Test build #76354 has started for PR 17800 at commit f6f2b7a.

LGTM

Test build #76354 has finished for PR 17800 at commit f6f2b7a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76354/
Test PASSed.

Merged build finished. Test PASSed.

Thanks! Merging to master/2.2

@gatorsmile do you think this should go back into 2.1? seems like a clean fix to a non-trivial problem. I don't particularly care either way; you may have more context about the problem.


Slow Response Handling with Custom Defined Model

I have noticed that http4s client response handling is really slow, when handled with custom defined model.
For response size 40MB, entity handling with custom defined model is taking 25866 ms = ~26 sec
For the same size, when response is handled as String and then parsed to custom defined model it is taking 1235ms = ~1 sec
When size is bumped just to 80MB, handling is extremely slow with custom model. It took around ~220 sec
The response handled as String and then parsed to custom defined model took around ~2 sec
I was capturing packets sent in wireshark. Both String and custom model  handling the same amount of packets in stream. Difference is in how fast app handling stream of packets.
I have reproduced this case in following repo https://github.com/mukhayy/scala-http4s-decoder
How String parsing differs from custom defined model parsing, why performance between two is significant?

Sorry, what do you mean by "custom model"? What is it exactly?
Btw, I noticed you are using http4s 0.22. Note that this series is end-of-life. You should upgrade to 0.23 which is supported and has much better performance as well.

How String parsing differs from custom defined model parsing, why performance between two is significant?

Yes, this is very different.
String "parsing" is very easy. The server receives bytes over the network socket. A String is actually just bytes, so it doesn't need to do any more work, just make a defensive copy and wrap it in String class.
For your Response class, I see you are decoding it as JSON. So first all those bytes need to parsed for JSON tokens and converted to the JSON ADT (an in-memory datastructure). Then, that JSON ADT needs to be decoded into your model class.
So it is not surprising you see a difference here: JSON will be slower than String.

When doing response.as[String] do we load entire string into memory? As by definition String is allocated in Heap Memory. I am just trying to understand how stream of bytes[] is pulled from OS receive buffer?

I also have updated http4s to latest, there was no significant change on performance.

One last question, what is best practice handling response in http4s to achieve better performance? As this example only ran in localhost, isolated from real network latency problems.

Thank you a lot!

When doing response.as[String] do we load entire string into memory

Yes.

I am just trying to understand how stream of bytes[] is pulled from OS receive buffer?

You can study the networking code in FS2 to learn more about how that works. Ember uses FS2 for all networking.
https://github.com/typelevel/fs2/blob/5dbe235e5a4e763251f94c3880a75ba20915edbb/io/jvm-native/src/main/scala/fs2/io/net/SocketPlatform.scala

One last question, what is best practice handling response in http4s to achieve better performance? As this example only ran in localhost, isolated from real network latency problems.

http4s (and Cats Effect) make design choices that are optimized for real-world scenarios, where there is latency and a server is handling 1000s of concurrent connections at once. That is the situation where it will shine. If your goal is to maximize performance for moving bytes on a single connection on localhost, then http4s is not the right fit for your needs :)


Deprecate "fractionalEvaluation", rename to "fractional".

With the completion of https://github.com/open-feature/flagd/issues/843 we have a much more powerful fractionalEvaluation.
One problem remains:
"fractionalEvaluation": [
          "email"
          [
            "red",
            25
          ],
          [
            "blue",
            25
          ],
          [
            "green",
            25
          ],
          [
            "purple",
            25
          ]
        ]

has been replaces with:
"fractionalEvaluation": [
          {
            "var": "email"
          },
          [
            "red",
            25
          ],
          [
            "blue",
            25
          ],
          [
            "green",
            25
          ],
          [
            "purple",
            25
          ]
        ]

However, there's a problem which was not immediately apparent. "email" in the first variant is treated as a literal in our new operator: by the time our operator runs, it's difficult (impossible?) to know if the first value ("email" in this case) was the result of an expression ( "var": "myProp" ) or it was hard-coded. This means we should deprecate the old fractionalEvaluation and ignore it, and instruct people on how to properly use a new operator fractional. We can do this with a helpful log warning.

by the time our operator runs, it's difficult (impossible?) to know if the first value ("email" in this case) was the result of an expression ( "var": "myProp" ) or it was hard-coded

A hack is to check if the first value (reference key) is present in the data. If it does, we can safely assume it is a replacement performed by Json logic for a variable. If not, then we can assume it's a user inserted literal that requires a replacement (similar to first example). Then we attempt to fill that from data as a fallback.

by the time our operator runs, it's difficult (impossible?) to know if the first value ("email" in this case) was the result of an expression ( "var": "myProp" ) or it was hard-coded

A hack is to check if the first value (reference key) is present in the data. If it does, we can safely assume it is a replacement performed by Json logic for a variable. If not, then we can assume it's a user inserted literal that requires a replacement (similar to first example). Then we attempt to fill that from data as a fallback.

Ya, that's possible, but it does feel hacky. We'd have to implement it elsewhere too.
What we've implemented here feels "right" to me... Using "var" to reference data... That's consistent with all other json logic. TBH we probably never should have just taken a string as the first arg. Hindsight is 20/20 though.
I plan on doing a git mv on what was just implemented by @craigpastro to a new evaluator called "fractional" and then just replacing the contents of the old evaluator with a depreciation warning. We can even link a little migration guide in the docs which will amount to telling people to do {"var": "xyz"} where they had "xyz"

https://github.com/open-feature/flagd/pull/873 fixes this in a non-breaking way.

From the description above, I don't understand how changing the word fractionalEvaluation to fractional fixes anything?
This sounds like a problem in the "new operator", not the wording used to describe the act of doing a fractional evaluation.
FWIW fractionalEvaluation is a lot more descriptive that fractional.


Make math & stream nodepacks part of a XIBLE installation by default

The math & stream nodepack currently need to be downloaded from the registry before you can use them.
However, since they are fairly essential, it would make sense to make them part of the default set of nodes that ship with XIBLE.

Complete list to be defaulted which are currently separate nodepacks;

math
stream
filesystem
process (/child-process, not published yet)
timing


[HOTFIX][TESTCASE] Testcase fix for replacing lambda function for Java-1.7

Changed Lambda function for compile with Java-1.7.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/680/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/682/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/685/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/685/

@jackylk Yes the intention for this PR is to build with Java-1.7.


Passing subnet-ids dynamically is failing.

Hello friends,
I am trying to create a vpc, and replicate an existing RDS instance. It's failing with error below :
Error: Incorrect attribute value type

  on .terraform/modules/rds_replica/main.tf line 68, in resource "aws_db_subnet_group" "default":
  68:   subnet_ids = ["${var.subnet_ids}"]

Inappropriate value for attribute "subnet_ids": element 0: string required.

What am I doing wrong?
COde :

module "vpc" {
  source  = "terraform-aws-modules/vpc/aws"
  version = "2.6.0"

  name                 = "terraform-vpc"
  cidr                 = "<IP_ADDRESS>/16"
  azs                  = data.aws_availability_zones.available.names
  private_subnets      = ["<IP_ADDRESS>/24", "<IP_ADDRESS>/24", "<IP_ADDRESS>/24"]
  public_subnets       = ["<IP_ADDRESS>/24", "<IP_ADDRESS>/24", "<IP_ADDRESS>/24"]
}

module "rds_replica" {
  source                      = "git::https://github.com/cloudposse/terraform-aws-rds-replica.git?ref=master"
  subnet_ids                  = ["${element(module.vpc.public_subnets, 0)}", "${element(module.vpc.public_subnets, 1)}"]
}

)

I am also facing this issue :

Error: Incorrect attribute value type

  on .terraform/modules/rds_replica.dns_host_name/main.tf line 7, in resource "aws_route53_record" "default":
   7:   records = ["${var.records}"]

Inappropriate value for attribute "records": element 0: string required.

I am using public subnet's manually now, just till the problem I first mentioned is solved. I have these values for zoneid and hostname :

dns_zone_id                 = "OUR_ZONE_ID"
host_name                   = "terraform_host"
Whats the DNS hostname here? Our subnets have public IP enabled. and dnssupport as well.

I am also facing this issue. Has anyone come up with a work around or is there a plan to fix this in the near future? @akshaysgithub have you fixed the problem for yourself?


derive count of vaccinated people from metric ratio

change Projection.getVaccinationsInfo to derive count of people from metric ratio and population if not in the API.
Tested
Changed src/assets/data/data_url.json to snapshot 1571 (or merge develop, the latest uses snapshot 1573 which has TN data) and went to /us/tennessee-tn/county/haywood_county/chart/6 and checked that vaccines are now displayed.

 ETL TN County Vaccine Data into API

I did a lousy job of testing this. https://covidactnow.org/us/tennessee-tn/county/shelby_county/chart/6?s=1574514 says "In Shelby County, Tennessee, 332 people (3.5%) have received the first shot". The county has population 940k so that count should be 33326.

Ooops.  I tested it too and apparently did an equally lousy job! 😞


Fix custom color setting with dark backgrounds

The RegExp only matched the first of two style rules for tokens.

Nice catch @parasyte, thank you for the pull request.


Project data structure results in brittle iteration over projects/software/specs on hub site

In our project data structure, software and specs are located in directories within each project’s directory.
However, Jekyll doesn’t have a concept of subcollections. Jekyll puts under a collection key all files found in that collection’s directory or nested subdirectories.
This means site.projects holds projects, software and specs mixed up. To iterate over just software or specs, we iterate over the whole collection, and on each item we check for URL substring.
Since on project site software and specs become their own collections, this is only an issue on hub site.
We may want a more elegant way of enumerating projects, software and specs, while also keeping it straightforward how to avoid data duplication.

One way to achieve this would be via a plugin, example: https://github.com/codeinpink/jekyll-portfolio-generator

#7 improves on how data is stored, but we’d still want to have a better way of parsing that data neatly. For example, in open project site templates we should be able to access an array of docs under site.specs to iterate on specifications, instead of having to iterate over site.projects and weed out ineligible items with inner conditionals.