<EMAIL_ADDRESS>ReferenceError: React is not defined when rendering a Dialog-component from @mui/material

Describe the bug
When rendering a page containing a Dialog component from @mui/material while using @vitejs/plugin-react version 1.1.4, the app crashes with error message ReferenceError: React is not defined. It seems to be related to the bug fix regarding React.createElement in the latest release.
When switching version to 1.1.3 everything works as expected. Unfortunately, I was not able create an isolated reproduction of the error in StackBlitz. To reproduce, render a MuiDialog in an app using @vitejs/plugin-react version 1.1.4. The issue is only occuring in production builds, not dev environment.

Reproduction
StackBlitz repro
System Info
System:
    OS: macOS 12.0.1
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 1.13 GB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node
    Yarn: 1.22.17 - ~/Dev/naeva/home/node_modules/.bin/yarn
    npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm
  Browsers:
    Chrome: 97.0.4692.71
    Firefox: 85.0.2
    Safari: 15.1
  npmPackages:
    @vitejs/plugin-react: 1.1.4 => 1.1.4
    vite: ^2.6.4 => 2.7.12

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

use a github repository if you can't repro against stackblitz

I experienced the same error in production builds only. Downgrading to<EMAIL_ADDRESS>got things working again for me.

The issue seems to related to a custom MuiDialog from our component library. I will try to reproduce the problem.

I have updated the issue with repro on stackblitz, although the issue does not seem to happen when running npm run serve on StackBlitz. Are there any known differences in running locally vs. on StackBlitz?

Same issue in our app. ReferenceError: React is not defined with 1.1.4 when running npm run serve. Works with 1.1.3. If it's not something obvious I'll try to come up with repro.

I'm in way over my head when it comes to this stuff, but my best(and only) bet is that the changes in (ce65c56) broke the way Vite handles our compiled MuiDialog from our component library. Related PR: (#6110)
Since the issue does not happen in the repro above, I am guessing that it is a conflict between babel/vite since we are using babel in our library.

This might be related to https://github.com/alloc/vite-react-jsx/issues/10 and https://github.com/vitejs/vite/issues/5608

Happened to me as well, but only when running vite build without a --mode option
When ran vite build --mode staging for example the transformation works fine
I believe is something with a different production bundling/transformation logic, but no sure what

Hmm, so looking at other discussions of similar issues, just a hunch but I think it might be when a library explicitly uses React.createElement or anything else on React but the plugin doesn't catch all of those to transform to the new way (https://reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html ), then some of those React.createElement remains in the build, but no import React is injected for those special ones. Hence failing with React is not defined.
The plugin is supposed to transform all the cases, according to the README of the plugin that was merged into the current plugin: https://github.com/alloc/vite-react-jsx
Using the older @vitejs/plugin-react-refresh plugin that doesn't do the new transforms, works for me if I inject an React import (if you don't add it in components yourself)
defineConfig({
  plugins: [reactRefresh()],
    esbuild: {
    jsxInject: `import React from 'react'`,
  })

I have the same issue in production mode and I can confirm than downgrading @vitejs/plugin-react to 1.1.3 fixes the issue.


Wrong word-break

The wordbreak for the two utf8 characters "═🇫" is reported inside an utf-8 char sequence.
Testcase:
#include <stdio.h>
#include <string.h>
#include "wordbreak.h"
int main()
{
    unsigned char utf8[] = {
        0xe2, 0x95, 0x90,
        0xf0, 0x9f, 0x87, 0xab,
        0x00
    };
    char brks[sizeof(utf8)];
    int i;
    set_wordbreaks_utf8( utf8, strlen(utf8), NULL, brks );
    for( i=0; i < sizeof(utf8); ++i )
        printf( "%d\n", (int)brks[i] );
    return 0;
}

Sorry for the delayed response, I was on holiday and away from keyboard. I'm back now.
I tested it and can confirm it's an issue. I'm looking into it.


Bug in TextBuffer::setTextInBufferRange() ?

Hi,
I'm not sure, but something seems not logical to me. According to the doc of TextBuffer::setTextInBufferRange() :

Public: Set the text in the given range.

range A {Range}
text A {String}
normalizeLineEndings (optional) {Boolean} (default: true)

Returns the {Range} of the inserted text.

But when passing a Range argument to the method, I do not observe a text replacement, but an insert.
I've seen in the unit tests that you use an array as param, witch works as excepted : the old text is replaced by the given one.
Steps to reproduce :
 atom --safe

add some text in a new file : 1234 in the first line
then in developper tools console :

textBuffer = atom.workspace.getActiveTextEditor().getBuffer();
textBuffer.setTextInRange([[0,0], [0,1]], 'a');

=> Ok first line becomes a234

now trying to replace back the 'a' by '1', using a Range argument :

textBuffer.setTextInRange(new Range([0,0], [0,1]), '1')

=> Not Ok first line becomes 1a234, it's not a replace but an insert

We did not rename as part of the api freeze. Closing as we plan on keeping it the way it is.


fix: Wrapped promise allows ES6 sub-classing

Sub-classing the global Promise using ES6 classes after the agent has loaded results in the extended class properties not being present on the created promise instance. The wrapper has been moved to use ES6 sub-classing allowing further sub-classing.

Overview

Rewrote the promise wrapper to use ES6 sub-classing of the global Promise.
Related Issue(s)

https://new-relic.atlassian.net/browse/NR-155491
Testing

Closing for now. We can revisit this if we need to after the spa refactor.


Proper Tagged Github Releases with Binaries

the last release on this repo was

Could this repo start tracking releases again and at the very least include the zipped .nupkg for both the Compiler Service and Project Cracker?

@cloudRoutine Yes it should, though it seems to complicate the release process - I think we were getting failures in the github release creation. Perhaps we should just delete the github releases and use only nuget.org for now

Really? We do it all the time with most of the F# OSS projects I work on with essentially the same GithubRelease Target as this repo's build.fsx, the main difference being
createClient user pw
|> createDraft gitOwner gitName release.NugetVersion (release.SemVer.PreRelease <> None) release.Notes
|> uploadFile "temp/forge.zip"
|> releaseDraft
|> Async.RunSynchronously

the file upload.
The nupkgs are already being built so all it takes it pointing uploadFile to the buildDir for each pkg. The only thing that would make it a bit more complex is each pkg should get an additional tag (FCS & Project Cracker) in addition to the version number.
If @rneatherway  was doing the releases was it some mono issue?

It worked infrequently, but some people preferred to upload the nuget packages manually I think. I use this all the time for FsAutoComplete on mono.

OK, let's aim to get it working again

6.0.2 released on nuget and github.  Main thing is you need to do set nugetkey=... before build Release


[Code Health] Use SaferCPlusPlus to reduce memory usage/ violations

Description of the new feature/enhancement
"SaferCPlusPlus" is essentially a collection of safe data types intended to facilitate memory and data race safe C++ programming. This library is intended to work with and be complimentary to the Core Guidelines lifetime checker over its various stages of development and availability. (Including situations where the lifetime checker is not available at all.)
A clear and concise description of what the problem is that the new feature would solve.
See the rest of the README for the benefits as well usage examples: https://github.com/duneroadrunner/SaferCPlusPlus/blob/master/README.md
Proposed technical implementation details (optional)
Include the necessary headers as described in the README.
A clear and concise description of what you want to happen.
A more memory safe conhost, conpty, and Terminal.

Hey there! Thanks for the request and the idea, but it's important for us to remain close to the VC++ STL. I agree that memory and data race safety would be an awesome thing to add, especially as "close-to-drop in replacements", but I think that request is better made against the upstream STL.
Sorry!

I think the idea is to use only the headers you need to save on performance. Implementing at STL is great idea but that would mean having all headers added. I'm not sure that's what we want, especially as it does take away some dangerous behaviors for some of the std calls. I'd say it's more likely to get traction with gsl but they follow upstream and the upstream isn't really interested in picking it up, hence why it's "complimentary" to Core Guidelines.
So this boils down into two paths:

We get STL to adopt it and potentially break any number of customer workflows

or

We implement it at this project and as we have a fallback "legacy" mode for conhost, we don't have to worry as much about breaking workflows. As it's mostly drop-in replacements, the biggest hurdle would determining which headers we need and which ones we don't.

https://github.com/microsoft/STL/issues/241 filed for tracking.

Not sure if noticed but that issue was closed. I had high suspicion it might be. I found an issue for adopting at the iso guidelines repo but it hasn't been looked at in over a year. So for now, I'd think this project should adopt it as it implements best practice and requires not much to start using.


Add documentation for the native type system.

Here's a proposal for the addition to the docs.
@craigtaverner I added you in this one to have a quick look at [[reference:native-property-types:spatial-types]]. Thanks.

Thanks for your thorough review, @craigtaverner. Regarding the 4 different types: Yes, the do carry their CRS and they can describe it and we are fit for the thousands to come.


Missing normalisation for "datetime[ns]" dtype

Today I was starting my Explorer journey and I pulled a parquet dataset from "https://d37ci6vzurychx.cloudfront.net/trip-data/yellow_tripdata_{year}-{month}.parquet" (e.g.: year -> 2019, month -> 01).
When importing it using Explorer.DataFrame.from_parquet/1, I realised we are missing the match to the "datetime[ns]" dtype in the PolarsBackend.Shared.normalise_dtype/1 function.
Are we really missing it or maybe we don't want it in here?
For the first option, should be enough adding the following match:
def normalise_dtype("datetime[ns]"), do: :datetime

Pushing a PR with the change so it can be reviewed.
See the error in the attached photo below (using Livebook 📖 )

Closing in favor of the PR (so the discussion is in one place).


Colab Error : fd 78 failed with Input/output error

Hello,
I tried using your google collab and i got this error on "Create a model and load checkpoints" step
note that i used the default configuration (default video and default image).
`RuntimeError                              Traceback (most recent call last)
 in ()
1 from demo import load_checkpoints
2 generator, kp_detector = load_checkpoints(config_path='config/vox-256.yaml',
----> 3                             checkpoint_path='/content/gdrive/My Drive/first-order-motion-model/vox-cpk.pth.tar')
2 frames
/usr/local/lib/python3.6/dist-packages/torch/serialization.py in _legacy_load(f, map_location, pickle_module, **pickle_load_args)
779     offset = f.tell() if f_should_read_directly else None
780     for key in deserialized_storage_keys:
--> 781         assert key in deserialized_objects
782         deserialized_objects[key]._set_from_file(f, offset, f_should_read_directly)
783         if offset is not None:
RuntimeError: read(): fd 78 failed with Input/output error`

Something wring with the checkpoint how did you put it to Google drive. What is the size of it?

Fixed.
I just removed the shortcut of "first-order-motion-model" folder from my drive and then created another shortcut of this same folder and it works now. thank you for your help.
Note that I used this collab 3 months ago and it worked.  if anyone get this error just remove and re-assign the folder.


chore(master): release 0.4.29

:robot: I have created a release beep boop
0.4.29 (2024-10-14)
⚡ Performance

pre-create worker if needed at the end of task execution (cd7406c)

📚 Documentation

README.md: revert reformatting (5561f4e)

🤖 Automation

deps: Bump github/combine-prs from 5.1.0 to 5.2.0 (3412820)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.4.29
:sunflower:


uboot: 2022.10 -> 2023.01

Description of changes
Updated u-boot to the latest stable release, due to a bug in u-boot which led the booting process hang usb SSD connected.
After updating the new 2023.01 version. And It does compiles and raspberrypi4 tested booting from the USB SSD that previously made the u-boot hang.
Things done
Changed u-boot version and updated checksum. Tested the new build with raspberrypi4 b 2GB v1.1
With new version finally my USB SSD not causing issue and I am able to boot from there as well.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 218816 run on x86_64-linux 1

1 package marked as broken and skipped:

odroid-xu3-bootloader

3 packages built:

diffoscope
ubootQemuX86
ubootTools

please rebase instead of merging master into your branch

I'm still new to participating in project that has more than a handful people and I have messed up rebasing. Now it should  be fine.

That's mainly an issue when rebasing between branches (master vs staging), but thanks for being cautious.

Please format the commit message as instructed by CONTRIBUTING.md.

~Please format the commit message as instructed by CONTRIBUTING.md.~ Actually I can just fix that on merge.

Thanks I will keep that in mind next time.

Note: Allwinner boards may not build as they are right now due to a change in the build tooling. As reported in https://github.com/NixOS/nixpkgs/pull/156034#issuecomment-1665623718.
       > binman: Filename 'scp.bin' not found in input path (.,.,./board/sunxi,arch/arm/dts) (cwd='/build/u-boot-2023.01')

Solution will be to provide either an SCP binary path, or /dev/null via SCP
SCP = "/dev/null";

In the future all U-Boot builds exposed in Nixpkgs should be built successfully before building, through pkgsCross.the-right-arch-here.

It looks like this solution with SCP = "/dev/null";  doesn't work for A64 OLinuXino. I haven't yet had chance to try with the SCP binary path. Note that at this point we have to work with the p11-kit from staging-next due to a problem with p11-kit in master failing because cross compilation tests are not permitted.


Support docker run with  --user $(id -u):$(id -g) cli arg (shared process error)

Test environment
Host OS: OSX 10.14.4
Docker: <IP_ADDRESS> (31259)
image: codercom/code-server:1.621
Request
Hi,
We run docker in a locked down environment where we alias the docker run cli command to prepend --user $(id -u):$(id -g) on all host operating systems. This is a security constraint we can't remove. When i try to execute code server simulating this environment it throws a shared process error. Any ideas on an approach to resolve?
Repro
docker run -it -p <IP_ADDRESS>:8443:8443 -v "${PWD}/codeserver:/home/coder/project" -u $(id -u):$(id -g) -v "${PWD}/codeserver/.cache:/.cache" -v "${PWD}/codeserver/.local:/.local" codercom/code-server:1.621 --allow-http --no-auth
INFO  code-server development
INFO  Additional documentation: http://github.com/codercom/code-server
INFO  Initializing {"data-dir":"/.local/share/code-server","extensions-dir":"/.local/share/code-server/extensions","working-dir":"/home/coder/project","log-dir":"/.cache/code-server/logs/20190405152816797"}
INFO  Starting webserver... {"host":"<IP_ADDRESS>","port":8443}
WARN  No certificate specified. This could be insecure.
WARN  Documentation on securing your setup: https://github.com/codercom/code-server/blob/master/doc/security/ssl.md
WARN  Launched without authentication.
INFO
INFO  Started (click the link below to open):
INFO  http://localhost:8443/
INFO
INFO  Starting shared process [1/5]...
INFO  Starting shared process [2/5]... {"error":"Exited with 1"}
INFO  Starting shared process [3/5]... {"error":"Exited with 1"}
/src/packages/server/out/cli.js:325
return"boolean"==typeof e.extractComments?(r.preserve=i,r.extract=/^\**!|@preserve|@license|@cc_on/i):"string"==typeof e.extractComments||e.extractComments instanceof RegExp?(r.preserve=i,r.extract=e.extractComments):"function"==typeof e.extractComments?(r.preserve=i,r.extract=e.extractComments):Object.prototype.hasOwnProperty.call(e.extractComments,"condition")?(r.preserve=i,r.extract=e.extractComments.condition):(r.preserve=!1,r.extract=i),["preserve","extract"].forEach(e=>{let t,n;switch(typeof r[e]){case"boolean":r[e]=r[e]?()=>!0:()=>!1;break;case"function":break;case"string":if("all"===r[e]){r[e]=(()=>!0);break}if("some"===r[e]){r[e]=((e,t)=>"comment2"===t.type&&/^\**!|@preserve|@license|@cc_on/i.test(t.value));break}t=r[e],r[e]=((e,n)=>new RegExp(t).test(n.value));break;default:n=r[e],r[e]=((e,t)=>n.test(t.value))}}),(e,t)=>{if(r.extract(e,t)){const e="comment2"===t.type?`/*${t.value}*/`:`//${t.value}`;n.includes(e)||n.push(e)}return r.preserve(e,t)}})(e,c,u));const

Error: ENOENT: no such file or directory, uv_os_get_passwd
    at new t.Server (/src/packages/server/out/cli.js:325:105264)
    at e.exports.w.on (/src/packages/server/out/cli.js:325:102138)
    at emitTwo (events.js:131:20)
    at e.exports.emit (events.js:214:7)
    at handleUpgrade.t (/src/packages/server/out/cli.js:489:29992)
    at e.exports.completeUpgrade (/src/packages/server/out/cli.js:489:32439)
    at e.exports.handleUpgrade (/src/packages/server/out/cli.js:489:31556)
    at upgrade (/src/packages/server/out/cli.js:489:29963)
    at emitThree (events.js:136:13)
    at u.emit (events.js:217:7)
    at onParserExecuteCommon (_http_server.js:542:14)
    at socketOnData (_http_server.js:477:3)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at Socket.Readable.read (_stream_readable.js:475:10)
    at flow (_stream_readable.js:846:34)
    at emitReadable_ (_stream_readable.js:514:3)
    at emitReadable (_stream_readable.js:507:7)
    at addChunk (_stream_readable.js:274:7)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at TCP.onread (net.js:601:20)

after educating myself a bit on docker user and group management, this does not appear to be something that is fixable by codercom devs. I will be closing this issue.  Here's a brief synopsis:

coder (properly) adds a user to the image and ensures codeserver is executed as that user
this user will resolve to 1000:1000 in /etc/passwd in the container per ubuntu defaults
if you are lucky enough to be running on a host where your user id equals 1000, passing -u $(id -u)  will just work; otherwise, which I assume is most cases, it will not

in short docker is doing what it's supposed to, and my uid does not resolve to the uid that codeserver is instructed to run as. We are discussing other approaches as passing the -u $(id -u) flag does not seem like something that will scale appropriately, particularly for third party images.

after educating myself a bit on docker user and group management, this does not appear to be something that is fixable by codercom devs. I will be closing this issue. Here's a brief synopsis:

coder (properly) adds a user to the image and ensures codeserver is executed as that user
this user will resolve to 1000:1000 in /etc/passwd in the container per ubuntu defaults
if you are lucky enough to be running on a host where your user id equals 1000, passing -u $(id -u)  will just work; otherwise, which I assume is most cases, it will not

in short docker is doing what it's supposed to, and my uid does not resolve to the uid that codeserver is instructed to run as. We are discussing other approaches as passing the -u $(id -u) flag does not seem like something that will scale appropriately, particularly for third party images.

If you are building your own Docker image you can designate what user you want the container to use in your Dockerfile.

Unless I'm mistaken you would need to have a custom docker build for every user in the organization that wants to use code server with this approac. This could be in the thousands in our world, and is not scalable. The core requirement is dynamic uid/guid resolution to be mapped at runtime, not build time. Ideally a single hosted instance could support multiple users, obviating the need for this,  which seems like it's being investigated:
https://github.com/codercom/code-server/issues/33
Until then we are looking at podman.io, or possibly creating our own image that includes a PAM module that could resolve our UIDs from a directory server.  Or even potentially an approach like fixid: https://boxboat.com/2017/07/25/fixuid-change-docker-container-uid-gid/. Very early days for us.

Hey @satlus I did the usermode changelist for it and this seems to be similar to the OpenShift case as stated in #223. Kindly reopen as I would be happy to investigate and properly fix it

Cool, re-opened. I think I see the approach here per your openshift fork. I noticed that you're doing an append to the container /etc/passwd file based on uid:guid in the entry point script. I've done similar in my fork, but using a sudo groupmod so we don't keep appending duplicate entries:
https://github.com/codercom/code-server/compare/master...satlus:satlus-nonrootuser
I'm currently at a very low bandwidth area and get build the docker image to test - when I can I'll post back.

Any update on this @satlus ?

I was able fiddle with this today, and I couldn't get an approach using sudo usermod or vanilla usermod, to work.  I captured the UID:GID in container env vars, and then ran usermod in the entrypoint script prior to execution. the problem is that if you do this with the host user, you're not in /etc/passwd and usermod fails (sudo will fail as well for the same reason). More details here:
https://github.com/codercom/code-server/commit/70424c8edcadb7f15f2890b38e9f3d01a5de2496
disclaimer: I shouldn't be considered authoritative on this subject I'm experimenting. I'll play around a bit more, but including trying sr229's approach

If I supply -u (or --user) flag to keep file permissions correct as if I were to play with my files on the host, the service is failing to create a ./cache directory. Is it something that can be configured to create under the /tmp instead of the root of the file system?
$ mkdir /tmp/foo
$ cd /tmp/foo
$ docker run --rm -it \
  -u $(id -u):$(id -g) \
  -p <IP_ADDRESS>:8443:8443 \
  -v $PWD:/home/coder/project \
  codercom/code-server --allow-http --no-auth
(node:6) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
ERROR { [Error: EACCES: permission denied, mkdir '/.cache']
  [stack]: 'Error: EACCES: permission denied, mkdir \'/.cache\'',
  [message]: 'EACCES: permission denied, mkdir \'/.cache\'',
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/.cache' }

If you scroll horizontally you'll see I pass volume mounts to make the directories writable. You'll need to do the same. I have examples in my fork:
https://github.com/satlus/code-server/blob/satlus-nonrootuser/DockerLaunchCommands.MD
I think you will still hit the shared process issue I originally reported, which is ultimately due to this:
https://github.com/cdr/code-server/issues/439#issuecomment-481850310

I guess https://github.com/boxboat/fixuid can help resolve the UID/GID issue at least.

I guess https://github.com/boxboat/fixuid ( 9 hours ago) can help resolve the UID/GID issue at least.

This looks great. I was just now coming across this same issue with mounted partitions. I am about to try that out right now. It seems extremely useful in many situations. Thanks for the link. : D

added fixuid in my branch, and it's working in my test environment. I've submitted a PR for review here:
https://github.com/cdr/code-server/pull/640

You beat me to this PR @satlus, good job! :+1:
I have provided some feedback in the PR, but I am no authority on this repo.

CC @satlus I'll be including your modifications in my Docker image so people can pre-test it and have their feedback.

The thing is I'll be re-modifying it to use a production image of the editor will update when I have a working image.

@sr229 I've been pulled away from this for a couple of weeks, but this image was running successfully in our environment. Happy to discuss mods via #640. Ideally it would eventually get merged, as I see it as non invasive.

Wanted to add my band-aid for this problem by overriding the entrypoint with the following script.
#!/bin/bash
sudo /usr/sbin/groupadd <my gid>
sudo /usr/sbin/usermod -u <my uid> -g <my gid> coder
/usr/bin/dumb-init /usr/local/bin/code-server --disable-telemetry


Issue #17 - Create pages for the following listed below

Description:
Design and implement a custom pages with helpful navigation options and proper images and links. Basically you dont have to type the exact content but rather just create a template for the pages listed below

[ ] Privacy Policy
[ ] Terms of Service
[ ] Contact Us

Technical Requirements:

React components
React Router

Acceptance Criteria:

Proper template for adding text, images and links
Helpful navigation options
Responsive design
Consistent styling

hey @Siddheshuncodes would love to work on this! Could you assign it to me?

@patricksolka
Thank you for taking up this issue. Please keep us updated with your progress on this.

@patricksolka Hey, any update on this issue?

Hey @Siddheshuncodes, sorry for the delay! I've been busy the past few days, but I'll start working on it today!

@Siddheshuncodes, I noticed that there are currently two "Contact us" links—one is empty, and the other redirects to the GitHub repo. Should I combine them into a single link?

@patricksolka Thanks for noticing that.
Yes, combine them into a single link

Hey @divyesh-mali just pushed a PR


Error in Go routine: runtime error: invalid memory address or nil pointer dereference

Do you want to request a feature or report a bug?
Bug
What did you do?
Tried to add a load-balancer service for A-B testing.
What did you expect to see?
No panic
What did you see instead?
Panic
Output of traefik version: (What version of Traefik are you using?)

Docker Swarm.
environment:
  TRAEFIK_ENTRYPOINTS_WEB_ADDRESS: ":80"
  TRAEFIK_ENTRYPOINTS_WEB_FORWARDEDHEADERS_TRUSTEDIPS: "<IP_ADDRESS>/20,<IP_ADDRESS>/22,<IP_ADDRESS>/22,<IP_ADDRESS>/22,<IP_ADDRESS>/18,<IP_ADDRESS>/18,<IP_ADDRESS>/20,<IP_ADDRESS>/20,<IP_ADDRESS>/22,<IP_ADDRESS>/17,<IP_ADDRESS>/15,<IP_ADDRESS>/12,<IP_ADDRESS>/13,<IP_ADDRESS>/22,2400:cb00::/32,2606:4700::/32,2803:f800::/32,2405:b500::/32,2405:8100::/32,2a06:98c0::/29,2c0f:f248::/32"
  TRAEFIK_ENTRYPOINTS_WEBSECURE_ADDRESS: ":443"
  TRAEFIK_ENTRYPOINTS_WEBSECURE_FORWARDEDHEADERS_TRUSTEDIPS: "<IP_ADDRESS>/20,<IP_ADDRESS>/22,<IP_ADDRESS>/22,<IP_ADDRESS>/22,<IP_ADDRESS>/18,<IP_ADDRESS>/18,<IP_ADDRESS>/20,<IP_ADDRESS>/20,<IP_ADDRESS>/22,<IP_ADDRESS>/17,<IP_ADDRESS>/15,<IP_ADDRESS>/12,<IP_ADDRESS>/13,<IP_ADDRESS>/22,2400:cb00::/32,2606:4700::/32,2803:f800::/32,2405:b500::/32,2405:8100::/32,2a06:98c0::/29,2c0f:f248::/32"
  TRAEFIK_ENTRYPOINTS_TRAEFIK: "false"
  TRAEFIK_API: "true"
  TRAEFIK_LOG: "true"
  TRAEFIK_LOG_LEVEL: INFO
  TRAEFIK_LOG_FORMAT: "json"
  TRAEFIK_ACCESSLOG: "true"
  TRAEFIK_ACCESSLOG_FORMAT: "json"
  TRAEFIK_ACCESSLOG_FILEPATH: "/root/logs/traefik/access.log"
  TRAEFIK_ACCESSLOG_BUFFERINGSIZE: 10
  TRAEFIK_PING: "true"
  TRAEFIK_PROVIDERS_DOCKER: "true"
  TRAEFIK_PROVIDERS_DOCKER_NETWORK: proxy
  TRAEFIK_PROVIDERS_DOCKER_SWARMMODE: "true"
  TRAEFIK_PROVIDERS_DOCKER_EXPOSEDBYDEFAULT: "false"
  TRAEFIK_PROVIDERS_FILE_DIRECTORY: "/etc/traefik/conf.d/"
  TRAEFIK_METRICS_STATSD: "true"
  TRAEFIK_METRICS_STATSD_ADDRESS: "influxdb_telegraf:8125"

This seems to be the offending TOML.  When I add this in a separate file it causes the error.
[http.services.php73-varnish-split-production]
  [[http.services.php73-varnish-split-production.weighted.services]]
    name = "php73-production@docker"
    weight = 10
  [[http.services.php73-varnish-split-production.weighted.services]]
    name = "varnish@docker"
    weight = 10

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
End of the debug log below.
{
  "entryPointName": "websecure",
  "level": "debug",
  "middlewareName": "tracing",
  "middlewareType": "TracingForwarder",
  "msg": "Added outgoing tracing middleware php73",
  "routerName": "php73@docker",
  "time": "2019-11-14T05:58:42Z"
}
{
  "entryPointName": "websecure",
  "level": "debug",
  "middlewareName": "traefik-internal-recovery",
  "middlewareType": "Recovery",
  "msg": "Creating middleware",
  "time": "2019-11-14T05:58:42Z"
}
{
  "entryPointName": "websecure",
  "level": "debug",
  "middlewareName": "metrics-entrypoint",
  "middlewareType": "Metrics",
  "msg": "Creating middleware",
  "time": "2019-11-14T05:58:42Z"
}
{
  "entryPointName": "websecure",
  "level": "debug",
  "middlewareName": "metrics-entrypoint",
  "middlewareType": "Metrics",
  "msg": "Creating middleware",
  "time": "2019-11-14T05:58:42Z"
}
{
  "entryPointName": "traefik",
  "level": "debug",
  "middlewareName": "metrics-entrypoint",
  "middlewareType": "Metrics",
  "msg": "Creating middleware",
  "time": "2019-11-14T05:58:42Z"
}
{
  "entryPointName": "web",
  "level": "debug",
  "middlewareName": "metrics-entrypoint",
  "middlewareType": "Metrics",
  "msg": "Creating middleware",
  "time": "2019-11-14T05:58:42Z"
}
{
  "level": "error",
  "msg": "Error in Go routine: runtime error: invalid memory address or nil pointer dereference",
  "time": "2019-11-14T05:58:42Z"
}
{
  "level": "error",
  "msg": "
    Stack: goroutine 73 [running]:
    runtime/debug.Stack(0xc000112000, 0x24d0e85, 0x17)
      /usr/local/go/src/runtime/debug/stack.go:24 +0x9d
    github.com/containous/traefik/v2/pkg/safe.defaultRecoverGoroutine(0x209b8c0, 0x3ee5610)
      /go/src/github.com/containous/traefik/pkg/safe/routine.go:160 +0xb1
    github.com/containous/traefik/v2/pkg/safe.GoWithRecover.func1.1(0x25ab3a0)
      /go/src/github.com/containous/traefik/pkg/safe/routine.go:150 +0x57
    panic(0x209b8c0, 0x3ee5610)
      /usr/local/go/src/runtime/panic.go:679 +0x1b2
    github.com/containous/traefik/v2/pkg/metrics.OnConfigurationUpdate(0xc0007bc270, 0xc0003e0e80, 0x3, 0x4)
      /go/src/github.com/containous/traefik/pkg/metrics/prometheus.go:232 +0x618
    github.com/containous/traefik/v2/pkg/server.(*Server).loadConfiguration(0xc0001f6000, 0x24aa889, 0x4, 0xc000995840)
      /go/src/github.com/containous/traefik/pkg/server/server_configuration.go:59 +0x49a
    github.com/containous/traefik/v2/pkg/server.(*Server).listenConfigurations(0xc0001f6000, 0xc00008c230)
      /go/src/github.com/containous/traefik/pkg/server/server_configuration.go:249 +0x51
    github.com/containous/traefik/v2/pkg/server.(*Server).Start.func3(0xc00008c230)
      /go/src/github.com/containous/traefik/pkg/server/server.go:183 +0x34
    github.com/containous/traefik/v2/pkg/safe.(*Pool).Go.func1()
      /go/src/github.com/containous/traefik/pkg/safe/routine.go:90 +0x7b
    github.com/containous/traefik/v2/pkg/safe.GoWithRecover.func1(0x25ab3a0, 0xc00047dc80)
      /go/src/github.com/containous/traefik/pkg/safe/routine.go:153 +0x57
    created by github.com/containous/traefik/v2/pkg/safe.GoWithRecover
      /go/src/github.com/containous/traefik/pkg/safe/routine.go:147 +0x49
  ",
  "time": "2019-11-14T05:58:42Z"
}

Offending line:
https://github.com/containous/traefik/blob/v2.0.4/pkg/metrics/prometheus.go#L232
Of note is that we use StatsD and InfluxDB, but not Prometheus.

Duplicate of #5755
Fixed by #5759


cli: Add --cli-root-volume-access-modes

What this PR does / why we need it:
To support live migration the PVCs have to be with ReadWriteMany mode, this change add an option to use that mode.
Checklist*

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/test kubevirt-e2e-kubevirt-aws-ovn

/lgtm
/approve
/hold
one kubevirt e2e passes, remove the hold

/test kubevirt-e2e-kubevirt-aws-ovn
retesting, the first test failed during ipi setup, so our test cases never executed

/retest

/test kubevirt-e2e-kubevirt-aws-ovn

/hold cancel


No clue how to use this library

Even with the added wiki pages I have absolutely no clue how to get this to work. I tried copying the kotlin code from the example for converting to java later but I get an Unresolved reference for import android.support.v4.app.DialogFragment and so the extends DialogFragment() doesn't work either. Am I missing something?

Solved it by replacing import android.support.v4.app.DialogFragment with import androidx.fragment.app.DialogFragment


Day 05 react polymer concurrently

Execution time went down from ~580ms to ~175ms on my quad core machine.

Thanks! Neat! Unfortunately, I'm going to have to pass. As the README says, I specifically did not focus on performance because it's an unending rabbit hole with no obvious benchmarks.
This repo is more for folks just learning Rust and asking questions.

I see! Speaking of questions of people learning Rust: do you know repos of tweaked solutions? I come from Java and I am curious about "low level" tuning.

No, sorry. You might have better luck here: https://www.reddit.com/r/adventofcode/

@Journeycorner If you are interested in an efficient solution for this particular problem, I pasted mine here. It finishes in something like 5ms single-threadedly on my old laptop, and it's also far simpler than any other solution I saw, weighing roughly 20 lines of Rust.


Fix indents in "quick start"

Done:

no more spaces before an commands (important when you copy-paste it)
~add export for OVPN_DATA~

The clean-up of the spaces are welcome.  Docker Hub used to have a bug and hence why those were there, this has been resolved for some time though.
As for the export, why? The variable is only referenced from the commands running directly in the shell, none of the sub processes.

As for the export, why? The variable is only referenced from the commands running directly in the shell, none of the sub processes.

You are right, change reverted.
Hope now PR can be merged.

Thanks.

@kylemanna thank you for this awesome project: it's fastest VPN setup ever that I did :bomb:


Modal dialog too wide on a viewport with a width between 544px and 600px

The modal dialog is too wide on a viewport with a width between 544px and 600px. this causes on current master because of _modal.scss:130
@include media-breakpoint-up(sm) {
  // Automatically set modal's width for larger viewports
  .modal-dialog {
    width: $modal-md;
    margin: 30px auto;
  }
  [...]
}

The media breakpoint sm is defined to 34em in _variables.scss:91 which is exactly 544px, but the modal width is defined with $modal-md which is 600px (_variables.scss:505)
The output css is (dist/css/bootstrap.css:5176):
@media (min-width: 34em) {
  .modal-dialog {
    width: 600px;
    margin: 30px auto;
  }
  [...]
}

You can see the problem that the viewport is 544px width, but the modal is 600px width.
Look at the following codepen: https://codepen.io/anon/pen/pbgaVJ
Open your inspector tools and set the iframe (viewport) to width:544px;
document.querySelector('.result-iframe').style.width = '544px'

Hi @dennify!
You appear to have posted a live example (https://codepen.io/anon/pen/pbgaVJ.html), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 8, column 1: E046: .modal elements must have a tabindex attribute.

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

Sorry see thisis  a duplicate. I'am not searching closed issues because this error still exists on master

master is Bootstrap v3. For Bootstrap v4, you want v4-dev.


Make include headers -  PUBLIC

Make
target_include_directories(Candle-s PRIVATE include)
to
target_include_directories(Candle-s PUBLIC include)
Because I can`t include library as add_subdirectory(), I must write bypassing
 target_include_directories(${PROJECT_NAME} PRIVATE extlibs/Candle/include)
Mine CMakeLists.txt
cmake_minimum_required(VERSION 3.18.4)

project(Spark)

set(INCROOT include/Spark)
set(SRCROOT src)

set(SRC
    ${SRCROOT}/Main.cpp
)

add_executable(${PROJECT_NAME} ${SRC})
target_include_directories(${PROJECT_NAME} PRIVATE ${INCROOT})

find_package(SFML COMPONENTS system window graphics REQUIRED)
target_link_libraries(${PROJECT_NAME} PRIVATE sfml-system sfml-window sfml-graphics)

add_subdirectory(extlibs/Candle)
target_link_libraries(${PROJECT_NAME} PRIVATE Candle-s)
#target_include_directories(${PROJECT_NAME} PRIVATE extlibs/Candle/include) <----- It`s too much, it`s bad

add_custom_command(
    TARGET ${PROJECT_NAME}
    POST_BUILD
    COMMAND ${CMAKE_COMMAND} -E copy_directory
    ${CMAKE_SOURCE_DIR}/assets
    ${CMAKE_SOURCE_DIR}/build/assets
)

Candle CMakeLists.txt
cmake_minimum_required(VERSION 3.12)

project(Candle)

# set C++11 standard
set(CMAKE_CXX_STANDARD 11)

# set output files directories
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY bin)
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY lib)
set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY lib)

# might need to set manually SFML_ROOT to the install location of SFML for Windows users
# set(SFML_ROOT "")

# if the user wants to use static SFML libs
# set(SFML_STATIC_LIBRARIES TRUE)

find_package(SFML 2.5 REQUIRED COMPONENTS  graphics)

set(CANDLE_SRC

	src/LightingArea.cpp
	src/LightSource.cpp
	src/RadialLight.cpp
	src/DirectedLight.cpp
	src/Line.cpp
	src/Polygon.cpp
	src/Color.cpp
	src/VertexArray.cpp
	src/Constants.cpp

)

# Static library target
add_library(Candle-s STATIC ${CANDLE_SRC})
target_include_directories(Candle-s PRIVATE include) <------------------------- Must be public
target_link_libraries(Candle-s sfml-graphics)

option(RADIAL_LIGHT_FIX "Use RadialLight fix for errors with textures" OFF)

if(RADIAL_LIGHT_FIX)
	target_compile_definitions(Candle-s PUBLIC -DRADIAL_LIGHT_FIX)
endif()

# Demo target
option(BUILD_DEMO "Build demo application" OFF)

if (BUILD_DEMO)
	set(DEMO_SRC demo.cpp)
	add_executable(demo ${DEMO_SRC})
	target_include_directories(demo PRIVATE include)
	target_link_libraries(demo PRIVATE sfml-graphics Candle-s)
endif()

Honestly, I know very little about CMake, so thanks for fixing this in # 15
@all-contributors please add @Dead-Deus for infrastructure and bug report


[fix] #2850: Fix deserialization/decoding of Fixed

Signed-off-by: Shanin Roman<EMAIL_ADDRESS>

Description of the Change
Check that Fixed is not negative during decoding/deserialization.

Issue
Closes #2850.

Benefits
Corrent decoding/deserialization behavior.

Possible Drawbacks
None.

Usage Examples or Tests [optional]
cargo test --package iroha_primitives --lib -- fixed::tests --nocapture

It seems that this PR also close my recently opened issue #2950 (I didn’t notice that #2850 and #2950 were the same)


tcp_port_scan_scapy.py does not parse results correctly

Hello @josevnz ,
I think there's an issue with tcp_port_scan_scapy.py not parsing the scan results correctly. I am scanning a machine that has 3 closed ports but the script reports all ports open.
Results running the simple Pything TCP scanner script:
google.com:80: OK
amazon.com:80: OK
dragon:22: OK
dragon:9090: ERROR
dragon:8086: ERROR
dragon:21: ERROR

Results running the same input file with the Scapy script:
OK -> <IP_ADDRESS>:80
OK -> <IP_ADDRESS>:80
OK -> <IP_ADDRESS>:22
OK -> <IP_ADDRESS>:9090
OK -> <IP_ADDRESS>:8086
OK -> <IP_ADDRESS>:21

As you can see, it should report ports 9090, 8086, and 21 as closed.

I can reproduce the error, I think the issue is how I'm interpreting the response packets. Will debug and fix.

Fixed, the new version also offers a more detailed port analysis:
[josevnz@dmaf5 StopUsingTelnetToTestPorts]$ ./scripts/tcp_port_scan_scapy.py data/port_scan.csv
OPEN -> google.com:80
OPEN -> amazon.com:80
OPEN -> raspberrypi:22
OPEN -> raspberrypi:9090
OPEN -> raspberrypi:8086
CLOSED -> raspberrypi:21
FILTERED -> dmaf5:22
FILTERED -> dmaf5:80


Fixed typo in second example

Made the variable name the same between the two lines of the example, would not work otherwise.

Docs Build status updates of commit 16cd7aa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Test-TextExtraction.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Feature Request: Smarter indent guides

When something is indented in a 'non-standard' way like this:

multiple indent guides are shown, even though there's really only one logical indent here. Could the indent lines be smarter and only draw one here?

The computation of indent guides is programming language agnostic.
So that algorithm does not know that , in this context does not introduce a new "statement". For example, in other programming languages the indentation could be intentional

We already have a feature that highlights brackets over the cursor-placed region. It means that VSCode is able to detect and work with brackets over any region. How about rendering indent guides only in-between brackets?
Example

with brackets over any region. How about rendering indent guides only in-between brackets?

Please check out bracket pair guides.


perf: Weave in pre-computed function hash for RPCs

Instead of computing it at runtime for every call
See #3381, #3377 and #3375

We should be able to revert #3377 after this is merged since there is no more runtime uses left


Remove duplicated entry

changes

Removed the [10.0.17763.437] and [10.0.17763.437-SLInit] duplicated entries
Added some comments

Also, @zhangyoufu's suggested SingleUserOffset.x64=13469 instead of SingleUserOffset.x64=1322C (see here)

closed in favor of #2


Self-managed hosting

Hear me out, this is a little wild and a complete paradigm breakdown for me. I'm trying to figure out whether it should have some relationship to django-simple-deploy to allow for a better transition to a more traditional controlled approach to deployment.
One killer feature of Wordpress is that it can update itself, you can install plugins from a store, and modify just about everything about it. As a developer this makes me cringe for all kinds of reasons, but it's also an incredible way to get people that don't know about development to run something themselves. A great on-ramp. It's got significant drawbacks, but I'm so interested in exploring possibilities for making getting started with Django development simpler that I'm really interested to see what could happen.
I haven't figured out exactly what that looks like yet. Perhaps a docker image running systemd to manage the application, and then some fancy footwork with virtualenvs to allow for installing new sets of dependencies through a web UI without making the upgrade irreversible.
While I want this so that it makes it simpler for people to get started with Django, I really don't want it to stop there. I want little places where people can start by doing CMS-style stuff for a while, hit a limitation, then dip their toes into some code to make something custom, all in the UI. Their first taste of development. As they experience that, then somewhere along the way I want it be easy to switch from a non-developer focused approach to a more traditional approach with git, reproducible docker images, even up to and including putting it on a PaaS.
For now I'm just playing around with this idea, but I wonder if you have any thoughts about it given this project and what you're trying to do with it: simplify the deployment on-ramp. It seems like perhaps an good ramp from the self-mutating approach to a more traditional deployment model might fit really well with using this project. Does that sound right? Do you see problems or things that I should keep in mind as I'm thinking about this if I want to use django-simple-deploy to create that pathway for project progression?
I don't immediately see this as reasonable to make a platform of this project, it's really a totally different approach afaict, but if there are things that I can do to make the transition simpler as a new person transitions to be a developer, that would be really cool.

Hi Ryan. I've always found that this project brings up interesting ideas once you start thinking about it more. At first it seems like it's just focused on beginners, but it has use cases for people at all experience levels, and all kinds of reasons for using Django.

One killer feature of Wordpress is that it can update itself, you can install plugins from a store, and modify just about everything about it. As a developer this makes me cringe for all kinds of reasons, but it's also an incredible way to get people that don't know about development to run something themselves. A great on-ramp. It's got significant drawbacks, but I'm so interested in exploring possibilities for making getting started with Django development simpler that I'm really interested to see what could happen.

I think there's a compelling use case for defining simpler ways of starting projects with Django, that lead naturally into a fully-fledged Django project. That's why I'm excited about projects like nanodjango, which take the single-file approach that's been discussed among insiders for years now, but also give a straightforward path for converting your project into a standard Django project as it evolves.
That said, I'm not so convinced of trying to turn Django into something that's trying to serve non-programmers as well as developers. I can see some third-party projects using Django under the hood to do something like this, but I don't know how much it matters that Django is being used to build out the wrapper platform. Is Wagtail doing some of what you're describing?

While I want this so that it makes it simpler for people to get started with Django, I really don't want it to stop there. I want little places where people can start by doing CMS-style stuff for a while, hit a limitation, then dip their toes into some code to make something custom, all in the UI.

This reminds me of Anvil.

For now I'm just playing around with this idea, but I wonder if you have any thoughts about it given this project and what you're trying to do with it: simplify the deployment on-ramp. It seems like perhaps a good ramp from the self-mutating approach to a more traditional deployment model might fit really well with using this project.

As simple_deploy gets out of the pre-1.0 proof-of-concept phase and gains some stability, one of the things I'm most curious to see is where its boundaries are. What kinds of projects are "simple" enough for it to be relevant? How complex of a project can it handle, while staying true to the original vision of not trying to handle overly complex cases? I think the plugin model really opens up those possibilities. You can have some plugins that handle the simplest use cases, but there's not much stopping someone from writing a much more complex plugin, I believe.
The main thing I'm trying to do right now is be really clear about what tools simple_deploy offers to plugins. For example it has utilities like add_file(), add_dir(), and modify_file(). Those are all tasks a plugin needs to carry out in order to prepare a project for deployment. If there are capabilities you'd like to see to support a specific aspect of your vision, please feel free to propose them, or even just discuss ideas.


Command injection causes Heroku to die [🐛]

:bug: Bug report
Description
The Heroku instance dies if process.exit() is injected in the request URL. While this issue isn't particular to Juice Shop's source code, the Node Goat project is great at recovering from such a crash (it recovers instantly).
Is this a regression?
I'm not sure. It's a problem inherent to Heroku's instance.
:microscope: Minimal Reproduction

Goto: https://juice-shop.herokuapp.com/rest/products/1/reviews
Replace with: https://juice-shop.herokuapp.com/rest/products/process.exit()/reviews

App dies for everyone >10 minutes!

 Your payload easily even beats my protection on develop of truncating after 40 chars as it is only 14 chars short... 😁
https://juice-shop-staging.herokuapp.com/rest/products/process.exit()/reviews = 💀
Gotta fix this somehow w/o having to disable NoSQLi on Heroku/Docker because that would mean no orders and no reviews, which is not acceptable.
Thanks for this awesome find!

The particular attack string is now sanitized after the truncation to 40 chars and should not work any more. The words process and exit are replaced with funny characters instead of removing them to avoid having to deal with recursion attacks. Feel free to try bypassing it, as it is definitely not bullet proof.
💡 For a long-term safer solution the vulnerable MarsDB query calls should probably be sandboxed.

/rest/products/global['proc'+'ess']['ex'+'it']()/reviews 😉

I'll sandbox it if possible soon and disable the challenges on Heroku...

@bkimminich Darn.. I wanted to teach this usecase as an example of Command Injection attack at a Bachelor level security lecture. Is there any other command injection vulnerability in JS? (I don't want to touch SQLi for now).
Thank you for your help! :)

It is still possible to exploit in local installations, only in Docker and Heroku it is turned off by default now. You even there turn it back on by using a custom config with only
challenges:
  safetyOverride: true

in it. Actually, I'll provide that one as config/unsafe.yml with v9.1.1 so you could start it with NODE_ENV=unsafe npm start or similarily pass that into your Docker or Heroku as an environment variable.

That'd be awesome! Thanks so much! 👍


docs: add runtime format in config doc

add format example in docs, or user may confused how to
add runtime in config file. Also add this for
docs/features/pouch_with_kata.md and docs/features/pouch_with_runV.md.
Signed-off-by: Ace-Tang<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

fixes: #2094
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
no need.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #2110 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2110      +/-   ##
==========================================
+ Coverage   65.09%   65.13%   +0.04%
==========================================
  Files         208      208
  Lines       16411    16411
==========================================
+ Hits        10682    10690       +8
+ Misses       4399     4392       -7
+ Partials     1330     1329       -1

Flag
Coverage Δ

#criv1alpha1test
33.15% <ø> (-0.16%)
:arrow_down:

#criv1alpha2test
33.94% <ø> (-0.01%)
:arrow_down:

#integrationtest
39.84% <ø> (+0.04%)
:arrow_up:

#unittest
23.87% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

cri/v1alpha1/cri.go
63.44% <0%> (-0.35%)
:arrow_down:

daemon/mgr/container.go
56.3% <0%> (+0.2%)
:arrow_up:

ctrd/image.go
78.94% <0%> (+2.19%)
:arrow_up:

ctrd/watch.go
80.3% <0%> (+4.54%)
:arrow_up:

lgtm


Why is the documentation so simplistic?

Setting header fields doc is useless
Are you sure this description is useful?
Setting header fields is simple, invoke .set() with a field name and value:

 request
   .get('/search')
   .set('API-Key', 'foobar')
   .set('Accept', 'application/json')
   .then(callback);
You may also pass an object to set several fields in a single call:

 request
   .get('/search')
   .set({ 'API-Key': 'foobar', Accept: 'application/json' })
   .then(callback);

Hello @jackwener – v5.0.0 was just released to NPM and an updated README is now available here on GitHub (see https://github.com/visionmedia/superagent#superagent).
What's new

Browser version is now only 19KB (that's 60% in file size savings from v4.x which was 48KB)!
Codebase refactored using xo, prettier, remark, and more
Browser compatibility linting via eslint-plugin-compat
Browserslist integration (current targets are > 1%, last 2 versions, ie 9)

How to install
npm install superagent@latest

Or if you're using yarn:

yarn add superagent@latest

Polyfills
Please see the Required Browser Features section in the README if you plan to support IE 9 and/or IE 10 and use superagent.


Broken Tool Tip

It took some time trying to figure out why my tooltips were broken in AUTOMATIC1111
stable-diffusion-webui
After exhausting all community posts to try and resolve the problem I unloaded all of my extensions and fixed my tool tips. I started loading extensions 1 by 1.
I discovered that this extension breaks the tooltips.
I don't like making bug reports so I hope this finds you in good spirits.

I found four extensions in my local installation which use the hinting system, two of them being a potential source of this problem. The issue, anyway, seems not too complex to fix, perhaps just renaming the hints file and looking at the code content for the other two hints files.
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/7534#issuecomment-1455946524

Unfortunately, I am currently away from my workstation so I am unable to test if changing the file name as suggested by @Harvester62 will fix it for the next month or so. Since it affecting more than just this extension, if someone could make a pull request with the changes and test that it fixes the bug, that would be a great help.

Hi @imrayya I modified your hints.js both renaming the file to prompt_generator_hints.js and adapting the code inside it. I have just tested it and the problem is now fixed. I had also to do the same with the hints.js file of the extension/script gif2gif otherwise the overwriting of the hints.js inside ROOT\javascript would have not been fixed; for this other extension I will write to the related author. I am ready to do a PR but I think I would have to fork your repository and create a new branch to be able to do it, right?

Thanks for the help @Harvester62. I approved your pull request and hope that solves the issue for everyone


emqttd-centos7-v2.1.2-1.el7.centos.x86_64.rpm conflicts with other packages

This is CentOS 7.3:
rpm -i emqttd-centos7-v2.1.2-1.el7.centos.x86_64.rpm
[sudo] password for simon:
file /etc from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /usr from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /usr/lib from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /var/lib from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /usr/lib/debug from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /usr/src/debug from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /usr/lib64 from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /usr/src from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /usr/sbin from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /var from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /var/log from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package filesystem-3.2-21.el7.x86_64
file /etc/init.d from install of emqttd-2.1.2-1.el7.centos.x86_64 conflicts with file from package chkconfig-1.7.2-1.el7.x86_64

@nestor5  rpm -ivh --force emqttd-centos7-v2.1.2-1.el7.centos.x86_64.rpm


Add element instance postprocessing

Elements (and dependency injection) was implemented in scope of #39
However, element post processing was not added. Things missing:

Field dependency injection.
Calling "post construct" method after field dependencies are injected.

Add interface ElementPostprocessor and implementations for all points above. This interface takes an object and does not return anything. All implementations should be applied to all new element objects, in a well defined order.

Reduced scope of this ticket: no longer includes concrete implementations of post-processors, just the framework for them.


Set 2 as max digits after .

This PR fixes #1444.
CR @alonsogarciapablo

It should be nice, but we need to think about the implementation. Right now we have different precision wether the number is bigger than 100, 1 or 0. How it would fit with it?


[Bug]: Not supported to run in Cloudflare Worker Edge environment

What happened?
Using the Next.js 14 + TypeScript tech stack, with the API set to the edge environment, an error occurs when calling paddle.transactions.create after importing the @paddle/paddle-node-sdk package: Module build failed: UnhandledSchemeError: Reading from "node:crypto".
Steps to reproduce
Reproduction code snippet:
// route.ts

import { Environment, Paddle } from '@paddle/paddle-node-sdk'

export const runtime = 'edge'

const paddle = new Paddle(process.env.PADDLE_SECRET_KEY!, {
  environment: Environment.production,
})

const transaction = await paddle.transactions.create({
  items: [
    {
      quantity: 1,
      priceId: 'priceId',
    },
  ],
})

What did you expect to happen?
I hope to use @paddle/paddle-node-sdk in an edge environment.
Logs
⨯ node:crypto
Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
Import trace for requested module:
node:crypto
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Hi @wytxer,
Thank you for opening this bug report with all the details.
I am sorry that you are running into this issue.
Our node SDK was built for Node.js Runtime, as Edge runtime uses web API some of the dependencies we use like the crypto module will not work.
Even though removing the node: prefix might solve the problem for you, I fear it will break for others. So that is not an option.
I will find a solution to this problem and get back to you once it is released.
Thank you.

Thank you for your reply. I am building a product based on Cloudflare Worker. Is there a plan for when it will be released?

@vijayasingam-paddle I'm trying to implement paddle in Cloudflare workers, As you mentioned,

We do support CloudFlare workers using NodeJS runtime.

I'm planning to use Cloudflare workers as the backend, so could you let me know if this works?

Hi @westlinkin,
Yes, our SDK works in CloudFlare workers using NodeJS runtime.
This issue is relevant only to the Edge runtime
Please feel free to reach out to us if you face any difficulties while integrating with your application.
Thank you.

Oh, I use CloudFlare Worker as the backend, node:crypto prevents me continuing

Hi @richhost,
We haven't made any progress on this yet. As we had not planned to support this, it is taking longer to prepare for this change.
Meanwhile, can you please try version 1.2.2? We were using crypto as a dependency at this point so it might work for you.
There are a few functional differences between 1.2.2 and the latest version. You can read through our Changelog to find the differences
I will get back to you once a proper fix is released.
Thank you.

Hi @wytxer, I am afraid that it will take a while for us to change this as we had not planned to run our SDK using web APIs and supporting both runtimes will be tricky.
We do support CloudFlare workers using NodeJS runtime. However, looking at your snippet, you are deploying a NextJS app to CloudFlare workers which as I understand can only run on an edge runtime.
If you don't mind me asking, is there any particular reason not to deploy this in Vercel or Netlify where the infra plays well with NextJS applications compared to CF workers?
Thank you.

Because the website that is already online is based on Cloudflare Worker, migrating the entire site to a platform like Vercel to use the Paddle API would be very costly.

@vijayasingam-paddle I'm trying to implement paddle in Cloudflare workers, As you mentioned,

We do support CloudFlare workers using NodeJS runtime.

I'm planning to use Cloudflare workers as the backend, so could you let me know if this works?

Bro, you can consider trying the version I forked: https://github.com/wytxer/paddle-node-sdk. I changed crypto to crypto-js, and one of my projects is using it. The API is completely consistent with the official version. You can click to check my modification history.
npm i @wytxer/paddle-node-sdk

Hello, you could try this in your next.config.js:
webpack: (config) => {
    config.externals.push({
      'node:crypto': 'commonjs crypto',
    });
    return config;
  },

I see 2.0.0-rc.0 supports edge runtime. Can vijayasingam-paddle recommend the same temporarily?

Hey @arfath-linklet, of course the v2 release candidate can't be confirmed as completely stable but we're more than happy for you to give it a go and let us know if you run into any issue

This can be closed as it's a Cloudflare problem, which they've now solved.
Add this to your wranger.toml file:
compatibility_flags = [ "nodejs_compat" ]
compatibility_date = "2024-09-23"
# or
compatibility_flags = [ "nodejs_compat_v2" ]

Docs:
https://developers.cloudflare.com/workers/runtime-apis/nodejs/
https://developers.cloudflare.com/workers/configuration/compatibility-flags/#nodejs-compatibility-flag

Vercel Edge is Cloudflare Workers
Netlify / Supabase / Deno Deploy are all Deno (with 100% Node compat)

As mentioned, this is now moot since 2.0 has RuntimeProviders that brings/uses different crypto imports.

Going to close this issue as this is now supported in the 2.0.0 release, thanks all for your input on this


Error when adding plots

I follow these steps:
git clone https://github.com/hulatang/ceres-combineharvester.git
cd ceres-combineharvester/
sudo chmod +x install.sh
./install.sh
. ./activate
ceres init
vim ~/.ceres/mainnet/config/coins_config.yaml       # uncomment -flax
ceres init --coins
ceres generate_ssl
Then, when I try to add plot directory, I get KeyError for "plot_directories":
ceres coin plots add -d /plots/$dir
Unable to check permissions for /home/dong/.ceres/mainnet/config/ssl/ca/chia_ca.crt: file /home/dong/.ceres/mainnet/config/ssl/ca/chia_ca.crt does not exist
Unable to check permissions for /home/dong/.ceres/mainnet/config/ssl/ca/chia_ca.crt: file /home/dong/.ceres/mainnet/config/ssl/ca/chia_ca.crt does not exist
Unable to check permissions for /home/dong/.ceres/mainnet/config/ssl/ca/chia_ca.key: file /home/dong/.ceres/mainnet/config/ssl/ca/chia_ca.key does not exist
Unable to check permissions for /home/dong/.ceres/mainnet/config/ssl/ca/chia_ca.key: file /home/dong/.ceres/mainnet/config/ssl/ca/chia_ca.key does not exist
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@             WARNING: UNPROTECTED SSL FILE!              @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0664 for '/home/dong/ceres-combineharvester/mozilla-ca/cacert.pem' are too open. Expected 0644
One or more SSL files were found with permission issues.
Run `ceres init --fix-ssl-permissions` to fix issues.
Traceback (most recent call last):
  File "/home/dong/ceres-combineharvester/venv/bin/ceres", line 33, in <module>
    sys.exit(load_entry_point('ceres-blockchain', 'console_scripts', 'ceres')())
  File "/home/dong/ceres-combineharvester/ceres/cmds/ceres.py", line 144, in main
    cli()  # pylint: disable=no-value-for-parameter
  File "/home/dong/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/home/dong/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/home/dong/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/dong/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/dong/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/dong/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/home/dong/ceres-combineharvester/venv/lib/python3.8/site-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/dong/ceres-combineharvester/ceres/cmds/plots.py", line 190, in add_cmd
    add_plot_directory(ctx.obj["root_path"], final_dir)
  File "/home/dong/ceres-combineharvester/ceres/plotting/util.py", line 74, in add_plot_directory
    if str(Path(str_path).resolve()) not in get_plot_directories(root_path, config):
  File "/home/dong/ceres-combineharvester/ceres/plotting/util.py", line 57, in get_plot_directories
    return config["plot_directories"]
KeyError: 'plot_directories'

I tried to add ['harvester'] after config to fix the error message, but I am not sure whether this would successfully add the directory. To check it, however, I get KeyError on harvester when running ceres plots show:
Traceback (most recent call last):
  File "venv/bin/ceres", line 33, in <module>
    sys.exit(load_entry_point('ceres-blockchain', 'console_scripts', 'ceres')())
  File "/ceres-combineharvester/ceres/cmds/ceres.py", line 144, in main
    cli()  # pylint: disable=no-value-for-parameter
  File "/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/ceres-combineharvester/venv/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/ceres-combineharvester/venv/lib/python3.8/site-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/ceres-combineharvester/ceres/cmds/plots.py", line 212, in show_cmd
    show_plots(ctx.obj["root_path"])
  File "/ceres-combineharvester/ceres/cmds/plots.py", line 23, in show_plots
    for str_path in get_plot_directories(root_path):
  File "/ceres-combineharvester/ceres/plotting/util.py", line 58, in get_plot_directories
    return config['harvester']["plot_directories"]
KeyError: 'harvester'

By the way, why is it still looking for "chia_ca.crt" which is set in ceres/util/initial-config.yaml and should be fixed.

currently, you should add plot directories manually
open file ~/.ceres/mainnet/config/coins_config.yaml
plot_directories:

/home/your/plot/path/0001

/home/your/plot/path/0002

/home/your/plot/path/0003

.different function currently load config attributes in different config files
will be integrated into one config file.
ceres/util/initial-config.yaml is just a template for ceres initializition.
after ceres init
there will be two config files under ~/.ceres

~/.ceres/mainnet/config/config.yaml
this file is derived from initial-config.yaml, only plot_directories is active

~/.ceres/mainnet/config/coins_config.yaml
some configure related to farmer is set in this file

all will be integrated into one file in future
Thank you


Multi copy fix

possible fix for #37 & #35

@gmethvin basically I've added the check on ENTRY_DELETE when directory then all pathHashes starting with this path should be deleted.
I've run also tests on my Win-Computer and they were green. From here I'd need some assistence and maybe some suggestion - instead of using future.get() and waiting for 5 sec, we could use awaitlity with some timeout? (that should make tests run a little faster)

Thanks. This looks like the right approach.
I would suggest adding a different test case for what you're trying to test, rather than modifying an existing test case. This way it's easy to see that the previous test still passes.
If you check https://ci.appveyor.com/project/gmethvin/directory-watcher/builds/22961252, you see messages like this:
DEBUG io.methvin.watcher.DirectoryWatcher - Failed to hash created file [C:\Users\appveyor\AppData\Local\Temp\1\4625184721898994304\parent-646139223358167817\child-1012901355892023436.dat]. It may have been deleted.

It's possible in the CI environment it just takes longer for those events to get emitted, so the test ends up finishing before the watcher detects them. You could try adding a longer delay, and maybe also a short delay between the copySubDirectoryFromOutside tests. I wouldn't be opposed to a utility like Awaitility if you wanted to try it.
Also, somehow the code formatting has changed on many files. If you run sbt compile test:compile it will automatically format them properly.


[New API] : GeoPlaceAPI

Brief Description 🤓
Overview
The Geocoding, Reverse Geocoding, and Place Autocomplete API provides developers with functionalities to convert addresses to geographic coordinates, find addresses from coordinates, and offer predictive search suggestions as users type.
How will you develop it?🤩
Development Approach

Setup Express Server: Create an Express.js server to handle HTTP requests.
Integrate Google Maps API: Utilize Axios to make HTTP requests to Google Maps API endpoints for geocoding, reverse geocoding, and place autocomplete.
Define Endpoints: Implement Express routes for geocoding, reverse geocoding, and autocomplete functionality.
Handle Responses: Parse and handle responses from Google Maps API, providing appropriate data back to the client.
Error Handling: Implement error handling for API requests and responses to ensure reliability.
Testing: Test the API endpoints thoroughly to ensure functionality and performance.

Deployment
No
Select the open source program you are contributing to
Other
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINES of this project.

Greetings @Suyash878🎀 ! , We are excited to have you dive into another issue with us!🚀
Your involvement in our project has been invaluable, and we're confident that your skills and insights will help us conquer this challenge😇.  Use command /gssoc24 to self assign the issue.  This issue represents an exciting opportunity for us to improve and enhance our project, and we are thrilled to have you on board.
We request you to follow CONTRIBUTING GUIDELINES.
Looking for your PR soon!
In case of any issues, you can contact us on Discord.❣

/gssoc24

Hey @Suyash878 ! I wanted to inform you that we have closed issue.Thank you for your understanding, and we look forward to your continued engagement with our repository🤗.
In case of any issues, you can contact us on Discord.
Thank you! ❣
Happy Coding! ✨
Will See you soon❣


Cleanup & Refactoring

These changes come from the work I've done on the Neo4j 2.2 adapter (see https://github.com/xnlogic/blueprints/tree/neo4j-2.2 for more details). In fact, I was about to submit a PR with my work to tinkerpop, but then I discovered I was a day too late.
This pull request includes a few minor improvements (getting rid of deprecated method calls and other Java warnings), and some code re-factoring.

We have gone through many additional improvements and re-factoring, and the changes are now in our master branch. I am closing this PR, and will submit a different one that includes all recent changes.


(Question) Terraform Module outside of tests

Hey, we're looking to execute terraform from golang in our application (not necessarily as testcases) and would love to re-use the terraform wrapper already in here however it has a tight coupling with testing.T.
Perceived Options:

Contribute to terratest decoupling terraform from testing
Execute go test from production code

Any recommendations or preferred direction here?
NOTE: Do not believe mocking testing.T is option due to *testContext
type T struct {
	common
	isParallel bool
	context    *testContext // <-- private
}

Thanks!

Hi @tiny-dancer
I am nervous about starting to support using the modules in here for anything other than test use cases, primarily because these functions are optimized for test use cases and we want to keep it that way. For example, the command functions implement streaming stdout and stderr to the test logger so that we can parse it out later using the terratest_log_parser. In a production version, we would have to remove this and then introduce a layer of abstraction to support the testing use case. This may seem nice in that it supports a wider use case, but it complicates the library because you would have to be concerned about supporting the production use case, or the test use case adding decision overhead to feature development.
I would instead suggest creating a new project/library that uses the terratest patterns that is optimized for production use cases. We already do some of this at Gruntwork: for example, the gruntwork-cli library has a version of the shell module that is more optimized for production use cases (https://github.com/gruntwork-io/gruntwork-cli/tree/master/shell).

I would instead suggest creating a new project/library that uses the terratest patterns that is optimized for production use cases.

thanks @yorinasub17, we will embark on this direction.


"assume" command

Hi, just wondering if there would be any objects to adding one additional command: migrate assume, which would simply:

Create the schema_migrations table if it does not exist
Set the version as if we had run migrations up to that version (but do not actually run any migrations)

The primary usecase of this feature is when we have an existing database that we want to begin managing with migrate, but also want everything to be create-able ground-up from the migrations.
Right now we just have to work around it by creating and/or updating the schema_migrations table manually.

Set the version as if we had run migrations up to that version

We don't set a "last" version migrated in the DB. Migrate will compare each migration file, and will run them if the version is not found in the schema_migrations table. That means we would insert all the versions.
I'm trying to figure out a use-case for that: You have some migrations used in a DB, and want to start using the same repo, for another DB? Why not using another repo then, or squashing the first migration?

Ah didn't notice it inserts all versions (I was looking at a DB that happened to only have 1 migration run). But yeah you're correct, we would insert all versions for this to work.
My use-case now is this: I have an existing DB schema in use that had previously been managed by some other method (liquibase, hand-crafted sql, etc.), and I would like to start using migrate instead.
One option is that I could just make the migrations assume that there is existing schema, but then I can't use the migrations to build a new environment from scratch.
What I would prefer to do is dump the schema into migration 1, then use migrate assume 1 on existing databases so that I can run future migrations on them, but not try to run migration 1. Does that make sense?

Ok I see.
We had a similar case when squashing migrations for a project lately. All migrations were squashed into a single one, and we inserted the new version by hand in the DB.
So, to make it clear:

migrate assume would create schema_migrations if needed, and insert all versions into DB
migrate assume [version] would do the same, but would insert all migrations up to [version] only.

sounds good? Do you want to start working on this PR?

Yep sounds good.
I would like to get it done but I'm not completely sure yet that I can, it might depend on how much this issue bites us.
But at least now I do know it may be worth working on if I get to it :)


Fixes Typos

Replaced occurrences of "tootlip" with "tooltip".

Thanks!

:tada: This PR is included in version 3.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


VRTK_InteractableObject sets parent to null

There are cases where VRTK_InteractableObject will LoadPreviousState() without having ever calling SaveCurrentState(). That will overwrite transform.parent with previousParent's null value.
To reproduce, create a VRTK_InteractableObject that on use sets itself or its parent inactive. If you then set the object to active again, it will see that forcedDropped is true and LoadPreviousState(). forcedDropped is true because ForceStopInteracting is called OnDisable, and it sees that it's currently touching the controller and so lists itself as forcedDropped.
This is fixed by adding SaveCurrentState() to the end of Awake, but that's probably not the right fix.

In cases like this you're probably best off extended the Interactable Object class and overriding the relevant methods to accommodate your logic


Connect all DSC Resource Repos to Reviewable.io

At the moment it is up to the individual submitting a PR or the repo owner if Revieable is able to be used to review each PR. It would be good if the repo owners of all the DSCResources could authorize Reviewable reviews by default - it makes PR review a lot easier for both parties.

Just ignore this - I didn't realize you could just paste the URL of a GitHub PR into the box at the bottom of Reviewable to enable that PR to be reviewed. Closing.


Better choose when to build and upload Sentry info

Fixes: #4100
See also discussion.

Thanks -- this solution looks like a good one to me! Comments below; please merge at will after those.

Merged, thanks for the review!


connecting to private blockchain Gsalzer

everything worked fine until it connects to the emptychain
it wont proceed... (stays in the connecting loop forever)
installed is sucsessfully 2 years ago but idkn what i am missing
its the smartbugs version from Gsalzer

sitting here for 3 day but i wont give up

everything worked fine until it connects to the emptychain it wont proceed... (stays in the connecting loop forever) installed is sucsessfully 2 years ago but idkn what i am missing its the smartbugs version from Gsalzer

Did you managed to find a solution for this issue? I just faced the same issue.


avoid incorrect usage of TimelineTask

This code was added based on a misunderstanding of the API surface.
I believe there's a test for this but can't remmeber where it lives and want to see if CI catches it.

(this came out of https://github.com/flutter/devtools/issues/5835)

The existing test did not assert against this, but now it does.


Delete unused "background reports" test

It does nothing. Has a setup, but not tests.

Not really. This file only had one test from the beginning and it was about end-users: https://github.com/3scale/apisonator/commit/24af813b753d7d850e32b131666d7cb7df800eca#diff-0fb07a335a966eed4d944bec40dd298b
When we removed the code to support end-users, we deleted that test and didn't realize that it was the only one in the file.


Standard of shared region

This is what I wanted!
And, I have a question.
Your figure about relations among Unsupervised Learning, Self-Supervised Learning and Representation Learning impressively.
but, What is the reason that de-occlusion and correspondence are not included in the shared region?
Process of de-occlusion predicts the occluded region and process using correspondence should understand sincere relations between corresponding pixel or patch.
Through this, I think the representation could be learned.
thank you.

Deocclusion and correspondence do not aim at learning image representations.


Adding React component that abstracts CSS3 flexbox

The  component makes use of inline styles to reduce the amount of boilerplate css required. It's main value is in reducing boilerplate while developing lots of small, layout-heavy components (e.g. a multi-layer menu or tab system) where you end up with many small css files with repetetive code (lots of display: flex and flex-direction, or lots of includes if using mixins).
Example usage and comparison to alternatives here:
https://gist.github.com/JonathonAshworth/8a2c5d37482a9d66cc1ae712116383e1

I like the approach.
There's a few things though:

How do we handle responsive UI? since inline styles doesn't have an easy way to do that. There're a few situations we'll need to consider:

We need an overflow container to wrap things on mobile (to allow horizontal swipe)
We need to stack things up on mobile

Can we modify 'flex-wrap' property? Sometimes you might need that


Integrate Rocky's design into Docsy WTF site

Intiser to lead - Anthony and Tyler to support
Context: Take new assets, CSS files and designs and integrate with Docsy pages.

Homepage

[ ] Background
[ ] Github Button add
[ ] Customize button
[ ] Vertical Cards section
[ ] Horizontal Cards section
[ ] Divider
[ ] Video Embed
[ ] Notification and announcement section

DocPage

[ ] Add search to doc page only
[ ] Customize search outlook
[ ] Change color to company theme  color

ShowcasePage

[ ] Add short background
[ ] Showcase cards
[ ] Learn  more button

Navigation bar

[ ] Add github and discord button
[ ] change the color to white when the logo is ready.

Footer

[ ] Add main menu

@rtilney are you able to make a pull request for your theme customisations into this repo?

@cpswan I don't know the procedure for this. My designs are static XD files.

@rtilney - so the walkthrough we did a few days back was an XD mockup rather than a customised version of Docsy?
If that's the case then we have much more work to do than I thought when we were in the sprint planning, because somebody (who?) needs to implement the design as a customised Docsy theme.

@cpswan Correct. Sitemap, design, and implementation are all separate tasks. I can provide the assets. ie: hex codes, fonts, heading tags, icons, etc...and the static design reference.

@rtilney Yeahh can you please share all the assets?

@Intiserahmed Here is the developer XD link. https://xd.adobe.com/view/f8181f50-f288-4e59-99c5-b786dbfc5d66-ad4b/

The latest on this - @Intiserahmed has done some of the styling changes but yet to integrate into the WTF site.

@Intiserahmed can you please determine next steps and add to the issue card?  @aannttoo and I added context to the card for the team.  Thank you!

@ksanty sure done!

@ksanty sure done!

Fantastic!  Super helpful @Intiserahmed.  Thank you!


LOC-20 ⁃ Internal error when bootstraping

$ cdklocal --version
1.72.0 (build c2f38e8)

$ localstack --version
0.12.2

$ cat ~/.aws/credentials
[local]
aws_access_key_id = dummy
aws_secret_access_key = dummy

$ echo $AWS_PROFILE
local

I start localstack like this:
$ SERVICES=serverless,sqs,sns DEFAULT_REGION=eu-west-2 DEBUG=1 localstack start

I run:
$ cdklocal bootstrap -c env=local aws://000000000000/eu-west-2

The logs from localstack are the followings:
2020-11-11T11:48:16:DEBUG:localstack.services.cloudformation.cloudformation_listener: Error response for CloudFormation action "DescribeStacks" (400) POST /: b'<ErrorResponse xmlns="http://cloudformation.amazonaws.com/doc/2010-05-15/">\n  <Error>\n    <Type>Sender</Type>\n    ValidationError\n    <Message>Stack with id CDKToolkit does not exist</Message>\n  </Error>\n  <RequestId>cf4c737e-5ae2-11e4-a7c9-ad44eEXAMPLE</RequestId>\n</ErrorResponse>'
2020-11-11T11:48:16:DEBUG:localstack.services.cloudformation.cloudformation_listener: Error response for CloudFormation action "DescribeStacks" (400) POST /: b'<ErrorResponse xmlns="http://cloudformation.amazonaws.com/doc/2010-05-15/">\n  <Error>\n    <Type>Sender</Type>\n    ValidationError\n    <Message>Stack with id CDKToolkit does not exist</Message>\n  </Error>\n  <RequestId>cf4c737e-5ae2-11e4-a7c9-ad44eEXAMPLE</RequestId>\n</ErrorResponse>'
2020-11-11T11:48:16:DEBUG:localstack.services.cloudformation.cloudformation_listener: Error response for CloudFormation action "CreateChangeSet" (500) POST /: b'<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">\n<title>500 Internal Server Error</title>\n
Internal Server Error
\n
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
\n'
2020-11-11 11:48:16,640:API: Error on request:
Traceback (most recent call last):
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/werkzeug/serving.py", line 323, in run_wsgi
    execute(self.server.app)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/werkzeug/serving.py", line 312, in execute
    application_iter = app(environ, start_response)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/moto/server.py", line 168, in __call__
    return backend_app(environ, start_response)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/app.py", line 2464, in __call__
    return self.wsgi_app(environ, start_response)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/app.py", line 2450, in wsgi_app
    response = self.handle_exception(e)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask_cors/extension.py", line 165, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask_cors/extension.py", line 165, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/app.py", line 1867, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/_compat.py", line 39, in reraise
    raise value
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/app.py", line 2447, in wsgi_app
    response = self.full_dispatch_request()
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/app.py", line 1952, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask_cors/extension.py", line 165, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask_cors/extension.py", line 165, in wrapped_function
    return cors_after_request(app.make_response(f(*args, **kwargs)))
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/app.py", line 1821, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/_compat.py", line 39, in reraise
    raise value
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/app.py", line 1950, in full_dispatch_request
    rv = self.dispatch_request()
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/flask/app.py", line 1936, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/moto/core/utils.py", line 151, in __call__
    result = self.callback(request, request.url, {})
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/moto/core/responses.py", line 202, in dispatch
    return cls()._dispatch(*args, **kwargs)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/moto/core/responses.py", line 312, in _dispatch
    return self.call_action()
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/moto/core/responses.py", line 397, in call_action
    response = method()
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/moto/core/utils.py", line 282, in _wrapper
    response = f(*args, **kwargs)
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/moto/cloudformation/responses.py", line 135, in create_change_set
    parameters = {
  File "/opt/code/localstack/.venv/lib/python3.8/site-packages/moto/cloudformation/responses.py", line 136, in <dictcomp>
    param["parameter_key"]: param["parameter_value"]
KeyError: 'parameter_value'
2020-11-11T11:48:17:DEBUG:localstack.services.cloudformation.cloudformation_listener: Error response for CloudFormation action "CreateChangeSet" (500) POST /: b'<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">\n<title>500 Internal Server Error</title>\n
Internal Server Error
\n
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
\n'

┆Issue is synchronized with this Jira Bug by Unito

Hi @BlueMagma2
I'm not able to reproduce your issue 😔 I tried different python versions, localstack from repo and PyPI, different versions of aws-cdk.
All of my tries were successful and I saw this message every time without issue you've provided:
$ cdklocal bootstrap -c env=local aws://000000000000/eu-west-2
 ⏳  Bootstrapping environment aws://000000000000/eu-west-2...
CDKToolkit: creating CloudFormation changeset...
[··························································] (0/3)

 ✅  Environment aws://000000000000/eu-west-2 bootstrapped.

Could you share a little bit more information like pip freeze, exact python version and OS you're using?
You can also try what I did:
$ python3.8 -m venv local38
$ source local38/bin/activate
$ pip install localstack
$ SERVICES=serverless,sqs,sns DEFAULT_REGION=eu-west-2 DEBUG=1 localstack start

$ npm install -g aws-cdk-local
$ cdklocal bootstrap -c env=local aws://000000000000/eu-west-2

Let me know if this works.

still getting this error :(
Environment aws://000000000000/eu-west-2 failed bootstrapping: Error [ValidationError]: Template error: resource StagingBucket does not support attribute type RegionalDomainName in Fn::GetAtt     at Request.extractError (/usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/protocol/query.js:50:29)     at Request.callListeners (/usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/sequential_executor.js:106:20)     at Request.emit (/usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/sequential_executor.js:78:10)     at Request.emit (/usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/request.js:688:14)     at Request.transition (/usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/request.js:22:10)     at AcceptorStateMachine.runTo (/usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/state_machine.js:14:12)     at /usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/state_machine.js:26:10     at Request.<anonymous> (/usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/request.js:38:9)     at Request.<anonymous> (/usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/request.js:690:12)     at Request.callListeners (/usr/local/lib/node_modules/aws-cdk-local/node_modules/aws-cdk/node_modules/aws-sdk/lib/sequential_executor.js:116:18) {   code: 'ValidationError',   time: 2020-11-27T11:17:23.816Z,   requestId: undefined,   statusCode: 400,   retryable: false,   retryDelay:<PHONE_NUMBER>4596891 } Template error: resource StagingBucket does not support attribute type RegionalDomainName in Fn::GetAtt

@jackmcguire1 you should pull the new image of localstack, the error was fixed on moto and the image has been updated
docker images | grep localstack/localstack
check the ageing of you image and pull the new one

Great, thanks for confirming the fix @apalumbo . Please report here (with a small sample and detailed steps to reproduce) if the problem persists with the latest Docker image @jackmcguire1 . Thanks!


JHUAPL-Gecko now not included in dashboard

The JHUAPL-Gecko model (hospitalization forecasts only) used to be displayed as an optional model to select. The latest it was certifiably seen in the dashboard was Oct 17. It was unavailable "a week or two" after that.
An initial look indicates that this is a pipeline problem. The raw predictions_cards.rds and scores*.rds files in the S3 bucket don't contain any forecasts from this model.
The dashboard hasn't had any code changes since Oct 4 and should be immune to package updates since it runs off a static docker image. On the other hand, the pipeline runs off of dev, which has had many changes since mid-October.

This is a problem with the arrow package. I've filed an issue. Until that's fixed, we should pin arrow to version 4.0.1 or 5.0.0.


Downloads aren't cancelled by pressing Esc, but are finished in the background

Thank you so much @ninxsoft for this unique, simple and (almost) perfect tool!
:beetle: Description
Downloads aren't cancelled by pressing Esc, they are finished in the background, you come back to the Mist home page. From the home page you can start further downloads, if more than one are running at the same time, they will all fail. If Mist is quit or restarted, all downloads are aborted completely.
:clipboard: Steps to Reproduce

Open Mist
Wait for refreshing
Start downloading anything
Press Esc, you will return to the Mist home page
Monitor the downloaded data volume via Activity Monitor or with Stats
Although caching was disabled in the Mist settings, the unfinished file appears in the selected cache directory

:computer: Environment

Mist version: 0.9
macOS Version: 13.4.1 22F82
Hardware:

Model: MacBook Air M1
Model Identifier: MacBookAir10,1
Chip: Apple M1

@F1248 great catch! I have been able to replicate this issue.
The quick and easy way to fix this bug is to add the .interactiveDismissDisabled() modifier to the "Activity" sheet view, preventing dismissal via the escape key:
https://developer.apple.com/documentation/swiftui/view/interactivedismissdisabled(_:)
I will try to investigate if there is a way to prompt the user when the escape key is pressed, much like pressing the Cancel button (ie. the user is asked if they want to indeed cancel). Ultimately I feel this will be a better user experience.
Thanks again, will let you know if I make any progress 👍

Well that wasn't too painful, 2-3 lines of code 😅
https://github.com/ninxsoft/Mist/pull/72


Documentation of NvBlastExtUnity_x64.dll wanted but not found

I search for documentation of NvBlastExtUnity_x64.dll then I got this project : https://github.com/NVIDIAGameWorks/Blast.
But I still cannot find the specific doc of NvBlastExtUnity_x64.dll.

Hi, I am also facing the same issue. You have closed this as completed. Did you find a solution for this or closed this because no solution was found?


Accept any str/int/float versions and output warning.

@ccl-core Thanks! Which issue do you refer to?

Addresses: https://github.com/mlcommons/croissant/issues/91