[Feature Request]: Review Section

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
There should be Review Section on landing page and also in aboutUs page..
Use Case
other customer canreview the services that you provide..
Benefits
New Customer ca get easly idea about your services..
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

/assign

@Meetpidev, proceed.

@jeevan10017 review PR..

@GAVINESHWAR Please Review PR


Slim 873 implement get configuration object request

All is well.

When new pages are added like "GetConfigurationObject.md" and "GetConfigurationObjectResponse.md", update "SUMMARY.md" as well to have them included in the index, and to make sure the links in GitBook display a html rendering of the markdown sources.

All is well.


Implement semantic cache

That's a feature that already exists in langchain and will be beneficial to save costs.  The idea will be to ported from phyton to c#
https://github.com/zilliztech/GPTCache
https://python.langchain.com/docs/integrations/llms/llm_caching/
https://www.mongodb.com/developer/products/atlas/advanced-rag-langchain-mongodb/

Be able to save all the queries together with llm responses in some database and try to fetch it first from there,  if not then call the LLM,  and have some parameters to invalidate or update cache from time to time.

@markwallace-microsoft, going to assign this to @dmytrostruk since this is one of the samples he's working on using filters.

Also assigning @eavanvalkenburg since he was working on filters for Python

hello @dmytrostruk is there any progress on this feature?  Thanks

Example for Semantic Caching in .NET is here: https://github.com/microsoft/semantic-kernel/blob/main/dotnet/samples/Concepts/Caching/SemanticCachingWithFilters.cs

Nice,  we are going to take a look.  Thanks

Removing the .Net tag, since the sample exists. Leaving python as we haven't completed this yet.

Hi! Any news on the Python version?


Add more mutable iterator methods

feat: ✨ Add a new method called indexed_iter_mut

@becheran What's your process for publishing? Do you publish periodically after a certain number of pull requests? Just curious, since it would be cool to start using some of these features now!

@pcbowers just released v0.13.0. The process right now is that if I feel that there are enough new changes that are worth releasing I will create a new release. Thanks again for the PR!


Measure with exact measurement when stretch is defined

An optimization which will measure with EXACTLY when possible given stretch alignment. Text measurement specifically is much more performant when it knows the exact measurement up front and given that stretch alignment is the default this has quite a big performance impact on certain types of layouts.

I'm assuming my environment is set up differently than the person who last generated the code. That is why so many lines are whitespace removal.

@rigdern Would love it if you took a look

@emilsjolander Where does the performance win come from? Do you have an example layout?
In case you weren't aware, you can view the changes while ignoring whitespace by adding ?w=1 to the end of the URL. For example: https://github.com/facebook/css-layout/pull/193/files?w=1. However, I don't think you can write or view comments in this view :(

I tried to describe it in the PR description but I'll expand on it a bit.
In a simple layout such as
<View style={{width: 1000}}>
  <Text>zZzZ</Text>
  <Text>zZzZzZzZ</Text>
  <Text>zZzZzZzZzZzZ</Text>
</View>

View defaults to alignItems: 'stretch' which previous to this diff would initially measure children with AT_MOST width. Not only is this wrong as they should be measured with an exact width due to there alignment it is also bad for performance as the text itself needs to figure out how big it is instead of being told a size.

@emilsjolander Sorry for the delay. I tested this change today in our app and didn't notice any issues.
Your change looks good to me.

Thanks Adam!
On Tue, 7 Jun 2016 at 23:35, Adam Comella<EMAIL_ADDRESS>wrote:

@emilsjolander https://github.com/emilsjolander Sorry for the delay. I
tested this change today in our app and didn't notice any issues.
Your change looks good to me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/css-layout/pull/193#issuecomment-224478929,
or mute the thread
https://github.com/notifications/unsubscribe/ABdIpG-GDc3bUTJjTvxucFyBt20h45xjks5qJjiHgaJpZM4IsuJM
.

Looks good with nits fixed.


create error message and handle the case where y input is an integer

Right now if the user is referring to y-var in train() using an integer, it does not give a clear error message. This is slightly confusing, as we accept so many different ways to use integers for x-vars.

this is fixed.


isLast and isAfterLast checking removed for TYPE_FORWARD_ONLY ResultSet

Support for the isLast and isAfterLast methods are optional and up to the vendor for the ResultSets of type TYPE_FORWARD_ONLY.

@s5r3, thank you. I will merge and make an updated release.

Fix for this is available. Repo updated, maven updated but may take a while to show up in maven central.


✨ Add API Server config for RapiDoc

Signed-off-by: Alexandre Franke<EMAIL_ADDRESS>

The “before” screenshot disagrees with you though.

The before screenshot didn't get the memo sent out 2 years ago 😇


Vuln advisories and signing binaries

Added further suggestions to include a requirement for a project to:

to issue vulnerability advisories
sign executable binaries

BTW: In the future, please split up unrelated proposals, it makes things easier to track.
I'll accept.  The problem with signed executables is that they're useless unless the signature is checked AND users will reject executables with bad signatures.  So it's not a crazy idea, but I'd like to hear many more people crying for it specifically.

noted.
On Thu, 24 Sep 2015 at 04:11 David A. Wheeler<EMAIL_ADDRESS>wrote:

BTW: In the future, please split up unrelated proposals, it makes things
easier to track.
I'll accept. The problem with signed executables is that they're useless
unless the signature is checked AND users will reject executables with bad
signatures. So it's not a crazy idea, but I'd like to hear many more people
crying for it specifically.
—
Reply to this email directly or view it on GitHub
https://github.com/linuxfoundation/cii-best-practices-badge/pull/31#issuecomment-142684304
.


[GUI] Paging is ignored when user clicks device list icon

Steps:

Display devices on the map

Click on the device list icon

If the user, instead of clicking on the icon, click on the bar, the pagination is done:


Using maven-jlink-plugin with Dropwizard 1.3.0rc5 fails due to transitive dependencies

Tried building the dropwizard-example repo with the maven-jlink-plugin out of curiosity and it fails with:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink (default-jlink) on project dropwizard-example: The given dependency ~/.m2/repository/org/jboss/spec/javax/transaction/jboss-transaction-api_1.2_spec/1.0.1.Final/jboss-transaction-api_1.2_spec-1.0.1.Final.jar does not have a module-info.java file. So it can't be linked. -> [Help 1]
This seems to be a transitive dependency:
mvn dependency:tree
[INFO] +- io.dropwizard:dropwizard-hibernate:jar:1.3.0-rc5-SNAPSHOT:compile
[INFO] |  +- io.dropwizard:dropwizard-db:jar:1.3.0-rc5-SNAPSHOT:compile
[INFO] |  |  \- org.apache.tomcat:tomcat-jdbc:jar:8.5.24:compile
[INFO] |  |     \- org.apache.tomcat:tomcat-juli:jar:8.5.24:compile
[INFO] |  +- com.fasterxml.jackson.datatype:jackson-datatype-hibernate5:jar:2.9.3:compile
[INFO] |  +- com.github.arteam.jadira:usertype.core:jar:6.0.1.GA-jdk9:compile
[INFO] |  |  +- org.hibernate:hibernate-entitymanager:jar:5.2.1.Final:compile
[INFO] |  |  \- com.github.arteam.jadira:usertype.spi:jar:6.0.1.GA-jdk9:compile
[INFO] |  \- org.hibernate:hibernate-core:jar:5.2.12.Final:compile
[INFO] |     +- org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final:compile
[INFO] |     +- antlr:antlr:jar:2.7.7:compile
[INFO] |     +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.1.Final:compile

Which seems to have fixed the problem and made a new release with the tag jboss-transaction-api_1.2_spec-1.1.1.Final.
Is this something dropwizard want to fix before making an official 1.3.0 release?

Created an issue in the hibernate issue tracker for this.

We could exclude jboss-transaction-api_1.2_spec from the Hibernate dependency and declare a new version with the Automatic-Module-Name tag in the manifest file. I think we can wait for a response from the Hibernate guys. If they won't make a new release, we will fix it on our side.


10.17.0 copy fails with --include-directory-stub=true

Which version of the AzCopy was used?
10.17.0
Which platform are you using? (ex: Windows, Mac, Linux)
Mac and Windows
What command did you run?
azcopy copy "https://srscwrflustrehsm.blob.core.windows.net/wrfhsm" "https://jmstoragescus.blob.core.windows.net/wrfhsm" --overwrite=prompt --s2s-preserve-access-tier=true --include-directory-stub=true --recursive --log-level=INFO
What problem was encountered?
The copy started then failed with following message:
2.3 %, 188 Done, 0 Failed, 7188 Pending, 0 Skipped, 7376 Total, 2-sec Throughput (Mb/s): 75.7227  panic: folder https://jmstoragescus.blob.core.windows.net/wrfhsm/shared/build/aws/dist/awscli/botocore/data/personalize was not registered when properties persistence occurred

goroutine 7041 [running]:
github.com/Azure/azure-storage-azcopy/v10/ste.(*jpptFolderTracker).ShouldSetProperties(0xc001d640a0, {0xc0017d9f10, 0x69}, 0x2, {0x100c8aa80, 0xc000972000})
	/Users/runner/work/1/s/ste/folderCreationTracker.go:126 +0x2ff
github.com/Azure/azure-storage-azcopy/v10/ste.(*blobFolderSender).EnsureFolderExists(0xc001512400)
	/Users/runner/work/1/s/ste/sender-blobFolders.go:124 +0x2ba
github.com/Azure/azure-storage-azcopy/v10/ste.anyToRemote_folder({_, _}, {{0xa9cefaa2, 0xaf0c, 0xba4c, {0x70, 0x68, 0xa4, 0xdf, 0x43, ...}}, ...}, ...)
	/Users/runner/work/1/s/ste/xfer-anyToRemote-folder.go:70 +0x233
github.com/Azure/azure-storage-azcopy/v10/ste.anyToRemote({0x100c9f8e0, 0xc00111b960}, {0x100c8a7c0, 0xc000f2e100}, {0x135b1d880, 0xc00081a000}, 0xc0026c0e80?, 0x2e?)
	/Users/runner/work/1/s/ste/xfer-anyToRemote-file.go:183 +0x318
github.com/Azure/azure-storage-azcopy/v10/ste.parameterizeSend.func1({0x100c9f8e0?, 0xc00111b960?}, {0x100c8a7c0?, 0xc000f2e100?}, {0x135b1d880?, 0xc00081a000?})
	/Users/runner/work/1/s/ste/xfer.go:77 +0x44
github.com/Azure/azure-storage-azcopy/v10/ste.(*jobPartMgr).StartJobXfer(0x10129fe60?, {0x100c9f8e0?, 0xc00111b960?})
	/Users/runner/work/1/s/ste/mgr-JobPartMgr.go:720 +0x50
github.com/Azure/azure-storage-azcopy/v10/ste.(*jobPartTransferMgr).StartJobXfer(0xc00111b960?)
	/Users/runner/work/1/s/ste/mgr-JobPartTransferMgr.go:237 +0x32
github.com/Azure/azure-storage-azcopy/v10/ste.(*jobMgr).transferProcessor.func1({0x100c9f8e0, 0xc00111b960})
	/Users/runner/work/1/s/ste/mgr-JobMgr.go:1020 +0x1b9
github.com/Azure/azure-storage-azcopy/v10/ste.(*jobMgr).transferProcessor(0xc000752800, 0x0?)
	/Users/runner/work/1/s/ste/mgr-JobMgr.go:1032 +0xbd
created by github.com/Azure/azure-storage-azcopy/v10/ste.NewJobMgr
	/Users/runner/work/1/s/ste/mgr-JobMgr.go:202 +0xc37

How can we reproduce the problem in the simplest way?
The source blob container has 0B file with metadata including hdi_isfolder:true that requires the --include-directory-stub=true flag.  This has been replicated on Mac and Windows clients running 10.17.0.  The same command works with 10.16.2 on both Mac and Windows.
Have you found a mitigation/solution?
Use 10.16.2 instead
a9cefaa2-af0c-ba4c-7068-a4df437e1c6b.log

I forgot to note that if i run the same azcopy command without --include-directory-stub=true using 10.17.0 it does not crash but does not copy the metadata stub files

I forgot to note that if i run the same azcopy command without --include-directory-stub=true using 10.17.0 it does not crash (but also does not copy the metadata stub files)

Correct. This appears to be related to the folder persistence manager.

Use 10.16.2 instead

We made some changes to the way folder persistence works in 10.17.0, so that makes sense why this regression would appear.

I'll do some investigation today and try to repro/fix.


feat(dashboard): enrich portfolio css

scaffold out header css

:tada: This PR is included in version 1.6.0 :tada:
The release is available on:

GitHub release
v1.6.0

Your semantic-release bot :package::rocket:


error when "TASK [geerlingguy.drupal : Install dependencies with composer require (this may take a while).]"

Issue Type

Bug Report

Your Environment
Vagrant 2.1.5
VirtualBox 5.2.10_Ubuntur121806
ansible 2.7.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/burak/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.15rc1 (default, Apr 15 2018, 21:51:34) [GCC 7.3.0]

content of my config.yml
vagrant_synced_folder_default_type: nfs
vagrant_gui: false

# If you need to run multiple instances of Drupal VM, set a unique hostname,
# machine name, and IP address for each instance.
vagrant_hostname: drupalvm.local
vagrant_machine_name: drupalvmlocal
vagrant_ip: <IP_ADDRESS>

# A list of synced folders, with the keys 'local_path', 'destination', and
# a 'type' of [nfs|rsync|smb] (leave empty for slow native shares). See
# http://docs.drupalvm.com/en/latest/getting-started/syncing-folders/ for more.
vagrant_synced_folders:
  # The first synced folder will be used for the default Drupal installation, if
  # any of the build_* settings are 'true'. By default the folder is set to
  # the drupal-vm folder.
  - local_path: .
    destination: /var/www/drupalvm
    type: nfs
    create: true

# Memory and CPU to use for this VM.
vagrant_memory: 2048
vagrant_cpus: 2

drupal_build_composer_project: true
drupal_install_site: true

# Comment out any extra utilities you don't want to install. If you don't want
# to install *any* extras, set this value to an empty set, e.g. `[]`.
installed_extras:
  - adminer
  # - blackfire
  - drupalconsole
  - drush
  # - elasticsearch
  # - java
  - mailhog
  # - memcached
  # - newrelic
  - nodejs
  - pimpmylog
  # - redis
  # - ruby
  # - selenium
  # - solr
  # - tideways
  - upload-progress
  # - varnish
  - xdebug
  # - xhprof # use `tideways` if you're installing PHP 7+

# PHP Configuration. Currently-supported versions: 5.6, 7.0, 7.1, 7.2.
# See version-specific notes: http://docs.drupalvm.com/en/latest/configurations/php/
php_version: "7.2"

php_packages_extra:
  - php-bcmath #this is needed for commerce/intl

Your OS

Linux (Ubuntu 18.04 - 4.15.0-36-generic)

Full console output
https://gist.github.com/kburakozdemir/37bb1d8d486aa84216ebcb77dc43301e
Don't have the full output console so I pasted the error only
Summary
when vagrant up during installation exactly while
TASK [geerlingguy.drupal : Install dependencies with composer require (this may take a while).] ***
the error appears.
Few days ago it was working. after searching issues etc., I tried different options (for manual debug :) )
I tried with:

master branch (no way)
checking out tags/4.9.0 (no way)
I also tried with  (no way)

drupal_composer_project_package: "drupal-composer/drupal-project:8.x-dev"
#removed --prefer-dist to try
drupal_composer_project_options: "--stability dev --no-interaction"

I tried the combinations of the above with a clean vagrant up and they all failed.

then i tried with this configuration added to my config.yml (this means I removed devel module to install and enabled defaultly).

drupal_composer_dependencies: []
drupal_enable_modules: []

and opps! it worked! I took me 6 hours to find out! :)
I think the reason is the devel module (defaultly installed and enabled), however I didn't inquiry the reason behind the devel module.
As we know the default dvm config has:
drupal_composer_dependencies:
  - "drupal/devel:1.x-dev"
drupal_enable_modules: [ 'devel' ]

I can confirm this. I've had the same issue.

Seems like the same as #1743

Does look the same—I've just committed what I hope is the fix. It seems that maybe the 1.x-dev tag is no longer available through Packagist :-O


[Bug] Unknown Guild

I couldn't find out where this Error is thrown, but its impacting the announcement sending

Associate with the pr #191


FullWidth Modal

Add new 'fullWidth' props to modal component to open modal on entire screen

Hi Quentin,
Unfortunately we don't allow users to make changes to the base UX and UI of the library a modal with full width currently isn't supported.
All the best
Sajad


Env Variables created for each of the ports in addition to env variables...

... for  port ranges, regression from #1834
Closes #9900
Signed-off-by: Srini Brahmaroutu<EMAIL_ADDRESS>

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
git commit --amend -s --no-edit && git push -f

LGTM

We should probably add a few integration tests to enforce the environment variables for a container or it maybe pretty easy to write a unit test for this method.

Yup, +1 to tests.

@crosbymichael @LK4D4 Thanks for the review. I will add tests shortly. One scenario that I am not very convinced about is that env for range may show differently, for example
docker run --name backend -p 7101:7101 -p 7102:7102 -p 7103-7105:7103-7105
<we get normal ENV variables for all 5 ports with this fix but the range env variables will look like below since we detect the continuity in allocation>
BACKEND_PORT_7101_TCP_PORT_END=7105
BACKEND_PORT_7101_TCP_PORT_START=7101

Please see that I added a unit test for check all env variables.

LGTM

@LK4D4 Anything else to add to this or can we merge?

Thanks for the tests!


Implement the functionality of legacy CC Search.

Is your feature request related to a problem? Please describe.
We would like to decommission legacy CC Search (https://search.creativecommons.org/) as soon as possible but it does offer some functionality that the new CC Search does not – the ability to search CC licensed works that are not images. We would like to integrate that functionality into the current site.
Describe the solution you'd like

A search bar that takes a search query and provides the user with a list of providers to select from. When the user searches, the site should redirect the user to the search results page of that provider with the query already filled in.
We should only show providers that provide content types that are not images. For images, we want them to use the primary CC Search experience.
It should be really clear that this is not the primary CC Search experience. One way to do this is to put this functionality in a separate page linked to from the top nav. Feel free to propose another idea.

Additional context
Since this is a major addition, the implementation needs product input from CC staff. Please post your design here before implementing the full functionality so that we can give you feedback.

@kgodey I'm moving this to the Parking Lot, since we may simply prioritize integrations with those collections directly through (new) CC Search instead. I'll add those to Catalog Pipeline for further research. Definitely move back if you have a different view on this.

@annatuma I don't think we can integrate stuff like Google Images into CC Search. I think we need some sort of plan to shut down old CC Search; we shouldn't keep maintaining it forever. I'm worried moving it into the Parking Lot will mean we forget about it.

I would like to take it up.
Thank you.

hey @kgodey I think that i have skills that  can help with this issue can i work on it ?

Hi! @akmadian @kgodey Can i work on this issue, if no one is working on this !

I think we should run this by @annatuma, this would be a significant UI and functionality change.

Hey folks, apologies for the delayed response here. I've gone ahead and blocked this one. This will require thoughtful internal discussion, and hasn't been prioritized to date because of other work on (new) CC Search.
@genedy377 @abhisheknaiidu please look for other "help wanted" issues to contribute to.

We're currently mocking up what this functionality could look like on new search. Under consideration is content type below search bar, content type in navbar, further options to be discussed and considered.
Working notes, regarding Sources:
Europeana image integration is forthcoming. We can include them on audio & video pages on CC Search with filters in place for "TYPE"
Sample query from Old Search:
https://www.europeana.eu/en/search?query=dogs AND RIGHTS%3A*creative* AND NOT RIGHTS%3A*nc* AND NOT RIGHTS%3A*nd*
Sample query with video filter:
https://www.europeana.eu/en/search?page=1&qf=TYPE%3A"VIDEO"&query=dogs AND RIGHTS%3A*creative* AND NOT RIGHTS%3A*nc* AND NOT RIGHTS%3A*nd*&view=undefined
Sample query with audio filter:
https://www.europeana.eu/en/search?page=1&qf=TYPE%3A"SOUND"&query=dogs AND RIGHTS%3A*creative* AND NOT RIGHTS%3A*nc* AND NOT RIGHTS%3A*nd*&view=undefined
Flickr is indexed by CC Search
Google (web) currently filters by "as_rights"
Sample search query:
https://www.google.com/search?as_rights=(cc_publicdomain|cc_attribute|cc_sharealike).-(cc_noncommercial|cc_nonderived)&q=dogs&hl=
We may include information on how to filter on Google by resource rights on a help page on CC Search, but this likely won't be built into the CC Search UI prominently.
Google Images will not be indexed by CC Search. At present, similar to Google (web), we may reference how to search Google Images by open content, but won't support it in the UI.
Jamendo have changed their search functionality, so the current experience linked from Old Search doesn't work. Assuming we can figure out how to filter by CC-licensed music again, we'd include this on an Audio page.
Open Clip Art Library will hopefully be indexed on CC Search as an image source (https://github.com/creativecommons/cccatalog/issues/169). Until then, we may include them in a resource list of non-indexed image providers, but this would be secondary to UI support for video/audio from old Search.
SpinXPress is offline.
Wikimedia Commons as a source has both audio and video available that we'd like to allow users to search, respectively. We'd need to add the parameter "filetype" for each.
Sample audio search:
https://commons.wikimedia.org/w/index.php?sort=relevance&search=dogs+filetype%3Aaudio&title=Special%3ASearch&profile=advanced&fulltext=1&advancedSearch-current={"fields"%3A{"filetype"%3A"audio"}}&ns0=1&ns6=1&ns14=1
Sample video search:
https://commons.wikimedia.org/w/index.php?sort=relevance&search=dogs+filetype%3Avideo&title=Special%3ASearch&profile=advanced&fulltext=1&advancedSearch-current={"fields"%3A{"filetype"%3A"video"}}&ns0=1&ns6=1&ns14=1
YouTube won't be indexed in the long run, most likely, similar to Google Images. In the short term we can support this source in a "non-indexed" UI for video. If/when we do index video sources, we'll need to transfer this to either a resource page (like Google Images) or find another way to support pre-filtered search for YouTube.
Sample query:
https://www.youtube.com/results?search_query=dogs%2Ccreativecommons
Pixabay no longer supports CC licenses for content, and won't be indexed on CC Search for images.
ccMixter will be added to the queue for audio indexing on CC Search. In the interim, they should be supported on the audio meta search UI.
Sample search query:
http://ccmixter.org/api/query?datasource=uploads&search_type=all&sort=rank&search=dogs&lic=by,sa,s,splus,pd,zero
SoundCloud is in the queue for audio indexing on CC Search. In the interim, they should be supported on the audio meta search UI.
Sample query:
https://soundcloud.com/search/sounds?q=dogs&filter.license=to_modify_commercially
Filters include "to modify commercially" and "to share commercially" so we need to ensure we map to those filters depending on the filters set in our own UI.
In summary, we plan to support the following sources for meta search of audio and video, until we're able to index those content types:
Audio meta search
Europeana
Wikimedia Commons
Jamendo
ccMixter
SoundCloud
Video meta search
Europeana
Wikimedia Commons
YouTube

Start with a fresh meta ticket for this: https://github.com/creativecommons/cccatalog-frontend/issues/921 and two sub tickets to tackle each addition.
Closing this one out.


Cannot download excel sheet in forge server

i made the changes on appServiceProvider
    if ($this->app->environment('production')) {
        URL::forceScheme('https');
        $this->app['request']->server->set('HTTPS', true);
    }

and still getting forbidden

Same here. only on Forge server


Deleted lots confuses app

Some lots were deleted right before the sale went live, and now the "jump to current lot" view is pointing to the wrong lot.

closing as dupe of #1793


SES: SendRawEmailMessage fails to deliver to Bcc when bcc address is set through Destinations property

email-2010-12-01.normal: Fixed what looks like incorrect mapping type Destinations, misspelled from Destination, which is the property that actually contains the To:, CC:, and BCC: addresses mentioned in the comment. Without this, any consumer fails to deliver its email to the BCC as the Destination header in the email message does not contain the appropriate recipient type (ToAddresses, CCAddresses and BccAddresses)
SimpleEmail: Added simple integration test to verify that the change to the template fixes the issue.

Unfortunately, the change you are suggesting is a breaking change (an existing property is being removed), as well as a deviation from the service specification.
To achieve what you are attempting, leave the Destinations field empty and populate MailMessage.To and MailMessage.Bcc collections with the destination emails. This is the officially recommended approach.

I understand, I actually ran into the same issue described in the same post and the next post by jyotik in response to JustinC@AWS, and I found the Destination approach, which I tried to fix, as leaving the Destinations field empty and populating the To, CC and Bcc delivers email to all but Bcc.
Looks like I should first fix the original problem and work my way there. Anyway, thanks for the feedback!


Remove FOUT bold headings

Upon loading some headings are bold first then morphed to thinner font weight. Need to investigate

Looks like by default browser loads font-weight: bold for headings. And then CSS get reapplied afterwards. Could be the critical CSS doesn't contain the final headings font-weight.


 The failure stems from the account's company name appearing in the user menu button at the top of the page -- that issue will be handled separately, but this fixes the test in the meantime by searching for the company name only in the billing contact summary section on the billing page.
Changes  🔄

Fix billing-contact.spec.ts failure

How to test 🧪
We can rely on CI for this
As an Author I have considered 🤔
Check all that apply

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[ ] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

Commit message and pull request title format standards

Note: Remove this section before opening the pull request
Make sure your PR title and commit message on squash and merge are as shown below

<commit type>: [JIRA-ticket-number] - <description>
Commit Types:

feat: New feature for the user (not a part of the code, or ci, ...).
fix: Bugfix for the user (not a fix to build something, ...).
change: Modifying an existing visual UI instance. Such as a component or a feature.
refactor: Restructuring existing code without changing its external behavior or visual UI. Typically to improve readability, maintainability, and performance.
test: New tests or changes to existing tests. Does not change the production code.
upcoming: A new feature that is in progress, not visible to users yet, and usually behind a feature flag.

Example: feat: [M3-1234] - Allow user to view their login history

Thanks for the fix, Joe! This change looks good, passes locally.
Can we create a quick M3 ticket for this to make it trackable, especially in light of what we were discussing this morning about the changes FE will need to make as a result of the API change? Even copy and pasting what you have for the PR description would be fine.

Absolutely -- I really should be doing this as a matter of habit anyway! Created M3-7737 👍 (feel free to link that to any other tickets that might make sense from a Parent/Child dev perspective)


Fix nextpnr interchange installed device

The installed devices do miss patches information, relevant for constraints and LUTs definition.
This PR installs the correct devices and also removes the symbiflow-yosys run dependency package which should not be needed.

If you're going to change that FIXME @acomodi also please unify the tags in commit messages.

Done

@acomodi I missed the fact that if the package doesn't require symbiflow-yosys anymore then it doesn't need to wait for it in CI. So remove also this line from the workflow file with the requirements/run change: https://github.com/hdl/conda-eda/blob/277f77b52db710cfcfed5b9522cb09597a5867c1/.github/workflows/build-packages.yml#L367
After that I will merge the PR as none of these latest changes can cause a CI failure.


Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@directus/update-check' imported from /directus/cli.js

Describe the Bug
Hello Guys,
I wanted to add the extensions to my custom Dockerfile. But when the container is starting up, I always get an error in the logs.
To Reproduce
Follow
Follow https://github.com/bcc-code/directus-schema-sync?tab=readme-ov-file#install
Node.js v18.18.2
node:internal/errors:496
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@directus/update-check' imported from /directus/cli.js
    at new NodeError (node:internal/errors:405:5)
    at packageResolve (node:internal/modules/esm/resolve:890:9)
    at moduleResolve (node:internal/modules/esm/resolve:939:20)
    at defaultResolve (node:internal/modules/esm/resolve:1132:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
    at link (node:internal/modules/esm/module_job:76:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v18.18.2

Any Idea what is going on?
Version
10.8.2
Installed Extension Via
Docker file

Add to use pnpm instead of npm ... problem solved :)


docs: fix broken links

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

docs/Explore Algorithms/Deep Learning/Distributed Training.md
97
100
100
link
:white_check_mark:

docs/Explore Algorithms/Deep Learning/Getting Started.md
100
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx


Bug Report: Installed WSL distributions incorrectly detected

Environment
Windows build number: 10.0.18362.175
Windows Terminal version (if applicable): from Windows Store

Any other software?
WSL with following distributions (as reported by 'wsl.exe --list'):

- Debian (Default)
- openSUSE-42
- Ubuntu
- kali-linux

Steps to reproduce
Install and run Windows Terminal from Windows Store.
Expected behavior
Menu contains an entry for each of the installed WSL Distros.
Actual behavior
Menu contains an entry for Ubuntu 18.04 WSL Distro, which is not installed.

I thought Terminal can't auto-detect distros at present, but I can be wrong.

Terminal only auto-detects distributions the first ever time you launch it. #754 will cover a bit of fixing that.


'expo-cli' is not recognized as an internal or external command,

I whan to try this demo but im stuck on this error.
yarn start
yarn run v1.22.1
$ expo start
'expo-cli' is not recognized as an internal or external command,
operable program or batch file.
This command requires Expo CLI.
Do you want to install it globally [Y/n]? Y
Installing the package 'expo-cli'...
Expo CLI installed. You can run expo --help for instructions.
'expo-cli' is not recognized as an internal or external command,
operable program or batch file.
This command requires Expo CLI.
Do you want to install it globally [Y/n]? n
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

There are some bug after manual install npm -i expo-cli -g it worked


12 transfer steem and sbd to savings balance

Closes #12

Closed this PR. Realised that the branch from from another branch and not master. fixing now


Allow to add values in form's textfield Validation pattern

Problem you would like to solve
I would like to extend the list of "validation pattern" and add some other values on top of "mail" and "phone", for example "fiscalCode", ecc..
Proposed solution
Allow to edit the list adding new values or expose the list as editable configuration file.
Alternatives considered
We are using a convention setting "Custom" as validation pattern and defining a list of known values for the field "Custom Regular Expression" we can interpret.
If it's a known value, we apply the relevant regex, otherwise we'll apply the one defined in the field.

Additional context
No response

@pinussilvestrus @Skaiir 👀


Missing Data For Weapons

Everything looks pretty good!
The only part I've not managed to see,: http://mhrise.mhrice.info/weapon/GreatSword_024.html You've got the cost to craft/buy tags, but the buy cost isn't specified anywhere.
The price for crafting is 66% of the "base_val" cost which you're showing, but the 12k cost for buying the item isn't shown.
I can't see where this is handled though.
On the site - you're showing the forge vs upgrade item costs where relevant but not the price.
For the first in the tree, you're showing forge price + materials and also just price with no materials but that's not clearly specified either.
Hoping you can help and clarify? :)
weapon keys: ['base_data', 'product', 'change', 'process', 'tree', 'name', 'explain']
Product being the buying info and process being the upgrade?

I have updated the website. The base_val is the cost for upgrading, and the cost for crafting from scratch ("Forge") is 1.5 * base_cost. The buying cost is buy_val. Btw, the particular weapon you linked cannot be bought by just money in game, so it has buy_val = 0 and isn't shown on the page.
product forging. process is upgrading. There is no dedicated "buying" section because that's using only money and doesn't have much else info.

I am closing this as I think the question has been answered. Feel free to reopen if there is still something unclear


Add an example on how to use

Can you please add an simple example on how the options must be structured to show a simple sunburst chart:
requirejs(["src/js/sunburst"], function(Sunburst) {
	var sunburst = new Sunburst('#sunburst', {
		data: {}
	});
});

I'm currently looking into different existing implementations and I'm curious about yours! Thanks!

Hi mojoaxel,
Thanks for pointing this out. I've now added a README with some documentation in it.

Thx!


gRPC async server looses track of _futures

Hi MLServer -
To start off, this is an awesome tool and the team has impressive work to get to this point.
I'm currently using MLServer in a high-throughput, low-latency system where we use gRPC to perform inferences. We have added an asynchronous capability into our inference client which sends many requests to the gRPC server at once (typically about 25). We have a timeout set on our client and we first started seeing a number of DEADLINE_EXCEEDED responses and I started to look into the model servers themselves to figure out why the server had started to exceed deadlines (we hadn't experienced this very often in the past) and it looks like the process loop is actually being restarted due messages being lost.
We see the following traceback:
2024-03-28 19:56:42,015 [mlserver.parallel] ERROR - Response processing loop crashed. Restarting the loop...
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/mlserver/parallel/dispatcher.py", line 186, in _process_responses_cb
    process_responses.result()
  File "/usr/local/lib/python3.10/site-packages/mlserver/parallel/dispatcher.py", line 207, in _process_responses
    self._async_responses.resolve(response)
  File "/usr/local/lib/python3.10/site-packages/mlserver/parallel/dispatcher.py", line 102, in resolve
    future = self._futures[message_id]
KeyError: 'cea95af0-859f-413a-a033-dfbe51e96c05'

where the dispatcher is trying to check on a given message, but it's lost.
^ once this error occurs once, all of the rest of our parallel inference requests fail with the same exception (different message_id obviously).
I took a look at the source code and it looks like when the process_response.result() is called, the logic has a blanket exception for anything that isnt an asyncio.CancelledError and assume that the process loop has crashed, so it restarts it by scheduling a new task, but it's not immediately clear (to me, at least) if this is really what should be happening. I don't see any signals from the server that the processing loop actually crashed - it just seems to be confused about which message its supposed to be getting.
As a note about our system set up, we have these deployed into Kubernetes (so is our client app) as a deployment with between 10-15 pods at any given time with environment variable MLSERVER_PARALLEL_WORKERS=16.
We are also using a grpc.aio.insecure_channel(server) pattern to manage the gRPC interactions on the client side.

hello, I had this problem too. I'd like to ask you if you've solved this problem yet?

I'd like to ask you if you've solved this problem yet? Thanks.

Hi @ShengJinhao -- Thanks for bringing this up. I will assign this issue to myself and have a look at the underlying problem.
Do you have a reproducible example you can share with me regarding this behavior?

你好@ShengJinhao-- 感谢您提出这个问题。我会把这个问题分配给我自己，并看看根本问题是什么。
关于此行为，您有一个可以与我分享的可重现的例子吗？

Yes. But how should I share it with you? The problem I encountered is this: after I sent a large number of requests, I could receive them at first, but then I couldn't receive them at all, and I checked the logs and found the same problem as above.


Particle Actions

Would let players spawn particles via action, however we may have to impose some serious limits to prevent lagging. Perhaps a limit of 5,000 particles / second?

Pretty much completed!


Suggestions on AppBundler

First off, I want to say "thank-you" for doing this.  Appbundler.jl seems like a huge step for the Julia community: being able to distribute double-clickable applications is a big deal, and without this tool, I wouldn't know where to begin to start tackling this issue.  The fact that you've tried to do this for MacOS, Windows, and Linux is even more impressive!
I realize that this is not the final polished version, and it is really a first draft, but I wanted to give some feedback on the documentation that would allow Appbundler to be more accessible to the Julia community at large.

Could you explain the recipes in more detail?  What are they for?  How do they work?  When should I use them, and how do I use them?

I found this example confusing: "bundle_app(MacOS(:x86_64), APP_DIR, "$BUILD_DIR/gtkapp-x64.app")".  I'm no MacOS/Unix command-line expert (I'm guessing most of the incoming Julia users are not), but when I read this, I assumed the $BUILD_DIR was some sort of special variable.  I initially tried something like this:

AppBundler.bundle_app(MacOS(:aarch64), "/Users/…/Development/AppBuilderVersion/Trichromacy", "$BUILD_DIR/Trichromacy.app")

…and got this as an error:
ERROR: UndefVarError: `BUILD_DIR` not defined`

Of course, this works:
AppBundler.bundle_app(MacOS(:aarch64), "/Users/…/Development/Trichromacy/AppBuilderVersion/Trichromacy", "/Users/…/Development/Trichromacy/AppBuilderVersion/Trichromacy.app")

Is $BUILD_DIR a variable that we should know about?  Is it part of AppBundler, but isn't working for some reason?  If not, maybe it would be easier to show an example like this:
AppBundler.bundle_app(MacOS(:aarch64), "/Users/…/Development/myAppProject/myApp", "/Users/…/Development/myAppProject/myApp.app")

Take home message: When in doubt, pretend we are dumb!
MacOS

Many of us have never had to codesign an app before (and I've been coding on Macs since 1993!  I miss Codewarrior…).  Maybe include a link to this Youtube video on how to make a certificate:

https://www.youtube.com/watch?v=OpR9-onRZko

Also, feel free to include my command line example for codesigning:

sudo codesign --verbose --deep --force --sign "MyCertificate" --options runtime --entitlements "/Users/…/Development/myAppProject/myApp.app/Contents/MacOS/Resources/Entitlements.plist" "/Users/…/Development/myAppProject/myApp.app"

Overall, this is a really cool tool!  I can't thank you enough for doing this, as I think this has the potential to have a huge effect on the future of Julia outside of academia.

The recipe system is used when a bundle for either platform is made. It consists of a list of rules specified within the AppBundler.jl/recipes.jl file for each platform. Each rule specifies its origin and destination. The origin/destination can be directories or files. In case the rule is for a file, additional parameters on whether it is treated as a template and whether it needs to be executable (for Linux and macOS) can be provided.
During the build step of a bundle, the rules are run in sequence. The files are copied from the origin to the destination. If the origin of a rule exists in the meta directory, the files are taken from there; otherwise, the origin for a rule is taken from the AppBundler.jl /recipes folder. When the default path of an origin is unspecified, the rule is skipped.
The last bit in the picture is interfering rules. When a previous rule has already affected the destination, the new rule respects the previous rule and skips merging in a particular file. This is useful for flattening the configuration directory structure while retaining the possibility of following a more hierarchical organisation used by the bundle.
In situations when the bundling does not work for the users, which I would like to hear about, they can modify bundle_app for their needs, which is only 40 lines of code to change, add or remove rules.
Let me know how well you could follow this description so I can consider this explanation as part of the docs. I also improved docs bundle_app and added more information on how one can generate a code signing certificate.

BTW: After AppBundler has matured, I think it would be great if the VSCode team could make it part of the user interface, so that users could click a single button to compile a standalone app.

Does that mean that if I do not have a meta folder in my source folder, AppBundler automatically picks the correct recipe from AppBuilder/recipes?

It is more detailed than that. The recipe consists of a list of rules which has origin location. If the origin for the rule exists in the MyApp/meta folder, then it is taken from there. If origin doesn't exist there, the rule is taken from AppBundler.jl/recipes unless it doesn't exist there either, in which case it is skipped. This is done for every recipe rule sequentially.


加载配置文件无法使用*.json

10 10月 2023 10:52:30 [main] INFO  Unrecognized field: Unrecognized field "include" (class com.github.dreamhead.moco.parser.model.SessionSetting), not marked as ignorable (8 known properties: "response", "redirectTo", "mount", "proxy", "request", "websocket", "on", "resource"])
at [Source: (String)"[
{"include": "*.json"}
]"; line: 2, column: 18] (through reference chain: java.util.ArrayList[0]->com.github.dreamhead.moco.parser.model.SessionSetting["include"])
10 10月 2023 10:52:30 [main] ERROR Unrecognized field [ include ], please check!

You should use -g option.
java -jar moco-runner-<version>-standalone.jar http -p 12306 -g settings.json

还是一样的，当我的配置文件中指定了文件名，就不会出现这错误

I figure out what's wrong: you put global setting and configuration files in same directory. Moco loads global setting file as configuration file.
The simple solution is to put configuration file in separated directory, e.g foo:
[
  {
    "include": "foo/*.json"
  }
]

The problem has been solved，thanks


[Feature request] Simulator

A simulator similar to the one added to the Bitbox 1 would be nice for people integrating Bitbox 2 into their own software in order to do CI.

That sounds like a good thing to have. We are currently quite busy with preparing the launch, so unfortunately this needs to wait for a bit longer.
I sent you an email regarding getting you a device.

I believe this has been completed in PR #1167 and such code has continued to be maintained.

Right, and a PR in HWI to integrate the simulator into the HWI CI is also open and being worked on by @asi345:
https://github.com/bitcoin-core/HWI/pull/741
Thanks again!

Also: the simulator is being released alongside the regular BitBox02 Multi releases, the first one in https://github.com/BitBoxSwiss/bitbox02-firmware/releases/tag/firmware%2Fv9.19.0.
It has also been integrated into the bitbox-api-rs repo for integration tests in https://github.com/BitBoxSwiss/bitbox-api-rs/pull/69 and in bitbox02-api-go for integration tests in https://github.com/BitBoxSwiss/bitbox02-api-go/pull/97.


Server token isn't saved on close

Hi !
I managed to launch a dedicated server for Don't Starve Together. Very usefull !
But unfortunately, the server token isn't saved on close. Every textbox inputs are saved except server token, so I have to enter it on each launch. Very boring !
Is somebody got a solution ?
Thank's !

Oh sorry, I found the solution !
You have to go to the server parameters page on your Klei account, then downloas server parameters.
In the downloaded zip, you'll find the cluster_token.txt file. Copy it in your cluster save folder.
On Vox startup the token is now present =)

Hey, your solution works, but it should be required.
It only saves the text box when you stop edditing it (like when you start editing another text box).
It might be better to also save it when you launch the server. Thanks for reporting.


fix: remove duplicated func call

Hi, fn(api.ProgressResponse{Status: "converting model"}) is called twice in line 101 and line 111. Just remove one.

I find this is fixed in pr https://github.com/ollama/ollama/pull/6327 , just close.


[#47] Update About Us page to include team member (Hanif) details

#47

Codecov Report

Merging #82 (86fee57) into master (9ebd3d7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #82   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 9ebd3d7...86fee57. Read the comment docs.


ODK does not have licensing terms in the repository

via Twitter: https://twitter.com/jgmac1106/status/804671714403749888
We should select and apply a license.

@iamjessklein do you have any strong feelings about this? We should do this sooner rather than later.

@LauraHilliger do you have any thoughts on this particular piece?

Since the interesting thing about this project is less the code and more the content, I imagine that this should be a Creative Commons license. My inclination is CC-BY:

This license lets others distribute, remix, tweak, and build upon your work, even commercially, as long as they credit you for the original creation. This is the most accommodating of licenses offered. Recommended for maximum dissemination and use of licensed materials.

Given that more of my work is visual and less of it's code, I'm more familiar with the CC licenses. We might consider non-commercial, though, because with CC-BY someone could package ODK and sell it as a product, if I'm not mistaken...

CC-BY ND would still let someone use a derivative for commercial purposes:

This license lets others remix, tweak, and build upon your work non-commercially, and although their new works must also acknowledge you and be non-commercial, they don’t have to license their derivative works on the same terms.

CC BY-NC-SA is more restrictive:

This license lets others remix, tweak, and build upon your work non-commercially, as long as they credit you and license their new creations under the identical terms.

I suppose it really comes down to whether we're worried that'll be an issue.

Honestly, I'm always on the fence about licensing!
this thread on the badge wiki Loomio has some arguments for less restrictive licensing.
https://www.loomio.org/d/YqhueSTa/creative-commons-license-for-badge-wiki

I've found this site to be a great resource for plain english comparing and contrasting of various licenses: https://choosealicense.com/

Hello @everyone
After the presentation of OpenDesignKit at OpenSourceDesign NYC meetup yesterday, we discussed the fact that the lack of license was probably slowing down future collaborations and improvements. @iamjessklein invited us to join this issue and hopefully help reach a final decision soon regarding this.
I see in this thread that everyone feels quite comfortable with the Creative Commons Licenses. That's good. These are all well known licenses (so most of the visitors will already have encountered them) and they still allow us to decide how open we want to be.
Now, I sense here a desire to be as open as possible. And I totally agree with that.
To be as open as possible, the very permissive CC-BY is the most open one, while still giving credit to the creators.
I, personally, am in favor of a license that imposes on anyone wanting to build on the project to share back their improvements under the same license. I think it's the closest behavior to a classic open source license such as the GPL. In that sense, CC-BY-SA  is the one.
I would dismiss any ND (no derivative) or NC (non commercial) clauses as they restrict the uses of the project. The ND would totally prevent anyone from submitting any changes or improvements. It would just make this project instantly obsolete or require a very complex process to participate, which beats the original purpose.
And the NC clause is so confusing to me (and a lot of people), I discourage its use, ever. As an example, in the case ODK would be published under CC-BY-NC, I would never know for sure if I could use it for anything else than a volunteer project. I'm not sure anyone could use it for a paid gig, even if it's in the context of a non-profit organization. We could discuss this at length, but the fact that it creates such debates is a good argument to move away from it as it probably creates more problem than anything.
So, it seems to me the choice boils down to a CC-BY or CC-BY-SA.
@iamjessklein is very inclined for CC-BY.
Are we all willing to support her in this choice?

I prefer CC-BY because it is the most simple one.
When working with CC-BY-SA, I sometimes was unsure what constituted a use which needed the works used together with it to be CC-BY-SA, too. I got it sorted out in most cases, but it was a hassle (particular if it concerned non-text works).
I also support not using NC and ND, just like @xuv: They prevent many usecases most projects actually want to support.
Aside from the largely hypothetical evil company (it rarely happens and even if: Who sues them?), NC hurts a lot of potential users who have decent usecases: Professors at universities, a designer payed to do a workshop, a (not-for-profit?) org who likes it and shares it (properly credited and linked) on their website, usage in many free knowledge projects like the ones by Mozilla or Wikimedia…
More on the problems of NC in this pdf

Okay, let's go with CC-BY and get this up on the website (I'll write another issue for us).
To confirm, here's the link from Creative Commons on the license.

I also hopped on the creative commons slack channel and had this validating conversation:

I'm closing this issue.
Our next action item is in #275
Thanks everyone for the thoughtful conversation! cc/ @jdittrich @xuv @susanjrobertson @ajpiano @mjchamplin @LauraHilliger


allow overriding autoconnect behavior

For some reason androidAutoConnect got hard-coded to true, but causes very long connect delays for us (>30s) which is unacceptable. For backwards compatibility, the default value is still true, but can now be overriden.
This solution is still not ideal because now we have to deal with reconnects etc. in the app. Long-term, a better fix would be to abstract all of that away behind a simple API.

Thanks for your contribution to FlutterBlue!
This issue was resolved during the latest wave of development. Please see ab3c7f14ea8c55fcaa0bc85c6d3956928e154900


Fix Issue 17: Removing "extra" json parsing entirely.

This causes errors (see #17) -- there is no need for this as we do not support this token based auth.

Approving my own changes for this simple fix.


Using temporary filing system names on Master gives "Bad name"

Using LOAD or SAVE with a temporary filing system (between hyphens at the start of the filename) on the Master (at least MOS 3.50) gives Bad name.  For example:
>SAVE "-ADFS-$.TEMP.RVHELLO"
Bad name
>

But switching filing system and saving to the file is OK:
>*ADFS
>SAVE "$.TEMP.RVHELLO"
>

It doesn't matter if ADFS is the current filing system or not to get the error.

FWIW, this problem doesn't appear to affect things like OPENOUT.

Sorry for not responding - for some reason Github didn't notify me. I'll investigate now.

This one is quite strange.
In Richard's BBC Basic, the quotation marks around the filename are optional. If you omit them then it works.
I suspect the issue occurs when the filename passed across the tube includes the quotation marks.
I think what's happening is that when the filename includes quotation marks, MOS 3.20 is somehow imposing a length limit. You get similar errors without a Co Pro running, if the quotation marks are present:

What's curious is the length limit the MOS is imposing seems to depend on the current file system. Do you have a MOS 3.50 system to try?
I can probably fix this by sanitizing the filename in my OS wrapper class.

I usually use MOS 3.50 (although I have 3.20 on a MultiOS switcher) and am getting the same behaviour, with a 7 character limit whilst in MMFS (even though I'm saving to -ADFS-XX) and a 10 character limit whilst in ADFS (-ADFS-XXXXX).  If I use ANFS, I get the same 10 character limit but get the error Bad path instead of Bad name, so presumably it's doing some sort of sanity check in the name using the currently selected FS.  That's presumably a MOS bug of some sort?
Interestingly, *SAVE -ADFS-"XXXXX" 2000+1000 does work fine and, when I use quotes with something like *SAVE "-ADFS-XXXX" 2000+1000, I end up with a file on my ADFS drive literally called -ADFS-XXXX, so I think the expected behaviour here is that you can't pass over quotes, if you want to use a temporary filing system name.
I guess the solution would be to strip the quotes out in the OS wrapper, as you're suggesting!

I guess the solution would be to strip the quotes out in the OS wrapper, as you're suggesting!

I've done than now.


Update create-graph-python.md

add 'pip install gremlinpython' to guide user for import gremlin_python

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

#label:"aq-pr-triaged"

#sign-off

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

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


1.16.0 is intercepting binstub arguments and throwing 'unknown switches' error

I've just created a new Rails project with bundler 1.16.0, and when trying to invoke the webpack binstub with command line arguments for the underlying executable, Bundler is throwing the message 'unknown switches':
$ ./bin/webpack --colors --progress
Unknown switches '--colors, --progress'

This did not / does not happen with 1.15.x Bundler.
I would expect that binstub command line arguments should still be proxied through to the underlying executable? I can find no documentation or issues that would suggest this chnge in behaviour was wanted.

It seems this change: https://github.com/bundler/bundler/blob/01fe509b27b317dd4d640beb9140ab31331ea349/lib/bundler/templates/Executable#L11-L12
Is responsible for the change in behaviour? Is this needed?

Confirmed, removing those two lines from my binstubs restores the correct behaviour of proxying command line arguments along to the underlying executable.
Removing them also seems to have no detrimental effect?

I was able to reproduce this, thanks for the report!

This shouldn't be happening, since we only old the "real" bundler exe when that file is invoked directly: https://github.com/bundler/bundler/blob/892a637f2d9bf18b9898ea31d4f5bf8d1e8cb8e4/lib/bundler/templates/Executable.bundler#L103-L105

I just ran into this problem as well.
This happens to me in Rails, because out of the box rails new generates the following bin/bundle binstub:
#!/usr/bin/env ruby
ENV['BUNDLE_GEMFILE'] ||= File.expand_path('../../Gemfile', __FILE__)
load Gem.bin_path('bundler', 'bundle')

When I generate a binstub manually, the new binstub doesn't work:
$ bundle binstub unicorn
$ bin/unicorn -E development
Unknown switches '-E'

The fix is to regenerate bundler's binstub:
$ bundle binstub bundler --force
$ bin/unicorn -E development
I, [2017-11-11T14:59:40.867225 #93138]  INFO -- : listening on addr=<IP_ADDRESS>:8080 fd=9
I, [2017-11-11T14:59:40.867334 #93138]  INFO -- : worker=0 spawning...
I, [2017-11-11T14:59:40.868225 #93138]  INFO -- : master process ready
I, [2017-11-11T14:59:40.868991 #93151]  INFO -- : worker=0 spawned pid=93151
I, [2017-11-11T14:59:40.869413 #93151]  INFO -- : Refreshing Gem list
I, [2017-11-11T14:59:42.193645 #93151]  INFO -- : worker=0 ready

I suspect that this will commonly be a problem even for non-Rails projects. E.g., if you started the project before bundler 1.16.0 was released, you have the pre-1.16.0 bin/bundle binstub. If you upgrade bundler to 1.16.0 and then generate a new binstub, you will encounter this error.

Also reported in Rails issue tracker: https://github.com/rails/rails/issues/31193
Looks like many existing Rails users are going to experience this problem.

@mattbrictson thanks for the heads up! Just so things are clear, this is not an upgrade issue for Bundler. Bundler 1.15 refused to create a binstub for itself:
$ bundle _1.15.4_ binstubs bundler
To update, run `gem install bundler`
Resolving dependencies...
Sorry, Bundler can only be run via Rubygems.

Bundler 1.16 started to support a bundle binstub as a first step towards letting applications quickly load the correct version of Bundler for that application.
I'm not sure how long Rails has been creating a bin/bundle, but it's definitely not a Bundler binstub. To resolve this, we might need to start throwing an informative exception if bin/bundle is the wrong kind of binstub.

I can confirm that this is a problem with other executables as well. For example sidekiq:
$ gem install bundler
Fetching: bundler-1.16.0.gem (100%)
Successfully installed bundler-1.16.0
1 gem installed
$ bundle version
Bundler version 1.16.0 (2017-10-31 commit 10f20fa33)
$ bundle binstubs sidekiq
$ bin/sidekiq -C config/sidekiq.yml
Unknown switches '-C'

@indirect Understood that the bin/bundle that Rails has been distributing is not a Bundler binstub. The reason I brought this up as an upgrade issue for Bundler is that as @johnmcdowall mentioned, binstubs generated by Bundler 1.16 now contain this code:
bundle_binstub = File.expand_path("../bundle", __FILE__)
load(bundle_binstub) if File.file?(bundle_binstub)

So before, the binstubs generated by Bundler 1.15 and below would be oblivious to the bin/bundle provided by Rails. But now the binstubs generated by Bundler 1.16 explicitly look for bin/bundle and load it, which leads to the problem.
Perhaps, as you said, Bundler needs to identify this and fail with a helpful error message. For example, it could work like this:
$ bundle binstubs sidekiq
An outdated bin/bundle executable was detected and this command cannot continue.
Run `bundle binstubs bundler --force` to correct this.

@mattbrictson yep, that's close to what I was imagining. I think we'll probably need to do something like this, to ensure that a bad bin/bundle fails in a predictable way:
def bundle_stub?(path)
    return false unless File.file?(path)
    return true if File.read(path, 150) =~ /This file was generated by Bundler/
    abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.")
end

bundle_binstub = File.expand_path("../bundle", __FILE__)
load(bundle_binstub) if bundle_stub?(bundle_binstub)

@indirect that looks like a good solution 👍

I'm having this issue with Bundler version 2.0.1 (2019-01-04 commit d7ad2192f).
The switches --name-only, --without-group, and --only-group are unknown. Only --paths works.
which bundle just prints /home/p/.gem/ruby/2.6.2/bin/bundle, which is where I installed Ruby using ruby-install. The header in the file itself says it was generated by RubyGems.
Any ideas?

You mean with bundle list, right? The problem is that the help that documents those options is for the new list command, that it's yet to be released. That has been fixed in https://github.com/bundler/bundler/pull/7072, and will be released with the next version.

Yes, I meant bundle list. Is there another way to just list the gems in a particular group?


Public Code.yml

Overview
We need to evaluate Public Code.yml's priority in the Product Development Roadmap (PDR)
Action Items

[ ] Review all Public Code.yml assets and discuss with relevant parties

Resources/Instructions
Assets:

https://github.com/civictechindex/publiccode-pusher
Parties:
Colin King-Bailey, Open Oakland (former author of Public Code.yml pusher)
Some people in Italy (@ExperimentsInHonesty will fill this in)

Screenshots from Public Code Pusher

From Harishlingam, March 29th, screenshots from test logins:

https://ckingbailey.github.io/publiccode-pusher/

https://ckingbailey.github.io/publiccode-pusher/

It's great, it guides you through fixing the errors (missing fields) and in the end it opens a pull request (so I can merge it or not).
To verify if feature and tag are mandatory
To verify where the values in the dropdowns (and other lists) come from.

It's great, it guides you through fixing the errors (missing fields) and in the end it opens a pull request (so I can merge it or not).
To verify if feature and tag are mandatory
To verify where the values in the dropdowns (and other lists) come from.

I'm looking at the problem to deploy/run a version out of one of our github repository (mine or CfA).
Then I think we know what to do, we need mostly to decide which fields make mandatory and the content of some of the list of values (this relate to the Taxonomy).

Created a new repository https://github.com/codeforamerica/publiccode-pusher
Able to run it without jumping back to someone else version https://codeforamerica.github.io/publiccode-pusher/
Still verifying some build issue.
Not sure why we have this issue in CTI.

Unless this issue is to somehow integrate with publiccode, there is no reason to have a publiccode issue open here. Any activity for now will be done in https://github.com/codeforamerica/publiccode-pusher.
Closing this.


Inline unreachable code

Checking this again... can be we losing the no-report test in this refactor. I mean in this snippet:

    fun throw1(p: Int): Int {
        if (p == 0) {
            throw IllegalArgumentException()
            println() // report 1 - unreachable code
        }
        throw IllegalArgumentException()
    }

We could be testing that the first throw creates unrechable code but the second don't. All at the same snippet...

@BraisGabin I'll create another PR that includes this scenario. I saw your comment too late.


Support for IPv6

Support for IPv6 as now available in Zipkin 1.4.0
This closes #13

wow. you're fast!


Delay when taking something out of vendor

There's a delay when you take something out of a vendor, about a second or a bit less. It is inconvenient, but not urgent.

fixed with the better server, was lag related


Refactoring content parsing

Description
One of the fields read from markdown files for rules is the reason.md. We just discovered that this file can live both at rule level and error key level, so the current parsing strategy doesn't fit very well with both possibilities.
This refactor intends to separate the parsing of the files and the validation of which fields are missing or not
Fixes #88
Type of change

Bug fix (non-breaking change which fixes an issue)

Testing steps
Regular CI

Codecov Report

Merging #95 into master will decrease coverage by 2.19%.
The diff coverage is 65.62%.

@@            Coverage Diff             @@
##           master      #95      +/-   ##
==========================================
- Coverage   75.00%   72.80%   -2.20%
==========================================
  Files           8        9       +1
  Lines         312      364      +52
==========================================
+ Hits          234      265      +31
- Misses         63       80      +17
- Partials       15       19       +4

Impacted Files
Coverage Δ

conf/configuration.go
81.13% <0.00%> (ø)

server/server.go
100.00% <ø> (+20.58%)
:arrow_up:

content-service.go
43.61% <30.76%> (-4.92%)
:arrow_down:

content/content.go
84.84% <79.10%> (-5.26%)
:arrow_down:

content/errors.go
100.00% <100.00%> (ø)

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 ecc07ba...e66b59b. Read the comment docs.


Restore a wallet locally by scanning the QR code exported by Google Authenticator

Implemented in https://github.com/polymorpher/one-wallet/commit/1e58213a604e93d077e8b204f4bcc19505982af2 . This was missed (though mentioned) in the original planning document: https://github.com/polymorpher/one-wallet/issues/5


Added routine for reading shader code from embedded buffer.

New function loadShaderFromBuffer() for loading a shader from an
inmemory string.
New function readBinaryFile() for reading a binary file.
Rewrote loadShader() to use the above two functions.

As there is no sample in my repo that requires such a function I'll close this PR for now.


8.0.4 does not run on HA < 2024.11

Describe the bug
Release 8.0.4 and newer do not work on HA < 2024.11 due to a dependency on the newly-introduced AlarmControlPanelState enum introduced in #1240.
To reproduce
Steps to reproduce the behavior:

Upgrade to version 8.0.4 or newer while running  HA 2024.10.4.
Restart HA.

The error is:
ImportError: cannot import name 'AlarmControlPanelState' from 'homeassistant.components.alarm_control_panel'

Expand for full stack trace
Logger: homeassistant.config_entries
Source: config_entries.py:594
First occurred: 26 November 2024 at 12:28:01 (1 occurrences)
Last logged: 26 November 2024 at 12:28:01

Error setting up entry localhost for eufy_security
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/eufy_security/__init__.py", line 56, in async_setup_entry
    await hass.config_entries.async_forward_entry_setups(config_entry, PLATFORMS)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2147, in async_forward_entry_setups
    await integration.async_get_platforms(platforms)
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1177, in async_get_platforms
    import_future.result()
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1177, in async_get_platforms
    import_future.result()
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1177, in async_get_platforms
    import_future.result()
  [Previous line repeated 7 more times]
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1165, in async_get_platforms
    platforms.update(self._load_platforms(platform_names))
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1090, in _load_platforms
    platform_name: self._load_platform(platform_name)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1264, in _load_platform
    cache[full_name] = self._import_platform(platform_name)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1296, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/config/custom_components/eufy_security/alarm_control_panel.py", line 6, in <module>
    from homeassistant.components.alarm_control_panel import (
ImportError: cannot import name 'AlarmControlPanelState' from 'homeassistant.components.alarm_control_panel' (/usr/src/homeassistant/homeassistant/components/alarm_control_panel/__init__.py)

Expected behavior
The component should work on a HA version that was released barely 1 month ago (2024.10.4 was released on October 25).
Since the enum was only just introduced in https://github.com/home-assistant/core/pull/126283 and will be removed in 2025.11 don't you feel it's a bit premature to introduce this breaking change just because of a deprecation warning? Not everyone is on the bleeding edge all the time with HA.
Suggested fix
If it's too much to live with a warning in logs for a few months then it is possible in code to test if the enum exists and use it if so, falling back to the deprecated constants otherwise. This would be removed closer to the deprecation cut-off.
Alternatively, simpler but not as good for users: in hacs.json it is possible to indicate the minimum required HA version with the homeassistant property. Setting a value there would at least prevent users from shooting themselves in the foot by upgrading to a version that is incompatible. The breaking change should also be indicated in release notes.

Since latest HA update i lost my door lock

2024-12-16 08:53:31.545 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-16 08:53:31.546 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-16 08:53:31.547 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration toyota_na which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-16 08:53:31.547 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration govee which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-16 08:53:31.548 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-16 08:53:31.548 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration eufy_security which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-16 08:53:33.845 ERROR (MainThread) [homeassistant.config] Unknown error when validating config for sensor from integration template - argument of type 'NoneType' is not iterable
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config.py", line 1074, in _async_load_and_validate_platform_integration
return platform.PLATFORM_SCHEMA(p_integration.config)  # type: ignore[no-any-return]
~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^

Since latest HA update i lost my door lock

I have same issue.


Make CDN ESM paths work

Describe the feature
I want to specify this config:
{
  "jsc": {
    "paths": {
      "@swc/wasm-web": [
        "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>      ]
    },
    "parser": {
      "syntax": "typescript",
    },
  }
}

and have this input:
import foo from '@swc/wasm-web';
foo();

give this output:
import foo from "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>foo();

but instead I get this:
import foo from "./https:/cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>foo();

I can't tell if there's already a way to do this or not, but it looks like no, so I'm specifying it as a feature request at the very least.
Babel plugin or link to the feature description
No response
Additional context
No response

I haven't tested it yet, but it appears to be exactly what you need.
See https://github.com/swc-project/swc/discussions/9016#discussioncomment-10308208

Thanks, but when I use jsc.experimental with an empty object, or include plugins with an empty array, or include this plugin with an empty object, etc, swc crashes with a weird error that I can't find anything about. I also can't find any docs for this plugin or for how to use the experimental-plugins feature. So I'm trying to create a plugin manually instead to use with the non-experimental plugin feature to accomplish this.

@sdegutis JS plugin is deprecated, and I would recommend using wasm plugins if possible.
It's documented at https://github.com/swc-project/plugins/tree/34141644d2a9ac43ff8d853b4c938f2afd5fb610/packages/transform-imports, but @swc/wasm-web does not support it. But @swc/wasm* does not support JS plugin, too.


Updating Readme

Pull Request for DL-Simplified 💡
#587
Issue Title : [README Enhancement]: Google Recaptcha Image Classification

Info about the related issue (Aim of the project) : Just Updating Readme
Name: Avishek Rauniyar
GitHub ID: Avishek8136
Email ID<EMAIL_ADDRESS>**Idenitfy yourself: GSSOC | Contributor

Closes: #587
Describe the add-ons or changes you've made 📃
Added Readme
Give a clear description of what have you added or modifications made
Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ x] This change requires a documentation update

How Has This Been Tested? ⚙
Describe how it has been tested
Describe how have you verified the changes made
Checklist: ☑

[x ] My code follows the guidelines of this project.
[x ] I have performed a self-review of my own code.
[x ] I have commented my code, particularly wherever it was hard to understand.
[x ] I have made corresponding changes to the documentation.
[ x] My changes generate no new warnings.
[ x] I have added things that prove my fix is effective or that my feature works.
[ x] Any dependent changes have been merged and published in downstream modules.

The readme is okay. I checked it woth model. I just dragged it outside the folder. Just change the thing if needed or else just close the issue.


Change f_of_x... to np.ndarray instead of float

This has now been changed. Additionally, f_of_* have been renamed to f_*. Closing.


Tracking issue: move unnecesary VM tests

Issue description
There are some VM tests that don't actually use any of the VM's capabilities. These would be better suited as installation tests on the packages that they test
Upsides:

Cheaper on resources
Works on all platforms instead of just on NixOS
More local: everything is in the package instead of spread out
(possibly neutral): Test always runs when building instead of only when explicitly called

Affected tests
Possibly incomplete list, maintainers: feel free to edit this comment if you know of more.

[ ] etesync-dav(?) (opens a port, not sure if that can be done in the sandbox) (cc @3699n)
[ ] kbd-setfont(?)
[ ] handbrake (#143687)
[x] cifs-utils (#144039)
[x] ammonite (cc @NeQuissimus) (#143813)
[x] awscli (#143776)
[x] spike(?) (cc @blitz) (#143832)
[x] bat (#143768)
[x] lsd (cc @NeQuissimus)
[x] ucg (cc @AndersonTorres) (#143708)
[x] google-cloud-sdk (#143375)
[x] yq (#143366)

Possible further steps

[x] Edit PR template to make it clearer that not all packages need a nixos test (https://github.com/NixOS/nixpkgs/pull/144033)

@Synthetica9 I've moved the spike nixos test to be an installCheck. See #143832.

[ ] Edit PR template

I would have made that the first step. See https://github.com/NixOS/nixpkgs/pull/144033

Handbrake test can be marked as finished, too, as per #143687.


Stylelint configuration and scss fixes

Description :sparkles:
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #110 (72bc290) into master (f8827a5) will decrease coverage by 0.11%.
The diff coverage is 94.11%.

@@            Coverage Diff             @@
##           master     #110      +/-   ##
==========================================
- Coverage   90.92%   90.81%   -0.12%
==========================================
  Files          87       85       -2
  Lines        2204     2199       -5
  Branches      416      428      +12
==========================================
- Hits         2004     1997       -7
- Misses        196      198       +2
  Partials        4        4

Impacted Files
Coverage Δ

...rc/common/components/form/fields/DropdownField.tsx
75.75% <ø> (ø)

...mmon/components/form/fields/MultiDropdownField.tsx
94.28% <ø> (ø)

...mmon/components/form/fields/PlaceSelectorField.tsx
70.00% <ø> (ø)

...onents/multiSelectDropdown/MultiSelectDropdown.tsx
84.00% <ø> (ø)

src/common/components/textInput/InputWrapper.tsx
90.62% <ø> (ø)

src/common/components/timepicker/utils.tsx
100.00% <ø> (+31.25%)
:arrow_up:

src/domain/app/layout/PageLayout.tsx
100.00% <ø> (ø)

src/domain/event/calendarButton/CalendarButton.tsx
87.80% <ø> (ø)

src/domain/place/placeInfo/PlaceInfo.tsx
91.30% <ø> (ø)

src/domain/place/placeInfo/PlaceMapLink.tsx
93.33% <ø> (ø)

... and 11 more

Continue to review full report at Codecov.

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


Added PM2, tweaked readme to reflect PM2 and a little beautification

Removed forever manager and added PM2 manager instead. The file in question is package.json. This meant changing start to "start": "pm2 start ./lib/index.js --name GPT-Shell && pm2 save && pm2 logs" and reflecting the changes in README.md.
Misc changes:

Beautification mainly on links and commands to enable readers copy easily.
Added example.env.local to ease setting up env vars and reflected it to README.md

Thank you for the pr.
Is there a particular reason to switch away from modern yarn?

Yw,
What I did was remove Forever. Removing the Forever package and installing PM2 does not necessarily mean that I switched away from modern Yarn. Yarn is a package manager that can be used to manage dependencies for a Node.js project, and it is not limited to any specific package or tool.
Both Forever and PM2 are process managers for Node.js applications, and they can be used with any package manager, including Yarn. So, I just chose to continue using Yarn with PM2, as I 've demonstrated earlier by modifying the package.json file to use the yarn start command with PM2.
I guess your question is originating from the 300+ changed files, I was working from a codespace so it automatically updated yarn, so the only changes I made were on package.json and README.md, you can change those two files and close this pr, or lemme redo it prolly later when I'm on my local machine

Alright, now I fixed the changes to only show on package.json and README.md

Thank you, taking a look :)

Alr, honestly, I dodn't understand why you would need both npm and yarn; npm could be fine on its own, but I didn't want to move away from yarn because I haven't gone through the whole code

Great work, thank you so much :D
I just need to consider moving away from zero-installs and modern yarn...
I guess it's very experimental still so ok, will clean up the modern yarn requirements before merging this PR
I need to finish up a few other things first but after those I'll come back to this :)

Alr, honestly, I dodn't understand why you would need both npm and yarn; npm could be fine on its own, but I didn't want to move away from yarn because I haven't gone through the whole code

Update: experimented a bit with not having the yarn cache etc and allowing typical npm and not "zero install" yarn, and it feels better, especially after testing with a few different hosting solutions.
So when I have free time hopefully in the next week or so, can do that and bring your PR in :)
Thanks!

Merged via #19 :) thanks!


EN-13889: Trigger a resync, don't mark as broken, if the WC publicati…

…on state is unexpected
Since our reaction to getting paged because of this is to manually trigger a resync, why not have the code do this for us?
Resyncing should take care of the working copy being in an unexpected state when we get a WorkingCopyPublished event.

This build looks good.


Job profile page should present CPU and GPU in natural terms

At the moment the y axis is in terms of "percentages of core" or "percentages of a card".  The main table in jobquery divides these by 100 to get natural values but the profile display does not, and it should.

@ashenr This is actually somewhat high priority.  In addition to presenting the "best" units (lets discuss this) the profile graphs should have a legend stating what the unit is so that there is no confusion at all about what we're looking at.  Even now I'm confusing myself.

OK, complication: this bug really only pertains to the html format output, because that's the case where the front-end can't massage the output further.  For all the other cases it's probably easiest to keep the format in the form it already has, where "100" is "100% of 1 core", etc.

Should also tag the timestamps with "Z" as we do elsewhere.


ServiceAccount type subscription-admin role binding

Signed-off-by: Roke Jung<EMAIL_ADDRESS>ServiceAccount type subject in the cluster role binding.
subjects:

kind: ServiceAccount
name: adminsa
namespace: default

/lgtm

/lgtm


Allow retries while connecting to Cassandra

This should reduce some of the excessive controller logging and fix an issue with the upgrade script attempting to run before Cassandra is ready.

https://ocd.appscale.com:8080/job/Daily Build/1640/


Faucet Login and Mint Tokens Integration

Summary of changes
Provide a detailed description of proposed changes.

Integrate the Twitter Login flow
Integrate the Mint Tokens flow
Improve error handling (integrate neverthrown usage)

Proposed area of change
Put an x in the boxes that apply.

[ ] apps/bridge-dapp
[ ] apps/stats-dapp
[ ] apps/webbsite
[x] apps/faucet
[ ] apps/tangle-website
[x] libs/webb-ui-components

Reference issue to close (if applicable)
Specify any issues that can be closed from these changes (e.g. Closes #233).

Closes NaN

NEXT_PUBLIC_APP_URL="http://localhost:4200" # optional
NEXT_PUBLIC_FAUCET_BACKEND_URL="http://<IP_ADDRESS>:8000" # optional
NEXT_PUBLIC_TWITTER_CLIENT_ID="<YOUR_TWITTER_CLIENT_ID>"
TWITTER_CLIENT_SECRET="<YOUR_TWITTER_CLIENT_SECRET>"

We need to set these environment variables in the Github Secret @dutterbutter.

Please resolve conflicts @AtelyPham

I cannot seem to login via Twitter even though logging in produces a successful response on the local server.
After logging in via Twitter:

Server success:

@AtelyPham can we add a "Add token to MetaMask" button so its readily easy for users to see the tokens present in their wallet.

Yes, we can definitely do that! However, the data we currently have is mocked, including the claim data on the backend. Nonetheless, I’ll work collaboratively with Shady to get the actual data for the faucet.


Fatal error at installation when executing "pack info": Server does not allow request for unadvertised object

Expected Output:
Package Collection  : nightly-230201
Idris2 URL          : https://github.com/idris-lang/Idris2
Idris2 Version      : 0.6.0
Idris2 Commit       : ad12f8335c4e0fbd532b2c672c17edc88b34f56d
Scheme Executable   : chezscheme
Pack Commit         : b3f8cd2bbdf1fecc749d80f16f1190f56dac45cf
Installed Libraries : base
                      contrib
                      filepath
                      idris2
                      linear
                      network
                      prelude
                      test
                      toml

Actual Output:
error: Server does not allow request for unadvertised object 698971cbcc7f7ce702a65c0d9af0704b6b727e18
[ fatal ] Error when executing system command.
          Command: "git" "fetch" "-q" "origin" "698971cbcc7f7ce702a65c0d9af0704b6b727e18"
          Error code: 1

I tried to search "698971cbcc7f7ce702a65c0d9af0704b6b727e18" in the directory ~/.pack/.cache and I found it in two files:
git/github.com/stefan-hoeck/idris2-pack-db/collections/nightly-230201.toml:
[db.barbies]
type        = "github"
url         = "https://github.com/stefan-hoeck/idris2-barbies"
commit      = "698971cbcc7f7ce702a65c0d9af0704b6b727e18"
ipkg        = "barbies.ipkg"
packagePath = false

and git/github.com/stefan-hoeck/idris2-pack-db/STATUS.md
[barbies](https://github.com/stefan-hoeck/idris2-barbies) | Barbies: Data types that can change their clothes | [698971c](https://github.com/stefan-hoeck/idris2-barbies/commit/698971cbcc7f7ce702a65c0d9af0704b6b727e18)

So I changed my directory to ~/.pack/.cache/git/github.com/stefan-hoeck/idris2-barbies and executed 'pack info' again, and then it worked.
Operating System: Ubuntu 20.04.

What git version are you using? There are minimal requirements in the preparation section of the installation instructions.

I was using git version 2.25.1. I'm sorry that I didn't check the version requirements for git. I thought the package in the default repository was enough.
Upgrading to the latest version of git solved this problem.

I'm closing this as resolved.


Move all use of bat behind a module

This makes it possible to build a vendored cargo-expand with a patched lib.rs to access the sanitize module, without depending on bat too.
@diliop

Never mind, you'd already not be building main.rs in that case, so this shouldn't be necessary. It would only be a problem if one of the modules you wanted (like edit) was using bat, but none of them are.


Answer Semantic Similarity gives output not in range 0-1

Describe the bug
The output of the AnswerSimilarity metric should be in range 0-1, but gives also negative output, and not in range 0-1. This affects also answer correctness metric. If i do not put the param "threshold" to None, the output results binary True/False.
Ragas version: 0.0.22
Python version:3.10.6
Code to Reproduce
answer_similarity=AnswerSimilarity(llm=ragas_bedrock_model,embeddings= bedrock_embeddings, threshold=None)
answer_similarity.score(ds)
output: 35.83004634
Expected behavior
The score should be between 0 and 1, not specifiyng thresholds values.

Are your embeddings normalized? This might be one reason

I'm passing to the api the embedding model, not embeddings  theirself, so the library should do this.

Hi @AnnamariaGalante , thanks for reporting this issue. Does this occur in every sample or is it once in a while issue?

Hi @shahules786, It occurs in every sample, using bedrock embeddings. I think this affects answer correctness too.

that's interesting, Would you like to help us find out the issue here with bedrock? I think this is due to the embedding not being normalised @AnnamariaGalante


ark alias conflicts with Ark, the KDE archiving tool

Expected Behaviour
When  arkade is installed, my os basic tools should keep working... ;)
Current Behaviour
When arkade is installed, it creates a symlink /usr/local/bin/ark that override the ark utility ( located in /usr/bin/ark) which is used to handle all archive file on KDE desktops (tar, bz, etc.). All gui-based operations on these files are then broken (from the file manager, etc.).
Possible Solution
Avoid creating that alias by default, use a command line argument to create it only when explicitly requested.

Hi @PierreRustOrange would it be useful to you if we have an env-var to suppress the alias?
export CREATE_ARKADE_ALIAS=0

Thanks for your answer.
I'd rather have an env-var to create the alias than to suppress it,  it's actually very easy to fix the problem (only need to rm the symlink), the only difficult part is to identify it. It took me some time to understand why I could not open any tar.gz anymore...
Either way, as long as it is mentioned in the doc I'd say it's fine !

What if we checked for ark existing in PATH before creating it? Would that resolve this issue?

That's a great idea, that would completely resolve the issue and could probably be implemented by simply checking the return form whereis ark before creating the symlink.

I know you didn't come here necessary to write a PR, but would you be up for giving it a shot? we use get.sh in this repo.

You're right, I should have done that before.
The PR is done, my bash is probably a bit rusty, there might be a more efficient way to implement that check but it seems to do the trick.

/close
This was implemented in #89
thanks


Is this project still alive?

There haven't been any commits in months. Is this project alive?

What is it that you've been working on, if you don't mind me asking?
On Thu, Apr 5, 2018 at 5:22 PM, Houssam Haidar<EMAIL_ADDRESS>wrote:

Sadly no, we've all been very busy at our company and haven't had the
bandwidth to work on this thing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sdelements/lets-chat/issues/781#issuecomment-379081046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ads01PjfVD7vBFIxvI5DzJb45CPMl613ks5tlosxgaJpZM4TDyDy
.

Haha I'm not sure why you'd be interested, but mainly a react rewrite of SD Elements (our main app) and now I'm working on a new product with a new team.

Curiosity killed the cat :P
On Thu, Apr 5, 2018 at 11:40 PM, Houssam Haidar<EMAIL_ADDRESS>wrote:

Haha I'm not sure why you'd be interested, but mainly a react rewrite of
SD Elements (our main app) and now I'm working on a new product with a new
team.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sdelements/lets-chat/issues/781#issuecomment-379139870,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ads01EC2s0FL96XkRFBzCRgQYOZIsk7eks5tluPLgaJpZM4TDyDy
.

@hhaidar Which rival of Let's chat would you recommend?

@RoestVrijStaal probably @mattermost or RocketChat. I can't really comment though, because I haven't ran them apart from demos.
If it helps, our company ended up switching to @slackhq last January.

Mattermost is open source, slack is not.
On Thu, Jun 28, 2018 at 4:06 PM, Houssam Haidar<EMAIL_ADDRESS>wrote:

@RoestVrijStaal https://github.com/RoestVrijStaal probably @mattermost
https://github.com/mattermost or RocketChat. I can't really comment
though, because I haven't ran them apart from demos.
If it helps, our company ended up switching to @slackhq
https://github.com/slackhq last January.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sdelements/lets-chat/issues/781#issuecomment-401140943,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ads01IOeZ_yc5SMkr0DTTsE9xqPz1Q-Kks5uBSk9gaJpZM4TDyDy
.

@hhaidar i love lets chat, because of its light footprint on my server and easy manageability, so i have forked it and i cant wait to see where it goes, i will continue with implementing markdown support first then move on to features like direct messages etc, if you all want to follow it, you can see my fork 😃

Hi @LizAinslie , are you still maintaining this fork? FYI I curate a list of potential free code replacements for Slack. It's worth considering software that implements a federation protocol like XMPP (Snikket) or matrix (Element or Gitter), so you don't end up stuck in yet another chat silo.

Hi @LizAinslie , are you still maintaining this fork? FYI I curate a list of potential free code replacements for Slack. It's worth considering software that implements a federation protocol like XMPP (Snikket) or matrix (Element or Gitter), so you don't end up stuck in yet another chat silo.

@strypey unfortunately I am not. My company, Synapse Technologies, will provide its own chat solution but it will also be closed-source. While Matrix and XMPP protocol support are in consideration and for the most part planned, on-premises licensing will be priced according to enterprise service as per the business model we operate on. Another thing to keep in mind is that this is all in early stages, and enterprise licensing won't be made available until November 2021. I guess I ought to plug the Synapse website here for anyone who may be interested, even though there's nothing but an NGINX default page there as of yet. (I'll get the landing transferred from our old host soon, but for now enjoy NGINX: https://synapsetech.dev)
And while the paid licensing isn't exactly what a lot of people want to hear, all Synapse services (including our chat service) will be free (/freemium) for individual users to benefit from, so it's not entirely locked down to enterprise plans.
And it goes without saying that we may also shift our plans towards open-source community releases alongside the full-fledged option.
TL;DR is no, I am not still maintaining my fork, but I will have an alternative to offer in the very near future.
Sorry for the (absurdly) late response by the way, I've been out for a while for personal reasons. Hope I helped though!