Adding Dry Deposition Parameterization Using ACCESS

@zmoon  Following discussions at the AMS Fire and Forest conference with Michael Vermeuel (Post-Doc with Dylan Millet at University of Minnesota) on his work on multi-layer canopy model with dry deposition in MLC-Chem and FluCS 2021 dataset (and comparison to GEOS-Chem big-leaf resistance method), we have good ideas to move forward with initial version of an explicit dry-deposition module in canopy-app.
This can be linked with say our BVOC emissions model in canopy-app for BIDI-sensitive species as well.  To accomplish this tasks, however, we may need to link surrogate/ML models as in issue #59 to handle driving a stand-alone canopy-app interface with chemical concentrations, compensation points (for BIDI-VOC) etc., and we can use more generalized dry deposition models that depend on chemical properties and diffusivities as inputs.
The question is what is the best method to get stomatal (and included species-dependent mesophyll) resistances:
(1) the default multiplicative method in the Wesely scheme (W89) and Zhang et al. (2003) scheme (Z03), (2) the traditional photosynthesis-based Farquhar–Ball–Berry (FBB) stomatal algorithm, and/or (3) the Medlyn stomatal algorithm (MED) based on optimization theory.  We could add options to use each method in the canopy-app NL.
We could just add a deposition velocity functions, which employ option to either input (e.g., bulk RS from the LSM) or calculate  the stomatal resistances at leaf level and use data tables that parameterize the mesophyll resistance as a function of solubility following Wesely (1989) or another method above.
Or, maybe if we need to calculate the RS take the approach used in MLC-Chem or even better use the MLC codes for different stomatal resistance options from  ACCESS dry deposition as a start.  I think using ACCESS is the best initial path forward for adding dry deposition velocity in the canopy.
We could take some insight Clifton et al. 2022 type approach in LES.
Also, after we get something more general, maybe add new approaches such as ecophysiology models.

Also need to bring in aerosol distribution, probably first. Beiming will work on this:
https://www.nicholas.duke.edu/people/faculty/katul/AE_Katul_2011.pdf
https://agupubs.onlinelibrary.wiley.com/doi/pdf/10.1029/2009JD012853

this is the link to multi-layer simplified ACCESS model. please do not use main brunch, but trail_0721 brunch. I will do additional test to merge before merge the main brunch. link: https://github.com/btang1/DryDep_MultiLayer_code/blob/trial_0721/DryDep.f90
it has 3 component codes: DryDepo, ACCESS_modules, ACCESS_constant.

updated successful off-line multi-layer model. GitHub link: https://github.com/btang1/DryDep_MultiLayer_code/blob/main/DryDep.f90

updated off-line multi-layer model. Slide link: https://docs.google.com/presentation/d/1XjnAuANq3lX5qOH_9AnOjfoaqyVRGyvQ/edit?usp=sharing&ouid=117233739375959098251&rtpof=true&sd=true

@btang1 Great progress, and discussion today!  As discussed, and as you showed, you are close to getting the stand alone dry dep modules into canopy-app to compile, but need to firm up the coding standards required currently in canopy-app DEBUG mode.
Next, we need to continue to work on getting other multi-layer calculations in canopy-app needed for dry deposition, which include:
Canopy Air Temperature:  tk   (Example ACCESS IntegrateTempAir)
Canopy Water Vapor: qh (Example ACCESS IntegrateWaterVapor)
Canopy Air Pressure:  pmb  (This can be based on surface pressure input and barometric formula)
Canopy Sunlit Stomatal Conductance:  gs_sun (Example ACCESS gs_medlyn)
Canopy Shaded Stomatal Conductance:  gs_shade (Example ACCESS gs_medlyn)
However, caveat is that you need the net photosynthesis assimilation rate calculation to get anet for gs_medlyn.  It seems you are using the test CANCACC gs_sun and gs_shade as inputs to your gs_medlyn calculation, but these values need to be dynamically calculated in canopy-app.
While typically many of these calculations are done by using a Leaf Energy Balance (LEB) equation, in canopy-app, we have already approximated the leaf temperature and PPFD through the canopy using parameterizations, and will not need a LEB initially to get these.
So, we should pull out of ACCESS/CANACC physics codes just what we need to calculate  tk, qh, pmb, gs_sun, gs_shade, and anet, and use the input GFS surface met/land variables as the upper boundaries to parameterize as similarly in other canopy-app functions.  We may need to read more input GFS variables from the input files in canopy-app, and you can see the current list we input in canopy-app README, Table 2.  This will be easy as all surface variables are available from the GFS inputs.
It would be great if you could help with this to get the dry dep to work in canopy-app, and we can discuss further where to add these new functions/modules (i.e.,  tk, qh, pmb, gs_sun, and gs_shade) in canopy-app.

Thanks Patrick!
On Aug 21, 2023, at 3:50 PM, Patrick Campbell @.***> wrote:
@btang1https://github.com/btang1 Great progress, and discussion today! As discussed, and as you showed, you are close to getting the stand alone dry dep modules into canopy-app to compile, but need to firm up the coding standards required currently in canopy-app DEBUG mode.
Next, we need to continue to work on getting other multi-layer calculations in canopy-app needed for dry deposition, which include:
Canopy Air Temperature: tk (Example ACCESS IntegrateTempAirhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L205)
Canopy Water Vapor: qh (Example ACCESS IntegrateWaterVaporhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L137)
Canopy Air Pressure: pmb (This can be based on surface pressure input and barometric formula)
Canopy Sunlit Stomatal Conductance: gs_sun (Example ACCESS gs_medlynhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L502)
Canopy Shaded Stomatal Conductance: gs_shade (Example ACCESS gs_medlynhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L502)
However, caveat is that you need the net photosynthesis assimilation rate calculationhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L709 to get anet for gs_medlyn. It seems you are using the test CANCACC gs_sun and gs_shade as inputs https://github.com/btang1/DryDep_MultiLayer_code/blob/main/DryDep.f90#L63 to your gs_medlyn calculation, but these values need to be dynamically calculated in canopy-app.
While typically many of these calculations are done by using a Leaf Energy Balance (LEB) equation, in canopy-app, we have already approximated the leaf temperature and PPFD through the canopy using parameterizations, and will not need a LEB initially to get these.
So, we should pull out of ACCESS/CANACC physics codes just what we need to calculate tk, qh, pmb, gs_sun, gs_shade, and anet, and use the input GFS surface met/land variables as the upper boundaries to parameterize as similarly in other canopy-app functions. We may need to read more input GFS variables from the input files in canopy-app, and you can see the current list we input in canopy-app README, Table 2https://github.com/noaa-oar-arl/canopy-app#table-2-canopy-app-required-input-variables. This will be easy as all surface variables are available from the GFS inputs.
It would be great if you could help with this to get the dry dep to work in canopy-app, and we can discuss further where to add these new functions/modules (i.e., tk, qh, pmb, gs_sun, and gs_shade) in canopy-app.
—
Reply to this email directly, view it on GitHubhttps://github.com/noaa-oar-arl/canopy-app/issues/60#issuecomment-1686944703, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMGOO65GMO5N25XBR7UYAWDXWO3ZDANCNFSM6AAAAAAXU7PL4M.
You are receiving this because you were mentioned.Message ID: @.***>

Hi Patrick,
Good news. After Zach teach me to replace dp to rk, and i4 to ik.
Now I have compile canopy-app with my drydep code successfully.
Best wishes,
Beiming
On Aug 21, 2023, at 3:50 PM, Patrick Campbell @.***> wrote:
@btang1https://github.com/btang1 Great progress, and discussion today! As discussed, and as you showed, you are close to getting the stand alone dry dep modules into canopy-app to compile, but need to firm up the coding standards required currently in canopy-app DEBUG mode.
Next, we need to continue to work on getting other multi-layer calculations in canopy-app needed for dry deposition, which include:
Canopy Air Temperature: tk (Example ACCESS IntegrateTempAirhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L205)
Canopy Water Vapor: qh (Example ACCESS IntegrateWaterVaporhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L137)
Canopy Air Pressure: pmb (This can be based on surface pressure input and barometric formula)
Canopy Sunlit Stomatal Conductance: gs_sun (Example ACCESS gs_medlynhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L502)
Canopy Shaded Stomatal Conductance: gs_shade (Example ACCESS gs_medlynhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L502)
However, caveat is that you need the net photosynthesis assimilation rate calculationhttps://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L709 to get anet for gs_medlyn. It seems you are using the test CANCACC gs_sun and gs_shade as inputs https://github.com/btang1/DryDep_MultiLayer_code/blob/main/DryDep.f90#L63 to your gs_medlyn calculation, but these values need to be dynamically calculated in canopy-app.
While typically many of these calculations are done by using a Leaf Energy Balance (LEB) equation, in canopy-app, we have already approximated the leaf temperature and PPFD through the canopy using parameterizations, and will not need a LEB initially to get these.
So, we should pull out of ACCESS/CANACC physics codes just what we need to calculate tk, qh, pmb, gs_sun, gs_shade, and anet, and use the input GFS surface met/land variables as the upper boundaries to parameterize as similarly in other canopy-app functions. We may need to read more input GFS variables from the input files in canopy-app, and you can see the current list we input in canopy-app README, Table 2https://github.com/noaa-oar-arl/canopy-app#table-2-canopy-app-required-input-variables. This will be easy as all surface variables are available from the GFS inputs.
It would be great if you could help with this to get the dry dep to work in canopy-app, and we can discuss further where to add these new functions/modules (i.e., tk, qh, pmb, gs_sun, and gs_shade) in canopy-app.
—
Reply to this email directly, view it on GitHubhttps://github.com/noaa-oar-arl/canopy-app/issues/60#issuecomment-1686944703, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMGOO65GMO5N25XBR7UYAWDXWO3ZDANCNFSM6AAAAAAXU7PL4M.
You are receiving this because you were mentioned.Message ID: @.***>

Great news!  Let's move forward integrating and getting it to work in
canopy-app with my suggestions above.  Thank you
On Thu, Aug 24, 2023, 1:08 AM Beiming Tang @.***> wrote:

Hi Patrick,
Good news. After Zach teach me to replace dp to rk, and i4 to ik.
Now I have compile canopy-app with my drydep code successfully.
Best wishes,
Beiming
On Aug 21, 2023, at 3:50 PM, Patrick Campbell @.***> wrote:
@btang1https://github.com/btang1 Great progress, and discussion today!
As discussed, and as you showed, you are close to getting the stand alone
dry dep modules into canopy-app to compile, but need to firm up the coding
standards required currently in canopy-app DEBUG mode.
Next, we need to continue to work on getting other multi-layer
calculations in canopy-app needed for dry deposition, which include:
Canopy Air Temperature: tk (Example ACCESS IntegrateTempAir<
https://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L205>)
Canopy Water Vapor: qh (Example ACCESS IntegrateWaterVapor<
https://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L137>)
Canopy Air Pressure: pmb (This can be based on surface pressure input and
barometric formula)
Canopy Sunlit Stomatal Conductance: gs_sun (Example ACCESS gs_medlyn<
https://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L502>)
Canopy Shaded Stomatal Conductance: gs_shade (Example ACCESS gs_medlyn<
https://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L502>)
However, caveat is that you need the net photosynthesis assimilation rate
calculation<
https://github.com/rdsaylor-noaa/ACCESS_FULL/blob/master/src/CanopyPhysics.f90#L709>
to get anet for gs_medlyn. It seems you are using the test CANCACC gs_sun
and gs_shade as inputs <
https://github.com/btang1/DryDep_MultiLayer_code/blob/main/DryDep.f90#L63>
to your gs_medlyn calculation, but these values need to be dynamically
calculated in canopy-app.
While typically many of these calculations are done by using a Leaf Energy
Balance (LEB) equation, in canopy-app, we have already approximated the
leaf temperature and PPFD through the canopy using parameterizations, and
will not need a LEB initially to get these.
So, we should pull out of ACCESS/CANACC physics codes just what we need to
calculate tk, qh, pmb, gs_sun, gs_shade, and anet, and use the input GFS
surface met/land variables as the upper boundaries to parameterize as
similarly in other canopy-app functions. We may need to read more input GFS
variables from the input files in canopy-app, and you can see the current
list we input in canopy-app README, Table 2<
https://github.com/noaa-oar-arl/canopy-app#table-2-canopy-app-required-input-variables>.
This will be easy as all surface variables are available from the GFS
inputs.
It would be great if you could help with this to get the dry dep to work
in canopy-app, and we can discuss further where to add these new
functions/modules (i.e., tk, qh, pmb, gs_sun, and gs_shade) in canopy-app.
—
Reply to this email directly, view it on GitHub<
https://github.com/noaa-oar-arl/canopy-app/issues/60#issuecomment-1686944703>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AMGOO65GMO5N25XBR7UYAWDXWO3ZDANCNFSM6AAAAAAXU7PL4M>.
You are receiving this because you were mentioned.Message ID: @.***>
—
Reply to this email directly, view it on GitHub
https://github.com/noaa-oar-arl/canopy-app/issues/60#issuecomment-1691010182,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGLFYNWKUIUJTZ5B7EYMHL3XW3OVBANCNFSM6AAAAAAXU7PL4M
.
You are receiving this because you were assigned.Message ID:
@.***>


Add caching to tests

This PR sets up caching for setting up JANUS and SOCRATES. This completely eliminates build times on repeated runs with the same SOCRATES or JANUS versions. This should reduce total test times by ~1.5 minutes for each run.
The caches are keyed by the python version and pyproject.toml for JANUS and to SOCRATES/version for SOCRATES.
I also scoped the test runs, so that they no longer run twice in a PR.

I am happy to review it, since Laurent is on holiday this week. So if you are ok with this, I will go ahead.

Cheers, I'll just merge it now then. If there need to be additional changes, I'm happy to fix it!


Thanos query is not fetching old data from s3

We are trying to fetch old data from s3 storage via Grafana using thanos query.
We are not able to see old data and below error is coming in Thanos query
level=warn ts=2020-02-24T10:24:13.399884678Z caller=storeset.go:429 component=storeset msg="update of store node failed" err="getting metadata: fetching store info from MonitoringStoreContainer:10911: rpc error: code = DeadlineExceeded desc = latest connection error: connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:10911: connect: connection refused"" address=MonitoringStoreContainer:10911

Hi @satyabhama it looks like the address <IP_ADDRESS>:10911 is either not accessible from the thanos querier or simply nothing is listening at that endpoint.
Could you maybe share more information about how you are running? e.g. config/manifests (it looks like maybe docker containers?)
Are you sure that the querier can actually hit that port?
-Lucas

Hey @squat we have thanos query and store running in one docker.
Query commands:

Command
["query","--http-address=<IP_ADDRESS>:19192","--store=:10912","--store=MonitoringStoreContainer:10911","--query.replica-label=replica"]

Store commands:

Command
["store","--objstore.config-file=/etc/thanos/prometheusconfig.yml","--data-dir==/thanos/store","--grpc-address=<IP_ADDRESS>:10911","--sync-block-duration=15m"]

Could you please us from where IP <IP_ADDRESS>:10911 is coming??

Hi @satyabhama that IP is coming from Docker's service name resolution. <IP_ADDRESS>/16 is the CIDR for the default Docker network, and <IP_ADDRESS> is apparently the IP being given to your Thanos Store container.
However, it seems that the port 10911 is not accessible. Are you sure that Docker is correctly exposing this port? Ie running Docker with the --port flag to expose the port

Can you share the actual Docker commands you are running? Or if using Swarm, your Docker Swarm config?

In one docker container we have store and query component running and here is commands for that
Query commands:
Command | ["query","--http-address=<IP_ADDRESS>:19192","--store=:10912","--store=MonitoringStoreContainer:10911","--query.replica-label=replica"]
Store commands:
Command | ["store","--objstore.config-file=/etc/thanos/prometheusconfig.yml","--data-dir==/thanos/store","--grpc-address=<IP_ADDRESS>:10911","--sync-block-duration=15m"]


serviceuser v1 api: can't list enabled services for a project

I'm trying to list the enabled APIs for a project and am failing. The API call I'm trying to make is https://cloud.google.com/service-management/reference/rest/v1/services/list with the consumerID query string param set to "project:". I'm calling https://cloud.google.com/service-management/reference/rest/v1/services/list (https://godoc.org/google.golang.org/api/serviceuser/v1#ProjectsServicesService.List) passing the project ID in, but I get the following error:

404. That’s an error.

The requested URL /v1/project:project-id-3416666172000000000/services?alt=json was not found on this server.  That’s all we know.

From my reading of the API docs, the URL should be:
/v1/services?consumerID=project:project-id-3416666172000000000

Am I doing something wrong or is there a bug?

I found a resolution, in the source code I saw https://github.com/google/google-api-go-client/blob/master/serviceuser/v1/serviceuser-api.json#L122 which states how the project ID needs to be passed in, but this comment doesn't make it into the docs at https://godoc.org/google.golang.org/api/serviceuser/v1 (unless I'm blind).

I see that the documentation for the "name" parameter in the ProjectsServicesService.Enable call is similarly absent from the godoc and it's impossible to divine what needs to be passed from any docs I see.

Okay, I think I found part of the problem. There are two APIs: Service User and Service Management.
What threw me off for a while is that the Service User API's definition (what is used to generate client code and Go Docs) points to the documentation for Service Management.
It sounds like you are looking for https://godoc.org/google.golang.org/api/servicemanagement/v1

Assuming from lack of response that your problem is resolved. Reopen otherwise.


test: Add Uart output test

Couldn't help myself to add a UART Output test before heading off to work.
I still want to add a UART input test before I start to refactor out the global state as those two branches are the only that touch the DOM directly and depend on a few globals.
Also added the --verbose option to jest so that we can see every tests result with timings on the github actions console.

This is what I meant with the verbose flag. Took less than 100ms on my machine and was curious how much the gh action runner differs.

OK, we have a bit of a problem. I don't know how I'll go about testing your work in Firefox 52 before I upload it to GitHub Pages. Namely, on my Oracle Solaris 11.4 virtual machine, on which Firefox 52 is installed, Shared Folders do not work, and neither does the terminal emulator (to run git clone https://github.com/agustiza/PicoBlaze_Simulator_in_JS.git). And I have a cybernetics test on 29/08 (Tuesday) that I am not quite ready for, so I cannot waste a lot of time on this.

Not sure if I understand. Did something break or just not tested?
What was working should keep working as not a single line has changed so far, only tests which do not run on the browser.
That said it's your project, do as you have to (or not).

Not sure if I understand. Did something break or just not tested?
What was working should keep working as not a single line has changed so far, only tests which do not run on the browser.
That said it's your project, do as you have to (or not).

Not sure if I understand. Did something break or just not tested?
What was working should keep working as not a single line has changed so far, only tests which do not run on the browser.
That said it's your project, do as you have to (or not).

I don't know how I will test your changes in Firefox 52 before accepting them. The Solaris virtual machine on which I have Firefox 52 installed isn't working properly.

@agustiza I found a simple solution. I will, on the host machine, do this:
git clone https://github.com/agustiza/PicoBlaze_Simulator_in_JS.git new_code
cd new_code
php -S <IP_ADDRESS>:8080

Then I will start the Solaris 10.4 virtual machine in VirtualBox, fire up Firefox 52 and set the URL to http://<IP_ADDRESS>:8080. That's how I will test whether what you have done works in Firefox 52.

That works. If it helps I could also just host a GH pages on my repo and you'd just test there. Up to you.


fix variable set but not used

Summary
These variables will trigger variable 'ret' set but not used warnings due to different configurations.
For using variables only in assert, added UNUSED to declare
Warnings in external repositories are ignored in the makefile
Impact
Let's ignore the following format check, which seems to have nothing to do with this change
apps/modbus/nuttx/porttimer.c:51:9: error: Mixed case identifier found
  return xMBPortSerialSetTimeout(ulTimeOut);

Testing

Please verify the issues with sim/zipfs

I think it doesn't need with the new approach. Let's close it now.


[$500] Connect bank account - User can't continue / receives error if returns to entering account page and tap Continue

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:  1.3.94-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
Action Performed:

Go to staging.new.expensify.com or open Expensify App and login with any account
Go to existing workspace or create new one
Go to Workspace > Connect bank account
Tap 'Connect with Plaid' and select any bank (eq. Chase)
Follow the flow until 'Personal Information' page
Click 'Back' (<) button twice to return to the page for entering routing and account numbers
Click/Tap 'Continue'

Expected Result:
User goes to the page 'Company Information'
Actual Result:
User receives an error message and cannot continue
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/115492554/e35a94b1-7177-408a-8505-1cc97b30f847

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~011f6c8b5dad4aad8a
Upwork Job ID:<PHONE_NUMBER>927179264
Last Price Increase: 2023-11-08
Automatic offers:

dukenv0307 | Contributor | 27590431

Proposal
Please re-state the problem that we are trying to solve in this issue.
Connect bank account - User can't continue / receives error if returns to entering account page and tap Continue
What is the root cause of that problem?
Because we got validation about masked accountNumber here.
https://github.com/Expensify/App/blob/a31933a049b9a9aa4222a4d3edab19b54a4555b7/src/pages/ReimbursementAccount/BankAccountManualStep.js#L40-L44
What changes do you think we should make in order to solve the problem?
We don't need to validate about masked accountNumber because that is saved after validation on step3.
so we need to change validation
We need to update like this.
if (
        values.accountNumber &&
        !shouldDisableInputs &&
        !CONST.BANK_ACCOUNT.REGEX.US_ACCOUNT_NUMBER.test(values.accountNumber.trim()) &&
        !CONST.BANK_ACCOUNT.REGEX.MASKED_US_ACCOUNT_NUMBER.test(values.accountNumber.trim())
) {

What alternative solutions did you explore? (Optional)
We can didn't mask about account number
https://github.com/Expensify/App/assets/65789015/0e706366-e2db-4aee-8a44-90a8d8180107

Sorry for the delay. Will review the proposals shortly.

Thanks for the proposal everyone.
@dukenv0307 Thanks for the detailed explanation on root cause analysis.

The back-end is always leaving 4 last digits and mask the rest, while the front-end is expecting account number longer than 13 digits to be masked differently here. So the front-end regex will throw error if a more-than-13-digits account number has 4 last digits unmasked and the rest masked.

As mentioned in the proposal, the format in which backend returns the account detail is different than expected in the frontend. So, to solve the issue we should either update frontend to expect only last 4 digits for masked account number. Or update backend to return account number with first 6 digit and last 4 digit if the length of account number is greater than 13.
Proposal from @dukenv0307 looks good to me.
🎀 👀 🎀 C+ reviewed

@dukenv0307 proposal LGTM 👍

@dukenv0307 In my opinion, the backend is the source of truth. I would go with #1. @sobitneupane what's your opinion?

Yeah. Good to go with first option.

PR was deployed to production two weeks back. Ready for payment.
cc: @CortneyOfstad

Requested payment on newDot.

$500 payment approved for @sobitneupane based on comment above.


WIP Add The Current Implementation work

Appreciate the effort, but I went ahead and adapted the current Raw JSON serializer to also support XML.


M3-3599 Longview e2e tests

Longview UI tests

Created test for the longview plan subscription and longview clients.
All tests can be run individually or together. The beforeEach and API calls will set up the data for the tests to run and use the information
from the responses for verification.

note there is an ugly browser.pause(1500) in the changePlan function.
This is because once the button is selected it is set to a disabled mode
so the check for the button to not be enabled will not work. Need a better
way to wait for the loading state on the button.
When running tests remember to use a user that does NOT have longview
clients installed. The tests will clear out all longview clients to make
sure the tests run reliably.
Added in some needed selectors to allow for UI automation to work easier. We are now using the data-testid instead of data-qa for testing attribiutes.
Fixes for crumb/header changes
changed title selector from '[data-qa-dialog-title]' to 'h1'
Type of Change

Non breaking change ('update', 'change')

Applicable E2E Tests
To run relevant E2E tests, run these commands in 3 separate terminals:

yarn up
yarn selenium
yarn e2e --file longview/longview-plan-details.spec.js

Note to Reviewers
When running tests remember to use a user that does NOT have longview
clients installed. The tests will clear out all longview clients to make
sure the tests run reliably.

I fixed a small issue with a merge from Pat that overwrote my header changes. I also added a slightly longer wait time for the client to open. If you are still having issues with a hanging browser could we do a session together to see what might be different? I have asked @Jskobos to pull this branch again and see if he has any issues. I still have not had any hanging or failing issues.

@jstamis-linode @johnwcallahan I can still run these consistently using prod-test-011 (empty/unused account) without issue

@jstamis-linode It could have been a freak thing. If everyone else is seeing passing tests, and you're seeing passing tests on my test account, I feel okay about merging.


Deprecated either.{right,left}.value.

Fixes #972

the deprecations will be reversed in 2.12.0-RC2 due to negative community feedback
they might still eventually go forward, so that doesn't necessarily mean this PR should be discarded — you could make a decision about what version of the code you like best, and perhaps leave feedback on https://github.com/scala/scala/pull/5135

The deprecations are back as of 2.13 so can we get this patch applied please?

Because of the time that passed since the last comment a quick check.
The deprecation is still in place in 2.13.1, does that mean it's going to stay?

The deprecation is still in place in 2.13.1, does that mean it's going to stay?

at present .right is deprecated (and I believe it will stay that way) but .left isn't, as per https://github.com/scala/scala/pull/8012
Welcome to Scala 2.13.1 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_202).
Type in expressions for evaluation. Or try :help.

scala 2.13.1> Right("foo").withLeft[Int]
res0: scala.util.Either[Int,String] = Right(foo)

scala 2.13.1> res0.left
res1: scala.util.Either.LeftProjection[Int,String] = LeftProjection(Right(foo))

scala 2.13.1> res0.right
                   ^
              warning: method right in class Either is deprecated (since 2.13.0): Either is now right-biased, use methods directly on Either
res2: scala.util.Either.RightProjection[Int,String] = RightProjection(Right(foo))

Okay thanks for the heads up :)

Would love to get this merged.
See also my comment on  #972 - I think it makes sense to keep .left.value and just add .value directly on Either.

Would really like to see this merged or some variation of it. Using the toOption workaround is just cluncky.

I wonder, what exactly is missing in this PR that prevents it from being merged finally? It hangs open since 2016 already.

See also #1775 & #1746

@cla-bot[bot] check

This can be closed, as it was addressed in https://github.com/scalatest/scalatest/pull/1895.


Superb library - I am running on Node v20

Thanks @fivdi (for this + epoll)
Can I help run tests / contribute a PR for Node v20 coverage
Anecdotally this seems to work perfectly - but let me know if I can help.

Sorry for not responding sooner. All so ok with Node v20 and Node v21 and everything should function as expected. It's just not mentioned in the readme.

Thanks


Fails to load on Mac and Linux

attempting to launch initial session results in error when calling os module to access "LOCALAPPDATA" folder. Need to ensure solution is cross platform and validate on macOS and linux.

@mprib I'm getting this error when trying to launch on MacOS 14.1 Sonoma

Hi @Corey-PT! Could you paste in the precise error when attempting to launch and describe when it happens? A previous issue with macOS was its integration with Mediapipe, and getting compatibility was a bit like threading a needle. I might need to revisit that needle with an updated macOS, so any details you could provide would be much appreciated...

Also, @Corey-PT,  i"m opening up a new issue just to have a clean slate to discuss your specific issue:
https://github.com/mprib/pyxy3d/issues/481


fix: allow proving in wasi

In attempting to get the sp1 prover working in wasm32-wasi, we ran into an error originating from https://github.com/rust-lang/rust/blob/master/library/std/src/sys/pal/wasi/os.rs#L268-L270
This fix avoids using tempfile for wasm32, which was traced as the source of the problem.

We've run into memory issues with this solution when applying it to non-toy problems. We're working on an alternative approach using https://docs.rs/tempfile/latest/tempfile/fn.tempfile_in.html and an env var to define the temporary directory, since that will work in WASI (tempfile_in() doesn't use the offending temp_dir(): https://github.com/Stebalien/tempfile/pull/138). We'll have a new PR (or a commit here?) with that approach soon.

Hey @hosted-fornet, just wanted to say that it's super awesome you're trying to get this working. There's another team right now trying to get SP1 working on mobile, so this could be quite interesting for them.

Nice, that sounds like an interesting application: we're building a p2p node that uses wasm32-wasi components as userspace apps. SP1 would be a great unlock for us.
Hopefully we can get our fix out soon so we can all have something more concrete to discuss.

Ok, so @tadad did some good work tracking down the issue. It turns out the issue is not with the tempfiles; it is a separate issue.
The problem is that WASM modules are limited to 4GB of memory since they are 32bit!
This PR allows at least the smaller cases (fibonacci, e.g.) to work inside WASM modules. However, for more "real world" usecases, WASM is probably not ready for proving without the memory64 proposal. Verification works great, though.
More specifically, adapting the ed25519 example to our system doesn't work because we hit the 4GB memory limit here.

Just to follow up, it takes something like 20GB of memory, running natively on my machine, to prove the ed25519 example. Manipulating the shard size/threshold has no effect on this memory peak.

Hey @nick1udwig, I am about to merge in a PR which should make memory performance much better.

Hi @nick1udwig, thanks for running it. Yeah hm, lowering the memory usage there is a bit hard to avoid in the current design of the system. I'm going to look into lowering the memory usage even more.

Gotcha. @dr-frmr has told me that the ed25519 example is unrealistic for production because it'd be a precompile, so maybe I should just be using a different example? I do not understand this technology at more than a "user" level.

Hey @jtguibas, I updated this branch and kept the minimum change to allow the prover to run in Wasm. This is the code we've been using in our Wasm apps, and it seems to work. The memory limits are a separate problem of course, but this allows us to handle small-medium proofs without the tempfile::tempfile() call causing compilation issues.

Hi @dr-frmr, in the latest version of the prover, we no longer use tempfile::tempfile(), so hopefully it should work more out of the box now!

Oh, well that's great to hear -- can go ahead and close this then.

Nice


[CLI]: Have to call API twice to get wanted information

Describe the bug

When I make a single call nothing gets returned.

        self.api = wandb.Api({'entity': self.entity,
                              'project': self.project})

        # redundancy needed due to a W&B bug
        logging.info('Establishing W&B API connection established')
        self.runs = self.api.runs()   # this variable will contain no information about the runs
        self.runs = self.api.runs()   # this one will have the expected information
        logging.info('W&B API connection established')

Additional Files
No response
Environment
WandB version:  0.12.18
OS: Arch Linux
Python version: 3.10.4
Versions of relevant libraries:
Additional Context
No response

Hi @miguelvalente,
Our API lazily loads runs as they are accessed, which is why you were not seeing anything on the first call through the debugger. Could you try iterating through the runs once just to confirm if you are able to print the names / run id's for all of the runs? If you can, the API is working fine.

@ramit-wandb
PS:
Forgot to confirm what you said. Yes indeed it works as expected.

Hey @miguelvalente,
len(self.runs) should give the expected number of runs.
Thanks,
Ramit

@ramit-wandb Thanks!


Fix incorrect reading of somaxconn for tcp backlog on linux

Problem:
Dropwizard drops connections during a burst of short lived connections, as the accept queue is set to (most commonly) 1 or 2 due to Files.readAllBytes unable to work with pseudo files like somaxconn
Solution:
Adopt Netty's implementation
Result:
Test passed and dropwizard should be more burst resistant. Closes #2429
Dropwizard users currently afflicted by this bug, can override this default behavior by specifying an acceptQueueSize in their configuration.

Just a note. You say that affected users can override it in settings. However, the system limit still applies.
Users trying beyond that will not get over that effectively, AFAICT. To override:
sysctl -w net.core.somaxconn=65535

Typically added to sudo nano /etc/rc.local.

I suspect there is still another bug in Jetty in how it handles the sockets with refused connections. Setting higher accept queue will make it close to impossible to hit in real world scenarios though.
When we hit this issue, we see connection timeouts on the client side after 60 seconds. If it was just the accept queue full, the client would get the rejection and fail the connection right away. But it does not - instead, it keeps waiting. I think what is happening is described here: https://blog.cloudflare.com/this-is-strictly-a-violation-of-the-tcp-specification/
In short, Jetty doesn't close() the rejected connections properly.

Or maybe not. Petr Kacer said he checked with ss and there were no CLOSE_WAIT pending.


Smart Charging - Handle charging stations, which refuse the charging profile

Retry 3 times to push the charging profiles and if failed, exclude the charging station from the Smart Charging, send a notification to the Admins and retry again to apply the Smart Charging on the Site Area.

I think axios is used by the SetChargingProfile OCPP command, so it already retries 3 (tunable) times before throwing an error.

I think axios is used by the SetChargingProfile OCPP command, so it already retries 3 (tunable) times before throwing an error.

Perfect so no need to check that part then 👍

In fact, axios will not retry because it's not an HTTP error ;)
The retry condition lie in the upper network layer protocol.

In fact, axios will not retry because it's not an HTTP error ;)
The retry condition lie in the upper network layer protocol.

Perfect so we need to check that part then 👍 :-)


Clicking an input

"cosmos-js": "0.6.8",

My component optimistically set the internal state's value when clicked.  But, for some reason, shouldComponentUpdate is firing.
It looked like this should've been addressed in #133, but maybe it's something different?
Anyway, my main point is this is still a really freaking awesome project!!!!

Anyway, my main point is this is still a really freaking awesome project!!!!

Thanks! A lot of work has been put into it but in a way it's just the beginning of what it can become :)

My component optimistically set the internal state's value when clicked. But, for some reason, shouldComponentUpdate is firing.

I would need to see the source of that component. The component should not re-render unless you change the fixture or the fixture contents in the editor.

@ericclemmons is this still a problem?

You know what, I honestly don't know.  The components got rewritten & now not seeing it.
:shrug:


How to make this work on Azure Function v2?

I tried to read the Current Principal on Azure Functions v2, but
Thread.CurrentPrincipal as ClaimsPrincipal is null
Does Azure Functions v2 works with Easy Auth ?

A little bit late but
https://docs.microsoft.com/en-us/azure/app-service/overview-authentication-authorization
At this time, AAD V2 (including MSAL) is not supported for Azure App Services and Azure Functions. Please check back for updates.


Handling of single and double quotes, backslashes and newlines

📦 Published PR as canary version: 0.4.2--canary.22.c9bf52e4611347b2fa18551c0a5670723e49c01a.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in v0.5.1 :rocket:


Android device unable to receive message notifications

Hi there,
I tried compiling the latest code, but notifications are not being sent to the device when new messages arrive.
Does the current version support app notifications? For example, can it show notifications in the notification bar when new messages arrive?
I noticed Firebase Cloud Messaging (FCM) is integrated into the code. Is this feature already fully functional?
Can we use only local notifications?
If remote notifications are the only option, what parts of the code do I need to modify to implement notification functionality?
Thanks a lot.

Hello,
Yes indeed, the app does support notifications.
If you're not seeing them, the quickest way to debug might be to install the current production app (from the legacy zulip-mobile codebase) — it has some troubleshooting features that may help pin down what the issue is.

notifications are not being sent to the device when new messages arrive.

Note that by default Zulip doesn't send a notification for every new message — only for DMs, @-mentions, and topics you're following. You can change that setting:
https://zulip.com/help/mobile-notifications

Closing to get this out of our queue, since it's not actionable for us at present. If you're still seeing this issue and interested in investigating it, please feel free to reply with more information and I'll be happy to re-open.


Unable to compile after flutter upgrade (v3.10.0)

Hi @zezo357
Yesterday I upgraded my flutter version to 3.10.0.
I was trying to lunch your example code but I'm giving this errors:
Launching lib\main.dart on Windows in debug mode... main.dart:1 /C:/Users/-/AppData/Local/Pub/Cache/hosted/pub.dev/helpers-1.2.0/lib/helpers/misc.dart(127,7): error GBF4691A2: No named parameter with the name 'window'. [D:\Users\-\Desktop\flutter_meedu_videoplayer\package\example\build\windows\flutter\flutter_assemble.vcxproj] /C:/Users/-/AppData/Local/Pub/Cache/hosted/pub.dev/helpers-1.2.0/lib/helpers/misc_build/build_color.dart(33,42): error GD65BB2B6: The getter 'accentColor' isn't defined for the class 'ThemeData'. [D:\Users\-\Desktop\flutter_meedu_videoplayer\package\example\build\windows\flutter\flutter_assemble.vcxproj] /C:/Users/-/AppData/Local/Pub/Cache/hosted/pub.dev/helpers-1.2.0/lib/helpers/misc_build/build_color.dart(109,42): error GD65BB2B6: The getter 'buttonColor' isn't defined for the class 'ThemeData'. [D:\Users\-\Desktop\flutter_meedu_videoplayer\package\example\build\windows\flutter\flutter_assemble.vcxproj] C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: la compilazione personalizzata per 'D:\Users\-\Desktop\flutter_meedu_videoplayer\package\example\build\windows\CMakeFiles\205649b68d02cc4897ce61264a7c9555\flutter_windows.dll.rule;D:\Users\-\Desktop\flutter_meedu_videoplayer\package\example\build\windows\CMakeFiles\808581536beb0a9b893da9de0aa8029b\flutter_assemble.rule' � stata terminata. Codice: 1. [D:\Users\-\Desktop\flutter_meedu_videoplayer\package\example\build\windows\flutter\flutter_assemble.vcxproj] Exception: Build process failed. Exited (sigterm)
This happens both on Windows and Linux.
This is my flutter doctor:
`Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.10.0, on Microsoft Windows [Versione 10.0.22621.1702], locale it-IT)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Enterprise 2019 16.11.19)
[√] Android Studio (version 2021.1)
[√] VS Code (version 1.78.2)
[√] Connected device (3 available)
[√] Network resources
• No issues found!`
Can you help me?

Do flutter pub upgrade
It should get fixed.

to be safe use, flutter_meedu_videoplayer: ^4.2.10

@0Franky is it safe to assume this is fixed?

Hi @zezo357,
I was busy with the PR code.
I just checked and I was able to launch the app correctly after upgrading to 3.10
I think is fixed.
Thank you again!


use nvidia-smi instead of obsolete pynvm

Closing this because I rebranded and published my own package, feel free to use that instead :)


<EMAIL_ADDRESS>hash check failed

It seems that they updated on 11/28/2018 to new version <IP_ADDRESS>

Fixed in https://github.com/lukesampson/scoop-extras/pull/1477


Disable ppi group in BufferedUarte drop

Solve the issue where power consumption stays high after dropping BufferedUarte

bors r+


Make floating menus not switch to nearby widgets on hover except when they are sibling widgets

Currently, if you stray your mouse within 100px (before the floating menu disappears), and there is another widget which spawns a floating menu, it is designed to switch to that floating menu. This is by design, inspired by Blender, and is useful for things like the window menu bar (File, Edit, ..., Help) and neighboring dropdown menus in an options bar, for example.
But it should only happen when things are actually neighbors. This means their input widget is a sibling within the same container div. We need to check if that's the case, and only allow a transfer to the other widget in that circumstance. Perhaps it should even be opt-in by applying a data-allow-floating-menu-transfer attribute to the parent div.
Some examples of places we don't want this to happen, where it's happening right now: the primary/secondary color picker, rows in the Properties panel, between the tool options bar and the window menu bar, and others.

If I recall correctly, I started working on building this and there may be some partially-implemented code in place for it. Feel free to adapt or remove that. I think there is, for example, already a data- attribute based on this idea.


Explain  EVENT_TYPE column or remove

From the specs:
EVENT_TYPE type: bit field (in FITS tform=32X)
        Event quality partition.

Why is this a bitfield?
What is the meaning of the 32 bits?
What shall this column be used for?

This EVENT_TYPE came from the original event spec by @kosack . Karl, maybe you can comment?
Fermi also has EVENT_TYPE, but I think they use INT , not BITFIELD?
See my comment here: https://github.com/open-gamma-ray-astro/gamma-astro-data-formats/issues/119#issuecomment-408022392
Probably we should add a glossary entry explaining what the idea behind event type is (same as Fermi).
@MaxNoe or anyone - If you have time to send PRs for the spec, that would be great. If not I'll try to address these comments soon.

For IACTs or any data, the idea is that the definition of event class and type are left to the instrument. EVENT_CLASS is provenance, or possibly used when looking up IRFs in a CALDB (not specified yet).
EVENT_TYPE is not used by science tools at the moment, but in the future could be in a similar way as Fermi, i.e. to associate with IRFs and have multiple types in a joint analysis.

If you have time to send PRs for the spec

I would like to. However, I have no Idea what this field is supposed to contain, this is why I created this issue.

I tried to address this issue. See https://github.com/open-gamma-ray-astro/gamma-astro-data-formats/pull/116#issuecomment-408611796
I don't think I can explain it better. It's just a few people that are starting to prototype and use EVENT_TYPE, really defining it in the spec and using it like e.g. Fermi-LAT did is future work that will likely take another 1-2 years.
OK?
Closing this issue now. If you have a specific suggestion for a change, or to improve the explanation, please re-open or send a PR or open a new issue.


As a grid operator I want to be able to change the location details of a metering point

Benefit hypothesis
As a grid company
We want to be able to update the location details of a metering point
So that we can ensure that the data is always up to date
Description
It must be possible for a grid company to update metering point master data after a metering point has been created. So once a metering point has been created it should be possible immediately after to update metering point master data. The things in scope for this story is the request from the grid company, validation of the message and accept/reject the request. The information to current and future balance supplier is treated in a separate story.
This story enables the grid company to update the location details for a metering point
Acceptance criteria

[ ] It must be possible for a grid company to send in a request for update metering point master data with business reason update metering point master data

[ ] If the request is rejected an reject message is generated and sent to the grid company.

[ ] If the request is approved an accept message is generated and sent to the grid company.

DoD

[ ] All tasks have been completed
[ ] All acceptance criteria have been completed
[ ] Unit test performed
[ ] Integration test performed
[ ] Tested
[ ] Accepted by business
[ ] Solution is deployed to test environment

Is solved in #299.


Writing gimie output to file instead of shell not consistent

Using

returns a unicode decode error (when I probe numpy github) However, if I put gimie repo as the repository to scrape, it works no problem. I don't understand why the difference between the two repos could cause a character encoding error.

This probably happens because there are unicode (e.g. russian, japanese) characters in some names and the windows console apparently does not support them by default. Does this solve your problem? https://stackoverflow.com/a/32176732/8440675


fix gateway name

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

fix #667
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #672 (165e0ea) into main (a554ee1) will decrease coverage by 0.05%.
The diff coverage is 12.50%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #672      +/-   ##
==========================================
- Coverage   35.63%   35.59%   -0.05%
==========================================
  Files          73       73
  Lines       10447    10449       +2
==========================================
- Hits         3723     3719       -4
- Misses       6438     6443       +5
- Partials      286      287       +1

Files
Coverage Δ

pkg/ingress/kube/ingress/controller.go
62.27% <100.00%> (-0.04%)
:arrow_down:

pkg/ingress/kube/ingressv1/controller.go
5.42% <0.00%> (+<0.01%)
:arrow_up:

pkg/ingress/kube/kingress/controller.go
42.49% <0.00%> (+0.07%)
:arrow_up:

pkg/ingress/kube/common/tool.go
50.19% <0.00%> (-0.99%)
:arrow_down:

... and 1 file with indirect coverage changes


Add image to Meme Generator example

In examples/index.html, there is an example #7 with 2 text boxes aligned and styled as in a meme. But the example is lacking background image.
Add a meme-like image bellow the text in this example

I'm gonna pick this one

Thank you @Rasmuskrogh
If you have any questions, let me know.

@all-contributors please add @Rasmuskrogh for code


Can't find color-util.js file?

Hello,
could you tell me where I can find the final color-util.js file?
Thanks

Thank you, will try it :)


make add customer node support update role

Related Issue: https://github.com/rancher/rancher/issues/11341
Add support to update role for adding customer node.

Just add the state "updated" in node type, if the custom node update, will set to updated state first and then provision. Related types PR https://github.com/rancher/types/pull/297, could you help talk a look? @alena1108 @StrongMonkey

LGTM. @alena1108? do you think NodeConditionUpdate will be a good name for updating?

also do not include trash.lock file in commits.

LGTM


Develop Quiz LeaderBoard

Description:
Implement a leaderboard feature in the flashcard quiz application to enhance user engagement and provide a competitive aspect to the quizzes. The leaderboard will display the top users based on their quiz scores, encouraging users to improve their performance.
Requirements:
User Score Tracking:
- The application must track the scores of all users after completing quizzes.
- Scores should be calculated based on the number of correct answers.

Sorting Mechanism:
- The leaderboard should automatically sort users based on their scores in descending order.
- Users with the same score should be sorted by the most recent attempt.

Refresh Mechanism:
- The leaderboard should refresh automatically after each quiz completion.

Visual Design:
- The leaderboard must be visually appealing and consistent with the overall design of the application.
- Include animations or transitions for a smoother user experience.

Acceptance Criteria:
Functionality:
- Users can view their scores and rankings on the leaderboard after completing quizzes.
- The leaderboard displays the correct user information and scores.

Sorting and Ranking:
- The leaderboard correctly sorts users based on their scores and completion times.
- Users with identical scores are ranked correctly based on the fastest completion time.

This PR handles the fix for the issues
https://github.com/WolfByteCollective/FlashCards/pull/8


Interpolate for real

Implements and utilizes the compose.Interpolator interface. Closes #266.

merging to manifest branch


⚠ Bofrost.es has degraded performance

In 6dc4635, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1467 ms

Resolved: Bofrost.es performance has improved in fd58cda after 6 minutes.


Engine networking reworked to use Swarm 2 store etc

@mrjana
API convergence; integration with Engine

Done. /cc @mrjana


Fixes spelling in doc

This is will conflict with https://github.com/apache/trafficserver/pull/5387 . Let's get that merged in before this one.


Kali Linux post docker install update error!

After installing docker I can apt-get upgrade my system but when I apt-get update I receive the following error(s):
Hit:1 https://packages.microsoft.com/repos/microsoft-debian-stretch-prod stretch InRelease
Ign:3 https://download.docker.com/linux/debian kali-rolling InRelease
Err:4 https://download.docker.com/linux/debian kali-rolling Release
404  Not Found [IP: 2600:9000:201a:7400:3:db06:4200:93a1 443]
Get:2 https://kali.download/kali kali-rolling InRelease [30.5 kB]
Get:5 https://kali.download/kali kali-rolling/main i386 Packages [17.1 MB]
Get:6 https://kali.download/kali kali-rolling/main amd64 Packages [17.2 MB]
Reading package lists... Done
E: The repository 'https://download.docker.com/linux/debian kali-rolling Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Does anyone have a clue how to fix this issue???

Seeing a similar issue.  Maybe changes coming since the release of 2019.1?
Get:1 http://kali.download/kali kali-rolling InRelease [30.5 kB]
Ign:2 http://kali.download/kali kali-rolling/non-free Sources
Get:3 http://kali.download/kali kali-rolling/main Sources [12.8 MB]
Ign:2 http://kali.download/kali kali-rolling/non-free Sources
Ign:4 http://kali.download/kali kali-rolling/contrib Sources
Get:5 http://kali.download/kali kali-rolling/main amd64 Packages [17.2 MB]
Ign:4 http://kali.download/kali kali-rolling/contrib Sources
Ign:6 http://kali.download/kali kali-rolling/contrib amd64 Packages
Ign:6 http://kali.download/kali kali-rolling/contrib amd64 Packages
Ign:7 http://kali.download/kali kali-rolling/non-free amd64 Packages
Ign:2 http://kali.download/kali kali-rolling/non-free Sources
Ign:4 http://kali.download/kali kali-rolling/contrib Sources
Ign:7 http://kali.download/kali kali-rolling/non-free amd64 Packages
Get:6 http://kali.download/kali kali-rolling/contrib amd64 Packages [375 kB]
Get:7 http://kali.download/kali kali-rolling/non-free amd64 Packages [796 kB]
Err:2 http://http.kali.org/kali kali-rolling/non-free Sources
Connection failed [IP: <IP_ADDRESS> 80]
Ign:4 http://http.kali.org/kali kali-rolling/contrib Sources
Fetched 375 kB in 4min 1s (1552 B/s)
Reading package lists... Done
E: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/non-free/source/Sources  Connection failed [IP: <IP_ADDRESS> 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

Thanks for opening this ticket, however, this GitHub issue tracker is not intended as a general support forum, but for reporting bugs and feature requests for the documentation. For other type of questions, consider using one of;

the Docker Support Forums - https://forums.docker.com
the Docker community Slack channel

I'm closing this issue because this is not an issue with the documentation, but feel free to continue the conversation after I closed 🤗


Narrowing with switch/case not working

Bug Report

🔎 Search Terms

Narrowing
Inferring
Generic Types

🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about narrowing

⏯ Playground Link

Playground link with relevant code
💻 Code

type A = { type: "a" }
type B = { type: "b" }

type inferLetterOutput<Letter extends A | B> = Letter["type"] extends "a" ? number : Letter["type"] extends "b" ? string : never

export const transformWithSwitchCase = <Letter extends A | B>(
    letter: Letter,
    input: string
): inferLetterOutput<Letter> => {
    switch (letter.type) {
        case "a":
            return parseInt(input, 10);
        case "b":
            return input.toString();
        default:
            return
    }
}

🙁 Actual behavior
I am sure this should be possible to be typed correctly. I am trying to infer/narrow the return type of a function, but once the function is returning something, I am not able to type this correctly.
🙂 Expected behavior
I am expecting the function "return" statements to be correctly typed and not raising an error.

This is a design limitation. Resolving of conditional types that involve unbound type arguments is deferred. Within the body of your function the compiler has no clue what type inferLetterOutput<Letter> is, because at this point it doesn't know what type Letter is, so it can't verify the value you return matches.
You should use overloads in this case instead.

duplicate of #33912

There's also the fact that, in general, narrowing the type of the argument letter doesn't tell you anything about the type parameter Letter.


Facebook Messenger fix

Can edge-mqtt.facebook.com be added to the whitelist? If this domain is blocked, Messenger will act up, and refuse to connect.

@kyle95wm It is now added to optional-list.txt


Broken Tracker Logic: Bow requires Varia Suit, Varia Suit Requires Bow

Checking the spoiler log, it seems to think I can get past the Armos Knights without a bow.
Seed:<PHONE_NUMBER>
Settings:
settings_string.txt

Do you mean the icy Armos Knights in GT? Between the sword, the hammer, and the ice rod, you should be able to take them down. It'll take a bit, though!

Huh, I legitimately didn't think they were vulnerable to anything else. Thanks

No prob!


max_problem_size settings

Hi there,
Nice tool, but I have been confused by the max_problem_size setting.
for s, e in zip(fixed_c_idxs[:-1], fixed_c_idxs[1:]):
    assert e-s+1 <= max_problem_size+5

in the segment (line 712)
Why raise an error here rather than skip the unsatisfied pair index.
Looking forward to your reply,
Logan

Hello Yuelong. This is a bug. I'm working on fixing it. Meanwhile, you can
comment the two-line for loop to ensure running.
On Mon, Jul 12, 2021 at 7:37 PM Yuelong Logan Chen @.***>
wrote:

Hi there,
Nice tool, but I have been confused by the max_problem_size setting.
for s, e in zip(fixed_c_idxs[:-1], fixed_c_idxs[1:]):
assert e-s+1 <= max_problem_size+5
in the segment (line 712)
Why raise an error here rather than skip the unsatisfied pair index.
Looking forward to your reply,
Logan
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vpc-ccg/freddie/issues/31, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABP6AOPTJRV3C5MXM6XXJ2LTXORGRANCNFSM5AIAXA3A
.

--
Baraa Orabi
PhD Student
Vancouver Prostate Centre


[occm] add priorityClassName to helm chart

What this PR does / why we need it:
ability to add priority class for occm
Special notes for reviewers:
Release note:
NONE

/ok-to-test
Not that I think these have test coverage?

/ok-to-test
Not that I think these have test coverage?

I didn't see that here were tests for the helm chart

I didn't see that here were tests for the helm chart

IIRC there is no helm chart test ..

/approve

/lgtm
Makes perfect sense to me.


nixos/minio: Allow multiple data directories for erasure coding.

Motivation for this change
Allowing minio to use multiple data directories for erasure coding.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @aanderse @bachp

I have neither Minio nor Nix specific knowledge, but to be on the correct side, there should be an option to enable erasure coding that invalidates the single dataDir option and requires a list of paths instead. This complicates the code and I don't know sure what is the idiomatic way of dealing with mutually exclusive options in NixOS. If you think I'm on the correct track I'll read on the docs to implement it.
PS: Minio is quite blunt with this, you just provide single or multiple paths as arguments its server and that's all.

I'll be happy to review this later and give some thoughts and pointers.  I'm running a minio cluster at work and have some idea how it works these days.

ping @arianvp

What's the status here? Thanks!

It works with the following configuration (rebased on the master):
https://gist.github.com/taku0/0ffd5caf9770cfdeda8674e4a58eb643
rm -f nixos.qcow2 && nixos-rebuild build-vm -I nixos-config=./configuration.nix -I nixpkgs=. && ./result/bin/run-nixos-vm

Please update nixos/doc/manual/release-notes/rl-2105.xml and change commit message to nixos/minio: allow multiple data directories for erasure coding.

Updated my master, rebased this branch on it, updated release-notes.
The issue is, there's no mention of release-notes in CONTRIBUTING.md, and two times it was referred in this PR as a "changelog", which can't be found in the repo.

Could you also change the commit message to nixos/minio: allow multiple data directories for erasure coding and squash the two commits?

Could you also change the commit message to nixos/minio: allow multiple data directories for erasure coding and squash the two commits?

I could and I did, but could I ask why? Isn't it done automatically on PR merge? Github has the option, and it's surely less error-prone. The PR title has to become the commit message automatically (if PR has more than one commit). No jumping through hoops necessary.
Again, I would have done already it if it was listed as a requirement in CONTRIBUTING.md.

nixpkgs use merge commits rather than squashed commits. The commit message written on merging is for the merge commit, not individual commits.

nixpkgs use merge commits rather than squashed commits. The commit message written on merging is for the merge commit, not individual commits.

Understood. Sorry, my bad. Reread the nixpkgs manual and found the required actions. Not sure they were there when I authored the PR first. I think some of the necessary steps should be lifted to CONTRIBUTING.md so they are harder to miss.


Add p004 Swift Implementation

@Sentdex This implementation more closely matches what you are doing in the video series. Please merge unless you have suggestions I need to re-implement.
I would love to continue making these for the duration of this series.

Andrew does this require swift for tensorflow (I believe that it does)? Or can you give the arena or nef command I need to generate the playground that can run it?
I like the simplicity of this approach but do note a couple of concerns:

It does appear to require swift for tensorflow.. in which can we can just import numpy from python directly. And, I thought the point of this topic was specifically to do the work without using libraries like tensorflow.
there's no gaussian random number seed .. I bet you can fix that.

Hi Robert!
Yes, this does require Swift for Tensorflow but this is not dissimilar to what sentdex is doing in the video series. While he initially shows how to perform certain operations, after the explanations have been given he resorts to using external libraries like numpy.
Maybe we can import numpy that feels less swifty than using the Swift for Tensorflow module which is the closest counterpart to a library like numpy.
Honestly, I am hoping somebody creates a nice library in swift for doing numpy like operations.

I think the python can only be imported cleanly , to be able to use bumpy, with swift for tensorflow. I wouldn’t be against using a separate folder for swift for tensorflow, But since it is a literally a separate language I think it is not good for swift

Well, I don't think importing numpy libraries is either. Why even write a swift version if we are just using 50% python code?
@robbiemu I have a solution lets to reimplement numpy from scratch in swift :D
@Sentdex What is your opinion on this? Do we really need a separate folder if we are using Swift for Tensorflow? All of the deep learning people using swift are going to have familiarity with this technology. I don't think it's unreasonable to use but ultimately it's your call.

Ahh sorry for the misunderstanding. To be honest my only experience with swift has been using the S4TF module, I honestly didn't know it was a separate language. I thought it was a library for Swift.
I will close this PR and re-open with another folder :-) Nice work on doing lots of the other reimplementationsf rom scratch. They look great.

please do - This all is just my opinion but, I think there is some real merit to a swift for tensorflow variant. Tensorflow is a big name in this field. The fact that they are putting their full weight into bringing it to Swift carries a lot of gravity and value to that implementation: long story short, even more than a typescript version, I think a swift for tensorflow version is merited.
Eventually, their changes might become a core part of swift, and then it won't be a variant any more. That appears to be the desire of some of the core developers. It just hasn't happened yet.

Agreed. Especially with people like Chris Lattner heading up the project. They are putting so much effort into making this the best possible tool they can! Thanks for the feedback man.


Continuous profiling on demand

Regarding continuous profiling, I see that for go applications we can limit targeted pods by using annotations.
However I wonder if something similar can be used also for kernel ebpf profiling ?

Use case is - in cluster we have a lot of pods, some of them short living batch jobs we would like not to be profiled


⚠ Bofrost.be has degraded performance

In 2cd3422, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2305 ms

Resolved: Bofrost.be performance has improved in da76a2c.


Add size prop to SelectMenu component

This PR introduces the size prop to the SelectMenu component. I have introduced an example in the docs as well, let me know if you want me to update the order of that section 👌🏼
Note
You can independently control the size of the SelectMenuSearchInput via the searchInputProps prop with the size key.

Thanks!!


Prepare the implementation of the new gitops structure

Signed-off-by: Romain Arnaud<EMAIL_ADDRESS>

Marked as draft because I'd like PR#76 to be merged first, which will force me to rebase.
I'd still like to start gathering feedback.


Markup feeds with microformats2

Marking up each room as a microformats2 h-feed of h-entry messages would provide a simple way of beginning to bridge matrix to the indieweb people.

well I got a schema.org based WIP commit https://github.com/MTRNord/riot-static/commit/8b913152423c83b65867d1844ea7eea2b35a4dfb @non-Jedi Not sure if that fits their needs (?)

@MTRNord: That's great! But it definitely wouldn't close this issue.
The philosophy behind microformats is a lot different than schema.org, it's the more established technology in the semantic web field, and it's also not in any way technically inferior to microdata (which schema.org builds on). The philosophy behind microformats is that web standards should be built/specced in a collaborative, open way for the needs of the community (through W3C). Schema.org was kinda just handed down to us from on high. This is why the indieweb uses microformats rather than schema.org.
I in no way want to discourage you from adding schema.org markup. A page without semantic markup gaining semantic markup is always a positive! But in the future, I'd like to encourage you to consider going with microformats over other semantic markup technologies.

actually I take back what I said about microformats coming from W3C. The W3C recommendation for semantic web is RDFa; take that as you will.


Allow to set custom repo

This can be used for an action workflow in Umbrel itself which builds a test OS image. I don't know if you want his feature, and I'm working on the Umbrel part, commit 2 of https://github.com/AaronDewes/umbrel/pull/9 is an example for that, but the build is not finished yet, and the image isn't tested. Please ignore branch name and commit name, they'll be changed anyway when merging this PR. (if you want this feature and merge the PR)

LGTM.

Test image now at https://github.com/AaronDewes/umbrel/suites/1031073137/artifacts/13650489.

Also tested the image, looks good. Haven't tested with a custom UMBREL_REPO but we can do that later.

This doesn't work, I'm currently trying to debug this and fix it.

Found the fix, actually not related to this repo, but to the actions workflow that builds this.


Chat history available across multiple devices

Is your feature request related to a problem? Please describe:
The problem is using bolt.new across multiple devices.
The chat history created from one device is not available in another's chat history - quite a shame given you can spend hours on creating one app and not accessible from another device sucks.

Describe the solution you'd like:

Make all chats history available across devices
Describe alternatives you've considered:

Additional context:

Appreciate the feedback! We are aware of this issue with chat persistence. Temporary workarounds and updates can be found here: #39. (Go to stackblitz.com, login (same credentials as Bolt), click Collections on the left-hand side, click Bolt Collection). Appreciate your patience as improvements continue to be made.


[cleanup] Detect target environment

Detect the target environment (in macros.h) by examining compiler
defined preprocessor symbols.  Define one or more of
OT_PLATFORM_TARGET, OT_PLATFORM_RV32 and OT_PLATFORM_HOST depending
on the compiler target.
Eliminate use of MOCK_MMIO in favor of OT_PLATFORM.  The mmio and other
target specific libraries will never work on the host (unittest) platform.
The only versions of such libraries which make sense are the mocked
libraries.
Relax the target_compatible_with constraints on many of the Mask ROM's
cc_library targets.  Being compatible only with OPENTITAN_CPU causes
many of the unittests to be skipped.

Signed-off-by: Chris Frantz<EMAIL_ADDRESS>

I'm going to suspend work on this PR until we transition the Mask ROM to bazel and eliminate meson.  There are too many failures with this change and the current structure of the meson build and it's not worth the effort to fix meson considering it's impending elimination.

Obsolete.


Adding example demonstrating how to customize the memory management for a component

adding traits::component_heap_type
flyby: adding `local_new(launch::sync, ...)
flyby: don't bind gids that hold lva

It would be great if someone could review and approve this - I really want to use the possibility of having a custom allocator for certain types. Thanks a ton @hkaiser for bringing this in and so quick!