Error on Jar generation app-service

When The build is generating from gradle of app-service it doesn't create the folder libs into this
app-service/build/libs
The possible solution is replace the task jar for the next:
task explodedJar(type: Copy) {
with jar
into "${buildDir}/exploded"
}
For more details contact me:
My corporate email --><EMAIL_ADDRESS>

Hi Victor,
You are ok, in the next version will be fixed.
Regards.


Add Documentation for Setting Up the Project for Contributors

To enhance the onboarding experience for new contributors, we need to add comprehensive documentation that guides them through setting up the project locally.
This documentation should cover all necessary steps, from cloning the repository to running the project and executing tests.

should be fixed by #213, happy to accept a PR to improve that page if you think something is missing.


Containerized agents immediately self terminate on signal from cluster

Agent Version and Platform
Version of your agent? latest
OS of the machine running the agent? Linux Container on AKS
Azure DevOps Type and Version
dev.azure.com (formerly visualstudio.com)
What's not working?
We have built the agents container according to https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/docker?view=azure-devops
We then bundled a number of this in an AKS kubernetes statefulset that has a “terminationGracePeriodSeconds: 900”.
Now agents handle on their own agent updates but we’re facing issue when updating the container’s images (e.g.: on new builds of the image).
In that case we reset the image of the manifest specs causing a redeployment of the pods (ordered by the statefulset).
When we do that, Kubernetes signals the pod the impending shutdown and our expectations where that the pods would try finish the current job up to the above terminationGracePeriodSeconds but, instead, we can see that the agent software receives the Kubernetes signal and immediately truncates the current job and self terminates.
What are we missing in order for the agents to try to complete the running jobs before self-terminating?

I'm investigating running agents on AKS as well and have been thinking about how to handle this - I'm planning to run the agents with run-once mode, but still want to ensure they don't get terminated mid job (due to cluster upgrade or similar). Is there any way to query the agent to find out if it is currently running a job? Then something like a pre-stop hook could be used to block termination until the job completes

@casey-robertson I could have sworn there was another issue more related to the behavior you're describing, but now I can't find it. What can a container/process do to indicate to Kubernetes that it's shutting down on purpose, not due to failure?

We are facing this same exact issue. We would like to use the run-once mode but for jobs execute in super fast fashion, Kubernetes treats these pods as "crashing" and starts doing exponential crash loop backoff.

We are facing this same exact issue. We would like to use the run-once mode but for jobs execute in super fast fashion, Kubernetes treats these pods as "crashing" and starts doing exponential crash loop backoff.

Did you by any chance find a solution to this? I am facing the same issue too.

We are having some of our own issues running agents in Kubernetes (EKS in our case). We are using the RunOnce model. The problem is that Kubernetes sees these a broken pods because they are shutting down when the job finishes. If it does this over "x" threshold, Kubernetes puts the pod in a CrashLoopBackoff state and doesn't reschedule it for 5 minutes. This is causing backups in our pipelines.

Did you by any chance find a solution to this? I am facing the same issue too.

I have the exact same issue. Would love to find a workaround or a fix for this.


feature: Support a flag that tells Meltano whether to merge or overwrite state at the end of a run

Feature scope
CLI (options, error messages, logging, etc.)
Description
Spec

A new CLI option to meltano run: --merge-state.

Under the hood

Add merge_state attribute to ELBContext

https://github.com/meltano/meltano/blob/d9a9809614c18e31029eb7acb272e0578a101842/src/meltano/core/block/extract_load.py#L69-L78

Add the same attribute to ELTContext to satisfy the interface.
Modify the SingerTarget plugin class to check for the merge_state attribute to decide whether to treat state as partial.

https://github.com/meltano/meltano/blob/d9a9809614c18e31029eb7acb272e0578a101842/src/meltano/core/plugin/singer/target.py#L165-L166

Worth noting that SDK-based taps default to merging input with resulting state, so I think this is only needed for other taps.

@edgarrmondragon Can I Pick it Up ?

@arorarohan981 Yes! Do take your time to go through the codebase to understand the scope so you can add tests and docs.


irmin: allow to keep tree caches after a commit

Expose the clear flag threaded through to Tree.export.
With this, usingS.set_tree_exn ~clear:fase in https://gitlab.com/tezos/tezos/-/merge_requests/8169 seems to fix the issue.
It's also unclear what the default should be - There's an explicit Tree.clear for those who really want to clear the caches, so maybe by default, we should have clear=false?

Codecov Report

Merging #2225 (d6644ee) into main (8eeffae) will decrease coverage by 0.01%.
The diff coverage is 66.66%.

:exclamation: Current head d6644ee differs from pull request most recent head 9d04fc6. Consider uploading reports for the commit 9d04fc6 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #2225      +/-   ##
==========================================
- Coverage   68.09%   68.09%   -0.01%
==========================================
  Files         135      135
  Lines       16480    16484       +4
==========================================
+ Hits        11222    11224       +2
- Misses       5258     5260       +2

Impacted Files
Coverage Δ

src/irmin/store.ml
66.23% <65.71%> (+<0.01%)
:arrow_up:

src/irmin/tree.ml
81.07% <100.00%> (-0.21%)
:arrow_down:

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I've added some documentation and tests. It needs #2227 to be able to compare repository configurations in a finer grain as before (as previously we would always cleanup these fields after an export)


Allow precise configuration of raw request body

The following body represents a chunk in a Transfer-Encoding: chunked request (content length, content, remaining chunks):
data: |
  7
  foo=bar
  0

While the contents of the lines is readable, the line breaks are not, but are relevant to the request, as the specification requires each line to be terminated with \r\n. In this particular context it is also not possible to properly encode the line breaks.
One idea to get around this limitation is to provide a "line specification", like so:
raw_lines:
  - content: 7
    ending: "\r\n"
  - content: "foo=bar"
    ending: "\r\n"
  - content: 0
    ending: "\r\n"

This format would give us more control and better readability, in addition to sending malformed request bodies.

We have encoded_request, that's good enough for now.


(BUG) The blurred background

The bugs related to the blurred background  are united to this main issue:
(BUG) Background of pop-up is displayed and blocked further action on the dashboard after swiping green cards #1765
(BUG) The blurred background is stayed on the screen after using the "back" system button #1971

I could reproduce 1765 only on android devices/emulator. The functionality related to the blurred background works fine. I think it is a rendering issue, likely in src/components/dashboard/FeedModalList.js ->
// When target offset changes (by the prev useEffect) scrollToOffset
  useEffect(() => {
    if (offset === undefined) {
      return
    }

    // If offset is 0 we don't need to scroll, just set to false
    if (offset <= 0) {
      setLoading(false)
    } else {
      // Fire scrollToOffset within a delay to ensure the action is executed.
      // https://stackoverflow.com/questions/40200660/react-native-scrollto-with-interactionmanager-not-working
      setTimeout(() => {
        flatListRef && flatListRef.current && flatListRef.current.scrollToOffset({ animated: false, offset })
      }, 0)
    }
  }, [offset, flatListRef])

@sirpy @mauriguz issue isn't reproduced anymore
Checked on  QA 1.6.1-2
LG V30+ // Android 8.0 // Google Chrome 86.0.4240.75


Add lib/domains/il/org , Hayovel school Israel

https://www.hayovel.org.il/

@pallemry hayovel.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


Menu Bar adds to window content height causing scrollbar

Using menubar adds extra space to window contents height causing the vertical scrollbar to appear, even if the window content is small and no scrollbar would be shown normally. I tried to play with margin-top, margin-bottom etc., but couldn't correct this.

From the partly visible application bar I assume you're running it on a Mac, are you? I didn't test this target as of yet simply because this library aims at Windows & Linux.
I know how to fix it though.

From the partly visible application bar I assume you're running it on a Mac, are you? I didn't test this target as of yet simply because this library aims at Windows & Linux. I know how to fix it though.

No. it's Linux with some WM theme from https://www.xfce-look.org/browse?cat=138&ord=rating
Thank you very much!
I like NeutralinoJS, and a nice looking MenuBar is very useful to have.


Add Levenberg-Marquardt algorithm as a optimizer for keras.

Hi！please add Levenberg-Marquardt algorithm as a optimizer for keras. This algorithm is great useful for some problems.

@Fly-Playgroud
Can you please elaborate about your feature and please specify the use cases for this feature. Thanks!

Here is an example of an implementation of levenberg-Marquardt algorithm in Keras. Lots of useful applications.
https://github.com/fabiodimarco/tf-levenberg-marquardt
See also results here. Very helpful for PINNs
https://arxiv.org/abs/2205.07430

@JohnTaylor2000 Thanks for your reply, I just skimmed the article and I think it's really well written and quite helpful.
Only I didn't find the code for this side of the article, it would have been nice to have it.I found this project(https://github.com/fabiodimarco/tf-levenberg-marquardt) a long time ago, I tried to use it and did not feel very comfortable.

Hi,
This was the code that I have been using. You can also find an implementation in scipy:-
https://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.least_squares.html method=’lm’
Best wishes,
John
From: BUG|Fly @.>
Date: Monday, 23 May 2022 at 7:36 pm
To: keras-team/keras @.>
Cc: Taylor, John (Data61, Black Mountain) @.>, Mention @.>
Subject: Re: [keras-team/keras] Add Levenberg-Marquardt algorithm as a optimizer for keras. (Issue #16498)
@JohnTaylor2000https://github.com/JohnTaylor2000 Thanks for your reply, I just skimmed the article and I think it's really well written and quite helpful.
Only I didn't find the code for this side of the article, it would have been nice to have it.I found this project(https://github.com/fabiodimarco/tf-levenberg-marquardt) a long time ago, I tried to use it and did not feel very comfortable.
—
Reply to this email directly, view it on GitHubhttps://github.com/keras-team/keras/issues/16498#issuecomment-1134429794, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADZKLP2LJHEYAA4LSL5U2P3VLNGRRANCNFSM5VFKU34A.
You are receiving this because you were mentioned.Message ID: @.***>


Implement /ext in Steve

Context
Parent issue: https://github.com/rancher/rancher/issues/47010
As part of the Imperative API, we want a new API endpoint in Steve that will be accessible by users. The endpoint needs to be compatible with extension API servers, as described in the RFC.
Summary
We want a http.Handler that serves the following routes:

/openapi/v2 (OpenAPI V2)
/openapi/v3 (OpenAPI V3)
/openapi/v3/* (OpenAPI V3)
/apis/* (Discovery API + resources API)

All these APIs have well-defined inputs/outputs/etc. See the Imperative API RFC for details.
There are a few ways we can achieve what we want:

Making everything custom: This is how we did it in the POC
Same as 1 but the k8s.io/apiserver/pkg/endpoints/handlers package to implement the resources API
Use the GenericAPIServer abstraction from k8s.io/apiserver.

We shouldn't go full custom (1) because we risk not being fully compatible with all clients out there. (eg: Have to implement our own logic for finalizers, logic for webhooks, content type negotiation, object conversion to Table or PartialObjectMetadata, PATCH handling, etc).
So it's between (2) and (3). (3) seems very opinionated with its storage interface, so we need to check if we're able to have our own "store" abstraction described in the RFC). There's a neat sample-apiserver project from upstream k8s that shows how to use (3).
As far as requirements goes, we'd like to:

be able to configure the OpenAPI schemas with the ones we generated from https://github.com/rancher/rancher/issues/47007. Note that the POC and the sample-apiserver project also does this, so you can inspire yourself there.
have the OpenAPI paths auto-generated. This is done by the POC, the GenericAPI approach (3) also does this for us.
be able to serve custom resources. (Should be able to add new groups (eg: ext.cattle.io), new version for that group (eg: v1) and resources inside that group (eg: tokens, kubeconfigs, etc). Here's how they do it for GenericAPIServer: https://github.com/kubernetes/apiserver/blob/d97582edf43f2c2871edcb93b83fce39b68565b2/pkg/server/genericapiserver.go#L826.
be able to handle authentication in different ways ( through /ext endpoint, auth needs to be done by rancher using rancher tokens, through the extension API server, auth needs to be done using TLS certificates (same as in the POC))
be able to authorize the user
Have some sort of Store interface that developers will be able to implement for their types (see the RFC or the POC)

We'll probably end up with something like the following:
type ExtensionAPIServer struct {
  // unexported fields (eg: maybe apiserver.GenericAPIServer from k8s.io/apiserver?)
}

// Implements net/http.Handler
func (e *ExtensionAPIServer) ServeHTTP(w http.ResponseWriter, req *http.Request) {
}

// Allow adding api new group/version/resources
func (e *ExtensionAPIServer) InstallAPIGroup(apiGroup ..) {
}

// Or something, whatever, we just need a way to set the schema generated from wrangler
func (e *ExtensionAPIServer) SetOpenAPISpec(..) {
}

The end goal in Rancher (a few other GH issues), we'll be able to:

var apiServer *ExtensionAPIServer

// /ext endpoint => has its own authentication
mux.Prefix("/ext").Handle(apiServer)

// extension API server => has its own different authentication
http.ListenAndServe(..., apiServer)

PR merged, QA of this will happen in https://github.com/rancher/rancher/issues/47032. Closing.


add support oidc

Horacio completed work, documentation and links available here: https://docs.kivaprotocol.com/docs/oidc-adapter


styled() components do not accept marginY or marginX

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
styled() improperly parses marginX and marginY (compared to sx).
Example:
import { Divider, Paper, styled, Typography } from '@mui/material';

const SpacedDivider = styled(Divider)(({ theme }) => ({
  marginY: theme.spacing(1),
  marginX: theme.spacing(1), // added only to test how this parsed
}));

export const Component = () => {
    return (
    <Paper>
      <Typography>text</Typography>
      <Divider
        sx={(theme) => ({
          marginY: theme.spacing(1),
        })}
      />
      <Typography>text 2</Typography>
      <Divider
        sx={(theme) => ({
          marginX: theme.spacing(1),
        })}
      />
      <Typography>text 3</Typography>
      <SpacedDivider />
      <Typography>text 4</Typography>
    </Paper>
  );
};

results in the following CSS for the hr:
/* Divider with sx (theme) => { marginY: theme.spacing(1) } */
.css-1b008ma-MuiDivider-root {
	margin: 0;
	-webkit-flex-shrink: 0;
	-ms-flex-negative: 0;
	flex-shrink: 0;
	border-width: 0;
	border-style: solid;
	border-color: rgba(0, 0, 0, 0.12);
	border-bottom-width: thin;
	margin-top: 8px;
	margin-bottom: 8px;
}

/* Divider with sx (theme) => { marginX: theme.spacing(1) } */
.css-14qwiik-MuiDivider-root {
	margin: 0;
	-webkit-flex-shrink: 0;
	-ms-flex-negative: 0;
	flex-shrink: 0;
	border-width: 0;
	border-style: solid;
	border-color: rgba(0, 0, 0, 0.12);
	border-bottom-width: thin;
	margin-left: 8px;
	margin-right: 8px;
}

/* styled(Divider) with ({ theme }) => { marginY: theme.spacing(1), marginX: theme.spacing(1) } */
.css-qk8zwa-MuiDivider-root {
	margin: 0;
	-webkit-flex-shrink: 0;
	-ms-flex-negative: 0;
	flex-shrink: 0;
	border-width: 0;
	border-style: solid;
	border-color: rgba(0, 0, 0, 0.12);
	border-bottom-width: thin;
	margin-x: 8px;
	margin-y: 8px;
}

Expected behavior 🤔
The CSS for the styled component should match that of the component styled with sx
Steps to reproduce 🕹
Steps:

use styled() to style a MUI component

Context 🔦
I'd like to make a styled divider that adds some margin-top and margin-bottom using the marginY prop for reusability.
For now, I can simply add the marginTop and marginBottom props
Your environment 🌎

npx @mui/envinfo
  Don't forget to mention which browser you used. Firefox 102.0 (64-bit)
  Output from `npx @mui/envinfo` goes here.
System:
    OS: Windows 10 10.0.19044
  Binaries:
    Node: 17.4.0 - E:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 8.13.1 - E:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1266.0), Chromium (103.0.1264.44)
  npmPackages:
    @emotion/react: ^11.9.3 => 11.9.3
    @emotion/styled: ^11.9.3 => 11.9.3
    @mui/icons-material: ^5.8.4 => 5.8.4
    @mui/material: ^5.8.6 => 5.8.6
    @types/react: ^18.0.14 => 18.0.14
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^4.7.4 => 4.7.4

You have to use mx or my. px or py is also an options
import { Divider, Paper, styled, Typography } from '@mui/material';

const SpacedDivider = styled(Divider)(({ theme }) => ({
  my: theme.spacing(1),
  mx: theme.spacing(1), // added only to test how this parsed
}));

export const Component = () => {
    return (
    <Paper>
      <Typography>text</Typography>
      <Divider
        sx={(theme) => ({
          my: theme.spacing(1),
        })}
      />
      <Typography>text 2</Typography>
      <Divider
        sx={(theme) => ({
          mx: theme.spacing(1),
        })}
      />
      <Typography>text 3</Typography>
      <SpacedDivider />
      <Typography>text 4</Typography>
    </Paper>
  );
};

@socramm9 @cbprosser By default, the styled API does not know how to parse shorthand syntax.
import { Divider, Paper, styled, Typography } from '@mui/material';

const SpacedDivider = styled(Divider)(({ theme }) => ({
  // ...the styles here should be valid CSS
  // that's why `marginY`, `marginX` does not work.
}));

If you want to use the shorthand syntax inside the styled API, you have to use experimental_sx utility:
import { Divider, Paper, styled, Typography, experimental_sx as sx } from '@mui/material';

const SpacedDivider = styled(Divider)(sx({
  my: 1, // equals theme.spacing(1)
  mx: 1, // equals theme.spacing(1)
}));

// or
const SpacedDivider2 = styled(Divider)(({ theme }) => [
  { ...styles },
  sx({
    my: theme.spacing(1),
    mx: theme.spacing(1),
  })
]);

Sorry to comment on a closed issue, but this came up in my search for an answer. I believe others with the current version of react will land here with the same problem, which is likely just not knowing the options for theme.spacing with multiple parameters.
I searched for mx and my support so I can adjust the x and y margins as I would normally with SX but it is not needed:
const SpacedDivider = styled(Divider)(({ theme }) => ({
    margin: theme.spacing(1 2, 1, 2)
}));

Even shorter.  Parameter ordering is Top, Right, Bottom, Left.


Unify ndt5 and ndt7 result schema

This change modifies the data.NDTResult struct used to serialize the test summary data for both the ndt5 and ndt7 protocols. Previously, ndt7 logs were JSONL -- now the results are a single data.NDTResult serialized as JSON.
This change introduces two new fields to the NDTResult struct for ndt7 Upload and Download tests. To change how data is written (from line-based to whole-object based) the result.File interface is updated to allow incrementally "saving" test model.ArchivalData such as client metadata, client & server measurements, and other fields.
This change also consolidates the ndt5data.Metadata and client-provided Meta fields into a single control.ArchivalData structure corresponding to the ndt5 "control channel" connection. Now every top-level object in the NDTResult struct represents a connection to the NDT server and all metadata collected by that connection.
As well, client and server ports are recorded in the result data for both protocols.
As well, the struct field names are uniform throughout, preferring "UUID" globally and "ClientMetadata" for client-provided metadata.

This change is

Pull Request Test Coverage Report for Build 819

82 of 94 (87.23%)  changed or added relevant lines in 10 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.6%) to 73.797%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ndt7/saver/saver.go
4
6
66.67%

ndt7/results/file.go
18
21
85.71%

ndt7/upload/upload.go
6
9
66.67%

ndt7/handler/handler.go
22
26
84.62%

Files with Coverage Reduction
New Missed Lines
%

ndt7/saver/saver.go
1
82.98%

Totals

Change from base Build 799:
0.6%

Covered Lines:
1442

Relevant Lines:
1954

💛  - Coveralls

Part of https://github.com/m-lab/ndt-server/issues/139


Adding a new difficulty page is outdated

What needs to be documented?


Nestings greater than 3 get smoshed on reloading if numbering is greater than 10

Environment

Elixir & Erlang/OTP versions (elixir --version):
Operating system: Linux
How have you started Livebook (mix phx.server, livebook CLI, Docker, etc):  livebook CLI
Livebook version (use git rev-parse HEAD if running with mix):

Erlang/OTP 26 [erts-14.2] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit:ns]

Elixir 1.15.5 (compiled with Erlang/OTP 26)

Livebook 0.12.1

Browsers that reproduce this bug (the more the merrier): Firefox
Include what is logged in the browser console:
Include what is logged to the server console:

Current behavior
I have the following livemd index header. I auto-generate an index for all my pages, so they can link to each other easily.
## Index
1. [Toc](./toc.livemd)
2. [User](./user.livemd)
   1. [Data](./user/data.livemd)
3. [Contributing](./contributing.livemd)
   1. [Understanding Any Module](./contributing/understanding-any-module.livemd)
   2. [Writing Documents](./contributing/writing-documents.livemd)
   3. [Examples Over Testing](./contributing/examples-over-testing.livemd)
   4. [Examples](./contributing/examples.livemd)
   5. [Git](./contributing/git.livemd)
   6. [Hoon](./contributing/hoon.livemd)
   7. [Iex](./contributing/iex.livemd)
   8. [Mnesia Vs Actor State](./contributing/mnesia-vs-actor-state.livemd)
   9. [Observer](./contributing/observer.livemd)
   10. [Testing](./contributing/testing.livemd)
       1. [Running Tests](./contributing/testing/running-tests.livemd)
       2. [Writing Tests](./contributing/testing/writing-tests.livemd)
4. ...

This works great except when I open up the document in which it serializes to:
## Index

1. [Toc](./toc.livemd)
2. [User](./user.livemd)
   1. [Data](./user/data.livemd)
3. [Contributing](./contributing.livemd)
   1. [Understanding Any Module](./contributing/understanding-any-module.livemd)
   2. [Writing Documents](./contributing/writing-documents.livemd)
   3. [Examples Over Testing](./contributing/examples-over-testing.livemd)
   4. [Examples](./contributing/examples.livemd)
   5. [Git](./contributing/git.livemd)
   6. [Hoon](./contributing/hoon.livemd)
   7. [Iex](./contributing/iex.livemd)
   8. [Mnesia Vs Actor State](./contributing/mnesia-vs-actor-state.livemd)
   9. [Observer](./contributing/observer.livemd)
   10. [Testing](./contributing/testing.livemd)
   11. [Running Tests](./contributing/testing/running-tests.livemd)
   12. [Writing Tests](./contributing/testing/writing-tests.livemd)
4. [Visualization](./visualization.livemd)

Now if I edit the file by hand in the livebook editor (in firefox), to make it indent again, it saves the following to disk
## Index
1. [Toc](./../toc.livemd)
2. [User](./../user.livemd)
   1. [Data](./../user/data.livemd)
3. [Contributing](./../contributing.livemd)
   1. [Understanding Any Module](./../contributing/understanding-any-module.livemd)
   2. [Writing Documents](./../contributing/writing-documents.livemd)
   3. [Examples Over Testing](./../contributing/examples-over-testing.livemd)
   4. [Examples](./../contributing/examples.livemd)
   5. [Git](./../contributing/git.livemd)
   6. [Hoon](./../contributing/hoon.livemd)
   7. [Iex](./../contributing/iex.livemd)
   8. [Mnesia Vs Actor State](./../contributing/mnesia-vs-actor-state.livemd)
   9. [Observer](./../contributing/observer.livemd)
   10. [Testing](./../contributing/testing.livemd)
       1. [Running Tests](./../contributing/testing/running-tests.livemd)
       2. [Writing Tests](./../contributing/testing/writing-tests.livemd)
4. [Visualization](./../visualization.livemd)

However, if I close the page and reopen it, we get the following saved to disk again:
1. [Toc](./toc.livemd)
2. [User](./user.livemd)
   1. [Data](./user/data.livemd)
3. [Contributing](./contributing.livemd)
   1. [Understanding Any Module](./contributing/understanding-any-module.livemd)
   2. [Writing Documents](./contributing/writing-documents.livemd)
   3. [Examples Over Testing](./contributing/examples-over-testing.livemd)
   4. [Examples](./contributing/examples.livemd)
   5. [Git](./contributing/git.livemd)
   6. [Hoon](./contributing/hoon.livemd)
   7. [Iex](./contributing/iex.livemd)
   8. [Mnesia Vs Actor State](./contributing/mnesia-vs-actor-state.livemd)
   9. [Observer](./contributing/observer.livemd)
   10. [Testing](./contributing/testing.livemd)
   11. [Running Tests](./contributing/testing/running-tests.livemd)
   12. [Writing Tests](./contributing/testing/writing-tests.livemd)
4. [Visualization](./visualization.livemd)

I believe this occurs because when livebook opens the file it normalizes the spacing and numbering, however since it normalizes the spacing, it only makes indent level 3 have 6 spacing instead of 7. And since 10. has 2 digits, it should have an indent of 7 if i
Expected behavior
To have sections nested past 10 to work properly.
This can either be done by normalizing any section indented within a number to have an extra space for each spacing (My logic generating the TOC does this now), or by having 2 spaces auto indent without caring about the section's previous level.

For the time being I can get around this in the project I work on, as I've made tooling that lets me control where articles are placed in the TOC if I so desire. And since only a few pages in that section have sub documents, it's workable.

@mariari thanks for the report, fixed on main :)


Progress bar look for each block

Jake, thank you for a great library. I extended it slightly to show a funnel where each block looks like a bar chart. Would you be interested in merging adding this feature to d3-funnel? If so, I could tidy up the source code, add a few tests and submit a pull-request.
example
source code

Sure. Just make sure that the previous tests also succeed (I see you skipped the test for gradients, probably due to the edit at this line).

That really looks great, great contribution, looking forward to a PR!

Closed with 4935052.


logging: support runtime packaging without format strings in mem

This adds support for runtime packaging with tagged arguments so that cbprintf_package() can function without the format strings in memory. This allows the format strings to be removed from final binary to converse space.

@nordic-krch here is my attempt to do runtime packaging without format strings in memory. In current form, this is guarded behind kconfig so the old path is still the default (as not to disrupt anyone). CONFIG_LOG_PRINTK is not supported at the moment as it would require some more macro work. I will work on supporting printk() if this is an acceptable way to go forward.

@dcpleung I started to think that it can actually be done much simpler as part of static packaging. What we need is to add runtime string length to package length when macro is called with NULL pointer and when macro is called with a buffer we can create an array with indexes where string arguments are located and then call a function that takes created package and array of those indexes and do the copying into the package.
Pieces of this is already done since there is an option to collect indexes of strings and attach it to the package (added by #37133):
https://github.com/zephyrproject-rtos/zephyr/blob/22c0843485b5d03a8bf1de8499fe1d20d2ded3d3/include/sys/cbprintf_internal.h#L276
As the outcome we could use static method in all cases. That would speed up a lot. Runtime packaging would be used when features are not supported or to reduce stack usage in no optimization case.

@dcpleung fyi, keep working on the proposal. Will publish something tomorrow.

@dcpleung fyi, keep working on the proposal. Will publish something tomorrow.

That's great. Thank you. :)

Took more time but draft PR is out: #43150


Bundler/builder service

With a list of components and URLs, we could later build a frontend to bundle together selected components.
Bootstrap Customizer
jQuery UI Builder

:+1:


[helm-docs] Use helm docs for all charts [WIP] [ci-skip]

Description of the change

Use helm-docs and templates for charts READMEs.
Benefits

Less boiler-plate for charts and ensure changelog and value descriptions are updated.
Possible drawbacks

Applicable issues

NA

Additional information

Checklist

[ ] Chart version bumped in Chart.yaml according to semver.
[ ] Title of the PR starts with chart name (e.g. [home-assistant])
[ ] (optional) Chart is using our common library as a dependency.
[ ] (optional) Variables are documented in the README.md

There are 8 charts I did not migrate yet since they require more time to move the value comments from the readme into the value.yaml.
I will do those in a separate PR next weekend if nobody do them before

ok, big change done - let us see how many charts require an extra bump...
If you have the time please do the PR for the remaining 8. If do not think I will have the time prior to the weekend


TST: avoid/reduce unimportant warnings in tests

It looks like some changes got mixed up with PR #361. Cleaned up.

Thanks!


Fetcher DAG development

This is a PR representing the work @barbarahui and I did in writing a first fetcher DAG. Since writing to s3 is not fully supported by the codebase, this work is coordinated with some updates to ucldc/aws-mwaa-local-runner described here: https://github.com/ucldc/aws-mwaa-local-runner/pull/3 and is built on top of the DATA_DEST environment variable work here: https://github.com/ucldc/rikolti/pull/495
This PR, in contrast to the DATA_DEST environment variable work, is exclusively DAG-specific work.

dags/operate_sample_dag.py is a DAG written using the classic airflow PythonOperator.
dags/taskflow_sample_dag.py is a DAG written using the airflow taskflow model. This file also includes a variety of small tasks demonstrating specific, but relevant airflow features.
dags/fetcher_dag.py is a functional fetcher DAG.

In order to run the fetcher DAG, you must have:

Pulled the ucldc/aws-mwaa-local-runner:dags-development branch
Modified the aws-mwaa-local-runner/docker/.env file:

# aws-mwaa-local-runner/docker/.env
DAGS_HOME="<path to this repository>/rikolti"
PLUGINS_HOME="<path to this repository>/rikolti/plugins"
REQS_HOME="<path to this repository>/rikolti/dags"
STARTUP_HOME="<path to this repository>/rikolti/dags"
RIKOLTI_DATA_HOME="<path to where you would like the fetcher to write data>"

Run ./mwaa-local-env build-image
Write a startup.sh file in the dags folder:

# startup.sh
FETCHER_DATA_DEST=file:///usr/local/airflow/rikolti_data
MAPPER_DATA_DEST=file:///usr/local/airflow/rikolti_data
MAPPER_DATA_SRC=file:///usr/local/airflow/rikolti_data

Run ./mwaa-local-env start

startup.sh needs to look like this:
# startup.sh
export FETCHER_DATA_DEST='file:///usr/local/airflow/rikolti_data'
export MAPPER_DATA_DEST='file:///usr/local/airflow/rikolti_data'
export MAPPER_DATA_SRC='file:///usr/local/airflow/rikolti_data'


iOS SDK voice recognition not recognizing returning desired result

Using iOS SDK voice recognition is not working properly. For Android it's working properly. Also whenever I speak using iOS SDK all requests are visible as Sub-Log of main Log. Is that a issue or do I need to set some parameter in the iOS sdk provided?

Hi, do your have some error? You use demo application or not?

Nope. There is no error. It's not recognizing properly. I am speaking same sentence simultaneous on my android and iOS app. Android app is doing very good while iOS app is not recognizing. I can share my client access token if required. I am using api.ai with email id<EMAIL_ADDRESS>I can see in api.ai log that my recognized sentenced is totally wrong.

Maybe... You can show Your code? Android SDK using google speech recognizer, but in iOS using our ASR... it differed

Or just low quality of the recognition?

Here it goes
-(instancetype)initWithView:(UIView*)view{
self.apiAI = [ApiAI sharedApiAI];
// Define API.AI configuration here.
id <AIConfiguration> configuration = [[AIDefaultConfiguration alloc] init];
configuration.baseURL = [NSURL URLWithString:@"https://api.api.ai/v1"];
configuration.clientAccessToken = @"XXXXX";
configuration.subscriptionKey = @"YYYY";
self.apiAI.configuration = configuration;
self.view = view;

return self;

}
-(UIView*)getRequestButtonView:(BOOL)showButton{
if (showButton) {
UIView *customView = [[UIView alloc] init];
[customView setFrame:CGRectMake(20, self.view.frame.size.height/4, self.view.frame.size.width - 40, self.view.frame.size.height/3 + 50)];
customView.layer.cornerRadius = 10;
UILabel *speakLabel = [[UILabel alloc] initWithFrame:CGRectMake(0, 15, customView.frame.size.width, 30)];
[speakLabel setTextAlignment:NSTextAlignmentCenter];
speakLabel.text = @"Speak";
[speakLabel setTextColor:[UIColor darkGrayColor]];
[customView addSubview:speakLabel];
[customView setBackgroundColor:[UIColor colorWithWhite:200.0/255 alpha:1.0]];
AIVoiceRequestButton *button = [[AIVoiceRequestButton alloc] init];
[button setSuccessCallback:^(id response) {
NSLog(@"Response: %@",[response description]);
}];
    [button setFailureCallback:^(NSError *error) {
        NSLog(@"Error: %@",[error description]);
    }];

    [customView addSubview:button];
    [self alignToCenter:button toView:customView];

    self.requestButton = button;
    return customView;
}
return nil;

}

You skip step "Init audio session.". If does not do it, then audio cannot be recorded.
see https://github.com/api-ai/api-ai-ios-sdk#integratingintoyourapp
That's right?

It has been done in AppDelegate.m
-(void)initAudioService{
   [[AVAudioSession sharedInstance] setCategory:AVAudioSessionCategoryPlayAndRecord error:nil];
   [[AVAudioSession sharedInstance] setActive:YES error:nil];
}

True, it is a low quality of recognition. Some simple text it's able to recognize.

Okey. I Cannot fix this problem now. We always working with quality of out ASR.


fashion mnist FPGA_accuracy is very low

Hi Erwei. I am trying to apply your project to mnist fashion dataset. armcpu_accuracy is high but FPGA_accuracy is very low.
First I trained the mnist fashion dataset on caffe with the same lenet model. After loading the weights to fpga and testing, I get the following results. where am i doing wrong.

The problem was due to the training parameters. Problem solved using sgd.


Refactor post list

On index.html
Instead of
{% for post in site.posts %}

    {% if forloop.index > site.post_num_index %}
    {% continue %}

It would be more Jekyll convention to use limit instead .
{% assign posts = site.posts | limit: site.post_num_index %}
{% for post in posts %}
...

Also better naming would be
site.max posts

By the way, continue skips the current iteration only so it has to skip a lot which is inefficient

1
2
3
4 skip
5 skip
...
99 skip
100 skip
stop

But if you break, it would stop iterating

1
2
3
stop

Thank you very much for your suggestion. This is indeed an obvious logical problem. I will fix this problem in the next submission.
By the way, I don’t know why
{% assign posts = site.posts | limit: site.post_num_index %}
{% for post in posts %}
...

not working.
I replaced it with the scheme below
{% for post in site.posts limit: site.max_posts %}
...

Oh sorry limit is not a filter like I thought, just a for loop modifier.
I checked this as a reference now https://learn.cloudcannon.com/jekyll-cheat-sheet/


[Sema] Better ambiguity diagnosis in overloaded function calls

Save unresolved argument number from callee candidate info, use it to diagnose ambiguity sooner and more specifically.

@swift-ci Please smoke test

🙏🙌


alerts are not visible

most modern browsers suppress alert() on page load, so critical messages do not even show up
for example, this is only visible in browsers console log as alert was suppressed by browser

The host is online, but the API seems to be disabled.

why not use a div element in top-right to show messages and get rid of all alerts?

OS and Version: Windows 11 with Chrome 108
GPU: RTX3060
Browser and Version: Chrome 108
Any browser extensions: N/A
Commit of openOutpaint-webUI-extension: 2fd0126454c7a836e41103311655f304772983fa (01/03/2023)
Commit of A1111 webUI: b7deea47eeb033052062621b0005d4321b53bff7 (01/04/2023)
How you interact with A1111 webUI: Local hardware

originally opened in https://github.com/zero01101/openOutpaint-webUI-extension/issues/17, but i think its better fitted here.

That is a thing I have considered since the beginning... Just continued ignoring the issue... I think it wouldn't be really hard. Will mark as good first issue for now.

bonus would be:

use the same div for dream/upscale/save/whatever messages
have it auto-clear on timer so last message is not stuck indefinitely

Hi, @vladmandic! I pushed some changed the other day that switch to a custom notification system for alerts. Confirmations were also migrated, but prompt() instances still not. Can you see it this seems to be an okay start?

@seijihariki i see the notification box in bottom left show up when i switch model, but its barely noticeable. still a good start.
btw, i don't see notifications if im using standard model instead of inpainiting one?

Notification should not have anything to do with the selected model, I think. I remember @zero01101 had done some changes to inpainting model detection, so he would probably know to answer that.
I will see what I can do so the notifications are more prominent.

yeah, the only notification that should have anything to do with the selected model would be the first-time-online check alerting you if your currently selected model isn't Inpainting and offering you an option to switch to a detected Inpainting model
that API endpoint I added for checking unet counts isn't actually used anywhere yet, it just kinda hangs out being pointless lol; it's actually pretty slow :(

Will be closing this issue for now... We can reopen it in the future.


Offline Access

Describe the bug
I was recently offline for a few days and had to pull my laptop out on day 3 to do some work. Quite quickly Ray had a pop up complaining that it couldn't verify my license and that the product was not active. Not only was I unable to use Ray (despite having an active license) but there was no way to close the pop up window which was forced on top of all my other windows. The only solution I had was to kill the Ray process directly to close it.
Versions
Ray version (you can see this in "About Ray"): 2.0.1
To Reproduce
Steps to reproduce the behavior:

Go offline for a couple of days
Use Ray
Run into a license pop up after

Expected behavior

As long as I have an active license I'd like to be able to continue to use Ray whether or not I have an internet connection. I travel somewhat frequently and it's not unusual for me to be offline for a few days and that shouldn't render my paid products un-usable.

You shouldn't have to kill the process to get Ray to close in this situation. I should be able to exit out of the license window and that should close Ray.

Screenshots
I didn't take any and I'm unable to re-create without being offline for a long period of time.
Desktop (please complete the following information):

OS: MacOS
Version: 12.5

same here, i need to go in a place that has no network connection, but ray suddenly issue when offline access


rubocop fixes

I was reading through the code because I'm planning production use.
Did some easy changes to make rubocop happier.

Hi there!  Thanks for the patch
What Rubocop settings did you use for this?

I'm running linter-rubocop in atom.
Opened the atom package's source and it uses default settings: https://github.com/AtomLinter/linter-rubocop/blob/master/index.coffee


Normalize errors and validate behavior

fixes #85

It contains two main updates:

validate now returns {valid, errors} object instead of throwing errors which was not a javascript approach
normalized throwing errors across the whole library. Now only DataPackageError could be raised (not error, array of errors or even array of strings as it was). If  there are multiple errors an interface is predictable now:

try {
  // some lib action
} catch (error) {
  console.log(error) // you have N cast errors (see error.errors)
  if (error.multiple) {
    for (const error of error.errors) {
        console.log(error) // cast error M is ...
    }
  }
}

@georgiana-b
could you please review? It's the same as https://github.com/frictionlessdata/tableschema-js/pull/87

Have it merge now but please take a look on merged if needed


Test coverage

Missing tests

Filterer: The new function, and archetype definition should be tested

Done with a96f73de0666a18a518cba281f93990be8ba8f76


Suspense #fallback not work in defineOptions preFetch in ssr mode

Vue version
3.4.21
Link to minimal reproduction
https://github.com/fengjac/ssr-suspense-demo
Steps to reproduce

$ pnpm i
$ pnpm run dev
click About nav in http://localhost:9100/

What is expected?
Show Loading... label (loading state) when I click About nav. And then after the API call done, show About page
What is actually happening?
No loading state when I click About nav
System Info
System:
    OS: Windows 10 10.0.19041
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
    Memory: 6.07 GB / 15.82 GB
  Binaries:
    Node: 20.12.1 - D:\nodejs\node.EXE
    Yarn: 1.22.22 - D:\nodejs\yarn.CMD
    npm: 10.5.0 - D:\nodejs\npm.CMD
    pnpm: 8.15.6 - D:\nodejs\pnpm.CMD
  Browsers:
    Chrome: 90.0.4430.212
    Edge: Spartan (44.19041.964.0), Chromium (123.0.2420.81)
    Internet Explorer: 11.0.19041.1
  npmPackages:
    vue: ^3.4.18 => 3.4.21

Any additional comments?
No response

preFetch is handled by the Quasar framework internally, it is not a part of Vue. It seems that components with preFetch are not converted to async components by Quasar and Suspense works only with async components or async setup function according to docs
You should use Quasar's loading state instead. Suspense works well in this scenario if we make the component async as stated in Vue docs, for instance, if we add await sleep(2000) in the AboutPage body we will see the loader for 2 seconds after the component has been fetched.
Probably, it is a feature request to Quasar's team to make their components with preFetch work with Suspense
Please, correct me if I am wrong this is an issue related to Vue and further investigation is required.

Thanks @quiteeasy for looking into it. Closing as it doesn't seem to be caused by Vue core.


Remote Update (everything-v10): donovandmc/everything

This pull request has been superseded by #324


Decide if refactor current code base or start things over

I'll adjust current PRs #145 and #155 to make it working.


Update PSPrivateGalleryPublishEnvironment.psd1

Fixed issue registering gallery on windows 2012r2

Hi @davidwallis3101, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

added firewall rule, then realised it was after the example of getting a module from the gallery which fails without the firewall rule

@davidwallis3101 - Thanks for the contribution. Looks good


Wrap (de)mangling namespaces in an inline namespace.

Since libDemangling is included in the Swift standard library,
ODR violations can occur on platforms that allow statically
linking stdlib if Swift code is linked with other compiler
libraries that also transitively pull in libDemangling, and if
the stdlib version and compiler version do not match exactly
(even down to commit drift between releases). This lets the
runtime conditionally segregate its copies of the libDemangling
symbols from those in the compiler using an inline namespace
without affecting usage throughout source.
cc: @compnerd

This probably should be rebased.

This is rebased on master now that #30732 is merged, and as we discussed offline, I pushed the inline namespace down into Demangle/Mangle/Punycode and just use compiler/runtime without the underscore for the name.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - f1f009cd7c4665f6d23c1eee1b117ea63d4b0b89

Build failed
Swift Test Linux Platform
Git Sha - f1f009cd7c4665f6d23c1eee1b117ea63d4b0b89

Just to verify the reason that the runtime aspect of this change is scattered is because of the custom CMake handling in the runtime preventing properly using CMake correct?

It's a combination of the add_swift_target_library macro splatting out the platform/arch cross product of targets and some of the other various runtime-affected targets (like the unit tests) touching the libDemangling headers in their own ways. Each one was discovered by attempting a build and then adding the define if I hit linker errors.
I imagine if there was a common "choke point" that all runtime targets depended on libDemangling through, we could reduce the cognitive overhead here, but I don't know CMake well enough to know the best way to compose that. If you have any ideas, I'd be happy to try to simplify it.

Hmm, Im not a fan of this, but, I think that it is safe to put that into add_swift_target_library.  That is guaranteed to only be used by targets that are designed to run on the target which is what the runtime is for.  I'd be okay with it being a follow up if its a big change.

FAILED: source/Core/CMakeFiles/lldbCore.dir/Mangled.cpp.obj
T:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\clang-cl.exe  /nologo -TP -DGTEST_HAS_RTTI=0 -DLLDB_CONFIGURATION_RELEASE -DUNICODE -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_ENABLE_EXTENDED_ALIGNED_STORAGE -D_HAS_EXCEPTIONS=0 -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -D_UNICODE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Isource\Core -IS:\jenkins\workspace\swift-PR-windows\lldb\source\Core -Isource -IS:\jenkins\workspace\swift-PR-windows\lldb\include -Iinclude -IS:\jenkins\workspace\swift-PR-windows\llvm\include -IT:\llvm\include -IS:\jenkins\workspace\swift-PR-windows\clang\include -IT:\llvm\tools\clang\include -IT:\swift\include -IS:\jenkins\workspace\swift-PR-windows\swift\include -IS:\jenkins\workspace\swift-PR-windows\lldb\source -I"C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\include" -IS:\jenkins\workspace\swift-PR-windows\lldb\tools\clang\include -I..\clang\include -IS:\jenkins\workspace\swift-PR-windows\lldb\source\. /GS- /Oy /Zc:inline /Zc:strictStrings /Oi /Zc:rvalueCast -Wno-deprecated-declarations -Wno-unknown-pragmas -Wno-strict-aliasing -Wno-deprecated-register -Wno-vla-extension /MD /O2 /Ob2   -UNDEBUG -wd4018 -wd4068 -wd4150 -wd4201 -wd4251 -wd4521 -wd4530  /EHs-c- /GR- -std:c++14 /showIncludes /Fosource\Core\CMakeFiles\lldbCore.dir\Mangled.cpp.obj /Fdsource\Core\CMakeFiles\lldbCore.dir\lldbCore.pdb -c S:\jenkins\workspace\swift-PR-windows\lldb\source\Core\Mangled.cpp
In file included from S:\jenkins\workspace\swift-PR-windows\lldb\source\Core\Mangled.cpp:28:
In file included from S:\jenkins\workspace\swift-PR-windows\lldb\include\lldb/Target/SwiftLanguageRuntime.h:23:
In file included from S:\jenkins\workspace\swift-PR-windows\lldb\source\Plugins/LanguageRuntime/ObjC/AppleObjCRuntime/AppleObjCRuntimeV2.h:16:
In file included from S:\jenkins\workspace\swift-PR-windows\lldb\source\Plugins/LanguageRuntime/ObjC/AppleObjCRuntime/AppleObjCRuntime.h:15:
In file included from S:\jenkins\workspace\swift-PR-windows\lldb\source\Plugins/LanguageRuntime/ObjC/AppleObjCRuntime/AppleThreadPlanStepThroughObjCTrampoline.h:14:
In file included from S:\jenkins\workspace\swift-PR-windows\lldb\include\lldb/Target/ThreadPlan.h:17:
In file included from S:\jenkins\workspace\swift-PR-windows\lldb\include\lldb/Target/Target.h:33:
S:\jenkins\workspace\swift-PR-windows\lldb\include\lldb/Symbol/SwiftASTContext.h(659,16): warning: 'CreateTupleType' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
  CompilerType CreateTupleType(const std::vector<TupleElement> &elements);
               ^
S:\jenkins\workspace\swift-PR-windows\lldb\include\lldb/Symbol/SwiftASTContext.h(122,3): note: overridden virtual function is here
  CreateTupleType(const std::vector<TupleElement> &elements) = 0;
  ^
S:\jenkins\workspace\swift-PR-windows\lldb\include\lldb/Symbol/SwiftASTContext.h(661,16): warning: 'GetErrorType' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
  CompilerType GetErrorType();
               ^
S:\jenkins\workspace\swift-PR-windows\lldb\include\lldb/Symbol/SwiftASTContext.h(111,24): note: overridden virtual function is here
  virtual CompilerType GetErrorType() = 0;
                       ^
In file included from S:\jenkins\workspace\swift-PR-windows\lldb\source\Core\Mangled.cpp:30:
In file included from S:\jenkins\workspace\swift-PR-windows\swift\include\swift/Demangling/Demangle.h:28:
S:\jenkins\workspace\swift-PR-windows\swift\include\swift/Demangling/NamespaceMacros.h(29,2): error: Libraries that depend on Demangling must set "SWIFT_INLINE_NAMESPACE"        to be a valid identifier.
#error Libraries that depend on Demangling must set "SWIFT_INLINE_NAMESPACE" \
 ^
In file included from S:\jenkins\workspace\swift-PR-windows\lldb\source\Core\Mangled.cpp:30:
S:\jenkins\workspace\swift-PR-windows\swift\include\swift/Demangling/Demangle.h(36,1): error: unknown type name 'SWIFT_BEGIN_INLINE_NAMESPACE'
SWIFT_BEGIN_INLINE_NAMESPACE
^
S:\jenkins\workspace\swift-PR-windows\swift\include\swift/Demangling/Demangle.h(620,1): error: unknown type name 'SWIFT_END_INLINE_NAMESPACE'
SWIFT_END_INLINE_NAMESPACE
^
S:\jenkins\workspace\swift-PR-windows\swift\include\swift/Demangling/Demangle.h(621,1): error: expected unqualified-id
} // end namespace Demangle
^
2 warnings and 4 errors generated.

It looks like lldb may be including Demangling without having the dependency declared, so it's not inheriting the compile definition. I'll verify and prep a PR for that.
For the other change, what do you think about just creating two separate swiftDemangling targets? swiftDemangling would remain as is, and we could also have swiftDemanglingRuntime that has the same sources but defines SWIFT_INLINE_NAMESPACE=runtime instead. Then as long as the targets declare the dependency on the correct target, they'll automatically get the correct definition. Do you see any problems with that approach?

I would say that is the correct approach ... if its not Swift :-(.  The separate library should be an OBJECT library that gets subsumed by swiftCore.  Sadly, this approach is currently not viable due to the way that the CMake for this project is setup.  But, you are approaching the problem precisely as it should be handled.  It would obviate a bunch of workarounds and difficulty in this.  Perhaps Im missing something (or Im not thinking of a clever workaround) but it seems that its going to be a bit more work to get that working.

Ok, I've pushed an update that pulls the compile definition up into _add_swift_target_library_single, which cut the number of files changed from 26 to 17. I also noticed that lib/SwiftRemoteMirror was using the wrong definition (it should have had a dependency to host swiftDemangling), so I added that.
The only place where the runtime namespace is repeated now is in the unit test targets that link to target Demangling. It's possible we might be able to conditionalize that somehow, but since the same add_swift_unittest macro is used for host and target tests, it seemed better as a follow-up.

@compnerd I've fixed up recent merge conflicts; now that the LLDB changes have been merged, can you kick off CI again please?

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 2ab34f2d5d6de601989df0a4730a531b27ef8a29

Build failed
Swift Test OS X Platform
Git Sha - 2ab34f2d5d6de601989df0a4730a531b27ef8a29

Now that lldb is forward-declaring symbols in swift::Demangling:: without including the header, adding the namespace for the compiler's (and thus lldb's) version of the symbols won't work cleanly. I've opened https://github.com/apple/llvm-project/pull/1295 to revert those changes and updated this PR to only add the inline namespace if the SWIFT_INLINE_NAMESPACE symbol is defined for the runtime. Otherwise, the macros do nothing.

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - f1018aee24e12bf624ce128c5d346537e01b8ff6

@swift-ci please clean test

Build failed
Swift Test OS X Platform
Git Sha - f1018aee24e12bf624ce128c5d346537e01b8ff6

@swift-ci please clean test

@swift-ci please clean test

@swift-ci please test Windows platform

@swift-ci please clean test macOS platform

Build failed
Swift Test OS X Platform
Git Sha - d8ac4d154c383eb36a58694b16a1266f28d38256

@swift-ci please clean test

Build failed
Swift Test Linux Platform
Git Sha - 3c42c4126c92ec4e1e046b4c1aaa645433a1ff3f

@swift-ci please test

@swift-ci please clean test

@swift-ci please test Windows platform

CC: @mikeash @slavapestov


Use faster-fifo for queues

Switches to the faster-fifo library to bring about massive performance improvements to the mock sim and to the pi, even in real time.
Also optimizes logger buffer logic a little bit.

[x] Get things working
[ ] Windows support?

Part of #85.

Tested this on the Pi extensively today. It works very well with no practical downsides. We no longer get any "spikes" in fetched packets. Actual queue size is also <2 when run in real time.

@JacksonElia how badly do you want Windows support? I think it's trivial to keep windows support but it might hurt readability just a little bit

probably at the top of the files that use the queues we have an if statement that checks which os you're on, and depending on that imports the queue that we want with a common alias

probably at the top of the files that use the queues we have an if statement that checks which os you're on, and depending on that imports the queue that we want with a common alias

Yes that's what I was thinking. So you do want Windows support?

Yeah, when doing development it is so important/crucial to be able to run the mock

Alright just added Windows support. @JacksonElia can you confirm if it works?
Need to test this one last time on the pi before merging.

Latest commit adds a couple of tests which I believe are robust enough that I don't need to test this PR on the Pi before merging.
If one of you can confirm that this works on Windows within 24 hours, I can merge (still need an approving review). Otherwise, I have a Windows machine nearby I can quickly test on.


GenerateContentRequest.FunctionCallingConfig is missing

This is a preview feature
https://cloud.google.com/vertex-ai/generative-ai/docs/model-reference/function-calling#functioncallingconfig-[preview]

This was added in https://github.com/googleapis/google-cloud-dotnet/pull/13035, but we haven't done a release yet. (We need to decide whether we're going to do a minor version with the breaking changes, or a new major version.)

(Note that it's not in GenerateContentRequest directly - you'd set the GenerateContentRequest.ToolConfig property to a ToolConfig which in turn has a FunctionCallingConfig.)

This should now be available in Google.Cloud.AIPlatform.V1 version 3.0.0

Yes, thank you.

Yes, now is in the version 3.0.0. But now, im missing support for gemini 1.5 flash, not only pro:
"Unable to submit request because the forced function calling (mode = ANY) is only supported for Gemini 1.5 Pro models."

Sorry, that's not something we can help with - if the client library is making the requests accurately (which I expect it is) you'll need to check the AI Platform documentation and support for further information.


store: Process start times growing linearly with blocks in objstore

Thanos, Prometheus and Golang version used:
thanos, version 0.15.0 (branch: HEAD, revision: fbd14b49f95e7543883fedf9381a21127d4dda2b)
build user:       root@d35b081d3e19
build date:       20200907-09:29:21
go version:       go1.14.2
Object Storage Provider: GCS
What happened: The time that that Thanos Store takes to become Ready has steadily grown over the last few months, as our block count, including marked-for-deletion blocks, have grown. Currently, it takes about 20 min for the process to start and become ready for grpc query traffic. This makes recovery from OOMs and updates to configs dangerous, as process restarts must be coordinated between HA store nodes so that the service is not unavailable.
What you expected to happen: Thanos Store process restart takes at most a few minutes.
How to reproduce it (as minimally and precisely as possible):

Create GCS bucket with uploaded thanos blocks of type:

{state="loaded"} | 17291
{state="marked-for-deletion"} | 8543
{state="duplicate"} | 2795
{state="time-excluded"} | 2468
{state="no-meta-json"} | 7
{state="label-excluded"} | 0
{state="too-fresh"} | 0
{state="corrupted-meta-json"} | 0
{state="failed"} | 0

Configure thanos store to use that bucket via objstore.config and start the process
Monitor logs for "duration=" to see the base fetcher duration

Full logs to relevant components:
level=info ts=2020-09-10T16:09:59.54113385Z caller=http.go:57 service=http/server component=store
  msg="listening for requests and metrics" address=<IP_ADDRESS>:9090
level=info ts=2020-09-10T16:30:39.287137249Z caller=fetcher.go:453 component=block.BaseFetcher
  msg="successfully synchronized block metadata" duration=20m39.746067576s cached=30429 returned=17226 partial=5
...
level=info ts=2020-09-10T16:31:42.380517614Z caller=store.go:329
  msg="bucket store ready" init_duration=21m42.83945024s

Anything else we need to know:
It appears the bulk of the process start time is in https://github.com/thanos-io/thanos/blob/e0b7f7b32e9c1071586cb5fb1b4ed4f134235824/pkg/block/fetcher.go#L400, based on observing thanos_objstore_bucket_operations_total.
From thanos_objstore_bucket_operations_total we can chart the progress of the f.wrapped.fetch function, which appears to have two phases:

a highly concurrent f.fetchMetadata(ctx) phase
a single threaded (f *IgnoreDeletionMarkFilter) Filter phase

When started cold, with no on-disk meta cache, {operation="get"} and {operation="exists"} rise in tandem. In this attached graph we see fetchMetadata completing within 1m 20s of process start. Then, only {operation="get"} continues to increase, at a much slower rate, for the next 10 or so minutes, at which point a chef converge restarted the process before it was ready.

When the process is started with an already present on-disk meta cache, only {operation="exists"} operation count rises, as the files are being found and loaded from disk. However, the slow rate of {operation="get"} in the second phase appears the same as the cold start case.

When searching through the code, I was able to match the cold start rise of {operation="get"} and {operation="exists"} to (f *BaseFetcher) loadMeta and its use of exists and get.
Further code reading suggests that the slow rise of {operation="get"} operations appears to be from IgnoreDeletionMarkFilter.Filter metadata.ReadDeletionMark
The chart seems to show that we are naively fetching deletion marks for all blocks in the objstore, as thanos_objstore_bucket_operations_total{operation="get"} rises by ~30K before the process is ready for queries. Looking at the code, the single threaded nature of the filter block seems to fit the increase in Thanos Store process start time with number of blocks, as well.
I think that there are a number of possible improvements to these filter functions, such as adding the same goroutine based concurrency to filters as fetchMetadata has, and/or caching deletion-marks on disk and using lightweight exists objstore calls to see if they exist before attempting to get.
It is possible a similar bug exists in Compact, as it uses a similar code path, but compact is not a user visible component and is not as sensitive to delays in start up time.

Very nice investigation! It seems to me like we should implement concurrency there and re-use this value here https://github.com/thanos-io/thanos/blob/03b6991949601d82fe17c4fbd2a658f678f0a6a5/cmd/thanos/store.go#L42 in that filter + add locking around modifying f.deletionMarkMap to avoid modifying the map concurrently.

Just curious if you have PV for those store GW instance?

Same problem here, I have more than 5k of blocks in gcs, and thanos-store component takes around 20min to load it. Is there any configuration to make this time decrease ?

Same issue for us too. Takes more than 25m.

Hopeful that #3500 and 0.18.0 speeds store start up, but have not had a chance to test the rc. Will update once we either get to the rc or deploy the 0.18.0 official release.

@gburek-fastly Have you observed any improvements after #3500?

Just as a stopgap solution, have you tried to utilize a shared cache (memcached)?
 If so how does your config look like?

@kakkoyun with 0.18.0, I have seen a reduction in startup time of store from approximately 2*N to N where N is the block count.
Our block count (with store  --max-time=-170h) is:
{state="failed"} | 0
{state="label-excluded"} | 0
{state="marked-for-no-compact"} | 0
{state="corrupted-meta-json"} | 0
{state="too-fresh"} | 0
{state="no-meta-json"} | 1
{state="duplicate"} | 8
{state="marked-for-deletion"} | 234
{state="time-excluded"} | 12275
{state="loaded"} | 26903

With 0.17.2: ts=2021-02-16T20:29:06.957979067Z caller=store.go:332 msg="bucket store ready" init_duration=40m19.691307451s
With 0.18.0: ts=2021-02-16T21:00:20.674829232Z caller=store.go:332 msg="bucket store ready" init_duration=28m3.441506353s
0.17.2:

0.18.0:

#3500 seems to reduce the 10m window where get operations are increasing to maybe 10s. The window where iter operations are rising remain similar, with 26m in 0.17.2 and 23m in 0.18.0
Our store nodes already use a shared index-cache in memcache, but not store.caching-bucket.
We also run compact, but have have about 250 prometheus replicas and thanos sidecars uploading blocks, which results in our fairly large block count.

Looking more at logs, the bulk of the improvement is in https://github.com/thanos-io/thanos/blob/v0.18.0/pkg/block/fetcher.go#L437-L442
0.17.2: ts=2021-02-16T20:33:31.264784686Z caller=fetcher.go:458 component=block.BaseFetcher msg="successfully synchronized block metadata" duration=13m29.266629999s cached=39429 returned=26909 partial=68
0.18.0: ts=2021-02-16T20:04:53.292830948Z caller=fetcher.go:458 component=block.BaseFetcher msg="successfully synchronized block metadata" duration=3m49.776358561s cached=39935 returned=26909 partial=0
However, both versions still take ~24m from that point in start up to become ready for queries.
Looking at the code and logs, it seems the iter section coincides with the addBlock section of SyncBlocks. Adding thanos_bucket_store_block_loads_total (which is incremented in addBlock) to the previous graph of thanos_objstore_bucket_operations_total I think confirms this:

Looking closer at our node metrics, it appears we hit a ~60MB/s Sustained throughput limit on our disks during the 23m iter section. This implies 60MB/s *24 minutes = 86.4 GB read on start up, which checks out.
We should be able to increase our disk throughput and our --block-sync-concurrency to get this faster and stop linear growth of start up time.


 Auth-controller update ClusterRole and RoleBinding to get permissions of namespaces, when user is updated. May be we should add user as a kind of resource.

Watch Namespace and update the permissions of namespace scoped resources for regular user.
@resouer @feiskyer

Need more details about how auth/authz are executed, e.g. auth-controller is actually not in the user request flow, it is responsible of updating RBAC rules and binding when

a new user is created: allow the user to create/get namespace
a new namespace is created/deleted
a network is created/deleted
a user is removed: delete all user related data

@feiskyer You are right, auth-controller is not in request flow. It run alone, and watch resources to update RBAC.

Use Third Party Resources to create user resource:

apiVersion: extensions/v1beta1
kind: ThirdPartyResource
metadata:
  name: user.stable.example.com
description: "A specification of a User"
versions:
- name: v1

Add a user object. May be there more detail user information will be set using custom fields like username. At least username are required.

apiVersion: "stable.example.com/v1"
kind: User
metadata:
  name: alice
username: "alice chen"

auth-controller
auth -controller will watch resources including User, NameSpace, Network and update RBAC roles and binding using superuser.
First  create ClusterRole for regular user to get permissions of NameSpace :
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1alpha1
metadata:
  # "namespace" omitted since ClusterRoles are not namespaced.
  name: namespace-creater
rules:
  - apiGroups: [""]
    resources: ["namespace"]
    verbs: ["get", "create"] # I think verbs should include "delete"，user have permission of deleting their namespace

a new user are created:

create ClusterRoleBinding for new regular user reference namespace-creater role:
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1alpha1
metadata:
  name: username-namespace-creater
subjects:
  - kind: User
    name: username
roleRef:
  kind: ClusterRole
  name: namespace-creater
  apiGroup: rbac.authorization.k8s.io

a new namespace are created:

create Role namespaced:
kind: Role
apiVersion: rbac.authorization.k8s.io/v1alpha1
metadata:
  namespace: namespace
  name: access-resources-within-namespace
rules:
  - apiGroups: [""]
    resources: [ResourceAll]
    verbs: [VerbAll]

create Rolebinding reference to role namespace:
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1alpha1
metadata:
  name: namespace-binding
  namespace: namespace
subjects:
  - kind: User
    name: username
roleRef:
  kind: Role
  name: access-resources-within-namespace
  apiGroup: rbac.authorization.k8s.io

role and rolebinding will be removed when namespace are deleted

a network is created/deleted

Which kind of resource Network will be defined, namespaced or non-namespaced? @feiskyer If it is non-namespace, we can set permission of Network in ClusterRole when user are created. If it is namespaced resource, the permission of Network will be set in Role when namespace are created.

a user is deleted:

ClusterRoleBinding related the user will be removed at least.
cc @resouer @feiskyer

@heartlock  Network is not namespace scoped. It could be associated with multiple namespaces. All pods belonging to same namespace share same network, but different namespaces may be associated with different networks.
And please merge all your comments here into a single doc, and send a PR to place it into docs/proposals, then feiskyer and I can review and merge it.

close this in favour of #163


credentials ownership in the UI

Hi Bruce
thanks a lot for the amazing work!
i just tested the docker container and i would like to know if there is a way to mount the current credentials without changing their ownership  within the container. just to better explain
imagine i run as root and i have my credentials there, if i run  the container as suggested
docker run -u griduser -ti --rm --name ui -v $HOME/.globus:/home/griduser/.globus quay.io/egi/ui /bin/bash
the credentials available under the griduser home will be owned by root
is there a way in docker to mount a volume and give the ownership to the user specified via -u?
thanks
Andrea

Ciao @andrea-manzi
With griduser I was primarily concerned with not running clients as root in the container. Not that it's a problem for the container, but some of the clients would complain.
The case you specify will indeed fail - I guess I should create a test case for that (thanks!)
I will check the docker documentation, but I think the only way to win that game is to run the container as root.


Add support for FIPS140-3

related: backlog/issues/1450

This PR can only be merged once x64LinuxIBM has FIPS140-3 enabled in JDK17.
FYI @AdamBrousseau

@AdamBrousseau This PR is ready for review.
cc @LongyuZhang


Where is the function segment in class GaussianModel doing in the code?

I did not find anywhere that declares this function. Also I noted that there is an empty mask check where the code is directed to Please run seg.py. But I cannot see such python script titled as <seg.py>. Can someone do me a favor to help me understand this?

This function removed the background Gaussians and its related attributes from the model. The remained Gaussians describe the target object you segmented (stored as precomputed_mask.pt, which is a binary mask)

This function removed the background Gaussians and its related attributes from the model. The remained Gaussians describe the target object you segmented (stored as precomputed_mask.pt, which is a binary mask)

Hi, Jumpat, thanks for your answer. But I am still wondering where its explicit cal is in the project?

In render.py, with args --segment, the script will call .segment to get the foreground object.


adds second part of the blog tracing system calls using ebpf

Signed-off-by: ashutoshcloud<EMAIL_ADDRESS>) (CloudDefense.AI)
What type of PR is this?
/kind content
Any specific area of the project related to this PR?
/area blog
What this PR does / why we need it:
This PR adds the second part of the blog Tracing System Calls Using eBPF.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ashutoshcloud
Once this PR has been reviewed and has the lgtm label, please assign vjjmiras for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

content/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ashutoshcloud, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 68ecebb57dfed03ada35922464de0ccdabd344b0


fix hyperlinking from schema docs (schemas-only): https://github.com/…

…metanorma/iso-10303/issues/41
Metanorma PR checklist

[ ] Breaking changes (list related PRs)
[ ] Documentation update required (create task for this)
[ ] External dependency introduced (documentation update need)
[ ] Gem with native library introduced

I'd have to rubocop all of metanorma-plugin-lutaml, it does not adhere to our rubocop...

@opoudjis : @kwkwan will reimplement the lutaml-express code with Liquid::Drop which prevents us from needing to serialize before going into Liquid, which will greatly enhance performance.

Good, thank you!

@ronaldtse @kwkwan Update on this?


Sorting is not working correctly

Hi! I am new to list.js. It seems easy to use and does what I need. I am running in to a weird problem, however, and I'm not sure why.
When I sort, it works on all columns except for a couple, which sorts the entire list correctly except the first couple cells. Maybe there's a weird thing about the character or data or something, but I'm looking at the original file, the input data, the data how it reads on the screen, and it all seems to be fine. Take a look at my site here: https://goo.gl/vKvVyv. Try clicking the headers to sort by column. They all work fine, except for the Commitment and Paid to Date fields, which do something like this:
In "descending" order:
$450
$900
$16,000
$15,500
$15,400
$15,200... and so on
Why are my first couple values not sorted properly?
Thanks!
BDPARKER

Ok, I know why, but I still need a solution.
It's treating the numbers with commas (ie. 16,000) as decimals (so it sees it as 16) and sorts it accordingly. Therefore, $15,500 is less than $400 becuase it sees it as $15.5. How do I fix this? It's doing it with all my columns.
Here's a real example from my site:
18.75%
14.88%
12.70%
5,000.00%
2.89%
1.56%

Hi
An easy way to sort as number by list.js is defining 'data-xxx' attribute in your data of TD. You can use two types of string, displaying for human and sorting for list.js.

002, Blessed Sacrament
Rochester
107
$35,862.00
$34,904.00
$73,822.00
48.58%

In addition, you have to change your js code as follows.

Best,
Kanaxx

Thanks, I gave it a try. It did not work for me, though. Instead of sorting incorrectly (and seeing commas as decimals), it didn't sort at all.

Another thing, I ran a script to change all commas "," to something else, like a weird character, a "'" or anything else. It does the same thing. It's like it sees the first non-numeric character as a decimal and treats it as such. If I get rid of the character (so that it reads $52586.90, for example), it sorts just fine, but I can't have that.

let me show you my example, https://kanaxx.github.io/listjs/number-sort.html
Commitment and  Percent have other value for sorting, data-comm and data-perc. You have to make with data-xxx into all TD column and make a data-xxx's value with only decimal character.
Paid to Date and Goal don't have data-xxx attribute and values so these column sort don't work fine.


TECS: Initialize all integrals in one place when not active

@tumbili Enjoy!

Tested in HIL, this is going in.

Applied, closing.


New version: DataStructures v0.17.5

Registering package: DataStructures
Repository: https://github.com/JuliaCollections/DataStructures.jl
Created by: @oxinabox
Version: v0.17.5
Commit: 452caf87dc59838b731d7ad750d51dc6bd117240
Reviewed by: @oxinabox
Reference: https://github.com/JuliaCollections/DataStructures.jl/commit/452caf87dc59838b731d7ad750d51dc6bd117240#commitcomment-35707833

Your new version pull request met all of the guidelines for automatic merging.
I will automatically merge this pull request during the next cron job.
If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]


is there any way to return mongodb query in response?

My api app use both mysql and mongo and i use https://github.com/jenssegers/laravel-mongodb for mongodb eloquent, i want to know that can i get mongo query in response or should i use other package?

You can create a mongodb query collection, then add it to config https://github.com/mlanin/laravel-api-debugger/blob/master/config/api-debugger.php


Reflow Markdown for translations

Extract links
Remove line breaks (please use "Word Wrap" in your editor)

Signed-off-by: Roman Tsisyk<EMAIL_ADDRESS>

➜  organicmaps.github.io git:(markdown-reflow) zola serve
Building site...
Checking all internal links with anchors.
> Checked 3 internal link(s) with anchors: 1 target(s) missing.
Error: Failed to serve the site
Error: Found 1 broken internal anchor link(s)
  1. The anchor in the link<EMAIL_ADDRESS>in /Users/alex/Developer/omim/organicmaps.github.io/content/_index.md does not exist.


TabNavigator first tab with FlexBox bug on iOS!

when i use TabNavigator,the first tab flex box will have bug,this is my code.

the same code will show different result in different tab,this is example

as you know , flex: 1 should seprate the view parent, but the first tab does not show normal,how can i solve this bug

I believe this is a bug with tab-view or in Yoga (react-native) that should be reported there, @satya164 ?

It's likely a bug with ScrollView/Yoga. Can you try to reproduce this in a normal ScrollView?

I have solved this bug.please look at this https://github.com/react-community/react-navigation/issues/1071


Refactor the operator naming

Describe the problem
As we have emerging number of operators we should use naming convention for Operators and it's resources.
Proposed solution
As the domain we should use: banzaicloud.io. (this is a company wide rule)
For the application group we can use: logging or log.
For the configuration (like application logging): config
Example new application config crd: config.logging.banzaicloud.io
Example fluentd specific crd: fluentd.logging.banzaicloud.io

This was revisited in #56 we have the following crds:
fluentbits.logging.banzaicloud.com
fluentds.logging.banzaicloud.com
plugins.logging.banzaicloud.com


[Fonts] Icon request: audio_file

Hi @tsuyo625, this icon is already available on the stable channel. See https://api.flutter.dev/flutter/material/Icons/audio_file-constant.html.
Closing as this icon already exists.


Add presenter layer

As seen in show and tell™
Before we put service data onto a page, we might want to do two things:

Pre-process the data from the API into a different format
Specify a template macro which is suitable for the type of data

This commit looks up both of these things based on the type property of the question object in the content but defaults to doing no processing if a presenter is not defined.
This means that we have more control over how each row in the summary is displayed, ie we can go:

…from this
…to this

:+1:


model html remove from dom on close

hi semantic team,
when i call the modal with this line if code,
//show modal
        $(e.target).parents('.card-request-js')
            .children('.confirm-modal-js')
            .modal({debug:true,performance:true,verbose:true})
            .modal('show');

runs first time. but when i close the modal, removes the completely html block of the modal from the dom.
my modal

                    Profile Picture

We've auto-chosen a profile image for you.

We've grabbed the following image from the gravatar image associated with your registered e-mail address.

Is it okay to use this photo?

                        Nope

                        Yep, that's me

thanks for help

i found the issue, it was a problem with the context argument.
sorry for the issue


erratic highlighting of stewardship icon

hey @bbest - if you mouse over the stewardship icon in the infographic, you'll notice that the highlighting and tooltip show up erratically:

I think that there is some error in the stewardship elements in the infographic svg, but it isn't immediately apparent what it is. When I check out the layer panel for the svg in Illustrator (shown below), the elements seem to be labelled properly. Unclear where the problem lies.

Hey @bbest - the issue turns out to have nothing to do with the svg. The reason that the tooltip was displaying in an erratic manner for the stewardship icon was because it's title was too long. In the associated google spreadsheet, the title was listed as "Number of participants in Sanctuary maritime heritage stewardship events". When the code attempted to make this a tooltip, it didn't work predictably. However, I solved the problem by shortening the title to "Participants in maritime heritage stewardship events" in the spreadsheet. With this new title, the tooltip works fine.


Update Globals “site_data”

Automatically generated by Netlify CMS

👷 Deploy Preview for anatidaephobia processing.

Name
Link

🔨 Latest commit
3a72c533b06bc2830ae9f95b48bf6a2675c1aaae

🔍 Latest deploy log
https://app.netlify.com/sites/anatidaephobia/deploys/6243fe03ffe5c600093d4b78


test-branch/execute-job/quoted-authorization/507bf856-1dff-4c64-8140-702694944fd6

PR for testing f21cb6830fed2242aa95990d644686d54afd8563

/canonical/self-hosted-runners/run-workflows f21cb6830fed2242aa95990d644686d54afd8563


What is the use of watcher in the APIs?

Hi @24x7soumya!
When set to true, there should be a watcher added and events are sent to the client. There's corresponding functions where you can pass explicit callback functions. I don't remember if I've ever used a true value when using the one with booleans, though.
I think this is the place where it is done from the C wrapper: https://github.com/yfinkelstein/node-zookeeper/blob/master/src/node-zk.cpp#L481
And re-emitted in the JavaScript client: https://github.com/yfinkelstein/node-zookeeper/blob/master/lib/zookeeper.js#L79

Thanks for the response @DavidVujic . It is a bit confusing about how the event will be received.
But I got the idea.


[Mod] directory level of output error images

modify directory level of output error images to enable search what you want to see.

first level: Error types
second level: label names

enable rename output directory name of error images

add name of argument m to directory prefix

Sorry for bother you when you have tough tasks.

Thank you for your review!
I pushed lintered.


Add analog/digital pin read/write blocks for sensebox

Add these general Arduino blocks for Sensebox in configuration and program toolboxes and check that they are properly implemented.

Blinking an LED on all ports works in digital and analog mode.


[BuildSystem] Fix BuildValue initialization & serialization.

The initializer was allowing uninitialized data in the commandSignature for
sentinel values (like virtual inputs).

The move initialization was failing to initialize some fields (!).

The serialization was also failing to properly normalize values, so the
serialized value was not properly deterministic.

@swift-ci please test

@m-i-r-z-a can you review? We really need some proper serialization support code, but in lieu of that this at least fixes a major problem.

@swift-ci please smoke test

LLVM does a SmallVector, but because we are serializing by type punning the bytes we have to directly manage all of the implementation details. It's also significantly larger in size for the 1-or-many case because of the general purpose nature.
I suspect we could clean it up in other ways though if we had explicit serialization instead of type punning.


move qml.ml.* python modules to qml.*

On second thought it seems unnecessary to type qml.ml.respresentations, rather than qml.representations.
Anybody against me moving it back to it's former dir?

If nobody is against this, I will make the pull request today. :+1:

Done


Adding support for onCreateItemViewHolder to create multiple type of viewholder base on row and column

I understand that viewing csv file and supporting dragging required every table cells are the same but it would be great if AdaptiveTableLayout can support multiple type of viewholder in readonly mode. That will make displaying multiple type of data (for each column) with different layouts much more easy.

+1 for this.
I really need a way to render different layouts for each regular "item" cell. Something similar to what the RecyclerView does by implementing your own:
public int getItemViewType(int position)
and passing the the viewType field as a second param to the
onCreateItemViewHolder method. Or even just pass the row and column values to it.

Hi @hlongvu @cioraneanu , thx for using our library.
We will integrate this feature in the next releases.
With best regards Cleveroad team.


feat: JS Editor

Description
Js collection
Fixes #1751
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.

Test A
Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: feature/jsCollectionEval

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
54.22 (-0.72)
36.06 (-0.76)
32.85 (-0.77)
54.73 (-0.75)

:sparkles: :new:
app/client/src/actions/jsActionActions.ts
68
100
0
54.55

:sparkles: :new:
app/client/src/actions/jsPaneActions.ts
68.18
100
0
53.33

:sparkles: :new:
app/client/src/api/JSActionAPI.tsx
60.87
100
11.11
59.09

:green_circle:
app/client/src/api/PluginApi.ts
89.47 (0.58)
100 (0)
60 (0)
88.89 (0.65)

:red_circle:
app/client/src/components/editorComponents/ActionNameEditor.tsx
26.09 (-1.18)
3.39 (0)
0 (0)
27.69 (-0.88)

:sparkles: :new:
app/client/src/components/editorComponents/JSResponseView.tsx
43.08
20.29
0
45.9

:red_circle:
app/client/src/components/editorComponents/ActionCreator/Fields.tsx
27.62 (-1.11)
22.64 (-2.89)
7.35 (-0.34)
26.79 (-1.09)

:red_circle:
app/client/src/components/editorComponents/ActionCreator/index.tsx
41.62 (-5.58)
7.76 (1.18)
38.46 (-5.98)
41.53 (-5.24)

:green_circle:
app/client/src/components/editorComponents/CodeEditor/generateQuickCommands.tsx
28.95 (0.95)
6.25 (-0.42)
6.25 (0)
28 (0.97)

:red_circle:
app/client/src/components/editorComponents/CodeEditor/hintHelpers.ts
78.57 (0.31)
70 (-5)
40 (0)
77.78 (0.51)

:red_circle:
app/client/src/components/editorComponents/CodeEditor/index.tsx
62.41 (0)
35.06 (-0.47)
50 (0)
64.75 (0)

:green_circle:
app/client/src/components/editorComponents/CodeEditor/styledComponents.ts
90.57 (0.19)
60.23 (-0.24)
100 (0)
94.12 (0.12)

:red_circle:
app/client/src/components/editorComponents/Debugger/EntityLink.tsx
27.14 (-3.37)
7.41 (-2.11)
7.14 (-1.19)
27.94 (-3.64)

:red_circle:
app/client/src/components/editorComponents/GlobalSearch/SearchResults.tsx
23.36 (-1.26)
22.22 (-0.46)
0 (0)
23.88 (-1.32)

:red_circle:
app/client/src/components/editorComponents/GlobalSearch/index.tsx
53.68 (-1.13)
16.81 (-1.41)
37.31 (-0.79)
54.69 (-1.51)

:red_circle:
app/client/src/components/editorComponents/GlobalSearch/useRecentEntities.tsx
48.65 (-2.87)
7.5 (-2.5)
37.5 (-5.36)
50 (-3.13)

:green_circle:
app/client/src/components/editorComponents/GlobalSearch/utils.tsx
71.3 (0.13)
29.41 (1.75)
68.18 (0)
69.89 (0.23)

:green_circle:
app/client/src/constants/messages.ts
71.58 (0.78)
100 (0)
14.29 (2.39)
78.17 (-0.62)

:green_circle:
app/client/src/constants/routes.ts
83.44 (1.56)
41.38 (1)
63.64 (3.64)
81.56 (1.72)

:green_circle:
app/client/src/entities/Action/index.ts
70.59 (1.84)
50 (0)
66.67 (0)
78.57 (1.65)

:red_circle:
app/client/src/entities/DataTree/dataTreeFactory.ts
43.24 (-0.51)
100 (0)
42.86 (-7.14)
41.67 (-0.27)

:sparkles: :new:
app/client/src/entities/DataTree/dataTreeJSAction.ts
12.12
0
0
10

:red_circle:
app/client/src/icons/MenuIcons.tsx
60 (-1.54)
100 (0)
14.29 (-2.38)
60 (-1.54)

:green_circle:
app/client/src/pages/Editor/routes.tsx
42.25 (0.82)
22.22 (0)
6.67 (0)
46.77 (0.87)

:red_circle:
app/client/src/pages/Editor/Explorer/EntityExplorer.tsx
84.31 (-3.19)
40 (-7.06)
50 (-10)
85.42 (-3.47)

:green_circle:
app/client/src/pages/Editor/Explorer/ExplorerIcons.tsx
88.71 (1.21)
58.33 (0)
20 (0)
88.33 (1.29)

:red_circle:
app/client/src/pages/Editor/Explorer/helpers.tsx
63.64 (-4.22)
34.62 (-10.38)
25 (-8.33)
58.62 (-5.38)

:red_circle:
app/client/src/pages/Editor/Explorer/hooks.ts
46.28 (-2.15)
28.17 (-1.06)
60.47 (1.01)
50.34 (-1.66)

:red_circle:
app/client/src/pages/Editor/Explorer/Entity/EntityProperties.tsx
21.21 (-1.2)
0 (0)
0 (0)
21.54 (-1.27)

:green_circle:
app/client/src/pages/Editor/Explorer/Entity/Name.tsx
59.21 (0.31)
26.83 (-0.67)
46.15 (0.7)
58.33 (0.36)

:sparkles: :new:
app/client/src/pages/Editor/Explorer/JSActions/JSActionContextMenu.tsx
35.71
0
0
37.04

:sparkles: :new:
app/client/src/pages/Editor/Explorer/JSActions/JSActionEntity.tsx
63.64
100
0
63.64

:sparkles: :new:
app/client/src/pages/Editor/Explorer/JSActions/JSActionGroup.tsx
61.11
0
0
61.11

:sparkles: :new:
app/client/src/pages/Editor/Explorer/JSActions/MoreJSActionsMenu.tsx
31.58
33.33
0
34.29

:sparkles: :new:
app/client/src/pages/Editor/Explorer/JSActions/helpers.tsx
40
0
0
38.46

:green_circle:
app/client/src/pages/Editor/Explorer/Pages/PageEntity.tsx
90.91 (0.91)
40 (2.5)
60 (0)
90.91 (0.91)

:green_circle:
app/client/src/pages/Editor/Explorer/Pages/PageGroup.tsx
79.49 (0.54)
60 (1.18)
50 (0)
81.58 (0.5)

:green_circle:
app/client/src/pages/Editor/GeneratePage/components/CrudInfoModal.tsx
80.77 (1.92)
89.66 (0)
41.67 (8.34)
79.17 (2.09)

:sparkles: :new:
app/client/src/pages/Editor/JSEditor/Form.tsx
46.67
85.71
0
48.84

:sparkles: :new:
app/client/src/pages/Editor/JSEditor/JSObjectNameEditor.tsx
22.22
4.44
0
23.73

:sparkles: :new:
app/client/src/pages/Editor/JSEditor/index.tsx
56.67
33.33
33.33
61.54

:sparkles: :new:
app/client/src/reducers/entityReducers/jsActionsReducer.tsx
5.77
0
0
6.19

:sparkles: :new:
app/client/src/reducers/uiReducers/jsPaneReducer.ts
31.25
100
0
31.25

:red_circle:
app/client/src/sagas/ActionSagas.ts
10.93 (-0.03)
0.78 (0)
3.7 (0)
13.27 (-0.04)

:red_circle:
app/client/src/sagas/DebuggerSagas.ts
15.64 (-1.54)
4.52 (-0.55)
17.65 (0)
17.39 (-1.66)

:red_circle:
app/client/src/sagas/EvaluationsSaga.ts
22.29 (0.14)
1.59 (-0.05)
10 (-1.11)
25.55 (0.36)

:red_circle:
app/client/src/sagas/InitSagas.ts
42.02 (-2.02)
12.82 (-1.47)
66.67 (0)
46.94 (-0.89)

:sparkles: :new:
app/client/src/sagas/JSActionSagas.ts
16.07
2.04
6.67
18.98

:sparkles: :new:
app/client/src/sagas/JSPaneSagas.ts
21.31
2.13
9.09
25

:green_circle:
app/client/src/sagas/PageSagas.tsx
23.6 (0.07)
6.25 (0)
14.29 (0)
25.27 (0.09)

:red_circle:
app/client/src/sagas/PluginSagas.ts
14.58 (-1.51)
2.94 (-0.63)
10 (-1.11)
17.5 (-1.94)

:red_circle:
app/client/src/sagas/PostEvaluationSagas.ts
17.73 (-0.26)
0 (0)
0 (0)
21.74 (-0.38)

:red_circle:
app/client/src/sagas/RecentEntitiesSagas.ts
40.63 (-4.2)
10 (-2.12)
50 (0)
40.63 (-4.2)

:green_circle:
app/client/src/sagas/index.tsx
92.45 (0.29)
60 (0)
100 (0)
94.12 (0.24)

:red_circle:
app/client/src/selectors/editorSelectors.tsx
69.51 (-2.39)
57.89 (-3.65)
53.7 (-4.3)
66.67 (-2.13)

:green_circle:
app/client/src/selectors/entitiesSelector.ts
51.85 (0.24)
8.54 (1.96)
28.07 (0.03)
49.09 (0.06)

:red_circle:
app/client/src/utils/AppsmithUtils.tsx
56.41 (-0.73)
34.09 (0)
34.88 (-2.62)
51.5 (-0.97)

:red_circle:
app/client/src/utils/DynamicBindingUtils.ts
89.58 (-1)
83.54 (-0.46)
78.26 (0)
88.1 (-1.07)

:sparkles: :new:
app/client/src/utils/JSPaneUtils.tsx
3.64
0
0
2.27

:red_circle:
app/client/src/utils/autocomplete/EntityDefinitions.ts
28.13 (-15.62)
0 (0)
16.67 (-3.33)
27.59 (-16.16)

:green_circle:
app/client/src/utils/autocomplete/TernServer.ts
50.71 (0.24)
38.7 (0.98)
36.21 (0)
55.35 (0.27)

:red_circle:
app/client/src/utils/autocomplete/dataTreeTypeDefCreator.ts
70.37 (-12.96)
50 (-7.14)
100 (0)
66.67 (-13.33)

:red_circle:
app/client/src/workers/DataTreeEvaluator.ts
83.65 (-4.8)
64.91 (-11.28)
83.12 (-4.02)
83.06 (-5.23)

:red_circle:
app/client/src/workers/evaluate.ts
94.52 (-5.48)
80 (-3.33)
89.47 (-10.53)
94.44 (-5.56)

:red_circle:
app/client/src/workers/evaluationUtils.ts
81.2 (-3.38)
67.48 (-3.69)
78.05 (-3.53)
79.9 (-4.06)

:red_circle:
app/client/src/workers/validations.ts
79.12 (0)
69.27 (-0.64)
73.08 (0)
81.2 (0)

some bugs are fixed here https://github.com/appsmithorg/appsmith/pull/7056


So, the kernel do not support SMP now,right?   :-)

Maybe add the MultiProcessor support for xbook2 is feasible, but i find it's also difficult,because should conversion the "pic" to "apic" contain the interrupt.And also will influence the process and switch  :-)
There May be more problems

I have also learned about SMP before, and I also know that APIC support is required. Therefore, I tried to implement APIC, but it was too complicated, involving many registers and many operations. And this is only the interrupt part, SMP also needs to use other more operations. Especially scheduling processes to different processors, synchronization and mutual exclusion issues, memory management issues. This is indeed a very complicated part.

I quite agree with you, haha. When I thought how to add this feature into xbook2,I felt there are too (much) things to do just like to rebuild the kernel at the beginning time.  XD

Yes, there is such a big difference between supporting a single processor and multiple processors. It's too difficult to do, the new system, you can call him xbook-smp, haha.

O(∩_∩)O good idea haha

As long as the modification of the processor is involved, it is equivalent to porting to another platform. Even x86->x86 smp.

...emm yeah, That's also a big question.


Minimum Tasks Checklist for the RTS Project

Following task should be completed for the project, please, add comments below if desired and reference big commits to the issue.
DESIGN

[ ] GDD: Game Design Document Docs/GDD.md
[ ] TDD: Tech Design Document Docs/TDD.md
[ ] GUI Document Docs/GUIDocument.md
[ ] Art Bible Docs/ArtBible.md
[ ] Audio Bible Docs/AudioBible.md
[ ] QA Workflow Docs/QAWorkflow.md
[ ] Production Plan Docs/ProductionPlan.md

GENERAL

[ ] Screens transitions: fade-in/fade-out or better transitions (RS: Camera Transitions)
[ ] GOD mode (F10): no-damage, fly-around mode, increase-resources...
[ ] Game resolution: 1280x720px@60fps, support for windowed mode and fullscreen
[ ] Custom game icon, custom mouse icon, executable properties (metadata) (RS: Installer)
[ ] Assets/Resources loaded from a ZIP (RS: Assets ZIP Management)
[ ] Automatic Continuous Integration and Deployment (RS: Automatic CI + CD)

SCREEN: LOGO

[ ] Logo implemented: custom art, avoid plain text
[ ] ANIM: Animated Logo in/out (fading, movement…) (RS: Camera Transitions)
[ ] AUDIO: Sound FX characteristic for the logo

SCREEN: TITLE

[ ] Main game title implemented, custom art, avoid plain text
[ ] ANIM: Title animation with easings (fading, movement…)
[ ] AUDIO: Sound FX characteristic for the title appearing
[ ] AUDIO: Music track specific for the screen
[ ] UI: Main game menu implemented: START - CONTINUE - OPTIONS - EXIT
[ ] UI: ANIM: Animated menu, responsive, visual feedback...
[ ] UI: AUDIO: Buttons/UI fx feedback sounds

SCREEN: OPTIONS

[ ] UI: Basic game config options implemented with custom font
[ ] UI: OPTION1: Fullscreen mode selection
[ ] UI: OPTION2: Music volume slider
[ ] UI: OPTION3: Fx sounds volume slider
[ ] UI: OPTION4: Gamepad/Keyboard configuration -> visual
[ ] ANIM: Animated options menu, responsive, visual feedback...
[ ] AUDIO: Sound feedback for buttons and sliders
[ ] AUDIO: Music track specific for the screen

SCREEN: GAMEPLAY

[ ] Implement at least 3 types of Resources (RS: RTS Balancing)
[ ] Implement at least 4 types of Playable Units (RS: RTS Balancing)
[ ] Implement at least 3 Quests (RS: Quest Manager)
[ ] Implement at least 4 Dialogs (RS: Dialog System)
[ ] Implement at least 5 Particle Systems (RS: Particle System)
[ ] Implement group movement (RS: Group Movement)
[ ] Implement fog of war (RS: Fog of War)
[ ] INPUTS: Gamepad + Keyboard/Mouse inputs implemented
[ ] UI: PAUSE menu available on pause
[ ] UI: PAUSE menu animated with feedback (custom font)
[ ] AUDIO: PAUSE menu in/out animation with audio feedback
[ ] UI: Minimap implemented and fully functional (RS: Minimap)
[ ] UI: ANIM: Interface elements should be animated with visual feedback
[ ] UI: AUDIO: Sound feedback for the interface elements (when required)
[ ] AUDIO: Minimum of 15 fx game sounds implemented
[ ] AUDIO: Positioning in the scree: Volume effects (RS: Spatial Audio & Music Manager)
[ ] AUDIO: Music track specific for the screen (RS: Spatial Audio & Music Manager)
[ ] AUDIO: Music effects fade-in/fade-out, lower volume on PAUSE

SCREEN: ENDING

[ ] Custom background with victory/lose messages (custom font)
[ ] ANIM: In/out animations (easings) for ending messages
[ ] AUDIO: Sounds for messages and animations
[ ] AUDIO: Music track specific for the screen

NOTE: This checklist could change at any given point with added/deleted requirements.

No tasks completed yet? 😕


SVG content like marker

Hello
My ask it's about how to insert a svk like a marker, but the text inside, not the url path. That's because i need to change some properties on the interface. There are some example to do that? thanks!

Hi, great to hear that you find Leaflet useful!
However, this issue tracker is used for reporting bugs and discussing new features. For questions on using Leaflet, please use gis.stackexchange.com or stackoverflow.