Can't start manual brew on Pico C

So I setup the latest version of the Picobrew Raspberry server last night. (Thanks again for the hard work.) I tried to run a manual brew this afternoon on my C and I could connect to the picoserver's wifi BUT it errored out when I wanted to start a manual brew. Any ideas?

Sometimes it'll timeout doing requests back and forth... I'd try power cycling and trying again a few times (assuming you haven't)

I did try that. The pico gave me directions to connect the hoses, put the hop cage in the step filter, fill the tank, and then i think it errored out just before asking to fill the step filter with grain and water. I lost patience and switched back to the official server for my brew session today. I am happy to provide any server logs. Thanks.

ddrum2000, can you provide any info on if the PicoC interface appears any different when connected to the official server vs the local server? How do you select one of the recipes (json files) that are in the library?

No display does not appear different then when on the manual server. Yesterday I was doing a manual brew no a preprogrammed brew so I wasn't looking to choose a recipe from the server.
Linking to a conversation I had with Ender today on facebook...
"I'm trying to brew cold brew today and have a similar problem to yesterday. I get a Code 7 error when trying to begin the brew cycle. When I test the wifi under the Settings menu no errors are reported. I have restarted both the RPi and the Pico and it eventually worked but data doesn't seem to be logging the graph. The Pico C data plot still waiting to brew. Should this be happening in the Cold Brew cycle?
A side observation, when connecting to the RPi wifi access point, it seems like it takes much longer to move from the "Connected" response to the main menu as compared to the official server.
...some chatter back and forth...
From Ender - Chris (me) check the error logs, on some firmwares there was an update to allow session to continue upon receiving an error from the server. No data logging would happen if that was the case as the machine may choose to stop sending them. Though maybe the machine is sending them, but the server is failing as well.
From me - Ender yes certainly errors. I can dump the file but there are a lot of entries similar to this in picobrew.error.log:
2020/09/08 21:10:41 [error] 389#389: *255 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: www.picobrew.com, request: "GET /API/pico/log?uid=38cb1da690ae8f330733ad970049633b&sesId=5040a605df26473d80ec&wort=119&therm=328&step=Maintain&error=0&sesType=4&timeLeft=2545&shutScale=0.20 HTTP/1.0", upstream: "http://[::1]:8080/API/pico/log?uid=38cb1da690ae8f330733ad970049633b&sesId=5040a605df26473d80ec&wort=119&therm=328&step=Maintain&error=0&sesType=4&timeLeft=2545&shutScale=0.20", host: "picobrew.com"

ddrum2000, ahh, for some reason I thought the interface would behave/look differently. So, is there a way to use the recipe files (preprogrammed) I have loaded into the picobrew server via samba instead of the manual brew process? I am building my own picopak and hop-pak bins and would like to be able to add ingredients to them and start a brew cycle similar to when the machine pulls the info from the rfid tag. Is this possible? Can ask these questions on FB if that is a better place to do so.

ddrum2000, ahh, for some reason I thought the interface would behave/look differently. So, is there a way to use the recipe files (preprogrammed) I have loaded into the picobrew server via samba instead of the manual brew process? I am building my own picopak and hop-pak bins and would like to be able to add ingredients to them and start a brew cycle similar to when the machine pulls the info from the rfid tag. Is this possible? Can ask these questions on FB if that is a better place to do so.

That's the whole point of this 🧐.  Any recipes you created are retrieved when you do "Brew Pack" and then push in the rotary knob (since you're bypassing the RFID read)

ddrum2000, ahh, for some reason I thought the interface would behave/look differently. So, is there a way to use the recipe files (preprogrammed) I have loaded into the picobrew server via samba instead of the manual brew process? I am building my own picopak and hop-pak bins and would like to be able to add ingredients to them and start a brew cycle similar to when the machine pulls the info from the rfid tag. Is this possible? Can ask these questions on FB if that is a better place to do so.

ecraigsmit, when you have designs for the grain and hops bins ready, I would gladly purchase or build them.
Pete (or Ender I think ?), I was copying our conversation here so it was logged in github.

ddrum2000, will supply PDF's of the parts (1:1 scale) so they can be traced onto sheet polyethylene, cut out, bent and then stitched together once I finish my set and see if they assemble correctly. I ordered my material from McMaster-Carr and with shipping was a little expensive ($80 for enough material to make 2 sets). PDF's will be freely available, just like the server code (Thanks developers!).
Chiefwigms, concerning the recipes, doh! I stopped when the pico said "insert picopak" as I didn't have any. Didn't know I just had to press the damn button one more time. haha Looks like it's time to do a "water" trial run now.

All these "issues" are related to network drop outs and are out of our control.  I can't tell if you have the pi in a box or have something else obstructing the antenna, where relevant items are located (pi, picos, and router), distance between them, etc... These are all important factors which will affect operation and are out of our control.  If part of the sequence that any Pico devices do fail, them you'll see the results you are seeing.  These should all be lumped onder one "network" issue, but odds are no one will look at it because....   If you want a fool proof method, get a router which supports dd-wrt or one that can do dnsmasq and you won't have any of these problems - I never guaranteed it would work 💯 of the time with a pi  - it was just the quickest way for users without a computer background to come up to speed

ecraigsmit, when you have designs for the grain and hops bins ready, I would gladly purchase or build them.

Design files (flat-pattern pdf's) are on the Picobrewers Facebook files page. Post there also has material callouts required.  Just need to try a brew session with them now.

@chiefwigms Thanks for all the patience with me. My Pico wasn't even connecting to my home router so I rebooted the router and factory reset the pico as well as both ferms. Now at least the Pico and the Ferms connect both to my home internet as well as the Pi. I do wonder about the contents of the Ferm API calls. It seems like the Ferm is connected to the Pi but not sending any data to it. Do you know what triggers the Ferm into sending data?

@ddrum2000 currently the ferm doesn't have much UI on the offline server to "manually start a session". For the ferm to send data the "periodic phone home" API request needs a response from the server that toggles logging
We do that already for a default 14d from fermentation start.
I believe to start fermentation (aka wake up the Picoferm) you need to press one of the buttons. I haven't really used the Picoferm much yet so not 100% certain though I'd give that a try.

Thanks @tmack8001. I'm pretty familiar with the typical operation of the Ferm from using it on the original picobrew server. I guess what I'm not familiar with is how it should interact your server. A few observations that bothered me about how the ferm interacts with the RPi server:

I'm happy accept that the wifi chip in the Pi Zero W sucks when it is both in host and client mode simultaneously even though i've tried to be very about keeping the Pi and the Pico devices not too close together and not too far away, not too much metal to act as a Faraday cage, etc.. Sometimes when the Ferm connect to the RPi i get the red error light and other times I get the yellow in progress light. On occasion I get the green complete light but that doesn't really make sense to me. Then again I don't know what information trigger "fermentation complete".

I preface the next comment by saying I can read some code and get the gist but I am no good at writing code... I read through Python the code relating to the Ferm API calls and it seems that the Ferm should be sending time, temp, pressure, and voltage at regular intervals though many times, the fields for temp and pressure have no value in them.

I started fermentation around ~11 PM last night and something seems odd about how the data is transmitted. The ferm only seem to be transmitting exactly 12 data point in ~3-4 hour intervals. See the attached plot.

I guess for points 2 & 3, if this operation is totally normal for the Ferm then I'm happy to quiet down and accept that the produce is kind of "sketchy". Either way, if logs or other info from my end would be helpful I'm happy provide them.

@ddrum2000 no worries at all. Neither @chiefwigms nor I use the PicoFerms regularly in our brewing setup. The implementation as currently marked "beta" was provided to us by Brian Moineau.

The logging state is shared to the picoferm from this API (https://github.com/chiefwigms/picobrew_pico/blob/88c9663cd690dc3e6b3fd6628e23d8ff4a5070aa/app/main/routes_picoferm_api.py#L62-L73). There currently is very little logic on the picoferm state (in progress, complete, etc) if the PicoFerm asks for state we return "yes please send us data. However, upon receiving logging data the state is sent back to the picoferm. In this situation the server will say "thanks, you can stop" after 14 days (https://github.com/chiefwigms/picobrew_pico/blob/88c9663cd690dc3e6b3fd6628e23d8ff4a5070aa/app/main/routes_picoferm_api.py#L107-L110)

# Get State: /API/PicoFerm/getState?uid={UID}
#  Response: '#{0}#' where {0} : 2,4 = nothing to do, 10,0 = in progress/send data, 10,16 = in progress/error, 2,16 = complete/stop sending data

since the data is sent in the URL you could get some device server logs to see when the data is being transmitted as empty if ever unless that is what you have done. If that is the case then that explains the gaps as if there are no data points in data query parameter we don't parse that request and continue on until we receive another valid data point (https://github.com/chiefwigms/picobrew_pico/blob/88c9663cd690dc3e6b3fd6628e23d8ff4a5070aa/app/main/routes_picoferm_api.py#L95)

The picoferm decides when to transmit data the offline server doesn't have a way to ask to transmit more frequently or less frequently so no clue as to why only 12 points are transmitted and then it goes quiet for some time. Is the PicoFerm on battery? Are they fully charged?

Again sorry about your experience so far with the PicoFerm as I mentioned I've actually never used it for fermentation monitoring, but have use it for measuring the ambient temperature and "pressure" in my Brewhouse / basement but only left it on for a little while to verify things were logging successfully and that I could update its firmware with the config.yml features I've added.

So this all makes sense. The biggest confusion point for me is why the pico ferm returns the red error light most of the time. that could be a wifi issue but the devices are located 8-10 feet apart with only a a drywall wall in between.

Even when the yellow fermenting light shows up, the ferm rarely sends data the Pi. (Both of my ferms had no problem working with original server). I can see in the access log where the ferm connects to the Pi and sends data:
<IP_ADDRESS> - - [23/Sep/2020:10:05:34 -0400] "GET /API/PicoFerm/isRegistered?uid=5ccf7f5fa78a&token=3f63505e HTTP/1.0" 200 3 "-" "-" <IP_ADDRESS> - - [23/Sep/2020:10:05:34 -0400] "GET /API/PicoFerm/checkFirmware?uid=5ccf7f5fa78a&version=0.2.6 HTTP/1.0" 200 3 "-" "-" <IP_ADDRESS> - - [23/Sep/2020:10:05:34 -0400] "GET /API/PicoFerm/getState?uid=5ccf7f5fa78a HTTP/1.0" 200 6 "-" "-" <IP_ADDRESS> - - [23/Sep/2020:10:05:34 -0400] "GET /API/PicoFerm/logDataSet?uid=5ccf7f5fa78a&rate=5&voltage=0.01&data=[{\x22s1\x22:67.46,\x22s2\x22:0.00},{\x22s1\x22:67.46,\x22s2\x22:0.00},{\x22s1\x22:67.46,\x22s2\x22:0.00},{\x22s1\x22:67.47,\x22s2\x22:0.00},{\x22s1\x22:67.48,\x22s2\x22:0.00},{\x22s1\x22:67.48,\x22s2\x22:0.02},{\x22s1\x22:67.49,\x22s2\x22:0.12},{\x22s1\x22:67.50,\x22s2\x22:0.21},{\x22s1\x22:67.51,\x22s2\x22:0.32},{\x22s1\x22:67.52,\x22s2\x22:0.44},{\x22s1\x22:67.52,\x22s2\x22:0.56},{\x22s1\x22:67.53,\x22s2\x22:0.67}] HTTP/1.0" 200 6 "-" "-"

Great but this only happens rarely. Most of the time, only the first three lines occur:
<IP_ADDRESS> - - [23/Sep/2020:13:36:11 -0400] "GET /API/PicoFerm/isRegistered?uid=5ccf7f5fa78a&token=3f63505e HTTP/1.0" 200 3 "-" "-" <IP_ADDRESS> - - [23/Sep/2020:13:36:11 -0400] "GET /API/PicoFerm/checkFirmware?uid=5ccf7f5fa78a&version=0.2.6 HTTP/1.0" 200 3 "-" "-" <IP_ADDRESS> - - [23/Sep/2020:13:36:11 -0400] "GET /API/PicoFerm/getState?uid=5ccf7f5fa78a HTTP/1.0" 200 6 "-" "-"

I'm not running on battery, I'm using a wall cord so there is juice all of the time. The bigger issue may be going back to point 1 where more often then not, I get the red error light which I presume may be not connecting to the Pi's wifi fast enough but i really have no idea.

According to picobrew site, they both are running firmware version 0.2.6. In your server files there appears to be a version 0.2.7. Do you have any what the difference might be?

I went and clicked my status button yesterday afternoon and it did take a while for the first data point to show up, but once that started happening there have been regular intervals since.

The red status light does seem to be an issue. The yellow light means that fermentation is ongoing (aka the server told the device to log data) though may take time for the regular intervals to appear... Not sure why there as the server told the device to log data. Again as I don't have a Picoferm on my Picobrew account I can't confirm nor deny how the BrewHouse works myself.
The logs you sent show 0.2.6 and not 0.2.7 as the active firmware for the device. The server does have a newer "beta" firmware release, but I haven't done tear downs of the binary to figure out what was different and why Picobrew never released it to the entire community, I know a few in the FB group worked with support and got early releases of it for testing.

Interesting...
I do konw that wha I used the ferm with the official server, I had to click start in the brew house and then it took a ~few hours for the first data points to appear. If that the way the Pi server behaves then no big deal. I'm still getting this intermittent 12 data point thing (see below) that is hard to explain.

In the access log, I can see what the ferm sends to the server but is there a log to show what the server sends back to the ferm? I'd love to monitor to two way communication to see what's going on.
Also I wonder if something is going on funny with my ferms for whatever reason. It would be nice try another person's to see if there is something odd going on with mine or for someone with a functioning setup to try mine.

@ddrum2000 does your access log have the same periodic 12 data points with hours or nothing or is there still data being reported in that time just not showing up in the graphs? Also this is for both the live graph? Simple question (I'm sure you did this) have you refreshed the page?

First, yes I refreshed the page.
Second, the access logs...

The access logs mirror the data plot for when data is transmitted. However what you will see in the access log is a number of times, the ferm talks the the Pi  but no data gets transmitted. This occurs when the yellow in progress light blinks. Many other times the red error light blinks.
It seems sort of random when the ferm chooses to transmit data to the Pi. Having said that when it does transmit, it always seems to be 12 data points. I suspect maybe that's the limit of what is stored in internal memory.
I've attached two logs to illustrate the example. The IP address of interest is <IP_ADDRESS>.

picobrew.access.log.txt

9/24 00:00 -> present

picobrew.access.log.1.txt

9/23 00:00 -> 9/24 00:00

Hrm yeah those access logs were what I thought they would be.
9/24 00:00 -> present ==> 2 requests to set data:

24/Sep/2020:09:32:55 --- with 12 data points included
24/Sep/2020:11:33:56 --- with 12 data points included

Not sure, but when I look at my raspberrypi and view the access logs I see the same pattern to mine. The rate is "5" meaning a measurement every 5 minutes and included in the log is a set of 12 meaning here are the measurements from the past hour of data logging. Not sure why mine (within 3-5 ft of connected AP) is reporting consistently once every hour. Literally every hour there is the following requests made from the PicoFerm:

/API/PicoFerm/isRegistered (checking if the ferm is attached to a user... we no-opt this locally)
/API/PicoFerm/checkFirmware (checking if there is a new released firmware... you can set minimum version in config.yml)
/API/PicoFerm/getState (checking if the ferm is marked as monitoring an active fermentation... this is defaulted to #10,0#' (yes; please log data)

/API/PicoFerm/logDataSet (dumping 12 data points measured at 5 min intervals)

Only things I can think of is that WiFi connectivity is spotty so it is dropping on and off network or the PicoFerm is bad somehow. I do see that both mine and your PicoFerm are running on a 0.2.6 release so that 0.2.7 is likely not going to change much... but feel free to try it out can always downgrade later.

I do konw that wha I used the ferm with the official server, I had to click start in the brew house and then it took a ~few hours for the first data points to appear. If that the way the Pi server behaves then no big deal. I'm still getting this intermittent 12 data point thing (see below) that is hard to explain.

Regarding "starting fermentation" yes it takes at least an hour from hitting "status/on" and seeing data populate. Maybe more than an hour if WiFi connection is spotty or for other reasons the PicoFerm isn't reporting data consistently. Checking out the manual here, https://picobrewcontent.blob.core.windows.net/content/picoferm/PicoFerm_Manual.pdf, it claims that "Note: if you see a flashing red light, this means that there is an error with your fermentation. Log in to your BrewHouse to see error details.".... I'm wondering what that means as the access logs don't show any indication to me that an error occurred. Wondering if that red light could mean that there was an issue communicating to "picobrew.com" (aka the WiFi issue as earlier mentioned)? If the server was incorrectly responding to the device it would have shown in the access log unless the request didn't make it to the server itself.

Thanks for roughly validating my analysis. I moved my Ferm a little closer to the Pi last night. Now it's about 3 ft away with a clear line of sight. This has not changed the rate that data is sent back to the Pi server.
At times I can press the on/status button and sometimes I get the red error light and other times the yellow in progress light. I think my bigger concern is that when I do get the the yellow in progress light AND I can see in the access log that the ferm talked to the server, why isn't the ferm sending the saved data back to the Pi? Even if it isn't ideal, if for instance I only got 1 hour worth of data every 3 or 6 hours that would be fine. Clearly that is not what is happening...

I'm not sure what the PicoFerm firmware is doing. Never looked under the hood before.
From the server side everything is operating as expected though 🤷♂

@ddrum2000 did you check to see if the error log from nginx had anything in it?

So my ferm just did the usual connect to the Pi with with yellow light but no data upload. Here are the relevent line from access.log:
<IP_ADDRESS> - - [25/Sep/2020:17:23:36 -0400] "GET /API/PicoFerm/isRegistered?uid=5ccf7f5fa78a&token=3f63505e HTTP/1.0" 200 3 "-" "-" <IP_ADDRESS> - - [25/Sep/2020:17:23:36 -0400] "GET /API/PicoFerm/checkFirmware?uid=5ccf7f5fa78a&version=0.2.6 HTTP/1.0" 200 3 "-" "-" <IP_ADDRESS> - - [25/Sep/2020:17:23:36 -0400] "GET /API/PicoFerm/getState?uid=5ccf7f5fa78a HTTP/1.0" 200 6 "-" "-"
And from error.log:
2020/09/25 17:23:36 [error] 389#389: *3139 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: www.picobrew.com, request: "GET /API/PicoFerm/getState?uid=5ccf7f5fa78a HTTP/1.0", upstream: "http://[::1]:8080/API/PicoFerm/getState?uid=5ccf7f5fa78a", host: "www.picobrew.com"
The other instances where no data is uploaded from the ferm have the same line in the error log.

*3139 connect() failed ah now we are getting somewhere! Thanks for that. Looks to be a connection establishment error between nginx (reverse proxy offering http and https) and python+flask (API implementation and web interface).
I'll do some debugging on my side as I haven't seen these errors myself. I got a few rpi devices laying around I can try to do vanilla installs on as well.
Anyways thank you this is good progress in attempting to find the issue. Wondering if every hour when there are no logs if a similar connect failed error appears in the nginx logs?
Thanks for sticking with it. Not sure when I'll have a fix for this issue, but I will definitely keep you posted. Appreciate the logs and detailed analysis and debugging!

Thank you! I appreciate the hard work that you and Ender have put in but I was getting frustrated by the only response being "its a wifi issue".
I am getting similar issues to what you describe in the error log whenever the ferm connects to the Pi but does not necessarily upload data (yellow led). I think the red led is a wifi error where the ferm never actually connects to the Pi. My guess is that is takes much longer to make the connection to the Pi's access point as compared to my router. I really have no idea how to fix that but anecdotally I have observed similar behavior in comparing the connection times for my laptop between the Pi's access point and the my router. Like I said previously, if every 3rd, 4th, or 6th hour I get an hour's worth of data from the ferm, I'm not really complaining.
I've attached my most recent access and error log files which should confirm my statements. I'm happy to provide any other data that would be helpful for troubleshooting this issue. The only changes I've made from stock image (0.0.1-beta3) that you have provided are:

I created a username separate from pi. I did make this a sudo user.
I changed time zone so that the console would display Eastern Time.
I purchased Adafruit mini PiTFT (https://www.adafruit.com/product/4393). I'm running it in console mode and I know that the script had to install a kernel module to get the display to work. The instructions and link to the script is located here: https://learn.adafruit.com/adafruit-mini-pitft-135x240-color-tft-add-on-for-raspberry-pi/kernel-module-install.
Yes I did purchase a lexan case from Adafruit (https://www.adafruit.com/product/3005) but given that it's a pretty thin dielectric, I'd be really surprised if that was causing the wifi issue.  I'm not necessarily an expert but I know enough to be dangerous).

picobrew.access.log
picobrew.error.log
Really, thanks again I appreciate it.

If you're in facebook send me a message after my post in a few minutes on the picobrewers group

I'll keep my eyes out for it tonight or tomorrow. We've talked on facebook before. Thanks.

I'll review the access and error logs to see if there is any pattern seen as well as go down the route of debugging the connect failed error found in the error logs.
Thanks again! 🍻

Like I said, let me know if I can help in any way.

Try https://github.com/chiefwigms/picobrew_pico/releases/tag/v0.0.1-beta4

I'll give it a whirl at lunch today and get back to you

Ok so here are the updates after about 34 hours on beta 4:

I've hooked up my second pico ferm to use it as a data logger to help troubleshoot
Data is transmitted in periodic intervals to the RPi but the error LED still appears pretty regularly
I'm seeing similar symptoms as before except that I'm not seeing the PicoFerms in the error log this time. By this I mean that the Ferms do occasionally connect to the RPi but the logged data does not seem to be transmitted on a regular basis to the RPi. (Please the logs attached below)

Here are the relevant plots and logs:

<IP_ADDRESS> - Currently Fermenting

<IP_ADDRESS> - Data Logger

picobrew.access.log
picobrew.error.log
Any thoughts?

No changes since the list update. I noticed that there is new firmware for the brcm80211. The new version is 20190114-1+rpt9. Previously, version rpt8 was the problematic version. Does anyone know if rpt9 fixes the problems in rpt8?

@ddrum2000 are you still not able to get manual brews on your C? I don't have a C, been looking out to rescuing one from the dump to test with... My S/Pro thingy works just fine it appears, I ran a test with water.

@ddrum2000 are you still not able to get manual brews on your C? I don't have a C, been looking out to rescuing one from the dump to test with... My S/Pro thingy works just fine it appears, I ran a test with water.

@tmack8001 to be honest I've been continuing to use the cloud server since the new owners "committed" to keeping it online. I just got a Z so i'll be setting that up in the next few days. Come to think of it, I was also having a bunch of file system errors on my RPi. I replaced the SD card and that seemed to fix a number of issues.
I can't remember, do you live in the Boston area? If so, you can borrow it to experiment. I'm planning to give my C to a friend  but I can delay that if it helps. I can run test with water too. Can you send me your recipe steps and I'll try it out?

@tmack8001 to be honest I've been continuing to use the cloud server since the new owners "committed" to keeping it online. I just got a Z so i'll be setting that up in the next few days. Come to think of it, I was also having a bunch of file system errors on my RPi. I replaced the SD card and that seemed to fix a number of issues.
I can't remember, do you live in the Boston area? If so, you can borrow it to experiment. I'm planning to give my C to a friend  but I can delay that if it helps. I can run test with water too. Can you send me your recipe steps and I'll try it out?

Come to think of it, I was also having a bunch of file system errors on my RPi. I replaced the SD card and that seemed to fix a number of issues.

If the SD card becomes corrupted (can happen various ways but most notably by hard power downs) this can happen.

Boston area

Yup that is me. I have a S I dug out of storage (leaks like crazy...) someone gave it to me instead of tossing in the trash and ran a manual session just fine. Maybe there is a small detail in the firmware that is different with the Cs other than the size resolution (same screen just partially hidden by the cheap plastic shell)?

Come to think of it, I was also having a bunch of file system errors on my RPi. I replaced the SD card and that seemed to fix a number of issues.

If the SD card becomes corrupted (can happen various ways but most notably by hard power downs) this can happen.

Boston area

Yup that is me. I have a S I dug out of storage (leaks like crazy...) someone gave it to me instead of tossing in the trash and ran a manual session just fine. Maybe there is a small detail in the firmware that is different with the Cs other than the size resolution (same screen just partially hidden by the cheap plastic shell)?

Where in Boston, I'm in Charlestown.
I can run a water only recipe to do you have a suggestion on the recipe structure to try it out. Alternatively, I can drop it off to you for a few days.

Where in Boston, I'm in Charlestown.
I can run a water only recipe to do you have a suggestion on the recipe structure to try it out.
It might not be self discoverable when if you are wanting to start a brew from a recipe stored on the server you need to brew as if you were brewing a picopak.

@ddrum2000 wasn't this issue about not being able to start "manual brew" and not for a "recipe" driven picopak brew?
It might not be self discoverable when if you are wanting to start a brew from a recipe stored on the server you need to brew as if you were brewing a picopak.

I'm out in Newton area. You can PM me on Facebook if you use that (check for Ender)

I'm out in Newton area. You can PM me on Facebook if you use that (check for Ender)

@tmack8001 to be honest I've been continuing to use the cloud server since the new owners "committed" to keeping it online.

Sure makes sense to me. From public knowledge (not like they communicate often with us...) there doesn't seem to be a "rush" to abandon their servers. Though that said the Pak line is completely gone so if you want to automate any part of your brew (multi mash, etc) then you are SOL unless you go with a server like this one.

@tmack8001 to be honest I've been continuing to use the cloud server since the new owners "committed" to keeping it online.

Sure makes sense to me. From public knowledge (not like they communicate often with us...) there doesn't seem to be a "rush" to abandon their servers.

So I'll try the following and let me know if you think it will do the job. I'll try two different "water" brews:

A manual brew with a few different temperature steps
An automated brew simulating a few different mash steps and trying all of the adjuncts.

Would that cover it or are there any other commands that you think I should try?

So I'll try the following and let me know if you think it will do the job. I'll try two different "water" brews:

A manual brew with a few different temperature steps
An automated brew simulating a few different mash steps and trying all of the adjuncts.

Would that cover it or are there any other commands that you think I should try?

Nah that would be great.

Nah that would be great.

Quick question, what is the max temp of the Pico C/Pro in automated mode?
On Fri, Jan 8, 2021 at 1:43 PM Trevor Mack<EMAIL_ADDRESS>wrote:

Nah that would be great.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chiefwigms/picobrew_pico/issues/108#issuecomment-756930924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGZHUITCLVS2HEHWPHDRVLSY5G65ANCNFSM4Q6WNMWA
.

Quick question, what is the max temp of the Pico C/Pro in automated mode?
On Fri, Jan 8, 2021 at 1:43 PM Trevor Mack<EMAIL_ADDRESS>wrote:

Nah that would be great.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chiefwigms/picobrew_pico/issues/108#issuecomment-756930924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGZHUITCLVS2HEHWPHDRVLSY5G65ANCNFSM4Q6WNMWA
.

208 from memory is that max

208 from memory is that max

Sounds good. I should have test data to post tonight
On Sun, Jan 10, 2021 at 4:00 PM Trevor Mack<EMAIL_ADDRESS>wrote:

208 from memory is that max
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chiefwigms/picobrew_pico/issues/108#issuecomment-757543304,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGZHUI5OGKHJOEKCTXO3BDSZIIO7ANCNFSM4Q6WNMWA
.

Sounds good. I should have test data to post tonight
On Sun, Jan 10, 2021 at 4:00 PM Trevor Mack<EMAIL_ADDRESS>wrote:

208 from memory is that max
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chiefwigms/picobrew_pico/issues/108#issuecomment-757543304,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGZHUI5OGKHJOEKCTXO3BDSZIIO7ANCNFSM4Q6WNMWA
.

System

Pi Zero W
Updated to beta5.
Updated all available packages using sudo apt update and sudo apt upgrade
I have the a small TFT display and installed a kernel module for display support. Info on the display can be found here: Adafruit Mini PiTFT - 135x240 Color TFT Add-on for Raspberry Pi

Test 1 - Manual Brew

102F - 5 min
152F - 5 min
175F - 5 min
203F - 5 min

Worked well. The only issue was that first time I tried to initiate the Manual Brew command there was an error connecting to the server. I tried it again a second time initiate the manual brew and it worked fine. The data plot is sown below.

Test 2 - Automated "PicopaK" Brew
The recipe I used for the water test is shown below:

This too worked fine. I had a similar problem when i clicked "Brew Pickpak" the C couldn't fine the receipe. Adfter trying it a second time it found the recipe. Here is the data plot

I did a few weird things while running the program but I think the data logging worked fine.
Please let me know if you'd like any other info. I plan to pack this up and ship it to a friend later this week after I setup my new Z :)

System

Pi Zero W
Updated to beta5.
Updated all available packages using sudo apt update and sudo apt upgrade
I have the a small TFT display and installed a kernel module for display support. Info on the display can be found here: Adafruit Mini PiTFT - 135x240 Color TFT Add-on for Raspberry Pi

Test 1 - Manual Brew

102F - 5 min
152F - 5 min
175F - 5 min
203F - 5 min

Worked well. The only issue was that first time I tried to initiate the Manual Brew command there was an error connecting to the server. I tried it again a second time initiate the manual brew and it worked fine. The data plot is sown below.

Test 2 - Automated "PicopaK" Brew
The recipe I used for the water test is shown below:

This too worked fine. I had a similar problem when i clicked "Brew Pickpak" the C couldn't fine the receipe. Adfter trying it a second time it found the recipe. Here is the data plot

I did a few weird things while running the program but I think the data logging worked fine.
Please let me know if you'd like any other info. I plan to pack this up and ship it to a friend later this week after I setup my new Z :)

Yeah looks and sounds like there is still some glitch in the internal networking. This impacts the frequency of data points and the occasional missed request (why you had to try to start twice for instance).

Yeah looks and sounds like there is still some glitch in the internal networking. This impacts the frequency of data points and the occasional missed request (why you had to try to start twice for instance).

i'm going to close, since the networking issue is only related to Pi's


IPFS deps are being linked into all noms clients

Rafaels-MacBook-Pro-2:csv-export rafael$ git reset --hard 1a7e006862eb1e16cfd9901f0c6b0204100b09a1
HEAD is now at 1a7e0068 Landing beginning of IPFS experiment on trunk (#3625)
Rafaels-MacBook-Pro-2:csv-export rafael$ go build
Rafaels-MacBook-Pro-2:csv-export rafael$ ls -la csv-export
-rwxr-xr-x  1 rafael  staff  33759076 Sep 15 05:36 csv-export
Rafaels-MacBook-Pro-2:csv-export rafael$ git reset --hard 8b5cd66cceb8d1204dd55b428c36b108e779b93e
HEAD is now at 8b5cd66c NBS: Expose hashes request builder for use in tests (#3630)
Rafaels-MacBook-Pro-2:csv-export rafael$ go build
Rafaels-MacBook-Pro-2:csv-export rafael$ ls -la csv-export
-rwxr-xr-x  1 rafael  staff  12743332 Sep 15 05:37 csv-export

e.g. nearly tripped the size of the csv-export binary

I presume this is for spec parsing, and I'm not sure you can do much about that:
https://github.com/attic-labs/noms/blob/1e6a54d89f91061690ce6d5c153cdf69db72176f/go/spec/spec.go#L185
@willhite
@arv mentioned something in slack about this a while back too

We could add some api that allowed clients to add protocols dynamically and we could use that for our IPFS chat application. The nice thing is that noms and all of other utils/samples would be unencumbered by IPFS libraries, the downside is that they wouldn't  work with IPFS-based databases. :-(

I think it is fine to make it pluggable. Just somebody needs to design the
contract with spec package.
On Thu, Sep 21, 2017 at 8:14 PM, Dan Willhite<EMAIL_ADDRESS>wrote:

We could add some api that allowed clients to add protocols dynamically
and we could use that for our IPFS chat application. The nice thing is that
noms and all of other utils/samples would be unencumbered by IPFS
libraries, the downside is that they wouldn't work with IPFS-based
databases. :-(
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/attic-labs/noms/issues/3709#issuecomment-331339233,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAE6BIt08orsaDjmJfBbgaVqLnXce8Prks5skyYrgaJpZM4PY6cR
.


Remove events fetching error temporary fix

Time spent on this PR: 0.5
Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Resolves #
What is the new behavior?

Other information

tested against latest version of katana and madara on main and works with the events now ✅


create ioctl on diskimage  failed: Device or resource busy

Issue Summary
I'm experiencing two errors when attempting to build the Linux vanilla sd_card.img using colcon on my workstation. These errors occur under different conditions:

First Execution after Booting:

Error message: mount: /tmp/sdcard_img_p1: overlapping loop device exists for /home/claudio/krs_ws/acceleration/firmware/kv260/sd_card.img.
Outcome: The sd_card.img is generated correctly, but this error appears.

Subsequent Executions:

Error message: device-mapper: create ioctl on diskimage failed: Device or resource busy. Command failed.
Outcome: The command fails to create the sd_card.img on subsequent attempts after the initial successful build.

Environment
Host OS: Ubuntu 22.04 (on a partitioned SSD)
Working Directory: ~/krs_ws
Command: colcon acceleration linux vanilla --install-dir install-kr260
Using: KRS

First Error:

Second Error:

More info on my env:
 ROS2` humble
 rmw_cyclonedds as DDS

I have followed the KRS setup tutorial and the KR260 workaround.


Disable lines number

I would like to know if it is possible to disable the lines in a specific example

Yup! You can turn them off per block by passing {"lineNumbers": false} as an option.
See https://torchlight.dev/docs/options/line-numbers and https://torchlight.dev/docs/options#setting-options-per-block

Amazing. Thanks


If there is not a state with '/' defined, infinite loop

http://plnkr.co/edit/cH0LiMq29CIyzfZzHYva?p=preview
Seems like if there is not a state with a url of '/' then the states will go in an infinite loop.

I did some testing, and it seems that the / state cannot be an abstract parent state.
http://plnkr.co/edit/0wnnfKpS9l11i4azravK

App Bootstraps; url is ""
-> check rules against ""; only otherwise('/home') matches
-> $location.path('/home')
-> check rules against "/home"; match 'home' and transitionTo('home')  (Transition 1)
-> Transition 1) $stateChangeStart.preventDefault()
-> transitionTo('login') (Transition 2)
-> Transition 2) $stateChangeStart, not prevented; goes to async portion
-> Stack popped until we get back to...
-> Transition 1) $stateChangeStart.defaultPrevented === true, so call $urlRouter.update()
-> $location.path() is reset to the last know url, ""
cycle starts

I can't seem to create a failing unit test.  Perhaps this is due to the mocks behaving differently.
Also interesting: the plunker works if you downgrade angular to 1.3.3 or earlier.  1.3.4 and above exhibit the infinite digest.

I'm glad to hear I was of help @christopherthielen. Great job on the fix!


Validation tool should detect RequestedHeight tag should come after label tag and before SourceLocation tag

Github issue - https://github.com/OfficeDev/office-js/issues/1074
RequestedHeight tag should come after label tag and before SourceLocation tag must appear in the manifest validation tool

office-toolbox is no longer used for validation. The office-addin-manifest "validate" command is used instead. Use npx office-addin-manifest validate <manifest> to do this validation.
This was just updated yesterday to use a different validation service. Please see whether this is still an issue. If it is, please raise the issue in the https://github.com/OfficeDev/Office-Addin-Scripts repository.


Add custom className support

Reasolves #1.

Add className as a propType (to show intent)
Add react-gravatar as a defaultProp
Add documentation to the README

I didn't run your Makefile, I figured you'd want to handle that.
Let me know if this is cool / needs anything else - thanks for the useful component!

Thanks!

Thanks for the PR! Pushed out a 1.1 release. Enjoy :)


feat: Added Polygon zkEVM Mainnet

Description
Added new network and rpc credentials for Polygon zkEVM Mainnet
BREAKING CHANGE: No
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address:
codingwithmanny.eth

@tmm wanted to ask if this should be a minor or patch for the changeset?

Thx @jxom 🙏

9de63cd59f8062e9a2e16ca5fe32632123eeecf9


Numeric JSONRPC Request ID

workaround for ethereum/go-ethereum#295

not needed anymore, @tgerring already fixed it in ethereum/go-ethereum#295


train  only class

hi ,thank you very much. Do you used training only class using retina-head?

We have not tried it before. Maybe related to #275

Solved in the PR.


Start out using mantle

Having vollowed the introductory steps I have a vagrant vm at https://<IP_ADDRESS>/
However I am unable to login. My admin credentials do not seem to work. Which key on the security.yml file is the correct one?

@geoHeil What are you unable to log in to? To ssh into your machine try vagrant ssh. To login to the administrative interfaces of Consul, etc. use the value at the nginx_admin_password key in security.yml.

If none of that works for you, please post back with where you're unable to log in to, and what exactly happens when you aren't able to.

Hi,
I try to login at the http-basic auth at <IP_ADDRESS>:80with credentials like u: georg p: georg as specified by nginx_admin_password however this seems to be wrong. According to vagrant port only port 22 is forwared to the local machine.
to follow along:
hronos_http_credentials: admin:georg
chronos_principal: chronos
chronos_secret: TaK0ky7Uiii7h0Viqw8Lxb/aTJJCMk03mZ/qhe0LE4BA
consul_acl_agent_token: b86f84c7-5ee8-4d73-a598-ee7279c3f68a
consul_acl_master_token: 088b0ae3-fec4-4668-84f8-055be88c4310
consul_default_acl_policy: allow
consul_gossip_key: +1LrTyWACg5ZWzaLklSPPg==
do_chronos_auth: true
do_chronos_iptables: true
do_chronos_ssl: true
do_consul_auth: true
do_consul_ssl: true
do_mantl_api_auth: true
do_mantlui_auth: true
do_mantlui_ssl: true
do_marathon_auth: true
do_marathon_iptables: true
do_marathon_ssl: true
do_mesos_auth: true
do_mesos_follower_auth: true
do_mesos_framework_auth: true
do_mesos_iptables: true
do_mesos_ssl: true
do_private_docker_registry: false
mantl_api_principal: mantl-api
mantl_api_secret: knBsBAU5NusDVEsuz63VXVq0PPoMOW/DRAVMMuN+OOTu
marathon_http_credentials: admin:georg
marathon_principal: marathon
marathon_secret: eAgcYA1qNZv2PnG9+U0bu/RkGldZ1cWlvuz5V5vskIVl
mesos_credentials:
- {principal: marathon, secret: eAgcYA1qNZv2PnG9+U0bu/RkGldZ1cWlvuz5V5vskIVl}
- {principal: chronos, secret: TaK0ky7Uiii7h0Viqw8Lxb/aTJJCMk03mZ/qhe0LE4BA}
- {principal: mantl-api, secret: knBsBAU5NusDVEsuz63VXVq0PPoMOW/DRAVMMuN+OOTu}
mesos_follower_principal: follower
mesos_follower_secret: aBulwNKVOvoi18kv0/JZYx3jAYR0ba+0xPKUDqdRRxMz
nginx_admin_password: georg
security_enabled: true
zk_chronos_user: chronos
zk_chronos_user_secret: pfA4gnj8M5pGQrLT
zk_chronos_user_secret_digest: sOQJMs0ofkAuZGs00gFeE2mQm7o=
zk_marathon_user: marathon
zk_marathon_user_secret: gKOce2AgA3TwRaZs
zk_marathon_user_secret_digest: boCEgoZ87n4gXGFpjGNWKyhUGNI=
zk_mesos_user: mesos
zk_mesos_user_secret: VnpV6TNjBPhKEHRX
zk_mesos_user_secret_digest: oAgt1eHT7VTJz3CgWReVHST6o/8=
zk_super_user: super
zk_super_user_secret: 9ksB1NW7An3txc3fm86ZaF7fvec0CozVtwuOWlqJpdlv

Can you try logging in as admin:georg? The default user is always admin

for user: admin and password: admin:georg I unfortunately only receive an error 401 - no auth

Sorry, I meant just using georg as a password.

Thank you very much.


Allow arbitrary HTTP headers to be added to requests

Adds a single function, with_additional_headers/1 that adds whatever heads the caller wants to the base request.
This is useful for e.g. using portkey's LLM gateway.

@kofron Have you tested this against portkey?
It might be a little more expressive for the additional headers to be a key-value map, rather than a header string.
I think we should also have an example in the user guide showing the exact call for the portkey sample.
You'll also have to run 'mix format' for the CI tests to pass.

@kofron Have you tested this against portkey?

Sure have!  Works a charm.

It might be a little more expressive for the additional headers to be a key-value map, rather than a header string.

I like this suggestion, done.

I think we should also have an example in the user guide showing the exact call for the portkey sample.

Sounds good, happy to do that - how does one update the user guide.  FWIW, it looks like this:
OpenaiEx.new(open_ai_api_key)
|> OpenaiEx.with_base_url("https://api.portkey.ai/v1")
|> OpenaiEx.with_additional_headers(%{"x-portkey-api-key"=>portkey_api_key, "x-portkey-provider"=>"openai"})

You'll also have to run 'mix format' for the CI tests to pass.

Done.

@restlessronin should be all set

@kofron Merged. Thanks much 🙏🏾🙏🏾 for the PR.

@restlessronin awesome, thanks for the library!
What's the release cycle like for this hitting hex.pm?

@kofron I just published v0.8.4 on hex.pm with the latest changes.


[INFINITY-3133] Added missing Kerberos auth for readiness check

Missed this the first time around - the kerberos tests don't do a restart/replace of the journal nodes so the readiness check doesn't actually succeed after the first time it passes.

Sounds like there should be a restart integration test in the Kerberos suite then, no?

Yup, will add

@benclarkwood added restart integration test


Optimize DB

https://github.com/rancher/rancher/issues/8716

We should consider profiling the improvement to DBs hit as a result of this PR

Very stale. Closing. Thanks! Please open a new PR if there is still a relevant change.


Where in the world is the def file

As always, just a little information, but not the full answer.
Where does one find the .def file? How is it created?

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

ID: 142bb8a9-d18a-1e94-653d-c5d4c8a64ecc
Version Independent ID: 40d6607d-8df0-1185-dc0a-fac2c3d4fab5
Content: Linker Tools Warning LNK4070
Content Source: docs/error-messages/tool-errors/linker-tools-warning-lnk4070.md
Product: visual-cpp
Technology: cpp-diagnostics
GitHub Login: @corob-msft
Microsoft Alias: corob

@ianclarke1422
If the linker created a .DEF file or a .EXP file, I expect it should be in the output directory with the object files. That directory depends on your build configuration.


Add capability to pass fixed hostname

Hello,
Currently the tailscale agent would assign the hostname based on the real hostname of the machine. Often this is undesirable, and we'd like to have a fixed value of this hostname. Hence, I'm proposing that we have the capability to pass a custom hostname in the input.

The request check failed because this PR originated from a fork, so it doesn't have access to the authkey secret used by the runner. It looks fine to me, if the check fails after merging to main then I'll fix it.


allporncomic.com not ripping

Ripme version: <IP_ADDRESS>
Java version:  v8 update311
Operating system: Win10 Pro 21H1

Exact URL you were trying to rip when the problem occurred:
https://allporncomic.com/porncomic/the-simpsons-the-simpsons-croc/1-the-simpsons/
Please include any additional information about how to reproduce the problem:

Expected Behavior
Rip complete, saved to /Volumes/SAMSUNG/Com3x/rips/Tekuho/allporncomic_the-simpsons-the-simpsons-croc_1-the-simpsons
Actual Behavior
Failed to load https://allporncomic.com/porncomic/the-simpsons-the-simpsons-croc/1-the-simpsons: Status Code 403. You might be able to circumvent this error by setting cookies for this domain

Ripme version: <IP_ADDRESS>
Java version: v8 update331
Operating system: macOS 10.13.6
I have the same issue on High Sierra with almost every website. The only site that works is reddit.
It use to work fine a few years ago, and with this same macOS.
Any solutions?


Fatal exception when syncing resource with default of empty string and allow null

How to reproduce
To reproduce in any resource have a default of an empty string on a property as well as an allow key with null.
This is an example:
email: jsonApi.Joi.string().email()
      .default('')
      .allow(null)

If you create the resource when sync is executed it crashes with the following partial stack trace:
Uncaught TypeError: Cannot read property 'id' of null
      at Resource._construct (lib/Resource.js:19:20)
      at lib/Resource.js:286:10
      at lib/Transport.js:94:12

This error originates from here:
Resource.prototype.sync = Promise.denodeify(function(callback) {
  var self = this;
  var target = self._client._update;
  if (!self._getBase().id) {
    target = self._client._remoteCreate;
  }

  target.call(self._client, self, function(err, rawResponse, rawResource) {
    if (err) return callback(err);
    self._construct(rawResource, self._client);

The job of Resource.sync is to either update the resource, or create it if it doesn't exist. Following an update, the remote response should contain the newly modified resource, which we use to synchronise the local Resource.
I'd be interested to know how we're getting no error in combination with a null data payload. I think the only course of action if this scenario is to throw an Error - I'm pretty sure this behaviour isn't allowed in the specification?

The following DEBUG output should help to clarify the sequence of events (this was obtained by tweaking the people resource definition in the jsonapi-server examples with the above mentioned changes):
  jsonApi:requestCounter 0 +0ms POST /rest/people
  jsonApi:validation:input<EMAIL_ADDRESS>+3ms
  jsonApi:handler:create {"type":"people","data":{"id":null,"type":"people","attributes":{"email":"john.doe@example.com"},"relationships":{}}} +1ms<EMAIL_ADDRESS>  jsonApi:handler:find {"type":"people","data":{"id":null,"type":"people","attributes":{"email":"john.doe@example.com"},"relationships":{}},"id":"79c7eee6-0078-472e-b5c7-08d13b92b8ca"} +0ms<EMAIL_ADDRESS>  jsonApi:validation:output<EMAIL_ADDRESS>+1ms
  jsonApi:requestCounter 1 +9ms GET /rest/people/79c7eee6-0078-472e-b5c7-08d13b92b8ca
  jsonApi:handler:find {"type":"people","id":"79c7eee6-0078-472e-b5c7-08d13b92b8ca"} +1ms<EMAIL_ADDRESS>  jsonApi:validation:output<EMAIL_ADDRESS>+0ms
      ✓ creates a resource (42ms)
  jsonApi:requestCounter 2 +5ms POST /rest/people
  jsonApi:validation:input {"id":"be2d1e75-28a2-4895-aa0a-653d3d803f98","type":"people"} +1ms
  jsonApi:handler:create {"type":"people","data":{"id":null,"type":"people","attributes":{},"relationships":{}}} +0ms [null,{"id":"be2d1e75-28a2-4895-aa0a-653d3d803f98","type":"people","email":""}]
  jsonApi:handler:find {"type":"people","data":{"id":null,"type":"people","attributes":{},"relationships":{}},"id":"be2d1e75-28a2-4895-aa0a-653d3d803f98"} +0ms [null,{"id":"be2d1e75-28a2-4895-aa0a-653d3d803f98","type":"people","email":""}]
  jsonApi:validation:output {"id":"be2d1e75-28a2-4895-aa0a-653d3d803f98","type":"people","email":""} +0ms
  jsonApi:validation:error child "email" fails because ["email" is not allowed to be empty] +1ms {"id":"be2d1e75-28a2-4895-aa0a-653d3d803f98","type":"people","email":""}

Ok. In this instance, the Joi schema is invalid. a "" value is not accepted by the Joi.string() validator.
> var t = Joi.string().allow(null).default("");
undefined
> Joi.validate("test", t, function() { console.log(arguments) });
{ '0': null, '1': 'test' }
undefined
> Joi.validate(undefined, t, function() { console.log(arguments) });
{ '0': null, '1': '' }
undefined
> Joi.validate('', t, function() { console.log(arguments) });
{ '0':
   { [ValidationError: "value" is not allowed to be empty]
     name: 'ValidationError',
     details: [ [Object] ],
     _object: '',
     annotate: [Function] },
  '1': '' }

"test" validates fine.
undefined get changed to the default of ""
"" is an invalid value.

The default you've chosen doesn't match your validation :(

I have encountered this type of error. It crashed my client when I try to sync the resource with ' '. How to fix this?


feat: docs for api endpoints to generate openapi specification

What problem does this PR solve?
Added openapi specification for API routes. This creates swagger UI similar to FastAPI to better use the API.
Using python package flasgger
Type of change

[x] New Feature (non-breaking change which adds functionality)

Not all routes are included since this is a work in progress.
Docs can be accessed on: {host}:{port}/apidocs

Appreciate your contribution.
There's conflicts, please resolve them.


Add tensorboard, nvdashboard, conda-store-ui jlab extensions

Reference Issues or PRs

What does this implement/fix?
Add the following jupyter extensions to the JupyterLab image:

https://pypi.org/project/jupyter-tensorboard/
https://github.com/rapidsai/jupyterlab-nvdashboard

Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Documentation

Access-centered content checklist
Text styling

[ ] The content is written with plain language (where relevant).
[ ] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
[ ] All links describe where they link to (for example, check the Nebari website).
[ ] This content adheres to the Nebari style guides.

Non-text content

[ ] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
[ ] If there are emojis, there are not more than three in a row.
[ ] Don't use flashing GIFs or videos.
[ ] If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

@iameskild can we do a build from this branch instead of using main? I would like to avoid one of those extension-breaking things if possible.


Strange output?

For the most part this library works great! But I'm encountering some strange things when iterating over a parsed CSV in my unit tests. Sometimes the parsing seems to fail and the values are populated with goggly goop like this column value of \0\0\0èä\u{05}\0\0\0\0\0\0\0\0\0\0\0\0\0+\u{07}\u{01}\0\0\0Ø.
Not sure if anyone else has encounter this, I haven't been able to figure out any sort of patter as to why it is happening.

Getting the same thing.

@yaslab any ideas what could be causing this?

@kgn I don't know the cause yet.
Although it may not be related to this issue, I think that it may not be good to have some functions implemented in a struct. I'm currently working on replacing struct with class.
I will release this weekend so please try it.

@kgn I released version 2.0.0 in June. As it may have been fixed, please try out the new version.


Disable automatic version check

Hello! I'm using Boats to assemble and build the OpenAPI spec for an application I'm developing.
Boats gets invoked every time the application is compiled, which is done automatically in a CI pipeline and when building the Docker image. Every now and then the build is broken by the following message produced by Boats:
Checking version with npm-tool-version-check from: https://raw.githubusercontent.com/johndcarmichael/boats/master/package.json
WARNING: The version of BOATS you are running, 1.20.4, is OUTDATED!
THERE IS A BETTER VERSION: 1.23.0
? Are you sure you want to continue with an outdated package? This will result in some serious technical dept in the future and prevent security updates arriving... (y/N)

Is there a way I can disable this check so that the build can proceed even if I'm using an older version of boats?
Upgrading a dependency is something that requires careful consideration and is always done manually to validate the new build, I cannot afford to have broken builds due to a tool that wants to update itself.

One workaround you can use is to set NODE_ENV=test, which skips the version check

@p-mcgowan I see the PR, I like the proposed --yes flag. I'll wait for the change to be released and use the NODE_ENV workaround in the meantime, thank you so much for the very quick response! Love the project btw

@MatteoJoliveau thanks! We like it too and we're happy to see it in the wild.
It's still in active development and use and we are always happy to receive community feedback so we can continue to make it better!


rangeAlgorithmClassName can't work ?

I use 4.0 proxy version.
here is config-sharding.yaml  :

If i use = or in ,the preciseAlgorithmClassName can be work.
but i user >= & <= ,the rangeAlgorithmClassName can't be work,
here is the sql excute:

but i really config rangeAlgorithmClassName , may be something is error ?
thanks .

According the log, you config a inline strategy, plz check it.

yes，see the log must be config a inline strategy.
but the picture,  i really config stardard,  user myself RangeShardingAlgorithm

i know the truth,   because the databaseStrategy i use inline , so , the proxy think the table is inline ,but i set tableStrategy set standard 。
so  tableStrategy  is standard ,databaseStrategy  must be standard  ?

Can you make a simple demo to reproduce this issue for me to profiling it ?

this config throw : Inline strategy cannot suppory range sharding

no databaseStrategy  inline config can be ok .
i means ,  databaseStrategy of inline can affect tableStrategy's standard  .

Just the information said: Inline strategy cannot suppory range sharding
If you want use range sharding, please config range algorithm, please see example to get more information.


Diagnosing consumer failures is really hard

When a consumer test fails, the only error message tends to be an opaque the method annotated with @Pact did not run message. This makes diagnosing the underlying cause very hard.
There are several sub-problems.
Diagnosing absence
This is a fundamental Pact issue. If something didn't happen (the tests didn't hit the expected endpoint), it's hard to know what we can tell the user that's helpful. Monitoring all traffic and reporting what did happen would help, but it's not trivial. The wording of the error message maybe could be improved, but it's hard to see an obvious solution beyond that.
Maybe Quarkus can use its knowledge of the stack to monitor outbound traffic more easily than base Pact can.
Over-long stack traces
I don't think it's necessary to get the stack trace for the Pact failure, since it doesn't help us diagnose things.
Suppressed error messages
This is unique to continuous testing. And bad. For some errors, like a class not found, we get a helpful message with mvn verify, but not with continuous testing. Somehow in CT the error message gets swallowed.
Missing diagnostics for global issues
For some issues, breaking the tests is 'global' and seems to affect the whole runtime. For example, with #58, having one annotation will break all pact tests. In these cases, we don't get any messages at all (although in normal mode the tests run, so it's hard to compare.)

Quoting from @markusdlugi's suggestion on #73 and , so we don't lose the idea:

For example, in our project we are using a custom Wiremock server that is started as part of Dev Services and acts as a proxy to the Pact Mock Server. This accomplishes two things for us:
We can point our application's REST Client to Wiremock, where we have more control due to Dev Services integration, so we also get rid of the programmatic RestClientBuilder.
Additionally, Wiremock is a little more verbose regarding its requests and responses than the Pact MockServer, so it's easier to spot mismatched request

And from @holomekc:

The approach in our wiremock / pact setup is, that we have a Quarkus test resource for Wiremock with a custom annotation, which makes it easy to inject Wiremock into tests etc. In a base test class, we do exactly that and provide a method, which accepts the MockServer and creates the proxy config for Wiremock using the MockServer url. Then we just need to call this method. In theory this setup can be achieved wherever the MockServer is available then.


backend onChange undefined

Description
I followed the example on https://tiptap.dev/docs/hocuspocus/getting-started
My backend
import { Server } from '@hocuspocus/server'

const server = Server.configure({
  port: 1234,

  async connected() {
    console.log('connections: ', server.getConnectionsCount());
  },
  async onChange(data) {
    console.log('document', data.document.toJSON());
    console.log('tasks', data.document.get('tasks').toJSON())
  },
})

server.listen()

My frontend (Vue)
import * as Y from "yjs";
import { HocuspocusProvider } from "@hocuspocus/provider";

// Connect it to the backend
const provider = new HocuspocusProvider({
  url: "ws://<IP_ADDRESS>:1234",
  name: "example-document",
});

// Define `tasks` as an Array
const tasks = provider.document.getArray("tasks");

// Listen for changes
tasks.observe(() => {
  console.log("tasks were modified", tasks.toJSON());
});

// Add a new task
tasks.push(["buy milk"]);

And the log from frontend
tasks were modified ['buy milk']
But on the server side, the log is
connections:  1
document { tasks: undefined }
tasks undefined

Why tasks on backend is undefined? Is there anything I missed?
Environment?

operating system: win10
browser: chrome
mobile/desktop: desktop
Hocuspocus version:  v2.11.2

Additional context
Add any other context about the problem here.

I tried this
...
import { TiptapTransformer } from '@hocuspocus/transformer'

...
async onChange(data) {
  const prosemirrorJSON = TiptapTransformer.fromYdoc(data.document);
  console.log(prosemirrorJSON)
},

crash came out
[onChange] item.toDelta is not a function
file:///xxxx/hocuspocus/node_modules/y-prosemirror/src/lib.js:331
      const delta = item.toDelta()
                         ^

TypeError: item.toDelta is not a function
    at serialize (file:///xxxx/hocuspocus/node_modules/y-prosemirror/src/lib.js:331:26)
    at Array.map (<anonymous>)
    at yXmlFragmentToProsemirrorJSON (file:///xxxx/hocuspocus/node_modules/y-prosemirror/src/lib.js:375:20)
    at yDocToProsemirrorJSON (file:///xxxx/hocuspocus/node_modules/y-prosemirror/src/lib.js:308:10)
    at Prosemirror.fromYdoc (file:///xxxx/hocuspocus/node_modules/@hocuspocus/transformer/dist/hocuspocus-transformer.esm.js:2625:20)
    at Tiptap.fromYdoc (file:///xxxx/hocuspocus/node_modules/@hocuspocus/transformer/dist/hocuspocus-transformer.esm.js:2667:39)
    at Object.onChange (file:///xxxx/hocuspocus/index.js:14:47)
    at file:///xxxx/hocuspocus/node_modules/@hocuspocus/server/dist/hocuspocus-server.esm.js:2806:109
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Sorry, I located my mistakes:
On the backend, I used a get instead of getArray, and data.document.toJSON() is deprecated.
console.log('tasks', data.document.**getArray**('tasks').toJSON()) // logs: tasks [ 'buy milk' ]


Pylama failes to check file on other drive on Windows

Hello!
I have Windows 8 x64. I installed Miniconda2 on drive C: (C:\Miniconda2). Then I installed pylama using pip (pip install pylama). After that I tried to check file on drive E:
pylama E:\test_file.py
I got error:
ValueError: File is on drive E: start on drive C:

If I cd to E drive and than run file check then works fine. But because of this pylama doesn't works correctly in pylama-linter plugin for atom.
How can I fix it?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/32389415-pylama-failes-to-check-file-on-other-drive-on-windows?utm_campaign=plugin&utm_content=tracker%2F394650&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F394650&utm_medium=issues&utm_source=github).

I found that problem is at line 28 of core.py file:
path = op.relpath(path, rootdir)

I could not understand why relative path is needed. So I just commented this line and added before my variant:
path = op.abspath(path)

I tested it in cmd (Windows) and now it works.


Migration autogeneration fails if the source environment is empty

The autogenerate command fails with a TypeError: Cannot read properties of undefined (reading 'filter') error if the source (primary) environment has no models or blocks.
The command completed successfully as soon as I created a model in the primary environment.
Example command:
# `next` is the name of the sandbox environment
datocms migrations:new 'add company' --ts --autogenerate='next'

Sorry for the inconvenience, please try with v1.1.9!


Dip 158 follow ups

Updated the sequence to include QR Scan (focus on mobile)
Comment about error codes list being non-exhaustive
Minor typos and phrasing

@davidiw - please merge this one

Please rebase this PR and ping me so I can merge.


Verifying a school email address

@CohenRus Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


make as the package manager app name is weird/confusing, how about  pkman,

make is not something I wrote or named. It's a build system, which I'm abusing as a scripting language. The code of the package manager in the file named Makefile, which make automatically finds in the current directory and interprets.
Also, env/shell.sh makes pacmake an alias for the package manager, accessible from any directory (which I think is a sufficiently punny name).


Uncaught ReferenceError: webpackJsonp is not defined

hi there, well, only when run the tests, this happens when I split my app into chunks by using the CommonsChunkPlugin to split vendor libraries in this case angular
here's my webpack.config.js
var path = require('path'),
    webpack = require('webpack');

var config = {
   context: __dirname,
   devtool: 'source-map',
   entry: {
      main: [
         'babel-polyfill',
         './client/crm/crm.js',
         './client/build/vendors.js',
         './client/crm/assets/stylus/styles.styl'
      ],
      // Since angular is installed as a node module, node_modules/angular,
      // we can point to it directly, just like require('angular');
      vendors: ['angular']
   },
   output: {
      path: __dirname + '/client/build',
      //publicPath: 'http://localhost:8080/client/crm/',
      filename: 'bundle.js'
   },
   module: {
      preLoaders: [{test: /\.js$/, loader: 'jshint-loader', exclude: /node_modules/}],
      loaders: [
         {
            test: /\.js$/,
            loader: 'babel',
            exclude: [
               path.resolve(__dirname, 'node_modules')
            ],
            // Options to configure babel with
            query: {
               cacheDirectory: true,
               plugins: ['transform-runtime'],
               presets: ['es2015', 'stage-2']
            }
         },
         {test: /\.html$/, loader: 'html', exclude: /node_modules/},
         {test: /\.css$/,  loader: 'style!css', exclude: /node_modules/},
         {test: /\.styl$/, loader: 'style!css!stylus', exclude: /node_modules/},
         {test: /\.png/,   loader: 'url?limit=100000&mimetype=image/png' },
         {test: /\.jpg/,   loader: 'file-loader' },
         {test: /\.woff(2)?(\?v=[0-9]\.[0-9]\.[0-9])?$/, loader: 'url-loader'},
         {test: /\.(ttf|eot|svg)(\?v=[0-9]\.[0-9]\.[0-9])?$/, loader: 'url-loader' }

      ]
   },
   plugins: [
      new webpack.optimize.CommonsChunkPlugin('vendors', 'vendors.js')
   ]
};

if (process.env.NODE_ENV === 'production') {
   config.output.path = __dirname + '/dist';
   config.plugins.push(new webpack.optimize.UglifyJsPlugin());
   config.devtool = 'source-map';
}

module.exports = config;

and offcourse I added to my index.html
<!DOCTYPE html>
<html lang="en">
<head>
   <meta charset="UTF-8">
   <title>CRM+</title>
   <link rel="stylesheet" href="crm/assets/css/bootstrap.css">
</head>
<body class="CRM-background">

<crm></crm>

<script src="build/vendors.js"></script>
<script src="build/bundle.js"></script>

</body>
</html>

but when I run the tests, I got this:

even that I added to the spec.bundle.js I got the same error

is there something that I missing??? I've searched but coudn't find something similar to this case, hope somebody help me :)

Read the following and should fixes the issue.
https://github.com/webpack/webpack/issues/368

did you ever solve this problem?

In my case, in .html I was referencing app.js BEFORE vendor.js, reversed/corrected the order, and the webpackJsonp error was gone.
Hope this helps.

I believe it's because your config entry points are in the wrong order. Shouldn't the vendor entry come before app?

Strangely enough, I was able to fix this by clearing my cache with ctrl+F5. This error randomly showed up after updating an HTML file with a button, but that seems unrelated as it stuck with I removed what I added.

Kind of related, kind of not. But if you are using Safari, I can confirm this is a cache issue. I resolved it by opening safari > preferences > privacy > manage website data > clear all

6

In my case, in .html I was referencing app.js BEFORE vendor.js, reversed/corrected the order, and the webpackJsonp error was gone.
Hope this helps.

Doh!  I know this is an old thread, but it helped me...  Using laravel mix with babel-plugin-syntax-dynamic-import to split my js, I had added 'defer' to my main app.js but to none of the chunks that are used sporadically throughout my site...  Deferring the chunks too has worked a charm :)


Fix app-command event always return 'unknown'.

Fixes #2306 .
No need to mask the command id for appcommand message. Having test with media key on keyboard.

:+1:


An error occurred during the fetch of repository 'rules_foreign_cc'

OS Platform and Distribution
macos
Compiler version
No response
Programming Language and version
java
Installed using virtualenv? pip? Conda?(if python)
No response
MediaPipe version
No response
Bazel version
bazel 5.2.0
XCode and Tulsi versions (if iOS)
No response
Android SDK and NDK versions (if android)
pixel 5 api 30
android 11.0
Android AAR (if android)
None
OpenCV version (if running on desktop)
No response
Describe the problem
bazel build -c opt --config=android_arm64 mediapipe/examples/android/src/java/com/google/mediapipe/apps/hairsegmentationgpu:hairsegmentationgpu

Complete Logs
An error occurred during the fetch of repository 'rules_foreign_cc':
   Traceback (most recent call last):
	File "/private/var/tmp/_bazel_xxx/e16bf2cb4a010c61f2f7c06851ef75fc/external/bazel_tools/tools/build_defs/repo/http.bzl", line 100, column 45, in _http_archive_impl
		download_info = ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://github.com/bazelbuild/rules_foreign_cc/archive/0.1.0.zip] to /private/var/tmp/_bazel_xxx/e16bf2cb4a010c61f2f7c06851ef75fc/external/rules_foreign_cc/temp6405001367640443065/0.1.0.zip: Connection reset

Helo @pareekshiv07
Can you please let us know if you have followed the Android setup guide after the Installation guide for your Mac OS?
Specifically, the WORKSPACE file should be updated with the android_ndk_repository() and android_sdk_repository() rules.
Also, refer to this comment on how to update the WORKSPACE file.


Admin Tab

Working on editing and deleting posts but got modal up and running. Able to delete users (cant delete another admin). Still having trouble with seeded data roles.

Now able to update and delete blog post from admin tab. Sometimes throwing some react errors but does function. Needs to be cleaned up with styling a little.


Fix typo "exsits" --> "exists"

fixes #109

Oh sorry, I just hard commited this in b325675195b1bfc1c6703fa382af9726a22b6470.


Add Dong Thap University

Dong Thap University - Vietnam
https://en.dthu.edu.vn

@thanhla-cs The domain registrant for dthu.edu.vn is Trường Đại học Đồng Tháp (Dong Thap University). This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@thanhla-cs Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


OCaml version

This version is here to prove a point, that was actually made here (and in many other places). This uses Lwt.
node for comparison :
regular: 488.650ms
warmed-up: 367.576ms
ocaml lwt: 0.035144s
ocaml direct: 0.020431s
ocaml trunk lwt: 0.025163s
ocaml trunk direct: 0.018966s
This is not averaged or anything, I didn't bother, the whole thing is already comparing apple to oranges. Comparing vastly different threading techniques is not useful.
Side note: the code is not optimized at all, it's the most naive thing you would do with lwt.

:+1:

At what point did concurrency benchmarking turn into cooperative threads benchmarking? :)

When someone added benchmarks using goroutines and/or promises. :)

Well, at least goroutines do stuff on multiple cores, unlike the Node example (or this ocaml one, I assume) :)
Although the Go example never seems to go over 50% CPU usage on my machine, while the Scala one easily reaches 95-100%. Probably the overhead on Go is too much.
Try upping the iterations to 10M and Go version suddenly eats 5GB of memory, at 20M it goes over 20GB :D

@ochrons I agree, this version was not here to make a comparison with OCaml, just to show how the whole thing was misleading when pushed to the extreme. And indeed, it runs on a single core. :)

Goroutines are somewhat comparable to actors, but futures/promises aren't indeed.
The original idea was using the most obvious idea capable of spawning 1M independent processes for any language.

This only uses one green thread.


Use hw.ncpu on macOS instead of nproc

This doesn't hit us on CI since we install the coreutils package, which
installs nproc for us. If that isn't installed, however, this line will fail.
The appropriate substitute is the same as for FreeBSD.

Just checked and I don't think there's anything else we need from coreutils, so I'll update the PR to remove it.


[1.10-rc1] volume reference logic error

I just got the following error: 409 Client Error: Conflict ("Conflict: remove 9fb498dc7c51ea2a371008fb89e86e4b33f3462bc6d77740137a528b507a191c: volume is in use - [209001478e702f5d5bf59f9604d4584f604a4cda01f4416c81d53d9016034b22]") but 209001478e702f5d5bf59f9604d4584f604a4cda01f4416c81d53d9016034b22 does not exist.  After daemon restart I was able to delete it.  All I did was launch a couple hundred nginx containers and then delete them.  There was not volumes-from or sharing of volumes.  I will try to reproduce.

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

@cpuguy83 Okay, I reproduced it with a container that failed to delete.  So
$ docker rm -fv 7755
Failed to remove container (7755): Error response from daemon: Driver overlay failed to remove root filesystem 7755ee59efaaf4f0847e022ad59410da10af489d989b186680fb3950915e2733: readdirent: no such file or directory

$ docker rm -fv 7755
Error response from daemon: No such container: 7755
Error: failed to start containers: 7755

$ docker volume rm asdfasdf
Error response from daemon: Conflict: remove asdfadsf: volume is in use - [7755ee59efaaf4f0847e022ad59410da10af489d989b186680fb3950915e2733]

So apparently the container was failed to removed, but then Docker still removed it and the volume cleanup logic didn't get called?

ah, I have an idea, thanks!

#19676


Required more explaination

There is sentence in the blog,
"Collaborative domains where many users access the same data in parallel. CQRS allows you to define commands with enough granularity to minimize merge conflicts at the domain level, and conflicts that do arise can be merged by the command"
I cannot imagine the scenario.

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

ID: 0c0ec92e-c237-f3a6-1835-f2078486dcb3
Version Independent ID: f597c9a2-f18f-3722-57f9-acd535472b0b
Content: CQRS pattern - Azure Architecture Center
Content Source: docs/patterns/cqrs.yml
Service: architecture-center
Sub-service: azure-guide
GitHub Login: @martinekuan
Microsoft Alias: architectures

@Arjun-Mandavkar
Thanks for your feedback! We will investigate and update as appropriate.

Hi @Arjun-Mandavkar
Sorry for the delay.
The sentence is related to: [“Commands should be task-based, rather than data centric. ("Book hotel room", not "set ReservationStatus to Reserved").
”](https://learn.microsoft.com/en-us/azure/architecture/patterns/cqrs#solution).
The pattern creates a sequence of tasks which are going to impact the write store. The size of what is going to do depends on the domain. For example: Sell the car XXX to John Doe. The granularity in your domain can be a tool to minimize conflicts, and we could manage the result. Selling a car implies several data collections, and the car selling is in parallel. We could design to be represented by one task and solve the way to sell only once “car XXX” there.
The problems need to be solved with or without CQRS, but here you have the concept of commands queue.
I will close the ticket, but feel free to open a new one if you still have concerns.
#please-close


Dose BMCloss only work for minibatch > 1?

The bmcloss equals 0.0 when I added BMCloss to my project with minibatch==1.
I noticed that bmcloss is calculated by treating the regression predictions in a batch as multiclass classification. But since the size of each of my samples is different, my minibatch can only be set to 1.
Is it not feasible to apply bmcloss in this case?

Yes. In this case, other loss variations like GAI will be more suitable. GAI precomputes the label statistics.

Thanks for your reply!


rtfd: fix building  with stable/latest

What does this PR do?
Fixes following:

Your documentation did not generate an 'index.html' at its root directory. This is required for documentation serving at the root URL for this version.

Before submitting

[x] Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.

Did you have fun?
Make sure you had fun coding 🙃

:books: Documentation preview :books:: https://torchmetrics--2101.org.readthedocs.build/en/2101/

the links checks is being fixed in #2104


Actions documentations

We have implemented action possibility in the login and register process. this should be documented. Also we should mention what in the future should be possible with the actions
Acceptance criteria

[ ] Add Actions to documentation
[ ] Future plans with actions

currently support 3 triggers in the external authentication flow:

post authentication (user has authenticated externally and we retrieved / mapped the information as far as possible)
pre creation (before user is "autoregistered" / clicks on register on overview page after external authentication)
post creation (after the user was created from an external authentication)

context (information we provide you with):

accessToken (string for opaque and JWT)
idToken (string)
getClaim(string) interface{}: function which returns the requested claim
claimsJSON(): function which returns the complete payload of the id_token

api (information you can manipulate):

setFirstName(string)
setLastName(string)
setNickName(string)
setDisplayName(string)
setPreferredLanguage(string)
setGender(Gender)
setUsername(string) (currently only available on trigger pre creation!)
setPreferredUsername(string) (currently only available on trigger post authentication!)
setEmail(string)
setEmailVerified(bool)
setPhone(string)
setPhoneVerified(bool)
metadata (array of Metadata, push new entry)
userGrants (array of UserGrant, push new entry) (currently only available on trigger post creation!)


[Moderate] Add a better animation to the 'OK' button

@Sanket1308 I would like to work on this

Go ahead! Contribute well🚀

@Sanket1308 can i work on this ?

@Sanket1308 can i work on this ?

Hey bhawana
I am working on this you can find some other issue


Lookup facet config from finder definition

https://trello.com/c/UhV3PPfO/87-metadata-tagger-should-use-finder-facet-definitions
Facet config is stored in YAML in this project and should be
treated as the single definition of the facets and values we
tag with. This should reduce the impact of changes to metadata
values and names.

@barrucadu done in https://github.com/alphagov/rummager/pull/1343/commits/6f40399010e1ff126829df12b53e9eb838a588cb


How does i predict an image instead of a webcam?

Hello,
i found the code for tensorflow.js very helpful:
https://github.com/googlecreativelab/teachablemachine-community/blob/master/snippets/markdown/image/tensorflowjs/javascript.md
But i couldn't figure out how i can predict an image instead of a webcam image.
Is it possible to provide an example for using static images?
Best regards
Markus

I know this code is a mess, but it can handle webcam and user uploaded images using filereader API.
https://github.com/Gerard-Szulc/isTodd/blob/main/src/components/ToddChecker.vue


[Docs] [WIP] Modify command reference doc pages

Signed-off-by: Aadhitya A<EMAIL_ADDRESS>Description
This PR fixes #2984
Notes for Reviewers
This involves basic rework of doc pages. Small note: Gemfile.lock is now updated with new packages, need to verify it for confirmation!
Signed commits

[x] Yes, I signed my commits.

🚀