Zero delay retry loop

NetworkResourceProviderClient.get_long_running_operation_status() does not set a value for result.retry_after. When long running operations start looping and checking the status they get None for this value. Then in places like NetworkInterface.create_or_update [line 7124], this check fails:
if delay_in_seconds == 0:
  delay_in_seconds = 15

This has the nasty potential of eating up my rate limit quota and locking me out from further API calls for an hour.

Hey Mike.  Thanks for finding this.
Did you see delay_in_seconds set to None or is that an assumption?  I only ask since time.sleep complains if you pass it anything that is not a positive number.  If it were getting None at that point you would see a TypeError. Particularly line 86 to add a default value.
 self._retry_after = kwargs.get('retry_after', 0)
I am guessing you are using the code from pypi though and not this repo?  There was a change to networkresourceprovider.py around a week ago https://github.com/Azure/azure-sdk-for-python/commit/f7f90121099a699b010fe50a76ea7bd3526d9473.

I got the latest from pypi after I first saw the bug. I tried again after updating and it still exists. I'm pretty sure it was None because I manually put a print() in there to check.
Sent from Outlookhttp://aka.ms/Ox5hz3
On Thu, Oct 1, 2015 at 8:58 PM -0700, "Christopher Wilcox" <notifications<EMAIL_ADDRESS>wrote:
Hey Mike. Thanks for finding this.
Did you see delay_in_seconds set to None or is that an assumption? I only ask since time.sleep complains if you pass it anything that is not a positive number. If it were getting None at that point you would see a TypeError. Particularly line 86 to add a default value.
self._retry_after = kwargs.get('retry_after', 0)
I am guessing you are using the code from pypi though and not this repo? There was a change to networkresourceprovider.py around a week ago f7f9012https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-python%2Fcommit%2Ff7f90121099a699b010fe50a76ea7bd3526d9473&data=01|01|mideeks%40microsoft.com|7f00f8e9a07e4bcbde9a08d2caddb179|72f988bf86f141af91ab2d7cd011db47|1&sdata=9BQHXb8AAeY7w6tJP0Efrd%2BnAyVs%2BnATb5XxhF%2Bb%2FAQ%3D.

Reply to this email directly or view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-python%2Fissues%2F485%23issuecomment-144911292&data=01|01|mideeks%40microsoft.com|7f00f8e9a07e4bcbde9a08d2caddb179|72f988bf86f141af91ab2d7cd011db47|1&sdata=6no6xRA9mJSmFqVWnTonN%2FzR9q12xBS3%2Bik3iUpmyVE%3D.

Fixed in latest release, which I just published to PyPI.


[ot-ctl] fix ot-ctl hang

Fixes #6377
Fixes #6376
Fixes #6355

Beyond the scope of this PR:

The code uses char lineBuffer[kLineBufferSize]; for storing input lines, and assumes that char lineBuffer[kLineBufferSize]; may not be large enough to hold the a whole line. However, char lineBuffer[kLineBufferSize]; can actually hold the whole line because kLineBufferSize == OPENTHREAD_CONFIG_CLI_MAX_LINE_LENGTH. We can further simply the implementation if we just receive and send the whole line within the lineBuffer.
We need to make sure that OPENTHREAD_CONFIG_CLI_MAX_LINE_LENGTH can hold the maximum length of a command . The command I have in mind is dataset set active .... The typical length of active dataset hex string is 200. So, OPENTHREAD_CONFIG_CLI_MAX_LINE_LENGTH should be at least 200 + strlen("dataset set active "), which is currently true for OPENTHREAD_CONFIG_CLI_MAX_LINE_LENGTH = 384. We might need to add a static_assert to make sure this always hold true.

Thoughts? @bukepo


No redirect to login page when secure pages are accessed unauthenticated

When we hit the profile page (secure page) , without logging in, it is not redirecting to login page, instead JS error is thrown saying token is null

It's intentional for that sample :) These samples present incremental feature additions for securing a whole application. There will be a sample up shortly called 04-Authorization which will cover what you're looking for. In the meantime, check out angular-jwt and, in particular, the instructions for adding requiresLogin.

Here's the sample: https://github.com/auth0-samples/auth0-angularjs-samples/tree/master/04-Authorization

Thanks for the quick turn around @chenkie . Will test it soon, and close the issue.
Btw, we are starting a new angular spa using auth0 with api auth, and i assume this project should be prefered than the old angular samples, which doesnt use newer options for api auth (OIDC) ?

No prob :)
Yes that's correct! We recommend following OIDC as laid out in these samples and in the quickstarts.


How can I integrate this project API to TensorFlow or Caffe?

Is there some tips or docs? Thanks a lot!

Hi,
We're working on it but it's still early stages. We'll publish some blog posts and examples in the coming weeks / months.

Thank you

Thank you very much for your work! :+1:
We will continue to focus on this repo.

The licensing terms allow you to do this if you intend to do it yourself. We intend to integrate our library with Caffe and TensorFlow however this is still work in progress, so watch this space!

I really hope that ARM can intergrate upstream like Intel.

Hi @Thunderbob! Will you be creating a repository for Caffe/Tensorflow with the ComputeLibrary?

We're only getting started, we haven't decided yet how we were going to contribute to these projects

As I contributed CLBlast support in Caffe, I see two options to optimise Caffe on ARM Mali GPUs when using the BLAS approach for computing convolutions:

Implement all Mali-optimised functions needed by Caffe in a BLAS library (based on this released compute library) and provide its integration with Caffe similar to clBLAS, CLBlast, [ISAAC]
(https://github.com/ptillet/isaac), etc.
Provide a Mali-optimised plugin for CLBlast using a new plugin framework proposed by @intelfx. In fact, he already used the Mali-optimised SGEMM code that ARM released over a year ago for creating a Mali-optimised CLBlast overlay. The new framework should allow to use Mali-optimised implementations on Android (where the LD_PRELOAD trick is not available).

I'm happy to provide further pointers and discuss.

@psyhtest  seems openblas works best

@austingg Yes, but it was fairly optimised implementation on quad-core Cortex-A15 @ 1700 GHz vs unoptimised implementation on quad-core Mali-T628 @ 600 MHz...

Closing for inactivity. Anyway to answer the initial question:
There is a project made exactly to solve this kind of problems: ArmNN
Here is the link to the repo:
https://github.com/ARM-software/armnn


Support for running on OSX

from the development meeting today 11-13-22 , there is an issue with all nodes not able to access the configuration node. Might be the case of UDP issues on docker and OSX.
@Micky-G FYI, do you know if lionel has a github account?

He does yes, liolemaire

great! @liolemaire can you put your logs here?

Hi, it worked for me on os x 12.5.1 (mpb intel 2020, ram 16gig),
docker desktop : 4.14.1
I had to install Xquartz : 2.8.4
In xquartz, you need to issue the command 'xhost +' to allow connection to the x11 server from the container.
In vscode, I updated the devcontainer.json like this :
'
"containerEnv": {
// "DISPLAY": "${localEnv:DISPLAY}",
"DISPLAY":"host.docker.internal:0",
'


Discourse shield is added.

Signed-off-by: Swapnil Bhabal<EMAIL_ADDRESS>Description
fixed #69
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Excellent.


Fix Keysym names for named Keysyms and test them agains xkbcommon

Fixes https://github.com/rust-windowing/xkeysym/issues/18.
This PR changes the names of the named keysyms to get them in line with the names that xkbcommon returns and tools such as xdotool expect. The only change needed for named keysyms was to get rid of the XK_ part. The only part I am struggling with, is returning the correct name for keysyms representing unnamed unicode codepoints. I have no experience with Rust no_std and don't know how to implement it. The corresponding C code is very simple, so I left a placeholder and left this PR in a "Draft" state. Hopefully somebody can fill in the correct Rust code for it.
I also added a test to make sure the function continues to return the same names for all possible keysyms. There are a few commented out parts that I needed to try the test on my machine with a newer libxkbcommon. I will remove them once the placeholder is properly implemented
I added the KEYSYM_MAX constant. It was added in xkbcommon 1.6.0 and shortens the time the test runs.

The test runs for a long time, so it might be a good idea to split it into a separate Workflow

I have no experience with Rust no_std and don't know how to implement it.

TL;DR: I believe this would require an API break to implement.
Let's ignore no_std for the moment. How would you implement this "normally"? This has to return Option<&'static str> (and this is publically reachable via Keysym::name(). So, the only possibility is to have some kind of static, huge string table (well, it could be lazily initialised, but this is still complicated).
This in contrast to the API from xkbcommon which gets a buffer as its argument and writes the string into that. Thus, no 'static (in Rust-speak) is involved.

Can't the static string get generated dynamically? Something like this:
fn name() -> Option<&'static str> {
    static RESULT: [u8; 3] = [97u8, 98u8, 99u8];
    core::str::from_utf8(&RESULT).ok()
}

The values of the RESULT buffer would have to get calculated.

This would require a massive table for computation that would surely bloat the program. Just returning names like this is enough; we don't have to be concerned about the entirety of Unicode.
We could also add a new method that handles Unicode, but returns Cow<'static, str> instead. This would only be enabled on an alloc feature.
For the tests, try running the test cases in parallel with rayon. It should speed things up.

Something like this:

That RESULT can only store a single value. As a caller, I can keep references to multiple names at once: let foo = [k1.name(), k2.name(), k3.name()];. Thus, to be sound, RESULT may no longer be modified after it was filled once (since the borrow is 'static and thus effectively forever).

Okay, returning names for keysyms representing Unicode codepoints will not be part of this PR.
I used rayon for the test. The tests are failing right now, because the newest keysyms were not yet added to this crate. Once https://github.com/rust-windowing/xkeysym/pull/26 gets merged, it should succeed. This will happen on a regular basis, but the output of the test lists the differences.
The test is ignored per default and does not run in the CI workflow, because running the test still takes around 5 mins. Unfortunately we have to install xkbcommon even if the test is ignored. This adds around 2 min to the time the workflow takes to complete.
I think the PR is ready to be reviewed

Please rebase on #26

Sure, it has been rebased


Added xml wrapper tags around a few key prompt items

Seems to create better results on anthropic, which is all I use now.
One thought is to use langdspy which automatically takes declarative language and reformats it into the optimal prompting strategy for the architecture, very lightweight: https://github.com/aelaguiz/langdspy
Just a suggestion I like the results for my own use case.
Thanks for building this!

Thanks for sharing this.
It looks like you didn't make changes to editblock_prompts.py. That's the one that is used by default with Claude 3.5 Sonnet.
Are you using fenced-diff or udiff  with Anthropic models?

lol I understand less than I thought. I'll see if I can make this work right. Thx paul!


Replace Orbis Chat with the new Discussion Feed module

Description
Replace the Orbis chat module on the Spatial Browser with Orbis's new Discussion Feed module.
Requirements

Replace the current chat bubble & toggle with three buttons across the bottom of the browser (Parcel Chat, WebAR/Web Content, & Gallery)--see mockup
Use the geo-web-browser context with a : separator followed by the parcel ID (or other unique identifier) to create separate chats for each parcel

I think it should probably start clean. Safer to not force the new licensor to assume the "baggage" of the last licensor.


How to modify link uri if getClient can't receive arguments?

Can you maybe provide a bit of code showcasing how you did it until now and where you were getting that from in the first place?

It's probably better in an issue, since you'll not be the last person with this question :)
So I'll write a bit more of a "general answer here":
Modifying a request URI as a "one-off" with an existing Apollo Client
Generally, there are a few different ways you can modify the uri of outgoing requests.
From call site:
You can just use the uri value in context with an outgoing query
const { data } = await getClient().query(MY_QUERY, {
  context: {
    uri: "someOtherUri",
  },
  fetchPolicy: "no-cache",
});

Using an uri callback
In an uri callback you have access to the full operation, which means that you could look at things like operation.operationName or operation.variables - or in this example, operation.getContext().
export const { getClient } = registerApolloClient(() => {
  return new ApolloClient({
    cache: new InMemoryCache({
      // ...
    }),
    link: new HttpLink({
      uri(operation) {
        const context = operation.getContext();
        if (context.token) {
          return `${process.env.CMS_API_URL}?token=${context.token}`;
        }
        return process.env.CMS_API_URL;
      },
      // ...
    }),
  });
});

In your case, you'd then call that with token in the context - your call site wouldn't really be aware of the uri abstraction:
const { data } = await getClient().query(MY_QUERY, {
  context: {
    token: "myToken",
  },
  fetchPolicy: "no-cache",
});

❗Note that in both of these examples, I used fetchPolicy: "no-cache".
That's not generally necessary, but something to consider: You are redirecting your Apollo Client to a different data source here. If you wouldn't use no-cache, the results from that other data source would get merged into your existing InMemoryCache - and in your case, where you probably have "original" and "draft" with the same typename and id, there's a risk that the drafts would overwrite the originals in the cache.
Creating more than one cache
With that warning note from the last example - you might also want to consider creating more than one cache.
In that case, call registerApolloClient twice to create two independent cache instances per incoming request.
const { getClient } = registerApolloClient(...)
// this will probably still need something like context to pass in the token for this cache on this request., unless you get the token from a cookie, then you can directly call `cookies()` inside the callback function in `registerApolloClient`.
const drafts = registerApolloClient(...)

later distinguish between getClient() calls and drafts.getClient() calls.

Great! I'm gonna close this issue then. Have a great day!


Implement Cloud block

Feature description 💡
Terraform's preferred backend block is the Cloud block as of Terraform 1.1.0. It would be great to see this backend type implemented in Terrakube.
Along with that, the cloud block allows use of workspace tags, which allow for more dynamic workspace selection within Terraform code. These would be a great addition to the workspace settings in Terrakube.
Reference:
https://developer.hashicorp.com/terraform/language/settings/backends/remote
https://developer.hashicorp.com/terraform/cli/cloud/settings
Anything else?
No response

Support to use terraform init with cloud block using workspace name was added in #406
Support for terraform plan, apply and destroy will be added in other PRs

Hello @alfespa17 @jderieg, this issue is now focused on implementing the cloud block. For the Workspace tagging feature, please see the new issue I created here: https://github.com/AzBuilder/terrakube/issues/409
I will try to add Workspace tagging in the next 2.14.0 version

Cloud block was implemented in #411 and #406 It will support the following usage:
terraform {
  cloud {
    organization = "simple"
    hostname = "8080-azbuilder-terrakube-sscrnu9jbie.ws-us99.gitpod.io"

    workspaces {
      name = "samplecloud"
    }
  }
}

We are still missing the use of "tags", we will need to implement #409 before adding the support in the cloud block.

Support to use cloud block with tags will be added in #420, I am closing this issue because the basic cloud block usage is now supported in version 2.14.0


fix(runtime): remove react-markdown

Remove react-markdown because its 6.x version will cause vite build error and 7.x+ version only export esm package which blocks ssr.

LGTM, and this introduce a breaking change?

Yes, but i checked in installer and zbs-insight. They don't use md format text.


[WIP] Integrating hvpa-controller into Gardener

What this PR does / why we need it:
Integrating hvpa-controller into Gardener
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
perf tests are going on, and we will update the results, and then will remove the WIP label.
Release note:

I've identified several issues with HVPA which IMHO should be fixed before getting this in:

[ ] https://github.com/gardener/hvpa-controller/issues/31
[ ] https://github.com/gardener/hvpa-controller/issues/32

The performance tests results are summarised here.
@mvladev
gardener/hvpa-controller#31 is resolved now via gardener/hvpa-controller#38.
However, regarding gardener/hvpa-controller#32, can you please suggest next steps after our last discussion on the github issue page. Thanks.
PS: Removing the WIP label.

Ref https://github.com/gardener/gardener/pull/1456#issuecomment-535046429.


fix(nuxt): don't override options signature with schema

🔗 Linked issue
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
A regression from introducing schema was overriding the basic signature of the NuxtOptions interface when there was no defined schema.
However, I would also consider fixing upstream in untyped - or maybe defaulting to [key: string]: unknown? (cc: @pi0)
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Defaulting to : unkown seems a nice idea for me 👍🏼

Defaulting to : unkown seems a nice idea for me 👍🏼

Was thinking about the same 👍🏻

Great - let's default to [key: string]: unknown upstream.
But I think we also do need to merge this for consistency.

Without this option, a single schema property generates an interface without a signature, but if there are no defined properties there there is a signature. That's inconsistent no matter what the default signature is, I think.

Moreover, I don't think we want to overriding NuxtOptions/NuxtConfig key signatures, or run the risk of incompatible ones.

So I would feel much safer omitting the signature entirely in Nuxt itself (unless there's something I'm missing that we need it for - @pi0?)


Bug: Build Error on Next.js 14 on v1.20.2, works on v1.18.0

Describe the issue
Module not found: Can't resolve './SVGLoader.mjs'
Module not found: Can't resolve './widgets/InsertImageWidget.mjs'
Steps to reproduce the issue

Install<EMAIL_ADDRESS>in Next.js Project
Import in project
Run next build

Expected behavior
Build Successful
Observed behavior
js-draw works on v1.18.0
What I suspect from the changes v1.18.0 to v1.19.0 is SVGLoader.ts is moved to SVGLoader/index.ts.
But in the js-draw/dist/mjs/lib.mjs, SVGLoader.ts import doesn't changed
packages/js-draw/src/SVGLoader.ts → packages/js-draw/src/SVGLoader/index.ts

Version information
1.20.2
Platform
No response
Logs
> next build

  ▲ Next.js 14.2.3
  - Experiments (use with caution):
    · instrumentationHook

   Creating an optimized production build ...
Failed to compile.

./node_modules/js-draw/dist/mjs/Editor.mjs:10:1
Module not found: Can't resolve './SVGLoader.mjs'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./node_modules/js-draw/dist/mjs/lib.mjs
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/document-sign/Dialog.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/ProcessActionDocumentSign.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/ApplicantPreview.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/ApplicantPage.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/page.tsx

./node_modules/js-draw/dist/mjs/image/export/editorImageToSVG.mjs:3:1
Module not found: Can't resolve '../../SVGLoader.mjs'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./node_modules/js-draw/dist/mjs/Editor.mjs
./node_modules/js-draw/dist/mjs/lib.mjs
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/document-sign/Dialog.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/ProcessActionDocumentSign.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/ApplicantPreview.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/ApplicantPage.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/page.tsx

./node_modules/js-draw/dist/mjs/lib.mjs:23:1
Module not found: Can't resolve './SVGLoader.mjs'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/document-sign/Dialog.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/ProcessActionDocumentSign.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/ApplicantPreview.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/ApplicantPage.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/page.tsx

./node_modules/js-draw/dist/mjs/rendering/renderers/SVGRenderer.mjs:2:1
Module not found: Can't resolve '../../SVGLoader.mjs'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./node_modules/js-draw/dist/mjs/rendering/lib.mjs
./node_modules/js-draw/dist/mjs/lib.mjs
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/document-sign/Dialog.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/ProcessActionDocumentSign.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/ApplicantPreview.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/ApplicantPage.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/page.tsx

./node_modules/js-draw/dist/mjs/toolbar/AbstractToolbar.mjs:28:1
Module not found: Can't resolve './widgets/InsertImageWidget.mjs'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./node_modules/js-draw/dist/mjs/lib.mjs
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/document-sign/Dialog.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/process-action/ProcessActionDocumentSign.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/preview/ApplicantPreview.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/_components/ApplicantPage.tsx
./src/app/admin/(menu)/(shell)/job-schedule/applicant/[id]/page.tsx

> Build failed because of webpack errors

Additional information
No response

Thanks for the support and quick response!

./node_modules/js-draw/dist/mjs/lib.mjs
/**
 * The main entrypoint for the NPM package. Everything exported by this file
 * is available through the [`js-draw` package](https://www.npmjs.com/package/js-draw).
 *
 * ## Example
 *
 * [[include:doc-pages/inline-examples/main-js-draw-example.md]]
 *
 * @see
 * - {@link Editor}
 * - {@link Editor.loadFromSVG}
 * - {@link AbstractToolbar.addActionButton }
 * - {@link EditorSettings}
 *
 * @packageDocumentation
 */
import  Editor  from './Editor.mjs';
export  *  from './image/lib.mjs';
export  *  from './types.mjs';
export  *  from './inputEvents.mjs';
export  { default as getLocalizationTable, matchingLocalizationTable }  from './localizations/getLocalizationTable.mjs';
export  *  from './localization.mjs';
export  { default as SVGLoader }  from './SVGLoader.mjs';
export  { default as Viewport }  from './Viewport.mjs';
export * from '@js-draw/math';
export  *  from './components/lib.mjs';
export  *  from './commands/lib.mjs';
export  *  from './tools/lib.mjs';
export  *  from './toolbar/lib.mjs';
export  *  from './rendering/lib.mjs';
export  *  from './testing/lib.mjs';
export  *  from './shortcuts/lib.mjs';
export  { default as EventDispatcher }  from './EventDispatcher.mjs';
export  { default as Pointer, PointerDevice }  from './Pointer.mjs';
export  { default as UndoRedoHistory }  from './UndoRedoHistory.mjs';
export  *  from './util/lib.mjs';
// @internal
export  { default as __js_draw__version }  from './version.mjs';
import  AbstractToolbar  from './toolbar/AbstractToolbar.mjs';
export { Editor, AbstractToolbar, };
/**
 * Using the HTMLToolbar alias is deprecated. Use
 * `AbstractToolbar` instead.
 * @deprecated
 */
export { AbstractToolbar as HTMLToolbar };
export default Editor;

I think this import is invalid because it's pointing to .mjs file, which doesn't exist
export  { default as SVGLoader }  from './SVGLoader.mjs';

Directory of node_modules\js-draw\dist\mjs

Directory of node_modules\js-draw\dist\mjs\SVGLoader

This should be fixed in v1.20.3. Please let me know if this is still an issue.
For future reference, the .mjs extension is added by the build script on this line.


Fix node-red crashing when volume control used in flow

When adding volume control node to a flow, node-red would crash because of a missing null check.
Fixes #45.

Please pull.


GitBook Editor 6.3.2:  Copy/paste code cannot be edited

Category

What is the current behavior?

Edit pasted code
Additional information
Linux Mint 18

It's working for me (6.3.3 on OS X), can you make a small video/gif of the bug?

Same on 6.3.3 on Mint 18 (Ubuntu based)


Jinja2 in the vendor directory isn't used. Can be dropped.

The directory contains a copy of jinja2 which isn't used by the user code.
Digging through the history ... This was used to be a requirement for click-completion.
However, this is now dropped, and instead click own completion is used.
Dropping it can reduce the package size.
The tests code uses it, but one can expect developers to be able to install jinja2.

Thanks, we need to figure out is there any other unneeded vendors. Can you help?

I'm already on it. Tracking this on the rebuild for Gentoo.
Thanks for the quick response!


Fix PyPI auto upload; bump version

Coverage remained the same at 100.0% when pulling bf35964ec50fad155186b949a8d6d3a8d8864791 on jeskew/version_bump_pypi into<PHONE_NUMBER>c2853cde92fdf5ac62f5a553719ba9 on master.


Update README.md

if docker version > 1.25.5, use docker compose command to start ShenYu

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

pls add my wechat: yijia1949


Panic on wasm: time not implemented on this platform

I gave it a spin and it seems to fail at runtime: time not implemented on this platform (on WASM runtime).
All I did so far it to add minitrace with features = ["enable"] and did the following at startup:

  let collector = LocalCollector::start();
  let result = run_flow(req, env).await;
  let local_spans = collector.collect();
  let parent_context = SpanContext::random();
  let span_records = local_spans.to_span_records(parent_context); // ❗

I'm pretty sure this originates in to_span_records, because without calling it, it seems to work fine. I printed local_spans and it seems to correctly contain the spans 🎉

Originally posted by @dotansimha in https://github.com/tikv/minitrace-rust/issues/185#issuecomment-1906809996

It'll be hard to get timing done without a timer... Do you have any idea? @dotansimha

what about https://lib.rs/crates/web-time? @andylokandy

Originally posted by @dotansimha

Seems good. Would you like to create a PR for adding web-time to minstant? SystemTime is only used in https://docs.rs/minstant/latest/minstant/struct.Anchor.html#method.new

@andylokandy Sure! https://github.com/dotansimha/minstant

Closed by https://github.com/tikv/minstant/pull/34


[stable/airflow] added option to specify git-clone initContainer custom resources

Signed-off-by: Joshua Leuenberger<EMAIL_ADDRESS>What this PR does / why we need it:
The default resource limitation of the resource container using the main container needed to much resources. #22274
Added the option to specify the initContainer ressources
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

Hi @thesuperzapper
I went ahead and updated the resource configuration in the values below initContainer.
I think it is the cleaner way to not use git-sync resources for both.
Thanks for your inputs.
@gsemet Can you take a look at this?

@gsemet do not merge this yet

@yehlo this PR would introduce more issues, see the alternative here: #22298
What you did in this PR is confusing, as it doesn't do what it implies, you have called the value dags.initContainer.resources when it isn't the resources for initContainer.
The best option is to use the already present dags.git.gitSync.resources, as to preform the initial git-clone will not require more resources than any following syncs.

@thesuperzapper I see that I fd-up the indentation of the values.yaml. Fixed it in the most recent commit. Maybe you meant that with?

What you did in this PR is confusing, as it doesn't do what it implies, you have called the value dags.initContainer.resources when it isn't the resources for initContainer.

I do think that the git-sync and git-clone containers need to be treated separately since they are different mechanisms.
Using the git-sync resources attribute on the git-clone container is in my opinion confusing.  And even if you don't use the git-sync mechanism you'd have to define atleast the resources part if need be.

I agree that we should seperate the requests between git-sync and git-clone, but do you realise that initContainer is not the same as the git-clone container?

Wait, I am mistaking preinitdb for initContainer.

This looks ok now, please squash your commits.

@gsemet this looks ok to test

I guess the naming is kind off confusing.
Thanks for your inputs.
@gsemet It's up for merging now :)


HTTP instead of HTTPS

While following the tutorial, I noticed that the test link provided for the API endpoint was "https://localhost:/". I believe that this link should be changed to "http://localhost:/" and I would like to suggest this change.
My reasoning for this suggestion is that to use the "https" protocol we need to mess with settings in postman which the user might forget to enable later. However, in the case of this tutorial, we are simply testing a very basic API endpoint, and there is no sensitive information being transmitted. Therefore, using the "http" protocol is more appropriate and avoids any unnecessary overhead associated with setting up an SSL connection.
Furthermore, using the "http" protocol is more straightforward and easier to understand for beginners who may not be familiar with setting up SSL certificates. This change will make the tutorial more accessible and easier to follow, even preventing users from making mistakes by forgetting to disable the "SSL certificate verification" setting in postman which would give a confusing error.
I believe that this change will improve the overall user experience of the tutorial and I would be more than happy to submit a pull request to implement this change. Thank you for your consideration.

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

ID: ab408035-6313-a183-9940-32de00e0e977
Version Independent ID: ab408035-6313-a183-9940-32de00e0e977
Content: Tutorial: Create a minimal API with ASP.NET Core
Content Source: aspnetcore/tutorials/min-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @wadepickett
Microsoft Alias: wpickett

@bunyod16, I see your point, and agree using https makes it a step more complicated.  However, based on feedback I have seen over the years, I believe whenever we made things a step simpler by using HTTP rather than HTTPS, we would get complaints that the example/tutorial is neither secure nor realistic (if I remember correctly).  Hense we are always using HTTPS (or both HTTP and HTTPS).  For an API example like this, HTTPS would usually be expected.  That said, it is cool you offered to do the PR yourself, thanks for the awesome community spirit!
@tdykstra and @Rick-Anderson, who have been involved in this topic longer than I, in case they have some additional thoughts on the matter.

Closing this issue after additional author feedback and per note  above on the larger scope of customer feedback we have received in the past on avoiding HTTPS and after reviewing past customer feedback history on this topics.


CSS Upgrade

I can go through and update it to look a little more modern.

@TheShonuff ,
Yes it's currently on decent ui,
We would like to upgrade ui but without being effected in the product (codeblocks preview & print )

@TheShonuff

@SGI-CAPP-AT2 simple upgrade not affecting the original idea of minimalism. Added hover feature for buttons.

@TheShonuff ,
It's effected on the code block preview
&
The border radii for inputs not looking good


Dynamic opening hours

Knaus and Rundhallen are always closed according to the opening hours, because the opening hours for these areas are determined by events. Ideally, the opening hours should be automatically updated when events are made for these areas. The opening hours for the specific area pages (like https://www.samfundet.no/daglighallen) should also be inferred from the opening hours instead of being static.

Going through old issues:
The way all "pages" work, which are dynamic based on markdown/html, prevents us to get opening hours from the server in a simple way. A way around this would be to split up pages into pages related to areas, say pages_area and regular pages, such that pages_area looks up the opening hours from the database, as found in the administration panel. Will be considered when rewriting Samfundet.


⚠ Bofrost.be has degraded performance

In 21bebe0, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1625 ms

Resolved: Bofrost.be performance has improved in fae114a.


Bug: VC 1.0.0 breaks compat with MC 1.18.2

Hiya!
From the crash log:
A potential solution has been determined:
	 - Replace mod 'Villager Converting' (villagerconverting) 1.0.0 with any version that is compatible with:
		 - minecraft 1.18.2
Unmet dependency listing:
	 - Mod 'Villager Converting' (villagerconverting) 1.0.0 requires any 1.19.x version of 'Minecraft' (minecraft), but only the wrong version is present: 1.18.2!
	 - Mod 'RoundaLib' (roundalib) 0.1.8 requires any 1.19.x version of 'Minecraft' (minecraft), but only the wrong version is present: 1.18.2!

Your Modrinth listing says "Fabric 1.18.2—1.19" are the compats for 1.0.0. Cheers!

Ah, thanks for that. Modrinth should really remove that functionality entirely, or better document exactly what they mean by "primary" - "most recent version" is already covered by the mod version field / filename, and "version for the most recent MC" is already handled by the game version field. It's far superior UX if users can trust that clicking a download button labelled with their version of MC guarantees compatability, without having to navigate to a deeper page first to make sure. They should add a conditional dropdown field after clicking the download icon if the labeled mod version has separate files per MC version.
Curse already made (*sigh*) manual dependency management awful enough; Modrinth doesn't need to retraumatise the modding community any further, haha.


Run all linters even if PR has no files applicable to the linter

We recently added the below linters as Required gate checks for PR gates

Linted: GITHUB_ACTIONS
Linted: GITLEAKS
Linted: YAML

But, we are noticing that the super-linter skips linters if no file types applicable to the linter changed in the PR. So, if a PR has no workflow file changes, GITHUB_ACTIONS linter is skipped. And if there are no YAML file changes, YAML linter is skipped. When that happens, the PR is unmergeable even if it has approvals.
Is there a way to tell super-linter to always run all the liners and report back status to PR?

Ok, we solved this by setting VALIDATE_ALL_CODEBASE=true in the linter.


shelter: build failure with make LA=1

cd inclavare-containers
make -C shelter LA=1
make: Entering directory '/root/inclavare-containers/shelter'
CGO_ENABLED=1 go build "-mod=vendor" -buildmode=pie   -ldflags "" -o /root/inclavare-containers/shelter/racommand.o .
# github.com/inclavare-containers/shelter
/root/go/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
/root/inclavare-containers/ra-tls/build/lib/libra-challenger.a(wolfssl-la-challenger.o): In function `la_verify_sgx_cert_extensions':
/root/inclavare-containers/ra-tls/sgx-ra-tls/wolfssl-la-challenger.c:43: undefined reference to `g_eid'
collect2: error: ld returned 1 exit status

Makefile:60: recipe for target '/root/inclavare-containers/shelter/racommand.o' failed
make: *** [/root/inclavare-containers/shelter/racommand.o] Error 2
make: Leaving directory '/root/inclavare-containers/shelter'

Currently there is no requirement to do LA support in shelter. Just leave this as a place holder.

ra-tls is depreciated so this issue won't be fixed.


Support for command line args in test schemes

Support for passing command line args to
test schemes
Fixes #1514

@rasberik can you confirm this PR addressed your issue? Thanks!

args = ["--command_line_args=-AppleLanguages,(en)"] (comma separated)
Expected Output would be: -AppleLanguages (en) (space separated)
Also, I noticed from original source that there can be several --command_line_args, so each new argument is defined separately, and comma representing space?
@ra1028 Can you please have a look if you have time?

In my understanding, this PR already supports extracting multiple --command_line_args in Array.extractCommandLineArguments(). However, rules_apple also supports a comma-separated list of arguments in a single flag, so I think rules_xcodeproj should follow that too.
e.g.
--command_line_args=-UIPreferredContentSizeCategoryName,UICTContentSizeCategoryXXXL
- -UIPreferredContentSizeCategoryName
- UICTContentSizeCategoryXXXL

If you pass space-separated arguments in Xcode and dump ProcessInfo.processInfo.arguments, you'll see that they are propagated as separate elements like ["-AppleLanguages", "(ja)"].
It means that passing the following two results in the same.
- -AppleLanguages (ja)

- -AppleLanguages
- (ja)

Therefore, I think @rasberik's concerns would solve if comma-separated arguments will be supported.


fix(subscription): validation rule for tag values

Overview/summary
Replace this with a brief description of what this Pull Request fixes, changes, etc.
This PR fixes/adds/changes/removes

fixes #000

Breaking changes

Replace me

Testing evidence
Please provide testing evidence to show that your Pull Request works/fixes as described and documented above.
As part of this pull request I have

[ ] Checked for duplicate Pull Requests
[ ] Associated it with relevant issues, for tracking and closure.
[ ] Run and make fmt & make docs to format your code and update documentation.
[ ] Created unit and deployment tests and provided evidence.
[ ] Updated relevant and associated documentation.

This has broken my implementation I use a codebase tag with link to github source as part of tagging taxonomy this is backed by a few strict policies and automation around how required tags are derived. So essentially I need github.com/org/blahblah. What's the background behind this? I have 10s of thousands of resources outside of the sub deployment that depend on the taxonomy as-is for automation and the like.

This has broken my implementation I use a codebase tag with link to github source as part of tagging taxonomy this is backed by a few strict policies and automation around how required tags are derived. So essentially I need github.com/org/blahblah. What's the background behind this? I have 10s of thousands of resources outside of the sub deployment that depend on the taxonomy as-is for automation and the like.

What's your scenario specifically? This change was to liberalize the validation on tag values so things like / are now allowed...

I see that intention now, let me check dependabot hasn't done something dumb. Since bumping the version I'm now getting the old error for the first time...

@luke-taylor @matt-FFFFFF
https://github.com/Azure/terraform-azurerm-lz-vending/blob/2b4d4579246ed7e650ff09b364e16643818f0b2d/modules/subscription/variables.tf#L158
tags wrong or something not merged?

was a release never created for this... ?

was a release never created for this... ? Last release was April 10th, this was merged April 16th.

Hey, just cut the release. v4.1.1

was a release never created for this... ? Last release was April 10th, this was merged April 16th.

Hey, just cut the release. v4.1.1

sweet

Telemetry embedding 4.1.0 in the name, not sure what sort of impact that has on tracing accuracy.


Pagination component causes hydration error

Hello @Balick! Can you please provide more context about the error and your code(how are u using this component). As, Pagination Component is working fine when I was running their site(/apps/www) locally.
Thanks!

also i am facing same issue

Hello @Balick! Can you please provide more context about the error and your code(how are u using this component). As, Pagination Component is working fine when I was running their site(/apps/www) locally.
Thanks!

To replicate the reported issue, please follow the Next.js + Shadcn installation guide here and include the Pagination component as it is presented in the documentation.
After conducting an investigation, I have addressed and resolved this issue in pull request #2335.

Maybe it's related to #2416 .

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


add cloudflare-operator-system namespace to verify

Following the getting started I noticed it was missing the -n cloudflare-operator-system namespace

Hey @acrogenesis yes indeed. Thanks for the PR!


Write-Warning style is not reset when PSAnsiRendering is enabled

Steps to reproduce
Enable-ExperimentalFeature PSAnsiRendering

Then, restart PowerShell.
Write-Warning 'xxx'

Expected behavior
With PSAnsiRendering disabled, output yellow text only for warning message (xxx), not for prompt.

Actual behavior
With PSAnsiRendering enabled, output yellow text for warning message (xxx), and all the following output.
Write-Error resets the style.

Environment data

PS D:\tools\PowerShell-7.2.0-preview.2-win-x64> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.2.0-preview.2
PSEdition                      Core
GitCommitId                    7.2.0-preview.2
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

seems to be fixed in #14698.


Missing json dependency?!

It seems like with Neovim master "json" is required?!
Not sure, but I've noticed this with https://github.com/tweekmonster/vim-testbed - and have not really investigated yet.
+docker run -a stderr --rm -v /home/travis/build/tweekmonster/vim-testbed/example:/testplugin -v /tmp/tmp.MbsDtSmQ3M:/home/vimtest -v /home/travis/build/tweekmonster/vim-testbed/example/test/plugins:/home/vimtest/plugins vim-testbed-example neovim-master --headless -u NONE '+ruby open('\''/home/vimtest/ruby'\'', '\''w'\'') { |f| f << '\''ruby was here'\'' }' +q
function provider#ruby#Call[8]..remote#host#Require[10]..provider#ruby#Require, line 10
Vim(if):ch 1 was closed by the client
/usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- json (LoadError)
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/gems/2.4.0/gems/neovim-0.6.0/lib/neovim/logging.rb:2:in `<top (required)>'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/gems/2.4.0/gems/neovim-0.6.0/lib/neovim/session.rb:1:in `<top (required)>'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/gems/2.4.0/gems/neovim-0.6.0/lib/neovim/client.rb:3:in `<top (required)>'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/gems/2.4.0/gems/neovim-0.6.0/lib/neovim.rb:1:in `<top (required)>'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/gems/2.4.0/gems/neovim-0.6.0/lib/neovim/host.rb:1:in `<top (required)>'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
^Ifrom /usr/lib/ruby/gems/2.4.0/gems/neovim-0.6.0/bin/neovim-ruby-host:3:in `<top (required)>'
^Ifrom /usr/bin/neovim-ruby-host:23:in `load'
^Ifrom /usr/bin/neovim-ruby-host:23:in `<main>'
Failed to load ruby host. You can try to see what happened by starting nvim with $NVIM_RUBY_LOG_FILE set and opening the generated log file. Also, the host stderr is available in messages./bin/bash: line 30: /tmp/tmp.MbsDtSmQ3M/ruby: No such file or directory
+'[' '' '!=' 'ruby was here' ']'
+echo 'Failed to get output from Ruby for neovim-master --headless.'
Failed to get output from Ruby for neovim-master --headless.

Installing the Alpine ruby-json fixed it.
Feel free to close this issue.

Hmm yeah I just added this dependency, that's weird that it's failing on ruby 2.4.0, since it should be part of the stdlib: http://ruby-doc.org/stdlib-2.4.0/libdoc/json/rdoc/JSON.html.
I'll patch this and push a new gem shortly. Sorry about that.

No problem.  It might be something special about Alpine Linux, where this is a separate package for space reasons etc.
Just having the dependency would have failed, too - since it likely requires additional headers then to build it.

Can you give it another try with the latest release (0.6.1)? It uses multi_json instead of a hard json dependency, and only loads it when logging is enabled.

Thanks!
Trying in https://github.com/tweekmonster/vim-testbed/pull/52.

Thanks for the quick fix!


Use OpenAPI to document the API

Description
Use OpenAPI to document the Metecho API. This replaces manually-maintained .rst files for each endpoint which were often outdated and inaccurate with an auto-generated schema.yml file:

Extract API schema using drf-spectacular
Output AP details to Sphinx with sphinxcontrib-openapi
Generate browsable docs using Redoc

Steps to test/reproduce
Quick demo: use an online Redoc viewer to parse the contents of schema.yml.
Redoc viewer (same as above but running locally)

Go to http://localhost:8000/api/schema/redoc/. Refresh the page whenever the views/serializers change.

Sphinx

Run python manage.py spectacular --validate --file docs/api/schema.yml to compile a new schema after changing views/serializers. This can be added to CI checks as well to verify the schema is always up to date.
Run cd docs && make html. The resulting API docs will be written to docs/_build/html/api/index.html
As an alternative we could embed the Redoc viewer directly in the Sphinx-generated HTML with https://sphinxcontrib-redoc.readthedocs.io/en/stable/

Show me

What's the maintenance cost?

All CRUD actions on viewsets are documented automatically, they don't need any changes made to their view or serializer code.
Special actions on viewsets (any method decorated with @action) need to be decorated with @extend_schema(request=InputSerializer, responses=OutputSerializer). This also means we should use more serializers instead of manually handling request data in the view (which I think is a good thing). The docstring will also be picked up by the schema. More advanced use cases are supported (like multiple return codes) but this should cover around 80% of cases.
Any custom serializer fields should be decorated with @extend_schema_field(RETURN_TYPE) if the return type cannot be derived from annotations. This also applies to serializer method fields.
If a serializer field simply calls a model method, the return type should be type-annotated in the model.

I think this PR already did the most difficult part, which is decorating and annotating all existing code. Maintenance going forward should be pretty easy and I would argue that it'll take less time than writing the docs manually, as well as being much less error-prone.
More features
Since we now have a standard-compliant schema.yml file we can use it to auto-generate TypeScript interfaces and even an API client using something like openapi-typescript-codegen. drf-spectacular mentions this use case and makes some recommendations in their docs.

 Automatically document the API

This can be added to CI checks as well to verify the schema is always up to date.

I think we might as well go ahead and do this in this PR?

Will do 👍

As an alternative we could embed the Redoc viewer directly in the Sphinx-generated HTML...

I'm not clear on the pros/cons here, so I'll defer to whatever you recommend @jerivas

sphinxcontrib-openapi will just output some static HTML (demo here), while sphinxcontrib-redoc will generate and embed the Redoc UI in the HTML generated by Sphinx. My preference is towards Redoc. @davisagli does that work for you?

@jgerigmeyer https://github.com/oddbird/Metecho/pull/1495/commits/9ecd8c77d00bda2d5f883bd4d69614dcf0b08a86 checks the schema as part of the python test suite.


storing complex valued data

Adding a waveform with complex valued data (e.g. spectra) raises a TypeError:
TypeError: The trace's dtype ('complex128') is not allowed inside ASDF. Allowed are little and big endian 4 and 8 byte signed integers and floating point numbers.

A work around is to split the real and imaginary parts into separate tags, but this seems kludgy.  Is this a design decision, or am I missing something?

That's a design decision but if you disagree we are very open for discussion.
The waveforms are really intended to store seismic waveforms as time series data. Anything else is supposed to be stored in the auxiliary data group. The reasoning is that most other things just don't have an established standard on how they should be stored and also what meta information is really required and the auxiliary data gives flexibility to store anything. This is also described in the paper in a bit more detail: http://dx.doi.org/10.1093/gji/ggw319
>>> import numpy as np
>>> from pyasdf import ASDFDataSet
>>> ds = ASDFDataSet("temp.h5")
>>> ds.add_auxiliary_data(data=np.empty(1000, dtype=np.complex128),
...                       data_type="Spectra", path="name_for_it",
...                       parameters={"df": 0.01})

# Reading it again:

>>> ds.auxiliary_data.Spectra.name_for_it
Auxiliary Data of Type 'Spectra'
	Path: 'name_for_it'
	Data shape: '(1000,)', dtype: 'complex128'
	Parameters:
		df: 0.01

data_type is supposed to be the type of the data in a single word, and parameters are arbitrary extra arguments useful to store meta information. Note that the paths can be arbitrarily nested, e.g. path="some/deep/path" allowing for complex hierarchies.

Thanks Lion.  I agree with your aux data approach and see the logic.  I should have started by saying thanks for the work on ASDF and this great tool!
I'd like to calculate and store complex spectra for segments.  My approach now is to chunk up the data into single days and store an nsegment x npts complex array for each day under path=<year>/<julday>/<sta_chan>.  Is there a more efficient approach?
Nathan

Hi Nathan,
thanks :-) The next step is to get the community to try it out and hopefully adopt it but it seems to be going quite well.
path=<year>/<julday>/<sta_chan> is perfectly fine. Nesting helps when there are a lot of datasets but its not strictly necessary. HDF5 has no limit on the number of datasets per group and I guess it gets a bit slower once a certain number is reached but that is probably a very high number.
One thing to keep in mind: if you use e.g. path="2009/135/BW_ALTM" you can no longer use the dot accessors in pyasdf, e.g.
ds.auxiliary_data.Spectra.2009.135.BW_ALTM
does not work. This is a limitation of Python as attributes cannot start with a number. You have to do
ds.auxiliary_data.Spectra["2009"]["135"]["BW_ALTM"]
which does exactly the same but tab completion in IPython no longer works. Otherwise it has no further consequences.
You could use path="Y2009/J135/BW_ALTM" and tab completion/dot access works which might be a bit more convenient.
Cheers!
Lion


Derive instance Typeable MaxSize to fix build on GHC 7.8

In my capacity as a hackage trustee, I've made a revision to stop <IP_ADDRESS> from trying to build on GHC 7.8 https://matrix.hackage.haskell.org/package/size-based


Add tlv schema for unsigned integer

After making the schema generic, it made more sense to merge TlvCodec / TlvObjectCodec and Template into the Schema object.
This PR implements an unsigned integer encoding / decoding only without the validate() method.
After we are converged on the code structure, I will implement validate() in the next PR, splitting UnsignedNumberTlv into UInt8Tlv / UInt16Tlv, UInt32Tlv, UInt64Tlv than add other data type Tlv schemas.

@turon Updated per your comments


World Mortality Rate Analysis and Prediction

ML-Crate Repository (Proposing new issue)
:red_circle: Project Title : World Mortality Rate Analysis and Prediction
:red_circle: Aim : This project will help us in analyzing and predicting the mortality rate using the provided dataset.
:red_circle: Dataset : https://www.kaggle.com/navinmundhra/world-mortality
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.
Hello, ML-Crate contributors, this issue is only for the contribution purposes and allocated only to the participants of SWOC 2.0 Open Source Program and JWOC '22 Open Source Program.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'SWOC' and 'JWOC' contributors of 'ML-Crate' project.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID :
Approach for this Project :
What is your participant role?

[ ] SWOC 2.0 Participant.
[ ] JWOC 2022 Participant.
[ ] Contributor

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

I want to work on this issue under JWOC

Follow the guidelines and comment out with proper details mentioned in the issue @nishtha2405

@abhisheks008 I would like to work on this issue.
Name: Piyush Bhujbal
GitHub profile link: https://www.github.com/PiyushBL45t
Approach for this project:

Filter the dataset.
Analyze the columns.
Take out useful columns.
Dropping out useless columns.
Making visualizations.
Implementing ML algorithms if necessary.
Derive useful results from the visuals.

Participant Role: HSOC participant

You need to create a prediction model, and before that a good EDA is required.
Issue assigned to you @PiyushBL45t

Thanks @abhisheks008/ML-Crate
@.***>
On Wed, Aug 3, 2022, 1:45 PM Abhishek Sharma @.***>
wrote:

Assigned #355 https://github.com/abhisheks008/ML-Crate/pull/355 to
@PiyushBL45t https://github.com/PiyushBL45t.
—
Reply to this email directly, view it on GitHub
https://github.com/abhisheks008/ML-Crate/pull/355#event-7116375642, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASB2BKNWRSFIRV4D354T4PDVXITCLANCNFSM55NRT5KQ
.
You are receiving this because you were assigned.Message ID:
@.***>

I will do it
On Sat, Jul 23, 2022, 7:16 PM Abhishek Sharma @.***>
wrote:

Assigned #110 https://github.com/abhisheks008/ML-Crate/issues/110 to
@PiyushBL45t https://github.com/PiyushBL45t.
—
Reply to this email directly, view it on GitHub
https://github.com/abhisheks008/ML-Crate/issues/110#event-7050310191,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASB2BKO7ZLDD3U4SDAUOJBLVVPZS5ANCNFSM5NGKWUDA
.
You are receiving this because you were assigned.Message ID:
@.***>


Update logos

What does this PR do?

Fixes # (issue)
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@Borda i can't see my changes reflected in the doc build. any idea?

@edenlightning Might need to change or somehow override the path here since we use pt_lightning_sphinx_theme:
https://github.com/PyTorchLightning/lightning_sphinx_theme/blob/73a7d937ae5423100e1268263f6d1c09edcab585/pt_lightning_sphinx_theme/static/css/theme.css#L9726

@edenlightning @Borda We currently have no logo on README because https://github.com/PyTorchLightning/pytorch-lightning/pull/4844 removed the old lightning logo image which was also used in Bolts' README.md. Shall we merge this PR so that we can have the new logo image in README.md and continue to apply the new logo to the docs in another PR maybe?


Unable to build new eks cluster from scratch

Description
I am trying to create an EKS platform for launching our application code. Currently we have nothing up and running in AWS that is managed by Terraform. Ideally we want to spin up and tear down entire infrastructures using a single set of terraform config. Currently I cannot get the EKS module to build a successful plan.
When trying to plan or apply, this module will fail due to an internal dependency issue with the for_each statement in the main.tf file on line 207 as well as the sub-module eks-managed-node-group\main.tf line 427. (See the error output below)
╷
│ Error: Invalid for_each argument
│
│   on <PATH TO EKS MODULE>\main.tf line 207, in resource "aws_iam_role_policy_attachment" "this":
│  207:   for_each = var.create && var.create_iam_role ? toset(compact(distinct(concat([
│  208:     "${local.policy_arn_prefix}/AmazonEKSClusterPolicy",
│  209:     "${local.policy_arn_prefix}/AmazonEKSVPCResourceController",
│  210:   ], var.iam_role_additional_policies)))) : toset([])
│     ├────────────────
│     │ local.policy_arn_prefix is a string, known only after apply
│     │ var.create is true
│     │ var.create_iam_role is true
│     │ var.iam_role_additional_policies is empty list of string
│
│ The "for_each" value depends on resource attributes that cannot be determined until apply, so Terraform cannot
│ predict how many instances will be created. To work around this, use the -target argument to first apply only the
│ resources that the for_each depends on.
╵
╷
│ Error: Invalid for_each argument
│
│   on <PATH TO EKS MODULE>\modules\eks-managed-node-group\main.tf line 427, in resource "aws_iam_role_policy_attachment" "this":
│  427:   for_each = var.create && var.create_iam_role ? toset(compact(distinct(concat([
│  428:     "${local.policy_arn_prefix}/AmazonEKSWorkerNodePolicy",
│  429:     "${local.policy_arn_prefix}/AmazonEC2ContainerRegistryReadOnly",
│  430:     "${local.policy_arn_prefix}/AmazonEKS_CNI_Policy",
│  431:   ], var.iam_role_additional_policies)))) : toset([])
│     ├────────────────
│     │ local.policy_arn_prefix is a string, known only after apply
│     │ var.create is true
│     │ var.create_iam_role is true
│     │ var.iam_role_additional_policies is empty list of string
│
│ The "for_each" value depends on resource attributes that cannot be determined until apply, so Terraform cannot
│ predict how many instances will be created. To work around this, use the -target argument to first apply only the
│ resources that the for_each depends on.
╵

Versions

Terraform:

 Terraform v1.1.2
on windows_amd64

Provider(s):

+ provider registry.terraform.io/hashicorp/aws v3.72.0
+ provider registry.terraform.io/hashicorp/cloudinit v2.2.0
+ provider registry.terraform.io/hashicorp/helm v2.4.1
+ provider registry.terraform.io/hashicorp/kubernetes v2.7.0
+ provider registry.terraform.io/hashicorp/tls v3.1.0

Module:

module "heliponix-eks" {
  source = "terraform-aws-modules/eks/aws"

  cluster_name          = var.cluster-name
  cluster_version       = var.k8s-version
  cluster_enabled_log_types = [
    "api",
    "audit",
    "authenticator",
    "controllerManager",
    "scheduler",
  ]

  create_iam_role = true
  iam_role_name = "${var.cluster-name}ClusterRole"

  vpc_id = module.heliponix-vpc[var.vpc-network-type].vpc_id
  subnet_ids = concat(
    module.heliponix-vpc[var.vpc-network-type].public_subnet_ids,
    module.heliponix-vpc[var.vpc-network-type].private_subnet_ids,
  )

  cluster_endpoint_private_access = true
  cluster_endpoint_public_access  = true
  cluster_endpoint_public_access_cidrs = [
    "<IP_ADDRESS>/0",
  ]
  cluster_security_group_id = module.heliponix-vpc[var.vpc-network-type].control_plane_security_group_id
  cluster_service_ipv4_cidr = "<IP_ADDRESS>/12"

  enable_irsa                 = true # IAM Role for Service Accounts (IRSA)
  openid_connect_audiences    = ["sts.amazonaws.com"]

  eks_managed_node_groups = {
    managed-data-plane = {
      iam_role_arn            = aws_iam_role.node-instance.arn
      desired_capacity        = var.desired-node-count
      max_capacity            = var.max-node-count
      min_capacity            = var.min-node-count
      launch_template_id      = aws_launch_template.worker-node.id
      launch_template_version = "1"
      subnets                 = module.heliponix-vpc[var.vpc-network-type].private_subnet_ids
      update_config = {
        max_unavailable_percentage = 50
      }
    }
  }
  depends_on = [
    module.heliponix-vpc,
    aws_iam_role.node-instance,
    aws_launch_template.worker-node,
  ]
}

Reproduction
Steps to reproduce the behavior:
Currently there are no AWS resources created in the region

terraform init
terraform plan

Expected behavior
No internal files should have dependency issues
Actual behavior
The IAM role policy attachment uses local.policy_arn_prefix which uses data.aws_partition.current.partition which is known only after apply
Terminal Output
(in the description)

Duplicate of #1753 - see thread for more details

Note - you shouldn't need your depends_on block, you already have those resources specified in the cluster definition and they will create the appropriate dependencies. You can double check by comparing graph outputs


feat: remove de-AT if possible

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

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 59.618%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
1332

Relevant Lines:
2021

💛  - Coveralls


menu options on Ubuntu 16.04

I still have to hit "alt" to pull up the file option etc. on the <IP_ADDRESS> build
I don't know what to type in the search bar if i want to import/export a key
Since the "fix" didn't work, maybe you could supply a map of what the menu options are so I can use nexus-qt

Try doing a

sudo apt-get remove appmenu-qt5

and restart. Let me know if that takes care of it.

Yes.  That worked!  Thank you.
And I now see the options are just the btc core options too.   I guess I was used to using armory on top of it for bitcoin.
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com https://tutanota.com

Apr 2018 14:00 by<EMAIL_ADDRESS><EMAIL_ADDRESS>

Try doing a
sudo apt-get remove appmenu-qt5
and restart. Let me know if that takes care of it.
—
You are receiving this because you authored the thread.
Reply to this email directly, > view it on GitHub https://github.com/Nexusoft/Nexus/issues/70#issuecomment-380108993> , or > mute the thread https://github.com/notifications/unsubscribe-auth/Aj20qNEGshxNSqKVr582LgsTbAN9-xGGks5tnLsGgaJpZM4TKb9R> .


Support scala 3.0.0-M3

@bplommer thank you for this contribution! 🚀 I'll review this over this week/weekend.
@LMnet, would be great if you could take a look too.

I'm +1 on this.
Great work! Thanks @bplommer


error while building android example

I get this error while building the android example
System information

OS Platform and Distribution :ubunut 20.04 lts
Compiler version : gcc 9
Programming Language and version : python 3.8

bazel build -c opt --config=android_arm64 mediapipe/examples/android/src/java/com/google/mediapipe/apps/handtrackinggpu:handtrackinggpu
--define MEDIAPIPE_DISABLE_GPU=1
--action_env PYTHON_BIN_PATH=$(which python3)
Complete Logs:
Starting local Bazel server and connecting to it...
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'bazel_skylib' because it already exists.
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'pybind11' because it already exists.
DEBUG: /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/external/tf_runtime/third_party/cuda/dependencies.bzl:51:10: The following command will download NVIDIA proprietary software. By using the software you agree to comply with the terms of the license agreement that accompanies the software. If you do not agree to the terms of the license agreement, do not use the software.
INFO: Analyzed target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/handtrackinggpu:handtrackinggpu (154 packages loaded, 14664 targets configured).
INFO: Found 1 target...
INFO: Deleting stale sandbox base /home/kitmek/.cache/bazel/_bazel_kitmek/35c4330a980a6ba06cfd6fda00a7a779/sandbox
INFO: From ProtoCompile mediapipe/calculators/util/landmarks_to_render_data_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/core/gate_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/core/split_vector_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/collection_has_min_size_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/rect_to_render_data_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/annotation_overlay_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/detections_to_render_data_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/internal/callback_packet_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/labels_to_render_data_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/calculator_profile.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/tool/calculator_graph_template.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/core/constant_side_packet_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/rect_transformation_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/framework/calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/core/clip_vector_size_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tensor/tensors_to_landmarks_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/landmark_projection_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/core/flow_limiter_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/detections_to_rects_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tensor/tensors_to_floats_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tensor/tensors_to_classification_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/thresholding_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tensor/inference_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/tensor/image_to_tensor_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile mediapipe/calculators/util/association_calculator.pb.h:
bazel-out/android-arm64-v8a-opt/bin/external/com_google_protobuf/src: warning: directory does not exist.
ERROR: /home/kitmek/mediapipe/mediapipe/java/com/google/mediapipe/framework/BUILD:34:16: Validating proguard configuration failed (Exit 127): proguard_whitelister failed: error executing command bazel-out/k8-opt-exec-50AE0418/bin/external/bazel_tools/tools/jdk/proguard_whitelister --path mediapipe/java/com/google/mediapipe/framework/proguard.pgcfg --output ... (remaining 1 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox proguard_whitelister failed: error executing command bazel-out/k8-opt-exec-50AE0418/bin/external/bazel_tools/tools/jdk/proguard_whitelister --path mediapipe/java/com/google/mediapipe/framework/proguard.pgcfg --output ... (remaining 1 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox
/usr/bin/env: 'python': No such file or directory
Target //mediapipe/examples/android/src/java/com/google/mediapipe/apps/handtrackinggpu:handtrackinggpu failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 17.715s, Critical Path: 9.19s
INFO: 468 processes: 125 internal, 337 linux-sandbox, 6 worker.
FAILED: Build did NOT complete successfully

I tried all the solutions but still , I have the problem

Duplicate https://github.com/google/mediapipe/issues/1128

Hi @AhmedEmadEldinHussin, Could you please check you're python installation. Above error is because of it as mentioned in the duplicate issue. Thanks!

We are closing this issue  now due to lack of activity


problem with inspector

When I enable inspector, then { please select a scope } appear in window but after clicking on something there is an error in the console

Uncaught TypeError: Cannot read property 'indexOf' of undefined

Mac OS 10.8.3 / Chrome 26.0.1410.43
If You need more info, than let me know

Unable to reproduce.


New feature update notify and a button to set all element in store no "New"

Hi,
Great Job the tools it is amazing i'd like if it is possible two new feature:

For the new element into tab store there is a label "New" can you add a button to set all element not New (Because at moment i have all with these label and i can't understand the new element showed in the list )
The HACS can send a notify when there is a new update to do?

Thanks

1 No
2 Create an automation based of the sensor from it.
There are an example here https://community.home-assistant.io/t/custom-component-hacs/121727/157?u=ludeeus

Thanks


rancher -agent registration  for help

Rancher Version:0.59.1
Docker Version:1.10.2
OS: centos 7.2
Steps to Reproduce:
Results:
Expected:
we  add the same host running the Rancher server as a host in Rancher, host has a private or local IP address like 192.168.1.* [But IP is not fixed]and host ip <IP_ADDRESS>,from quick-start-guide docs ,we know
sudo docker run -e CATTLE_AGENT_IP=<IP_ADDRESS> -d --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent:v0.9.2 http://<IP_ADDRESS>:8080/v1/scripts/DB121CFBA836F9493653:1434085200000:2ZOwUMd6fIzz44efikGhBP1veo.
but  we faild.
Our purpose is not to achieve LAN IP (192.168.1.*) rancher -agent registration, because HOST IP is not fixed.What should we do？

Can you provide your logs from your rancher/agent?

Before re-registering with your -e CATTLE_AGENT_IP, please do the following commands.
# rm -rf /var/lib/rancher/state
# docker rm -fv rancher-agent
# docker rm -fv rancher-agent-staterancher-agent-state

@sunhawk2100 If you are still having issues after my recommended steps, please re-open.


Made Pipelines user guide consistent and clearer

Main changes:

The first section was written as if there was only one output, but the code had two; looks like the markdown wasn't updated when the code was
Removed stray , ready_parameter='ready', auto_advance=True in early example; looks like something meant for the last example
Clarified hierarchical arrangement of .layout
Cleaned up descriptions and narrative flow

I opened some issues found while reviewing this (#731, #732, #733, #734). When those are fixed, the text in this notebook will need to be updated accordingly, so this PR should probably be merged before addressing any of those (or updated each time).
One additional issue is that I wasn't sure why .init() needed to be called or precisely when it should be called; isn't there some way that it can be called automatically?  It's a confusing, stateful thing...

The init issue can probably be solved thinking about it. The issue was that it wasn't obvious how to set up the graph when you declare a simple linear pipeline without calling define_graph, but if we simply build up the linear pipeline as stages are added and then override if define_graph is called there is no problem.

That sounds right from what I remember of that code, thanks.

Changes look good thanks!


Add e2e test cases

/assign @deads2k

/assign @pmorie

/assign @qiujian16

tests need to start somewhere.  Here seems reasonable.
/lgtm
/approve


Bug: Automaticly selects .gjs-lory-slide

The Slider automaticly selects .gjs-lory-slide on clicking a slide. It changes the Background Image for every slide automaticly.

@BerkeAras
Check the example:  https://github.com/artf/grapesjs/blob/gh-pages/demo.html
As you can see you must add selectorManager: { componentFirst: true } to the init if you want to target the id (not the class) of the slide when you select it.
@artf maybe it could be a good idea to add this information to the README  ?
It was a little bit confusing for me also.

@BerkeAras
Check the example:  https://github.com/artf/grapesjs/blob/gh-pages/demo.html
As you can see you must add selectorManager: { componentFirst: true } to the init if you want to target the id (not the class) of the slide when you select it.
@artf maybe it could be a good idea to add this information to the README  ?
It was a little bit confusing for me also.


Weekly crates.io release

What
Part of https://github.com/rerun-io/rerun/issues/1343

Adds get-version command to scripts/ci/crates.py, which can be used to query the current version specified in the root Cargo.toml
Adds the weekly_release workflow, which runs at 2 PM every monday. It will:

Bump the crate versions, and create a pull request
Once the pull request is merged, it will release all crates

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested demo.rerun.io (if applicable)

PR Build Summary
Docs preview
Examples preview

Unfortunately, GitHub doesn't let you dispatch workflows which don't exist on main. Since this won't run by itself until next monday, it's safe to yolo merge it, so I'll do that in order to test it.


Updates to support doc

preview the experience by going to https://dovholuknf.github.io/ziti-doc/api/index.html and clicking on the c api


Add toKelvin method to Temperature Class

Purpose
Add method to convert from Celsius to Kelvin. I had a General Chemistry class last semester and we were constantly using this conversion when working with ideal gasses. I'm sure there are other science-based uses for Kelvin conversion as well.
Tests
Added test to confirm the conversion is accurate.
Docs
If you'd like, I can update the docs to mention this method and the other method in the Temperature class as it doesn't appear to be in the docs at the moment.

Thanks! I'd appreciate a PR that adds any missing method to the docs 👍


Tooltip demo not working

Documentation
Relevant Radix Component(s)
Tooltip
Demo page for the Tooltip does not seem to work. Nothing happens when hovering the "+" icon (macOS Safari 16.1).

@hey-stefan Does your window have focus? can you provide a video?

Well this is embarrassing, but upon further inspection the Tooltip does work. I just did not hold the cursor over it for long enough.
(sidenote: maybe the default delay should be shorter 😅)


fx: 34.0.0 -> 35.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/antonmedv/fx/releases.
meta.description for fx is: Terminal JSON viewer
meta.homepage for fx is: https://github.com/antonmedv/fx
meta.changelog for fx is: https://github.com/antonmedv/fx/releases/tag/35.0.0
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 35.0.0 with grep in /nix/store/1xhy7ciznjd1w5li0nb2l2p3sc243szg-fx-35.0.0
found 35.0.0 in filename of file in /nix/store/1xhy7ciznjd1w5li0nb2l2p3sc243szg-fx-35.0.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

fx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1xhy7ciznjd1w5li0nb2l2p3sc243szg-fx-35.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A fx https://github.com/r-ryantm/nixpkgs/archive/94efc587d82a2a7e9ec2687fd844e1cd95df5285.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/94efc587d82a2a7e9ec2687fd844e1cd95df5285#fx

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1xhy7ciznjd1w5li0nb2l2p3sc243szg-fx-35.0.0
ls -la /nix/store/1xhy7ciznjd1w5li0nb2l2p3sc243szg-fx-35.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

fx

Maintainer pings
cc @figsoda for testing.

Result of nixpkgs-review pr 322913 run on x86_64-darwin 1

1 package built:

fx


Missing license

Hi!
I was lately also thinking whether it would make sense to submit our logs to Sentry (also using Async, so very convenient), so I am happy I stumbled over this library. But it is missing any kind of license, so it is a bit problematic to use and to contribute.
Could you please pick some license? Thanks a lot!

Sorry about that, I must have forgot to add this. Commit c5e438c381584b45f021abc1b5d1653ab24418f1 adds one (public domain).

FYI, I'm having trouble getting nice Async backtraces (see #1). If you have ideas for improving that let me know, or open a pull request.

Thanks!
From what I see it does sound like the best idea to patch Error with support for the raw_backtrace. I don't know if I have time to write these patches but I can see if I can fit that in.
What I am a confused about is that raw_backtrace can only be sensibly used its exception handler, so I am worried that storing it in Error.t wouldn't work since it would point to outdated/invalid data.

I created this issue to get the data we need from Async: https://github.com/janestreet/async_kernel/issues/10
raw_backtrace can be safely passed around. The annoying part is that you can only safely call Printexc.get_raw_backtrace in an exception handler (before calling any other function).


fix handling of null timestamps

When running circle-cli projects I receive an error message similar to parsing time "null" as ""2006-01-02T15:04:05Z07:00"": cannot parse "null" as """
http://stackoverflow.com/questions/26684752/json-decode-cannot-parse-timestamp-in-json-into-go-struct explains that you need to make pointer to *time.Time to handle null dates to become nil.
This PR changes all time.Time -> *time.Time

The downside of this is that we push the responsibility of handling nil times to the end-user, even for times that are never nil; however, given CircleCI's lack of documentation about the possible types returned, this is probably a more robust solution. Do you know which time field specifically was nil?

Closing this due to inactivity, but please feel free to reopen!


Break apart our single global Spanish translation file

This changes breaks apart the large, global Spanish translation files in cfgov/locale/ so that messages that come from individual apps (like ask_cfpb, v1, etc) are stored in their apps.
This includes all the messages that come from our templates after https://github.com/cfpb/consumerfinance.gov/pull/7402, which relocated the majority of them from cfgov/jinja2/v1 into their respective app packages.
How to test this PR
After checking out and running the site with this PR, ensure that translations within each relevant app work.
For example, the search controls in Ask CFPB: http://localhost:8000/es/obtener-respuestas/buscar/?q=
The Financial Well-being tool http://localhost:8000/consumer-tools/financial-well-being/es/
Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)

In the interest of slimming this PR down a little bit, and for general simplification, what would you think about purposefully removing internationalization of Wagtail admin-only strings and/or strings that we know will never be on non-English pages?
Looking at the various apps that are getting locale files here:

App
Needs translations?

ask_cfpb
Yes, pages are in Spanish

cfgov
Probably, if we want to provide our own translations for language names

core
No, because these error messages never make it to the user, and we show a 404 if signature validation fails

jobmanager
No, because we don't have a separate Spanish job listings page

login
Not really, because we don't really support non-English use of the Wagtail admin, and other parts of the login flow aren't translated

mega_menu
Yes, because the menu needs to work in different languages

permissions_viewer
No, Wagtail admin only

regulations3k
No, because we don't support non-English regs (correct me if I'm wrong)

retirement_api
Yes, because there is Spanish content

search
No, Wagtail admin only (also, I think these templates were removed in #7415, so there should be no translatable strings left in this app)

teachers_digital_platform
I don't think so, are there any translated pages here?

wellbeing
Yes, Spanish content

wagtailadmin_overrides
No, Wagtail admin only

v1
Yes, lots of content to be translated

Of the 14 apps above, only 6 really need translations. This increases to 9 if we want to translate our Wagtail admin customizations; to me this is definitely a nice-to-have but short of an actual use case it adds complexity in terms of these translation files with no real benefit. So this PR could be reduced quite a bit if we only generate the translations files we really need.
What do you think?

Just want to amend this:

cfgov
Probably, if we want to provide our own translations for language names Not now, since per ongoing discussion in internal#122 we don't actually need the ability to translate the language names

So this PR could be reduced quite a bit if we only generate the translations files we really need.
What do you think?

Not sure it reduces the PR as such, since removing the {% trans %} and _() calls, but I've done that and pushed that change because it does clean up our use of translations — and I like the clarifying notion that we should only mark strings for translations in apps that are intended to be translated as a whole. Random translated Show/Hide strings on English pages don't align with the research results we've seen.

Probably, if we want to provide our own translations for language namesNot now, since per ongoing discussion in internal#122 we don't actually need the ability to translate the language names

I'm still not sure about this, and the Django examples do show using ('de', _('German')) in LANGUAGES. I'm inclined to leave it, and leave them untranslated for this PR until we figure that out.

It's very odd, the PR browse view only shows one file removed:

But I can confirm that the file is gone when browsing the branch, and locally. So I rescind that comment.


Impact of "IBM Cloud Container Registry is Deprecating Container Builds"

We need to verify the impact of "IBM Cloud Container Registry is Deprecating Container Builds".
This could have impact for our bash scripts and other automations we made for the workshops.
https://www.ibm.com/cloud/blog/announcements/ibm-cloud-container-registry-deprecating-container-builds?_ga=2.151918137.1436322187.1603873424-1354875151.1603726778

ibmcloud cr build  is used in these scripts:

iks-scripts/deploy-articles-java-jee.sh
iks-scripts/deploy-authors-nodejs.sh
iks-scripts/deploy-web-api-java-jee-v2.sh
iks-scripts/deploy-web-api-java-jee.sh
iks-scripts/deploy-web-app-vuejs.sh
reactive/iks-scripts/deploy-articles-reactive-postgres.sh
reactive/iks-scripts/deploy-authors.sh
reactive/iks-scripts/deploy-web-api-reactive.sh
reactive/iks-scripts/deploy-web-app-reactive.sh

and also referenced in the documentation here:

authors-java-jee/README.md
workshop/02-container.md
workshop/06-java-development.md
workshop-one-service/4-kubernetes.md

Seems like we need to replace it with local docker build, docker tag, and docker push. This in turn requires local installation of Docker.

@Harald-U Thanks for the list. Let's see how to convert the existing commands and scripts in the workshops.

@thomassuedbroecker I have updated the deploy scripts in iks-scripts, tested, works. Next I'll do the reactive scripts :-)
Local Docker is a requirement anyways, ic cr build requires local docker installed.

There are scripts for reactive but the instructions (https://github.com/IBM/cloud-native-starter/blob/master/reactive/README.md#reactive-java-microservices) point to a toolchain: "Server-side Setup in IBM Cloud Kubernetes Service"(https://github.com/nheidloff/cloud-native-starter-reactive-toolchain).
The toolchain definition will probably need rework once the deployment method for IKS changes. I wouldn't modify the scripts in reactive/iks-scripts, I would rather remove them. Your decision :-D

@Harald-U Thanks for your help :-)


[spookyswap] Update SpookySwap strategy to include xBOO

Updated strategy to add additional token and staking pools

I see an active proposal on spookyswap.eth which is using this strategy, you sure these changes won't affect that?

We are willing to affect the current active proposal with these changes. The bigger importance for us is to include votes that are currently not counted, but should be.


Connecting to MySQL database using faivorite tool

Issue Type

Bug Report / Support Request

Your Environment

Got errors on some ... as you see. But my Drupal VM is working fine
C:\drupalsites\drupalvm\drupal-onset3-project\drupal-vm>vagrant --version
Vagrant 1.9.7
C:\drupalsites\drupalvm\drupal-onset3-project\drupal-vm>echo "VirtualBox `vboxmanage --version`"
"VirtualBox `vboxmanage --version`"
C:\drupalsites\drupalvm\drupal-onset3-project\drupal-vm>ansible --version
'ansible' is not recognized as an internal or external command,
operable program or batch file.

Your OS

Windows (version)

Full console output
Summary
Want to use my faivorite SQL tool runing from my Windows client. Have problem getting connected with ssh in the first place. Can access the site with Git Bash fine using:
ssh<EMAIL_ADDRESS>-i C:/Users/Matthias/.vagrant.d/insecure_private_key -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PasswordAuthentication=no -o IdentitiesOnly=yes
Got the info how to do this from here:
http://www.hashbangcode.com/blog/connecting-vagrant-box-without-vagrant-ssh-command
But in DbVisualizer or DBeaver the ssh setup settings do not allow these details. Experimentet with different setups. It may comes down to that it needs a Passphrase for the ssh key which is in .vagrant.d\insecure_private_key. So it can contact the ssh server with my IP and port 2222. But it fails to connect.
I saw the info how to connect with the mac tool Sequel Pro.
http://docs.drupalvm.com/en/3.5.2/extras/mysql/
But this does not work for me on Windows. And I wonder why this does not require an entry for the SSH passphrase. Leaving it empty did not help me.
P.S. This is a niche to have as the URL to the adminer SQL works just fine.

It may comes down to that it needs a Passphrase for the ssh key which is in .vagrant.d\insecure_private_key.

On Windows, I think I've seen MySQL Workbench primarily used as a GUI to the database, though many just use Adminer instead.
If DBVisualizer or DBeaver don't allow an SSH key to be selected (there's no password on the insecure_private_key key), then I don't think you'd be able to connect using them. You have to be able to set a hostname, username (vagrant) and SSH key, then have it tunnel through that connection to the MySQL host.
Are you able to use these directions to connect?
http://confluence.dbvis.com/display/UG91/Using+an+SSH+Tunnel
If you leave the SSH Password blank, and select the insecure_private_key file for the 'Private Key File', I wonder if that would work.

You can also login using the user vagrant with the password vagrant.

DBVisualizer and DBeaver  allow to set hostname, username and SSH key. But for some reason they do not cooperate then :). As they also have the field for password, I will try using vagrant as the password. Thanks for your advice.

@matjes63 for reference you can also use the insecure_private_key as the SSH key which is found in ~/.vagrant.d/insecure_private_key

If you wanted to do this, you could open up port 3306 in config.yml and change the given user in mysql's mysql database to come from any host.
There are some security problems which might result from this, but it does work.
$ curl http://<IP_ADDRESS>:3306
curl: (56) Recv failure: Connection reset by peer
a+jH4bL mysql_native_password��Got packets out of order

I still could not get DBVisualizer to work. But I got dbeaver working.
After upgrading dbeaver to 4.2.5 I was able to connect with it. It was important to use port 22 and not the default it had 2222. Beside that I was just using:
Connections setting:
server host: localhost
port: 3306
database: drupal
user name: drupal
password: drupal
Network settings:
Host/Ip: IP of my vagrant instance
port: 22
user name: vagrant
Auth. method: Public key
Private key: C:\user\myusername .vagrant.d\insecure_private_key
Passphrase: I left this blank
Thanks to all of you.

Could you also close the issue as it's solved, no reason to make Jeff to close it.
Thought did you see this: http://confluence.dbvis.com/display/UG91/Using+an+SSH+Tunnel
There is a way to connect with DBvis through a ssh tunnel according to that documentation.

Yes I saw this:
Thought did you see this: http://confluence.dbvis.com/display/UG91/Using+an+SSH+Tunnel
But could not get it to work. Then tried Dbeaver and got that working.
Will colse this now, as I switched to Dbeaver.

Just want to leave a note for people to double check their ssh user/password by visiting <IP_ADDRESS> from your browser. I'd forgotten that my project reqs had required these be changed, so drupal/drupal weren't working, but the creds reflected on <IP_ADDRESS> worked perfectly.