Theme doesn't affect anything when selected on atom 0.184.0

When I apply the syntax theme on atom 0.184.0 my file's syntax reverts to the backgrund color of my UI theme (I'm using atom-dark currently).
For example, in a python file this is what I see:

I've tried different languages including HTML, C++ , Javascript, and, of course, Python. I get no syntax highlighting whatsoever.
Atom doesn't report any errors.

Oh, atom reports the theme's version at 2.1.0

Odd, I'll take a look.

Still the same issue with Version 2.1.1

Thanks. 2.1.1 was not intended to fix the atom issues. I am not sure what is going on, I'll have to look around.

Found a solution. I just added a index.less file in the root folder of your theme (material folder) with the following content:
@import "./atom/material-dark/styles/base.less";
Works (at least as a workaround).

Wow! I removed that thinking it wasn't actually doing anything. Goes to show...
Fixed in 2.1.2 via 2398305a3b64bc59e051fec965437eed0d9f45d4

V 2.1.3 works again

Thanks for finding the fix @saschaeggi


docs-bug(mat-calendar): Document mat-calendar component

Documentation Feedback
Please document the mat-calendar component.
Blog posts have been written about this component (e.g. https://onthecode.co.uk/angular-material-calendar-component/) but the official documentation has nothing about the mat-calendar.
Many app designers and developers require for the calendar to be always displayed on the page and don't need to resort to a date picker toggle. Therefore, an official documentation entry would be great.

Duplicate of #15353


Add Docker support.

.NET 6 Preview 4 has issues with the WASM AOT workload which causes the dockerfile to fail.


Add Django Channels consumer

Background
This update adds a Django Channels consumer that works out of the box and also has some configuration options.
Verification
I didn't write any tests. Per the docstring, the out of the box configuration is pretty much as simple as adding path("ws/<str:room>", ChannelsConsumer.as_asgi()), to a list of Django URLs. The easiest way to verify the code is therefore to make a Django app per its docs, set up Django Channels per its docs, add this snippet, and then verify that /ws/<room> serves clients as expected.
Other notes

Not sure how you wanted to handle the dependency?
Tried to follow code standards, let me know if anything needs improvement.

@davidbrochart per discussion on the YJS forum

@davidbrochart did all of the requested changes as requested except the last one but I improved that in a way that you might be happy with. Let me know if you still want me to make that change, otherwise it is ready to merge from my perspective.

@davidbrochart that's funny, I prefer that styling too. I actually only named it this way to try to match with ASGIServer and that sort of thing. Just renamed!


Fix broken jquery url

Thanks!

Thank you for a good job!
wt., 12 mar 2019 o 09:01 Francesco Novy<EMAIL_ADDRESS>napisał(a):

Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mydea/handsontable-chosen-editor/pull/14#issuecomment-471895272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD2RPB42SywfJbdalWqhBe41F59iDVKrks5vV16_gaJpZM4bpq5l
.


Comiple error Afnetworking 3.0 Swift

NSURLSessionDataTask or NSURLSessionTask both are giving same problem . kindly update the document or help me how to resolve it

I have similar issue. Do not know what is the root of the problem but you can help yourself by not specifying some parameter's type, in this case 'error' in POST method call:

    manager.post("http://...", parameters: [:], progress: nil, success: { (operation: URLSessionDataTask, responseObject: Any?) in
        print("Success")
    }, failure: { (operation: URLSessionDataTask?, error) in
        let error = error as? Error
        print("Failure, error is \(error?.description)")
    })


Sonobuoy Scanner displays empty report

Hi!
I tried out the sonobuoy scanner tool on a local vagrant setup of a Kubernetes 1.8.0-rc.1 cluster. The tests finished after about 50 minutes but at the end, the UI showed an empty report.
Could someone have a look?
https://scanner.heptio.com/1edc4542a2ebd2aecce43730f51fecb6/diagnostics/

@charleslieferando Thank you for the feedback!
We're aware of the issue and are working on a fix ASAP.  The common issue we have seen is a condition when a test blocks or times out, which then cascades to cause a sonobuoy timeout.  There are details in the artifacts but we are working on surfacing this up to users.

@charleslieferando @chuckha has updated the landing page if there are issues.  Please let us know if you have issues.

it works! thanks

I just moved my local vagrant setup to AWS and running on Kubernetes 1.8.3. I ran the tests but saw a similar issue...empty results at https://scanner.heptio.com/79d9360dbd18f0f6f24f47cfd6884113/diagnostics/
This time though, I see the server pod from the e2e-tests-prestop-t7l4p namespace stayed running since the test started (5 hours ago).
ubuntu@k8s-master-10-59-16-94:~$ kubectl get pods --all-namespaces

NAMESPACE                 NAME                                   READY     STATUS    RESTARTS   AGE
default                   prometheus-operator-94cc5d5c-7fhrl     1/1       Running   0          10h
default                   wrk-59c4546c4f-btvbm                   2/2       Running   0          9h
e2e-tests-prestop-t7l4p   server                                 1/1       Running   0          5h
istio-system              grafana-8667b7fbfb-6cxjt               1/1       Running   0          9h

Here are the logs from that pod's container
ubuntu@k8s-master-10-59-16-94:~$ kubectl logs --namespace=e2e-tests-prestop-t7l4p server

2017/11/21 14:56:37 Server version: &version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.3", GitCommit:"f0efb3cb883751c5ffdbe6d515f3cb4fbe7b7acd", GitTreeState:"clean", BuildDate:"2017-11-08T18:27:48Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

This to me indicates the e2e tests did not clean up properly. I wonder if they crashed for some reason in the middle of a run?
Is there any chance you captured the sonobuoy pod logs?

Hi. Unfortunately I did not capture the sonobuoy pod logs. I'll rerun the tests and see if the issue occurs again.


Design modification DONE (:

Closed: #9
Before Modification:

After Modification :

DONE Modifications :

Header navigation design fixed
Added new fonts
Added hover effect on the navigation
Active page indication in navigation
Added HTML required validation during blog compose

@PARKHI277 Please correct label meaning hacktoberfest-accepted 'k' is missing

Done


Polestar images for Changeling and Shapeshifter do not match the game

I think TP made some changes to some images that need to re-imported into datacore assets.

You don't like the placeholder hand drawn Odo bucket? 😄
Thanks for the reminder, will force an image update soon and close ticker once done.

thank you.


Upgrade LLVM to latest release

Describe the feature you'd like supported
Use latest LLVM release, but currently optimizations break verification.
Blocked on working with the LLVM bpf maintainers.
Proposed solution
Probably need changes in LLVM per discussion at LSF/MM/BPF.
Additional context
No response

reassigning myself so I remember to send the data to the LLVM maintainer

Sent data to Yonghong Song and discussed at LSF/MM/BPF last week.   He will look into it and see if anything can be done for the next version of clang.  Meanwhile, Jose (gcc bpf maintainer) is interested in possibly using PREVAL inside GCC to guide optimizations, so that is another possible future avenue for a developer.

We should try clang 18 with -O1 (not -O2) as a workaround.


Any plans to support local deployment on Macbook?

Thanks for your work! I find that the inference scripts in UltraChat/UltraLM/inference_cli.py at main · thunlp/UltraChat · GitHub  is still a vanilla one. Do you plan to provide deployment scripts on low-resource devices such as MacBook?

Hi, thanks for your question.
Yes, supporting local deployment on low-resource device is definitely a must-do future work. We are currently focusing on training and releasing larger and better models, though. Later, we will explore the techniques in low-resource deployment for LLMs.


Circuits: wrong display of A-Z termination site

Environment

Nautobot version (Docker tag too if applicable): 1.4.1
Python version: 3.7.13
(tested also on demo instance)

Steps to Reproduce
In Nautobot GUI to to Circuits:

Create a circuit
Add a termination side A (from any site, e,g. AMS01)
Add a termination side Z (from any other site, e.g. SIN01)

Expected Behavior
To see both sites in a overview table of circuits ("/circuits/circuits/`) .
Observed Behavior
Only A termination site is shown (see attached image) (btw. "old" circuits are displayed properly)
If only one termination (either A or Z) is set, then the overview table displays the one site correctly.

Looks like yet another cacheops issue. If I filter the table (changing the queryset being used) the new termination shows up just fine. I suspect that running nautobot-server invalidate all will also fix the issue though I haven't tested this. Tagging #1721.


adding buttons in confirm box

Hello sir i want to know that how can  add 2 or 3 buttons in place or confirm and cancel.

Sorry, Currently only 2 buttons (confirm, cancel) are supported. I'm considering to update the plugin to accept an array of buttons.

+1

+1

This has now been added in v3.
:)

getting lots of problem sir
onloadwff.js:1573 TypeError: Cannot read property 'getElementsByTagName' of null(…)
onloadwff.js:1573 TypeError: Cannot read property 'getElementsByTagName' of null(…)
onloadwff.js:1573 TypeError: Cannot read property 'getElementsByTagName' of null(…)
onloadwff.js:1573 TypeError: Cannot read property 'getElementsByTagName' of null(…)
onloadwff.js:1573 TypeError: Cannot read property 'getElementsByTagName' of null(…)

On 07-Nov-2016, at 7:25 PM, Boniface Pereira<EMAIL_ADDRESS>wrote:
This has now been added in v3.
:)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/craftpip/jquery-confirm/issues/56#issuecomment-258841306, or mute the thread https://github.com/notifications/unsubscribe-auth/AL3kJv1_cEDNKmgVhmKNJYzOc7S8a2b9ks5q7y3rgaJpZM4G1ObO.

I looked into this, its caused while fetching animation-duration property,


proceed_on is always empty

If proceed-on is not set in the gRPC message, it will not be displayed on the list (data is empty in the gRPC request). It is applied properly because when writing to the dispatcher, it is converted to a bitmask and a default mask is used for an empty vector.
Resolves: #157
Signed-off-by: Billy McFall<EMAIL_ADDRESS>

/lgtm
thanks!


✨ Create a curated set of Terraform modules

User Story

As a platform administrator I want a curated set of Terraform modules for Data Platform products to consume
User Type(s)

Platform and Product engineering teams
Value

Product engineering teams can select modules that have been signed off by Platform engineering
Proposal
Build and publish a suite of Terraform modules
Definition of done

[ ] readme has been updated
[ ] user docs have been updated
[ ] another team member has reviewed
[ ] tests are green
[ ] UR test OR added to continual research plan

Reference
How to write good user stories

We will endeavour to use modules from https://github.com/terraform-aws-modules or from MoJ CP or MP


[WFLY-20037 - WFLY-19496] - OIDC Authentication Request and Scope com…

…munity promotion
https://issues.redhat.com/browse/WFLY-20037
https://issues.redhat.com/browse/WFLY-19496

Thanks for the PR, @pedro-hos! Looks like there are some test failures related to these changes, e.g., see:
https://ci.wildfly.org/buildConfiguration/WF_PullRequest_LinuxJdk17/471813

@fjuma thank you for your feedback. Adding the missing files, let's see if the CI shows anything else.

@fjuma I think that the error isn't related to the changes. Please, let me know if I need to do something else. Thank you


Document that python 3 is required in metadata so pip for python 2 will not go after newer versions

Too late for 3.0.3 -- but subsequent releases
Adding something like
python_requires='>=3'
and for classifiers,
Programming Language :: Python :: 3 :: Only

Thanks for bringing this to my attention.
3.0.4 released, with the proper python_requires and <3.0.4 releases yanked to get pip to install as expected.


Cannot use ninja from a venv

I'm currently having an issue using meson-python in an environment where I cannot install ninja system-wide.
In particular, I'm in a venv
python3 -m venv venv
source venv/bin/activate
pip install -e . # has `requires = ["meson-python"]`

Which results in the following ninja:
Found ninja-1.11.1.git.kitware.jobserver-1 at /tmp/pip-build-env-3_c2bhz3/normal/bin/ninja

However, this doesn't work in the venv:
>>> import constellation
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1138, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1078, in _find_spec
  File "/home/stephan/Projects/constellation/venv/lib/python3.11/site-packages/_constellation_editable_loader.py", line 271, in find_spec
    tree = self.rebuild()
           ^^^^^^^^^^^^^^
  File "/home/stephan/Projects/constellation/venv/lib/python3.11/site-packages/_constellation_editable_loader.py", line 312, in rebuild
    subprocess.run(self._build_cmd, cwd=self._build_path, env=env, stdout=stdout, check=True)
  File "/usr/lib/python3.11/subprocess.py", line 548, in run
    with Popen(*popenargs, **kwargs) as process:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/subprocess.py", line 1026, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.11/subprocess.py", line 1953, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip-build-env-3_c2bhz3/normal/bin/ninja'

I also tried installing ninja in the venv and setting the NINJA env var, but this also doesn't work:
meson-python: error: Could not find ninja version 1.8.2 or newer.

which I think is because this is called outside of the venv - ninja --version in the venv is fine.

pip install creates a new venv to use instead, due to "build isolation".
meson-python will anyways install ninja as a pip-based build dependency if you don't have one on PATH, so no need to do so manually.

You have to use:
pip install -e . --no-build-isolation

See the docs in https://mesonbuild.com/meson-python/how-to-guides/editable-installs.html for the background on why  --no-build-isolation is necessary.

Ah ok - so even when I want to use ninja from a venv, I need to pass --no-build-isolation?

Ah right, and with --no-build-isolation I need to install meson-python beforehand - quite annoying, thanks for your help!

Ah right, and with --no-build-isolation I need to install meson-python beforehand - quite annoying, thanks for your help!

Yeah but if you don't pass no-build-isolation then pip installs meson-python plus meson, compiles the project once, and uninstalls meson-python plus meson.
You might have meson already installed. I guarantee many other users of editable installs don't. :D

Yeah but if you don't pass no-build-isolation then pip installs meson-python plus meson, compiles the project once, and uninstalls meson-python plus meson.

I guess this is the annoying part - it would be nice if one could tell pip to leave those package persistently

it would be nice if one could tell pip to leave those package persistently

pip devs don't seem to have much interest in this, but someone should just write a small wrapper to install build deps listed in pyproject.toml into the development environment and then invoke pip install -e . --no-build-isolation. This would be the most sensible behavior for any project with compiled code, independent of which build backend is used.

Dears, I try to comment here, will open a separate issue if that's better. I'm looking for help with editable modes. Using pip install -e . --no-build-isolation I can correctly install the package and compile my C code, which is called through ctypes.
However once I try to use the package it fails to find the shared libraries:
  File "/home/deppep/Dropbox/Progetti/hbstools/hbstools/hbstools/triggers/bft_cwrap.py", line 16, in <module>
    clib_bft = ctypes.CDLL(_LIBCFOCUS)
               ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/ctypes/__init__.py", line 376, in __init__
    self._handle = _dlopen(self._name, mode)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: /home/deppep/Dropbox/Progetti/hbstools/hbstools/hbstools/triggers/.sharedlibs/lib-pfocus.so: cannot open shared object file: No such file or directory

The _LIBCFOCUS above is implemented here:
def _library_path(libname: str) -> str:
    """Gets the path to the C shared library, with appropriate extension.
    Assumes the library and this file to be installed in the same directory"""
    from pathlib import Path
    import sys

    if sys.platform.startswith("win32"):
        suffix = ".dll"
    elif sys.platform.startswith("linux"):
        suffix = ".so"
    elif sys.platform.startswith("darwin"):
        suffix = ".dylib"
    else:
        raise OSError("System not supported")

    return str(Path(__file__).parent / f"{libname}{suffix}")

_LIBCFOCUS = _library_path(".sharedlibs/lib-pfocus")

The problem is that, once in editable mode, the code looks for the shared libraries in the wrong place. While not in editable mode, the libraries are installed  in my local environment directory (site-packages/hbstools/triggers/.sharedlibs/lib-pfocus.so). However, once in editable-mode, I do not understand where they are actually installed, but they are expected to be in my source directory.
Is it possible to install my project in editable mode? Thank you.

@peppedilillo if @eli-schwartz's reply is not enough yet to help you solve the problem, please copy your original question, the reply and what you want to ask next to a new discussion.
(try to not comment on closed issues unless you're very sure it's the same thing, which this is not)


feat: Add filter_policy init parameter to all retrievers

Why:
The changes across various integrations (Astra, Chroma, Elasticsearch, MongoDB Atlas, OpenSearch, pgvector, Pinecone, Qdrant, and Weaviate) address a common need for more flexible filtering options within the retrieval process. By introducing a filter policy option (replace or merge), developers can now control how runtime filters are applied relative to initialization time filters.

fixes https://github.com/deepset-ai/haystack-core-integrations/issues/780

What:

Added filter_policy parameter with options replace and merge across multiple retrievers to control filter behavior dynamically.
Adjustments made to initialize, serialize (to_dict), and run methods to support the new filter conservatively policy behavior.
Unit tests were updated or added to validate the new functionality.

How can it be used:

Dynamic Filter Behavior Adjustment:  Users can decide whether to completely override the initial filters set during the retriever's initialization (replace) or merge them with runtime filters, with the latter taking precedence (merge).
# Example: Using the filter_policy parameter
retriever = SomeRetriever(document_store=my_doc_store, filters={"status": "active"}, filter_policy="merge")

Complex Search Scenarios:

In cases where the context of a query might dictate altering pre-set filters without discarding them, the merge option allows for an additive approach.
For strict query contexts that require ignoring initial filters, the replace option offers a clean slate for filters at runtime.

How did you test it:

Unit tests were enhanced or newly created to cover both replace and merge scenarios for the filter_policy parameter.
Tests ensure that filter logic is correctly applied based on the policy setting, whether it merges runtime filters with initial filters or replaces them entirely.
Additional test cases should be considered for complex filter merge scenarios to ensure priority and override mechanisms function as expected.

Notes for the reviewer:

Make sure all retrievers in the project are accounted and appropriately adjusted
Pay special attention all retrievers have the same new init param + proper pydoc
Verify unit tests were adjusted appropriately
Pay special attention to Qdrant  retrievers, there we needed (or not, I'm not 100% sure) to keep attribute filters as None
It's essential to ensure backward compatibility; existing implementations should default to replace to maintain current behavior unless explicitly set to merge.

@silvanocerza we also need to address retrievers in Haystack project itself. I suppose we need to somehow coordinate this PR and that one and their releases?

Can we please break this down into single PRs for single integrations? This will make rolling out these changes with appropriate releases for the single packages easier, as well as producing better release notes.

Superseded by:
https://github.com/deepset-ai/haystack-core-integrations/pull/819
https://github.com/deepset-ai/haystack-core-integrations/pull/820
https://github.com/deepset-ai/haystack-core-integrations/pull/821
https://github.com/deepset-ai/haystack-core-integrations/pull/822
https://github.com/deepset-ai/haystack-core-integrations/pull/823
https://github.com/deepset-ai/haystack-core-integrations/pull/824
https://github.com/deepset-ai/haystack-core-integrations/pull/825
https://github.com/deepset-ai/haystack-core-integrations/pull/826
https://github.com/deepset-ai/haystack-core-integrations/pull/827


Update Makefile: Build shared lib when platform is SDL

When using PLATFORM=PLATFORM_DESKTOP_SDL and RAYLIB_LIBTYPE=SHARED, it didn't build the library (.so file).

@JupiterRider Thanks for the review!


add CVE-2018-6128

Hi, this PR add CVE-2018-6128, an uXSS which triggered by an URL parsing bug.
I like this repo very much, hope this PR doesn't bother you.

Hi @LyleMi!
Yeah, I've seen this bug (even before it became popular).

Wanted to write a short post about this, there are a lot of things to discuss here.

Sure, thanks for help 👍
Feel free to submit more bugs


drivers: uart_nrfx_uarte: Prevent re-enabling RX until UART_RX_DISABLED

Fix the driver so that after a call to uart_rx_disable() it does not allow re-enabling RX until the UART_RX_DISABLED is generated (what means that the disabling procedure is complete). Otherwise, it is possible that the RXTO event from the previous RX is handled right after a new RX is started, and the RX buffer pointer gets corrupted in the rx_flush() function.
Signed-off-by: Andrzej Głąbek<EMAIL_ADDRESS>

Please do not merge the PR until I confirm that it fixes our issue. Thanks!

I confirm that the fix is working on our side and can be merged. Thanks for fixing this!


Add node 12.17.0 image

It has security fixes, plus backported AsyncLocalStorage which we wanna use.

@SimenB We're welcome to a PR!

I can send one for the abse thing as that has a script. I don't see one for the browser image, though? I might very well be missing something, of course

done


Update filepicker library version to 0.2.0

Update filepicker library version to 0.2.0.
This PR should only be merged once https://github.com/ARK-Builders/ARK-Memo/pull/57 is merged.
Related issue: https://github.com/ARK-Builders/ARK-Memo/issues/60

@hieuwu @shubertm Can you help review this PR please?


Rack::Cache works in test environment

Dragonfly inserts Rack::Cache middleware in all environments when requiring "dragonfly/images". This is fine for development environment but causes troubles in Capybara integration tests. Let's say, I have a CategoriesController with index action that uses HTTP caching.
def index
  expires_in 5.minutes, :public => true
end

When I visit the page in Capybara integration test (that in turn uses Rack::Test), Rack::Cache stores it and returns it for the rest of tests which usually want fresh pages each.
def test_multiple_categories
  Category.create!(name: "Books")
  Category.create!(name: "Pets")
  visit categories_path
  assert has_content?("Books")
  assert has_content?("Pets")
end

def test_no_categories
  visit categories_path
  assert has_content?("No categories")
end

In the above example one of tests will get a stale page and will fail. It took me a while to realize why the tests were randomly failing. Now I have the following initializer that removes Rack::Cache middleware in test environment:
Rails.application.middleware.delete(Rack::Cache) if Rails.env.test?

I think that Dragonfly should not include Rack::Cache in test environment.

Actually I think it should be disabled in development too. I was going crazy because changes to my templates wouldn't take affect until I deleted tmp/dragonfly/cache. Given that Rails 3.2 also uses Rack::Cache, should it even be caching pages into that directory? Rather than handle this on a per-environment basis, we should use the action_controller.perform_caching setting.
Rails.application.middleware.delete(Rack::Cache) unless Rails.configuration.action_controller.perform_caching


ILogger: Ability to add a tag and/or CorrelationId to a log entry

Microsoft.Extensions.Logging.ApplicationInsights 2.14.0
Runtime version: netcoreapp3.1
Local dev environment

What are you trying to achieve?
Add a custom property for every log request while just using services.AddApplicationInsights("iKey").
Something like "Tag" would be great.
We have like 5-6 microservices, each running in a separate pod. We would like to log to one single ApplicationInsights instance, and then filter from there on. Either via the "Tag" I'd love to give each service, or via a separate "CorrelationId" which would be generated by our API gateway, and given further down to each subsequent request in our microservice architecture.
Is anything like that possible? We already had a look at the ELK project, and there is something like that. I was looking for something like that in AI logging.
(for reference: https://github.com/elastic/ecs-dotnet/blob/master/src/Elasticsearch.Extensions.Logging/ReadMe.md)
What have you tried so far?

Had a look at AddApplicationInsights configure action whether there was anything..
Had a look at the other similar issues this repo
Had a look at TelemetryProcessors, but they don't seem to get executed?

The right approach is to use TelemetryInitializer - https://docs.microsoft.com/en-us/azure/azure-monitor/app/api-filtering-sampling#addmodify-properties-itelemetryinitializer

Yes you're right. We already implemented the kubernetes package which almost does everything we wanted.
For anyone else looking for something similar: https://github.com/microsoft/ApplicationInsights-Kubernetes
Thanks!


fix(deps): update dependency rxjs to v6.6.0

This PR contains the following updates:

Package
Type
Update
Change

rxjs
dependencies
minor
6.5.5 -> 6.6.0

Release Notes

reactivex/rxjs
v6.6.0
Compare Source

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

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

v5.1.6
GitHub release

Your semantic-release bot :package::rocket:


Can not get user image in larger size

Can not obey the full size image. The "picture.type (large)" parameter returns empty. Only the small image with the "picture" parameter is returned.

Hi, do you mean profile picture? if so then you can adjust height (autoscale-wise) by adding parameter
https://graph.facebook.com/{app-scoped-user-id}/picture?height=640
Let me know if i misunderstood your issue please.

The following code does not return an image URL:
var profileFacebookDict = await _facebookClient.RequestUserDataAsync (
                 new [] {"picture? height = 640", "email", "first_name", "last_name", "birthday"
                 new [] {"email", "user_birthday"});
How do I return the URL of the full size image?

Well i'm not quite sure if you can set parameters after question mark in that string array.
But here is what you can do.  If you just want profile picture URL of required app-user-id you can request id too in your Request and then use this api call to retrieve either json or redirect to jpg profile picture of your desired width/height ratio
https://graph.facebook.com/123456789}/picture?height=640
You can also use call below to retrieve json array with picture path instead of redirected jpg
https://graph.facebook.com/123456789/picture?height=640&json=true

The suggestion from @TimotejRybar might be the simpler way to do it.
If you want to use the plugin can do it this way:
 await CrossFacebookClient.Current.QueryDataAsync("me/picture?height=640", new string[]{ "public_profile"});


Webui can now show syslog output for bootstrapper

aeon group now has read privs for syslog
Bootstrapper logs in webUI now reads from syslog

Coverage remained the same at 77.673% when pulling d04fd48aaf829ad9bb8689e604c0488339478b32 on syslog_privs into 9f9f097544f852291032f4d6d03c153301ad2d50 on master.

Coverage remained the same at 77.673% when pulling d04fd48aaf829ad9bb8689e604c0488339478b32 on syslog_privs into 9f9f097544f852291032f4d6d03c153301ad2d50 on master.


Some improvements

Not sure, but think this will better. Feel free to drop or cherry pick any commit to master.

NACK on https://github.com/ExodusMovement/buffer-expand/pull/1/commits/9c8d71f277aca79f4385bc69eedb7f4ede0babbe and https://github.com/ExodusMovement/buffer-expand/pull/1/commits/9a456efeeb7dd4d191c0a58b2f71e90d5496abe7
The rest is good though.

Why not use randombytes? (part of crypto-browserify)

Why not use randombytes? (part of crypto-browserify)

This module exists to serve Exodus and secure-container. It's an unnecessary dependency. If someone wants to use it outside of Exodus or secure-container, they can just use browserify/crypto-browserify.

@jprichardson You keep posting what I'm going to say just ahead of me. :laughing:

Okay, updated.

ACK


please pump path-to-regexp dependency (high severity vulnerabilities now)

Is there an existing issue for this?

[X] I have searched the existing issues

Current behavior
high severity vulnerabilities reported by npm audit
Minimum reproduction code
https://github.com/nestjs/serve-static
Steps to reproduce
No response
Expected behavior
No vulnerabilities reported by npm audit
Package version
4.0.2
NestJS version
10.4.5
Node.js version
22.8.0
In which operating systems have you tested?

[X] macOS
[ ] Windows
[X] Linux

Other
No response

https://github.com/nestjs/serve-static/pull/1454


Getting error

Hello, I got this error when I run : sudo npm install -g alfred-real-time-stock-price
Error: Command failed with exit code 1 (EPERM): alfred-link
at makeError (/usr/local/lib/node_modules/alfred-real-time-stock-price/node_modules/execa/lib/error.js:59:11)
at handlePromise (/usr/local/lib/node_modules/alfred-real-time-stock-price/node_modules/execa/index.js:112:26)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async /usr/local/lib/node_modules/alfred-real-time-stock-price/node_modules/alfy/init.js:7:3 {
command: 'alfred-link',
exitCode: 1,
exitCodeName: 'EPERM',
stdout: '',
stderr: 'Error: Permission denied to read Alfred preferences at location /Users/sikai/Library/Preferences/com.runningwithcrayons.Alfred-Preferences-3.plist\n' +
'    at module.exports (/usr/local/lib/node_modules/alfred-real-time-stock-price/node_modules/resolve-alfred-prefs/index.js:44:9)',
all: 'Error: Permission denied to read Alfred preferences at location /Users/sikai/Library/Preferences/com.runningwithcrayons.Alfred-Preferences-3.plist\n' +
'    at module.exports (/usr/local/lib/node_modules/alfred-real-time-stock-price/node_modules/resolve-alfred-prefs/index.js:44:9)',
failed: true,
timedOut: false,
isCanceled: false,
killed: false,
signal: undefined
}

hey @sikai   please update your npm and try it again. Or you can download the workflow file directly and install it. Thanks


Issues with helm provider - failure to move/rename?

Sorry for not using the template, but this is much faster to just show what's happening:
$ m1-terraform-provider-helper install hashicorp/helm -v v2.4.1
Repo: https://github.com/hashicorp/terraform-provider-helm
GitRepo: git@github.com:hashicorp/terraform-provider-helm
2022/01/12 08:34:05 Executingcd /Users/et304383/.m1-terraform-provider-helper && git clone git@github.com:hashicorp/terraform-provider-helm
Cloning into 'terraform-provider-helm'...
Cancel
Updating files: 100% (6301/6301), done.
2022/01/12 08:34:39 Cloning into 'terraform-provider-helm'...
Updating files: 100% (6301/6301), done.

HEAD is now at ac4d18cc1 .github/workflows: Fix waiting-response label removal (#758)
2022/01/12 08:34:39 version: v2.4.1
==> Checking that code complies with gofmt requirements...
go build -v .
2022/01/12 08:35:16 Move from /Users/et304383/go/bin/terraform-provider-helm to /Users/et304383/.terraform.d/plugins/registry.terraform.io/hashicorp/helm/v2.4.1/darwin_arm64/terraform-provider-helm_v2.4.1_x5
2022/01/12 08:35:16 rename /Users/et304383/go/bin/terraform-provider-helm /Users/et304383/.terraform.d/plugins/registry.terraform.io/hashicorp/helm/v2.4.1/darwin_arm64/terraform-provider-helm_v2.4.1_x5: no such file or directory
$ ll ~/.m1-terraform-provider-helper/terraform-provider-helm/terraform-provider-helm
-rwxr-xr-x  1 et304383  staff    69M 12 Jan 08:35 /Users/et304383/.m1-terraform-provider-helper/terraform-provider-helm/terraform-provider-helm
$

So it looks like the file is there, in the git directory.  Perhaps the helm devs aren't following a standard for binary generation?

So using the generated binary doesn't work.  The make build is calling out to Docker even, so it's like ARM compilation isn't even possible in the current state, even building from source!
They have an open ticket to add ARM support: https://github.com/hashicorp/terraform-provider-helm/issues/816

I think the issue is that the helm build is just doing go build and not actually installing the binary to the expected home directory under go/bin.

Yeah, that could be the reason. We expect the binary to be placed in the $GOPATH/bin/ (https://github.com/kreuzwerker/m1-terraform-provider-helper/blob/main/internal/app/install.go#L230) and copy it from there.
If that's not the case then we would need to implement a custom buildCommand which executes make build and then copies the binary to $GOPATH/bin/ so that we can successfully copy it.
Would be quite easy to implement, as we already have custom build commands in place (https://github.com/kreuzwerker/m1-terraform-provider-helper/blob/main/internal/app/install.go#L188)

Released v0.3.1 which should enable you to install the helm provider :) @et304383

@Junkern thank you!  I worked around it already by just manually copying the file from ~/.m1-terraform-provider-helper/terraform-provider-helm but at least I'm covered in the future!


redbiom nice display of 504

After doing some more tests with qiita/redbiom, I realized that if you retrieve a lot of results, the server will send a 504 (timeout) and this wasn't being caught by JS. Obviously, this is not a solution but the solution is something that might take some discussion of how to better implement + implementation time. So for the time being this PR adds a "nice" error message.
If timeout:

if something else,

Additionally, decided to improve the show_loading by adding a flag to show some extra text: "This task might take a long time (up to 5 minutes), please do not close this page.". This feature is currently only being used by redbiom but this might be useful for others in the future. Note that 5 min is just a number based on what I was seeing in my tests.

Codecov Report

Merging #2311 into release-candidate will not change coverage.
The diff coverage is n/a.

@@                Coverage Diff                @@
##           release-candidate   #2311   +/-   ##
=================================================
  Coverage               93.8%   93.8%
=================================================
  Files                    163     163
  Lines                  18581   18581
=================================================
  Hits                   17430   17430
  Misses                  1151    1151

Continue to review full report at Codecov.

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


Allow full ecto functionality

Now we can just load by id or a named association. It would be nice if we can support the full ecto functionality by having the ability to load any queryable.
We cannot do batching on queryables, so that benefit is gone, but we can execute the queries in parallel, reducing waterfalls and apply simple caching. Any thoughts?

The built in loading function does a bit more than I think you realize. Suppose you have a Category schema that has a slug column like "news", "weather", "opinion" that sort of thing. You can look those up via:
|> Dataloader.load(Source, {:one, Category}, slug: "news")

For truly arbitrary stuff though you only need the run_batch option. To pick an example from the tests: You've got users who can create posts, and posts have a title. Suppose I want to lookup all users who have made a post with some set of titles.
source =
  Dataloader.Ecto.new(Repo,
    query: &query/2,
    run_batch: &run_batch/5
  )

def run_batch(User, query, :post_title, titles, repo_opts) do
      query =
      from(
        u in query,
        join: p in assoc(u, :posts),
        where: p.title in ^titles,
        select: {p.title, u}
      )

    results =
      query
      |> Repo.all(repo_opts)
      |> Enum.group_by(fn {title, _} -> title end, fn {_, user} -> user end)

    for title <- titles, do: Map.get(results, title, [])
end

Then you use this via:
|> Dataloader.load(Source, {:one, User}, post_title: "Foo")

The run_batch function lets you do basically anything you want. If all you want is parallel execution then you're probably just better off with Task.async_stream in the ordinary case or async with Absinthe.
Avoiding ecto queries outside the context module is a central design principle of Dataloader, which I can talk more about if you want.

Avoiding ecto queries outside the context module is a central design principle of Dataloader, which I can talk more about if you want.

Ok, that might be a difference. Ideally you'd like to (lazy) load data within the context. That's not really practical with the current implementation, but my PR is a step into that direction.
Interested to hear your thoughts, but I don't really agree with the premise.
IMO the dataloader should work at a Repo level, and the contexts should leverage dataloader as tool on top of Ecto or another source, to efficiently load data in terms of IO. So batching, caching and paralyzing. The GraphQL API layer should just call the context, and the context is responsible for leveraging dataloader (or not). What you gain is that every part of your app will load data efficiently. Additionally every dataloading that happens in the business logic layer that does not directly map to graphql fields (like authorization) can now also be efficiently loaded (these things can make the current dataloader pretty worthless in the current form).
I don't really see the role of contexts in this.
It would be nice if we have the ability to load any queryable even though they might not batch (it's not only a batching library!). One benefit for instance, is that it potentially would be possible to cache direct id lookups if they already appeared in a list for instance (not yet implemented, but would be quite trivial). If we cannot run the list query (might be a untypical query) through dataloader, we cannot do that.
We can do Task.async_stream indeed, but dataloader will abstract this away. As it knows the queries that are pending. Building another abstraction just like dataloader but for non-batchable queries would just add more complexity.

That's an interesting take, and I'll have to think about it more. My concern is that you'd either have an enormous proliferation of API functions from the context so you could grab stuff from GraphQL, or you'd simply be duplicating the dataloader API and then you're just using dataloader from the resolvers anyway.
Setting aside questions of how Dataloader should be used for a moment though, how do you feel that Dataloader itself prevents you from doing what you want? The built in Ecto source takes the stance I've articulated for sure, but you could simply write another source that works differently. The built in Ecto source can't and won't be going undergoing a conceptual rewrite any time soon, at a minimum the book depends on its current functionality.
The point of using a protocol however is to let other folks do what they want, and I think that there are a wide variety of options available.

Yes it severely limits what I can do. I'm not married to the approach. Dataloader now is nice if your database maps exactly to your graphql schema and you don't have authorization logic in the context.
Happy to do this in a separate package, or as a fork. Also interested if there is another way to solve it.
It's not so much an interesting take, but it's the intended purpose of dataloader (the facebook version).
I don't get how this approach will result in a proliferation of API functions. The resolver will just call Posts.get(id, account) for each Post so the API surface area is very small.

If you don't think the Lazyloader approach should be part of dataloader, I can publish it as a seperate package. However in my opinion this should be part of dataloader (as it's also part of the other instances of dataloader in other languages).

That's an interesting take, and I'll have to think about it more. My concern is that you'd either have an enormous proliferation of API functions from the context so you could grab stuff from GraphQL, or you'd simply be duplicating the dataloader API and then you're just using dataloader from the resolvers anyway.

I don't understand how the context "grabs stuff" from graphql. I think you are referring to re-using the dataloader state across context functions.

As for the dataloader in the current form, yes it severely limits what I can do.

I was hoping you would offer specifics about what you find lacking in the Dataloader.Source protocol. I know that you find the Dataloader.Ecto implementation lacking but I'm trying to figure out if you feel that the protocol functions found within Dataloader.Source make it impossible for you to achieve what you want with a different source.

it is the intended purpose of dataloader (the facebook version).

Correct me if I'm wrong but the Facebook dataloader exclusively does batched key value lookups, so we're already pretty far afield from its functionality.
Let me take a step back and articulate the problem I was trying to solve with Dataloader. Dataloader exists to solve not just a technical set of problems, but also some conceptual and structural problems that arise in projects.
The Problem
Phoenix Contexts forced Absinthe to re-think data access. The most important characteristic of a context in my view is that it has the responsibility of enforcing your business rules with respect to the data and functionality in its charge. This is I think most important for mutations to that data, but it applies to queries as well.
However, this poses a problem for both Absinthe and even regular controllers. For Absinthe, the assoc/2 helpers from absinthe_ecto aren't really compatible, because by directly walking all the ecto associations there's no easy to enforce data access rules from within the context (IE, don't return things with deleted: true to pick a simple example). With absinthe_ecto out, Absinthe was back to the N+1 problem. Controllers have all of these same problems because they used Repo.preload all the time which would also skip data access rules, and any cross-context lookups required obnoxious helper functions to avoid N+1.
Dataloader
Central to the Dataloader implementation then was the idea that all of the actual data retrieval and access would happen within the context code. The context would have both full access to all of the data in its domain, as well as the ability to apply restrictions and limit access patterns for any query that came through Dataloader. The exact manner by which this happens of course depends on the Dataloader source, and I very explicitly didn't want Dataloader to be Ecto specific.
If you have context A and context B, and A can call a function in B and pass in an Ecto query that relates to B's schemas, then we're violating that control. The whole point is to prevent arbitrary SQL access at arbitrary points in the application. If A wants to use Dataloader within itself to load things, and you want to do so with Ecto query inputs then that seems fine, but at this point we're just basically re-creating Ecto.Repo with a different API.

I agree with all of the above. But I don't think you get my point.
The above explains how you design your modules, agree 100%. However if you use a module you shouldn't be exposed to dataloader at all. Using dataloader within a context should just be an implementation detail inside of contexts, as a consumer of a context (for instance for a GraphQL API layer, I shouldn't have to know or care about it.
The point is that in the current implementation if I use the dataloader inside a function in a context, for instance Post.get(id, actor), it doesn't batch if this function is called multiple times (I can only batch within the function).
In the current implementation the dataloader is exposed in the graphql layer (should need to be IMO), the graphql layer should just translate a request for something into the right call to the internal API (context). Much like controllers (you call the context, you aren't exposed to Ecto).
How can we do that in Elixir when we execute eagerly and don't have a concept like ticks (the javascript dataloader implementation uses a hack where it waits 1 tick before executing queries so it can batch queries that happen at the same time)?
Well we need to have lazy evaluation. I did this by implementing a Deferrable protocol. A function can return a Deferrabla then when I want to evaluate this Deferrable I need to do that explicitly. The graphql layer can evaluate these deferables so that all queries are batched/cached etc efficiently.
With this solution the Dataloader just becomes an implementation detail in a context. The only thing we need is a simple middleware that knows how to handle deferred values.
As for the concrete example it is impossible with the current dataloader implementation to do authorization of fields (for each posts in a list of posts) efficiently whereby you need to query associations. Preloads can be a solution, but that only works for simple cases, and is not ideal.

I know that you find the Dataloader.Ecto implementation lacking but I'm trying to figure out if you feel that the protocol functions found within Dataloader.Source make it impossible for you to achieve what you want with a different source.
As per above, it's not really about Source. However it would be nice to make Dataloader.Ecto feature complete so we can run any query (small change).

Correct me if I'm wrong but the Facebook dataloader exclusively does batched key value lookups, so we're already pretty far afield from its functionality.
If you use Facebook dataloader in the context/model whatever the name where the business logic is it will batch repeat calls, like this:

Post.get(1)
Post.get(2)
Post.get(3)
Post.get(1)

That only results in a single query. Now if I use dataloader in my elixir get context function it will not batch at al. It will only batch within get.
So that is the functionality that is lacking now. And in my opinion it's the most important feature.
If the Post.get simply get's a record from the posts table, we can solve that with the elixir Dataloader. However the get probably queries the roles table as well to see if the current user has a role in this post, if it's not a public posts. If that is not the case the post might have a parent post so we'd like to query the parent post to see if the current user has a role in the parent posts (for instance). Another example we'd might want to check if the current user is a friend of one of the authors in the post.

there's no easy to enforce data access rules from within the context (IE, don't return things with deleted: true to pick a simple example

Not showing deleted posts is really the job of the function that returns a list of posts in the context IMO, like if I run:
Post.all()
But I might be interested in the deletions in some cases:
Post.all_including_deleted()
The dataloader should query whatever the query is inside of those functions.

These are a lot of great ideas and I think I better understand your position now. In essence, you want Dataloader to be an implementation detail of the context, instead of an explicit part of the API of the context. Once it's an implementation detail of the context then we should feel free to pass in any argument value (like queries) that we want.
I actually feel like we're closer to being on the same page than may be obvious. Dataloader started off as "how can I make an API where the actual data retrieval mechanism is an implementation detail". Deferrables are trying to say "how can I make even using dataloader an implementation detail". I'm not entirely convinced however that deferrables aren't exactly what dataloader is, just with guarantees around the API to try to actually get batching.
Here are my questions:
deferred_post_1 = Blog.get_post(1, actor)
deferred_post_2 = Blog.get_post(2, actor)

what is actor?
What does get_post look like?

To expand on #2, I'm unclear on how batching actually happens. Maybe I need to simply dig into your implementation of the Deferrables protocol.

As for the concrete example it is impossible with the current dataloader implementation to do authorization of fields (for each posts in a list of posts) efficiently whereby you need to query associations.

This seems seems entirely possible to me, so maybe working through this example will help further this discussion. Can you expand on this situation a bit so I can sketch a "concrete" solution?

Nice. I'll be speaking at a meetup about this, so I can work on this a bit more. So I can work on explaining this in a bit more detail.
Let me work out the example in code, so you'll have a better idea why it's not possible with the current dataloader (or there might be a solution for it, I'll doubt it would be a good solution but maybe I'll just don't see it😅).
I will also work out the example using the code of the PR.

what is actor?

it's the acting user (a name convention we use in our codebase)

What does get_post look like?

I'll write an example in code but basically:

fetching post,
checking if user can open post (with the data fetching necessary to assert that) and
returning {:ok, post} or {:error, msg}

I actually feel like we're closer to being on the same page than may be obvious. Dataloader started off as "how can I make an API where the actual data retrieval mechanism is an implementation detail". Deferrables are trying to say "how can I make even using dataloader an implementation detail". I'm not entirely convinced however that deferrables aren't exactly what dataloader is, just with guarantees around the API to try to actually get batching.

Dataloader is indeed 90% there. Deferrables solve the last 10%. But let me work it out in code so it's clearer to see.

Any progress on this front ? Pretty interested in this topic and curious to see where it leads eventually. @benwilson512 did you have a chance to watch @jfrolich talk ?

Hey @jfrolich @tlvenn I just wanted to provide an update. The last 6 months have been overwhelmingly busy for me both with Cargosense stuff as well as personally. Fortunately we've made a lot of progress on Absinthe 1.5 and hope to release it in the week after ElixirConf. At that point I look forward to focusing on this question.
FWIW we've run into this too. It is not possible with the current Dataloader functionality to use it within a context function, which makes it very difficult to have context functions that take on complex business logic while still loading efficiently. I'm very interested in your deferred execution approach. I'm also curious about what could be done with a multiprocess approach.

@benwilson512: Same with my startup as well, so I also left it in an incomplete state. Looking forward working on a good solution/API for this!

@benwilson512 do you have thoughts on these kind of these kinds of loading issues in 2021? Is there a good answer to this with the current iterations of Absinthe / Dataloader?

Hi @tlvenn I don't have a concrete issue. I'm evaluating implementing dataloader on a project and was curious about usage from context functions and more complex authorization scenarios. Ben and Jaap mentioned those here, so was curious of their take today and what patterns they're using for the concepts raised in this issue.


Enable usage of async foreach on SF IAsyncEnumerable

This change will allow using ServiceFabric.Data.IAsyncEnumerable<T> in the async foreach, since it uses duck typing.
So instead of manually working with enumerator we can write:
async Task SomeMethond(ServiceFabric.Data.IAsyncEnumerable<T> asyncEnumerable)
{
  await foreach(var item in asyncEnumerable)
  {
     /*  Some code that use item variable */
  }
}

This will NOT allow using the extension method of System.Collection.Generic.IAsyncEnumerable<T> like WithCancelation or ConfigureAwait in order to do that interface needs to be implemented.
This change could help with following issue https://github.com/microsoft/service-fabric/issues/406

@bpm-ms @anmolah  could you please have a look?


Plaintext Usernames in $_SESSION

Since usernames stored as plaintext in the session, it is sufficiently easy to become any user if the attacker can execute php on the same server. Proof of concept here:
<?php
session_start();
$_SESSION['phpCAS']['user'] = 'anotherUserName';

An attacker who has permission to execute php on the same server can run this script in php and effectively become 'anotherUserName'.

I don't have a great solution, but someone who is much better at encryption should definitely help out here.

My gut reaction is that this is a non-issue.
If the adversary can execute arbitrary PHP server-side, then he can do anything.  There is nothing that phpCAS can do that cannot be done in PHP, since phpCAS is itself run as PHP.
So, it's possible to add complexity here (e.g., encrypting the username in the session) but it's not possible to add security, since necessarily phpCAS would need access to the key to encrypt and decrypt that username to have encrypted it in the first place and to make use of it when called upon, and if phpCAS can access the key, arbitrary PHP can access the key.
phpCAS doesn't solve the problem of adversaries who are able to execute arbitrary code server-side (but it does prevent even such adversaries from obtaining the end user's password.)

@apetro nailed it on the head: CAS/phpCAS keeps the user's password away from the web server, but while phpCAS should not introduce arbitrary code execution vulnerabilities, there is nothing it can due to prevent them in client applications.

Well, yes that is a common issues for all web apps. If i'm able to execute arbitrary code on the same host i can always hijack you sessions. I can do pretty much the same in any other interactive language. I can even go so far as to write a the REMOTE_USER variable in the apache auth modules. Same applies for anyone being able to read the session storage directory.
If you look at encrypting session data you always end up with having the key somewhere in the filesystem or in server variable which must be readable for the webserver itself. The only mitigation i can currently think of in such a shared environment would be safe_mode which is pretty much broken itself....
Since apache has no concept of separating users i think you are pretty much on your own if you want to secure this area. I guess only java enterprise servers actually support something like security realms and sandboxing etc.
I'm always happy to discuss this further if there is anything unclear.

Ok, all good points. I figured this had already been thought out, I just thought I would bring it up in case somehow it hadn't.


Unhandled EOFError() after 300s

For any long-running query, after 300 seconds, dbt will return with an unhandled error:
File "/usr/local/lib/python3.7/site-packages/dbt_core-0.13.0-py3.7.egg/dbt/adapters/sql/connections.py", line 61, in add_query
    cursor.execute(sql, bindings)
  File "/Users/jerco/dev/dbt-dev/dbt-spark/dbt/adapters/spark/connections.py", line 100, in execute
    return self._cursor.execute(sql, bindings)
  File "/usr/local/lib/python3.7/site-packages/PyHive-0.6.1-py3.7.egg/pyhive/hive.py", line 364, in execute
    response = self._connection.client.ExecuteStatement(req)
  File "/usr/local/lib/python3.7/site-packages/PyHive-0.6.1-py3.7.egg/TCLIService/TCLIService.py", line 280, in ExecuteStatement
    return self.recv_ExecuteStatement()
  File "/usr/local/lib/python3.7/site-packages/PyHive-0.6.1-py3.7.egg/TCLIService/TCLIService.py", line 292, in recv_ExecuteStatement
    (fname, mtype, rseqid) = iprot.readMessageBegin()
  File "/usr/local/lib/python3.7/site-packages/thrift-0.11.0-py3.7-macosx-10.14-x86_64.egg/thrift/protocol/TBinaryProtocol.py", line 148, in readMessageBegin
    name = self.trans.readAll(sz)
  File "/usr/local/lib/python3.7/site-packages/thrift-0.11.0-py3.7-macosx-10.14-x86_64.egg/thrift/transport/TTransport.py", line 66, in readAll
    raise EOFError()

This is raised by readall() in the thrift.transport module that the Spark adapter includes here.
The query itself is not cancelled and will continue running (to failure/completion/otherwise) in Spark.

Closed by https://github.com/fishtown-analytics/dbt-spark/pull/26


Make it so pressing shift makes you go faster when in camera mode

Implemented BYU-PCCL/holodeck-engine/pull/171


fixes *mut esp_netif_obj not Sync compiler error

Fixes #56 (again).
Implements a new type wrapper SendSyncPtr for arbitrary pointer types and impls Send and Sync on that wrapper. This is just an assertion for the compiler and assumes that the underlying apis from the sdk are relatively thread safe.

Fixes #56 (again). Implements a new type wrapper SendSyncPtr for arbitrary pointer types and impls Send and Sync on that wrapper. This is just an assertion for the compiler and assumes that the underlying apis from the sdk are relatively thread safe.

There is no such thing as "relatively" thread safe. Either they are thread safe (i.e. you can call methods on the pointer concurrently, from any thread - so you can unsafely "proclaim" the raw C API as Send + Sync) or not. If it is not, and you still mark it as Send + Sync you'll be ending up with Rust UB = weird crashes/misbehaviors in your program, which is against the whole point of using rust in the first place.
esp_netif_t is not thread-safe, contrary to what the ESP IDF documentation says.  Did you read this? It is right there, in #56.
What you are doing with this PR is a bit to blindly apply Send + Sync to a bunch of raw C APIs. This is very dangerous. Each API has to be reviewed in detail as to if it can be proclaimed Send + Sync (i.e. "thread safe").
The event loop might be thread safe. The Netif API, as per above - is just not (data races between reading the Netif state and another thread modifying the Netif state).
I'll address the await + tokio::sync::Mutex topic in the issue, a bit later.


consider changing data logic

atm. the app loads all the data stored in multiple files (cases, death, hospitalizations, per us/states) and then one of the first steps is to filter them again by targetVariable (cases, deaths, ...), scoreType, and location.
one option would be to load only the data that is really needed and better split the up in multiple files (targetVariable x score x location (nation or states)). This would reduce the initial loading time and with https://shiny.rstudio.com/reference/shiny/1.6.0/bindCache.html shiny could take care of caching datasets.

Thanks @krivard.  And sounds like a good idea, @sgratzl
What happened to the idea of reading data from disk instead of from the S3 bucket?  I remember @nmdefries mentioning that it's actually slow to read from the S3 bucket.  And then I suggested we just download a local clone of all the data each Monday that we can read from for the dashboard.  Has that been implemented and does it lead to speed improvements?

I've implemented caching for the score data in #169 that only loads the score data twice a week, after each pipeline run. Every other user besides the first one following a pipeline run will be reading the scores from memory. Releasing the caching change is waiting on another PR -- let me go poke some people.

This behavior has been added for target variables, but geo types are still combined due to the only small additional benefit that change would provide. Most of the time we're handling state forecasts, both when a single state is requested or when we're summarizing across them; separating out US data only saves effort ~1/60 of the time.


Containers don't have access to internet when using multi-host overlay network

I'm following https://github.com/docker/libnetwork/blob/master/docs/overlay.md
Containers on different host are able to ping each other but none of them have internet access.
I think this issue was reported but I can't seem to find it.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

To access the internet you have to attach a bridge network to the container.

@mountkin  how do I do that? I am reading https://docs.docker.com/reference/run/#network-settings but can't find an option to attach additional network

@gauravphoenix When using the overlay network if you want to access internet start the container with -p option. You can give any port number. Passing the -p option creates an endpoint on the default bridge network (docker0 bridge) and provides external connectivity. This is the current behavior in 1.8 experimental version.
We are working on providing a cleaner solution in the next release.

@gauravphoenix there is a minor hack that makes the external connectivity work in experimental channel. Containers in overlay network gets external connectivity automatically when the container is launched with -p or -P or --expose flags. Essentially, when either of these flags are used to expose / port-map, the daemon automatically attaches the container to the bridge network.
But, this will change in a few days through proper external connectivity support.

Thanks @mavenugo and @sanimej

@mavenugo @sanimej
I am trying to build a docker image from a Dockerfile against a docker daemon which is using overlay networking. In the dockerfile I have a "wget" command which needs internet access. How do I workaround this issue now?

@gauravphoenix remove the daemon --default-network configuration. That will make bridge driver as the default driver and hence you will not hit this issue.

@mavenugo  thanks. That should work

Hi maenugo,
I also have the problem with containers connecting to a docker-overlay network not having Internet access.
I am starting up the Containers with docker-compose, but there are also some started dynamically.
I understand "-p", "-P", "--expose" was a solution with previous versions of Docker, but what is the way to get around this now?
[root@ip-10-43-185-247 log]# docker -v
Docker version 1.11.2, build b9f10c9/1.11.2
[root@ip-10-43-185-247 log]# uname -a
Linux ip-10-43-185-247 4.4.23-31.54.amzn1.x86_64 #1 SMP Tue Oct 18 22:02:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@ip-10-43-185-247 log]# docker info
Containers: 160
Running: 0
Paused: 0
Stopped: 160
Images: 25
Server Version: 1.11.2
Storage Driver: devicemapper
Pool Name: docker-202:1-395936-pool
Pool Blocksize: 65.54 kB
Base Device Size: 10.74 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 11 GB
Data Space Total: 107.4 GB
Data Space Available: 36.81 GB
Metadata Space Used: 40.85 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.107 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev or use --storage-opt dm.no_warn_on_loop_devices=true to suppress this warning.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.93-RHEL7 (2015-01-28)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: host bridge null
Kernel Version: 4.4.23-31.54.amzn1.x86_64
Operating System: Amazon Linux AMI 2016.09
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.8 GiB
Name: ip-10-43-185-247
ID: CC6B:EWR3:LNJT:OESW:SVBT:BN6B:DBSK:HB34:U4OA:J2BV:AX37:BY3J
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Http Proxy: http://webproxy.aws.db.de:8080/
Https Proxy: http://webproxy.aws.db.de:8080/
Registry: https://index.docker.io/v1/
Thanks & Cheers,
Bert


[WIP] Glitch Embeds

adding initial glitch embeds! more on the way.

eyo, can you please rebase off of master so you can get the updated cloud build config

@MylesBorins will the robot auto link up a preview here?

@potch it is supposed to. The github action is saying it is "queued"... will dig into why that isn't working
here is the URL
https://storage.googleapis.com/staging.nodejs.dev/29f1bdc/index.html
TL;DR canonically it will always the above URL modulo the 7 digit sha

@potch this is a bug in cloud build, if you push the branch onto this repo everything works as expected. If the PR build is kicked off from a fork the check doesn't finish in the same way and the action is never triggered to post the link 😅

All the examples are in a Glitch Team: https://glitch.com/@nodejs-dev

@potch qq
I noticed that the examples require you to click through / remix to edit at all. Is there any way around this?

closing this in favor of #50.


Systen insert monomer from the library to the canvas even if it shouldn't (and error message is wrong) 2

Steps to Reproduce

Go to Macromolecules mode - Sequence mode
Go to the Library - Peptide tab
Click on A peptide twice to put two As on the canvas
Move cursor to the beginning of sequence

Go to Library - RNA tab, open Bases section
Click on C base (C section, it has no R2 connection point)

Actual behavior
System split existed sequence on two and adds monomer at the end on the first one. And shows error message

Expected behavior

No monomers should be changed.
As per requirement:

.....2.2 If monomer being added lacks AP necessary for establishing connections then error message should be displayed and no monomer is added.

Error message text should be The monomer lacks R2 attachment point and cannot be inserted at current position

Versions

Ketcher Version 2.24.0-rc.1 Build at 2024-08-06; 19:17:47
Indigo Toolkit Version 1.23.0-rc.1.0-g85f89b8f5-wasm32-wasm-clang-19.0.0
Windows 10 Pro
Chrome Version 127.0.6533.100 (Official Build) (64-bit)

Related issue - https://github.com/epam/ketcher/issues/4878

Partially fixed.
No monomer insertion happens but error message is wrong.
Follow up bug has been created: https://github.com/epam/ketcher/issues/5300

Ketcher Version 2.24.0-rc.2 Build at 2024-08-14; 19:00:14
Indigo Toolkit Version 1.23.0-rc.2.0-g6a2a7526a-wasm32-wasm-clang-19.0.0
Chrome Version 127.0.6533.100 (Official Build) (64-bit)
Win10


move the four numbers to MAPL Constants?

https://github.com/GEOS-ESM/MAPL/blob/8bb4b4ae158e8f26400dadd4a5052d0814220d8e/generic/MAPL_Generic.F90#L4119-L4133

Those are @dr0cloud things, so I'm mentioning him here...

Are these constants being duplicated any where else? Anyone who accesses the Orbit should now do so through the mechanisms of MAPL_SunGetInsolation which uses these constants, not through some other adhoc routine. I did notice the other day that there were orbital parameters in the MAPL Physical Constants. Who is using these?

As @weiyuan-jiang points out, they are in some catch code it looks like:
https://github.com/GEOS-ESM/GEOSgcm_GridComp/issues/667

@weiyuan-jiang @dr0cloud Is this now taken care of via #1920 ?

Hi Matt, PR #1920 replaces PR #1902 and whatever the issue it was based on. P.
Peter Norris, Ph.D.
Senior Research Scientist
Global Modeling and Assimilation Office (GMAO) / NASA Goddard Space Flight Center
Goddard Earth Sciences Technology and Research (GESTAR) II / University of Maryland, Baltimore County (UMBC)
Cell<PHONE_NUMBER>
From: Matthew Thompson @.>
Reply-To: GEOS-ESM/MAPL @.>
Date: Sunday, January 15, 2023 at 3:32 PM
To: GEOS-ESM/MAPL @.>
Cc: "Norris, Peter M. (GSFC-610.1)[UNIVERSITY OF MARYLAND BALTIMORE CO]" @.>, Mention @.***>
Subject: [EXTERNAL] Re: [GEOS-ESM/MAPL] move the four numbers to MAPL Constants? (Issue #1818)
@weiyuan-jianghttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fweiyuan-jiang&data=05|01|peter.m.norris%40nasa.gov|cf8ccec3c12b46699d4808daf737a3ee|7005d45845be48ae8140d43da96dd17b|0|0|638094115594834866|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=UMN95hTiCoGQM%2F306Zlqenq4yZkqt4245uuHwnykRhw%3D&reserved=0 @dr0cloudhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdr0cloud&data=05|01|peter.m.norris%40nasa.gov|cf8ccec3c12b46699d4808daf737a3ee|7005d45845be48ae8140d43da96dd17b|0|0|638094115594834866|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=pCLo6nc2b13l6f%2BM2Pes9kBDMEmaweKuiraRFbBksSg%3D&reserved=0 Is this now taken care of via #1920https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGEOS-ESM%2FMAPL%2Fpull%2F1920&data=05|01|peter.m.norris%40nasa.gov|cf8ccec3c12b46699d4808daf737a3ee|7005d45845be48ae8140d43da96dd17b|0|0|638094115594991079|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=DDiRg8QLBfPlu8If1jSalr83ptlkrPujb8BTq7gePf8%3D&reserved=0 ?
—
Reply to this email directly, view it on GitHubhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGEOS-ESM%2FMAPL%2Fissues%2F1818%23issuecomment-1383244721&data=05|01|peter.m.norris%40nasa.gov|cf8ccec3c12b46699d4808daf737a3ee|7005d45845be48ae8140d43da96dd17b|0|0|638094115594991079|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=LgAyDtA6T6Llt0eHEZoJ80dO3K0YBR8z3FCvlyTeqoc%3D&reserved=0, or unsubscribehttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALBN7E3N5CXB767FJSLAGUTWSRNFZANCNFSM6AAAAAASCJIHXI&data=05|01|peter.m.norris%40nasa.gov|cf8ccec3c12b46699d4808daf737a3ee|7005d45845be48ae8140d43da96dd17b|0|0|638094115594991079|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=CupXowQ%2BvRRuQ2Be%2BTsfM8FnoCdhFBqt7pcHFMBIsFw%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>


Return the correct host IP

Don't use stream server address as it default to <IP_ADDRESS> now.
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

/test all

/test critest_fedora


tests: Remove redundant __init__s

@booxter can you rebase this? then we can merge

@russellb done


Error for loading state_dict for DALLE

Got runtime error for training command for CUB data
(" python running_command/run_train_cub.py " )
RuntimeError: Error(s) in loading state_dict for DALLE:
Unexpected key(s) in state_dict: "transformer.log_alpha", "transformer.log_1_min_alpha", "transformer.log_cumprod_alpha", "transformer.log_1_min_cumprod_alpha".
Any point that I missed?

How did you resolve this error?


Fix for "Suspicious Spoolsv Child Process"

Its just searching for dll files named "gupdate.exe" etc. This commit hunts for processes named "gupdate.exe" etc.

Closing this request. You fixed it in an other commit.


Prevent animations on first load

Gets ride of a flicker in DateMonth mode where it first shows the time then animates to the calendar

Think this would be very good to add, as we have to do this manually each time we update the pod.


[fix][ffmpeg] changing $PATH separator for Linux

Using a semicolon in $PATH might break on some flavors of Linux, eg Docker based on Ubuntu 18.04.

I am seeing build failures on windows with this change, can you look into that?  Also don't forget to bump the CONTROL version number.


Fixes versioning when using versioned named union variants

Example of bug: playground

All changed packages have been documented.

:white_check_mark: @typespec/versioning

Show changes
@typespec/versioning - fix ✏

Fixes versioning when using versioned named union variants

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


Fixes #4

Bumps RxSwift/RxCocoa dependency to 2.1.0 to be able to compile due to a missing SectionedViewDataSourceType reference

@RxSwiftCommunity/contributors this would need after merging a new tag and a push to CocoaPods.
Don't want to merge myself; would love for someone else to check it though


Always enable Soroban diagnostic events on local

What
Always enable Soroban diagnostic events on local, unless explicitly disabled.
Why
Most of the time when folks are using quickstart in local mode they're developing locally or running quickstart in CI. In these modes diagnostic events are critical for understanding what's happening when things go wrong, and debugging during testing and development.
Much like how we enable other test capabilities in local, we should enable diagnostics because that's the most sensible default for developing in local.
We shouldn't change the default for testnet/pubnet, because diagnostics cause unmetered execution and on testnet/pubnet there's no guarantee other peoples contracts being executed would not cause unreasonable resource consumption.
The addition of the ability to disable on local is so that the Digital Ocean template can turn it off since that is a deployed local instance.

fyi @tyvdh


in Source Keys when selected "visualName": "", in device configs ignored for Additional Light 1-19

Expected behavior:
Should show entry in "visualName": "",
Actual behavior:
shows Additional Light 1 - Additional Light 19
How often does this problem occur?

every time
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:

Create layout using additional keys 1-19
Select keys in source keys
label should be defined ones in "visualName": "",

What is the version of Aurora you are experiencing this issue with?

My version is... 0.6.3-522
Does the previous version of Aurora have this issue?
Yes
Please include any logs, screenshots, or files that are related to this issue:

This isn't issue. Additional Keys names are intentionally ignored in layout file so we can create small size LED without printing its name all over it as it won't fit the whole name. Check for keyboardlayoutmanager.cs, there is code which tells the Aurora to ignore visualname tag for Additional keys.

Thanks for quick response.
As there are now 32 Additional keys could the extra ones above 19  be added to keyboardlayoutmanager.cs so that the behaviour of Additional Keys is the same.


updated docs for Icon style override

overriding global icon styles using MuiSvgIcon as MuiIcon doesn't work like it was mentioned in the font awesome section on the same page

This is a general piece of knowledge, I'm closing per https://next.material-ui.com/customization/theme-components/#global-style-overrides. thanks for the suggetion

Alright thanks, @oliviertassinari


Sorting by url name / verb / status / order

When opening the BDSM UI in the request history pane on the left add some helpful filtering for sorting by name, verb and status.

This should also take account of: https://github.com/500tech/bdsm/issues/93
Where initial sorting should show failed requests first.


Addition of Configuration

Updated a configuration in the document to reflect the CPU usage during scheduled scans.
Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/8929

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.


我也占个坑吧，对新的开源项目希望可以尽点力，al糊涂呀

Thank you for your support and interest! With the release of our first official version, we’re closing this issue for better issue management. If you encounter any problems or have suggestions, don’t hesitate to share them with us.
谢谢你的支持和关注，我们已经发布了第一个正式版本！为了更好的管理issue，我们将会对此issue进行关闭。如果你有任何使用上的问题或者建议，欢迎提出来。


Npm modules

cc/ @stubbornella @vinsonchuong
This PR makes publishing NPM modules programmatic. It publishes the following packages to NPM

prismjs containing all of the JavaScript
prismjs-THEMENAME-theme one package per theme:

prismjs-coy-theme
prismjs-dark-theme
prismjs-default-theme
prismjs-funky-theme
prismjs-okaidia-theme
prismjs-tomorrow-theme
prismjs-twilight-theme

Run gulp createPackages --version X.X.X to create the packages. The theme packages are added to the dist/ folder. The version number in the main package.json is updated as well.
If all looks good, run gulp publishPackages to publish to npm.
We published v0.0.1 of all the packages to NPM and added you as an owner

Hi @LeaVerou,
This is the PR I was telling you about. It makes a gulp task for publishing your packages to npm. We made you an owner of all of the Prism packages, does it look like it's working on your end?
Cheers,
Nicole

@Golmote please take a look at this PR

I'm not sure about the dist directory containing only themes (i.e. not a usable distribution of Prism). Couldn't it have a name that reflects better its content?

What is the status of this?

Our configuration for travis-ci now publishes automatically to npm on every new release.


Support multiple unsubscibe options

Header example:
List-Unsubscribe: <https://example.org/mailman/options/example>, <mailto:example-request@example.org?subject=unsubscribe>

I've just added this now.


Implement do_history() to get history access

Description
Fixes #61
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update
[ ] Documentation update

Hello @HarshCasper! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file metacall_jupyter/kernel.py:

Line 95:80: E501 line too long (85 > 79 characters)
Line 103:80: E501 line too long (86 > 79 characters)
Line 506:80: E501 line too long (80 > 79 characters)
Line 510:80: E501 line too long (83 > 79 characters)


'Download Core' occurs an error: Zlib.zlibOnError, errno: -5, code: 'Z_BUF_ERROR'

Running script 'Download Core' occurs an error
Steps to Reproduce
Using Xcode build a react-native project.
Or run command node node_modules/realm/scripts/download-realm.js ios --sync
Log
Resolved requirements: { SYNC_SERVER_FOLDER: 'sync',
SYNC_ARCHIVE: 'realm-sync-cocoa-3.7.0.tar.gz',
SYNC_ARCHIVE_ROOT: 'core' }
No lockfile found at the target, proceeding.
Download url: https://static.realm.io/downloads/sync/realm-sync-cocoa-3.7.0.tar.gz
Extracting realm-sync-cocoa-3.7.0.tar.gz => /node_modules/realm/vendor/realm-ios
{ Error: unexpected end of file
at Zlib.zlibOnError [as onerror] (zlib.js:153:17) errno: -5, code: 'Z_BUF_ERROR'
}
Command /bin/sh failed with exit code 1
Version of Realm and Tooling
Realm version:
Realm: 2.12.0
Xcode version: ?
Xcode 9.4.1
iOS/OSX version: ?
10.13.6
Dependency manager + version: ?
node: v8.11.3
react-native-cli: 2.0.1
react-native: 0.55.4
npm: 5.6.0
More info
I can download from https://static.realm.io/downloads/sync/realm-sync-cocoa-3.7.0.tar.gz using safari.
Thanks.

Closing this issue with no recent activity. I assume this issue has been resolved -- please let us know if that is not the case.


Docs: update documentation of inventory and external_dependencies

issue #521

Add documentation for remote inventory federation
Update documentation of external dependencies

Nice! :) Thanks for the update here.


Simplified diff views

The idea is to create virtual documents without all the non-essential information for the workflow logic so we can display cleaner diffs when comparing two versions of the same workflow.
Some of the sections or fields that can be removed are:

position
uuid
errors
version (The main WF version)

xref https://github.com/microsoft/vscode/issues/138550


operator mondoo-operator (1.6.1)

Signed-off-by: Joel Diaz<EMAIL_ADDRESS>

/merge possible

/merge possible


Add Yoneda and CoYoneda types

CoYoneda can be used to avoid the need to create a functor instance for types used with Free.

Released in 2.0.0-FINAL


Firefox browser Crash - Ticket issuer Token Negotiator V1.

Issue found when testing in prep for Liscon. The issue occurs when the application begins to negotiate.

This is now working. I will close this issue.
To add more detail in case we find this issue re-appears this was coming from the Token Negotiator Version 1:
https://tokenscript.github.io/token-negotiator-examples/github-pages-use-only/ticket-issuer-website/build/negotiator.js
To reproduce, open: https://tokenscript.github.io/token-negotiator-examples/github-pages-use-only/ticket-issuer-website/build/index.html


FileNotFoundError: [Errno 2] No such file or directory: 'mergecap'

when it notice me to Select a network to crack and then i select one,a moment later it show this notice:
FileNotFoundError: [Errno 2] No such file or directory: 'mergecap'
how can i fix it?

Hi there, please see the Prerequisites section of the README.md.
You must have mergecap installed, which comes as part of the Wireshark application.
You can check if you have successfully installed it by running mergecap in the terminal.


Open a new PR to get a review

Hi fellow code reviewer,
This is the final PR of this project.
Looking forward,
José

Hi @Team
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that does not follow the proper flow to receive a review, please merge all your pull requests to your dev branch and open a pull request in dev branch that would be merged in to main, please see the project requirements for requesting an external review
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification @prolajumokeoni.
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.


Fix one-way collision when having ends collide with margins.

This allows an object to pass through a one way colliding object
without getting its end caught in colliding object's margins.
For example, A is colliding with B, with B's
one way collision vector being (0, 1) or straight down.
Currently, if A is moving up and the bottom of A intersects
with the bottom of B, it is likely the collision vector will
in some part be pointing down, so the collision will be ignored.
Conversely, if A is moving down and the bottom of A
intersects with the top of B, the collision vector will in some
part be pointing up and the collision is recorded.
However, if A is moving up and the bottom of A intersects
the top of B, there will be a collision recorded.
This fixes that scenario by taking into account
motion during the collision. In this example, since A
is moving up, the collision will be ignored.
It also accounts for the colliding object moving with a velocity
that can overtake the original object.
Finally, it takes care of not trying to unstick the object
when passing through the colliding object, which is obvious
when the one way collision margin is very large.
Partially fixes #25967, #36280 should fix that all the way

Going to close this pull request, not updating after a force push.


Could not load Qt module in Mac

Hi,
I'm using Mac OSX 10.10.2 Yosemite, julia 0.4.0-dev+3391. When I ran "using OpenCV", it told me
"WARNING: Could not add directory /Users/pengfei/Qt/5.3/clang_64/lib/ to clang search path!
ERROR: LoadError: LoadError: could not load module /Users/pengfei/Qt/5.3/clang_64/lib/QtCore.framework/QtCore_debug: dlopen(/Users/pengfei/Qt/5.3/clang_64/lib/QtCore.framework/QtCore_debug.dylib, 1): image not found"
I found "Qt_support.jl" is trying to find Qt in user's home directory
const qtlibdir = joinpath(homedir(),"Qt/5.3/clang_64/lib/"
After I reinstalled Qt into my home directory, it looks fine except a warning:
Warning: requiring "OpenCV" did not define a corresponding module.
but when I ran cvPoint(10, 10)
WARNING: [a,b] concatenation is deprecated; use [a;b] instead
in depwarn at ./deprecated.jl:40
in oldstyle_vcat_warning at ./abstractarray.jl:26
WARNING: [a] concatenation is deprecated; use [a;] instead
in depwarn at ./deprecated.jl:40
in oldstyle_vcat_warning at ./abstractarray.jl:26
WARNING: [a,b] concatenation is deprecated; use [a;b] instead
in depwarn at ./deprecated.jl:40
in oldstyle_vcat_warning at ./abstractarray.jl:26
Cxx.CppValue{Cxx.CppTemplate{Cxx.CppBaseType{symbol("cv::Point_")},(Int32,)},(false,false,false)}(UInt8[0x0a,0x00,0x00,0x00,0x0a,0x00,0x00,0x00])
This problem appeared in Cxx as well.

Sorry about the inconvenient path search for Qt.  I have to find a more general solution.
I will at least add this to the README so that it is more clear to everyone in the future.
The warning requiring "OpenCV" did not define a corresponding module. is not a problem; its a matter of declaring OpenCV.jl as a self-contained module.  I will change this soon.
The deprecation warnings (in Cxx.jl) are new to me. Obviously, the syntax of some array operations has changed recently and this has to be updated in Cxx.jl itself. Will you file an issue there?

Hi Maxruby,
Thanks for reply, yes, I have done that.


Always fire onCardLeftPlay when leaving play area.

Previously, if a card was played during set up, but then dragged back to
hand, any effects applied by the card would remain in place. The
reported example was The Arbor granting its +3 gold even though the
player moved it back to hand. This was because the onCardLeftPlay event
is relied upon by the effects engine and was explicitly not being fired
during the setup phase.
(during my brief testing this didn't seem to break anything but I can't really remember why it was written this way in the first place. No tests broke when removing the if, so whatever the reason it was apparently not important enough to test).

I think the reason was because previously putting cards in play in setup didn't raise any events.  You changed that so this should be fine


The readme should mention npm @types

The tsd repo points to here, but this tool is not required since TS2 was released and supports npm @types. The readme should mention that the tool is optional (or for legacy TS1 support?) to make it less confusing for returning users.

We'd love to, but people can't replace it yet thanks to https://github.com/Microsoft/types-publisher/issues/4. See https://github.com/typings/typings/pull/756.


createBankAccount

Hello, can i have help plz ?
I can create a user, create a wallet, but i can't create a bank account.
This function does nothing. No warnings... my callback is never called.
var api = new mangopay({...});
api.Users.create({...}, function(user) {
api.Users.createBankAccount(user.Id, {
"OwnerAddress": 'XXX',
"OwnerName": 'XXX',
"IBAN": 'FR3020041010124530725S03383',
"BIC": 'CRLYFRPP'
}, function(data){
console.log('BankAccount', data);
});
});

OK, after specifying Type: 'IBAN', it works.
However the issue is still there, i would really appreciate warnings or documentation about this case :)
thanks


Add ipfs fallback gateway support

Adds the following to support a fallback IPFS gateway:

Restructured the IPFS config to now contain primary and fallback config items..
Fallback config item is optional.
Updated HTTP module to use the fallback gateway incase an IPFS request has failed with the primary gateway.
Unit test updates

Codecov Report

Merging #82 (f118065) into main (943a1ad) will increase coverage by 1.59%.
The diff coverage is 71.59%.

@@            Coverage Diff             @@
##             main      #82      +/-   ##
==========================================
+ Coverage   35.83%   37.43%   +1.59%
==========================================
  Files          23       23
  Lines        1705     1822     +117
  Branches      376      399      +23
==========================================
+ Hits          611      682      +71
- Misses        854      874      +20
- Partials      240      266      +26

Impacted Files
Coverage Δ

src/config.rs
0.00% <0.00%> (ø)

src/proxy.rs
15.73% <ø> (ø)

src/http/mod.rs
70.16% <72.72%> (+0.01%)
:arrow_up:

src/rpc/mod.rs
53.21% <100.00%> (+0.33%)
:arrow_up:

src/http/hyper_client.rs
0.00% <0.00%> (-23.41%)
:arrow_down:


无法访问数据

1: beyond-hd 2022-10-01  Reason: Sign_in=> Url: https://beyond-hd.me redirect to https://beyond-hd.me/
2: dmhy 2022-10-01  Reason: Sign_in=> No permission to access data
3: hdcity 2022-10-01  Reason: Sign_in=> Sign in failed, no sign in
5: hdsky 2022-10-01  Reason: Sign_in=> No permission to access data
8: open 2022-10-01  Reason: Sign_in=> No permission to access data

检查baidu ocr


docs(versioning): clarify distribution channels configuration

Summary

update the documentation to be more clear about the branching and releasing strategy for the repository.

Change List (commits, features, bugs, etc)

update readme, contributing, versioning docs
reformat contributing with prettier (proseWrap)

Acceptance Test (how to verify the PR)

check my grammar and typos

:tada: This PR is included in version 2.140.0-next.3 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix/Update a broken link in readme

Description
Update a broken link in readme
Type of change

[x] Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Associated Issues
closes #3035
Checklist

[ ] Code in this PR is covered by automated tests (Unit tests, E2E tests)
[ ] My changes generate no new warnings
[ ] I have reviewed my own code
[ ] I have filled out all required sections
[ ] I have tested my changes on the preview link
[ ] Approver of this PR confirms that the changes are tested on the preview link

Seems these changes are merged with https://github.com/reown-com/appkit/pull/3130 - closing


Tooltip on buttons on iOS

On iOS you can't focus a button, it's therefore not possible to have the tooltip displayed on a button, without the button click event being executed
This is from your React DOM Interactions documentation example, I just added an alert on the onclick event:
https://codesandbox.io/s/nervous-wind-je0ytp
Is it possible to show the tooltip without having the alert appear? is this a bug? is a workaround needed?
On android you can trigger the focus event by holding for a long time, so the problem does not occur.

On android you can trigger the focus event by holding for a long time

To make it work on iOS we probably need to handle touch events and check for long presses. Maybe it should be a dedicated hook or a new prop for useHover or such.


Speed up project page by getting changesets in separate query

Fixes #330.

Currently failing with "TypeError: r.definitions is not iterable", which appears to come from our queryStore helper function in src/lib/sql/gql-client.ts.
TypeError: r.definitions is not iterable
    at getOperationType (file:///app/node_modules/.pnpm/@urql+core@4.1.1_graphql@16.6.0/node_modules/@urql/core/dist/urql-core-chunk.mjs:220:19)
    at Client.createRequestOperation (file:///app/node_modules/.pnpm/@urql+core@4.1.1_graphql@16.6.0/node_modules/@urql/core/dist/urql-core.mjs:676:77)
    at Module.queryStore (/app/node_modules/.pnpm/@urql+svelte@4.0.4_graphql@16.6.0_svelte@3.59.1/node_modules/@urql/svelte/dist/urql-svelte.mjs:47:20)
    at GqlClient.queryStore (/app/src/lib/gql/gql-client.ts:77:47)
    at load (/app/src/routes/(authenticated)/project/[project_code]/+page.ts:10:31)
    at Module.load_data (/app/node_modules/.pnpm/@sveltejs+kit@1.18.0_svelte@3.59.1_vite@4.4.9/node_modules/@sveltejs/kit/src/runtime/server/page/load_data.js:180:43)
    at async eval (/app/node_modules/.pnpm/@sveltejs+kit@1.18.0_svelte@3.59.1_vite@4.4.9/node_modules/@sveltejs/kit/src/runtime/server/page/index.js:179:13)

@myieye Would you like to take a look at the changes in this PR (not much so far) and see if you can figure out where this "definitions" property is coming from?

The r.definitions error appears to be an issue with changing GQL queries while running skaffold dev or task up. Quitting and re-running skaffold, so that the lexbox-ui container builds from scratch, gets rid of the issue. Now I'm getting an "entries is not iterable" error, which at least makes some sense.

Got the data flow correct this time (subscribing to a store inside a promise isn't quite as straightforward as I might like), so it looks like this PR is ready for review.

After mucking around with (and overcomplicating) this, I finally refactored the gql-client to not always wrap query-store results in a promise and now I think it landed in a good spot.


Visibility of matchCommand function

I found matchCommand very useful in my command handlers like SENSE:FUNC:
scpi_result_t sense_function(scpi_t* context) {
  const char* param;
  size_t param_len;

  if (!SCPI_ParamText(context, &param, &param_len, TRUE)) {
    return SCPI_RES_ERR;
  }

  if (matchCommand("VOLTage", param, param_len)) {
    // switch to DC voltage
  } else if (matchCommand("VOLTage:RATio", param, param_len)) {
    // switch to DC voltage ratio
  } else...`
}

But visibility of matchCommand prevents using it in my code. Could you change its visibility or add a public wrapper function?
Thanks

SCPI_ParamChoice is not enough for you? It does not support ":" in the name and it can't support it because of IEEE488.2 but it is very similar to your task.
You can define the list by array
const char * sense_function_list[] = {
    "VOLTage",
    "VRATio",
    NULL /* termination of option list */
};

scpi_result_t sense_function(scpi_t* context) {
    int32_t param;
    if (!SCPI_ParamChoice(context, sense_function_list, &param, true)) {
        return SCPI_RES_ERR;
    }

    switch(param) {
        case 0:
            // handle voltage
            break;
        case 1:
            // handle voltage ration
            break;
        default:
            return SCPI_RES_ERR;
    }
    return SCPI_RES_OK;
}

And later call
SENSE:FUNC VOLT
SENSE:FUNC VRAT

Unfortunately SCPI_ParamChoice is not an option. Argument can have a colon, e.g. VOLTage:DC, and this is standard value. If I simply change it then I lose compatibility with other SCPI devices.
Could you add a preprocessor directive to change visibility?


Authorization problem

when I testing Authorization service,it reports this error:

my auth.py is

the rtg_config.json is

Hello, the output of the script should be a JSON. In your case, I think you just put JSON data in a .py file.
To fix this you could:

completely remove the authCommand line from the rtg_config.json file, in case your API does not require authentication
change the authCommand to cat auth.py (or Windows equivalent command) to make the command print out the content of the file
change your python script to print out JSON

Please let me know if you managed to run the code.


fix Filter out all not running tablets if cumu compaction for shadow tablets is disabled (#42245)

Proposed changes
pick: #42245
As title. If cumu compaction for shadow tablets is disabled, shadow tablets may be picked to do cumu compaction and result in error status.

run buildall