Challenges for elastalert-kibana-plugin 1.4.0

For 7.10.0, 7.10.1, 7.10.2 zip, please recreate the zip file referring to the following issue.
Also, please check the operation properly before releasing.

https://github.com/Karql/elastalert/issues/1
https://github.com/Karql/elastalert/issues/8

Corresponding versions of 7.12.0, 7.12.1, 7.13.0, 7.13.1, 7.13.2, 7.13.3, 7.13.4 and 7.14.0 have not been released. You should be able to create it by referring to the following issue. Also, please check the operation properly before releasing. Even if you say you've released something that doesn't work, it's just garbage.

https://github.com/Karql/elastalert/issues/2
https://github.com/Karql/elastalert/issues/5
https://github.com/Karql/elastalert/issues/7

I have just released versions up to 7.14.0.

Even if you say you've released something that doesn't work, it's just garbage.
Have you confirmed that it is not working or just saying so?

Please release it after confirming the operation.

I have checked every single version.

So why I am asking you if something not working for you.

I've answered the question. Why is it a question again?

All you have to do is check the minimum operation. Don't you know that?


Minor fixes to improve getting started experience

Wow, this package looks awesome. I'm gonna spend next few days playing with it :-)
Here are couple minor fixes to improve getting started experience:

add .stack-work to .gitignore, this is standard practice for stack projects
fix duplicate ' in the "not found" error message which appears when running examples with 'check'
make all samples executable (cd examples && chmod +x *.hs), so they can also be run like ./example.hs without prefixing the command with stack

Thanks for the patch and have fun!


Goyo & Airline won't play well together

environment

vim: neovim v0.4.2
vim-airline: up-to-date through plugged
OS: OpenSUSE Tumbleweed (up-to-date as of Sept. 29 2019)
Have you reproduced with a minimal vimrc: Yes
What is your airline configuration:

set laststatus=2
let g:airline_theme='pencil'
let g:airline_powerline_fonts = 1
let g:airline_section_z = '%l of %L'
let g:airline_section_y = ''
let g:airline_extensions = []

(but this happens even if I remove all of the configuration lines)
if you are using terminal:

terminal: konsole
$TERM variable: xterm-256color
color configuration (:set t_Co?): (This variable isn't set for me?)

actual behavior
I started using airline recently. When I opened up nvim and I use Goyo (Goyo 80x100%), everything works as expected until I move focus to another window and do something there (usually moving another window will initiate it), and then when I re-focus on the nvim window, airline has re-appeared. I've tried :AirlineToggle but that doesn't help. I can get it to go away again by using Goyo 80x100% again, but I don't want to have to re-type that command every time I tab back in to type.
expected behavior
When I'm in the Goyo environment, the airline should go away completely and stay away until I leave the Goyo environment.

So what exactly does goyo do to disable airline?

Am 01.10.2019 um 02:05 schrieb dorgnarg<EMAIL_ADDRESS>
environment
vim: neovim v0.4.2
vim-airline: up-to-date through plugged
OS: OpenSUSE Tumbleweed (up-to-date as of Sept. 29 2019)
Have you reproduced with a minimal vimrc: Yes
What is your airline configuration:
set laststatus=2
let g:airline_theme='pencil'
let g:airline_powerline_fonts = 1
let g:airline_section_z = '%l of %L'
let g:airline_section_y = ''
let g:airline_extensions = []
(but this happens even if I remove all of the configuration lines)
if you are using terminal:
terminal: konsole
$TERM variable: xterm-256color
color configuration (:set t_Co?): (This variable isn't set for me?)
actual behavior
I started using airline recently. When I opened up nvim and I use Goyo (Goyo 80x100%), everything works as expected until I move focus to another window and do something there (usually moving another window will initiate it), and then when I re-focus on the nvim window, airline has re-appeared. I've tried :AirlineToggle but that doesn't help. I can get it to go away again by using Goyo 80x100% again, but I don't want to have to re-type that command every time I tab back in to type.
expected behavior
When I'm in the Goyo environment, the airline should go away completely and stay away until I leave the Goyo environment.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

So what exactly does goyo do to disable airline?
As far as I can tell, on launch, it runs AirlineToggle. Is this something that should be better taken up with them?

until I move focus to another window and do something there (usually moving another window will initiate it)

Are you talking about windows within the current vim instance, or are you talking about windows of other applications?
So when Goyo is active, what does :au FocusLost show?

Are you talking about windows within the current vim instance, or are you talking about windows of other applications?

Other Applications

So when Goyo is active, what does :au FocusLost show?

No commands or plugins are listed. It shows
--- Autocommands ---

with nothing listed under it. I get the same thing initially on :au FocusGained.
Once Airline comes back unexpectedly, FocusLost stays the same, but now FocusGained has
--- Autocommands ---
airline  FocusGained
    *         unlet! w:airline_lastmode | :call <sid>airline_refresh()

Is there an easy way to reproduce?

Am 01.10.2019 um 19:47 schrieb dorgnarg<EMAIL_ADDRESS>
Are you talking about windows within the current vim instance, or are you talking about windows of other applications?
Other Applications
So when Goyo is active, what does :au FocusLost show?
No commands or plugins are listed. It shows
--- Autocommands ---
with nothing listed under it. I get the same thing initially on :au FocusGained.
Once Airline comes back unexpectedly, FocusLost stays the same, but now FocusGained has
--- Autocommands ---
airline  FocusGained
*         unlet! w:airline_lastmode | :call airline_refresh()
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Is there an easy way to reproduce?

For me, entering the Goyo environment (:Goyo), shifting focus and interacting with another window, then shifting focus back and typing reproduces it every time. After some more testing, it takes me using the keyboard in vim after re-focusing on it to make it happen, not just tabbing/clicking back into the terminal window.

is this gvim or terminal vim? If terminal vim, what kind of terminal are you using?

I just tried with the latest airline and goyo version and cannot seem to reproduce the issue in gvim. Please give specific steps to reproduce it. For me goyo keeps active and the airline statusline won't appear unexpectedly.

it looks like you have a plugin in use, that uses a CursorHold or CursorMoved or similar autocommand that will trigger an :AirlineToggle call. I am only guessing here. Please check your plugins in use and your configuration. Because I cannot reproduce and therefore not fix it.

I'm doing this in the terminal (using Konsole) with neovim. I'm positive it's not an issue with another plugin because it still happens, even when I've disabled every plugin except for Goyo and Airline and use a completely empty vimrc (or I guess init.vim for neovim)
Here's what I can do to reproduce the issue every time:

Open an existing file (it doesn't seem to happen with empty files, at least)
Type :Goyo in Normal mode
Interact with another window (moving windows around is the easiest way to do it, but typing or clicking around does the trick just as well)
Re-focus on the terminal window containing the file, press any button (I usually use j or k to move, but any command I've used in normal mode does the trick). If I'm in insert mode, sometimes I don't even have to press a button.
Airline shows back up without me asking it to.

I found a fix from here; using the commands they suggested seems to stop the problem.

As I said, I cannot replicate. Also I wonder how that link is helping. You specifically said there is no FocusGained autocommand when goyo is active.

Am 03.10.2019 um 19:55 schrieb dorgnarg<EMAIL_ADDRESS>
I found a fix from here; using the commands they suggested seems to stop the problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

if you can reliably reproduce, please share or open a new issue. Closing.

Just to note that I found this issue whilst trying to track down the same problem. It's not quite as reliably reproduced for me as simply interacting with another window and coming back, but I'm definitely experiencing the behaviour of airline (often) appearing in Goyo windows after switching to a different workspace and back again.
This is with Goyo and arline, under neovim. I'm running it in the kitty terminal, under the i3 window manager.
I can also confirm that the fix mentioned by @dorgnarg seems to have resolved the problem for me. Reproducing it here, in case other people find this issue:
autocmd! User GoyoEnter nested set eventignore=FocusGained
autocmd! User GoyoLeave nested set eventignore=

(in $HOME/.config/nvim/init.vim).

Sorry to bump an old thread but another solution for the next one that comes searching:
I had airline popping up when returning to normal mode after making changes even with the above solution applied, here's my working solution:
augroup golight
	autocmd!
	autocmd User GoyoEnter let g:airline_disabled=1
	autocmd User GoyoLeave unlet! g:airline_disabled
augroup END

g:airline_disabled turns it off globally for the vim instance rather than the temporary AirlineToggle
The augroup is not strictly required but it's good practice as vimscript goes ;)


add fixture 'martin/mac-axiom-hybrid'

add fixture 'martin/mac-axiom-hybrid'
update register.json

Thank you @https://github.com/novasfronteiras!

Export files validity
(Output of test script tests/github/exports-valid.js.)
Test the exported files of selected fixtures against the plugins' export tests.
Fixture martin/mac-axiom-hybrid changed in this PR

d-light

attributes-correctness

:x: martin/mac-axiom-hybrid-std.xml
Show errors

Duplicate parameter name: FOCUS/PAN
Duplicate parameter name: FOCUS/TILT

ecue
ofl
qlcplus

xsd-schema-conformity

:white_check_mark: Martin-MAC-Axiom-Hybrid.qxf

Export files validity
(Output of test script tests/github/exports-valid.js.)
Test the exported files of selected fixtures against the plugins' export tests.
Fixture martin/mac-axiom-hybrid changed in this PR

d-light

attributes-correctness

:white_check_mark: martin/mac-axiom-hybrid-std.xml

ecue
ofl
qlcplus

xsd-schema-conformity

:white_check_mark: Martin-MAC-Axiom-Hybrid.qxf

LGTM now


Hide message and exception type when stack trace is supressed

@jtamayo

Also, how do we feel about special-casing on the exception type when setting the status code? Lots of people use throw BadRequestException to indicate that a 400 should be returned.

You want to suppress always for 400s but not for others?

I'm proposing that any exception which is a subclass of WebApplicationException uses the error code associated with the exception (and not the one passed in the constructor). This allows us to use the pattern of throwing WAEs to control the error codes our APIs return.
If we do that, then it feels natural to always serialize exceptions as subclasses of WAE if possible and fall back to ISE when the exception is something else. ISE seems okay to me, because any exception we throw that isn't a WAE is unexpected, and a problem with the server.

Is it reasonable to assume that ISE exists on the client?

It's a member of javax.ws.rs so I would say so.

@jtamayo brang up a good point -- ISE uses static methods off RuntimeDelegate to create response objects. This requires either jersey or some other JAX-RS implementation on your classpath -- some clients might have trouble deserializing an ISE.

So let's stick with RuntimeException, I think it's fine.


Improve performance of multivector arithmetic by avoiding copies

Multiplications become roughly 20% faster, and addition 33% faster.
There's now a new copy argument to the MultiVector constructor.
Some timings:
Edit: These timings are out of date, and include the effects of #283 which used to be part of this PR. We should retime before merging
After:
In [1]: from clifford import Cl
In [2]: layout, _ = Cl(5)
In [3]: a = layout.randomMV(); b = layout.randomMV()

In [4]: %timeit a * b
The slowest run took 4.76 times longer than the fastest. This could mean that an intermediate result is being cached.
20.4 µs ± 11.3 µs per loop (mean ± std. dev. of 7 runs, 1 loop each)

In [5]: %timeit a * b
8.64 µs ± 341 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

In [6]: %timeit a * b
9.23 µs ± 606 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

In [7]: %timeit a + b
3.9 µs ± 250 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

Before:
In [1]: from clifford import Cl
In [2]: layout, _ = Cl(5)
In [3]: a = layout.randomMV(); b = layout.randomMV()

In [4]: %timeit a * b
The slowest run took 4.37 times longer than the fastest. This could mean that an intermediate result is being cached.
18.6 µs ± 14.2 µs per loop (mean ± std. dev. of 7 runs, 1 loop each)

In [5]: %timeit a * b
11.7 µs ± 759 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

In [6]: %timeit a * b
11.3 µs ± 660 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

In [7]: %timeit a + b
6.11 µs ± 871 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

I'm wondering if actually we should just change the default to copy=False. I haven't yet found an internal call that would break if we did this.

Let's not merge this till we:

Decide on #282
Re-profile it in isolation


Maintenance release of 1.1.x with GHC<7.4, bytestring>=0.10 support?

Related: https://github.com/bos/text/issues/108
We are running builds against multiple ghcs and versions for curation. The fact that text-1.1.*  doesn't build with bytestring >= 0.10 is causing us problems, e.g. http://matrix.hackage.haskell.org/package/process-listlike#GHC-7.2/process-listlike-1.0
Would it be possible to get a <IP_ADDRESS> release that fixes this?
I prepared and tested a commit for this (can't send PR's against tags): https://github.com/bergmark/text/commit/fba4081026ae7d70e26c10e28ce44f2becce4d88
Thanks,
Adam

I tried to upload a new 1.1 for you, but I'm blocked by a regression in Hackage.

Thanks for trying! A lot of packages are affected by this so hopefully there will be a fix soon...

<IP_ADDRESS> is out now.

Thank you Bryan, green bars everywhere!


Passthrough

WIP, this makes things more like the node version, wanted to know if you thought this was a good idea

non overridden methods of a module behave like the original

[x] fixes the first order behavior
[ ] does a deep merge

Can you help me understand why we might want this? Is there a specific use-case you can share?
My team at work actually wrote an alternative to the node proxyquire that didn't do this because having call through proxies caused a lot of problems for us. That said, I wouldn't be opposed to this provided that it wasn't the default behavior and I better understood the benefit..


Update resource-manager-deployment-model.md

Fixed typos in text and code.

Hi @alexandair, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@alexandair thanks for fixing this topic. The changes look good.

@ggailey777 - this PR in the public repo can be merged.


Add support for query parameters and claims

There was no native support to retrieve info from query parameters.

Awesome, as per usual - I've asked @obsd to review :)


Feature/fe 1380 photo progress update UI component

Why?
Implemented a UI component to display the photo upload verification status
How?

Added the initialization of the Upload Service in App
Created a GlobalUploadObserverService which listens to upload events and emits the events in a MutableSharedFlow<UploadPhotosState>
Created util class ImageFileHelper which has many functions related to images or files to fit our needs and not having those functions in Activities/Fragments.
Created composable PhotoUploadState which consists of the progress state, the progress bar and the station name in order to reuse it whenever we need it.
In DevicesFragment created the function initAndObserveUploadState which according to the state populates the top card showing the upload progress
Test code for uploading in PhotoGalleryActivity

Testing
Follow the flow to upload photos via a local server and ensure everything looks OK after uploading them regarding this new UI component in the Devices list.

Fixed! :)


The sasToken in copy_source_url is needed when specify requires_sync=True in copy_blob method.

I used the copy_blob method to copy blobs in the same storage account, and both of the containers are private.
If I did not specify the sasToken in the copy_source_url, then an error occured, like below:
HTTP status code=404. ErrorCode: CannotVerifyCopySource. The specified resource does not exist.
The completed code is as below:
from azure.storage.blob import BlockBlobService

accountName="xxx"
accountKey="xxx"

blobs = BlockBlobService(account_name=accountName,account_key=accountKey)

#copy_source_url
copySource="https://xxxx.blob.core.windows.net/f22/gen2.JPG"

blobs.copy_blob("dest_container","dest_blob_name",copySource,requires_sync=True)

Some other observations:

if the source container is public, it works without specify sasToen
if the source container is private, but remove the requires_sync=True, it can work well.

Could you please let me know if it's by design or it's a bug? I cannot find any docs about it.

I found this issue a few days ago. Previously the function worked fine with require_sync=True, but stopped working out of the blue. I wonder if Azure have made a change on the remote end that is tripping it up somewhere.

Hi @imeya thanks for reaching out!
It's expected behavior but we should definitely improve the doc. I'll make sure the behavior is more clearly explained.

Hi @theocranmore, nothing was changed, maybe your sources were public before?

FYI the REST API doc is here.

@zezha-msft , thanks for looking into this issue. And why it needs the sasToken in the source_url, since both the destionation / source container are in the same storage account? can you help explain why?

Hi @imeya, it was the service's decision to make it that way, my guess is that unlike its asynchronous counterpart, synchronous copy also supports external sources (that are outside of Azure), it's simpler to always require authentication on the source so that the logics are simpler in general and easier to communicate.


NativeFile drag works intermittently on Firefox 58

Native file drag seems to not work as expected when the drag is cancelled. Next time we try to drag a native file onto a target, target fails to identify the drag item.

Investigated a bit to see some Firefox specific quirks added in the codebase (probably bcoz of the previous behaviour of the browser).
Looks like Firefox has improvised and we no more need this quirk; which solves this problem.

This is still an issue for me, and it only starts working again if I restart Firefox.


PEP 8 compliant format strings

Thanks for this.
If you'd be so kind, could you make this to the pattern 3 fork rather than here. That way we can merge #107 can be merged cleanly (hopefully soon).

Made the PR there!


ScytaleC ZeroMQ support

Hi, this is microp11, the author  of ScytaleC decoder for STD-C. I just learned about your project and wanted to know if the USB demodulated signal comes out as audio or I/Q?
The std-c channels are 5kHz separated, alongside the JAERO band, 4kHz in width, 1200 baud unfiltered BPSK.
Can such a signal be extracted using the receiver, USB demodulated at 48k? Is the output Audio or I/Q?
I think it would be worth adding 0MQ messaging to the ScytaleC because it can than run in parallel as well.
I was working on something similar using GNU Radio, to get the demodulated signal out. And I have a feeling that your project already does that and a lot more. Excellent work!
https://bitbucket.org/scytalec/scytalec/
Thanks.

Hi!
For jaero the output is USB since it expects that but it does have the ability to send I/Q data although it needs a little tinkering to make it work properly but that should be straight forward.
Otherwise yes I think that should work fine. You could define 48Khz USB VFO's in the receiver and then consume this data in your application with a zmq subscriber. You could use the low pass filter in the receiver with maybe a 10Khz filter to remove adjacent channels if needed.
Not sure what bandwidth you need to cover all channels but it may be enough with a 288Khz sample rate on the RTL? That way you keep CPU nice and low. Jaero decodes 1200 bps MSK at 12Khz sample rate just fine so you may be able to drop the rate for each VFO down to that but I guess it depends on your application.  Or are you saying all the channels would fit into a single 48Khz VFO?
Thanks :-)
/Jeroen

Hi @jeroenbeijer, thank you for the answer. I wills set up my system with your app and will investigate. The reason I did not answer is that I was (and still) not able yet to find any time, but would like to acknowledge your answer and let you know it is much appreciated. Just need to catch up. Thanks, Paul

Hi Paul, I think time is something we could all use a little more of :-)
I setup an ini file for the receiver with the STD-C channels I found on 25E in the center. I found a bunch of channels around 1539.465 that I could decode with your excellent decoder. I will post the ini file below. I used 1536000 as the sample rate, seems the RTL gives some weird results at 288K so will have to look at that later.
Just for fun I connected jaero to one of the VFO's and low and behold it locks onto the PSK signal!
So in summary I think if you add a ZMQ receiver in your program for USB audio at either 48Khz and connect to the SDR host and port number defined in the ini file with the right topic name you should be good to go. Keep in mind you will receive alternating packets of data and a packet (4 byte) indicating the samplerate of the audio.
/Jeroen

sample_rate=1536000
center_frequency=1539465000
zmq_address=tcp://*:6005
#valid tuner gains r82xx_gains[] = { 0, 9, 14, 27, 37, 77, 87, 125, 144, 157, 166, 197, 207, 229, 254, 280, 297, 328, 338, 364, 372, 386, 402, 421, 434, 439, 445, 480, 496 };
tuner_gain=496
correct_dc_bias=1
[main_vfos]
size=1
1\frequency=1539550000
1\out_rate=288000
[vfos]
size=7
1\frequency=1539415000
1\gain=10
1\out_rate=48000
1\filter_bandwidth=5000
1\topic=VFO01
2\frequency=1539445000
2\gain=10
2\out_rate=48000
2\filter_bandwidth=5000
2\topic=VFO02
3\frequency=1539455000
3\gain=10
3\out_rate=48000
3\filter_bandwidth=5000
3\topic=VFO03
4\frequency=1539465000
4\gain=10
4\out_rate=48000
4\filter_bandwidth=5000
4\topic=VFO04
5\frequency=1539475000
5\gain=10
5\out_rate=48000
5\filter_bandwidth=5000
5\topic=VFO05
6\frequency=1539485000
6\gain=10
6\out_rate=48000
6\filter_bandwidth=5000
6\topic=VFO06
7\frequency=1539495000
7\gain=10
7\out_rate=48000
7\filter_bandwidth=5000
7\topic=VFO07

I have started today to look into adding support for ZMQ into scytalec.
First step, finding the NCS on 54W done:
#list of frequencies at https://forums.radioreference.com/threads/scytale-and-sdr-newbie-inmarsat-questions.425814/, by dlwtrunked

sample_rate=1536000
#center_frequency=1539465000
center_frequency=1541450000

zmq_address=tcp://*:6005

#valid tuner gains r82xx_gains[] = { 0, 9, 14, 27, 37, 77, 87, 125, 144, 157, 166, 197, 207, 229, 254, 280, 297, 328, 338, 364, 372, 386, 402, 421, 434, 439, 445, 480, 496 };
tuner_gain=496
correct_dc_bias=1

[main_vfos]
size=1
1\frequency=1541450000
1\out_rate=288000

[vfos]
size=1

#1541.4500,54W,Inmarsat-C,NCS,144,,
1\frequency=1541440000
1\gain=10
1\out_rate=48000
1\filter_bandwidth=4000
1\topic=VFO01

2\frequency=1539445000
2\gain=10
2\out_rate=48000
2\filter_bandwidth=5000
2\topic=VFO02

Now to read the ZMQ documentation.

My test client now receives:
56464F3031 = VFO01 in ASCII
80BB0000 = 48000
D4006901E801540... up to 48000 bytes and it repeats
56464F3031
80BB0000
E302E102A90...

So now to add it to the decoder...

Hi @jeroenbeijer , I am saving the data-only (no topic or rate) into a binary file, and trying to open it with audacity in raw mode hoping to hear the known signal. What format is the data? I have tried different variations but no success? Thanks

Stuck, need some help on the output stream format.

How to intepret the data? I brought it in scytalec, however...

Hi Paul, sorry for the late response, been very busy and not had much time for this project. Basically on the SDR side each USB sample is converted from float to 16 bit short. So each bucket of data you receive is basically an array of 16 bits shorts. When jaero receives this from zmq the byte or is maintained and so basically the right most bit in each short is the least significant. Not sure how you pick this up and if this may affect the formatting.

Hi, thank you:
Does this make sense?

Each sample contains short I and short Q
-----------------------------------------

Bucket 0, byte 0 is first received, byte length-1 is last received in the bucket array

Byte 0 | Byte 1 | Byte 2 | Byte 3 |      ...      | Byte length-4 | Byte lenght-3 | Byte length-2 | Byte length-1 |
-------------------------------------------------------------------------------------------------------------------
   short   I    |   short  Q      |      ...      |            short   I          |         short  Q              |
-------------------------------------------------------------------------------------------------------------------
              Sample 0            |      ...      |                        Sample length/4                        |
-------------------------------------------------------------------------------------------------------------------

Bucket 1, byte 0 is the first byte in the next bucket following byte length-1 from the previous bucket

Byte 0 | Byte 1 | Byte 2 | Byte 3 |      ...      | Byte length-4 | Byte lenght-3 | Byte length-2 | Byte length-1 |
-------------------------------------------------------------------------------------------------------------------
   short I      |    short Q      |      ...      |         short I               |           short Q             |
-------------------------------------------------------------------------------------------------------------------
              Sample 0            |      ...      |                        Sample length/4                        |
-------------------------------------------------------------------------------------------------------------------

The short is LSB:

0xABCD = -21555

Hi, the audio from the receiver out is not I/Q but USB, upper side band only.


Add docs for spinning up elfpy bots to the infra repo

we have better general instructions in the infra repo now after today's merge, but nothing bot-specific.
leaving this open to add better bot-specific instructions in the future.

Initial docs are in the infra repo as well as updated INSTALL.md from #521


problem with fortran.includePaths

Hello,
Thanks for providing this extension.
I have a problem under linux with fortran.includePaths, if I specify only one value in the array, it works well, but with 2 values it doesn't.
By spying the generated gfortran command line it appears that the generated include paths are as follows :
-I /path1 /path2
instead of
-I/path1 -I/path2
By modifying helper.js line 78 :
return '-I ' + paths.join(' ');

into
return '-I' + paths.join(' -I');

then it works well.

Hello there, thank you for pointing that out.
Can you create a Pull Request for this since you've already fixed it?
Thank you! :+1:

Done.

This first solution I gave did not work well, it only worked under my testing setup.
I updated the branch for which I created the pull request with a solution using a string array that actually works at least under linux.


Remove generics in key_builder

The Key_builder supports generics to allow schema.Field or schema.QueryableField. This should be removed and key_builder should only accept schema.QueryableField.
Steps to get this working:

Remove generics in key_builder
Fix tests to only accept schema.QueryableField this could be done by converting the current schema.Field options into a queryableField before running the test
Add a method on schema.DefaultCollection to get the primarykeys as a list of queryablefields

I'll pick this up

Related Discord discussion thread - https://discord.com/channels/1033842669983633488/1033843208192524348/1095960587806183494


Fix(VIM-2227): Wrong behavior when deleting / changing surround with invalid character

This looks correct. Thank you for the contribution!


Issue 683: Create ArtifactEntry.created property

Hi!
Thank you for your contribution!
Would you mind signing the ICLA, as described in the Contributing page?
Kind regards,
Martin

@mkuligowski : Could you please sign the ICLA and mail it to me? I can only then merge this pull. Thanks! :)


Validation: image-alt-text-duplicated

This PR addresses the issue: image-alt-text-duplicated errors (duplicate alt text descriptions within an article)
This PR fixes 20 issues across 1 file and is part of ongoing Validation cleanup efforts.
No other content has been edited or added.

Global effort to fix validation errors
@Rick-Anderson
The Content & Learning team is fixing build validation errors on docs.microsoft.com. This effort will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. I’d very much appreciate your timely review and feedback on these changes I’ve suggested. Thanks!

Global effort to fix validation errors
@Rick-Anderson
The Content & Learning team is fixing build validation errors on docs.microsoft.com. This effort will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. I’d very much appreciate your timely review and feedback on these changes I’ve suggested. Thanks!


Crypto algorithm error - No conversion rate for the following cash

Hi all,
I am quite new to lean.io and trying to get started with a minimal setup to trade crypto. This simple code keep throwing the below error. Even the BasicTemplateCryptoAlgorithm does throw the same error.
I did validate and the data seems to exists if looking here : https://www.quantconnect.com/data/tree/crypto/bitfinex/minute/btcusdt
Is that error normal or some error got introduced in the AddCrypto at some point?
Thank you
Expected Behavior

Get the market data for BTCUSDT in algo using AddCrypto("BTCUSDT", Resolution.Minute);
Actual Behavior

ERROR:: Failed to assign conversion rates for the following cash: USDT,BTC. Attempting to request daily resolution history to resolve conversion rate
Potential Solution

Reproducing the Problem

public override void Initialize()
        {
            SetStartDate(2020, 10, 07);  //Set Start Date
            SetEndDate(2020, 10, 08);    //Set End Date
            SetCash("USDT", 1000);           //Set Strategy Cash

            SetBrokerageModel(Brokerages.BrokerageName.Bitfinex, AccountType.Cash);
            AddCrypto("BTCUSDT", Resolution.Minute);
        }

        /// <summary>
        /// OnData event is the primary entry point for your algorithm. Each new data point will be pumped in here.
        /// </summary>
        /// <param name="data">Slice object keyed by symbol containing the stock data</param>
        public override void OnData(Slice data)
        {
            var rsi = RSI("BTCUSDT", 14, Indicators.MovingAverageType.Simple);

            if (rsi <= 35)
            {
                MarketOrder("BTCUSDT", 0.0001);
            }
            else
            {
                if (Portfolio.Invested == true && Portfolio.CashBook["BTCUSDT"].Amount > 0)
                {
                    MarketOrder("BTCUSDT", -0.0001);
                }
            }
        }

System Information

Lean master branch running on windows 10 and VS 2022 preview 1
Checklist

[x ] I have completely filled out this template
[x ] I have confirmed that this issue exists on the current master branch
[x ] I have confirmed that this is not a duplicate issue by searching issues

[x ] I have provided detailed steps to reproduce the issue

Hey @dominiclapointe! Is the data available locally for lean to use? By default Lean will ask for the last 10 minutes bars prior to the start date of the algorithm to get the conversion rate, if it doesn't work it will use daily resolution. My guess is that there is no data for (2020, 10, 07) - 10min locally

Hum would make sense I guess. My expectation was that  lean would fetch the data based on the given date.
Is there a way to get the data through an API or I have to gather all the data manually and put it in a specific folder?
Thank you

Is there a way to get the data through an API

Yeah! Take a look at https://www.youtube.com/watch?v=Iedf4x4Bnj4 & https://www.youtube.com/watch?v=faazkn8BIv0 more info at https://www.lean.io/docs/lean-cli
Closing since this isn't an issue of lean

Not to complain, lean seems so far quite the best quant product out there but, the free tier of quantconnect (commercial product) allow for gathering this data for free while the lean.io open source plateform charge in order to get this data?
Do you have any documentation on how to plug our data provider and make it works seamlessly with lean.io? Like, is there a way to call binance API (only crypto in my case), map it to whatever entity lean.io uses behind the hood and be able to use the QCAlgorythm?
Thank you


tcl symlink in /bin => File is a symlink to a nonexistent target

lrwxrwxrwx  1 root root        8 Feb 12 02:57  tclsh -> tclsh?.?
File is a symlink to a nonexistent target
Why is this, @dylanaraps ?
Thank you.

The glob didn't match.


Update pyicloud version

Description:
Updates the pyicloud version to the latest version. This is needed for the new icloud platform.
In this version, the upgrade issue is fixed when the cookie folder was corrupted so everyone can safely upgrade now.
Related issue (if applicable): #
Example entry for configuration.yaml (if applicable):

Checklist:
If code communicates with devices:

[X] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Last time this update caused users setup to break which lead to negative voices on social media and a hotfix release to revert the change. I do not want this to happen again.
So I'll be merging this right after the next release. That way we have 2.5 weeks to test and make sure this doesn't break users setup.

Absolutely! 😊

Op 18 apr. 2016 om 17:50 heeft Paulus Schoutsen<EMAIL_ADDRESS>het volgende geschreven:
Last time this update caused users setup to break which lead to negative voices on social media and a hotfix release to revert the change. I do not want this to happen again.
So I'll be merging this right after the next release. That way we have 2.5 weeks to test and make sure this doesn't break users setup.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Also, can you point me at the code in iCloud that will prevent the issues
that plagued us last time?
On Mon, Apr 18, 2016 at 11:52 AM, Bart274<EMAIL_ADDRESS>wrote:

Absolutely! 😊

Op 18 apr. 2016 om 17:50 heeft Paulus Schoutsen <
<EMAIL_ADDRESS>het volgende geschreven:
Last time this update caused users setup to break which lead to negative
voices on social media and a hotfix release to revert the change. I do not
want this to happen again.
So I'll be merging this right after the next release. That way we have
2.5 weeks to test and make sure this doesn't break users setup.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/home-assistant/home-assistant/pull/1849#issuecomment-211525227

--
PaulusSchoutsen.nl
It's nice to be important but it's more important to be nice.

Sure, it was fixed here: https://github.com/picklepete/pyicloud/commit/358d84e334c5afdcf4264bb372b9b88af23f7056

Op 18 apr. 2016 om 22:18 heeft Paulus Schoutsen<EMAIL_ADDRESS>het volgende geschreven:
Also, can you point me at the code in iCloud that will prevent the issues
that plagued us last time?
On Mon, Apr 18, 2016 at 11:52 AM, Bart274<EMAIL_ADDRESS>wrote:

Absolutely! 😊

Op 18 apr. 2016 om 17:50 heeft Paulus Schoutsen <
<EMAIL_ADDRESS>het volgende geschreven:
Last time this update caused users setup to break which lead to negative
voices on social media and a hotfix release to revert the change. I do not
want this to happen again.
So I'll be merging this right after the next release. That way we have
2.5 weeks to test and make sure this doesn't break users setup.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/home-assistant/home-assistant/pull/1849#issuecomment-211525227

--
PaulusSchoutsen.nl
It's nice to be important but it's more important to be nice.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

This also introduces support for 2FA (in 0.8.0). Security FTW

2FA is supported by pyicloud 0.8.0 but can't be implemented to be used in HA...

Op 24 apr. 2016 om 04:48 heeft Jeff Schroeder<EMAIL_ADDRESS>het volgende geschreven:
This also introduces support for 2FA (in 0.8.0). Security FTW
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


Empty object is not assignable to all-optional mapped type when used with generic inside class

TypeScript Version:  2.1.1 (http://www.typescriptlang.org/play/index.html)
Code
class Form<T> {
    private values: {[P in keyof T]?: T[P]} = {}
}

Expected behavior:
No compile error
Actual behavior:
Type '{}' is not assignable to '{[P in keyof T]?: T[P]}'

I agree, it seems meaningful to support this.


Enable /black in comments

Same as MONAI repo, it will be more convenient for users to fix code format issues

Issue: https://github.com/Project-MONAI/monai-code-formatter/runs/6911719251?check_suite_focus=true#step:7:336
Since runtests.sh in this repo does not have clangformat check, we cannot use project-monai/monai-code-formatter directly in chatops.yml.

addressed by updating the code formatter logic. https://github.com/Project-MONAI/monai-code-formatter/actions/runs/2926956836


Duplicating nested blocks doesn't create new field IDs in children

Link to reproduction
No response
Describe the Bug
Creating nested blocks inside a collections and duplicating the parent in the admin panel will cause the fields below to have duplicated IDs.
MongoDB entry after the duplication:
"layout": [
    {
      "child": [
        {
          "columns": [
            {
              "size": "oneThird",
              "richText": [
                {
                  "children": [
                    {
                      "text": "adf"
                    }
                  ]
                }
              ],
              "link": {
                "type": "reference",
                "appearance": "default"
              },
              "id": "6614304ae9c51b52291640a7"
            }
          ],
          "id": "66143047e9c51b52291640a6",
          "blockType": "content"
        }
      ],
      "id": "66142fc045f115b51b8bd467",
      "blockType": "parent"
    },
    {
      "child": [
        {
          "columns": [
            {
              "size": "oneThird",
              "richText": [
                {
                  "children": [
                    {
                      "text": "adf"
                    }
                  ]
                }
              ],
              "link": {
                "type": "reference",
                "appearance": "default"
              },
              "id": "6614304ae9c51b52291640a7"
            }
          ],
          "id": "66143047e9c51b52291640a6",
          "blockType": "content"
        }
      ],
      "id": "6614305ce9c51b52291640a8",
      "blockType": "parent"
    }
  ],

Here both "content" blocks (and their children) have the same IDs.
To Reproduce
Config Snipped (from "pages" collection in website template):
{
          label: 'Content',
          fields: [
            {
              name: 'layout',
              type: 'blocks',
              required: true,
              blocks: [
                CallToAction,
                Content,
                MediaBlock,
                Archive,
                {
                  slug: 'parent',
                  fields: [
                    {
                      type: 'blocks',
                      name: 'child',
                      blocks: [Content],
                    },
                  ],
                },
              ],
            },
          ],
        }

Payload Version
2.12.1
Adapters and Plugins
db-mongodb

What about adding an arbitrary layer of constraints at the base... 1st code contact from right to left as a block for an additional constraint with a conditional exception for a pass through for more control over everything --> and an additional constraint with a conditional ifelse at all no x{?


add the ZAPI request id on RequestError message

Alternative to https://github.com/scrapy-plugins/scrapy-zyte-api/pull/142

Codecov Report

Merging #52 (cd8454e) into main (91b141e) will increase coverage by 15.02%.
The diff coverage is 100.00%.

:exclamation: Current head cd8454e differs from pull request most recent head 0e684a3. Consider uploading reports for the commit 0e684a3 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main      #52       +/-   ##
===========================================
+ Coverage   43.28%   58.31%   +15.02%
===========================================
  Files          10       10
  Lines         365      367        +2
  Branches       53       53
===========================================
+ Hits          158      214       +56
+ Misses        205      145       -60
- Partials        2        8        +6

Files
Coverage Δ

zyte_api/aio/client.py
71.42% <100.00%> (+36.76%)
:arrow_up:

... and 5 files with indirect coverage changes

Tox is failling for 3.7. I suppose removing it would be apt. https://github.com/zytedata/python-zyte-api/pull/53


stable/sonarqube templates/deployment.yaml initContainers.image value override

initContainers.image: {{ default "busybox:1.31" .Values.plugins.initSysctlContainerImage }}

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/mychartname])

A couple of changes needed before this can be merged:

Commits need signed: https://github.com/helm/charts/pull/19950/checks?check_run_id=380011600
The version in chart.yaml needs incremented
The new override needs to be included in values.yaml and the readme so people can find it easy

/assign

This chart has been deprecated and moved: https://github.com/helm/charts/pull/21007


DSND-466:Initialise Spring Boot Application for Charges API

Hi @adeshpandech
Also I spokw to Dom regarding few files missing, can you please add missing files like start.sh, version
Please check charges-delta-consumer repo for reference. Thanks

Hi @adeshpandech
Also I spoke to Dom regarding few files missing, can you please add missing files like start.sh, version Please check charges-delta-consumer repo for reference. Thanks


Implement OnlyKpse for LuaTeX

Status
READY
Description
Add an option KpseOnly to restrict font searches to fonts in the TeX directories as discussed in #413.
In XeTeX the option works too but is ignored.
Todos

[ ] Tests added to cover new/fixed functionality
[x] Documentation if necessary
[x] Code follows expl3 style guidelines

Minimal example demonstrating the new/fixed functionality
\documentclass{article}
\usepackage{unicode-math}
\setmainfont{texgyrepagella}[
  KpseOnly,
  Extension = .otf ,
  UprightFont = *-regular.otf ,
  ItalicFont  = *-italic.otf  ,
]
\begin{document}
hello \emph{hello}
\end{document}

This probably should have been the default, since it is both the XeTeX and the original luaotfload behavior that IMHO should have never been changed, since file name support was added specifically to locate fonts under texmf tree.


Disable keyboard shortcuts

is there a way to disable keyboard shortcuts for inputs, for example the space bar will toggle the last selected check box / folder etc.
This isn't an 'issue' per-se but it is leading to some undesired behaviour which it would be good to be able to disable.
Thanks

Ideally, keyboard shortcuts should be kept as it keeps the component accessible to keyboard users. If absolutely necessary maybe an override option could be implemented, but this should really be given more thought - is it important enough to warrant making the component inaccessible to keyboard-primary users?

I do not recommend to disable the default behavior in consistency reason. It may reduce usability. But if you still want to do that, maybe you can do that by listening keyboard events of the target element and preventing the default behavior.


Use no-op gatekeeper in proxy-noauth pipeline

I tried this out and did like it.  I had some confusion about how it interacted with the null-namespace and a pipeline with versioned_writes.  I was also trying to imagine if there was room in vsaio for something like this so we didn't need it to be an externally managed/versioned/tested/intergrated dependency.

how it interacted with the null-namespace and a pipeline with versioned_writes

It just gets out of your way :slightly_smiling_face: Send X-Backend-Allow-Reserved-Names: true to your heart's content!

if there was room in vsaio for something like this

Sure; that works, too. I just didn't have much prior art to go on there.


Path parameter with List

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
@app.get(
    V4L2_ROUTE + "controls/{ctrl_list}",
    response_model=List[ControlValue],
    tags=[Tags.controls],
)
def get_controls(
    ctrl_list: List[str],
    params: CommonParams = Depends(),
) -> JSONResponse:
    """Get v4l2 controls"""
    return Camera.get_controls(ctrl_list, params.dev)

Description
When trying to declare a route with a Path parameter which is a List I get the following error: AssertionError: Path params must be of one of the supported types
But from what I can see it should be possible to have Lists in the Path: https://stackoverflow.com/questions/2602043/rest-api-best-practice-how-to-accept-list-of-parameter-values-as-input
Fx: http://our.api.com/Product/101404,7267261
Operating System
Linux
Operating System Details
No response
FastAPI Version
0.85.0
Python Version
Python 3.10.5
Additional Context
No response

A Path param is always a int or a str. However, you could simply do the conversion yourself. The below example shows how to deal with a list of values like 'int,int,int' etc. Using pydantic, I will also perform basic validation, yay!
from fastapi import Depends, FastAPI, HTTPException, Path
from pydantic import BaseModel, ValidationError

app = FastAPI()

class ListOfIds(BaseModel):
    ids: list[int]

def list_path_param(list_of_ids: str = Path()):
    try:
        ids = ListOfIds(ids=list_of_ids.split(","))
    except ValidationError:
        raise HTTPException(400, "IDs must be valid integers.")
    return ids

@app.get("/controls/{list_of_ids}")
async def get_list_of_ids(list_obj: ListOfIds = Depends(list_path_param)):
    return {"count": len(list_obj.ids), "ids": list_obj.ids}

if __name__ == "__main__":
    import uvicorn

    uvicorn.run(app, host="<IP_ADDRESS>", port=8000)

This will take the str and will split it (resulting in a list), and construct a Pydantic model with its parts (thus performing validation). The above will run as is.

cool, thanks
It could be nice to also add such an example to the docs/tutorials :)

Thanks for the help @JarroVGIT ! 🙇
And thanks for coming back to close the issue @mariannasb . ☕
I would suggest not using lists in path parameters. A path is normally expected to point to a unique resource (a unique thing), and if the list is in the wrong order it would probably still point to the same thing.
It's also not common (I've never seen that before), so it might be a bit confusing for other developers using your API.
The alternative I would suggest is query parameters. You can make them required, require a minimum number of items, etc.

Yes, I ended up using query parameters in the end.
Partly because that was my work around before I got this solution.
But mostly because it ended up making more sense with the rest of the API since I also needed to do a POST with a list (which ended up as a Dict[str, ControlValue])

Ah, get it, great!


running pm2 spikes cpu and memory

using with
pm2: 3.2.2
node: 8.12.0
npm : 6.4.1
@google-cloud/pubsub: 0.20.1
os: Ubuntu 16.04.3 LTS
subscription type: pull

file: subscription.js
const path = require('path');
const logger = require('debug')(`job:${path.basename(__dirname)}: `);
const PubSub = require('@google-cloud/pubsub');
const messageHandler = require('./handler');
const settings = require('../settings');

const keyFilePath = path.resolve(__dirname, './key-file.json');

// Creates a client
const pubsub = new PubSub({
  keyFilename: keyFilePath,
});

const { subscriptionName } = settings.google;

// References an existing subscription
const subscription = pubsub.subscription(subscriptionName);

logger('listening to any publication to any Businesses Notification');

subscription.on('message', messageHandler);

running this in pm2 initially
first

second

third

fourth

is there other debugging environment i should use to deepen the debugging?
thanks.

@JustinBeckwith, hold your horses. :D, in version v.0.19.x the cpu is behaving smoothly.
It appears the v0.20x. is not sending 'message' event to the publishers, but confirmed to work on 0.18 and 0.19. Or do i have to create another issue for this one?


[DOC] move doc to main website and apply simple pre-commit hooks

move most of the content of the README to the main doc website (see https://github.com/MOxUnit/MOxUnit/pull/105)
add citation.cff
add license
add codespell and pre-commit config and run them

@nno should we setup github CI to run the tests here and removed the travis config?


remove windows manual instructions

This is already covered here: https://docs.docker.com/engine/installation/windows/docker-ee/#use-a-script-to-install-docker-ee

@friism Please don't delete these instructions. These for the latest Docker CE bits (17.09). We are referencing this in our documentation that is going live tomorrow. If this page is gone, there will no instructions for our users to install our product. This is needed for Windows IoT Core where Docker for Windows GUI installer will not work...


listTut Display

I feel like adding Tutorial in between tutorial name and tutorial id does not work well though because T indicates tutorial already in the id.
Is it better to have it in such a format: 1. CS1010 (T1001) or something similar?

It would be better to keep the Tutorial name inside, for better readability for the user


cmd/go: cannot recover from go env -w GOTOOLCHAIN=*

If previously set an older version as GOTOOLCHAIN
~$ gotip env -w GOTOOLCHAIN=go1.20.2
~$ gotip version
go version go1.20.2 darwin/amd64
~$ gotip env -w GOTOOLCHAIN=
go: unknown go command variable GOTOOLCHAIN

or if entered a wrong version by mistake
~$ gotip env -w GOTOOLCHAIN=1.20.2
~$ gotip version
go: invalid GOTOOLCHAIN "1.20.2"
~$ gotip env -w GOTOOLCHAIN=local
go: invalid GOTOOLCHAIN "1.20.2"

Some ideas:

handle go env command before switch toolchain
or disallow versions older than go1.21 for GOTOOLCHAIN value (I hope not...)

And

validate the version string before accepting go env -w

cc @rsc @bcmills
EDIT: I found the following helps.
$ GOTOOLCHAIN=local gotip env -w GOTOOLCHAIN=local

I still cannot set to an empty value
$ GOTOOLCHAIN=local gotip env -w GOTOOLCHAIN=
warning: go env -w GOTOOLCHAIN=... does not override conflicting OS environment variable

Probably go env -w should apply any GOTOOLCHAIN changes to itself before exec'ing the GOTOOLCHAIN-based switch.

Probably go env -w should apply any GOTOOLCHAIN changes to itself before exec'ing the GOTOOLCHAIN-based switch.

Actually, I think that implies that you can't use go env -w to set a toolchain older than 1.21, since writing GOTOOLCHAIN into go.env guarantees that the file isn't compatible with a pre-1.21 toolchain. 🤔

@bcmills Won't the same sort of problem unfold any time a new variable gets added to go.env? For example, suppose Go 1.22 adds support for GOFOO.
$ go env -w GOFOO=bar
$ go env -w GOTOOLCHAIN=go1.21.0

Now everything will fail because 1.21 doesn't understand GOFOO, and I cannot fix it without manually editing the go.env file.
Even if go env -w prevented me from setting GOTOOLCHAIN in this case, it seems like this could lead to frustration going forward and ultimately undermine the utility of both GOTOOLCHAIN and go.env. Is there a reason the toolchain needs to fail on unrecognized entries instead of just ignoring them?

Is there a reason the toolchain needs to fail on unrecognized entries instead of just ignoring them?

go env -w certainly ought to do that to prevent typos, and I think the original reason for applying the same logic to the file was to detect erroneous hand-edits. But perhaps we should ignore unrecognized settings once they're already in the file.
But I don't see that that would help much for this particular case, because the same error will occur if you set GOTOOLCHAIN=1.18.10 and the 1.18 release is no longer receiving backports.

Re "I still cannot set to an empty value", the command does set it to an empty value. It just prints a warning that your environment is still going to override the value if you keep your environment that way.

Thinking out loud ...
There are a few cases here.
If you set GOTOOLCHAIN=garbage, then that will fail consistently, and you have to use GOTOOLCHAIN=local go env -w GOTOOLCHAIN=... to get back out.
If you set GOTOOLCHAIN=go1.19, that works fine for ordinary go commands, but you still have to use GOTOOLCHAIN=local go env -w GOTOOLCHAIN=... to get back out.

Note that the go command already does ignore unrecognized settings in the file.
It seems like encouraging GOTOOLCHAIN=local as the workaround is the right answer today.
It's almost always a mistake to set go env -w GOTOOLCHAIN=go1.19 anyway (as opposed to setting a normal environment variable that way), so I'm not sure we have to worry too much about this case.
On the other hand, suppose for the sake of argument that we special case go env -w GOTOOLCHAIN=... to not invoke the known toolchain and just handle that one case itself. What could go wrong if we didn't invoke a newer toolchain for that? I suppose a newer toolchain might do some extra sanity checking of the GOTOOLCHAIN value, so we'd be cutting ourselves off from that. Maybe that's not enough of a compelling reason? Maybe we should add the special case?

Another option to consider is to allow only a couple of recognized values (e.g. local, auto??) for go env -w GOTOOLCHAIN=.... Even for go1.22, I cannot think of a valid case where setting this is desirable. Accidentally setting go env -w GOTOOLCHAIN=go1.20 will result in an unpleasant  surprise when the user upgrades the local go version.
The only reason I encountered this issue was because I was messing with it to prototype an experimental idea. I ended up creating a special environment variable for the purpose.


feat: FVT for inference service.

closes #106
Motivation
Modifications
Result

Also, need to install the inferenceservice CRD in the Github Actions environment before ModelMesh Serving is installed.
Can probably just add a kubectl apply -f https://raw.githubusercontent.com/kserve/kserve/master/test/crds/serving.kserve.io_inferenceservices.yaml here.
For your local testing, I think just installing ModelMesh Serving then the above crd yaml should be fine. No need for Knative and Istio.

@ScrapCodes  Looks like the FVTs managed to pass here: https://github.com/kserve/modelmesh-serving/actions/runs/1932155743 but not the latest one. Was there anything different with the code that time versus the latest?

Hi @pvaneck, no difference, looks like test is flaky!


Provide a solution on how to embed Kyma extenssions in Busola

Description
Find the best solution to embed Kyma and ISTIO extensions in Busola.
Reasons
We want to have a solution that allows Busola integrators to embed extensions as part of the Busola deployment.
We want to decouple Busola code from the extension code.
Acceptance Criteria

[x] The extensions should be part of the built process and not part of the code

[x] Embedded extensions should not be visible on Busola extensions view.

[x] Our solution will allow performant way to cover 20+ extensions

[x] the POC will use existing ISTIO extensions as input	-

Question: the extensions files don't need to be stored in ConfigMap format, we could just store the data.

What about the version, which resides in metadata.labels? I think we should not care about the version, since we are to maintain them ourselves. ✅
This brings the topic of breaking changes - we need to test those views thoroughly.

Mayor takeouts, besides the connected PR:

version - we have an access to the versions (both the one of resource and a list of supported ones) during the build process, we could check the version of resource and show a warning or even stop the build
The extensions are built to YAML format - this format stays.
We don't need to edit our current kustomize config (as it was done in the PR) - we could provide yet another one, containing only the busola-builtin-resource-extensions.yaml and overrides for already deployed Busola deployment.
Would be nice to not only gather the extensions from extensions folder, but also have a file with pairs of extension link and version, that could be used to download extensions from the external sources, and use them during packing.

We have kyma-dashboard, so we can close it.


Gather Community Feedback on Proposal

https://forum.celo.org/t/governance-proposal-to-reward-early-users/662/2


Cannot Get Access Token

Hi,
I am trying to get Access Token, but failed. Error message is
Unable to retrieve access token for current auth strategy.
ReactStormpath.getAccessToken()
  .then((accessToken) => {
    fetch('http://localhost:3000/api/subscription', {
      method: 'get',
      headers: {
        'Authorization': 'Bearer ' + accessToken
      }
    });
  }).catch(() => {
    // Could not get access token, user is not logged in
  });

Then, realise there is no getToken method in the UserSerivce.js
Please verify this.
Thanks

I have a very similar issue. I am able to login and I see the the actions USER_SET, USER_LOGIN, USER_SET get dispatched. When I call ReactStormpath.getAccessToken() I get an uncaught type error:  "_reactStormpath2.default.getAccessToken is not a function"

@MadJay getAccessToken was not in version 1.3.3, but after I upgrade to 2.0, you will be able to access that function. However, at least from my tests, I couldn't get the access token.

@yangyu0311ugroop Are you using the Client API? The token store functionality is only accessible (at the time this was written) if you are. If you look at https://github.com/stormpath/stormpath-sdk-react/blob/master/src/app.js#L44, the Client-API-based ClientApiUserService is only used if you set up a base URI pointing to a different host for auth, otherwise we use the UserService which, as you rightly pointed out, does not support this operation.
@MadJay @yangyu0311ugroop was correct in pointing out only 2.X.X supports this (thanks, by the way :)). Is this still happening if you upgrade?

I did upgrade to 2.0.0 Thanks! I initially just took the NPM default version, the 'not a function' error is gone. I am no where yangyu0311ugroop  and am looking at your advice to him on this.

@Tweety-FER Thank you for pointing that out. I do not have different hosts so no base URI was set in App, so the question what will be the easiest way to fetch the access token from the React-SDK? Because some of the functions, I am trying to use is not in React-Stormpath-SDK, I need use standard API call.

I now capture the TOKEN_SET action to grab the access and refresh tokens as they are dispatched from the react-stormpath sdk. But my issue is now the same as @yangyu0311ugroop, I'm not sure how to capture the accessToken from the SDK other than via the dispatched TOKEN_SET action.

@yangyu0311ugroop @MadJay At the moment, I believe such "hacky" solutions are the only solution directly from the React SDK, when not using the Client API for your auth needs. This will probably change in the future, when the back-end integrations also begin to support the same flow that is currently used with the Client API.
However, if you are using one of the back-end integrations, maybe the simpler solution would simply be to proxy the calls through them, implementing the new endpoints there? It's a bit more complicated than just grabbing it, but it certainly can be done (you would need to grab the header and them use the nJwt or similar to unpack it).
On the other hand, if you're just doing authentication for the tokens and want to send the tokens elsewhere, maybe using the Client API feature is the better option? That's kind of the idea of it, and that's why the ClientApiUserService implements this feature in the first place. That way you can get the token when you need it and just pass it around to wherever you need it, and without the need to set up all the nitty-gritty details of Stormpath in the back-end.

@MadJay I figure it out finally. After you call React-Stormpath-Sdk login, cookie will be set from StormPath-Server (I an using the Express-Stormpath-Node).
From the front end, I am using whatwg-fetch. In the document, you shall have a look at sending cookie section. Basically, for the same origin. You use this.
fetch('/me', {
  credentials: 'same-origin'
})

And if you have different host, you use   credentials: 'include', cookie will pass along when you request. I have tested both, it works.
fetch('https://example.com:1234/users', {
  credentials: 'include'
})

I'm receiving a javascript error indicating that getAccessToken is not a function. When I look at the source in the repository I can see where the method is defined on the App class, but when I look in my node_modulesc folder (after forcing an install of<EMAIL_ADDRESS>the app.js file does not include this method.

Hello everyone, thank you for all the help and debug info!
As mentioned by @Tweety-FER, the 2.x upgrade is moving this library towards using the Stormpath Client API for authentication.  This change makes your app simpler, because you don't need extra code in your server to handle login, you just need to focus on protecting your endpoints with the access token that you can now get from the Client API.
In 2.0.0, the internal logic says "if the endpoints.baseUri is the same domain as the current page, use our traditional cookie approach for storing the token".  In this case, getAccessToken() won't work becuaes the token is hidden in a secure cookie.
I don't see a way to override this behaviour, so I'm proposing a change to make the cookie mode an opt-in configuration, so that you can use the new token strategy as the default, with both the Client API and your own server.
Please see #175 for my proposed changes.  Thanks!

Why doesn't the 2.0.0 version of the react-stormpath package reflect the source in this repository? Will that be changing any time soon?

Hi @GodsBreath , I do see that the file app.js in the es6 and lib folders is out of date, I'm not sure why that is, @typerandom can you look at this with me?
@GodsBreath can you tell us how you're wanting to include the files in your project?  Thanks.

I'm using npm + webpack.
Thanks for looking into this!

Forgot to tag you, @robertjd. I assume you have other ways of getting notified of activity in these threads, though.

Hi @GodsBreath , thanks for the ping - unfortunately we haven't had a chance to look into the issue with app.js.  Could you compare your webpack configuration to what we have in our example app? I'm curious, because while the app.js file isn't getting updated, our example app is still working (I'm assuming it requires/imports the index.js instead of app.js).  The example app is here:
https://github.com/stormpath/stormpath-express-react-example
Thanks!

Thanks for your reply, @robertjd . I think you're onto something with the webpack configuration. The only differences I see are implementation-specific. However, based on your suggestion I looked at the lib/index.js. Initially it did not match the contents of index.js from installing node dependencies for your example app. However, installing the package again in my own app updated the index.js file.
However, once I ran webpack in my project, the contents of index.js reverted back to the old, outdated version! I don't know what it could be if not my webpack configuration.

Thanks @GodsBreath !  Could you show me your webpack configuration file, and also show me how you're requiring or importing our library?  Thanks!

webpack.config.js
`var webpack = require('webpack');
var path = require('path');
var BUILD_DIR = path.resolve(__dirname, 'public/javascripts');
var APP_DIR = path.resolve(__dirname, 'src');
var config = {
entry: {
devotionals: APP_DIR + '/devotionals.jsx'
},
output: {
path: BUILD_DIR,
filename: '[name].js'
},
module: {
loaders: [
{
test: /.jsx?/,
include: [
APP_DIR
],
loader: 'babel'
}
]
}
};
module.exports = config;`
main.js
import React from 'react'; import {render} from 'react-dom'; import { Col, Row, Table, Label, ButtonGroup, Button } from 'react-bootstrap'; import ReactStormpath, { Router, LoginRoute, AuthenticatedRoute, HomeRoute, LogoutLink } from 'react-stormpath'; import { Route, browserHistory } from 'react-router'; ...

Added a prepublish hook in #178 to avoid the possibility of outdated files.
As for this latest issue, I've been trying to look into it, but I cannot seem to reproduce it. The babel-loader's configuration seems fine, as the whitelist include should automatically exclude node_modules. However, we discussed, I noted one odd thing about the package when downloaded with npm: unlike when building manually, where only index.js is created, the downloaded version also contains all the other files, just transpiled. No idea what that's about, as we have no hooks/scripts that should be doing this. Something very odd is going on, all in all. Will investigate more, but so far no luck.

@Tweety-FER
I'm going to try moving the project files to a different folder that isn't a git repository. Even though I have a git ignore for node_modules, it seems possible that git may be somehow responsible for changing the file.

@Tweety-FER
I was right. I moved all of the files (minus git-related files, hidden or otherwise) to a completely different directly. So far, the file has remained stable. No unexpected changes. This must be some kind of git bug!

@GodsBreath Good to hear you found a way around it, but very odd, I have to say. Did you have any git hooks set up? That's really the only thing that's coming to mind, never seen something like this before otherwise.

@Tweety-FER
I'm sorry to say that just moments ago the issue began recurring, after several days developing with no problems. I had never heard of Git hooks until I read your comment.

@GodsBreath Hm, thanks for the report. Getting more odd by the minute. Could you give me the contents of your package.json?

  "name": "ods",
  "version": "0.0.0",
  "private": true,
  "scripts": {
    "build": "webpack -d",
    "start": "bin/www"
  },
  "dependencies": {
    "body-parser": "~1.15.2",
    "cookie-parser": "~1.4.3",
    "debug": "~2.2.0",
    "express": "~4.14.0",
    "express-stormpath": "^3.1.7",
    "jade": "~1.11.0",
    "moment": "^2.17.1",
    "mongodb": "^2.2.16",
    "morgan": "~1.7.0",
    "react": "^15.4.2",
    "react-bootstrap": "^0.30.7",
    "react-dom": "^15.4.2",
    "react-router": "^3.0.2",
    "react-router-bootstrap": "^0.23.1",
    "react-stormpath": "^2.0.0",
    "reqwest": "^2.0.5",
    "serve-favicon": "~2.3.0"
  },
  "devDependencies": {
    "babel-core": "^6.21.0",
    "babel-loader": "^6.2.10",
    "babel-preset-es2015": "^6.18.0",
    "babel-preset-react": "^6.16.0",
    "webpack": "^1.14.0"
  }
}```

Hi all, we found that the latest tag in npm was linked to 1.3.5, this was a mistake when we published a patch on the 1.x series.  The tag has been fixed and now points to 2.0.0.  This issue may have caused you problems, we fixed it several days ago (my bad for not following up here!).
@GodsBreath I'm happy to do some pair programing to see what's going on with your situation (I'd like to understand for posterity).
Otherwise, I would like to close this issue as it seems we have resolved the other problems by fixing the latest tag.


Upgrading introduction paragraph and contribution guide

What changed? Why?
Updated the introduction and the contribution guide section.
Notes to reviewers
How has it been tested?

@fakepixels run yarn format to format the mdx files

@kyhyco thx for the guidance!


'Overview' object has no attribute 'ScreenerView'

Hi I am running the example in the documentation and I am getting this error
from finvizfinance.screener.overview import Overview

foverview = Overview()
filters_dict = {'Index': 'S&P 500'}
foverview.set_filter(filters_dict=filters_dict)
df = foverview.ScreenerView()

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
/var/folders/7g/gr9fl0cx43g5f42xf78n_str0000gn/T/ipykernel_59856/4129785455.py in <module>
      2 filters_dict = {'Index': 'S&P 500'}
      3 foverview.set_filter(filters_dict=filters_dict)
----> 4 df = foverview.ScreenerView()

AttributeError: 'Overview' object has no attribute 'ScreenerView'

I cannot understand the reason.

Sorry for the late response. The most functions have changed the function name to meet the python coding style. So ScreenerView has changed to screener_view. Please refer to the latest doc (https://finvizfinance.readthedocs.io/en/latest/index.html) for others. Thanks.


[klima data]  Make Verra credits breakdown match design

Description
Make Verra credits breakdown match design
Related Ticket
Resolves #1732
Changes

Before
After

Checklist

[x] I have run npm run build-all without errors
[x] I have formatted JS and TS files with npm run format-all

@biwano preview link on this one is broken?

@biwano preview link on this one is broken?

Sorry about that, The link should work now.


DR-HPF004S can rotate further - -75/+75 horizontal; -30/90 vertical

DR-HPF004S has a greater range of angles than other models; therefore need to update the min/max values

How does that impact other models?
Don't we need to adjust per model?

I guess the ideal long term solution is yes adjust per model. I only have this fan so hard to say what it does to other models.

Each model sends back their ranges in the api call to get their definitions. I'm working on a larger refactor and once that's done we should be able to better auto detect this stuff.

Will implement this differently - We need to look at the device list and look for limits in the returned JSON.


Multiple designs with Sky130 fakerams/SRAMs face 'routing congestion too high' error at Global Routing step

Description
Designs (BSG manycore_proc_vanilla, BlackParrot frontend) face 'routing congestion too high' error at Global Routing Step. This congestion issue has been occurring on many designs using sky130 fakerams/real SRAMs. Another previous design on which this was faced was a Serv processor design with SRAM macros (Similarly even on other designs with Sky130 SRAMs). This issue was also occurring on OpenROAD-flow-scripts but they have fixed it in this pull request. After this fix, all these designs (with sky130 SRAMs) that were failing to pass global routing (on OpenROAD-flow-scripts) due to congestion were able to pass global routing easily (on OpenROAD-flow-scripts).
The fix they applied was to remove a certain option used to avoid routing too close to macros (it's the 'set_macro_extension' option in the fastroute config). Could this congestion issue on OpenLane also be stemming from the same root cause?
I tried looking through the OpenLane scripts but could not figure out quite how the fasteroute config. might be getting handled.
Environment
Python: v3.8.10
Kernel: Linux v4.19.128-microsoft-standard
Distribution: ubuntu 20.04
Container Engine: docker v20.10.8
OpenLane Git Version: 2021.12.25_01.36.09
---
PDK Version Verification Status: FAILED
Could not find SOURCES file for the installed sky130A PDK.
Traceback (most recent call last):
  File "/mnt/c/Users/LENOVO/Documents/gsocbp/OpenLane/dependencies/verify_versions.py", line 66, in verify_versions
    sources_str = open(sources_file).read()
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/c/Users/LENOVO/Documents/gsocbp/OpenLane/pdks/sky130A/SOURCES'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/mnt/c/Users/LENOVO/Documents/gsocbp/OpenLane/dependencies/verify_versions.py", line 68, in verify_versions
    raise Exception("Could not find SOURCES file for the installed sky130A PDK.")
Exception: Could not find SOURCES file for the installed sky130A PDK.

Failed to compare PDKs.
---
Git Log (Last 3 Commits)

commit efc75133f0e7ea23424febcdbf8b56203bcef6ab
Author: Donn<EMAIL_ADDRESS>Date:   Fri Dec 24 13:08:02 2021 +0200

    Typo (#801)

    [skip ci]

commit 16d977225a3982e5e5c7887dfcbb903b21f68b1f
Author: Donn<EMAIL_ADDRESS>Date:   Fri Dec 24 13:07:50 2021 +0200

    The Perl Purge (#800)

    `cts_simple.pl`, `analyze.pl` and `libtrim.pl` translated as literally as possible to Python.

commit ec1e6bec68a94a0aa37964cf6aa1a62f930eaf66
Author: Donn<EMAIL_ADDRESS>Date:   Fri Dec 24 01:45:19 2021 +0200

    Update environment survey, allow configuring python versions (#794)

    * Update environment survey

    This updates the issue environment survey to better detect whether it's running inside the OpenLane container or not, and properly discourage people from doing so.

    * Make the version of Python used configurable via environment variable

    [skip ci]

Reproduction Material

Designs:
bsg_manycore_proc_vanilla_fakeram.tar.gz
bp_fe.tar.gz

Command used: ./flow.tcl -design bsg_manycore_proc_vanilla_fakeram, ./flow.tcl -design bp_fe

Expected behavior
These two designs (and the others previously seen to face this issue) easily complete the flow on OpenROAD-flow-scripts, so expecting the designs to be able to complete the flow without congestion on OpenLane too.
Logs
[INFO GRT-0102] Iteration 19
[INFO GRT-0126] Overflow report:
[INFO GRT-0127] Total usage          : 1737041
[INFO GRT-0128] Max H overflow       : 7
[INFO GRT-0129] Max V overflow       : 7
[INFO GRT-0130] Max overflow         : 7
[INFO GRT-0131] Number overflow edges: 46803
[INFO GRT-0132] H   overflow         : 31704
[INFO GRT-0133] V   overflow         : 41400
[INFO GRT-0134] Final overflow       : 73104

[WARNING GRT-0227] Reached 20 congestion iterations with less than 15% of reduction between iterations.
[INFO GRT-0104] Minimal overflow 67743 occurring at round 10.
Usage checked
[INFO GRT-0105] Maze routing finished.
Final 2D results:
[INFO GRT-0126] Overflow report:
[INFO GRT-0127] Total usage          : 1737041
[INFO GRT-0128] Max H overflow       : 7
[INFO GRT-0129] Max V overflow       : 7
[INFO GRT-0130] Max overflow         : 7
[INFO GRT-0131] Number overflow edges: 46803
[INFO GRT-0132] H   overflow         : 31704
[INFO GRT-0133] V   overflow         : 41400
[INFO GRT-0134] Final overflow       : 73104

[INFO GRT-0106] Layer assignment begins.
[INFO GRT-0107] Layer assignment finished.
[INFO GRT-0197] Via related to pin nodes: 190337
[INFO GRT-0198] Via related Steiner nodes: 136
[INFO GRT-0199] Via filling finished.
[INFO GRT-0111] Final number of vias: 272661
[INFO GRT-0112] Final usage 3D: 2555024
[ERROR GRT-0118] Routing congestion too high.
Error: groute.tcl, 66 GRT-0118
[ERROR]: during executing openroad script /openlane/scripts/openroad/groute.tcl
[ERROR]: Exit code: 1
[ERROR]: Last 10 lines:
child process exited abnormally

Congestion Map (taken using OpenROAD GUI)
Congestion map of bsg_manycore_proc_vanilla_fakeram design (taken at global route step)

Propagate macro_extension from openroad to openlane as shown in the pull request.


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/ranger-fm-feedstock#2.


add ability to specify appName on a per msg

Hi,
use senario:  I have several libraries running on the same ESP, doing a variety of things. With debugging enabled I'd like to be able to send debug messages from different bit of software on the same device.  so the device name is the same, but the app name is different.
Would be great to have overloads to be able to specify the log level and app name for a message.
what do you think?

Yes it's possible to implement. There is only one problem with logf functions without pri parameter because of varargs. You cannot have defined both logf(const char *, ...) and logf(const char *, const char *, ...).
Anyway in one of my project I call appName before log / logf methods to do same as you describe:
IPAddress ip = WiFi.localIP();
syslog.appName("network").logf(LOG_INFO, "Assigned %s.local [%u.%u.%u.%u]", DEVICE_HOSTNAME, ip[0], ip[1], ip[2], ip[3]);

Only caveats is that appName store the value for following calls of log / logf. So you have it everywhere.

yes. i realised that.  and there is no function to fetch it, set the new one, then set it back to the old one!

i wonder what the most elegant solution would be.  Think its worth having!

I've come up with a method that might work.  I'm going to try an roll it into my own syslog attempt for my ESPManager software.  I've written a string class with derived versions myStringf and mystgingf_P with constructors that take the ....  This allows you to do this:
log( "appName", myStringf_P( PSTR("Test %u"), "123" );
log( "appName", myStringf("Test %u", "123" );
log( "appName", "123" );

Using the right move semantics makes it efficient...

I've use some of your code to write my own syslog client, mainly the log mask stuff and message generation.  I've given you credit for it at the top of the .h is that ok.  There is no licence in the repo so I want to check? Its all none profit, open source stuff.

I closed this by accident.  sorry.


chg: usr:  contact Gregor: Paper 2 submission for S17-IR-2028, removed the styles folder

I am closing this pull request and ignore it as you have notified me you did something els. however you forgot to close this pull request. If you still need some changes, make sure to create a new pull request. Make sure yo are in sync with the repo and always rebase.


Loading annotate/annotate_models breaks ActiveRecord dynamic finders

'annotate/annotate_models.rb' uses a monkey patched :method_missing to get around the problem of recognizing unknown macros ('acts_as_something' and the like).  This monkey patch is only meant to be loaded when running the rake task to create annotations.
Unfortunately, we are requiring the 'annotate/annotate_models.rb' file to load in order to modify the output with comments.  If we remove the requirement, our modification hook will never be inserted because the environment (and all gems) are loaded by the annotation rake task before the 'annotate/annotate_models.rb' file.
We'll need to find an alternative hooking method that doesn't require including the 'method_missing' monkey patch.

As a possible workaround, see this commit that moves the monkey patch to a separate file that only loads when running the rake task - https://github.com/pinnymz/annotate_models/commit/aae82380edd8561944402ada717239c4b0b98e27


add support for linux ARM64

hardhat-zksync-solc plugin is unable to compile contracts or be used at all when using ubuntu 22.04 on ARM. I am personally using ubuntu on apple M1 but I believe even more common setups of linux/ubuntu on ARM64 metal will run into the same issue I did.
Took me a while to locate this repo as the origin of the issue: the zksolc binaries that are pulled via the @matterlabs/hardhat-zksync-toolbox suite of hardhat plugins don't support linux ARM and so an 'unusable' error is thrown (shown in the screenshot below) by the plugin when attempting to compile contracts in hardhat.
In the meantime, it may be worth including a snippet noting that compiling/deploying contracts to zksync using zksolc on linux ARM is not currently possible, to save developers the debugging time/headache. If you agree, I can add that as a blurb to the contract deployment tutorial and quickstart guides.
I am using:
yarn version 1.22.19
nodejs v18.13.0
solidity ^0.8.0
ethers 5.7.2

@robriks @pauldowman but how are using solc on this platform?

@hedgar2017 It's used by the hardhat-zksync-solc npm package, which tries to download it: https://github.com/matter-labs/hardhat-zksync/blob/60c33dfef3b1c6567351fbc87dff3a9b87514c3b/packages/hardhat-zksync-solc/src/utils.ts#L89
On a Mac using Docker it generates this URL: https://github.com/matter-labs/zksolc-bin/raw/main/linux-arm64/zksolc-linux-arm64-musl-v1.3.10
...which is a 404.

@hedgar2017 It's used by the hardhat-zksync-solc npm package, which tries to download it: https://github.com/matter-labs/hardhat-zksync/blob/60c33dfef3b1c6567351fbc87dff3a9b87514c3b/packages/hardhat-zksync-solc/src/utils.ts#L89
On a Mac using Docker it generates this URL: https://github.com/matter-labs/zksolc-bin/raw/main/linux-arm64/zksolc-linux-arm64-musl-v1.3.10
...which is a 404.

I see. We'll fix the hardhat error.
As for zksolc, we'll see what we can do, but we won't be able to support ARM64 Linux very soon.

OK, so developing with Docker on a Mac is unsupported for now. Thanks for looking into it! 🙇


Import shadow fix

Description
Import shadow fix
Type of change

Fix (non-breaking change which fixes an issue)

Testing steps
To be checked on CI.
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Patch and project coverage have no change.

Comparison is base (1b8deb7) 95.84% compared to head (b4a68a0) 95.84%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #304   +/-   ##
=======================================
  Coverage   95.84%   95.84%
=======================================
  Files          41       41
  Lines        1372     1372
=======================================
  Hits         1315     1315
  Misses         41       41
  Partials       16       16

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


Publishing PreRelease content (to OntoServer)

Our aim is to develop new SNOMED content in volume for Pathology in the UK using a more Agile approach than has been taken in the past. One part of this is to be able to publish pre-release content quickly and easily to users so they can provide feedback before the content is "solidified" in a Live SNOMED release.
Ultimately this could support daily Beta release builds as implemented (I believe) by SNOMED International
Describe the solution you'd like
We want to be able to publish UK Pathology Module content, whether pre-release or Live versioned material, via the CSIRO OntoServer platform. Having spoken to the CSIRO team about the requirements that platform has for loading RF2, and particularly pre-release content we have identified a number of gaps that will need to be bridged to meet this requirement, direct testing will be required to prove whether this list is complete-
Requirements (general)

A Module Dependency Refset (MDR) file that represents the full dependency tree of the selected UK SNOMED Module
Availability of the Modules referenced in the MDR, either within the single RF2 export file or accessible separately
Valid non-null effectiveTime values in the exported data to allow dependencies to be reconciled during load

Requirements (Pre-Release content)

File naming within the RF2 package, as specified in the SI documentation, that uses the "x" prefix to denote non-Live content
Full timestamps (i.e date+time) in effectiveTime values of pre-release modules (note, the OntoServer platform does not strictly demand this, but we understand this is the recommendation from SI for the format of pre-release data)
Content loaded with a version URI rooted at http://snomed.info/xsct (vs http://snomed.info/sct for Live content)

Describe alternatives you've considered
There are two options for exporting prerelease content we are aware of (there may be others).

We can export RF2 from a task branch in SnowOwl. This gives us-

Blank/null effectiveTime values
Empty MDR file
Does not follow pre-release file naming patterns within the RF2 export

In theory we could implement an approach where we "rewind time" by-

Creating a snapshot of the SnowOwl content just before versioning
Versioning the content
Generating a release

then-

Reverting the snapshot to put the SnowOwl instance back in the state before versioning
Continuing to edit content in the task branch

This gives us (we believe)-

Valid dates in the effectiveTime values, (but not datetime format)
An MDR file based on SnowOwl's notion of the module dependencies, which does not represent the full scope of the UK module set
Does not follow pre-release file naming patterns within the RF2 export

By comparison we believe publishing Live content to OntoServer should be more straightforward, but the issue with the MDR remains.
None of these options represent a smooth direct path to publishing content. In particular the format of exported PreRelease content is quite a long way from the required structure.
I would like B2i's comments on these requirements. What might be on the roadmap already, and what is not. The technical feasibility of possible solutions, and any issues with the requirements overall would also be of interest.

With apologies- this RFE was inadvertently submitted twice due to a session timeout. Closing one copy.


Deployment w/ GitHub Pages

Hi,
I am having trouble deploying the website with GitHub pages. For example, I have followed the setup instructions and have the site working on my local machine. How can I make this my personal webpage?
Thanks for the help

You can follow this guide to setup a github.io domain page.
Then, your Hugo website project should contain a /public dir, this is the content that should go into the repo created following the guide. Pushing to it should deploy the running website.
In my website repo, I have the public folder as a git submodule linking to the website repo, this way, when I run hugo, the public folder gets updated. I can then just push this folder to have an updated website.
I saw that you have your Hugo project directly into your *.github.io repo, which is wrong. Indeed this should contain the /public Hugo output.
Let me know if this makes sense.


Allow configuring executor resources per pod

Summary
Currently executor resources is configured in the workflow controller configmap globally.  Configuring it per pod would be nice.  Maybe this can already be done with podSpecPatch, not sure.
Use Cases
Some steps have huge artifacts, while others not so much.  Currently tuning resources on the executor globally for the worst case, which wastes resources on the cluster.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

yes, You can set init/wait for container resource quota using podSpecPatch

Will do, thanks!


CI for Node

✕ Contains the compiled JavaScript (10 ms)
✕ Initializes with two players (4 ms)
✕ Starts the game with a random player (1 ms)
✕ Sets the current player to be whoever it is not (1 ms)


flynn docker push fails with latest OS X Docker CLI

flynn docker push meroje/alpine-nchan
flynn: getting image config with "docker inspect -f {{ json .Config }} meroje/alpine-nchan"
flynn: tagging Docker image with "docker tag --force meroje/alpine-nchan docker.example.com/nchan:latest"
unknown flag: --force

Seems docker tag doesn't have --force flag anymore:
docker tag --help

Usage:	docker tag IMAGE[:TAG] IMAGE[:TAG]

Tag an image into a repository

Options:
      --help   Print usage

flynn version
v20160714.0

This was fixed by #3106. The fixed binary will roll out with tonight's nightly.


additionalProperties (object) fails to validate

Hello!
I am using NSwag to model a swagger.json that is valid for CouchDB - and it seems to me, that the validation of attachments does not work correctly.
{
  "id": "https://localhost/array",
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "couchDoc": { "$ref": "#/definitions/CouchDBDoc" }
  },
  "definitions": {
    "CouchDBDoc": {
      "properties": {
        "_id": {
          "type": "string"
        },
        "_rev": {
          "type": "string"
        },
        "_attachments": {
          "type": "object",
          "additionalProperties": {
            "type": "object",
            "properties": {
              "content_type": {
                "type": "string"
              },
              "revpos": {
                "type": "string"
              },
              "digest": {
                "type": "string"
              },
              "length": {
                "type": "integer",
                "format": "int32"
              },
              "stub": {
                "type": "boolean"
              }
            }
          }
        }
      },
      "type": "object"
    }
  }
}

And the json fragment:
{
  "couchDoc": {
    "_id": "a8efd3c91985279c8f4882e14f33551e",
    "_rev": "1-d1ec00873703cc1e6a41554de2eebe77",
    "_attachments": {
      "image": {
        "content_type": "application/octet-stream",
        "revpos": 1,
        "digest": "md5-l7ZIe3+wrfBKB5qROXH3hw==",
        "length": 236694,
        "stub": true
      }
    }
  }
}

I made a small standalone schema and a unit test for it.
UnitTestProject1.zip

I serialized the validation result:
[   {     "Errors": {       "NJsonSchema.JsonSchema4": [         {           "Kind": 1,           "Property": "revpos",           "Path": "#/couchDoc._attachments.image.revpos"         }       ]     },     "Kind": 35,     "Property": "image",     "Path": "#/couchDoc._attachments.image"   } ]
As you can see, you defined revpos as string but in the test data, the property is an integer....
 Sorry.

No problem. Thanks for using the library.


Debugging performance: handle events properly ( stopPropagation )

Hi,
I would like to debug performance of interaction of my app, and see if I am handling events properly.
I have a stage associated with pinch gesture.
Above the stage, I have several sprites with each own its texture.
I would like to capture the event on the stage, and prevent trickling down do the images (pinch is only associated to stage)
I would like to prevent bubble up of events associated to textures (pointertap is only associated to textures).
Each texture is interactive with a pointertap interaction, like:
ui.thumbnail.interactive = true;
    ui.thumbnail.buttonMode = true;
    ui.thumbnail.on('pointertap', function(e){
   // do things
}

I would like a debrief on how events are handled here VS events on DOM (I was using Hammer.js),
and understand how to properly handle events on pixi (reading here about DOM: https://stackoverflow.com/questions/4616694/what-is-event-bubbling-and-capturing)
and understand how to track or debug if I am doing it correctly :)
Do I have to stopPropagation() ? Is it handled by default on textures ? ...

If I actually understand your question, then the answer is: "Yes, stopPropagation will prevent the event from going to any other objects". This is listed in the docs (and source):
https://github.com/pixijs/pixi.js/blob/3031846ba0791b072d1a8b3ef1c699a3f090bd87/src/interaction/InteractionEvent.js#L51-L55

How does propagation works for objects in canvas VS objects in DOM ?
Does stopPropagation for objects apply for both propagating to parent elements and child elements  ?

JS has no "objects in canvas". All interaction events in pixi are purely within pixi and have nothing to do with the DOM.
The events in pixi use bubbling, in that it first emits on the element then all parents. in sequence If you call stopPropagation it will not travel any higher up the hierarchy.
In DOM there are multiple event phases (capture & bubble), as well as multiple ways to change the behavior of the event/browser (preventDefault & stopPropagation). Try not to get the two systems confused with eachother. The browser doesn't dispatch any events on the pixi objects, that is just pixi.


[422] Import school rake task runs automatically everyday at 2am

Some reordering and group of other rake tasks in terraform as the files begin to get quite long now
Remove duplicate DSI configuration set on ECS

 Ensure hiring staff who belong to knew schools can sign-in if invited

Rebased


Add ability to shut specific workspace

In this change we introduce the ability to shut specific workspaces with the command "shut ". In order to shut all workspaces we now need to use "shut all". I tried to make just "shut" work but wasn't obvious.
This works by just adding the workspace as an attribute to the minion objects, which we can then easily filter by when closing windows.

"I am not afraid of storms, for I am learning how to sail my ship." - Louisa May Alcott/(maybe) Eugene


[R20-446][R20-430] Add complex image dynamic component mapping

Issue:

https://digital-vic.atlassian.net/browse/R20-446
https://digital-vic.atlassian.net/browse/R20-430

What I did

Integrate built complex image (RplMediaEmbed) with mapping to Tide landing page component
Investigate generator templating (will do a separate PR)

How to test

pnpm -F nuxt-app dev

/sdpta-complex-image-landing-page-fixture
/publication-cc-1

Checklist

For all PR's

[ ] I've added relevant changes to the project Readme if needed.
[ ] I've updated the documentation site as needed.
[x] I have added unit tests to cover my changes (if not applicable, please state why in a comment)

For new components only

[ ] I have added a story covering all variants
[ ] I have checked a11y tab in storybook passes
[ ] Any events are emitted on the event bus

:hand: Just adding a note here, this implementation has dropped some functionality from ripple 1, specifically the ability to set a non-source caption and override the three link labels (view fullscreen / show data / download). All of these are still provided by the Tide API, so we may need to revisit this if there is demand for these fields.


2.8.0 OOM

2.8.0 version OOM always， update from 2.7.2

@HarveyJie are you using remote_write?

@codesome yes!, I use remote_write  by timesale

remote_write uses WAL in 2.8.0 which apparently takes more memory than before. Work is in progress here https://github.com/prometheus/prometheus/pull/5316 to reduce the memory usage.


fix(timestamp): toMicros() should work for all timestamps fitting in bigint

As #7506, toMicros() throws because the computation overflows when multiplying
negative number then add positive number. In this case the final result still
fits in int64_t. This PR fixes this issue by using int128_t to make sure the
computation does not overflows.

@laithsakka @kagamiori Would you please help review this fix similar to toMillis()? Thanks!

@laithsakka @kagamiori @pedroerp Hey, could you please help review this? Thanks!