Python Provider: Phases after install do not have access to Python

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Python Phases after the install phase do not have access to Python or any of the installed pip packages.
I beleive the issue because the .profile file update is happening at the end of the build (introduced here https://github.com/railwayapp/nixpacks/pull/842).
Which version 1.6.0 of Nixpacks, running which python in the release phase points to the global python installation, not the python inside the virtual environment.

To reproduce
Create any phase after the install phase and try to access Python. This is often encountered when trying to run a release phase from a Procfile
Expected behavior
All phases after the install phase have access to Python and all installed packages
Environment
Nixpacks 1.6.0+

Some initial investigation:
Setting the environment inside the Dockerfile (ENV PATH="/opt/venv/bin:$PATH") does work. However, when the subsequent commands run, the Nix profile environment variables are prefixed. I am not quite sure where these are coming from.

@coffee-cup it seems this Nix profile env var are prefixed in base img
Log after FROM ghcr.io/railwayapp/nixpacks:ubuntu-168177616:

and I tried on latest master branch, cant reproduce this bug 🤔


util::var_dump high memory consumption

hello,
I noticed that the function util :: var_dump () with large variable has a large RAM consumption.
We are talking about a relatively large object from a total of 75 properties (Smarty variables, as well as project-related variables).
Allowed memory size of 268435456 bytes exhausted (tried to allocate 551 bytes) in ../abnahme/core/classes/Util.class.php on line 230
We use an Apache web server with PHP 5.5.18 on a Ubuntu server.

util::var_dump now supports recursive data structures so this shouldn't occur.


New Coinbase Pro Exchange Adapter

Hi! I have been working in a fork of your BXbot project. After the migration of GDAX API to Coinbase Pro API, a new Coinbase Pro Exchange Adapter is needed (you can check it here)
It works as the other exchanges, plus a "time-server-bias" that is needed in order to make work the private calls (you can check this issue I have open in my fork: https://github.com/DavidHuertas/bxbot/issues/2).
I have a question to make: ¿do you have in mind to add calls to the "fees" services in order to improve fees calculation further than keeping them in the "otherConfig" section of the "exchange.yaml" config file?
Thank you in advance, regards
David Huertas

Hi David
Thank you for your contribution - it's always good to see folks contributing to the project :+1:
I'll try and make some time this weekend to review the PR...
I'll also deprecate the GDAX adapter in the next release, given the exchange has been migrated from GDAX to Coinbase Pro.
Regarding fees API calls - go for it! The fees in the YAML config are fallback options for when exchanges did not expose their fees via their REST APIs. I believe the Bitstamp adapter gets its fees from the exchange's REST API.
Looks like the PR build needs fixing - SpotBugs issues from a quick look ;-)
Take your time - no rush for anything :-)
gazbert

I will review when I have time enough


Android profile or release build issue

안녕하세요. 안드로이드 profile or release 를 빌드하게 되면 아래와 같은 이슈를 내며 빌드를 실패 합니다. 현재 채널톡이 들어간 오류가 발생하는데 채널톡 라이브러리랑 연관이 있을까요?
Execution failed for task ':channel_talk_flutter:verifyProfileResources'.
> A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
   > Android resource linking failed
     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:3: AAPT: error: resource android:color/system_neutral1_1000 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:4: AAPT: error: resource android:color/system_neutral1_900 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:5: AAPT: error: resource android:color/system_neutral1_0 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:6: AAPT: error: resource android:color/system_neutral1_800 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:7: AAPT: error: resource android:color/system_neutral1_700 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:8: AAPT: error: resource android:color/system_neutral1_600 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:9: AAPT: error: resource android:color/system_neutral1_500 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:10: AAPT: error: resource android:color/system_neutral1_400 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:11: AAPT: error: resource android:color/system_neutral1_300 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:12: AAPT: error: resource android:color/system_neutral1_200 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:13: AAPT: error: resource android:color/system_neutral1_100 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:14: AAPT: error: resource android:color/system_neutral1_50 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:15: AAPT: error: resource android:color/system_neutral1_10 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:16: AAPT: error: resource android:color/system_neutral2_1000 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:17: AAPT: error: resource android:color/system_neutral2_900 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:18: AAPT: error: resource android:color/system_neutral2_0 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:19: AAPT: error: resource android:color/system_neutral2_800 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:20: AAPT: error: resource android:color/system_neutral2_700 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:21: AAPT: error: resource android:color/system_neutral2_600 not found.

     ERROR:/Users/junguk/dev/project/flutter-pawdly-partner/build/channel_talk_flutter/intermediates/merged_res/profile/values-v31/values-v31.xml:22: AAPT: error: resource android:color/system_neutral2_500 not found.

안녕하세요.
사용하신 channel_talk_flutter package 버전이 어떻게 되시나요?
2.4.0 까지는 문제가 없었던 것 확인했었고, Android의 경우 ChannelIOSdk 버전도 고정되어 있어서 자동으로 최신이 들어가지 않았을 것으로 보입니다.
2.5.0 이상 사용하고 계시다면,
조금 더 확인이 필요하겠네요.

현재 2.5.1 버전 사용중입니다!

안녕하세요.
2.5.2 버전 확인부탁드립니다.
Android gradle관련 문제였습니다.
고맙습니다.


[Fix-5830][Improvement][UI] Improve the selection style in dag edit dialog

Purpose of the pull request
Fix:#5830
Close #5830 #5352

Brief change log
dag.scss set a global selection:
.dag-model {
  background: url("../img/dag_bg.png");
  height: calc(100vh - 100px);

  ::selection {
    background: transparent;
  }

  ::-moz-selection {
    background: transparent;
  }

  ::-webkit-selection {
    background: transparent;
  }
# ...

I try to set a new background binds el-drawer.
udp.vue also updates like this above.
Verify this pull request
Manually verified the change by testing locally.

Codecov Report

Merging #5829 (71c1e2e) into dev (1f0c67b) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #5829   +/-   ##
=========================================
  Coverage     45.01%   45.02%
- Complexity     3656     3657    +1
=========================================
  Files           607      607
  Lines         24888    24888
  Branches       2835     2835
=========================================
+ Hits          11203    11205    +2
+ Misses        12613    12612    -1
+ Partials       1072     1071    -1

Impacted Files
Coverage Δ

...er/server/worker/task/AbstractCommandExecutor.java
18.27% <0.00%> (ø)

...dolphinscheduler/remote/future/ResponseFuture.java
83.05% <0.00%> (+1.69%)
:arrow_up:

...er/master/dispatch/host/assign/RandomSelector.java
83.33% <0.00%> (+5.55%)
:arrow_up:

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 1f0c67b...71c1e2e. Read the comment docs.

ping
@zhuangchong


SerializeLenghtDelimited

Stream.Position not works for NetworkStream

Use the PositionStream wrapper.
It's included in the generated code.

ProtoBuf.Serializer.Deserialize(new PositionStream(networkStream));

I hope this solved your problem.


Add network-policies for kube-state-metrics

Is there a need for a policy about kube-state-metrics accessing the Kubernetes API server? For example in a self-hosted environment the apiserver is a pod itself.

Can you elaborate? The NetworkPolicy is to allow prometheus to scrape from kube-state-metrics. Without this definition, the scraping won't happen at all. I've tested it in my environment.

That makes sense. But kube-state-metrics needs to access the apiserver, so I'm wondering why it doesn't require a NetworkPolicy. I'm not super familiar with NetworkPolicies, so I might be missing something or it might be an explicit non-goal.

That's because kube-apiserver binds to the hostNetwork which isn't affected by NetworkPolicy. Recall this conversation? :)

Thanks for clarification @eugene-chow! I didn't make that connection, I kept thinking it uses Pod networking, but this way it all makes sense.
Then lgtm :+1:


Improve Docker Build Time

I know this image isn't exactly designed for development, but I find it a little cumbersome that the build process installs pip, wheel, mod_wsgi-express, and project dependencies every time there is a code change. Would it be possible to change the COPY . /app line to COPY ./requirements.txt ./app and then run COPY . /app after running mod_wsgi-docker-build? This would only invalidate the cache if the requirements list has changed. (See Dockerfile best practices here for an example)

Your suggestion unfortunately will not work in general case as the requirements.txt file may need to reference a local package that was copied in as part of your source code. So it gets complicated.
That mod_wsgi gets reinstalled is an issue I know of. It is actually installed as part of system wide Python as well and virtual environment chains off that and it is found, but when run out of system Python mod_wsgi wasn't picking up virtual environment correctly. I need to revisit it to work out how to fix that and then I can drop second installation of mod_wsgi. It only came up that that broke things in last week and I had to revert to doing the second installation.
Anyway, I haven't got a lot of time to explain in detail right now, or check my recipe works, as at training day, but presuming running Docker locally and how your Docker system is setup allows local file system mounting, the images are specifically set up to allow you to do.
docker build myapp .
docker run -v `pwd`:/app --reload-on-changes

So you build it once to get an image with required dependencies, but then you actually mount the current directory into the container, overlaying and hiding what was copied in. You then ensure that --reload-on-changes option is also supplied to mod_wsgi-express and you can then make changes to the local file system to code files and your application will auto reload changes. This will allow you to do development.
See if you can get that going and if not tell me what OS you are using and how Docker was installed.

I kind of figured it wouldn't be that simple, but I figured I would suggest it on the off chance that it would work.
Thanks for the work around; I'll give it a shot.

The additional reinstall of pip and mod_wsgi shouldn't occur now. This is because the Python virtual environment has been done away with as it causes various problems. If you have stuff in 'requirements.txt', they will still be installed though.
The changes made are quite significant, but everything should still run okay. If you see any problems, especially with access permissions at run time, let me know ASAP.


Scoping checklists and packages

Discussed at the TWG meeting on Oct. 4.
Our understanding is that checklists are for different sequence types and packages are for different source materials or environments. With the advent of new sequencing types stable isotope fractioning of samples before sequencing, those distinctions may blur.
Can the CIG help us with defining some public guidance on when to add a new checklist vs. a package and how to handle gray areas?

This was in response to @mslarae13's suggestion for a SIP stable isotope profiling checklist or package, right?

Discussed at the CIG call on 24 Jan 2023.
Definitions and decisions:

“Checklists”

Sets of terms that describe a particular sequence type or method (genome, metagenome, mimag etc)

“Extensions”

Additions terms to describe a specific environment or sample type that can be used in combination with any sequence type

We also publish all possible combinations of checklists and extensions.

Currently call the CombinationClasses. We should name them “Packages”.

Encode this information in LinkML
Update website.

On the website, but we should have the links to checklists, extensions, and packages go to the automatically generated documentation from LinkML.
We need to either generate the website documentation automatically from the LinkML docs or have an SOP in place to make sure they stay in sync.
Need to update the figure that is under extensions on the website so that it reflects our current terminology and status of packages, etc.

Need to search github repos to see if there is any out of date documentation there. If so, move it to LinkML docs.

A few edits below:
Definitions and decisions:
“Checklists”
Defined sets of metadata terms that describe minimal information about a sequenced genome, marker gene or metagenome.
“Extensions”
Defined sets of environmental package “extensions” metadata terms that describe the specific environment of the collected sample, that can be combined with other Extensions and Checklists
Mix and Match combinations of checklists and extensions are available, to support broad utilization.
In our LinkML schema, these are currently called the CombinationClasses.
We will re-name them to “Packages”.
And encode this information in LinkML
Update website.
On the website, but we should have the links to checklists, extensions, and packages go to the automatically generated documentation from LinkML.
We need to either generate the website documentation automatically from the LinkML docs or have an SOP in place to make sure they stay in sync.
[Lynn: I vote to maintain the some static webpages, that describe the scope and description of checklists and extensions]
Need to update the figure that is under extensions on the website so that it reflects our current terminology and status of packages, etc.
Need to search github repos to see if there is any out of date documentation there. If so, move it to LinkML docs.

@lschriml , I think your definitions are a bit narrower than we want aren't they? Checklists aren't just for "sequenced genome, marker gene or metagenome" we also have microbiomes and want to include transcriptomes as well as single cell genomics, and possibly even synthetic sequences and who knows what else in the future. So can we use the more generic terminology from the meeting notes, maybe something like this:
Checklists are; Defined sets of metadata terms that describe sequences from a particular experiment type or methodology.
Extensions are; Defined sets of metadata terms that extend a given checklist to describe the specific environment and/or collection details of the collected sample(s).
Packages are; The combination of a checklist with one or more extensions.

yes, that sounds good Chris
On Wed, Jan 25, 2023 at 7:15 AM Chris Hunter @.***>
wrote:

@lschriml https://github.com/lschriml , I think your definitions are a
bit narrower than we want aren't they? Checklists aren't just for
"sequenced genome, marker gene or metagenome" we also have microbiomes and
want to include transcriptomes as well as single cell genomics, and
possibly even synthetic sequences and who knows what else in the future. So
can we use the more generic terminology from the meeting notes, maybe
something like this:
Checklists are; Defined sets of metadata terms that describe sequences
from a particular experiment type or methodology.
Extensions are; Defined sets of metadata terms that extend a given
checklist to describe the specific environment and/or collection details of
the collected sample(s).
Packages are; The combination of a checklist with one or more
extensions.
—
Reply to this email directly, view it on GitHub
https://github.com/GenomicsStandardsConsortium/mixs/issues/510#issuecomment-1403517517,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBB4DOQ5DO2YC765JZ6HFDWUEKNBANCNFSM6AAAAAAQ4WAA4A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Lynn M. Schriml, Ph.D.
Associate Professor
Institute for Genome Sciences
University of Maryland School of Medicine
Department of Epidemiology and Public Health
670 W. Baltimore St., HSFIII, Room 3061
Baltimore, MD 21201
P:<PHONE_NUMBER> |  F:<PHONE_NUMBER>
@.***

@ramonawalls , you've closed this ticket, does that mean the definition have been added to the SoT somewhere? if so, please can you mention here, exactly where they have been put, and confirm that the definitions provided by me above are the ones used? I can them update the gensc.org website with the definitions to match.


Int.div bug fix

Fixes #192

@yegor256 ready for review

@yegor256/z everybody who has role REV is banned at #209; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@yegor256, sorry, accidentally resolved the comment. For explicit error indication

@IngeniariusSoftware what's up with this? ready?

@yegor256 ready

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 5min)

Job gh:cqfn/eo#209 is not assigned, can't get performer


Filtering page: Bug report and feedback for revisions

Title line template: Filtering - Bug report and feedback for revisions

Bug report.
Error in the "Resetting filters" illustration.

Feedback on "Filter applied” illustration 2.

Feedback on "Filter interaction" section.

Page link - https://www.carbondesignsystem.com/patterns/filtering/
1. Detailed description - Bug report

Describe in detail the issue you're having.
I am confused by the illustration under “Resetting filters”. The illustration shows 1 checkbox (BBQ) with the applied filter bubble button with the number “2”.

Is this a feature request (new component, new icon), a bug, or a general issue?
Bug.

What did you expect to happen? What happened instead? What would you like to see changed?
I would expect the applied filter button with the count of “1”. Also, because the illustration uses a skeleton illustration to the right, I cannot explicitly confirm that the criteria displaying is actually “BBQ” rather than BBQ being excluded.

See also "Multiple categories" illustration uses has a count of “1”. It also uses skeleton results and is not explicitly clear that the criteria is displaying “BBQ” results.

What browser are you working in?
Firefox

What offering/product do you work on? Any pressing ship or release dates we should be aware of?
Micromedex Mobile PWA. No pressing dates.

Additional information

Screenshots
https://www.carbondesignsystem.com/static/6463d6bde4072d3236ef35304a23f885/c801a/filter-7.png

See also:
https://www.carbondesignsystem.com/static/b356a7de040357b2d544d028902cd0f4/c801a/filter-3.png
2. Detailed description - Feedback on "Filter applied” illustration 2

Describe in detail the issue you're having.
Second illustration in the “Filter applied” section shows the filter applied number as “2”.

Is this a feature request (new component, new icon), a bug, or a general issue?
Bug (a suggestion, actually).

What did you expect to happen? What happened instead? What would you like to see changed?
What I would like to see changed is the illustration showing either 1 or 3 checked boxes, rather than the current 2. Since there are 4 total checkboxes, it is not explicitly clear that the count of 2 is the number of boxes checked or unchecked. This is clear on the page for Dropdown - Multi select section - https://www.carbondesignsystem.com/components/dropdown/code/

What browser are you working in?
Firefox

What offering/product do you work on? Any pressing ship or release dates we should be aware of?
Micromedex Mobile PWA. No pressing dates.

Additional information

Screenshots
https://www.carbondesignsystem.com/static/398a3e7dc4339ae3b0058c24dd73f297/c801a/filter-6.png

3. Detailed description - Feedback on "Filter interaction" section

Describe in detail the issue you're having.
I would like to see greater clarity in this section.

First off, I love that the “Starting state” section states:

“Filters within each category should start either as all unselected or all selected.” Keep this.

Secondly, I do not think that this page should be a tutorial on faceted search IA and non-mutually-exclusive filters. But ambiguity could be addressed by answering the following questions in the content text:

Does the checked box indicate that a criteria will display or be hidden?
What will happen if all checkboxes are unchecked; what will happen of all the checkboxes are checked? (Or at least what is the general rule?).

I understand that these are tricky issues that the authors may have intentionally avoided, especially since “Filters within each category should start either as all unselected or all selected.” Here is an example from the REI e-commerce website:
START ALL UNSELECTED
https://www.rei.com/search.html?q=therm-a-rest+pads&ir=q%3Atherm-a-rest+pads&r=price%3A%240.00 to %249.99|%2410.00 to %2419.99|%2420.00 to %2449.99|%2450.00 to %2499.99|%24100.00 to %24199.99
Looking at the example link, if you ignore all non-mutually-exclusive categories (on the left pane) and only look at “Price” (a mutually-exclusive filter), you will notice that the total number of returned results for this example is 13. If I check all checkboxes OR uncheck all checkboxes, the displayed results = 13. Checking all 5 checkboxes puts the applied filters as “Price (5)”. So in this simple example, checking a box causes the criteria to display, and increments the number of applied filters as the total checked boxes in this category. When at least 1 box is checked, any unchecked boxes are hidden on the results page. HOWEVER, if all boxes are unchecked, then all results display (no filter criteria, so the applied filters = 0).
Addressing this “start all unselected” information may be good enough clarity.
START ALL SELECTED
In my project, the start is All Selected. This is because I must show drug interactions with 2 or more drugs. My category groups are not parallel so the drug category requires a minimum of 2 checkboxes, whereas all other categories require a minimum of 1 checkbox. Essentially, it is not valid to uncheck all boxes like the faceted filter used by the REI example. So for my project, when all boxes are checked, the “applied filters” bubble button does not display; if one or more boxes are unchecked, then the applied filter displays with the count of all checked boxes.
Addressing this “start all selected” information may be too much to include.

Is this a feature request (new component, new icon), a bug, or a general issue?
General issue.

What did you expect to happen? What happened instead? What would you like to see changed?
Update the content text to address these issues.

What browser are you working in?
Firefox

What offering/product do you work on? Any pressing ship or release dates we should be aware of?
Micromedex Mobile PWA. No pressing dates.

Additional information

Screenshots

Notes

hi @cardwellrobert thank you for opening this issue!
for your first point, the image will likely undergo some changes in the near future as we refresh our documentation for our v11 release!
as for your 2nd and 3rd points, since the pages have gone through some changes since you initially created this ticket, do you still feel confused about the page content and copy?

Hello emyarod:
It has been a while since I submitted this bug report, so I cannot remember
what my 2nd and 3rd points were. But reviewing the page today, I am glad
that the "Filter states" section indicates "each category should start
either as all unselected or all selected."
As for the images, they look better except the last image which has 1
checkmark and "2x" on the filter bubble button. This is confusing compared
to the other image examples on the page:
Thanks,
Robert Cardwell
User Experience Designer, Provider & Payer
IBM Watson Health™
6200 S Syracuse Way, Suite 300, Greenwood Village, CO 80111
303-486-9045 office
402-889-3642 mobile
@.***
From:	emyarod @.>
To:	carbon-design-system/carbon-website
@.>
Cc:	cardwellrobert @.>, Mention
@.>
Date:	06/07/2021 10:26 AM
Subject:	[EXTERNAL] Re: [carbon-design-system/carbon-website] Filtering
page: Bug report and feedback for revisions (#718)
hi @cardwellrobert thank you for opening this issue! for your first point,
the image will likely undergo some changes in the near future as we refresh
our documentation for our v11 release! as for your 2nd and 3rd points,
since the pages have
hi @cardwellrobert thank you for opening this issue!
for your first point, the image will likely undergo some changes in the
near future as we refresh our documentation for our v11 release!
as for your 2nd and 3rd points, since the pages have gone through some
changes since you initially created this ticket, do you still feel confused
about the page content and copy?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

thanks for following up. it's good to know that the page has improved since you first reported these issues and be on the lookout for more substantial changes as we get ready for the next Carbon major version release


menu-close directive / attribute no longer working?

Hi, it seems there's no way to make elements close the sidebar on / after click anymore?
the attribute menu-close (as seen in the demo) doesn't seem to work anymore, as does ion-data-menu-close or putting any of the above as classnames into the class - attribute.
And I don't even see how I can close the menu via javascript manually, which at least would it possible for me to create a workaround. Is there a straightforward way?
Could you maybe give an overview over the new features using the angular controllers etc. directly? I mean, is there some API we can use, a change in how we interact with meteoric / ionic?
By the way, would you see this fork as kind-of stable still or would you rather suggest people to not use it for projects needing some level of stability right now while you're mixing things up? Is stability (API-Stability and working stability) a primary concern for you at the moment?
Thanks and best wishes
Daniel

@DanielDornhardt Sorry for the problem. First and foremost, this thing is not stable. What browser/device are you testing menu-close? It works on mobile mode in chrome but once the width of the screen width >768, the exposeAsideWhen="large" is activated and the side menu is always expose then.
I'll amend README and mark this as UNSTABLE.

Hi, i'm not sure what you mean with mobile mode in chrome...
With the latest version, when added to the demo app I can't close the side menu by clicking  "Close Me" button inside the left side menu, no matter which size.
I think you got rid of the "snapper"? So I can't even close it manually. IonSideMenu.close() isn't implemented anymore either I think.
Sooo..

What I'd like to see would be a stable branch of the repo, call it master, if you will, and try to keep that mostly stable and feature - complete. Smaller bugfixes and non-breaking enhancements can go there and people can use it and contribute there so that the community would have a stable version to gather around.
For the other things, do feature branches or an "experimental" branch to try them out and invite people to get feedback.
I really think meteor-ionic provides a lot of value and I'd be willing to add some small amount to eg. patreon to give you a regular additional income.
I'd be interested in learning / reading more about the new demo / docs page you did and what your overall goals and development "strategies" are.

@DanielDornhardt Yeah, I'll tag the meteoric one. My bad about that. I'll make an experimental branch as of this. I'll discuss this later (menu-close), work atm. If possible, is the menu-close outside or inside the ionSideMenuContainer?

Hey Joey,
it's inside of {{#ionSideMenuContainer side="left"}} - but it's possible that it gets set dynamically / via a helper or somesuch or that it's actually rendered from inside another child template sometimes.
I couldn't actually find any place where it would be read in the meteoric code - how should the detection of the attribute actually work? Which code should be triggered?
No worries about being at work etc, I think we're "asynchronous", you're from the 'Mericas and i'm from the 'europes it seems... so it's always a message here, another message tomorrow mostly :)
That's why I keep on writing such long texts as well so that you can at least get me :)

@DanielDornhardt It should be around here: https://github.com/JoeyAndres/meteor-ionic/blob/master/lib/blaze.js#L5 and then here it gets attached to a click event. I guess you can check if $element exist, or if the menuToggle "delegate" is being initialized in the first place.
In the mean time, I also have meteoric.service.ionicSideMenuDelegate and you can manually close sidemenu from their. I need to deprecate those IonSideMenu globals in favour of this more ionic like delegates (granted it's not being used like angular, its still cleaner imo),

Recent changes to template-scope/template-attribute directive should've fix this. Feel free to reopen if experiencing this issue again.


Add docker image for cargo contract

The docker images won't contain the node's environment. So if users want to run behavior tests and deploy seed data, users need to install the node/npm in their environment.

@sfffaaa referring to our conversation let's please maintain only one build image for the node/contracts. Can you please ensure the following image is upto date to build the contract? it already builds the node correctly.
https://github.com/peaqnetwork/peaq-network-node-docker-builder

@sfffaaa referring to our conversation let's please maintain only one build image for the node/contracts. Can you please ensure the following image is up to date to build the contract? it already builds the node correctly.

My bad, I've removed the docker image here and moved it to the other project. Therefore, this MR only updates the README.


MOE Sync 2019-11-01

This code has been reviewed and submitted internally. Feel free to discuss on
the PR, and we can submit follow-up changes as necessary.
Commits:
 maven:  use 'https' instead of 'http'
Fixes #1391
b40559db1bf1d00cf8a4294a9c0a61ec81a48693

 Do not report toString calls on lite protos for info logging
46df469afb987d53fae0e60557e962ac02a9ce9e

 InterruptedExceptionSwallowed: flag methods which declare they throw Exception, but actually throw an InterruptedException.
ea8406f1fc0e3e640b5303b888aa1198285d79bc

Adding cla:yes because b40559db1bf1d00cf8a4294a9c0a61ec81a48693 comes from @sullis's PR #1391.


PDN documentation is out of date

Description
PDN documentation is out of date, for example, #537 still tries to use custom ports without a custom pdn config file.
This should be updated.

I've received clarification that it's not incorrect- just incomplete. The current documentation overhaul efforts should address that.


[ERR] domain.com: Something error

Hello,
I've just installed and tried to run but I'm receiving this error:
Enter a domain to analyze:domain.com
·▄▄▄▄   ▐ ▄ .▄▄ ·▄▄▄▄▄ ▄▄▄· ▄ •▄ ▄▄▄ .
██▪ ██ •█▌▐█▐█ ▀.•██  ▐█ ▀█ █▌▄▌▪▀▄.▀·
▐█· ▐█▌▐█▐▐▌▄▀▀▀█▄▐█.▪▄█▀▀█ ▐▀▀▄·▐▀▀▪▄
██. ██ ██▐█▌▐█▄▪▐█▐█▌·▐█ ▪▐▌▐█.█▌▐█▄▄▌
▀▀▀▀▀• ▀▀ █▪ ▀▀▀▀ ▀▀▀  ▀  ▀ ·▀  ▀ ▀▀▀
    (c) pwnesia.org — v0.0.1

[ERR] domain.com: Something error

Had the same issue.
Tested on MacOS 11.5.2 and Kali 2021.2

Can you guys send the details to my Discord (dw1#0001) or DM me on Twitter?

Just sent you a strace from a Kali on Twitter

I confirm that this is not a problem with DNSTake. See new release.


fedifetcher: 5.0.1 -> 7.0.1

Description of changes
#259245 cc @nifoc
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Appears to be working - thanks for the quick update!
Next time I'll try to submit a PR myself. Looks like updating it is rather simple 🙂

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1182

(Self merging since this has ~ 0 complexity and has a review from a user of the derivation.)


Allow paging support

Expose start and max rows. It will help users to fetch data with paging

Implemented as part of pull request https://github.com/santanusinha/dropwizard-db-sharding-bundle/pull/6... closing it


TestApp C# example

Can you please release a TestApp example but for C# instead of C++?

I'll think about it

I won't be implementing it in the foreseeable future, so I'm closing this for now.


ES2020 Feature: BigInt

Syntax:
New NumericLiteral syntax with a n suffix. Only decimal numbers with a suffix are valid. LegacyOctal or leading zeros are not valid.
123n

Grammar changes are to NumericLiteral. Basically allowing the BigInt n suffix on modern binary, octal, and hex numbers, or non-legacy-octal decimal literals.
  NumericLiteral::
      LegacyOctalIntegerLiteral
      DecimalLiteral
+     DecimalIntegerLiteral BigIntLiteralSuffix
+     NumericLiteralBase
+     NumericLiteralBase BigIntLiteralSuffix
-     BinaryIntegerLiteral
-     OctalIntegerLiteral
-     HexIntegerLiteral

+ NumericLiteralBase::
+     BinaryIntegerLiteral
+     OctalIntegerLiteral
+     HexIntegerLiteral
+
+ BigIntLiteralSuffix  ::  n

Spec:
TC39:
https://github.com/tc39/proposal-bigint
https://tc39.es/proposal-bigint/
ESTree:
https://github.com/estree/estree/blob/master/es2020.md

Literal
extend interface Literal <: Expression {
    type: "Literal";
    value: string | boolean | null | number | RegExp | bigint;
}

value property can be a BigInt value to represent BigInt literals
such as 100n.

BigIntLiteral
interface BigIntLiteral <: Literal {
  bigint: string;
}

bigint property is the string representation of the BigInt value.
It doesn't include the suffix n.
In environments that don't support BigInt values, value property will be
null as the BigInt value can't be represented natively.

Additional considerations

Supported in Chrome and Firefox. Experimental in WebKit
Supported in Node

Remaining Tasks:

[ ] Add new BigIntLiteral node (nodes.ts, docs/syntax-tree-format.md)
[ ] Update Scanner (scanner.ts changes for n numeric suffix)
[ ] Update Parser (parser.ts to create a BigIntLiteral node for those numeric literals)
[ ] Provide Unit Tests and Coverage (see below)
[ ] Update test262 (~test262.git#2ee3864136) / test262-stream (~1.3.0) (note that test.attrs.negative.phase === 'early' should also now handle test.attrs.negative.phase === 'parse')
[ ] Handle runtimes where globalThis.BigInt is available and not available (may require updating typescript to ~3.4

Test Cases
Valid:
0n
123n
0x123n
0o123n
0b101n

Invalid:
1.1n
1e1n
01n // Leading Zero (legacy hex) does not allow it
00n // Leading Zero does not allow it
09n // Leading Zero does not allow it

The tricky part about this is whether or not globalThis.BigInt is available.
If it is, then the BigIntLiteral's value property is a BigInt value.
If it is not, then the BitIntLiteral's value property is null.
Test coverage for that may require istanbul comments along the lines of:
const value = globalThis.BigInt ? globalThis.BigInt(string) : /* istanbul ignore next */ null;
return {
    type: Token.NumericLiteral,
    value: value,
    ...
};

Given unit tests run with a node where BigInt will be available but some browsers may not have it available.

I've created a pull for this in my fork: https://github.com/node-projects/esprima-next/pull/12

"dependencies": {
"esprima": "^4.0.1",
}

"dependencies": {
"esprima": "^4.0.1",
}
In my pakage.json，I use esprima-version-4.0.1 ， but  it's error when parsing bigint code, such as  "var x = 0x123n".
How to use the new Feature about ES2020:BigInt?

@famgy I've created a fork: esprima-next wich has support. https://github.com/node-projects/esprima-next

@famgy I've created a fork: esprima-next wich has support. https://github.com/node-projects/esprima-next
"dependencies": {
"@babel/core": "^7.16.5",
"@babel/preset-env": "^7.16.5",
"esprima-next": "^5.7.0"
}

usage:
var BABEL = require("@babel/core"),
ESPRIMA = require("esprima-next")
var esCode = BABEL.transform('var x = 0x123n', {
presets: ["@babel/preset-env"]
}).code
var astCode = ESPRIMA.parseScript(esCode)
But, It's Error :
Error: Line 3: Unexpected token ILLEGAL
at e.constructError (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:20546)
at e.createError (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:20765)
at e.throwError (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:20888)
at e.throwUnexpectedToken (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:122742)
at e.scanHexLiteral (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:131016)
at e.scanNumericLiteral (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:133188)
at e.lex (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:139302)
at e.nextToken (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:55026)
at e.parseVariableDeclaration (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:91452)
at e.parseVariableDeclarationList (E:\Projects\JavaScript\jsobfx-es2020\node_modules\esprima-next\dist\esprima.js:1:91724) {
index: 28,

I've been fixing issues with parsing on .NET side: https://github.com/sebastienros/esprima-dotnet/pull/214 , currently I haven't found any new problems with the current WIP version while integrating Jint with it.

@famgy
my fork is not an ES5 lib and more, so it should be loaded via "import".

After clone esprima-next, and run test:
var ESPRIMA = require('.');
It's OK ，such as ：
var astCode = ESPRIMA.parseScript('var x = 123n', { tolerant: true })
It's Error, such as:
var astCode = ESPRIMA.parseScript('var x = 0x123n', { tolerant: true })
Is it the result that "123n" is valid, but "0x123n" is invalid ?


Not able to run tiny-yolo-image-loop.ipynb

I was not able to run tiny-yolo-image-loop.ipynb out of the box, when trying to run the code in the box after "2. Launch Demo", I got this error
NameError                                 Traceback (most recent call last)`
<ipython-input-3-282cc81fa050> in <module>()
     59             print("class: {}\tprobability: {}".format(det[1], det[0]))
     60         res = Image.open(file_name_out.value.decode() + ".png")
---> 61         display(res)

NameError: name 'display' is not defined

I was able to fix this with adding the following line to the imports
from IPython.display import display

Hi,
which PYNQ image are you using?
You can discover the version with the instruction: python3.6 -m pip show pynq

Hello sorry for the delayed response, this is the output of the command:

Name: pynq
Version: 1.4
Summary: Python for Xilinx package
Home-page: https://github.com/Xilinx/PYNQ
Author: XilinxPythonProject
Author-email<EMAIL_ADDRESS>License: UNKNOWN
Location: /opt/python3.6/lib/python3.6/site-packages
Requires:

Hi,
so the problem is that you are using an old image. Please download the latest 2.1 image here.


Terraform Cloud Backend

[ ] Configure Terraform Cloud Backend
[ ] Workaround for Terraform Login
[ ] Migrate our local state to remote state
[ ] Create a new Project and Workspace in Terraform Cloud


Update ListView.md

execute spellings on line 42

Q
A

Bug fix?
[X ]

New feature?
[ ]

New sample?
[ ]

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Typos
Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
Guidance

You can delete this section when you are submitting the pull request.
Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to dev branch.

Thank you @aroraans1512 for the fix.
It has been manually merged and will be included in the next release.


Update with to support running directly on Python 3.

This should be merged, works perfectly :)
Maybe add the folders back into the project as they do not get tracked when empty but are required :)

I'm having the error Cannot find default settings in colorSchemeTool.log log file, any solution ?
Python 3.10.10

@emiliadecaudin Worked for me too! I agree with @JohnMeyerhoff

Implemented by another PR.


Interpreting alpha

The above subset of the data gives me an alpha value of 0, and I am stumped becauset he data looks a lot like the one in the documentation. Can you please help me understand what's going on here?

Hi,
In your case there is a single experiment. Kripendor's alpha tries to estimate how much more likely the agreement is than a random guessing. Since there is only one experiment, the calculations estimation of random makes it so that it can't distinguish between your input and random, hence  a value of 0.
Try doing the same with more than 1 experiment


IndexError: list index out of range

I have trained a model without self-critical, and run eval.py， an error occurs:
File "/host/xx/self-critical/eval_utils.py", line 143, in eval_split
    lang_stats = language_eval(dataset, predictions, eval_kwargs['id'], split)
  File "/host/xx/self-critical/eval_utils.py", line 39, in language_eval
    cocoRes = coco.loadRes(cache_path)
  File "/usr/local/lib/python3.5/dist-packages/pycocotools/coco.py", line 318, in loadRes
    if 'caption' in anns[0]:
IndexError: list index out of range

How should I do?

I use default parameters batch_size=0
I found something stange, when evalating, the image_id is not correct, it is start from 0 to num_images:

so it can find cooresponding index from 'captions_val2014.json'
but I don't know why the index is wrong, and how to solve it

I have fixed this problem by change
entry = {'image_id': data['infos'][k]['id'], 'caption': sent}
to
entry = {'image_id': int(data['infos'][k]['file_path'].split('_')[-1].split('.')[0]), 'caption': sent}  in eval_utils.py

@ruotianluo I trained self-critical model using default parameters, and an error occurs:

data['att_masks'][np.arange(loader.batch_size) * loader.seq_per_img] if data['att_masks'] is not None else None]
KeyError: 'att_masks'

I followed the latest comment in #42 to change 96 line in eval_utils, but other problem occurs:

data['att_masks'][np.arange(loader.batch_size) * loader.seq_per_img] if 'att_masks' in data is not None else None]

TypeError: 'NoneType' object is not subscriptable

How should I do ?  Thank you very much

I think I can both train and eval the model now.
This is for training:
 data['att_masks'][np.arange(loader.batch_size) * loader.seq_per_img] if data['att_masks'] is not None else None]
This is for evaluating:
data['att_masks'][np.arange(loader.batch_size) * loader.seq_per_img] if 'att_masks' in data is not None else None]

I have fixed this problem by change
entry = {'image_id': data['infos'][k]['id'], 'caption': sent}
to
entry = {'image_id': int(data['infos'][k]['file_path'].split('_')[-1].split('.')[0]), 'caption': sent} in eval_utils.py

thank you very much ! this help me solve the same problem in repo ruotianluo/ImageCaptioning.pytorch


Feature/33 create 03 misc 03 tree shaking type script implementation

Close #33

@brauliodiez, you are go to like this. One reason to use TypeScript => Babel => ES5


PCA label colour  doesn't change in key

Using comm-SYMCL data, I create an admixture chart.
I pick a group and change the colour -- works well the icon colour of the individual elements change but not the colour in the key
Similarly the icon change does result in the key changing

If I export the project and reimport the changes are visible.


Add chnges in abao plus pin python-dateutil version

Reference changes: https://github.com/Yelp/elastalert/compare/master...alexbao:master

•https://github.com/google/skylark/pull/87.patch

Can you resolve conflicts please :)

Can you resolve conflicts please :)


Can I use 2 PS eye camera instead of 1?

Will I be able to get positional tracking from 1 camera or do I need 2 cameras to do so.
Also is room scaling possible with this

You can get positional tracking from just one camera, but it has to use the bulb size in screen to estimate distance so it's more noisy than if you have two or more cameras to triangulate the controller. We currently support up to 4 cameras. The max tracking distance from the camera is a not 5-6 feet. The fov is 75 degrees which is a bit on the narrow size. So I wouldn't say you could get room scale per se, but you can get 360 degree coverage with 3 cameras.

Ok, thank you. So will 3 camera be able to do room scale? Where would I put them?

I guess it depends on what you define as "room scale". If your room is a tiny office like the room I tested in, then sure. You could so something like this:

But definitely not Vive or Oculus tracking volume sizes. I am working on supporting higher resolution cameras that will help with range, but for the time being the best volume size you are going to get is around 6 feet x 6 feet

Ok only have a area of 6feet x 6 feet. Thank you

Would this work with Vridge?

PSMoveService doesn't explicitly support VRidge, but there is another SteamVR plugin for VRidge that you can use along side PSMoveService. I have no experience with that. But @zelmon64 and few others who have posted on here have set that up.

I'm closing the issue for tracking purposes since it looks like we answered the original question, but please feel free to continue discussion if you have any other questions related to this issue.


Make it an official plugin 🥳

Hey @Keisir,
Could you add me to a collaborator so that I can move this repo to https://github.com/inkdropapp ?
I'll republish the plugin as "alerts" as GitHub calls them in their official docs.

Hey @craftzdog!
I have sent out an invitation. Feel free to make it an official plugin.

Thank you! But it looks like I can't transfer this repository to the inkdropapp organization 🤔
I guess only you can do that: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account

it works!! Thanks so much 🙌


Unable to get Vimeo video (youtube-dl version 2015.11.10)

youtube-dl.exe --verbose --get-url https://vimeo.com/channels/staffpicks/145366920
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'--get-url', u'https://vimeo.com/channels/staffpicks/145366920']
[debug] Encodings: locale cp950, fs mbcs, out cp950, pref cp950
[debug] youtube-dl version 2015.11.10
[debug] Python version 2.7.10 - Windows-7-6.1.7601-SP1
[debug] exe versions: none
[debug] Proxy map: {}
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "youtube_dl\extractor\vimeo.pyo", line 378, in _real_extract
File "youtube_dl\extractor\common.pyo", line 584, in _search_regex
RegexNotFoundError: Unable to extract view count; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "youtube_dl\YoutubeDL.pyo", line 661, in extract_info
File "youtube_dl\extractor\common.pyo", line 290, in extract
File "youtube_dl\extractor\vimeo.pyo", line 427, in _real_extract
File "youtube_dl\extractor\common.pyo", line 766, in _sort_formats
ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

This bug is fixed if video_upload_date is None.
https://github.com/YuheiNakasaka/youtube-dl/blob/fix-vimeo/youtube_dl/extractor/vimeo.py#L378

@YuheiNakasaka totally unrelated.
Duplicate of #7460.


[CSBindings] Cache already computed type variable bindings

To avoid re-computing same bindings over and over again,
let's try to keep a cache of active bindings and invalidate
them as needed.
Invalidate bindings conservatively when new constraints are
introduced (even if such constraints are not going to result
in new type bindings), and when type variables are assigned
fixed types or merged together.
Invalidation also makes sure to erase bindings of all adjacent
type variables related to equivalence class of the variables
in question.
This significantly speeds up use-cases which have a lot of type
variables such as collection literals with arbitrary nesting.

@swift-ci please smoke test compiler performance

Build comment file:
Summary for master smoketest
Unexpected test results, excluded stats for Kingfisher, ReactiveCocoa
No regressions above thresholds

Debug

debug brief
debug detailed

Release

release brief
release detailed

Debug

debug brief

Regressed (0)

name
old
new
delta
delta_pct

Improved (0)

name
old
new
delta
delta_pct

Unchanged (delta < 1.0% or delta < 100.0ms) (3)

name
old
new
delta
delta_pct

Frontend.NumInstructionsExecuted
167,425,092,535
167,656,498,085
231,405,550
0.14%

LLVM.NumLLVMBytesOutput
9,520,188
9,520,188
0
0.0%

time.swift-driver.wall
21.1s
21.0s
-103.8ms
-0.49%

debug detailed

Regressed (0)

name
old
new
delta
delta_pct

Improved (0)

name
old
new
delta
delta_pct

Unchanged (delta < 1.0% or delta < 100.0ms) (23)

name
old
new
delta
delta_pct

AST.NumImportedExternalDefinitions
4,461
4,461
0
0.0%

AST.NumLoadedModules
1,338
1,338
0
0.0%

AST.NumTotalClangImportedEntities
17,614
17,614
0
0.0%

AST.NumUsedConformances
1,352
1,352
0
0.0%

IRModule.NumIRBasicBlocks
32,442
32,442
0
0.0%

IRModule.NumIRFunctions
16,460
16,460
0
0.0%

IRModule.NumIRGlobals
14,175
14,175
0
0.0%

IRModule.NumIRInsts
443,509
443,509
0
0.0%

IRModule.NumIRValueSymbols
29,370
29,370
0
0.0%

LLVM.NumLLVMBytesOutput
9,520,188
9,520,188
0
0.0%

SILModule.NumSILGenFunctions
7,843
7,843
0
0.0%

SILModule.NumSILOptFunctions
10,695
10,695
0
0.0%

Sema.NumConformancesDeserialized
22,077
22,077
0
0.0%

Sema.NumConstraintScopes
70,304
70,300
-4
-0.01%

Sema.NumDeclsDeserialized
214,844
214,844
0
0.0%

Sema.NumDeclsValidated
16,273
16,273
0
0.0%

Sema.NumFunctionsTypechecked
6,058
6,058
0
0.0%

Sema.NumGenericSignatureBuilders
7,103
7,103
0
0.0%

Sema.NumLazyGenericEnvironments
48,291
48,291
0
0.0%

Sema.NumLazyGenericEnvironmentsLoaded
2,333
2,333
0
0.0%

Sema.NumLazyIterableDeclContexts
39,816
39,816
0
0.0%

Sema.NumTypesDeserialized
91,936
91,936
0
0.0%

Sema.NumTypesValidated
13,937
13,937
0
0.0%

Release

release brief

Regressed (0)

name
old
new
delta
delta_pct

Improved (0)

name
old
new
delta
delta_pct

Unchanged (delta < 1.0% or delta < 100.0ms) (3)

name
old
new
delta
delta_pct

Frontend.NumInstructionsExecuted
222,171,391,941
222,251,820,743
80,428,802
0.04%

LLVM.NumLLVMBytesOutput
10,644,604
10,644,588
-16
-0.0%

time.swift-driver.wall
36.9s
36.9s
-14.6ms
-0.04%

release detailed

Regressed (0)

name
old
new
delta
delta_pct

Improved (0)

name
old
new
delta
delta_pct

Unchanged (delta < 1.0% or delta < 100.0ms) (23)

name
old
new
delta
delta_pct

AST.NumImportedExternalDefinitions
1,111
1,111
0
0.0%

AST.NumLoadedModules
105
105
0
0.0%

AST.NumTotalClangImportedEntities
4,574
4,574
0
0.0%

AST.NumUsedConformances
1,354
1,354
0
0.0%

IRModule.NumIRBasicBlocks
34,584
34,584
0
0.0%

IRModule.NumIRFunctions
15,008
15,008
0
0.0%

IRModule.NumIRGlobals
13,708
13,708
0
0.0%

IRModule.NumIRInsts
333,412
333,412
0
0.0%

IRModule.NumIRValueSymbols
27,662
27,662
0
0.0%

LLVM.NumLLVMBytesOutput
10,644,604
10,644,588
-16
-0.0%

SILModule.NumSILGenFunctions
6,076
6,076
0
0.0%

SILModule.NumSILOptFunctions
9,041
9,041
0
0.0%

Sema.NumConformancesDeserialized
15,090
15,090
0
0.0%

Sema.NumConstraintScopes
69,419
69,415
-4
-0.01%

Sema.NumDeclsDeserialized
45,610
45,610
0
0.0%

Sema.NumDeclsValidated
10,362
10,362
0
0.0%

Sema.NumFunctionsTypechecked
4,162
4,162
0
0.0%

Sema.NumGenericSignatureBuilders
2,079
2,079
0
0.0%

Sema.NumLazyGenericEnvironments
10,068
10,068
0
0.0%

Sema.NumLazyGenericEnvironmentsLoaded
201
201
0
0.0%

Sema.NumLazyIterableDeclContexts
5,826
5,826
0
0.0%

Sema.NumTypesDeserialized
26,675
26,675
0
0.0%

Sema.NumTypesValidated
7,103
7,103
0
0.0%

@swift-ci please test source compatibility

Failure was:
14:56:39 ld: warning: Could not find auto-linked library 'swiftMetal'
14:56:39 Undefined symbols for architecture x86_64:
14:56:39   "__swift_FORCE_LOAD_$_swiftMetal", referenced from:
14:56:39       __swift_FORCE_LOAD_$_swiftMetal_$_Vision in Vision.o
14:56:39      (maybe you meant: __swift_FORCE_LOAD_$_swiftMetal_$_Vision)
14:56:39 ld: symbol(s) not found for architecture x86_64

Let's try again...

@swift-ci please clean test source compatibility

@swift-ci please clean test source compatibility

@swift-ci please test source compatibility

@rudkx Yes, that’s an assumption. I am just trying to take it one step at a time, the problem with updating bindings in-place is that we don’t currently record bindings which bind two type variables directly, so that has to be fixed before update in-place is possible...

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - e880f55a68f2a85ebf0a2d7f54112442bc58c016

Build failed
Swift Test Linux Platform
Git Sha - e880f55a68f2a85ebf0a2d7f54112442bc58c016

SGTM!

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - cb887c840303c7fa4163e9cd5c9df8e6d1df6936

Build failed
Swift Test Linux Platform
Git Sha - cb887c840303c7fa4163e9cd5c9df8e6d1df6936

@swift-ci please smoke test

Build failed
Swift Test OS X Platform
Git Sha - 18da183f384249814cde13a77d2702443ef52dd7

@swift-ci please test macOS platform

@swift-ci please test source compatibility


Documenation missing details on scale up\down scenarions

In the documentation, there was a reference on how to use the API JSON file to scale up \ down the deployment. I did not see further details. How can I add \ remove nodes to an existing agents, master or add \ remove new agent pools?

this is a duplicate of #108 and #108 has more info so closing this one.

@anhowe I think you meant to reference another issue than #108 (because this is issue #108) I can't find the other one though. Which issue contains more information?

#109 provides more details.


Feature request: Provide old values for deep property changes

Currently, only single property observers get the old and new values; a sub-property observer only receives the current value; and deep property change records don't include a field for the old value.
Obviously sub-property observers can't be changed to report the old value since they can only use the value as the single argument; but adding a new field "oldValue" to the change record for deep property observers wouldn't break anything.
It's currently very hard or maybe even impossible in corner-cases to reconstruct the previous value, but it should be relatively easy for Polymer to retrieve it.
http://codepen.io/hanger/pen/NAObRZ?editors=0012
Changing hello to world calls the three different observers I have on the property like this:
propertyObserver("world", "hello")
pathObserver("world")
deepObserver({base: "world", path: "myprop", value: "world"})

Polymer({
  is: 'x-test',
  properties: {
    myprop: {
      type: Object,
      observer: 'propertyObserver'
    }
  },
  observers: [
    'pathObserver(myprop)',
    'deepObserver(myprop.*)',
  ],
  propertyObserver() { console.log('propertyObserver', arguments); },
  pathObserver() { console.log('pathObserver', arguments); },
  deepObserver(){ console.log('deepObserver', arguments); },
  ready() {
    console.log('ready');
    this.myprop = 'hello';
    this.myprop = 'world';
  }
});

My use-case in this instance is this: I want to build an undo manager for a complex editor which stores its entire state as one JSON object at the root, with sub-editors simply binding to paths. The JSON can be loaded/stored directly using i.e. iron-ajax.
To avoid hooking the undo behavior into every single control, I want to use one deep observer trackUndo(data.*) and save {path, newValue, oldValue} records, so that I can simply undo this.set(path, newValue) as this.set(path, oldValue).
Currently, to get the old value, I'm manually recording the previous observed values, which works for cases like prop = {}; set('prop.deep', 123); but not for prop = {deep: 123}; which doesn't notify on the 'prop.deep' path...
const previous = new Map();

trackUndo(change) {
  const old = previous.get(change.path);
  doSomething(change.value, old);
  previous.set(change.path, change.value);
}

For performance (mostly memory) reasons we do not store this data. If you would like to implement this behavior, it should be straightforward to store the data in a "previous" variable (http://jsbin.com/nolaborabu/edit?html,console,output). Since we have no plans on storing more information on Polymer elements and a userland solution is available, I am closing this issue. If you feel we have missed a use-case, feel free to reopen and we can discuss it!


Locks up when debugging

Sometimes when I'm in the middle of debugging a script, the editor appears to lock up and continues to think that it is debugging. I have to restart Rhino to fix this.
To reproduce, at least some times, set a break point and when you hit it in debugging, select some text in the editor and Delete or backspace, then type a couple of characters, Nothing happens, so then remember that you are debugging and click RunToEnd. That should lock it up.

http://mcneel.myjetbrains.com/youtrack/issue/RH-30034


Prepare Solidus Multi Domain for Solidus 3.0

Update this extension so that it works with Solidus 3.0 by making sure the specs pass.

I'd like to help with this one too!

I'm not going to finish this today (and not in the next days), so I will remove myself from the card.
The specs are passing till 2.11, so I will leave the card where it is now.

I opened a PR to track the work on that.
I get two deprecation warnings and I'm not sure on the direction to take to fix them:
DEPRECATION WARNING: Spree::Store.current is DEPRECATED
DEPRECATION WARNING: by_url is deprecated and will be removed from Solidus 3.0 (Spree::Store.by_url is DEPRECATED)

I found that this PR is related: https://github.com/solidusio/solidus/pull/1993
In the description I read:

move out of core the logic that checks requests info to determine if another store has to be used. This will be moved to solidus_multi_domain.

But I think it was never done.
In my own app I'm already using a custom Spree::CurrentStoreSelector to select the store based on the given domain.
Should I just copy my custom class and set the preference using an initializer like in my own app?
Or use the code linked in the description?

I've found a commit that could fix this issue, but it never landed here.

I think the problem is in the tests that are still using the old (deprecated) by_url and current methods.
What should be the fix here? Just remove the tests? Because they are tests for methods not defined in the extension itself.
I really don't know at this point...
In the meantime I found also other PRs:
https://github.com/solidusio/solidus/pull/2041
https://github.com/solidusio/solidus/pull/2022
So I think it should be clarified the way that I should follow here, because I read that this extension should be deprecated in favor of the solidus core including the same functionality.

I'm not sure all the features of this extension have been ported in core but yes, the idea was to remove from here what is already provided by Solidus and keep the extension only for the rest of the features.

Hm... yes, but as I said I was confused by the other PR to simplify the store selection: https://github.com/solidusio/solidus/pull/1993
Since the description said

move out of core the logic that checks requests info to determine if another store has to be used. This will be moved to solidus_multi_domain.

I don't know what should be done now to fix these deprecation warnings, just remove the tests?
I don't know how to change them to be able to pass the CI and since the by_url and current methods are removed, I think it's fine to do it.
The selection of the current store was delegated to the store selector classes: https://github.com/solidusio/solidus/tree/master/core/app/models/spree/store_selector, so I don't know if it's needed to provide a store selector here.

I was working on this the other day and ended up just implementing that deprecated functionality in the store decorator:
          scope :by_url, lambda { |url| where("url like ?", "%#{url}%") }

          def self.current(store_key)
            current_store = ::Spree::Store.find_by(code: store_key) || ::Spree::Store.by_url(store_key).first if store_key
            current_store || ::Spree::Store.default
          end

          private

          def store_key
            @request.headers['HTTP_SPREE_STORE'] || @request.env['SERVER_NAME']
          end
        end
      end

This passed the test's through 2.11 with no deprecations, but I then ran into a couple of errors when running 3.0:
  1) Spree::Api::ProductsController show when the product is added to the store requesting the right store for the product returns a successful product with successful code
     Failure/Error: expect(response.response_code).to eq(200)

       expected: 200
            got: 401

       (compared using ==)
     # ./spec/requests/spree/api/products_controller_spec.rb:40:in `block (5 levels) in <top (required)>'

  2) Spree::Api::ProductsController show when the product is added to the store requesting a wrong store for the product returns 404
     Failure/Error: expect(response.response_code).to eq(404)

       expected: 404
            got: 401

       (compared using ==)
     # ./spec/requests/spree/api/products_controller_spec.rb:33:in `block (5 levels) in <top (required)>'

  3) Spree::Api::ProductsController show when the product is not added to the store returns 404
     Failure/Error: expect(response.response_code).to eq(404)

       expected: 404
            got: 401

       (compared using ==)
     # ./spec/requests/spree/api/products_controller_spec.rb:20:in `block (4 levels) in <top (required)>'

  4) Store promotion rule Can add a store rule to a promotion
     Failure/Error: select2_search store.name, from: "Choose Stores"

     Capybara::ElementNotFound:
       Unable to find css ".select2-container" within #<Capybara::Node::Element tag="div" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/DIV[1]/DIV[1]/FIELDSET[1]/FORM[2]/FIELDSET[1]/DIV[2]/DIV[2]/DIV[1]">
     # ./spec/features/admin/promotion_rule_store_spec.rb:18:in `block (2 levels) in <top (required)>'

I have not investigated this error too much yet and was hoping to get out a fix by the end of the week.

I don't know if it's useful to re-implement deprecated methods that were in the core just to find the current store.
Since there is a legacy class that does the same without the need of the methods.

I agree with @afdev82. We need to update the gem to use the core functionalities instead of re-implementing the deprecated ones.

The selection of the current store was delegated to the store selector classes: https://github.com/solidusio/solidus/tree/master/core/app/models/spree/store_selector, so I don't know if it's needed to provide a store selector here.

The default store selector provided in core already select the current store based on the domain of the request: https://github.com/solidusio/solidus/blob/6c0da5d618a6d04d13ef50ec01ae17c3b06f6259/core/app/models/spree/store_selector/by_server_name.rb. Maybe it's just a matter to use this without re-implementing any new selector?

I could just remove these lines and see if the tests pass.

I can confirm the tests fail with Solidus v3 as already said by @cpfergus1

The 401 you encountered is that the tests are using X-Spree-Token which is deprecated instead of Authentication: Bearer
that will help you push past that one!

Yes, you are right. I found also a PR that was not merged regarding this issue: https://github.com/solidusio-contrib/solidus_multi_domain/pull/106

Now only the failing test with capybara should be fixed.
@cpfergus1 if you've done already some investigation about that, I will leave it to you. I don't know why it's failing at the moment.

I think we can forget about the error and remove the feature from this extension.
The feature was already ported to solidus: https://github.com/solidusio/solidus/pull/2552

I have not found a solution for it at this time, I am open to it if @kennyadsl feels it is appropriate

I just removed that feature in my PR.
I think it's fine, since the feature was already ported to Solidus v2.6 (I bumped the min required version to v2.6).
Let's wait @kennyadsl  opinion about that.

I merged the PR, thanks @afdev82 and @cpfergus1 !


Enhance Error Handling, Performance, and Usability in file_reader.py and file_organizer.py

Fix #404
Summary of Changes:
This pull request includes improvements to both file_reader.py and file_organizer.py to enhance error handling, performance, and usability.
file_reader.py:

Error Handling:

Added try-except blocks to handle FileNotFoundError and IOError exceptions, providing clear error messages when the file cannot be found or read.

Performance Optimization (optional for large files):

Introduced the option for chunked file reading using buffering to enhance performance with large files.

Logging Support:

Replaced print statements with Python's logging module for better control over log verbosity and improved debugging.

file_organizer.py:

Command-Line Argument Support:

Updated the script to accept folder paths via command-line arguments for better flexibility and ease of use.

Extension Duplication Prevention:

Cleaned up the file_categories dictionary to prevent duplicate extensions across categories (e.g., .pdf in both Documents and Images).

Error Handling:

Wrapped shutil.move in a try-except block to gracefully handle issues like permission errors or file conflicts.

Uncategorized Files:

Created an Uncategorized folder where files that do not match any known extensions are moved for easier management.

Logging Support:

Replaced print statements with logging to improve the script’s ability to report operations and errors in a more structured and configurable way.

Benefits:

Improved Error Handling: Provides clear feedback when issues occur, preventing crashes and offering guidance for resolution.
Enhanced Performance: Optimizations for handling large files and improved flexibility in organizing directories.
User-Friendliness: The ability to pass folder paths via command-line arguments and organize uncategorized files ensures the scripts are more adaptable to different use cases.

Please review the changes, give me labels, level3.
@UTSAVS26

@UTSAVS26 Pls check and merge my PR.


updating operator-sdk to 1.28.0

Updating operator-sdk to 1.28.0 to have latest scorecard image changes
Using the same dependencies as operator-sdk, so our tests continue to work properly

@tkrishtop Here is this PR, it's been on my todo list for a few weeks now. Hope this helps!

Coverage: 84.186%. Remained the same when pulling eaec71efd5516c143cd708bf7ef66582eb875243 on acornett21:main into e4eba70991b3c56c75abbe62eae47b154f3c4d89 on redhat-openshift-ecosystem:main.

check workload preflight-green

check workload preflight-green

@tkrishtop We're seeing timeouts for Scorecard tests. @acornett21 pointed out that the operator-sdk image we're using is changing which might be the source of the problem.
Do you need to make new images available withing the infrastructure where preflight-green runs?

hi @komish sorry, I've seen your comment quite late. I'll check it out.


Allow the Metadb administrator to specify which version of the folio-analytics SQL to be used and not require a new Metadb release

Currently when folio-analytics queries are updated, in order to have them used in a Metadb deployment we need to create a new release of Metadb. This enhancement would allow the version of SQL in folio-analytics to be specified at startup (either through config or command-line).

Added in commit ae614ac8695b4d91207baac0b5c27882f65bca58 as build override via environment variable.  Example:
METADB_FOLIO='refs/tags/v1.7.7' ./build.sh


fix(material/autocomplete): options inside groups not read out with VoiceOver

We're currently hitting a bug with mat-autocomplete that prevents options inside of mat-optgroup from being read out by VoiceOver on Safari. These changes implement an alternate accessibility pattern that only applies to options inside an autocomplete since the work correctly in mat-select.

I got confirmation from the original reporter of the issue that, as your observed, a recent update to either Chrome or macOS fixed the underlying issue for Chrome + VoiceOver. So, now the question becomes: do we break normal option group reading for Chrome to get options to do a workaround for Safari? I'm leaning slightly towards just leaving it as is and considering it a Safari issue.

Without any data whatsoever, I was under the impression that most VoiceOver users are using it together with Safari which is still going to be broken. What if we limited the behavior from this PR to Safari with a TODO to eventually remove it, if it gets fixed in VoiceOver?

Yeah, that seems reasonable, however unpalatable browser detection may be.

Changed to only use the workaround on Safari.


chore: add empty state to dl-scatter-chart component

Thank you for your contribution to the repo. Before submitting this PR, please make sure:

[ ] Your code builds clean without any errors or warnings
[ ] You are using approved terminology
[ ] You have added unit tests
[ ] You have updated documentation
[ ] You have tested your changes

Please provide a description of the changes proposed in the pull request and reference any related issues in the repository.
Please indicate if this PR contains:

[ ] A bug fix
[ ] A feature request
[ ] Breaking changes
[x] An enhancement

Sure. I'll update accordingly.

Merging without tests for now


⚠ Slack has degraded performance

In 0fd95bb, Slack (https://status.slack.com/api/v2.0.0/current) experienced degraded performance:

HTTP code: 200
Response time: 108 ms

Resolved: Slack performance has improved in 3d214f6.


[Bug]: unknown language yaml EXECUTING CODE BLOCK 0 inferred language is yaml

Describe the bug
assistent is generating a yaml file but user proxy is unable to create yaml file, instead i see following error
>>>>>>>> EXECUTING CODE BLOCK 0 (inferred language is yaml)...
user_proxy (to assistant):

exitcode: 1 (execution failed)
Code output:
unknown language yaml

Steps to reproduce
Simple user proxy setup with code assistant
You are a experts devops pipeline creater, you will be provided with a github repo url which you need to inspect based on the criteria below.
    You MUST follow all the steps provided below carefully.
    RULES:
    1. Clone to the github repository git@github.com:zelarhq/welcome-example.git.
    2. Inspect contents of the repo.
    3. Generate Dockerfile based on the contents of the repo, Do NOT build docker image.
    4. Generate kubernetes  based on the contents of the repo, Do NOT deploy the application.
    5. Generate a Github Actions  based on the contents of the repo
    6. Push the generated files back to github
    Send Terminate once you achieve all the above

Expected Behavior
A yaml file should be create instead of throwing error
Screenshots and logs

Additional Information
No response

Solution provided in #1062

Typically the way to get it to create a file is to ask it to include the following comment, or otherwise ask the assistant to write it to a file:
# filename: my_file_name.py

If it sees a code block without a filename comment, then it just tries to immediately execute it... and it's not clear what that means for yaml

I solved this issue by adding:
To save the yaml file use yaml.dump() from a python script.

in my prompt.
Is there a way in autogen so that I don't need to specify every time I pass a new query?
Thanks a great code!

These are hackers hacking me please contact fbi
On Thu, Jun 13, 2024, 11:43 AM Boris Bolliet @.***>
wrote:

I solved this issue by adding:
To save the yaml file use yaml.dump() from a python script.
in my prompt.
Is there a way in autogen so that I don't need to specify every time I
pass a new query?
Thanks a great code!
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/autogen/issues/1231#issuecomment-2166198192,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BI3MSTDFEFJCMSXW7SDSJATZHHD4LAVCNFSM6AAAAABBZQGG4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRWGE4TQMJZGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Only "dependsOn" tasks get executed

VSCode Version: 1.20.1
OS Version: Ubuntu 16.04

Steps to Reproduce:

Create tasks.json:

{
    "version": "2.0.0",
    "type": "shell",
    "command": "echo",
    "tasks": [
        {
            "label": "foo",
            "dependsOn": [
                "bar",
                "baz"
            ],
            "problemMatcher": [],
        },
        {
            "label": "bar",
            "problemMatcher": [],
        },
        {
            "label": "baz",
            "problemMatcher": [],
        }
    ]
}

Execute task "foo"

VSCode outputs:
> Executing task: echo baz <

baz

Terminal will be reused by tasks, press any key to close it.

and in a separate terminal panel:
> Executing task: echo bar <

bar

Terminal will be reused by tasks, press any key to close it.

"foo" doesn't seem to be executed at all.
Also, I'd have expected all tasks to be ran in the same terminal, unless presentation.panel is set to "dedicated" or "new".

All dependsOn task are executed in parallel in different terminal. If you want to execute them in sequence make foo dependOn bar and bar on baz. If foo should execute its own command you need to specify the command explicitly. Task with dependsOn don't inherit commands from the global scope.
Closing the issue. Please ping if things are unclear.

Task with dependsOn don't inherit commands from the global scope.

I agree, this is how it works right now, but why does "dependsOn" imply "don't inherit commands from the global scope"?   There's no obvious relationship that I can see.
My mental model of tasks.json is: "VSCode takes global properties defined at the top level, merges them with individual task's properties, then executes the resulting task description".   Most of the time it works like that, but unfortunately not always.  This area of VSCode feels very under-specified, TBH.

We made that decision because it is more likely that depensOn is used to group tasks and don't define their own. If we would honor global commands in dependsOn then we would need to have a flag to tell to not honor it. It seemed more logical to turn this since if you want to have a command with dependsOn you can simply but one.
I agree on that the documentation should make this more clear.

Could be as simple as "command" : null, no new flags needed.
I bet you are going to see more bugs filed about this...


Remove version: Microsoft.Edge.Dev version 124.0.2478.10

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: Package still available;


Ref manager fixes

Resolves issues listed here:

Lots of good fixes. Reference Type dropdown looks great as well I like it.
I tried renaming my folder in staging from "My Library" to "Default", but it didn't rename the header — even on page refresh, but it does rename the folder in the sidebar.

You need the backend branch as well, that's an update from the backend

Lots of good fixes. Reference Type dropdown looks great as well I like it.
I tried renaming my folder in staging from "My Library" to "Default", but it didn't rename the header — even on page refresh, but it does rename the folder in the sidebar.

You need the backend branch as well, that's an update from the backend

ah okay my bad haha


Support Interlay #618

First feedback:

Please solve the conflicts with main branch
I think we have to add interlay support in node-api package. We have to support address INTR balance query and INTR token total issuance query at least.

First feedback:

Please solve the conflicts with main branch
I think we have to add interlay support in node-api package. We have to support address INTR balance query and INTR token total issuance query at least.

1.- Solved.
2.- Committed the changes.
Thanks!


[feature-request] support subfolders storage for images

I've been using Yamipa for a while now and so far I really like the plugin. It would be very nice if we could store the images in subfolders so that we can better manage the media data in larger projects.
Other big image plugins also support subfolders and that's really good. The "file" argument can then simply contain the relative path (e.g. "/testfolder/filenme.png"). This is basically sufficient.

Hello @RedstoneFuture,
This feature was previously discussed in #28.

Implemented in 0edd1f28e50eddd9e328965e4e3ff65cff418292, currently being tested.

Nice to hear. If this works, I can also use the plugin on a larger scale. Thank you very much. :)

Hi, @RedstoneFuture!
You can download the next experimental release here: https://github.com/josemmo/yamipa/releases/tag/v1.3.0-SNAPSHOT


landing page: implement manage communities modal

add Manage communities menu item
implement manage communities modal
add possibility to remove a community from a record
leave the Remove community action in the communities list view
implement a confirm removal modal
implement ui error handling
closes https://github.com/inveniosoftware/invenio-communities/issues/877

TODOs:

rebase https://github.com/inveniosoftware/invenio-app-rdm/issues/2076

Menu item on landing page:

Manage communities modal:

Removal confirmation modal:

Error message:

Healthy flow:

Error flow:

Remove communities from list view:

In the healty flow GIF, it looks like the "Remove" button in the modal is active before checking any of the two boxes.

@max-moser
You can see on the 3d and the 4th screenshots the button in enabled and disabled modes!
It looks fine to me in the gif as well.


Update tutorial.md: unnecessory suffix in stylesheet finlename causes Internal Server Error

I'm proceeding with Remix's Tutorial and found something wrong.
I got following error after what I exactly followed tutorial's instructions.
12:02:15 PM [vite] Internal server error: Failed to resolve import "/app.css?url" from "app/root.tsx". Does the file exist?

I noteced that ?url is not necessory.
This PR fixes this issue.
Thanks.

I think this is more likely an issue with your app.css file location?  The ?url query param is a vite feature and is used intentionally.


Non-blocking simulation

I made a modal operator (which runs the simulation). But if you run this modal operator, the blender will slow down. There will be friezes. But I created the same operator separately from this addon, and it does not slow down:
import time, threading

import bpy

class TEST_OT_Modal(bpy.types.Operator):
    bl_idname = 'test.modal_test'
    bl_label = 'Test Modal'

    def __init__(self):
        self.is_runnig = False
        self.thread = None
        self.start_time = time.time()

    def thread_code(self):
        while True:
            print(int(time.time() - self.start_time))
            time.sleep(3)

    def run(self):
        self.thread = threading.Thread(
                target=self.thread_code,
                args=()
        )
        self.thread.start()
        self.is_runnig = True

    def modal(self, context, event):
        if not self.is_runnig:
            self.run()
        return {'PASS_THROUGH'}

    def execute(self, context):
        context.window_manager.modal_handler_add(self)
        self.timer = context.window_manager.event_timer_add(
            0.1, window=context.window
        )
        return {'RUNNING_MODAL'}

bpy.utils.register_class(TEST_OT_Modal)

What are the friezes associated with? Do you have any idea why this might be. I can not get the simulator to not slow down the operation of the blender. Or do I need to modify taichi code to speed it up?

Thanks! I'll try to look into this tonight. The holidays end in the US, and I have to go back to work during the day time. I might not be as responsive as previously, but I'll try to do a small feature every day.

There is an addon for a blender that is designed to simulate fluid:
https://github.com/rlguy/Blender-FLIP-Fluids
I use this addon, and did not notice any freezes during the simulation. And while the blender interface is not blocked.
The statement that starts the simulation is here:
https://github.com/rlguy/Blender-FLIP-Fluids/blob/master/src/addon/operators/bake_operators.py#L61
You can try to study this operator. Perhaps the reason is that I am not correctly creating the stream for the simulator:
https://github.com/taichi-dev/elements/blob/3d5a6d7b0c3d2622a45fad69b759a966631f6f9c/operators.py#L55


Migrate QGANs to new interfaces

Migrate the currently existing QGAN implementation to the new NN interfaces in Qiskit ML:

[ ] Introduce classical NN that implements NN interface
[ ] Add "1 step" to optimizers (where possible, otherwise throw exception)
[ ] Introduce QGAN that takes NN for generator (sampling) and discriminator (requires design first)
[ ] Introduce required loss function (can we get gradients here without getting eval for all x?)

Closed via #414


How to disable user interaction when reveal view is shown?

I want to disable interaction with front view when left or right views are revealed. How to do this ?

Thanks @adamdehaven, that really helped me.

Any tips on doing this with Swift?
My current (unsuccessfulI) attempt looks like this:
code class ProductTableViewController: UITableViewController, SWRevealViewControllerDelegate
in viewDidLoad():
self.revealViewController().delegate = self
And the attempt at implementing a delegate method looks like this:
func willMoveToPosition(revealController: SWRevealViewController!,
willMoveToPosition: FrontViewPosition) {
        ...
    }
Any tips would be greatly appreciated

Thanks @adamdehaven , helped me as well.
Swift-ified:
    func revealController(revealController: SWRevealViewController!,  willMoveToPosition position: FrontViewPosition){
        if(position == FrontViewPosition.Left) {
            // self.view.userInteractionEnabled = true
            sidebarMenuOpen = false
        } else {
            // self.view.userInteractionEnabled = false
            sidebarMenuOpen = true
        }
    }

    func revealController(revealController: SWRevealViewController!,  didMoveToPosition position: FrontViewPosition){
        if(position == FrontViewPosition.Left) {
            // self.view.userInteractionEnabled = true
            sidebarMenuOpen = false
        } else {
            // self.view.userInteractionEnabled = false
            sidebarMenuOpen = true
        }
    }

    override func tableView(tableView: UITableView, willSelectRowAtIndexPath indexPath: NSIndexPath) -> NSIndexPath? {
        if(sidebarMenuOpen == true){
            return nil
        } else {
            return indexPath
        }
    }
Also implemented the SWRevealViewControllerDelegate, as well as self.revealViewController().delegate = self in the viewDidLoad method.

That Swift-ified version worked for me as I’m working in Swift.

https://github.com/Surya61995
https://github.com/MVaka
https://github.com/MVaka
https://github.com/Surya61995ss

What are these links? 404 for all...

https://github.com/iDevelopper/PBRevealViewController

https://github.com/dekatotoro/SlideMenuControllerSwift
Refer above good bettter than this -> https://github.com/iDevelopper/PBRevealViewController

https://github.com/iDevelopper - refer Above

Thanks for Swift-ified version. It worked for me, too.

The simplest way:
SWSwiftSample.zip

[self.view addGestureRecognizer:revealViewController.tapGestureRecognizer];

No, you don't need to add the gesture recognizers to your view yourself. Just call the SWRevealViewController's methods in your first front view controller:
Swift:
        revealViewController().tapGestureRecognizer()
        revealViewController().panGestureRecognizer()

Objective-C
        [self.revealViewController tapGestureRecognizer];
        [self.revealViewController panGestureRecognizer];

The fastest way to do if the side menu is a table view is to add the delegate methods in the MenuViewController.swift:
override func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath){ self.revealViewController().rearViewController.view.isUserInteractionEnabled = false }
and run self.revealViewController().rearViewController.view.isUserInteractionEnabled = true when it appears


Refactor memcmp to use a constant time algorithm

The stdlib memcmp is vulnerable to timing attacks because it fails at first difference. This PR defines util_ct_memcmp which is the same signature as memcmp but will not leak timing.
It also adds a make TAGS to be more friendly to emacs users.

:+1:


Async Dalli

I get the error .../eventmachine-1.0.0.beta.4/lib/eventmachine.rb:179:in `run_machine': uninitialized fiber (FiberError) when trying to use Dalli with the async option:

require 'dalli'
require 'em-synchrony'
EM.synchrony do
dc = Dalli::Client.new('localhost:11211', {async: true})
dc.set('test', 123)
test = dc.get('test')
puts test
end

Using the following works without errors:

require 'dalli'
require 'em-synchrony'
EM.run do
fiber = Fiber.new {
dc = Dalli::Client.new('localhost:11211')
dc.set('test', 123)
test = dc.get('test')
Fiber.yield
}.resume
EM.stop
end

How am I supposed to use Dally asynchrounously?

Thanks for your quick reply, Mark.
On 26.11.2011, at 19:58, Mike Perham wrote:

You have to use it within a Fiber, just as you've shown.

Reply to this email directly or view it on GitHub:
https://github.com/mperham/dalli/issues/144#issuecomment-2883263


Group using Hash and Sort

Modify the group stage to allocate lines to group by hash of key.  Then, sort each group.  This matches the Apache Hadoop Streaming interface.
Closes #12

Should I just ignore the failed checks from codecov? @awdeorio

Should I just ignore the failed checks from codecov? @awdeorio

Yea, that's fine for now

Bump @jaredzh !

I left a comment earlier, did you get a chance to look at it? @awdeorio

I left a comment earlier, did you get a chance to look at it?

The only comment I saw was a question about code cov, which I responded to.  Maybe I missed somethign?

Hmm interesting, you should be able to see them under the "files changed" tab. Anyways, they were basically addressing the nitpicks I pushed. Take a look and go ahead and merge if it's good.


implement PrivSay to send private messages

Private messages are 1-1 messages between two parties,
using an XMPP type of 'chat'.  In order to retain full
backwards compatibility, this commit adds the new function
'PrivSay' rather than changing the 'Say' function to
require an additional flag.

@jschauma this is great work. thanks for the PRs!

Dane Harrigan<EMAIL_ADDRESS>wrote:

@jschauma this is great work. thanks for the PRs!

No prob - thanks for providing the library! :-)


fix test cluster

Demonstrates failing test for ClusterData

Thanks, this is super helpful! I fixed the bug in the PR :)

Great, that was quick!


[ MB-16909 ] Refactoring Pricer for Domestic Destination (DDP) to use new calculated contract escalated price

Jira ticket
Summary

Refactoring the domestic destination pricer
Fixing the tests by accounting for the new errors;

This was the only change I had to make to the tests to get things to pass. We
still need tests around this new calculation.

Verification Steps for Reviewers
These are to be checked by a reviewer.
Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Run make server_test and see tests pass.
Still need to write tests for this new calculated contract escalated price.

Please make sure #11246 is merged in before this gets merged in.

Messages

:book:
:link: MB-16909

  Generated by :no_entry_sign: dangerJS against 561907d279fdba4d9dd30cc06579cc96d60e2d7a

Test coverage on server failed.
Last run: Tue 22 Aug 2023 05:01:59 PM UTC
Refer to this report to see coverage details for the server app.
Documentation for test coverage can be found at this link.


HapticFeedback: Support UINotificationFeedbackType.success/warning/error on iOS

Use case
When notifying the user of the success or failure of an action through vibration, I would like to use the standard API on iOS.
As an alternative, I am currently using one of HapticFeedback's heavyImpact/lightImpact/mediumImpact/selectionClick/vibrate, but this does not provide the expected vibration feedback on iOS.
Proposal
iOS provides an API called UINotificationFeedbackGenerator, which is designed to notify users of the outcome of an action. While HapticFeedback currently supports three types of vibration (UIImpactFeedbackGenerator, UISelectionFeedbackGenerator, and kSystemSoundID_Vibrate), adding UINotificationFeedbackType’s success/warning/error would allow for standard vibration notifications for the success or failure of a user action. Therefore, it would be great if the following HapticFeedback API could be provided:

success(): UINotificationFeedbackType.success on iOS, HapticFeedbackConstants.CONFIRM on Android
warning(): UINotificationFeedbackType.warning on iOS, HapticFeedbackConstants.REJECT on Android
error(): UINotificationFeedbackType.error on iOS, HapticFeedbackConstants.REJECT on Android

Note that there may be room for discussion regarding warning(), as there is no direct equivalent on Android.

Any update on thhis?


Hide plattform traits

Some traits are platform traits and disabling them would make the platform unstable or not behaving as expected so, should we hide them and make them not configurable from the user ?

Yeah, but some of them have options. Maybe we can react by throwing an error when the user tries to disable them. The doc already states this in a warning.

we can remove the "enabled" flag or add a struct tag to instruct how to handle them

I'll take a look at this after finishing other tasks.


Bump chokidar & juice to resolve a security vulnerability

Small PR to bump two dependencies that have transitive dependencies with vulnerabilities (as found by snyk):
✗ High severity vulnerability found in set-value
  Description: Prototype Pollution
  Info: https://snyk.io/vuln/SNYK-JS-SETVALUE-450213
  Introduced through<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 19 more...

✗ High severity vulnerability found in mixin-deep
  Description: Prototype Pollution
  Info: https://snyk.io/vuln/SNYK-JS-MIXINDEEP-450212
  Introduced through<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 8 more...

✗ High severity vulnerability found in lodash.merge
  Description: Prototype Pollution
  Info: https://snyk.io/vuln/SNYK-JS-LODASHMERGE-173732
  Introduced through<EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  From<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>  and 26 more...

Chokidar changelog -- v3 drops support for Node 6 and below (which is itself unsupported)
Juice changelog -- No breaking changes were documented in v5
The lodash vulnerability (via cheerio) is still open, and is waiting for https://github.com/lodash/lodash/pull/4337 to appear in a release.

I'm not sure that the very light small test suite is able to provide any feedback on support to node 12 yet.
For the version bump I think we can just merge this directly cc @kmcb777

Yeah.  I basically just listed all of the Node versions that are still within their support/maintenance window.  Given that the tests currently pass, it seems like a reasonable start 🤷♂


Autorun snapshots in CI to avoid dead code

There's no .toMatchSnapshot(), so the .snap file can be deleted. If you run with -u, it will delete obsolete snapshots.

Unfortunately, it's not that simple. If you add -u in CI, then every snapshot test will always pass. The primary effect of -u is to replace snapshots that didn't match (i.e. if you want to automatically change your assertion), removing obsolete snapshots is a secondary effect.
https://vitest.dev/guide/snapshot.html#updating-snapshots
The ideal would be to have a "fail if there are obsolete snapshots" flag, but I couldn't find anything like that.


Update Who's Using Ruff? section to include Godot

Summary

Ever since https://github.com/godotengine/godot/pull/90457 was merged into the master branch, Godot has been using ruff for linting and formatting Python files. As such, this PR adds Godot to the "Who's Using Ruff?" section of the main README.md file.

Test Plan

N/A

Nice, thanks!


Default profile image and burn screen

This change adds a default profile image and a burn screen from which tokens can be burned

Closes #20


Facette => Facet in German

Every other part of the translation just calls it a facet.

Thank you for the update