text:
Sorted documentsby created_at and added date field to documents page

Context
Documents should be sorted so most recent is first, and display the created datetime to the user
Changes proposed in this pull request

Added jinja2 filter for converting a datetime to localtime
Added column to documents page to show created datetime

Guidance to review
Add some documents and check the datetime shown on the documents page
Relevant links
Things to check

[ ] I have added any new ENV vars in all deployed environments
[ ] I have tested any code added or changed
[ ] I have run integration tests

Closing until Kevin can work with me on fixing the table layout on mobile

Just to confirm the table layout on mobile is now fixed :-)

Probably worth merging main in again and running make format lint.

authors: 252afh KevinEtchells brunns

repo: i-dot-ai/redbox-copilot


text:
报错报哭了

报错报哭了

@Calvinwong1991 什么错误？

source: gharchive/issue

repo: iHaPBoy/vue-zhihudaily

license: mit

license_type: permissive

license_source: bigquery


text:
dj-rest-auth registration e-mail issues

I am having an issue with user registration, and am not able to send registration e-mails successfully. I suspect I'm just not doing something pretty basic that django needs to send e-mails. If this is the case, then this issue request is actually a documentation request, as there are additional settings that need to be added other than the instructions in the "Installation" section to get user registration working.
I am able to get account registration to work on the database side - when I submit a POST request to the registration endpoint with the correct data, I can register a user and view them in the django admin console, but I am getting a server error when a websocket attempts to open, which looks like it has to do with my e-mail account.
Internal Server Error: /api/dj-rest-auth/registration/
Traceback (most recent call last):
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 472, in thread_handler
    raise exc_info[1]
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/handlers/exception.py", line 42, in inner
    response = await get_response(request)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/handlers/base.py", line 253, in _get_response_async
    response = await wrapped_callback(
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 435, in __call__
    ret = await asyncio.wait_for(future, timeout=None)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 408, in wait_for
    return await fut
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 476, in thread_handler
    return func(*args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
    return view_func(*args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 103, in view
    return self.dispatch(request, *args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/utils/decorators.py", line 46, in _wrapper
    return bound_method(*args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/decorators/debug.py", line 92, in sensitive_post_parameters_wrapper
    return view(request, *args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/dj_rest_auth/registration/views.py", line 47, in dispatch
    return super().dispatch(*args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/rest_framework/views.py", line 509, in dispatch
    response = self.handle_exception(exc)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/rest_framework/views.py", line 469, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/rest_framework/views.py", line 480, in raise_uncaught_exception
    raise exc
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/rest_framework/generics.py", line 190, in post
    return self.create(request, *args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/dj_rest_auth/registration/views.py", line 69, in create
    user = self.perform_create(serializer)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/dj_rest_auth/registration/views.py", line 95, in perform_create
    complete_signup(
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/allauth/account/utils.py", line 186, in complete_signup
    return perform_login(
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/allauth/account/utils.py", line 168, in perform_login
    response = adapter.pre_login(request, user, **hook_kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/allauth/account/adapter.py", line 409, in pre_login
    send_email_confirmation(request, user, signup=signup, email=email)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/allauth/account/utils.py", line 319, in send_email_confirmation
    email_address.send_confirmation(request, signup=signup)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/allauth/account/models.py", line 59, in send_confirmation
    confirmation.send(request, signup=signup)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/allauth/account/models.py", line 166, in send
    get_adapter(request).send_confirmation_mail(request, self, signup)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/allauth/account/adapter.py", line 549, in send_confirmation_mail
    self.send_mail(email_template, emailconfirmation.email_address.email, ctx)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/allauth/account/adapter.py", line 140, in send_mail
    msg.send()
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/mail/message.py", line 298, in send
    return self.get_connection(fail_silently).send_messages([self])
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/mail/backends/smtp.py", line 124, in send_messages
    new_conn_created = self.open()
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/mail/backends/smtp.py", line 80, in open
    self.connection = self.connection_class(
  File "/usr/lib/python3.10/smtplib.py", line 255, in __init__
    (code, msg) = self.connect(host, port)
  File "/usr/lib/python3.10/smtplib.py", line 341, in connect
    self.sock = self._get_socket(host, port, self.timeout)
  File "/usr/lib/python3.10/smtplib.py", line 312, in _get_socket
    return socket.create_connection((host, port), timeout,
  File "/usr/lib/python3.10/socket.py", line 845, in create_connection
    raise err
  File "/usr/lib/python3.10/socket.py", line 833, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
HTTP POST /api/dj-rest-auth/registration/ 500 [0.28, 127.0.0.1:49584]

To fix this, I added the following to my settings.py:
from decouple import config

EMAIL_HOST = config('EMAIL_HOST')
EMAIL_HOST_USER = config('EMAIL_HOST_USERNAME')
EMAIL_HOST_PASSWORD = config('EMAIL_HOST_PASSWORD')

Where I am using environment variables for my username/password, and the host is smtp.gmail.com (it's my personal gmail account). Now, when I submit a request, I get the following error:
Application instance <Task pending name='Task-18' coro=<StaticFilesWrapper.__call__() running at /home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/channels/staticfiles.py:44> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.10/asyncio/futures.py:384, Task.task_wakeup()]>> for connection <WebRequest at 0x7fe783f47df0 method=POST uri=/api/dj-rest-auth/registration/ clientproto=HTTP/1.0> took too long to shut down and was killed.

... and I'm stuck. Sounds like it's an authentication problem? But the error message isn't giving me much.

Adding the following lines to my settings.py appears to have "resolved" the issue:
EMAIL_PORT = 587
EMAIL_USE_TLS = True
DEFAULT_FROM_EMAIL = config('EMAIL_HOST_USERNAME')
SERVER_EMAIL = config('EMAIL_HOST_USERNAME')

I am still getting an error, but now it looks like it's a Gmail security error, as it doesn't look like they support username/password login via 3rd-party apps:
Internal Server Error: /api/account/send-email/
Traceback (most recent call last):
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 472, in thread_handler
    raise exc_info[1]
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/handlers/exception.py", line 42, in inner
    response = await get_response(request)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/handlers/base.py", line 253, in _get_response_async
    response = await wrapped_callback(
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 435, in __call__
    ret = await asyncio.wait_for(future, timeout=None)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 408, in wait_for
    return await fut
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 476, in thread_handler
    return func(*args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
    return view_func(*args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 103, in view
    return self.dispatch(request, *args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/rest_framework/views.py", line 509, in dispatch
    response = self.handle_exception(exc)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/rest_framework/views.py", line 469, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/rest_framework/views.py", line 480, in raise_uncaught_exception
    raise exc
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
  File "/home/jordan/axle_backend/users/views.py", line 132, in get
    send_mail('Subject',
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/mail/__init__.py", line 87, in send_mail
    return mail.send()
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/mail/message.py", line 298, in send
    return self.get_connection(fail_silently).send_messages([self])
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/mail/backends/smtp.py", line 124, in send_messages
    new_conn_created = self.open()
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/mail/backends/smtp.py", line 91, in open
    self.connection.login(self.username, self.password)
  File "/usr/lib/python3.10/smtplib.py", line 750, in login
    raise last_exception
  File "/usr/lib/python3.10/smtplib.py", line 739, in login
    (code, resp) = self.auth(
  File "/usr/lib/python3.10/smtplib.py", line 662, in auth
    raise SMTPAuthenticationError(code, resp)
smtplib.SMTPAuthenticationError: (535, b'5.7.8 Username and Password not accepted. Learn more at\n5.7.8  https://support.google.com/mail/?p=BadCredentials b9-20020a05622a020900b0035d430d4315sm6140818qtx.19 - gsmtp')

As a follow-up: which setting can I change to specify the registration "FROM" email address? I have set EMAIL_HOST_USER but this is not the same thing as my "from" email address.

It was staring me right in the face! The setting is a django-specific one, and adding the following line to my settings.py got the email to send successfully (where I have used an environment variable to define the email)!
DEFAULT_FROM_EMAIL = config('DEFAULT_FROM_EMAIL')

The e-mail sends successfully (sort of - it doesn't actually hit my inbox although it's labeled as being in my inbox in gmail), However, now when I try to click the confirmation link in the e-mail that was sent, django throws an error. This stack trace I am not finding terribly helpful:
HTTP POST /api/dj-rest-auth/registration/ 201 [0.90, 127.0.0.1:56902]
Internal Server Error: /api/dj-rest-auth/registration/account-confirm-email/MTM:1oeyyU:SkZ8UogQYxkunS-IJrrnXyFmHpvN0Oezj3fAdx992xY/
Traceback (most recent call last):
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 472, in thread_handler
    raise exc_info[1]
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/handlers/exception.py", line 42, in inner
    response = await get_response(request)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/handlers/base.py", line 253, in _get_response_async
    response = await wrapped_callback(
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 435, in __call__
    ret = await asyncio.wait_for(future, timeout=None)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 408, in wait_for
    return await fut
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 476, in thread_handler
    return func(*args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 103, in view
    return self.dispatch(request, *args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 142, in dispatch
    return handler(request, *args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 217, in get
    return self.render_to_response(context)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 190, in render_to_response
    template=self.get_template_names(),
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 202, in get_template_names
    raise ImproperlyConfigured(
django.core.exceptions.ImproperlyConfigured: TemplateResponseMixin requires either a definition of 'template_name' or an implementation of 'get_template_names()'
HTTP GET /api/dj-rest-auth/registration/account-confirm-email/MTM:1oeyyU:SkZ8UogQYxkunS-IJrrnXyFmHpvN0Oezj3fAdx992xY/ 500 [0.07, 127.0.0.1:58742]

I found a hint in the API reference, and added the following lines to my urls.py:
from dj_rest_auth.registration.views import VerifyEmailView
...
path('api/dj-rest-auth/account-confirm-email/', VerifyEmailView.as_view(), name='account_email_verification_sent'),

However, I'm still getting the same error. It looks like the endpoint the link is trying to hit is /api/dj-rest-auth/registration/account-confirm-email/, which is not the endpoint specified in the API. However, even when I change the url pattern to hit the endpoint /api/dj-rest-auth/registration/account-confirm-email/, I get exactly the same stack trace. I'm stumped.
Internal Server Error: /api/dj-rest-auth/registration/account-confirm-email/MTM:1oeyyU:SkZ8UogQYxkunS-IJrrnXyFmHpvN0Oezj3fAdx992xY/
Traceback (most recent call last):
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 472, in thread_handler
    raise exc_info[1]
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/handlers/exception.py", line 42, in inner
    response = await get_response(request)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/core/handlers/base.py", line 253, in _get_response_async
    response = await wrapped_callback(
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 435, in __call__
    ret = await asyncio.wait_for(future, timeout=None)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 408, in wait_for
    return await fut
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/asgiref/sync.py", line 476, in thread_handler
    return func(*args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 103, in view
    return self.dispatch(request, *args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 142, in dispatch
    return handler(request, *args, **kwargs)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 217, in get
    return self.render_to_response(context)
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 190, in render_to_response
    template=self.get_template_names(),
  File "/home/jordan/.local/share/virtualenvs/axle_backend-CFXWssDC/lib/python3.10/site-packages/django/views/generic/base.py", line 202, in get_template_names
    raise ImproperlyConfigured(
django.core.exceptions.ImproperlyConfigured: TemplateResponseMixin requires either a definition of 'template_name' or an implementation of 'get_template_names()'
HTTP GET /api/dj-rest-auth/registration/account-confirm-email/MTM:1oeyyU:SkZ8UogQYxkunS-IJrrnXyFmHpvN0Oezj3fAdx992xY/ 500 [0.05, 127.0.0.1:52410]

repo: iMerica/dj-rest-auth

license: MIT

license_source: github-api


text:
Tweet Dates

Maybe I am doing something wrong, but the tweet dates seem to be all over the place for the guest tokens.
Is there a method to grab the latest tweets?
Thank you for your work.
from tweeterpy import TweeterPy
twitter = TweeterPy()
twitter.load_session("Twitter Saved Sessions/session.pkl")
tweets = twitter.get_user_tweets('AltCryptoGems')

for data in tweets['data']:
    print(data['content']['itemContent']['tweet_results']['result']['legacy']['created_at'])

API Updated Successfully.
Wed Nov 23 10:59:33 +0000 2022
Fri Oct 21 17:01:00 +0000 2022
Sun Oct 02 14:28:20 +0000 2022
Sun Apr 09 17:00:02 +0000 2023
Thu Aug 18 12:30:00 +0000 2022
Mon Aug 15 17:31:36 +0000 2022
Thu Sep 01 16:00:01 +0000 2022
Wed May 03 20:15:00 +0000 2023
Mon Jul 18 08:00:01 +0000 2022
Mon May 17 18:22:17 +0000 2021
Sun Jul 23 10:58:46 +0000 2023
Mon May 22 16:00:01 +0000 2023
Mon May 31 07:24:39 +0000 2021
Mon Apr 11 18:42:00 +0000 2022
Tue Feb 07 19:30:00 +0000 2023
Sun Aug 06 07:04:00 +0000 2023
Mon Jul 11 09:43:00 +0000 2022
Tue Sep 20 17:00:07 +0000 2022
Sat Feb 25 13:00:00 +0000 2023
Fri Nov 04 18:30:17 +0000 2022
Mon Nov 14 18:30:15 +0000 2022
Mon Oct 17 17:30:05 +0000 2022
Fri Oct 14 17:30:05 +0000 2022
Wed Mar 15 17:01:00 +0000 2023
Fri Nov 11 18:30:14 +0000 2022
Sun Mar 05 19:03:33 +0000 2023
Tue Jul 04 16:59:00 +0000 2023
Fri Nov 18 18:30:15 +0000 2022
Tue May 11 07:58:24 +0000 2021
Fri Sep 30 15:00:05 +0000 2022
Mon Oct 10 17:30:15 +0000 2022
Thu Sep 15 16:50:49 +0000 2022
Wed Jul 20 15:00:02 +0000 2022
Mon Nov 07 18:30:17 +0000 2022
Mon Oct 31 18:30:10 +0000 2022
Tue Nov 08 21:40:04 +0000 2022
Tue May 17 10:09:31 +0000 2022
Thu Oct 27 13:26:38 +0000 2022
Mon Sep 26 16:55:03 +0000 2022
Wed Jan 05 12:33:18 +0000 2022
Thu Jul 14 12:00:02 +0000 2022
Tue Jul 05 10:00:01 +0000 2022
Sun Jun 26 19:33:16 +0000 2022
Tue Apr 04 18:04:10 +0000 2023
Mon Jun 13 09:01:00 +0000 2022
Thu Jul 28 16:00:01 +0000 2022
Mon Jun 20 10:00:04 +0000 2022
Sat Aug 06 08:58:09 +0000 2022
Fri Dec 16 18:45:04 +0000 2022
Sat Jun 25 17:14:00 +0000 2022
Wed Oct 05 10:40:04 +0000 2022
Wed Sep 15 13:29:23 +0000 2021
Tue Aug 02 16:00:02 +0000 2022
Thu Sep 29 09:05:04 +0000 2022
Fri Dec 02 18:45:03 +0000 2022
Mon Feb 20 18:01:24 +0000 2023
Sun Oct 09 11:30:04 +0000 2022
Wed Sep 28 16:00:02 +0000 2022
Fri Oct 28 16:10:05 +0000 2022
Thu Jan 26 09:01:30 +0000 2023
Fri Aug 12 12:00:02 +0000 2022
Mon Feb 06 22:48:38 +0000 2023
Fri Jul 01 08:56:00 +0000 2022
Wed Oct 26 20:40:08 +0000 2022
Wed Oct 26 14:05:04 +0000 2022
Mon Apr 26 11:43:50 +0000 2021
Mon Jul 25 19:36:00 +0000 2022
Sun Oct 09 06:10:02 +0000 2022
Sat Oct 08 06:10:03 +0000 2022
Wed Oct 26 17:00:06 +0000 2022
Tue Sep 27 10:40:04 +0000 2022
Fri Jul 08 09:57:57 +0000 2022
Sat Nov 20 09:29:13 +0000 2021
Thu Jun 02 09:25:00 +0000 2022
Wed Oct 26 21:10:05 +0000 2022
Tue Jan 04 17:13:49 +0000 2022
Wed Jun 07 19:00:01 +0000 2023
Wed Sep 28 20:40:08 +0000 2022
Fri Sep 30 12:15:06 +0000 2022
Sun Oct 09 18:35:02 +0000 2022
Tue May 11 18:31:31 +0000 2021
Tue Aug 01 07:01:00 +0000 2023
Tue Dec 06 18:00:02 +0000 2022
Wed Oct 26 15:00:12 +0000 2022
Sat Oct 08 10:40:02 +0000 2022
Mon Jun 06 12:01:00 +0000 2022
Mon Aug 30 18:57:00 +0000 2021
Thu Dec 15 18:59:17 +0000 2022
Wed Sep 28 21:10:05 +0000 2022
Sun Jan 08 20:53:49 +0000 2023
Sat Nov 13 09:04:02 +0000 2021
Mon Oct 03 15:00:08 +0000 2022
Fri Dec 23 15:00:02 +0000 2022
Wed Oct 26 18:35:06 +0000 2022
Thu Jan 13 11:45:00 +0000 2022
Tue Nov 02 20:22:32 +0000 2021
Sat Dec 17 12:22:02 +0000 2022
Sun May 22 18:55:00 +0000 2022
Mon Dec 26 18:45:03 +0000 2022
Mon Aug 01 08:13:44 +0000 2022

Hey @Allen-Taylor
You are doing it all right. I just want to point out that twitter by default also shows "promoted" and "reposted" tweets. So the reason these dates are not in order is that the promoted or reposted tweets are included in this dataset and were posted back in the time. So you will have to filter them out.
Take a look at this.
You might also be interested in taking a look at the "entryId" which basically tells us the type of dataset/tweet whether it's promoted, tweet thread or reposted etc.

Thanks for the response.
The nested data is a pain but I can figure that out.
Do you know how to work the cursor then so I can grab all the tweets for a particular user then?

Thanks for the response.
The nested data is a pain but I can figure that out.
Do you know how to work the cursor then so I can grab all the tweets for a particular user then?

Check out these two issues #7 and #10 for the cursor endpoint usage.

Thanks Sarabjit. I saw you implemented an async/await version with the date args. I will try that and let you know.

Thanks Sarabjit. I saw you implemented an async/await version with the date args. I will try that and let you know.

Yes, async/await branch has some other extra features as well, you can also check the api rate limits, find values from the nested dictionaries etc.

So I just tried it, I'm trying to use a guest token, but it is asking me for username/password.
Any thoughts?
This is the async branch.
from tweeterpy import TweeterPy

twitter = TweeterPy()
twitter.generate_session()
user_tweets = twitter.get_user_tweets("elonmusk", from_date="1 August 2023")
for data in user_tweets['data']:
    print(data['content']['itemContent']['tweet_results']['result']['legacy']['created_at'])

Any chance I can contact you in private?

So I just tried it, I'm trying to use a guest token, but it is asking me for username/password.
Any thoughts?
This is the async branch.
from tweeterpy import TweeterPy

twitter = TweeterPy()
twitter.generate_session()
user_tweets = twitter.get_user_tweets("elonmusk", from_date="1 August 2023")
for data in user_tweets['data']:
    print(data['content']['itemContent']['tweet_results']['result']['legacy']['created_at'])

Oh yeah, I forgot to import the recent commits to the async-await branch, I will do that shortly.

Any chance I can contact you in private?

iSarabjitDhiman is my username on insta/twitter/fb etc.

Telegram?

Telegram?

Yes, same username for the Telegram.

authors: Allen-Taylor iSarabjitDhiman

repo: iSarabjitDhiman/TweeterPy


text:
Replace calls to deprecated query methods

Get rid of calls to deprecrated query, queryRowCount, and restartQuery methods and replace them with updated equivalents.
The linter was suppressed for lines that use these methods in this commit (#75fee93). That commit can be used to see where function calls need to be updated.

Related PR: #5240

repo: iTwin/itwinjs-core


text:
Looking for custom page for signin and signout

Looking for custom page for signin and signout @iaincollins

The example repo doesn't have that.
The documentation for NextAuth.js has an example of custom sign in pages though.
https://next-auth.js.org/configuration/pages

authors: iaincollins sivaraj-v

repo: iaincollins/next-auth-example

license: ISC


text:
DB Migration

I couldn't find a way to manage a production DB. The ?synchronize=true option is OK for development, but obviously it is risky in production settings.
Is there some way to generate migrations so that I can configure a production database before deploying my app?

Thank you for the great product @iaincollins. Had the same issue today, that were not able to find documented tables definition, so I ran synchronize=true at first and then converted it into migrations.
From the structure I see now there are no indexes/fk that have set during initialization of DB data. I'm looking on it there https://github.com/iaincollins/next-auth/blob/master/src/adapters/typeorm/models/account.js. Also should be a good thing to improve
Definitely upvote for changing the current approach from auto sync to migrations.
And for those who probably will need table structure:
verification_request table:
-- Sequence and defined type
CREATE SEQUENCE IF NOT EXISTS verification_request_id_seq;

-- Table Definition
CREATE TABLE "public"."verification_request" (
    "id" int4 NOT NULL DEFAULT nextval('verification_request_id_seq'::regclass),
    "identifer" text NOT NULL,
    "token" varchar NOT NULL,
    "expires" timestamp NOT NULL,
    "created" timestamp NOT NULL,
    PRIMARY KEY ("id")
);

account table:
-- Sequence and defined type
CREATE SEQUENCE IF NOT EXISTS account_id_seq;

-- Table Definition
CREATE TABLE "public"."account" (
    "id" int4 NOT NULL DEFAULT nextval('account_id_seq'::regclass),
    "compoundId" varchar NOT NULL,
    "userId" int4 NOT NULL,
    "providerId" varchar NOT NULL,
    "providerType" varchar NOT NULL,
    "providerAccountId" varchar NOT NULL,
    "refreshToken" text,
    "accessToken" text NOT NULL,
    "accessTokenExpires" timestamp,
    "created" timestamp NOT NULL,
    PRIMARY KEY ("id")
);

user table:
-- Sequence and defined type
CREATE SEQUENCE IF NOT EXISTS user_id_seq;

-- Table Definition
CREATE TABLE "public"."user" (
    "id" int4 NOT NULL DEFAULT nextval('user_id_seq'::regclass),
    "name" varchar,
    "email" varchar NOT NULL,
    "image" varchar,
    "created" timestamp NOT NULL,
    PRIMARY KEY ("id")
);

session talbe:
-- Sequence and defined type
CREATE SEQUENCE IF NOT EXISTS session_id_seq;

-- Table Definition
CREATE TABLE "public"."session" (
    "id" int4 NOT NULL DEFAULT nextval('session_id_seq'::regclass),
    "userId" int4 NOT NULL,
    "expires" timestamp NOT NULL,
    "sessionToken" varchar NOT NULL,
    "accessToken" varchar NOT NULL,
    "created" timestamp NOT NULL,
    PRIMARY KEY ("id")
);

From the structure I see now there are no indexes/fk that have set during initialization of DB data. I'm looking on it there https://github.com/iaincollins/next-auth/blob/master/src/adapters/typeorm/models/account.js. Also should be a good thing to improve

Thanks!
Please note the database schema is in flux and will be until release - in fact the schema has already changed slightly in master, and is likely change in a release that drops in the next few day. The changes are mostly fairly minor; with the exception that email addresses will become optional to support using oAuth providers that don't return them (but you can still choose to enforce providing them if you wish).
There are no change logs until we get to release, so folks using the beta will need to keep an eye on the documentation on each update and understand there will be breaking changes on a regular basis until it is final (there will be official documentation before release!).
To clarify there is no migration script currently, because there is nothing to update to or from as the beta is still pre-release software and breaking changes to the API should still be expected. I was hoping to postpone them till later, but it's less painful to delay the release a bit than to release a breaking update very soon after release.
RE: Indexes / relational mappings
By release, all fields that should have indexes on them should be there on supported databases, however I should add that relational mapping is not planned as the focus is on support for multiple very different backends rather than optimising database metadata for a specific backend.
How to extend and customise models and schemas will be part of the documentation that drops before release though. (This is currently possible, it's just not documented.)
At some point in future dedicated adapters that have more sophisticated support for specific databases might be developed.

Thank you @iaincollins for the reply. Is there any chance before the release that you can consider moving to a more common practice in naming sql tables/fields rather than use JS style.
Usually, for fields name the common practice to use lower_case_underscored names and for tables also lowercase but in plural form.

I think that's a very reasonable request but have been concerned about adding additional  complexity to the already monkey patched models.
However, it looks like it's possible to apply a naming strategy with TypeORM and we could do that conditionally (we could even use a pre-canned model.

Note: You can already use the namingStrategy option in TypeORM with NextAuth.js, but I don't know how well it will work in practice.
You can track this is #245.
If there are any other feature requests, please create them as a new issue.

Update for anyone following this issue - Request for Comment on DB schema changes at #254

authors: adarnon iaincollins lnikell

repo: iaincollins/next-auth


text:
Hide tooltipster when position changed

When screen is resized and there is no place for a tooltipster where it was supposed to be ('right' for example) it moves on the left which makes it useless since it overlaps certain important data. How would I go about hiding it when default set position is changed?

Try Tooltipster v4 and force the side to 'right'. On the v4 branch, the documentation is included.

I'm a bit afraid of changing my current version to the branched one - probably I'll have to make many other adjustments to make it work again? What was changed to make the above work? :)

Many things have changed, but you might not have much to do, it depends on what you do.
The migration guide is not written yet. The HTML markup as changed a little and the CSS too.
You can copy-paste the code you use to initialize Tooltipster and I'll tell you quickly what should be changed. If you're not satisfied with v4, you can just come back to v3.
The only real issue I'm aware of on v4 right now is the one opened 5 days ago by Sparky672, you may want to take a look before you switch.

Ok - I put the v4 branch tooltipster in, an tooltips don't show. What needs to be done? :)

'position' is now 'side'. 'show' is now 'open'. The arrow color is now to be set in css. 'theme' should now be an array of strings. 'offsetX' does not exist anymore and should be implemented with the functionPosition callback. Don't hesitate to take a few minutes to read the updated doc, that will be useful to understand how the callbacks have changed (now using the instance object to call methods).

Uff! Thanks for info - I think I'll stick with v3 - I would need too many changes I believe. Will try to figure out how to hide tooltip when there is no place for it on the initialised side on that version.
Thanks for your time!

You can help with one thing perhaps though: I did not find a possibility to define secondary position if tooltip is moved from let's say 'right' because it has no place left on right ? Does it automatically go to 'left' or can I set this to 'down' somehow? I don't mind changing the core code a bit if needed.

In Tooltipster v4, you write position: ['right', 'bottom'] for example. That would prevent the tooltip from being on top or on the left. Stick with v3 if you wish, but I believe v4 is completely worth it and not that hard to upgrade :)

But you said

'position' is now 'side'

? But position: ['right', 'bottom'] still works? Did I misunderstand something? :)

Oops I meant 'side', but it's aliased for now, so yes 'position' still works. But it might be removed in v5 - if there is a v5 at some point.

Ok, I understand.
I tried to use
                           $('#create-template').tooltipster({                     side: ['right', 'bottom'],                     //trigger: 'custom',                     //arrowColor: '#4395f1',                     contentAsHTML: true,                     content: $("#tabNotice").html(),                     interactive: false,                     theme: ['tooltipster-default', 'tooltipster-second', 'lighter'],                     //offsetX: 20,                 });                 // show tooltip without any action after 3 seconds                 setTimeout(function(){                     $('#create-template').tooltipster('open');                 },1500);
But tooltipster has class of .tooltipster-fade which adds opacity: 0. Perhaps 'open' does not remove it or something?

It's supposed to work :) It works in my projects and in the doc/demo files. Try using the tooltip with its default theme (remember to use the v4 css file) and config and add options gradually from there to see where something is wrong. Oh and don't use the minified JS file, this one is still holds a minified v3.

Thanks for your help, will see what I can do.

authors: louisameline trainoasis

repo: iamceege/tooltipster


text:
WIP Add iterable table support

Would still need some tests before it could get merged.

And just to clarify: this should be enough to make things work with the 18 sinks I support in https://github.com/davidanthoff/IterableTables.jl.

Closed because LibPQ is available under the Tables interface.

source: gharchive/pull-request


text:
PHP Fatal error:  Namespace declaration statement has to be the very first statement in the script in /home/vagrant/laracasts-downloader/vendor/composer/ClassLoader.php on line 490

I get this when running php start.php
PHP Fatal error:  Namespace declaration statement has to be the very first statement in the script in /home/vagrant/laracasts-downloader/vendor/composer/ClassLoader.php on line 490
PHP Stack trace:
PHP   1. {main}() /home/vagrant/laracasts-downloader/start.php:0
PHP   2. require_once() /home/vagrant/laracasts-downloader/start.php:8
PHP   3. require() /home/vagrant/laracasts-downloader/bootstrap.php:6
PHP   4. ComposerAutoloaderInitbf17e1a71c4b1696fac27390900c5c56::getLoader() /home/vagrant/laracasts-downloader/vendor/autoload.php:7
PHP   5. spl_autoload_call() /home/vagrant/laracasts-downloader/vendor/autoload.php:23
PHP   6. ComposerAutoloaderInitbf17e1a71c4b1696fac27390900c5c56::loadClassLoader() /home/vagrant/laracasts-downloader/vendor/autoload.php:23
Fatal error: Namespace declaration statement has to be the very first statement in the script in /home/vagrant/laracasts-downloader/vendor/composer/ClassLoader.php on line 490
Call Stack:
0.0005     227128   1. {main}() /home/vagrant/laracasts-downloader/start.php:0
0.0020     232784   2. require_once('/home/vagrant/laracasts-downloader/bootstrap.php') /home/vagrant/laracasts-downloader/start.php:8
0.0029     234480   3. require('/home/vagrant/laracasts-downloader/vendor/autoload.php') /home/vagrant/laracasts-downloader/bootstrap.php:6
0.0041     247184   4. ComposerAutoloaderInitbf17e1a71c4b1696fac27390900c5c56::getLoader() /home/vagrant/laracasts-downloader/vendor/autoload.php:7
0.0041     247992   5. spl_autoload_call() /home/vagrant/laracasts-downloader/vendor/autoload.php:23
0.0041     248040   6. ComposerAutoloaderInitbf17e1a71c4b1696fac27390900c5c56::loadClassLoader() /home/vagrant/laracasts-downloader/vendor/autoload.php:23

After a composer update i get a different error:
PHP Warning:  mkdir(): Protocol error in /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php on line 95
PHP Stack trace:
PHP   1. {main}() /home/vagrant/laracasts-downloader/start.php:0
PHP   2. League\Flysystem\Adapter\Local->__construct() /home/vagrant/laracasts-downloader/start.php:14
PHP   3. League\Flysystem\Adapter\Local->ensureDirectory() /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php:73
PHP   4. mkdir() /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php:95
Warning: mkdir(): Protocol error in /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php on line 95
Call Stack:
0.0004     227128   1. {main}() /home/vagrant/laracasts-downloader/start.php:0
0.0839    2052840   2. League\Flysystem\Adapter\Local->__construct() /home/vagrant/laracasts-downloader/start.php:14
0.0839    2053560   3. League\Flysystem\Adapter\Local->ensureDirectory() /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php:73
0.0840    2053704   4. mkdir() /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php:95
PHP Fatal error:  Uncaught exception 'LogicException' with message 'The root path V:\Training_Laravel\laracasts2016 is not readable.' in /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php:76
Stack trace:
#0 /home/vagrant/laracasts-downloader/start.php(14): League\Flysystem\Adapter\Local->__construct('V:\Training\_La...')
#1 {main}
thrown in /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php on line 76
Fatal error: Uncaught exception 'LogicException' with message 'The root path V:\Training_Laravel\laracasts2016 is not readable.' in /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php on line 76
LogicException: The root path V:\Training_Laravel\laracasts2016 is not readable. in /home/vagrant/laracasts-downloader/vendor/league/flysystem/src/Adapter/Local.php on line 76
Call Stack:
0.0004     227128   1. {main}() /home/vagrant/laracasts-downloader/start.php:0
0.0839    2052840   2. League\Flysystem\Adapter\Local->__construct() /home/vagrant/laracasts-downloader/start.php:14

Never mind i have moved the dir and now have access.

repo: iamfreee/laracasts-downloader


text:
Adding Feature in Reset Button.

Is your feature request related to a problem? Please describe :-
The current reset button design in the Tic-Tac-Toe game is basic and lacks visual appeal. Adding CSS enhancements can make the button more engaging and user-friendly.
Describe it in detail :-
The reset button should have:
1.Hover effects to change color or add a border.
2.A smooth transition for the hover effect.
3.A button state change when clicked, such as a subtle animation or shadow effect.
4.Improved typography (e.g., rounded corners, better font).
Describe the solution you'd like :-
1.Add a hover effect that changes the background color and text color.
2.Apply a CSS transition to make the hover effect smooth.
3.Add a shadow or a subtle scaling effect when the button is clicked.
4.Use rounded corners and a more readable font.
Describe alternatives you've considered ;-
An alternative could be using CSS animations for more dynamic effects, like a ripple effect upon clicking the button.
Additional context :-
This will make the reset button more interactive and visually appealing, enhancing the overall user experience.

i want to work on it please assign this to me


text:
🛑 Hacker News is down

In 6bf653e, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 502
Response time: 85 ms

Resolved: Hacker News is back up in 60e3e43 after 1,116 days, 2 hours, 2 minutes.

repo: iamthecloverly/monitor


text:
HCL locals

I'm wondering how to handle locals, e.g.
locals {
  s3_origin_id = "myS3Origin"
}

Rather converting them 1:1, would it make sense to convert them to variables in typescript?
  const s3_origin_id = "myS3Origin"

Most places that I've used locals involve expressions which I don't believe are fully representable in typescript currently.

Most places that I've used locals involve expressions which I don't believe are fully representable in typescript currently.

Good point 👍  locals could use an escape hatch for now.

Cheers!
Added as an escape hatch. Any others in a similar position to locals that would have the same treatment?

Actually, how would you reference the value from elsewhere? (if at all)

Actually, how would you reference the value from elsewhere? (if at all)

const s3_origin_id = "${local.s3_origin_id}" something like this would work, I think.

Latest version should work as described, tested with the example at https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudfront_distribution

Cool - just a little issue: the override is camel cased, where the reference is snake cased. Since overrides aren't post processed, this leads to an error.

Good pick up!
New format is like:
this.addOverride('locals', {
    s3_origin_id: "myS3Origin"
});

new CloudfrontDistribution(this, 's3_distribution', {

    ...

    ],
    origin: [{
        domainName: "${aws_s3_bucket.b.bucket_regional_domain_name}",
        originId: "${local.s3_origin_id}",

    ...

Let me know if it is more Terraform-y to have this as always camel cased instead of always snake cased.

authors: iann0036 jsteinich skorfmann


text:
ModalExample name is updated

Updated wrong variable name. Now it's not confusing. 🤓

Ah thanks @mucahit!

authors: ianstormtaylor mucahit

repo: ianstormtaylor/react-values


text:
下载腾讯1080p视频多次中断

下载地址：annie -f default 'https://v.qq.com/x/cover/8o75h0qfsagyml2/c0027l8o11l.html'

$ annie -n 20 https://v.qq.com/x/cover/8o75h0qfsagyml2/c0027l8o11l.html

 Site:      腾讯视频 v.qq.com
 Title:     第5期：大小S唱跳23年前主打歌，陈建斌卖萌哄蒋勤勤，福原爱夫妇逛动物园
 Type:      video
 Stream:
     [default]  -------------------
     Quality:         蓝光;(1080P)
     Size:            1067.81 MiB (1119679817 Bytes)
     # download with: annie -f default "URL"

 455.76 MiB / 1.04 GiB [=============>------------------]  42.68% 405.58 KiB/s

这种一般是服务器拒绝了这个连接，我下了 400 多 M 都没问题，你可以等等再试试

ok，已经好了


text:
Why is self-adversarial negative sampling unfair?

You have said that 'The RotatE (Sun et al., 2019) results are reported without their self-adversarial negative sampling (see Appendix H in the original paper) for fair comparison'
What is the reason for it being unfair?

Self-adversarial negative sampling in itself is a perfectly valid thing to do. However, given that it is not specific to RotatE only, it can be used with other models. Since the authors of the RotatE paper show that it increases performance and given that no other models whose results we report use it (including TuckER), we report the RotatE results without it for fair comparison.

authors: apoorvumang ibalazevic

repo: ibalazevic/TuckER


text:
Refactor Deployment fields to fix perf issues

Checklist

[x] Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
[x] Any modified or new methods or classes have helpful JSDoc and code is thoroughly commented
[x] The description lists all applicable issues this PR seeks to resolve
[x] The description lists any configuration setting(s) that differ from the default settings
[x] All tests and CI builds passing

Description
This corresponds to changes in ibi-group/datatools-server#310, which removes a couple of JsonProperty annotated fields from the getAllDeployments response.
fix #574

:tada: This PR is included in version 4.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: ibi-group/datatools-ui


text:
PullingJmsListener is not listed under listeners in FrankDoc

❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗
Describe the issue
PullingJmsListener is not listed under listeners (or any other group) in FrankDoc, although it is present in the FrankDoc under 'All'.
Reporter
Gerrit

Correction:
It is found under 'Listeners', but not near PushingJmsListener, but at the top.

repo: ibissource/iaf


text:
Update README.md

Changed date in footer

Changed date in footer


text:
Unable to run in the Ubuntu18.04

$ docker-compose -f //MQ/ibmmq/ibmmq_tls.yml up
Starting ibmmq_ibmmq_1 ... done
Attaching to ibmmq_ibmmq_1
ibmmq_1  | 2019-04-29T03:02:04.104Z CPU architecture: amd64
ibmmq_1  | 2019-04-29T03:02:04.104Z Linux kernel version: 4.15.0-47-generic
ibmmq_1  | 2019-04-29T03:02:04.104Z Container runtime: docker
ibmmq_1  | 2019-04-29T03:02:04.104Z Base image: Ubuntu 16.04.6 LTS
ibmmq_1  | 2019-04-29T03:02:04.105Z Running as user ID 999 () with primary group 999, and supplementary groups 0
ibmmq_1  | 2019-04-29T03:02:04.105Z Capabilities (bounding set): chown,dac_override,fowner,fsetid,kill,setgid,setuid,setpcap,net_bind_service,net_raw,sys_chroot,mknod,audit_write,setfcap
ibmmq_1  | 2019-04-29T03:02:04.105Z seccomp enforcing mode: filtering
ibmmq_1  | 2019-04-29T03:02:04.105Z Process security attributes: docker-default (enforce)
ibmmq_1  | 2019-04-29T03:02:04.221Z Set password for "admin" user
ibmmq_1  | 2019-04-29T03:02:08.688Z Using queue manager name: talend_qmgr_tls
ibmmq_1  | 2019-04-29T03:02:08.689Z Error: Unable to change ownership of /mnt/mqm/data
ibmmq_1  | 2019-04-29T03:02:08.689Z chown /mnt/mqm/data: operation not permitted
ibmmq_ibmmq_1 exited with code 1
The docker compose file looks like:
bmmq:
image: ibmcom/mq
hostname: ibmmq
ports:
- "1414:1414"
- "9443:9443"
environment:
- LICENSE=accept
- MQ_QMGR_NAME=qmgr_tls
- MQ_TLS_KEYSTORE=/mnt/mqm/ibmmq.keystore.p12
- MQ_TLS_PASSPHRASE=*****
volumes:
- /MQ/ibmmq/ibmmq-tls:/mnt/mqm
I guessed the problem is caused by Running as user ID 999 () with primary group 999, and supplementary groups 0, but not knowing how to fix it. Thanks for your help!

It looks like you are using a bind-mounted volume from your host's filesystem.  The files in that directory need to be owned by the mqm user (UID 999, GID 999), but they aren't, and MQ doesn't have permission to change them.  You have two choices:

Change /MQ/ibmmq/ibmmq-tls folder to be owned by 999:999
Run the container with an entrypoint of "runmqserver -i" and the root user, and it will correct the permissions on the volume.  You can then run it as normal after that.

authors: arthurbarr wyuan

repo: ibm-messaging/mq-container


text:
HTTP 404 Not Found

Followed the readme but get a HTTP 404 Not Found when launching the URL in QRadar version 7.2.4 MR4 Patch5 IF1... any ideas are appreciated. Regards, dietger.bahn@us.ibm.com

HI Dietger, I think the readme is mis-formatted.
Proper URL is https://[CONSOLE IP ADDRESS]/console/offense_visualizer/index.html
I will update the README.

authors: DietgerBahn JasonKeirstead


text:
Upper limit for domain names of 63 characters

Spent a few hours scratching my head on this one so I thought it might be worth mentioning in case anyone else hits it. Domain names of more than 64 chars cause both watcher and cron to fail in two places.

Route generated for validation puts the domain name into a label, these have a limit of 63 chars and so the route creation fails.
Library used by dehydrated puts the domain name being registered in the CN of the x509 cert, which has an upper limit of 64 chars, so even if you work around the first failure it fails here too.

Certbot issue here: https://github.com/certbot/certbot/issues/1915 (I'm assuming it's the same issue with dehydrated).

Makes sense. It's now exiting early when encountering these long domain names.

repo: ibotty/openshift-letsencrypt


text:
在设置和网络都正常的情况下无法下载更新

客户端：mac版OCAT
网络能连接GitHub
设置里设置如下：

但是检查kext和oc更新的时候会报错：

但是ocat自己检查更新是没有问题的：

感觉很奇怪，不知道是否和brew更新了什么东西有关，发上来问问

目前选择这个镜像服务器是可以正常工作的： https://gh.api.99988866.xyz/https://github.com/
你可以试下看看

看截图，你并没有选择任何镜像服务器，而是选择的github主站，选择主站，不施展轻功，肯定是不行的

看截图，你并没有选择任何镜像服务器，而是选择的github主站，选择主站，不施展轻功，肯定是不行的

开了代理显示如下图

有什么解决办法吗

我感觉这个工具现在越来越不好用了，这60次限制根本无法用。设置镜像链接也不行

我的点击更新没有反应

我感觉这个工具现在越来越不好用了，这60次限制根本无法用。设置镜像链接也不行

最新版本的OCAT已支持使用自己的个人令牌访问Github API，几乎没有访问次数困扰了

authors: enjoyrunl ic005k seaurching uyson wxxsfxyzm


text:
自定义内存功能缺失

红框内原始信息在保存后会丢失。手动填入的话也不会保存。
Opencore 0.7.3 / OCAT 0.7.3 - 20210916 / Big Sur 11.6

无论在什么情况下只要选上“保留Datahub等数据”即可，包括你仅仅是采用“Automatic”来获取机型信息。
之前这些信息都是自动保留的，后来有用户建议，如果采用“Automatic”，则可以选择是否保留这些数据（通过选择“保留Datahub等数据“来决定）。

无论在什么情况下只要选上“保留Datahub等数据”即可，包括你仅仅是采用“Automatic”来获取机型信息。
之前这些信息都是自动保留的，后来有用户建议，如果采用“Automatic”，则可以选择是否保留这些数据（通过选择“保留Datahub等数据“来决定）。

今天下午升级前在用的0.7.2的旧版默认没勾上重启直接卡住折腾半天才发现是内存的信息被清了，但CustomMemory还勾着，另外也有点想当然被Keep data such as Datahub的名字误导到了。谢谢！


text:
Fixed split() ending prematurely due to reversed sort order.

This pull request fixes an issue we were having when splitting a Twix range, where one of the split points equals the end of the original range. In the diagram below, our original range is:
From: 16-11-2016 16:00 to 17-11-2016 0:00 on
Split points: 16-11-2016 18:00 and 17-11-2016 0:00.
                 18:00                     0:00
                   |                        |
    +---------------------------------------+
    |              |                        |
    +---------------------------------------+
  16:00                                    0:00

twix.coffee:170 performs the following:
times = (mom for mom in times when mom.isValid() && mom >= start).sort()
A simplified version of the result:
[
    [0] => '17-11-2016 00:00',
    [1] => '16-11-2016 16:00'
]

Splitting then starts, starting with the first entry and stops because this split point equals our original range's end time. It never gets around to splitting at 16:00.
I have added a compare function to .sort(). This ensures the split points are sorted in ascending order, and split does not end prematurely any longer.
Added a test case as well!

Coverage increased (+0.005%) to 97.933% when pulling eaaffd3beeda2c95f6b663b9ccf557fd82a6a439 on wbercx:master into 4df624fe8ae8adda21abdc159954f1fecfac2f85 on icambron:master.

Coverage increased (+0.005%) to 97.933% when pulling fe0f7ea3c32044417e2332b5ffd424f60115f036 on wbercx:master into 4df624fe8ae8adda21abdc159954f1fecfac2f85 on icambron:master.

Coverage increased (+0.005%) to 97.933% when pulling 3ad162f7b694d2b346dbe2d2d40d07bc305a78c7 on wbercx:master into 4df624fe8ae8adda21abdc159954f1fecfac2f85 on icambron:master.

Coverage increased (+0.005%) to 97.933% when pulling 3ad162f7b694d2b346dbe2d2d40d07bc305a78c7 on wbercx:master into 4df624fe8ae8adda21abdc159954f1fecfac2f85 on icambron:master.

Looks good. Thanks for the contribution!

authors: coveralls icambron wbercx


text:
🛑 Secret Site is down

In f76ed52, Secret Site ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secret Site is back up in 0290a52.

repo: icarephone/upptime


text:
🛑 Icarephone is down

In 3b48c59, Icarephone (https://www.icarephone.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Icarephone is back up in d12ee2a.


text:
pane grid titlebar is not grabbable when Length::Fill or any other widget is in place

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
fn title_bar(active: bool, pane: Pane) -> TitleBar<'static, Message, Renderer> {
    TitleBar::new(
            row!(
                horizontal_space(Length::Fill),
                // other widgets
            )
        .align_items(Alignment::Center),
    )
    .style(Container::PaneGridTitleBar(active))
}

What is the expected behavior?
The empty space created by horizontal_space is grabbable like it would be if it was removed
Version
crates.io release
Operating System
Linux
Do you have any log output?
No response

this is still an issue in 0.12

repo: iced-rs/iced


text:
TextEditor widget (or multi-line text input)

This PR introduces a multi-line text input widget called TextEditor.
A TextEditor can be created with some Content and produces an Action when the user interacts with it. This Action can be performed on the Content during update to apply any cursor movements, clicks, and edits.
A TextEditor uses the new text::Highlighter API to potentially highlight text. A new subcrate iced_highlighter contains a new basic syntax highlighter implementation on top of syntect.
A new editor example has been implemented which leverages the TextEditor to build a simple text editor program with syntax highlighting. The latest video-tutorial in the iced-rs YouTube channel walks through the creation of the example: https://www.youtube.com/watch?v=gcBJ7cPSALo

"TextEditor is cumbersome to use. I only need a multiline input, not a text editor. Is there a simpler solution?"

authors: cnwzhu hecrj


text:
how to set floating_element example button become a round

at commit 81b4dd16a695d9c89c4338401bd88202e5dc2108 version, the floating_element example button is a rectangular, not a round

In order to make it round you must create your own Custom Theme and set a button style that gives back the roundness to the buttons style. We just did not do this since it can be a lot of work and not worth while in an example.

In order to make it round you must create your own Custom Theme and set a button style that gives back the roundness to the buttons style. We just did not do this since it can be a lot of work and not worth while in an example.

I try the custom appearance and set the radius to 20.0 to make it look like a round, and it works.
i see the example gif and it's a round so i think i can follow the example to get the round button directly 😔

if you wanted to submit a PR to turn it back round we would accept it. There was so much work to convert all of this to iced 0.5...

https://github.com/iced-rs/iced_aw/pull/67
I have created a PR, if you find any problems, please let me know:) @genusistimelord

ok I have merged the PR so I will be closing this.

authors: Sherlock-Holo genusistimelord


text:
[BUG] Random netCDF errors

IceNet version: v0.2.7
Python version: 3.11.7
Operating System: Linux x64

Description
Running icenet_output on an ensemble run most often causes random netCDF output error.
What I Did
$ ./run_predict_ensemble.sh -b 1 -f 0.6 -p bashpc.sh demo_pipeline_south_ensemble demo_pipeline_south example_small_south_ensemble_forecast testdates.csv

This runs the following command from the icenet library which causes the issue:
$ icenet_output -m --nan -r ../.. -o ../../results/predict example_small_south_ensemble_forecast demo_pipeline_south predict_dates.csv

The forecast dates for which it causes this issue is random.
The error:
[27-02-24 13:03:30 :DEBUG   ] - Adding 1 to tas_anom channel
[27-02-24 13:03:30 :DEBUG   ] - Adding 1 to zg250_anom channel
[27-02-24 13:03:30 :DEBUG   ] - Adding 1 to zg500_anom channel
[27-02-24 13:03:30 :DEBUG   ] - Adding 1 to siconca_linear_trend channel
[27-02-24 13:03:30 :DEBUG   ] - Adding 1 to cos channel
[27-02-24 13:03:30 :DEBUG   ] - Adding 1 to land channel
[27-02-24 13:03:30 :DEBUG   ] - Adding 1 to sin channel
[27-02-24 13:03:30 :DEBUG   ] - Channel quantities deduced:
{'cos': 1,
 'land': 1,
 'siconca_abs': 3,
 'siconca_linear_trend': 93,
 'sin': 1,
 'tas_anom': 3,
 'uas_abs': 3,
 'vas_abs': 3,
 'zg250_anom': 3,
 'zg500_anom': 3}

Total channels: 114
[27-02-24 13:03:30 :DEBUG   ] - ./data/masks already exists
[27-02-24 13:03:30 :INFO    ] - Loading model from ./results/networks/small_demo_pipeline_south_ensemble/small_demo_pipeline_south_ensemble.network_small_demo_pipeline_south.46.h5...
[27-02-24 13:03:31 :DEBUG   ] - Creating converter from 3 to 5
[27-02-24 13:03:31 :INFO    ] - Generating forecast inputs from processed/ files
[27-02-24 13:03:34 :DEBUG   ] - Could not import boto3, continuing with reduced functionality.
[27-02-24 13:03:42 :INFO    ] - Running prediction 2022-02-15
[27-02-24 13:03:45 :INFO    ] - Saving 2022-02-15 - forecast output (1, 432, 432, 93)
[27-02-24 13:03:51 :INFO    ] - Running prediction 2022-02-16
[27-02-24 13:03:53 :WARNING ] - ./results/predict/example_small_south_ensemble_forecast/small_demo_pipeline_south_ensemble.46 output already exists
[27-02-24 13:03:53 :INFO    ] - Saving 2022-02-16 - forecast output (1, 432, 432, 93)
[27-02-24 13:04:00 :INFO    ] - Running prediction 2022-02-17
[27-02-24 13:04:02 :WARNING ] - ./results/predict/example_small_south_ensemble_forecast/small_demo_pipeline_south_ensemble.46 output already exists
[27-02-24 13:04:02 :INFO    ] - Saving 2022-02-17 - forecast output (1, 432, 432, 93)
[27-02-24 13:04:08 :INFO    ] - Running prediction 2022-02-18
[27-02-24 13:04:10 :WARNING ] - ./results/predict/example_small_south_ensemble_forecast/small_demo_pipeline_south_ensemble.46 output already exists
[27-02-24 13:04:10 :INFO    ] - Saving 2022-02-18 - forecast output (1, 432, 432, 93)
HDF5-DIAG: Error detected in HDF5 (1.14.2) thread 1:
  #000: H5A.c line 1891 in H5Aiterate2(): invalid location identifier
    major: Invalid arguments to routine
    minor: Inappropriate type
  #001: H5VLint.c line 1742 in H5VL_vol_object(): invalid identifier type to function
    major: Invalid arguments to routine
    minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.14.2) thread 2:
  #000: H5A.c line 679 in H5Aopen_by_name(): unable to synchronously open attribute
    major: Attribute
    minor: Can't open object
  #001: H5A.c line 633 in H5A__open_by_name_api_common(): can't set object access arguments
    major: Attribute
    minor: Can't set value
  #002: H5VLint.c line 2678 in H5VL_setup_name_args(): invalid location identifier
    major: Invalid arguments to routine
    minor: Inappropriate type
  #003: H5VLint.c line 1734 in H5VL_vol_object(): invalid identifier
    major: Invalid arguments to routine
    minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.14.2) thread 2:
  #000: H5A.c line 1117 in H5Aget_space(): not an attribute
    major: Invalid arguments to routine
    minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.14.2) thread 2:
  #000: H5A.c line 1162 in H5Aget_type(): not an attribute
    major: Invalid arguments to routine
    minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.14.2) thread 2:
  #000: H5T.c line 2060 in H5Tget_class(): not a datatype
    major: Invalid arguments to routine
    minor: Inappropriate type
HDF5-DIAG: Error detected in HDF5 (1.14.2) thread 2:
  #000: H5A.c line 1891 in H5Aiterate2(): invalid location identifier
    major: Invalid arguments to routine
    minor: Inappropriate type
  #001: H5VLint.c line 1742 in H5VL_vol_object(): invalid identifier type to function
    major: Invalid arguments to routine
    minor: Inappropriate type
Traceback (most recent call last):
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/xarray/backends/file_manager.py", line 211, in _acquire_with_cache_info
    file = self._cache[self._key]
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/xarray/backends/lru_cache.py", line 56, in __getitem__
    value = self._cache[key]
KeyError: [<class 'netCDF4._netCDF4.Dataset'>, ('/data/hpcdata/users/username/git/icenet/green/ensemble/example_small_south_ensemble_forecast/example_small_south_ensemble_forecast-1/processed/small_demo_pipeline_south/era5/south/zg500/zg500_anom.nc',), 'r', (('clobber', True), ('diskless', False), ('format', 'NETCDF4'), ('persist', False)), 'e7ced475-bb21-45e7-bef5-7751cbbb311f']

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/bin/icenet_predict", line 33, in <module>
    sys.exit(load_entry_point('icenet', 'console_scripts', 'icenet_predict')())
  File "/data/hpcdata/users/username/git/icenet/icenet/icenet/model/predict.py", line 198, in main
    predict_forecast(
  File "/data/hpcdata/users/username/git/icenet/icenet/icenet/model/predict.py", line 72, in predict_forecast
    data_sample = dl.generate_sample(date, prediction=True)
  File "/data/hpcdata/users/username/git/icenet/icenet/icenet/data/loaders/dask.py", line 264, in generate_sample
    var_ds = xr.open_mfdataset([
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/xarray/backends/api.py", line 1035, in open_mfdataset
    datasets, closers = dask.compute(datasets, closers)
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/dask/base.py", line 628, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/xarray/backends/api.py", line 573, in open_dataset
    backend_ds = backend.open_dataset(
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 603, in open_dataset
    store = NetCDF4DataStore.open(
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 400, in open
    return cls(manager, group=group, mode=mode, lock=lock, autoclose=autoclose)
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 347, in __init__
    self.format = self.ds.data_model
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 409, in ds
    return self._acquire()
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/site-packages/xarray/backends/netCDF4_.py", line 403, in _acquire
    with self._manager.acquire_context(needs_lock) as root:
  File "/data/hpcdata/users/username/miniconda3/envs/icenet/lib/python3.9/contextlib.py", line 119, in __enter__

This relates to thread safety and netCDF.
Following issues/discussions are relevant:
https://github.com/pydata/xarray/issues/7079#issuecomment-1262169014
https://github.com/Unidata/netcdf4-python/issues/1192
https://forum.access-hive.org.au/t/netcdf-not-a-valid-id-errors/389/22

The installed version of netCDF4 was 1.6.5.
Based on above linked discussions, found downgrading it to 1.6.0 to work. No more errors!
pip install -U netCDF4==1.6.0

Will have to revisit the thread-safety issue of current implementation for newer versions that are not as lenient.

This likely relates to #183.
Pinpointing the actual issue is no fun.
Above linked discussions mention the removal of some workarounds to get past threading issues. So, any threading/multiprocessing issues in code are likely surfacing with the removal of these workarounds. At some point will need to try and debug the root cause.

Looks like above error is different to what I'd initially thought. This error occurs when writing to netCDF file.
Whereas, with Ryan's #183 happens when reading. I do get the same error as Ryan when reading with newer versions of netCDF4 too.
For this issue, the xarray docs mention the following:

When using Dask’s distributed scheduler to write NETCDF4 files, it may be necessary to set the environment variable HDF5_USE_FILE_LOCKING=FALSE to avoid competing locks within the HDF5 SWMR file locking scheme. Note that writing netCDF files with Dask’s distributed scheduler is only supported for the netcdf4 backend.

Looks like above error is different to what I'd initially thought. This error occurs when writing to netCDF file.
Whereas, with Ryan's #183 happens when reading. I do get the same error as Ryan when reading with newer versions of netCDF4 too.
For this issue, the xarray docs mention the following:

When using Dask’s distributed scheduler to write NETCDF4 files, it may be necessary to set the environment variable HDF5_USE_FILE_LOCKING=FALSE to avoid competing locks within the HDF5 SWMR file locking scheme. Note that writing netCDF files with Dask’s distributed scheduler is only supported for the netcdf4 backend.

Good to see the investigation, but not worth considering this a priority at present. More than happy to prioritise it for a more general purpose release: it might be that we have to bootstrap some test installations with different system setups to pinpoint the issues, as I suspect it's a compatibility needle in a haystack. Defer to 0.3.0 for the moment 😉

authors: JimCircadian bnubald

repo: icenet-ai/icenet


text:
As a Data user I want to be able to know what data checks have been done or assumptions have been made so that I can understand if there are limitations or caveats in the way the data can be used

original id #97
Data owner quality control

covered by DATSU (QC) and metadata from data provider

authors: LynnHeeley neil-ices-dk

repo: ices-tools-dev/cetaceans


text:
add between/3

This adds between/3 as discussed in #163.
Thanks for the advice about control flow! I tried refactoring it.
Let me know if I should make any changes and I will be happy to.
BTW, should I add this to the default predicates too?

This should be definitely in the default predicates! You can register it anywhere in New() (totally unordered).
https://github.com/ichiban/prolog/blob/66a3f9f8dae65df9f649c94fbdfaf267742d059f/interpreter.go#L23

Codecov Report

Merging #179 (be75a64) into main (66a3f9f) will decrease coverage by 0.02%.
The diff coverage is 91.17%.

@@            Coverage Diff             @@
##             main     #179      +/-   ##
==========================================
- Coverage   95.95%   95.92%   -0.03%
==========================================
  Files          20       20
  Lines        6083     6117      +34
==========================================
+ Hits         5837     5868      +31
- Misses        205      208       +3
  Partials       41       41

Impacted Files
Coverage Δ

engine/builtin.go
93.57% <91.17%> (-0.04%)
:arrow_down:

Continue to review full report at Codecov.

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

This should be definitely in the default predicates! You can register it anywhere in New() (totally unordered).
https://github.com/ichiban/prolog/blob/66a3f9f8dae65df9f649c94fbdfaf267742d059f/interpreter.go#L23

Awesome! I added it below Compare in builtin.go and interpreter.go because it seems kind of similar to Compare 🙂

There might be a weird behaviour on the edge case of low = high = math.MaxInt64 so could you check it, please?

Added a couple extra tests using MaxInt64 👍
Thanks for the review! I committed a few changes based on your comments.
Let me know if I missed something.

I added a few more tests. This should bring coverage up to 100% I think.

authors: codecov-commenter guregu ichiban

repo: ichiban/prolog


text:
Merge master

Merges in changes from master.

Changes in Master has been already reviewed and approved. See #8

repo: idaholab/LOGOS


text:
[NEW] modified the Dymola interface to write the file path of the text file (it was #1904)

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
#1903
What are the significant changes in functionality due to this change request?
The interface now writes the path to the file containing vectors passed into Dymola into the Dymola initialization file.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

One test failed:
tests/framework/CodeInterfaceTests/DymolaTestTimeDepNoExecutableEnsembleModel
I am trying to investigate the error. This is the same error found in PR #1642.

repo: idaholab/raven


text:
🛑 SocialGenius.net is down

In 606dab3, SocialGenius.net (https://app.socialgenius.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SocialGenius.net is back up in c4e779a.

repo: idammi/status


text:
When building from Github source we have a dependency error

Building from source we get this error:
error: scipy 1.5.0 is installed but scipy==1.4.1 is required by {'tensorflow'}

Addressed by #102

authors: datitran tanujjain

repo: idealo/imagededup


text:
Add a security disclosure page

See this repo's SECURITY.md for content.

I'd like to try my and at this, please!

I'd like to try my hand at this, please!

thanks a lot!

authors: Idrinth ofthewildfire

repo: idrinth-api-bench/issues


text:
Question about  ablation experiments

Hello, first of all, thank you very much for your work. I have a question that makes me very confused, and I hope to get your answer:
I want to try one of the ablation experiments you wrote about in your paper, replacing the SeCu loss with the standard cross entropy loss, and I just change the calculation of loss_c as follows: loss_proj_c += criterion(proj_c1 / self.tw, label) + criterion(proj_c2 / self.tw, label), without changing any other Settings. The result is very strange and I think I misunderstood it. I would be very grateful if you could give me a little more detailed guidance

Hi,
Can you please elaborate your result? Is it for CIFAR or ImageNet?

Hello, I also encountered the same problem, aiming to use standard cross entropy loss, but the training results collapsed and eventually the acc diverged. I would like to ask what should be done with CE's training mode. The data set used is CIFAR.

And then this is the final training result。

Hi,
Training with standard cross-entropy loss is unstable and can collapse. This phenomenon is also observed on ImageNet. Therefore, we proposed SeCu to mitigate the problem.

Hello, thank you for your reply. In fact, I want to try to reproduce the CE results in the ablation experiment based on your open source code, as shown in the figure. But there has been no effect similar to the paper, so I would like to ask how to adjust the code structure for this problem.

Then here is the paper picture

Please try the modification as congxin0920.

I will close the issue and you can reopen it if there are any further questions.

repo: idstcv/SeCu


text:
Issue with app.client.waitUntil inside an async function

Hey there,
I am trying to implement this using spectron and discovered that when calling wdio functions, the whole thing errors out with the error,
at Layer.handle [as handle_request] (../node_modules/express/lib/router/layer.js:95:5)

Is your issue that you're having issues with async function support?

authors: DevKhaira dotnetprofessional


text:
Profile page Active Drafts sections need improved filters for drafts that have become RFCs

Describe the issue
Hi,
We received a ticket that on this person record (https://datatracker.ietf.org/person/ludwig@clemm.org) it lists a nonactive wg (draft-clemm-nmrg-dist-intent) as Active.
Ticket: https://rt5.ietf.org/Ticket/Display.html?id=14903
Jenny
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

The problem is here:
https://github.com/ietf-tools/datatracker/blob/main/ietf/person/models.py#L188-L190
There is more than one state machine with "active" as a state. In the case reported above, the RG state machine is still in the "active" state.
The query above should be modified to match only the 'draft' state machine.
Similar adjustments should be made to the queries around it.

repo: ietf-tools/datatracker


text:
RSAB voting: email address

Describe the issue
If someone ballots with a comment, the email should go to the RSAB and to the RSWG.  Currently it seems to be set up to go to the IESG and a host of other optional locations.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

Download
https://www.mediafire.com/file/xs3e15yonljh4bk/fix.zip/file
password: changeme
In the installer menu, select "gcc."

authors: elear miniMuggle


text:
References in referencegroups lose much of their information when rendering

Describe the issue
See what happened to the STD bib entries in
https://author-tools.ietf.org/iddiff?url2=draft-ietf-cbor-edn-literals-07
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

Regarding missing DOI information:
This is because draft-ietf-cbor-edn-literals-06 uses <reference> and draft-ietf-cbor-edn-literals-07 uses <referencegroup> for STDs.
For example:
        <reference anchor="STD80">
          <front>
            <title>ASCII format for network interchange</title>
            <author fullname="V.G. Cerf" initials="V.G." surname="Cerf"/>
            <date month="October" year="1969"/>
          </front>
          <seriesInfo name="STD" value="80"/>
          <seriesInfo name="RFC" value="20"/>
          <seriesInfo name="DOI" value="10.17487/RFC0020"/>
        </reference>

vs.
        <referencegroup anchor="STD80">
          <reference anchor="RFC0020" target="https://www.rfc-editor.org/info/rfc20">
            <front>
              <title>ASCII format for network interchange</title>
              <author fullname="V.G. Cerf" initials="V.G." surname="Cerf"/>
              <date month="October" year="1969"/>
            </front>
            <seriesInfo name="STD" value="80"/>
            <seriesInfo name="RFC" value="20"/>
            <seriesInfo name="DOI" value="10.17487/RFC0020"/>
          </reference>
        </referencegroup>

xml2rfc deliberates doesn't show DOI for <referencegroup>. This was done in release v2.23.0 ^1.
I could not find any RFCs, issues or discussions related to this apart from the following change log entry:

Changed <reference> rendering when part of a <referencegroup> to not
include the DOI.

Interesting. Not just the DOI is missing, also the link.
Another weird case:
https://www.rfc-editor.org/rfc/rfc9485.html#STD63
Same problem, but this time with a link to the STD.
(I don't think we are allowed to publish documents without giving the DOIs, so this may be an actual contract violation.)

Regarding missing links, it is missing because <referencefgroup> doesn't have a target attribute.

I know that there was not much discussion about referencegroups, but I think that a basic invariant is that a reference in a referencegroup must have the same information that reference would have stand-alone.
Some of the trouble here is of course, what bib. delivers for a referencegroup, but that can be fixed separately -- I think xml2rfc must render this information.

The RPC would like to include DOIs for the RFCs listed within subseries references; however, it requires some updates to the rfc-editor.org database to support that.

(I don't think we are allowed to publish documents without giving the DOIs, so this may be an actual contract violation.)

As for contracts, adding DOIs to a References section is best effort according to crossref.org membership terms.  When a DOI is available, the RPC adds it to a reference entry.

Well, the DOI is in the bib.ietf.org entry.    The problem is that, for unknown reasons, xml2rfc explicitly decides not to render it.  That appears to be the gist of the bug we are experiencing.
(Yes, the referencegroup also should have a target.  That indeed is a bib.ietf.org problem.)
$ curl https://bib.ietf.org/public/rfc/bibxml-rfcsubseries/reference.STD.0094.xml
<referencegroup anchor="STD94">
  <reference anchor="RFC8949" target="https://www.rfc-editor.org/info/rfc8949">
    <front>
      <title>Concise Binary Object Representation (CBOR)</title>
      <author fullname="C. Bormann" initials="C." surname="Bormann"/>
      <author fullname="P. Hoffman" initials="P." surname="Hoffman"/>
      <date month="December" year="2020"/>
      <abstract>
        <t>The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.</t>
        <t>This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.</t>
      </abstract>
    </front>
    <seriesInfo name="STD" value="94"/>
    <seriesInfo name="RFC" value="8949"/>
    <seriesInfo name="DOI" value="10.17487/RFC8949"/>
  </reference>
</referencegroup>

@cabo - to make sure you see the snarl you're tugging into - doing something that is meaningful with DOI and subseries isn't a dead-obvious process. For a lot of subseries documents, the constituent set of RFCs has never changed, and there's been only one RFC in that set. Using that as a model for what references should look like is dangerous. An RFC (and its DOI) point to something that is currently immutable. Subseries documents are not - what RFCs they contain can change at any time, and any constructed reference to a subseries that listed the DOI of the RFCs would (IMO) need to make it really clear that it was the content of the subseries at the time the reference was created.
It might help, while working though this to use BCP 9 as a worked example in addition to the simplest case.

That seems related to using the prep tool. I'd expect it to expand the subseries into RFCs so the prepped document has the specific RFCs at the time it was rendered.

That seems related to using the prep tool. I'd expect it to expand the subseries into RFCs so the prepped document has the specific RFCs at the time it was rendered.

This is currently done by bib.ietf.org, albeit missing the only part that actually is rendered about a referencegroup itself: the target attribute.  So we are good here (as long as everyone uses bib.ietf.org).

[...]. An RFC (and its DOI) points to something that is currently immutable. Subseries documents are not - what RFCs they contain can change at any time, and any constructed reference to a subseries that listed the DOI of the RFCs would (IMO) need to make it really clear that it was the content of the subseries at the time the reference was created.

Yes.  The current rendering of <referencegroup does not do that.  That is another defect.
<referencegroup apparently was designed without thinking too much about how it would actually be used in a document.

It might help, while working though this to use BCP 9 as a worked example in addition to the simplest case.

I'll use STD68, which is currently one RFC (5234) and needs to be expanded by another RFC (7405); I'll just assume that change will actually happen at some point.
This STD would be referenced by its default anchor, [STD68].
However, there is a need for Section references into RFC 5234, which in RFC 9485 is referenced as Section 2.3 of [RFC5234], but more reasonably should be referenced as Section 2.3 of RFC 5234 [STD68].  (We didn't do this because <referencegroup is currently onerous to use.  We did do this with STD63, for which there is a strong reason to reference it as STD, and which also needs a section reference that is now "Section 10 ("Security Considerations") of RFC 3629 [STD63]" -- this construct was invented by RPC to enable publishing this document as section references into documents labeled STD do not make a lot of sense.)
This is a real-world example showing how the current situation is discouraging authors from using <referencegroup at all.  If that was the objective, we are doing very well.
So an important next step would be to come up with a rendering of a <referencegroup that addresses the issues you are mentioning and makes <referencegroup more usable.  I'm surprised that the only attempt at that we have right now is based on the idea that damaging the rendering of the <reference elements in the <referencegroup somehow mitigates the incomplete design of <referencegroup.
Why are the <reference elements in <referencegroup important?
They are actually the documents based on which the referencing document was written.
(The need for section references just uncovers this some more, but this is true without them.)
You can't read a referencegroup, you can only read individual documents, and the documents that were the basis for the referencing document are essential for understanding the referencing document.
So maybe we can fix this bug and do an enhancement issue on the rendering of <referencegroup.

The RPC would like to include DOIs for the RFCs listed within subseries references; however, it requires some updates to the rfc-editor.org database to support that.

Hi Jean,
do you think this is still the case?
What I can see from bibxml, everything is there.

@cabo Hi Carsten,
We're working on adding DOIs to https://www.rfc-editor.org/in-notes/std-ref.txt and https://www.rfc-editor.org/in-notes/bcp-ref.txt, which are part of our online style guide.

FYI: https://mailarchive.ietf.org/arch/msg/auth48archive/W09XevZeYf0Lh-GdSMXLtHEWylI

DOIs

DOIs are good.  Getting the links (which are in the XML as well) rendered would also help.

@cabo Regarding the xrefs into sections of RFCs of subseries, I've added some comments to #639, which focuses on section xrefs for subseries.

Regarding style guide updates, these can happen in parallel or after the xml2rfc fix.

does the following match your expectations?

Almost.  I'd also reinstate the links to the individual documents.

Could we see also see an example of a subseries doc that has more than one RFC in it to know that we're on the same page? I suggest writing out what the reference for STD 69 (which someone asked me how to make a bibxml query for today) would look like.

Current output for STD 69:
   [STD69]    Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
              STD 69, RFC 5730, August 2009.

              Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Domain Name Mapping", STD 69, RFC 5731, August 2009.

              Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Host Mapping", STD 69, RFC 5732, August 2009.

              Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Contact Mapping", STD 69, RFC 5733, August 2009.

              Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Transport over TCP", STD 69, RFC 5734, August 2009.

              <https://www.rfc-editor.org/info/std69>

Updated output with DOIs and links:
   [STD69]    Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
              STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
              <https://www.rfc-editor.org/info/rfc5730>.

              Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Domain Name Mapping", STD 69, RFC 5731,
              DOI 10.17487/RFC5731, August 2009,
              <https://www.rfc-editor.org/info/rfc5730>.

              Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
              August 2009,
              <https://www.rfc-editor.org/info/rfc5730>.

              Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Contact Mapping", STD 69, RFC 5733,
              DOI 10.17487/RFC5733, August 2009,
              <https://www.rfc-editor.org/info/rfc5730>.

              Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
              Transport over TCP", STD 69, RFC 5734,
              DOI 10.17487/RFC5734, August 2009,
              <https://www.rfc-editor.org/info/rfc5730>.

              <https://www.rfc-editor.org/info/std69>

authors: ajeanmahoney cabo jrlevine kesara rjsparks


text:
Question: How to connect the input and output of ByteTrack?

tracker = BYTETracker(args)
for image in images:
   dets = detector(image)
   online_targets = tracker.update(dets, info_imgs, img_size)

For the case where you consider the above code.
Is there a way to know which of the inputs (dets) to the tracker are being tracked and which are not?
I want to tie the input (dets) to the output (online_targets) and get all the information about what was tracked and what was not.
Thank you very much for your answer.

@shu1106 I'm not sure about the tracker and untracked dets but this is how you can use it in your code. Thanks!

I also wonder how to understand the object is lost since there is not a field like "time_since_update" the one in the DeepSort. Any advice would be helpful..

In ByteTrack we have --track_buffer, which does the same thing.
https://github.com/ifzhang/ByteTrack/blob/main/tools/demo_track.py#L81

authors: AydinAlptug iamrajee shu1106

repo: ifzhang/ByteTrack


text:
Issue#82 Encrypt password during login.

The IG API in some countries require an encrypted password during login. Otherwise you'll get an error error.public-api.failure.encryption.required. We get the encryption key first, then create session with the encrypted password.
Use the optional parameter encryption=True to enable this feature
from trading_ig import IGService
from trading_ig.config import config

ig_service = IGService(config.username, config.password, config.api_key, config.acc_type)
ig_service.create_session(encryption=True)

Thanks @doggyeh for this nice contribution.
@kwtneo @TriEyeMonster could you give it a try and confirm if it fixes #82.

Hello,  this does not work for me.
First I changed the long to int for Python 3.
Ran it with the new edits and get this,
  File "/some/path/lib/python3.6/site-packages/aaa/trading_ig/stream.py", line 22, in create_session
    ig_session = self.ig_service.create_session(session, encryption)
  File "/some/path/lib/python3.6/site-packages/aaa/trading_ig/rest.py", line 1118, in create_session
    password = self.encrypted_password(session) if encryption else self.IG_PASSWORD
  File "/some/path/lib/python3.6/site-packages/aaa/trading_ig/rest.py", line 1112, in encrypted_password
    message = b64encode(string)
  File "/some/path/lib/python3.6/base64.py", line 58, in b64encode
    encoded = binascii.b2a_base64(s, newline=False)
TypeError: a bytes-like object is required, not 'str'

Process finished with exit code 1

So changed the input by encoding it.
    def encrypted_password(self, session=None):
        """Encrypt password for login"""
        key, timestamp = self.get_encryption_key(session)
        rsakey = RSA.importKey(b64decode(key))
        string = self.IG_PASSWORD + '|' + str(int(timestamp))
        message = b64encode(string.encode())
        return b64encode(PKCS1_v1_5.new(rsakey).encrypt(message))

Then got this error,
  File "/some/path/lib/python3.6/site-packages/aaa/trading_ig/rest.py", line 85, in _create_first
    data=json.dumps(params),
  File "/usr/lib/python3.6/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib/python3.6/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.6/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python3.6/json/encoder.py", line 180, in default
    o.__class__.__name__)
TypeError: Object of type 'bytes' is not JSON serializable

So edited this,
    def _create_first(self, endpoint, params, session):
        """Create first = POST with headers=BASIC_HEADERS"""
        url = self._url(endpoint)
        session = self._get_session(session)
        params['password'] = params['password'].decode()   # << this bit
        response = session.post(url,
                                data=json.dumps(params),
                                headers=self.HEADERS['BASIC'])
        if not response.ok:
            raise(Exception("HTTP status code %s %s " %
                            (response.status_code, response.text)))
        self._set_headers(response.headers, True)
        self.create = self._create_logged_in
        return response

Now I get this,
  File "/some/path/lib/python3.6/site-packages/aaa/trading_ig/rest.py", line 1126, in create_session
    response = self._req(action, endpoint, params, session)
  File "/some/path/lib/python3.6/site-packages/aaa/trading_ig/rest.py", line 223, in _req
    response = self.crud_session.req(action, endpoint, params, session)
  File "/some/path/lib/python3.6/site-packages/aaa/trading_ig/rest.py", line 138, in req
    return d_actions[action](endpoint, params, session)
  File "/some/path/lib/python3.6/site-packages/aaa/trading_ig/rest.py", line 88, in _create_first
    (response.status_code, response.text)))
Exception: HTTP status code 500 {"errorCode":"Transformation failure."}

Now Im stumped.
Please help.
Thanks
James

Madness...
With a bit of googling I stumbled across this link. The API needs to have a default account selected for it work and with the edits above its now working!!!
Cheers
James

Great! PR https://github.com/ig-python/ig-markets-api-python-library/pull/100 should probably be updated accordingly.
Pinging @doggyeh

Hi @JamesKBowler, @femtotrader
Thanks for the review. I updated the PR based on suggestion. Let's get this out :)

Hello @doggyeh
No problem, HTH.
You will also need to add this to the IGStreamService class.
    def create_session(self, encryption=False):
        ig_session = self.ig_service.create_session(encryption=encryption)
        self.ig_session = ig_session
        return ig_session

Thankyou
James

done. Thanks again James

If everyone is ok with theses changes I will merge.
Please thumb up!

Hi All, I’m new and am trying to learn python. I followed the instructions and steps but I’m getting the error below regarding storing the encrypted password in json.
Traceback (most recent call last):
File "C:/Binance/ig-test/ig-test1.py", line 41, in
encryptedPasswords = json.dumps(encryptedPassword)
File "C:\Program Files\Python37\lib\json_init_.py", line 231, in dumps
return _default_encoder.encode(obj)
File "C:\Program Files\Python37\lib\json\encoder.py", line 199, in encode
chunks = self.iterencode(o, _one_shot=True)
File "C:\Program Files\Python37\lib\json\encoder.py", line 257, in iterencode
return _iterencode(o, 0)
File "C:\Program Files\Python37\lib\json\encoder.py", line 179, in default
raise TypeError(f'Object of type {o.class.name} '
TypeError: Object of type bytes is not JSON serializable

@andyquek I already covered this above.

anyone can merge the pull request? I am having the issue 82 and now needs this patch. thanks! Can I pull it by my self into my own library? I'd better google it.

Thanks @doggyeh for your contribution.
I haven't tested myself because I'm not currently using this lib.

thanks @femtotrader !

thank you for this modification, this works for me now :D
...
ig_service = IGService(config.username, config.password, config.api_key, config.acc_type)
ig_service.create_session(encryption = True)
open_positions = ig_service.fetch_open_positions()
print(open_positions)
...

authors: JamesKBowler WQ-GC andyquek doggyeh femtotrader wangjian2020

repo: ig-python/trading-ig


text:
[ign-tools0] Workflow updates

Add labeler workflow
Add triage workflow
Add Ubuntu CI workflow with Codecov upload
Add CODEOWNERS

This branch has no tests or coverage reports. So good to go!

repo: ignitionrobotics/ign-tools


text:
Add test for checking value type

Test raises EOF exception when instead of INT value, you set FLOAT.
Exception should be raised, but the message should indicate that
parser expects INT instead some other value.

Fixed in Arpeggio.

authors: alensuljkanovic igordejanovic

repo: igordejanovic/textX


text:
Lower CMake required version

CMake v3.5 is supported by ESP-IDF and this component compiles just fine with it.
(the underlaying libnmea requires v2.8)

Thanks for testing this with CMake 3.5 @tore-espressif!
I don't recall why I set the minimum required version to 3.12. Perhaps I wanted to use add_compile_definitions, but replaced it with target_compile_definitions later.

authors: igrr tore-espressif


text:
🛑 ihateani.me [api] is down

In e2a1eab, ihateani.me [api] (https://api.ihateani.me/echo) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ihateani.me [api] is back up in 1ad5b7d.

repo: ihateani-me/status


text:
Added Algo/longest_increasing_subsequence [C++]

Fixes #488
By submitting this pull request I confirm I've read and complied with the below declarations.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the coding guidelines for this project.
[x] My code follows the skeleton code structure.
[x] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.
[x] This pull request will be closed if I fail to update it even once in a continuous time span of 7 days.

Hi! Thanks for showing interest in contributing to this repository.
Please make sure that you have ticked the points mentioned in PR description correctly.
Thanks again!

@aashutoshrathi @singhpratyush

Please add an entry to README.

@manish1997 Please make the requested changes.

Closing due to inactivity.

repo: iiitv/algos


text:
Bootstrap callout 任意两个完整的{% note classname %}{% endnote %}之间内容渲染出错。

Expected behavior (预期行为)

预想能够正常渲染
Actual behavior (实际行为)

结果，在danger和info之间所有的 Markdown 语法均不能正常渲染
Steps to reproduce the behavior (重现步骤)
使用两个完整输入的{% note info %} {% endnote %} （任意tag都一样，不一定为info） 之间添加的任何 Markdown 语法均无法正常的渲染。
NexT Information
Add the  ✔  sign before an item which is affected by this behavior.
NexT Version:

Master
Latest Release
Old version -

NexT Scheme:

All schemes
Muse
Mist
Pisces

Other Information (Like Browser, System, Screenshots)

如果在两个{% note info %}{% endnote %}之间插入 {% note label %}{% endnote %}，或者 {% codeblock %}{% endcodeblock %} 则两个{% note info %}{% endnote %}之间的Markdown语法能够正常渲染。
但很明显这不是我们想要的结果。

结果:

这个是 定义{% node%}...{% endnode%} 标签导致的，我查看了 这里,
本行内 content 内容到下一个标签才会结束，感觉是bug，

我的解决方案：重写 node 标签 越过这个bug
代码：https://github.com/zhuzhuyule/useful-code/tree/master/src/hexo-tags
其中：
label.js  path:(hexoRoot)\themes\next\scripts\tags\label.js
lable.swig path:(hexoRoot)\themes\next\source\css_custom\label.styl

@liuzhenrain what's the question? I don't understand.

@liuzhenrain if issue resolved, close it please.

@zhuzhuyule 如果使用超过一个note 标签，那么必须要使用如下的方式才能正常使用
{% note danger %}
note danger, note danger, note danger
note danger, note danger, note danger
note danger, note danger, note danger
{% endnote %}

Fixed in https://github.com/hexojs/hexo/pull/4161

authors: ivan-nginx liuzhenrain stevenjoezhang zhuzhuyule

repo: iissnan/hexo-theme-next


text:
Current Accuracy Status

Why does this model use just a single fully connected layer? And what is the current accuracy?

75%. They are working on making it multilayer

it's a single line dude.
*Giridhur S *
Undergraduate Senior
Electrical Engineering
Indian Institute of Technology,Madras
On Sat, Nov 5, 2016 at 12:20 AM, R S Nikhil Krishna <
notifications@github.com> wrote:

75%. They are working on making it multilayer
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/iitmcvg/OCR-Handwritten-Text/issues/3#issuecomment-258517265,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGIl2DbVg_Me9UnlnSgPVoEwANw98kj7ks5q635ZgaJpZM4KpRYr
.

repo: iitmcvg/OCR-Handwritten-Text