Automate last step of merging main into develop as part of our release workflow

The problem
Currently after making a release we need to manually merge main back into develop and push. We should automate the whole process to avoid the chance of forgetting to do this last step.
The solution

Add a final step to the release workflow that checks if: steps.changesets.outputs.published == 'true' and then proceeds to merge main into develop and push
Update documentation

I know that GitHub has a tough time doing fast-forward merges when merging PRs in the UI, so my hope is we won't run into this same issue programmatically/with the Actions API.


Addind functx unnecessary?

https://github.com/peterstadler/existdb-docker/blob/7345e489737df8b07fefc267552e47c3f00ea4b1/Dockerfile#L47
Adding the functx-1.0.1.xar is unnecessary, at lest fo reXist-db v5.2.0, as it's already included in the autodeploy directory. Is there any reason for keeping this, e.g. for older eXist versions?

Yes, you are right. This looks like superfluous legacy code. Do you want to remove it as you're working on #3 ?


Unresponsive Slave incorrectly triggers unsync alerts

If a slave is unresponsive, we should bypass the code to trigger a slave_unsynced alert. Currently it sets unsynced based on missing data, which causes double the alerts for an unresponsive slave.

This should be fixed via 063b3f300037ff9ab316b63621972c52c664b211.


Fix ConnectivityManagerImpl.cpp in order to let the ESP32 connect to …

…WiFi while STA mode is enabled but AP mode is disabled
Problem
Currently when the AP mode is disabled on the device. For example when one does not expect Rendezvous over WiFi, the ESP32 station mode does not work since the expected mode is APSTA while the current mode is only STA in this case.

@jelderton @hawk248 @robszewczyk ?


Upon further investigation, this is working as intended; just a quirk of the lack of granularity.


Possible issue

First, love this, it's awesome!
Second, codewords aren't working correctly. I tried multiple settings and could never get it to auto invite a guildie that whispered me whether they were on the list or not, whether invites were started or not. If you need help testing I am Gad on Atiesh-US.

@Mooslemike Hey, thanks for the feedback :) Are you available at about 23:00 GMT tonight? Then we can meet up and debug the issue. Thanks!

Yes, I’ll be free. My Discord is Gad#0451
Sent from my iPhone

On May 27, 2020, at 4:45 AM, Daniel Stoller<EMAIL_ADDRESS>wrote:

@Mooslemike Hey, thanks for the feedback :) Are you available at about 23:00 GMT tonight? Then we can meet up and debug the issue. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Seems to have been resolved in v0.3, so closing this for now.


More Stats on the Userpage.

Past Time Outs.
Number of Times timed out
number of bans
recent links posted
account age
These are just thing i feel would be helpful.
Maybe the ability to reset some data as well. Like resetting the number of times timed out

Just a few questions to clarify-

Account age as in "first time seen by this pajbot" or "date account was created with Twitch"?
Do you want to count timeouts and bans not from "paid timeout" and "paid ban" too?

No just normal vans and timeouts. Account date created with twitch

created separate issues


root5: fix build

Motivation for this change
ROOT5 includes a C++ interpreter/introspection tool called cint (rootcint) which is also is being used during the build of ROOT itself. The interpreter will try to access libc headers at /usr/include, which is not pure and can possibly break the build. We also can not supply our glibc headers because those require a modern compiler. This fix should remove some of the direct access to libc/posix calls, that should not affect functionality very much.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-review
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build xfitter

BTW would it make sense to bump this to latest 5.x while visiting it?
78c6129160560307216b3b308d965b4834b67634 is what I mean.
(I imagine moving to the 6 series is a bigger deal--from packaging or usage perspectives?)

@dtzWill Thanks for the bump, I went with 5.34.36 for root5 because 5.34.38 was never announced and probably it is not as widely adopted.
We have 6.x branch under root. It is the one to be used by the most people. I am not aware of any such kind of impurities in 6.x that I fix in this PR. The root5 is needed for legacy purposes.


project() not working when using ReactFlowProvider

I recently started using ReactFlowProvider and I noticed that the project function stopped working properly. My application has a sidebar where I can drag items and drop them into the react-flow-renderer. I use project to convert the screen coordinates so that the new node will appear at the drop location even after panning. This works perfectly fine when the provider is not present. As soon as I wrap <ReactFlow> with <ReactFlowProvider> (and change no other code), project always returns the passed position unchanged.
Not sure if I am doing something else wrong, but thought I would mention it here in case its a bug on your end.
I am using version 5.4.0.
Here is some relevant code:

export default function Graph(props: GraphProps): JSX.Element {
  const reactFlowInstance: any = useRef(null);

   ...etc

  const adjustPosition = (e: any): any => {
    const pos = { x: e.clientX - 300, y: e.clientY - 8 };
    console.log('position before: ', pos);
    const adjustedPos = reactFlowInstance.current.project(pos);
    console.log('position after: ', adjustedPos);
    return adjustedPos;
  };

  const addVertex = (e: any): void => {
   ...etc
    const newPos = adjustPosition(e);
    const newVertex = new ReactiveVertex(graphStore.getVertexById, newPos.x, newPos.y, displayText, transformData);
   ...etc
  };

  const onInstanceLoad = (instance: any): void => {
    reactFlowInstance.current = instance;
  };

   ...etc

  const vertices: any = graphStore.vertices.map((vertex) => ({
    id: vertex.id,
    type: 'vertex',
    sourcePosition: 'right',
    targetPosition: 'left',
    data: {
      vertex: vertex,
      ...etc
    },
    position: { x: vertex.posx, y: vertex.posy },
  }));

  const edges = graphStore.edges;
  const elements = vertices.concat(edges);

  return useObserver(() => (
    <Styled.Stage
      onDrop={addVertex}
      onDragOver={(e): void => e.preventDefault()}
      previewOpen={props.previewOpen}
    >
      <ReactFlowProvider>
        <ReactFlow
          onLoad={onInstanceLoad}
          elements={elements}
          onElementsRemove={onElementsRemove}
          onConnect={(connection): void => {
            setConnection(connection);
          }}
          onElementClick={(event, element): void => {
            if (element.type === 'vertex') {
              setSelectedVertexId(element.id);
            } else {
              setSelectedVertexId('');
            }
          }}
          onSelectionChange={(elems)=>{
            if (elems === null) {
              setSelectedVertexId('');
            }
          }}
          nodeTypes={{
            vertex: StagedVertex,
          }}
        >
          <Controls />
        </ReactFlow>
      </ReactFlowProvider>

     ...etc

    </Styled.Stage>
  ));
}

Hey @L33thaxor118
thanks for the report but there is already an issue for this bug #285
I hope you can find a workaround for now.

Hey @L33thaxor118
your issue was a good motivation to look into this bug again ;)
It should work with v5.4.1.


[AutoPR billing/resource-manager] Add GTM APIs.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5423

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/1781


Allow tg:toggler to prevent event propagation for displayed elements

The general technique used to prevent scrolling with the mouse wheel over an open hamburger menu is as follows:
let toggleIsFixed = function(active) {
  const htmlElem = document.getElementsByTagName("html").item(0);
  if (active) htmlElem.classList.add("is-fixed")
  else htmlElem.classList.remove("is-fixed");
}

html.is-fixed,
html.is-fixed body {
  height: 100%;
  overflow: hidden;
}

Consider using the Event.stopPropagation() method.

Introduce tg:stop="mousewheel".


Errors when using any other color LUT modes in the fog volume

Changing the color LUT mode to any other setting causes all the materials to go solid pink, and results in this error in the console:

This happens in every single project I've tested it in. I know it was working before, but something in a recent update must have brought up an issue.

Fixed. It landed in 1.6.0. thanks for reporting🖤


Add support for Plume Mainnet

Note that Plume is an Arbitrum Orbit chain, so multicall can't be deployed using the pre-signed transaction because the gas limit is too low.
Chain Name
Plume Mainnet
Chain ID
98865
RPC URL
https://phoenix-rpc.plumenetwork.xyz/FH7uok8YdCXHhBu4B18j632wpHogyMYan
Block Explorer URL
https://phoenix-explorer.plumenetwork.xyz
Deployment Funds
Yes

Do you have another RPC URL? The provided one does not work

Updated the RPC URL! Sorry about the churn.

Hey @mds1 - any updates on this? 0x1E91557322053858cf75cFE5b2d030D27cb2cA8D has 0.1 ETH on the provided RPC URL.

Done, thanks!


TBoxGenerator: Support UTF-8 files with BOM

The majority of CSV editing tools (Excel, Notepad++, VS Code) will create files with the UTF-8 BOM by default. At the time of writing, these files are not supported by the TBoxGenerator (it will throw errors about missing headings).
Suggest the code is updated to support UTF-8 BOM as this rather esoteric error will confuse new users.

Alternatively, output an explicit "File has UTF-8 BOM, please remove and try again" error.


Support upgrading hashes with --fix

Is your feature request related to a problem? Please describe.
pip-audit fixes only package versions but not their hashes.
Describe the solution you'd like
Update package hashes.
Describe alternatives you've considered
Run pip-compile after pip-audit.
Additional context

Thanks for the report @q0w -- like #564, this sounds like a bug, so we'd appreciate it if you'd use the bug template.

Updated

Thanks for reporting this @q0w! We should definitely support updating hashes with --fix.

@di We discussed this issue briefly yesterday. I can confirm that we've never supported this before so this isn't a 2.5.x regression. I think it's still worth making this one a priority though.


Upgrade traefik from v1 to v2 in vdc initialization

Description
Add certificate reslovers:

default: staging letsencrypt
le: letsencrypt
ghanem: ca1.grid.tf

ghanem's resolver works only for csfarmer farm.
Currently, traefik v1 is uninstalled using helm delete and the new one is installed.

To use the certificate resolver, ingress.certresolver should be set one of the 3 resolvers in the issue (default, le, ghanem). After the charts gets upgraded according to the issue
https://github.com/threefoldtech/vdc-solutions-charts/issues/31


Possible routes towards hybrid HPC workflow with on-premises machines

Hi, there. I am pretty new to AWS and maybe my question is too broad and general.
I was wondering whether parallelcluster could setup on-premises/cloud hybrid HPC infrastructures. Based on what I have read from the doc, the configurations are all about pure cloud HPC solutions. And my ideal setup would be, say, a master head node (and several compute machines) on premises and more elastic scaling compute nodes on the cloud which can be provisioned by submitting tasks on slurm. Besides, it would be a great plus if we can also incorporate these fascinating types of cloud storages (like FSx for Lustre) into such HPC.
Any suggestion on roadmaps to this setup? Or is there any future plans on supporting this by parallelcluster? Is this example a good way to go if I want to try something hybrid?

Hi @refraction-ray,
first of all thank you for you interest.
As you have noticed, AWS ParallelCluster is a AWS native tool that uses AWS resources to build an High Performance Computing environment in the cloud.
For an hybrid approach, there may be different solutions depending on the requirements. The one you linked as example could be one, see this blog post as a starting point.
If possible, can you share the size of your on prem cluster and the desired for the cloud one? What is your use case in terms of application that you would like to execute?
L

Hi @lukeseawalker ,
Thanks for your reply.
Currently, we have maintained two mini clusters in our department: one in the size around 30, the other one in the size around 10 nodes (with newer hardwares). One of our computation needs is to do memory consuming computations (such as full diagonalization of large matrix) whose memory requirements might fall into the range of 300G to 2T. These types of numerical tasks don't need too much internodes communications and are insensitive to any start up overheads (diagonalization of one matrix takes several hours, so other overheads in seconds are irrelevant). Therefore, I believe cloud high performance solutions fit well here: 1. powerful hardware spec (extra large memory); 2. very little communication (avoid bottleneck of communication through the Internet for hybrid scheme); 3. insensitive of overheads (the bulk of the task: a single MKL routine dominates the time).
One can argue that there is no need for hybrid solution here as the user can create a pure cloud HPC and submitting the tasks. And this is true in some sense. But I guess there are at least several benefits by utilizing hybrid architecture with master nodes on premises.

The software stacks have already been installed, configured and fine tuned on the master node, so less work is required for the cloud part.
The learning curve is the most smooth for normal users in this scenario, they don't need to know details of cloud computations. They could just submit their jobs by slurm on the on prem cluster as before (at most a switch of slurm partition). And this brings users the most consistent user experience (they don't need to run tasks on two different clusters and check back and forth, instead, all output data files are saved in the same place, either local storage or cloud storage).
Honestly speaking, I am very interested in this solution myself, since I would like to try something challenging and interesting. As I couldn't find much on-line resources of real experience on this topic, I think the architecture itself is very interesting to explore.

Of course, all the above are just my personal thoughts right now. We need some time to try and see what happens.

Thanks, @refraction-ray for giving us some insight into your use cases and workload. While your use case is a very interesting one, AWS ParallelCluster remains for the time being, an AWS-native product without any official support for hybrid architectures.
If you are committed to pursuing a hybrid approach then I would recommend reviewing the blog post that Luca shared in addition to the Slurm plugin you linked to and seeing whether either might fit your use case.
Marking this issue as closed for now.

Wondering if there's been any development for OP's question since it was asked? Curious about a similar setup


Typescript: Add support for class properties and emitDecoratorMetadata

Hello,
switching Typescript transpilation to jiti in Nuxt 2.15.0 has caused some problems with our code base that have prevented us from upgrading:
We are using class-validator to validate data and define our classes like this:
export class SomeModel {
  @IsString()
  @IsDefined()
  public readonly someField!: string;
}

This causes an Error: TRANSFORM_ERROR: Definitely assigned fields cannot be initialized here, but only in the  constructor on Nuxt startup which can be fixed by adding @babel/plugin-proposal-class-properties to the transformation. Somehow, @babel/plugin-syntax-class-properties is already included.
In addition, we are using Nest for our serverMiddleware and have some way to utilize it's dependency injection during server side rendering. Since the dependency injection relies on emitDecoratorMetadata we'd need babel-plugin-transform-typescript-metadata to be added to the transformation.

I am also seeing issues trying to use json2typescript on a model in a Nuxt servermiddleware. I specifically see the error about using proposal-class-properties.
 ERROR  Decorating class property failed. Please ensure that proposal-class-properties is enabled and runs after the decorators transform.

Consdiering you already imported IsString and IsDefined this syntax works:
export class SomeModel {
  @IsString()
  @IsDefined()
  public readonly someField: string;

  constructor(someField: string) {
    this.someField = someField;
  }
}

We also improved decorator meta support for v2.


Many of the Shared Containers are using unnecessary properties.

Many of the Shared Containers are using unnecessary properties for transfering state data, instead of simply using the Redux state object itself.

Fixed with 1b4b14e 🎉


Issue #2900 Cassandra implementation of payload offload including rollback support

we should add fhir-persistence-blob to the list of modules in our README

General question:  are these changes abstracted from the FHIRPersistenceInterceptor or will interceptor implementations need to be aware of changes to the FHIRPersistenceContext object?

General question: are these changes abstracted from the FHIRPersistenceInterceptor or will interceptor implementations need to be aware of changes to the FHIRPersistenceContext and/or event object?
And same question for audit...

Robin confirmed that the context and event objects should be the same as before.  One difference is that the persistence context will now have the offloadPayloadResponse, but that is strictly additive and interceptors should continue to work as expected.


remove unused import

I was looking for opn issues and found this here not being used.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fixes 37

fixes 37

Codecov Report

Merging #52 into master will increase coverage by 0.31%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #52      +/-   ##
==========================================
+ Coverage   95.23%   95.55%   +0.31%
==========================================
  Files          65       65
  Lines         735      742       +7
  Branches      100      100
==========================================
+ Hits          700      709       +9
  Misses         11       11
+ Partials       24       22       -2

Impacted Files
Coverage Δ

lib/models/v3/Sequelize.ts
97.95% <ø> (ø)
:arrow_up:

lib/models/v3/Model.ts
95.23% <100%> (+9.52%)
:arrow_up:

lib/services/models.ts
90.69% <0%> (+0.77%)
:arrow_up:

Continue to review full report at Codecov.

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

closes #37


when replying by mail to a ticket notification does not contain comment

The problem is that get_mail.ticket_from_message does not include the comment in context that is passed to send_templated_mail
So we have to move notifications after adding followup, and in case of an update, add the comment to the context.
This commit fix that: https://github.com/alexgarel/django-helpdesk/commit/db18f648d5b032c53819f086e1126530b4219290

The commit I just pushed (969c0cd) updates Alex's commit to merge cleanly with HEAD as of right now.
Can we get this pulled into your master branch, Ross?
Thanks.

Clsoed by Pull Request #112.


Unable to fetch static asset from endpoint on Cloudflare adapter

Describe the bug
This is the error I'm running into:
500

Fetch API cannot load: /shiki/themes/github-dark.json

TypeError: Fetch API cannot load: /shiki/themes/github-dark.json

Here's a screenshot of the error:

This is a fresh project and I've installed shiki and shx, modified the package.json to copy files into the static folder, and added the following index.ts file:
import * as shiki from 'shiki'
import { base } from '$app/paths'

export async function get() {
  shiki.setCDN(`${base}/shiki/`)
  const highlighter = await shiki.getHighlighter({ theme: 'github-dark' })
  return {
    body: { data: highlighter.codeToHtml(`console.log('shiki');`, { lang: 'js' }) },
  }
}

Here's the scripts I've added to the package.json file:
    "copy": "shx mkdir -p static/shiki && shx cp -r node_modules/shiki/* static/shiki/",
    "predev": "npm run copy",
    "prebuild": "npm run copy",

Source repo for reproduction:
https://github.com/kdheepak/sveltekit-shiki-endpoint-error
Reproduction
Go to https://sveltekit-shiki-endpoint-error.pages.dev/
You'll see the error: Fetch API cannot load: /shiki/themes/github-dark.json. However, the following file exists:
https://sveltekit-shiki-endpoint-error.pages.dev/shiki/themes/github-dark.json
Logs
09:14:08.999	Initializing build environment. This may take up to a few minutes to complete
09:14:11.157	Success: Finished initializing build environment
09:14:11.157	Cloning repository...
09:14:12.912	Success: Finished cloning repository files
09:14:13.234	Installing dependencies
09:14:13.246	Python version set to 2.7
09:14:17.258	Downloading and installing node v17.1.0...
09:14:17.737	Downloading https://nodejs.org/dist/v17.1.0/node-v17.1.0-linux-x64.tar.xz...
09:14:20.124	Computing checksum with sha256sum
09:14:20.258	Checksums matched!
09:14:25.540	Now using node v17.1.0 (npm v8.1.2)
09:14:26.115	Started restoring cached build plugins
09:14:26.131	Finished restoring cached build plugins
09:14:26.847	Attempting ruby version 2.7.1, read from environment
09:14:32.741	Using ruby version 2.7.1
09:14:33.105	Using PHP version 5.6
09:14:33.284	5.2 is already installed.
09:14:33.312	Using Swift version 5.2
09:14:33.313	Started restoring cached node modules
09:14:33.335	Finished restoring cached node modules
09:14:33.806	Installing NPM modules using NPM version 8.1.2
09:14:43.271
09:14:43.271	><EMAIL_ADDRESS>prepare
09:14:43.271	> svelte-kit sync
09:14:43.271
09:14:43.492
09:14:43.493	added 382 packages, and audited 383 packages in 9s
09:14:43.493
09:14:43.493	45 packages are looking for funding
09:14:43.493	  run `npm fund` for details
09:14:43.495
09:14:43.495	found 0 vulnerabilities
09:14:43.508	NPM modules installed
09:14:44.043	Installing Hugo 0.54.0
09:14:44.737	Hugo Static Site Generator v0.54.0-B1A82C61A/extended linux/amd64 BuildDate: 2019-02-01T10:04:38Z
09:14:44.742	Started restoring cached go cache
09:14:44.764	Finished restoring cached go cache
09:14:44.922	go version go1.14.4 linux/amd64
09:14:44.943	go version go1.14.4 linux/amd64
09:14:44.947	Installing missing commands
09:14:44.948	Verify run directory
09:14:44.948	Executing user command: npm run build
09:14:45.430
09:14:45.431	><EMAIL_ADDRESS>prebuild
09:14:45.431	> npm run copy
09:14:45.431
09:14:45.816
09:14:45.817	><EMAIL_ADDRESS>copy
09:14:45.817	> shx mkdir -p static/shiki && shx cp -r node_modules/shiki/* static/shiki/
09:14:45.817
09:14:46.213
09:14:46.214	><EMAIL_ADDRESS>build
09:14:46.214	> svelte-kit build
09:14:46.214
09:14:46.636	vite v2.9.2 building for production...
09:14:46.750	transforming...
09:14:47.321	✓ 13 modules transformed.
09:14:47.396	rendering chunks...
09:14:47.428	.svelte-kit/output/client/_app/manifest.json                    1.14 KiB
09:14:47.430	.svelte-kit/output/client/_app/layout.svelte-23d0f029.js        0.53 KiB / gzip: 0.35 KiB
09:14:47.430	.svelte-kit/output/client/_app/error.svelte-bb9909e1.js         1.56 KiB / gzip: 0.74 KiB
09:14:47.430	.svelte-kit/output/client/_app/pages/index.svelte-dfe298c1.js   0.80 KiB / gzip: 0.47 KiB
09:14:47.430	.svelte-kit/output/client/_app/chunks/index-dd45c2ae.js         6.83 KiB / gzip: 2.79 KiB
09:14:47.431	.svelte-kit/output/client/_app/start-bd943a5d.js                22.63 KiB / gzip: 8.55 KiB
09:14:47.445	vite v2.9.2 building SSR bundle for production...
09:14:47.582	transforming...
09:14:47.874	✓ 13 modules transformed.
09:14:47.897	Generated an empty chunk: "hooks"
09:14:47.903	rendering chunks...
09:14:47.921	.svelte-kit/output/server/manifest.json                        1.37 KiB
09:14:47.921	.svelte-kit/output/server/index.js                             65.50 KiB
09:14:47.921	.svelte-kit/output/server/entries/endpoints/index.ts.js        0.33 KiB
09:14:47.921	.svelte-kit/output/server/entries/fallbacks/layout.svelte.js   0.24 KiB
09:14:47.921	.svelte-kit/output/server/entries/fallbacks/error.svelte.js    0.72 KiB
09:14:47.921	.svelte-kit/output/server/entries/pages/index.svelte.js        0.32 KiB
09:14:47.921	.svelte-kit/output/server/chunks/paths-396f020f.js             0.16 KiB
09:14:47.921	.svelte-kit/output/server/chunks/index-2dc61825.js             2.29 KiB
09:14:47.921	.svelte-kit/output/server/chunks/hooks-1c45ba0b.js             0.00 KiB
09:14:47.944
09:14:47.944	Run npm run preview to preview your production build locally.
09:14:47.947
09:14:47.947	> Using @sveltejs/adapter-cloudflare
09:14:48.105	  ✔ done
09:14:48.131	Finished
09:14:48.131	Note: No functions dir at /functions found. Skipping.
09:14:48.131	Found _worker.js in output directory. Uploading.
09:14:48.154	Validating asset output directory
09:14:48.558	Deploying your site to Cloudflare's global network...
09:14:59.121	Success: Your site was deployed!

System Info
npx envinfo --system --binaries --browsers --npmPackages "{svelte,@sveltejs/*,vite}"

  System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz
    Memory: 336.47 MB / 16.00 GB
    Shell: 5.8 - /usr/local/bin/zsh
  Binaries:
    Node: 17.1.0 - ~/miniconda3/bin/node
    npm: 8.5.3 - ~/miniconda3/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.34
    @sveltejs/kit: next => 1.0.0-next.311
    svelte: ^3.44.0 => 3.47.0

Severity
blocking all usage of SvelteKit
Additional Information
No response

This is expected — you can't fetch a root-relative URL from an endpoint like you can in the browser, because there's no origin. (It appears to work in dev and preview because shiki loads directly from node_modules, ignoring shiki.setCDN, though I don't totally understand what it's doing under the hood.)
Instead, you would have to do this...
import * as shiki from 'shiki';
-import { base } from '$app/paths';

-export async function get() {
-	shiki.setCDN(`${base}/shiki/`);
+export async function get({ url }) {
+	shiki.setCDN(`${url.origin}/shiki/`);
	const highlighter = await shiki.getHighlighter({ theme: 'github-dark' });
	return {
		body: { data: highlighter.codeToHtml(`console.log('shiki');`, { lang: 'js' }) }
	};
}

...except that doesn't work either, apparently because shiki just doesn't want to run on Cloudflare Workers:

I'm not sure if there's a way to make this work, but it might be worth trying to see if you can get shiki to work in a vanilla worker (i.e. no SvelteKit) — at least that way we'll know if the problem is somehow caused by SvelteKit's build process.

FWIW I use Shiki is a static site generation workflow using the static adapter with SvelteKit and that seems to work completely fine.


Remove reference to CanvasLayer in WebXR example, because it can cause rendering issues in AR

Fixes #45505
The WebXR example in the docs recommends putting the "Enter VR" button under a CanvasLayer. While no one has seen this cause issues with VR, it has been shown to cause rendering problems in AR with Android smartphones.
To avoid folks encountering this problem when trying to use WebXR with AR in the future, let's remove that recommendation from the docs!
This should cherry-pick cleanly to Godot 3.2.

Thanks!

Thanks!

Cherry-picked for 3.2.4.


Ponyfills for older browsers

use ponyfills for older browsers

Ponyfill: A polyfill that doesn't overwrite the native method

[x] array-foreach
[x] array-map
[x] array-reduce

Coverage increased (+0.02%) to 98.63% when pulling 436b467b63f380ee5493613768068154973fd664 on ponyfills into 7e68d453b6ceb3e556cf2e2304072ca2f4b102a9 on master.

Coverage increased (+0.02%) to 98.63% when pulling 436b467b63f380ee5493613768068154973fd664 on ponyfills into 7e68d453b6ceb3e556cf2e2304072ca2f4b102a9 on master.


Reflow on mouseenter

When the mouse comes into a major activity, we show a little menu for editing or deleting. This causes reflow of the content, which is annoying.

This is just ugly, not actually breaking anything. Pushing to 0.3.2


Not scrolling on touch screens in Chrome

On Chrome, scroll is not properly responding to touch on touchscreens. It seems to scroll a tiny bit every time I gesture to scroll up or down but it's not an acceptable behavior.
It seems to work OK in Edge but even there, it's very very jumpy but at least it does scroll.
And it's the same issue on the new Chrome based Edge.
Using a mouse, everything works fine but touch produces a very poor experience.

close this issue for we have another for tracking. #92


Added priv pod creation on before suite, updated vendor

@mcornea Hello, the util function (CreatePrivilegedPods) in the helper will be added once a PR is merged in eco-goinfra.

lgtm but let's add the CreatePrivilegedPods function before merging. Thanks.


Literally error in every install.

From here to anywhere, it's full of errors. I don't know why.
I'm using Python 3.10.6 with pip 22.2.2
Fails to install Spacy.
Or maybe it uses an outdated packages or something that newer versions of Python is incompatible with.
I seen a lot of issues similar to this so I think this should be fixed sooner.
Please.

Try this:
https://github.com/gunthercox/ChatterBot/issues/2262#issuecomment-1210893149


Trying to test

Hi guys, i am trying to reproduce the Getting Started guide but didnt succeed
I cloned and installed all dependencies by: npm install
then, in the root folder: mern/  i run: ~/mern$ npm run server:dev
but i am getting this error:
><EMAIL_ADDRESS>server:dev /home/pedro/Desktop/Web/e-commerce/mern
> nodemon NODE_ENV=development --inspect bin/server.js

  Usage: nodemon [nodemon options] [script.js] [args]

  See "nodemon --help" for more.

There is any thing i am doing wrong?

hi, thanks for the issue,
nodemon did some breaking release since I last worked on this project.
Could you try downgrading your nodemon version, maybe to 1.19.4.

hello @anikethsaha , i will try downgrading it and let you know asap.
thanks!


⚠ ClamAV has degraded performance

In 26b6b4f, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 614 ms

Resolved: ClamAV performance has improved in 0098811 after 13 minutes.


Optimised version of fused classifier + bugfixes(?)

This is a faster version of the cool new kernel from #117 (still /dev/cuda/ only). The biggest difference is it is optimised for doing one row per 1024-wide block rather than per 32-wide warp, which massively reduces the amount of data in-flight, and this allows us to basically always hit in the L2 cache for the 2nd read and this saves a huge amount of DRAM bandwidth. It also uses 128-bit loads which implicitly requires V to be a multiple of 4.
However, I believe the validation in classifier_fused.cu is currently not working correctly, possibly because the distribution of inputs results in all probabilities being ~zero, which is something I think ngc92 has a fix for.
Finally, I changed both old and new kernels to write to the gradient tensor, rather than modify it (read-modify-write) which costs us an extra DRAM access. I don't think accumulating gradients is required for this part of the network. All performance numbers below are with this change including Kernel1.
Performance:
Fused Kernel1 (old, block size invariant): ~6ms
Fused Kernel2 (new, 1024 threads per block): ~3.7ms
Forward Softmax Kernel7 (512 threads per block): 5.7ms (current default used in train_gpt2.cu)
Forward Softmax Kernel7 (1024 threads per block): ~3.7ms (optimal block size, got it wrong in my original PR for kernel7)

oops this PR now conflicts because I merged the other one. Sounds good, agree it is ok to skip += here, but I think it should come with a comment on this subtle issue. Please add a brief one, or I'm also ok adding after.

Should be ready to be merged again now (at least to /dev/cuda/)!
I made it more flexible so it can now also work as a forward-only option by passing a pointer to "probs" and making "dlogits" NULL instead.
Combined with the bounds checking it's making the code a bit longer than I'd like, and with a bit more overhead in terms of GPU instructions, but given it's massively DRAM limited it seems maybe worth it to only have one function doing everything?


Yaml config support

Add support for using a yaml file instead of json using the std/encoding module.

Closing as it is already implemented in rework branch.


Fail to load more than one Banner ad on  GridView

getting Ad failed to load : 3 when using BannerAd inside GridView.builder
outside it it works fine

when I used NativeAd instead ad BannerAd  it works fine

You're using adaptive banner? There must be enough space to load the banner

Hey! Do you still see this issue?


The SDK assets retire method is not working

Seems to be a marketplace-api problem, assigning @dancespiele


⚠ Jenkins Plugins Artifactory has degraded performance

In 2720858, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1025 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 418b742 after 43 minutes.


Large Image File/Size Upload Fails - Small Image File/Size Upload Success - iOS or Android

Summary
Large Image upload fails from mobile app. iOS or Android. Reduced image size uploads successfully.
Environment Information

Device Name: Raspberry Pi 4B+ ::: 4GB Ram
OS Version: Ubuntu 21.04 64Bit
Kernel: Linux 5.11.0-1017-raspi
Architecture: arm64
Mattermost Server Version: 6.0.2 (Build dev-linux-arm-v6.0.2)
Apache2 Reverse Proxy

Mobile Device for Testing

Device Name: Samsung Galaxy Z Fold 3
OS Version: Android 12
Mattermost App Version: 1.47.2 (Build 3000377)

Steps to reproduce
From the mobile app, open any chat/channel and attempt upload a photo sized 4000 x 3000 (or larger) ~2.4Mb.
Expected behavior
Expect the upload to succeed and then to post the image.
Observed behavior (that appears unintentional)
For a while a blue progress bar appears across the bottom of the thumbnail. After some time a 'retry' symbol appears on the image thumb.
If you press "send" you are informed that the image was not uploaded and asked if you want to send the message anyway.
NOTE: If the image is resized to 20% or less of its original size, the upload completes successfully.
This issue persist on iOS or Android. Indiscriminate.
Additional Details
File uploads for the same failing content on the mobile app uploads successfully via PC or Mobile Web Browser.
Uploads from Mattermost Classic App work successfully.

@trbolexis

Do you or your admin have access to check if there are any errors in the server logs?
Has this issue happened in previous versions?
Do you see the same issue on our community server https://community.mattermost.com/?

Thank you for the comment.

I do have admin login, and I am also unsure of details found in the logs. Nothing stands out to me, but I am no expert: https://pastebin.com/dCQEqRrZ
This is my first installation/implementation of Mattermost (self-hosted), So I am unable to speak about previous versions.
I did NOT experience the same issue uploading to the community,mattermost.com server in my testing a moment ago.

This does seem to indicate a server issue, right?

Reviving this issue as I have the same problem and (nearly) same setup.
Environment Information

Device Name: Raspberry Pi 4B+ ::: 4GB Ram
OS Version: Ubuntu 21.04 64Bit Raspberry Pi OS 32bit
Kernel: Linux 5.11.0-1017-raspi 5.10.103-v7l+
Architecture: arm64
Mattermost Version: dev-linux-arm-v6.6.0
Database Schema Version: 78
Database: mysql
Apache2 Reverse Proxy

Mobile Device for Testing

Device Name: Iphone SE 2nd gen
OS Version: ios 15.4.1
Mattermost App Version:  1.51.0 (B391)

nothing interesting in the logs except some DEBUG messages about non-existent plugins (com.mattermost.apps and com.mattermost.calls)
Happy to poke around the server if there are any good ideas.

@yukdumboobumm We have seem issues like this before that had to do with the configuration of NGINX regarding timeouts. Could this be the issue here? (i.e. since it takes so long to upload the file, nginx just timeout the connection)

I am experiencing the same issue on multiple iOS devices when using the app to upload e.g. a 30 sec video or multiple images simultaneously. The error in the app is URLSessionTask failed with error: The request timed out.
I am certain that the app is the problem and not the reverse proxy since uploading using the browser works perfectly fine.
App Version: 2.4.0 (Build 471)
Server Version: 7.8.6
OS: Ubuntu Jammy 64bit
Architecture: amd64
Reverse proxy: Caddy

Same here, I also timed it at exactly 30 secs. No reverse proxy, same error message...

I think I pinpointed the issue. Will let you know when it is fixed.

Looking forward to it. Clients are restless.

@xmoov The fix should be available in 2.7 (August release). It will probably be available in next Wednesday beta, so I would appreciate if you could verify the fix then.

@larkox I find it hard to believe that this fix resolves the actual issue. Maybe for @xmoov, but I’m having upload problems on iOS, and the OP also specifically states «This issue persist on iOS or Android. Indiscriminate.»

@larkox I find it hard to believe that this fix resolves the actual issue. Maybe for @xmoov, but I’m having upload problems on iOS, and the OP also specifically states «This issue persist on iOS or Android. Indiscriminate.»

@helgehatt is the statement true when trying on our community server?

@enahum Okay, so I’ve tested on the community server now, and uploading a two minute video or ten images works fine and is much faster than on my server. However, when trying to upload multiple videos I get the exact same error. To me it seems like you can get away with bigger file sizes with higher upload bandwidth, but the underlying issue persists regardless. I’m getting the error when uploading four one minute videos. Should be fairly easy for you to reproduce the error yourselves.

I bet that if I was in an area with bad cellular reception (read: low upload bandwidth) I wouldn’t be able to upload a single one minute video to the community server either.

I bet that if I was in an area with bad cellular reception (read: low upload bandwidth) I wouldn’t be able to upload a single one minute video to the community server either.

Did you time how long it took to fail? Was it 30 as previously reported?

I bet that if I was in an area with bad cellular reception (read: low upload bandwidth) I wouldn’t be able to upload a single one minute video to the community server either.

Did you time how long it took to fail? Was it 30 seconds as previously reported?

@eric-benjamin It’s definitely not exactly 30 seconds. Somewhere between 30-40 seconds, and the uploads doesn’t necessarily fail at the same time.

I can send a screen capture if that would help.

Right now I’m in an area with mediocre cellular reception (about 10Mbps upload speed), and I am no longer able to upload ten images to the community server.
https://github.com/mattermost/mattermost-mobile/assets/12933913/a06b9d67-654c-45d1-8a52-bfbc7f711b3e

@larkox would you say this would be fixed with the recent changes about the timeout defaults?

@enahum Should be, yes.


Changed the project to a gradle java project

The project structure has undergone significant changes. It is recommended to directly review all code in the IDE, and it is not recommended to review code by comparing differences.


I am using Kubernetes for deployment, but not able to retain data

Describe the bug
I am using Kubernetes for deployment but afraid if the node goes down my data will be lost, I want to retain data for last one week, by somehow mounting of volume.
I am using your base image and only specifying the yaml configuration as I am not able to go in the Image/container. I wanted to know does gatus exposes some functionality for this or not..
What do you see?
I am using Kubernetes for deployment but afraid if the node goes down my data will be lost, I want to retain data for last one week, by somehow mounting of volume.
What do you expect to see?
I want to retain the data even if node goes down
List the steps that must be taken to reproduce this issue
Just kill the node and data is gone
Version
latest
Additional information
pls comment ASAP, need this on enterprise level

The docs have this full explanation about it. You can configure an external database and for the production environment the basis is to use a CSI with HA in those disks. If your cluster goes down the storage still intact

@antikilahdjs I can see some examples for using storage with docker compose configuration, could you pls point out if there's any documentation for using storage with Kubernetes.

I have tried with below deployment yaml which have postgres DB container with PVC but still data is not retaining when gatus pod goes down. Anyone tried to deploy gatus tool with PVC to retain health chks api data?
apiVersion: v1
kind: ConfigMap
metadata:
name: gatus
namespace: kube-system
data:
storage.yaml: |
type: postgres
path: "postgres://username:password@postgres:5432/gatus?sslmode=disable"
config.yaml: |
metrics: true
endpoints:
- name: website
url: https://twin.sh/health
interval: 5m
conditions:
- "[STATUS] == 200"
- "[BODY].status == UP"
  - name: github
    url: https://api.github.com/healthz
    interval: 5m
    conditions:
      - "[STATUS] == 200"

  - name: cat-fact
    url: "https://cat-fact.herokuapp.com/facts/random"
    interval: 5m
    conditions:
      - "[STATUS] == 200"
      - "[BODY].deleted == false"
      - "len([BODY].text) > 0"
      - "[BODY].text == pat(*cat*)"
      - "[STATUS] == pat(2*)"
      - "[CONNECTED] == true"

  - name: example
    url: https://example.com/
    conditions:
      - "[STATUS] == 200"

apiVersion: v1
kind: ServiceAccount
metadata:
name: gatus
namespace: kube-system
apiVersion: apps/v1
kind: Deployment
metadata:
name: gatus
namespace: kube-system
spec:
replicas: 1
selector:
matchLabels:
app: gatus
template:
metadata:
name: gatus
namespace: kube-system
labels:
app: gatus
spec:
serviceAccountName: gatus
terminationGracePeriodSeconds: 5
containers:
- env:
- name: POSTGRES_DB
value: gatus
- name: POSTGRES_USER
value: username
- name: POSTGRES_PASSWORD
value: password
image: postgres
imagePullPolicy: Always
name: postgres
ports:
- containerPort: 5432
protocol: TCP
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /var/lib/postgresql
name: gatus-db
- image: twinproduction/gatus
imagePullPolicy: IfNotPresent
name: gatus
ports:
- containerPort: 8080
name: http
protocol: TCP
resources:
limits:
cpu: 250m
memory: 100M
requests:
cpu: 50m
memory: 30M
readinessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 5
periodSeconds: 10
successThreshold: 1
failureThreshold: 3
livenessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 1
failureThreshold: 5
volumeMounts:
- mountPath: /config
name: gatus-config
volumes:
- configMap:
name: gatus
name: gatus-config
- name: gatus-db
persistentVolumeClaim:
claimName: gatus  ### created an EBS based PVC
apiVersion: v1
kind: Service
metadata:
name: gatus
namespace: kube-system
spec:
ports:
- name: http
port: 8080
protocol: TCP
targetPort: 8080
selector:
app: gatus`

Hello,
I don't if I got it but it is about gatus or pvc? For example, in gatus doc it is possible to point it to postgres and I did it before and works fine but I've decided put it in my CSI because I have the PROD environment with WEKA then I have a large storage replication with the same point of access.
If you use the OpenEBS for example it will mount in each node and in that case if the server crash you will lose it .
Today I using this configuration below.
  storage:
  caching: false
  path: /data/gatus.db
  type: sqlite

Inside of the pod the path is /data but for in my CSI is /data/weka and all my gatus has a PVC attached then my data will be instacted, it is the normal way for all deployment and so on
If you need put it in own database the gatus just support postgres
storage:
  type: postgres
  path: "postgres://user:password@<IP_ADDRESS>:5432/gatus?sslmode=disable"

Can you format your configuration properly? (Wrap it using ```)
At a glance, it seems like the problem has to do with your storage configration.
It should be
storage:
  type: postgres
  path: "postgres://username:password@postgres:5432/gatus?sslmode=disable"

But instead, you're putting it in a storage.yaml file:
storage.yaml: |
  type: postgres
  path: "postgres://username:password@postgres:5432/gatus?sslmode=disable"

Can you format your configuration properly? (Wrap it using ```)
At a glance, it seems like the problem has to do with your storage configration.
It should be
storage:
  type: postgres
  path: "postgres://username:password@postgres:5432/gatus?sslmode=disable"

But instead, you're putting it in a storage.yaml file:
storage.yaml: |
  type: postgres
  path: "postgres://username:password@postgres:5432/gatus?sslmode=disable"

I have tried with below config as u suggested but still data is not retaining. Any other suggestions? i have updated the complete  using code in my previous post.
  storage: |
    type: postgres
    path: "postgres://username:password@postgres:5432/gatus?sslmode=disable"```

It's because you're not formatting the configuration properly.
It should look like this:
kind: ConfigMap
metadata:
  name: gatus
  namespace: kube-system
data:
  config.yaml: |
    metrics: true

    storage:
      type: postgres
      path: "postgres://username:password@postgres:5432/gatus?sslmode=disable"

    endpoints:
      - name: website
        url: https://twin.sh/health
        interval: 5m
        conditions:
          - "[STATUS] == 200"
          - "[BODY].status == UP"

      - name: github
        url: https://api.github.com/healthz
        interval: 5m
        conditions:
          - "[STATUS] == 200"


Thread leak (and likely memory leak) on Logstash reload

When Logstash pipelines are reloaded via the a configuration change, the rufus jobs thread is not shut down.
Profiling via YourKit (filtering live threads by rufus):
After 1 reload:

After another reload:

..and another reload:

The root cause here is that the rufus stop/shutdown is defined as:
    def shutdown(opt=nil)

      @started_at = nil

      #jobs.each { |j| j.unschedule }
        # provokes https://github.com/jmettraux/rufus-scheduler/issue/98
      @jobs.array.each { |j| j.unschedule }

      @work_queue.clear

      if opt == :wait
        join_all_work_threads
      elsif opt == :kill
        kill_all_work_threads
      end

      unlock
    end

...but we are not sending any options to the shutdown method, so the worker threads never get killed. Any objects associated with that thread would considered to be a memory leak. ...pure subjecture is that JDBC drivers may use thread locals to hold cached state which could lead to a decent memory leak over time and volume

The fix here is to add the :wait option to the shutdown when reloading a pipeline.
With the fix after a couple reloads:


fix(frontend): fix responsiveness issues

fixes #39, fixes #37, fixes #32

@Samy-33, Please review this.

Why aren't the folks from 2021 batch contributing to these? These were really easy issues to get them started.

I told the 2021 batch to contribute multiple times but there was little to no response. We can't just force them to contribute.

Also, there's already a PR for https://github.com/BitByte-TPC/TPC-website/issues/32, shouldn't we help the author of that PR to get it merged?

That PR is inactive for the last 10 days.

I told the 2021 batch to contribute multiple times but there was little to no response. We can't just force them to contribute.

It's not about forcing them to contribute, it's more of a concern that why aren't they participating in these activities, which are going to benefit them the most. Let's discuss about this on Discord.

That PR is inactive for the last 10 days.

I think we should first ask the author of the PR if they are still interested in working on the issue and if they are not or don't respond in a reasonable amount of time, we can move ahead without that PR.

Okay, will remember next time.


podman push: 500 Internal Server Error with Harbor

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Unable to push images with podman to Harbor registry created through Bitnami helm chart. Every push is met with 500 Internal Service Error. Issue does not occur when using Docker to push.
Steps to reproduce the issue:

Deploy Bitnami Harbor Chart

Setup Ingress accordingly

Push image to Harbor registry

Describe the results you received:
Writing manifest to image destination
Copying blob 99b5261d397c skipped: already exists
Copying blob 2a8e1e567b0b skipped: already exists
DEBU[0000] ... already exists
Copying blob 99b5261d397c skipped: already exists
Copying blob 99b5261d397c skipped: already exists
Copying blob 2a8e1e567b0b skipped: already exists
Copying blob 99b5261d397c skipped: already exists
Copying blob 2a8e1e567b0b skipped: already exists
Copying blob d05f202848f3 skipped: already exists
Copying blob 0c6f7f5f6419 skipped: already exists
Copying blob e4102d5e6f43 [--------------------------------------] 0.0b / 0.0b
DEBU[0000] exporting opaque data as blob "sha256:3a8ef3de58ba30e71b027b89ed740a407a2bf5ea10e20395d7762cbccd990456"
DEBU[0000] No compression detected
DEBU[0000] Using original blob without modification
DEBU[0000] Checking /v2/library/sonarr/blobs/sha256:3a8ef3de58ba30e71b027b89ed740a407a2bf5ea10e20395d7762cbccd990456
DEBU[0000] HEAD https://harbor.svc.example.com/v2/library/testapp/blobs/sha256:3a8ef3de58ba30e71b027b89ed740a407a2bf5ea10e20395d7762cbccd990456
DEBU[0000] ... already exists
Writing manifest to image destination
DEBU[0000] PUT https://harbor.svc.example.com/v2/library/testapp/manifests/latest
DEBU[0000] Writing manifest using preferred type application/vnd.oci.image.manifest.v1+json failed: Error writing manifest: Error uploading manifest latest to harbor.svc.example.com/library/testapp: received unexpected HTTP status: 500 Internal Server Error
ERRO[0000] Error copying image to the remote destination: Error writing manifest: Error uploading manifest latest to harbor.svc.example.com/library/testapp: received unexpected HTTP status: 500 Internal Server Error

Describe the results you expected:
Writing manifest to image destination
Storing signatures

Additional information you deem important (e.g. issue happens only occasionally):
Attempted with podman 1.7.0 from Fedora 30 rpm and podman 1.8.2 built from source. Same error.
Output of podman version:
podman version 1.8.2

Output of podman info --debug:
debug:
  compiler: gc
  git commit: 028e3317eb1494b9b2acba4a0a295df80fae66cc
  go version: go1.12.15
  podman version: 1.8.2
host:
  BuildahVersion: 1.14.3
  CgroupVersion: v1
  Conmon:
    package: conmon-2.0.10-2.fc30.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.10, commit: 35d9b09d9d2791c7167091a9f25792535a380967'
  Distribution:
    distribution: fedora
    version: "30"
  MemFree: 583499776
  MemTotal:<PHONE_NUMBER>
  OCIRuntime:
    name: runc
    package: runc-1.0.0-102.dev.gitdc9208a.fc30.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc10
      commit: ffa084d279c26351e6e63bd2c3f28d43fa1f6e57
      spec: 1.0.1-dev
  SwapFree: 0
  SwapTotal: 0
  arch: amd64
  cpus: 2
  eventlogger: journald
  hostname: kube-master.gaia-project.net
  kernel: 5.4.17-100.fc30.x86_64
  os: linux
  rootless: false
  uptime: 19h 37m 5.17s (Approximately 0.79 days)
registries:
  search:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 42
  GraphDriverName: overlay
  GraphOptions:
    overlay.mountopt: nodev,metacopy=on
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  ImageStore:
    number: 62
  RunRoot: /var/run/containers/storage
  VolumePath: /var/lib/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.7.0-3.fc30.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
Virtual machine on ESXi

Are you building your own images, if so then maybe the Harbor registry does not support OCI images?
You can build your images with the --format docker and see if the images are accepted then.
podman build --format docker ...
man podman build
...
       --format

       Control  the  format  for  the  built image's manifest and configuration data.  Recognized formats
       include oci (OCI image-spec v1.0, the default) and docker (version 2, using schema  format  2  for
       the manifest).

       Note: You can also override the default format by setting the BUILDAH_FORMAT environment variable.
       export BUILDAH_FORMAT=docker

If this is true,could you contact the Harbor people and ask them to support the standard format?

That worked, I'll need to prune the old images as rebuilding them does not appear to generate the new manifest (easy fix). I will open an issue with goharbor and cite this one as the cause is definitely related to the oci manifest. Thanks!


Don't send AOS notifications if case is in Awaiting Conditional Order

Change description
As case is already in Awaiting CO, we don't need to notify them of next steps.
Prod error.

MIght need more thought, as the submit AOS service can alter the state of an application, moving it back to Holding. Faisal is looking into that though, so this PR will remain open incase it's needed.

Closing as it seems this isn't needed. If an issue ever arises again, they should be able to find this PR with the closed PR search.


[Bug]: Permission Set Open Permissions

Describe the issue
In same cases where the permission set name is 19 or 20 characters the user gets an error when from Permission Sets Page selects Action "Permission".

Expected behavior
Open permissions
Steps to reproduce
Create a permssion set with 19 or 20 chars long name and select permissions
Additional context
the problem lies here in function GetSourceForLinkedPermissionSet
the parameter of the function is code[20] but the input in same cases is the filltered value of the permission set name including '' so making the total lenght beoyond 20 chars.

That looks like a product defect and must hence get reported to support, to ensure it is addressed within the right SLA and in all supported versions of Business Central.
This repository is only for Business Central extensibility requests or code contributions towards the 1st party Business Central apps.

Can you please guide me or send me the link for reporting the bug to support?

To file a support case please visit:
On premises - https://support.microsoft.com/en-us/supportforbusiness/productselection?sapId=93d37907-ad94-d591-22e9-593cfa09dd3f
Cloud – contact your partner, or if you are a partner open a support incident through Partner Center - https://partner.microsoft.com/en-us/pcv/dashboard/overview


Flipkart plus page is blank BUG:

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I would like to work on this page.. please give the overview on what to do? please assign this task to me
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Go ahead @SuhainaFathimaM

#500 Resolves this issue


Discovery endpoint shows pairwise subject identifier is supported but it is not

Even though the  well known endpoint documentation[1], mentions the subject_types_supported as "pairwise", it is not supported currently in the solution.
[1] https://docs.wso2.com/display/IS570/OpenID+Connect+Discovery

When calling the oidc discovery endpoint https://localhost:9443/oauth2/oidcdiscovery/.well-known/openid-configuration the following is available in the response.
"subject_types_supported": [
        "pairwise"
    ],


Typo in Deploy.ps1

Line 909 in 3_Deploy.ps1 has "some some"

THX! Great to see someone is reading the scripts 👍 . In next push it will be fixed!

I’m trying the S2D scenario but I cannot find any instructions after Deploy.ps1, can you help?
From: Jaromir Kaspar<EMAIL_ADDRESS>Sent: Wednesday, July 12, 2017 1:38 PM
To: Microsoft/ws2016lab<EMAIL_ADDRESS>Cc: Walid AlMoselhy<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/ws2016lab] Typo in Deploy.ps1 (#45)
THX! Great to see someone is reading the scripts 👍 . In next push it will be fixed!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/ws2016lab/issues/45#issuecomment-314743268, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATkLo9kyEu8yiuY0056zpIyTJJusntcEks5sNK_6gaJpZM4OVfGM.

Login to dc and paste the scenario script. As shown here https://m.youtube.com/results?q=ws2016lab&sm=1 - video number 3.

This is MAGIC! Thanks man, will spend many hours learning from this script.
From: Jaromir Kaspar<EMAIL_ADDRESS>Sent: Wednesday, July 12, 2017 3:11 PM
To: Microsoft/ws2016lab<EMAIL_ADDRESS>Cc: Walid AlMoselhy<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/ws2016lab] Typo in Deploy.ps1 (#45)
Login to dc and paste the scenario script. As shown here https://m.youtube.com/results?q=ws2016lab&sm=1 - video number 3.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/ws2016lab/issues/45#issuecomment-314764232, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATkLo2Jg3U4gBEdVUTvijhLzeYq1Uz0-ks5sNMXYgaJpZM4OVfGM.

Happy to help! I wrote it this way, so anyone can learn from it. I also write labs for Microsoft Premier workshops for SDS and Hyper-V, so if you can attend, you will see labguides based on these scripts. If you like this, please show it to your peers. Jaromir


(WIP) Sphinx documentation

(not really ready for review yet)
This PR brings Sphinx documentation (#1656).
Sphinx docs are added to documentation/sphinx, with an introduction, installation instructions, getting started instructions, concepts, command-line and API (for what exists in spinalcordtoolbox namespace...) references, a link to support resources, and some development notes (the release procedure should be there, but I can't find it).
The code is (not yet) modified for docstrings to be parsed by Sphinx.

@perone @jcohenadad @charleygros I'm not requesting a review for merging, just take a look and comment.
As .travis.yml does:
cd documentation/sphinx
make html

Sure, I'll take a look tonight !

Notes:

@jcohenadad I tried to make a short intro, rewording the README's and not repeating it, but it kind of sucks;
@perone / @charleygros I added something in concepts, on the segmentation tools (“deepseg_sc work well but you may try propseg...”) and further information on that would be nice, I'm certain.

@jcohenadad There's a lot of stuff on SourceForge that should probably end up being in Sphinx, with redirects in place on SF, and for now the reverse is done. It looks like some info is obsolete.

@benjamindeleener if the "advanced propseg" info on SF is up-to-date, I can convert it to reST and include it quickly. Or I can just let you do it.

Looks fine to me, just some issues I found:

It might be better to add the sphinx and contrib dependencies in the setup.py
We just need to be careful to not confuse users with two documentation sites, so we should move everything from SourceForge to ReadTheDocs or put a warning on the ReadTheDocs that it is still in development and pointing to the SourceForge docs, or another approach that can avoid this problem;
In my opinion there are too many installation procedures, I don't know if the section "Hard-core Installation-less SCT usage" is worth, because it is too technical, maybe another section for Developers would be better suited for this section;
I got these errors during the make html:

Probably because of these errors, the Alabaster theme doesn't get rendered well in Chrome, it seems that there some issues with the padding/margin, but ir definitely doesn't look the original Alabaster rendering. For instance, in an old project that I have the Alabaster gets rendered like this, but on SCT I got something like this:

It looks like everything was shifted to the left and there is no margin/padding.

During the installation procedure, I got the following error, I don't know if it is something with my environment or with this branch, but just in case here is the error:

The CSS of Alabaster has a fixed width of 940 pixels and as I'm allergic to fixed widths (it looks bad when resizing windows), I disabled it, which does cause the stuff to go to the left. This can be reverted by removing the conf.py edit in 5c0a7017. In the command-line section, everything was cropped for no reason without disabling the fixed width...

The msct_parser message was fixed in the #1680  PR. I don't know where it comes from but it's been here for a while.

I'm not against putting sphinx in setup.py, if it's an extra.

As for the switch-over to wherever the new docs would be, yeah we'd have to make the new stuff better to the old one before switching, and anything on SF should point to its new version.

 Since sphinx was not installed, i wanted to install it from the Python of SCT (to stay in the same environment). That's what i did:
cd $SCT_DIR
git fetch
git checkout -b cJ-sphinx origin/cJ-sphinx
SCT_INSTALL_TYPE=in-place add_to_path=no change_default_path=yes ./install_sct -d -b -m
cd documentation/sphinx
make html
--> /usr/bin/python: No module named sphinx
--> make: *** [html] Error 1
pip install sphinx
make html
--> Running Sphinx v1.7.3
--> Extension error:
--> Could not import extension sphinxcontrib.programoutput (exception: No module named programoutput)
--> make: *** [html] Error 2

@zougloub did you added the dependencies as extra ?
@jcohenadad try running: pip install sphinxcontrib-programoutput to check if it solves the dependency problem. But I think that @zougloub will add it into the setup.py so we don't have to install it manually.

There's something important to consider: Sphinx docs are usually generated from the source tree, and are importing the code. Meaning you have to have SCT deps installed to run sphinx; this can be installed by installing SCT and using the SCT python environment to run Sphinx, from the source directory.
The deps were added as extra docs and aren't installed by default; to install them:
$ PATH="${SCT_DIR}/python/bin:$PATH" # we probably want to use SCT's installed python interpreter
$ pip install ${SCT_SOURCE_DIR}[docs] # re-install with extras

@zougloub, sorry it still doesn't work for me. That's what i did:
git checkout cJ-sphinx
git pull --rebase
source python/bin/activate  # to use SCT python
pip install -e .  # install
PATH="${SCT_DIR}/python/bin:$PATH"
pip install ${SCT_SOURCE_DIR}[docs]

julien-macbook:~/code/sct $ git checkout cJ-sphinx
Already on 'cJ-sphinx'
Your branch is up-to-date with 'origin/cJ-sphinx'.
julien-macbook:~/code/sct $ git pull --rebase
remote: Counting objects: 5, done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 5 (delta 4), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (5/5), done.
From github.com:neuropoly/spinalcordtoolbox
   80ce314..1f74c9f  cJ-sphinx  -> origin/cJ-sphinx
First, rewinding head to replay your work on top of it...
Fast-forwarded cJ-sphinx to 1f74c9fb99f9bfbd9a7df5be83fd33845c6c145a.
julien-macbook:~/code/sct $ source python/bin/activate
(root) julien-macbook:~/code/sct $ pip install -e .
Obtaining file:///Users/julien/code/sct
Requirement already satisfied: futures==3.2.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: nipy==0.4.1 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: nibabel==2.1.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: dipy==0.11.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: tqdm==4.11.2 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: tensorflow==1.3.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: Keras==2.0.6 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: h5py==2.7.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: pytest==3.5.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: pytest-cov==2.5.1 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: sympy>=0.7.0 in ./python/lib/python2.7/site-packages (from nipy==0.4.1->spinalcordtoolbox===dev)
Requirement already satisfied: scipy>=0.9 in ./python/lib/python2.7/site-packages (from dipy==0.11.0->spinalcordtoolbox===dev)
Requirement already satisfied: six>=1.10.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: tensorflow-tensorboard<0.2.0,>=0.1.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: mock>=2.0.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: numpy>=1.11.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: protobuf>=3.3.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: backports.weakref>=1.0rc1 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: wheel in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: theano in ./python/lib/python2.7/site-packages (from Keras==2.0.6->spinalcordtoolbox===dev)
Requirement already satisfied: pyyaml in ./python/lib/python2.7/site-packages (from Keras==2.0.6->spinalcordtoolbox===dev)
Requirement already satisfied: pluggy<0.7,>=0.5 in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: attrs>=17.4.0 in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: funcsigs; python_version < "3.0" in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: setuptools in ./python/lib/python2.7/site-packages/setuptools-23.0.0-py2.7.egg (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: py>=1.5.0 in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: more-itertools>=4.0.0 in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: coverage>=3.7.1 in ./python/lib/python2.7/site-packages (from pytest-cov==2.5.1->spinalcordtoolbox===dev)
Requirement already satisfied: mpmath>=0.19 in ./python/lib/python2.7/site-packages (from sympy>=0.7.0->nipy==0.4.1->spinalcordtoolbox===dev)
Requirement already satisfied: markdown>=2.6.8 in ./python/lib/python2.7/site-packages (from tensorflow-tensorboard<0.2.0,>=0.1.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: html5lib==0.9999999 in ./python/lib/python2.7/site-packages (from tensorflow-tensorboard<0.2.0,>=0.1.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: bleach==1.5.0 in ./python/lib/python2.7/site-packages (from tensorflow-tensorboard<0.2.0,>=0.1.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: werkzeug>=0.11.10 in ./python/lib/python2.7/site-packages (from tensorflow-tensorboard<0.2.0,>=0.1.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: pbr>=0.11 in ./python/lib/python2.7/site-packages (from mock>=2.0.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Installing collected packages: spinalcordtoolbox
  Found existing installation: spinalcordtoolbox dev
    Uninstalling spinalcordtoolbox-dev:
      Successfully uninstalled spinalcordtoolbox-dev
  Running setup.py develop for spinalcordtoolbox
Successfully installed spinalcordtoolbox
You are using pip version 9.0.1, however version 10.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
(root) julien-macbook:~/code/sct $ pip install -e .
(root) julien-macbook:~/code/sct $ PATH="${SCT_DIR}/python/bin:$PATH"
(root) julien-macbook:~/code/sct $ pip install ./[docs]
Processing /Users/julien/code/sct
  Requirement already satisfied (use --upgrade to upgrade): spinalcordtoolbox===dev from file:///Users/julien/code/sct in /Users/julien/code/sct
Requirement already satisfied: futures==3.2.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: nipy==0.4.1 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: nibabel==2.1.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: dipy==0.11.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: tqdm==4.11.2 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: tensorflow==1.3.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: Keras==2.0.6 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: h5py==2.7.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: pytest==3.5.0 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: pytest-cov==2.5.1 in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: sphinx in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: sphinxcontrib-programoutput in ./python/lib/python2.7/site-packages (from spinalcordtoolbox===dev)
Requirement already satisfied: sympy>=0.7.0 in ./python/lib/python2.7/site-packages (from nipy==0.4.1->spinalcordtoolbox===dev)
Requirement already satisfied: scipy>=0.9 in ./python/lib/python2.7/site-packages (from dipy==0.11.0->spinalcordtoolbox===dev)
Requirement already satisfied: six>=1.10.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: tensorflow-tensorboard<0.2.0,>=0.1.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: mock>=2.0.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: numpy>=1.11.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: protobuf>=3.3.0 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: backports.weakref>=1.0rc1 in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: wheel in ./python/lib/python2.7/site-packages (from tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: theano in ./python/lib/python2.7/site-packages (from Keras==2.0.6->spinalcordtoolbox===dev)
Requirement already satisfied: pyyaml in ./python/lib/python2.7/site-packages (from Keras==2.0.6->spinalcordtoolbox===dev)
Requirement already satisfied: pluggy<0.7,>=0.5 in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: attrs>=17.4.0 in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: funcsigs; python_version < "3.0" in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: setuptools in ./python/lib/python2.7/site-packages/setuptools-23.0.0-py2.7.egg (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: py>=1.5.0 in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: more-itertools>=4.0.0 in ./python/lib/python2.7/site-packages (from pytest==3.5.0->spinalcordtoolbox===dev)
Requirement already satisfied: coverage>=3.7.1 in ./python/lib/python2.7/site-packages (from pytest-cov==2.5.1->spinalcordtoolbox===dev)
Requirement already satisfied: Pygments>=2.0 in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: requests>=2.0.0 in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: docutils>=0.11 in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: snowballstemmer>=1.1 in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: alabaster<0.8,>=0.7 in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: Jinja2>=2.3 in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: sphinxcontrib-websupport in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: imagesize in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: babel!=2.0,>=1.3 in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: typing; python_version < "3.5" in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: packaging in ./python/lib/python2.7/site-packages (from sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: mpmath>=0.19 in ./python/lib/python2.7/site-packages (from sympy>=0.7.0->nipy==0.4.1->spinalcordtoolbox===dev)
Requirement already satisfied: markdown>=2.6.8 in ./python/lib/python2.7/site-packages (from tensorflow-tensorboard<0.2.0,>=0.1.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: html5lib==0.9999999 in ./python/lib/python2.7/site-packages (from tensorflow-tensorboard<0.2.0,>=0.1.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: bleach==1.5.0 in ./python/lib/python2.7/site-packages (from tensorflow-tensorboard<0.2.0,>=0.1.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: werkzeug>=0.11.10 in ./python/lib/python2.7/site-packages (from tensorflow-tensorboard<0.2.0,>=0.1.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: pbr>=0.11 in ./python/lib/python2.7/site-packages (from mock>=2.0.0->tensorflow==1.3.0->spinalcordtoolbox===dev)
Requirement already satisfied: MarkupSafe>=0.23 in ./python/lib/python2.7/site-packages (from Jinja2>=2.3->sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: pytz>=0a in ./python/lib/python2.7/site-packages (from babel!=2.0,>=1.3->sphinx->spinalcordtoolbox===dev)
Requirement already satisfied: pyparsing>=2.0.2 in ./python/lib/python2.7/site-packages (from packaging->sphinx->spinalcordtoolbox===dev)
You are using pip version 9.0.1, however version 10.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

Then, compiling the doc:
make --directory=./ html
make: *** No rule to make target `html'.  Stop.

I'll wait for this merge to change the doc of sct_deepseg_gm with the information about the models (slices/subjects trained, etc).

@jcohenadad fixed that invalid make command in the Sphinx README (should be run in documentation/sphinx: make --directory=documentation/sphinx html).


rpm 软件包打包

finished by https://github.com/hust-open-atom-club/hustmirror-cli-archive/commit/8646602a9beaf0fe3f33f09f29c277db9b0636c9


Use ctx instead of this.

I think using ctx for *neo.Ctx is more expressive than this.

Hm, it would make sense. But I used this in all project website examples. Can you change them too? You can find code in gh-pages branch.

Ok, I will.


File cleanup

-Reorganized folder structure in src/app
-Deleted unused files (snapshots.ts and useForceUpdate)
-Fixed the Remix demo-app to work with TS
-Small changes to Readme's:
-rename dev readme to DEVELOPER_README and update link ref in contributing.md
-try to fix h1 header in main readme

Meant to merge oslabs/beta/reactime v23 dev to master branch, please disregard this PR.


Use builder-base to build builder-base

Use builder-base as runtime in builder-base Prowjobs.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/close


add a note about copyright violations to our FAQ

fix for #453 - pls review and merge, @danimo @LukasReschke

THX! :+1:


[Bug] Can't load form with N-N relationship (and subfields) with pivot table alias

Bug report
What I did
I have two models related to each other with a "BelongsToMany" relation.
This relation has pivot attributes, but more importantly it has a customized pivot attribute name like so: ->as('alias')
I defined a Many to Many relation field with subfields on one form and pivotSelect data, then I simply loaded the form by editing an entry.
What I expected to happen
The form loads properly with no errors. All related items are present with all pivot data.
What happened
This error occures :
Call to a member function getAttributes() on null
The error trace leads to ....\vendor\backpack\crud\src\app\Library\CrudPanel\Traits\Update.php:139
It is notable on that line that $item = $model->pivot->getAttributes(); the pivot attribute is directly referenced as "pivot".
What I've already tried to fix it
Everything works just fine as soon as i remove the pivot attribute name customization.
Also it seems to work better if i fetch the pivot accessor dynamically this way:
$item = $model->{$relation->getPivotAccessor()}->getAttributes();
Is it a bug in the latest version of Backpack?
After I run composer update backpack/crud the bug... is it still there?
Yes
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 7.4.27 (cli) (built: Dec 14 2021 19:52:13) ( ZTS Visual C++ 2017 x64 )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Xdebug v3.1.2, Copyright (c) 2002-2021, by Derick Rethans
LARAVEL VERSION:
v8.83.9@ac6e16bb56510eda2e373c6365d5c92da3fd559d
BACKPACK VERSION:
5.0.18@06ea421e44c353604ba56669e1fd3ac7a18981df

@singeryo I can totally replicate this, I haven't used aliases for pivots myself and I think I forgot to support them. Thank you very much for such good issue report, and for providing the solution for it.
I've just tested your fix, and it works wonders. I can submit the PR, but since it's a small change and you have all the credits here I decided to ask you if you want to do it and show up as a Backpack Contributor.
If you don't have time, or just don't feel like doing it, just let me know and I do the PR, no problem 👍
Cheers

Hey @pxpm no problem i'll try to get it done today !
Cheers

Fixed by https://github.com/Laravel-Backpack/CRUD/pull/4401 - thanks @singeryo !


feat: Add linter to adhere coding standards

Overview
This pull request adds the following features:

lint -> run eslint WITHOUT fixing anything (a 'dry-run')
lint:fix -> run eslint while also attempting to fix the problems
Adds husky pre-commit hook that will lint your files before committing.

Will fix #14.

:rocket: PR was released in v0.1.0 :rocket:

:rocket: PR was released in v0.1.0 :rocket:


Hierarchical State Nodes - Executing actions on deep transitions

In xstate/fsm, identifying the actions to execute on a transition is relatively :) straightforward. The actions returned from a transition (for execution in the interpreter) are:

any onexit of the source
any actions of the transition
any onentry of the target

(all excluding any assign actions effecting the context, which are handled inside the transition by updating the returned context)
see next comment for as is xstate/fsm code for handling transition actions.
"In the presence of compound states, transitions no longer simply move from the current active state to a new active state, but from one set of active states to another." See 3.1.4 and 3.1.5 at https://www.w3.org/TR/scxml/
In particular the scxml spec describes in 3.1.5 that upon a transition, a sequence of onexit and onentry actions (along with defined transition actions) is required for all active states, dependig upon the source and target states.
Hence a function is required in xstate/fsm-plus to implement this logic and return an array of actions that are to be executed on a given transition from a source to target states.

xstate/fsm as is functionality for handling transition actions:

Diagram shows asis xstate/fsm code for handling actions on transition (note this is after changes to replace JS destructuring which is not supported in Espruino JS).
1 extracts any transition actions from the transition object
2 build allActions array with actions concat with current state onExit actions plus target state onEntry actions
3 handles any assign actions and returns the modified context and any 'non assign' actions for returning from the transition.


Code style

some more updates.

Impressive! @asukaminato0721, you are a better Rust coder than me!

Very good. Thanks @asukaminato0721 👍


Added tm1_dimension_subset_to_set function

tm1_dimension_subset_to_set  will act the same as tm1_subset_to_set, but without the need for the hierarchy argument.

Thanks


Is there any possibility to get sequence of connected nodes.

Is there any way to get drawFlowId of all nodes before the selected_node Id? I tried but with some conditions, it was going in the infinite loop please suggest any solution, if you have any idea about this let me know.

I was thinking that we can convert your lib to react lib because I don't think any other react library provides these many features that you have in this library.

Hi @amikum1997
You can get the nodes connected to the node with the function:  getNodeFromId(id) and so on until the end of the flow.
I have seen that someone has already converted to react https://github.com/ImuruKevol/react-Drawflow or https://github.com/valerii15298/Drawflow-react

thanks a lot.


Missing required named parameter is reported in legacy libraries

--- Command "dart2analyzer" (took 33ms):
DART_CONFIGURATION=ReleaseX64NNBD out/ReleaseX64NNBD/dart-sdk/bin/dartanalyzer --enable-experiment=non-nullable --ignore-unrecognized-flags --packages=/b/s/w/ir/cache/builder/sdk/.packages --format=machine --no-hints /b/s/w/ir/cache/builder/sdk/tests/co19/src/LanguageFeatures/nnbd/legacy_libraries_A02_t01.dart

exit code:
1

stderr:
ERROR|COMPILE_TIME_ERROR|NOT_ENOUGH_POSITIONAL_ARGUMENTS|/b/s/w/ir/cache/builder/sdk/tests/co19/src/LanguageFeatures/nnbd/legacy_libraries_A02_t01.dart|29|8|2|1 positional argument(s) expected, but 0 found.
ERROR|COMPILE_TIME_ERROR|NOT_ENOUGH_POSITIONAL_ARGUMENTS|/b/s/w/ir/cache/builder/sdk/tests/co19/src/LanguageFeatures/nnbd/legacy_libraries_A02_t01.dart|25|8|2|1 positional argument(s) expected, but 0 found.
ERROR|COMPILE_TIME_ERROR|MISSING_REQUIRED_ARGUMENT|/b/s/w/ir/cache/builder/sdk/tests/co19/src/LanguageFeatures/nnbd/legacy_libraries_A02_t01.dart|23|5|3|The named parameter 'named' is required but was not provided.
ERROR|STATIC_TYPE_WARNING|UNDEFINED_METHOD|/b/s/w/ir/cache/builder/sdk/tests/co19/src/LanguageFeatures/nnbd/legacy_libraries_A02_t01.dart|29|11|4|The method 'test' isn't defined for the type 'C'.
ERROR|COMPILE_TIME_ERROR|MISSING_REQUIRED_ARGUMENT|/b/s/w/ir/cache/builder/sdk/tests/co19/src/LanguageFeatures/nnbd/legacy_libraries_A02_t01.dart|24|3|4|The named parameter 'named' is required but was not provided.
ERROR|STATIC_TYPE_WARNING|UNDEFINED_METHOD|/b/s/w/ir/cache/builder/sdk/tests/co19/src/LanguageFeatures/nnbd/legacy_libraries_A02_t01.dart|25|11|4|The method 'test' isn't defined for the type 'C'.

--- Re-run this test:
python tools/test.py -n analyzer-asserts-strong-linux co19/LanguageFeatures/nnbd/legacy_libraries_A02_t01

https://dart-review.googlesource.com/c/sdk/+/139323


Edge Drag

I do not speak English well, so I use Google Translate.
I modified it so that I can change the target vertex by dragging the edge.
Edge routing is not yet applied when you drag.
Please acknowledge the inexperience of using Github.

Hello! Looks very interesting. Have to check the code as there are too much changes. Seems like you have different code style so there are many of blanks and refactoring, including the classes not affected by described feature.


Handle Parameters section with POST and PATCH methods

It would be great to be able to display the parameters UI section for POST and PATCH query as you are currently doing with GET query. The idea would be to specify the mandatory and optional parameters with a short description.

I know there is no direct way to handle this with Insomnia but maybe using a similar pattern than the response query in the docs tab ?

Is this question still relevant? If I recall correctly, you can actually set query parameters for non-GET requests in Insomnia and if that's the case, the documenter should display them. If it doesn't please let me know so I can look into it!


Improve development process

add config for netlify to avoid refresh the page which hosted by will become page 404

use vite-react-swc

add dockerignore for build

@TrNgTien Thanks!

You're welcome ^^


How to specify other tables in an update statement

From the postgres spec:
[ WITH [ RECURSIVE ] with_query [, ...] ]
UPDATE [ ONLY ] table_name [ * ] [ [ AS ] alias ]
    SET { column_name = { expression | DEFAULT } |
          ( column_name [, ...] ) = [ ROW ] ( { expression | DEFAULT } [, ...] ) |
          ( column_name [, ...] ) = ( sub-SELECT )
        } [, ...]
    [ FROM from_list ]
    [ WHERE condition | WHERE CURRENT OF cursor_name ]
    [ RETURNING * | output_expression [ [ AS ] output_name ] [, ...] ]

I'm unable to figure out how to add [ FROM from_list ] items. I'm attempting to do a simple join on the update. Attempting to build something like this:
update user_groups set role = ? from groups where user_groups.group_id = groups.id and groups.account_id = ? and user_groups.id = ?

Please don't look too much into this example. There are lots of uses for joins during update.

With v8 #110 this will be easier to accomplish, Ill look into adding this next.

This will be in the next release v8.0.1. I added support for both postgres and mysql.
Examples:
Postgres
dialect := goqu.Dialect("postgres")

ds := dialect.Update("table_one").
    Set(goqu.Record{"foo": goqu.I("table_two.bar")}).
    From("table_two").
    Where(goqu.Ex{"table_one.id": goqu.I("table_two.id")})

sql, _, _ := ds.ToSQL()
fmt.Println(sql)

Output:
UPDATE "table_one" SET "foo"="table_two"."bar" FROM "table_two" WHERE ("table_one"."id" = "table_two"."id")

MySQL
dialect := goqu.Dialect("mysql")

ds := dialect.Update("table_one").
    Set(goqu.Record{"foo": goqu.I("table_two.bar")}).
    From("table_two").
    Where(goqu.Ex{"table_one.id": goqu.I("table_two.id")})

sql, _, _ := ds.ToSQL()
fmt.Println(sql)

Output:
UPDATE `table_one`,`table_two` SET `foo`=`table_two`.`bar` WHERE (`table_one`.`id` = `table_two`.`id`)


is blur prop working?

i've passed blur prop. My background has no change. are you sure it's working?

@tuguScript Yes, it is working. Can you show me a snippet so I can see how you are using it? In which browser are you testing?

@tuguScript sorry, but next time please think of:

Giving a more detailed error description
Answer other questions as you also want to have answers as quick as possible.

I will close this issue. Re-open it if there is still a problem


Timeout not working

🐛 Bug Report
Test runs forever instead of timming out.
ts-jest issue: https://github.com/kulshekhar/ts-jest/issues/1973
To Reproduce
Steps to reproduce the behavior:
export const testFct = (value: number) => {
    while (value < 1) {
        ;
    }
    return value;
}

describe('Test', () => {
    test(`should work`, () => {
        expect(testFct(-0.5)).toEqual(1);
    }, 1000);
});

Stuck at  RUNS  ./foo.spec.ts
Expected behavior
Timeout
Link to repl or repo (highly encouraged)
https://repl.it/repls/GlisteningScentedOpendoc#sum.test.js
https://github.com/cdalexndr/ts-jest-1973
envinfo

  System:
    OS: Windows 10 10.0.18362
    CPU: (4) x64 Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz
  Binaries:
    Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.13.1 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    jest: ^26.4.2 => 26.4.2

Any idea how to fix this? we experience similar issues in our setup


ngc+AOT+webpack - compile error

Issue Summary
The following error occurs, when I try to build my project using webpack and taking advantage of AOT
Error: Error encountered resolving symbol values statically. Only initialized variables and constants can be referenced because the value of this variable is needed by the template compiler (position 3:22 in the original .ts file), resolving symbol ExtandableRequest in D:/01_trunk/angular2-webpack-starter/node_modules/service-mocker/server/request.d.ts, resolving symbol MockerRequest in D:/01_trunk/angular2-webpack-starter/node_modules/service-mocker/server/request.d.ts
I have a feeling that it is related to this<EMAIL_ADDRESS>...
Tsc works just fine.
Expected Behavior
Succesful compilation.
Environment

Version of service-mocker: 1.1.0

Sorry I am not familiar with angular 2. Will it be possible to do AoT compilation only in production?

@BogdanDumitruMarian we've just released 2.0.0 version, can you upgrade your service-mocker and test it again?

Hello, it seems to work now.


Adding support for React 19

The current peer dependencies for @hookform/devtools do not include support for React 19, while react-hook-form already does.
@hookform/devtools/package.json
  "peerDependencies": {
    "react": "^16.8.0 || ^17 || ^18",

react-hook-form/package.json
  "peerDependencies": {
    "react": "^16.8.0 || ^17 || ^18 || ^19"
  },

Can we add the support for React 19?

We need a quick fix ASAP


Re-evaluate loops argument in Mixer::playMusic function

Ref: #923 comment

The playMusic loop arguments are specific to and part of the SDL Mixer API. Requiring the loop arguments in the base Interface should be re-evaluated.

I thought I commented on this already... hrmm.
Well anyway,
I'm in favor of removing the loops argument from playMusic and fadeInMusic -- I don't think I've ever used anything other than the default value there and it's fair to assume that music will be played continuously.
That stated, there are cases where the user will want to play a music track only once -- I can think of the case in OPHD with multiple tracks. When a track finishes, a signal is emitted and another track is started. In these cases it might make sense to just have a separate function, something like playMusicOnce. Or maybe playMusic and playMusicContinous.

I can see a music player-like functionality similar to Command and Conquer. The repeat setting is part of the player and can be turned on/off. The value of the button would determine if looping were enabled or not and by being an on/off toggle (like, how all music players do) it would be be default "continuous" (i.e., "as many times as allowed").
Regardless, I agree, separating out looping vs non-looping into their own functions would make things cleaner.

Issue #944 doesn't have a clear distinction from this issue. Perhaps we should close one of them. They kind of look like duplicate issues.

I'd be tempted to remove loop support from the backend, and dump that responsibility on the front end for playlist control.
For the simple case, to loop music they could setup a music complete callback that would just start playing the same track again.
For the more complicated case of having full playlist control, such as in Command and Conquer, the loop feature of the backend wouldn't likely be of much use, and would probably just be ignored.
I sort of feel like adding looping support to the API may actually just be adding needless complexity.

From an engine standpoint, looping or not would be defined at the asset level. Unreal Engine has Audio Assets that encode whether or not they are looping and that determines how the buffer is initialized for playing. NAS2D doesn't have an asset system. This allows us to punt on looping support engine-side for now and let the user use the callback system to restart the music. It might introduce a small delay but "meh".

Was revisiting issues we haven't touched in awhile.
I'm in favour of removing looping support from the API, and instead rely on the caller to make use of the callback system to either restart the track for looped music, or to play a new track.
In terms of impact, I think such a change would not really be noticed. OPHD doesn't current have music playing during gameplay. It might be relevant if someone spends enough time at the main menu. Though, infinitely looping a single track can get pretty annoying.
Many years ago, I was at a LAN party, and someone left a DVD on the main menu, that just kept looping some intro sequence. Everyone was too busy playing some long intense game to stop the DVD, and as the game dragged on, the looped intro music in the background got really really annoying.  Let's not be like that.

I'm ultimately not opposed to taking it out and requiring the user to use some form of callback. I'd rather keep it out of the assets to make it really easy to deal with stuff like this. I'd rather avoid needing to have additional tools to encode stuff like that.
SDL1/2/3 provides callback methods so we can just build that into NAS2D and have the end-user code hook into that as an event and go from there. Would also eliminate the need for the playMusicWithIntro() type function that I used to have (might still be there? Don't remember).


coll: bang fix

fixing bangs, hopefully..
also started taking some notes for capture,.. nothing functionally has changed yet... just trying to understand how the code works

there was a compile error that I fixed!


This no longer works since Mozilla removed Services.jsm

I spent a few hours to debug why this repo doesn't work on my system and found Mozilla has already removed Services.jsm, please refer to https://phabricator.services.mozilla.com/rMOZILLACENTRALa920ea193e291fa023837bed7b86f6b74ed06e51.

console.warn(
"Services.jsm will be removed by Firefox 117 or 118. Use the Services global variable instead"
);

It seems it works again after I remove below lines:

const {Services} = Components.utils.
import('resource://gre/modules/Services.jsm');

Seems https://github.com/tsaost/autoload-temporary-addon/pull/3 already exist to address this issue.