Spyder crashes after I upgraded to 3.2.0 because of OpenGL issues

I just upgraded Spyder to 3.2.0 (Python 3), and it stopped working. Specifically, when I tried launching it at a terminal with spyder, I got the following message:
WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed.
Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::SwapBehavior(DefaultSwapBehavior), swapInterval 1, profile  QSurfaceFormat::OpenGLContextProfile(NoProfile))
Aborted (core dumped)

It seems like a problem stemming from OpenGL? I tried making a fresh virtualenv and just installed spyder and pyqt5, and it still doesn't work...
However, the same works in Python 2.
What steps will reproduce the problem?

mkvirtualenv --python=/usr/bin/python3 testenv
pip install pyqt5 spyder
spyder

Versions and main components

Spyder Version: 3.2.0
Python Version: 3.5.2
Qt Version: 5.9.1
PyQt Version: 5.9
Operating system: Ubuntu 16.04 LTS

Please post the output of pip freeze when run in your virtualenv.

@ccordoba12 Thanks for the quick response.
Here's the result of pip freeze:
alabaster==0.7.10
astroid==1.5.3
Babel==2.4.0
bleach==2.0.0
certifi==2017.4.17
chardet==3.0.4
decorator==4.1.2
docutils==0.13.1
entrypoints==0.2.3
html5lib==0.999999999
idna==2.5
imagesize==0.7.1
ipykernel==4.6.1
ipython==6.1.0
ipython-genutils==0.2.0
isort==4.2.15
jedi==0.10.2
Jinja2==2.9.6
jsonschema==2.6.0
jupyter-client==5.1.0
jupyter-core==4.3.0
lazy-object-proxy==1.3.1
MarkupSafe==1.0
mccabe==0.6.1
mistune==0.7.4
nbconvert==5.2.1
nbformat==4.3.0
numpydoc==0.7.0
pandocfilters==1.4.1
pexpect==4.2.1
pickleshare==0.7.4
pkg-resources==0.0.0
prompt-toolkit==1.0.14
psutil==5.2.2
ptyprocess==0.5.2
pycodestyle==2.3.1
pyflakes==1.5.0
Pygments==2.2.0
pylint==1.7.2
PyOpenGL==3.1.0
PyQt5==5.9
python-dateutil==2.6.1
pytz==2017.2
pyzmq==16.0.2
QtAwesome==0.4.4
qtconsole==4.3.0
QtPy==1.2.1
requests==2.18.2
rope==0.10.5
simplegeneric==0.8.1
sip==4.19.3
six==1.10.0
snowballstemmer==1.2.1
Sphinx==1.6.3
sphinxcontrib-websupport==1.0.1
spyder==3.2.0
testpath==0.3.1
tornado==4.5.1
traitlets==4.3.2
urllib3==1.22
wcwidth==0.1.7
webencodings==0.5.1
wrapt==1.10.10

@kuo000 it might be something related to PyQt5==5.9

This is bug in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1590737
so I'm sorry, but there's nothing we can about it in our side.

You can find a possible solution here:
https://forum.qt.io/topic/74998/failed-to-create-opengl-context-for-format-qsurfaceformat-in-qt-5-6-0
but I really don't know what's meant for it.

@ccordoba12 Understood.
Thanks for taking the time to investigate this!

@jaxankey, it looks like a bug with the Nvidia drivers, so you should switch to use your Intel card instead.

No idea how you know that, but thank you! I changed from nvidia-390.59 to nvidia-396.24 in Mint's driver manager, and it works now.
Strange that it suddenly happened like this, but glad it's fixed!
Thanks again,
Jack

No idea how you know that, but thank you!

Well, it was reported in the Ubuntu bug I linked above :-)

@ccordoba12 I have the same pb.
Which version of spyder can I downgrade to, to make spyder work back again ?

@ccordoba12 I also this error before the Failed to create OpenGL context message :
AttributeError: '_ModuleMock' object has no attribute 'PLUGIN_CLASS'
Any idea ?

@sebma https://github.com/spyder-ide/spyder/issues/7415

@luolitao Hi, can please reopen because mine is not solved, here is what I did :
conda update qt pyqt spyder and I still get :
$ spyder &
[1] 31885
$
 WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed.
Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::SwapBehavior(DefaultSwapBehavior), swapInterval 1, profile  QSurfaceFormat::OpenGLContextProfile(NoProfile))

[1]+  Aborted                 (core dumped) spyder

@sebma, there's nothing we can do about this in Spyder because it's a problem with your graphic card drivers.
So please update them or use your Intel card instead of your Nvidia one, and try again.

As For Me, i just
conda install pyqt=4
and then conda install tensorflow-gpu (something you need, which will install pyqt5 automaticly)
thing goes well now, maybe it just because i miss something when i install spyder

@Magicwangs Thanks a ton! It worked! :)


Can Deepspeed be used?

Hi,I'm very sorry to disturb you.
Due to the high hardware requirements involved in the project, can distributed tools such as DeepSpeed be used for training？
Can I achieve distributed training by directly using deepspeed in llama_operor.cy and base_1lama_operator. py as news encoders for large models?
Will it affect other parts of the project？

Sorry, I have never tested it before, but our project only supports the training on a single GPU now.


New Documentations for this API

Need to make Documentations for this API.
Either using Normal HTML or Use any Documentation Library.

Would swagger UI work?

@phoenix1796
Sure!

Is there any progress? @phoenix1796

Can I be assigned this?

Hi, apologies for the delayed response, I've mapped out the basic API endpoints and am in the middle of mapping them down.

Sure
Regards
Piyush Mehta
http://piyushmehta.com
https://github.com/piyush97
https://linkedin.com/in/piyush24
On 9 Oct 2018, 1:43 PM +0530, Amarnath Karthi<EMAIL_ADDRESS>wrote:

Can I be assigned this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The earlier the better
Regards
Piyush Mehta
http://piyushmehta.com
https://github.com/piyush97
https://linkedin.com/in/piyush24
On 9 Oct 2018, 1:44 PM +0530, Abhishek Chopra<EMAIL_ADDRESS>wrote:

Hi, apologies for the delayed response, I've mapped out the basic API endpoints and am in the middle of mapping them down.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix failing safety

https://nvd.nist.gov/vuln/detail/CVE-2022-42969 landed recently and there's no fix in py (which is maintenance mode). From my analysis, that CVE cannot hurt us (famous last words), so we'll ignore the vuln for now.

@mattbowen-usds - also it seems that the map is loading nicely!
https://screeningtool.geoplatform.gov/en?flags=stage_hash=2114/4d9a8a574963aea16429e666d72450b57184076b#3/33.47/-97.5
This is the latest staging link.
I'm investigating why there are so many comments labeled "** Map Deployed! **", I'm guessing one for every failure? Seems like it shoudn't have deployed the map if it failed. 🤔

@vim-usds that is new! and i don't understand either!

@vim-usds my best guess as to why we got so many deploys was I  was pushing commits pretty quickly, and so some of the backend runs could have ended up still running; they wouldn't have had much reason to fail on their own, if the network didn't let them down, and maybe github just failed to kill them since I kept pushing new commits.


Fix md list in docstring

Lack of indentation broke markdown bullet list in the docstring for servedocs()

thanks!


Add PauliList class

Summary
Add PauliList to replace PauliTable and StabilizerTable
Details and comments
This class functions as an optimized list of the new Pauli class (including phase).

[x] tests
[x] Improve documentation

@ShellyGarion Thank you very much for your review. The missing tests about the phase were fatal, and I forgot the TODO. I am thankful for your review helped me realize them.
I have fixed them in the PR: https://github.com/chriseclectic/qiskit-terra/pull/24

@mtreinish Thank you. I made a PR to add the release note. https://github.com/chriseclectic/qiskit-terra/pull/25
@chriseclectic Could you merge this PR if it's OK.

It looks like there is a conflict here now: https://dev.azure.com/qiskit-ci/qiskit-terra/_build/results?buildId=29265&view=logs&j=377f2c8d-8b6f-583f-e152-2ff025e2543a&t=28b3ff0d-9e76-5e94-89e9-eed7321a383e&l=12999 probably after #6442 merged

OK. I'll fix this soon.

Thank you. I think this PR fixes the error on CI. (I've tested on my local and it passed.)
https://github.com/chriseclectic/qiskit-terra/pull/26


Update LLMCaller.js to Preview URL and v1beta2 endpoint

Problem: PaLM API URL and endpoint was out of date as of June 17th 2023.
Fix: Updated PALM URL and API endpoints to generativelanguage.googleapis.com and v1beta2 as per https://developers.generativeai.google/guide/palm_api_overview

Not my directory, but this is clearly correct.
Thanks.


Convert JSON Data to HTML passes with incomplete sollution

Challenge Waypoint: Convert JSON Data to HTML has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0.
Steps to repro:

Go to http://www.freecodecamp.com/challenges/waypoint-convert-json-data-to-html
paste the below snippet in the solving section the following code
Click CTRL+ENTER

        json.forEach(function(val){
          var key = Object.keys(val);
          console.log(JSON.stringify(key));
        });

Expected: test should fail
Actual: test passes
From what I see, the test passes even with syntax problems...
My code:

Cat Photo Finder

      The message will go here

      <button id = "getMessage" class = "btn btn-primary">
        Get Message
      </button>

I thought FCC only supported Chrome?

Then, let's loop through our JSON, adding more HTML to that variable. When the loop is finished, we'll render it.

I think your test should pass, but only if the returned data would be passed in the html var.
I tested your code a bit more, to see how much i could reduce. And apperently i only need
// Only change code below this line.
json.forEach
// Only change code above this line.

to pass the test. This assert should be altered to check against the returned value.
Altho the goal of this waypoint just seems to be a copy/paste one. Maybe we should alter it a little bit. To actually make it a challenge thats worthwhile completing.
@benschac FCC goal is to support as many browsers as possible, certainly the mainstream ones: Chrome, FF, Safari, Edge

Confirmed.  The issue is that we don't have the infrastructure in place yet to properly test asynchronous events.  At this time we're basically just checking the editor for certain strings.
All of the jQuery lessons need better, more comprehensive tests.

How can I start to work on this? Are we waiting for the infrastructure? Or is the solution would be building it?

Does anybody work on this issue? Can i work on it?

@chiptus @yzhbankov I think we're still waiting on the infrastructure to test async actions. The most you can do at this point, as pointed out above, is to just check they are using some code in the editor. However, there are many variants of implementing the code so trying to regex all answers might be difficult.
Also, note that this challenge has been changed in the staging branch. You can see the changes here on the beta site.


Feature: customize pages' path from config

Customize pages' path (in a section) from the configuration.
ie:
paths:
  - section: Blog
    path: :section/:year/:month/:day/:slug

Available placeholders:

:year
:month
:day
:section
:slug

Trying to fix #813.


new users should automatically be added to the 'All Users' group

via Hubstaff
User: Sabir Hassan
Project: server - https://app.hubstaff.com/projects/2310881
Date Range: 02/03/23 - 02/03/23
Work session total: 0:34:53
Billable: Yes
Grand total: 3:20:54


Does Fused Multi-head Attention support self-defined attention-mask?

Branch/Tag/Commit
main
Docker Image Version
nvcr.io/nvidia/pytorch:21.04-py3
GPU name
3090
CUDA Driver
525.89.02
Reproduced Steps
Bert Model with self defined attention-mask;
modify the input parameters in the FusedAttentionLayer.cu as following line, but the final result dosn't change.
dispatcher_fp16->run(qkv_buf_, attention_mask, padding_offset, attn_workspace_, qkv_buf_2_, stream_);

does UnFusedAttentionLayer's performance is much slower than FusedAttentionLayer?


DOC: Pull Request Template Creation

What's wrong with the existing documentation
I am writing to express my interest in contributing to your repository by creating a pull request template.
I believe that having a standardized template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review and merge pull requests.
Could you please assign me the issue under gssoc24? I am excited about the opportunity to contribute to your project and help improve the workflow for all contributors.
Add ScreenShots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@PradnyaGaitonde, could you please send me the template via screenshot?

@mdazfar2

@PradnyaGaitonde as of now, we think we don't need this, will let you know in future, if there is need


Swaps/trading infos

Hello,
1>> i think it's good idea to add some infos about trading/swaps volume ^^
2>> i guess this is crazy idea but i like it add dico calendar/liste to hyperdex should be perfect ^^'
regards

@ip-config Friendly ping :)


Typo in tinyurl link to spreadsheet

The offending line is linked here
https://github.com/RDorville/digfab/blame/64802c4b747c1343457669fb0be046cde78ddb03/examples/ea_camp_2021_03_29.md#L49
The broken link is https://tinyurl/ea210329
This is probably the correct link? https://tinyurl.com/ea210329

Honestly, I prefer full links (https://docs.google.com/spreadsheets/d/16JHsFF9a6SU_tu8fffEiCRyk0ALl2xEb4C_ZrWskUW8/edit) compared to tinyurl links.


[BUG] Cramming does not review every card; it buries siblings, which does not match the intended functionality of cramming

Tried to cram a deck with multiple clozes on cards, and it buries all similar cards. This setting should be applied in normal reviews, but cramming should make it clear that the intent is to see every single card

Hi @nayyala
I couldn't reproduce this. For example (with "bury sibling cards" enabled)

When I cram this deck, I see the following:

After clicking easy...

After clicking easy...

Please detail the issue with screenshots and the precise sequence of GUI interactions.
Cheers
Ronny

@ronzulu My apologies you are correct! I think it applies to cards that haven't been started yet and don't have the special dates added.

Actually, looking at the code, I think the problem you raise can occur.
But only when skipping cards during the review. Is that possibly what you encountered?


ctypes.ArgumentError: argument 2: <class 'TypeError'>: Don't know how to convert parameter 2

I'm trying to check a certain pixel and see if it's color matches a certain RGB tone. This is the line that gives the error:
if pyautogui.pixelMatchesColor(hisLeft + 48, hisTop + 128, (0, 95, 0)) is True:

This is the error that prints out on the console:
Traceback (most recent call last):
File "C:\Users\User\PycharmProjects\Project\m.py", line 196, in
status()
File "C:\Users\User\PycharmProjects\Project\m.py", line 26, in status
buy()
File "C:\Users\User\PycharmProjects\Project\m.py", line 144, in buy
if pyautogui.pixelMatchesColor(hisLeft + 48, hisTop + 128, (0, 95, 0)) is True:
File "C:\Users\User\PycharmProjects\Project\venv\lib\site-packages\pyscreeze_init_.py", line 589, in pixelMatchesColor
pix = pixel(x, y)
File "C:\Users\User\PycharmProjects\Project\venv\lib\site-packages\pyscreeze_init_.py", line 608, in pixel
color = windll.gdi32.GetPixel(hdc, x, y)
ctypes.ArgumentError: argument 2: <class 'TypeError'>: Don't know how to convert parameter 2
I tried to look online, and I didn't find much on this error, and the only fix that I found didn't work. Does anyone know the problem?

I've encountered this error too
What I did which worked was to convert the arguments to int explicitly (although I am not sure why this is needed).
e.g.
return pyautogui.pixelMatchesColor(int(x), int(y), (214, 190, 0), tolerance=10)


Warning about switching to Kompose

Don't know how to phrase that correctly :-(
Can someone suggest better wording?

Thank you @cdrage, that looks much better.

LGTM!


[feature] adds 'binary install' option to override kubelet (and other) binaries

Allows you to specify URLs for binaries in order to replace the default (RPM installed) binaries for kubelet, kubeadm and kubectl with customized one.
This idea came about initially because Feng mentioned that we'd like to have the ability to do this to use a custom built modification of k/k binaries in order to provision a lab for IPv6.
It may find other uses as well for spinning up a cluster given customized builds of Kubernetes to later run other end-to-end tests of our own scenarios with our own Kubernetes builds, and... Maybe offload the building of Kubernetes from this repo to say, something more focused particularly on that task.
Fixes #81

Much appreciated on the eyeballs! ...Mergin'!


API to create PURL domain

There should be an API to create a domain.

[ ] To create a PURL, the domain it should be created in, must exist.
[ ] Creating a PURL is a separate action
[ ] Trying to create a PURL on a non-existent domain will fail

An alternative to an explicit endpoint would be automatic creation of a domain if a client tries to create a purl inside a non-existent domain. This would only be possible if there are no parameters to configure when creating domains.
The benefit of automatic domain creation would be that api consumers would not have to implement a setup logic which must be run one to create the domain, ensuring it exists. This is interesting to me because there are scenarios where persurl my be used by api consumers which create lot's of domains (hundreds - thousands).
On the other hand, an explicit endpoint to create a domain allows persurl to validate parameters which may be added in the future.

I think it is the better option to start with an explicit endpoint. If in the future no special parameters are added to domain creation, there is always the option to allow implicit domain creation when creating a PURL.
For now, explicit it is.

Closed by #15 and #22


feat: enable swarm-desktop with environment variable

Resolves https://github.com/ethersphere/js-team-zenhub/issues/135

How does this work? Is this picked up in all CI workflows?

How does this work? Is this picked up in all CI workflows?

Oh you are right. I tested this in a test repo but I guess I had something wrongly setup.  By default github actions don't load .env files. So our options are:

We use github action like simple-dotenv or dotenv
We manually provide this variable to the workflows.

Which one do you prefer

Would you keep .env file for local setup? If you want to build it locally because you are for example testing something.


Add ScreenshotTestRule to roboscreenshots

WHAT
Add ScreenshotTestRule to roboscreenshots.
WHY
In order to not force usage to have to extend a specific class.
HOW

Add ScreenshotTestRule;
Add convenience class ScreenShotBaseTest that can be used the same way that ScreenshotTest was being used;

Checklist :clipboard:

[x] Add explicit visibility modifier and explicit return types for public declarations
[x] Run spotless check
[x] Run tests
[x] Update metalava's signature text files

@yschimke TIOLI, proposing it for review before removing ScreenshotTest and updating all tests; changed few classes to test it, haven't checked the record functionality yet.

LGTM


Strange behavior with MAP command and actions deployed with concurrency limit greater than one.

In both cases the composition result is calculated correctly.
The disadvantage is that trying to enable concurrency to have lower latency, the execution time is penalized by:

conductor actions which are forced (for some reason) to wait for a timeout to expire;
cold starts introduced by a further call to the echo action.

I am also facing something similar, in case of fan-in pattern my autogenerated conductor action waits till the last 30 second of whatever timeout I set to actually be called. Did you face any similar issue?


AHN download fails if the full path /data/pointcloud/AHN4/as_downloaded/LAZ does not already exist

I only created the path /data/pointcloud/AHN4/as_downloaded (without the LAZ dir) and this resulted in all AHN files getting downloaded with the filename 'LAZ' and errors.

I added these mkdir commands  in a previous PR so this should solve the problem
https://github.com/3DBAG/3dbag-pipeline/blob/fc3c0ab0bd97ba8e72ff14062ce588291c0e2df5/packages/core/src/bag3d/core/assets/ahn/download.py#L150
https://github.com/3DBAG/3dbag-pipeline/blob/fc3c0ab0bd97ba8e72ff14062ce588291c0e2df5/packages/core/src/bag3d/core/assets/ahn/download.py#L206
https://github.com/3DBAG/3dbag-pipeline/blob/fc3c0ab0bd97ba8e72ff14062ce588291c0e2df5/packages/core/src/bag3d/core/assets/ahn/download.py#L263


How do I set default dates different

As I show in syntax, you are passing year, month and day. Hopefully it will set default from and to date.
How can I set fromDate different like before six months and toDate as current date.
Thank you.

I found new constructor for specify from and to date individually.
DatePickerDialog dpd = com.borax12.materialdaterangepicker.date.DatePickerDialog.newInstance(
                        AnalyticsFragment.this,
                        now.get(Calendar.YEAR),
                        now.get(Calendar.MONTH),
                        now.get(Calendar.DAY_OF_MONTH),
                        nowEnd.get(Calendar.YEAR),
                        nowEnd.get(Calendar.MONTH),
                        nowEnd.get(Calendar.DAY_OF_MONTH)
                );

Hope you will add in ReadMe


The default topic permission does not read from the configuration file, but directly   from the code.

Line 133 in PlainPermissionLoader.java does not read the variable values in the configuration file.
The code is:
byte ownedPerm = isGroup ? needCheckedAccess.getDefaultGroupPerm() :
needCheckedAccess.getDefaultTopicPerm();

Firstly,you should put forward a issue according to issue's template.


Update crypto 2019-10-04

Update crypto submodule:

ARMmbed/mbed-crypto#277: Improve speed of PBKDF2 by caching the digest state of the passphrase
ARMmbed/mbed-crypto#269: Add PSA API versioning
ARMmbed/mbed-crypto#278: Fix on target test issues
ARMmbed/mbed-crypto#286: Fix defgroup syntax for API version section
ARMmbed/mbed-crypto#75: ASN.1 tests without x509

Update error.c; this fixes check-generated-files breaking in the TLS testing on Mbed Crypto.
Uncomment a test case that was broken until ARMmbed/mbed-crypto#75 fixed it.

One DTLS test case failed on CI in one configuration, only on the head job and not on the merge job. I ran it on my machine and it passed. It looks like a DTLS packet got dropped, which our test framework doesn't protect against.


New UI on Angular

new user interface on angular + angular material

home page with sessions listing
direct connection, load dump file and load session file
spanner metadata database configuration option
main work area with three column layout

tree view for object navigation
separate pane for summary with filter
middle pane for object view and edit

separate instruction page

session management feature

Co-authored-by: sagar<EMAIL_ADDRESS>Co-authored-by: shellymathew98<EMAIL_ADDRESS>Co-authored-by: lyazii22<EMAIL_ADDRESS>Co-authored-by: pratikdhanavesearce<EMAIL_ADDRESS>

@shreyakhajanchi your comments will be addressed in the newly raised PR #287.
CC @bharadwaj-aditya
Will close this PR soon.

Hi @shreyakhajanchi @bharadwaj-aditya @Deep1998
Some of the comments addressed in the PR #287 and few are logged as issue. Hence closing this PR.


Add a license badge to README.md

Also, move the crates.io badge beyond the license badge to optimize the badge
row's utility as a status dashboard as discussed in #525.

Thanks for contributing! Unfortunately, I'm here to tell you there were the following style issues with your Pull Request:

Commit: 81e4965f69e24c44939dbf4f2698d5143b54e03b
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Whoops.

Coverage remained the same at 88.78% when pulling 81e4965f69e24c44939dbf4f2698d5143b54e03b on ssokolow:patch-1 into 486a219bc88c5cc532a7d7a23d89f9999721f1bf on hyperium:master.

There. Sorry about that. My sleep cycle is somewhat disrupted and I forgot to consider how it subtly affects my memory and judgement.

Coverage remained the same at 88.78% when pulling 19d2530c3c411ee930ecd08dff7a19eaa95aa5ff on ssokolow:patch-1 into 486a219bc88c5cc532a7d7a23d89f9999721f1bf on hyperium:master.

Coverage remained the same at 88.78% when pulling 19d2530c3c411ee930ecd08dff7a19eaa95aa5ff on ssokolow:patch-1 into 486a219bc88c5cc532a7d7a23d89f9999721f1bf on hyperium:master.


Image component not clearing cache

🐛 Bug Report
Once image is set,  it will not changing second time. (cache is not clearing even when i get new image url)
Expected Behavior
Image should show latest url image.
Code Example
profile_picture = "http://<IP_ADDRESS>/amino/public/upload/profile/profile_img_12.jpeg";
<Image
    key={profile_picture}
   source={{ uri: profile_picture, cache: "reload" }}
   style={styles.ProFileImg}
 />

Environment
 React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: (4) x64 Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz
      Memory: 68.05 MB / 8.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 8.12.0 - /usr/local/bin/node
      Yarn: 1.12.3 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.4 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
      Android SDK:
        API Levels: 23, 25, 26, 27, 28
        Build Tools: 27.0.3, 28.0.0, 28.0.3
        System Images: android-27 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.3 AI-182.5<IP_ADDRESS>99772
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.0-alpha.8af6728 => 16.6.0-alpha.8af6728
      react-native: 0.57.4 => 0.57.4
    npmGlobalPackages:
      react-native-cli: 2.0.1

@sunilzalavadiya do you fix it? i have the same question


Vidstack layout is deformed in preview

Current Behavior:
Im creating a project using sveltekit and vidstack. The play looks good and ok with pnpm dev. But after I did pnpm build then pnpm preview, its layout was deformed same with using node ./build. Here is what it looks like on preview
WIDE screen

Mobile screen

I am just following the most simplest instruction in the documentation. Again this happened only on build but in dev its okay
Here is my pattern

Select Framework: Svelte
Select Bundler: None, also tried Sveltekit
Select Provider: Hls
Select Styling: Default Layout

npm i vidstack@next hls.js

Then follow steps as how it was given in the documentation.
Then using adapter-node i did
pnpm build

pnpm preview

Again the bug only be seen in build preview

I also tried and reproduce the bug to reproduce
Docs step I followed
My steps
pnpm create svelte@latest

npm i vidstack@next hls.js

I followed this steps
https://www.vidstack.io/docs/player/getting-started/installation/svelte?bundler=none&provider=hls&styling=default-layout
pnpm build
pnpm preview

Am also getting the same problem since today, was working well before

I'm testing it now and it's working as expected. Followed the exact same steps. It installed<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

By the way, there was a small mistake in our SvelteKit bundler option. The plugin order was incorrect. See the fix if you'd like to use it instead.

Thanks! I tested it on new setup of svelte project and it works good. I also want to mention that for some reason I need to remove purgeCss() to the actual project for vidstack to work properly. I also tried rearranging their position but the one the works for me is to disable it. I hope this helps.


fix: Same keybindings for creating horizontal and vertical panes

Resolves issue gpakosz /.tmux#550

Hello @OlaoluwaM 👋
I won't accept your PR.
Issue #550 is invalid. The bindings for horizontal and vertical pane split are different: - (dash) and _ (underscore).


ci: move spotless and api check to build step.

Guidelines
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce?

[ ] Bugfix (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)

Preparing a pull request for review
Ensure your change is properly formatted by running:
$ ./gradlew spotlessApply

Please correct any failures before requesting a review.

Thank you for your contribution, @MahmoudMabrok. But the reason of this is, I want to clarify the reason of the CI failures without going to see the details when the build failed.

Thanks for reply. I agree with you.
so we can run all as single job with multiple steps, so we reduce time for 2 extra [checkout, run gradle], also gradle tasks will be cached so lower time.

could you please check ? @skydoves

Please check @skydoves


Updating .rosinstall to use the release-latest of dependencies

Issue #, if available:
See comments here: https://github.com/aws-robotics/aws-robomaker-sample-application-cloudwatch/pull/30
tt: P26480778
Description of changes:
Updating .rosinstall to use the release-latest of dependencies
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Did you test this locally and/or in robomaker?


[5.3] [Function builders] Use one-way constraints for closure parameters.

Introduce one-way constraints for the parameters of closures to which a
function builder is being applied. This was an intended part of the
model when one-way constraints were introduced, but somehow got
missed. This should further break up large constraints systems for
faster solving, and most likely won't break much source code in
practice.
Fixes rdar://problem/64231116.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - fd296593c58cdba404204b717873bfe0f8ffe784

Build failed
Swift Test OS X Platform
Git Sha - fd296593c58cdba404204b717873bfe0f8ffe784

@swift-ci please test Linux

@swift-ci please test macOS


Add the possibility to show the dialog also for visitors outside the EU

This can be useful for performance purposes when the owner of the website knows the majority of its traffic comes from the EU: on a slow network, the request to freegeoip can take long to execute, and in the meanwhile the user can't view the dialog.

Hi,
What about something more explicit for the flag, like skipLocationCheck or something, what do you think?
For the second commit, is there something something wrong with the animation?
Thanks!

You're right: skipLocationCheck is way more clear than my previous proposal.
For the second commit, it was an edit that I wanted on my project, because the entry animation attracted too much attention by the users, and without it the website is the first thing they focus on.
My bad I forgot to create a dedicated branch for this PR, so my "personal" commit has been queued to the PR.
BTW I amended the first commit and rewrote my git history, so now the PR has only the skipLocationCheck commit.
Let me know if it's all ok ;)

Seems good :)
I will merge and push a new release soon


My friend can't join my world port

https://mclo.gs/zUar06s

The stack trace is vanilla Minecraft (and one Forge) code paths, suggesting that this has nothing to do with ExtendedCrafting.
The disclaimer at the bottom of the log is just to remind you that you're using our fork of ExtendedCrafting, not the original mod: if the issue is explicitly related to ExtendedCrafting then you should report that bug here rather than to the original mod's repository.


UnknownZodTypeError  with object with default value

When using a default value I'm getting the below error.
UnknownZodTypeError {
  message: 'Unknown zod object type, please specify `type` and other OpenAPI props using `ZodSchema.openapi`.',
  data: {
    currentSchema: {
      innerType: [ZodString],
      defaultValue: [Function (anonymous)],
      typeName: 'ZodDefault',
      openapi: [Object]
    },
    schemaName: 'Object'
  }
}

Problem code
registry.register("Object", z.string().openapi({ description: "object" }).default(""));

Hello @blade2005,
Thank you for using asteasolutions/zod-to-openapi and reporting your problem. Yes, default values are not currently handled. It would be a straight forward feature to implement. I'll add it to a new release tomorrow morning.
In the meantime you can provide a type by using  .openapi({ type: 'string' }) to avoid the overall error.

Added in the v1.2.0 release.


[backport] Canal readiness probe failed with statuscode 503 for k8s 1.15

[backport] rancher/rancher#23430

rancher/rancher:v2.2-head d3dfcff0

Created 1.15.5 cluster
Canal deployment correctly contains:

- name: USE_POD_CIDR
    value: "true"

CRD is present in cluster: networksets.crd.projectcalico.org
No failing readiness checks observed


Cannot handle messages from only one participant

If I were to quote messages from only one participant, then I get an internal server error when I run . On retrying (by clicking 'back'), the Who are you dropdown doesn't get an entry, hence cannot proceed.
Sample input:
[10/4 1:14 AM] Karan Luthra: I know it because i was part of the organizing team
[10/4 1:14 AM] Karan Luthra: Yeah
[10/4 1:14 AM] Karan Luthra: Take a day or two
Output:
500 Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

Just checked. Yes, you're right, it breaks when there's only one participant. Better look into it. Thanks!


Updated URL for download

It seems that DaNLP has updated their download URLs and it therefore also needs to be updated in here...

Actually it looks like the old URL is still working, and it's also the one that is mentioned in https://github.com/alexandrainst/danlp/blob/master/docs/docs/datasets.md
What makes you think we should use the new URL ?

I might have jumped to conclusions a bit too fast here...
I was working in Google Colab and got an error that it was unable to use the URL. I then forked the project, updated the URL, ran it locally and it worked. I therefore assumed that my URL update fixed the issue, however, I see now that it might rather be a Google Colab issue...
Still - this seems to be the official URL for downloading the dataset, and I think that it will be most beneficial to use. :-)

It looks like they're using these new urls for their new datasets. Maybe let's change to the new URL in case the old one stops working at one point. Thanks


[Bug] Updates to chapters still not working after 2.5.1 upgrade

Device information

Tachiyomi version: 2.5.1
Android phone & version: Pixel 2XL, Android 11

Steps to reproduce

upgrade to 2.5.1
it starts to update chapters, but never finishes.
the process hangs until you kill it. I waited for 35 minutes.

Expected behavior
it should update the chapters
Actual behavior
the update process never exits.
Other details
if you try to do an update after killing the hanging update, it will revert back to the 2.5.0 behavior of never starting the update.

Can confirm process hang during initial phases of chapter update and library-wide update (the phase when the notification hasn't shown any progress yet and just says "Neko"), but it eventually completes on my side.

@X9VoiD  does it eventually show the manga progress bar?
@jaredanson because you have this an another logout issue, are you able to actually read?  Can you open a manga through the webview and it work?

Yes the progress bar eventually shows up in the notification (that previously only shows "Neko" with cancel button, and during the moment that there's only "Neko", pressing any manga will hang the app until the progress bar shows up). The weird thing about it though is that it doesn't seem to be updated properly. The update process finishes faster than before as the changelog states but the notification only showed "some" mangas being updated and then suddenly it's done.
To clarify up some stuff:

Open Neko
Swipe down to update library
"Updating Library" toast shows up
An empty notification with "Neko" and "Cancel" button shows up

From this point on there's three branches I may take:

Press any manga
Neko hangs
(Pressing cancel doesn't do anything)
Neko's notification will eventually show a progress bar
Neko is responsive again

or

Press "Cancel" found in Neko's notification
Neko is responsive again

or

Wait until Neko's notification shows a progress bar
Neko won't hang anymore if we press any manga

@X9VoiD so the change moved the processing more async, doing so the manga title has to be sent after it was processed.  Nothing is being dropped but i wouldnt be surprised if when two manga complete update they both send the title to the notification and it immediately overwrites the other one.
Thank  you for the clarifications and it looks like library update will be my next big rewrite

@CarlosEsco yes i can read manga just fine. It seems to be unrelated to chapter update and log in/out issues

@CarlosEsco just as an update, i upgraded to 2.5.2 and the chapters are still behaving the same way for me where the update process never finishes

@jaredanson
In advanced settings enable log level extra
force close the app
do a library update
then when it gets stuck send the log file   located in the neko folder

fixed in 2.5.3


fix TypeError: Cannot read properties of null (reading 'parent') within isInCustomHookDef

Hello! I've discovered an issue with eslint-plugin-valtio in the following scenario:
type MyValue = any;
function MyFunction() {
  const id = useSnapshot(store) // normal usage of valtio snapshot
  const [value, setValue] = useState({});

  useQuery({
    queryKey: ['test'],
    queryFn: () => {
      setValue(prev) => {
        return {
          ...prevent,
          [id]: value as MyValue //breaks on this line
        }
      }
    },
  });

}

The error I'm receiving is:
TypeError: Cannot read properties of null (reading 'parent')
Occurred while linting MyComponent.tsx:91
Rule: "valtio/state-snapshot-rule"
    at isInCustomHookDef (MyProject/node_modules/eslint-plugin-valtio/index.js:238:60)
    at Identifier (MyProject/node_modules/eslint-plugin-valtio/index.js:346:92)

By checking if these nodes exist, I'm able to fix the issue. Thanks!

Don’t have my laptop so this is based off what i could read on the phone screen.

instead of returning false, we’d  like to add a check for if it’s in a function inside an object inside a custom hook

reasoning is that we might have further cases that might come up in the future and the plugin would return false for everything
if that makes sense, please make the changes accordingly if not, i’ll pick this up once i have fixed my work machine 😅


LUIS: Turning off active learning

Hi,
Is there as way to turn off active learning for LUIS? I couldn't find the specific Node.js reference for the same.
Any help would be appreciated.
Thanks!

can you please follow up with<EMAIL_ADDRESS>on this.

Thanks @cahann. Wrote to them.
I'm trying to recall something I came across in past. Isn't there a line of code in node.js BotBuilder script that stops LUIS from registering data that it doesn't recognize?
I'll keep digging the docs meanwhile...

@cahann is that the correct email address for Luis Support?

Hi @jaskiratr, I'm assuming you followed up with the luis team directly via email (yes, that's the right email address), so I'm closing this issue. Feel free to reopen if needed. Thanks!


OLS-716: Update lightspeed operator readme file

Description

Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

We can also mention that we can set the env var IMG for make deploy and make docker-build docker-push to build and deploy an image in another registry, such as our personal registry for debugging use.

/lgtm

/retest

/retest

/retest

/lgtm


Adding plugins/hooks to route paths

Hey, really amazing plugin. One question I have is how to integrate plugins with this since there's no inner module scope/context. For example, adding the fastify-bearer-auth plugin only for certain route paths. The way to do this normally would be:
// Authenticated
fastify.register((instance, opts, next) => {
  instance.register(bearerAuthPlugin, { keys })
  instance.get('/sensitive', (req, res) => res.send('hello'))
})
// Open access
fastify.register((instance, opts, next) => {
  instance.get('/login', (req, res) => res.send('hello'))
})

I see there is an opts.preHandler option which I can use, is this compatible with plugins so that I can just do IE:
POST.opts = {
  preHandler: bearerAuthPlugin
}

Hi
You can see the attached pull request
What I had in mind, is adding a preRegister function to the plugin opts, so you can register other plugins using the instance, so you can register them in a context
fastify.register(fastifyNow, {
    routeFolder: ...,
    preRegister: (instance) => {
        instance.register(bearerAuthPlugin, { keys })
    },
});

Just started it, and not sure when it will be done
If you can help, feel free to go over it, change it, add tests, so it will suite your and others needs

closing due to inactivity

closing due to inactivity


Automate Tern's release process

Describe the Feature
When a new or patched release is cut, the Tern maintainers follow the steps outlined here. This is time consuming and limits the frequency that releases can be made available. Ideally, we would automate this process.
Use Cases
Anytime we want to cut a release, having at least a portion of this process automated will save time and reduce errors.
Implementation Changes
Write a script that takes the release notes and other relevant files or information as inputs and cuts a release. It may not be possible to fully automate this, but we the script should at least prepare all the necessary material for the maintainers to cut a release faster than the fully manual process we have now.

Heya, looking at the different parts of the release process.
Could "Update direct dependencies and run tests" be replaced with dependabot?

Hi @rnjudge, @nishakm might of mentioned I have a software engineering student doing a uni placement at the moment.
He is starting to look at this issue. We spent a bit of time reviewing the release checklist and I would appreciate feedback on the following as an approach.

manage direct dependency updates separately to releases, using dependabot (runs tests automatically when the PR is raised)
prepare release PR

manually triggered GitHub workflow, which does the following steps
creates a release notes file, next.md with section headings and relevant git log output
copy requirements.txt to docs/releases/next-requirements.txt
creates next branch and PR

preparation of release notes

maintainer 1 completes release notes in the next PR branch
maintainer 2 reviews release notes, merges PR

create and publish release

manually trigger GitHub workflow, version specified when triggering release, which does the following steps
rename next.md and next-requirements.txt to include version, create release commit
build package
install locally built package and run smoke tests
build docker image
run locally built docker image and run smoke tests
create GitHub release (which also tags the commit)
create Tern vendor tar and upload to GitHub release
upload package to GitHub release
publish package to PyPI
publish docker image to Docker Hub

@ReconPangolin I'll try to review what you've done in your fork tomorrow to provide some feedback before raising a draft PR here.
Can you have a look at what I've put above? I put some more thought into the steps required across the whole process. You could start working on the create and publish release steps next.

Thanks, I'll finish up step 2 to copy requirements across and then get started on automatically building the release.

@coderpatros and @ReconPangolin, Thanks for taking this issue on! We have a release checklist: https://github.com/tern-tools/tern/blob/main/docs/releases/release_checklist.md. We have started a list of functional tests here: https://github.com/tern-tools/tern/blob/main/ci/release_tests.py. It should be enough to get you started, but if not, feel free to comment on this issue!
One issue we've found with dependabot is that it flags dependencies in the release freeze files located in the docs/releases folder. I don't think dependabot has the ability to work on just the top level requirements.txt file.
We use pip-tools to manage our dependencies. It's worked out pretty well! Details are in the release checklist.

Hi @nishakm, how are you executing the tests in release_tests.py?

@coderpatros The tests will be run with:
for t in tests:
    subprocess.check_output(t, shell=True)  # nosec

A lingering PR was just opened to make this change. Currently tests are run this way in ci/test_files_touched.py


Database access

Have a way in DDLite to easily query the database, work with samples from the database

#322


Monitoring of switch to Firefox mv3

As Firefox is switching to manifest version 3 (mv3) in a couple of months, we should keep an eye on if functionality is breaking, what we need to change, etc. I tend to think that the impact will be a bit more limited than Chrome's switch to mv3 as it is my understanding that Firefox intends to keep some of the deprecated APIs around. However, at the beginning of next year, when Chrome is making the switch, we should address this.
Currently, the timeline of Firefox's switch to mv3 and which APIs will be deprecated is unclear but will become more clear over the next couple of months. Here are some official resources:

Manifest v3 in Firefox: Recap & Next Steps
Manifest V3 Firefox Developer Preview — how to get involved

Please everyone keep this on the radar. We do not want to wake up one day and everything is broken (and we can't even update anymore on the Firefox Store).

We already moved to MV3 in Chrome (protection mode only). So, there is nothing more to be done there. But the question is to which extent is MV3 still relevant for our Firefox version. Ideally, if we still have protection mode in Firefox, then the protection mode extension (for Chrome and Firefox) should have the same code. @sophieeng and @OliverWang13 will look into this.
@Jocelyn0830 and @katehausladen, if you could look into how the MV3 changes affect the analysis mode crawler (Firefox only). @Jocelyn0830 opens an issue in the crawler repo to discuss MV3 over there.
Here is the last from Firefox.

In preparation of the new release, @OliverWang13 and i have been looking to the Firefox MV3 status. Because analysis mode has been removed from the OptMeowt extension, we are left with two protection modes: one for Chrome and one for Firefox. The main difference between the two protection modes is which Manifest version they're built for. The Chrome version has been changed to MV3, which involves new service workers and different APIs.
Because we are unsure if Firefox MV3 will have the same changes that Chrome had when migrating between versions, we don't want to make Firefox and Chrome the same. We prefer leaving Firefox in MV2 until a list of changes for FF MV3 comes out and we can compare FF MV3 and Chrome MV3. We will reevaluate from there. In the future, it would be nice to have one protection file that works for Chrome and Firefox, but we don't know if that's a possiblity.

@sophieeng will update on the current Firefox MV3 status.

Firefox has not had any timeline changes to the switch from MV2 to MV3. Currently, both versions are supported on Firefox but developers cannot create an extension that supports both, so they must be able to distribute both types. Firefox began supporting MV3 on November 21, 2022 and has stated they will look for an appropriate timeline to depreciate MV2 near the end of 2023. While we keep monitoring the situation, it would be especially good to check then.
Also, I do not see it mentioned but Google has put their own MV3 timeline under review. This means that switching to MV3 has been postponed.
In accordance with earlier posts in this issue, we will continue to wait for more clarity on what Firefox's MV3 will require before we make changes to our extension.

@sophieeng, can you check and report on the status of MV3?

Manifest v3 signing available November 21 on Firefox Nightly
Resuming the transition to Manifest V3

The questions are (for both Firefox and Chrome):

Do we need to do anything now?
Should we prepare anything for later?

Chromium:
Chrome has been making changes to MV3 to close gaps in functionality. We do not need to do anything as we were able to fully migrate to MV3 without losing functionality because it was unsupported in MV3. MV2 will be phased out in June of 2024 at the minimum. We do not need to prepare anything else for Chrome as we are fully migrated.
Firefox:
Firefox is supporting MV3 and allowing MV3 version extensions starting the Mozilla store on November 21st. Here is their MV3 documentation. As of now, MV2 is still supported for the foreseeable future. At the end of 2023, Firefox will decide the timeline to depreciate MV2.
To do now: Start reading over MV3 documentation, and identify aspects that will be critical for our extension.
Prepare for later: Keep an eye on how the MV3 documentation as it may be modified over time. Come back to this issue at the end of the year to document the depreciation timeline

Thanks, @sophieeng!

To do now: ... Prepare for later

It would be great if you could take the lead and prepare a plan (with the help of @OliverWang13, as necessary) on the concrete changes that we need to make. Especially, we need to find out:

Do we need to make big architectural changes or just switch out APIs?
Which changes exactly on these different levels?
By when? In other words, when is a good time for making these changes? We do not want to do it when the MV3 changes are still in flux, but we also should not do it too late.

@katehausladen, is the crawler also affected by the change to MV3?

Plan going forward: I'll start comparing the Firefox and Chrome MV3 documentation and make note of where the two browsers may need different code. In general we want to have as similar code bases between the two as we can.
I'll look for the Firefox MV2 depreciation timeline at the beginning of 2024 / the Spring semester.

I misspoke in the meeting saying Firefox was phasing out MV2, they haven't updated their timeline to phase out MV2 yet. I will keep an eye out for a new MV3 timeline update but I didn't see anything as of today. Jocelyn and I will still continue to create a list of changes because MV3 is fully supported now in Firefox.
Firefox migration guide
Firefox MV3 new features

Jocelyn and I will still continue to create a list of changes because MV3 is fully supported now in Firefox.

Sounds good!

@sophieeng and @OliverWang13 will check if now is a good time to move to MV3. @Mattm27 and @franciscawijaya can actually do most of the implementation.

@OliverWang13 and I have begun to put together a to-do list specifically catered to migrating Optmeowt to MV3. Here is what we have so far:

Update manifest.json manifest_version key to 3
Move host permissions in permission key to host_permission key in manifest.json
Set the persistent property to be false ("persistent": false”) in the background section of manifest.json
Move extensions CSP to “content_security_policy.extension_pages” in manifest.json

i.e. "content_security_policy": {
"extension_pages": "…"
Can remove unsafe-eval as it is discouraged in mv3

Update code to use the scripting API (More details to follow)
Add add-on ID to browser_specific_settings.gecko.id in manifest.json

These tasks were created based on the migration guide posted by Firefox, but is preliminary as there is more needed to get done to complete the migration.

Thanks, @Mattm27!
A few of these seem fairly trivial.

Set the persistent property to be false ("persistent": false”) in the background section of manifest.json

This is the same as what was necessary to move our Chrome version to MV3, so hopefully we can create a new file based on our Chrome file (or ideally consolidate them into one file). Persistence is what allows us to maintain global variables, which is currently integral to how our protection-ff.js runs.

Can remove unsafe-eval as it is discouraged in mv3

This might be able to be removed or not depending on if we need it in order to place the DOM signal. It is possible that we need it.

Update code to use the scripting API (More details to follow)

This is also what we needed to do for Chrome MV3, so hopefully we can just reuse our content script methods.

@Mattm27, @sophieeng, and I met to try and get started on implementing MV3 changes. Things are looking a little more complicated than I originally thought, but it should still be doable. Different permissions are allowed for Firefox and Chrome, so not all of our methods will hold up between them. Our method for injecting the DOM signal might not work for Firefox, but this still will need more investigation. Our method for the headers on Chrome should work for Firefox as well, but that will require more investigation.
We have started off by making some of the simpler manifest changes and trying a few long-shot ideas, but we can now proceed in a more methodical manner.

Excellent!

@Mattm27 will work on this together with @OliverWang13 and @sophieeng.

I've been messing around with the code and reading some Mv3 discussion threads. It seems as though a big difference for Firefox Mv3 is that permissions are not granted automatically on each site.
See here and here
Once I approved the permissions, the header signal sent just fine (only the universal header that sets the GPC, the logic to turn off the header is not implemented yet).
@Mattm27, could you read the threads above and try to replicate these results? Could you also investigate to find if there is a workaround for requesting permissions manually for each site? Thanks.

@OliverWang13, I was able to replicate these results, and once I enabled host permissions the header signal was sent as it should.
One potential workaround for requesting permissions manually for each site I came across in this thread mentions creating a runtime.OnInstalled handler to the background script which will open a new tab upon installation or after an update where we can request required host permissions from the user using the callback permissions.request. However, the only caveat to this is that if the user ignores this request at the time of installation, they may be confused as to why the extension is not working properly when they try to use OptMeowt, so another option would be to utilize permissions.contains which checks if host permissions have been enabled whenever a user visits a site with OptMeowt turned on. If these host permissions are not found, we can send a clarification message to the user asking them again to grant permissions using a button that will initiate the permissions.request callback.
These are just a few options for workarounds to manually request permissions for each site, but I will continue to look into other ways to solve this problem.

Nice, @Mattm27! Can you try implementing one of these approaches?
Let me know if you have any questions

Note to update readme/Wiki and tutorials accordingly based on new permission requests after MV3 migration.

So far I have implemented a button to the OptMeowt popup, allowing for a more programatic way to enable host permissions. Once these permissions are set, they will persist on all sites for as long as the extension is installed. This is more of just a proof of concept with the end goal being to move this button to some sort of alert or new tab upon installation notifying the user that these host permissions are needed for the extension to work properly.
@OliverWang13 and I are planning to meet sometime later this week to discuss the implementation of a listener and handler using runtime.onInstalled to prompt the user to enable these permissions upon installation. In addition to this, we will also be looking into ways to flag if a user already has these host permissions enabled so they will not receive an invasive alert helping to improve user experience.

Excellent!

@OliverWang13 and I met today and implemented a popup in the options page upon installation prompting the user to enable host permissions using a button that then sets these permissions. After the button is clicked, the header signal sends correctly however we are still working on implementing these same strategies for sending the DOM Signal.

We have implemented DOM Signal functionality into our MV3 migration and have removed a large majority of the browser checks from the codebase. In the reference server, the DOM signal is now present when OptMeowt is enabled however we are still working through bugs relating to the website response dropdown in the popup and the OptMeowt extension icon not changing colors when Do Not Sell is enabled. @OliverWang13 and I will continue to work through these bugs this upcoming week, but it seems we are nearing an end to this migration process.

@OliverWang13 and I have met and solved the problem resulting in bugs with the Website Response and extension icon. These bugs occurred because of the argument sender.origin was marked as undefined not allowing us to access the necessary URL. To work around this we implemented a new message argument message.origin.url to access this URL instead. We are putting together a checklist for final bug checks that we will continue to work through.
We also stumbled upon another slight structural issue surrounding our 3rd party domain storage that should have been fixed for Chrome MV3 but must have slipped through the cracks which we will look into more this week.

Here is a checklist @OliverWang13 and I put together to go through after implementing MV3 changes:

[ ] - 3rd Party Domains button responding correctly
[ ] - Website Response button in popup reflects GPC Signal information
[ ] - Domain List button works and the list builds correctly when visiting new sites
[ ] - Domains can be toggled on/off
[ ] - Remaining two buttons on the settings page (Enable and Disable) work correctly
[ ] - Export and Import Domain List buttons are fully functional
[ ] - Disable/Enable button works visually
[ ] - Disable/Enable button works functionally
[ ] - Domain List button Popup button works
[ ] - Darkmode Toggle functional

We are still working through errors with 3rd Party Domain and Website Response dropdown functionality as we mentioned in this weeks meeting.

For @OliverWang13:

[ ] - 3rd Party Domains button responding correctly
[ ]  - Website Response button in popup reflects GPC Signal information
[ ]  - Domain List button works and the list builds correctly when visiting new sites
[ ]  - Domains can be toggled on/off
[ ]  - Remaining two buttons on the settings page (Enable and Disable) work correctly
[ ]  - Export and Import Domain List buttons are fully functional
[ ]  - Disable/Enable button works visually
[ ]  - Disable/Enable button works functionally
[ ]  - Domain List button Popup button works
[ ]  - Darkmode Toggle functional

@OliverWang13 and I have implemented a new storage system using IndexDB to store 3rd Party Domain data to work around the deprecation of persistent background pages in MV3. This has proven to be a good approach as the 3rd party data is no longer wiped when the background page is terminated, allowing the 3rd Party Domains dropdown to function properly in the popup.
We began attempting to use the same approach to tackle problems with the Website Response button dropdown, storing wellknown data fetched in the contentScripts.js using IndexDB. However we have run into problems accessing this data in other background scripts like protection.js, so we are planning on moving forward by instead just fetching and storing this wellknown data within protection.js.

@OliverWang13 and I have separately implemented changes to tackle issues with the Website Response button dropdown as well as changing the color of the extension icon when a site accepts the GPC signal. Although both functions are working correctly, they are a bit buggy at times only working on some websites once the site is reloaded.
This issue seems to be occurring because the wellknown data is stored in the database only after the webpage is reloaded, which was a similar bug we ran into with 3rd party domains.
We will continue working through this bug as the week goes on.

Good progress, @Mattm27!
It would be good if you can demo today.

@OliverWang13 and I have fixed a bug that was occurring with 3rd party domains, in which some 3rd party domains on one site would accumulate within the 3rd party domains drop-down of a separate site although they were not present on the current site. We resolved this issue by storing 3rd party domains based on the tab ID they are associated with using details.tabId in the updateDomainlist function in protection.js.
At this point, some refactoring is left to do before we are set for a new release but the migration to MV3 in terms of main functionality now seems to be complete.

Excellent! Well done!

Refactoring has been finished, we are now ready to create a new release.

Excellent! Great work, @Mattm27 and @OliverWang13!
@Mattm27, if all tests are passing and the UI tests are good, feel free to create a release in the repo.
Also, it would be good if you can create a new release on the Firefox Add On Store. You should have all rights to do so. They might approve it right away but there may also be some back-and-forth.
For Chrome, can you provide me a distribution version so that I can create a release on the Chrome Web Store?
Before creating the releases be sure to update the version number, permissions, ..., anything else necessary in the manifest files.

Note to update readme/Wiki and tutorials accordingly based on new permission requests after MV3 migration.

Were you able to make these updates, @Mattm27?

I have not, but will read through and update today.

The green ring issue (#460) popped up again (for Firefox).

Both the Firefox Add-on Store and the Chrome Web Store now have v5.0.1 with mv3.
@Mattm27, if there is nothing more to do from your end, feel free to close this issue!
Great work!

I have not, but will read through and update today.

Especially, if you can confirm, that this is done.

I have not, but will read through and update today.

Especially, if you can confirm, that this is done.

Yes this is complete. I will close the issue!


VirtualBox Guest Additions version does not match latest VirtualBox version

The VirtualBox Guest Additions version on server2 does not match latest VirtualBox version.
Guest Additions Version: 5.2.30
VirtualBox Version: 6.0
This might cause issues for users in the future.
Steps to reproduce the behavior:

After running 'vagrant up' for the first time, the error occurs while it is checking for the guest additions in the VM.

Same problem here.. Can you update the vagrant box ?
[server1] GuestAdditions versions on your host (6.1.18) and guest (5.2.30) do not match.
Updating Subscription Management repositories.
Unable to read consumer identity
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Error: There are no enabled repos.
Unmounting Virtualbox Guest Additions ISO from: /mnt
umount: /mnt: not mounted.
==> server1: Checking for guest additions in VM...
server1: The guest additions on this VM do not match the installed version of
server1: VirtualBox! In most cases this is fine, but in rare cases it can
server1: prevent things such as shared folders from working properly. If you see
server1: shared folder errors, please make sure the guest additions within the
server1: virtual machine match the version of VirtualBox you have installed on
server1: your host and reload your VM.
server1:
server1: Guest Additions Version: 5.2.30
server1: VirtualBox Version: 6.1
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
umount /mnt
Stdout from the command:
Stderr from the command:
umount: /mnt: not mounted.


update for Fastify v5

Resolves #26

Removed the engines field in for consistency with other plugins and https://github.com/fastify/accept-negotiator/issues/26#issuecomment-1790633565


Angular date filter in IE

Hi,
I have an issue with date filter and timezone in IE 11.
I created a plunker.
http://plnkr.co/FzVbYl
The filter is not formatting the date-time based on the timezone.
Example, if you change your system time and run the plunker, the time is the local time of browser. Which is incorrect.
This works btw in chrome, safari and firefox.

Basically, this is an IE/Edge bug:
When Date.parse-ing a date string, they don't recognize the timezone in the format +HH:mm (but only without the :). According to the spec, the timezone should contain :.
The ISO 8601 Standard allows both forms (with and without :). Although the Date implementation in JavaScript does not 100% follow the ISO 8601 Standard (it's just based on it), all other browsers seem to recognize both forms as well.
Typically this is a browser bug, but since it should be easy to work-around, I believe this is worth fixing in Angular itself.
--
@shavo007, in the meantime, you can remove the : from timezone offset (i.e. replace +09:30 with +0930) to work make it work consistently across browsers.

Fantastic. I appreciate the detailed response.

@gkalpak  what release is this in?

@shavo007, this has been fixed in master. It will be in the upcoming 1.5.0 and 1.4.10 releases (although I'm not sure about the exact release dates).

No probs.

MICROSOFT LOVES STANDARDS. AS LONG AS THE ARE MADE BY THEM


BeanParam was not correctly handling hidden values

The code was checking for hidden, however used it only to not ask
about additional metadata. It ended up still adding it to the
collection.

@jaym Close this PR and create a new one. There was an issue with travis #346
;)


feat(storage): make it possible to disable read tx timeout

Builds on top of https://github.com/paradigmxyz/reth/pull/6177, as per the PR title.

How can we reduce duration of these tests? 2x60s seems a bit excessive. @shekhirin


Snippets won't show in cshtml files

Hello! I've found a bug while using your extension. It appears that the snippets aren't working for cshtml files because of the language mode. They only work when the language mode is set to html.
Taking a look at your project, I think this can be fixed by adding these two snippets inside package.json:
"contributes": {
        "snippets": [
            (...)
            {
                "language": "razor"
                "path": "./snippets/razor.json"
            },
            {
                "language": "aspnetcorerazor"
                "path": "./snippets/razor.json"
            },
        ]
    }

Nice extension by the way; Thank you in advance!

Hi, I've set it to HTML some time ago when Razor support did crash a lot - so that it works even if you disable Razor support. It seems fine now so I could probably revert it but it should work as-is anyway in HTML parts of .cshtml file.

If I were to just add entries for aspnetcorerazor and razor (without disabling it for HTML) it would lead to snippets appearing twice in the list (if I remember correctly).
Is C# extension working correctly for you? Do you get regular autocompletion from it in .cshtml files?

At first, when I read your response, thought the problem was that my project is a Razor Pages project, so i created an MVC project and the extension worked fine.
Then I created a new Razor Pages project and extension worked too, but it still wouldn't work on my original Razor Pages project.
Finally, I just closed and reopen my original project and the extension started to work again...
You were right, there was something wrong going on with the C# extension. I'm sorry, my bad! 😅
Thank you!


2 GPUs showing misalignment

First, thank you.
I have two GPUs, and after adding the display, they were a bit misaligned. How to solve it? Thanks

how do you show 2 GPUs. I only get one one of them....

how do you show 2 GPUs. I only get one one of them....
LCC GPU module might be running the Conky backend on your system, while only the pynvml backend supports multiple GPUs. To check if pynvml backend can discover all GPUs, run /path/to/lcc/lib/components/gpu_nvml.

Fixed by commit 652367c7 which improves support for multiple GPUs.


PowerTrack v2 rule validation

This pull request adds functionality for validating PowerTrack rules against the new rule validator end-point described here: http://support.gnip.com/apis/powertrack2.0/transition.html#NewEndpoints

Thanks! Merged at https://github.com/zauberlabs/gnip4j/pull/65. I changed how POST can return a payload, added a test, and also changed the name of some getters.


Task Status Not Visible in Note Refs

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[X] Views.  Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[ ] Publish.  External Site Publish
[X] Markdown.  Markdown features, such as syntax support and features

Describe the bug
Note Refs no longer show Tasks Status correctly in Preview.
To Reproduce

Create a Task Note
Link to it in Note A
Reference Note A in Note B
Notice the Preview for Note B does not show a checkbox for the Task Link in the Note A Reference.

Expected behavior
Task Note should show Status in Note References.
Screenshots
How it looks currently:

How it should look:

Desktop (please complete the following information)

OS: [e.g. iOS]
Browser (if with published websites; include version): [e.g. chrome, safari]
Versions (all that apply to bug):

Dendron Extension: v0.114.0
VS Code version: 1.71.2
Dendron CLI:

Additional context
Add any other context about the problem here.
Dendron Log file
dendron.log

#3578

Thank you for the report @RenStrike,
and @samuelxyz for linking the issue.
@RenStrike looks like #3578 is a duplicate issue. Please let us know if there are additional concerns outside what #3578 is describing, and let us know here in the thread? (or alternatively, you could close this and comment in the existing issue so we can track the issue at one place)


Bugs related to Access Camera permission when using WalletConnect feature

Describe the bug
Bugs related to Access Camera permission when using WalletConnect feature

[x] Do not show popup Access camera permission when using the WallectConnect feature
Case 1: Access permission
Steps:

Open the SubWallet app
Go to Settings then click on WalletConnect
On the popup Access camera setting then choose "Don't allow/Dismiss"
Observe the screen displayed

Actual:

iOS device: Show black screen -> Can't use app
Android: Show "Camera not authorized"

Expect: Back to Settings screen
Case 2: After dismiss permission
Actual: Show black screen with message "Camera not authorized", do not show popup "Notifications"
Expected: Show popup "Notifications", redirect user go to Setting device to edit permission (refer camera access with other feature)
https://github.com/Koniverse/SubWallet-Mobile/assets/130966515/6bb2bf05-f58c-4196-b668-adf6301c8a61

[x] Show a grey screen when disconnecting the WalletConnect connection while standing on the "Manage connection" screen
Pre-condition: Performing connected to WalletConnect
Steps:

Go to the manage WalletConnect connection screen (dApp on desktop)
Go to dApp page, perform disconnect
Back to mobile app then observe the screen display

Actual: Show black screen
Expect: Back to the Settings screen
https://github.com/Koniverse/SubWallet-Mobile/assets/130966515/c33e3093-a9ac-489a-ba92-e721776c9edf
Notes for Tester @ThaoNguyen998 : after fixed these bug, re-check all feature using Camera

Version test: PR #1290 12:06 26/12/2023
Device test: MI 8 Lite

[ ] Show popup access camera when cancel
Steps:

Install SubWallet app
Go to WalletConnect
On the popup access camera, select Cancel
Observe the displayed screen

Actual: Show popup access camera
Expect: Back to Setting screen

Version test: PR #1290 19:28 27/12/2023
Device test: IP 11, SS S20 FE 5G, Mi 8 Lite
Validation passed.


KafkaJSNonRetriableError: Invalid topic

Hello,
So following is the output i receive. I've added the test code below as well.
[Nest] 14783   - 12/20/2020, 2:30:46 PM   [RoutesResolver] AppController {}: +151ms
[Nest] 14783   - 12/20/2020, 2:30:46 PM   [RouterExplorer] Mapped {, GET} route +3ms
[Nest] 14783   - 12/20/2020, 2:30:46 PM   [RouterExplorer] Mapped {/auth/amazon/callback, GET} route +1ms
[Nest] 14783   - 12/20/2020, 2:30:46 PM   [RoutesResolver] TestConsumer {/kafka}: +10ms
[Nest] 14783   - 12/20/2020, 2:30:46 PM   [RouterExplorer] Mapped {/kafka, POST} route +1ms
[Nest] 14783   - 12/20/2020, 2:30:46 PM   [RouterExplorer] Mapped {/kafka, GET} route +12ms
[Nest] 14783   - 12/20/2020, 2:30:46 PM   [KafkaService] INFO [Consumer] Starting {"timestamp":"2020-12-20T19:30:46.656Z","logger":"kafkajs","groupId":"test-e2e-consumer"}
[Nest] 14783   - 12/20/2020, 2:30:46 PM   [NestApplication] Nest application successfully started +145ms
[Nest] 14783   - 12/20/2020, 2:30:50 PM   [ExceptionsHandler] Invalid topic +3637ms
KafkaJSNonRetriableError: Invalid topic

import { Module } from '@nestjs/common';
import { KafkaAvroRequestSerializer, KafkaAvroResponseDeserializer, KafkaModule } from '@rob3000/nestjs-kafka';
import { TestConsumer, TOPIC_NAME } from './test.consumer';

@Module({
  imports: [
    KafkaModule.register([
      {
        name: 'KAFKA_SERVICE',
        options: {
          client: {
            clientId: 'test-e2e',
            brokers: ['localhost:9092'],
            retry: {
              retries: 2,
              initialRetryTime: 30,
            },
          },
          consumer: {
            groupId: 'test-e2e-consumer',
            allowAutoTopicCreation: true,
          },
        }
      },
    ]),

  ],
  providers: [],
  controllers: [TestConsumer],
})
export class TestModule {
}

import { Controller, Get, Inject } from '@nestjs/common';
import { KafkaService, SubscribeTo } from '@rob3000/nestjs-kafka';
import { Payload } from '@nestjs/microservices';

export const TOPIC_NAME = 'say.hello';

@Controller('/kafka')
export class TestConsumer {

  // Used to log the errors for testing.
  messages = [];

  constructor(
    @Inject('KAFKA_SERVICE') private client: KafkaService,
  ) {
  }

  onModuleInit(): void {
    this.client.subscribeToResponseOf(TOPIC_NAME, this);
  }

  @SubscribeTo(TOPIC_NAME)
  async message(@Payload() data: any): Promise<void> {
    this.messages.push(data);
  }

  @Get()
  async index() {
    const a = {
      messages: [{
        key: '1',
        value: '<IP_ADDRESS>',
      }],
      topic: TOPIC_NAME,
    };
    return await this.client.send(a);
  }
}

Hey @kodeine This will most likely because you're trying to consume from a topic that doesn't exist. The allowAutoTopicCreation is used for producing messages. In order to consume the topic needs to exist. We create the topic here: https://github.com/rob3000/nestjs-kafka/blob/5ea3ceb21411bd8a2d45877deaf47153e59be56c/kafka/docker-compose.yml#L26


Fixed decryptAndSetPassword to avoid NPE on entries without password

Hi,
While running the code that iterates through all entries and displays the password I received a NullPointException when executing "entry.getPassword().isEmpty()". The reason was a forgotten entry without password so "entry.getPassword()"  was null.
I added an additional null verification before the password decrypt.
Cheers,

Thanks for the fix!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


oc-client renderComponent(s) fail with 'getCompiledTemplate is not a function'

I am using oc-client 2.1.0 in a nodejs project and when I call renderComponent I get the following error:
/node_modules/oc-client/src/get-compiled-template.js:36
        cb(null, templateEngines[template.type].getCompiledTemplate(templateText, template.key));
                                                ^

TypeError: templateEngines[template.type].getCompiledTemplate is not a function
    at /Users/nenodimitrov/projects/partner-value/branded-seo-generator/server/node_modules/oc-client/src/get-compiled-template.js:36:49
    at respond (/Users/nenodimitrov/projects/partner-value/branded-seo-generator/server/node_modules/minimal-request/src/index.js:35:7)
    at IncomingMessage.<anonymous> (/Users/nenodimitrov/projects/partner-value/branded-seo-generator/server/node_modules/minimal-request/src/index.js:73:11)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

It looks like while the source for oc-client is written for os-template-jade 2.0, the dependency in package.json is still oc-template-jade 1.0.0 thus the templateEngine has getPrecompiledTemplate method instead of getCompiledTemplate

You're right. @nickbalestra I think we didn't update the client/package.json when working on this https://github.com/opentable/oc/pull/385
And the tests didn't catch the issue as they use the root's package.json as source.

@nenodimitrov I just published 2.1.1 with the fix. Sorry for the inconvenience.


Training it from scratch

Has anyone tried to train SqueezeDet from scratch? If yes how long does it take to converge? I have some multimodal features I am using hence cannot use the ImageNet pretrained weights. But my model doesn't seem to converge. Any ideas/ tips/tricks is highly appreciated thanks.

@aditya1709 Hi!
How did you notice the model non-convergence?
Did you check mAP?


Migrate to Poetry

Python packaging isn't solved yet but Poetry is the most popular closest-to-the-solution thing out there.
With Poetry, we'll get:

Dependency locks.
Automatic venvs.
Python version pinning.
Runtime and dev dependencies managed in pyproject.toml.
Neat build targets in a future Makefile.

Migration checklist

[ ] api project is Poetry-installable.
[ ] Build isn't broken for both Dockerfiles.
[ ] All api- and platform- workflows are not broken.
[ ] Update documentation

Hi folks, I am interested to solve this one. Should this be a one big PR or broken into multiple small PRs?

I don't think there are TOO many things to change here? So I would go for 1 PR.

I think I forgot to add the documentation updates with the PR.

I think I forgot to add the documentation updates with the PR.

Ah yes, could you submit a separate PR with that?

I can't seem to find any docs for it, where should I put it ?
I think basic instructions to setup the project, and running tests is enough

https://docs.flagsmith.com/deployment/hosting/locally-api
and
https://docs.flagsmith.com/platform/contributing
Thats all I think!

hey @tushar5526 - just checking to see if you are still planning on working on the docs? No problem if not, but we don't want to duplicate your work - thanks!

I would love to do it, but I won't be able to do it till the weekend.

OK sure no problem - thanks for the reply


Fix yml method call

yml is from Project class

This is important as it fixes the hardcover integration.

:beers:


Add TouchFart

One of the original fun things to do on the touch bar, why wouldn't it be in this list?

love this 😆 thanks for the PR!


Add "shell" option to user

Adding support for "shell" option.(for itamae

+1 for this change :+1:
I had been trying to do the same work for Serverkit's user resource and I'm about to send a pull-request. However, your pull-request seems great than mine. I hope this change will be merged soon :pray:

LGTM. Thanks!

Released as v2.29.0.

Thanks for quick merging! Now serverkit can easily create user with specified login-shell :heart_eyes:
$ echo '
resources:
  - type: user
    name: zshlover
    shell: /bin/zsh
' > recipe.yml
$ gem install serverkit
$ serverkit apply recipe.yml
[DONE] user zshlover on <IP_ADDRESS>

Thank you for merging!!


License problem

Hi, can you give this project a license so I can deploy it to webjars? Thanks!

Hi, This has a license; a GE Software Development License.
As this is part of the GE brand, it will NOT be opened sourced like other Predix Design System repos. To use the code in this repo, you will have to purchase Predix or otherwise work with GE procurement to obtain a license.


What's redisConfigurationKey = "redis"

I configed exactly same the guidline:
const string redisConfigurationKey = "redis";
services.AddSingleton(typeof(ICacheManagerConfiguration),
    new CacheManager.Core.ConfigurationBuilder()
        .WithJsonSerializer(serializationSettings: jss, deserializationSettings: jss)
        .WithUpdateMode(CacheUpdateMode.Up)
        .WithRedisConfiguration(redisConfigurationKey, config =>
        {
            config.WithAllowAdmin()
                .WithDatabase(0)
                .WithEndpoint("localhost", 6379);
        })
        .WithMaxRetries(100)
        .WithRetryTimeout(50)
        .WithRedisCacheHandle(redisConfigurationKey)
        .WithExpiration(ExpirationMode.Absolute, TimeSpan.FromMinutes(10))
        .Build());
services.AddSingleton(typeof(ICacheManager<>), typeof(BaseCacheManager<>));

It work well. But what's the redisConfigurationKey? Does it have anything to do with the configuration in appsettings.json file?

You can configure the expiration settings for each handle/layer when configuring the CacheManager instance. More info


Auto push package to PyPI on merge to master if tests pass

Should be fairly trivial via Codeship.

Not quite as trivial as expected.


Catalog provider ReadObject doesn't return the properties schema

model.CatalogState{
Id: "catalog1",
Spec: &model.CatalogSpec{
ParentName: "parent",
Properties: map[string]interface{}{
"components": map[string]interface{}{
"Name": "name",
"Type": "type",
},
},
},
}

Not sure if it's by designed.

Can you please clarify what do you mean by "properties schema"?

The catalog properties is like this:
Properties: map[string]interface{}{
"components": map[string]interface{}{
"Name": "name",
"Type": "type",
},
However. if we do catalog provider read object, the returned result is like this
{
"Name":"name"
"Type": "type"
}
The components field is missing.
I believe here's the cause:
https://github.com/eclipse-symphony/symphony/blob/e0d08a86434c4247f985f702d6ba3959439f7340/api/pkg/apis/v1alpha1/providers/config/catalog/catalogprovider.go#L137
@Haishi2016


Create Lazy Load container import

Currently, a full import of containers must be performed via an external process. While this is a good first step, it can lead to obvious synchronization issues, especially for higher traffic registries. It is necessary to create an inline "lazy container image load" function that performs on-the-fly-imports as such:

if the container blob is not listed in the Estuary index or IPFS

pull down container from source registry mirror
parse and add container blobs to estuary/IPFS per import process
send the HTTP redirect to the CID back to the client per normal flow

See https://github.com/docker/docker.github.io/blob/master/registry/recipes/mirror.md


Transient test failures

$ ./test
Building fleetd...
Building fleetctl...
Running tests...
ERROR reconcile.go:253: Desired state and current state of Job(foo.service) nil, not sure what to do
ERROR reconcile.go:253: Desired state and current state of Job(foo.service) nil, not sure what to do
ERROR unit_state.go:224: Refusing to push UnitState(foo.service), no MachineID: &unit.UnitState{LoadState:"", ActiveState:"active", SubState:"", MachineID:"", UnitHash:"", UnitName:"foo.service"}
--- FAIL: TestUnitStatePublisherRunWithDelays-2 (0.00 seconds)
	unit_state_test.go:626: bad published UnitStates: got []string{"0.service", "2.service", "4.service", "1.service", "3.service"}, want []string{"0.service", "1.service", "2.service", "3.service", "4.service"}
	unit_state_test.go:640: bad published UnitStates: got []string{"0.service", "2.service", "4.service", "1.service", "3.service"}, want []string{"0.service", "1.service", "2.service", "3.service", "4.service"}
	unit_state_test.go:658: bad UnitStates: got []string{"foo.service", "baz.service", "bar.service"}, want []string{"foo.service", "bar.service", "baz.service"}
FAIL
coverage: 70.6% of statements
FAIL	github.com/coreos/fleet/agent	0.009s
ok  	github.com/coreos/fleet/api	0.010s	coverage: 80.4% of statements
ok  	github.com/coreos/fleet/config	0.004s	coverage: 100.0% of statements
ok  	github.com/coreos/fleet/engine	0.009s	coverage: 54.5% of statements
ok  	github.com/coreos/fleet/fleetctl	0.010s	coverage: 23.3% of statements
ok  	github.com/coreos/fleet/job	0.009s	coverage: 89.2% of statements
ok  	github.com/coreos/fleet/machine	0.007s	coverage: 35.1% of statements
ok  	github.com/coreos/fleet/pkg	0.009s	coverage: 81.9% of statements
ok  	github.com/coreos/fleet/pkg/lease	0.006s	coverage: 14.3% of statements
ok  	github.com/coreos/fleet/registry	0.008s	coverage: 26.7% of statements
ok  	github.com/coreos/fleet/ssh	0.009s	coverage: 42.5% of statements
ok  	github.com/coreos/fleet/systemd	0.006s	coverage: 15.5% of statements
ok  	github.com/coreos/fleet/unit	0.037s	coverage: 88.4% of statements

Seeing this every once in a while on travis. This failure was from https://travis-ci.org/coreos/fleet/jobs/66578356

Here's another: https://travis-ci.org/coreos/fleet/jobs/67288307

i can't reproduce this at all locally, but lately it happens repeatedly on travis-ci. :-1:

can reproduce with GOMAXPROCS > 1. there's also a nice deadlock..
$ PKG=agent ./test -run TestUnitStatePublisherRunWithDelays
Building fleetd...
Building fleetctl...
Running tests...
fatal error: all goroutines are asleep - deadlock!

goroutine 1 [chan receive]:
testing.RunTests(0x80af70, 0x910c80, 0x12, 0x12, 0x7c9001)
        /home/mischief/go1.4/go/src/testing/testing.go:556 +0xad6
testing.(*M).Run(0xc20804a320, 0x91b660)
        /home/mischief/go1.4/go/src/testing/testing.go:485 +0x6c
main.main()
        github.com/coreos/fleet/agent/_test/_testmain.go:142 +0x291

goroutine 5 [semacquire]:
sync.(*WaitGroup).Wait(0xc20800a4c0)
        /home/mischief/go1.4/go/src/sync/waitgroup.go:132 +0x169
github.com/coreos/fleet/agent.TestUnitStatePublisherRunWithDelays(0xc20806a1b0)
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/agent/unit_state_test.go:621 +0x115e
testing.tRunner(0xc20806a1b0, 0x910de8)
        /home/mischief/go1.4/go/src/testing/testing.go:447 +0xbf
created by testing.RunTests
        /home/mischief/go1.4/go/src/testing/testing.go:555 +0xa8b

goroutine 6 [select]:
github.com/coreos/fleet/agent.(*UnitStatePublisher).Run(0xc208084080, 0xc208056360, 0xc2080563c0)
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:128 +0x3df
github.com/coreos/fleet/agent.func·017()
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/agent/unit_state_test.go:568 +0x43
created by github.com/coreos/fleet/agent.TestUnitStatePublisherRunWithDelays
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/agent/unit_state_test.go:569 +0x6a5

goroutine 17 [select]:
github.com/coreos/fleet/agent.func·008()
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:73 +0x296
created by github.com/coreos/fleet/agent.(*UnitStatePublisher).Run
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:89 +0xf5

goroutine 18 [chan receive]:
github.com/coreos/fleet/Godeps/_workspace/src/github.com/jonboulle/clockwork.(*fakeClock).Sleep(0xc208056240, 0xb2d05e00)
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/Godeps/_workspace/src/github.com/jonboulle/clockwork/clockwork.go:115 +0x55
github.com/coreos/fleet/agent.func·016(0x780970, 0xb, 0xc20809a1e0)
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/agent/unit_state_test.go:548 +0x74
github.com/coreos/fleet/agent.func·009()
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:118 +0x27f
created by github.com/coreos/fleet/agent.(*UnitStatePublisher).Run
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:122 +0x1fe

goroutine 19 [chan receive]:
github.com/coreos/fleet/Godeps/_workspace/src/github.com/jonboulle/clockwork.(*fakeClock).Sleep(0xc208056240, 0xb2d05e00)
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/Godeps/_workspace/src/github.com/jonboulle/clockwork/clockwork.go:115 +0x55
github.com/coreos/fleet/agent.func·016(0x77dd30, 0xb, 0xc20809a120)
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/agent/unit_state_test.go:548 +0x74
github.com/coreos/fleet/agent.func·009()
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:118 +0x27f
created by github.com/coreos/fleet/agent.(*UnitStatePublisher).Run
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:122 +0x1fe

goroutine 20 [select]:
github.com/coreos/fleet/agent.func·009()
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:100 +0x2aa
created by github.com/coreos/fleet/agent.(*UnitStatePublisher).Run
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:122 +0x1fe

goroutine 21 [chan receive]:
github.com/coreos/fleet/Godeps/_workspace/src/github.com/jonboulle/clockwork.(*fakeClock).Sleep(0xc208056240, 0xb2d05e00)
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/Godeps/_workspace/src/github.com/jonboulle/clockwork/clockwork.go:115 +0x55
github.com/coreos/fleet/agent.func·016(0xc20802aa70, 0x9, 0xc208056600)
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/agent/unit_state_test.go:548 +0x74
github.com/coreos/fleet/agent.func·009()
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:118 +0x27f
created by github.com/coreos/fleet/agent.(*UnitStatePublisher).Run
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:122 +0x1fe

goroutine 22 [chan receive]:
github.com/coreos/fleet/Godeps/_workspace/src/github.com/jonboulle/clockwork.(*fakeClock).Sleep(0xc208056240, 0xb2d05e00)
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/Godeps/_workspace/src/github.com/jonboulle/clockwork/clockwork.go:115 +0x55
github.com/coreos/fleet/agent.func·016(0x77dd90, 0xb, 0xc20809a180)
        /mnt/host/source/src/third_party/fleet/gopath/src/github.com/coreos/fleet/agent/unit_state_test.go:548 +0x74
github.com/coreos/fleet/agent.func·009()
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:118 +0x27f
created by github.com/coreos/fleet/agent.(*UnitStatePublisher).Run
        github.com/coreos/fleet/agent/_test/_obj_test/unit_state.go:122 +0x1fe
FAIL    github.com/coreos/fleet/agent   0.006s

there seems to have been a number of races in the agent tests, the last of which i believe is following:
$ PKG=agent ./test
Building fleetd...
Building fleetctl...
Running tests...
ERROR reconcile.go:265: Desired state and current state of Job(foo.service) nil, not sure what to do
ERROR reconcile.go:265: Desired state and current state of Job(foo.service) nil, not sure what to do
ERROR unit_state.go:243: Refusing to push UnitState(foo.service), no MachineID: &unit.UnitState{LoadState:"", ActiveState:"active", SubState:"", MachineID:"", UnitHash:"", UnitName:"foo.service"}
--- FAIL: TestUnitStatePublisherRunWithDelays-4 (0.00s)
        unit_state_test.go:650: bad toPublishStates: got map[string]*unit.UnitState{"bar.service":(*unit.UnitState)(0xc2080a06c0), "foo.service":(*unit.UnitState)(0xc2080a0660), "baz.service":(*unit.UnitState)(0xc2080a0720)}, want map[string]*unit.UnitState{"bar.service":(*unit.UnitState)(0xc2080a0840), "baz.service":(*unit.UnitState)(0xc2080a08a0), "foo.service":(*unit.UnitState)(0xc2080a07e0)}
FAIL
coverage: 70.6% of statements
FAIL    github.com/coreos/fleet/agent   0.007s

The ordering of https://github.com/coreos/fleet/blob/1eebf3bead8dfdd25c1debe317b97658523257f4/agent/unit_state_test.go#L620-L626 is significant yet since they're all goroutines there's no guarantee they'll be scheduled that way. Not sure yet about a solution; ideally we would run them consecutively until they block here - https://github.com/coreos/fleet/blob/1eebf3bead8dfdd25c1debe317b97658523257f4/agent/unit_state.go#L167

For now I tossed in a Skip in https://github.com/coreos/fleet/pull/1354


read Verilog A 2.4 includes

escaped identifier for logic discipline
any other parsing issues
Optional semicolon following the nature identifier in a nature declaration
A.1.6, Syntax 3-4
Optional semicolon following the discipline identifier in a discipline declaration
A.1.7, Syntax 3-5
See sections 2.8, 2.8.1 for more information about escaped identifiers

2.8.1 Escaped identifiers
Escaped identifiers shall start with the backslash character () and end with white space (space, tab, newline,
or formfeed). They provide a means of including any of the printable ASCII characters in an identifier (the
decimal values 33 through 126 or 21 through 7E in hexadecimal).
Neither the leading backslash character nor the terminating white space is considered to be part of the identifier. Therefore, an escaped identifier \cpu3 is treated the same as a non-escaped identifier cpu3.
Examples:
\busa+index
-clock
*error-condition*
\net1/\net2
{a,b}
\a*(b+c)


HIVE-24999: HiveSubQueryRemoveRule generates invalid plan for IN subquery with multiple correlations

Work in progress, do not review yet!
What changes were proposed in this pull request?
Why are the changes needed?
How was this patch tested?

Closing as the fix was merged in https://github.com/apache/hive/commit/4f4cbeda00d5ebb7d0b8cedee5daa2c03df4a755.


Add monitoring.

We need monitoring in our app. We should monitor the following:

[x] Average CPU Load.
[x] Logins per day.
[x] Average response time for different pages.
[x] Average response time per api function
[x] Up time for server
[ ] Number of users
[ ] Number of messages
[ ] Average number of followers per user.
[ ] Average user interactions with page
[ ] Graphs for number growths.
[ ] Average Messages per second
[ ] Average Requests per second
[ ] How long does the different database queries take.
[ ] How often do we query it.
[ ] Load per application
[ ] Memory usage per application
[ ] Check if programs were killed due to excessive memory consumption
[ ] Monitor if network is up
[ ] Monitoring of load and requests per IP
[ ] Disk space
[ ] Average response time per repository function

If we want anything else monitored, please add it to the list.

My todo:

[x] Graph requests per route
[x] Average requests over last 10 minutes metric


Adding 'Python Script Generator Using ChatGPT'

I would like to propose adding a new project, the "Python Script Generator Using ChatGPT," to this repository. This project aims to provide a Python script that interacts with the OpenAI GPT-3 API to generate Python code snippets based on user-provided prompts. The generated Python scripts can be valuable for automating various tasks and simplifying the development process.

sure

could you please review my PR, your feedback would be greatly appreciated.


Reparametrize raisedcosine

This edits introduce a one extra hyper-parameters for initializing the linear raised cosine bumps, and an two one for the log-raised cosines:

width: this hyper-parameter is set for both linear- and log-spaced raised cosines. It controls the width of the cosine bumps, default is 2. The original implmentation was assuming this to be 1, but that produces aliasing
time_scaling: this hyper-parameter is available only for log-spaced raised cosines and controls the logarithmic stretch magnitude. as time_scaling approaches to 0, the transformation becomes linear. large time_scaling result in basis that are tightly concentrated around t=0
enforce_decay_to_zero: boolean, if true, it enforce the last basis to decay to zero.

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

Comparison is base (2dcf1b2) 94.88% compared to head (664169d) 95.04%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #50      +/-   ##
==========================================
+ Coverage   94.88%   95.04%   +0.16%
==========================================
  Files          10       10
  Lines         840      868      +28
==========================================
+ Hits          797      825      +28
  Misses         43       43

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

I changed the code so that the peak location is computed so that the decay to zero of the last basis element happens as late as possible. this is not equivalent to what we had before, (it would be if i use np.ceil(width) instead of width to compute the last peak location.