Pours drinks 2 times

The bartender pours one drink than finishes the progress but without any extra input it pours a second drink. It's not possible to do anything between those two processes. On some boots of the Pi it does only pour one at a time but that's gone on the next restart.

That wouldn't be a problem. Could you explain me what to do exectly? That would be a huge help

No problem. I used this guide when I originally programmed it. You'll want to make the changes so the button is similar to the button on pin #24 (we implemented the ones on 23/17 in our code).
http://raspi.tv/2013/how-to-use-interrupts-with-python-on-the-raspberry-pi-and-rpi-gpio-part-3

Thanks, I will try that.

Changed the selection Button to an rising edge detection but when I tried it the Oled was Converted, so everything black was white and vice verca. Also it detected the button push but it fell into a loop, not only was it doing it two times as before but it didn't want to stop. Now gone back to original code and wiring and somehow the Oled is still converted...

I also didn't install the LED strip, don't know if thats connected to this?

Weird. Sounds like the OLED library might be conflicting with the button pins somehow. I would try either switching the pins for the buttons or commenting out all calls to the OLED screen (menu prints in the terminal).

I deconnected the grounded pins of the buttons and strangly he randomly started to pour a drink right now. Is that even possible?

It's possible. Sounds like your buttons are misconfigured.

OK, I didn't used excectly the same ones as you but also momentary switches so I thoght that would be alright or are there diferences which could cause these problem?

How am I able to adapt the interrupts for my buttons?

Take a look at that link I sent. They can trigger on either high or low, but make sure they're wired like that guide depending on what you do.
Also try using different GPIO pins for the buttons and commenting out calls that turn on the screen.

Changed the GPIO pins, after rebooting everything worked fine but when I took the Pi from the power ( not letting him shut down - that shouldn't cause this right?) the same pattern started again. Wondering why it worked and then suddenly not anymore.

Also commented out everything that turned on the sreen but after that he didn't recognise any button push anymore.

Changed both buttons so they are connected to 3.3V and changed the code. First when I got only the select button connected everything worked fine even after multiple restarts but after I connected the second one it's in its loop again, without ending but when I deconnected the one again it didn't stop to loop. Even when I got all deconnected it starts randomly pouring drinks one after one. Last time I changed the buttons to trigger on high I connected them to the 3.3V pin of the disply, this time I took the one of the relais and the display worked fine.

When I now press to pour a drink it gets into a loop without where it also randomly switches drinks between each pour. Don't understand the part in the code where the event detection for the pins is stopped, wouldn't that cause problems detecting button presses? Really need help over here.

So after testing and researching I foundation out that there's a problem with the gpio pins detecting false Inputs with momentary switch buttons which leads them into a state of floating and therefore not beeing able to correctly detect the input gut rather detect multiple ones. After changing the code in a way that it doesn't recognise these false inputs I manage to get it to work so that it only pours one at a time but now I got the problem that after some pours the system doesn't recognise any inputs anymore where could be the problem that something like that happens? I will add a link to the changed code.

The link to the Raspberry forum where I also stated my problem:
https://www.raspberrypi.org/forums/viewtopic.php?f=37&t=214560&p=1320522#p1320522

I can't make sense of this at all but when I decreased the milliliter amount of what the pumps draw from 100+ down to 50, the system does not pour multiple drinks.

Do u mean the flowrate or the actual amount for the drink? Because I already put the amount down and that didn't change anything.

The actual amount for a drink. It was 150 oj, 50 vodka. I decreased oj to 50 and it only poured once. I repeated 3 times for other drinks. As soon as I bumped it back to 150ml it doubled or tripled up on drinks again

I already had amounts below that and for me it sadly din't change anything...

I decided to start over and reinstall Raspbian. Right out of the box, it made one drink. As soon as I edited the pump_config.json file and added 2 more pumps it went back to the multiple pours again. Thinking this might be the case I saved the original pump_config file and reloaded it. Everything worked fine again. Since my OLED screen is still not working I'm watching the drink selection in the terminal. Something I noticed was as soon as the drink was done being made it would list the drink again about 2 seconds later, and then a 3rd time but the bartender still only made one drink.
I went back to the pumps_config file and only edited the liquid: pump 1= vodka, pump 2=rum (the order I prefer to have it). I ran the Bartender.py as normal and after the drink was done it triplicated the name of the drink again but this time it did make a second drink... and third... and then I rebooted.
Back to square one, I deleted the new pumps_config file, reloaded old one, ran another gin&tonic and almost the same thing happened. After the drink was made, 2 seconds later, it listed the drink in the terminal again, 2 seconds later it listed it a third time but this time it listed Configure and then Pump 1.
I was about to say there is something in the coding that doesn't like the pumps_config file messed with but when this new issue happened, it's basically telling us there are random firings of buttons.
Ugh! Only if I had a way to make an alcoholic beverage to lessen the tension I am feeling from the build process of this technological paperweight. :-D

That's the same I'm experiencing. The second drink you see in the terminal is just the display showing the drinks after it has finished making a drink but after that it starts randomly receiving button presses. I already tried manually debouncing and avoiding the problem of a floating condition of the pin which would cause this problem. Sadly no effect could even be seen. Also changed the buttons but the same again. The problem - for me - also only happens right after the drink has finished, so it's not completly random but rather somehow connetected to the sript, because I already changed the code in such a way that it changes the pins for the buttons into an output during the time of pouring so it shouldn't even be able to receive any new inputs but right at the moment the mode of the pins change back into inputs it missfires again... I can only think that after the sript for pouring a drink has finshed there's something in the code, which influences the script that it thinks there are still presses left to process.
The amount of alcohol I drunk since I started building it is probably more I will ever make with this bartender xD

Just an interesting note: I actually edited the bartender.py file to accept commands over ssh for the left and right buttons (just to make testing stuff easier), which called self.menuContext.advance() or self.menuContext.select() on a keystroke.  Even operating it with that interface, it would still sometimes pour 2 drinks in a row, which leads me to think it's not an issue with the hardware button bounce times.

I make no claims to being a competent developer, but I had a crack anyway :p

Just tested your code and until know it seems to be working! Can't be completly sure but this weekend it's going to be tested throughout ;D

Finally sat down with the Bartender, removed the original Smart-Bartender folder. Then cloned https://github.com/Danzibob/Smart-Bartender
I then cloned https://github.com/BLavery/lib_oled96
Then the following happened:
~/Smart-Bartender $ sudo python bartender.py
Traceback (most recent call last):
File "bartender.py", line 10, in
from lib_oled96 import ssd1306
ImportError: No module named lib_oled96
I copied the contents from the lib_oled96 folder directly into the Smart-Bartender folder and got then the following happened:
~/Smart-Bartender $ sudo python bartender.py
Traceback (most recent call last):
File "bartender.py", line 14, in
I2CBUS = SMBus(1)
IOError: [Errno 2] No such file or directory
What am I doing wrong?

Have you installed smbus using pip?

I am operating with a 3Bb. My apologies, I could have sworn I had the i2C functionality already enabled through raspi-config. I am feeling quite annoyed that what seemingly should be simple is now getting complicated. After I took care of the i2c functionality I now get this message when running the bartender.py:
~/Smart-Bartender $ sudo python bartender.py
Traceback (most recent call last):
File "bartender.py", line 297, in
bartender = Bartender()
File "bartender.py", line 52, in init
self.led = ssd1306(I2CBUS) # Change rows & cols values depending on your display dimensions.
File "/home/pi/Smart-Bartender/lib_oled96.py", line 54, in init
const.DISPLAYON)
File "/home/pi/Smart-Bartender/lib_oled96.py", line 63, in _command
self.bus.write_i2c_block_data(self.addr, self.cmd_mode, list(cmd))
IOError: [Errno 121] Remote I/O error
To confirm: the lib_OLED96 folder should be in the Smart-Bartender directory as its own directory?

Just tested it again with a drink with all 6 pumps pouring and suddenly I get the same problems as before... Also the program crashes after some pours because of a segmentation fault... I just changed the original code with the doubledrink fix would there be anything different? I don't use the i2c display so couldn't use your code.

Well the Problem of multiple pours seems to only happen one time and not anymore but I'm still getting that segmentation fault, not everytime but for some drinks it happens and for some not...

Hello, I am not a developer nor do I know python, surely it is not the correct solution but it worked for me, putting prints in the code, I see this ...
LEFT_BTN pressed
long Island
Finished processing left button press
The above is ok, but when I pressed the right button ...
RIGHT_BTN pressed
Rum & Coke
After about 5/6 seconds this again ...
Rum & Coke
Finished processing right button press
And there was the second drink without touching anything, the phantom drink! :)
It caught my attention that the right button did not finish processing, so I try this ...
def run (self):
self.startInterrupts ()
main loop
try:
while True:
time.sleep (0.1)
except KeyboardInterrupt:
GPIO.cleanup () # clean up GPIO on CTRL + C exit
GPIO.cleanup () # clean up GPIO on normal exit
self.stopInterrupts () # 15ago
Since there was the self.startInterrupts () but not the stop, it worked for me, surely the bug, if there is one, for me it is in menu.py and in MenuItemClicked, but as I said, I am not a developer.
In short, add this line, self.stopInterrupts () # 15ago, and they no longer occur, maybe this is masking the real problem but this is how it works for me.
Also add a 100k resistor to positive so that the gpio is not in the air, but it did not work either, well, then they tell me.
Greetings from Argentina. (Sorry for my English)
Max


Integrating in a existing app

First take a look at the following

https://github.com/jeremykenedy/laravel-roles#opening-an-issue
https://github.com/jeremykenedy/laravel-roles/issues?q=is%3Aissue+is%3Aclosed

Please describe what you are needing help with below:
I have a fully functional invoicing management laravel 8 app. It has users and authentication system, but does not have permissions. Can I use laravel-roles to add this functionality to my existing app?

yes


Use separate headers instead of binary flags in the xhr sandbox (close #122)

\сс @inikulin @miherlosev

\r-

FPR

\r-

FPR

\r- Overall looks good, just a single minor issue.

FPR

lgtm

lgtm


Test coverage: Auth/

@benbrown - Since you took on Auth, I assume you are handling the test coverage around it too?


Can't run from file:///

Opening your OpenSeadragon HTML file with file:/// instead of off of a local web server causes the tile paths to be wrong. If you try https://github.com/CanOfBees/osd-test in that way, you'll see errors like:
Tile 8/0_1 failed to load: file:///example-images/sanborn_knoxville1884_0001_files/8/0_1.png
Note that the path it's looking for is at the root of my hard drive, whereas it really should be the folder I ran from (in my case file:///Users/iangilman/projects/openseadragon/pulls/canofbees-osd-test/osd.html).
At first I thought this was due to #70, but I'm not so sure anymore.

This has been fixed.

Good catch!


cleanup and refactoring

just some suggestions, check if you like (some of) them

Already merged with other PR


VPCS does not save default name

Hi
I use vpcs 0.6.2
I put on GNS3 a VPCS device : his default name is "VPCS-1"
I start it
His name is : VPCS-1
On OS : cat projects/untitled/project-files/vpcs/794eb714-30c7-41eb-b711-b4f33c91ee21/startup.vpc
set pcname VPCS-1
I save his config : save
On OS : cat projects/untitled/project-files/vpcs/794eb714-30c7-41eb-b711-b4f33c91ee21/startup.vpc
The file is empty
If i restart this device, his name is "VPCS"

Fixed by https://github.com/GNS3/vpcs/pull/12


Introduce --endpoint-url option

I want to use it with S3 compatible storage, so I added the --endpoint-url option.
I tested in さくらのクラウド オブジェクトストレージ.

Thank you!

I've just released v1.0.3 and it will be available soon!
https://github.com/hirose31/s3surfer/releases


Add exceptions to UseConsistentWhitespace rule

Ignore open braces in invocation of magic method. For example, ignore the open brace in (1..5).foreach{$_}.
Ignore range operator. For example, do not flag the .. in 1..5.

Resolves PowerShell/PowerShellEditorServices#380

Thanks @daviwil


MicroBitUtilityService - replaces PR 178

A fresh branch from current master.
Replaces https://github.com/lancaster-university/codal-microbit-v2/pull/178
TODO: How should the service and characteristic UUIDs determined?
This currently uses the micro:bit base UUID plus 1 and 2.
TODO: MICROBIT_ID_UTILITY - ID definitions have moved into codal-core
MicroBitUtilityService.h/cpp - BLE service providing replies to simple client requests
MicroBitUtilityTypes.h - Details of the service requests that support reading MicroBitLog data
MicroBitCompat.h - Define MICROBIT_ID_UTILITY for service events
MicroBitConfig.h - Macros to control creation in pairing / application mode, default pairing mode only.
MicroBit.cpp - Create service according to config macros. To create in BLEManager::init would need to pass MicroBitLog.
MicroBitBLEChar.cpp - Changed DMESGF to DMESG.

@finneyj I tested it now, using https://github.com/martinwork/microbit-v2-samples/tree/test-mydata.
I had to modify MicroBit.cpp for the panic 071 problem. Would you like me to add a commit for that here? Make a separate PR?

Generally looks good to me @martinwork! Thanks for the contribution!
I do think we should keep this aligned with the USB based mailbox implementation we drafted for reading the log in due course - just so that we can keep and consistent API for both USB and BLE based transactions. This is already pretty close though, and seeing as we don't want to hold this up any longer, I suggest we tackle that down the line - perhaps by aligning the USB implementation with your BLE one here...

Thanks for checking it @finneyj

I'm happy to merge then @martinwork - thanks for the work and quick responses. Unless you have any further thoughts @JohnVidler?


Add menu swaps for pyramid plunder start-minigame and quick-leave

This pull request Closes #7138 #7401.
As opposed to other PRs this one closes both issues with a single config and I wrote the code such that it checks the mummy such that if other NPCs exist/are added with a start-minigame option this code will not have to change.

Enabling both swaps with one option is not optimal. Pyramid plunder is done in a lot of ways. Some people rush first room and some go all the way to the last room. There's a huge risk of accidently clicking quick-leave.

If having both swaps enabled is a problem it should probably be fixed with a drop down menu like many of the other menu swapper configurations. Splitting up the plug in options into 2 entry's would take up too much space and would be diffrent than the other existing elements of the plug in. Ill push a new commit as soon as I have the time, maybe today or tomorrow.

added in 5344cd6ddbd0e435bad7a088dbc266738319a5fc


fleetctl: support truthy values in boolean unit options

Support truthy values in boolean unit options(true, yes, on, 1, t).
Originally written by @wuqixuan
Supersedes https://github.com/coreos/fleet/pull/1271
Fixes: https://github.com/coreos/fleet/issues/1108

LGTM

Done.

Added a new unit test TestUnitIsTruthy.
Renamed astr to s.

Merged https://github.com/coreos/fleet/pull/1574/. Thanks.


phpmd.org website is down ?

Description
It looks like the phpmd website does no longer exists website, don't know if it's a github issue, or a repository issue (can't find the documentation repository)
I have 404 page:

Checks before submitting

[x] Be sure that there isn't already an issue about this. See: Issues list
[x] Be sure that there isn't already a pull request about this. See: Pull requests
[x] Tell if you have the possibility to create a Pull Request to solve this issue.
[x] If possible add a URL to the incorrect website page or documentation file.
[x] This issue is about 1 documentation or website issue and nothing more.

I suppose is due to Github Actins pipeline (even if it worked)

I suppose is due to Github Actins pipeline (even if it worked)

Very likely, it's due to the CNAME deletion that happened in the GitHub Action:
https://github.com/phpmd/phpmd/runs/1664216748#step:9:127

Very likely, it's due to the CNAME deletion that happened in the GitHub Action:
https://github.com/phpmd/phpmd/runs/1664216748#step:9:127

Website is back

Website is back


[VOTO] Updated API documentation to stable

Added

Configuration endpoint
Config images endpoint
Metric endpoint
Custom Mail request

Removed

Theming endpoint

Some spelling mistakes


Redundant with xorg-libpthread-stubs

Whoops. While working on providing the whole set of X.org client libraries with conda-forge, I didn't manage to discover that this package had already been created. The relatively new xorg-libpthread-stubs package is redundant with this one.
I'm biased but I'd recommend keeping xorg-libpthread-stubs and deprecating this one. That package is built on all three platforms, whereas this one is provided for Linux only. It also has a recipe and build scripts that are consistent with the rest of the X.org packages I've been working on.
I think this package is only used as a dependency of the Qt 5 package ... does anyone know if that's correct or not?

That's correct. I don't have a problem with deprecating this package since you're in charge of it now.
@ocefpaf, @jakirkham, what do you say?

My opinion is that we are trying to get towards increased binary compatibility and renaming packages works in the opposite direction.

Compatibility between conda-forge and defaults you mean?

Myself and @ocepaf have spoke of trying to make things more compatible when possible. Qt5 from defaults was rebuilt with more recent jpeng and libpng libraries built by @ilanschnell. ICU is next on the list. If the concensus is that defaults needs to rename libxcb then so be it but in general I think new builds should try not to rename things without good reason.

I see, then @pkgw I'm -1 on removing this feedstock.

Ray, I agree. Let us take the shortest path towards compatibility. What
side has fewer packages to fix? I  believe it is conda-forge, if so let's
keep defaults' names.
I am not familiar with the packages in question. But I'll try to put a list
together so discuss this and reach a consensus quickly and move forward.
On Jan 28, 2017 7:04 PM, "Ray Donnelly"<EMAIL_ADDRESS>wrote:
Myself and @ocepaf have spoke of trying to make things more compatible when
possible. Qt5 from defaults was rebuilt with more recent jpeng and libpng
libraries built by @ilanschnell https://github.com/ilanschnell. ICU is
next on the list. If the concensus is that defaults needs to rename libxcb
then so be it but in general I think new builds should try not to rename
things without good reason.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/pthread-stubs-feedstock/issues/3#issuecomment-275877969,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6BL00C9qlAuXVZDLcF8fERdp72ylZGks5rW7trgaJpZM4LwncR
.

BTW this was my mistake for not paying attention when reviewing and merging
Peter's PRs. Sorry Peter.
On Jan 28, 2017 7:20 PM, "Filipe Pires Alvarenga Fernandes" <
<EMAIL_ADDRESS>wrote:
Ray, I agree. Let us take the shortest path towards compatibility. What
side has fewer packages to fix? I  believe it is conda-forge, if so let's
keep defaults' names.
I am not familiar with the packages in question. But I'll try to put a list
together so discuss this and reach a consensus quickly and move forward.
On Jan 28, 2017 7:04 PM, "Ray Donnelly"<EMAIL_ADDRESS>wrote:
Myself and @ocepaf have spoke of trying to make things more compatible when
possible. Qt5 from defaults was rebuilt with more recent jpeng and libpng
libraries built by @ilanschnell https://github.com/ilanschnell. ICU is
next on the list. If the concensus is that defaults needs to rename libxcb
then so be it but in general I think new builds should try not to rename
things without good reason.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/pthread-stubs-feedstock/issues/3#issuecomment-275877969,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6BL00C9qlAuXVZDLcF8fERdp72ylZGks5rW7trgaJpZM4LwncR
.

It wouldn't be hard to switch things to remove the "xorg-" prefix from the packages that have already been added to conda-forge. I guess I'd like to keep the prefix for packages not already in defaults, but I don't feel especially strongly about that.

I like the prefix for ones that are not already there and conda is learning about deprecation too so if we keep the unprefixed ones for now, hopefully down the line we can deprecate them.

@pkgw, so what's the plan now? Remove the packages you added?

I guess the thing to do would be (1) import my build scripts as PRs to the existing packages, since they add support for more platforms, etc.; (2) apply the rename in dependent packages; (3) remove the xorg- prefixed packages.

Good plan! please go ahead with it then.
I'm closing this one as the issue is solved now.


DCA and schematic REST API: D&T AWS deployment test

Add benchmarking, like shinyloadtest, for multiple DCA instances access 1-2 schematic instances

Let's prioritize the case where multiple DCA instances access one schematic instance: stress testing and benchmarking the schematic REST API performance with multiple concurrent requests.

how DCA can be configured to access different schematic instances

This^ can wait - we likely won't need support for this case, at least for a while.

@afwillia Will work with DPE and IT to access D&T AWS account

Update: schematic is running on an EC2 instance and DCA + dashboard works


Added the feature to auto comment on pull request being raised

Related Issue
Fixes #744
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

There have some issues check it once

There have some issues check it once

I have checked it and I don't think there are any issues. Can you please specify what issue you faced?

Do Git pull and then commit all your code and push them. Then recreate new PR.

Do Git pull and then commit all your code and push them. Then recreate new PR.

This issue simply involves adding a file in the .github directory to add the necessary workflow. Git pull is not necessary for this issue. Could you please merge this pr and add the labels for gssoc.


luci-mod-status: Adding scroll buttons on syslog and kernellog status pages

My log files can grow rather big, typically if i look at the log files then i want to look at the bottom, not the top, so I was missing a scroll down button.
So I added these:

Please let me know if you have any comments or suggestions.

Might I suggest Tail and Head, especially for those who might already be
familiar with those utilities that do exactly these things.

@systemcrash yes i use that, but sometimes I want to just check the log from my phone, then i have to scroll all the way down... Anyway if you think this is not a good addition then fine, just reject this PR, i will just use it on my own openwrt installs, just thought it might be useful for somebody else as well. Not sure though why we would not want to make the LuCi logfile page more useful... Or do you mean I can use tail from LuCi? Please tell me how.

do you mean I can use tail from LuCi? Please tell me how.

Example of reversing log.
https://forum.openwrt.org/t/status-system-log-new-text-should-be-at-the-top-not-bottom/151740/4

@systemcrash Which package is that in?

The button style looks wrong

@jow- if you can show me an example what button style you would like, then I can adjust it, np. I just put in the most simple button i could find

@jow- Like this perhaps:

I just tested this, and it seems to work fine. Can you put a bit more padding between scroll to head button and the log field?

@systemcrash I encapsulated the bottom button now in a div and added 20px padding below the button.  The padding between the button and the logfile itself is in the 'textarea' already, so i cannot really remove it. I can also add paddint to the top button either at above and/or below the button.  Just a matter of what the preference is i suppose

@systemcrash I encapsulated the bottom button now in a div and added 20px padding below the button. The padding between the button and the logfile itself is in the 'textarea' already, so i cannot really remove it. I can also add paddint to the top button either at above and/or below the button. Just a matter of what the preference is i suppose

Below the botton at the top, so it's not adjoining the log field

Ah you didnt mean the scroll to head button, but the scroll to tail button. Something like this?

and

Exactly so

ok cool.

Please rebase onto current master.

Please rebase onto current master.

done

Thank you, nicely done :)

And thank you for the review and the suggestions :)


List of countries (Component)

You need to include the changes on dev branch with git pull origin dev to solve the conflicts.


Medium Icon on Mobile Gets Cut off

Not sure what the best approach would be here for mobile. There isn't a lot of space for the extra icons


Should Get-VMwareTools return the very latest version?

The VMware Tools mapping file https://packages.vmware.com/tools/versions lists versions that are not included in an ESXi build. Should Get-VMwareTools return very latest version (11.1.0 in the example below) or the latest version that is bundled with an ESXi build (11.0.5 in the example)?
Client Server      Version Build
------ ------      ------- -----
11296  esx/0.0     11.1.0
11270  esx/0.0     11.0.6
11269  esx/6.7p02  11.0.5  16075168

Or add a property "Included" with true/false that whoever wants to download VMware tools can choose. Sometimes you may want a newer release if this solves an issue.
And/or maybe introduce a Property "-All" for all Get- cmdlets to list all available versions/architecture/etc available, not only latest version.


[QUESTION] How to separate permissions to pull / push containers?

Can you help to implement restricted access to docker registry - some users can only pull, other - only push containers?

I think this isn't the right place for this kind of functionality.
This should be handled by the registry itself. This is more like a secured gate to connect to the registry


OCIS ignores OCIS_INSECURE=false Environment variable

Describe the bug
I want to setup OCIS with Caddy reverse proxy.
I initialized OCIS with OCIS_INSECURE=false to disable self signed certificates as document said , while OCIS wtill use https://xxx.xxx:9200 with self signed certificates.
Steps to reproduce
Steps to reproduce the behavior:

init ocis config
podman run --rm -it \
    --mount type=bind,source=/mnt/pool/srv/owncloud_config/,target=/etc/ocis \
    owncloud/ocis init

with certificate checking disabled yes
Do you want to configure Infinite Scale with certificate checking disabled?
 This is not recommended for public instances! [yes | no = default]

run ocis with OCIS_INSECURE=false
podman run \
    --label "io.containers.autoupdate=registry" \
    --name ocis \
    --rm \
    -p 9200:9200 \
    --mount type=bind,source=/mnt/pool/srv/owncloud_config/,target=/etc/ocis \
    --mount type=bind,source=/mnt/pool/srv/owncloud_data/,target=/var/lib/ocis \
    -e PROXY_HTTP_ADDR=<IP_ADDRESS>:9200 \
    -e OCIS_INSECURE=false \
    -e OCIS_URL=https://oc.example.caddy \
    owncloud/ocis:latest

Caddyfile
*.example.caddy {
    encode gzip
    tls { xxxxxxxx }
    @oc host oc.example.caddy
    handle @oc {
            reverse_proxy http://<IP_ADDRESS>:9200
    }
}

Expected behavior
OCIS should export :9200 as HTTP server but HTTPS when OCIS_INSECURE is set to false.
I can access OCIS in caddy https://oc.example.caddy
Actual behavior
https://oc.example.caddy shows Client sent an HTTP request to an HTTPS server.
if I change
reverse_proxy http://<IP_ADDRESS>:9200
to
reverse_proxy https://<IP_ADDRESS>:9200
OCIS server error with
2022/09/11 04:30:04 http: TLS handshake error from IP:42912: remote error: tls: bad certificate
Setup
Please describe how you started the server and provide a list of relevant environment variables or configuration files.

OCIS_INSECURE=false
PROXY_HTTP_ADDR=<IP_ADDRESS>:9200
OCIS_URL=https://oc.example.caddy

Additional context
When SSL CA is managed by reverse_proxy, OCIS should not use self signed CA to connect with reverse_proxy

Great! It works


set_word_prior be used with Correlated Topic Model?

I'm wondering if the set_word_prior function is compatible with the correlated topic model? My understanding of CTM is that the per document distribution is logistic normal and the per topic word distribution remains a Dirichlet, and in dynamic topic model the opposite is true (document distribution is Dirichlet, topic distribution is logistic normal).
For my research, I'm interested in the possibility of developing a correlated topic model where the topic distributions can also shift over time. Can the posterior topic distribution of CTM be used as the prior for a subsequent time window CTM like in the dynamic topic model? Thanks for the help/advice.

I just reread Blei and Lafferty's 2006 DTM paper, and wow... realized this was s silly question given that they also use the multinomial logistic in DTM. Since you developed your implementation of DTM on their methods, I'm just going to go ahead and close this now.

Hi @jmparelman,
Yes, it's possible that one model's posterior is used as another model's prior.
However, I'm not sure if this method can provide a unified view of the entire data.
Following this method, you will get separated models by time and each model is connected weakly to its previous-time model.
In this scheme, only a model at time t-1 can effect a model at time t, and not vice versa. And more importantly, it is impossible to optimize the whole set of models at time t_0 to t.
Thus, I think, you may build a new model, where topic correlation(CTM) and shift over time(DTM) is combined, to your research. But I don't know whether it is easy or difficult, and possible.


The setting 'editor.codeLens' cannot be overrided by 'csharp.referencesCodeLens.enabled' anymore

Environment data
dotnet --info output:
VS Code version: 1.81.0
C# Extension version: 2.0.328
Steps to reproduce

Set as below on Settings.json file:

"editor.codeLens": true,
"csharp.referencesCodeLens.enabled": false

Open an C# file, you'll then see "xxx references" everywhere now, which were not shown before.

The setting is no longer working for me too, the visual clutter is annoying.

This is a dupe of https://github.com/dotnet/vscode-csharp/issues/5809 and will be fixed in this weeks release.


chore: remove qemu

Description
Installing qemu failed for me in this job https://github.com/stackrox/stackrox/actions/runs/6027762599/job/16354089057?pr=7645
Let's remove it if it's not needed.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
CI
It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list.
It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only.
It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are
responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change
ASAP after it gets merged or explain in PR when the validation will be performed.
Explain here why you skipped testing in case you did so.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

I see that this works, but honestly I can't understand why. How does buildx get a power or z machine 🤔

So maybe it's not working but we do not have a check for Z?

Let's remove it if it's not needed.

How do you know that? Did you check that images are actually pushed for power and Z?

@stehessel Good point. We have no tests running on arm nor ppc. Let's close it for now until we have a way to verify that everything is working. Also we have qemu action in more places.

/test ibmcloudz-4-16-qa-e2e-tests

Closing in favour of

https://github.com/stackrox/stackrox/pull/12041


A command line (app) SignalR Client

I would like to see the example as a non web UI client.  I have been working for months to get a command line app that is the SignalR Client using Azure SignalR Service (ASRS). I have found nothing on step by step to scale with the ASRS. MS docs says to scale by adding App Service, by other documentation says that ASRS will scale for you. If adding App Services to Azure is needed then clients will need to open multiple and growing number of firewall rules to allow access to the ASRS and the Hubs.
Thanks you,
Robert Dean
<EMAIL_ADDRESS>
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 608c01ec-d21f-7bdf-a700-7288222ad27c
Version Independent ID: 94920b97-adc0-3899-f8bd-aff821f3435b
Content: Cross-platform Chat - Azure Solution Ideas
Content Source: docs/solution-ideas/articles/cross-platform-chat.yml
Service: architecture-center
Sub-service: solution-idea
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 442761

This article is going to be deleted and our team does not have any plans of adding additional SignalR content at this time, but thank you for the suggestion.
#please-close


Implement Audio Ops for Python Client

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Mac OS X 10.10.5
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.2.1
Python version: 3.5.2

There are some very useful audio operations defined in tensorflow/core/ops/audio_ops.cc. It would be great if python client users could access these by default.

@petewarden would know about any plans for the state of these operations and whether they can be made available in the Python API

@Abhipray @petewarden FYI I have recently begun work on this. There are a couple of outstanding tasks:

Add tests for the audio_ops.py
Add tests cases for multi-channel inputs.
Determine why AudioSpectrogramOp fails with Spectrogram size calculation failed for multi-channel inputs.

Ahh hm, so there's a reason that those ops don't have Python wrappers yet -- we don't actually want to make them public / supported yet. I'm sorry this decision wasn't better documented, but could you please hold off on this work?

Ah, that's a shame; may I inquire as to the reason why? Presumably the ops & kernels will remain in core, so it's safe to take a dependency on them in a saved model?

We are planning on making them public soon, I have a pending change that I hope to get in over the next couple of weeks.

Excellent, thanks.
In the mean while, I identified a small issue with the AudioSpectrogram op shape function; should I submit a PR for this, or leave it?

@petewarden @rryan Is the python wrapper for mfcc available in the 1.3 release of tensorflow ? Thanks

Trying the "Simple Audio Recognition", but get the " ImportError: cannot import name 'audio_ops'", Any way or plans to make it work?

Are you using the latest development version of TensorFlow? https://hub.docker.com/r/tensorflow/tensorflow/
The op changes missed the deadline for 1.3, but should be in 1.4.

Can you please add an dct bool option to the "audio_ops", so that the current mfcc function can be used to extract log-mel features as well? Thanks!

I cloned the master, don't use docker. don't see version 1.4, see only 1.3

When will TensorFlow version 1.4 be available? Can anyone guild me how to get through the Speech Command example with version 1.3. Thanks

It's in the nightly builds (e.g. tensorflow/tensorflow:nightly-gpu-py3).

Hi @rryan ,
I can see that there are two alternatives for processing raw audio waveforms (to obtain spectrograms and mfccs, for example):

audio_ops.audio_spectrogram(), audio_ops.mfcc()
contrib.signal.stft(), some processing, contrib.signal.mfcc_from_log_mel...()

What are the intended / recommended use cases of these two approaches ? It looks confusing to me.

Is there any doc/tutorial for those APIs? It would be very helpful.

Hi @rryan ,
I can see that there are two alternatives for processing raw audio waveforms (to obtain spectrograms and mfccs, for example):
audio_ops.audio_spectrogram(), audio_ops.mfcc()
contrib.signal.stft(), some processing, contrib.signal.mfcc_from_log_mel...()
What are the intended / recommended use cases of these two approaches ? It looks confusing to me.

Hi @georgesterpu,
You can think of audio_ops.audio_spectrogram and audio_ops.mfcc as "fused" ops (like fused batch-norm or fused LSTM cells that TensorFlow has) for the ops in tf.contrib.signal. I think the original motivation of them was that a fused op makes it easier to provide mobile support. I think long term it would be nice if we removed them and provided automatic fusing via XLA, or unified the API to match tf.contrib.signal API, and provided fused keyword arguments to tf.contrib.signal functions, like we do for tf.layers.batch_normalization.
The benefits of tf.contrib.signal are:

Support for backpropagation in training. If you are building machine learning models that generate audio this is crucial. For example, you could include an MFCC loss in a network that generates spectrograms (such as Tacotron) that ensures the MFCCs of your generated spectrogram match those of the target spectrogram.
GPU support -- another crucial feature for training. It's so fast on GPU that you can just compute them as part of your network and feed raw waveforms into your model. We compute all our features on the fly on my team at Google.
Flexibility and experimentation -- you can change the computation of the MFCC or spectrogram to find out what combinations of operations (e.g. different compression options, different frequency warpings, etc.) work best for your use case. There is no "one true" way of computing a spectrogram. There are dozens of different choices that go into it, and machine learning practitioners need the flexibility to experiment.

Is there any doc/tutorial for those APIs? It would be very helpful.

@NearLinHere: I wrote a guide to using tf.contrib.signal that is included in the TensorFlow documentation. Check it out!

Hi there, when I used audio_ops.audio_spectrogram() and contrib.signal.stft() for generating MFCCs, I found that the one using audio_ops is faster than the contrib.signal one. Do you have the same feeling? And do you plan to improve contrib.signal? Thanks a lot!

@jundengdeng, yup -- the main benefit of a "fused" op is that it avoids the compute and memory overhead of the TensorFlow runtime executing a graph of fine-grained ops. For this reason, on CPU the fused ops are likely to perform better (they don't support GPU/TPU).
We are working on making these faster, but as I said, on GPU they are plenty fast for use on the fly (no preprocessing). My suggestion would be to use them on GPU for training instead of running them on CPU in a preprocessing queue / tf.data pipeline.
We are working on making them faster. My hope is that XLA will be able to automatically compile tf.contrib.signal into something that is as fast as a hand-written fused op on CPU.

Thank you, @rryan.

It's so fast on GPU that you can just compute them as part of your network and feed raw waveforms into your model. We compute all our features on the fly on my team at Google.

Does your terminal get flooded with the ffmpeg log whenever you decode audio on the fly ? Asked here as well. I could not find an easy way such as an environment variable for ffmpeg to turn off the output log, there's only a command-line argument loglevel but TF's decode_audio() does not support it. Do you have any suggestion ?

@georgesterpu, I don't use decode_audio, but that sounds quite annoying! Want to file an issue and CC me and @fredbertsch ?

@rryan What do you use to handle audio files ?

We store all of our audio in a protobuf format that's roughly isomorphic to a WAV file (i.e. S16LE audio or float samples, uncompressed on disk). We use custom C++ ops to parse it / the associated metadata. tf.SequenceExample is pretty common, too.

It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Hi @rryan

tf.contrib.signal.mfccs_from_log_mel_spectrograms - for computing MFCCs from log mel spectrograms with GPU and gradient support.

Does this mean GPU is used for feature extraction of audio signals or for training models.
Thanks

Does this mean GPU is used for feature extraction of audio signals or for training models.

Both! It's up to you whether a GPU is used for feature extraction -- you can control where the ops run with tf.device.

The underlying ops all support CPU, GPU, or TPU execution.

Hi, I am trying to update the feature extraction pipeline of an speech command recognition model replacing  the function audio_ops.audio_spectrogram() by  tf.contrib.signal.stft(). I assumed that they were equivalent, but  I am obtaining different results with the same input audio. Could someone explain the relation between the two methods, or if is it possible to obtain the same results using tf.contrib.signal.stft()?
My code:

audio_ops method:

#WAV audio loader
wav_filename_placeholder_ = tf.placeholder(tf.string, [], name='wav_filename')
wav_loader = io_ops.read_file(wav_filename_placeholder_)
sample_rate = 16000
desired_samples = 16000 #1 sec audio
wav_decoder = audio_ops.decode_wav(wav_loader, desired_channels=1, desired_samples=desired_samples)

#Computing the spectrograms
spectrogram = audio_ops.audio_spectrogram(wav_decoder.audio,
                                              window_size=320,
                                              stride=160,
                                              magnitude_squared=False)
with tf.Session() as sess:
    feed_dict={wav_filename_placeholder_:"/<folder_path>/audio_sample.wav"}
    #Get the input audio and the spectrogram
    audio_ops_wav_decoder_audio, audio_ops_spectrogram = sess.run([wav_decoder.audio, spectrogram], feed_dict)

tf.contrib.signal method

#Input WAV audio (will be initialized with the same audio signal: wav_decoder.audio )
signals = tf.placeholder(tf.float32, [None, None])

#Compute the spectrograms and get the absolute values
stfts = tf.contrib.signal.stft(signals,
                               frame_length=320,
                               frame_step=160,
                               fft_length=512,
                               window_fn=None)
magnitude_spectrograms = tf.abs(stfts)
with tf.Session() as sess:
    feed_dict = {signals : audio_ops_wav_decoder_audio.reshape(1,16000)}
    tf_original, tf_stfts, tf_spectrogram, = sess.run([signals, stfts, magnitude_spectrograms], feed_dict)

Thank you in advance

I would also like to know why there is a difference in the code provided by @vadel

Could it be related to this maybe?

https://stackoverflow.com/questions/48660391/using-tensorflow-contrib-framework-python-ops-audio-ops-audio-spectrogram-to-gen

@vadel, @imranparuk -- the implementation of audio_spectrogram and tf.contrib.signal.stft are different (note, in TensorFlow >1.12 and 2.0, this will be tf.signal.stft, as signal is moving out of contrib into core).
audio_spectrogram is a C++ implementation of an STFT, while tf.signal.stft uses TensorFlow ops to compute the STFT (and thus has CPU, GPU and TPU support).
The main cause of difference between them is that audio_spectrogram uses fft2d to compute FFTs while tf.contrib.signal.stft uses Eigen (CPU), cuFFT (GPU), and XLA (TPU). There is another very minor difference, which is that the default periodic Hann window used by each is slightly different. tf.contrib.signal.stft follows numpy/scipy's definition.
From @vadel's code:
#Compute the spectrograms and get the absolute values
stfts = tf.contrib.signal.stft(signals,
                               frame_length=320,
                               frame_step=160,
                               fft_length=512,
                               window_fn=None)

Setting window_fn=None is the main problem here -- applying a window is a core part of the STFT. If you use the default window the difference between audio_spectrogram and tf.contrib.signal.stft is much smaller (to within a tolerance of 1e-3 for the simple example I link below, and 1e-4 when you fix the difference in default window). You cannot in general expect them to produce bit identical outputs because the implementations are different -- even order of operations of floating point operations will affect the result.
We should be able to get very close though -- in this Colab notebook, I show that the difference between the two is less than 1e-4 when using TensorFlow's CPU FFTs. The reason it isn't closer is that tf.contrib.signal.stft uses float32 FFTs, while audio_spectrogram uses float64 FFTs internally. Once I add float64 support to tf.spectral.rfft, you will have the option of using 64-bit math with tf.contrib.signal.stft, which should improve on this bound.

@vadel, @imranparuk -- the implementation of audio_spectrogram and tf.contrib.signal.stft are different (note, in TensorFlow >1.12 and 2.0, this will be tf.signal.stft, as signal is moving out of contrib into core).
audio_spectrogram is a C++ implementation of an STFT, while tf.signal.stft uses TensorFlow ops to compute the STFT (and thus has CPU, GPU and TPU support).
The main cause of difference between them is that audio_spectrogram uses fft2d to compute FFTs while tf.contrib.signal.stft uses Eigen (CPU), cuFFT (GPU), and XLA (TPU). There is another very minor difference, which is that the default periodic Hann window used by each is slightly different. tf.contrib.signal.stft follows numpy/scipy's definition.
From @vadel's code:
#Compute the spectrograms and get the absolute values
stfts = tf.contrib.signal.stft(signals,
                               frame_length=320,
                               frame_step=160,
                               fft_length=512,
                               window_fn=None)

Setting window_fn=None is the main problem here -- applying a window is a core part of the STFT. If you use the default window the difference between audio_spectrogram and tf.contrib.signal.stft is much smaller (to within a tolerance of 1e-3 for the simple example I link below, and 1e-4 when you fix the difference in default window). You cannot in general expect them to produce bit identical outputs because the implementations are different -- even order of operations of floating point operations will affect the result.
We should be able to get very close though -- in this Colab notebook, I show that the difference between the two is less than 1e-4 when using TensorFlow's CPU FFTs. The reason it isn't closer is that tf.contrib.signal.stft uses float32 FFTs, while audio_spectrogram uses float64 FFTs internally. Once I add float64 support to tf.spectral.rfft, you will have the option of using 64-bit math with tf.contrib.signal.stft, which should improve on this bound.

Thanks for the explanation. Though the output is similar for the spectrogram when we have to calculate the mfccs the outputs for audio_ops.mfcc doesn't match with the output of tf.signal.mfccs_from_log_mel_spectrogram.
This notebook has the code which was written to replicate, Colab Notebook

I am comparing audios_ops.mfcc and tf.signal.mfccs_from_log_mel_spectogram to each other they are the same only with a tolerance of 1e-1.
Is that an expected amount of difference of should they be closer?


No longer supported on Version 23.12.1?

Bug/Issue Description
Add on startup failed on latest version of anki
To Reproduce
Steps to reproduce:

Open anki on the latest version
See error

I'm sorry if this report is not formatted correctly, I just joined GitHub. And, thank you so much for the add on, I have found it so motivating!

Check existing issues before creating one.
https://github.com/iamjustkoi/StudyTimeStats/issues/40

Hi - I had checked. The add-on worked perfectly for me when that issue was reported. I've opened a new one because I thought that this was to do with the add-on not being supported with the latest version. But, I'll check again to see if the fix for that issue will work for mine.

Check existing issues before creating one. #40

Hi - I had checked. The add-on worked perfectly for me when that issue was reported. I've opened a new one because I thought that this was to do with the add-on not being supported with the latest version. But, I'll check again to see if the fix for that issue will work for mine.

Sounds like you hadn't upgrade to 23.10 at the time of the existing issue in that case. This addon will not work for anyone who upgrades to 23.10+.

Sounds like you hadn't upgrade to 23.10 at the time of the existing issue in that case. This addon will not work for anyone who upgrades to 23.10+.

Yeah this seems like it could be the case.
Either way, appreciate the report and will merge as a duplicate of #40, for the time being!
Thanks again, will be trying to merge PR #43 and push an update/fix for this as soon as I can! ^^


rust-analyzer is not usable on project that uses specs crate

The project I'm working on contains specs crate. If I edit any of the specs' systems (eg. if I edit SystemData type) and make any kind of mistake (eg. forget to use &mut instead of &), rust-analyzer doesn't let me to even save the file. It's stuck on "Formatting" in VSCode forever and uses 100% of CPU. Even if I exit VSCode, rust-analyzer-mac process doesn't stop and I have to kill it manually.
I was able to replicate this in basic.rs example in specs repo. Edit line type SystemData = (WriteStorage<'a, Pos>, ReadStorage<'a, Vel>); in SysA to contain ReadStorage<'a, Vel> one more time and rust-analyzer immediatelly does what I described above.
I'm using:

rust-analyzer 0.2.224
specs 0.16.1
VSCode
MacOS 10.15.5

Does cargo fmt work?

Yes, it does.

Can you check the output pane for panics?

If you mean Output -> Rust Analyzer Language Server Trace, then it's completely empty. I tried to let it hang for a couple of minutes and there was no change. CPU was at 100% and stuck on "Running 'rust-analyzer' Formatter" until it eventually formatted and saved the file.

A minimal reproducible example (preferably as a git repo with cargo.lock) would help us to debug this faster :)

@matklad I have mentioned in the original post how I was able to reproduce it. The example is located in specs repo.

Ah, sorry, I've missed the link, thanks for pointing this out!

Same problem on Windows, with rust-analyzer version 0.2.297. In projects using amethyst crate (that has dependencies on specs).
The extension resumes normal operations after restarting VScode.
Found this log, not sure if it helps/is relevant:
[2020-09-04 21:20:31.119] [renderer1] [error] content modified: Error: content modified
	at handleResponse (matklad.rust-analyzer-0.2.297\out\src\main.js:3413:48)
	at processMessageQueue (matklad.rust-analyzer-0.2.297\out\src\main.js:3238:17)
	at Immediate.<anonymous> (matklad.rust-analyzer-0.2.297\out\src\main.js:3222:13)
	at processImmediate (internal/timers.js:439:21)
[2020-09-04 21:40:42.085] [renderer1] [error] content modified: Error: content modified
	at handleResponse (matklad.rust-analyzer-0.2.297\out\src\main.js:3413:48)
	at processMessageQueue (matklad.rust-analyzer-0.2.297\out\src\main.js:3238:17)
	at Immediate.<anonymous> (matklad.rust-analyzer-0.2.297\out\src\main.js:3222:13)
	at processImmediate (internal/timers.js:439:21)
[2020-09-04 21:42:16.701] [renderer1] [error] read ECONNRESET: Error: read ECONNRESET
	at TLSWrap.onStreamRead (internal/stream_base_commons.js:183:27)
[2020-09-04 21:49:08.414] [renderer1] [error] content modified: Error: content modified
	at handleResponse (matklad.rust-analyzer-0.2.297\out\src\main.js:3413:48)
	at processMessageQueue (matklad.rust-analyzer-0.2.297\out\src\main.js:3238:17)
	at Immediate.<anonymous> (matklad.rust-analyzer-0.2.297\out\src\main.js:3222:13)
	at processImmediate (internal/timers.js:439:21)

@ondrowan can you test this again? I can't reproduce:

I have tried it and it seems this has been already fixed. Thanks!


Test updated break functionality on Windows

I've merged the changes that use setBreak/clearBreak APIs in #287. It runs fine on the windows systems I've tried, with the caveat that any program must have a 200ms delay before writing to serial port due to framing issues covered in #194.
I'm opening this issue for @PropGit to verify these changes on his system as well. Please let me know if you run into any issues with the new build.

@2fast2fourier - I'm not having success. :-(

I rebuilt

On my Ubuntu VM, I first tried git pull origin master but it failed with a merge conflict in package.json.  I'm not sure why it didn't just fast forward.
So I deleted my whole repo folder and did a git clone git@github.com:parallaxinc/Parallax-IDE
Followed by cd Parallax-IDE
Then npm install
Then npm run build
Then I copied assets, fonts, icons, _locales, background.js, bundle.js, index.html, and manifest.json to my Win 7 64-bit host
Then I loaded it as an unpacked extension

Verified I'm running Chrome v45

Ran app and tried Download

I tried downloading the following code:

'{$STAMP BS2}
'{$PBASIC 2.5}

STOP

and got no response

So I tried downloading the same exact code on the BSE and it was instantly successful.

BSE Reference
--zoomed out--

-- and a zoom-in of the start of the second burst (successful download after successful identify)

Parallax IDE Capture
--zoomed out--

-- and a zoom-in of the start of the first burst (failed identify)

On the plus side, I see that there is now just a single DTR pulse at the start of every attempt, just like BSE; fantastic!
On the negative side, The Host TX seems to be holding the line in BREAK (High) constantly and then unBREAKing at the moment it should actually be BREAKing the TX.  It's the opposite of what it should be.
How does this look on your side?  You said you've had success on your Windows systems.

What version(s) of Windows did you use?
What version of Chrome are you using that/those systems?

@2fast2fourier - Related to our meeting discussion about the port being left in BREAK from the previous open.  I didn't know that was even possible.  Please update the code to always ensure BREAK is disengaged upon port opening so the inverted signal state is not a problem on any future port openings that the app attempts.

@PropGit I have the changes we discussed on the call available on the break-compat branch. If you could check out that branch, delete the node_modules folder, and re-install, it should get the right dependencies.
Please let me know what you see, and post logic scans if you can. Thanks!

@2fast2fourier - Yes, I'll be able to check this out later tonight.  Thanks!

@2fast2fourier - Success!
At first I thought it failed again, but then I realized I didn't have by BOE powered- so what it was telling me was truthful.
In case it matters, I noticed that the Tx is set in BREAK the very first time the port is open, and then the app seems to clear it.
Here is the results of an identify, the first time the port is opened from the App (and happens to be with the BOE not powered).

Here's the second time (still with the BOE unpowered).

Notice the difference at the start?  I don't think this is going to cause any problems; just wanted to mention it in case it sparks a thought.
Here's the trace when the BOE is powered and Parallax IDE successfully identifies and then downloads to the BS2.

Here's the zoomed-in view of the download portion of the trace.

So, it looks like it's working well now!  I'll keep testing and report anything I find that's a problem.  Otherwise, I'll report total success again.

@2fast2fourier - Can you test against Chrome 45?
I'm asking because it appears you've drastically improved the situation; dare I say, completely fixed it?
In my tests I haven't had it fail to download again despite various DEBUG statements in previous downloads that are outputting version lengths and types of data.
For example, this code:
'{$STAMP BS2}
'{$PBASIC 2.5}

DO
  DEBUG "This is a big test where lots of text is being out plus a number: ", DEC W0, CR
  W0 = W0 + 1
LOOP

causes v0.8.1 to fail; however, this new version (built against the break-compat branch, commit 7166893... ) hasn't failed to download against it yet!

@PropGit Great news.  He tested against Chrome 45 while putting together the fix.  I think the download failures are still possible, just much less likely.  I will get this change propagated through the dependencies and into master before release.

I've updated the dependency in master and will be removing the branches shortly

Sounds great.  Looking forward to testing all the other changes when you release.

Done.  Things are so much better than before!  See Issue #194 and Issue #144.


Problem when trying to cache views

Discussed in https://github.com/laravel/framework/discussions/44729

Originally posted by Sebteams69 October 25, 2022
Hi everybody,
I deployed in production my backend which use laravel. After deploying I ran into an issue a I don't understand how to solve it.
The problem occurs when I run the command php artisan view:cache
An exception is raised in Illuminate\Foundation\Console\ViewCacheCommand::Illuminate\Foundation\Console{closure}(Object(Symfony\Component\Finder\SplFileInfo), "vendor/laravel/framework/src/Illuminate/Notifications/resources/views/email.blade.php"
I have upgraded my composer to the latest laravel/framework version but still have the same issue.
Could anyone help me please?
Regards,
Sebastien

Please don't move discussions to issues, thanks.


⚠ Fetchers has degraded performance

In 4583f4b, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 291 ms

Resolved: Fetchers performance has improved in 37a528e.


Use Gson as the default JSon ser/de library

Address serialization enhancements as mentioned in PR https://github.com/MSOpenTech/msopentech-tools-for-intellij/pull/33 discussion

Below are the Json Occurrences.

JsonSlurper is no longer being used in the code.


#17 Updates jacoco configuration for multiplatform project

The issue is with jacoco configuration, with existing configuration jacoco was not able to generate report for kotlin multiplatform project.
Reference: https://stackoverflow.com/questions/59802396/kotlin-multiplatform-coverage
Coverage Report: https://codecov.io/github/ashishkujoy/klogging/commit/7702016938f7c55c0f117db48385d8e30bbf9caf

Codecov Report

Merging #56 (7702016) into main (b94228d) will increase coverage by 85.94%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #56       +/-   ##
===========================================
+ Coverage        0   85.94%   +85.94%
- Complexity      0       98       +98
===========================================
  Files           0       67       +67
  Lines           0     2163     +2163
  Branches        0      143      +143
===========================================
+ Hits            0     1859     +1859
- Misses          0      231      +231
- Partials        0       73       +73

Impacted Files
Coverage Δ

src/commonMain/kotlin/io/klogging/Level.kt
41.66% <0.00%> (ø)

...mTest/kotlin/io/klogging/context/LogContextTest.kt
74.28% <0.00%> (ø)

...c/commonMain/kotlin/io/klogging/config/Defaults.kt
100.00% <0.00%> (ø)

src/commonMain/kotlin/io/klogging/Klogging.kt
85.71% <0.00%> (ø)

...c/commonMain/kotlin/io/klogging/sending/SendElk.kt
65.00% <0.00%> (ø)

...monMain/kotlin/io/klogging/rendering/RenderAnsi.kt
53.33% <0.00%> (ø)

...ommonMain/kotlin/io/klogging/context/LogContext.kt
89.47% <0.00%> (ø)

...monMain/kotlin/io/klogging/config/LoggingConfig.kt
70.00% <0.00%> (ø)

...commonMain/kotlin/io/klogging/config/LevelRange.kt
100.00% <0.00%> (ø)

src/commonMain/kotlin/io/klogging/NoCoLogger.kt
0.00% <0.00%> (ø)

... and 57 more

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 b94228d...7702016. Read the comment docs.


[FEATURE] Builder methods for Optional fields

Describe the feature
Add an overloaded method to set the value of an java.util.Optional field directly with Optional.of() See usage example.
`
@Value
@Builder(toBuilder = true)
public class Pojo {
String requiredField;
@Builder.Default
Optional<String> optionalField = Optional.empty();

public static void main(String[] args) {
    Pojo pojo = Pojo
            .builder()
            .requiredField("required")
            .optionalField(Optional.of("optional"))
            //This is not supported
            //.optionalField("optional")
            .build();
}

}
`

I would love this feature, for @With annotations as well :)

See Lombok’s position on null and Optional.

Hence, any feature requests that involve optional will likely be denied.

See also this recommendation from Brian Goetz who helped introduce Optional to the language:

You should almost never use it as a field of something


error: ‘EPrecision’ is not a member of ‘tcnn::cpp’; did you mean ‘Precision’?

error: ‘EPrecision’ is not a member of ‘tcnn::cpp’; did you mean ‘Precision’?

Change EPrecision to Precision. It happens when you use a newer version of tiny-cuda-nn

I have the same problem. Have you solved it


Bump Postgrex to version 0.10

Ecto >= 1.1 (https://hex.pm/packages/ecto/1.1.0) uses Postgrex 0.10 which causes the dependency resolution to fail.
Looking up alternatives for conflicting requirements on postgrex
  Activated version: 0.9.1
  From mix.exs: >= 0.0.0
  From mix.lock: 0.9.1
  From ecto v1.1.1: ~> 0.10
  From guardian_db v0.3.0: ~> 0.9.1

** (Mix) Hex dependency resolution failed, relax the version requirements or unlock dependencies

This issue (#5) will be corrected by removing the Postgrex dependency as planned in issue #7.


[AIRFLOW-1245] Fix random failure in test_trigger_dag_for_date

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following:

AIRFLOW-1245 Fix random failure of test_trigger_dag_for_date unit test

Description

[x] This failure happens from time to time:
https://travis-ci.org/apache/incubator-airflow/jobs/235993912

======================================================================
14) FAIL: test_trigger_dag_for_date (tests.www.api.experimental.test_endpoints.ApiExperimentalTests)
----------------------------------------------------------------------
   Traceback (most recent call last):
    tests/www/api/experimental/test_endpoints.py line 87 in test_trigger_dag_for_date
      self.assertEqual(200, response.status_code)
   AssertionError: 200 != 404

Tests

[ ] All existing tests pass.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2325 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2325      +/-   ##
==========================================
- Coverage   69.48%   69.47%   -0.01%
==========================================
  Files         144      144
  Lines       11028    11028
==========================================
- Hits         7663     7662       -1
- Misses       3365     3366       +1

Impacted Files
Coverage Δ

airflow/models.py
87.05% <0%> (-0.05%)
:arrow_down:

Continue to review full report at Codecov.

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

LGTM


Getting vulnerable issue<EMAIL_ADDRESS>

Hi,
Please check below
Facing Veracode valunerablity issue using<EMAIL_ADDRESS>--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | --<EMAIL_ADDRESS>deduped | --<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>deduped
1 high severity vulnerabilities
how to resolve above issue?

Hi 👋 and sorry you are having an issue. Unfortunately I'm not sure off-hand what issue you are getting. Please go ahead and follow our process to report security issues outlined at https://github.com/expressjs/express/blob/master/Security.md and provide as much information as poasible so we can assess.


OCPBUGS-8481: [release-4.13] Bump CAPI, CAPI providers, go 1.19

4.13 backport of https://github.com/openshift/cluster-capi-operator/pull/101
Related PRs:
https://github.com/openshift/cluster-api/pull/169
https://github.com/openshift/cluster-api-provider-aws/pull/458
https://github.com/openshift/cluster-api-provider-azure/pull/270
https://github.com/openshift/cluster-api-provider-gcp/pull/192
Todo:

[ ] once all 4.13 backports for the CAPI providers rebases merged to 4.13 branches run make assets + commit

/label cherry-pick-approved

/retest

/approve
/lgtm
/label backport-risk-assessed

/retest-required


abseil-cpp failure on s390x

I'm trying to use Abseil-cpp which is dependency of Istio-proxy on s390x by following https://abseil.io/docs/cpp/quickstart but its failing with the following error:
ERROR: /home/ajay/.cache/bazel/_bazel_ajay/05774821e5b6d73b3dae6e2f79bcee31/external/com_google_absl/absl/base/BUILD.bazel:80:1: C++ compilation of rule '//absl/base:malloc_internal' failed (Exit 1)
In file included from absl/base/internal/low_level_alloc.cc:26:0:
./absl/base/internal/direct_mmap.h: In function 'void* absl::base_internal::DirectMmap(void*, size_t, int, int, int, off64_t)':
./absl/base/internal/direct_mmap.h:96:39: error: cast from 'void*' to 'uint32_t {aka unsigned int}' loses precision [-fpermissive]
       reinterpret_cast<uint32_t>(start), static_cast<uint32_t>(length),
                                       ^
./absl/base/internal/direct_mmap.h:99:10: error: 'reintrepret_cast' was not declared in this scope
   return reintrepret_cast<void*>(syscall(SYS_mmap, buf));
          ^
./absl/base/internal/direct_mmap.h:99:27: error: expected primary-expression before 'void'
   return reintrepret_cast<void*>(syscall(SYS_mmap, buf));
                           ^
./absl/base/internal/direct_mmap.h:99:27: error: expected ';' before 'void'
./absl/base/internal/direct_mmap.h:99:32: error: expected unqualified-id before '>' token
   return reintrepret_cast<void*>(syscall(SYS_mmap, buf));
                                ^
./absl/base/internal/direct_mmap.h:99:32: error: expected initializer before '>' token
./absl/base/internal/direct_mmap.h:95:12: warning: unused variable 'buf' [-Wunused-variable]
   uint32_t buf[6] = {
            ^
INFO: Elapsed time: 72.279s, Critical Path: 2.16s
INFO: 14 processes, linux-sandbox.
 Is it not supported on s390x. What could be the issue here?

I think uint32_t should actually be unsigned long in that function, but I don't have a way of testing on s390x. I can make the change, but if you could try testing it first that would be very helpful.

Now getting below error:
In file included from /home/test/abseil-cpp/absl/debugging/stacktrace.cc:43:0:
/home/test/abseil-cpp/absl/debugging/internal/stacktrace_config.h:71:2: error: #error Not supported yet
 #error Not supported yet
  ^
/home/test/abseil-cpp/absl/debugging/stacktrace.cc:48:3: error: #error Cannot calculate stack trace: will need to write for your environment
 # error Cannot calculate stack trace: will need to write for your environment
   ^
In file included from /home/test/abseil-cpp/absl/debugging/stacktrace.cc:54:0:
/home/test/abseil-cpp/absl/debugging/internal/stacktrace_win32-inl.inc:40:66: fatal error: windows.h: No such file or directory
compilation terminated.
absl/debugging/CMakeFiles/absl_stacktrace.dir/build.make:62: recipe for target 'absl/debugging/CMakeFiles/absl_stacktrace.dir/stacktrace.cc.o' failed
make[2]: *** [absl/debugging/CMakeFiles/absl_stacktrace.dir/stacktrace.cc.o] Error 1
CMakeFiles/Makefile2:546: recipe for target 'absl/debugging/CMakeFiles/absl_stacktrace.dir/all' failed
make[1]: *** [absl/debugging/CMakeFiles/absl_stacktrace.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

Now getting below error:
In file included from /home/test/abseil-cpp/absl/debugging/stacktrace.cc:43:0:
/home/test/abseil-cpp/absl/debugging/internal/stacktrace_config.h:71:2: error: #error Not supported yet
 #error Not supported yet
  ^
/home/test/abseil-cpp/absl/debugging/stacktrace.cc:48:3: error: #error Cannot calculate stack trace: will need to write for your environment
 # error Cannot calculate stack trace: will need to write for your environment
   ^
In file included from /home/test/abseil-cpp/absl/debugging/stacktrace.cc:54:0:
/home/test/abseil-cpp/absl/debugging/internal/stacktrace_win32-inl.inc:40:66: fatal error: windows.h: No such file or directory
compilation terminated.
absl/debugging/CMakeFiles/absl_stacktrace.dir/build.make:62: recipe for target 'absl/debugging/CMakeFiles/absl_stacktrace.dir/stacktrace.cc.o' failed
make[2]: *** [absl/debugging/CMakeFiles/absl_stacktrace.dir/stacktrace.cc.o] Error 1
CMakeFiles/Makefile2:546: recipe for target 'absl/debugging/CMakeFiles/absl_stacktrace.dir/all' failed
make[1]: *** [absl/debugging/CMakeFiles/absl_stacktrace.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

A fix should be submitted early next week.

0268795 should fix this. Please confirm.

Here is the error from make:
[ 61%] Building CXX object absl/debugging/CMakeFiles/absl_examine_stack.dir/internal/examine_stack.cc.o
/home/test/abseil-cpp/absl/debugging/internal/examine_stack.cc:59:2: error: #error "Undefined Architecture."
 #error "Undefined Architecture."
  ^
make[2]: *** [absl/debugging/CMakeFiles/absl_examine_stack.dir/internal/examine_stack.cc.o] Error 1
make[1]: *** [absl/debugging/CMakeFiles/absl_examine_stack.dir/all] Error 2
make: *** [all] Error 2

Another patch is coming. In the mean time, can you post the output with bazel build -k? The -k means bazel will keep going after an error so that we can see if anything else also needs to be fixed.

Actually, can you give my s390x branch a try before I commit it here? https://github.com/derekmauro/abseil-cpp/tree/s390x

output of bazel build -k on both master and derek's s390x branch:
Starting local Bazel server and connecting to it...
.....................
Loading:
Loading: 0 packages loaded
Analyzing: 0 targets (0 packages loaded)
Analyzing: 0 targets (2 packages loaded)
INFO: Analysed 0 targets (2 packages loaded).
INFO: Found 0 targets...
[0 / 1] [-----] BazelWorkspaceStatusAction stable-status.txt
INFO: Elapsed time: 2.509s, Critical Path: 0.01s
INFO: 0 processes.
INFO: Build completed successfully, 1 total action
INFO: Build completed successfully, 1 total action

output of  make -k on both master and derek's s390x branch:
[test@a87fc788a350 build]$ make -k
[  1%] Built target absl_dynamic_annotations
[  3%] Built target absl_malloc_internal
[  5%] Built target absl_spinlock_wait
[ 12%] Built target absl_base
[ 14%] Built target absl_throw_delegate
[ 15%] Built target absl_algorithm
[ 17%] Built target absl_container
[ 19%] Built target test_instance_tracker_lib
[ 21%] Built target absl_stack_consumption
[ 25%] Built target absl_stacktrace
[ 31%] Built target absl_symbolize
[ 33%] Built target absl_leak_check
[ 46%] Built target absl_strings
[ 47%] Built target absl_int128
[ 60%] Built target absl_time
[ 61%] Building CXX object absl/debugging/CMakeFiles/absl_examine_stack.dir/internal/examine_stack.cc.o
/home/test/derel-absiel/absl/debugging/internal/examine_stack.cc:59:2: error: #error "Undefined Architecture."
 #error "Undefined Architecture."
  ^
make[2]: *** [absl/debugging/CMakeFiles/absl_examine_stack.dir/internal/examine_stack.cc.o] Error 1
make[2]: Target `absl/debugging/CMakeFiles/absl_examine_stack.dir/build' not remade because of errors.
make[1]: *** [absl/debugging/CMakeFiles/absl_examine_stack.dir/all] Error 2
Scanning dependencies of target absl_synchronization
[ 61%] Building CXX object absl/synchronization/CMakeFiles/absl_synchronization.dir/barrier.cc.o
[ 62%] Building CXX object absl/synchronization/CMakeFiles/absl_synchronization.dir/blocking_counter.cc.o
[ 63%] Building CXX object absl/synchronization/CMakeFiles/absl_synchronization.dir/internal/create_thread_identity.cc.o
[ 64%] Building CXX object absl/synchronization/CMakeFiles/absl_synchronization.dir/internal/per_thread_sem.cc.o
[ 65%] Building CXX object absl/synchronization/CMakeFiles/absl_synchronization.dir/internal/waiter.cc.o
[ 66%] Building CXX object absl/synchronization/CMakeFiles/absl_synchronization.dir/internal/graphcycles.cc.o
[ 67%] Building CXX object absl/synchronization/CMakeFiles/absl_synchronization.dir/notification.cc.o
[ 67%] Building CXX object absl/synchronization/CMakeFiles/absl_synchronization.dir/mutex.cc.o
[ 68%] Linking CXX static library libabsl_synchronization.a
[ 68%] Built target absl_synchronization
Scanning dependencies of target absl_debugging
[ 69%] Building CXX object absl/debugging/CMakeFiles/absl_debugging.dir/absl_debugging_header_only_dummy.cc.o
[ 70%] Linking CXX static library libabsl_debugging.a
[ 70%] Built target absl_debugging
Scanning dependencies of target absl_memory
[ 71%] Building CXX object absl/memory/CMakeFiles/absl_memory.dir/absl_memory_header_only_dummy.cc.o
[ 72%] Linking CXX static library libabsl_memory.a
[ 72%] Built target absl_memory
Scanning dependencies of target absl_meta
[ 72%] Building CXX object absl/meta/CMakeFiles/absl_meta.dir/absl_meta_header_only_dummy.cc.o
[ 73%] Linking CXX static library libabsl_meta.a
[ 73%] Built target absl_meta
Scanning dependencies of target absl_numeric
[ 74%] Building CXX object absl/numeric/CMakeFiles/absl_numeric.dir/absl_numeric_header_only_dummy.cc.o
[ 75%] Linking CXX static library libabsl_numeric.a
[ 75%] Built target absl_numeric
Scanning dependencies of target absl_utility
[ 76%] Building CXX object absl/utility/CMakeFiles/absl_utility.dir/absl_utility_header_only_dummy.cc.o
[ 77%] Linking CXX static library libabsl_utility.a
[ 77%] Built target absl_utility
Scanning dependencies of target str_format_extension_internal
[ 78%] Building CXX object absl/strings/CMakeFiles/str_format_extension_internal.dir/internal/str_format/extension.cc.o
[ 79%] Building CXX object absl/strings/CMakeFiles/str_format_extension_internal.dir/internal/str_format/output.cc.o
[ 80%] Linking CXX static library libstr_format_extension_internal.a
[ 80%] Built target str_format_extension_internal
Scanning dependencies of target absl_span
[ 81%] Building CXX object absl/types/CMakeFiles/absl_span.dir/absl_span_header_only_dummy.cc.o
[ 81%] Linking CXX static library libabsl_span.a
[ 81%] Built target absl_span
Scanning dependencies of target str_format_internal
[ 82%] Building CXX object absl/strings/CMakeFiles/str_format_internal.dir/internal/str_format/arg.cc.o
[ 83%] Building CXX object absl/strings/CMakeFiles/str_format_internal.dir/internal/str_format/bind.cc.o
[ 83%] Building CXX object absl/strings/CMakeFiles/str_format_internal.dir/internal/str_format/extension.cc.o
[ 84%] Building CXX object absl/strings/CMakeFiles/str_format_internal.dir/internal/str_format/float_conversion.cc.o
[ 85%] Building CXX object absl/strings/CMakeFiles/str_format_internal.dir/internal/str_format/output.cc.o
[ 86%] Building CXX object absl/strings/CMakeFiles/str_format_internal.dir/internal/str_format/parser.cc.o
[ 87%] Linking CXX static library libstr_format_internal.a
[ 87%] Built target str_format_internal
Scanning dependencies of target absl_str_format
[ 88%] Building CXX object absl/strings/CMakeFiles/absl_str_format.dir/absl_str_format_header_only_dummy.cc.o
[ 89%] Linking CXX static library libabsl_str_format.a
[ 89%] Built target absl_str_format
Scanning dependencies of target absl_variant
[ 89%] Building CXX object absl/types/CMakeFiles/absl_variant.dir/bad_variant_access.cc.o
[ 90%] Linking CXX static library libabsl_variant.a
[ 90%] Built target absl_variant
Scanning dependencies of target absl_bad_any_cast
[ 91%] Building CXX object absl/types/CMakeFiles/absl_bad_any_cast.dir/bad_any_cast.cc.o
[ 92%] Linking CXX static library libabsl_bad_any_cast.a
[ 92%] Built target absl_bad_any_cast
Scanning dependencies of target absl_any
[ 93%] Building CXX object absl/types/CMakeFiles/absl_any.dir/absl_any_header_only_dummy.cc.o
[ 94%] Linking CXX static library libabsl_any.a
[ 94%] Built target absl_any
Scanning dependencies of target absl_bad_optional_access
[ 94%] Building CXX object absl/types/CMakeFiles/absl_bad_optional_access.dir/bad_optional_access.cc.o
[ 95%] Linking CXX static library libabsl_bad_optional_access.a
[ 95%] Built target absl_bad_optional_access
Scanning dependencies of target absl_optional
[ 96%] Building CXX object absl/types/CMakeFiles/absl_optional.dir/optional.cc.o
[ 97%] Linking CXX static library libabsl_optional.a
[ 97%] Built target absl_optional
make[1]: Target `all' not remade because of errors.
make: *** [all] Error 2
make: Target `default_target' not remade because of errors.

output of bazel build -k absl/... on master:
[test@a87fc788a350 abseil-cpp]$ bazel build -k absl/...
Starting local Bazel server and connecting to it...
..........................................................................................
INFO: Analysed 157 targets (25 packages loaded).
INFO: Found 157 targets...
ERROR: /home/test/abseil-cpp/absl/base/BUILD.bazel:324:1: Couldn't build file absl/base/_objs/endian_test/absl/base/internal/endian_test.pic.o: C++ compilation of rule '//absl/base:endian_test' failed (Exit 1)
absl/base/internal/endian_test.cc:41:25: error: 'k8Value' was not declared in this scope
 const uint8_t k8ValueLE{k8Value};
                         ^~~~~~~
absl/base/internal/endian_test.cc:53:25: error: 'k8Value' was not declared in this scope
 const uint8_t k8ValueBE{k8Value};
                         ^~~~~~~
cc1plus: warning: unrecognized command line option '-Wno-unused-private-field'
INFO: From Compiling absl/debugging/symbolize_test.cc:
/tmp/ccuZhDRN.s: Assembler messages:
/tmp/ccuZhDRN.s:2407: Warning: ignoring changed section attributes for .text
ERROR: /home/test/abseil-cpp/absl/debugging/BUILD.bazel:79:1: Couldn't build file absl/debugging/_objs/examine_stack/absl/debugging/internal/examine_stack.pic.o: C++ compilation of rule '//absl/debugging:examine_stack' failed (Exit 1)
absl/debugging/internal/examine_stack.cc:59:2: error: #error "Undefined Architecture."
 #error "Undefined Architecture."
  ^~~~~
absl/debugging/internal/examine_stack.cc: In function 'void* absl::debugging_internal::GetProgramCounter(void*)':
absl/debugging/internal/examine_stack.cc:41:17: warning: unused variable 'context' [-Wunused-variable]
     ucontext_t* context = reinterpret_cast<ucontext_t*>(vuc);
                 ^~~~~~~
INFO: Elapsed time: 228.388s, Critical Path: 42.85s
INFO: 488 processes: 102 local, 386 processwrapper-sandbox.
FAILED: Build did NOT complete successfully

output on derek's s390x branch:
Starting local Bazel server and connecting to it...
....................................
INFO: Analysed 157 targets (25 packages loaded).
INFO: Found 157 targets...
INFO: From Compiling absl/debugging/symbolize_test.cc:
/tmp/cc5DY5px.s: Assembler messages:
/tmp/cc5DY5px.s:2407: Warning: ignoring changed section attributes for .text
ERROR: /home/test/derel-absiel/absl/base/BUILD.bazel:324:1: Couldn't build file absl/base/_objs/endian_test/absl/base/internal/endian_test.pic.o: C++ compilation of rule '//absl/base:endian_test' failed (Exit 1)
absl/base/internal/endian_test.cc:41:25: error: 'k8Value' was not declared in this scope
 const uint8_t k8ValueLE{k8Value};
                         ^~~~~~~
absl/base/internal/endian_test.cc:53:25: error: 'k8Value' was not declared in this scope
 const uint8_t k8ValueBE{k8Value};
                         ^~~~~~~
cc1plus: warning: unrecognized command line option '-Wno-unused-private-field'
INFO: Elapsed time: 210.561s, Critical Path: 41.36s
INFO: 492 processes: 102 local, 390 processwrapper-sandbox.
FAILED: Build did NOT complete successfully

Thanks. I pushed another commit to my s390x branch to address the error in endian_test.cc. Can you sync that branch and post the output of bazel test -k absl/...? Hopefully this is the last time I'll need you to do this.

Build was successful on recent s390x branch, output of  bazel test -k absl/... :
INFO: Build completed, 22 tests FAILED, 105 total actions
//absl/algorithm:algorithm_test                                          PASSED in 0.0s
//absl/algorithm:container_test                                          PASSED in 0.0s
//absl/base:atomic_hook_test                                             PASSED in 0.0s
//absl/base:bit_cast_test                                                PASSED in 0.0s
//absl/base:call_once_test                                               PASSED in 0.1s
//absl/base:config_test                                                  PASSED in 0.7s
//absl/base:endian_test                                                  PASSED in 0.6s
//absl/base:exception_safety_testing_test                                PASSED in 0.0s
//absl/base:inline_variable_test                                         PASSED in 0.2s
//absl/base:invoke_test                                                  PASSED in 0.1s
//absl/base:low_level_alloc_test                                         PASSED in 4.3s
//absl/base:raw_logging_test                                             PASSED in 0.6s
//absl/base:spinlock_test                                                PASSED in 0.8s
//absl/base:thread_identity_test                                         PASSED in 0.2s
//absl/base:throw_delegate_test                                          PASSED in 0.1s
//absl/container:fixed_array_exception_safety_test                       PASSED in 0.1s
//absl/container:fixed_array_test                                        PASSED in 3.3s
//absl/container:fixed_array_test_noexceptions                           PASSED in 3.3s
//absl/container:inlined_vector_test                                     PASSED in 0.3s
//absl/container:inlined_vector_test_noexceptions                        PASSED in 0.3s
//absl/container:test_instance_tracker_test                              PASSED in 0.1s
//absl/debugging:demangle_test                                           PASSED in 0.1s
//absl/debugging:disabled_leak_check_test                                PASSED in 0.1s
//absl/debugging:failure_signal_handler_test                             PASSED in 2.4s
//absl/debugging:leak_check_no_lsan_test                                 PASSED in 0.1s
//absl/debugging:leak_check_test                                         PASSED in 0.1s
//absl/debugging:stack_consumption_test                                  PASSED in 0.1s
//absl/debugging:symbolize_test                                          PASSED in 0.1s
//absl/memory:memory_exception_safety_test                               PASSED in 0.1s
//absl/memory:memory_test                                                PASSED in 0.2s
//absl/meta:type_traits_test                                             PASSED in 0.1s
//absl/numeric:int128_test                                               PASSED in 0.5s
//absl/strings:ascii_test                                                PASSED in 0.1s
//absl/strings:char_map_test                                             PASSED in 0.3s
//absl/strings:charconv_bigint_test                                      PASSED in 0.6s
//absl/strings:charconv_parse_test                                       PASSED in 0.1s
//absl/strings:charconv_test                                             PASSED in 21.8s
//absl/strings:escaping_test                                             PASSED in 0.2s
//absl/strings:match_test                                                PASSED in 0.2s
//absl/strings:memutil_test                                              PASSED in 0.2s
//absl/strings:numbers_test                                              PASSED in 22.7s
//absl/strings:ostringstream_test                                        PASSED in 0.1s
//absl/strings:resize_uninitialized_test                                 PASSED in 0.5s
//absl/strings:str_cat_test                                              PASSED in 1.4s
//absl/strings:str_format_arg_test                                       PASSED in 0.1s
//absl/strings:str_format_bind_test                                      PASSED in 0.1s
//absl/strings:str_format_checker_test                                   PASSED in 0.2s
//absl/strings:str_format_convert_test                                   PASSED in 6.4s
//absl/strings:str_format_extension_test                                 PASSED in 0.1s
//absl/strings:str_format_output_test                                    PASSED in 0.1s
//absl/strings:str_format_parser_test                                    PASSED in 0.2s
//absl/strings:str_format_test                                           PASSED in 1.5s
//absl/strings:str_join_test                                             PASSED in 0.2s
//absl/strings:str_replace_test                                          PASSED in 0.1s
//absl/strings:str_split_test                                            PASSED in 12.7s
//absl/strings:string_view_test                                          PASSED in 12.8s
//absl/strings:strip_test                                                PASSED in 0.1s
//absl/strings:substitute_test                                           PASSED in 0.7s
//absl/strings:utf8_test                                                 PASSED in 0.1s
//absl/synchronization:barrier_test                                      PASSED in 1.0s
//absl/synchronization:blocking_counter_test                             PASSED in 1.1s
//absl/synchronization:graphcycles_test                                  PASSED in 5.1s
//absl/synchronization:lifetime_test                                     PASSED in 0.1s
//absl/synchronization:mutex_test                                        PASSED in 125.4s
//absl/synchronization:notification_test                                 PASSED in 0.2s
//absl/synchronization:per_thread_sem_test                               PASSED in 4.3s
//absl/time:time_test                                                    PASSED in 7.3s
//absl/time/internal/cctz:civil_time_test                                PASSED in 0.1s
//absl/time/internal/cctz:time_zone_format_test                          PASSED in 0.9s
//absl/time/internal/cctz:time_zone_lookup_test                          PASSED in 3.0s
//absl/types:any_exception_safety_test                                   PASSED in 0.1s
//absl/types:any_test                                                    PASSED in 0.1s
//absl/types:any_test_noexceptions                                       PASSED in 0.1s
//absl/types:optional_exception_safety_test                              PASSED in 0.1s
//absl/types:optional_test                                               PASSED in 0.0s
//absl/types:span_test                                                   PASSED in 0.1s
//absl/types:span_test_noexceptions                                      PASSED in 0.1s
//absl/types:variant_exception_safety_test                               PASSED in 0.1s
//absl/types:variant_test                                                PASSED in 0.1s
//absl/utility:utility_test                                              PASSED in 0.0s
//absl/algorithm:algorithm_benchmark                                     FAILED in 2.3s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/algorithm/algorithm_benchmark/test.log
//absl/base:sysinfo_test                                                 FAILED in 1.3s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/base/sysinfo_test/test.log
//absl/base:thread_identity_benchmark                                    FAILED in 0.3s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/base/thread_identity_benchmark/test.log
//absl/container:fixed_array_benchmark                                   FAILED in 0.3s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/container/fixed_array_benchmark/test.log
//absl/container:inlined_vector_benchmark                                FAILED in 0.3s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/container/inlined_vector_benchmark/test.log
//absl/numeric:int128_benchmark                                          FAILED in 0.4s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/numeric/int128_benchmark/test.log
//absl/strings:char_map_benchmark                                        FAILED in 0.4s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/char_map_benchmark/test.log
//absl/strings:charconv_benchmark                                        FAILED in 0.5s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/charconv_benchmark/test.log
//absl/strings:escaping_benchmark                                        FAILED in 0.7s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/escaping_benchmark/test.log
//absl/strings:memutil_benchmark                                         FAILED in 0.7s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/memutil_benchmark/test.log
//absl/strings:numbers_benchmark                                         FAILED in 0.8s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/numbers_benchmark/test.log
//absl/strings:ostringstream_benchmark                                   FAILED in 0.5s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/ostringstream_benchmark/test.log
//absl/strings:str_cat_benchmark                                         FAILED in 0.5s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/str_cat_benchmark/test.log
//absl/strings:str_join_benchmark                                        FAILED in 0.4s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/str_join_benchmark/test.log
//absl/strings:str_replace_benchmark                                     FAILED in 0.7s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/str_replace_benchmark/test.log
//absl/strings:str_split_benchmark                                       FAILED in 0.6s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/str_split_benchmark/test.log
//absl/strings:string_view_benchmark                                     FAILED in 0.6s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/strings/string_view_benchmark/test.log
//absl/synchronization:graphcycles_benchmark                             FAILED in 0.3s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/synchronization/graphcycles_benchmark/test.log
//absl/synchronization:mutex_benchmark                                   FAILED in 0.3s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/synchronization/mutex_benchmark/test.log
//absl/time:time_benchmark                                               FAILED in 0.3s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/time/time_benchmark/test.log
//absl/time/internal/cctz:cctz_benchmark                                 FAILED in 0.3s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/time/internal/cctz/cctz_benchmark/test.log
//absl/types:variant_benchmark                                           FAILED in 0.4s
  /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/types/variant_benchmark/test.log

Executed 102 out of 102 tests: 80 tests pass and 22 fail locally.
INFO: Build completed, 22 tests FAILED, 105 total actions

Glad the it builds, I'll get these fixes committed to the main repository soon.
We should try to deal with the test failures though. Since all but one of the test failures is a benchmark, there is probably a single cause to all of those failures. Can you post the test log file for one of the benchmark failures?
Also, //absl/base:sysinfo_test is the only non-benchmark test that is failing. Can you post that log as well?
To get the logs, you may have to re-run the test command. The log for sysinfo_test, for example, is /home/test/.cache/bazel/_bazel_test/bebead0d3439847fa452d4aab3f3a5c1/execroot/com_google_absl/bazel-out/s390x-fastbuild/testlogs/absl/base/sysinfo_test/test.log in the output you posted above.

Thanks. This should build now on s390x at e0def7473e52336f58759e11db4cd9467e5e0356.
The tests don't look like something I'm going to be able to fix without either a machine to test on, or a lot of back and forth, but I think it should still be safe to use Abseil.
I'm going to close this now that the build is fixed. We will don't officially support s390x, but let us know if something breaks and I will look into it.

Thanks @derekmauro and Abseil Team for your efforts and patience into making the build pass on s390x even without having and actual machine to test on.


fix: update pyproject and put package

Put package in pyproject and updated some dependencies

No vulnerabilities detected
No vulnerabilities with HIGH,CRITICAL severity have been detected in the code.


Add Tox integration - Merge after #9

Use Tox to automate testing in different virtualenvs with TravisCI. One can use tox to have the same results of TravisCI without needing to push.

Simplifies travis.yml
Add tox.ini
Add Python 3.7-dev test env
Integrate Tox with TravisCI
Add install_requires explicitly
Remove dev-requirements.txt because it's no longer used

This pull request should be merged after #9 in order to work, because it uses Python 3

All the changes were made and for a cleaner solution I created another PR #12 . I close this


References to use '&T' notation instead of 'Reference' notation

This is with the goal of eventually deprecating the 'Reference<' notation.


Update README.md

Checkmarx One – Scan Summary & Details – 3f13f88b-d244-4766-b2cb-0435b3ce51d8
No New Or Fixed Issues Found