投稿時間:2022-01-05 23:23:16 RSSフィード2022-01-05 23:00 分まとめ(32件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
AWS	AWS DevOps Blog	Monitor AWS resources created by Terraform in Amazon DevOps Guru using tfdevops	https://aws.amazon.com/blogs/devops/monitor-aws-resources-created-by-terraform-in-amazon-devops-guru-using-tfdevops/	Monitor AWS resources created by Terraform in Amazon DevOps Guru using tfdevopsThis post was written in collaboration nbsp with Kapil Thangavelu CTO at Stacklet Amazon DevOps Guru is a machine learning ML powered service that helps developers and operators automatically detect anomalies and improve application availability DevOps Guru utilizes machine learning models informed by years of Amazon com and AWS operational excellence to identify anomalous application behavior e g increased …	2022-01-05 13:06:35
python	Pythonタグが付けられた新着投稿 - Qiita	「ディープラーニングの数学」９章補足　決定境界の標示	https://qiita.com/makaishi2/items/c8f6c2191529f9e1102c	書籍のリンクはこちら読者から章の多値分類モデルに関して、決定境界表示はできないのかとの質問があり、試しに実装した結果を公開します。	2022-01-05 22:17:02
python	Pythonタグが付けられた新着投稿 - Qiita	Azure Functionsを用いたサーバーレスなTwitter botを開発してみた（その３、ローカル開発環境でツィートする）	https://qiita.com/ataraken/items/2a1acf4c814b6fba51e0	しかし、実行ログを見ると冒頭venv環境でrequirementstxtのライブラリをインストールしているように見えますが、あれはいったい何なのでしょうか開設できる方がいらっしゃいましたらぜひともご教授ください。	2022-01-05 22:13:44
python	Pythonタグが付けられた新着投稿 - Qiita	モーションセンサの可視化に使えるリアルタイムチャートをDjango ChannelsとWebGL-Plotでつくってみた	https://qiita.com/yakiimo121/items/e7b984c9aed2e81bca30	WebGLPlotを用いることで、Epochjsを用いた可視化システムの課題であったリフレッシュレートを改善しました。	2022-01-05 22:13:24
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	cordovaで位置情報を取得したい	https://teratail.com/questions/376792?rss=all	よろしく おねがい し ます 。	2022-01-05 22:49:51
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	静的ライブラリをリリースビルドとデバッグビルドで共用したい。	https://teratail.com/questions/376791?rss=all	一般的に配布されている静的ライブラリはリリースビルドとデバッグビルドで共通のものが使用されていると思っています。	2022-01-05 22:36:50
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	Pythonで画像を読み込むことができない	https://teratail.com/questions/376790?rss=all	教えていただけると幸いです。	2022-01-05 22:27:13
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	unity　で使用しているc#の「 ; expected」「 } expected」エラーコード	https://teratail.com/questions/376789?rss=all	unityで使用しているcの「expected」「expected」エラーコード前提・実現したいこと私はunityでcを使用してプログラムを書いています。	2022-01-05 22:27:09
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	numpy.core._exceptions._UFuncNoLoopErrorを解決したい	https://teratail.com/questions/376788?rss=all	numpycoreexceptionsUFuncNoLoopErrorを解決したい前提・実現したいこと下記のようなエラーを直し、チェックボックスで受け取った値によって、表示されるヒストグラムの内容を変え、好きなデータ毎に比較できるようにしたいです。	2022-01-05 22:22:47
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	ジャンプ中に移動ボタンを離しても着地後移動し続けてしまう	https://teratail.com/questions/376787?rss=all	ジャンプ中に移動ボタンを離しても着地後移動し続けてしまう前提・実現したいこと昨日の今日ですみません。	2022-01-05 22:11:28
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	pythonで素数を１００まで出す　コードを作ってたのですが何回も同じ数時が出て困ってます	https://teratail.com/questions/376786?rss=all	angel	2022-01-05 22:08:01
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	Macのターミナル初期化について、python3系導入失敗？	https://teratail.com/questions/376785?rss=all		2022-01-05 22:06:27
Docker	dockerタグが付けられた新着投稿 - Qiita	Multipass と cloud-init で Docker Desktop の代用	https://qiita.com/silverskyvicto/items/ac1c297ed6158cc43604	そんな中で、Multipassとcloudinitを使用してDockerDesktopの代わりにしている記事がCanonical社のブログにあったので試した記事となります。	2022-01-05 22:28:00
海外TECH	DEV Community	Creating a Project with Nest.js + Next.js	https://dev.to/yakovlev_alexey/creating-a-project-with-nestjs-nextjs-3i1i	Creating a Project with Nest js Next jsThis is the first part in a series of articles about combining nest js and NEXT js Today you will learn how to setup a project and choose a valid SSR strategy In the second part that is coming soon you will learn about Hot Module Replacement more SSR techniques and subdirectory deployments This post is a translation of the original articles by me on Habr The translation had no input from experienced tech writers or editors So any feedback towards correcting any mistakes is greatly appreciated Table of Contents Table of Contents Introduction Before we start Creating a nest js application NEXT js installation SSR data preparation Using nest js controller Using direct services access By sending requests to itself Wrapper for fetch Passing path parameters Next steps IntroductionWhen choosing a framework for web development in you might be considering NEXT js It is a React based framework that supports SSR SSG Typescript great codesplitting and opinionated routing out of the box It s truly a great choice for solo developers and teams alike NEXT js also offers some backend functionality with serverless functions However serverless may not be the way for you and you would like to use something you are more used to nest js is a great choice here it follows MVC architecture familiar to many which makes it very scalable and extendable NEXT js and nest js are very similar in naming so I will be always typing NEXT js the React framework in uppercase and nest js the MVC backend framework in lowercase to differenciate between them more easily But how do you integrate these two How do you make them work together The simplest option would be to create a sophisticated or not so sophisticated proxy that would forward API requests to nest js and all others to NEXT js But this might not be an option for you if you are limited by the amount of microservices you can use or you might not want a real monorepo in order to share code between services Luckily there is an easy option for you to embed Next js right in your nest js server Meet nest next a view renderer for nest js which uses NEXT js to render pages right from a controller with a single decorator However this leads to a few caveats in the inner workings of your application Let s create a simple nest next application together from the ground up so that we can discover these caveats and I can tell you about some of the best practices I and my colleagues discovered using this technology Throughout the article I will try to delve as little as possible into each of the frameworks and will primarily focus on the bridge between the two When certain knowledge about a framework is needed I will leave links to official documentation Before we startIt s highly likely that you or your team opted for NEXT js before choosing a backend Here I recommend you to stop temporarily and seriously consider NEXT js server features you might not need a real backend for many use cases like a simple backend of the frontend render server Using two frameworks and maintaining a bridge between them would be an overhead You should only consider using nest next if you are either planning a real node js backend or you already have certain Express fastify nest js infrastructure you plan to employ The article is fairly large since it covers most of the quirky details about the frameworks and it has been split into two parts In the first one we will create a simple application from the ground up and show solutions the very basic problems you might have with SSR If you consider yourself an experienced developer in this stack it might be more interesting for you to start on the second part which is coming soon where I talk about some of the more advanced use cases like Hot Module Replacement SSR techniques and deployment in a subdirectory And finally for those who prefer skipping the article and getting right into code you can find the source code for this article on my GitHub commit history mostly follows the article Creating a nest js applicationFirst we would need a nest js application as our base We will use nest js CLI to generate a template npx nestjs cli new nest next exampleFollow the instructions I had chosen yarn as my package manager and will leave command snippets for yarn in the article but I assume you are familiar with package managers will be fine using npm in this article Upon command completion we will get a mostly empty project which may start instantly I will remove all the test files test directory and app controller spec ts from the project since we are not going to create any tests in this article I also recommend using the following directory structure that resembles a monorepo└ーsrc ├ーclient client code hooks components etc ├ーpages actual NEXT js pages ├ーserver nest js server code └ーshared common types utils constants etcLet s make the necessary changes to the nest js configuration to support our new layout nest cli json collection nestjs schematics sourceRoot src entryFile server main Now if we start the application using yarn start dev we should see Hello world when visiting localhost in the browser Due to certain caveats in nest js building pipelines you might see an error in your terminal The error might looks something like this Error Cannot find module dist server main In that case you may temporarily set entryFile to just main that should solve the issue NEXT js installationNow let s add NEXT js to our project NEXT js and its peersyarn add next react react dom required types and eslint presetyarn add D types react types react dom eslint config nextNext you should start NEXT js development server using yarn next dev Necessary changes to your tsconfig will be made as well as a few new files added including next env d ts NEXT js will boot successfully However if we now start nest js server we will discover that NEXT js broke our typescript config Let s create a separate config for nest js I will be reusing existing tsconfig build json as tsconfig server json with the following contents tsconfig server json extends tsconfig json compilerOptions noEmit false include src server ts src shared ts types d ts Now nest js works again Let s update scripts section in our package json file package json scripts prebuild rimraf dist build yarn build next amp amp yarn build nest build next next build build nest nest build path tsconfig server json start node dist server main js start next next dev start dev nest start path tsconfig server json watch start debug nest start path tsconfig server json debug watch start prod node dist main lint format test etc Let s add an index page and an App component to src pages directory src pages app tsximport FC from react import AppProps from next app const App FC lt AppProps gt Component pageProps gt return lt Component pageProps gt export default App src pages index tsximport FC from react const Home FC gt return lt h gt Home lt h gt export default Home Now when you start the app using yarn start next you should the this page on localhost You should also add next folder to your gitignore that is where NEXT js stores its builds Making acquaintance between the frameworksNow we have two separate servers But what we want is a single nest js server making use of nest next so let s install it yarn add nest nextNext we should initialize the newly installed RenderModule in app module ts src server app module tsimport Module from nestjs common import RenderModule from nest next import Next from next import AppController from app controller import AppService from app service Module should pass a NEXT js server instance as the argument to forRootAsync imports RenderModule forRootAsync Next controllers AppController providers AppService export class AppModule Now we can make use of Render decorator exported from nest So let s create our first page controller in app controller ts src server app controller tsimport Controller Get Render from nestjs common import AppService from app service Controller export class AppController constructor private readonly appService AppService Get Render index home return However when we start the app using yarn start dev and open the desired page in web browser we will see an error in NEXT js the build was not found Turns out the render server was booted in production mode and expected to see a ready made build of the frontend application To fix this we should provide dev true argument when initialising server instance src server app module tsimports RenderModule forRootAsync Next dev true Let s try again Open localhost in your browser and you will see a Which is unexpected since we have both a controller and a NEXT js page Turns out nest next is looking in a wrong folder By default it uses views subdirectory in pages folder rather than the folder itself I personally do not like this inconsistency with NEXT js so let s specify viewsDir null in our RenderModule instance src server app module tsimports RenderModule forRootAsync Next dev true null means that nest next should look for pages in root dir viewsDir null Adjacent to viewsDir is another dev option this time for nest next which enables more specific error serialization I did not find this option useful but it is there for you if you need it Finally when we open localhost in the browser we see the page we described earlier in index tsx SSR data preparationOne of the primary NEXT js advantages is the ability to easily fetch data required to statically or dynamically render a page Users have a few options to do so We will use getServerSideProps GSSP the most up to date way of fetching dynamic data in NEXT js However nest next properly supports other methods as well Time to add another page Let s imagine that our index is a blog page And the page we would be creating is a blog post by id Add the necessary types and controllers src shared types blog post tsexport type BlogPost title string id number src server app controller tsimport Controller Get Param Render from nestjs common Get id Render id public blogPost Param id id string return Add the new page src pages id tsximport GetServerSideProps from next import Link from next link import FC from react import BlogPost from src shared types blog post type TBlogProps post BlogPost const Blog FC lt TBlogProps gt post gt return lt div gt lt Link href gt Home lt Link gt lt h gt Blog post title lt h gt lt div gt export const getServerSideProps GetServerSideProps lt TBlogProps gt async ctx gt return props export default Blog And refresh our Home page src pages index tsximport GetServerSideProps from next import Link from next link import FC from react import BlogPost from src shared types blog post type THomeProps blogPosts BlogPost const Home FC lt THomeProps gt blogPosts gt return lt div gt lt h gt Home lt h gt blogPosts map title id gt lt div key id gt lt Link href id gt title lt Link gt lt div gt lt div gt export const getServerSideProps GetServerSideProps lt THomeProps gt async ctx gt return props export default Home Great Now we have a few pages that need some data The only thing left is to supply this data Let s explore the different ways we can do that Using nest js controllerOur home controller in app controller ts return an empty object It turns out that everything that happens to be in that object will be accessible in ctx query in GSSP Let s add some stub data in app service ts src server app service tsimport Injectable from nestjs common import from from rxjs const BLOG POSTS title Lorem Ipsum id title Dolore Sit id title Ame id Injectable export class AppService getBlogPosts return from BLOG POSTS In controller we may access this service and return the data src server app controller tsimport map toArray from rxjs Get Render index home return this appService getBlogPosts pipe toArray map blogPosts gt blogPosts Now we will have access to blogPosts property in ctx query in GSSP However it seems that this implementation is not very reliable TypeScript should warn us that there is in fact no blogPosts in ctx query It is typed to be ParsedUrlQuery Surely TypeScript is wrong Let s leave a few console logs of ctx query in our index tsx GSSP Then open localhost Check our terminal that s where the logs would land GSSP is only run on the server We indeed see that blogPosts are there What s wrong then Let s open localhost and then click the Home link Suddenly our terminal logs an empty object But how is that possible we clearly return blogPosts property from our controller When navigating on the client side NEXT js fetches an internal endpoint that executes just the GSSP function and returns serialized JSON from it So our home controller is not called at all and ctx query is populated purely with path params and search query Using direct services accessAs stated previously GSSP is only executed on the server Therefore we could technically use nest js services directly from inside GSSP This is in fact a very bad idea You either have to construct every service yourself then you have lots of repeated code and loose any profits from DI or expose nest js application with it s get method Still even if you were to bare with the spaghetti facilitated by global application access from different contexts you would end up missing the HTTP contexts when calling services By sending requests to itselfNothing really stops us from making asynchronous request using fetch from GSSP However we should make a wrapper around fetch to choose which address to call But before we proceed we have to get information about where the code is executed and what port the server is subscribed to src shared constants env tsexport const isServer typeof window undefined export const isClient isServer export const NODE ENV process env NODE ENV export const PORT process env PORT Now update port subscription in main ts await app listen PORT and choose NEXT js mode depending on environment src server app module tsRenderModule forRootAsync Next dev NODE ENV development viewsDir null package json start dev NODE ENV development nest start path tsconfig server json watch Now that server imports modules from src shared the structure of compiled nest js server differs from before If you previously changed entryFile in nest cli json return it to the old value server main ts clean dist folder and reboot the server Wrapper for fetchNow we can add a wrapper for fetch to choose hostname depending on execution environment src shared utils fetch tsimport isServer PORT from constants env const envAwareFetch url string options Record lt string unknown gt gt const fetchUrl isServer amp amp url startsWith http localhost PORT url url return fetch fetchUrl options then res gt res json export envAwareFetch as fetch And update app service ts src server app service tsimport Injectable NotFoundException from nestjs common import from of toArray from rxjs const BLOG POSTS title Lorem Ipsum id title Dolore Sit id title Ame id Injectable export class AppService getBlogPosts return from BLOG POSTS pipe toArray getBlogPost postId number const blogPost BLOG POSTS find id gt id postId if blogPost throw new NotFoundException return of blogPost Add new API endpoints to app controller ts src server app controller tsimport Controller Get Param ParseIntPipe Render from nestjs common import AppService from app service Controller export class AppController constructor private readonly appService AppService Get Render index home return Get id Render id public blogPost Param id id string return Get api blog posts public listBlogPosts return this appService getBlogPosts Get api blog posts id public getBlogPostById Param id new ParseIntPipe id number return this appService getBlogPost id Finally let s update GSSP methods src pages index tsximport fetch from src shared utils fetch export const getServerSideProps GetServerSideProps lt THomeProps gt async gt const blogPosts await fetch api blog posts return props blogPosts src pages id tsximport fetch from src shared utils fetch export const getServerSideProps GetServerSideProps lt TBlogProps gt async gt const id ctx query id const post await fetch api blog posts id return props post Visit localhost Indeed the blog list is available Let s visit one of the links to a post everything should work here as well client side navigation is fine However when we update the page on a post page we get an error there is no such blog post Everything seemed to work with client side navigation As we already discovered nest next puts controller return value to ctx query This means that the actual query is not there and it the responsibility of the user to prepare it To fix this issue we will return the id from blogPost controller src server app controller ts Get id Render id public blogPost Param id id string return id API endpoint casted the parameter to an integer In this case it s better to not parse parameters to stay consistent with NEXT js and keep them as strings Now let s refresh the page in the browser this should have solved our issue Passing path parametersObviously we are at a terrible situation when we need to manually pass all the parameters in controllers What if we need to use search parameters Surely there is a way to fix that We will use a snippet of AOP Aspect oriented programming and one of its mechanisms in nest js an Interceptor src server params interceptor tsimport Injectable NestInterceptor ExecutionContext CallHandler from nestjs common import Request from express import Observable from rxjs import map from rxjs operators Injectable export class ParamsInterceptor implements NestInterceptor intercept context ExecutionContext next CallHandler Observable lt unknown gt const request context switchToHttp getRequest as Request after executing the handler add missing request query and params return next handle pipe map data gt return request query request params data According to NEXT js documentation path parameters take priority over search params We also will not override the data from our handler Decorate page controller handlers with new interceptor src server app controller tsimport UseInterceptors from nestjs common import ParamsInterceptor from params interceptor Get Render index UseInterceptors ParamsInterceptor public home return Get id Render id UseInterceptors ParamsInterceptor public blogPost return It is important that path parameters have the same names in nest js and NEXT js In other words path params in Get and in Render should be the same API endpoints must not have this interceptor we do not want to return path params back when calling API It would be wise to separate API and page controllers Then we would be able to put UseInterceptors decorator on the entire controller class In this article for simplicity purposes API and page controllers are merged Let s validate our changes in the browser by refreshing the page We should still properly see a blog post by id Next stepsAt this point we have a basic nest next application capable of rendering pages and supplying them with data However we are yet to capitalise on some of the real advantages of such a setup There are also some other quirks you might encounter especially using this combo for enterprise development Stay tuned to the second part where you will learn about HMR more caveats with SSR and subdirectory deployments At this moment I hope this article helped you to finally try out those frameworks together with great efficiency despite the scarce info on actual nest next usage in docs	2022-01-05 13:38:22
海外TECH	DEV Community	React Fragments: What and Why	https://dev.to/saranshk/react-fragments-what-and-why-30h4	React Fragments What and WhyReact fragments were a feature released in React They have been around for a while now but have been a relatively lesser used feature Let us explore the what and why the feature exists What are React Fragments React fragments are a syntax addition to React that allow wrapping or grouping of multiple HTML elements without the need for any additional DOM nodes We mostly come across this situation when a React component needs to return multiple elements The traditional approach has been to wrap them in a div element because a React component can return only one element This behavior results in useless additional markup and also makes the DOM tree heavy with additional layers of divs The traditional solution to render child components in a single component would have been const App gt return lt div gt lt ChildA gt lt ChildB gt lt ChildC gt lt div gt With fragments this can be const App gt return lt React Fragment gt lt ChildA gt lt ChildB gt lt ChildC gt lt React Fragment gt Note React Fragment can also be replaced by empty tags as lt gt lt gt const App gt return lt gt lt ChildA gt lt ChildB gt lt ChildC gt lt gt Why React fragments There are typical use cases for fragments Returning groups of elementsThis one is the typical use case for fragments As discussed above using fragments avoids additional div containers that can make the DOM heavy and also often cause problems when styling things Conditional renderingFragments make it easier to conditionally render groups of elements without any extra markup const Login isLoggedIn name gt isLoggedIn lt gt lt h gt Welcome name lt h gt lt p gt You are logged in lt p gt lt gt lt gt lt h gt Login lt h gt lt input type text id username gt lt input type password id password gt lt input type submit value Login gt lt gt Rendering arrays with keyed fragmentsFragments can have key props This is yet another powerful feature which can be pretty handy at times This cannot be used with the empty tags though This can be helpful when rendering lists such as const Glossary items gt return lt gt items map item gt Without the key React will fire a key warning lt React Fragment key item id gt lt dt gt item term lt dt gt lt dd gt item description lt dd gt lt React Fragment gt lt gt AdvantagesReact fragments are a bit faster and have little lesser memory consumption lesser DOM nodes This is helpful in applications with deep tree structures Styling can be easier at times since there is no additional div created Sometimes some libraries depend on parent child relationships and the div in the middle causes layout issues The DOM is easier to inspect because of less clutter And that is all there is to know about React fragments Originally published at on July	2022-01-05 13:00:48
海外TECH	Engadget	Apple's 24-inch iMac M1 is cheaper than ever on Amazon right now	https://www.engadget.com/apples-24-inch-imac-m1-is-cheaper-than-ever-on-amazon-right-now-135540267.html?src=rss	Apple x s inch iMac M is cheaper than ever on Amazon right nowThose looking to add a speedy desktop to their household or upgrade from an old machine should consider Apple s latest iMac The sleek machine earned a score of from us thanks in part to its fast performance and updated design and now you can pick up the silver model for less at Amazon The inch iMac M with an core CPU and a core GPU along with GB of RAM and GB of storage is down to or off its normal price Only the silver model is this low right now and the last time it saw a similar discount was back in July of last year Buy inch iMac M at Amazon Apple s M chipset powers the latest iMacs delivering noticeable performance improvements over previous models The desktop can handle video editing spreadsheet work and even Apple Arcade gaming without breaking a sweat and wakes almost instantaneously from sleeping and only takes around seconds to boot in a cold start It also has a stunning K Retina Display that can show over one billion colors and reach up to nits of brightness so everything from photos to videos pops on this screen Plus the under pound iMac is pretty easy to move around so while you may just want to park it in one room of your home you can move it when necessary without much effort Our biggest gripes with the iMac are its lack of vertical screen adjustment and its USB C only port array The base model which is the one on sale only has two USB C ports ーand you ll have to spring for the core GPU version in order to get two more That means that you ll most certainly be living the dongle life if you invest in this laptop and that s an inconvenience that might be too much for some You do get the color matching Magic Mouse and Magic Keyboard with this desktop though and while there are more comfortable combos out there they will work just fine for most people nbsp Follow EngadgetDeals on Twitter for the latest tech deals and buying advice	2022-01-05 13:55:40
海外TECH	Engadget	Walmart's InHome Delivery service will reach up to 30 million households in 2022	https://www.engadget.com/walmart-expanding-inhome-delivery-30-million-households-132840121.html?src=rss	Walmart x s InHome Delivery service will reach up to million households in Walmart has big plans for its InHome delivery service in aiming to expand it from million households to million by the end of the year To achieve that it will hire more than full time associate delivery drivers and build out a fleet of all electric delivery vans nbsp The InHome service which handles more than items from stores first launched in Since then it s been operating in select markets at a fee of per month or per year a bit more than the you pay for Amazon Prime membership However Walmart notes that tips for associates are built into the fee nbsp Once signed up you can order items from the Walmart app and select InHome as the preferred delivery method Drivers can unlock the customer s door using a one time access code with a vest worn camera recording the entire delivery You can use your own smart lock or purchase one from InHome for nbsp Walmart said that the new associate delivery driver position is full time and includes benefits like medical vision and dental insurance K matching paid time off and free college degrees Drivers also get paid a hour premium compared to other store workers nbsp The company plans to equip those workers with a fleet of all electric vans It has yet to specify exactly which delivery vehicles it will use though it has tested EV s used by GM s Cruise division and autonomous electric box trucks employed by a startup called Gatik Walmart said it will make InHome delivery service accessible to million households by the end of the year reaching around percent of the US population nbsp	2022-01-05 13:28:40
海外科学	NYT > Science	In Omicron Hot Spots, Hospitals Fill Up, but I.C.U.s May Not	https://www.nytimes.com/2022/01/04/health/covid-omicron-hospitalizations.html	In Omicron Hot Spots Hospitals Fill Up but I C U s May NotCovid hospitalizations are surging but a smaller proportion of cases is severe compared with previous waves With staff shortages some hospitals are still in crisis	2022-01-05 13:37:04
金融	RSS FILE - 日本証券業協会	ＳＤＧｓ特設サイトのトピックスと新着情報（リダイレクト）	https://www.jsda.or.jp/about/torikumi/sdgs/sdgstopics.html	特設サイト	2022-01-05 13:23:00
ニュース	BBC News - Home	Covid: PCR not needed after positive lateral flow under new plans	https://www.bbc.co.uk/news/uk-59878823?at_medium=RSS&at_campaign=KARANGA	agency	2022-01-05 13:55:28
ニュース	BBC News - Home	Covid: Greater Manchester hospitals cancel surgery as NHS pressures mount	https://www.bbc.co.uk/news/uk-england-manchester-59878179?at_medium=RSS&at_campaign=KARANGA	manchester	2022-01-05 13:12:22
ニュース	BBC News - Home	Covid: Travel firms call for removal of testing rules	https://www.bbc.co.uk/news/business-59876063?at_medium=RSS&at_campaign=KARANGA	impact	2022-01-05 13:27:12
ニュース	BBC News - Home	First leg of Arsenal v Liverpool semi-final postponed amid Anfield Covid outbreak	https://www.bbc.co.uk/sport/football/59883780?at_medium=RSS&at_campaign=KARANGA	First leg of Arsenal v Liverpool semi final postponed amid Anfield Covid outbreakLiverpool s Carabao Cup semi final first leg at Arsenal on Thursday is postponed because of a severe outbreak of Covid at the Anfield club	2022-01-05 13:34:51
ニュース	BBC News - Home	What are the Covid self-isolation rules now?	https://www.bbc.co.uk/news/explainers-54239922?at_medium=RSS&at_campaign=KARANGA	ireland	2022-01-05 13:53:04
ニュース	BBC News - Home	Omicron: How do I get a lateral flow or PCR Covid test?	https://www.bbc.co.uk/news/health-51943612?at_medium=RSS&at_campaign=KARANGA	covid	2022-01-05 13:49:54
LifeHuck	ライフハッカー［日本版］	精密構造の両刃でスッキリ深剃り。高コスパを誇るシェーバー「HENSON」が登場	https://www.lifehacker.jp/2022/01/248907-machi-ya-henson-start.html	henson	2022-01-05 23:00:00
LifeHuck	ライフハッカー［日本版］	早くも話題！ 柴犬デザインがかわいいバッグホルダー「bow hook shiba」	https://www.lifehacker.jp/2022/01/248058-machi-ya-bowhook-review1.html	bowhookshiba	2022-01-05 23:00:00
LifeHuck	ライフハッカー［日本版］	200万冊以上が読み放題｢Kindle Unlimited｣が2カ月99円に〜1/6まで	https://www.lifehacker.jp/2022/01/248910kindle-unlimited-2022-01.html	kindle	2022-01-05 22:35:00
LifeHuck	ライフハッカー［日本版］	「Apple Watch Series 7」に替えて得た副次的なメリット｜これ買ってよかった	https://www.lifehacker.jp/2022/01/248623best-buy-apple-watch-7.html	applewatchseries	2022-01-05 22:05:00
北海道	北海道新聞	羅臼、苫小牧大雪　道内広範囲で降雪ピークは越す	https://www.hokkaido-np.co.jp/article/630376/	太平洋側	2022-01-05 22:08:46
北海道	北海道新聞	Ｃ大阪の坂元達裕、ベルギーへ　オーステンデに期限付き移籍	https://www.hokkaido-np.co.jp/article/630377/	坂元達裕	2022-01-05 22:07:00
北海道	北海道新聞	中国、米軍は「ウイルス拡散者」　沖縄の感染拡大、会見で批判	https://www.hokkaido-np.co.jp/article/630375/	中国外務省	2022-01-05 22:03:00