Delete task on completion

I have to manually delete a task via the portal each time it completes (successfully or otherwise). Is there an option to delete a task automatically on termination? Otherwise, if I submit a task again, I get the following error message:
-------------------------------------------
The specified task already exists.
RequestId:<whatever>
Time:<whatever>
-------------------------------------------

The reason for this is because we require each "task" or --name to be unique. I think we should solve this by allowing users to submit the same values for paramter --name. Maybe append a datetime string to the end of the 'task name' or something like that.

I think deleting a task is an interesting possibility. Keeping the task around isn't strictly necessary since the main reason we would reference the task (spark app) again is to retrieve logs for it. And we can get logs directly from storage -- the task plays no role in that. Issues could start to prop up in error cases, though.
In the event that the task fails before the Spark output logs are created, deleting the task would make debugging much harder. And if the logs don't exist, there is no way to tell the difference between a task that failed and a task that never existed. So, if you wanted to retrieve status for your Spark app, you couldn't tell the difference between a Spark app that has completed (and been deleted) and one that was never created at all.
As far as appending timestamps goes, it's unclear how we would reference logs in this model. We could write logs to storage in this format:

blob name: <job_id>
blob path: <app-name>/<timestamp>/output.log

But to get logs for any given app name, we would have to prompt users to select which timestamp they want. This is fine for the CLI, but for the SDK that makes a lot less sense.

I don't think the task should be deleted automatically on termination, since, as you say, it might not yet have written logs before failing, and it would make it harder to debug if deleted. Perhaps a command like:
aztk spark task delete --id
is sufficient? It would save me from hunting through the portal for the task to delete it (unless there is some quick way to find it in the portal?

We can explore adding something like that, but I'm not sure what the timeline for that would be.
The current recommendation is just to have different task name each time you submit a spark application.
In the meantime, if you find yourself trying to delete tasks regularly and don't want to use the portal, BatchLabs is a good application to look into. Should make interacting with the Batch service easier in the meantime.

Understood. But changing the task name for each run still leaves completed tasks lying around, and means that a code, run, observe results, code, ... cycle means iterating the task name/id. I'll check out BatchLabs in the meantime.

I'm reopening because I think this issue deserves a little more discussion/thought around what the best approach is.
There is definitely issues with the way tasks exist today, so hopefully we can find a better solution that will allow:

Spark app submission with the same name
Spark app deletion
Spark app listing (with status)


Add ability to order containers in groups

In the "Containers" view / page of the Web UI there should be the option to group a number of containers and give that group a name. For example, this would allow for adding a group named "Shipyard" under which Shipyard related containers could be listed. It would simplify the view greatly when many containers are being managed. The groups would have no deeper meaning than simplifying the aforementioned view / page.

I would like to see this feature as well. What do you think about labels that you could apply to containers and create dynamic groups based on that labels? Or do you prefer a basic grouping feature like e.g. in Jenkins for jobs?

This feature should be automatic when we use the scale command.
Example: when I scale my web server up to 50 instances, it isn't relevant to list these 50 entries.

If anyone has some time to look at this, switching the tables to use: http://ng-table.com/#/grouping/demo-grouping-basic would help with this.


Fixes in contextual layers

Avoid including no needed params to the contextual-layers endpoint, for example: indicatorId https://vizzuality.atlassian.net/browse/LANDGRIF-1134
Fix resolution to 4 https://vizzuality.atlassian.net/browse/LANDGRIF-1130

Alright, in that case I would consider this PR as approved, feel free to merge it. Thanks!


Add prompt lookup decoding

@Wovchena , we have a proposal for optimizing kv cache trimm from @sammysun0711: https://github.com/sammysun0711/openvino.genai/commit/d7a24e5b9282062ef2df15144e1f58504ca811c1, based on parallel for.
It could give 3x speed up for cache update.
Should we apply it as well?


lambda tests should not be triggered from client

I should explicitly run yarn test lambda to test lambda, it should not be triggered by yarn test

since #32 merged, it's not an issue anymore (no lambda, no tests, ha)


add missing dependency

07c85331e replaced the use of distutils.version (which is deprecated)
with the officially recommended packaging package. Declare packaging as
a dependency.

Codecov Report

Merging #83 (5bd67ec) into main (7984ddd) will decrease coverage by 0.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #83      +/-   ##
==========================================
- Coverage   67.37%   67.26%   -0.11%
==========================================
  Files          10       10
  Lines         947      947
  Branches      172      163       -9
==========================================
- Hits          638      637       -1
- Misses        251      252       +1
  Partials       58       58

Impacted Files
Coverage Δ

pglookout/pglookout.py
67.35% <0.00%> (-0.21%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[Android] Fix the display for the website's title after navigation.

This patch is to display the website's title when open multiple URLs and
press the back or forward button.
The event of update title will be fired in render frame host and title will be
compared to the one in navigation entry, if they are same, the update
title event will not be sent to Java layer.
BUG=XWALK-2333

Don't we need tests?

@rakuco The fixing is for displaying the title on tab in XWalkCoreShell, I have verified the title manually.
Refine the test case for navigation and add test case for onLoadFinished to ensure the title is identical.

@lincsoon @axinging @fujunwei PTAL. Thanks

LGTM. Thanks for quick patch.

LGTM

@rakuco

Please backport if needed.


Display Voting Power Modal on First Wallet Connect Only

https://github.com/GeneralMagicio/pairwise-rf6/issues/74

@maryjaf , could you run linter
yarn run lint:fix i think it will resolve most of the warnings


fix(components): fire MenuGroup onPress callback if passed via props …

Please read and mark the following check list before creating a pull request:

[x] I read and followed the CONTRIBUTING.md guide.
[x] I read and followed the New Feature Checklist guide.

Short description of what this resolves:

Closing this in favor https://github.com/akveo/react-native-ui-kitten/pull/1339


Implementation of Softcopy Presentation States

Implementation of GSPS. Focus is on text and graphic annotations, other optional functionality such as shutters, masks, crops, and transformations is omitted, but could be added later.
Tested in Osirix viewer.

Can't seem to add @seandoyle  as a reviewer(?) but would be great if he could take a look also!

Can't seem to add @seandoyle as a reviewer(?) but would be great if he could take a look also!

We will need to add him to the team. However, he should still be able to just a review.

Nice @CPBridge! Looks great at first glance. I will take a closer look and review.
It would be great if we could add support for the LUTs of the grayscale transformation:

Modality LUT
VOI LUT
Presentation LUT
Palette Color Lookup Table

Sure, I'll add in the LUT parts

@hackermd Implementation of the following modules is now complete:

Modality LUT
VOI LUT
Presentation LUT
Palette Color Lookup Table

In order to accommodate these, the scope has broadened to include 3 presentation state IODs:

Grayscale Softcopy Presentation State
Pseudo Color Softcopy Presentation State
Color Softcopy Presentation

The code is feature complete and well tested, so it makes sense to do a full review now. However we should probably test the color and pseudo color files produced in some viewers before merging. We have tested the GSPS in a few viewers (eUnity, Osirix) and it seems to be working fine.

@hackermd Implementation of the following modules is now complete:
* Modality LUT
* VOI LUT
* Presentation LUT
* Palette Color Lookup Table

@CPBridge I don't think you added Palette Color Lookup Table, did you? I will need this for Parametric Map, but can also add this later.

@CPBridge I don't think you added Palette Color Lookup Table, did you? I will need this for Parametric Map, but can also add this later.

I did, but because these attributes exist at the root level of the dataset, I didn't create a highdicom class encapsulating it. I think some way of making this re-usable would be a good idea (you suggested this here) I will think about how to best do this.

@CPBridge we were able to resolve most comments already and get clarity on the coordinate issue (thanks @dclunie for your help).
One remaining topic is the abstraction of Palette Color Lookup Table and the reuse of such an abstraction for Parametric Map. This may require some changes to the API of the pm package, but I think it would be worth it.

@hackermd I have made several refactors as suggested and this is now ready for review. May want to test more in some viewers before finally merging.
Biggest changes are:

Factor out PaletteColorLookupTable into its own class. This is now used by the PseudoColorSoftcopyuPresentationState class, and also added into the ParametricMap class.
Factor out VOILUT into its own class, from which SoftcopyVOILUT is derived. This could now be used elsewhere such as by parametric map, but I stopped short of this breaking change for this PR.
While doing the above I discovered some duplicated logic that I addressed by factoring ReferencedImageSequence into its own class that is now used in a few different places.

Tests are failing in pydicom 2.3.0 and hence CI/CD, but passing with pydicom 2.2.x

Leaving a note here for myself on what still needs to happen as this page is getting messy (cc @hackermd):

Add checks that no image or frame is covered by multiple items of the Softcopy VOI LUT sequence
Factor out the copy_voi_lut functionality into a utility function. Add this to the usage.rst?
Remove the copy_modality_lut parameter and perform this by default if the user does not specify a modality LUT
Consider whether to rebase the ModalityLUT class on Dataset rather than on LUT (my initial gut instinct is to keep it as it is)
Consider how/whether to refactor the presentation state base class to be more general
Figure out how to create ICC Profiles that meet the constraints. Use this to add a test for the case when a user passes a valid profile (this test is currently commented out). Add documentation and possibly built-in profiles that the user can use (all this is probably a separate PR)

@hackermd so are we good to go on this now?


fix: absolute URLs from links in RecursiveUrlLoader

Description
This PR solves an absolute link problem in RecursiveUrlLoader. When the "href" of a link on the page contains an absolute URL, the link is ignored.
Example:  will be ignored when base_url is http://test.com/.
@rlancemartin @eyurtsev

Sorry, I didn't test it with the notebook. I've tested it, and it should be fixed now.

Sorry, I didn't test it with the notebook. I've tested it, and it should be fixed now. @rlancemartin

Thanks! There's a newer PR that overhauls the loader more extensively and should resolve this.
Feel free to have a skim: https://github.com/hwchase17/langchain/pull/7756

I think a bug I have is related to this fix, and is still going on with the changes in this PR:
I found that I can only get a depth of 1 returned.

Example page: https://www.askzeta.com/help

from langchain.document_loaders.recursive_url_loader import RecursiveUrlLoader

url = 'https://askzeta.com'
subdomain = '/help'

loader = RecursiveUrlLoader(
  url=url+subdomain,
  max_depth=100,
  timeout=25)

docs = loader.load()
print(len(docs))

I get only 13 documents, but it should be ~110. 13 is the number of links on the given page. Each of those 13 have, when clicked into, another ~5-10 subpages. The code in this PR, which I copied the code for, specifically from this commit (and the RecursiveUrlLoader in the main branch) only go one layer and do not find more pages for the example link given.
I read over the RecursiveUrlLoader and didn't see anywhere obvious that was causing it to go only one layer deep instead of recursing further. Any ideas? I was hoping to help point this out, for this PR, if it's a bug, before it is pushed out.
If this is not related to the above changes, then never mind! It did seem like it was.

I think a bug I have is related to this fix, and is still going on with the changes in this PR:
I found that I can only get a depth of 1 returned.
* Example page: https://www.askzeta.com/help

from langchain.document_loaders.recursive_url_loader import RecursiveUrlLoader

url = 'https://askzeta.com'
subdomain = '/help'

loader = RecursiveUrlLoader(
  url=url+subdomain,
  max_depth=100,
  timeout=25)

docs = loader.load()
print(len(docs))

I get only 13 documents, but it should be ~110. 13 is the number of links on the given page. Each of those 13 have, when clicked into, another ~5-10 subpages. The code in this PR, which I copied the code for, specifically from this commit (and the RecursiveUrlLoader in the main branch) only go one layer and do not find more pages for the example link given.
I read over the RecursiveUrlLoader and didn't see anywhere obvious that was causing it to go only one layer deep instead of recursing further. Any ideas? I was hoping to help point this out, for this PR, if it's a bug, before it is pushed out.
If this is not related to the above changes, then never mind! It did seem like it was.

I don't think it is related to this PR.
On the site you mentioned, there are no other links when you click on a category (e.g. "General" redirecting to this link: https://www.askzeta.com/help/joint-card-general).
The items displayed on the page are not links (like ), but
 that redirect with JavaScript to another page when the user clicks on them, as can be seen here:

Please see here and ensure it resolves your use case:
https://github.com/langchain-ai/langchain/pull/8502

@gauthier-th If this PR is not needed anymore, could you, please, let me know or close this PR?
If this #8502 does not resolve your use case, please, resolve the merging issues. After that ping me and I push this PR for the review. Thanks!

Fixed with #8502


enableActivityTracking() doesn't work in synchronous JavaScript Tracker

See screenshot. Suspect it's being called before DOM has finalised or something like that...

I couldn't reproduce this. Closing since this was probably fixed unknowingly at some point in the last three years...

7 Jul 2013! Incredibly old ticket


Add attributes and parent pointers in the HTML chapter

This PR adds the attributes and parent properties to ElementNodes, and parent and (empty) children properties to TextNodes. The ElementNode changes are required by later chapters, so it makes sense to do them here, and they also clarify the stack handling in the parser just a little bit.

Thanks, great suggestions. Will merge once everything passes.

Thanks, great suggestions. Will merge once everything passes.


Feature: add value object for Policy for record-keeping

What this PR changes/adds
Policies should be stored alongside ContractNegotiations and ContractAgreements, and for that we need another policy object without an ID.
This PR renames Policy -> PolicyDefinition and introduces a Policy object, that comes without an ID.
Why it does that
To fix a bug during data transfers, where the PolicyArchive could not resolve a policy because the ID was not serialized over IDS.
Further notes
WIP.
Linked Issue(s)
Closes # <-- insert Issue number if one exists
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[ ] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #1365 (d5748d7) into main (eb73b99) will decrease coverage by 0.04%.
The diff coverage is 70.70%.

@@            Coverage Diff             @@
##             main    #1365      +/-   ##
==========================================
- Coverage   67.60%   67.55%   -0.05%
==========================================
  Files         716      717       +1
  Lines       15858    15896      +38
  Branches     1041     1043       +2
==========================================
+ Hits        10721    10739      +18
- Misses       4663     4683      +20
  Partials      474      474

Impacted Files
Coverage Δ

...aspaceconnector/policy/model/PolicyDefinition.java
0.00% <0.00%> (ø)

...api/datamanagement/policy/PolicyApiController.java
80.64% <ø> (ø)

...tamanagement/policy/service/PolicyServiceImpl.java
87.09% <ø> (ø)

...econnector/cosmos/policy/store/PolicyDocument.java
100.00% <ø> (ø)

...s/domain/contract/agreement/ContractAgreement.java
0.00% <0.00%> (ø)

...negotiation/store/SqlContractNegotiationStore.java
82.22% <66.66%> (ø)

...iation/ProviderContractNegotiationManagerImpl.java
90.86% <93.75%> (ø)

...taspaceconnector/core/base/policy/ScopeFilter.java
92.64% <100.00%> (ø)

...ceconnector/contract/ContractServiceExtension.java
95.08% <100.00%> (ø)

...iation/ConsumerContractNegotiationManagerImpl.java
87.78% <100.00%> (-0.06%)
:arrow_down:

... and 21 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eb73b99...d5748d7. Read the comment docs.


do not repeat trust id in logs

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

Service entry can select k8s pods

Yes. Added that condition.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f4dcddc5d55068f6d084eaea427c840fac86e68a
link
true
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

For se + wle, the service account conversion is also base on spiffe

Looks like it needs more thought - I have just left this PR for log changes.

@hzxuzhonghu PTAL when you get chance?

@howardjohn can you PTAL when you get chance?

@istio/wg-security-maintainers Can you PTAL?

@howardjohn can you PTAL when you get chance?

@istio/wg-security-maintainers can you PTAL?


Show publication date next to the version number in overview

Right now, there is no way to see when a data set was published, but I think this is crucial information:

We should display the publication data next to the version information or in a separate column. This is related to #479.

Yes, we can display it as an extra column. However, it is already displayed when you view a published surface:

Okay, nice!

Should this still be added to the Search results as an own column, since the publication date is available on the detail page
in the version button?
If yes, this would need horizontal space in all rows, which cannot be used for long names/tags.
The column header for the publication date should be as short as possible, e.g. "Pub Date" or just "Date".
As alternative - what about a tooltip at the version number?

We need an additional column. The date is more important than the version number, I'd vote to remove the version number and replace it with the date. A search should then only find the highest version of a dataset. Any thoughts @tdbjacobs

Let me make this more specific. We should the date of version 1 and underneath the date of the highest version (if not =1), maybe with a text "last updated on". The "WIP" version is only shown in the search results if there is no published version.

I'm okay with removing the version number and showing a date - although it has one disadvantage: You cannot see by "last update" date alone that a surface is a published surface, only by the little tag label "published", which is still visible.
About the suggestion with the two dates in one date field: I'm not sure that for a user it is clear what that actually means.
Why showing the date of version 1 and not only showing the "last updated on" date and use this also as column header?
So far, every surface instance in the database (so e.g. "WIP" and "Version 1") is an own row in the search result.
Each of them could be shown with a "last update" date.
About hiding the "WIP" version: I think it should not be hidden on the select page, because as a creator or collaborator, I want to see it and be able to edit it. And if a surface is not shared with a user, already now only the published versions are visible,
because the user has no permission to see it.
Maybe I completely misunderstand your proposal?
Probably you mean this: Every related "thread" of surfaces ("WIP"->"Version 1"->"Version 2"->...) should only get one row in the search result? This could be done with an extra widget, some kind of "Version dropdown" like on the detail page
which only shows the versions which apply to the search and filter terms.

I suspect that most of our surfaces will be published once and never
changed. (i.e. they will only have one version)
Therefore, we could probably hide the version number for v1 and only show
the date. But if a surface HAS been updated, then a button appears like
"See older versions". When viewing an older version, it can give info like
"V2, updated 3 May 2020"
(PS - What format are we using for dates? We want it to be US and EU
compatible - so CANNOT use "5/3/20")
-Tevis
Tevis Jacobs
William Kepler Whiteford Faculty Fellow and Associate Professor
Mechanical Engineering and Materials Science
University of Pittsburgh
http://www.engineering.pitt.edu/JacobsLab/
Mail: 636 Benedum Hall, 3700 O'Hara St., Pittsburgh, PA 15261
Office: 538-E Benedum Hall,<PHONE_NUMBER>
@.***
On Fri, Apr 16, 2021 at 11:44 AM Michael Röttger @.***>
wrote:

I'm okay with removing the version number and showing a date - although it
has one disadvantage: You cannot see by "last update" date alone that a
surface is a published surface, only by the little tag label "published",
which is still visible.
About the suggestion with the two dates in one date field: I'm not sure
that for a user it is clear what that actually means.
Why showing the date of version 1 and not only showing the "last updated
on" date and use this also as column header?
So far, every surface instance in the database (so e.g. "WIP" and "Version
1") is an own row in the search result.
Each of them could be shown with a "last update" date.
About hiding the "WIP" version: I think it should not be hidden on the
select page, because as a creator or collaborator, I want to see it and be
able to edit it. And if a surface is not shared with a user, already now
only the published versions are visible,
because the user has no permission to see it.
Maybe I completely misunderstand your proposal?
Probably you mean this: Every related "thread" of surfaces
("WIP"->"Version 1"->"Version 2"->...) should only get one row in the
search result? This could be done with an extra widget, some kind of
"Version dropdown" like on the detail page
which only shows the versions which apply to the search and filter terms.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ContactEngineering/TopoBank/issues/608#issuecomment-821266349,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFOUYWVGTOBPQ6FHDO3IBPTTJBLMVANCNFSM4ZO35EDA
.

I think the best date format is spelling out the month, i.e. "Apr. 3, 2021".
Even if only a single published surface is shown, you can still navigate to WIP by clicking on it and then choosing WIP. I think it is very confusing to a novel user if multiple results of the same surface show up. There should only be a single search result for let's say our UNCD surface.

Hm - I guess we need to rethink what the Search page does. If the user searches for a certain word
and it's used in the description of the WIP surface, but not in the published version, at least then the WIP version should show up.
Similar if some filter values changes, e.g. the category (although this is unlikely, but it can happen).
What about this idea: Instead of a date, there is a dropdown with publication dates or "Work in Progress", like
on the detail page. It would only list the versions which apply to the search and filter terms.
I still think the default version shown should be the WIP version and not the published version, because this is what the user is working with. Wouldn't it be more confusing to show the published version only? Maybe it's better to discuss this in person,
I still don't understand why showing the published version only is an improvement.

Okay, I've talked to Lars. Result:
We keep a column "version" but also show the publication date there, e.g. "1 (Apr. 3, 2021)". There will be
still multiple results according to search term and filters.
Concerning the date format: On the dropdown button on the detail page, I have "Version 1 (2021-04-03)" instead, so
the ISO format, which I personally find more practical in a list than a format with written month names.
However, I could also use "Version 1 (Apr. 3, 2021)" there to make it consistent, if you like.

ISO-format is fine @tdbjacobs any opinion?

fine with iso format. i think it's used commonly enough to be recognized.
-tevis
Tevis Jacobs
William Kepler Whiteford Faculty Fellow and Associate Professor
Mechanical Engineering and Materials Science
University of Pittsburgh
http://www.engineering.pitt.edu/JacobsLab/
Mail: 636 Benedum Hall, 3700 O'Hara St., Pittsburgh, PA 15261
Office: 538-E Benedum Hall,<PHONE_NUMBER>
@.***
On Fri, Apr 16, 2021 at 12:43 PM Lars Pastewka @.***>
wrote:

ISO-format is fine @tdbjacobs https://github.com/tdbjacobs any opinion?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ContactEngineering/TopoBank/issues/608#issuecomment-821301788,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFOUYWRJHUVYWFQKQJUKVNDTJBSKFANCNFSM4ZO35EDA
.


[liquid_handling] fix unawaited machine backend setup

lh.setup() is broken since we don't await the machine backend setup

Smh


Have a My "Snippets" page to view Snippets added my the user

Is your feature request related to a problem? Please describe.
When I add a snippet, I can't see it at the home page. Later if I want to search and edit the snippet, it becomes a tedious task.
Describe the solution you'd like
Have a separate "My Snippets" page where the user can view and edit all the snippets added by him.
Describe alternatives you've considered
Same as mentioned above
Additional context
No additional context.

@ZayedShahcode
Thank you for your enthusiasm! Before moving on to another issue, could you please focus on resolving the current one #33 ? This will help keep the project organised and ensure that progress is made steadily. Once the issue is resolved, feel free to tackle the next one.

Hey @ZayedShahcode I can work on this.

@harish08102004 If you want to work on this issue, i will assign you. Before contributing keep in mind to fetch the develop branch and make a PR for the same

I would like to work on the issue also.

@inkerton That's awesome! 🎉 I really appreciate your enthusiasm—it's great to see you taking on another issue. This will be your second one, and I’m sure you’ll do an amazing job just like before. 🙌 Feel free to reach out if you need any help along the way! 😊

@harish08102004 i will be removing you from the assignees as you haven't updated me science 3 days

Hey @notsoocool I'm working on it.

@harish08102004, I appreciate your interest, but @inkerton has already resolved the issue. If you'd like, you can choose another issue to work on.

Ohh I almost finished.

Ohh I almost finished. Ok no issues.

I am sorry but you haven't updated me since 3 days thats why i had to assign it to others, feel free to work on other issues as well


operator - unclear which component fields should be --set from

Using the operator, I want to the set the outboundTrafficPolicy. In helm this is --set global.outboundTrafficPolicy.mode=REGISTRY_ONLY
Attempts in the operator:
$ ik x manifest generate --set global.outboundTrafficPolicy.mode=REGISTRY_ONLY
bad path=value: global.outboundTrafficPolicy.mode=REGISTRY_ONLY
$ ik x manifest generate --set values.outboundTrafficPolicy.mode=REGISTRY_ONLY | grep ALLOW_ANY
      mode: ALLOW_ANY  # The overlay did not do anything
$ ik x manifest generate --set trafficManagement.components.pilot.values.outboundTrafficPolicy.mode=REGISTRY_ONLY
bad path=value: trafficManagement.components.pilot.values.outboundTrafficPolicy.mode=REGISTRY_ONLY

Its not clear to me what the expected behavior is and what I am doing wrong. Not sure if this is a bug or docs/UX issue

Since you're accessing the values field in the IstioControlPlaneSpec API, it should be
ik x manifest generate --set values.global.outboundTrafficPolicy.mode=REGISTRY_ONLY
Give that a shot @howardjohn.

ahh .values.global, I think thats the one combination I didn't try. That seems to work. Thanks


Decide whether to use testpypi like a conda dev channel

It's possible (have tried it out), and it seems to work fine.
If going down this route, would modify pip releases to upload to testpypi as well as pypi (in the same way that conda releases are added to pyviz/label/main and pyviz/label/dev).

Is there demand for this?

I don't know, but I doubt it (because testpypi is not generally a source people consider using).
I've used it for our packages, e.g. where A depends on B and C. I can do "dev" releases of B and C to testpypi, then a dev build of A. The dev build of A might fail because B or C is missing something/buggy. So I repeat, developing B and C until they actually provide what A needs. At that point, I can release B and C on pypi once, and then A.
I.e. like pyviz/label/dev vs pyviz/label/main

I'd say to use it if it helps with your release process, but otherwise seems like we have no reason to make anything available there.

pypi now seems to support pre-releases:

Previously, 1.8.0a1 would have appeared to be the current version on pypi (i.e. showing up by default), which was very confusing.
pip's behavior is still the same:
$ pip install param
[...]
Successfully installed param-1.7.0

$ pip install --pre --upgrade param
[...]
Successfully installed param-1.8.0a1

(note that unlike with conda, --upgrade or a version specification is necessary for pip if you already have a version of param installed)
I think we should consider putting dev releases on pypi.

(the param dev release mistakenly went to pypi because of a recent mistake I made editing param's travis file...)


Fix incorrectly grouped search_strings in the ripgrep script

Some keys were wrongly categorised.
It doesn't matter if you run it as-is but I was commenting out sections to concentrate on one set of APIs at a time.
When I got to User defaults I was very confused! 😄

Thanks a lot 👍


joinImages is not a function

framework: Nuxt 3
file: server/api/image.ts
import joinImages from 'join-images';
export default defineEventHandler(async (event) => {
joinImages(['image-1.png', 'image-2.png']).then((img) => {
// Save image as file
img.toFile('out.png');
});
return image
})
error:
[nuxt] [request error] joinImages is not a function   at /F:/wordpress/nuxt3/nuxt-app/.nuxt/dev/index.mjs:409:3   at async /F:/wordpress/nuxt3/nuxt-app/node_modules/h3/dist/index.mjs:417:19   at async Server.nodeHandler (/F:/wordpress/nuxt3/nuxt-app/node_modules/h3/dist/index.mjs:367:7)

framework: Nuxt 3 file: server/api/image.ts
import joinImages from 'join-images'; export default defineEventHandler(async (event) => { joinImages(['image-1.png', 'image-2.png']).then((img) => { // Save image as file img.toFile('out.png'); }); return image })
error:
[nuxt] [request error] joinImages is not a function at /F:/wordpress/nuxt3/nuxt-app/.nuxt/dev/index.mjs:409:3 at async /F:/wordpress/nuxt3/nuxt-app/node_modules/h3/dist/index.mjs:417:19 at async Server.nodeHandler (/F:/wordpress/nuxt3/nuxt-app/node_modules/h3/dist/index.mjs:367:7)

I had this same problem. I managed to solve it by changing the import: import * as ji from 'join-images';
and then using the function:
ji.joinImages(...)
I hope it helps you

thank you! Your reply solved my problem


Use --target=web also for WebWorkers

Brought this PR https://github.com/thedodd/trunk/pull/624 here as well :)
Before this can be merged I should implement the changes discussed in the linked PR.

Closing since trunk main seems to have been revived :)

Not yet, but we can re-open if it doesn't work out.


gnome3.gnome-control-center: 3.34.1 -> 3.34.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gnome-control-center/versions.
meta.description for gnome3.gnome-control-center is: '"Utilities to configure the GNOME desktop"'.
meta.homepage for gnome3.gnome-control-center is: '""

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.34.2 with grep in /nix/store/678a4j3f1pzl6piy4x351mflrzh8hfd1-gnome-control-center-3.34.2

directory tree listing: https://gist.github.com/7dbc19eeb1432ab6140d0f398d57f970

du listing: https://gist.github.com/1bb72f29d94684b1d2f4d4fc66dd6f2e

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
gnome3.gnome-control-center
gnome3.gnome_control_center

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/678a4j3f1pzl6piy4x351mflrzh8hfd1-gnome-control-center-3.34.2 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A gnome3.gnome-control-center https://github.com/r-ryantm/nixpkgs/archive/9c063f4080ab6a8d69da0f3c5a5871c11892fee7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/678a4j3f1pzl6piy4x351mflrzh8hfd1-gnome-control-center-3.34.2
ls -la /nix/store/678a4j3f1pzl6piy4x351mflrzh8hfd1-gnome-control-center-3.34.2/bin

cc @lethalman @jtojnar @hedning @worldofpeace for testing.

Runs without problems. News:

Updated translations

Applications

Fix a memory leak

Background

Fix crash if a BgRecentSource is unreffed during an async operation

Display

Use correct mode for supported scale checking

Printer

Provide a scheme to address parser

User Accounts

Fix password dialog crashes and hangs

Note that 3.42.3 will be hardcoding usermod path. https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/653#note_678656


Update CI config for main branch, update changelog

#141  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Add unset default project column

Close: https://github.com/go-gitea/gitea/issues/23401

Need to find a new icon for it.

Codecov Report

Merging #23531 (d84c968) into main (f521e88) will increase coverage by 0.00%.
The diff coverage is 44.01%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff            @@
##             main   #23531    +/-   ##
========================================
  Coverage   47.14%   47.15%
========================================
  Files        1149     1154     +5
  Lines      151446   152276   +830
========================================
+ Hits        71397    71803   +406
- Misses      71611    71993   +382
- Partials     8438     8480    +42

Impacted Files
Coverage Δ

cmd/dump.go
0.67% <0.00%> (ø)

cmd/web.go
0.00% <0.00%> (ø)

models/actions/run.go
1.64% <0.00%> (-0.08%)
:arrow_down:

models/packages/package.go
45.45% <0.00%> (-1.13%)
:arrow_down:

models/user/search.go
77.50% <0.00%> (-6.29%)
:arrow_down:

modules/actions/github.go
0.00% <0.00%> (ø)

modules/actions/workflows.go
0.00% <0.00%> (ø)

modules/doctor/storage.go
31.93% <0.00%> (ø)

modules/setting/git.go
45.45% <ø> (ø)

modules/storage/minio.go
1.51% <0.00%> (-0.06%)
:arrow_down:

... and 49 more

... and 8 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Still searching for a better icon?

It seems that there are no good unpin icons.
Created an icon request issue: https://github.com/primer/octicons/issues/940

CI failure related

Should we wait for https://github.com/primer/octicons/issues/940
It seems they are working on this.

Should we wait for primer/octicons#940 It seems they are working on this.

I think we can wait for a few days.

I wouldn't wait, just go with the pin icon for now.


configurable scroll hide timeout

Currently hide timeout is hard coded to one second
Can we have configurable timeout

That makes sense. Also this could be defined in CSS with some transition delays instead of in the JS. Would be easier to customise.

CSS looks nice
But actually I just copied your code into my app converted into typescript (my project is in typescript) and added timeout using data attribute

Closed in<EMAIL_ADDRESS>


Make it faster!

First I have removed Flask-Migrate/Alembic as it is not really needed and does not work if c3bottles has been installed like we describe in the documentation. In addition, the second migration fails for SQLite which I use a lot for testing, so I simply dropped Flask-Migrate. Our models and the setup are so simple that we do not need it anyway.
Apart from small cosmetic cleanups, the main change is adding a state column to the drop point table. Before, when querying all drop points and their states (like for the map or the list), that would trigger one select for all the drop points and then another two queries for every single drop point to calculate its state. When adding the state to the database explictly, only one single query is needed.
Before:
In [5]: %timeit [dp.last_state for dp in drop_point.DropPoint.query.all()]
11.4 ms ± 41 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)

After:
In [10]: %timeit [dp.last_state for dp in drop_point.DropPoint.query.all()]
466 µs ± 2.4 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

This is for a small dataset and gets even better, the more drop points and reports there are.
By doing something similar with the calculation of visit priority, we probably will be able to increase performance even further.
In addition, now that we set the state explicitly for every drop point, we can add this to the Prometheus metrics properly via labels. looks at @J-Ha

There is more:

[ ] location (this needs changing the location constructor so that we can construct locations in memory, serialize them and add them to the drop point table)
[ ] count and weight of new reports (since the last visit) for priority calculation
[ ] total report and visit count

The goal would be to be able to query all relevant properties of drop points (apart from details of past reports, visits and locations which are only shown in the history for a single drop point) from one single request to the database for all drop points at once.


docs coverage are not always correct

In some situations such as gtk-rs/gstreamer-rs where the docs can't be shipped with the crate for license reasons, it causes a very very low docs coverage which is often not true.
See https://docs.rs/crate/gstreamer/0.16.7 for example.
cc @GuillaumeGomez

Thanks for opening the issue!
Explanations: it'd require to run the build.rs script with the docs.rs features provided and that's pretty much it.

I'll send a fix tomorrow.

Interestingly enough, we use prepare_commands which uses in turn Metadata::cargo_args. So normally, the features should be set when running the command. Seems like a bigger issue than expected. :)

This is not a docs.rs bug. The issue is that the build script fails to generate the docs (which you can see passing -vv to the build script):
[gstreamer 0.16.7] Cannot open 'src/toc_serde.rs': Read-only file system (os error 30)
[gstreamer 0.16.7] Cannot open 'src/typefind.rs': Read-only file system (os error 30)
[gstreamer 0.16.7] Cannot open 'src/utils.rs': Read-only file system (os error 30)
[gstreamer 0.16.7] Cannot open 'src/value.rs': Read-only file system (os error 30)
[gstreamer 0.16.7] Cannot open 'src/value_serde.rs': Read-only file system (os error 30)

We don't allow writing to the source directory; if you want to generate code, you have to output it to OUT_DIR. I'd suggest also changing gstreamer-rs-lgpl-docs to give a hard error if generating docs fails.

Unfortunately, we update the source code files, so that's not possible to simply write to OUT_DIR. Any way how we could go around that limitation? Because otherwise, the doc generated on docs.rs is really the bare minimum...

Rather than updating the source files in place, you could generate a parallel tree of source files into OUT_DIR and include! them. Even outside of docs.rs modifying the files inside ~/.cargo/registry/src is not a good setup, that directory is assumed immutable by a lot of tooling.

It's not possible either, unless we add include! on all items which would include empty files all the times unless we fill them. It'd literally kill compilation time. So not an option. :-/

The include! on all the items would be cfg-conditional though, right? And so it would only affect compilation time with that feature turned on?
#[cfg_attr(feature = "embed-lgpl-docs", doc = include!(concat!(env!("OUT_DIR"), "...")))]

(one addition downside is that it makes embed-lgpl-docs nightly-only until after https://github.com/rust-lang/rust/pull/83366 makes it into stable, if it's not nightly-only already)

But that would mean one file for every item. That seems like a horrible idea. Anyway, we decided to simply not generate anything on docs.rs. Makes things simpler on our side. We will provide full documentation on our side.


Release v24.9.1

Description
Release v24.9.1.
Remove optional [cite] dependency from PyBaMM as per this issue. This will be added back in a future patch release once PyBaMM releases their v24.9.1 patch.
Issue reference
Fixes # (issue-number)
Review
Before you mark your PR as ready for review, please ensure that you've considered the following:

Updated the CHANGELOG.md in reverse chronological order (newest at the top) with a concise description of the changes, including the PR number.
Noted any breaking changes, including details on how it might impact existing functionality.

Type of change

[ ] New Feature: A non-breaking change that adds new functionality.
[ ] Optimization: A code change that improves performance.
[ ] Examples: A change to existing or additional examples.
[ ] Bug Fix: A non-breaking change that addresses an issue.
[ ] Documentation: Updates to documentation or new documentation for new features.
[ ] Refactoring: Non-functional changes that improve the codebase.
[ ] Style: Non-functional changes related to code style (formatting, naming, etc).
[ ] Testing: Additional tests to improve coverage or confirm functionality.
[ ] Other: (Insert description of change)

Key checklist:

[ ] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All unit tests pass: $ nox -s tests
[ ] The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.
Further checks:

[ ] Code is well-commented, especially in complex or unclear areas.
[ ] Added tests that prove my fix is effective or that my feature works.
[ ] Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

Thank you for contributing to our project! Your efforts help us to deliver great software.

I've confirmed the testing suite passes when this release branch is installed locally via pip. It's now ready for review.


Constraint “unique_role_per_person_in_metadata” is violated.

Constrained is always violeted from django admin when inserting a new role for a person

fixed by 8cfb261da31214cbb25d2c602b15271cf782af65


Note taking MVP meeting 18 May 2023

Please add notes as comments below.
See also https://github.com/alan-turing-institute/Living-with-Machines/issues/3211

Closing this as it fed into the lwmdb roadmap.


Unflake InteropReliabilityTests

This is a continuation of https://github.com/aspnet/AspNetCore/pull/13226. There are a few more cases where InteropReliabilityTests interacts with the client without waiting for an explicit outcome. Those tests show up in the CI analytics as unreliable.
I'm removing the [Flaky] attributes here because we have reason to believe they shouldn't be flaky any more, and if we don't remove it now, we don't (yet) have any system for knowing it's time to remove it in the future.

Oh, just found out these are already fixed (in exactly the same way) in release/3.1. I didn't realise because they haven't propagated to master yet.
Closing this PR as redundant.


Receive multiple data buffers over UART using interrupts

Hi, I am trying to receive data over the UART0 peripheral through interrupts. I am following example 4 (Usage-4) from the hx_drx_uart.h header file.
I would like the uart_dma_rx_cb()  interrupt service routine to be triggered every time the rx_buffer becomes full with new data. However, with the example code, the callback function is triggered only the first time that the rx_buffer becomes full. Therefore, I believe that it is necessary to somehow lower the flag that is raised for the interrupt so that the callback may be triggered again.
What changes could I make to accomplisht that?
Here is my current code:
Global variables
uint32_t g_datasize = 0;
volatile  uint8_t rbuffer[8];
DEV_UART_PTR dev_uart_ptr;
DEV_BUFFER rx_buffer;

Main function:
int app_main(void)
{
    printf("Init UART...\r\n");
    // Initialize UART 0
    hx_drv_uart_init(USE_DW_UART_0, HX_UART0_BASE);

    uint32_t data_size = 8;

    memset(rbuffer, 0x00, data_size);
    g_datasize = data_size;
    rx_buffer.buf = (void *)rbuffer;
    rx_buffer.len = g_datasize;

    dev_uart_ptr = hx_drv_uart_get_dev(USE_DW_UART_0);
    dev_uart_ptr->uart_open(UART_BAUDRATE_921600);
    dev_uart_ptr->uart_control(UART_CMD_SET_RXCB,  (UART_CTRL_PARAM)uart_dma_rx_cb);
    dev_uart_ptr->uart_control(UART_CMD_SET_RXINT_BUF, (UART_CTRL_PARAM)&rx_buffer);
    dev_uart_ptr->uart_control(UART_CMD_SET_RXINT, (UART_CTRL_PARAM)1);

    while(1) {
        printf("Hello\r\n");
    };

    return 0;
}

Callback function:
void uart_dma_rx_cb(void)
{
    int i;
    xprintf("Transfer : RX Done\r\n");
    xprintf("Data Received: \r\n");
    for (i = 0; i < g_datasize; i++)
        printf("0x%02x,", rbuffer[i]);
    memset(rbuffer, 0x00, g_datasize);
}

The  uart_pinmux_cfg() function that I call from pinmux_init() is:
void uart_pinmux_cfg()
{
   // UART0 pin mux configuration
   hx_drv_scu_set_PB0_pinmux(SCU_PB0_PINMUX_UART0_RX_1, 1);
   hx_drv_scu_set_PB1_pinmux(SCU_PB1_PINMUX_UART0_TX_1, 1);
}

Hi @epibaikas,
Sorry we didn't explain clearly how to use uart API.
After receiving UART data, UART RX should be enabled again to receive incoming data.
You can modify the uart_dma_rx_cb() function as follows.
void uart_dma_rx_cb(void)
{
    int i;
    xprintf("Transfer : RX Done\r\n");
    xprintf("Data Received: \r\n");
    for (i = 0; i < g_datasize; i++)
        xprintf("0x%02x,", rbuffer[i]);
    memset(rbuffer, 0x00, g_datasize);
    dev_uart_ptr->uart_control(UART_CMD_SET_RXINT_BUF, (UART_CTRL_PARAM)&rx_buffer);
    dev_uart_ptr->uart_control(UART_CMD_SET_RXINT, (UART_CTRL_PARAM)1);
}


⚠ Bofrost.hr has degraded performance

In 9ef71fd, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 2886 ms

Resolved: Bofrost.hr performance has improved in d238be9 after 7 minutes.


Typo "@user_defined_event_id"→"@user_defined_event_id"

Italic with escape characters
https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-audit-write-transact-sql?view=sql-server-2017

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Correction confirmed. Thanks.


python3Packages.ircstates: 0.11.5 -> 0.11.6; python3Packages.ircrobots: 0.3.5 -> 0.3.6

Motivation for this change
New upstream release.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 105703 run on x86_64-linux 1

1 package failed to build:

python39Packages.ircrobots

5 packages built:

python37Packages.ircrobots
python37Packages.ircstates
python38Packages.ircrobots
python38Packages.ircstates
python39Packages.ircstates

waiting for ofborg to finish

Result of nixpkgs-review pr 105703 run on x86_64-darwin 1

1 package failed to build:

python38Packages.ircrobots

5 packages built:

python37Packages.ircrobots
python37Packages.ircstates
python38Packages.ircstates
python39Packages.ircrobots
python39Packages.ircstates

Result of nixpkgs-review pr 105703 run on x86_64-linux 1

1 package failed to build:

python39Packages.ircrobots

5 packages built:

python37Packages.ircrobots
python37Packages.ircstates
python38Packages.ircrobots
python38Packages.ircstates
python39Packages.ircstates


IPFS Berlin Meetup - May 2nd 2016

Hi all,
We're planning on having an IPFS Berlin Meetup around Squatconf. The current dates we're thinking are Thursday the 28th and Monday the 2nd of May.
Proposed locations are: C-Base and CoUp. Anyone well-connected to C-Base who could check if they can host us? @bergie @lgierth?
If anyone has suggestions for other places that could host us, let me know.
Follow this thread for more information!

I'm not available on 28th, but 2nd would work.
There seems to be a Sailfish OS meetup in the evening, but we could probably fit IPFS too at c-base https://www.c-base.org/cal/day.php?cal=regular,termine&getdate=20160502
The best way to check that is to get in touch with cultorga.

I am in Berlin for 29th to 7th, so Squatconf and following week.

I've emailed C-Base re. 2nd of May. Co.up would be able to host on the 28th (they have room for 75+ ppl). Will give an update as soon as I have more information.

IPFS Berlin Meetup will happen on Monday the 2nd of May
We have secured C-Base as the meetup location \o/ More info to follow.

Awesome!
BTW: sorry, it's looking way less likely that I can make May 2nd :(  i have to be at http://www.coindesk.com/events/consensus-2016/

(feel free to have the meetup without me, plenty of ipfs folks in berlin)

We have finally an official event announcement & registration online, see here: https://www.eventbrite.com/e/ipfs-berlin-meetup-tickets-24998261473
If you're coming, please register as we have limited seats (70). Feel free to spread to word and invite people who might be interested. Hope to see you all there on Monday!

If you'd like to present something and give a (short) talk, please let us know! We currently have the following talks:
Agenda
Introduction to IPFS (10min).
Davis Dias -- IPFS core dev and member of Protocol Labs -- will attempt a short but deep introduction to The IPFS Project. This should give enough context for newcommers to follow the rest of the talks.
Registry Mirror -- NPM on IPFS. (20min)
David Dias -- IPFS core dev and member of Protocol Labs-- will speak about registry-mirror and package management. IPFS is fantastic for package managers, because of its decentralized, secure, and permanent linking. registry-mirror is a node.js module that makes it so you can install npm packages directly from IPFS, peer-to-peer!
Orbit -- Distributed p2p chat on IPFS. (15min)
Samuli Poyhtari -- IPFS core dev and member of Protocol Labs -- will speak about Orbit, a distributed p2p chat on IPFS. Think decentralized Slack or IRC! This talk will demo it, discuss how it works, and its components. And we will discuss how we can build realtime apps on IPFS.
IPFS dead drop -- Publish Files to IPFS from USB stick (15min)
Uwe Kamper -- IPFS contributor and C-Base member -- will talk about IPFS Dead Drop, an anonymous, offline, peer to peer file-sharing network in public space. Located at C-Base, you plug a USB memory into the dead drop device and it will automatically access the memory stick and publish all the files on the web using IPFS. After files have been published, you'll get a shareable link to your files. Uwe will present the project and you can give it a go at meetup premises at C-Base.

We have one more lightning talk for the meetup:
IPFSDroid  -- Making IPFS an implementation detail on android for now (5min?)
Markus Ligi. This is a lightning talk to spark conversation about IPFS on Android.

There will be a talk from Ascribe/BigchainDB also (don't have the details yet).
Also, we'll be live streaming the meetup talks! Will post links tomorrow before starting the meetup.

This is happening tonight!
It was pointed out to me that the entrance to c-base is "non-standard", so here's a little more details on how to find it:
If you come from S/U-Bahn Jannowitzbrücke, walk across the river and after the bridge, take a left and walk all the way down to the river. There's a narrow sidewalk that takes you further, keep walking. You'll come to the end of it and think "can't get further" but not to worry! Continue towards the trees, walk up towards the little garden and you'll see the building under construction up ahead. Keep walking further, past the building being renovated and you'll finally reach the house c-base is located at (the red building).
We'll try to put up some posters, arrows or stickers along the way.

What time does the Meetup start?

Due to a organizational mishap, we don't have snacks at theeetup. Sorry everyone.
The meetup will start at 1900 (7pm).

LIVE(tm) STREAM: https://www.youtube.com/watch?v=UOC_QqtEJtg

Thanks everyone! Was great to watch the Livestream.
Let's do another one. For now, closing this.

This was a great meetup! Was especially blown away by the implications of the orbit demo / dynamic apps on IPFS  - great stuff! Also the follow-up was great - I now have a real IPFS node running on android - thought I will stick to mocks/centralized solutions way longer. The future is bright - hope there will be one more IPFS meetup this year in Berlin!


v0.3.11 error win32 x64

:warning:Please attach %TEMP%\vscode-java-installer\log.txt and %TEMP%\vscode-java-installer\AdoptOpenJDK-MSI.log for more details.
version: 0.3.11
env:
JAVA_HOME: undefined
PATH:
C:\Program Files (x86)\Common Files\Oracle\Java\javapath
C:\ProgramData\Oracle\Java\javapath
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\WINDOWS\System32\WindowsPowerShell\v1.0\
C:\WINDOWS\System32\OpenSSH\
C:\Program Files\Git\cmd
C:\Program Files\Java\jdk1.8.0_131\bin

C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
C:\Users\Mohammad\AppData\Local\Microsoft\WindowsApps
C:\Users\Mohammad\AppData\Roaming\Dashlane\6.1839.0.13410\bin\Firefox_Extension\{442718d9-475e-452a-b3e1-fb1ee16b8e9f}\components
C:\Users\Mohammad\AppData\Roaming\Dashlane\6.1839.0.13410\ucrt
C:\Users\Mohammad\AppData\Roaming\Dashlane\6.1839.0.13410\bin\Qt
C:\Users\Mohammad\AppData\Roaming\Dashlane\6.1839.0.13410\ucrt
C:\Users\Mohammad\AppData\Roaming\Dashlane\6.1839.0.13410\bin\Ssl
C:\xampp\php
C:\xampp\mysql\bin

C:\Users\Mohammad\AppData\Local\Programs\Microsoft VS Code\bin
JDKs:

log:
[4:58:20 PM] AdoptOpenJDK-11-x64
[5:02:43 PM] Download JDK ... [Completed]
[5:02:43 PM] Install JDK
[5:02:43 PM] Installing AdoptOpenJDK-11-x64...
[5:02:47 PM] Error occurred
[5:02:47 PM] Error: Command failed with exit code 1618: C:\WINDOWS\System32\msiexec.exe /i "C:\Users\Mohammad\AppData\Local\Temp\vscode-java-installer\binaries\jdk\11\x64\OpenJDK11U-jdk_x64_windows_hotspot_<IP_ADDRESS>_1.msi" MSIINSTALLPERUSER=1 ADDLOCAL=FeatureJavaHome,FeatureEnvironment,FeatureJarFileRunWith /passive /l*v "C:\Users\Mohammad\AppData\Local\Temp\vscode-java-installer\AdoptOpenJDK-MSI.log"
Another program is being installed. Please wait until that installation is complete, and then try installing this software again.

1618 is a Windows error code that means: "Another installation is already in progress. Complete that installation before proceeding with this install."

Java on VS Code requires JDK 11, it tried installing a JDK 11. But you seemed to have unfinished installation running, the AdoptOpenJDK installer just failed with code 1618. Can you terminate other installation or reboot your machine, and then give it a retry?

1618 is a Windows error code that means: "Another installation is already in progress. Complete that installation before proceeding with this install."

Java on VS Code requires JDK 11, it tried installing a JDK 11. But you seemed to have unfinished installation running, the AdoptOpenJDK installer just failed with code 1618. Can you terminate other installation or reboot your machine, and then give it a retry?


✨  Some Changes In CSS Normalizer

✨  Some Changes In CSS Normalizer.
I have used some other css normalizer (reseter.css.
Hope You Like And Implement It :)

Thank you for the pull request, but after further revisions the code you provided alters too many elements. We'll take in consideration reseter.css if we decide to drop normalize.css in future major versions of Skelet.css


Improve GHE Docs

Link out to the official GHE API docs where it mentions that GitHub Apps are enabled via an early access preview. See here for that link.

I manually updated the website submodule to get this change published right away instead of waiting until the next release. https://github.com/probot/probot.github.io/commit/874fbdd5ec5fe3a7d3f0ecf3a499208001e2eb88


Crash when using marketplace

Hi folks
Error description
Sadly I am encountering a crashing error every time I try using the Anno 1800 market place (does not matter weather I try to place it normally from the menu or copy paste it) with the following log:
https://pastebin.com/gbUfkmZR
Reproduction (sort of):
I'm not sure, but I think I was experimenting with giving buildings other colors than they normally have and now every time I spawn a market place from the menu it turns out gray instead of its old color and the designer crashes instantly 😭
Solution attempt
I tried to get rid of the error by removing the program code, unpack it again from the zip.. but that did not change anything.. so there must be any persistent settings data somewhere... where is that? 😄 maybe deleting that would help?
I hope I can help improve the designer 😄 NICE WORK anyway 👍 thx take care

Abt the color changing : it seams i forgot to give the marketplace a standard color... will be fixed as soon as i release the new presets/color json files

I don't think we store anything that may cause that in user settings - if you want to double check, you can reset the user settings by deleting the C:\Users\<your user name>\AppData\Local\AnnoDesigner folder.
I am able to reproduce this - its this building specifically:

Turning off the "Show True Influence Range" option stops the issue.

Looks like its caused when the first building placed is an Anno 1800 building and it has an influence radius.
The call to max() throws an exception as AnnoCanvas.PlacedObjects is empty when RenderObjectInfluenceRadius is called. The PlacedObjects list is then used in the erroring code.

@AgmasGold oh.. turning off that feature is sad :( as I really like it and it is really useful for optimizing city layout 😉 But thx anyway for the info.
Is there anything I can help you with?

You should be able to switch it back on again once you have at least one other building that doesn't have an influence range placed onto the screen. We already have a fix created that will be in the next release.

@AgmasGold actually I tried out to disable the true influence radius.. but the crash keeps coming up. I also removed the C:\Users\<your user name>\AppData\Local\AnnoDesigner - files.. still no change. I uploaded my file so maybe you can find another clue :)
Ultimatives Zentrumsviertel V2.zip
When loading the file I cal easily reproduce the crash by dragging a select rectangle over a huge area covering several streets and the 2 buildings.

@Riesenmumpitz I think I could reproduce the issue.
When opening your layout quickly selecting and unselecting buildings there could be a crash.
This should also be fixed with PR #199.
I also think it is unrelated to your original issue.
If you want to give it a try you could use a version which is based on PR #199:
Anno.Designer.PR199.zip
Please give it a try and give feedback. As you are still having troubles I reopen the issue.

@FroggieFrog I just tried PR199 out and it works fine 😃

loading my file
placing the market place in it or a new file
turning the option true influence radius on
nice 👍

I'm glad we could help.
The next official update will of course contain those fixes. So please update if it available.


add installation test

As title, but oar -h fail to run, @rioliu-rh do you happen to know why?
MacBook-Pro:release-tests jianzhang$ make install
python3 -m pip install --upgrade pip && pip3 install -e . && oar -h
...
Successfully installed oar-0.1.dev108+ge88dabe
Traceback (most recent call last):
  File "/opt/homebrew/bin/oar", line 5, in <module>
    from oar.cli.__main__ import main
ImportError: cannot import name 'main' from 'oar.cli.__main__' (/opt/homebrew/lib/python3.11/site-packages/release_tests-1.0.0-py3.11.egg/oar/cli/__main__.py)
make: *** [install] Error 1

MacBook-Pro:release-tests jianzhang$ oar -h
Traceback (most recent call last):
  File "/opt/homebrew/bin/oar", line 5, in <module>
    from oar.cli.__main__ import main
ImportError: cannot import name 'main' from 'oar.cli.__main__' (/opt/homebrew/lib/python3.11/site-packages/release_tests-1.0.0-py3.11.egg/oar/cli/__main__.py)

/approve
/lgtm

Anyway, merge it first for Prow testing.

@jianzhangbjz from this article https://stackoverflow.com/questions/49836676/error-after-upgrading-pip-cannot-import-name-main,  seems like we need to upgrade pip with sudo

I can run this cmd successfully from my local


nixos/zathura: init

Description of changes

This commit adds zathura as a module for nixos.
It allows for setting options and extra config on a system level.
Credit to the home manager module which this pull request is heavily inspired on.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module
[x] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I can understand porting nixos modules to HM but is the reverse judicious (double the maintainance etc) ?

system-wide module for a pdf reader 🙄

The point is for users who don't use HM or users who want to set a systemwide configuration.
I can see the downside of having double the maintenance.
But if NixOS can provide the interface for configuration of so many other things, why not also this?

wdym @Kranzes?

@Alexnortung It's not specific to your PR, sorry it falls on you ^^  the code duplication between home-manager and nixpkgs concerns me, especially if it deals with something non-fundamental like a pdf-reader, wouldn't it be simpler to install it though the home-manager module ?

But if NixOS can provide the interface for configuration of so many other things, why not also this?

because HM was not possible/harder to use as a module. For a datapoint, I've added a neovim module to nixpkgs but I now regret it as it's not in sync with HM and is unnecessarily confusing.

Thanks for the answer, that makes sense. I totally agree that code duplication is bad and I understand your concern. Howerver do we lose anything by adding the module other than it would mean more maintainability?
Maybe I see the potential gain to be greater than the downside and I understand why others may not, since it is already in HM.


babel-runtime error

I get TypeError: "Cannot call a class as a function" error both in node v0.12.5 and in node v0.10.39. package.json lists le_node as v1.0.8
My code is just the example code:
var Logger = require('le_node');
var log = Logger({
  token:[redacted]
});

module.exports = log;

Any idea what's going wrong and how to fix it?
Trace:
./node_modules/le_node/node_modules/babel-runtime/helpers/class-call-check.js:5
    throw new TypeError("Cannot call a class as a function");
          ^
TypeError: Cannot call a class as a function
    at exports.default (/home/bshaya/Documents/rest/Flik/node_modules/le_node/node_modules/babel-runtime/helpers/class-call-check.js:5:11)
    at Logger (/home/bshaya/Documents/rest/Flik/node_modules/le_node/lib/node_modules/logger.js:135:3)
    at Object.<anonymous> (/home/bshaya/Documents/rest/Flik/services/logentries.js:2:11)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/bshaya/Documents/rest/Flik/app/Flik3.js:21:11)

needed to use "new Logger({" instead of "Logger({"


chore(main): release 1.1.1

:robot: I have created a release beep boop
1.1.1 (2022-11-11)
🧹 Miscellaneous

call correct build command during release (0575bc9)
fix lint issues (2994c9a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/tobiasdiez/nuxt-graphql-server/releases/tag/v1.1.1 :sunflower:


Add check for Logger check for Type AWSCW and Space

The combination of Space and Type=AWSCloudWatch will cause an exception. This will provide the user with a more verbose error

@IanTracyLC thank you for you PR, apologies for not watching Greengo closely recently. I hope I'll get my hands to finishing v2 on a break.


phase2 - ignition - reverting etcd-container image back to  etcd:2.2.1

With the ignition image having etcd:3.0.4, we have observed issue, volume can not be detached from the node after pod is deleted.
This issue is producible on Kubernetes Release v1.5.3,  which is working fine with etcd:2.2.1.
Issue is verified with creating two ignition images, and using same Kubernetes releases - 1.5.3

divyen/ignition.etcd-3.0.4:v1 - disk never get detached from node VM, after pod is deleted.
divyen/ignition.etcd-2.2.1:v1 - disk get detached from the node VM, after pod is deleted.

@tusharnt @BaluDontu @abrarshivani

Filed issue on Kubernetes Repo : https://github.com/kubernetes/kubernetes/issues/44175

@divyenpatel Thanks for doing this.


Would be better if support with SvelteKIT !

Seems to there VITE warning when you use with sveltekit
Adding /* @vite-ignore */ comment inside import call could solve the warning problem !! But syntax highlighting doesn't working

I haven't used it with SvelteKit yet. I will have a look.

@thurti Yes Thanks ! Do something ASAP !!! : )

Thanks for updating the package !! : ) Works well


Triggers in Firebird

Only one trigger is shown in firebird, which is transaction_commit. This trigger seems to be part of dbeaver

Global triggers are database-level triggers (they are definitely not part of DBeaver).
To see table triggers in have to go to a table:


No syntax highlighting for .stylus files (.styl works)

Hey there,
wanted to check out your plugin, so I installed it with Vundle, unfortunately after properly installing and starting a fresh vim session with .stylus files, no syntax highlighting was available at all for me. It appears that .styl files work. any ideas what the issue could be?

adding the following lines to my .vimrc fixes the issue:
autocmd BufNewFile,BufRead *.styl setlocal filetype=stylus
autocmd BufNewFile,BufRead *.stylus setlocal filetype=stylus

after that doens't work property autocomplete values...
i'm something do wrong? https://stackoverflow.com/questions/62560579/why-im-getting-colons-in-vimiloginow-vim-stylus-while-edit-styl-files


feat(form components): dark mode color tokens

Summary
Implement Dark Mode color tokens from updated Figma files for 2.0 Breaking Changes on the following components:

[x] Checkbox -- (* check after Robert's new tokens are updated, may need to update checked base tokens)

[x] Radio Button -- (* check after Robert's new tokens are updated)

[x] Text Input

[x] Text Area

[x] Toggle Button

[x] Dropdown -- (* check tags when tokens updated)

[x] Number Input (* check +/- when button tokens updated)

[x] Form Label

[x] form-input.scss* (base styles for most form input components) -- check WARNING, check whether disabled labels should have styling

Form components that will be handled on a separate PR:

Date Picker
Date Range Picker
Timepicker

ADO Story or GitHub Issue Link

Checkbox
Text Input
Text Area
Toggle Button
Dropdown
Number Input
Radio Button

Figma Links

Checkbox
Text Input
Text Area
Toggle Button
Dropdown
Number Input
Radio Button

Checklist

[x] Used Conventional Commit messages as outlined in the contributing guide.

[x] Noted breaking changes (if any).

[x] Documented/updated all props, events, slots, parts, etc with JSDoc.

[x] Ran the analyze command to update Storybook docs.

[x] Added/updated Stories with controls to cover all variants.
[x] Ran test locally to address any failures.
[x] Added/updated the Figma link for the Story's Design tab.
[x] Added any new component exports to the src/index.ts file

Figma/Storybook Inconsistencies

thumb color on toggleButton hover in dark mode (--kd-color-background-ui-hollow-default):
Background/UI/Default/Secondary (--kd-color-background-ui-default-secondary) -- not available in storybook/tokens (push requested from design team)
Background/Container/Default (--kd-color-background-container-default) doesn't match figma

Testing Instructions

all of these components should have a Storybook sidenav item, except for Form Label, that can be most easily checked in the Patterns/Forms story
there are still a few inconsistencies in the colors as they appear in Figma vs. Storybook. i've noted all that i could find in the section above, but please make any notes of others that you might see. the tokens themselves should all be consistent between the code and the figma file, just not fully reflected yet in storybook

Screenshots
(if any)

Hi @wbarbee ,

The tooltips in the dark mode - shows with black or transparent background - is this expected?
The Figma links provided does not show the dark theme - are these just for reference? (just check for 2 checkbox and Text area)

Hi @wbarbee ,

The tooltips in the dark mode - shows with black or transparent background - is this expected?
The Figma links provided does not show the dark theme - are these just for reference? (just check for 2 checkbox and Text area)

hi @srpriyankashetty

the tooltips and buttons will be updated separately as they are their own components
not all of the figma files have dark mode, we're just going off of the token values that they both share

thanks!

In Dropdown
Multi select, multi select searchable and Data driven options - The selected options text is not clearly visible due to font color in dark mode.

In Dropdown Multi select, multi select searchable and Data driven options - The selected options text is not clearly visible due to font color in dark mode.

same thing here @srpriyankashetty. those are instances of the Tags component that will be styled correctly once those changes are merged in

Verified Checkbox, Checkbox group and Checkbox subgroup looks fine in dark mode theme. Verified Single, Single searchable, Multi select, Multi select searchable, Grouped and Data driven options dropdown looks fine in dark mode theme. Verified the Number input in dark mode and looks fine Verified the Toggle button in dark mode and looks fine. Verified Text input and text input with icon in dark mode theme and looks fine. Verified that Text Area looks fine in Dark mode theme. Verified the Radio button and Radio button group in dark mode theme.
@wbarbee . Just need clarification on the color of Radio button in dark mode - is this expected color? The look and feel wise i feel its better if we have some lighter color.!

confirmed that this token, --kd-color-background-button-secondary-state-default, matches the checked color values from the radio button figma file. i'll double-check again when we make our final pass on these components. thank you!

:tada: This PR is included in version 2.0.0-next.21 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Move osrg/earthquake/pyearthquake/middlebox -> osrg/hookswitch

NOTE: you need to run pip install git+https://github.com/osrg/hookswitch@2b4e673e15b04664b07bce876981bc21ba1eb9e3

Pulled, thanks!


Version 1.1.3 is broken

Using the library and creating an OpenBISClient instance produces this exception, which does not occur in version 1.1.2:
Caught: java.lang.NoClassDefFoundError: ch/systemsx/cisd/common/exceptions/InvalidSessionException
java.lang.NoClassDefFoundError: ch/systemsx/cisd/common/exceptions/InvalidSessionException
	at life.qbic.Query.main(Query.groovy:11)
Caused by: java.lang.ClassNotFoundException: ch.systemsx.cisd.common.exceptions.InvalidSessionException
	... 1 more

Fixed in version 1.1.4 https://github.com/qbicsoftware/openbis-client-lib/releases/tag/1.1.4

the problem was that version 1.1.3 did not include any openBIS dependencies, but version 1.1.4 does.


Karabiner needs uninstall pkgutil:

The karabiner cask is missing pkgutil:, and there seems to be no reason for it. It certainly could benefit from one.
VMWare Fusion is currently deciding to freeze my computer, so can’t test it on a VM as of now.

I would like to tackle this issue for hacktoberfest.

@johndavidmartinez Go for it. No need to tell us, everyone is free to work on whatever they like.

@johndavidmartinez Already done by @johndbritton in https://github.com/caskroom/homebrew-cask/pull/25175.


cryptopp: 5.6.5 -> 8.2.0

Motivation for this change
Poor thing was unmaintained and ignored by nixpkgs-update bot because of its convoluted version declaration.
I've added myself as maintainer and made version a simple var.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-review
--> I've built many reverse-deps but not scylladb and ceph yet
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @
Closure size
$ nix path-info -Ssh
/nix/store/wfny8i467jn129h14q6s5dzidpkk9aah-crypto++-5.6.5        12.1M   44.4M
/nix/store/y2gf42wcj64qz92pak53m9c8v9jbcndh-crypto++-8.2.0         8.3M   40.6M

Ok I'll need to redo the GNUmakefile patch for Darwin

I've updated closure size informations above, because static lib sneaked in before.
Now that we install only shared lib + headers and no static lib and no test program/datas the closure size is actually lower than v5.6.5

@GrahamcOfBorg build cryptopp python27Packages.pycryptopp amule

@GrahamcOfBorg build cryptopp python27Packages.pycryptopp amule


ARROW-2871: [Python] Raise when calling to_numpy() on boolean array

Also marks that to_numpy API is experimental, since we need to figure out what to do about nulls (ARROW-2870)

Codecov Report

Merging #2277 into master will increase coverage by 2.39%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2277      +/-   ##
==========================================
+ Coverage   84.26%   86.65%   +2.39%
==========================================
  Files         290      234      -56
  Lines       44299    41565    -2734
==========================================
- Hits        37330    36020    -1310
+ Misses       6942     5545    -1397
+ Partials       27        0      -27

Impacted Files
Coverage Δ

python/pyarrow/tests/test_array.py
100% <100%> (ø)
:arrow_up:

python/pyarrow/array.pxi
66.97% <100%> (+0.45%)
:arrow_up:

go/arrow/array/booleanbuilder.go

go/arrow/array/array.go

go/arrow/type_traits_numeric.gen.go

rust/src/list.rs

go/arrow/array/binary.go

go/arrow/memory/memory_avx2_amd64.go

go/arrow/array/bufferbuilder.go

go/arrow/math/float64_sse4_amd64.go

... and 48 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3d5b4d8...c07b9b4. Read the comment docs.


Store browser states

Store browser states for next time browser bootstrapping.
For instance,

[x] Tab history
[x] Open last open tabs
[x] Download history
[x] Browsing history

Though everything above got done, there are still some problems need to be solved before we bump Lulumi-browser to 1.2.0.

[x] Tab reordering doesn't make changes to the corresponding page object.
[x] Should save the state of app periodically.
[x] Sometimes, the first restored page would render incorrectly.

For problem: Sometimes, the first restored page would render incorrectly.:

It's the problem that caused by Vue.js cache system design.
Because v-for directive needs key to calculate and estimate whether a specific Vue component needs to be re-rendered or not, the Vue component will remain the same if the corresponding key is the same. Logic is here.
The proposed fix is to give the random pids of stored pages while saving, and therefore makes Vue components to re-render the DOMs.


added wacv19 and fixed cvpr19

wacv19 stats link - https://www.dropbox.com/s/dblra3txqatzq93/WACV_2019_Pocket_Guide.pdf?dl=0

Thanks for your contribution.
I am afraid that I cannot include the WACV in this list. Can you just commit the change on the statistics of CVPR?

done.


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
Winget updated the Postman client to V11 which isn't a valid version from Postman.
https://community.postman.com/t/the-team-only-supports-version-vx-message-is-displayed/40386
Steps to reproduce
Start Postman after updating application with Winget.
Actual behavior
Postman displays an error message.

Expected behavior
Start normally and load team workspace.
Environment
Windows Package Manager v1.7.10861
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.3296
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10861.0

Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

Screenshots and Logs
No response

https://github.com/microsoft/winget-pkgs/pull/148306 Should fix this issue.

https://github.com/microsoft/winget-pkgs/pull/148306 Should fix this issue.

Above linked PR has been merged

#148306

@PckgrBot

Hi all,
I'm using evergreen to detect the latest version. I've manually checked evergreen now and it's also rolled back to version 10 so I'm wondering if the Postman rolled it back themselves.


Route-based IPsec / big packets / fragmentation not working correct

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I have searched the existing issues and I'm convinced that mine is new.
Describe the bug
I have changed a working policy-based VPN connection to a route-based. After the change ping, normal traffic, DNS, ... everything is working fine, except SIP and bigger packets. The SIP router on the remote end network sends for call signalization a big packet (1500 bytes). In the policy-based configuration everything worked fine, so here is not the problem.
I've checked the firewall log on the remote end and there you can see lots of normal packet directed to the vti interface from the SIP router (<IP_ADDRESS>). These packets are reaching me on the local side (<IP_ADDRESS>) - fine. But you can also see also some fragmented UDP packets directed to the IPsec interface. This also happens when I try to send pings with 1400 or 1450 bytes.
When I try to ping with DF flag, the ping is rejected. But without it is lost.
I have tried to change the MTU of the vti interface. This has an effect to the DF flag of my ping. But does not help with the fragmentation problem.
To Reproduce
Connect two host over the internet with route based IPsec and try to ping over the VPN with 1450 bytes.
Expected behavior
Packtes should be fragmented and put correct together again.
Screenshots

Relevant log files
If applicable, information from log files supporting your claim.
Additional context
Add any other context about the problem here.
Environment
OPNsense 19.1.9-amd64
FreeBSD 11.2-RELEASE-p10-HBSD
OpenSSL 1.0.2s 28 May 2019

can you try from the firewall itself first and ping both tunnel endpoints, there are many places where this can go wrong in the network.
From my end, using a basic setup sending 1500 bytes:

Something strange happens: from my firewall I can ping with 1700 bytes the remote firewall and host in the remote network. But from the remote firewall I can only ping with 1700 bytes the local firewall. Hosts are not pingable.

The big pings are all logged with IPsec as interface. The smaller ping to the same destinations are logged with the vti_ interface.

Any suggestions where I can dig deeper into?
I have done further test from my local LAN to several remote LANs. All connected via VPN and all gateways are OPNsense machines. In every policy-base connection the big packet 1700 bytes is written als one packet in the log with 1728 bytes as input on the IPsec interface and with 1728 bytes as output on the LAN interface. And I get response from the destination machine.
With all route-based connections I can see the input fragmented on the IPsec interface as two packets and as one packet with 1728 bytes on the LAN interface as output. I don't know what form this packet finally has at the destination machine, but I do not get any answer from there.
I can ping with 1700 all remote OPNsense interfaces on all ends from all LANs and from all OPNsense. But not the LAN behind them in route-based configuration.
What is the difference in the packet forming between route- and policy-based IPsec?

When I deactivate the complete packet filtering in the "Advanced Settings" of the firewall, everything works. I have tried to deactivate all set rules, but this did not have the same effect.
Any idea where to look?

Anything set in Firewall -> Settings -> Normalisation? a copy of the ruleset /tmp/rules.debug (without private addresses) and bit of context about the interfaces might help

No normalisation set. I have tried to switch off scrub. But this didn't help with SIP communication.
The rules.debug is nearly 300 lines long. May I send you this via Mail? Too many IP addresses to remove...

ok, let's focus on settings and scrub first then:
grep -E '^(set|scrub)' /tmp/rules.debug

this is likely a configuration issue, I rather keep the exchanged content online within community support time.
When disabling scrub, did the ping work as expected? there could be multiple issues, so best to step by step here.

set limit table-entries 1000000
set ruleset-optimization profile
set optimization normal
set timeout { adaptive.start 0, adaptive.end 0 }
set limit states 805000
set limit src-nodes 805000
set loginterface ix0
set skip on pfsync0
scrub on lo0 all
scrub on igb3 all
scrub on ix0 all
scrub on igb4 all
scrub on igb1_vlan400 all
scrub on igb0 all
scrub on igb2 all
scrub on igb1_vlan40 all
scrub on igb5 all
scrub on ipsec7000 all
scrub on ipsec8000 all

Yes, when scrub was disabled I could ping with 1700 through the local firewall

ok, when considering this situations (with scrub enabled as it is now):
[client A]  ---> [firewall A] --- tunnel --- [firewall B] ---> [client B]

can client A ping large packets to the tunnel IP of Firewall A ?

Yes, [client A] can ping [firewall A] end of the tunnel with 1700

can you share ifconfig output (with obfuscated addresses)?

ipsec8000: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1400
        tunnel inet XXX --> YYY
        inet6 fe80::ae1f:6bff:fe69:f6ae%ipsec8000 prefixlen 64 scopeid 0x13
        inet <IP_ADDRESS> --> <IP_ADDRESS> netmask 0xffffffff
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        reqid: 8000
        groups: ipsec

from all related interfaces (lan, wan, tunnel)

LAN:
ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
        ether ac:1f:6b:69:f6:ae
        hwaddr ac:1f:6b:69:f6:ae
        inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
        inet6 fe80::ae1f:6bff:fe69:f6ae%ix0 prefixlen 64 scopeid 0x1
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
        status: active

WAN:
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
        ether ac:1f:6b:69:f3:86
        hwaddr ac:1f:6b:69:f3:86
        inet XXX.59 netmask 0xfffffff8 broadcast XXX.63
        inet XXX.58 netmask 0xfffffff8 broadcast XXX.63
        inet6 XXX%igb0 prefixlen 64 scopeid 0x3
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active

These were the standard values from the system. Any suggestions for MTU and MSS fix?

can you try to set mss on ipsec8000 to anything lower then 1400?

MSS only works for TCP, normally MTU should be received from parent interface, but no idea how to realize.

@mimugmail you're right, my mistake. just out of curiosity, could you reproduce the ping large packet issue on your end? Personally I would expect that switching off scrubbing should keep the normal behaviour. Maybe the better question to @jroehler23 is if the large packet ping works when scrub is disabled.

I can test next week. Normally, when ICMP is allowed in every direction correctly, PMTU discovery should take care of (when DF bit not set)

ok, thanks in advance.

#3327 could be related. Worth a test to disable pf completely and check If it works. Perhaps some auto rules etc. prohibit ICMP messages (or sysctl)

I think @jroehler23 mentioned it worked with pf disabled, which leaves scrubbing or filtering as most likely candidates. The new version (19.7) should also show these internal rules in the overview, for now they should generate log entries when logging is enabled if I'm not mistaken.

I can confirm that large ping and the SIP signalization from the remote LAN is working when pf is deactivated.
With scrubbing disabled I can ping with large packet, but not really stable. When I try to SIP call the remote location from outside (public phone number), neither the ping is working the same time I am calling, nor the SIP is passed from the remote LAN to the telephone server in the local LAN. But it seams to use and block to VPN tunnel with its packets.

New experience:
I have checked once again the VPN configuration at the local OPNsense and I have found one policy-base tunnel configuration is still active. After I deactivated this one, I have only two route-based IPsec tunnels active.
After a reboot the large pings are working! BUT: not from the beginning! I have to ping at least once with a normal size ping (e.g. 32 bytes). When I try to ping direct with 1700 bytes it is still not working.

And I have to keep pinging with small packets. I have waited now for 40 minutes and cannot ping with 1700 bytes. I have to ping first with a small packet, then the big ping is working again. It is getting stranger and stranger...

Next watching: after 24 hours the LAN at the remote site is not reachable any more. Even via ssh connection to the remote OPNsense - no ping to any host in the remote LAN is possible. I have tried to reload services or to deactivate the complete pf. No change.
But the tunnel is still active, routes are set and both endpoints are reachable. Also the LAN address of the remote OPNsense is reachable. Clients in the WLan or other networks there are reachable via ping from the remote OPNsense.
After a reboot of the remote sense, the remote LAN is reachable again. Any hint where to look, to get rid of this behavior? I am confused...

Unfortunately not, it could be some other network or configuration issue, it's a complex world. Within the boundaries of community support I'm afraid I can't help you at the moment.
If someone can isolate a specific issue which we can reproduce on our end, I'll gladly take a look.

I'm seeing a similar problem with my roadwarrior setup.
After a while, no traffic is able to go through the tunnel, but disconnecting and reconnecting works, until it stops again after a while, and the cycle repeats.

So this evening I started a test with a complete new installation and did the complete configuration by hand from the scratch.  I have absolute no idea why this happend.
From my side we can close this.

Same here, no Idea what can help.
Switching to policy-based setup might help hopefully.

On 23.7? Freebsd 13.2 adds PMTU support for ipsec, maybe it helps to frag packets before loosing them

Hi Michael,
its 23.1.6.
I will try to upgrade, keep fingers crossed.

https://docs.opnsense.org/manual/vpnet.html#path-mtu-discovery


ScrollBar breaks when ScrollViewer content changes

Describe the bug
ScrollBar breaks when switching between tabs in the Control Gallery.
I spent some time trying to debug how I had broken this with the changes in #10803, before realising that the same bug also appears on master. If the fix for this isn't going to be simple, it may be better to wait until that PR completes to start on it.
To Reproduce

Start the Control Gallery
Switch to another tab
Switch back to the first tab
Scroll the tab content

If you scroll with the mouse wheel or by clicking the up/down arrows, the scroll bar doesn't move. If you scroll by dragging the scroll bar, it still doesn't move and while the viewer does scroll, the "scroll zone" is very small, resulting in much faster movement than expected.
Expected behavior
No change to scroll behaviour after switching back to the tab.
Desktop (please complete the following information):

OS: Windows
Version: master

Things have improved a little, and the very fast scrolling no longer occurs. But the scroll bar is still locked in place.