[FEATURE]Add Integration installation Progress Bar

Is your feature request related to a problem?
Currently the installation of an S3 based integration may take minutes
Customer may suffer confident lose if there is no indication of progress during this installation process
What solution would you like?
Return the informative progress bar showing the different stages the integration needs to install and indicate which is the current step

Completely agree on the status bar as a bouncing icon might get confused with a broken impl.  If it takes minutes, people may assume its broken and re-initiate the action because there is no real indication of progress.  We have two options from what I see.  1/ have a running list of assets being installed and enumerate those on the screen as they get installed 2/ put a status bar with "estimated" percentages.  It is only a UI thing right now and automation / APIs will most likely be the highest percentage of how users install Integrations.  But overall, we added something similar for the OpenSearch Service for blue/green deployments because of lack of progress visibility.  There may be some integrations that require further setup times and we dont want people to abandon a setup due to perceived lack of progress.

@YANG-DB , This issue actually reminds me that, for speeding up the installation, maybe some of the procedure can be run in parallel, by implementing a parallel executor as @Swiddis mentioned before.  For example, after the table creation, instead of a sequential run for both mv index creation query and skipping creation query, it can be a parallel run for these indices creation queries.

@YANG-DB , This issue actually reminds me that, for speeding up the installation, maybe some of the procedure can be run in parallel, by implementing a parallel executor as @Swiddis mentioned before. For example, after the table creation, instead of a sequential run for both mv index creation query and skipping creation query, it can be a parallel run for these indices creation queries.

Just created an issue for the above comment: https://github.com/opensearch-project/dashboards-observability/issues/1859


Adding a time stamp to each image possible?

Hi,
I must admit, that I´m a rookie, so forgive me if I ask for something simple.
I would like to know, if it is possible to add a time stamp to the image name e.g. image"hour""minute""second"?
Seconds are not mandotory, but hour and minute. Reason is that I have an internet page build by wordpress and there are only a few webcam plugins available. One which seems to work needs a time stamp in order to show a new image after refreshing.
Thanks in advance
Sven

@Wischi1 Please see the Wiki page on overlays.  It explains what you can have overlaid on top of the image, including the date/time.
If this answers your question, please close the Issue.
And going forward,  if you have a question or want to request a feature, please use the Discussions link at the top of the page so we can keep the Issues list for actual bugs.
Thanks, and welcome to the Allsky community!

Hi Eric,thanks for the info. Next time I will use discussion for raising questions.
Maybe I was not clear enough, I mean is there chance, to add the time to the file name, not to the picture. This I already have.
Sven

@Wisch1 Which filename are you referring to?  The ones in allsky/images/DATE/*.jpg have the date and time in their names.  The newest version of Allsky, released a couple days ago, initially saves files with these names (it used to save a file called "image.jpg" which was then processed and copied to allsky/images/DATE/).

@Wischi1   ?

Hey Eric, thanks for Information. I will try the new version and see, if it fits to what I expect.
But in the meantime I installed a Wordpress plugin called webcamviewer and this plugin already solved my problem. It refreshes every minute the allsky image.jpg without having a time stamp.
Cheers Sven

@Wischi1 A plugin shouldn't be needed to do what you want, unless I don't understand what you're trying to accomplish.  But, if it's working, don't mess with it.
I'll close the Issue.


Supports fish shell for environment variables

Fish environment variables are slightly different, we should support it.
set -g -x DOCKER_HOST tcp://<IP_ADDRESS>:2376

Need to write these commands in ~/.config/fish/config.fish instead of running them.


Support for DECLARE and SET statements on mssql to use scalar functions

Would it be possible to add support to declaring local SQL variables and setting their value ?
something along these lines:
declare @max_inv varchar(10) ;
set  @max_inv = func_getMaxInv(); --this is a scalar function to get the latest invoice number

SELECT 'table' as component

select [id] , [invoice_no], [invoice_date], [cust_no]
from SALES_HISTORY
where invoice_no = isnull($invoice_no, @max_inv)

This snippet should either show the invoice passed in the parameter or the last one.

That would indeed be nice ! But this will require support from sqlparser-rs first. Let's ask them !

In your particular example, is there a reason you cannot use

select [id] , [invoice_no], [invoice_date], [cust_no]
from SALES_HISTORY
where invoice_no = isnull($invoice_no, func_getMaxInv())

?

Yes, I can do that as workaround in this particular case. In amore generic way I still would love to be able to use local variables so there is no need to call a function many times.

Let's keep that open to keep track of the feature. It's something I'd like to see in SQLPage too

SET is supported as of 0.12.0-beta, and implemented on sqlpage's side (the variable are stored in sqlpage, not in the database).
This allows for new interesting use cases, using variable values as inputs to sqlpage functions.


Using xcodeproj 1.0.0

xcodeproj finally reached release 1.0.0. I think it's time to make the change 😋

Woot! Thanks!

Can we have a new release? 🎉

Yep! I'll do a release later today after merging https://github.com/venmo/synx/pull/104

great - thank you!

Just pushed 0.2.1 to rubygems. Held off on #104 because I'd like to see a test for it


ThunderFX's splitter looks tad conservative for custom torch.autograd.Functions by pushing them to the fallback path

🐛 Bug

ThunderFX does not seem to support some custom torch.autograd.Functions that thunder.jit could handle.
To Reproduce
Simpler torch.compile custom backend calling thunder.jit handles the following snippet (the program is the same as https://github.com/Lightning-AI/lightning-thunder/blob/9de543417260bd32740e2d7bd0763a5871fdee5c/thunder/tests/test_jit_general.py#L1144)
ThunderFX however seems to have the fallback handle the program as in #1538.
import torch

import thunder
from thunder.dynamo.utils import recompile_graph, remove_empty_autocast, reproducer, CompilerType

class MyFunction(torch.autograd.Function):
    @staticmethod
    def forward(ctx, x: torch.Tensor) -> torch.Tensor:
        return x * 2.0

    # this is wrong on purpose.
    @staticmethod
    def backward(ctx, grad_output) -> torch.Tensor:
        return grad_output

class Model(torch.nn.Module):
    def __init__(self):
        super().__init__()

    def forward(self, x) -> torch.Tensor:
        return MyFunction.apply(x)

def thunderfx_no_fallback(gm: torch.fx.GraphModule, sample_args):
    remove_empty_autocast(gm)
    recompile_graph(gm)
    jitted = thunder.jit(gm)
    jitted_fns.append(jitted)
    return jitted

jitted_fns = []

if __name__ == "__main__":

    device = torch.device("cuda")
    dtype = torch.bfloat16

    model = Model().to(device=device, dtype=dtype)
    jitted = torch.compile(model, backend=thunderfx_no_fallback)

    x = torch.randn((2, 2), device=device, dtype=dtype, requires_grad=True)
    out = jitted(x)

    jitted = jitted_fns[0]
    print(thunder.last_traces(jitted)[-1])
    print(thunder.last_backward_traces(jitted)[-1])

What follows is the output of the snippet above.
# Constructed by Delete Last Used (took 0 milliseconds)
import torch
from thunder.executors.torchex import no_autocast

@torch.no_grad()
@no_autocast
def computation(L_x_):
  # L_x_: "cuda:0 bf16[2, 2]"
  [autograd_function_apply] = nvFusion0(L_x_)
    # t11 = prims.convert_element_type(L_x_, dtypes.float32)  # t11: "cuda:0 f32[2, 2]"
    # t12 = prims.mul(t11, 2.0)  # t12: "cuda:0 f32[2, 2]"
    # autograd_function_apply = prims.convert_element_type(t12, dtypes.bfloat16)  # autograd_function_apply: "cuda:0 bf16[2, 2]"
  return {'output': (autograd_function_apply,), 'flat_args': [L_x_], 'flat_output': (autograd_function_apply,)}, ((), ())
# Constructed by Delete Last Used (took 0 milliseconds)
import torch
from thunder.executors.torchex import no_autocast

@torch.no_grad()
@no_autocast
def backward_fn(saved_for_backward, cotangents):
  # cotangents: "Collection"
  t0, = cotangents
  clear_mutable_collection(cotangents)
  del cotangents
  [t17] = nvFusion0(t0)
    # t14 = prims.convert_element_type(t0, dtypes.float32)  # t14: "cuda:0 f32[2, 2]"
    # t16 = prims.mul(2.0, t14)  # t16: "cuda:0 f32[2, 2]"
    # t17 = prims.convert_element_type(t16, dtypes.bfloat16)  # t17: "cuda:0 bf16[2, 2]"
  del t0
  return (t17,)

Expected behavior

Environment

PyTorch Version (e.g., 1.0):
OS (e.g., Linux):
How you installed PyTorch (conda, pip, source):
Build command you used (if compiling from source):
Python version:
CUDA/cuDNN version:
GPU models and configuration:
Any other relevant information:

Additional context

https://github.com/Lightning-AI/lightning-thunder/blob/9de543417260bd32740e2d7bd0763a5871fdee5c/thunder/dynamo/splitter.py#L121
The splitter decides whether the operator is supported by thunder by a pre-run, it seems there's an operator not registered in thunder torch.autograd.function.FunctionCtx

It doesn't feel like the missing FunctionCtx is the major cause in my gut feeling.
The target (meaning one in https://github.com/Lightning-AI/lightning-thunder/blob/9de543417260bd32740e2d7bd0763a5871fdee5c/thunder/dynamo/utils.py#L349) should be torch.ops.higher_order.autograd_function_apply which has a lookaside for it in https://github.com/Lightning-AI/lightning-thunder/blob/9de543417260bd32740e2d7bd0763a5871fdee5c/thunder/core/jit_ext.py#L777.


Release botservice microsoft.bot service 2022 09 15

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[X] new API version
[ ] update existing version for new feature
[X] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
1/2023
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[X] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[X] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[X] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[X] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[X] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Thank-you @thatChang - Just want to confirm: the new properties you are adding to existing APIs are actually already part of those APIs? IOW, all of the changes to previous APIs are to make the spec match the API as shipped. Is that correct?

This PR replaces #20803, thank-you @thatChang.
Just want to confirm: the new properties you are adding to existing APIs are actually already part of those APIs? IOW, all of the changes to previous APIs are to make the spec match the API as shipped. Is that correct?

After reviewing the changes in this PR and the current contents of the REST repo, it looks to me like the new API here (2022-09-15) is essentially just promoting the latest existing one (2022-06-15-preview) to GA without significant changes. The rest of the changes look like a bunch of breaking changes (adding properties, removing properties, changing mutability). However, if these are aligning the spec to match the actual API, then ARM feedback isn't needed.
@thatChang - If you can confirm my understanding, then I can sign off for ARM.

@mentat9 Thanks for your feedback. Yes, the PR contains the GA of one preview version and several breaking changes to fix S360 issues - which are align with what actual APIs are.

@mentat9 Thanks for your feedback. Yes, the PR contains the GA of one preview version and several breaking changes to fix S360 issues - which are align with what actual APIs are.

@thatChang - I saw your comment and signed off. For next time, you would normally remove the ARMChangesRequested label to revert back to ARM review (see comment: https://github.com/Azure/azure-rest-api-specs/pull/22077#issuecomment-1372904079).

The PR is the replacement of
https://github.com/Azure/azure-rest-api-specs/pull/20803.

Hi @JeffreyRichter @mikekistler Could you help review the swagger breaking change? Thanks!

@tadelesh Please help confirm Go breaking


xgcm v0.2.0

OceanSpy version: 0.0.11

Description
I tried to do a cutout of the model domain on my local computer. It did not work because the grid was not properly loaded. It turns out the problem was that oceanspy is not currently compatible with xgcm v0.2.0. When I went back to 0.1.0 it worked fine.

Can you please share the error and/or the cutout parameters that generated the error?

See #65 (Ignore the curvilinear grid part; it turned out that was not the problem)

OK, the grid object changed a little in version 0.2.
od._grid.axes['X'].coords['outer'].name now needs to be replaced by od._grid.axes['X'].coords['outer'].
Since we don't have a stable release yet, I would just support xgcm0.2. We can also replace some of OceanSpy's functions with xgcm new features (autogenerate for midp dimensions and we can now use the coords parameter in xgcm.Grid without having to add comodo attributes).


Missing required parameters for id & model

Hi there,
I did a fresh install of this package by following the quickstart documentation, and then I saw a little bit of an error.
Missing required parameters for [Route: filament.pages.workflow-history/{id}/{model}] [URI: admin/workflow-history/{id}/{model}] [Missing parameters: id, model].
After, seeing your code I found the problem came from this line a required parameter of id & model. And I think we need to make it optional like this workflow-history/{id?}/{model?}. Cause when I try to change it into optional on the vendor directory, it works like a charm.
Thanks

Hello @muhibbudins
I will try to check this ASAP and let u know, sorry for the late answer.

No problem, thanks in advance @heloufir


Can't upgrade to Gradle 6.3-rc-1 from 6.1 (new project)

Expected Behavior

./gradlew wrapper --gradle-version=6.3-rc-1
A fresh Gradle project should be able to upgrade from 6.1 to 6.3-rc-1 on JDK 14.
Current Behavior

Could not initialize class org.codehaus.groovy.runtime.InvokerHelper
Context

I was able to upgrade a single project from a version of 6.3 that did not support JDK 14 to one that does... for some reason, all other projects cannot be upgraded (even brand spanking new ones).
Steps to Reproduce

Just create a new Gradle project in IntelliJ IDEA EAP (March 12 update).
------------------------------------------------------------
Gradle 6.1
------------------------------------------------------------

Build time:   2020-01-15 23:56:46 UTC
Revision:     539d277fdba571ebcc9617a34329c83d7d2b259e

Kotlin:       1.3.61
Groovy:       2.5.8
Ant:          Apache Ant(TM) version 1.10.7 compiled on September 1 2019
JVM:          14 (Oracle Corporation 14+36-1461)
OS:           Linux 5.5.9-arch1-2 amd64

@redlet Can you please share the whole stacktrace?
Also, when you upgrade using ./gradlew wrapper --gradle-version=6.3-rc-1 you're still running an older Gradle version that is not compatible with Java 14 but as it looks using a Java 14 JVM. I think you need to use a supported version to do the upgrade. Or provide some more steps to reproduce this issue.

@bmuskalla You were right; my IDE was using JDK 14. I thought IntelliJ IDEA was packaged with its own JDK. sudo archlinux-java set java-13-openjdk then relaunching IDEA fixed the issue. (Prior to this, I actually copy/pasted the gradle wrapper from another project lol.)


Error: Cannot find module '/root/.leon/node_modules/stt/lib/binding/v1.1.0/linux-x64/node-v108/stt.node'

Specs:

Leon version 1.0.0-beta.7
OS: UBUNTU 22.04 LTS
Node Version : v18.14.1
Command to check leon  sudo pipenv run leon check

(python) (base) geek@g3:~/my-projects$ sudo pipenv run leon check
Loading .env environment variables...

><EMAIL_ADDRESS>check
> babel-node scripts/run-check.js

Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
⠋

.: CHECKING :.
ℹ  Leon version
✅ 1.0.0-beta.7

ℹ  node --version
✅ v18.14.1

ℹ  npm --version
✅ 9.6.1

ℹ  pipenv --version
✅ pipenv, version 2023.2.18

ℹ  pipenv --where
✅ /home/geek/my-projects/bridges/python

ℹ  pipenv run python --version
✅ Python 3.9.10

ℹ  pipenv run python bridges/python/main.py scripts/assets/intent-object.json
✅ {"domain": "leon", "skill": "random_number", "action": "run", "lang": "en", "utterance": "Give me a random number", "entities": [], "slots": {}, "output": {"type": "end", "codes": ["61"], "speech": "61", "core": {}, "options": {}}}

ℹ  Global resolvers NLP model state
✅ Found and valid

ℹ  Skills resolvers NLP model state
✅ Found and valid

ℹ  Main NLP model state
✅ Found and valid

ℹ  Amazon Polly TTS
⚠  Amazon Polly TTS is not yet configured

ℹ  Google Cloud TTS/STT
⚠  Google Cloud TTS/STT is not yet configured

ℹ  Watson TTS
⚠  Watson TTS is not yet configured

ℹ  Offline TTS
⚠  Cannot find bin/flite/flite. You can setup the offline TTS by running: "npm run setup:offline-tts"

ℹ  Watson STT
⚠  Watson STT is not yet configured

ℹ  Offline STT
⚠  Cannot find bin/coqui/huge-vocabulary.scorer. You can setup the offline STT by running: "npm run setup:offline-stt"

.: REPORT :.
ℹ  Here is the diagnosis about your current setup
✅ Run
✅ Run skills
✅ Reply you by texting
⚠  Amazon Polly text-to-speech
⚠  Google Cloud text-to-speech
⚠  Watson text-to-speech
⚠  Offline text-to-speech
⚠  Google Cloud speech-to-text
⚠  Watson speech-to-text
⚠  Offline speech-to-text

✅ Hooray! Leon can run correctly
ℹ  If you have some yellow warnings, it is all good. It means some entities are not yet configured

Expected Behavior
Offline stt can work properly
Actual Behavior
when I run sudo pipenv run leon start following error occur:
(python) (base) geek@g3:~/my-projects$ sudo pipenv run leon start
Loading .env environment variables...

><EMAIL_ADDRESS>start
> cross-env LEON_NODE_ENV=production node ./server/dist/index.js

.: TCP CLIENT :.
✅ New instance

.: INITIALIZATION :.
✅ The current env is production
✅ The current version is 1.0.0-beta.7
✅ The current time zone is Asia/Calcutta
✅ Collaborative logger enabled

.: BRAIN :.
✅ New instance

.: CONVERSATION :.
✅ New instance

.: NLU :.
✅ New instance

.: NLU :.

.: NLU :.

.: NLU :.
✅ Global resolvers NLP model loaded
✅ Skills resolvers NLP model loaded
✅ Main NLP model loaded

.: NER :.
✅ New instance

.: INITIALIZATION :.
✅ Server is available at http://localhost:1337

.: TCP CLIENT :.
✅ Connected to the TCP server tcp://<IP_ADDRESS>:1342

.: CLIENT :.
✅ Connected
ℹ  Type: webapp
ℹ  Socket id: iSZOgKMrGtMKHVWsAAAB

.: BRAIN :.
✅ New instance

.: CONVERSATION :.
✅ New instance

.: NLU :.
✅ New instance

.: NLU :.

.: NLU :.

.: NLU :.
✅ Global resolvers NLP model loaded
✅ Skills resolvers NLP model loaded
✅ Main NLP model loaded

.: NER :.
✅ New instance

.: ASR :.
✅ New instance

.: STT :.
✅ New instance
ℹ  Initializing STT...
node:internal/modules/cjs/loader:1075
  const err = new Error(message);
              ^

Error: Cannot find module '/root/.leon/node_modules/stt/lib/binding/v1.1.0/linux-x64/node-v108/stt.node'
Require stack:
- /root/.leon/node_modules/stt/index.js
- /root/.leon/server/dist/stt/coqui-stt/parser.js
- /root/.leon/server/dist/stt/stt.js
- /root/.leon/server/dist/core/http-server/server.js
- /root/.leon/server/dist/index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
    at Module._load (node:internal/modules/cjs/loader:920:27)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/root/.leon/node_modules/stt/index.js:24:17)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/root/.leon/node_modules/stt/index.js',
    '/root/.leon/server/dist/stt/coqui-stt/parser.js',
    '/root/.leon/server/dist/stt/stt.js',
    '/root/.leon/server/dist/core/http-server/server.js',
    '/root/.leon/server/dist/index.js'
  ]
}

Node.js v18.14.1
Error: Command failed with exit code 1: npm start

How Do We Reproduce?
Reproduce by running following command on node version 18.14.1 on UBUNTU 22.04 sudo pipenv run leon start

 🐞 [1.0.0-beta.8] Coqui STT does not work with Node.js 18


amplify env remove test, removed all resources of prod branch

Amplify CLI Version
can't remember (cuz I upgraded afterwards), but it wasn't the latest version
Question
I had my main amplify env branch prod, which includes all the resources (dynamo db tables, s3 buckets, cognito, ...)
then I did amplify env add another branch called test. I think I added it when I try to do amplify push on it, it throws exception: 🛑 Template error: instance of Fn::GetAtt references undefined resource authokband411e4d5b
which made me unable to finish amplify push (so I think no resources (dynamo tables, s3 buckets, ...) was generated for test branch
so i decided to just remove this branch by amplify env remove test, then to my shock, it remove ALL my resources (dynamo db tables, s3 buckets, cognito, ...) in prod branch....maybe it's because the amplify push for test branch was never finish so it didn't link its own resources but instead linked prod's resources??
But anyway it resulted in a tragedy that the test branch and all my resources of prod branch was removed. prod branch was left with an empty branch with no resources.
I don't know if I did something wrong that resulted this

Hey @Weixuanf :wave: thanks for raising this! While we begin to look at this in more depth would you mind posting the project ID output from amplify diagnose --send-report?


Cannot read property 'value' of undefined

I'm getting this error when I type inside my input field:

index.js:77 Uncaught TypeError: Cannot read property 'value' of undefined

It's in reference to this line:
return _this2.props.currentLanguage ? _suggestion._highlightResult.name[_this2.props.currentLanguage].value : _suggestion._highlightResult.name.value;

Any idea what could be the issue. I'm rendering my component to page like so:
<AgAutocomplete
  apiKey={"redacted"}
  appId={"redacted"}
  index={"games"}
  inputId="input-search"
  placeholder="Search..."
/>

Any help is appreciated. Thanks in advance!

Hi @realph are you sure that the disaplayKeyinside your algolia data model has a value?
can you share an example of the data that algolia reutrns?

I've run into the same error and the problem was caused because because "name" was not present in the _higlitghtResult object

My only solution is change my model and every single reference to it through my whole app.
I suggest changing
suggestion._highlightResult.name.value;
to
suggestion._highlightResult[displayKey].value;
As I'm not familiar with the api a catch'em all solution could be
for (first in suggestion._highlightResult) break; suggestion._highlightResult[first].value;

thanks @odinti i'll update it as soon as possible.
If you use algolia everyday you may know apis better then me so PR are welcome if you want :)


Wish: "Change with Bracket..." in pop up menu

Hi,
I wish that when I click with the right mouse button on a file used in web sites (html, css, js ...) also appear in the menu marked "Edit with Brackets ...". This writing must be translated into multiple languages depending on the language  set in Bracket.

Closing since we already have a backlog item tracking this


Accessible namespaces functionality is broken in 4.1.0-beta2

Describe the bug
Accessible namespaces functionality is broken in 4.1.0-beta2
To Reproduce
Steps to reproduce the behavior:

Add a new cluster and configure Accessible Namespaces
Click on cluster
See error

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "namespaces is forbidden: User \"https://sts.windows.net/fa7b1b5a-7b34-4387-94ae-d2c178decee1/#nqPjN1BDJSi4LUEkIYa8fR1C1-mZpoOiACmZXDYMKjE\" cannot list resource \"namespaces\" in API group \"\" at the cluster scope",
  "reason": "Forbidden",
  "details": {
    "kind": "namespaces"
  },
  "code": 403
}

just tried https://github.com/lensapp/lens/releases/tag/v4.1.0-rc.2 where I see the previous fixes went it but I still have issues using NS functionality. NS listing is still triggered
console.js:124 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/config.json
console.js:124 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/lens-workspace-store.json
console.js:124 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/lens-cluster-store.json
console.js:124 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/lens-extensions.json
console.js:124 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/lens-filesystem-provisioner-store.json
console.js:124 info: [WORKSPACE-STORE] requesting initial state sync
console.js:124 info: [CLUSTER-STORE] requesting initial state sync
console.js:124 info: [CLUSTER-STORE] start to listen (1)
console.js:124 info: [WORKSPACE-STORE] starting to listen state events
console.js:124 info: [EXTENSION]: enabled<EMAIL_ADDRESS>console.js:124 info: [EXTENSION]: enabled<EMAIL_ADDRESS>console.js:124 info: [EXTENSION]: enabled<EMAIL_ADDRESS>console.js:124 info: [EXTENSION]: enabled<EMAIL_ADDRESS>console.js:124 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/extension-store/lens-survey/preferences-store.json
console.js:124 info: [EXTENSION]: enabled<EMAIL_ADDRESS>/Applications/Lens.app/Contents/Resources/extensions/telemetry/dist/renderer.js:121 telemetry extension activated
console.js:124 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/extension-store/lens-telemetry/preferences-store.json
console.js:124 info: [EXTENSION]: enabled<EMAIL_ADDRESS>console.js:124 info: [LENS-VIEW]: init dashboard, clusterId=95d07f09-3f0e-4152-b236-2352e1200524
console.js:124 error: Can't find working API for the Kubernetes resource ingresses
VM57 Lens.js:2 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/config.json
VM57 Lens.js:2 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/lens-workspace-store.json
VM57 Lens.js:2 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/lens-cluster-store.json
VM57 Lens.js:2 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/lens-extensions.json
VM57 Lens.js:2 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/lens-filesystem-provisioner-store.json
VM57 Lens.js:2 info: [WORKSPACE-STORE] requesting initial state sync
VM57 Lens.js:2 info: [CLUSTER-STORE] requesting initial state sync
VM57 Lens.js:2 info: [CLUSTER-STORE] start to listen (5)
VM57 Lens.js:2 info: [WORKSPACE-STORE] starting to listen state events
VM57 Lens.js:2 info: [APP]: Init dashboard, clusterId=95d07f09-3f0e-4152-b236-2352e1200524, frameId=5
console.js:124 info: [LENS-VIEW]: loaded from http://95d07f09-3f0e-4152-b236-2352e1200524.localhost:63333/
VM57 Lens.js:2 info: [EXTENSION]: enabled<EMAIL_ADDRESS>VM57 Lens.js:2 info: [EXTENSION]: enabled<EMAIL_ADDRESS>VM57 Lens.js:2 info: [EXTENSION]: enabled<EMAIL_ADDRESS>VM57 Lens.js:2 info: [EXTENSION]: enabled<EMAIL_ADDRESS>VM57 Lens.js:2 info: [EXTENSION]: enabled<EMAIL_ADDRESS>VM137 renderer.js:121 telemetry extension activated
VM57 Lens.js:2 info: [STORE]: LOADED from /Users/amuraru/Library/Application Support/Lens/extension-store/lens-telemetry/preferences-store.json
VM57 Lens.js:2 info: [EXTENSION]: enabled<EMAIL_ADDRESS>95d07f09-3f0e-4152-b236-2352e1200524.localhost:63333/api-kube/api/v1/namespaces?:1 Failed to load resource: the server responded with a status of 403 (Forbidden)
VM57 Lens.js:2 Loading store items failed Object
loadAll @ VM57 Lens.js:2
95d07f09-3f0e-4152-b236-2352e1200524.localhost:63333/api-kube/api/v1/namespaces?:1  Do you see an error page or is cluster dashboard just empty?

Moving to 4.1.1 because I cannot reproduce this.

@jakolehm thanks for looking into this. Unfortunately I am still seeing this in latest 4.1.2.
Here is a recording of my session:
https://recordit.co/yGDKo8aprA

Will investigate again

Looking at code this is definitely broken will create a PR to fix, namespace select is ignoring changes to accessible-namespaces and only ever displays items gotten from the namespace API.

This is working for me! Thanks!

Excellent thanks, did you try that branch or is it fixed in the latest release?

4.1.3 release seems to fix that

Excellent, thanks.

this bug is back, it works in 4.2.2 but 4.2.3 and 4.2.4 cannot list namespaces

/reopen

Will investigate.

@Nokel81 any update on this please? It's quite annoying cause I cannot find a way to pin the version to 4.2.2
For some reason - lens keeps updating to latest 4.2.4 even if I select No when upgrade popup appears

There was a bug in 4.2.2 where updating was accidentally forced. I will see if I can reproduce the accessible namespaces not working in 4.2.4

I have verified that this is working in the 5.0.0 beta releases.

hi @Nokel81 - just tried this in Lens: 5.0.0-beta.7.20210607.1 and I can still see the issue with the namespaces not being displayed in the dropdown and errors trying to list the namespaces in the console log.
here is a testing session recording:
https://user-images.githubusercontent.com/728853/121344687-b8235780-c92c-11eb-880f-c2cc3905ddad.mov
And the console logs:
localhost-1623237101796.log
I am not sure if this is something specific to my environment (k8s version, rbacs, etc) - let me know if you need more info

Thanks for the repro, I am currently working on simplifying the accessibleNamespaces logic, so I will keep this in mind. Will link the PR when I get it up.


Practice 6 - simple_local_planner - target velocity formula

This part of the code:
https://github.com/jaak-peterson/autoware_mini_practice/blob/d5e11e765d962cfe8e2896618da3ddcb2e42be6b/practice_6/nodes/planning/local/simple_local_planner.py#L154-L155

You should remove np.maximum from target_distances formula. It is OK if it goes negative. It will have balancing effect in the following formula by lowering the target velocity output.
np.maximum should be added to target_velocities formula so that np.sqrt won't have a negative value

ok


Better interop with NodeJS-native ES Modules

Motivation:
Make package work with modern NodeJS (native ES Modules)
Changes:

Set type to module so that NodeJS understands that .js files are written in ES Module syntax
Rename files that use CommonJS syntax to .cjs to trigger proper handling in NodeJS (specifically used in tests & exports)
Add file extensions to imports for better compatibility with ES Modules
Provide dual exports so that the package can be both imported and required in NodeJS
Explicitly exportessentials and selection builds (ES Modules only — this mimics the previous behavior)
Upgrade unit tests (tape & jsdom) to play nice with the new ES Module setup

Awesome! I was just trying to figure out how to do this last night, using v3 of d3-transition as a starting point. Questions:

Do we need the sideEffects or peerDependencies properties like d3-transition has? d3-transition also imports a range of packages ("d3-color": "1 - 3",)
Since D3 is dropping CommonJS exports does it make sense to bother with duel exports instead of just doing a major version bump?
If we're doing a major version bump, should we also switch over to d3v7 once their ESM conversion is finished? I think only a couple of small changes to nestBy, attachTooltip and loadData would be needed along with a refresh of the documentation. cc @gka

D3's API hasn't changed too much since being split into modules and jetpack doesn't hit too many edge cases; I think 1 - 3 should work just fine.
I'm not sure how modern javascript works, but I think peer dependencies of 2-3 for d3-transition and d3-selection might fix #68.
Merging this as is to fix the tooling issue also works; the major version bump can wait till d3's.

@1wheel Hey Adam, thanks again for your feedback. I've added peerDependencies and sideEffects per your suggestion. I've also discussed this with @gka and we decided to stick with v1 dependencies for now to keep backwards compatibility. We haven't merged this into master yet because it needs more testing, but we're working on a new release here: https://github.com/gka/d3-jetpack/pull/76


Syntax highlighting for each supported language

🚀 Feature
Depending on the programming language specified in the cell, the syntax highlighter must react to its changes and output accordingly.

Sir Can I Give it Try?

@Subhraneel77 sure, go ahead with it.

I've left here a bit of doc: https://github.com/metacall/jupyter-kernel/pull/159#issuecomment-1020023655

Hello @viferga!
I am an openforce 2022 contributor. I would love to work on this issue and make PR as soon as I resolve the issue. Please do assign this to me.
ThankYou:)


feature request: pull specific tag

Hi!
For pushing it's already possible; I would like to be able to retrieve translations only for a specific tag.
I have a monorepo app for which all translations are in the same localise project. Each project in my codebase corresponds to a specific tag in localise.
So:
npx loco-cli pull

To:
npx loco-cli pull --tag my-tag

Equal to push command:
npx loco-cli push --tag my-tag

Hi! This is actually a great suggestion. I will look into it, or if you want you can open an MR 🙂

Hi, this feature will be added in v2 🎉. You now have access to all push and pull options from the Loco API:
{
  "push": {
    "tag-new": "my-tag",
  },
  "pull": {
    "filter": "my-tag"
  }
}

The new version is currently in RC, but you can already test it out. See the Release Notes here


Linux build?

With Tauri, it should be possible to generate a Linux build of this quite easily.
Is that something one would be interested in?

There are too many linux versions, so the compiled version is not provided. If necessary, you can compile it through the source code.


[5.5] Implement XCTAssertIdentical & XCTAssertNotIdentical

Merge pull request #325 from egorzhdan/XCTAssertIdentical
cc @egorzhdan

@swift-ci Please test

Show me how :)
On Thu, Aug 5, 2021, 6:34 AM Stuart Montgomery @.***>
wrote:

Merge pull request #325
https://github.com/apple/swift-corelibs-xctest/pull/325 from
egorzhdan/XCTAssertIdentical
cc @egorzhdan https://github.com/egorzhdan
You can view, comment on, or merge this pull request online at:
https://github.com/apple/swift-corelibs-xctest/pull/327
Commit Summary

Merge pull request #325 from egorzhdan/XCTAssertIdentical

File Changes

M Sources/XCTest/Public/XCTAssert.swift
https://github.com/apple/swift-corelibs-xctest/pull/327/files#diff-207fe88e155496bb8f4148c8590760ba3d7d650d705d4e0254b57bff1bb7c92c
(32)
M Tests/Functional/FailureMessagesTestCase/main.swift
https://github.com/apple/swift-corelibs-xctest/pull/327/files#diff-b341b6d4b2a0fcbed758ef8369fc96feabae8eb835bbaacd4b579f50b792b211
(29)

Patch Links:

https://github.com/apple/swift-corelibs-xctest/pull/327.patch
https://github.com/apple/swift-corelibs-xctest/pull/327.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apple/swift-corelibs-xctest/pull/327, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUCT7RMGUZDS7G52VUHCCBTT3KHOZANCNFSM5BT4AUYQ
.

Thank you.
On Thu, Aug 5, 2021, 8:04 AM xeL_oloR @.***> wrote:

Show me how :)
On Thu, Aug 5, 2021, 6:34 AM Stuart Montgomery @.***>
wrote:

Merge pull request #325
https://github.com/apple/swift-corelibs-xctest/pull/325 from
egorzhdan/XCTAssertIdentical
cc @egorzhdan https://github.com/egorzhdan
You can view, comment on, or merge this pull request online at:
https://github.com/apple/swift-corelibs-xctest/pull/327
Commit Summary

Merge pull request #325 from egorzhdan/XCTAssertIdentical

File Changes

M Sources/XCTest/Public/XCTAssert.swift
<
https://github.com/apple/swift-corelibs-xctest/pull/327/files#diff-207fe88e155496bb8f4148c8590760ba3d7d650d705d4e0254b57bff1bb7c92c

(32)

M Tests/Functional/FailureMessagesTestCase/main.swift
<
https://github.com/apple/swift-corelibs-xctest/pull/327/files#diff-b341b6d4b2a0fcbed758ef8369fc96feabae8eb835bbaacd4b579f50b792b211

(29)
Patch Links:

https://github.com/apple/swift-corelibs-xctest/pull/327.patch
https://github.com/apple/swift-corelibs-xctest/pull/327.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apple/swift-corelibs-xctest/pull/327, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AUCT7RMGUZDS7G52VUHCCBTT3KHOZANCNFSM5BT4AUYQ
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apple/swift-corelibs-xctest/pull/327#issuecomment-893532863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUCT7RJWEKLGF4PU5WS3EPTT3KSBNANCNFSM5BT4AUYQ
.


Upload video tests

Added Junit tests for uploading video functionality.
Test results: https://screenshot.googleplex.com/XJVJAfQVcJf
The GET and POST methods of VideoUploadServlet.java rely on the getUrl() and postUrl() methods of the VideoUplaod.java class, so these are the methods I have tested. I use a local Datastore service stub for all my tests so all the data is held in memory.

shotsServlet tests are in the last PR (It wasn't approved when i sent you the 5 PRs all at once), but it should be by the end of today! And yes, DataServlet never had anything in it- I was kind of just using it as a template

I added a screenshot of test results to the description. New helper methods and 3 tests that do postUrl and getUrl together are near the bottom of the file!
@vkkpng-g I didn't think it was necessary to test getUploadedFileUrl in VideoUploadServlet because this method is just retrieving Blobstore data that has been uploaded through the code at the top of the upload.jsp file. The rest of the doGet and doPost methods don't have any logic to test, so I would just test the HTTP connections to the servlets. Should I do this?


hover state of icons added

I have added the hover state in icons in the footer....

hi @gabrysia694 I have created a pr for this issue, I have not added any color in this hover state as it was not looking good..I have just done some random change, hope it will be good to merge....


Fix -pkeyopt handling in apps/pkeyutl -rawin

The EVP_DigestSignInit and EVP_DigestVerifyInit have to be initialized before the EVP_PKEY_CTX_ctrl_str is invoked. The statement about delayed initialization (introduced by https://github.com/openssl/openssl/commit/ee633ace7397ebc9829b845e7e7bbd8283b455f6) feels wrong. When the ctx not initialized properly the ctrl command used to set -pkeyopt fails.
This PR fixes handling of the -pkeyopt argument when -rawin is also defined by moving EVP_DigestSignInit and EVP_DigestVerifyInit before EVP_PKEY_CTX_ctrl_str.

Would you mind to add a test?

Would you mind to add a test?

Yeah, sure! It's there now.

Yeah, sure! It's there now.

@mattcaswell, would you please review this patch? It modifies the code you contributed, so I wonder if my assumptions are correct.

ping @openssl/committers for the second review

This pull request is ready to merge

Merged to master. Thank you for the contribution!

Thank you very much for your help with this!


Split debuginfo into separate files

@joestringer  Fixes: #3799
I added a flag "--file-per-command" which generates a single file for each command,
and restructured the code to make it more readable
Single file:
$ cilium debuginfo -f debug.md
Warning, some of the BPF commands might fail when run as not root
Markdown output at debug.md

Multiple files:
$ cilium debuginfo -f debug.md --file-per-command
Warning, some of the BPF commands might fail when run as not root
Markdown output at debug-cilium-status.md
Markdown output at debug-cilium-endpoint-list.md
Markdown output at debug-cilium-service-list.md
Markdown output at debug-cilium-policy.md
Markdown output at debug-cilium-memory-map.md
Markdown output at debug-cilium-version.md
Markdown output at debug-kernel-version.md
Markdown output at debug-cilium-environment-keys.md

With multiple files, i insert the command name between the file-name and file-extension

test-me-please

test-me-please

@raybejjani can you review again

test-me-please


Small improvements

Changed [] to <>
Added prefix/color to /tphere
Updated information for /vanish command in README
Changed core.vanish.others to es.vanish.others
Added aliases from Bukkit's Essentials

Thanks


Is it possible to make available this feature for m.facebook.com ?

Closing for #90 < should cater for mobile android.


Translation memory

As per @hturner at https://r-contributors.slack.com/archives/C0210D7EN1X/p1684139404126109

Weblate/Weblate Translation Memory in the automatics suggestions: https://docs.weblate.org/en/latest/admin/machine.html#weblate - I think this will allow us to clone translations for strings that appear multiple times in the sources.

It has been enabled globally for all projects at https://translate.rx.studio/manage/machinery/


Bug: POWERTOOLS_PARAMETERS_SSM_DECRYPT environment variable not respected for get multiple

Expected Behaviour
When the environment variable POWERTOOLS_PARAMETERS_SSM_DECRYPT is set to true, a call to get_multiple parameters should automatically decrypt the values, as is the way with a call to get.
Current Behaviour
The POWERTOOLS_PARAMETERS_SSM_DECRYPT is ignored when calling get_multiple and only the explicit decrypt argument is respected.
Code snippet
from aws_lambda_powertools.utilities.parameters.ssm import SSMProvider
import os

os.environ['POWERTOOLS_PARAMETERS_SSM_DECRYPT'] = 'true'
ssm_provider = SSMProvider()

for _, v in ssm_provider.get_multiple('/some/parameters').items():
    print(v) # Still encrypted

Possible Solution
https://github.com/aws-powertools/powertools-lambda-python/pull/3241
Steps to Reproduce
Please see code snippet
Powertools for AWS Lambda (Python) version
latest
AWS Lambda function runtime
3.10
Packaging format used
PyPi
Debugging logs
No response

Hi @sean-hernon! Thank you so much for reporting this bug and sending the PR to fix it! I'll review it tomorrow so we can merge it.


runtime: fpTraceback fails when trying to take a stack trace of a goroutine in a syscall

After https://go.dev/cl/567076 (for #65634) landed, the runtime began trying to take the frame-pointer-based stack trace of a goroutine in a syscall. Turns out, the runtime had never tried to this before, and it's totally broken.
The main issue is that traceStack tries to use gp.sched.bp but that's not even set when entering a syscall. Worse still, gp.sched in general could get clobbered by calling systemstack. It can then get updated again when switching back to the Go stack (since the syscall path wants to undo the clobbering).
For now, I'm just going to disable getting a stack trace for goroutines blocked in a syscall for the entirety of a generation. To resolve this, what we really need is a gp.syscallbp, akin to gp.syscallpc and gp.syscallsp. The latter two are already used by the regular stack unwinder if available, and they're actually stable, as opposed to gp.sched which gets mutated. Implementing that will be a bigger change, so I'm putting that on the backburner.

Aha! I wondered about this when looking into https://github.com/golang/go/issues/66734.
Adding syscallbp makes sense to me. Perhaps we don't need to completely disable getting a stack trace, though? Could we fall back to the regular non-frame pointer stack trace method if the goroutine has a Gsyscall status? For example, changing this check to add an || readgstatus(gp)&_Gsyscall check to take the slow path.

Yeah, I just went ahead and implemented syscallbp. It wasn't hard.

This PR altered the goid offset, potentially disrupting compatibility with several Go applications that depend on it. For those interested in the latest goid() support, I have updated my goid library here: https://github.com/phuslu/goid.


[RFC] Proposal: introduce new Flint Table concept

Introduction
Currently the fundamental component accessible to users is the Flint Index. In essence, a Flint index represents a derived dataset sourced along with its metadata log for index state management. Physically, the data associated with each Flint index resides within an individual OpenSearch index, ex. flint_{table_name}_skipping_index, while its metadata log is stored as a single document in the shared .query_request_index_{datasource} index.
The current user workflow involves initially creating a Spark table or utilizing existing ones. Subsequently, a Flint index is created on this table. Taking the example of a skipping index, the process is illustrated below:
CREATE TABLE myglue.default.alb_logs
(
    type string,
    time string,
    elb string,
    client_ip string,
    ...,
)
USING JSON
OPTIONS (
  path 's3://alb_logs/'
);

CREATE SKIPPING INDEX ON myglue.default.alb_logs
(
  year PARTITION,
  month PARTITION,
  day PARTITION,
  request_processing_time MIN_MAX,
  client_ip VALUE_SET
)
WITH ( auto_refresh = true );

The utilization of Flint indexes empowers users to opt for various optimization techniques such as skipping index, covering index, and materialized view creation, all aimed at enhancing data retrieval speed from the source table.
Problem Statement
The existing Flint index and user workflow exhibit the following challenges:

Performance

The process of S3 listing during source file discovery incurs high costs. This is presently triggered with each Flint index refresh and therefore leading to performance bottlenecks. https://github.com/opensearch-project/opensearch-spark/issues/218
The coordination between Flint index streaming refresh is also a challenge. https://github.com/opensearch-project/opensearch-spark/issues/93

Compatibility

Users encounter difficulties with creating Flint index on varying Hive table structures. https://github.com/opensearch-project/opensearch-spark/issues/91
Users cannot use partitioned dataset that doesn't follow Hive convention in Spark/Flint. https://github.com/opensearch-project/opensearch-spark/issues/212

Usability

Users often lack guidance in selecting the appropriate type of Flint index and skipping algorithm to create.
For semi-structured data, users may not know the schema until query time. The current need to create a table with all columns causes inconvenience.

Proposed Solution
In this document, our proposal focuses on the introduction of the Flint Table, a higher-level abstraction compared to the Flint Index. Beyond encompassing table schema information and data present in other Spark tables, a Flint table incorporates a new Table Metadata concept enhanced by leveraging the Flint skipping index.
TBD: 1) register metadata as SQL table; 2) covering index/MV under same Flint table concept or not

SQL Interface [TBD]

CREATE TABLE flint_table_name
( column_list )
USING Flint
OPTIONS (
  flint_table_options
);

Examples
Now user can simply create a Flint table and immediately initiate queries on it:

CREATE TABLE myglue.default.alb_logs
(
    type string,
    time string,
    elb string,
    client_ip string,
    ...,
)
USING Flint
OPTIONS (
  path='s3://alb_logs/',
  projection='s3://alb_logs/year=${year}/month=${month}/day=${day}' # partition projection
)
PARTITIONED BY (year, month, day);

For semi-structured data, users can effortlessly create a Flint table, specifying only the columns they intend to use in their subsequent queries:

CREATE TABLE app_logs
(
  @timestamp datetime,
  @message string # field capture entire log line
)
...

SELECT ... FROM alb_logs WHERE status = 200 # implicit @message

Currently assume there is no changes on covering index and materialized view side:

CREATE INDEX elb_status_and_clientip_idx
ON myglue.default.alb_logs
( elb_status_code, client_ip )
WHERE year = 2023 AND elb_status_code = 400
WITH (auto_refresh = true);

CREATE MATERIALIZED VIEW alb_logs_mv
AS
  SELECT window.start_time, COUNT(*)
  FROM myglue.default.alb_logs
  WHERE year = 2023 AND elb_status_code = 400
  GROUP BY TUMBLE(timestamp, 'interval')
WITH (auto_refresh = true);

While the immediate enhancement is the simplified process eliminating the step of creating a Flint index explicitly, the actual influence extends far beyond. As discussed in the upcoming Functionalities section, the semantics of the proposed Flint Table solution introduces a range of features. These features not only streamline the workflow, but also significantly address various issues highlighted in the Problem Statements section.
Functionalities
The interface of the Flint table above provides the following functionalities and semantics:

Automated Metadata Maintenance: With minimum user input, Flint table maintains essential information in its metadata, including source file lists, partition information and column statistics [Solved usability issue]
Semi-Structured Data Handling: Users can provide minimal schema information for semi-structured data, effectively addressing usability concerns related to schema definition. [Solved usability issue]
Validation and Compatibility: Flint table does comprehensive validation and ensure provided table option can function without issues [Solved compatibility issue]
Efficient Metadata Refresh: Flint table utilizes efficient approach to refresh its metadata, such as efficient S3 listing or SNS push mode [Solved performance issue]
Automatic Acceleration: Any direct query or covering index/MV refresh involving a Flint table benefits from automatic acceleration by leveraging metadata. This enhancement includes file listing, partition pruning and data skipping [Solved performance issue]

Future Scope
TODO

Related to semi-structured datatype, Spark 4.0 feature, Support Variant data type, https://issues.apache.org/jira/browse/SPARK-45891


Questions about open source licenses

I am trying to use an open source chart library, but it is marked like the image above.
If private use is listed, is it not possible to use it in our project?

Can you state which library is it? I want to check which license type is used for the library :)

https://github.com/recharts/recharts/blob/master/LICENSE
This chart library! :)

MIT License seems ok :)
But one more check!
Do you want to use the code itself in https://github.com/recharts/recharts or just use the package itself?
More specifically, which one is what you want between following options?

I want to copy & paste the code in https://github.com/recharts/recharts to out repository
I want to just import recharts library like require(recharts)

I want to just import recharts library like require(recharts) :)

Then it seems to have no problem :)
I will let you know later if there were some missing points!

The question has been resolved. thank you.


incorrect size for type - 21gb file size

Tried to parse 21gb europe.osm.pbf
ends with error:
2018/02/23 13:22:21.742922 [WARN] Non-empty /data/valhalla/2 will be purged of tiles
2018/02/23 13:22:22.961088 [INFO] Parsing files: d
2018/02/23 15:44:04.893466 [INFO] Finished with 51415903 routable ways containing 514
2018/02/23 15:59:05.821170 [INFO] Finished with 51415903 routable ways containing 514441587 nodes
2018/02/23 15:59:05.821202 [INFO] Sorting
2018/02/23 16:14:29.174705 [INFO] Finished with 440142 simple restrictions
2018/02/23
2018/02/23 16:29:51.573276 [INFO] Finished with 440142 simple restrictions
2018/02/23 16:29:51.573367 [INFO] Finished with 4 lane connections
2018/02/23 16:29:51.581615 [INFO] Sorting complex restrictions by from id...
2018/02/23 16:29:51.594421 [INFO] Sorting osm way node references by node id...
terminate called after throwing an instance of 'std::runtime_error'
  what():  This file has an incorrect size for type

did you run out of space on the device? that error happens you try to memory map a file and the files size doesnt match the size of the objects that should be in the file (ie the size isnt a multple of the objects that should be in there).

how to pass custom osm.pbf file from github, valhalla.json(newly generated is not giving the output so i have custom json for the pbf file)  to this dockerfile


Error when Administrator tries to delete themself

Call to a member function getUserID() on a non-object is thrown if a administrator (not super admin) goes to the user search, selects themselves, and tries to delete themselves. (Occurs in the release/8.0.0 branch, not sure about develop)
I think we should either not let the user delete themselves via the gui, or we should process the delete and log the user out.  It's seems like kind of a nonsensical thing to do to me so I'd opt for the former.

Uhh should we post a self-deletion hotline number for administrators who might be considering this option?


(C++, USINGZ) InflatePaths with negative delta sets Z value to 0

Hi,
when I use InflatePaths with a positive delta, the Z values in the points are conserved, but with a negative delta, the Z values are set to 0.
Is this intended?
Paths64 subject64;
subject64.push_back(MakePathZ({ 800, 800, 1006, 1200, 800, 1006, 1000, 1200, 1006 }));
Paths64 test64inflated = InflatePaths(subject64, 10, JoinType::Miter, EndType::Polygon);
Paths64 test64deflated = InflatePaths(subject64, -10, JoinType::Miter, EndType::Polygon);

subject64:
x = 800, y = 800, z = 10006
x = 1200, y = 800, z = 10006
x = 1000, y = 1200, z = 10006
test64inflated:
x = 1006, y = 1210, z = 10006
x = 994, y = 1210, z = 10006
x = 784, y = 790, z = 10006
x = 1216, y = 790, z = 10006
test64deflated:
x = 1184, y = 810, z = 0
x = 1000, y = 1178, z = 0
x = 816, y = 810, z = 0

Can anyone reproduce this and/or explain that behaviour to me please?

Yes, i agree

I'll fix it shortly. I've been away on holidays.

Also if the original Z < 0 it always become 0 after offset

OK, I've now had a very good look at this issue - where concave joins will always lose their Z values.
Unfortunately, it's almost impossible to fix this without introducing very complex code.
Even explaining why this is problematic isn't easy.
Basically, concave joins create negative areas in the offset polygons that are later removed in a Union operation.
And it's extremely difficult to associate intersection points in this Union op with vertices in the original paths.
IOW, this won't be fixed and I'll flag this to document it as a library limitation.

On 14.02.24 г. 2:11 ч., Angus Johnson wrote:

OK, I've now had a very good look at this issue - where concave joins
will always lose their Z values.
Unfortunately, it's almost impossible to fix this without introducing
very complex code.
Even explaining why this is problematic isn't easy.
Basically, concave joins create negative areas in the offset polygons
that are later removed in a Union operation.
And it's extremely difficult to associate intersection points in this
Union op with vertices in the original paths.
IOW, this won't be fixed and I'll flag this to document it as a library
limitation.

If Z=nan in such cases it will be easier to fix by postprocessing.
Niki

I've found a way to (mostly) solve this issue of not assigning Z values at concave offsets.


The wramup-ratio of QQP in RoBERTa is 0.25, not 0.06

❓ Questions and Help
What is your question?
Why QQP use the much larger warm-up ratio than other GLUE tasks?
I searched the paper of RoBERTa, and cannot find any explanation.
Code

https://github.com/pytorch/fairseq/blob/master/examples/roberta/README.glue.md#3-fine-tuning-on-glue-task

@ngoyal2707 can you help with this question? thanks very much.

Can someone help with this question? I am having trouble reproducing the results from the paper, and I am wondering if this is the cause.


Persist a Map from SliceID to bound original names

For better visualization we want to know a name for each slice. SliceIDs are ugly.

5827eea5e525b945486161a5b8aa9554c4a05e9d yes!


Removing config annotation does not deregister backends

Removing config annotation anthos.cft.dev/autoneg still left the anthos.cft.dev/autoneg-status annotation, and also generated a controller.autoneg.dev/neg-status annotation.
I would expect autoneg to deregister backends, remove the status annotation, and remove the finalizer.

Please check the latest comment in #88.


FIxed ignored parameters in getTrip

Dear @liodali
Here is a fix for the getTrip interface to the API. I took the liberty to standardize the nomenclature between this implementation, and the official API (geometrie/try to geometries) and fixed one typo in the Doc. If you disagree with the nomeclature changes, please feel free to tell, I'll revert these changes
Yours


useForeignObject

how to set useForeignObject in chartist to be false?
because i want to tansform ForeignObject in svg to canvas , but failed,
so I want to customise this option custom

Hi,
Do you have a code example with just Chartist for what you trying to do ?

finally, I find a way to tansform ForeignObject in svg to canvas through
removeAttr  'xmlns' in 'foreignObject span' for sake of the error about  " reuse namespace "
before svg2canvas:
    $(svg).find('foreignObject span').each(function () {
      $(this).removeAttr('xmlns')
    })


fhir-bucket process should exit after reindex failure

Is your feature request related to a problem? Please describe.
I have a kubernetes job for executing the fhir-bucket client-driven reindex process.
Under certain conditions, I see that failing as follows:
2021-09-09 14:01:06.145 00000001    INFO x.ClientDrivenReindexOperation Starting monitor thread
2021-09-09 14:01:07.476 00000018    INFO x.ClientDrivenReindexOperation called $retrieve-index (afterIndexId=2739214): 200 OK [took 0.401 s]
2021-09-09 14:01:07.479 00000018    INFO x.ClientDrivenReindexOperation Index IDs available for processing - filling worker pool
2021-09-09 14:01:11.124 0000001a    INFO x.ClientDrivenReindexOperation called $reindex (indexIds=2739215,...): 200 OK [took 3.642 s]
...
2021-09-09 14:01:24.818 0000001e    INFO x.ClientDrivenReindexOperation called $reindex (indexIds=2741015,...): 200 OK [took 6.425 s]
2021-09-09 14:02:07.521 00000018    INFO .http.impl.execchain.RetryExec I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://fhir-internal:9443: The target server failed to respond
2021-09-09 14:02:07.522 00000018    INFO .http.impl.execchain.RetryExec Retrying request to {s}->https://fhir-internal:9443
2021-09-09 14:02:07.524 00000018  SEVERE bucket.client.FHIRBucketClient Error while executing the POST request. org.apache.http.NoHttpResponseException: fhir-internal:9443 failed to respond
2021-09-09 14:02:07.524 00000018 WARNING bucket.client.FHIRBucketClient POST URL: https://fhir-internal:9443/fhir-server/api/v4/$retrieve-index
Request Body: {"resourceType":"Parameters","parameter":[{"name":"_count","valueInteger":1000},{"name":"notModifiedAfter","valueString":"2021-06-13T12:00:00Z"},{"name":"afterIndexId","valueString":"2741213"}]}
2021-09-09 14:02:07.525 00000018    INFO x.ClientDrivenReindexOperation Waiting for 60 threads to complete before exiting
2021-09-09 14:02:12.527 00000018    INFO x.ClientDrivenReindexOperation Waiting for 60 threads to complete before exiting
2021-09-09 14:02:17.528 00000018    INFO x.ClientDrivenReindexOperation Waiting for 60 threads to complete before exiting
2021-09-09 14:02:22.529 00000018    INFO x.ClientDrivenReindexOperation Waiting for 60 threads to complete before exiting
2021-09-09 14:02:27.530 00000018    INFO x.ClientDrivenReindexOperation Waiting for 60 threads to complete before exiting
2021-09-09 14:02:32.531 00000018    INFO x.ClientDrivenReindexOperation Waiting for 60 threads to complete before exiting
2021-09-09 14:02:37.533 00000018    INFO x.ClientDrivenReindexOperation Waiting for 60 threads to complete before exiting
2021-09-09 14:02:42.534 00000018    INFO x.ClientDrivenReindexOperation Waiting for 60 threads to complete before exiting
2021-09-09 14:02:47.536 00000018    INFO x.ClientDrivenReindexOperation Waiting for 60 threads to complete before exiting
...
2021-09-09 14:01:24.818 0000001e    INFO x.ClientDrivenReindexOperation called $reindex (indexIds=2741015,...): 200 OK [took 6.425 s]
2021-09-09 14:07:07.661 00000018  SEVERE x.ClientDrivenReindexOperation Reindexing was not fully completed, restart reindex from index ID '2741213' to resume
Exception in thread "Thread-4" com.ibm.fhir.database.utils.api.DataAccessException: FHIR server connection failed
	at com.ibm.fhir.bucket.client.FHIRBucketClient.post(FHIRBucketClient.java:315)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.callRetrieveIndex(ClientDrivenReindexOperation.java:315)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.monitorLoop(ClientDrivenReindexOperation.java:204)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.lambda$init$0(ClientDrivenReindexOperation.java:123)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation$$Lambda$50/0x0000000000449100.run(Unknown Source)
	at java.base/java.lang.Thread.run(Thread.java:836)

However, the job is still has a status of running which means that the process has never exited.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A. System.exit after some time of waiting
B. Keep as-is and deal with outside of fhir-bucket (e.g. by add some kind of timeout to the job)
Acceptance Criteria

GIVEN [a precondition]
AND [another precondition]
WHEN [test step]
AND [test step]
THEN [verification step]
AND [verification step]

Additional context
Add any other context or screenshots about the feature request here.

Same issue as https://github.com/IBM/FHIR/pull/2225

To verify, I ran a large reindex job with 60 threads.
After the first few requests, it hit a case where the server does not respond (due to an environmental issue I think).
I think this used to cause the reindex process to exit, but now it was able to recover and continue running, as seen in the last couple messages:
2021-09-20 19:47:30.149 00000012    INFO x.ClientDrivenReindexOperation called $reindex (indexIds=1901,...): 200 OK [took 1.370 s]
2021-09-20 19:48:22.116 0000000c    INFO .http.impl.execchain.RetryExec I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://fhir-internal:9443: The target server failed to respond
2021-09-20 19:48:22.117 0000000c    INFO .http.impl.execchain.RetryExec Retrying request to {s}->https://fhir-internal:9443
2021-09-20 19:48:22.120 0000000c  SEVERE bucket.client.FHIRBucketClient Error while executing the POST request. org.apache.http.NoHttpResponseException: fhir-internal:9443 failed to respond
2021-09-20 19:48:22.121 0000000c WARNING bucket.client.FHIRBucketClient POST URL: https://fhir-internal:9443/fhir-server/api/v4/$retrieve-index
Request Body: {"resourceType":"Parameters","parameter":[{"name":"_count","valueInteger":1000},{"name":"notModifiedAfter","valueString":"2021-06-13T12:00:00Z"},{"name":"afterIndexId","valueString":"1999"}]}
2021-09-20 19:48:22.121 0000000c  SEVERE x.ClientDrivenReindexOperation Throwable caught. FHIR client thread will exit

FHIR server connection failed
com.ibm.fhir.database.utils.api.DataAccessException: FHIR server connection failed
	at com.ibm.fhir.bucket.client.FHIRBucketClient.post(FHIRBucketClient.java:315)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.callRetrieveIndex(ClientDrivenReindexOperation.java:321)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.monitorLoop(ClientDrivenReindexOperation.java:204)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.lambda$init$0(ClientDrivenReindexOperation.java:123)
	at java.base/java.lang.Thread.run(Thread.java:829)
2021-09-20 19:48:22.125 0000000c    INFO .http.impl.execchain.RetryExec I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://fhir-internal:9443: The target server failed to respond
2021-09-20 19:48:22.126 0000000c    INFO .http.impl.execchain.RetryExec Retrying request to {s}->https://fhir-internal:9443
2021-09-20 19:48:22.128 0000000c  SEVERE bucket.client.FHIRBucketClient Error while executing the POST request. org.apache.http.NoHttpResponseException: fhir-internal:9443 failed to respond
2021-09-20 19:48:22.129 0000000c WARNING bucket.client.FHIRBucketClient POST URL: https://fhir-internal:9443/fhir-server/api/v4/$retrieve-index
Request Body: {"resourceType":"Parameters","parameter":[{"name":"_count","valueInteger":1000},{"name":"notModifiedAfter","valueString":"2021-06-13T12:00:00Z"},{"name":"afterIndexId","valueString":"1999"}]}
2021-09-20 19:48:22.130 0000000c  SEVERE x.ClientDrivenReindexOperation Throwable caught. FHIR client thread will exit

FHIR server connection failed
com.ibm.fhir.database.utils.api.DataAccessException: FHIR server connection failed
	at com.ibm.fhir.bucket.client.FHIRBucketClient.post(FHIRBucketClient.java:315)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.callRetrieveIndex(ClientDrivenReindexOperation.java:321)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.monitorLoop(ClientDrivenReindexOperation.java:204)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.lambda$init$0(ClientDrivenReindexOperation.java:123)
	at java.base/java.lang.Thread.run(Thread.java:829)
2021-09-20 19:48:22.133 0000000c    INFO .http.impl.execchain.RetryExec I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://fhir-internal:9443: The target server failed to respond
2021-09-20 19:48:22.134 0000000c    INFO .http.impl.execchain.RetryExec Retrying request to {s}->https://fhir-internal:9443
2021-09-20 19:48:22.139 0000000c  SEVERE bucket.client.FHIRBucketClient Error while executing the POST request. org.apache.http.NoHttpResponseException: fhir-internal:9443 failed to respond
2021-09-20 19:48:22.140 0000000c WARNING bucket.client.FHIRBucketClient POST URL: https://fhir-internal:9443/fhir-server/api/v4/$retrieve-index
Request Body: {"resourceType":"Parameters","parameter":[{"name":"_count","valueInteger":1000},{"name":"notModifiedAfter","valueString":"2021-06-13T12:00:00Z"},{"name":"afterIndexId","valueString":"1999"}]}
2021-09-20 19:48:22.140 0000000c  SEVERE x.ClientDrivenReindexOperation Throwable caught. FHIR client thread will exit

FHIR server connection failed
com.ibm.fhir.database.utils.api.DataAccessException: FHIR server connection failed
	at com.ibm.fhir.bucket.client.FHIRBucketClient.post(FHIRBucketClient.java:315)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.callRetrieveIndex(ClientDrivenReindexOperation.java:321)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.monitorLoop(ClientDrivenReindexOperation.java:204)
	at com.ibm.fhir.bucket.reindex.ClientDrivenReindexOperation.lambda$init$0(ClientDrivenReindexOperation.java:123)
	at java.base/java.lang.Thread.run(Thread.java:829)
2021-09-20 19:48:22.143 0000000c    INFO .http.impl.execchain.RetryExec I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://fhir-internal:9443: The target server failed to respond
2021-09-20 19:48:22.143 0000000c    INFO .http.impl.execchain.RetryExec Retrying request to {s}->https://fhir-internal:9443
2021-09-20 19:48:22.229 0000000c    INFO x.ClientDrivenReindexOperation called $retrieve-index (afterIndexId=1999): 200 OK [took 0.087 s]
2021-09-20 19:48:23.074 00000022    INFO x.ClientDrivenReindexOperation called $reindex (indexIds=2059,...): 200 OK [took 0.842 s]

If the reindex job completes, I think we can close this one as resolved.

2021-09-20 22:59:34.575 0000000c    INFO x.ClientDrivenReindexOperation Reindexing was completed
2021-09-20 23:00:34.545 0000000b    INFO   com.ibm.fhir.bucket.app.Main Stopping all services


Read the Primary from the Cache on Reconcile Start

Currently the primary resource is read from the cache before the resource is submitted to the executor before the reconciliation. If there is high load the actual reconciliation process might start significantly later. So when if primary resource is updated in between, we will process an older version of the primary while the new version is already in the cache. Reading the resource from the cache when the reconciliation actually starts will make to work on up to date primary resource (well that is known to the operator).
On the other hand this might lead to a double processing of the resource.  Since the event from the primary change will mark the processor to make it reconcile again. We might however handle this situation, thus not marking the resource to reconcile if a resource with a same version is already submitted for reconciliation.

Can you detail under which circumstances, there would be such a high load that the SDK wouldn't process the primary soon enough? Slow dependent reconciliation? Load on the operator process or the Kubernetes API server?

With the current default settings there does not needs to such high load. Basically now the fixed thread pool for executor has size of 5 (maybe double this at least for default?) :
https://github.com/java-operator-sdk/java-operator-sdk/blob/f15f948e5af18ac2e3642c739b3e309af5090187/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/ConfigurationService.java#L83-L83
If the reconciliation takes long (calls for external APIs) then those 5 threads could be easily used up. The execution scope is created here before submit: https://github.com/java-operator-sdk/java-operator-sdk/blob/f15f948e5af18ac2e3642c739b3e309af5090187/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/event/EventProcessor.java#L139-L139
So it's actual execution could be delayed.
Also seen related issue with patch. Since we don't put resource into temp cache after reconcile. And there were events meanwhile for the resource (from event sources or cr), the execution will start without the fresh resource. However, typically seen in Flink operator logs that, when the executor service actually  executes the dispatcher meanwhile the resource event from patch arrived and was already in cache.
The double processing as mentioned is a problem, but that we can handle with an in memory state.
So at the end this issue is an optimization (not about correctness), but might help actually in significant number of cases.

I think we should expose some metrics about it. Contention detection could work too. But maybe an better approach is to delegate it to tools like Prometheus. So there is history also about that. Since having some temporal spikes is could be normal, and not sure if an issues is just temporal the thread pool should be increased, probably not.
So probably doing such decision is the best by observing history not a point in time.

Yes, was thinking about using metrics for that in a first step, indeed. Coupled with alerting (for people who are interested in such signal) would work nicely enough, imo.


Add recently searched text in the search

Checklist

[x] Bug Report - The issue you are reporting might be there already. Please search on the issues tracker before creating or reporting an issue.
[x] Before reporting, please ensure (if you can) that you have tested it with the latest (dev) version of the software.
[x] Don't forget to tag your issue, it makes it easier to discover.
Summary:

Add recently searched text in the search
Steps to reproduce:
How can we reproduce the issue?
Device and Android version:
Android 8.1 (API 27) Asus Zenfone MAx M1 pro
Screenshots:

I would like to work on this

@teolemon  whats your view on this??


[Mono] Exported List of enum values gives incorrect values when loaded

Godot version:
v3.2.3 Mono (Stable)
OS/device including version:
Windows 10
Issue description:
Exported lists of enums give bad values once loaded. Editor and data files have the correct expected values, but once loaded are shown to be invalid. They appear to alternate between seemingly random values and 0.
This appears to be consistent over exported script variables and resources.
Steps to reproduce:

Create a scene with a Node with a CSharp script.
Within the script declare an enum called TestEnum, with values VALUE_0, VALUE_1, VALUE_2.
Within the class, create an exported property of a List.
Within the class, in the _ready method, write a for loop and print statement to print the values of the list.
From the editor, increase the list size to ~6 and optionally, set the values.
Run the code, and observe that the values that are printed out are incorrect.

Minimal reproduction project:
Attached is a minimal reproduction project. It has a single scene with a single Node2D with script attached. The script loads a resource (containing exported enum list) and also contains an exported list filled with the same enum type
. It prints one list then the other when run. There are no visual elements to this project.
EnumBug.zip
Sample output
Values from resource:
Value: 533223456
Value: 0
Value: 533223480
Value: 0
Values from member:
Value: 533220256
Value: 0
Value: 533220280
Value: 0
Value: 533220304
Value: 0
Expected output
Values from resource:
Value: 0
Value: 1
Value: 2
Value: 0
Values from member:
Value: 0
Value: 0
Value: 0
Value: 2
Value: 1
Value: 0

Duplicate of https://github.com/godotengine/godot/issues/42926.

Believe it or not I did search before posting. Was looking specifically for lists though, which is maybe why I didn't find it.
Confirmed duplicate. Same issue.


Add reorderable list component

Add reorderable list component to be used for reordering attachments in Publications.
Preview
Desktop

JavaScript enabledJavaScript disabled

Mobile

JavaScript enabledJavaScript disabled

Screen reader instructions
Examples using VoiceOver

JavaScript enabledJavaScript disabled

Move Budget 2018 up, button, list 5 items.

Order index for Budget 2019, edit text, list 5 items

Notes:

Raised this early for visibility and feedback.
JavaScript tests to be added – currently trying to work out how to test the responsive behaviour in Jasmine.

Trello card

We need to think about the data this element will submit. Firstly, the order_index inputs will need to be kept in-sync when elements move on the page. Secondly, we need to know which index goes with each element. There are a couple of ways we could do this. I think the easiest option is for each item to have an original_order_index[], so we can work out how the items have moved.

I was hoping that we can save users from some JavaScript being served and computations being done after each move by exposing a reversed attribution `input-name[new_index]=old_index.
I'll try and exemplify how I envisioned the order submission would work:
no-js: before reorder
reorderable-list[0]=1
reorderable-list[1]=2
reorderable-list[2]=3

no-js: after reorder (users manually replacing the 2 with 1 in the first input and vice-versa for the second)
reorderable-list[0]=2 #the second item will get index 0
reorderable-list[1]=1 #first item will get index 1
reorderable-list[2]=3 #third item remains the same

js enabled: before reorder (after script is being executed)
reorderable-list[]=1
reorderable-list[]=2
reorderable-list[]=3

js enabled: after reorder
reorderable-list[]=2
reorderable-list[]=1
reorderable-list[]=3

Now looking at it may work fine, but what I'm not capturing here is how do proceed when we have custom item IDs. I'm trying to figure out what a new set of inputs storing original_order_index would involve (both frontend and backend) – maybe we can catch-up on this.

We seem to lose the focus states for the Up/Down buttons on click and on "Enter". I think there may be a general point there about indicating the element that was moved.

Great point. I've updated the code to preserve the focus.

There's something weird going on with the drag/drop, which I can demo in person: sometimes the item 'jumps' downward and then returns to its current position.

Thanks for demo-ing this bug. I've updated the code to fix this.

There's a slight inconsistency in the total space of the buttons for the first/last items. Probably not a big deal, but I thought I'd mention it, since we were concerned about it in the first commit.

Updated the code to fix these inconsistencies.

My screen reader is seeing the first 'Down' button as a list of 5 buttons. I had a quick Google but can't immediately see the reason for this - I'm guessing it's reading down the 'column'.

It's a standard way for screen readers to let you know this is an element in a list of 5 items – valuable information when you're reordering.

When using my screen reader I found the 'Move' help text confusing, since it sounds like it's part of the title. Can we make the label just Move Up and "aria-describedby" the title?

Replied in an inline comment below; I consider the aria-label suggestion as being more practical that aria-describedby – regardless it requires an update on the button component.

One last comment from me!
Been thinking about how best to represent the ordering. I think the backend can be kept very simple (no need to pass a original_order_index, or indeed any index) and frontend needs to render only one input:
<% items = [{ id: 43, type: "FileAttachment"}, { id: 37, type: "FileAttachment" }] %>
<% # ^ example output from backend %>
<% items.each_with_index do |item, index| %>
  <input type="text" name="order_for_item_#{item.id}" value="#{index}" />
<% end %>

NoJS version: user can edit the value of the input, and submit the form. JS version: user can drag-and-drop (or use buttons) to move the element around; the JS should update the value of all inputs automatically. Then form submission would be something like:
def reordered_items
  items.sort do |a, b|
    params["order_for_item_#{a.id}"].to_f <=> params["order_for_item_#{b.id}"].to_f
  end
end

Although it's nice submitting an input array (as that shows some relationship between the inputs), I think this approach is simpler as it means not having to maintain two separate arrays for original and new ordering.

@ChrisBAshton thanks for the suggestion. I can see a couple of problems we would encounter when we come to implementing it, which make me think we should still with the two-array approach:

Each item would be a different parameter. This means we would have to manually extract each one from the params by name, instead of a single array. It's also a bit of a smell that a group of related values aren't actually grouped, except by a common name.
The ID of featured attachments is not unique, since it depends on a combination of the database ID and the type of attachment model we're referring to, as mentioned on the card about reordering. We did explore this approach, but believe it's simpler to focus the data around the order, not IDs.

We wouldn't necessarily have to use .id - we could pass some combination of id and attachment type to the frontend. So long as it's globally unique - and reversible - the frontend doesn't need to know how we've arrived at the ID, we're only using it ephemerally and can change our implementation of the ID over time if needed.
I do agree about the code smell 👍 I've thought more about your proposed implementation - I think what you're proposing is this:
<%
  items = [
    { id: 43, type: "FileAttachment", order_index: 1, original_order_index: 1 },
    { id: 37, type: "FileAttachment", order_index: 2, original_order_index: 2 }
  ] %>
<% # ^ example output from backend %>

<% items.each do |item| %>
  <input type="hidden" name="original_order[]" value="#{item.original_order_index}" />
  <input type="text" name="new_order[]" value="#{item.order_index}" />
<% end %>

...on form submission, we'd have something like:
def reordered_items
  # params["original_order"] # ["1", "2", "3"] # I don't think we'll need to use this!
  # params["new_order"] # ["2", "1", "3"]

  params["new_order"].map do |old_index|
    items[old_index.to_i]
  end
end

This, too, can be simplified I think 🤔
<% items = [{ id: 43, type: "FileAttachment"}, { id: 37, type: "FileAttachment" }] %>
<% # ^ example output from backend %>
<% items.each_with_index do |item, index| %>
  <input type="text" name="new_order[]" value="#{index}" />
<% end %>

Form submission:
def reordered_items
  # params["new_order"] # ["2", "1", "3"]

  params["new_order"].map do |old_index|
    items[old_index.to_i]
  end
end

Either way, I don't think the backend needs to pass additional array(s) of orderings. They can be inferred by the order of the items array and some clever manipulation of the form DOM.

Chatted IRL with Ben, I now see the issue 😅
* ('foo' param added to disambiguate each input, since their values can change)

<input foo="bar" val="1">
<input foo="baz" val="2">
<input foo="tom" val="3">

<input foo="tom" val="3">
<input foo="bar" val="1">
<input foo="baz" val="2">

...would give form params of: [3, 1, 2]
...which could be mapped to: [tom, bar, baz]
...great!

But the noJS version wouldn't use ordering, it would involve changing the values:

<input foo="bar" val="2">
<input foo="baz" val="3">
<input foo="tom" val="1">

...would give form params of: [2, 3, 1]
...which would be mapped to: [baz, tom, bar]
...and NOT [tom, bar, baz] as we wanted!

Not sure why that took so long to click!
And to clarify, the suggested implementation is:
<% items = [{ id: 43, type: "FileAttachment"}, { id: 37, type: "FileAttachment" }] %>
<% # ^ example output from backend %>

<% items.each_with_index do |item, index| %>
  <input type="hidden" name="original_order[]" value="#{index}" />
  <input type="text" name="new_order[]" value="#{index}" />
<% end %>

(i.e. we will not pass any extra params from the backend. Rather, it is the frontend that will pass the ordering params to the backend).

@ChrisBAshton Thank you for the review and for trying to find a way to only use one input. I've been 'seduced' by the same drive to reduce the number of inputs, but it seems like it just doesn't fit with the requirements.

@alex-ju I think @kevindew is planning to comment, so this is just a pre-emptive warning. After talking with @kevindew, we think there's a better approach we can take to solving the ordering approach in the backend - sorry for so many iterations! The quick summary is:

introduce an extra UUID into the ordering data we store (and rename id/type to attachment_X)
have a single params hash that's set like attachments[uuid]=<order_index> to represent the reordering

So each item/attachment still needs to arguments set, but we're proposing to use them differently.

Ah yes it was taking me a while to get the notes down. I've just had a chat with Ben about the parameters here and I'm summarising it here.
Two parameter fields
We talked about the need for two parameter fields, the working understanding was that we would need two input fields for example:

  <input type="hidden" name="previous_ordering[]" value="0" />
  <input type="text" name="new_ordering[]" value="2" />

Where this would look up the item in the file attachment ordering at item 0 and then move that item to be at position 2.
We've identified that this could be resolved with passing the id in as part of the params. For example:

  <input type="text" name="ordering[0]" value="2" />

Where the ordering hash could be looped through and the item at 0 could then be moved to position 2.
Using the ordering as an id
We then talked about the risks in using the ordering as index to look up which items should have its position moved. We talked in a particular about a concurrent editing situation where for example: An editor asks a slack room for someone to move a CSV to the top of the list of featured attachments. If both Kevin & Ben load the page before the other has submitted their edits the first person (Ben) to submit the form will achieve the ordering as expected, whereas when Kevin submits it the data submitted on current ordering will be out of date and will undo the changes Ben made.
To resolve this we talked about what could be used as an id and came up with perhaps using a UUID. The effect of this could be changing the featured attachment array to something like:
[
  { id: "696d2cfb-b97a-479f-952a-abcef0c1c88e",
    attachment_type: "FileAttachment",
    attachment_id: 123 },
  { id: "217ab88f-74a9-41eb-ab47-428f54461c02",
    attachment_type: "HtmlAttachment",
    attachment_id: 456 }
]

and then changing the input approach to something like:

  <input type="text" name="ordering[696d2cfb-b97a-479f-952a-abcef0c1c88e]" value="1" />

So I'm guessing we'd end up with something along these lines to do the ordering (where the infinity is used to push any items missed from submission to the end of the list and doing nothing can have them at the start):
id_1, id_2, id_3 = 3.times.map { SecureRandom.uuid }
file_attachments = [{ id: id_1 }, { id: id_2 }, { id: id_3 }]
submission = { id_1 => "1", id_2 => "0" }
ordering = submission.sort { |a, b| a.last.to_i <=> b.last.to_i }.map(&:first)
sorted = file_attachments.sort_by { |a| ordering.index(a[:id]) || Float::INFINITY }

To resolve this we talked about what could be used as an id and came up with perhaps using a UUID.

Thank you for the comment @kevindew. Coping with concurrency was what I was thinking when I referred to 'custom item IDs' above, and in previous discussions. What I wasn't sure about was how permissive the index is in terms of character types (e.g inputname[696d2cfb-b97a-479f-952a-abcef0c1c88e] which contains -) but I imagine it's flexible enough. I updated the code to support custom indexes again, only that now both inputs will share the same index.

I've added a bunch of comments. I also was a bit confused about whether some of the existing ones were pending response/resolution?

Thank you, @kevindew. I tried to reply to them all.

@ChrisBAshton, sure I will. I don't expect to get this merge anytime sooner, as it needs refactoring after the requested changes in govuk_publishing_components.

Updated screenshots, updated the code to profit from the changes introduced in govuk_publishing_components for buttons and inputs. Unfortunately, I've only got support in using custom classes for js- selectors (which cleans the JavaScript code a bit), but not for styling (which leaves us with things like gem-c-button:first-of-type in our code). I'll try and raise the custom classes topic again in community discussions. I hope I addressed and/or reply to all queries and suggestions.


[Crunchyroll] Edit Metadata Season

Checklist

[X] I'm reporting a feature request
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2<IP_ADDRESS>. (update instructions)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
Currently for series that have only one season the season number appears as 0 (when I use %(season_number)s), this request is to change this to 1. Unless these are problems directly from the Crunchyroll website.

Open a "Site feature request" with all necessary details

Open a "Site feature request" with all necessary details

Ok


Add UTC -2:30 as a valid offset.

At the moment parsing a string like 2019-07-17T12:30:00.000-02:30 doesn't work, because -02:30 is not present in the valid offsets list.
Timestamps with this offset are observed in Newfoundland Time Zone (NT) during daylight saving time (NDT timezone). This offset is not listed on the linked wikipedia page of UTC time offsets, because "Places that observe daylight saving time (DST) during their respective summer periods are listed only once, at the offset for their winter (usually known as "standard") period;"

Hi all! A friendly reminder - anything holding back a merge of this PR?


Fix dependabot grouping

Clear release notes
Fix typo in dependabot grouping
Prepare release notes for release v0.6.1

Force-merging because it is a trivial fix and we need to merge to find out if it now really works anyway.


Pin dependencies in examples

Signed-off-by: Kern Walster<EMAIL_ADDRESS>Issue #, if available:
N/A
Description of changes:
The version of x/sys used in the examples uses unsafe.Slice which was introduced in go1.17, but we support back to go1.14. This change downgrades x/sys to the same version used in the rest of the firecracker-go-sdk.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Looks like the buildkite pipeline installs a plugin as well. We can probably replace that with an explicit make target call to install or let make dependencies handle it.
Reference: https://github.com/firecracker-microvm/firecracker-go-sdk/blob/da8e44af507a3cc6e6dab14c5e4a13d9cf539f38/.buildkite/pipeline.yml#L80

The load snapshot integration tests will intermittently fail which #418 is trying to address. That is outside the scope of this change which is why I reran for the green.

@Joffref This will take the place of your PR. Can you please take a look?

@Kern-- LGTM.
Also, you can mention that it closes issue #446.


Fix pinned items don't show up in home

Related to https://github.com/stackernews/stacker.news/pull/783#issuecomment-1925919942
TODO:

[x] ~make sure pinned posts don't disappear from recent, too~ (that was already the case)

Oh nice catch! For some reason I thought my other changes fixed this


CIGAR and query sequence lengths differ for reads in smoothed.selective.bam

Hi,
I was trying to use this exciting tool to call SVs using HiFi reads on a genome assembled from those same reads.
I can run SVDSS index and SVDSS smooth. The file smoothed.selective.bam is generated. When I run SVDSS search --assemble the process completes generating files called solution_batch_*.assembled.sfs, but the log contains the samtools error  [E::bam_read1] CIGAR and query sequence lengths differ for m64069_220917_213940/14419164/ccs multiple times for different reads.
Because of this, I am unable to generate an index for the BAM
$ samtools index smoothed.selective.bam
[E::bam_read1] CIGAR and query sequence lengths differ for m64069_220917_213940/163645521/ccs
samtools index: failed to create index for "smoothed.selective.bam"

Meaning I cannot complete the pipeline.
I am able to index the BAM input to SVDSS smooth without issue.
I have tried to filter the BAM for primary reads, but I run into the same problem.
Please let me know if you have any advice to overcome this issue.
Thanks
Kyle

Hi Kyle, thanks for trying SVDSS out.
I encountered a similar issue some times ago, I tried to solve it with no success and then I forgot to go back to it..
Just to be sure that the issue is the same, can you please try to use the SVDSS version you find in the lowcov branch? Unfortunately, you'll have to compile it from scratch since it's a development branch and I didn't produce the binary yet..
I suspect that for those alignments, in the new version you should see a line starting with |. Something like:
| m64069_220917_213940/163645521/ccs xxxxx xxxxxxx

(where xxxxx are numbers).
If this is the case, I'll try to fix it.
If you have any issue, please let me know. Other way to check this (in case you encounter any issue while compiling):

you can send me a bam with the original alignment that fail (so I'll try to reproduce the error)
I can provide you a binary (but it'll take a bit more time)

Let me know what you prefer.
Best,

Hi,
I got the same error. I used pbmm2 to map raw fastq files and used the mapped bam files as input to SVDSS. After using smooth to obtain the smoothed.selective.bam file, I have the same problem. Below are the first 10 lines of smoothed.selective.bam. Do you have any thoughts on this issue?
Thanks,
Yh
[2-svdss]$ samtools view smoothed.selective.bam | head | cut -c 1-80 m54337U_221231_061623/144640562/ccs     0       1       32442   46      1685S3=1X6=1X5=2D14=1X2=1X2=1I2 m54337U_221231_061623/40501721/ccs      16      1       34529   47      13S3=1X6=1X1=1X4=1X7=1X1=2X10=2 m54337U_221229_210659/167772847/ccs     0       1       39016   60      16S129=1I224=1X223=1X2=1X401=1X m54337U_221231_061623/48891338/ccs      16      1       41572   37      15S142=1X102=22I76=1X97=1X119=1 m54337U_221231_061623/55642959/ccs      16      1       43466   41      123S8=1X5=1X4=1X6=1X3=1X6=1X3=1 m54337U_221229_210659/139004586/ccs     16      1       45080   30      62S136=1X373=1X109=1X82=1X59=1 m54337U_221229_210659/15860237/ccs      0       1       49121   60      18S10=1X10=1X2=1X4=1X6=2X1=1X1=1 m54337U_221231_061623/135398753/ccs     2064    1       52978   30      16S5=1X2=1X6=1D1X2=1X19=1X3= m54337U_221231_061623/54004238/ccs      0       1       54175   38      8058S5=1X4=1I5=2X8=1X9=1I10=1X2= m54337U_221231_061623/132055825/ccs     16      1       54364   41      16S91=1X64=1X49=1X7=1X213=1X14

Thanks for the response,
I cloned and compiled from the lowcov branch git clone -b lowcov https://github.com/Parsoa/SVDSS.git and can confirm the expected output from SVDSS smooth
[I] Loading first batch..
|m64069_220917_213940/119343055/ccs 6 34509
|m64069_220917_213940/30672650/ccs 4 32868
|m64069_220917_213940/2884910/ccs 36358 36360
|m64069_220917_213940/92735840/ccs 32692 32697
|m64069_220917_213940/137824722/ccs 4 34365
|m64069_220917_213940/75367744/ccs 4 31994
|m64069_220917_213940/67633453/ccs 4 29212
|m64069_220917_213940/130025065/ccs 4 27036
|m64069_220917_213940/153945456/ccs 4 19448
|m64069_220917_213940/172427254/ccs 4 21069
|m64069_220917_213940/19465819/ccs 4 20898
|m64069_220917_213940/3998562/ccs 4|m64069_220917_213940/142673267/ccs 6 33368
 41157
|m64069_220917_213940/105841111/ccs 4 31923
|m64069_220917_213940/61081766/ccs 4 19399
||m64069_220917_213940/139266167/ccs 6 32847
|m64069_220917_213940/93456725/ccs 4 31757
m64069_220917_213940/85919307/ccs 6 34644

samtools index now runs ok on smoothed.selective.bam.
SVDSS search--assemble appears to run without issue.
SVDSS call provides an Illegal instruction (core dumped) error.
Thanks

I see. Well, at least we found the problem. I'll fix the smooth and let you know.
In the meantime, can you please try to run the SVDSS call step using the v1.0.4 release? If it crashes, please open a new issue - otherwise it's a bug in the dev branch (for sure I messed something up).
@YahGao I suspect your error is the same, so I'll let you know when it's solved.
Best,

I think I've fixed this. Please, check the new commit on the lowcov branch.
So pull, recompile, and rerun the smoothing. You shouldn't see any warning anymore (or line starting with |). And the produced .bam should be correct.. Please let me know if this is not the case.
Regarding the SVDSS call issue, let me know how it's going and/or open a new issue.
Best,

Please check the latest release v1.0.5. This bug should be fixed now.