Error creating services and collections

While configuring an OpenTaxii instance and running both commands below,
opentaxii-create-collections -c collections.yml
opentaxii-create-services -c services.yml
I get this error message:
Traceback (most recent call last):
File "/home/fortinet/venv3/bin/opentaxii-create-services", line 11, in
load_entry_point('opentaxii==0.1.9a1', 'console_scripts', 'opentaxii-create-services')()
File "/home/fortinet/venv3/lib/python3.5/site-packages/opentaxii-0.1.9a1-py3.5.egg/opentaxii/cli/persistence.py", line 23, in create_services
services_config = anyconfig.load(args.config, forced_type="yaml")
File "/home/fortinet/venv3/lib/python3.5/site-packages/anyconfig/api.py", line 377, in load
**options)
File "/home/fortinet/venv3/lib/python3.5/site-packages/anyconfig/api.py", line 262, in single_load
cnf = psr.load(path_or_stream, **options)
File "/home/fortinet/venv3/lib/python3.5/site-packages/anyconfig/backend/base.py", line 290, in load
cnf = self.load_from_path(path_or_stream, container, **options)
File "/home/fortinet/venv3/lib/python3.5/site-packages/anyconfig/backend/base.py", line 424, in load_from_path
return self.load_from_stream(self.ropen(filepath), container, **kwargs)
File "/home/fortinet/venv3/lib/python3.5/site-packages/anyconfig/backend/base.py", line 75, in wrapper
return func(*args[1:], **kwargs)
File "/home/fortinet/venv3/lib/python3.5/site-packages/anyconfig/backend/yaml.py", line 167, in _yml_load
return container() if ret is None else container(ret)
ValueError: dictionary update sequence element #0 has length 8; 2 is required
Any hint is more than welcome.
Thanks in advance.
\Max

Has anyone successfully deployed services and collections as described in the configuration guide? I am stuck with the error I posted earlier. Many thanks in advance for any hint.

Hi @maxymax68, it looks like anyconfig is failing in loading the configuration. I think that the issue is the version of anyconfig. So please try to stick to version '0.5.0' of this module.  Can you try and see if this works for you?

@maxymax68 yes, the issue is with latest version of anyconfig. Please downgrade to 0.5.0 for now. I'm working on removing anyconfig dependency in the next release

I just changed requirements.txt 257df639429da41819313e2012bf3f2c486948e7, so it points to exact version for anyconfig

It worked after I downgraded anyconfig module to 0.5.0
Many thanks,

great! good to hear @maxymax68

reopening this, until anyconfig is not removed

I am encountering a similar error to the original post, as referenced in issue #70
2017-05-11T06:07:12.235001Z [opentaxii.utils] info: api.initialized {timestamp=2017-05-11T06:07:12.235001Z, logger=opentaxii.utils, api=opentaxii.persistence.sqldb.SQLDatabaseAPI, event=api.initialized, level=info}
2017-05-11T06:07:12.238918Z [opentaxii.utils] info: api.initialized {timestamp=2017-05-11T06:07:12.238918Z, logger=opentaxii.utils, api=opentaxii.auth.sqldb.SQLDatabaseAPI, event=api.initialized, level=info}
2017-05-11T06:07:12.239042Z [opentaxii.server] info: opentaxii.server_configured {timestamp=2017-05-11T06:07:12.239042Z, logger=opentaxii.server, event=opentaxii.server_configured, level=info}
Loading: services.yml
Traceback (most recent call last):
  File "/usr/local/bin/opentaxii-create-services", line 11, in <module>
    sys.exit(create_services())
  File "/usr/local/lib/python2.7/dist-packages/opentaxii/cli/persistence.py", line 28, in create_services
    services_config)
  File "/usr/local/lib/python2.7/dist-packages/opentaxii/persistence/manager.py", line 62, in create_services_from_object
    service = blob_to_service_entity(blob)
  File "/usr/local/lib/python2.7/dist-packages/opentaxii/taxii/converters.py", line 332, in blob_to_service_entity
    properties = dict(blob)
ValueError: dictionary update sequence element #0 has length 1; 2 is required

Originally was using version 0.9.1 of anyconfig, after reading the above, I have downgraded to 0.50 as seen here
$ pip show anyconfig
Name: anyconfig
Version: 0.5.0
Summary: Generic access to configuration files in some formats
Home-page: https://github.com/ssato/python-anyconfig
Author: Satoru SATOH
Author-email<EMAIL_ADDRESS>License: MIT
Location: /usr/local/lib/python2.7/dist-packages
Requires:

However, re-running opentaxii-create-services results in the same error.
Any pointers in the right direction?
Thank you

@tmehdi94 do you have lists or a dict as a top element in services.yaml?

@traut ,  this error occurs with the example services file provided from: https://raw.githubusercontent.com/eclecticiq/OpenTAXII/master/examples/services.yml

@tmehdi94 that example expects you to have provided patch in place and non-downgraded anyconfig. So you either downgrade anyconfig but use old example, or use new example and latest master code

@traut Thank you, that has resolved the issue. I was using pip install opentaxii which appears to not have the latest changes, cloning directly from Github has fixed the problem.

@tmehdi94 awesome. If you use pip install opentaxii, you install latest stable version, not the master


[Bug]Create Data Group fail

What happened

What you expected to happen

How to reproduce
Follow the above operation
Environment
Kubernetes 1.10+
Helm 3.0+
InLong version
1.2.0
InLong Component
InLong Dashboard
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@xingzhoutan please use the master branch code and try again, thanks.

the image with the latest tag is the related to the master branch.


create a starting-workflow.yml

Like with the original template, want to have a starting-workflow.yml that can clean up some template files that aren't necessary for the end product (example being used in this PR for the original template)

PR #86 addressed this


[Controller Figure] Fix text alignment

Fix text alignment in "benchmarking engine" and margins
@Assigned to @ekapassa

figure updated,
@gmixoulis I will send it to you. Please close this issue once the new figure is uploaded


New Relic backend: Added support for throttling ("Retry-After" header)

Description
Under heavy loads using New Relic backend I've observed GoStatsD is not handling throttling correctly. In cases when New Relic reply with StatusCode = 429, we should read a header, sleep (potentially) and then retry.
New Relic documentation
API returns a 429 response for the remainder of the minute. The response will include a Retry-After header indicating how long to wait in seconds before resubmitting or sending new data.
Rationale
With this PR the code will try to use "Retry-After" (if available) header to sleep instead of backoff algorithm. In case of invalid or missing header it will fallback to backoff algorithm.
This change is intended to be backward-compatible.
Changes

[New Relic backend] added support to handle rate-limiting from the API by handling Retry-After response's header.
[New Relic backend] added new Error for rate-limit case.
[New Relic backend] added unit-test for new feature.

@tiedotguy, @MovieStoreGuy please can I get a review on this one?
Thanks in advance!

I'll get a release cut shortly.


task-service-example: ping response is not compatible

While building task service example  getting the following error:
.

.

This already seems to be fixed by someone else. I could not reproduce this error. start command -

@Surbhi-sharma1 can you verify

yes ,its working now

fixed with PR #
https://github.com/sourcefuse/loopback4-microservice-catalog/pull/1684


Multiple file writes test timeout

The multiple file writes test times out unless I increase the timeout from 1.5s to 5s:
mocha -r should -R spec -t 5000
or reduce NUM_FILES from 500 to 150
node-storage 0.0.7
Node 9.4
Windows 7
Intel i7-3770 @ 3.4 GHz
Sorry for not having an SSD :-)

Yes, that was definitely a bad assumption :) Sorry about that.


Add ability to specify user_info as an extra parameter when instantiating UserInfoAuth derived classes

Hi, thank you for you great work.
I have a question/feature request.
Currently, there is no straightforward way to pass user_info into a respective UserInfoAuth derived class (eg. CognitoCurrentUser) before the instantinaion and only inheritance will work. So it'll be great to have something like this:
current_user_auth = CognitoCurrentUser(
        region=settings.aws_region,
        userPoolId=settings.userpool_id,
        client_id=settings.app_client_id,
        user_info=settings.user_info_class      <---- here
    )

The current implementation of CognitoCurrentUser doesn't allow to do this.
It will be nice to have something like this:
class CognitoCurrentUser(UserInfoAuth):
    """
    Verify ID token and get user info of AWS Cognito
    """

    user_info = CognitoClaims

    def __init__(
        self,
        region: str,
        userPoolId: str,
        client_id: str,
        *args: Any,
        **kwargs: Any,
    ):
        url = f"https://cognito-idp.{region}.amazonaws.com/{userPoolId}/.well-known/jwks.json"
        jwks = JWKS(url=url)
        user_info = kwargs.get("user_info") or self.user_info           <----- new code
        super().__init__(
            jwks,
            user_info=user_info,   <---- changes
            audience=client_id,
            issuer=f"https://cognito-idp.{region}.amazonaws.com/{userPoolId}",
            extra=CognitoExtraVerifier(
                client_id=client_id,
                issuer=f"https://cognito-idp.{region}.amazonaws.com/{userPoolId}",
                token_use={"id"},
            ),
            *args,
            **kwargs,
        )

or be more explicit and add user_info as a paramter to CognitoCurrentUser __init__ method

Let's close this "issue". Currently, I followed up with the following implementation (using dependecy):
async def get_current_user(
    settings: AppSettings = Depends(get_app_settings),
    http_auth: Optional[HTTPAuthorizationCredentials] = Depends(HTTPBearer(auto_error=False)),
) -> CognitoCurrentUser:
    current_user_auth = CognitoCurrentUser(
        region=settings.aws_region,
        userPoolId=settings.userpool_id,
        client_id=settings.app_client_id,
    )
    # Set custom Cognito claims class with extra attributes
    current_user_auth.user_info = settings.user_info_class
    return await current_user_auth(http_auth)


(PDB-2083) Bump project.clj version for 3.2.0 release

Signed-off-by: Ken Barber<EMAIL_ADDRESS>

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-stable/55/
Test FAILed.

That PR test was cancelled on purpose ^^


xcodebuild.nvim reports a build failure on a successful build

I am working on a project that produces some deprecated API warnings, which the plugin incorrectly reports as errors. I believe the issue is that the warning has the word "error" as part of a method name.
'unarchiveObjectWithData:' is deprecated: first deprecated in macOS 10.14 - Use +unarchivedObjectOfClass:fromData:error: instead [-Wdeprecated-declarations]
The first screenshot shows that the build succeed, while the second shows the failure due to the deprecated warnings.

@notlus could you switch to fix/issue-92 branch and check if it resolves your issue? (#93)

Yes, that resolves my issue. Thanks!


Update "uploadPerform" to set "Initial revision" if it applies

This commit ensures that the first revision of new item will always be
associated with the comment "Initial revision". This applies to new files
uploaded using either the web apis or the web interface.
The behavior is now consistent with the initial message set in
UploadComponent::createLinkItem() and ApisystemComponent::uploadGeneratetoken()

Cc: @cpatrick @jamiesnape

To illustrate, when uploading a new file:

Before this change:

After this change:

I do not think having a description "Initial revision" really adds anything. Revision 1 is obviously the initial revision. Is there a compelling reason why this is required?

Consistency with what was done in UploadComponent::createLinkItem() and ApisystemComponent::uploadGeneratetoken().

I think remove it.


Add MaskImageNode

Adds a Mask Node
This node behaves weirdly when using the 'Input' node as a Mask, this might possibly be maybe partially "fixed" when merging #1065

Blocked on the crash (relevant diagnostics included in the committed code) which we probably need @TrueDoctor to help with. Unless @isiko you are able to figure out the reason why mask_pixel.r() can go negative or even to NaN when a node like Levels is used upstream of the mask's Stencil input.

Not blocked on the crash because that is caused by the levels node


string.new.spin: StripChr() should return a pointer to the string

Currently it returns the number of matched characters to be stripped found in the source, but it'd be more useful (and consistent with other functions in the library) if it returned a pointer to the string, so it can be used inline in expressions. Currently, it reads as more of a standalone 'statement.'

Left(), Right(), Mid() (others?) should be rewritten to operate the same way


Disable a part of the Syntax unit tests under no-asserts.

This is a quick fix to get the no-asserts bot back to passing; there may be a better way to clean up the code later.

@swift-ci Please smoke test and merge

Hm. @shahmishal, the "and merge" part of this seems to have failed. Leaving for you to investigate in its broken state.

It looks like it eventually gave up. Merging by hand.


issue-32-add-function-to-update-the-value-for-the-deprecated-status-of-items

Add function to api.py that allows requests to be sent to the 'updateState' REST API function. Note that items for which we wish to update the deprecation status are specified as an array of objects with agency id/identifier/version. This allows the function to be used to deprecate sets of items, not just an individual item specified using function arguments.

@jli755 You'll need to approve this PR before it gets merged, I can't approve my own PRs. Thanks!


PR for issue #585 Add IAM Read only permissions to SAM Policy templates

Issue #, if available: Issue ID 585
I am creating a serverless app that will validate whether a specified AccessKey is valid or not and if valid , it will return some metadata like accesskeycreatedate ,lastuseddate and so on.
This requires the following permissions -
{
"Action":[
"iam:ListAccessKeys",
"iam:GetAccessKeyLastUsed",
"iam:ListUsers"
],
"Effect":"Allow",
"Resource":"*"
}
Currently there is no Policy template is SAM which provides IAM Readonly permissions .
Description of changes:
Added the following permissions as part of a new policy in all required files
{
"Sid":"IAMPermissions",
"Action":[
"iam:ListAccessKeys",
"iam:GetAccessKeyLastUsed",
"iam:ListUsers"
],
"Effect":"Allow",
"Resource":"*"
}
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thank you for your contribution! We are reviewing this Policy Template submission and will get back to you soon!

Could you please scope the Resource appropriately? See documentation https://docs.aws.amazon.com/IAM/latest/UserGuide/access_permissions-required.html

Additional review note: Access Key Last Used may not be available in China regions, how did we want to address this?

Closing due to lack of response.


Switch to Lyo 6.0.0-SNAPSHOT or 5.1.2

https://github.com/OSLC/lyo-samples/actions/runs/5879335669/job/15943162077

done for client samples; LyoD adaptors need regen


Update Exchange-Teams-interact.md

Updated table:

Change Retention support to Yes with supplemental information item 3 for on dedicated and on premise exchange.
Added supplemental information note 4 for voicemail to provide more context. Voicemail is supported in Teams regardless of mailbox location, but voicemail messages will not be available in Teams for on premise mailbox.
Removed (hybrid configuration) for requirement for Oauth for Exchange on-premise. Oauth MUST be configured so that exchange on premise allow Outh authenticated connection to EWS from Teams Middle Tier Service. HOWEVER, Houston we have a problem, the Exchange article we are referencing has the WRONG authserver configuration. Teams service will present a token from Azure AD (evoSTS) and that needs to be configured in Exchange on premise for authentication to be successful. Without this, connectivity to mailboxes to access user data will fail. I put in a github request to have that article updated but not sure if that will get processed. If you could put in a word to that team, that would be awesome.

I need to make a correction to the above. What we need to emphatically state is that Exchange Hybrid is a requirement. Helped an engineer on a case and found that we need the exchange web service URL's in the Service Principal names in online as well as the on premise configured with the Oauth Server. The Exchange Hybrid Wizard will handle this, but we also need to state that we require Exchange 2013 latest CU-1 and customer should re-run the Hybrid Wizard if they had an older Exchange 2013 deployment.
So on the 3rd update I made, we actually need to change the whole reference to Oauth and instead just state what I said above. We can skip the reference out to the outdated Exchange Oauth article.


Adding capability to easily process velocity and flow data based on adjusted year

@mountaindboz The CSV data files for velocity and flow did not change with this fix. The RDS files did change, but I'm guessing that must just be some metadata stored in those files unrelated to the actual data.

Closing this pull request because we decided to continue using traditional water years for the inflow/outflow and velocity analyses.


I cannot run rnv command

Describe the bug
I had a problem when I try to run rnv command.

That sounds like node can't build gyp. I think you need to install Python.
Please follow the requirements for windows from https://github.com/nodejs/node-gyp. You do not need to install node-gyp, you only need the requirements. Then run npm i again

I installed Python v2.7 and windows-build-tools with npm install --global --production windows-build-tools and I have the same problem. I also have installed Visual Studio Community 2019 with ASP.NET.

@jesusbarrientos latest releases of node tend to have issues with node-gyp. not sure what is your exact node version but it sounds like v12.x.x
try to downgrade it to v10.19.0, clean project and run it again

Thanks. https://stackoverflow.com/a/56285684/470749 mentioned something similar. This worked for me:
node --version
v12.16.1
sudo apt-get update
sudo apt-get install -y python3-pip build-essential libssl-dev libffi-dev python3-dev python3-venv python-django
nvm --version
0.35.3
nvm install 10
npm install rnv -g

I get the same problem , when I try to run rnv new I get an error... What can I do ?

This issue seems to have a fix provided and also is not related to rnv itself, therefore closing. Feel free to reopen on create a new ticket if similar issue reoccurs


Add Option to Break Harvest Block

Hi there! I hope it's fine to request a feature here.
I would like to have an option to have the plugin break the harvest block and drop the items to the ground in order to collect them instead of putting them straight into the inventory. It is very convenient the way the plugin works right now but it is feeling far less rewarding.
I don't think this option would defeat the purpose of the plugin since automatic replanting itself and being able to hold down right click is still a breeze for harvesting large fields. It should probably not be the default configuration though as most people probably like the current behavior best.

Hi there! I think I can fulfill your request 👌

Thank you so much for adding the option I've requested! Also it's amazing how quickly you acted on it. Thank you.
I've had a chance to test it out and I think it adds exactly what I've been missing in the original implementation. I have a few other suggestions to further improve upon it though. I hope it's fine to add my thoughts here:
Add Block Breaking Effect
I think it needs a bit more work to appear just like vanilla's block breaking. Firstly the particle animation is missing entirely and secondly the configured sound from the configuration still plays. Instead the block's breaking sound should play.
In order to help a bit with this change and not just ask I've researched a bit and I think this fuction adds at least the particles, maybe even the correct sound.
https://hub.spigotmc.org/javadocs/spigot/org/bukkit/World.html#playEffect(org.bukkit.Location,org.bukkit.Effect,T)
https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Effect.html#STEP_SOUND
The block's Material can be accessed by calling getType on the Block and the Effect should probably be STEP_SOUND judging by the Enum's descriptions. The effect should be called on the world to make it visible to all players. This would override the custom sound which then probably only applies to dispensers. But since this might have the potential to cause some lag it would be best to make it configurable. Maybe by default the effect should be played only for the player themselves and optionally it's called on the world?
These are just some thoughts and possible implementation ideas. I've never written a server plugin before but seeing your commits helped me understand it all a bit better. I hope this is a help. Thank you again for your work!


Network settings option

Can you split the options so I can use a daemon running remotely but with a local wallet please?

This issue has been resolved by f1cd058a9e3a1fe786200ef164703e0b49cc7aba.


update the plotting part

I updated the plotting codes since the previous legend didn't show the full name of ssp scenarios.

Perfect. Thank you @Weiwei047


Add description to Lightning-Fast Big Data Analysis. Advanced Analytics with Spark.

Hello @sryza @srowen ! hope you are both doing ok. Would one of you care about writing a small description about your book for awesome-spark ? Thanks ! :)

If you just need a description, I think it's reasonable to use the text at http://shop.oreilly.com/product/0636920035091.do or https://smile.amazon.com/Advanced-Analytics-Spark-Patterns-Learning/dp/1491912766


Decimal resolution of points when editing results: Saving not possible

Currently, points are awarded in battles and rounded to the first decimal point. When editing a result which such partial points, it can however not be saved again, as the mask demands an integer value for points.

fixed in next release


Order manage referrals by submitted_at desc

https://trello.com/c/ln9qVxgv/1234-manage-referral-list-should-be-newest-first

 Manage - referral list should be newest first


Update README.md for vscode extension

Searching for "PullRequestQuantifier" found no results so I had to fine-tune my search.
Including the command-line installation explicitly and the extension ID will improve the discoverability  of this vscode extension

Thanks for the doc improvement.


Response time for NextJS version seems too high

Description
I'm working with @helios2003 in https://github.com/asyncapi/studio/issues/224. In particular, I'm its mentor through GSoC2024.
As part of such project, we evaluated the possibility to run the AsyncAPI Parser-JS and parse AsyncaPI documents loaded via the base64 query param.
@helios2003 made a test measuring response time with and without the addition of the parsing (which would made the page from being statical to ssr). Our surprise came when we realized the NextJS version hosted in https://github.com/asyncapi/studio/issues/224 took ~4 seconds to just serve the HTML for the Studio page (without even loading any doc on it!), just plain /.
Today I decided to run another test, and confirmed the findings. However, a weird caching mechanism is happening.
Let me share with you 3 consecutive requests I made and the results:

Request #
Cache-Status
Cache-Status meaning
Seconds total

1st
[Next.js; hit, Netlify Edge; fwd=miss]
Missed Cache at Netlify level, Hit Cache of NextJS
4.072090

2nd
[Netlify Edge; hit]
Hi Cache at Netlify level, meaning response is served from Netlify edge directly
0.123647

3rd
[Next.js; hit, Netlify Edge; fwd=miss]
Missed Cache at Netlify level, Hit Cache of NextJS
0.572575

My assumption and understanding is that, for some reason:

During the first request there is stuff being rendered at server level dynamically (runtime) instead of something precompiled at build time.
The second request does a hit in Netlify Edge cache, the reason why it takes an insignificant time to give a response since is not even reaching Studio app.
The third request hits another Netlify edge server which still has no cached content (normal), then the request reaches the NextJS app and, in this case, the content is finally served by the NextJS cache.

The point is that I don't expect the first call to take 4 seconds but just as the third request since a request made to the root page should always give the same response (static). Besides that, no clue why the cache-status header in the 1st request saying the content was served as cached from NextJS.

https://asyncapi-studio-studio-next.vercel.app is built with output: 'standalone'.
Please check if it has the same behavior.
This build includes f5676ec feat: add og tags to studio-next (#1106).

Iteration
Time taken (milliseconds)

1st
569.98

2nd
49.12

3rd
202.69

4th
37.65

5th
160.47

Yes, in your case @aeworxet the time taken is much less for even the first hit. The output: standalone is what makes the difference I guess. Also the URL used is same as mentioned here: https://github.com/asyncapi/studio/issues/224#issuecomment-2160148396

@aeworxet's instance is deployed on Vercel, when I try adding the same optimization he mentioned in Netlify the response time reduces significantly for me as well. Thanks @aeworxet
My instance can be found here: https://studio-helios2002.netlify.app

@aeworxet's instance is deployed on Vercel, when I try adding the same optimization he mentioned in Netlify the response time reduces significantly for me as well. Thanks @aeworxet

That doesn't seem to happen. Those are the times when requesting your site:
---
time_lookup: 0.013921
time_connect: 0.040744
time_appconnect: 0.070180
time_pretransfer: 0.070328
time_redirect: 0.000000
time_starttransfer: 3.804182
———
time_total: 3.831893

The diff in terms of the response between your app and @aeworxet is the fact the second is always cached: "x-vercel-cache":["HIT"]
I guess we should do some local testing first rather than relying on CDN.

Are those the times to load the entire page? By less time I meant to fetch the initial HTML that is server-side rendered and contains the meta tags.

Because these are times I see on my side:

Iteration
Time (milliseconds)

1st
867.38

2nd
105.30

3rd
84.85

4th
84.92

5th
113.89

Are those the times to load the entire page? By less time I meant to fetch the initial HTML that is server-side rendered and contains the meta tags.

What I shared is the time of a curl request made against your site. The time_total is the time of the whole curl execution. the time_starttransfer is the time it passed until the server started serving content.

Because these are times I see on my side:

Aren't you hitting cache?

Because these are times I see on my side:
Iteration	Time (milliseconds)
1st	867.38
2nd	105.30
3rd	84.85
4th	84.92
5th	113.89

These are the times I got for a fresh document itself, so I don't think I am hitting the cache and also the time for the first response is much higher than the next 4.

https://studio-helios2002.netlify.app

What do you mean by first response? The first response after a deployment?

Nope, I mean that I send 5 requests continuously to the site, and the time it takes to obtain the meta-tags for each time is what I am calling a response.

Ok, meta-tags. Interesting. I'm just doing a curl. Not sure what the client you use is doing. Anyway, the issue is still there.
For the record, sharing two responses and their headers. As you can see there is no difference, not even in cache headers.
The first request was made this early morning, the second right after the first:
1st
response_code: 200
headers: {"age":["35139"],
"cache-control":["public,max-age=0,must-revalidate"],
"cache-status":["\"Next.js\"; hit","\"Netlify Edge\"; fwd=miss"],
"content-type":["text/html; charset=utf-8"],
"date":["Fri, 14 Jun 2024 05:09:43 GMT"],
"etag":["\"3wn78und5ueoa\""],
"netlify-vary":["header=x-nextjs-data|x-next-debug-logging|RSC|Next-Router-State-Tree|Next-Router-Prefetch|Accept-Encoding,cookie=__prerender_bypass|__next_preview_data"],
"server":["Netlify"],
"strict-transport-security":["max-age=31536000; includeSubDomains; preload"],
"vary":["RSC,Next-Router-State-Tree,Next-Router-Prefetch,Accept-Encoding"],
"x-content-type-options":["nosniff"],
"x-nextjs-date":["Fri, 14 Jun 2024 05:09:43 GMT"],
"x-nf-request-id":["01J0AJDH1HTFWZK1YF8AAYZKSB"],
"x-powered-by":["Next.js"],
"content-length":["19062"]
}
---
time_lookup: 0.015968
time_connect: 0.045507
time_appconnect: 0.076425
time_pretransfer: 0.076563
time_redirect: 0.000000
time_starttransfer: 3.505065
———
time_total: 3.532842

2nd
response_code: 200
headers: {"age":["35548"],
"cache-control":["public,max-age=0,must-revalidate"],
"cache-status":["\"Next.js\"; hit","\"Netlify Edge\"; fwd=miss"],
"content-type":["text/html; charset=utf-8"],
"date":["Fri, 14 Jun 2024 05:16:34 GMT"],
"etag":["\"3wn78und5ueoa\""],
"netlify-vary":["header=x-nextjs-data|x-next-debug-logging|RSC|Next-Router-State-Tree|Next-Router-Prefetch|Accept-Encoding,cookie=__prerender_bypass|__next_preview_data"],
"server":["Netlify"],
"strict-transport-security":["max-age=31536000; includeSubDomains; preload"],
"vary":["RSC,Next-Router-State-Tree,Next-Router-Prefetch,Accept-Encoding"],
"x-content-type-options":["nosniff"],
"x-nextjs-date":["Fri, 14 Jun 2024 05:16:34 GMT"],
"x-nf-request-id":["01J0AJT4HJ7V04BBH4Z48QQP9J"],
"x-powered-by":["Next.js"],
"content-length":["19062"]
}
---
time_lookup: 0.014502
time_connect: 0.041648
time_appconnect: 0.071193
time_pretransfer: 0.071333
time_redirect: 0.000000
time_starttransfer: 0.530230
———
time_total: 0.558090

Here is the diff:
2c2
< headers: {"age":["35139"],
---
> headers: {"age":["35548"],
6c6
< "date":["Fri, 14 Jun 2024 05:09:43 GMT"],
---
> "date":["Fri, 14 Jun 2024 05:16:34 GMT"],
13,14c13,14
< "x-nextjs-date":["Fri, 14 Jun 2024 05:09:43 GMT"],
< "x-nf-request-id":["01J0AJDH1HTFWZK1YF8AAYZKSB"],
---
> "x-nextjs-date":["Fri, 14 Jun 2024 05:16:34 GMT"],
> "x-nf-request-id":["01J0AJT4HJ7V04BBH4Z48QQP9J"],
19,22c19,22
< time_lookup: 0.015968
< time_connect: 0.045507
< time_appconnect: 0.076425
< time_pretransfer: 0.076563
---
> time_lookup: 0.014502
> time_connect: 0.041648
> time_appconnect: 0.071193
> time_pretransfer: 0.071333
24c24
< time_starttransfer: 3.505065
---
> time_starttransfer: 0.530230
26c26
< time_total: 3.532842
---
> time_total: 0.558090

Even though in my case as well the entire document does need to be fetched this is the script I used for anyone wanting to try it out: https://gist.github.com/helios2003/2fdb65377a8b1580b91464cbc7a1d974

The theory that is gradually becoming more solid in my head is that we are always SSR. And that makes sense, because afaik NextJS is set up by default to SSR (even for static pages), then rely in cache.
Since SSR in Netlify happens in Netlify functions (serverless), the first request requires a function cold start, which takes a lot.
The rest, are either cached by the Edge or we find the serverless function to be warmed up.
Post backing up someho my theory: https://answers.netlify.com/t/slow-initial-load-time-on-ssg-with-nextjs/46384/3

The theory that is gradually becoming more solid in my head is that we are always SSR. And that makes sense, because afaik NextJS is set up by default to SSR (even for static pages), then rely in cache. Since SSR in Netlify happens in Netlify functions (serverless), the first request requires a function cold start, which takes a lot. The rest, are either cached by the Edge or we find the serverless function to be warmed up.
Post backing up someho my theory: https://answers.netlify.com/t/slow-initial-load-time-on-ssg-with-nextjs/46384/3

In order to validate this theory, I believe measuring the time since the request hits NextJS router until it serves the response should tell us the time spent on processing the request. The rest, would be time of spinning up such a serverless function.
Note that my NextJS knowledge is close to zero and I'm  just assuming the SSR happens before hitting NextJS router. If it's not the case, we should test accordingly.

Additionally, can we check if we are using NextJS Runtime at Netlify? Build logs should show something like

@smoya Yes, the NextJS runtime is enabled in https://studio-helios2002.netlify.app/.

A difference that I notice in Netlify's version and Vercel's version is the build cache. The attached image shows the build logs of the Vercel deployment.

I believe Studio maintainers can verify if this cache is being generated on the Netlify deployment. Because from what I observe, Netlify creates a NextJS cache but not a build cache.

@KhudaDad414, can you tell why we aren't caching certain components during the build time itself and following Static Site Generation (SSG).
Also, in the previous comment do you mean that in the first request the page is entirely rendered on the server?
Ref: https://nextjs.org/docs/pages/building-your-application/rendering/static-site-generation
Also is there a build cache being uploaded in the production deployment?

The theory that is gradually becoming more solid in my head is that we are always SSR. And that makes sense, because afaik NextJS is set up by default to SSR (even for static pages), then rely in cache. Since SSR in Netlify happens in Netlify functions (serverless), the first request requires a function cold start, which takes a lot. The rest, are either cached by the Edge or we find the serverless function to be warmed up.
Post backing up someho my theory: https://answers.netlify.com/t/slow-initial-load-time-on-ssg-with-nextjs/46384/3

Hi @smoya, I'm new to the AsynApi community, but I disagree with some of your points here. Netlify Edge had used deno deploy which relies on V8 isolates and V8 isolates have been known for a fast start even when a cold start happens, it's different from what we see in virtual machines. My assumption here is probably related to some CSS package being downloaded during the initial startup, I will try to set the bundle analyzer and see what happens there
Reference:
https://news.ycombinator.com/item?id=31912582
https://www.netlify.com/blog/deep-dive-into-netlify-edge-functions/
https://deno.com/blog/anatomy-isolate-cloud

can you tell why we aren't caching certain components during the build time itself and following Static Site Generation (SSG).

The whole page is statically generated and cached currently. not just some components. we would be able to make the page generation dynamic in the future because we have to generate OpenGraph metadata at some point.
First Scenario: No cache at CDN level (Netlify Edge) and had to cold start the server and get the Next.js cache.

Second Scenario: cache at CDN level (Netlify Edge)

Second Scenario: No cache at CDN(Netlify Edge)  level but cache at Next.js.

@jerensl I don't think the problem is with downloading some css packages. As you can see in the above examples the wait time increases in the Server Processing stage which is before any download begin.
The problems

When we miss the CDN(Netlify Edge) cache, the lambda function(or whatever Netlify uses) needs a cold start, that's why we are getting the 4sec time in the first request. there is nothing we can do here as far as I know. 🤷

CDN(Netlify Edge) cache misses randomly: the default behaviour should work fine. but for some reason, it doesn't.

Based on some tests that I have done on my fork, hosted here we can resolve this issue by having custom cache options in the response header:
  # Netlify CDN should keep the cache for 100 days.
  CDN-Cache-Control: public, max-age=3640000, must-revalidate
  # Other Layers (including browser) shouldn't do any caching.
  Cache-Control: public, max-age=0, must-revalidate

@KhudaDad414
@jerensl I don't think the problem is with downloading some CSS. As you can see in the above examples the wait time increases in the Server Processing stage which is before any download begins.

Yeah, you are right there something related to Server Processing stage

The problems

When we miss the CDN(Netlify Edge) cache, the lambda function(or whatever Netlify uses) needs a cold start, that's why we are getting the 4sec time in the first request. there is nothing we can do here as far as I know. 🤷

But I think we can do something with 4sec coldown. Let me explain, after checking using bundle analyzer, I found monaco-editor have been use both in the client side and nodejs(server side)

And I'm running another test on this website https://studio-helios2002.netlify.app/, and found there are long running task in main thread related to monaco which identical to the cold start in nodejs

And then I'm checking the code where monaco being declare using web worker

Why there are no web worker task running here?

Conclusion

Running the monaco editor using web worker is not working here but what happened it's running on the main thread which block around 4-6 second
This also affected the nodejs on the server side because monaco have been use both in client and server side, I don't know why

After making some contributions on Modelina, I realized they did it so well with monaco-editor, shout out to the maintainers there, they did a great job

Ideally, Monaco Editor should be run in the worker and not block the main thread as in the image above, so the user gets their content first and does not block the render.
One thing I realized between Modelina and Studio is:

Modelina use Pages router (By Default Client Side)
Studio use App Router (By Default Server Side)

Let's check Theo's video here, he explains so well why App Router will mostly get a cold start and offers a solution to that problem https://www.youtube.com/watch?v=zsa9Ey9INEg&t=643s
Solution:

Migrate to Pages router, I think this is the most visible solution I can think of because most of the Monaco Editor we want them to run on the client side and we can isolate them not using global.window from the server

Running the monaco editor using Web worker is not working here but what happened is it's running on the main thread which blocks around 4-6 seconds

main thread of what? client or server? on server the page is static and is only being built once (at build time). if you mean on the client then why the the Next.js version is outperforming https://studio.asyncapi.com/ in every scenario? it should be behind by 4 sec right? since https://studio.asyncapi.com/ is being served without the server overhead.

Ideally, Monaco Editor should be run in the worker and not block the main thread as in the image above, so the user gets their content first and does not block the render.

It does (at least the two workers that are supposed to. , main worker and yaml worker)

Migrate to Pages router, I think this is the most visible solution I can think of because most of the Monaco Editor we want them to run on the client side and we can isolate them not using global.window from the server

can you point out what exact feature do we need from pages directory that isn't accessible in app directory? and how would we isolate them not using global.window from the server? considering the page is static?

@KhudaDad414

main thread of client or server? if you mean on server the page is static and is only being built once (at build time). if you mean on the client then why it always doesn't have that 4 sec waiting time? and is on par with https://studio.asyncapi.com/ which is a normal CRA.

can you point out what feature do we need from pages directory that isn't accessible in app directory? and how would we isolate them not using global.window from the server? considering the page is static?

I think the concept you mention is more related to the Pages router which is an old way of using NextJS without React Server components(RSC), the way you all implemented here is by using the App router which is built on top of React Server Components(RSC) by default. I also see you are using a Client Component, I think there are misconceptions about what it is supposed to do, what I know it's the Client Component will render both the server and client and do some technique called hydration to the Client Side by injecting some functionality, also see here how Dan Abramov explain about RSC in simple way
In my opinion, NextJS App Router and Pages Router are two different types of framework, as the discussion here I think it's not be considered as different types of architecture and on to do list(React Server Components), App Router is more similar to Remix than Create React App.
I also not find any decision around why you came up with the idea to use React Server Components here https://github.com/asyncapi/studio/blob/master/doc/adr/0007-use-nextjs.md
Based on how it works in React Server Components, it's not surprising why we got 4 second cold start, because component render both happened in Client and Server
Consider how huge the changes to use React Server Components, which makes us rethink how we are supposed to deal with server and client at the same time, which also makes some state managers think again about how their supposed to deal with it
https://github.com/pmndrs/zustand/discussions/2200

It does (at least the two workers that are supposed to. , main worker and yaml worker)

If the get fix, it's good then, btw I running test on the website mention above which is https://studio-helios2002.netlify.app/

Thanks for the explanation @jerensl.

I think the concept you mention is more related to the Pages router which is an old way of using NextJS without React Server components(RSC)

by static I meant that the / route is statically rendered and by extension Full Route Cached.

Based on how it works in React Server Components, it's not surprising why we got 4 second cold start, because component render both happened in Client and Server

This would be valid if we had a Dynamically Rendered page. Since the Page is Statically Rendered and is Full Route Cached, the server side components won't render with requests but is rendered at build time and is served to the client as React Server Component Payload.
Are you suggesting that a cold start invalidates cache and the page is generated again?

@KhudaDad414

by static I meant that the / route is statically rendered and by extension Full Route Cached.

'/' route I basically a server component that statically renders by default but it's work very different with client component which need a server rendering

This would be valid if we had a Dynamically Rendered page. Since the Page is Statically Rendered and is Full Route Cached, the server side components won't render with requests but is rendered at build time and is served to the client as React Server Component Payload.

But we still have components/StudioWrapper.tsx  right? because of that the page '/' route which a static rendering before becomes dynamically rendering

Are you suggesting that a cold start invalidates cache and the page is rendered on the server again?

No, but I'm suggesting trying to experiment with partial prerendering but keep in mind it is still an experiment feature, basically it will render statically render without waiting for dynamic rendering
Reference:
https://www.youtube.com/watch?v=MTcPrTIBkpA

But we still have components/StudioWrapper.tsx right? because of that the page '/' route which a static rendering before becomes dynamically rendering

Yes it does. but only at build time. No server side code runs for statically generated routes. doesn't matter if there is a "use client" directive or no.
Tested here
Can you give an example that an pre-rendered as static route renders on server?

@KhudaDad414

Yes it does. but only at build time. No server side code runs for statically generated routes. doesn't matter if there is a "use client" directive or no. Tested here

I think I got it wrong here but sure statically generated will run during build time to generate HTML except for client components during initial load without lazy loading SSR

Can you give an example that a pre-rendered as static route renders on server (other than build time of course)?
Sorry, I don't understand, how does a route with static rendering "becomes" dynamic? can you explain it a bit more?

It can happen under strict rules but not in our case, for example, if we have a cookie or turn no cache on fetch API

Do you know what I'm missing here? Did NextJS statically generate JSX to HTML component, why majority of the website still on JSX and just the header which got only statically generated on built time? Did they mean skipping SSR meaning no Staticly Generated HTML during built time too? Is it the point we use NextJS because they making into the HTML

Do you know what I'm missing here?

Full route cache (Statically generated route, if we can call it that) will only take effect when you are not opting out of it.

why majority of the website still on JSX and just the navbar which got only statically generated on built time?

Well, since we are using Monaco and it can't be rendered on the server, plus the other two components (Navigation and Preview) are dependent on the state has to be generated on the client.
the other two (Sidebar and the toolbar at the top) I am not sure if we can render them on the server. It may be possible.

Did they mean skipping SSR meaning no Staticly Generated HTML during built time too?

It means do not try to load this at the Server side since it relies on the window object and will fail.
Some questions that I completely don't know the answer to and we need to answer to decide how we are going to structure the Application.

what can be rendered on the server and what should render on the client?
How are we going to manage the state, should we keep the current approach?

Which are out of the scope of this issue and needs to be discussed separately.

what can be rendered on the server and what should render on the client?

RSC Client Component is already smart enough to separate what belongs to the client and what is on the server via hydration mechanism. Before RSC we need to use useEffect as side effect for detecting window/browser API but with RSC we don't need that anymore

How are we going to manage the state, should we keep the current approach?

Just so you know, before server components existed, react-query had a solution to managing this complexity of state between server and client as their claim as an asynchronous state.
The implementation of RSC in react-query seems a bit complex and reminds me of why we are moving out from redux in the first place, and they are still figure it out how they will do it in the future https://tanstack.com/query/latest/docs/framework/react/guides/advanced-ssr. They also write a blog about trade-off to make on network waterfall https://tanstack.com/query/latest/docs/framework/react/guides/request-waterfalls. This network waterfall also make why remix is better then NextJS + RSC https://remix.run/blog/react-server-components#obsessed-with-ux
Also, let's talk about network waterfall, seems like it has been a hot topic between NextJS + RSC vs Remix, the way NextJS did it by rewriting the fetch standard on the server. This solution is supposed to fix deduplication of the same fetch request and introduce it as the default caching behavior in NextJS as we have seen now but other frameworks like Remix insist it should not rewrite in the web standard and let the developer control their own caching behavior, this one also led to controversy and made the React Team remove fetch cache from RSC https://github.com/facebook/react/pull/28896, let's see if NextJS will follow it or no https://www.youtube.com/watch?v=AKNH7mXciEM&t=920s.
It's supposed to be a good answer but I'm also don't know yet, because we are at an awkward spot now as web developers.


Adding config options for custom schema type names

-Adding new config option to contain Schema customizations SchemaCustomizations
-Adding property to contain custom schema type names customTypeNames

.. if it only affects the Swift code, I think it's appropriate to keep it as a config option rather than a schema directive.

I do agree with this statement and the proposed struct/JSON changes are looking good. 👍🏻


CI is not working

CI in this repo has stopped working, we need to fix it

we also need to test against newer versions of Kubernetes


Fix export typing

In TypeScript 2.6 the prior typing fails to compile with
export default chalk as Chalk;
               ^^^^^^^^^^^^^^
The expression of an export assignment must be an identifier or qualified name in an ambient context.

Duplicate of #217. Oops.


app:showFullScreenButton error

when add  app:showFullScreenButton="true" at the xml file, "ERROR: attribute showFullScreenButton  not found" occurs.
how can fix it?

https://github.com/PierfrancescoSoffritti/android-youtube-player/releases/tag/11.0.0
Since version 11.0.0, attributes like useWebUi, enableLiveVideoUi, showYouTubeButton etc have been removed, as they don't make sense with web ui as default.

As @TinhHuynh says.
You can replicate the old behaviour by using DefaultPlayerUiController


Is there compatibility with TJAStudio

The execute function in TJAStudio chart editor shows you can launch TJAPlayer with the song currently being edited
and have that song autoupdate for changes when you press f5 without closing the window.
However this feature doesn't work for some reason, it will just launch the player and not open the song.

Support for TJAStudio (external control and plugin support, more accurately) was removed due to lack of use and maintainability issues it was causing in the TJAPlayer3 codebase. It had to go in order to make progress on cleaning other things up.
(DirectSound support, as another example, is next on the chopping block for similar reasons, to be replaced with explicit shared wasapi support (which is what DirectSound actually runs on these days anyway.) Maintainability was sacrificed for so long during TJAPlayer's evolution that things like this are going to have to go from time to time otherwise there will be a day where TJAPlayer3 simply stops working and cannot be resurrected with reasonable effort.)


Create js for bootstrapping TPL configuration

The script should be ran after the deployment script from #178
Then, it should perform the following actions:
Add validator to the jurisdiction
Add attribute to the jurisdiction
Add validator approval to the jurisdiction
Add Zeppelin organization to the validator
Add other organizations in the validator
As with the last script, it should then verify that everything went well, and provide information about the deployment.

Addressed by https://github.com/zeppelinos/zos/pull/186


Logo

Hi guys. I have posted on YT, but here is better. Following my simple logo for your apreciation and use. Need the PNG call me! http://i.imgur.com/E7zwHcM.jpg

we can close it ? nope ?


Missing documentation from man pages

estimate 1

[ ] No page for the ApplicationSampler C++ interface.
[ ] Some high level signals are missing (e.g. CPU_FREQUENCY_MIN_AVAIL) from the geopm_pio.7 man page.

Missing high level documentation was discovered below:
cmcantal@mcfly1:~/Git/geopm/service/docs/source (fix-msr-names)]$ for ff in $(cat ~/high-level-controls); do if ! grep -q $ff geopm_pio.7.rst; then echo "$ff"; fi; done
CPU_FREQUENCY_MIN_AVAIL
CPU_FREQUENCY_STEP
CPU_FREQUENCY_STICKER
CPU_UNCORE_FREQUENCY_MAX_CONTROL
CPU_UNCORE_FREQUENCY_MIN_CONTROL
cmcantal@mcfly1:~/Git/geopm/service/docs/source (fix-msr-names)]$ geopmwrite | grep -v : > ~/high-level-controls
cmcantal@mcfly1:~/Git/geopm/service/docs/source (fix-msr-names)]$ for ff in $(cat ~/high-level-controls); do if ! grep -q $ff geopm_pio.7.rst; then echo "$ff"; fi; done
CPU_UNCORE_FREQUENCY_MAX_CONTROL
CPU_UNCORE_FREQUENCY_MIN_CONTROL

The signals are from the CpuinfoIOGroup, but the controls are published by the MSRIOGroup.


pull request for e2e test at 12/29/2016 18:26:09

:white_check_mark: Validation status: passed
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.


Add script-disabled rule to disable scripts inside html

This rule is useful when you want to restrict users to have any script inside HTML, to prevent XSS attacks.

Coverage increased (+0.01%) to 98.746% when pulling be7997e7f3fb15008f343d1e7e36235bbe6dfbcf on SergeyYukhnevich:script-disabled-rule into 152a114f277645474ca1f70d68a0e01e75f3eb51 on yaniswang:master.

I think that can safely be merged


possibility of defining a repo and a branch for each project individually

Hi,
is it possible to have a way to define a repo for each project ? and a branch to push the files to?

From what I can see inside the application.properties: https://github.com/apache/camel-karavan/blob/main/karavan-web/karavan-app/src/main/resources/application.properties:
karavan.git-repository=http://gitea:3000/karavan/karavan.git
karavan.git-username=karavan
karavan.git-password=karavan
karavan.git-branch=main

you could choose a branch, but all inside same repo. Each project would be a folder inside that repo, but you could eventually have different branches for different environments, for example.

Thanks @arheom
@samar-elsayed you could configure only one repository for Karavan instance.


reaction labels are not showing while using overflow-x to hidden

Hey, can you check this bug where you give overflow property hidden to the parent div  and the labels on the emoji stop showing
https://codesandbox.io/s/sweet-joliot-tzkuw?file=/src/App.js
And also can you show me the files where the styles are, so I can also make a PR

Nice catch.
The PokemonSelector uses the FacebookSelector so you should edit those styles. Here is the FacebookSelector Reaction Bar and the Reaction Bar Emoji.
Thanks!

Nice catch. Thanks for the reproduction on CodeSandbox.
The PokemonSelector uses the FacebookSelector so you should edit those styles. Here is the FacebookSelector Reaction Bar and the Reaction Bar Emoji.
Thanks!

I have made a PR, check it  if that works

Hey @the-wrong-guy,
I checked out the PR, but I do not think it solves your issue while wrapping the PokemonSelector inside a div with overflow: hidden. Just remove overflow: hidden and the labels will work properly.
Why do you need to have overflow hidden? I don't think this is an issue.
Thanks.

If you want, I could make it so you can pass styles to the component, so you could add margin to the top of the component so then you can make sure the labels are not cut off when using overflow hidden.
Would a prop to pass styles be helpful?

If you want, I could make it so you can pass styles to the component, so you could add margin to the top of the component so then you can make sure the labels are not cut off when using overflow hidden.
Would a prop to pass styles be helpful?

Well i am making an animation like on clicking an emoji the selectors will slide in from transform: translateX(100%)   to transform: translateX(0)  and again on clicking it will slide out slide in from transform: translateX()   to transform: translateX(100%)   so i need to hide the selectors that's why i need to use overflowX : hidden
I hope you get my point, maybe you should also add that kind of animation by default, that will be much helpful to the users

Would it be possible for you to create a demo of the problem you are experiencing with the animation? It sounds good but I cannot picture exactly what is happening.

Here it's  https://codesandbox.io/s/sweet-joliot-tzkuw?file=/src/styles.css

This issue is more difficult than I initially thought.

@the-wrong-guy, does this demo solve your problem? I added opacity: 0; and pointer-events: none to the class PokemonSelector_Idle and removed overflowX: hidden from the parent div.
Please let me know if this solves your problem and then I can close the issue.

@the-wrong-guy, does this demo solve your problem? I added opacity: 0; and pointer-events: none to the class PokemonSelector_Idle and removed overflowX: hidden from the parent div.
Please let me know if this solves your problem and then I can close the issue.

Well actually it didn't, you can see this codesandbox, they are overlapping  the button and after that, I can see the Selectors for some secs before fading out, i don't want it to show after the button

Okay, thanks for the code sandbox. I understand better now what your question is. I don't have time to look into this now, but what I would do is use overflowX: hidden on the parent div, and when you click the button to show the Selector, then setTimeout() for 200ms and remove overflowX: hidden once the selector has slid into the location.
I can make a demo once I have time, but that might be in a couple weeks. This is lower priority since this isn't a bug but an issue with your CSS rules.

Okay, thanks for the code sandbox. I understand better now what your question is. I don't have time to look into this now, but what I would do is use overflowX: hidden on the parent div, and when you click the button to show the Selector, then setTimeout() for 200ms and remove overflowX: hidden once the selector has slid into the location.
I can make a demo once I have time, but that might be in a couple weeks. This is lower priority since this isn't a bug but an issue with your CSS rules.
Sure, until I will also try to solve thus

How does this demo look?

Closing due to inactivity. I believe the previous demo solves the issue.


Setting Center Frequency

The meter that I am attempting to capture uses 917.58Mhz. I am able to use rtlamr on my PC set to that frequency and I pick up a number of meters. The addon uses 912.38Mhz as the center frequency and is not picking up any meters.
Can an option be added to the addon configuration to set the center frequency?

Sure seems reasonable. Is that what the value of this option looks like? A float basically? The doc just says this:
-centerfreq=0: center frequency to receive on

Want to properly validate the option so need to know if its used like this:
-centerfreq=912.38

or like this:
-centerfreq=912.38Mhz

I believe it is looking for float + M like:
912.380M or 915M
I believe rtlamr pretty much does nothing with it and just passes it to rtl_tcp.


No signature of method

Hiya,
Bit of a noob here, but I'm receiving the following message when pasting the code when creating "A new Smartapp" within the smarthings ide.
No signature of method: script_app_metadata_4f356889_0d09_44c6_907d_1332e8358580.metadata() is applicable for argument types: (script_app_metadata_4f356889_0d09_44c6_907d_1332e8358580$_run_closure1) values: [script_app_metadata_4f356889_0d09_44c6_907d_1332e8358580$_run_closure1@54bdd45f] Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)
Any suggestions?
Thanks

I had this issue and finally figured it out.  You have to add in the groovy paths for your github areas.

Thanks. Know of any references on how to do this?

I went [here] (https://github.com/apache/groovy) and forked it.  Worked after that.

You will also run into this issue if you tried to add a smart app rather than a device handler. From the instructions:

Within the SmartThings IDE, click on 'My Device Handlers'.
Click the '+ Create New Device Handler' button.

Thanks. Know of any references on how to do this?

Did you figure it out?


feat(dspy): add vector, hybrid and fulltext search support in azure ai search module

Feature Addition: Updating AzureAISearchRM Class
This pull request aims to enhance the functionality of the AzureAISearchRM class by introducing support for additional search capabilities. Specifically, the class is updated to enable Vector Search, Hybrid Search, and Full Text Search with Semantic ReRanker, providing users with more versatile and powerful search options.
Changes Included:

Integration of Vector Search, Hybrid Search, and Full Text Search functionalities.
Implementation of Semantic ReRanker to enhance search results with semantic understanding.
Addition of necessary methods and attributes to support the new features.
Updates to the documentation to reflect the expanded capabilities of the class.

Checks:
Pre-Commit checks are passing (locally and remotely)
Title of your PR / MR corresponds to the required format
Commit message follows required format {label}(dspy): {message}
If there are any further improvements or adjustments required, please feel free to provide feedback. This pull request aims to enhance the functionality and usability of the AzureAISearchRM class, and any suggestions for refinement are highly appreciated.

@insop @arnavsinghvi11 , Can I get the review on this PR.

Thanks @HARISHKUMAR1112001 ! left a few minor comments. good to merge after that!

Thanks @arnavsinghvi11 for the quick review. I have updated the code with correct spellings.

Thanks @HARISHKUMAR1112001 !

@HARISHKUMAR1112001 @arnavsinghvi11 i'm getting the following error with the following code:
requirements.txt
git+https://github.com/stanfordnlp/dspy.git
azure-search-documents==11.6.0b1
`
client = openai.AzureOpenAI(
base_url=f"{openai.api_base}/openai/deployments/{deployment_id}/extensions",
api_key=openai.api_key,
api_version=openai.api_version
)
    azure_search = AzureAISearchRM(
    search_service_name=search_endpoint,
    search_api_key=search_key,
    search_index_name=search_index_name,
    field_text="content",
    k=3,
    azure_openai_client=client,
    openai_embed_model="text-embedding-ada-002",
    )

    dspy.settings.configure(rm=azure_search)
    retrieve = dspy.Retrieve(k=3)
    retrieval_response = retrieve(name).passages

    response=''
    for result in retrieval_response:
        print("Text:", result, "\n")
        response += result + "\n"

error:
[2024-04-18T08:45:17.286Z] Executed 'Functions.f29bot2' (Failed, Id=60fe1453-0587-4435-bd53-525ca750323c, Duration=222ms)
[2024-04-18T08:45:17.286Z] System.Private.CoreLib: Exception while executing function: Functions.f29bot2. System.Private.CoreLib: Result: Failure
[2024-04-18T08:45:17.286Z] Exception: ServiceRequestError: <urllib3.connection.HTTPSConnection object at 0x7138005e6140>: Failed to resolve 'https' ([Errno -2] Name or service not known)
[2024-04-18T08:45:17.286Z] Stack:   File "/usr/lib/azure-functions-core-tools-4/workers/python/3.10/LINUX/X64/azure_functions_worker/dispatcher.py", line 495, in _handle__invocation_request
[2024-04-18T08:45:17.286Z]     call_result = await self._loop.run_in_executor(
[2024-04-18T08:45:17.286Z]   File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
[2024-04-18T08:45:17.286Z]     result = self.fn(*self.args, **self.kwargs)
[2024-04-18T08:45:17.286Z]   File "/usr/lib/azure-functions-core-tools-4/workers/python/3.10/LINUX/X64/azure_functions_worker/dispatcher.py", line 768, in _run_sync_func
[2024-04-18T08:45:17.286Z]     return ExtensionManager.get_sync_invocation_wrapper(context,
[2024-04-18T08:45:17.286Z]   File "/usr/lib/azure-functions-core-tools-4/workers/python/3.10/LINUX/X64/azure_functions_worker/extension.py", line 215, in _raw_invocation_wrapper
[2024-04-18T08:45:17.286Z]     result = function(**args)
[2024-04-18T08:45:17.286Z]   File "/home/juanjo/juanjo_repos/functions/f29bot2/init.py", line 54, in main
[2024-04-18T08:45:17.286Z]     retrieval_response = retrieve(name).passages
[2024-04-18T08:45:17.286Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/dspy/retrieve/retrieve.py", line 30, in call
[2024-04-18T08:45:17.286Z]     return self.forward(*args, **kwargs)
[2024-04-18T08:45:17.286Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/dspy/retrieve/retrieve.py", line 39, in forward
[2024-04-18T08:45:17.286Z]     passages = dsp.retrieveEnsemble(queries, k=k,**kwargs)
[2024-04-18T08:45:17.286Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/dsp/primitives/search.py", line 57, in retrieveEnsemble
[2024-04-18T08:45:17.286Z]     return retrieve(queries[0], k, **kwargs)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/dsp/primitives/search.py", line 12, in retrieve
[2024-04-18T08:45:17.287Z]     passages = dsp.settings.rm(query, k=k, **kwargs)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/dspy/retrieve/retrieve.py", line 30, in call
[2024-04-18T08:45:17.287Z]     return self.forward(*args, **kwargs)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/dspy/retrieve/azureaisearch_rm.py", line 328, in forward
[2024-04-18T08:45:17.287Z]     results = self.azure_search_request(
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/dspy/retrieve/azureaisearch_rm.py", line 288, in azure_search_request
[2024-04-18T08:45:17.287Z]     sorted_results = sorted(results, key=lambda x<EMAIL_ADDRESS>reverse=True)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/search/documents/_paging.py", line 54, in next
[2024-04-18T08:45:17.287Z]     return next(self._page_iterator)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/paging.py", line 75, in next
[2024-04-18T08:45:17.287Z]     self._response = self._get_next(self.continuation_token)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/search/documents/_paging.py", line 124, in _get_next_cb
[2024-04-18T08:45:17.287Z]     return self._client.documents.search_post(search_request=self._initial_query.request, **self._kwargs)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/tracing/decorator.py", line 78, in wrapper_use_tracer
[2024-04-18T08:45:17.287Z]     return func(*args, **kwargs)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/search/documents/_generated/operations/_documents_operations.py", line 777, in search_post
[2024-04-18T08:45:17.287Z]     pipeline_response: PipelineResponse = self._client._pipeline.run(  # pylint: disable=protected-access
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/_base.py", line 230, in run
[2024-04-18T08:45:17.287Z]     return first_node.send(pipeline_request)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/_base.py", line 86, in send
[2024-04-18T08:45:17.287Z]     response = self.next.send(request)
[2024-04-18T08:45:17.287Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/_base.py", line 86, in send
[2024-04-18T08:45:17.288Z]     response = self.next.send(request)
[2024-04-18T08:45:17.288Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/_base.py", line 86, in send
[2024-04-18T08:45:17.288Z]     response = self.next.send(request)
[2024-04-18T08:45:17.288Z]   [Previous line repeated 2 more times]
[2024-04-18T08:45:17.288Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/policies/_redirect.py", line 197, in send
[2024-04-18T08:45:17.288Z]     response = self.next.send(request)
[2024-04-18T08:45:17.288Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/policies/_retry.py", line 553, in send
[2024-04-18T08:45:17.288Z]     raise err
[2024-04-18T08:45:17.288Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/policies/_retry.py", line 531, in send
[2024-04-18T08:45:17.288Z]     response = self.next.send(request)
[2024-04-18T08:45:17.288Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/_base.py", line 86, in send
[2024-04-18T08:45:17.288Z]     response = self.next.send(request)
[2024-04-18T08:45:17.288Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/_base.py", line 86, in send
[2024-04-18T08:45:17.288Z]     response = self.next.send(request)
[2024-04-18T08:45:17.288Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/_base.py", line 86, in send
[2024-04-18T08:45:17.288Z]     response = self.next.send(request)
[2024-04-18T08:45:17.288Z]   [Previous line repeated 2 more times]
[2024-04-18T08:45:17.288Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/_base.py", line 119, in send
[2024-04-18T08:45:17.288Z]     self._sender.send(request.http_request, **request.context.options),
[2024-04-18T08:45:17.288Z]   File "/home/juanjo/juanjo_repos/functions/.venv/lib/python3.10/site-packages/azure/core/pipeline/transport/_requests_basic.py", line 386, in send
[2024-04-18T08:45:17.288Z]     raise error
[2024-04-18T08:45:17.288Z] .
already commented this on the discord this morning

thanks for ur response @HARISHKUMAR1112001
it was really weird because both the AzureOpenAI and the SearchClient were working alone without DSPy
but
debugging with a custom AzureRM class i think i found the error
it was related to the "search_service_name=search_endpoint" arg
I was passing the search_endpoint as a complete url:
search_endpoint = "https://f29search.search.windows.net";
[2024-04-19T12:36:57.321Z] Azure Search Request
[2024-04-19T12:36:57.321Z] <SearchClient [endpoint='https://https://f29search.search.windows.net.search.windows.net', index='sharepoint-index']>
tried then without "https://"
search_endpoint = "https://f29search.search.windows.net";
[2024-04-19T12:41:45.467Z] Azure Search Request
[2024-04-19T12:41:45.469Z] <SearchClient [endpoint='https://f29search.search.windows.net.search.windows.net', index='sharepoint-index']>
but should have passed the service name only:
search_endpoint = "f29search"; # Add your Azure AI Search endpoint here
now it worked!
sorry for bothering, was my bad!


REQUEST: New membership for @MregXN

GitHub Username
@mregxn
I'm working in Microsoft Dapr China Team now. I am now trying to add E2E tests and Metadata files.
Requirements

[x] I have reviewed the community membership guidelines (https://github.com/dapr/community/blob/master/community-membership.md)
[x] I have enabled 2FA on my GitHub account. See https://github.com/settings/security
[x] I have subscribed to the Dapr community Discord server
[x] I am contributing (any of the following apply: issues, discussions, PRs, reviews) to 1 or more Dapr repositories

List of contributions to the Dapr project

PRs in dapr/components-contrib
PRs in dapr/java-SDK
Repo in dapr-sandbox

Sponsors
@mukundansundar  @skyao

I support this request.

+1 I support this request.

@yaron2  Hi. Can you approve this issue for me ?

+1

@MregXN - Invitation sent

Closing issue


docs: file.delete() method

f.delete() works well. I saw the URL in models-file but not the method for it. It would be good to have in readthedocs quickstart if possible
[via Erik L]

The method will be added to the documentation. Thanks Erik L & @jackDiGi

Added to the documentation.


Enable requireNumericLiterals rule.

https://github.com/jscs-dev/node-jscs/blob/master/lib/rules/require-numeric-literals.js

Each bad example needs to be in a separate file to ensure it fails properly.
Other than that, this looks good (though I've not done any of these parseInt versions before).

Yeah, me neither, it just seemed in line with this projects goal of enforcing use of the new syntax.

Yep. Agreed totally.

How are we supposed to parse simple strings into integers?

You can use Number(), which I believe may be more accurate than parseInt since it'll actually return NaN if the argument is not valid, unlike parseInt, e.g.:
let value = "123abc";
parseInt(value); // => 123
Number(value); // => NaN

That said, I was under the impression this rule was only to prevent using parseInt with string literals, and mainly for binaries, octals, and hexadecimals (as the examples and description suggest). Was the intention of the rule to unconditionally forbid the use of parseInt altogether, @hzoo?

@brzpegasus Right, but consider this example:
return `rgba(${parseInt(red, 16)}, ${parseInt(green, 16)}, ${parseInt(blue, 16)}, 0.1)`;

Using Number this would become:
return `rgba(${Number(`0x${red}`)}, ${Number(`0x${green}`)}, ${Number(`0x${blue}`)}, 0.1)`;

Aren't nested template strings a bit "too much"? I don't have a very strong opinion on this.

All of those examples should be fine. This rule should only complain about literal values (not variables).

Well, based on the rule upstream I am wrong (it seems that it is forbidding all usage of parseInt?!?).

Only forbids parseInt with radix 2, 8 or 16.

It's probably that I didn't check if the first argument was a literal or not https://github.com/jscs-dev/node-jscs/blob/master/lib/rules/require-numeric-literals.js. (Didn't write enough test cases) Feel free to do a PR and we can backport to 2.x

Submitted https://github.com/jscs-dev/node-jscs/pull/2133 to fix.


Outbound call Disconnect Issue

Outgoing call reject not working
When i make outgoing call its connecting to receiver. In receiver side before pick the call they disconnect the call it disconnected but in sender side call not disconnecting. timer for the call duration still running after the call disconnected by receiver side.
Voice-quickstart-andriod-sdk
Android studio 3.0.1
Android Build version  25.0.0
Android Gradle Version "com.android.tools.build:gradle:2.3.0"
target sdkversion 23

Hi @Mahawbc
Is this happening to you both on Android and iOS? If this is an Android Voice SDK issue, please go to Android Voice Quickstart and file a new issue.
Thanks
-bobie

Hi Dear ,
i was using twillio api with call kit in swift , but problem is that  i have implement  these delegate TCDeviceDelegate,TCConnectionDelegate and in which func connectionDidDisconnect(_ connection: TCConnection) {
    print(connection)

    AppDelegate.shared.providerDelegate.providers.reportCall(with: UUID(), endedAt: nil, reason: .failed)

    self.timingDelegate?.setTimingState(isCallReceivedOrAccpt: false, connectionState: "disconected")

    for call in AppDelegate.shared.callManager.calls{

        CallManager.manager.end(call: call)

    }

This func is not called in reciver side when sender hang up call , but func is called on sender side   when call is hang up by receiver side , we are implement this using call kit in swift language , Please provide us desire solution for it

Hi @promaticsIosTeam
The Twilio Client 1.2 SDK is not supported anymore and please follow this quickstart guide to integrate the Programmable Voice iOS SDK (4.0) to your application.
In a alice-to-bob call scenario, the caller will receive the callDidConnect: delegate callback when the call is connected between the caller and Twilio Voice service. The callee only receives the callDidConnect: callback after calling call.accept() and connected to the call.
Let us know if you have any trouble using the Programmable Voice SDK.
Thanks,
-bobie


feat: Support Pyth Network oracle migration

Migrate wooracle to pyth oracle

Diff: https://www.diffchecker.com/lO1kvN63/


Reproducing Performance on DocVQA using LayoutLMv3/LayoutLMv2

I tried my best to reproduce the results reported in the paper, which is about 78% test set ANLS. But all I get is just 74% on the test set (73% on validation set), which is still way below what is reported.
Can we know more details about how to get the reported number.
My repo: https://github.com/allanj/LayoutLMv3-DocVQA
Model I'm using: LayoutLMv3-base
OCR I use: Microsoft READ API, using the latest model version.

I tried different matching mechanism to find the answer.
Try sliding window approach (which not really works)
Even following the paper to use 128 batch size, 100k optimization steps (which is equivalent to 300 epochs I don't really think that is necessary.)

The best performance I can get for using LayoutLMv3-base is just about 73.3% on validation set.
I also refer the following issues as I can't really find a public codebase that can reproduce the DocVQA results.

https://github.com/NielsRogge/Transformers-Tutorials/issues/49
https://github.com/microsoft/unilm/issues/616
https://github.com/microsoft/unilm/issues/501
https://github.com/microsoft/unilm/issues/282

Appreciate that if the authors can give more suggestions/details about the experiments.

There are several steps to experiment on DocVQA with the extractive method:

Pre-processing.
1.1 Get the text information of the documents using an OCR engine (e.g., Microsoft Read API)
1.2 Find the start and end token-level positions of each answer in the text (e.g., with edit distance matching)
Model prediction.
2.1 Train (with parameter tuning) and predict the start and end positions with models (e.g., LayoutLMv2/3)
Post-processing.
3.1 Reconstruct the answers from the text based on the predicted positions
3.2 Fix apparent errors (e.g., remove some whitespaces and punctuation marks)

Each step could have room for improvement. It can be helpful to analyze and improve the upper bound step by step. For example, what is the ANLS score calculated using the answers found by your start and end positions/indices? If we can get a perfect text from human annotations, the score should be close to 100. With good OCR results, the score could be greater than 95.

Thanks. Is it possible to provide the details about how you did it for this dataset? I think this could be important to reproduce the performance and better help the open-source community.

@allanj I am trying to reproduce the result with layoulmv2 model on your code but getting below error
RuntimeError: CUDA error: device-side assert triggered
This error is occurring on train_dataloader loop


Update issue status from "In Progress" to "In Review" when PR is linked to the issues

For this workflow, we need just GitHub jobs to handle them.
Small example:

https://medium.com/@martatatiana/github-projects-change-issue-status-based-on-pull-request-change-45dcacab9fb7

Isn't this already builtin Github behavior
https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue

You can link a pull request or branch to an issue to show that a fix is in progress and to automatically close the issue when the pull request or branch is merged.

It only works for closing the issues. It will not move it to "In Review" when PR is created.
So the built-in function is just to close the issue (mark it as done) once PR is merged/closed


Fix broken rendering in Google Colab

Before patch :

After patch :

Thanks! Could you sign the CLA agreement?


remove sus ass check for 'cshacked.pl' that results in a BSOD.

why is this in here?

why was this denied? this is malicious code.

@danielkrupinski can you adress that? thats fishy

@MrBisKit That was testing code. It does not harm your software nor hardware in any way.

still not nice tho that internet connectivity/force BSOD shit is so hidden

@MrBisKit It does not connect to internet at all.

@danielkrupinski do you even know the code thats inside your cheat? jesus christ dude from the looks of this source it looks like a mashup of other's code but god damn. you're either lying to our faces or you're completely oblivious to the code inside "your" cheat.

ignoring all this, why havent you removed this yet? why must this remain in the public source?

@kittenzok can you explain what it does excacly? i can't really understand this code

the 'data' array is an encoded string, in the hooking function the array is decoded to "cshacked.pl"
the 'checkdata' function is actually DnsQuery_A which uses the internet to check for valid dns records for the provided domain name (cshacked.pl)
in the event that this check does not find a vaild dns record it will call 'updatehookdata' which is actually RtlAdjustPriviledge
this adjusts the programs priviledge level so that it may throw a hard error and crash the system resulting in the blue screen of death.
then 'savehookdata' is called which is actually NtRaiseHardError and is used to throw the exception to crash the entire machine.
tldr; code checks if cshacked.pl exists and if not throws a wrench in the virtual cogs of your machine and causes it to shutdown
its a commonly used technique by skids because of some youtube vid by another skid teaching the other skids how to make (((epic))) trollz and bsod in cpp for teh lulz
i believe the video has been deleted but im 99% it was made by Zer0Memory on youtube

@kittenzok You are wrong, read about functions before talking about them.


Feature request: Send an email through local sendmail for each notification

I suggested this on Reddit, and it seemed to get some positive comments.

I realize this might not be straight forward, since there is no central server to send out emails, but perhaps a call to the user's local sendmail can be triggered, if OpenBazaar is running on a Linux machine? Or at least add an option to enable or disable this.
I think it would be nice for people who are running the OB server headlessly and maybe remotely, that they can enable emails to be instantly notified of sales, questions from buyers, money received, updates on disputes, etc. Maybe even PGP encrypted emails.

We're going to use this issue to track the email feature @hoffmabc
Requirements
As a user, I need to get an email when...

[ ] Someone follows you (once per node)
[ ] Dispute opened
[ ] Dispute resolved
[ ] Chat message (once per node per day)
[ ] Chat message in an order (once per node per day)

As a Vendor, I need to get an email when...

[ ] I receive a funded order
[ ] I receive funds (direct or escrow)
[ ] I receive a rating received

As a Buyer, I need to get an email when...

[ ] The order is confirmed/shipped
[ ] An order refunded

We also need email templates for each of these email notifications. @SamPatt this might be a good one for you.

Thanks @drwasho I'll look at this.
Minor point: The "Dispute resolved" message should probably be different based on if they won or lost a dispute, since one requires action (accept payout) and the other doesn't.

This was completed.


cargo run is error

extern crate http;

use http::Request;

fn main() {
    let request = Request::builder()
      .uri("https://www.rust-lang.org/")
      .header("User-Agent", "awesome/1.0")
      .body(())
      .unwrap();
}

cargo run is  error....
warning: unused variable: `request`
 --> src/main.rs:6:9
  |
6 |     let request = Request::builder()
  |         ^^^^^^^ help: consider prefixing with an underscore: `_request`
  |
  = note: `#[warn(unused_variables)]` on by default

    Finished dev [unoptimized + debuginfo] target(s) in 0.56s
     Running `target/debug/http`

There is no error in that output.

warning: unused variable: request

Warnings are not errors.

Its OK, I know why, because there's no use of this variable in the back, so warning, thanks.


fix: changed color on splash screen

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/35018
PROPOSAL: -
Tests

Note: The issue happened only in production

Open the app on the web as a production build
Refresh to see the splash screen

[x] Verify that the logo has a proper color
[x] Check this PR   in case of regression
[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Open the app on the web as a production build
Refresh to see the splash screen

[x] Verify that the logo has a proper color
[x] Check this PR   in case of regression
[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

n/a

Android: mWeb Chrome
n/a

iOS: Native

n/a

iOS: mWeb Safari
n/a

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/7682108/09eaf3d6-e7ad-4957-9e11-632405f2988b

MacOS: Desktop
n/a

Bumping my question above, then I can merge - is there a way to build for production locally? Thanks!

Bumping my question above, then I can merge - is there a way to build for production locally? Thanks!

Yup! https://github.com/Expensify/App/tree/main?tab=readme-ov-file#local-production-builds

sweet! Did that, looks great

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 1.4.33-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to staging by https://github.com/dangrous in version: 1.4.34-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@dangrous @barttom Should we test above PR in production or staging?

@kbecciv you can wait for production, thanks!

There's deploy blocker came from this PR

@dangrous We checked on production build v1.4.33-5 - issue is there, but not in Staging. PR steps are referring to production.
Let me know if QA team should re-test on staging. Thanks
https://github.com/Expensify/App/assets/93399543/963ae9f5-7611-4d75-b0f9-093eb7995857

🚀 Deployed to production by https://github.com/francoisl in version: 1.4.34-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

@kbecciv we ended up reverting this PR, you can ignore all testing - thanks!


After the gocd db data is migrated, the following error message is displayed:

Perform data backup as described in admin backup, and migrate the data to the new gocd environment. Click plugin-cd.go.contrib.elasticagent.kubernetes The following error is reported in the log file. It is found that the cruise.h2.db database using the new gocd is normal, but there will be problems using the migrated cruise.h2.db file. Please help me
The log is as follows, please help analyze：
2022-11-23 03:15:09,988 ERROR [101@MessageListener for WorkFinder] KubernetesPlugin:127 - Failed to handle request cd.go.elastic-agent.should-assign-work
io.fabric8.kubernetes.client.KubernetesClientException: Operation: [list]  for kind: [Pod]  with name: [null]  in namespace: [A namespace name]  failed.
[...]
com.thoughtworks.go.plugin.infra.FelixGoPluginOSGiFramework.executeActionOnTheService(FelixGoPluginOSGiFramework.java:303)
[....]
Caused by: java.net.SocketTimeoutException: connect timed out

Please supply more information, e.g

what type of migrate or upgrade you performed
which versions of GoCD and plugins you were using before and after
what you have done to try and debug or fix the issue

This doesn't sound related to database change, but may relate to the upgrade you performed or just your new environment. This indicates the plugin cannot talk to your cluster's API server. Try comparing the config for the cluster profile before and after to check the cluster URL/token/cluster CA cert is correct for the new environment. If you are trying to load the config in a new cluster, you will need to correct the configuration for the new cluster in your elastic agents configuration at the very least.

The gocd image and plug-in version after migration are consistent with those before migration (gocd==19.5.0, plug-in version==3.0.0-156)
I found that the problem was not cluster URL/token/cluster CA certificate, because the plug-in can call the cluster api to create the pod of go agent
What places do you need to configure to load the configuration in the new cluster? I have configured the k8s cluster profile and Elastic Agent Profiles under the administrative profiles of GOCD. Is there anything else you need to configure?

The error above says 'connect timed out' which would indicate a connectivity issue calling the API server so I don't understand what problem you are having if you say it can create pods successfully.

Other than that what is different about your new clusterr to the old cluster? Which k8s version? These are very old versions you are dealing with. No guarantees they work on new k8s and docker.

Closing this for now - if you can supply additional info we can re-open it.


address format

Need to figure out an address format.
I'm thinking that something like
(type(:args)?)(,type(:args)?)*
where , is a separator, type is a protocol name (ws or net or utp etc) args is whatever information type needs (optional - for example gzip doesn't need args)
ipfs uses / like a unix path, but I think this is ambigious because you have to know how many arguments a type takes to be able to parse it! That is especially bad for an upgradable system where you may see a descriptor for a thing that you don't support yet, and won't know what it means. It may mean you'll need to do IO while parsing.
instead better to use a different seperator, and allow protocols to format their args however they need, (provided any internal separators are escaped)
'|' would be nice, because it's a lot like piping, but `,' means you couldn't need to escape it on the terminal.

@clehner what do you think?

Sounds good

note: we could also hook into the mulitserver addresses to allow users with higher privacy requirements to say things like "only replicate my data over local networks" or "only over tor", etc,
or "not over these protocols which I consider weak" etc

made this: https://github.com/dominictarr/separator-escape
could use \ as escape, which is familiar, but since other things use \ too you have to escape the escapes which is confusing! the separator isn't a problem.


Render six-select correctly when value is set before rendering

Addresses an issue where the six-select component failed to render properly if the value was set before the rendering process. Additionally, it resolves a bug that prevented selected items from being displayed as checked when the options property is used.

Closed in favor of https://github.com/six-group/six-webcomponents/pull/50


Return empty json array in case of no results returned

I'm using the -json output of the duckdb command as that allows me to send the query result straight to a client application without having to parse through it slowly in python.
The query returns empty string when there are no results, which is not consistent with the case when the query result is non-empty, in which case an array of json objects is returned.
% duckdb -json /tmp/xxx.db 'select 1 where 1=1'
[{"1":1}]
% duckdb -json /tmp/xxx.db 'select 1 where 1=0'
%
% # ^ empty string returned

It's no big deal because I can just wrap it in an if statement, but I think it should be made consistent. Empty result should return
[] instead of empty string.
Alternatively it would be nice if there was an option to receive jsonlines output directly, ie. results not wrapped in an array.
Also it would be nice if I could receive json data directly using the python client.

This is again the SQLite shell that does this, not DuckDB

This is again the SQLite shell that does this, not DuckDB


Allow setting negative exposures e.g. in lat-long environment EDF

Does this mean just being able to move the slider to <0 as you can set the exposure in lat-long edfs to negative values in the text field. Also, do you want to set the default slider position for lat-long edfs to have a range from -ve to +ve like diffuse edf? I hope my questions are clear?

This ticket is not only about environment EDFs, it's about exposures in general: wherever there is an exposure parameter, it should be possible to specify a negative exposure value, either by typing the value directly, or by moving the slider. The slider's defaut range should probably be symmetric around 0 to readily allow negative values.

Ah ok. I've fixed the issue through #1886 by first fixing the slider range in colormaps and then set the slider to be symmetric around zero for exposure fields. The exposure fields with numeric inputs have slider bars that are already symmetric around 0. I hope this is what you want. However, the travis build gets timed out for gcc 6.

@rgirish28 What's the status on this?

I think this issue can be closed as we have merged the fix through #1886. The build timing out also was fixed before merging.

Thanks!


CAMEL-20410: documentation fixes for camel-file

Fixed samples
Converted to use tabs
Fixed grammar and typos
Fixed punctuation
Added and/or fixed links
Fixed out-of-order elements
Cleaned up duplicated elements

There were a lot of problems on this one, so I had to reorganize things a bit.