Amplify migrate api not working

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
18.12.1
Amplify CLI Version
10.6.1
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
None
Describe the bug
When I run amplify migrate api, I get the message "You are using the deprecated parameterization of @connection which cannot be automatically migrated."
I then go into the schema, and update all the @connection directive, and replace them by the appropriate @hasOne, @hasMany...
When I then run amplify upgrade api, I now get the message: 'Your GraphQL Schema is using "@belongsTo", "@hasMany", "@hasOne", "@index" directives from the newer version of the GraphQL Transformer. Visit https://docs.amplify.aws/cli/migration/transformer-migration/ to learn how to migrate your GraphQL schema.'
So I then updated amplify/cli.json to read:
{
"features": {
"graphQLTransformer": {
"addMissingOwnerFields": false,
"validateTypeNameReservedWords": true,
"useExperimentalPipelinedTransformer": true,
"enableIterativeGSIUpdates": true,
"secondaryKeyAsGSI": true,
"transformerVersion": 2,
"skipOverrideMutationInputTypes": true,
"suppressSchemaMigrationPrompt": true
}, [...]
But when I then run amplify upgrade api, I get the same message: 'Your GraphQL Schema is using "@belongsTo", "@hasMany", "@hasOne", "@index" directives from the newer version of the GraphQL Transformer. Visit https://docs.amplify.aws/cli/migration/transformer-migration/ to learn how to migrate your GraphQL schema.'
I get the same message when I try to run amplify push.
Expected behavior
After updating the graphql schema to not have any @connection directive, amplify upgrade api should work rather than telling me that I have directive tied to the new V2 version
Reproduction steps

run amplify migrate api
have amplify tell you that you need to replace the @connection directive with their new counterpart
update your schema file to not contain any @connection directive, and instead the requested replacement (@hasOne, @hasMany, ...)
run amplify migrate api again
have amplify say that you can't use these new directive since you are using V2 directives

Project Identifier
No response
Log output

# Put your logs below this line
BEFORE REMOVING @connection:

ldaudet@pc:~/janus_envs/v2update$ amplify migrate api
⚠ Your instance type for OpenSearch is t2.small.elasticsearch, you may experience performance issues or data loss. Consider reconfiguring with the instructions here https://docs.amplify.aws/cli-legacy/graphql-transformer/searchable/
GraphQL schema compiled successfully.

Edit your schema at /home/ldaudet/janus_envs/v2update/amplify/backend/api/gen2/schema.graphql or place .graphql files in a directory at /home/ldaudet/janus_envs/v2update/amplify/backend/api/gen2/schema
You are using the deprecated parameterization of @connection which cannot be automatically migrated.

AFTER REMOVING @connection and replacing them with the new directives @hasOne, @hasMany, ...

ldaudet@pc:~/janus_envs/v2update$ amplify migrate api
⚠ Your instance type for OpenSearch is t2.small.elasticsearch, you may experience performance issues or data loss. Consider reconfiguring with the instructions here https://docs.amplify.aws/cli-legacy/graphql-transformer/searchable/
🛑 Your GraphQL Schema is using "@belongsTo", "@hasMany", "@hasOne", "@index" directives from the newer version of the GraphQL Transformer. Visit https://docs.amplify.aws/cli/migration/transformer-migration/ to learn how to migrate your GraphQL schema.

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hi  @ldaudet 👋, thanks for raising this issue.we are working on reproducing the issue. Could you please run below command and send us the report amplify diagnose --send-report. please refer here

Hi @AnilMaktala , thanks for getting back to me. Which command do you want me to run before sending you the report? If you mean 'amplify migrate api', do you want me to run it before I update the schema to V2 directive, when amplify then tells me I need to remove @connection for example, or after I update the schema, when amplify then tell me that I can't use V2 directives

Hey @ldaudet, amplify diagnose --send-report command is sufficient for now.

Hi @AnilMaktala , just ran the command. Let me know if there is anything I can do.

Hey @ldaudet, Please add the generated Project identifier to the ticket. Please refer the instructions here

Hi @AnilMaktala, unlike what is being shown in the doc you shared, the command does not print out a project identifier. Here is the full output of the command when I ran it:

Hi @ldaudet, Are you executing the command from the root directory of the project?

@AnilMaktala yes I am

Hey @ldaudet :wave: were you able to migrate all instances of @connection and similar v1 directives in your schema manually? If you have done so and have also updated the feature flags (as posted in your original post), you will not need to run the migration tool. Are you able to push after the manual migration?

Hi @josefaidt . I am not able to push after doing the manual migration. I get the same error that I get when doing amplify api upgrade:  'Your GraphQL Schema is using "@belongsTo", "@hasmany", "@hasone", "https://github.com/Index" directives from the newer version of the GraphQL Transformer. Visit https://docs.amplify.aws/cli/migration/transformer-migration/ to learn how to migrate your GraphQL schema.'

My guess is that once I have updated all the schema to be V2 compliant, I then needs to have amplify understand that I am now using the V2 transformer. Right now, it still thinks I am using the V1, and thus won't be allowing me to run any amplify operations. I am not sure what the procedure is to manually update the transformer version so that amplify understands that it now needs to use the V2 to compile the schema.

Also, I attempted to let amplify know of the upgrade to V2 by setting the cli.json in the amplify folder the following values:
"features": {
"graphqltransformer": {
...
"useexperimentalpipelinedtransformer": true,
"transformerversion": 2,
...
},

Hey @ldaudet those are the correct feature flags to change. Do you have a cli-inputs.json file in your API's directory? With contents like the following:
{
  "version": 1,
  "serviceConfiguration": {
    "apiName": "a11942",
    "serviceName": "AppSync",
    "defaultAuthType": {
      "mode": "API_KEY",
      "expirationTime": 7
    }
  }
}

Hi @josefaidt , I have a cli-inputs.json in the folder of my REST API, but no in the graphql API. Is there a command to run to create this file for the graphql API, or should I create it manually?

Hey @ldaudet since you have migrated the schema manually and have updated the corresponding feature flags I think it's easiest to create this manually, but we can help! In general it should follow the structure above, but do you have any other auth mechanisms applied like Cognito User Pools for owner auth?

Hi, thanks @josefaidt , the missing file was indeed the issue. I was able to recreate it, and that allowed the upgrade to go through. Unfortunately, the push itself was a failure because of the GSI. With the upgrade, all of them more or less have been changed, so a push would mean more than one GSI operation per table. I found a flag that allows for incremental GSI push and set it to true. This brought issue with the limit of files being opened, but after raising the limit, the app was able to create a push with 13 steps to deploy all the changes. Unfortunately, during step 4/13, the push stopped entirely. After over an hour with no updates, I had to terminate the process. This left the dev backend I was attempting the push in a completely unstable state, and after 3 days of working on nothing but this, I still haven't find a way to get the push to go through, on this backend or a new one I created since then. Finally, all these attempts to deploy means that I am apparently hitting some rate limit of some kind, as I get 'InternalFailureException: Oops, something went wrong. Please try again later.', with no clear explanation as to what the root cause is, that block progress until the next day...

Do you know of any way I can check on the actual progress of an iterative deployment? I can see nothing happening on cloudformation, and the deployment state file has been stuck like this for over an hour:
{   "version": "1",   "startedAt": "2023-02-21T14:21:04.738Z",   "status": "DEPLOYING",   "currentStepIndex": 2,   "steps": [     {       "status": "DEPLOYED",       "previousMetaKey": "amplify-appsync-files/73816dc2b29d89f655e0f22ab0394aac2a9fe9ff/states/initial-stack/deployment-meta.json"     },     {       "status": "DEPLOYED",       "previousMetaKey": "amplify-appsync-files/73816dc2b29d89f655e0f22ab0394aac2a9fe9ff/states/01/deployment-meta.json"     },     {       "status": "DEPLOYING",       "previousMetaKey": "amplify-appsync-files/73816dc2b29d89f655e0f22ab0394aac2a9fe9ff/states/02/deployment-meta.json"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     },     {       "status": "WAITING_FOR_DEPLOYMENT"     }   ] }

My concern is that the deployment hits a rate limit a stalls silently. I am trying to find a way to check whether or not that is the case, or what other issue might be happening that causes the deployment to stall.

Hey @ldaudet glad to hear you were able to create the file and pass that speedbump, but sorry to hear of the rough experience past that! For what it's worth, CLI logs are captured in ~/.amplify/logs, which should log a RateException if you were experiencing a rate limit exception. Can you try deleting the leftover deployment-state.json file and re-attempt the push?

Hi @josefaidt , thanks for letting me know, I didn't know logs file were available there. Unfortunately, no luck on the rate limit exception, here is the log for the error I had yesterday:
2023-02-21T01:36:42.281Z|info : amplify init core   2023-02-21T01:36:42.301Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({} 2023-02-21T01:36:51.695Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["profile"]) 2023-02-21T01:36:51.696Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"us-east-1"}]) 2023-02-21T01:36:51.696Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["profile"]) 2023-02-21T01:36:51.702Z|info : amplify-provider-awscloudformation.amplify-service-permission-check.checkAmplifyServiceIAMPermission.amplifyClient.listApps([]) 2023-02-21T01:36:52.370Z|info : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.listApps([{"maxResults":25}]) 2023-02-21T01:36:52.509Z|info : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.getBackendEnvironment([{"appId":"[***]8lk7qq","environmentName":"[***]test"}]) 2023-02-21T01:36:52.725Z|error : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.getBackendEnvironment([{"appId":"[***]8lk7qq","environmentName":"[***]test"}]) NotFoundException: BackendEnvironment lasttest does not exist. 2023-02-21T01:36:52.725Z|info : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.getBackendEnvironment([{"appId":"[***]8lk7qq","environmentName":"[***]test","stackName":"[***]ify-[***]us-[***]test-[***]651","deploymentArtifacts":"amplify-janus-lasttest-203651-deployment"}]) 2023-02-21T01:36:54.142Z|error : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.getBackendEnvironment([{"appId":"[***]8lk7qq","environmentName":"[***]test","stackName":"[***]ify-[***]us-[***]test-[***]651","deploymentArtifacts":"amplify-janus-lasttest-203651-deployment"}]) InternalFailureException: Oops, something went wrong. Please try again later.
I am not sure what was going on, and assumed it was a rate issue because then this morning, I just got on the same cli, pressed up and enter to run the same command and got the deployment of the initial state of the app (pre-V2 resolver upgrade), to go through.
As far as trying the V2 upgrade to deploy, I removed the deployment-state.json file and re attempted the push, but got the error:
DeploymentError: ["Index: 0 State: {\"deploy\":\"waitingForDeployment\"} Message: Resource is not in the state stackUpdateComplete"]
I then tried running amplify api push --iterative-rollback, and got the error:
DeploymentError: ["Index: 0 State: {\"deploy\":\"waitingForDeployment\"} Message: Resource is not in the state stackUpdateComplete"]
This is the same thing that happened on our dev environment, where we are gonna have to scrap it because it has been left in an unstable state where push are now failing. When checking on CloudFormation, I see that the graphql api deployment crashed because a lot of the tables went from status UPDATE_IN_PROGRESS to status UPDATE_FAILED with the reason being, in the case of the Education table for example:
Embedded stack arn:aws:cloudformation:us-east-1:441488514709:stack/amplify-janus-lasttest-64029-apigen2-SVFMODO692ZH-Education-1H55F4SIRPKV3/8a74f780-b1e2-11ed-9327-0ab450570d63 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [EducationTable].

For other tables, the error might be involving the resolver as well, such as the Application table:
Embedded stack arn:aws:cloudformation:us-east-1:441488514709:stack/amplify-janus-lasttest-64029-apigen2-SVFMODO692ZH-Application-IHG6RCSWIUJ3/8ab97a90-b1e2-11ed-b4a2-0ee6615464f1 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [CreateApplicationResolver, GetApplicationResolver, ApplicationTable].
No matter what though, the error on the tables themselves is always the same:
Resource handler returned message: "Cannot perform more than one GSI creation or deletion in a single update" (RequestToken: be2ae932-20bc-7ff9-6f41-fc36319e967c, HandlerErrorCode: InvalidRequest)
I just don't understand why this error is being thrown. I assumed that maybe the table had had some modifications done from the initial attempt to push, and amplify not being aware of it somehow is sending updates that conflict with the ones that have already been applied. But when I check the tables for drift, none is detected. I am at a complete loss as to what could amplify be doing to cause that error to trigger when doing an incremental update specifically to prevent it from happening. At this point though, as far as I can tell, the backend is in a locked state where all push will fail.

Going further down, I compared the current template for the Education table as defined on CloudFormation, and compared it with the template on the S3 from .../states/initial-stack/stacks/Education.json. On the current template, the AttributeDefinition for the GSI looks like this:
        "AttributeDefinitions": [           {             "AttributeName": "id",             "AttributeType": "S"           },           {             "AttributeName": "memberEducationId",             "AttributeType": "S"           },           {             "AttributeName": "menteeEducationId",             "AttributeType": "S"           },           {             "AttributeName": "mentorEducationId",             "AttributeType": "S"           }         ],
While on the S3, the template for the initial step looks like this:
                "AttributeDefinitions": [                     {                         "AttributeName": "id",                         "AttributeType": "S"                     },                     {                         "AttributeName": "educationSchoolId",                         "AttributeType": "S"                     },                     {                         "AttributeName": "educationMentorId",                         "AttributeType": "S"                     },                     {                         "AttributeName": "educationMenteeId",                         "AttributeType": "S"                     },                     {                         "AttributeName": "memberEducationId",                         "AttributeType": "S"                     },                     {                         "AttributeName": "menteeEducationId",                         "AttributeType": "S"                     },                     {                         "AttributeName": "mentorEducationId",                         "AttributeType": "S"                     }                 ],
So indeed, amplify is trying to add three new attributes at once, though I have no idea as to why, let alone how to resolve the issue. Any help would be greatly appreciated.

Hi @ldaudet, Could you please check if "respectprimarykeyattributesonconnectionfield" is set to true or false in cli.json file.
Please set it to false and re-try the migration and let us know.

Hi @AnilMaktala , I didn't have that key set in my cli.json, but checking into it, it seems to be false by default. I did add it just in case, and then run the amplify api push command. The command went ahead and failed like the previous ones, and for the same reason: "Cannot perform more than one GSI creation or deletion in a single update"
I am going to recap the issue here, in the hope that it might help you find a solution:

I update the schema of my application manually to be using version 2 of the graphql transformer (as the amplify update script didn't work)
I set the cli.json file to have enableIterativeGSIUpdates set to true
I ran amplify api push
this command created 13 different step for the push, and uploaded the files to the deployment bucket for the app
the push went through the initial step, step 1, step 2, step 3, and then stopped. No errors, no crashes, just nothing happening for over an hour, both on the command line window where amplify api push was running, and checking the deployment-state.json file on the S3
I stopped the amplify api push command
I ran amplify api push command again and got an error that a push was already in progress
I stopped working for the day, to let some time for whatever process to finish
tried amplify api push again the next day, and got the same error. I then realized that was because of the deployment-state.json file on S3
I deleted the deployment-state.json file on S3 and tried amplify api push again. It crashed because "Cannot perform more than one GSI creation or deletion in a single update"
after a lot of searching, I figured that the issue is that the initial push did went through for the first 4 steps. Now the problem is that the amplify pull command does not actually pull the state of the backend but instead pull the #current-cloud-backend.zip file from the deployment bucket. BUT that file only gets updated at the end of a push, not after each step. So now, I have a backend that is SEEN by amplify as being in its original, V1 state, a backend that is ACTUALLY 4 steps into a V2 migration, and now way to connect the two...

So, from there, I am not sure where to go. As I see it, there are two possible ways to fix this, neither of which I know how to get done:
Solution 1: I somehow revert the backend to its original state and attempt the push again. There are two problems with that solution. First, I don't know how to revert the backend to its original state as amplify push --iterative-rollback didn't work. Second, if the iterative push stalled on the fourth step last time, I am not sure why it would work any differently this time.
Solution 2: I have amplify push the ACTUAL state of the backend, from the actual resources in cloud formation, so it knows what the state of the backend truly is, so that I can try amplify api push again, but skipping the first 4 states that have already been deployed.
If I can provide any other details on the issue, please don't hesitate to ask. Thank you for your help.

Hi @ldaudet, I'm sorry to hear that the recommendation we provided did not solve the issue. Would it be possible for you to share the schema or the diagnose report.zip file with me through the community Discord server?


banner tool for Tamil.

Provide a tool like Linux command banner for Tamil text
It should take one or more sentences from command line, or a file(s) and generate a vertical banner on terminal using ASCII characters like #, &, (,)_,-:;, etc.

Good model is to use Rajaraman's style :http://dev.neechalkaran.com/p/ascii-tamil.html
──────o─────o
─╔╦──║─║║─║╔╦
╔╬╬╦─║─║║─║║║
╚═╝╠╗╚═╝╚═╝║║
╚═══╝───────╝


First version of user documentation.

Based on the work by @curiosity54 and @HowWeiBin this PR adds a first version of a user documentation. The structure is similar to rascalines but of course with different content.
If you review take a close look at the general structure since the content is in a rough state.

Closing in favor of #91


Bag of bits

This is kinda partly due to me flailing around. I just wanted to get some of the helper bits I've been fiddling with reviewed before I get too far away from things. Hopefully this will all settle down once we've got into a pattern of how we're going to manage our data flow.

I manually checked this compiled on the branch with the rest of my outstanding change stashed.


incsearch not working

FAQ

[X] I have checked the FAQ and it didn't resolve my problem.

Issues

[X] I have checked existing issues and there are no open or closed issues with the same problem.

Neovim Version
0.7.0
Minimal reproducible full config
if !exists('g:loaded_cmp') | finish | endif

set completeopt=menuone,noinsert,noselect

" Use <Tab> and <S-Tab> to navigate through popup menu
inoremap <expr> <Tab>   pumvisible() ? "\<C-n>" : "\<Tab>"
inoremap <expr> <S-Tab> pumvisible() ? "\<C-p>" : "\<S-Tab>"

lua <<EOF
  local cmp = require'cmp'
  local lspkind = require'lspkind'

  cmp.setup({
    snippet = {
      expand = function(args)
        require('luasnip').lsp_expand(args.body)
      end,
    },
    mapping = cmp.mapping.preset.insert({
      ['<C-d>'] = cmp.mapping.scroll_docs(-4),
      ['<C-f>'] = cmp.mapping.scroll_docs(4),
      ['<C-Space>'] = cmp.mapping.complete(),
      ['<C-e>'] = cmp.mapping.close(),
      ['<CR>'] = cmp.mapping.confirm({
        behavior = cmp.ConfirmBehavior.Replace,
        select = true
      }),
    }),
    sources = cmp.config.sources({
      { name = 'nvim_lsp' },
    }, {
      { name = 'buffer' },
    }),
    formatting = {
      format = lspkind.cmp_format({with_text = false, maxwidth = 50})
    }
  })

  vim.cmd [[highlight! default link CmpItemKind CmpItemMenuDefault]]
EOF

Description
Found that this commit breaks incsearch and inccommand=split:
https://github.com/hrsh7th/nvim-cmp/commit/5054c14
I rolled back to bba6fb6 for now.
Steps to reproduce

Hit / and type words.

Or,

Hit :%s/ and type words.

Expected behavior
nvim should highlight matched text as you type without hitting the return key.
Actual behavior
not highlighting
Additional context
Thanks for the great plugin🙏

Thank you! I'll check it.

Can confirm I also have this problem.

Can confirm I also got the problem (and like 3 other people I talked with got it as well)

I did a binary search, and found out that the cause are some of the extension plugins, in particular:
hrsh7th/cmp-buffer
f3fora/cmp-spell
andersevenrud/cmp-tmux

What's interesting is that hrsh7th/cmp-nvim-lsp didn't introduce the issue.
By the way, I commented out all setup functions, so just loading a plugin seem to be sufficient.


[ItemList] No way to get/set columns titles

Godot version
ba54c34551d1bda5139515d74e7d614ccbc43cea
System information
macOS Macbook Pro M1
Issue description
There is no functionality in ItemList (a GUI component) to set column titles.
I want to create an ItemList with 3 columns and have their titles visible.
Tree GUI componenet however, does have this functionality.
Steps to reproduce
Create ItemList.  Can't create columns.
Minimal reproduction project
None

This should be a proposal as it's not a bug but a potentially missing feature

This should be a proposal as it's not a bug but a potentially missing feature

Thanks, proposed:
https://github.com/godotengine/godot-proposals/issues/7707


Add proposal for lookups

What is the context of this PR?
This proposes how lookups might be represented in a survey schema.
How to review

See if you think the proposal makes sense.
Is there anything I've missed?

I had pondered whether including a limit for the number of results to display might be appropriate?

I think when this was initially discussed, we talked about having the ability to avoid using a lookup api for simple lookups, i.e. where there are not many options. Obviously there are some disadvantages to this, so I assume this was ruled out?

@bitdivision - don't remember that conversation, but I guess that's still an option if we set a flag to indicate the query_path will come from runner host itself?

@bitdivision I think the intent of the lookup has changed as it's gone through user testing. The current design/prototype is for the suggestions from the lookup to behave more like a search than an autocomplete. If we weren't using the api we'd end up having to have two implementations of that, one client side and another in the api.

I think when this was initially discussed, we talked about having the ability to avoid using a lookup api for simple lookups, i.e. where there are not many options. Obviously there are some disadvantages to this, so I assume this was ruled out?

Presumably all the look ups need to behave the same regardless of the number of entries in the datasets? Unless a simple lookup could replicate the behaviour of an elasticsearch api (e.g. partial tokenized matches etc) then it might impact the user experience.

Does path_to_query need to live in the schema?. Have we considered a lookup_type option instead?

@MebinAbraham Regarding the number of items shown, we discussed this briefly yesterday and I think the conclusion was that there should be one number which makes sense for all devices and that number can be chosen by the product owner. There shouldn't ever be a need to modify it on a per schema basis.


Mod mail integrated with the api

The modmail should be integrated with the api making use of the mod mail boolean field.

This is already in issue #88


doc: add meeting notes 2023-02-06

Signed-off-by: Ulises Gascon<EMAIL_ADDRESS>Co-authored-by: Yagiz Nizipli<EMAIL_ADDRESS>Co-authored-by: Marvin Hagemeister<EMAIL_ADDRESS>

@nodejs/performance


Remove postgres, implement Pizza Tracker

Postgres was unused and so is being removed
Pizza Tracker for processors was not fully implemented; with this update python processors that support Pizza Tracker will start a subprocess that runs the tracker, and the tracker has been updated to handle buffering commands from the named pipe and continuing to read until END is read.

tested and verified

LGTM


FadeOut and transparency

When fading out a composed Mobject (i. e. containing submobs), the pixels fade to black instead of the color of the mobject hidden behind it.
from helpers import *
from mobject import Mobject
from mobject.vectorized_mobject import *
from animation.animation import Animation
from animation.transform import *
from animation.simple_animations import *
from topics.geometry import *
from scene import Scene
from camera import Camera

class SampleScene(Scene):

    def construct(self):

        lines = Mobject() # VMobject()
        line1 = Line(LEFT, RIGHT)
        line2 = Line(UP, DOWN)
        lines.add(line1, line2)

        rect = Rectangle(fill_color = BLUE, fill_opacity = 1)

        self.add(lines)
        self.add(rect)

        self.wait()

        self.play(FadeOut(lines))

Result:

This does not happen in the exported PNG, and also not if lines is instantiated as a VMobject.

Actually, the lines are fading out into the background color only. Since you are "adding" the lines to the screen, they are becoming visible in the end . Just write self.wait(5) after the fadeout statement to observe that lines fadeout to background color . Hope this helps you .Knidly  can you close the issue as it no longer exsists..


Added files

Hello, I think you made this Pull request by mistake. You have also published the .env file with the MapTiler api key. It is not recommended to publish .env files on GitHub and if you do, ensure to protect your key per domain. Here, you can see how to protect your key https://documentation.maptiler.com/hc/en-us/articles/360020806037-How-to-protect-your-map-key.
I also recommend replacing your default password since it has been leaked.

Hello @CS50X-RGB , I think you made this Pull request by mistake. You have also published the .env file with the MapTiler api key. It is not recommended to publish .env files on GitHub and if you do, ensure to protect your key per domain. Here, you can see how to protect your key https://documentation.maptiler.com/hc/en-us/articles/360020806037-How-to-protect-your-map-key.
I also recommend replacing your default password since it has been leaked.

Yeah sorry it was for my personal project sorry 😅


Automated docker build

Adds automated docker builds on push to master

I don't mind merging, but I can't maintain. Build failed, feel free to troubleshoot and open another PR: https://github.com/coracle-social/dufflepud/actions/runs/4555757142

You need to give permissions to actions to read/write in settings > actions > general

I think that's already done, see below.

Its this one, to do with GITHUB_TOKEN

That's grayed out for me, and it's not immediately obvious how to enable it:


Fix CF destroy by unpacking certificates for tf

What
This appears to have been broken since we added ELB's with certificates on them for metrics etc, but nobody noticed as we rarely totally destroy cf environments.
How to review
Run the destroy pipeline. It should succeed.
Who can review
Not @jonty or @timmow.

Destroy now works again...


Feature/621 make dates required

Pull Request

Made beginDate and endDate required
Commented out date-validation.pipe.ts and replaced it with custom decorators:

is-iso-format.pipe.ts
is-valid-date.pipe.ts
is-in-date-range.pipe.ts

Removed "endDate >= beginDate" validation from the service and replaced it with a custom decorator:

is-date-greater.pipe.ts

If user enters invalid format, invalid date, or a date that is out of range, the system shall return a list of all the date validation errors it failed

Previously it would only return one date validation error with the priority being format>valid date>range
But now all three validations will be checked (and not short circuited)

If the user does not input a beginDate or endDate, the system shall only return this error message:

"[insert property] should not be null or undefined"
It will not return the format, valid date, or range error messages, as there is no value provided to validate

updated date-range decorator to accept a min and max date
updated error messages per requirements
added swagger plugin

updated date-range decorator to accept a min and max date
updated error messages per requirements
added swagger plugin


[BUG] Add validations on signup

Description
I want to add multiple validations on sign up page. Please assign me this issue.
Screenshots
No response
Browser 🥦
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no)

Hi @Rishita1304 , this has already been done here do take a look.
Please refrain from raising duplicates.


CPU overloading

@KromDaniel Any chance you want to re-commit your great code that overloads the CPU using a spawned process?
If no time to perform the adjustments, I can do it easily, just share the code
p.s. I'm coming to hear you speak next week!

@i0natan  sure, I need some time to remember what happened there :)
p.s, I'm coming to hear you speak next week also!!

@KromDaniel You submitted a PR, I suggested a minor change and you pulled it for edits. I suggest you just re-submit it, we can fix together - it's one line of code.
p.s. I want to present this tool in the testing session next week as a project both presenters contributed to :]


with doesn't play nicely with withSchema

Related to #1599 - I'm using Knex (awesome btw!) with Postgres and attempting to use CTEs through the with method, but I'm not having all that much luck.
var db = knex.widthSchema('schemaName');

await db
  .with( 'tTwo', qb => {
    qb.select( '*' ).from( 'tableTwo' );
  } )
  .select( 'col1', 'col2' )
  .from( 'tableOne' )
  .leftJoin( 'tTwo', 'tableOne.id', 'tTwo.id' )
  .groupBy( 'id' )

Results in SQL such as:
with "tTwo" as (
  SELECT * FROM "tableTwo"
)
SELECT "col1", "col2"
FROM "schemaName"."tableOne"
LEFT JOIN "schemaName"."tTwo" ON "tableOne"."id" = "tTwo"."id"
GROUP BY "id"

There are two issues with the generated SQL:

I would have expected the table in the with statement to have inherited the schema name from the host. Instead it is defaulting to the public schema resulting in an error unless I add the schema name there as well.
The left join name should not be prefixed by the schema name - it should just be "schemaName"

I haven't looked at the code base yet, so I'm not sure what is involved in changing these, but are these two issues that I've mentioned valid and correct? If they are I'll take a look and see what I can do to implement them.
Thanks!

@DataTables The withSchema() only works for the table of the FROM clause. Knex cannot implicitly guess if the join table need or not to be prefixed.
IMO, you have to
await knex
  .withSchema('schema')
  .with( 'tTwo', qb => qb.select( '*' ).withSchema('schema').from( 'tableTwo' ) )
  .select( 'col1', 'col2' )
  .from( 'tableOne' )
  .leftJoin( 'tTwo', 'tableOne.id', 'tTwo.id' )
  .groupBy( 'id' )

or simply,
await knex
  .with( 'tTwo', qb => qb.select( '*' ).from( 'schema.tableTwo' ) )
  .select( 'col1', 'col2' )
  .from( 'schema.tableOne' )
  .leftJoin( 'schema.tTwo', 'tableOne.id', 'tTwo.id' )
  .groupBy( 'id' )

Thanks for the reply!
I agree - best way is just to write the query a little more explicitly.


Feature 20171213 ConcatDataSource

ConcatDataSource is DataSource wrapper for multiple DataSources.
Using some DataSources, it's better that they behave like as single DataSource.
This will be effective for using different format data sources as the same time.

@YukioOobuchi Can you review and merge?


[Feature Request]: Signed cookies?

Package
lucia
Description
I'm wondering if there should be support for giving Lucia constructor a secret that will be used for signing and unsigning cookies?

Duplicate of #1156


Damerau-Levenshtein edit ratio Evaluator

Adds dlratio as an option for -validaion_metric.  Implemented so that it counts the DL edit distance for each (prediction, reference) pair (as strings), then divides the total number of edits across all pairs by the total length in characters of all reference strings.

Codecov Report

Merging #326 into master will decrease coverage by 0.02%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #326      +/-   ##
==========================================
- Coverage   70.78%   70.75%   -0.03%
==========================================
  Files          68       68
  Lines        5637     5639       +2
==========================================
  Hits         3990     3990
- Misses       1647     1649       +2

Impacted Files
Coverage Δ

onmt/train/Trainer.lua
22.61% <33.33%> (-0.19%)
:arrow_down:

Continue to review full report at Codecov.

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

Hi @dblandan - thanks for this contribution. Can you please add a unit test also - see https://github.com/OpenNMT/OpenNMT/blob/master/test/onmt/BleuTest.lua. Thanks!

Hi @jsenellart - unit test added.  Cheers!

Thanks!

Happy to do it.  Thanks, guys!  :smiley:


Storybook github actions

Description
Creating github action that publishes storybook to github pages on every merge to main branch. Use the metamask/action-publish-gh-pages repo https://github.com/MetaMask/action-publish-gh-pages

Updating storybook version

@shanejonas Haaaaalp 😢


[SPARK-48086][PYTHON][TESTS][3.5] Remove obsolete comment

What changes were proposed in this pull request?
This PR proposes to remove those comments for skipped tests related to different Arrow version in JVM.
Why are the changes needed?
Arrow version incompatibility is something we cannot avoid. We should just skip those tests for now.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Linters.
Was this patch authored or co-authored using generative AI tooling?
No.

Merged to branch-3.5.


fix: improve transaction cost estimation for pay modal

Problem solved
fixes CNCT-2514

#5548  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Support literal constants in typing of object methods

Adds a support_literals argument to bound_function to enable passing literal constants to typers of object methods.

Codecov Report

Merging #3189 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3189      +/-   ##
==========================================
- Coverage   81.13%   81.13%   -0.01%
==========================================
  Files         384      384
  Lines       75151    75152       +1
  Branches     8438     8438
==========================================
- Hits        60977    60975       -2
- Misses      12884    12886       +2
- Partials     1290     1291       +1

I think this change is trivial enough and testing it is troublesome enough that i'm ok if it isn't tested.

Thanks @sklam . I agree. I tested it manually and don't see any problems.


global: ils exceptions

created new ils exceptions
use new circulation exceptions
fixed tests
addresses #193

This one requires depends on this https://github.com/inveniosoftware/invenio-circulation/pull/102 to be merged and released first.


Surprising pipenv install behaviour regarding the lockfile

I'm afraid I the pipenv.help command couldn't find pipenv, so I couldn't run it. I'm running v10.1.2, and I was very surprised to see that pipenv install does not use the lockfile by default! This led to a crash where my package could not be installed, as pipenv install on the end user's machine tried to upgrade the lockfile and broke. pipenv install --ignore-pipfile worked fine, but it was extremely surprising to me that this wasn't the default.
Basically, I consider pipenv install without any arguments to be a distribution-time command, ie it will be run when I want to distribute my package and install all the requirements. I would expect this to use the lockfile, if available.
I realize that pipenv install <somepackage> is a development-time command, breaking symmetry, but the way I imagined things working regarding the lockfile was that a command like pipenv install <package> would change both Pipfile and Pipfile.lock, a command like pipenv lock or pipenv upgrade would upgrade packages in the lockfile, and a command like pipenv install would use that lockfile to install packages.
I think many people will be bitten by the surprising default behavior of pipenv install to not only not use the lockfile, but to upgrade it as well, and the main problem is that nobody will realize what's happening until stuff blows up.
If you won't consider changing pipenv install to use the lockfile, maybe a separate command could be added.
I just now realized that pipenv sync is close to what I want, but it seems to be an alias for pipenv install --keep-outdated. Does that mean that new versions of the packages will be installed, but the lockfile won't be changed? That's what "Keep out–dated dependencies from being updated in Pipfile.lock." seems to imply, ie that it will install the new dependencies but won't touch the lockfile. Also, pipenv sync doesn't seem to use the Pipenv file if a lockfile does not exist.
To sum up, I am concerned that the commands are, at least, not documented well enough/a bit unclear. What is the recommended way, currently, of using the lockfile if it exists, or the Pipfile otherwise?

Another problem of the sync command is that it doesn't work with --system, making it unsuitable for Dockerized deployments. Basically, the most useful thing is a command that would run pipenv install --ignore-pipfile if a lockfile exists, or pipenv install otherwise.

... that’s what install does.
What makes you think otherwise?
Sent from my iPhone

On Mar 9, 2018, at 9:42 PM, Stavros Korokithakis<EMAIL_ADDRESS>wrote:
Another problem of the sync command is that it doesn't work with --system, making it unsuitable for Dockerized deployments. Basically, the most useful thing is a command that would run pipenv install --ignore-pipfile if a lockfile exists, or pipenv install otherwise.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

But only if the lockfile is up-to-date.
Sent from my iPhone

On Mar 9, 2018, at 9:47 PM, Kenneth Reitz<EMAIL_ADDRESS>wrote:
... that’s what install does.
What makes you think otherwise?
Sent from my iPhone

On Mar 9, 2018, at 9:42 PM, Stavros Korokithakis<EMAIL_ADDRESS>wrote:
Another problem of the sync command is that it doesn't work with --system, making it unsuitable for Dockerized deployments. Basically, the most useful thing is a command that would run pipenv install --ignore-pipfile if a lockfile exists, or pipenv install otherwise.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Then, in that instance, it re-locks before installing... from the lockfile.
Sent from my iPhone

On Mar 9, 2018, at 9:47 PM, Kenneth Reitz<EMAIL_ADDRESS>wrote:
... that’s what install does.
What makes you think otherwise?
Sent from my iPhone

On Mar 9, 2018, at 9:42 PM, Stavros Korokithakis<EMAIL_ADDRESS>wrote:
Another problem of the sync command is that it doesn't work with --system, making it unsuitable for Dockerized deployments. Basically, the most useful thing is a command that would run pipenv install --ignore-pipfile if a lockfile exists, or pipenv install otherwise.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

That's kind of the problem, what do you mean "if it's up to date"? I don't want to lock my dependencies when developing, push that to dev, test and push to production, only to find that there's a new, incompatible version of some package, and the production server arbitrarily decided to install that one.
Basically, if there's a lockfile, and pipenv deletes it, creates a new one and then installs from that, there's basically no lockfile. What's the use of a lockfile if it's only used when it's not needed?

You want install --deploy

No, I don't want it to abort. Consider this scenario: I developed, tested, froze all my dependencies, etc. Now, a month later, when all the red tape has been cleared, I want to deploy what I tested, with all the dependencies I used when testing, etc to production. I don't want pipenv to upgrade anything, I don't want it to fail if there are new packages: I want it to install the exact versions, to the byte, of what's in the lockfile.

A lockfile contains the hash of the pipfile that generated it. If the hashes don’t match, it’s invalid, and needs to be re-created as soon as possible.

E.g. a lockfile is a cached result of a pipfile. They change together.

Oh, is that what you mean by "out of date"? If so, I agree. I hadn't touched the Pipfile, though. Maybe I'm mistaken (and I don't have my scrollback buffer to paste any more), but what I saw happen was that pipenv updated my lockfile even though I hadn't touched the Pipfile.
For my clarification, is pipenv install ever supposed to change the lockfile based on the versions of the packages on PyPI? Or will it always use the lockfile if the Pipfile hash matches?

A bare pipenv install will always use the pipfile.lock, if the hashes match.

Ah, thanks. Then I'm either mistaken (most likely) or there's a pipenv bug. I'll close this issue and open another one with more information if I manage to reproduce my earlier experience. Sorry for the hassle and thanks for the clarification.

Thanks for the due dilligence!


streamlines filter

Resolve #198
This adds a .streamlines() filter that will integrate a vector field to generate streamlines.
Todo:

[ ] Document the filter
[ ] Add parameter descriptions

@JiaweiZhuang: would you look over these changes and provide feedback?
Example A:
import vtki
from vtki import examples
mesh = examples.download_carotid()

streamlines = mesh.streamlines(max_time=100.0,
                           initial_step_length=2., terminal_speed=0.1,
                           n_points=25, source_radius=2.0,
                           source_center=(133.1, 116.3, 5.0) )

p = vtki.Plotter(notebook=1)
p.add_mesh(mesh.outline(), color='k')
p.add_mesh(streamlines.tube(radius=0.15))
p.add_mesh(mesh.contour([160]).wireframe(),
           color='grey', opacity=0.25)
p.camera_position = [(182., 177., 50),
                     (139, 105, 19),
                     (-0.2, -0.2, 1)]
p.show()

Example B:
import vtki
from vtki import examples

mesh = examples.download_blood_vessels().cell_data_to_point_data()
mesh.set_active_scalar('velocity')

streamlines, src = mesh.streamlines(return_source=True, source_radius=10,
                           source_center=(92.46, 74.37, 135.5) ,)

boundary = mesh.decimate_boundary()

p = vtki.Plotter(notebook=1)
p.add_mesh(streamlines.tube(radius=0.2), ligthing=False)
p.add_mesh(src)
p.add_mesh(boundary, color='grey', opacity=0.25)
p.camera_position = [(10, 9.5, -43),
                     (87.0, 73.5, 123.0),
                     (-0.5, -0.7, 0.5)]
p.show()

Note that I had to convert the blood vessel dataset to point data:
mesh = examples.download_blood_vessels().cell_data_to_point_data()

I have no idea why, but this implementation currently does not handle vector field on the cells of a mesh... ParaView has no issue with it so I wonder what's different? Maybe they're running a cell data to point data filter behind the scenes?

Thanks for such fast work!

would you look over these changes and provide feedback?

I am able to reproduce your plot at test_streamlines.ipynb Looks great. No major things to add.

I had to convert the blood vessel dataset to point data

Yeah that's weird. mesh.cell_centers().streamlines() also gives empty data. "Cell data" vs "point data" is something that confuses me a lot in VTK. While mesh.points is the 3D coordinate of grid points, mesh.cells is an array of integer indices, referring to the point array. It's size is 9 * n_cells which I am not sure how to interpret it (see the below screenshot from the notebook). Maybe such information is insufficient for computing the streamlines.

I want to point out that this is an awesome demonstration of vtki's benefit - "Example A" above using the carotid dataset is a replica of this example from VTK. Note that with just the VTK package, this takes about 80 lines of code while with vtki, this takes 10 lines of code to make the same exact 3D scene (not including comments or line breaks for code style/readability)

@JiaweiZhuang:

mesh.cell_centers().streamlines() also gives empty data ... Maybe such information is insufficient for computing the streamlines.

That should be expected because the cell_centers() filter returns vertex cells of all the cell center locations - a vertex cell is just a point in 3D space which doesn't have an area or volume associated with it - thus it cannot be integrated by the vtkStreamTracer filter

Cell data" vs "point data" is something that confuses me a lot in VTK. While mesh.points is the 3D coordinate of grid points, mesh.cells is an array of integer indices, referring to the point array. It's size is 9 * n_cells which I am not sure how to interpret (see the below screenshot from the notebook).

This is fair - we haven't documented the difference between point and cell data very well in vtki and it's not very intuitive to new VTK users (hence the reason for #161). In brief, the difference comes down to where in space your scalar/vector values live - cell data means the entire cell (2D triangle, 3D voxel, 3D hexahedron, etc.) is associated with your data (scalar array or vector), while point data means the scalars or vectors live on the nodes of the mesh and not the cells (nodes are the points that make up a cell's extent). When rendering, if plotting the cell data, the entire cell's color is mapped to its value and when plotting point data, cells colors are interpolations of the values at all the nodes of that cell:
import vtki
from vtki import examples

mesh = examples.load_uniform()

p = vtki.Plotter(shape=(1,2))
p.add_mesh(mesh, scalars='Spatial Cell Data', show_edges=True)
p.subplot(0,1)
p.add_mesh(mesh, scalars='Spatial Point Data', show_edges=True)
p.show()

In vtki, we've mostly kept this hidden from users to avoid confusion but the difference is really important for VTK and when trying to visualize data resolution.
As for the points and cells properties on the meshes, this is something that needs updating in the docs... the points property is simply the nodes of the mesh in 3D space - the cells simply connect the points in a specific order to create a volume or surface, etc.
As for why the cells array is 9 times the length of your number of cells, this is because you have a mesh where all of the cells are of the same type and defined by 8 node locations (the points of the voxel) - the 9th element comes from having to separate the cell indices to make individual cells.
The mesh.cells array comes directly from VTK and has a structure where the first value (8 in your case) tells you how many indices make that first cell (8 indices) then the following n (8 again) elements in that array are the indices of the points/nodes array that make that cell.
note that the cells property is only available on vtki.UnstructuredGrid class - why might want to make a more universal implementation
# using init snippet above
mesh = mesh.cast_to_unstructured_grid()

print(mesh.cells[0:9])

[  8   0   1  10  11 100 101 110 111]

last_cells_nodes = mesh.points[mesh.cells[-8:]]

p = vtki.Plotter()
p.add_mesh(mesh, show_edges=True)
p.add_mesh(last_cells_nodes, point_size=10)
p.show()

@banesullivan Thanks for this detailed explanation; this makes it much clearer!

cell data means the entire cell (2D triangle, 3D voxel, 3D hexahedron, etc.) is associated with your data (scalar array or vector), while point data means the scalars or vectors live on the nodes of the mesh and not the cells (nodes are the points that make up a cell's extent).

Yeah this is also what I imagined. Point data are like finite difference grids and cell data are like finite volume grids.

As for why the cells array is 9 times the length of your number of cells, this is because you have a mesh where all of the cells are of the same type and defined by 8 node locations (the points of the voxel) - the 9th element comes from having to separate the cell indices to make individual cells.

Thanks for the clarification. I naively expected that mesh.cells would also return some sort of coordinate values, like ``mesh.points` does.


Lets keep is_reversed_score as a potential valid input argument to avoid breaking changes

https://github.com/jina-ai/jina-hub/blob/d89bc5e8f527f1212c3228a15775e222983c0087/rankers/SimpleAggregateRanker/__init__.py#L23
Lets add with deprecation warning the possibibility to use the old set of arguments.

Can we use deprecated_alias in hub?

Can we use deprecated_alias in hub?
#4146

Yes

@Yongxuanzhang is this closed?

@Yongxuanzhang is this solved?

Yes. But just realize that should we add a test to it? If so, I will add a test accordingly

@Yongxuanzhang is this solved?

Yes. But just realize that should we add a test to it? If so, I will add a test accordingly

let's add it

@Yongxuanzhang is this solved?

Yes. But just realize that should we add a test to it? If so, I will add a test accordingly

let's add it

Sure! I will do it today!


Cannot handle a message that does not have a handler bound

Currently sending a message that has not been registered will throw an exception. Instead make this configurable so that this can be handled and a custom action taken instead.

You can now register a handler for the NoMatchingRegistrationEvent event.


question about dataset?

There are some files which are missed in the data.

Could you please provide these files so that I can follow your step?
Thanks very much.

Sorry for the late response. Please use the latest version of download.sh to download the data and check if the files are still missing. I double-checked that it contained the three missing files that you mentioned. Thank you!
$ ./download.sh

...

$ ls -lha data/yelp-default
total 2.0G
drwxrwxr-x 2 suhara suhara 4.0K Oct  6 17:53 .
drwxrwxr-x 3 suhara suhara 4.0K Oct  6 17:55 ..
-rw-r--r-- 1 suhara suhara  45M May  6  2020 dev.csv
-rw------- 1 suhara suhara 609K Nov 27  2019 summaries_0-200_cleaned_fixed_business_ids.csv
-rw-r--r-- 1 suhara suhara  46M May  6  2020 test.csv
-rw-r--r-- 1 suhara suhara 765K May  6  2020 test_gold_8_15_all_all_300_8.csv
-rw-r--r-- 1 suhara suhara 832K Oct  5 23:06 test_gold.csv
-rw-r--r-- 1 suhara suhara 363M May  6  2020 train.csv
-rw-rw-r-- 1 suhara suhara 1.6G Nov 28  2019 yelp.jsonl

Dear author, I would like to inquire about the three files generated during the aggregation process. Could you please explain the purpose and content of these files? I would greatly appreciate your assistance. Thank you!


Throw EUNPLUGGED if the drive gets unplugged during write/validation

In Windows, this error is ENOENT, in macOS, the error is ENXIO, and in
GNU/Linux, the error is EIO.
See: https://github.com/resin-io/etcher/issues/1124
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

I'll merge this so we can release today, but happy to address any review comments later.


Remove version from ObjectRef?

Pros:

The version is not counted for K8s object identity, Deployment.v1.apps/foo and Deployment.v1beta1.apps/foo refer to the same backend object

Downsides:

They're not represented the same in the client
Some APIs (like https://docs.rs/k8s-openapi/0.9.0/k8s_openapi/apimachinery/pkg/apis/meta/v1/struct.OwnerReference.html) inexplicably use versioned references
We need it if we ever want to allow using it to perform dynamic queries

Yeah, the api still require the version field passed in the url, and AFAIK Deployment.v1.apps/foo and Deployment.v1beta1.apps/foo cannot coexist, so there must be some magic in this area.
How does kubectl deal with dynamic queries? I thought it would do it opportunistically by trying the latest versions first.
Have not actually dug into the source for this though.

AFAIK kubectl downloads the entire API surface and then does its own sorting heurestics. It generally works fine.. until it goes hilariously wrong, like how it would prefer Deployment.v1beta1.extensions over Deployment.v1.apps, all the way until extensions/v1beta1 was finally dropped.

In light of recent PRs and thinking; if we are going to support the runtime features around dynamic objects (like out of the api-resources api), it's only necessary to do the lookup of version once, then fix it for any runtime usage (which will allow users to select how they pick versions in case of ambiguous Deployment versions say).
I think if we get in #385, it will solve the problems with dynamic queries.


support for when WP is loaded over https but site URL and home are http

When https the admin site is loaded over https, but the WP site URL and/or home are http, the plugin tries to load frontend assets over http, which is blocked by insecure warning.
The crawling will likely also not work properly.

On version 7, I ran into the certificate error for curl. In src/SitemapParser.php, I changed this line
$client = new WP2StaticGuzzleHttp\Client();

to this
$client = new WP2StaticGuzzleHttp\Client(['verify' =>false]);

Crawling already works. See https://github.com/WP2Static/wp2static/blob/0e6e23f597dcb6e20148b373c23ee48d71b0ad68/src/Crawler.php#L61
The only thing that doesn't work with a self-signed SSL certificate is the SitemapParser.


ci: Disable presubmit LLM tests temporarily

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

LGTM although is LLM capacity the only ML capacity we ran up against?

I guess merging this will help answer that question!

LGTM although is LLM capacity the only ML capacity we ran up against?

I guess merging this will help answer that question!

Yeah, we were wondering about the slot reservation but it seems we are well within the capacity https://screenshot.googleplex.com/5VDoK8TXXsrLUtH

The presubmit test still took 1h17m
https://fusion2.corp.google.com/ci/kokoro/prod:bigframes%2Fpresubmit%2Fpresubmit/activity/d238d224-d057-4545-9500-11b99fefde5d/summary
I am reverting this change in https://github.com/googleapis/python-bigquery-dataframes/pull/148


External monitors blank starting with 9601a2a

https://github.com/swaywm/wlroots/commit/9601a2abf024fb8ac400c0df178bb41ec9e5d215 has brought back the issue with blank external monitors using intel+nouveau configuration:
https://github.com/swaywm/wlroots/issues/2526
WLR_DRM_NO_MODIFIERS=1 workaround is broken as well.

I'm also getting a few meson warnings. (I can open a separate issue for this if required.)
|WARNING: Project targeting '>=0.56.0' but tried to use feature deprecated since '0.56.0': meson.build_root. use meson.current_build_dir instead.

I'm using meson 0.57.1

The warnings are a Meson bug: https://github.com/mesonbuild/meson/pull/7772#issuecomment-775201986

Can you try https://github.com/swaywm/wlroots/pull/2788?

not OP but I also had the same symptoms: intel+nouveau, black screen since 9601a2a.
Can confirm with #2788 everything works again!


feat: Create scheduling Select Date Time page

Notion ticket link

Scheduling Flow - Select Date and Time

Implementation description

Add select date and time page that consists of the following components:

Calendar to select a date
Select daypart (Early morning, Morning, Afternoon, Evening, Night)
Select drop-off time
Select frequency
Enter proposed end date (only render if this is NOT one time donation"

Steps to test

Select a date in the datepicker. Only the dates for this week and next week can be selected. Everything else should be disabled.
Select a time of day
This should render the time slots. Each time slot should have icons representing number of ppl booked that slot.
Select frequency
Enter a proposed end date.
Validations?
Go to next page or go back and come back to this page. You should still see all the correct selected options.

Preferably, on the next page, do a console.log(formValues) and make sure all the formValues are correct.
https://user-images.githubusercontent.com/37950626/144347321-8915c538-7df4-4bdc-926f-86007f7a4494.mov

What should reviewers focus on?

Checklist

[x] My PR name is descriptive and in imperative tense
[x] My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
[x] I have run the appropriate linter(s)
[x] I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

looks good!! I think the reason the person icon isn't showing up in the deployed link is because assets can only be accessed in the public folder? (the pictures in the donation step don't show up either in the deployed link) but that can be fixed in a separate item


home icon doesn't link to index.html

Home icon from breadcrumbs trail doesn't link to index.html
Ask if bug.

resolves when published


direction: vertical why only from down to top?

Version
Tell us which versions you are using:

react-native-router-flux v3.38.0
react-native v0.44.0

Expected behaviour
I just have an gallery app and using swipe to reach the pictures or other parts of the app. What I only need is for example when I swipe down, I want to see the upcoming page from up to down(on the swipe direction). However, when I use the direction as vertical, the next page pops up from down to top which I dont want. Is there a sollution for it ? may be something like leftToRight as the opposite transition to horizontal??

I changed it on my own, in case someone needs, you can ask

@hasancanozkan Are you searching for the topToBottom option?
I only can't figure out how to close it by swiping up

if you use topToBottom, the reverse move is basically in the direction of swiping up, isnt it?


Refactor sphinx RST parsing in towncrier extension

Backport of https://github.com/ansible/pylibssh/pull/119
For now, no tests, or anything.

Not sure if I should continue to polish this PR or just know that it's there and when the code is a little more ready to accept contributions (with tests and all), we'll have an easy PR.

@ewjoachim I don't think I'll have any further refactoring requests. You may either update it yourself or I could do it for you. Either way, I'd like to accept it rather than postpone it.

Then be my guest :)

@ewjoachim thanks!

👍 Thanks to you !


feature-request: ORGiD SDK to support Goerli, Polygon, Gnosis Chains

The problem: Depracation
The network chains currently supported by the ORGiD SDK are:

Sokol xDAI Testnet
Arbitrum Rinkeby Testnet
Rinkeby Testnet (To be deprecated)
Ropsten Testnet (To be deprecated)
As indicated above Rinkeby and Ropsten are to be deprecated soon.

Feature Request
To forestall the deprecation of the chains above and increase the options of networks available,
can some or all of the following chains be included among the supported networks?

Goerli
Polygon
Gnosis Chains

Thanks!

I think it will be quite easy to implement it for Gnosis Chain and, maybe Goerli, but I am not sure about the Polygon.
We need to check if their evm has restrictions on the solidity compiler version. If not - we will be able to deploy contracts there without changes on the smart contract level. I need to discuss it with my team -  when it will be possible to pay attention on the ORGiD project.

This is very much appreciated. Thank you!

version 3.1.0 is already supported Goerli, Gnosis and Polygon nets


Organization and Application audience concept is not clear under the "Roles" config of an applicaition

Describe the issue:
$subject

How to reproduce:

Expected behavior:
Imporve the UX and descriptions to clearly denote what each type of role is
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

Duplicate of https://github.com/wso2/product-is/issues/17820


Sync upstream

I did:
git clone git@github.com:20treeAI/up42-py.git
cd up42-py/
git remote add upstream https://github.com/up42/up42-py.git
git remote -v   # to check it worked
git fetch upstream
git merge upstream/master

Then I noticed that the geopandas loose restriction was removed (but it was also the case in master branch surprisingly). So I brought back this change in a new commit.

Sync'd master with upstream via Github UI


Switch to CircleCI

We currently have Travis for our CI integration, but the Operation Code CI/CD pipeline uses CicleCI. We need to make the switch for everything to be easier on deployment.

This was fixed by #182


release a version?

@laglangyue, it's not functional yet but since there seems to be some interest I might put in a few hours when I can.


AVCaptureSessionPreset list

http://stackoverflow.com/a/31964333/1418457

iPhone 5 Front Camera because the device does not support AVCaptureSessionPreset1920x1080

iPhone 5 Can't add <AVCaptureDeviceInput: 0x1724d560 [Front Camera]> because the device does not support AVCaptureSessionPreset1920x1080. Use -[AVCaptureDevice supportsAVCaptureSessionPreset:].


Provide baseUrl to App to use in Vue-router

If I use a baseUrl in vue.config.js eg. '/directory1' i also must have base: '/directory1' when setting up vue-router otherwise it will route to '/'. I want to be able to reference baseUrl in my vue app so I can have
base: baseUrl
in my vue router setup.

See https://cli.vuejs.org/guide/mode-and-env.html#using-env-variables-in-client-side-code


within-time -> how to have timespan on certain days?

i would like to have time-events from within-time not every day, but only on SA or MO.
Is this possible? Do i have to calculate it somehow with jsonata or on the time-drop down?
How do it  have witin time from 12:00-13:00 only on Sunday?

Pete Scargills BigTime has some nice checkboxes for Days and Months.
within-time on  only on certain weekdays would be great1 👍

maybe time-compare could do it, but looks like overkill to filter on a SA
and no docu? How would i set this filter for certain days of a week?

i could maybe be solved with time-inject and gate-node as a filter on this,
but to use only a single  "within-time "-node itself as a gate would be more readable....
maybe you can show how to use within-time only on certain days...

I will add the day selection to the within-time node. But this will take some time.

Great! 🎉 🍪
should i come here to look for update? How do i check progress? Version updates?

seems complicated to trigger the blind-node on certains wwekdays.
at the moment looks like i have to send time-inject with Weekdays on the "msg.ts" but i have only two filter conditions (means 2 days). Or i must filter for simple weekdays condition even more complicated with  reg-ex? Or how is is designed to be done?

The selection of days is already planned for the next version.

info for me: consider #84 also for within-time node

implemented in<EMAIL_ADDRESS>

i updated, wonderfull!
thx for implementing it.
i personally like the full daynames,
shortened days to make it more compact...

OK, I will check if I can enhance the display in any of the next version. I have created a new issue --> #91

👍


Crop image on the server side

I have been surprised that I cant use the metadata provided by the "vue-croppa" to crop image on the server side, because its scale ratio calculates for its purposes and does not fit for original image.
Correct me if I am mistaken.

Guys, just set a prop "quality" equal to 1.


Multiple PerfEventVisitors in PerfEventProcessor, don't take ownership

PerfEventProcessor now suports multiple PerfEventVisitors and doesn't take
ownership of them, instead is passed bare pointers.

Thanks. From the code LGTM. Could you add in the commit message "why" we want multiple visitors and also that the owner will be the tracer-thread.
Meta-question:
Why is the tracer-thread the owner of the visitors and not the eventprocessor.

You're right, I specified both in the commit message. This is all for thread-state-related changes that will come at a later time.


add IF EXISTS

adding support for IF EXISTS conditionals in DROP TABLE and DROP MATERIALIZED VIEW as i just would have needed that.
would be great if you would consider adding this. if you would recommend any changes, please go ahead.

I'd love to have this but, as you may have noticed from the tests, we support c* 2.x. I'm open to options for how this might be made to support both new and old versions. However, I am not ready to give up support for the older versions just yet. (I have projects still on them. :) )

@pezra would it be feasible to configure the tests to not be run with cassandra 2x and update the documentation to reflect support with 3x?

I am not ready to drop support for the older versions just yet.
We could potentially detect which version of C* we are connected to and then only add the IF EXISTS when the C* version is high enough.

oh sorry, i did not mean to drop tests for old versions in general, just for this functionality! usually the way i would go about this is to add meta-data to rspec and than have a tag on the spec so that it will only be run for a match (in this case the cassandra version).

same goes for the documentation, i was just referring to the usage of that specific flag.

OIC... A CQL version tag on specs for newer CQL features is a good idea!.

@pezra added tagging for cassandra version, please take a look

👍 i like that approach to excluding those tests. I'll merge once travis completes and then we can the tagging on #353.

released in 2.1.0


Consider adding SFTP and SMB support

Hi, I recently discovered AnExplorer and I like it very much.
I don't know whether you accept feature requests or not, but it would be awesome if, other than traditional FTP and FTPS browsing, you could also add SFTP, and maybe SMB.

Also would like SMB


RFC: Degraded NodePool Status Condition

Description
See Design File for full RFC but this change seeks to add the Degraded status condition to NodePools in order to better communicate to users when a NodePool may be misconfigured.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.04%) to 81.259%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/expectations/expectations.go
2
94.81%

pkg/utils/termination/termination.go
2
92.31%

Totals

Change from base Build<PHONE_NUMBER>2:
-0.04%

Covered Lines:
9023

Relevant Lines:
11104

💛  - Coveralls

So in the case of utilizing Unknown, we'd still not have the new status condition be a pre-condition for readiness and then eagerly switch into Unknown... Yea, I think that makes sense as a third option and still leaves the possibility of it being able to affect functionality in the future if we want.
Flapping in and out of Unknown seems fine if we don't block provisioning for that NodePool. Do you see any disadvantages to changing the status condition from Unknown to True after a single success?


Log more error details in azure core

Need to continue working on serializer, jackson, util.

Overall I'm happy with the better logging just need to iron a few things.

/azp java - storage - ci

/azp run java - storage - ci

/azp run java - storage

/azp run java - core


Change attribute string in generator method, not in template

Sorry, I think a was a bit to quick to open a PR... while looking at the code again, I realized a better place to put that code would be in the generator, not in the template, as there is already a method called stimulus_attribute_value which changes the attribute string.
I was just about to change my PR, but it was already merged in... Sorry :worried:

Even better. Thanks!


Test code cov pr

What does this PR do?
What issues does this PR fix or reference?
Is it tested? How?

PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

Oops this was meant for my fork... please ignore.


implement monte-carlo methods

Great! Thanks!

Changes Unknown when pulling 6f10cccf7200cacafb40b57ecd4377497c0ea011 on amosbird:master into ** on Hoverbear:master**.


Add tree stories

#660

@LibbyUX I've changed the icon, it should be using the correct one now.
Question about keyboard navigation, do we still want the same behavior as in the FTU Explorer?

Hi @edlu77, yes please to the same keyboard tab functionality with the focus visible state.
Thanks so much for knocking this out!

@LibbyUX Made some updates and the keyboard navigation should be working now. Let me know if there are any other changes needed!

@LibbyUX Yes, that is the focus state. I agree it's a bit redundant since we already have a selected state which usually overrides it. You can only see this on expandable nodes that are clicked (since they can't be selected). I can remove the outline to make it cleaner.


Add Racial Equality banner to /web/ homepage

Adds the DevSite wide Racial Equality banner to /web/

:+1:


Add Leap and Tap to Place to Release Notes

Overview
Added Leap Motion support to the top of the release notes with a new gif and added Tap to Place.
Changes

Fixes: #7798

/azp run mrtk_docs


add DOI link for v0.9.1 in readme

@HealthyPear 0.9 contains a known important bug and was superseded very quickly by 0.9.1. So I think not including it is a sound decision.

Yes, the idea is that I will list only the "Stable" version of each major release (well minor using current numbering), so it will just be one link per 0.X release, with the latest patch number.  So for v0.9, it would be v0.9.1.
Semantic versioning implies that 0.9.1 is really the "0.9" release, but with some fixes.


Ambari service fixes

This includes some small bug fixes from 3.5.0:

Use 3.5 CDAP repositories
Explicitly check for debian/ubuntu and fall-back to RPM-based install (reverse logic)
recursive=True is create_parents=True in Ambari 2.4

LGTM


[Auto-conversion] - Bare bones version (taken from #346)

Use Case
As a user with data from a supported simulation engine, I want to load a file from the external engine without having to convert in Python first, and instead provide my data through a UI. This version will only include the:

engine type
file
trajectory name? (we could just display the file name)

Acceptance Criteria
File(s) from any of the simulation engines supported by simulariumio can be loaded locally in the Viewer
Any additional information needed from the user but not contained in the file(s) can be entered in a UI

[x] #394
[ ] #395
[ ]  Include trajectory file name ?

User feedback and control

[ ] #390
[ ] #389
[ ] Implement general failure error message modal
[ ] #408
[ ] #387

@lynwilhelm please review the second section and delete any issues you don't think are needed for the bare bones version

@interim17 @meganrm @blairlyons
I added a new section to the designs with just 2 slides to show what an "MVP" version would look like. You can find the link for it on the first Table of Contents page. https://xd.adobe.com/view/5f448466-eebd-4ad2-bdd8-314a55133403-0a17/
All work items above still apply except #395 could be changed to describe the Trajectory Title input as the only optional display data field to keep. Also, I think #389 could be postponed until later version as well. If there is an issue, the user will just get the generic error message.


AppSync Simulator: TypeError

Describe the bug
Trying to upgrade to serverless framework v3 and its throwing this error
AppSync Simulator: TypeError: Cannot convert undefined or null to object

Its working as expected when I downgrade to v2
I tried the solution mentioned at https://stackoverflow.com/questions/72695038/appsync-simulator-typeerror-cannot-convert-undefined-or-null-to-object and looked at issue #170 too, it didn't solve the issue
Screenshots

Additional context
here's relevant section of  package.json
 "resolutions": {
    "serverless-appsync-simulator/cfn-resolver-lib": "1.1.7"
  },
  "devDependencies": {
    "serverless": "^3.22.0",
    "serverless-appsync-cloudfront": "^1.0.2",
    "serverless-domain-manager": "^6.1.0",
    "serverless-dotenv-plugin": "^3.8.1",
    "serverless-iam-roles-per-function": "^3.2.0",
    "serverless-offline": "^9.3.0",
    "serverless-plugin-canary-deployments": "^0.7.0",
    "serverless-plugin-datadog": "^3.5.1",
    "serverless-plugin-lambda-insights": "^1.5.0",
    "serverless-prune-plugin": "^1.4.3",
    "serverless-python-requirements": "^5.1.0",
    "serverless-wsgi": "^1.7.6"
  },
  "dependencies": {
    "serverless-appsync-plugin": "^1.14.0",
    "serverless-appsync-simulator": "^0.20.0",
    "serverless-plugin-lambda-dead-letter": "^1.2.1"
  }

sorry for the noise here,  I did a fresh installation and this is no longer an issue.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter vis-timeandweather for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.vis-timeandweather
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E164] onlyWWW should have common.mode "none" in io-package.json

WARNINGS:

[ ] :eyes: [W127] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W134] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W154] Missing suggested translation into uk,pt,nl,fr,it,es,pl,zh-cn of some "common.news" in io-package.json.
[ ] :eyes: [W172] "common.localLink" in io-package.json is deprecated. Please define object "common.localLinks": { "_default": "..." }
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.noConfig" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI.config":"none".
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W523] "package-lock.json" not found in repo! Please remove from .gitignore!

SUGGESTIONS:

[ ] :pushpin: [S526] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 13 Sep 2024 14:23:12 GMT based on commit 185cf90128513f5300b5d2ba6f976cefaaf32fd5
ioBroker.repochecker 3.0.5

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[E162] js-controller dependency missing. js-controller 4.0.24 is required as minimum, 5.0.19 is recommended. Please add to dependencies at io-package.json.
:thumbsup:Thanks for fixing the issues.


Migrate to new documentation platorm

Since the recent changes in the release process, the documentation on the old website is getting outdated. We should move to a new documentation platform that can host the up-to-date documentation - preferably in a CI fashion.
The team has expressed a requirement for both versioned and unversioned documentation to be supported on whatever platform we migrate to.
Notes form the Read the Docs platform investigation:

Automation support for automatically updating documentation as commits are added to branches.
Support for versioned and unversioned documentation ("Single Version Documentation")

Versioned and unversioned documentation can co-exist in the same search space via the sub-project system.
This would require a separate branch or repo for the unversioned documentation.

The breathe plugin can ingest the existing Doxygen in-code documentation, and display it in a style consistent with the rest of the documentation.

Prerequisite: https://github.com/ARMmbed/mbedtls/issues/3852
The task is done once

a Read the Docs project is set up for Mbed TLS
version independent (https://github.com/ARMmbed/mbedtls-docs) documentation is displayed
version dependant (doc directory in https://github.com/ARMmbed/mbedtls) documentation is displayed
doxygen documentation in the latter is displayed in a consistent style

Prerequisite: https://github.com/ARMmbed/mbedtls/issues/3852
The task is done once

a Read the Docs project is set up for Mbed TLS
version independent (https://github.com/ARMmbed/mbedtls-docs) documentation is displayed
version dependant (doc directory in https://github.com/ARMmbed/mbedtls) documentation is displayed
doxygen documentation in the latter is displayed in a consistent style

The version-independent documentation has been set up with a Sphinx configuration in ARMmbed/mbedtls-docs#16. I have opened #4848 to track the migration of the version-dependent documentation at a future time. All that remains is to set up a Read The Docs project and move the version-independent documentation.

Parts of the tasks have been moved to https://github.com/ARMmbed/mbedtls/issues/4862 and #4848. Everything else in this task is done.


Input is returning escaped string - needs unquoting

stripcslashes() should solve this

0.9.0 https://github.com/macder/wp-form-validation/pull/75 introduced new methods render and transform methods to the input class that solve this problem.


Status bar initial implementation

Closes #2175

During today's meeting with @andreasgeier, we decided on the next steps:

I'll update the branch to use a light status bar.
For Monday, I'll provide an application build which can be used for experiments with the colors.
My next step will be to implement the status bar overlay with Engine Profile specifically.

Clean implementation, I like :+1:.
One tiny issue: The engine profile does have a different font-size, resulting in a slight miss-alignment:
.
Should be 13px instead of 14px I believe and we're good:

I've adjusted the line height and the status bar height so that we can keep the font as it is. Should be in the centre now.

The font sizes should be the same, right? Or is there a reason XML and the engine profile are off by 1px?

As mentioned the fix is to make the profile text 13px in size, just like the other texts in the status bar: https://github.com/camunda/camunda-modeler/pull/2176#issuecomment-809317005

Oh sorry. I haven't noticed :D

There is no reason for that. Thanks for noticing!

After closing the XML View, the button has a weird focus state

Oh, actually I saw my branch was not updated to the latest state... It's gone :)

Wazzup merge-me?


updated to new oauth hash

This fixes the User model to look for the new hash that github is now using in it's payload. It no longer sends user_info, it's just called info now. Here's the primary difference:
def user_data_from_oauth(payload)
  {
    'name'  => payload['user_info']['name'],
    'email' => payload['user_info']['email'],
    'login' => payload['user_info']['nickname'],
    'github_id' => payload['uid'],
    'github_oauth_token' => payload['credentials']['token']
  }
end

... to ...
def user_data_from_oauth(payload)
  {
    'name'  => payload['info']['name'],
    'email' => payload['info']['email'],
    'login' => payload['info']['nickname'],
    'github_id' => payload['uid'],
    'github_oauth_token' => payload['credentials']['token']
  }
end

Note that this is currently not allowing new users to register via github on travis-ci.org

@sethvargo Thank you very much for fixing this, this is very very helpful, mucho thanks!


OpenSSL/3.1.4 Error

When using cURL to download a file from Amazon AWS S3 bucket using cURL command, the following error is given:
OpenSSL/3.1.4: error:80000002:system library::No such file or directory
However when using the native macOS cURL command the file is downloaded without an issue.
var $curl; $response: Object

$curl:=new object(\
"URL"; "<url_from_s3.amazonaws.com/keys>"; \
"DEBUG": Get 4D Folder (Logs folder); \
"WRITEDATA"; System folder(Desktop)+"sample_001.zip"\
)

$response:=cURL($curl) // $response.status = 35

for error 60 (not 35)
https://github.com/miyako/4d-plugin-curl-v3/blob/main/curl/test/Project/Sources/Methods/TEST_https.4dm

"DEBUG": Get 4D Folder (Logs folder)

care to share the log files?

alway good practice to do a quick search (or use AI, if you like...) the error message before asking for help from a real person
https://github.com/beyondcode/expose/issues/391

even though the plugin is using a static library, the paths may be hard coded by default.

"DEBUG": Get 4D Folder (Logs folder)

care to share the log files?

If you wish to have the CURLINFO_SSL_DATA_@ files I can send those also, but the CURLINFO_TEXT.log is:
Host redacted.s3.amazonaws.com:443 was resolved. IPv6: (none) IPv4: X.X.X.X, Y.Y.Y.Y, Z.Z.Z.Z   Trying <IP_ADDRESS>:443... Connected to redacted.s3.amazonaws.com (X.X.X.X) port 443 ALPN: curl offers h2,http/1.1 TLSv1.3 (OUT), TLS handshake, Client hello (1): TLSv1.3 (IN), TLS handshake, Server hello (2): TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): TLSv1.3 (IN), TLS handshake, Certificate (11): TLSv1.3 (OUT), TLS alert, unknown CA (560): OpenSSL/3.3.0: error:80000002:system library::No such file or directory Closing connection

do you or don't you have problems with other URLs? is the problem specific to Amazon S3 bucket? (B.T.W, I don't use Amazon (for anything, actually, not even Prime Video) and I can't confirm your report without an actual URL.

I can provide the code snippet via messages if you'd prefer. Considering the data is somewhat sensitive, I'd prefer not to post publicly.

the latest version uses OpenSSL/3.3.0 so your error suggest you are using an old version.
keep in mind that OpenSSL requires Monterey minimum. in general, you should always specify your OS version when talking about a potential bug.

Currently running macOS Sonoma 14.4.1, 4D 20R2 (100434), and v4.7.1 of your plugin.

I think you should specify CACERT.

I think you should specify CAINFO or else disable SSL_VERIFYPEER

You're correct. Setting "SSL_VERIFYPEER" to 0 allows the curl plugin to download the ~550 MB zip file.


can't easily edit the codeblocks in live preview

[x] The Plugin is up to date
[x] Obsidian is up to date

Describe the bug
In live preview, there is only a copy button, covering the edit button.
clicking on the codeblock does not turn it into an editable thing.
To Reproduce
add a codeblock, turn on the plugin, go to Live Preview
Expected behavior
clicking on the codeblock should go into edit more.
Or, move the copy code button elsewhere, so it doesen't obscure the edit button.
Screenshots
Occurs on

[x] Windows
[ ] macOS
[ ] Linux
[ ] Android
[ ] iOS

Plugin version
0.2.1
Additional context

clicking on the codeblock does not turn it into an editable thing.

That is by design, allowing you to freely select text in the code block.

In live preview, there is only a copy button, covering the edit button.

I will try to move the copy button.

I moved the copy button to the lower right corner


loaders: Add getSources() to ContractResult

Added getSources?: () => Promise<ContractSources>; to ContractResult
Currently only supported by the Etherscan loader
ContractSources automatically deserializes the encoded source code structure. This will help once we add support for the Sourcify loader which uses a different format (and will require a separate request for each import).
ContractResult is not yet accessible from AutoloadResult, so would need to use loaders directly to access it for now. (This will require a bit more plumbing, since autoload uses loadABI rather than loadContract, so we'll need yet another flag to include contract sources.)
Fixes #111

Usage:
const result = await loader.getContract(address);
const sources = await result.getSources();

for (const s of sources) {
  console.log(s.path, " -> ", s.content.slice(25) + "...");
}

Alright I think this is ready for merge and then probably new release time!


Sync README.md with latest envvar names

e.g. readme says AXIOM_DEPLOYMENT_URL, code looks for AXIOM_URL.

Which ones should we use? I prefer the long ones since they are more explicit and we do it in all our other OSS projects, as well.

the short ones, across all our projects. And also, AXIOM_URL should be optional and https://cloud.axiom.co by default across all our projects too :)


provided data types on git repository detailed view dont show ✅  for related type.

Environment

Python version: 3.7
Nautobot version: 1.3.5

Steps to Reproduce

Create/Sync a git data source.
Click on the detailed view for that git-repository
On the right hand pane under provided data types all show ❌  even though the edit view for that git repository has a data source properly selected.

Expected Behavior
✅  for the data source type the repository is related to.

Observed Behavior
All show ❌  even though the edit view for that git repository has a data source properly selected.

Looks like a bug introduced by #1212. The following diff appears to fix it:
diff --git a/nautobot/extras/templates/extras/gitrepository.html b/nautobot/extras/templates/extras/gitrepository.html
index 9b269f108..ca230793a 100644
--- a/nautobot/extras/templates/extras/gitrepository.html
+++ b/nautobot/extras/templates/extras/gitrepository.html
@@ -78,9 +78,9 @@
                                 {{ entry.name|title }}

                                 {% if entry.content_identifier in object.provided_contents %}
-                                    {{ true | render_boolean }}
+                                    {{ True | render_boolean }}
                                 {% else %}
-                                    {{ false | render_boolean }}
+                                    {{ False | render_boolean }}
                                 {% endif %}


Violation messages in Chrome Version 63.0.3239.84 console in Angular app

In recent versions of Chrome, I've started to see many "violation" messages in the Chrome console when running an Angular app (latest versions of Angular, etc.):
[Violation] Added non-passive event listener to a scroll-blocking 'wheel' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952

Also:
[Violation] 'load' handler took 314ms

This is a simple Angular app, that has a list of data on it, so I'm assuming it's because Chrome needs to scroll to show the whole list?
(complete message below)
zone.js:1662 [Violation] Added non-passive event listener to a scroll-blocking 'wheel' event. Consider marking event handler as 'passive' to make the page more responsive.