On mac OS, joinThread hangs after calling puppy.fetch in the thread

In one of my projects, i'm creating a thread and making network requests from it using puppy. When i'm done, i send a signal that stops the thread and then i wait for the thread to finish using joinThread. With puppy 1.0.3 this worked, but after updating to 1.4.0 i found that joinThread doesn't return.
Here's a minimal example:
https://gist.github.com/oakes/c12bc0e7ff3e6d256dd7f9e41ca8efa4
With puppy 1.0.3 it prints:
Fetch success!
Stopped client thread

With puppy 1.4.0 it prints:
Fetch success!
objc[17434]: NSConcreteMutableData object 0x7fca4400f9d0 overreleased while already deallocating; break on objc_overrelease_during_dealloc_error to debug

I'm on mac OS 10.15.7. I tested on ubuntu 20.04 and it seems to work fine there so this is probably only a mac OS issue.
Also, thank you for this library :D

Hello and thanks for reporting the issue and especially thanks for the minimal example.
Currently I am unable to reproduce this issue. I've tried on my M1 Pro (12.1) which not the same as 10.15 but it is what I've got. I also added it to our GitHub Actions and it passed on Mac: https://github.com/guzba/puppy/runs/4822347092?check_suite_focus=true#step:11:136
I ran it with and without --gc:arc. Do both fail with the same error for you?
A further note, the current Channels in Nim is not recommended and the replacement is https://github.com/nim-lang/threading See https://github.com/nim-lang/Nim/issues/19105#issuecomment-974057788 for context and more info.

With arc enabled i get:
Fetch success!
No stack traceback available
SIGSEGV: Illegal storage access. (Attempt to read from nil?)

Without arc it just hangs like i described above. Maybe this only happens on 10.15...i'm too afraid to update macos since other things could break.

I am at M1 macOS 11.3.1. I get no issue running the test case.
Nim Compiler Version 1.6.2 [MacOSX: amd64]

Another anecdote: I have 10.14.16 on a different Mac and test_issue48.nim passes there with both arc and default GC. (Nim 1.6.2, puppy current #head / 1.5.0)

Actually, that test passes for me too. And when i do nimble develop my own example now runs fine. This must have been fixed after 1.4.0 so i'll close this.


One more open source project

Maybe this can be added https://github.com/jaysavsani07/FlutterBMI
Also, I think now each project are able to have a web demo, I'll glad to help with that

No response


Add lints for v2.0

See https://github.com/dart-lang/lints/projects/1.
Fixes https://github.com/dart-lang/lints/issues/64
Fixes https://github.com/dart-lang/lints/issues/42
Fixes https://github.com/dart-lang/lints/issues/23
Fixes https://github.com/dart-lang/lints/issues/71
Fixes https://github.com/dart-lang/lints/issues/61
Fixes https://github.com/dart-lang/lints/issues/66
Fixes https://github.com/dart-lang/lints/issues/68
Fixes https://github.com/dart-lang/lints/issues/67
Fixes https://github.com/dart-lang/lints/issues/70
Fixes https://github.com/dart-lang/lints/issues/58

/cc @mit @pq @srawlins

I believe we are ready to submit this PR. @pq or @mit-mit can you review it?

🚀

I am just waiting on 2.17.0-206.0.dev to successfully roll into Flutter before submitting this PR. This is the PR to watch for the roll: https://github.com/flutter/flutter/pull/100270


Fixes Android search by replacing horsey with pixabay autocomplete.

Horsey is broken on Android so search doesn't work.
I've fixed it by replacing horsey with Pixabay's autocomplete code.
I've already fixed this in hugo-theme-learn
One drawback of pixabay is that you have to press the down arrow at least once, whereas with horsey you can just press enter to visit the first suggestion. This could probably be tweaked, but it is not an option in the original source.

Thanks !


Added indexOf to stringUtils.sol

This is my first ever code contribution to an open source project. Be gentle...

Thanks a lot for the pull request!
It would be great if you could make some small adjustments.
In the long run, we should implement something like Knuth-Morris-Pratt or Boyer-Moore.

Ok I updated my branch. Can you see and merge the changes?


time: per-thread time.now() function

Closes https://github.com/google/starlark-go/issues/516.
p.s. there are quite a few changes that go fmt wants to make. I kept them out of this PR.

p.s. there are quite a few changes that go fmt wants to make. I kept them out of this PR.

Thanks. I've posted https://github.com/google/starlark-go/pull/519.


Section Footer text overlaps with cell content on 4 inch screen

I don't think it is related to this Framework. Does the issue only occur when table view is added to one of the side views?
Feel free to reopen if it is really related to LGSideMenuController itself.


Engine: Implement Implicit Type Casting

Problem
Currently the Engine enforces strict data typing when assigning to the attribute.
For example compiling using the following component types:
Velocity = ComponentDef(
    name="velocity",
    schema={
        "x": types.float64,
    },
)

Keyboard = ComponentDef(
    name="keyboard",
    schema={
        "key": types.char,
    },
)

Compiling the following system:
@sim.system
def issue_sys(g: Plotter):
    controls = g.entity(components=[Keyboard])
    controls[Keyboard].key = ord("a")

    car = g.entity(components=[Movement, Velocity, Position, Meta])
    car[Velocity].x = 2

generates the following Graph:
outputs:
- mutateAttr:
    attribute: key
    component: keyboard
    entityId: 1
  toNode:
    constOp:
      heldValue:
        dataType:
          primitive: INT32
        primitive:
          int32: 97
- mutateAttr:
    attribute: x
    component: velocity
    entityId: 2
  toNode:
    constOp:
      heldValue:
        dataType:
          primitive: INT32
        primitive:
          int32: 2

causing the Engine to produce these Error message:
Something went wrong while running the initGraph of the simulation: Data type of given value does not match schema type for attribute key.
Something went wrong while running the initGraph of the simulation: Data type of given value does not match schema type for attribute x.

Investigation

The SDK's Graph Compiler infers the types of 2 and 97 (ord("a") == 97) as INT32 and generates mutateAttr assigning them to x and key  of float64 and char types respectively.
The Engine employing strict type checking finds that the data types don't exactly match for these assignments INT32 != float64, INT32 != char and produces the error.

Proposed Fix

[ ] Implement implicit type casting on the Engine to be used when the types do not exactly match. Type casting should follow C++ semantics

The engine side cannot fully implement implicit type casting as the engine does not know what are the intermediate variable types. For example, if we have an int32 and int64 and we add them I need to know that the result is int64.
This makes it non-trivial for the engine side and I believe, for the SDK side as well. Both sides, in the end, have to have some mapping between two type operations and the resulting type.
What the engine can do is cast for mutateOp. This is possible because the attribute data type is known.

After more experimentation, I have found that it is quite possible to use C++ semantics on intermediate variable types. This is done by replacing fixed setters given by protobuf (like set_int_64()) with templated setters which deduce the type (e.g. set(protoVal, T val). In doing so, we let C++ determine the type to set.
For operations like max where two possible types may be returned, the type that results from summing the two types is returned. This type can be determined by using std::declval and decltype:
auto max = []<class X, class Y>(X x, Y y) {
    typedef decltype(std::declval<X>() + std::declval<Y>()) ReturnType;
    // ...
}


create cookbook about VRaptor + AngularJS

just a simple example, we've a lot of users asking about it

I'm working on this in pair with @linyatis.

@Turini
I've made something about it on my personal blog (https://pedrohosilva.wordpress.com/2014/12/29/aplicacao-web-com-vraptor-4-pt1/), but I can do it smaller and more formal. I think it's something like what you want.
Can I do it in order to finish this issue?

hi @pedro-hos! It'd be great, but i'm not sure if linyatis is still working on it.
Could you confirm that, @linyatis?
And maybe you guys could change ideas about this ;) as many, as better

Hey all! @Turini, sorry for the delay with this cookbook =(
@pedro-hos, I did an example app for this cookbook, but I could not finish the text. Do you want to write this together?

@linyatis  great, we can write together. What have you done?

esta em algum repositório esse cookbook? Gostaria de ajudar tambem..

Hey all! Any progress about that cookbook? I like to help

hey guys, i'm sure any help will be very welcome here.
anyone whats to write a quick tutorial providing a simple usage example?


[test] Improved repo-check GH action - PR in mfem repo

It may be nice if the "skipped" checks above are not shown (at least not in the PR summary).
Unfortunately there doesn't seem to be a way to do that.

Discussion continued in https://github.com/mfem/mfem/pull/3001


Update polybase-linux-setup.md

RECONFIGURE [WITH OVERRIDE]; this errors out with syntax error on both SSMS and ADS it should be RECONFIGURE WITH OVERRIDE;

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

@pradm Thanks for the fix and apologies for the delay.


bump Go 1.20

[ ] Updated Unreleased section in CHANGELOG or it's not notable changes.

Thanks!


Pp 11237

WHAT YOU DID
Given CardPayment is under the uk.gov.pay.api.model package, having links is always going to be part of the API response for a card, and we are never going to use CardPayment as a database model, so we can move links information into it and delete a bunch of classes.
Payment can be deleted. We used to have a direct debit payment model, hence this super class but this is no longer needed.
Deleted the following classes:
PaymentWithAllLinks
Payment
PaymentLinksForSearch
GetPaymentResult
Documentation

[ ] Updated README.md for any of the following ?

Introduced any new environment variables / removed existing environment variable
Added new API / updated existing API definition

I don't know for sure but I have a hunch that one of the reasons for the distinction between PaymentsWithAllLinks and without was to make it clear in auto-generated API docs that the request payload didn't require to have links included.
I'm not sure now what Pay's API documentation strategy is but it would be worth double checking the consequences of this refactor on that? Did we move to having a separate curated api spec doc rather than using the auto-generated one?

I don't know for sure but I have a hunch that one of the reasons for the distinction between PaymentsWithAllLinks and without was to make it clear in auto-generated API docs that the request payload didn't require to have links included.
I'm not sure now what Pay's API documentation strategy is but it would be worth double checking the consequences of this refactor on that? Did we move to having a separate curated api spec doc rather than using the auto-generated one?

PaymentsWithAllLinks are only used in responses and doesn't affect requests. I believe we're using an auto-generated spec.


add brave search tool

add tool for Brave Web Search API to query Brave Search and get back search results from the web

Disclaimer: This review was made by a crew of AI Agents.
Code Review Comment: Brave Search Tool Implementation
Overview
This pull request introduces a Brave Search Tool with three main components: README.md, brave_search_tool.py, and brave_search_tool_test.py. The implementation demonstrates a solid foundation but requires several enhancements for improved robustness and user guidance.
1. Code Structure and Organization
Positive Aspects:

Separation of Concerns: Clear delineation between documentation, implementation, and testing, which aids maintainability.
Type Hints and Validation: The use of type hints and Pydantic contributes to code clarity and harnesses Python's type system effectively.
Inheritance: Utilizing a base class (BaseTool) promotes code reuse and can simplify future extensions.

Areas for Improvement:
1.1 Missing __init__.py
Recommendation: Add an __init__.py file in the brave_search_tool directory to ensure it functions correctly as a Python package. This change will facilitate importing the module in other parts of the codebase.
1.2 Enhanced Module Documentation
The module-level docstring can be improved to better convey its functionalities:
"""
BraveSearchTool - A tool for performing web searches using the Brave Search API.

This module provides functionality to search the internet using Brave's Search API,
supporting customizable result counts and country-specific searches.

Dependencies:
    - requests
    - pydantic
    - python-dotenv (for API key management)
"""

2. Implementation Issues
2.1 Lack of Error Handling
The current implementation lacks sufficient error handling to address networking and validation issues. Here’s an improved error handling example:
def _run(self, **kwargs: Any) -> Any:
    try:
        search_query = kwargs.get("search_query") or kwargs.get("query")
        if not search_query:
            raise ValueError("Search query is required")

        response = requests.get(self.search_url, headers=headers, params=payload)
        response.raise_for_status()  # Handle non-200 responses

        results = response.json()
        return results
    except requests.RequestException as e:
        return f"Error performing search: {str(e)}"
    except KeyError as e:
        return f"Error parsing search results: {str(e)}"

2.2 API Key Validation
It's crucial to validate the API key during initialization to prevent runtime errors:
def __init__(self, *args, **kwargs):
    super().__init__(*args, **kwargs)
    if "BRAVE_API_KEY" not in os.environ:
        raise ValueError("BRAVE_API_KEY environment variable is required for BraveSearchTool")

2.3 Correct Date Import
Correct the import statement in the _save_results_to_file method:
from datetime import datetime  # Ensure this is included

def _save_results_to_file(content: str) -> None:
    filename = f"search_results_{datetime.now().strftime('%Y-%m-%d_%H-%M-%S')}.txt"
    # ... additional file handling code ...

3. Testing Improvements
3.1 Test File Enhancements
The test suite can be strengthened to ensure broader coverage and better fault tolerance:
import pytest
from unittest.mock import patch
from crewai_tools.tools.brave_search_tool import BraveSearchTool

@pytest.fixture
def brave_tool():
    return BraveSearchTool(n_results=2)

def test_brave_tool_initialization():
    tool = BraveSearchTool()
    assert tool.n_results == 10
    assert tool.save_file is False

@patch('requests.get')
def test_brave_tool_search(mock_get, brave_tool):
    mock_response = {
        'web': {
            'results': [
                {
                    'title': 'Test Title',
                    'url': 'http://test.com',
                    'description': 'Test Description'
                }
            ]
        }
    }
    mock_get.return_value.json.return_value = mock_response

    result = brave_tool.run(search_query="test")
    assert 'Test Title' in result
    assert 'http://test.com' in result

4. Additional Recommendations
4.1 Rate Limiting
Implement a rate-limiting mechanism to avoid overwhelming the API:
from time import sleep

class BraveSearchTool(BaseTool):
    _last_request_time: ClassVar[float] = 0
    _min_request_interval: ClassVar[float] = 1.0  # seconds

    def _run(self, **kwargs: Any) -> Any:
        current_time = time.time()
        if (current_time - self._last_request_time) < self._min_request_interval:
            sleep(self._min_request_interval - (current_time - self._last_request_time))
        self._last_request_time = time.time()
        # ... invoke search logic ...

4.2 Result Caching
Consider implementing a caching mechanism to improve performance for repeated searches:
from functools import lru_cache

class BraveSearchTool(BaseTool):
    @lru_cache(maxsize=100)
    def cached_search(self, query: str, n_results: int) -> str:
        # Implement search logic here with caching

5. Documentation Improvements
README.md Suggestions
The README.md file is generally good but could include:

Examples of API responses and their structure.
Detailed instructions for usage scenarios.
Clarifications on error handling, potential issues, and rate limiting practices.
Setup instructions for required environment variables.

Conclusion
While the Brave Search Tool is a promising start, several improvements are necessary to enhance error handling, validation, and documentation. Prioritize the following:

Implement comprehensive error handling.
Validate the API key on initialization.
Expand the test suite for better reliability.
Enhance documentation for more clarity.

These enhancements will lead to a more robust, user-friendly, and maintainable tool. Thank you for your contributions!

@joaomdmoura Made the changes as per your suggestions.

Love it @siddas27 great work! merging


error Trying to upgrade from newer version "0.59.9" to older "0.59.10"

React Native version:
info
  React Native Environment Info:
    System:
      OS: macOS 10.14.5
      CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
      Memory: 1.57 GB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.15.1 - ~/.nvm/versions/node/v10.15.1/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.9.0 - ~/.nvm/versions/node/v10.15.1/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
    IDEs:
      Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.9 => 0.59.9
    npmGlobalPackages:
      react-native-rename: 2.4.1

Steps To Reproduce

In a React native 0.59 project folder run
 react-native upgrade

Describe what you expected to happen:
Upgrade RN version
Snack, code example, or link to a repository:
I get:
info No version passed. Fetching latest...
error Trying to upgrade from newer version "0.59.9" to older "0.59.10"

This is fixed in the<EMAIL_ADDRESS>please update to this version (by removing cli from lockfile and reinstalling)


the videos in funQA dataset

hi ~thanks for releasing this excellent work to the public! But it seems that there is only annotations json file released, how can i donwload the videos in train/val/test sets.

Thanks for your interest in our work!
We are preparing for the FunQA contest this week. We will release all the material and data just these days!
Stay tuned!

Please checkout here:
https://entuedu-my.sharepoint.com/:f:/g/personal/jingkang001_e_ntu_edu_sg/EmBja9v8w4NAgqVmLC_xZ2QBKD1a2vjzxpW-QZisk1sc-g?e=bSbdQg

Hi @Jingkang50 ! Thank you very much for sharing the link! Could you please verify if it is still working because I cannot access on my end? That would be very helpful


Cluster-GCN: How to achieve mirco-F1=0.966 on Reddit?

I run the code of Cluster-GCN with the default parameters in run_reddit.sh, but the micro-F1 I get is 0.962. What's the optimized parameters for Reddit dataset?

I have a similar question: Why the parameters used here are different from the parameters in your paper?


Support for Elliptic Curve (EC) key types

When trying to connect Azure B2C with another IdP, using custom policies, we encounter the following error in AppInsights logging:
Key type not supported: 'EC'.
and it bails out with a FatalException
The IdP we're trying to connect to supports RSA and EC key types, and sends both of them in the JWKS endpoint.
B2C does not seem to handle the EC key type in the JWKS.
Could you please fix this? Or is there any setting in B2C we could use to prevent the error from happening?
Thanks in advance

Any workaround to clear error?
https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/38510968-aad-b2c-add-support-for-ec-key-type-to-openid-con


change the issuer for a certificate

I have a certificate issued with a ClusterIssuer using a HTTP01 ACME challenge. Because of recent security restrictions (a firewall), I can't renew it. But can I change its ClusterIssuer to a DNS01 one, in order to renew it?
I tried with kubectl patch with and kubectl edit with no success:
Before:
$ kubectl get certificates.cert-manager.io tls-certificate -o=jsonpath='{.spec.issuerRef}' | jq
{
  "group": "cert-manager.io",
  "kind": "ClusterIssuer",
  "name": "letsencrypt-prod"
}

Trying to patch:
$ kubectl patch certificates.cert-manager.io tls-certificate -p '{"spec":{"issuerRef":{"name":"letsencrypt-prod-cloudflare"}}}'
Error from server (UnsupportedMediaType): the body of the request was in an unknown format - accepted media types include: application/json-patch+json, application/merge-patch+json, application/apply-patch+yaml

Editing seems not to fail:
$ kubectl edit certificates.cert-manager.io tls-certificate
certificate.cert-manager.io/tls-certificate edited

... but the certificate still hasn't changed:
$ kubectl get certificates.cert-manager.io tls-certificate -o=jsonpath='{.spec.issuerRef}' | jq
{
  "group": "cert-manager.io",
  "kind": "ClusterIssuer",
  "name": "letsencrypt-prod"
}

Thanks!

A certificate will not be re-issued because issuer spec has changed. You can see in which cases it will get re-issued here https://cert-manager.io/docs/faq/#when-do-certs-get-re-issued.

Actually I ended up re-creating the certificate. In order to minimise the downtime, I did it like this:
export BACKUP_PATH=/some/path/on/your/computer/
# we assume the secret and the certificate have the same resource name, in this case, `tls-certificate`:
export CERT=tls-certificate

kubectl get certificates.cert-manager.io $CERT -o yaml > $BACKUP_PATH/$CERT-certificate.yaml
kubectl get secrets $CERT -o yaml > $BACKUP_PATH/$CERT-secret.yaml

cp $BACKUP_PATH/$CERT-certificate.yaml $BACKUP_PATH/$CERT-certificate.bak
vim $BACKUP_PATH/$CERT-certificate.yaml

(change the ClusterIssuer to the DNS01 one; clean up...)
kubectl delete certificates.cert-manager.io $CERT
kubectl delete secret $CERT

kubectl apply -f $BACKUP_PATH/$CERT-certificate.yaml

and it worked!


🐛 [firebase_crashlytics] iOS crash logs missing exception type, message, termination reason

Bug report
Describe the bug
On Flutter we get crashlytics bugs that only include stack traces, but are missing what the exception actually was.  For example on a native iOS crash at the top might say:
Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: DYLD 1 Library missing
Library not loaded: @rpath/App.framework/App

but the crashlytics bugs we get don't have that info, just the stack trace.  I'm not sure if this a flutterfire plugin issue, or an underlying crashlytics limitation on iOS.
Steps to reproduce
Throws exception and see the app crash.  Check crashlytics logs for exception reason.
Expected behavior
Expect to see what exception was thrown, any related messages, termination reason, etc.
Additional context
Example report: https://github.com/flutter/flutter/issues/113014
Flutter doctor
From same report:
Click To Expand
Flutter 3.0.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision https://github.com/flutter/flutter/commit/ee4e09cce01d6f2d7f4baebd247fde02e5008851 (5 months ago) • 2022-05-09 16:45:18 -0700
Engine • revision d1b9a6938a
Tools • Dart 2.17.0 • DevTools 2.12.2

Thanks for the report @jmagman :)
I think this could be related / similar to https://github.com/firebase/flutterfire/issues/3534 which got closed due to no activity further. https://github.com/firebase/flutterfire/issues/3534#issuecomment-935720155
Keeping this issue open and labeling for further insights from the team.
/cc @russellwheatley

Hey @jmagman, It looks like the crash is coming from the Flutter SDK's native side, I don't think it is occurring in the Dart side.
All errors in Flutter are caught using the PlatformDispatcher.instance.onError or FlutterError.onError handler depending on sync/async.
We have a PR for updating the docs and Crashlytics example app to use PlatformDispatcher.instance.onError as that is a recent change to Flutter, and you can see how that is implemented here.
This setup produces crash reports showing the Dart stack trace like so:

The crash report you linked is pure native. It also looks like it was automatically triggered (i.e. not sent using Firebase Crashlytics API). As an aside, the pubspec.yaml contained here: https://github.com/flutter/flutter/issues/113014 doesn't have any FlutterFire plugins mentioned, but I assume the reporter just missed firebase_crashlytics from the report.
Hope that helps!

Closing this out as it isn't a problem with the firebase_crashlytics plugin.


Login in failed with Google Account

Hi all,
I'm trying to log in with my google account, but it says: "OpenID 2.0 for Google-accounts has ended".
So I'm not able to login at the website anymore.

We are on it :) Expect it working by the end of the week.
Thanks.

Dear @Lieke22 it should work now. Please test and let us know it's all good.

it does work now.


windows7 import modules of installed app from app_packages

First off, thank you for the awesome beeware projects!!
I built a little gui toga helper app for my colleagues, that helps
them archiving their mails from Outlook in a more efficient way.
(for that I use the non-std packages psutil and pywin32)
The app works well on my dev machine (windows7 python 3.6)
straight from the IDE(pyCharm), but when I install it, the installed
app refuses to load.
The temperature converter from the examples does not have that
issue and also works installed.
So I went ahead and redirected stderr to a text file:
(maybe this is worth adding into a troubleshooting section in readthedocs(?))
python/pythonw.exe app/start.py 1>stdout.txt 2>stderr.txt
according to this SO post:
https://stackoverflow.com/questions/9705982/pythonw-exe-or-python-exe#30313091
This showed me that the modules could not be found by pythonw
although they were nicely downloaded packaged up in app_packages.
As a quick&dirty test I threw in:
import sys
print("pre_imports")

for p in sys.path:
    print(p)

app_pkg = "D:/outlook_mail_exporter/windows/content/app_packages"
w32_dir = os.path.join(app_pkg, "win32")
w32_lib_dir = os.path.join(w32_dir, "lib")
sys.path.extend([app_pkg, w32_dir, w32_lib_dir])

for p in sys.path:
    print(p)

import pywintypes
print("pywintypes imported!")
import win32api
print("winapi32 imported!")

to find that the app actually works, if append the path to sys as shown above.
I am a bit puzzled by this behavior, as this seems to be what start.py is doing already?
Do you have an idea/hint why I needed the extra sys-path appends?
Thank you!

..maybe related to #46 ?

Over the years pywin32 module has often had issues with the path and imports due to the different ways it's tried to install and then find it's bundled DLL libraries.
Your issue is probably related to this.
The actual error message when it fails, doors it refer to not being able to lead a DLL?
Either way, of your path changes above work I wouldn't worry about it too much.
I can check on Monday what we do for pywin32 if it helps. I know I've got some manual path fixups to work when running from source, can't remember if I had to fix it for running from briefcase... although I've rewritten start.py to work with our application compiled through nuitka rather than from source.

Ah I see.
Well then I guess it is a pywin32 thing - so I just leave a nicer version of my sys path fix in.. (-:
Thanks a lot!
btw:
It seems (without my fix) that it gets until the __init__.py of win32com and gets stuck there (so no dlls involved):
Traceback (most recent call last):
  File "app\start.py", line 9, in <module>
    from outlook_mail_exporter.app import main
  File "app\outlook_mail_exporter\app.py", line 24, in <module>
    import win32com.client
  File "app_packages\win32com\__init__.py", line 5, in <module>
    import win32api, sys, os
ModuleNotFoundError: No module named 'win32api'


Reworks gas meters by refactoring into a special smart meter type.

Connects to #274

SonarQube analysis reported 11 issues:

 6 major
 5 info

Watch the comments in this conversation to review them.
Note: the following issues could not be reported as comments because they are located on lines that are not displayed in this pull request:

 Method has 8 parameters, which is greater than 7 authorized.
 Private method 'prePersist' is never used.
 Constructor has 9 parameters, which is greater than 7 authorized.
 Private method 'preUpdate' is never used.
 Override this superclass' "equals" method.

All is well.

LGTM


[Feature]: Add support for new Account parameters ADMIN_USER_TYPE etc

Use Cases or Problem Statement
Snowflake is introducing new parameters for account creation, specifically relevant for use cases where accounts are created programmatically.
As part of our continued effort to improve our customer security, we recently announced enforcement of MFA by default for new Snowflake accounts. This change will be introduced as part of BCR Bundle 2024_08 and your account will be impacted by this change. This bundle is expected to be deployed for testing during the week of October 7th, 2024 in release 8.38.  Please note dates are subject to change.
Details of the changes are below:
What you need to do
We recommend following the steps in this whitepaper and this video. More specifically:
When creating new accounts programmatically, use the newly introduced ADMIN_USER_TYPE property for the admin as part of account creation
CREATE ACCOUNT  [ ADMIN_USER_TYPE = PERSON | SERVICE | LEGACY_SERVICE | NULL ]
For human users, set ADMIN_USER_TYPE=PERSON. PERSON users will be subject to MFA policies.
For service users, set ADMIN_USER_TYPE=SERVICE. SERVICE users will not be subject to MFA policies.
Service users will not be allowed to use passwords by policy and the caller should specify ADMIN_RSA_PUBLIC_KEY instead of admin password as part of account creation.
If your service users cannot use key pair authentication, set ADMIN_USER_TYPE=LEGACY_SERVICE during account creation and continue setting up passwords. LEGACY_SERVICE users will not be subject to MFA policies.
LEGACY_SERVICE  users are not allowed to log in via UI and  cannot have a first name / last name. See this link for more details.
LEGACY_SERVICE is a temporary solution and we highly recommend that you fix your tooling.
Read more about user types and their limitations in the create user documentation.
For users created after a new account is bootstrapped
Make sure to mark the TYPE for all users
For human users TYPE=PERSON, follow the DUO enrollment process and start using MFA
For service users TYPE=SERVICE, make sure to either: 1) use external OAuth (preferred), or 2) use key pair authentication combined with network policy.
If a service user cannot leverage a key pair, mark them as TYPE= LEGACY_SERVICE. This is a temporary solution and we highly recommend that you fix your deployment based on the above.
This feature request would be to update the Account resource to support the newly introduced arguments/parameters, and also update the User resource to support the Snowflake TYPE setting (e.g. TYPE = "SERVICE" or TYPE = "PERSON".
Having had a look, I can see some sort of awareness of this as a //TODO comment in: https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/97fa9b4485cf26c5bf93dedfe3b88f688a71b3e6/pkg/resources/user.go#L206C1-L206C14
[SNOW-1645348]: revisit with service user work
Category
category:resource
Object type(s)
resource:account
Proposal
Update the Account resource
How much impact is this issue causing?
Low
Additional Information
No response
Would you like to implement a fix?

[ ] Yeah, I'll take it 😎

Hey @sean-stage. Thanks for reaching out to us.
We have it on our radar. We will check if the new syntax breaks the current account resource implementation this or early next week and adjust it if needed. I will ;eave a comment in this issue after these tests.
The new parameters will be handled no sooner than with the account resource rework (https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/v1-preparations/ESSENTIAL_GA_OBJECTS.MD) that is incoming. Before that you can use https://registry.terraform.io/providers/Snowflake-Labs/snowflake/latest/docs/resources/unsafe_execute to change the type.

Thanks for the response Artur @sfc-gh-asawicki

Hi @sfc-gh-asawicki Artur, any progress on this front? Snowflake Trust Center is now flagging accounts without MFA around this, and it'll be nice to ensure programatically created service style accounts are set to the correct 'type' via Terraform.

Hey, yes: https://github.com/Snowflake-Labs/terraform-provider-snowflake/pull/3236/files#diff-cbd81edd0019b2c801bdab54fa0e2697ee800d9f381edbebe4899eb20fa83bedR52.

Hello 👋
Recently, we released v0.100.0 and v1.0.0 that contains reworked account resource. The the admin_user_type is supported there, please migrate with the use of migration guide and let us know if the issue can be closed. Thank You :)


Injectable Modules, Named configuration data, and Injected Commands

We have made a number of additions to dropwizard-guice.
I'm thinking the upgrade to Dropwizard 0.8 might be a good chance to see if any of these additions would be of interest to the project (the attached code is currently based off my 0.8 update PR).
The additions are (usage descriptions can be found in the updated readme):

Injectable Modules Allows for singletons with config data, etc.  This is accomplished through double injection.  The InitModules are initialized first, at Dropwizard initialization.  During the Dropwizard run phase, after the environment and config data is added, the rest of the modules are injected and a child injector is created from these modules.
Named config data Each field in the Configuration object is bound and named based on the field name (done recursively for any sub-config objects found in scope).  This allows you to inject a String with @Named("defaultPerson.name") instead of injecting the configuration object and doing config.getDefaultPerson().getName().  We have found this to be particularly useful when sharing Bundles between projects.  The code using the config data doesn't have to take a dependency on the actual config object.
InjectedCommands A set of Command types that allow for full injection of config data and other modules.  These were needed because Command objects must be initialized and passed to Dropwizard before the Configuration and Environment data exists.
Integration Tests The start of tests for these features and the rest of dropwizard-guice.

Fantastic work @oillio and @yunspace. I found a bug in jersey2-guice that caused
@Qualifier
@BindingAnnotation

to not be injected into the jersey resources (https://github.com/Squarespace/jersey2-guice/issues/22) properly. Hopefully they'll accept my PR (https://github.com/Squarespace/jersey2-guice/pull/23) and then let's upgrade the dependency. I thought you should know as I first suspected that it was the order we initialize things in that was the culprit, but it wasn't!

@jontejj Thanks.  Let me know when jersey2-guice accepts your patch and I will rev the dependency version.

Will do. I think he tried to merge my PR but got formatting issues. Soon...
On Feb 18, 2015 7:14 PM, "Dan Jasek"<EMAIL_ADDRESS>wrote:

@jontejj https://github.com/jontejj Thanks. Let me know when
jersey2-guice accepts your patch and I will rev the dependency version.
—
Reply to this email directly or view it on GitHub
https://github.com/HubSpot/dropwizard-guice/pull/46#issuecomment-74916293
.

@yunspace and @jontejj
I am getting tired of maintaining two branches and it looks like HubSpot has all but abandoned this project.  I think Elias is no longer with HubSpot as well.
I am thinking about forking the project, registering it with Maven Central, and using this branch as the mainline.  The three of us seem to be the most active users.  So, a survey:
Do you agree that moving to a fork is waranted?
Do you like the improvements made in this branch, and do you agree this should be the mainline?

We have definitely not abandoned this project! We have 200+ services in production using dropwizard-guice and have no plans to use something else. Unfortunately we are still on dropwizard 0.6, but I can try to this and #45 merged into master and cut a new release

@oillio @jontejj @HiJon89 whilst I think staying on the mainline is good to leverage the existing community base, I do feel that it may be slightly overwhelming for HubSpot to support new features and issues related to dropwizard 0.8 when the bulk of their services are on 0.6.
Also #45 is practically a different code base using a third party library. The core GuiceContainer is replaced by HK2Linker and friends. All the tests written so far are also aimed at DW0.8 using Jersey2-Guice
There is no doubt the good folks at HubSpot have built a pretty stable foundation in dropwizard-guice. Rather than spreading support across versions 0.6, 0.7 and 0.8 which are all drastically different, perhaps now is a good time to make a fork and delegate DW 0.8 + Jersey2 support to teams who are actively building 0.8 services.
Just my 2 cents. But if we do need a fork, I actually have Continuous Delivery pipeline and unofficial BinTray repository set up for #45 (just need to change namespace etc):
https://snap-ci.com/Trunkplatform/dropwizard-guice/branch/master
https://bintray.com/trunkplatform/dropwizard-modules/dropwizard-jersey2-guice/view

Thanks @HiJon89.  Sorry to jump the gun.  After 3 moths without a commit or comment I was just getting a bit nervous.
I don't care who owns the project so long as we get timely releases and code reviews; I don't want to have to continue to maintain a private build and branch.
If you need help maintaining the 0.8 branch, I am happy to help.

I'm happy to help support 0.8 release also if this project will remain active and timely. Once the 0.8 changes are merged, I can point my CI setup back to here.

We are still here. My office is a few blocks from HubSpot and I am using 0.7 but I could move easily to 0.8 since I only have two services in my new company so far.
I am away this weekend so let's get this sorted out Monday. I have been meaning to catch up on .8 and jersey 2.
—
Sent from Mailbox
On Fri, Feb 20, 2015 at 6:01 PM, Dan Jasek<EMAIL_ADDRESS>wrote:

@yunspace and @jontejj
I am getting tired of maintaining two branches and it looks like HubSpot has all but abandoned this project.  I think Elias is no longer with HubSpot as well.
I am thinking about forking the project, registering it with Maven Central, and using this branch as the mainline.  The three of us seem to be the most active users.  So, a survey:
Do you agree that moving to a fork is waranted?
Do you like the improvements made in this branch, and do you agree this should be the mainline?
Reply to this email directly or view it on GitHub:
https://github.com/HubSpot/dropwizard-guice/pull/46#issuecomment-75335557

@oillio I don't like the idea of binding configuration properties using @Named because of the chance of collisions with apps that might already be binding similarly named properties, thoughts on making a new annotation for this purpose such as @Configuration?

Great suggestion Jonathan. Once my jersey2-guice fix is in we can even
support injecting it into the resource classes.
On Feb 23, 2015 7:39 PM, "Jonathan Haber"<EMAIL_ADDRESS>wrote:

@oillio https://github.com/oillio I don't like the idea of binding
configuration properties using @Named because of the chance of collisions
with apps that might already be binding similarly named properties,
thoughts on making a new annotation for this purpose such as
@Configuration?
—
Reply to this email directly or view it on GitHub
https://github.com/HubSpot/dropwizard-guice/pull/46#issuecomment-75603550
.

That sounds good to me and should be easy to implement.  I think it will also help me fix another annoyance with the current design.
Mind if I call it @Config instead?

OK, I converted it to use a new annotation called @Config.
I also added the ability to specify a root config class, to which the provided path will be relative.
So, for instance, if you have a configuration setup like this:
public class MyConfiguration extends Configuration {
    private FooConfig foo;
}

public class FooConfig {
    private String data;
}

You can get to data with either of these attributes:
@Config("foo.data")

@Config(FooConfig.class, "data")

This is particularly useful if FooConfig, and the classes using "data" are in an external library.  This way, the library doesn't have to know where exactly FooConfig is located within the parent project's config object, just so long as it is there somewhere.

Fixed.

I'm going to see if I can make dropwizard-guice extensible enough to support these use-cases easily (maybe with a new type of Bundle that can add Guice bindings?), I would rather keep the core library lean (maybe a separate module with common extensions?)

Sounds good.  The @Config stuff can be pretty cleanly moved to an independent Guice module.  Do you want me to split that feature out into a separate pull request?

Sure

Also, I meant a separate Maven module for the common extensions

Yep.  I was going to pull the @Config stuff out of DropwizardEnvironmentModule into it's own Guice module.  So, when you go to implement the extension hooks, it will be easier to refactor it out into the extension Maven module.

I pulled out the @Config functionality from this PR and moved it to its own PR.

Great, I'll take a look tomorrow

When pulling the @Config code out I noticed that, with the double injection feature, we may not need the user to set the configurationClass.
Is there any scenario where the configurationClass should not be configuration.getClass()?
If the answer is no, I should be able to remove setConfigClass and significantly simplify DropwizardEnvironmentModule.

I'm going to try and see if I can merge the 2 test applications: hello-world.yml and test-config.yml into a single test suite. A single test application will hopefully make it easier to demonstrate the various new functionalities to users of this tool (including myself).

Sounds good.  Thanks.
I based my test application off of the pre-existing example app.  It could definitely do for some cleanup.
As it stands, it is a bit difficult to follow the tests and understand why certain bits are setup the way they are.  I wanted to test end to end functionality, going through the Jersey integration, and I couldn't come up with a better way to do it.  If you have any better ideas...

As I began splitting the tests into 2 groups: DoubleInjectApplication and SingleInjectApplication. It became more clear that the logic should also be split up, into either:

GuiceBundle and DoubleInjectBundle. Where DoubleInjectBundle would come with all the new Command objects and extra tests. Similar to DW's HibernateBundle vs ScanningHibernateBundle where users have a choice.
Or potentially as separate maven modules: dropwizard-guice vs dropwizard-guice-doubleinject. Similar to guice vs guice-assistedinject maven dependencies.

I believe this was what @HiJon89 was hinting at by splitting the extensions? Whilst the double injection functionality is quite powerful and forms the basis for @Config; it does come across more as an advanced feature and should be an optional add-on for users who can't satisfy their needs using single module inject.
What does everyone think? In the mean while I've made a rough start on option 1, but haven't progressed very far. Will submit a PR to @oillio's branch when it's in a good state.

I worry that splitting them up adds additional complexity for the user with little gain.  Under what scenario would a user not want to use double injection?
For the base case, the user can configure their bundle just as they did before.  Their modules will be added during the run phase, there shouldn't be any performance hit to the double injection, and everything should work as expected.  Even better so as their modules will be added after the environment and configuration objects are added to the injector, so no singleton issues, etc.
For more advanced users, they can add injected fields to their modules and initialization modules as needed without any configuration change or change to performance or functionality.  If we split up the functionality into two modules, the transition would take additional effort and understanding.
I would agree that the @Config functionality could be an optional addon.  There is additional configuration required to make it work as expected and a potential performance hit for complex configuration objects.

Complexity for the users is a fair point. But I think it's also reasonable that many users just use single injection for simple injections and don't have any issues related to configuration or environment. But regardless, both usages are covered by the tests.
In the spirit of keeping the library lean and easy to understand, I've move things around a bit. All the double injection related stuff are in a separate sub-package, along with their tests. It's a lot clearer now (I hope) who is using who, and may form a good basis for future refactoring.
I wrote new test catering for #19. where users want to create a eager singleton DBI that takes both Configuration and Environment module. Everything passes, except InjectedConfiguredCommandTest for some reason beyond my understanding. I've created https://github.com/oillio/dropwizard-guice/pull/3
In regards to @oillio previous question:
Is there any scenario where the configurationClass should not be configuration.getClass()?

I don't understand why the user needs to set Configuration class either. Can anyone shed some light? Or in the spirit of TDD, the best way probably write a test case for both scenarios and see if the results end up the same.

Hi @HiJon89 @eliast, any update on this PR? Just heard from a friend in BSkyB where 2 of their teams are using this project with custom double injection to bind Environment dependent eager singletons. He mentioned the lazy singleton work around isn't desirable since their services needs to be all warmed up when started.
I've pointed him out to this PR and they are happy to try it out. Happy to discuss any concerns, but as a lazy advocate I'm beginning to see eager singletons through double injection is quite useful. I'll volunteer to update the README to clarify the new usages.


replacing JSON encoder with Yajl

To avoid character encoding problems with malformed UTF-8:
"[fluentd] ... failed to flush the buffer. ...
error_class="JSON::GeneratorError" error="source sequence is
illegal/malformed utf-8" ..."
(idea for this patch comes from
https://github.com/uken/fluent-plugin-elasticsearch/issues/19)

@dembaca Thanks for this :clap:! Could please add a supporting test for this change?

👋  @dembaca: Have you had a chance to add a test for this change?


Allow setting ID's across an entire file

Should go through each section and apply the logic according to the settings for how to determine the prefix

Completed


Add SemicolonToken

Hey David, can you add SemicolonToken as a node type? Seems walking through the children of an ExpressionStatement can give me this guy. Would be good to have on the TypeGuards.
Thanks!

Within the compiler, there's not a node specifically for SemicolonToken. In this case, I added a type guard for SemiColonToken, but it still just returns a plain Node.

Ah, interesting. Ok, thanks then!


pyzmq v20

It's a major bump due to dropped Python version support and some changes to how its built, but should have no real consequences for users
Should unblock #60

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Non noarch packages should have python requirement without any version constraints.

Hm, that seems like a misleading linter error, since it's clearly wrong. I'll remove it anyway, since the constraint is outside currently supported Pythons.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


using file.sync in a folder with symlinks on it

Describe the bug
I am trying to sync a folder with a symlink on it.
It seems pyinfra replaces the symlink into the "symlink destination" or ignores the symlink if its to a folder.
To Reproduce
create a folder "test"
create file "test/1" and folder "test/a"
cd "test" and do "ln -s 1 2" and "ln -s a b"
pyinfra will copy the files 1 and replace symlink 2 with the destination, this case 1.
pyinfra will ignore the symlink b
Expected behavior
it would be expected that it would have the symlinks 2 and b, like they are in the source folder.
Meta

Include output of pyinfra --support.
How was pyinfra installed (source/pip)?
Include pyinfra-debug.log (if one was created)
Consider including output with -vv and --debug.

Thanks for pyinfra, i am very new to it, but seems very cool!

If you use files.rsync, this will preserve your symlink structure.  I just tested this and it works.

Thank you for raising this issue @alexjp! Currently files.sync doesn't have any handling for links - but it definitely should copy the links as-is!
Sidenote: I'm also going to bump the rsync operation to beta because it's stable, albeit not as well tested as others (incl files.sync).

thanks !
and also thanks for marking rsync as beta also :)


md-grid-list

[x] Move existing TS code from angular/angular
[x] Update code to new syntax
[x] Remove Dart wrappers
[x] Fix issue with host binding and lifecycle
[ ] Can change number of columns based on screen size
[ ] Grid tile header and footer
[ ] Refactor scss
[ ] unit tests
[ ] e2e tests
[ ] readme

Initial version of grid-list is in.


Zpoken Wallet Extension Documentation

Is your feature request related to a problem? Please describe.
As of 9.2.2023, we have seen a live demonstration of transaction send via the Zpoken web wallet, but we don't have a step-by-step guide for letting testnet users do this themselves with the least amount of setup work.
Describe the solution you'd like
We would like a brief summary of the (current, as of the most recent testnet) steps needed to start a local node, install the web wallet extension to Chrome, and interact with the testnet to the fullest extent possible without using pcli.
Additional context
This is related to ongoing interface support work tracked in #1775 - producing these docs and ensuring that they work for new users will be critical to ensuring ease of access to the wallet user interface and that Penumbra team has provided the necessary protocol and other support. This work should follow any in-flight updates to the existing testnet join guide, such as those in #1976, so we can provide up-to-date instructions across the board.

This is paused while we wait for the state of the extension to settle

As part of #2216, I made very small changes to the readme docs in that repo: https://github.com/penumbra-zone/penumbra_dapp/commit/ee87b0fb238c180291074c2e147f0d6465fd55e5 My understanding is that to complete this ticket, we'll want to add setup steps to guide.penumbra.zone. If that's so, do we still consider this blocked? We might do well to document what we have and let folks on the next testnet take it for a spin.

Discussed at sprint planning today. We plan to ask for community testing of the web extension shortly after the release of Testnet 52. Given the typical several-day delay to get new versions of the webext verified and available in the Chrome store, we expect the following:

Monday 2023-05-08 we release Testnet 52.
Zpoken updates the web extension and uploads it to Chrome store.
Wait a few days, during which we can write these docs.
Receive confirmation of new version published, double-check docs are accurate.
Make a second announcement, calling for community testing of the webext.

@conorsch is going to take a first pass at writing these docs and @aubrika will review

Fixed by:

https://github.com/penumbra-zone/penumbra/pull/2651
https://github.com/penumbra-zone/penumbra/pull/2810
https://github.com/penumbra-zone/penumbra/pull/2811


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_1b478eca-866a-4b6f-b1e7-e44688ba81bf/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_1b478eca-866a-4b6f-b1e7-e44688ba81bf.git

Docs Build status updates of commit d676058:
:clock10: Pending: waiting for processors (10 builds ahead of you)
:warning: Docs Build is busy, currently there are 10 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit d676058:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-27-05-13-26 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-27-05-13-26

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


documentation for word vector, romanization, example

Coverage decreased (-3.4%) to 55.766% when pulling d15c3755660ef602fb283f9660423c2a36bb9665 on petetanru:dev into 9743aa66ca5064fc804faa8c2e2ee31345883545 on PyThaiNLP:dev.

Coverage decreased (-3.4%) to 55.766% when pulling d15c3755660ef602fb283f9660423c2a36bb9665 on petetanru:dev into 9743aa66ca5064fc804faa8c2e2ee31345883545 on PyThaiNLP:dev.


Update rdf4j-model, rdf4j-query, ... to 4.3.3

About this PR
📦 Updates

org.eclipse.rdf4j:rdf4j-model
org.eclipse.rdf4j:rdf4j-query
org.eclipse.rdf4j:rdf4j-queryalgebra-evaluation
org.eclipse.rdf4j:rdf4j-queryalgebra-model
org.eclipse.rdf4j:rdf4j-queryparser-sparql
org.eclipse.rdf4j:rdf4j-rio-rdfxml
org.eclipse.rdf4j:rdf4j-storage

from 3.7.7 to 4.3.3 ⚠
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.eclipse.rdf4j" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.eclipse.rdf4j" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #93.


Rados commands

Enable the use of the librados functions:

rados_mon_command
rados_mon_command_target
rados_osd_command

These can be useful to get additional info about monitors & cluster status.

Looks good to me. I haven't been able to run the tests though.
Anything to add @nislim ?

I ran the tests succesfully, so they should work.
Nothing to add.

I removed the newline characters and squashed that commit into the last commit.
Any other remarks @wido ?

Nope, looks good to me. Merging.


Problem with ResourceOwnerPasswordCredentialsGrant

I am using version 2.6.1 of sprintfox and want to make swagger ui use sprint boot oauth service before invoking my REST controller.
I added grant type as ResourceOwnerPasswordCredentialsGrant("http://localhost:8080/oauth/token");
So when press toggle button I can see pop up with title Available authorizations and
Authorization URL:
flow: password
So, Authorization URL is empty.
When check scopes I want to grant (all) I have bean redirected to new page
http://localhost:8080/null&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2Fwebjars%2Fspringfox-swagger-ui%2Fo2c.html&realm=pets&client_id=clientapp&scope=write%3Apets read%3Apets&state=undefined
and I'm stack here.
Thanks
.

I don't think ResourceOwnerPasswordCredentialsGrant is supported as of 2.6.1

@dilipkrish  thanks for response. What You suggest then for how to make a call from swagger io (pressing Try out button) when documented controller is under oauth with spring boot? I need to send header with valid access_token to be able to test it from swagger ui.
Thanks

@TodorSusnjevic Did you ever figure out how to make this work?  We are running into the same issues.
Thanks!

Here's my solution:
@Configuration
@EnableSwagger2
public class SwaggerConfig {
@Bean
public Docket newApi() {
    return new Docket(DocumentationType.SWAGGER_2)
            .groupName("appserver")
            .apiInfo(apiInfo())
            .select()
            .paths(regexPaths())
            .build()
            .securitySchemes(apiKeys())
            .securityContexts(securityContext());

}

private ApiInfo apiInfo() {
    ApiInfo apiInfo = new ApiInfo("back server",
            "rest api ",
            "1.0",
            "NO terms of service",
            new Contact("andy zhao", "", "286505491@qq.com"),
            "more-tech",
            ""
    );//

    return apiInfo;
}

private Predicate<String> regexPaths() {
    return or(
            regex("/admin/.*"),
            regex("/api/.*"),
            regex("/v[0-9]/.*")
    );
}

private List<SecurityContext> securityContext() {
    List<SecurityContext> securityContexts = new ArrayList<>();
    SecurityContext context = SecurityContext.builder()
            .securityReferences(defaultAuth())
            .forPaths(regexPaths())
            .build();
    securityContexts.add(context);
    return  securityContexts;
}
List<SecurityReference> defaultAuth() {
    List<AuthorizationScope> authorizationScopeList = new ArrayList<>();
    AuthorizationScope[] authorizationScopes = new AuthorizationScope[2];
    authorizationScopes[0] = new AuthorizationScope( "read", "read only" );
    authorizationScopes[1] = new AuthorizationScope( "write", "read and write" );
    List<SecurityReference> list=  new ArrayList<SecurityReference>();
    SecurityReference s = new SecurityReference("Authorization", authorizationScopes);
    list.add(s);
    return list;
}

@Bean
public SecurityConfiguration securityInfo() {
    return new SecurityConfiguration(
            "client_id",
            "client_secret",
            "realm",
            "XXX",
            "Bearer ",
            ApiKeyVehicle.HEADER,
            "Authorization",
            ",");
}

private List<SecurityScheme> apiKeys() {
    ArrayList<SecurityScheme> securitySchemes = new ArrayList<>();
    securitySchemes.add(new ApiKey("Authorization", "Authorization", "header"));
    return securitySchemes;
}

step1:
get the access token by the command as below:
curl  -vu client_id:client_secret http://localhost:8080/oauth/token -d "grant_type=password&username=xxxxx&password=xxxxx"
step2:
add the access_token in the swagger "key" edittext of the swagger-ui page at the top right place;
Bearer access_token
there's a blank between the Bearer  word and the access_token
then u invoke the secured methods that should be worked.
Anyhow, the annoying thing is that when the page has been refreshed, u have to added the access_token again and again.Then u can invoke the secured method to do test with the swagger.
if any problems, feel free to contact me.
and my email<EMAIL_ADDRESS>

Thank you @androidzhaoxiaogang!!

@androidzhaoxiaogang If I add valid access token on swagger ui it generates curl like
curl -X GET --header 'Accept: application/json' --header 'Authorization: Bearer**%20**0de17b0d-82bf-4905-87cb-fbf6b203bdc3' 'http://localhost:8080/antennas'
and it is not accepted cause rest returns invalid token. It encodes this white space.


Update config.yaml.md

'portForwarding' should be 'ports'
What issue type does this pull request address? (keep at least one, remove the others)
/kind documentation

LGTM


Become an embed.ly provider

Server portion of: https://github.com/PayButton/paybutton/issues/288

We may need to charge a fee for this one as it probably involves hitting the server.


Fix httpx async / decoded responses

This is a follow up from #807.
I tested v6.0.1 last week and my issue recording requests against openai was resolved. However, I just uplifted my app from Flask to FastAPI for async support and ran into an issue with v6.0.1 trying to start another event loop:
Traceback (most recent call last):
  File "/app/.venv/lib/python3.11/site-packages/openai/_base_client.py", line 880, in _request
    response = self._client.send(
               ^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/httpx/_client.py", line 915, in send
    response = self._send_handling_auth(
               ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/httpx/_client.py", line 943, in _send_handling_auth
    response = self._send_handling_redirects(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/httpx/_client.py", line 980, in _send_handling_redirects
    response = self._send_single_request(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/vcr/stubs/httpx_stubs.py", line 184, in _inner_send
    return _sync_vcr_send(cassette, real_send, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/vcr/stubs/httpx_stubs.py", line 177, in _sync_vcr_send
    asyncio.run(_record_responses(cassette, vcr_request, real_response, aread=False))
  File "/usr/local/lib/python3.11/asyncio/runners.py", line 186, in run
    raise RuntimeError(
RuntimeError: asyncio.run() cannot be called from a running event loop

I also found assert not hasattr(resp, "_decoder") was preventing recording https://api.openai.com/v1/embeddings responses made by the openai client as they seem to already be decoded by the client before this code runs.
The changes in this PR resolve both issues and allow me to record openai responses in my uplifted FastAPI async app. It's not clear to me the benefit of the async refactor in httpx_stubs.py, but I'll note that my original patch in #807 continued to work in my uplifted FastAPI app.

Closed in favor of https://github.com/kevin1024/vcrpy/pull/833


Resize treeview

It would be very nice to be able to resize the treeview. Some large filepaths break the line (it gets ugly)

It's not ideal but you can manually change the width by editing sidebar.less


npm create-react-app awesome-project fails with node_modules\core-js: EINVAL: invalid argument error

npx create-react-app not working properly and continuously failing
OS: Windows 10
Yarn version: 1.21.0
Node version: 13.3.0
Npm version: 6.13.1
Attached the logs file.
Here below is cmd prompt logs:
C:\Users\satis\Documents\reacttest>npx create-react-app awesome-project
Creating a new React app in C:\Users\satis\Documents\reacttest\awesome-project.
warning ....\package.json: No license field
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
yarn add v1.21.0
warning ....\package.json: No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "react-scripts > @typescript-eslint/eslint-plugin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
[4/4] Building fresh packages...
[1/3] ⠂ core-js-pure
[2/3] ⠂ core-js
error An unexpected error occurred: "C:\Users\satis\Documents\reacttest\awesome-project\node_modules\core-js: EINVAL: invalid argument, mkdir 'C:\Users\satis\AppData\Local\Temp;C:\Program Files (x86)\Minimal ADB and Fastboot;\yarn--1576052903837-0.6643317013326462'".
info If you think this is a bug, please open a bug report with the information provided in "C:\Users\satis\Documents\
Aborting installation.
yarnpkg add --exact react react-dom react-scripts cra-template --cwd C:\Users\satis\Documents\reacttest\awesome-project has failed.
yarn-error.log

The issue was with running the command yarnpkg add --exact react react-dom react-scripts cra-template --cwd C:\Users\satis\Documents\reacttest\awesome-project, which is out of our control, so I don't think I can help much.
Try running with the --use-npm flag and see if it still happens? npx create-react-app awesome-project --use-npm.

I'm seeing the same thing on my development system while creating a new app. My OS is Windows 10.
PS D:\src\Experimental> npx create-react-app my-react-app
npx: installed 91 in 8.731s

Creating a new React app in D:\src\Experimental\my-react-app.

(node:13656) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...

yarn add v0.27.5
(node:2268) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[1/4] Resolving packages...
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
warning<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
error<EMAIL_ADDRESS>The engine "yarn" is incompatible with this module. Expected version ">=1.0.0".
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Aborting installation.
  yarnpkg add --exact react react-dom react-scripts cra-template --cwd D:\src\Experimental\my-react-app has failed.

Deleting generated file... package.json
Deleting generated file... yarn.lock
Deleting my-react-app/ from D:\src\Experimental
Done.

Using the --use-npm flag did allow me to create an app.

@jrsconfitto Seems like you just need to upgrade yarn? 0.27 is a couple of years old.


keep the iframe url at the playground rendered

If the user browses from inside the renderer iframe, it might lost the capacity to render more to render new pre-visusalizations

this is fixed through the reset button


schema-location-pattern does not include schemas from another .jar library files

I have put all the .graphqls in a common library built as .jar file and references in other projects deployed as .war files. When the application starts I see the following exception:
Caused by: java.lang.IllegalStateException: No graphql schema files found on classpath with location pattern '**/*.graphqls'.  Please add a graphql schema to the classpath or add a SchemaParser bean to your application context.

Here is my application.yml:
graphql:
  servlet:
    enabled: true
    corsEnabled: true
    exception-handlers-enabled: true
    mapping: /graphql
  tools:
    schema-location-pattern: "classpath*:**/*.graphqls"
    #schema-location-pattern: "**/*.graphqls"
        # Enable or disable the introspection query. Disabling it puts your server in contravention of the GraphQL
        # specification and expectations of most clients, so use this option with caution
    introspection-enabled: true

In your config you've set the value for schema-location-pattern to include "classpath*", while this is already done in the code. The default schema location pattern should already handle this. I see you also include a lot of default settings in your config that you don't have to specify explicitly. Could you try if the following config works for you?
graphql:
  servlet:
    exception-handlers-enabled: true

Think all other settings are the same as the defaults.

I'm assuming my last comment helped you in fixing the problem. If not and you have any follow-up questions feel free to re-open the issue.

Hello Michiel, is there a possibility to contact to you to talk about this problem, I;m working with spring-boot and doing a simple "hello world" but I still getting this error: "No graphql schema files found on classpath with location pattern '**/*.graphqls'"
Well only if you have the possibility to do it. Thank you.

Is this issue resolved? I am still facing this issue with Spring Boot GraphQL

I added 2 dependencies to my Gradle file
implementation 'com.graphql-java-kickstart:graphql-spring-boot-starter:6.0.1
implementation 'com.graphql-java-kickstart:graphiql-spring-boot-starter:6.0.1'

And when trying to starl app, app crashes with exception:
Caused by: java.lang.IllegalStateException: No graphql schema files found on classpath with location pattern '**/*.graphqls'.  Please add a graphql schema to the classpath or add a SchemaParser bean to your application context.

What I missed?

Still not sure of the solution here, how can schema-location-pattern be customised to allow for the schema to come from a jar/dsl

First step will be adding a unit test to the library to reproduce this problem. Any contributions for this are very welcome.


Node 6.4.0 Breaks Ink

#I am pretty sure that after updating to Node 6.4.0 it broke Ink.  Is Ink compatible with this version of Node yet?  I had some Ink stuff working just fine right before I upgraded.  Now it's bombing.

This code now breaks in my application:
        setTimeout(() => {
            const el = ReactDOM.findDOMNode(this);
            if(el && document.getElementById("interviewHeading")) {
                new Ink.UI.Sticky(el, {topElement: "#interviewHeading", bottomElement: "#footer"});
            }
        }, 100);

Node version shouldn't at all affect the functionality of the framework.
By the stack trace, check if you're trying to attach a component to an unattached DOM node. Or if document.body is present. Follow the stack until you reach the root of the problem.

found out actually another middleware broke after doing an npm update.  Disregard.


[tests-only][full-ci] Forward-port search/report response test scenarios for personal shares

Description

It is the forward-port of PR https://github.com/owncloud/ocis/pull/5456  to master branch

keeps on failing in wait-for-ocis-server https://drone.owncloud.com/owncloud/ocis/18583/60/10
I'll restart it again


Child tables of Child Table to root missing from final dynamicframes_map

If a child table to root has more child tables, they're missing in the final dynamic frames map.
Relationalize is spitting them, But we're loosing them in clean_column_names.
As, this function will take only root table as input and it'll recursively pick child tables associated to the root.
Also, why is always root table is set to have child to true, any child table can also have another child table.
Can we make this part more generic to dynamically figure if a table (root or child or anything) has a child or not and then clean the column names.

Thank you for bringing this to our attention, I will review the code.
The use case you mention, was meant to be implemented so I need to verify why it is not working as expected.
Could you share a sample file or just a sample schema that it is similar to your if there is sensitive information?

{
"timestamp":<PHONE_NUMBER>065,
"dummydata": {
"DummyKey": "1234567890",
"UpdateRegion": "us-west",
"DummyType": "Letter",
"DummyKeyValues": [{
"Value": "1234567890",
"Source": "Dummys-task",
"TimeStamp": "2021-01-31T20:04:38.9781619Z"
}
],
"FileTypes": ["zip", "pdf", "csv"],
"DummyKey": "126gdf1324-36da-s5172-8c4d-vf43526",
"DummyClassifications": {
"Values": {
"Dummy-task": [{
"Pages": ["0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11"],
"Value": "Letter",
"Source": "Dummy-task",
"TimeStamp": "2021-01-28T21:26:02.4571552Z"
}
],
"dummy-classification": [{
"Pages": ["0"],
"Value": "Other",
"Source": "dummy-classification",
"TimeStamp": "2021-01-28T19:48:34.7445087Z"
}, {
"Pages": ["1"],
"Value": "Other",
"Source": "dummy-classification",
"TimeStamp": "2021-01-28T19:48:34.7445087Z"
}, {
"Pages": ["2"],
"Value": "Other",
"Source": "dummy-classification",
"TimeStamp": "2021-01-28T19:48:34.7445087Z"
}, {
"Pages": ["3"],
"Value": "Other",
"Source": "dummy-classification",
"TimeStamp": "2021-01-28T19:48:34.7445087Z"
}, {
"Pages": ["4"],
"Value": "Other",
"Source": "dummy-classification",
"TimeStamp": "2021-01-28T19:48:34.7445087Z"
}, {
"Pages": ["5"],
"Value": "Other",
"Source": "dummy-classification",
"TimeStamp": "2021-01-28T19:48:34.7445087Z"
}, {
"Pages": ["6"],
"Value": "Other",
"Source": "dummy-classification",
"TimeStamp": "2021-01-28T19:48:34.7445087Z"
}, {
"Pages": ["7","8"],
"Value": "Other",
"Source": "dummy-classification",
"TimeStamp": "2021-01-28T19:48:34.7445087Z"
}
]
},
"Overall": [{
"Pages": ["0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11"],
"Value": "Letter",
"Source": "Dummy-task",
"TimeStamp": "2021-01-28T21:26:02.4571552Z"
}
]
},
"UploadedBy": {
"FirstName": "John",
"UserName": "JD",
"LastName": "Doe"
},
"UploadKey": "56tr1-231q-4af6-b12a-q213we",
"Name": "Letter"
}
}

Hi ,
so the sample file you shared has at root level a timestamp field and a nested structure containing the data:

maximum level of nested structure is 2.
The script can run in more ways:

fully denormalizing the json file (set the parameter --num_level_to_denormalize to a high level i.e. 999) ; in this case it   will only create one table containing all the attributes in tabular format.

or

keeping all the table split by the relationalize (set the parameter --num_level_to_denormalize to 0)

and so on
or

only denormalizing some levels (set the parameter --num_level_to_denormalize to the number of nested levels to collapse i.e. 1)

can you explain me what do you think get lost in the execution?


Clang modulus with integral

Do not use Jammy until GCC12 warn on Boost is handled.
See also https://github.com/boostorg/multiprecision/issues/460


4.08.01

As a claimant, I want the entry of an expense item to have minimal required navigation in the user interface.

This is a UI/View test.

Nothing empirical to test.


Computed properties can not be observed, if they have dots in keypath

Description:
Seems like computed properties can not be observed, if they have dots in keypath. No warning or error arises.
Versions affected:
0.8.7
Platforms affected:
Chrome 55.0.2883.87 m
Reproduction:
Just create a computed property with dot(s) in keypath, and then try to observe it's value.
https://jsfiddle.net/Minstel/4v7fysj0/
Code:
var r = new Ractive({
	data: {
    	zoo: 4 + 5,
	},
	computed: {
    	'bar\\.foo': '4 + ${zoo}',
	}
});

r.observe('zoo', function(newValue, oldValue, key) {
	console.log('changed zoo: ', newValue, oldValue, key);
});

// Try to observe computed with dots
r.observe('bar.foo bar\.foo bar\\.foo bar\\\.foo bar\\\\.foo', function(newValue, oldValue, key) {
	console.log('changed computed: ', newValue, oldValue, key);
});

r.set('zoo', 10);

To clarify, it can be observed (the handler executes), but the old and new values aren't provided. Very minimum reproduction: https://jsfiddle.net/4mot9kqL/
var r = new Ractive({
  data: {
    zoo: 4 + 5,
  },
  computed: {
    'bar.foo': '4 + ${zoo}',
  }
});

r.observe('bar.foo', function(newValue, oldValue, key) {
  console.log('changed computed: ', newValue, oldValue, key);
});

r.set('zoo', 10);

@fskreuz it's initial call to observe that you see, when values are undefined. Non-initial observe, when value is recomputed, is not preformed. Try to set {init: false} in options.
I've changed my issue fiddle a little, so that it was clear.
Also when using computed keypath without escaping dot, like you provide, it's value can not be obtained event with get function. According to Ractive changelog, as of 0.8.0 we should escape dots.
It's also the other face of bug. Non-computed properties, if dot in keypath is not escaped, are presented as object ierarchy, and we can get their values with get. With computed properties, we can only get value if dot was escaped when setting value.

You should still define computeds with plain dotted keypaths e.g. computed: { 'foo.bar': '...' } as you would with any other data. You should access them with escaped keypaths e.g. r.get('foo\\.bar') as you would with any other data.
This is now fixed in 0.8-dev and edge, and will be published when 0.8.8 is released. Thanks for the report!


Fix clippy warnings and errors

Fix warnings and errors while clippy

HI, all. Is contributions welcomed for this repo ? I'd like to help ! I fixed some errors.

HI, all. Is contributions welcomed for this repo ?

Of course yes! Thanks for your contribution! Can you also add the clippy lint to CI check?

Add clippy lint in GitHub workflows ?

Yes.

Already added the lint. By the way, Why you start to write this key-value store from scratch ? Why no rocksdb ? Could you clear this for me ? Thank you !!!

Rocksdb is too complicated and general. This project is about to act quickly and bring aggressive optimizations for TiKV only. Writing it in Rust can bring memory safety and be easier integrated into TiKV. This is an experimental engine for TiKV, we will still keep using rocksdb.

Got it! I looked through the code base. Is there any draft docs over the design for now ? I see that there are only some development plans to implement the core features of a classical key-value store.  Or it's planed to implement the main features for a key-value store firstly and introduce optimizations later ?

Got it! I looked through the code base. Is there any draft docs over the design for now ? I see that there are only some development plans to implement the core features of a classical key-value store. Or it's planed to implement the main features for a key-value store firstly and introduce optimizations later ?

We have updated our roadmap in README.md. Thanks for your interest.

Thanks for your work! Would you please rebase or merge latest master onto this branch? (Or you may open a new PR for clippy). It seems that the git diff contains content from previous commits, and it's hard to review what has really changed.

Thanks for your work! Would you please rebase or merge latest master onto this branch? (Or you may open a new PR for clippy). It seems that the git diff contains content from previous commits, and it's hard to review what has really changed.

Of course! I would open another PR for this.


typo in repository description

should be Stäubli instead of Staübli in the repository description

Not sure what you're talking about ;)


feat(postgres): allow specifying deferred mode on unique constraints

TODO: docs, also for the FK defer mode as that is missing too

Only after working on https://github.com/mikro-orm/mikro-orm/pull/5641 I spotted that you worked on this PR. Looking at the source, it seems we have some overlap, though this is specifically handling manually created unique constraints, while my PR handles unique constraints created automatically for 1:1 relations. How should we proceed on this? :)

i can merge yours first and release to stable, since its a fix. i am keeping this one for v6.3, which i'd like to start working on soon (this weekend probably), i also have #5482 which is waiting for the exact same reason, and have some other small things i want in there that will deserve a blog post


Can't Pair devices

hello I have problem on pair my hub. any suggestions?
Nuki lock start pairing
Nuki lock start pairing
Nuki lock start pairing
Nuki lock start pairing
Nuki lock start pairing
Nuki lock start pairing
Nuki lock start pairing
Nuki lock start pairing
Nuki lock start pairing
Nuki lock start pairing

I manage to pair device with a total reset with this tool:
https://espressif.github.io/esptool-js/
then reflash with https://technyon.github.io/nuki_hub/
without reset
then
configure Wifi settings
configure MQTT settings
pairing Nuki first with app
diasble pairing in app (Settings --> Features & Configuration --> Button & LED --> Bluetooth Pairing)
enable pairing in app
bring Nuki device in paring mode


Must Login Twice when using driver (Linux)

hello, for some reason, my display manager forces me to enter my password a second time after the first time (and activates extra displays)
loginctl shows 2 sessions
$ loginctl
SESSION  UID USER SEAT  TTY
2 1000 xxxx seat0
4 1000 xxxx seat0
2 sessions listed.
it does not matter if i use lightdm or gdm or sddm.
the setup i am using is arch with displaylink from aur and this xorg file:
/usr/share/X11/xorg.conf.d/20-evdidevice.conf
Section "OutputClass"
Identifier "DisplayLink"
MatchDriver "evdi"
Driver "modesetting"
Option  "AccelMethod" "none"
EndSection
please advise

Hi @ameeno
How many monitors are you using? Also, what is your GPU card?
Here is something which sounds similar:
https://support.displaylink.com/knowledgebase/articles/1859356-x-server-crashes-on-nvidia-systems-when-displaylin
Note in the solution there is Section Device and there is less options ;)
You could also try to check this out
https://support.displaylink.com/knowledgebase/articles/1883074-ubuntu-16-04-x-server-starts-in-low-graphics-mode

Hello.I am using and integrated hd4600 from hasw3ll CPU, with 2 additional screens connected via displaylink (chip supports 3 screens)I think the problem is to do with systems load order and the displaylink acctioins.Basically displaylink systems file is told to start after display-manager has ended. But does not actually start u til password is entered on the login screen (sddm or lighten)And loginctl shows me 2 sessional one I just logged into and one I crashed out off,What logs can tell us what's happening?Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Dawid Kurek<EMAIL_ADDRESS>Date: 19/04/2019  07:29  (GMT+00:00) To: DisplayLink/evdi<EMAIL_ADDRESS>Cc: Arun Shah<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [DisplayLink/evdi] Must Login Twice when using driver (Linux) (#153) Hi @ameeno
How many monitors are you using? Also, what is your GPU card?
Here is something which sounds similar:
https://support.displaylink.com/knowledgebase/articles/1859356-x-server-crashes-on-nvidia-systems-when-displaylin
Note in the solution there is Section Device and there is less options ;)
You could also try to check this out
https://support.displaylink.com/knowledgebase/articles/1883074-ubuntu-16-04-x-server-starts-in-low-graphics-mode
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/DisplayLink/evdi","title":"DisplayLink/evdi","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/DisplayLink/evdi"}},"updates":{"snippets":[{"icon":"PERSON","message":"@displaylink-dkurek in #153: Hi @ameeno \r\nHow many monitors are you using? Also, what is your GPU card?\r\n\r\nHere is something which sounds similar:\r\nhttps://support.displaylink.com/knowledgebase/articles/1859356-x-server-crashes-on-nvidia-systems-when-displaylin\r\nNote in the solution there is Section Device and there is less options ;)\r\n\r\nYou could also try to check this out\r\nhttps://support.displaylink.com/knowledgebase/articles/1883074-ubuntu-16-04-x-server-starts-in-low-graphics-mode\r\n"}],"action":{"name":"View Issue","url":"https://github.com/DisplayLink/evdi/issues/153#issuecomment-484780722"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/DisplayLink/evdi/issues/153#issuecomment-484780722",
"url": "https://github.com/DisplayLink/evdi/issues/153#issuecomment-484780722",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

Have you checked the suggested solutions?
I would guess the 'login twice' is actually xserver crash on the first attempt.
You can check Xorg logs, the location of them depends on the version you use
(${HOME}/.local/share/xorg, or /var/log/xorg, somethign like that)
You can also explicitly look for xserver crashed, or look into dmesg.. :-)

Hi, I will look at this when i get a chance. but i have since moved back to windows 10.
it works better and my linux needs can be fulfilled via WSL/Hyper-V.


Add condition for instrumentedApplication

don't forget adding it also to odigos-charts

Done in https://github.com/odigos-io/odigos-charts/pull/56


image_builder: Force mount_dir to be created in /tmp

Immutable systems, as such Red Hat Core OS and Fedora Core OS, will not
allow mount_dir to be created in a location that's not read-write.
Let's ensure we use /tmp as base for mount_dir, as it's a safe writable
choice for any distro supported by kata.
Fixes: #437
Signed-off-by: Fabiano Fidêncio<EMAIL_ADDRESS>

/test

We talked a bit on IRC, but to repeat here: rather than hardcode /tmp, use standard TMPDIR with a fallback, like ${TMPDIR:-/tmp}

We talked a bit on IRC, but to repeat here: rather than hardcode /tmp, use standard TMPDIR with a fallback, like ${TMPDIR:-/tmp}

Done! Thanks for the quick review, Cole.

/test


Release next version of pyxform

I'd like to explore what it would take to release an updated version of pyxform and what we can all do to help.
Here are the things that I think are must-haves:

~#114 Use Validate 1.5.0 -- this will allow use of new XPath functions and range~ closed in #116!
#79 Support for numeric range questions -- this is now in JavaRosa but we have to agree on an approach for XLSForm
~#85 Replace curly quotes with normal quotes -- this breaks a lot of people copying examples; @dorey is on it.~ closed in #118!

I think if there's a release scheduled on the horizon we might also get excited about fixing other long-standing bugs!
The ODK core tools are now releasing on the last Sunday of each month. From our end, the ideal would be to have a pyxform release around June 19th so we can update all the tools that depend on it (online/offline form converters, etc).
@ukanga what do you think?

Thank you @lognaturel for putting this together.

It seems you are already on #114, not sure if you will be working on hooking it up to a windows CI before we merge that in.
#79 requires some movement, no clear spec has emerged. If the discussion on that can be completed I can work on implementation.
#85 will you please assign it to @dorey  on the issue, you have pointed out that he is working on this.

Thanks @ukanga!
I was going to manually try it on Windows. I do really like @lindsay-stevens suggestion to use AppVeyor. If you're open to a pull request configuring that, I will try it out. There may be a limit to what I can do without being part of the organization and I'll ping you as needed.
Similarly, only organization members can assign issues but it looks like @dorey was so fast he didn't even need assigning anyway. 😊
Will try to move the conversation along on #79! It would be very helpful to get some comments from XLSForm masters. I've mostly been playing on the XML side of things so I may not have the right instincts.

@lognaturel I should probably have communicated this, all the issues here have been resolved. The only issue that has held me back is we need a new release of ODK Validate that includes the fix https://github.com/opendatakit/javarosa/issues/64. Any chance you can make that happen? A movement on https://github.com/XLSForm/pyxform/issues/113  could also result in us releasing pyxform.

Thanks so much for pushing on all this! Will aim to do a Validate release in the next few days. @yanokwa does that sound right? I think #113 is going to take a little bit.

Would be amazing if #137, #128 and #126 could be squeezed in. I need some guidance on approach but am happy to get them done.
If you'd prefer not to delay further, that's fine too!

Clearly I was too optimistic about adding on that additional functionality!
I have a pull request for #128 ready. If you have a chance to review that it would be great but if not or it needs a lot of work, it can be pushed back. I'll try to get to the others soon but I don't think they should block a release. There will be a release of ODK Collect on the 30th and it would be great to be able to announce range and the few nice incremental improvements to XLSForm at the same time if possible.

@ukanga @lognaturel I think at this stage, we are letting perfect be the enemy of the good. I think we have enough to do a release of pyxform, so let's do one as soon as possible and then iterate from there...

Closing in favor of https://forum.opendatakit.org/t/pyxform-release-process/10431 since that seems like a more appropriate place for high-level discussions!


Jaeger client for Lua

@ldeveloperl1985 https://github.com/jaegertracing/jaeger/issues/366#issuecomment-401012559 :

is there any Lua client or any other way to use jaeger in Lua language?

@isaachier :

that largely depends on whether or not OpenTracing decides to support Lua. Also, the issue of many different dialects makes the situation much more difficult. Which version of Lua do you use? Is it original Lua or LuaJIT?

@ldeveloperl1985 :

I've used kong 0.11v. which uses Lua 5.1 and LuaJIT 2.1.0

@isaachier :

Kong is probably the primary use case. I am not familiar with that version, but does it support 64 bit integers? My problem is maintaining compatibility across several versions of Lua.

@ldeveloperl1985 :

You can easily maintain compatibility across several versions of LUA. Lua is a dynamically typed language. There are no type definitions in the language; each value carries its own type.

@isaachier :

That is much easier said than done. I know for a fact that 64 bit integers are only supported in >= 5.3. Also, I believe the C API has inconsistencies across minor versions and LuaJIT.

Cf: https://github.com/Kong/Kong-plugin-zipkin.

I think @rbtcollins @ror6ax might be interested in this conversation too.

Thanks @isaachier - we are. We're currently using the nginx c++ module and poking around inside it from lua, which is not the most straightforward thing to do.

There's this: https://github.com/opentracing/lua-bridge-tracer

Per #3362, we're sunsetting Jaeger clients.


Set pending block only after making sure it is valid.

Motivation
https://github.com/linera-io/linera-protocol/pull/2904 introduced block proposal size limits that are only enforced when the proposal was handled in the worker, not when staging block execution. This could result in the pending block getting set to an invalid proposal.
Proposal
Handle the proposal in the local node before setting the pending block.
Test Plan
The explicit clear_pending_block call was removed from the test.
Release Plan

Nothing to do / These changes follow the usual release cycle.

Links

Fixes https://github.com/linera-io/linera-protocol/issues/2906.
reviewer checklist

Thanks!
As discussed, I will try to simplify the code in a separate PR.


Implement versioning

https://docusaurus.io/docs/versioning
Doc says: "Versioning is best suited for websites with high-traffic and rapid changes to documentation between versions. If your documentation rarely changes, don't add versioning to your documentation."
What do you think?

don't think we are that point tdex related, we are almost stable API wise (on daemon, specs and SDKs) so would not see any benefit having this.