remove diacritics on filter

I really need this feature, can you guys help me?

See inline comment on _.deburr.  We just need a test case for this now.  See Dropdown-test.js.

for example when i have this options:
when i search after: floresti
i will get no response as i type
FLOREŞTI
ŞANŢU FLOREŞTI

Yep, I'm noting we should use lodash's _.deburr method rather than writing our own filter:

ty for your quick response, i will try to add a test, first time I am doing a pull request so please have patience :)

Codecov Report

Merging #2021 into master will decrease coverage by 0.19%.
The diff coverage is 80%.

@@            Coverage Diff            @@
##           master    #2021     +/-   ##
=========================================
- Coverage   99.76%   99.57%   -0.2%
=========================================
  Files         148      148
  Lines        2556     2560      +4
=========================================
- Hits         2550     2549      -1
- Misses          6       11      +5

Impacted Files
Coverage Δ

src/modules/Dropdown/Dropdown.js
98.73% <80%> (-1.27%)
:arrow_down:

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 e1ff28a...3f1284b. Read the comment docs.

Awesome, congrats on your first PR :)  I left a couple more comments, then I think we're ready to go here.

Be sure to run npm run lint:fix as well.  This will run lint checks and also fix some issues for you.  You can ignore the warnings, but the errors will need fixed.  This one was failing CI:
/home/ubuntu/Semantic-UI-React/src/modules/Dropdown/Dropdown.js
  799:97  error  Infix operators must be spaced  space-infix-ops

hey i've made the changes, i hope they are good

Thanks! Nice work, brag away my friend :)

Released in<EMAIL_ADDRESS>


Did you ever try the resnet50, resnet101 and resnet 152 in your work?

Hi @deepmeng
I didn't try. But you can simply change the architecture via training argument.


Check if get_editor request is non-scratch before early-returning

This fixes a bug where Ctrl+N to create a new scratch file would replace the current open editortab, uncaring of whether there was edits or not.

Codecov Report

Merging #1422 (73d9129) into master (3ce1306) will increase coverage by 0.04%.
The diff coverage is 0.00%.

 Learn more


Edit notes from DCAN weekly code review

Overall notes:
•	make it so the table of contents on the left lists subsections (similar to the table of contents shown on the right side of the page)
•	perhaps switch order of Inputs and Pipelines section
•	use A, B, C, etc instead of numbers for subsection labels. or 1.1, 1.2 etc
•	perhaps explain the overall purpose of this documentation and how it can be used
Table of Contents:
•	ABCC Documentation Summary: should cite ABCC paper and DAIC here instead of just having the useful links section
•	How to Contribute:
•	should we remove Amanda's email and just ask people to post GitHub issues? or maybe use the DCAN lab email?
•	move this section to the end
•	Documentation Guide - remove this section and change settings so that it opens new tab when you click on links. remove this section from all of the subsections
•	Table of Contents:
•	move this section to under ABCC Doc Summary
•	rename as "Overview"

Release Notes:
•	Possibly move both 1.1 ABCC Collection and 1.2 Background to Table of Contents section since it doesn't seem to be directly related to releases. And then the first section will be "Ongoing Releases"
•	move this Release Notes section to further down, perhaps between Derivatives and Useful Links somewhere
•	1.2 Background: need to state explicitly that this data is being housed on NDA

Inputs
General comments about this section:
•	a lot of the info could go into a section named "Metadata" (such as 5. MRI Acquisition Parameters)
•	add information about sidecar jsons and other information required to run pipeline? Or at least include link to pipeline RTD that describes how to run pipeline
•	it should be more clear that this section is describing how the data was processed, not instructions on how you would process the data yourself

2.1. About this Document:
•	move description about pipeline processing to the "Pipeline" section - doesn't seem to be relevant to information here. can keep last 2 sentences
•	add both task and rest fMRI data
•	state clearly that ABCC includes BIDS-formatted raw data (NIFTIS) and processed data and this section describes what raw data was used and how it was processed (as opposed to describing how one would process it themselves - many people in group are getting confused on this point)
2.2. Input Data Subsets Breakdown:
•	possibly use  or * instead of #
•	delete 1st sentence "Section 3 .." because this is confusing - unclear which Section 3 it is referring to
•	describe what is meant by "input data subsets" since this has a specific meaning according to NDA
•	inputs.anat. - should the file name include "_rec_normalized" in "sub-#/ses-#/anat/sub-#_ses-#(_rec-normalized)(run-#)(T1w|T2w).json"
•	possibly make separate section for data structure
2.3 DAIC Quality Control
•	consider moving this information to beginning of RTDs
•	move ABCD repo info to 2.4 DICOM to BIDS conversion section
•	go to NDA open workshops to gain more information to add to this section
2.6 Scanner Differences
•	2nd paragraph: should specify that ANTS was used for all anatomical data preprocessing
•	any description of pipeline should be in pipeline description, confusing to include that information here
•	the info currently in this section only discusses ANTs - we should either flesh out this section with more scanner differences, change the name, or make it more complete. it also reads as somewhat anecdotal
•	the info in this section could also be moved to 2.5 MRI acquisition parameters
2.7 Field Map Selection Process
•	1st sentence: replace with link to BIDS definition of pair of pepolar fieldmaps
•	combine 2.7 with section 2.8 (BIDS Field Map "IntendedFor" Metadata)
•	specify that pair of fmaps were selected for all scans, currently language is a bit unclear
2.9 Diffusion-weighted Imaging (DWI)
•	should allude to fact that we are currently starting to process the DWI data and so processed dwi data will be included in future release
•	middle paragraph: should say these bval and bvec files were provided to us by the DAIC due to formatting irregularities that come with the files in DICOMs
2.10 BIDS Modality-agnostic files
•	replace "small blurb" with more formal language
•	typo in word "dataset"
3. Pipeline
3.1 About this Doc
•	remove "1" from other pipeline sentence, confusing
3.2 Pipeline Overview
•	link goes to ABCD-STUDY repo - should also link to whichever version of pipeline used to do processing
•	update link to DockerHub to our new UMN DockerHub
•	add section about which version of the pipeline was used for processing (looks like it's 1.2.0 from what it says in 1.1 Release Notes) or just link back to Release Notes section
•	Zenodo: explicitly state version, or include link to all versions
•	Bigger picture: need to figure out which data subsets were processed with which version and make that explicit including specific release links, especially for future releases
3.3 Pipeline Stages
•	part 3 motion censoring: temporal mask range is actually 0 to 1.0 mm now
•	could be more explicit that stages 8-10 (custom clean, filemapper, and connectivity matrix generation) are not technically a part of the ABCD-HCP pipeline
•	stage 10: add link to cifti-conn-wrapper repo

Derivatives
4.1 About this Document
•	fMRIPrep and QSIPrep should be added elsewhere and not mentioned here- just add to useful links section?
•	specify that these are the derivatives that are available on the NDA, not the full pipeline outputs
4.2/4.3 Anatomical/Functional
•	perhaps present this information in a table format
•	figure out different want to insert blanks (currently using _ _ _ _) - perhaps use pipe notation instead, and add note at bottom that clarifies how to interpret this
•	specify that all the parcellated time series are concatenated
•	"Prerequisites for each fMRI type to have 8 derivative data subset:" reword to make it more clear and move to Inputs section
4.4 Derivative Data Subsets Breakdown
•	change "Section 3 and onward" to "This section" - in general, perhaps remove this language so that it sounds less like a paper
•	put this section into a table format
•	consider just linking to FreeSurfer documentation for some of this information (https://surfer.nmr.mgh.harvard.edu/fswiki/FsTutorial/AnatomicalROI#IndividualStatsfiles)
•	parcellations: can just list parcellations used, don't need to have so much redundancy - could also put this info into a table as well (data subset name, derivatives, file path) with description above or below
•	Motion Framewise displacements: change FD threshold range to 0-1.0 mm
4.5 Executive Summary
•	add link to executive summary documentation
4.8 Caveats
•	perhaps add this information to release notes or some place that's updated more regularly
•	double check that executive summaries are still not available yet for anat-only subjects and update text as needed
•	clarify what the last point on exec summaries is referring to ("labeled as fMRI scan_type in records")

5 Recommendations
General note: add more context for what each specific recommendation actually is. the information throughout this section is frequently presented without context
5.1 About this Document
•	explain more about what these recommendations are for, generally need more context
5.2 The BIDS Participant Files and Matched Groups
•	add more context for why we are showing table
•	explain that we recommend that when using data for analyses, you should split the subjects following this table that we've provided so that the demographics are similar between groups
5.3 BIDS Quality Control File
•	add context for specific recommendation - that one should consider using these QC metrics to determine which data to include in their analyses
5.4 Downloading and Unpacking Data
•	put this section before "BIDS participant files and matched groups" section
5.7 DCAN Labs Software
•	move this section from recommendations entirely and merge with customclean and filemapper sections under Pipeline section
•	also, for custom clean, should remove info about GUI since we don't use that anymore
5.8 BIDS Folder Layout
•	move this section to Derivatives section, perhaps at the top?
•	and remember to update links within the section as needed

@LuciMoore I addressed all of the above issues (to be released by Barry next week) except for the following:
2.2. Input Data Subsets Breakdown:
• possibly make separate section for data structure
2.7 Field Map Selection Process
• 1st sentence: replace with link to BIDS definition of pair of pepolar fieldmaps
3.3 Pipeline Stages
• stage 10: add link to cifti-conn-wrapper repo --> not planning on adressin this since we will be only using BICEPS moving forward
Would be good to address this in a further ABCC review when the new version is pushed.

Thank you Amanda! I hope your new position is off to a great start!
On Wed, Jun 29, 2022 at 12:20 PM Amanda Rueter @.***>
wrote:

@LuciMoore https://github.com/LuciMoore I addressed all of the above
issues (to be released by Barry next week) except for the following:
2.2. Input Data Subsets Breakdown:
• possibly make separate section for data structure
2.7 Field Map Selection Process
• 1st sentence: replace with link to BIDS definition of pair of pepolar
fieldmaps
3.3 Pipeline Stages
• stage 10: add link to cifti-conn-wrapper repo --> not planning on
adressin this since we will be only using BICEPS moving forward
Would be good to address this in a further ABCC review when the new
version is pushed.
—
Reply to this email directly, view it on GitHub
https://github.com/ABCD-STUDY/nda-abcd-collection-3165/issues/29#issuecomment-1170395343,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBYTQY67NBD4DH5WSDL5TTVRSOZRANCNFSM5SDILLIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Lucille A. Moore, PhD
Project Manager & Technical Specialist
Developmental Cognition and Neuroimaging Lab
Masonic Institute for the Developing Brain, University of Minnesota

complete


Query: Is there any plan to support Grove BME680 Bosch Sensor

We plan to use BME680 on GrovePi and would like to know if there is any plan to add this sensor support? I see https://github.com/Seeed-Studio/Seeed_BME680_V1/ available, with Arduino IDE

Hi @BinduRao2018, we are not currently working on adding new Bosch/Grove sensors to the UPM library and are instead focused on consolidating the APIs based on sensor categories for the next major update. If you are actively using this sensor and would like to try and find help for porting the library you linked to MRAA supported boards please let us know.

Hi @Propanu,
I managed to integrate bme680, using https://github.com/BoschSensortec/BME680_driver as a reference. The functionality provided from my work uses mraa APIs and not UPM.  This was verified on UP2 Grove IoT Development Kit and Raspberry Pi.  W.r.t outputs from the sensors for Temp, Humidity and Pressure, I would say it was fairly reasonable and not very accurate. This is due to the calibration values (I have used the same reference values as available in the above mentioned repo) as the details are not available.
PS: I haven't integrated the changes with BSEC library that is suppose to provide more accurate measurement values, however the library is not available on all platforms for download.


[server] Fix storage node read quota enforcement

[server] Fix storage node read quota enforcement
The PR fixed several issues in the ReadQuotaEnforcementHandler.java:

The ReadQuotaEnforcementHandler used to only keep the token bucket of the current version. As a result when FC metadata is updated asynchronously it's possible that it will query the server for a different "current" version. During this transition period we don't have the corresponding token bucket and quota is not enforced.

In the old channelRead0 there is a bug when handling retry requests. Retry request will not enter the if block but enter the else if unintentionally and trigger handleEnforcingAndNoBucket on the request.

updateQuota used to blindly replace existing token bucket with a new one even if they are identical. Now it checks if it's different and only replace it if it's different to avoid unnecessary initialization of new token buckets.

Removed the old usage ratio metric since it's not very useful due to the bucket's large headroom for spike handling and we can get a more useful ratio by looking at the QPS and bucket stats. Instead, added quota_rcu_allowed_unintentionally metric to track requests allowed due to missing token bucket.

Initialize ServerQuotaTokenBucketStats for the server node's token bucket to gain visibility on the storage level quota enforcement.

How was this PR tested?
Existing and new tests
Does this PR introduce any user-facing changes?

[ ] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

Removed the old usage ratio metric since it's not very useful due to the bucket's large headroom for spike handling and we can get a more useful ratio by looking at the QPS and bucket stats. Instead, added quota_rcu_allowed_unintentionally metric to track requests allowed due to missing token bucket.

So new metrics will cover the qps beyond quota limit?
I feel the usage ratio is still useful even the current quota mechanism can tolerate spike since this behavior is not deterministic since it is a best effort.
If the existing stores use up the per-server quota, these excessive requests will be rejected.

Removed the old usage ratio metric since it's not very useful due to the bucket's large headroom for spike handling and we can get a more useful ratio by looking at the QPS and bucket stats. Instead, added quota_rcu_allowed_unintentionally metric to track requests allowed due to missing token bucket.

So new metrics will cover the qps beyond quota limit?
I feel the usage ratio is still useful even the current quota mechanism can tolerate spike since this behavior is not deterministic since it is a best effort. If the existing stores use up the per-server quota, these excessive requests will be rejected.

But we can also arrive at a ratio by looking at the corresponding token bucket stats and qps. Do we really need a ratio that's usually low during steady state but can quickly go to 1 or even exceed 1 during spike scenarios? To me it's only worth it if we plan to put some alerting on it, maybe if we return a simpler ratio. qps / Refill per second allocated to this node, what do you think?

But we can also arrive at a ratio by looking at the corresponding token bucket stats and qps. Do we really need a ratio that's usually low during steady state but can quickly go to 1 or even exceed 1 during spike scenarios? To me it's only worth it if we plan to put some alerting on it, maybe if we return a simpler ratio. qps / Refill per second allocated to this node, what do you think?

Sorry for the late reply.
So what will be the new alerting strategy?
Will we still come up with a ratio metric based on the qps and token bucket stats and setup alert against it as today?

But we can also arrive at a ratio by looking at the corresponding token bucket stats and qps. Do we really need a ratio that's usually low during steady state but can quickly go to 1 or even exceed 1 during spike scenarios? To me it's only worth it if we plan to put some alerting on it, maybe if we return a simpler ratio. qps / Refill per second allocated to this node, what do you think?

Sorry for the late reply. So what will be the new alerting strategy? Will we still come up with a ratio metric based on the qps and token bucket stats and setup alert against it as today?

Yes, unless we prefer to have an explicit metric instead of a derived one. I can also emit one directly from the bucket stats. Taking the ratio of token requested/refill amount over the refill interval.

But we can also arrive at a ratio by looking at the corresponding token bucket stats and qps. Do we really need a ratio that's usually low during steady state but can quickly go to 1 or even exceed 1 during spike scenarios? To me it's only worth it if we plan to put some alerting on it, maybe if we return a simpler ratio. qps / Refill per second allocated to this node, what do you think?

Sorry for the late reply. So what will be the new alerting strategy? Will we still come up with a ratio metric based on the qps and token bucket stats and setup alert against it as today?

Yes, unless we prefer to have an explicit metric instead of a derived one. I can also emit one directly from the bucket stats. Taking the ratio of token requested/refill amount over the refill interval.

If we can use the derived metric to achieve the same result of direct metric, that would be fine.


27 add nj

Link to pivotal/JIRA issue
https://github.com/newjersey/affordability-pm/issues/27
Is PM acceptance required? (delete one)
???
What was done?

Add New Jersey, following the North Carolina issue linked in issue 27
Base is linux-development branch. PR should be rebased on main, with all of those commits dropped, once that branch is merged

How to test?

Run rspec tests

Screenshots (for visual changes)

@aloverso ty for the review! I replied to one comment about some of the files with comments that I can go ahead and remove. One clarification: by "huge schema files" do you mean the intake model and the intake factory? Those comments are generated intentionally and automatically by a gem when you run migrations

@mmazanec22 yes for the big blocks of comments, I was referencing spec/factories/state_file_nj_intakes.rb and app/models/state_file_nj_intake.rb. Didn't realize those comments are auto generated! Gotcha


SpeechSynthesis.StopSpeakAsync has bug

Describe the bug
When you call this method in middle of a speech, future object won't return when you can call .get() on the future object.
To Reproduce
Steps to reproduce the behavior:

start speaking using SpeakSsmlAsync method on android
In Middle of speech , call .StopSpeakAsync() to get a future object.
call .get() on the future object.
.get() never return.

Android 10

@incomingflyingbrick Thanks for reporting, we are investigating this issue.

@incomingflyingbrick Thanks for reporting, we are investigating this issue.

Hi @incomingflyingbrick The bug is fixed and will be released with 1.15.0

Hi @incomingflyingbrick The bug is fixed and will be released with 1.15.0


work on #136 Add LPT to GraphQL

@ericxtang I am done with #136 please review PR, and let me know suggestion/changes if required.

Oh and @mkpdev please update your initial comment on this thread to reflect to format specified in https://raw.githubusercontent.com/livepeer/livepeerjs/master/PULL_REQUEST_TEMPLATE.md

okay @jozanza will do mentioned changes. Thanks!

@mkpdev Thanks for your contribution.


[shell plus] IPython autoreload

Hello, first of all thanks for this amazing package, that in a way or another is always installed in my projects :)
I've a little pain point with shell_plus, which I like to use with IPython.
An amazing feature in IPython is the autoreload extension, which reloads the modules when edited on disk (vaguely resembling to the automatic restart of runserver).
I managed to activate it using this configuration:
IPYTHON_ARGUMENTS = [
    "-c=%load_ext autoreload\n%autoreload 2",
    "-i",
]

Which is a little awkward, and moreover Django itself don't like this way of doing things:
.../lib/python3.9/site-packages/django/db/models/base.py:321: RuntimeWarning: Model 'app.model_name' was already registered. Reloading models is not advised as it can lead to inconsistencies, most notably with related models.
  new_class._meta.apps.register_model(new_class._meta.app_label, new_class)

So, I've some questions:

Is there a better way to achieve my autoreloady goals?
I'd like to contribute to the project, what about adding an option to activate the autoreload extension and suppressing (or maybe not) this warning?

Thanks!

+1


The style on this component requires your app theme to be Theme.MaterialComponents (or a descendant)

Adding the CardForm in expo app  gives   :
Binary XML line #9: Error inflating class com.google.android.material.card.MaterialCardView
The style on this component requires your app theme to be Theme.MaterialComponents (or a descendant)

Smartphone (please complete the following information):

Device: Android emulator ( Pixel 4XL API 28 )

OS: Windows 10
"@stripe/stripe-react-native": "0.23.3",
"expo": "^48.0.0",
"react": "18.2.0",
"react-native": "0.71.6",

When I use CardField everything is fine.

hi! this is in our requirements for cardform: https://github.com/stripe/stripe-react-native#requirements

@charliecruzan-stripe looks like you mention requirements for CLI project, how can we fix it on expo?

@jonqwerty I am facing the same issue, can you share the solution with me as well? CardField is working fine but it is not what I want for my design.
"@stripe/stripe-react-native": "0.28.0"
"react-native-svg": "13.9.0"
"react-native": "0.72.6"
"react": "18.2.0"
"expo": "~49.0.15"


 I have tried alternative packages but they seems to have even more bugs

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

Hi @BayanAlramlawi
Can you please provide your flutter doctor -v a minimal complete reproducible code sample?
Thank you

Microsoft Windows [Version 10.0.19041.685]
(c) 2020 Microsoft Corporation. All rights reserved.
D:\Flutter\my_shop>flutter doctor -v
[√] Flutter (Channel beta, 1.24.0-10.2.pre, on Microsoft Windows [Version 10.0.19041.685], locale en-US)
• Flutter version 1.24.0-10.2.pre at C:\src\flutter
• Framework revision 022b333a08 (4 weeks ago), 2020-11-18 11:35:09 -0800
• Engine revision 07c1eed46b
• Dart version 2.12.0 (build 2.12.0-29.10.beta)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at C:\Users\bayan\AppData\Local\Android\sdk
• Platform android-30, build-tools 30.0.2
• Java binary at: C:\Program Files\Android\Android Studio1\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 4.1.0)
• Android Studio at C:\Program Files\Android\Android Studio1
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] IntelliJ IDEA Community Edition (version 2020.2)
• IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2.3
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin version 202.8070
[√] VS Code, 64-bit edition (version 1.51.1)
• VS Code at C:\Program Files\Microsoft VS Code
• Flutter extension version 3.16.0
[√] Connected device (3 available)
• Web Server (web) • web-server • web-javascript • Flutter Tools
• Chrome (web)     • chrome     • web-javascript • Google Chrome 87.0.4280.88
• Edge (web)       • edge       • web-javascript • Microsoft Edge 87.0.664.60
• No issues found!

`1eed46b
• Dart version 2.12.0 (build 2.12.0-29.10.beta)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at C:\Users\bayan\AppData\Local\Android\sdk
• Platform android-30, build-tools 30.0.2
• Java binary at: C:\Program Files\Android\Android Studio1\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 4.1.0)
• Android Studio at C:\Program Files\Android\Android Studio1
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] IntelliJ IDEA Community Edition (version 2020.2)
• IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2.3
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin version 202.8070
[√] VS Code, 64-bit edition (version 1.51.1)
• VS Code at C:\Program Files\Microsoft VS Code
• Flutter extension version 3.16.0
[√] Connected device (3 available)
• Web Server (web) • web-server • web-javascript • Flutter Tools
• Chrome (web)     • chrome     • web-javascript • Google Chrome 87.0.4280.88
• Edge (web)       • edge       • web-javascript • Microsoft Edge 87.0.664.60
• No issues found!
`

Hi @BayanAlramlawi
Please provide what was asked in https://github.com/flutter/flutter/issues/72322#issuecomment-745206138. The output you provided is not complete.

@pedromassangocode
Hi,
thank you for your help.
apparently I was using beta channel and this was the cause of my issues (so many issues in fact), so as soon as I changed back to stable channel everything works perfectly normal.
again, thank you for your help


New version: FreeTime.FormatFactory version <IP_ADDRESS>

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

Yeah no just tested, this is not unattended
The current version https://github.com/microsoft/winget-pkgs/blob/master/manifests/f/FreeTime/FormatFactory/5.4.5/FreeTime.FormatFactory.yaml also failed, so this package should be removed


Extend documentation some more

This change extends the documentation with an overview of the crate, more examples, and a bunch of explanations of the public modules.

Going ahead with the merge once CI is through.


How to extend layer numbers of AALBERT?

I have another question, AALBERT just has 3 Transformer layers, and I want to extend it to 7 or more layers in my experiment.
In VGG and other CNN models, it is easy, but in AALBERT I found it's hard. I tried several methods by debugging codes to extend layers, but all failed！
It's because when I get every layer out in the first several layers, the Transformer layers needs  but I can not got right  pos_enc and attn_mask.
Do you have an easy way or suggestion to solve this problem？ Thanks a lot! @leo19941227

Hi @myhrbeu,
I'm not sure if I understand your question correctly, but you can change the number of layers by changing this line: https://github.com/s3prl/s3prl/blob/e52439edaeb1a443e82960e6401ae6ab4241def6/s3prl/pretrain/audio_albert/config_model.yaml#L4
For example:
num_hidden_layers: 7

Aha！ That's an easy way to do my experiments! Thanks a lot!
And I  used debugging code for several hours to achieve this target through the way like transfer-learning, and I found it is very slow when having 7 layers.
I have two questions：
1、If I use AALBERT and use config.share_layers=False, is it means every layer begins with the same weights and is different at the end?
2、Is the Transformer layer in AALBERT the same as used in NLP tasks? I want to use the pre-trained weights for the downstream tasks, so I think loading the weights to my own model, will make my experiments much easier.
Thanks！


[3.x] #1778 subdomain routing issues

Different approach to https://github.com/area17/twill/pull/1779
My main concern is the overwriting of config. I have not dived too deep into it but I made a solution (I think) where it is irrelevant where the request comes from.
My main concern was that with overwriting config, in memory adaptions can cause conflicts (like the tests) but also Laravel octane.
One breaking change here, is that when subdomain routing is enabled, base domain routes are no longer created. I might need to revise this based on input.
Fixes https://github.com/area17/twill/issues/1778
I think this test covers the usecases: tests/integration/SubdomainRoutingTest.php

Looking at the tests this has a lot of side effects, Investigating it :)


miopen only supports 4D tensors, dim=5 not allowed

I run a 3d conv network.
I have a problem
Has anyone encountered it?
Predict volume shape: (24, 31, 31)
2019-06-06 16:58:04.595653: F tensorflow/stream_executor/rocm/rocm_dnn.cc:494] miopen only supports 4D tensors, dim=5 not allowed
GPU:radeon vii

What is your ROCm version and MIOpen version? Are you running HIP or OpenCL?

I install miopen-opencl
Version is as follows
$ apt-cache policy rocm-dkms
rocm-dkms: 2.4.25
$ apt-cache policy miopen-opencl
miopen-opencl: 1.8.1-84fcb51

Unfortunately we have an imbalance in our library where we have implemented 3-D convolutions in rocBLAS. This mean it is currently only supported by the HIP backend. We are working on restoring symmetry to our library in a future release.


Licensing the repository

First thanks @alexanderson1993 for this really awesome project 🥇
I noticed that the repository doesn't have a license can this be added ?

I can do that, but in the meantime just consider it MIT licensed. Have fun, don't sue me.


[Bug] The issue of duplicate enhancement in apm-jdk-threadpool-plugin

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
Java Agent (apache/skywalking-java)
What happened
The apm-jdk-threadpool-plugin may encounter duplicate enhancement of Runnable or Callable objects, such as the case where it has already been enhanced by RunnableWrapper or CallableWrapper with toolkit.
What you expected to happen
When The apm-jdk-threadpool-plugin encounter duplicate enhancement of Runnable or Callable objects, the same thread invocation may result in the creation of two LocalSpan instances.
How to reproduce

jdk 1.8
skywalking agent 8.14.0
move apm-jdk-threadpool-plugin to plugins dir.
use RunnableWrapper to wrap Runnable when execute in ThreadPoolExecutor

        ThreadPoolExecutor executor = new ThreadPoolExecutor(10, 10, 1000, TimeUnit.HOURS, new ArrayBlockingQueue<>(10));
        executor.execute(RunnableWrapper.of(() -> {
            log.info("executor.execute");
        }));

Anything else
In some old projects, RunnableWrapper or CallableWrapper are used for enhancement. However, in newer code that incorporates the apm-jdk-threadpool-plugin, using wrappers for asynchronous thread execution with ThreadPoolExecutor is no longer necessary. This can lead to the mentioned situation.
I believe I can add a check in the apm-jdk-threadpool-plugin to ignore Runnable or Callable objects that have already been enhanced by Skywalking.
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I need to see how you check. This could be done, but be careful of the ClassLoader about checking the class is enhanced.

No update in a week. Close for now.


Typo - Quality instead of Quantity

There's a typo in the "Print the Sales journal report" section, at step 2.
I believe that instead of "Quality", the author meant "Quantity":
In the Quality field, enter 1.

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

ID: 2b14b0dc-1149-4d37-054c-1324f8f5340e
Version Independent ID: 85841d28-402d-1ece-38f5-cec29c9a2e34
Content: Journal reports - Finance | Dynamics 365
Content Source: articles/finance/localizations/emea-bel-journal-reports.md
Service: dynamics-365-finance
Product: ****
Technology: ****
GitHub Login: @AdamTrukawka
Microsoft Alias: atrukawk

Same comment for the "Print the Purchase journal report" section:
I think "Quantity" should be written instead of "Quality" at step 2 - In the Quality field, enter 3.

@gebaluta, thank you for your feedback. The article has been updated.

@twheeloc I still see the old(incorrect) statement in the docs:


dep: bumping go 1.19 to 1.19.1

Signed-off-by: David Dymko<EMAIL_ADDRESS>Description
Bumping Go from 1.19 to 1.19.1
https://go.dev/doc/devel/release#go1.19.minor
Related Issues
List related issues.
Testing
CI goes green
Checklist

[ ] I made sure to update CHANGELOG.md.
Remember, the CHANGELOG needs to mention:

Any new features
Any changes to our included version of Envoy
Any non-backward-compatible changes
Any deprecations

[x] This is unlikely to impact how Ambassador performs at scale.
Remember, things that might have an impact at scale include:

Any significant changes in memory use that might require adjusting the memory limits
Any significant changes in CPU use that might require adjusting the CPU limits
Anything that might change how many replicas users should use
Changes that impact data-plane latency/scalability

[x] My change is adequately tested.
Remember when considering testing:

Your change needs to be specifically covered by tests.

Tests need to cover all the states where your change is relevant: for example, if you add a behavior that can be enabled or disabled, you'll need tests that cover the enabled case and tests that cover the disabled case. It's not sufficient just to test with the behavior enabled.

You also need to make sure that the entire area being changed has adequate test coverage.

If existing tests don't actually cover the entire area being changed, add tests.
This applies even for aspects of the area that you're not changing – check the test coverage, and improve it if needed!

We should lean on the bulk of code being covered by unit tests, but...
... an end-to-end test should cover the integration points

[ ] I updated DEVELOPING.md with any any special dev tricks I had to use to work on this code efficiently.

[ ] The changes in this PR have been reviewed for security concerns and adherence to security best practices.

lgtm...shouldn't be any issues with patch release for Edge Stack but let's make sure we land it there too.

The CVEs in 1.19 https://github.com/emissary-ingress/emissary/runs/8331034081 will be fixed by this PR


Falsifying examples are not shown in case of hypothesis errors

If the test run discovers multiple errors and hypothesis.errors.MultipleFailures: Hypothesis found 2 distinct failures. is raised, then all the other output is missing
Also, it goes for timeout errors, we can display it as "E" in the CLI output and not stop the whole test suite

Is this actually fixed? I believe I am still seeing this problem in version 3.9.3

Hm, it was a while ago, but I believe it was fixed at least for the case I was facing. Could you, please, provide an example where it doesn't work?

I am running through Python code, here is a reproducible example:
# api_contract_tests.py

import schemathesis
from schemathesis.checks import status_code_conformance

schema = schemathesis.from_uri(
    "https://developer.nylas.com/_spec-files/public-cloud-api.yaml",
    base_url="https://api.nylas.com"
)

@schema.parametrize(endpoint="/calendars/availability$")
def test_api(case):
    response = case.call()
    case.validate_response(response, checks=(status_code_conformance,))

% pytest api_contract_tests.py
E
==============================================================================
ERROR: api_contract_tests.py::test_api[POST /calendars/availability][P]
------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/david/dev/cloud-core/nylas/api_contract_tests.py", line 23, in test_api
    def test_api(case):
  File "/Users/david/.pyenv/versions/3.8.5/envs/cloud-core-3.8/lib/python3.8/site-packages/hypothesis/core.py", line 1122, in wrapped_test
    raise MultipleFailures(
hypothesis.errors.MultipleFailures: Hypothesis found 2 failures in explicit examples.

------------------------------------------------------------------------------
Ran 1 tests in 2.77s

FAILED (errors=1)

Here is my output:
⇒  pytest /home/stranger6667/.config/JetBrains/PyCharm2020.3/scratches/scratch_65.py
========================================================================================================================= test session starts ==========================================================================================================================
platform linux -- Python 3.9.5, pytest-6.2.4, py-1.10.0, pluggy-0.13.1
rootdir: /home/stranger6667
plugins: mock-1.13.0, schemathesis-3.9.2, allure-pytest-2.8.36, hypothesis-6.13.12, forked-1.3.0, httpserver-1.0.0, doctestplus-0.9.0, xdist-1.34.0, deadfixtures-2.2.1, subtests-0.5.0, asyncio-0.11.0
collected 1 item

../../../.config/JetBrains/PyCharm2020.3/scratches/scratch_65.py F                                                                                [100%]

=============================================================================================================================== FAILURES ===============================================================================================================================
______________________________________________________________________________________________________________ test_api[POST /calendars/availability][P] _______________________________________________________________________________________________________________

    @schema.parametrize(endpoint="/calendars/availability$")
>   def test_api(case):
E   hypothesis.errors.MultipleFailures: Hypothesis found 2 failures in explicit examples.

../../../.config/JetBrains/PyCharm2020.3/scratches/scratch_65.py:13: MultipleFailures
------------------------------------------------------------------------------------------------------------------------------ Hypothesis ------------------------------------------------------------------------------------------------------------------------------
Falsifying explicit example: test_api(
    case=Case(headers={'Accept': '', 'Authorization': 'Bearer '}, body={'duration_minutes': 30, 'start_time':<PHONE_NUMBER>, 'end_time':<PHONE_NUMBER>, 'interval_minutes': 10}),
)
Traceback (most recent call last):
  File "/home/stranger6667/programming/PycharmProjects/schemathesis/src/schemathesis/_hypothesis.py", line 41, in test_function
    return test(*args, **kwargs)
  File "/home/stranger6667/.config/JetBrains/PyCharm2020.3/scratches/scratch_65.py", line 15, in test_api
    case.validate_response(response, checks=(status_code_conformance,))
  File "/home/stranger6667/programming/PycharmProjects/schemathesis/src/schemathesis/models.py", line 420, in validate_response
    raise exception_cls(
schemathesis.exceptions.CheckFailed:

1. Received a response with a status code, which is not defined in the schema: 401

Declared status codes: 200

----------

Response payload: `{"message":"Could not verify access credential.","type":"invalid_request_error"}
`

Run this Python code to reproduce this response:

    requests.post('https://api.nylas.com/calendars/availability', headers={'User-Agent': 'schemathesis/3.9.2', 'Accept-Encoding': 'gzip, deflate', 'Accept': '', 'Connection': 'keep-alive', 'Authorization': 'Bearer ', 'Content-Type': 'application/json', 'Content-Length': '98'}, data=b'{"duration_minutes": 30, "start_time":<PHONE_NUMBER>, "end_time":<PHONE_NUMBER>, "interval_minutes": 10}')

Falsifying explicit example: test_api(
    case=Case(headers={'Accept': '', 'Authorization': 'Bearer '}, body={'duration_minutes': 30, 'start_time':<PHONE_NUMBER>, 'end_time':<PHONE_NUMBER>, 'interval_minutes': 10, 'emails'<EMAIL_ADDRESS>'free_busy': [{'email'<EMAIL_ADDRESS>'object': 'free/busy', 'time_slots': [{'start_time':<PHONE_NUMBER>, 'end_time':<PHONE_NUMBER>, 'object': 'time_slot', 'status': 'busy'}]}], 'open_hours': [{'emails'<EMAIL_ADDRESS>'days': ['0'], 'timezone': 'America/Chicago', 'start': '10:00', 'end': '14:00', 'object_type': 'open_hours'}]}),
)
Traceback (most recent call last):
  File "/home/stranger6667/programming/PycharmProjects/schemathesis/src/schemathesis/_hypothesis.py", line 41, in test_function
    return test(*args, **kwargs)
  File "/home/stranger6667/.config/JetBrains/PyCharm2020.3/scratches/scratch_65.py", line 15, in test_api
    case.validate_response(response, checks=(status_code_conformance,))
  File "/home/stranger6667/programming/PycharmProjects/schemathesis/src/schemathesis/models.py", line 420, in validate_response
    raise exception_cls(
schemathesis.exceptions.CheckFailed:

1. Received a response with a status code, which is not defined in the schema: 401

Declared status codes: 200

----------

Response payload: `{"message":"Could not verify access credential.","type":"invalid_request_error"}
`

Run this Python code to reproduce this response:

    requests.post('https://api.nylas.com/calendars/availability', headers={'User-Agent': 'schemathesis/3.9.2', 'Accept-Encoding': 'gzip, deflate', 'Accept': '', 'Connection': 'keep-alive', 'Authorization': 'Bearer ', 'Content-Type': 'application/json', 'Content-Length': '464'}, data=b'{"duration_minutes": 30, "start_time":<PHONE_NUMBER>, "end_time":<PHONE_NUMBER>, "interval_minutes": 10, "emails"<EMAIL_ADDRESS>"free_busy": [{"email"<EMAIL_ADDRESS>"object": "free/busy", "time_slots": [{"start_time":<PHONE_NUMBER>, "end_time":<PHONE_NUMBER>, "object": "time_slot", "status": "busy"}]}], "open_hours": [{"emails"<EMAIL_ADDRESS>"days": ["0"], "timezone": "America/Chicago", "start": "10:00", "end": "14:00", "object_type": "open_hours"}]}')

======================================================================================================================= short test summary info ========================================================================================================================
FAILED ../../../.config/JetBrains/PyCharm2020.3/scratches/scratch_65.py::test_api[POST /calendars/availability][P] - hypothesis.errors.MultipleFailures: Hypothesis found 2 failures in explicit examples.
========================================================================================================================== 1 failed in 3.74s ===========================================================================================================================

How your pytest.ini looks like? And what pytest version are you using?

Ok, I was using pytest 6.2.2, but when I switched to 6.2.4, it worked. Thanks!

It is weird that I'm still seeing this problem, I am using pytest 7.1.2

@JLU-Neal Could you, please share your Schemathesis / Python / OS versions as well? Do you run the same code sample as above?

Actually, I did not run the code here, but I face the same problem. Python 3.8.10, OS ubuntu 20.

Also getting this problem on both pytest 6.2.4 and 7.1.2
pytest.ini is empty
platform linux -- Python 3.7.5, pytest-7.1.2, pluggy-1.0.0
rootdir: /app/core/tests, configfile: pytest.ini
plugins: hypothesis-6.54.0, cov-3.0.0
collected 1 item

core/tests/unit/unifiers/test_frame_scaling.py F                                                                                [100%]

================== FAILURES ==================
test_frame_persists_aspect_ratio_after_scale

    @given(...)
>   def test_frame_persists_aspect_ratio_after_scale(resolution_in: ImageResolution, resolution_out: ImageResolution):
E   exceptiongroup.ExceptionGroup: Hypothesis found 4 distinct failures. (4 sub-exceptions)

core/tests/unit/unifiers/test_frame_scaling.py:7: ExceptionGroup
generated xml file: /app/reports/report.xml
=========== short test summary info ============
FAILED core/tests/unit/unifiers/test_frame_scaling.py::test_frame_persists_aspect_ratio_after_scale - exceptiongroup.ExceptionGroup: Hypothesis found 4 distinct failures. (4 sub-exceptions)
=========== 1 failed in 1.28s ===========

By any chance, do you run it via PyCharm launcher?
Btw, @subatiq , I don't see the schemathesis plugin installed in your output - how does it relate to schemathesis behavior?

@Stranger6667 strange, I never installed it before, just used hypothesis and had no problems.
Ran it with schemathesis and still the same output. Plugins from output: plugins: hypothesis-6.54.0, subtests-0.6.0, cov-3.0.0, schemathesis-3.16.1
Looks like python version also has nothing to do with that, tested on 3.7.5 and 3.10.5
Also, no PyCharm, I ran everything from the terminal

It might be better to report it upstream to Hypothesis, as it looks like the test itself doesn't use Schemathesis, and its output does not depend on Schemathesis installed

Yes, sorry, seems like I missed the hypothesis repo and found yours instead

No worries! :)


Improve Route53 instructions.

solves
https://github.com/cert-manager/website/issues/289

Thanks!
/lgtm
/approve
/ok-to-test

@meyskens Can you please re approve this?

/lgtm


🔧 make google oauth client id customizable

Currently, the ID is fixed to a test client that I own. Only me and people I personally authorize can login using it. To allow others to use petibrugnon, I need to make this customizable, and document how one can create an OAuth client to use petibrugnon with.

Done


Plugin do not scan recursevely when multi repositories inside folder inside workspace

Extension version: 0.15.0
VSCode Version: 1.44
OS: Fedora 31

Steps to Reproduce:

Have a folder with several repositories
Add this top folder only to the workspace
Not even changing the repository in source pane makes the pull requests to appear

Creating a new workspace with 10 repositories folders added to it ( instead of 1 ) makes the plugin to show some PRs ( 14 PRs ), but not all. Changing the project on Source pane, or Git pane doesn't make any difference .

Closing as a duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/436. This should be fixed in version 0.20.0 of the extension. Thanks!


Test on UCFRep

I want to test the model on the UCFRep. How should I reorganize the UCFRep so I can use the UCFRep_loader.py

And How do I get the ucfval.csv

Hi, sorry for the late reply. I try to find my preprocessed ucfval.csv but failed, since I am not following this work anymore, and the disk of our gpu cluster was cleaned once.
In the file of these .mat, the label is something like: [0, 9, 12, 20], which means that it should be changed into [0 9 9 12 12 20] in our label format. By doing this in matlab, you can get the ucfval.csv. I believe it is not hard to implement this. If you have any other questions, you can still ask me here.


Added "Security Tools" category and "Scout: Bug Fighter" entry

This PR adds the "Security Tools" category to the "Developer Tools" documentation, with "Scout: Bug Fighter" as the first entry in this new category.
Scout is a static code analysis tool designed to assist Soroban developers and auditors in identifying potential security threats, with a strong focus on detection capabilities, usability, and developer experience.
Maintainability
Scout is under active development and has continuous support. Since its launch in June 2023, 17 versions have been released, three of them in the past 30 days. The most recent release (0.2.15) has been downloaded 264 times from the crates.io Rust package manager. The total number of downloads since Scout's launch has reached over 7,000. See Scout crates.io entry here.
Functionality
Scout analyzes Soroban smart contracts to identify potential issues and deviations from best practices, helping developers write safer and more reliable code. Please refer to this video for a quick introduction.
It currently supports 23 detectors, with 4 additional detectors to be released shortly.
The tool includes various features to facilitate smooth integration into developers' workflows:

A CLI to run Scout directly from the terminal.
A VSCode extension for integration into one of the most popular IDEs.
A GitHub action for integration into CI/CD pipelines.
Multiple output formats (md, pdf, json, html, sarif).

Documentation
Scout includes comprehensive documentation on detectors and tool usage, available here.
Community Support
Scout has been awarded in 3 Stellar Community Fund submissions, and the Scout team remains active in Soroban's developer community.
In addition, we have ongoing initiatives to contribute to the community with educational material on security and Soroban development:

Workshops
Video tutorials
Security-reviewed Soroban smart contract examples

Scout website: https://www.coinfabrik.com/products/scout/
Scout repository: https://github.com/CoinFabrik/scout-soroban

Thank you so much for the PR! We'll get it reviewed and approve or let you know if we have any feedback 🙏

Hi! Sorry for the delay on reviewing this. It's on our radar and we'll get to it soon.

Hi! Sorry for the delay on reviewing this. It's on our radar and we'll get to it soon.

No problem! Let me know if you need any further clarifications.

This is actually really awesome.  The reports, especially the HTML format, is really clear and easy to use and has a lot of great context for how to resolve the issue.

The VS code extension is great too, identifying security issues early in the dev process.

Great feedback! Thank you @anataliocs! @ElliotFriend I'm happy to merge if you are.

Love to hear it! Thanks @anataliocs for testing and vetting it!! 👍🏻

Alright, thanks again @matiascabello!


How to clear the cache?

HI.
First: thanks for this extension, I am using it massively.
I have right now two questions about clearing the cache:

How to clear the cache completely?
How to clear the cache just for one image?

The second one is for the case if an image is re-uploaded and thus has the same name, but might be different in content. In that case it would be cool if I could manually trigger a deletion of the old cached files, something like this:
\Yii::$app->imageresize->clearCache($filename);
I do see a function "clearCache" in your code, but it is not working.  I suppose it is meant for my Question 1 above, deleting all caches, right?
Any help highly appreciated.
gb5256

Hi @gb5256 ,
The method clearCache should remove all files, what is the error you get?
At the moment i'm very busy, maybe you can make a pull request with the possibility to remove single cached files?
Regards,
Noam


Where to handle ExternalInterface.call from swf?

I emebd swf using  tag in index.html like this:
    <script >
        function testExternalCall(str) {
            console.log(str);
        }
    </script>
    <webview id="swf" src="./asapp/out/Main.swf" style="display:inline-block; width:1024px; height:768px"
        plugins="on" disablewebsecurity="on"></webview>

in actionscript make a call like this:
ExternalInterface.call("testExternalCall", "invoke from actionscript testExternalCall");

However， testExternalCall function in js is not triggered. Any suggestion?

You can check the solution in #2041.

@zcbenz ,thanks for your reply.
Yesterday I have checked the #2041 thread, also i fixed the security issue.
If i embed html in webview tag, then put testExternalCall function in Main.html. It works well，function is triggered.
<webview id="swf" src="./asapp/out/Main.html" style="display:inline-block; width:1024px; height:768px"
        plugins="on" disablewebsecurity="on"></webview>

I don't know where to put testExternalCall function if directly set src=Main.swf.
I have tried the preload attribute of webview tag. The result is js file is loaded, but function in js is still not triggered.
// alert is triggered
alert("swfBridge is loaded")

// this function is not triggered when ExternalInterface.call from actionscript
function testExternalCall(str) {
    console.log(str);
}

Maybe you can try window.testExternalCall = function() {...}, the preload script doesn't run in global scope.

Still doesn't work.
Is the webview tag the only way to embed swf content? I try add these code in index.html, and cause a "Couldn't load plugin" error. It seems only webview tag has attribute plugins="on".
<object id="swf" width="550" height="400">
        <embed src="./asapp/out/Main.swf"
        type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="1024" height="768"></embed>
        <param name="movie" value="sample.swf" />
        <param name="bgcolor" value="#ffffff" />
        <param name="height" value="768" />
        <param name="width" value="1024" />
        <param name="quality" value="high" />
        <param name="menu" value="false" />
        <param name="allowscriptaccess" value="always" />
    </object>

Another question, can i use "ipc" module in webview embed html pages and communicate with index.html?

You have to load flash plugin to make flash work:
https://github.com/atom/electron/blob/master/docs/tutorial/using-pepper-flash-plugin.md

Another question, can i use "ipc" module in webview embed html pages and communicate with index.html?

There is ipc.sendToHost API.


Loc.GetString refactor issues

Description
Keeping track of any issues caused by the big fluent refactor by @GalacticChimp in #4155
PA computer is messed up (Seþ # 2464)

AME number labels don't have spaces before them (Seþ # 2464)

R&D console is messed up (Seþ # 2464)

Medical scanner verb eject is messed up (Seþ # 2464)

Connecting dialog is broken.

ok, I'll take a look at these

Character inventory menu is broken

#4226

so far I've fixed all of the above issues + a few more. Perhaps let's wait a week more, and collect a few more errors.


Support building arklib-android in MacOS

Support building arklib-android in MacOS without using cargo-ndk (https://github.com/bbqsrc/cargo-ndk).

Going to be superseded by PR with better README containing cargo-ndk instructions.

Provided cargo-sdk as a building alternative, so these changes are not needed anymore: https://github.com/ARK-Builders/arklib-android/pull/123


Set colors for categorical attributes in artists dataset

For now, only the colors for gender are set. All categorical attributes should get some color. Makes it also easier to see if filters work.

@bikramkawan, you've addressed this issue already, right? Please don't forget to reference the issues in your commits and keep the status of the issues up-to-date.

I did that Sorry I forgot to update here.
https://github.com/Caleydo/mothertable/commit/301234c0af981e4ec05fd6fadcbd89dbfa8c303f


[iOS] Update Cocoapods for 0.14 release

Update the podspec version to 0.14 to prepare for the 0.14 pod release.

Good catch, I've updated this PR to include that


Schema reference having a same name as the schema in parent document

Consider having two open api documents.
 info:
  title: Common Data Types
  version: "1.0"
paths:
  /subscriptions:
    get:
      summary: read all of the active subscriptions for the app.
      operationId: getSubscriptionsById
      parameters:
        - name: appId
          in: path
          description: App ID
          required: true
          schema:
            type: integer
            format: int64
      responses:
        '200':
          description: OK (Successful)
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Subscription'
        '500':
          $ref: './issue-1108-1.yaml#/components/responses/E500'
        '501':
          $ref: '#/components/schemas/ProblemDetails'
components:
  schemas:
    ProblemDetails:
      type: object
      properties:
        title:
          type: string
          description: A short, human-readable summary of the problem
        status:
          type: integer
          description: The HTTP status code for this occurrence of the problem.
    Subscription:
      type: string

Open api document for sample.yaml
info:
  title: Common Data Types
  version: "1.0"
paths: {}
components:
  responses:
    E500:
      description: Server Error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ProblemDetails'
  schemas:
   ProblemDetails:
      type: object

Here there are two schema having the same name.  Can this be referenced like wise.
Open API cannot have duplicate schema under components.
By this there totally two schema with the same.
can you point me towards the part of the specification that clarifies the part about referencing schema with name as in original document or can you shed some light as to the correctness of my understanding and validate where this is correct ?.

It's been more than 2 weeks so I'm assuming the answer was sufficient.


marlin fail ValueError: infeatures must be divisible by 128 and outfeatures by 256.

model: qwen1.5 14b chat
auto_gptq : 0.8.0dev+cu118,0.7.0dev+cu118
quantize code:
quantize_config = BaseQuantizeConfig(
    bits=4,  # quantize model to 4-bit
    group_size=128,  # it is recommended to set the value to 128
    desc_act=False,  # desc_act and group size only works on triton
    damp_percent=0.005,
    is_marlin_format=True
)
# load un-quantized model, the model will always be force loaded into cpu
model = AutoGPTQForCausalLM.from_pretrained(pretrained_model_dir, quantize_config=quantize_config)

# quantize model, the examples should be list of dict whose keys can only be "input_ids" and "attention_mask"
# with value under torch.LongTensor type.
model.quantize(traindataset, use_triton=False)

# save quantized model
model.save_quantized(quantized_model_dir)

quantize no problem.
load code:
model_q = AutoGPTQForCausalLM.from_quantized(model_path, device="cuda:0", use_safetensors=True, use_marlin=True)
tokenizer = AutoTokenizer.from_pretrained(model_path)

prompt = "what is your name?"
inp = tokenizer(prompt, return_tensors="pt").to(device)
res = model_q.generate(**inp, num_beams=1, min_new_tokens=60, max_new_tokens=60)
predicted_text = tokenizer.decode(res[0])

WARNING - ignoring unknown parameter in quantize_config.json: quant_method.
INFO - The layer lm_head is not quantized.
Overriding QuantLinear layers to use Marlin's QuantLinear...:   2%|▍                   | 12/566 [00:00<00:12, 44.73it/s]Traceback (most recent call last):
File "/home/oneway/LongLM-master/fastapi_use.py", line 16, in
uvicorn.run("autogptq_infer_api:app", host='<IP_ADDRESS>', port=6006, workers=1)
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/uvicorn/main.py", line 587, in run
server.run()
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/uvicorn/server.py", line 62, in run
return asyncio.run(self.serve(sockets=sockets))
File "/root/anaconda3/envs/train/lib/python3.9/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "uvloop/loop.pyx", line 1517, in uvloop.loop.Loop.run_until_complete
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/uvicorn/server.py", line 69, in serve
config.load()
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/uvicorn/config.py", line 458, in load
self.loaded_app = import_from_string(self.app)
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/uvicorn/importer.py", line 21, in import_from_string
module = importlib.import_module(module_str)
File "/root/anaconda3/envs/train/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/home/oneway/LongLM-master/autogptq_infer_api.py", line 17, in
model = AutoGPTQForCausalLM.from_quantized(ckpt, trust_remote_code=True,use_marlin=True,strict=False, device="cuda:0")
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/modeling/auto.py", line 135, in from_quantized
return quant_func(
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/modeling/_base.py", line 1229, in from_quantized
model, model_save_name = prepare_model_for_marlin_load(
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/utils/marlin_utils.py", line 37, in prepare_model_for_marlin_load
model = convert_to_marlin(model, quant_linear_class, quantize_config, repack=False)
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/utils/marlin_utils.py", line 152, in convert_to_marlin
new_module = MarlinQuantLinear(
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/nn_modules/qlinear/qlinear_marlin.py", line 98, in init
raise ValueError("infeatures must be divisible by 128 and outfeatures by 256.")
ValueError: infeatures must be divisible by 128 and outfeatures by 256.

@Minami-su Duplicate of https://github.com/AutoGPTQ/AutoGPTQ/issues/581
Direct quantization of marlin is broken. You need to check the above workaround.

@Minami-su Duplicate of #581
Direct quantization of marlin is broken. You need to check the above workaround.

I tryed non marlin -> load use marlin=True,but have error at load model
model = AutoGPTQForCausalLM.from_quantized(ckpt, trust_remote_code=True,use_marlin=True,strict=False, device="cuda:0")
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/modeling/auto.py", line 135, in from_quantized
return quant_func(
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/modeling/_base.py", line 1229, in from_quantized
model, model_save_name = prepare_model_for_marlin_load(
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/utils/marlin_utils.py", line 63, in prepare_model_for_marlin_load
model = convert_to_marlin(model, quant_linear_class, quantize_config, repack=True)
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/utils/marlin_utils.py", line 152, in convert_to_marlin
new_module = MarlinQuantLinear(
File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/nn_modules/qlinear/qlinear_marlin.py", line 98, in init
raise ValueError("infeatures must be divisible by 128 and outfeatures by 256.")
ValueError: infeatures must be divisible by 128 and outfeatures by 256.

@Minami-su  Please use PR https://github.com/AutoGPTQ/AutoGPTQ/pull/586 to generate the quantized marlin directly and then  test again. The problem with main branch is that it does quantize successfully but the marlin format file you generated is actually not marlin at all.

@Minami-su Please use PR #586 to generate the quantized marlin directly and then test again. The problem with main branch is that it does quantize successfully but the marlin format file you generated is actually not marlin at all.

I installed your project executing non marlin int4 quantize ->infer use_marlin==True then it works
But marlin int4 quantize ->infer use_marlin==True still reports an error
File "/home/oneway/LongLM-master/autogptq_infer_api.py", line 17, in <module>
   model = AutoGPTQForCausalLM.from_quantized(ckpt, trust_remote_code=True,use_marlin=True,strict=False, device="cuda:0")
 File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/modeling/auto.py", line 135, in from_quantized
   return quant_func(
 File "/root/anaconda3/envs/train/lib/python3.9/site-packages/auto_gptq-0.8.0.dev0+cu118-py3.9-linux-x86_64.egg/auto_gptq/modeling/_base.py", line 1247, in from_quantized
   accelerate.utils.modeling.load_checkpoint_in_model(
 File "/root/anaconda3/envs/train/lib/python3.9/site-packages/accelerate/utils/modeling.py", line 1625, in load_checkpoint_in_model
   set_module_tensor_to_device(
 File "/root/anaconda3/envs/train/lib/python3.9/site-packages/accelerate/utils/modeling.py", line 318, in set_module_tensor_to_device
   raise ValueError(f"{module} does not have a parameter or a buffer named {tensor_name}.")
ValueError: QuantLinear() does not have a parameter or a buffer named g_idx.

Have a new issue,it's works on 0.5B model ,but not work on 14b model ,infeatures, outfeatures have 13696 % 256=53.5 can't Integer divide

13696 % 256=53.5 can't Integer divide

@Minami-su This is a limitation of marlin kernel. Please use e.g. exllama/cuda-old kernel instead.

@Minami-su You may try out this workaround from Qwen docs to pad the weights before quantization.

@vhain There is no workaround needed with https://github.com/ModelCloud/GPTQModel

@Qubitium I wasn't aware of ModelCloud/GPTQModel, thanks for pointing out!
Just cancelled quantization with the workaround + AutoGPTQ, and just restarted the jobs with ModelCloud/GPTQModel.


Timeout when dconf.settings has ('xkb', 'us+alt-intl') [org/gnome/desktop/input-sources]

[org/gnome/desktop/input-sources]
current='uint32 0'
sources=[('xkb', 'us+alt-intl')]
xkb-options=['terminate:ctrl_alt_bksp', 'lv3:ralt_switch']
The above addition to my dconf.settings file makes dconf2nix time out when trying to parse into a .nix file. It also times out when there is a list of multiple sources and 'us+alt-intl' is one of them, but not when it is a list of sources like 'us' and 'fr'. Curious if it is because of the '+' and '-' in the keyboard name.
Edit 1: But looking at Dconf.hs on line 66 it seems to allow for these characters in Strings.
Edit 2: It seems the commit that allows '+' in Strings came after the last release. I will try using the master branch.

This was fixed by building the master branch. I look forward to the next release!

This has been fixed in #29 but I forgot to make a new release. If you try out master instead, this should work.

@michzappa I just published a new release: https://github.com/gvolpe/dconf2nix/releases/tag/v0.0.7
It'll take a while until the new version reaches nixpkgs unstable, though, so it's always better to use an overlay to be on the latest version.


Improved OPTIONS support and improved docs

Codecov Report

Merging #13 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master    #13   +/-   ##
=======================================
  Coverage       100%   100%
- Complexity       66     67    +1
=======================================
  Files             5      5
  Lines           194    196    +2
=======================================
+ Hits            194    196    +2

Impacted Files
Coverage Δ
Complexity Δ

src/AbstractRestfulController.php
100% <100%> (ø)
40 <0> (+1)
: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 b89c4dd...1edeae7. Read the comment docs.


An inconsistency from heterogeneous equality

Currently, we can conclude a == b from eq #a #b x y. Hence, we can conclude nat == int from eq3 #nat #int 1 1, which is provable, and we get a contradiction.
This happens since a heterogeneous equality eq3 #a #b x y is encoded to z3 simply as (= x y), without accounting for their types. Nik quickly cooked up a patch to encode it as (and (= a b) (= x y)) preventing this bug, since one cannot prove eq3 #nat #int 1 1 anymore. It's currently under CI to test the impact, but it appears to be the right solution.
Here's the original proof of false. The lemma elim2 misteriously fails, but it succeeds, correctly we think, with the new encoding. In this version we jump through some hoops to prove it.
module Bug

let elim a b (x:a) (y:b) : Lemma (requires (eq3 #a #b x y)) (ensures (x == y)) = ()

(* Why does this fail, if the above succeeds? *)
[@expect_failure]
let elim2 (a b:Type0) (x:a) (y:b) : Lemma (requires (eq3 #a #b x y)) (ensures (a === b)) = ()

open FStar.Squash

let elim3 (a b:Type0) (x:a) (y:b) (h : eq3 #a #b x y) : Lemma (a === b) =
 bind_squash #(h_equals #a x #b y) #(a === b) h (function | HRefl -> assert (a === b))

let elim3' (a b:Type0) (x:a) (y:b) : Lemma (requires (eq3 #a #b x y)) (ensures (a === b)) =
 assert (eq3 #a #b x y);
 let h : squash (eq3 #a #b x y) = () in
 let _ = bind_squash #(eq3 #a #b x y) #(a === b) h (fun h' -> elim3 a b x y h') in
 assert (a === b)

let coerce #a (#b:Type{b == a}) (x:a) : y:b{y === x} = x

let _ =
  elim3' nat int 1 1;
  assert (nat == int);
  let x : nat = coerce #int #nat (-1) in
  assert False

Seems we were not lucky and we have some failures related to prop, here are the first ones:
FStar.Algebra.Monoid.fst(55,27-55,31): (Error 19) Subtyping check failed; expected type Prims.prop; got type Prims.logical
FStar.Algebra.Monoid.fst(84,33-84,39): (Error 19) Subtyping check failed; expected type Prims.prop; got type Prims.logical
FStar.Algebra.Monoid.fst(153,26-153,28): (Error 19) Subtyping check failed; expected type Prims.prop; got type Prims.logical
FStar.Algebra.Monoid.fst(155,14-155,18): (Error 19) Subtyping check failed; expected type Prims.prop; got type Prims.logical
FStar.Algebra.Monoid.fst(166,28-166,32): (Error 19) Subtyping check failed; expected type Prims.prop; got type Prims.logical
Verified module: FStar.Algebra.Monoid (9014 milliseconds)
5 errors were reported (see above)

Can't look into it now, but this module is a bit unusual in that it uses singleton:
(*
 * Pure and ghost inner let bindings are now always inlined during the wp computation, if:
 * the return type is not unit and the head symbol is not marked irreducible.
 * To circumvent this behavior, singleton can be used.
 * See the example usage in ulib/FStar.Algebra.Monoid.fst.
 *)
irreducible let singleton (#a:Type) (x:a) :(y:a{y === x}) = x

I have a fix for this with a green on F* in the branch nik_eq3_false
Waiting to push until I get an everest green also ... but the everest build has been flaky last week.


[WIP] Encapsulate tests for plugins

Thanks, I didn't get around to supporting this in my initial branch :+1:

@zachmullen If you like how 93d260b implements it, then I'll go ahead and port the rest of the plugin-specific tests over.
I want to make sure that's done right, specifically in regards to coverage, and if we're ok with
add_python_test(graph PLUGIN vtk PLUGINS_ENABLED vtk) as opposed to having CMake pick up on what directory/plugin it is and the user leaving PLUGIN vtk out.

:+1:

5eed106 highlights an inconvenience with having to rename tests because they may exist in a plugin as well as core.
Additionally, I left the table/tree plugin tests in core because some of them use converters from the vtk plugin and the r plugin, so they are codependent but it doesn't make sense to group them together.

Ready for review.

This LGTM


RFC: Add support for bitwise operators

Rendered

I too, am in favor of adding bitwise operator support <3

I will note that bitwise operators are explicitly documented as something that we don't plan to support here: https://luau-lang.org/compatibility. While decisions like that can always be reversed in the future, in general we are unlikely to start supporting a feature that is explicitly documented as "we don't think we will support it" without an extensive amount of justification.
From the performance perspective, we're already using specialized paths inside the interpreter so you aren't paying the full overhead of a function call. Bit operations are still not free, but part of the cost there is simply checking the argument types and converting between number and integer types.
From the behavior perspective, this RFC alludes to having the bit operators work for all numbers somehow but doesn't clarify the behavior - absent full integer support (which, again, see compatibility page for - no current plans), we'd need to have the exact same semantics as bit32 library has today, as you can't represent a 64-bit integer precisely in a 64-bit double.
From the syntax perspective, while bitwise operators can be more familiar to people who come from other languages, the xor operator makes this a little bit of a harder sell. Additionally, the bit32 library is substantially richer as it provides arithmetic shift (which in languages like C you get as a byproduct of having signed types, and in languages like Java you have to use yet another operator), rotate (which is really important for hashes/cryptographic algorithms), and some convenience functions like bit32.extract that usually make bit manipulation code easier to understand.
And of course from the complexity perspective, this argues for 6 more operations and metamethods for something that you can already use bit32 library for.
So while bitwise operations have some attractions, they also have downsides and it's not clear that it justifies the cost, which is why the compatibility page explicitly says we won't support them at this time. This decision might change if we decide to implement first class integers - after all, it would indeed make sense to have bitwise operations if integers are a native type - but that's an even more complicated tradeoff wrt performance and, crucially, backwards compatibility and "sane" numeric tower, hence why we currently don't think we'll implement either.

From the performance perspective, we're already using specialized paths inside the interpreter so you aren't paying the full overhead of a function call. Bit operations are still not free, but part of the cost there is simply checking the argument types and converting between number and integer types.

In Luau the FASTCALL operations help with performance but have edge-cases where they won't exist and environments aren't always guaranteed to be safe.
For e.g when using bit32.band FASTCALL2 or FASTCALL2K will get generated
bit32.band(a, 0xFF) -- GETIMPORT, FASTCALL2K

bit32.band(a,b) -- GETIMPORT, FASTCALL2

local bit = bit32
local band = bit.band
band(a,b) -- CALL

Perhaps the bit library could receive some more optimizations similarly to how select with varargs gets optimized for commonly used numbers like bit.band(a, 0xFF)

From the behavior perspective, this RFC alludes to having the bit operators work for all numbers somehow but doesn't clarify the behavior - absent full integer support (which, again, see compatibility page for - no current plans), we'd need to have the exact same semantics as bit32 library has today, as you can't represent a 64-bit integer precisely in a 64-bit double.

This is true but I made this RFC with hopes that there'd be more freedom with bits and more specifically bit packing, I don't really think it'd be possible to add a bit packing library or functions instead.

From the syntax perspective, while bitwise operators can be more familiar to people who come from other languages, the xor operator makes this a little bit of a harder sell. Additionally, the bit32 library is substantially richer as it provides arithmetic shift (which in languages like C you get as a byproduct of having signed types, and in languages like Java you have to use yet another operator), rotate (which is really important for hashes/cryptographic algorithms), and some convenience functions like bit32.extract that usually make bit manipulation code easier to understand.

The Xor operator is usually the ^ token but that is already used by the POW operation. The other points are valid though.

bit32.band(a, 0xFF) -- GETIMPORT, FASTCALL2K

Note that GETIMPORT is not executed (assuming you mean it for bit32.band), it's just there as fallback. So effectively there's only one opcode that gets executed in this case, assuming a is a local. We might also change codegen around a little bit to move these fallback sequences outside of the common path so that they don't even take space in the CPU cache.

Not only would built-in operators be ergonomically beneficial as it is tedious to call out functions, but these built-in bitwise operators also open up the doors to applying constant folding which would additionally be a considerable optimization making bit manipulation more practical when it comes to bit-manipulation based algorithms or just plain bit-hacks.

For this I'll note that we plan to constant fold builtin calls in the future, maybe under -O2 as it has some interactions wrt unsandboxed environments. This isn't merely theoretical in that we actually have seen production code that, for example, uses math.floor in context of a fixed length for loop; when that loop is unrolled, the lack of constant folding for builtins gets in the way.


Fix api docs

What changes are proposed in this pull request?
Fix #15414
Why are the changes needed?
https://github.com/kongchen/swagger-maven-plugin says that each item of "location" must have a tag, such as
<locations>
    <location>com.github.kongchen.swagger.sample.wordnik.resource</location>.
    <location>com.github.kongchen.swagger.sample.wordnik.resource2</location>
</locations>

I tested the PR and it works for the api docs.
Does this PR introduce any user facing changes?
No

alluxio-bot, merge this please


[full-ci][k6-test] Release 7.0.0-rc.5

Release 7.0.0-rc.5

Changelog folder name is not correct.
use 7.0.0-rc.5_2024-12-10 (underscore separates version and date, date uses dashes)


Why is it not compatible with foundation-sites?

This is a great and neat project, works with angularjs and so on, beautiful. But, I wonder why is it not compatible with foundation-sites in the first place?
I made an issue a few days ago (#733) about the action sheet disapearing for no reason. In fact I was using foundation-sites scss on top of foundation-apps. I'm asking this because components are usually the same, but foundation-sites has more features.
For example, label.middle, I've to add:
label.middle {
    @include form-label-middle;
}

But I can't @include foundation-form-label or the style of most foundation-app form components will be broken... I thought it'd be compatible.
Another example, tabs (sites vs apps). With foundation-sites I could make vertical tabs, those are not available with foundation-apps. The foundation-apps markup is different, but I'm assuming it's almost the same SASS component? So why so many differences? Why are you re-inventing the wheel (or maybe you're not and I'm lost alone in the zurbness).
Can't an app have breadcrumbs? What about tables? For now I'm including:
@import 'settings';
@import 'foundation';
@import 'components/table';
@import 'components/breadcrumbs';
@import 'forms/forms';
@import 'util/util';
@include foundation-breadcrumbs;
@include foundation-table;

The weird thing is that even _settings.scss is not compatible with the one from foundation-sites (missing global-* for example).
Apart from having the grid with flexbox (which is foundation-apps default but available in foundation-sites too), I don't understand why there are so many differences.
Please could you provide more information on this subject?

I've run into a similar issue. I want to use components from Foundation Sites on Apps. Did you run into a lot of problems bringing components from Sites into Apps? Or was it only specific components that didn't work for you?
Hope we learn a solution to this soon!

It works well, I'm building with node-sass by including both foundation-sites and foundation-apps directories to the includePaths option.
For now I'm only using table, breadcrumbs and the form-middle-label mixin.
Maybe that those components will get into foundation-apps?
What are you trying to include on top of what's already available with foundation-apps?

I'll have to give that a try. I wasn't sure where I could include those files where there wouldn't be a conflict or if including any foreign components would be problematic.
I would hope that Foundation Apps gets more components like Sites. Things still feel a little limited on this release, but I think it's a good start for building responsive web apps.
I'm working on a dashboard so presenting data is a big part of it. I found that some of the components are categorized a little bit on Sites and Apps, but similar function.
Foundation Sites components that’s not in Foundation Apps

Top bar menu (I think Apps has something similar)
Responsive Navigation
Dropdown Menu (I think Apps uses action sheet)
Pagination
Breadcrumbs
Table
Progress Bar
Tooltip
Form validation (this is a big one)

You can use the action sheet for the Tooltip.
For the top bar I use a mix of title bar and menu ('d have to check).
For the rest :+1:

@gakimball I'd be glad to make a Pull request about those missing components if you need me to.

@soyuka I'd hold off on that for now, although we really appreciate the interest :)
We're in the early planning stages of Foundation for Apps 2, and we know we need to do a better job of sharing components between frameworks.
However, we want to keep the community in the loop so they can contribute, so we'll try to publish our thoughts on that soon.

+1 would love to see those
I think that the list from @marleneclayton is a good start, IMHO most of foundation-sites components could be reused, except those that really belong to a "website" (orbit, slider, flex-video).
Also, I really like what you've achieved with the action sheet that can easily be used for dropdowns, tooltips, typeahed (made a small proto and it did well) etc.
For the integration, I don't see why foundation-apps could not depend on the foundation-sites scss :).

@soyuka I'm interested in exploring this option, although it begs the question "just how many of those jQuery plugins will we be rewriting in Angular?"

Indeed @gakimball, that was also my thought while going through both docs. There is also angular-foundation, but I prefer your work, it feels more "natural". Also, angular v2 is now in beta stage.
May I ask why you build foundation-apps in the first place?

@gakimball
How heavily is jQuery used in foundation for sites?  Is it unthinkable to try to remove that dependency?
From an architecture standpoint, you shouldn't be writing core functionality in angular.  Any components shared between F4S and F4A should be part of a shared core framework.  This core framework should be javascript only with minimal dependencies.  This will enable the framework to be used by ANY javascript framework and not just F4S and F4A (#587).
F4A is already in a predicament with angular in that angular 2.0 is stated to not be backwards compatible with angular 1.0.  A ton of effort will need to be spent migrating the code to work with angular 2.0, so rather than making EVERYTHING angular, now would be a great time to figure out which code is not angular dependent and put that into the core JS framework.  The core JS framework can then be wrapped by F4A to provide an angular solution and wrapped by F4S to provide a jQuery solution.  The core JS framework can also be wrapped by others to provide similar functionality for other common web frameworks.

@soumak77 I think @zurbchris (who wrote most all of the JavaScript for Sites 6) is very interested in this idea. You can probably count on two hands the number of jQuery functions that are useful when you need to support IE9: addClass, removeClass, hasClass, extend, on/off (not just for the easier syntax, but for event namespacing also).
Over time the F4S codebase will rely on jQuery less and less, mostly for speed reasons.
I think wrapping a series of plain JavaScript plugins in jQuery/Angular is sensible, but I've always wondered: are you losing a core benefit of Angular/React/etc., which is more efficient DOM manipulation? Presumably our plain JS plugin is going to be doing its own manual DOM manipulation, and the wrapper will just be calling those methods. So is it that problematic or not? Or is there a different way to address it that I'm not thinking of?

You can do something similar to angular 1.0 (likely the same in 2.0, but haven't looked into it), where they use jqLite and allow for dropping in your own implementation if needed. This allows angular to work with jQuery without having to change any internal functionality as the drop in replacement (jQuery) is a superset of the required framework (jqLite). So if you want to use this new foundation core JS in angular, you could drop in angular.element and the framework should work. You can also drop in jQuery when using it for F4S and it should work as well.
I don't think there is a major issue here so long as the core JS is properly wrapped. So for instance with angular, you'll still want to use directives as much as possible as they are extremely powerful, but you'll need to ensure $scope.digest or $scope.apply is called in the correct locations after DOM manipulation is done via the core JS framework so the directive (and other scopes) reflect the changes.

@gakimball @zurbchris
Here's an interesting article on Angular 2 I found that relates directly to this conversation.  I would suggest reading the entire article as it mentions some good points you'll want to keep in mind when developing a plain JS UI framework.  Here are some snippets:
2.3.6 jqLite
jQuery has been supported in Angular since day one. That support isn't going away, but Angular will no longer include it's own miniature version (jqLite). It's also in line with how Angular prefers declarative over imperative (as discussed in 2.1.2).
2.1.2 Controllers, providers, and directives
One of the most common use cases in web development is creating custom pieces of elements on a page, like tabs or buttons with spinners in them. Today the web lacks a good way to separate concerns and easily manipulate the DOM. While things are on their way (see section 2.2) we've had the need for some time.
jQuery is great for controlling the DOM in a direct way. We call that an imperative model. To help developers transition to Angular it has supported that way of thinking. But Angular has at the same time tried to give us a more declarative model where we're more concerned with what, rather than how. Data binding is probably the most notable of these features as we can just use our JS data in the HTML, rather than grabbing the element and pushing in the value ourselves.

This is a great discussion! Thanks for your insight @soumak77, @gakimball, and @soyuka!
I am trying to build a dashboard with Foundation 6 Apps as my base and then integrating Rails into the app. I'm trying to see if I can just "rip" out the components that I need from Foundation 6 Sites without breaking dependencies, if any.

@marleneclayton You can rip the CSS out no problem, if you're fine writing your own JavaScript. There are some .ng- classes in the code, but I think over time we can try to make that stuff more library-agnostic.

@soyuka I would actually like flex-video in foundation-apps. I am surprised and annoyed that the two don't share UI components 100%. I feel the components from sites should at least be optional includes in apps.
This makes the choice between the two especially difficult for me, because I want the sites components but in Angular. There is Foundation Ultra, but I am implementing Foundation for a client and I don't want them to be stuck with an unofficial, immature, spin-off project that lacks documentation (and is likely at risk of becoming unmaintained).

@gakimball is it possible to follow discussions/ideas somewhere?

@soyuka We need to solidify some of our thinking before we can announce anything, but we can say Apps 2 will be built on Angular 2.
I'd like to bring people in as soon as possible to get feedback on our ideas, but we probably won't have anything solid to show for another month.

Angular 2 ?! Great News :+1: just take the time it needs. I'm sure a solid framework will came out when Angular2 & F4A are combined :+1:

@gakimball Thanks for your reply. What would be the recommended way of importing F6S components into F6A using Sass currently, and preserving my ability to upgrade? Do I just install F6S into a separate folder, and then @import certain SCSS files? I take it there would be clashes if I blindly imported everything?

@hguiney Yep, you can install the foundation-sites Bower or npm package alongside foundation-apps. In your Sass file, you'll need to selectively @import things, and then also add the @includes to print the CSS of those components. Looking at the 6 component list, you could bring in:

Top bar
Callout
Media object
Table

Or if you turn off any Apps components, you could bring in the Sites equivalent.

What is this foundation-sites vs. foundation-apps?
This is a really odd naming scheme given the continued grey area expanding between the concept of "sites" and "apps".  I'm am building an App (with Ember) yet I find myself using "sites" (with ember-cli-foundation-6-sass).

@cfator We realized this, which is why Sites and Apps will be more tightly coupled in the future. The two frameworks will share most of their CSS, and the main differentiator will be how the JavaScript is implemented. Apps will still have some special components, like it's unique grid, notifications, etc. And of course Apps will be written in Angular.

Is the grid not the same as the new flex grid from Sites?
+1 about the shared scss base components ofc.

@soyuka You'll use the two grids in tandem. So in Apps, we have .grid-frame, .grid-block and all that, and that will still exist, but the naming scheme will be different. And we'll do a better job of explaining it so it's not crazy confusing.
That grid will be used to carve up the sections of your app, and make your fixed headers and sidebars and so on. And then inside that grid (which we're calling a frame right now), you'll use the traditional 12-column grid.
We tried overloading the two core apps grid classes, .grid-block and .grid-content, with these two kinds of functionality, but the more we built with it the more of a hassle we realized it was. So now there will be two grids.
Here's a possible example. Note that .row replaces .grid-container.

Excited about version 2. It be nice to have this be basically a wrapper around Foundation for Sites with angular compatible widgets.

I'm interested in using Foundation with Ember. While it possible to use F4S, F4A definitely not. As @soumak77 mentioned earlier, it would be great if F4A was agnostic in such a way that it could be wrapped by other frameworks, such as Ember. This would enable Foundation to be even more widely used.

@gakimball - any update on a rough release estimate for Foundation Apps/Sites for Angular 2? We've started a project where we may need to work on some form of polyfill to get the Foundation JS dependancies working for us in the short term. However if a release is on the horizon that would save us a fair bit of work.

@edhatricksmith I'm no longer with ZURB, so unfortunately I couldn't tell you :< But FYI for y'alls, ZURB is hiring a senior engineer if you want to be a part of the process!

@gakimball - fair enough, thanks anyway.
Anyone else have any info?

Wow, so @gakimball and @AntJanus are both no longer with Zurb? No wonder this project died, it seemed like they were the driving force behind it...

also @zurbchris: https://github.com/zurb/foundation-sites/commit/fcb6c15e2194b29d08641405deaeccf4095e1bcb

They should really mention on the docs that one should not use foundation-apps... Last update 9 dec 2015, issues count is growing and using a specific JS (read forcing the use of) framework on a front-end framework (read css) isn't a good idea (see good comments above).

@mattgrande I had no idea about geoff leaving. I was a contractor so it was kind of understood that I'd work on this only for a short amount of time.

@AntJanus - Ahh, didn't realise you were a contractor. That makes sense.


cannot use the SDK with sandbox - error even on getting authenticated -- works ok direct via requests.

Every time I try to use the sandbox with correct client id and secrete I get a strange error on access
doing this directly with httpx or other module in python works fine but then I have to formulate all the REST commands manually and I get error.
Based on docs for sandbox I set base_url = "https://api.ingrammicro.com:443/sandbox" following your access example.
'Reason: Not Found\n'
"HTTP response headers: HTTPHeaderDict({'Date': 'Wed, 06 Mar 2024 00:52:49 "
"GMT', 'Content-Type': 'application/json', 'Content-Length': '186', "
"'Connection': 'keep-alive', 'X-Frame-Options': 'DENY', "
"'Strict-Transport-Security': 'max-age=86400', 'X-Content-Type-Options': "
''nosniff', 'Content-Security-Policy': "frame-ancestors 'none'", '
"'X-XSS-Protection': '1'})\n"
'HTTP response body: {"fault":{"faultstring":"Unable to identify proxy for '
'host: default and url: '
'\/sandbox\/oauth\/oauth20\/token","detail":{"errorcode":"messaging.adaptors.http.flow.ApplicationNotFound"}}}\n'

To obtain the access token, please use the base path: https://api.ingrammicro.com:443 for both sandbox and production environments. This should resolve the access issue. Please ensure that the base path remains the same only for the get-access-token operation. Thank you for your attention.


Call projectById query cause crash in backend

query {
  projectById(id:1){
  	title
    slug
    totalProjectUpdates
  }
}

testing this out on graphql staging -

I can successfully run this query and don't see any error - output looks good
was there anything else to test on this issue @mohammadranjbarz ?

testing this out on graphql staging -
I can successfully run this query and don't see any error - output looks good
was there anything else to test on this issue @mohammadranjbarz ?

No that's it , the playground is disabled but backend is up
I think this testing is enough


Unclear that I had to generate a tasks.json and fill in launch.json

I ran into errors debugging because I needed to generate a tasks.json file, also i needed to fill out launch.json with the path to app.dll

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

ID: 3343b35c-90c1-2e11-498d-ee1d4eb409f6
Version Independent ID: f2eda261-d4c3-c90a-1294-dfe11e55c341
Content: Getting started with .NET Core on macOS
Content Source: docs/core/tutorials/using-on-macos.md
Product: dotnet-core
GitHub Login: @bleroy
Microsoft Alias: mairaw

Thanks for your feedback @wugeorgeq. Which version of .NET Core you're using?
VS Code should create those for you when running the commands and launching the debugger.

Also, can you run this one successfully?
https://docs.microsoft.com/en-us/dotnet/core/tutorials/with-visual-studio-code

I'm having this same issue.
`.NET Core SDK (reflecting any global.json):
Version:   2.2.103
Commit:    8edbc2570a
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.13
OS Platform: Darwin
RID:         osx.10.13-x64
Base Path:   /usr/local/share/dotnet/sdk/2.2.103/
Host (useful for support):
Version: 2.2.1
Commit:  878dd11e62
.NET Core SDKs installed:
1.0.1 [/usr/local/share/dotnet/sdk]
2.2.103 [/usr/local/share/dotnet/sdk]`

I have the same issue,

using VS Code Version 1.30.1 (1.30.1)
with .NET Core SKD version 2.2.104

The launch.json is created but with a placeholder for the "program" entry of "configurations.
Had to infer from this thread that the correct line should be
            "program": "${workspaceFolder}/app/bin/Debug/netcoreapp2.2/app.dll",

Thanks for the information everyone! We'll look into this topic more closely as we prepare for .NET Core 3.0 release.

@BillWagner Your PR #16349 has a Fixes #9490 comment but this issue didn't get closed automatically.  Should it be closed?

@tdykstra Yes, this should be closed. I'll close now.