Visualisation problems

Link to PDF file (or attach file here): http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/111/95/491-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/112/96/493-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/113/97/494-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/115/98/495-1
Configuration:

Web browser and its version: All, it happens more in google chrome and in opera,  happens less frequently in internet explorer and firefox.
Operating system and its version: Windows and Linux
PDF.js version:   1.0.907
Is an extension: Yes

Steps to reproduce the problem:

Click the link in different Browsers and OS.
If visualization is weird:
Click fullscreen button
Press Esc

What is the expected behavior?
PDF should be showed well formated.

What went wrong?
Some fonts problems.

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/111/95/491-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/112/96/493-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/113/97/494-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/115/98/495-1

WFM on Mac OSX. Please provide exact versions of the Linux (and Windows) as well as browsers.
Can you reproduce this with the viewer at http://mozilla.github.io/pdf.js (files can be opened via the open file button)?

Hi,
With viewer at http://mozilla.github.io/pdf.js I can't reproduce the error.
Let's starting getting just one OS and Browser.
OS: Windows 10 x64
Browser chrome: Versão 55.0.2883.87 m
Please open all the four links.
It does not happen every time.
I think it's cache-related.
After displaying the PDF correctly it does not show weird for a while.
After half an hour, weird reappears.
Regards.

Tarcisio Pereira

De: Yury Delendik<EMAIL_ADDRESS>Enviado: quarta-feira, 21 de dezembro de 2016 11:46
Para: mozilla/pdf.js
Cc: Tarcisio; Author
Assunto: Re: [mozilla/pdf.js] Visualisation problems (#7908)
WFM on Mac OSX. Please provide exact versions of the Linux (and Windows) as well as browsers.
Can you reproduce this with the viewer at http://mozilla.github.io/pdf.js (files can be opened via the open file button)?
Pdf.js: PDF Reader in JavaScript - mozilla.github.iohttp://mozilla.github.io/pdf.js
mozilla.github.io
©Mozilla and individual contributors. PDF.js is licensed under Apache, documentation is licensed under CC BY-SA 2.5

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mozilla/pdf.js/issues/7908#issuecomment-268526419, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGZMcyrGz5wseJipwcrD-1Q6wLsu_NDuks5rKS3MgaJpZM4LS67-.

PDF.js version: 1.0.907

With viewer at http://mozilla.github.io/pdf.js I can't reproduce the error.

The viewer deployed at www.livrosabertos.sibi.usp.br is old version. We cannon upgrade third-party deployment. Please notify the admins of this site about the issue. Closing as fixed.

Hi @yurydelendik
Viewer deployed at www.livrosabertos.sibi.usp.br is now updated.
Now, this problem is less frequent.
From what I've noticed is only happening in chrome and never when I use the open button.
It's very strange.
Regards,
Tarcisio Pereira

Sounds like #7136, but it's hard to guess or suggest anything without being able to reproduce the issue on different computer.


Issue with 'Start Trace Server' command

Screen Recording 2022-09-06 at 4.07.19 PM.webm

Picking up this issue


no video playback Assassin's Creed

I'm submitting a ...

[*] bug report
[ ] feature request
[ ] support request

General infomration
Prerequisites

[*] Are you running the latest version?

Description
Trying to play movie 'Assassin's Creed' sound is working but no video, all other movies tested work fine.
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Context (Environment)
Installation

[*] I installed the plugin via zip from the Releases page
[ ] I´m using the Netflix Repo
[ ] I´m using a different source (Please tell which)

Operating System

[ ] Linux (x86/x64)
[ ] OSX (x86/x64)
[ ] Windows (x86/x64)
[*] Linux (ARM)
[ ] Android

Additional informatin on the environment
[ using LibreElec #1117, Netflix Latest Master, Raspberry Pi 3 B+]
Debug log
[Please include a link to your debug log (use something like http://sprunge.us/) or similar, please do not paste]
Other information
[e.g. detailed explanation, related issues, suggestions how to fix, links for us to have context, etc.]
Screenshots
[Please add a screenshot if that helps understanding your problem]
[You can erase any parts of this template not applicable to your Issue.]

I dont access to that title but try to define max and secure resolution on InputStream... and please share your log.

http://ix.io/1sg5

Thank you posted Log, I think. thank you - Great work!!!!
On Sun, 18 Nov 2018 at 12:55, jakermx<EMAIL_ADDRESS>wrote:

I dont access to that title but try to define max and secure resolution on
InputStream... and please share your log.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/asciidisco/plugin.video.netflix/issues/538#issuecomment-439667868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASiFOToRhM9OVp8cV-3sXeCQrVzav5IXks5uwOhbgaJpZM4Ynx-q
.

http://ix.io/1sg6

Did Setting the Resolutions work?

no
inputstream adaptive
secure set to 720p
general 1080p
other movies are working fine

try setting both general and secure on 720p, since netflix uses software based codec the RPI does not suppport 1080p videos processing, also, on settings-player, disable OMX just leave MMAL enabled, and post pack the results please.

share your log after trying to play it please

Kodi crash log and config
http://ix.io/1sg7
kodi log and configs
http://ix.io/1sg8

I am running into the same issue with Coco. I can post some of my logs in a little bit if it would help.

yep!! trying to playing coco same issue

Since you have some codecs capabilities announced but  disabled, try setting Inputstream Stream Selection to Manual instead of Manual and post the results back... please.
13:27:57.967 T:1403831152 WARNING: OpenStream - Unsupported stream 1. Stream disabled.

I am running into the same issue with Coco. I can post some of my logs in a little bit if it would help.

I dont have it available as well, but please share your logs, they will help...

Just update your Netflix Addon version to 0.13.18 - should fix not playable movies/tv shows

I have the latest netflix addon install from master.zip
set inputstream selection to manual, rebooted
No change

I have the latest netflix addon install from master.zip
set inputstream selection to manual, rebooted
No change
Your log saids, you have 0.13.17

19:11:54.802 T:1938465440  NOTICE: ADDON: plugin.video.netflix v0.13.17 installed

i have now disabled auto-update on netflix. because it is automatically downgrading the version. working now.. Im embarrassed. thank you


Cache JWKS response from Cognito

Caching support was added in PR https://github.com/labd/django-cognito-jwt/pull/12. I think this can be closed as it duplicates functionality.

Thank you for your contribution! We just released 0.0.2 with caching support.


Increase HKDF_MAXBUF from 1024 to 2048

We've encountered some scenarios that need to use more than 1 kB of
data as the HKDF-Expand() "info" argument (which, per RFC 5869,
contains "optional context and application specific information").
Since HKDF_MAXBUF is used to size an array in the HKDF_PKEY_CTX
structure, this adds 1 kB of memory footprint to each EVP_PKEY_CTX
used for HKDF.

I did not do an in-depth investigation, but I believe that there are some HKDF workflows that don't even use the HKDF_PKEY_CTX.info structure member.  Based on what (somewhat cursory) investigation I did, the workflows that do not use the field are short-lived ones, so perhaps the transient additional allocation is not harmful there.
I do, however, welcome opinions on how big the field has to get before we stop inlining it in the HKDF_PKEY_CTX and allocate it separately.  2kB is probably getting close...

I don't see anything in the standard about limiting the size of this value.

Right, the standard does not impose any real limit (other than the max capacity of the underlying hash function) on the size here.  Having any limit at all is an implementation choice, and if we wanted to be really flexible we would allocate something on-demand and support extremely large info arguments.  But I'm lazy and don't want to do that if there's no real pressing need :)

Agreed, we can do it once the problem is reported.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Thanks for taking a second look (and it was a good question to ask in the initial review)!
Merged to master, so closing.


Swift 3

Great module, love it.  Would love it more if you post a version for Swift 3.   :)

You can take a look at swift-3.0 branch

@poolqf  How do I use swift-3.0 branch using cocoa pod?

Take a lot here


hello_timer wrong printf output

running hello_timer.hex from pico examples result in this output:

Unimplemented peripheral PADS_BANK0_BASE read from 4
Unimplemented peripheral PADS_BANK0_BASE write to 4: -129
Unimplemented peripheral IO_BANK0_BASE write to 4: 2
Unimplemented peripheral PADS_BANK0_BASE read from 8
Unimplemented peripheral PADS_BANK0_BASE read from 8
Unimplemented peripheral PADS_BANK0_BASE write to 8: -129
Unimplemented peripheral IO_BANK0_BASE write to c: 2
UART sent:  H
UART sent:  e
UART sent:  l
UART sent:  l
UART sent:  o
UART sent:
UART sent:  T
UART sent:  i
UART sent:  m
UART sent:  e
UART sent:  r
UART sent:  !

UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
SEV
UART sent:  c
UART sent:  a
UART sent:  n
UART sent:  c
UART sent:  e
UART sent:  l
UART sent:  l
UART sent:  e
UART sent:  d
UART sent:  .
UART sent:  .
UART sent:  .
UART sent:
UART sent:  V
UART sent:
UART sent:
SEV
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
UART sent:  R
UART sent:  e
UART sent:  p
UART sent:  e
UART sent:  a
UART sent:  t
UART sent:
UART sent:  a
UART sent:  t
UART sent:
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:  V
UART sent:
UART sent:
SEV
SEV
UART sent:  c
UART sent:  a
UART sent:  n
UART sent:  c
UART sent:  e
UART sent:  l
UART sent:  l
UART sent:  e
UART sent:  d
UART sent:  .
UART sent:  .
UART sent:  .
UART sent:
UART sent:  V
UART sent:
UART sent:
SEV
SEV
UART sent:  D
UART sent:  o
UART sent:  n
UART sent:  e
UART sent:
UART sent:

while on a real pico it prints:
Hello Timer!
Timer 1 fired!
Repeat at 2501544
Repeat at 3001630
Repeat at 3501668
Repeat at 4001705
Repeat at 4501742
Timer 1 fired!
Repeat at 2503970
Repeat at 3004063
Repeat at 3504105
Repeat at 4004144
Repeat at 4504182
cancelled... 1
Repeat at 7504054
Repeat at 8004053
Repeat at 8504053
Repeat at 9004053
Repeat at 9504053
Repeat at 10004053
cancelled... 1
Done

Investigating with gdbdiff it looks like at some point the silicone runs code from bootrom and the emulator gets mad.
As far as I've seen it seems it does not properly handle the 16bit instructions when the memory address is in the bootrom memory.
on the silicone set a breakpoint at 0x10000416  (line 45 of hello_timer.c) then after roughly 70ish si it goes to bootrom memory area.
I tried this test, it actually use LSLS instruction instead of BL because not able to read/write properly at bootrom addresses:
it('should execute `bl 0x23c2` instruction', async () => {
    await cpu.setPC(0x00000122);
    await cpu.writeUint32(0x00000122, opcodeBL(0x23c2));
    await cpu.singleStep();
    const registers = await cpu.readRegisters();
    expect(registers.pc).toEqual(0x000024e8);
    expect(registers.lr).toEqual(0x00000127);
  });

Hmm... so the emulator doesn't print the numbers correctly?
I suspect it may have to do with the integer divider that we still haven't implemented.
Can you check if there are any writes to SIO addresses at 0xd0000060 or 0xd0000068 ?

out.txt
correct, a lot of missing sio warnings, I didn't see anything to 68 but 60 there are, a lot.
also seen that __wrap_vprintf goes to bootrom

Thanks for attaching the logs!
These are SIO reads (and not writes) but I can see some reads come from the integer divider area:
Read from invalid SIO address: 60
Read from invalid SIO address: 64
Read from invalid SIO address: 74
Read from invalid SIO address: 70

70 is DIV_QUOTIENT,
74 is DIV_REMAINDER
I guess printf() is trying to divide the number by 10 each time to get one digit at a time, and it uses the integer divider for that. But we haven't implemented it yet, so it spits out garbage...
One workaround may be to disable the hardware divider. There's probably a way to tell them compiler not to use the hardware divider, I'll try to google that / look into the SDK sources

I think this is the code is the build system which enables the hardware divider:
https://github.com/raspberrypi/pico-sdk/blob/master/src/rp2_common/pico_divider/CMakeLists.txt
So maybe adding
pico_set_divider_implementation(hello_timer compiler)

to the project's CMakeLists.txt will do the trick?

As it seemed not so complicated (for sure i introduced bugs, no doubt on this) I implemented the hardware divider and , as usual, You were right: the printf output is now correct

You implemented the hardware divider? Cool! I'll check the pull request soon.


Design User management

Find technologist and create tasks for the implementation of user management.

We are archiving this repo.


Shadowdark Character sheet

suggestions:

On the background page/tab can you make the class drop down simple fillable.  To allow for custom Class entry.  It appears all this does anyway is turn off the spell tab.  Perhaps a check-box that does the same.
Several custom classes allow for more than one Luck token, would you make the Luck box a single numerical fillable?

suggestions:
1. On the background page/tab can you make the class drop down simple fillable.  To allow for custom Class entry.  It appears all this does anyway is turn off the spell tab.  Perhaps a check-box that does the same.

Customisable classes are planned.  See Issue #374

2. Several custom classes allow for more than one Luck token, would you make the Luck box a single numerical fillable?

Issue #343 already covers this
Clossing as duplicates


VCR not triggering, requests going straight to guzzle

I'm having an issue which may be related to https://github.com/php-vcr/php-vcr/issues/234 but not necessarily the same.
After updating a lot of packages (part of our update from laravel 5 to laravel 6), I now have a strange issue whereby;
If I run an individual test, it works fine with VCR
If I run a whole file (with many VCRs), many of them fail - and it is evident the requests are not going to VCR.
Just wondering how to go about debugging is, and where does VCR hook into phpunit/guzzle, so I can check what's going on ?
Thanks

Disregard, not an issue.


st2ctl clean isn't really working because mongo not found

Running st2ctl clean returns the following and ultimately does not clean the history.
This will drop the database and delete all logs.   By any chance did you install StackStorm and its dependencies by hand or did you use one of our scripted installs?
If you are using ubuntu 14.04 you will also need mongodb-clients to be installed. Btw, we require mongodb 2.4 and running apt-get install mongodb-server should also pull mongodb-clients as a dependency on ubuntu.

@manasdk I used a scripted install on ubuntu 14.04.
https://docs.stackstorm.com/install/all_in_one.html
I ran the apt-get you mentioned and it looks good now!  Thanks for the quick response!!

Cool. Yeah AIO did install the right packages and am unsure what happened. Btw, going forward we are recommending package-based installers https://docs.stackstorm.com/install/deb.html. Something to keep in mind going forward.


Bug: colored sheep loot

I looked through the generated json files, and breaking heavy_weighted_pressure_plate should give the loot of pink sheep. So I would expect to get pink wool and raw mutton. Or, since it directly references the loot table of minecraft:entities/sheep, cobbled_deepslate_stairs instead of mutton, which is what entities/sheep.json resolves to. Instead I get nothing, after trying multiple times.
I tried the same with objects that should result in loot from other colored sheep, with the same result.
I'll add the json files, if that helps.
heavy_weighted_pressure_plate.json
sheep.json

Colored banners have the same issue. Other colored items I tried work fine.

Uh, sorry, nvm. Works fine with Minecraft 1.20.3 instead of what was the newest version back then, which was 1.20.6.... Please ignore

Your issue did still give me a heads up to check for that ahead when adding support for the new versions, so don't worry about.

Then glad I could be of help :)


UI-tinymce editor not even showing after building the project with grunt build. Do i need to change options?

editor works fine in development but its not working anymore when i build it with minification of files...
guys help me out....is there anyone whos has this kind of error....do i need to change tinymce options in the controller??

I came across similar issue, check if tinymce's theme, skin and plugin directories are getting copied to your dist folder
I dont know if its clean or not, but adding following line to my grunt-copy config solved my issue
{cwd: 'bower_components/tinymce-dist/', src: ['plugins/**', 'themes/**', 'skins/**'], dest: 'dist/', filter: 'isFile', expand:true}

not working , I added the above code in copy.js file, but its not adding those files in dist folder..

Can you please post a plunker reproducing your issue with the minified files, or show the error in question?

h faced with the same problem.
In my case, based on the console log, I change the copy pattern as follow:
	    {
		cwd : 'bower_components/tinymce/',
		src : [ 'plugins/**', 'themes/**',
		    'skins/**' ],
		    dest : 'dist/scripts',
		    filter : 'isFile',
		    expand : true
	    }

+1

@mostafabarmshory solution worked for me.  Not quite sure why it was necessary, but I don't need to know.

I am going to close this issue as this is not an issue with ui-tinymce library itself.
If you feel there is still an issue in this library please open an new issue with a plunker recreating the issue.


SHOW CREATE TABLE does nor order CONSTRAINTs in MySQL 5.5

In MySQL 5.5 (and earlier versions) the SHOW CREATE TABLE output does not order lines with FOREIGN KEY constraints. For example, the  SHOW CREATE TABLE may provide:
        CREATE TABLE constraints (
          name varchar(30) DEFAULT NULL,
          code char(20) CHARACTER SET latin1 COLLATE latin1_bin,
          num int(10) unsigned NOT NULL,
          KEY idx1 (name) COMMENT 'lol',
          KEY idx2 (num),
         CONSTRAINT num_fk FOREIGN KEY (num) REFERENCES nums (num),
          CONSTRAINT name_fk FOREIGN KEY (name) REFERENCES names (name)
        ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
In contrast, the instance.go orders lines with constraints per
ORDER BY BINARY rc.constraint_name, kcu.ordinal_position
This leads to actual != expected here resulting in the table flagged as having UnsupportedDDL, which prevents skeema from generating DDL operations on that table.

Great catch, thank you for the excellent bug report! I now have a simple automated reproduction for MySQL 5.5 and Percona Server 5.5. Luckily, newer versions (5.6+) are unaffected.
Please see https://github.com/skeema/tengo/commit/72ffc93f119c4a01080ea57061727a68ed3b8da0 for the test change (currently in a branch), and https://gist.github.com/evanelias/7516e31e6685df34a73c86d082895de6 for test execution and output. (If trying to run the tests locally, just be aware this requires Dep, Docker, enough disk space to store 11 mysql/mariadb Docker images locally, and several minutes of execution time.)
Please let me know if you'd like to try a fix PR using a similar approach as fixIndexOrder()? Also happy to try on my end, up to you. Either way, thanks again!

I like you suggestion and submitted the PR with updated .travis.yml line just for this test.

Awesome, thank you! Your PR in skeema/tengo is now merged.
The final step will be to update the frozen version of skeema/tengo used here in skeema/skeema. I can do this on my end, or if you'd like to open a PR for it let me know. The process requires a slightly-old* version of the dep tool, v0.4.1, and just looks like this:
cd $GOPATH/src/github.com/skeema/skeema # or wherever you have a clone of skeema/skeema
dep ensure -update github.com/skeema/tengo
git commit -a

That should automatically bring in some changes to vendor/github.com/skeema/tengo/, and also updates Gopkg.lock.
* Dep v0.5.0 breaks backwards-compatibility and I never got around to upgrading. I'm likely going to switch to using Golang v1.11's Modules functionality instead in a few weeks, and move away from Dep entirely.

Locally I got one test failing:
--- FAIL: TestIntegration/SkeemaIntegrationSuite.TestFlavorConfig:mysql:5.7 (1.18s)
skeema_cmd_test.go:1041: Expected init to skip flavor, but it was found
As I was unable to configure Travis-CI for my repo clone, I submit the PR anyway.

My PR build failed at
=== RUN   TestIntegration/SkeemaIntegrationSuite.TestAddEnvHandler:mysql:5.6
/home/travis/gopath/src/github.com/skeema/skeema/testdata/.scratch/mydb: Error 1193: Unknown system variable 'information_schema_stats_expiry')


[ListItem] Secondary action is positioned with gutter when gutters are disabled

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When a ListItemSecondaryAction is presented in a ListItem that has gutters disabled, the secondary action is positioned with an assumed right gutter.

Expected Behavior 🤔
I think this is incorrect.  If we're disabling gutters on a list item, I'd expect the secondary action to be positioned at the right edge.
We could apply another class to the container when the last child is ListItemSecondaryAction and disableGutters is true:
  /* Styles applied to the `container` element if `children` includes `ListItemSecondaryAction` and gutters are disabled. */
  disabledGuttersContainer: {
    marginRight: -16,
  },

Steps to Reproduce 🕹
Live example: https://codesandbox.io/s/material-demo-6mk5u
Context 🔦
I'm rendering a list within an element that defines its own gutters, like CardContent, and I'm using disableGutters on the items to remove the left and right padding.

Your Environment 🌎

Tech
Version

Material-UI
v4.11.0

React
v16.13.1

Browser
Chrome

If you think this is worth pursuing, I'd be happy to submit a PR.
Thanks!

@kgregory It sounds like a valid concern, I think that a pull request would make sense here :). Note that we plan to break down the component in #13597. Regarding the implementation, we would use the context to forward the disableGutters state from the ListItem to the ListItemSecondaryAction component?

Regarding the implementation, we would use the context to forward the disableGutters state from the ListItem to the ListItemSecondaryAction component?

That makes sense.  Okay, I'll get something together today.  Thanks for taking a look.

@oliviertassinari thanks for the suggestion.  Submitted!


kernel: disable IO scheduler on Apple NVME

By default the internal NVME SSD gets the "mq-deadline" IO scheduler applied to it.
According to Ubuntu's documentation, choosing "none" as the IO scheduler provides "minimal overhead" and is "Ideal for fast random I/O devices such as NVME".
https://wiki.ubuntu.com/Kernel/Reference/IOSchedulers
According to benchmarks compiled by Phoronix, "overall though, using 'none' as your I/O scheduler option will still generally offer the best performance for speedy NVMe SSD storage with a few exceptions".
https://www.phoronix.com/review/linux-56-nvme/4
This commit changes the IO scheduler for NVME devices from mq-deadline to none.  Successfully tested on my MacBook Air M1.

@tpwrules Will you be reviewing this pull request, or shall I close it?

I am not interested in having an opinion on this right now.


backup raw kv

What have you changed?
Support Raw KV backup tikv/issues#6213
What is the type of the changes?

add backup_raw
add BackupRawKVWriter

How is the PR tested?

Integration test test_backup::test_backup_rawkv
Integration test test_backup::test_backup_raw_meta

@xinhua5 please fix

@xinhua5 please fix the error below,
let stat = match brange.backup(&mut writer, &engine, backup_ts) {

 ^^^^^^ expected 4 parameters

/release

/release

/test

/test
/release

/test

/release

/test

Test goes well. PTAL @overvenus @5kbpers

@overvenus  PTAL again. Thanks.
By the way, it's found in test that TiKV(a498b9d) may throw an "Invalid argument: Keys must be added in order" from rawkv backup and snapshot generation. It seems not to be related to changes in this PR, and needs further investigation. After confirming the problem I'll file an issue for it.


Edge to another package

Is there any way to edge to another package?

Hey @vahid-sohrabloo!
I’m not really sure what does it mean. Can you please elaborate on the use case?

mypakcage
├── barpackage
│   └── ent
│       └── schema
│           └── bar.go
└── foopackage
    └── ent
        └── schema
            └── foo.go

I want to M2M between Bar Entity (bar.go) and Foo Entity (foo.go)

This option is not supported (and we don't have plans to support it). Thanks!

Closing, but of course, feel free to continue the discussion if you want 😃


NmeaClient: check ACCESS_FINE_LOCATION permission

locationManager.addNmeaListener() requires the ACCESS_FINE_LOCATION permission. With only reduced locations enabled this would cause an exception.
Fixes #1520
Fixes #1515
Pre-launch Checklist

[ ] I made sure the project builds.
[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is does not need version changes.
[ ] I updated CHANGELOG.md to add a description of the change.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I rebased onto main.
[ ] I added new tests to check the change I am making, or this PR does not need tests.
[ ] I made sure all existing and new tests are passing.
[ ] I ran dart format . and committed any changes.
[ ] I ran flutter analyze and fixed any errors.

@SebastianKeller Hey, was there a reason this wasn't merged? I am still encountering those errors on some devices.

@matijakevic
My bad, i've deleted my repository. Didn't expect this would automatically close this PR.

Sorry for the troubles.
https://github.com/Baseflow/flutter-geolocator/pull/1540

Thank you for restoring it :)


Brainstorm!

Come up with ideas for our semester long project; we'll discuss and chose!

Music Maker - use some learning process to create music

I like the music maker idea. My other thought was some sort of machine learning to predict commodity prices, but that would not be as fun as music hahaha

I'm obviously super into the music maker idea, but similarly open to other ideas like the pricing or voice control.  I was intrigued by the text mining too, so lots of options!
Even if we're not required to go super in depth, I think the dream team can do something pretty cool with access to a cluster like this.


New notes should be prepopulated with title

New notes should be pre-populated with title, and autofocused, with cursor at end.
This may have been a regression from #334, or maybe it was just missed earlier.

Fixed by https://github.com/subconsciousnetwork/subconscious/pull/341


Fixed hardware ray tracing issue

fixes xverse-engine/XV3DGS-UEPlugin #31
In the custom material function discard was changed to alpha = 0.0f.
Because discard does not seem to be supported in HW ray tracing.

Hello pixelpunk,
I have issue with my unreal 5.2 with hardware raytracing
and I tried your commit with two binary files chang but it doesn't show any different with my project,
Is there anything for me to do more then changing M_GS_relight.uasset / M_GS_unlit.uasset in plugins?

Yes, that's all that changed.
On both materials it should change in this custom node:

from discard to alpha = 0.0f;
Which errors do you have in the shader of the original branch?

Implimenting this fix also works for me. Although I found I have the edit
if (power > 0.0f) 		discard;
to be if
(power > 0.0f)
   	power = 0.0f;

Yes. I am not an HLSL expert myself. But as far as I understand is that the discard operation is a rasterize operation, which is not supported in SM5+ raytracing.
So instead of discarding the pixel, we set it to be transparent. That adds a bit to the shader costs but makes it work with h/w rt.
So please feel free to add it :)


SLURM 20.02.7 NOT AVAILABLE!

Slurm 20.02.7 not available on https://download.schedmd.com/slurm/ for a security issue. Anyone have the source, wget dont work

I find the source of Slurm 20.02.7 here: https://<IP_ADDRESS>/packages/slurm/slurm-20.02.7.tar.bz2
Change original wget from official slurm webside for:
wget https://<IP_ADDRESS>/packages/slurm/slurm-${SLURM_VERSION}.tar.bz2 --no-check-certificate && \
WARNING, ALTHOUGH THIS SOURCE WORK THIS NOT OFFICIAL SLURM WEBSITE


Update repositories.txt

@ArduinoBot

@ArduinoBot

Hello @Jeroen88. The automated system here only operates on open pull requests. Since your submission was already accepted and the pull request merged, the bot won't pay any more attention to this pull request.
But this human is happy to provide assistance. Was there something you needed from the bot?

Hi @per1234, so nice that not only bots are watching! Thank you for you reaction! I released a new version of my updated EasyOpenTherm Arduino library and thought that I should send the above comment. But from your reaction I do understand this is not needed? If I update the version in the library.properties file and push a new version to my Github main this is automatically seen by the bot? The active version should now be 1.1.0, could you confirm that? :)

from your reaction I do understand this is not needed? If I update the version in the library.properties file and push a new version to my Github main this is automatically seen by the bot?

That is correct. There is some information on publishing new releases here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#how-can-i-publish-a-new-release-once-my-library-is-in-the-list
The repositories are checked hourly, but since the Library Manager index is cached we give a conservative estimate of the release being available to all users everywhere within a day's time. When that doesn't happen, it is nearly always because the release was found to be non-compliant with the requirements. You can monitor the indexing at the dedicated logs web page for your library:
http://downloads.arduino.cc/libraries/logs/github.com/Jeroen88/EasyOpenTherm/

The active version should now be 1.1.0, could you confirm that?

I confirm:

@per1234 thank you so much, also for the links with information about releases. I was not aware of the automatic update of a new release. I will keep that in mind for the next release. Have a nice day!


[WIP] Speed up assets and accounts pages

Description
Running against the simulation DB with 196 Assets and 59 users, the existing code takes about 134s to load the asset page. With the changes introduced in this PR, the asset pages loading time is brought down to 53s, which is still pretty high.
Further Improvements

Time profiling to identify slow routines.

Related Items
Closes https://github.com/FlexMeasures/flexmeasures/issues/964

[X] I agree to contribute to the project under Apache 2 License.
[X] To the best of my knowledge, the proposed patch is not based on code under GPL or other license that is incompatible with FlexMeasures

The loading time for the asset page is still unacceptable. How we process our internal API responses needs some work, I believe. For example, for assets, we are going through considerable trouble to recreate Asset objects, from what our API gives us, without querying our database and keeping them out of our db session. But then we also assign to it an owner (via a db query), child assets (via recursively processing our internal API response), a parent (via a db query) and sensors (via a db query). This is all costing considerable time when loading the assets page.
I see a couple of options:

It would be a lot quicker to just query the asset table and have the objects live in the session.
Bypass the internal API altogether.
Stop loading owners, children and parents unless the UI needs them (the assets page doesn't use them), and have the response of the internal API include a sensor count so we don't need to query the sensor table.

Before you start work, know that I did a tech spike on these options, so I can quickly push some code once we decided.
@nhoening your input is desired.

All I want to maintain is that if possible we call the internal API, as then we know we use our one layer where authorization is defined.
One or two internal API calls per UI page load should suffice, of course. We can definitely change anything after that.
We should study if that approach is feasible for what the asset and account page needs to do.

I implemented option 1, such that we still call the internal API for the auth check, but then reload the Assets from the db instead of separately querying its parents, owner, children and sensors. This further reduces the loading times on the assets page (I saw loading times of 17 seconds now).

Should we run a profiler to check where the 17 seconds are spent?

I noticed that there are fewer assets in the /assets listing compared to before this PR, so there must still be something wrong. Also, the asset icons (which are based on the asset type) are gone.

I tried it out locally and found the same. It turns out that we were only considering the assets of the current_user and the PUBLIC assets were missing, as well. Added these two and updated the tests.

Reminder: this PR requires an API changelog entry.

Even with the changes introduced in this PR, the assets page didn't load so I look for other measures to speed up the loading:

Pagination. It's WIP, but the PoC is working. Still we need to send the number of rows that there are in total.
Limiting the fields that we are sending for the child assets. Before, we were sending the whole offspring when only the name (even the count) was enough.

I believe pagination for all our asset and sensor tables is needed.
It's a bigger operation but there are nice tutorials. I believe I recently looked some of them up.

Yes, I haven't worked with pagination in the past but SQLAlchemy has nice methods for this.
This PR implements a POC of pagination but it need a rethink on the API output. It's quite worth it I think.

@victorgarcia98  I tested the assets page here and it looks like your PoC of pagination is working great! I mean, it makes this admin feature usable again in our simulation site where the number of assets is really high. A very good start, and it gives us an approach which I hope we'll use across the UI in other pages!

You mentioned we "need to send the number of rows that there are in total" - I didn't see this happening in the network console. I see page=11&per_page=10&all_accessible=true. You mean the server needs to tell the client?
I found that search still works, but not when going to page 2 (then a 404 appears). Maybe the underlying number of rows would need an update (from the server)? Maybe this TODO would help with that.
Selecting the second page (with page size 10) leads to page=11. More elegant might be page=2 and the server deduces (using page size) that 11 is where to start getting the next items.
Love that you bring us to start using db.paginate()! It seems you are not using all features advertised on https://flask-sqlalchemy.palletsprojects.com/en/3.1.x/pagination/, however. Maybe pagination.total would be useful?

These are only some comments on pagination I had when understanding the approach
I believe this PR is doing useful things, but also a couple at the same time. Actually, can you re-write the PR description to reflect what things * are* part of this PR by now?
In essence, as it started in February, we should try to merge this soon, perfect or not. It makes something usable which is a pain to use atm. We can create follow-up issues, rather than build further here.

Thanks for the review and for trying it out.
I've fixed the issue that you encountered and updated the PR description to reflect the latest additions. Please, let me know if you find any other issue or have any change suggestion.


PMID:26366556

altered level of stress responsive gene mRNA during vegetative growth
decreased level of lipid metabolism gene RNA during vegetative growth

'altered level of stress responsive gene mRNA during vegetative growth' is FYPO:0004363 (we've also had 'increased' longer - FYPO:0002664)

decreased level of lipid metabolism gene RNA during vegetative growth FYPO:0004880

edit file: efec7cd516c8799b2c97b8f32feb60b54f957b00
release: 19d729c9796e57e7f473149f79135db5f54c5999


hyprctl devices: Get caps/num lock state

Describe your PR, what does it fix/add?
#7271
Adds caps/num lock state to hyprctl devices -j
...
{
  "address": "0x<the address>",
  "name": "<the name>",
  "rules": "",
  "model": "",
  "layout": "us",
  "variant": "",
  "options": "",
  "active_keymap": "English (US)",
  "capsLock": true/false,
  "numLock": true/false,
  "main": true/false
}
...

Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
No
Is it ready for merging, or does it need work?
Ready

Are you sure that these 1 and 4 is something that won't ever change / be different for some keyboard?
As far as I can see it's just the order from
https://github.com/hyprwm/Hyprland/blob/08cc063e175e48cea44d26b7e3762f4b8611f0c5/src/devices/IKeyboard.cpp#L13-L15
And here
Details

https://github.com/hyprwm/Hyprland/blob/08cc063e175e48cea44d26b7e3762f4b8611f0c5/src/devices/IKeyboard.cpp#L131-L134
[LOG] ApplyConfigToKeyboard for "logitech-usb-keyboard", hasconfig: 1
[LOG] Attempting to create a keymap for layout us,ru with variant  (rules: , model: , options: caps:escape,grp:toggle)
[LOG] Updating keyboard 6450bb5c1b00's translation state from a provided keymap
[LOG] xkb: LED index 0 (name Num Lock) got index 1
[LOG] xkb: LED index 1 (name Caps Lock) got index 0
[LOG] xkb: LED index 2 (name Scroll Lock) got index 2
[LOG] xkb: Mod index 0 (name Shift) got index 0
[LOG] xkb: Mod index 1 (name Lock) got index 1
[LOG] xkb: Mod index 2 (name Control) got index 2
[LOG] xkb: Mod index 3 (name Mod1) got index 3
[LOG] xkb: Mod index 4 (name Mod2) got index 4
[LOG] xkb: Mod index 5 (name Mod3) got index 5
[LOG] xkb: Mod index 6 (name Mod4) got index 6
[LOG] xkb: Mod index 7 (name Mod5) got index 7
[LOG] Updating keymap fd for keyboard Logitech USB Keyboard

it seems to match for me.
But will that always hold true? What if some mod is absent?

hm, right, worth checking...

So would this be fine?
((k->modifiersState.locked & (1 << xkb_map_mod_get_index(k->xkbKeymap, XKB_MOD_NAME_CAPS))) == 2 ? "true" : "false"),
((k->modifiersState.locked & (1 << xkb_map_mod_get_index(k->xkbKeymap, XKB_MOD_NAME_NUM))) == 16 ? "true" : "false")

I think so, yes.
But instead of == 16 and == 2, which are tied to an index, have > 0.
As we do a bitwise AND with a number that's 1 with INDEX zeros after in binary (1 << INDEX), either there is 1 on INDEX position in .locked and the result will be positive, or there is 0 on that position, so the rest doesn't matter and will be 0 after &.


fix(is-npm): support more ways of importing + non-standard import names

Currently, the is-npm codemod assumes that developers name the imported members isNpm, isYarn and isYarnOrNpm. However, there are two ways in which developers could alter the imports that can't be handled by the codemod:
// ESM
import { isNpm as banana, isYarn as pear, isNpmOrYarn as strawberry } from 'is-npm';
import * as banana from 'is-npm';

// CJS
const { isNpm: banana, isYarn: pear, isNpmOrYarn: strawberry } = require('is-npm');
const banana = require('is-npm');

Moreover, by relying on hardcoded names, we also could potentially make unsafe modifications to developer code (they could have an isNpm variable themselves which is different from the imported one and has a different meaning)
This PR makes the codemod detect the imported names dynamically so that it supports the styles above. It also adds test cases to handle the new styles.
The PR introduces the getImportIdentifierMap helper which creates a map like this:
// import { isNpm as banana, isYarn as pear, isNpmOrYarn as strawberry } from 'is-npm';
const map = {
  isNpm: "banana",
  isYarn: "pear",
  isNpmOrYarn: "strawberry"
}

// import * as banana from 'is-npm';
const map = {
  [Symbol(NAMEPSACE_IMPORT)]: "banana"
}

This helper should be useful for cases where a module exports multiple names and const { identifier } = removeImport() is not sufficient.
There is some duplication in the codemod code, as the "individual name import" and "namespace import" cases need to be handled separately. However, since I suspect that this issue will also apply to other codemods, I believe the duplication is fine for now — we can figure out better abstractions as we continue improving the mods.
Thanks for reading!

Nice, thanks!


Wrap model in object class and refactor data changes in head menu

#251

Can put some of the sc.util.domain function on here possibily or a similar construction

Close this for now, replaced in #284


Add random number module

Should lower to a Hugr extension which in turn lowers to the corrrsponding runtime functions

related #445


Add arguments from Sandbox.create to exec protos

Describe your changes
In an effort to provide all the functionality in Sandbox.create to Sandbox.exec, this commit adds proto definitions for timeouts, secrets, and a working directory.
 Backward/forward compatibility checks

Check these boxes or delete any item (or this section) if not relevant for this PR.

[x] Client+Server: this change is compatible with old servers
[x] Client forward compatibility: this change ensures client can accept data intended for later versions of itself

Note on protobuf: protobuf message changes in one place may have impact to
multiple entities (client, server, worker, database). See points above.

@prbot approve


xds: Validate NPHDS updates before upserting

This should catch recent errors such as the one reported in #3825.
@rlenglet @jrajahalme  I played around a bit with this locally but couldn't reproduce #3825, so not sure what conditions are necessary for it. In the mean time we can certainly add some better validation / logging as per this commit.

test-me-please

Previous CI run was successful, I just rebased and updated strings per @rlenglet 's comments.

Backport #3856


Bad CMake executable "C:\Program Files\CMake\bin\cmake.exe".

Brief Issue Summary
I had been using the extension for several months with little issue.  One day, it stopped working.  I get this error:
Bad CMake executable "C:\Program Files\CMake\bin\cmake.exe". Is it installed or settings contain the correct path (cmake.cmakePath)?
That path is correct, and I can still run cmake from the command line using that absolute path, as well as by the command line finding it in my PATH.
Expected:

Push Configure button
Project is configured.

Apparent Behavior:

Push Configure button
Error pops up. (text given above).

CMake Tools Log

2019-05-16T00:08:57.844Z [debug] [rollbar] Updated Rollbar payload {"environment":"production","packageJSON":{"name":"cmake-tools","version":"1.1.3"},"client":{"code_version":"1.1.3"},"platform":"win32"}
2019-05-16T00:08:57.957Z [debug] [kit] Reading kits file C:\Users\joee\AppData\Local\CMakeTools\cmake-tools-kits.json
2019-05-16T00:08:57.957Z [debug] [kit] Not reading non-existent kits file: c:\Users\joee\dev\cmaketest\.vscode\cmake-kits.json
2019-05-16T00:08:57.994Z [info] [kit] Successfully loaded 12 kits from C:\Users\joee\AppData\Local\CMakeTools\cmake-tools-kits.json
2019-05-16T00:08:57.996Z [debug] [main] Safe constructing new CMakeTools instance
2019-05-16T00:08:57.996Z [debug] [variant] Constructing VariantManager
2019-05-16T00:08:57.998Z [debug] [main] Constructing new CMakeTools instance
2019-05-16T00:08:57.998Z [debug] [main] Starting CMakeTools second-phase init
2019-05-16T00:08:57.998Z [debug] [rollbar] Checking Rollbar permissions
2019-05-16T00:08:57.998Z [debug] [rollbar] Rollbar enabled?  true
2019-05-16T00:08:58.033Z [info] [variant] Loaded new set of variants
2019-05-16T00:08:58.034Z [debug] [main] CMakeTools instance initialization complete.
2019-05-16T00:08:58.036Z [debug] [kit] Reading kits file C:\Users\joee\AppData\Local\CMakeTools\cmake-tools-kits.json
2019-05-16T00:08:58.051Z [info] [kit] Successfully loaded 12 kits from C:\Users\joee\AppData\Local\CMakeTools\cmake-tools-kits.json
2019-05-16T00:08:58.063Z [debug] [kit] Not reading non-existent kits file: c:\Users\joee\dev\cmaketest\.vscode\cmake-kits.json
2019-05-16T00:08:58.739Z [error] [main] Failed to get version information for CMake during upgarde
2019-05-16T00:09:04.013Z [debug] [extension] [6342] cmake.configure started
2019-05-16T00:09:04.013Z [debug] [extension] Start selection of kits. Found 13 kits.
2019-05-16T00:09:04.013Z [debug] [extension] Opening kit selection QuickPick
2019-05-16T00:09:07.778Z [debug] [extension] User selected kit  {"label":"VisualStudio.14.0 - x86","description":"Using compilers for VisualStudio.14.0 (x86 architecture)","kit":{"name":"VisualStudio.14.0 - x86","visualStudio":"VisualStudio.14.0","visualStudioArchitecture":"x86","preferredGenerator":{"name":"Visual Studio 14 2015"}}}
2019-05-16T00:09:07.779Z [debug] [rollbar] Updated Rollbar payload {"kit":{"name":"VisualStudio.14.0 - x86","visualStudio":"VisualStudio.14.0","visualStudioArchitecture":"x86","preferredGenerator":{"name":"Visual Studio 14 2015"}}}
2019-05-16T00:09:07.779Z [debug] [main] Injecting new Kit into CMake driver
2019-05-16T00:09:07.781Z [debug] [main] Run configure
2019-05-16T00:09:07.781Z [debug] [main] Saving open files before configure/build
2019-05-16T00:09:08.376Z [debug] [extension] [6342] cmake.configure finished (returned -1)
2019-05-16T00:09:38.911Z [debug] [extension] [9226] cmake.viewLog started
bug] [extension] [5962] cmake.viewLog started
2019-05-16T00:06:42.724Z [debug] [extension] [5962] cmake.viewLog finished (returned undefined)
2019-05-16T00:07:54.282Z [debug] [extension] [5563] cmake.configure started
2019-05-16T00:07:54.282Z [debug] [main] Run configure
2019-05-16T00:07:54.282Z [debug] [main] Saving open files before configure/build
2019-05-16T00:07:54.894Z [debug] [extension] [5563] cmake.configure finished (returned -1)
2019-05-16T00:08:01.181Z [debug] [extension] [3999] cmake.configure started
2019-05-16T00:08:01.181Z [debug] [main] Run configure
2019-05-16T00:08:01.182Z [debug] [main] Saving open files before configure/build
2019-05-16T00:08:01.769Z [debug] [extension] [3999] cmake.configure finished (returned -1)
2019-05-16T00:08:05.661Z [debug] [extension] [1908] cmake.configure started
2019-05-16T00:08:05.662Z [debug] [main] Run configure
2019-05-16T00:08:05.662Z [debug] [main] Saving open files before configure/build
2019-05-16T00:08:06.260Z [debug] [extension] [1908] cmake.configure finished (returned -1)
2019-05-16T00:08:07.230Z [debug] [extension] [8321] cmake.configure started
2019-05-16T00:08:07.233Z [debug] [main] Run configure
2019-05-16T00:08:07.233Z [debug] [main] Saving open files before configure/build
2019-05-16T00:08:07.790Z [debug] [extension] [8321] cmake.configure finished (returned -1)
2019-05-16T00:08:18.032Z [debug] [extension] [4776] cmake.viewLog started
2019-05-16T00:08:18.110Z [debug] [extension] [4776] cmake.viewLog finished (returned undefined)
2019-05-16T00:08:53.117Z [debug] [extension] [4252] cmake.resetState started
2019-05-16T00:08:53.118Z [debug] [extension] [4252] cmake.resetState finished (returned undefined)
2019-05-16T00:08:53.168Z [debug] [extension] Deactivate CMakeTools
e.setVariant finished (returned false)
2019-05-15T23:15:01.394Z [debug] [extension] [2983] cmake.setVariant started
2019-05-15T23:15:04.686Z [debug] [extension] [2983] cmake.setVariant finished (returned false)
2019-05-15T23:16:33.379Z [debug] [extension] [7517] cmake.setVariant started
2019-05-15T23:16:37.191Z [debug] [main] Active build variant changed
2019-05-15T23:16:37.194Z [debug] [main] Run configure
2019-05-15T23:16:37.195Z [debug] [main] Saving open files before configure/build
2019-05-15T23:16:38.147Z [debug] [extension] [7517] cmake.setVariant finished (returned true)
2019-05-15T23:19:58.161Z [debug] [extension] [7558] cmake.configure started
2019-05-15T23:19:58.161Z [debug] [main] Run configure
2019-05-15T23:19:58.162Z [debug] [main] Saving open files before configure/build
2019-05-15T23:19:58.795Z [debug] [extension] [7558] cmake.configure finished (returned -1)
2019-05-15T23:25:26.998Z [debug] [extension] [1615] cmake.configure started
2019-05-15T23:25:27.000Z [debug] [main] Run configure
2019-05-15T23:25:27.000Z [debug] [main] Saving open files before configure/build
2019-05-15T23:25:27.638Z [debug] [extension] [1615] cmake.configure finished (returned -1)
2019-05-15T23:28:19.000Z [debug] [extension] [1460] cmake.clean started
2019-05-15T23:28:19.001Z [debug] [main] Run build clean
2019-05-15T23:28:19.637Z [fatal] [rollbar] Unhandled exception: Unhandled Promise rejection: clean Error: Impossible: CMake driver died immediately after successful configure {}
2019-05-15T23:29:42.344Z [debug] [extension] [6241] cmake.clean started
2019-05-15T23:29:42.345Z [debug] [main] Run build clean
2019-05-15T23:29:42.997Z [fatal] [rollbar] Unhandled exception: Unhandled Promise rejection: clean Error: Impossible: CMake driver died immediately after successful configure {}
2019-05-15T23:29:46.657Z [debug] [extension] [8631] cmake.build started
2019-05-15T23:29:46.658Z [debug] [main] Run build
2019-05-15T23:29:47.276Z [fatal] [rollbar] Unhandled exception: Unhandled Promise rejection: build Error: Impossible: CMake driver died immediately after successful configure {}
2019-05-15T23:29:55.438Z [debug] [extension] [2746] cmake.configure started
2019-05-15T23:29:55.439Z [debug] [main] Run configure

Platform and Versions

Operating System: Windows 10
CMake Version: 3.14.4
VSCode Version: 1.33.1
CMake Tools Extension Version: 1.1.3
Compiler/Toolchain: multiple.

Other Notes/Information
I uninstalled cmake, reinstalled the latest version.
I uninstalled VS code, reinstalled the latest version.
I may have had other Cmake extensions installed at some point, but they are all removed now.
I already tried resetting the extension just now.  No effect.

Hey, it looks like a broken cmake path, or wrong cmake executable or missing Flfiles to start cmake.
What happens if you call cmake -version from a terminal inside of vscode?
What does the cmake.cmakePath settings looks like?

It does look that way, doesn't it?
cmake -version from the vscode terminal works fine.
C:\Users\joee\dev>cmake --version
cmake version 3.14.4

CMake suite maintained and supported by Kitware (kitware.com/cmake).

cmake.cmakePath is the path to the file.  If I use this from the command line or the vs code terminal, it finds cmake, no problem.
I have also tried resetting this settings to the default, which is just "cmake".  That doesn't work either.  I have done all this for user settings and workspace settings.  No luck.
Bear in mind, this was working fine for months, and just started failing with this error one day.  I don't recall changing any settings right before it happened.

Sorry, I can not reconstruct your problem. There are no debug information to detect the return code or output of cmake. Maybe you could debug, an give me more detail whats happens in cmake-executable.ts function getCMakeExecutableInformation.

Thanks.  I'm going to try this soon -- hopefully next week.

I have also faced on same problem.
My environment is below.
Ubuntu 18.04 TLS
cmake 3.15.0 : /usr/local/cmake
vscode 1.37.0
And, my error log in vscode is below.

Bad CMake executable "". Is it installed or settings contain the correct path (cmake.cmakePath)?

I installed cmake again like below.
$ sudo ./cmake-3.7.2-Linux-x86_64.sh
$ sudo mv cmake-3.7.2-Linux-x86_64 /opt
$ sudo ln -s /opt/cmake-3.7.2-Linux-x86_64/bin/* /usr/bin

After that, it seems that vscode recognize cmake and cmake-tools also recognize cmake.

I installed cmake again like below.
$ sudo ./cmake-3.7.2-Linux-x86_64.sh
$ sudo mv cmake-3.7.2-Linux-x86_64 /opt
$ sudo ln -s /opt/cmake-3.7.2-Linux-x86_64/bin/* /usr/bin

After that, it seems that vscode recognize cmake and cmake-tools also recognize cmake.

It seems that my problem depends on vscode.
It seems that vscode doesn't recognize cmake which is not path to /usr/bin

@nackdai your environment says you put cmake in /usr/local not /usr/local/bin, is that correct?  Is /usr/local in your $PATH?  The extension only auto-detects cmake if it's in your $PATH.

Sorry, I miss-typed.

I installed cmake as /usr/local/bin/cmake and set /usr/local/bin/ in my $PATH.
But, in that case, it seemed that cmake was not detected automatically.

I removed cmake from /usr/local/bin/cmake and installed cmake again like below

$ sudo ./cmake-3.7.2-Linux-x86_64.sh
$ sudo mv cmake-3.7.2-Linux-x86_64 /opt
$ sudo ln -s /opt/cmake-3.7.2-Linux-x86_64/bin/* /usr/bin

In that case, it seems that cmake is detected automatically.
What difference are there between 1. and 2.?

The extension uses which cmake to find the path to cmake.  There should have been no difference between the locations if your $PATH includes /usr/local/bin

I installed cmake as /usr/local/bin/cmake and set /usr/local/bin/ in my $PATH.
But, in that case, it seemed that cmake was not detected automatically.

In above case, cmake tools ran after I set cmake path directly like below.
[Settings]->[Extensions]->[CMake Tools Configuration]->[CMake:Cmake Path]
/usr/local/bin/cmake

I finally got around to playing with this today.  I started with a fresh install of windows 10 (I was required to upgrade), cmake, VS code, the plugin -- everything.  I still got this error.  I wondered if the plugin might not like a cmake path with spaces in it, since my path did.  I tried uninstalling / reinstalling cmake in c:\cmake, and the problem went away.
It appears that the plugin is not currently compatible with the default install folder on Windows.  It'd be nice if it could support spaces in that path.
I really do wonder how I'm the only one filing a defect about this if that is all it was.
I also wonder how I had it working before, and then it stopped suddenly.  I don't recall moving my cmake installation.  I would like to think that the plugin used to support spaces in the path, and then a bug was introduced that broke that, and my updating the extension on my PC introduced the problem for me.  That does not seem likely, but that's all I've got.

The extension does work with a version of CMake that has spaces in the path, so I think there's some other variable causing the problem.  Can you share your settings?

Sure.  It's a fresh VS.code install.  I haven't set very much.  The difference between working and not was where cmake was installed.
{
    "cmake.sourceDirectory": "${workspaceRoot}/projects/projname",
    "cmake.buildDirectory": "${workspaceRoot}/projects/projname",
    "cmake.configureOnOpen": true
}

What do you get when you run cmake --version?

(For context, I'm trying to emulate the code path that you're going through. Something seems to have failed around this point where we are detecting your CMake version. Note that this code has changed a little bit in version 1.2.0 which is being released this week, but I am testing on 1.1.3 to try to figure out your issue.)

cmake version 3.16.0-rc2
That matches the version on the cmake install packages that I used for both "c:\program files\cmake" and "c:\cmake".
I did just notice that I used their .msi for the program files one, and the zip file for the c:\cmake one, which works.  There could be a difference there, but it seems unlikely.

If you're using a custom cmake path, I didn't see it in the settings you've shared.  How are you specifying cmake.cmakePath?  Are you using \\ for slashes in the json?  e.g.: C:\\program files\\cmake\\bin\\cmake.exe

You're right.  I'm not currently setting cmake.cmakePath.  I played around with that quite a bit, using \\ and /.  I could not get it to work before -- I generally saw the "Bad CMake executable" error.
Now that it is working, I see it log the following in the output:
[proc] Executing command: C:\\cmake\\cmake-3.16.0-rc2-win64-x64\\bin\\cmake.exe --build ...
On the settings page, I can leave it with the default Cmake Path, "cmake", and it works.  I can also enter "c:\cmake\cmake-3.16.0-rc2-win64-x64\bin\cmake.exe", which appears in the json as "c:\cmake\cmake-3.16.0-rc2-win64-x64\bin\cmake.exe", and it works.  If I introduce a typo, I start getting this error again.  This seems correct, now.
However, I'm pretty sure I tried all of this before when cmake was in "c:\program files\cmake", and I could not get it to work.
I do have cmake.exe in my path, and at one point I had to set 'CMAKE_ROOT`.   But I don't think those help the plugin find the binary.
Are you not able to reproduce the problem with cmake installed under "c:\program files"?

Are you not able to reproduce the problem with cmake installed under "c:\program files"?

Correct, I cannot repro the problem with cmake installed under C:\Program Files.  And the extension does not check CMAKE_ROOT when looking for the binary.

I tried re-installing from the msi to "C:\program files\cmake\bin\cmake.exe".  I can type that into the command line with quotes, and the shell finds and runs it fine.  The extension does not find it.
If I point the extension at my "c:\cmake\cmake-3.16.0-rc2-win64-x64\bin\cmake.exe", it works.  If I rename that folder (It's from the zip, not the msi) to "C:\cmake good\cmake-3.16.0-rc2-win64-x64\bin\cmake.exe" the extension finds it.  This rules out my theory of spaces being a problem.
That leaves the possibility of the .msi being "bogus" somehow.  If I install the msi into c:\cmake, the extension finds it.
If I copy the .zip contents to "C:\Program Files\cmakeb\cmake-3.16.0-rc2-win64-x64\bin\cmake.exe" and point the extension at it, it finds it.
That seems to rule it down to something very special about "C:\Program Files\cmake\bin\cmake.exe".  After a fresh install of windows and cmake, I can't imagine what would be special about it.
It seems to be something very specific about "C:\Program Files\cmake\bin."
I tried moving the zip contents to "C:\Program Files\cmake\cmake-3.16.0-rc2-win64-x64\bin\cmake.exe".  It finds it.  That's a little different than the "specific" broken path.
I take that same zip contents and put them in "C:\Program Files\cmake\bin\cmake.exe", and the extension cannot find it.
I rename the "bin" folder "bina", as follows: "C:\Program Files\cmake\bina\cmake.exe".  The extension can find it.
Every test, I tried running the same path on the command line, and it worked, (just to double check for a typo)
This seems to imply that it doesn't matter if it's from the zip or the msi.  All that matters is if it is installed to c:\Program Files\cmake\bin.  It won't find it there.  Anywhere else, and it will find it.  This is pretty absurd.
This is a fresh install of Windows 10.  Before, I was seeing this (although I didn't test all these cases) on Windows 7.  That is one specific "bug".  I don't know what else I can try.  That is all I have time for at the moment.  At least I have a workaround.

@jeverton  I have a similar issue in Ubuntu https://github.com/microsoft/vscode-cmake-tools/issues/838
Also at present I can't get the extension to work on Windows 10, VS2019 and the latest CMake 3.16 at all.

I'm also experiencing this issue on Ubuntu:
I installed vscode/cmake from snap packages

$ cmake --version
cmake version 3.16.0-rc4
CMake suite maintained and supported by Kitware (kitware.com/cmake).

But I got this error from the vscode extension:

Bad CMake executable "/snap/bin/cmake". Is it installed or settings contain the correct path (cmake.cmakePath)?

I checked my path

echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

I checked my cmake

$ which cmake
/snap/bin/cmake

@hdf89shfdfs For snaps, please, check: #838

I also encountered this problem when using the Remote Development Extension. It does not work with the path set to be ${userHome}/.local/bin/cmake.

I have the same problem on KDE Neon (Linux). I uninstalled Cmake tools, reinstalled, no luck,
From VS Code terminal:
$ cmake --version
cmake version 3.16.3
$ which cmake
/usr/bin/cmake
The error that pops up is:
Bad CMake executable "/home/foobar/Projects/git/MyProject/.dependencies/cmake-3.15.5/bin/cmake". Is it installed or settings contain the correct path (cmake.cmakePath)?
There is no .dependencies folder under MyProject, I double checked.
This is on a fresh machine, fresh install of VSCode, no customized settings, just installed the extension and tried to open an existing project.

I'm sorry, we haven't been able to reproduce this problem.

I'm sorry, we haven't been able to reproduce this problem.

I faced the same problem on windows. I fixed it by :

removing cmake.cmakePath from the settings.json file
resetting the extension (CTRL+SHIFT+P then "CMake: Reset CMake Tools Extension State (For troubleshooting)"
checking that cmake is in my Path
just putting "cmake" (without the brackets) in the extension settings GUI

@Eight9inerEcho, do you have the same problem on a small project that you create from scratch, for example with the command "CMake: Quick Start" in the palette?
Can you increase the logging verbosity with "cmake:loggingLevel": "Debug", reload the project and share us the text in the "CMake/Build" output channel?

I do have the same issue.
Verbosity set to debug. Below is a screenshot of an attempted build

I really think this is a problem with VS code having the wrong path for the Cmake executable. How can I find out where the Cmake executable was installed by the toolchain so I can point to in manually?

About finding the exact cmake executable installed by the toolchain, I don't know how to do that other than searching on your system for all cmake and trying to guess which one. Maybe there is documentation about that particular toolchain or if you run it again may give some path indication.
I am still thinking of what else can happen here.

mark

sudo ln -s /opt/cmake-3.7.2-Linux-x86_64/bin/* /usr/bin
Thanks, this solves my problem.
I initially used cmake 2.16 with the latest stable version of vscode, the cmake tools does not work.
After uninstalling the cmake with apt remove cmake and installed the latest cmake from official website binary, it still does not work.
It only works after I make a link from the installation directory to /usr/bin.

Glad to hear that you are unblocked @Bill0412. I'll wait to hear from other users on this thread, hopefully they will be able to use the same command and be unblocked. Then I will close his report.

I'm on a M1 mac and I get the same error. I installed cmake via brew and it is placed under /opt/homebrew/bin/cmake.  Linking to /usr/bin is not possible on macOS, but I've tried to link to /usr/local/bin to no avail.

@wAuner, I understand that (and I have no idea why yet) the link command didn't work for you but did you also define "cmake.cmakePath"? Just double checking.

Yes I’ve tried that too (to define it with the full path, although cmake already is in my path),  but that didn’t help. Sometimes it finds it, sometimes not. Seems very unstable

I was also getting the same error in ubuntu 20. I was able to find a consistent way to reproduce the issue.
Let us assume that cmake extension is working properly in your pc. Following these steps you can get the Bad cmake executable error:

Go to File-> Preferences->Settings and search for Update:Mode
Normally it is set to default. You need to change it none.
After this, vscode will prompt you to restart it. After restart, CMake shouldn't work and you should get the Bad cmake executable error.

How to fix:

Change the Update Mode in vscode back to default & exit.
Remove your existing cmake installation sudo snap remove cmake
Reinstall cmake sudo snap install cmake --classic
Restart vscode. It should now detect cmake.

I don't understand why the update setting screws up cmake. It will be nice if someone can dig into this.


This article also talks about user-assigned NAT Gateway

Hello there,
The article's tittle is "Managed NAT Gateway", but it is also explaining how to set up AKS to use a user-assigned (byo).
This is confusing. I would improve the documentation by selecting one of the below options:

You change the article's title to something like this: Managed and user-Assigned NAT Gateway for AKS
You create another article dedicated exclusively to user-Assigned NAT Gateway

Thanks a lot!
Agustin!

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

ID: e3ea12e7-6e6d-cfa1-b094-2f33e2e7b64b
Version Independent ID: cd0f7701-6a0a-425c-1da2-29683db39ef9
Content: Managed NAT Gateway - Azure Kubernetes Service
Content Source: articles/aks/nat-gateway.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: juda

Hi @amantaras, thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and update as appropriate

#reassign:schaffererin


Remove duplicate compact and iscompact in jagged

Hi, while trying to fix a bug I have in my analysis, I noticed this double-implementation of compact and iscompact in jagged.py. the exact same 27 lines are repeated 2 times, I thought it might be good to fix that.
Cheers!

You're right—that must have been some weird copy-paste thing. Thanks!


Kinematics cost function tutorial fails due to IK solver not supporting cost functions

When I tried to run the Kinematics cost function tutorial when testing https://github.com/moveit/moveit2_tutorials/pull/984, I got this error:
[ERROR] [1730606304.619170929] [kinematics_cost_fn_tutorial.moveit.core.kinematics_base]
This kinematic solver does not support IK solution cost functions

(it also fails on main, I checked)
Any ideas?

Gah, no, you have to change the solver to something like BioIK -- I should RTFM.


Remove test dependency on local remotes server

Use the configurable resolver to short-circuit the localhost requests for the
remote test schemas.

Thanks for this @leshill! Now I feel silly for wasting time getting Python running alongside Ruby on CI :)


When there are multiple dependent links and those services are in the stopped state, those services cannot be deleted

Describe the bug
When there are multiple dependent links and those services are in the stopped state, those services cannot be deleted.
Steps to reproduce

Create multiple services that have multiple dependent links;
Stop all services;
Delete all services.

Result

Environment

Walrus version: v0.4.0

Duplicate of https://github.com/seal-io/walrus/issues/1636

Environment

Walrus version: main 8048eb2af52e636e42e656ee507d875cb83999d9
UI version: dev-33d2ecd

Test Result: pass


Removed unwanted methods from SKABase and SKAMaster

Not sure why PR #82 was closed, and most of those changes added again in this new PR? Also, some comments in that PR have still not been addressed.

That was due to some misunderstanding about how github works.

Please add a proper description and title to the PR. "Aditya" is not a good title.

Agree. Cannot remember how "Aditya" was entered. Might be some copy paste error. Will take care in future.

Agree. Cannot remember how "Aditya" was entered.

Github automatically uses the branch name as the title for a new PR if it has more than one commit.  Click the Edit button to the right of the description to fix both the title and the detailed description.

Closing this PR as this branch is stale now.


[GPUCodegen] Characterize performance for dynamic fused self attention

We would like to know performance characteristics for dynamic parameters for fused self attention.
M dynamic lengths :  1024, 2048, 3072, 4096, 5120, 6144, 7168, 8192, 16384
M tile sizes : 16, 32, 64 and 128
K1 values to be used : 64, 128
K2 values : this should be equal to M to be self-attention

For K1/N you can use 64/128. You can probably ignore 256.

Do we want this done for MI300X in CPX ?

Do we want this done for MI300X in CPX ?

SPX/CPX either on MI300X should be fine.

I ll start with CPX then...

Either should be fine, but I think we have SPX available more easily. The trends should be the same.

!dtype = f16
!Q     = tensor<1x?x64xf16>
!K     = tensor<1x?x64xf16>
!V     = tensor<1x?x64xf16>
!O     = tensor<1x?x64xf16>

#tuning = #iree_codegen.compilation_info<lowering_config = #iree_gpu.lowering_config<{ workgroup = [1, 64, 0, 0, 0], reduction = [0, 0, 0, 0, 32] }>, translation_info = #iree_codegen.translation_info<LLVMGPUVectorDistribute workgroup_size = [64, 4] subgroup_size = 64 ,{mma_schedule = #iree_gpu.mma_schedule<intrinsic = #iree_gpu.mma_layout<MFMA_F32_32x32x8_F16>, subgroup_m_count = 4, subgroup_n_count = 1> , llvm_func_attrs = { "amdgpu-waves-per-eu" = "2","denormal-fp-math-f32" = "preserve-sign" }}>>

#Q = affine_map<(b, m, n, k1, k2) -> (b, m, k1)>
#K = affine_map<(b, m, n, k1, k2) -> (b, k2, k1)>
#V = affine_map<(b, m, n, k1, k2) -> (b, k2, n)>
#S = affine_map<(b, m, n, k1, k2) -> ()>
#O = affine_map<(b, m, n, k1, k2) -> (b, m, n)>

func.func @main(%Q : !Q, %K : !K, %V : !V) -> !O {
  %scale = arith.constant 1.0 : !dtype
  %c1 = arith.constant 1 : index
  %size1 = tensor.dim %Q, %c1 : !O
  %empty = tensor.empty(%size1) : !O
  %O = iree_linalg_ext.attention
       { indexing_maps = [#Q, #K, #V, #S, #O]
         ,compilation_info = #tuning
       }
       ins(%Q, %K, %V, %scale : !Q, !K, !V, !dtype) outs(%empty : !O) {
          ^bb0(%score: f32):
            iree_linalg_ext.yield %score : f32
        } -> !O
  return %O : !O
}

I ve managed to generate IRs as above but its not compiling as of now.
Im suspecting Im missing something much simpler given that dynamic attention kernels are supported., yes?
is there any test/example of a dynamic attention kernel in the codebase?

Maybe we should try static sizes for those shapes. Making the shape dynamic will not give us as clear a signal yet.

@Groverkss @MaheshRavishankar ,
following https://github.com/iree-org/iree/pull/18937,
I think there is some misalignment.
IIUC PR,
its looking at shape of the attention, to whether to use fused attention or not.
Is this for decode attention ?
If so, I think this should be changed to
M = 16, 32, 64, 128 sort of lower range.
K2 = 1024, 2048, 3072, 4096, 5120, 6144, 7168, 8192, 16384

Here is the data:
https://amdcloud-my.sharepoint.com/:x:/g/personal/mkarunar_amd_com/EUn8SRgVutlAtODEUMPKYW0BEM56zrKPlPYyrxKCce8DvQ?e=1EFf0a&nav=MTVfezBCNjA4MzJCLTM1MDEtNEUzOS1BRDM3LTYxMDdCRDI1NTVCRX0

^ Please use public links when working in open source. Google Drive files and GitHub gists are both good options. Uploading zip files to issues is also an option, but binary files can be security risks.

iree_attention_decompose.xlsx


v1.0.7

Adds the (--publisher|-p) flag to the search command
Fixes various bugs surrounding mirror selection
Massive refactor removing useless code & double usage of code, less prone to errors
Some speed up on search/download
Restructure GitHub Actions workflow

Pull Request Test Coverage Report for Build 154849294

47 of 154 (30.52%)  changed or added relevant lines in 2 files are covered.
11 unchanged lines in 1 file lost coverage.
Overall coverage increased (+23.4%) to 53.786%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libgen/download.go
28
74
37.84%

libgen/api.go
19
80
23.75%

Files with Coverage Reduction
New Missed Lines
%

libgen/download.go
11
50.0%

Totals

Change from base Build 154837792:
23.4%

Covered Lines:
277

Relevant Lines:
515

💛  - Coveralls


Using selectors in action creators.

I searched the issues and didn't find a similar issue.
Is it possible to use a selector within an action creator?
For instance, if I had a forms reducer and wanted to get values from a specific formId.
export const updateModule = moduleId => (dispatch, getState) => {
  const moduleUpdates = formSelector(getState(), moduleId);
  return axios.post(`${API_URL}/modules/${moduleId}`, moduleUpdates);
};

I'm sure it would function (not throw), but are there any repercussions using the selector here?

  Selectors are useful anywhere you have access to the Redux state tree.  That includes mapState functions, thunks, sagas, and even in reducers as well.  (And, they don't necessarily have to take the entire tree either - you can have selectors that work on a subset of the tree too.)
Selectors generally provide three main benefits:

Encapsulation of potentially complex lookup logic
Encapsulation of specific data locations in the state tree
Possible memoization of lookups, which is particularly helpful if there's expensive work being done (such as filtering or sorting of data).

Awesome!
Thanks for the quick response. I converted a pretty bloated container component to use reselect today and it was so quick and easy to update that I figured why not just use it everywhere I can.
Thanks again!

@markerikson What would happens if selectors are used in actions, regarding "Sharing Selectors with Props Across Multiple Components"?
For example, when I have a state indexed by unique ids:
const state = Immutable.Map({
    'id-1': {...},
    'id-2': {...},
})

The documentation leads me to believe I should create the selector with a factory each time I call an action, right? However, if I do so the memoization would not happen.
Right now, I'm using the example provided in https://github.com/reactjs/reselect#q-how-do-i-create-a-selector-that-takes-an-argument to fetch and transform things from the state which are indexed by a unique id.
I understand this approach is not optimal because if any sibling updates, it would recompute avery other sibling (in a lazy way).


Play/stream/download external video, links, torrent in Integrated player (mpv)

Describe your suggested feature
When clicked on .torrent file, any video then animetail should appear in (open in app) popup
& also there should be option to download/stream external torrent, links
& open any local video from *this_screen
Other details
*this_screen

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is a request regarding an extension, I should be opening an issue in the extension's repository.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I will fill out all of the requested information in this form.

That'd be a great implementation ngl


Disabling Terminal External Plugin Has No Effect

Description
What steps will reproduce the problem?

The spyder-terminal plugin is enabled despite disabling in Preferences->Plugins.

Start Spyder from conda environment using bootstrap
Disable Terminal in Preferences->Plugins
Restart Spyder
Observe error window. This is flashed rapidly and barely visible on the gif. A still shot is also attached.
Upon restart, observe that Terminal is still enabled

spyder_terminal_err.log
No QCoreApplication instance found. Application patches not applied.  This requires a new release of Spyder-terminal.

That's one thing, but I was talking about adding enable to the default options of Spyder-terminal:
https://github.com/spyder-ide/spyder-terminal/blob/7bafa8cc1b7dc82c46e13fdfbfd707b59ec42953/spyder_terminal/config.py#L18-L37
Since that option is missing, then Spyder can read/write it to disk when enabling/disabling the plugin.
I think that should solve the problem, according to what @dalthviz found.

I already tried that option, and it is not working.

Mmmh, that's bad news.
@andfoy, any ideas about this?

A while ago with @steff456  we did reached the same conclusion as Daniel, because of the current configuration implementation, an external plugin configuration is picked only after the plugin loads. In order to fix this, all configurations should be available at all times, regardless if a plugin has loaded. However, this requires a (potentially extensive and expensive) implementation of the configuration system that needs further discussion and implementation

Ok, so the solution for now is not allowing Spyder-terminal to be disabled in Preferences > Plugins, right?

Ok, so the solution for now is not allowing Spyder-terminal to be disabled in Preferences > Plugins, right?

Should we consider reverting the inclusion of spyder-terminal in the standalone applications until this is fixed? I don't know which is better: to have the plugin but unable to disable it, or not have the plugin yet...

@dalthviz @andfoy , wouldn't it be better for Spyder's config file to store the enabled state of all plugins (internal + external)? Rather than relying on the plugin's config file?

Ok, so the solution for now is not allowing Spyder-terminal to be disabled in Preferences > Plugins, right?

That could be a possibility. For that there is some missing code in the Plugins config page to also check for CAN_BE_DISABLED on external plugins A similar logic as is used for internal plugins:
https://github.com/spyder-ide/spyder/blob/9e545f8ac90fee862a95ca01b7e58c0517022683/spyder/api/plugin_registration/_confpage.py#L41-L43

Should we consider reverting the inclusion of spyder-terminal in the standalone applications until this is fixed? I don't know which is better: to have the plugin but unable to disable it, or not have the plugin yet...

I'm not sure either but at least we shouldn't show the option to disable the plugin if that can't be done

wouldn't it be better for Spyder's config file to store the enabled state of all plugins (internal + external)? Rather than relying on the plugin's config file?

That could be an interesting approach. It could be like a list of disabled plugins maybe or a dict where each entry key is the name of the plugin and has if the plugin is enabled or not as value?

When I saw this issue a while back I decided to just not allow Spyder-terminal to be disabled because at the end as it currently is a third party plugin people have to install it in order to use it. So it seems weird if someone install the plugin and disables it, because it will be the same as just uninstalling it. We could just prevent third party plugins to not be able to disable them for now while we think of a solution that is not that hard to implement.

Our proposal back a time ago was to create a higher-level configuration file that mapped each section to the place where it should looked for (external, internal, etc). By doing so, the main Spyder configuration file will be split into internal, external and even other categories such as project-wise configurations that might help users override global configurations per project. However, this needs more discussion. At least on my opinion, I'd prefer a well-implemented solution rather than a quick one

That could be an interesting approach. It could be like a list of disabled plugins maybe or a dict where each entry key is the name of the plugin and has if the plugin is enabled or not as value?

The issue with this approach is that we will need to create an instance of the plugin to get all its configuration, letting the "disable/enable" option just aesthetic and not reducing the amount of things that Spyder has to load at startup

Should we consider reverting the inclusion of spyder-terminal in the standalone applications until this is fixed?

I think Spyder-terminal is mature enough to be part of the installers. Since solving this problem the right way will require a good amount of work, I propose to add the necessary code to Spyder-terminal so that it creates terminals only if it's visible at startup.
In other words, if the user hides it and then restart Spyder, the plugin wouldn't do anything. This is not the same as a full teardown, but it's pretty close.

@dalthviz

That could be an interesting approach. It could be like a list of disabled plugins maybe or a dict where each entry key is the name of the plugin and has if the plugin is enabled or not as value?

That's exactly what I was thinking. In principle, the Spyder application only needs to know two things with regard to plugins: 1) is it available (code is installed); and 2) is it enabled. The plugins themselves don't need to control these things, and the Spyder application wouldn't need to load a plugin in order to get that information.

@andfoy

Our proposal back a time ago was to create a higher-level configuration file that mapped each section to the place where it should looked for (external, internal, etc). By doing so, the main Spyder configuration file will be split into internal, external and even other categories such as project-wise configurations that might help users override global configurations per project. However, this needs more discussion. At least on my opinion, I'd prefer a well-implemented solution rather than a quick one

I agree that a well-implemented solution is better than a quick one. Why do we need to segregate the internal/external plugins? I also noticed that the internal plugin configurations are included in Spyder's configuration file, but external plugins have their own configuration file in their own directory. Is there a reason why we treat these plugins differently? I understand that "internal" plugins are included in Spyder's source code, but it seems to me that regardless of whether a plugin is "internal" or "external" they should be treated exactly the same. Perhaps each plugin should have its own configuration file in its own directory, does not have an enabled configuration, but Spyder's configuration has [plugins] with a list of available plugins and their enabled state.
I don't know what a "higher-level configuration file" would look like, but it seems to me that only a single configuration file for Spyder is best, even for project-wise configurations. For multi-project implementation, I think the same paradigm as for plugins would work: a [projects] section lists the currently open project(s), but individual projects maintain their own configuration files (as I think they currently do, but are unused?). However, in this case, there is just a hierarchical preference, where Spyder has global settings which are overridden by a project's configuration, depending on which project is open (in single project support) or which project has focus (in multi-project support)

@steff456

So it seems weird if someone install the plugin and disables it, because it will be the same as just uninstalling it.

I agree, except that for the macOS app, the user cannot choose to install/uninstall it. I think we've discussed before the desire to have a package manager in Spyder, in which case users would be able to install/uninstall Python packages. When we implement this, I think this idea could also be extended to Spyder's plugins.

That could be an interesting approach. It could be like a list of disabled plugins maybe or a dict where each entry key is the name of the plugin and has if the plugin is enabled or not as value?

The issue with this approach is that we will need to create an instance of the plugin to get all its configuration, letting the "disable/enable" option just aesthetic and not reducing the amount of things that Spyder has to load at startup

I don't completely understand all the plugin mechanisms, so perhaps I'm mistaken, but wouldn't having Spyder maintain a list of available plugins and whether they are enabled mean that Spyder does not have to load the plugin to get that information? Only if a plugin is enabled does Spyder need to load the plugin, and only in that instance does Spyder need the plugin to serve up its configuration?

Should we consider reverting the inclusion of spyder-terminal in the standalone applications until this is fixed?

I think Spyder-terminal is mature enough to be part of the installers. Since solving this problem the right way will require a good amount of work, I propose to add the necessary code to Spyder-terminal so that it creates terminals only if it's visible at startup.
In other words, if the user hides it and then restart Spyder, the plugin wouldn't do anything. This is not the same as a full teardown, but it's pretty close.

@ccordoba12 whether or not Spyder-terminal is enabled/disabled, closing the Terminal pane is honored, i.e. upon restart the Terminal widget is not visible and remains deselected in View->Panes->Terminal. I'm sure that the plugin is still loaded, but as far as the user is concerned, it may have the same effect. So maybe this is good enough for now? or just disable the enable checkbox in Preferences?

To add a bit of extra context to this issue: On my company laptop, the process started by spyder-terminal gets stuck and starts using 100% CPU. While this is probably an issue with my laptop, rather then with spyder-terminal, it would be nice if I could disable the plugin (or at least not start the server process).
Even on my personal laptop, the server process also keeps using some small amount of CPU all the time, even though I am not using it, or even interacting with spyder. So also here I would like to be able to disable the plugin.


Initial dependabot configuration

Codecov Report

Merging #113 (392891d) into master (ed5e46b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #113   +/-   ##
=========================================
  Coverage     76.71%   76.71%
  Complexity      306      306
=========================================
  Files            54       54
  Lines           932      932
=========================================
  Hits            715      715
  Misses          217      217

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 ed5e46b...392891d. Read the comment docs.


external functions --> SmartContractAudit1.0

Codecov Report

Merging #203 into contracts/SmartContractAudit1.0 will decrease coverage by 19.2%.
The diff coverage is 54.54%.

@@                         Coverage Diff                          @@
##           contracts/SmartContractAudit1.0     #203       +/-   ##
====================================================================
- Coverage                             99.8%   80.59%   -19.21%
====================================================================
  Files                                    6        6
  Lines                                  508      500        -8
  Branches                                94       90        -4
====================================================================
- Hits                                   507      403      -104
- Misses                                   1       97       +96

Impacted Files
Coverage Δ

contracts/DutchExchange.sol
79.72% <54.54%> (-20.06%)
:arrow_down:

contracts/Tokens/TokenTUL.sol
77.77% <0%> (-22.23%)
:arrow_down:

contracts/ForTestingOnly/InternalTests.sol
77.77% <0%> (-22.23%)
: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 fbd8a27...77bb866. Read the comment docs.


Fix: module enablement; Import Key Test

what

Ensure module adheres var.enabled
fix tests and ensure examples_import_key_test is run in test suite

why

Resources were created even when var.enabled was false

references

Issue identified in https://github.com/cloudposse/terraform-aws-components/pull/340

/test all


pyansys.load_parameters errors

I am in win10 and the lasted pyansys,but when i use load_parameters ,the ansys shuted down and there are the errors. Thanks a lot

I'll check this out.  Which version of ANSYS are you using?

Just ran the following with no issues.  Would it be possible for you to share the database that caused the issue?
>>> import pyansys
>>> ansys = Mapdl()
'0.39.10'
>>> ansys.load_parameters()
2019-12-16 18:39:30,721 [INFO] pyansys.mapdl: *** NOTE ***                            CP =       0.266   TIME= 18:39:30
 Write parameters to file= C:\Users\alex\AppData\Local\Temp\ansys\paramet
 ers.parm.

 *** NOTE ***                            CP =       0.266   TIME= 18:39:30
 Parameters written.  Lines= 5.

Following up again.  Still having issues with this?  If not, I'd like to close this issue due to inactivity.


URL Parsing Error

Describe the bug
When working on a solid vite starter, I successfully managed to get everything a javascript version working on mac, thanks for everything that went into that! However, I shared with others and found a new unexpected behavior: on Windows new URL('file:' + '/path/to/something.cjs').href reports only double slashes which is inconsistent with the native behavior.
All thanks to @rturnq for tracking this one down
Link to the blitz that caused the error
https://stackblitz.com/edit/node-url-bug
Steps to reproduce

open https://stackblitz.com/edit/node-url-bug
see that file://path/to/something.cjs is logged

Expected behavior
I would expect file:///path/to/something.cjs to be logged (note the triple slash instead of a double slash)
Screenshots
https://cdn.discordapp.com/attachments/730114401427783713/874526003450503168/unknown.png
Platform
On a mac with chrome this works, but on windows it fails

Chrome 92.0.4515.107
Windows 10.0.19042 Build 19042

Additional context
This seems to be a difference in behavior between the browser native new URL feature, Firefox on windows reports the other way

see that file://path/to/something.cjs is logged

@modderme123  I see three slashes, maybe you are running a cached, old version?

This specifically only happens on Windows computers (on mac it works), and clearing cache doesn't help

@modderme123 Oh, sorry, I understand what you're saying now. It seems we're being bitten by a web compat bug. Thanks for reporting!

This is fixed now.


Updated composer from 1.5.2 to 1.5.5

Could not review pull request. It may be too large, or contain no reviewable changes.


Feature request Wifi transport for RP2040 W

Issue template

Hardware description: rp2040 pico W
Installation type: Platformio

Steps to reproduce the issue
I would like to use Wifi transport with a PicoW
Additional information
Is this a hard problem to solve? Or is it just that no one attempted it yet?

Hello @samuk, it should be easy to implement following the structure of any networked transport such as this one.
It is not in our roadmap, but contributions and PR are welcome.

Thanks, wouldn't I be using the existing https://github.com/micro-ROS/micro_ros_platformio/blob/main/platform_code/arduino/wifi/micro_ros_transport.cpp

Note to self. Maybe just drop Platformio & use micro-ros-arduino instead: https://github.com/micro-ROS/micro_ros_arduino/pull/1425

So it seems the task would be to get Microros running under https://github.com/earlephilhower/arduino-pico

@samuk - I haven't had a chance to try it yet with Pico W, but I understand that the pull request https://github.com/platformio/platform-raspberrypi/pull/36 @maxgerhardt has done all the heavy lifting to pull in arduino-pico.  On your VSCode terminal, type pio pkg install -g -p https://github.com/maxgerhardt/platform-raspberrypi and that re-adds the platform-raspberrypi with all the earlephilhower goodness.  Platformio haven't accepted the pull request due to licensing issues.

Thanks, unfortunately MicroROS doesn't run under Earlephilhower.. So that's the remaining task to get that running.

It runs under platform.io if you do the above command - I tried it
I just haven't had a chance to test Pico W with it with micro-ros

Yes I can install and run Earlephillhower and use it under platformio to flash the Pico. I can't get MicroROS to compile in that environment though.

Or maybe it was just the wifi transport I couldn't enable, it was a while ago that I tried.

Arduino RP2040 Connect is supported, and I have one, but am away for a while.  Will have a go hopefully next week.