投稿時間:2022-11-15 19:20:43 RSSフィード2022-11-15 19:00 分まとめ(26件)

カテゴリー等 サイト名等 記事タイトル・トレンドワード等 リンクURL 頻出ワード・要約等/検索ボリューム 登録日
TECH Techable(テッカブル) 出社社員と在宅社員が気軽に立ち話できる! 近寄るだけで離れたワーカーと話せるデバイスが発売 https://techable.jp/archives/186628 当たり前 2022-11-15 09:54:26
TECH Techable(テッカブル) エレコムがついにミュート不要で自分の声だけ拾うヘッドセットを発売!地下鉄車内レベルの騒音も余裕でカット https://techable.jp/archives/186612 騒音 2022-11-15 09:33:55
AWS AWS - Japan Git の最新アップデートから考える開発手法の潮流 #AWSDevLiveShow https://www.youtube.com/watch?v=ScNN3uGXFd0 Gitは「clone」して「ファイルを編集」して「add」して「commit」、「push」するのが基本的な流れですが、チーム開発をしていると「merge」、「rebase」など少し理解が難しいものが出てくると思います。 2022-11-15 09:29:09
python Pythonタグが付けられた新着投稿 - Qiita Databricks にて Azure Synapse Analytics Dedicated SQL (専用 SQL プール) から Spark コネクター経由でデータを取得する方法の検証 https://qiita.com/manabian/items/7217bd388007db05d54a azure 2022-11-15 18:48:27
python Pythonタグが付けられた新着投稿 - Qiita n**2+1の素数判定を2次ふるいで行う https://qiita.com/masa0599/items/89d295035fbcd6333dc1 sympy 2022-11-15 18:30:35
python Pythonタグが付けられた新着投稿 - Qiita VSCodeでPythonインタープリターが選択できない https://qiita.com/nebocco/items/ad873b7ca98a5067daa4 pythonex 2022-11-15 18:23:36
Ruby Rubyタグが付けられた新着投稿 - Qiita 【Ruby on Rails】pry-rails導入方法 https://qiita.com/slamdunkducksky/items/524efb58b35e48f1e5a8 bundleinstalltechcamp 2022-11-15 18:36:13
AWS AWSタグが付けられた新着投稿 - Qiita 祝!VMware Cloud on AWS の i4i.metalインスタンスがGAされました https://qiita.com/sanjushi003/items/be4b4f06e9a1151314c6 iimetal 2022-11-15 18:30:25
Azure Azureタグが付けられた新着投稿 - Qiita Databricks にて Azure Synapse Analytics Dedicated SQL (専用 SQL プール) から Spark コネクター経由でデータを取得する方法の検証 https://qiita.com/manabian/items/7217bd388007db05d54a azure 2022-11-15 18:48:27
Ruby Railsタグが付けられた新着投稿 - Qiita 【Ruby on Rails】pry-rails導入方法 https://qiita.com/slamdunkducksky/items/524efb58b35e48f1e5a8 bundleinstalltechcamp 2022-11-15 18:36:13
技術ブログ Mercari Engineering Blog メルカリShopsの注文システム安定化の歩み https://engineering.mercari.com/blog/entry/20221115-improve-order-system/ hellip 2022-11-15 10:00:35
技術ブログ Developers.IO GrafanaのTime streamsで棒グラフと折れ線グラフを同じパネルに表示する https://dev.classmethod.jp/articles/display-line-and-bar-graphs-in-the-same-panel-with-grafana-time-streams/ delivery 2022-11-15 09:35:37
技術ブログ Developers.IO Amazon AppFlow カスタムコネクタで使用する Lambda 関数を VPC Lambda にする場合は Secrets Manager への通信経路を確保する必要がある https://dev.classmethod.jp/articles/amazon-appflow-custom-connector-vpc-lambda/ amazonappflow 2022-11-15 09:28:14
海外TECH MakeUseOf 5 Hidden Gems Curators to Discover Weird and Wacky Things Online https://www.makeuseof.com/hidden-gems-curators-discover-weird-wacky-things-online/ Hidden Gems Curators to Discover Weird and Wacky Things OnlineFrom weird articles on Wikipedia to the best updates from advice seekers on Reddit these are the internet s most fascinating hidden gems 2022-11-15 09:30:14
海外TECH DEV Community How to use the ElevatedButton widget in Flutter? https://dev.to/kuldeeptarapara/how-to-use-the-elevatedbutton-widget-in-flutter-1jf7 How to use the ElevatedButton widget in Flutter This article will give examples of using the ElevatedButton widget in Flutter starting with the most fundamental usage It is the perfect example written by our Flutter experts who have vast experience developing Flutter apps One of the buttons in Material Design in Flutter web is called Elevated Button has the feature of rising in elevation as the user presses it Use the ElevatedButton widget in Flutter if you need to construct a Material Design elevated button When tapped by the user these buttons primary feature is a small elevation of their surface toward the screen Simply put elevated buttons are raised non deprecated buttons without a clearly defined button style There are two parameters It goes without saying that you must transmit a Widget as a child usually a Text or an Icon widget Additionally you must pass the onPressed callback which is triggered when a button is pressed by the user A static factory function ElevatedButton icon makes it simpler for you to create an elevated button that has both Icon and Text widgets For each icon and label you must pass a Widget rather than a child This constructor can be used to create an ElevatedButton ElevatedButton Key key required VoidCallback onPressed VoidCallback onLongPress ValueChanged onHover ValueChanged onFocusChange ButtonStyle style FocusNode focusNode bool autofocus false Clip clipBehavior Clip none MaterialStatesController statesController required Widget child What are the properties of an ElevatedButton autofocus It delivers a boolean value which corresponds to the button s initial focus of Flutter clipBehaviour Whether or not the content is clipped is determined by clipBehavior focusNode Depicts the widget s focus node ButtonStyle style Determines how the button will be styled onLongPress When the button is long pressed by the user an action is to be taken called onLongPress enabled Gives a boolean value for the button s activity called “enabled hashcode The button s hashcode is determined by the hashcode onFocusChanged When a button s focus changes a method called onFocusChanged is called onHover The action that will be carried out when the user hovers over the button Example import package flutter material dart void main runApp const MyApp class MyApp extends StatelessWidget const MyApp super key override Widget build BuildContext context return const MaterialApp home MyHomePage class MyHomePage extends StatefulWidget const MyHomePage super key override State createState gt MyHomePageState class MyHomePageState extends State override Widget build BuildContext context return Scaffold body Column mainAxisAlignment MainAxisAlignment center crossAxisAlignment CrossAxisAlignment center children ElevatedButton style ElevatedButton styleFrom minimumSize const Size padding const EdgeInsets symmetric horizontal shape const RoundedRectangleBorder borderRadius BorderRadius all Radius circular onPressed child const Text Looks like a RaisedButton ElevatedButton style ElevatedButton styleFrom onPressed child const Text ElevatedButton with custom foreground background ElevatedButton style ElevatedButton styleFrom backgroundColor Colors red onPressed null child const Text ElevatedButton with custom disabled colors ElevatedButton style ButtonStyle backgroundColor MaterialStateProperty resolveWith Set states if states contains MaterialState disabled return Colors red return Colors blue Defer to the widget s default foregroundColor MaterialStateProperty resolveWith Set states if states contains MaterialState disabled return Colors blue return Colors blue Defer to the widget s default onPressed null child const Text ElevatedButton with custom disabled colors ElevatedButton style ButtonStyle elevation MaterialStateProperty resolveWith Set states if states contains MaterialState pressed return return onPressed child const Text ElevatedButton with a custom elevation Output Conclusion So in this article we learned how to use the ElevatedButton widget You can change and update this Flutter code according to your requirement I hope you liked reading this Flutter is the best choice to develop your business apps Adopt a Flutter app development company to build your dream Flutter mobile application Frequently Asked Questions FAQs Which is the essential argument for an ElevatedButton in Flutter You can make the ElevatedButton in the Flutter by calling the constructor Usually there are two kinds of parameters First you must pass the widget as a child and the text or icon You also have to give the onPressed Callback that is called when the user presses the button How do you increase the size of a widget in Flutter app development You can utilize the LayoutBuilder which will fetch a parent widget s dimension and will adjust the children s widget dimension according to the parent How do you give the style to an ElevatedButton in a Flutter project You can not provide the style to ElevatedButtons in Flutter You cannot modify the button s color font size etc Explicitly like raised buttons You can pass the text or icons as a child widget to them 2022-11-15 09:11:10
海外TECH DEV Community How KuFlow supports Temporal as a worfkows engine for our processes? https://dev.to/kuflow/how-kuflow-supports-temporal-as-a-worfkows-engine-for-our-processes-3j5c How KuFlow supports Temporal as a worfkows engine for our processes In such a diverse world it would be boring to have a single way of doing things That s why at KuFlow we support different ways to implement the logic of our processes and tasks And in this post we will talk about one of them the orchestration through Temporal which gives us a powerful way to manage our workflows We will not go into detail on the concepts that are handled in our platform for that you can consult the documentation or other blog entries but as a general idea we can stay with the following KuFlow is a platform that allows you to model business processes that involve a series of tasks to carry out their achievement These tasks can be performed by humans or by systems and are basically activities to perform actions and or collect information We also need to establish a way to control the performance of these tasks their order their asynchronous or non asynchronous nature or their ability to recover from errors In other words we need a workflow to orchestrate our process At KuFlow we call WorkFlow Engine for the different types of implementations we support In this case Temporal is the Workflow Engine Why use Temporal for your KuFlow processes The use of Temporal gives us several benefits the main one being the ability to implement the resilience of our operations in a comfortable and reliable way For example let s imagine that a task of one of our processes makes a call to a third party API If this API is not available at the time of its call the task fails and our process could be blocked In this case we would like the workflow of our process to be retried later and have to forget about all the scaffolding required to do so Also if we have already issued modification requests to other external APIs we would like that when recovering the process the consumption of these APIs would be deterministic and would not fail because we have consumed them twice We achieve all this by implementing our workflows with Temporal How does Temporal integrate with KuFlow In order to simplify as much as possible the infrastructure of our customers in KuFlow we have our own Temporal cloud avoiding the need to deploy this infrastructure by customers Having a Temporal cloud is not our core business and in the future we may also offer the possibility to use other clouds such as Temporal Cloud or any other To implement a Workflow in a process using Temporal we need to develop what in KuFlow we call Worker A worker is nothing more than an application that runs on our customers servers and interacts with the KuFlow API and the Temporal API available in our cloud This approach allows for a hybrid cloud architecture that provides flexibility when accessing the different services that you want to consume in the Worker Thus for example a Worker deployed on the customer s servers would have access to the customer s private services in a secure and reliable way in order to extract data and make decisions based on their needs To facilitate the development of this Worker a library that facilitates the consumption of the KuFlow API through Temporal Activities is provided Together with the different SDKs provided by Temporal the construction of a Worker is in most cases child s play The various languages for which these libraries are provided are updated frequently SecurityOne of the most important aspects for us is everything related to security And for this reason apart from a powerful RBAC system that is deployed on the customer s resources we use a series of authentication mechanisms to access the different APIs that we offer To facilitate the management of access and credentials to these APIs KuFlow defines the concept of Application By definition an Application is composed of credentials and access certificates In turn these applications are used as candidates or principals to grant roles and permissions to the resources you want How is authentication and authorization achieved with the Temporal API Schematically to authenticate we will use Mutual TLS and to get authorization we will use a JWT bearer token Obtaining the certificates and credentials is done from the KuFlow App in a simple way without the need to create and upload the certificates manually Armed with this data we can now connect our workers to the KuFlow cloud The authentication mechanism follows the following flow On the one hand it is necessary to obtain a JWT bearer token that will allow us authorization in Temporal for this a request is issued to the KuFlow API Rest authenticated by BasicAuth that returns the token With this token the communications to Temporal s API GRPC are made besides using the certificates to encrypt the communication and to achieve the authentication with this API For more information please refer to the documentation To deal with problems such as carrier token renewal and to make the developer s experience as comfortable as possible this mechanism is implemented in the libraries we provide as support for Workers An example of token renegotiation can be seen in this code extracted from the kuflow engine client library in Java public class KuFlowAuthorizationTokenSupplier implements AuthorizationTokenSupplier private static final Logger LOGGER LoggerFactory getLogger KuFlowAuthorizationTokenSupplier class private static final double EXPIRE PERCENTAGE private static final Duration EXPIRE MAX DURATION Duration ofMinutes private final AuthenticationApi authenticationApi private volatile String token private volatile Instant tokenExpireAt public KuFlowAuthorizationTokenSupplier AuthenticationApi authenticationApi this authenticationApi authenticationApi Override public String supply String token this requestToken return Bearer token private String requestToken String token this token Instant tokenExpireAt this tokenExpireAt if isTokenNonExpired token tokenExpireAt return token synchronized this token this token tokenExpireAt this tokenExpireAt if isTokenNonExpired token tokenExpireAt return token AuthenticationResource authentication new AuthenticationResource authentication setType AuthenticationTypeResource ENGINE authentication this authenticationApi createAuthentication authentication Duration expireDuration Duration between Instant now authentication getExpiredAt expireDuration Duration ofSeconds long expireDuration getSeconds EXPIRE PERCENTAGE if expireDuration compareTo EXPIRE MAX DURATION gt expireDuration EXPIRE MAX DURATION this token token authentication getToken this tokenExpireAt tokenExpireAt Instant now plus expireDuration LOGGER debug Regenerated JWT Temporal authorization token Expired at tokenExpireAt return token private static boolean isTokenNonExpired String token Instant tokenExpireAt return token null amp amp tokenExpireAt null amp amp Instant now isBefore tokenExpireAt What we have done here is to implement the AuthorizationTokenSupplier interface provided by the Temporal SDK to use our KuFlow API client library to negotiate a token when needed In the same way we implemented the GrpcMetadataProvider interface with the purpose of adding as metadata the token provided by the previous implementation public class AuthorizationGrpcMetadataProvider implements GrpcMetadataProvider public static final Metadata Key lt String gt AUTHORIZATION HEADER KEY Metadata Key of authorization Metadata ASCII STRING MARSHALLER private final AuthorizationTokenSupplier authorizationTokenSupplier public AuthorizationGrpcMetadataProvider AuthorizationTokenSupplier authorizationTokenSupplier this authorizationTokenSupplier authorizationTokenSupplier Override public Metadata getMetadata Metadata metadata new Metadata metadata put AUTHORIZATION HEADER KEY authorizationTokenSupplier supply return metadata This metadata provider class for the GRPC connection to Temporal will be the one we will use later when we configure our WorkflowServiceStub in the Worker WorkflowServiceStubsOptions newBuilder addGrpcMetadataProvider new AuthorizationGrpcMetadataProvider new KuFlowAuthorizationTokenSupplier this authenticationApi As the last step to successfully connect to Temporal we need to create an SSL context that will be used in the negotiation with MutualTLS For this we need to extend the SslContext class of the SDK The implementation depends on your needs but an example of it can be found in the following code snippet available in our example repositories on GitHub private SslContext createSslContext MutualTlsProperties mutualTls this applicationProperties getTemporal getMutualTls if StringUtils isBlank mutualTls getCert amp amp StringUtils isBlank mutualTls getCertData return null if StringUtils isNotBlank mutualTls getCert amp amp StringUtils isBlank mutualTls getKey StringUtils isBlank mutualTls getCa throw new KuFlowEngineClientException key and ca are required if StringUtils isNotBlank mutualTls getCertData amp amp StringUtils isBlank mutualTls getKeyData StringUtils isBlank mutualTls getCaData throw new KuFlowEngineClientException keyData or caData are required try InputStream certInputStream this openInputStream mutualTls getCert mutualTls getCertData InputStream keyInputStream this openInputStream mutualTls getKey mutualTls getKeyData InputStream caInputStream this openInputStream mutualTls getCa mutualTls getCaData KeyStore trustStore KeyStore getInstance KeyStore getDefaultType trustStore load null null XCertificate certificate XCertificate CertificateFactory getInstance X generateCertificate caInputStream trustStore setCertificateEntry temporal ca certificate TrustManagerFactory trustManagerFactory TrustManagerFactory getInstance TrustManagerFactory getDefaultAlgorithm trustManagerFactory init trustStore TrustManager trustManager trustManagerFactory getTrustManagers return SimpleSslContextBuilder forPKCS certInputStream keyInputStream setTrustManager trustManager build catch KeyStoreException NoSuchAlgorithmException CertificateException IOException e throw new KuFlowEngineClientException Unable to configure mTLS e Finally like the GRPC metadata provider we add this SSL context to our WorkflowServiceStubs options public WorkflowServiceStubs workflowServiceStubs Builder builder WorkflowServiceStubsOptions newBuilder builder setTarget this applicationProperties getTemporal getTarget builder setSslContext this createSslContext builder addGrpcMetadataProvider new AuthorizationGrpcMetadataProvider new KuFlowAuthorizationTokenSupplier this authenticationApi WorkflowServiceStubsOptions options builder validateAndBuildWithDefaults return WorkflowServiceStubs newServiceStubs options At this point it is useful to remember that when configuring a Temporal backed process in the KuFlow APP it is possible to download a ready to use Worker template that uses these connection configuration mechanisms so you have a working example just a few clicks away Similarly much more information and integration examples can be found in our GitHub repository and in our documentation Notes on the Temporal cloud deployed in KuFlowAs discussed earlier in the article the purpose of offering a Temporal deployment is to facilitate integration for our customers At this point it is important to highlight some issues Our Temporal deployment is a slightly modified version of the one available in the official Temporal repositories Basically security and authorization modifications have been added As a result some API methods are not available For example you will not be able to use our Temporal deployment to execute Workflows that are not launched from KuFlow processes which is necessary to avoid abuse Or in the same way it is also not possible to cancel Workflows if not from the KuFlow App Other APIs may not be available unlike a normal Temporal installation However all the APIs that guarantee the correct functioning of your workers are enabled If you need any of the currently disabled APIs you can request them by contacting us Some other modifications made allow you for example to know from the App if there is any worker currently online for your process In the same way we try to keep our Temporal deployments as up to date as possible if you have any questions about this please contact us ConclusionIn this article we have superficially explored the use of Temporal as a workflow engine for our KuFlow processes This solution provides us with a number of advantages over the other workflow engines we support such as access to private services allowing greater flexibility when implementing Worker In the same way the resilience and scalability offered by Temporal makes it the most recommendable option when the processes are highly complex and need to orchestrate different external APIs The following table shows a summary of the main features of each of the supported Workflows Engine Try KuFlow for free creating your own free account and start automating your company Originally published in KuFlow s Blog How KuFlow supports Temporal as a worfkows engine for our processes 2022-11-15 09:06:11
海外TECH Engadget One of our favorite portable Bluetooth speakers is 30 percent off right now https://www.engadget.com/ultimate-ears-wonderboom-3-portable-speaker-is-30-percent-off-right-now-092518056.html?src=rss One of our favorite portable Bluetooth speakers is percent off right nowIf you re on the lookout for a portable Bluetooth speaker the Ultimate Ears Wonderboom is a top choice and now available at an all time low price You can grab one in four colors at Amazon for for a savings of percent off of the regular price tag nbsp Buy Ultimate Ears Wonderboom at Amazon The UE Wonderboom was one of the stars of our best portable Bluetooth speaker roundup It s tiny yet powerful delivering the biggest sound in its size range It s also quite handsome and the refreshed model comes in a variety of colors including the black white blue and pink models on sale It delivers an extra hour of battery life over the past model along with improved wireless range With an IP rating on top of the company s five foot drop test durability it can go with you almost anywhere and survive to tell the tale The audio quality is punchy and bright enough for what you d expect at this scale and price range Although there s no app support or connectivity with the rest of the UE speaker lineup you can easily pair it with a second Wonderboom for stereo sound There s also an outdoor mode button on the bottom that boosts the mid and high range to help the audio carry over a greater distance Follow EngadgetDeals on Twitter and subscribe to the Engadget Deals newsletter for the latest tech deals and buying advice 2022-11-15 09:25:18
金融 RSS FILE - 日本証券業協会 外国株式信用取引の取扱状況 https://www.jsda.or.jp/shiryoshitsu/toukei/foreign-shinyo/index.html 信用取引 2022-11-15 10:00:00
ニュース BBC News - Home Record wage rises still outpaced by soaring inflation https://www.bbc.co.uk/news/business-63624996?at_medium=RSS&at_campaign=KARANGA inflationwages 2022-11-15 09:06:11
ニュース BBC News - Home Autumn Statement: When is it and how will it affect me? https://www.bbc.co.uk/news/business-63555313?at_medium=RSS&at_campaign=KARANGA unveil 2022-11-15 09:28:57
ニュース BBC News - Home Faf du Plessis was 'jealous' of AB de Villiers & labels David Warner a 'bully' https://www.bbc.co.uk/sport/cricket/63571811?at_medium=RSS&at_campaign=KARANGA Faf du Plessis was x jealous x of AB de Villiers amp labels David Warner a x bully x Former South Africa captain Faf du Plessis says he was jealous of AB de Villiers and labels David Warner a bully in his new book 2022-11-15 09:09:16
京都 烏丸経済新聞 京都の大学生が杉本住宅の掃除を体験 産学連携で掃除グッズ開発へ http://karasuma.keizai.biz/headline/3685/ 京都女子大学 2022-11-15 18:38:56
ニュース Newsweek 比マルコス政権、発足4カ月で46人を殺害 麻薬捜査現場で続く「超法規的殺人」 https://www.newsweekjapan.jp/stories/world/2022/11/446.php ドゥテルテ前大統領時代の犠牲者「今後も麻薬捜査では警察官や麻薬捜査当局捜査官による現場での実力行使を最小限とするという方針に変更はない」とも述べたアズリン長官は「超法規的殺人」を暗黙に容認していたとされるドゥテルテ前大統領の時代にその犠牲となった容疑者の数について人であるとの数字を示した。 2022-11-15 18:21:41
ニュース Newsweek ロシア兵が動物を略奪する映像に驚愕、木に吊るされた死骸も https://www.newsweekjapan.jp/stories/world/2022/11/post-100117.php その撤退ついでに、ロシア軍の兵士たちが動物園から動物を盗んでいく様子を撮影した動画が、インターネット上で大きな注目を集めている。 2022-11-15 18:16:06
IT 週刊アスキー ミストトレインガールズ~霧の世界の車窓から~、「月に寄りそう乙女の作法」とのコラボイベント開催! トレジャーイベントなどを実施 https://weekly.ascii.jp/elem/000/004/113/4113178/ exnoa 2022-11-15 18:40:00
IT 週刊アスキー 「石臼粗挽き蕎麦 28」が、ごろっと野菜の彩りと食感が楽しめる「8種の具材と自家製肉入り和風カレーつけそば」を発売 https://weekly.ascii.jp/elem/000/004/113/4113179/ 野菜 2022-11-15 18:40:00

コメント

このブログの人気の投稿

投稿時間:2021-06-17 05:05:34 RSSフィード2021-06-17 05:00 分まとめ(1274件)

投稿時間:2021-06-20 02:06:12 RSSフィード2021-06-20 02:00 分まとめ(3871件)

投稿時間:2020-12-01 09:41:49 RSSフィード2020-12-01 09:00 分まとめ(69件)