[bugfix]fix using deepEqual incorrectly

Now we use the following statement to indicate whether overrides are updated.
needsUpdate := !equality.Semantic.DeepEqual(overrides, currentOverrides)

But overrides's type is overridesMap, whereas currentOverrides is a slice. So needsUpdate is always true which may lead to some useless updates.
BTW, I discovered that the resource had this event when I created the resource but did not associate the overrides policy which made me feel strange.
updated overrides according to override polic(ies)

After I deep into the codes, I found this mainly happens when fedobject needs to be updated. It has two situations:

override policy updates
pending annotation updates, e.g. we found no ops and removed the override-policy from pending controllers.

In the latter situation, event information is inaccurate. What do you think? /cc @gary-lgy @limhawjia @mrlihanbo

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (2c3b898) 28.54% compared to head (9fe3137) 28.53%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #256      +/-   ##
==========================================
- Coverage   28.54%   28.53%   -0.01%
==========================================
  Files         113      113
  Lines       13513    13523      +10
==========================================
+ Hits         3857     3859       +2
- Misses       9273     9282       +9
+ Partials      383      382       -1

Flag
Coverage Δ

unittests
28.53% <75.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

pkg/controllers/override/util.go
72.15% <100.00%> (+1.50%)
:arrow_up:

.../controllers/override/overridepolicy_controller.go
0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes

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

BTW, I discovered that the resource had this event when I created the resource but did not associate the overrides policy which made me feel strange.
updated overrides according to override polic(ies)

After I deep into the codes, I found this mainly happens when fedobject needs to be updated. It has two situations:

override policy updates
pending annotation updates, e.g. we found no ops and removed the override-policy from pending controllers.

In the latter situation, event information is inaccurate. What do you think? /cc @gary-lgy @limhawjia @mrlihanbo

Agree that in the second situation the event is misleading. Would you like to fix it?

BTW, I discovered that the resource had this event when I created the resource but did not associate the overrides policy which made me feel strange.
updated overrides according to override polic(ies)

After I deep into the codes, I found this mainly happens when fedobject needs to be updated. It has two situations:

override policy updates
pending annotation updates, e.g. we found no ops and removed the override-policy from pending controllers.

In the latter situation, event information is inaccurate. What do you think? /cc @gary-lgy @limhawjia @mrlihanbo

Agree that in the second situation the event is misleading. Would you like to fix it?

I'd like to fix it later.


[Bug]: Loss of interactive Bash functionality in Pure Mode

Current Behavior (bug)
When using Bash as a shell and running devbox shell --pure, the following is observed:

The arrow keys input ^[[A ^[[B ^[[C ^[[D instead of moving the cursor and navigating through the history
The tab key does not perform command completion

These errors (from an unmodified .bashrc) are also shown:

bash: shopt: progcomp: invalid shell option name
bash: shopt: hostcomplete: invalid shell option name
bash: complete: command not found

Expected Behavior (fix)
If I add the bashInteractive package to my devbox and then type bash from inside the pure shell, the problems listed above go away. So, the fix seems to be that Devbox should use the bashInteractive package for pure mode, rather than the normal bash package.
Additional context
Output of devbox version -v:
Version:     0.5.5
Platform:    linux_amd64
Commit:      891e8de7a8ab7a3fec42fad069326d68cb84603e
Commit Time: 2023-06-19T19:18:00Z
Go Version:  go1.20.5
Launcher:    0.2.0

Arrow keys and tabs definitely look like a bug. Good catch on the bashInteractive package, we can try using that to create the shell to confirm if that fixes things.
The bashrc errors seem related to your issue #1196. The missing packages make sense (in pure mode, you wouldn't have access to those packages unless you installed them in Devbox), but we should probably not source the .bashrc as part of creating the shell

FYI the errors listed above do go away when using bashInteractive as they relate to Bash Builtin Commands rather than separate binaries. Issue #1196 covers different errors.

@apgrucza thanks for reporting this. Will look into this and fix it for next release, if the fix doesn't introduce more complications.
We wanted the pure shell have minimal impact from the system for use cases where absolute reproducibility is crucial. If the only solution is to add a bashInteractive package on user's behalf, I'd rather leave that as a suggestion when pure shell is activated.

This issue should be fixed in 0.5.6


Then the lord stated, allow there to be panes on that space

About the PR

#18074 but better
Media

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

Changelog

:cl:

fix: Windows can go next to eachother

pr merge speedrun?

Please don't use meme PR names because we have to rename it.

i don't think there is a problem with window placement

i don't think there is a problem with window placement

try placing more than 3 windows in a line, or in atmos, breaking a window to the gas miners and replacing it

i tested it on master and it works

Does this fix #14424?

like i already reverted change that broke window placement before #17815

that didnt fix it
i have had window placement be fucky several times

Please don't use meme PR names because we have to rename it.

new name 👍


confirm exit if it have unsaved changes

#9

The message doesn't show up on my browser (Chrome 56.0.2924.87 OSX)
However I do get the confirm message that is functional.
I can see that you followed the recommendations from MDN so it looks good.
Does the message show up in your browser ?

yes, i see it (Elementary OS : chrome 56.0.2924.87, Firefox 49.0.1)

OK let's merge then, the behavior is acceptable on my setup anyway, thanks !
Also as mentioned on Gitter, I'll rename this repo to apiko-ui, to prevent the generic ui name to be used in forks... Sorry about that


Make mysensors component async

Description:

Use async dispatcher and discovery.
Run is_serial (I/O) in executor.
Make mysensors actuator methods async.
Upgrade pymysensors to 0.13.0.
Use async serial gateway.
Use async TCP gateway.
Use async mqtt gateway.

Pull request in home-assistant.github.io with documentation (if applicable):
home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
mysensors:
  gateways:
    - device: '/dev/ttyACM0'
  version: '2.2'

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

I'm going to update the docs a bit too.

Is anyone interested in reviewing this? Otherwise I'll go ahead and merge this. It's been ready for a month now.


[WV-253] Convert static methods TEAM REVIEW

Changes
Convert to static methods removing self parameter
Also fixes
PEP8 E303 too many blank lines

👍


Example Usage on ReadMe.md

I thought adding an example usage (e.g. downloading the Node Runtime from nodejs.org) was essential to every library... b'coz I can't find any example of how to use this seemingly awesome library.

Agree, I'm still trying to figure out how to use this library properly in my system. I end up with using zeltice-mt-downloader- a fork of this library.

It's the first node library that i don't know how to use lol.
Weird documentation dude.
Write examples.


Better Dataset implementation

Motivation and Context
A continuation from #62 and should also solve #79
Description

[ ] DataAccessor class that acts as a lightweight reader
[x] Native Dataset
[x] Torch Dataset
[x] Tensorflow Dataset
[ ] Support for TF2.0 & TF1.0
[x] Make batching possible for native
[ ] Return namedtuple if find useful
[x] Make shuffling possible (relevant for native and TensorFlow)
[ ] Parallel reads (relevent for native and tensorflow)
[ ] Rebalancing
[ ] Dataset split for the test, train and validation
[ ] Batching nested arrays

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Documentation update
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Is this PR ready for review, or a work in progress?

[ ] Ready for review
[x] Work in progress

How Has This Been Tested?
Put an x in the boxes that apply:

[ ] Current tests cover modifications made
[ ] New tests have been added to the test suite
[ ] Modifications were made to existing tests to support these changes
[ ] Tests may be needed, but they are not included when the PR was proposed
[ ] I don't know. Help!

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have signed (or will sign when prompted) the tensorwork CLA.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

So I like where this is heading @hhsecond! Nice job!
As you'll undoubtedly notice, I've put a bit of time into this in the last two days... It's actually been relaxing to focus on something sane after the automation hell I've been through to get 0.5 built correctly on all the different platforms this past week...
A few points:
1. On the rename:
I really like this! dataset makes so much more sense than dataloaders. We need to push the "a dataset is just a view of  pieces in various columns` message hard. I think this will help.
2.  Digging in I got a bit worried about the time/memory cost tho. Making this performant when dealing with large repos is going to be our main challenge going forward. We need to make sure this doesn't collapse if repos have many columns which each might contain hundrends of thousands / millions of samples.

I've already taken a first pass at the HangarDataset class. Generators + set comprehensions / in-place updates seems to be the way to go. I only got through the one module so far, but a few benchmarks show significant speed/memory savings.... While there's a few more optimizations to make in that module alone, I'm fairly certain that we'll need to be critical of most every step in the call chain here.

I saw a note you left about trying to use something leaner that individual column instances to load the data. Great idea! We'll want a column around up front for a few convenience methods and utilities in the preprocessing / view creation, but once the samples have been split and batched, the column is absolutly not needed. I'll help out with this one, but it's as simple as building a few dictionaries mapping samples to backend locations, opening the backend file handles of interest with

https://github.com/tensorwerk/hangar-py/blob/01c94bd0a8bf7cba0f61770afcad3d8d665b6fef/src/hangar/columns/common.py#L99-L121
and then calling the same 2 lines of code we use in the column classes to read from disk.
spec = self._samples[key]
# self._be_fs = dict['backend_codes'] -> backend reader instances.
return self._be_fs[spec.backend].read_data(spec)

3. API:
There are two issues I see here:

Collating data in different columns which have different types.
Specifying views across columns which have different layouts.

It took a minute to see, but these are the exact same problems we've solved in the rest of Hangar's API..
1. Column/Schema Types
We've already solved the "incompatible data type" problem with a plugable system of column schemas... Since each schema knows exactally what it is and how to process data passing through the column API, we can rely on it to collate/stack batches of data correctly.

for the ndarray columns, we would of course just stack arrays along a new access to create the batch...
we should do the same with the str typed column schemas, instead of calling np.stack, it should be a list.append() operation (or something else which makes sense for how python strings are grouped together in a container, it doesn't really matter...)
The point is that we can't stick an 'np.ndarray' AND 'str' typed piece of data together in any way that makes sense. What we can do is put each piece of data together appropriately for the type of column that it is stored in.

As far as for how it's returned to the user, we handle that the same way we handle everything else: order in == order out. If you specify
dset = make_numpy_dataset(
    columns=['train_images', 'train_labels'],
    keys=('foo', 'bar', 'baz', 'foo', 'bar2'),
    batch_size=2,
    drop_last=False)

for data_batch in dset:
    print(data_batch)

It should output something like the following in a regular tuple. where len(data_batch) == len(columns) and the order of output column results is exactally the order in which they appeared in the input columns argument to make_foo_dataset().
The order of samples returned in each batch - and it's index in the batch - should exactaly match the ordering of their position in the input keys sequence unless shuffle=True is specified. We don't deduplicate requests for the same keys, we don't mutate order or structure in any way unless explicitly asked to. For example:
([[img_foo_data], [img_bar_data]],  [label_foo_data, label_bar_data])
([[img_baz_data], [img_foo_data]],  [label_baz_data, label_foo_data])
([img_bar2_data], [label_bar2_data])

If we preserve order unless explicitly instructed otherwise we can eliminate a lot of hardship right up front: simple to use and understand, as well as highly customizable based on the end user application.
In regards to the type of container the output is stored in:
namedtuple is a no-go since dynamic definition is a disaster. The choice is between tuples and dicts. I'm strongly in favor of tuples (so long as we preserve ordering like I outlined above),. I don't see a clear need to return a mapping in most cases, and creating many thousands of dicts is actually a non-trivial expense if we don't need to use them. I think returning tuples as a default and including an option to return a dict instead would provide enough flexibility for most people.?
2. Specifying Views / Column Layouts
The column layouts were created with the express purpose of allowing for access/usage paterns which are wholly incompatible. There may be similarities and best practices, but at the end of the day we can't force a single-level store to be used in the same way a nested dictionary would be.
I'm going to propose we use a slightly modified version of the syntax used to retrieve a view of some sample / columns from the checkout object.
>>> dset[('nested_col', 'sample_1', '0'), ('foo', '0')]
[np.array([1, 0]), np.array([0])]

>>> dset[('nested_col', 'sample_1', ...), ('foo', '0')]
[{'subsample_0': np.array([1, 0]), 'subsample_1': np.array([1, 1])},
 np.array([0])]

>>> dset[('foo', '0'), ('nested_col', 'foo', 0:3)]
[np.array([0]),
 {'subsample_0': np.array([1, 0]),
  'subsample_1': np.array([1, 1]),
  'subsample_2': np.array([2, 2])}]

But instead of having to specify the column every time, the sample keys for one view would be nested in a list and matched to their column by index. Something like this?
>>> make_numpy_dataset(column=('nested_col', 'foo'),  keys=[(('sample_1', '0'), '0'),])

>>> make_numpy_dataset(
...     column=('nested_col', 'foo'),
...     keys=[(('sample_1', ...), '1'), (('sample_2', ...), '2')]
... )

# it's easy enough to generate keys this way as well.
>>> generated_keys = []
>>> for sample in train_col.keys():
...     samp_key = ((sample, ...), sample, ('train_category', sample))
...     generated_keys.append(samp_key)
>>>
>>> make_numpy_dataset(('nested_col', 'foo', 'nested_categories'), keys=generated_keys])

Still a bit of a WIP, but it'd be nice to be consistent across the platform and this seems like a reasonable solution.
At any rate, I think we could knock this out in a short bit and push it to 0.5.1? Let me know your thoughts!

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: hhsecond:x: rlizzoYou have signed the CLA already but the status is still pending? Let us recheck it.

I found that the commit history is somehow screwed up and not fixable without careful analysis and probably that's not worth it. I am closing this PR in favor of creating a #206


added external links for additional reading for the reader

as purr convo with @adlerjohn, adding external links for the reader to do additional reading on the different topics

linter failing due to files outside of this branch, will fix in the appropriate branch


Add correct stream_table picture

It was displaying mysql_to_kafka.gif instead.

Good catch - thanks for the PR!


Disable automatically updating Python Language Server

How can I disable the auto-update feature of python language server? I need to update it whenever I want, not in the middle of my work or when I'm in a rush!

This is controlled by the client (extension) so please open issue in https://github.com/Microsoft/vscode-python


App already shows fully vaccinated on day 14 after the last shot

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[ ] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository - Currently checking
[X] Bug is not already reported in another issue

Technical details

Device name: Requested
Android version: 11
App version: 2.3.3

Describe the bug
The app already shows the "Fully vaccinated" tile on the Home Screen on day 14 and not only at day 15.
This leads to the problem that the user is seeing the fully vaccinated tile but the CovPassCheck App still shows that the certificate is not valid yet. It says that the full vaccination status will be archived on the next day.
Steps to reproduce the issue

Register a vaccination certificate
Wait till you reached day 14 after your last shot
See that CWA already shows "Fully vaccinated"
See that CovPassCheck shows that you don't yet have a valid vaccination certificate.

Expected behaviour
Fully vaccinated tile should only be shown starting on day 15 after the vaccination.
Additional context

This is a report I did based on Feedback on Twitter.
I'm checking the behavior under iOS, but I can't find a test QR-Code which has received all shots but the vaccination is not yet 14 days ago, do you have a QR-Code for me from which I could test this?

Internal Tracking ID: EXPOSUREAPP-7831 iOS
Internal Tracking ID: EXPOSUREAPP-7865 Android

Thanks everybody for reporting here. Similar report on AppStore therefore transferred to doc repo.

Internal Tracking ID: EXPOSUREAPP-7831
Corona-Warn-App Open Source Team

@dsarkar
I looked at the Android test VaccinatedPersonTest.kt. It uses a vaccination date of 2021-04-27 and says at 2021-05-10T12:00:00.000Z that the result is COMPLETE vaccination and at 2021-05-11T12:00:00.000Z the result is IMMUNITY.

Date
Days since vaccination
CWA Result

2021-04-27
0
COMPLETE

2021-04-28
1
COMPLETE

2021-04-29
2
COMPLETE

2021-04-30
3
COMPLETE

2021-05-01
4
COMPLETE

2021-05-02
5
COMPLETE

2021-05-03
6
COMPLETE

2021-05-04
7
COMPLETE

2021-05-05
8
COMPLETE

2021-05-06
9
COMPLETE

2021-05-07
10
COMPLETE

2021-05-08
11
COMPLETE

2021-05-09
12
COMPLETE

2021-05-10
13
COMPLETE

2021-05-11
14
IMMUNITY

2021-05-12
15
IMMUNITY

This does not agree with the definition provided by https://digitaler-impfnachweis-app.de/faq/ from the Robert Koch-Institut.
"Der volle Corona-Impfschutz ist erst 14 Tage nach der letzten erforderlichen Impfung erreicht. Der QR-Code als Nachweis für den kompletten Impfschutz ist daher erst ab Tag 15 nach der vollständigen Corona-Impfung gültig."
 Tag 1 nach der vollständigen Impfung ist wohl 28.04.2021, daher ist logischerweise Tag 15 nach der vollständigen Impfung 12.05.2021 und nicht 11.05.2021. IMMUNITY sollte erst ab 12.05.2021 gezeigt werden und nicht schon am 11.05.2021.

(I wrote in German since this is an interpretation of a rule written in German and I didn't want to introduce translation interpretations into the analysis.)

@guruguruguru
Thanks for adding your observations!

@MikeMcC399 Thank you so much for your investigation! I'll look at the iOS code when I find the time to do.

Can you provide for your examples the concrete date of vaccination and the display date in the app?

These are the screenshots from the Twitter user:

CWA showing immunity too early (12.06.)
CovPass shows when the certificate becomes valid
CovPasCheck shows that the certificate is invalid

Maybe related here: https://github.com/Digitaler-Impfnachweis/certification-apis/issues/91

I found https://www.bundesanzeiger.de/pub/publication/x6tHxtuQ0pora3FnUEG/content/x6tHxtuQ0pora3FnUEG/BAnz AT 08.05.2021 V1.pdf?inline with the definition

ein Impfnachweis ein Nachweis hinsichtlich des Vorliegens einer vollständigen Schutzimpfung gegen das Coronavirus SARS-CoV-2 in deutscher, englischer, französischer, italienischer oder spanischer Sprache in verkörperter
oder digitaler Form, wenn die zugrundeliegende Schutzimpfung mit einem oder mehreren vom Paul-Ehrlich-Institut
im Internet unter der Adresse www.pei.de/impfstoffe/covid-19 genannten Impfstoffen erfolgt ist, und
a) entweder aus einer vom Paul-Ehrlich-Institut im Internet unter der Adresse www.pei.de/impfstoffe/covid-19
veröffentlichten Anzahl von Impfstoffdosen, die für eine vollständige Schutzimpfung erforderlich ist, besteht
und seit der letzten erforderlichen Einzelimpfung mindestens 14 Tage vergangen sind oder
b) bei einer genesenen Person aus einer verabreichten Impfstoffdosis besteht,

So according to this, CWA is proclaiming immunity one day too early.
Since there is no time-stamp, only a date, on the vaccination certificate, we have to assume that the vaccination takes place late on day 0. So to ensure that at least 14 full days have past, we have to wait for days 1 to 14 to pass. Only on day 15 can we say that a person is immune.

This line seems to be doing the calculations for the iOS app:
https://github.com/corona-warn-app/cwa-app-ios/blob/b28ef6f0898064bbc86788d91c366e252a87952e/src/xcode/ENA/ENA/Source/Services/HealthCertificate/Models/HealthCertifiedPerson.swift#L115
Looks like iOS also calculates immunity one day early. But I am not a Swift guy, so take this with a grain of salt.

@dsarkar
Is there any dev feedback to Internal Tracking ID: EXPOSUREAPP-7831 yet?
This seems quite a visible issue even though the issue resolves itself one day later for an individual when all apps then deliver the same result. Is it considered high priority to resolve, perhaps also if necessary in a hotfix to 2.3.x?

Looks like iOS also calculates immunity one day early. But I am not a Swift guy, so take this with a grain of salt.

Yes, I have the same issue on my iphone and on my android.

@dsarkar
Getting feedback on this issue to say whether it is a bug or not and when (if a bug) it will be fixed, is more about the reputation of the app for providing correct information than anything else. So I think responding to the issue should be treated urgently.
The consequence for the person owning the vaccination certificate receiving immunity status one day too early is in favor of the vaccinated person. That should not be a worry in itself.
The consequence for people who the person owning the vaccination certificate might be allowed to come into contact with, one day too early, is negative, however the difference in the risk of infection between the 14th and the 15th day after vaccination is going to be extremely small. The legal definition of 14 days is also an arbitrary length of time to say that the risk is acceptable.
So this is about reputation and reliability of the app. I hope there will soon be a response to this issue.

@MikeMcC399 @Ein-Tim Thanks..... this snowed under, I will forward your info now. Thanks!

FYI this matter is set to "very high" priority

Internal Tracking ID: EXPOSUREAPP-7831 iOS
Internal Tracking ID: EXPOSUREAPP-7865 Android

FYI PR iOS https://github.com/corona-warn-app/cwa-app-ios/pull/2950

FYI PR Android https://github.com/corona-warn-app/cwa-app-android/pull/3467

It's good to see that the issue has already been fixed in Android and iOS and will be ready for release together with version 2.4.x. 👍🏻

I looked at the Android test VaccinatedPersonTest.kt. It uses a vaccination date of 2021-04-27 and says at 2021-05-10T12:00:00.000Z that the result is COMPLETE vaccination and at 2021-05-11T12:00:00.000Z the result is IMMUNITY.
Date	Days since vaccination	CWA Result
2021-04-27	0	COMPLETE
2021-04-28	1	COMPLETE
2021-04-29	2	COMPLETE
2021-04-30	3	COMPLETE
2021-05-01	4	COMPLETE
2021-05-02	5	COMPLETE
2021-05-03	6	COMPLETE
2021-05-04	7	COMPLETE
2021-05-05	8	COMPLETE
2021-05-06	9	COMPLETE
2021-05-07	10	COMPLETE
2021-05-08	11	COMPLETE
2021-05-09	12	COMPLETE
2021-05-10	13	COMPLETE
2021-05-11	14	IMMUNITY
2021-05-12	15	IMMUNITY
This does not agree with the definition provided by https://digitaler-impfnachweis-app.de/faq/ from the Robert Koch-Institut.
"Der volle Corona-Impfschutz ist erst 14 Tage nach der letzten erforderlichen Impfung erreicht. Der QR-Code als Nachweis für den kompletten Impfschutz ist daher erst ab Tag 15 nach der vollständigen Corona-Impfung gültig."
 Tag 1 nach der vollständigen Impfung ist wohl 28.04.2021, daher ist logischerweise Tag 15 nach der vollständigen Impfung 12.05.2021 und nicht 11.05.2021. IMMUNITY sollte erst ab 12.05.2021 gezeigt werden und nicht schon am 11.05.2021.

(I wrote in German since this is an interpretation of a rule written in German and I didn't want to introduce translation interpretations into the analysis.)

Sorry in advance for bringing this up so late in the process but I just started thinking about a bit this after a quick discussion on Twitter with @Ein-Tim and others.
I personally think the new interpretation of how to count the days is not correct and actually the previous logic was already right.
Quoting https://www.rki.de/SharedDocs/FAQ/COVID-Impfen/FAQ_Liste_Durchfuehrung_Impfung.html#FAQId15234274:

Als vollständig geschützt gelten Personen 14 Tage nach Verabreichung aller notwendigen COVID-19-Impfstoffdosen, also am 15. Tag.

So a person is considered "fully protected" 14 days after the second dose, on the 15th day.
If you focus on "15. Tag" (15th day), that leaves room for interpretation, depending on if you consider the day of the vaccination the "zero-th" day or the "first day". However, if we focus on "14 days after the second dose", it becomes much more clear:
If I got my second dose on 04-27, 04-28 would be "1 day after second dose", i.e. 05-11 is "14 days after second dose" (as is shown in your table) which from my interpretation fulfill's the criteria as specified by the RKI.
This by deduction means that the "15th day" must be counted with the day of the vaccination being considered the "1st day"

@lumaxis
You can read the legal text quoted on http://www.pei.de/impfstoffe/covid-19:
"... und seit der letzten erforderlichen Einzelimpfung mindestens 14 Tage vergangen sind ..."
I explained in https://github.com/corona-warn-app/cwa-documentation/issues/638#issuecomment-860655241 how I interpreted this, and implicitly the Open Source Team agrees with this because they have changed the app accordingly in preparation for the 2.4 release. The CovPass app was already calculating this way.
You have a different interpretation which depends on counting at the beginning of the day instead of the end of the day. To a certain extent this is all arbitrary anyway, but at least all apps should be consistent.
When CWA 2.4 is released we can say that CWA and CovPass will be in agreement and that will help remove some confusing experiences for users of the current CWA 2.3 version.

@lumaxis
Also, §§ 186 ff. BGB are relevant here.
§ 187 Abs. 1 Alt. 1:

Ist für den Anfang einer Frist ein Ereignis [...] maßgebend, so wird bei der Berechnung der Frist der Tag nicht mitgerechnet, in welchen das Ereignis [...] fällt.

This also seems to imply that the solution the CWA has now adopted is the correct one.

@lumaxis
doctors and bureaucrats think differently.
From a medical point of view (for example when it comes to setting the date of the second vaccination) 14 days later would be day 14 and not day 15! Doctors don't take the exact time into account when calculating the intervals, since vaccinations are usually given during normal opening hours and not in the middle of the night. In addition, a few more or less hours do not matter at all.
Vaccine studies show that effectiveness begins after 10-12 days. This is also the time when the shift from IgM to IgG antibodies (measurable in laboratories) takes place. RKI has probably rounded up to two weeks in order to have an interval that is easier to count on the calendar and two more days for safety.
If you look at this from a legal point of view, the immunity defined by the RKI begins after 14 days, i.e. 336 hours and no second before! Since the exact time is not recorded, one can even construct the extreme case that someone is vaccinated at 23 clock and wants to enter a nightclub at midnight on the 14th day. Then only 13 days and 1 hour would have passed and this is nearly one day too early!
totally petty, but correct.

Thanks for the explanations, everyone! 🙂

"... und seit der letzten erforderlichen Einzelimpfung mindestens 14 Tage vergangen sind ..."

I think this way of phrasing it makes it much more clear and also intuitively makes sense when you think about it in that way.
"Wait at least 15 days to ensure at least 14 days have passed, even if someone was vaccinated at 23:59 on day 0", which I believe is also what @Geimpfter was hinting at.

To a certain extent this is all arbitrary anyway, but at least all apps should be consistent.

This we can definitely all agree on and to me is by far the most important aspect anyway. 💯
Thanks again for indulging me and discussing this a bit more and thanks everyone for the work you do on the app! 🙇🏼

Version 2.4 has just been released and is in staged rollout! It would be nice if someone could confirm the fix before I close this issue. Thanks!

@krausf confirmed the fix under iOS in https://github.com/corona-warn-app/cwa-app-ios/issues/3008#issuecomment-868327015.
Can someone confirm the fix under Android?

I Just got 2.4.2.
My second dose was on 13.06.2021 12:59 and the app says  "vollständiger Impfschutz in 1 Tag".
I would have expected to be fully protected on Monday (2 days)

@guruguruguru Which version are you using? R 2.3 or R 2.4? Under R 2.4 it will take one more day to show full immunisation.

As I wrote, Version is 2.4.2

@guruguruguru
Could you maybe keep watching the behavior and report back what happens tomorrow (whether the app really shows the "Vollständiger Impfschutz" card tomorrow).
Also, could you maybe scan the QR-Code with the CovPass App and see what date it shows?

@guruguruguru

I Just got 2.4.2.
My second dose was on 13.06.2021 12:59 and the app says "vollständiger Impfschutz in 1 Tag".
I would have expected to be fully protected on Monday (2 days)

Could you say whether you are using Android or iOS?
I suspect it is Android and that the countdown code was not changed only the status code. I think that the Android 2.4.2 app will show you the tick mark for "Digitaler Impfnachweis" correctly on June 28, 2021 (and not on June 27, 2021).
If I am right and you are seeing the problem on Android, I suggest that you open a separate Bug Report issue in the Android repository.

Hi, yes this is Android. I will come back to you tomorrow/monday to Update you on the behaviour.

So today it says "Impfschutz in 0 Tagen vollständig"
So it seems to be correct as it seems to switch to fully protected tomorrow but the output should be changed to the correct value as well

@guruguruguru
Could you please open a new issue for the "0 days issue"?
I would suggest to open it in the respective repo (iOS or Android - depending on what OS you are using).
However, the devs should try to reproduce the issue on both OS.
That would be fantastic! Thank you!

I asume it is android I created a JIRA Ticket EXPOSUREAPP-8121

@thomasaugsten So I do not need to file another issue, right?

I would still like to have a separate GitHub Issue to track this bug. Also to make sure it does only affect Android.
I would consider this issue I reported here (in the OP) as solved, so I will close this issue now.
Closing as fixed in version 2.4.

@thomasaugsten  I can confirm that it's a bug at least under android. Before and after the update the counter shows the same value (in my case "1").
Before update (2.3):

After the update (2.4):

FYI everybody (especially @DerVogel2020 & @guruguruguru), I opened https://github.com/corona-warn-app/cwa-app-android/issues/3561 to track the "0 days issue".

FYI everybody (especially @DerVogel2020 & @guruguruguru), I opened https://github.com/corona-warn-app/cwa-app-android/issues/3561 to track the "0 days issue". Feel free to add your observations there.

Thanks. Will report there.


Fix libsodium version checking.

Addresses issue #52

@bendoerr landed here https://github.com/abstractj/kalium/commit/286b670e321cd81d0c3ef72a37c06b2889a3b722, thank you.


fix(useProjectToken): Fix useProjectTokens test failing 50% of the time

This PR fixes a curious bug that provoked a test failure 50% of the time of a useProjectTokens test. This was due to some MSW mockings that were having an influence on different tests depending on the time of execution. I added a unique project ID to each test to ensure this couldn't happen anymore.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Animation export is broken

Describe the bug
Simple animation is not exported correctly from Blender
To Reproduce
Export an animated cube and import back.
The action is not imported at all.
When opening the file on https://sandbox.babylonjs.com/ the action will be present but the animation count will be 0, and the end frame will be a negative value. The action will not play.

These files where created with a recent Blender 2.8 build
.blend file
AnimExport.zip
.gltf file
anim.zip
Version

Blender Version 2.80 (2019-07-08)

The attached .gltf file seems to contain two duplicated versions of the node. Both share identical name and mesh, but only other one is animated. Only the non-animated version is included in the scene.

Confirmed, after manually removing duplicate nodes the files load correctly

Seems to be caused by #561. The node cache breaks because the animation gather now calls with different params (None for blender_scene) and then creates a new node instead of using the existing one :S

I hope this can be fixed soon before the Blender RC since animation export is completely broken even on the simplest of cases

The RC is due out today.  I don't think this fix is going in RC1, but I would expect some more bugs & fixes to come in before the next Release Candidate comes along.

I would also like to chime in about the broken animation.
Here is a gif showing what the animation looks like after it has been imported to the Godot engine. When I import it back into blender there is no animation at all, but I mostly care about getting my animations out of blender.

This just seems wrong. I'm noticing that the bouncing up and down in the torso should instead be a rotation as I didn't animate an idle cycle this terrible.
Any ideas?

@jedStevens Please report a complete bug report, as requested :

provide a .blend file
what export options are you using ?

Please first test with "always sample animations" option at export.

This is now fixed here.
Here is info about merge into blender : https://lists.blender.org/pipermail/bf-committers/2019-July/050047.html
(we are in master freeze, so I hope it will be merged before release)

@julienduroure Thank you

@julienduroure it appears we got the goahead https://lists.blender.org/pipermail/bf-committers/2019-July/050050.html


dx11/dx12: Replace comptr with wio

Temporary refering to my wio fork as we are blocked on winapi 0.3 (or a new 0.2 release) anyway and this might require an wio version bump again.
Closes #1402

bors r+

@notriddle Do you know why there is no status report?

According to the log, bors failed to push the commit to your master branch ({:error, :push}). The log is right here, though crash reports are only visible to reviewers and admins: https://app.bors.tech/repositories/848/log
You need to turn off the "Review required" thing. It's in Settings -> Branches -> Protected Branches -> master

Thanks @notriddle !
bors retry

bors r+


Git exe required for execution

Placeholder requested by Francis.
On Ubuntu 22 VM, used:
pip3 install qnxmount
to install.
Launching with:
python3 -m qnxmount efs image mnt
resulted in:
FileNotFoundError: [Errno 2] No such file or directory: 'git'
Installing git resolved the error.

Sorry for the long delay, this should be fixed with the changes I just made.
I also pushed a new version: 0.1.5 to pypi


[SUPPORT] Update capi-release to mitigate CVE-2019-3785

What
This was actioned because of https://www.cloudfoundry.org/blog/cve-2019-3785/
How to review

Code review
Check it has run down a pipeline

Who can review
Not @tnwhitwell

This is currently running down my pipeline


chore: add volunteer chifarol

chore: add volunteer chifarol

Thanks @chifarol for volunteering! Added some comments. PTAL


Typescript support

Hey,
I'd like to hear your stance on this topic.
Personally I think it's a great developer tool and a great aid when exposing the API to the end user.
I'd happily convert the existing code if you'd like me to.

I've definitely thought about using it for this project, but I'm still not quite sure. Typescript makes more sense to me for larger projects and projects that have a lot of contributors so it seems a little overkill for something like this. Let me stew on this for a while longer :)

I did a proof-of-concept port to typescript a while back (not as clean as it could be).  You can see it at here:
gle-gs3d.
It's definitely difficult to maintain a port while the library is still under heavy development.
If you just want to provide support for typescript consumers, you can simple provide typescript declarations.  I ended up using a fork to do just that, which you can see here:
gle-gaussian-splat-3d
The pertinent bits are in the rollup.config.js where you can use rollup-plugin-dts to generate the declarations.
Wonderful library by the way, I've been using it in my React Three Fiber / Cesium gle-scene-components project and it works exceptionally well!
Here's an example.


Fix httprequest tests to be more lenient on error message

The unit tests for the httprequest node have been broken for a little while but gone unnoticed.
This is due to some new tests that were recently added in #3776. Took me a moment to track down the issue as the tests check the version of node and only run if on the versions of node that introduced the strict parser... and I was slightly down-level so couldn't recreate.
The tests was looking for a very specific error message - however it appears the text of the error changes in different node versions. So I've relaxed the test just to check for an error, rather than the full text.

Coverage increased (+0.006%) to 68.322% when pulling c62a101635fd070a08d799b5e26a0e9450f6485e on fix-httpreq-tests into 32999ffa84e96f5f72a11714055ec3e716af052a on master.


add scrollTo() before each click()

if a web element is out of the current screen, webdriver can't click on it.
I'd like to suggest scrolling to the element before clicking. It should help.

Coverage decreased (-0.09%) to 77.303% when pulling dc3461d70acc7f7ced561531dfa22fb691c1f65f on anatolyburtsev:scrollToBeforeClick into bdb3e0b6ca7c5224b8cb9fc10e4ea311c3153404 on alfa-laboratory:master.

Coverage decreased (-0.3%) to 77.138% when pulling 47ec95189dccc71a28f08ae6cc47c77e2870b149 on anatolyburtsev:scrollToBeforeClick into bdb3e0b6ca7c5224b8cb9fc10e4ea311c3153404 on alfa-laboratory:master.


How can we tune knnmindistance, knnmaxdistance, and other transition params?

Knndistancethreshold has be raised from 0.1 to 1.0 and positiondistancethreshold has been raised from 5 to 10. Apparently no ill effects have been observed. These have to be changed in documentation too.

This issue was moved to hulop/NavCogIOS#14


es werden keine Geräte gefunden

DONT'T DELETE THIS.
Please answer all questions as good as possible.
Make sure you have read the documentation at https://github.com/danielperna84/custom_homematic#custom_homematic.
Make sure you are running the latest version of hahomematic or it's custom_component (and Home Assistant) before reporting an issue.
custom_component/hahomematic version (if applicable):
0.38
Home Assistant version (if applicable):
2022.3.5
CCU version:

Model (CCU2/3, Raspi3/4, NUC, ProxmoxVE, ...): Raspi3/
OS (Original, RaspberryMatic, debmatic/...): PIVCCU3
Version: lates

Problem-relevant configuration:
Do you use tls? no
Do you use callback? no
Do you use username and password? tried wih out without
Which interfaces do you use? Classic wireless , IP wireles
Describe the bug
no devices will be discoverd by HA only 2 for Classic wireless and HM IP wireless ans 16 sensless deactivate enties.
I tried without any restriction and no password , with FHEM erverything is working.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Relevant HA log entries
non

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Authentication must be enabled in CCU -> Password is required for CCU.
Please update to 0.38.1.
What happens after a restart?
Click in HA on "vollständiges Log ..." to get log entries.

I did the update and a fresh install of raspimatic with only one hm-ip plug in the config. I did a new integration of the new system and got this:
`
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: homeassistant.config_entries
Source: custom_components/hahm/control_unit.py:104
Integration: Homematic(IP) Local (documentation, issues)
First occurred: 16:41:12 (1 occurrences)
Last logged: 16:41:12
Error setting up entry RaspberryMatic for hahm
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/hahm/init.py", line 27, in async_setup_entry
await control.async_start()
File "/config/custom_components/hahm/control_unit.py", line 104, in async_start
await self._central.start()
File "/usr/local/lib/python3.9/site-packages/hahomematic/central_unit.py", line 213, in start
await self._start_clients()
File "/usr/local/lib/python3.9/site-packages/hahomematic/central_unit.py", line 221, in _start_clients
await self._init_hub()
File "/usr/local/lib/python3.9/site-packages/hahomematic/central_unit.py", line 384, in _init_hub
await self._hub.fetch_data()
File "/usr/local/lib/python3.9/site-packages/hahomematic/hub.py", line 226, in fetch_data
await self._update_entities()
File "/usr/local/lib/python3.9/site-packages/hahomematic/hub.py", line 241, in _update_entities
variables = await self._central.get_all_system_variables()
File "/usr/local/lib/python3.9/site-packages/hahomematic/central_unit.py", line 674, in get_all_system_variables
return await client.get_all_system_variables()
File "/usr/local/lib/python3.9/site-packages/hahomematic/client.py", line 918, in get_all_system_variables
key, value = parse_ccu_sys_var(var)
File "/usr/local/lib/python3.9/site-packages/hahomematic/helpers.py", line 116, in parse_ccu_sys_var
return data[ATTR_NAME], float(data[ATTR_VALUE])
ValueError: could not convert string to float: ''
`

This is related to system variables, but should not affect devices
Which devices do you have connected?

Please post screenshots of the device overview and add a diagnostics file (click on the integration, download diagnostics)

right now it is only a "HMIP-PSM" ip meter plug, nothing else.
i did not find where to download the diagnostics (sorry)

https://www.home-assistant.io/blog/2022/02/02/release-20222/#diagnostics-for-integrations-and-devices

there is no diagnostics download button / linke available, sorry

Go on the integrations page
Click on the service

it is not there because it never had started completely

Please try 0.38.2. That should log the defect SysVar

I updated the upadate and loaded an old HM config with many devices and now it is working. thankyou very much for your help


missing some cvs appts that are open in mi

currently there are appointments open at Holt, MI and Lansing, MI

tool is only picking up lansing appts for some reason, both in the gui and the api output.

wait - weird - about 5 min later it found it!

closing some sort of weird delay - great tool by the way!


Add Identify support to the darwin Framework

Problem
There's currently no way to trigger the Identify cluster from the Darwin Framework
Summary of Changes
Add an API to the DeviceController to trigger Identify on an accessory

@saurabhst @jelderton @hawk248 @BroderickCarlin ?


route.path is not editable in extendRoute

Regarding https://github.com/posva/unplugin-vue-router/discussions/468#discussioncomment-10243690
When editing route.path, the path stays unchanged.
This causes https://github.com/posva/unplugin-vue-router/discussions/468#discussioncomment-10243694 to still occur
e.g.:
extendRoute(route)
{
    console.log(route.path); // "question/:q-id"
    route.path = "question/:qId";
    console.log(route.path); // still "question/:q-id"
}

Edit:
I just saw https://github.com/posva/unplugin-vue-router/blob/main/src/core/extendRoutes.ts#L144, adding a leading slash would break my route hierarchy.

Duplicate of #341


Integrate OpenAI with LZA

Open AI available as Private Endpoint

On discussion around integrating the openai module directly, opened an issue based on the tagging limitation:
https://github.com/Azure/terraform-azurerm-openai/issues/35


Claude 3 Opus. Images are not supported for this model. Use models like GPT-4 Vision instead.

How come the application does not allow pasting images while the Claude 3 models are capable of understanding and analyzing images?

Sorry, just noticed that this issue is already present @ https://github.com/mckaywrigley/chatbot-ui/issues/1563


Upload company logos to github and use those links in USERS.md

The USERS.md file contains some broken images.
Ideally, we upload all images to github.
I used this method: https://gist.github.com/NawalJAhmed/2168f7659c08b6a033e7f6daf8db69a6 to upload the images to GitHub, such that the images are working now and will keep working in the future.

/approve


Add PTC auth host to list of endpoints to map to hostname

I think this is the only PTC SSO host, but correct me if I'm wrong.

Aw, sweet! Thank you again and again 😄


DartDoc failed because Diagnostics

Where does the error
dart: >=2.10.0 <2.11.0
flutter: >=1.22.0 <2.0.0
Using plugin: webview_flutter: ^ 1.0.5
I think these errors come from foundation/diagnostics.dart, as there are some shortcomings in the documentation.
Steps to Reproduce

Run dartdoc
...
dartdoc failed

Logs

admins-MBP:Tinkoff-Acquiring-SDK-Flutter mit$ dartdoc
Documenting tinkoff_acquiring...
Initialized dartdoc with 563 libraries in 58.8 seconds
Generating docs for library tinkoff_acquiring_core from package:tinkoff_acquiring/tinkoff_acquiring_core.dart...
Generating docs for library tinkoff_acquiring_ui from package:tinkoff_acquiring/tinkoff_acquiring_ui.dart...
error: unresolved doc reference [new DiagnosticsNode.message]
from tinkoff_acquiring_ui.WebView3DS.debugDescribeChildren: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3457:25)
in documentation inherited from diagnostics.DiagnosticableTree.debugDescribeChildren: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3457:25)
error: unresolved doc reference [DiagnosticsProperty]
from tinkoff_acquiring_ui.WebView3DS.debugDescribeChildren: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3457:25)
in documentation inherited from diagnostics.DiagnosticableTree.debugDescribeChildren: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3457:25)
error: unresolved doc reference [RenderTable.debugDescribeChildren]
from tinkoff_acquiring_ui.WebView3DS.debugDescribeChildren: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3457:25)
in documentation inherited from diagnostics.DiagnosticableTree.debugDescribeChildren: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3457:25)
error: unresolved doc reference [int]
from tinkoff_acquiring_ui.WebView3DS.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/widgets/framework.dart:509:8)
in documentation inherited from diagnostics.Diagnosticable.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3342:8)
error: unresolved doc reference [DiagnosticsTreeStyle]
from tinkoff_acquiring_ui.WebView3DS.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/widgets/framework.dart:509:8)
in documentation inherited from diagnostics.Diagnosticable.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3342:8)
error: unresolved doc reference [ColorProperty]
from tinkoff_acquiring_ui.WebView3DS.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/widgets/framework.dart:509:8)
in documentation inherited from diagnostics.Diagnosticable.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3342:8)
error: unresolved doc reference [Color]
from tinkoff_acquiring_ui.WebView3DS.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/widgets/framework.dart:509:8)
in documentation inherited from diagnostics.Diagnosticable.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3342:8)
error: unresolved doc reference [IconDataProperty]
from tinkoff_acquiring_ui.WebView3DS.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/widgets/framework.dart:509:8)
in documentation inherited from diagnostics.Diagnosticable.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3342:8)
error: unresolved doc reference [IconData]
from tinkoff_acquiring_ui.WebView3DS.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/widgets/framework.dart:509:8)
in documentation inherited from diagnostics.Diagnosticable.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3342:8)
error: unresolved doc reference [TransformProperty]
from tinkoff_acquiring_ui.WebView3DS.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/widgets/framework.dart:509:8)
in documentation inherited from diagnostics.Diagnosticable.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3342:8)
error: unresolved doc reference [Matrix4]
from tinkoff_acquiring_ui.WebView3DS.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/widgets/framework.dart:509:8)
in documentation inherited from diagnostics.Diagnosticable.debugFillProperties: (file:///Users/mit/SDK/flutter/versions/1.22.0/packages/flutter/lib/src/foundation/diagnostics.dart:3342:8)
Validating docs...
warning: dartdoc generated a broken link to: README.ru.md, linked to from package-tinkoff_acquiring: file:///Users/mit/Projects/Tinkoff-Acquiring-SDK-Flutter
found 1 warning and 11 errors
Documented 2 public libraries in 5.2 seconds
dartdoc failed: dartdoc encountered 11 errors while processing..
#0      Dartdoc.generateDocs (package:dartdoc/dartdoc.dart:231:9)

#1      Dartdoc.executeGuarded. (package:dartdoc/dartdoc.dart:500:15)
#2      _rootRun (dart:async/zone.dart:1190:13)
#3      _CustomZone.run (dart:async/zone.dart:1093:19)
#4      _runZoned (dart:async/zone.dart:1630:10)
#5      runZonedGuarded (dart:async/zone.dart:1618:12)
#6      Dartdoc.executeGuarded (package:dartdoc/dartdoc.dart:498:5)
#7      main (file:///b/s/w/ir/cache/builder/sdk/third_party/pkg/dartdoc/bin/dartdoc.dart:24:11)

#8      _startIsolate. (dart:isolate-patch/isolate_patch.dart:299:32)
#9      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)

@mit-73
Assuming you are using dartdoc plugin, issues related to it may have to report in this repo : https://github.com/dart-lang/api.dart.dev/issues

Okay, I have duplicated this issue

@mit-73 Thanks. I am closing this from here. Feel free to comment if you think it need to be kept open in this repo.


Creating a publisher requires a cats.effect.Blocker

closes #230
@alexander-branevskiy have a look if you can.
@Daenyth your review would be much appreciated as well.

Ready for review (and copying this message so it doesn't get lost):

I went with adding Blocker directly when creating an Fs2Rabbit client. Even if you don't need publishing, you need to create a Blocker which might not be ideal but it makes the API usage much easier.

I don't know, feels like a reasonable choice to make for now but I'd be happy to change this in a future release if users are not happy with it.


eth-testrpc installation errors (e.g. python)

Hi,
the installation of eth-testrpc raises several errors. Interessting is the python too:
http://pastebin.com/yKrXXMZa
The installation was done with "pip install eth-testrpc"
It seems that the installation uses a python3 library although python2.7 is needed.
If you see in the log, the library python2.7 is used in most part of the installation, but there is an error concerning the utils_py3.py library, between others
Regards
SkyDog

This should be fixed.  The library has been significantly overhauled since this was opened.  Please re-open if this is still an issue.


Give plot_series the option of not showing zeros

Description
It would be nice to have the option of not plotting zero values when using the plot_series function when they're not relevant to the analysis.
from utilsforecast.data import generate_series
from utilsforecast.plotting import plot_series
ts = generate_series(n_series=1)
ts.loc[30:50, 'y'] = 0
plot_series(ts)

We could have an optional parameter, for example exclude_zeros=True, that allows users to choose whether to plot zero values.
Use case
I'm currently working on the Python version of fpp4, specifically chapter 12.5, which involves plotting the number of calls to a bank, with no calls outside of operational hours.

The book uses fill_gaps which creates NaNs for times that were missing. plot_series behaves the same way, i.e.
import pandas as pd
from utilsforecast.preprocessing import fill_gaps

bank_calls = pd.read_csv(
    'https://nixtla-public.s3.amazonaws.com/fpp4-datasets/bank_calls.csv',
    parse_dates=['ds']
)
filled = fill_gaps(bank_calls, freq='5min', start='per_serie', end='per_serie')
plot_series(filled)

Closing due to lack of response.


Can't Get Plugin to Function

Jekyll 2.5.3, Octopress 3.0.9, date-format 3.0.3
I've added the gem to my jekyll_plugins group in my Gemfile, and other plugins I've added there work fine. I can see the gem is installed, but upon building the site, neither the {{ post.date }} I've added to the post layout or the example conditional to show the post updated time display. I did add the date_updated setting in the YAML front matter of the post, but nothing ever renders after I build the site. What might I be doing wrong?

Gemfile
post.html
test post

Same issue. The dates used to appear under my blog title, but it's not being rendered since updating to the latest release. I didn't make changes to the date.html partial that gets loaded into the post layout, yet it's no longer rendered.
{% if page.date %}{% capture time %}{{ page.date_html }}{% endcapture %}{% endif %}
{% if post.date %}{% capture time %}{{ post.date_html }}{% endcapture %}{% endif %}

{% if page.updated %}{% capture updated %}{{ page.date_updated_html }}{% endcapture %}{% endif %}
{% if post.updated %}{% capture updated %}{{ post.date_updated_html }}{% endcapture %}{% endif %}

I updated the following gems:

jekyll 2.0 to 3.8.5
octopress-hooks 2.2 to 2.6.2
octopress-date-format 2.0 to 3.0.3

I added the gems to the plugins list where other Jekyll plugins are loading properly:
# config.yml
plugins_dir: ./plugins
plugins:
  - octopress-date-format
  - octopress-hooks
  ...

Did anyone manage to resolve this? When I upgraded the gem, it stopped working.
octopress-date-format 2.0.2 to 3.0.3

All the methods return null:
date_text
time_text
date_xml
date_html
date_time_html

Even after making the change in my above comment 1, this plugin still doesn't work for me. I'm using octopress 3.0.11 and jekyll 4.0.1. I came across this issue because I tried upgrading from octopress 2.x and jekyll 2.5.3. This previous combination of octopress and jekyll worked because jekyll 2.5.3 has code to extract the date from the post's filename here 2 and assign it to a page and post's date attribute before execution hits octopress-date-format here 3.
Jekyll 4.0.1 doesn't seem to set the date attribute on pages and posts anymore by parsing the file name. The closest logic to that I can see if this 4, but execution doesn't seem to hit this line before 3.
3 workarounds I can think of

don't upgrade
set explicit date: fields in the post YAMLs
patch octopress-date-format's hack_date() method here 5 to have either the jekyll logic from 2 or 4


Deprecate unary migration

Deprecate unary migration?

This is the one where the result can only migrate to a Functor, not to an ACSet.


possible security issues, feedback needed

Our customer uses checkmarx SAST checks and we get the following results.
Can you check these and provide feedback?

Some more information, details, example of XSS?

Unfortunately I can not check that in detail anymore. So I'll close this issue.


Please upgrade "spfx-controls-react" to use latest version of "markdown-it" due to bugs in the current version of the referenced code

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
None
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
No response
Describe the bug / error
Current latest version "<EMAIL_ADDRESS>is using out of date version of "markdown-it" which contains issues and vulnerabilities. Please upgrade to the latest version of<EMAIL_ADDRESS>or latest
Steps to reproduce
You can run scan with tools like Snyk to see highlighted issue
Expected behavior
Latest version of ""markdown-it"

@YaroslavPentsarskyy I think you are in the wrong repo - there is already a ticket open:
https://github.com/pnp/sp-dev-fx-controls-react/issues/1916

Closed as per above (duplicated: https://github.com/pnp/sp-dev-fx-controls-react/issues/1916)

Closing as in a wrong repo. Good request though.


Diagnose files that aren't in the crate hierarchy

As of recently, we diagnose mod m; with a #[cfg] that is currently inactive. We do not emit a diagnostic for the contents of m.rs though, which can be pretty confusing, since it just shows up as "IDE is not working" while editing m.rs.

It'd also be really great to have a big warning when editing a file that isn't in the module tree at all.

According to the Rust discord, warnign about this is also apparently a feature in jetbrains. Would also address issues like this: https://github.com/rust-analyzer/rust-analyzer/issues/7345

I'm planning to add a quickfix that treats files like this as standalone crates instead.

I added a quickfix that adds the appropriate mod name; item instead


JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)

When I conducted yarn test-erc20

This is hardhat.config.ts

@eitanz-coti kindly check

Hi @Gessi12 ,
can you please confirm that you fetched the latest version tag v1.0.0 and also that you reinstall the yarn package ?

Hi @Gessi12 ,
can you please confirm that you fetched the latest version tag v1.0.0 and also that you reinstall the yarn package ?

yes

Hi @Gessi12 , thanks again for answering.
could you please try to delete node_modules , artifacts and cache direcotries and try agin ?

Hi @Gessi12 , thanks again for answering. could you please try to delete node_modules , artifacts and cache direcotries and try agin ?

It's useless, the same prompt still applies

I don't know if there is a problem with testnet, as my account is also unable to make transfers and has been pending

Hi @Gessi12
please verify the correct RPC url was added to metamask - https://testnet.coti.io/rpc.
if the url is correct please try to see that the correct nonce is been set, it can be retrived by running the below in some trminal:
curl https://testnet.coti.io/rpc
-X POST
-H "Content-Type: application/json"
--data '{"method":"eth_getTransactionCount","params":["0xcA4322401c97C0AFAcD274aC38DbE1bDE5aABCda", "latest"],"id":1,"jsonrpc":"2.0"}'
{"jsonrpc":"2.0","id":1,"result":"0x15f"} --> the result is in Hex and need to be convert to decimal.

if you need example for python or node js please let me know .

regarding the  test-erc20, i faced this issue when node_modules was not deleted when moving to testnet version > 1.0.0.
can you please everything from scratch including delete of node_modules, artifacts and cache directories.

example

yes, I need example for python or node js

Hi @Gessi12 please verify the correct RPC url was added to metamask - https://testnet.coti.io/rpc.
if the url is correct please try to see that the correct nonce is been set, it can be retrived by running the below in some trminal: curl https://testnet.coti.io/rpc -X POST -H "Content-Type: application/json" --data '{"method":"eth_getTransactionCount","params":["0xcA4322401c97C0AFAcD274aC38DbE1bDE5aABCda", "latest"],"id":1,"jsonrpc":"2.0"}'
{"jsonrpc":"2.0","id":1,"result":"0x15f"} --> the result is in Hex and need to be convert to decimal.

if you need example for python or node js please let me know .

regarding the test-erc20, i faced this issue when node_modules was not deleted when moving to testnet version > 1.0.0. can you please everything from scratch including delete of node_modules, artifacts and cache directories.

RPC url is right, but it still prompts a JSON-RPC error.
yes, I need example.

@eitanz-coti bash: curl https://testnet.coti.io/rpc: No such file or directory

@eitanz-coti

Latest version

@eitanz-coti
Same problem when using yarn test-erc20,  I have checed to the tag v1.0.0. it seems some problem when connect to testnet.coti.io, my rpc url is const provider = initEtherProvider('https://testnet.coti.io/rpc'), also i have test it using cmd curl https://testnet.coti.io/rpc -X POST -H "Content-Type: application/json" --data '{"method":"eth_getTransactionCount","params":["0x48f4BDb54c5802194024dCe5fA7B1d8443CB7aA1", "latest"],"id":1,"jsonrpc":"2.0"}'
But all failed with error curl: (28) Failed to connect to testnet.coti.io port 443: Operation timed out or JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)

@eitanz-coti Same problem when using yarn test-erc20, I have checed to the tag v1.0.0. it seems some problem when connect to testnet.coti.io, my rpc url is const provider = initEtherProvider('https://testnet.coti.io/rpc'), also i have test it using cmd curl https://testnet.coti.io/rpc -X POST -H "Content-Type: application/json" --data '{"method":"eth_getTransactionCount","params":["0x48f4BDb54c5802194024dCe5fA7B1d8443CB7aA1", "latest"],"id":1,"jsonrpc":"2.0"}' But all failed with error curl: (28) Failed to connect to testnet.coti.io port 443: Operation timed out or JsonRpcProvider failed to detect network and cannot start up; retry in 1s (perhaps the URL is wrong or the node is not started)

@eitanz-coti Me too, no matter it's testnet or devnet. Is it an RPC issue?

@Gessi12 , @manxiaqu
please use https://github.com/coti-io/confidentiality-contracts/releases/tag/1.0.3

@gmesika-coti
curl https://testnet.coti.io/rpc
-X POST
-H "Content-Type: application/json"
--data '{"method":"eth_getTransactionCount","params":["0xcA4322401c97C0AFAcD274aC38DbE1bDE5aABCda", "latest"],"id":1,"jsonrpc":"2.0"}'
I want to use RPC to retrieve data. Is there any other RPC that can be used?

@Gessi12 , @manxiaqu please use https://github.com/coti-io/confidentiality-contracts/releases/tag/1.0.3

I try to connect to the rpc just using ethers, but it doesn't work, here is the code:
import { JsonRpcProvider } from "ethers";

describe("rpc test", function () {
  it("ether rpc test", async function() {
    const rpcProvider = new JsonRpcProvider("https://testnet.coti.io/rpc");
    let out = await rpcProvider.getBalance("0x48f4BDb54c5802194024dCe5fA7B1d8443CB7aA1");
    console.log(out);
  })
})

Is there any limit for rpc? or can you give a simple runnable code to test the connection of the rpc

I try to connect to the rpc just using ethers, but it doesn't work, here is the code:我尝试仅使用 ethers 连接到 rpc，但它不起作用，这是代码：
import { JsonRpcProvider } from "ethers";

describe("rpc test", function () {
  it("ether rpc test", async function() {
    const rpcProvider = new JsonRpcProvider("https://testnet.coti.io/rpc");
    let out = await rpcProvider.getBalance("0x48f4BDb54c5802194024dCe5fA7B1d8443CB7aA1");
    console.log(out);
  })
})

Also, I have tried with/without vpn, But it all failed.另外，我试过有/没有 vpn，但都失败了。
Is there any limit for rpc? or can you give a simple runnable code to test the connection of the rpcrpc 有限制吗？或者你能给出一个简单的 runnable 代码来测试 RPC 的连接

I also think there is a problem with RPC

try to replace JsonRpcProvider with getDefaultProvider

try to replace JsonRpcProvider with getDefaultProvider

Same error.
The logic is the same when passing the rpc url to getDefaultProvider, they all use new JsonRpcProvider to create provider

`import requests
import json
定义请求的URL
url = "https://testnet.coti.io/rpc"
定义请求头和请求数据
headers = {"Content-Type": "application/json"}
data = {
"method": "eth_getTransactionCount",
"params": ["0x415d6de6DD9d14b1502E3400365D4c70B0c56ad9", "latest"],
"id": 1,
"jsonrpc": "2.0"
}
发送POST请求
response = requests.post(url, headers=headers, data=json.dumps(data))
检查响应状态码
if response.status_code == 200:
# 输出响应数据
print("Response:", response.json())
else:
print(f"Error: {response.status_code}, {response.text}")
`
I tried to use Python to retrieve data but failed

`import requests
import json
url = "https://testnet.coti.io/rpc"
headers = {"Content-Type": "application/json"}
data = {
"method": "eth_getTransactionCount",
"params": ["0x415d6de6DD9d14b1502E3400365D4c70B0c56ad9", "latest"],
"id": 1,
"jsonrpc": "2.0"
}
response = requests.post(url, headers=headers, data=json.dumps(data))
if response.status_code == 200:
print("Response:", response.json())
else:
print(f"Error: {response.status_code}, {response.text}")
`
I tried to use Python to retrieve data but failed

Please try the following code snippet and reply back with the output.
you can try also 2 other RPC endpoints
testnet-magnus-validator.coti.io
testnet-minor-validator.coti.io
`import requests
import json
import logging
import contextlib
from http.client import HTTPConnection
def debug_requests_on():
'''Switches on logging of the requests module.'''
HTTPConnection.debuglevel = 1
logging.basicConfig()
logging.getLogger().setLevel(logging.NOTSET)
requests_log = logging.getLogger("requests.packages.urllib3")
requests_log.setLevel(logging.NOTSET)
requests_log.propagate = True

def debug_requests_off():
'''Switches off logging of the requests module, might be some side-effects'''
HTTPConnection.debuglevel = 0
root_logger = logging.getLogger()
root_logger.setLevel(logging.WARNING)
root_logger.handlers = []
requests_log = logging.getLogger("requests.packages.urllib3")
requests_log.setLevel(logging.WARNING)
requests_log.propagate = False

debug_requests_on()
url = "https://testnet-magnus-validator.coti.io/rpc"
headers = {"Content-Type": "application/json"}
data = {
"method": "eth_getTransactionCount",
"params": ["0x415d6de6DD9d14b1502E3400365D4c70B0c56ad9", "latest"],
"id": 1,
"jsonrpc": "2.0"
}
response = requests.post(url, headers=headers, data=json.dumps(data))
if response.status_code == 200:
print("Response:", response.json())
else:
print(f"Error: {response.status_code}, {response.text}")`

Please try the following code snippet and reply back with the output.请尝试以下代码片段，并回复输出。 you can try also 2 other RPC endpoints您还可以尝试其他 2 个 RPC 端点
testnet-magnus-validator.coti.io testnet-minor-validator.coti.io

import requests
import json

import logging
import contextlib
from http.client import HTTPConnection

def debug_requests_on():
    '''Switches on logging of the requests module.'''
    HTTPConnection.debuglevel = 1

    logging.basicConfig()
    logging.getLogger().setLevel(logging.NOTSET)
    requests_log = logging.getLogger("requests.packages.urllib3")
    requests_log.setLevel(logging.NOTSET)
    requests_log.propagate = True

def debug_requests_off():
    '''Switches off logging of the requests module, might be some side-effects'''
    HTTPConnection.debuglevel = 0

    root_logger = logging.getLogger()
    root_logger.setLevel(logging.WARNING)
    root_logger.handlers = []
    requests_log = logging.getLogger("requests.packages.urllib3")
    requests_log.setLevel(logging.WARNING)
    requests_log.propagate = False

debug_requests_on()
url = "https://testnet-magnus-validator.coti.io/rpc"

headers = {"Content-Type": "application/json"}
data = {
    "method": "eth_getTransactionCount",
    "params": ["0x415d6de6DD9d14b1502E3400365D4c70B0c56ad9", "latest"],
    "id": 1,
    "jsonrpc": "2.0"
}

response = requests.post(url, headers=headers, data=json.dumps(data))

if response.status_code == 200:
    print("Response:", response.json())
else:
    print(f"Error: {response.status_code}, {response.text}")

DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): testnet-magnus-validator.coti.io:443

I test the rpc url with curl again, but it all failed, if I replace the url to ethereum Sepolia rpc url, it's ok. So I think it is the rpc's issue.

@Gessi12 is this issue still releavent?


Error: cannot import name 'score_model' from 'brainscore'

Hi Martin,
I installed brainscore library in a new machine and found this error.
cannot import name 'score_model' from 'brainscore'
BrainScore in an old machine works normally.
Is it because of the latest update?

Hi maytusp,
this should still work -- are you able to import brainscore? When you dir(brainscore), do you see score_model as one of the items? Perhaps you are importing a different package that is also called brainscore?

Hi Martin,
Thanks for a very quick reply, it's just my mistake that I create a python file named brainscore.py in that folder.
The script imports this file instead of the actual brain-score library.


added parameter doctrine.orm.auto_generate_proxy_classes (in comment)......

... makes it easier to configure when running ./app/console --env=prod doctrine:ensure-production-settings

When would you want to change the default value?

I think I miss something,... Maybe I forgot to set debug to false when checking "ensure production settings", i'll check again tomorrow, cheer @fabpot

I made a mistake when "ensuring production settings" ... forgot the no-debug switch... ./app/console --env=prod --no-debug doctrine:ensure-production-settings
Everything is fine... anyway this emphasizes the fact that "doctrine:ensure-production-settings" should return a better message...
Environment "prod" (with debug set to off) is correctly configured for production.

instead of:
Environment is correctly configured for production.

and:
Proxy classes are always regenerating in "prod" environment (with debug set to on).

instead of
Proxy Classes are always regenerating.

@fabpot anyway thanks


new Pull Request from meeting on on 12/05/2017

tagging @dfederlein @thedoubl3j @tima

Do we need to these changes?

resubmitting, there is a problem b/c i need to squash


spec: support for passing client image name for mirroring use case

There is an assumption to today that a server implementation of the distribution specification will either not care about the name used by the client or that all requests will have a known common namespace. An example of this is the Docker Hub assuming that all requests are prefixed with docker.io even though the registry hostname is registry-1.docker.io. However this has always caused difficulty when a client then wants to mirror content, localhost:5000/library/ubuntu could proxy to registry-1.docker.io/library/ubuntu, however localhost:5000 could never proxy to anything else. Complicated registry configurations have been proposed to remedy this as well as a backwards incompatible approach of requesting as localhost:5000/docker.io/library/ubuntu.  However a goal of this specification should be simplicity and backwards compatibility. I believe that a solution does belong in the specification to unlock the mirroring use cases without complicated configuration or DNS setup.
My proposal is to add a way to pass up the name resolved by the client to the registry, (e.g. docker.io/library/ubuntu). So if a request is going to localhost:5000/library/ubuntu, it could mirror both docker.io/library/ubuntu and quay.io/library/ubuntu and switch based on request parameters. There are 2 possible ways to achieve this, one is by creating adding an HTTP request header (e.g. OCI-REF-NAME: docker.io/library/ubuntu) or by adding a query parameter ?oci-ref-name=docker.io/library/ubuntu). The first is clean but the second may be more useful for static mirroring. I am not suggesting one over the other yet, just stating the problem and solutions to discuss.

On Mon, Apr 16, 2018 at 10:35:39PM +0000, Derek McGowan wrote:

So if a request is going to localhost:5000/library/ubuntu, it
could mirror both docker.io/library/ubuntu and
quay.io/library/ubuntu and switch based on request parameters.

This could also be a “caching proxy” use case, depending on when the
upstream requests happen.  Just dropping in some additional keywords
in case that helps folks discover this issue again later on.

Complicated registry configurations have been proposed to remedy
this as well as a backwards incompatible approach of requesting as
localhost:5000/docker.io/library/ubuntu.

Can you shed more light on why this is backwards incompatible?  I
don't see wording in the current spec that would care about what goes
into the ‘’ portion of the URLs besides 1:
Classically, repository names have always been two path components
where each path component is less than 30 characters. The V2
registry API does not enforce this…
If a registry was trying to mirror/proxy multiple upstream registries,
I don't see why the registry couldn't define a default (for any of
these approaches).  For example, “when I get a two-component name, the
implicit first component is ‘docker.io’” (or whatever) as a local
policy.  And without such a default, I don't see how it would support
clients who are only capable of creating two-component names.
Longer term, the default-component approach may run into issues
(e.g. if you wanted to mirror/proxy a namespace that didn't expect two
child components, e.g. example.com/ubuntu or
example.com/some/group/app).  The default-name-component approach is
not forward-compatible with those cases, but that's a distinct issue
from backwards compatibility.  And you could cludge around the
limitation with blacklists for defaults (e.g. “don't inject default
components if the given name's first component is example.com”).  If
we go with the default component approach, folks maintaining default
components would ideally get their user-base upgraded to clients which
used fully-qualified names before the forward-compat issues became too
troublesome.  If that timescale is expected to be very long (because
some clients will never upgrade?), then one of your “this channel
always contains the fully-qualified image name” approaches would be a
better choice.

@wking number of components have no relevance here. The specification does not define anything about the path components. The backwards incompatibility comes from existing clients and servers. If a client is upgraded and now starts requesting localhost:5000/docker.io/library/ubuntu, the registry would have to be configured to treat docker.io as the same as previous requests it had seen. If it was an older registry, then it would just not understand the request, forcing the client to resend the request without docker.io. This sort of feature probing is a huge pain to implement for clients and this kind of configuration is really messy on the server. Using headers or query parameters can be safely ignored by older registries or omitted by older clients.

On Mon, Apr 16, 2018 at 11:32:43PM +0000, Derek McGowan wrote:

If a client is upgraded and now starts requesting
localhost:5000/docker.io/library/ubuntu, the registry would have
to be configured to treat docker.io as the same as previous
requests it had seen.  If it was an older registry, then it would
just not understand the request, forcing the client to resend the
request without docker.io.

Ah, I'd only considered old-client/new-registry above.  I agree that
new-client/old-registry would need some sort of client fallback for
registries that didn't recognize the fully qualified name in the URL
path.

Using headers or query parameters can be safely ignored by older
registries or omitted by older clients.

So what would the logic for new clients be?  Always set the
fully-qualified name in the query parameter (or wherever) and always
drop the leading component when constructing the URL path?  That would
probably work, although it doesn't end up in a world where we could
eventually drop the query parameter.  The spec already supports
version checks 1, perhaps we can do whatever for the remainder of v2
and then require fully-qualified names in the path once we cut a v3
API?  That would at least restrict “feature probing” to the initial
version check that clients should be performing anyway (or should be
performing when their non-version request 404s ;).

just like mirror-proxy function, it not spec scope in my mind.

Yes I think a query parameter is better, otherwise for caching you need to set vary-by on a nonstandard header.

@justincormack my plan here to PoC it in containerd then open a PR for the spec here. I am not sure we have used a consistent naming scheme for what we call this, in containerd we usually call this part the namespace. Sometimes it is referred to as domain, registry, or host.

I think this is a good approach and the first step in separating registry location from the "authority". The eventual goal should be to encode the authority in the image name, but this will allow for cases where it is not.
Do registries currently ignore this parameter?


https://developer.mozilla.org/en-US/docs/MDN/Community

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[x] New documentation
[x] Correction or update

Details
Subject: Proposal for a feature
The Mozilla firefox browser does not offer an option to move a tab to a different window session. For example, I have two windows of the browser open, and I want to transfer one tab to the other session. Does the browser tracks sessions or currently open windows for the browser? Is it possible. I have attached a screenshot for reference. Would like to know what the community here thinks about this!
Cheers.

Also, please direct me to the correct place to put up this issue if I have landed at the wrong one.

Hi @vansjyo! The place to submit feature requests for the Firefox browser is Bugzilla. You will need to create a Bugzilla account in order to submit an issue.


Use Stdout and Stderr in canonical proto urls for logging

description
we recently added protos for logging that use the names Stderror and Stdoutput - these are derived from the unix names which are actually stderr and stdout
i think if we dont change these we are going to confuse/annoy people who will not be familiar with this name, and make it harder to remember
if down the road (eg after documenting #15652 ) we decide to change to the common names its going to be much harder to change than addressing the issue now

cc @davinci26 @mattklein123

I believe this was done on purpose for some reason but I can't remember. @phlax? I would be fine renaming if we do it quickly since it just landed.

The reason that I did is that stdout and stderr are defined with (#define) in Windows so when the url is translated to a C++ namespace it causes collisions.

would it be possible to just change the canonical names?
grepping i see its in paths, filenames and files so theres quite a bit of change
mho is that we should change now and avoid regret

would envoy.extensions.access_loggers.stdoutput.v3.StdoutAccessLog work?
The reason I did not went for this approach is that there are two different names for stdout in the same type. The problem is envoy.extensions.access_loggers.stdoutput.v3.StdoutputAccessLog is translated into envoy::extensions::access_loggers::stdoutput::v3::StdoutputAccessLog and there is a namespace collision when it changes to stdout.

would envoy.extensions.access_loggers.stdoutput.v3.StdoutAccessLog work?

i think that is more confusing tbh
is there no way to workaround the ns clash  ?

is there no way to workaround the ns clash ?

I have tried undefing it but this breaks fmt.
Another alternative would be to use envoy.extensions.access_loggers.standardstreams.v3.StdoutAccessLog

what about envoy.extensions.access_loggers.access.v3.StdoutAccessLog
not sure if this would then clash with stderr - but perhaps they could be merged in that way - which i think would also be easier to remember

iiuc this would have the same problem/solution as using standardstreams

not sure if this would then clash with stderr

Not sure on top of my head. I will have to validate it myself

im just looking at the dir  - perhaps just stream would be closer to file which is the closest comparison i think

I think there will be clash but a way around it is to have two types in the same proto under the the stream package

envoy.extensions.access_loggers.stream.v3.StdoutAccessLog

and
envoy.extensions.access_loggers.stream.v3.StderrAccessLog

wfm if its possible to do it that way
@mattklein123 - any thoughts on this ?

tbh i would even leave off the final AccessLog if that was possible - shorter the better i think - and it dupes

hmm - maybe that would be inconsistent with others

I don't have a strong opinion. Whatever you both agree to is fine but we need to change it ASAP if we are going to change it.

I am working on this now, I will try to get at it today.


Hide related bugs:

Unhide inconsistent behavior :
Occasionally seeing last text and counter of hidden contact- whereas Zen menu considers the group as hidden .
another symptom : hidden group sometime appears with this indication upon incoming message :

Hello.
Now a gray circle appears when a hidden contact sends you the first message.
What you need to do:

Remove the gray circle.
fix the gray circle. The gray circle will appear whenever there is a new message.

Hi,
For now we hold the fixing of this bug until final estimation on #48
If we need to fix it in the future no grey circle should appear. ever.

Implementation changed


How to test changes to Tooling without affecting production?

I have a change to the tooling to remove '.html' extensions inside links.
This is not - I think - necessary. Support for routes without '.html' has been resolved. So changing from explicit links to pages into a route form is just neat, but not necessary.
If I wanted to suggest this change, I would want to test a branch of the tooling on a dev-docs container.
How can this be done?

This is strongly related to https://github.com/Raku/doc-website/issues/217, right?

@2colours yes this is related to #217. I was thinking how to implement a solution to this issue when I came up with the idea in #217. My bad that I did not simply attach the idea to this issue.
But @dontlaugh assigned it to himself and I didn't know if he had done any work on it.

This is strongly related to #217, right?

You're correct. I'm going to close this as a duplicate, and respond over there.


Undefined symbols for architecture x86_64:

"OBJC_CLASS$_SocialAn", referenced from:
objc-class-ref in ViewController.o
objc-class-ref in DetailViewController.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

This doesn't look like a problem with OCMock. Please check how you link all your other code with your tests.

thanks for replies,
I create custom frameword and implement into my project it's working all flow on debug mode but when I create same as release mode it gives error like above mentioned.

Like I said, from the information you provided, there is no reason to believe this has anything to do with OCMock. Regarding issues, please review the contribution guidelines: https://github.com/erikdoe/ocmock/blob/master/CONTRIBUTING.md


Low performance for large SQL statements

Superset parses the same SQL statement multiple times during a single request. For large SQL queries that may take a few seconds to parse each time it quickly adds up to long execution times.
For example, a 172kB SQL query that I tested (selects hundreds of columns in a wide table) takes about 7 seconds to parse (sqlparse.parse) or format  (sqlparse.format). Total query execution in Superset was close to 2 minutes for that query, while actual query execution in the database was around 7 seconds. Majority of the time Superset spent parsing and reformatting that query (stripping comments).
One source of improvement could be refactoring ParsedQuery so it doesn't perform unnecessary SQL parsing and formatting operations. For example, strip_comments method is called multiple time in various is_* methods. Each time it takes SQL statement string, strips comments and returns a string which is later parsed again. It happens even if it was already done previously or during initialisation.
For SQL statements which parsing takes more than a few seconds it quickly adds up, because of calls like is_readonly_query or is_select_query.
Another source of improvement would be to use already parsed queries rather than their string representation that later needs to be parsed again. (e.g. in execute_sql_statement)
How to reproduce the bug
The issue requires a large SQL query that selects hundreds of columns from a very wide table.
Expected results
I would expect Superset to parse a query only a few times per request and avoid unecessary parsing and formatting.
Actual results
Superset parses and formats SQL statement multiple times per request.
Environment

browser type and version: unrelated
superset version: 2.1.0
python version: 3.8.13
node.js version: unrelated
any feature flags active: nothing that could impact this

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Closing this out, since sqlparse is out of the picture with the (in-progress) SIP-117. While that's effectively work in progress, I think it's sufficient to close out this issue as a committed solution to the reported problem. CC @betodealmeida in case they would prefer to keep it open until work is completed.


Fix tests with GeoUtils data.setter and __array_interface__ update

Updating a couple tests that used syntax only supported by the previous __array_interface__ or raised UserWarning due to the new data.setter of Raster.
Will make CI pass once https://github.com/GlacioHack/geoutils/pull/302 is merged.

I finally found the source of the errors (it's been 2 weeks)! Parallelized tests run automatically with pytest-xargs, and this started impacting Raster reading/writing (maybe because of some issue in a low-level dependency).
The issue for tracking this, is that the effect was that sometimes (randomly) the grid was read as full of nodata.
Locally, we rarely run with pytest -n=auto, which is why we could not reproduce it. Here's the fix: 0a59b42
Closed https://github.com/GlacioHack/geoutils/issues/293. In the end, this is not related to floating nodata at all...

Merging this, as only 2 lines have changed: the pytest-xargs fix + the commit hash for the new xdem-data with nodata changed to -9999. We can decide later if we keep this new -9999, or revert to the floating nodata.


Wanted to say thank you.

Not an issue, but wasn't sure how else to reach out to you. I'm using this library in my port of A Dark Room to Arduboy. It's a fantastic font :-)
I'd like to have a thank you to you in the credits. Anything you'd like me to put in there?

Thank you <3
It's great to hear that someone is using it in a game!
You can better reach me in the arduboy forums, my username is botisaurus. ;)
Nah you don't need to put anything there! Save progmem for the actual game haha ;D.


Stair grief V1

Description
It is extremely easy to abuse how stairs work to create evil traps for executive officers and or invading xenos
Reproduction
create this but with reinforced walls

same can be done but even worse with ladders

Fixed with https://github.com/RMC-14/RMC-14/pull/3815

Still an issue with ladders

Fixed for ladders in https://github.com/RMC-14/RMC-14/commit/947a24329db4f989b09058502ab193983b64b08c


Logging when user uploads and delete files.

This PR logs whenever a user uploads or deletes a file.
Uploading Files Example:

Deleting Files Example:

I don't know the background to this. From my perspective, if a file upload is being logged, the log message would be more useful if it also noted the file storage location and folder.


Read string field for Document

Hi, Lior. I would like to make a similarity search, not for a vector of a number, but for a vector of objects  (with a name for each of numbers: [{"name":"a", "value": 0.42},{"name":"b", "value": 0.52}]), is any way to read string value like BinaryDocValues way?

No. The plugin expects a comma separated list of floats after it decodes
the Base64 embedding.
On Sun, Feb 16, 2020, 11:37 AM KTOIA<EMAIL_ADDRESS>wrote:

Hi, Lior. I would like to make a similarity search, not for a vector of a
number, but for a vector of objects (with a name for each of numbers: [{"name":"a",
"value": 0.42},{"name":"b", "value": 0.52}]), is any way to read string
value like BinaryDocValues way?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lior-k/fast-elasticsearch-vector-scoring/issues/41?email_source=notifications&email_token=ABGGISATJB4G46NKHJKCPKTRDECO5A5CNFSM4KWBMJPKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IN2TKCQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGGISFQZRG7VFARVPWEQN3RDECO5ANCNFSM4KWBMJPA
.

Yes, I understand, that current implementation doesn't support this approach, but maybe you know, how to read a string field. I only found the way to get the whole document as a string and convert it to Object, but it dramatically inefficient.

I found:
leafContext.reader().getSortedSetDocValues(fieldName);
It's good for me, thank you for your quick answer!


Maya add render image path to settings

Enhancement
Image rule for renders in Maya is configurable in Settings.

repair action on validator still set hardcoded value

It's Fixed


bqplot breaks ipympl in jupyterlab 3

Describe the bug
When I install both bqplot and ipympl Iget an "Error displaying widget: model not found" with ipympl
To Reproduce
pip install bqplot ipympl
"Error displaying widget: model not found" happens with bqplot
Expected behavior
bqplot and ipympl should work with each other
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Is it JupyterLab?
Could you give us your JupyterLab version and the output of jupyter labextension list?


Restore state for edit controls

This PR adds full support for control state restoration in all mixin controls that are based on FCCtrlEdit.
I had to jump through a few hoops to make this all happen smoothly but the results should all be consistent with the native methods.

Yes this is ready to go.


HIVE-24514: UpdateMDatabaseURI does not update managed location URI

What changes were proposed in this pull request?
When FS Root is updated using metatool, if the DB has managed location defined,
updateMDatabaseURI API should update the managed location as well. Currently it only updates location uri.
Why are the changes needed?
Hive metatool is used for cases where NN changes and the metastore fs root has to be updated. When updating the fs root using metatool, if the databases have MANAGEDLOCATION explicitly defined the tool misses to update the fs root of the managed location.
Does this PR introduce any user-facing change?
Fixes user facing bug for specific fs root change scenario.
How was this patch tested?
Manually in test cluster which has ability to Update FS Root.

retest

retest

recheck

recheck


HTTPConnection on _create_connection doesn't send cookies

Hello,
Currently, _create_connection https://github.com/cobrateam/splinter/blob/master/splinter/request_handler/request_handler.py#L38 doesn't send cookies with the request. Sometimes, this may cause errors.
For instance, if we make an attempt to visit a page which demands auth, and the server answers with 403 (Forbidden), since it won't be able to verify the user, ensure_success_response will fail and visiting the page will not be possible.
What's the right approach to handle it? add cookies to HTTPConnection?

We don't have the request_handler proxy anymore. So, I'm closing this.