vc_dispmanx_display_open: command not found

I've installed a fresh copy of Raspberry Pi OS Lite (Bullseye) onto a Raspberry Pi Zero W and I've installed fbcp-ili9341 using the pirate-audio display mode, and when I try to run it, it says vc_dispmanx_display_open failed! Make sure to have hdmi_force_hotplug=1 setting in /boot/config.txt. If I try to run vc_dispmanx_display_open in my shell, it says -bash: vc_dispmanx_display_open: command not found. I think that it might not be installed but I can't seem to find a package for it. I need help finding the package/getting the correct settings to make this work. Thanks in advance!
EDIT 1:
I forgot to mention that I have added hdmi_force_hotplug=1 in my /boot/config.txt

Some logs in case they help. After running fbcp-ili9341 on my rpi3 5.10.92-v7+ the display turns from white to black suggesting wiring is ok.
pi@raspberrypi3:~/test/build $ sudo ./fbcp-ili9341
bcm_host_get_peripheral_address: 0x3f000000, bcm_host_get_peripheral_size: 16777216, bcm_host_get_sdram_address: 0xc0000000
BCM core speed: current: 250000000hz, max turbo: 400000000hz. SPI CDIV: 40, SPI max frequency: 10000000hz
Allocated DMA channel 7
Allocated DMA channel 1
Enabling DMA channels Tx:7 and Rx:1
DMA hardware register file is at ptr: 0x75ca0000, using DMA TX channel: 7 and DMA RX channel: 1
DMA hardware TX channel register file is at ptr: 0x75ca0700, DMA RX channel register file is at ptr: 0x75ca0100
Resetting DMA channels for use
DMA all set up
Initializing display
Resetting display at reset GPIO pin 22
Setting TFT backlight on at pin 18
Creating SPI task thread
InitSPI done
vc_dispmanx_display_open failed! Make sure to have hdmi_force_hotplug=1 setting in /boot/config.txt

pi@raspberrypi3:~/test/build $ tail /var/log/syslog -n 50
Apr 13 13:18:54 raspberrypi3 fbcp-ili9341: vc_dispmanx_display_open failed! Make sure to have hdmi_force_hotplug=1 setting in /boot/config.txt
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: mmap() failed: Cannot allocate memory
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Failed to create permanent mapping for memfd region with ID =<PHONE_NUMBER>
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Failed to register memfd mempool. Reason: could not attach memfd SHM ID to pipe
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: mmap() failed: Cannot allocate memory
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Disabling srbchannel, reason: Failed to allocate shared writable memory pool.
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: mmap() failed: Cannot allocate memory
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Failed to create permanent mapping for memfd region with ID =<PHONE_NUMBER>
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Error opening PCM device hdmi:1: No such device
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Ignoring received block reference with non-registered memfd ID =<PHONE_NUMBER>
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Ignoring received block reference with non-registered memfd ID =<PHONE_NUMBER>
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Ignoring received block reference with non-registered memfd ID =<PHONE_NUMBER>
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Ignoring received block reference with non-registered memfd ID =<PHONE_NUMBER>
Apr 13 13:18:54 raspberrypi3 pulseaudio[582]: Ignoring received block reference with non-registered memfd ID =<PHONE_NUMBER>
Apr 13 13:18:54 raspberrypi3 kernel: [  834.137797] hdmi-audio-codec hdmi-audio-codec.2.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -19
pi@raspberrypi3:~/test/build $

Does this issue help? https://github.com/juj/fbcp-ili9341/issues/100

I think this might be a problem with Bullseye because I switched over to retropie (buster) and it worked. Issue #100 seems to be the same problem and they fixed it with a downgrade.

Tried #100 setting GL driver to 'Legacy', still no luck but the message changed:
pi@raspberrypi3:~/fbcp-ili9341/build $ sudo ./fbcp-ili9341
bcm_host_get_peripheral_address: 0x3f000000, bcm_host_get_peripheral_size: 16777216, bcm_host_get_sdram_address: 0xc0000000
BCM core speed: current: 250000000hz, max turbo: 400000000hz. SPI CDIV: 30, SPI max frequency: 13333333hz
Allocated DMA channel 7
Allocated DMA channel 1
Enabling DMA channels Tx:7 and Rx:1
DMA hardware register file is at ptr: 0x75b44000, using DMA TX channel: 7 and DMA RX channel: 1
DMA hardware TX channel register file is at ptr: 0x75b44700, DMA RX channel register file is at ptr: 0x75b44100
DMA RX channel 1 was assigned another peripheral map 5!
DMA channel 0 has peripheral map 0 (is lite channel: 0, currently active: 0, current control block: (nil))
DMA channel 1 has peripheral map 5 (is lite channel: 0, currently active: 1, current control block: 0xff533a40)
DMA channel 2 has peripheral map 11 (is lite channel: 0, currently active: 1, current control block: (nil))
DMA channel 3 has peripheral map 17 (is lite channel: 0, currently active: 1, current control block: (nil))
DMA channel 4 has peripheral map 13 (is lite channel: 0, currently active: 1, current control block: (nil))
DMA channel 5 has peripheral map 0 (is lite channel: 0, currently active: 0, current control block: (nil))
DMA channel 6 has peripheral map 13 (is lite channel: 0, currently active: 1, current control block: (nil))
DMA channel 7 has peripheral map 0 (is lite channel: 1, currently active: 0, current control block: (nil))
DMA channel 8 has peripheral map 0 (is lite channel: 1, currently active: 0, current control block: (nil))
DMA channel 9 has peripheral map 0 (is lite channel: 1, currently active: 0, current control block: (nil))
DMA channel 10 has peripheral map 0 (is lite channel: 1, currently active: 0, current control block: (nil))
DMA channel 11 has peripheral map 0 (is lite channel: 1, currently active: 0, current control block: (nil))
DMA channel 12 has peripheral map 0 (is lite channel: 1, currently active: 0, current control block: (nil))
DMA channel 13 has peripheral map 0 (is lite channel: 1, currently active: 0, current control block: (nil))
DMA channel 14 has peripheral map 0 (is lite channel: 1, currently active: 0, current control block: (nil))
DMA RX channel was assigned another peripheral map!

Downgrade to buster may not be an option for some users. I for example would like to use this display with a Raspiblitz node.

Got it to work, all I had to do was change DMA channels after setting GL driver to 'Legacy' on raspi-config menu.
pi@raspberrypi3:~ $ cmake -DADAFRUIT_ILI9341_PITFT=ON -DILI9341=ON -DSPI_BUS_CLOCK_DIVISOR=30 -DARMV8A=ON -DGPIO_TFT_DATA_CONTROL=26 -DGPIO_TFT_RESET_PIN=22  DDMA_TX_CHANNEL=0 -DDMA_RX_CHANNEL=5 ..

Got it to work, all I had to do was change DMA channels after setting GL driver to 'Legacy' on raspi-config menu.
pi@raspberrypi3:~ $ cmake -DADAFRUIT_ILI9341_PITFT=ON -DILI9341=ON -DSPI_BUS_CLOCK_DIVISOR=30 -DARMV8A=ON -DGPIO_TFT_DATA_CONTROL=26 -DGPIO_TFT_RESET_PIN=22  DDMA_TX_CHANNEL=0 -DDMA_RX_CHANNEL=5 ..

Thank you, that solved the issue for me also. In my case:
cmake -DSPI_BUS_CLOCK_DIVISOR=30 -DWAVESHARE35B_ILI9486=ON -DDMA_TX_CHANNEL=0 -DDMA_RX_CHANNEL=5 ..

But i have some sort of overlay with stats. Is that normal? How do i get rid of it?


get_obs_surface no available data behaviour

What should be the behaviour when get_obs_surface can't find any data? I've just set it to return an empty ObsData object, does thi sound right?

Yes I think returning some form of nothing would be best here. If/when we can log then this would be a good thing to add to a log but maybe a print statement for now to alert the user that nothing was found with the passed inputs?
Is ObsData.data being set to a None?
Personally I would prefer it returned None, because it's more clear that nothing was found - an empty ObsData object requires further investigation but if ObsData.data is being set to a None that might be clear enough.


[WIP] update impostors, closer to original implem

This is another attempt to update impostors in LMNN (like #223), closer to the original implementation

I think it now works on my machine, so I guess the only thing needed is a bit of refactoring, but at first sight, what do you think @bellet @perimosocordiae ?

Also, the test example does not have a decreasing number of active constraints. I'll try to find an example where it's the case, also where the original impostors are not the ones at the end. This way, everything will be properly tested.

So I tried on another example (more features, and more noise, to be more like what we saw in #208 , that is to say distances between points don't separate them well at first) where the number of active constraints diminishes, and it does not work anymore (the values are still similar but not exactly the same). I'll try to find why.
I'll re-read the modifications I did, and also try to look at the gradient, see if it suddenly differs at some point and why...

Looks fine at first sight

I just added the more robust test where the number of impostors varies and it fails this time on my machine (at iteration 21, the gradient is quite different, I checked if it could be some accumulated uncertainties somewhere but it does not seem so, since the gradient is exactly equal at iteration 20...) I'll check what's happening

Did you check if this improves the results on the doc example?
Overall i think not updating the impostors was problematic and not consistent with the specifications of the algorithm. We can probably improve the efficiency later but i am for merging this now (if the tests pass)

Yes, it improves the result, but this time at the condition to not set the init (i.e. not set it to 'random', as before). Setting to random barely changes wrt the original image. I'll remove it in this PR. Here is the result:

CI tests are green we can merge when we're ready

Let's merge this and maybe if needed later we can make changes


Auto spacing now working (AngularJS v1.6.5)

Does not leave a space when you type. and place holder problem available. Error visual present in address
photouploads.com/images/269b61.png

any new about ?


local stratum 10 and manual in chrony.conf - why?

We should not rely on local time and I am not sure why "manual" is in the template.

@Martin-Weiss Thanks! These two lines are being dropped by #311


[Editor] Make the focused stamp annotation more clear from a screen reader point of view (bug 1911994)

It has been tested with Voice Over (mac) and with NVDA (windows).
When an added stamp annotation is focused, the screen reader will announce that it's a figure containing a graphic with the added alt-text.

/botio integrationtest

/botio integrationtest

/botio integrationtest

/botio integrationtest


Can't upgrade from Beta 10 to the latest version of IONIC2

Currently, I am running my app in Beta 10 which is fully written in JavaScript.
So far, it's working fine. I've tried to upgrade to the latest version of IONIC2, but I don't have any clue so far.
I was not able to find any documentation of upgrade from Beta 10 to the latest release, especially in JS.
Can you please help me on that?

The ionic team switched to 100% typescript focus a few versions back
I also started working in JS and then converted to TS format when that was announced, it's a bit of a pain but really not that hard.  The easiest way I found was to start a new project and then merge in my old pages / providers one at a time updating each as I went.  Took a day for a reasonably large app.
I then had to go through a do a similar task again for the migration to RC0 because of the large changes there.
So you're lucky in a way because if you start a new project now it will already be on RC1 and you can run through a 1 time migration to get everything over into Typescript AND onto the latest RC release after which there shouldn't be further huge breaking changes.
It's the price of working with beta software I guess.  I was also worried about the ts vs js thing at first but the typing and ahead of time compiling, compile time error catching is really handy.

@ghenry22 Thanks for your comment, the issue I am having is that the app I am working on it right now, is a pretty large app that took almost 5 months to build, knowing that I am the only developer. Learning TypeScript, and converting from JS to TS seems to me like climbing the Everest mountain. I have 0 knowledge in TypeScript, and I really don't have time to invest to learn a new language. I believe that there should be a way to update to the latest release and keep JS, but I really don't have an idea on how to do so.

@HamzaLJ I also had never touched typescript before but it is just javascript with some decorations (or decorators!) don't think of it as a whole new language.  I also ported a large app that I had been working on for several months as a sole developer and it only took a day.  Use the ionic conference app for reference or just a clean new starter project and it's pretty easy.
Since typescript is the only supported option going forward with ionic2 I would recommend putting in the time as it's going to get harder and harder to maintain otherwise.  Also as I mentioned there was a big step between beta and RC which basically required you to port your app into a new starter project anyway for the easiest migration so at least you are doing it once where I had to do it twice!
Check this out:
http://www.joshmorony.com/converting-ecmascript-6-to-typescript-in-ionic-2/
Very useful guide showing the bare minimum you need to do to convert from es6 js to ts with an ionic2 project and then showing you a couple of steps beyond the bare minimum that you can tackle later if you want to.

@ghenry22 thanks again, I believe I would take the way and convert my project from JS to TS.
Just a quick question before, do I need to upgrade from Beta 10 to Beta 11, then from Beta 11 to RC0 or I can upgrade from Beta 10 to the latest RC directly?

If it was me I go directly to the latest RC (RC1).  just update your ionic commandline tools, start a new project.  Use the built in generator to create the base templates for all your pages / components / providers etc then follow the guide I posted cutting and pasting your content from the old project to the new one and adjusting each file one at a time.  After the first couple it becomes pretty obvious and fast.
Also make sure to read through the change logs for Beta 11, RC0 and RC1 before and as you go as there are breaking changes in a number of areas like naming of lifecycle events, how alert / actionsheet etc controllers work and various others.  None hard to deal with just be aware though.

@ghenry22 Thanks a ton!
By the way, when I was developing in JS, many errors where not shown in the browser. In case of an error, it shows a blank page.
I've heard that typeScript shows errors, etc.. Is that right?

typescript will catch a lot of errors at compile time rather than relying on you to figure them out after a build which can be very useful.
Otherwise once it's running it's basically just javascript so debugging with console / xcode etc is the same as usual.

Hi! You may create new project of 2.0.0-RC0 and transfer your app code from 2.0.0-beta10 to new app.

Hello all! Thanks for helping @HamzaLJ out! I just want to add a note that beta to rc update instructions can be found here in our changelog. The only thing you would do different would be to install rc1 instead of rc0.


Update css file name from ooni.org

Fixes ooni/backend#440
@hellais For the missing fonts problem, the best solution is to configure CORS policy on ooni.org

Also, this dependency on the CSS filename is not a good idea. There should be a more auto


Explicit 'send bug report' button

For scenarios where you can't rageshake or rageshake isn't working, please can we have an explicit send bug report button

Done


Use project relative paths in finder window

Hey,
so great to see your plugin becoming better and better! :rocket:
I recognized that in the window with all the references etc using the lsp_finder function, all paths are relative to the users home directory. At least for me this is the case. And for me this sometimes end up with really long paths. Which make the window huge and "bad" to read. What would you think about making them relative to the projects root? I'm not sure if it is possible to get the root as detected by the LSP server. But probably it would be fine to set them relative to NeoVims current directory as well. Not that powerful, but better then relative to $HOME. Wouldn't it? :thinking:

Now I had used the lsp root dir or home dir . but some file path still too long.
https://github.com/glepnir/lspsaga.nvim/blob/b01607b22b02c80c004bc2ba8b94263b0a453a04/lua/lspsaga/provider.lua#L58-L63

Now I had used the lsp root dir or home dir . but some file path still too long.
https://github.com/glepnir/lspsaga.nvim/blob/b01607b22b02c80c004bc2ba8b94263b0a453a04/lua/lspsaga/provider.lua#L58-L63

Hmm. I just did an update and are locally now on b01607b which includes your references changes. But I still get the home relative path. When I open :LspInfo, the root of the language server is correct. For all of them (I use efm as general purpose language server for linting and formatting next to the "regular" servers). Any idea how I could debug this?

Hmm. I just did an update and are locally now on b01607b which includes your references changes. But I still get the home relative path. When I open :LspInfo, the root of the language server is correct. For all of them (I use efm as general purpose language server for linting and formatting next to the "regular" servers). Any idea how I could debug this?

can you post the min code and which server? now I am work with remake auto preview window.

can you post the min code and which server? now I am work with remake auto preview window.


updated movesets

Changed movesets according to New Update.
Not resolving #4323 since it contains useful info until dev is merged into master.

Did you get all of these (from someone's diff):
Here is the complete list of what changed:
Jigglypuff play rough > dazzling dream
Digglet & Dugtrio mud shot > mud slap
graveler & golem mud shot > mud slap
Grimer acid > poising jab
muck acid > lick
Gengar: sludge wave > sludge bomb
Hitmonlee stomp > brick break
Koffing & Weezing removed acid
chansey psybeam > hyperbeam
staryu quick attack > tackle
gyarados removed: dragon breath
porygon quick attack > zen headbut
Omastar rock throw > mud shot
Mew: removed: moonblast hurricane > blizzard

miss the 1st one.

@mjmadsen Yes. Also, there is a move missing in your list:
Starmie: Psybeam > Psychic

@MZorzy It's there, please check the complete file if you may.

https://github.com/PokemonGoF/PokemonGo-Bot/pull/4338/commits/9e2bce21d9c0c258831304a238e77a8f5e933bf0
Not see dazzling dream


Can the project be taken to Google summer of code 2021 as organization

Hello to people maintaining the project, I would like to contribute to this amazing hardware project and I was wondering if this project can be taken to google summer of code 2021, the organization application openings start from February I believe, please do consider my request.

@pawan-nirpal-031
Yes, you can take this project to the google summer of code 2021.
You can use this project as you would any other open source project licensed under the permissive Apache 2.0 license.
Let us know if there are any other details you need clarified.

@pawan-nirpal-031
Yes, you can take this project to the google summer of code 2021.
You can use this project as you would any other open source project licensed under the permissive Apache 2.0 license.
Let us know if there are any other details you need clarified.


visible_messages fix

Haven’t tested yet, but otherwise it looks good to me.
Will merge if/when I have time after Easter.

Sorry about the slow response.
I just tested, and on my main inbox, where 50 emails are shown, I get this response:

That is 75 emails are returned, instead of the 50 I expected. That sounds like too much to me, right?

Disregard the previous (now deleted) message. I tested api.get.visible_emails(), not api.dom.visible_messages().
As far as I can tell the code works properly, so consider it merged :smile:


Innovation - Primitives

Code.org work:

Primitives notes + hacks
Bash notes + hacks + tool checks
Example of some notes about college board
Categories to organize notes for this class and other topics

2.7+

thorough primitives program
extra bash checks
good productive posts on collegeboard
extra code.org


ARROW-18232: [Release][macOS][wheel] Disable GCS/S3 tests on not available env

This is needless because ARROW-17487 / #14499 removed this block.


Update channels.csv

Description

This PR updates the SBS channel information in the channel database, correcting existing data and enhancing details such as the logo, website, and broadcast categories.

Related issue

Edit SBS channel information #14425

@ProPontifex,
I’ve updated the code based on the feedback provided earlier regarding issue #14343. Could you please review the changes when you have time? Let me know if there are any additional adjustments needed. Thank you!

Image link is broken, I believe it's "i.imgur.com", not "imgur.com"

이미지 링크가 끊어졌습니다. "imgur.com"이 아니라 "i.imgur.com"인 것 같습니다.

Thank you for your feedback, I've done the modification!


chore: update translations for it locale

Summary
This updates translations for the it locale
Testing
👀

Hi @LRocc!
You've previously been responsible for updating it translations.
Would you mind updating the translations in this pull request by either:

Adding suggestions for each translation in this pull request. click here for more information on adding suggestions.
Updating the attached CSV and attaching it to the pull request

it-locale-update-Dec2023.csv


Unexpected processing order of received messages

First of all: I guess we have no bug here, but a behavior which might need some documentation (if not existing yet).
Consider the following case:
A client subscribes to a topic and calls a function. The result of the function is awaited.
Now the server first publishes something on the topic and instantly afterward returns the result of the function call.
What happens now on the client side is that first the subscription handler is fired (synchronously I guess) and then once the future is resolved the function call result is processed.
The behavior can be easily simulated:
Client:
async def onJoin(self, details):
    await self.subscribe(self.handle_change, 'changed')

    all_changes_future = self.call('all_changes')
    await self.call('make_change', 'a change')

    all_changes = await all_changes_future

    print('all_changes: ', all_changes)

def handle_change(self, change):
    logging.info('change# %s', change)

Server
@wamp.register('make_change')
def make_change(self, the_change):
    print('make_change')
    self.all_changes.append(the_change)

    self.publish('changed', the_change)

    return the_change

@wamp.register('all_changes')
def all_changes(self):
    print('all_changes')
    return self.all_changes

Complete example code can be found here: https://gist.github.com/aberres/0c5b356190991b1d0204bbf5ca399e05
The server will print

all_changes
make_change

while we see

change:  a change
all_changes:  ['a change']

on the client side.
I'd say technically this behavior is correct. It might be unexpected for a developer though.
When could this be a problem?
I noticed this in practice when I have a function to retrieve the current state of some objects and send around any changes as delta.
Now there is a possibility for a race the moment the client registers.
The complete state might not have been handled yet while a subscription is already processed.
I can solve this problem by adding sequence numbers to all sent packages. I can then process the received deltas with a higher sequence number once the complete state is read.

I think at least theoretically I might run into this issue as well when using wamp functionality:
Consider the case where you want to track registered clients.
When starting up you might have a function like this:
    async def query_already_registered_workers(self) -> None:
        registrations = await self.session.call('wamp.registration.list')

        for registration_id in registrations['exact']:
            details = await self.session.call('wamp.registration.get', registration_id)

            self.register_worker(registration_id, details)

and to track gone clients you do
    @wamp.subscribe('wamp.registration.on_delete')
    def unregister_worker(self, session_id, registration_id):
        # remove worker from internal datasctructure
        pass

What happens now if while await self.session.call('wamp.registration.list') is still pending while a worker is unregistered and the change is notified?
Then I have exactly the problem described above. First unregister_worker is called and then the complete list is handled. The worker is still considered to be alive.
Am I misusing the API here?

If you just ran the example code as given, why do you have 2 things in the "all_changes" list?
Anyway, you could just always publish the latest state and use the "history" feature so that new clients will always get the last published state. If your state is really too big to do that, then yes you'll have to do "something" to deal with the possibility of a race between "ask for the current state" and "get some changes". That is, you can't know if another client has called "make_change" between when you asked for something and when you get the answer. In general you'll want to subscribe first, then ask for the current state but be prepared to throw away some changes (because they're on earlier versions of the state than you got in your answer).
You can do "acknowledged" publishes, but that just acks that the router received the publish. There is no way to get acks from each subscriber.
For your second comment, you're not mis-using the API per se, but you can control exactly when you subscribe to on_delete so you could choose to do that only after you've gotten your answer for the list. There's still a possible race there, though: while the router is processing wamp.registration.list a registration could be deleted for some reason after your answer is in-flight but before you subscribe to on_delete...Again, the right answer is to subscribe first but be prepared to get called before all your other async "setup" (.list, multiple .get calls) finishes.

If you just ran the example code as given, why do you have 2 things in the "all_changes" list?

Sorry, had executed receiver.py two times.

In general you'll want to subscribe first, then ask for the current state but be prepared to throw away some changes (because they're on earlier versions of the state than you got in your answer).

Yeap, this is how I would expect things to work. But now comes the tricky part this whole issue is about:
One also needs to handle the case where a change is processed (not received) before the complete state is processed.
The problem is that the processing order does not match the order of packages in the wire.

One more thing:
As one cannot throw away all messages arrived before processing the current state I see problems with the wamp.registration API.
In my app, I added a "message sequence number" which is increased for every package sent. Clients can then drop all packages with a lower sequence number. This is not possible with the given API though.


Display going nuts

Describe the issue
A clear and concise description of what the issue is. BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.
Configuration

UTM Version: 2.0.28
OS Version: 11.3.1
Intel or Apple Silicon?  Sillicon

Crash log
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to Crash Reports, and find the latest entry for either QEMU, QEMUHelper, or qemu-*. Right click and choose Reveal in Finder. Attach the report here.
Debug log
For all issues, including crashes, you should attach a debug log. Open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.    It doesn't crash. it just freezes and never crashes
Upload VM
(Optional) If possible, upload the config.plist inside the .utm. If you do not have this, you can upload the entire .utm but note this contains your personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

Could you please update your issue with a detailed, concise description of the problem? Just a title of "Display going nuts" without any context is not helpful. Thanks!

ent

and

dfk;

Duplicate of #2569


Add a script to observe the API during Redis migration

Fixes

Addresses WordPress/openverse-infrastructure#611 by @AetherUnbound
Description

This PR adds a script to monitor the API during the Redis migration. This script

counts response status codes (ideally we are looking for all 200s, some 424s but zero 429s)
checks for response times from the stats endpoint that will no longer be cached

The PR also

updates the Dockerfile to build on top of grafana/k6 image using a multistage build like the API
matches the code style of the API Dockerfile
unifies the name of the access token to be ACCESS_TOKEN everywhere

Testing Instructions

Sign up for a test account on the staging API, verify email (or look in HelpScout for my existing test account credentials) and exchange the client ID and secret for an access token.

Export the ACCESS_TOKEN env var with the token value.

Run the observation script
$ cd utilities/load_testing/
$ just k6 observation.js

Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[X] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[X] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@dhruvkb Can you explain the goal of this approach compared to using CloudWatch to monitor this? What does this give us in place of CloudWatch?
Just trying to understand to make sure the monitoring we do during the deployment matches the expectations and needs we're aiming for.

The reasons for this (in addition to Cloudwatch, not a replacement) were

the flexibility of scripting

to monitor the response status code for individual endpoints
to parse the response JSON and tally custom metrics from that

ability to observe the metrics which Cloudwatch provides but from the perspective of the end-user, so this factors the effect of networking and the Cloudflare cache

Cloudwatch does not always reflect the experience of the end-user so this just makes sure that during the migration the end user's experience is not adversely affected.


ENH: Add Enumeration states to XTCE parser

Change Summary
Overview
This adds the ability to include derived enumeration states from the "States" tab in the spreadsheets.
Testing
Manual testing with SWE's packet definition. Unfortunately it looks like we don't have any tests for this utility and it is a pain to mock up the spreadsheets. This should be an action item to do in the future though.
closes #782

Unfortunately it looks like we don't have any tests for this utility and it is a pain to mock up the spreadsheets. This should be an action item to do in the future though.

Of course, I totally missed that we had an Excel sheet and expected output in the test_data folder! 🐑
I've changed from that Excel sheet to a dynamically generated Excel file instead as I suggested initially. The expected output file has a minimal diff with the new enumeration updates.

@bourque , I am pinging you to see if you agree with updating/changing the tests here now.
Codecov is now 100% for this diff.


SCP-2375: Kwxm/rescale ledger costs

This rescales costs as seen by the ledger by a factor of ~10^6~ 10^3, shifting them into ~microseconds~ nanoesconds.  For the validation benchmarks reported here that gives cpu costs roughly in the range 500,000 - 4,000,000 (microseconds gives 500-4,000 which is maybe a bit too coarse). We could divide by another 10 or 100 to get smaller numbers but that might get a bit confusing when trying to compare costs with times.

Pre-submit checklist:

Branch

[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages
[x] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

I think I'll merge this soon.  I think we should keep separate ScaleUp and ScaleDown operations because the former preserves information but the latter can lose it.  I've added a note about this and also a check which calls error if an attempt is made to scale costs by a factor that isn't strictly positive.

See also SCP-2399 for an issue about making this more type safe.

I think I'll merge this soon.

Fine, I won't fight you about rational scaling (although I still think it's better :) ).


[stable/minio] Add subpath for /export volume

Conditionally adds the subPath for the /export volume mount.
Works only if persistence.enabled is true and persistence.subPath
is not empty string.
This is handy in cases where the volume plugin doesn't
support sub folder mounting. GlusterFS plugin, for example doesn't support
it whereas NFS actually does.

Could it be just me that's running in to this? I've seen other charts implement it.

Any way for me to get this moving forward? @viglesiasce

/ok-to-test

Thanks @Rio!

merci beaucoup ^_^


[WIP] Use newly created abandoned checkouts route from core

The admin/abandoned_checkouts route is now available on core.
Hence, there is no need to specify the element_name, as we can use the default one.
Depends on https://github.com/Shopify/shopify/pull/198172 .

@manumilou is this tied to a particular version of the admin API? I noticed in our docs for abandoned checkouts the path still shows as checkouts rather than abandoned_checkouts.

@nwtn I jumped the gun a little bit when creating this PR. The new path is available but not used. I would like the new path to be bundled with the 2019-07 version. We should wait for it before shipping this.

@manumilou are you still interested in shipping this?


IAM roles support for the S3 Client

If the passed in authenticationInfo is null, use the AWS SDK provided
provider chain that covers IAM roles, ECS container roles, etc. instead
of passing the null as credentials. Passing null as credentials
shortcuts the provider chain and puts the client in an anonymous mode.
Instead, we now always go through the provider chain which, if it can't
find any credentials in the chain, throws an exception (instead of
anonymous mode).
This commit is for #18. The implementation is similar in intent to the suggested code of: aws-maven but uses the AWS DefaultAWSCredentialsProviderChain instead of a custom provider chain. The advantage is that the DefaultAWSCredentialsProviderChain seems to be getting longer in later versions of the Amazon SDK (the newest one seems to be the EC2ContainerCredentialsProviderWrapper) and so using the default may help stay in sync as new methods get added. In both this implementation and the one from aws-maven, an error is thrown if credentials can't be found which may make this be considered a breaking change.

Awesome, thanks! Will look at getting a release out shortly.


Allow passing SSL Cert/Key when using HTTPS

What problem does this feature solve?
Allows users to utilize custom SSL certs for HTTPS.
In some cases, it might be necessary to use an SSL certificate for local development.
Moreover, these options are accepted for both webpack-dev-server and the newer webpack-serve:

https://webpack.js.org/configuration/dev-server/#devserver-https
https://github.com/webpack-contrib/webpack-serve#cli

I think it makes sense to expose these options to users.
Other CLIs have accepted similar PRs:

https://github.com/pallets/flask/pull/2606

What does the proposed API look like?
The addition of --key, --cert and potentially --cacert to vue-cli-service serve.
These values would be optional when --https is used, but in order to use --key and --cert, --https would be required. Or we could infer --https from the presence of a cert/key.

You should be able to specify these options in vue.config.js, in the devServer property:
https://github.com/vuejs/vue-cli/blob/dev/docs/config.md
So just that I understand:

Did you try this and it didn't work?
or did you not know about it?
or did it work, but you want these to be available as CLI arguments as well?

 I actually didn't know I could override it there, but it makes sense.
I could argue these should be CLI arguments as well. I think those were my expectations having worked with other similar CLIs. Seeing https as a possible argument but not seeing the others made me think they weren't exposed.
This is fine though. You can close this if you feel that overriding via config is sufficient.

It works via config. I don't think this is necessary anymore. Thanks for pointing it out!

I'm trying to do exactly this, and added the stuff called for to vue.config.js:
const fs = require('fs');

module.exports = {
  devServer: {
    https: {
      key: fs.readFileSync('./certs/server.key'),
      cert: fs.readFileSync('./certs/server.crt'),
      ca: fs.readFileSync('./certs/ca.crt'),
    },
  },
};

and I still get an invalid SSL cert (unrecognzied CA) when I run
vue-cli-service serve --mode development --https --port 8001 from npm
Using @vue/cli-service 3.4.1

OK - nevermind. I figured out what was wrong. Passing --https to vue-cli-service serve appears to OVERRWRITE the https element of devServer (probably with true). That's a bit of guesswork/inference, but what is clear, is that eliminating the --https parameter to vue-cli-service serve fixed my problem, and caused vue-cli-serve to properly use the provided certs.

I am not able to import the fs module. It is throwing an error
ERROR  Error loading vue.config.js:
ERROR  SyntaxError: Cannot use import statement outside a module
My vue.config.js looks like this. Please help
const fs = require('fs');

module.exports = {
  devServer: {
    https: {
      key: fs.readFileSync('./ssl/server.key'),
      cert: fs.readFileSync('./ssl/server.crt'),
      ca: fs.readFileSync('./ssl/ca.crt'),
    },
  },
};

Hm sorry to bump this but webpack document suggests :
module.exports = {
  //...
  devServer: {
    https: true,
    key: fs.readFileSync('/path/to/server.key'),
    cert: fs.readFileSync('/path/to/server.crt'),
    ca: fs.readFileSync('/path/to/ca.pem'),
  }
};


use left to switch slide view instead of transform

@zhouyu11 I'm gonna close this issue as there is no context regarding the actual issue solved.
Note that the transform property is supposed to provide better performance

my scenario : I want to fixed a alert dialog to the html body , but we have
used the transform3d in swipview container style,
but *'transform'  *will renew the coordinate system , so the alert dialog
will fixed to swipeable-view container.
[image: Inline image 1]
So I change it to this
On Thu, Aug 18, 2016 at 4:35 PM, Olivier Tassinari<EMAIL_ADDRESS>
wrote:

@zhouyu11 https://github.com/zhouyu11 I'm gonna close this issue as
there is no context regarding the actual issue solved.
Note that the transform property is supposed to provide better performance
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/oliviertassinari/react-swipeable-views/pull/125#issuecomment-240659182,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJYw-ZNMb8p4XmlQlMcfvhNq1HpD0i_Bks5qhBljgaJpZM4JgJJF
.

--
Yu Zhou
Developer
Email<EMAIL_ADDRESS>Telephone +86 1 <+86+18200277051>7090072590
[image: ThoughtWorks]
http://www.thoughtworks.com/?utm_campaign=yu-zhou-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator

Oh right, so the related issue is #125.


Accrescent unable to update itself if originally installed from outside Accrescent

I have downloaded Accrescent 0.20.0 from GitHub releases using Obtainium. Now that Accrescent 0.21.0 has been released, Accrescent is unable to update itself, as it can see that it was installed from a different source. The button which would usually allow to update is greyed out with text reading "App installed from another source."

This is expected behavior as of 0.20.0, but an option should be added to make Accrescent take over as the installer of record

I understand that this is expected for apps installed using Accrescent (since 0.20.0), but the release notes (as far as I understand) make it sound like Accrescent should be able to take ownership of itself, and update itself (even when installed from a different source), but in my case, Accrescent is unable to update itself.
From the 0.20.0 release notes:
"Accrescent now respects other app stores and manual APK installations, no longer attempting to take over updates for apps you installed outside of Accrescent (one exception: Accrescent itself installed manually from an APK)."
Sorry if I'm misunderstanding.

I think there should be also an option for ability to take ownership for any of the listed apps.
If we clear Accrescent's data or reinstall it, all apps have to be uninstalled and installed to restore Accrescent's ownership.

I understand that this is expected for apps installed using Accrescent (since 0.20.0), but the release notes (as far as I understand) make it sound like Accrescent should be able to take ownership of itself, and update itself (even when installed from a different source), but in my case, Accrescent is unable to update itself.
From the 0.20.0 release notes: "Accrescent now respects other app stores and manual APK installations, no longer attempting to take over updates for apps you installed outside of Accrescent (one exception: Accrescent itself installed manually from an APK)."
Sorry if I'm misunderstanding.

I see how it's worded a little confusingly. It's supposed to mean that Accrescent won't attempt to update any app installed from somewhere other than Accrescent, including Accrescent itself if it was installed from e.g. Obtainium. The only exception is that Accrescent can update itself if it was originally installed from an APK.

I'm going to mark this as closed by https://github.com/accrescent/accrescent/commit/75f48437e363be84c93aad5bb604763cc4dec369 since it should allow Accrescent to update itself, but I've created https://github.com/accrescent/accrescent/issues/534 for the update takeover feature


Upstream Server(s)

The readme currently says:

The proxy requires a recursive DNS resolver, such as Knot, PowerDNS or Unbound.

Is it expected to remain this way?  I really like the idea of a single self-contained dependency-free executable that provides both DNSCrypt and DoH, but would not want the upstream connection to be provided or even suggested.  I personally like Unbound, but would like the continued freedom to change [or not change] that based on my own evaluation.  Does that make sense?

Yes, don't worry, it will remain that way.
The only change that can happen is the ability to use multiple upstream servers simultaneously.


referencing slot component predicate methods

I have a ToolbarComponent that renders a single RansackerComponent, and the RansackerComponent renders multiple FilterComponent slots. Here's a simplified version of the setup:
# toolbar_component.rb
class ToolbarComponent < ViewComponent::Base
  renders_one :ransacker, Ransack::RansackerComponent
end

# ransacker_component.rb
module Ransack
  class RansackerComponent < ViewComponent::Base
    renders_many :filters, ->(field:, select_options:, prompt:, checkbox: false) do
      Ransack::FilterComponent.new(
        field: field,
        ransack_param: param,
        ransack_form_id: id,
        select_options: select_options,
        prompt: prompt,
        checkbox: checkbox,
      )
    end
  end
end

In the view, the components are used like this:
# In views
<%= render ToolbarComponent.new do |toolbar| %>
  <% toolbar.with_ransacker(query: query, url: url) do |ransacker| %>
    <% ransacker.with_filter(field: field, select_options: []) %>
  <% end %>
<% end %>

And the ToolbarComponent template looks like this:
# toolbar_component.html.erb

<%= ransacker if ransacker? %>

<% if ransacker&.filters? %>

    <% ransacker.filters.each do |filter| %>
      <%= filter %>
    <% end %>

<% end %>

The ransacker component renders a ransack search form, and the rendering of the filters is delegated to be rendered within the toolbar component.
Problem
If I swap the order of the components (i.e., checking for ransacker.filters? before rendering ransacker), nothing gets rendered at all.
Questions

Is my usage of the components valid in this context?
Is it safe to call predicates on slots like ransacker&.filters? to check if the slot component has slot components?

Steps to reproduce
Expected behavior
The ToolbarComponent should conditionally render the RansackerComponent and its FilterComponent slots. When the order of checking and rendering components is swapped, the components should still be rendered correctly.
Actual behavior
When the order of checking for ransacker.filters? and rendering ransacker is swapped, nothing gets rendered at all. It seems that the conditional checks on slots like ransacker&.filters? might not be working as expected.
System configuration
Rails version: 7.0.4
Ruby version:  3.1.0
Gem version:   3.0.0
Any insights or recommendations would be greatly appreciated!

Hey @mosaaleb, thanks for opening an issue with us! I think this happens because the block passed to with_ransacker isn't called until the ransacker slot is rendered. I don't know if there's a way to figure this out so that we can raise or warn if folks try to access slots in advance of that, but it might be a good thing to add if we can.
This behaviour isn't obvious, but I think it could signal some changes you may want to make to your components.
Looking at this, I would expect that this code indicates the hierarchy of components here:
<%= render ToolbarComponent.new do |toolbar| %>
  <% toolbar.with_ransacker(query: query, url: url) do |ransacker| %>
    <% ransacker.with_filter(field: field, select_options: []) %>
  <% end %>
<% end %>

That is, I'd expect the template for ToolbarComponent to render RansackerComponent, and I'd expect the template for RansackerComponent to be rendering FilterComponents. In this code:
# toolbar_component.html.erb

<%= ransacker if ransacker? %>

<% if ransacker&.filters? %>

    <% ransacker.filters.each do |filter| %>
      <%= filter %>
    <% end %>

<% end %>

...ToolbarComponent is reaching down into the RansackerComponent's FilterComponents to render them. So I would first consider the structure of these components – if ToolbarComponent needs to do something based on the filters, perhaps consider passing them into it as data and then using said data in a lambda slot, e.g.:
# ToolbarComponent.new([{ field: field, select_options: []}, {...}])
class ToolbarComponent < ApplicationComponent
  def initialize(filters)
    @filters = filters
  end

  renders_one :ransacker, lambda do |**kwargs|
    RansackerComponent.new(**kwargs)
      .tap do |c|
        @filters.each { |filter_args| c.with_filter(**filter_args) }
      end
    end
  end
end

@mosaaleb does the above work for you or is it still an issue


added use case for issue #2685

#2685

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1c275fc). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2793   +/-   ##
=========================================
  Coverage          ?   80.14%
  Complexity        ?     7109
=========================================
  Files             ?      145
  Lines             ?    26783
  Branches          ?     6401
=========================================
  Hits              ?    21466
  Misses            ?     3479
  Partials          ?     1838

Continue to review full report at Codecov.

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


DOM elements not displayed correctly, during protractor test

Hi there!
I test an Angular application with protractor and since today the DOM-elements are not displayed correctly during the testing. I am using it on macOS.
What I tried to solve the problem is:

uninstall protractor and reinstall
uninstall webdriver-manager and reinstall
remove all node_modules and did yarn install again
Tried to find another person who has the same problem

Here is a screenshot:
Screenshot
Another thing is, the tests are green and in the DOM everything is okay, but debugging is a bit difficult, when you don't see anything.
Thanks in advance for your help.
Bug report

Node Version: v6.11.3
Protractor Version: 5.2.2
Angular Version: 2.4.0
Browser(s): Chrome
Operating System and Version MacOS Sierra 10.12.6 (16G1314)

I could solve the problem with downgrading the Chrome version. Chrome updated itself to chrome version 67 and afterwards it did not work.
After installing chrome version 66 it works as it should. But maybe this issue help others with the same issue.


High RAM usage for istio-proxy

Hey,
The bump to 1.0.1 has significantly improved my boot times, yay, but I'm noticing a little higher memory footprint for the sidecars, they're all circa 220meg(ish) on our preprod cluster:
Numbers:

VirtualServices: 45
ServiceEntry: 14
Services: 76
Pods: 214

Adding 250ish meg of ram to the memory footprint of every pod, some of which only use around 500meg themselves is quite a bit of an overhead.
Interestingly, they're significantly less in dev (which has less apps on it, thus less services), so there appears to be a correlation:
Numbers:

VirtualServices: 22
ServiceEntry: 14
Services: 52
Pods: 139

OK I've done some more digging in the dev cluster and it appears correlation =/= causation, I've found some istio-proxy pods on the less utilised cluster also using 2.5x the RAM of others:

What I have noticed is all the istio-proxies that are using more ram, have some event at different times in their history where ram usage really jumped:

I've attached the log from the second sreenshots istio-proxy, which i must add is quite spammy with cluster reloads and grpc disconnections?
istio-proxy.log

cc @PiotrSikora LCTrie mem optimizations don't seem to help.

@Stono compared to https://github.com/istio/istio/issues/7912 and my experiments, those numbers look awfully high for the number of services in your clusters. How many CPUs are on the host systems running those containers? Could you run those commands for me?
$ kubectl exec -it <pod> -c istio-proxy -- grep -c ^processor /proc/cpuinfo
$ kubectl exec -it <pod> -c istio-proxy -- pgrep -w envoy | wc -l
There are 2 major sources of high RAM usage in the proxy:

Per cluster/service overhead (~80% of which is allocated for stats), which is currently proportional to number of services in the cluster,
Per worker thread overhead for each cluster/service, which makes 1. even worse.

By default, proxy will start worker thread for each CPU on the host system, which means that the more powerful machine you're using, the more RAM proxy is going to consume by default.
If you're not processing thousands of requests per second, then you might try to lower the number of worker threads to something more reasonable, even 1 or 2, using the global.proxy.concurrency setting, i.e.:
helm install install/kubernetes/helm/istio --name istio --namespace istio-system --set global.proxy.concurrency=1

Unfortunately, the change didn't make into 1.0.1 release, so you'd need to use daily from 20180828 or newer to play with it now.

❯ kubectl exec -it $pod -c istio-proxy -- grep -c ^processor /proc/cpuinfo
12

❯ kubectl exec -it $pod -c istio-proxy -- pgrep -w envoy | wc -l
      30

I can't unfortunately use daily releases on these systems.
I'm confused however that istio-proxy would be creating threads per cpu on the host, rather than looking at the cgroup allocation for that pod?
Nodes are by nature multi tenant, based on our size of node for us we get this sort of setup:
❯ k get pods --all-namespaces -o wide | grep gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
conference-application       conference-application-6b754b56c8-4jkrm                    2/2       Running   0          6h        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
consumer-platform            consumer-platform-5c78cd6bc9-js86x                         2/2       Running   0          2d        <IP_ADDRESS>     gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
core-system                  prometheus-node-exporter-v68sm                             1/1       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
core-system                  weave-scope-agent-brmhq                                    1/1       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
data-platform                alertmanager-0                                             2/2       Running   0          5d        <IP_ADDRESS>     gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
data-platform                cloudwatch-billing-exporter-5b698f9dbc-g9vcn               1/1       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
kube-system                  calico-node-4hzlh                                          2/2       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
kube-system                  calico-typha-horizontal-autoscaler-5545fbd5d6-9qgrq        1/1       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
kube-system                  filebeat-preprod-gtrww                                     1/1       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
kube-system                  ip-masq-agent-s594r                                        1/1       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
kube-system                  kube-dns-788979dc8f-29scp                                  4/4       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
kube-system                  kube-proxy-gke-delivery-platform-cpu1ram2-f11b16a5-nkfb    1/1       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
kube-system                  metrics-server-v0.2.1-7486f5bd67-clfm5                     2/2       Running   0          5d        <IP_ADDRESS>     gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
location-service-soap        location-service-soap-56f7dd754f-5glkh                     2/2       Running   0          23h       <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
private-advert-service       private-advert-service-57d7c6f859-w5pm8                    2/2       Running   0          1h        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
sauron-web-partners          sauron-web-partners-5659987d69-62cpj                       2/2       Running   0          49m       <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
sauron-web                   sauron-web-549884d69b-2gq5k                                2/2       Running   0          40m       <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
search-solr                  zoonavigator-6874bcc68b-5qg8j                              1/1       Running   0          5d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
search-solr                  zoonavigator-api-f6cb74f4d-w4rq9                           1/1       Running   0          5d        <IP_ADDRESS>     gke-delivery-platform-cpu1ram2-f11b16a5-nkfb
vehicle-metric-service       vehicle-metric-service-6f5df59fdb-w2ps8                    2/2       Running   0          1d        <IP_ADDRESS>    gke-delivery-platform-cpu1ram2-f11b16a5-nkfb

7 of these apps have istio sidecars, so that's 7 processes creating 12 threads?

@stono, you can update the sidecar-injector config map and add

—concurrency
“1”

And then restart a pod to be reinjected.

Will give it a go today @mandarjog - ta

Rolling out concurrency=1 seems to have significantly reduced our memory use.

This does feel like a mitigation though, i would still question having proxy default threads === cores on node, imagine someone was running 64 core nodes, with 32 apps (thus 32 proxies) on there, it'd be pretty catastrophic :)
Feels like it'd be more sensible to set a fixed, lower limit and then document how to tweak under high throughput?

@Stono great, thanks for testing!
Yes, I totally agree that we should have 1 or 2 proxy threads by default, at least for the sidecar, otherwise we're stealing resources away from the workload. Adding global.proxy.concurrency (and soon annotations for it) was just prerequisite to dialing it down.

can global.proxy.concurrency be modified after installation ?
i'm having this same issue but would prefer not to reinstall

The default now is 2.
You can update global.proxy.concurrency, rerender the template.
Most of the changes should be no-op, so it is not a reinstall.


144 prefilled answers structure

PR Related to #144

You need to change the PrefilledAnswersController in Admin to only list prefilled answers with null structures

You need to change the PrefilledAnswersController in Admin to only list prefilled answers with null structures

Done


Added ingressClassName parameter in ingress chart

IngressClassName is a new parameter in ingress chart.

@sanhidalgoo thank you - can you increment the chart minor version please?

also, can you add documentation to the chart README?

@ameijer Of course! I just to add de docs and I changed the minor version.


Update LocalKMeans.scala

Proposed Change
After picking each new initial centers, it's unnecessary to compute the distances between all the points and the old ones.
Instead this change keep the distance between all the points and their closest centers, and compare to the distance of them with the new center then update them.
Test result
I test the KMeans++ method for a small dataset with 16k points, and the whole KMeans|| with a large one with 240k points.
The data has 4096 features and I tunes K from 100 to 500.
The test environment was on my 4 machine cluster, I also tested a 3M points data on a larger cluster with 25 machines and got similar results, which I would not draw the detail curve. The result of the first two exps are shown below
Local KMeans++ test:
Dataset:4m_ini_center
Data_size:16234
Dimension:4096
Lloyd's Iteration = 10
The y-axis is time in sec, the x-axis is tuning the K.

On a larger dataset
An improve show in the graph but not commit in this file: In this experiment I also have an improvement for calculation in normalization data (the distance is convert to the cosine distance). As if the data is normalized into (0,1), one improvement in the original vesion for util.MLUtils.fastSauaredDistance would have no effect (the precisionBound 2.0 * EPSILON * sumSquaredNorm / (normDiff * normDiff + EPSILON) will never less then precision in this case). Therefore I design an early terminal method when comparing two distance (used for findClosest). But I don't include this improve in this file, you may only refer to the curves without "normalize" for comparing the results.
Dataset:4k24
Data_size:243960
Dimension:4096
Normlize 	Enlarge 	Initialize 	Lloyd's_Iteration
NO    	1 	         3 	          5
YES 	        10000 	 3 	          5
Notice: the normlized data is enlarged to ensure precision
The cost time: x-for value of K, y-for time in sec

SE for unnormalized data between two version, to ensure the correctness

Here is the SE between normalized data just for reference, it's also correct.

Can one of the admins verify this patch?

@mouendless please read https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark  There are a number of things wrong with the PR and code

FYI, it would be great if you run ./dev/run_tests first and then follow https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark, https://cwiki.apache.org/confluence/display/SPARK/Spark+Code+Style+Guide and https://github.com/databricks/scala-style-guide/blob/master/README.md.

@srowen @HyukjinKwon , Thx and Sry I failed to removed clearly the test parts of my code. And I'm reading the guide and testing the code

I am careful of saying this but personally I would suggest to close this first and then follow the guides from scratch.

@HyukjinKwon Thx and this really is my first contribution, I will follow ur suggest

@mouendless Thank you for bearing with me.


Documentation: Small Spelling Mistake in Domain Models

Small spelling mistake in the documentation in the section Use Canonic Primary Keys

For example they can turn this recommendation of using canonic primary keys into a project-wide policy by usins base types and aspects as follows:

Admittedly not world changing, but caught my eye..

Thanks for reporting this. We will fix this today :).

Issues was fixed weeks ago, see https://cap.cloud.sap/docs/guides/domain-models#use-canonic-primary-keys. Issue can be closed @gregorwolf.


[v9rc3] Bug: v8 packages install but fail when visiting package Dashboard pages

Exceptions in various v8 packages I've successfully installed in v9rc3. The error log screen doesn't say what initially caused it or where or in which file. It's simply this:

Are you sure you are using v9rc3? In your image we see it's the rc2...

Yes, I'm using rc3, just updated a few hours ago. The image is a week old from rc2. But the bug is still there.

How can we replicate the error?

Install a Project Skeleton package:
https://github.com/linuxoid/ab_project_skeleton
and visit the Project Skeleton page in Dashboard

The problem is that you have a dashboard page controller that overrides the on_start method of the core dashboard page controller:

core: https://github.com/concrete5/concrete5/blob/9.0.0RC3/concrete/src/Page/Controller/DashboardPageController.php#L83
your package: https://github.com/linuxoid/ab_project_skeleton/blob/9a9f761d4f472007663144c04403619a4b5dbda8/controllers/single_page/dashboard/package_skeleton.php#L38

So, the on_start method of the core controller isn't called.
you have to change your on_start method so that the core method is called - this way:
    public function on_start()
    {
        parent::on_start();
        $this->set('app', $this->app);
    }

Ok, thank you. But that all worked in v8.

Yep, with v9 the on_before_render method requires that the core on_start method is called.
Generally speaking, when you override a core method it's better to also call the overridden method (calling parent::methodName();).

Is that also required in a PackageController? It throws an error there:
Call to undefined method Concrete\Core\Package\Package::on_start()

If there's a core method you are overriding, then call it.
If it doesn't exist, obviously don't call it.

Whilst I agree with the fix for on_start', there is still something fundamentally wrong with a 'whoops' display that crops the line for the error it is purporting to show off the top of the screen. The purpose of the right pane on the whoops is to show the error. It should do that irrespective of how close the code causing the error is to being correct.


Fix samples redirect, and remove old sshd from TOC

The /samples/wordpress/ location collided with an old redirect to the official images, so removed the redirect
Removed the sshd example from the table and TOC, as the example   was removed, and now pointing to an alternative examples. The   page is kept for people that may have bookmarked it, but no  need to include it in the navigation.

@StefanScherer @usha-mandya ptal


How to declare an external package?

This is the case in the ordinary case:
BeginPackage["xxx`",{"JLink`"}]
Begin["`xxx`"]

JavaNew["..."]

End[]
EndPackage[]

Now with the Loader.m, no longer needed write BeginPackage.
But also can't specify Contexts, so I must write:
Begin["`xxx`"]

JLink`JavaNew["..."]

End[]

Is there any way to add JLink to all sub-packages?

You can avoid the Begin statements by using a subfolder for subcontexts. This is how BTools manages its context names. The folder name will automatically be used as the context name and all the symbols declared publicly in it will still be exposed to the rest of the package. You can add other contexts to the context path used by the package via the function PackageExtendContextPath which you can see in use here: https://github.com/b3m2a1/mathematica-PublicPacletServer/blob/master/Packages/Main.m

cool

I can't understand this: https://github.com/b3m2a1/mathematica-BTools/issues/10#issuecomment-419332475
fun11::usage="doc11"
fun12::usage="doc12"
fun21::usage="doc2"

Begin[`subpkg1`]
fun11="do something"
fun12="do something"
End[]
Begin[`subpkg2`]
fun21="do something"
End[]

Which equal to
- Packages\
    - subpkg1\
        - fun11.m
        - fun12.m
    - subpkg2\fun21.m
    - main.m

Now in main.m
fun11::usage="doc11"
fun12::usage="doc12"
fun21::usage="doc2"

Now nothing will happen when I call fun11.

Is this possible?

@GalAster I think the issue you're hitting is that you actually want to declare fun11::usage="doc11" in fun11.m. The autoloader finds all symbols declared before a Begin block in every package file it can and puts all the contexts it builds onto a special context path that's used whenever a file is loaded. This way every symbol knows about every other symbol, but they can be declared in the same place they're defined.
A good example for this is what I do in this subcontext of BTools. Each file in that directory inherits the "BTools`Paclets`" context, but each symbol is declared only in the package it's defined in (although this package will not load until the symbol is used). If you drill deeper into the directory structure a similar thing occurs there. E.g. all the symbols declared before the Begin here have the context "BTools`Paclets`DocGen`" but they're still visible to the rest of the package.


feat(#52): unknown-rt lint back

as requested in https://github.com/objectionary/lints/pull/86#issuecomment-2515012218

@yegor256 unknown-rt lint is back :)

@h1alexbel thanks!


add documentation and ops guide to guidelines

Are there further changes pending here or we can merge.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This has been open for far quite long without progress. Please, move on with it or close it.

This has been open for far quite long without progress. Please, move on with it or close it.

can be merged, should I

can be merged, should I

CLA assistant seems not to work. See an empty page

CLA assistant seems not to work. See an empty page

CLA assistant seems not to work. See an empty page

@msohn

CLA assistant seems not to work. See an empty page

@msohn


During installation, python swirl.py setup sometimes hangs after message "Collecting Statics:"

Pressing ENTER produces an error message.

Workaround:
python manage.py collectstatic

Fixed by https://github.com/sidprobstein/swirl-search/commit/67c57390da69bbadb7235668b34a309ab9a07e86

swirl.py will be further revised to handle this case


Document proximity sensor code

The proximity sensor code is confusing and seems like magic without context:
// This method returns whether the proximity sensor reads within
// the proximity threshold.
bool ProximityActivated() {
  digitalWrite(pinProximityTrigger, LOW);
  delay(2);
  digitalWrite(pinProximityTrigger, HIGH);
  delay(10);
  digitalWrite(pinProximityTrigger, LOW);

  unsigned long distance = pulseIn(pinProximityEcho, HIGH);
  // Divided by 2 because the sound travels twice the distance
  // Speed of sound is 343m/sec = 0.0343cm/μs = [1/29.1] cm/μs
  distance = (distance/2) / 29;
  //Serial.println(distance);
  return distance < thresholdProximity;
}

The reason for doing this to detect the proximity of an object should be explained.

Working on this using the branch proximity-documentation.

Implemented in above-referenced pull request.


How to get a list of destinations

I may be missing something obvious, but while using pdf.js with the included pdfviewer.js I can't find where the list of destinations is.
I know it must exist, but for the life of me I can't find it.
I need to present a "TOC" that contains existing anchors inside the PDF file. Could you point me in the right direction? With a file loaded in the viewer, where can I get the existing list of anchors without having to generate it each time?

I though so as well, but I couldn't make it work. Then I tried with pdfDocument.getDestinations() but that didn't work either.
I know I'm missing something but I can't find what it is.

In test/unit/api_spec.js we have unit tests for both, so they should work in the way indicated above. Otherwise, please provide a runnable version of your code on e.g., JSBin or JSFiddle so we can take a look, but without that there is not much more we can do.


Cannot install via pip due to protoc not found (caused by substrait)

  error: failed to run custom build command for `substrait v0.4.0`

  Caused by:
    process didn't exit successfully: `/private/var/folders/rx/8kr6cmjx6f52xx6b8p_vkdv40000gn/T/pip-install-myehnazd/raysql_52859e2a502a40079f1c38502fa9483c/target/release/build/substrait-542ab9f5b4afdffb/build-script-build` (exit status: 101)
    --- stdout
    cargo:rerun-if-env-changed=FORCE_REBUILD
    cargo:rerun-if-changed=substrait/text/simple_extensions_schema.yaml
    cargo:rerun-if-changed=substrait/proto/substrait/capabilities.proto
    cargo:rerun-if-changed=substrait/proto/substrait/algebra.proto
    cargo:rerun-if-changed=substrait/proto/substrait/function.proto
    cargo:rerun-if-changed=substrait/proto/substrait/plan.proto
    cargo:rerun-if-changed=substrait/proto/substrait/extensions/extensions.proto
    cargo:rerun-if-changed=substrait/proto/substrait/type_expressions.proto
    cargo:rerun-if-changed=substrait/proto/substrait/type.proto
    cargo:rerun-if-changed=substrait/proto/substrait/parameterized_types.proto

    --- stderr
    thread 'main' panicked at 'Could not find `protoc` installation and this build crate cannot proceed without
        this knowledge. If `protoc` is installed and this crate had trouble finding
        it, you can set the `PROTOC` environment variable with the specific path to your
        installed `protoc` binary.You could try running `brew install protobuf` or downloading it from https://github.com/protocolbuffers/protobuf/releases

workaround is to install protoc per the instructions given in the error message


Error in package.json deploying Angular2 app on Azure using bitbucket

I am facing a issue deploying angular2 app on azure. I get an error on following line
"engines":{"node":"6.2.1"},
Here is the snapshot

I have given this version as WEBSITE_NODE_DEFAULT_VERSION has the value 6.2.1. Anyone having idea about this then please share.
package.json looks as follows:
{
  "name": "angular-quickstart",
  "version": "1.0.0",
  "engines":{"node":"6.2.1"},
  "description": "QuickStart package.json from the documentation, supplemented with testing support",
  "scripts": {
    "start": "tsc && concurrently \"tsc -w\" \"lite-server\" ",
    "docker-build": "docker build -t ng2-quickstart .",
    "docker": "npm run docker-build && docker run -it --rm -p 3000:3000 -p 3001:3001 ng2-quickstart",
    "pree2e": "npm run webdriver:update",
    "e2e": "tsc && concurrently \"http-server -s\" \"protractor protractor.config.js\" --kill-others --success first",
    "lint": "tslint ./app/**/*.ts -t verbose",
    "lite": "node_modules\\.bin\\lite-server",
    "postinstall": "typings install",
    "test": "tsc && concurrently \"tsc -w\" \"karma start karma.conf.js\"",
    "test-once": "tsc && karma start karma.conf.js --single-run",
    "tsc": "node_modules\\.bin\\tsc",
    "concurrently": "node_modules\\.bin\\concurrently",
    "tsc:w": "node_modules\\.bin\\tsc -w",
    "typings": "node_modules\\.bin\\typings",
    "webdriver:update": "webdriver-manager update"
  },
  "keywords": [],
  "author": "",
  "licenses": [
    {
      "type": "MIT",
      "url": "https://github.com/angular/angular.io/blob/master/LICENSE"
    }
  ],
  "dependencies": {
    "@angular/common": "~2.1.0",
    "@angular/compiler": "~2.1.0",
    "@angular/core": "~2.1.0",
    "@angular/forms": "~2.1.0",
    "@angular/http": "~2.1.0",
    "@angular/platform-browser": "~2.1.0",
    "@angular/platform-browser-dynamic": "~2.1.0",
    "@angular/router": "~3.1.0",
    "@angular/upgrade": "~2.1.0",

    "angular-in-memory-web-api": "~0.1.5",
    "bootstrap": "^3.3.7",
    "systemjs": "0.19.39",
    "core-js": "^2.4.1",
    "reflect-metadata": "^0.1.8",
    "rxjs": "5.0.0-beta.12",
    "zone.js": "^0.6.25",
    "concurrently": "^3.0.0",
    "lite-server": "^2.2.2",
    "typescript": "^2.0.3",
    "typings": "^1.4.0"
  },
  "devDependencies": {
    "concurrently": "^3.0.0",
    "lite-server": "^2.2.2",
    "typescript": "^2.0.3",
    "typings": "^1.4.0",

    "canonical-path": "0.0.2",
    "http-server": "^0.9.0",
    "tslint": "^3.15.1",
    "lodash": "^4.16.2",
    "jasmine-core": "~2.5.2",
    "karma": "^1.3.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-cli": "^1.0.1",
    "karma-htmlfile-reporter": "^0.3.4",
    "karma-jasmine": "^1.0.2",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "^3.3.0",
    "rimraf": "^2.5.4"
  },
  "repository": {}
}

Please suggest a solution.

Please include a sample repo as describe in this page.
Also, what is the error that you are getting? You only give the line of the error but not the actual error message.

Closing until we get repro app.

Sample repo: https://github.com/skendrot/angular2-test


childTypes don't seem to work

Running into the same issue as reported in #34 regarding aliases. The way the documentation reads (to me at least), I understand it to work as follows:
In base/parent model:
protected $childTypes = [
        'EbayListing' => App\Marketplaces\Ebay\EbayListing::class,
        'ShopifyListing' => App\Marketplaces\Shopify\ShopifyListing::class,
    ];

When I create a new EbayListing record and save it, I still get the fully qualified class name instead of just "EbayListing" as the value in the type column.
Using 0.7 ... any ideas? Thanks in advance! This is a terrific idea for a package, by the way :)

Also, I had to put a leading backslash in as well:
'EbayListing' => \App\Marketplaces\Ebay\EbayListing::class,

Ok, I did some further debugging and the issue was on my end (slaps forehead).
I had the namespace in my child class in the wrong case ('Marketplaces' != 'MarketPlaces') ... d'oh! Closing this out now :D


Fix RTX seq num ending up in main receive register

When we received blank padding packets on the RTX stream those would end up getting
registered in the receive register for the main stream. This would in
turn cause us to NACK packets that never existed in the main stream.
The relevant code looked like this:
let receipt = if is_repair {
    // Blank padding packets will have empty data.
    if !data.is_empty() { // 1
        // Rewrite the header, and removes the resent seq_no from the body.
        stream.un_rtx(&mut header, &mut data, pt);
    }

    // Now update the "main" register with the repaired packet info.
    // This gives us the extended sequence number of the main stream.
    //
    // We need to do this also for blank padding to schedule the "paused event".
    let receipt = stream.update(now, &header, clock_rate, false); // 2

    // Drop blank padding
    if data.is_empty() {
        return;
    }

    receipt
} else {
  // omitted
}

A blank padding packet with seq no X would skip the !data.is_empty()(1) branch and thus not have the sequence
number in the header rewritten. Then we would call
StreamRx::update with the unmodified sequencer number X, that of the RTX
stream and it would be registered as received in the ReceiveRegister for the main stream.

Looking at this a different solve strikes me:
diff --git a/src/session.rs b/src/session.rs
index 30a2fde..6774229 100644
--- a/src/session.rs
+++ b/src/session.rs
@@ -495,7 +495,7 @@ impl Session {
             // This gives us the extended sequence number of the main stream.
             //
             // We need to do this also for blank padding to schedule the "paused event".
-            let receipt = stream.update(now, &header, clock_rate, false);
+            let receipt = stream.update(now, &header, clock_rate, data.is_empty());

             // Drop blank padding
             if data.is_empty() {

However, this means we'll register the same SeqNo twice for each blank RTX packet, but I guess that's fine 🤔


Feature request: Telescope extension

I like to use both the quickfix window and telescope. I think that it would be cool if there was some sort of telescope extension that could be packaged with this plugin

Telescope integration would be cool, but should probably be implemented in a separate plugin. I’d rather not add and maintain support for another plugin that I don’t personally use

Alright, I'll look into creating something like this. I know that telescope already has a marks picker builtin, but it is the same output of the marks command. I've already got something I've started on a while back that was integrating this plugin with telescope. For me to create it as a plugin and publish it apart from my dotfiles repository, I'll need to do a little bit more to it and add configuration options.
The reason that I created this is because some other plugins (e.g., folke/todo-comments.nvim) provide both a quickfix and telescope version. I use both, but I understand. I'll close this and look into creating a plugin sometime fairly soon.

I'm reopening this issue because ideally the plugin would expose bookmark information in a more easily accessible way rather than requiring any telescope extension to plumb through require'marks'.bookmark_state.

This works for me with bookmarks:
vim.keymap.set('n', '<leader>b', '<cmd>BookmarksListAll<CR><cmd>lcl<CR><cmd>Telescope loclist<CR>', { silent = true })

I see the new #106 pull request that integrates telescope. Curious how it's any different.

Hi!
As stated by @chentoast I added methods allowing to simply return data from marks and bookmarks to be able to use it in the telescope plugin. (they could be useful for any new feature needing to get marks and bookmarks).
That's a nice workaround @insanum indeed. The advantage of the homemade telescope implementation is that we have to control over how infos are displayed in telescope.
For example, the telescope loclist display feels a bit messy to me:

While mine looks like this for buffer marks (since I don't need to see in what file are these marks):

And like this when looking for all project marks:

Moreover the file path will be showed based on user config.
Hope it makes sense.

Hello, any update?


Lifetime issues with <airup_sdk::nonblocking::Connection as airup_sdk::Connection>::invoke

It's hard to use the following pattern with current implementation due to lifetime issues:
async fn with_connection<T, F: Future<Output = Result<T, airup_sdk::ipc::Error>>>(
    &self,
    f: impl FnOnce(&mut Connection) -> F,
) {
    /* ... */
}

self.with_connection(|conn| conn.trigger_event(&event)).await;

The plan is:

When async keyword generics is added to Rust, current emulation is rewritten.
When related unstable features are stabilized, use unboxed futures to replace boxed ones.
Fix the issue.

Priority: Low.


FPGA board support

does this core support the Zedboard - FPGA? Thanks in advance

Hi Thach,
Steel was developed and tested on Xilinx FPGAs. Although it has not been tested on a Zedboard, I believe that there should be no problems when synthesizing Steel on this board - if you face any problem, you can open a new issue here so I can help you to solve it. ;)
Rafael.

@rafaelcalcada  Thank you, I started a new issue. I hope you can help me.

Great! I'm closing this issue :)