Added Tags (Challenge 161- 180)

Added tags from Challenges 161 to 180 in order to filter the search results on the web application.

Ellabit/Challenges/Challenge175Countonesinbinaryrepresentationofinteger.cs has a compile error

I think I tweaked and then merged it into the primary branch.
So your good, nothing needs to be done.


Apply hints suggested by the multi-arch hinter

Apply hints suggested by the multi-arch hinter.

libcypher-parser-doc: Add Multi-Arch: foreign. This fixes: libcypher-parser-doc could be marked Multi-Arch: foreign. (ma-foreign)

These changes were suggested on https://wiki.debian.org/MultiArch/Hints.
This merge proposal was created automatically by the Janitor bot.
For more information, including instructions on how to disable
these merge proposals, see https://janitor.debian.net/multiarch-fixes.
You can follow up to this merge proposal as you normally would.
The bot will automatically update the merge proposal to resolve merge conflicts
or close the merge proposal when all changes are applied through other means
(e.g. cherry-picks). Updates may take several hours to propagate.
Build and test logs for this branch can be found at
https://janitor.debian.net/multiarch-fixes/pkg/libcypher-parser/d491fb81-2136-4257-bb25-f397c2526f06.
Debdiff
These changes affect the binary packages:
File lists identical (after any substitutions)
No differences were encountered between the control files of package **cypher-lint**
No differences were encountered between the control files of package **cypher-lint-dbgsym**
No differences were encountered between the control files of package **libcypher-parser-dev**
Control files of package libcypher-parser-doc: lines which differ (wdiff format)

{+Multi-Arch: foreign+}

No differences were encountered between the control files of package **libcypher-parser8**
No differences were encountered between the control files of package **libcypher-parser8-dbgsym**
You can also view the diffoscope diff (unfiltered).

This merge proposal will be closed, since the branch for the role 'main'
has changed to None.


Intermittent error: "error reading S3 Bucket: empty output"

Persona

I'm a maintainer of this repo
Description

We're getting an intermittent error: "error reading S3 Bucket: empty output". This is most likely being caused by a race condition of some kind.
Use Case

Race conditions make tests flaky, which undermines confidence in the stability of the work.
Impact

If we don't fix it we'll keep getting failed tests intermittently.
Completion

A fix is implemented that we are reasonably confident will fix the intermittent issue.

Another one: https://github.com/defenseunicorns/delivery-aws-iac/actions/runs/4862819934/jobs/8669688391#step:15:14609

🤔
test-command · defenseunicorns/delivery-aws-iac@46eef83
https://github.com/defenseunicorns/delivery-aws-iac/actions/runs/4866265566/jobs/8677604708
test-command · defenseunicorns/delivery-aws-iac@46eef83
https://github.com/defenseunicorns/delivery-aws-iac/actions/runs/4866264655/jobs/8677604017

I've noticed it seems to always be the Insecure test. Is there any way that the sshuttle is messing with it?

Not that I know of. Though, the secure test does things differently. For one thing, it runs terraform apply twice, with the first one being the target of the vpc and the bastion. With that plus the sshuttle stuff the difference may be just that the secure mode test waits longer in the right area

The bucket we seem to be having issues with is the one in the bastion module, which is created and consumed immediately in both cases.
Would it make sense to use two different runners to isolate the runs from each other?

I'm playing around with this resource https://registry.terraform.io/providers/hashicorp/time/latest/docs/resources/sleep which you kind of feed a resource through into the dependent resource, can tweak the sleep. 30s didn't work unfortunately.

just got it 3 times in a row with 90 second sleep time 😬
test-command · defenseunicorns/delivery-aws-iac@46eef83
https://github.com/defenseunicorns/delivery-aws-iac/actions/runs/4866709223/jobs/8678517311
test-command · defenseunicorns/delivery-aws-iac@46eef83
https://github.com/defenseunicorns/delivery-aws-iac/actions/runs/4866709363/jobs/8678517440
test-command · defenseunicorns/delivery-aws-iac@46eef83
https://github.com/defenseunicorns/delivery-aws-iac/actions/runs/4866709782/jobs/8678518364

it looks like I'm consistently getting this error now in all of these jobs - even when not running the secure test
https://github.com/defenseunicorns/delivery-aws-iac/pull/215

Going to refactor the terraform to use the deprecated  logging implementation where you enable logging when creating the bucket. It seems to work without fail.

For now I think we put a bandaid over this test and add RetryableTerraformErrors


SessionOptions should be declared as defined.  should be included to use itoa.

Some minor issues found while porting the code to Windows.

Can one of the admins verify this patch?

@tensorflow-jenkins: test this please

Merged


Add commands and arguments for monitoring replication status when publishing images

Resolves https://github.com/SUSE/azurectl/issues/89

great :+1:


test vector semantics

Adds a checkVectorSemantics method that checks the recently-added Scalars and scalars requirements.
Migrates all the existing vector semantics checks to be inside of checkVectorSemantics too.

Converting to draft because we discussed some improvements in person.

I have updated this and it's ready for review now.

I rebased this and updated it based on the github and in-person comments.
I also added a new test for the AnyArrayBuffer Vector conformance and found a failure: #184


tweaks to README for PATH, .electron folder,...

tweaks to README for PATH, .electron folder, and cleanup gotchas

Merged


fix: Enable at_client to initialize in offline when network is down

- What I did

This PR introduces offline access capabilities to the AtClient SDK, allowing the client to initialize for offline access when network connection is not available during the authentication of an atSign.

- How I did it

The "authenticate" method has been updated to support offline access for the AtClient. Within the method, the call to "authenticate" from the AtAuth package is enclosed in a try block. If a network failure occurs during this call, the exception is caught. The code then checks if the user is already onboarded. If the user is onboarded, the AtClient is subsequently initialized for offline access.
Added AtLookup as optional parameter to AtAuthServiceImpl to enable injecting mock instance for writing unit tests. If the optional parameter "AtLookup" is not injected, then the it is initialized in "_initAtClient" method which is the existing behaviour.

- How to verify it

Added unit tests for the below scenarios

Test to verify AtClient initializes successfully in offline mode upon network failure when keychain manager contains keys.
Test to verify AtClient initialization fails when network is offline and keychain manager does not have keys.
Test to verify authenticate is successful and initialization is successful

- Description for the changelog

Enable at_client to initialize in offline when network is down

Thanks @sitaram-kalluri ... I will set aside some time tomorrow to test this out in various scenarios with noports and at_talk. @cconstab you may be interested also

Thanks @sitaram-kalluri ... I will set aside some time tomorrow to test this out in various scenarios with noports and at_talk. @cconstab you may be interested also

Ah this only applies to at_client_mobile. What manual testing has been done with apps, @sitaram-kalluri ?

Thanks @sitaram-kalluri ... I will set aside some time tomorrow to test this out in various scenarios with noports and at_talk. @cconstab you may be interested also

Ah this only applies to at_client_mobile. What manual testing has been done with apps, @sitaram-kalluri ?

Manual testing documented here

Following discussion with @sitaram-kalluri, we will look at introducing a feature flag so that application code needs to opt in to this behaviour rather than having it happen by default, as it can lead to changes in app behaviour if this feature is enabled by default

Following discussion with @sitaram-kalluri, we will look at introducing a feature flag so that application code needs to opt in to this behaviour rather than having it happen by default, as it can lead to changes in app behaviour if this feature is enabled by default

After further discussion, we have decided not to introduce a feature flag.


Python 3 - pathod.log

Uh, I think my last comment was moot. We probably want to log unicode?

:confused:

I merged cdc4acc689673141a928e2ee3e5e2b753a28a8f7 into master and fixed the tests. We're set here! :smiley:


fix(): update cahte ttl

https://openforge.teamwork.com/#/tasks/17524811
I updated the Cache TTL for the files that are under our control, only left 4 from initial 23 that are not under our control so we might need check them with the dev team to see how we can update that Cache TTL
I added Cache for 1 year for assets/images since those are not going to change (if change is the entire image to another one) so thats fine.
And for js files I added like 3 months cache since the files contain hash code and the filename changes.

Tested the service worker was still working and that everything loaded correctly. Not sure if there is anything else I should test specifically, if so please let me know. Saying QA Passes for now.


[FLOC-2370] Redirects

Fixes https://clusterhq.atlassian.net/browse/FLOC-2370

Looks good. Merge when green.


Adding pacman game

Adding pacman would be a good choice to a retro kinda website and I'm confident in implementing the same

Heyy I would like to add PacMan in this amazing project!!!
looking forward to it.

Assigned this issue to you. Kindly complete the work in a week and also go through the readme and contributing.md for successful merge. All the best to your work Tushar... !!!

Can you please assign me this issue


Check status script before turning on instance

The status script may fail because java could not properly be configured.
It could be available when running the process directly but not when calling it from *.bat or sh script.
As a result some GAP users are reporting that the instance is running properly after running the task instanceUp however immediately after starting script when instance status script is being run, build fails with an error about unknown status code 9009 which usually means "path not found" on Windows (because shell script is somehow not seeing java (?)).
to prevent running instances when java is not properly configured, let's run a status script before running instances. the status script should report "not running" status and should not fail and it will be another good prerequisite check.

done in 14.2.14


Setup and mobile first

in the project

INVALID ❌ ❌ ❌
Hi @LethaboMot  👋
While you made a great effort in this project, I can't go ahead and review your code.
Invalid Code Review Request ❌
You have submitted a project that doesn't have a README file 😨, Kindly add the README to your project and submit again once you are done 🙏
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Kindly create  a new PR that follows the Gitflow approach
Cheers and Happy coding!👏👏👏
✅ Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me in your question so I can receive the notification.
⚠ Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Unable to find the template “_inlinejs/register-service-worker.min.js”.

Unable to find the template “_inlinejs/register-service-worker.min.js”.
if have no files in my _inlinejs folder

Make sure you're running the gulp scripts before you try to load the site - they're located at the bottom of package.json. Try running npm run start or yarn start.


Fix "export" statements on packages

Changes fix some export errors when:

register the library as a plugin
import individually packaged components

Important PR. I was starting to investigate same issue


Incompatibility issue when upgrading PyJWT >= 2.0.0 by any other package

When installing any package with PyJWT >= 2.0.0 the server crashes as the django-push-notifications require PyJWT < 2.0.0
Traceback:
Exception in thread django-main-thread:
Traceback (most recent call last):
  File "/Users/anon/.pyenv/versions/3.9.0/lib/python3.9/threading.py", line 950, in _bootstrap_inner
    self.run()
  File "/Users/anon/.pyenv/versions/3.9.0/lib/python3.9/threading.py", line 888, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/django/utils/autoreload.py", line 64, in wrapper
    fn(*args, **kwargs)
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/django/core/management/commands/runserver.py", line 110, in inner_run
    autoreload.raise_last_exception()
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/django/utils/autoreload.py", line 87, in raise_last_exception
    raise _exception[1]
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 375, in execute
    autoreload.check_errors(django.setup)()
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/django/utils/autoreload.py", line 64, in wrapper
    fn(*args, **kwargs)
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/django/apps/registry.py", line 91, in populate
    app_config = AppConfig.create(entry)
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/django/apps/config.py", line 224, in create
    import_module(entry)
  File "/Users/anon/.pyenv/versions/3.9.0/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 790, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/push_notifications/__init__.py", line 4, in <module>
    __version__ = pkg_resources.require("django-push-notifications")[0].version
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/pkg_resources/__init__.py", line 886, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages/pkg_resources/__init__.py", line 777, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (PyJWT 2.3.0 (/Users/anon/.virtualenvs/venv/lib/python3.9/site-packages), Requirement.parse('PyJWT<2.0.0,>=1.4.0'), {'apns2'})

that package needed to be adjusted IMHO

@auvipy I figured out now that the problem mainly at the apns2 package and actually its updated there but the maintainer didn't release the master update now.
https://github.com/Pr0Ger/PyAPNs2/issues/133

this is because the package is not updated on pip. Use github master branch to install the lastest package

Can we install django-push-notifications without the apns2? I mean, is it necessary if one plans to use FCM?

Was anyone able to get this to work? I get this issue when I used the latest commit
apns2 @ git+https://github.com/Pr0Ger/PyAPNs2.git@910780bb909c85ffd40f8d2cd517b764c4576253
PyJWT==2.3.0
django-push-notifications==3.0.0
[03/Apr/2022 19:00:54] "PUT /api/changeTransactionStatus/fdf8c2fd-c937-475a-960f-9d8b862db492/ HTTP/1.1" 200 13966
Traceback (most recent call last):
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 138, in run
self.finish_response()
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 183, in finish_response
self.close()
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/django/core/servers/basehttp.py", line 114, in close
super().close()
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/simple_server.py", line 38, in close
SimpleHandler.close(self)
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 321, in close
self.result.close()
File "/Users/madhavsoni/Documents/BazarBackend/bazar_backend/api/views/TransactionViews/TransactionView.py", line 168, in close
self.then_callback()
File "/Users/madhavsoni/Documents/BazarBackend/bazar_backend/api/views/TransactionViews/TransactionView.py", line 232, in send_push_notification
badge=lambda token: APNSDevice.objects.get(
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/push_notifications/models.py", line 136, in send_message
creds=creds, **kwargs
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/push_notifications/apns.py", line 154, in apns_send_bulk_message
creds=creds, **kwargs
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/push_notifications/apns.py", line 103, in _apns_send
**notification_kwargs
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/apns2/client.py", line 203, in send_notification_batch
priority, expiration, collapse_id, push_type)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/apns2/client.py", line 141, in send_notification_async
auth_header = self.__credentials.get_authorization_header(topic)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/apns2/credentials.py", line 60, in get_authorization_header
token = self._get_or_create_topic_token()
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/apns2/credentials.py", line 90, in _get_or_create_topic_token
headers=headers)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/jwt/api_jwt.py", line 63, in encode
return api_jws.encode(json_payload, key, algorithm, headers, json_encoder)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/jwt/api_jws.py", line 113, in encode
key = alg_obj.prepare_key(key)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/jwt/algorithms.py", line 416, in prepare_key
key = load_pem_public_key(key)
TypeError: load_pem_public_key() missing 1 required positional argument: 'backend'
[03/Apr/2022 19:00:55] "PUT /api/changeTransactionStatus/fdf8c2fd-c937-475a-960f-9d8b862db492/ HTTP/1.1" 500 59
Exception happened during processing of request from ('<IP_ADDRESS>', 51618)
Traceback (most recent call last):
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 138, in run
self.finish_response()
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 183, in finish_response
self.close()
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/django/core/servers/basehttp.py", line 114, in close
super().close()
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/simple_server.py", line 38, in close
SimpleHandler.close(self)
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 321, in close
self.result.close()
File "/Users/madhavsoni/Documents/BazarBackend/bazar_backend/api/views/TransactionViews/TransactionView.py", line 168, in close
self.then_callback()
File "/Users/madhavsoni/Documents/BazarBackend/bazar_backend/api/views/TransactionViews/TransactionView.py", line 232, in send_push_notification
badge=lambda token: APNSDevice.objects.get(
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/push_notifications/models.py", line 136, in send_message
creds=creds, **kwargs
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/push_notifications/apns.py", line 154, in apns_send_bulk_message
creds=creds, **kwargs
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/push_notifications/apns.py", line 103, in _apns_send
**notification_kwargs
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/apns2/client.py", line 203, in send_notification_batch
priority, expiration, collapse_id, push_type)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/apns2/client.py", line 141, in send_notification_async
auth_header = self.__credentials.get_authorization_header(topic)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/apns2/credentials.py", line 60, in get_authorization_header
token = self._get_or_create_topic_token()
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/apns2/credentials.py", line 90, in _get_or_create_topic_token
headers=headers)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/jwt/api_jwt.py", line 63, in encode
return api_jws.encode(json_payload, key, algorithm, headers, json_encoder)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/jwt/api_jws.py", line 113, in encode
key = alg_obj.prepare_key(key)
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/jwt/algorithms.py", line 416, in prepare_key
key = load_pem_public_key(key)
TypeError: load_pem_public_key() missing 1 required positional argument: 'backend'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 141, in run
self.handle_error()
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/django/core/servers/basehttp.py", line 119, in handle_error
super().handle_error()
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 368, in handle_error
self.finish_response()
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 180, in finish_response
self.write(data)
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 274, in write
self.send_headers()
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 331, in send_headers
if not self.origin_server or self.client_is_modern():
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 344, in client_is_modern
return self.environ['SERVER_PROTOCOL'].upper() != 'HTTP/0.9'
TypeError: 'NoneType' object is not subscriptable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/socketserver.py", line 650, in process_request_thread
self.finish_request(request, client_address)
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/socketserver.py", line 360, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/socketserver.py", line 720, in init
self.handle()
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/django/core/servers/basehttp.py", line 174, in handle
self.handle_one_request()
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/django/core/servers/basehttp.py", line 197, in handle_one_request
handler.run(self.server.get_app())
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/handlers.py", line 144, in run
self.close()
File "/Users/madhavsoni/eb-virt/lib/python3.7/site-packages/django/core/servers/basehttp.py", line 114, in close
super().close()
File "/Users/madhavsoni/.pyenv/versions/3.7.2/lib/python3.7/wsgiref/simple_server.py", line 35, in close
self.status.split(' ',1)[0], self.bytes_sent
AttributeError: 'NoneType' object has no attribute 'split'


User registration

Implement user registration form

Login box needs a link to "Don't have an account? Register here." link.


[TimePicker][#230] Got the clock handles working on Android Chrome

There's no offsetX/Y in TouchEvent objects. So we have to calculate it manually.

Thanks @martianboy


Is MvbInvoke always required for Winform controls?

Thank you very much for the great library. I found Mvb after struggling with ReactiveUI framework. I really love Mvb. I think it's the missing component for a perfect Winform framework. I tried several MVVM/MVC frameworks for  Winform but not sastified. I have an issue when applying Mvb for Winform application. When I used MvbInvoke  to handle MvbAction and update control's properties, the form was frozen for several seconds. If I update control directly then the issue did not happen.
Did I use MvbInvoke wrong in somewhere?

Hi, thanks for appreciating my work. That's some strange behavior you describe, do you have any way to share the repository or code snippet?
The only thing the MVCAction does is make sure that the UI change happens on the main thread

Sorry, I was wrong. It's not an issue of MvbInvoke . I could fix the frozen issue. My project is a MS Office add-in with several Winform forms. Thank a lot again!!!


DLL load failed

Hi guys,
I've seem to be getting the same error across three different Windows-pc's when trying to run otioview or when import opentimelineio in Python. I ran pip install opentimelineio and PySide2.
Is this a known issue?
Thank you for your time
Traceback (most recent call last):
  File "C:\Python37\Scripts\otioview-script.py", line 11, in <module>
    load_entry_point('OpenTimelineIO==0.12.0', 'console_scripts', 'otioview')()
  File "c:\python37\lib\site-packages\pkg_resources\__init__.py", line 489, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "c:\python37\lib\site-packages\pkg_resources\__init__.py", line 2852, in load_entry_point
    return ep.load()
  File "c:\python37\lib\site-packages\pkg_resources\__init__.py", line 2443, in load
    return self.resolve()
  File "c:\python37\lib\site-packages\pkg_resources\__init__.py", line 2449, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "c:\python37\lib\site-packages\opentimelineview\__init__.py", line 27, in <module>
    from . import (
  File "c:\python37\lib\site-packages\opentimelineview\details_widget.py", line 27, in <module>
    import opentimelineio as otio
  File "c:\python37\lib\site-packages\opentimelineio\__init__.py", line 35, in <module>
    from . import (
  File "c:\python37\lib\site-packages\opentimelineio\opentime.py", line 1, in <module>
    from . _opentime import ( # noqa
ImportError: DLL load failed: The specified module could not be found.

Hi there! You are right. Can you take a look at issue https://github.com/PixarAnimationStudios/OpenTimelineIO/issues/667 please? If you move the two files I mention as I describe, otio will work for you, while we look at the installation script.

@meshula Once again, thanks! I can finally start, I'm even more excited now

Sounds like this is resolved, closing.  Thanks!

I am still getting this problem. And cannot find the way to solve this in #667 . I'm using the 0.13.0,python 2.7.


mail notification

Hi,
I am wondering if mentioning an user and sending the comment will notify user via mail?
Thanks.

Hi @camel028,
Sending email requires you to either implement and integrate with your own email server, or then use existing APIs such as AWS SES.
For security purposes, these integrations need to happen in the backend, and that is unfortunately not in the scope of this library.


add specs for MemoizedInstanceVariableName

Add a regression test for Naming/MemoizedInstanceVariableName with EnforcedStyleForLeadingUnderscores: disallowed, see https://github.com/rubocop-hq/rubocop/issues/6084#issuecomment-407370135 and the following comments.
The manual says that it is ok if method name and variable name are the same, but thats not the case if the both are starting with a _.
With rubocop 0.57.2 this offence didn't happen.

Are you saying you want to add a definition that this is okay or that you think this is a bug and the spec will help show how we currently are aligned?

Both
This adds only a missing test case wich implementation work.
https://github.com/timoschilling/rubocop/blob/4543904220da9550e30d561df38cd7b57ad57c9b/spec/rubocop/cop/naming/memoized_instance_variable_name_spec.rb#L222-L228
This spec shows a regression to 0.57.2, the specs are only green while the spec is pending
https://github.com/timoschilling/rubocop/blob/4543904220da9550e30d561df38cd7b57ad57c9b/spec/rubocop/cop/naming/memoized_instance_variable_name_spec.rb#L106-L113

any updates on this?

Sorry about the lack of responses. I'm on the road for a couple of weeks and I'm pretty short on time. I'll think more about this when I can.
In the mean time I'd defer to the @rubocop-hq/rubocop-core. :-)

👍


update svg command

Suggested changes for airfoil convert svg

don't add "svg" in front of the filename
switch with dimension the "size" prop gets mapped directly to. Right now it's the width, should be the height


[.*:] Upgrade Minio used for local development and e2e tests

[x] Change is not relevant to the end-user.

Changes

Upgrade Minio used for local development and e2e tests to https://github.com/minio/minio/commit/91130e884b5df59d66a45a0aad4f48db88f5ca63 because this version upgrades github.com/shirou/gopsutil from version v2.20.3 to v2.20.9, adding support for Apple Silicon

Verification

If you try to run make test on a Apple Silicon based MacBook using main you get a few undefined: KinfoProc erros:
bogo@Bogos-MacBook-Pro ~/D/thanos (main)> make test
(re)installing /Users/bogo/Developer/Go/bin/alertmanager-v0.20.0
(re)installing /Users/bogo/Developer/Go/bin/minio-v0.0.0-20200527010300-cccf2de129da
# github.com/shirou/gopsutil/cpu
../../Go/pkg/mod/github.com/shirou/gopsutil@v2.20.3-0.20200314133625-53cec6b37e6a+incompatible/cpu/cpu_darwin_cgo.go:13:5: warning: 'TARGET_OS_MAC' is not defined, evaluates to 0 [-Wundef-prefix=TARGET_OS_]
# github.com/shirou/gopsutil/disk
disk_darwin.c:28:2: warning: 'IOMasterPort' is deprecated: first deprecated in macOS 12.0 [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:132:1: note: 'IOMasterPort' has been explicitly marked deprecated here
# github.com/shirou/gopsutil/process
../../Go/pkg/mod/github.com/shirou/gopsutil@v2.20.3-0.20200314133625-53cec6b37e6a+incompatible/process/process_darwin.go:576:34: undefined: KinfoProc
../../Go/pkg/mod/github.com/shirou/gopsutil@v2.20.3-0.20200314133625-53cec6b37e6a+incompatible/process/process_darwin.go:577:8: undefined: KinfoProc
../../Go/pkg/mod/github.com/shirou/gopsutil@v2.20.3-0.20200314133625-53cec6b37e6a+incompatible/process/process_darwin.go:590:32: undefined: KinfoProc
../../Go/pkg/mod/github.com/shirou/gopsutil@v2.20.3-0.20200314133625-53cec6b37e6a+incompatible/process/process_darwin.go:594:62: undefined: KinfoProc
make: *** [/Users/bogo/Developer/Go/bin/minio-v0.0.0-20200527010300-cccf2de129da] Error 2

After the upgrade, the errors stop happening:
bogo@Bogos-MacBook-Pro ~/D/thanos (upgrade-bingo-minio)> make test
(re)installing /Users/bogo/Developer/Go/bin/minio-v0.0.0-20201125204248-91130e884b5d
# github.com/shirou/gopsutil/cpu
../../Go/pkg/mod/github.com/shirou/gopsutil@v2.20.9+incompatible/cpu/cpu_darwin_cgo.go:13:5: warning: 'TARGET_OS_MAC' is not defined, evaluates to 0 [-Wundef-prefix=TARGET_OS_]
# github.com/shirou/gopsutil/disk
iostat_darwin.c:28:2: warning: 'IOMasterPort' is deprecated: first deprecated in macOS 12.0 [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:132:1: note: 'IOMasterPort' has been explicitly marked deprecated here
# github.com/shirou/gopsutil/host
smc_darwin.c:75:41: warning: 'kIOMasterPortDefault' is deprecated: first deprecated in macOS 12.0 [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:123:19: note: 'kIOMasterPortDefault' has been explicitly marked deprecated here
(re)installing /Users/bogo/Developer/Go/bin/prometheus-v2.4.3+incompatible
go: finding module for package github.com/oklog/oklog/pkg/group
go: finding module for package github.com/go-kit/kit/log/level
go: finding module for package github.com/mwitkow/go-conntrack
go: finding module for package github.com/pkg/errors
go: finding module for package github.com/go-kit/kit/log
go: finding module for package gopkg.in/alecthomas/kingpin.v2
go: finding module for package gopkg.in/yaml.v2
go: finding module for package golang.org/x/net/context
go: finding module for package golang.org/x/net/context/ctxhttp
go: finding module for package github.com/opentracing/opentracing-go
go: finding module for package github.com/gogo/protobuf/proto
go: finding module for package github.com/golang/snappy
go: finding module for package golang.org/x/time/rate
go: finding module for package github.com/opentracing-contrib/go-stdlib/nethttp
go: finding module for package github.com/prometheus/client_model/go
go: finding module for package golang.org/x/net/netutil
go: downloading golang.org/x/net v0.0.0-20220526153639-5463443f8c37
go: finding module for package google.golang.org/grpc
go: finding module for package github.com/hashicorp/consul/api
go: finding module for package github.com/aws/aws-sdk-go/aws
go: finding module for package github.com/aws/aws-sdk-go/aws/credentials
go: finding module for package github.com/aws/aws-sdk-go/aws/credentials/stscreds
go: finding module for package github.com/aws/aws-sdk-go/aws/ec2metadata
go: finding module for package github.com/aws/aws-sdk-go/aws/session
go: finding module for package github.com/aws/aws-sdk-go/service/ec2
go: finding module for package gopkg.in/fsnotify/fsnotify.v1
go: downloading github.com/hashicorp/consul v1.12.1
go: finding module for package golang.org/x/oauth2
go: downloading github.com/aws/aws-sdk-go v1.44.24
...

@bwplotka this is my first time using https://github.com/bwplotka/bingo and I noticed that after I executed bingo get github.com/minio/minio@91130e884b5df59d66a45a0aad4f48db88f5ca63 it changed the .gitignore and all this .sum files became untracked, so I committed all of them! Is this expected?

Good question, crossposted that on slack as well (#5394 thanos-dev)

Yes, it's ok to bring those .sum in (: we changed bingo to keep them as it's useful for security checksum reason

Circle CI is flaky, do you mind repushing a commit? I cannot even restart it

@bwplotka done :)

Looks like something is pending but I am not sure what 🤔

Yeah, CircleCI is still pending :disappointed: Not sure what's up. Maybe trying closing / re-opening PR?

Hmm, I am guessing that the "create pull request" or some other webhook failed to be sent to CircleCI, causing this check to be pending forever... there is also no build related to this PR on CircleCI. I will try to open a new Pull Request using the same branch

@thanos-io/thanos-maintainers any ideas what we could do here to unblock? Should someone else open a PR from this branch and see if this somehow related to a first-time contributor? I'm out of ideas.

I think I solved the problem by login into CircleCI using my Github user... not sure why this stopped the build from running before though


Bug in "dita-utilities.xsl" getVariable when called from string context

There seems to be a bug in the official DITA-OT2
If getVariable is called as follows ...
    <xsl:variable name="$myNode" select="." as="node()"/>
    <xsl:analyse-string select="..." regex="{'something'}">
        <xsl:matching-substring>
           <xsl:call-template name="getVariable">
               <xsl:with-param name="id" select="'Chp'"/>
               <xsl:with-param name="params" select="$myNode""/>
           </xsl:call-template>
        </xsl:matching-substring>
    </xsl:analyse-string>

then the compile breaks because in xsl\common\dita-utilities.xsl
    <xsl:template name="getVariable">

... issues ...
        <xsl:sequence select="dita-ot:get-variable(., $id, $params)"/>

... which issues (.) as the first parameter. But (.) in the context 'matching-substring' is of xs:string and the compile breaks because dita-ot:get-variable expects a node as first parameter
The fast fix here could be
<xsl:template name="getVariable">
    <xsl:param name="id" as="xs:string"/>
    <xsl:param name="params" as="node()*"/>
        <xsl:choose>
            <xsl:when test=". instance of xs:string">
                <xsl:sequence select="dita-ot:get-variable($params, $id, $params)"/>
            </xsl:when>
            <xsl:otherwise>
                <xsl:sequence select="dita-ot:get-variable(., $id, $params)"/>
            </xsl:otherwise>
        </xsl:choose>
  </xsl:template>

but a better fix might be thought of

We wouldn't want the getVariable parameters themselves to be the context. That said, I could see the usefulness adding a parameter that provides the context (which is used to determine the language).
That is, we could add a $ctx parameter that defaults to the current node, but allows you to pass in a context node if calling getVariable from an unsupported context. The $ctx parameter in the function call would become the $ctx variable in the dita-ot:get-variable function, so that lines up nicely. The two uses I can see for this:

When calling from an unsupported context (such as a string), this provides a way to set the context so the function can still find a language and find a string
From any context, I think this would provide a mechanism to override the language, by passing in something like <node xml:lang="fi"/> (though I'm not sure how useful this would be outside of a test scenario).

This seems to work for me - language retrieval still works from current node and ancestor node:
<xsl:template name="getVariable">
    <xsl:param name="id" as="xs:string"/>
    <xsl:param name="params" as="node()*"/>
    <xsl:param name="ctx" as="node()" select="."/>
    <xsl:sequence select="dita-ot:get-variable($ctx, $id, $params)"/>
  </xsl:template>

I also tried calling this while passing in a node to reset the context - this retrieved a Russian string, and would work from any context (string context or anything else):
<xsl:with-param name="ctx" as="node()"><dummy xml:lang="ru"/></xsl:with-param>

Thanks to both of you for this efficient solution !


PIXI.blendModes.ADD not working correctly in WebGL with transparent background

Using v2.0 but also had this problem when using v1.6.
This applies if you have a transparent canvas with no solid display objects between the webpage and the blended children. (The children have transparent backgrounds).
If you alter the alpha of a display object while its blend mode is set to ADD you can see the objects bounds over the top of other children, as can be seen in the following image:

I have also made a pen to demonstrate the behaviour:
http://codepen.io/davidhartley/pen/oFbiL
This behaviour only applies to WebGL and not canvas and only seems to affect the ADD blend mode which makes me believe it is something to do with the destination alpha used in the WebGL render.
I am currently using PIXI.blendModes.SCREEN instead for the time being as this produces a similar effect to ADD but without this bug.

Hey there! Been looking into this and seems that theres not much that can be done with the ADD blend mode working correctly with transparency :/
Hopefully SCREEN will be good enough for you needs ?


Refactor tastyapi package

As mentioned in #1416 we do no longer use parts of the tastyapi package. That made me work on refactoring it completely as I think that the api client code should live next to it's server code. That way once we completely moved away from API v1, we can just ditch the api package and we are set.

I'm a little late but :+1:


Syntax highlighting in VSCode

Just as subject says: We should make ".l" files have proper syntax highlighting in VSCode editor.

I would like to work on this issue. I've noticed that we have a syntax highlighting configuration for vim, but it doesn't look complete enough as a grammar description. Do we have a formal description of the grammar of Logica yet?

@EricWay1024 just curious, are you planning to go the VS Code direct API route or the Language Server Protocol route(https://code.visualstudio.com/api/language-extensions/language-server-extension-guide)

@EricWay1024 This is awesome! I'll post a formal syntax description by the end of this work week.

@EricWay1024 just curious, are you planning to go the VS Code direct API route or the Language Server Protocol route(https://code.visualstudio.com/api/language-extensions/language-server-extension-guide)

@RAbraham As this issue is only concerned with syntax highlighting which is a declarative language feature and is defined in configuration files, for now I plan to first work on writing Logica syntax in TextMate grammars (as is described here). So at this stage I haven't considered which approach to take when developing programmatic language features. Any suggestions?

@EricWay1024 This is awesome! I'll post a formal syntax description by the end of this work week.

OK, thank you for your help.

@EricWay1024 textmate grammar sounds good!
re: programmatic language features. If you have the time and interest, the Language Server Protocol has the benefit that we do it once and we can reuse it across different editors(e.g. Vim, PyCharm and VSCode) and not just VSCode. On the flip side, it 'may' be more complex than the VS Code API.
Caveat, I haven't done this before but that would be the direction I would consider if I had the time to help.

@EricWay1024, I've added a BNF syntax specification in dev branch:
https://github.com/EvgSkv/logica/blob/dev/docs/syntax.md
Let me know if you have any questions, or note any problems with it.

Also, @EricWay1024 would you mind singing Google's CLA, so we can accept your contributions?
Please see https://github.com/EvgSkv/logica/blob/main/CONTRIBUTING.md for details.

@EvgSkv Thank you for your work! I've signed Google's CLA now.
Should I create a new repo for this VS Code extension or put everything in some folder in this repo?

Thanks for signing it, @EricWay1024!
I've moved the VIM files to a new syntax folder.
It would be great if you could put the VSCode files into a sub-folder of syntax.
I don't know how VSCode syntax highlighting works, but it looks like implementing the whole parsing there could take quite a bit of time. Having just basic highlighting of predicates/variables/numbers/strings/operators etc, like it's done in current VIM would definitely be a great start.
In anyway, thank you very much for looking into this! I am looking forward to using VSCode for my logical programs! :-)

@EvgSkv OK, I see. I'll be working on the basic highlighting first. I'll submit a pull request once this is finished, hopefully in several days. :smiley:

Thanks to @EricWay1024 work Syntax Highlighting is available in VS code!
Closing the issue as fixed!


fix: bump version and respect relative path

:tada: This PR is included in version 1.5.4 :tada:
The release is available on:

GitHub release
1.5.4
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Updating data & options

So from what I've read, it seems with the use of chartjs 2.0+, chart.js should just automatically determine what data values have changed and then animate the change to those new values (rather than doing the entire initial load animation).
Similarly, from chartjs 2.5+, the same should occur with options.
Using ember-cli-charts with 3.3.0 should have both of these features since it uses chartjs 2.6.
Due to this new feature, updating data/options in ember-cli-chart has been simplified down to essentially just
chart.config.data = data;
chart.config.options = options;
chart.update();

However, at least for me, it seems that it doesn't work at all. When some value in data changes, it replaces the entire chart.config.data with the new data which causes the animation to reload from the beginning (rather than just animating the changed value).
Similarly, changing a single option and then replacing the entire chart.config.options actually doesn't seem to apply the new options at all.
The following example snippets work though, if they are placed in the update chart function of ember-cli-chart instead of the existing  chart.config.data = data; and chart.config.options = options; statements;
Changing data (example, works)
myChart.config.data.datasets[0].data = [36, 19, 3, 5, 2, 3];

Changing options (example, works)
myChart.config.options.legend = {
    display: true,
    position: 'bottom'
};

or
myChart.config.options.legend.position = 'bottom';

Am I missing something here? Is data/options changing working for anyone else without having to resort to modify the individual datasets/options?
Thanks

I experimented with their live demo here: http://www.chartjs.org/samples/latest/charts/pie.html
Replacing the data object as a whole doesn't work. If you copy the object, modify it and then assign it again then it will work ... which defeats the purpose. I suggest creating a ticket in the chartjs repo.

Thanks, will do.
For the moment, to get the data change animation to work properly, I am just overriding the ember-cli-chart updateChart() function and doing the following
updateChart: function() {
	...
	if (chart.config.data && chart.config.data.datasets && chart.config.data.datasets.length > 0) {
		for (var i = 0; i < data.datasets.length; i++) {
			Object.keys(data.datasets[i]).forEach((key) => {
				chart.config.data.datasets[i][key] = data.datasets[i][key];
			});
		}
	} else {
		chart.config.data = data;
	}
	...
}

But this is obviously inherently unreliable and I thought this was what chartjs 2.0+ was supposed to avoid...

@aomran How do I get the chart instance in Ember to call update() on it?
I'm looking at these examples https://jsfiddle.net/red_stapler/u5aanta8/1/
where they do
var myLineChart = Chart.Line(canvas,{
	data:data,
  options:option
});

and then do something like
myLineChart.data.datasets[0].data[7] = 60;
myLineChart.data.labels[7] = "Newly Added";
myLineChart.update();

Just wondering what is the ember equivalent for this or if you can point me in the right direction

Hi @tchan ,
If you have chart data defined like this
chartdata: {
	labels: ["January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", "December"],
	datasets: [{
		label: "DFM Alerts",
		backgroundColor: "rgba(255,99,132,0.2)",
		borderColor: "rgba(255,99,132,0.8)",
		data: [65, 59, 80, 81, 56, 55, 40, 10, 57, 105, 39, 56]
	}, {
		label: "TPMS Alerts",
		backgroundColor: "rgba(54,162,235,0.2)",
		borderColor: "rgba(54,162,235,0.8)",
		data: [28, 48, 40, 19, 86, 27, 90, 32, 26, 49, 41, 5]
	}]
}

And an ember-chart declared like this
{{ember-chart data=chartdata}}

And you then need to modify that data, do it like so..
var cdata = this.get('chartdata');
cdata.datasets[0].data[7] = 60;
cdata.labels[7] = "New August";
this.set('chartdata',cdata);

This will then trigger an observer in the ember-chart, which will set the data and then call update() for you
See here;
https://github.com/aomran/ember-cli-chart/blob/master/addon/components/ember-chart.js#L32-L39
Unfortunately this method of updating the data will cause a full refresh/redraw of the graph, (which is what this github issue is about) - in which case you then need to override updateChart() like I have above (but worry about this when you have the update working first)
Hope that helps!

@tchan yeah you could subclass and implement your update function. I've gone down that road before, and unfortunately, the code gets messy when trying to do this for all chart types. This library is a small wrapper around the Chartjs project -- if anyone has a fix for the update issue then, please contribute upstream to that project. It would be good not to have to mutate every data point manually.

Yeah, I can't get the update working... :(
This is my data parameter where I initialize the data array as []
  actionTypeData: computed('labels', 'data', function() {
    return {
      labels: get(this, 'labels'),
      datasets: [{
          backgroundColor: ['#60C0DC', '#EEAC57', '#5FB760', '#D75452'],
          borderWidth: 1,
          data: []
      }]
    };
  })

I then have a computed function (sorry it's a bit shit) that gets data from an api call, and pushes the values into the original data array but it doesn't seem to be updating.
  data: computed(function() {

    let _this = this;
    let actionTypeData = get(this, 'actionTypeData');
    // console.log('actionTypeData', actionTypeData.datasets[0].data);
    let data = actionTypeData.datasets[0].data;
    let ajax = get(this, 'ajax');
    let promise = ajax.request(`/api/bison/reporting/action/1/`);
    var model = PromiseArray.create({ promise });
    let arr = [];
    model.then(function(item) {
      // console.log('item:', item);
        item.forEach(function(action) {
          // console.log('action', action);
          actionTypeData.datasets[0].data.push(action.cnt);
        });

        // console.log('actionTypeData', actionTypeData.datasets[0].data);
        _this.set('actionTypeData', actionTypeData);
        // console.log(actionTypeData);
        return arr;
    })
  }),

Show me your line in handlebars?
Something like {{ember-chart ... }}
Assuming it's set like {{ember-chart data=actionTypeData}}, and you're definitely sure that the computed function data is being called, try doing a this.set('actionTypeData',null) and then setting this.set('actionTypeData',actionTypeData) - see if that works. Just trying to make sure the updateChart() observer is being called.

@Techn1x  That did the trick. I had something silly instead... apologies

No problem at all, glad it worked in the end

@Techn1x have you had any issues for your charts not redrawing/updating since the 2.7 release of chartjs?

Hmm, not entirely sure what has broken here or why. Not currently in a position to check my own webapp at the moment to see if it updates either.
If you need it to work though, first update ember-cli-chart to 3.3.2 (this swaps from using observers to using didUpdateAttrs() component lifecycle hook which should be better)
Now I noticed that for some reason in the twiddle, even after going to 3.3.2, didUpdateAttrs() isn't being called automatically when you set the new testData, this could be because it's technically the same object I guess? (not sure) but if you want to fix it, add the line this.notifyPropertyChange('testData'); after you do the this.set('testData',cdata);. This will fire the didUpdateAttrs() hook and cause the chart to update

How strange. It causes the update but I'm also after the animation just for the user experience. Also interested to know if your web app was affected, please keep me updated (if you remember :) )

3.3.2 also introduced an animate attribute on the ember-chart component (by default it's false)
So also set animate=true like so;
{{ember-chart type='pie' data=testData height=300 width=300 options=options animate=true}}

We got same error in our project. I checked docs for chart.js and found where issue comes from.
Here is link to PR implemented what we want:
https://github.com/chartjs/Chart.js/pull/3587
Here is whole update function from that PR:
function updateConfig(chart) {
+		var newOptions = chart.options;
+
+		// Update Scale(s) with options
+		if (newOptions.scale) {
+			chart.scale.options = newOptions.scale;
+		} else if (newOptions.scales) {
+			newOptions.scales.xAxes.concat(newOptions.scales.yAxes).forEach(function(scaleOptions) {
+				chart.scales[scaleOptions.id].options = scaleOptions;
+			});
+		}
+
+		// Tooltip
+		chart.tooltip._options = newOptions.tooltips;
+	}

So if we want to explain Chart.js to refresh it we need update chart.options variable instead of chart.config.options variable which ember-cli-chart set when we provide new data to it.
P.S. i will implement fix for it. but don't know how much time it will take for me.


Add loong64 support

This patch adds support for loong64 architecture. I am forwarding it from a bug report submitted to Debian. It has been applied in a patch for Debian also.

I have added this patch in dev branch. see https://github.com/xmake-io/xmake/pull/4569


It doesn't work

I try to search something like "se#/x" without the "#/" and still got adult result

I know it's being very late now. But I will look into it now


473 Create hold to delete photo interaction

#473 - put wrong issue # in branch by accident

[x] Remove existing delete buttons from PhotoPreview
[ ] Add the trash icon to the icon font
[x] When the user long-presses on a thumbnail, show delete buttons over all the thumbnails; buttons should be translucent to show the photo behind them but they should cover the whole thumbnail so the entire area is tappable
[x] When the user taps a delete button, delete the photo immediately
[x] Tapping anywhere other than one of the delete buttons should exit deletion mode, i.e. the buttons disappear and the thumbnails appear as they did before

https://user-images.githubusercontent.com/13311268/218353123-709f4f5c-c0cd-4bc9-a6fd-3f3c7c04de11.mov
Other usages of PhotoCarousel persist

@jtklein can do, originally had to do that because of the modal but realized taking out the modal was part of the spec. Can revert this.


No producers configured! Please add producer IDs and private keys to configuration.

Yesterday is ok.
After checkouting the latest in the master ,today it tell me:
3035677ms thread-0   producer_plugin.cpp:175       plugin_startup       ] No producers configured! Please add producer IDs and private keys to configuration.
At the same time, the file--config.ini didn't create by auto.

I find it:
./nodeos -e -p eosio --plugin eosio::wallet_api_plugin --plugin eosio::chain_api_plugin --plugin eosio::account_history_api_plugin

how to config? I have   the  same problem

./nodeos -e -p eosio --plugin eosio::wallet_api_plugin --plugin eosio::chain_api_plugin --plugin eosio::account_history_api_plugin
or
modify  /Users/xxx/Library/Application' 'Support/eosio/nodeos/config/config.ini

I find that this only fixes the problem for a clean install and if you don't stop nodeos from running it causes error  https://github.com/EOSIO/eos/issues/2142.


Merge the core services

Unfortunately, splitting the auth- and resource-server didn't really work out. Especially in view of the migration to a standalone application (#5), it makes sense to just have 1 artifact. Other reasons are:

The communication between auth- and resource-server increases the overall complexity and introduces a bottleneck within the system
Both services are tightly coupled by design, leaving a split questionable
The core OSIAM services should feel like "one thing" not a distributed system in itself
Versioning is sometimes confusing
Building, testing and deploying is more complex than necessary
Documentation, issues and other information is scattered across multiple repos

This list makes no claims of being complete.
I'd also suggest, that we merge the functionality of addon-self-administration and addon-administration into the core, too. But I would leave that for the future.
As splitting once had a use case, namely operating the user-facing auth-server part on a public interface, but hide the resource-server part in a private network, we should think about

whether we still want to support this use case
how we want to implement it

To answer 1.: I don't think so. After all, controlling access is OSIAM's business, so there should be no harm in having the resource-server's endpoint publicly available. They're secured with OAuth anyway. I'm also not aware of that anyone is operating OSIAM like this. One can still simulate this "feature" by putting OSIAM in a private network and reverse proxying just the auth-server endpoints, or something like that.
We should put this on the 3.0 Roadmap, as it is a major breaking change.

I've started to implement this (https://github.com/tkrille/osiam-osiam/tree/merge-servers), but have a question:
Should we remove the creation of data (admin user, example-client, etc.) from the Flyway migrations and rather create them on the first start, i.e. when no data is contained in the database. Remember, we can now have a fresh start of this.

I like your work on that very much and fully agree with you on all the points raised. Thank you for working on it. I like the idea of getting rid of using flyway to initially creating data and move that to the first start of the application.

I also like your work and mostly agree.
One point is missing:
When the auth- and resource-server are merged, we can migrate to BCrypt hashes.

I'd also suggest, that we merge the functionality of addon-self-administration and addon-administration into the core, too. But I would leave that for the future.

I don't think that's a good idea, but like you said, let's discuss this later.

Should we remove the creation of data (admin user, example-client, etc.) from the Flyway migrations and rather create them on the first start, i.e. when no data is contained in the database.

Yes, good idea. Later we should make this configurable. Maybe just switch it on or off or make the data configurable via yaml. I think the use case is that a customer wants an easy customization of the data within they install process.

When the auth- and resource-server are merged, we can migrate to BCrypt hashes.

I've incorporated this in my description, thanks.
Ok, then we remove the creation of example data via Flyway. I'll create a separate issue for this.


Android + select2 v3.4.5 dropdown wrong position

Good day.
We found a bug with select2 plugin in mobile device.
Device: Samsung Galaxy S4, Android 4.4.2, Chrome;
Bug: http://www.screencast.com/t/TWVqKvUgb
As you see after click on select Browser showing keyboard and select dropdown disappear.
Also checked on iPhone 5s — it's fine. Is it possible to fix it via update to 4.0 version?
Thanks

The dropdown should be positioned properly in Chrome in Select2 4.0.0.
Unfortunately we no longer support Select2 3.4.5.

I have the same problem but in Android 5.+


chore: fix some comments

0x17427ec1e97102973a713b7e33b8766409f6fc92

https://www.coingecko.com/en/portfolios/public/BAh7BjoRcG9ydGZvbGlvX2lkaQOxOME=--4926f8b4f2a17458ab27e24148f4ba68d7e449ef


Fix app JSPM client baseUrl

The "file://" URL handler requires the full path to the html file. Before
this commit, this was accomplished by modifying the jspm-generated
config.js file. It was necessary to do it every time jspm init/install was
run, as config.js does not support dynamic values.
This commit fixes this issue by setting the client baseUrl to "." in the
jspm init wizard. As a result, client baseUrl is preserved by jspm.

thx, as mentioned in the comments on my blog


vcfsort and bedpesort are probably broken when not used on a stream

Looks like specifying an output file and no input file will probably result in the program trying to read the output file. Check this and fix if necessary.

Nothing really needed to change as the arguments in the svtools wrapper were positional. Updated documentation.


Catch more cases where a rust keyword in schemas or queries would break code generation

Depends on #253
Depends on #258
Fixes #255
Fixes #256
Catch more cases where a rust keyword in schemas or queries would break code generation. This includes variables, Inputs, enum fields, response fields. Adds integration test (keywords_query.graphql+keywords_schema.graphql).
This PR makes the following schema possible (contains rust keywords and doesn't work right now):
"""The top-level Query type."""
type Query {
  """Keyword type"""
  search: Self
}

"""Keyword type"""
type Self {
  """
  A keyword variable name with a keyword-named input type
  """
  transactions(struct: extern!): Result
}

"""Keyword type"""
type Result {
  """Keyword field."""
  for: String
  """dummy field with enum"""
  status: AnEnum
}

"""Keyword input"""
input extern {
  """A field"""
  id: crate
}

"""Input fields for searching for specific values."""
input crate {
  """Keyword field."""
  enum: String

  """Keyword field."""
  in: [String!]
}

"""Enum with keywords"""
enum AnEnum {
  where
  self
}

I fixed the merge conflicts and already merged the commit about renaming rust keywords (thanks!).
Next step is to look at this PR and https://github.com/graphql-rust/graphql-client/pull/257 to figure out the best way to normalize the generated query struct names when generating from the CLI.

https://github.com/graphql-rust/graphql-client/pull/257 was merged, so since the rust keywords renaming is already merged, I think we can close this PR :)


GKrellM - New Theme

Hello team!
I created a theme for GKrellM. I've enjoyed using it, and thought maybe the community would like it as well.
Here's the repository: https://github.com/timsan7sk/Dracula
--
Best regards,
timsan

Hey, that's very cool! ✨
I just sent you an invitation to join the organization.
I also cloned your repository for Dracula's organization, so you can go ahead and delete or archive yours:

Your repository.
New repository.

Thanks for building this! 🎉


Out of process JSRuntime support

Replaces all usages of IJSInProcessRuntime to IJSRuntime with true async calls to js.
Fixes #9

LGTM


Minor typo in comments

Minor typo in the comments on IdentityUser and IdentityRole

Linked to https://github.com/aspnet/Identity/pull/1161

Merged.


Replace the notions of inputs and outputs with fulfillments and conditions

In a comment on issue https://github.com/bigchaindb/bigchaindb/issues/626#issuecomment-256020754 , @r-marques wrote:

This is a good step to probably replace the notion of inputs and outputs with fulfillments and conditions

The mission, therefore, is to grep through all the code and documentation, and to:

replace all mentions of (Bitcoin-style) "output(s)" with "condition(s)"
replace all mentions of (Bitcoin-style) "input(s)" with "fulfillment(s)"

Note: This is not as easy as it might seem. The words "output" and "input" might be used in other contexts where we don't mean Bitcoin-style outputs or inputs (i.e. conditions or fulfillments in BigchainDB). For example:

Susan phoned and asked me for my input.

Don't change those ones.
Related phrases are "spending an output" or "unspent outputs." That's a cryptocurrency-specific phrase. In BigchainDB, one doesn't "spend an output," one "fulfills a condition" (a txid+cid pair). Therefore, a third thing to do is:

replace all phrases such as "spends an output" with "fulfills a condition". Some methods and exceptions should be renamed accordingly. If you like, you can create a new issue for this chore but it makes sense to tackle it at the same time as the other two, because occurrences will be in the same neighborhood as "inputs" and "outputs."

Proposal
This proposal addresses both this issue and #626 .

[ ] Replace all notions of inputs and outputs in the documentation with fulfillments and conditions like @ttmc proposed above.
[ ] Replace all notions of inputs and outputs in the code with fulfillments and conditions
[ ] Replace all occurrences of owners_before and owners_after in the code with simply with public_keys.

Current Condition model
{
    "cid": "<condition index>",
    "condition": {
        "details": {
            "bitmask": "<base16 int>",
            "public_key": "<new owner public key>",
            "signature": null,
            "type": "fulfillment",
            "type_id": "<base16 int>"
        },
        "uri": "<string>"
    },
    "owners_after": ["<new owner public key>"],
    "amount": "<int>"
}

New condition model
{
    "cid": "<condition index>",
    "condition": {
        "details": {
            "bitmask": "<base16 int>",
            "public_key": "<new owner public key>",
            "signature": null,
            "type": "fulfillment",
            "type_id": "<base16 int>"
        },
        "uri": "<string>"
    },
    "public_keys": ["<new owner public key>"],
    "amount": "<int>"
}

owners_after is implicit since its a public key in a condition.
Current Fulfillment Model
{
    "owners_before": ["<public key of the owner before the transaction happened>"],
    "fid": 0,
    "fulfillment": "cf:4:RxFzIE679tFBk8zwEgizhmTuciAylvTUwy6EL6ehddHFJOhK5F4IjwQ1xLu2oQK9iyRCZJdfWAefZVjTt3DeG5j2exqxpGliOPYseNkRAWEakqJ_UrCwgnj92dnFRAEE",
    "input": {
        "cid": 0,
        "txid": "11b3e7d893cc5fdfcf1a1706809c7def290a3b10b0bef6525d10b024649c42d3"
    }
}

New Fulfillment Model
{
    "public_keys": ["<public key of the owner before the transaction happened>"],
    "fid": 0,
    "fulfillment": "cf:4:RxFzIE679tFBk8zwEgizhmTuciAylvTUwy6EL6ehddHFJOhK5F4IjwQ1xLu2oQK9iyRCZJdfWAefZVjTt3DeG5j2exqxpGliOPYseNkRAWEakqJ_UrCwgnj92dnFRAEE",
    "cid": 0,
    "txid": "11b3e7d893cc5fdfcf1a1706809c7def290a3b10b0bef6525d10b024649c42d3"
}

owners_before is implicit since its a fulfillment.
Further simplify and remove input since a fulfillment needs to point to a condition. In the case of a CREATE transaction we can just have cid: null and txid: null.
Further discussion

[ ] We still need a terminology for owners after and owners before for the documentation.
[ ] Possibly replace the entire condition key with only the uri, similar to the fulfillment key

Further simplify and remove input since a fulfillment needs to point to a condition. In the case of a CREATE transaction we can just have cid: null and txid: null.

Would it make more sense to call the dict fulfills rather than flattening it? It's really weird seeing a cid inside a fulfillment.

We still need a terminology for owners after and owners before for the documentation.

From https://github.com/bigchaindb/bigchaindb/issues/626, "previous fulfillers" and "new fulfillers" makes sense, given what they semantically mean.

Possibly replace the entire condition key with only the uri, similar to the fulfillment key

I agree, for the sake of simplifying the condition. Much of the details don't seem to be important, since they're information that can be derived from the condition uri.

Would it make more sense to call the dict fulfills rather than flattening it? It's really weird seeing a cid inside a fulfillment.

I think this is a good idea

Would it make more sense to call the dict fulfills rather than flattening it? It's really weird seeing a cid inside a fulfillment.
I think this is a good idea

I would prefer the flattened version, or some other approach than fulfills and fulfillment as two keys on the same level -- it's confusing. Moreover, it's generally best practice to use complete names, unless there's really an obvious abbreviation that everyone gets. I assume the complete name would be fulfillments. In this case, seeing both fulfills or it's explicit version, fulfillments and fulfillment side by side simply begs for confusion to step in.
But perhaps I am missing some key knowledge with which it would make sense.

Bottom line is a fulfillment needs to point to a condition and a condition is indexed by a txid and cid. Something like: "This fulfills the condition 0 of the transaction with id somehash"

I assume the complete name would be fulfillments

Naw, I meant fulfills as a verb and complete as itself.
But this brings up a good point, rather than condition and fulfillment representing the uris, why not uri (I think @ttmc suggested that earlier somewhere too)?

Naw, I meant fulfills as a verb and complete as itself.

Oh, ok, sorry then. Wrong assumption on my part.
Well, could we use this to decide:
>>> import this
The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

There is "Flat is better than nested.", but here are also other points. I still would prefer "flat". But if someone can convince me using the above zen of python, I would be most happy to change my mind. :smirk

Explicit is better than implicit.
Readability counts.

Oh, well, I find the flat version more readable, simpler, more beautiful, and even more explicit, since the the entire body is a fulfillment.

since the entire body is a fulfillment

Not necessarily true, cid and txid actually make up a TransactionLink object that becomes redundant in IPLD.

IPLD is out of scope for this issue.
Updated the Proposal to address the comments. See Edit 1

:+1:
Very nice proposal. I think it will make the code easier to understand.
I can draft some docs explaining how to interpret public_keys.
@diminator may have some concerns about being able to resolve issue #677 (Add checks to ensure conditions & fullfillments are internally consistent). But that's a separate issue.

@sohkai do you agree with the edited proposal?

@r-marques yep 👏!
(IPLD is out of scope, but without fulfills, we'd have to revisit this issue once we consider implementing it again)

The edited proposal does include the fulfills keys, regardless of IPLD support.
@sbellem, @ttmc and @sohkai agreed so this proposal is frozen and ready for implementation

New condition model

Why is condition.details not in the new condition model anymore?
We cannot remove it, as creating a condition-uri is lossy.

Its currently still there. This is just a proposal

I agree that public_keys is a step forward from owners_[before|after], the only thing I'd submit for consideration is to use the word parties, ie, to be party to a condition/fulfillment, just because it seems to be "nice" terminology, and more suggestive of the nature of the relationship between the list of public keys and the condition/fulfillment.

Why is condition.details not in the new condition model anymore?
We cannot remove it, as creating a condition-uri is lossy.

Good point, we were previously overlooking threshold conditions for the condition model. From what I can tell, condition.details holds either of two types of data:

Details about a ED25519 condition: this is duplicated elsewhere in the new condition model (either in the URI or public_key)
Subfulfillment details for threshold conditions, which we'd lose if we remove condition.details: I'd argue that we should be using something else to model this, rather than details, and I'm not sure how valuable this information is anyway. We still have the public keys of the thresholds, so we'd only be losing their fulfillment types, required feature bitmask, and weights. At the end of the day, cryptoconditions should be able to verify whether or not a condition is fulfilled by a fulfillment from just their URIs so this extra information is only useful for querying.

Is this accurate, @TimDaub / @diminator?

Some of us were chatting about how someone constructing a TRANSFER transaction (or any transaction) must keep in mind two sets of conditions: 1) the conditions that the transaction's fulfillments fulfill and 2) the conditions that subsequent TRANSFER transactions might fulfill. Sometimes we may need language to distinguish those sets of conditions, but maybe not in the code, maybe only in documentation. One idea for names was "incoming conditions" and "outgoing conditions."

One idea for names was "incoming conditions" and "outgoing conditions."

Then we can just use the established lingo in place: Inputs and Outputs (that is btw. recognized in the Blockchain space).
Another thing to consider:
Doublespents

My problem is with input conditions there really are no input conditions.
There are only fulfillments for output conditions.

"Input conditions"

Using conditions here wrong and inconsistent. At least we should aim for the interledger lingo, that is "Input Fulfillments".

Doublespents

keep it - because it resonantes with the problem to solve - independent of the implementation

Sorry but when we're speaking of a single transaction there is:

An "output condition" (the future lock)
An "input condition"/"incoming condition"/to-be-fulfilled-condition/whateverdudeitexists (the lock we're opening in that transaction)
A fulfillment (a key to the "input condition")

Its just a pointer to an output condition with the fulfillment to unlock it

One idea for names was "incoming conditions" and "outgoing conditions."

thanks @ttmc for putting this into writing
I agree with @ttmc's point about the importance of distinguishing between the condition that is being fulfilled and the condition that would need to be fulfilled to consume the transaction.
When you are constructing the payload you do need two conditions, the old one, and new one, or whatever you may want to call them, they are definitely two, and they are definitely different.
I think this is an important part if the payload to think about. Perhaps there are different approaches of using crypto-conditions that could be considered.
As a very rough example of a different approach, the current spec for an ed25519 fulfillment is:
Ed25519FulfillmentPayload ::= SEQUENCE {
     publicKey OCTET STRING (SIZE(32)),
     signature OCTET STRING (SIZE(64))
   }

there is a preface (e.g.: cf) and type (e.g.: 4) in front, so one ends up with a uri like so:
cf:4:7Bcrk61eVjv0kyxw4SRQNMNUZ-8u_U1k6_gZaDRn4r-2IpH62UMvjymLnEpIldvik_b_2hpo2t8Mze9fR6DHISpf6jzal6P0wD6p8uisHOyGpR1FISer26CdG28zHAcK
so what if we added to this protocol a "ledger payload":
LedgerPayload ::= SEQUENCE {
     ledger-id OCTET STRING,
     txid OCTET STRING (SIZE(64))
     cid INTEGER (0..MAX)
}

an example fulfillment would then be:
cf:4:7Bcrk61eVjv0kyxw4SRQNMNUZ-8u_U1k6_gZaDRn4r-2IpH62UMvjymLnEpIldvik_b_2hpo2t8Mze9fR6DHISpf6jzal6P0wD6p8uisHOyGpR1FISer26CdG28zHAcK:bigchaindb-7fde91ebdb05bb49af4e7613647c27cf4e30809efcbae28e6b34e138e0360c76-0


[Organization] Update existing email notifications for organizations

1 - If the target of the email is an organization, updated any reference of you or your account with your organization
2 - If the target of a package ownership email is an organization, the email sends to the admins of the organization and not the organization DL (because org admins are the only users who can handle these requests)
Messaging pending review with @anangaur

Can you take care of this?
https://github.com/NuGet/NuGetGallery/issues/5443

@chenriksson looked into #5443, seems hilariously non-trivial, should be fixed in a separate change


Verifier calculating encodedSessionTranscript

A Holder performing a presentation uses this library's helper functions of the form usingSessionTranscript_____. Under the covers these construct appropriately formed CBOR-encodings of a DataItem using custom extensions to an external CBOR library. Without access to those custom CBOR extensions, how can a Verifier make the same calculation?
I could see two potential solutions:

the library exports its cborEncode function so that verifiers can use it to calculate what the session transcript bytes should be; or
additional helper functions like the usingSessionTranscript_____ on DeviceResponse are added to the Verifier class so that they can be called instead.

+1, there is no need for the verifier to know how to construct the session transcript. We are implementing option 2 for v2 (see https://github.com/auth0-lab/mdl/pull/16)
In the meantime, you need to install cbor-x as dependency (DataItem is already exported by the lib):
import { DataItem } from '@auth0/mdl';
import { Encoder } from 'cbor-x';

const cborEncode = (
  obj: unknown,
): Buffer => {
  const enc = new Encoder({
    tagUint8Array: false,
    useRecords: false,
    mapsAsObjects: false,
    useTag259ForMaps: false,
  });

  return enc.encode(obj);
};

const getSessionTranscriptBytes = (clId: string, respUri: string, nonce: string, mdocNonce: string) => cborEncode(
  DataItem.fromData([
    null, // DeviceEngagementBytes
    null, // EReaderKeyBytes
    [mdocNonce, clId, respUri, nonce], // Handover = OID4VPHandover
  ]),
);

const verifier = new Verifier(ISSUERS_CERTIFICATES);
await verifier.verify(encodedDeviceResponse, {
  encodedSessionTranscript: getSessionTranscriptBytes(clientId, responseUri, verifierGeneratedNonce, mdocGeneratedNonce),
});


Request to add a new paper

Hi, may I ask if it is possible to add a new paper related to the real robotics.
Pave the Way to Grasp Anything: Transferring Foundation Models for Universal Pick-Place Robots Paper
Thanks a lot!

Hi Jiange, we have added your amazing paper to our list.

Hi Jiange, we have added your amazing paper to our list.

Thanks!


fix: cookies() .set() reflect priority attribute into set-cookie

Closes https://github.com/vercel/next.js/issues/56848
This PR provides the fix for cookies() .set() to reflect the priority attribute into set-cookie
RE: @balazsorban44's comment and request change on https://github.com/vercel/next.js/pull/56850 Pull Request:
"Thanks for the PR, the @edge-runtime/cookies package is an upstream dependency, meaning it should be addressed there first, could you open these changes there, so we can bump the package here to incorporate it?
See https://github.com/vercel/edge-runtime/blob/main/packages/cookies/src/serialize.ts#L16"

Thanks, @renchris, could you run pnpm changeset in the root of the repo and follow the instructions? This can be a patch, so you'll end up with something like

Thanks, @renchris, could you run pnpm changeset in the root of the repo and follow the instructions? This can be a patch, so you'll end up with something like

Okay, I ran the pnpm changesetcommand in the root of the repo and follow the instructions. I commited the returned markdown being at edge-runtime/.changeset/fifty-eagles-invite.md
---
'@edge-runtime/cookies': patch
---

fix cookies() .set() to reflect the priority attribute into set-cookie


Help with my config file

Hi there,
I have just setup cabernet and through trial and error managed to get it working great with Pluto TV.
SO i took the next step and adde daddylive.
The Channel list is working fine oon TVHeadend but i cant for the life of me get the EPG to work.
Here is my config file
`[loggers]
keys = root
[logger_root]
level = DEBUG
handlers = loghandler
[handlers]
keys = loghandler, filehandler
[formatters]
keys = extend,simple
[handler_filehandler]
enabled = False
level = INFO
formatter = extend
class = lib.common.log_handlers.MPRotatingFileHandler
args = (os.getenv('LOGS_DIR','data/logs')+'/cabernet.log', 'a', 10000000, 10)
[handler_loghandler]
enabled = True
level = DEBUG
class = StreamHandler
formatter = extend
args = (sys.stdout,)
[formatter_extend]
format = %(asctime)s-%(levelname)s:%(module)s %(message)s
[formatter_simple]
format = %(levelname)s:%(module)s %(message)s
[main]
uuid = D4F0F08C-3204-11EE-B9F2-A01D48C75C55
maintenance_mode = False
[tvguide]
enabled = True
[epg]
genre = tvheadend
epg_prettyprint = True
[tvguide_default]
label = TVGuide Instance
enabled = True
[hdhomerun]
hdhr_id = 105D13F2
[daddylive]
hdhr_id = 10568DA3
enabled = True
epg-plugin = ALL
[daddylive_default]
label = DaddyLive Instance
enabled = True
epg-plugin = ALL
channel-import_groups = False
player-enable_url_filter = False
epg-enabled = True
channel-start_ch_num = 2000
[tvguide_daddylive]
label = TVGuide DaddyLive
enabled = True
[plutotv]
hdhr_id = 105059A4
enabled = True
epg-plugin = ALL
[plutotv_default]
enabled = True
label = PlutoTV Instance
epg-plugin = ALL
channel-thumbnail = colorLogoPNG
epg-enabled = True
channel-start_ch_num = 1000
[tvguide_plutotv]
label = TVGuide PlutoTV
enabled = True`
Any Idea what im doing wrong?
`

Try checking out the 'beginner setup' thread. I think the daddylive EPG and other various other configuration info is discussed there.
https://github.com/cabernetwork/cabernet/issues/78#issuecomment-1504244835

duplicate of #78

Thank you.
I did look at that thread originally but i missed that comment about the tvguide.
After uninstalling the plugin, reinstalling and leaving daddylive at the default chnnel numbers its now getting the EPG.
One thing i did notice was it only has EPG data for the US channels only. Im guessing that is beacuse tvgiode epg plugin is US based?
Any way of getting UK EPG data?
Can you create a copy of the tvgiuide plugin and edit the json file to reflect tvguide.co.uk and add this as a second EPG plugin?


Add some space before team name and border of table

In the screenshot, "jon jake" is too close to the start of the table. Add some space between the table left border and the name of the team.

can i take this on @jportella93 ?

For sure :)

I want to do this? @jportella93

@MuhammadTanveer94 sure!


ClientModel: Improve APIs on ResponseBufferingPolicy

We removed all the static getters and setters in favor of public properties on message -- I think these APIs are pretty simplified now.


How to make choice prefer the first parser?

I'm trying to parse a simple tag-like language, for example foo{{x}}bar would be a valid input. I tried using choice to parse this, like so:
let tag = any().map(Token::Verbatim).repeated();
choice((
    tag.delimited_by(just("{{"), just("}}")).map(Token::Tag),
    any().map(Token::Verbatim)
))

However, this also parses {{ as two verbatim characters, instead of as a tag delimiter. How can I make choice prefer the first parser?

choice (and or) will always try the parsers in the order that they appear.
The problem here is that any().map(...).repeated() will accept any character, any number of times, and hence will always succeed and consume all remaining input in the process.
You probably want to use none_of('}').map(Token::Verbatim).repeated() instead, or the take_until parser if you want to allow singular braces.

Oh ok I see - but that's a problem. If a {{ appears in the input, I must ensure it always takes the first parser, even if there's no matching }} (that would be an error, not a valid input).

Do you want a {{ without a corresponding }} to be an error?

Yes, exactly. Like {{ is always an opening delimiter, and no }} should be a missing closing delimiter

just("{{").ignore_then(take_until(just("}}"))) is probably what you want in that case.

Ok so I tried to use this code instead of the delimited_by code:

Ok so I tried this instead of delimited_by:
fn group<T>(
	begin: &'static str,
	end: &'static str,
	parser: impl Parser<char, T, Error = Simple<char>>
) -> impl Parser<char, T, Error = Simple<char>> {
	just(begin).ignore_then(parser).then_ignore(just(end))
}

Calling it like group("{{", "}}", none_of(['}'])) works but trying to do group("{{", "}}", just("foo")) on input {{bar}} still produces verbatim except I need it to fail parsing.

I'm not really sure what to say. The code you gave wouldn't parse {{bar}} at all, so the problem must be elsewhere in your parser.

Ok sorry let me give you a full example (the code for Tag will eventually get slightly more complicated but this should do for now):
use chumsky::prelude::*;

fn group<T>(
	begin: &'static str,
	end: &'static str,
	parser: impl Parser<char, T, Error = Simple<char>>
) -> impl Parser<char, T, Error = Simple<char>> {
	just(begin).ignore_then(parser).then_ignore(just(end))
}

#[derive(Debug, Eq, PartialEq)]
enum Token {
	Tag(Tag),
	Verbatim(char)
}

impl Token {
	fn lexer() -> impl Parser<char, Self, Error = Simple<char>> {
		let tag = group("{{", "}}", Tag::lexer()).map(Self::Tag);
		let verbatim = any().map(Self::Verbatim);
		choice((tag, verbatim))
	}
}

#[derive(Debug, Eq, PartialEq)]
struct Tag;

impl Tag {
	fn lexer() -> impl Parser<char, Self, Error = Simple<char>> {
		just("foo").map(|_| Self)
	}
}

fn lexer() -> impl Parser<char, Vec<Token>, Error = Simple<char>> {
	Token::lexer().repeated().then_ignore(end())
}

#[test]
fn parse_tag_foo() {
	let tokens = lexer().parse("{{foo}}").unwrap();
	assert_eq!(&tokens, &[Token::Tag(Tag)]);
}

#[test]
#[should_panic]
fn parse_tag_bar() {
	lexer().parse("{{bar}}").unwrap();
}

#[test]
#[should_panic]
fn parse_tag_foo_unclosed() {
	lexer().parse("{{foo").unwrap();
}

This parses everything that doesn't match all of the parsers of the first choice as the second choice, i.e. accepting all input:
running 3 tests
test parse_tag_bar - should panic ... FAILED
test parse_tag_foo ... ok
test parse_tag_foo_unclosed - should panic ... FAILED

What I want/need/.. (possibly there's another way to express this that I'm not aware of) is to enter the first choice if its first parser matches (the just("{{") one) and then stick with that choice even if later on an error occurs.

let verbatim = any().map(Self::Verbatim);
This parser accepts any character. It appears in a .repeated()  in lexer. Ergo, the parser will always succeed because it can always just repeatedly use verbatim to consume everything.
I guess what you really want is a way to do
any().but_not(just("{{"))
Right now, but_not doesn't exist: but this case (and a few others I've seen recently) are convincing me that maybe it should. I'll try to look into this over this week.

Yes, I see why choice doesn't work for my case. A but_not parser would certainly work here, eventhough an API like the following would appear more "natural" from a user's perspective:
branch(just("{{"))
    .then(Tag::lexer().then_ignore(just("}}")).map(Self::Tag))
    .or_branch(...)
    .or_else(any().map(Self::Verbatim))

I have no idea how hard this would be to implement or if that's at all feasible.

The API you suggest would just do the same think as your current parser though. It's any() that's the issue, it needs to know that it's not allowed to parse {{.

Also, just from a quick look any().but_not(just("{{")) seems a little bit contradicting, as any matches one char and the just matches two chars, but I guess if but_not existed I could modify the parser to accept more than one char at a time if that was required, and if but_not would ensure that any() stopped parsing before it encountered the {{.

I'm wondering whether I can generalise this a bit further, even, to a.and_is(b.not()). You'd read this as "parses a, if it also parses as not being a b".

I'm wondering whether I can generalise this a bit further, even, to a.and_is(b.not()). You'd read this as "parses a, if it also parses as not being a b".

Why not use a.and_is_not(b)? It sounds more natural to me.

Because having separate combinators for and_is and not is more composable, allowing more things to be expressed. For example, none_of(...) now just becomes any_of(...).not().


Move past tiledbsoma 1.11.2 workaround

#157 was necessary in order to complete artifact delivery for 1.11.2.
At head of TileDB-SOMA, the patch there is no longer necessary, and in fact, attempts to apply it break nightlies as at #160.
That said, head as of this moment has at the top of its recipe/meta.yaml
{% set name = "tiledbsoma" %}
{% set version = "1.11.2" %}
{% set sha256 = "e3933c7d7b3d8df59a40ed7833fb20774917f531a915debc76abb569e958a421" %}
...
source:
  url: https://github.com/single-cell-data/TileDB-SOMA/archive/{{ version }}.tar.gz
  sha256: {{ sha256 }}

and this PR (as of the first commit) is failing CI since 1.11.2 does require the patch.
So this repo is trying to serve two masters:

Latest release tag of TileDB-SOMA -- here 1.11.2 -- does need the patch
main of TileDB-SOMA -- nightlies -- has moved past 1.11.2 -- needs to not have the patch, and fails if the patch is present

Second attempt https://github.com/TileDB-Inc/tiledbsoma-feedstock/pull/161/commits/0f5c93dc28a63dc4b625d6987a45a6d86b8a70df

@jdblischak please see https://github.com/TileDB-Inc/tiledbsoma-feedstock/pull/161/commits/0f5c93dc28a63dc4b625d6987a45a6d86b8a70df -- also I updated the description field of this PR (probably while you were replying in the discussion log).

Really up to you. If you can live with red nightly CI until 1.12.0 pre-check, I can ...

This isn't a problem for me in this case because I don't envision it causing us other problems

This is my preference if you're OK with it. I know how to write sed (for 30 years now) but I don't see the one-off PR work as worth the keystroking.

Agreed. I don't think it is worth the effort


What's the reasoning behind this gem?

Hello,
I stumbled upon this gem and wondering, what is the problem that this gem is trying to solve?
Is it to increase Rails security? how? I'd love to understand more and then contribute and write a short wiki maybe as currently there's none.

Hi @ClaudioCarmeli,
The point of this gem is to provide a way to configure and manage security headers in an application while providing safe defaults, validation of header values, and APIs for dynamically changing values. It also provides configuration options for cookies.
It's an extension of Rails' default_headers mechanism with more bells and whistles.
The combination of safe defaults and high configurability is meant to make adoption of the headers a little bit easier.

Thanks fro the offer to update the wiki! I'd be happy to help you with any questions you come across along the way.

@oreoshake Thanks a lot! I'll re-read your answer a couple of times more, ask at work and then send a small PR for you to look at.

@ClaudioCarmeli I'm doing some cleaning and closing this one out. Your wiki additions are always welcome.


How to remove X-Frame-Options: SAMEORIGIN from response header

How to remove X-Frame-Options: SAMEORIGIN from response header
When I'm using ASP.Net 5 RC1 and MVC 6 there is always a X-Frame-Options: SAMEORIGIN in the response header . Unfortunately I have to embed this page in SharePoint. How to remove X-Frame-Options: SAMEORIGIN?
thx
Wolfgang
http://forums.asp.net/t/2082693.aspx?remove+X+Frame+Options+SAMEORIGIN+from+response+header

Are you, by any chance, calling SetAntiforgeryCookieAndHeader anywhere in your views?

There's also a SuppressXFrameOptionsHeader property on the AntiforgeryOptions that you can set to true.

Thanks
Additional info :
https://github.com/aspnet/Mvc/issues/3155 and https://github.com/aspnet/Announcements/issues/34

Thanks @khellang  :+1:


[Version Update] Iris outdated

Is it a mod compatibility issue?
Yes
If it's a mod compatibility issue, please provide the link(s) to the incompatible mod(s)
https://modrinth.com/mod/iris
Minecraft version
1.20.1
Describe the issue
iris updated in the recently and the version check needs updating. should probably also be a warning, not a strict compatability check, so minor version updated dont prevent loading the game and the user is left to decide if there is an issue or not

This mod lock Iris version because this mod uses Iris internal that may break in new versions of Iris (this happened many times at past).
For now, you can use dependency override https://fabricmc.net/wiki/tutorial:dependency_overrides to get rid of the restriction (but it may crash in-game)
Put fabric_loader_dependencies.json into config folder with these content:
{
  "version": 1,
  "overrides": {
    "immersive_portals": {
      "-breaks": {
        "iris": "IGNORED"
      }
    }
  }
}

(I haven't tested that.)

Probably fixed in 3.3.7


regen ouroboros-network/default.nix

Many dependencies removed since consensus was separated.

This is a cabal2nix-generated file.

Merging without review because it's trivial.


QueryResource: Fix incorrect request log start times.

A similar fix is included in #4561 but this patch has been cut down
for the 0.10.1 branch.
Fixes #4655.

@gianm can you just take the startMs directly?
Or does TimeUnit.MILLISECONDS.toMillis(startMs) do something special?

Or does TimeUnit.MILLISECONDS.toMillis(startMs) do something special?

@drcrallen It doesn't do anything special, I removed it.


Update PRT renew requirements

Hi team, as per internal conversations PRT can be renewed externally without being in corp network but as per one customer, windowstransport endpoints are required externally to be able to renew the PRT but as per PG these are not required externally. Please clarify and add the correct information

@rdiazel : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@RavennMSFT please review

@rdiazel pls correct the changes that this is only required for password auth when password is changed. We dont need access to windowstransport endpoints otherwise. If there's a need for discussing this further, let's take this offline

@rdiazel are you planning on making the updates requested?

@rdiazel Please review the requested changes.

I have done the changes requrested. @RavennMSFT  please review if now is ok.

#sign-off

@RavennMSFT: I'm sorry - only the author of this article, @MicrosoftGuyJFlo, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@MicrosoftGuyJFlo signing off on the PR. Please merge

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


validation timeouts and image digest fetch issues in AWS EKS and ECR

We publish and sign container images in AWS ECR using cosign and use latest version of policy controller for validation.
We are running AWS EKS version v1.22.9-eks-a64ea69 with nodes  v1.22.6-eks-7d68063.
Images are signed using AWS KMS keys and verified using public key stored in ClusterImagePolicy.
apiVersion: policy.sigstore.dev/v1beta1
kind: ClusterImagePolicy
metadata:
  annotations:
spec:
  authorities:
  - key:
      data: |
        -----BEGIN PUBLIC KEY-----
        ...
        -----END PUBLIC KEY-----
    name: authority-0
  images:
  - glob: '**'

When deploying large helm charts such as kube-prometheus-stack we often get errors like:
Error: Internal error occurred: failed calling webhook "policy.sigstore.dev": Post "https://webhook.cosign-system.svc:443/validations?timeout=10s": context deadline exceeded

and issues with fetching digests:
invalid value: [<AWS_ACCOUNT_ID>.dkr.ecr.eu-north-1.amazonaws.com/prometheus/node-exporter:v1.3.1](http://<AWS_ACCOUNT_ID>.dkr.ecr.eu-north-1.amazonaws.com/prometheus/node-exporter:v1.3.1) must be an image digest: spec.containers[0].image

Both issues happen at random.
Some tests done:

tried sha256 sum image pining
tried publishing and signing just platform linux/amd64 container image to reduce size of digest
tried scaling to multiple replicas and increasing cpu/memory limits for webhooks but didn't change a thing
checked cloudwatch for performance issues and it looks ok
tried running images manually with kubectl run and worked ok

Any debugging tips much appreciated.

@blazdivjak Thanks for opening this issue. After reading your comment, I assume when you are not deploying other big apps in the same cluster, you don't face any validation issues. Is that correct ?
Does it always fail or it happens sometimes ?
On the other hand I recommend you to use digests instead of tags.

Apps with just one deployment/pod seam to be more stable and work ok.
This failures happen often, but sometimes it just works. I used sha pining / digests but didnt  solve the issue. It reappears after some time.

I'm having the same issue, do you have any solution?

Closing as issue appears to be resolved