[WIP] Add missing button for re-checking authentication status for middleware

Purpose or Intent
Add the authentication re-check button for middleware. [As was just done for several other providers]

Links

#8912

@mtho11 please put the screenshot here in the PR (the one you put in the original issue)
thanks!

tests failure look unrelated since they are in catalog_bundle_initialization_spec

@mtho11 I verified the fix, and the functionality works as expected. however the tooltip displays a placeholder instead of the proper string, please see this screenshot.

@mtho11 the latest revision works (and looks :smiley: ) as expected. imo you can remove wip. then I can move it to miq

@miq-bot rm_label wip

@miq-bot assign @chessbyte

@chessbyte this is very similar to changes that @AparnaKarve made for other providers


Email content not preview.

How can i check what email goes to my customers ?? there are no option for view content of send mails.

Hello @mbbhimani,
Thanks for submitting a GitHub issue! We are very sorry that you are running into this problem. In order to better serve you, as this does not present itself as a library specific issue, we would like to ask that you reach out to our support team at https://support.sendgrid.com.
Thank you!
SendGrid DX Team


Transition to Hugo Image Processing

Issue
#171
Description
This change will changeover all user-configurable images within the layout to utilize Hugo's Image Processing which allows for images to automatically be scaled and optimized, increasing page load performance.
It also implements a basic shortcode {{<rimg src="Export-25.jpg" alt="A pretty image">}} that will allow for the srcset attribute to be used, allowing compatible browsers to load the appropriately sized image in posts.
Changes

Images are loaded using the Hugo Image Processing functionality
Images must be loaded from the /assets folder instead of the /static folder. This is a breaking change

Mitigation of Breaking Changes
It would be possible to check for the value of a site-wide config that will dictate whether to use this way or the standard way. This could allow for a transition period, wherein the user has to make the switch.
Changing is as simple as copying the files
Also possible would be to in case of failure to load image via hugo processing, fall back to old way and hope they are still in /static folder.
Test Evidence
Copy images from /static to /assets and use this version of the theme. Images will be appropriately resized and or scaled.

Two more issues that need to be addressed(Based on further testing with my personal site):

Hugo Image Processing only supports jpg, png, tif, bmp, and gif. SVG is not supported. Therefore, we need to check for this before trying to resize
If the supplied path is not valid, it errors out. It should display nothing instead, or the missing image logo.

@RotatingFans Sorry for being late. It may take few more days. I just couldn't make time to test it.

with this change, i don't know how to set the hero jpg address,before the change,i set the hero like the link
/assets/images/hero/winter-1142029_1920.jpg
now , I can't get a good understanding of how the new code
themes\toha\layouts\partials\helpers\get-hero.html
works，please help how to set hero link,if the images as the link /assets/images/hero/winter-1142029_1920.jpg
thank you so much

with this change, i don't know how to set the hero jpg address,before the change,i set the hero like the link
/assets/images/hero/winter-1142029_1920.jpg
now , I can't get a good understanding of how the new code
themes\toha\layouts\partials\helpers\get-hero.html
works，please help how to set hero link,if the images as the link /assets/images/hero/winter-1142029_1920.jpg
thank you so much

Just put your hero image in the same folder as you post markdown. Rename your hero image as hero.png, or hero.jpg or hero.svg. You don't have to specify anything in the post-front matter.

Just put your hero image in the same folder as you post markdown. Rename your hero image as hero.png, or hero.jpg or hero.svg. You don't have to specify anything in the post-front matter.

i test but can't work...
i test Different catalogues。
\content\Pro-bono,   as \content\Pro-bono\hero.jpg
the md \content\Pro-bono\about.md not show the hero.
i also test set in \content\Pro-bono\about\hero.jpg
not change...
i aslo change the post-front matter:
hero: hero.jpg
or
del hero:
I don't know what I did wrong，thank you for your patience.

i test but can't work...
i test Different catalogues。
\content\Pro-bono,   as \content\Pro-bono\hero.jpg
the md \content\Pro-bono\about.md not show the hero.
i also test set in \content\Pro-bono\about\hero.jpg
not change...
i aslo change the post-front matter:
hero: hero.jpg
or
del hero:
I don't know what I did wrong，thank you for your patience.

Can you point me to your repository?

Can you point me to your repository?

You can follow the sample post structure as this

You can follow the sample post structure as this

I know where I went wrong.
If I want to show hero, I have to create a folder for any file and name it index.md before hero work.
it work,when i change about.md to index.md and put it in`\content\Pro-bono\about'

I don't think this is a good change. Because it would mean that I would have to create a folder for each file, which might instead break the readability and edit management of the files, if there are a lot of md.
Wish there was a better way to manage the hero.and I think HERO is the background, not the content.thank you for your hard work：）

I know where I went wrong.
If I want to show hero, I have to create a folder for any file and name it index.md before hero work.
it work,when i change about.md to index.md and put it in`\content\Pro-bono\about'

I don't think this is a good change. Because it would mean that I would have to create a folder for each file, which might instead break the readability and edit management of the files, if there are a lot of md.
Wish there was a better way to manage the hero.and I think HERO is the background, not the content.thank you for your hard work：）

This structure is recommended by hugo. ref: https://gohugo.io/content-management/organization/

This structure is recommended by hugo. ref: https://gohugo.io/content-management/organization/

I do see your concerns about the readability and management of files, but I think this style of content management actually makes it more manageable, especially for larger sites. It proactively prevents issues where you may add a resource to a page without having the dedicated folder for it. It breaks up each page on the content side cleanly into its own little folder. It prevents the clutter of having hero-image-1234567.jpg and so forth all in one folder. It is unfortunate that it restricts users to a predefined organization, but it is easier to do it from the start that way.

I do see your concerns about the readability and management of files, but I think this style of content management actually makes it more manageable, especially for larger sites. It proactively prevents issues where you may add a resource to a page without having the dedicated folder for it. It breaks up each page on the content side cleanly into its own little folder. It prevents the clutter of having hero-image-1234567.jpg and so forth all in one folder. It is unfortunate that it restricts users to a predefined organization, but it is easier to do it from the start that way.


Gandi DNS: use acme.FindZoneByFqdn function

Commit 8512fab modified the cloudflare, dnsimple and route53 providers to use the acme.FindZoneByFqdn function. This commit makes the corresponding change to the Gandi provider.
Benefits are a small reduction in code size and keeping code style similar to the other providers.

Guilty as charged. Looks good though, much cleaner :+1:

Thanks @LukeHandle. I hope so :)

Tests failing on Go 1.4 only. I don't think it's something introduced in this PR?

The test failure cause would appear to be this commit in google.golang.org/cloud/compute/metadata which is used by google.golang.org/api/dns/v1 which is used by the googlecloud provider. It uses http.Request.Cancel which is Go 1.5+. It's being discussed in this issue.

Looks good though, much cleaner

I agree :)


Fix CNI version to be v0.3.1

[ ] Tests
[ ] Documentation
[ ] Release note

Use CNI spec version 0.3.1

Deploy preview for calico ready!
Built with commit bf5038039e0c0679387799a65adec8b3aefa355d
https://deploy-preview-2882--calico.netlify.com

Deploy preview for calico ready!
Built with commit 6776b132f6ee4a81602bbc2798a079f8abe91116
https://deploy-preview-2882--calico.netlify.com

Does this fix #2886?

I think #2886 is actually a result of us tagging a release from a commit before this change.
I think we should close #2886 though - we'll cut a new patch release in the near future which updates the release archive with the new manifests.


Discord logo only shows half of the logo

Describe the bug
Discord logo only shows half of the logo when used in SvelteKit as :

Reproduction
Using as:
<script>
import Discord from "svelte-supertiny/Discord.svelte";
</script>

<Discord />

Version and System Info
System:
    OS: Windows 10
  Binaries:
    Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
    Watchman: 20220918.223204.0 - C:\ProgramData\chocolatey\bin\watchman.EXE
  Browsers:
    Chrome: 126.0.6478.114
  npmPackages:
    @sveltejs/kit: ^2.5.10 => 2.5.10
    svelte: ^4.2.15 => 4.2.15
    svelte-supertiny: ^1.0.4 => 1.0.4
    vite: ^5.2.10 => 5.2.10

A new version is released.
pnpm i -D svelte-supertiny@latest

A new version is released.
pnpm i -D svelte-supertiny@latest

I ended up finding the bug and made a duplicate svg😅 Amazing! Super fast - thank you💪🏾💪🏾💪🏾

Actually, @shinokada im not seeing the change in the updated pkg.
This was the fix I did on my local: inside the transform of the SVG:

As you see on the website, it should be fixed. https://svelte-supertiny.codewithshin.com/icons

@shinokada For some reason if i scroll down to the Discord logo on your page: https://svelte-supertiny.codewithshin.com/icons i see this>>>

👆🏾half logo.
I can see the same problem on these logos too: Godot, Openbugbounty.
But if i use the 'Search bar' for "Discord" it shows correctly! ??
I currently still have the issue when using the pkg logo.
On my local, I fixed the problem by changing the SVG href from '#a' to '#discord' to match the 'id' of the SVG (see snippy above)

Thanks for the update.
It seems that the new version was not reflected on the dist dir.
Please try v1.0.6 and let me know.
This is on the REPL:
https://svelte.dev/repl/13412dd4129d4c76a0764f47470a5043?version=4.2.18

Ok that Discord logo works now, but suddenly the BG fill color (white) is now appearing 😬 >>>

I was previously using the logos like this, and it was working correctly, so I'm not sure what's causing this new issue:
<Discord fill="none" size="30" pointer-events="none" tabindex="-1" />

You want to remove the white background?

yeah - previously this worked <Discord fill="none" size="30" pointer-events="none" tabindex="-1" />

Please try v1.0.7 and let me know.

Perfect 💪🏾


Add gender to name generator

This fixes #289
Not merge yet! First a question:
@stympy Does I have to distinguish the gender in all language files? Or put in them a alias to first_name instead?

You don't need to modify all the locale files... as long as the old first_name method works across all locales, I'm happy. :)

I have to check if parse doesn't return empty in the cases that first name is defined as single string (the locales that don't have gender), that's fine?

@MaicolBen, @stympy hello! Is this coming anytime soon ? :) Thanks in advance!

Rebased, I make sure that the names weren't updated, but male_first_name method is defined now (without this PR), is it called dynamically?

@MaicolBen thank you for the speed! 👍  This looks great! I hope @stympy can merge this into the main repo soon. :)

If it doesn't merge, there is male_name and female_name in https://github.com/factory-helper/factory-helper

@b264 thank you. Will check it out, at least until the PR is merged into faker itself. That, or I'll end up separating the male/female names into arrays and doing a ".sample" on them. 😅 In any case, thanks a lot!

Pull Request Test Coverage Report for Build 2016

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 33.923%

Totals

Change from base Build 2014:
0.0%

Covered Lines:
1476

Relevant Lines:
4351

💛  - Coveralls

Pull Request Test Coverage Report for Build 2016

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 33.923%

Totals

Change from base Build 2014:
0.0%

Covered Lines:
1476

Relevant Lines:
4351

💛  - Coveralls

Pull Request Test Coverage Report for Build 2016

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 33.923%

Totals

Change from base Build 2014:
0.0%

Covered Lines:
1476

Relevant Lines:
4351

💛  - Coveralls

@MaicolBen could you also update the CHANGELOG.md and add the title of this PR + your GitHub ID?

@vbrazo Done! You should add rubocop to travis or add Code Climate

Pull Request Test Coverage Report for Build 2164

6 of 7 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 99.605%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/faker/name.rb
6
7
85.71%

Totals

Change from base Build 2163:
0.04%

Covered Lines:
2270

Relevant Lines:
2279

💛  - Coveralls

Any updates on this PR?

@vbrazo Sorry, I was on vacation. Also, I rebased tons of time this PR since I created it (look at the creation date). While rebasing I saw the middle name was added copying from first names from both genders (lib/locales/en/name.yml), that's a bad approach, I would take a random one from first_name

@MaicolBen I fixed the middle_name issue in this PR https://github.com/stympy/faker/pull/1270.

@MaicolBen we worked on the middle name locales and I remember that we copied this information from the web.


WFP-1465

yeah, sorry. When we were integrating we realised we always needed the current community person manager unless it was unallocated


Update xNFT docs

Updated xNFT docs and added a callout in gh-pages to promote xnft's

Thanks @nicoeft , LGTM!


ratarmount v0.14.1

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

I messed up. I meant to push to my fork's branch but did push directly to the feedstock. At least it seems to work just fine After adding the patch to remove rapidgzip from the dependencies. Adding the patch also was another time sinkhole by itself ...


Add cBioPortal/TCGA processor

One approach is to process the raw data into summary statistics of interest. For instance, define a list of disease types and pool all the studies for that particular disease. Then calculate the mutation frequency of genes appearing across all studies for that disease, and create gene-mutated_in (frequency: x%)->disease relations to capture the data.

Parts of this were done in #32 but the original idea is not yet integrated.


Manual install of sysvad_tabletaudiosample fails

Target: Windows 10 x86
These are the logs from setupapi.dev.log
[Device Install Log]
OS Version = 10.0.10240
Service Pack = 0.0
Suite = 0x0100
ProductType = 1
Architecture = x86
[BeginLog]
[Boot Session: 2015/10/15 13:49:43.345]

[Device Install (DiInstallDevice) - ROOT\MEDIA\0000]
Section start 2015/10/15 14:06:53.006
cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc
dvi: Selected driver installs from section [SYSVAD_SA] in 'c:\users\wdkremoteuser\desktop\debug\package\tabletaudiosample.inf'.
dvi: Class GUID of device remains: {4d36e96c-e325-11ce-bfc1-08002be10318}.
dvi: Set selected driver complete.
ndv: Driver package 'c:\users\wdkremoteuser\desktop\debug\package\tabletaudiosample.inf' exists under
'C:\Windows\System32\DriverStore\FileRepository\tabletaudiosample.inf_x86_fe8ba9a060f09a3c\tabletaudiosample.inf' (oem20.inf).
inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\tabletaudiosample.inf_x86_fe8ba9a060f09a3c\tabletaudiosample.inf' ([???])
<<<  Section end 2015/10/15 14:06:53.027
<<<  [Exit status: FAILURE(0xe0000203)]

[Device Install (DiInstallDevice) - ROOT\MEDIA\0000]
Section start 2015/10/15 14:06:53.030
cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc
dvi: {Plug and Play Service: Device Install for ROOT\MEDIA\0000}
ump:      Creating Install Process: DrvInst.exe 14:06:53.061
!    ndv:      Installing NULL driver!
dvi:      Set selected driver complete.
dvi:      {DIF_ALLOW_INSTALL} 14:06:53.068
dvi:           Using exported function 'MediaClassInstaller' in module 'C:\Windows\system32\mmci.dll'.
dvi:           Class installer == mmci.dll,MediaClassInstaller
dvi:           No CoInstallers found
dvi:           Class installer: Enter 14:06:53.074
dvi:           Class installer: Exit
dvi:           Default installer: Enter 14:06:53.076
dvi:           Default installer: Exit
dvi:      {DIF_ALLOW_INSTALL - exit(0xe000020e)} 14:06:53.077
dvi:      {DIF_REGISTER_COINSTALLERS} 14:06:53.078
dvi:           Class installer: Enter 14:06:53.079
dvi:           Class installer: Exit
dvi:           Default installer: Enter 14:06:53.080
dvi:                Co-installers registered.
dvi:           Default installer: Exit
dvi:      {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 14:06:53.082
dvi:      {DIF_INSTALLDEVICE} 14:06:53.083
dvi:           No CoInstallers found
dvi:           Class installer: Enter 14:06:53.085
dvi:           Class installer: Exit
dvi:           Default installer: Enter 14:06:53.086
!    dvi:                Installing NULL driver!
dvi:                Install Null Driver: Removing device sub-tree. 14:06:53.088
dvi:                Install Null Driver: Removing device sub-tree completed. 14:06:53.092
dvi:                Install Null Driver: Restarting device. 14:06:53.096
dvi:                Install Null Driver: Restarting device completed. 14:06:53.097
dvi:                Writing common driver property settings.
dvi:                Install Device: Configuring device class. 14:06:53.100
dvi:                Install Device: Configuring device class completed. 14:06:53.101
dvi:                Install Device: Starting device. 14:06:53.102
dvi:                Install Device: Starting device completed. 14:06:53.105
dvi:           Default installer: Exit
dvi:      {DIF_INSTALLDEVICE - exit(0x00000000)} 14:06:53.111
dvi:      {DIF_DESTROYPRIVATEDATA} 14:06:53.114
dvi:           Class installer: Enter 14:06:53.194
dvi:           Class installer: Exit
dvi:           Default installer: Enter 14:06:53.200
dvi:           Default installer: Exit
dvi:      {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 14:06:53.202
ump:      Server install process exited with code 0x00000000 14:06:53.205
ump: {Plug and Play Service: Device Install exit(00000000)}
<<<  Section end 2015/10/15 14:06:53.210
<<<  [Exit status: SUCCESS]

Please pick up this change and retry: https://github.com/Microsoft/Windows-driver-samples/commit/2c9b5b696dc2c396e6ffc9ec721d8085f279a114


[Tracking Issue] TFLite operator support

In https://github.com/apache/tvm/issues/9187 we implemented quantised version of operators in TFLite frontend. Recently, I just noticed a few more operators (with varying priorities) that can be taken as beginner friendly tasks, for someone who's starting in TVM.
I'm creating this as a tracking issue to mark those operators that need to have quantization support implemented and tested:

[x] FLOOR_DIV (#15724)
[x] FLOOR_MOD (#15733)
[x] DIV (#15768)
[ ] POW (#15798)
[ ] REVERSE_SEQUENCE
[ ] SQUARE
[ ] ELU
[ ] LOCAL_RESPONSE_NORMALIZATION (LRN)
[ ] L2_NORMALIZATION
[ ] MIRROR_PAD
[ ] ARG_MIN
[x] NOT_EQUAL (#15769)
[x] LESS (#15746)
[ ] LESS_EQUAL (#15790)
[x] GREATER_EQUAL (#15775)

For each operator above, there are actions to be taken:

Remove the conditional block if self.is_quantized(op): ...
Implement unit tests
ask any committer in the project to update this issue, reflecting the PR to support the operators on the list above

https://github.com/apache/tvm/pull/9165 can be used as an example.
In case you're interested, a good starting point is the TFLite frontend:
https://github.com/apache/tvm/blob/bee073b0c8e8625216184a2dbb0204c0a376fc26/python/tvm/relay/frontend/tflite.py#L78-L185

hi--if no one has taken this yet, can I give this a shot?

hi--if no one has taken this yet, can I give this a shot?

Absolutely @p3achyjr. Each operator can be submitted individually, so we have self contained, easier to review PRs.
Let us know if you need any help. Thanks!

@leandron  I see that the code has changed a lot from the example#9165. All tests are all combined to one function, so if I just need to remove the conditional block and test it? Besides, because I am totally new to it, I find it a little bit tough to have a test, can you offer me some simple ways?

@tlopex if you're working on this too, would you like to divide up the operators so we don't do redundant work?

@p3achyjr  I'm glad to do that. What operators tasks have you doing now?

@leandron I see that the code has changed a lot from the example#9165. All tests are all combined to one function, so if I just need to remove the conditional block and test it? Besides, because I am totally new to it, I find it a little bit tough to have a test, can you offer me some simple ways?

Maybe https://github.com/apache/tvm/pull/14667 can be an updated version of the way to support new operators? Have a look on this one and let me know.

@p3achyjr  So am I.  I think I won't have time to do this work until the first few days of September. If you start to work on it, just inform me. Thanks.

I'm back now. I can take a look at FLOOR_DIV.

@p3achyjr Okay, got it. I am now trying to work on SQUARE.

Finally getting around to this--a draft PR is at https://github.com/apache/tvm/pull/15724

Got it. Actually I don't know clearly how to write a test for unary element operation... And I will try again in following days.

@p3achyjr Thanks. You set me a really great example. I'll try it again.

It looks like this may be causing some flaky CI failures.  I'm noticing some failures in tests/python/frontend/tflite/test_forward.py (link) on unrelated PRs.  These are occurring in the _test_floor_mod function, added as part of https://github.com/apache/tvm/pull/15733,

Confirmed, when running test_all_elem with only _test_forward_elemwise_quantized(_test_floor_mod) enabled, the test fails about 50% of the time.  (44 failures out of 100 iterations).

I'm not able to create a revert--has one already been created?

@Lunderberg what error messages do you see when the tests fail? I wonder if the range should be (0,150) since mod can't be negative, and whether that's causing the failures.

Between the mismatches having suspicious 255 expected values, and this comment, I agree that something is incorrect with the range of inputs/outputs.  Testing different permutations (e.g. excluding negatives, excluding zero) in _test_elemwise_qnn_out_range didn't result in any combinations that became a valid test, so I suspect it won't be a simple numerical change.
My current guess is that there's something going on with the data generation.  Currently, _test_forward_elemwise_quantized generates random uint8 data for the test case, but that could produce zero for the RHS of floormod.  That would produce undefined behavior, with different results based on different optimizations.

I see what you're saying--maybe we can add min/max overrides for _test_forward_elemwise_quantized. I'm surprised that div and floor_div aren't failing in this case though, since the rhs can generate 0s :/.
May I ask how you're running these tests multiple times? This seems to just tell you how to run it one time.

I see what you're saying--maybe we can add min/max overrides for _test_forward_elemwise_quantized.

That's what I'm thinking as well.  It looks like it currently uses the same range for both quantization and for data generation.  I think it will need to override the data generation range to exclude zero from the denominator, but to keep zero in the quantization range as zero may occur in the output.

I'm surprised that div and floor_div aren't failing in this case though, since the rhs can generate 0s :/.

Agreed, as I would expect the same problem to effect any operator with a restricted domain.  My guess is that there's some optimization that assumes the inputs to be valid (a legal assumption, as the output is typically undefined when the denominator is zero), and that that optimization is affecting floormod differently from floordiv.  It probably would be good to track that optimization down at some point, if it occurs at the TVM level, but I don't think that should delay the re-enabling of the unit test.

May I ask how you're running these tests multiple times?

It's a bit of a hacky way to do so.  I commented out everything in test_all_elemwise except for the _test_forward_elemwise_quantized(_test_floor_mod) line, then added a parametrized pytest fixture to the file.  When running pytest as usual (python3 -mpytest -sv tests/python/frontend/tflite/test_forward.py::test_all_elemwise), it then repeats every test the number of times specified.
import pytest

@pytest.fixture(params=list(range(100)), autouse=True)
def repeat_all_tests(request):
    return request.param

I suppose I could have just made a for loop, but I was lazy and this let me use pytests pass/fail counter instead of making my own :P.

I ran some tests--it looks like div, floor_div, and floor_mod all fail. Here is an example of an offending input:
Fail.
Input Node: ['inq_1']
Input Data: [array([[ 12, 215, 181, 106,  92,  19],
       [ 58, 160, 194,  62, 231, 143],
       [ 24, 128,  91, 219,  69,  68]], dtype=uint8)]
TFLite: [[127 129 130 128 125 128]
 [127 131 129 127 129 135]
 [127   0 125 128 127 126]]
TVM: [[127 129 130 128 125 128]
 [127 131 129 127 129 135]
 [127 255 125 128 127 126]]
Raw Data:  [array([[152,  88, 238,   4, 202,  53],
       [ 98, 228,  85,  95, 173, 253],
       [247,  65, 180,  60,  78, 172]], dtype=uint8), array([[ 12, 215, 181, 106,  92,  19],
       [ 58, 160, 194,  62, 231, 143],
       [ 24, 128,  91, 219,  69,  68]], dtype=uint8)]

so at the index where the elements diverge (-5), the input data is 128. Presumably, this is the zero-point for quantization, so min/max overrides won't work.
My question is whether 128 is always the zero point, or if we determine it some other way. If it is, we can just prevent 128 in the RHS. @Lunderberg @leandron do either of you know?

@p3achyjr
            # with respect to its fp32 input range, defined in fake_quant.
            # s = 255/(fmax-fmin);  m = -fmin*s (the zero point)
            for i in input_arrays:
                try:
                    quant_scale = 255 / (input_range[i][1] - input_range[i][0])
                except ZeroDivisionError:
                    print("Min and max of the input range for tensor " + i + " can't be equal")
                mean = -input_range[i][0] * quant_scale
                input_stats[i] = (mean, quant_scale)```
Here, if the range is symmetrical, the zero point will always be 128.

@p3achyjr
            # with respect to its fp32 input range, defined in fake_quant.
            # s = 255/(fmax-fmin);  m = -fmin*s (the zero point)
            for i in input_arrays:
                try:
                    quant_scale = 255 / (input_range[i][1] - input_range[i][0])
                except ZeroDivisionError:
                    print("Min and max of the input range for tensor " + i + " can't be equal")
                mean = -input_range[i][0] * quant_scale
                input_stats[i] = (mean, quant_scale)

Here, if the range is symmetrical, the zero point will always be 128.

Thanks @tlopex!
I'm working on a draft PR to regenerate the input values if any of them are at the zero point. Hopefully I can have it up soon.

@p3achyjr Rather than regenerating, would it be easier to alter the generated values?  That would avoid potentially regenerating data over and over.
# Assuming we know that the operator is mod/div/floormod/floordiv,
# and the generated denominator is in a np.ndarray named "denominator".
denominator[denominator==0] += 1

Thanks for that! sorry not a numpy guy.

@p3achyjr  May I ask you how did you run the tests. Why I use some commands like python3 -mpytest -sv tests/python/frontend/tflite/test_forward.py::test_all_elemwise always get passed even I used offending input you gave. It bothers me for a while.

@tlopex @Lunderberg had a comment above^^
import pytest

@pytest.fixture(params=list(range(100)), autouse=True)
def repeat_all_tests(request):
    return request.param

put that at the bottom of the test file and then run the docker script as usual.

@p3achyjr  Thanks.


Better explanation on output

It tells the user that not just the folders will be checked but also the subfolders inside of them

@dark-coder-cat can you take a look at this pull request? Im quite new to GitHub and Im trying to learn how to use it, would you approve this?

@dark-coder-cat can you take a look at this pull request? Im quite new to GitHub and Im trying to learn how to use it, would you approve this?

thnx for the contribution


Issue: java.lang.IllegalArgumentException: pointerIndex out of range

Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
Explain the motivation for making this change. What existing problem does the pull request solve?
Currently when implementing a Carousel in React Native ScrollView when you add pinch-to-zoom or some other type of touch handler, functionality the onTouchEvent can crash sometimes on Android.
see:
https://github.com/alwx/react-native-photo-view/issues/15
https://github.com/alwx/react-native-photo-view/issues/22
https://code.google.com/p/android/issues/detail?id=18990
https://github.com/chrisbanes/PhotoView/issues/293
https://github.com/chrisbanes/PhotoView/issues/81

I'll close this for now but please feel free to open a new PR that fixes the root cause or handles the error at the exact line where it's happening and logs it.


[bug] Drag image to upload, but tauri open the file

Describe the bug
When dragging and dropping a file to upload it, if the image is dragged and dropped onto the titlebar, Tauri will open the file. The HTML drag and drop event is being used and the system's drag and drop has already been disabled. How can I prevent the dragged image from being opened?
Reproduction
No response
Expected behavior
Tauri should not be opening image files.
Platform and versions
Environment
  › OS: Mac OS 12.6.3 X64
  › Node.js: 16.18.1
  › npm: 8.19.2
  › pnpm: 7.29.0
  › yarn: 1.22.19
  › rustup: 1.25.2
  › rustc: 1.68.0
  › cargo: 1.68.0
  › Rust toolchain: stable-aarch64-apple-darwin

Packages
  › @tauri-apps/cli [NPM]: 1.2.3
  › @tauri-apps/api [NPM]: 1.2.0
  › tauri [RUST]: 1.2.4,
  › tauri-build [RUST]: 1.2.1,
  › tao [RUST]: 0.15.8,
  › wry [RUST]: 0.23.4,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: http://localhost:5173/
  › framework: Vue.js
  › bundler: Rollup

App directory structure
  ├─ dist
  ├─ node_modules
  ├─ public
  ├─ .github
  ├─ src-tauri
  ├─ .git
  ├─ .vscode
  └─ src
✨  Done in 10.18s.

Stack trace
No response
Additional context

Tauri's fileDropEnabled is not related to that. Disabling it may even cause the issue in the first place because then tauri's file drop doesn't interfere with the webview's own drag and drop anymore.
You currently have to prevent this in JavaScript the same way you'd do in a normal browser by listening to drag & drop events and calling event.preventDefault()

I have added event.preventDefault(), there will be no problem in the content area of the page, just drag the picture to the titlebar and just open the picture


Deploy a CAP Business Application to SAP Business Technology Platform - NPM Issue

Tutorials: https://developers.sap.com/tutorials/cap-service-deploy.html
When executing the command npm add @sap/hana-client --save a fatal error is reported, indicating that no suitable image was found:
<EMAIL_ADDRESS>1): no suitable image found.  Did find:
<EMAIL_ADDRESS>mach-o, but wrong architecture
<EMAIL_ADDRESS>mach-o, but wrong architecture
.../my-bookshop/node_modules/@sap/hana-client/lib/index.js:58
db.__stopAllWork();
^
I am using a MacBook Pro with the M1 chip. Is that architecture currently not supported by the HANA Client?

To which steps you are referring to?  Which version of @sap/cds-dk are you using?
Can you please provide the output of cds -v?

I am referring to https://developers.sap.com/tutorials/cap-service-deploy.html, Step 1, Point 3. When adding the SAP HANA driver dependency via npm add @sap/hana-client --save I get the aforementioned error.
Output of cds v:
@sap/cds: 4.6.5
@sap/cds-compiler: 1.50.0
@sap/cds-dk: 3.5.1
@sap/cds-foss: 2.2.1
@sap/cds-runtime: 2.9.1
Node.js: v14.16.0
home: .../.nvm/versions/node/v14.16.0/lib/node_modules/@sap/cds-dk/node_modules/@sap/cds
(node:87479) Warning: Accessing non-existent property 'INVALID_ALT_NUMBER' of module exports inside circular dependency
(Use node --trace-warnings ... to show where the warning was created)
(node:87479) Warning: Accessing non-existent property 'INVALID_ALT_NUMBER' of module exports inside circular dependency
In general I am using a free installation, and that is the first error I observe. The previous tutorial (https://developers.sap.com/tutorials/cp-apm-nodejs-create-service.html) could be completed without issues.
Thanks for looking into the issue.

I have tested it today with node v14.6 and the latest version of cds-dk w/o any issues:
@sap/cds: 4.6.5
@sap/cds-compiler: 1.50.0
@sap/cds-dk: 3.5.1
@sap/cds-foss: 2.2.1
@sap/cds-runtime: 2.9.7
Need to discuss this with the dev colleagues, why using node v 4.16. fail and will get back here asap.

Hi @ahusemann84,
Together with the dev colleagues, we searched for a solution. Could you please try this "workaround" and get back to us, if this works?
In the meanwhile, I will contact the colleagues responsible for the @sap/hana-client module to ask if they are aware of issues using the new MacBook Pro with M1.
Thank you and best regards,
Iwona

Hi @iwonahahn,
thanks for your hint, it actually solved my issue. Besides running the Terminal using Rosetta I had to uninstall node and install it again afterwards.
Then I could also install the hana-client without any problems.
Thanks and best regards,
Arne

Hi Arne,
Thanks a lot for the confirmation :).
Best regards,
Iwona

Just want to share with you this post (and the answer of Sators) was solving my issue too. Check with "node" > process.arch on which architecture your installation is based. Due to this issue (especially with the @sap/hana-client), I had to re-install with node v14 and the specific x64 architecture. Maybe it's worth it writing it down, so the next one will also find it :)

@drvup thanks for the link. Solved my issue as well


[BUG]Boat through the block &Redstone

Boat through the block:

Place the boat on a block and sit on it;
Destroy it on boat;
In under the block.

Redstone:

I'll keep this closed for now, since I do not know what you are talking about without those images.


Add i18n json schema

Whoops -- let's try that again. I think I signed up via the appropriate channels, this time.

I'm going to submit a PR from a different branch -- want to put this in my experimental directory so I can use cider.


getMedias not working on prod

I'm trying to display a list of the last posts from an instagram account (not private) in my Symfony project :
$instagram = new \InstagramScraper\Instagram();
        try {
            $posts = $instagram->getMedias('nameoftheaccount', 6);
        }
        catch (Exception $e) {
            $posts = [];
        }

Perfecty working on my dev version in localhost, but exception caught on prod.
Any idea ?

Which error are you getting?

Hi, I am getting this same problem. The code is running fine in development but not in production.
The error that I am getting is "Account doesn't exist".
The error is occurring at line no.  353 Instagram.php .
if (!isset($userArray['entry_data']['ProfilePage'][0]['graphql']['user'])) {
throw new InstagramNotFoundException('Account with this username does not exist');
}
Any help is much appreciated.

do you get that error with All accounts or just some? Try using dedicated proxies.

The issue has got auto-resolved. The only thing I did was stop the code in development and was only using in production.
@fsjdg when I was getting the error , I was getting in all accounts.

Have same error on prod when I try to get medias: "Uncaught exception 'InstagramScraper\Exception\InstagramException' with message 'Response code is 200. Body:" . Localy work fine without any errors.

I am experiencing the exact same problem. Locally it works perfectly, but I get the following error message on my live-site: Uncaught InstagramScraper\Exception\InstagramException: Response code is 200.'
What to do?

Have you guys @bastluc @MadsWL tried using rotating proxies? it should help.

Also, if do several request to Instagram API, make sure you do some random pauses to avoid bot detection.

@fsjdg Just tried to use a proxy, same error... even on localhost

@bastluc Can't be any proxy. Usually, Instagram detects datacenter's proxies. Are you making this request with a logged-in account or without it?

@fsjdg I'm making de request without any account login


Adjust settings dialog to prevent overflow

What does this PR do
Adjust settings dialog to prevent overflow, specially on screens with display scaling
Apparently Chrome is misbehaving when display scaling is turned on. We define our settings dialog's width and height, and Chrome makes the dialog window bigger. Sadly, the content does not scale up.
I tried some CSS to make Chrome respect the dimensions, but couldn't. At least there's no more overflow.
How to test

Have high resolution screen, change display scaling

If you also have this feature on your OS (Mac, Linux), please let me know how that looks for you
See issue, before and after.
Check specially if there are no uneeded scroll bars, and if the scroll bars are not clipped.

Kinda closes #845

The only problem that I can see on a mac is the double scrollbar, which doesn't go away in this branch either so this PR doesn't seem to be doing anything for me :P

Darn it... I need help with this, then :|
If someone on a Mac can also make a commit?
It's really tough to debug, because if you open the settings.html on a tab, the CSS looks fine, so it should work.  So you have to test it out :|
We have to work around this Chrome thing.
It really makes a difference in Windows, though... from this:

To this:

Not pretty. Really wish we could resize the dialog. But at least we don't have two option pages showing up.
I was also having a horizontal scrollbar appear

and this also removes it.
Not really sure how to get rid of that. Perhaps a overflow:hidden on the body could work there, since from the screenshot there doesn't seem to be a huge vertical overflow, so maybe.
But... Someone on a Mac need to test it out, sadly :|

Well... From the screenshot, it just seems "scrolled down", probably not it, but worth pointing out.
The real problem is when you enable screen scaling. If I use the whole 4k resolution of my screen, everything is tiny, but nothing is broken. Trouble is with screen scaling turned on. Is that the case?

Yep, tried both with scaling on & off. And what I was trying to show was the content getting clipped before it reaches the navigation at the top, it doesn't happen on master.

If you don't even get the double scrollbar on master, I'll get back to the drawing board... Just tried again on Chrome  60.0.3112.78 on Windows, with display scaling, and got this:

This commits really does make it go away, and doesn't break on non-display-scaled screens.
It really seems like a Chrome issue, but couldn't find any discussions about it :|

As an alternative, maybe we should consider using conditional CSS rules for Windows only then.

Just pushed a commit to fix the changelog text position on Mac:

And another to improve the vertical content scrolling, because it was clipping a little below the header (also adds a border below the header):

@Phenome: can you please check if this doesn't break things again on Windows? If everything looks alright: 🚀

This is looking way better today. As assumed, the problem would just "go away" some time when Chrome updated this... It really seemed like a Chrome problem. Giving out wrong dimensions on a display scaled situation.
Report:

Everything looking alright :D Does not break on Windows
Looks even better than before. Thx Chrome


moveit_commander: 0.5.7-1 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository moveit_commander to 0.5.7-1:

upstream repository: https://github.com/ros-planning/moveit_commander.git
release repository: https://github.com/ros-gbp/moveit_commander-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.20
previous version for package: 0.5.7-0

moveit_commander
* Merge pull request #21 <https://github.com/ros-planning/moveit_commander/issues/21> from pirobot/hydro-devel
  Added set_support_surface_name function to move_group.py
* Added set_support_surface_name function to move_group.py
* Contributors: Patrick Goebel, Sachin Chitta

Something may be strange with this. Although version is incremented in the upstream, here only the patch version? (how do you call the version number after dash "-") is updated. Is that what you intended @sachinchitta ?


Fixed inconsistency of outputs collection

Because naming logic for utils.collect_named_outputs in max_pool2d and convolution2d is different, collection is getting filled with inconsistent names.
code to reproduce:
graph = tf.Graph()

node_collection = 'nodes'
with graph.as_default():
    x = tf.placeholder(tf.float32, (1, 20, 20, 3))

    with tf.name_scope('name_scope'):
        conv = tf.contrib.layers.conv2d(
            x, num_outputs=8, kernel_size=4,
            scope='conv', outputs_collections=node_collection)
        max_pool = tf.contrib.layers.max_pool2d(
                conv, kernel_size=2, stride=2, scope='max_pool',
                outputs_collections=node_collection)

print([nt.name for nt in graph.get_collection(node_collection)])
=============================================
['conv', 'name_scope/max_pool']

Expected output is ['name_scope/conv', 'name_scope/max_pool'].
It is also important for those who use tf.name_scope to distinguish processing of different inputs with the same layer, like in siamese neural network. Currently, they will get identical names.
Code to reproduce:
graph = tf.Graph()

node_collection = 'nodes'
with graph.as_default():
  input_a = tf.placeholder(tf.float32, (1, 20, 20, 3))
  input_b = tf.placeholder(tf.float32, (1, 20, 20, 3))
  with tf.variable_scope('feature_extractor') as vs:
    for name_scope, inputs in [('a', input_a), ('b', input_b)]:
      with tf.name_scope(name_scope):
        conv = tf.contrib.layers.conv2d(
          inputs, num_outputs=8, kernel_size=4,
          scope='conv', outputs_collections=node_collection)
        max_pool = tf.contrib.layers.max_pool2d(
          conv, kernel_size=2, stride=2, scope='max_pool',
          outputs_collections=node_collection)
      vs.reuse_variables()

print([nt.name for nt in graph.get_collection(node_collection)])
=============================================
['feature_extractor/conv', 'feature_extractor/a/max_pool', 'feature_extractor/conv', 'feature_extractor/b/max_pool']

Can one of the admins verify this patch?

ping for @sguada

Jenkins, test this please.

@Egor-Krivov could you add a test for it?

OK, I'll add some tests. Can I just add new methods to classes in tensorflow/contrib/layers/python/layers/layers_test.py?

Jenkins, test this please.

@Egor-Krivov please review the test that are failing.

@sguada
Seems like a problem with testing system. All problems in some Java libraries. There are similar problems here https://github.com/kubernetes/kubernetes/issues/26822

@tensorflow-jenkins test this please

I going to add tests in an hour

@sguada
I've added tests for fully connected and conv2d

@tensorflow-jenkins test this please

@tensorflow-jenkins test this please

@rmlarsen Please merge.


Qtgl fix

These two commits improve the shutdown sequence of the QtGlPreview and DrmPreview windows, with the result that you can now successfully open a second one!

@chrisruk Hi Chris, a couple more commits, at least these are fixing some genuine problems!


remove the credentials

j...

@RealSput the firebase config is public information, doesn't need to be removed


Add self-updating

This could probably just be a wrapper around ipydeps.pip('ipydeps', upgrade=True).

Or could it also be an option in the ipydeps.conf file to have it always self update?

Putting --upgrade in ipydeps.conf should do the trick, since ipydeps should just pick it up. #untested

Given the need for underlying stability, making self-updates automatic now seems like a bad idea.  Power users should still be able to explicitly update though other means.  One day #4 will get rolled in, and then it will be slightly easier.


Change "Toggle comment" shortcut

The current keyboard binding for toggle comment is ctrl+1, it can be changed to Ctrl+/ which is by far the most widely used toggle comment shortcut that I have seen

@blink1073 and @goanpeca, thoughts?

I never use the shortcut, but it is Ctrl+/ in Sublime.  I can change it as part of #2217.

Well... to be honest I am used to Ctrl+1 after all this time.... and I am only using spyder now... or notepad++ on windows...
I guess to make an informed decision we should make a coparison (Wiki I guess) where we can have a table on the standard shortcuts used in other IDE/editors, for me is fine if it helps people come over to spyder.

Well, both Ctrl+1 and Ctrl+/ can co exist, I'll send a PR, I already have edited the local Spyder running on my machine

when multiple shorcut presets are implemented, ctrl+\ will be present in some of them, so we can keep ctrl+1 as spyder's default (I'm used to it too)

Stockholm Syndrome is no excuse :smile:, existing users can easily edit it, but I think we should optimize the defaults for new users.

Can't we have both? Because I am aware of ctrl+1 being used only in Spyder and Toad/sql developer, while ctrl+/ is used in a wide range of apps including Eclipse, Geany, LightTable, Sublime etc

Yes, I don't see any problem with leaving both of them.

Sure we can have both, I am ok with it, I am all in for making the new user xp the best possible.
It means that both shortcuts should be fixed shortcuts? or...? does it mean one will be fixed and the other editable? or if both will be editable how will it work out?

Both should be ideally present, let the user use either.

'editor/toggle comment': "Ctrl+1",
+'editor/toggle comment': "Ctrl+/",

I think both should be fixed, and shown in the corresponding menu entry. There is no need to make them configurable :-)

:+1:

'editor/toggle comment': "Ctrl+1", 'editor/toggle comment': "Ctrl+/",
I made the above changes, but the second shortcut overrides the first one, I tried renaming the second one to
'editor/toggle comment two': "Ctrl+/",
it still didn't work. I want to submit my first PR to spyder :D

@thewhitetulip we should make them fixed not configurable... as @ccordoba12 suggest

:+1: , which file should I change?

Looks like issue #478 needs to be fixed first.

Hi, I'm thinkng of contributing to this issue is it still open? Also @thewhitetulip do you still have the modified version of it?

Oh ok, Ty!!

@chends888 Which modified version are you talking about? If I have them then it'll be present on Github (hopefully).

Oh @thewhitetulip It's already closed, I'm working on another issue now. Ty!


git:clone is not a dokku command.

When executing the command dokku git:clone --build tests https://github.com/dokku/smoke-test-app.git
The error below is returned
!     `git:clone --build tests https://github.com/dokku/smoke-test-app.git` is not a dokku command.
!     See `dokku help` for a list of available commands.

My version of Dokku is: dokku version 0.22.8

This command isn't available yet, the repository is just here to support a pull request.

This command isn't available yet, the repository is just here to support a pull request.


Android: Setup Appbuilder being called multiple times

The bug
When the app isn't entire closed, if we try open the app again, the Avalonia Activity OnCreate method is triggered again and causes the problem.
To Reproduce

Start your application
"Exit" pressing "Back" (That should keep the app running in background)
Try return to your app without close it
Throws this error:

System.InvalidOperationException: Setup was already called on one of AppBuilder instances
   at Avalonia.Controls.AppBuilderBase`1[[Avalonia.AppBuilder, Avalonia.PlatformSupport, Version=0.10.999.0, Culture=neutral, PublicKeyToken=c8d484a7012f9a8b]].Setup() in /_/src/Avalonia.Controls/AppBuilderBase.cs:line 302
   at Avalonia.Controls.AppBuilderBase`1[[Avalonia.AppBuilder, Avalonia.PlatformSupport, Version=0.10.999.0, Culture=neutral, PublicKeyToken=c8d484a7012f9a8b]].SetupWithLifetime(IApplicationLifetime lifetime) in /_/src/Avalonia.Controls/AppBuilderBase.cs:line 179
   at Avalonia.Android.AvaloniaActivity`1[[Sample.App, Sample, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].OnCreate(Bundle savedInstanceState) in /_/src/Android/Avalonia.Android/AvaloniaActivity.cs:line 52
   at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_(IntPtr jnienv, IntPtr native__this, IntPtr native_savedInstanceState)
   at Android.Runtime.JNINativeWrapper.Wrap_JniMarshal_PPL_V(_JniMarshal_PPL_V callback, IntPtr jnienv, IntPtr klazz, IntPtr p0)

OS: Android 10
Version 0.10.15 + 0.10.999-cibuild0019213-beta

I forgot, but my stock phone room is infamous for causing bugs because of the aggressive battery optimization.
I don't have another phone to test it, then maybe my issue may be invalid.

@maxkatz6 I think we should

move AppBuilder initialization from AvaloniaActivity to a separate AvaloniaMainActivity class
have some static fields in said class to initialize only once and keep Content alive between instances

have some static fields in said class to initialize only once and keep Content alive between instances

AndroidX with android-viewmodel sharing was added for that matter before. See https://github.com/AvaloniaUI/Avalonia/pull/7435
But I think we can move it to the separated activity and remove androidx from dependencies list.

@marcussacana I can reproduce it as well, so most likely not related to your phone

thx guys!


WIP: support for Julia 0.7

Passes tests on 0.6 and 0.7 locally.
I commented out the showarray method and associated test for now. The showarray functionality has changed quite a bit on master.
Benchmark results are a mixed bag, but nothing outrageous (and no allocations):
 Pair{Any,Any}("RotMatrix{3} * RotMatrix{3}", TrialJudgement(+5.88% => regression))
 Pair{Any,Any}("Rotations.SPQuat{Float64} -> Rotations.RodriguesVec{Float64}", TrialJudgement(-3.23% => invariant))
 Pair{Any,Any}("Rotations.SPQuat{Float64} -> Rotations.AngleAxis{Float64}", TrialJudgement(+2.72% => invariant))
 Pair{Any,Any}("Rotations.RodriguesVec{Float64} -> Rotations.Quat{Float64}", TrialJudgement(-1.10% => invariant))
 Pair{Any,Any}("Rotations.Quat{Float64} -> Rotations.RodriguesVec{Float64}", TrialJudgement(-9.68% => improvement))
 Pair{Any,Any}("Rotations.Quat{Float64} -> Rotations.AngleAxis{Float64}", TrialJudgement(+28.40% => regression))
 Pair{Any,Any}("Rotations.AngleAxis{Float64} -> Rotations.SPQuat{Float64}", TrialJudgement(-4.46% => invariant))
 Pair{Any,Any}("Rotations.SPQuat{Float64} -> Rotations.Quat{Float64}", TrialJudgement(+5.66% => regression))
 Pair{Any,Any}("Rotations.Quat{Float64} -> Rotations.SPQuat{Float64}", TrialJudgement(-21.57% => improvement))
 Pair{Any,Any}("Rotations.RotMatrix{3,Float64,9} -> Rotations.Quat{Float64}", TrialJudgement(-1.27% => invariant))
 Pair{Any,Any}("Rotations.RotMatrix{3,Float64,9} -> Rotations.AngleAxis{Float64}", TrialJudgement(+5.60% => regression))
 Pair{Any,Any}("Rotations.AngleAxis{Float64} -> Rotations.RodriguesVec{Float64}", TrialJudgement(+6.45% => regression))
 Pair{Any,Any}("Rotations.RodriguesVec{Float64} -> Rotations.AngleAxis{Float64}", TrialJudgement(+7.84% => regression))
 Pair{Any,Any}("Rotations.RodriguesVec{Float64} -> Rotations.RotMatrix{3,Float64,9}", TrialJudgement(-22.18% => improvement))
 Pair{Any,Any}("Rotations.RodriguesVec{Float64} -> Rotations.SPQuat{Float64}", TrialJudgement(+12.41% => regression))
 Pair{Any,Any}("Rotations.Quat{Float64} -> Rotations.RotMatrix{3,Float64,9}", TrialJudgement(+34.88% => regression))
 Pair{Any,Any}("Rotations.AngleAxis{Float64} -> Rotations.RotMatrix{3,Float64,9}", TrialJudgement(+1.43% => invariant))
 Pair{Any,Any}("Rotations.RotMatrix{3,Float64,9} -> Rotations.SPQuat{Float64}", TrialJudgement(-5.98% => improvement))
 Pair{Any,Any}("Rotations.SPQuat{Float64} -> Rotations.RotMatrix{3,Float64,9}", TrialJudgement(+13.04% => regression))
 Pair{Any,Any}("Rotations.AngleAxis{Float64} -> Rotations.Quat{Float64}", TrialJudgement(+1.59% => invariant))
 Pair{Any,Any}("Rotations.RotMatrix{3,Float64,9} -> Rotations.RodriguesVec{Float64}", TrialJudgement(+32.09% => regression))

Alright, redid the show stuff. Should pass tests and be ready for review now.

Addressed the comments.

Thanks again :)


Doesn't work in all modes

App version: 2.8
Device information: Android 12 (API 31)
[arm64-v8a, armeabi-v7a, armeabi]
Screen resolution: 2263 x 1078
MIUI 13.0.5

The latest version is 2.8, please try with that:
https://f-droid.org/en/packages/com.github.muellerma.coffee/

App version: 1.3.2 (10320)

There was no version 1.3.2 for this app. Are you sure you're using Coffee?
If so, did you enable alternate mode?

Closed due to inactivity

Can you try it again with 2.11 and the issue still persists, capture a log via adb?

Can you capture the log via adb? Does the notification show up when Coffee is activated?

but it disappears after the screen is turned off

Do you turn off the screen manually, e.g. by pressing the lock button?

When you lock the screen manually, Coffee turns off. This is intentional behavior.

I wouldn't veto against a switch in the settings to make this optional. However I don't know if a wakelock can survive the manual screen lock.


Automate Section Numbering

Problem:

Section numbering can be automated
Add option execute section from a specific number to cursor
Add option to execute from cursor to section

Approach:

Anchor the section using the TreeView option

Button should toggle one section as anchor (default to top)

Add numbering trait to Section object

Exit:

Updated .ts with section numbering, section anchoring, and execution from/to anchored

Progress:

Got an efficient section tree
Fixed a bug with run section not working when cursor on last line of file

Next:

Likely an overhaul of the section creation, callbacks, and execution
Section label with auto numbering

Progress:

First draft of Section Tree with numbering

Potentially noticeably slower startup of navigator with multi-tree generation during debugging

Debug: buttons for each section not functioning due to changes to definition of tree item

Results:

Next:

Update section button callbacks
Update usage throughout to use cached Trees
Ways to expand / collapse all subtree in a document
Anchor section for execution

Progress:

Reformatted to flatten sections rather than nested tree

vscode API is limited in collapse / expand tree programmatically?!

Added maximum number of actively tracked files

Results

Next:

Add number of tracked active files to configurable

Support for auto / manual section level marking

* after section marker like # %% * Heading for auto numbering
- like # %% -- Heading for a manual level 2 heading

Clean up, update, and publish

Next next: add anchor to mark section as run starting position

Allows for run to / from anchor when a file has section with anchor
run to anchor default should be end of file
run from anchor default should be top of file

Progress:

Added visible | opened viewing options for navigator

Next:

Review, cleanup, update README, and publish
Add anchor feature


Use JUNIT report output as source of truth for E2E test status output

We currently parse test results text in order to report on failed tests in the slack channel.
This is brittle and prone to error.
We should use the JUNIT report output by each test execution to determine which tests passed/succeeded, and use this as the source of truth for the test status reporting.

Big fan!

The python junitparser module is not readily available with AWS Lambda. We will either have to manually parse the junit results or use a method like this.


Milestone 0.1.4

Coverage remained the same at 92.857% when pulling 5fb7c80a3554f296f3572b325d26dc9ce40442c5 on milestone-0.1.4 into 23fea88906d7b582e3429ebb2eb9979ecc5641d1 on master.


SIG dies immediately when if disconnects from dispatcher

This is a intermediate measure. Eventually, we want to have
proper reconnect functionality but until then it's better
to kill the process instead of keeping it alive and malfunctioning.

This change is

go/sig/ingress/dispatcher.go, line 95 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This doesn't run in a goroutine, it runs directly from main(). A simple change would be:

make read() have an error return value, if a dispatcher error happens, have read() return that.
change Dispatcher.Run to return the value of read()
change the log message in main() to be slightly more generic, e.g. "Ingress dispatcher error".

The main goroutine has the same treatment as all other goroutines; there is a defer log.LogPanicAndExit() at application start (go/sig/main.go:75).
It's maybe simpler to have the same logic in the reader and writer and not make it overly complex, especially since it's a temporary solution until we have proper reconnection (which should be soon).


Image in VM Creation misleading

The image in the VM creation section (https://docs.microsoft.com/en-us/azure/load-balancer/tutorial-load-balancer-standard-public-zone-redundant-portal#create-virtual-machines) is misleading - do the virtual machines need a public IP address?

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

ID: bc7e0331-9d68-1430-9b52-872104c8f838
Version Independent ID: af5762f8-05d6-e98c-fef8-17cd9e22b9ec
Content: Tutorial: Load balance VMs across availability zones - Azure portal - Azure Load Balancer
Content Source: articles/load-balancer/tutorial-load-balancer-standard-public-zone-redundant-portal.md
Service: load-balancer
GitHub Login: @asudbring
Microsoft Alias: allensu

I should elaborate - the steps listed are missing the Public IP address component (but yet these are present in the image):
Enter these values for the VM settings:
zone 1 - for the zone where you place the VM.
myVNet - ensure it is selected as the virtual network.
myBackendSubnet - ensure it is selected as the subnet.
myNetworkSecurityGroup - for the name of network security group (firewall).
In this case, the VMs are sitting behind a Public Loadbalancer, so they do not need a Public IP address assigned. I assume this image was just repurposed from the "Load balance VMs within an availability zone with Standard Load Balancer" tutorial.

@andrewbeaumont Thanks for the feedback! A Public IP Address is not needed here. The VMs will have outbound connectivity via the Load Balancer, and if individual access to the VMs is needed, ports can be forwarded from the Load Balancer.
Having the Public IP Address here will cause no issues with this tutorial, it will only allow a separate IP Address to access your VMs.
I have assigned the issue to the content author to evaluate and update as appropriate.

Removed incorrect screenshot.
#please-close


highlightjs 9.13.1 css fails to load in online mode

In a presentation with code syntax highlighting (e.g. https://gitpitch.com/glblcd/pyladies-2019-02) syntax highlighting fails with the following console error:
(Chrome MacOS Version 72.0.3626.109 (Official Build) (64-bit))
Refused to apply style from 'https://gitpitch.com/assets/libs/highlight.js/9.13.1/Default.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(Safari Version 12.0.1 (146<IP_ADDRESS>.1))
Failed to load resource: the server responded with a status of 404 (Not Found)
Highlighting works fine in offline mode. If I try to load the file manually in either browser I get a 404 error.

Hi Sam, it looks like the problem is with the value you have set on the highlight property in the PITCHME.yaml for your presentation.
See the highlight setting guide, in particular, this note:

All highlight.js style names specified on the highlight setting must be in lower-case only.

So try changing your current setting value from:
highlight: Default

To:
highlight: default

And let me know if that solves your problem.

Quick update. I've just pushed a patch - now live on gitpitch.com - that makes the value on the highlight setting case-insensitive. So now Default, default, or any case-variation on that word will result in the correct syntax highlighting for code on your slides.


set validateStatus failed

I set the validateStatus between 200 and 500, when the http status code=302, why it enter to the error function console.log(444);  but not console.log(123)

If this code is run in the browser, redirections are automatically followed so there isn't a way to intercept them. In Node.js redirections are followed by default but you can't disable that behaviour by setting maxRedirects: 0 in the request config.


Zombies after melee rework

Description

You as a zombie on client-side look like you're punching instead of clawing things, the range is also really weird.
Reproduction

Zombify yourself
1A. Look at another zombie
Attempt to claw something, it shows up as a punch
2A. The other zombie attempts to claw something, it shows up properly.
Cry as you cannot claw, yet can only punch.

Pretty sure this was fixed.


gf: unstable-2023-08-09 -> unstable-2024-08-21; include extensions and add plugin support

bumped version to unstable-2024-08-21 (changelog);
the developer has released freely their previously paywalled extensions: I've added a parameter (default on) to include such extensions;
reading gf's README, there is a section about plugin support; I don't use them but I figured this make it easier for NixOS users who do.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

moved the file to the new position (still had my system on an old checkout of nixpkgs), also ran nixfmt-rfc-style on it since I forgot doing it before

Pushed both changes, I seem to have missed that particular README.

@decromo can you update commit message and PR title to match version in the commit

@kirillrdy good catch, thanks for pointing that out; should be good to go now?


Option to use iTunes Store API to retrieve artwork and/or metadata

I would love the option to download the artwork and/or show artwork from the iTunes store instead / as well as The TVDB. I will look in to writing a patch for this.
For reference see http://www.apple.com/itunes/affiliates/resources/documentation/itunes-store-web-service-search-api.html and as an example https://itunes.apple.com/search?term=Breaking+Bad&attribute=tvSeasonTerm&entity=tvEpisode

Does anybody know how or what Subler (https://bitbucket.org/galad87/subler) uses to pull meta data from the iTunes store?  That app seems to bee pretty reliably querying all the meta data and full size art work for shows and movies.


ClientScript stops working after updating to 10.8.5

I updated to Jellyfin 10.8.5 a few hours ago, and since then I have been unable to get scrubbing to return. I've manually injected <script plugin="Jellyscrub" version="<IP_ADDRESS>" src="/Trickplay/ClientScript"></script> to index.html, restarted JF and cleared browser cookies and cache for my server. When I play a video, everything behaves as if ClientScript isn't there. I can navigate to https://server.com/Trickplay/ClientScript and it shows up there. Not seeing any mention of Jellyscrub or ClientScript in my browsers inspector either, which I normally would.
EDIT: Looking at the source for index.html, I can conclude that the injected script does not appear there. This is odd given that I did clear cookies and cache and when I open the file in my jellyfin folder, the script is there. I have however seen similar behaviour before and maybe the solution is editing main.jellyfin.bundle.js instead of index.html since in my experience the changes do stick better from there. I unfortunately am not skilled enough at javascript yet to know where one could inject the script in that file however.

For now I have remedied this using #42 as this seems like the most consistent way of doing it. Thanks @tam1m!
I'll keep this open in case someone not using nginx runs into the same issue.

Unable to reproduce this issue when upgrading to 10.8.7 and on a new 10.8.7 install. Not sure if this was version specific or just a random occurrence but I'll close the issue in a couple of days unless you've experienced this further.


Logging Pods (DeamonSet) have Permission Issue

I setup the Splunk Connect on Openshift with Below Steps:
Followed the Steps provided here  https://github.com/splunk/splunk-connect-for-kubernetes
Installed using Helm 3 with below commands.
$ Kubectl create ns splunk-connect
$ helm install  splunk-connect   -f esf_aro_splunk_values.yaml   splunk/splunk-connect-for-kubernetes -n splunk-connect
$ oc adm policy add-scc-to-user privileged "system:serviceaccount:splunk-connect:splunk-connect-splunk-kubernetes-logging"
Object and metrics pods working fine and able to see the events in Splunk. But Container logs are uploaded to Splunk.
Further Investigation found below error in Logging Pods:
2021-08-05 17:45:37 +0000 [info]: #0 starting fluentd worker pid=279 ppid=1 worker=0
2021-08-05 17:45:37 +0000 [info]: #0 listening port port=24224 bind="<IP_ADDRESS>"
/usr/share/gems/gems/fluentd-1.11.5/lib/fluent/plugin_helper/http_server/compat/server.rb:84: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
/usr/share/gems/gems/fluentd-1.11.5/lib/fluent/plugin_helper/http_server/compat/webrick_handler.rb:26: warning: The called method build' is defined here **2021-08-05 17:45:37 +0000 [error]: #0 unexpected error error_class=Errno::EACCES error="Permission denied @ rb_sysopen - /var/log/splunk-fluentd-kube-audit.pos"**   2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/plugin/in_tail.rb:215:in initialize'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/plugin/in_tail.rb:215:in open'   2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/plugin/in_tail.rb:215:in start'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/root_agent.rb:200:in block in start'   2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/root_agent.rb:189:in block (2 levels) in lifecycle'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/root_agent.rb:188:in each'   2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/root_agent.rb:188:in block in lifecycle'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/root_agent.rb:175:in each'   2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/root_agent.rb:175:in lifecycle'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/root_agent.rb:199:in start'   2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/engine.rb:248:in start'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/engine.rb:147:in run'   2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/supervisor.rb:607:in block in run_worker'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/supervisor.rb:845:in main_process'   2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/supervisor.rb:598:in run_worker'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/lib/fluent/command/fluentd.rb:361:in <top (required)>'   2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/bin/fluentd:8:in require'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/share/gems/gems/fluentd-1.11.5/bin/fluentd:8:in <top (required)>'   2021-08-05 17:45:37 +0000 [error]: #0 /usr/bin/fluentd:23:in load'
2021-08-05 17:45:37 +0000 [error]: #0 /usr/bin/fluentd:23:in `'
2021-08-05 17:45:37 +0000 [error]: #0 unexpected error error_class=Errno::EACCES error="Permission denied @ rb_sysopen - /var/log/splunk-fluentd-kube-audit.pos"
2021-08-05 17:45:37 +0000 [error]: #0 suppressed same stacktrace
2021-08-05 17:45:37 +0000 [info]: Worker 0 finished unexpectedly with status 1
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="tail.containers.var.log.containers.dns-controllerdns-controller.log" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="tail.containers.var.log.containers.kube-dnssidecar.log" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="tail.containers.var.log.containers.kube-dnsdnsmasq.log" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="tail.containers.var.log.containers.kube-apiserverkube-apiserver.log" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="tail.containers.var.log.containers.kube-controller-managerkube-controller-manager.log" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="tail.containers.var.log.containers.kube-dns-autoscalerautoscaler.log" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="tail.containers.var.log.containers.kube-proxykube-proxy.log" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="tail.containers.var.log.containers.kube-schedulerkube-scheduler.log" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="tail.containers.var.log.containers.kube-dnskubedns.log" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding filter in @CONCAT pattern="journald.kube:kubelet" type="concat"
2021-08-05 17:45:38 +0000 [info]: adding match in @CONCAT pattern="**" type="relabel"
Environment: Openshift  4.7 Running in Azure

Attached full log file

Adding Values file.
esf_aro_splunk_values_masked-yaml.txt

Are you on ARO or custom OpenShift on Azure?
Did you try the example: https://github.com/splunk/splunk-connect-for-kubernetes/blob/develop/helm-chart/splunk-connect-for-kubernetes/examples/openshift4-logging-only.yaml

Are you on ARO or custom OpenShift on Azure?
Did you try the example: https://github.com/splunk/splunk-connect-for-kubernetes/blob/develop/helm-chart/splunk-connect-for-kubernetes/examples/openshift4-logging-only.yaml

I am on ARO   ( OpenShift Version: 4.5.39 )

The logging pod won't initialize because of lack of access to logfiles on the OpenShift Nodes:
:EACCES error="Permission denied @ rb_sysopen - /var/log/splunk-fluentd-kube-audit.pos"

Makes sure the Logging container runs with extended permissions to access them using SCC.
For OpenShift you should go through the values.yaml umbrella file and do some more changes in regards to SCC and logfile location, logfile format, additional logfiles (e.g. oauth-auditlog). Search the comments for everything related to OpenShift:

use this https://github.com/splunk/splunk-connect-for-kubernetes/blob/develop/helm-chart/splunk-connect-for-kubernetes/examples/openshift4-logging-only.yaml to get an idea of what needs to be changed

go through the logging-part of the umbrella values.yaml and check for

containers.pathDest (var(log/pods)
container.logFormatType: cri
rbac/ServiceAccount/podSecurityPolicy should possibly be true (not sure you need a separate SCC-Policy, there is a template which will do it for you but might be too open. YMMV)
I don't think we need AppArmor enabled on CoreOS based OpenShift Nodes
kube-audit: adjust path to /var/log/kube-apiserver/audit.log
If required: add oauth-audit log or additional logs

The logging pod won't initialize because of lack of access to logfiles on the OpenShift Nodes:
:EACCES error="Permission denied @ rb_sysopen - /var/log/splunk-fluentd-kube-audit.pos"

Makes sure the Logging container runs with extended permissions to access them using SCC.
For OpenShift you should go through the values.yaml umbrella file/logging-section and do some more changes in regards to SCC and logfile location, logfile format, additional logfiles (e.g. oauth-auditlog). Search the comments for everything related to OpenShift:

use this https://github.com/splunk/splunk-connect-for-kubernetes/blob/develop/helm-chart/splunk-connect-for-kubernetes/examples/openshift4-logging-only.yaml to get an idea of what needs to be changed

go through the logging-part of the umbrella values.yaml and check for

containers.pathDest (var(log/pods)
container.logFormatType: cri
rbac/ServiceAccount/podSecurityPolicy should possibly be true (not sure you need a separate SCC-Policy, there is a template which will do it for you but might be too open. YMMV)
I don't think we need AppArmor enabled on CoreOS based OpenShift Nodes
kube-audit: adjust path to /var/log/kube-apiserver/audit.log
If required: add oauth-audit log or additional logs

Thank you for the input, seems like it resolved permission issue, but, I still dont see my application logs in Splunk.
I mimicked "openshift4-logging-only.yaml" manifest file and update "splunk-kubernetes-logging:" section of values file. Now with that, i am able to see logs. But only from platform. None of my application container logs are offloading to Splunk.
All the Application Containers are deployed in different namespaces, Do I need to add any tag or annotate anything at namespace level so that all the application containers logs flow into Splunk ?

That shouldn't be the issue when you changed the containers.pathDest in the values.yaml.
To be clear: the default path in the values.yaml will not work in OpenShift as it does not use docker any more and CRI-O/RHCOS puts them under a new path. Most of the steps I listed above were not optional.
Just SSH into one of your OCP Master Nodes and look in /var/log/* where all the relevant stuff resides.
Once the path is changed you can verify with oc logs <name of one logging pod> if fluentd starts tailing all the container logs you would expect from that pod. Until then you won't see anything in the backend.
You can also upload your latest values.yaml (w/o confidential information).

There might still be something wrong with the SCC, your values.yaml does not have all the settings I would set.
This is not necessary if you have your own Rolebinding etc, as you mentioned above. But this needs to be bulletproof.
Could you -just for testing- roll it out with these settings activated:
rbac:
 create: true
 openshiftPrivilegedSccBinding: true
serviceAccount:
    create: true

  podSecurityPolicy:
    create: true
    apparmor_security: false
    apiGroup: policy

It will then create its own bindings. They might be too open for your environment but ok for troubleshooting.
If still not working, maybe you could provide the output of oc logs <name of one logging pod> (again, omit private data)
(By "working" I mean: have a stable pod with no errors in the logs and listing all the container logs it found; seeing the logs in the backend is the second step.)
You could also set the logging to "debug", but for initial troubleshooting "info" is ok.
Logoutput normally starts with fluentd versions, the complete fluent conf and after some while all the container logs.
You did not mention the version of SCK you are using, I guess 1.4.7/1.4.8?
I am also not too familiar with ARO but I don't think they changed the internal logging of RHOCS.

I tried above rbac and podsecuritypolicy settings, still same results. I dont see log entries from application containers in the Splunk.
Here I am attaching one of Logging POD log and values file too.  Please suggest, if i am missing anything.  You also mentioned, you are not seeing all the settings in the values file, can you suggest what all I could add too ?
here is the label for the SCK version on daemon set: splunk-kubernetes-logging-1.4.9 and
image in logging daemon set is docker.io/splunk/fluentd-hec:1.2.5
splunk-connect-splunk-kubernetes-logging-x8zl7-splunk-fluentd-k8s-logs.log
esf_aro_splunk_values_v1_yaml.txt

I"m still confused on the version(s) your are using:
You mention splunk-kubernetes-logging-1.4.9 which is the latest release and fluentd-hec:1.2.5 which is the older version.
--> for 1.4.9 those should be the plugin versions reported by oc logs ... when the pod starts: https://github.com/splunk/splunk-connect-for-kubernetes/blob/release/1.4.9/PLUGIN_VERSIONS.sh
--> These basically come from the image tags in the values.yaml file, for 1.4.9: https://github.com/splunk/splunk-connect-for-kubernetes/blob/release/1.4.9/PLUGIN_VERSIONS.sh
--> your values.yaml used the previous containers 1.1.5 and 1.2.6, so you are either running SCK <1.4.8 or a newer version with old container images? I'm speculating here.
--> if you installed it with helm. what is the version reported by helm list <name of sck installation>?

please clean up log files too. They contain things, you might not want to show here (hec_host, hec_token...)

you did not set podSecurityPolicy.create: true
BUT: the pod seems to be stable now and the errors are gone.
Also: These following tail of /var/log/containers/... seem to show, that fluent is in fact processing the logs (this was from a master server I guess, there is only infrastructure stuff).
There are no real warnings as I could tell, but I'm not a Splunk/Fluent guy.

You could:

If you use 1.4.9: start from scratch (tarball from https://github.com/splunk/splunk-connect-for-kubernetes/releases/tag/1.4.9, remove old installation, configure the new values.yaml, use newer container images etc.)
raise loglevel to debug via values.yaml for logging (or change the ConfigMap and restart some logging pods)
Check your backend configuration for connection logs, index-Setup...If the pods do not complain, it means they were able to offload their chunks somewhere...

Here is the output for "helm list" (I installed via helm chart and it is taking the latest version)
helm list -n splunk-connect
NAME          	         UPDATED                              	                        CHART                                              	APP VERSION
splunk-connect	2021-08-20 11:24:02.8395207 -0400 EDT	splunk-connect-for-kubernetes-1.4.9	1.4.9
I also enabled debug for the logging and changed podSecurityPolicy.create: true, here is latest log file from one of POD. Did not notice any abnormalities, still not seeing application container logs in Splunk
splunk-connect-splunk-kubernetes-logging-qlc6t-splunk-fluentd-k8s-logs.log

The debug logs seem fine too, with chunks being uploaded.
I would recommend to start from scratch. Your values.yaml seems to be for an older version than 1.4.9, it uses older container images and you deleted all the snippets from the logging section, I guess something got lost on the way.
Just do an helm uninstall, get the new values.yaml from the 1.4.9 release and customize it to your needs. Do not delete stuff, just activate it or fix it (OpenShift stuff).
This is a diff from my values.yaml for SCK 1.4.9 showing the global and logging section only(!) with changes to the original values.yaml, running OCP 4.6.x
Some caveats:

My splunk guys had a different entry in the global section for indexName than in the sections for logging, metrics, objects. I don't remember why. I'm just the OpenShift guy. In the end it depends on your setup in the backend
We've also set indexFields: to something. I believe it is optional. The links in the comments weren't helpful...
journallogs are not active because the default setting  journalLogPath: /run/log/journal will not work for OpenShift. You really should think twice if you want that kubelet output in splunk as the amount of logging is immense. This might need some more configuration for systemd-units I guess.
That audit-log stuff for oauth-audit hasn't been tested much by us. Just be careful who can access it in Splunk.

# diff <(grep -v '#' sck_149_official_values_yaml)  <(grep -v '#' sck_my_ocp_values.yaml)
6c6
<       host:
---
>       host: $HOST
8c8
<       token:
---
>       token: $TOKEN
10,11c10,11
<       indexName:
<       insecureSSL:
---
>       indexName: $INDEXNAME
>       insecureSSL: true
17c17
<     clusterName: "cluster_name"
---
>     clusterName: $CLUSTERNAME
40,41c40,41
<     pathDest: /var/lib/docker/containers
<     logFormatType: json
---
>     pathDest: /var/log/pods
>     logFormatType: cri
57c57
<     openshiftPrivilegedSccBinding: false
---
>     openshiftPrivilegedSccBinding: true
64,65c64,65
<     create: false
<     apparmor_security: true
---
>     create: true
>     apparmor_security: false
74,75c74,75
<       indexName:
<       insecureSSL:
---
>       indexName: $INDEXNAME_LOGGING
>       insecureSSL: true
187c187
<           path: /var/log/kube-apiserver-audit.log
---
>           path: /var/log/kube-apiserver/audit.log
190a191,204
>     oauth-audit:
>       from:
>         file:
>           path: /var/log/oauth-apiserver/audit.log
>       timestampExtraction:
>         format: "%Y-%m-%dT%H:%M:%SZ"
>       sourcetype: kube:oauth-apiserver-audit
>     openshift-audit:
>       from:
>         file:
>           path: /var/log/openshift-apiserver/audit.log
>       timestampExtraction:
>         format: "%Y-%m-%dT%H:%M:%SZ"
>       sourcetype: kube:apiserver-audit-openshift
238c252
<     securityContext: false
---
>     securityContext: true

Thank you for posting the YAML - that was exactly what I need! Apologies for the late reply. This work sort of fell to the wayside and got tabled.
I'm not sure why when I try the example, it didn't seem to ingest it, but I manually replaced the config map with the values you had above and it works. I am sooooo thankful. Have a lovely holiday season!


Add layout building by strings

Goals

To add the ability to build contents using a built-in layout builder, provide a couple of strings and some mappers from characters to buttons.

Non-Goals

It is not an attempt to replace manual modifications to a menu not layout built.

Motivation
I've written some code in Lotus, which was very boilerplate and verbose. //nice you're being very respectful !
Writing a layout builder can easily reduce such boilerplate and verbosity.
Example:
Capacity capacity = Capacity.of(...);

Content content = Content.builder(capacity)
        .layout(Layout.builder()
                        .set('X', Button.empty(...))
                        .set('Y', Button.clickable(...))
                        .create(
                            "XXXXXXXXX"
                            "XY    YX"
                            "YYYYYYYYY"
                         )
        )
        .draw(..., ...)
        .build();

// Do stuff with "content".

Not bad.

Bro's mad because I was motivated 😭

Bro's mad because I was motivated 😭

You should have published your PR in a more respectful manner


Unexpected token '.'

OS: Windows 10
Running the example command for Docusaurus v2 fails with the message  Unexpected token '.'
Command:
npx mr-pdf --initialDocURLs="https://docusaurus.io/docs/" --contentSelector="article" --paginationSelector=".pagination-nav__item--next > a" --excludeSelectors=".margin-vert--xl a" --coverImage="https://docusaurus.io/img/docusaurus.png" --coverTitle="Docusaurus v2"

Screenshot:

I was having this issue on a Mac as well. For me the issue was happening due to the version of node that I was using. On node v12.22.1 this error was being generated. For work I need to switch between different version of node regularly, so I used nvm to change the node version to v14.17.0, and the pdf generated successfully. Hope this helps.

Are you using NVM for windows? I experienced something similar with NPX and with the same error message (when installing docusaurus with npx).
What worked for me was to upgrade "NVM for windows" to the latest version. (https://github.com/coreybutler/nvm-windows)
Afterwards, you also have to reinstall the node version(s) causing problems, see: https://github.com/npm/cli/issues/4234#issuecomment-1275612483

Close the issue according to the @pankaj-pant solution. Thanks!

Re-open this issue. Benefits when considering Dockerize.


Update manifest.json

Added real themes name & description
Added the right repo link

Thanks @visualcookie! :smile:


Websockets

Fixes #67, #76, #77
The websockets section has now become quite large now. This may need some future clean up or trimming.

"the ability to add push notifactions, streams, chat, etc"
a) The WebSocket protocol does not do streaming.  It opens a persistent bi-directional connection.
b) "push notifications" implies one way.  WebSockets are event-driven and are full-duplex.

Ok I'll add some better clarification of what the websocket protocol does. They were meant to be limited examples of what can be done with it.


how to enable table transformer

Hi, I use md_proc following the basic usage:
print(markdownToHtml('# Hello world!'));
but It does not work for table ,could you please figure out how to enable the fucntion for table.
thanks

Table syntax isn't available. It's present somewhere in roadmap, but not implemented yet.


Duplicated comment in index.js when appsync and multi dynamodb tables permission granted to Lambda function.

Describe the bug
After amplify function update auto generated duplicated comment in index.js.
Amplify CLI Version
4.17.1
To Reproduce
$ amplify function update
Using service: Lambda, provided by: awscloudformation
? Please select the Lambda Function you would want to update function1
? Do you want to update permissions granted to this Lambda function to perform on other resources in your project? Yes
? Select the category api, storage
? Api has 4 resources in this project. Select the one you would like your Lambda to access XXXXXX
? Select the operations you want to permit for XXXXXX create, read, update
? Storage has 18 resources in this project. Select the one you would like your Lambda to access Foo:@model(appsync), Bar:@model(appsync)
? Select the operations you want to permit for Foo:@model(appsync) read
? Select the operations you want to permit for Bar:@model(appsync) read

Expected behavior
/* Amplify Params - DO NOT EDIT
You can access the following resource attributes as environment variables from your Lambda function
var environment = process.env.ENV
var region = process.env.REGION
var apiXXXXXXGraphQLAPIIdOutput = process.env.API_XXXXXX_GRAPHQLAPIIDOUTPUT
var apiXXXXXXGraphQLAPIEndpointOutput = process.env.API_XXXXXX_GRAPHQLAPIENDPOINTOUTPUT
var apiXXXXXXFooTableName = process.env.API_XXXXXX_FOOTABLE_NAME
var apiXXXXXXFooTableArn = process.env.API_XXXXXX_FOOTABLE_ARN
var apiXXXXXXBarTableName = process.env.API_XXXXXX_BARTABLE_NAME
var apiXXXXXXBarTableArn = process.env.API_XXXXXXX_BARTABLE_ARN

Amplify Params - DO NOT EDIT */

Actual behavior
/* Amplify Params - DO NOT EDIT
You can access the following resource attributes as environment variables from your Lambda function
var environment = process.env.ENV
var region = process.env.REGION
var apiXXXXXXGraphQLAPIIdOutput = process.env.API_XXXXXX_GRAPHQLAPIIDOUTPUT
var apiXXXXXXGraphQLAPIEndpointOutput = process.env.API_XXXXXX_GRAPHQLAPIENDPOINTOUTPUT
var apiXXXXXXFooTableName = process.env.API_XXXXXX_FOOTABLE_NAME
var apiXXXXXXFooTableArn = process.env.API_XXXXXX_FOOTABLE_ARN
var apiXXXXXXGraphQLAPIIdOutput = process.env.API_XXXXXX_GRAPHQLAPIIDOUTPUT
var apiXXXXXXFooTableName = process.env.API_XXXXXX_FOOTABLE_NAME
var apiXXXXXXFooTableArn = process.env.API_XXXXXX_FOOTABLE_ARN
var apiXXXXXXGraphQLAPIIdOutput = process.env.API_XXXXXX_GRAPHQLAPIIDOUTPUT
var apiXXXXXXBarTableName = process.env.API_XXXXXX_BARTABLE_NAME
var apiXXXXXXBarTableArn = process.env.API_XXXXXXX_BARTABLE_ARN
var apiXXXXXXGraphQLAPIIdOutput = process.env.API_XXXXXX_GRAPHQLAPIIDOUTPUT

Amplify Params - DO NOT EDIT */

Desktop:

OS: Ubuntu
Node Version: v12.14.1

@chakimar I'm unable to repro this using CLI version 4.18. Please reopen if you're still seeing the issue in the latest version.

Nevermind, just repro-ed

For me it also duplicates the cloud formation template, for example I had permissions for table X and I added permissions for table Y, it will append all permissions (including new and current) to the template, without checking if permission X already exists, which caused my template to be 2000 lines because it had 7 declarations of the same permission and it threw an error that the template it too big. Maybe it’s related?


fix: update blockcontents typing to be more precise

small update to typing

:tada: This PR is included in v1.20.0 :tada:


[chip tests] Shutdown AON timer before exit

This commit shuts down to AON timer completely before exitting the
simulation to avoid the counters from counting up and thereby, causing
end-of-sim assertion failures due to simulation exitting at a time
when the counts were not fully synchronized from the AON to core
clock domain.
Signed-off-by: Srikrishna Iyer<EMAIL_ADDRESS>

would you mind in the PR description just linking a few issues that observed this error?

It looks like this could require almost every test to add some code? Is there a way to address the assertions from the SV side instead? As in some of the standard CIP functions?

It looks like this could require almost every test to add some code? Is there a way to address the assertions from the SV side instead? As in some of the standard CIP functions?

@sriyerg previously had some code in the tb that would kill certain assertions right before the test finished..i think that was the hammer solution.

That may have been a hammer, but this needs changes in the test source for each test unpredictably failing, so we would need to diagnose the failure to add this epilogue. That is why I wonder if there is a better way.

i'm fairly certain the FPGA failures here just need a rebase.

I wonder if there is some other way to deal with this, since this change needs to be done for specific tests once we find them to fail in some unpredictable way.

that might be the case. But should we work on getting this one merged first? and we can keep brainstorming for a better solution.

This is okay for now, but I filed #14913 asking to come up with a better solution.

sounds good. Thanks @matutem.

i'll take over this PR for now.


Module build failed when project already has a .babelrc

Description:
Starting Storybook within a project with an existing .babelrc fails.
Config:

<EMAIL_ADDRESS>Node v7.2.1
Npm 4.0.5
<EMAIL_ADDRESS>
Repro steps
$ meteor create sbrepro
$ cd sbrepro
$ meteor npm install
$ meteor npm install --save-dev babel-plugin-transform-class-properties
$ nano .babelrc

# {
#  "plugins": [
#    "transform-class-properties",
#    "babel-root-slash-import"
#  ]
# }

$ getstorybook
$ npm run storybook

Note that no .babelrc file is present in .storybook/
Expected behavior:
Storybook server starts.
Result:
Server crashes with this log:
> sbrepro@ storybook /Users/vikti/dev/sbrepro
> start-storybook -p 6006

@kadira/storybook v2.35.1

=> Loading custom .babelrc
=> Using default webpack setup based on "Create React App".
=> Loading custom webpack config (full-control mode).

Found the .babelrc you use into the source. Now it works with:
{
  "presets": ["es2015", "es2016", "stage-0", "react"],
  "plugins": [
    "transform-decorators-legacy",
    "transform-class-properties",
    "babel-root-slash-import"
  ]
}

I am not use at babel config at all and I think I am not the only one. Maybe it would be use full to state in the docs the minimum .babelrc requirements before customize it.


Update CONTRIBUTING.md

I had some minor issues getting Laravel to migrate without errors - namely importing scryfall-default-cards.json into the database.

Thanks for reporting this and the revised guidelines.
I think I will modify the failing migration file, so that if the database is empty it won't run the part where the scryfall file is needed. It's intention is to update existing cards in the database, so with new deployment (no cards in the database yet) it's not needed.
After fixing that, we don't need to manually download the bulk-file either, so we should change the guide accordingly. The bulk-file will be later downloaded with php artisan full-update
Another minor issue with the guide is duplication of the steps composer install  and php artisan key:generate
If you could fix those, I see no problem with merging.

@Dankirk: fixed mentioned issues and added some minor changes. Commits added to patch-1


Dropout should give an error message when rate is greater than 1

It is a minor issue but dropout should throw a warning or an error if the rate is greater than 1 (it already caps it)
https://github.com/keras-team/keras/blob/master/keras/layers/core.py#L101-L106

[x] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/keras-team/keras.git --upgrade --no-deps

[x] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[x] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

For background I had a nasty little typo in a model where instead of having Dense(256), I had  Dropout(256) which doesn't make sense and results in a model learning nothing because 100% of the values are being set to 0 at training time. It's probably not a common problem but a warning would be useful


Opening Visual Nuget by Ctrl+Shift+P keys and select target project.

Now:

Expected:

Added this functionality in v0.3.2. Thank you for the suggestion and please let me know if you spot any issues with it.

Fixed

@adrian-pavel  Works fine, thank you!


Updated docstrings

Codecov Report

Merging #10 into master will decrease coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage    95.5%   95.45%   -0.06%
==========================================
  Files           6        6
  Lines          89       88       -1
==========================================
- Hits           85       84       -1
  Misses          4        4

Impacted Files
Coverage Δ

celestial_tools/client/system/cmdline.py
96.87% <100%> (ø)
:arrow_up:

celestial_tools/client/rootfs/__init__.py
91.89% <100%> (-0.22%)
:arrow_down:

Continue to review full report at Codecov.

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


Problem about ‘SyntaxError: invalid syntax’ when running 'eval.py'

I run 'eval.py' and it shows following error:
Traceback (most recent call last):
File "bin/eval.py", line 12, in
from pysot.evaluation import OPEBenchmark, AccuracyRobustnessBenchmark, EAOBenchmark, F1Benchmark
File ".\pysot\evaluation_init_.py", line 1, in
from .ar_benchmark import AccuracyRobustnessBenchmark
File ".\pysot\evaluation\ar_benchmark.py", line 107
row += f'{Fore.RED}{accuracy_str}{Style.RESET_ALL}|'
^
SyntaxError: invalid syntax
could anyone help me? pls.  Is it related to python verison?

I only test on python 3, what's your python version?

I only test on python 3, what's your python version?

My python version is 3.5.6

Another question, should the OTB result file be saved as .mat or .txt? How about VOT result?

If you want to evaluate on official MATLAB toolkit, you should save as .mat
VOT format is .txt

If you want to evaluate on official MATLAB toolkit, you should save as .mat
VOT format is .txt

Forget the official VOT-toolkit, a number of problem happened in that platform.

I also test on python 2.7 and still happened same problem

python 3.5 are not supported to this.
You may chang the code f'{Fore.RED}{accuracy_str}{Style.RESET_ALL}|'
into row += '{}{}{}|'.format(Fore.RED,accuracy_str,Style.RESET_ALL)

python 3.5 are not supported to this.
You may chang the code f'{Fore.RED}{accuracy_str}{Style.RESET_ALL}|'
into row += '{}{}{}|'.format(Fore.RED,accuracy_str,Style.RESET_ALL)

thanks a lot, I will try

python 3.5 are not supported to this.
You may chang the code f'{Fore.RED}{accuracy_str}{Style.RESET_ALL}|'
into row += '{}{}{}|'.format(Fore.RED,accuracy_str,Style.RESET_ALL)

It works! Thank u!