Reconsider Parquet read buffer size

ParquetPartitionReaderBase uses the parquet.read.allocation.size config to control the copy buffer used for reading from the Parquet input stream.  The default is 8MB which is pretty big, especially when there are many reader threads via the multithreaded reader.  With a large number of reader threads all performing Parquet reads, these per-thread buffers can add up to a nontrivial amount of heap memory which can trigger OOMs.  We should do some empirical measurements in various environments to see if we can significantly lower the default for this.

Duplicate of issue #9269


Fix stddev test

Fix stddev test by comparing output to expected spark output.
@OlivierBlanvillain review please.

Current coverage is 81.04% (diff: 100%)

Merging #45 into master will decrease coverage by 0.27%

@@             master        #45   diff @@
==========================================
  Files            20         20
  Lines           364        364
  Methods         360        360
  Messages          0          0
  Branches          4          4
==========================================
- Hits            296        295     -1
- Misses           68         69     +1
  Partials          0          0

Powered by Codecov. Last update 1d1c0be...e1570ad

:+1: Many thanks!


Website Domain Expired

Just FYI, your http://dynjs.org/ domain appears to be expired as of May 5, 2015 at 17:20 UTC.

fixed, thanks!


[$125] mWeb - 2FA - In 2FA magic code page, after refresh briefly error message is displayed

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

Version Number: V9. 0.75-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Issue reported by: Applause Internal Team
Device used: Redmi note 10s android 13
App Component: User Settings
Action Performed:
Pre-condition: Login with unverified gmail account

Go to https://staging.new.expensify.com/home
Go to settings- security - two factor authentication
Enter incorrect magic code
Refresh the page

Expected Result:
In 2FA magic code page, after refresh briefly error message must not be displayed.
Actual Result:
In 2FA magic code page, after refresh briefly error message is displayed.
Workaround:
Unknown
Platforms:

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

Screenshots/Videos
https://github.com/user-attachments/assets/2df08823-e574-42a1-809b-adaaefc48f22
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021867646284163514204
Upwork Job ID:<PHONE_NUMBER>163514204
Last Price Increase: 2024-12-20

Issue OwnerCurrent Issue Owner: @dominictb

I'm currently OoO - but will be back on Tuesday - Reassigning to get the ball rolling, but happy to take back on Tuesday

@dominictb please attempt reproduction and review the above proposals - thanks!

@dominictb lmk if this needs to wait until the new year! 🎄

@dominictb Could you review my proposal? thanks

@nyomanjyotisa's proposal looks promising. Onyx update is the async action and calling func in did-mount happens after rendering the component.
So using canShowError and clear the error on mount are the good ideas to solve the issue and be consistent with this PR
But I just wonder:

Should we call clearValidateCodeActionError along with clearError like what we did here?
If we use canShowError, I don't think we need to clear error in clean-up function. Please correct me if I miss something.

@dominictb Why are we even considering a problem that is hypothetical raised linked to other PR. I have uploaded a video on my proposal as POC that the problem @nyomanjyotisa is claiming doesn't even exist. The approach I am suggesting is used in other places in our code base such as here here @nyomanjyotisa proposal is my proposal plus a solution for a problem that doesn't even exist from my testing. Can you provide an evidence of the brief display of the error occuring in this issue's case?

If you can prove the issue doesn't happen anymore (by plain text not just record the video), I'll consider the decision again. Thanks 🙏

I am not saying my video should be taken as evidence but if you guys are sure the problem can also happen here give me a proof otherwise what is the point of applying a workaround solution for an edge case problem that's not even there.
The explanation that I can give you here is

BTW useOnyx is late in loading data I remember an issue arising on mWeb of not auto-populating tag on iou confirmation page when withFullTransactionOrNotFound HOC was migrated to use useOnyx from withOnyx and transaction was being undefined on useEffect run on render that used to work well with withOnyx and regarding the pr https://github.com/Expensify/App/pull/52303#issuecomment-2470033635 linked by @nyomanjyotisa you can see that the useOnys migration commit was made later. It might be because we are getting the error data from useOnyx that I am not reproducing the issue he is claiming and the problem wouldn't occur here because we would be clearing the error even before it is read from onyx in mWeb.

It doesn't really convince me. Can you show me the code?

@dominictb Just proceed with your review and let the assigned engineer decide whether we should apply a fix for an invisible bug or not 👍


Schema Parsing Bug with anyOf type array

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/283
Originally created by @pnadolny13 on 2021-11-30 19:36:21

Summary
An error is thrown when the certain nested schema definitions are encountered.
The error message is shown in what @visch already logged as an issue in MeltanoLabs/target-athena using tap-shopify but I ran into the same issue with tap-gitlab and dug deeper, which led me to the SDK.
Steps to reproduce
I think theres a bug in get_datelike_property_type when a schema is encountered with a nested anyOf key.
An example is this tap-gitlab project stream.
To replicate just run tap-gitlab with project stream selected into an SDK based target.
What is the current bug behavior?
An error is thrown by the target when the a stream certain nested anyOf schema definitions are included.
What is the expected correct behavior?
All schema types are parsed with no errors.
Relevant logs and/or screenshots
Possible fixes

View 1 previous comment from the original issue on GitLab


Implement global debug panel

Candidates

http://kehomsforge.com/tutorials/multi/GodotAddonPack/part06
https://github.com/GuyUnger/HyperLog

Using Kehom's. While HyperLog is great, it does not have timed labels. Also, I couldn't figure out how to properly log variables which are no properties of a class.


Add tests for uncovered examples

Some of the examples are not covered by tests yet, these should be added.

I know the fastapi example does not have any tests. To test it httpx needs to be added to the requirements.txt. Then a test client fixture is needed. Something like:
@pytest.fixture
async def test_client():
    async with AsyncClient(
        transport=ASGITransport(app=app), base_url=f"http://<IP_ADDRESS>:8000"
    ) as client:
        yield client

Then tests from here should be a good example of how to test the routes.
It's possible there are also other tests missing. I named the tests after the files, so for example test_add_documents_in_batches in test_async_examples.py is the test for async_add_documents_in_batches.py, so if any of those are missing they need to be added also.


Squoosh website vs CLI compression size

Describe the bug
When I use the Squoosh app to compress an image (OxiPNG, 40 width, 30 colors, everything else default) I get an output that is about 600-700 bytes in size. If I use the CLI, doing the same thing (or what I think should do the same thing, since I use the "Copy npx command" button), I get 2kb.
npx @squoosh/cli output/*.png --resize '{"width": 40, "method": "lanczos3" }' --quant '{"numColors":30, "dither": 1}' --oxipng '{"level": 2}' -s "-squoosh" -d output
Is there anything I'm missing from the script, or is the CLI just not yet able to compress to the same level as the website?
Version:

OS w/ version: macOS Big Sur 11.4
Browser w/ version: Chrome v91.0.4472.114
Node version: v14.16
npm version: v6.14.11

Let me know if there is any additional information needed.
Thank you very much for your time, and for creating this wonderful tool.

I can confirm I ran into the same issue.
cli-command:
npx @squoosh/cli --quant '{"enabled":true,"zx":0,"maxNumColors":64,"dither":0}' --oxipng '{"level":3,"interlace":false}' *.png -d png8_64c
Squoosh-cli: version ? (latest 30 May 2022, -V parameter not working)
OS: OSX 12.4
NodeJS: 16.14.0
NPM: 8.5.5
Output via CLI is 1.5 - 3 x the size of the output of the app.
I'm using the 'copy npx command' in the header of the settings to get the cli command.
Alos, running the cli command shows the following errors:
(node:62688) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 unpipe listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(Use node --trace-warnings ... to show where the warning was created)
(node:62688) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 error listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(node:62688) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 close listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(node:62688) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 13 finish listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit

Unfortunately, due to a few people leaving the team, and staffing issues resulting from the current economic climate (ugh), the CLI and libsquoosh packages are no longer actively maintained. I know that sucks, but there simply isn't the time & people to work on this. If anyone from the community wants to fork it, you have my blessing. The squoosh.app web app will continue to be supported and improved.

@Paxatax @AforDesign
Seeing as we actually needs this functionality, we've forked the project. A CLI-capable version up at https://squoosh.frostoven.com/
Do you have an example of an image that has the size discrepancy? We'd not been able to reproduce it ourselves, and will be happy to have a look and see if we can find the underlying issue

Thanks alot for picking up this great feature!
I've mailed you a set of examples.

I've mailed you a set of examples.

@AforDesign No emails have come through yet. It's possible you sent it to a noreply address. Can you please mail those examples to hexagon [at] frostoven.com ?

Could you check if it arrived this time?

@AforDesign It came through :). Will investigate next week

@AforDesign I've improved some of the size issues; there were multiple bugs:

The color reduction count specified via terminal was completely ignored (for all image types).
The interlace option specified via terminal was ignored for OxiPNG.

The image size discrepancy is not completely fixed, and I have found some personal images that are still larger in CLI when compressed via OxiPNG. But, at least for the images you've supplied me, all image sizes match the web UI, or are smaller.
Additionally, I've removed the annoying warnings spammed while running the application.
Seeing as @squoosh/cli has been retired, you'll need to uninstall that and use @frostoven/squoosh-cli. There a manual page for it here.

@aggregate1166877 Thanks for opening up access to @frostoven's fork.  Maybe some of the previous & new contributors can head over there & chip in?

@aggregate1166877 That's awesome! And you fixed this super fast. Thanks alot for the great work.
Somnewhere next week I will run your update on a large batch.
I will let you know if any size discrepancy occurs.
I'm especially curious how images with a lower color count then set in the parameter will be processed. That has been a big issue with many optimizers, resulting in images larger than the original.


[Internal QA]: Fix: Logged-In Agents Can Appear to Delete Workspaces in NewDot Without Actual Deletion or Error Message

Explanation of Change

Fixed Issues

$ https://github.com/Expensify/App/issues/52854
PROPOSAL: https://github.com/Expensify/App/issues/52854#issuecomment-2501816322
Tests

Precondition: User is supportal logged in OR set this line/ condition to true

As supportal logged in, and goes to users workspace list page
Click on the three dots of any workspace
Click Delete worksapce

Verify that error modal is shown

[x] Verify that no errors appear in the JS console

Offline tests

Precondition: User is supportal logged in

As supportal logged in, and goes to users workspace list page
Click on the three dots of any workspace
Click Delete worksapce

Verify that error modal is shown
QA Steps

N/A.  Internal QA

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/895735c8-51cd-4f09-b27d-f5190486b7e2

Android: mWeb Chrome
https://github.com/user-attachments/assets/5fa1eb9d-0994-4019-bd51-29b2247b680f

iOS: Native
https://github.com/user-attachments/assets/b8895cb8-c543-4a02-aadf-69b5a67ef8c4

iOS: mWeb Safari
https://github.com/user-attachments/assets/e98a1a49-9089-4db4-91b9-4e871d6d6ff7

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/9e42f5cf-af6d-4caa-b6e8-db1f4f85030f

MacOS: Desktop
https://github.com/user-attachments/assets/c7fc7728-1b2a-4268-8654-42f25fdd85bf

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

This is very unlikely the real performance blocker as we're just adding a Modal in 1 scenario

Looking good!!


Failed to create record.

{   "errorDetails": "Failed to save the record: database is locked (5) (SQLITE_BUSY)",   "errorMessage": "Failed to create record." }

I'm getting this problem when I'm sending less than 100 requests concurrently via go routines, I'm sending there file and 2 text fields.

And logs are looking very bad at this moment:

As hardware I'm using raspberry pi 4(ubuntu 22.04 arm64) and external samsung T7 ssd (exfat) via USB
Last version of pocketbase builded from master, version from release still has same issue.
I guess problem is because of files uploading, like we are locking sqlite on uploading start and unlock on end, but there are a lot of parallel uploadings. Currently my collection size is more than 80k items

Maybe it's possible to support another DB providers for a better high loading? Like postgres for example, or don't block DB while creating and add something like a queue for TXs?

@Fuchsoria Support for other databases is in the roadmap, but has the lowest priority for now and may or may not be implemented for v1.
Yesterday I've pushed in master a quick fix that move out the files handling from the transaction so the file upload no longer should affect the locking times.
We don't have control over the sqlite db locks. SQLite supports only a single writer at a time (writes queue up) but when mixing read&write in a transaction it could lead to a deadlock situation and SQLite ignores the busy_tiemeout pragma and directly throws the "database is locked error" since there is no point of waiting the transaction to complete.
I'm currently experimenting with a mixed fail/retry + optional blocking waitgroup/queue approach for all Dao operations. Will post an update once I manage to finalize the tests and eventually release it as v0.9.1.

In my case I'm hosting app which sends requests on same host like pocketbase instance, that means I have direct connection via localhost, and it creates requests and sends requests parallel without latency, right now I use only 1 sender instead of multiple routines, and it's my temp solution to let service alive

@Fuchsoria A blocking query semaphore and base fail/retry handling was implemented in master and it will be released as part of v0.9.1 soon. Please give it a try and see if it improve the concurrent requests processing (I've tested locally with 5k concurrent create requests and collection structure similar to yours with body size of ~ 500kb).
The blocking semaphore currently is only per query basis to avoid performance issues with the general requests handling so there are still edge cases where SQLITE_BUSY could occur. There is no easy way to solve that and it's just how SQLite works. I'm not familiar with your use case, but if your app needs high concurrent requests processing all the time and it is not just for some temporary data import, then you could consider:

batching the requests
use the CGO driver by building with CGO_ENABLED=1(it is ~2-3 times faster then the noncgo version)
reavaluate whether PocketBase is suitable for your use case since we inherit some of the SQLite limitations (you could also check https://www.sqlite.org/whentouse.html)

@ganigeorgiev Thank you for fast update, I build yesterday master branch and started with my default configuration, ~50 parallel requests with images ~1mb-4mb are looking really nice now, I see my logs clean. Small question about releases, are releases build with CGO=1 or not? I tested it with CGO=0

Small question about releases, are releases build with CGO=1 or not? I tested it with CGO=0

No, the GitHub releases are with CGO_ENABLED=0 because it is easier to cross-compile.
You can find the goreleaser config in https://github.com/pocketbase/pocketbase/blob/master/.goreleaser.yaml.

The above fixes are now part of v0.9.1 release.
If you stumble on something else, please let me know and I'll investigate it.

It's possible that in next days I will migrate more than 25k objects from another db to pocketbase through API with many parallel post/get requests, I will write feedback here

2022/12/10 01:51:55 readObjectStart: expect { or n, but found 5, error found in #1 byte of ...|502 Bad Gat|..., bigger context ...|502 Bad Gateway
Unable to reach the origin service.|...

I had something like 25k items, started everything together with routines, and send there first request to get data, second request to post new data with relations from loaded data. And service died

I don't think this is related to the latest changes.
PocketBase usually doesn't return 502 and I guess the service was killed due to the high memory consumption or drained file descriptors (you can find your fd with ulimit -a). You can also check https://github.com/pocketbase/pocketbase/discussions/1224.
Memory allocations will be improved in the near future (there is a task in the roadmap for that). I've already identified at 2 places inefficient assignments in hot paths that takes ~20% of the total memory and fixes for that will be submitted soon.


Windows: Temporarily disable TestBuildLastModified

Signed-off-by: John Howard<EMAIL_ADDRESS>@thaJeztah @AkihiroSuda Temporary fixes #30890 - Looks like something has changed in the master busybox image so that -e is no longer working on ls.

How about pinning the busybox image to an older version instead?
If we need to use the latest busybox, this PR SGTM.

I don't believe the hosting site holds prior versions...
The white spaces are a result of gofmt - not sure how they were missed before....

The white spaces are a result of gofmt - not sure how they were missed before.... (as in I think it's right)

Ah, alright. I think gofmt check is not performed on test files, so that would explain 👍

OK, LGTM

Moving to merge status for when CI completes successfully


can't install go-pg

What version of dep are you using (dep version)?
dep:
version     : devel
build date  :
git hash    :
go version  : go1.8.3
go compiler : gc
platform    : linux/amd64

What dep command did you run?
dep ensure

Output
ensure Solve(): No versions of github.com/go-pg/pg met constraints:
v8.0.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v8.0.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v8.0.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v8.0.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v8.0.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v8.0.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v8.0.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v7.1.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v7.1.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v7.1.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v7.1.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v7.1.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v7.1.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v7.1.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v7.1.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v7.0.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.15.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.15.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.14.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.14.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.14.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.14.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.14.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.14.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.13.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.13.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.13.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.13.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.13.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.13.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.13: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.12.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.11.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.11.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.11.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.10.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.9.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.9.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.9.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.9.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.9.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.9.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.9.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.8.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.8.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.7.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.7.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.7.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.26: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.25: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.24: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.23: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.22: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.21: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.20: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.19: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.18: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.17: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.16: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.15: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.14: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.13: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.12: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.11: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.6.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.5.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.5.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.24: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.23: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.22: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.21: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.20: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.19: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.18: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.17: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.16: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.15: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.14: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.13: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.12: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.11: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.4.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.3.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.3.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.3.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.3.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.3.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.3.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.2.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.2.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.2.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.1.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.1.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.1.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.1.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.1.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.1.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.1.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.1.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.1.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.0.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.0.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.0.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.0.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.0.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v6.0.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.3.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.3.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.3.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.3.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.2.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.1.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.17: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.16: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.15: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.14: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.13: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.12: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.11: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5.0.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.9.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.9.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.9.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.9.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.9.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.9.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.12: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.11: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.8.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.11: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.7.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.6.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.6.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.6.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.6.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.6.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.6.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.5.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.5.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.5.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.5.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.5.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.5.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.5.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.4.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.3.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.3.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.2.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.1.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.1.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.1.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.1.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.1.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.1.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.1.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.1.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.1.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.13: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.12: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.11: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4.0.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.5.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.5.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.5.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.5.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.5.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.5.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.5.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.4.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.4.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.4.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.14: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.13: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.12: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.11: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.10: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.9: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.8: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.7: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.6: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.5: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.4: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.1.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3: Could not introduce github.com/go-pg/pg@v3, as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v2: Could not introduce github.com/go-pg/pg@v2, as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v1: Could not introduce github.com/go-pg/pg@v1, as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v9.0.0-beta.9: github.com/go-pg/pg imports github.com/go-pg/pg/v9/orm, which contains malformed code: no package exists at github.com/go-pg/pg/v9/orm
v9.0.0-beta.8: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: unknown error for github.com/go-pg/pg/v9/internal, if you get this error see https://github.com/golang/dep/issues/351
v9.0.0-beta.7: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal/pool, which contains malformed code: no package exists at github.com/go-pg/pg/v9/internal/pool
v9.0.0-beta.6: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: unknown error for github.com/go-pg/pg/v9/internal, if you get this error see https://github.com/golang/dep/issues/351
v9.0.0-beta.5: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: unknown error for github.com/go-pg/pg/v9/internal, if you get this error see https://github.com/golang/dep/issues/351
v9.0.0-beta.4: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal/pool, which contains malformed code: no package exists at github.com/go-pg/pg/v9/internal/pool
v9.0.0-beta.3: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal/pool, which contains malformed code: no package exists at github.com/go-pg/pg/v9/internal/pool
v9.0.0-beta.2: github.com/go-pg/pg imports github.com/go-pg/pg/v9/orm, which contains malformed code: no package exists at github.com/go-pg/pg/v9/orm
v9.0.0-beta.15: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: no package exists at github.com/go-pg/pg/v9/internal
v9.0.0-beta.14: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: unknown error for github.com/go-pg/pg/v9/internal, if you get this error see https://github.com/golang/dep/issues/351
v9.0.0-beta.13: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: unknown error for github.com/go-pg/pg/v9/internal, if you get this error see https://github.com/golang/dep/issues/351
v9.0.0-beta.12: github.com/go-pg/pg imports github.com/go-pg/pg/v9/orm, which contains malformed code: no package exists at github.com/go-pg/pg/v9/orm
v9.0.0-beta.11: github.com/go-pg/pg imports github.com/go-pg/pg/v9/types, which contains malformed code: unknown error for github.com/go-pg/pg/v9/types, if you get this error see https://github.com/golang/dep/issues/351
v9.0.0-beta.10: github.com/go-pg/pg imports github.com/go-pg/pg/v9/types, which contains malformed code: no package exists at github.com/go-pg/pg/v9/types
v9.0.0-beta.1: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: unknown error for github.com/go-pg/pg/v9/internal, if you get this error see https://github.com/golang/dep/issues/351
v9.0.0-beta: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: unknown error for github.com/go-pg/pg/v9/internal, if you get this error see https://github.com/golang/dep/issues/351
master: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: unknown error for github.com/go-pg/pg/v9/internal, if you get this error see https://github.com/golang/dep/issues/351
fix/trim-simplfiy: Could not introduce github.com/go-pg/pg@fix/trim-simplfiy, as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v3: Could not introduce github.com/go-pg/pg@v3, as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v4: Could not introduce github.com/go-pg/pg@v4, as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v5: Could not introduce github.com/go-pg/pg@v5, as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
v8: Could not introduce github.com/go-pg/pg@v8, as it is not allowed by constraint ^9.0.0-beta from project github.com/MohitKS5/edtech_hindquarters.
What did you expect to see?
go-pg gets installed.
What did you see instead?
v9.0.0-beta: github.com/go-pg/pg imports github.com/go-pg/pg/v9/internal, which contains malformed code: unknown error for github.com/go-pg/pg/v9/internal, if you get this error see https://github.com/golang/dep/issues/351

I shifted to go modules to solve this for now.

+1 This issue

Hi - We're looking for a source of funding to help fix this and other issues. https://github.com/golang/dep/issues/2165

+1 same issue

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


feat(appService): moved appLeadImage endpoint to AppChange controller

feat(appService): moved appLeadImage endpoint to AppChange controller
Ref: CPLP-2645

to resolve conflicts I did rebase on dev. You need to first pull those changes to continue.


[2.3.8] safe eeprom json hot fix, some boulder async

Reverse PR since I forgot to work on my branch

This looks reasonable. It works in testing?

Haven't had a chance to test the async stuff yet, not in office today. The "hot" part is for the EEPROM loading. The SPI spectrometers are outputting malformed JSON that were refusing to load (still trying to figure out why the output was bad, also need to go in office for that)


add a flag for indicating that not all the file was parsed.

Problem:
the current behavior of Quick is to only validate the rows recognized by the rows descriptions in the validation profile.
if a user has automated a Quick action to validate a periodically generated file, Quick may will miss some newly generated rows that do not fit any of the rows description specified by the user.
solution:
to avoid this, Quick should throw an error if a rows didn't match any of the rows description provided by the user, and a flag "-i" will be added to override this behavior and ignore these rows, so the user can explicit specify that she wants this behavior.

the -i flag is used to indicate the file description id used, so the flag -u is used instead.

closed in 57b5e91


Seadrop deployment failing when a certain line is added to the constructor.

I add the line mintSeaDrop to the constructor like so:
    constructor(
        string memory name,
        string memory symbol,
        address[] memory allowedSeaDrop
    ) ERC721ContractMetadata(name, symbol) {
        // Put the length on the stack for more efficient access.
        uint256 allowedSeaDropLength = allowedSeaDrop.length;

        // Set the mapping for allowed SeaDrop contracts.
        for (uint256 i = 0; i < allowedSeaDropLength; ) {
            _allowedSeaDrop[allowedSeaDrop[i]] = true;
            unchecked {
                ++i;
            }
        }
	mintSeaDrop(0x373F3D184E7a9145B9a8c4528Fb48E79171154aA,1); //<--- added here

        // Set the enumeration.
        _enumeratedAllowedSeaDrop = allowedSeaDrop;

        // Emit an event noting the contract deployment.
        emit SeaDropTokenDeployed();
    }

And it gives me the following error:
[⠒] Compiling...
[⠒] Compiling 78 files with 0.8.17
[⠊] Solc 0.8.17 finished in 9.85s
Compiler run successful with warnings:
Warning (5574): Contract code size is 30473 bytes and exceeds 24576 bytes (a limit introduced in Spurious Dragon). This contract may not be deployable on Mainnet. Consider enabling the optimizer (with a low "runs" value!), turning off revert strings, or using libraries.
  --> script/DeployAndConfigureExampleToken.s.sol:12:1:
   |
12 | contract DeployAndConfigureExampleToken is Script {
   | ^ (Relevant source part starts here and spans across multiple lines).

Warning (5574): Contract code size is 27955 bytes and exceeds 24576 bytes (a limit introduced in Spurious Dragon). This contract may not be deployable on Mainnet. Consider enabling the optimizer (with a low "runs" value!), turning off revert strings, or using libraries.
  --> script/DeploySeaDropCloneFactory.s.sol:10:1:
   |
10 | contract DeploySeaDropCloneFactory is BaseCreate2Script {
   | ^ (Relevant source part starts here and spans across multiple lines).

Warning (5574): Contract code size is 25025 bytes and exceeds 24576 bytes (a limit introduced in Spurious Dragon). This contract may not be deployable on Mainnet. Consider enabling the optimizer (with a low "runs" value!), turning off revert strings, or using libraries.
  --> src/extensions/ERC721SeaDropBurnable.sol:15:1:
   |
15 | contract ERC721SeaDropBurnable is ERC721SeaDrop {
   | ^ (Relevant source part starts here and spans across multiple lines).

Traces:
  [6234925] → new DeployAndConfigureExampleToken@0x5b73C5498c1E3b4dbA84de0F1833c4a029d90519
    └─ ← 30473 bytes of code

  [309288] DeployAndConfigureExampleToken::run()
    ├─ [0] VM::startBroadcast()
    │   └─ ← ()
    ├─ [243336] → new <Unknown>@0x71FCaB2Cd648f4b1c5f1BbAdf1f4526Cf8271346
    │   ├─ emit OwnershipTransferred(param0: 0x0000000000000000000000000000000000000000, param1: 0x373F3D184E7a9145B9a8c4528Fb48E79171154aA)
    │   ├─ [78371] OperatorFilterRegistry::registerAndSubscribe(0x71FCaB2Cd648f4b1c5f1BbAdf1f4526Cf8271346, 0x3cc6CddA760b79bAfa08dF41ECFA224f810dCeB6)
    │   │   ├─ emit RegistrationUpdated(registrant: 0x71FCaB2Cd648f4b1c5f1BbAdf1f4526Cf8271346, registered: true)
    │   │   ├─ emit SubscriptionUpdated(registrant: 0x71FCaB2Cd648f4b1c5f1BbAdf1f4526Cf8271346, subscription: 0x3cc6CddA760b79bAfa08dF41ECFA224f810dCeB6, subscribed: true)
    │   │   └─ ← ()
    │   └─ ← 0 bytes of code
    └─ ← 0x15e26ff3

Error:
Script failed.

Any way to fix this?

Use the internal _mint function instead, and as I said previously please open discussions instead of issues for your questions.


fix: add support for Decimal property values

Summary
This simple adding fixes converting dictionary which contains decimal value and passing through API.
We've faced with issue that decimal values were ignored on Amplitude console on this framework, but legacy framework works well.
Checklist

[x] Does your PR title have the correct title format?
Does your PR have a breaking change?:  No

Hi @doctorcooper, could you please fix the lint warnings?  Otherwise, I have been working on a more comprehensive fix for Encodable support that will be ready soon.

Hello @crleona !
Fixed lint warnings. Thanks!

Thanks @doctorcooper!

@doctorcooper, FYI: https://github.com/amplitude/Amplitude-Swift/pull/192


New deployment is showing as v1.2.1 instead of v1.2.2

Describe the bug
The latest branch is supposed to be v1.2.2 but my deployed TEAM is showing as v1.2.1

Can confirm, just updated


Postgres Docker image issue

Hi, i got an error like this when trying to get docker image for postgres:
Error pulling image (latest) from docker.io/library/postgres, Server error: Status 0 while fetching image layer (fa42b668d5b9b8f33530b22653686a58bd39b2efd7518061aa7546e2d23f8f84)
I using Windows 10 OS.
I'm new to docker.
Thanks

it's possible that you were disconnected - I would restart the VM to make sure the connection is solid and try again:
docker-machine restart default


Searching for a string with boolean / filter

Hi @karmi, thanks to your comment in this issue, I was able to get a set records based on a boolean.
Now, I'd like to combine the two. I'd like to search within the set of artists that have the has_music => true. I tried many ways of building this query, some of which are below:
Term
artist_search = Artist.search do
  query do
    string @query
  end
  filter :term, :has_music => true
end

The rest had parse errors:
artist_search = Artist.search do
  query do
    string @query
    boolean do
      must { string :has_music => true }
    end
  end
end

artist_search = Artist.search do |search|
  search.query do |query|
    query.string @query
    query.boolean do |boolean|
      boolean.must { string :has_music => true }
    end
  end
end

How do you combine the two?
Thanks

+1

artist_search = Artist.search do |search|
  search.query do |query|
    query.boolean do |boolean|
      boolean.must { string :has_music => true }
      boolean.must {string @query }
    end
  end
end

Probably like that?


removed SysNodeExpressions from GlobalReferenceResolver

also instantiate expressions that use os/network/jvm/process stats on demand and cache them in the resolver in order to be able to re-use the OS and process probes and achieve atomic os/process queries

changes.txt

ack, pls backport


MWPW-154249: Update mappings to support t3 events

Adding mapping for t-3 events hub pages.

Resolves: MWPW-154249
Test URLs:
For Milo Changes

Before: https://main--milo--adobecom.hlx.page/drafts/shkhan/mwpw-132559?martech=off
After: https://shkhan-events-t3--milo--shkhan91.hlx.page/drafts/shkhan/mwpw-132559?martech=off

For t3 testing
https://stage--events-milo--adobecom.hlx.page/events/hub
https://dev--events-milo--adobecom.hlx.page/events/hub

Closing this for now. Feel free to re-open when the PR is ready and out of the draft state and ready to be reviewed without any conflicts.


consuming store credits first during renewal

@bryanmtl , @peterberkenbosch
It seems that during renewals, this gem expects a credit card to be present. But some sites may have the https://github.com/spree-contrib/spree_store_credit_payment_method installed therefore some customers have store credits in their account that can fully cover the renewal and some subscription may not have a CC attached to it.
This causes an error during renewal. "uninitialized constant CreditCard"
My plan is to check and see if there are any "Spree::StoreCredit" payment method available, if so then I would consume the store credits amount first before attempting to look for and charge the customer's credit card.
Should you guys have another way in dealing with this let me know.
cc @alixgt

@mickeyren That sounds like a good place to start to me.

Did we solved this already? @mickeyren


Build Warning: Layout 'nil' requested in _posts/2012-12-28-response-status-codes.md does not exist.

Another change in Jekyll, whereby the entries in the posts where layout: nil is specified should now be changed to layout: null

@hunvreus @saraiva132 Could you please review #31 if possible? It should solve this ticket.

Fixed here: https://github.com/vivi90/a-la-carte


Possibility to override buttons onClickListeners and to set buttons visibility implemented

1º implementation:
Finish and back button:
Directly onClickListener replaced by overridable method;
Next button:
Added ordinaryScreenClickListener and its class;
Added next button functions constants;
2º implementation:
Directly onClickListener replaced by method that writes onClickListener action inside due variable to allow method overriding every single next button action;
Set button visible method created for all three buttons;
Initialization of back and skip buttons onClickListeners unified to take this responsibility out of set button visible methods.  Next button is out of this because it has multiple action;

closing due to lack of maintenance.


App loading off the screen

Hi,
I've updated to the latest OS X (10.11.2) no so long ago and now the Facebook Messenger app now loads off the screen boundaries, I am unable to drag the app back down to the centre of the desktop as well. Would there be a configuration file which sets where the load app on the screen?

Yes there is one. On mac I'm not very sure where it is located since I only use window and linux. Its a json file, so I imagine you can search for it...

I was unable to find the file myself due to lack of information, however, I was unable to result the issue. I installed CCleaner and used it's built in uninstaller to remove the program and any traces of it, re-isntalled it and now the issue is resolved.


Fix pool panics

We've been experiencing a few panics related to connection errors. Looks like storing error interfaces in atomic.Value isn't a good idea:
panic: sync/atomic: store of inconsistently typed value into Value

goroutine 1 [running]:
sync/atomic.(*Value).Store(0xc42009a0a0, 0x5fdb00, 0xc42011d540)
    /home/dim/.gimme/versions/go1.9.linux.amd64/src/sync/atomic/value.go:79 +0x10d
bitbucket.org/infectious/tsdb/vendor/github.com/go-redis/redis/internal/pool.(*ConnPool).setLastDialError(0xc42009a090, 0x76d840, 0xc42011d540)
    /home/dim/src/bitbucket.org/infectious/tsdb/vendor/github.com/go-redis/redis/internal/pool/pool.go:141 +0x4e
bitbucket.org/infectious/tsdb/vendor/github.com/go-redis/redis/internal/pool.(*ConnPool).NewConn(0xc42009a090, 0xc420097da0, 0xc4203f8001, 0xc4203f8000)
    /home/dim/src/bitbucket.org/infectious/tsdb/vendor/github.com/go-redis/redis/internal/pool/pool.go:106 +0x14a
bitbucket.org/infectious/tsdb/vendor/github.com/go-redis/redis/internal/pool.(*ConnPool).Get(0xc42009a090, 0x4114b7, 0xc4203f64c0, 0x40, 0x38)
    /home/dim/src/bitbucket.org/infectious/tsdb/vendor/github.com/go-redis/redis/internal/pool/pool.go:193 +0x16d

Released v6.7.2


merging fire_station node and area adds building tag

create node with amenity=fire_station (or have some to reuse)
create new way for the outline of the area.
select both
merge with the +
new way has amenity=fire_station AND building=yes   8-/

IMO the fire station can have multiple buildings inside and should be tagged on the area and not at the building. Example

Well this is a surprise to me. Up until January the advice on the OSM wiki was to map amenity=fire_station as a building, not as a property.
And sure enough, someone changed it recently (January of this year):  https://wiki.openstreetmap.org/w/index.php?title=Tag:amenity%3Dfire_station&diff=1551166&oldid=1401001
This sort of thing happens sometimes where a person will quietly change the OSM wiki with no plan for reviewing all the existing data or communicating this change to the people who write the software, then somebody else will show up on our repo a little while later complaining that "iD is doing a wrong thing".
Please stop this.  It is never ok to change the advice on the OSM wiki about whether a thing should be mapped as a building outline (the vast majority of things) or as a property outline (a short list of things that I know about and treat specially in iD to not confuse people).
Please put the page back to how it was before January, and accept that many of the fire stations in OSM are already tagged as buildings going back years.
There was a discussion on tagging@ about this as well (not specific to fire stations) but I can't find it now, because mailing lists are a terrible way to discuss things that you want to find later.
Sorry for the tone, but I get kind of angry every time people do this.  I'm not blaming you..


pin to specific version

Hi,
How can I build Caddy with specific souin version?
I could build it successfully last week, but today with latest changes (new olric...) its crashing.
How can I specify commit in this command?
xcaddy build --with github.com/darkweak/souin/plugins/caddy

I tried this, but it didn't work.
xcaddy build --with github.com/darkweak/souin/tree/f3669a8ebe3d71c967899793b21c066decb54593/plugins/caddy

Here is build log:
#8 34.81 2022/12/09 21:29:14 [FATAL] exit status 1
#8 ERROR: executor failed running [/bin/sh -c xcaddy build     --with github.com/caddy-dns/cloudflare     --with github.com/shift72/caddy-geo-ip     --with github.com/darkweak/souin/plugins/caddy]: exit code: 1

failed to solve: executor failed running [/bin/sh -c xcaddy build     --with github.com/caddy-dns/cloudflare     --with github.com/shift72/caddy-geo-ip     --with github.com/darkweak/souin/plugins/caddy]: exit code: 1
#7 [stage-1 1/2] FROM docker.io/library/caddy:2.6-alpine@sha256:25a0097607868fb05a89a5ab9fea2f2ea4cecdc89d887d7dcee8c778a21b9e1f
------
 > [builder 2/2] RUN xcaddy build     --with github.com/caddy-dns/cloudflare     --with github.com/shift72/caddy-geo-ip     --with github.com/darkweak/souin/plugins/caddy:
#8 25.70 go: downloading github.com/vmihailenco/tagparser/v2 v2.0.0
#8 30.92 go: downloading github.com/bits-and-blooms/bitset v1.4.0
#8 30.92 go: downloading github.com/mschoch/smat v0.2.0
#8 33.41 github.com/darkweak/souin/plugins/caddy imports
#8 33.41 	github.com/darkweak/souin/cache/providers imports
#8 33.41 	github.com/buraksezer/olric/client: cannot find module providing package github.com/buraksezer/olric/client
#8 33.41 github.com/darkweak/souin/plugins/caddy imports
#8 33.41 	github.com/darkweak/souin/cache/providers imports
#8 33.41 	github.com/buraksezer/olric/query: cannot find module providing package github.com/buraksezer/olric/query
#8 34.81 2022/12/09 21:29:14 [FATAL] exit status 1

thank you

Actually its not Souin that I need to pin, rather Olric.
Still, no idea how to solve it.

Hello @tasiotas you can use xcaddy build --with github.com/darkweak/souin/plugins/caddy@THE_SHA_OR_THE_VERSION --with github.com/darkweak/souin@THE_SHA_OR_THE_VERSION

thank you


brew bundle install and cleanup incorrectly handling casks from AdoptOpenJDK/openjdk

In a similar vein to #480 the commands brew bundle install and brew bundle cleanup will incorrectly identify the casks adoptopenjdk8 and adoptopenjdk11 to be installed and cleanup when they are in fact part of the Brewfile as primary dependency (and already installed via the same bundle).
brew update was run prior to brew bundle install.
The relevant parts of the Brewfile are:
tap 'homebrew/cask'
tap 'AdoptOpenJDK/openjdk'
cask_args appdir: '/Applications'
cask 'adoptopenjdk8'
cask 'adoptopenjdk11'

Output
$ brew update
Already up-to-date.
$ brew bundle install
Installing adoptopenjdk8
Installing adoptopenjdk11
Homebrew Bundle complete! 2 Brewfile dependencies now installed.
$ brew bundle install
Installing adoptopenjdk8
Installing adoptopenjdk11
Homebrew Bundle complete! 2 Brewfile dependencies now installed.
$ brew bundle cleanup
Would uninstall casks:
adoptopenjdk/openjdk/adoptopenjdk11                                                          adoptopenjdk/openjdk/adoptopenjdk8

I checked the brew files of both dependencies, they both use .pkg installers and are from a cursorily analysis not wildly different then say the firefox cask (from homebrew-casks). Maybe it has something to do with the AdoptOpenJDK dependencies requiring sudo and being installed in /Library/Java/JavaVirtualMachines/? Or is the sha256 version hash applied incorrectly to verify a particular version is, in fact installed?

Please paste the brew bundle check --verbose output for anything that wants to be installed that already seems to be installed. Closing for now as this seems user/cask specific.

As requested the output of the check command as well as the output of brew cask info for each of the two casks:
$ brew bundle check --verbose
brew bundle can't satisfy your Brewfile's dependencies.
→ Cask adoptopenjdk8 needs to be installed or updated.
→ Cask adoptopenjdk11 needs to be installed or updated.
Satisfy missing dependencies with `brew bundle install`.
$ brew cask info adoptopenjdk8
adoptopenjdk8: 8,212:b03
https://adoptopenjdk.net/
/usr/local/Caskroom/adoptopenjdk8/8,212:b03 (97.7MB)
From: https://github.com/adoptopenjdk/homebrew-openjdk/blob/master/Casks/adoptopenjdk8.rb
==> Name
AdoptOpenJDK 8
==> Artifacts
OpenJDK8U-jdk_x64_mac_hotspot_8u212b03.pkg (Pkg)
$ brew cask info adoptopenjdk11
adoptopenjdk11: 11,0.3:7
https://adoptopenjdk.net/
/usr/local/Caskroom/adoptopenjdk11/11,0.3:7 (181.4MB)
From: https://github.com/adoptopenjdk/homebrew-openjdk/blob/master/Casks/adoptopenjdk11.rb
==> Name
AdoptOpenJDK 11
==> Artifacts
OpenJDK11U-jdk_x64_mac_hotspot_11.0.3_7.pkg (Pkg)

What's the output of brew bundle dump?

The output of brew bundle dump is:
tap "adoptopenjdk/openjdk"
tap "homebrew/bundle"
tap "homebrew/cask"
tap "homebrew/core"
cask "adoptopenjdk/openjdk/adoptopenjdk11"
cask "adoptopenjdk/openjdk/adoptopenjdk8"

I guess then that simply using adoptopenjdk11 or adoptopenjdk8in the original Brewfile is insufficient?

I guess then that simply using adoptopenjdk11 or adoptopenjdk8in the original Brewfile is insufficient?

Yep!

Would you have any idea on how to "fix" that in the upstream adoptopenjdk casks, i.e. make it consistent with what I expected to happen in the first place when creating the Brewfile? I'd be willing to do the actual work, I just have no idea what needs changing.

Can't be fixed in the casks, just need to use the correct Brewfile syntax as otherwise the reference is ambiguous.


Add Hugo Pipes logic for local and vendored scripts.

@XhmikosR
I stored the Hugo pipe logic in a returning partial so we can:

not concern ourselves with whitespace and line breaks when working logics
use partialCached on the logic
compontentize.

Also:

When missing mounts, I'm using warnings instead of errors, but I think you wanted errors so the build is stopped. In this case we can replace warnf by errorf through the code.
For now the docsearch.min.js file is not published at the desired permalink (including version) but will after Hugo .74 introduces the new resources.Put method (see comment)
I'm not 100% sure the order in which files should be bundled is correct, but I don't have any errors in console.
I used my own conventions for file naming and commenting, feel free to adjust to the team's own.
I left alone the asset loaded from CDN (bootstrap.bundle.min.js), but once you are ready to let Hugo handle it we'll just have to include in the GetJSAssets partial.

Preview: https://deploy-preview-29283--twbs-bootstrap.netlify.app/

First of all, sorry for the late response; the weird times we are living in have hit me hard :/
I rebased my branch and yours, made a few typo fixes and renamed the partial.

When missing mounts, I'm using warnings instead of errors, but I think you wanted errors so the build is stopped. In this case we can replace warnf by errorf through the code.

Yup, that's the whole idea otherwise I think we could simplify this a lot.

For now the docsearch.min.js file is not published at the desired permalink (including version) but will after Hugo .74 introduces the new resources.Put method (see comment)

We are using a fairly recent Hugo build so feel free to adapt the code :)

I'm not 100% sure the order in which files should be bundled is correct, but I don't have any errors in console.

As long as the vendor files come first, it should be fine indeed

I left alone the asset loaded from CDN (bootstrap.bundle.min.js), but once you are ready to let Hugo handle it we'll just have to include in the GetJSAssets partial.

I think that's for another time since we currently just include the dist files (please correct me if I misunderstood something).

That being said, how do you feel of this approach in general? It seems it doesn't scale totally in the sense that we have 2 places we have to handle the vendor files; one is config.yml and the other one is the new partial. What's the alternative solution? Dropping this solution and just go with my patch only and in case a vendor file is missing we'll just get a JS runtime error?
Thanks again for the patch, I really appreciate helping us, especially now that we are moving towards v5 stale :)

I'm going to merge this to my branch for now and we can tweak it later hopefully :)


Cannot load ROMS from Everdrive 64 v3 flashcard

Thank you for creating this emulator. I have followed all instructions in the Readme file. When I start the emulator, I get a black screen which displays "Boot to BIOS" in white text. The only buttons that work on the N64 controller is the up and down d-pad buttons which change the cursor from an arrow to a flat line, and the B button which produces a visual distortion image which crashes the emulator.
I have made sure to have acquired the right BIOS files (and ROM files) and placed them in a folder named "press-f" as directed. I am using an Everdrive 64 v3 with a PAL Nintendo 64.
I'd like to help out in any way I can with this emulator. I hope this issue can help you in some way.

"Boot to BIOS" displaying but the A button not responding should indicate
the BIOS are seen to exist on the SD Card but can't be read for some
reason. Pressing B here backs out the emulation to a Channel F with no ROM
loaded.
I can introduce some error handling for accessing the files if you would
like to tell me the output of it. For now, can you confirm the BIOS files
are both of size 1KB?
On Tue, Nov 19, 2024, 6:14 AM jedipimp81 @.***> wrote:

Thank you for creating this emulator. I have followed all instructions in
the Readme file. When I start the emulator, I get a black screen which
displays "Boot to BIOS" in white text. The only buttons that work on the
N64 controller is the up and down d-pad buttons which change the cursor
from an arrow to a flat line, and the B button which produces a visual
distortion image which crashes the emulator.
I have made sure to have acquired the right BIOS files (and ROM files) and
placed them in a folder named "press-f" as directed. I am using an
Everdrive 64 v3 with a PAL Nintendo 64.
I'd like to help out in any way I can with this emulator. I hope this
issue can help you in some way.
—
Reply to this email directly, view it on GitHub
https://github.com/celerizer/Press-F-Ultra/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH5UPFXNTZIDXYMSXCDUYCD2BMTSLAVCNFSM6AAAAABSB5GXNKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY3TCOJQHAYTEMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

"Boot to BIOS" displaying but the A button not responding should indicate the BIOS are seen to exist on the SD Card but can't be read for some reason. Pressing B here backs out the emulation to a Channel F with no ROM loaded. I can introduce some error handling for accessing the files if you would like to tell me the output of it. For now, can you confirm the BIOS files are both of size 1KB?
…
On Tue, Nov 19, 2024, 6:14 AM jedipimp81 @.> wrote: Thank you for creating this emulator. I have followed all instructions in the Readme file. When I start the emulator, I get a black screen which displays "Boot to BIOS" in white text. The only buttons that work on the N64 controller is the up and down d-pad buttons which change the cursor from an arrow to a flat line, and the B button which produces a visual distortion image which crashes the emulator. I have made sure to have acquired the right BIOS files (and ROM files) and placed them in a folder named "press-f" as directed. I am using an Everdrive 64 v3 with a PAL Nintendo 64. I'd like to help out in any way I can with this emulator. I hope this issue can help you in some way. — Reply to this email directly, view it on GitHub <#1>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5UPFXNTZIDXYMSXCDUYCD2BMTSLAVCNFSM6AAAAABSB5GXNKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY3TCOJQHAYTEMY . You are receiving this because you are subscribed to this thread.Message ID: @.>

Hello, I tried two sets of the BIOS files and they were 1k.

On hardware, this program has only been tested on my Everdrive 64 X5, but I believe libdragon should support other Everdrive versions as well. As well as checking the size of both ROMs to be 1KB, the "press-f" directory is in the SD root, correct? (should be sd://press-f/sl31253.bin and not something like sd://roms/press-f/sl31253.bin)

Hmm you know what the folder is in a subdirectory. I’ll try moving it to the root folder and seeing if that makes a difference!

Sorry, one more question! Does the Press-F-Ultra emulator prefer the Channel F ROMS be in .bin or .chf format?

Are you copying the files over using a Mac? The files prefixed with ._ are metadata that is typically invisible in MacOS but will be seen on everything else. I suppose I should make the file browser ignore those and entries with blank filenames (I'm not sure why so many of those are showing in your case).
I will make these changes and push a new build later today.

Yes I am using a Mac. They may explain the ._
I’m going to try new ROM files to see if they make a difference as well.
Thank you so much for your help. I greatly appreciate people like yourself building up the retro emulator community for all of us to enjoy!

Hello, I've just published a new release here that should hopefully fix the issues we've discussed:
https://github.com/celerizer/Press-F-Ultra/releases/tag/r2
Thank you for your interest!

I'm going to close this as fixed. Feel free to reopen if there are any further issues.


charting menu question

What is your question?
what is the quant stuff in the charting menu for?

nvm i figured it out xd


Add new testnets

Added new Sepolia testnets as the older Goerli testnets are or are about to get decommissioned (with reference to #150). zkEVM Cardona is Polygon's new zkEVM testnet, the older testnet is about to be deprecated.

Arbitrum Sepolia testnet
Metis Sepolia testnet
zkEVM Cardona testnet

Call it polygon-zkevm-sepolia-testnet pls