Log session start time Wed Mar 24 20:30:20 CST 2021
| Level | Date | Message | MethodOfCaller | FileOfCaller | LineOfCaller |
| INFO | 2021-03-24 20:30:20,802 | HV000001: Hibernate Validator 6.1.6.Final | <clinit> | Version.java | 21 |
| INFO | 2021-03-24 20:30:20,916 | Starting DesformApiTest on LAPTOP-ZKS with PID 27808 (started by Lenovo in E:\Jeecg\jeecg-boot\jeecg-boot-module-system) | logStarting | StartupInfoLogger.java | 55 |
| INFO | 2021-03-24 20:30:20,918 | The following profiles are active: dev | logStartupProfileInfo | SpringApplication.java | 655 |
| INFO | 2021-03-24 20:30:24,073 | Multiple Spring Data modules found, entering strict repository configuration mode! | multipleStoresDetected | RepositoryConfigurationDelegate.java | 249 |
| INFO | 2021-03-24 20:30:24,077 | Bootstrapping Spring Data Redis repositories in DEFAULT mode. | registerRepositoriesIn | RepositoryConfigurationDelegate.java | 127 |
| INFO | 2021-03-24 20:30:24,279 | Finished Spring Data repository scanning in 181ms. Found 0 Redis repository interfaces. | registerRepositoriesIn | RepositoryConfigurationDelegate.java | 187 |
| INFO | 2021-03-24 20:30:25,355 | Bean 'spring.redis-org.springframework.boot.autoconfigure.data.redis.RedisProperties' of type [org.springframework.boot.autoconfigure.data.redis.RedisProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:25,364 | Bean 'org.springframework.boot.autoconfigure.data.redis.LettuceConnectionConfiguration' of type [org.springframework.boot.autoconfigure.data.redis.LettuceConnectionConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:25,771 | Bean 'lettuceClientResources' of type [io.lettuce.core.resource.DefaultClientResources] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:26,033 | Bean 'redisConnectionFactory' of type [org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:26,036 | Bean 'shiroConfig' of type [org.jeecg.config.shiro.ShiroConfig$$EnhancerBySpringCGLIB$$cb2bd6d2] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:26,139 | Bean 'shiroRealm' of type [org.jeecg.config.shiro.ShiroRealm] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:27,271 | ===============(1)创建缓存管理器RedisCacheManager | redisCacheManager | ShiroConfig.java | 207 |
| INFO | 2021-03-24 20:30:27,277 | ===============(2)创建RedisManager,连接Redis.. | redisManager | ShiroConfig.java | 225 |
| INFO | 2021-03-24 20:30:27,286 | Bean 'redisManager' of type [org.crazycake.shiro.RedisManager] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:27,312 | Bean 'securityManager' of type [org.apache.shiro.web.mgt.DefaultWebSecurityManager] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:27,405 | Bean 'authorizationAttributeSourceAdvisor' of type [org.apache.shiro.spring.security.interceptor.AuthorizationAttributeSourceAdvisor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:27,940 | Bean 'spring.datasource.dynamic-com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceProperties' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:27,952 | Bean 'com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAutoConfiguration' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAutoConfiguration$$EnhancerBySpringCGLIB$$d57dffaa] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:27,966 | Bean 'dsProcessor' of type [com.baomidou.dynamic.datasource.processor.DsHeaderProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:28,039 | Bean 'redisConfig' of type [org.jeecg.config.redis.RedisConfig$$EnhancerBySpringCGLIB$$4214c5e6] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:28,188 | Bean 'org.apache.shiro.spring.boot.autoconfigure.ShiroBeanAutoConfiguration' of type [org.apache.shiro.spring.boot.autoconfigure.ShiroBeanAutoConfiguration$$EnhancerBySpringCGLIB$$7f086c89] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:28,201 | Bean 'eventBus' of type [org.apache.shiro.event.support.DefaultEventBus] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) | postProcessAfterInitialization | PostProcessorRegistrationDelegate.java | 335 |
| INFO | 2021-03-24 20:30:28,775 | Tomcat initialized with port(s): 0 (http) | initialize | TomcatWebServer.java | 108 |
| INFO | 2021-03-24 20:30:28,794 | Initializing ProtocolHandler ["http-nio-auto-1"] | log | DirectJDKLog.java | 173 |
| INFO | 2021-03-24 20:30:28,800 | Starting service [Tomcat] | log | DirectJDKLog.java | 173 |
| INFO | 2021-03-24 20:30:28,802 | Starting Servlet engine: [Apache Tomcat/9.0.39] | log | DirectJDKLog.java | 173 |
| INFO | 2021-03-24 20:30:28,808 | Loaded Apache Tomcat Native library [1.2.24] using APR version [1.7.0]. | log | DirectJDKLog.java | 173 |
| INFO | 2021-03-24 20:30:28,810 | APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. | log | DirectJDKLog.java | 173 |
| INFO | 2021-03-24 20:30:28,811 | APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true] | log | DirectJDKLog.java | 173 |
| INFO | 2021-03-24 20:30:28,816 | OpenSSL successfully initialized [OpenSSL 1.1.1g 21 Apr 2020] | log | DirectJDKLog.java | 173 |
| INFO | 2021-03-24 20:30:29,175 | Initializing Spring embedded WebApplicationContext | log | DirectJDKLog.java | 173 |
| INFO | 2021-03-24 20:30:29,175 | Root WebApplicationContext: initialization completed in 8142 ms | prepareWebApplicationContext | ServletWebServerApplicationContext.java | 285 |
| INFO | 2021-03-24 20:30:31,329 | {dataSource-1,master} inited | init | DruidDataSource.java | 994 |
| INFO | 2021-03-24 20:30:31,332 | dynamic-datasource - load a datasource named [master] success | addDataSource | DynamicRoutingDataSource.java | 132 |
| INFO | 2021-03-24 20:30:31,332 | dynamic-datasource initial loaded [1] datasource,primary datasource named [master] | afterPropertiesSet | DynamicRoutingDataSource.java | 237 |
| INFO | 2021-03-24 20:30:36,511 | --- redis config init --- | redisTemplate | RedisConfig.java | 66 |
| INFO | 2021-03-24 20:30:37,798 | Using default implementation for ThreadExecutor | instantiate | StdSchedulerFactory.java | 1220 |
| INFO | 2021-03-24 20:30:37,801 | Job execution threads will use class loader of thread: main | initialize | SimpleThreadPool.java | 268 |
| INFO | 2021-03-24 20:30:37,817 | Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl | <init> | SchedulerSignalerImpl.java | 61 |
| INFO | 2021-03-24 20:30:37,817 | Quartz Scheduler v.2.3.2 created. | <init> | QuartzScheduler.java | 229 |
| INFO | 2021-03-24 20:30:37,823 | Using db table-based data access locking (synchronization). | initialize | JobStoreSupport.java | 672 |
| INFO | 2021-03-24 20:30:37,825 | JobStoreCMT initialized. | initialize | JobStoreCMT.java | 145 |
| INFO | 2021-03-24 20:30:37,827 | Scheduler meta-data: Quartz Scheduler (v2.3.2) 'MyScheduler' with instanceId 'LAPTOP-ZKS1616589037800' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads. Using job-store 'org.springframework.scheduling.quartz.LocalDataSourceJobStore' - which supports persistence. and is clustered. | initialize | QuartzScheduler.java | 294 |
| INFO | 2021-03-24 20:30:37,828 | Quartz scheduler 'MyScheduler' initialized from an externally provided properties instance. | instantiate | StdSchedulerFactory.java | 1374 |
| INFO | 2021-03-24 20:30:37,829 | Quartz scheduler version: 2.3.2 | instantiate | StdSchedulerFactory.java | 1378 |
| INFO | 2021-03-24 20:30:37,831 | JobFactory set to: org.springframework.scheduling.quartz.SpringBeanJobFactory@459df48d | setJobFactory | QuartzScheduler.java | 2293 |
| INFO | 2021-03-24 20:30:43,227 | Exposing 2 endpoint(s) beneath base path '/actuator' | <init> | EndpointLinksResolver.java | 58 |
| INFO | 2021-03-24 20:30:43,778 | Mapped URL path [/v2/api-docs] onto method [springfox.documentation.swagger2.web.Swagger2Controller#getDocumentation(String, HttpServletRequest)] | initHandlerMethods | PropertySourcedRequestMappingHandlerMapping.java | 69 |
| INFO | 2021-03-24 20:30:44,582 | Initializing ExecutorService 'applicationTaskExecutor' | initialize | ExecutorConfigurationSupport.java | 181 |
| INFO | 2021-03-24 20:30:46,251 | Starting ProtocolHandler ["http-nio-auto-1"] | log | DirectJDKLog.java | 173 |
| INFO | 2021-03-24 20:30:46,295 | Tomcat started on port(s): 31166 (http) with context path '/jeecg-boot' | start | TomcatWebServer.java | 220 |
| INFO | 2021-03-24 20:30:46,297 | Context refreshed | start | DocumentationPluginsBootstrapper.java | 160 |
| INFO | 2021-03-24 20:30:46,331 | Found 1 custom documentation plugin(s) | start | DocumentationPluginsBootstrapper.java | 163 |
| INFO | 2021-03-24 20:30:46,470 | Scanning for api listing references | scan | ApiListingReferenceScanner.java | 41 |
| INFO | 2021-03-24 20:30:46,735 | Generating unique operation named: addUsingPOST_1 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,738 | Generating unique operation named: deleteUsingDELETE_1 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,743 | Generating unique operation named: deleteBatchUsingDELETE_1 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,746 | Generating unique operation named: editUsingPUT_1 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,748 | Generating unique operation named: queryByIdUsingGET_1 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,754 | Generating unique operation named: queryPageListUsingGET_1 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,766 | Generating unique operation named: addUsingPOST_2 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,770 | Generating unique operation named: deleteUsingDELETE_2 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,772 | Generating unique operation named: deleteBatchUsingDELETE_2 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,774 | Generating unique operation named: editUsingPUT_2 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,779 | Generating unique operation named: queryByIdUsingGET_2 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,794 | Generating unique operation named: queryPageListUsingGET_2 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,808 | Generating unique operation named: addUsingPOST_3 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,812 | Generating unique operation named: deleteUsingDELETE_3 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,815 | Generating unique operation named: deleteBatchUsingDELETE_3 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,821 | Generating unique operation named: editUsingPUT_3 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,823 | Generating unique operation named: queryByIdUsingGET_3 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,838 | Generating unique operation named: queryPageListUsingGET_3 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,849 | Generating unique operation named: addUsingPOST_4 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,857 | Generating unique operation named: deleteUsingDELETE_4 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,861 | Generating unique operation named: deleteBatchUsingDELETE_4 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,864 | Generating unique operation named: editUsingPUT_4 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,893 | Generating unique operation named: queryPageListUsingGET_4 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,905 | Generating unique operation named: addUsingPOST_5 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,909 | Generating unique operation named: deleteUsingDELETE_5 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,912 | Generating unique operation named: deleteBatchUsingDELETE_5 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,916 | Generating unique operation named: editUsingPUT_5 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,920 | Generating unique operation named: queryByIdUsingGET_4 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,928 | Generating unique operation named: queryPageListUsingGET_5 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,956 | Generating unique operation named: addUsingPOST_6 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,958 | Generating unique operation named: deleteUsingDELETE_6 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,969 | Generating unique operation named: deleteBatchUsingDELETE_6 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,973 | Generating unique operation named: editUsingPUT_6 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,983 | Generating unique operation named: queryByIdUsingGET_5 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:46,993 | Generating unique operation named: queryPageListUsingGET_6 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,008 | Generating unique operation named: addUsingPOST_7 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,013 | Generating unique operation named: deleteUsingDELETE_7 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,015 | Generating unique operation named: deleteBatchUsingDELETE_7 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,018 | Generating unique operation named: editUsingPUT_7 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,020 | Generating unique operation named: queryByIdUsingGET_6 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,029 | Generating unique operation named: queryPageListUsingGET_7 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,046 | Generating unique operation named: addUsingPOST_8 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,048 | Generating unique operation named: deleteUsingDELETE_8 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,053 | Generating unique operation named: deleteBatchUsingDELETE_8 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,057 | Generating unique operation named: editUsingPUT_8 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,095 | Generating unique operation named: queryByIdUsingGET_7 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,198 | Generating unique operation named: addUsingPOST_9 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,204 | Generating unique operation named: deleteUsingDELETE_9 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,221 | Generating unique operation named: deleteBatchUsingDELETE_9 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,224 | Generating unique operation named: editUsingPUT_9 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,231 | Generating unique operation named: queryByIdUsingGET_8 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,246 | Generating unique operation named: queryPageListUsingGET_8 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,266 | Generating unique operation named: addUsingPOST_10 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,331 | Generating unique operation named: deleteUsingDELETE_10 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,335 | Generating unique operation named: deleteBatchUsingDELETE_10 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,358 | Generating unique operation named: editUsingPUT_10 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,445 | Generating unique operation named: queryPageListUsingGET_9 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,525 | Generating unique operation named: addUsingPOST_11 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,541 | Generating unique operation named: deleteUsingDELETE_11 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,545 | Generating unique operation named: deleteBatchUsingDELETE_11 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,549 | Generating unique operation named: editUsingPUT_11 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,564 | Generating unique operation named: queryPageListUsingGET_10 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,581 | Generating unique operation named: addUsingPOST_12 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,582 | Generating unique operation named: deleteUsingDELETE_12 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,584 | Generating unique operation named: deleteBatchUsingDELETE_12 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,586 | Generating unique operation named: editUsingPUT_12 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,587 | Generating unique operation named: queryByIdUsingGET_9 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,593 | Generating unique operation named: queryPageListUsingGET_11 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,600 | Generating unique operation named: addUsingPOST_13 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,603 | Generating unique operation named: deleteUsingDELETE_13 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,605 | Generating unique operation named: deleteBatchUsingDELETE_13 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,607 | Generating unique operation named: editUsingPUT_13 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,608 | Generating unique operation named: queryByIdUsingGET_10 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,618 | Generating unique operation named: queryPageListUsingGET_12 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,624 | Generating unique operation named: addUsingPOST_14 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,628 | Generating unique operation named: deleteUsingDELETE_14 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,629 | Generating unique operation named: deleteBatchUsingDELETE_14 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,630 | Generating unique operation named: editUsingPUT_14 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,632 | Generating unique operation named: queryByIdUsingGET_11 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,638 | Generating unique operation named: queryPageListUsingGET_13 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,643 | Generating unique operation named: addUsingPOST_15 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,644 | Generating unique operation named: deleteUsingDELETE_15 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,646 | Generating unique operation named: deleteBatchUsingDELETE_15 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,648 | Generating unique operation named: editUsingPUT_15 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,652 | Generating unique operation named: queryByIdUsingGET_12 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,658 | Generating unique operation named: queryPageListUsingGET_14 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,662 | Generating unique operation named: addUsingPOST_16 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,663 | Generating unique operation named: deleteUsingDELETE_16 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,665 | Generating unique operation named: deleteBatchUsingDELETE_16 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,667 | Generating unique operation named: editUsingPUT_16 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,669 | Generating unique operation named: queryByIdUsingGET_13 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,672 | Generating unique operation named: queryPageListUsingGET_15 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,683 | Generating unique operation named: addUsingPOST_17 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,686 | Generating unique operation named: deleteUsingDELETE_17 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,692 | Generating unique operation named: deleteBatchUsingDELETE_17 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,693 | Generating unique operation named: editUsingPUT_17 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,694 | Generating unique operation named: queryByIdUsingGET_14 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,699 | Generating unique operation named: queryPageListUsingGET_16 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,707 | Generating unique operation named: addUsingPOST_18 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,709 | Generating unique operation named: deleteUsingDELETE_18 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,713 | Generating unique operation named: deleteBatchUsingDELETE_18 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,715 | Generating unique operation named: editUsingPUT_18 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,717 | Generating unique operation named: queryByIdUsingGET_15 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,723 | Generating unique operation named: queryPageListUsingGET_17 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,736 | Generating unique operation named: addUsingPOST_19 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,737 | Generating unique operation named: deleteUsingDELETE_19 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,742 | Generating unique operation named: deleteBatchUsingDELETE_19 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,743 | Generating unique operation named: editUsingPUT_19 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,745 | Generating unique operation named: queryByIdUsingGET_16 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,757 | Generating unique operation named: queryPageListUsingGET_18 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,762 | Generating unique operation named: addUsingPOST_20 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,764 | Generating unique operation named: deleteUsingDELETE_20 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,766 | Generating unique operation named: deleteBatchUsingDELETE_20 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,768 | Generating unique operation named: editUsingPUT_20 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,770 | Generating unique operation named: queryByIdUsingGET_17 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,774 | Generating unique operation named: queryPageListUsingGET_19 | startingWith | CachingOperationNameGenerator.java | 40 |
| INFO | 2021-03-24 20:30:47,792 | Starting Quartz Scheduler now | startScheduler | SchedulerFactoryBean.java | 727 |
| INFO | 2021-03-24 20:30:48,082 | ClusterManager: detected 1 failed or restarted instances. | logWarnIfNonZero | JobStoreSupport.java | 3644 |
| INFO | 2021-03-24 20:30:48,082 | ClusterManager: Scanning for instance "LAPTOP-ZKS1616588228403"'s failed in-progress jobs. | clusterRecover | JobStoreSupport.java | 3503 |
| INFO | 2021-03-24 20:30:48,138 | Scheduler MyScheduler_$_LAPTOP-ZKS1616589037800 started. | start | QuartzScheduler.java | 547 |
| INFO | 2021-03-24 20:30:48,156 | Started DesformApiTest in 28.111 seconds (JVM running for 30.956) | logStarted | StartupInfoLogger.java | 61 |
| INFO | 2021-03-24 20:30:48,164 | 服务已启动，准备初始化路由配置 ################### | onApplicationEvent | SystemInitListener.java | 27 |
| INFO | 2021-03-24 20:30:51,040 | RestUtil --- request --- url = http://localhost:8080/jeecg-boot/desform/api/qingjiadan | request | RestUtil.java | 189 |
| INFO | 2021-03-24 20:30:53,162 | Scheduler MyScheduler_$_LAPTOP-ZKS1616589037800 paused. | standby | QuartzScheduler.java | 585 |
| INFO | 2021-03-24 20:30:53,660 | Shutting down ExecutorService 'applicationTaskExecutor' | shutdown | ExecutorConfigurationSupport.java | 218 |
| INFO | 2021-03-24 20:30:53,663 | Shutting down Quartz Scheduler | destroy | SchedulerFactoryBean.java | 845 |
| INFO | 2021-03-24 20:30:53,663 | Scheduler MyScheduler_$_LAPTOP-ZKS1616589037800 shutting down. | shutdown | QuartzScheduler.java | 666 |
| INFO | 2021-03-24 20:30:53,663 | Scheduler MyScheduler_$_LAPTOP-ZKS1616589037800 paused. | standby | QuartzScheduler.java | 585 |
| INFO | 2021-03-24 20:30:53,665 | Scheduler MyScheduler_$_LAPTOP-ZKS1616589037800 shutdown complete. | shutdown | QuartzScheduler.java | 740 |
| INFO | 2021-03-24 20:30:53,672 | dynamic-datasource start closing .... | destroy | DynamicRoutingDataSource.java | 217 |
| INFO | 2021-03-24 20:30:53,675 | {dataSource-1} closing ... | close | DruidDataSource.java | 2029 |
| INFO | 2021-03-24 20:30:53,686 | {dataSource-1} closed | close | DruidDataSource.java | 2101 |
| INFO | 2021-03-24 20:30:53,686 | dynamic-datasource all closed success,bye | destroy | DynamicRoutingDataSource.java | 221 |


By accessing the website at https://www.talhaawan.net/, you are agreeing to be bound by these terms of service, all applicable laws and regulations, and agree that you are responsible for compliance with any applicable local laws. If you do not agree with any of these terms, you are prohibited from using or accessing this site. The materials contained in this website are protected by applicable copyright and trademark law.
In no event shall Talha Awan or its suppliers be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption) arising out of the use or inability to use the materials on Talha Awan' website, even if Talha Awan or a Talha Awan authorized representative has been notified orally or in writing of the possibility of such damage. Because some jurisdictions do not allow limitations on implied warranties, or limitations of liability for consequential or incidental damages, these limitations may not apply to you.
The materials appearing on Talha Awan website could include technical, typographical, or photographic errors. Talha Awan does not warrant that any of the materials on its website are accurate, complete or current. Talha Awan may make changes to the materials contained on its website at any time without notice. However Talha Awan does not make any commitment to update the materials.
Talha Awan has not reviewed all of the sites linked to its website and is not responsible for the contents of any such linked site. The inclusion of any link does not imply endorsement by Talha Awan of the site. Use of any such linked website is at the user's own risk.
Talha Awan may revise these terms of service for its website at any time without notice. By using this website you are agreeing to be bound by the then current version of these terms of service.
These terms and conditions are governed by and construed in accordance with the laws of Pakistan and you irrevocably submit to the exclusive jurisdiction of the courts in that State or location.


I was born with the wrong sign
In the wrong house
With the wrong ascendancy
I took the wrong road
That led to
The wrong tendencies
I was in the wrong place
At the wrong time
For the wrong reason
And the wrong rhyme
On the wrong day
Of the wrong week
Used the wrong method
With the wrong technique
Wrong
Wrong
(Depeche Mode - "Wrong")


{% extends "site_base.html" %} {% load i18n %} {% block title %}Error 404{% endblock title %} {% block nav %} {% include "navigation.html" %} {% endblock %} {% block content_base %} {% trans "Page not found" %} {% trans "We're sorry but that page could not be found." %} {% endblock %}
{% trans "We're sorry but that page could not be found." %}


Frequently Asked Questions
What is MeetingShot?
MeetingShot is a faux meeting screenshot generator designed to help those suffering from FOMMO - Fear of Missing Meetings Online.
Is this a real meeting? Does this use Zoom/Teams/Google Meet, etc?
No, it's just a fun app to create an image of a fictitious meeting.
Why doesn't this work on mobile?
This is the first prototype of the project, so we didn't focus on the mobile experience yet. As we get more free time, we'll get to that as well.
Can I actually schedule a meeting with the folks listed in the image selector?
No. At least not through MeetingShot, it's just a fake screenshot generator.
Can I style this to look like my favorite video calling app?
The current version only supports Zoom. We'd love contributiosn to the project as it is open source on GitHub .
Are my custom or webcam images uploaded anywhere?
No. Everything that you see is rendered directly in your browser. We do not store, analyze or send your images anywhere. We are using html2canvas to generate the final image and that's also done directly in your browser and not on some remote server.


Starring: a, b, c
{ “Title”: “Clue”, “Year”: “1985”, “Rated”: “PG”, “Released”: “13 Dec 1985”, “Runtime”: “94 min”, “Genre”: “Comedy, Crime, Mystery”, “Director”: “Jonathan Lynn”, “Writer”: “John Landis (story), Jonathan Lynn (story), Jonathan Lynn (screenplay)”, “Actors”: “Eileen Brennan, Tim Curry, Madeline Kahn, Christopher Lloyd”, “Plot”: “Six guests are invited to a strange house and must cooperate with the staff to solve a murder mystery.”, “Language”: “French, English”, “Country”: “USA”, “Awards”: “N/A”, “Poster”: “http://ia.media-imdb.com/images/M/MV5BNTc3NDc1ODYxNl5BMl5BanBnXkFtZTcwMjc5MDMyMQ@@._V1_SX300.jpg", “Metascore”: “36”, “imdbRating”: “7.3”, “imdbVotes”: “56,225”, “imdbID”: “tt0088930”, “Type”: “movie”, “tomatoMeter”: “62”, “tomatoImage”: “fresh”, “tomatoRating”: “5.8”, “tomatoReviews”: “26”, “tomatoFresh”: “16”, “tomatoRotten”: “10”, “tomatoConsensus”: “N/A”, “tomatoUserMeter”: “87”, “tomatoUserRating”: “3.6”, “tomatoUserReviews”: “93492”, “tomatoURL”: “http://www.rottentomatoes.com/m/clue/", “DVD”: “27 Jun 2000”, “BoxOffice”: “N/A”, “Production”: “Paramount Pictures”, “Website”: “N/A”, “Response”: “True” }


We never really had to bother with designing a water-based transportation system for the simple reason that there really wasn't any place to go. The fundamental tenet of transportation is that it is a process of moving people and cargo from A to B. However, the vCity wasn't set up to simulate an archipelago. In short, anyone who wants to can move from A to A, which isn't very exciting. The "B", so to speak, is a motley collection of off-shore industrial destinations (sites) including an oil-drilling platform techsimm, two undersea research and/or mining facilities simmcorps, and a handful of aquaculture farm sites.
Nevertheless, we tried to set up some kind of seaport infrastructure that would enable individuals and corporations to engage in residential, commercial/leisure, and industrial activity on the Bay and the Ocean, even if all they did was float around. Surprisingly, there was a brisk demand for VR design of new fishing vessels, oceanographic research vessels, cruise ships, casino ships, restaurant ships, whale watchers, pleasure motor- and sailboats of all kinds, and houseboats. Apparently boat and ship designers had already been using VR technology in their Computer Assisted Design and Manufacture (CAD/CAM), so it was relatively easy for professionals to fool around with VR sites on the side.
Someone even did a marketing study of the potential for servicing an off-shore residential population. After all, reasoned the analysts, if people are going to drift like motorized jellyfish in their brand-new houseboats, they will need supplies and services. It gave a whole new meaning to the phrase "cash float." Anyway, what they discovered is that construction and operation of houseboats is still very expensive, and there are drawbacks to sacrificing a fixed position even in an age of wireless comm technology.


--- layout: page title: About header-img: "img/about-bg.png" ---
Sam received his Bachelors in Science from the University of New Hampshire with a double focus in Finance and International Business & Economics. In his spare time, he enjoys gastronomy experiences with his SO. He is also an avid reader, gamer and tech enthusiast. Hoping one day to create his own app to share with the world.


--- layout: post title: Cavalry charge date: '2016-07-22T18:30:49+02:00' categories: - Horses - Sketchbooks - Sketches picture_url: https://film-Storyboards.tumblr.com/post/147818988101 ---
Reno charge with his men at Little Bighorn Battle


Adventure Harley-Davidson is a dream come true website for Harley lovers. Visit online and check out what you can buy at a great, affordable price. There are brand new and pre owned Harley Davidson motorbikes that you can buy for a bargain. You can also buy all genuine parts and accessories for Harley Davidson, riding apparel, jackets, footwear, shirts, wallets, bags. Adventure Harley-Davidson also carries jewelries, collectibles, motorbike accessories and lots of other useful items. Check it out online today. You will love the website; it is cool and user friendly. Use our discount coupon to get the best prices on Adventure Harley-Davidson.
Adventure Harley-Davidson caters to the needs of all Harley Davidson enthusiasts and owners. If you need exhausts, windshields, grips for your motorbike, saddlebags etc Adventure Harley-Davidson is a great place to look. Enjoy riding your Harley Davidson in the most comfortable, cool and smart clothes at great affordable prices. There are lots of accessories to choose from at Adventure Harley-Davidson. Seek and find something your heart desires that also suits the budget. Get men and women’s leather jackets that are beautiful and comfortable. You can also buy power lock kit, chrome auxiliary lighting kit and lots of other useful and necessary products. Check out Adventure Harley-Davidson online today and be amazed!
Adventure Harley-Davidson is the place to find all your genuine Harley parts and other collectible items at an affordable price. For everything a Harley Davidson enthusiast would need, Adventure Harley-Davidson is the best adventure one could embark on. Use our discount coupons to get a great price.


HPX V1.0.0 (Apr 24, 2017)¶
General changes¶
Here are some of the main highlights and changes for this release (in no particular order):
Added the facility
hpx::split_future
which allows to convert afuture<tuple<Ts...>>
into atuple<future<Ts>...>
. This functionality is not available when compiling HPX with VS2012.Added a new type of performance counter which allows to return a list of values for each invocation. We also added a first counter of this type which collects a histogram of the times between parcels being created.
Added new LCOs:
hpx::lcos::channel
andhpx::lcos::local::channel
which are very similar to the well known channel constructs used in the Go language.Added new performance counters reporting the amount of data handled by the networking layer on a action-by-action basis (please see PR #2289 for more details).
Added a new facility
hpx::lcos::barrier
, replacing the equally named older one. The new facility has a slightly changed API and is much more efficient. Most notable, the new facility exposes a (global) functionhpx::lcos::barrier::synchronize()
which represents a global barrier across all localities.We have started to add support for vectorization to our parallel algorithm implementations. This support depends on using an external library, currently either Vc Library or Boost.SIMD. Please see Issue #2333 for a list of currently supported algorithms. This is an experimental feature and its implementation and/or API might change in the future. Please see this blog-post for more information.
The parameter sequence for the
hpx::parallel::transform_reduce
overload taking one iterator range has changed to match the changes this algorithm has undergone while being moved to C++17. The old overload can be still enabled at configure time by specifying-DHPX_WITH_TRANSFORM_REDUCE_COMPATIBILITY=On
to CMake.The algorithm
hpx::parallel::inner_product
has been renamed tohpx::parallel::transform_reduce
to match the changes this algorithm has undergone while being moved to C++17. The old inner_product names can be still enabled at configure time by specifying-DHPX_WITH_TRANSFORM_REDUCE_COMPATIBILITY=On
to CMake.Added versions of
hpx::get_ptr
taking client side representations for component instances as their parameter (instead of a global id).Added the helper utility
hpx::performance_counters::performance_counter_set
helping to encapsulate a set of performance counters to be managed concurrently.All execution policies and related classes have been renamed to be consistent with the naming changes applied for C++17. All policies now live in the namespace
hpx::parallel::execution
. The ols names can be still enabled at configure time by specifying-DHPX_WITH_EXECUTION_POLICY_COMPATIBILITY=On
to CMake.The thread scheduling subsystem has undergone a major refactoring which results in significant performance improvements. We have also imroved the performance of creating
hpx::future
and of various facilities handling those.We have consolidated all of the code in HPX.Compute related to the integration of CUDA.
hpx::partitioned_vector
has been enabled to be usable withhpx::compute::vector
which allows to place the partitions on one or more GPU devices.Added new performance counters exposing various internals of the thread scheduling subsystem, such as the current idle- and busy-loop counters and instantaneous scheduler utilization.
Extended and improved the use of the ITTNotify hooks allowing to collect performance counter data and function annotation information from within the Intel Amplifier tool.
Breaking changes¶
We have dropped support for the gcc compiler versions V4.6 and 4.7. The minimal gcc version we now test on is gcc V4.8.
We have removed (default) support for
boost::chrono
in interfaces, uses of it have been replaced withstd::chrono
. This facility can be still enabled at configure time by specifying-DHPX_WITH_BOOST_CHRONO_COMPATIBILITY=On
to CMake.The parameter sequence for the
hpx::parallel::transform_reduce
overload taking one iterator range has changed to match the changes this algorithm has undergone while being moved to C++17.The algorithm
hpx::parallel::inner_product
has been renamed tohpx::parallel::transform_reduce
to match the changes this algorithm has undergone while being moved to C++17.the build options
HPX_WITH_COLOCATED_BACKWARDS_COMPATIBILITY
andHPX_WITH_COMPONENT_GET_GID_COMPATIBILITY
are now disabled by default. Please change your code still depending on the deprecated interfaces.
Bug fixes (closed tickets)¶
Here is a list of the important tickets we closed for this release.
PR #2596 - Adding apex data
PR #2595 - Remove obsolete file
Issue #2594 - FindOpenCL.cmake mismatch with the official cmake module
PR #2592 - First attempt to introduce spmd_block in hpx
Issue #2591 - Feature request: continuation (then) which does not require the callable object to take a future<R> as parameter
PR #2588 - Daint fixes
PR #2587 - Fixing transfer_(continuation)_action::schedule
PR #2585 - Work around MSVC having an ICE when compiling with -Ob2
PR #2583 - chaning 7zip command to 7za in roll_release.sh
PR #2582 - First attempt to introduce spmd_block in hpx
PR #2581 - Enable annotated function for parallel algorithms
PR #2580 - First attempt to introduce spmd_block in hpx
PR #2579 - Make thread NICE level setting an option
PR #2578 - Implementing enqueue instead of busy wait when no sender is available
PR #2577 - Retrieve -std=c++11 consistent nvcc flag
PR #2576 - Add missing dependencies of cuda based tests
PR #2575 - Remove warnings due to some captured variables
PR #2573 - Attempt to resolve resolve_locality
PR #2572 - Adding APEX hooks to background thread
PR #2571 - Pick up hpx.ignore_batch_env from config map
PR #2570 - Add commandline options –hpx:print-counters-locally
PR #2569 - Fix computeapi unit tests
PR #2567 - This adds another barrier::synchronize before registering performance counters
PR #2564 - Cray static toolchain support
PR #2563 - Fixed unhandled exception during startup
PR #2562 - Remove partitioned_vector.cu from build tree when nvcc is used
Issue #2561 - octo-tiger crash with commit 6e921495ff6c26f125d62629cbaad0525f14f7ab
PR #2560 - Prevent -Wundef warnings on Vc version checks
PR #2559 - Allowing CUDA callback to set the future directly from an OS thread
PR #2558 - Remove warnings due to float precisions
PR #2557 - Removing bogus handling of compile flags for CUDA
PR #2556 - Fixing scan partitioner
PR #2554 - Add more diagnostics to error thrown from find_appropriate_destination
Issue #2555 - No valid parcelport configured
PR #2553 - Add cmake cuda_arch option
PR #2552 - Remove incomplete datapar bindings to libflatarray
PR #2551 - Rename hwloc_topology to hwloc_topology_info
PR #2550 - Apex api updates
PR #2549 - Pre-include defines.hpp to get the macro HPX_HAVE_CUDA value
PR #2548 - Fixing issue with disconnect
PR #2546 - Some fixes around cuda clang partitioned_vector example
PR #2545 - Fix uses of the Vc2 datapar flags; the value, not the type, should be passed to functions
PR #2542 - Make HPX_WITH_MALLOC easier to use
PR #2541 - avoid recompiles when enabling/disabling examples
PR #2540 - Fixing usage of target_link_libraries()
PR #2539 - fix RPATH behaviour
Issue #2538 - HPX_WITH_CUDA corrupts compilation flags
PR #2537 - Add output of a Bazel Skylark extension for paths and compile options
PR #2536 - Add counter exposing total available memory to Windows as well
PR #2535 - Remove obsolete support for security
Issue #2534 - Remove command line option
--hpx:run-agas-server
PR #2533 - Pre-cache locality endpoints during bootstrap
PR #2532 - Fixing handling of GIDs during serialization preprocessing
PR #2531 - Amend uses of the term “functor”
PR #2529 - added counter for reading available memory
PR #2527 - Facilities to create actions from lambdas
PR #2526 - Updated docs: HPX_WITH_EXAMPLES
PR #2525 - Remove warnings related to unused captured variables
Issue #2524 - CMAKE failed because it is missing: TCMALLOC_LIBRARY TCMALLOC_INCLUDE_DIR
PR #2523 - Fixing compose_cb stack overflow
PR #2522 - Instead of unlocking, ignore the lock while creating the message handler
PR #2521 - Create
LPROGRESS_
logging macro to simplify progress tracking and timingsPR #2520 - Intel 17 support
PR #2519 - Fix components example
PR #2518 - Fixing parcel scheduling
Issue #2517 - Race condition during Parcel Coalescing Handler creation
Issue #2516 - HPX locks up when using at least 256 localities
Issue #2515 - error: Install cannot find “/lib/hpx/libparcel_coalescing.so.0.9.99” but I can see that file
PR #2514 - Making sure that all continuations of a shared_future are invoked in order
PR #2513 - Fixing locks held during suspension
PR #2512 - MPI Parcelport improvements and fixes related to the background work changes
PR #2511 - Fixing bit-wise (zero-copy) serialization
Issue #2509 - Linking errors in hwloc_topology
PR #2508 - Added documentation for debugging with core files
PR #2506 - Fixing background work invocations
PR #2505 - Fix tuple serialization
Issue #2504 - Ensure continuations are called in the order they have been attached
PR #2503 - Adding serialization support for Vc v2 (datapar)
PR #2502 - Resolve various, minor compiler warnings
PR #2501 - Some other fixes around cuda examples
Issue #2500 - nvcc / cuda clang issue due to a missing -DHPX_WITH_CUDA flag
PR #2499 - Adding support for std::array to wait_all and friends
PR #2498 - Execute background work as HPX thread
PR #2497 - Fixing configuration options for spinlock-deadlock detection
PR #2496 - Accounting for different compilers in CrayKNL toolchain file
PR #2494 - Adding component base class which ties a component instance to a given executor
PR #2493 - Enable controlling amount of pending threads which must be available to allow thread stealing
PR #2492 - Adding new command line option –hpx:print-counter-reset
PR #2491 - Resolve ambiguities when compiling with APEX
PR #2490 - Resuming threads waiting on future with higher priority
Issue #2489 - nvcc issue because -std=c++11 appears twice
PR #2488 - Adding performance counters exposing the internal idle and busy-loop counters
PR #2487 - Allowing for plain suspend to reschedule thread right away
PR #2486 - Only flag HPX code for CUDA if HPX_WITH_CUDA is set
PR #2485 - Making thread-queue parameters runtime-configurable
PR #2484 - Added atomic counter for parcel-destinations
PR #2483 - Added priority-queue lifo scheduler
PR #2482 - Changing scheduler to steal only if more than a minimal number of tasks are available
PR #2481 - Extending command line option –hpx:print-counter-destination to support value ‘none’
PR #2479 - Added option to disable signal handler
PR #2478 - Making sure the sine performance counter module gets loaded only for the corresponding example
Issue #2477 - Breaking at a throw statement
PR #2476 - Annotated function
PR #2475 - Ensure that using %osthread% during logging will not throw for non-hpx threads
PR #2474 - Remove now superficial non_direct actions from base_lco and friends
PR #2473 - Refining support for ITTNotify
PR #2472 - Some fixes around hpx compute
Issue #2470 - redefinition of boost::detail::spinlock
Issue #2469 - Dataflow performance issue
PR #2468 - Perf docs update
PR #2466 - Guarantee to execute remote direct actions on HPX-thread
PR #2465 - Improve demo : Async copy and fixed device handling
PR #2464 - Adding performance counter exposing instantaneous scheduler utilization
PR #2463 - Downcast to future<void>
PR #2462 - Fixed usage of ITT-Notify API with Intel Amplifier
PR #2461 - Cublas demo
PR #2460 - Fixing thread bindings
PR #2459 - Make -std=c++11 nvcc flag consistent for in-build and installed versions
Issue #2457 - Segmentation fault when registering a partitioned vector
PR #2452 - Properly releasing global barrier for unhandled exceptions
PR #2451 - Fixing long shutdown times
PR #2450 - Attempting to fix initialization errors on newer platforms (Boost V1.63)
PR #2449 - Replace BOOST_COMPILER_FENCE with an HPX version
PR #2448 - This fixes a possible race in the migration code
- PR #2445 - Fixing dataflow et.al. for futures or future-ranges wrapped
into ref()
PR #2444 - Fix segfaults
PR #2443 - Issue 2442
Issue #2442 - Mismatch between #if/#endif and namespace scope brackets in this_thread_executers.hpp
Issue #2441 - undeclared identifier BOOST_COMPILER_FENCE
PR #2440 - Knl build
PR #2438 - Datapar backend
PR #2437 - Adapt algorithm parameter sequence changes from C++17
PR #2436 - Adapt execution policy name changes from C++17
Issue #2435 - Trunk broken, undefined reference to hpx::thread::interrupt(hpx::thread::id, bool)
PR #2434 - More fixes to resource manager
PR #2433 - Added versions of
hpx::get_ptr
taking client side representationsPR #2432 - Warning fixes
PR #2431 - Adding facility representing set of performance counters
PR #2430 - Fix parallel_executor thread spawning
PR #2429 - Fix attribute warning for gcc
Issue #2427 - Seg fault running octo-tiger with latest HPX commit
Issue #2426 - Bug in 9592f5c0bc29806fce0dbe73f35b6ca7e027edcb causes immediate crash in Octo-tiger
PR #2425 - Fix nvcc errors due to constexpr specifier
Issue #2424 - Async action on component present on hpx::find_here is executing synchronously
PR #2423 - Fix nvcc errors due to constexpr specifier
PR #2422 - Implementing hpx::this_thread thread data functions
PR #2421 - Adding benchmark for wait_all
Issue #2420 - Returning object of a component client from another component action fails
PR #2419 - Infiniband parcelport
Issue #2418 - gcc + nvcc fails to compile code that uses partitioned_vector
PR #2417 - Fixing context switching
PR #2416 - Adding fixes and workarounds to allow compilation with nvcc/msvc (VS2015up3)
PR #2415 - Fix errors coming from hpx compute examples
PR #2414 - Fixing msvc12
PR #2413 - Enable cuda/nvcc or cuda/clang when using add_hpx_executable()
PR #2412 - Fix issue in HPX_SetupTarget.cmake when cuda is used
PR #2411 - This fixes the core compilation issues with MSVC12
Issue #2410 -
undefined reference to opal_hwloc191_hwloc_.....
PR #2409 - Fixing locking for channel and receive_buffer
PR #2407 - Solving #2402 and #2403
PR #2406 - Improve guards
PR #2405 - Enable parallel::for_each for iterators returning proxy types
PR #2404 - Forward the explicitly given result_type in the hpx invoke
Issue #2403 - datapar_execution + zip iterator: lambda arguments aren’t references
Issue #2402 - datapar algorithm instantiated with wrong type #2402
PR #2401 - Added support for imported libraries to HPX_Libraries.cmake
PR #2400 - Use CMake policy CMP0060
Issue #2399 - Error trying to push back vector of futures to vector
PR #2398 - Allow config #defines to be written out to custom config/defines.hpp
Issue #2397 - CMake generated config defines can cause tedious rebuilds category
Issue #2396 - BOOST_ROOT paths are not used at link time
PR #2395 - Fix target_link_libraries() issue when HPX Cuda is enabled
Issue #2394 - Template compilation error using HPX_WITH_DATAPAR_LIBFLATARRAY
PR #2393 - Fixing lock registration for recursive mutex
PR #2392 - Add keywords in target_link_libraries in hpx_setup_target
PR #2391 - Clang goroutines
Issue #2390 - Adapt execution policy name changes from C++17
PR #2389 - Chunk allocator and pool are not used and are obsolete
PR #2388 - Adding functionalities to datapar needed by octotiger
PR #2387 - Fixing race condition for early parcels
Issue #2386 - Lock registration broken for recursive_mutex
PR #2385 - Datapar zip iterator
PR #2384 - Fixing race condition in for_loop_reduction
PR #2383 - Continuations
PR #2382 - add LibFlatArray-based backend for datapar
PR #2381 - remove unused typedef to get rid of compiler warnings
PR #2380 - Tau cleanup
PR #2379 - Can send immediate
PR #2378 - Renaming copy_helper/copy_n_helper/move_helper/move_n_helper
Issue #2376 - Boost trunk’s spinlock initializer fails to compile
PR #2375 - Add support for minimal thread local data
PR #2374 - Adding API functions set_config_entry_callback
PR #2373 - Add a simple utility for debugging that gives supended task backtraces
PR #2372 - Barrier Fixes
Issue #2370 - Can’t wait on a wrapped future
PR #2369 - Fixing stable_partition
PR #2367 - Fixing find_prefixes for Windows platforms
PR #2366 - Testing for experimental/optional only in C++14 mode
PR #2364 - Adding set_config_entry
PR #2363 - Fix papi
PR #2362 - Adding missing macros for new non-direct actions
PR #2361 - Improve cmake output to help debug compiler incompatibility check
PR #2360 - Fixing race condition in condition_variable
PR #2359 - Fixing shutdown when parcels are still in flight
Issue #2357 - failed to insert console_print_action into typename_to_id_t registry
PR #2356 - Fixing return type of get_iterator_tuple
PR #2355 - Fixing compilation against Boost 1 62
PR #2354 - Adding serialization for mask_type if CPU_COUNT > 64
PR #2353 - Adding hooks to tie in APEX into the parcel layer
Issue #2352 - Compile errors when using intel 17 beta (for KNL) on edison
PR #2351 - Fix function vtable get_function_address implementation
Issue #2350 - Build failure - master branch (4de09f5) with Intel Compiler v17
PR #2349 - Enabling zero-copy serialization support for std::vector<>
PR #2348 - Adding test to verify #2334 is fixed
PR #2347 - Bug fixes for hpx.compute and hpx::lcos::channel
PR #2346 - Removing cmake “find” files that are in the APEX cmake Modules
PR #2345 - Implemented parallel::stable_partition
PR #2344 - Making hpx::lcos::channel usable with basename registration
PR #2343 - Fix a couple of examples that failed to compile after recent api changes
Issue #2342 - Enabling APEX causes link errors
PR #2341 - Removing cmake “find” files that are in the APEX cmake Modules
PR #2340 - Implemented all existing datapar algorithms using Boost.SIMD
PR #2339 - Fixing 2338
PR #2338 - Possible race in sliding semaphore
PR #2337 - Adjust osu_latency test to measure window_size parcels in flight at once
PR #2336 - Allowing remote direct actions to be executed without spawning a task
PR #2335 - Making sure multiple components are properly initialized from arguments
Issue #2334 - Cannot construct component with large vector on a remote locality
PR #2332 - Fixing hpx::lcos::local::barrier
PR #2331 - Updating APEX support to include OTF2
PR #2330 - Support for data-parallelism for parallel algorithms
Issue #2329 - Coordinate settings in cmake
PR #2328 - fix LibGeoDecomp builds with HPX + GCC 5.3.0 + CUDA 8RC
PR #2326 - Making scan_partitioner work (for now)
Issue #2323 - Constructing a vector of components only correctly initializes the first component
PR #2322 - Fix problems that bubbled up after merging #2278
PR #2321 - Scalable barrier
PR #2320 - Std flag fixes
Issue #2319 - -std=c++14 and -std=c++1y with Intel can’t build recent Boost builds due to insufficient C++14 support; don’t enable these flags by default for Intel
PR #2318 - Improve handling of –hpx:bind=<bind-spec>
PR #2317 - Making sure command line warnings are printed once only
PR #2316 - Fixing command line handling for default bind mode
PR #2315 - Set id_retrieved if set_id is present
Issue #2314 - Warning for requested/allocated thread discrepancy is printed twice
Issue #2313 - –hpx:print-bind doesn’t work with –hpx:pu-step
Issue #2312 - –hpx:bind range specifier restrictions are overly restrictive
Issue #2311 - hpx_0.9.99 out of project build fails
PR #2310 - Simplify function registration
PR #2309 - Spelling and grammar revisions in documentation (and some code)
PR #2306 - Correct minor typo in the documentation
PR #2305 - Cleaning up and fixing parcel coalescing
PR #2304 - Inspect checks for stream related includes
PR #2303 - Add functionality allowing to enumerate threads of given state
PR #2301 - Algorithm overloads fix for VS2013
PR #2300 - Use <cstdint>, add inspect checks
PR #2299 - Replace boost::[c]ref with std::[c]ref, add inspect checks
PR #2297 - Fixing compilation with no hw_loc
PR #2296 - Hpx compute
PR #2295 - Making sure for_loop(execution::par, 0, N, …) is actually executed in parallel
PR #2294 - Throwing exceptions if the runtime is not up and running
PR #2293 - Removing unused parcel port code
PR #2292 - Refactor function vtables
PR #2291 - Fixing 2286
PR #2290 - Simplify algorithm overloads
PR #2289 - Adding performance counters reporting parcel related data on a per-action basis
Issue #2288 - Remove dormant parcelports
Issue #2286 - adjustments to parcel handling to support parcelports that do not need a connection cache
PR #2285 - add CMake option to disable package export
PR #2283 - Add more inspect checks for use of deprecated components
Issue #2282 - Arithmetic exception in executor static chunker
Issue #2281 - For loop doesn’t parallelize
PR #2280 - Fixing 2277: build failure with PAPI
PR #2279 - Child vs parent stealing
Issue #2277 - master branch build failure (53c5b4f) with papi
PR #2276 - Compile time launch policies
PR #2275 - Replace boost::chrono with std::chrono in interfaces
PR #2274 - Replace most uses of Boost.Assign with initializer list
PR #2273 - Fixed typos
PR #2272 - Inspect checks
PR #2270 - Adding test verifying -Ihpx.os_threads=all
PR #2269 - Added inspect check for now obsolete boost type traits
PR #2268 - Moving more code into source files
Issue #2267 - Add inspect support to deprecate Boost.TypeTraits
PR #2265 - Adding channel LCO
PR #2264 - Make support for std::ref mandatory
PR #2263 - Constrain tuple_member forwarding constructor
Issue #2262 - Test hpx.os_threads=all
Issue #2261 - OS X: Error: no matching constructor for initialization of ‘hpx::lcos::local::condition_variable_any’
Issue #2260 - Make support for std::ref mandatory
PR #2259 - Remove most of Boost.MPL, Boost.EnableIf and Boost.TypeTraits
PR #2258 - Fixing #2256
PR #2257 - Fixing launch process
Issue #2256 - Actions are not registered if not invoked
PR #2255 - Coalescing histogram
PR #2254 - Silence explicit initialization in copy-constructor warnings
PR #2253 - Drop support for GCC 4.6 and 4.7
PR #2252 - Prepare V1.0
PR #2251 - Convert to 0.9.99
PR #2249 - Adding iterator_facade and iterator_adaptor
Issue #2248 - Need a feature to yield to a new task immediately
PR #2246 - Adding split_future
PR #2245 - Add an example for handing over a component instance to a dynamically launched locality
Issue #2243 - Add example demonstrating AGAS symbolic name registration
Issue #2242 - pkgconfig test broken on CentOS 7 / Boost 1.61
Issue #2241 - Compilation error for partitioned vector in hpx_compute branch
PR #2240 - Fixing termination detection on one locality
Issue #2239 - Create a new facility lcos::split_all
Issue #2236 - hpx::cout vs. std::cout
PR #2232 - Implement local-only primary namespace service
Issue #2147 - would like to know how much data is being routed by particular actions
Issue #2109 - Warning while compiling hpx
Issue #1973 - Setting INTERFACE_COMPILE_OPTIONS for hpx_init in CMake taints Fortran_FLAGS
Issue #1864 - run_guarded using bound function ignores reference
Issue #1754 - Running with TCP parcelport causes immediate crash or freeze
Issue #1655 - Enable zip_iterator to be used with Boost traversal iterator categories
Issue #1591 - Optimize AGAS for shared memory only operation
Issue #1401 - Need an efficient infiniband parcelport
Issue #1125 - Fix the IPC parcelport
Issue #839 - Refactor ibverbs and shmem parcelport
Issue #702 - Add instrumentation of parcel layer
Issue #668 - Implement ispc task interface
Issue #533 - Thread queue/deque internal parameters should be runtime configurable
Issue #475 - Create a means of combining performance counters into querysets


Achievements
|
-
Intern at Tech Analogy
- July,2021 - Present.
-
Collaborate on amazing projects and workshops
- Certified Responsive Web Developer from freecodecamp.org
- Completed CyberSecurity Internship at Supraja Technologies
- August,2020 - September,2020
- Performed Variious Tasks and Assignments
- Completed Advanced CyberSecurity Internship at Supraja Technologies
- April,2021-June,2021
- Hunted Bugs in Websites and prepared reports for submition
- Advanced Level C++ Programmer and Intermediated Level Python Programmer
- Have in-depth knowledge of javascript and Node.js
|
|


abstract fun executeCommand(command: ByteArray): ByteArray?
Implement logic to execute the command and commit the transaction to the log. Helper methods are provided for transaction processing: commitInputStates, validateTimestamp, and sign.


IP Multicast FIB¶
Basics¶
An IP multicast FIB (mFIB) is a data-structure that holds entries that represent a (S,G) or a (*,G) multicast group. There is one IPv4 and one IPv6 mFIB per IP table, i.e. each time the user calls ‘ip[6] table add X’ an mFIB is created.
A path describes either where a packet is sent to or where a packet is received from. mFIB entries maintain two sets of ‘paths’; the forwarding set and the accepting set. Each path in the forwarding set will output a replica of a received packet. A received packet is only accepted for forwarding if it ingresses on a path that matches in the accepting set - this is the RPF check.
To add an entry to the default mFIB for the group (<IP_ADDRESS>, <IP_ADDRESS>) that will replicate packets to GigEthernet0/0/0 and GigEthernet0/0/1, do:
$ ip mroute add <IP_ADDRESS> <IP_ADDRESS> via GigEthernet0/0/0 Forward
$ ip mroute add <IP_ADDRESS> <IP_ADDRESS> via GigEthernet0/0/1 Forward
the flag ‘Forward’ passed with the path specifies this path to be part of the replication set. To add a path from GigEthernet0/0/2 to the accepting (RPF) set do:
$ ip mroute add <IP_ADDRESS> <IP_ADDRESS> via GigEthernet0/0/2 Accept
A (*,G) entry is added by not specifying a source address:
$ ip mroute add <IP_ADDRESS> via GigEthernet0/0/2 Forward
A (*,G/m) entry is added by not specifying a source address and giving the group address a mask:
$ ip mroute add <IP_ADDRESS>/24 via GigEthernet0/0/2 Forward
Entries are deleted when all paths have been removed and all entry flags (see below) are also removed.
Advanced¶
There are a set of flags associated only with an entry, see:
$ show mfib route flags
only some of these are relevant over the API/CLI:
Signal - packets that match this entry will generate an event that is sent to the control plane (which can be retrieved via the signal dump API)
Connected - indicates that the control plane should be informed of connected sources (also retrieved via the signal dump API)
Accept-all-itf - the entry shall accept packets from all interfaces, thus eliminating the RPF check
Drop - Drop all packet matching this entry.
flags on an entry can be changed with:
$ ip mroute <PREFIX> <FLAG>
An alternative approach to the RPF check, that does check the accepting path set, is to give the entry and RPF-ID:
$ ip mroute <PREFIX> rpf-id X
the RPF-ID is an attribute of a received packet’s meta-data and is added to the packet when it ingresses on a given entity such as an MPLS-tunnel or a BIER table disposition entry.


This chapter describes the set of core expression types available in the #F’s default environment. These expression types, together with macro forms [ch.4], definitions [ch.5], and system interface constructs [7.] provide all necessary machinery for bulding a larger language (or languages) in a modular and controlled manner. #F system comes with a set of pre-built libraries which provide most of the features expected of a reasonably complete Scheme system. These libraries are built on top of the core language described here and each other; from the compiler’s point of view, the libraries are no different from any other #F source file.
The core language provides a set of basic Scheme expressions, aimed at representing non-redundant features of Scheme. A smaller set could be devised, but this one is sufficiently small for practical purposes (that is to give the compiler something to chew on).
| variable | syntax |
An expression consisting of a variable (an identifier which is not a syntactic keyword) is a variable reference. The value of the variable reference is the value stored in the location to which the variable is bound. It is an error to reference an unbound variable.
The following example assumes the base math library has been imported:
(define x 28) x ⇒ 28
(operator operand1 …) | syntax |
A procedure call consists of expressions for the procedure to be called and the arguments to be passed to it, with enclosing parentheses. A form in an expression context is a procedure call if macroexpansion of operator does not produce a macro transformer (see section ?.? Macro uses).
When a procedure call is evaluated, the operator and operand expressions are evaluated (in an unspecified order) and the resulting procedure is passed the resulting arguments.
The following example assumes the base math library has been imported:
(+ 3 4) ⇒ 7 ((if #f + *) 3 4) ⇒ 12
(lambda (variable1 …) expression) | syntax |
A lambda expression evaluates to a procedure. The environment in effect when the lambda expression was evaluated is remembered as part of the procedure. When the procedure is later called with some actual arguments, the environment in which the lambda expression was evaluated will be extended by binding the variables in the formal argument list to fresh locations, the corresponding actual argument values will be stored in those locations, and the expression in the body of the lambda expression will be evaluated in the extended environment. The result(s) of the body expression will be returned as the result(s) of the procedure call.
The following example assumes the base math library has been imported:
(lambda (x) (+ x x)) ⇒a procedure((lambda (x) (+ x x)) 4) ⇒ 8 (define reverse-subtract (lambda (x y) (- y x))) (reverse-subtract 7 10) ⇒ 3 (define add4 ((lambda (x) (lambda (y) (+ x y))) 4)) (add4 6) ⇒ 10
It is an error for a variable to appear more than once in the formal argument list.
Note: In contrast to other dialects of Scheme, #F does not support sequences of definitions and expressions as primitive syntax of lambda expressions. Improper argument lists are also not considered primitive. Both features can be introduced by extending the primitive form (as exemplified by definitions provided in base library).
Note: #F does not require each procedure created as the result of evaluating a lambda expression to be (conceptually) tagged with a unique storage location. Two computationally equivalent procedures may share a single storage location even if they were created by two distinct lambda expressions.
(if test consequent alternate) | syntax |
An if expression is evaluated as follows: first, test is evaluated. If it yields a true value (see section ?.?), then consequent is evaluated and its value(s) is(are) returned. Otherwise alternate is evaluated and its value(s) is(are) returned. Test, consequent, and alternate may be arbitrary expressions.
The following example assumes the base math library has been imported:
(if (> 3 2) 'yes 'no) ⇒ yes (if (> 2 3) 'yes 'no) ⇒ no (if (> 3 2) (- 3 2) (+ 3 2)) ⇒ 1
Note: In contrast to other dialects of Scheme, #F does not support one-armed if form as primitive. This feature can be added by extending the primitive form (and can be imported from base library).
(set! variable expression) | syntax |
Expression is evaluated, and the resulting value is stored in the location to which variable is bound. Variable must be bound either in some region enclosing the set! expression or at top level of the current compilation unit. The result of the set! expression is unspecified.
(define x 2) (+ x 1) ⇒ 3 (set! x 4) ⇒unspecified(+ x 1) ⇒ 5
Note: #F does not allow the same top-level variable to be assigned from more than one compilation unit.
(letcc variable expression) | syntax |
A letcc expression is evaluated as follows: first, the continuation for the letcc expression being evaluated is captured in a form of a procedure. Then, the environment in which the letcc expression is evaluated is extended by binding variable to a fresh location, the continuation procedure is stored in this location, and expression is evaluated in the extended environment. The result(s) of the expression is(are) returned.
(withcc continuation expression) | syntax |
When a withcc expression is evaluated, continuation is evaluated and the resulting procedure is used as the continuation for evaluation of expression. The result(s) of the expression is(are) returned directly to the supplied continuation procedure in a tail-recursive manner. The continuation used to evaluate withcc form is ignored.
Rationale: #F’s special-form interface to continuations is chosen for three reasons. First, it allows for a more precise syntactic characterization of the proper tail-recursive behavior in presence of continuations: if letcc or withcc form is in tail position, its body expression is also in tail position. Second, Scheme’s traditional call/cc interface does not allow passing the values of an application to a continuation procedure in a tail-recursive manner (both direct application and call-with-values have to add an extra control frame because of the procedural nature of the interface). Third, the letcc / withcc pair is not encumbered by dynamic contexts and translates to CPS in a straightforward manner (and allows reverse translation for CPS form with no restrictions on the use of continuation-bound identifiers). Traditional Scheme interface built upon these two forms can be imported from base library.
(sequence expression1 expression2) | prototype syntax |
The sequence expression is one of #F’s “stub” or “prototype” syntax forms which have a suggested semantics but are not implemented in the core language itself. The raison d'être for such forms is to pass as many implementation decisions as possible to library authors in cases when the related “surface” syntax has to be supported, but cannot be implemented as a macro.
The suggested semantics for the sequence expression is first to evaluate expression1, discarding its return values in an implementation-dependent manner. Then, expression2 is to be evaluated tail-recursively and its result(s) is(are) returned.
Sequence expressions can be written explicitly or appear as intermediate forms during expansion of some begin, syntax-lambda, top-level and derived forms featuring implicit sequencing (in a form of a “body” or a “sequence of commands”). If any such form is used in the program, a syntax transformer for the sequence form should be provided.
(begin expression1 expression2 …) | derived syntax |
The begin expression provides one of several ways to request sequencing of side effects (the other being implicit body of a syntax-lambda form and top-level of a compilation unit). The semantics of begin expressions is fully defined by their transformation into nested sequence expressions, as if begin were defined as follows:
(define-syntax begin (syntax-rules () ((begin exp1 exp2) (sequence exp1 exp2)) ((begin exp1 exp2 . more) (sequence exp1 (begin exp2 . more)))))
In reality, begin’s transformer has to handle the use of begin as a definition form (see ?.?) and a splicing top-level form (see ?.?). #F’s macro definition mechanism is not expressive enough to handle overloaded syntax forms, so they are handled by built-in syntax transformers.
Examples:
(define x 1) (begin (set! x 4) 5) ⇒error: sequence is not defined(define-syntax sequence (syntax-rules () ((sequence exp1 exp2) ((lambda (ignore) exp1) exp2)))) (begin (set! x 4) 5) ⇒ 5 x ⇒ 4 (begin (letcc k (k 1 2)) 5) ⇒error: too many values


The Web Is Dead, Long Live the Web
I love the Ignite format for presentations, where you have to get your point across in five minutes with 20 slides that advance automatically every 15 seconds.
Bill Appleton made a good point with his Fluent 2014 Ignite Presentation “The Big Shift From Web Pages to RESTful Apps”. He reminds us that the legacy Internet is basically based on Ethernet: high bandwidth, low latency, and cheap because you pay for the connection, not the bytes. Then he contrasts that with the new mobile web network: lower in bandwidth, higher in latency, and expensive because you’re charged for your data consumption.
This is part of the reason the old school dev paradigm of server-side MVC–with data, logic and presentation all happening on a server tier–is showing its age so poorly. The old click-get-a-page model is predisposed to a high bandwidth, low latency connection with a simple browser on the end node doing nothing more than rendering what the server sent in HTML.
Appleton proposes that the new development stacks emerging are in part a response to this infrastructure change. The new model of services in the middle producing tiny chunks of JSON instead of an app server that creates heavy HTML are at least in part a response to the network limitations of mobile, but it’s these new stacks that have also enabled native mobile apps and the Internet of Things.
This meshes with what John Gruber writes in “Rethinking What We Mean by ‘Mobile Web’”. The new mobile app landscape isn’t a replacement for the old HTML/CSS/JavaScript world, it’s a complement to it.
The new web is the old web. REST APIs fit in well with the web model: it will still be a web of linked content, but we’ll be delivering more JSON than HTML.


Best Student Branch Activity Award
Description
The award is presented annually, under the domain of IEEE Sri Lanka Section to recognize an initiative taken by a student branch that proved to be of strategic importance to the IEEE’s goal and development objectives of IEEE Sri Lanka Section. Purpose of the award is to increase the quality of events organized by student branches in Sri Lanka and to encourage more creative ideas with a significant impact.
Eligibility Criteria
- The award requires interested student branches to submit a report on their initiative(s).
- The event should not be coupled with any other event unless they are related and if related, it should be clearly proven in the report.
- The activities should be reported to the IEEE, using vTools, to be eligible for the award.
- The event should fall within 1st November, 2016 and 1st November, 2017.
- Any student branch, active or newly established can submit nominations for the award.
Best Young Professional Activity Award
Description
The award is presented annually, under the domain of IEEE Sri Lanka Section to recognize an initiative taken the young professionals community that proved to be of strategic importance to IEEE’s goals and development of IEEE Sri Lanka. Purpose of the award is to increase the quality of events organized by young professional’s community in Sri Lanka and to encourage more creative ideas with a significant impact.
Eligibility Criteria
- The award requires the interested activity chairs to submit a report of their initiative(s).
- The event should not be coupled with any other event unless they are related and if related, it should be clearly proven in the report.
- The activities should be reported to the IEEE, using vTools, to be eligible for the award.
- The event should fall within 1st November 2016 and 1st November 2017.
Best WIE Activity Award
Description
The award is presented annually, under the domain of IEEE Sri Lanka Section, to recognize an initiative taken by a student branch affinity group of IEEE WIE that proved to be of strategic importance to IEEE’s goals and development objectives of IEEE Sri Lanka. Purpose of the award is to increase the quality of events organized by affinity groups of IEEE WIE in Sri Lanka and to encourage young women to come up with more creative ideas with significant impact.
Eligibility Criteria
- The award requires interested WIE affinity groups to submit a report of their initiative(s).
- The event should not be coupled with any other event unless they are related and if related, it should be clearly proven in the report.
- The activities should be reported to the IEEE, using vTools, to be eligible for the award.
- The event should fall within 1st November 2016 and 1st November 2017.
- Any student branch, active or newly established can submit nominations for the award.
Membership Retention Award
Description
The award is presented annually, under the domain of IEEE Sri Lanka Section to recognize the student branch(s) which contributes to the IEEE Sri Lanka Section on membership development and retention.
Eligibility Criteria
- All the active student branches under Sri Lanka Section will be eligible for the award.
- Student branches don’t have to apply for this award. IEEE SL SAC will gather the data from SAMIEEE and based on the data winner will be chosen.
Nomination Process
- Nomination for the award shall be submitted by filling an online application on or before 12th December 2017. Fill the nomination form and complete each section in a concise manner, explaining how the activity qualifies for the award.
- Attach a report to the google form with photos, promotional materials, testimonials etc. It is compulsory that the attachment is limited to a maximum of five(5) pages and is in pdf format (can be opened in Adobe pdf viewer and Foxit Reader). Documents not adhering to these criteria will not be considered for evaluation.
- Submitting more than one nomination for the same activity will result in disqualification.
- When successful submission is done, the person who did the nomination should receive an email within 48 hours. If not please consult with IEEE Sri Lanka Awards Committee on<EMAIL_ADDRESS>Judging Committee
The judging committee will also include a selected set of members from the Section executive committee.
The result for this award along with the points and justification(s) shall be revealed anonymously after the deadline and before awards presentation to all nominees.
The decision of the judging committee shall be the final and cannot be challenged.
Award Instrument
A token of appreciation.
Presentation
The award shall be presented at the IEEE Sri Lanka Section SYW Congress 2017 to be held from 22nd to 24th December 2017. The awards ceremony will take place 22nd December 2017. Please be advised, no travel grant or funds in any means shall be provided to the winners by IEEE Sri Lanka Section. The award winner shall be responsible for their own expenses.
Publicity Rights
Information provided by the nominators for the IEEE Sri Lanka Section awards may be used for the promotional and/or publicity purpose on IEEE websites, Facebook, Twitter and other social medias, printed materials and press releases etc. By submitting a nomination, nominators and nominee agree for the release of submitted information and the photographs of awards ceremony for these purpose.
Evaluation Criteria
Each nomination will be evaluated with a predefined criteria and shall be given a score out of hundred (100) which is calculated as follows;
Value Creation (0-35)
- Uniqueness and Creativity (0-15)
- Positive impact (0-10)
- Value driven after event i.e. post results (0-10)
Participation Status (0-35)
- Participation/Collaboration with other student branches or affinity groups (0-10)
- Collaboration with other NGO/ Companies/ Organizations/ Public etc (0-10)
- Implementation (0-10)
Sustainability (0-30)
- Repeatability (0-15)
- Potential to be applied in other student branches 90-10)
- Portability (0-5)


Mock It 'til You Make It
Tech
Demo App
Storybook Stories
So far...
So far...
Stories with Mocking
Stories with Auto Mocking
So far...
So far...
So far...
So far...
Auto Mocking with Local Resolvers
Auto Mocking with Merged Resolvers
So far...
So far...
Stories with Auto Mocked States
So far...
Mocking with Local State
Mock It 'til You Make It
References
Licensing


--- layout: post title: "January 2017 Ed-Tech Funding" date: 2017-02-05 12:35:00 +0000 tags: image: https://s3.amazonaws.com/audreywatters/2017-02-05-justice.jpg imagecredits: http://algorithmic.rotoscope.work/ ---
Education technology startups raised $172,150,000 in January. More than half that total was the $100,000,000 invested in homework help platform Xueba100.com.
The total for January was down by about $2 million from this time last year, and down by about half from January 2015 (a record-setting year for ed-tech investment). The size of the average investment was down by about $1 million. The number of deals – 22 – was up slightly from January 2016 when there were 17. There were 11 acquisitions in January; the same as last year.
It’s far too early to identify trends, although I can’t help but notice that a student loan startup, a tutoring startup, and two homework help startups raised money. Some things do not change…
As always the data for this project is freely available on GitHub.


.NET Conf: Focus on Xamarin Watch .NET Conf: Focus on Xamarin, a free livestream event March 23, 2020 to learn all about how to build native mobile apps with C#. Mark your calendar!
Generated Passwords, UX and Security Absolutism Last month, Disney launched their new streaming service Disney+; "The best stories in the world, all in one place", apparently. The service was obviously rather popular because within days the tech (and mainstream) headlines were proclaiming that thousand...
Edgar Allan Poe Society of Baltimore - Works - Tales - The Philosophy of Composition [Text-02] The Philosophy of Composition, by Edgar Allan Poe
System.Buffers - .NET This article provides an overview of types that help read data that runs across multiple buffers. They're primarily used to support PipeReader objects.
.NET Design Review: GitHub Quick Reviews 00:00:00 - Approved: More cancellation overloads for HttpContent https://github.com/dotnet/runtime/issues/576#issuecomment-564164757 00:14:05 - Needs Work: Option to allow HttpClient to follow HTTPS -) HTTP redirects https://github.com/dotnet/corefx/issu...
Talk to Transformer See how a modern neural network completes your text. Type a custom snippet or try one of the examples. Learn more below.
Start PowerShell Faster With This One Trick The title of this post is very tongue in cheek and a bit of a jab at click-bait posts, but I genuinely have a “trick” that will make starting up PowerShell faster and give you hours back throughout your development career.
Debugging 3rd Party .NET Code without symbols in Visual Studio - Michael's Coding Spot It's not so rare to see weird things happen in 3rd party library code. Call some method and you've got a strange exception. Or an incorrect behavior or even a process crash. It sure would be nice to debug some of these issues. In this article we're going ...
AWS re:Invent 2019: [REPEAT 1] BPF performance analysis at Netflix (OPN303-R1) Extended BPF (eBPF) is an open-source Linux technology that powers a whole new class of software: mini programs that run on events. Among its many uses, BPF can be used to create powerful performance-analysis tools capable of analyzing everything: CPUs, m...
ASP.NET Community Standup - Dec 3rd, 2019 - Blazor Update with Daniel Roth Join members from the ASP.NET teams for our community standup covering great community contributions for ASP.NET, ASP.NET Core, and more. Community Links: https://www.theurlist.com/aspnet-standup-2019-12-03
Azure Functions 3.0 go-live release is now available | Azure updates | Microsoft Azure The go-live release for Azure Functions 3.0 is now available, so it’s now possible to build and deploy 3.0 functions in production. Functions 3.0 brings new capabilities including the ability to target .NET Core 3.1 and Node 12.
Creating Bespoke Input Components for Blazor from Scratch In this post, I'm going to show you how to create bespoke input components for your Blazor applications. We'll look at how to integrate with Blazor's validation system, but also, how to work outside it.
Blazor: Getting Started Learn how to build your first application in a hands-on way using Blazor, Microsoft's solution to use C# to write interactive web UIs without JavaScript.
We made Windows Server Core container images >40% smaller | .NET Blog Over the past year, we’ve been working with the Windows Server team to make Windows Server Core container images a lot smaller. They are now 40% smaller! The Windows Server team has already published the new images in the Server Core Insider Docker repo,
.NET Core, Docker, and Cultures - Solving a culture issue porting a .NET Core app from Windows to Linux In this post I describe how I fixed an issue with Cultures that arose when porting an ASP.NET Windows app to ASP.NET Core on Linux.
Seeing Sharply Technical blog of Microsoft certified developer James Hickey. Helping you reach the next step of your career as a software developer!
Hitting Parallel_Redo_Flow_Control waits with Availability Groups In late June 2019, June 26th to be exact, we experienced an outage on Stack Overflow for about 11 minutes. It’s not unusual that we had an outage. They happen. Not often, but they do still happen. This one, however, was a little different because it was c...
GC Perf Infrastructure - Part 1 | .NET Blog We open sourced our new GC Perf Infrastructure! It’s now part of the dotnet performance repo. I’ve been meaning to write about it ‘cause some curious minds had been asking when they could use it after I blogged about it last time but didn’t get around to ...
How to generate random numbers using water bubbles BubblesRNG - This was my final project I submitted as part of my reading the B.Sc. Computing and Information Systems degree at Goldsmith, University of London. The camera take snapshots of the water surface at regular intervals and detects bubbles (circl...