Failed to load config.cson / [stdin]:1:1 error: unexpected, config.cson filled with whitespaces

Windows 10 Build 9926
Atom version 0.182.0

Community Packages:
atom-lint
minimap
recent-files
recent-projects

The contents of the file are exactly 238 whitespaces. I have no idea why it's that, I didn't modify anything on my own.

Fix: Remove the config.cson file and it gets generated again on startup.

Would it be possible to include the exact contents of the file in a comment here?

Was all the whitespace on the same line or broken across multiple lines?

Would it be possible to include the exact contents of the file in a comment here?

Off-topic:  I haven't been able to add file attachments to these issues.  Am I missing something?

Off-topic: I haven't been able to add file attachments to these issues. Am I missing something?

You're not -- currently, it's not possible to add file attachments on GitHub issues. You can only upload images. A workaround is to include the contents inline in a code block or create a gist and link to it.

@kevinsawicki All the whitespace were in one line.

I tried to delete it but the error still occures. Can you provide a guilty config + instruction where to store the file ?

Just installed Atom (v0.189.0) for the first time on this particular system (OS X 10.10.2), and with the very first launch, the first thing I see on Welcome Guide pane:

Failed to load config.cson

[stdin]:4:13: error: literal is not a function
'themes': [
^

![welcome_guide_-_atom](https://cloud.githubusercontent.com/assets/352182/6957501/fa79bd10-d8b8-11e4-98b1-fdd6d1640fa9.jpg)

`Contents/Resources/app/dot-atom/config.cson`:
```coffee
'editor':
  'fontSize': 16
'core':
  'themes': [
    'one-dark-ui'
    'one-dark-syntax'
  ]

@pixelchutes That is probably another bug. My Config got killed by something. Yours still exists.

Close the atom. Open config.cson, for example, using notepad ++. Clear the contents of the file. Save. And open the atom.

I removed that file and restart Atom. Now all works fine. Atom generates a new one. Thx

How we can remove it ?

The same way we can remove any other file from the computer.

what is the directory for this file ?

~/.atom/config.cson on Mac and Linux, %USERPROFILE%\.atom\config.cson on Windows.

To developers, a suggestion: Later with time would be great to have a self healing function. In this case for example, the tool would detect the error (code) and try to solve it by an automatic scritpt or something else that employs the solution deleting the file (in this case)

removed it i had two instances of the same file i deleted both and it fixed the problem.......thanks alot

I have the feeling that this error comes up if Atom is closed too abrupt. My computer got a BSOD and since then I got this error.


Broadcast is broken in rcon-cli

Describe the bug
Broadcast seems broken when attempting to do it from rcon-cli. String seems to be truncated.
[user@arch-nas palworld-server-docker]$ docker-compose exec -it palworld rcon-cli
Waiting commands for <IP_ADDRESS>:25575 (or type :q to exit)
> broadcast Testing please ignore
Broadcasted: Testing
> broadcast "Testing please ignore"
Broadcasted: "Testing
>

As you can see it seems to be truncated at the first space

To Reproduce
Steps to reproduce the behavior:

Log into rcon-cli with docker-compose exec -it palworld rcon-cli
Attempt to broadcast a multi-word sentence
Notice that it gets truncated at the first space

Expected behavior

Broadcast will send the whole message
Actual behavior

Broadcast sends the first word and then stops
Screenshots

OS information

OS:  Arch Linux
Palworld Version: 0.14.0
Docker Image Version:  0.21.0

Hardware information

CPU:  Ryzen 5600G
Memory:  32G 3200MT RAM

docker-compose.yml contents
services:
   palworld:
      image: thijsvanloef/palworld-server-docker:latest
      restart: always
      ports:
        - 8211:8211/udp
        - 27015:27015/udp
      environment:
         - PUID=1000
         - PGID=1000
         - PORT=8211 # Optional but recommended
         - PLAYERS=16 # Optional but recommended
         - SERVER_PASSWORD="<redacted>" # Optional but recommended
         - MULTITHREADING=true
         - RCON_ENABLED=true
         - RCON_PORT=25575
         - ADMIN_PASSWORD="<redacted>"
         - COMMUNITY=false # Enable this if you want your server to show up in the community servers tab, USE WITH SERVER_PASSWORD!
         - SERVER_NAME="<redacted>"
         - SERVER_DESCRIPTION="<redacted>"
         # Custom game settings
         - PAL_EGG_DEFAULT_HATCHING_TIME=24
      volumes:
         - ./palworld:/palworld/

Hi there!
Yes, this is known and unfortunately nothing we can fix. It's up to Pocket Pair. For now we suggest to use underscores or hyphens to bridge the gaps between words.

Duplicate of https://github.com/thijsvanloef/palworld-server-docker/issues/85


Use local/dockerized Postgres?

How can I use a local or dockerized instance of Postgres instead of Railway?

You can set the DATABASE_URL env var to any Postgres instance you like, eg, DATABASE_URL=postgresql://<USERNAME>:<PASSWORD>@localhost:5432/<DATABASE_NAME>.  Let me know if you need more help.


Add sahara proposal

Im guessing this will fail until https://github.com/crowbar/crowbar-openstack/pull/480 is merged?

+1

+1


Remove OTEL/contrib dependency on cmd/collector/app/sampling

Part of #6408, please read that first.
The dependency exists in OTEL/contrib/extension/jaegerremotesampling. It might be relatively easy to break, but need to try it out.

[ ] Copy whichever code is needed from cmd/collector/app/sampling and plugin/sampling/strategyprovider/static to OTEL/contrib.
[ ] Refactor Jaeger code internally so that these modules are hidden under some /internal/ package (discuss options/proposals on this ticket first)

Hi @yurishkuro, I'm interested in trying this. I'll try to prepare a doc to discuss this in detail.

Hi @yurishkuro, for the first part of this issue, here are my findings:
In OTEL/contrib/extension/jaegerremotesampling,

The internal package has the following dependencies:

Provider interface from cmd/collector/app/sampling/samplingstrategy
GRPCHandler from cmd/collector/app/sampling

As for the root package in OTEL/contrib/extension/jaegerremotesampling, it depends on the code from:

plugin/sampling/strategyprovider/static/constants.go
plugin/sampling/strategyprovider/static/options.go
plugin/sampling/strategyprovider/static/providers.go

Also, some of these have a dependency on github.com/jaegertracing/jaeger/proto-gen/api_v2, which I can see in the parent issue #6408 is also marked for moving. For this issue, do we need to resolve this dependency on the copied code or should we add it as is?

@ary82 I would keep the dependency on proto-gen/api_v2 for now, to reduce the scope. Once the other dependencies you mentioned are untangled it would be easier to refactor them to not depend on proto-gen from Jaeger (they can generate the same code internally).


fix doc comments

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

client/lib/amqp-common/auth/token.ts
:white_check_mark:Succeeded

client/lib/amqp-common/connectionConfig.ts
:white_check_mark:Succeeded

client/lib/amqp-common/dataTransformer.ts
:white_check_mark:Succeeded

client/lib/amqp-common/errors.ts
:white_check_mark:Succeeded

client/lib/batchingReceiver.ts
:white_check_mark:Succeeded

client/lib/connectionContext.ts
:white_check_mark:Succeeded

client/lib/eventHubClient.ts
:white_check_mark:Succeeded

client/lib/eventHubReceiver.ts
:white_check_mark:Succeeded

client/lib/eventHubSender.ts
:white_check_mark:Succeeded

client/lib/eventPosition.ts
:white_check_mark:Succeeded

client/lib/iothub/iotHubConnectionConfig.ts
:white_check_mark:Succeeded

client/lib/iothub/iotSas.ts
:white_check_mark:Succeeded

client/lib/iothub/iothubClient.ts
:white_check_mark:Succeeded

client/lib/linkEntity.ts
:white_check_mark:Succeeded

client/lib/managementClient.ts
:white_check_mark:Succeeded

client/lib/streamingReceiver.ts
:white_check_mark:Succeeded

client/lib/util/constants.ts
:white_check_mark:Succeeded

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.


[iOS] 0.11.4 - ListView sections do not scroll to the absolute top of its container

I created a basic scaffold, copied "ListViewPagingExample.js" from master, pasted it into my 0.11.4 codebase as the only view, and noticed something very strange. The sections don't scroll as expected to the top of the view.
See below.

Inside of an application without a header:

What is very confusing is that this works perfectly within the confines of a Navigator component.   ListView is just one of those components that is so very mysterious sometimes :P

Turn off automatic adjustment of the content insets.

@ide, thank you! I found similar issues after some more searches.
This is clearly a documentation issue. I've tripped over this a few times already.
automaticallyAdjustContentInsets is not a direct property of ListView. Without knowledge of the source, that is that ListView implements a ScrollView, how does a new person actually resolve this issue?
It seems that the ScrollView prop types (https://github.com/facebook/react-native/blob/master/Libraries/CustomComponents/ListView/ListView.js#L114) are included, but the documentation doesn't mention this at all.
I'd love to make a PR for this but to date, i've made several, all of which have been stalled or just ignored.
Thoughts?

@jaygarcia They have lots of pull requests. We should be patient.


How to:?  Permissions for End User to run Flow from lightning page.

I added the Mass Action Flow to a Lightning Page for my end users.  I'm passing in the id of the Mass Action.
When they navigate to the page, they get a "unhandled fault error" - This is before they even press the next button to execute the flow.
What MAS permissions do they need in order to see and run this flow from a lightning page?  I know MAS comes with the MAS Admin perm set, but I only want them to have the minimum perms to run the flow.
Direction or help is appreciated!

I'm having the same issue, not the error however they don't see the package in the drop down.


   :-)

...
   :-)
Seriously.
FuzzyOpen is an absolutively awesome VS 2015 Extension.
I could not find a way to contact you-- your Git profile does not seem to accept comments or questions and etc.
  The behemoth that is VS 2015, which is at times both awesome and at times a total PITA that make my eyeballs explode, stopped working and started breaking. The VS stupid (cause it is broken) built-in search from Solution Explorer crashes VS with NotResponding every time I try to use it, a known bug (Google that)  and is claimed as fixed in Update 2, but sadly and more is the pity it is not actually fixed as of Update 3. So, I could not search for files in VS, which is a crazy thing to need to do (I get it) but I was stuck until the shining light and beauty of FuzzyOpen.
Seriously, man (woman? whatever you are), thank you SO much.
I will, no joke, be sending you at least 1 Million Dollars USD in pure silver bars. So, on the lookout for that, as it will hopefully make your day. I will be delivering that by helicopter to you within 5 minutes of when I click Submit on this "issue" and so I hope that helps.
Peace out.
(Note, yes, I know, this is a shameless, but Fair Use, Leafy Parody, and if you get that reference then GREAT but if not then that's OK too.
-- Mark Kamoski
...

Thanks for the kind words! Good to hear that the extension has been of use to you. I'm closing this issue, but if you have anything you would like to be improved about the tool let me know!


Fixed: ioutil.ReadFile is deprecated

Description
Fixed: ioutil.ReadFile is deprecated
Type of change

Bug fix (non-breaking change which fixes an issue)

Testing steps
Done on CI
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report

Merging #138 (73b3164) into master (73249d1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #138   +/-   ##
=======================================
  Coverage   57.63%   57.63%
=======================================
  Files           7        7
  Lines         845      845
=======================================
  Hits          487      487
  Misses        320      320
  Partials       38       38

Continue to review full report at Codecov.

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


multipart_uploads_enabled not propagated in AsyncGraphQLView, causing file uploads to fail

Describe the Bug
In strawberry-graphql==0.253.0 and strawberry-graphql-django==0.50.0, setting multipart_uploads_enabled=True in the AsyncGraphQLView does not enable multipart uploads as expected. The self.multipart_uploads_enabled attribute remains False, causing file uploads via multipart/form-data to fail with a 400 Bad Request error.
To Reproduce

Configure the GraphQL view in Django:

path(
    'graphql/',
    AsyncGraphQLView.as_view(
        schema=schema,
        graphiql=settings.DEBUG,
        multipart_uploads_enabled=True,
    ),
    name='graphql',
),

Attempt to perform a file upload mutation from the client.

Example cURL Command:
curl -X POST -H "Content-Type: multipart/form-data" \
  -F 'operations={"query":"mutation createImages($data: [ImageInput!]!) { createImages(data: $data) { id imageWebUrl }}","variables":{"data":[{"image":null,"imageType":"PACK"}]}}' \
  -F 'map={"0":["variables.data.0.image"]}' \
  -F<EMAIL_ADDRESS>\
  http://localhost:8080/graphql

Observe that the server responds with a 400 Bad Request error stating "Unsupported content type".
Inspect the self.multipart_uploads_enabled attribute inside the AsyncGraphQLView and find that it is False.

Expected Behavior
Setting multipart_uploads_enabled=True should set self.multipart_uploads_enabled to True in the AsyncGraphQLView, enabling multipart uploads and allowing file uploads to work correctly.
Actual Behavior
Despite setting multipart_uploads_enabled=True, self.multipart_uploads_enabled remains False, causing the server to reject multipart/form-data requests.
Additional Context

This issue did not occur in previous versions:

strawberry-graphql==0.219.1
strawberry-graphql-django==0.32.1

According to the documentation:

Breaking Changes in 0.243.0 - Multipart Uploads Disabled by Default
Django Integration Options

The issue seems to be that multipart_uploads_enabled is not properly propagated to the AsyncGraphQLView instance.

If I force it to True in this method everthing works fine:
    async def parse_http_body(
        self, request: AsyncHTTPRequestAdapter
    ) -> GraphQLRequestData:
        headers = {key.lower(): value for key, value in request.headers.items()}
        content_type, _ = parse_content_type(request.content_type or "")
        accept = headers.get("accept", "")

        protocol: Literal["http", "multipart-subscription"] = "http"
        if self._is_multipart_subscriptions(*parse_content_type(accept)):
            protocol = "multipart-subscription"

        if request.method == "GET":
            data = self.parse_query_params(request.query_params)
        elif "application/json" in content_type:
            data = self.parse_json(await request.get_body())
        elif self.multipart_uploads_enabled and content_type == "multipart/form-data":
            data = await self.parse_multipart(request)
        else:
            raise HTTPException(400, "Unsupported content type")

        return GraphQLRequestData(
            query=data.get("query"),
            variables=data.get("variables"),
            operation_name=data.get("operationName"),
            protocol=protocol,
        )

Question
Am I misconfiguring something, or is this a bug in strawberry-graphql? Any guidance on how to fix or work around this issue would be appreciated.

Hi @BranDavidSebastian, I'm having a hard time reproducing this. We have (passing) tests for this and I just created an example repository containing a minimal (working) demo for this.
Can you take a look at the demo repository and confirm I understood your issue/setup correctly?
Besides that only two things come to my mind at this point:

Are you possibly subclassing AsyncGraphQLView and not calling super().__init__(*args, **kwargs) from your subclass?
Since you said multipart_uploads_enabled is False in your case it shouldn't make a difference, but does using the csrf_exempt decorator as suggested in the docs help?

Hello @DoctorJohn. thank you for the example repository and the help. After I played it for a while and started to set up closer to my actual environment I realized I forgot to mention an essential detail in the initial issue: I’m using Strawberry in an ASGI + Channels+Daphne setup.
I added a fork to your example to demonstrate step by step how we end up with the error here.
In essence the big difference is the asgi.py that looks like this:
import os
from django.conf import settings
from django.core.asgi import get_asgi_application
from strawberry_django.routers import AuthGraphQLProtocolTypeRouter
from starlette.middleware.cors import CORSMiddleware

os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'example.settings')
django_application = get_asgi_application()

# Import your Strawberry schema after creating the django ASGI application
# This ensures django.setup() has been called before any ORM models are imported
# for the schema.
from .schema import schema  # NOQA
application = AuthGraphQLProtocolTypeRouter(
    schema,
    django_application=django_application,
)

application = CORSMiddleware(
    application,
    allow_origins=settings.CORS_ALLOWED_ORIGINS,
    allow_headers=settings.CORS_ALLOWED_HEADERS,
    allow_methods=settings.CORS_ALLOWED_METHODS,
    allow_credentials=settings.CORS_ALLOW_CREDENTIALS
)

After installing Channels and Daphne, you’ll see the issue. I noticed that in AuthGraphQLProtocolTypeRouter:
http_urls: list[URLPattern | URLResolver] = [
            re_path(url_pattern, GraphQLHTTPConsumer.as_asgi(schema=schema)),
        ]

So  requests end up at GraphQLHTTPConsumer, where multipart_uploads_enabled defaults to False if it isn’t passed (and is never passed). Since they never reach AsyncGraphQLView, the file upload config doesn’t apply, leading to the error.
For a fix I found out that the most straight forward one will be to be able to config the multipart_uploads_enabled inside the AuthGraphQLProtocolTypeRouter like this:
class AuthGraphQLProtocolTypeRouter(ProtocolTypeRouter):
    """Convenience class to set up GraphQL on both HTTP and Websocket.

     This convenience class will include AuthMiddlewareStack and the
     AllowedHostsOriginValidator to ensure you have user object available.

    ```
    from strawberry_django.routers import AuthGraphQLProtocolTypeRouter
    from django.core.asgi import get_asgi_application.

    django_asgi = get_asgi_application()

    from myapi import schema

    application = AuthGraphQLProtocolTypeRouter(
        schema,
        django_application=django_asgi,
    )
    ```

    This will route all requests to /graphql on either HTTP or websockets to us,
    and everything else to the Django application.
    """

    def __init__(
        self,
        schema: BaseSchema,
        django_application: ASGIHandler | None = None,
        url_pattern: str = "^graphql",
        multipart_uploads_enabled: bool = False,
    ):
        http_urls: list[URLPattern | URLResolver] = [
            re_path(url_pattern, GraphQLHTTPConsumer.as_asgi(schema=schema, multipart_uploads_enabled=multipart_uploads_enabled)),
        ]
        if django_application is not None:
            http_urls.append(re_path(r"^", django_application))

        super().__init__(
            {
                "http": AuthMiddlewareStack(
                    URLRouter(
                        http_urls,
                    ),
                ),
                "websocket": AllowedHostsOriginValidator(
                    AuthMiddlewareStack(
                        URLRouter(
                            [
                                re_path(
                                    url_pattern,
                                    GraphQLWSConsumer.as_asgi(schema=schema),
                                ),
                            ],
                        ),
                    ),
                ),
            },
        )

And then we can simply config like this:
application = AuthGraphQLProtocolTypeRouter(
    schema,
    django_application=django_application,
    multipart_uploads_enabled=True
)

application = CORSMiddleware(
    application,
    allow_origins=settings.CORS_ALLOWED_ORIGINS,
    allow_headers=settings.CORS_ALLOWED_HEADERS,
    allow_methods=settings.CORS_ALLOWED_METHODS,
    allow_credentials=settings.CORS_ALLOW_CREDENTIALS
)

It works well but requires setting multipart_uploads_enabled in two places, which might not be ideal. I’m not entirely familiar with the codebase, so there may be a better approach
Thank you for your assistance! I’m looking forward to getting this resolved, as it’s currently blocking a major Strawberry upgrade release in one of our projects. In the worst-case scenario, we can override the AuthGraphQLProtocolTypeRouter in our project until the fix is applied in the main repository. Please let me know if there’s anything I can do to help and sorry again for the time lost due to my oversight in not mentioning the ASGI part.


movie module is down

The backend API has gone private, and is no longer free.
https://www.patreon.com/posts/api-is-going-10743518
Look for an alternative.
P.S. It'd be great to have #207 resolved asap, rather than have people report that a module is down in the gitter chatroom! 😅

What do you think of: https://www.themoviedb.org/documentation/api ?

One disadvantage of using TMDb is that it doesn't generate an IMDB link the way OMDb did. I have a basic module patch for TMDb at: https://github.com/edadesd/JARVIS-on-Messenger/commits/movieAPI

Why not use the official rotten tomatoes api? It's legal and just as legit as imdb.

Rotten Tomatoes and Fandango APIS: https://developer.fandango.com/
It sounds like the Rotten Tomatoes API only gives reviews and scores. The (related) Fandango API says it can give movie information, but from the documentation it doesn't appear that you can search by movie name. You have to search by location to get movies showing at nearby theaters.

TMDb it is, then.

You can keep looking for another API if you want. I only linked to my TMDb patch instead of setting up a PR in case someone found a better API to use.

IMDb id is important, as we only provide a gist of the movie information in the response.
Here's a relevant link: https://www.themoviedb.org/talk/5851f2ddc3a368258c0127b0 😉

That's a good link, thanks for finding it. I'll work on a version that uses the TMDB ID to fetch the IMDB ID and makes an IMDB link.

Opened PR #251 to address this.


fix: clean up broken links

Description

Running lychee link checker on main returns a number of invalid links that should be cleaned up. Hopefully, some links can be updated during the PR review. Others can be left in /.lycheeignore permanently.
There is also an attempt to add a link to product selector. It was formerly committed or rendered with unsafe characters unencoded, such as {, [, :. For details on unsafe characters, see RFC 1738 > 2.2. URL Character Encoding Issues.

Related

Testing

Checklist
Before submitting a Pull Request, please ensure the following:

[x] 🚨 This PR does not introduce breaking changes.
[x] All CI checks (GH Actions) pass.
[ ] Documentation is updated as needed.
[ ] Tests are updated or added as necessary.
[ ] Code is well-commented, especially in complex areas.
[x] Git history is clean — commits are squashed to the minimum necessary.

@alisitszn I know that you maintain ESP-Modbus repo. I have a link to it that returns 404.
Can you please propose what to replace this link with?

@f-hollow,
The documentation for the esp-modbus project is the same for all targets. the component has the dependencies to standard components such as UART driver, LWIP, MDNS, esp-timer. The correct link to this documentation for esp-modbus v1.0.x.


Intermittently getting 'Unable to retrieve stored state!'

I'm using the Google OAUth2 provider and for some reason we are getting the error below intermittently:
authomatic: Google: Continuing OAuth 2.0 authorization procedure after redirect.
authomatic: Google: Validating request by comparing request state with stored state.
authomatic: Google: Reported suppressed exception: FailureError('Unable to retrieve stored state!',)!
authomatic: Google: Procedure finished.
 Error during authentication flow Unable to retrieve stored state!

See below how I'm initializing Webapp2Session:
session = Webapp2Session(self, session=self.session)

Any clue on what could be causing this ?
Thanks in advance
Fábio

I'm getting this for FaceBook now—did you ever figure out how to fix this error?

I'm also seeing this error on chrome vChrome/56.0.2924.87 with the build 0.1.0.post1

We have had a big overhaul of code with several PRs and other issues resolved. Please can you try this again with the latest code from master and let us know if the issue is still persists.

Hi @mrichar1 ,
Thank you so much for the awesome work!
I'm currently using the latest pull from Github master and am seeing similar error by the following Django code:
@require_http_methods(('GET',))
def login(request):
    response = HttpResponse()
    result = AUTHOMATIC.login(DjangoAdapter(request, response), 'google')
    if result and result.user:
        if not getattr(result.user, 'email', None):
            result.user.update()
            # Some customized AuthBackend stuff here
        response = HttpResponseRedirect('/')
    elif result and result.error:
        print(result.error)
        return HttpResponse('{"msg": "login-failed"}', status=401)
    return response

# printed error being:
> Unable to retrieve stored state!

Suspecting the handling of session is not quite updated with Django 1.11.2 which is the version we are using. I've added some random print-outs and it seems that the session was indeed set after _session_set but upon _session_get at phase 2 the session object becomes an empty dict.
The cookie is returned to the browser as Set-Cookie: authomatic=... with correct domain and path values though. Thank you very much!

Hi @xch91 - thanks for the extra info.
I've tried using google as a provider with the django example in the repo (after making some appropriate updates to get it working with django > 1.10 (#185).)
I can't seem to get it to fail in the way you describe - logins are always successful, and the _sesison_get('csrf') always returns an appropriate value.
Can you try using the example code to at least rule out any issues elsewhere in your code that I can't see?  The only change you'll need to make (apart from applying #185) is to add google to the views - something like:
--- a/examples/django/example/simple/views.py
+++ b/examples/django/example/simple/views.py
@@ -13,7 +13,7 @@ authomatic = Authomatic(CONFIG, 'a super secret random string')
 def home(request):
     # Create links and OpenID form to the Login handler.
     return HttpResponse('''
-        Login with Facebook.

+        Login with Google.

         Login with Twitter.

         <form action="login/oi">
             <input type="text" name="id" value="me.yahoo.com" />

Thanks!

Hi @mrichar1 ,
That was a very prompt reply 👍
I tried to mimic something similar to the simple app as closely as possible (with no AUTHENTICATION_BACKENDS and tried both cache and signed_cookie as SESSION_ENGINE) but still seeing the same error. If I subclass oauth2.Google and explicitly disable supports_csrf_protection, it works unproductionly smoothly.
The simple app was also tried but it returns an 'Invalid Signature' error which I haven't dug deep into XDD
Thank you :)

Thanks for testing!
Invalid Signature: is raised when deserializing the cookie when getting data, if the returned signature doesn't match the one sent. This implies that something is interfering with the data coming and going between the app, the oauth provider and/or the browser.
Can you let me know what browser you are using for testing, and also try without any browser plugins or other add-ons enabled ('private browsing' mode is probably a good idea).
Can you also check that the time is correctly in sync on both the client where the browser is running, and the app server?

Argh!!! I tried another time with Opera Private mode and it worked XDD
What happened to my good old Chrome?!
Thank you so much for the million dollar suggestion. Will explore into the syndrome later.

xch91: If you do find out the issue in the browser, please let us know so we can document/expect it.

Always develop in private mode. Otherwise try CTRL F5 to force full refresh.

After several years of inactivity, authomatic is now under community management, and we have just released a new stable version (1.0.0).
We are now reviewing all issues and PRs and hoping to begin work to solve as many of these as possible.
We are keen to find out which issues still apply, and which PRs are still required/are likely to merge cleanly into the current code. We are aiming to review them all, but any help with prioritisation would be very useful!
If you are still interested in having this issue/PR resolved, or are able to help us work on it, please reply to this message. That way we know which issues are most important to the community.


Modified 78, 82 to prevent edge cases of functions and objects converting to strings

We had edge cases in nested templates where functions and objects were getting concatenated to empty strings resulting in [Object] or function() { ...} appearing in the rendered HTML. Simply checking that the second argument to concat was not going to be the empty string solved the problem. We ran your tape test suite. All tests passed. We were unable to define a simple unit test that reproduced the error we were having, but it has definitely been resolved.

Heya; this patch looks good to me — but could you perhaps remove the comments? I agree with you a test would be better; but the inline comment looks a bit distracting. Thanks!

Will do
On Oct 31, 2017 2:51 PM, "Yoshua Wuyts"<EMAIL_ADDRESS>wrote:

Heya; this patch looks good to me — but could you perhaps remove the
comments? I agree with you a test would be better; but the inline comment
looks a bit distracting. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/choojs/hyperx/pull/61#issuecomment-340870077, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEuqS5OEqx24B3DPRJvhc6DASbW7ASWJks5sx2wfgaJpZM4QKazs
.

Comments removed

v2.3.2 :tada:


[CELEBORN-1742] Fix bounded driver Inbox deadlock

What changes were proposed in this pull request?
fix the deadlock by clear the message queue if it has been full before we put OnStop message
Why are the changes needed?
it is possible that the message queue has been full when we want to insert OnStop, and unfortunately, we have to hold the inbox as the lock when doing this....
this creates the scenario of deadlock, main thread is waiting for more capacity holding inbox lock, message processors are stuck because it needs inbox lock
(the screenshots are based on 0.4 client tho)
main thread:

processor thread:

Does this PR introduce any user-facing change?
no
How was this patch tested?
in prod

@CodingCat, please fix the failed test case RpcEnvSuite.

Was this bug introduced by https://github.com/apache/celeborn/pull/2366?

Was this bug introduced by https://github.com/apache/celeborn/pull/2366?

yes

It seems current main/branch-0.5 doesn't have this bug, because the messages object of Inbox is using a LinkedList.  But from your screenshot, it seems to be a blocking queue @CodingCat

It seems current main/branch-0.5 doesn't have this bug, because the messages object of Inbox is using a LinkedList. But from your screenshot, it seems to be a blocking queue @CodingCat

actually, I found that it is true that current master does not have this issue, however, it was lucky to have a bug which misses the check of the queue length when adding onStop
so I am not entirely sure what the ideal way is to move forward here....

The current code doesn't seem to have any obvious issues, and I prefer to keep the status, so I close this PR unless new problems arise.


Add Amazon Managed Grafana check in the UserAgent string header

To support this issue in the AWS IoT TwinMaker plugin repo: https://github.com/grafana/grafana-iot-twinmaker-app/issues/217
We want to track which of our customers are using Amazon Managed Grafana (AMG) to run this plugin, or a self-managed Grafana server. We can do this by checking the AWS_TRAVERSAL_FETCH variable. This is a configuration option for the AWS Datasource provisioner app, which is only used in AMG.
Adding this check for AMG in each AWS call will allow all AWS services that own Grafana plugins to publish metrics about Grafana and AMG usage. This is particularly important for AWS IoT TwinMaker.
The easiest way to notify AWS IoT TwinMaker is through the user agent header in each API call. We already provide information about the Grafana build and runtime version. We should also add whether this is in AMG or not.

Follow up will remove custom UserAgent logic in the AWS IoT TwinMaker plugin and rely on the grafana-aws-sdk to set the header

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fix: downgrade got to v11

Fixes #85

Tests pass locally

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


Update dependencies, travis and fix test

Update some dependencies
Fix zip-file downloader for not existing zip files
Remove deprecated options in test

also fix the deprecation warning of archive.bulk() (#462)

hmm, travis crashed here o.O I think it's a travis problem, I've run the same commit in my repo & there travis has no problems ...
https://travis-ci.org/piwonesien/nw-builder/jobs/357921814 -> this pr works
https://travis-ci.org/nwjs-community/nw-builder/jobs/357921882 -> this pr fails

This would also bring in a newer version of hoek, which has a vulnerability < 4.2.1
https://nodesecurity.io/advisories/566

Hi, any updates?

@f3l1x  Will publish to npm asap


virtctl console fails if VM is marked as running but is not

/kind bug
What happened:
$ virtctl console node
Successfully connected to node console. The escape sequence is ^]
                                                                 Virtual Machine's /var/run/kubevirt-private/79f2438a-bfcc-11e8-b6af-5254000b34fc/virt-serial0 socket is currently unavailable

when a VMI is in this state:
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: 2018-09-24T07:37:28Z
    message: 'server error. command Launcher.Sync failed: virError(Code=1, Domain=10,
      Message=''internal error: process exited while connecting to monitor: 2018-09-24T07:37:28.537019Z
      qemu-system-x86_64: -drive file=/var/run/kubevirt-private/vmi-disks/rootvolume/disk.img,format=raw,if=none,id=drive-ua-rootdisk:
      Could not open ''/var/run/kubevirt-private/vmi-disks/rootvolume/disk.img'':
      Permission denied'')'
    reason: Synchronizing with the Domain failed.
    status: "False"
    type: Synchronized
  interfaces:
  - ipAddress: <IP_ADDRESS>
  nodeName: localhost
  phase: Running

What you expected to happen:
Console does nto connect while the VM is in a bad state OR it waits until it's good
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version): v0.8.0
Kubernetes version (use kubectl version):
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

@fabiand This PR https://github.com/kubevirt/kubevirt/pull/1323 didn't fix this issue?

/close


inventories: create BlockingInventory

I create an executor every time we call next_batch.
Another option is to do:
@staticmethod
@cache
def get_executor() -> Executor: ...

And use the same executor for all calls, but then it isn't clear who should shutdown the executor.

@isra17 review plz!

Really not a fan of creating an executor on each call, this is where most of the overhead is spent. I see 3 ways:

Use the default executor (Pass None)
Use __init__ to create an executor? And add a close method to cleanup inventories, called by the Job using it.
Add a service to the ServicesManager that provides an executor.

I guess using the default executor is the simplest, it pretty much just create a ThreadpoolExecutor in the asyncio loop instance and take care of cleaning and all.

Using the default executor is simple enough. Done.


All Amplify builds suddenly started failing (even past successful builds)

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
React
Amplify APIs
REST API
Amplify Version
v6
Amplify Categories
function
Backend
Amplify CLI
Environment information

# Put output below this line
  System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 631.20 MB / 15.72 GB
  Binaries:
    Node: 20.8.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.15.5 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Chromium (126.0.2592.68)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @getbrevo/brevo: ^1.0.1 => 1.0.1
    @prisma/client: ^5.16.0 => 5.16.0
    @types/aws-lambda: ^8.10.92 => 8.10.137
    aws-sdk: ^2.1415.0 => 2.1605.0
    aws-serverless-express: ^3.3.5 => 3.4.0
    body-parser: ^1.20.2 => 1.20.2 (1.20.1)
    dotenv: ^16.3.1 => 16.4.1
    express: ^4.15.2 => 4.18.2
    fyers<EMAIL_ADDRESS>=> 0.0.1
    jsencrypt: ^3.3.2 => 3.3.2
    multer: ^1.4.5-lts.1 => 1.4.5-lts.1
    node-rsa: ^1.1.1 => 1.1.1
    prisma: ^5.16.0 => 5.16.0
    rsa-key: ^0.0.6 => 0.0.6
    stripe: ^12.17.0 => 12.18.0
    tastytrade<EMAIL_ADDRESS>=> 0.0.4
    tradestation<EMAIL_ADDRESS>=> 0.0.4
    tradier<EMAIL_ADDRESS>=> 1.0.23
  npmGlobalPackages:
    @aws-amplify/cli: 12.10.1
    corepack: 0.20.0
    npm: 10.1.0
    pnpm: 8.15.5
    yarn: 1.22.22

I've removed tokens for security

Describe the bug
Backend build fails with this error:
42 2024-06-26T16:55:05.445Z [WARNING]: ✖ There was an error initializing your environment.

43 2024-06-26T16:55:05.451Z [INFO]: 🛑 Packaging lambda function failed with the error

44 Command failed with exit code 1: yarn amplify:brokerboticsapi

45 npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>
When the build started failing, the version of prisma in yarn-lock was 5.15 (package.json had "^5.15.0"). So I was really confused to see 5.16. I changed package.json to have "5.15.0" exactly and got the same error. After that I updated my package.json to have "^5.16.0" to see if that fixes the problem. But I still got the same error. After that I tried running a build that was successful in the past to eliminate doubts that new code is causing the error. Past successful builds are also failing now.
Expected behavior
Builds in amplify should succeed and backend should get deployed.
Reproduction steps
I have amplify set up to build on pushes to certain branches. Expectation is that those builds should succeed in Amplify. The error stared happening yesterday. Last successful build was 6/21/2024. Same build fails today.
Code Snippet
// Put your code below this line.

Log output

// Put your logs below this line

aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response

@cwomack Thanks. After updating the token I'm back to the original error. But I read it in more detail and have narrowed down the real issue to this:
46 Error: Could not find Prisma Schema that is required for this command.
47 You can either provide it with `--schema` argument, set it as `prisma.schema` in your package.json or put it into the default location.
48 Checked following paths:
49 schema.prisma: file not found
50 prisma/schema.prisma: file not found
51 prisma/schema: directory not found

I suspect something has changed in the last few days with how the amplify backend deals with paths because the schema file is in the default location of prisma/schema.prisma and nothing has changed otherwise.

So, I figured out the issue. I had a script in the frontend package.json called "amplify:brokerboticsapi" where brokerboticsapi is the name of my function. That script has been there in the package.json for 12 months according to github but it was never run until recently. And that script errored out causing all my problems. I removed it and a deploy succeeded.


Error validating shader  33

On my Mac:
Error validating shader  33

Furthermore:
Error validating shader  33
Shader  34  ( ../src/glsl/GenerateVolumeEnt.c ) compile error:  WARNING: 0:2: extension 'GL_ARB_uniform_buffer_object' is not supported

Shader  35  ( ../src/glsl/GenerateVolumeEnt.c ) compile error:  WARNING: 0:2: extension 'GL_ARB_uniform_buffer_object' is not supported

Program  75  link error:  WARNING: Output of vertex shader 'finalVec' not read by fragment shader

Full information:
blockSizeInHolders: 16
blockSizeInPixels: 32768
terDataBufPitchScaledXY 48
maxChangesInHolders: 8
volGenFBOX: 128
volGenFBOY: 16384
visPageSizeInPixels: 512
holderSizeInPixels: 2048
bufferMult: 1.25
metersPerLot: 64
pixelsPerMeter: 128
unitsPerMeter: 4
blockSizeInLots: 4
pixelsPerUnit: 32
unitsPerLot: 256
pixelsPerLot: 8192
holderSizeInPages: 4
holdersPerLot: 4
visPageSizeInUnits: 16
unitSizeInPixels: 32
worldSizeInBlocks:    256.000000   256.000000   1.000000
worldSizeInLots:    1024.000000   1024.000000   4.000000
worldSizeInHolders:    4096.000000   4096.000000   16.000000
worldSizeInPages:    16384.000000   16384.000000   64.000000
worldSizeInTerData:    4096.000000   4096.000000   32.000000
MAX_UNIFORMS: 32767

worldSizeInPixels:    8388608.000000   8388608.000000   32768.000000
Error validating shader  33
Shader  34  ( ../src/glsl/GenerateVolumeEnt.c ) compile error:  WARNING: 0:2: extension 'GL_ARB_uniform_buffer_object' is not supported

Shader  35  ( ../src/glsl/GenerateVolumeEnt.c ) compile error:  WARNING: 0:2: extension 'GL_ARB_uniform_buffer_object' is not supported

Program  75  link error:  WARNING: Output of vertex shader 'finalVec' not read by fragment shader

FONT LOAD

FONT LOAD

Loading:  ../data/fonts/arial_regular_24.js
Load Successful

Valid JSON

Loading:  ../cdat/lastJSONBuffer.js
Load Successful

Valid JSON

Loading:  ../cdat/lastImageBuffer.txt
Load Successful
Sea Level: 171
start place cities
end place cities
start grow provinces
end grow provinces
start find neighboring cities
end find neighboring cities
start find city blocks
end find city blocks
start add in city roads
end add in city roads
start link close cities
end link close cities
start find biggest ocean gaps
iteration: 0
iteration: 1
end find biggest ocean gaps
start road regions
end road regions
start filling houses
end filling houses
DONE WITH MAP
Loading:  ../cdat/lastJSONBufferGUI.js
Load Successful

Valid JSON

getJVNodeByString(inventoryData.items)
inventoryData
items
getJVNodeByString(inventoryData.items)
inventoryData
items
Loading GUI Values
Loading:  ../cdat/saves/save0/compMap.txt
Load Successful
End Loading GUI Values
Error validating shader  129
Shader  130  ( ../src/glsl/GenerateVolumeEnt.c ) compile error:  WARNING: 0:2: extension 'GL_ARB_uniform_buffer_object' is not supported

Shader  131  ( ../src/glsl/GenerateVolumeEnt.c ) compile error:  WARNING: 0:2: extension 'GL_ARB_uniform_buffer_object' is not supported

Program  171  link error:  WARNING: Output of vertex shader 'finalVec' not read by fragment shader

GW DONE
copyTerToTexture resIndex:  0
2016-08-04 19:46:12.972 VoxelQuest[19127:155909] GLUT Warning: glutCurrentModifiers: do not call outside core input callback.

Thanks, I will take a look

See comment in this commit.
https://github.com/gandf/vqisosmall/commit/7037d346b3fae1d44f0cc8c43d716a3dcb30a8a8
Texture3D doesn't work without parameter. I wrote "//***" at end lines to modify in GenerateVolume.c and f00300_singleton.hpp.
Thanks.

Some tests on windows 10 :

AMD graphic card HD6970 on desktop : Issue with Texture3D in shader GenerateVolume.c
INTEL Iris Pro Graphics 5200 on laptop : Issue with Texture3D in shader GenerateVolume.c
nVidia Geforce GTX 960M on laptop : no issue. All work.

I think this is a problem with an old OpenGL versions I've mentioned here.

AMD Driver give log (not INTEL).

Validation failed! - Different sampler types for same sample texture unit in fragment shader.

Error is because we can only use ont type of sampler. We can use sampler2D or sampler3D.
uniform sampler3D Texture0; //volume texture nearest uniform sampler3D Texture1; //volume texture linear uniform sampler2D Texture2; //terrain heightmap uniform sampler2D Texture3; //terrainID // no longer used uniform sampler3D Texture4; //ter tex
Since all texture3D have been disable, only texture2D are used and work on all GPU.
I think we need to do two shader.

@gandf - its possible that upping the shader version would allow texture3D where it is failing, but that would involve a bit of other work as the OpenGL pipeline on the c++ end changes as well (no more use of old commands like glBegin, etc)

Currently, this game engine is not enought quick to be used for game.
I think what we need to do upgrade version to GLSL 330 to have most of current hardware working with this engine. This will increase performance and fluidity.
Work already done is significant and switch to version 330 needs to change code structure and how code works.
With new version, we can't use direct access to write if we want to improve performance.
What do you want us to do ?

nothing : only nVidia GPU can run slowly game.
upgrade to version 140 : A lot of work most GPU compatible with run slow game.
upgrade to version 330 : most GPU compatible with better performance but greatest work.

I'm not openGL developer and I can't say what we should and may to do.

@gandf - upgrading to 330 is probably a good idea for compatibility purposes, but I don't think you will get much in the way of performance gains unless you actually change the underlying algorithms.  There are plenty of ways to make it faster, but you will probably have to rethink the core algorithms.  On high end hardware (gtx 980/1080) it is playable but the chunk picking system sucks (and thus much time is wasted in loading empty chunks and chunks that are underground). In future versions I have better chunk picking/loading (such as the following perspective version).


New package: Samsung.UpdatePlus version <IP_ADDRESS>

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/111982&drop=dogfoodAlpha

Supporting custom hardware in validation is "Not Planned".

https://github.com/microsoft/winget-pkgs/issues/199504


bug in read_data

I have discovered a clear bug in the read_data method of Database.   The bug is failure to properly handle an error in specifying a normalize collection.    The bug was uncovered by my a dumb mistake I made while using the reader where I remembered a name wrong.  That is I used normalize=['event','site'] instead of the mspass schema correct call normalize=['source','site'].
I don't know how you do the links to github to a highlight a code segment, so I'll just paste  in the problem code.  This is lines 334-350 of database.py:
        # 1.2 read the attributes in the metadata schema
        col_dict = {}
        for k in read_metadata_schema.keys():
            col = read_metadata_schema.collection(k)
            # 1.2.1. col is not None and is a normalized collection name
            # 1.2.2. normalized key id exists in the wf document
            # 1.2.3. k is not one of the exclude keys
            # 1.2.4. col is in the normalize list provided by user
            if col and col != wf_collection and col+'_id' in object_doc and k not in exclude_keys and col in normalize:
                if col not in col_dict:
                    col_dict[col] = self[col].find_one(
                        {'_id': object_doc[col + '_id']})
                # might unable to find the normalized document by the normalized_id in the object_doc
                # TODO: this is not covered by test
                if not col_dict[col]:
                    continue
                md[k] = col_dict[col][self.database_schema[col].unique_name(k)]

That throws this error that is not at all descriptive of the true problem:

  File "/home/pavlis/data/copy_pwmigtest/runpwstack.py", line 18, in <module>
    pwstack_return = pwstack(db,pf,slowness_grid_tag='Slowness_Grid_Definition')

  File "/home/pavlis/.local/lib/python3.8/site-packages/pwmigpy/pwmig/pwstack.py", line 398, in pwstack
    d=read_ensembles(db,q,control)

  File "/home/pavlis/.local/lib/python3.8/site-packages/pwmigpy/pwmig/pwstack.py", line 274, in read_ensembles
    d=db.read_ensemble_data(cursor,collection='wf_Seismogram',

  File "/home/pavlis/.local/lib/python3.8/site-packages/mspasspy/db/database.py", line 2244, in read_ensemble_data
    data = self.read_data(i, mode=mode, normalize=normalize, load_history=load_history, exclude_keys=exclude_keys, collection=wf_collection,

  File "/home/pavlis/.local/lib/python3.8/site-packages/mspasspy/db/database.py", line 350, in read_data
    md[k] = col_dict[col][self.database_schema[col].unique_name(k)]

KeyError: 'net'

The TODO comment in the code is right on target because that is indeed the section that has the problem.
I would try to fix this, but I am afraid I'm not totally sure what all that code section is doing.   Besides fixing this bug I suggest whoever gets the job of doing the fix add some additional comments on what each code segment in the read_data method is doing.
What is needed is fairly clear, but how to do so is not something I want to try as the complexity here could create unintended side effects created by my incomplete understanding of this code.  That is, what is needed is to just trap the error condition I made early in the read code:  an undefined normalize collection.    It should be assumed that collection listed as one to use for normalization should be defined in the schema.  It seems fair to abort if one tries to use an undefined collection as I did.

@haruming Could you please address this? Seems to be an easy fix.

Sure, I will look into it soon!

Sorry, but there seems to be more to this problem.  Note in all those words above the error thrown was a KeyError exception on the attribute with the key "net".   I think there is a bigger bug in that section related to handling of whether or not an attribute is "normal" (or other similar) versus "required".  The problem I'm seeing is that when the reader is run on data I'm trying to load this code segment is doing something wrong.    Here is my debug version I tried with print statements needed to understand the output I'll show after:
        # 1.2 read the attributes in the metadata schema
        col_dict = {}
        for k in read_metadata_schema.keys():
            col = read_metadata_schema.collection(k)
            # debug
            print(k,col)
            # 1.2.1. col is not None and is a normalized collection name
            # 1.2.2. normalized key id exists in the wf document
            # 1.2.3. k is not one of the exclude keys
            # 1.2.4. col is in the normalize list provided by user
            if col and col != wf_collection and col+'_id' in object_doc and k not in exclude_keys and col in normalize:
                if col not in col_dict:
                    col_dict[col] = self[col].find_one(
                        {'_id': object_doc[col + '_id']})
                # might unable to find the normalized document by the normalized_id in the object_doc
                # TODO: this is not covered by test
                if not col_dict[col]:
                    continue

                md[k] = col_dict[col][self.database_schema[col].unique_name(k)]
                # debug
                print('metadata set=',k,md[k])

The print statements when this was run are these leading up to the KeyError exception being thrown at line 350:
_id wf_Seismogram
npts wf_Seismogram
delta wf_Seismogram
sampling_rate wf_Seismogram
starttime wf_Seismogram
time_standard wf_Seismogram
calib wf_Seismogram
site_id wf_Seismogram
source_id wf_Seismogram
tmatrix wf_Seismogram
net site

The if conditional block is not entered at all until the "net site" pair is tested.   On  line 350 [self.database_schema[col].unique_name(k)] correctly resolves to 'net'.   The problem is this:
IPdb [4]: col_dict[col]
{'_id': ObjectId('617d4c2766d6360656038e87'), 'lat': 36.389, 'lon': -121.552, 'elev': 0.542, 'coordinates': [-121.552, 36.389], 'sta': 'HAST'}

which shows this problem is being created by an issue with this data set that conflicts with the code is trying to do.  My "site" collection for this test data set does not define "net" or "loc".  Both are listed in the schema as "normal", but this section is treating them like they are required.
I think there may also be a build in  inefficiency in this code section whose solution might be a solution to this bug.  I wonder if that loop should not be driven by what actually is in col_dict instead of looping through the keys defined in the schema.   The alternative fix is to bypass the problem code if a key is not required.  I'm not sure which is right that would not produce unintended consequences.  I think I understand this code a bit better right now but it is still a bit mysterious.
To be clear - the original bug point remains an issue.  This just shows there is a second bug hidden in the same code block and the error was mysterious because my guess about the case (using 'event' instead of 'source') was not the actual problem. I reiterate the original remains an issue also.

Aha, this is clearly a bug. A missing "normal" key should be captured and logged in the elog here. I guess part of the problem is that in our design doc, we did not define the behavior for missing keys. The constraints such as required, normal, and optional are designed for mismatching types only. We did not consider this scenario where the key definitions are mismatched between the schema and database. Part of it is that we expect the user to change the schema when needed. However, such an error is inacceptable anyway.

That's a clear bug and I didn't find that earlier, thanks for pointing it out!
I think we better ignore reading the attributes if they are not in the normalized records. However, if they are required attributes, we should post an elog entry to the wf object created after.

I agree.   Incidentally this bug will cause any read to fail with normalization if any attribute listed in the schema is not defined in the document linked with the id (the normalizing document from a collection like site and source.)   I know this because I had to do a workaround for source as well as site until this is fixed.


Filter out migration folder if they don't exist

$projectDir/src/flyway/kotlin/db/migration/sqlite causes issues when building as it's not included in the repository. This checks if the folders exist to get around the issue

Thanks for the contribution!


Support for Python 2 virtualenvs

Would you consider adding support for Python 2 virtualenvs if I'm contributing a PR?
There are various reasons for having that feature. E.g. packages which are Python 2 only (#65) or if you want to have something like flake8 for Python 2 and for Python 3 available.
This shouldn't be to hard:

use virtualenv instead of venv in create_venv if Python 2 is the base Python
fix get_binaries_script so it is 2/3 compatible
add a --binary-suffix flag which is passed to expose_binaries_globally so you can install the same binary from multiple venvs (so maybe create a flake8-2.exe). To make upgrade work we have to store the suffix in a config file. But this might be an interesting feature even without Python 2 virtualenvs.

I appreciate the offer and would probably be open to it, but there is still the issue of not having pathlib installed, no f-strings, various subprocess incompatibilities and likely some encode/decode issues.
After those were fixed, then your changes could be added. But I am not interested in maintaining a codebase without those features 😞 . I suppose pipsi might work for this use case?

@cs01 if you are OK with having version dependent dependencies, there are backports for subprocess and pathlib. There is even an f-string backport but to be honest, I would feel reluctant to use it on "production". Plain strings are not the end of the world after all.

There will be some cases where packages only have a Python 2 implementation, but they are in a minority (I think). In those cases, pipx will not be an option and virtualenv or a system install will have to be used instead. There are lots of tools moving to Python 3.6+ only, and I think this is a good thing because it forces people to get unstuck from old versions. So although I wish I could promise support for all environments, I have to make tough choices around my own sanity/support workload (I do this in my spare time) and which environments the tool is advertised to support.

get_binaries_script is run in the venv so it must be Python 2/3 compatible. Actually, I don't like this style of having the script embedded as string (no source code checking possible, not really debuggable, etc.). What do you think about putting this in a real script and just passing arguments to it?
What do you think about --binary-suffix (I would really need this for my use case: two flake8 versions)? At first, we could ignore the config file / upgrade issue as upgrades are not reproducible anyhow (see other open issues).

I know these types of comments aren't that helpful, but I'd love to have the ability to do this to install geeknote through pipx

Actually, I don't like this style of having the script embedded as string (no source code checking possible, not really debuggable, etc.). What do you think about putting this in a real script and just passing arguments to it?

@schlamar I love this idea. I have been meaning to do this. pipsi does it.

What do you think about --binary-suffix (I would really need this for my use case: two flake8 versions)? At first, we could ignore the config file / upgrade issue as upgrades are not reproducible anyhow (see other open issues).

What would this do? Install to a different pipx venv?

I know these types of comments aren't that helpful, but I'd love to have the ability to do this to install geeknote through pipx

@aiguofer No way, I definitely appreciate it. Good to know the work won't go to waste.

What would this do? Install to a different pipx venv?

No, this would just append a suffix to the binaries in expose_binaries_globally. There are scripts which behave different depending on the Python version they are installed with. E.g. flake8 does checking for Python 2 when installed on Python 2 and checking for Python 3 when installed on Python 3.
So my idea to get a flake8.exe for Python 3 and a flake8-2.exe for Python 2:
pipx install flake8  # default flake8.exe for Python 3
pipx install flake8-2 --binary-suffix -2 --python C:\Python27\python.exe --spec flake8  # installs flake8 with Python 2 as flake8-2.exe

Oh I see what you mean. That is a pretty cool idea. It would require pipx to change how it installs packages since pipx uses the folder name of the virtual environment to determine the package name. So pipx currently would not let you install a package of the same name with two different versions.
I am not sure this is something that belongs in pipx because it starts going into areas where I think there would not be very many users plus it would be hard to implement and maintain. You might be better off just manually creating a venv and a symlink at that point.

It would require pipx to change how it installs packages

No, actually you can already install unrelated packages with the spec parameter (see my example call above). The only change would be passing the suffix to expose_binaries_globally and append it to the targets of copy/symlink operations.

Pipx has been modified to have its inline strings in a script like you mentioned.  It will be easier to support python2 only packages if you want to give it a shot now.

Thanks. This is definitely on my TODO list, but I'm kind of busy right now...

Hi,
I would be very interested in having support in pipx for Python 2. Isolating old apps is in my opinion perfect use case for pipx.
Does anyone have some info about this feature?

You want to look at pipx.venv.Venv.create_venv(), and change the call to use virtualenv instead (and also provide the corresponding flags). Environments created by virtualenv 20.0+ are expected to be completely compatible with ones created by the standard library venv, and I expect the change to cause minimal impact.
Note that, however, since virtualenv carries a bunch of extra dependencies, it is unlikely a good idea to carry virtualenv as a hard dependency of pipx. I would try to do something like:

Try the virtualenv command, if available.
Use venv, if the Python version is 3.4 or later.
Generate an error message saying the user needs to pipx install virtualenv for Python 2 support.

Since Python 2 is EOL, this isn't something we have the time or inclination to support in pipx.


Asus (RGB.NET) not working

Expected Behaviour
Aurora controls MB and VGA LEDs
Actual Behaviour
Asus (RGB.NET) can't initialize. The following message is presented: "Device provider "Asus (RGB.NET)" threw exception System.IO.FileNotFoundException: Could not load file or assembly 'Interop.AuraServiceLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified."
Reproduction steps
Just open the program
Frequency
Every time
Aurora Version:
v143
Previously an Issue?
No. It worked in v131.
2023-05-27 09.49.20.log

Thanks for the report. I'm trying to fix it

Same here. Do you need any logs for this one?

Didn't need. After lots of work I finally managed to fix it. I will make the release once I fix other bug I have locally 👍🏻

Can you try the latest release?
https://github.com/Aurora-RGB/Aurora/releases/tag/v144

yes it's working now!
thanks a lot :)


[bug] Cant Access the url api route next js when finish build and open application

Describe the bug
when dev environment is api route is all working when build the application and run the api is not working

Reproduction
No response
Expected behavior
No response
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.22621 X64
    ✔ WebView2: 121.0.2277.128
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.11.1
    - yarn: 1.22.21
    - npm: 8.19.2

[-] Packages
    - tauri [RUST]: 1.6.0
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.7
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.10

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../out
    - devPath: http://localhost:3000/
    - framework: React (Next.js)
    - bundler: Webpack

Stack trace
No response
Additional context
this is my tauri.conf.json
{
"$schema"<EMAIL_ADDRESS>"build": {
"beforeBuildCommand": "yarn build ",
"beforeDevCommand": "yarn dev",
"devPath": "http://localhost:3000",
"distDir": "../out"
},
"package": {
"productName": "tauri-app",
"version": "0.1.0"
},
"tauri": {
"allowlist": {
"all": true
},
"bundle": {
"active": true,
"category": "DeveloperTool",
"copyright": "",
"deb": {
"depends": []
},
"externalBin": [],
"icon": [
"icons/32x32.png",
"icons/128x128.png",
<EMAIL_ADDRESS>"icons/icon.icns",
"icons/icon.ico"
],
"identifier": "com.tauri.dev",
"longDescription": "",
"macOS": {
"entitlements": null,
"exceptionDomain": "",
"frameworks": [],
"providerShortName": null,
"signingIdentity": null
},
"resources": [],
"shortDescription": "",
"targets": "all",
"windows": {
"certificateThumbprint": null,
"digestAlgorithm": "sha256",
"timestampUrl": ""
}
},
"security": {
"csp": null
},
"updater": {
"active": false
},
"windows": [
{
"fullscreen": false,
"height": 600,
"resizable": true,
"title": "tauri-app",
"width": 800
}
]
}
}

that's CORS issue, we can't do anything about it, you can workaround this by using our rust http client, see https://tauri.app/v1/api/js/http


General improvements

Minor improvements to some icons, buttons and backgrounds.

Removed trailing spaces and fixed collapsible content.
Before

After

Will update extension on Firefox, great work!


Add the OpenLayers logo and the OSGeo-project badge to README

This PR suggests to add two images to our README:

our very own logo (copied from the openlayers.github.io) repository
the "OSGeo project" badge (copied from the OSGeo SVN)

Fixes #4760

ugh ...

blech.

Is that screenshot from a checkout or from the 'github-view-file', @tschaub?

Ok got it. Will update.

I have opened a PR for updating the openlayers website here: openlayers/openlayers.github.io#57
If people agree to merge that one, the src-attributes vcan be changed to link to the resources on the website.


[BUG]can not login

Describe the bug
can not login
region:china
LOG:
Two-step authentication required.
Please enter validation code
(string) --> 933302
Traceback (most recent call last):
File "/app/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 715, in urlopen
httplib_response = self._make_request(
File "/app/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 404, in _make_request
self._validate_conn(conn)
File "/app/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1058, in validate_conn
conn.connect()
File "/app/venv/lib/python3.10/site-packages/urllib3/connection.py", line 419, in connect
self.sock = ssl_wrap_socket(
File "/app/venv/lib/python3.10/site-packages/urllib3/util/ssl.py", line 449, in ssl_wrap_socket
ssl_sock = ssl_wrap_socket_impl(
File "/app/venv/lib/python3.10/site-packages/urllib3/util/ssl.py", line 493, in _ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/local/lib/python3.10/ssl.py", line 513, in wrap_socket
return self.sslsocket_class._create(
File "/usr/local/lib/python3.10/ssl.py", line 1104, in _create
self.do_handshake()
File "/usr/local/lib/python3.10/ssl.py", line 1375, in do_handshake
self._sslobj.do_handshake()
ssl.SSLEOFError: [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1007)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/venv/lib/python3.10/site-packages/requests/adapters.py", line 489, in send
resp = conn.urlopen(
File "/app/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 799, in urlopen
retries = retries.increment(
File "/app/venv/lib/python3.10/site-packages/urllib3/util/retry.py", line 592, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='p219-fmipweb.icloud.com.cn', port=443): Max retries exceeded with url: /fmipservice/client/web/refreshClient (Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1007)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/venv/bin//icloud", line 8, in
sys.exit(main())
File "/app/venv/lib/python3.10/site-packages/icloudpy/cmdline.py", line 296, in main
for dev in api.devices:
File "/app/venv/lib/python3.10/site-packages/icloudpy/base.py", line 554, in devices
return FindMyiPhoneServiceManager(
File "/app/venv/lib/python3.10/site-packages/icloudpy/services/findmyiphone.py", line 28, in init
self.refresh_client()
File "/app/venv/lib/python3.10/site-packages/icloudpy/services/findmyiphone.py", line 36, in refresh_client
req = self.session.post(
File "/app/venv/lib/python3.10/site-packages/requests/sessions.py", line 635, in post
return self.request("POST", url, data=data, json=json, **kwargs)
File "/app/venv/lib/python3.10/site-packages/icloudpy/base.py", line 79, in request
response = super().request(method, url, **kwargs)
File "/app/venv/lib/python3.10/site-packages/requests/sessions.py", line 587, in request
resp = self.send(prep, **send_kwargs)
File "/app/venv/lib/python3.10/site-packages/requests/sessions.py", line 701, in send
r = adapter.send(request, **kwargs)
File "/app/venv/lib/python3.10/site-packages/requests/adapters.py", line 563, in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='p219-fmipweb.icloud.com.cn', port=443): Max retries exceeded with url: /fmipservice/client/web/refreshClient (Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1007)')))

Seems like server-side error. The app retried few times. Is it still happening?


Add encode_url function and test, fix a typo and update README.md

@snull Thank you for submitting the PR. Could you please provide a brief description of the PR's purpose? Thanks.

First of all thanks for the library.
The main purpose of this PR is adding the ability of encoding urls(percent-encoding); decoding was already there and i thought adding this function would be helpful(specialy in cases that non-ASCII characters would be a problem)

Would it be possible to split this into two separate Pull Requests? One could focus exclusively on the typo fixes, while the other addresses the API changes. This would allow for more targeted discussion on each set of changes. What are your thoughts?

Sure, I can do that if you want to, but it was just a really minor typo (an extra h letter in "characters" in the comment section of the decode_url function)
now thinking, it wasn't even worth mentioning XD.

I suggest that we isolate different changes in separate pull requests for better visibility and discussion. It would be helpful to create two separate pull requests: one for the changes made to fix the typo and white space issues, and another for the new functionality added to the package's API. This will ensure that each change is reviewed and discussed separately, leading to a more organized and effective review process.


Add BCMS

Name
Link

BCMS
https://github.com/bcms/cms

BCMS is an API-base content management system. It's open-source and self-hostable. Built with Vue and Tailwind.

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

Inside BCMS, things are pretty atypical. Far from straightforward and usual Tailwind CSS stuff :D

Agreed. Let's remove it, I have some time tonight.

I'm in the stage of submitting the PR now.


⚠ Guya.moe Proxied has degraded performance

In 7433803, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 12959 ms

Resolved: Guya.moe Proxied performance has improved in d4b17de after 22 minutes.


Open pixel art gd

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

Updated Us


Update generate-tarball.go to include abfs ufs

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.5 please.


ball doesnt work in iOS 8

First off, thanks for these great CSS spinner animations! I'm using .ball on a site and I noticed it doesn't work in iOS 8.2 (not sure about other versions). I tried quite a bit of editing the resulting CSS to see if I could narrow down what the issue is, but I couldn't get it to work.
Here are some screenshots of what it looks like. Most of the time nothing is visible, but at the top of the ball-highlight animation, that part is visible for part of its path.

All the other animations worked in iOS, so at this point I'm really just curious as to why this one doesn't work? Can anyone educate me as to what this animation is doing differently than the others?

On accident I found that adding transform: translate3d(0, 0, 0); to the parent containing the .ball spinner will make the animation work on iOS 8.
Here's the code I tested that made it work on iOS 8:
<!doctype html>

    <link rel="stylesheet" href="css/spinners.css">

Maybe there could be a note added to the ball example page about this?

The reason this fix works could be because 3D CSS transforms use hardware acceleration, whereas 2D ones don't. This could be triggered by transform: translateZ(0); as well as the translate3d(0, 0, 0); you used.
Not sure why iOS 8 doesn't render the non-3D version in the first place, but this feels like the only explanation for the difference that I can think of.


test: finished cypress tests for info page - incl fixes

Issue
https://gravitee.atlassian.net/browse/APIM-2075
Description
Info page tests for APIs in APIM.
Splitting out my General and Plan commits, with updated code and faker details.
This is final PR (finished test). Including conflict resolve and lint fixes.
Tests for Danger Zone to be continued at a later date when I understand full consequence and can fulfil end-to-end test.
Additional context

📚  View the storybook of this branch here

My tests are passing (ui-api-info.spec.ts) so imo this is ready to be merged.


For consistency: add-migration after applying validation rules

Copy from @shadinamrouti #10429 since this is updated first.
Mainly, the following two attributes affect the schema:

[Required] will alter the relevant column and make it not null
[StringLength(60)] will alter the type of the column and make it nvarchar(60)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 39b6d0f3-9bc7-d091-0d45-9fc1e2e7aac8
Version Independent ID: 20e7eb53-215b-09ab-205d-d20177221278
Content: Add validation to an ASP.NET Core Razor Page
Content Source: aspnetcore/tutorials/razor-pages/validation.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@tdykstra  this seems like a good idea. However, you don't get an error if you don't create the migration.

@Rick-Anderson As suggested, it would be good to mention this but I don't think you have to write detailed instructions for creating and applying a migration.  Migrations is covered more thoroughly in the two EF series.


Customising aws_cognito_user_pools annotation

Which Category is your question related to?
API
Amplify CLI Version
4.11.0
Provide additional details e.g. code snippets
Given
type Mutation {
  createSomething(input: AWSJSON): Something @function(name: "createSomething-${env}")
}

How can I scope this custom mutation to permit only certain cognito groups? Does the @aws_cognito_user_pools annotation take any arguments? There doesn't appear to be any docs on it.

@steveparkerSG You can probably use the @auth directive and scope it to groups. You can read more here - https://aws-amplify.github.io/docs/cli-toolchain/graphql#auth

@steveparkerSG Can you try it with the lates version this should be working now.

@steveparkerSG Let us know if you're still stuck on this. As @ammarkarachi mentioned above - this should be fixed in the latest version of our CLI.


[testing][hexagon] Better subproc errors

When a subprocess completes with a non-zero exit code, include
its stdout and stderr text in the Python exception's error message.
cc @mehrdadh

In Python 3.6, subprocess.run does not have capture_output parameter.  It was added in Python 3.7.

https://github.com/apache/tvm/pull/11985


Consider using mint in the place of ImVec2, etc

I agree with https://github.com/Gekkio/imgui-rs/pull/61#issuecomment-313841337 that it doesn't make sense in all usages of ImVec to have general math operations implemented, but we should consider using mint ("math interoperability standard types").
This would make it much easier to use (and leverage the math operations from) libraries like euclid, cgmath, nalgebra, etc with imgui-rs, as they all implement conversions to mint types.
let window_size = euclid::TypedSize2D::new(800.0, 600.0);
let extra = euclid::TypedSize2D::new(50.0, 50.0);

// pub fn size(mut self, size: mint::Vector2<f32>, condition: Condition) -> ...
Window::new(im_str!("Hello world"))
    .size((window_size + extra).into(), Condition::Once)
    .build(&ui, || {});

0.1 abolishes ImVec2 and ImVec4 from safe APIs and simple arrays are used instead ([f32; 2], [f32; 4]). This should make things easier in general, and I imagine libraries usually provide conversions to/from these kind of arrays if you want to do more complicated stuff.

Sounds good to me, it looks like at least euclid, cgmath, nalgebra, and gfx support impl Into<[f32; ...]> for ... most of their types.
There may still be an argument to use mint still to have a distinction between a [f32; 2] representing a "point" and a [f32; 2] representing a "vector", etc, but feel free to close this.

Closing since Gekkio's resolution works for me!


WIP: Add nimbus

Implements #11

Currently building successfully for shuffle, but crashes almost immediately with a difference detected.

Currently building successfully for shuffle, but crashes almost immediately with a difference detected.

Runtime error due to incorrect config. Fixed up other things, but this error was resolved by using the mainnet config via NIMFLAGS= -d:const_preset=mainnet

Accidentally closed


Schema missing simpleLicensingInfo_AnyLicenseInfo class

When generated against the latest model, the schema generated is missing the $ref/simplelicensing_AnyLicenseInfo definition.  It is also missing from the anyClass list.
Was this intentional?
Note that the $ref/simplelicensing_AnyLicenseInfo_derived is present.

The current generated schema can be found at: https://github.com/spdx/spdx-spec/blob/gh-pages/v3.0.1-draft/model/schema.json.
I noticed that there were a lot of referenced to the undefined AnyLicenseInfo, so I suspect this may be an issue.

Ah, ya. That's a bug in the JSON schema validation; it's not skipping abstract classes


fix broken multi-head attention cell

Description
Otherwise it will throw an error "AttributeError: 'MultiHeadAttentionCell' object has no attribute '_query_units'" while training transformer.
@eric-haibin-lin
Checklist
Essentials

[ ] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Thanks for catching this @ZiyueHuang. However, I don't see why you got the AttributeError. The line setattr(self, '_{}_units'.format(name), unit) creates the self._query_units attribute. Obviously  self._query_units then shouldn't be used as key and value units, but that's a separate issue (fixed by this PR).

Job PR-878/2 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-878/2/index.html

@ZiyueHuang I believe you are running python3.5. python3.5 is unsupported by GluonNLP.
Either way, thankfully due to python3.5 you discovered this bug.


Visual Studio Test task uses duplicate test adapters by default

The Visual Studio Test task uses the source root folder as the /TestAdapterPath by default. With xUnit, this makes vstest.console.exe discover multiple copies of the xunit.runner.visualstudio.testadapter.dll, one for each project where the package is referenced, plus one for each instance of the nuget package. Each instance of the test adapter runs all tests in all projects.

The default behavior is designed to make sure we help users get their tests working by finding any adapters that exist. To override the default search, you can specify a path in the "Path to Test Adapters" field. Thanks!

The default behavior is executing four thousand tests in a solution that has only four hundred. Test execution is unstable and ignores parallelization constraints. It took us weeks to notice and several days to understand the problem before we could identify the test adapter path as the culprit. AND WE HAVE TWO PEOPLE WHO USED TO WORK ON VSTEST ON OUR TEAM. This is a very bad user experience. Your competitor, AppVeyor just works, correctly, try it to see what the experience is supposed to be.


[Pulsar-Netty] Add Netty Connector Support for Tcp Messages

Motivation
Netty is NIO client server framework by supporting asynchronous event-driven communication and custom protocol implementation.
Ref: https://netty.io/
This PR proposes Pulsar-Netty Connector by helping the Tcp clients. It enables an embedded Tcp Server to listen incoming Tcp messages and writes them to Pulsar by behaving as Pulsar Source.
There are also other potential use-cases for this connector as follows:

Tcp Client (Pulsar Sink): It can listen Pulsar messages and can write to remote Tcp Server.
Http Server and Client (Pulsar Source and Sink)
Udp Server and Client (Pulsar Source and Sink)
Also Pulsar Functions can be applied to incoming Tcp, Http and Udp messages through related topics.

Modifications
1- PulsarTcpServer: Initializes an embedded Tcp Server to listen incoming Tcp Requests
2- PulsarTcpServerHandler: Inbound Channel Handler to handle incoming Tcp Requests
3- PulsarChannelInitializer: Pulsar Channel Initializer to support different types of decoders and handlers
4- PulsarSerializer: Pulsar Generic Serializer Interface to serialize generic typed objects to byte-array
5- PulsarStringSerializer: String Implementation of Generic Serializer Interface as user-ready
6- PulsarUtils: Initializes and services singleton Pulsar Producer
7- UT Coverage
8- Examples: Covers both String and Pojo based message examples
9- README.md

oh I see you mentioned following in the description:

Also Pulsar Functions can be applied to incoming Tcp, Http and Udp messages through related topics.

You are thinking something of Tcp, Http like source connectors. I am wondering can this be taking one step further to think about integrating KNative or providing similar capability as KNative.
basically Pulsar core serves the "eventing" part, this Tcp servers + Functions serve as "serving" part?
/cc @merlimat @srkukarni in this conversation.

I'm also unclear as to how this is different from a regular source in our io framework?

@sijie and @srkukarni Firstly, thanks for reviews.
1- Yep, i think about Pulsar both Source and Sink connectors for Tcp, Udp and Http protocols. On the other hand, i was also thinking where these connectors can sit ideally such as:

pulsar-core level (if the user does not use Pulsar Functions and need to work with Tcp, Udp and Http) or
pulsar-io level (if the user needs to use Pulsar functions, this connectors can be moved into pulsar-io by implementing org.apache.pulsar.io.core.PushSource and Sink Interfaces).

So, this is also open question for me and we can make decision.
Sample Use Cases:
https://netty.io/wiki/adopters.html (Netty Use Cases)
https://keyholesoftware.com/2016/05/24/whirlpool-microservices-using-netty-and-kafka/
http://bahir.apache.org/docs/flink/current/flink-streaming-netty/
2- Knative: I think Knative support can be a required feature. As a sample high level Pulsar pipeline on Knative:
Source(Pulsar Event / Other Source Events(Pulsar IO Source)) -> Channel (Pulsar Channel) --Subscription--> Service (Pulsar Functions -> Sink(e.g: Tcp/Udp/Http)))

Native Pulsar Support on Knative Repo can be useful for specially PulsarSource and PulsarChannel (as persistent). On the other hand, Service(Pulsar Function)) layer can be user-driven.
Pulsar Functions/IO Sinks can need to be supported as runnable and deployable (through Docker in order to be managed functions' lifecycle through pods)

Also, Knative Support can be separated PIP

@erenavsarogullari I think that it makes more sense to put them into pulsar-io as sources and sinks. That way we keep the core cleaner/more focused on core messaging and leave the other peripherals to the io.

@srkukarni Thanks for feedback.
Sure, I will be working on current proposal to move pulsar-io.
I think we can close this PR and i can create a new one by linking this if we do not have any concern.

closed this PR as discussed. a separated PR will introduce this feature to pulsar-io


Consider if ModifiedTime/EtagAccess Conditions should be moved to core.

Azure::Storage::ModifiedTimeConditions
Azure::Storage::ETagAccessConditions

Consider move this to Core.

Storage team is OK with either decision. Please close or assign back to Storage team if pushing back.

MatchConditions and RequestConditions added to core

Storage needs to switch to the new types

blocked by https://github.com/Azure/azure-sdk-for-cpp/issues/1608


ERROR: Could not find a version that satisfies the requirement pydud (from versions: none) ERROR: No matching distribution found for pydud

ERROR: Could not find a version that satisfies the requirement pydud (from versions: none)
ERROR: No matching distribution found for pydud
这个How to soive如何解决？

Do a fresh install please, it should want to install pydub as in the install.py.


Login for XSS attack

Hi Guys,
I didn't mean to open an issue for it, however I didn't find any forum and document where I get this information.
Would someone please let me know how to target xss attack for the pages which requires authentication.

Easiest way, use cURL to authenticate, save the cookie into a file. Then in xsser, set the --cookie= to the contents of the cookie file.

Did the approach I mentioned work for you?

Hi I followed the alternate approach provided by Arachni of phamtomjs
driver. and it worked.
Gaurang Shah
Blog: AutomationTesting.co.in http://automationtesting.co.in
Mobile: +91<PHONE_NUMBER>
On Tue, May 19, 2015 at 3:22 AM, Apollo Clark<EMAIL_ADDRESS>wrote:

Did the approach I mentioned work for you?
—
Reply to this email directly or view it on GitHub
https://github.com/gauntlt/gauntlt-demo/issues/7#issuecomment-103224347.

Hi,
the alternate method I used to login in arachni doesn't work with gauntlt,
so now I want to use curl, however I am not sure how to club these two
command.
Can you please provide some guideline. I am doing something like this,
however it's not working.
If I don't include " When I run `curl -ik  --data
'j_username=xxxx&j_password=xxxx'
https://<IP_ADDRESS>/webui/j_spring_security_check -c /tmp/cookie.txt" line
it works fine.
code:
Feature: Look for cross site scripting (xss) using arachni against a URL
Scenario: Using arachni, look for cross site scripting and verify no issues
are found
Given "arachni" is installed
And The default aruba timeout is 600 seconds
When I run curl -ik  --data 'j_username=xxxx&j_password=xxxx' https://<IP_ADDRESS>/webui/j_spring_security_check -c /tmp/cookie.txt
And I launch an "arachni" attack with:
"""
arachni --http-cookie-jar=/tmp/cookie.txt --scope-https-only
--scope-dom-depth-limit=20 --audit-links
--scope-extend-path=/root/gauntlt/paths --report-save-path=test1.afr
https://<IP_ADDRESS>/
"""
Then the output should contain "0 issues were detected."

Failing Scenarios:
cucumber test.attack:3 # Scenario: Using arachni, look for cross site
scripting and verify no issues are found
Gaurang Shah
Blog: AutomationTesting.co.in http://automationtesting.co.in
Mobile: +91<PHONE_NUMBER>
On Mon, May 25, 2015 at 1:29 PM, Gaurang shah<EMAIL_ADDRESS>wrote:

Hi I followed the alternate approach provided by Arachni of phamtomjs
driver. and it worked.
Gaurang Shah
Blog: AutomationTesting.co.in http://automationtesting.co.in
Mobile: +91<PHONE_NUMBER>
On Tue, May 19, 2015 at 3:22 AM, Apollo Clark<EMAIL_ADDRESS>wrote:

Did the approach I mentioned work for you?
—
Reply to this email directly or view it on GitHub
https://github.com/gauntlt/gauntlt-demo/issues/7#issuecomment-103224347
.

I run a simple bash script. The first line does the login to curl, saves the Session cookie into a file, and then passes that session cookie file to any of the remaining tests. I usually save the cookie to "/tmp/cookie.txt," so that it's a static location every other gauntlt run command can access.
Archani does allow you to load a static cookie file:
http://support.arachni-scanner.com/kb/general-use/logging-in-and-maintaining-a-valid-session#from-cookie-jar

Hi apollo,
Thanks for the help, finally figure it out, i was missing quotes when providing login script,  Now the same phantomjs script is working fine.
Closing the issue.


Fix bugs builds

From devel branch run npm run build
It will return some refactoring errors.
In the old implementation:
new Wallet(seed:"string_seed_phrase");
Refactor to:
new Wallet("string_seed_phrase");

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a passionate and results-driven web developer, currently deepening my knowledge in web3 technologies, Cairo, and open-source development through Dojo Coding. My skill set includes expertise in JavaScript, React, HTML, CSS, C# with .NET Entity Framework, and more. I also have experience with tools like Git, GitHub, SQL Server, and Postman. My focus has been on building solid web applications, from task lists to full-fledged CRUD systems, with front-end, back-end, and database integration.
I have already made a contribution to the open-source ecosystem and am excited to continue learning and collaborating on innovative projects
How I plan on tackling this issue
If I need to refactor the Wallet code to accept just a string instead of an object with a seed property, I'd start by updating the constructor to take the seed phrase directly as an argument. Then, I'd go through the code to update where the old constructor was used. After that, I'd run the build to check for any remaining errors and fix them if needed.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I'm full stack developer with experience in languages like PHP, JS, TS and Frameworks like React, Laravel. Also, I made several courses in Alchemy University to be prepared to challenges in web3 like this one. So I hope to move forward in this application.
How I plan on tackling this issue
Well, run npm run build, see the errors and then fix them with new implementations as shown in the latest version of the documentation.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
With over four years of experience in blockchain development, I have worked across multiple blockchain ecosystems. My expertise spans the entire development lifecycle—from project conceptualization and smart contract design to managing on-chain interactions, seamless protocol integration, and implementing strong security practices.
This enables me to handle both on-chain and off-chain infrastructure, ensuring the development of reliable, scalable blockchain applications.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
3+ years Full Stack developer
How I plan on tackling this issue
I will refactor all instances of new Wallet(seed: "string_seed_phrase") to new Wallet("string_seed_phrase") and update the Wallet class constructor to accept a string argument. Then, I will run npm run build to ensure the issue is resolved.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
This demand is super simple, I can start with it.