User name in EnterNameComponent not being saved? Possibly not being passed back down

It is being saved, but nothing in the component is being updated so it's grabbing the "old" state from redux.
I think we can do const [name, setName]=useState(""); and call that setname between redux dispatch and select- that should trigger the re render.

This is good. I just move the api calls to the start page component instead of the EnterNameComponent


Builder for minifiers

Hello I try to follow your example. Can you please write somewhere that for building site.js, or site.css we need to add "dotnet add package BuildBundlerMinifier". Otherwise example in this page "https://nbarbettini.gitbooks.io/little-asp-net-core-book/content/chapters/add-more-features/add-todo-items.html" will not work. At least in my case it didn't.

It sounds like ASP.NET Core is running in Production mode because it isn't finding the ASPNETCORE_ENVIRONMENT variable. When you start up the server, does it say Development or Production?

Either way, I'll add a note about BuildBundlerMinifier. 👍


Json file reader example

Initial code for reading a JSON file from disk. A single JSON element (hardcoded to one of my files) will be added to a window.

I understand that this is the base for a larger example but to be merged it should be working as is and complete even if there are plans for future extensions.
Do you mind if we make the example slightly more generic or post pone until its more complete, I have added reviews to help.
what are you thoughts?

I don't mind at all - this is my first PR so I'm learning as I go along - I'm happy to help.

Hope to see continued work on this it is a good example!


Add GitHub Actions warning/error annotations for deprecations/disables.

This should make these messages, particular warnings, more obvious to GitHub Actions users.
There's an argument perhaps we should do this more broadly for all warning/error messages but: this feels like a good start.
CC @Bo98 as this came out one of our discussions.

Thanks for corrections and review @Bo98!


support .net standard 2.0

Help to move net standard. However, DataTable is not available in .net standard 1.6. So only 2.0 is available.

@phatcher seems like the AppVeyor configuration needs to be updated to use Visual Studio 2017.

waiting for support .net core 2.0


Log in page UI improvement

main div in log in page is not alligned properly and complete UI for this page can be improved, I would like to contribute to this issue as GSSoC'23  contributor.

Already assigned issue, please check the issue section before raising any new issue. Thank you!


"Unable to extract login-form form"

Hi everyone,
When I try to download with udemy-dl, I get Unable to extract login-form form.
I updated the packages:

sudo pip install requests --upgrade
sudo pip install unidecode --upgrade
sudo pip install requests[security] --upgrade

What should I do?
Thanks in advance.

I foun

It seems like Udemy detects download attempts so I'll wait and see.

I waited a couple of minutes and just retried now. I got: Udemy Says : You do not have permission to perform this action. Run udemy-dl against course within few seconds.

@Nocxy i cannot reproduce the error. please follow issue reporting guideline.

I believe this is a Linux related issue. I can attest I'm having the same problems.
I'll work on trying to gather proper docs for reproduction of error, but I believe this is a legitimate issue that should be investigated.

@Avidexp this error would most likely occur if SSL version is out dated. otherwise this is a simple handle to the exception if udemy API does not return any information against course it mean either you are not enrolled in course or udemy Server is not accepting request. i cannot reproduce the above error i tried on Ubuntu, Mac, CentOS, Windows 7/8/10.

@Nocxy i cannot reproduce and there is no update from you as well so i 'm closing this issue now.

I am having this issue too. How can I help to provide more information?

It is working now. It might be some temporary lock by udemy.


Accordion: button hover in "region" affected by "heading" style

Bug already reported?

[X] I confirm that I have checked if the bug already has been reported

For which framework/library you are reporting the bug
Chlorophyll
Component name
Accordion
Description
The style:
.accordion>div:has(button[aria-expanded=true]) button:hover {
background-color: var(--gds-ref-pallet-base200);
}
effects buttons in the region part of the accordion. When I think its only meant to effect actual accordion expand button in the heading part.
Should probably change this style to only include button:hover in heading.
Steps To Reproduce
Add a simple Test element in the region part of an accordion. Hover the button and it will have a grey background.

Current Behaviour
Overriding normal button behavior in region part.
Expected Behaviour
Only set hover color for heading

I get the same bug by adding Test before the  tag inside the .


extend README about NixOS installation

makes it a bit easier to manage in my opinion.

Looks good, thank you!  I don't personally know much about Nix, so I'm grateful we have others kind-of maintaining the README for it.


[SYSTEMML-1613] Remove incubator disclaimer from project

Since Apache SystemML is now a Top Level Project, remove the Incubator DISCLAIMER and accompanying references from the project.

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/1481/

Checked-out PR and verified disclaimer no longer present.  Thank you Deron for handling this!
LGTM

Thanks for reviewing @gweidner! I'll merge.


Hover build fails with linux

when i run "hover build linux" command
hover: Downloading engine for platform linux-x64 at version b863200c37...
hover: Failed to download engine: failed to get Content-Length header: strconv.Atoi: parsing "": invalid syntax

Does this error occurs on flutter channel beta ?

Does this error occurs on flutter channel beta ?

yes,i execute this ‘flutter channel beta’,then build successful,but i run it command
creating glfw window: VersionUnavailable: GLX: Forward compatibility requested but GLX_ARB_create_context_profile is unavailable

The glfw error might comes from your Drivers.
here are some more information:
https://github.com/go-flutter-desktop/go-flutter/issues/272#issuecomment-535403717
https://github.com/go-flutter-desktop/go-flutter/issues/248#issuecomment-535428357
TL;DR: hover run --opengl=none.


ebitenmobile compile takes too long

compile is too inefficient，is there ways to implement incremental compilation？

Unfortunately this is inevitable so far. I think the main reason is that Oto requires Oboe, which is written in C++.
https://github.com/hajimehoshi/oto/tree/main/internal/oboe

I have noticed it takes a while, too, but it's less of a hinderance when plugged into an automated pipeline.  I just kick it off and look at other code until it's done.

The situation should be fixed by

https://github.com/golang/go/issues/37902
https://github.com/golang/go/issues/54770


check meta server real path

Fixes #1413

Codecov Report

Merging #1415 into master will increase coverage by 7.4%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master    #1415     +/-   ##
===========================================
+ Coverage      48.4%   55.81%   +7.4%
+ Complexity     1796     1038    -758
===========================================
  Files           379      191    -188
  Lines         10914     5585   -5329
  Branches       1115      577    -538
===========================================
- Hits           5283     3117   -2166
+ Misses         5247     2232   -3015
+ Partials        384      236    -148

Impacted Files
Coverage Δ
Complexity Δ

.../ctrip/framework/apollo/core/MetaDomainConsts.java
81.7% <100%> (ø)
18 <0> (ø)
:arrow_down:

...trip/framework/apollo/openapi/dto/OpenItemDTO.java

...ework/apollo/portal/controller/ItemController.java

...o/configservice/wrapper/DeferredResultWrapper.java

...omponent/emailbuilder/GrayPublishEmailBuilder.java

...k/apollo/portal/controller/FavoriteController.java

...apollo/portal/entity/vo/AppRolesAssignedUsers.java

.../framework/apollo/portal/entity/vo/SystemInfo.java

...rk/apollo/portal/service/NamespaceLockService.java

...k/apollo/portal/spi/ctrip/CtripUserInfoHolder.java

... and 181 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 e098232...a10a75d. Read the comment docs.


reset vep to 105

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

This was causing this error when running VEP with our references:
  MSG: ERROR: gnomAD data is not available in this cache

  STACK Bio::EnsEMBL::VEP::CacheDir::get_all_AnnotationSources /usr/local/share/ensembl-vep-112.0-0/modules/Bio/EnsEMBL/VEP/CacheDir.pm:180
  STACK Bio::EnsEMBL::VEP::AnnotationSourceAdaptor::get_all_from_cache /usr/local/share/ensembl-vep-112.0-0/modules/Bio/EnsEMBL/VEP/AnnotationSourceAdaptor.pm:122
  STACK Bio::EnsEMBL::VEP::AnnotationSourceAdaptor::get_all /usr/local/share/ensembl-vep-112.0-0/modules/Bio/EnsEMBL/VEP/AnnotationSourceAdaptor.pm:92
  STACK Bio::EnsEMBL::VEP::BaseRunner::get_all_AnnotationSources /usr/local/share/ensembl-vep-112.0-0/modules/Bio/EnsEMBL/VEP/BaseRunner.pm:170
  STACK Bio::EnsEMBL::VEP::Runner::init /usr/local/share/ensembl-vep-112.0-0/modules/Bio/EnsEMBL/VEP/Runner.pm:128
  STACK Bio::EnsEMBL::VEP::Runner::run /usr/local/share/ensembl-vep-112.0-0/modules/Bio/EnsEMBL/VEP/Runner.pm:200
  STACK toplevel /usr/local/bin/vep:46
  Date (localtime)    = Wed Sep 25 09:05:51 2024
  Ensembl API version = 112


Deployer v7

This PR will contain my work on next Deployer v7.

@antonmedv do we have a roadmap for it?
Accepting help with the project?

Hi,
Yes, some sort of roadmap is on the way. I think I'll release the first alpha version after rebasing v7 to the master. PR can be merged after this.

Codecov Report

Merging #1904 into master will decrease coverage by 36.77%.
The diff coverage is 11.02%.

@@              Coverage Diff              @@
##             master    #1904       +/-   ##
=============================================
- Coverage     64.31%   27.54%   -36.78%
- Complexity      561      691      +130
=============================================
  Files            67       63        -4
  Lines          2228     2349      +121
=============================================
- Hits           1433      647      -786
- Misses          795     1702      +907

Impacted Files
Coverage Δ
Complexity Δ

src/Collection/PersistentCollection.php
0.00% <0.00%> (ø)
4.00 <0.00> (ø)

src/Component/Initializer/Initializer.php
0.00% <0.00%> (ø)
8.00 <8.00> (?)

src/Component/PharUpdate/Console/Command.php
0.00% <0.00%> (ø)
8.00 <8.00> (?)

src/Component/PharUpdate/Console/Helper.php
0.00% <0.00%> (ø)
2.00 <2.00> (?)

src/Component/PharUpdate/Exception/Exception.php
0.00% <0.00%> (ø)
3.00 <3.00> (?)

src/Component/PharUpdate/Manager.php
0.00% <0.00%> (ø)
9.00 <9.00> (?)

src/Component/PharUpdate/Manifest.php
0.00% <0.00%> (ø)
16.00 <16.00> (?)

src/Component/PharUpdate/Update.php
0.00% <0.00%> (ø)
31.00 <31.00> (?)

src/Component/PharUpdate/Version/Builder.php
0.00% <0.00%> (ø)
27.00 <27.00> (?)

src/Component/PharUpdate/Version/Comparator.php
0.00% <0.00%> (ø)
30.00 <30.00> (?)

... and 73 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 7d090af...882c564. Read the comment docs.

Okay, I have plans to merge into master and continue to develop next version in master.


JHU Test Fixtures

We need a few representative test fixtures for JHU. These fixtures are GBL JSON files and should work as representative items for your collection, or for custom features you need tested.
Example fixtures from the BTAA project are here:
https://github.com/BTAA-Geospatial-Data-Project/geoportal/tree/develop/spec/fixtures/solr_documents
The README in that directory helps illustrate the reason each fixture is present.

Hi Eric,
I've attached the sample json files. I've validated them, but let me know if you have any trouble uploading them or find errors.
samplejson.zip

@mjanowiecki - Thanks for sending these along! Please let me know if you have any questions about the feedback below. I'm happy to chat via zoom/phone/slack further, too.

I'm running into a couple of issues trying to import these documents into Solr. The errors seem pretty simple to fix, but also look like each document in the zip file might have the same issues.
Using the first document here as an example: 0ade4b5e-b3b3-4949-86ab-a83277d6e35b
solr_geom values
This document's solr_geom ENVELOPE values are out of sequence. Solr needs a string in WKT/CQL ENVELOPE syntax, which is minX, maxX, maxY, minY order.
The order you have in the document is:
ENVELOPE(-77.311635, 39.348365, -76.787243, 39.720769)

When I import the doc with that order I see this error:
Error adding field 'solr_geom'='ENVELOPE(-77.311635, 39.348365, -76.787243, 39.720769)' msg=Unable to parse shape given formats "lat,lon", "x y" or as WKT because org.locationtech.spatial4j.exception.InvalidShapeException: maxY must be >= minY: 39.720769 to -76.787243 input: ENVELOPE(-77.311635, 39.348365, -76.787243, 39.720769)

The order that looks correct to me is:
ENVELOPE(-77.311635, -76.787243, 39.720769, 39.348365)

dct_references_s
The values in this field look fine, however GeoBlacklight needs this field to be "stringified" json. We'll need to further escape the values here into a single string.
Instead of:
  "dct_references_s": "{'http://schema.org/url': 'http://jhir.library.jhu.edu/handle/1774.2/32814', 'http://schema.org/downloadUrl': 'http://jscholarship.library.jhu.edu/handle/1774.2/32814/p.42-43 Franklin, Hampstead, New Windsor.jpg'}",

We'll need it to look like:
  "dct_references_s": "{\"http://schema.org/url\": \"http://jhir.library.jhu.edu/handle/1774.2/32814\", \"http://schema.org/downloadUrl\": \"http://jscholarship.library.jhu.edu/handle/1774.2/32814/p.42-43 Franklin, Hampstead, New Windsor.jpg\"}",

Fixed Example
Here's a version of the document including these fixes that imports correctly for me:
{
  "dc_identifier_s": "http://hopkinsgeoportal/0ade4b5e-b3b3-4949-86ab-a83277d6e35b",
  "dc_rights_s": "Public",
  "dc_title_s": "Franklin District No. 9, Hampstead, New Windsor, and Winfield P.O., 1877",
  "layer_slug_s": "0ade4b5e-b3b3-4949-86ab-a83277d6e35b",
  "solr_geom": "ENVELOPE(-77.311635, -76.787243, 39.720769, 39.348365)",
  "solr_year_i": 1877,
  "dc_creator_sm": [
    "Lake, Griffing, & Stevenson"
  ],
  "dc_description_s": "Maps of Franklin District No. 9, Hampstead, New Windsor, and Winfield P.O. from An Illustrated Atlas of Carroll County, Maryland by Lake, Griffing, & Stevenson.",
  "dc_format_s": "Mixed",
  "dc_language_sm": [
    "English"
  ],
  "dc_publisher_sm": [
    "Lake, Griffing, & Stevenson"
  ],
  "dc_source_sm": [
    "13eebc92-05c2-4f50-8b8e-a22f057e596f"
  ],
  "dc_subject_sm": [
    "Planning and Cadastral",
    "Atlases"
  ],
  "dc_type_s": "Image",
  "dct_references_s": "{\"http://schema.org/url\": \"http://jhir.library.jhu.edu/handle/1774.2/32814\", \"http://schema.org/downloadUrl\": \"http://jscholarship.library.jhu.edu/handle/1774.2/32814/p.42-43 Franklin, Hampstead, New Windsor.jpg\"}",
  "dct_spatial_sm": [
    "District 9, Franklin, Maryland, United States",
    "Hampstead, Maryland, United States",
    "New Windsor, Maryland, United States",
    "Winfield, Maryland, United States"
  ],
  "dct_temporal_sm": [
    "1877"
  ],
  "layer_geom_type_s": "Image",
  "suppressed_b": "False",
  "dct_provenance_s": "Johns_Hopkins",
  "geoblacklight_version": "1.0"
}

Screenshot of Fixed Example

Hi-- that all seems totally fixable. It might take me an hour or two to edit my python script and produce these again, but I'll try to get these back to you as quick as possible.
Thank you so much for this feedback.

I think these are fixed, they look good from my end. Let me know if not.
samples_edited.zip

These are all indexing correctly now. Thanks for updating them so quickly!
I have added these docs to:
https://github.com/jhu-sheridan-libraries/geoblacklight/tree/master/spec/fixtures/solr_documents/jhu_documents
This places them directly within the repository for source control, but it also allows them to be optionally indexed via a rake task:
bundle exec rake jhu:index_jhu_fixtures

I assume you will be adding B1G metadata elements to these documents over time. Here are a couple suggestions to enhance these fixtures, to leverage features within the codebase:
dct_provenance_s
Values here can just be "Johns Hopkins", with no underscore necessary.
b1g_centroid_ss
Documents with this value will display in search results map clusters
b1g_date_range_drsim
Documents with a date range value will better match date range queries

Found a couple more issues here

Looks like this title could be spaced better:

ace11792-fca6-4c3a-a814-e7093de4deda

Found errors in the IIIF key/value in dct_references_s for:

df152b1c-6bc0-485e-9a07-271a22adf80f
fcb4e970-e54a-4778-876c-f595fe3878d9
2b50b898-93a8-44c4-8f3a-1810ab72e8a0
fbdbf577-0033-4979-922f-1e7d3f8d056a
67f3bee7-01b7-4bcf-86ed-86462952cebc
c8003de7-ed22-4813-82ce-b9d63ad572f2
9cb90240-9d5e-4cb4-9225-ffd1513442ab

If you look at the "http://iiif.io/api/image" values, you'll see some curly quotes which are breaking the application's JSON.parse call.
{
  "dc_identifier_s": "df152b1c-6bc0-485e-9a07-271a22adf80f",
  "dc_rights_s": "Public",
  "dc_title_s": "Bird's Eye View of the City of Annapolis, MD",
  "layer_slug_s": "df152b1c-6bc0-485e-9a07-271a22adf80f",
  "solr_geom": "ENVELOPE(-76.539535, -76.469805, 38.998867, 38.94302)",
  "solr_year_i": 1864,
  "dc_creator_sm": [
    "Magnus, Charles"
  ],
  "dc_description_s": "This image was produced from an original print copy held as part of the Baetjer Collection. In the spring of 2017 the Venable LLP law firm generously donated to the Sheridan Libraries most of the maps, views and prints in the Baetjer Collection. One print, color lithograph, hand colored; 38 x 43 cm.",
  "dc_format_s": "Mixed",
  "dc_language_sm": [
    "English"
  ],
  "dc_publisher_sm": [
    "Magnus, Charles"
  ],
  "dc_subject_sm": [
    "Imagery and Base Maps"
  ],
  "dc_type_s": "Image",
  "dct_references_s": "{\"http://schema.org/url\": \"http://jhir.library.jhu.edu/handle/1774.2/61866\", \"http://schema.org/downloadUrl\": \"http://jscholarship.library.jhu.edu/handle/1774.2/61866/V430.jpg\", \"http://iiif.io/api/image’: ‘https://image.library.jhu.edu/iiif/js%2F1774.2%2F61866%2FV430/’}",
  "dct_spatial_sm": [
    "Annapolis, Maryland, United States"
  ],
  "dct_temporal_sm": [
    "1864"
  ],
  "layer_geom_type_s": "Image",
  "suppressed_b": false,
  "dct_provenance_s": "Johns_Hopkins",
  "geoblacklight_version": "1.0",
  "_version_":<PHONE_NUMBER>952512500,
  "timestamp": "2020-02-19T17:47:46.934Z",
  "solr_bboxtype__minX": -76.539535,
  "solr_bboxtype__minY": 38.94302,
  "solr_bboxtype__maxX": -76.469805,
  "solr_bboxtype__maxY": 38.998867
}

I'll have to investigate how to make the uuid spacing better, those were just autogenerated.
Thanks for catching that curly quote error-- those little guys are the worst. Would you like me to regenerate the json files for those and fix the errors? I can do that this morning if it wouldn't be too much hassle/time for you to upload the new files.

Sorry for the confusion! I didn't mean the UUID was awkward, but the dc_title_s attribute for that record has a space typo in it. Lots of child documents for that record, so you see the bad title on many pages.
Please go ahead and regenerate them. It's absolutely easy to upload and index the new files.

Ok, that makes more sense. Apologies, I think I need more coffee. Update files coming your way.

I've attached the edited files here. I couldn't find c8003de7-ed22-4813-82ce-b9d63ad572f2 though -- is that possibly an old id from the first, unedited json files?
samples_edited2.zip

Closing. Completed during the February Winter Code Sprint.


swipeEnabled property not working in materialTopNavigator

Current Behavior
const TabNavigator = createMaterialTopTabNavigator({
Screen1,
Screen1,
}, {
swipeEnabled: true,
});

When I try to swipe between screens, it doesn't do anything

Here's the documentation
https://reactnavigation.org/docs/en/material-top-tab-navigator.html#tabnavigatorconfig
My Environment
"react": "16.8.6",
"react-native": "0.60.5",
"react-native-gesture-handler": "^1.4.1",
"react-native-reanimated": "^1.2.0",
"react-navigation": "^4.0.0",
"react-navigation-stack": "^1.5.3",
"react-navigation-tabs": "^2.4.0"

Weird, I'm experiencing the same issue in my environment, but when I create an Expo it seems to work: https://snack.expo.io/Bk0Q5jwwr

Please follow the getting started guide and configure react-native-gesture-handler: https://reactnavigation.org/docs/en/getting-started.html

@satya164 thank you for your input. I checked that guide again, and did indeed miss something, but even if I add react-native-screen and add the two lines to my android/app/build.gradle. It doesn't seem to work.

@johman10 have you configured react-native-gesture-handler? please double-check and if it's still a problem, open an issue with a runnable demo in a GitHub repo.

@satya164 new issue opened with a reproduction repo.

Closed because @satya164 was correct after all.
To everyone having this issue please note that you even though you're on ReactNative 0.60+ you will still have to do the part staying "To finalize installation of react-native-gesture-handler" of the getting started guide

check your react-native-gesture-handler setup in MainActivity file. example here
package com.swmansion.gesturehandler.react.example;

import com.facebook.react.ReactActivity;
+ import com.facebook.react.ReactActivityDelegate;
+ import com.facebook.react.ReactRootView;
+ import com.swmansion.gesturehandler.react.RNGestureHandlerEnabledRootView;

public class MainActivity extends ReactActivity {

  @Override
  protected String getMainComponentName() {
    return "Example";
  }

+  @Override
+  protected ReactActivityDelegate createReactActivityDelegate() {
+    return new ReactActivityDelegate(this, getMainComponentName()) {
+      @Override
+      protected ReactRootView createRootView() {
+       return new RNGestureHandlerEnabledRootView(MainActivity.this);
+      }
+    };
+  }
}


Magnet online testnet is unstable

The block generation time is very long and unstable. The time has a range and is not a fixed block generation time.
When upgrading to 0.7.2, an error will occur and the program will interrupt.

How about the local testnet? has the same issue happened?

It's normal. I can't find this problem on local testnet.

assigned this issue to @sulijia


Remove .DS_Store file

Removes a .DS_Store file that was left behind

@begedin 😭

👍

@HeroicEric just invited you to volunteers team now so no more forks for you.


sql 引擎解析 对 presto 数据库 增加 try_cast 关键字解析

sql 引擎解析 对 presto 数据库 增加 try_cast 关键字解析

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


Update to use Java 17

The current default java is java 11.
For more informations see the debian package repository (https://packages.debian.org/en/bullseye/default-jre). As you can see there, default-jre is java 11 on bullseye.
As mentioned in the Readme it should be java 17.
(17 is LTS as well as 11 is, but support for 11 ends in 8 months)

personally i'd suggest to use bellsoft liberica jdk. might make a pr for that later.

2023-01-25T15:34:40Z #8 52.08 E: Unable to locate package openjdk-17-jre
2023-01-25T15:34:40Z ------
2023-01-25T15:34:40Z ERROR: failed to solve: executor failed running [/bin/sh -c apt update && apt upgrade -y && apt -y install curl software-properties-common locales git && apt-get install -y openjdk-17-jre && apt-get -y install liblzma-dev && apt-get -y install lzma && adduser container && apt-get update && apt -y install cmake]: exit code: 100
2023-01-25T15:34:40Z Build failed using Buildkit (1)

2023-01-25T15:34:40Z #8 52.08 E: Unable to locate package openjdk-17-jre


Dropbox slowly start

Every time the system reboots the Dropbox starts indexing and synchronization process.
This is very costly. Is it possible to disable?

Currently, Elementary OS is not my daily driver, but I did not have this problem. Anyway, this script only installs Dropbox, any problem related to its behavior should be reported directly to Dropbox developers.


Expose the getResourcePath and getRootResourcePath wrappers.

Due to the importance of path safety, the internal sanitisation wrappers
for volumes and containers should be exposed so other parts of Docker
can benefit from proper path sanitisation.
Signed-off-by: Aleksa Sarai<EMAIL_ADDRESS>(github: cyphar)

/cc @cpuguy83 @shykes @vieux @crosbymichael @unclejack @tiborvass @vishh

LGTM

LGTM

@cyphar Is there any particular places? Because I think that both container and volume can be fully private.

@LK4D4 There's quite a few places (see: the builder) where they use their own path sanitisation rather than just using these wrappers.

@cyphar Where?
I wouldn't expect anything outside the stuff in the daemon package to be looking into the container like that.

builder/internals.go inside addContext is one example. And I think there's somewhere else in the builder too.

:( This should be a call on the daemon.

@cyphar Then you should use them there. I'm not in favor having not used public methods (I know that there are already a lot of them :))

@LK4D4 @cpuguy83 I've fixed up those cases to use the newly exposed wrappers (there were also two cases where we didn't use get(Root)?ResourcePath inside daemon). Also rebase'd.

@cyphar Something pretty bad with tests. Are they passing on your machine?

ping @cyphar

Yes, sorry. The second commit's to blame -- I will fix it this weekend.

LGTM, except for documentation about what "resource path" and a "root resource path" actually are.
Thank you for the nice refactoring!

There, I fixed the problem (container.RootfsPath is a weird name for something that returns the basefs, given that root has a different meaning, btw). PTAL.
/cc @cpuguy83 @shykes @vieux @crosbymichael @unclejack @tiborvass @vishh

There, I've fixed up the comments. PTAL.
/ping @cpuguy83 @shykes @vieux @crosbymichael @unclejack @tiborvass @vishh @stevvooe

LGTM

oh gosh, @cyphar would you mind rebasing? Sorry :(

rebase'd. pls2merge kthxbai.
/ping @cpuguy83 @shykes @vieux @crosbymichael @unclejack @tiborvass @vishh @stevvooe

rebase'd. pls2merge kthxbai.
/ping @cpuguy83 @shykes @vieux @crosbymichael @unclejack @tiborvass @vishh @stevvooe

LGTM


replace-systemd: example boots but systemctl can't find shared library.

systemctl: error while loading shared libraries: libsystemd-shared-251.7-611.fc37.so: cannot open shared object file: No such file or directory

I updated the example because it was no longer building but to build I needed to remove /var/libs
/var/libs content I imagine was important?
FROM quay.io/fedora/fedora-coreos:stable
RUN rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2022-bb55f82158 && \
    #https://coreos.github.io/rpm-ostree/architecture-core/#content-in-var
    echo "ls /var/lib\n" && ls /var/lib/ && \
    ostree container commit

STEP 1/2: FROM quay.io/fedora/fedora-coreos:stable
STEP 2/2: RUN rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2022-bb55f82158 &&     echo "ls /var/lib\n" && ls /var/lib/ &&     ostree container commit
Downloading https://kojipkgs.fedoraproject.org/packages/systemd/251.6/609.fc37/x86_64/systemd-udev-251.6-609.fc37.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/systemd/251.6/609.fc37/x86_64/systemd-251.6-609.fc37.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/systemd/251.6/609.fc37/x86_64/systemd-libs-251.6-609.fc37.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/systemd/251.6/609.fc37/x86_64/systemd-container-251.6-609.fc37.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/systemd/251.6/609.fc37/x86_64/systemd-pam-251.6-609.fc37.x86_64.rpm...done
Downloading https://kojipkgs.fedoraproject.org/packages/systemd/251.6/609.fc37/x86_64/systemd-resolved-251.6-609.fc37.x86_64.rpm...done
Enabled rpm-md repositories: fedora updates-modular updates fedora-cisco-openh264 fedora-modular updates-archive
Updating metadata for 'fedora'...done
Updating metadata for 'updates-modular'...done
Updating metadata for 'updates'...done
Updating metadata for 'fedora-cisco-openh264'...done
Updating metadata for 'fedora-modular'...done
Updating metadata for 'updates-archive'...done
Importing rpm-md...done
rpm-md repo 'fedora'; generated: 2022-11-10T09:30:00Z solvables: 66822
rpm-md repo 'updates-modular'; generated: 2022-12-09T00:53:59Z solvables: 1457
rpm-md repo 'updates'; generated: 2022-12-15T01:21:14Z solvables: 12985
rpm-md repo 'fedora-cisco-openh264'; generated: 2022-10-06T11:01:40Z solvables: 4
rpm-md repo 'fedora-modular'; generated: 2022-11-10T09:23:24Z solvables: 1454
rpm-md repo 'updates-archive'; generated: 2022-12-15T02:02:37Z solvables: 12315
Resolving dependencies...done
Installing 6 packages:
  systemd-251.6-609.fc37.x86_64 (@commandline)
  systemd-container-251.6-609.fc37.x86_64 (@commandline)
  systemd-libs-251.6-609.fc37.x86_64 (@commandline)
  systemd-pam-251.6-609.fc37.x86_64 (@commandline)
  systemd-resolved-251.6-609.fc37.x86_64 (@commandline)
  systemd-udev-251.6-609.fc37.x86_64 (@commandline)
Downgrading: systemd-libs;251.6-609.fc37;x86_64;local
Downgrading: systemd-pam;251.6-609.fc37;x86_64;local
Downgrading: systemd-resolved;251.6-609.fc37;x86_64;local
Downgrading: systemd;251.6-609.fc37;x86_64;local
Downgrading: systemd-container;251.6-609.fc37;x86_64;local
Downgrading: systemd-udev;251.6-609.fc37;x86_64;local
Cleanup: systemd-udev;251.7-611.fc37;x86_64;installed
Cleanup: systemd-container;251.7-611.fc37;x86_64;installed
Cleanup: systemd;251.7-611.fc37;x86_64;installed
Cleanup: systemd-libs;251.7-611.fc37;x86_64;installed
Cleanup: systemd-pam;251.7-611.fc37;x86_64;installed
Cleanup: systemd-resolved;251.7-611.fc37;x86_64;installed
/usr/lib/sysusers.d/basic.conf:9: conflict with earlier configuration for user 'root', ignoring line.
/usr/lib/sysusers.d/basic.conf:12: conflict with earlier configuration for group 'nobody', ignoring line.
/usr/lib/sysusers.d/basic.conf:13: conflict with earlier configuration for user 'nobody', ignoring line.
/usr/lib/sysusers.d/chrony.conf:2: conflict with earlier configuration for user 'chrony', ignoring line.
/usr/lib/sysusers.d/systemd-resolve.conf:8: conflict with earlier configuration for user 'systemd-resolve', ignoring line.
/usr/lib/sysusers.d/systemd-timesync.conf:8: conflict with earlier configuration for user 'systemd-timesync', ignoring line.
ls /var/lib\n
NetworkManager
alternatives
authselect
chrony
containerd
containers
dnsmasq
fwupd
games
initramfs
iscsi
kdump
logrotate
machines
misc
nfs
os-prober
polkit-1
portables
private
rpm
samba
selinux
sss
systemd
tpm2-tss
vagrant
Found file: "var/lib/systemd/catalog/database"
Found file: "var/lib/systemd/random-seed"
Found file: "var/lib/alternatives"
Found file: "var/lib/rpm"
Found file: "var/lib/vagrant"
Found file: "var/lock"
Found file: "var/log/README"
Found file: "var/log/tallylog"
Found file: "var/log/wtmp"
Found file: "var/log/btmp"
Found file: "var/log/lastlog"
Found file: "var/mail"
Found file: "var/run"
error: Found content in var

Any quick and fast way to resolve this or remove the example for now?

No luck with an upgrade using: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a82842a059 either:
Last login: Thu Dec 15 20:40:26 on ttyS0
Fedora CoreOS 37.20221106.3.0
systemctl: error while loading shared libraries: libsystemd-shared-251.7-611.fc37.so: cannot open shared object file: No such file or directory
[core@tutorial ~]$ sudo reboot
reboot: error while loading shared libraries: libsystemd-shared-251.7-611.fc37.so: cannot open shared object file: No such file or directory
[core@tutorial ~]$

What seems to be happening is that for some reason the /usr/bin/systemctl is left at the old version.  Doing rpm --reinstall  https://kojipkgs.fedoraproject.org//packages/systemd/251.6/609.fc37/x86_64/systemd-251.6-609.fc37.x86_64.rpm fixes it here.
# rpm -V systemd|grep -Fv '.......T.' | grep -v missing
....L....    /usr/lib/systemd/system/default.target
# rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2022-bb55f82158
...
(apparent success)
...
# sha256sum /usr/bin/systemctl
acac0aa21c430381bf7e4bcb48f1e85d8d1cd0530b6ee682e1d47cee725aefd4  /usr/bin/systemctl
# rpm -V systemd|grep -Fv '.......T.' | grep -v missing
..5....T.    /usr/bin/systemctl
#

So it's just somehow only that binary...

Oh man, of course...the problem is our cliwrap logic again...we're swapping it back to the old binary.  To handle this, I think we may need to detect the case where /usr/bin/systemctl got swapped back, and then just delete the old version.

thanks for the workaround here is in a PR: https://github.com/coreos/layering-examples/pull/50
Lets leave this issue open while we get a proper fix in rpm-ostree to remove the workaround then.


Remove minter bean from integration test configuration

Related to: https://jira.duraspace.org/browse/FCREPO-1696

https://github.com/fcrepo4-exts/fcrepo-camel/pull/98 should take the place of this PR

This PR should be merged once the fcrepo-camel component upgrades to a fcrepo4 version beyond 4.4.0.
Reference from http://irclogs.fcrepo.org/2015-11-05.html :
<awoods> acoburn: You have a comment that the fcrepo-camel PR should not be included... at least not before: https://github.com/fcrepo4-exts/fcrepo-camel/pull/98
<awoods> acoburn: do you want to have the following included now? https://github.com/fcrepo4-exts/fcrepo-camel/pull/97
<acoburn> awoods: no, I think not
<awoods> acoburn: ok, you want the minter?
<acoburn> awoods: definitely not
<awoods> acoburn: or you do not like the scanning?
<acoburn> awoods: the thing is we've decoupled the versioning
<acoburn> awoods: I like the scanning!
<acoburn> awoods: but we're using fcrepo version 4.4.0
<acoburn> awoods: and that has the minter built in, so we need the spring config to contain the minter stuff
<awoods> acoburn: ok, that makes sense
<acoburn> awoods: once the minter project is pulled out of fcrepo and there's a new release, then we can change this on fcrepo-camel
<acoburn> awoods: that is, then we'll *have* to change this
<awoods> acoburn: exactly
<awoods> acoburn: I will keep the PR around for later

merged via bc35a9475372fcc553d30376001290ec87c9011f


Parallel downloads

Implements the functionality of downloading chunks in parallel. It limits the number of concurrent connections (active downloads) per server through the HTTP transport.

@cuducos, could you please take another look?

Thanks for the review! Merging as soon as the CI is green.


MNT: Update pandas notebook

Uses inplace=True, improve groupby answer, and calls axis='columns' to avoid having to explain what 0 and 1 mean.
Closes #444.

Need to make sure inplace doesn't cause warnings to issue. Might need to do:
df = df.drop(...)

instead.


MSA search by MMSEQ server

Hi, thanks for all great work.
I have a question about confidential issues when we use 'use_msa_server' flag for our confidential target protein?

Yea, it’s a server.  It will send your sequence to an external computer to
run the MSA.   You probably do not want to use this option.
However, if it’s a target, there may be less importance. Ie - it’s not a
lead compound.  It’s like googling sortof.  You have probably googled your
target and looked  it up on uniprot, maybe even the PDB.  You probably want
to err on the side of caution, but ultimately, that’s a choice you will
need to make.
On Thu, Nov 21, 2024 at 8:20 PM Kyeongtak (David) Han <
@.***> wrote:

Hi, thanks for all great work.
I have a question about confidential issues when we use 'use_msa_server'
flag for our confidential target protein?
—
Reply to this email directly, view it on GitHub
https://github.com/jwohlwend/boltz/issues/42, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZDHRDCCOUUFPDJL45RYN32B2BHNAVCNFSM6AAAAABSIIZM4KVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY4DCNBXGI2DMNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I cannot speak to the confidentiality of the server since it's an outside service not maintained by us. It's up to the user to decide. You are welcome to create your own MSA's of course. Setting up colabfold locally is fairly straightforward, as are the databases used by AlphaFold

There is now an option to set your own URL for the colabfold server if you host it locally. Closing for now!


progress bars

See progress examples of https://nostalgic-css.github.io/NES.css/

can i have a go at the progress bars?

Sure!!  @GrumpyMonk26
I thought of something like: !todo progress POSITION PERCENT - just one color for now
and I think it could be placed under the item text for
Tell me if you need any other informations :)

@GrumpyMonk26 feel free to ask if you need any help :)


src-env-specific for scratch orgs possible?

Describe the question to doc
Its not a bug, but I did not found any documentation to it: Is there way to define "src-env-specific" metadata for all scratch orgs?
Its relevant for audiences which are needed for a community cloud/digital experience site with a variation navigation.
You can't push/deploy a default audience without any criteria to scratch orgs, but to sandboxes (its a sf bug). Sandboxes cant have a criteria in a default audience. The workaround would be to have different Default Audience's for scratch orgs and the sandboxes.
https://dxatscale.gitbook.io/sfpowerscripts/faq/package-types/source-packages#what-are-my-options-with-source-packages

you can put it in the default folder, check here
https://github.com/Accenture/sfpowerscripts/blob/develop/decision records/deployments/001-aliasified-data-sourcepackages.md


Does not handle -1 properly

When the device is in Standby mode, peoplecount returns -1
Even though the goal would be to have the device always on (awake or halfwake mode), it is nessary to better handle this case in the code.

Seems like the default behavior would be to interpret -1 as 0, since we can assume the device is in standby mode if not used, and then, nobody is present.
Moreover, the wakeuponpresence setting would have woken up the device is setup properly.


How to show arrow buttons.

Should the arrow buttons show by default?
I've tried various themes but I'm not seeing the button.
Am I overlooking basic CSS requirements for my containers or is this a configuration concern?
Thanks for a great plugin!

Arrow buttons do not show by default. You need to enable them via the scrollButtons: enable option:
$(selector).mCustomScrollbar({
  scrollButtons:{
    enable:true
  }
});

Also, make sure you have the mCSB_buttons.png on the same dir with plugin's stylesheet (jquery.mCustomScrollbar.css).

Thanks and apologies, I should have taken greater care reviewing the configuration parameters that have been well documented.
I'm immensely enjoying the ease of use this plugin as well as the broad variety of beautifully designed scroll-bars styles that come bundled with the plugin.
Thanks!

I am trying to add custom arrow button image in the css. But unable to do so. Request you lemme know how this is done.
.mCSB_buttonDown{
border: 1px solid #898888;
background-position: center;
background-repeat: no-repeat;
background-size: 18px 18px;
background-image: url('../Images/Icons_6x/Down-Grey.png');
}
Thanks.

Arrow buttons do not show by default. You need to enable them via the scrollButtons: enable option:
$(selector).mCustomScrollbar({
  scrollButtons:{
    enable:true
  }
});

Also, make sure you have the mCSB_buttons.png on the same dir with plugin's stylesheet (jquery.mCustomScrollbar.css).

It doesn't work


chore(deps): update renovate/renovate docker tag to v37.31.4

This PR contains the following updates:

Package
Update
Change

renovate/renovate
patch
37.31.1 -> 37.31.4

Release Notes

renovatebot/renovate (renovate/renovate)
v37.31.4
Compare Source
Miscellaneous Chores

deps: update actions/setup-node action to v3.8.2 (#25350) (939c1c7)
deps: update dependency @ls-lint/ls-lint to v2.2.1 (#25329) (45cc69a)
deps: update dependency @ls-lint/ls-lint to v2.2.2 (#25347) (5dbfe44)
deps: update ossf/scorecard-action action to v2.3.1 (#25352) (040b344)

Build System

deps: update dependency @cdktf/hcl2json to v0.19.0 (#25353) (8be845a)

v37.31.3
Compare Source
Bug Fixes

monospace version in ignoreOther and ignoreMajor PR close comment (#25333) (18e578b)

v37.31.2
Compare Source
Bug Fixes

deps: update ghcr.io/containerbase/sidecar docker tag to v9.23.5 (#25341) (3918a30)

Documentation

Add example for registryAliases support list (#25331) (3a95764)
update references to renovate/renovate to v37.31.1 (#25342) (334aa5f)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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


[Store] Broken layout

Page store is broken on branch develop

I fixed all bug at branch "issue-fixbrokendevelop" and waiting your confirm. Thank you your time.

Resolve #30


support for Rust Language Server

Any plans to use Rust Language Server?

I've been thinking about toying with that, but if I'm honest it's probably way above my skill in elisp. =)

I would be interested too but my skill in elisp are limited to being able to edit my emacs config files. :) Now that emacs supports "shared/dynamic libraries" I wonder if it could be written in Rust.
Some people began to work on LSP support but I don't know if they will continue. https://github.com/sourcegraph/emacs-lsp
2 people were also interested to work on this on the internal rust forum. I just asked them if they did any progress.
https://internals.rust-lang.org/t/introducing-rust-language-server-source-release/4209/31?u=bbigras

There is now an emacs-lsp package on Melpa which seems to be updated regularly.

There is now an emacs-lsp package on Melpa which seems to be updated regularly.

Yeah I'm going to try this one when RLS will be installable with rustup (see https://users.rust-lang.org/t/announcing-rustup-1-1-0/10242).

Given that emacs-lsp exists, I'm inclined to think that this bug can be closed -- or is there some change to be made in rust-mode?

Does rust-mode do things like run cargo to check for compilation errors that could conflict or be redundant when using emacs-lsp?

@tromey I don't know how realistic it is, but I would like it if there were some "easy way" to install rust-mode in emacs that covered rustfmt, RLS setup, and other configuration. Maybe that's a separate bug.

RLS is now installable via rustup.

@nikomatsakis

but I would like it if there were some "easy way" to install rust-mode in emacs that covered rustfmt, RLS setup, and other configuration

At now I use:

flycheck-rust for online syntax checking
cargo for compiling, syntax checking and
and also it has great feature cargo-process-current-test if your cursor inside #[test]
you run this elisp function and emacs run only this rust test function.
emacs-racer for obvious reasons
rust-playground for fast way to check some
syntax construction (running snippet with ctrl+enter is great)
and rust-mode of course

I not use rls via emacs-lsp, because of completetions work too slow in compare with emacs-racer.
Bad things that these are separate tools, and some times it conflict with each other,
for example if you change code  and run cargo build with active flycheck-mode, then
one of two operations: syntax check or cargo build hangs with message like this Blocking waiting for file lock on build directory.
It would be great to combine this tools on basis of some emacs ide framework, like
http://cedet.sourceforge.net/ede.shtml (which is part of emacs 25 as I know).

I think that preferably most of those packages should be combined into one package for Rust, but it would require several people merging their projects with what becomes the defacto package. I think @nikomatsakis mentioned this somewhere else but he wanted rust-mode to be everything that is required to use Rust in Emacs. I fully agree with this but you have five or six packages at least that would need to merge with it.

What about integration of lsp-rust as starting point?
It is very small package with < 50 lines of code. That take care about launch rls and find Cargo.toml.  If rust-mode can take care about this stuff this should simplify things.

What about integration of lsp-rust as starting point?

That has lsp-mode as a dependency, which is quite a bit larger.  At some point I think it would make sense to just make these dependencies of rust-mode.  Maybe when RLS lands in a stable release?  Also the caveats in the lsp-rust README are worrying.

The warning I think comes because it doesn't run asynchronously, so when it hangs, Emacs hangs. I'm fairly certain there are ways to work around this for Emacs, but not sure how easy or good the solutions are.

It's probable that CIDER has figured this out. Maybe we could take inspiration from it.

I got RLS working in emacs.  There might be a simpler way, but here's what I did:

Install rust-mode
Install flycheck
Install markdown-mode
Install lsp-mode
Install lsp-rust

I tried it and also got it working. A bit finnicky to do. No idea how we could streamline that.

Now GNU's ELPA has eglot, which is another LSP client.

eglot works great for me; very "plug and play". https://github.com/joaotavora/eglot

I will update the readme and add some notes about lsp support in emacs.


Ugly fix for loadAudio_ and playAudio (due to changes in blockly itself)

This modification fixes the Blockly vs. blockly-games synch problems with loadAudio_ and playAudio usage, which makes almost all the games work again (on master).
The fix is really a workaround...

Want to pull

Do I need to do something to let you do that?

i have pull & deploy but it gives me error
Error: Not Found
The requested URL /maze?lang=en was not found on this server.

Arjen did they accepted your workaround?
I think my error, was for this also.

They did not - but are working on a different branch so probably had low
priority. Maybe you can put a comment in the github that it worked for you?

Please excuse brevity - sent from a mobile.
Op 21 jul. 2015 20:11 schreef "Hendrys Tobar"<EMAIL_ADDRESS>
Arjen did they accepted your workaround?
I think my error, was for this also.
—
Reply to this email directly or view it on GitHub
https://github.com/google/blockly-games/pull/16#issuecomment-123415181.

This pull request worked for me. Who is in charge of reviewing it or accepting it?

Works for me! ty

Blockly Games should build properly now without any hacks.


Outlook Add-in not working in windows 10

I have created Outlook add-in in visual studio 2013 which is working fine in windows 2007 and office 2016, but plugin is not getting Loaded in windows 2010 and office 2016.

Add-in is not available under disabled COM add-in list.
Its registry value of load behaviour is 3 i.e loaded.

Is any compatibility issue with windows 10?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b6cb5f52-dfc5-4fa2-6508-194d6f1c674a
Version Independent ID: 8f3caf2d-fba3-166f-43bc-1d3e4007abab
Content: Troubleshoot user errors with Office Add-ins - Office Add-ins
Content Source: docs/testing/testing-and-troubleshooting.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

Thanks for your interest in Outlook Add-ins. The issues in this repo are intended to track errors in documentation. Please raise technical questions like this on StackOverflow. Be sure to tag it outlook-web-addins.


V2 - Corporate console - permission issues for cla-manager-designee endpoint

Tested with below user roles and observed that they have access to the  cla-manager-designee endpoint. 403 should be returned when below users access the  cla-manager-designee endpoint
Endpoint
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/company/{{companySFID}}/project/{{projectSFID}}/cla-manager-designee
httpMethod
POST
Payload
{
"userEmail": "{{useremail}}"
}

User role with scope as Individual - No Account
400 is returned instead of 403

@wanyaland  please check this - it might have already been fixed.

This issue has been resolved.


feat: add the cdot linter

The cdot linter is a syntax linter that flags uses of the "cdot" · that are achieved by typing a character different from ·.
For instance, a "plain" dot . is allowed syntax, but is flagged by the linter.

bors r+


Rebuild for libboost 1.82

Bot cannot open due to the hard pin on cgal-cpp.
This should probably move to the global pinning, but for now I'm just following https://github.com/conda-forge/graph-tool-feedstock/commit/c000165852680992079c02539ca4213cba639375

Linux builds timing out, but only on py<311...?
  CXX      src/graph/topology/graph_similarity.lo
  CXX      src/graph/topology/graph_similarity_imp.lo
[nothing after that]

Looking at the successful run for py311, that one object did take >20 minutes though!
2023-10-03T04:35:10.1747625Z   CXX      src/graph/topology/graph_similarity.lo
2023-10-03T04:35:17.7464222Z   CXX      src/graph/topology/graph_similarity_imp.lo
2023-10-03T04:56:03.6827838Z   CXX      src/graph/topology/graph_subgraph_isomorphism.lo

So perhaps it's running out of memory...
At least the OSX builds are fine now...

Thanks, @h-vetinari!


[6.5.x] GUVNOR-2616: Editing dialog for 'Field' doesn't show selected value

See https://issues.jboss.org/browse/GUVNOR-2616
This is the corollary of https://github.com/droolsjbpm/drools-wb/pull/250 for 6.5.x
(cherry picked from commit 6caf98eac8098c78c91c26473d261350cc586f20)
(Lamda's in the master commit had to be replaced with anonymous inner classes)

@Rikkola @karreiro Could you please review?

+1


Eye of sargeras should be in cd after a hero takes it like in VJASS version

https://imgur.com/a/EFpk2Dl

Fixed.


contextUri.path wrongly uppercased on Windows

VS Code Version: 1.53.1
OS Version: macOS 11.2

Hi, I'm the author of the Angular schematics extension (400 000 users).
Basically, it's a graphic interface for the Angular CLI (ie. the generation of component files), so the user right-click on a folder in the Explorer menu where he/she wants to generate, then the extension retrieves the folder path and pre-fill the component path.
To do so, I basically do this:
import * as path from 'path';

path.posix.relative(workspaceFolder.uri.path, contextUri.path);

where contextUri is the argument passed by VS Code when the user right-clicked a folder and chose "Angular: Generate something" in the context menu from the extension.
Issue is on Windows, contextUri.path is inconsistent:

sometimes the drive letter is lowercased (/c:/Users/Elmo/angular-project/right-clicked-folder), which is what is expected as all other VS Code paths are like that (for example workspaceFolder.uri.path)
sometimes the drive letter is uppercased (/C:/Users/Elmo/angular-project/right-clicked-folder), which causes path.posix.relative() to give the wrong result

When testing myself, the second and wrong scenario happens only in a multi-workspaces setup. But the user of the extension who reported the issue first is telling he is in a single workspace setup.
Steps to Reproduce:
On Windows:

Generate a random Angular project (to be able to see the extension logs, as it only activates in Angular projects):

npm install @angular/cli -g
ng new (options asked don't matter)

Generate a second random Angular project (to be able to test in a multi-workspaces setup):

ng new (options asked don't matter)

Clone the extension:

git clone https://github.com/cyrilletuzi/vscode-angular-schematics
cd vscode-angular-schematics
git checkout windowsissuewithcontexturi
npm install

Open the extension project in VS Code
Launch a debug session (just click "Run" in the debug view)
In the debug window:

open the first Angular project
right-click on any folder or file in the Explorer menu
choose "Angular: generate a component" in the context menu

Go back to the extension project window and check the Debug console: the path should be correct (/c:/Users/Elmo/angular-project/right-clicked-folder)
Go back to the debug window:

File > Add a new folder to workspace > choose the second Angular project
right-click on any folder or file in the Explorer menu
choose "Angular: generate a component" in the context menu

Go back to the extension project window and check the Debug console: the path should be incorrect (/C:/Users/Elmo/angular-project/right-clicked-folder)

Does this issue occur when all extensions are disabled?: Yes

@cyrilletuzi so you want the drive letter to be normalized for explorer contributed context commands.
This makes sense, however we will not do it.
It might break a lot of extensions and nobody complained in these 5 years. Explorer simply passes the URI along, it does not change the drive letter.
For now leaving this open to gather more feedback.

so you want the drive letter to be normalized for explorer contributed context commands

No, it's not what I ask. I would like for vscode.Uris path (and fsPath) to be consistent:

it's not normal that Node path.relative() fails with 2 paths coming from the same API and on the same OS, it definitively means that one of the path is wrongly formatted,
it's also not normal that the exact same API (contextUri.path) returns a different value for the exact same right-clicked folder, depending on unknown conditions.

Explorer simply passes the URI along

I'm quite sure it's not exact. From what I understand, vscode.Uris contain:

.fsPath: the OS-specific path (so C:\path\to on Windows, /usr/path/to on Linux)
.path: the path in Linux format (so /C:/path/to on Windows, /usr/path/to on Linux)

While fsPath is indeed probably just a raw value, I'm quite sure path is derived and formatted from fsPath.
So maybe the issue is not in contextUri management itself but in some cases where path is not derived correctly from fsPath, but still there is an issue somewhere.

fyi @jrieken as the owner of our URI class

Closing the issue as it has not been taken into account and is now lost in the void, but the issue is still there.


Disconnect Camera

I have write code using JavaScript for camera connection and connection stablished successfully but while Disconnected camera i am not able to get any event in Browser.Please provide support for this.
In go server i have received error log as below screenshot but in Browser not able to recived.

:+1: when RTSPtoWeb loses connection to the camera, the camera feed on my browser freezes on the last frame. In certain applications it can be dangerous if the user does not realize that the feed is down. It would be better if the RTSPtoWeb server sent an error or close message so I could properly relay the camera feed state to my users.

I have same problem here, in my case some of cameras was in wi-fi network and sometimes the video freezes as there's no comunication with player to call a reconnect function or anything like that in webrtc demo implementing right here, to solve it I did some research and figure out that webrtc has a function called getStats() that gives you a lot of information about your connection using the protocol like jitter, framespersecond, bytesreceived and so on, so I just include this code in "onopen" function from sendChannel, like that:
this.webrtcSendChannelInterval = setInterval(() => {
                this.webrtcSendChannel.send("ping");

                this.webrtc.getStats().then(function (stats) {
                    stats.forEach(function (report) {
                        if (report.type === "inbound-rtp") {
                            //console.log(report);
                            if (report.framesPerSecond < 5 || !report.framesPerSecond) {
                                _this.stalled();
                            }
                        }
                    });
                });
            }, 5000)

Also created the function stalled() inside the webrtc play function:
    this.stalled = function () {
        console.log("Video stalled by FPS monitoring. Reestablishing connection...");
        if (this.webrtc) {
            clearInterval(this.webrtcSendChannelInterval);
        }
        this.destroy();
        this.playWebrtc();
    }

    this.destroy = function () {
        var _this = this;
        _this.webrtcSendChannel.close();
        _this.webrtc.close();
    }

Now it works like that: Every time that the framespersecond parameter drops below 5 or it don't exist (in case of connection didn't finished), this will call the stalled function that is going to close dataChannel, then close the webrtc connection using destroy function, then I just call the play function again to create a new connection.
This example works good for me, but keep in mind that my play function is quite different from the demo one that is in web template, you need to adjust it to your interface.
Also there's a lot of things you can check adding to this idea, but for me, the simple one like that works just good.


chore(deps): 🤖 bump node to v18

Pull Request Checklist
🚨 Please review the guidelines for contributing to this repository.

[ ] Appropriate label or labels have been added
[ ] ✅ Tests for the changes have been added (for type:fix / type:feat)
[ ] 📝 Docs have been reviewed, added or updated if needed (for type:fix / type:feat)
[ ] 🏁 Issue number has been linked if this PR closes one

Description
Please describe your pull request.
Breaking Change?

[ ] 💥 Yes
[ ] No

❤ Thank you for contributing!

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (58a0091) 100.00% compared to head (36786c4) 100.00%.

: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
Additional details and impacted files
@@            Coverage Diff             @@
##            master      #190    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           24        24
  Lines         2142      2025   -117
  Branches        16        16
==========================================
- Hits          2142      2025   -117

Impacted Files
Coverage Δ

src/typescript/rules.ts
100.00% <100.00%> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


#1901 feat(script): Support add jvm args to start uniffle server

What changes were proposed in this pull request?
Support define jvm args for coordinator/shuffle-server/dashboard
Why are the changes needed?
Fix: #1901
Does this PR introduce any user-facing change?
User can define jvm args within rss-env.sh
like
UNIFFLE_DASHBOARD_JAVA_OPTS=" -Dio.netty.leakDetection.level=PARANOID "
UNIFFLE_SHUFFLE_SERVER_JAVA_OPTS=" -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005 "
UNIFFLE_COORDINATOR_JAVA_OPTS=""

How was this patch tested?
Package and launch each server process by the startup script.

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

Project coverage is 53.19%. Comparing base (0a60834) to head (d59fc88).
Report is 2 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1905      +/-   ##
============================================
+ Coverage     53.12%   53.19%   +0.07%
+ Complexity     3002     2642     -360
============================================
  Files           448      403      -45
  Lines         24482    20785    -3697
  Branches       2282     1971     -311
============================================
- Hits          13006    11057    -1949
+ Misses        10669     9010    -1659
+ Partials        807      718      -89

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

-Xlog:gc*
-Xlog:gc+age=trace
-Xlog:gc+heap=debug
-Xlog:gc+promotion=trace
-Xlog:gc+phases=debug
-Xlog:gc+ref=debug
-Xlog:gc+start=debug
This parameter should be removed during the startup of JDK9 and above, which prints a lot of JVM logs that are actually already printed in gc log files.

-Xlog:gc* -Xlog:gc+age=trace -Xlog:gc+heap=debug -Xlog:gc+promotion=trace -Xlog:gc+phases=debug -Xlog:gc+ref=debug -Xlog:gc+start=debug This parameter should be removed during the startup of JDK9 and above, which prints a lot of JVM logs that are actually already printed in gc log files.

@maobaolong ping~

Thanks for your contribution @maobaolong

Can we add these env vars to the docs?

@EnricoMi With pleasure, I'll add it at once

Can we add these env vars to the docs?

@EnricoMi Docs added by https://github.com/apache/incubator-uniffle/pull/1933


Try to retrieve schema from all schemas cache if not found in individual cache

I noticed REST create and query always perform a query on all schemas followed by an unnecessary single schema query before the data query/update. This optimisation will prevent that happening so will reduce database queries by around 1/3.

Looking great, thanks!


trigger image rebuild

Signed-off-by: Jonathan Marcantonio<EMAIL_ADDRESS>For issue, [2.5-integration] Remediate package vulnerability in applifecycle-backend-e2e #22450

/lgtm

/approve


Redocly CLI Hangs When Running In A Container

Describe the bug
We're using the Redocly CLI to bundle our OpenAPI specs, but for some reason it seems to hang randomly. We believe this started with Docker image redocly/cli:1.13.0, but we're not 100% certain. For now we've snapshotted ourselves to 1.12.0.
For context, the CLI works when I install it directly with NPM or use the docker pull ... && docker run ... commands found on your documentation. However, if I intentionally use the desktop-linux builder in Docker Hub that's when it ends up hanging.
Unfortunately, it doesn't look like there's any way to enable debug logs with the CLI so I'm not sure if it's pausing on something related to our OpenAPI spec or if it's a genuine issue which is making it hard to determine where it's coming from.
To Reproduce
To reproduce this issue on my ARM Mac, I ran the following:

Dockerfile content:

FROM redocly/cli as bundle-spec
WORKDIR /spec
COPY . .
RUN redocly bundle --remove-unused-components --dereferenced openapi.yaml -o dist/bundled_openapi.yaml

export DOCKER_BUILDKIT=1
docker buildx create --name linuxbuilder --use
docker buildx inspect linuxbuilder --bootstrap
docker buildx build --platform linux/amd64 -t your-image-name .

Expected behavior
The spec should bundle successfully or at least error out with some sort of reason why it failed.
Logs
After running the steps above, I can see this. Notice that this step has been running for 481 seconds already (and climbing)
 => [bundle-spec 4/8] RUN redocly bundle --remove-unused-components --dereferenced openapi.yaml -o dist/bundled_openapi.yaml            481.5s
 => => # (node:1) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
 => => # (Use `node --trace-deprecation ...` to show where the warning was created)
 => => # bundling openapi.yaml...

OpenAPI description
We are using OpenAPI 3.1.0. I'm not sure if I can post my spec here so I will try to find a test example that reproduces this issue. If I do, I will post it as a comment below.
Redocly Version(s)
For the test scenario above, I'm pulling the latest which I believe is 1.16.0
Node.js Version(s)
Using the Docker image provided by you
Additional context
N/A

Hi @its-hammer-time! Could you check whether it also hangs outside the docker container (when installed globally with npm install -g @redocly/cli and run via redocly bundle --remove-unused-components --dereferenced openapi.yaml -o dist/bundled_openapi.yaml)?

Hey @tatomyr, it seems to work when I run it in a "Mac" environment. What I mean by that is NPM and DockerCLI both work, but as soon as I try to build it with the desktop-linux setup I described above it hangs.
I was doing some testing yesterday with my own spec and it seems to be stemming from a portion of our OpenAPI spec. Essentially, i commented out all of our paths and slowly uncommented them to see if it was potentially coming from a circular dependency that wouldn't resolve when the environment changed. Again this is just a theory, but maybe the OS integrations change so Mac works, but Linux doesn't or something of that sort.
Anyways, I narrowed it down to a few endpoints, but what was interesting is it would work if my paths were ordered in a certain way, but if I moved an endpoint around it broke. I'm still trying to dig into this, but my theory is that the internal $ref resolution mechanism is breaking under a very unique case. It would be great if there was a way to enable debug logs on the CLI, but for now I'll keep playing around with it.
For example, this does NOT work:
/endpoint/A
/endpoint/B
/endpoint/C
/endpoint/D
/endpoint/E

But this does?
/endpoint/A
/endpoint/B
/endpoint/D
/endpoint/E

/endpoint/C

Okay, this is very interesting. I was able to isolate a failure case for two endpoints like the following:
# This does NOT work
/endpoint/A
/endpoint/B

# This works
/endpoint/B
/endpoint/A

I then iteratively removed pieces all the way down endpoint A to see if it was maybe a $ref issue like I explained above. However, what I found is that it's a single minimum value on an enum that breaks the bundler. I'm honestly not quite sure why, but here's the schema that I edited. As long as I comment out that minimum field it works?
  day:
    description: The day of the month to run the report schedule.
    examples:
      - 23
    type:
      - integer
      - "null"
    minimum: -1
    maximum: 31

I'm going to try and create an example spec that reproduces this issue so we have something to work off of together. I know it can be hard to debug these types of issues when you don't get an example spec.

Okay, I'm starting to believe the minimum piece I mentioned above was a red herring. After I found that, I wanted to isolate the two endpoints so I commented out all of our components as well and all of a sudden it starting working with the minimum field. I slowly added components back in until it failed again at which point I ran the bundler multiple times. Depending on how "complex" the spec is (i.e. how much I uncomment), I'm getting inconsistent results.
For example, with ~20% of the spec, I get build issues maybe 2/10 times, but if I filter it down to ~10% of my spec I don't get any build issues. Then with 100% of the spec I get build issues every time. For context, I'm just running the following command over and over after making a change in my openapi.yaml file. It's the same as in my original post, but I added the --no-cache arg so I can re-run the build.
docker buildx build --no-cache --platform linux/amd64 -t your-image-name .

With that said, it seems like this may be a race condition or a resource constraint.

I don't think the issue you've mentioned is related to your case. The memory issue crops up with the build-docs command (which runs the React renderer) while you're using bundle.
I hope you'll be able to come up with some repro because it's indeed very hard to figure out what's wrong without it.

Summary
Okay, I was able to get a small working example from our existing spec "working".... in other words, it's broken 😄. I'll put my steps below on how I reproduce it as well, but what's funny is that minimum: -1 value is still a culprit in it breaking. If I comment that out or even change the value to 0 it works all of a sudden. I'm not sure why that would break the bundler, but that's what I'm noticing.
example.zip
System Setup

2021, 14-inch, Macbook Pro
64 GB memory
macOS 14.5
Docker version: 26.0.0

Ensure you're using desktop-linux as your builder
I'm fairly certain this builder is provided by docker so I imagine everyone has it? If not, let me know, but here's how to use it:
# Lists the builders you currently have, ensure desktop-linux is an option
docker buildx ls

# Check your current builder and write it down somewhere incase you need to swap back
docker buildx inspect

# Swap to desktop-linux
docker buildx use desktop-linux

Build The Image
From now on, I essentially just re-run this command whenever I want to "test" the container build. Note that we're using the no cache arg so we can ensure a full build every time.
docker buildx build --no-cache --platform linux/amd64 -t your-image-name .

Test Cases
I've also noticed the following changes to the spec seem to resolve the issue. At this point, I'm honestly not sure why it's behaving like this. The "fixes" seem random to me, but hopefully you will have more insight as to what may be happening.
Don't Use -1 Minimum Value
As mentioned above, in open_api_spec/components/schema/report_schedule.yaml, there's a property called day that has minimum: -1 set. If you comment that out or change the value to 0 it starts to work all of a sudden.
No Changes: 0% success rate (0/10 builds passed)
Using 0: 100% success rate (10/10 builds passed)
Commented Out: 100% success rate (10/10 builds passed)
Don't Include Campaign Schema
In open_api_spec/example.yaml, under components/schemas there's a field called Campaign. If you comment this out, it appears to start working even with the minimum still set to -1?
No Changes: 0% success rate (0/10 builds passed)
Campaign Commented Out: 100% success rate (10/10 builds passed)

Thank you! I'll review the example a bit later.

Using the example.zip above, I was able to confirm that using redocly/cli:1.12.0 works whereas redocly/cli:1.13.0 does not! Perhaps a dependency changed between these two versions and doesn't support the amd64 platform on ARM?

Hey @tatomyr, any update on this?

Hi @its-hammer-time, I've examined all changes between those versions and I haven't found anything suspicious that can potentially cause the issue.
I'm going to close this issue as it's not related to our NPM/Docker packages and we don't have the capacity to investigate this edge case. If you're interested, you can try digging more into the commits by yourself (maybe reverting them one by one and trying to build).
Out of curiosity, what is the reason for building your own image?

Hey @tatomyr - I'm not trying to build my own image, it's failing when using the Redocly image as a build stage in my Dockerfile like the following (the syntax may not be exactly right, just trying to get the point across):
FROM redocly/cli:latest as bundle-spec
COPY . .
RUN redocly bundle ...

FROM python:3.12
COPY --from=bundle-spec bundled_spec.yaml .
...

I'm not familiar with redocly-core, but I believe the issue came from updating that dependency? I'm not sure if your team even owns this package though
https://github.com/Redocly/redocly-cli/releases/tag/%40redocly%2Fcli%401.13.0

Either way, my company recently migrated our Docker image builds to run in the cloud rather than on our laptops so that may get us around this issue as we will now be building images on the native platform rather than trying to build AMD on ARM. I haven't tested it yet, but I'm guessing it should work now.

I'm not familiar with redocly-core, but I believe the issue came from updating that dependency? I'm not sure if your team even owns this package though

Yes, we do. However, as I mentioned, I have no clue about what might have potentially impacted the build.

I haven't tested it yet, but I'm guessing it should work now.

Thanks for the update @its-hammer-time! Please let me know whether it works or not.


cupy.cross function not available

I noticed that function numpy.cross, which implements cross product for 2D and 3D vectors, is not available in cupy. Is this intentional? Would a numpy-equivalent implementation of cross product be a welcome contribution to cupy?
Let me know what you think. Thank you.

There is no reason for the non-existence of cupy.cross. Contribution is always welcome!!

I'll work on this issue


Info page elements for extracted files

Page that appears when an archive file that has been extracted is opened.

Uncompressed size.
Link to extracted files.
Tree view of extracted file contents.

Completed in #52


Update ISSUE_TEMPLATE.md - added code blocks

Fix for #3952. Adds fenced code blocks / output blocks to the Steps to reproduce, Expected behavior and Actual behavior sections, so as to facilitate proper formatting.

@mklement0,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

LGTM.


chore: v0.4.0

Description

Bumps version to 0.4.0.
Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[x] 🗑 Chore

Is there anything left for v0.4.0 to be released?

@spydon yup! we need to merge the constraints and animations PRs, but I think we can release those in another PR, thanks for reminding!


Support for Accept.js

Following the discussion on https://github.com/thephpleague/omnipay-authorizenet/issues/41

Quick question: if the front-end form puts the tokenized card into POST data opaqueDataDescriptor and opaqueDataValue, does that mean the application does not need to handle it explicitly at the back end? Are those the field names the official SDK suggests?

I dont fully understand your first question. Here is the code I run in the back end:
/**
 * @var \Omnipay\AuthorizeNet\AIMGateway $gateway
 */
$gateway = Omnipay\Omnipay::create('\Omnipay\AuthorizeNet\AIMGateway');

$gateway->setApiLoginId(...);
$gateway->setTransactionKey(...);

$request = $gateway->purchase([
    'notifyUrl' => 'htts://www.perdu.com',
    'amount' => $amount,
]);

$request->setOpaqueDataDescriptor($_POST['data_descriptor']);
$request->setOpaqueDataValue($_POST['data_value']);

$response = $request->send();

if ($response->isSuccessful()) {
    // ...

}

As for the field names, I didnt check them against the SDK. Taking a look at it:
https://github.com/AuthorizeNet/sample-code-php/search?utf8=✓&q=opaque
https://github.com/AuthorizeNet/sdk-php/blob/9d24edc675362b6349983205b8288d178fa0c469/lib/net/authorize/api/contract/v1/OpaqueDataType.php
Seems like the relevant approach would be to handle an OpaqueDataType object made of two properties dataDescriptor and dataValue.
I dont have any strong opinion about it. Let me know what you decide, I'll change it.

The request class, used to POST data to the gateway, is looking at GET data in putting its data together. That makes an assumption about what is happening in the environment in which the request object is put together. I was just clarifying that was intentional and that I understood why it was working that way.
Actually, looking again, it should probably be removed since it uses GET and not even POST:
https://github.com/thephpleague/omnipay-authorizenet/pull/77/files#diff-3197c271405074529f9f6b7b308a0546R171
If I understand correctly, that could potentially be injected by an end user just by adding GET parameters to the merchant site credit card form POST URL, and without any input validation. Best leave full control in the merchant application like in your example.

In other words, when a payment request is created, what it contains will be affected by GET parameters in the URL of the page that constructs the payment request, and that cannot be prevented by the application without explicitly resetting those two values, which any site NOT wanting to use Accepy.JS would not be doing.

Ok I get you. I just removed that. That originally was in Mark's snippet and I assumed this was right.
Regarding the variable naming, any thoughts?

Thanks, I think that is safer.
The variable name looks good to me. It is named very specifically for Authorize.Net, and we can provide a more generic wrapper or mapping later if and when we develop any common across the various gateways.

I was missing the setter in my code, which is why I needed to fetch it directly from the $_GET.

Looks like it works as expected here 👍 Just had to fix my javascript to use the right names.
:shipit:

All merged - thank you. If you could confirm the master branch works for you, I'll try to get a release done today. I've added a few notes to the README too - anything to add or correct, just shout PR :-)

I tested it and it works fine for me! Let us know about the release. Thank you.

Thanks, I'll work on a release ASAP. It looks like there are a number of other PRs coming related to reporting and refunds (the transactionReference is a little messy) so it would be good to get a new baseline.


Change Task.execute and Executor.execute to take a RowReceiver

This removes the TaskResult from the interface in order to make it
possible to later on stream rows via RowReceiver to a client.

ack


Add SwapExecutionPage

Store route in swapExecutionStateAtom
use swapExecutionStateAtom to render SwapExecutionPage

there are some eslint error u need to solve


CogSolid does not exists

Describe the bug

as what the title says only CogOutline is fine
Reproduction

Version and System Info
"flowbite-svelte-icons": "^1.0.2",

Please use the latest version.
pnpm i -D flowbite-svelte-icons@latest

still got the same problem

It does!..
https://svelte.dev/repl/594644f2b9cc45c8b2d4aaf27d9229eb?version=4.2.12
Restart your VSCode.

It does!.
https://svelte.dev/repl/594644f2b9cc45c8b2d4aaf27d9229eb?version=4.2.12

Restart your VSCode.

got it working after the restart, that was pretty dumb of me lol thanks.


[Keyword search] Globally unique id as elasticsearch index

Description
Node id is not globally unique, since if e.g. the same notion is plugged on two workspaces, the same page will have the same node id in both workspaces
Fixes #9527
Risks
none, index is not used yet and we'll backfill ES from scratch when all data source folders are already backfilled too
Deploy
core

(feel free to merge once fixed)

Should we add the data_source_internal_id as indexed field? If we index on data_soruce_id already can we index on the internal_id instead :pray:

Looks great but I would just pass node in delete_node ?

Went for it; lead to an indeed cleaner refactor :+1:


Payload Currency Arrays Appear To

Description
2021-08-12 16:02:25 [-][19346][-][error][stamped-io] Client error: `POST https://stamped.io/api/v2/201702/survey/reviews/bulk` resulted in a `400 Bad Request` response:
"data_array_needed"

Steps to reproduce

Order Something
Check the stamped error logs

Additional info

Plugin version: 1.0.0
Craft version: Pro 3.6.17
Multi-site: No

Additional context
Commerce Version : <IP_ADDRESS>
Here is a payload that once did work:
{
	<snipped>
	"orderCurrencyISO": "USD",
	<snipped>
}

Here is a payload that did not work
{
	<snipped>
	"orderCurrencyISO": {
		"id": "1",
		"iso": "USD",
		"primary": "1",
		"rate": "1.0000",
		"minorUnit": 2,
		"alphabeticCode": "USD",
		"currency": "US Dollar",
		"numericCode": 840,
		"entity": "VIRGIN ISLANDS (U.S.)"
	},
	<snipped>
}

Did something change? What changed?

Y'all gonna ever update your version / package with these currency patches?

Totally didn't realise we never tagged a release for this. See 1.0.1


LIBPOSTAL_ADDRESS_NONE is not functional

Hi!
I was checking out libpostal, and saw something that could be improved.

My country is

India
Here's how I'm using libpostal

Expanding addresses, but for reasons I want to do ONLY number related normalizations
'Forty Three' = 43
but not things like 'St' = 'Street'

Here's what I did

Call expand with address_components None (0)
expand_address('Quatre-vingt-douze St',  address_components=postal.expand.ADDRESS_NONE )
I also tried explicitly setting all the others to false except expand numex

Here's what I got

Other expansions also occur:
['92 ststst', '92 st st', '92  stst', '92   st']

Here's what I was expecting

['92   st']
The issue in code
https://github.com/openvenues/libpostal/blob/master/src/expand.c#L1564
Here we're essentially override NONE option with ANY
Here's what I think could be improved

Either remove the ANY override or suggest a way to access the None expansion (only numeric expansions)
Thank you!

Hi, can I get any insights on the above?


Simplify graph_dedup [run_process_replay]

this one should be a speedup btw

minor benchmark change,
master:
***** model forward in  53.18 ms
***** model schedule in  16.89 ms
***** model lower in 2138.58 ms

this branch:
***** model forward in  54.26 ms
***** model schedule in  17.03 ms
***** model lower in 2139.69 ms

I like that all_nodes is gone


Training with affine AND TPS

I have looked at the training code but I don't understand how you're using the affine warped output for TPS to get the final result. The code implies that you can train TPS separately and affine separately, but don't you need to both?
Am I missing something?

I have looked at the training code but I don't understand how you're using the affine warped output for TPS to get the final result. The code implies that you can train TPS separately and affine separately, but don't you need to both?
Am I missing something?

I think that each transformation has different advantages? If you apply affine first, then TPS, you would get better warped results.
May be affine transformation can give general shape of the target, but for more accurate in detail shape, TPS is better.


Fix API V2 filter by size [OSF-4948]

Purpose
Fix the problem that API v2 is not able to filter by file size
Changes
Add SerializerMethodIntegerField, a subclass of SerializerMethodField.
Change "size" of FileSerializer to be a SerializerMethodIntegerField
Side effects
None
Ticket
https://openscience.atlassian.net/browse/OSF-4948
Note
This PR is a new version of https://github.com/CenterForOpenScience/osf.io/pull/5715, which I had to close due to some improper use of git.

I think, aside from minor formatting issues, this should be good. If we have to do many more variations of the filterable serializer method fields then what we have would become cumbersome, but I don't think we'll need to and we can cross that bridge when we come to it. For this PR, should be great. 🐧

Okay. I'll do the cleanup. The odd formatting seems like an issue caused by copying and pasting.

@brianjgeiger Code cleanup for the test file is done.

Sorry about this, should have caught it weeks ago, and hopefully there won't be a lot of scope creep here. The simple thing is ensure that the test will also filter out things that don't match; if your file came up first and the filter did nothing, then the test you have would pass. So just verify that a file that does not match the criterion does not show up in the results.
Second, numeric things should be able to use other operators than just equality. So filter[size][gt]=100 should get every file larger than 100. I thiiiiink that should just happen, in which case all you need is a test. If the test doesn't succeed, however, then we can evaluate. I'm 90% sure it'll be fine, though.

@brianjgeiger
So I should add another test to verify that whatever files that does not match the size would not show up, right?
For the second thing, I just tried and "filter[size][gt]=100" doesn't seem to work. In the code it it specified that
COMPARABLE_FIELDS = NUMERIC_FIELDS + DATE_FIELDS
and that
NUMERIC_FIELDS = (ser.IntegerField, ser.DecimalField, ser.FloatField)
Simply adding the SerializerMethodIntegerFied to the set of NUMERIC_FIELDS can make it work. Should I proceed and do so? Are there any other unit tests I should include?

Yes to adding the field to NUMERIC_FIELDS. That plus the couple of tests I proposed should do it.

@brianjgeiger Okay. I have added a line in the original test to make sure the data returned contains only one file. I have also added a separate test to make sure filter by size using operators works. Also added the SerializerMethodIntegerField to the set of NUMERIC_FIELDS.

This approach has a couple of minor design issues:

The SerializerMethodIntegerField adds no behavior to its parent class and exists only for type-checking. This is antipattern in OOP, esp. in the Python language, which discourages type-checking
We should be able to generalize the implementation of a filterable SerializerMethodField to other types

How about a TypedSerializerMethodField which can know about its return value type?
size = TypedSerializerMethodField(return_type=int)

The return_type can be used by the filter class to cast the client's input value. You could also (optionally) use it to validate against the serializer method's return value.
size = TypedSerializerMethodField(return_type=int)

def get_size(self, obj):
     # this will cause an error to be raised by TypedSerializerMethodField
    return 'not an int'

Pass finished.


could not compile with serde_macros depdendency

please take a look at https://github.com/serde-rs/quasi/issues/35#issuecomment-202404870 i've exacly the same problem, but couldn't solve this by using
[dependencies.rs-es]
version =  "0.3.2"
features = ["nightly_without_ssl"]

Hello,
I haven't been able to reproduce this problem, testing it with a blank project with that configuration.  Could you provide more information, specifically: the version of rustc, the full Cargo.toml file, and the full error message?  Also which OS is it being built on (I'm currently testing it on Ubuntu).
Thanks

i try to use it in this project: https://github.com/timglabisch/rustinvoice (316a347f2651512d4c89b5ed935b31d5949dc9a7)
on OSX Yosemite 10.10.5 with rustc 1.10.0-nightly (b5ba5923f 2016-04-21)
i just added
[dependencies.rs-es]
version = "0.3.2"
features = ["nightly_without_ssl"]

to the toml file:
rustinvoice git:(master) ✗ cargo run
    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading lazy_static v0.2.1
 Downloading gcc v0.3.28
   Compiling gcc v0.3.28
   Compiling lazy_static v0.2.1
   Compiling quasi v0.9.0
   Compiling aster v0.15.0
   Compiling openssl-sys-extras v0.7.10
   Compiling openssl v0.7.10
   Compiling quasi_codegen v0.9.0
   Compiling serde_codegen v0.7.2
   Compiling quasi_macros v0.9.0
/Users/tim/.multirust/toolchains/nightly/cargo/registry/src/github.com-88ac128001ac3a9a/quasi_macros-0.9.0/src/lib.rs:19:29: 19:32 error: mismatched types:
 expected `&mut syntex::Registry`,
    found `&mut rustc_plugin::Registry<'_>`
(expected struct `syntex::Registry`,
    found struct `rustc_plugin::Registry`) [E0308]
/Users/tim/.multirust/toolchains/nightly/cargo/registry/src/github.com-88ac128001ac3a9a/quasi_macros-0.9.0/src/lib.rs:19     quasi_codegen::register(reg);
                                                                                ^~~
/Users/tim/.multirust/toolchains/nightly/cargo/registry/src/github.com-88ac128001ac3a9a/quasi_macros-0.9.0/src/lib.rs:19:29: 19:32 help: run `rustc --explain E0308` to see a detailed explanation
error: aborting due to previous error
Build failed, waiting for other jobs to finish...
error: Could not compile `quasi_macros`.

Cool, thanks for this.
I think there are multiple issues here.  At the moment, there is a different issue with Quasi and the latest Rust nightlies.  Once that is fixed (there's a PR being merged at the moment), I'll update rs-es too once all the dependencies are on crates.io.  I'll use this example as a test case for the new version.
In the meantime everything should work with Stable or Beta Rust releases.  Although, of course, developing things that use Serde is easier with the nightlies.

This is currently dependent on #65

The upstream issues have been fixed and released.  If you use the 0.3.4 version of rs-es and a recent Rust nightly everything should be good.
[dependencies.rs-es]
version = "0.3.4"
features = ["nightly_without_ssl"]
default-features = false


Ensure docs show nav on small-screen devices

The issue
The sidebar (which is the bottom navigation) on mobile devices is hidden by a line of CSS.  This prevents pages from being navigated on small-screen devices, as mentioned in #3527.
The fix
Removes the CSS line, which means the navigation gets shown again.  Nav is responsive on small-screen devices care of the Alabaster base theme so there's no issue with showing it.
The checklist

[x] Associated issue
[x] A news fragment in the news/ directory to describe this fix with the extension .bugfix, .feature, .behavior, .doc. .vendor. or .trivial (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

Seems like a good idea to me, thanks for the PR and for your patience while we fix things :)

Also thanks @dimaqq for the triage


Error: SyntaxError: Unexpected token

After doing a clean install of this repo and adding the Router to the app with:
import {bootstrap}    from 'angular2/platform/browser';
import {AppComponent} from './app.component';
import {ROUTER_PROVIDERS} from 'angular2/router';

bootstrap(AppComponent, [ROUTER_PROVIDERS]);

I'm getting the following error in the browser console (Chrome 49 - OS X 10 El Capitan):
Error: SyntaxError: Unexpected token <(…)   angular2-polyfills.js:322
ZoneDelegate.invoke @ angular2-polyfills.js:322
Zone.run @ angular2-polyfills.js:218
(anonymous function) @ angular2-polyfills.js:567
ZoneDelegate.invokeTask @ angular2-polyfills.js:355
Zone.runTask @ angular2-polyfills.js:254
drainMicroTaskQueue @ angular2-polyfills.js:473
ZoneTask.invoke @ angular2-polyfills.js:425

The current version of this repository is sadly broken. We are waiting to beta .12 to fix this issues.
So let's wait for that update and see if that fixes your issue or not.

Could you update the repo and try now please?

I downloaded again this app and followed the same procedure to add the router and I'm getting a similar error message:
Error: SyntaxError: Unexpected token <(…)   angular2-polyfills.js:332
ZoneDelegate.invoke @ angular2-polyfills.js:332

You need to include the router after you include angular:
<script src="node_modules/angular2/bundles/angular2.dev.js"></script>
<script src="node_modules/angular2/bundles/router.dev.js"></script>

Just tried with beta.13 and it works fine.
As @Foxandxss observes, you must add the independent router library to your index.html.
Please note that this is not a support site. Closing because there is no issue.


Bundle calls TRE API

PR for issue #1571
What is being addressed
Communicate with the TRE API from the Resource Processor
How is this addressed

TRE API credentials get added to keyvault
Use a new credential set in Porter to retrieve the necessary credentials.
Temp script that uses these credentials to just call api/workspaces and return the current workspaces (just as an example)
Need to discuss how this will really work with a firewall (when it's ready)

/test

/test

/test


Prefer Quilt files over Fabric files where both are available (MR fixed)

If a mod supports both with different jars, the Fabric version might be chosen on the Quilt loader (as Quilt has compatibility with Fabric mods). Ideally, the Quilt version should be chosen, particularly if there are differences that break the mod on Quilt. The current code isn't terribly well designed for this.

https://github.com/packwiz/packwiz/commit/65688cf2b113702a97539f9dafe6bae26eac2519 fixes this for Modrinth; hasn't been done for CurseForge yet as it's more complicated.

curseforge seems to always be more complicated


create the IBMCLoudPlatform type for the ingress operator try2

created new PR to indicate the changes as it seems old PR (https://github.com/openshift/api/pull/536) is pulling in too many files due to the api repo having changed quite a bit since that PR was opened.

cc @csrwng @derekwaynecarr using this PR as it seems cleaner the changes than https://github.com/openshift/api/pull/536

/ok-to-test

are there some logs to indicate why the verify-client-go test is failing?  it just seems to say
"Submitted failure event to sentry (id=26e749ea8a894ce4ab5a6459b6936d88)
error: could not run steps: step verify-client-go failed: test "verify-client-go" failed: the pod ci-op-9xyqn8tc/verify-client-go failed after 8m5s (failed containers: ): ContainerFailed one or more containers exited"
But doesn't give detail on what might have cause the container to exit or logs from the container

/test verify-client-go

/assign @jwforres

https://github.com/openshift/origin/pull/24346 is the corresponding openshift/origin PR

/lgtm

/assign @jwforres

/assign @derekwaynecarr

/unassign @jwforres

/test verify

@AndreaM12345 you need to re-run make update to update generated files


theme agnoster show "?"

I know maybe a lot of people have asked this question before, and i searched a lot on the internet.
I've already install powerline-font but it still show this.
what should i do?

You may have an outdated Powerline font. Download fresh ones from the main Powerline fonts repo, and make sure your Oh My Zsh installation is also up to date.
If you are using iTerm2 or another terminal emulator that has separate selections for "non-ASCII" fonts, make sure the "Non-ASCII Font" in your terminal profile is also set to a Powerline font.
See #1906, #4091, #4083, #3713, #2869.
Somebody needs to write a FAQ on this. :)

@apjanke Thank you for your answer :D
I redownload Powerline fonts repo and reinstall oh-my-zsh.But it still doesn't work for me. So I change font from menlo to Meslo LG M Regular for Powerline and that work for me.
Once again, thank you for your professional answer. It's really need someone to write a FAQ about this.

So I change font from menlo to Meslo LG M Regular for Powerline and that work for me.

Yes, that is what you should do. "Menlo" is a classic font. "Meslo" is a derivative of "Menlo". And "Meslo XXX for Powerline" is a non-standard Powerline-patched derivative of "Meslo", which is what you need to make Agnostor and other Powerline-dependent themes work.
Sorry for any confusion! (And this is not your fault; you just ran in to a compabibility/licensing/release-management/font-fallback/private-use-area mess.)

change font from menlo to Meslo LG M Regular for Powerline  ,it work for me.

yes, we should change the terminal fonts.