question: folder custom file modules.yaml in cisco ACI nexus as code

I would like to know in which folder I have to put the custom modules.yaml file since it only uses the one inside the .terraform folder which enables all the modules creating resources not required with the default setting. also I would like to know how the external bridge domains can be created since it seems to be an absent feature

Can be any folder or file referenced by the yaml_files or yaml_directories module attribute. Not sure what you are referring to by "external bridge domains".

I cannot put the modules.yaml anywhere as it does not overwrite the settings in the modules.yaml file present in .terraform/modules/aci/defaults where all modules are in true
for example if I put in my yaml file aci_aaa: false, terraform will still try to create the module since it is active in the default yaml file
fabric-> access policies-> physical and external domains -> external bridged domain
there is no module for this
Translated with DeepL.com (free version)

Whatever you have in your "data" files/directories should always overwrite what is included in the module defaults. Could you share the content of your modules.yaml and main.tf file as well as the plan output?

"External bridge domain" is a legacy feature for tenant l2outs which is typically not used nowadays.

main.tf
required_providers {
aci = {
source = "CiscoDevNet/aci"
}
}
}
locals {
apic_config = yamldecode(file("${path.module}/data/defaults/apic.yaml"))
}
provider "aci" {
username = local.apic_config.apic.credentials.username
password = local.apic_config.apic.credentials.password
url      = local.apic_config.apic.credentials.url
insecure = true
}
module "aci" {
source = "netascode/nac-aci/aci"
yaml_directories = ["data"]
manage_access_policies    = true
manage_fabric_policies    = true
manage_pod_policies       = false
manage_node_policies      = false
manage_interface_policies = false
manage_tenants            = true
data/defaults/modules.yaml
modules:
aci_access_policies
aci_aaa: false

module.aci.module.aci_aaa[0].aci_rest_managed.aaaAuthRealm will be created

resource "aci_rest_managed" "aaaAuthRealm" {

annotation = "orchestrator:terraform"
class_name = "aaaAuthRealm"
content    = {

"defRolePolicy" = "no-login"
}

dn         = "uni/userext/authrealm"
id         = (known after apply)
}

module.aci.module.aci_aaa[0].aci_rest_managed.aaaConsoleAuth will be created

resource "aci_rest_managed" "aaaConsoleAuth" {

annotation = "orchestrator:terraform"
class_name = "aaaConsoleAuth"
content    = {

"providerGroup" = null
"realm"         = "local"
}

dn         = "uni/userext/authrealm/consoleauth"
id         = (known after apply)
}

module.aci.module.aci_aaa[0].aci_rest_managed.aaaDefaultAuth will be created

resource "aci_rest_managed" "aaaDefaultAuth" {

annotation = "orchestrator:terraform"
class_name = "aaaDefaultAuth"
content    = {

"fallbackCheck" = "false"
"providerGroup" = null
"realm"         = "local"
}

dn         = "uni/userext/authrealm/defaultauth"
id         = (known after apply)
}

module.aci.module.aci_aaa[0].aci_rest_managed.aaaUserEp will be created

resource "aci_rest_managed" "aaaUserEp" {

annotation = "orchestrator:terraform"
class_name = "aaaUserEp"
content    = {

"pwdStrengthCheck" = "no"
}

dn         = "uni/userext"
id         = (known after apply)
}

module.aci.module.aci_aaa[0].aci_rest_managed.pkiWebTokenData will be created

resource "aci_rest_managed" "pkiWebTokenData" {

annotation = "orchestrator:terraform"
class_name = "pkiWebTokenData"
content    = {

"maximumValidityPeriod"  = "24"
"uiIdleTimeoutSeconds"   = "1200"
"webtokenTimeoutSeconds" = "600"
}

dn         = "uni/userext/pkiext/webtokendata"
id         = (known after apply)
}

Try to put the modules.yaml file directly in the data/ directory, not a data/defaults/ subdirectory.

thanks i try and woks only in main folder data/

i solve the problem with this command in the main.tf
yaml_directories = ["data", "defaults"]


Please release a first version to maven-central

Hi!
Please release a first version (maybe 0.0.1) to maven-central, so the dependency can
be included without extra repository /snapshot-repository configurations.
Thanks!

@domdorn I’m planning to release a first non-snapshot version at the end of this week / start of next.

0.0.1 release to Maven central.


[Discussion] Create integration tests

Problem
Currently, this project has jest setup to do unit tests but there is no tool to do integration tests.
Goal
Have integration, end-to-end tests to make sure that the components work together. This will give us more confidence in releasing.
Possible Solutions
Use cypress for integration tests. Add it to CI.

Thanks for bringing this up Roshan, we have plans to roll out a common testing framework throughout our frontend projects (Dashboard, Jinabox). Cypress seems like a great solution, I will look further into this and determine how well this would fit into our entire stack and the next steps for implementation.

With https://github.com/jina-ai/dashboard/pull/75, we're starting to use cypress.
Next steps:

Add cypress to CI
Add tests to cover existing views.


Detect and process escape and enter

Hi,
How do you detect keypresses for escape and enter to end editing and either save or cancel the changes?  I am new to Ember so I might just not know how to do it...  If not possible, I would like to request it as a feature.
tried escape-press='alertUser' without success.
Thanks!

I had a try and it's not currently possible - adding support for it now :smile:

Released 0.2.0 which should fix this, just update the version in your package.json and do an npm install and both escape-press='alertUser' and enter='otherEvent' should work.
Let me know i you have any more issues :)

This is an amazing add-on!  Well done and thank you so much!  Also very impressed with the response times :)
Tested both escape-press and enter attributes and they work as advertised.

When I look at:
https://github.com/emberjs/ember.js/blob/v1.13.6/packages/ember-views/lib/mixins/text_support.js
Ember includes this so that you can get a reference back to the input. See line 236.
sendAction('escape-press', this, event);
On escape, I need to stop editing and lose focus and undo changes and it will help to get a reference to this.
Thanks!

Actually, I see that this file implemented sendAction differently... and they only pass currentValue.  I think it is important to be consistent with the Ember implementation.. but it might make sense to add currentValue first and then also a reference to the contentEditable... unless there is a better way to accomplish what I am trying to do.

Oops yeah you're definitely right about keeping consistent with the Ember implementation. I'll update later to match their params / happy to accept a PR before then too.

Ok, params now match those from TextSupport like you pointed out.
For the current value you wanted, could you just use contentEditable.get('value'), where contentEditable is the first param to escape-press?
Hope that helps.

Thanks - i am all set with this one.


ci: integration-node-drivers

How was this created?
# open scripts/bump-engines.ts
# comment `await run(path.join(__dirname, '..'), `pnpm update -r @prisma/prisma-fmt-wasm@${version}`)`
pnpm run bump-engines 4.16.0-13.integration-node-drivers-b380f1e24042c44c2ebbaf1a01137388d0d0cf4e
# create integration/node-drivers branch
# commit packages and lock
# push

Why @prisma/prisma-fmt-wasm was excluded?
because the WASM build failed in prisma-engines https://github.com/prisma/prisma-engines/actions/runs/5197985075/jobs/9373535137
Meta: integrates changes in https://github.com/prisma/prisma-engines/pull/4017

Superseded by https://github.com/prisma/prisma/pull/19710.


Transparent Background

The part you want to Enhancement
Make superfile's background transparent.
Why it is necessary to enhancement
Better integrate with my terminal workflow.
Additional context
I saw a couple of theme examples had transparent backgrounds, but I'm unsure how to recreate it.

The transparent background is set by the user's terminal.
Most software/extension on Linux can blur windows (like Gnome blur my shell etc)
I'm not sure if it can be done on a Mac, but it can be done easily on most desktop environments on Linux.

Sorry if my wording was misleading. I want to disable the spf background. You can see the first image is how my terminal looks by default, then how spf looks (I want to remove the background color)

It's not your English problem.
My English is awful:(
I think this is a good idea and I will add it!

currently you can just remove the whole background section. It will not apply any color.
but yh it's just undefined behaviour which we are misusing.
it'd be good to have an option for it.

Should there be one more file to set related settings?
(related to theme but not color)
For example, Cursor is an arrow or option background highlight, as well as Border style, etc.

I don't think there is a need for it. But it will cause no harm. For long term, you should have one.

Basically, this works really well, but since in the unfocused state the sidebar's border can be set to follow the background color or have its own color, this results in the sidebar's border not being able to determine if it should be eliminated or not.
(Other elements have some similar issues)
Now I will set these in question to clear the background (currently no theme requires not clearing the background) but this should be a issue in the future.

Update in https://github.com/MHNightCat/superfile/commit/4108d40bc0b93656eca2da98253a83dbc0cb27a9
still have some issue need fix :(

Thanks, I'm looking forward to the next release.

Hey @MHNightCat a quick update:

Looks like there is a typo on the config option (should be transparent_background with a d at the end)
When I added this to my config it had no effect. I will play around with it more to figure out if it's a user error

Hi, thanks for the transparency addition! But the text in file preview has a background color behind it. Maybe it is possible to fix it on my end but maybe you could disable it along with other background elements.

Ok thanks for your report!

@112batuhan
Fixed it!

Thanks for quick update!

It's working for me @yorukot, I put my config in ~/.config/superfile and I had to move it to ~/Library/Application Support/superfile for macOS.

It's working for me @yorukot, I put my config in ~/.config/superfile and I had to move it to ~/Library/Application Support/superfile for macOS.

love it! I'm closing this question for now.


API resolved without sending a response

Hi! Thanks for the awesome library.
I'm getting an issue when using the example configuration, where when I query my graphql endpoint, I get the response
API resolved without sending a response for /api/graphql, this may result in stalled requests.

Any ideas on how I could fix this?

Turns out this was an issue with auth0. Closing


Fugitive.vim doesnt exists?

I checked in lazyvim that the vim-fugitive is already installed, but while i tried type Git command, it doesnt exist. It only another Git blabla command showing in pipeline.

The fugitive plugin is only activated when certain conditions are met. Are you sure it is started already??

all should working correctly, i dont know what happened but it solved by using packer


Get error when try to build from source code

Error:
Missing:
----------
1) org.apache.maven.archetype:archetype-packaging:jar:RELEASE

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=org.apache.maven.archetype -DartifactId=archetype-packaging -Dversion=RELEASE -Dpackaging=jar -Dfil
e=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=org.apache.maven.archetype -DartifactId=archetype-packaging -Dversion=RELEASE -Dpackaging=jar -Dfile=
/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.switchyard.archetypes:switchyard-application:maven-archetype:2.1.0-SNAPSHOT
        2) org.apache.maven.archetype:archetype-packaging:jar:RELEASE

----------
1 required artifact is missing.

for artifact:
  org.switchyard.archetypes:switchyard-application:maven-archetype:2.1.0-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  fusesource-public-release-repository-group (https://repository.jboss.org/nexus/content/repositories/fs-releases),
  jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/),
  jboss-enterprise-techpreview-group (http://maven.repository.redhat.com/techpreview/all/)

OS: win7 64bit
Maven: 2.2.1 ( regarding to switchyard core README file )
Java:

java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)

Another issue is cannot find the camel-sap artifact

[ERROR] Failed to execute goal on project switchyard-component-camel-sap: Could not resolve dependencies for project org.switchyard.componen
ts:switchyard-component-camel-sap:bundle:2.0.0.Final: Failure to find org.fusesource:camel-sap:jar:6.2.0.redhat-064 in https://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1]

JDK8 is not support?

Please start a thread here detailing the build issues you are having, JDK/maven used, and errors you see here -
https://developer.jboss.org/en/switchyard?view=discussions
It's been a month or two since I've tried it, but I believe JDK8 is fine for building.    There may be one test that fails under JDK 8 but I believe it has been temporarily excluded.


pkgs-lib/shell: sudo nixos-generate-config

$ btrfs subvol show / >/dev/null; printf "%s\n" "$?"
ERROR: Could not search B-tree: Operation not permitted
1

Btrfs's ioctl() BTRFS_IOC_TREE_SEARCH requires elevation. btrfs subvol show <path> may be called by nixos-generate-config, and if btrfs subvol show <path> fails then nixos-generate-config fails.

Thanks for the PR! That sounds good to me.
We are actually in the process of completely moving the devos library to https://github.com/divnix/digga. So your change won't have any affect after #276 is merged.
It would be great if you could switch your PR to target digga instead. It should be the same thing except src/pkgs-lib/shell.

If #276 will cause core to be based off of up-to-date digga, then could this still be merged to core here as a backport?

develop is probably going to be merged into core in a matter of minutes, so we are on kind of a "freeze" on core at the moment.

your fix just made it in https://github.com/divnix/devos/commit/634cfcb30162b18f194cb2ca90a54a5c937cba3c
Thank you :)


WIP: Refactored mdoel name validation functionality

Ref https://github.com/Activiti/Activiti/issues/2860


refactor: integration test suite

Move helper functions to own file
Use physical rather than logical CPU cores for parallel runs
Add verbose flag when running on CI, which makes it much easier to debug failures

Oh damn, it should be requested changes, sorry about that. Could you still remove?

Oh damn, it should be requested changes, sorry about that. Could you still remove?

I did, but I forgot to push...
Sorry about that, opened https://github.com/prefix-dev/pixi/pull/2083


resolves STREAMS-588

fixes streams-examples / .. / TwitterFollowNeo4j
by adding a way to clear zero-size objects, empty arrays, and null / empty values out of objects en-route to neo4j
and improving testing in PropertyUtil

lgtm +1


Calendar UI Bug - Left / Right Navigation - Invalid Header

I'm submitting a ...  (check one with "x")

[x] bug report
[ ] feature request

Issue description

Current behavior:

The header of the "Calendar" component does not update as expected while using the left / right navigation buttons.
Expected behavior:

The header of the "Calendar" component properly updates while using the left / right navigation buttons.
Steps to reproduce:

Navigate to:  https://akveo.github.io/react-native-ui-kitten/docs/components/calendar/overview#calendar

Observe that using the right navigation button  does not update the Calendar header, and using the left navigation button produces an unexpected jump in months.

NOTE:  If the website is unavailable in step 1, you can insert a "Calendar" component into a demo project from the 4.3.0-beta.1 build.

Related code:

Render the following component:
import { Calendar } from 'react-native-ui-kitten';

const ExampleComponent = () => {
    return <Calendar date={ new Date() } onSelect={ () => null } />;
}

Other information:
OS, device, package version
MacOS 10.14, 4.3.0-beta.1

Thanks for reporting this and #712. I've reviewed your PR #714 and left a comment on this. We can use this PR for the future discussion


1.15 update (required changes)

Loom updated to 2.7
updated Yarn+MC version
updated trinkets
fixed 2 lines of code
probably could update loader_version
would need a version bump

Go ahead and update loader, bump yarn to the v2 spec, and bump the version in gradle.properties while you're at it.

done


Heap security issues

crashes.zip
There are some heap vulnerabilities-mainly use after free and heap buffer overflow, in box-dumper processing .mov files which I think come from the library.
Attached are some files that cause crashes.

#include "lsmash.h"
#include <stdio.h>
#include <stdlib.h>
int main(int argc, char* argv[]){
	if(argc!=2){
		printf("Usage: %s file", argv[0]);
		return 0;
	}
	lsmash_root_t *root = lsmash_create_root();
	if(!root){ printf("root is NULL"); exit(0); }
	lsmash_file_parameters_t file_param = { 0 };
	if(lsmash_open_file(argv[1], 1, &file_param)<0){
		exit(0);
	}
	int dump_box = 1;
	if( dump_box )
        	file_param.mode |= LSMASH_FILE_MODE_DUMP;
	lsmash_file_t *file = lsmash_set_file( root, &file_param );
	if(!file){ printf("Failed to set file"); exit(0); }
	if( lsmash_read_file( file, &file_param ) < 0 ){ printf("Failed to read file"); exit(0); }
	/*if (dump_box) {
		if(lsmash_print_movie(root, "-")<0){
			printf("error printing movie");
		}
	}*/
	uint32_t id = lsmash_create_track(root, ISOM_MEDIA_HANDLER_TYPE_VIDEO_TRACK);
	lsmash_delete_track(root, id);
	if(lsmash_activate_file(root, file)<0){
		printf("Error activating file");
		exit(0);
	}
	lsmash_box_t *box = lsmash_file_as_box(file);
	if(!box){
		printf("Error converting file to box");
		exit(0);
	}
	if(lsmash_add_box(box, box)<0){
		printf("Error adding box to itself");
		exit(0);
	}
	lsmash_destroy_box(box);
	lsmash_close_file(&file_param);
	lsmash_destroy_root( root );
	return 0;
}

This is the code the fuzzer ran on. Running any of the files in the crashes.zip as an argument to this program causes a segmentation fault that is exploitable.

I don't know if @VFR-maniac is retired or not, but I'll take a look at these over the holiday period if I get a chance, and send a PR here + update our fork.

Thanks.
Is there a way to debug I'm trying to see where the issue is so I can submit a PR to fix it.
Whenever I compile with "-g" the binary is still stripped without debugging symbols.

configure --enable-debug

I tried that flag but for some reason when I debug it the source code isn't showing even with "-g"


Drop support for Python 2.x

Current coverage is 82.90% (diff: 100%)

Merging #21 into master will decrease coverage by 0.25%

@@             master        #21   diff @@
==========================================
  Files             3          3
  Lines           398        392     -6
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            331        325     -6
  Misses           67         67
  Partials          0          0

Powered by Codecov. Last update 4786cbe...0da45e7

Current coverage is 82.77% (diff: 100%)

Merging #21 into master will decrease coverage by 0.38%

@@             master        #21   diff @@
==========================================
  Files             3          3
  Lines           398        389     -9
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            331        322     -9
  Misses           67         67
  Partials          0          0

Powered by Codecov. Last update 4786cbe...af33967


Updated base cost to 800 USD and fee naming

Baseline cost from 400 to 800 USD (but keeping the industry one at 2000 USD).
Fee is now called "Tuition fee" instead of "Registration fee", in order to be consistent with the website and the portal.

@ebatty you merge this ASAP, please?


Databricks Support for Table ACL

Summary
Add support to Hive & Databricks for dbproperties / tblproperties and table ACL
Related Issue: #IssueId
PR Type: Feature
Status: Ready to review
Breaking change? No

Codecov Report

Merging #82 (b9289fe) into master (fdd8fb4) will decrease coverage by 0.27%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##           master      #82      +/-   ##
==========================================
- Coverage   66.98%   66.71%   -0.28%
==========================================
  Files         120      120
  Lines        5004     5035      +31
  Branches      249      267      +18
==========================================
+ Hits         3352     3359       +7
- Misses       1652     1676      +24

Flag
Coverage Δ

unittests
66.71% <25.00%> (-0.28%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ala/ai/starlake/job/ingest/DummyIngestionJob.scala
0.00% <ø> (ø)

...scala/ai/starlake/workflow/IngestionWorkflow.scala
44.82% <0.00%> (-1.61%)
:arrow_down:

...in/scala/ai/starlake/job/ingest/IngestionJob.scala
62.90% <24.00%> (-1.69%)
:arrow_down:

src/main/scala/ai/starlake/utils/Utils.scala
92.15% <83.33%> (-1.18%)
:arrow_down:

...ai/starlake/job/index/bqload/BigQueryJobBase.scala
36.84% <100.00%> (-2.29%)
:arrow_down:

...main/scala/ai/starlake/privacy/PrivacyEngine.scala
85.18% <0.00%> (+1.23%)
:arrow_up:

Continue to review full report at Codecov.

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


IdentityVisitor loses source locations

Add an update method to nodes that preserve extra information or modify IdentityVisitor.

Fixed in ad9460afe48b34ee2bc5e97067686796653da2d0.


New callable param to deal with non hashable positional and/or keywords args

Creating a callable param (hash_params) to generate a key when positional and/or keywords arguments are not hashable.
It can work as a workaround in scenarios that positional and keywords args are not hashable but one can be generated with a properly method for each case
For example, a pd.DataFrame object can have a key using the following command: hashlib.sha256(pd.util.hash_pandas_object(obj).values.tobytes()).hexdigest()

Suggested tests created

I've added documentation and released this in version v1.4.2.


Support for typeorm v0.3+

Recently typeorm updated their package to 0.3 which changed connection methods.
So getConnection doesn't work.
https://github.com/typeorm/typeorm/releases/tag/0.3.0

Anyone have a work around for this?

Anyone have a work around for this?

I think you could do something like this:

  const connection = await new DataSource(require('../orm.config.js')).initialize();

  ApolloServerLoaderPlugin({
        typeormGetConnection: () => connection,
      }),

However, I believe upgrading TypeOrm to 0.3 is breaking a dependency. I am getting Cannot find module 'typeorm' error from the dataloader

In 0.3 Typeorm just renamed Connection to DataSource, so @CMethoddata's snippet works (that's what I'm using). I'm on Typeorm 0.3.6 and using this library successfully.


Provide a update-goal parameter: add if missing

Suppose you have a year mentioned in your header and your project is long lasting which means the code is produced over years.
If you change the year in your header, all files will be changed - not only the new ones. I understand this behaviour is needed in some use cases but is unwanted in the one described above.

Yes I agree.
Please provide a pull request :-)

duplicate of #81


Intermittent startup error

thread 'sel_ldr' panicked at src/safeposix/syscalls/fs_calls.rs:515:66:
called `Option::unwrap()` on a `None` value
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: core::option::unwrap_failed
   4: rustposix::safeposix::syscalls::fs_calls::<impl rustposix::safeposix::cage::Cage>::stat_syscall
   5: rustposix::lib_fs_utils::visit_children
   6: rustposix::safeposix::dispatcher::cleartmp
   7: lindrustinit
   8: NaClSelLdrMain
             at /home/lind/lind_project/src/native_client/src/trusted/service_runtime/sel_main.c:455:3
   9: main
             at /home/lind/lind_project/src/native_client/src/trusted/service_runtime/nacl_test_injection_main.c:11:10
  10: <unknown>
  11: __libc_start_main
  12: _start

This seems to stem from socket inodes being leftover and not being dealt with in the log based file system.


Pier should exit unsuccesully on failed script

Currently pier won't exit unsuccessfully even if the script being run does.
One way to do this would be to check for an unsucessful exit with the Output struct that we get back from the command and if it's unsucessful return an error like ScriptError with pier_err! and then in the main function compare the error returned using the EnumKind proc macro that is applied to the PierError enum.
An example of this type of comparison on errors can be found in these files tests/macros.rs and test/error_handling.rs.
Links:
[https://doc.rust-lang.org/std/process/struct.Output.html](Rust docs - std::process::Output)
[https://docs.rs/enum-kinds/0.4.1/enum_kinds/](docs.rs - enum_kinds)

fixed in #53


Item 5767: Secure ODBC connections

approved mirror pr: https://github.com/LabKey/platform/pull/333

Almost certain that my testing did work here, but I've asked Ankur for confirmation via email.

Confirmed with Ankur that my testing was correct and the results that came from it were expected. I think we can merge these pull requests.


[feature request] Add WikiLink

very thanks for your useful plugin first! these days I encounter some trouble when formating wikiLink markdown file, for example
[[some page]]

after format this file, this change to
\[\[hello\]\]

the wikiLink not work properly now...
github wiki now support this format , can you add this feature?

Interesting, so it looks like the GFM spec (https://github.github.com/gfm) does not have wiki links, but when you have the "Markdown" format selected when editing a Wiki page they are converted to internal links anyway and you don't have to switch to something like the MediaWiki edit mode (https://www.mediawiki.org/wiki/Help:Formatting from wikicloth of https://github.com/github/markup).
Given that the wiki links don't appear to be documented as part of GFM, my first thought is that the feature would need to be a separate package to support users who want the strict implementation of GFM.
However, you're in luck because a package already seems to exist and you can use it today: https://github.com/tmr232/mdformat-wikilink 🎉
Let me know if mdformat-wikilink solves your issue

yes, it does work! but I don't see this plugin in mdformat docs, so maybe I should take a pr for it 😄


Does Classification Label only support multi-label classification?

I have multilabel classification labels, can I use Tensorbay to manage my dataset?

Hi, thanks for your interest in TensorBay.
For better solving your problem,
can you please paste one or several data samples and their multilabel classification labels here?

Hi, thanks for your interest in TensorBay.
For better solving your problem,
can you please paste one or several data samples and their multilabel classification labels here?

https://www.google.com/url?sa=i&url=https%3A%2F%2Fwww.kaggle.com%2Fc%2Flish-moa%2Fdiscussion%2F180500&psig=AOvVaw13cKP4pzaF6R3-CeMxYoCN&ust=1622542114440000&source=images&cd=vfe&ved=0CAIQjRxqFwoTCLDOlcnW8_ACFQAAAAAdAAAAABAD

Hi, thanks for your interest in TensorBay.
For better solving your problem,
can you please paste one or several data samples and their multilabel classification labels here?

https://images.app.goo.gl/3DGJj2DLJsxXrrZU7

Another thing is that your customer service guy, whom I scanned the QRcode from your website and added via WeChat, does not reply anything

Hi, thanks for your interest in TensorBay.
For better solving your problem,
can you please paste one or several data samples and their multilabel classification labels here?

https://images.app.goo.gl/3DGJj2DLJsxXrrZU7

Hi，we may support multi-label classification in the future.
Currently, you can use the following solution：
from tensorbay.label import Classification

classification_label = Classification(
    attributes={
        "Dog": True,
        "Cat": False,
        "Horse": False,
        "Fish": False,
        "Bird": True,
    }
)

Another thing is that your customer service guy, whom I scanned the QRcode from your website and added via WeChat, does not reply anything

We are sorry for your bad experience when using our Python SDK.
Here is the QRcode of our WeChat users group.
Please use WeChat to scan and join in.


Refactor embedder service protocol handler API

[ ] We need to be able to reply to the request asynchronously.
[ ] We need to be able to push events.

Assuming this is stale.


AMD ROCm: Conformer-transducer diverges

Describe the bug
Making this issue mostly for myself, and to track/document/point others to the problem.
The LibriSpeech conformer-transducer recipe fails to train with the stock parameters. The loss remains high, and there are non-finite loss warnings every few batches (but not every).
The NaNs seem to appear even in the forward. This might be an upstream bug but we don't support another NaN loss that can be made to work with AMD ROCm (yet).
Only tested with fp16 so far. bf16 cannot be tested since the torchaudio transducer does not support it.
The NaN loss seems to originate from the transducer loss but it might not necessarily be the direct culprit.
The non-finite loss doesn't seem to reproduce:

On the LibriSpeech conformer-large CTC recipe
With fp32 it seems okayish so far, but there are oddly still a few Patience not yet exhausted. messages.

Expected behaviour
Model should succesfully train.
To Reproduce
Train the model on a MI250X (e.g. Adastra) with fp16 on stock parameters.
Environment Details
Latest develop.
Reproduces on 1x and 8x MI250X GCDs. Running on CINES' Adastra.
Custom compiled torchaudio from ROCm/audio's release/2.1_add_rnnt branch (can provide instructions if anyone is interested).
Relevant Log Output
No response
Additional Context
No response

If this doesn't reproduce with CTC alone (need to check), one option would be to use #1465 and to fork k2's fast_rnnt with HIPify support.
Maybe this is related to issues we were encountering on #2533 but I doubt it.

Currently poking around the pruned RNN-T loss and managed to get something to start converging, so it's not some catastrophic kind of issue.


andisatya.atlassian.net

http://andisatya.atlassian.net
Thank you for contributing! Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[ ] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[ ] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

``http://andisatya.atlassian.net

Use Payment BarterPay at https://www.barterpay.blogspot.com for transaction
for Business ecommerce.
Love
SINAR SEJAHTERA
Pada Kamis, 18 Juli 2019, rachelbruner<EMAIL_ADDRESS>menulis:

@rachelbruner approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/explore/pull/873?email_source=notifications&email_token=AMTLZG3POBYS4U3O6SYPIB3P77ZVJA5CNFSM4IEUPYUKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB6ZZZ2A#pullrequestreview-263429352,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMTLZG47GGWLUTWMRXPK5L3P77ZVJANCNFSM4IEUPYUA
.

--
null


fix: Chat completion 401 when no Authorization header

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[X] Target branch: Please verify that the pull request targets the dev branch.
[X] Description: Provide a concise description of the changes made in this pull request.
[ ] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for validating the changes?
[X] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[X] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description

When we send a request to /api/chat/completions without the Authorization header, the server just crashes and creates a stack trace, returning "Internal Server Error" to the calling client because of a KeyError. With this fix, the server sends a 401 to the client with the content {"detail": "Not authenticated"}.

Fixed

Add a try/except handle the case where there is no Authorization header. Returns status 401 Not Authorized and {"detail":"Not authenticated"} body if the header is not found.

Good catch, Thanks!


Update the build process

Summary of Changes

Use pyproject.toml and where necessary, setup.cfg.
Use python -m build

Will this PR fix the deprecation notice?

DEPRECATION: sphinx-sitemap is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559

If not I can file a new issue. Please let me know. Thank you!

It should, is there a way I can replicate the current deprecation notice?

Here's an example GHA build:
https://github.com/plone/documentation/actions/runs/3749024374/jobs/6367030809#step:5:126
And to build the Plone docs locally, you can follow our guide:
https://6.docs.plone.org/contributing/setup-build.html
Pretty much, clone and make html, and you're done. You can skip installing Vale.

BTW, the maintainer of livereload just uploaded a wheel, we now install wheel in our requirements, and the deprecation notice for that package went away. See https://github.com/plone/documentation/issues/1395 and https://github.com/lepture/python-livereload/issues/240

I just released a new version and the 2.3.0 files show a .whl now, this should fix your issue. Thanks for pointing that out!

Thank you for the quick response!


runV support

Hi,
I'm one of the maintainers of Hyper container and runV: github.com/hyperhq/runv.
Does kubevirt plan to support full-blown VM only, or include virtualized container like runV in the future?
Thanks.

Hey Gnep,
the primary purpose of kubevirt is to support full-blown VMs - from an API POV.
We are not trying to solve virtualized containers.
But because VMs are involved in both approaches, to me it is still an open question if the implementations for the two use-cases could align - in one way or the other - over time.

I would assume it should be fairly easy to run a VM that specializes in running containers, such as https://getfedora.org/en/atomic/

es, running atomic, or boot2docker are options. But also running a kubelet within the vm (like minikube).
In that case a VM could become another node of the cluster (self hosted), and you get the vm isolation for all the pods within that node.

Pretty late to the discussion.
@Gnep do you have something specific in mind? Afaik, hyper is  built in a way, that it is transparent to kubernetes, right?

@rmohr
Yes, we have a project to integrate Hyper to K8s via CRI: github.com/kubernetes/frakti. It would be great to support kubevirt in frakti too.
Also we just submitted Stackube https://review.openstack.org/#/c/462453/. The idea is to mix Container (Hyper) and VM to the same class of cabin, and share the implementation of Cinder/Neutron, etc.


feat: get token from wellknown endpoint

fix: improve color in light terminal
fix: disable auth command for linux

Using #187 instead


Change spaces used for indentation into tabs

Resolves #28, supersedes #330
This brings consistency to the entire project, where much of the existing code already used tabs.
Tabs are a natural choice for indentation. It's semantic, one character per one indent. It's easy to adjust. It's easy to recognize indentation errors where indentation is significant (ie, Python). Especially for this last reason I feel this is one place where PEP8 has made a grave mistake.
Note that this PR is not to debate tabs vs spaces nor PEP8, as maintainer we are decidedly tabs. Comments reserved for reporting missed conversions, regressions, or conflicts.

Merging early to minimize potential future merge conflicts

And how many bytes were 'saved' by this commit? :rofl:


A11y_Azure Tools Storage Explorer_Activities_Activities tab_ScreenReader: When the voiceover is turned on and the user uses Control + Option + Arrow keys on successful message notification, the focus is moving to 'tick' mark decorative image.

GitHubTags: #A11yMAS;#A11yTCS;#A11ySev2;#BM_AzureToolsStorageExplorer_May2022;#Azure Tools Storage Explorer;#MAC;#FTP;#DesktopApp;#WCAG1.3.1;#Voiceover;#AINotInScope;
Environment Details:
Application Name: Azure Tools Storage Explorer
Application Version: 1.24.0
Mac Version: macOS Monterey 12.3.1
Screen Reader: Voiceover
Repro Steps:

Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after verification of the fix.
Launch Azure Tools Storage Explorer.
Sign in to Azure.
Tab to 'Explorer' pane tree view.
Navigate to any of the file inside "Blob Containers"
Tab to 'Activities' tab.
Tab till any of the successfully completed message.
Turn on voiceover and use VO + Arrow keys (Control + Option referenced as VO)

Actual:
When the voiceover is turned on and the user uses Control + Option + Arrow keys on successful message notification, the focus is moving to 'tick' mark decorative image.
Expected:
When the voiceover is turned on and the user uses Control + Option + Arrow keys on successful message notification, the focus should not move to 'tick' mark decorative image. Decorative image should have null alt text (alt="") so that can be ignored by assistive technologies such as screen readers.
User Impact:
Screen reader users may not be able to understand the purpose of the image when used for decorative purpose.
Attachment:

@bbarik06 can you clarify what you would expect voice over to read as you press the various possible arrow keys, starting from voice over focusing "Clear completed".
So for example, in your reply I am looking for something like:

"Clear completed" focused
ctrl + option + right arrow
"Clear successful" focused
ctrl + option + right arrow
etc.
etc.
etc.

I would suggest you not to bring focus to the 'Decorative image' since the information that you want to attach with it such as 'Clear successful' is already present with the text message beside it in the form of text 'completed'. From accessibility point of view, focus should not move decorative image.

The green checkmark is not decorative. It is used to convey the state of the activity (success), so we need to see if we have an appropriate alt text.

@craxal  this issue is specifically to screen reader users, if you provide alt text to the image then the announcement will be redundant, as the same text is available beside the image. So we will request you to keep the alt-text blank and not to have focus move to the tick image.

@Shivamd1 Activities have a "status" property as well as a "message" property. The image reflects the value of the "status" property, which is independent of the "message" value. Therefore, it can, in theory, convey information that is not in "message". Therefore, this information should not be discarded for screen reader users. Visual users can quickly verify the status of an activity by looking at the icon. From a usability standpoint, screen reader users would not get this same benefit if it was treated as purely decorative.
To complicate things, even if we were to set alt="", the image is not in an <img> element, and therefore there is no alt attribute for us to modify. It is an inline SVG, and the standard way for providing alternative text is to include a <title> element. But we seem to have conflicting requirements for screen reader + mouse users in that regard (see #3506).

@craxal Please join office hour call for further clarification<EMAIL_ADDRESS>

Hi @bbarik06
Please verify that this bug is fixed using the Storage Explorer build at: https://storageexplorerpublish.blob.core.windows.net/privatebuilds/20220624.3-accessibility-testing/StorageExplorer-darwin-x64.zip


Axis directions

Coordinate origins should be
X=0 -> Left side of screen
Y=0 -> Bottom of screen
Z axis -> Positive direction pointing out of screen

At least the Z direction should be fixed with d5752c3dbbacd062d0a259543123685fbd3c8c24


How to get the moves made in a game?

How can I get the moves made in a game (like 1. e4 e5 2. Nf3 Nc6 etc.)?

SebLague Has updated the repo with this! Then again this is 5 days old, and you probably noticed, but for anyone else with the question there you go!
P.S. Can you close this now?


BadUSB: Honk.txt - Fix powershell is not starting

Fix suggested by @Svaarich

Hey, I’m new here!


Change attribute/property binding syntax to require opt-in to properties.

The current syntax of lit-extended sets properties by default and requires opting out of properties to set attributes with the $ suffix.
This has a number of downsides:

The default of setting properties is different from plain HTML
When you add a binding to an attribute it changes from an attribute to a properties
There's no syntax indication that some behavior is different from HTML
Case-sensitive attributes like viewBox are harder to implement
The syntax isn't a super-set of lit-html core

This issue is to document the rationale for changing the syntax to set attributes by default and require opt-in to properties with a . prefix.
Compison
Current syntax:
html`<input id$=${id} value=${value} required?=${required} on-change=${onChange}>`

Proposed syntax:
html`<input id=${id} .value=${value} required?=${required} on-change=${onChange}>`

And for consistency, we could go further and make all binding modifiers be single-symbol prefixes, like:
html`<input id=${id} .value=${value} ?required=${required} @change=${onChange}>`

I'm liking the last option the more I look at it. It places the modifier in a consistent place and away from the other symbols required for a binding (=${ or ="${) so it stands out more.
I think it'll be nice with a lot of bindings, when I typically put each attribute on a separate line:
html`<input
       id=${id}
       .value=${value}
       ?required=${required}
       @change=${onChange}>`

There the binding type is very clear.
The downside is that @ is a new symbol and might not be obvious to first-time readers. On the other hand we should optimize for the repeat reading of daily users.

Definitely the last option. The one right under Proposed Syntax feels very confusing to me, personally.

How about this version? This is something that we are already using but if possible on-change is preferable instead of introducing more symbols.
html`<input
             id=${id}
             value.=${value}
             required?=${required}
             change@=${onChange}>`

I personally prefer the clean-slate (everything changes together consistently) including where you put the modifier. Everything else has a bit of hysteresis.

@motss my problem with that is the run of symbols between the attribute name and value. The modifier gets very lost, imo.

The bias for me being left to right is how I read, and what @justinfagnani just stated.

My vote is:
html<input              id=${id}              value:=${value}              required?=${required}              change+=${onChange}>
But I haven't really thought it through.

And regarding a new symbol: I partially agree, but after looking at the examples for a bit I find on- to stick out. I also like that all the prefixes don't work with setAttribute() so they're very unlikely to clash with real attributes.

The third option seems the most consistent to me; and as @appsforartists just said, @<event> is growing on me as an easy way to distinguish magical lit sugar from standards.

Special symbols and characters are something you usually regret over time. It's harder for people to learn. on-click is something everyone immediately understands.
Defaulting to attributes is definitely the right call though!

I like the .prop, ?optional and @event character prefixes. Well worth the change long-term and better than the current way where normal looksjustlikeanattribute="" really means a property but isthisanattribute$ is an attribute. Also, I think the on- prefix for event handlers is slightly confusing and people don't always realize it's part of lit compared to the normal platform on... handlers
Feels like the prefix characters being first would also make things slightly easier when you have to create regexes for tools like html minifiers to ignore certain parts of the templates. It is also nicer having them away from the ${} part plus they would line up if put onto separate lines (all the props together etc...)
"make it so!" in best Jean-Luc Picard voice ...

Overall huge fan of the proposed attribute by default, property with dot prefix. And moving the boolean attribute to prefix for consistency seems good too.
I'm on the fence regarding the @event syntax. I'm mostly concerned about introducing too many symbols, making html harder to parse at a glance. It's starting to exceed my weirdness budget, as you folks like to say. On the other hand I'm usually initially heavily biased against change, so if I'm neutral about it now I'll probably think it's a good idea later.

I'm really ambivalent, just throwing out concerns in case any of them might be important.  Yeah, if easier to parse, that's a strong argument.  On an aesthetic level, I remember the Scala language "guy" explaining why he put types after the variable name,  which seems to be a trend.  What's important comes first.  What type it is comes after, because it's a technical detail.

I'm wondering if !event works better than @event? For me it denotes 'action' more which fits better and the @ is a bit 'heavy' and '!' should align with the '.' prefix and fit with '?' as well ... all "dot at the bottom"

The @ is also the decorator symbol in JS, or was the decorator feature dropped from spec? Either way, Angular uses @ as a decorator.

Using fancy symbols is kind of the way how Angular does this if I remember correctly. I think I'm comfortable with @justinfagnani 's idea.
html`<input
       id=${id}
       .value=${value}
       ?required=${required}
       @change=${onChange}>`

But then there is another question is that which symbols are much more appropriate to be used so that it makes sense to many of us. We might need a poll for that. I also have an idea like attribute we can probably use [value]=${value} which inspires by CSS selectors.

how would @change="${onChange}" affect #145 ?

Also, I've seen event names beginning with @ in the wild, would lit choke on those?
html`<my-el @@event="${onEvent}"></my-el>`

I like the prefixes, . works for properties, but @ instead of on- might be a little confusing for events. @ prefixes are already used in far too many places already.

Personally I love agree with most of the above (+ for everything, issues with @). I would argue about ! though as it is a boolean not and many people would confuse it. There are not many symbols though to be used and neither looks like "this is an event" out of the box. Also as @bennypowers pointed out, there might be events that start with @ and probably ones that start with any symbol, so dunno if that's an issue for us.
What you guys think about * for events, like <my-el *click="${listener}">? The only thing that comes to my mind when looking at * is wildcard, but that would mean every, so *click could translate to every click.

I like @Draccoz's idea, but there might be some overlap with generator function* syntax.
To me generators suggest RxJS/observable patterns, so repeated events with asyncAppend or asyncReplace.
I'm not sure whether that's a good thing or a potential confusion.

Almost every symbol means something :D. Unless somebody suggests something really good, we will just have to pick the least confusing out of the confusing ones :(.

^change or ~change or :change ;-)
The latter is like assign to/subscribe to, so works for me

@KeithHenry, since lit-html is a separate parser system, we shouldn't restrict its syntax with anything exists in JS. Even if * is taken for generators and @ for decorators, they can be used in lit-html because it is not JavaScript

@Lodin Can't agree with that. It may not be JS, but it's still closer to JS than funky templating systems (closer to JSX, which kinda still is JS). That means most of the people using lit (if not all) will be JS devs, and they should not be mislead by different meanings of the symbols they are used to.
However, we don't (and probably wont?) have generators/decorators passed like that in lit, so we may use either symbol. Still though, it should be as intuitive as possible.

@Lodin if it's not JavaScript, then what it is? (don't say TypeScript 😄)

@moebiusmania I think he means this is not imperative pure JS code (like document.createElement('my-element').value = '...'), but an abstract syntax lit-html specific :).

FWIW (🚴♀🏠) @ LGTM, with my above provisos. "at" and "on" are almost synonyms.

the latter with @ LGTMT

I think @ for events is nice because when you say "at" it's quite similar in meaning to "on" but in a way you can't confuse with the platform properties for event listeners. Definitely not a fan of use "!" as it makes me think of "not" which has nothing to do with events, and using "*" makes me feel like I'm missing something.

How about literal prop({someProp: val})and event({someEvent: fn}) ... this way you can have a map of props or events prop(propsMap) and event(eventsMap)

Naively speaking. Have yet to use lit-html and the ergonomics of proposed and existing syntax is after all just ergonomics, nothing that we can determine objectively. Maybe just make it user defined syntax with default being the ., ? and @ prefixes?

@lodin that wasn't really my point - we can use pretty much anything we want, but ideally it should confuse devs used to JS syntax as little as possible. To me @ suggests users or decorators, ! means not, and * suggests subscription to an observer (rather firing an event that might be consumed by an observer).
We could make any of them work, but ideally we'd pick one that feels intuitive.
Personally I might go for + as I'm used to .NET's subscription syntax +=.

You could go the opposite direction and make on-event the syntax you keep, so:
in-property=${valueForPropertyOnly}
if-attribute=${booleanForExistenceOfAttributeAndProperty}
on-event=${eventHandlerToBeAdded}
attribute=${valueForAttributeAndProperty}
Hyphenated attribute names already raise a flag when reading, and polymer users are already familiar with the on- prefix, even if I'm still confused.  Progress on a learning curve is a terrible thing to waste.
Also, you won't be struggling to find the right single character for:
set-property=${writeTraceForProperty}
get-property=${readTraceForProperty}
whenever they or other proposals come up.

@recri That's going to be fun for a lot of existing web components. Most actively avoid on-event or (React style) onEvent, but there will be lots of in-property/inProperty and if-property/ifProperty attributes out there.
on- is an existing convention, but for maximum interopability new prefixes need to be invalid in setAttribute calls.

@KeithHenry for those used to .NET + might feel convenient, for me it sums numbers or concats strings :P.
@recri That convention would bring even more confusion, like in-name="${userName}" or if-age="${userAge}", doesn't feel natural, especially the latter feels like it's a question about the property/attribute itself, not the value passed to it. The set-property looks better, but would confuse people with setAttribute.
To sum up: I have never ever seen a framework or library that uses verbose prefix to indicate property. True that Polymer community is used to on-event, but they are also used to attribute$ :P.

I'd like to restate my argument for why I think it's better to put the property modifiers at the end of the property name rather than the beginning:

It is argued that they stand out more by being at the beginning.  I would argue that we want these distinctions, especially between attributes, object/string properties, boolean attributes, to be subtle, not jarring.  Yes, technically they are important, but starting off with a strange symbol would detract from the more important name of the property.  Having them at the beginning looks more -- nerdy?  Kind of like regular expressions, which tends to scare developers away

I think ergonomically it is better to be able to type a word for a property, then lift one's hands and deal with all the characters off the main typing area in one go, rather than two.

I'm thinking events should be different.  Maybe events should come at the beginning.  I'm thinking of the css hover:  a:hover.
So my new revised proposal is:
html`<input id=${id} value:=${value} required?=${required} :change=${onChange}>`

I don't think what any other language (including JS) uses for symbols really matters. This is a DSL to generate HTML templates so that should really be the main focus, not how any symbol is used or what it means elsewhere - so many languages, all different.
Having the attribute syntax align with HTML attribute usage is definitely an improvement as part of that. We just want to come up with a clear and simple way to indicate properties and events.

I like
html`<input id=${id} .value=${value} ?required=${required} @change=${onChange}>`

Although I don't understand why we need the ? syntax at all. I'm not familiar with the internals of the package but can't we just check the value type and behave accordingly? The logic could look something like this:
if (val === true) {
  el.setAttribute(attr, "");
} else if (val === false) {
  el.removeAttribute(attr);
} else {
  el.setAttribute(attr, val);
}

If you really want to bind the string representation of the boolean you can still do that explicitly by wrapping it in quotes. I.e.:
html`<div active=${true}></div>`

would render as

While
html`<div active="${true}"></div>`

would result in

This is much closer to what I would expect coming in unbiased (if fact the second case is identical to what would happen in vanilla template literals) and since the whole point was to get rid of special syntax when binding to attributes this is a logical step imo.
One could go even further and define special behavior for promises, generators etc as well all of which can be optet out of by simply using quotes.
Finally, I think the prefix should only specify the target, while the interpretation of the value could be consistent across targets. I.e. promises could be handled identically for properties, attributes and even event handlers (of course in the latter case the promise would have to resolve to a function). If the expression resolves to something that isn't valid for a given target (e.g. a boolean for an event handler), an error should be thrown.

@KeithHenry, @Draccoz, @moebiusmania, I suppose, @CaptainCodeman said everything I wanted in the better way. I believe if lit-html syntax is restricted basing on any other language it would harm lit-html's expressiveness. Moreover, I cannot imagine how decorator's @ could mix up with event's @: they are completely different. It's almost like comparing twitter's @ to JS decorator's @.
Anyway, I would vote for the following solution:
html`<input id=${id} .value=${value} ?required=${required} @change=${onChange}>`

IMO, it is very expressive and consistent solution.
BTW, why not to create poll anywhere, e.g. in twitter?

I do agree with @Lodin and @CaptainCodeman, and my only issue with @ are mentions on slack (would have same issues to # :P). Other than that, @ does look like the best candidate for me, as it kinda is synonym for on (like @bennypowers pointed out).
Over all while still having personal favorites, I would be happy with either symbol.
Besides of events, I think most of us agrees for the rest?
@MaKleSoft Personally™ I would prefer to avoid things like auto magic inside lit. If we had lit to decides what to do, we may end up with use cases where it does not what we expect it to and sometimes it might be hard to fix.

@Draccoz, regarding Slack: if you use triple backtick block for code (or snippet which is even better), it won't create any mentions. And you have to use this block anyway because if you don't Slack will highlight all your string between html's backticks (and won't create mention anyway :) ).

I know that very well, kept reminding people about it all the time (sometimes I get tired of it though and ignore it...). We - slackers - are aware of it, but hell-of-a-lot of newcomers either don't know it or don't care about it, this is the potential source of infinite mentions (EmpressPolymer and couple of others know it very well since Polymer moved to npm with its own namespace ^^).

@Draccoz Not sure how my proposed solution would be any more magic than what lit already does.  Can you elaborate?

In the current proposal, you can clearly see what is happening, if there is a ? in front, it will definitely be a boolean, if . it will definitely be a property, etc. In your approach it's unclear what is going to happen, if somebody accidentally assigns 1 instead of true to the property (or the other way around by for example negating the value with !), it's gonna change the behavior, which shouldn't happen. This may be easier in TypeScript (which hints you types etc), but with plain JavaScript it may end up different than desired, and a lot of devs still prefer plain JS over TS.

@Draccoz @Lodin Yeah, avoiding @ for TS decorators is just a confusion thing, but since @polymer/lit-element is planning to support decorators we should consider those users.
However, the @ for usernames is just a personal gripe - we're going to be sharing lots and lots of code on forums like Twitter, Slack and GitHub that treat @ as a username. Yeah, you can work around that, it's something I find annoying.

Thanks for all the fruitful discussion everyone!
I haven't said much yet, because so far there's really good reasoning going on and it's very interesting to just see how people think and feel about this and how that even changes rather quickly based on new comments. I definitely missed an opportunity to spread lots of 🚲and 🏠emoji throughout this issue!
I wanted to drop a couple of responses, though, maybe most importantly this:
from @Lodin:

BTW, why not to create poll anywhere, e.g. in twitter?

Mainly, because that might give the impression that the poll winner should "win". There are a lot of inputs to this decision, like how people feel, how intuitive it is, how familiar it is to other syntaxes, how easy it is to parse, consistency, etc. It's not a fully democratic decision. Even if it were, we all know how accurate internet polling is, and who knows what fraction of the future user-base the poll would actually reach.
And finally, because this is at least in part a subjective decision, as is all bike-shedding, there's an element of taste and even tastemaking here. We're going to take everything into consideration and try to make a decision that makes a cohesive whole.
What's really interesting here is that this is a decision just for the default syntax. The unopinionated core will remain, and it's very easy to make your own syntax. This is the entirety of the Option 3 syntax implementation:
export const partCallback =
    (instance: TemplateInstance,
     templatePart: TemplatePart,
     node: Node): Part => {
      if (templatePart.type === 'attribute') {
        const name = templatePart.name!;
        const prefix = name[0];
        if (prefix === '.') {
          return new PropertyPart(
              instance, node as Element, name.slice(1), templatePart.strings!);
        }
        if (prefix === '@') {
          return new EventPart(instance, node as Element, name.slice(1));
        }
        if (prefix === '?') {
          return new BooleanAttributePart(
              instance,
              node as Element,
              name.slice(1),
              templatePart.strings!);
        }
      }
      return defaultPartCallback(instance, templatePart, node);
    };

Now, we probably don't want a massive proliferation of syntaxes out there, but if some company, major widget library, or framework that uses lit-html wants to have a different opinion here to use across their templates, they can. @bgotink already has an Angular-inspired syntax which has quite a few additional features: https://github.com/bgotink/lit-html-brackets
Now some specific points:
One way to do something
I didn't mention this before, but I really want there to be one and only one way to do something. Since we can't do anything but set attributes when there's not a binding, this would require that the default binding is to attributes and that there is no other attribute syntax. So no :foo or similar for attributes.
LHS vs RHS positioning
For properties and events I'm fairly convinced that the LHS is the right position, so that it's clear at a glance that these are not properties. For boolean attributes I could go either way, since it is an attribute and the ? just modifies how it behaves, but consistency and avoid the symbol jumble are pretty strong arguments to me.
Events: @ vs !
Personally ! looks too much like "not" or "important". Of course @ has several meanings in different web-related contexts, but somehow it looks relatively "right" to me here, and phonically sounds almost event related, as pointed out by @bennypowers.
I just looked and Vue's shortcut for events is @, so that's an relevant precedent. There's even a proposal to add a .foo shorthand for properties, so overall we'd align pretty closely with Vue.
Automatic property setting
This is pretty well ruled out, but I haven't discussed why in this repo yet. There are two big problems here:

We greatly prefer explicit over implicit. I think reading templates and knowing whether an attribute or property is set without having to know about the implementation of the element is useful. Sometimes the automatic choice won't be correct, and then you need syntax to force either attributes or properties, and then you have two ways to do both - automatic and explicit. I think all together it ends up being confusing. I know Preact does this, but that's mostly because they don't have control of syntax in JSX to be explicit.

We want to be compatible with upgrades. Pre-upgrade an element won't have many properties defined, so they'd be set as attributes, and then hopefully pulled in correctly by the element when it does upgrade. This won't work correctly for complex objects though.

Thanks for all the input everyone!
#398 is merged now. We decided to go with option 2:
html`<input id=${id} .value=${value} ?required=${required} @change=${onChange}>`

Note that lit-extended.js hasn't changed, so the next release should be non-breaking, but it is deprecated.
cc @bgotink who maintains a syntax

does this also support setting properties if just provided as a string
html`<my-el .prop="some-string">`

@dakmor No. lit-html doesn't process attributes that don't have bindings. Supporting that might have a perf impact, and would require some API changes. Let me think about this for a little bit...

This syntax does exactly what you want, without any performance overhead:
html`<my-el .prop=${"some-string"}>`

I think it's much easier to explain that lit-html interacts with and only with instances of ${ ... } in your template. Implementing syntax like the property binding suggested by @daKmoR violates that expectation, which weakens the abstraction.
It's a slippery slope. Property setters through attributes are ok, but data bindings are not? It'll just become an arbitrary cutoff point for what 'feels right'. The cutoff for what lit-html interacts with should be ${ ... } which is clear and non-arbitrary.

I totally agree with @ruphin, lit only interacts with template string intersections, the rest is a 100% standard html behavior. If we start messing with those, we end up with a library being far away from the standards (and we aimed at it didn't we?).

@justinfagnani in lit-extended we could bind an attribute like link and the $ would influence the binding such that when foo is undefined, the target attribute would not be stamped to the DOM. With the changes in #398 this functionality appears to be gone -- am I missing something here? Thanks!

@klebba that was actually a bug that ignored undefined for the initial render, but not subsequent renders. Fixing that was not related to the syntax change, but was probably released at the same time.
We've since added the ifDefined directive, which can be used like so:
import {ifDefined} from 'lit-html/directives/if-defined.js';

html`<a target="${ifDefined(foo)}">link</a>`

Would be convenient to be able to accomplish this using template syntax, e.g.

Agree 100%


a readme in Chinese by jqr

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


CLIMATE-640 - Fix missing evaluation variable in time series example

Merged build triggered. Test Failed.

Merged build started. Test Failed.

Merged build finished. Test Passed.


ci: update node and python dependencies

Codecov Report

Merging #85 (2f1c8eb) into main (384f124) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #85   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         1    -1
  Lines           93        24   -69
  Branches         4         3    -1
=========================================
- Hits            93        24   -69

Flag
Coverage Δ

macos-12-clang
?

ubuntu-22.04-clang
?

ubuntu-22.04-gcc
100.00% <ø> (ø)

windows-2022-cl
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

lib/math/include/math/math.hpp
100.00% <0.00%> (ø)

test/math/math-test.cpp

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


Update assignment 4

Still needs a grammar pass ;)
Needs to add diagrams and Gradescope links.

I'm good with this whenever you are. Thanks for the updates.

Thanks for reviewing this, Jason.


Add a (visible) link to the source code for Pext

Maybe I'm just blind, but I couldn't find one on the page.

Fixed in 6a1fd4ef5f4d77d38c009d5eaeb895bf0768aee2, thanks!


Compute family of functions for mutable and immutable Maps

Consider adding
// Possible implementations in terms of public-facing API.

def compute(key: K, f: Option[V] => Option[V]): Map[K, V] =
  f(this.get(key)) match {
    case None => this.remove(key)
    case Some(x) => this.updated(key, x)
  }

def computeIfAbsent(key: K, f: => V): Map[K, V] =
  this.get(key) match {
    case None => this.updated(key, f)
    case Some(_) => this
  }

def computeIfPresent(key: K, f: V => Option[V]): Map[K, V] =
  this.get(key) match {
    case None => this
    case Some(x) => f(x) match {
      case None => this.remove(key)
      case Some(y) => this.updated(key, y)
    }
  }

to immutable Maps and similar operations to mutable Maps (see https://docs.oracle.com/javase/8/docs/api/java/util/Map.html).
These patterns occur fairly often in Java (probably 90% of operations on java.util.Map in my experience).

I think in Scala they would be called updatedWith?  compute seems particularly misleading since they return a modified collection, not a computation on the part of the collection you're asking for.

I would prefer currying these functions for a more flexible Scala API:
def compute(key: K)(f: Option[V] => Option[V]): Map[K,V]
def computeIfAbsent(key: K)(f: => V): Map[K,V]
def computeIfPresent(key: K)(f: V => Option[V]): Map[K,V]

Or even:
def compute(key: K): MapCompute[K,V]

trait MapCompute[K,V] {
   def apply(f: Option[V] => Option[V]): Map[K,V]
   def ifAbsent(f: => V): Map[K,V]
   def ifPresent(f: V => Option[V]): Map[K,V]
}


Sentiment analysis problem

Hi,
Could you please suggest solution for the .sentiment function error
'HTTP Error 429: Too Many Requests'.
It was working fine but then whenever I run it, this error pops up. I was thinking that it must be the textblob-ar is using an API like Google and I need some cool off period, but I tried after leaving it for a whole day. Still the problem is the same.
Thank you

Hi @sadanyh ... I had the same issue. After some Googling it turned out that this is a limit for the Google translate API which limits users to 1000 calls per day. It is really frustrating if true.
@adhaamehab Is there any workaround for this?

Sorry guys, this is limit in google translate api. There is now workaround.

Maybe it would have been better to have this limitation in the library description stated at the landing page. Sadly, after investing some time in installation & coding I was surprised by it.


Validate nested structs

Fixes #367 .
Make sure that you've checked the boxes below before you submit PR:

[x] Tests exist or have been written that cover this particular change.

Change Details:
This change allows using (any: custom or backed in) validations on nested structs.
@go-playground/admins

Hey @zenovich finally found some time to take a look at this, nice work! I've wanted to make all validations run the same way whether structs or fields.
There's only one thing I'm concerned about and that's the order the validations are done.
If I've had validations on a struct and it's fields I would expect that the validations run on the struct first and then the fields, but with these changes looks like is the opposite.
I'll keep thinking about it, if you can come up with something please let me know :)

Hitting the same issue as  @zenovich

Thanks, @deankarn. Sorry for the delay. I think we cannot treat a piece of data as a struct if it doesn't pass the fields validation, otherwise there can be a lot of suprises for struct validators. For the reason, I implemented it so the struct's fields are validated before the struct itself. I hope it makes sense.

Hey @zenovich sorry for the delay. I really do like the change but my thoughts are that the struct validations still need to come first before the fields.
My reasoning is that a struct comes first in the hierarchical eg. you can't have fields to validate if the struct say is nil. just like not being able to validate the values of an array or map before checking if there are values.

I guess what you said is exactly what I mean, you have to do checks/validations on the struct first to ensure existence of data to check. If it’s nil then there are no fields to validate and is why I believe the order needs to run validations on the struct itself first.

Closing until the matter of order can be addressed.

@deankarn, sorry for the delay. I haven't enough time for investigation to answer your question till now. I've just rechecked that actually everything works exactly in the way you want: the validators are run on the structs first, than on the fields, so validators are not run for the fields when the struct is null.
Sorry for the confusion. Can you reopen the PR please?

func TestStructValidation_SkipsNotGivenNestedStructs(t *testing.T) {
	type inner struct {
		Test string `validate:"required"`
	}
	type TestStruct struct {
		Test *struct {
			Test string `validate:"required"`
		} `validate:"one,two,dive"`
		Test2 *inner `validate:"one,two,dive"`
	}

	ts := TestStruct{Test2: &inner{Test: "some value"}}
	val := New()

	fn1 := func(fl FieldLevel) bool {
		return fl.Field().FieldByName("Test").String() == "some value"
	}
	fn2 := func(fl FieldLevel) bool {
		return fl.Field().FieldByName("Test").String() == "another value"
	}

	val.RegisterValidation("one", fn1)
	val.RegisterValidation("two", fn2)
	errs := val.Struct(ts)
	fmt.Print(errs.(ValidationErrors))
	Equal(t, len(errs.(ValidationErrors)), 2)
	AssertError(t, errs, "TestStruct.Test", "TestStruct.Test", "Test", "Test", "one")
	AssertError(t, errs, "TestStruct.Test2", "TestStruct.Test2", "Test2", "Test2", "two")
}

Note that the validator are not called for TestStruct.Test.Test because TestStruct.Test is null.

So, in the code, it looks like the validators of inner fields of a nested struct are being run before validators of the nested struct, but this never happens if the nested struct is null.

IMO the order for nested structs should:

check if the nested struct is null, otherwise skip this struct,
validate all the fields of the nested struct,
if there are no errors inside the nested struct, run validators for the nested struct itself.

The idea is that validators for the whole struct can only make sense if each part of the struct makes sense.
But there is a bug in this PR: on the step 3 validators validators for the nested struct get run even if there were errors inside :(
I'll fix this soon.

The reason is nils are handled a little differently in the code that shortcuts the logic.
Also would it work if a StructLevel validation was registered/used?
By all means please submit another PR and I’ll take a look at that one :)

@deankarn all the existing tests related to StructLevel are successful. Should we check any special cases?

By all means please submit another PR and I’ll take a look at that one :)

Done


Week should start with Sundy , 1 stand for Sundy?

I have some confusion about the description of the week.
I find that there are many sources that say 1 in the Cron expression means Sunday, but in the converted readable text representation, the week starts from Monday.

By default 0 means Sunday so 2 means Tuesday.  You can control this with the dayOfWeekStartIndexZero  option.

Thank you for your reply. And sorry for my inattentiveness.
Thanks again!


clean-repo: Also delete .pyc files with same timestamp as the .py file

I encountered a bug the other day which turned out to be fixed by deleting a certain .pyc file that had the same timestamp as the corresponding .py file but didn't actually match (caused, I think, by some rebase race).
This is a follow-up issue introduced by #5768.   Tagging it as a priority since the issue took a bit for me to debug, so I imagine most folks would just get confused and demoralized...

This problem is happening to others and pretty confusing, in that it's led to a few folks rebasing branches ending up with broken development environments.
@gnprice do you have time to fix this correctly, or should we revert #5768?

How big is the impact of #5760 which #5768 fixed?
The #5760 description says it accounts for 1/8 of the time in tools/test-js-with-casper 01. In a bit of testing just now on my machine, that command took 30.8s and 30.1s in two trials; and when I manually remove all .pyc files with the old version of the line replaced in #5768, it takes 29.8s and 30.4s.
... Oho, that's because #5768 actually didn't touch the part of tools/clean-repo that reaches Python 3's cache files -- and I'm running my dev environment in Python 3, so I was unconditionally clearing caches.
OK, but then even in Python 2 on master, it takes 26.8s and 27.1s; and after reverting #5768, 27.6s and 28.3s. So this appears to be costing maybe about a second, where running the shortest test file costs about 27s. If it was having a much bigger impact before, maybe something else changed to affect that.
At that level of impact, I think the work to diagnose how CPython is getting confused here and to then reliably fix it isn't worth it in at least the short term, and we should revert. Can you reproduce a much bigger impact now?

For me, it's the same 1s, but out of 8s.  Given the fact that 1s apparently doesn't scale, seems fine.


FPE in BatchMatMul

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf 2.14.0
Custom code
Yes
OS platform and distribution
Ubuntu 18.04.6
Mobile device
No response
Python version
Python 3.8.3
Bazel version
bazel 5.3.0
GCC/compiler version
gcc 7.5.0
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
Construct a malicious BatchMatMul operator model with a shape of 4x0x0x0.
The input_shape.Dims(i)  variable may be equal to 0, leading to a division by zero error.
// transpose_utils.cc
size_t Flatten(const RuntimeShape& input_shape,
               const RuntimeShape& output_shape, const TransposeParams& params,
               RuntimeShape* non_flatten_input_shape,
               RuntimeShape* non_flatten_output_shape,
               TransposeParams* non_flatten_params) {
  // Calculate the total size of non-flatten dimensions.
  int skip_dims_cnt = 0;
  size_t flat_size = input_shape.FlatSize();
  for (int i = 0; i < params.perm_count; ++i) {
    if (params.perm[i] == i) {
      flat_size /= input_shape.Dims(i);  // FPE

BatchMatMul_FPE.zip
Standalone code to reproduce the issue
When I use the benchmark tool for PoC validation, it causes the TensorFlow Lite inference process to be subjected to a DOS（coredump).

❯ ./benchmark_model --graph=../poc/BatchMatMul_FPE.tflite
INFO: STARTING!
INFO: Log parameter values verbosely: [0]
INFO: Graph: [../poc/BatchMatMul_FPE.tflite]
INFO: Loaded model ../poc/BatchMatMul_FPE.tflite
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
INFO: The input model file size (MB): 0.0006
INFO: Initialized session in 155.728ms.
INFO: Running benchmark for at least 1 iterations and at least 0.5 seconds but terminate if exceeding 150 seconds.
[1]    26298 floating point exception (core dumped)  ./benchmark_model --graph=../poc/BatchMatMul_FPE.tflite

### Relevant log output

_No response_

Hi @SiriusHsh, I'm getting a different error, this is with branch r2.14 and gcc, my bazel is more up to date (6.1.0):
./benchmark_model --graph=BatchMatMul_FPE.tflite
2023-09-22 20:08:07.554231: I tensorflow/tools/benchmark/benchmark_model.cc:475] Graph: [BatchMatMul_FPE.tflite]
2023-09-22 20:08:07.554309: I tensorflow/tools/benchmark/benchmark_model.cc:476] Init ops:
2023-09-22 20:08:07.554321: I tensorflow/tools/benchmark/benchmark_model.cc:477] Input layers: [input:0]
2023-09-22 20:08:07.554329: I tensorflow/tools/benchmark/benchmark_model.cc:478] Input shapes: [1,224,224,3]
2023-09-22 20:08:07.554337: I tensorflow/tools/benchmark/benchmark_model.cc:479] Input types: [float]
2023-09-22 20:08:07.554344: I tensorflow/tools/benchmark/benchmark_model.cc:480] Output layers: [output:0]
2023-09-22 20:08:07.554352: I tensorflow/tools/benchmark/benchmark_model.cc:481] Target layers: []
2023-09-22 20:08:07.554376: I tensorflow/tools/benchmark/benchmark_model.cc:482] Num runs: [1000]
2023-09-22 20:08:07.554398: I tensorflow/tools/benchmark/benchmark_model.cc:483] Inter-inference delay (seconds): [-1.0]
2023-09-22 20:08:07.554417: I tensorflow/tools/benchmark/benchmark_model.cc:484] Inter-benchmark delay (seconds): [-1.0]
2023-09-22 20:08:07.554433: I tensorflow/tools/benchmark/benchmark_model.cc:486] Num threads: [-1]
2023-09-22 20:08:07.554448: I tensorflow/tools/benchmark/benchmark_model.cc:487] Benchmark name: []
2023-09-22 20:08:07.554457: I tensorflow/tools/benchmark/benchmark_model.cc:488] Output prefix: []
2023-09-22 20:08:07.554471: I tensorflow/tools/benchmark/benchmark_model.cc:489] Show sizes: [0]
2023-09-22 20:08:07.554488: I tensorflow/tools/benchmark/benchmark_model.cc:490] Warmup runs: [1]
2023-09-22 20:08:07.554502: I tensorflow/tools/benchmark/benchmark_model.cc:256] Loading TensorFlow.
2023-09-22 20:08:07.554521: I tensorflow/tools/benchmark/benchmark_model.cc:264] Got config, 0 devices
2023-09-22 20:08:07.554619: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE3 SSE4.1 SSE4.2 AVX AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
[libprotobuf ERROR external/com_google_protobuf/src/google/protobuf/text_format.cc:337] Error parsing text-format tensorflow.GraphDef: 1:1: Invalid control characters encountered in text.
[libprotobuf ERROR external/com_google_protobuf/src/google/protobuf/text_format.cc:337] Error parsing text-format tensorflow.GraphDef: 1:9: Invalid control characters encountered in text.
[libprotobuf ERROR external/com_google_protobuf/src/google/protobuf/text_format.cc:337] Error parsing text-format tensorflow.GraphDef: 1:45: Interpreting non ascii codepoint 132.
[libprotobuf ERROR external/com_google_protobuf/src/google/protobuf/text_format.cc:337] Error parsing text-format tensorflow.GraphDef: 1:45: Message type "tensorflow.GraphDef" has no field named "TFL3".
2023-09-22 20:08:07.564334: E tensorflow/tools/benchmark/benchmark_model.cc:275] Could not create TensorFlow Graph: DATA_LOSS: Can't parse BatchMatMul_FPE.tflite as text proto
2023-09-22 20:08:07.564384: I tensorflow/tools/benchmark/benchmark_model.cc:502] Initialized session in 0.009869s

Did you upload the right file? Can you try with an updated Bazel?

Hi @SiriusHsh, I'm getting a different error, this is with branch r2.14 and gcc, my bazel is more up to date (6.1.0):
./benchmark_model --graph=BatchMatMul_FPE.tflite
2023-09-22 20:08:07.554231: I tensorflow/tools/benchmark/benchmark_model.cc:475] Graph: [BatchMatMul_FPE.tflite]
2023-09-22 20:08:07.554309: I tensorflow/tools/benchmark/benchmark_model.cc:476] Init ops:
2023-09-22 20:08:07.554321: I tensorflow/tools/benchmark/benchmark_model.cc:477] Input layers: [input:0]
2023-09-22 20:08:07.554329: I tensorflow/tools/benchmark/benchmark_model.cc:478] Input shapes: [1,224,224,3]
2023-09-22 20:08:07.554337: I tensorflow/tools/benchmark/benchmark_model.cc:479] Input types: [float]
2023-09-22 20:08:07.554344: I tensorflow/tools/benchmark/benchmark_model.cc:480] Output layers: [output:0]
2023-09-22 20:08:07.554352: I tensorflow/tools/benchmark/benchmark_model.cc:481] Target layers: []
2023-09-22 20:08:07.554376: I tensorflow/tools/benchmark/benchmark_model.cc:482] Num runs: [1000]
2023-09-22 20:08:07.554398: I tensorflow/tools/benchmark/benchmark_model.cc:483] Inter-inference delay (seconds): [-1.0]
2023-09-22 20:08:07.554417: I tensorflow/tools/benchmark/benchmark_model.cc:484] Inter-benchmark delay (seconds): [-1.0]
2023-09-22 20:08:07.554433: I tensorflow/tools/benchmark/benchmark_model.cc:486] Num threads: [-1]
2023-09-22 20:08:07.554448: I tensorflow/tools/benchmark/benchmark_model.cc:487] Benchmark name: []
2023-09-22 20:08:07.554457: I tensorflow/tools/benchmark/benchmark_model.cc:488] Output prefix: []
2023-09-22 20:08:07.554471: I tensorflow/tools/benchmark/benchmark_model.cc:489] Show sizes: [0]
2023-09-22 20:08:07.554488: I tensorflow/tools/benchmark/benchmark_model.cc:490] Warmup runs: [1]
2023-09-22 20:08:07.554502: I tensorflow/tools/benchmark/benchmark_model.cc:256] Loading TensorFlow.
2023-09-22 20:08:07.554521: I tensorflow/tools/benchmark/benchmark_model.cc:264] Got config, 0 devices
2023-09-22 20:08:07.554619: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE3 SSE4.1 SSE4.2 AVX AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
[libprotobuf ERROR external/com_google_protobuf/src/google/protobuf/text_format.cc:337] Error parsing text-format tensorflow.GraphDef: 1:1: Invalid control characters encountered in text.
[libprotobuf ERROR external/com_google_protobuf/src/google/protobuf/text_format.cc:337] Error parsing text-format tensorflow.GraphDef: 1:9: Invalid control characters encountered in text.
[libprotobuf ERROR external/com_google_protobuf/src/google/protobuf/text_format.cc:337] Error parsing text-format tensorflow.GraphDef: 1:45: Interpreting non ascii codepoint 132.
[libprotobuf ERROR external/com_google_protobuf/src/google/protobuf/text_format.cc:337] Error parsing text-format tensorflow.GraphDef: 1:45: Message type "tensorflow.GraphDef" has no field named "TFL3".
2023-09-22 20:08:07.564334: E tensorflow/tools/benchmark/benchmark_model.cc:275] Could not create TensorFlow Graph: DATA_LOSS: Can't parse BatchMatMul_FPE.tflite as text proto
2023-09-22 20:08:07.564384: I tensorflow/tools/benchmark/benchmark_model.cc:502] Initialized session in 0.009869s

Did you upload the right file? Can you try with an updated Bazel?

I'm sorry for the delayed response. I don't think it's a Bazel version issue. It's possible that the way I'm building differs from yours.
I'm using the build method recommended in this official guide, as follows:

git clone https://github.com/tensorflow/tensorflow.git tensorflow_src
mkdir tflite_build
cd tflite_build
cmake ../tensorflow_src/tensorflow/lite
cmake --build . -j
cmake --build . -j -t benchmark_model

The benchmark is in the tools directory
I still encounter the same issue in the latest code, commit id: abbbcb50208cf6d5a965b7bf60efec5bb078e142.

Hi @SiriusHsh, I wasn't able to reproduce this one:
git clone https://github.com/tensorflow/tensorflow.git tensorflow_src
mkdir tflite_build
cd tflite_build
cmake ../tensorflow_src/tensorflow/lite
cmake --build . -j
cmake --build . -j -t benchmark_model
cd tools/benchmark
cp path/to/BatchMatMul_FPE.tflite .
./benchmark_model --graph=BatchMatMul_FPE.tflite

./benchmark_model --graph=BatchMatMul_FPE.tflite
INFO: STARTING!
INFO: Log parameter values verbosely: [0]
INFO: Graph: [BatchMatMul_FPE.tflite]
INFO: Loaded model BatchMatMul_FPE.tflite
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
INFO: The input model file size (MB): 0.0006
INFO: Initialized session in 1.486ms.
INFO: Running benchmark for at least 1 iterations and at least 0.5 seconds but terminate if exceeding 150 seconds.
INFO: count=1785957 first=3 curr=1 min=0 max=78 avg=0.193891 std=0

INFO: Running benchmark for at least 50 iterations and at least 1 seconds but terminate if exceeding 150 seconds.
INFO: count=3571192 first=1 curr=1 min=0 max=101 avg=0.193897 std=0

INFO: Inference timings in us: Init: 1486, First inference: 3, Warmup (avg): 0.193891, Inference (avg): 0.193897
INFO: Note: as the benchmark tool itself affects memory footprint, the following is only APPROXIMATE to the actual memory footprint of the model at runtime. Take the information at your discretion.
INFO: Memory footprint delta from the start of the tool (MB): init=3 overall=3

Can you verify if you uploaded the same model file or if somehow the latest code resolve this issue? Thanks.


Remove local usage of deprecated tempdir

see #761

We still use tempdir because of params, so I think it makes more sense to wait until we switch to hyper. Otherwise we'll compile both tempdir and tempfile.
$ cargo tree -i -p tempdir
tempdir v0.3.7
├── multipart v0.13.6
│   └── params v0.8.0
│       └── cratesfyi v0.6.0 (/home/joshua/src/docs.rs)
└── params v0.8.0 (*)

We already use tempfile too (not at my checkout to check the tree).

You're quite right, we use it through Rustwide.


Replace the implementation with the one based on iprover

This resolves #32.

I conducted some experiments with the iprover-based equivalence reasoner, which show that it has trouble with certain slightly nontrivial goals.
While it could solve the respective goals in Thorn_Calculus-Core_Bisimilarities without problems, it didn’t cope well with some goals in Network_Equivalences-Communication. The attempts to prove the lemmas duploss_idempotency and duploss_nested_idempotency with the proofs currently on GitHub (see below) didn’t finish or at least would have taken more time than I was willing to wait. https://github.com/input-output-hk/network-equivalences/blob/1809aebea493c36aac863c42821c304d777e210d/src/Network_Equivalences-Communication.thy#L259-L269 After reducing the lists of chained facts from thorn_simps to just the facts related to the goals in question, the times needed for proving these lemmas were as follows:

duploss_idempotency: 8 seconds
duploss_nested_idempotency: 108 seconds

Since process families being functions might have contributed to this high time consumption, I ran analog tests with process family replaced by a base type introduced via typedecl and functions and facts replaced by corresponding ones introduced via axiomatization. The times spent for proving the lemmas were as follows:

duploss_idempotency: 4 seconds
duploss_nested_idempotency: 57 seconds

So using a non-function type could approximately halve the proving times.
That said, I tried with an even more reduced list of facts, one that didn’t contain “over the parenthesis” rules like loss_nested_idempotency. This resulted in the following times:

duploss_idempotency: 2 seconds
duploss_nested_idempotency: > 180 seconds (didn’t wait further)

I conclude that, no matter how you massage the list of chained facts, running times can easily be unacceptably large and it’s hard to predict how changes to the fact list change the running time. Therefore, I reckon that we should not use the iprover-based implementation and stick to the latest Simplifier-based one.


Using replit database on a different account doesnt work

I am trying to make an email verification system (which works) on a different account, but I cant hide the email and password without being interrupted by this error.
TypeError: 'NoneType' object is not subscriptable

The code I am using, and tried.
Replit.DB
replit.db['email'] = ""
replit.db['password'] = ""

OS
email    = os.environ['EMAIL']
password = os.environ['PASSWORD']

Please add more information, since it's vague where the error is coming from. Do you have a repl or a code snippet to share?

this has happened to me when REPLIT_DB_URL isn't set - when you're using the repl without logging in, but I don't know why using a different account wouldn't work

Yes, replit_db does not work if you are not logged in. You could try using repl auth or identity.


Design a Logo for the project COLLEGE.AI

Hi Admin,
I'm interested in contributing to your project as part of GSSoC. I've been following your work and believe my skills align well. You can find my portfolio here: (https://sites.google.com/view/uibymehtab) and LinkedIn (https://www.linkedin.com/in/mehtabarkhan/)
Thanks,
Mehtab

Hi Mehtab (@MehtabAsHellic ),
Thank you for your interest in contributing to our project as part of GSSoC. We have reviewed your portfolio and would love to assign this issue to you. Our team will review your work once submitted.

@AbhiDiva96 should I design the logo color according to the current theme of the https://collegeai.streamlit.app/,
or you want it as new branding identity

@SurajSanap Let me know your thoughts and we can iterate with the design and make more better with it.

I would like to work on this issue. Kindly assign me the issue.

@SurajSanap Let me know your thoughts and we can iterate with the design and make more better with it.

any comment @SurajSanap

Hi!
I am an ardent user of Canva and a part of design team of my club. I would really like to contribute and give my perspective for the logo for this project.

kindly  assign me  this issue.


argument -override-dev-pkg=

This PR adds a command line argument to the platform script to override on the fly the URL from which the sources of a .dev package are downloaded. This (or something equivalent) is needed in Coq CI since otherwise the platform job does not use the sources of Coq being part of the PR (but master).
CC @MSoegtropIMC , see also https://github.com/coq/coq/pull/14217

P.S.: I just saw that coq-dev also fails (on first glance I thought that only extended packages fail). I must admit I am not sure what the state of the dev-ci branch is - I am working on enabling dev builds in the 2021.02 branch.

ok, then I'm merging this to unblock coq/coq#14217


[requires.io] dependency update on manifest-fix branch

Coverage remained the same at 100.0% when pulling 53b71e6eb1cdd0d17f90270bcf3e02c0adb71392 on requires-io-manifest-fix into a28216caefa583a2edda40566f1d8c30d57097de on manifest-fix.

Codecov Report

Merging #204 into manifest-fix will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           manifest-fix   #204   +/-   ##
===========================================
  Coverage           100%   100%
===========================================
  Files                18     18
  Lines               461    461
  Branches             43     43
===========================================
  Hits                461    461

Coverage remained the same at 100.0% when pulling a774a3fa6625494650d59a5578d768b2e56b10e5 on requires-io-manifest-fix into a28216caefa583a2edda40566f1d8c30d57097de on manifest-fix.