Tidy of components + added storybook.js

Improvements

Moved all components into a single directory like next.js does. The components we getting really messy and the sub-directories weren't helping, this is a push to make it easier. There is still some work to do, but this is a good start
Made component names consistent with each other, they all prefix rather than suffix <FieldNumber/>, <FieldArray/> for example
Made component names consistent with their export class names. Previously the class IconLayer {} wasn't always consistent with the filename of the component
Added storybook for a few components with the aim to extend this across all the fields, and maybe further (see screenshot)
Add storybook as a CI artifact

Storybook allows for easier improvement/testing of existing/new components in a standalone way. Here's a screenshot of the current components.

(Note: Missing fonts is a known issue, will fix that in a later PR)

You can see storybook artifact in https://github.com/maputnik/editor/actions/runs/121594306

I've added a bunch more components to the storybook and also the a11y addon

Note: Some of the accessibility errors aren't actually errors, but things that don't make sense in the current context of the component. Currently I'm just ignoring those at the moment, but later on we should find out a way to disable them.

Merging to make it easier to start work on #319, any feedback please leave in this ticket and I'll look at it retrospectively


stake-pool: Update tests for 1.17

Problem
The SPL downstream tests were disabled in https://github.com/solana-labs/solana/pull/32524, but we need to re-enable the downstream tests to avoid breaking people in the future, per https://github.com/solana-labs/solana/pull/32655.
After doing the work to reinstate the old StakeState and re-enabling the downstream tests, there were errors in the stake pools tests.
Solution
The biggest change relates to the async rewards payout being implemented for https://github.com/solana-foundation/solana-improvement-documents/pull/15 -- we have to warp to slot + 1 in order to get out of the rewards payout time.
After that, there was one issue where we weren't serializing 200 bytes for stake accounts in a test.
And a little extra thing, I noticed that retain in the stake pool program was using a function pointer instead of a closure, so I changed to be a closure, same as all the other big_vec functions. This should improve compute-unit performance because the Rust compiler can inline closures, but not calling into function pointers.

otherwise lgtm


View error

I just installed this on my Laravel 9.52.4 project with PHP 8.0.23.
But I get error
Declaration of Vildanbina\LivewireTabs\Components\Tab::view(string $view): static must be compatible with Illuminate\View\Component::view($view, $data = [], $mergeData = [])

I think public function view(string $view): static must be changed to public function viewContract(string $view): static on L:92 in Components/Tab.php regarding https://github.com/laravel/framework/commit/28e0f61bba1cbc727383d183b7116eb723de7660

Merged! thank you for your contribution


[WIP] Implement inclusion proof generation and verification

Do not merge yet!
TODO

[x] Address https://github.com/SpinResearch/merkle.rs/pull/1#discussion_r88053466
[x] Remove MerkleTree::is_proof_valid
[x] Look for better function names
[x] Refactor tests
[x] Add more tests
[x] Write doc

Merged squashed as https://github.com/SpinResearch/merkle.rs/commit/b4cd7537b5a5474b88b95205ac753b322f9e93d7


heuristics: add network machines list

-pcap stats and dns verify both need to maintain list of in-network machines (from onos nab)
-integrate with rabbitmq and uncomment connection and callback handler installer

OBE


Nested items are still revealed after deselecting / removing the answer for the parent item

Describe the bug
The SDC has a feature which hides nested items until the parent item has been answered. On removing the answer/ deselecting the option , the nested items are still visible and do not go back to the hidden state.
Component
SDC library
To Reproduce
Steps to reproduce the behavior:

Go to datacapturegallery app.
Click on Neonate record from New South Wales, Australia
Scroll down to Hep B give y/n
Press the checkbox - Date given will appear
Uncheck the check box - Date given remains

Expected behavior
Date given is supposed to go back to hidden state
Screenshots

Smartphone (please complete the following information):

Device: One plus 7T pro
Android version: 10
Build number: QKQ1.200909.002

Originally reported by @f-odhiambo

@joiskash, can I work on this?

Sure , it fine by me :) cc: @Tarun-Bhardwaj @jingtang10

thanks for creating this issue!

repeating here what i posted in the PR: see this discussion:
https://chat.fhir.org/#narrow/stream/179255-questionnaire/topic/EnableWhen.20behavior.20with.20operator.20.60exists.60
Basically i think this is expected behavior - we probably need to render boolean questions as 3 radio buttons yes / no / [empty] rather than just a checkbox. this is becase an answer 'false' is still an answer and will make nested items appear.

same applies to multiple choice questions -- if you can choose a list of codes you must be able to clear the answer also

@maanuanubhav999 are you working on this issue?

@Tarun-Bhardwaj  yes.

@maanuanubhav999 , could you please provide an ETA for completing the code changes?

@Tarun-Bhardwaj  I was having some trouble with the instrumental test otherwise the PR was ready.  If the tests start working, 4-5 days.

@Tarun-Bhardwaj I was having some trouble with the instrumental test otherwise the PR was ready. If the tests start working, 4-5 days.

@maanuanubhav999 , any progress on this issue?

Hi, @Tarun-Bhardwaj I will update in 1-2 days. thanks


Change test install package from php to php-cli.

Description
The "php" package tends to bring in unnecessary side dependencies, such as http, etc.
"php-cli" will install only php and what's necessary to get it working from the CLI.
This should fix the problems with centos-5 tests.
Issues Resolved
No existing issues.
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[X] New functionality includes testing.
[X] New functionality has been documented in the README if applicable
[X] The CLA has been signed. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

This looks like it's still failing for Centos 5.

Yeah. It seems to be timing out now rather than failing due to dependency conflicts. Let me see how it works after rebasing.

Well using mirrorlist seems to have gotten it to pass at least one of the failing tests. I can't really tell if it's due to a fault in the CentOS 5 docker container or a networking problem.

Hmm, yeah it does seem to be timeouts. Well I'm going to pull this in, and we'll see if the timeout is resolved. Thanks!


Outdated tutorial

Type of issue
Code doesn't work
Description
Tutorial is outdated and not working anymore. SQLite batteries are not include and commands are not resulting in working version.
Page URL
https://learn.microsoft.com/en-us/ef/core/get-started/overview/first-app?tabs=netcore-cli
Content source URL
https://github.com/dotnet/EntityFramework.Docs/blob/main/entity-framework/core/get-started/overview/first-app.md
Document Version Independent Id
b38b9d14-6bad-12e0-8d2d-24b50bc4977e
Article author
@Rick-Anderson

@PicassoCT Can you post the specific error you are seeing and indicate at which stage it happens?

@ajcvickers  Its me. I added the wrong package: Microsoft.Data.Sqlite.Core instead of Microsoft.EntityFrameworkCore.Sqlite.Core. Just the universal background noise of noobs finding out. Thanks for caring.


How to use import from Typescript

I've seen Typescript d.ts, but I am not able to import correctly from my ts file.
import stringToStream from 'string-to-stream';
import {stringToStream} from 'string-to-stream';
Could you help me?

Sorry, but I was mistaken by a wrong node_modules. It works (first option)


Add inverse() function to Circuit.

We should have a function for calculating the inverse of a circuit.
The function inverse() should be a method of the Circuit class and should return a circuit whose elements are dagger of each of the elements in the original circuit with the order reversed. In this way, the circuit is the exact inverse of the circuit with which the function was called.
Deliverables:

[ ] New inverse() function described above.
[ ] Example usage in the init file for the circuits module
[ ] Tests covering various cases.

Affected repository: orquestra-quantum

This issue has been solved by this PR:
https://github.com/zapatacomputing/orquestra-quantum/pull/27


Additional role reqs for creating a website

In the "Create a website" row where "Required roles and permissions in Microsoft Power Platform" are listed, in addition to the "System Administrator" role, a user also needs the "Basic User" and "Environment Maker" roles. The UI will say you don't have permissions otherwise.

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

ID: 20c84550-bfea-6a51-3b10-87175c8a038b
Version Independent ID: 20c84550-bfea-6a51-3b10-87175c8a038b
Content: Roles required for Power Pages administration
Content Source: power-pages-docs/admin/admin-roles.md
Service: power-pages
Sub-service: ****
GitHub Login: @neerajnandwana-msft
Microsoft Alias: nenandwCreate a website	Required roles and permissions in Microsoft Power Platform (all are required):
A user account with Read-Write Access Mode.
System administrator role.
Permissions to register an app in Azure AD are required.
Is website creation disabled in the tenant?
If Yes, in addition to the roles and permissions above, a user will also need at least one of the following roles to create a website: Global administrator, Dynamics 365 administrator, or Power Platform administrator.

Thank you for your feedback and sorry to hear you are having issues. In our testing, only the system administrator role should be required to create a website. This may be something unique to your environment, I would suggest you engage with support to help you isolate the issue.


Adding basic augmentation methods with torchvision.transforms . Closes #22

Remove the test code snippets at the end of the module.


Bootstrapped the Website

I rewrote all of the webpages to use bootstrap.
Join server form is now a modal in index.html

Fixes #16


O365 Authentication

Need to authenticate to O365 services for a particular account. Use this guide - https://azure.microsoft.com/en-us/documentation/articles/active-directory-v2-devquickstarts-node-web/

Create an auth route, after the user signs in just display their user name

I'll work on this!

closed via https://github.com/sedouard/slack-o365-calendar/pull/11


Add ADOT package

Issue #, if available: N/A
Description of changes: Add otel-collector project
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

Are these images going to served in production from the ecr public uri or will they published to private ecr and be behind the gate?

@jaxesn They will eventually live in our private image ECR repo though this is not reflected in this PR. I will modify the CDK to add a ECR pull through cache rule to mirror the public image, and modify this build tooling repo one more time to point to the  private ECR. I figured I could do testing separately for those few items to keep things clean.

/unhold

/approve


IE9 not working on the homepage and my site

Hello,
I'm currently having an issue with IE9. It doesn't seem to be working on the Salvattore homepage, or on my own website.
The error I'm getting on my site is: SCRIPT16385: Not implimented.
It is referring to the character of the if statement in this block of code:
  self.get_stylesheets().forEach(function extract_rules(stylesheet) {
    Array.prototype.forEach.call(self.get_css_rules(stylesheet), function filter_by_column_selector(rule) {
      if (rule.media && self.media_rule_has_columns_selector(rule.cssRules)) {
        mediaQueries.push(global.matchMedia(rule.media.mediaText));
      }
    });
  });

Has anyone come across this problem? Any help would be appreciated!
Thanks.

As always happens, I've just worked out what the issue is. The current build is using grunt-bless, which splits large CSS files down into parts to beat the IE selector limit. The downside of this is it is using @import rules to include the rest of the other CSS files, which as mentioned on the homepage don't work well with Salvattore. This is what was causing the issue.


load graph_optimized.pb error  no EdgeBias???

tf.import_graph_def(graph_def_optimized)  load graph_optimized.pb error
##########################################################################
tensorflow 1.8.0 error
hortatech@1080Ti:~/projects/glow/demo$ python server.py
2018-07-24 18:11:15.266967: I tensorflow/core/platform/cpu_feature_guard.cc:140] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2018-07-24 18:11:15.348810: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:898] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2018-07-24 18:11:15.349242: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1356] Found device 0 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.683
pciBusID: 0000:01:00.0
totalMemory: 10.92GiB freeMemory: 10.46GiB
2018-07-24 18:11:15.349256: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1435] Adding visible gpu devices: 0
2018-07-24 18:11:15.529259: I tensorflow/core/common_runtime/gpu/gpu_device.cc:923] Device interconnect StreamExecutor with strength 1 edge matrix:
2018-07-24 18:11:15.529301: I tensorflow/core/common_runtime/gpu/gpu_device.cc:929]      0
2018-07-24 18:11:15.529308: I tensorflow/core/common_runtime/gpu/gpu_device.cc:942] 0:   N
2018-07-24 18:11:15.529496: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1053] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 10119 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1080 Ti, pci bus id: 0000:01:00.0, compute capability: 6.1)
Traceback (most recent call last):
File "server.py", line 1, in
import model
File "/home/hortatech/projects/glow/demo/model.py", line 88, in
tf.import_graph_def(graph_def_optimized)
File "/home/hortatech/miniconda3/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 432, in new_func
return func(*args, **kwargs)
File "/home/hortatech/miniconda3/lib/python3.6/site-packages/tensorflow/python/framework/importer.py", line 489, in import_graph_def
graph._c_graph, serialized, options)  # pylint: disable=protected-access
tensorflow.python.framework.errors_impl.NotFoundError: Op type not registered 'EdgeBias' in binary running on 1080Ti. Make sure the Op and Kernel are registered in the binary running in this process.
#############################################################
tensorflow 1.7.0
hortatech@1080Ti:~/projects/glow/demo$ python server.py
2018-07-24 19:07:14.947274: I tensorflow/core/platform/cpu_feature_guard.cc:140] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2018-07-24 19:07:15.041920: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:898] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2018-07-24 19:07:15.044762: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1344] Found device 0 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.683
pciBusID: 0000:01:00.0
totalMemory: 10.92GiB freeMemory: 10.46GiB
2018-07-24 19:07:15.044780: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1423] Adding visible gpu devices: 0
2018-07-24 19:07:15.217369: I tensorflow/core/common_runtime/gpu/gpu_device.cc:911] Device interconnect StreamExecutor with strength 1 edge matrix:
2018-07-24 19:07:15.217395: I tensorflow/core/common_runtime/gpu/gpu_device.cc:917]      0
2018-07-24 19:07:15.217402: I tensorflow/core/common_runtime/gpu/gpu_device.cc:930] 0:   N
2018-07-24 19:07:15.217590: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1041] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 10121 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1080 Ti, pci bus id: 0000:01:00.0, compute capability: 6.1)
Traceback (most recent call last):
File "server.py", line 1, in
import model
File "/home/hortatech/projects/glow/demo/model.py", line 88, in
tf.import_graph_def(graph_def_optimized)
File "/home/hortatech/miniconda3/lib/python3.6/site-packages/tensorflow/python/util/deprecation.py", line 432, in new_func
return func(*args, **kwargs)
File "/home/hortatech/miniconda3/lib/python3.6/site-packages/tensorflow/python/framework/importer.py", line 570, in import_graph_def
raise ValueError('No op named %s in defined operations.' % node.op)
ValueError: No op named EdgeBias in defined operations.

You need to pip install the blocksparse package, check install instructions in ./script.py


Add remove image from disk func

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

We usually do not create PR's for branches so closing this one.


InmisAddon thinks fabric-api is missing

With inmisaddon-1.0.1, launching the game fails and Fabric Loader 0.14.9 shows an error:
Incompatible mod set!
net.fabricmc.loader.impl.FormattedException: Mod resolution encountered an incompatible mod set!
A potential solution has been determined:
- Install fabric-api, any version.
Unmet dependency listing:
- Mod 'InmisAddon' (inmisaddon) 1.0.1 requires any version of fabric-api, which is missing!
at net.fabricmc.loader.impl.FabricLoaderImpl.load(FabricLoaderImpl.java:190)
at net.fabricmc.loader.impl.launch.knot.Knot.init(Knot.java:148)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:68)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
This is using a small custom modpack to play 1.19 using Fabric 0.14.9 - fabric-api-0.58.0+1.19.jar is definitely included.

What happens if you use the latest fabric api?

Having the same issue. It appears to not work with a later version of minecraft like 1.19.1. The other issue could be that it does not work with Fabric API 58.5 but that is the latest version for 1.19.1 so in my mind, same issue that it does not work with a MC version older than 1.19.2.
My testing:
I set up two new basic MC installs of version 1.19.2 and 1.19.1. I installed latest version of fabric and then only added three mods as shown below.
mod directory of version 1.19.2:

mod directory of version 1.19.1:

It worked for the version 1.19.2 but not the version 1.19.1. I get the same error as listed above from Rhys10220976 on 1.19.1:
Incompatible mod set!
net.fabricmc.loader.impl.FormattedException: Mod resolution encountered an incompatible mod set!
A potential solution has been determined:
- Install fabric-api, any version.
Unmet dependency listing:
- Mod 'InmisAddon' (inmisaddon) 1.0.1 requires any version of fabric-api, which is missing!
at net.fabricmc.loader.impl.FabricLoaderImpl.load(FabricLoaderImpl.java:190)
at net.fabricmc.loader.impl.launch.knot.Knot.init(Knot.java:148)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:68)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:577)
at org.multimc.onesix.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:210)
at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:245)
at org.multimc.EntryPoint.listen(EntryPoint.java:143)
at org.multimc.EntryPoint.main(EntryPoint.java:34)

Yes it is an issue with the api, fabric itself changed the id of the api to fabric-api.

Is that something you can/are willing to address for the MC 1.19.1 version?

I mean why not updating to 1.19.2?

I'm  having same problem with 1.19.  I am unable to update to 1.19.1 or 2 because of other conflicting mods not working in those versions.  Is there a way to get it to work with Fabric api 0.57.0 or 0.58.0?

The solution that worked for me was simply going to the fabric.mod.json file with notepad and at the bottom where it says "fabric-api": I just changed to say "fabric": and it worked.

The solution that worked for me was simply going to the fabric.mod.json file with notepad and at the bottom where it says "fabric-api": I just changed to say "fabric": and it worked.

I don't understant where the .json should be, I only have .jar in the mod folder.

Fixed with a later version, out of time reasons I only work on the latest version of my mods.


Implemented fallback into getCurrency in ContextFactory

Replaced a generic RuntimeException that is never caught with the only logical fallback. This makes it impossible for the currency-cookie to break the storefront if it is invalid.

1. Why is this change necessary?
Without this change an invalid value in the currency-cookie will break the entire storefront because the RuntimeException for this was never caught.
2. What does this change do, exactly?
It replaces the thrown RuntimeException with a fallback. When a currency is being loaded based on a cookie and it is not found in the database, now the result falls back to the default shop currency.
3. Describe each step to reproduce the issue or behaviour.
Open the storefront and replace the value of the currency-cookie with a different one that is invalid. This could easily happen when a currency is removed after a shop already had customers that used the currency switch.
4. Please link to the relevant issues (if any).
None.
5. Which documentation changes (if any) need to be made because of this PR?
None.
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

If the question comes up: I purposely did not persist the fallback currency uuid to the cookie because I don't think, this is the right place to do so. In general I think I makes sense to set the currency cookie to the fallback in case it is needed. But I think that should be handled by the Storefront bundle instead of the Context bundle.


Sample persistent map and persistent filesystem

A basic sample to demonstrate use of persistent map and persistent filesystem.
Files updated in the hello-world sample:
enclave/build.gradle
ReverseEnclave.java
README.md

@shamsasari @bonifazi-r3 Can you please have a look. Thank You!

Updated as per the comments.

Merging this sample which shows how persistence works, and how to use the persistent map and persistent file system. @divya-r3 confirmed that all the code review comments have been addressed, hence merging the same.


Forced language setting via variable

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the problem to be solved
Hi!
Now the service can automatically determine the locale settings and install the language, I have a question, is it possible to set the desired language through a variable to turn off this check?
For example, I need only English, how can I do it now? Thank u in advance!
Suggest a solution
Add environment variable for set up language of pages.
Additional context
No response

Hi @SAOPP!
Could you please explain what's the reason for your request? Automatic localization based on the browser locale (and nothing more), it's like a small piece of sugar for the end-users :) Maybe you have some problems with it?

Okay, why I have an english locale but I got russian pages? I think automatically detect it's not really cool, and I talked about variable for native setting this up.

Ok 👌, I will implement a flag for this a little bit later, ok?

Np homie :smiley: I still initially tried to understand whether it would be difficult to implement, thank u very much. :+1:

Could you please test changes in #94? Docker image (just for a test) tarampampam/error-pages:toogle-l10n

Ping @SAOPP

@SAOPP are you ok?

Yes, everything works, the language is ignored if you put non-English higher in the list in browser. :+1:
Btw, I would like to apologize for the fact that when I wrote this issue, I didn't keep track of the fact that for some reason my 'non-English' language was higher than English language is Chrome, which is why I actually wrote this issue - because in the list of languages in It's not obvious to Chrome that it's from this list that the language is defined as the main language. I'm not sure if I explained it clearly enough, let me know.

:fire: v2.13.0 released


bug: 401 error when trying to start facility

Describe the bug
When attempting to start the facility service using lpms-cli, the command fails with a 401 user not authorized, despite having freshly logged in using the default username / password.
To reproduce

git clone the develop branch of lpms-server into a new folder, and ensure that there is no database folder prior to using lpms-server.
Follow the quick start instructions at https://hackmd.io/jd852UC9QuC32bN_DFsoDQ. At the last command will fail with the 401 error.

This was a bug in the lpms-cli not passing in auth headers correctly.


🐛 read.php not using DB Prefix

I enountered an issue with read.php not using the database's prefix that was setup in config/environment.php which caused it to fail grabbing the QR Code
Related Code:
https://github.com/giandonatoinverso/PHP-Dynamic-Qr-code/blob/c6cb83638a7c8a5a6aec39a04ff0d852a8a15ac1/read.php#L18-L21

Sure, I will open PR in a bit


Can't get it to work with vue

This package seems to do exactly what i need for my vue project, but i can't get it to work. I'm not sure if i missed something or if it's not compatible with the versions that i'm using?
I use vue-shadow-dom to add my shadow root.
Any help would be much appreciated. I can add an english readme to your project if you want and if i get it to work. Thanks a lot in advance!
Dependencies
"@vitejs/plugin-legacy": "^2.0.0",
"@vitejs/plugin-vue2": "^1.1.2",
"sass": "^1.58.3",
"vite": "^3.0.2",
"vite-plugin-shadow-dom-css": "^0.0.2",
"vue": "^2.7.7",
"vue-shadow-dom": "^1.6.0"

vite.js
...
export default defineConfig({
    plugins: [
        vue2(),
        legacy({
            targets: ["ie >= 11"],
            additionalLegacyPolyfills: ["regenerator-runtime/runtime"],
        }),
        shadowDomCss(),
    ],
    ...
}
...

main.js (Entry Point)
import Vue from "vue";
import { createPinia, PiniaVuePlugin } from "pinia";
import Shadow from "vue-shadow-dom";

import App from "./App.vue";

Vue.use(PiniaVuePlugin);
const pinia = createPinia();

Vue.use(Shadow);

new Vue({
    render: (h) => h(App),
    pinia,
}).$mount("#app");

App.vue
<template>
    <shadow-root>

            test

    </shadow-root>
</template>

For future reference: I got it to work. I just found the example in the code :)
What was missing? The style provider. I use it like this:
App.vue
<template>
    <shadow-root>

            test

    </shadow-root>
</template>

Sub-components also have

It's working great now, thanks for your work!

Thank you for the code example. This project is still in an experimental state, if you have better suggestions, welcome to put forward.


fix a typo Kuberflow -> Kubeflow

fix a typo in line 25 Kuberflow -> Kubeflow

This change is

/assign @gaocegege

/ok-to-test

Thanks and welcome @yeya24! btw, just FYI the contents of this design doc is bit out dated. For usage info you might want to refer to the user guide or the quick starter guide. thanks.

Thanks for your reply! @xyhuang Should I close this pr?


Improve etc guidance

What do you need?
Re-write the etc guidance so it's a bit clearer. It's a departure from many people's home styles, and it made a few people scratch their heads during user research sessions.
We may also want to cross link from terms and phrases.
Which entry/section is this related to?
http://content-guide.apps.staging.digital.gov.au/punctuation-grammar/#eg-ie-etc-and-nb

Tracking in Trello


Cursor does not appear at top of buffer with Git Verbose Commit

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.83.0-insider
OS Version: macOS 14.0

With Git: Use Editor As Commit Input and Git: Verbose Commit, the cursor often does not appear on the top line above the comments (where you are supposed to write your commit message). Instead it appears at the bottom or even somewhere in between. I think this has to do with the verbose text being added after the commit tab is open and the cursor rendered. It's a bit annoying because you never know where the cursor will be and you cannot simply start writing as you press the shortcut to create a new commit.

try disabling all extensions, and ensure you're using the latest VS Code version, and check your Git configuration.

What should I check in my Git configuration? I don't think this is related to the Git configurations since the rendering of the verbose text happens in VSCode.
I'm on the latest Insiders, but I've noticed this behaviour since the Git: Verbose feature was added (which BTW, I love, even with this small annoyance) in both Insiders and stable versions.

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Open Run page

Fix the fact that a run is 1-1 to a CCC job.
(This is from Flo's planning notes, I'm actually not sure what it means)

Got it, so I guess in order for this card to be done:

The current "Thank You" page will not exist anymore, but a Thank You status will on submitting a Run step.  (This will probably need UI work from Malte, but I'll consider that separate).
Refactor some infrastructure around an entire App being "loading" based on one Run step.
Might need to make Run widgets' execution generic.


Charm++ on Apple Silicon (M1, arm64)

Hi,
I'm one of the developers for the numerical-relativity code spectre (https://spectre-code.org/), which relies on charm++. We support macOS, but I'm the first to try building it on an M1 (Apple Silicon, arm64) Mac. When I tried building charm++ 7.0.0-rc1 with
./build charm++ multicore-darwin -j16 --with-production as smart-build.pl suggested, I get an error that multicore-darwin is not supported.
I wonder if there might be a way forward to attempt to build charm++ on an M1 Mac? I'd be grateful for any hints or advice you might be able to give me!

Hi Geoffrey,
Please try the build tuplet multicore-darwin-arm8 to build as ARM64.
Also, thanks for mentioning smart-build.pl. If it recommended multicore-darwin then that is a bug we need to fix.

Thanks! I got charm++ to build. However, I have a followup question: how do I ensure that macOS runs my job (launched with charm run) on the faster performance cores, instead of on the slower, efficiency cores? Is this the default if I just ask for four cores?

Please disregard my previous question: I've verified with Activity Monitor that when I run with +p4 it runs on four performance cores.
I have noticed, however, that when benchmarking spectre (I'm part of the team developing spectre, which relies on charm++ for its parallelization), performance actually decreases on the M1 Mac as I increase the number of processor cores. Single-core performance is comparable, but as I increase the number of cores, the time to complete my sample job increases. This is not the case on my Intel Mac, where performance scales roughly as I'd expect with increasing numbers of cores (e.g., decreases by about a factor of two when going from 1 to 2 cores).
I wonder if you have any advice about performance on M1 Macs or arm8 when running on multiple cores?

I'm glad the build is working for you. Our experience with ARM64 until now has mostly been with low-power boards such as Raspberry Pi, so it is likely that Charm++ itself needs some tuning for within-node performance on the M1. If possible, could you share the steps needed to run a sample job with SpECTRE so that we can analyze it directly?

Hi @evan-charmworks! Thank you very much for being willing to help me debug what's happening!
Below are detailed instructions on how to build the spectre executable
that I'm using for my tests: it evolves a single black hole for a few
timesteps. When I run on one core on an M1 iMac, the walltime is 17.4 seconds,
but running on 4 cores, the walltime is 113.7 seconds.
If you have any insights on why this might be, they would be most welcome! Please also let me know if any of these steps don't work for you. I just ran through them myself to check them, but it's possible I made a mistake or missed something specific to the machine I'm using.
How to install and run Spectre on Apple Silicon
Here are steps to build a spectre test executable on an
Apple Silicon Mac.
These steps worked for me on a brand new Apple Silicon iMac. Please let
@geoffrey4444 know if you have trouble.
0. Install the xcode command-line tools.
Install the xcode command-line tools, which include the clang compiler, etc.
xcode-select --install

1. Make a directory to install prereqs
First, make a directory to hold some prerequisites that spectre depends on.
Name this directory whatever you like; I chose $HOME/apps.
export SPECTRE_DEPS_ROOT=$HOME/apps
mkdir $SPECTRE_DEPS_ROOT
cd $SPECTRE_DEPS_ROOT
mkdir src
cd src

2. Install python dependencies
Spectre depends on python and some python packages. Miniforge is a way to
install an arm64-native python stack.
curl -L https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-MacOSX-arm64.sh > Miniforge3-MacOSX-arm64.sh

# Install miniforge. Accept all default choices
bash Miniforge3-MacOSX-arm64.sh
# Activate conda base environment for current session
eval "$(/Users/gwpacworkstation/miniforge3/bin/conda shell.zsh hook)"
# Activate conda at startup (to make sure you're always using native python)
conda init zsh
exit # close shell. conda will automatically load when new zsh shells start.

In a new shell (new terminal window), do the following to get back to where
we were:
export SPECTRE_DEPS_ROOT=$HOME/apps
cd $SPECTRE_DEPS_ROOT/src

Now, install the necessary python packages. (Note: jupyter and notebook are n
ot necessary to install, but I prefer installing them any time I'm setting up a
new machine.)
conda install numpy scipy matplotlib h5py jupyter notebook

3. Install dependencies with Homebrew
Most of spectre's dependencies beyond python can be installed using the
homebrew package manager.
First, install Homebrew:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Then, run the following to install a fortran compiler and other
dependencies:
brew install gcc
brew install openblas boost gsl cmake
brew install ccache autoconf automake catch2 jemalloc hdf5 pybind11 yaml-cpp

3. Install remaining dependencies
Here, we'll install the remaining dependencies other than charm++.
cd $SPECTRE_DEPS_ROOT
mkdir blaze
pushd blaze
curl -L https://bitbucket.org/blaze-lib/blaze/downloads/blaze-3.8.tar.gz > blaze-3.8.tar.gz
tar -xf blaze-3.8.tar.gz
mv blaze-3.8 include
popd

git clone https://github.com/edouarda/brigand.git

# Need master branch of libxsmm to support Apple Silicon
git clone https://github.com/hfp/libxsmm.git
pushd libxsmm
make
popd

pushd ./src
git clone https://github.com/Libsharp/libsharp.git
cd Libsharp

# Do not use compiler flag -march=native (unsupported on Apple Silicon)
sed "s/-march=native//" configure.ac > configure.ac.mod
mv configure.ac.mod configure.ac

autoupdate
autoconf
./configure
make
mv auto $SPECTRE_DEPS_ROOT/libsharp
popd

Next, install charm++:
git clone https://github.com/UIUC-PPL/charm
pushd charm
git checkout v7.0.0-rc1
./build charm++ multicore-darwin-arm8 -j8 --with-production
popd

4.

# I'm pretty sure the warnings you get when building are safe to ignore
# This builds an executable that evolves a single black hole
make -j8 EvolveGhKerrSchild

5. Run the test executable
Inside the spectre build directory, make a directory to hold some test
simulations.
mkdir test_simulations
cd test_simulations
cp ../../tests/InputFiles/GeneralizedHarmonic/KerrSchild.yaml .

Edit KerrSchild.yaml. Change the Evolution: block to
Evolution:
  InitialTime: 0.0
  InitialTimeStep: 0.01
  TimeStepper: DormandPrince5

and change these options under DomainCreator:Shell as follows:
    InitialRefinement: 2
    InitialGridPoints: [9, 9]

Then, run on one core with
../bin/EvolveGhKerrSchild --input-file=KerrSchild.yaml

To run on 4 cores, delete the output via rm ./*h5 and then do
../bin/EvolveGhKerrSchild +p4 --input-file=KerrSchild.yaml

Thank you @geoffrey4444 for the detailed and comprehensive instructions. We will examine what is going on. Your directions will also be helpful for adding SpECTRE to Charm's continuous integration testing.

Thank you @geoffrey4444 for the detailed and comprehensive instructions. We will examine what is going on. Your directions will also be helpful for adding SpECTRE to Charm's continuous integration testing.

That sounds great, @evan-charmworks ! Thank you so much for taking a look...I really appreciate it!

I think we discussed in Core a couple weeks ago that one culprit in the poor scaling here might be the fact that darwin builds define the macro #define  CMK_NOT_USE_TLS_THREAD  1 in the conv-mach.h file. This causes Cpv variables to be implemented using an array rather than TLS variables, which may be susceptible to false sharing issues in a multicore build such as this. We could try defining that to 0 and rebuilding Charm++ and Spectre. It may cause other issues, but it's worth a try.

@stwhite91 please accept my apologies for taking so long to reply! I got swamped with a grant proposal and other end-of-semester work, and I've only now been able to try your idea.
I changed src/arch/multicore-darwin-arm8/conv-mach.h:64 in v7.0.0 of charm++ to 0 from 1 as you suggested, rebuilt charm, and rebuilt spectre. However, I still have the same problem: I see basically no change in performance when running on multiple cores: using +p1, +p2, +p4, +p8, and +ppn 7 +pemap 0-6 +commap 7 all fail to show the expected scaling. I would have expected using 8 cores would give at least a 7x speedup (assuming 1 core is stuck doing communication), but I see essentially zero difference in runtime.
I should have time to continue investigating this with you on a much more prompt timescale now, if this is something that you still might be able to help me resolve!

Hi again,
I tried running the charm++ piArray example on my M1 Mac, to get an idea of what kinds of performance I should expect:
./piArray +p1 31250000 32 ---- At time 61.180054, pi=: 3.141576
./piArray +p8 31250000 32 ---- At time 20.712907, pi=: 3.141562
I verified in Activity Monitor that the +p8 case was reporting running at 800%CPU, and that the activity was saturating the 8 performance cores.
Naively, I would have expected the speedup to be 8x, but it's actually only 3x. In contrast, a quick mpi4py version of the problem does give me the expected speedup (26.1 seconds on 1 core, 3.5 seconds on 8 cores).
Maybe it would be better to understand the scaling of the piArray example, instead of worrying about SpECTRE?

Hello Geoffrey,
Charm++ built with MPI does not seem to exhibit these problems on M1. After a quick:
brew install openmpi
Then: ./build charm++ mpi-darwin-arm8 --with-production -g3 -j
I am able to get piArray to scale more sensibly:
erinys :: examples/charm++/piArray ‹jszaday/cmi-shmem*› % mpirun -n 8 ./piArray 31250000 32
Charm++> Running on MPI version: 3.1
Charm++> level of thread support used: -1 (desired: 0)
Charm++> Running in non-SMP mode: 8 processes (PEs)
Converse/Charm++ Commit ID: v7.1.0-devel-141-g7e59686a2
Isomalloc> Synchronized global address space.
CharmLB> Load balancer assumes all CPUs are same.
Charm++> Running on 1 hosts (1 sockets x 10 cores x 1 PUs = 10-way SMP)
Charm++> cpu topology info is gathered in 0.000 seconds.
At time 0.000219, array created.
At time 0.000248, main exits.
At time 7.704571, pi=: 3.141593
[Partition 0][Node 0] End of program

I'm still investigating the issues with the multicore/netlrts builds -- but hopefully this helps!

Thanks for the update! I tried this on my MacBook Pro with version 7.0.0, and I don't notice any improvement in performance with mpi over nonmpi. I tried SMP and non-smp, and that also made no noticeable difference in performance on multiple cores. Maybe there's something different in the development version you're using? Do you see the speedup in the 7.0.0 release as well?

Good point. I checked v7.0.0 and it performs comparably on my Mac. I can, at least, demonstrate poor scaling for netlrts and multicore builds, so I'll focus my efforts there. Particularly, SMP builds are terribly slow regardless of build so that's something to look into as well.
❯ ./charmrun +p1 ./piArray 31250000 32
Running as 1 OS processes:  ./piArray 31250000 32
charmrun> mpirun -np 1  ./piArray 31250000 32
Charm++> Running on MPI version: 3.1
Charm++> level of thread support used: -1 (desired: 0)
Charm++> Running in non-SMP mode: 1 processes (PEs)
Converse/Charm++ Commit ID: v7.0.0
CharmLB> Load balancer assumes all CPUs are same.
Charm++> Running on 1 hosts (1 sockets x 10 cores x 1 PUs = 10-way SMP)
Charm++> cpu topology info is gathered in 0.000 seconds.
At time 0.000444, array created.
At time 0.000447, main exits.
At time 58.984039, pi=: 3.141622
[Partition 0][Node 0] End of program
❯ ./charmrun +p8 ./piArray 31250000 32
Running as 8 OS processes:  ./piArray 31250000 32
charmrun> mpirun -np 8  ./piArray 31250000 32
Charm++> Running on MPI version: 3.1
Charm++> level of thread support used: -1 (desired: 0)
Charm++> Running in non-SMP mode: 8 processes (PEs)
Converse/Charm++ Commit ID: v7.0.0
Isomalloc> Synchronized global address space.
CharmLB> Load balancer assumes all CPUs are same.
Charm++> Running on 1 hosts (1 sockets x 10 cores x 1 PUs = 10-way SMP)
Charm++> cpu topology info is gathered in 0.000 seconds.
At time 0.000083, array created.
At time 0.000093, main exits.
At time 7.838483, pi=: 3.141587
[Partition 0][Node 0] End of program
❯ ompi_info

                 Package: Open MPI<EMAIL_ADDRESS>Distribution
                Open MPI: 4.1.2
  Open MPI repo revision: v4.1.2
   Open MPI release date: Nov 24, 2021
                Open RTE: 4.1.2
  Open RTE repo revision: v4.1.2
   Open RTE release date: Nov 24, 2021
                    OPAL: 4.1.2
      OPAL repo revision: v4.1.2
       OPAL release date: Nov 24, 2021
                 MPI API: 3.1.0
            Ident string: 4.1.2
                  Prefix: /opt/homebrew/Cellar/open-mpi/4.1.2
 Configured architecture: aarch64-apple-darwin21.1.0
.
.
.

Thanks for sending this output! I figured out why my timing was different from yours. For some reason, after building charm++ with the command you gave me (./build charm++ mpi-darwin-arm8 --with-production -g3 -j), the piArray command wasn't using mpi. When I ran it, it was running in "standalone mode" using threads, which explains why it gave the same performance. Doing make clean; make in the piArray directory fixed this, and now I get the same timing for piArray as you quote above, which makes sense, since the output confirms it's now using mpi.

I've tried some different strategies for resolving this within-node performance gap on multicore-darwin-arm8, including things recommended by an official Apple tutorial, but so far have not made any improvement.
I suspect that piArray may not be the best choice of test case due to its use of the CrnDrand function, which can take up to 10% of the execution's CPU time according to Xcode's Instruments profiler. This may have confounded my measurements. @stwhite91 would you recommend a particular Charm++ test/example/benchmark for assessing SMP performance?
One thing also worth noting is that +p8 is not ideal for an M1 Mac, because its CPU is comprised of 4 performance cores and 4 efficiency cores. For this reason I have been focusing on +p4.
evan@tenacity ~ % lstopo
Machine (3577MB total)
  Package L#0
    NUMANode L#0 (P#0 3577MB)
    L2 L#0 (4096KB)
      L1d L#0 (64KB) + L1i L#0 (128KB) + Core L#0 + PU L#0 (P#0)
      L1d L#1 (64KB) + L1i L#1 (128KB) + Core L#1 + PU L#1 (P#1)
      L1d L#2 (64KB) + L1i L#2 (128KB) + Core L#2 + PU L#2 (P#2)
      L1d L#3 (64KB) + L1i L#3 (128KB) + Core L#3 + PU L#3 (P#3)
    L2 L#1 (12MB)
      L1d L#4 (128KB) + L1i L#4 (192KB) + Core L#4 + PU L#4 (P#4)
      L1d L#5 (128KB) + L1i L#5 (192KB) + Core L#5 + PU L#5 (P#5)
      L1d L#6 (128KB) + L1i L#6 (192KB) + Core L#6 + PU L#6 (P#6)
      L1d L#7 (128KB) + L1i L#7 (192KB) + Core L#7 + PU L#7 (P#7)
  CoProc(OpenCL) "opencl0d0"


incompatible architecture (have 'arm64', need 'x86_64')

Hi,
My machine is MacBook Pro with M1 chip (arm64) and macOS 14.6.1. I tried to build project but got the following error:
java.lang.UnsatisfiedLinkError: /private/var/folders/qx/3vjt4hs17zl42zj0lt9vwppm0000gn/T/whisper-jni-314748098316209/libwhisper-jni.dylib: dlopen(/private/var/folders/qx/3vjt4hs17zl42zj0lt9vwppm0000gn/T/whisper-jni-314748098316209/libwhisper-jni.dylib, 0x0001): tried: '/private/var/folders/qx/3vjt4hs17zl42zj0lt9vwppm0000gn/T/whisper-jni-314748098316209/libwhisper-jni.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/private/var/folders/qx/3vjt4hs17zl42zj0lt9vwppm0000gn/T/whisper-jni-314748098316209/libwhisper-jni.dylib' (no such file), '/private/var/folders/qx/3vjt4hs17zl42zj0lt9vwppm0000gn/T/whisper-jni-314748098316209/libwhisper-jni.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64'))
at io.github.givimad.whisperjni.WhisperJNITest.beforeAll(WhisperJNITest.java:47)
My system is arm64, why does it "need 'x86_64'" instead?
Thanks

@yun-xiao2
Checkout for Java Library :
It works on Desktop too even on IOS in near future
https://github.com/eix128/WhisperJET


TOC fix.

Q
A

content fix?
yes

What's in this Pull Request?
TOC fix for provision SharePoint items doc.

@chakkaradeep,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


AliCloud function - run in time-based iteration & add graceful shutdown

Required items, please complete
Change(s):

AliCloud azure function connector will now run in 60-seconds (configurable) chunks. In every iteration, it will retrieve the data for that time range only, send it to LA, and then update the state manager with that chunk end-time. Then, it will move to the next 60-second chunk.
Added graceful cancellation mechanism. Since max time for function is 20 minutes, we will stop it once we get to 18 minutes (configurable), before we get a timeout error. That way, the next function execution can continue from the last successful timestamp, so less chance of duplicate data and data loss.
Fixed bug in which the state is updated at the start of the run (in the generate_date method). We should only update the state after we successfully published data to LA (in our case, when we finished a time range chunk).

Reason for Change(s):

Multiple timeouts for customer with high volume. Function tries to retrieve data from last 30 minutes, and as a result, fails on timeout just before finishing to process it.

Testing Completed:

No - this isn't a KQL/table change, so existing testing & validation do not exist.

Checked that the validations are passing and have addressed any issues that are present:

No - this isn't a KQL/table change, so existing testing & validation do not exist.

Hello @hovavza, Please update the function app zip as well.

Thanks for committing the requested changes, Please accept license agreement too

Hello @hovavza, Please accept license agreement

We wanted to check on the status of PR #10421. PR is pending for more than 30 days in draft state. Please let us know if you need any assistance to review this PR. Per our standard operating procedures if no response is received in the next 5 business days, we will close this PR. Thank you for your cooperation.

Since we have not received a response in the last 7 days, we are closing your PR #10421 per our standard operating procedures. If you still need support for this issue, you can re-open the PR at any time.
If you do re-open, we simply request that you ensure the PR has response to the last request. Thank you for your cooperation.


[Bug]: Invalid link for "blockchains"

Description
When I go to the home page and click on "Blockchains" in the Beginner tab, it redirects it to a dead link "https://www.freeweb3resources.com/docs/blockchains/blockchains" (Page not found)
Solution-:
The link should be changed to "https://www.freeweb3resources.com/docs/blockchains"
To Reproduce

Go to 'https://www.freeweb3resources.com/docs/blockchains/blockchains'
Click on 'Blockchains'
See the error

Anything else?
No response
Code of Conduct

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

Is this issue closed or not??

Is this issue closed or not??

yes. @FrancescoXX please close this issue


Failed to decode downloaded font, again

The fix of #59 still does not work, try this:
@font-face {
  font-family: 'Material Icons';
  font-style: normal;
  font-weight: 400;
  src: url(/fonts/MaterialIcons.woff) format('woff');
}

This will only work with url(http://localhost:8080/fonts/MaterialIcons.woff), and hardcoding the dev host is a bad idea.

I am not really into this kind of stuff, but I checked bootstrap.css which was working when I tried and they have stuff like:
url(../fonts/foo.woff)
Not sure if that is a valid solution for you.

That wouldn't work. Fonts are located under src/public/fonts/. Not sure where the bootstrap fonts are.

Yes, in deploy you have a css folder and a fonts folder, so the path is actually valid on bootstrap. I need to research more to see what is a viable solution, but I guess that at the end you will need to override some stuff based on your needs.

I'm not doing anything specific on my end.
It seems to me that the source of the trouble is from webpack dev server, or, the way webpack font loader is configured.

I found the same issue with octicons. Their css points to fonts in ./name.svg but that gets webpacked into ./fonts/name.hash.svg. I wound up just using the svg in a directive since I only needed a couple of icons anyway.  But it would be nice to be able to maybe inject that hash into an output file with some  webpack loader.  Thanks for all your work on this great repo!

Technically when the css-loader process a font, the 3rd party lib should have it on a path it can find, then when it gets processed, it will be moved to another place where webpack can find it.

Whatever the loader does, the resulting request does not even hit the .woff file. This is the font request shown by chrome dev tools:
Request URL:http://localhost:8080/
Request Method:GET
Status Code:304 Not Modified
Remote Address:<IP_ADDRESS>:8080

Is this because of the way the webpack dev server is configured? It never returns 404, if you go to http://localhost:8080/whatever it still renders the index file.

@Foxandxss is there a temporary fix for this? Does the current build system support picking different files for production build? For example, how is it possible to include fonts-dev.scss for development and include fonts-prod.scss in production build?
Any other temporary fixes that you could think of?

I remember changing the font stuff a while ago and I am not sure if this is still an issue or not. Feel free to open a new one. Sorry.


install problem

Unless you provide the REQUIRED information, your problem may not be addressed.
Installed the pyabsa according the readme step by step, but it seems the installation is still failed.
here the error information after importing the package " from pyabsa import AspectTermExtraction as ATEPC, available_checkpoints"
Describe the bug
ImportError                               Traceback (most recent call last)
File ~\Anaconda3\envs\pyabsa\lib\site-packages\confection_init_.py:38, in
37 try:
---> 38     from pydantic.v1 import BaseModel, Extra, ValidationError, create_model
39     from pydantic.v1.fields import ModelField
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic_init_.py:13, in
4 from pydantic_core.core_schema import (
5     FieldSerializationInfo,
6     FieldValidationInfo,
(...)
10     ValidatorFunctionWrapHandler,
11 )
---> 13 from . import dataclasses
14 from ._internal._annotated_handlers import (
15     GetCoreSchemaHandler as GetCoreSchemaHandler,
16 )
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic\dataclasses.py:11, in
9 from typing_extensions import Literal, dataclass_transform
---> 11 from ._internal import _config, _decorators, _typing_extra
12 from ._internal import _dataclasses as _pydantic_dataclasses
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic_internal_config.py:9, in
7 from typing_extensions import Literal, Self
----> 9 from ..config import ConfigDict, ExtraValues, JsonEncoder, JsonSchemaExtraCallable
10 from ..errors import PydanticUserError
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic\config.py:9, in
8 from ._migration import getattr_migration
----> 9 from .deprecated.config import BaseConfig
10 from .deprecated.config import Extra as _Extra
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic\deprecated\config.py:6, in
4 from typing import TYPE_CHECKING, Any
----> 6 from typing_extensions import Literal, deprecated
8 from .._internal import _config
ImportError: cannot import name 'deprecated' from 'typing_extensions' (C:\Users\Lenovo\Anaconda3\envs\pyabsa\lib\site-packages\typing_extensions.py)
During handling of the above exception, another exception occurred:
ImportError                               Traceback (most recent call last)
Input In [3], in <cell line: 1>()
----> 1 from pyabsa import AspectTermExtraction as ATEPC, available_checkpoints
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pyabsa_init_.py:13, in
9 name = "pyabsa"
10 version = "<IP_ADDRESS>"
---> 13 from pyabsa.utils.notification_utils.notification_utils import (
14     check_emergency_notification,
15 )
17 check_emergency_notification()
19 from pyabsa.framework.flag_class import *
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pyabsa\utils_init_.py:9, in
1 # -- coding: utf-8 --
2 # file: init.py
3 # time: 2021/6/5 0005
4 # author: YANG, HENG<EMAIL_ADDRESS>(杨恒)
5 # github: https://github.com/yangheng95
6 # Copyright (C) 2021. All Rights Reserved.
8 from pyabsa.utils.data_utils.dataset_item import DatasetItem
----> 9 from pyabsa.utils.absa_utils.make_absa_dataset import make_ABSA_dataset
10 from pyabsa.utils.absa_utils.absa_utils import (
11     generate_inference_set_for_apc,
12     convert_apc_set_to_atepc_set,
13 )
15 from pyabsa.utils.text_utils.word2vec import train_word2vec
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pyabsa\utils\absa_utils\make_absa_dataset.py:18, in
14 from termcolor import colored
16 from pyabsa.framework.flag_class.flag_template import LabelPaddingOption
---> 18 from pyabsa.tasks.AspectTermExtraction.prediction.aspect_extractor import (
19     AspectExtractor,
20 )
21 from pyabsa.utils.pyabsa_utils import fprint
24 def make_ABSA_dataset(dataset_name_or_path, checkpoint="english"):
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pyabsa\tasks\AspectTermExtraction\prediction\aspect_extractor.py:33, in
31 from pyabsa.framework.prediction_class.predictor_template import InferenceModel
32 from ..models import ATEPCModelList
---> 33 from ..dataset_utils.lcf.atepc_utils import (
34     load_atepc_inference_datasets,
35     process_iob_tags,
36 )
37 from ..dataset_utils.lcf.data_utils_for_inference import (
38     ATEPCProcessor,
39     convert_ate_examples_to_features,
40     convert_apc_examples_to_features,
41 )
42 from ..dataset_utils.lcf.data_utils_for_training import split_aspect
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pyabsa\tasks\AspectTermExtraction\dataset_utils_lcf_\atepc_utils.py:12, in
9 import re
10 import string
---> 12 from pyabsa.tasks.AspectPolarityClassification.dataset_utils.lcf.apc_utils import (
13     get_syntax_distance,
14     get_lca_ids_and_cdm_vec,
15     get_cdw_vec,
16 )
17 from pyabsa.utils.pyabsa_utils import fprint
20 # It is hard to tokenize multilingual text, I decide to use a pretrained tokenizer, you can alter according to your demands
21 # tokenizer = AutoTokenizer.from_pretrained('bert-base-multilingual-cased')
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pyabsa\tasks\AspectPolarityClassification\dataset_utils_lcf_\apc_utils.py:13, in
11 import networkx as nx
12 import numpy as np
---> 13 import spacy
14 import termcolor
16 from pyabsa.framework.tokenizer_class.tokenizer_class import pad_and_truncate
File ~\Anaconda3\envs\pyabsa\lib\site-packages\spacy_init_.py:6, in
3 from typing import Any, Dict, Iterable, Union
5 # set library-specific custom warning handling before doing anything else
----> 6 from .errors import setup_default_warnings
8 setup_default_warnings()  # noqa: E402
10 # These are imported as part of the API
File ~\Anaconda3\envs\pyabsa\lib\site-packages\spacy\errors.py:3, in
1 import warnings
----> 3 from .compat import Literal
6 class ErrorsWithCodes(type):
7     def getattribute(self, code):
File ~\Anaconda3\envs\pyabsa\lib\site-packages\spacy\compat.py:4, in
1 """Helpers for Python and platform compatibility."""
2 import sys
----> 4 from thinc.util import copy_array
6 try:
7     import cPickle as pickle
File ~\Anaconda3\envs\pyabsa\lib\site-packages\thinc_init_.py:5, in
2 import numpy
4 from .about import version
----> 5 from .config import registry
7 # fmt: off
8 all = [
9     "registry",
10     "version",
11 ]
File ~\Anaconda3\envs\pyabsa\lib\site-packages\thinc\config.py:2, in
1 import catalogue
----> 2 import confection
3 from confection import VARIABLE_RE, Config, ConfigValidationError, Promise
5 from .types import Decorator
File ~\Anaconda3\envs\pyabsa\lib\site-packages\confection_init_.py:42, in
40     from pydantic.v1.main import ModelMetaclass
41 except ImportError:
---> 42     from pydantic import BaseModel, create_model, ValidationError, Extra  # type: ignore
43     from pydantic.main import ModelMetaclass  # type: ignore
44     from pydantic.fields import ModelField  # type: ignore
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic_init_.py:13, in
3 import pydantic_core
4 from pydantic_core.core_schema import (
5     FieldSerializationInfo,
6     FieldValidationInfo,
(...)
10     ValidatorFunctionWrapHandler,
11 )
---> 13 from . import dataclasses
14 from ._internal._annotated_handlers import (
15     GetCoreSchemaHandler as GetCoreSchemaHandler,
16 )
17 from ._internal._annotated_handlers import (
18     GetJsonSchemaHandler as GetJsonSchemaHandler,
19 )
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic\dataclasses.py:11, in
7 from typing import TYPE_CHECKING, Any, Callable, Generic, NoReturn, TypeVar, overload
9 from typing_extensions import Literal, dataclass_transform
---> 11 from ._internal import _config, _decorators, _typing_extra
12 from ._internal import _dataclasses as _pydantic_dataclasses
13 from ._migration import getattr_migration
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic_internal_config.py:9, in
6 from pydantic_core import core_schema
7 from typing_extensions import Literal, Self
----> 9 from ..config import ConfigDict, ExtraValues, JsonEncoder, JsonSchemaExtraCallable
10 from ..errors import PydanticUserError
11 from ..warnings import PydanticDeprecatedSince20
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic\config.py:9, in
6 from typing_extensions import Literal, TypeAlias, TypedDict
8 from ._migration import getattr_migration
----> 9 from .deprecated.config import BaseConfig
10 from .deprecated.config import Extra as _Extra
12 if TYPE_CHECKING:
File ~\Anaconda3\envs\pyabsa\lib\site-packages\pydantic\deprecated\config.py:6, in
3 import warnings
4 from typing import TYPE_CHECKING, Any
----> 6 from typing_extensions import Literal, deprecated
8 from .._internal import _config
9 from ..warnings import PydanticDeprecatedSince20
ImportError: cannot import name 'deprecated' from 'typing_extensions' (C:\Users\Lenovo\Anaconda3\envs\pyabsa\lib\site-packages\typing_extensions.py)
Would you please tell me how to fix the problem, thank you

Can you specify your environment, e.g., torch version, python version?

Please try to upgrade typing_extensions.

my torhc version is  2.0.1+cpu, python i installed according your instructions in the github, 3.8. thank you

Please try to upgrade typing_extensions.

typing_extensions is the newest version，4.7.1. and my typing_extensions is as follows:
Name: typing_extensions
Version: 4.7.1
Summary: Backported and Experimental Type Hints for Python 3.7+
Home-page:
Author:
Author-email: "Guido van Rossum, Jukka Lehtosalo, Łukasz Langa, Michael Lee"<EMAIL_ADDRESS>License:
Location: c:\users\lenovo\anaconda3\envs\pyabsa\lib\site-packages
Requires:
Required-by: annotated-types, huggingface-hub, pyabsa, pydantic, pydantic_core, torch, typer.
what should i do next if i want to use the pyabsa normally? thank you very much for reply and looking forward to your instructions. many thanks!

Probably your environment is not compatible with pyabsa. Try to create a new env of python3.9+, then retry installing pyabsa.

I see, i will have a try again. Thank you very much for your reply!
---Original---
From: "Heng @.>
Date: Sun, Aug 13, 2023 16:39 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [yangheng95/PyABSA] install problem (Issue #348)
Probably your environment is not compatible with pyabsa. Try to create a new env of python3.9+, then retry installing pyabsa.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Probably your environment is not compatible with pyabsa. Try to create a new env of python3.9+, then retry installing pyabsa.

Hi, I upgraded python to 3.9 and upgraded the pydantic to the newest version. typing_extensions is the newest version. However,  the same bug message come up as follows:
ImportError: cannot import name 'deprecated' from 'typing_extensions' (C:\Users\Lenovo\Anaconda3\envs\pyabsa\lib\site-packages\typing_extensions.py)
Is there any other solutions? Thank you very much!

https://github.com/tiangolo/fastapi/discussions/9808
try to use python3.7

tiangolo/fastapi#9808 try to use python3.7

thank you so much!!!! installation succeeded!!!!!!!!!


When I successfully placed a marker on a country I want to have a button saying “end turn”.

Resolved with commit: added hidden button when disabled


Query options are enabled

The API can now handle $skip, $top, $inlinecount, etc. New tests are also added

Merged.
A query like this still fails:
/breeze/Northwind/Products?$top=10&$skip=10&$select=ProductName


[7.x.x] Bump Dependencies #5488059144

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/5488059144

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Possible beta-19.1 issue - createSnapshot

I installed the plugin and attempted to use myModel.patch() and receive the following error:
internalModel.createSnapshot is not a function. myModel is a simple model with 3 attributes at the moment.
DEBUG: Ember      : 1.12.0
DEBUG: Ember Data : 1.0.0-beta.19.1

The plugin works for with beta.17; however, with beta.19.1 there are quite a few changes especially around the scheduleSave(...) and InternalModel. The InternalModel has a createSnapshot method which seems to be working fine inside the myModel.save().

beta.19
beta.19.1

Thanks for the help.

@kalebdf the issue-1 branch should cover this issue. Care to try changing your package.json file to use it? If everything's OK, I'll close this issue merging the PR.

@joelalejandro The DS.InternalModel does not have a reopen.

Uncaught TypeError: DS.default.InternalModel.reopen is not a function

Right, because it's not a typical Ember.Object. What was I thinking, lol?
I'll have another look at it.
Joel A. Villarreal Bertoldi
Diseñador gráfico / Desarrollador
Tel.: +54 9 (351) 6 - 710 - 728
2015-06-11 1:57 GMT-03:00 Kaleb Fulgham<EMAIL_ADDRESS>
@joelalejandro https://github.com/joelalejandro The DS.InternalModel
does not have a reopen.
Uncaught TypeError: DS.default.InternalModel.reopen is not a function
—
Reply to this email directly or view it on GitHub
https://github.com/joelalejandro/ember-data-patch-persistance/issues/1#issuecomment-110999158
.

Hi @joelalejandro , is this issue closed, because I am getting the same error while trying to patch my model. Thanks in advance

Vinoth, unfortunately I didn't fix it back then for beta-19.1, and since
then Ember Data has progressed so much that this addon is a bit obsolete by
now. I'll see if I can bring it up-to-date, but I don't have a timeline set
for this.
El lun., 18 de jul. de 2016 a la(s) 12:29, Vinoth Kumar <
<EMAIL_ADDRESS>escribió:

Hi @joelalejandro https://github.com/joelalejandro , is this issue
closed, because I am getting the same error while trying to patch my model.
Thanks in advance
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/joelalejandro/ember-data-patch-persistance/issues/1#issuecomment-233363829,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHQgdal0WTsxDP3hCo9w-iV_-mbWg3hks5qW5vfgaJpZM4E-19G
.

--
Joel Alejandro Villarreal Bertoldi
Desarrollador de software / Diseñador gráfico
GitHub / Twitter: @joelalejandro
Tel.:<PHONE_NUMBER>

Yeah I agree and by the way thanks for your quick response :)


Fix VAE randomness

The reparameterization trick did not perturb the gaussian multiplier during training. Now it does.
Introducing a new parameter 𝜖 allows us to reparameterize 𝑧 in a way that allows backprop to flow through the deterministic nodes. 𝜖 should be a source of randomness.

This merge request fixes the issue #790

With epsilon = 1.0, the line random_normal(shape=(batch, dim)) is equivalent to GaussianNoise(1.0)(tf.zeros((batch, dim))), except the latter is harder to read/follow. What's the purpose of this change?
For the record, GaussianNoise(1.0)(x) is equivalent to x + random_normal(), and is in fact implemented like this (except using V2-style stateless RNG instead of the old random_normal): https://github.com/keras-team/keras/blob/b96518a22bfd92a29811e507dec0b34248a8a3f5/keras/layers/regularization/gaussian_noise.py

Hello @fchollet,
Thank you for your response. I can't yet say why the two implementations are not equivalent. As evidence that they are: In the colab for this example (https://colab.research.google.com/github/keras-team/keras-io/blob/master/examples/generative/ipynb/vae.ipynb) if you replace only the single epsilon assignment line:

with

You will get different outputs for the losses. Particularly the kl_losses are an order of magnitude less in the GaussianNoise implementation.
Original:

Gaussian Noise:

I will further investigate the difference as to why epsilon = tf.keras.backend.random_normal(shape=(batch, dim)) is not equivalent to epsilon = keras.layers.GaussianNoise(1.0)(tf.zeros((batch,dim)))


Save space in final docker image

Uses multistage build to discard installation artifacts prior to finalization.

Docker still has squash marked as experimental.  As a result we will leave it to the developer to decide if squash is necessary.


uplication

[x] Using latest version as provided on the master branch
[x] Searched for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug
[x] Feature Request
[ ] Question
[ ] Other

Description

Hi guys, thanks for this python script.
I'd have a feature request that might would save some time and many resources.
Would be great to generate a file that collects the URLs of the tracks that has been downloaded, and the script would be able to skip those tracks. Currently, it takes a long time to parse the link, search the youtube URL, check if is there file with a similar name in the download folder then skip. This is not a big idea but it would be very useful I think.
Alternative solution:
Add a parameter that prevents to delete the downloaded URLs from the {playlist}.txt file after download. This way the downloaded URLs would be skipped before the downloading would start. Awesome, and easy, and it takes very small work.
+suggestion (maybe a bugreport?):
Please, avoid duplications in the {playlist}.txt files. If I run
'python3 spotdl.py --playlist https://open.spotify.com/user/nocopyrightsounds/playlist/7sZbq8QGyMnhKPcLJvCUFD'
twice, each URL will be duplicated in the file, AND during download the script will (try to) download the files twice. Let me know If I should open a new issue for this as a bug.

Closing as duplicate of #296.


docker-outside-of-docker feature wrongly update container entrypoint

in a dev container with compose.yml that use docker-outside-of docker feature it updates the main entrypoint which is not the expected result
with feature enabled
docker inspect --format='{{.Config.Entrypoint}}'  <container>
[
  [/bin/sh -c echo Container started
  trap "exit 0" 15
  /usr/local/share/docker-init.sh
  exec "$@"
  while sleep 1 & wait $!; do :; done - /usr/local/share/docker-init.sh
]

without feature enabled
docker inspect --format='{{.Config.Entrypoint}}'  <container>
[
  [/bin/sh -c echo Container started
  trap "exit 0" 15

  exec "$@"
  while sleep 1 & wait $!; do :; done - /usr/local/share/docker-init.sh
]

Solution
use the postStartCommand instead
Additional info
maybe #483  it's related

Hi 👋
Historically, for initializing docker, we have intentionally used the main entrypoint for docker-in-docker and docker-outside-of-docker Features. Using the entrypoint has the perk of starting the initializing process in the background as well as this is the suggested approach by Moby.
Let's keep this issue open for more feedbacks from the community, thanks for bringing this up.


Update release.sh according to this work flow:

update CHANGELOG.md on github, no PR needed, just edit directly.
git pull origin master in local master branch
run release.sh, keep pushing y vigorously
update documentation repo

https://github.com/BranchMetrics/documentation/edit/master/ingredients/web_sdk/_initialization.md
https://github.com/BranchMetrics/documentation/edit/master/ingredients/web_sdk/send_sms_example.md

post-release check

https://cdn.branch.io/example.html
https://cdn.branch.io/branch-v.version.number.min.js
https://github.com/BranchMetrics/Smart-App-Banner-Deep-Linking-Web-SDK/blob/v.version.number/CHANGELOG.md

One last thing, also stop ignoring -e temp files since... why not :D

:+1:

thanks! almost forgot this :)


Outdated files in the dev-1.17-ko.1

This is a Bug Report
Problem
Outdated files in the dev-1.17-ko.1 branch.
28 files to be modified

[ ] content/en/_index.html 1 file changed, 2 insertions(+), 2 deletions(-)
[ ] content/en/docs/concepts/architecture/cloud-controller.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/architecture/nodes.md 1 file changed, 25 insertions(+), 24 deletions(-)
[ ] content/en/docs/concepts/overview/what-is-kubernetes.md 1 file changed, 3 insertions(+), 3 deletions(-)
[ ] content/en/docs/concepts/services-networking/endpoint-slices.md 1 file changed, 12 insertions(+), 5 deletions(-)
[ ] content/en/docs/concepts/workloads/controllers/daemonset.md 1 file changed, 3 insertions(+), 15 deletions(-)
[ ] content/en/docs/concepts/workloads/controllers/statefulset.md 1 file changed, 8 insertions(+), 5 deletions(-)
[ ] content/en/docs/concepts/workloads/controllers/ttlafterfinished.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/workloads/pods/pod-topology-spread-constraints.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/reference/_index.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/reference/glossary/cloud-provider.md 1 file changed, 19 insertions(+), 5 deletions(-)
[ ] content/en/docs/reference/glossary/etcd.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/reference/kubectl/cheatsheet.md 1 file changed, 2 insertions(+), 2 deletions(-)
[ ] content/en/docs/reference/using-api/client-libraries.md 1 file changed, 1 insertion(+)
[ ] content/en/docs/setup/_index.md 1 file changed, 3 insertions(+), 3 deletions(-)
[ ] content/en/docs/setup/best-practices/certificates.md 1 file changed, 2 insertions(+), 2 deletions(-)
[ ] content/en/docs/setup/learning-environment/minikube.md 1 file changed, 3 insertions(+)
[ ] content/en/docs/setup/production-environment/container-runtimes.md 1 file changed, 14 insertions(+), 7 deletions(-)
[ ] content/en/docs/setup/production-environment/tools/kops.md 1 file changed, 64 insertions(+), 4 deletions(-)
[ ] content/en/docs/setup/production-environment/windows/user-guide-windows-containers.md 1 file changed, 101 insertions(+), 6 deletions(-)
[ ] content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/tasks/access-application-cluster/configure-dns-cluster.md 1 file changed, 2 insertions(+), 2 deletions(-)
[ ] content/en/docs/tasks/administer-cluster/cluster-management.md 1 file changed, 4 insertions(+)
[ ] content/en/docs/tasks/manage-kubernetes-objects/kustomization.md 1 file changed, 6 insertions(+), 6 deletions(-)
[ ] content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md 1 file changed, 3 insertions(+), 3 deletions(-)
[ ] content/en/docs/tasks/run-application/horizontal-pod-autoscale.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/tasks/tools/install-minikube.md 1 file changed, 43 insertions(+)
[ ] content/en/docs/tutorials/configuration/configure-redis-using-configmap.md 1 file changed, 2 insertions(+), 1 deletion(-)

0 files to be renamed
0 files to be deleted
Proposed Solution
Use git diff to check what is changed in the upstream. And apply the upstream changes manually
to the content/ko of dev-1.17-ko.1 branch.
For example:
# checkout `dev-1.17-ko.1`
...
# check what is updated in the upstream
git diff upstream/dev-1.16-ko.6 dev-1.17-ko.1 -- content/en/_index.html
# apply changes to content/ko
vi content/ko/_index.html
...
# commit and push
...
# make PR to `dev-1.17-ko.1`

Pages to Update
/language ko
/priority backlog
/kind cleanup

/assign

/close


Returning genres in Browse

Hi there,
I'd like to be able to return either the normal model for the Anime by adding a param to set that to true. Or i'd like to be able to return genres to the small anime model. Are either of those two possible to implement? It would save me from making another request to your API as I can just filter them on the client if I have that extra information.
Actually it'd just be nice to be able to set what extra keys you'd like that are already available in the large model as params to the request. But that sounds like a bit more work!
Thanks,
Jeff

The first point is not possible at the moment (not until api v2) and I'm not sure what you mean in your second point; is it you want small anime models to include their genres or something else?

Yeah exactly. So I'm returning all the anime in a season using /browse and I'd like to be able to see their genre. I'm returning all of them and I'd like to filter them on the client without having to make another API call
Sent from my iPhone
On Aug 6, 2016, at 3:48 AM, Josh Star <notifications<EMAIL_ADDRESS>wrote:
The first point is not possible at the moment (not until api v2) and I'm not sure what you mean in your second point; is it you want small anime models to include their genres or something else?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/joshstar/AniList-API-Docs/issues/96#issuecomment-237945716, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABKiFQvRCPxy7o2LfqkWZH15w0U6PQP7ks5qc5OEgaJpZM4JeAGY.

Any update on this? If not I guess i'll have to rework my logic to just use the API for filtering genres (I can see you've got that setup). But i wanted to take advantage of caching all anime per season and just filtering on the front-end. Less work on the API too.

I've added the genres array to the anime/manga small model, it should be live in the upcoming update later this month.

Thanks a lot josh!
Sent from my iPhone
On Aug 9, 2016, at 5:46 AM, Josh Star <notifications<EMAIL_ADDRESS>wrote:
I've added the genres array to the anime/manga small model, it should be live in the upcoming update later this month.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/joshstar/AniList-API-Docs/issues/96#issuecomment-238387850, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABKiFYJMySZG1J7BqJY2cUhcuyzsqeGYks5qd6OegaJpZM4JeAGY.


[CARBONDATA-1917] While loading, check for stale dictionary files

If any stale dictionary files is left in a load, the next load should check for the stale dict files existence and alert the user.

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[x] Testing done
Manual Testing

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2478/

retest this please

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1025/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2249/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2253/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1030/

retest this please

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1111/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2326/

retest this please

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1115/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1120/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2334/

retest this please

retest this please

retest this please

retest sdv please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2343/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2347/

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2348/

retest this please

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1127/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2349/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2563/

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1130/

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1133/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2566/

retest sdv please

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2570/

Retest sdv please

@dhatchayani ...From my perspective I think this PR is not required. This is a case when user deletes the dictionary and sort index file intentionally from back end from the system and keeps only the dictionary meta file. But in any case user should not be allowed to delete any of the carbon store files.
Therefore I think we should not handle this scenario.

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2587/


Custom Authentication Handler - Unable to retrieve Body

Expected Behavior
Be able to read the Request.Body from the HTTP Request.
Actual Behavior / Motivation for New Feature
Unable to retrieve the body. The reason for doing this is I'm implementing an API Key setup with HMAC and would like to verify the body data against the HMAC headers.
##Notes
I'm unsure if this is by design or not however i can't find a way to actually retrieve the body request from my custom authentication handler. By changing ocelots request body manipulation so that multiple reads can be made by doing:  request.EnableBuffering(). Fix's the problem, unsure if this is not done on purpose due to memory.

I have similar problem. I made custom authentication handler (based on Microsoft.AspNetCore.Authentication.AuthenticationHandler) which checks api key.
When I call controller method without api key or with wrong api key I got 401 with body.
When I call ocelot method without api key or with wrong api key I got 401 without body.
I noticed that in case of ocelot method HandleChallengeAsync is not called after HandleAuthenticateAsync.
May be I doing something wrong but I can't find right way how check api key and return message only for the secured routes.
Perhaps it is due with this issue https://github.com/ThreeMammals/Ocelot/issues/1144

yes same issue, i am trying to  make a HMAC authentication, so need to check hash of the request body, but i can not get request body in custom AuthenticationHandler, how to work around this

So i went through the source code more thourhgly and


Clean up old Workflow runs

Description
Clean up workflows that no longer exist, but are still visible in the Actions UI. Those workflows can be easily detected by checking if they have a link to existing yaml file.
To avoid additional work this issue might be only done after the issue Introduce naming scheme for workflow names and workflow files is completed, because in the mentioned issue the structure of workflows might change.
Motivation
Better visibility and up to date Actions on the UI.
ToDo [Developer]

[x] Remove workflow runs that no longer exists in the pipelines

PRs

[ ] https://github.com/kyma-project/istio/pull/1119

AC [PO]

[ ] Workflows that no longer exists are no longer visible in the Actions UI
[x] Follow up for API Gateway is created or Workflows are also clean up for API Gateway

For future reference. The script lists 500 recent workflow runs and concurrently will issue a deletion 15 at a time.
gh run list --json databaseId -q '.[].databaseId' -w {WORKFLOW_FILE} --limit "500" |
            xargs -IID -P 15 gh run delete ID


  That's definitely not what we want!  (Possibly caused by #4).
Option 1: Drop the existing table and replace it with the data from the export file.
Option 2: Upsert data.  Existing data should not change if the source data hasn't changed.
Option 1 is easiest, but not ideal if the data has been edited or augmented in some way.

inaturalist-to-sqlite uses insert with replace=True: https://github.com/dogsheep/inaturalist-to-sqlite/blob/master/inaturalist_to_sqlite/utils.py#L39


Markdown function wrongly expects at least 2 parameters. Easy fix!

I believe the parameters in the function header have to be switched around.
Wrong:
public function markdownFunction($context = false, $string, $block = true)

Better:
public function markdownFunction($string, $block = true, $context = false)

Simple testcase
This twig code fragment throws an error:
{% markdown *}
**bold?**
{% endmarkdown %}

https://github.com/getgrav/grav/blob/ed87faad92829b4218f91a3c81990f1fad23a7f5/system/src/Grav/Common/Twig/TwigExtension.php#L619

That is not markdown function but a twig tag issue.

Issue was introduced 10.8.2019 in revision 618a59921a1c4b54fdcf22ccffbc11aace912701.

Fixed in latest release


Modify generate sourcemaps script

Modify generate sourcemaps script in order to work with typescript files.

@joshuap hi, I don't know what the contributions guidelines are for this project but can you help with reviewing this PR?
For RN you can also use a index.tsx / index.ts file as main file, and running the current generate source maps script doesn't do anything if you have a ts file.
Thanks! :)

I was doing some research into this, and I'm not sure we want to include this.
Let me explain, and maybe you can help me understand.
The official RN docs state that index.js should remain index.js, even if the project uses TypeScript, as changing the entry point to .ts/x will cause issues with production bundling.
From https://reactnative.dev/docs/typescript:

I dug deeper into this, and came across these two recent PRs suggesting that index.js be converted to index.ts for TypeScript-only projects. The PR comments indicate that RN doesn't have support for anything but index.js for an entry point, and that renaming it would cause issues for bundling:
https://github.com/react-native-community/react-native-template-typescript/issues/121
https://github.com/facebook/react-native/pull/27491
I also looked into some RN TypeScript templates, and also found that while App.js has been renamed to App.tsx, index.js remains index.js.
Finally, since index.js is just a simple call to registerComponent to mount App, there really shouldn't be any cause to use JSX or TypeScript in there.
The technicals of the PR are correct, but I'm not sure adding this (and having to support the extra use case) would be prudent here.
But, once again, maybe you can help me understand. :)

Hi @andreybutov, you're correct. In my case I've migrated all files to typescript.
Although it's not recommended changing the index file into a typescript file, if you do, you can specify it in the "Bundle React Native code and images" phase, in Build Phases. Check screenshot below.
Maybe my case is unique and in this case my PR is not required. 😄

OK. We're going to hold off on pulling this in for now. Thanks!

No worries! Thank youu! 😄


provide fmt.Sprintf function alternative

this is more generic and not limited to proxy-wasm, will do in another repository

https://github.com/tetratelabs/getenvoy/issues/101

so far, we could use strings and strconv as an alternatives

verified that fmt.Sprintf works fine with TinyGo's WASI support


version 1.0.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

96 of 96 (100.0%)  changed or added relevant lines in 28 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.7%) to 89.713%

Totals

Change from base Build<PHONE_NUMBER>:
2.7%

Covered Lines:
2594

Relevant Lines:
2849

💛  - Coveralls


fix yaml for load testing

Description
Fix internal.yaml file in order to begin load testing for moves routing to services counseling.
This PR ensures that the yaml file passes validation.
You can check it out using the apitools swagger pareser
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?
Setup
Add any steps or code to run in this section to help others prepare to run your code:
echo "Code goes here"

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against d42d1ecd68004884bcc0c241014e6647efa3350a


Migrate ReactInstanceManager to lambda's

Summary:
We have modern Java now, so inline these lambda's to improve readability. Also removed some old logging related to a completed investigation.
Changelog: [Internal]
Reviewed By: rshest
Differential Revision: D45062457

Merged as https://github.com/facebook/react-native/commit/d97cca3d711655485545298bc5f4a8cffd4c6f34


follow up on odo create for docker pushTarget

odo needs to properly handle the situations where the user switches between pushTargets
URL created for Docker but pushed to Kube
▶ odo preference set pushtarget docker
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated

▶ odo url create
 ✓  URL backend-8080 created for component: backend with exposed port: 49213

To create the URL on the cluster, please use `odo push`

▶ odo preference set pushtarget kube
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated

▶ odo push
 •  Push devfile component backend  ...
 ✓  Waiting for component to start [24s]

Applying URL changes
 ✗  Failed To Update Config To Component Deployed.
Error: unable to create url: unable to create ingress: error creating ingress: Ingress.extensions "backend-8080" is invalid: spec.rules[0].host: Invalid value: "backend-8080.": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a

The error message is confusing, it doesn't say anything useful. It should detect what happened, and tell user what to do.
This PR https://github.com/openshift/odo/pull/2885 is adding URL Kind to env.yaml which might be useful here.
URL created for Kube but pushed to Docker
▶ odo url create  --host apps.testocp4x.psiodo.net
 ✓  URL backend-8080.apps.testocp4x.psiodo.net created for component: backend

To create the URL on the cluster, please use `odo push`

▶ odo preference set pushtarget docker
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated

▶ odo push
 •  Push devfile component backend  ...
 ✓  Pulling image quay.io/eclipse/che-java11-maven:nightly [2s]
 ✓  Starting container for quay.io/eclipse/che-java11-maven:nightly [595ms]
 ✓  Push devfile component backend [2s]
 ✓  Changes successfully pushed to component

Url was created but it was silently ignored :-/
secure for docker
▶ odo url create -h

      --secure             Creates a secure https url

How is --secure going to work on docker?
Originally posted by @kadel in https://github.com/openshift/odo/pull/2906#issuecomment-618362722

/area devfile
/area url
/area local

/assign

This issue should have been fixed in: https://github.com/openshift/odo/pull/2906
@kadel Can you help verify? Thanks

URL created for docker but push to kube
$ odo url create --port 8080
 ✓  URL local-java-spring-boot-8080 created for component: java-spring-boot with exposed port: 61981

To apply the URL configuration changes, please use `odo push`
$ cat .odo/env/env.yaml
ComponentSettings:
  Name: java-spring-boot
  Url:
  - Name: local-java-spring-boot-8080
    Port: 8080
    ExposedPort: 61981
$ odo preference set pushtarget kube
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated
$ odo url create local-java-spring-boot-8080 --host <IP_ADDRESS>.com --port 8080
 ✗  the url local-java-spring-boot-8080 already exists for a different push target. Please recreate one using different a url name

URL created for kube but push to docker
$ odo url create testurl1 --host <IP_ADDRESS>.com --port 9090
 ✓  URL testurl<IP_ADDRESS>.4.com created for component: java-spring-boot

To apply the URL configuration changes, please use `odo push`
e$ cat .odo/env/env.yaml
ComponentSettings:
  Name: java-spring-boot
  Url:
  - Name: local-java-spring-boot-8080
    Port: 8080
    ExposedPort: 61981
  - Name: testurl1
    Port: 9090
    host: <IP_ADDRESS>.com
$ odo preference set pushtarget docker
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated
$ odo url create testurl1 --port 9090
 ✗  the url testurl1 already exists for a different push target. Please rerun the command using a different a url name.

Also remove --secure flag if the push target is docker.

Here is the current behavior:
Swicth push target from docker to kube
Switch push target and run odo push, should successfully create pod&services, should see a warning message indicate there is no valid urls defined in env.yaml for ingress.
$ odo preference set pushtarget kube
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated

$ odo push
 ⚠  found url(s) defined for docker, but no valid urls with ingress host defined for the component java-spring-boot.

Validation
 ✓  Validating the devfile [224302ns]

Creating Kubernetes resources for component java-spring-boot
 ✓  Waiting for component to start [5s]

Applying URL changes

Syncing to component java-spring-boot
 ✓  Checking files for pushing [1ms]
 ✓  Syncing files to the component [3s]

Executing devfile commands for component java-spring-boot
 ✓  Executing devbuild command "/artifacts/bin/build-container-full.sh" [3s]
 ✓  Executing devrun command "/artifacts/bin/start-server.sh" [3s]

Pushing devfile component java-spring-boot
 ✓  Changes successfully pushed to component

Swicth push target from kube to docker
should successfully create container, should see a warning message indicate there is no valid urls defined in env.yaml for docker.
$ odo url create --host <IP_ADDRESS>.com --ingress
 ✓  URL java-spring-boot-8<IP_ADDRESS>.4.com created for component: java-spring-boot

To apply the URL configuration changes, please use `odo push`
$ odo preference set pushtarget docker
? pushtarget is already set. Do you want to override it in the config Yes
Global preference was successfully updated

$ odo push
 ⚠  found url(s) defined for ingress, but no valid urls with exposed port defined for the component java-spring-boot.

Validation
 ✓  Validating the devfile [121135ns]

Creating Docker resources for component java-spring-boot
 ✓  Pulling image maysunfaisal/springbootbuild [943ms]
 ✓  Starting container for maysunfaisal/springbootbuild [432ms]
 ✓  Pulling image maysunfaisal/springbootruntime [682ms]
 ✓  Starting container for maysunfaisal/springbootruntime [429ms]

Syncing to component java-spring-boot
 ✓  Checking files for pushing [1ms]
 ✓  Syncing files to the component [263ms]

Executing devfile commands for component java-spring-boot
 ✓  Executing devbuild command "/artifacts/bin/build-container-full.sh" [2s]
 ✓  Executing devrun command "/artifacts/bin/start-server.sh" [1s]

Pushing devfile component java-spring-boot
 ✓  Changes successfully pushed to component


Wrapping Button and reexporting prevents ButtonGroup from working

Description
When Gluestack Button "GButton" is wrapped and reexported, ButtonGroup no longer work
CodeSandbox/Snack link
https://codesandbox.io/s/example-44622s
Steps to reproduce

Import Button as GButton from library
Export const Button with children props
 {children}
If you wrap with a  in another component it no longer works

gluestack-ui Version
0.1.32
Platform

[X] Expo
[ ] React Native CLI
[ ] Next
[X] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
No response

@capturetheworld The codesandbox is not updated, could you please update that and let us know .

@capturetheworld The codesandbox is not updated, could you please update that and let us know .
Hi, this is a code snippet from my project, I cannot share the entire project as the code is proprietary. This gives you enough of an idea of how I am exporting the Button component. See Lines 27-30

@capturetheworld The codesandbox is not updated, could you please update that and let us know .

Hi, this is a code snippet from my project, I cannot share the entire project as the code is proprietary. This gives you enough of an idea of how I am exporting the Button component. See Lines 27-30 @makkarMeenu

Please try this snippet for wrapping the Button. Let me know if it works.
export const Button = ({ children , ...props}:any) => {
  return <GButton {...props}>{children}</GButton>;
};