Metadata option is not set when doing mount

Please fill out the below information:

Your Windows build number:  (Type ver at a Windows Command Prompt)
Windows 10 1709

What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

My folder home is /mnt/c and I am trying to use automount with options metadata but don't working

I have got a fix!

Go to Settings
Update & Security > Windows Security > Virus & threat protection
Virus & threat protection > Virus & threat protection settings > Manage settings > Exclusions > Add or remote exclusions > Add an exclusion
Select the folder C:\Users\<your-user>\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_<hash>\LocalState\rootfs.
Done


Replaces this repo with new-snarkyjs from monorepo

This is a port from the monorepo with a GitHub action for CI
For reviewers -- you can focus on the "adds github action" commit, the other commits are just removing files and adding files from the monorepo

We should run tests when they pass (but currently they don't 😄 , this should be fixed when @mrmr1993 handles the node side)


Extract color overrides from attrs_list into new color_spans field

This is a follow up for #100. It removes the color_opt field from Attrs and stores the information in the new color_spans field of BufferLine instead. This allows it to be mutated without having to do relayouts.
Fixes #69.

this looks very promising, However You probably should move Metadata in with the Color as these are ones that don't affect the Layout.


Improving Transform and Rerank Module

Description

Major Changes:

Added support for using multiple datasets during transformation - this is helpful if a single dataset is too small by itself, or there are too many failing transforms from it. Have changed
Changed rerank module to first select dataset and then config. Also to use dataset tags
Use Minimum Bayes Risk Decoding (i.e. majority vote) while choosing dataset and config
Added task expansion module to better capture requirements of our task
Added support for parsing responses from openAI which had Chain of Thought followed by json  (search for the rightmost json) - useful in code tasks which may have JSON in the COT also

Minor Changes/Fixes:

Removed dataset_index,json and reranking_dataset_index.json file from examples - this seems to have been mistakenly commited
Moved make_dataset_from_samples from prompt_based.py -> description_dataset_retriever.py
Moved most transform related variables (eg num_votes, max_failed_transforms etc) to be attributes of the DescriptionDatasetRetriever class so that we don't need to pass them around in functions
Added exponential backoff / parsing error message from OpenAI to see how long to sleep
Loggers would give duplicate messages sometimes, fixed that
Updated reranking_dataset_index_tiny.json (used in tests) for using tags
Updated tests in tests/dataset_retriever_test.py

Testing
Tested with dummy example + pytest
References

I've currently commented out dataset_transformer tests, want to make sure that you guys are happy with the current format before I add tests for it.
We should probably add CLI support for all the arguments (and set default values for most ofcourse)

Hi, I'm going to trust @saum7800 and @viswavi to take a look at this. It looks exciting, but it's a bit too voluminous for me to take a careful look now.


Change to image tagging stratgey

Description
It appears there's been a change to the image tagging prefix between v0.36.0 and 0.37.0.
ie. public.ecr.aws/karpenter/karpenter:0.37.0 vs public.ecr.aws/karpenter/karpenter:v0.36.0
I couldn't see this noted anywhere in the release notes for 0.37.0 which makes me wonder if it's unintentional?
If it's not, I think it'd be worth calling this out in the release notes & in the upgrade guide. It's a small thing but it is a 'breaking change' to some pipelines.

See https://karpenter.sh/preview/upgrading/upgrade-guide/#upgrading-to-0350

As @mikestef9 commented, this change was made at 0.35, not 0.37. This change was documented in the upgrade guide and in the release notes. I'm not sure how you would have been able to pull v0.36.0 from our ECR gallery, I've verified that no such tag exists.


svm: allow conflicting transactions in entries

(still under dev, new branch because reimplementing was easier than rebasing on latest changes)
Problem
Summary of Changes
Fixes #

Hi @2501babe, We met with Andrew at Breakpoint and he mentioned that you are working on SIMD#83 related PRs.
We did a quick review of this PR. I have also pushed a set of PRs to enable SIMD#83 and your work looks very similar to what is done already here PR1 PR2 PR3. Please take a look and see if they can help you in anyway.
We are available for any discussions needed.

hi! first off, really appreciate your desire to contribute to SIMD83
i looked through your PR1 code a bit before starting on this, but unfortunately concluded i wasnt able to use your code as-written. the way accounts are handled in svm has a lot of very nasty edge cases, especially since fee-only transactions were added, and i felt like i needed to start from scratch to make sure i had a full understanding of the flow
hoping we might be able to collaborate on the account locking changes, which i expect to be a lot more straightforward. ill review PR2 before i start on that and let you know what i think

Sure, we'll look forward to discussing PR2. A question about PR3.
It is related to the replay side. According to v2.1.0 release notes ryoqan's unified scheduler path will become default and we know it already implements SIMD#83.
Our PR3 implements implements SIMD#83 in replay for the BlockstoreProcessor path.
Do you know if the BlockstoreProcessor path will also be updated to support SIMD#83?

i believe the idea is that we want simd83 support for the existing scheduler so that validators can continue to use it if they prefer, as far as i know we arent removing it, and once we start making simd83 blocks, everyone will need to be able to replay them even if they dont produce them. however you might want to double-check with andrew to be sure

this branch is now superceded by #3146, which implements simd83 with a jit loading style rather than batched loading


Cannot read properties of undefined (reading 'watch')

I haven't been able to successfully run the devtools in my repo. I have put the DevTools component underneath a FormProvider. I get the following error:
Uncaught TypeError: Cannot read properties of undefined (reading 'watch')
    at useWatch (useWatch.ts:194:1)
    at useExportControlToExtension (useExportControlToExtension.ts:15:1)
    at DevTool (devTool.tsx:38:1)
    at renderWithHooks (react-dom.development.js:14985:1)
    at mountIndeterminateComponent (react-dom.development.js:17811:1)
    at beginWork (react-dom.development.js:19049:1)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945:1)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994:1)
    at invokeGuardedCallback (react-dom.development.js:4056:1)
    at beginWork$1 (react-dom.development.js:23964:1)
useWatch @ useWatch.ts:194
useExportControlToExtension @ useExportControlToExtension.ts:15
DevTool @ devTool.tsx:38
renderWithHooks @ react-dom.development.js:14985
mountIndeterminateComponent @ react-dom.development.js:17811
beginWork @ react-dom.development.js:19049
callCallback @ react-dom.development.js:3945
invokeGuardedCallbackDev @ react-dom.development.js:3994
invokeGuardedCallback @ react-dom.development.js:4056
beginWork$1 @ react-dom.development.js:23964
performUnitOfWork @ react-dom.development.js:22776
workLoopSync @ react-dom.development.js:22707
renderRootSync @ react-dom.development.js:22670
performSyncWorkOnRoot @ react-dom.development.js:22293
(anonymous) @ react-dom.development.js:11327
unstable_runWithPriority @ scheduler.development.js:646
runWithPriority$1 @ react-dom.development.js:11276
flushSyncCallbackQueueImpl @ react-dom.development.js:11322
flushSyncCallbackQueue @ react-dom.development.js:11309
discreteUpdates$1 @ react-dom.development.js:22420
discreteUpdates @ react-dom.development.js:3756
dispatchDiscreteEvent @ react-dom.development.js:5889

Versions are:
@hookform/devtools: 4.3.0
react-hook-form: 6.15.8

Are you still facing this issue @adamsuskin

Are you still facing this issue @adamsuskin

No, and IIRC this was resolved with an originating issue of compatibility between the 4.3.x version of devotols with the RHF 6.x. Pretty sure solution was to downgrade devtools (or upgrade RHF to 7.x but that was off the table given size of migration at the time).


Release notes and breaking changes

Purpose
Make a place for release notes and breaking changes.
Changes

New section in /api for Release Notes
Changed the {alert} on /api/index.md to point to /api/release-notes/breaking-changes.md for details on all the fun
Added /api/release-notes/2019-release-notes.md with placeholder info.

Caveats
Nobody should merge or release this until someone from engineering has gone into /api/release-notes/breaking-changes.md and filled in all the [TODO] spots
Additional helpful information

Somebody may need to get George up in hear to review and make changes.

reviewed in person with @thebenrob


Add a standard for structuring React Components for the Project

Description
This PR contains a brief detail on structuring React Components for the project. The CONTRIBUTING.md & the README.md files are updated with the necessary info.
Fixes #103
Changes Include

[x] This change requires a documentation update

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings

@afkcodes @Manav-SM @Bhupesh-V the PR contains some changes to the documentation so it would be nice to receive a second pair of eyes on it in case I missed out on some grammatical errors or something. So if you guys find something please feel free to point it out.

As we are using Tailwind Styles.ts will not be necessary for most of the components we make. we can make it optional.
I was thinking to introduce NEXT UI as a component library looks cool and modern and sleek UI
refer: https://github.com/nextui-org/nextui
other things looks good to me at first go. we can anyway comeback and update it when needed.

overall Looks good to me. i am assuming for other stuff (Utils, website tabs, etc) would be covered in a seperate PR

@yashsharan0805 yes, I'll keep the contributing guidelines updated as & when there's a need to document a workflow. It's not possible to outright predict what sort of contributions will we receive & people have differing styles of writing code as well. So, I'm keep an option for future adjustments in case there's a need for it.

@afkcodes as I mentioned it earlier on Discord as well, I like the looks of NextUI (& I'm in favour of using any sort of React Component Library like Chakra-UI as well!). But let's not switch context right now because quite a lot of people are onboard on this project already. And they're aware of the fact that the project uses TailwindCSS for it's styling requirements.
Regardless, I'll open a discussion thread & we can discuss the possible workflow for migrating the tech stack to using a Component lib instead of a CSS framework.


Accelerate cold-migration using the alloc_list

This patch relies on HermitCore/libhermit#100 to accelerate the cold-migration using a list of allocated memory areas. This avoids the unnecessary registration of the whole guest's physical memory to the HCA.

Closed. Using another approach now (see #5).


moving to Paytm's fork of npmlog

Removed NPMLOG.on(), as npmlog is not an EventEmitter now.
Updated npm for travis, as it's own version was breaking builds.
addLevel() can take an additional optional parameter, the stream
to write the logs to, for every level. process.stderr for error
and critical by default.

Coverage increased (+0.7%) to 98.276% when pulling ba97dc0e3276c535a601034ed444cba0c5881ef5 on forkedNpmlog into c34a3cb9c2a6dad583fbfb663a8e1aebcfebde0d on master.


fix: fix missing +build

fix: fix missing // +build
without this line of comment, code won't be able to be compiled with golang whose version is not greater than 1.16

lgtm, put to: https://github.com/casdoor/casdoor/commit/0841eb5c301be5937b2b3174c6da4a7f47c2c37d


Handling cache on Mac

I'm exploring the cache on Mac OSX, located in ~/Jagex/Runescape, and I believe the file format has changed. They have switched over to sqlite3 databases, is this the NXT format you refer to?
I found OGG files in "js5-14.jcache" and "js5-40.jcache"

https://gist.github.com/twrightsman/7fa275bc738747282f4611e657be814a
$ python3 find_ogg_in_RS_cache.py
Searching js5-40.jcache...
Found OGG file in js5-40.jcache in key 37292 at address 568
...
Found OGG file in js5-40.jcache in key 42043 at address 0
Searching js5-14.jcache...
Found OGG file in js5-14.jcache in key 307 at address 20
...
Found OGG file in js5-14.jcache in key 46091 at address 20

Yeah, they've changed around the format. However, the files they actually store are the same as the old cache (even the new models are in there). I started working on the NXT format (the older commits here: https://github.com/villermen/RuneScapeCacheTools/commits/feature/proper-cache-implementation), but I decided I'd rather get the old format working properly first. My full cache download tool (RSCD) doesn't download in the newer format anyway, so it's shelved for now. When I get everything working properly again I'll focus on NXT, and the small differences in the format.

The NXT format does store the raw files way more easy to obtain though (no compression, split up into different rows).

Would you mind if I made a python-based no-gui library to try and replicate what you're doing here (I know at least your license permits it)? Mostly so that I can work with the cache on *NIX and only target the NXT cache format.

Yeah, go ahead. Be sure to use the code in the branch I'm working on as your reference, as that code is working as it should =). The base working of the NXT cache should be pretty much the same, but there seem to be some subtle changes here and there that made me want to implement the RuneTek5 cache before starting on it. If you could annotate your findings in your code, and send me it or your repository when you get started that might help me out too even =)


KAFKA-16957: Enable KafkaConsumerTest#configurableObjectsShouldSeeGeneratedClientId to work with CLASSIC and CONSUMER

Based on KAFKA-16957, we would want to clean the CLIENT_IDS before the test starts.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@chiacyu could you please rebase code?


Support multi thread in TFLite binding

for currently version of tflite binding TfLiteInterpreterOptionsSetNumThreads that not real enable multi-thread with TfLiteInterpreter limitation
So, if we want to enable multi-thread now, we ONLY deprecated tflite code and replace all of tflite binding to c binding?  or TfLiteInterpreterOptionsSetNumThreads could be work in the future?

Sorry I don't quite understand what you're asking about. I believe the method TfLiteInterpreterOptionsSetNumThreads is supported, we just don't recommend its use since it's a mismatch with IREE's architecture. I'll hand over to @benvanik to see if he can provide more detail.

The tflite bindings are experimental and need some work around device creation - today it always uses vmvx (our super slow reference implementation) with the default threading configuration (based on physical CPU count): but TfLiteInterpreterOptionsSetNumThreads is supported and the value is just not plumbed through. The command line flags for changing the task system work in lieu of the plumbing (https://github.com/google/iree/blob/dd02da552a858f1aa0563a8473504c047a4c61d9/iree/task/api.c --task_topology_group_count=N) if needed.
I wouldn't design new software using tflite bindings - at least, not unless you'd like to help contribute to them - whether TfLiteInterpreterOptionsSetNumThreads works is by far not the biggest issue lurking in there :)

So just chatted f2f and it sounds like there are two issues:

We should get you on a real path (not the reference vmvx path)
Since you are trying to emulate TFLite as a drop-in for clients, this seems like an intended use of the bindings. As mentioned, this is not a direct match to how IREE sets up its thread pools -- still if this is a common enough case, maybe we do want to plumb it through with caveats of some kind.

But yes, the general caveat applies: this is experimental and we are assessing the value. If you believe it has value, that is good to know.


Add initial C++ support for the R package

This PR adds (somewhat preliminary) support for the C++ API to the R package permitting reads of basic column and table info.  The submitted changes are on purpose somewhat minimal to establish a baseline and 'proof of buildability'.  Additional key features (naming, parameter tests, continuous integration, ...) will all be added consequently.
The PR also adds a minimal bit of cosmetics by adding a file LICENSE referenced in DESCRIPTION and removes the superfluous declaration of LazyData as there are no data sets shipped with the package.   A manual file got updated as a side effect of running roxygen2, the underlying text was not changed.

@johnkerl Please (squash) merge as I cannot.

@johnkerl Please (squash) merge as I cannot.

oh no @eddelbuettel just saw this now! 👀

@eddelbuettel you are now a maintainer on this package -- sorry about that -- can you please retry the merge?
(I'm happy to merge it for you but I want you to have the ability)

Will try, it flags out of sync so let me try a rebase first.

@johnkerl Looks like it dies on macOS meaning not all CI is green.  The merge box is still grey for me so I can't do anything here.

Indeed @eddelbuettel at
https://github.com/single-cell-data/TileDB-SOMA/actions/runs/3177475493/jobs/5177956942
I see a message I've seen on a few PRs today
AFAICT a GHA issue involving Mac
As the MacOS CI is the only red x (the rest are green checks) I'll go ahead & merge this


Lint code

We've gone way too long without any proper code linting. We should try to align with Carbon on this.

[ ] commitlint
[ ] prettier
[ ] eslint
[ ] stylelint

I can help with this

Awesome! So I updated with 4 tasks to this based on what Carbon is doing to lint their code. The more we align the better, but feel free to pick one and submit a PR. Let me know if you have any trouble with anything that I might be able to help with. I can create separate tickets for each of these too. Thanks!


Doesn't work

This plugin does not work at all.
<template>

<el-form driver="vee" :model="values" :rules="rules" ref="values">
  <el-form-item :rules="rules.email" label="email">
    <el-input type="text" v-model="values.email" autocomplete="off"></el-input>
  </el-form-item>
</el-form>
</template>

<script>
  export default {
    props: ["type"],
    data() {
        return {
            values: {
                email: "",
            },
            rules: {
                email: 'required|email',
            },
            errors: {},
        }
    },
}
</script>

import ElementUI from 'element-ui';
import locale from 'element-ui/lib/locale/lang/en'
import 'element-ui/lib/theme-chalk/index.css';
import VeeValidate from 'vee-validate';
import VeeElement from 'vee-element';

const validator = new VeeValidate.Validator({}, {});

Vue.use(ElementUI, { locale });
Vue.use(VeeElement, validator, true);
.........

Doesn't do anything. Doesn't show errors on page and no errors on console.

Hi,
You forgot to add the prop attribute to the el-form-item but when I corrected this, I got errors.
Try the demo here:

https://codesandbox.io/s/k76x3n95r

The Vee Validate plugin is itself in Beta, so it's possible something has changed recently.
There is another ticket which is directly related to version numbers, so I'll try to take a look at this later today.

So I tried with this, including the prop
<template>
<el-form driver="vee" :model="values" :rules="rules" ref="values">
  <el-form-item :rules="rules.date" label="date" prop="startDate">
    <el-input type="text" v-model="values.startDate" autocomplete="off"></el-input>
  </el-form-item>
</el-form>
</template>

<script>
  export default {
    data() {
        return {
            values: {
                startDate: "",
                endDate: "",
            },
            rules: {
                date: 'required',
            },
            errors: {},
        }
    },
  };
</script>

import ElementUI from 'element-ui';
import locale from 'element-ui/lib/locale/lang/en'
import 'element-ui/lib/theme-chalk/index.css';

import VeeValidate from 'vee-validate';
import VeeElement from 'vee-element';

Vue.use(ElementUI, { locale });
Vue.use(VeeElement, VeeValidate.Validator, true);

But got this error [Vue warn]: Error in event handler for "el.form.change": "TypeError: validator.verify is not a function"
I think the demo directory just needs to be deleted and there needs to instead be a very simple quickstart. A basic, full code, nothing left out, but simple baseline to have like a single form input validate. Then users can get that working and from there add/tweak with no confusion about what  stopped working when they did something more.

Obviously with a demo, one wants to provide several scenarios, but it's a good suggestion.
I'll look to add that in when I get to the bottom of the error :)

That would be very helpful. Right now I can't figure out what is going on. I stripped my App down to just the simple form on the demo. Removed my package lock file and installed the same versions of vee validate and vee element as the demo. Now the error message is Uncaught (in promise) Error: [vee-validate] No such validator 'required' exists.
I don't know what else to do to reproduce or simplify because the demo includes other patterns like extending the Form with a view and has a router in it and the config is extending  the Validator and a bunch of other stuff. This is where a really simple quickstart would be very useful. Here is the template and here is the script you need to get one form input working.


[Select] Selected option overflows

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Specific GPU assignement

Specific gpu assignement fails

Code
model = scvi.model.SCVI(adata)
model.train(n_epochs = 1, use_gpu = ["2"])

Error
Traceback (most recent call last):
  File "train_scvi.py", line 47, in <module>
    model.train(n_epochs=2, use_gpu = ["2"])
  File "/home/eecs/khalil.ouardini/scvi-tools/scvi/model/base/_training_mixin.py", line 77, in train
    **trainer_kwargs,
  File "/home/eecs/khalil.ouardini/scvi-tools/scvi/train/_trainrunner.py", line 60, in __init__
    gpus, device = parse_use_gpu_arg(use_gpu)
  File "/home/eecs/khalil.ouardini/scvi-tools/scvi/model/_utils.py", line 49, in parse_use_gpu_arg
    return gpus, device
UnboundLocalError: local variable 'gpus' referenced before assignment

Does just "2" work?

No but passing an integer to torch.device works

Would you like to fix it @khalilouardini ? We can discuss on slack what the intended behavior is.


Runtime error

Occurs after giving valid filepath (Windows 10 Java(TM) SE Runtime Environment (build 1.8.0_171-b11))
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: -1
at java.util.ArrayList.elementData(Unknown Source)
at java.util.ArrayList.get(Unknown Source)
at proRAW.getPrevImage(proRAW.java:134)
at proRAW.getImageData(proRAW.java:152)
at proRAW.retrieveData(proRAW.java:74)
at proRAW.(proRAW.java:41)
at proRAW.main(proRAW.java:387)
Have tried different file locations, drives etc.
Will try using java 7 runtime instead

Using Java 7 it fails to launch at all, saying "Exception in thread "main" java.lang.UnsupportedClassVersionError: proRAW : Unsupported major.minor version 52.0"

I just made a pull-request on this. It should fix the array issue. But your java7 problem could only be fixed by using java 8


Release v2.15.3

@mpilgrem https://github.com/stable-haskell/stack/actions/runs/8230787986/job/22504766857
do you know what's wrong here?
No executables to be installed.

# build
# _release/stack-2.15.3-linux-aarch64.tar.gz
# _release/stack-2.15.3-linux-aarch64-bin
# _release/bin/stack-2.15.3-linux-aarch64/stack
stack --arch=aarch64 --interleaved-output --local-bin-path=_release/bin/stack-2.15.3-linux-aarch64 install --flag stack:-developer-mode --flag=stack:static --docker --system-ghc --no-install-ghc --docker-stack-exe=image --flag=stack:integration-tests --flag=stack:hide-dependency-versions --flag=stack:supported-build --pedantic stack
option --internal-docker-entrypoint: cannot parse value `DockerEntrypoint {user = Just (DockerUser {uid = 1000, gid = 1000, groups = [100,996,1000], umask = 18})}'

Usage: stack [--help] [--version] [--numeric-version] [--hpack-numeric-version]
             [--docker*] [--nix*]
             [--verbosity VERBOSITY | (-v|--verbose) | --silent]
             [--[no-]time-in-log] [--[no-]rsl-in-log] [--[no-]plan-in-log]
             [--stack-root STACK-ROOT] [--work-dir WORK-DIR] [--[no-]system-ghc]
             [--[no-]install-ghc] [--arch ARCH] [--ghc-variant VARIANT]
             [--ghc-build BUILD] [-j|--jobs JOBS] [--extra-include-dirs DIR]
             [--extra-lib-dirs DIR] [--custom-preprocessor-extensions EXT]
             [--with-gcc PATH-TO-GCC] [--with-hpack HPACK]
             [--[no-]skip-ghc-check] [--[no-]skip-msys] [--local-bin-path DIR]
             [--setup-info-yaml URL] [--[no-]modify-code-page]
             [--[no-]allow-different-user] [--[no-]dump-logs]
             [--color|--colour WHEN] [--snapshot-location-base URL]
             [--[no-]script-no-run-compile] [--resolver RESOLVER]
             [--compiler COMPILER] [--[no-]terminal]
             [--stack-colors|--stack-colours STYLES] [--terminal-width INT]
             [--stack-yaml STACK-YAML] [--lock-file ARG] COMMAND|FILE
Error when running Shake build system:
  at want, called at /home/github1/actions-runner/_work/stack/stack/etc/scripts/release.hs:157:10 in main:Main
* Depends on: build
  at apply1, called at src/Development/Shake/Internal/Rules/Rerun.hs:41:5 in shake-0.19.8-9WokKX0Eztk6x8gc5jVmKQ:Development.Shake.Internal.Rules.Rerun
* Depends on: _release/stack-2.15.3-linux-aarch64-bin
  at need, called at /home/github1/actions-runner/_work/stack/stack/etc/scripts/release.hs:235:5 in main:Main
* Depends on: _release/bin/stack-2.15.3-linux-aarch64/stack
  at cmd, called at /home/github1/actions-runner/_work/stack/stack/etc/scripts/release.hs:298:9 in main:Main
* Raised the exception:
Development.Shake.cmd, system command failed
Command line: stack --arch=aarch64 --interleaved-output --local-bin-path=_release/bin/stack-2.15.3-linux-aarch64 install --flag stack:-developer-mode --flag=stack:static --docker --system-ghc --no-install-ghc --docker-stack-exe=image --flag=stack:integration-tests --flag=stack:hide-dependency-versions --flag=stack:supported-build --pedantic stack
Exit code: 1
Stderr:
option --internal-docker-entrypoint: cannot parse value `DockerEntrypoint {user = Just (DockerUser {uid = 1000, gid = 1000, groups = [100,996,1000], umask = 18})}'

Usage: stack [--help] [--version] [--numeric-version] [--hpack-numeric-version]
             [--docker*] [--nix*]
             [--verbosity VERBOSITY | (-v|--verbose) | --silent]
             [--[no-]time-in-log] [--[no-]rsl-in-log] [--[no-]plan-in-log]
             [--stack-root STACK-ROOT] [--work-dir WORK-DIR] [--[no-]system-ghc]
             [--[no-]install-ghc] [--arch ARCH] [--ghc-variant VARIANT]
             [--ghc-build BUILD] [-j|--jobs JOBS] [--extra-include-dirs DIR]
             [--extra-lib-dirs DIR] [--custom-preprocessor-extensions EXT]
             [--with-gcc PATH-TO-GCC] [--with-hpack HPACK]
             [--[no-]skip-ghc-check] [--[no-]skip-msys] [--local-bin-path DIR]
             [--setup-info-yaml URL] [--[no-]modify-code-page]
             [--[no-]allow-different-user] [--[no-]dump-logs]
             [--color|--colour WHEN] [--snapshot-location-base URL]
             [--[no-]script-no-run-compile] [--resolver RESOLVER]
             [--compiler COMPILER] [--[no-]terminal]
             [--stack-colors|--stack-colours STYLES] [--terminal-width INT]
             [--stack-yaml STACK-YAML] [--lock-file ARG] COMMAND|FILE

Error: Process completed with exit code 1.

@hasufell, I'll have look. internal-docker-entrpoint seems to be something to so with Stack.Types.Docker.dockerEntrypointArgName.

Stack's 'official' equivalent (which had no problem) was as follows (reformatted for clarity) - which looks to me to be the same command:
# build
# _release/stack-2.15.3-linux-aarch64.tar.gz
# _release/stack-2.15.3-linux-aarch64-bin
# _release/bin/stack-2.15.3-linux-aarch64/stack
stack
--arch=aarch64
--interleaved-output
--local-bin-path=_release/bin/stack-2.15.3-linux-aarch64
install
--flag stack:-developer-mode
--flag=stack:static
--docker
--system-ghc
--no-install-ghc
--docker-stack-exe=image
--flag=stack:integration-tests
--flag=stack:hide-dependency-versions
--flag=stack:supported-build
--pedantic
stack

I am stumped ... the question seems to be: why can Read not interpret Show on your CI system?

The fields of these types changed after Stack 2.13.1.

https://github.com/commercialhaskell/stack/blob/1b61c2634818f67d7740653180e125faf97f25a6/.github/workflows/integration-tests.yml#L220
Maybe this is an issue with the distro that's running on the host? On my runner it is debian bookworm. Does it have to be an alpine on the host?

When I remove the --alpine, then the build seems to continue...

This works:
ghcup run --install --stack=2.13.1 -- stack --allow-different-user etc/scripts/release.hs build --allow-dirty --alpine --build-args --docker-stack-exe=image

So it seems building the release with latest stack is broken.

Seems I was too quick in judgement, it doesn't: https://github.com/stable-haskell/stack/actions/runs/8258633012/job/22591207598

I think what I'll will do here is to abandon the stack release script. It doesn't seems to work very well and is overcomplicated. I'll also drop the tests, until there's a working way to reliably build releases.

https://github.com/stable-haskell/stack/actions/runs/8259156009/job/22592597504


Syntax for link to service or URL showing up in doc

Paired regions To protect an application against a regional outage, you can deploy the application across multiple regions, using [Azure Traffic Manager][traffic-manager]
[Enter feedback here]

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

ID: d42fd9ae-205d-042a-4d38-4ca356e27d17
Version Independent ID: 694c671b-430e-31b6-9133-2324bb3a2efa
Content: Comparing AWS and Azure regions and zones - Azure Architecture Center
Content Source: docs/aws-professional/regions-zones.md
Service: architecture-center
Sub-service: cloud-fundamentals
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#283697

@tom-schultz Thank you for catching that error in the docs! I have submitted a PR to fix the issue, the change is merged internally and will go-live in the public docs shortly.


[APEXCORE-208] Fixed checkstyle violations in StreamingContainer.java

Fixed checkstyle violations in StreamingContainer.java.
Updated apex-style configuration in .idea to be consistent with CheckStyle settings in regards to line wrapping

@ilganeli I see that you're changing the code by wrapping the long lines. We some time ago decided on the Apex dev mailing list that we are not enforcing the character limit per line. See here.
If you're using IntelliJ IDEA, you can turn on the "Soft Wrap" feature so that you don't have to fiddle with the horizontal scrollbar.


Updated the AWS Product Maturity & Releases Table

Added the information that AWS Certificate Manager is supported by AWS CLI.
https://github.com/aws/aws-cli/blob/master/CHANGELOG.rst#1100

LGTM. This is a small factual change so merging directly. Thanks @raajheshkannaa !

Fixes #232


"Loading .env environment variables" logs to stderr

This is a minor annoyance, as in some scripts we log stderr.
I think this should be changed, as it is not an error message.
Thanks in advance!
https://github.com/pypa/pipenv/blob/4b95004f1aca99006a72789804a0d19cac95386c/pipenv/core.py#L166

Hey, thanks for the input! I agree it isn’t an error, but we actually log most things to stderr for various reasons. If we redo this it will be part of a broad restructuring, i would be very hesitant to change where we send messages haphazardly. Thanks again though!

Maybe it’d be reasonable to add an environ (PIPENV_QUIET) or something to suppress some of the informational messages we produce. This, the “installing initially failing packages”, the “ignoring marker”, and probably some else.

I think we have an env var and we just don't really use it much. We should flag this as a tracking item in a cleanup project

@techalchemy apologies for replying in a closed issue but I didn't want to open a dupe to add my thoughts.
I currently use pipenv run in several cron jobs and this creates a situation where I have to send all output to /dev/null or I get an email with Loading .env environment variables… on each run. I'm running the risk of not seeing real error output because I can't silence this message. I'd be all for a -q quiet flag or PIPENV_QUIET to handle this case.
Your last comment seems to indicate that you meant to re-open this. Maybe?

The PIPENV_QUIET has since been implemented, but it is not applied to run yet. Feel free to work on this.

@uranusjr I'm surprised to read that it has been implemented. As of version 2018.11.26 it doesn't appear in the list shown by pipenv --envs or listed in the docs.
I'll take a look at the code and try to implement it.


Ocassionally disconnected with NullPointerException

When using the client, I often get disconnected with a NullPointerException message.

Unfortunately, this is something on the KGS side that I'm unable to fix. I'm going to attempt to provide as much data to the KGS team as I can (per Issue #119), which hopefully helps them fix it.


Home page "featured", "searching for" and "results" typography update

Reference .ai file is found here

@samjianga said he could animate the "searching for" text in some simple way.. perhaps the "..."

@samjianga is this what you were asking for on slack?

@jesicarson - just looking at this - and it seems theres more structural changes than I had anticipated. I'm looping in @andreadelrio - We'll need your help to adjust the structure. I can brush up any typographical alignments after.

@jesicarson @andreadelrio - orrr.. maybe not - I think I've figured it out.

@samjiangweb please let me know if you need me to take over this.

@andreadelrio - we should be good - I pushed out my latest updates for this :) thanks!

@samjianga Thanks for taking this on. Just one catch - the homepage should say "Featured" by default.
Also, the type treatment was adjusted in the .ai file (per Amber's design instructions) so that the results text is the same as the article titles. There was definitely an earlier version with smaller type. I actually think the smaller type that is live now works well for results, but not necessarily for "Featured" thoughts? Maybe adding "Featured Results" would help for clarity? Perhaps just "Featured" on the homepage could be larger text? We want to be sure folks understand that the homepage is curated content. Thanks for your thoughts!

See #789


Crash when accessing history.state on IE10

Expected behavior
No crash.
Observed behavior
IE10 throws an 'Unspecified error' when bugsnag-js tries to access window.history.state.
Steps to reproduce
I can't exactly tell how to reproduce this. In my case, it happens when I open the page, and then do 'refresh'.
Version
bugsnag-js 4.5.0
Additional information
Searching for this issue brings up other repositories the same issue, e.g. https://github.com/angular/angular.js/issues/10367 I've seen this being fixed by just wrapping the read of history.state in a try {} catch ().
(e.g. https://github.com/netman92/angular.js/commit/3bd03ff56f898cddc078791b85a127fafad3ec3c )

Hey @remko thanks for letting us know about this issue. I'll take a look.


Added PipelinesDataFlowModel and serialization test

Signed-off-by: Shivani Shukla<EMAIL_ADDRESS>Description

Adds PipelinesDataFlowModel and tests
Added JsonInclude annotation
Updated JsonProperty annotations to match config values

Issues Resolved
[List any issues this PR will resolve]
Check List

[x] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #588 (95cf9f5) into main (42c5954) will increase coverage by 0.19%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #588      +/-   ##
============================================
+ Coverage     92.12%   92.31%   +0.19%
- Complexity      569      571       +2
============================================
  Files            71       72       +1
  Lines          1727     1731       +4
  Branches        144      144
============================================
+ Hits           1591     1598       +7
+ Misses          105      102       -3
  Partials         31       31

Impacted Files
Coverage Δ

...dataprepper/model/configuration/PipelineModel.java
100.00% <ø> (ø)

...er/model/configuration/PipelinesDataFlowModel.java
100.00% <100.00%> (ø)

...java/com/amazon/dataprepper/pipeline/Pipeline.java
92.85% <0.00%> (+4.28%)
:arrow_up:

Continue to review full report at Codecov.

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


no brew on linux stack

when running on the linux stack, ftp upload fails with the error message "/tmp/bitrise086566999/step_src/step.sh: line 61: brew: command not found". would be cool if you can fix it asap, as our ci pipeline depends on this step

Note for the fix: LFTP is available in apt-get too: http://linoxide.com/linux-how-to/setup-lftp-command-line-ftp/

Hi @mryvlin ,
new version of step (2.0.1) will be available in steplib.
In this version Linux install is fixed.


Add GDAL installation instructions to the readme

Adds instructions to patch #1.

Nice!! Are you trying to remove yourself as the single source of failure for updating the DB? :)

You guessed it! Doing some EC2 exploratory work with @jasonmoofang - you can check out the developing project spec here  if you want!


[fix] Fix account joi error

Description
Looks like the account validator patten miss object
Checklist

[ ] The version field in package.json is incremented following semantic versioning
[x] The box that allows repo maintainers to update this PR is checked
[ ] I tested locally to make sure this feature/fix works
[ ] This PR passes the Circle CI checks

@stonega Thanks for pointing this out...addressed in #988!


Render stop signs

Per discussion related to traffic signals https://github.com/ZeLonewolf/openstreetmap-americana/issues/795#issuecomment-1434905662, I'm opening a new issue to track rendering stop signs (highway=stop).
Stop signs are a ubiquitous feature of low-traffic American roads, moreso than in many other countries, such as in Europe. This perhaps partly explains their lack of rendering in OSM projects like Carto, where rendering them was declined by the maintainers.
I think it would be worthwhile for this style to render these features once you're zoomed in, maybe at z>17 or so. I think their locations are useful for people on a variety of modes at a neighborhood/street level. Also, Americana is perhaps more of a "road map" than some other renderers, so their appearance would be more appropriate. On a personal level, I like adding stop signs to my local area, and so I'd appreciate the mapper feedback that other renderers like Carto currently lack for these common features (more than 1.3 million mapped worldwide). The obvious icon would be an octagon, which could be red, though a black octagon would probably also be sufficiently recognizable and might fit in with the existing white fill on the road renderings better.
Stop signs are not currently in OMT, so they would need to be added to the schema before we could render them.

I agree that stop signs would be as relevant to the style as traffic signals. Unfortunately, the only examples of stop signs I can find in print maps are in tourist maps that aim for a cartoonish take on a realistic representation of traffic control features like stop signs and traffic signals. Even PSMA Australia, publisher of the incredibly detailed Sydways/Melways/etc. maps that meld American and British cartography, doesn’t seem to show stop signs. (There should be one at the end of Sherwood Street.)


[Closed]

Hi,
I used this library for my aws credentials, but google play console alerted me that I have exposing my aws credentials from .BuildConfig class
Any ideas?

From README:

Keep in mind this module doesn't obfuscate or encrypt secrets for packaging, so do not store sensitive keys in .env. It's basically impossible to prevent users from reverse engineering mobile app secrets, so design your app (and APIs) with that in mind.

Google is correct. You shouldn't save your AWS credentials in your app code.

Thanks!


Adjust AMQP consumer constructor

Modifications
Adjust AMQP consumer constructor for Pulsar <IP_ADDRESS>-rc2 change.
Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

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