testnet indicator

Currently the spec uses version byte to indicate a testnet paycode, which is incongruous with how we do cashaddrs.
Shouldn't we just use paycodetest: prefix instead?

We can, and it'll likely make it easier to differentiate visually. Using version probably won't be a great harm either, but it can be improved for sure.


feat: now you can press the Escape key to deselect all items in the main gallery view

Now, if you have one or more items selected in the media gallery, they will be deselected if you press the Escape key.

looks good and works well! Seeing a build error though thats tripping over the use of document on the server

looks good and works well! Seeing a build error though thats tripping over the use of document on the server

I know what that is. I had document.body in useEffect before so no error. Now it's a custom hook, so the useEffect isn't gating the call to document.body on the client-side. I'll put up a small fix shortly

works great! thanks @nickytonline

@all-contributors please add @nickytonline for code


Add rhyming_part to custom_dict

Two ways to do this:

Just store the actual phones as if they came from CMU_dict.
Store a word that is in CMU_dict and rhymes with the custom word.

Ok, makes more sense to store the entire phones, because that's the underlying data for both the stresses() method and the rhyming_part() method of the pronouncing package.
Which means that once I have the phones in custom_dict, I should stop using stresses_for_word() and instead call stresses() directly, and add a _phones attribute to WordBuilder.
Will close this issue and create a new one.


Feat/add password input Step 2 - add logic

Context
In this pull request, I continue to finish the password input step 2, the logic part
I
Changes

add ChceckListPopover (use MUI Popover to control the show/hide of CheckList)
create useIsFocued custom hook to easily control focus status
add validators for our password validation rules

Screenshot
https://github.com/benqqqq/aha-fe-assignment/assets/11547758/fb5f59aa-10da-478a-94e0-4e49f9528312

Codecov Report

Merging #3 (ae960db) into main (6fd0ae9) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff            @@
##              main        #3   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         6    +5
  Lines            3        22   +19
  Branches         1         2    +1
=========================================
+ Hits             3        22   +19

Impacted Files
Coverage Δ

src/components/CheckList/CheckList.tsx
100.00% <ø> (ø)

src/components/Common/LoadingOrError.tsx
100.00% <ø> (ø)

src/components/CheckList/CheckListPopover.tsx
100.00% <100.00%> (ø)

src/components/PasswordTextField/validators.ts
100.00% <100.00%> (ø)

src/hooks/useIsFocused.ts
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update this repository to the currently available version on modrinth

I was looking towards modifying the mod to save my pie-chart configuration across multiple minecraft sessions, only to realize that the version here is heavily outdated compared to the one that I downloaded from modrinth.
It would be highly appreciated if you would update the source code of the mod in this repository (or that you make the piechart position, size, etc be saved across multiple sessions :D), or link me somewhere where I could find the updated source code.
Thanks in advance!

Sorry about that. The git is now updated with the latest changes. 1.20.4 is on the main branch and 1.20.1 is on the 1.20.1 branch. If what you mean by cross-session saving as saving the settings to a file, I'm not sure why I haven't done that yet as I have a framework for this, and will actually start work on that now. If it's something else, I would love to see how you implement your idea. Let me know if you have any questions about the code. Thank you!

Oh yeah, that's what I meant with cross-session saving😅. Thanks for updating the repository!


Update get_tweets_from_moe.sh

changed tavern job output dir to not get interfered by other cron jobs on the machine
updated tavern job submission to retain a semi-permanent SSH session
modified method checking success of each step to using "success.log"

Hey Matt - I've updated several things as we've discussed. The script has been tested and seems to work well on March except I'm not sure if 202MB is a good file size. Please take a look and make comments where things could be done better/fixed. Thanks!

Also, I am not sure where the 202MB thing you're mentioning comes into play? Is this the size of the file you're checking for the Twitter moe job? If so, I think that is probably too large. I would just check to see if it is empty and return an error only if the file is completely empty.


Links fix

Fixes https://github.com/inventree/inventree-docs/pull/19
"Simplest" solution is to enforce relative link pathing

Nice job!


Using scoped slots not syncing with select object literal

Version
2.2.1
Reproduction link
https://jsfiddle.net/50wL7mdz/31241/
Steps to reproduce

Create a child component with a scoped slot.
In the parent template, add the scoped template to the child component with a bound select element to a data object.
Try selecting an option.

What is expected?
I expected for this to sync the component object to the selected data object using the select data binding.
What is actually happening?
Instead, nothing happens. If I change the option's values to string, then it binds correctly. I also noted that doing the same process but putting the select in the child component works as expected.

obj should be initialised. You can find more information about this caveat here: https://vuejs.org/v2/guide/reactivity.html#Change-Detection-Caveats

@posva The object is initialized in the component's data. Did you misread the reproduction?

Oh, sorry, I did misread, indeed. What is happening is that the props object should be treated as read-only, you can not modify the content of the scope in a scoped slot. Modifications of a component should explicitly pass through it

Great, thanks! I did note that if  obj is a String, then this example works successfully. Is that just a side effect but not a recommended use?

Can you share a fiddle of that? It shouldn't work: https://jsfiddle.net/posva/nyjwjg7x/

I did not speak completely correct. It works when using v-model on an object's attribute. I guess this would be hard to avoid though since javascript will be pointing to the data object. https://jsfiddle.net/posva/nyjwjg7x/

Yes, if you point to an attribute of an object, it will work because of javascript nature. No, it's not recommended although it can come in handy sometimes 🙂
You can, however, pass a method through the scoped slot and use that as the @change event handler. Together with a :value binding, it replaces the v-model in your case. Although it's even better to keep the select within the component


CRIMAPP-366 Add "pre order work" page

Description of change
Add "Do you intend to claim pre-order work?" page behind feature flag means_journey
Add db columns
cases. is_preorder_work_claimed(string)
cases. preorder_work_date(date)
cases. preorder_work_details(text)
Link to relevant ticket
https://dsdmoj.atlassian.net/browse/CRIMAPP-366
Notes for reviewer
Currently "Do you intend to claim pre-order work?" page is behind a feature flag for local and staging
Screenshots of changes (if applicable)
Before changes:

After changes:

How to manually test the feature

Description of change
Add "Do you intend to claim pre-order work?" page behind feature flag means_journey
Add db columns
cases. is_preorder_work_claimed(string) cases. preorder_work_date(date) cases. preorder_work_details(text)
Link to relevant ticket
dsdmoj.atlassian.net/browse/CRIMAPP-366
Notes for reviewer
Currently "Do you intend to claim pre-order work?" page is behind a feature flag for local and staging
Screenshots of changes (if applicable)
Before changes:

### After changes:

## How to manually test the feature

The edited screenshot was super helpful! thanks


3.x release date

Hi!
I see that you're actively developing on the 3.x branch, do you have an approximative release date for 3?
Thanks!

There's no tentative date for a stable release yet. There's an open PR #394 which I want to get merged but haven't had the time to review.
In the meantime you can use the 3.0.0-beta1 release and report back if you have any issues.

Thanks for your feedback !


customers make mistakes all the time. should we have a page on how to delete and start from scratch?

maybe give them a script or a list of objects they need to delete to reset the module?

I don't like this idea -- mostly because I use students making mistakes as an opportunity to fix what they broke publicly in front of everyone else. This provides an additional learning/training opportunity and also shows how easy it is to troubleshoot and recover from problems in OpenShift.
If a student gets so hosed that they need to start completely over, it means the leader is not checking in frequently enough with students to see if they're having problems!

Well... I don't think they see it has easy to go and delete routes, services, deployment, secrets and finally pod.   Yet again, this is the feedback.


Could this be extended to work with the Xiaomi Body Scale?

Basically the title says it all. I've got a Xiaomi Scale that seems to work in a very similar fashion to the HT sensor. It emits BLE and it seems that the data is just encoded differently (I haven't dug very deep yet).
If so, would you accept a PR to this library for adding support for this device? I'm looking for a cleaner fashion to bring this data into Home Assistant, rather than the current implementations floating around that rely on an mqtt gateway.
Thanks!

I'd say that should be a different lib. Feel free to clone this and adjust.
Apart from that, I don't own this device, sorry.


Updating code to make flake8 and sphinx happy

The changes made in this branch are finished.  Before I ask for a review by others, I will do a self-review that consists of

[x] Careful review of all the changes made in the PR

Comments questions addressed to developers involved in this PR

[x] Confirm that altered GH actions are capable of detecting/reporting intended failures

Confirmed that flake8 action fails when I violate PEP8 in a tool and for code in the package.
I cannot confirm that the docs build action fails on failures because I have warnings temporarily treated as warnings rather than errors in which case it appears that the doc generator always returns a zero error code.  This will be dealt with in Issue #100.

[x] Check GH action documentation artifacts
[x] Check correct rendering/publishing of sphinx docs in RTD (PR only rather than official page)
[ ] Assess with others if merging this into main after develop is correct

Alexandra is investigating this.

@jcyannotty I have added you as a reviewer.  Can you please review my comments/questions for you and review all the changes made to your files?

@jcyannotty We're close to getting this branch ready for merging.  However, there are still some issues with your code that need to be addressed first.
When I build the sphinx docs, I get the following warning:
WARNING: autodoc: failed to import module 'wrappers' from module 'Taweret.core'; the following exception was raised:
cannot import name 'linear_mix' from 'Taweret.mix.bivariate_linear' (/Users/jared/Projects/BAND/Taweret/.tox/html/lib/python3.11/site-packages/Taweret/mix/bivariate_linear.py)

We suspect that this might be related to the lines
from Taweret.mix.bivariate_linear import linear_mix as LM  # TODO: needs fixing, things have moved
from Taweret.mix.trees import trees_mix as TM                    # TODO: needs fixing, things have moved

When I run flake8, I get the following
./src/Taweret/core/trees_setup.py:28:80: E501 line too long (114 > 79 characters)
./src/Taweret/core/trees_setup.py:46:80: E501 line too long (96 > 79 characters)
./src/Taweret/core/trees_setup.py:59:80: E501 line too long (96 > 79 characters)
./src/Taweret/core/trees_setup.py:82:80: E501 line too long (89 > 79 characters)
./src/Taweret/core/trees_setup.py:83:9: F841 local variable 'delete_out' is assigned to but never used
./src/Taweret/core/trees_setup.py:84:80: E501 line too long (90 > 79 characters)
./src/Taweret/core/wrappers.py:16:80: E501 line too long (98 > 79 characters)
./src/Taweret/core/wrappers.py:17:80: E501 line too long (98 > 79 characters)
./src/Taweret/mix/trees.py:7:1: F401 'logging.raiseExceptions' imported but unused
./src/Taweret/mix/trees.py:15:1: F401 'typing' imported but unused
./src/Taweret/mix/trees.py:17:1: F401 'scipy.stats.norm' imported but unused
./src/Taweret/mix/trees.py:654:13: F841 local variable 'out_pred' is assigned to but never used
./src/Taweret/mix/trees.py:658:9: F841 local variable 'fig' is assigned to but never used
./src/Taweret/mix/trees.py:696:13: F841 local variable 'out_wts' is assigned to but never used
./src/Taweret/mix/trees.py:700:9: F841 local variable 'fig' is assigned to but never used
./src/Taweret/mix/trees.py:719:9: F841 local variable 'fig' is assigned to but never used
./src/Taweret/mix/trees.py:1118:80: E501 line too long (81 > 79 characters)
./src/Taweret/tests/test_bivariate_linear.py:23:1: E402 module level import not at top of file
./src/Taweret/tests/test_bivariate_linear.py:24:1: E402 module level import not at top of file
./src/Taweret/tests/test_bivariate_linear.py:25:1: E402 module level import not at top of file
./src/Taweret/tests/test_bivariate_linear.py:26:1: E402 module level import not at top of file
./src/Taweret/tests/test_bivariate_linear.py:27:1: E402 module level import not at top of file
./src/Taweret/tests/test_gaussian.py:18:1: E402 module level import not at top of file
./src/Taweret/tests/test_gaussian.py:19:1: E402 module level import not at top of file
./src/Taweret/tests/test_gaussian.py:20:1: E402 module level import not at top of file
./src/Taweret/tests/test_trees.py:33:1: E402 module level import not at top of file
./src/Taweret/tests/test_trees.py:34:1: E402 module level import not at top of file
./src/Taweret/tests/test_trees.py:46:80: E501 line too long (80 > 79 characters)
./src/Taweret/tests/test_trees.py:71:80: E501 line too long (81 > 79 characters)
./src/Taweret/tests/test_trees.py:72:29: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
./src/Taweret/tests/test_trees.py:75:5: F841 local variable 'fit' is assigned to but never used
./src/Taweret/tests/test_trees.py:98:5: F841 local variable 'f0_test' is assigned to but never used
./src/Taweret/tests/test_trees.py:150:80: E501 line too long (101 > 79 characters)

Please let me know if you need help setting up the tools to reproduce this output.

Updates have been made. I removed trees_setup.py and wrappers.py as they are no longer needed. I went ahead and resolved all of the issues in trees.py, test_trees.py, test_gaussian.py, and test_bivariate_linear.py. For E402,, I just commented out troublesome lines that caused the flake8 errors, we can probably just remove them entirely. They used to be essential but must no longer be needed (i.e. the tests passed without them).
Also note, your flake8 output differed from mine. I have one outstanding warning that your output does not show:
C:\Users\johny\Documents\packages\Taweret\src\Taweret\__init__.py:7:1: F401 '.test.test' imported but unused
Not sure if this needs to be fixed or not. I left this unchanged for the time being.

Adding to my previous comment - the sphinx documentation still fails to build. Note, the autodoc issue was just a warning (albeit it did identify outdated files, which was a good thing!). The actual error is this
pdf: exit 2 (0.00 seconds) /home/runner/work/Taweret/Taweret> make -C docs/build_pdf pid=5218   html: OK (73.40=setup[56.03]+cmd[0.62,16.74] seconds)   pdf: FAIL code 2 (55.60=setup[41.89]+cmd[0.34,13.37,0.00] seconds)   evaluation failed :( (129.09 seconds)
We still get this after my updates.

Clarification on a previous comment - "For E402,, I just commented out troublesome lines that caused the flake8 errors, we can probably just remove them entirely". This was old code that is no longer needed to set the paths in the test files. It is safe to remove this code. I have gone ahead and deleted the commented lines. For clarity, I am referring to lines such as this
`# Set Taweret Path
print(os.getcwd())
dirname = os.popen("find $PWD -type f -name test_trees.py").read()
taweret_wd = dirname.split("test")[0]
sys.path.append(taweret_wd)`

PR approved by both developers affected by these changes.  All tests/tasks are passing except for CodeCov.   Merging.


SPM - Initial Analytics

#no-changelog

Open questions at https://forums.swift.org/t/swiftpm-binary-linker-questions/39100

Going to merge here. I can follow up on any additional comments in subsequent PRs


Concurrent transactions on the same table are aborted

When we run concurrent transactions on the same table, with one transaction updating it and the other reading from it, the transaction performing the read gets aborted.
Here are the steps to reproduce the bug:
default_database=# create table foo (id int primary key, year int);
CREATE TABLE
default_database=# insert into foo values(1,1000);
INSERT 0 1
default_database=# insert into foo values(2,2000);
INSERT 0 1
default_database=# insert into foo values(3,3000);
INSERT 0 1
default_database=# select * from foo;
 id | year
----+------
  1 | 1000
  3 | 3000
  2 | 2000
(3 rows)

Now on one connection carry out the following steps:
default_database=# begin;
BEGIN
default_database=# update foo set year = 200 where id = 2;
UPDATE 1
default_database=# select * from foo;
 id | year
----+------
  1 | 1000
  3 | 3000
  2 |  200
(3 rows)

On another connection, try any queries on the same table:
begin;
BEGIN
default_database=# select * from foo;
SELECT 0
default_database=# select * from foo; // Attempting a select again.
current transaction is aborted, commands ignored until end of transaction block

This is actually the expected behaviour. Since we don't do speculative reads,  MVTO aborts a transaction that attempts to read or update a version whose write lock is held by another transaction. So unless a multi-statement Txn is explicitly made read-only, the Txn performing the read will get aborted in the presence of concurrent updates.

Does this fact explain our low TPC performance?
I guess we should augment the TPC numbers with the abort rate - or has
someone looked at this? If its high, that would be the place to look
instead of looking at cycles spent in each function.
On Wed, Jun 13, 2018 at 11:57 AM Gandeevan Raghuraman <
<EMAIL_ADDRESS>wrote:

This is actually the expected behaviour. Since we don't do speculative
reads, MVTO aborts a transaction that attempts to read or update a version
whose write lock is held by another transaction. So unless a
multi-statement Txn is explicitly made read-only, the Txn performing the
read will get aborted in the presence of concurrent updates.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cmu-db/peloton/issues/1314#issuecomment-397010603,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABS8HLsxOby1FMTTx1l5OFZejgAa60_1ks5t8URxgaJpZM4TcaDp
.

--
Anthony Tomasic
Language Technologies Institute
Carnegie Mellon University
http://www.tiramisutransit.com
http://mcds.cs.cmu.edu http://mcds.cs.cmu.edu
http://www.cs.cmu.edu/~tomasic


Certain NameTree state transitions can cause the client to stop receiving name updates

@obeattie reported an issue with the io.l5d.k8s namer where linkerd stops receiving updates.
Per @adleong:
Overview
In our QA veggies app, Lavender1 (the externally facing service) talks to Dill3.  We will delete and then re-create the k8s service object for Dill3 which will cause Lavender1's linkerd to no longer be able to route to Dill3.
Reproduction Steps
Using our QA veggies topology, delete the dill3 service object:
kubectl --namespace=veggies delete svc/dill3

You will see this reflected in Lavender1's linkerd's logs:
D 0804 23:49:12.501 THREAD18: k8s deleted: dill3
I 0804 23:49:12.503 THREAD18: #/io.l5d.k8s/veggies/incoming/dill3: name resolution is negative (local dtab: Dtab())
D 0804 23:49:12.508 THREAD18: k8s ns veggies initial state: cayenne9, rutabaga6, rosemary5, potato7, pumpkin10, taro8, rutabaga4, lavender1, rutabaga2
D 0804 23:49:12.510 THREAD18: k8s ns veggies service dill3 missing

You will also see the corresponding loadbalancer removes in Lavender1's linkerd's metrics:
"rt/outgoing/dst/id/#/io.l5d.k8s/veggies/incoming/dill3/loadbalancer/removes": 3,

Then re-create the Dill3 service object:
kubectl --namespace=veggies create -f Dill3-svc.yml

You will see this reflected in Lavender1's linkerd's logs:
D 0804 23:49:34.296 THREAD18: k8s added: dill3
D 0804 23:49:34.296 THREAD18: k8s ns veggies initial state: dill3, cayenne9, rutabaga6, rosemary5, potato7, pumpkin10, taro8, rutabaga4, lavender1, rutabaga2
D 0804 23:49:34.297 THREAD18: k8s ns veggies service dill3 found
D 0804 23:49:34.297 THREAD18: k8s ns veggies service dill3 port incoming found + /

However, the new endpoints aren't added to loadbalancer, according to the metrics:
"rt/outgoing/dst/id/#/io.l5d.k8s/veggies/incoming/dill3/loadbalancer/size": 0,

And attempts to route requests to dill3 fail:
$ curl ....
No hosts are available for /http/dill3, Dtab.base=[/ns=>/#/io.l5d.k8s;/iface=>/ns/veggies;/srv=>/iface/incoming;/http=>/srv], Dtab.local=[]. Remote Info: Not Available

Restarting the Lavender1 linkerd fixes the issue and requests can be correctly routed to Dill3 again.

Hypothesis: there are assumptions in finagle code about activities not going Pending once they are OK.

#567 provides a workaround--potentially a correct fix.  We still need to get to the bottom of this behavior and document the contract between namers and linkerd.

Our current theory is that finagle expects that Activities never go pending once they have gone ok.  As long as we obey that invariant, we should be ok (no pun intended).  Closing this issue until something contradicts this theory.


Upgrade Django to 2.2 and upgrade Django-related libraries to latest versions

Overview

Upgrade Django to 2.2
Upgrade some django-related libraries to their latest versions

I dd not upgrade libraries related to dedupe or batch processing, as I don't know how easy it is to test regressions there.
Connects #455
Demo

Testing Instructions

vagrant destroy then ./scripts/setup and verify that everything sets up as it should
./scripts/resetdb and ./scripts/server
visit the app on 6543 and verify that the following stuff works:

registering (and getting registration email)
signing in
uploading a list
searching for facilities
saving profile updates & generating API tokens

process the list you uploaded using batch_process and verify that that still works
visit your list in the UI and confirm or reject some facility matches if any are available, verifying that that works and also that you can remove list items
visit the API docs and verify that they load and that you can use them to test the various endpoints

Checklist

[ ] fixup! commits have been squashed
[ ] CI passes after rebase
[x] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

I ran this with Python warnings enabled to see all deprecation warnings:
$ docker-compose run --rm --entrypoint python django -Wa manage.py test

And got the following unique warnings:
/usr/local/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
/usr/local/lib/python3.7/site-packages/dedupe/blocking.py:30: DeprecationWarning: time.clock has been deprecated in Python 3.3 and will be removed from Python 3.8: use time.perf_counter or time.process_time instead
/usr/local/lib/python3.7/site-packages/dedupe/core.py:267: DeprecationWarning: time.clock has been deprecated in Python 3.3 and will be removed from Python 3.8: use time.perf_counter or time.process_time instead
/usr/local/lib/python3.7/site-packages/dedupe/core.py:280: DeprecationWarning: time.clock has been deprecated in Python 3.3 and will be removed from Python 3.8: use time.perf_counter or time.process_time instead
/usr/local/lib/python3.7/site-packages/dedupe/core.py:295: DeprecationWarning: time.clock has been deprecated in Python 3.3 and will be removed from Python 3.8: use time.perf_counter or time.process_time instead
/usr/local/lib/python3.7/site-packages/itypes.py:2: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
/usr/local/lib/python3.7/site-packages/jinja2/runtime.py:318: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
/usr/local/lib/python3.7/site-packages/jinja2/utils.py:485: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
/usr/local/lib/python3.7/site-packages/past/translation/__init__.py:35: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
/usr/local/lib/python3.7/site-packages/past/types/oldstr.py:5: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
/usr/local/lib/python3.7/site-packages/whitenoise/django.py:49: RemovedInDjango31Warning: The FILE_CHARSET setting is deprecated. Starting with Django 3.1, all files read from disk must be UTF-8 encoded.
/usr/local/lib/python3.7/site-packages/xlrd/xlsx.py:266: PendingDeprecationWarning: This method will be removed in future versions.  Use 'tree.iter()' or 'list(tree.iter())' instead.
/usr/local/lib/python3.7/site-packages/xlrd/xlsx.py:312: PendingDeprecationWarning: This method will be removed in future versions.  Use 'tree.iter()' or 'list(tree.iter())' instead.

which are all in libraries, not in our code, which is good.

I ran this with Python warnings enabled to see all deprecation warnings:

Cool. It appears that most of these reference Python 3.8, which is ahead of our version (and doesn't exist in a final version until October 2019).
I didn't update Dedupe or anything because that seemed like a separate set of things to test.

After rebuilding my VM, I set a value on OAR_CLIENT_KEY and restarted my `./scripts/server
diff --git a/docker-compose.yml b/docker-compose.yml
index a769732..1f477a4 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -25,7 +25,7 @@ services:
         - DJANGO_SECRET_KEY=secret
         - DJANGO_LOG_LEVEL=INFO
         - AWS_PROFILE=${AWS_PROFILE:-open-apparel-registry}
-        - OAR_CLIENT_KEY=
+        - OAR_CLIENT_KEY=clientkey
     build:
       context: ./src/django
       dockerfile: Dockerfile

The django-rest-swaggar UI is not sending the auth header

There is an open issue
https://github.com/marcgibbons/django-rest-swagger/issues/759
Rolling back to 2.1.1 seems like the most expedient way to resolve the problem.

Correction. 2.1.2 is the latest release before 2.2.0.

I pushed 3706843febf1f234d98a1c966002a95439f430aa which upgrades DRF to 3.10.1 and downgrades DR-Swagger to 2.1.2

Thanks for checking this! Going to squish and then merge.


Is it possible to strikethrough disabled dates?

I'm trying to block certain days from being selected and I'd like to represent this with an X or strikethrough text. I am unsure of how to do this after skimming through the documentation. I noticed the font can be changed. However I can't seem to set a date to NSStrikethroughstyleattributename. Any help or recommendations would be great!
I used cocoa-pods for installation FSCalendar V2.7.4

A good approach would be subclass FSCalendarCell.


Security Vulnerability: JSON::JWT.decode Method

Just listing this as a known security vulnerability.
Vulnerable to Improper Verification of Cryptographic Signature due to a sign/encryption confusion attack via the JSON::JWT.decode function . An attacker can bypass identity checks by exploiting the confusion between signature and encryption mechanisms in the token verification process.

How you could build such vulnerable application using this gem?
I don't think you can.
JWS decode output is Hash-like object, and JWE decode output is just an object including String payload.

@nov you will need to contest this CVE, otherwise it's going to stay in security advisory databases and people will keep asking for a patch.
https://nvd.nist.gov/general/FAQ-Sections/General-FAQs#faqLink4

this should be enough to prevent mixup of blank payload JWS w/ JWE.
https://github.com/nov/json-jwt/commit/9c4d842a9465bd7960570ca326c3de79b4abc9d0
otherwise, payload access will raise exception when JWE is given.

@nov I see that version 1.16.6 was released with the change to the logic. Should I update the CVE data in ruby-advisory-db and GHSA?


封了

推特把这个封了

CRITICAL:root:twint.run:Twint:Feed:noData'globalObjects

@AhmedShujaAbbasi fixed but caused by the limit
we only have 3200 tweets.

Thanks.. but i have another problem.
On Wed, Apr 26, 2023, 1:21 PM yihong @.***> wrote:

@AhmedShujaAbbasi https://github.com/AhmedShujaAbbasi fixed but caused
by the limit
we only have 3200 tweets.
—
Reply to this email directly, view it on GitHub
https://github.com/yihong0618/twint/issues/4#issuecomment-1522987428,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A35TGS7NGSWLOI7NHTE2G7LXDDLIZANCNFSM6AAAAAAXGKBSJA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Can you plz checkout once again
On Wed, Apr 26, 2023, 3:08 PM Shuja Abbasi @.***> wrote:

Thanks.. but i have another problem.
On Wed, Apr 26, 2023, 1:21 PM yihong @.***> wrote:

@AhmedShujaAbbasi https://github.com/AhmedShujaAbbasi fixed but caused
by the limit
we only have 3200 tweets.
—
Reply to this email directly, view it on GitHub
https://github.com/yihong0618/twint/issues/4#issuecomment-1522987428,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A35TGS7NGSWLOI7NHTE2G7LXDDLIZANCNFSM6AAAAAAXGKBSJA
.
You are receiving this because you were mentioned.Message ID:
@.***>

raise RefreshTokenException('Could not find the Guest token in HTML')
twint.token.RefreshTokenException: Could not find the Guest token in HTML

@hongqn
Since twitter block search for none login user
I recover it by using  timeline, but for now it limit 3200 tweets and can not search.
But anyway it works again

I also recover followers and following you can test.

Maybe we can do more things ~

Facing the same issues, CRITICAL:root:twint.run:Twint:Feed:noData'globalObjects and sporadically Could not find the Guest token in HTML. Issues still exist for me with the latest commit from this fork. My query is a single word.
Is it possible to use twint to log in with my Twitter account?

@LinqLover do not support for now.
twitter ban all search api if it is not login
try
twint -u LinqLover

Thank you. Unfortunately, for my project, I do need to do a full-text search on Twitter ...

for now it needs api or a login user...

Apparently, someone has commissioned to implement such a login feature on freelancer. Unfortunately, there is no information on whether someone is working on this project and whether they will publish their solution.

@yihong0618
pip install -U twint_fork
thanks it is working now. It will continue?

Now there won't be any problem?

CRITICAL:root:twint.run:Twint:Feed:noData-1
its giving me this error after running pip install -U twint_fork

yes it is dead again.

Can it be fixed again?

maybe just say that I will try.
And twitter ban another api....

@AhmedShujaAbbasi fixed


3D Polygon and Polyline annotation

I have noticed that the beta (online version) of this tool has an option to create 3D polygon/polyline annotation and segmentation as well. But we don't have that option in the current version (0.7.1) of this tool. Is there any possibility to install the beta version using the Docker method?

Hi @sarathsrk
These features are only available on the Cloud version.
Please contact me for the cloud and on-premises packages.
<EMAIL_ADDRESS>

Ok sure. Thanks


v3

[x]  Upgrade Babel to v7, Jest to v23.6 #775
[x]  Remove default polyfills, direct people to use CRA's #788
[x]  Add treeshaking in production #780 @thelarkinn
[ ] Optionally transpile node_modules with babel (like CRA does)
[x] Remove eslint and make it a plugin

@jaredpalmer what do you think the timeline is for v3?

Waiting for people to give feedback.

Do you have a suggested fix?

Fix for the second option? - not yet

@dan-lee can you submit a PR?

We upgrade one of our internal razzle app to thee alpha release, so far we don't have any mayor issue with it.
What I saw is the same warming message that @dan-lee already reported.

@olegreznichenko @jaredpalmer  there's already a PR for @babel/runtime: https://github.com/jaredpalmer/razzle/pull/845

I don't mind helping test out if possible. how do I go about setting up a new app with v3? can I use npx for it?

@jaredpalmer could we re-tag and include #845 ?

Waiting patiently for this version to be released!

Will cut a release later today

Just published a new alpha for those interested.

@jaredpalmer can you cut a new alpha version? I'm interested in the webpack-dev-server 3 piece. :) Thanks man.

Cutting a release right meow

Thanks @jaredpalmer, it works. I ran into some webpack import issue using react-loadable. Same issue that people are running into here:
https://github.com/webpack/webpack/issues/8656
and solved the issue by following this comment:
https://github.com/webpack/webpack/issues/8656#issuecomment-484134366

Ok, I converted my cra app to razzle 3, but tree shaking is not happening.  I can't find anything in the docs about it.  Is there something I need to configure?
Other than that, I am loving razzle 3!

@jlaustill same here, I fixed it by just adding sideEffects: ["*.css"] to my package.json.
but it must happen automatically, IDK why it behaves like this!


Get rid / unify poke front specific components

We currently have poke specific components, which are similar to sparkle ones. This require to maintain both, which doesn't make much sense.
Like PokeDataTable and stuff

sitrep?

Not there yet, there's still a bunch of stuff to implement in in sparkle to be able to fully get rid of front/components/poke/shadcn/.
Most of the work is on Table and DataTable as well as forms.


Web - Contact method - User can not access to verify modal, contact method is disabled.

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

Issue found when executing PR https://github.com/Expensify/App/pull/17678
Action Performed:

Go to NewDot and log in with expensifail account
Open Profile from Settings
Select contact method item
Add contact email ( can be email or phone number)
Click on it to procced to verification modal

Expected Result:
User can access to verify modal, contact method is enabled.
Actual Result:
User can not access to verify modal, contact method is disabled.
Workaround:
Unknown
Platforms:

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

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] Windows / Chrome
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
https://user-images.githubusercontent.com/93399543/234643068-9c96407b-bd73-441a-8e80-3e9a959c1b12.mp4
https://user-images.githubusercontent.com/93399543/234643089-4eb60729-5a1c-48bb-bee5-311078c37a0d.mp4
Slack conversation:
View all open jobs on GitHub

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Helping look into this since it may or may not be due to my PR :D

Weird, I'm not seeing this issue - I'm able to easily add new email contact methods, i'll see if I can add a phone number one next
https://user-images.githubusercontent.com/3885503/234823500-c2519b08-433c-46f9-9188-c1eb1a46308e.mov

Here's similar for phone number - I'm able to attempt to add the phone number contact method (it fails, which is expected since I'm not in the same country as that phone number's area code)
https://user-images.githubusercontent.com/3885503/234823918-44024a89-c426-421a-996b-71fce7cb3cd4.mov

I tried with the same phone number from the OP, saw the command to fail quickly (which is better than infinitely being disabled).
I am going to close this since this doesn't seem like a deploy blocker and I can't reproduce, @kbecciv do you mind testing again when you get the chance and reopening this if this is still a blocker for you? I wonder if we had a site slowdown around when you tested yesterday.

@Beamanator I tested this issue with expensifail account on build <IP_ADDRESS>., and contact method is disabled after added a secondary email log in.
Please check the video.
Credential<EMAIL_ADDRESS>https://user-images.githubusercontent.com/93399543/235265230-32b7eb62-a5fd-4117-b228-b481ba555269.mp4

@kbecciv that's super weird, I tried adding a contact method<EMAIL_ADDRESS>(just adding an extra 5 since the one you added has its own account apparently) and I quickly saw the option to enter a magic link 🤔
Can you try testing on v1.3.8-8 since that's the latest? Also can you let me know if you've been testing on good internet or pretty slow internet?

@Beamanator Issue reproductible in build <IP_ADDRESS>, attached the video.
https://user-images.githubusercontent.com/93399543/235662306-ba911eb3-0950-4e1b-ace3-26a300e7147f.mp4

Thanks @kbecciv - one more question for you, does that only happen with that one specific email address?
@bfitzexpensify have you been able to reproduce this at all? I'm adding the Needs Reproduction label because I can't seem to reproduce with any new contact method 🙃

Hm, no, I am not able to reproduce at all. Flow worked normally for me on staging with both an email address and phone number.

Same with me, @bfitzexpensify 🙃
Maybe we can wait to see if @kbecciv is only able to reproduce with that one specific email address... Oh also @kbecciv can you try adding that email address as a secondary login in OldDot?

Bump @kbecciv :D

@Beamanator Checking if I can reproduce it with latest build.

Issue is not reproduced on build <IP_ADDRESS>
https://user-images.githubusercontent.com/93399543/236953128-c2af79a0-c03c-400b-8b41-db0240428547.mp4


Minimum blocks in ledger to start effective lazy bootstrap

15,000,000 for live network
4,475,000 for beta network
Preventing start of lazy bootstrap on fresh node without launch flags

I think with the work in #1437 to fallback to legacy bootstrapping if not enough peers are helping to meet the goals that this is no longer needed


Feature: Add a healthcheck/system check endpoint

Add a way to poll the bot and see that it's alive and working (for example, to check after deployment is complete).

There's a status command now, so removed the status endpoint added.


URLs to online accounts break if the id/username is not the last part of the URL

What happened?
Social media services for which account URLs do not end with the username/id stored in Wikidata, Govdirectory will fail to produce a working URL.
The issue is because of the following line and affects major platforms like LinkedIn and Instagram.
https://github.com/govdirectory/website/blob/1106b32c9da97bb1daee75cf2c25154369bfb642/queries/account-data.rq#L23
What browsers are you seeing the problem on?
Other (describe above)

Do we have an example? I thought both LinkedIn and Instagram had the usernames in the end of the URL.

Example: https://www.govdirectory.org/sweden/Q33075406/
Technically they have a / at the end.
Rather than use SUBSTR/CONCAT to replace $1 we should use REPLACE.


Fix Issue #57 RuntimeError: Function 'CudnnConvolutionBackward' returned nan values in its 1th output.

Should be fixed with this change.

@richzhang would it be possible to accept this pull request? It seems people are getting the same NaN bug and this solves the problem


Cydia crashes when opening - iPhone 6s Plus 12.1.1

Open Cydia and the app crashes straight away. Any help? IOS 12.1.1 iPhone 6s Plus

Reinstalled cydia only and it works now

same issue here.
cydia works if u only choose 're-install cydia' in uncover.
but not tweaks working or showing in setting even if it shows installed correctly in cydia.


Catch error in packagin script and fail the build

Description

This PR is going to:

fail the build early if --use-timestamp is provided and working directory is not clean.
catch any potential error and fail the build (fix the regression added in<PHONE_NUMBER> (#2433))

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

GitHub Issue/PRs

Screenshots (if appropriate):
How Has This Been Tested?

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
Testing
[ ] I have added tests to cover my changes.
[ ] All relevant new and existing integration tests have passed.
 I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2032


Improve rpc server launch error diagnostic

Describe the feature
launching the RPC server(s) (ws, http for auth or regular) can fail if the address is already in use. The current error message makes this part clear, but does not provide any context about which server reth was trying to open a socket for.
Error: Address already in use (os error 98

We want meaningful error messages for this (most common) error.
We can add this via custom error types that wraps the jsonrpsee::Error and adds additional variants, for example:
#[derive(thiserror::Error)]
pub enum RpcError {
    #[error(transparent)]
    RpcError(jsonrpsee::core::Error),
    #[errr("")] // TODO
    AddressAlreadyInUse {
        error: io::Error,
        transport: (), // TODO add transport enum, WS,Http
        address: SocketAddr
    }
}

// we need a helper function here that converts the type and checks the `jsonrpsee::core::Error::Transport` variant for the io error and maps to AddressAlreadyInUse

Additional context
No response

Hi, I would like to give this a try if possible!

awesome,
if you have any questions please open a draft PR and we go from there


Use smaller dataset to testing csv-import/multi-map

Also reuse data already imported as blob by another test.

Current coverage is 87.62% (diff: 100%)

Merging #2609 into master will increase coverage by 0.01%

@@             master      #2609   diff @@
==========================================
  Files           240        240
  Lines         18025      18025
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          15791      15794     +3
+ Misses         1985       1982     -3
  Partials        249        249

Powered by Codecov. Last update 2582235...9bdc384


Raw password in payload of POST request when sign in

Even though the password gets sent via HTTPS isn't it a violation of Kerckhoff's Principle in that raw passwords are visible in the payload of POST requests when a user signs in via email? See below
https://polkadot-blockchain-academy.github.io/pba-book/cryptography/intro/page.html

Hii @ltfschoen
Raw password in payload request is fine. It is secured by https ssl encryption.
Only end user can see raw password.
Thankyou


feat: :sparkles: Add closeInside functionality to FwbDropdown component

This PR solve -> Dropdown closes when clicking inside the dropdown.
The dropdown is currently closing when you click inside it because of the onClickOutside function from @vueuse/core that is being used. This function is set to close the dropdown when a click is detected outside the dropdown. However, the FwbSlotListener component inside the dropdown is also triggering this function when clicked, causing the dropdown to close.  To prevent the dropdown from closing when clicking inside it, we can add a new property closeInside (default false) that prevents the onHide method from being triggered if this property is set to false.
Close: #99

LGTM


unclear where UserInteractionInstrumentation and XMLHttpRequestInstrumentation should be imported from.

Suggested improvements for page: https://opentelemetry.io/docs/languages/js/getting-started/browser/#add-instrumentations
As a starting point in OpenTelemetry, it is unclear where UserInteractionInstrumentation and XMLHttpRequestInstrumentation should be imported from.

thank you for your feedback @gilisho!
@open-telemetry/javascript-approvers please take a look

@gilisho thanks for pointing this out! Would you be interested in creating a PR with these changes? Something like this is probably what should get added into there.
npm install @opentelemetry/instrumentation-user-interaction \
  @opentelemetry/instrumentation-xml-http-request \

import { UserInteractionInstrumentation } from '@opentelemetry/instrumentation-user-interaction';
import { XMLHttpRequestInstrumentation } from '@opentelemetry/instrumentation-xml-http-request';

// code from earlier step

// Registering instrumentations
registerInstrumentations({
  instrumentations: [
    new DocumentLoadInstrumentation(), // from earlier
    new UserInteractionInstrumentation(),
    new XMLHttpRequestInstrumentation(),
  ],
});

Hey, sorry for the late reply. I'd love to contribute. will push a PR in the following days! 😄

@gilisho are you still interested in helping?

Hi, I've submitted the PR now. Thanks!

Hi, I've submitted the PR now. Thanks!

Thanks!


lxd/resources: Add GetNetworkState and GetNetworkCounters

Will be useful for external consumption by MAAS.
Also improves error handling slightly.
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

@tomponline @brauner should be good to go


Error after update to 1.4.1 -> 1.4.4

After updating to the new versions I get error's on all my charts. This is the error i get:
Apexchart Uncaught (in promise) TypeError: Cannot read properties of null (reading 'resetSeries')
For now, I had to roll back. Any suggestion how to fix this?

I'm also facing the same issue, have you found any solution for this?

Unfortunately not yet. I'll dive into it today

Same here... still not resolved. Had to rollback to 1.4.1


Initial

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.312%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
543

Relevant Lines:
558

💛  - Coveralls


[COM-51717, PXS-60201] Upgrade Scala and Java versions

This includes upgrading the following:

Java 8 -> Java 11
Scala 2.11 -> Scala 2.12
Scalaz -> Cats

I've switched to Scala 2.13 and made a new branch so this will be closed.


548 rsync exclude

exclude option in transfer-files now works. See unit test to learn how to use the option.
https://github.com/msk-mind/data-processing/blob/548-rsync-exclude/tests/data_processing/radiology/proxy_table/test_transfer_files.py#L79
As a consequence, TYPE_FILE_COUNT kvp is removed from the data ingestion template since files that are not needed can be excluded

Great this worked! A small risk is that if we don't exclude all file types that may exist in the nested folders, we could get a file count mismatch. I wonder if using --include is better, as it matches the logic of getting file_count (from specific file types) and including those file types in the transfer.

Great this worked! A small risk is that if we don't exclude all file types that may exist in the nested folders, we could get a file count mismatch. I wonder if using --include is better, as it matches the logic of getting file_count (from specific file types) and including those file types in the transfer.

Great point Doori! I have been ruminating about this and I think I finally got it to work and in a simple enough way where there is no room for human setup error. The interface only requires the include list now. Also now required and not optional. Everything else is excluded by default.
The only downside I see in this approach is it does not support the case where the files of interest have no extensions (but could possibly have naming patterns in which case we can use the patterns to include). In such a case we may want to possibly exclude files with extensions to minimize transfer load. But we can't apply such a logic since the interface does not support exclude in addition to include (that would be too complex and prone to human setup error). In any case, I would imagine that this usecase is highly unlikely. But something to be aware of.


Investigate bundle size and use more dynamic imports

If you run pnpm build we generate stats.html, which is bundle size info.  Here's what it looks like at the moment:

I've highlighted a few large modules we should consider importing dynamically vs. statically.  We've already done this for a few large modules, see https://github.com/search?q=repo%3Atarasglek%2Fchatcraft.org await import&type=code.
The modules highlighted above are for features of Mermaid diagrams and Katex math rendering.  Both of these are used in special cases, so we should consider loading the modules only when needed vs. every time.

love this...would also love to produce this as asset in github actions

Sure, we could put this stats.html page + Vite test coverage HTML on GitHub Pages or something.

When attempting to fix this I identified three large modules for dynamic importing:

elkjs (for Mermaid)
cytoscape (for Mermaid)
katex (for Math rendering)

The elkjs and cytoscape modules are both dependencies of mermaid:
The katex module is a dependecncy of two modules:

rehype-katex:
and micromark-extension-math (not directly imported in code):
...which itself is a dependency of remark-math (directly imported in code)

Full explanation available at https://github.com/tarasglek/chatcraft.org/pull/472
My findings:

elkjs and cytoscape can't be feasibly dynamically imported. At least with what I've tried, these can only be dynamically imported if mermaid is dynamically imported, but the mermaid package is always required., so it's not useful to dynamically import this. If there is a way to somehow dynamically import these dependencies from within mermaid

I tried dynamically importing the rehype-katex and remark-math packages in #472. These changes seem to work locally, but when deployed on the preview but there is a workbox-related issue preventing the app from loading. This can be revisited in the future if we can figure out the workbox-related issue.


c#-wrapper - Frame did not arrive in time!

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win10

Kernel Version (Linux Only)
-

Platform
PC

SDK Version
2.0

Issue Description
While debugging the cs-tutorial-1-depth-tutorial from the c#-wrapper an exception appears after some seconds. See:
System.Exception
HResult=0x80131500
Message=Frame did not arrive in time!
rs2_wait_for_frame(queue:000000001D8C0520)
Source=
StackTrace:

[Realsense Customer Engineering Team Comment]
hi @Tkong1,
could you please tell if RealSense Viewer also have this issue on your PC or only the C#-wrapper sample?
thanks.

hi @RealSense-Customer-Engineering ,
in RealSense Viewer after some seconds also an exception appears:
Oops, something went wrong!
RealSense error calling:
Unknown in rs2_close(sensor:000002568359BD60): profile not found
But the Error appears not always.

[Realsense Customer Engineering Team Comment]
hi @Tkong1,
since Realsense Viewer have issue, I think we should fix this before we move to C# wrapper issue..
would like to confirm before realsense viewer report error, do you see the D435 depth stream?
please also confirm your cable is USB3 certified.
thanks.

[Realsense Customer Engineering Team Comment]
hi @Tkong1,
do you still have this issue with latest release now?

[Realsense Customer Engineering Team Comment]
let me close this ticket here, please feel free to open new ticket if any follow question.


Draft implementation of sessions (via unix sockets) support

Sketch of #36 implementation.
In a nutshell:

If -s <SESSION> command-line option is provided in server mode (default one, w/o --kakoune or --request flag) then kak-lsp tries to bind unix socket under $TMPDIR/kak-lsp dir. Mode 0700 is set to directory. In case socket already exists kak-lsp tries to connect to it. If connection is successful, current instance just exits because server is already running. Otherwise it tries to remove dead socket and bind own.
--request mode interprets -s option as a destination. It doesn't try to start server if it's not running.
Integration with Kakoune basically looks like:

%sh{kak-lsp --kakoune -s $kak_session}
lsp-start

lsp-start is just a generated wrapper forking kak-lsp with the same session and diverting output to /dev/null, should be replaced with custom copy to have proper logging (like nop %sh{ (kak-lsp -s $kak_session)  > /tmp/kak-lsp.log 2>&1 < /dev/null & }).

Timeout defaults to 30 minutes and could be set via kak-lsp.toml or -t <TIMEOUT> command-line option. If kak-lsp doesn't receive any requests during timeout time it exits.

Technically Windows does support Unix sockets these days, but support is probably not nearly widespread-enough to be usable from Rust.
I haven't looked at the code yet, but from your description it sounds like a good start.

I haven't had a chance yet and it will likely be awhile until I have enough time to do so; feel free to ignore windows for the moment. Thanks :)

Thanks folks, I'll merge it then and cut new release to start gathering feedback.


Add guide to set an Gelato relay

Similar to Add guide to set an OpenZeppelin relay#85 and after https://github.com/semaphore-protocol/boilerplate/issues/44
Create a guide

Hi @aguzmant103, @vplasencia! I'm interested in this Gelato issue and would like to request an assignment.
Could you clarify the remaining tasks? Thanks!

Hi @aguzmant103, @vplasencia! I'm interested in this issue and would like to request assignment.
Could you clarify the remaining tasks for this issue? Any additional context would be appreciated. Thanks!


BasicCodingWpf - setting the environment variable to Develompent causes an exception

created a new simple project for testing; the app run without problems;
searching for the bug in progress

solving


Added validation for checking duplicate dictionary include/ exclude fields

Added validation for checking duplicate dictionary include/ exclude fields

If a same column is provided more than once in either DICTIONARY_INCLUDE or DICTIONARY_EXCLUDE, consider it only once and continue. No need for fail the create cube ddl.

This validation is not required


Capture broadcasting deps in fusion

@rjzamora I'd appreciate if you could take a look here, I am not too happy with he solution I found.
Background: Our fusion is not aggressive enough which results in a pegged scheduler for the tpch benchmarks on 1TB, this will get way worse if we re-run for 10TB. This PR achieves the same level of blockwise fusion that we have in dask/dask

Thanks! I'll definitely look through this today.


Update Archive button and link

Please change the name of the button to: "Watch the Recordings"
And the link to: https://streameth.org/archive?event=evm_summit
Also, switch it with "Learn More" to make this the first button.
@hugo-dc @gumb0
https://github.com/ipsilon/evmsummit.org/blob/cb81f912ffa0cb06e320beba4376e2bfc53e6c47/index.html#L104

PR: https://github.com/ipsilon/evmsummit.org/pull/39


Add os.ModeExecutable

What version of Go are you using (go version)?
go version go1.9 linux/amd64
What did you do?
Tried to determine if a file is executable
info, _ := os.Stat(file)
isExecutable := info.Mode()&os.ModeExecutable == 0

What did you expect to see?
os.ModeExecutable to equal 0111
What did you see instead?
os.ModeExecutable is not defined.

Executable for who?
We also don't have ModeReadable and ModeWritable, so why just executable?

@bradfitz makes sense


Use dirname(@FILE) instead of Pkg.dir

This allows installing the package elsewhere.
Add testing against 0.5 to Travis - this runs the most
recent RC now, release once final tags are done.

Coverage decreased (-14.03%) to 85.97% when pulling df71e8ec95291a4faabc9e451bc6681f61bbeb8f on tkelman:nopkgdir into e35d90d180fd0aeabbe3ab717d440f1cff749cea on BenLauwens:master.

Current coverage is 100% (diff: 100%)

Merging #19 into master will not change coverage

@@           master   #19   diff @@
===================================
  Files           9     9
  Lines         344   344
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits          344   344
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update e35d90d...df71e8e


Process memcycle is a responsibility of report error

Make pretty-printing a dependency cycle a responsibility of the Report_error module instead of Build_system.
It's weird to have build_system.ml responsible for this bit of error handling. It should either live in Memo, which is producing the error and has sufficient knowledge to pretty-print it, or in Report_error, as this PR does.

The extra backtraces next to dependency cycle errors are expected.
They were being dropped by the process_memcycle function, probably accidentally by dropping the Memo.Error.E wrapper.
If we don't like them, then we should adjust the logic around let memo_stack in report_error.ml instead of doing this confusing trick.


Support id/class in built-in components

Hello, currently some of the components support id/class like the form components.
I'd like to propose that these be supported in all the built in components where it makes sense.
I am primarily interested in id which is useful for anchor targeting (Some panel). It makes it possible to have links that scroll to a particular card or chart. For components that have a top level container, the id can be added to the container, and for those that don't have it can be added as a separate anchor.
class is nice to have for styling convenience.
Hope this feature is acceptable. Happy to revise if you have any suggestions.

Hi @lovasoa - I have added the docs and updated as per above comments.


Consider renaming 'build' and 'buildDocker'

As a new user ‘build’ and ‘buildDocker’ are not easy to differentiate in terms of what they do.

Decided rename buildDocker to buildToDockerDaemon

+1 to renaming to dockerBuild since that makes it clearer we are using docker


[Question]: 可以生成arm64的镜像发布到docker hub吗？

Is your question not already answered in the FAQ?

[X] I made sure the question is not listed in the FAQ.

Is this a general question and not a technical issue?

[X] I am sure my question is not about a technical issue.

Question
我想要一份arm64架构的镜像，在我的rk3588上运行

Duplicate of #103

1.14之前的版本都有arm64架构的，为什么最新的没有了呢？？


Doesn't enter a game

Not join game... (last version MOgar-edited)

client sided.
make sure ports are linked and server is open
make sure you are not signed into facebook/google

thx (facepalm) i know...

How do i get the yellow rings like the one in agar.io party


Order of precedence for environment variables

This is a Feature Request
The order of precedence for environment variables is not documented in [Define Environment Variables for a Container] page.
What would you like to be added
The order of precedence for environment variables is as follows:

Keys in env field
Keys in envFrom field
Keys defined in the container image

Why is this needed
it is important to know the precedence for environment variables
Comments

/language en
/assign

page need to be updated: https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/

I want to raise a PR if triage accepted.

/sig docs
/priority awaiting-more-evidence.

/priority awaiting-more-evidence

I was just looking for the information, couldn't find it on the mentioned page. The information would be immensely helpful to design Kustomize overrides for deployments.

@Erbureth
Precedence of environment variables are modified by mutating admission webhook.
Reference:
https://github.com/kubernetes/kubernetes/issues/122950#issuecomment-1938903330

The precedence is modified by admission webhook.
/close


[Relax][VM] Refactor CUDA graph builtins as VM extension

This PR introduce VM extension, which allow users to define target related runtime extensions. The VM holds the reference to the extension once created to ensure it is destructed at VM destruction.
CUDA graph builtins are refactored as VM extension to make the cuda graph cache per-VM instead of per-thread, to allow VM to be run on different threads (non-concurrently).
This PR need rebase after #16815
cc @tqchen

@vinx13 let us disable the failed hexagon test first, since it seems to be a flaky one


feat: script for reporting openshift access

Script:

scrubs all projects a user has access to
lists all projects and that user's rights
where possible, list other users and their rights

Count one user's projects:
oc projects | egrep "^.*-.*(.*)$" | wc -l

It's not obvious where this script should be committed, so a copy has been attached.  Rename the extension to .sh.
rights_reporter.txt


Unable to build Swift Algorand SDK in apple M1 processer

Version
Swift Algorand SDK Version - Latest 1.1.0
Xcode version - Version 13.2.1
iPhone simulator - iOS 15.2
Problem
When doing Xcode project build Algorand SDK showing missing import message. I have posted the error message billow.
Could not find module swift algorand sdk' for target x86_64-apple-ios-simulator: found: arm64,
arm64-apple-ios-simulator, at: /Users/madushansenavirathna/Librarv/Developer/Xcode/DerivedData
PagoWallet-evpbpapxecehakezlwvedywaomtm/Build/Products/Debug-iphonesimulator
swifT_algorand_sak.swintmodule

This project run with apple M1 silicon processor default Xcode excluded architecture coming with arm64 also added x86_64 for project targets and the SDK targets but remaining the same issue.
Change Build Settings > Excluded Architectures >
Debug : x86_64 arm64
          Any iOS Simulator SDK : x86_64 arm64
Release:  x86_64 arm64
          Any iOS Simulator SDK : x86_64 arm64

Also we Changed User-Defined from Targets > Build Settings
Targets > Build Settings > User-Defined added Valid_ARCH
Valid_ARCH:  arm64 armv7 i386 x86_64
         Release: arm64 armv7 i386 x86_64
         Debug: arm64 armv7 i386 x86_64

Finally we tried to build XCFramework combine  with x86_64 and arm64 binaries but this Swift Alfgorand SDK only supporting Swift Package Manger
Please  give us any suggestion to resolve this problem combine with two binaries by using XCFramworks in CoCoapods or if you can resolve this issue or update this library from your side let us know.
Thank you.

hi @MadushanSenavirathna, while we double check this particular situation can you please try Cocoapods? We've added support to it in latest release.
Asking this since I'm also using a M1 processor (with no need to exclude any architecture at all) and have zero issues compiling it.
Also I'm not sure what you mean with this:

Please give us any suggestion to resolve this problem combine with two binaries by using XCFramworks in CoCoapods

@MadushanSenavirathna pod "swift-algorand-sdk" should do the trick :)


Update tail docs to match built-in docs

Default value for tail helps me remember it's not a switch, but requires a value. This change makes it match the built-in docs.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Much appreciated, @ryansanford !


Vercel Blob onBeforeGenerateToken clientPayload Type issue?

Let me preface with I am relatively new to Typescript (and web development in general), so please help me understand if I am doing something wrong.
That being said, it looks like the type for the optional clientPayload param of onBeforeGenerateToken, which is currently set to string | null should be updated to string | undefined.
The docs say that you should pass a string to this optional parameter. When I take the Vercel code as a starting point (below), and then uncomment the line that reads clientPayload?: string, I get a Typescript error: Type 'null' is not assignable to type 'string | undefined'.ts(2322).
I was able to fix the Typescript error by updating the type for clientPayload from string | null to string | undefined.
To my knowledge, this should work fine because, at least in my case (I understand other people may have other instances where this wouldn't make sense?), I would never pass a null clientPayload... I either have a payload to pass or I don't, in which case it would be undefined.
Perhaps my "solution" creates additional problems. If so, please share! If the types were defined this way for a reason, and I am just doing something wrong... please share! 😆
onBeforeGenerateToken: async (
        pathname: string,
        clientPayload?: string, <--- when I remove the comment from this line, Typescript gets mad, until I change the type to string | undefined.
      ) => {
        // Generate a client token for the browser to upload the file
        // ⚠ Authenticate and authorize users before generating the token.
        // Otherwise, you're allowing anonymous uploads.

        // ⚠ When using the clientPayload feature, make sure to valide it
        // otherwise this could introduce security issues for your app
        // like allowing users to modify other users' posts

        return {
          allowedContentTypes: ['image/jpeg', 'image/png', 'image/gif'], // optional, default to all content types
          // maximumSizeInBytes: number, optional, the maximum is 5TB
          // validUntil: number, optional, timestamp in ms, by default now + 30s (30,000)
          // addRandomSuffix: boolean, optional, allows to disable or enable random suffixes (defaults to `true`)
          // cacheControlMaxAge: number, optional, a duration in seconds to configure the edge and browser caches.
          tokenPayload: JSON.stringify({
            // optional, sent to your server on upload completion
            // you could pass a user id from auth, or a value from clientPayload
          }),
        };
      },

Hey @luismeyer,
Thanks for the quick reply! Deleting the type annotation doesn't seem to do anything either (I had already tried that and forgot to mention it in my original post). This just creates a different Typescript error: Type 'null' is not assignable to type 'string'.ts(2322)

no, I meant deleting the types completely, also the string. This will always infer the type the SDK provides.


[pod-spec] prometheus_scrape_unit_address may be set to None

Bug Description
For pod-spec charms, the MetricsEndpointProvider may return None to prometheus_scrape_unit_address on:
    def _set_unit_ip(self, _):
...
        for relation in self._charm.model.relations[self._relation_name]:
            relation.data[self._charm.unit]["prometheus_scrape_unit_address"] = str(
                self._charm.model.get_binding(relation).network.bind_address
            )

Juju will only return an IP when the application pod defined by the pod-spec starts. That can cause race conditions where prometheus-related events happen before others and the application pod is not yet created. One possible fix is to check if the bind_address is set to None and raise an exception and defer the event on _set_scrape_job_spec method:
    def _set_scrape_job_spec(self, event):
...
        try:
            self._set_unit_ip(event)
        except PrometheusProviderBindAddressNotAvailable as e:
            logger.warning(
                "Prometheus relation bind address not available",
                e.message,
            )
           event.defer()
           return

...

    def _set_unit_ip(self, _):
...
        if not self._charm.model.get_binding(relation).network.bind_address:
            raise PrometheusProviderBindAddressNotAvailable()
        for relation in self._charm.model.relations[self._relation_name]:
            relation.data[self._charm.unit]["prometheus_scrape_unit_address"] = str(
                self._charm.model.get_binding(relation).network.bind_address
            )

That would allow _set_scrape_job_spec to defer the event until the pod is ready.
To Reproduce

juju deploy ch:argo-controller
juju deploy ch:minio
juju deploy ch:prometheus-k8s --channel=latest/edge
juju add-relation argo-controller prometheus-k8s
Argo-controller will not yet be ready to spin up the application container as minio relation is not set yet, prometheus will receive prometheus_scrape_unit_address=None

Environment
microk8s v1.21
juju v2.9.28
Relevant log output
$ juju show-unit prometheus-k8s/0
prometheus-k8s/0:
  opened-ports: []
  charm: local:focal/prometheus-k8s-0
  leader: true
  relation-info:
  - endpoint: prometheus-peers
    related-endpoint: prometheus-peers
    application-data: {}
    local-unit:
      in-scope: true
      data:
        egress-subnets: <IP_ADDRESS>/32
        ingress-address: <IP_ADDRESS>
        private-address: <IP_ADDRESS>
  - endpoint: metrics-endpoint
    related-endpoint: metrics-endpoint
    application-data:
      alert_rules: '{"groups": [{"name": "argo_62a27dd7-6426-4fc4-85ba-4470c63f53e0_argo-controller_argo-controller_unit_unavailable_alerts",
        "rules": [{"alert": "ArgoUnitIsUnavailable", "expr": "up < 1", "for": "0m",
        "labels": {"severity": "critical", "juju_model": "argo", "juju_model_uuid":
        "62a27dd7-6426-4fc4-85ba-4470c63f53e0", "juju_application": "argo-controller",
        "juju_charm": "argo-controller"}, "annotations": {"summary": "Argo unit {{
        $labels.juju_model }}/{{ $labels.juju_unit }} unavailable", "description":
        "The argo unit {{ $labels.juju_model }} {{ $labels.juju_unit }} is unavailable
        LABELS = {{ $labels }}\n"}}]}]}'
      scrape_jobs: '[{"metrics_path": "/metrics", "static_configs": [{"targets": ["*:9090"]}]}]'
      scrape_metadata: '{"model": "argo", "model_uuid": "62a27dd7-6426-4fc4-85ba-4470c63f53e0",
        "application": "argo-controller", "unit": "argo-controller/0", "charm_name":
        "argo-controller"}'
    related-units:
      argo-controller/0:
        in-scope: true
        data:
          prometheus_scrape_unit_address: None
          prometheus_scrape_unit_name: argo-controller/0
  provider-id: prometheus-k8s-0
  address: <IP_ADDRESS>

### Additional context

One possible work-around is to remove and re-add the prometheus relation after the pod started.

I can confirm this bug.
As suggested deferring the relation-joined event in MetricsEndpointProvider may be a valid way to fix this issue. However the semantics of Operator Framework's event.defer() effectively implies that events generated after the deferred event may still execute prior to the completion of the deferred event. Hence I would like to explore a solution (if possible) that avoids deferring the event.
In the case of side car charm the simplest fix would be to just not set a unit IP address if the workload container has not yet been started. This is because when the workload container starts it will receive a pebble-ready event in response to which the MetricsEndpointProvider will set unit IP as seen in its __intit__() method
for container_name in charm.unit.containers:
            self.framework.observe(
                charm.on[container_name].pebble_ready,
                self._set_unit_ip,
            )

This will trigger a relation-changed event for the MetricsEndpointConsumer and that should result in the correct scrape target.
However a fix may still be needed to MetricsEndpointConsumer since it should not have set a scrape target with none as the IP address. Perhaps MetricsEndpointConsumer should validate the IP address it has received from MetricsEndpointProvider. This validation may be done in the _relation_hosts() method of MetricsEndpointProvider. It may be sufficient to log a warning and just drop any invalid address here.
Finally the last part of the solution that does need some exploring is what additional events can MetricsEndpointProvider bind the _set_scrape_job_spec() to so that pod spec charms do forward updated scrape target information to Prometheus when their pods have started successfully. The selected event must be such that it does not cause a regression for sidecar charms and yet provides a valid unit address for pod-spec charms.

I don't think relation_joined will work reliably for pods that churn.
Also, about the following:

when the workload container starts it will receive a pebble-ready event
in response to which the MetricsEndpointProvider will set unit IP as seen
in its intit() method

AFAIK Pod Spec charms do NOT have pebble inside, so no pebble_ready is
fired.
On Mon, Apr 25, 2022 at 11:32 AM Balbir Thomas @.***>
wrote:

I can confirm this bug.
As suggested deferring the relation-joined event in
MetricsEndpointProvider may be a valid way to fix this issue. However the
semantics of Operator Framework's event.defer() effectively implies that
events generated after the deferred event may still execute prior to the
completion of the deferred event. Hence I would like to explore a solution
(if possible) that avoids deferring the event.
In the case of side car charm the simplest fix would be to just not set a
unit IP address if the workload container has not yet been started. This is
because when the workload container starts it will receive a pebble-ready
event in response to which the MetricsEndpointProvider will set unit IP
as seen in its intit() method
for container_name in charm.unit.containers:
self.framework.observe(
charm.on[container_name].pebble_ready,
self._set_unit_ip,
)
This will trigger a relation-changed event for the MetricsEndpointConsumer
and that should result in the correct scrape target.
However a fix may still be needed to MetricsEndpointConsumer since it
should not have set a scrape target with none as the IP address. Perhaps
MetricsEndpointConsumer should validate the IP address it has received
from MetricsEndpointProvider. This validation may be done in the
_relation_hosts() method of MetricsEndpointProvider. It may be sufficient
to log a warning and just drop any invalid address here.
Finally the last part of the solution that does need some exploring is
what additional events can MetricsEndpointProvider bind the
_set_scrape_job_spec() to so that pod spec charms do forward updated
scrape target information to Prometheus when their pods have started
successfully. The selected event must be such that it does not cause a
regression for sidecar charms and yet provides a valid unit address for
pod-spec charms.
—
Reply to this email directly, view it on GitHub
https://github.com/canonical/prometheus-k8s-operator/issues/262#issuecomment-1108324122,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADK675TYQU35UU4H5JQGVOTVGZRCXANCNFSM5UFE3PVA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

AFAIK Pod Spec charms do NOT have pebble inside, so no pebble_ready is fired.

Indeed, hence I mentioned "Finally the last part of the solution that does need some exploring is what additional events ...".

AFAIK Pod Spec charms do NOT have pebble inside, so no pebble_ready is fired.

Indeed, hence I mentioned "Finally the last part of the solution that does need some exploring is what additional events ...".

You see, I do not understand why would you change something that does work for workload containers that do have pebble ;-)

You see, I do not understand why would you change something that does work for workload containers that do have pebble ;-)

I think I am in total agreement with you here. I would not like to change the workflow for containers that have pebble. Hence I intend to explore if it is possible to bind an additional event that will not break the workflow for sidecar charms but additionally make it work for pod spec charms.

The only way we can reasonably solve this for PodSpec charms is to hook onto update-status, doing nothing until the IP is no longer None. Deferring is not a reasonable option, and there is no consistent event we can rely on that is even remotely equivalent to pebble-ready.

Hi, I've discussed this bug with @simskij. The main concern is to avoid deferring an event within the prometheus lib.
The two alternatives we discussed are: (1) as @simskij pointed out, the library could listen to more events, such as update-status or config-changed and use the _set_unit_ip to only set the IP when these events happen; or (2) create an event specific to no-ip-found, in this case, the main charm will have to listen to that event.
The main point with (2) is that it will demand an extra interface on the library, e.g. refresh method, that allows to inform the IP once it has been set.

@phvalguima There is now PR 268 that hopefully address this issue. Any feedback you may provide regarding if this feedback effectively resolves your issue will be very helpful. I am waiting on integration tests to run and trying to follow the steps you provided in "Steps to reproduce" locally now.

@phvalguima I am unable to add a relation between argo-controller (deployed from charmhub edge channel) and prometheus-k8s build using PR #268.
$ juju deploy argo-controller --channel edge
Located charm "argo-controller" in charm-hub, revision 59
Deploying "argo-controller" from charm-hub charm "argo-controller", revision 59 in channel edge on focal
ERROR cannot add application "argo-controller": state changing too quickly; try again soon

Is there any particular revision you would suggest ? Stable and beta do not seem to support the Prometheus charm's metrics-endpoint relation.
$ juju relate argo-controller prometheus-k8s
ERROR no relations found
``

Hi @phvalguima I can confirm PR #268 does indeed fix this issue. Here is the juju status
$ juju status --relations
Model  Controller  Cloud/Region        Version  SLA          Timestamp
lma    microk8s    microk8s/localhost  2.9.29   unsupported  13:28:59+01:00

App              Version                Status   Scale  Charm            Channel  Rev  Address         Exposed  Message
argo-controller                         blocked      1  argo-controller             0                  no       Waiting for object-storage relation data
minio            res:oci-image@1755999  active       1  minio            stable    57  <IP_ADDRESS>  no
prometheus-k8s                          active       1  prometheus-k8s              0  <IP_ADDRESS>   no

Unit                Workload  Agent  Address      Ports     Message
argo-controller/0*  blocked   idle                          Waiting for object-storage relation data
minio/0*            active    idle   <IP_ADDRESS>  9000/TCP
prometheus-k8s/0*   active    idle   <IP_ADDRESS>

Relation provider                 Requirer                         Interface          Type     Message
argo-controller:metrics-endpoint  prometheus-k8s:metrics-endpoint  prometheus_scrape  regular
prometheus-k8s:prometheus-peers   prometheus-k8s:prometheus-peers  prometheus_peers   peer

And here is the juju show-unit output
$ juju show-unit argo-controller/0
argo-controller/0:
  opened-ports: []
  charm: local:kubernetes/argo-controller-0
  leader: true
  relation-info:
  - relation-id: 1
    endpoint: metrics-endpoint
    related-endpoint: metrics-endpoint
    application-data: {}
    related-units:
      prometheus-k8s/0:
        in-scope: true
        data:
          egress-subnets: <IP_ADDRESS>/32
          ingress-address: <IP_ADDRESS>
          private-address: <IP_ADDRESS>

Also there is no scrape target for argo-controller in the Prometheus config file
global:
  scrape_interval: 1m
  scrape_timeout: 10s
  evaluation_interval: 1m
rule_files:
- /etc/prometheus/rules/juju_*.rules
scrape_configs:
- job_name: prometheus
  honor_timestamps: true
  scrape_interval: 5s
  scrape_timeout: 5s
  metrics_path: /metrics
  scheme: http
  follow_redirects: true
  static_configs:
  - targets:
    - localhost:9090
- job_name: juju_lma_938fb387-bf33-48b8-8ead-3daa04fc7c94_argo-controller_argo-controller_prometheus_scrape
  honor_labels: true
  honor_timestamps: true
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  follow_redirects: true
  relabel_configs:
  - source_labels: [juju_model, juju_model_uuid, juju_application]
    separator: _
    regex: (.*)
    target_label: instance
    replacement: $1
    action: replace

After adding a relation between argo-controller and minio , the Prometheus charm then does get a valid scrape target for argo-controller.  Screenshot is attached. Note however in the attached screenshot Prometheus is still not able to scrape from the argo controller because it is getting a "permission denied" error.


TextFormField fails to switch to the correct keyboard when switching from single to multiline

When moving the selection between two text fields one single line with the 'text' keyboard and a multiline textfield, the keyboard isn't correctly updated. Only tested this on iOS.
Steps to Reproduce
Open the Gallery app and open the text fields example. Toggle between a multiline textfield (e.g. Life story) and a standard single line (e.g. Name). The keyboard doesn't change until a key on the keyboard is pressed.

[✓] Flutter (Channel master, v0.5.2-pre.18, on Mac OS X 10.13.4 17E202, locale en-US)
    • Flutter version 0.5.2-pre.18 at /Users/vik/Projects/flutter
    • Framework revision 758711c85d (8 hours ago), 2018-05-31 10:33:15 +0200
    • Engine revision d174c4ff01
    • Dart version 2.0.0-dev.59.0.flutter-ff815d05a5

[!] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/vik/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)
    ✗ Android license status unknown.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.3.1, Build version 9E501
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    • Dart plugin version 171.4424
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)

[✓] Android Studio (version 2.3)
    • Android Studio at /Applications/Android Studio - old.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] IntelliJ IDEA Community Edition (version 2017.2.5)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 20.0.2
    • Dart plugin version 172.4343.25

[✓] Connected devices (1 available)
    • iPhone 6 • 5DE7BCCC-8793-413A-9924-3D413DE12FCD • ios • iOS 9.0 (simulator)

! Doctor found issues in 1 category.

Would probably be easy to fix this together with #18072

@vlidholt I'm looking at the code. Can you let me know where I can find TextFormInput? I only see TextFormField. I'm new to Flutter. Thank you!

@thphuc my bad updated to the right class name :)

I am able to reproduce this. Interestingly, as soon as there is actual text in the "Name" field the keyboard changes as expected when switching focus between Name and Life Story.

Looks like this issue is still present, but interesting is that it works fine in the simulator...

Is this Bug still bugging you or Closed?? Because, i find  a solution for a similar case!

Hi @vlidholt
Testing on flutter gallery form latest stable channel.
Keyboard switches without pressing on the keyboard in the simulator

flutter doctor -v
[✓] Flutter (Channel stable, v1.12.13+hotfix.9, on Mac OS X 10.15.4 19E287,
    locale en-GB)
    • Flutter version 1.12.13+hotfix.9 at /Users/taha/Code/flutter_stable
    • Framework revision f139b11009 (4 weeks ago), 2020-03-30 13:57:30 -0700
    • Engine revision af51afceb8
    • Dart version 2.7.2

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.44.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.1

[✓] Connected device (1 available)
    • iPhone 11 • 41EB2A85-7EB4-4FD2-8978-FBBE2A681D74 • ios •
      com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)

• No issues found!

if you're still experiencing this problem, please create a new issue and provide the information
required in the template.
Thank you


Fix for issue #231 - Problem with Timestamp.getDaysInMonthBound

This is a fix for the issue #231, a problem with Timestamp.getDaysInMonthBound.

There are a few issues with this pull request. The basic fix looks fine, but there is also a change to an unrelated file, alot of irrelevant commits and we're missing the release notes. See further PR #233


[docker] - update netutils image

Status
Ready/In Progress/In Hold (Reason for hold)
Related Content Pull Request
Related PR: link to the PR at demisto/content
Related Issues
Related: link to the issue
Description
added aiohttp, fastapi, uvicorn to the image

did we ignore this script for the native images currently out in content?

No changes to native image is needed, as the added package is already there (aiohttp)


¿Hook useIsFetching not Working?

I am trying to use this hook to show the buttons in loading mode, the problem is that what throws the hook is always false, and does not capture the first load and does not refetch them,
Are there any restrictions on this hook? o Should there be additional configuration?
Am I misunderstanding the meaning? o Do I have any erroneous configuration?
The isLoading does work correctly, but the global does not.
This is my _app with the provider.
// _app.tsx
 <StoreProvider store={store}>

                    <ThemeProvider theme={creatorCommerciTheme()}>

                        <CssBaseline/>

                        <ReactQueryConfigProvider>

                            <AppLayout type={AppRoles.Admin}>
                                <AnimatePresence exitBeforeEnter>

                                    <Component {...pageProps} key={router.route}/>

                                </AnimatePresence>

                            </AppLayout>
                        </ReactQueryConfigProvider>

                    </ThemeProvider>
</StoreProvider>

And this is one of my queries with a personalized hook.
// useCustomer.tsx
interface UseCustomerProps {
   id?: string | number;
}
export const useCustomerKey = 'UseCustomerGetCustomer';

function useCustomer(props: UseCustomerProps) {
   const customerApi = new CustomersAPI();
   return useQuery(
       [useCustomerKey, {id: props.id}],
       (args) => customerApi.getOneCustomer(args.id)
   );
}

// [cid].tsx
const CID = router.query.cid as string;
    const uiActions = useStoreActions((actions) => actions.ui);
    const ui = useStoreState((state) => state.ui);

    const {data: customer, isFetching, isLoading} = useCustomer({
        id: CID,
    });

Here I try to print the status of isFetching
// Form.tsx
const isFetching = useIsFetching();
const [mutate, { isLoading, error  }] = useUpdateCustomer();
console.log(isFetching); // ever false in loading o windows focus or mutation false false false false false

I need something more? Thank you very much c:
I use nextjs if they need extra information to replicate the problem can you tell me. I wanted to keep an eye on him but time consumes me so I will leave him here and I hope to be the only one that happens to him (hopefully it is my mistake)
LastVersion -- Jejejej

Mutations do not affect useIsFetching, which is meant to know if any useQuery instances are fetching. Mutation's come with their own state via const [mutate, { isLoading }] = useMutation(...).

If you still believe this is an issue, please create a new codesandbox with the least amount of code possible to replicate the issue.

Hi @tannerlinsley, I have noticed the same problem.
In this code sandbox, you can see that the global isFetching is always false:
https://codesandbox.io/s/nervous-knuth-ijple?fontsize=14&hidenavigation=1&theme=dark

I’ll look into this
Tanner Linsley
On Dec 5, 2019, 8:17 AM -0500, Julian Wachholz<EMAIL_ADDRESS>wrote:

Hi @tannerlinsley, I have noticed the same problem.
In this code sandbox, you can see that the global isFetching is always false:
https://codesandbox.io/s/nervous-knuth-ijple?fontsize=14&hidenavigation=1&theme=dark
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

This should be fixed in the latest version

Thank you! That was super fast. The sandbox works now, too! :smile:

😉😁


feat: onboarding add pin extension screen

Describe the changes you have made in this PR
Add a PIN extension screen as last step of onboarding.
Link this PR to an issue
Fixes #2343
Type of change

feat: New feature (non-breaking change which adds functionality)

Screenshots of the changes [optional]

How has this been tested?
Manually
Checklist

[x] My code follows the style guidelines of this project and performed a self-review of my own code
[x] New and existing tests pass locally with my changes
[x] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

I added code to detect dark mode browser setting, taken from utils/index.ts getTheme which should detect a users settings
window.matchMedia("(prefers-color-scheme: dark)").matches
I changed my Chrome browser setting to dark mode. The welcome screen appears dark, but the mechanism to detect it as taken from getTheme does not work. I wonder why the rest of the screen still appears dark, if the code has no effect.
Anyways, if the code in getTheme does not work, I think it's a different issue. What do you think @reneaaron ?

@lujakob You are on :fire:, great job!
Just tested it and worked fine for me. :muscle: Some minor things I noticed during testing:

[ ] The images are quite small (you could add the full size images in the original issue or downsize them to the biggest size they can be displayed)
[ ] Shadows and/or rounding of the box seems a bit off, could you please double check that with the designs?

Will continue with the code review probably later today / tomorrow, but looks quite good!

@lujakob You are on 🔥, great job!
Just tested it and worked fine for me. 💪 Some minor things I noticed during testing:

[ ]  The images are quite small (you could add the full size images in the original issue or downsize them to the biggest size they can be displayed)
[ ]  Shadows and/or rounding of the box seems a bit off, could you please double check that with the designs?

Will continue with the code review probably later today / tomorrow, but looks quite good!

I overlooked the width class on the image when copy/pasting. I increased it now to w-80. I found the next size w-96 too big in proportion to the rest of the content. If you think it is still to small, please test w-96 and let me know.
I copy pasted the component from SetPassword component which does not have rounded corners and shadow. I applied them to the PinExtension and also to SetPassword to have it consistent.
I also added the puzzle icon. I think it fits quite well. (didn't notice it on the current component where it is already used)
I also added the "Alby" icon on point "3." - what do you think?

@reneaaron Thanks for reviewing. I resolved all issues.

2 little nitpicks, other than that: 💯
Thanks also for taking the time to rename some functions and introducing a new useTheme hook. 💪
tACK

Sounds good. I updated.

Just tested another time, added some fixes regarding spacing. Great job! 💪
tACK

Thanks for reviewing 🙏

I removed the onboarding card now too, since those are kind of duplicate otherwise. cc @stackingsaunter