Error when rendering BackgroundVideo component

Hi all,
as the title says I'm encountering a client side issue when rendering the BackgroundVideo component.
This seems to be a problem correlated with a difference between what is rendered on the server and what is rendered on client.
The problem
Next gives this error:
Unhandled Runtime Error
TypeError: Cannot read properties of null (reading 'onError')

Call Stack
eval
node_modules/hls.js/dist/hls.mjs (24580:0)

Investigating in the console we can see this other error:
Warning: Extra attributes from the server: data-video
    at video
    at eval (webpack-internal:///(app-pages-browser)/./node_modules/@mux/mux-video-react/dist/index.mjs:8:407)
    at eval (webpack-internal:///(app-pages-browser)/./node_modules/next-video/dist/components/players/background-player.js:17:9)
    at div
    at eval (webpack-internal:///(app-pages-browser)/./node_modules/next-video/dist/components/video.js:24:9)
    at eval (webpack-internal:///(app-pages-browser)/./node_modules/next-video/dist/components/background-video.js:15:11)
    at WrapBackgroundVideo (webpack-internal:///(app-pages-browser)/./src/components/WrapBackgroundVideo.tsx:14:11)
    at div
    at MotionComponent (webpack-internal:///(app-pages-browser)/./node_modules/framer-motion/dist/es/motion/index.mjs:49:65)
    at div
    at MotionComponent (webpack-internal:///(app-pages-browser)/./node_modules/framer-motion/dist/es/motion/index.mjs:49:65)
    at MotionConfig (webpack-internal:///(app-pages-browser)/./node_modules/framer-motion/dist/es/components/MotionConfig/index.mjs:32:25)
    at RootLayoutInner (webpack-internal:///(app-pages-browser)/./src/components/RootLayout.tsx:275:11)
    at RootLayout (webpack-internal:///(app-pages-browser)/./src/components/RootLayout.tsx:526:11)
    at body
    at html
    at RedirectErrorBoundary (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/redirect-boundary.js:72:9)
    at RedirectBoundary (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/redirect-boundary.js:80:11)
    at NotFoundErrorBoundary (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/not-found-boundary.js:54:9)
    at NotFoundBoundary (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/not-found-boundary.js:62:11)
    at DevRootNotFoundBoundary (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/dev-root-not-found-boundary.js:32:11)
    at ReactDevOverlay (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/react-dev-overlay/internal/ReactDevOverlay.js:66:9)
    at HotReload (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/react-dev-overlay/hot-reloader-client.js:295:11)
    at Router (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/app-router.js:159:11)
    at ErrorBoundaryHandler (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/error-boundary.js:100:9)
    at ErrorBoundary (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/error-boundary.js:130:11)
    at AppRouter (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/components/app-router.js:436:13)
    at ServerRoot (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/app-index.js:128:11)
    at RSCComponent
    at Root (webpack-internal:///(app-pages-browser)/./node_modules/next/dist/client/app-index.js:144:11)

The code
I use the BackgroundVideo component without embedding the content inside, I take care of putting it behind the content myself, I don't think this could create the issue (I even tried to use it just like the docs say, like using it to wrap my content that needs to be displayed over it, but it didn't change the error).
'use client'

import BackgroundVideo from 'next-video/background-video';
import landingVideo from '/videos/landing.mp4?thumbnailTime=0';
import clsx from 'clsx';

export function WrapBackgroundVideo({
  className,
}: {
  className?: string
}) {
  return (
    <BackgroundVideo
      src={landingVideo}
      className={clsx(
        'next-video-container-absolute -z-50 -top-14 w-full',
        className
      )}
      disableTracking
    />
  )
}

Also, I notice that when loading the page, the thumbnail appears to be out of place before the video is loaded.
Conclusion
I'm trying to understand what I'm doing wrong on this. If anyone can help it would be greatly appreciated.
Thanks!

thanks for the report!

I've seen the first hls.js onError bug as well, luckily it's only appearing in next dev. In production there is no error.

The hydration data-video mismatch I haven't seen, it's not an attribute next-video sets.

The out of place thumbnail is difficult to debug, do you have an example online? maybe it's the CSS classes.
It's not an issue in our demo: https://next-video-demo.vercel.app/background-video

Hi @luwes, thanks again for responding.
I've resolved the issue about the out of place thumbnail, it was my fault on how I was trying to "retrofit" the next-video component without doing too much refactor. At the end with a bit of rework I was able to completely adapt it to my website and have the thumbnail in the right position while the video is loading.
About the actual issue reported, as you said, I'm also seeing the errors (both of them) only on dev. When I'm building and running of a prod build the errors do not show up anymore.
Is there a plan to fix this errors from showing up also on next dev? If not, do you have any idea on why it could be happening? I would like to help getting this fixed since my company website will be using this library 😀
Again, thank you so much for your help!

Happening with import MuxVideo from '@mux/mux-video-react' during dev only as well. Exactly the same error

Getting the same issue. But only when I use BackgroundVideo. NextVideo works fine.
`1 of 1 error
Next.js (14.2.3)
Unhandled Runtime Error
TypeError: Cannot read properties of null (reading 'onError')
Call Stack
eval
node_modules/hls.js/dist/hls.mjs (24569:1)`


DataLakeStoreAccountClient or DataLakeStoreAccountManagementClient

At Azure Data Lake Store modules for Node.js there is an object DataLakeStoreAccountClient created in the example.
But in the doc there is no mention of it. Though there is DataLakeStoreAccountManagementClient. Is it the same thing? Which one should be used?
Same question with DataLakeStoreFileSystemClient and DataLakeStoreFileSystemManagementClient

Thanks for reporting @JeanBaptisteScellier and our apologies for not responding sooner.
The page Azure Data Lake Store modules for Node.js has since been updated multiple times and does not have a reference for DataLakeStoreAccountClient anymore.
Please log a new issue at https://github.com/Azure/azure-sdk-for-js for any questions on how to use the data lake store modules for nodejs


t(emporal)PARAFAC2's temporal smoothness penalty

Implementation of temporal smoothness penalty, as presented in:

C. Chatzis, M. Pfeffer, P. Lind and E. Acar, "A Time-Aware Tensor Decomposition for Tracking Evolving Patterns," 2023 IEEE 33rd International Workshop on Machine Learning for Signal Processing (MLSP), Rome, Italy, 2023, pp. 1-6, doi: 10.1109/MLSP55844.2023.10285943.

This PR essentially adds the custom penalty class, (TemporalSmoothnessPenalty) to penalties.py.

Thank you very much for the thorough suggestions and help @MarieRoald!
I think I have addressed all of the raised issues and I added a small test test_A_assembly in tests/test_penalties.py that checks that both the efficient approach you proposed and "hard-coded" approach I had initially have the same result.
Kindly let me know what you think!

Hi, are there any updates on this? Thanks in advance :)

Looks good, but we need to know if the tests run. For some reason, the CI/CD pipeline doesn't want to trigger, so I made some changes to the .github/workflows/Tests.yml on main.
I tried to push the changes directly on top of your fork, but I wasn't able to. So I think that either, you need to merge main into your feature branch or make it so I can push to your branch.
To merge, I think it should work if you:

Make sure that my repo is added as a remote. Run git remote -v to list all remotes, there should be a remote with the name upstream (or something similar) that points to my repo. If there is no remote with the url https://github.com/MarieRoald/matcouply.git (or the SSH-equivalent), then you should run git remote add upstream https://github.com/MarieRoald/matcouply.git.
Check out main and pull latest changes: git checkout main followed by git pull upstream.
Finally, check out your branch and merge main: git checkout tPARAFAC2 followed by git merge main.


Add a new jsdoc plugin to fix event names

Originally, I was going to vendor the upstream templates here, but this change can be made with a simple plugin.  For bigger changes, we still may need to customize the jaguar template.

Codecov Report

Merging #708 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #708   +/-   ##
=======================================
  Coverage   95.27%   95.27%
=======================================
  Files          83       83
  Lines        8980     8980
=======================================
  Hits         8556     8556
  Misses        424      424

Continue to review full report at Codecov.

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


Reverting cherry-picked commits from qt5.11 topic branch

Changes reverted due to error on build.

When i did the initial pull request i didnt test them cos i was quite confident it would work. The reason i want to revert changes is because the bug/issue is on the master. I will continue working on it so that i fix this.

Apparently the error "internal compiler error killed (program cc1plus)" was related to my environment. The built had no failures on other environments therefore i'm closing this request.


docs: remove server.force

Description
server.force was removed in #8280.
refs #8398
Additional context
The following options were missing from docs. Most of them are experimental, so it is intended?

optimizeDeps.needsInterop
optimizeDeps.devScan
optimizeDeps.extensions
optimizeDeps.disabled
server.preTransformRequests
experimental.importGlobRestoreExtension
customLogger

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[x] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks for creating this list. Let's discuss it in a team meeting. Some are not documented because they are experimental and specific to a very small fraction of users (extensions for example) and some others because they were just added tagging them as experimental just to be able to move forward with the alphas (needsInterop). We still need to discuss the naming of these. I added some to the Migration guide to help the ecosystem maintainers when testing the current alpha.
Placing it on hold until we talked with the team. Maybe server.force should remain and we need a new build.force for example.

It looks like there may also be an undocumented configFile: false option?

I renamed force to optimizeDeps.force as we discussed.


⚠ Bofrost.lu has degraded performance

In 2651c1e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2532 ms

Resolved: Bofrost.lu performance has improved in d6cffc0 after 6 minutes.


reduce duplicate code for the zone aware callbacks

abstract the base functionality and pass in a capture variable instead of having a separate method for each value of capture.

I signed cla


[RFE] - Feature Request : Add support for Linkerd

Linkerd is an amazing alternative to Istio. It would be good to have native integration in Rancher just like what we have for Istio.

As end user for both projects for some time, my thoughts on some integration points would be:

Multi-cluster: This was added to linkerd with 2.8, rancher is also multi-cluster management platform so I think configure, install or enable east-west traffic between clusters on rancher UI and API would be interesting, especially enabling when creating new clusters. Linkerd multi-cluster capabilities

Adding apps to mesh: Since rancher has projects which contains namespaces and distributes secrets between them, I think we could activate mesh on specific projects. So when we create new namespaces in the project, we automatically inject all apps inside it. Also deploying a single app in UI could have "add to mesh" tick so if we don't want to enable mesh for whole cluster, we can still do that without dealing with CLI or complicated ways. Linkerd service injection

Rotation of certs: We can automatically rotate certs easily with both rancher and linkerd. It's not much but doing both in same place would be meaningful. Linkerd cerrs rotation

Network metrics for apps in Rancher UI: Linkerd creates network metrics for meshed apps and also can catch error rates, latency etc. Linkerd already have metrics exporter so when we enable monitoring for cluster in Rancher we can also see our network metrics in grafana aswell. Linkerd metrics export

Service mesh debug: In Rancher UI we can see application logs for debug purposes. In linkerd there is a way that you can also tap into network traffic and see what is going on. Maybe we could see this also in Rancher UI so we have more areas to cover while debugging for errors. Linkerd tap

Finally API first design: With rancher, you can do nearly all the things(or all the things?) with API calls and this creates automation opportunities like terraform or http requests for simple things in our platform pipelines. Linkerd also have API first design and integration points could be standardized for future stability. Linkerd architecture

Disclaimer: I'm not associated with both Rancher or linkerd(buoyant) by any means. I'm just big fan of these 2 projects and see real value with this integration. It would also speed up service mesh adoption which Rancher already doing for kubernetes adoption.

@akin-ozer very well written 👍🏻

From the Linkerd side, would love to see this and we'd be happy to help.

Linkerd easy to Install, fastest to spun up, give us security, reliability and observability who doesn't need that. Love to see rancher take this direction and Would love to do help in any way.

Ah, Rancher! No love for Linkerd :(

Just a note for anyone else who comes across this issue: there is nothing special needed to run Linkerd on Rancher (you can just use the basic installation), and there are many happy Linkerd + Rancher users running the two together today. Hop into the Linkerd Slack if you get stuck on anything.


Preview qwik shop

Overview

What is it?

[ ] Feature / enhancement
[ ] Bug
[ ] Docs / tests / types / typos

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

On mobile the floating cart button here is distracting.
Maybe further up in the top right corner would help?


Manually bump version to avoid clash on npm

@balena/compose has been used for POC about a year ago and had releases up to v1.0.0.
Change-type: major

@balena-ci I self-certify!


[ entropy_src, dv ] RFC: RNG samples dropped along non-seed boundaries

The entropy_src IP has no real backpressure on the RNG.  It must continuously accept RNG inputs to continue monitoring them, even when the "final FIFO" is full.   Thus it must any drop unused seeds at the input of the final FIFO.   However in order to maintain verifiability data is dropped only at the final fifo, and only as complete seeds.
The DV environment works around this by keeping lists of complete candidate seeds and comparing output seeds to any possible matches.  Any candidate seed that must be skipped is assumed dropped and removed from the candidate list.
This scheme is manageable enough for verification.  If, in addition, the entropy source were to arbitrarily drop 4-bit RNG inputs along non-seed boundaries, the necessary exploration space for verification could quickly become unmanageable.
Unfortunately, disabling and re-enabling the entropy source has the effect of discarding an arbitrarily long sequence of RNG.  Currently the entropy_src does an effective reset as it is disabled:

All the packers and FIFOs are cleared
The counters within the health checks are cleared
The SHA3 conditioner is purged of all data
Once enabled again, the entire state is completely fresh.

If such a reset is done in the middle of a seed calculation, the reset is then completely equivalent to discarding the first portion of the seed.   The verification environment has no way of knowing how many RNG inputs are dropped in the process, and particularly when the conditioning is enabled, even missing one RNG input will change the output entirely.

Consider, for example, the following waveform:

The signals should are taken from inside the adaptive proportion test.  The entropy_src has encountered several failing health tests and is in the alert state.  The virtual sequencer has caught the interrupt and is trying to bring the IP out of the alert state.   At Time D (red cursor, T=361ns) the enable register is set to MuBi-False and the active_i signal (light blue) strobes low.  This reset toggle actually happens twice in this waveform, but both pulses are able to reset the FSM and pull it from the alert state (FSM state not shown).
The simulation environment however is immediately unhappy.  At T=424 ns (end of sim) the sequencer checks the watermark register for this test and the scoreboard detects a discrepancy.   The last adaptive proportion test counted 185 1's, but the scoreboard thought that there should be eight more 1's somewhere, for 193.  Why the difference?
Both values are equally plausible.   (The average for this test is should be 192 with a standard deviation of ±9.8.)  However the score board does not know when the trigger was pulled to reset the DUT.
If we look at the usual heatlh check window boundaries (signal window_wrap_pulse_i, shown as an orange trace, with pulses demarcated by cursors at times A, B and C) we see that the typical health check window is ≈40μs.  The last disable pulse appears 20μs into the last health check window.  About half the original data is thrown away but afterwards the DUT processes as usual, working for another 40μs.   As currently written the scoreboard does not know about this shift, and uses the first 40μs to calculate the test, but the DUT uses the latter 40μs.   We've thrown away 20μs of data and the scoreboard has no way of knowing which RNG samples the DUT decided to use.
Based on previous testing we have reason to believe that DUT is performing the health check correctly on this later window.  However  once this shift takes place we have no way of accurately predicting what the DUT will do from here on out.
We need to find a way to constrain/predict this behavior.

In order to reproduce this result, pull the branch issue_10135  from my fork (git@github.com:martin-lueker/opentitan.git) and run the following  command (from $OT_ROOT on WD servers):
./util/dvsim/dvsim.py hw/ip/entropy_src/dv/entropy_src_sim_cfg.hjson -i entropy_src_rng -r 1 -t xcelium --job-prefix="nc run -C ncsim_interactive -Il" -w=shm -s=1 --run-modes set_verbosity_comp_a_uvm_debug set_verbosity_comp_b_uvm_debug

This last health check window starts at T=314.3μs

Note: this might be as simple as telling the scoreboard to discard all the RNG inputs when disabled.

Fixed by #10243


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.14.9",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d268a182c56e8361e19fb781137411643312b994"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d268a182c56e8361e19fb781137411643312b994",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "nvme-rdma: destroy cm id before destroy qp to avoid use after free\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.14.9 by commit d268a182c56e8361e19fb781137411643312b994. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001745


HidHide updater gives CURLE_OPERATION_TIMEOUT

Bug description
HidHide updater gives CURLE_OPERATION_TIMEOUT error when I try to update.
Screenshots

[] I have searched open and closed issues for duplicates
[x] I am submitting a bug report for existing functionality that does not work as intended
[] I have read the project documentation and not found a solution to my problem there
[x] This isn't a feature request or a discussion topic

Time to make it more robust against unstable networks 👀

For archival purposes; I accidentally left in the timeout of 5 seconds, that might have been too optimistic for the vast majority of network qualities existing out there. Also adding some retry logic and whatever else I can do to get the stuff downloaded successfully 💪


Error in initial_state.mem

Hello !
I have a problem to solve this error:

Based on the error message, I should check my code line in here:
# Create a blank state at the start of check function
initial_state = proj.factory.blank_state(addr=0x804846D, remove_options={simuvex.o.LAZY_SOLVES})

# The flag is a bit vector containing 30 bytes, each byte contains 8 bits
initial_state.mem[0x804B060] = initial_state.se.BVS('flag', 30*8)

# Setup return address
initial_state.mem[initial_state.regs.esp].dword = 0x8049A49

I still practice to use angr. I am so happy if there is someone who want to help me to solve this error.
Thank you.

Hi! If you're trying to store raw, untyped data, i.e. your flag bitvector, you don't want to use state.mem, you want to use state.memory. In this case, you should replace your second statement with initial_state.memory.store(0x804b060, initial_state.se.BVS('flag', 30*8).

Oh my God, It works, man!
Thank you so much. I really appreciate it.

No problem :)


Removes pre-condition for mint, adds conditionals for events

I am curious to hear thoughts on this proposal. It seems to me that nobody really cares about events coming from fungible token contracts that don't include the address of the account that owns them, so I though that it might help to just not emit them if the owner field isn't set. I also figured that if the amount of tokens being withdrawn or deposited is zero, we could also skip emitting the event.
My thoughts are that if the vault isn't stored in storage anywhere, then the event is kind of meaningless, so it saves space and execution time to just not emit it, such as when we are paying rewards or moving tokens in the staking contract. We have equivalent events defined in the staking contract that are much more useful than any deposit or withdrawal events because they include the node ID or delegator ID.
If it wasn't already clear, I would want to apply these changes to the FlowToken contract also
(I also modified a few dependencies to get CI to pass, but those aren't related)

This is a tricky one.
If these changes were implemented it's a shame we can't change the Address? in these events to Address, as that would be a nice way both of signalling that the Address will always be set and of (trivially) reducing the off-chain code required to  process the events.
Removing the > 0 precondition from deposit() does mean that we can now get zero value deposits, and combining those with deposits to (temporary or newly created) Vaults that do not have a set address means we will obviously get events that contain (0, nil) as their data. Which doesn't seem very informative. But there are edge cases where it may be, and where the advantages of (a petty 😉) consistency win out for offchain observers over saving gas.
We won't always get a deposit following a withdrawal, however, as apart from anything else a Vault can always be saved to storage directly. So we would be reducing the number of cases in which events are emitted further rather than deviating from perfect consistency in withdraw/deposit pairs.
It may be the case that we should redesign the FT events to only emit some sort of exchange event where we have two addresses and a transfer between them, enforced in some way via an updated FT API. This would mean that offchain watchers are guaranteed to see only balanced withdrawal/deposits and can reason about them more simply. But it would lead to even fewer informative events, so maybe not. 😺
A good person to comment on this would be @orodio .

It seems to me that nobody really cares about events coming from fungible token contracts that don't include the address of the account that owns them, so I though that it might help to just not emit them if the owner field isn't set.

Don't want to be too pessimistic but isn't this how we end up with 'buns without sesame' ? [0]
[0] https://www.joelonsoftware.com/2007/09/11/theres-no-place-like-127001/

@bluesign you might be right. I just wanted to get some feedback about this just in case. I'm not super attached to it, but think it would be good. And I wouldn't want to go any farther than this. Can you think of a good reason not to do it?

@joshuahannan In this current situation, actually this is correct fix. But my point was about the bigger picture a bit. Maybe the main problem is having owner = nil where we should have the owner. Maybe we need some fixes on Cadence level about ownership. I feel like owner=nil should not happen, if we can prevent. ( I don't remember exactly, but if I get vault from storage I think owner sets to nil, doesn't feel correct to me )

I feel like owner=nil should not happen, if we can prevent. ( I don't remember exactly, but if I get vault from storage I think owner sets to nil, doesn't feel correct to me )

The problem is that once a Vault is removed from storage in a transaction, we do not know which account it is associated with. Even without resources from multiple AuthAccounts in a single transaction, a Vault's association with the storage of the AuthAccount that it has just been removed from may not be strong enough to warrant identifying it as the Vault's owner. If we regard the owner as the storage that the Vault is in, this becomes tautological.
It may be the case that borrowed Vaults and other resources should act differently. But resources that have been removed from storage and retain an owner address may be conceptually equivalent to dangling pointers in ways we would need to think through.


Restructure directories and scripts to better accommodate multiple algorithms along with structure for test code

Since DPS currently supports only 1 image per repository, we can only support a 1 build script within the repository, even though the intent for this repository is to support many algorithms. If we were to maintain a separate build script for each algorithm, then each time one of the algorithms is registered, the DPS image would be built to accommodate only that algorithm, and the other algorithms might no longer function (because the image would no longer contain needed dependencies).
Therefore, the build.sh file at the top of this repo should act as a unifying build script that automatically invokes any build.sh scripts found in immediate subdirectories (only check 1 level down). That is, it should automatically look for a build.sh file at the top of each top-level subdirectory, and for each one found, it should run it.
Each build.sh within a subdir should construct its own conda env and populate it with the dependencies specific to the algo within that subdir. This way, when the top-level build.sh runs a child build.sh, the child script will create a distinct conda env, specific to the algo, and thus should avoid any conflict or interference between algos, each to be run within its own conda env when DPS runs the algo.
For example:
./
+-- build.sh
+-- gedi-subset/
|   +-- algorithm_config.yml
|   +-- build.sh
|   +-- environment.yml
|   +-- subset.sh
|   +-- src/
|       +-- subset.py
|       +-- ...
+-- another-algo/
|   +-- algorithm_config.yml
|   +-- build.sh
...

In addition, for the gedi-subset subdir, move *.py files into a src subdir as our first step towards better structure to accommodate unit tests (to be added in a separate PR).
Acceptance Criteria

Move lines 10 through end of file in build.sh to new gedi-subset/build.sh (and change relative paths as necessary)
After the lines kept in build.sh (first 9 lines), add logic to iterate over top-level subdirs and for each build.sh found at the top of each subdir, execute it
Move environment.yml to gedi-subset/environment.yml, as it is specific to gedi-subset
Move gedi-subset/*.py to gedi-subset/src/*.py
Move typings dir down into gedi-subset/src dir
Move pyproject.toml into gedi-subset dir

Opened #19 Restructured Repository


move @types/node to dependencies

A partial fix for https://github.com/electron/electron-typescript-definitions/issues/43
This will enable electron/electron to run tsc checks on the generated electron.d.ts file.

❯ np patch --yolo
 ✔ Prerequisite check
 ✔ Git
 ✔ Bumping version using Yarn
 ✔ Publishing package
 ✔ Pushing tags

 electron-typescript-definitions 1.2.3 published 🎉


ARROW-8878: [R] try_download is confused when download.file.method isn't default

Originally reported #7058
download.file() can be called with different methods, mostly for legacy reasons according to the docs, but apparently some are on systems where it has been set to "wget" method. In classic R fashion, the behavior of the function changes significantly depending on how this global variable is set.
This patch should make the behavior more consistent regardless of the method used, so that the Linux installation won't proceed thinking a file was downloaded successfully when it in fact was not.

Hi ! sorry to jump in but I still have problems running install_arrow() on linux (with firewalls in place). Should "libcurl" be the right choice (instead of "wget") ? It does not work for me. thanks!

Could you open a JIRA issue and provide more detail about what's going wrong?


[DC-1009] Truncate Data from RDR Export after a cutoff date

Thanks for requesting my input @dcampbell-vumc. You've already covered everything for the review so I don't have much to add. The queries are generated correctly. Your point about the NonImplementedError is accurate. I think this makes sense for setup_validation and validate_rule, but not for setup_rule. If there is nothing to set up, the rule should pass. This is called by the engine and it can break if it runs into the NonImplementedError. We use this error primarily for something that needs to be implemented for running a rule but isn't yet, causing unexpected behavior. It helps prevent the rule from running.
On a final note, I wanted to confirm that this rule is inclusive of the 8/1 date (and shouldn't cut-off at 7/31).

@nishanthpp93 @dcampbell-vumc I made the necessary changes. and I confirmed that the date should be 08/01 before starting to work on this ticket.


Release nlog 4.1 extended?

We should think/check if a 4.1 is needed of https://www.nuget.org/packages/NLog.Extended/

If nothing has changed, which looks to be the cased (besides some minor formatting), there is no reason to update the version.  Also, the core API that it depends on hasn't changed either.

OK thanks @kevindaub !


Create Testing Plan

All completed items in the VOD improvements epic need to be tested
All Catalyst integration points should be tested
SDK and any new additions need to be tested
QA tickets should be created on Studio board and assigned

It's gonna be really tight 😆
On Tue, 23 Aug 2022, 10:16 pglowacky, @.***> wrote:

Assigned #1211 https://github.com/livepeer/studio/issues/1211 to
@victorges https://github.com/victorges.
—
Reply to this email directly, view it on GitHub
https://github.com/livepeer/studio/issues/1211#event-7241907839, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMJ4RZD4JES32LWKHD7HJDV2TFJBANCNFSM57LOLUOQ
.
You are receiving this because you were assigned.Message ID:
@.***>

Decision:

Post multinode and catalyst, we'll do a load test (determine how many concurrent uploads we actually support) and determine which containers and codecs we support.


gf180 user_project redesign

First itterations that:

Changed config.json back to config.tcl
Incorprated the new changes done in caravel configuration
New template def file
Default configuration is specific for gf180mcuC
Fixed user_project_wrapper and example rtl verilog to be the same as the on in caravel
Removed all simulations as they are sky130 specific

TODO:

Make the repo usable for multiple technologies

NOTE: this is based on https://github.com/efabless/caravel-gf180mcu/pull/37

This is a PR to the wrong repo.


Replay from offset

Does racecar have an API to allow the consumer to seek from a specific offset?  There are times where we want to replay but right now I'm not seeing a way to do it.

Hey @allcentury it does not. Racecar aims to be a simple wrapping framework. You can easily fallback to the raw ruby-kafka, you can look at karafka that has this option or you can PR (always welcome) :)

I have kept this in my consumer
subscribes_to "requests_topic", start_from_beginning: false
When I restart my application, It is reading all the past messages again. Any help would be appreciated.


web app resource URL appending issue

When I create a web app resource in hs, I need to give a URL for hs to invoke. My URL looks like:
http://gwdev8.cigi.illinois.edu:8080/home/apps.php?app=taudem
When I open a DEM resource, and open it with the web app, the full URL becomes an invalid URL:
http://gwdev8.cigi.illinois.edu:8080/home/apps.php?app=taudem/?res_id=8defcfa0edd848daaf0ef25271fc6703&usr=yanliu&src=hs
So it'd be good to parse the URL configured by the app creator and merge the URL parameters with the hs params in order to fix this issue.

@zhiyu - is this a relatively easy fix?
On Fri, Feb 19, 2016 at 9:37 AM Yan Liu<EMAIL_ADDRESS>wrote:

When I create a web app resource in hs, I need to give a URL for hs to
invoke. My URL looks like:
http://gwdev8.cigi.illinois.edu:8080/home/apps.php?app=taudem
When I open a DEM resource, and open it with the web app, the full URL
becomes an invalid URL:
http://gwdev8.cigi.illinois.edu:8080/home/apps.php?app=taudem/?res_id=8defcfa0edd848daaf0ef25271fc6703&usr=yanliu&src=hs
So it'd be good to parse the URL configured by the app creator and merge
the URL parameters with the hs params in order to fix this issue.
—
Reply to this email directly or view it on GitHub
https://github.com/hydroshare/hydroshare/issues/993.

@yanliu-chn @danames
how about this:
we let user input a url/string containing some pre-defined key words. like:
http://gwdev8.cigi.illinois.edu:8080/home/apps.php?app=taudem&res-id=_HYDROSHARE_RESOURCE_ID_
Here HYDROSHARE_RESOURCE_ID is a key word, we will replace it with real res id.
So the user can input any url/string, and we just search for keywords and replace them with real values.

This seems like a workable solution. We could extend it with additional
"url template terms" later as needed.
On Fri, Feb 19, 2016 at 9:55 AM Drew Li<EMAIL_ADDRESS>wrote:

@yanliu-chn https://github.com/yanliu-chn @danames
https://github.com/danames
how about this:
we let user input a url/string containing some pre-defined key words. like:
http://gwdev8.cigi.illinois.edu:8080/home/apps.php?app=taudem&res-id=_HYDROSHARE_RESOURCE_ID_
Here HYDROSHARE_RESOURCE_ID is a key word, we will replace it with real
res id.
So the user can input any url/string, and we just search for keywords and
replace them with real values.
—
Reply to this email directly or view it on GitHub
https://github.com/hydroshare/hydroshare/issues/993#issuecomment-186301567
.

Hi Drew,
It's a good solution. This solution would allow app contributor to specify their own parameter names instead of res-id defined in HS. It also allows HS to define parameters that web apps need, including data resource id, user id, and possibly authentication information, too.
Here is something in my mind from app contributor point of view:

define "variable" form in programming fashion, e.g., ${HS_RES_ID} instead of HS_RES_ID
HS should list which variables are allowed. These variables include general ones (the existing ones), resource specific ones (e.g., metadata attributes associated with that particular resource (e.g., raster)), access control variables (what if the web app consumes the data resource files and as a result, pushes back additional files to the resources? the app then needs some way to write the resource with appropriate permission). Which variables to allow needs a design.
HS should check the validity of the URL before saving the app.

Yan for clarification, are you suggesting the URL template should be like
this:
http://my.url.com/mypage.php?myvariable=abc&myid=${HS_RES_ID}&mynewparam=${HS_XXX
}
Then our app resource code will replace the ${...} with the appropriate
metadata or variable from HydroShare?
I think this is a fine solution.
Can we discuss a list of optional template parameters?
how about:
${HS_RES_ID}                        required....
${HS_RES_NAME}                 could be handy?
${HS_HOST}                           this will tell us if we are launching
from www. or playground. etc.
others?
On Fri, Feb 19, 2016 at 10:33 AM Yan Liu<EMAIL_ADDRESS>wrote:

Hi Drew,
It's a good solution. This solution would allow app contributor to specify
their own parameter names instead of res-id defined in HS. It also allows
HS to define parameters that web apps need, including data resource id,
user id, and possibly authentication information, too.
Here is something in my mind from app contributor point of view:

define "variable" form in programming fashion, e.g., ${HS_RES_ID}
instead of HS_RES_ID
HS should list which variables are allowed. These variables include
general ones (the existing ones), resource specific ones (e.g., metadata
attributes associated with that particular resource (e.g., raster)), access
control variables (what if the web app consumes the data resource files and
as a result, pushes back additional files to the resources? the app then
needs some way to write the resource with appropriate permission). Which
variables to allow needs a design.
HS should check the validity of the URL before saving the app.

—
Reply to this email directly or view it on GitHub
https://github.com/hydroshare/hydroshare/issues/993#issuecomment-186318153
.

Yes. ${...} is easier to parse using regex.
I do not know enough of HS about which attributes of a resource are defined. I know with res_id, I can go back to HS rest api to pull more info about the resource. HS_HOST may not be needed because the URL is invoked in user's browser and if the web app does not pass this back to HS, there is no way for HS to know if an app is invoked on this host. HS_RES_TYPE may be more useful than HS_RES_NAME.
Also, for the parameters available for web app URL config, the value of them must not contain special characters in a URL such as :, &, /, ?, = ... Otherwise, URL instantiation will produce invalid URL too. This is a constraint when deciding which param should be allowed in app url.

closed. tested on www


[fuzzing] downgrade version of libfuzzer for lionhead to work

Motivation
[fuzzing] downgrade version of libfuzzer for lionhead to work #5817
Have you read the [Contributing Guidelines on pull requests]
yes
Test Plan
CI
Related PRs
5817

/land


Evaluate Plate Model Performance

In this pr, the model performance is evaluated across plates 3, 3 prime, and 5 using precision-recall (pr), f1-score, and the confusion matrix. I do not store the evaluation data here, as the pr data is too large for github. Please let me know if you have any suggestions.

Thanks for reviewing @jenna-tomkinson. I added the larger evaluation data, so I will merge now!


chore: added OPTIONS method support

Checklist

[ ] I have read the coding guide
[ ] My change requires a documentation update and I have done it
[ ] I have added tests to cover my changes.

Description
Added options support in allowed methods
Motivation and context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):

This change is

I think it's a good practice to sort the list of strings in alphabetical order.

pkg/api/cors_test.go line 151 at r5 (raw file):
Previously, acud (acud) wrote…
now you are testing the wrong header. we want to see that the Access-Control-Allow-Methods header is set, not Allow. You're in the CORS test, therefore you are interested in the access control headers

Done.

🎁


Populate missing info during schema error messages

Summary
Schema type checking errors that do not use a yaml file as a data value result in confusing error messages.
The confusion lies due to the error message 'missing' information (such as a file name, line number, and contents on the line number) to print within the 'diff' section of the error message.
This is a follow on story from https://github.com/vmware-tanzu/carvel-ytt/pull/411
Description
This is a known issue in at least the following 2 scenarios.
Using starlark to 'inject' a data value when rendering a template
e.g.
--- #@ template.replace(library.get("lib").with_data_values({'foo':'4'}).eval())`

results in
Schema Typecheck - Value is of wrong type
=========================================

     :
         |
       ? |
         |

         = found: string
         = expected: integer (by _ytt_lib/lib/schema.yml:4)

Suggested improvement:
Schema Typecheck - Value is of wrong type
=========================================

    template.yml :
         |
       1 |  --- #@ template.replace(library.get("lib").with_data_values({'foo':'4'}).eval())
         |

         = found: string
         = expected: integer (by _ytt_lib/lib/schema.yml:4)

Using ytt's --data-value flag
e.g.
ytt --data-value foo=42 ...

results in
Schema Typecheck - Value is of wrong type
=========================================

key 'foo' (kv arg):
    |
  1 |
    |

    = found: string
    = expected: integer (by schema.yml:3)

Suggested improvement:
Schema Typecheck - Value is of wrong type
=========================================

key 'foo' (kv arg):
    |
  1 | foo=42
    |

    = found: string
    = expected: integer (by schema.yml:3)
    = hint: update --data-value flag arg to comply with expected schema type

Describe the solution you'd like
Populate the missing information in the above 2 cases, and any other ways that a schema type check can fail and produce missing information in the diff.

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

The current state of those error messages are very unhelpful. Most definitely something we want to address (and ideally right away) ==> "carvel accepted"

I see this work being handled in two parts:

where any values injected via a replace need to be fully converted to AST.

I'm pretty sure that the template.replace() line is the closest we can get to attributing a line-of-source for the value... otherwise, we'd have to analyze the Starlark program AST and somehow determine where a given value was added to a collection (or something?)
any nodes that don't have a location within that AST sub-tree would be attributed to that template.replace().
this is exactly what @DennisDenuto spec'ed out, above.

find a way to preserve the command-line arg input as a source line.

There is one bit of work left as part of this: improving error messages for library functions. For example:
library.get("lib").with_data_values({'foo':'4'} still reports an error without line numbers. This was a much heavier lift than originally anticipating, so we're splitting it off into a separate story.


Invoke-SqlCmd2: Support for Encrypt=True in Connection String

This should support encrypting the connection to SQL server when using a username and password. I've briefly tested this and simply added a switch parameter -Encrypt and one more field to the connection string:
if ($Credential)  {      $ConnectionString = "Server={0};Database={1};User ID={2};Password="{3}";Trusted_Connection=False;Connect Timeout={4};Encrypt={5}" -f $SQLInstance,$Database,$Credential.UserName,$Credential.GetNetworkCredential().Password,$ConnectionTimeout,[bool]$Encrypt }
Thoughts?
BTW, thanks for this function - I have used it quite a bit!

I'm thinking encryption should be the default, with a -NoEncrypt parameter for SQL servers that don't support/work with.

Hi!
Good catch. I'm usually a fan of secure defaults, but would probably want to roll this in so that it continues to work as a drop in replacement, than can have a switch flipped to use SSL.
Might be worth adding TrustServerCertificate in conjunction with this.
Have some work I'm trying to get through before the summit; might not get to this until next week, unless you want to send a quick PR?
Thanks!
Warren

Yeah, on further research it just seems that most wouldn't have this capability configured so adding it is probably good.  Maybe use the TrustServerCertificate in conjunction with the -Encrypt param.

Warren,
I'll take a look and see if I can get this added in today or tomorrow.
Thanks!

Added in PR #14. I made changes to both Invoke-SqlCmd2 and New-SqlConnection. I'm looking into adding TrustServerCertificate per Martin's suggestion, but that will probably be a new PR.

Merged - thanks Matt!

Hi!  Not sure if there's more to do, but FYI, moved Invoke-SqlCmd2 to the SQLCollaborative org.
Closing this out, if there's more to do, feel free to re-open the issue there!
Cheers!


Update the graph used in quantization tutorial

Another fix to quantization tutorial after #11285
Currently, following the steps in the quantization tutorial will lead to weird results as pointed out in #11181. This is because the graph file and the evaluation script are unmatched.
From this image recognition tutorial, there are two pretrained graphs with two evaluation scripts.

classify_image_graph_def.pb in inception-2015-12-05.tgz is to be used with the (older) classify_image.py.
inception_v3_2016_08_28_frozen.pb in inception_v3_2016_08_28_frozen.pb.tar.gz is to be used with label_image.

The weird results came from using classify_image_graph_def.pb with label_image. The graphs are different (see also models#1314), especially in the last layer. The two scripts extract information from the last layer in different ways, so it works with its corresponding graph but not the other.
Further changes?

In the image recognition tutorial (source), the usage of Python API points to option 1 (above) but the C++ API points to option 2. This might cause confusion as the two graphs/scripts are not equivalent. Now that there's a python implementation of the newer label_image by @freedomtan, should we update the tutorial to use this python implementation instead?
Should this graph transform README be updated as well? Currently it uses the 2015 pre-trained graph, hence --inputs='Mul' --outputs='softmax'. If it is updated to the 2016 graph, these should instead say --inputs=input --outputs=InceptionV3/Predictions/Reshape_1.

Can one of the admins verify this patch?

@tensorflow-jenkins test this please


verify_ssl broken in 2023.6.2

When upgrading pipenv from 2023.5.19 to 2023.6.2 verify_ssl=false seems to be ignored, resulting in the following error:
Max retries exceeded with URL: [...] certificate verify failed: self signed certificate in certificate chain

I am still able to reproduce on master. Also I tried digging into the few commits between those two versions without success.
Workaround:
Revert to 2023.5.19
Steps to replicate
Create a simple Pipefile with a private self-signed PyPi repo and verify_ssl=false
Platform
win32 (not tested on unix/linux/mac)

I wonder if it has anything to do with the _get_hashes_from_remote_index_urls pep 508 work to get hashes from the URLs ... it uses a requests session during the lock phase, and that definitely doesn't consider verify_ssl at all ... could you help me further understand what action you are taking when getting the error?

Sure, here is the full log. Please note that when using sync instead of install pipenv is able to properly bypass the ssl certificate check. This also points to a missing verify_ssl support during the lock phase.

$ pipenv install
Creating a virtualenv for this project...
Pipfile: PIPFILE_ROOT\Pipfile
Using HOME/AppData/Local/Programs/Python/Python39/python.exe (3.9.12) to create virtualenv...
[   =] Creating virtual environment...created virtual environment CPython3.9.12.final.0-64 in 9236ms
  creator CPython3Windows(dest=HOME\.virtualenvs\riKWXtd8, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=HOME\AppData\Local\pypa\virtualenv)
    added seed packages: pip==23.1.2, setuptools==67.7.2, wheel==0.40.0
  activators BashActivator,BatchActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
Successfully created virtual environment!
Virtualenv location: HOME.virtualenvs\riKWXtd8
Pipfile.lock not found, creating...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
Locking Failed!
[=   ] Locking...
Traceback (most recent call last):
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\urllib3\connectionpool.py", line 703, in urlopen
httplib_response = self._make_request(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\urllib3\connectionpool.py", line 386, in _make_request
self._validate_conn(conn)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\urllib3\connectionpool.py", line 1042, in validate_conn
conn.connect()
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\urllib3\connection.py", line 419, in connect
self.sock = ssl_wrap_socket(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\urllib3\util\ssl.py", line 449, in ssl_wrap_socket
ssl_sock = ssl_wrap_socket_impl(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\urllib3\util\ssl.py", line 493, in _ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "HOME\AppData\Local\Programs\Python\Python39\lib\ssl.py", line 500, in wrap_socket
return self.sslsocket_class._create(
File "HOME\AppData\Local\Programs\Python\Python39\lib\ssl.py", line 1040, in _create
self.do_handshake()
File "HOME\AppData\Local\Programs\Python\Python39\lib\ssl.py", line 1309, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1129)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\requests\adapters.py", line 489, in send
resp = conn.urlopen(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\urllib3\connectionpool.py", line 787, in urlopen
retries = retries.increment(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\urllib3\util\retry.py", line 592, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
pipenv.patched.pip._vendor.urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='artifactory-pm.mlp.com', port=443): Max retries exceeded with url: /artifactory/api/pypi/pm-one11cap-pypi-virtual/simple/o11pandas/ (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1129)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\resolver.py", line 845, in
main()
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\resolver.py", line 831, in main
_main(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\resolver.py", line 811, in _main
resolve_packages(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\resolver.py", line 759, in resolve_packages
results, resolver = resolve(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\resolver.py", line 738, in resolve
return resolve_deps(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\utils\resolver.py", line 1154, in resolve_deps
results, hashes, markers_lookup, resolver, skipped = actually_resolve_deps(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\utils\resolver.py", line 954, in actually_resolve_deps
hashes = resolver.resolve_hashes()
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\utils\resolver.py", line 855, in resolve_hashes
self.hashes[ireq] = self.collect_hashes(ireq)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\utils\resolver.py", line 835, in collect_hashes
hashes = self._get_hashes_from_remote_index_urls(ireq, source)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\utils\resolver.py", line 783, in _get_hashes_from_remote_index_urls
response = session.get(pkg_url, timeout=10)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\requests\sessions.py", line 600, in get
return self.request("GET", url, **kwargs)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\requests\sessions.py", line 587, in request
resp = self.send(prep, **send_kwargs)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\requests\sessions.py", line 701, in send
r = adapter.send(request, **kwargs)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\patched\pip_vendor\requests\adapters.py", line 563, in send
raise SSLError(e, request=request)
pipenv.patched.pip._vendor.requests.exceptions.SSLError: HTTPSConnectionPool(host='artifactory-pm.mlp.com', port=443): Max retries exceeded with url: /artifactory/api/pypi/pm-one11cap-pypi-virtual/simple/o11pandas/ (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1129)')))
Traceback (most recent call last):
File "HOME\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "HOME\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 87, in run_code
exec(code, run_globals)
File "HOME\AppData\Local\Programs\Python\Python39\Scripts\pipenv.exe_main.py", line 7, in
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\vendor\click\core.py", line 1130, in call
return self.main(*args, **kwargs)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\cli\options.py", line 58, in main
return super().main(*args, **kwargs, windows_expand_args=False)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\vendor\click\core.py", line 1055, in main
rv = self.invoke(ctx)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\vendor\click\core.py", line 1657, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\vendor\click\core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\vendor\click\core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\vendor\click\decorators.py", line 84, in new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\vendor\click\core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\cli\command.py", line 235, in install
do_install(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\routines\install.py", line 195, in do_install
do_init(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\routines\install.py", line 800, in do_init
do_lock(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\routines\lock.py", line 79, in do_lock
venv_resolve_deps(
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\utils\resolver.py", line 1096, in venv_resolve_deps
c = resolve(cmd, st, project=project)
File "HOME\AppData\Local\Programs\Python\Python39\lib\site-packages\pipenv\utils\resolver.py", line 990, in resolve
raise RuntimeError("Failed to lock Pipfile.lock!")
RuntimeError: Failed to lock Pipfile.lock!

This broke pipenv on my work laptop due to MITM Cisco Umbrella. Downgrading to 2023.5.19 is a workaround as mentioned above.

Could someone try out if this branch fixes the issue:  https://github.com/pypa/pipenv/pull/5728

Thank you all for your help.
2023.6.12 work well, it also fixed another bug when a private auth token was not forwarded to requirements coming from a git+https//... package.


Oddities with htmlText in textfields

There seems to be some oddities and inconsistences with textfields, i realise textfields are being actively worked on but, unless im mistaken, these issues are new (i think i probably would have noticed / heard about them before otherwise - maybe not)
Maybe something with how these are being used (below) is incorrect now?
class Main extends Sprite {
    public function new() {
        super();

        var tf = new TextField();
        tf.htmlText = 'BOLD not bold';
        Lib.current.stage.addChild(tf);

        var tf = new TextField();
        tf.x = 60;
        tf.y = 30;
        tf.htmlText = 'BOLD not bold';
        Lib.current.stage.addChild(tf);

        var tf = new TextField();
        tf.x = 0;
        tf.y = 60;
        tf.htmlText = 'RED GREEN BLUE';
        Lib.current.stage.addChild(tf);

        var tf = new TextField();
        tf.x = 0;
        tf.y = 90;
        tf.htmlText = 'RED GREEN BLUE';
        Lib.current.stage.addChild(tf);

        var tf = new TextField();
        tf.x = 90;
        tf.y = 90;
        tf.htmlText = 'RED GREEN BLUE';
        Lib.current.stage.addChild(tf);
    }
}

Latest git openfl, but also confirmed on 9.1.0
Cheers,
Ian

@ianharrigan Thanks for pointing this out Ian. I'm glad someone is awake out there. I'll try to sort this out as soon as I get the chance. Either there is something wrong with text formatting or theres a measurement issue, or a combination of the two.

actually it is neither.
https://i.gyazo.com/2703bb5f7cc5517e755b250c496cb368.gif
Everything is rendering correctly, the caret index is just not being reset properly. I'll make the simple fix later this evening.

Nice one, sounds great... i wont pretend to understand much of openfls text internals (new or old) but sounds like its an easy fix (if you know where to look and what it all means ofc :D )
Thanks again,
Ian

Yeah no problem. The road is a little bumpy at the moment. We managed to squeezed out a nice performance leap without having to rewrite the whole thing(which really needs to be done at some point to get to performance parity with competing technology). There's a lot of moving parts and its pretty spaghettified, so some hiccups are to be expected. Unfortunately, 9.1.0 was a little rushed due to being a little blindsided by haxe 4.2 changes to abstracts.

Hey Chris,
Did you try the example above in the OP? It still looks off...

(Just pulled latest openfl, maybe i need lime too, but looking at the fix it didnt look like it)

what looks off about it?

thats one thing, yeah, though now i think about it, thats probably just auto size / inital size - the other issue is that bold  seems to have been applied to the whole thing

Yeah the cutoff is just the initial width (100px I believe). I didn't notice the bold issue! Ok.

Justify isn't implemented yet. As far as

Ok so, the html tags   and  are broken as far as I can tell. Its a really perplexing issue because one textfield will effect every other textfield that is added afterwards! This is especially weird because every textfield is isolated completely.... I'll have to take a really deep look into this....

I would also consider an issue at the font level, as I've run into this a number of times in the past. It seemed like the whole font family would be stuck, but it could be something else since I usually ignored it.

Solving this might be easier then expected, when I made the markdown interpreter which includes lots of textformats it worked fine. If this approach isn't taken, we might want to do so.
(I can do it myself too, we might be best doing what I did here:
https://github.com/ShaharMS/texter/blob/9e3d4b36acccde15f4d988c5d8ec9d519a2a508d/src/texter/general/markdown/MarkdownVisualizer.hx#L129
)


classloaderFilter

请问dubbo filter中的classloaderFilter的具体作用是什么？
What's role of classfilter ?

In design purpose, switch to classloader that has loaded the interface definition, so that the implementation works with the same classloader context.


LinkedResource throws "wrong number of arguments" exception

When accessing @LinkedResource with parameters (like findAllByName(String name)) throws "wrong number of arguments" exception.
This occurs only when return type is Collection implementation. With single objects it works fine. Also Collections work fine when they are marked with @LinkedResource but have no parameters

Hi, I can't reproduce this - and we have a test to verify this works. The test has the following annotated model method:
	@LinkedResource
	List<SimpleEntity> findByNameContaining(String query);

If you're still having trouble, perhaps you could post some more details (your annotated model class, your client code, and the exception stacktrace?)
Thanks

OK. Looked into your test code. I had SearchEntity as a class in my model. Changed it to interface and it works.
Thanks! And props to you for this library it is absolutely fantastic. Using it extensively.

That's great - and thanks! I'm thrilled people are using it and finding it useful.


Pods not routable after updating deployment

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
After updating a deployment (any deployment) the pods in that deployment is no longer routable through its service endpoint.
If I look at the service that I'm trying to connect to it says Cluster-IP - <IP_ADDRESS>
And the pod itself says IP: <IP_ADDRESS>
Before updating the deployment, this is what is logged in nginx-ingress-controller when performing a successful request.

2017-08-15T12:56:53.801501493Z <IP_ADDRESS> - [<IP_ADDRESS>] - - [15/Aug/2017:12:56:53 +0000] "GET /css/style.css HTTP/2.0" 200 243 "https://zept.io/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36" 53 0.005 [zeptio-zeptio-web-80] <IP_ADDRESS>:3000 361 0.005 200

However, looking at the nginx-ingress-controller log after updating, it still says the same IP:

2017-08-15T13:08:43.621796454Z 2017/08/15 13:08:43 [error] 401#401: *231611 upstream timed out (110: Connection timed out) while connecting to upstream, client: <IP_ADDRESS>, server: zept.io, request: "GET / HTTP/2.0", upstream: "http://<IP_ADDRESS>:3000/", host: "zept.io"

Even though the new pod has the IP <IP_ADDRESS>, the controller doesn't route the traffic correctly.
What you expected to happen:
I'm fairly new to kubernetes, but to me it seems the IP of the service is not updated.
I'd say the ingress should try to connect using the new IP assigned to the newly created pod.
How to reproduce it (as minimally and precisely as possible):
I'll tell you my ingress setup, since that's probably where this goes wrong. It's setup using Helm, and has been working fine for about 1 year now. This issue came about a few months ago, and persisted after upgrading the cluster from 1.5.1 to 1.6.6
kube-lego-0.1.10
nginx-ingress-0.6.0
Anything else we need to know?:
Rebooting the agent node in ACS renews the routes and brings all the pods back online. I've use this "solution" until I updated to v1.6.6. But since that didn't solve it, I'm now trying to find what's wrong.
Environment:

Kubernetes version (use kubectl version): 1.6.6
Cloud provider or hardware configuration**: Azure Container Service
OS (e.g. from /etc/os-release): Ubuntu 16.04.2 LTS
Kernel (e.g. uname -a): Linux k8s-master-XXX-0 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Install tools: az acs create
Others:

nginx-ingress-0.6.0 is really old, try one of the newer ones.

I did that now, but it's always concerning that something like a load balancer suddenly stops working. And idea where the problem could be? ngix-controller, kubernetes dns-discovery, azure load balancer?

possibly https://github.com/kubernetes/ingress/issues/768 ???

As @caseylucas suggested, I think this is the same issue as #768.
After updating to version 0.8.0 it works fine.

Keep in mind that #768 was discovered and fixed in a later release than 0.8.0. You may want to get a newer image than 0.8.0

We're using 0.8.3, and this issue seems to persist. I've manually deleted the pod, which spawned another, but requests are still going to the old local IP.

@enVolt please update to a newer version, 0.8.3 is almost a year and half old


[Bug]: No "pre_shared_key" when using shared lib

TLS client version
master and 1.7.5
System information
Arch Linux
Issue description
When using the shared library version of tls-client, the next request does not contain the "pre_shared_key" in the "extensions" section of the test at https://tls.peet.ws/api/all, yet the Go version works as expected.
Steps to reproduce / Code Sample
I added the tls.UtlsPreSharedKeyExtension extension to the chrome_124 profile in the following way:
diff --git a/profiles/internal_browser_profiles.go b/profiles/internal_browser_profiles.go
index 350bcc9..197b6f1 100644
--- a/profiles/internal_browser_profiles.go
+++ b/profiles/internal_browser_profiles.go
@@ -182,6 +182,7 @@ var Chrome_124 = ClientProfile{
 						{Group: tls.X25519},
 					}},
 					&tls.UtlsGREASEExtension{},
+					&tls.UtlsPreSharedKeyExtension{OmitEmptyPsk: true},
 				},
 			}, nil
 		},

and after building the library, I tested it with this program:
#include <stdio.h>
#include "tls-client-linux-ubuntu-amd64-with_psk.h"

char* requestPayload =
  "{"
    "\"tlsClientIdentifier\": \"chrome_124\","
    "\"withDefaultCookieJar\": true,"
    "\"withDebug\": true,"
    "\"catchPanics\": false,"
    "\"timeoutSeconds\": 60,"
    "\"sessionId\": \"test_session\","
    "\"requestUrl\": \"https://tls.peet.ws/api/all\","
    "\"requestMethod\": \"GET\","
    "\"requestCookies\": []"
"}";

int main() {
    char* resp = request(requestPayload);
    printf("%s\n", resp);

    printf("\n-----\n\n");

    resp = request(requestPayload);
    printf("%s\n", resp);
    return 0;
}

program output: shared_lib_output.txt (The second request is missing the "pre_shared_key")
I also made a Go program to test whether the issue was only present in the shared lib: main.go
However the Go version worked correctly (golang_output.txt) and the "pre_shared_key" is present in the second request response, which leads me to believe that there is some kind of issue in the shared lib.
Please let me know if you noticed any issues with my testing approach or if there is a way to get around this problem.

Ok, I already figured out what caused the problem. I had to remove go.mod and go.sum in cffi_dist, because the files made the shared libs use the code on GitHub and ignore my modifications. Perhaps those files should be generally removed from the repo to avoid similar confusion in the future?

@qiu-x
These two files are for the dependency managenent for the shared lib and required for the build process with xgo.
Yeah if you are doing modifications in the tls client code itself you need to the the shared library project to actualy use the specific modified version of the tls client and not the one published on github.
You can use a replace statement inside the go.mod targeting the local modified tls_client:
I also commented out the line in the go.mod file.
// replace github.com/bogdanfinn/tls-client => ../


Error using Nushell in vscode terminal

Hardware: M1 Apple MBP
OS: Mac 12.6
When trying to use Nushell in vscode terminal I get the following vscode error.
No terminal profile options provided for id "nushell_default"

I'm guessing this is because homebrew on the apple silicon is in /opt
https://apple.stackexchange.com/questions/410825/apple-silicon-port-all-homebrew-packages-under-usr-local-opt-to-opt-homebrew
$ which nu
/opt/homebrew/bin/nu

Confirmed working after:
$ sudo ln -s /opt/homebrew/bin/nu /usr/local/bin/nu

So seems like that path needs to get added to https://github.com/nushell/vscode-nushell-lang/pull/39/files#diff-04bba6a35cad1c794cbbe677678a51de13441b7a6ee8592b7b50be1f05c6f626R40

agreed. we will accept a pr for that addition. good find. i use brew but don't install nushell that way. we should probably have both of those paths in that code.


Fix routing system

The current system is broken, unreliable and inefficient, and should be replaced / fixed.

Okay, so I've just found a way to automatically determine the current sub-directory, so the sub-directory setting is, luckily, redundant now. For this reason, I'm not sure whether or replacing the routing library is still necessary.


Restore Web5 Project page and refactor Web5 Docs page

The Web5 project page was refactored so that it could be reused as the Web5 docs page
These pages have different purposes and CTAs so should not be mirrored.

Status on this, and linked commits if any?

Moving to Phase 3, can't find context on work in progress or specifically what should be done.


Allow custom constructors

I have yaml files for use with pyyaml where I have a custom constructor !include that allows me to include other yaml files.
The validation however fails because of that. Is there a way to allow such custom elements?

@Bouni Apologies for the delayed response. Let me take a look. It'll be helpful if you can provide the contents of a sample yaml file that fails validation

main.yml
---
title: Title of this file
language: german
date: 16.12.2022
draft: true
elements:
  - !include header
  - !include body
  - !include footer

header.yml
---
element1: This is the first element of the header
element2: This is the second element of the header

main.yml includes the header.yml in this example

@Bouni I think I have addressed this. Validation shouldn't fail anymore when tags like !include are present. The fix is present in the devatherock/drone-yaml-validator:latest image. If you can test it when you get a chance and confirm that it works as you expect, I'll release it.

Changes released as devatherock/drone-yaml-validator:3.0.0


Add clown emergency oxygen tank

About the PR

Updates the clown's emergency oxygen tank for one with 95% oxygen and 5% nitrous oxide.
No nitrogen version since slime people are immune to nitrous oxide effects.

(I forgot that animal tank visuals were a thing, so I have used the standard emergency oxygen tank for those. I can take a crack at those later, or someone else can if they are inclined.)
Why / Balance

This will guarantee that at least one person will laugh at the clown's antics during evac.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

add: Added a funny oxygen tank for the clown

This will guarantee that at least one person will laugh at the clown's antics* during evac.

*War crimes

Output pressure is 21.3 kpa on pure oxygen tanks, it's the same here despite 5% n2o.
Does going below 21.3 kpa oxygen cause suffocation?

Output pressure is 21.3 kpa on pure oxygen tanks, it's the same here despite 5% n2o.
Does going below 21.3 kpa oxygen cause suffocation?

Good catch. I've just tested again, and it looks like there's zero asphyxiation damage after going through a few of these, so it looks like it is enough. I can up the numbers a little bit if we want to be safe.

at 20C 18kpa is fully breathable on pure oxygen

at 20C 18kpa is fully breathable on pure oxygen

Interesting, time to tune down the dials on our tanks and get another minute of free air :trollface:

yes.


USB STM32 fixes

Fix TX FIFO overwrite causing failure with (at least) USB ECM
Fix potential null pointer dereference on ret_bytes parameter

@loicpoulain tested on 96carbon with ECM Ethernet, works fine with this patch, before I have almost pings missed. @jfischer-phytec-iot maybe this might be the reason for your PR #542.


Add support for Lithuania

Maybe this repo could start supporting calculations for different countries?
I need to calculate taxes for Lithuania. I think I could contribute some code so that this repo would be usable for revolut users in Lithuania.
Now I would need to add EUR currency support.
And the final report, needs only to include total profit/loss.

The calculator is developed strictly according to Bulgaria tax laws. It is impossible for me to support Lithuania(or other countries), as it would require consultancy and communication with the local tax agency.

Would it be possible to extract the parser part of the code?
On Wed, Apr 7, 2021 at 12:35 PM Doino Gretchenliev @.***>
wrote:

The calculator is developed strictly according to Bulgaria tax laws. It is
impossible for me to support Lithuania(or other countries), as it would
require consultancy and communication with the local tax agency.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/doino-gretchenliev/revolut-stocks/issues/24#issuecomment-814767671,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHPQD27FBJ7PWOLWOXRHIDTHQRNFANCNFSM42OVV6ZA
.

--
Aidis Stukas
+370 641 39571

Parsers are already implemented as plugins: https://github.com/doino-gretchenliev/revolut-stocks/tree/main/libs/parsers


Data Modification tool should include query by view

In the Data Modification tool (tools/select.html), there should be a query method that is based on a CouchDb view. This method should allow to specify start/end keys, or specific keys.

This issue has been resolved in the data modifications tool. To perform a query by view with the data modification tool, perform the following steps;

Click the "Add" queries button
Select the query type "Select documents reported in a view"
Select the view by it's name


kpt fn run should warn with declarative exec functions and --enable-exec  not set

Is your feature request related to a problem? Please describe.
I set up a YAML like
apiVersion: v1
kind: ConfigMap
metadata:
  name: test
  annotations:
    config.kubernetes.io/function: |
      exec:
        path: some-file
        network: true
    config.kubernetes.io/local-config: "true"

and ran kpt fn run --log-steps -v9. Nothing happens and there is no output
Describe the solution you'd like
Some logs to indicate why the function is not run
Describe alternatives you've considered
Additional context

As part of the new kpt 1.0 design, declarative functions must be dockerized (kpt render). Imperative invocation of a single function (kpt eval`) can use dockerized and non-dockerized executables.

@droot had a call with a customer today and they asked for exec in the pipeline.  The docker performance tax is too much for them and they are opting for using a shell script to mimic what pipeline does for them because of that.  Santosh can provide more details or ping me on Chat.


D5. Design

Added D5. Design.md file in addition to images used to create D5. Design file.

Akiel Aries (20%): Wrote section 2 of the D5 Design document.
Braedon Behnke (20%): Wrote 50% of section 5 of the D5 Design document.
Brandon Mack (20%): Wrote 50% of section 5 and Section 6 of the D5 Design document.
Brock Heinz (20%): Wrote Section 3 of the D5 Design document.
Kyler Conant (20%): Wrote Section 4 of the D5 Design document.


Doesn't work like the v7 Doc Type Grid Editor - doesn't work at all for me.

In the v7 version you could select a Doc Type that has a Property with a Data Type that is a Nested Content of some Doc Type e.g.
Doc Type: Accordion Section has a property Accordion of Data Type Accordion Panels.
Accordion Panels if a Nested Content of Document Type Accordion Panel.
Everything worked fine - the Accordion Section partial ran and displayed the Accordion Panels.
Now in v8 that is not possible.
The default is to allow you to select Doc Type "Accordion Panel" only and it expects a partial to exist to render it. This is because that doc type is marked as an "Element Type".
If I mark "Accordion Section" as an Element Type then I can no longer add this as a node in the content tree. Also if I mark this as an Element Type it still does not work. It produces the error
System.InvalidOperationException: Model Umbraco.Web.PublishedModels.EcAccordionSection expects argument of type Umbraco.Core.Models.PublishedContent.IPublishedContent, but got Our.Umbraco.DocTypeGridEditor.Models.DetachedPublishedElement.

Hi John, DTGE for v8 only allows you to use element types as grid editors, because they ARE elements 🙂
I think there has been mentioned some workarounds about using your element types as content nodes in our. Iirc, there was some fuzz about this when v8 got released.
Regarding the error message, did you rebuild models after changing to an element type?

Hi Søren,
Thanks for the reply.
That is disappointing news and a major breaking change from v7 of DTGE which supported any doc type.
Was there any reason to make this Element Type restriction?
The reason I ask is it makes this package not a viable proposition for me.
Let me explain: I used v7 of DTGE to include complex controls into grid cells like Tabs, Accordions, Carousels etc. Now the nature of these controls is that they have a doc type with some general properties to govern the overall look e.g tab widths and heights etc, and then they have a single property which is a Nested Content of a suitable Element Type. Now the template for this doc type needs to have visibility of all the Nested Content in order to correctly display the control. Now your restriction to only supporting the Nested Content makes this package wholly  unsuitable for my needs.
Now I was able to get my accordion to work with your package by making lots of hacks

All my Composition types in my Doc Type had to be switched to Element Types (so they no longer are IPublishedContent)
My Doc Type had to be switched to Element Type
I had to manually rebuild the models even though the model mode was LiveDll i.e. models should be rebuilt automatically.
All the content pages which use my basic accordion are broken because that type is no longer a IPublishedContent

It is just wrong from an architectural viewpoint to make my compositions and doc types element types just to make them work with your package. I think for the DTGE to be useful it needs to support all Doc Types otherwise I think the package should be renamed Element Type Grid Editor to reflect what it really is, and this would allow  someone else the opportunity to create a more general DTGE.  Thanks.

In case it is of use to anyone - I switched to using a macro in the grid cells to display my complex controls in a grid cell. It is a 1 line macro that has 1 parameter to pick the content item to be displayed in the grid cell. Works perfectly for my Accordion, Tabs, Carousels etc.  I just define these controls as child nodes of my grid section and pick the relevant node using the macro.
Macro Code:
`@inherits Umbraco.Web.Macros.PartialViewMacroPage
@{
var contentId = Model.MacroParameters["contentId"];
var content = Umbraco.Content(contentId);
}
@Html.Partial(content.GetTemplateAlias(), content)
`

Glad you found a way to make your setup work for you. Grid items IS elements, and that is not going to change.

Thanks @skttl for your reminder to rebuild models. I ran into this error message because after changing to an element type I forgot to rebuild models. Thought I would leave a comment here for anyone who wanders by this in the future with the same error message.


🐞 - New Textfield with <select tuiTextfield /> has incorrect behavior on mobile devices

Playground Link
https://taiga-ui.dev/next/components/textfield#dropdown
Description

Open https://taiga-ui.dev/next/components/textfield#dropdown
Click on the 2nd textfield

Desktop (MacOS):

Mobile device (iPhone 13 mini, ios 17.2.1):

Angular version
16
Taiga UI version
main branch
Which browsers have you used?

[ ] Chrome
[ ] Firefox
[X] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[ ] Windows
[ ] Linux
[X] iOS
[ ] Android

There's (pointerdown.prevent) that prevents opening on desktop and Android, looks like it's not enough for iOS. Maybe try something like capture.stop on various pointer/click events to see what helps.


errors in Switch managed disks between Standard HDD and Standard SSD block

$disk.Sku = [Microsoft.Azure.Management.Compute.Models.DiskSku]::new($storageType)
The property 'Sku' cannot be found on this object. Verify that the property exists and can be set.
At line:1 char:1

$disk.Sku = [Microsoft.Azure.Management.Compute.Models.DiskSku]::new( ...

  + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
  + FullyQualifiedErrorId : PropertyAssignmentException

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

ID: 7b67bcdd-0278-7c7f-89ac-5e4bc53de72c
Version Independent ID: 57815f78-825d-ec47-2751-128ab5a03d66
Content: Convert managed disks storage between standard and premium SSD - Azure Windows Virtual Machines
Content Source: articles/virtual-machines/windows/convert-disk-storage.md
Service: virtual-machines-windows
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

Thanks for the feedback! We are currently investigating and will update you shortly.

Please make sure that you are using Managed disk. If your disk is unmanaged, first convert it to a managed disk so you can switch between storage options.
To use Premium managed disks, your VM must use a VM size that supports Premium storage.

Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Cannot load all the models in SDXL Turbo to SD1.5 Refiner

I loaded some models myself but it seems incorrect. Can you share all the models used in this json file?

Actually I got this error, so I cannot run the queue. I have add the same model for vae in the same folders


Support embedded maps

If you have an embedded map in a struct, using db.Select() or db.Get() will silently fail to populate the map because the map will set to nil by default when sqlx generates the structs.
For example if you have your data model set up like:
import "database/sql/driver"

type Message struct {
	Text string
	Properties PropertyMap // Stored as JSON in the database
}

type PropertyMap map[string]string

// Implement driver.Valuer and sql.Scanner interfaces on PropertyMap
func (p PropertyMap) Value() (driver.Value, error) {
	if len(p) == 0 {
		return nil, nil
	}
	return json.Marshal(p)
}

func (p PropertyMap) Scan(src interface{}) error {
	v := reflect.ValueOf(src)
	if !v.IsValid() || v.IsNil() {
		return nil
	}
	if data, ok := src.([]byte); ok {
		return json.Unmarshal(data, &p)
	}
	return fmt.Errorf("Could not not decode type %T -> %T", src, p)
}

Storing Messages will work correctly, but retrieving them will not work:
m := Message{Text: "hi", Properties: PropertyMap{"color": "blue"}}
db.NamedExec("INSERT INTO messages(text, properties) VALUES (:text, :properties)", m)
// Examining data through psql shows that the message was stored correctly, including the Properties field.
res := []Message{}
db.Select(&res, "SELECT * FROM messages")
fmt.Println(res[0].Properties) // Prints <nil>

Currently reflectx.FieldsByIndexes will check if inner struct pointers are nil and generate them as necessary, but not maps.

Thanks for the great PR!  I added a test which should pass after merging.

No problem! Thanks for the super useful library :)


Add initial balance to OpenChain.

Motivation
The faucet currently creates two blocks for each user: One to create their chain and then one to transfer their initial balance.
And in general, a chain without any balance can't be used for anything, so the command-line and GraphQL commands for opening a chain will usually be followed by a transfer as well.
Proposal
Add a balance field to the OpenChain operation and message itself, so the parent chain can send an initial amount of tokens along that is credited to the child from the start.
Test Plan
The faucet test now exercises this.
Release Plan

Need to bump the major/minor version number in the next release of the crates.
Need to update the developer manual.

Links

reviewer checklist

Sure. Or we could use multiple transactions in the same block

I actually tried that first, and created https://github.com/linera-io/linera-protocol/issues/1200 because of it: We'd have to omit incoming messages in open_chain, or make them general transactions and put them after the OpenChain operation, because otherwise it would be impossible to know the new chain ID without first executing the incoming messages.
But then I thought that we'll almost always transfer some initial balance to every new chain anyway, so why not add it to the operation itself?

But then I thought that we'll almost always transfer some initial balance to every new chain anyway, so why not add it to the operation itself?

I've been wondering if we need the concept of "chain balance" or just balances for specific addresses. This is probably not blocking for this PR.

I've been wondering if we need the concept of "chain balance" or just balances for specific addresses.

Maybe, yes. Then each block (and/or transaction?) will have to specify who pays for it.


engine: add custom_build and kubectl exec sync

What's in this PR?
I split this PR in to two parts main commits, excluding a vendor commit:

custom_build

custom_build is a Tiltfile function that adds a new model (CustomBuild) that is used by a new builder (CustomBuilder). This builder knows how to invoke the command specified in custom_build and look for a resulting image in the image repository.

"synclet" deploys via kubectl exec.

We can't talk to the Docker socket in other container runtimes, like CRI-O. In order to do sync then we need to sync files the old fashioned way: via kubectl exec. This is slower, but a good enough solution for now. The SyncletBuildAndDeployer currently looks at the container run time and uses the existing synclet setup for that. Otherwise it uses this new kubectl exec syncing strategy.
What's left to do
I'm pretty happy with the test coverage around custom_build. I'd like to add an integration test for the kubectl exec stuff, or maybe more extensive unit test coverage.

could we split this up into separate PRs?
I'm a little bit concerned that this is going to take so long to review that it will create lots of merge conflicts and frustrate everyone on the team.
A good division of PRs might be:
PR #1) data model additions
PR #2) k8s vendoring
PR #3) engine implementation
PR #4) Tiltfile changes
this should easily be separable, because we've done a good job separating the responsibility of these packages.

(also, I suspect Maia will be a better 2nd reviewer than me, since she has the most context on the different Build strategy divisions)

Yeah if we feel that this is too much I'm happy to split out. # 3 in that plan is going to be by far the largest PR.
I'll get started on splitting it out now.

Closing in favor of split out PRs.


Add Ren'Py 7.3.2

Even if it's a tool to create games, I would suggest adding it to the games bucket.
https://github.com/Calinou/scoop-games

Even if it's a tool to create games, I would suggest adding it to the games bucket.
https://github.com/Calinou/scoop-games

I got nothing against that but some game engines such as Godot are already in the extras bucket, so I'd ask @Ash258 for some input on this.

I do not mind it here. Since cheat engine is here for example too.


docs(mutations): fix typo in example url

A tiny docs improvement 🐭

:tada: This PR is included in version 3.3.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Rubygem and Node Package both return nil/null

I'm having this issue with both the Ruby and Node versions of oakdex.  No matter what I call, I always just get null back.

var oakdex = require('oakdex-pokedex');
oakdex.findPokemon(number, function(p) {
            console.log(p.names.en);
});
// cannot read property 'names' of undefined

@Shwheelz Please try again for the ruby gem (release 0.1.3). It should work now. Thanks for reporting the bug!
I will further investigate in the node package.

The rubygem is working great now, thanks!  I'm still having trouble with the node package though.  I'm trying to call within an Alexa skill, so it's admittedly hard to debug.  But following your example, I have
let prepareQuestions = function(pokemonList) {
    let questionList = [];
    for (let pokemon of pokemonList) {
        Oakdex.findPokemon(pokemon, function(p) {
            let types = p.types;      // This is the error line below (index.js:43:26)
            questionList.push({question: pokemon, answer: types})
        });
    }

    return questionList;
}

Here's the stack trace; perhaps it could be useful.  I'll continue to poke around as I get time as well, and maybe we can solve this.  I this your node package is really useful, and I'm hoping to get it to work so I can make Alexa skills with it in the future.
module initialization error: TypeError
    at /var/task/index.js:43:26
    at /var/task/node_modules/oakdex-pokedex/src/oakdex_pokedex.js:106:13
    at /var/task/node_modules/oakdex-pokedex/src/oakdex_pokedex.js:47:5
    at allByName (/var/task/node_modules/oakdex-pokedex/src/oakdex_pokedex.js:9:5)
    at pokemonById (/var/task/node_modules/oakdex-pokedex/src/oakdex_pokedex.js:43:3)
    at /var/task/node_modules/oakdex-pokedex/src/oakdex_pokedex.js:103:9
    at allByName (/var/task/node_modules/oakdex-pokedex/src/oakdex_pokedex.js:9:5)
    at Object.findPokemon (/var/task/node_modules/oakdex-pokedex/src/oakdex_pokedex.js:100:5)
    at prepareQuestions (/var/task/index.js:41:16)
    at Object.<anonymous> (/var/task/index.js:51:22)

It appears all your node packages are passing, so I'm going to close the issue until I have ample time to debug my own app.  Thanks again for fixing the Rubygem though!  Great work!


[DRAFT] Implement abstract validation components

User Story:
As a developer, I need to perform various types of validation on data in numerous contexts.
Description/Use Case
Create a set of prototype objects (factory; abstract class, and optionally an interface) to represent the validation of data flowing through the universal pipeline. Also include an implementation of the validator that performs a no-op.
Risks/Impacts/Considerations
Consider adding some validation specific exceptions as appropriate.
Dev Notes:
See the design document in the repo for a code example of how to do this.
Acceptance Criteria

Resulting objects can be used to run a no-op validation
Results objects can be extended to run implement specific validations
At least one validation-specific exception created

@thetaurean Please move to ready for grooming or let me know if we should icebox this story.


Prepare the initial documentation template files

Within these changes we assemble the initial RST documentation files
for the Delivery Toolchain's documentation which will be hosted on
GitHub pages. We also provide a Makefile that includes entries that
will be used to build the documentation with Sphinx tool.

I'll merge that part so others can contribute.


Getting knitr to work again

Coverage remained the same at 79.523% when pulling 754800d74c63546964d2e156d76444b6ce2d345f on ldecicco-USGS:master into bc8f472e74f4a7173d1a4ca2c7d45a0e0c09e287 on USGS-R:master.


Possibility to watch config files.

When changing config files on build.dev, i have to manually restart the task. Can it be automated?

Wouldn't be too much work to stick it in your project tasks. I  personally don't know how I feel about opening up the watch to all the tooling but my first impression would be, given the extensibility built into the tooling that would tend to be flakey.
//cc @ludohenin @mgechev

I think it would be better to use something like nodemon for that ?

After giving this a bit more thought, it's really not viable imo.

Given that a change in the tools could very well change how / what / where you are outputting you would have to trigger a rebuild
That rebuild depending on what changed may or may not function the same way as the existing which would leave you in a messy state.

There certainly isn't a reason why you can't add a watch to your project tasks but I personally don't see this one being viable for all the options we support.


Updated README.md

Added Contributor and edited 'pandas' last line.

Thanks for this @ComputerGeekNerd. Do you mind implementing the two unrelated changes (adding your name and removing pandas) in separate pull requests please?


pgmodeler: 1.0.0-beta1 -> 1.0.0

Description of changes
pgmodeler 1.0.0 (stable) has been released today.

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

It seems the v1.0.0 tag was re-created so the hash doesn't match.
Are you working on a patch for this or would it be fine if I did @esclear?

Looking into this.

Building the fix to test it.
I'm currently trying to figure out what the difference between the old and new commits tagged v1.0.0 is 🤔

I was trying to find which commit the old v1.0.0 was pointing to but it got overwritten so I can't check.
Might just try to check what commits have been made since 3 days ago to 2 days ago

It seems like they did it to add this commit: pgmodeler/pgmodeler@28c9469 Instead of releasing a new v1.0.1 version.

I compared the nix-prefetch-git hashes of 28c946920319d2b3293581136b59b1e133b440d8 and 0f250e08b3aaded84871a61bbe2f3ba7f7e203ce and concur that this is indeed the commit that changed the codebase in the way that is reflected by the hashes.
While the changes were made on the 1.0.1 branch, the v1.0.0 tag was retagged.
Oof.


feat(ngMock): invoke nested calls to module immediately

before this change calling a nested module was just ignored, but it makes sense that ppl might use module() inside some helper function in order to get providers from DI and those helper methods should work no matter if they are called before or during the injector creation.

This actually worked in some weird way in angular 1.2 (nested modules were invoked last) since angular.forEach allowed adding items to array during iteration. I noticed it when migrating some app from 1.2 to 1.4, and it was actually really hard to create a workaround without making the code ugly: http://plnkr.co/edit/4XGPuQQGfXBGmMivgbio?p=preview

@lgalfaso or @petebacondarwin can you plz take a look?

Ping

LGTM - merging


ci: switch to GitHub Actions

Will push this to the other active branches, too (v9.0, v8.0, v7.0.0) - and then try to disable circle CI.

Mh. GitHub Actions doesn't run, yet. Maybe you have to enable it in the repo settings, @steve-chavez?

@wolfgangwalther Hm, I see Actions enabled:

Maybe it has to be merged into the main branch first?

Hm. I tried it on my fork and it worked there, so I guess it's fine to merge and try.

Ok, that worked. However, I can't disable circleCI - you'll have to do that @steve-chavez:

You must have admin access to stop building this project.

Just confirmed it's building in PRs now, too (#496).

Ok, that worked. However, I can't disable circleCI - you'll have to do that @steve-chavez:

Could you disable circle CI on this repo? It's still trying to run and failing all checks / PRs.

Done! I've hit the "Stop Building" button.