Define home tab index and enable auto return to home after specified time

Would like to be able to define a home tab (default could be set to index 0) and then have the ability to define how many seconds after the last swipe that the dashboard will automatically return to the home tab. Would be nice when you have a tablet serving as an on wall dashboard control to always display a home tab after the last person used the dashboard and moved between tabs. This way you can always be sure the next time you use the dashboard your most desired cards/controls will be displayed.

Duplicate of https://github.com/zanna-37/hass-swipe-navigation/issues/44.


Enumerate & Test the potential fast tx-meta and captive core configurations.

In #3112, we have the following sub-task:

Different possible configurations are enumerated and tested for bugs.

This issue exists to fulfill the "enumeration" aspect of this task. It's intended to be deeply collaborative (since I don't have nearly as much context as anyone else), so please edit it freely to expand it with the various configurations you know more about. It also should serve as an almost copy-pastable breakdown for when we create user- and developer-facing documentation.
Configurations
Based on the design doc and other documentation related to the architecture of fast txmeta and captive core, we essentially support two key deployment strategies: all-in-one and multi-machine.
In both cases, the following Horizon parameters (that are likewise expressible as environmental variables) enables captive core:

--enable-captive-core-ingestion

while the following are used depending on whether or not the Core node lives with the Horizon node:

--stellar-core-config-path, --stellar-core-binary-path
--remote-captive-core-url

All-in-One
This deployment strategy is catered towards developers and users without serious load requirements that want to "get up and go" as quickly as possible. There are many ways to get going this way, in order of "we support it":

running the Debian-based packages directly,
Docker-based deployment, and
manual compilation and deployment.

Prebuilt Packages
In this route, we have a Ubuntu repository that hosts our packages. This involves configuring both Stellar Core and Horizon through their respective methods (the .cfg file and env vars, respectively) to enable captive core ingestion.
Naturally, manual compilation is nearly identical to the pre-built route, except Core is built from scratch. This is the likely deployment route if you're not on a Debian-based system.
In either case, given the following prerequisites:

existence of a stellar-core binary under /usr/local/bin,
two PostgreSQL instances: one with a DB named stellar on port 5641, and another named horizon on port 5432
the following (lengthy) command will run Horizon with a captive core instance:

$ STELLAR_CORE_DATABASE_URL='postgres://postgres@localhost:5641/stellar?sslmode=disable' `
  HISTORY_ARCHIVE_URLS='https://history.stellar.org/prd/core-testnet/core_testnet_001' `
  NETWORK_PASSPHRASE='Test SDF Network ; September 2015' `
  STELLAR_CORE_URL='http://localhost:11626' `
  INGEST=true PER_HOUR_RATE_LIMIT=0 `
  DATABASE_URL='postgres://postgres@localhost:5432/horizon?sslmode=disable'
  ./horizon --enable-captive-core-ingestion `
    --stellar-core-binary-path=/usr/local/bin/stellar-core `
    --stellar-core-config-path=stellar-core-testnet.cfg

Naturally, all of the paths and URIs can point to other locations (databases living in docker containers, for example) as needed.
Docker-based deployment
Do we have/want the equivalent of stellar/quickstart or our Compose-based workflow for captive core?
Kubernetes-based deployment
The multi-machine section on k8s will go into more detail, but essentially we have an additional manifest to provide a single-machine override to the Kustomize-based deployment configuration.
Multi-Machine
The other primary deployment method is be spread across machines, with each key component of the fast txmeta architecture---Captive Core, Horizon ingestion, and Horizon HTTP---separated and independently scalable.

Obviously, this is doable "by hand" much like the above methods, but we only support on a Kubernetes-based deployment solution via Kustomize.
TODO: This can be filled out with the relevant instructions when those are complete.

@Shaptic what's the status here?

At this point, I think we can actually abandon a lot of this enumeration. The migration guide and (pending) deployment docs should cover the "All-in-One" as well as the "Multi-Machine" sections (by virtue of describing Remote Captive Core) entirely.
The other remaining sections (Docker and K8s) remain unclear to me since we are (a) apparently continuing to support stellar/quickstart (has it been updated to deploy Captive Core correctly?) and (b) I haven't been exposed to the k8s side at all. (Note that this touches a bit on the "this should be collaborative" part in the intro :wink:).
@ire-and-curses I recommend we make separate issues for the latter two points if we want to move forward with documenting a recommended deployment process for them formally, but I can't make the call on whether or not that's the case.

Ok let's just close this for now. When we get there I would like to document K8s but we can do that then.
I think we're actually at a point where we can push quickstart deprecation, but we need to sync with @brahman81 on that, and right now we've all got a lot of other things on our plates.


lack of red dot

i added my proton accounts but when i receive an email it doesn't apear the red dot on proton in the bar and in the station icon on the dock (mac os)..
i have the g mail account and app and it work but with proton nothing..

#299


Use markdown-magic to keep README HTML link versions up to date

Description
Update script to maintain link package version automatically for embedded HTML examples of browser usage of Mocha in docs/index.md.
 <link<EMAIL_ADDRESS>rel="stylesheet" />
 <script<EMAIL_ADDRESS>
Additional Information
Use https://github.com/forresst/markdown-magic-package-json to achieve this.
Substitute "package.json" version for "5.2.0" above.

It seems no more needed in https://github.com/mochajs/mocha/commit/81c60f92cdc70740526d52c9a5c28d9d2abeaf40


bug: Pasting with vim-pasta results in corrupted undo

Check the following:

[X] I have checked the behavior after setting "vscode-neovim.neovimClean" in VSCode settings.
[X] I have read the vscode-neovim docs.
[X] I have searched existing issues.

Neovim version (nvim -v)
NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1716656478
Operating system/version
macOS 14.5
Describe the bug
Pasting with vim-pasta cannot be completely undone with u. It used to work up until v1.17.2. I tracked down the issue (using git bisect) to 61f4e4f842d7a7a559b60e7e82f3acb26c908abb introduced with https://github.com/vscode-neovim/vscode-neovim/pull/2127.
In other words, vim-pasta appears to modify the buffer such that the changes cannot be undone cleanly by pressing u until no more recorded changes exist. I suspect this bug is not strictly related to the plugin, but so far I have not been able to reproduce it without vim-pasta.
Steps To Reproduce

Install vim-pasta
Yank a couple of lines
Paste x times
Undo x times

Expected Behavior
All changes are reverted. The statusline reads "Already at oldest change". The dirty indicator is not visible.

"editor.formatOnSave": true, seems to be another prerequisite.

It's unlikely that this will be fixed (you can only modify "editor.formatOnSave"), but you can try a more modern plugin, gbprod/yanky.nvim (Implemented using the nvim API, it results in fewer changes.)
You can subscribe to: https://github.com/microsoft/vscode/issues/221614


How to rename the node from item to some thing which am interested in for Element as an array in an array

DataFrame with a schema below:
 |-- a: array (nullable = true)
 |    |-- element: array (containsNull = true)
 |    |    |-- element: string (containsNull = true)

with data below:
+------------------------------------+
|                                   a|
+------------------------------------+
|[WrappedArray(aa), WrappedArray(bb)]|
+------------------------------------+

produces a XML file below:
...

    <item>aa</item>

    <item>bb</item>

...

How can i rename the item tag to something what am interested in.

Hm, I see. It sounds able to be configurable..

https://github.com/databricks/spark-xml/pull/603


[prim] Select proper generic implementation in prim_ram_2p_async_adv

Split off from #1066
This fixes a bug in prim_ram_2p_async_adv by selecting a valid generic configiguration. Without this change the memory only ever outputs 0. The unit only seems to be used in the USB device.

Thanks @stefanlippuner for fixing this bug and congrats for getting your first PR merged ;-)


New boundary attack

Description
This is an implementation of a new boundary attack by Li and Zhang (https://arxiv.org/abs/2007.15528).
Fixes #1167
Type of change
Please check all relevant options.

[ ] Improvement (non-breaking)
[ ] Bug fix (non-breaking)
[x] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing
I included a test in tests/attacks/inference/membership_inference/test_label_only_boundary_distance.py which runs the newly implemented calibration method (calibrate_distance_threshold_unsupervised). This test is basically a copy of test_label_only_boundary_distance_prob_calib.

[x] test_label_only_boundary_distance_prob_calib_unsup

Test Configuration:

Ubuntu 20.04 (Focal Fossa)
Python 3.8.10
commit number: 4c5b12eb
TensorFlow  2.3.2 / Keras 2.4.3 / PyTorch 1.8.1 / MXNet (not installed)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Codecov Report

Merging #1197 (41aca91) into dev_1.8.0 (4db46b5) will decrease coverage by 43.00%.
The diff coverage is 4.54%.

@@              Coverage Diff               @@
##           dev_1.8.0    #1197       +/-   ##
==============================================
- Coverage      64.77%   21.76%   -43.01%
==============================================
  Files            221      221
  Lines          19203    19213       +10
  Branches        3509     3511        +2
==============================================
- Hits           12438     4182     -8256
- Misses          5367    14781     +9414
+ Partials        1398      250     -1148

Impacted Files
Coverage Δ

...mbership_inference/label_only_boundary_distance.py
18.88% <4.54%> (-22.29%)
:arrow_down:

art/attacks/poisoning/perturbations/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...essing/expectation_over_transformation/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...formation/natural_corruptions/zoom_blur/pytorch.py
0.00% <0.00%> (-88.58%)
:arrow_down:

...mation/natural_corruptions/zoom_blur/tensorflow.py
0.00% <0.00%> (-87.88%)
:arrow_down:

...rt/defences/detector/poison/clustering_analyzer.py
8.22% <0.00%> (-86.71%)
:arrow_down:

...ces/detector/evasion/subsetscanning/scanningops.py
11.59% <0.00%> (-85.51%)
:arrow_down:

...ormation/natural_corruptions/shot_noise/pytorch.py
0.00% <0.00%> (-81.82%)
:arrow_down:

...ation/natural_corruptions/shot_noise/tensorflow.py
0.00% <0.00%> (-81.82%)
:arrow_down:

...tion/natural_corruptions/gaussian_noise/pytorch.py
0.00% <0.00%> (-81.82%)
:arrow_down:

... and 142 more

I only ran existing tests from test_label_only_boundary_distance.py since my changes only affected the LabelOnlyDecisionBoundary attack. Should I run all tests just in case?

I think that should be ok. I just started the full set of checks here which I expect should pass.


clarify autopilot scenario

#5076

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@DulceMontemayor - PR has been copy edited and is ready for final review. This is based on issue #5076
Thank you.
cc: @kenwith


Listener interface causes lots of string creation & parsing overhead

Even though header names are required to be strings the interface emits them as byte[] which requires the recipient to decode and copy to create the equivalent string every time creating unnecessary garbage.
Additionally many common values have a parsed representation that is not a string:

numeric type (:status)
repeated value (content-encoding),
more complex structure (P3P, User-Agent, ..)
handler reference (:path)

Being able to store the representations that applications ultimately use with values cached in the hpack table will lower parsing costs.

@scottmitch @nmittler from Netty land
Related stuff
https://github.com/netty/netty/issues/3597


mac版本忘记密码

Description
mac版本忘记密码怎么重置呀
Problem
No response
Other Description
No response
Checklist

[X] I am using the latest version and have confirmed that the feature is not yet implemented in the latest version
[X] I have searched for similar feature requests before submitting this one

输入./ddns-go -resetPassword 123456提示./ddns-go: No such file or directory。不是docker安装，不好找配置文件在哪

ddns-go下载解压目录


Adding support for local SGD.

Hi,
As discussed with @muellerzr , I am adding a non-breaking functionality to support local SGD, which enables efficient multi-GPU training in the case when no fast interconnect is possible.
This replaces a previous pull request
I incorporated recommendation to change the per device batch size and I also removed the erroneous code (borrowed from the examples) that reduced the size of the dataset (as well as code-related recommendations) and retested everything. There is still some unexplained behavior, but it looks almost reasonable now:
Here is a link to the summary of results and benchmarking code.
Importantly @sgugger @muellerzr I think it is possibly every no-trainer example has this line that reduces the dataset size, but I think it's a bug. Please double check!
It is not clear what kind of unit test can test this kind of functionality. The key ingredient (disabling gradient synchronization is being tested already).

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

@searchivarius any particular reason for closing/reopening later rather than modifying on the PR branch and having a trail to follow back through on the PR comments?

@muellerzr I just wanted to squash commits. If this is not an issue, I can reopen the PR & make additional commits, just let me know.

Not an issue at all, we squash all commits upon merge anyways

PS: @muellerzr  not quite ready yet, I am still making changes and testing.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

@muellerzr it should be ready, I am not sure why the quality check fails, make quality or 'make style` do not suggest any changes when run locally. Perhaps, there's some version mismatch.

@searchivarius you should try doing pip install -e .[quality], as we pin what versions we use which could be part of it? :)

@muellerzr it doesn't make a difference.

@searchivarius perhaps uninstall then reinstall everything in the docs dep? Otherwise I can fork + put a PR in to fix it. Aka:
pip uninstall black flake8 hf-doc-builder -y

pip install -e .[quality]

Note that you'll also need urllib3 to be < 2.0.0

Hi @muellerzr this didn't help: moreover, make style and make quality do not reformat the code. I suspect it's something about the version of black and ruff that is being installed. Do you know which versions do you use?
BTW, regarding urllib3:
>>> urllib3.__version__
'1.26.14'

Perfect, that's the right version of urllib3.
For the other deps, try installing these versions:
pip install black==23.1 ruff==0.0.241 hf-doc-builder==0.4.0

@muellerzr thank you, now the file is reformated properly. This is a chance that versions were not an issue, but I was rather working on a wrong branch. There's no way to know this for sure though.

@muellerzr @sgugger NP and thank you for the guidance. Do not forget to remove the division by the number of steps in examples like this one:
https://github.com/huggingface/transformers/blob/main/examples/pytorch/question-answering/run_qa_no_trainer.py#L758


Add missing test

I had put a test file in the wrong place.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.72%. Comparing base (86bee1c) to head (0cf04a7).

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #70      +/-   ##
==========================================
+ Coverage   97.80%   99.72%   +1.91%
==========================================
  Files           7        6       -1
  Lines         730      718      -12
  Branches      165      164       -1
==========================================
+ Hits          714      716       +2
+ Misses         13        1      -12
+ Partials        3        1       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


About segmentation mask

Thanks for sharing your code with us.
I have a question about how you trained your mask-rcnn since there is no GT mask.
Looking forward to your response.
Best wishes~

The mask head is trained with the generated instance masks pseudo-gt rendered together with the instance disparity pseudo-gt. If you need more detailed information like where those pseudo-gt masks are located, @f-sky can provide more information.
Additionally, manually annotated dataset like KINS would also be useful if you need more accurate mask boundaries.
Cheers~

Feel free to reopen this issue if you have more question.


Doc Feedback: APIM Default Ports (7611 & 7711)

Location : https://apim.docs.wso2.com/en/latest/install-and-setup/setup/reference/default-product-ports/
7611 - Authenticate data published when Thrift data publisher is used for throttling.
7711 - Port for secure transport when Thrift data publisher is used for throttling.
Why does the documentation specifying these default ports being used for Throttling as well as Analytics?
I cannot see anywhere in the docs which relate these ports to throttling.
Please check with the APIM team, and correct if necessary.

When it comes to data publishing we have two implementations such as binary and thrift [1]. In throttling by default, we use the binary type, and ports are 9611/9711. You can change this type to thrift for throttling data publishing and then the ports are 7611/7711. For some cases, we have users who use both types.
[1] - https://apim.docs.wso2.com/en/latest/reference/config-catalog/#api-m-throttling-configurations

This is for APIM ports
7611 - TCP port to receive throttling events. Required when Thrift data publisher is used for throttling.
7711 - SSL port for secure transport to receive throttling events. Required when Thrift data publisher is used for throttling.
9611 - TCP port to receive throttling events. Required when Binary data publisher is used for throttling.
9711 - SSL port for secure transport to receive throttling events. Required when Binary data publisher is used for throttling.
This is for analytics
7612 - TCP port to receive analytics events. Thrift data publisher is used.
7712 - SSL port for secure transport to receive analytics events. Thrift data publisher is used.


counter resizes windows

Thank you for your contribution to the Koda - Generative Art Marketplace.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #10024
[ ] Requires deployment <worker/stick/speck>

Before submitting pull request, please make sure:

[ ] My contribution builds clean without any errors or warnings
[ ] I've merged recent default branch -- main and I've no conflicts
[ ] I've tried to respect high code quality standards
[ ] I've didn't break any original functionality

Optional

[ ] I've tested it at </ahp/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Did your issue had any of the "$" label on it?

[ ] Fill up your DOT address: Payout

Community participation

[x] Are you at Koda Ecosystem Telegram?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

https://github.com/kodadot/nft-gallery/assets/76876702/b854099e-3180-4de2-a68e-1fb12eb4826f

Missing working Proof

updated

https://github.com/kodadot/nft-gallery/assets/22471030/2fe47b9a-920e-4607-bb82-8b470c4b803c

@yangwao how to reproduce?
can you test?

@prury It happens around the ipad breakpoint. The button changes the size of the card making it bigger when there is a decimal.
I just tested and my solution doesn't appear to fix it so I'll test with a real tablet in a bit.
How do you connect koda to subwallet on touch devices?

@prury It happens around the ipad breakpoint. The button changes the size of the card making it bigger when there is a decimal. I just tested and my solution doesn't appear to fix it so I'll test with a real tablet in a bit. How do you connect koda to subwallet on touch devices?

oh, thank you
using a real touch device you have to enter inside wallet app and use their built-in browser
to simulate one you can connect with koda on desktop, resize using browser tools and then refresh

cc @hassnian

Closing as bug still present after two weeks:
bug still present.webm


Is Moya still under active development?

Hello to whoever is still maintaining this package!
First of all, I would like to thank you for your effort as Moya is used in quite a few apps that I maintain. I couldn't help but to notice though that the project seems a bit stale, issues and PRs are piling up and this project has a few easily fixable issues that were not solved in over 6 months (though the PRs are there).
On the README file, user "Project status", the project is listed as under "active development" with the claim that it's being actively used by Artsy. However, to the best of my knowledge, Artsy made the switch to React Native back in 2016 and I have also noticed that the main contributors are not as active anymore.  So it begs the question: is Moya still under active development or is it now under life support? Is the project looking for new contributors and/or maintainers or perhaps someone willing to fork it and have it live on as a new package?

Hey @AndrewSB, I see that you are the most recently active contributor to Moya. Would it be fair to assume that this project is now under life support?

hey! sorry for missing this.
yes, I'd say so. there are no new features planned anytime soon.
if anyone wants to take charge and lead some fixes or new features, I can take a look at them, and help with questions, but unfortunately I don't have more than an hour or so a month to help maintain the project right now

Hey @AndrewSB
Thank you for responding.
So Moya is still an important piece of software for me and for others. I myself have 3 apps that depend on it and I believe that the biggest hurdle right now is that RxSwift has had a major version update and Moya has a trnasitive dependency to RxSwift 5. I have a PR open that updates that dependency to RxSwift 6.X.X, but I believe that I might be a better approach to completely remove both RxSwift and ReactiveCocoa from the project and create separate reactive extensions so that Moya doesn't need to be updated every time either of these frameworks has a major version change (even if people themselves have to write these reactive extensions, this is trivial work).
Since I rely on Moya a lot and I really like how it creates a neat interface for network calls, I've been thinking a lot about its future and maybe even volunteering to become a maintainer, but doe to the sheer size of of the project I don't think I would have enough bandwidth to deal with it. This is when it hit me: Moya is quite massive. It's a massive abstraction built on top on another massive abstraction which is Alamofire. I understand that this made a lot of sense when Moya was created at Artsy at around 2015. Artsy was probably already using Alamofire and relying on stuff such as certificate pinning (and the URLSession APIs weren't as competent as they are today). This is when I got the idea: what if I were to write a library based on Moya's interface (with a few adjustments based on what I think it could be after years of usage) and drop the Alamofire dependency which is, IMO, unnecessary in 2021. I have actually started work on this library and it's already working quite well on a project of mine which does all sorts of requests (plain, encodable, multipart, file upload) and it also handles stuff such as authentication methods (including refresh tokens). Now this library will not be ready for third-party usage for some time as I am still working on it as things are still prone to change as I make my mind on how to better do some things in 2021, so Moya is and will still be the first option for many apps out there.
What I propose here is: we do whatever is necessary to merge the RxSwift PR into main (this shall give Moya perhaps another year or so) and update the README to reflect the fact that the project is now under life support and that replacement libraries are not only encouraged but some are already being developed.
What do you think?

I also still use Moya for the app that I work on. luckily, I don't use RxSwift or ReactiveSwift any longer so it feels less precarious to me.
That sounds like a good plan to me. I tried to fix CI in https://github.com/Moya/Moya/pull/2159, but I haven't had the time to finish fixing it.
Are you using your RxSwift PR? It seems safe enough to merge into development & have people target that branch

@AndrewSB yes, I am using that PR for a while now and it's safe. It basically just replaces the deprecated RxSwift methods with the newer ones and bumps the dependency major version on the Podspec.

There have been a number of conversations about removing Moya's dependency on Alamofire, I've always thought it was a great idea. The core network abstraction is useful by itself

I think removing that dependency is a great idea but I might be wrong and might yet to stumble on something  big that Alamofire easily solves. Let's see how my little experiment goes. So far, the only thing I noticed is that with one less layer of abstraction, debugging network calls gets way easier.

sounds good, if you're able to get something that works, we'll likely leave it on a long-running branch for quite a while. It may not be wise to ship that large a breaking change to a release, or the master branch.
I could see another repository under the Moya org that we could use to stage a lighter Moya

could you update your PR to target development? we can merge it in there now in that case

@AndrewSB done  ;)

Now that I can do some open source again, I'm giving Moya some love by making sure we can keep its build succeeding and making sure we can update dependencies. Thanks for reaching out to us, @raphaelcruzeiro — I'm going to close this issue for now given where we're at now. :)


A simple broadcast using scratch buffer and option to use an executor on top of the main branch.

This PR has the broadcast algorithm that was present in the anantharamus/broadcast-amd branch but on top of the main branch.
It also has Mahdieh and Binyang's setup to use the executor plans for broadcast.

/azp run

/azp run mscclpp-ut


Fix #243 Cannot find module '@/app/ui/fonts' error

Issue: Resolves #243
Changes Made:

Fixed the 'Cannot find module '@/app/ui/fonts' error.

Description:
I have resolved the issue by adding "fonts.ts" file under app/ui directory
import { Inter , Lusitana} from 'next/font/google';
export const inter = Inter({
  subsets: ['latin']
});
export const lusitana = Lusitana({
    weight: ['400', '700'],
   subsets: ['latin'],
});

Test:
I have tested the changes locally to ensure that the error is fixed.

I think the omission of the fonts.ts file is intentional - there is a chapter in the nextjs.org/learn series that walks-thru adding this file to the project.

@RichardIshimwe Please see: https://nextjs.org/learn/dashboard-app/optimizing-fonts-images#adding-a-primary-font

I don't this pr is required


fix test

Fix a couple of issues:

Get rid of nans before using min to find indexes (by default naT was not dropped by min)
round returns floats, so convert to integers

Hello @malmans2! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file oceanspy/_oceandataset.py:

Line 998:89: E501 line too long (89 > 88 characters)

In the file oceanspy/subsample.py:

Line 546:89: E501 line too long (91 > 88 characters)


Adding German translation and fixing small translation bug

Thank you for submitting a pull request!
Description

FEATURE: Add German translation
FIX: Missing translation of 'Generate' button title

No linting errors
Expected behavior in webpack-dev-server

Type of Pull Request

[x] Adding a feature
[x] Fixing a bug
[ ] Maintaining documents
[ ] Others ()

Verify the followings

[x] Code is up-to-date with the main branch
[x] No lint errors after npm run lint
[x] Make sure all the exsiting features working well

Refer to CONTRIBUTING.MD for more details.

@ckFiber Thank you for the pull request. I have released it as v1.2.22

@ckFiber by the way, Could you add German translation to maplibre-gl-export, too (if possible)?
https://github.com/watergis/maplibre-gl-export

@ckFiber by the way, Could you add German translation to maplibre-gl-export, too (if possible)?
https://github.com/watergis/maplibre-gl-export

@JinIgarashi I'll try if I find some time.


viz workflow

Closed and re-opened as #4 because the repository was deleted and recreated, which loses all information about forks, PRs, etc.


installing nngraph via luarocks throws an error

When I try to run the command:
luarocks install nngraph
This gets displayed:
"Installing https://raw.githubusercontent.com/torch/rocks/master/nngraph-scm-1.rockspec...
Using https://raw.githubusercontent.com/torch/rocks/master/nngraph-scm-1.rockspec... switching to 'build' mode
Cloning into 'nngraph'...
fatal: unable to connect to github.com:
github.com[0: <IP_ADDRESS>]: errno=Connection timed out
Error: Failed cloning git repository."
I know I can connect to github correctly in the browser, and even cloning other repositories using git doesn't throw an error, so why is this happening? I assume it's because the repository is broken or doesn't exist anymore, but I want to see what the real issue is, because I don't see anyone talking about this in the issue tracker. Sorry if this is worded a bit weirdly.
OS: Ubuntu 22.04.2 LTS

I was able to get around it eventually by using:
git config --global url.https://github.com/.insteadOf git://github.com/
I also ensured I had my gitconfig already created with my user information.


Allow Range Fields on UDTs

Updated the type-checker to recognize UDT field references that refer to fields named Start, Step, and End without raising a type error.

@ScottCarda-MS Does this address #857

@ScottCarda-MS Does this address #857

Yes I'll respond to and close that issue when this is merged in.


Raise the flit-core limit for Python 3

flit-core is on version 3.9 now so I hope we can unpin this.

@tjni why do you hope this? IIRC the upper bound was mandated by Pex's continued support for Python 2.7, which is non-negotiable in the Pex 2.x release series.

I'm in an environment that is only using newer versions of flit-core. Your rationale for pinning makes sense, I updated the PR to keep the pin in Python 2 environments.

I'm sorry to keep pressing, but in what environment do you care about build requirements for a project that distributed a universal wheel? Pex vendors what would otherwise be its install requirements in order to be usable in any runtime environment. I have never thought of doing the same for its build requirement. The more detail you can provide that explains how this current setup affects you would be great. Although this seems harmless I'd like to understand the why before proceeding.

Sure, I understand and don't mind the questions. I work on packaging in nixpkgs and we build everything from source. We also don't keep around more than one version of a package (with rare exceptions), so we spend some energy on getting packages to work well with newer versions of their dependencies.

Ok, that makes sense then. We'll see what CI says, but I think your 1st change may have been sufficient although I prefer at least an upper bound on the major version on the grounds major versions are "allowed" to break folks and I don't want my build to break. I'm not sure if you've been tox -e<env> to test this out locally or not.

I'm happy to add the upper limit as well as try out just the first one if this CI run is happy.

Ok, I think just a single flit_core>=2,<4 should do it. Pip should pick the right flit for Python 2 & 3 respectively and the upper bound keeps the semver major version of the current 3.9.0 stable release so we don't pick up any breaks allowed in 4.x releases by mistake. This means nix may suffer pain in the future, but I imagine caring about build requirements already puts nix in this position more generally.

Let me update it and we can see what CI says.

This means nix may suffer pain in the future, but I imagine caring about build requirements already puts nix in this position more generally.

I appreciate you allowing the bound relaxation. I didn't realize you were still supporting Python 2, so doing this certainly adds more maintenance surface area, although I hope not a lot.


chrome-cli in crontab of MacOS may not work properly

Using "terminal" or even "remote terminal" (ssh) in macOS works just fine with chrome-cli.
All you need to do is just click on "OK" when some privacy notification windows pops up.
Then some entries will just appear in "Privacy" -> "Automation", indicating that some apps are allowed to access chrome's data directories.
But when I try to add some script regarding "chrome-cli" in "crontab".
(For example, just "chrome-cli chrome version" as simple as it is)
It will just print (null) on screen or file.
Is there any workaround for this?
I searched on the internet, unfortunately we can never add/remove apps manually in "Privacy" -> "Automation" configuration.
What I guess is that all I need is adding "cron" in "Automation".

As a workaround, add a LaunchAgent (that runs periodically) to dump the chrome-cli output to a file and let "cron" job read from this file. Have tried invoking "chrome-cli" from LaunchAgent is working fine.


Add RepositoryURL data to Issue type

Retrieve repository_url data returned for Issues from GitHub API (Fix #739)

@artmello You also need to run go generate as per the contributing guide - that should make the build pass.
I'll note that repository_url is part of the documented reponse at https://developer.github.com/v3/issues/#get-a-single-issue,  but it seems we are missing several other fields, including labels_url, comments_url, and events_url.

but it seems we are missing several other fields, including labels_url, comments_url, and events_url.

That sounds accurate. We can either add those too, or defer doing so until someone runs into a concrete need for them. Either way is fine. I’ll leave it to PR author to decide.

Thanks for reviewing it. I added the other 3 missing URLs  and executed "go generate". Should I take some action related with "Repository" field (remove it)? On my test case, getting issues from search or from IssuesService, this field is always nil, but I am not that familiar with the code base to know if it can be populated somewhere else

It probably is populated elsewhere. We don't need to deal with it as part of this PR.


DynamoDB Single Table Eventstore

One option for configuring the DynamoDB Event Store is to use a SingleTable setup. This approach could reduce the amount of repetitive code required to create a new table for each aggregate. Furthermore, it could enhance performance by enabling multiple aggregates to be fetched in a single call at a later stage, potentially also leading to cost savings.

@nirweiner2 Thanks for the suggestion :)
Indeed, I was thinking about adding the event store id as a prefix for aggregate partitions to the DynamoDBEventStorageAdapter so one table could serve for several event stores. Would that be a good solution for you ?

You mean, the aggregate type. Correct?
If that's what you mean then I think this is the right way to do it. :)
On Thu, Apr 20, 2023, 18:59 Thomas Aribart @.***> wrote:

@nirweiner2 https://github.com/nirweiner2 Thanks for the suggestion :)
Indeed, I was thinking about adding the event store id as a prefix for
aggregate partitions to the DynamoDBEventStorageAdapter so one table
could serve for several event stores. Would that be a good solution for you
?
—
Reply to this email directly, view it on GitHub
https://github.com/castore-dev/castore/issues/93#issuecomment-1516581349,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKVS35NPR6WRCCP6JVUWQTDXCFMOJANCNFSM6AAAAAAXFWMWEI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes, so if you're event store id is called POKEMONS, you would have the following event details in DynamoDB:
{
  aggregateId: "POKEMONS#01234567" // <= Pokemon id prefixed by POKEMONS
  version: 10
  type: "POKEMON_CATCHED"
  ...
}

Exactly
On Thu, Apr 20, 2023, 19:28 Thomas Aribart @.***> wrote:

Yes, so if you're event store id is called POKEMONS, you would have the
following event details in DynamoDB:
{
aggregateId: "POKEMONS#01234567" // <= Pokemon id prefixed by POKEMONS
version: 10
type: "POKEMON_CATCHED"
...}
—
Reply to this email directly, view it on GitHub
https://github.com/castore-dev/castore/issues/93#issuecomment-1516621602,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKVS35ONNWPZC2SJ7ETQGMLXCFP2TANCNFSM6AAAAAAXFWMWEI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Failed setup with 0.4.1

Not working for me anymore.  See below screengrabs.  How can I help debug?

Does the same happen if you try with a different provider?

I have the same error since I updated to 0.4.1 on May 9.  I just noticed that my Energy dashboard has no consumption costs since then. Let me know what information I can provide to assist.  The log entry I have is the same as provided abive by ryanwalexander.


Java API: About mediaTypeDiscovery

The Java API that the previously created  is no longer work after 45.0.6.  I get the following error when connecting to the Black Duck Hub.
Exception in thread "main" java.lang.NoSuchMethodError: com.synopsys.integration.blackduck.api.generated.discovery.MediaTypeDiscovery.determineMediaType(Ljava/lang/String;)Ljava/lang/String;
It seems that MediaTypeDiscovery has a new method added.
Why is it needed to connect to the Black Duck Hub?
Could you tell me how to use this method for connect hub.
Thank you!

I will try and create a test soon that will show you how we'd recommend using the library. For now, I would suggest using BlackDuckServerConfigBuilder to create a BlackDuckServerConfig, which you can use to create a BlackDuckServicesFactory.
With that factory, you can create the various services we expose to connect to Black Duck, and using their api's should (hopefully!) be clear enough.
Is there a particular problem you are trying to solve?
Thanks for reaching out!

I will try and create a test soon that will show you how we'd recommend using the library

I'm sorry for your inconvenience but thank you for your cooperation.

suggest using BlackDuckServerConfigBuilder to create a BlackDuckServerConfig,
which you can use to create a >BlackDuckServicesFactory.
With that factory, you can create the various services we expose to connect to Black Duck,

Thank you for the information. I will try it.
Thanks and Best regards.

@ekerwin
When I run the API with BlackDuckServerConfigBuilder, such as
blackDuckServerConfigBuilder= new BlackDuckServerConfigBuilder();
The following error has occurred.
Exception in thread "main" java.lang.NoClassDefFoundError: com/synopsys/integration/rest/support/UrlSupport 	at com.synopsys.integration.blackduck.service.BlackDuckServicesFactory.createDefaultUrlSupport(BlackDuckServicesFactory.java:91) 	at com.synopsys.integration.blackduck.configuration.BlackDuckServerConfigBuilder.<init>(BlackDuckServerConfigBuilder.java:77)
And I found in the "integration-rest" API, The follow file did not exist at version 5.0.0
[(https://github.com/blackducksoftware/integration-rest/tree/master/src/main/java/com/synopsys/integration/rest/support/UrlSupport.java) ]
What should I do for fix it?
Thanks and Best regards.

For version 49.1.0, which is the latest:
BlackDuckServerConfigBuilder` blackDuckServerConfigBuilder = new BlackDuckServerConfigBuilder();
blackDuckServerConfigBuilder.setUrl("https://blackduck_server");
blackDuckServerConfigBuilder.setUsername("username");
blackDuckServerConfigBuilder.setPassword("secret_password");

BlackDuckServerConfig blackDuckServerConfig = blackDuckServerConfigBuilder.build();
IntLogger logger = new PrintStreamLogger(System.out, LogLevel.DEBUG);
BlackDuckServicesFactory blackDuckServicesFactory = blackDuckServerConfig.createBlackDuckServicesFactory(logger);

With a BlackDuckServicesFactory, you can create the various services you might need. And if you want just a low level api client, you can use the BlackDuckService:
blackDuckServicesFactory.getBlackDuckService();
As for why media type discovery is needed, Black Duck wants certain values set for the HTTP Accept header and the media type discovery class is in charge of determining the correct media type value to use in that header.

It looks like your issues are from trying to include different versions of the libraries. You should only need to include the single blackduck-common 49.1.0 jar dependency. If you try and include old versions of the other integration libraries, you can get the errors you are seeing. If you are able to just include blackduck-common and are still unable to use the library, please re-open this and we can get you some more direct support. Thanks!


Updated .nvmrc to use v16

Description
Updated .nvmrc to align node version with dev.yml

Thank you!


Feat/ktabs

Looks like the tabs are inaccessible, we need to add aria attributes and allow users to be able to key through them:
Reference docs:
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Tab_Role
https://www.w3.org/TR/wai-aria/#tablist

Looks like the tabs are inaccessible, we need to add aria attributes and allow users to be able to key through them:
Reference docs:
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Tab_Role
https://www.w3.org/TR/wai-aria/#tablist

Attempted to format the MDN example into what has been built in this PR but it was unsuccessful. Instead I added aria labels, a tabindex and a handler to select the focused tab


User data scripts aren't executed when adding slaves

I think I've found a bug in the add-slaves command (or maybe I'm just misunderstanding how it's supposed to work). Here are my version specs:

Flintrock version: 1.0.0
Python version:  3.7.4
OS: MacOS Catalina 10.15.4 (19E266)

I create my cluster with a configuration file that looks like this:
services:
  spark:
    version: 2.4.5
  hdfs:
    version: 2.7.7

provider: ec2

providers:
  ec2:
    ...  # Omitting region, availability zone, etc here for brevity
    instance-type: m5.large
    ami: ami-0ce49ca477b768354
    user-data: scripts/install-python3.sh

launch:
  num-slaves: 2
  install-hdfs: True
  install-spark: True

debug: false

The user data script at scripts/install-python3.sh installs Python 3.7 and looks like this:
#!/usr/bin/env bash

set -e

sudo yum install -y python3 python3-devel python3-pip python3-setuptools python3-virtualenv

As expected, when I run flintrock launch the cluster is created and each node has Python 3 installed. I've verified this manually by SSH'ing into each node and checking.
Next, I add a single node by running flintrock add-slaves --num-slaves 1. When I log into the new node, Python 3.7 is unavailable. This is an unexpected result (in my opinion), but I'm not sure whether it's the intended behaviour or not so I'm reporting it here.
Thanks for the otherwise excellent tool! :)

Hello @dhorgan. Happy to hear that Flintrock is useful to you.
Thank you for submitting a well-written report. I can confirm that Flintrock is not attaching the correct user data to new slaves when it adds them to an existing cluster.
I suspect something is going wrong here, probably with the encoding of the data: https://github.com/nchammas/flintrock/blob/52c6c84c9a1845b0ce89ca138172a6ec4cf0d632/flintrock/ec2.py#L281

By the way, Flintrock's default (and my recommendation) is to use Hadoop 2.8.5.


Gram Schmidt on EmbeddingSet #159

I've created a first implementation to fix https://github.com/RasaHQ/whatlies/issues/159. I'm kind of proud of the notation but I should double check the numerical accuracy.
Internally I am using this idea.
import numpy as np
from functools import reduce
from whatlies import EmbeddingSet

away_words = ['prince', 'princess', 'man', 'woman']
away_embs = [emb[w] for w in away_words]
for i in range(len(away_words)):
    away_embs[i] = reduce(lambda a, b: b | a, away_embs[:i+1])

This is what away_embs now looks like:
[Emb[prince],
 Emb[(princess | prince)],
 Emb[(man | ((princess | prince) | prince))],
 Emb[(woman | ((man | ((princess | prince) | prince)) | ((princess | prince) | prince)))]]

These are all orthogonal vectors now that I need to project away from. This is now easy;
new_set = EmbeddingSet(self.embeddings.copy())
for e in orth_away:
    new_set = new_set | e

I'm happy that I've been able to re-use the notation to this extend but, again, I should now add some tests and see if I can confirm that we're still numerically sound.

@mkaze are you against merging this as is? I can still add some extra tests for the current implementation but I'd prefer to delay the QR implementation until I've found a nice use-case that allows us to test the numerical aspects.

@koaning I was just looking at it. Are you sure the implementation logic is correct?! It doesn't look like so to me! Besides, the test you have added has two problems:

It doesn't actually test the method for the added feature (i.e. the case where the second operand is an EmbeddingSet).
It doesn't check and validate that the logic is actually correct, i.e. whether the resulting embeddigns are orthogonal to the given embeddings (the second operand).

I've now added a test that checks for orthogonality.

from whatlies.language import SpacyLanguage

lang = SpacyLanguage('en_core_web_md')
embset1 = lang[['blue', 'red', 'green', 'dog']]
embset2 = lang[['color', 'cat', 'meet', 'air']]
x = embset1 | embset2

for e1 in x:
    for e2 in embset2:
        print(e1.orig, e2.name, e1.vector @ e2.vector)

# Output:
blue color -1.0015886
blue cat -1.1149356
blue meet -0.1489037
blue air -4.491012e-07
red color -0.87258
red cat -1.0220132
red meet -0.1383523
red air -3.3294782e-08
green color -1.8166131
green cat -1.427654
green meet -0.16886657
green air -1.5558908e-07
dog color -0.7157535
dog cat -0.29572958
dog meet -0.021123573
dog air 1.2514647e-08

Shouldn't all the values be close to zero, or have I made a mistake somewhere?

@mkaze I'd argue you're correct here! Well done!
I'll add this as a test example. Interesting to see that it is having no trouble with "air".
I am reminded of one thing though. Are you 100% sure that these vectors are linearly independant of eachother? spaCy sometimes (in an effort to save on memory) allocates the same vector to multiple tokens.

Interesting to see that it is having no trouble with the last projection "air".

That's basically because the air is the last embedding in the embeddingset, and therefore e in the final execution of this line new_set = new_set | e is actually air.

Are you 100% sure that these vectors are linearly independant of eachother?

I can confirm that none of the embeddings in embset1 is equal to those in embset2.

I've found a fix using QR.

Will go head and use that implementation now.

@koaning I was wondering, in this problem, if there is a guarantee that the resulting embeddings could produce the same vector space as the original ones.

@mkaze what do you mean with "produce same vector space"? The embeddings still have coordinates that are defined in 300 dimensions but after a projection I'd imagine there's less information in the vectors because we effectively project away information.

If there's a matrix with mat = [v1 v2 v3 v4] and the vectors inside are all linearly independant. Once we project away v4 then we get mat_new = [v1|v4, v2|v4, v3|v4, v4|v4].
This mat_new would have three linearly independant vectors where the original had 4.

@koaning The input and output vectors of Gram-Schmidt process generate the same vector space (or have the same linear span). This is an important property, otherwise there might be many ways to generate an orthogonal set of vectors from an initial set of vectors (e.g. always outputting the basis vectors of R^n).
Now my recent comment was regarding and pondering the fact that whether this property also holds (or must hold) in this problem as well, since this is a bit different problem than the problem of vector orthogonalization.

Given an orthogonal set embset_away then currently our embset | embset_away seems like a 1-1 mapping. What I do not know for 100% sure is if our projections are "minimum distance".
I'm pretty sure that I'm currently solving this problem:

I don't know if this approach also solves this one:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Type infeference fails when assignment is separate from declaration

Repo case for both OTI and NTI:
(function() {
var xhr;
xhr = new XMLHttpRequest();
xhr.open("GET", "somefile", true);
xhr.addEventListener(
  'load',
  function() {
    var data = new Uint8Array(xhr.response); // xhr is unknown
    console.log(data);
  }
);
xhr.send();
})()

If the initial assignment is on the same line as the declaration, the type is correctly inferred.
http://closure-compiler-debugger.appspot.com/#input0%3D(function()%2520%257B%250Avar%2520xhr%253B%250Axhr%2520%253D%2520new%2520XMLHttpRequest()%253B%250Axhr.open(%2522GET%2522%252C%2520%2522somefile%2522%252C%2520true)%253B%250Axhr.addEventListener(%250A%2520%2520'load'%252C%250A%2520%2520function()%2520%257B%2520%2520%2520%2520%250A%2520%2520%2520%2520var%2520data%2520%253D%2520new%2520Uint8Array(xhr.response)%253B%2520%252F%252F%2520xhr%2520is%2520unknown%250A%2520%2520%2520%2520console.log(data)%253B%250A%2520%2520%257D%250A)%253B%250Axhr.send()%253B%250A%257D)()%26input1%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3D1%26CHECK_CONSTANTS%3D1%26CHECK_DEPRECATED%3D1%26CHECK_ES5_STRICT%3D1%26CHECK_GLOBAL_NAMES%3D1%26CHECK_GLOBAL_THIS%3D1%26CHECK_SUSPICIOUS_CODE%3D1%26CHECK_SYMBOLS%3D1%26CHECK_TYPES%3D1%26CHECK_TYPES_NEW_INFERENCE%3D1%26CHECK_UNREACHABLE_CODE%3D1%26ENABLE_ALL_DIAGNOSTIC_GROUPS%3D1%26LANG_IN_IS_ES6%3D1%26MISSING_PROPERTIES%3D1%26PRESERVE_TYPE_ANNOTATIONS%3D1%26PRETTY_PRINT%3D1%26TRANSPILE%3D1

This is WAI for both OTI and NTI. If you look at the AST, xhr is of type XMLHttpRequest. The unknown type is on xhr.response, which is because the externs file is missing that property: https://github.com/google/closure-compiler/blob/b85923365aa8571db47ac09a27c1adddb0d299a2/externs/browser/w3c_xml.js#L295.

FWIW, even when you run NTI, the warning that you see is from OTI, because it runs after NTI. Normally OTI warnings are silenced, but there are a few that slip through the cracks, which I'm planning to fix.
NTI doesn't support reportUnknownTypes yet. I'll add support for it soon-ish.

Ahh that makes sense.


go: do not replace path to zoneinfo.zip

Prepend the nix path to the zoneinfo.zip file and keep the original alternatives
to allow go programs built using nix to run on non nix servers.
see https://github.com/NixOS/nixpkgs/issues/54603
Motivation for this change
Fixes: #54603
Allow Go programs built using nix to run on servers that don't have nix
Things done
I am very new to nix and could not figure out how to test this branch locally, reading
https://nixos.org/nixpkgs/manual/#chap-submitting-changes
I don't know what to replace this like with:
nix-env -i pkg-name -f <path to your local nixpkgs folder>

$ nix-env -i go -f /nix/store

[...] many warning similar to:
warning: name collision in input Nix expressions, skipping '/nix/store/mcgh4v55zwfp6f1x4b4zrdp6lrzki475-user-environment/nixpkgs'
[...] and finally:
error: cannot auto-call a function that has an argument without a default value ('derivations')

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Notify maintainers
cc @veprbl

The -f parameter should point to the git repository you used to make the pull request from:
$ git clone https://github.com/fmpwizard/nixpkgs
$ cd nixpkgs
$nixpkgs> git checkout issue_54603
$nixpkgs> nix-env -i go -f .

@GrahamcOfBorg build go

The same thing is happening with the mime types. I suggest fixing that as well if we want full support outside of Nix.
Our side: https://github.com/NixOS/nixpkgs/blob/5a0be78562c7de3daa450ee2c4698842e8ff7f8c/pkgs/development/compilers/go/1.13.nix#L59-L61
Upstream code: https://github.com/golang/go/blob/da4d58587e0e4028ea384580053c3c455127e446/src/mime/type_unix.go#L19-L23

@kalbasit great idea, I added a new commit. I tried to test this locally by running
nix-env -i go -f .

(at the root of this repo)
but I get this error:
--- FAIL: TestChown (0.00s)
        os_unix_test.go:51: gid: 100
        os_unix_test.go:63: groups:  [65534 100]
        os_unix_test.go:66: chown /tmp/_Go_TestChown141509686 -1 65534: chown /tmp/_Go_TestChown141509686: invalid argument
FAIL

I'm on Fedora 30 5.3.14-200.fc30.x86_64
Thanks!

it works locally for me. Can you please fix the commit, it should go: do not replace path to mime.types. It must start with go:  (see CONTRIBUTING.md) and the rest is for consistency. Please also update the title of the PR to reflect the change.
Once that's done, I'll submit it for build by ofborg and test locally on Linux/Mac.

@kalbasit thanks, I updated the commit message and the PR title

@GrahamcOfBorg build go pet jx


Compile issue when using Anna

Hello, I have encountered an issue when using Anna (Sorry for my careless of closing the old issue #24 ):
anna/build/libanna-proto.a(anna.pb.cc.o): relocation R_X86_64_PC32 against symbol `_KeyTuple_default_instance_' can not be used when making a shared object; recompile with -fPIC

How can I recompile Anna libs with -fPIC?
I add  -fPIC in the CMakefile but do not work:
IF(${CMAKE_CXX_COMPILER} STREQUAL "/usr/bin/g++")
  SET(CMAKE_CXX_FLAGS_COMMON
          "-std=c++11 -pthread -fPIC")
ENDIF()

SET(CMAKE_CXX_FLAGS_DEBUG
    "${CMAKE_CXX_FLAGS_DEBUG} \
    ${CMAKE_CXX_FLAGS_COMMON} \
    -g -O0 -fprofile-arcs -ftest-coverage")

SET(CMAKE_CXX_FLAGS_RELEASE
    "${CMAKE_CXX_FLAGS_RELEASE} \
    ${CMAKE_CXX_FLAGS_COMMON} \
    -O3")

Update:
It (the "-fPIC" issue) can be solved via manually modifying the file build/CMakeFiles/anna-proto.dir/flags.make and insert "-fPIC". How to generate it (via "Unix Makefiles" Generator, CMake Version 3.14) with "-fPIC" automatically?
Update: adding flags to CMAKE_CXX_FLAGS solves the issue.
IF(${CMAKE_CXX_COMPILER} STREQUAL "/usr/bin/g++")
  SET(CMAKE_CXX_FLAGS_COMMON
          "-fPIC -std=c++11 -pthread")
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS_COMMON}")
ENDIF()

2>
Then, it comes another issue about using GPU (nvcc)
[ 14%] Building NVCC (Device) object CMakeFiles/cuda_compile_1.dir/layers/cuda_compile_1_generated_exp_layer.cu.o
[ 14%] Building NVCC (Device) object CMakeFiles/cuda_compile_1.dir/layers/cuda_compile_1_generated_filter_layer.cu.o

anna/common/include/lattices/core_lattices.hpp(164): error: the object has type qualifiers that are not compatible with the member function "MapLattice<K, V>::at"
            object type is: const MapLattice<K, V>

1 error detected in the compilation of "/tmp/tmpxft_0000502a_00000000-4_cudnn_conv_layer.cpp4.ii".
CMake Error at cuda_compile_1_generated_cudnn_conv_layer.cu.o.Release.cmake:275 (message):
  Error generating file
CMakeFiles/cuda_compile_1.dir/layers/./cuda_compile_1_generated_cudnn_conv_layer.cu.o

make[2]: *** Waiting for unfinished jobs....

You should not need to use -fPIC. What version of libprotobuf do you have installed?

Oh, it is right when I complie Anna itself.
But when I use Anna's libs in other projects, I uses ld to link libanna-proto.a and this error happens.  The solution is to recomplie libanna-proto.a with flag -fPIC. (set it into CMAKE_CXX_FLAGS).

Update: the GPU issus is solved.
The issue is The object has type qualifiers that are not compatible with the member function C++.
It is caused by calling non-const member function on a const object.
anna/common/include/lattices/core_lattices.hpp
V &at(K k) const { return this->element[k]; } // add const here

in CMakefile.txt, we add -fpermissive into CMAKE_CXX_FLAGS.
This will remove the issue.

Got it. Thanks @authwork. Do you think it is worth adding this flag to the standard compile toolchain?

It only provide the solution for some rare cases, e.g., our project under nvcc.
-fpermissive, in fact, turns some "Errors" to "Warns".
We can add a nvcc label on this issue.


FlowType not working with pixels? What am I missing?

As there are no examples available to download to compare with, I'm not quite sure what I'm missing.
It would be a good idea to have a folder with examples. There's not even a fiddle or a codepen of its usage on the docs...
Here's a reproduction of what I'm trying to do.
I can see the font-size inline attribute being applied to the parent, but it doesn't seem to have any effect on the child elements.
It seems it only works when applying em instead of px to the element i want to make resizable.
Nothing is mentioned in the docs about having to use em instead of pixels. So not sure if this is a must or not...
Here's the same version but working as expected when using em units instead.
I've seen some other demos which doesn't seem to be working either.
What am I missing?

You need to include FlowType.js in your JSFiddle.

@jdgraffam it is there. Take a look at the left panel under the External Resources section.

Sorry, duh. Try this: http://jsfiddle.net/b51h4wcc/
Don't declare font-size on the h2.

Then I assume this lines in the docs are not correct when dealing with px, right?
body {
   font-size: 18px;
}

h1,h2,h3,h4,h5,h6,p {
   line-height: 1.45;
}

h1 { font-size: 4em; }
h2 { font-size: 3em; }
h3 { etc...


Changes SpinBox for a TextField

🦟 Bug fix
Fixes #542
Summary
Changes the implementation of GzSpinBox from a SpinBox to a TextField for MacOS.
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Closing since https://github.com/gazebosim/gz-gui/issues/542 is no longer an issue.


Test: running DA in extension host

Test for #45129:
Please note: since we do not ship this feature in March there is no need to have this tested by more than one dev.

[ ] anyOS: @isidorn

Complexity: 3
Testing:

Checkout the "cleanupDA" branch and build
run VS Code from branch
verify that debugging works correctly for both values of the user setting debug.extensionHostDebugAdapter.
try this for the C++ or Python debug extension

I have verified that debugging works for our vscode smoke test express and for a simple hello world python app. For both values of debug.extensionHostDebugAdapter


Task - Find source - hyperlink to Citation by Source

The hyperlink to Citation by Source does not work

If I use this link from Navigate radial, link works properly.
If I use Navigate radial, click View, click Report, click Citation by source. The hyperlink is also wrong.

@proceps Find source is gone, this is in recent now?


"caffe.LayerParameter" has no field name "bn_param"

Hi,
I got a problem when I tested.
[libprotobuf ERROR google/protobuf/text_format.cc:245] Error parsing text-format caffe.NetParameter: 19:12: Message type "caffe.LayerParameter" has no field named "bn_param".
F1006 14:45:42.856966 15514 upgrade_proto.cpp:88] Check failed: ReadProtoFromTextFile(param_file, param) Failed to parse NetParameter file: models/ucf101/tsn_bn_inception_rgb_deploy.prototxt
*** Check failure stack trace: ***
Aborted (core dumped)
I fixed bn_param in caffe.prototxt to batch_norm_param.
but, I got a similar problem like ~~~has no field named "frozen"
Could you please help me?

 Message type "caffe.LayerParameter" has no field named "bn_param".
This indicates you are running with another installation of Caffe. Please check your environment settings.
Also, the BN layer in our Caffe is different from BatchNorm layer in the official Caffe. We use the full implementation of batch normalization with the affine transformation attached, while BatchNorm only has the normalization part.

Hi,
Got this error. Correct action caffe version is built in lib/caffe-action
frame folder analysis done
WARNING: Logging before InitGoogleLogging() is written to STDERR
W1013 20:00:39.671665  4650 _caffe.cpp:122] DEPRECATION WARNING - deprecated use of Python interface
W1013 20:00:39.671728  4650 _caffe.cpp:123] Use this instead (with the named "weights" parameter):
W1013 20:00:39.671738  4650 _caffe.cpp:125] Net('models/ucf101/tsn_bn_inception_rgb_deploy.prototxt', 1, weights='models/ucf101_split_1_tsn_rgb_reference_bn_inception.caffemodel')
[libprotobuf ERROR google/protobuf/text_format.cc:245] Error parsing text-format caffe.NetParameter: 19:12: Message type "caffe.LayerParameter" has no field named "bn_param".
F1013 20:00:39.673532  4650 upgrade_proto.cpp:88] Check failed: ReadProtoFromTextFile(param_file, param) Failed to parse NetParameter file: models/ucf101/tsn_bn_inception_rgb_deploy.prototxt
*** Check failure stack trace: ***
Aborted (core dumped)

caffe-action is already built in lib/caffe-action.. Still getting this error
frame folder analysis done
WARNING: Logging before InitGoogleLogging() is written to STDERR
W1013 20:20:22.125752 16455 _caffe.cpp:122] DEPRECATION WARNING - deprecated use of Python interface
W1013 20:20:22.125816 16455 _caffe.cpp:123] Use this instead (with the named "weights" parameter):
W1013 20:20:22.125823 16455 _caffe.cpp:125] Net('models/ucf101/tsn_bn_inception_rgb_deploy.prototxt', 1, weights='models/ucf101_split_1_tsn_rgb_reference_bn_inception.caffemodel')
[libprotobuf ERROR google/protobuf/text_format.cc:245] Error parsing text-format caffe.NetParameter: 19:12: Message type "caffe.LayerParameter" has no field named "bn_param".
F1013 20:20:22.127086 16455 upgrade_proto.cpp:88] Check failed: ReadProtoFromTextFile(param_file, param) Failed to parse NetParameter file: models/ucf101/tsn_bn_inception_rgb_deploy.prototxt
*** Check failure stack trace: ***
Aborted (core dumped)

@Aravinda89
You are not using the Caffe you built under caffe-action. See this message
DEPRECATION WARNING - deprecated use of Python interface

You may need to check your environment settings so that other installations do intervene.

@Aravinda89  how do you check and set your environment settings ?

@Aravinda89  how do you check and set your environment settings ?


Improve mobile design

As it is right now, our design looks slightly off on mobile. Let's rework the design from the ground up to make the design feel more at home on a small screen. It's probably a good idea to mock up your ideas on Figma before implementing them and ask the rest of the team for feedback. Good luck!

there currently is a mockup on the figma, so now we just need to implement them!
*note to self: we should divide this up into smaller tickets later


Labs 1465/bundler demo code patch

Modify demo env to Sepolia, and directly interact with pre-deployed accounts.
I've modified the NonStandardAccount.sol so  anyone can send tx to it.

This account is for demonstration of BANNED OPCODE and invalid Storage Slot, other stuffs added to the account are only distractions. Remove the import of BaseAccount and modify from account example in previous tasks. This helps the participants to focus on the diff between each task, instead of getting a completely different account with many added features all of a sudden.

Fixed all codes suggested by Nic, NonStandardAccount is now more simple and just inherits the IAccount interface. The deploy script is also fixed to only deploy SimpleAccontFactory & SimpleAccount using official sample.


Fix type for newParam

Coverage decreased (-1.6%) to 31.212% when pulling 83a46928be1dc5530a2aa31d6959c032d2efa391 on fcastilloes:fix-type into bd3d9bc2c18dc16624b5f56bc02cbcd975e31736 on kusanagi:master.


moment is not defined

While trying to use your plugin, I am getting an error saying moment is not defined. Any suggestions please?

Hi Abhishek,
Please check whether your node_modules or bower_modules contains moment folder depending of the method of installation. If not please try to re-install "moment". Or please check the version of moment in pre-installed in project and version being used in the datetimepicker.
Thanks and regards
Amit


Add hover shadow to curricula cards

The little red dot is my mouse cursor. There is no transition yet, and the little text saying "View more details" has been removed. It seemed to miss the mark UX-wise, but I still wanted to keep some "haptic" feedback for the user.

So I added a CSS rule to transition smoothly. Feel free to tweak it. I think making the shadows stand out a tiny bit more might help but I am not a UX/UI/Seeing with my eyes person.

@zacharyjarnagin Thanks so much for working on this. I made the transition time a little faster, and made the shadow larger. Let me know what you think!

Looks good to me!

@zacharyjarnagin Feel free to review it (approve / request changes / comment). When Jaedyn gives it the green light I'll merge.


Install and config translations

Description
Install and config:

~react-18next~
[x] Translations

Translations will not be automatically generated, we will rely on DeepL, google translate and ChatGPT, as decided in #25.
This is the list of languages that the project should have when setting this up:

[x] English (the default one)
[x] Spanish
[ ] Catalan
[x] Korean
[ ] Japanese

@ehdlg You can continue implementing the other 2 languages.
Some tests might be broken, and there are some other compilation errors that prevented the push without --no-verify, so I'd be great if you could address those things as well.


Warn on ExceptionGroup subclass without derive

While there's probably some usecase which makes sense for this, at most someone could just implement like so:
class CustomEG(ExceptionGroup):
  def derive(self, exs):
    return ExceptionGroup(self.message, exs)

to get the original behavior (I think). From https://github.com/python-trio/trio/issues/3175

I was thinking that maybe this would fit better in flake8-bugbear due to being exceptiongroup-related and not necessarily async-specific, but given #302, #311, #301, #298 I think the best approach is creating a new 4xx series of rules for exceptiongroup-specific warnings.


🎇 Add in tutorial list

Description

Tutorial list added for user reference.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Tested on?

[x] Windows
[ ] Linux Ubuntu
[ ] Centos
[ ] Mac
[ ] Others  (State here -> xxx )

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged

The writing is overflowing.

The writing is overflowing.

@devenyantis Interesting, I will try to check out the bug

@devenyantis adjusted the container size, try to see if the overflowing problem still persist

It's not centered. Maybe a few pointer to help.

I think that is because you wrap the string by itself with this div. So, it will place the text according to the position in the box. Which is centered horizontal only.
Probably, few ways to solve it is use heading tag and apply css to center it OR very simple way is not to hard code the height of  the box.

@devenyantis Hi, I have made the height and width dynamic, please try it

It seems like you only change height to min-height. No change on my side still not centered vertically.

@devenyantis I added vertical align, see if it fix the issue


Guzzle abandoned

I cant install
symfony/event-dispatcher suggests installing symfony/dependency-injection ()
symfony/event-dispatcher suggests installing symfony/http-kernel ()
guzzle/guzzle suggests installing guzzlehttp/guzzle (Guzzle 5 has moved to a new package name. The package you have installed, Guzzle 3, is deprecated.)
aws/aws-sdk-php suggests installing doctrine/cache (Adds support for caching of credentials and responses)
aws/aws-sdk-php suggests installing ext-apc (Allows service description opcode caching, request and response caching, and credentials caching)
aws/aws-sdk-php suggests installing monolog/monolog (Adds support for logging HTTP requests and responses)
aws/aws-sdk-php suggests installing symfony/yaml (Eases the ability to write manifests for creating jobs in AWS Import/Export)
Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead.
Any idea ?

Those read like warnings to me, no error. What exactly is the issue?


feat(eslint-rules): add rule to prevent user from using array index as key in react

Using array index as a key is a bad practice that created bugs in my project (CIB) so I suggest this MR to prevent this to happen on all the future Theodo projects

@LeoAnesi can you provide an example in the commit description maybe? So that if one day someone wants to remove this option we can show an example of what kind of bug it helps to prevent. :)

@benja-M-1
Like this one? :)

Merci @LeoAnesi c'est cool !


Cannot run succesfully rc0 branch

After executing npm install and npm start on branch rc0, App doesn't do anything and prints following error into console:
Failed to load resource: the server responded with a status of 404 (Not Found)
localhost/:86 Error: Error: XHR error (404 Not Found) loading http://localhost:5555/node_modules/@angular/package.json(…) "Report this error at https://github.com/mgechev/angular2-seed/issues"

@sergidt - There is a discussion around this in the PR for rc0 https://github.com/mgechev/angular2-seed/pull/808
Currently incomplete as most of the maintainers were at ngconf this week.


Update list of contributors on readme.

We need to update the list of contributors in alphabetical order on the readme.

How about just pointing to this: https://github.com/GPflow/GPflow/graphs/contributors ?

Good suggestion - I'll do both so that the author list appears in text as well.


Triplet-loss on Market1501 Batch_size is ?

from the script when training with triplet loss , it doesn't give the explicit value of Batch_size , so the defalut batch_size of 256 is used ( I'm not quite sure) ? But in the paper the number is 18 ? Maybe it's the reason?

Thank you very much for the suggestion! The default setting is 256 batch size on 4 GPUs. So that each GPU has a mini-batch of 64 images, which belongs to 16 identities each having 4 instances (--num-instances 4). It is similar to the paper's setting.
I actually have tried using exactly the same setting with the paper (one GPU, 18 identities x 4 instances/id). The result is similar to the above default setting. Maybe I've missed something critical and need to wait for the authors' code.

Thanks! I will do some experiments too.


v0.7.1 tag doesn't deploy ReferenceGrant CRD via Kustomize

What happened:
When you download the v0.7.1 standard release yaml and extract just the CRD resource, there are 4 of them:
yq ea 'select(.kind == "CustomResourceDefinition") | .metadata.name' ~/Downloads/gateway-api-standard-install-v0.7.1.yaml
gatewayclasses.gateway.networking.k8s.io
---
gateways.gateway.networking.k8s.io
---
httproutes.gateway.networking.k8s.io
---
referencegrants.gateway.networking.k8s.io

However when you run the following command it only returns 3 resources:
kubectl kustomize "github.com/kubernetes-sigs/gateway-api/config/crd?ref=v0.7.1" | yq ea '.metadata.name' -
gatewayclasses.gateway.networking.k8s.io
---
gateways.gateway.networking.k8s.io
---
httproutes.gateway.networking.k8s.io

The issue is that the kustomization file here does not include that resource, only the 3 other CRDs.
Note that release-0.7 branch is up to date with the relevant line added.
The issue is that some other provided reference the git branch directly in their documentation with kustomize such as in Openshift ServiceMesh here. Note that yes they suggest v0.4.0 however I wanted to apply the latest.
What you expected to happen:
I expected both the release and then tag would have the same behaviour. I think this commit just needs ported to the v0.7.1 tag? or a new v0.7.2 release might be needed?
How to reproduce it (as minimally and precisely as possible):
Not working
kubectl kustomize "github.com/kubernetes-sigs/gateway-api/config/crd?ref=v0.7.1" | yq ea '.metadata.name' -

Works:
curl https://github.com/kubernetes-sigs/gateway-api/releases/download/v0.7.1/standard-install.yaml -L -O
yq ea 'select(.kind == "CustomResourceDefinition") | .metadata.name' ./standard-install.yaml

Anything else we need to know?:
This could be fixed in the RedHat docs for Openshift, but it still feels inconsistent here.
Also, this also fixes it by using the release branch as the ref instead:
kubectl kustomize "github.com/kubernetes-sigs/gateway-api/config/crd?ref=release-0.7" | yq ea '.metadata.name' -

Also for reference, if people were following istio docs but tweaking version, they might also encounter this issue.

Thanks for reporting this @hawksight!
This was fixed by https://github.com/kubernetes-sigs/gateway-api/pull/2084 and will be released in v0.8.0 (including the existing RC1 release).


Settings->Notifications on mobile

@keybase/react-hackers
Screenshot:

The commits 418fbf58db86...8f56078983a8 introduce visual changes on linux. :mag_right: 2 changed

Changed: Notifications-Unsub_All (before) (after)

Changed: Notifications-Normal (before) (after)


Update README.md

// Declare a class which extends null
class Foo extends null {}
// -> [Function: Foo]

new Foo() instanceof null;
// > TypeError: function is not a function

Not a bug! Because it is feature:
console.dir(Object.getPrototypeOf(Foo.prototype)); // is null

if the class has no constructor the call from prototype chain. But in the parent has no constructor. Just in case, I’ll clarify that null is an object. Therefore, you can inherit from it (although in the world of the OOP for such terms would have beaten me).
So you can't call the null constructor.
If you change this code:
class Foo extends null {
    constructor() {
        console.log(111);
    }
}

You se the error:
ReferenceError: Must call super constructor in derived class before accessing 'this' or returning from derived constructor

And if add super:
class Foo extends null {
    constructor() {
        console.log(111);
        super();
    }
}

JS throw error:
TypeError: Super constructor null of Foo is not a constructor

This is my explanation based on my experience and understanding how the  JS works.

I think we should extends function is not a function section with this explanation.

Closed due to no activity. Feel free to reopen.


Remove duplicate code in server views

Currently the elements in the views directoy contain a lot of duplicate code. Moreover, quite some elements are imported that are (probably) once used but not anymore. These should be cleaned up and integrated into a simpler structure to prevent code duplication.

Yeah, project is over yadada. Not gonna happen anymore :sob:

Unfortunately this project is indeed discontinue, feel free to leave feedback on our other projects though!


Warn if pdf used does not have any text.

I was saving websites as pdf, and used them for doing question answering. However, I did not realize that the pdfs were saved as images of the website instead of text. Despite being a simple problem, it took me some time to figure out the issue.
This also causes an unhelpful error message to show up when I try to refresh sources:
Can't pickle local object 'Selectable.__init__.<locals>.<lambda>'

Suggestion:
Add a warning when a pdf used does not contain any text.
Make the error message more helpful.

Thanks!  Will take a look.

@gerhean Do you happen to have the CLI's full stack trace for that odd error?  By itself it's hard to know why it happened or where it came from.

@gerhean Also, curious if you tried the URL entry instead for websites, might work better.
Also, if you have a list  of urls, that can be uploaded as a file itself in the drop area.

I wasn't able to reproduce that issue, but I got another odd error:
Loaded 1 new files as sources to add to UserData
Loaded 1 sources for potentially adding to UserData
Existing db, potentially adding 1 sources from user_path=user_path/tmp
Found 1 new sources (1 have no hash in original source, so have to reprocess for migration to sources with hash)
Removing 1 duplicate files from db because ingesting those as new documents
Existing db, added 1 new sources from user_path=user_path/tmp
Detected new embedding, updating db: UserData
load INSTRUCTOR_Transformer
max_seq_length  512
Done updating db for new embedding: UserData
Number of requested results 1000 is greater than number of elements in index 5, updating n_results = 5
Detected new embedding, updating db: UserData
Done updating db for new embedding: UserData
  0%|                                                                                | 0/1 [00:00<?, ?it/s]Failed to ingest user_path/tmp/./Best Centres website.pdf due to Traceback (most recent call last):
  File "/home/me/repos_wsl/h2ogpt/gpt_langchain.py", line 1213, in path_to_doc1
    res = file_to_doc(file, base_path=None, verbose=verbose, fail_any_exception=fail_any_exception,
  File "/home/me/repos_wsl/h2ogpt/gpt_langchain.py", line 1151, in file_to_doc
    doc1 = chunk_sources(doc1, chunk=chunk, chunk_size=chunk_size)
  File "/home/me/repos_wsl/h2ogpt/gpt_langchain.py", line 2243, in chunk_sources
    splitter = RecursiveCharacterTextSplitter(chunk_size=chunk_size, chunk_overlap=0, keep_separator=keep_separator,
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/langchain/text_splitter.py", line 585, in __init__
    super().__init__(keep_separator=keep_separator, **kwargs)
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/langchain/text_splitter.py", line 76, in __init__
    if chunk_overlap > chunk_size:
TypeError: '>' not supported between instances of 'int' and 'Number'

I should also say that this is done on wsl2.

I was able to get the error again:
~/repos_wsl/h2ogpt$ python generate.py --base_model='llama' --prompt_type=wizard2 --score_model=None --langchain_mode='UserData' --user_path=user_path/tmp
Using Model llama
Prep: persist_directory=db_dir_UserData exists, user_path=user_path/tmp passed, adding any changed or new documents
load INSTRUCTOR_Transformer
max_seq_length  512
Detected new embedding, updating db: UserData
load INSTRUCTOR_Transformer
max_seq_length  512
Done updating db for new embedding: UserData
0it [00:00, ?it/s]huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
100%|█████████████████████████████████████████████████████████████████████████████████████| 2/2 [00:00<00:00,  3.53it/s]
0it [00:00, ?it/s]
Loaded 0 sources for potentially adding to UserData
ggml_init_cublas: found 1 CUDA devices:
  Device 0: NVIDIA GeForce RTX 4080
llama.cpp: loading model from nous-hermes-13b.ggmlv3.q4_K_M.bin
llama_model_load_internal: format     = ggjt v3 (latest)
llama_model_load_internal: n_vocab    = 32001
llama_model_load_internal: n_ctx      = 1792
llama_model_load_internal: n_embd     = 5120
llama_model_load_internal: n_mult     = 256
llama_model_load_internal: n_head     = 40
llama_model_load_internal: n_layer    = 40
llama_model_load_internal: n_rot      = 128
llama_model_load_internal: ftype      = 15 (mostly Q4_K - Medium)
llama_model_load_internal: n_ff       = 13824
llama_model_load_internal: model size = 13B
llama_model_load_internal: ggml ctx size =    0.09 MB
llama_model_load_internal: using CUDA for GPU acceleration
llama_model_load_internal: mem required  = 2135.99 MB (+ 1608.00 MB per state)
llama_model_load_internal: allocating batch_size x (640 kB + n_ctx x 160 B) = 460 MB VRAM for the scratch buffer
llama_model_load_internal: offloading 40 repeating layers to GPU
llama_model_load_internal: offloading non-repeating layers to GPU
llama_model_load_internal: offloading v cache to GPU
llama_model_load_internal: offloading k cache to GPU
llama_model_load_internal: offloaded 43/43 layers to GPU
llama_model_load_internal: total VRAM used: 9441 MB
llama_new_context_with_model: kv self size  = 1400.00 MB
AVX = 1 | AVX2 = 1 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 1 | SSE3 = 1 | VSX = 0 |
Model {'base_model': 'llama', 'tokenizer_base_model': '', 'lora_weights': '', 'inference_server': '', 'prompt_type': 'wizard2', 'prompt_dict': {'promptA': "Below is an instruction that describes a task. Write a response that appropriately completes the request. If you don't know the answer, say that you don't know.", 'promptB': "Below is an instruction that describes a task. Write a response that appropriately completes the request. If you don't know the answer, say that you don't know.", 'PreInstruct': '\n### Instruction:\n', 'PreInput': None, 'PreResponse': '\n### Response:\n', 'terminate_response': ['\n### Response:\n'], 'chat_sep': '\n', 'chat_turn_sep': '\n', 'humanstr': '\n### Instruction:\n', 'botstr': '\n### Response:\n', 'generates_leading_space': False}}
Running on local URL:  http://<IP_ADDRESS>:7860
Detected new embedding, updating db: UserData
Done updating db for new embedding: UserData
0it [00:00, ?it/s]huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
0it [00:00, ?it/s]
Traceback (most recent call last):
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/gradio/routes.py", line 437, in run_predict
    output = await app.get_blocks().process_api(
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/gradio/blocks.py", line 1352, in process_api
    result = await self.call_function(
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/gradio/blocks.py", line 1077, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/anyio/to_thread.py", line 33, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 877, in run_sync_in_worker_thread
    return await future
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 807, in run
    result = context.run(func, *args)
  File "/home/me/repos_wsl/h2ogpt/gradio_runner.py", line 2396, in update_and_get_source_files_given_langchain_mode
    db, num_new_sources, new_sources_metadata = make_db(use_openai_embedding=False,
  File "/home/me/repos_wsl/h2ogpt/gpt_langchain.py", line 1511, in make_db
    return _make_db(**langchain_kwargs)
  File "/home/me/repos_wsl/h2ogpt/gpt_langchain.py", line 1612, in _make_db
    sources1 = path_to_docs(user_path, n_jobs=n_jobs, chunk=chunk, chunk_size=chunk_size,
  File "/home/me/repos_wsl/h2ogpt/gpt_langchain.py", line 1328, in path_to_docs
    documents = ProgressParallel(n_jobs=n_jobs, verbose=10 if verbose else 0, backend='multiprocessing')(
  File "/home/me/repos_wsl/h2ogpt/utils.py", line 805, in __call__
    return Parallel.__call__(self, *args, **kwargs)
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/joblib/parallel.py", line 1944, in __call__
    return output if self.return_generator else list(output)
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/joblib/parallel.py", line 1587, in _get_outputs
    yield from self._retrieve()
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/joblib/parallel.py", line 1691, in _retrieve
    self._raise_error_fast()
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/joblib/parallel.py", line 1726, in _raise_error_fast
    error_job.get_result(self.timeout)
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/joblib/parallel.py", line 735, in get_result
    return self._return_or_raise()
  File "/home/me/miniconda3/envs/h2ogpt/lib/python3.10/site-packages/joblib/parallel.py", line 753, in _return_or_raise
    raise self._result
AttributeError: Can't pickle local object 'Selectable.__init__.<locals>.<lambda>'

Those are very odd errors.  Do they happen every time?
I googled each.
The int vs. Number is super odd.  What if you add change chunk_size to int(chunk_size) when passing into that RecursiveCharacterTextSplitter function?  I'm assuming it's WSL specific.
The pickle thing might be windows specific issue with joblib.  A work-around might be to rename ProgressParallel to just Parallel in gpt_langchain.py when used (not import, just where used twice inside the functions).
Let me know if that works, and we can make a PR to adjust for WSL.

Using this:
image-based-pdf-sample.pdf


Re-writing the sample.

Changing auth to usable auth piggybacking on gcloud credentials.
Providing succinct examples for listing, insterting, and deleting instances.
Following current convention of main() and run() functions.
Adding markers for direct inclusion into cloud docs.

I just put some comments

How about to put travis config and a simple tox configuration, just to check coding style?

Added travis and tox config and make sure everything is passing. @tmatsuo any other tweaks?

LGTM
I still have some questions, but you can merge.

@elibixby I don't have collaborator access to this repo. Can you merge?


Update POS render function to use createRoot

Background
Currently all of our teardown functionality does not work. For example, the return method from a useEffect does not work in UI Extensions for POS (and I think on the other surfaces it's also broken?).
Solution
This replaces the deprecated render call with the createRoot function, which returns a root which has a render function, and an unmount function. We are passing the unmount method into the Promise.resolve, which means that it can be used on the host side to properly unmount everything when POS unmounts the UIExtensionContainer.
🎩
You can tophat this on POS with the following POS Branch:  https://github.com/Shopify/pos-next-react-native/pull/42289

Pull this branch to your machine.
Run yarn build, and go to the build directory for ui-extensions-react, and find the esm/surfaces/point-of-sale/render.mjs file that gets generated. Copy the contents.
In a POS UI Extension running locally, paste the contents of that into the<EMAIL_ADDRESS>Run your UI Extension and implement a useEffect with a tear down function.
Inject your UI Extension into POS on the branch I specified at the top of this tophat section.
Using a webview debugging console, make sure your tear down is getting called!

Checklist

[x] I have :tophat:'d these changes
[ ] I have updated relevant documentation

@NathanJolly Testing this on main of POS without any changes as seen in my other draft PR seems to work just fine. However, I don't feel the need to squeeze this in for 2024-10. If anything breaks on POS because of something we didn't test, well it just doesn't feel worth the risk right now. But perhaps while I'm on intermission you guys can ship this once the 2024-10 cut as been made, and then we can implement the appropriate changes on POS.

@vividviolet Updated the PR to move the logic into a shared util function. I can update the admin UI Extension with another commit in this PR if you want, or we can wait until you guys are ready down the line?

Can you please add it for admin as well? I think we do want it for the upcoming Oct release. I'll test the PR for Admin.

Can you please add it for admin as well? I think we do want it for the upcoming Oct release. I'll test the PR for Admin.

done
@vividviolet

@olavoasantos @vividviolet I've been gone for a month, did we make any decisions on the useEffect cleanup? Have we shipped anything yet? If not, we might have to settle with this approach for now, at least for POS, since we have some merchant/partners who have been nagging us about this for quite some time.

@js-goupil No decision has been made yet unfortunately. I'm leaning toward the simplicity of the clean up function instead of adding an event listener. @jakearchibald any opinions? We discussed this recently.