Fixing system encoding so UTF-8 is supported for everything

Is there a way to test this or, alternately, have printed out in test_qiita_env?

What do you want to test?

Make sure that UTF-8 is set. Probably useful to output encoding on qiita_test_install.

@squirrelo Added to qiita_test_install

Changes Unknown when pulling a7bbebe38e1d29062f094a2f30ec3a0f9e13d22e on josenavas:fixing-coding into ** on biocore:master**.

:+1:

Changes Unknown when pulling a7bbebe38e1d29062f094a2f30ec3a0f9e13d22e on josenavas:fixing-coding into ** on biocore:master**.

Changes Unknown when pulling 5d3fb771414ceb022c27d67264de723a5e8dc959 on josenavas:fixing-coding into ** on biocore:master**.

Changes Unknown when pulling 5d3fb771414ceb022c27d67264de723a5e8dc959 on josenavas:fixing-coding into ** on biocore:master**.

awesome!
On Thu, Feb 26, 2015 at 5:00 PM, Antonio Gonzalez<EMAIL_ADDRESS>wrote:

Merged #886 https://github.com/biocore/qiita/pull/886.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/pull/886#event-242949289.


allowing the ability to force the use of string enums

Related to issue #131, we don't have a reference to Json.Net in our models assembly so we've always used
var jsonFormatter = GlobalConfiguration.Configuration.Formatters.JsonFormatter;
jsonFormatter.SerializerSettings.Converters.Add(new Newtonsoft.Json.Converters.StringEnumConverter());

to configure the global formatters. Because of that we can't rely on the individual enums having the proper attributes so we need a way to tell swashbuckle how to use it.
This PR hard codes true for the override, but there shouldn't be a reason the default couldn't be to query the global formatters looking to see if StringEnumConverter is in there.
One note - it seems that once you set StringEnumConverter globally there isn't a good way to force int enums on individual items. That's why I went with the "force global string enum" option name.

Thanks for this - it makes prefect sense and I'm keen to get it merged in as soon as possible.
However, rather than exposing the config as a Func, I think my preference would be a bool and then have the Swahsbuckle code inspect SerializerSettings.Converters for the case when the "force" flag has NOT been provided.
If you agree with this, there are two ways to proceed:

You sync with origin (I've since modified the interaction between SwaggerDocsHandler and SwaggerDocsConfig) and then make the adjustments.

OR, if you're time is limited

I can merge as is and then make the adjustments

Let me know what you think?

Yeah, I kind of felt that Func might have been overkill but when I pulled down the project the Core library didn't have a reference to the appropriate libraries to do the inspections so I figured just punt and let the consumer handle their own logic with a gentle nudge into them inspecting SerializerSettings.Converters.
I think if you want to pull in whatever I've done and sync it that would probably provide the best long term solution. I'll happily admit this was mostly done in a "solved my problem" sort of fashion and definitely could use some love.


CASMCMS-8417: Improve BOS docs on using staged sessions with Slurm

Description
Adds examples to the session on using BOS staged sessions with Slurm
Relates to:
CASMCMS-8417

Checklist

[X] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[X] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[X] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.3

/backport release/1.4


toml to json now returns error reasons to byond + rust-analyzer.cargo.target gnu > msvc

toml to json: One half of better error reporting for things like banned word filters in game, the other half has to be displaying the error on DM side.
rust-analyzer.cargo.target: fixes #86 and let me say holy shit that was one hellish part of getting the analyzer working

Right now this is going to cause a backwards incompatibility issue where rustg_read_toml_file does something different now
I think you should change dmsrc to be like this:
#define rustg_read_toml_file_result(path) json_decode(call(RUST_G, "toml_file_to_json")(path) || "null")

/proc/rustg_read_toml_file(path)
    var/output = rustg_read_toml_file_result(path)
    if (output["success"])
        return output["content"]
    else
        CRASH(output["content"])

That way existing consumers and consumers that just want to runtime instead of need to manage it can use the existing thing, and anything that wants to especially handle the error case can use rustg_read_toml_file_result

Aye aye, cap'n!

@tralezab Needs to be in dmsrc

Right now this is going to cause a backwards incompatibility issue where rustg_read_toml_file does something different now
I think you should change dmsrc to be like this:
#define rustg_read_toml_file_result(path) json_decode(call(RUST_G, "toml_file_to_json")(path) || "null")

/proc/rustg_read_toml_file(path)
    var/output = rustg_read_toml_file_result(path)
    if (output["success"])
        return output["content"]
    else
        CRASH(output["content"])

That way existing consumers and consumers that just want to runtime instead of need to manage it can use the existing thing, and anything that wants to especially handle the error case can use rustg_read_toml_file_result

Make it rustg_raw_read_toml_file(), result is questionable.

👍

I don't know what's up with the linux build...

Looks like it is encoding the enabled field as 1 instead of true.

you need to fix the unit tests to expect the backtrace
/test/proc/check_toml_file2json ------------------------------------------

Now I understand what's up I got it


Search Memory Tracking - track memory used during a shard search

Is your feature request related to a problem? Please describe.
There is limited visibility into how much memory is consumed by a query. In an ideal world, resource consumption details should be abstracted out from users and everything should auto-tune/auto-reject. But we are not there (yet!) and with every query treated equally, certain memory heavy queries can end up tipping the memory breakers for all requests. It will be helpful to track and surface memory consumed by a query. This visibility can help users tune their query better
Describe the solution you'd like
The proposed solution is to leverage the single threaded nature of searching within a shard. I plan to use ThreadMxBean.getCurrentThreadAllocatedBytes for tracking the memory consumption and exposing this in 2 forms

Slow logs - Search slow logs
Node Stats - Adding a new search_stats section into /_node/stats API that returns top N expensive queries

Based on some initial rally benchmarks on a POC, the overhead does not look high. Having said that, my plan is to gate this under a cluster setting search.resource_tracking that defaults to false (disabled)
Describe alternatives you've considered

In addition to memory tracking the ThreadMXBean module exposes metrics like CPU time but i dont see an immediate use case of tracking it
Performance Analyzer  also tracks metrics but I did not go down that route as eventually this could serve as feedback to improve memory estimations prior to executing a query. Further the slowlog plumbing is already well defined in the core

How about having a way to stop/deprioritise memory heavy queries kind of like the way timeout for a query works?

Nice proposal, maybe we need an extension for aggregation reduce phases on the coordinator as well(major contributors to memory), also being cautious about deserialisation overhead.
@AmiStrn maybe we need a special handling for query prioritization for instance async searches should have a different priority than usual search. Also we might need to track/estimate memory prior to the memory allocation in order for it to be terminated early. I guess both of the above can be tracked separately. Thoughts?

@AmiStrn Today a query execution can be stopped on scenarios like hitting the bucket limit or parent breakers. There is value to adding some notion of memory sandbox and preempt the query on hitting a limit as the next phase and eventually improve the memory estimation (prior to executing)
@Bukhtawar good point. This approach will not capture the reduce phase overhead and I will explore that as a follow up

Finally got some time to explore this more and here are some thoughts

The utility of exposing top N via a new search_stats section into /_node/stats API to return N most expensive queries is limited and may not help answer questions like "What queries between October 4 and 5 were most expensive in terms of their memory footprint?" as N most expensive queries might have run 60 days ago.
Implementing this via tasks framework can provide a hook to track on parent task ids and not just restrict to isolated shard level memory tracking (thanks @sohami for the idea). It also allows for other actions (not just search, if they choose to) to track memory usage. Existing tasks API already tracks latency and adding memory consumption could be useful.
On completion of task - task info which will include memory used(for search tasks) can be dumped into a sink - sink could be configurable a simple log file or a system index for further analysis.


meson error while installing video_transcode_bench_avt on Ubuntu

Seeing error with meson. Looks like it is called with unsupported attribute.
/DCPerf/benchmarks/video_transcode_bench/ffmpeg_sources /DCPerf/benchmarks/video_transcode_bench /DCPerf

cd vmaf/libvmaf
meson setup _build --prefix=/DCPerf/benchmarks/video_transcode_bench/ffmpeg_build --default-library static --prefer-static --buildtype release
usage: meson [-h] {setup,configure,dist,install,introspect,init,test,wrap,subprojects,help,rewrite,compile,devenv} ...
meson: error: unrecognized arguments: --prefer-static
Traceback (most recent call last):
File "/DCPerf/./benchpress_cli.py", line 16, in
main()
File "/DCPerf/benchpress/cli/main.py", line 310, in main
args.command.run(args, bp.jobs)
File "/DCPerf/benchpress/cli/commands/install.py", line 75, in run
install_benchmark(job.install_script, env=env)
File "/DCPerf/benchpress/lib/util.py", line 89, in install_benchmark
raise Exception(f"Failed to run '{cmd_str}'")
Exception: Failed to run 'bash -x ./packages/video_transcode_bench/install_video_transcode_bench.sh'

Hi @CoolBlueSam  thanks for raising the issue. This has been fixed. Please pull the latest commit and try again. Let us know if you have further questions.

Thanks. It's working now.


Не работает #include

In file included from E:\Arduino\libraries\AttachInterruptEx\src/attachInterruptEx.h:4:0,
from E:\sketch200324.ino:8:
E:\Arduino\libraries\CallbackHelper\src/CallbackHelper.h:4:10: fatal error: array: No such file or directory
#include
^~~~~~~
compilation terminated.
exit status 1

Which board is this?

arduino Nano 328

Sorry, the lib won't work with avr-gvc. It needs some more modern c++ features.

Почему тогда эта библиотека есть в  списке библиотек arduino ide ?
возможно ли  сделать так чтобы работало?

Because Arduino is much more than those ancient avr328  boards. The lib should work for boards using a full version of gcc

Скажите для каких плат будет  работать?

I tested it with the following boards, but it will probably work with any other arduino compatible non avr board as well
[env:teensy41]
board = teensy41
[env:TeensyLC]
board = teensylc
[env:ESP32]
platform = espressif32
board = upesy_wroom
[env:XIAO]
board = seeed_xiao
platform = atmelsam
[env:nano33]
board = nano_33_iot
platform = atmelsam
[env:Nucleo F401-RE]
board = nucleo_f401re
platform = ststm32


dotnet test gives me error while running tests

Hello, I am getting below error when i try to use "dotnet test", can you please suggest me regarding this
dotnet test Test.kommmit.Offers/Test.kommmit.Offers.csproj
Build started, please wait...
/usr/local/share/dotnet/sdk/2.2.107/Microsoft.Common.CurrentVersion.targets(1179,5): error MSB3644: The reference assemblies for framework ".NETPortable,Version=v4.5,Profile=Profile259" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend. [/Users/manojdeshpande/.jenkins/workspace/Test_Local_Angebotsapp/kommmit.Offers/kommmit.Offers/kommmit.Offers.csproj]
/usr/local/share/dotnet/sdk/2.2.107/Microsoft.Common.CurrentVersion.targets(1179,5): error MSB3644: The reference assemblies for framework ".NETPortable,Version=v4.5" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend.
Before this error i got one more error shown as below which i resolved by updating path of "Microsoft.Portable.CSharp.targets" manually.
dotnet test Test.kommmit.Offers/Test.kommmit.Offers.csproj
Build started, please wait...
/Users/manojdeshpande/.jenkins/workspace/Test_Local_Angebotsapp/kommmit.Offers/kommmit.Offers/kommmit.Offers.csproj(220,3): error MSB4019: The imported project "/usr/local/share/dotnet/sdk/2.2.107/Microsoft/Portable/v4.5/Microsoft.Portable.CSharp.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
Build step 'Execute shell' marked build as failure
Finished: FAILURE

It looks like something is referencing .NETPortable ...
Do you have a minimal repro you can share?
@nguerrera @davkean can you please help route it? Thanks!

This behavior is to be somewhat expected, dotnet SDK doesn't come with portable support.

Closing then, or is there anything left to track?

The path forward would be to convert the portable class library projects to target .NETStandard.


Question about Syntax (TS)

Hi there,
i tryed using your library with one of these lines:
@Getter activeQuiz;
@Getter('activeQuiz') activeQuiz;

but i get prompted that
Member 'activeQuiz' implicitly has an 'any' type.
[tslint] The class property 'activeQuiz' must be marked either 'private', 'public', or 'protected' (member-access) [member-access]
Do you have any idea how to write that properly? Thanks in advance.
A common computed is written like this:
private get currentScore(): string {return ''} if that helps (using vue-property decorator).

Well I do know that the message says that. But i have no idea how to do that. That's why I was hoping for a small example.


what net inside tools/test_net.py?

test_net.py
https://github.com/FateScript/CenterNet-better/blob/7336530c7e50a462a9b5c6cda486a5faa04320d0/tools/test_net.py#L27
https://github.com/FateScript/CenterNet-better/blob/7336530c7e50a462a9b5c6cda486a5faa04320d0/tools/test_net.py#L34
are u sure these line can be imported? from where?

test_net.py
https://github.com/FateScript/CenterNet-better/blob/7336530c7e50a462a9b5c6cda486a5faa04320d0/tools/test_net.py#L27
https://github.com/FateScript/CenterNet-better/blob/7336530c7e50a462a9b5c6cda486a5faa04320d0/tools/test_net.py#L34
are u sure these line can be imported? from where?

Train_net and test_net are used for dl_train and dl_test comand.
Files named net.py and config.py could be found in playground, e.g. here.

thanks, found it.
Does there any visiualize demo on  any model?

thanks, found it.
Does there any visiualize demo on any model?

Sorry, I didn't try it, but I believe that visualize code in decectron2 will also work here, I might support it in the future.


Index html generation failed. undefined:9:283862: property missing ':'

The issue is in the the class
.clr-icon.clr-vmw-logo{
background-image: url(.....)
}
PLEASE FIX
Just follow the release documentation for the moment we release Clarity version that will work with Angular 12.
Originally posted by @Jinnie in https://github.com/vmware/clarity/issues/5947#issuecomment-851399532

This is an upstream dependency issue in the Angular CLI. You can follow this issue for a workaround
https://github.com/angular/angular-cli/issues/20760
The typical workaround is adding "inlineCritical": false to the angular.json file
https://github.com/vmware/clarity/blob/next/apps/core-angular-cli/angular.json#L64


Refactor/clean the CI

Is your feature request related to a problem? Please describe.
Refactor the following to simplify it:

Github Actions
CI scripts
Deployment files in the repository

I have worked something like this for codacy, I Can Work on this! :)

@Siddhant-K-code same for this, let's come to this in after a few other tasks 👏


feat(ixday/mruby): scaffold ixday/mruby

Check List

[x] Read CONTRIBUTING.md

[x] Read OSS Contribution Guide

[x] All commits are signed

This repository enables Require signed commits, so all commits must be signed

[x] Avoid force push
[x] Do only one thing in one Pull Request
[x] Execute cmdx s to scaffold code
[ ] Install and execute the package and confirm if the package works well

Thank you for your contribution!

📝 oniguruma is required on my M3 Pro.
$ mruby --help
INFO[0000] download and unarchive the package            aqua_version= env=darwin/arm64 exe_name=mruby package_name=IxDay/mruby package_version=3.3.0 program=aqua registry=standard
Downloading IxDay/mruby 3.3.0 100% |███████████████████████████████████████████████████████████████████████████| (1.6/1.6 MB, 23 MB/s)
dyld[76152]: Library not loaded: /opt/homebrew/opt/oniguruma/lib/libonig.5.dylib
  Referenced from: <E33DD367-6B35-3610-8670-28EB5B7A562D> /Users/shunsukesuzuki/.local/share/aquaproj-aqua/pkgs/github_release/github.com/IxDay/mruby/3.3.0/mruby-macos-aarch64/mruby-macos-aarch64
  Reason: tried: '/opt/homebrew/opt/oniguruma/lib/libonig.5.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/opt/oniguruma/lib/libonig.5.dylib' (no such file), '/opt/homebrew/opt/oniguruma/lib/libonig.5.dylib' (no such file)
zsh: abort      mruby --help

brew install oniguruma

$ mruby -h
Usage: mruby-macos-aarch64 [switches] [programfile] [arguments]
  switches:
  -b           load and execute RiteBinary (mrb) file
  -c           check syntax only
  -d           set debugging flags (set $DEBUG to true)
  -e 'command' one line of script
  -r library   load the library before executing your script
  -v           print version number, then run in verbose mode
  --verbose    run in verbose mode
  --version    print the version
  --copyright  print the copyright

🎉 https://github.com/aquaproj/aqua-registry/releases/tag/v4.281.0


add .nvmrc file, @types/lodash and @types/uuid has been moved to devDeps from Deps and installed ts-reset

Check Commits:
⚙ Chore(.nvmrc): add .nvmrc file with 20.X versions
⚙ Chore(enviroment): @types/lodash and @types/uuid moved to devDependencies and installed ts-reset
Important
added .vscode/settings.json by misstake and didnt mention it in commits.

you should probably move pnpm-lock.yaml to ignore

I don't think you need to commit your .vscode or .pnpm lock

Missclick 🙈

still need pnpm lock removed, this setup assumes npm

Dev dependencies @types/lodash, @types/uuid are not used.
I believe this project could run on node 18, can you re-test again to see if it work on node 18?
Also, I checked most popular nextjs templates: https://github.com/topics/nextjs-template none of them have .nvmrc file which leads me to believe this is something that is not usually committed.

Also, I checked most popular nextjs templates: https://github.com/topics/nextjs-template none of them have .nvmrc file which leads me to believe this is something that is not usually committed.

.nvmrc helps ppls with Node Version Manager to automatic change version of node in project.
NextUI this for example (It doesnt matter which type of project it is, it's just useful)

I believe this project could run on node 18, can you re-test again to see if it work on node 18?

I just setup version to same as in package.json
"node": ">=20.0.0 <21.0.0"

I tried 18 and prob he stand up, but im getting error cuz i didnt full setup it (no db etc), just try it on your own.

This project works well on Node 18 as well.
@INeedJobToStartWork nvm is old news my man but I guess many people still use it. I prefer fnm, look for it its awesome.


return transaction after donate

In progress.
Needed for https://github.com/OpenCollective/opencollective-api/issues/769

Coverage decreased (-0.005%) to 80.931% when pulling 8364eada9ab90b4fd0fef5f2cad48e0efbb8dd9e on returnTransaction into be19a1d846fb5ffb8616405de9d1b3d2c8874e10 on master.


Optional pigz integration

pigz works in parallel and in our case does compression faster for a large number of output files.

Let's add this in v1.0.1, disabling compression saves about 2 seconds for @dmitry-novikov on gigabit ethernet connection.
At the same time, disabling compression adds about 2 seconds for me on ac wifi connection, switching to pigz saves about 2 seconds back lol.

Just run some variations on MacBook Pro (Retina, 13-inch, Early 2015) without command execution timing, i. e. always packaging same sources and results. Using the local network.

Description
Avg. Time, s

gzip + compression 0
8

gzip + compression 1
9

gzip + compression 4
9

pigz + compression 1
7

pigz + compression 4
6

pigz + compression 6
7

bonus: pipe for scp and tar
9

K, let's add optional pigz support for both local and remote machines and add it to performance optimizations tips and instruction for remote machine setup!


Namespace needed for erava:

In some examples, there is a reference to the prefix erava: - we need to resolve to a stable URI.

The namespace erava: was reserved for internal resources only relevant in the context of the vehicle authorisation process. At the moment, we do not need these externally, as era: and vpa: suffice.
There may be one exception in the future: ontology for VA-documents and -applications may be located under a separate namespace (instances will all be non-public, and this approach is not legally supported at the moment).

Current status on namespaces:

We must assume very long-term usage, and hence should no longer refer to Register names as they exist now. It is better to use "domains", like railway subsystem names or terms which will not be removed, like VehicleType.
In the current onto, and this is a known imperfection, many era:-properties & classes already have such a more precise context. With the vehicle register now modeled as well, we notice a more urgent need to add namespaces for "domains".
Also the data instances are to be given a location prefix, which cannot be era: either.

(mdh)


fix docker-compose

@noob504 check the reproducibility on your machine. Should fix the issues for now. Proper fix will need to wait for a while(working product).

There still seems to be an issue with the docker compose setup. I am still not able to initialise the container for frontend.


Hover preview for icons

When hovering over a hex with the icon tool open, the app should show you what will happen if you click by drawing a symbol at 50% opacity or so where you're hovering.

This is in the latest release :)


Rewrite test/unit_test_io.jl with new fuselage/wing/tail

@argonaut22 IO unit test doesn't work because of new fuselage (and soon wing/tail)
we can fix this when wing/tail is pushed as you would have to fix it then too (If you want to get a head start you can pull the branch wing_remodel on my branch)

Left some suggestions and caveats here:
https://github.com/MIT-LAE/TASOPT.jl/blob/d2d9b340290b0acfccc5e8818f4ef2b04b11fd39/src/IO/quicksave_load.jl#L22-L26
and here:
https://github.com/MIT-LAE/TASOPT.jl/blob/d2d9b340290b0acfccc5e8818f4ef2b04b11fd39/src/IO/quicksave_load.jl#L108-L123


DOC: Document buffers of primary instruments

Codecov Report

Merging #200 (2e3a7e6) into develop (1904018) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           develop      #200   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           41        41
  Lines         1203      1228   +25
=========================================
+ Hits          1203      1228   +25

Impacted Files
Coverage Δ

pfhedge/instruments/primary/brownian.py
100.00% <ø> (ø)

pfhedge/instruments/primary/heston.py
100.00% <ø> (ø)

pfhedge/nn/modules/ww.py
100.00% <0.00%> (ø)

pfhedge/stochastic/cir.py
100.00% <0.00%> (ø)

pfhedge/nn/modules/loss.py
100.00% <0.00%> (ø)

pfhedge/features/_getter.py
100.00% <0.00%> (ø)

pfhedge/instruments/base.py
100.00% <0.00%> (ø)

pfhedge/nn/modules/clamp.py
100.00% <0.00%> (ø)

pfhedge/features/features.py
100.00% <0.00%> (ø)

pfhedge/nn/modules/hedger.py
100.00% <0.00%> (ø)

... and 9 more

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 1904018...2e3a7e6. Read the comment docs.


Don't bump up version from the pakcage.json but just from 1.0.0

Here is my repo using the semantic-release-monorepo ：https://github.com/arvinxx/commit-gitmoji
I meet a problem that when I add a fix commit and trigger the release ci, semantic-release just bump up version from 1.0.0 other than from version from my package.json .
Because I have release some packages to npm. It will be a huge trouble to bump vesion manually.(for example, add two empty useless feat commits to get 1.2.0)
Is there any solution to this problem? thanks!

For anyone wo meet similar situation.
fixed by add a previous tag version. for example 1.1.3. Than it will start with 1.1.4 or 1.2.0.
But I prefer to use a multisemantic-release  better


[Bug]: [Auto layout] the container  doesn't expand when invisible widget a is set to visible

Is there an existing issue for this?

[X] I have searched the existing issues

Description
the container doesn't expand when invisible widget is set to visible
Steps To Reproduce

Dnd A container
drag any widget
place another widget beneath the first and make it conditionally visible
check in preview mode and make the last widget visible
https://www.loom.com/share/93ed76bac37245c3ba4d719b005f5920

Public Sample App
No response
Issue video log
No response
Version
DP

Working as expected in the DP. Moving to done.


Dai contract

0x504209d4525c79ab82374074ac1750e345ce0f5367262e691007ebf0d04912c6

--- title: MIT License spdx-id: MIT featured: true hidden: false description: A short and simple permissive license with conditions only requiring preservation of copyright and license notices. Licensed works, modifications, and larger works may be distributed under different terms and without source code. how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. using: Babel: https://github.com/babel/babel/blob/master/LICENSE .NET Core: https://github.com/dotnet/runtime/blob/master/LICENSE.TXT Rails: https://github.com/rails/rails/blob/master/MIT-LICENSE permissions: - commercial-use - modifications - distribution - private-use conditions: - include-copyright limitations: - liability - warranty --- MIT License Copyright (c) [year] [fullname] Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


ddev config --web-environment-add= may fail to override env values already set in config

Is there an existing issue for this?

[X] I have searched the existing issues

Expected Behavior
The value that was set last should be used (1.0).
Actual Behavior
The config lines will be sorted and contain all values of this env var
web_environment:
    - SOME_VERSION=1.0
    - SOME_VERSION=2.0
    - SOME_VERSION=3.0

so the last one in this list will be used, which may not be the one that was set last.
This can cause problems when e.g. using DDEV in CI and overriding the env values.
Steps To Reproduce

Make a DDEV config.yaml with SOME_VERSION=2.0 in web_environment
Run ddev config --web-environment-add="SOME_VERSION=3.0"
Run ddev config --web-environment-add="SOME_VERSION=1.0"
Run ddev start, ddev ssh and echo $SOME_VERSION

Anything else?
No response

It's not correct to have 3 environment variables with the name SOME_VERSION. It can never work out. So your initial configuration is wrong.  Why do you want to do this? There should be exactly one variable. As you point out, the last one will be the one that wins. And I don't think any of this has to do with DDEV anyway in the end.

I want to replace override the variable via CLI. So yes the ideal solution would be if ddev config --web-environment-add replaced the variable when it already exists instead of adding it.

That's what ddev config --web-environment does, but of course it replaces all your web environment, not just a single thing. But if you don't have much to add, it will do fine for you.

You may also want to consider using .ddev/.env file, or the other various ways of setting environment variables. https://ddev.readthedocs.io/en/latest/users/extend/customization-extendibility/#providing-custom-environment-variables-to-a-container

hm, maybe .ddev/.env may work, but much more convenient way would be to have a command that adds or updates a single env value. So I think the best solution would be to fix --web-environment-add, it should check if the key already exists. Besides convenience it will also prevent people from accidentally creating invalid configs like this and figuring out why it does not work as intended (which can be difficult to debug in CI).

Oh, actually looks like .ddev/.env will not work too, because it does not override the config values.
We need to put the default env vars somewhere and commit them, and then sometimes override some of the env vars in CI, such as CMS and plugin versions.

I guess your actual complaint is that running ddev config --web-environment-add several times using the same environment variable (but different values for it) results in several items being added. Could you please update your original post and your title to express that?
So
ddev config --web-environment-add=ONE=one
ddev config --web-environment-add=ONE=two
ddev config --web-environment-add=ONE=three

results in this in the config.yaml:
web_environment:
    - ONE=one
    - ONE=three
    - ONE=two

And what you want is for it to update an existing environment variable if one is configured.
That's reasonable. A PR would be welcome.
I think it would be a good idea for you to discuss your workflow a bit to say what you're really trying to accomplish and how you end up in this situation, because I'm betting that something would be easier for you.

Could you please update your original post and your title to express that?

I think it expresses that already?
So the main use case is that we have values in the config (e.g. a WordPress version or some WP plugins) that we use by default during development. And we also run some tests in CI using DDEV, and sometimes we need to override these values there.

For your CI you may want to create a config.*.yaml that contains the environment overrides and swap that in or out, etc.


Update Microsoft.BotFramework.Orchestrator in OrchestratorRecognizer to version to 4.13.1

Fix for icu lib loading issue in MacOS

Shipping in 4.13.1


'tools:replace="android:appComponentFactory"'

Hello Muddz,
Greetings. I'm trying to use your tool in my project with Android 9, but I cannot because exist a conflict between your tool and my SDK version. What can I do?
Thank you.
Sincerely, Kevin.

@Kaiwen20111998 It looks like a conflict between AndroidX package and the support packages.
Please take a look at this thread and try some of the suggestions: https://stackoverflow.com/questions/52135251/manifest-merger-fails-for-appcomponentfactory


email_verified claim OIDC auth

Hi
I am working on setting up OIDC user authentication with chirpstack 4.5. I ran into issues with the IDP (Microsoft) not providing the email_verified claim, and manually adding it makes it a string and not boolean. I was wondering if there could be implemented an automatic typecast string->bool for the case of email_verified = "true" or "false". An even better way for our case is to revive the ability to set the assume_email_verified=true in the config, as I can not find any reference to this in the v4 code. Could this be added back to the current version @brocaar ?

I would greatly appreciate a skip_email_verified=true option returning.

This has been implemented by the above commit.


[AMBARI-23826] Save button is inactive for changed filtered property after configs comparing - addendum

What changes were proposed in this pull request?

Go to HIVE configs.
Filter configs by hive.metastore.client.socket.timeout.
Compare current version with some previous.
Close comparing panel.
Change filtered property.

Result: "Save" button is inactive. Was reproduced not for any service/property.
How was this patch tested?
UI unit tests:
21792 passing (28s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2517/
Test PASSed.


[transactional-tests] Initial runner implementation

New test runner that uses struct opt and functional-test like command sections/blocks
Apologies for the lack of documentation currently. There was more in internal docs that I will try to share at some point, just trying to move this forward ASAP to help testing efforts

Motivation

Will serve for a simpler replacement of the functional-tests and e2e tests
Lots of tiny things to fix, but that can be done as this is being used

Test Plan

Added example tests

@vgao1996 some updates here:

Added support for extra arguments on publish and run
Changed how subcommands work  (might change this again to deal as I type this out)

For most of your outstanding comments about leakiness or generalness: We are building a testing framework for the VM and the Diem adapter, and it would be incorrect to think about any other usecase in the future. The name of the game here is mostly code resuse and not so much bullet-proof abstractions. I'd rather just copy-paste the code to solve reuse between the VM and Diem adapter than build some crazy, ultra-general framework. But I think we are in a decent middle ground with some macros

Changed subcommands again

than build some crazy, ultra-general framework.

@tnowacki you might got my message wrong. To be clear, overall I'm pretty happy with the current design and I'm now fairly confidant that the adapter/command model will work for Diem (with some minor tweaks). I have no intention to complicate it drastically. (Although I do believe that the framework, in its current form, is already general enough to handle more clients.)
I'm seeing the leaky abstraction and the inclusion of fn init as relatively minor and isolated problems. I'm mentioning them because I think there exists drop-in replacements that still achieve your goal of code reusing, but don't suffer from the issues I raised. I think it's fine we deal with them later.
How about we get this landed first so you can start migrating some of the tests? I can do the fixes in my PR later.

@vgao1996, any blockers remaining on this for you? If not, it would be sweet to start migrating things

I'm seeing the leaky abstraction and the inclusion of fn init as relatively minor and isolated problems. I'm mentioning them because I think there exists drop-in replacements that still achieve your goal of code reusing, but don't suffer from the issues I raised. I think it's fine we deal with them later.

I would still argue against it being leaky but its kind of moot. I think we should just get this in and get crackalackin.
Any major blockers left that I missed though?

Not really. Let me know when you fix your lint and I'll stamp it then.

/land

:broken_heart: Test Failed - ci-test

/land

:boom: Tests timed-out


Component doesn't change because reactive data doesn't update

What problem does this feature solve?
Hi folks.
I came across an issue in which a component is depending on the reactive data but it doesn't change because the reactive data is not refreshing. I have a navigation drawer which should highlight an active element depending on scroll to this element. The reactive data doesn't want to update and also the active item doesn't change. It's seems to work only when I click the component in the vue-devtool panel. Any ideas why is that? Is it going to work in the production mode?
Specifically, the "model" data property doesn't change unless I click the component name in the dev tools panel.
Thanks for the interest
What does the proposed API look like?
data: () => ({
     drawer: null,
     model: {
       type: Number,
       require: false
     },

computed: {

if (this.currentScroll >= this.currentPositions[0].top ) {
              for(let i = 0; i < this.currentPositions.length; i  ) {

               if (this.currentScroll >= this.currentPositions[i].top && this.currentScroll <= this.currentPositions[i].bottom) {
                 return   this.model = i
                 }
           }
       } else {
          return this.model = -1
       }
   },
}```

<!-- generated by vue-issues. DO NOT REMOVE -->

It was created by the issue helper...

I am also running into this. Looks like reactivity breaks sometimes when vue dev tools is turned on. If I close the console and refresh the browser it fixes the issue

It was created by the issue helper...

Please use the bug reporting part of the issue helper:


Vim Vue syntax doesn't work.

All other syntaxes are fine. Just in case here is the list of plugins I use
Plugin 'VundleVim/Vundle.vim'           " Package Manager
Plugin 'jwalton512/vim-blade'           " Blade Syntax Support
Plugin 'posva/vim-vue'                  " Vue Syntax Support
Plugin 'othree/html5.vim'               " Html5 Syntax Support
I php, js syntax work fine.

I think the issue is with file name starting from Capital Letter. With lowercase it works fine.

Hello
If you're using file.Vue instead of file.vue then yeah, that's just that the filetype is not being detected. I don't think supporting uppercase extension is a good idea, so I'm closing the issue. If you want vim-vue to work with *.Vue files add au BufNewFile,BufRead *.Vue setf vue to your .vimrc


feat(tests): Add blob gas subtraction order tests

🗒 Description
Adds parameterized tests to ensure that the blob gas fee is subtracted from the sender's balance before a blob transaction is executed. Includes the case where the sender recieves funds before the blob tx is executed.
🔗 Related Issues
As requested by @marioevz: https://github.com/ethereum/execution-spec-tests/issues/385
✅ Checklist

[x] All: Set appropriate labels for the changes.
[x] All: Considered squashing commits to improve commit history.
[x] All: Added an entry to CHANGELOG.md.
[x] All: Considered updating the online docs in the ./docs/ directory.
[x] Tests: Included the type and version of evm t8n tool used to locally execute test cases:  e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
[x] Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

I initially tried to verify the balance values stored within the post state of the destination_account.
This was easy without the additional parameterization of the max_fee_per... fields.
You can find the following revision here: https://github.com/spencer-tb/execution-spec-tests/commit/4be8852d8c2084a0282d73baf7e21ef69f6184e3
Within this the entire total account minimum fee, required to execute the tx was removed (incl. the blob gas fee) before executing the tx and contract code.
However when it came to using the max_fee_per... fields, I maybe spend a day trying to figure out the correct formula for the balance subtraction, as the amount subtracted is less than the value for the total account minimum fee.

I initially tried to verify the balance values stored within the post state of the destination_account.
This was easy without the additional parameterization of the max_fee_per... fields. You can find the following revision here: spencer-tb@4be8852 Within this the entire total account minimum fee, required to execute the tx was removed (incl. the blob gas fee) before executing the tx and contract code.
However when it came to using the max_fee_per... fields, I maybe spent a day trying to figure out the correct formula for the balance subtraction, as the amount subtracted is less than the value for the total account minimum fee.
Would you like me continue and add a check for the balance? Similarly sstore the return value of the call to send funds?

So if we try to check the stored balance, the balance should be zero only for cases where
a) tx.max_fee_per_gas == block.base_fee_per_gas
b) tx.max_fee_per_blob_gas == block.blob_base_fee_per_gas
both (a) and (b) are true, because if you check the validation steps in 1559 (which are very similar to 4844) https://eips.ethereum.org/EIPS/eip-1559, the formula for the minimum balance for the transaction to be intrinsically valid takes tx.max_fee_per_gas and tx.max_fee_per_blob_gas into account, whereas the actual balance subtraction, which happens right before the transaction execution, uses block.base_fee_per_gas and block.blob_base_fee_per_gas respectively.
So this is why we fund the account with the maximum amount it would have to pay in any block, because otherwise the transaction is invalid.

To calculate the actual balance we can use a similar approach to function total_account_minimum_balance, but instead of calculating using tx_max_fee_per_blob_gas and tx_max_fee_per_gas, we use the actual blob base fee and normal base fee of the block (functions blob_gasprice and block_fee_per_gas pytest fixtures), and we subtract that from the minimum account balance.

We now have the total_account_transactions_fee fixture within: https://github.com/ethereum/execution-spec-tests/pull/407/commits/b49c5b043cbb5d1b7ca7ec9a83ba503feba11782 alongside the updates to the tests for the post state balance checks. Some small naming tweaks were made to the total_account_minimum_balance fixture.
Within: https://github.com/ethereum/execution-spec-tests/pull/407/commits/f226e5473845e42a6926947eb180772a86b2663f I removed a duplicate fixture.
I am just working on adding the max_priority_fee_per_gas parameterization to the calculation.

We should be a go now!


Secret types cleanup

Umbrella issue: #4491
This PR cleans up the "Types of Secrets" sections in the Secrets concept docs, as follows:

Clean up Secret and ServiceAccount capitalization and change a URL
Clean up the big note about TokenRequest to reduce cognitive load of a large callout. Instead:

Call it a legacy mechanism for long-lived credentials
Rework note content with a bullet list
Make the note callout apply to when you should use a SA token Secret
Improve link accessibility by separating them from inline links where it makes sense

Clean up the ddocker config Secrets section:

Move the paragraphs into the bullets and cut down on the content length, no major changes to the actual wording
Update the step wording to stop it reading like a continuous sentence from step to output

All authn sections:

Make the "This is provided only for convenience" paragraphs have similar syntax, no content changes other than that.

/sig docs
/language en

(I can squash these, just have them separate for ease of reviewing)

/label tid/merge-method-squash
/lgtm

/label tide-merge-method-squash

/label tide/merge-method-squash

My goodness, prow

IMO, no need to have Tide get GitHub to squash this. Each commit is logically separate.
/remove-label tide/merge-method-squash

/approve
@shannonxtreme if you did squash this, it's slightly better for you to squash down to 1 commit (which preserves LGTM provided you keep the same parent commit). And then you do a git push --force-with-lease or the equivalent thing in your IDE.

Understood, Tim, thank you! I'll remember that for next time


API Sample link 404

This page includes a link to API samples which currently results in 404/not found:
https://github.com/MicrosoftEdge/WebView2Samples/tree/master/WebView2APISample

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

ID: f1c3ae57-a8c8-4615-7dcf-855e006a4043
Version Independent ID: 39480ab3-700f-9151-cd72-a12aba59c63d
Content: Getting started with WebView2 for Win32 apps - Microsoft Edge Development
Content Source: microsoft-edge/webview2/gettingstarted/win32.md
Product: microsoft-edge
Technology: webview
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

@darianmiller
Thank you for bringing this to out attention.
For updates, please follow PR #846.


DEV 9107.3 Update version of gcloud 165.0.0 -> 173.0.0

https://github.com/Shippable/pm/issues/9107

this is done, closing


sgpa_To_cgpa_convertor

Feature: SGPA to CGPA Conversion
The SGPA to CGPA Converter is a user-friendly application that allows users to convert their Semester Grade Point Average (SGPA) to Cumulative Grade Point Average (CGPA). It offers the following features:
Easy-to-use interface: The application provides a simple and intuitive user interface, allowing users to input their SGPA values and calculate the corresponding CGPA.
Multiple semesters support: Users can enter the total number of semesters and input the SGPA values for each semester. The application dynamically adjusts the interface to accommodate the specified number of semesters.
CGPA calculation: Once the SGPA values are provided, the application calculates the CGPA by summing up the SGPA values and dividing them by the total number of semesters.
Reset functionality: Users have the option to reset the inputs and results, allowing them to start fresh and perform new calculations.
The SGPA to CGPA Converter simplifies the process of converting SGPA to CGPA, providing students with a convenient tool to assess their academic performance and track their overall progress throughout their academic journey.

Mention the Issue Number.

Issue Number #2064
@avinashkranjan


Enhance required/optional options info for some subcommands

Check if required options are displayed in the usage info, e.g. for sncast account delete -h it should be

Usage: sncast account delete [OPTIONS] --name <NAME>

instead of
Usage: sncast account delete [OPTIONS]

✋


Fix small typo in error message when a CA cert does not exist

What was changed
Fixed a small typo in the error message the CLI outputs when a CA cert does not exist.
Why?
See above. Typos aren't fun to have in CLI tools.

 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.

Thank you for the fix!


Add more advanced ML implementations (starting with LR, then DL, etc)

Currently the examples (and tests) use very basic shaders. Should explore adding more advanced implementations for either data processing or machine learning training/inference. Could start with something more basic like logistic regression implementation.

Logistic regression example has been added. Closing this issue in favour of more specific / targetted examples to be added.


Initial port of the service-api to Service Weaver.

The app currently starts locally and on GKE, generating the following example log output.
I0905 13:22:30.000000 weaver.Main sales-ap main.go:62 ] startup GOMAXPROCS="2"
I0905 13:22:30.000000 weaver.Main sales-ap main.go:104] starting service version="develop"
I0905 13:22:30.000000 weaver.Main sales-ap main.go:111] startup config="--build=develop\n--desc=BILL KENNEDY\n--web-read-timeout=5s\n--web-write-timeout=10s\n--web-idle-timeout=2m0s\n--web-shutdown-timeout=20s\n--db-user=postgres\n--db-password=xxxxxx\n--db-host=<IP_ADDRESS>\n--db-name=postgres\n--db-max-idle-conns=2\n--db-max-open-conns=0\n--db-disable-tls=true"
I0905 13:22:30.000000 weaver.Main sales-ap main.go:118] startup host="<IP_ADDRESS>" status="initializing database support"
I0905 13:22:30.000000 weaver.Main sales-ap main.go:144] startup URI="<IP_ADDRESS>" status="initializing the database"
I0905 13:22:32.000000 weaver.Main sales-ap main.go:155] startup status="initializing authentication support"
I0905 13:22:32.000000 weaver.Main sales-ap main.go:190] startup status="initializing V1 API support"
I0905 13:22:32.000000 weaver.Main sales-ap main.go:179] startup host="[::]:10001" status="debug v1 router started"
I0905 13:22:32.000000 weaver.Main sales-ap main.go:215] startup host="[::]:10000" status="api router started"

This is mindblowing!!!!  If I'm seeing what I think I am seeing, the service weaver team has done something very magical.  I want to create a branch and have you merge this into a branch. Then give you access to service. I want to bring this down and review it closer on my local machine.

I create a branch named weaver. Can we merge this into that branch please.


AP-1493: Allow Provider to delete applications

What
Link to story
Using the discard gem to allow soft-delete of applications by providers
Checklist
Before you ask people to review this PR:

[x] Tests and rubocop should be passing: bundle exec rake
[x] Github should not be reporting conflicts; you should have recently run git rebase master.
[x] There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
[x] The PR description should say what you changed and why, with a link to the JIRA story.
[x] You should have looked at the diff against master and ensured that nothing unexpected is included in your changes.
[x] You should have checked that the commit messages say why the change was made.

Rebased to remove gemfile.lock clash


Commands don't activate when i type them after 1.23 update.

I got the patch for the cyber engine tweaks mod but after I had it installed, I tried to type in a command to add money as a test to see if it was working ok (Command: Game.AddToInventory("Item.money",9000)), but the command didn't work, i tried other commands as well but none of those worked either. i don't know what went wrong

It should have been Items not Item. I suppose you mistyped other commands as well. Noone is reporting issues with commands with latest version available.
Know this is older one that noone apparently replied to but worth mentioning.
Game.AddToInventory("Items.money",1234) -- Gives 1234 eddies


improve nextTick by setImmediate

We should still prioritize the MutationObserver approach, because it uses microtask semantics, and setImmediate uses macrotask semantics. In environments where both are present (e.g. IE11), we should prioritize the one that is consistent with other browsers where only MutationObserver is present.
For microtask vs macrotask, see https://jakearchibald.com/2015/tasks-microtasks-queues-and-schedules/

Sorry to bump in a bit offtopic Evan ( @yyx990803 ), but what is a macrotask? The article only mentions tasks and microtasks (and it is a great article btw).
Scott

@yyx990803 gotcha. So mutation observer, promise belongs to microtask and setImmediate, setTimeout, process.nextTick belongs to (macro)task?
And Q1: mutation observer / promise >> (process.nextTick in Node.js > ) setImmediate > setTimeout(0) / process.nextTick polyfill in Browser. Is that correct?
Q2: why a DOM related solution (mutation observer) not promise?

Ahh...ok. A regular task is a macrotask. Right?
Scott

Q1: yes except that process.nextTick is also microtask in Node > 0.9
Q2: because MutationObserver is more widely supported than native Promise,
and the user may be using a Promise polyfill that doesn't adhere to the
microtask semantics.
On Thu, Jan 21, 2016 at 2:55 AM Scott<EMAIL_ADDRESS>wrote:

Ahh...ok. A regular task is a macrotask. Right?
Scott
—
Reply to this email directly or view it on GitHub
https://github.com/vuejs/vue/pull/2200#issuecomment-173487505.

Well, so this mr will be merged, closed, later or what else? (I have updated the order: MutationObserver, setImmediate, setTimeout)


Feature request: Return same ID type for node and relationship

When querying directly with CYPHER, on a node type with an alternate ID (such as UUID) the node returns uuid by default, but the relationship returns the internal Neo4j ID.
The request is: either have the node include the Neo4j ID, or (the better solution if we are looking to avoid referencing transient Neo4j IDs) have the relationship include the node's config-specified ID
Code example (inline, gist, or repo)
results = Neo4j::ActiveBase.current_session.query("MATCH (n)-[r]-() RETURN n, r LIMIT 3")

Runtime information:
Neo4j database version: 3.1.1
neo4j gem version: 8.0.9
neo4j-core gem version: 7.0.6

I would love to be able to use the built-in Neo4j ID for the id_property.  It would save a lot of code, but unfortunately the ID can be recycled and thus would cause problems for users of the gem.
We specifically avoided using something like a uuid on relationships because Neo4j (the company via the design of the database) strongly discourages queries which start with relationships.  All queries should start with nodes and use relationships to traverse to other nodes.
Does that make sense?  I'm open to other suggestions

No, that definitely makes sense; the Neo4j ID is best considered transient.
I'd much rather see the results with whatever permanent ID is used on the nodes.
The main problem this request is trying to solve is that the nodes do not return the Neo4j ID, and the relationships don't return any other ID. This means that the output of a raw query cannot be used to reconstruct the relationships.

Essentially;
This is not great but ok:
[{
	"index": 0,
	"n": {
		"identity": {
			"username": "Admin",
			"public_name": null,
			"staged": null,
			"id": "31c7b21c-d0c0-44e4-bb52-73b4c75647bd",
                        "neo_id": "0"
		}
	},
	"r": {
		"id": 0,
		"type": "AUTHORIZES_WEBSESSION",
		"properties": {},
		"start_node_id": 0,
		"end_node_id": 2
	},
	"m": {
		"web_session": {
			"date_created": null,
			"username": "Admin",
			"id": "edc4d3ec-e005-44c2-8072-2aedfeaa0dcc"
                        "neo_id": "2"
		}
	}
}]

This is better:
[{
	"index": 0,
	"n": {
		"identity": {
			"username": "Admin",
			"public_name": null,
			"staged": null,
			"id": "31c7b21c-d0c0-44e4-bb52-73b4c75647bd"
		}
	},
	"r": {
		"id": 0,
		"type": "AUTHORIZES_WEBSESSION",
		"properties": {},
		"start_node_id": "31c7b21c-d0c0-44e4-bb52-73b4c75647bd",
		"end_node_id": "edc4d3ec-e005-44c2-8072-2aedfeaa0dcc"
	},
	"m": {
		"web_session": {
			"date_created": null,
			"username": "Admin",
			"id": "edc4d3ec-e005-44c2-8072-2aedfeaa0dcc"
		}
	}
}]

And this is no good:
[{
	"index": 0,
	"n": {
		"identity": {
			"username": "Admin",
			"public_name": null,
			"staged": null,
			"id": "31c7b21c-d0c0-44e4-bb52-73b4c75647bd"
		}
	},
	"r": {
		"id": 0,
		"type": "AUTHORIZES_WEBSESSION",
		"properties": {},
		"start_node_id": 0,
		"end_node_id": 2
	},
	"m": {
		"web_session": {
			"date_created": null,
			"username": "Admin",
			"id": "edc4d3ec-e005-44c2-8072-2aedfeaa0dcc"
		}
	}
}]


soda migrations get confused with emacs temp/backup files.

Emacs creates temporary files with .# prefixes and backup files with ~ suffixes, and soda is getting confused and running one of these migrations instead of the actual non-temp, non-backup files.

Fixed with #152.


View Result message does not display even when value is overflowing in the cell

Bug Report
Description

View Result message does not display even when value is overflowing in the cell
Steps to Reproduce

Add a large value, like<PHONE_NUMBER>9992.5
View result message does not display on cell, instead the value is shown with elipsis.

Additional Context / Screenshots

Expected Behavior

Cell should display view result message
Possible Solution

Environment

Component Name and Version:
Browser Name and Version:
Node/npm Version: [e.g. Node 8/npm 5]
Webpack Version:
Operating System and version (desktop or mobile):

@ Mentions

@SharathAlur - Please verify your implementation and mock data contains the correct object API for indicating a numeric result value, therefore will apply the "View Results" display when large value exceeds the display space in the flowsheet-cell component.
It should be  isNumeric: true, and not type: 'NUMERIC',
Current Numeric Overflow example:
https://github.com/cerner/terra-clinical/blob/1b889e41cbeba71743bd19210e94b0c1a70744f1/packages/terra-clinical-result/src/terra-dev-site/doc/example/flowsheet-result-cell/FlowsheetResultCellNumericOverflow.jsx#L10-L20

For reference, pre-v.1.0 beta releases of the component originally contained type: 'NUMERIC', but was updated from a type enum to a simple bool:
https://github.com/cerner/terra-clinical/pull/574/commits/eb45fd842e6ee34fa355096be0ecf44e54483fd5#diff-1b09cfb2c9ed65173a6fe6991f54aae56766fdc74ac6718bc84198fef29ae79cL55-R55
- 55     type: 'NUMERIC',
+ 55     isTypeNumeric: true,

It was then updated again for final before the v1.0 release with the isNumeric key:
https://github.com/cerner/terra-clinical/commit/51ee5012627534065b337cb2891d543ecb7671b1#diff-1b09cfb2c9ed65173a6fe6991f54aae56766fdc74ac6718bc84198fef29ae79cL79-R79
- 55     isTypeNumeric: true,
+ 55     isNumeric: true,

@SharathAlur see comment on #762

Thanks, This is resolved after setting isNumeric to true.

This issue can be closed

Closing per the comments above.


Add admin page nested filters

For example, the following hierarchy of filters is now supported:
study year -> semester -> group
Nested filter allows to select only values within parent domain (if year is chosen, only 2 semesters will be available).

remove filtering by year: start with semester


[DFC-675]-Cache Busting Package - Update the base-page & base-form templates, so that I can access hashed file names within these templates

Proposed changes
What changed

This PR specifically aims to update the path for loading the javascript for the base-page & base-form template.
Why did it change

To allow a developer to serve hashed file names which be made available as a result of the changes in DFC-673.
Issue tracking

DFC-675

Checklists
Environment variables or secrets

[x] No environment variables or secrets were added or changed

[ ] Documented in the README
[ ] Added to deployment repository
[ ] Added to local startup repository

Other considerations

[ ] Update README with any new instructions or tasks

Local Testing
This PR CANNOT be merged until the changes made in  DFC-673 have been.
I have conducted local testing, by cp my version of CE into the Driving Licence Repo, and setting one of the file names to see if the browser attempts to load the file . I also checked that my changes are backwards compatible so if repos choose not to install the package, they can access this iteratively.
As shown below, the browser attempts to load the all-123.js file, which I have set. Since no value is specified for the analytics.js file, it correctly falls back to the hardcoded value and loads as expected.

Looks good! Will be good to test this locally using the package once DFC-675 and with a CRI repo (driving license) just to sense check this is all verified with the real package

Looks good! Will be good to test this locally using the package once DFC-675 and with a CRI repo (driving license) just to sense check this is all verified with the real package

I have tested this with the package in the Driving Licence Repo, and can confirm it works.

Is there anyway this can be made compatible with the approach used by govuk-frontend using assetPath?
e.g.
      <link rel="icon" sizes="48x48" href="{{ assetPath | default("/assets", true) }}/images/favicon.ico">

https://github.com/alphagov/govuk-frontend/blob/1ac6988d3d9e83a1ee156a8483b6668f8a861cca/packages/govuk-frontend/src/govuk/template.njk#L14
That would ensure that favicons and other assets provided by the design system can be easily cached

Is there anyway this can be made compatible with the approach used by govuk-frontend using assetPath?
e.g.
      <link rel="icon" sizes="48x48" href="{{ assetPath | default("/assets", true) }}/images/favicon.ico">

https://github.com/alphagov/govuk-frontend/blob/1ac6988d3d9e83a1ee156a8483b6668f8a861cca/packages/govuk-frontend/src/govuk/template.njk#L14
That would ensure that favicons and other assets provided by the design system can be easily cached

We currently hash files based on their content, ensuring they are invalidated only when a specific file changes. This fine-grained caching allows files to remain cached for longer. However, adopting the suggested approach would result in all files within the folder being invalidated if even one file changes, which undermines the purpose of our package. I agree it would be beneficial to follow the standard approach, so I'm open to suggestions on how we could adapt it if possible to work with our needs ?

Is there anyway this can be made compatible with the approach used by govuk-frontend using assetPath?
e.g.
      <link rel="icon" sizes="48x48" href="{{ assetPath | default("/assets", true) }}/images/favicon.ico">

https://github.com/alphagov/govuk-frontend/blob/1ac6988d3d9e83a1ee156a8483b6668f8a861cca/packages/govuk-frontend/src/govuk/template.njk#L14
That would ensure that favicons and other assets provided by the design system can be easily cached

We currently hash files based on their content, ensuring they are invalidated only when a specific file changes. This fine-grained caching allows files to remain cached for longer. However, adopting the suggested approach would result in all files within the folder being invalidated if even one file changes, which undermines the purpose of our package. I agree it would be beneficial to follow the standard approach, so I'm open to suggestions on how we could adapt it if possible to work with our needs ?

@merlinc
Hi Robin,
Just following up on this—still waiting for your response. Thanks!


Tutorial leve documentation

MVC description diagram for Voxa with responsibilities
New Alexa developers starting with Voxa
glossary/index

Coverage remained the same at 97.665% when pulling 643c18073d02e65cd6d811e5290bf12ff81cbd9d on cvaca7:documentation into ff32026c62b2d13a651e8f72bb97e53d7f9d00a5 on mediarain:master.

Coverage remained the same at 97.665% when pulling d85169ccbdc863aa866f6d5e525224eb41f4e300 on cvaca7:documentation into ff32026c62b2d13a651e8f72bb97e53d7f9d00a5 on mediarain:master.

Also, add some of the new text in the index to the README, that way it will show up in https://mediarain.github.io/voxa/

Coverage remained the same at 97.665% when pulling cdf876aeb024a155f684ed49bdbed818f4e29973 on cvaca7:documentation into ff32026c62b2d13a651e8f72bb97e53d7f9d00a5 on mediarain:master.

Coverage remained the same at 97.665% when pulling c2f7e416bf6e45f50c06afab628dc436f5b56c54 on cvaca7:documentation into ff32026c62b2d13a651e8f72bb97e53d7f9d00a5 on mediarain:master.

@cvaca7 let's make this PR to the dev branch instead of master


set_AbsoluteExpiration does not have an implementation.

Issue / Steps to reproduce the problem

Run command dotnet new is4inmem
Start
Unhandled exception thrown.
See attached log file

Relevant parts of the log file
identityserver4_log.txt
<log goes here>

did you do a restore?

Yeah, no difference

can't repro.

Looks like I ran into a dotnet core version hell. I did reinstall dotnet sdk. I can no longer pro either. Sorry for the trouble.


Can't displace town NPCs even if you are pressing SHIFT key

Environment

OS version: macOS
Elona foobar verision: develop

Cause
Maybe changes about keybindings?

Also you can't disable auto-pickup even if you are pressing CTRL key.


Update KubeOpsController.cs

Async void is very bad

@dmakeroam in addition to @davidfowl 's suggestion, you can use this async/await check list to prevent some common mistakes when working with async/await in .NET.

The right approach should be set a code analyzer tool to detect a problem.
However, using the check list has some useful links or description that can help us have some basic knowledge of async programming in .NET.


Rest api - MetaModel-as-a-Service - draft application

Hi all,
This is my attempt at building a 'MetaModel-as-a-Service' webapp. Although it is not yet as great as I imagine it should be before we release it, I do think there's a considerable amount of work here to go with, and that might trigger others who want to help with the finishing touches.
JIRA issue, for reference: https://issues.apache.org/jira/browse/METAMODEL-1097
This webapp allows the user to define data sources in a number of groups (in the code I used the word 'tenant' because I imagine usually each group would be a tenant of the application). The data source can then be explored, queried and updated using RESTful endpoints. For example:

PUT /t1 would register a new tenant with name 't1'.
PUT /t1/ds would register a new data source with name 'ds'.
GET /t1/ds would show information about 'ds', including it's schema names.
GET /t1/ds/s/public would show information about the schema 'public'.
GET /t1/ds/s/public/t/customers would show information about the table 'customers' in schema 'public'.
POST /t1/ds/s/public/t/customers would insert data into the 'customers' table.
GET /t1/ds/q?sql=SELECT+name+FROM+customers would fire the given query to the data source.

(see the controllers package for all endpoints).
Here's what is missing (as far as I can think of) before I think it is really releasable:

No formal interface documentation yet (I think we should add a swagger file).
No persistence of tenant or datasource information (I imagine we can have many ways of implementing this - the simplest would simply be a folder/file based persistence of tenant folders and data source folders / JSON files).
So far only a simple datasource definition reader for POJO data (but others should be very easy to add - I suggest adopting the MetaModel-spring module's approach to this).

Would love a review and discussion, and would invite anyone else to further contribute to making this releasable.

Seems it has kept your (somewhat old) remarks from the early commits @LosD. Maybe you can do me a favor and delete them so we can have a fresh view on the PR? The EOLs where fixed and you're more than welcome to post other remarks too :)

I've seen this before for EOLs. I guess it's because it confiders it another line

By the way, API Blueprint seems to be a good alternative to Swagger. Then apiary.io can be used as a mock server.

I'd maybe use POST for the SQL-like query, so UPDATE and INSERT can be performed safely.

We do not allow UPDATE or INSERT in the query interface. It's literally just a facade for DataContext.executeQuery(String) (which is just for SELECT queries).

That settles that, then ☺

This branch has now been updated with the new SPI provided in METAMODEL-1099. Shall we merge this (into 5.x)? Please vote :)

Closing this and #111 in order to create a new PR without all the commit-bound remarks.


Default value of \beta (args.reg_weight) and \gamma (args.prior_weight) wrong.

In the paper, it is described that \beta and \gamma were set to 10 and 0.2. However, the given code uses 0 as the default values for both of them, essentially meaning that the code is going to be ran without the proposed additional loss terms. I would appreciate it if the authors could provide some clarification on how \beta and \gamma were actually used during training.

Hi! Thank you for your attention on our work! Yes you are right, the default parameters in args are not what we described in the paper. That is because training with the "Sparse Object Prior" term is quite slow (I have to use for-loop to iterate over batch input to calculate s_i log(s_i)). Thus, it would be prohibitive to train BiDet with this term from scratch (may need 3-4 days to one week).
Besides, we find out that training with only the original loc and cls loss at the beginning, while adding the "Sparse Object Prior" and "I(X; F)" regularization term later results in equally good performances. Specifically, we first train with \beta=0 and \gamma=0 using learning_rate=1e-3 for several epochs, and then set \beta=0.1 and \gamma=0.2 at the first lr decay step (that's what the code here does).
Also, I have to point out that the "args.reg_weight" is actually not the same as \beta in IB formula. As you can see, args.reg_weight is multiplied with I(X; F) in the code, while \beta is multiplied with I(F; C, L) in our IB formula. So here args.reg_weight = \frac{1}{\beta}, and that's why I set args.reg_weight=0.1 instead of 10 in the code (0.1 = \frac{1}{10}).
Hope my answer can help you!

Thank you for your quick reply. I do have to mention that there is still a bug in the uploaded code because while args.reg_weight and args.prior_weight is set to a non-zero value some iterations later. the predicate used in calculating the respective losses are global variables REGULARIZATION_LOSS_WEIGHT and PRIOR_LOSS_WEIGHT which are set to 0. and never changed. Although this is quite a straightforward fix, this makes me think that the uploaded code wasn't actually tested to see if it reproduced the results.
Also, I get a division by zero error on L283 in train_bidet_ssd.py after fixing the predicates using the global variables. It seems that loss_count is set to zero and never incremented in the for-loop that calculates the prior loss. It would be really helpful if someone could look into this.

Thank you for your careful inspection of our code. For the first question, yes I have to admit that it's truly a bug. When I tested the code before uploading it to GitHub, I only ran it from a pre-trained weight and set args.reg_weight=0.1 & args.prior_weight=0.2 in command line. So I didn't discover the problem you mentioned. Really sorry for that.
For the second problem, loss_count is actually increased in the for-loop here. I guess the "division by zero" problem may be due to that the model hasn't been trained enough for prior loss calculation. As you can see, there are many conditions that the code will skip the loss_count += 1. operation such as no objects in the gt classes are detected. Therefore, if you use prior_loss right after random initialization of the model, it's quite possible loss_count will be 0. A quick fix may be to replace loss_p /= loss_count with loss_p /= (loss_count + 1e-6).
Again, thank you for your time on our work and code. I really apologize for the bugs in it and I should definitely test the code much more carefully the next time.


[BUG] Crash on open after upgrading from 30024 to latest build

Describe the bug
App crashes on open after upgradung from 30024 to 30033, 30101, or the latest github action build.
To Reproduce
Steps to reproduce the behavior:

Have 30024 installed
Install any newer version
Click in app icon
It crashes

Expected behavior
It shouldn't crash
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: Poco X3
OS: LOS 21/Android 14
Version 30024+

Additional context
Attached log
crash.log

Maybe not that big of a deal, because 30024 was just a nightly and going from 21204 to the latest github action build works without problem.

Yeah, the problem was that I validated the version upgrade only from official release, not from latest nightly release


Stream() doesn't work when a date type column is used to filter.

Bug report
Describe the bug
Hi when a date type column is used to listen for specific rows in the table, it just sends the data once (as a normal select method).
It works normally when listening to all the rows or with an int2 type column.
To Reproduce
Here is a minimum reproducible code
import 'package:flutter/material.dart';
import 'package:intl/intl.dart';
import 'package:supabase_flutter/supabase_flutter.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Supabase.initialize(
    url: 'my_url',
    anonKey: '''my_key''',
  );
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Column(
        children: [
          // when the stream doesn't seem to work (when date is used to filter)
          // I use this and it shows the new data, so the behavior is like a normal get and not a realtime.
          ElevatedButton(
            onPressed: () {
              setState(() {});
            },
            child: const Text('Refresh'),
          ),
          Expanded(
            child: Center(
              child: StreamBuilder(
                // this works
                // stream: Supabase.instance.client
                // .from('table')
                // .stream(['id']).execute(),

                // this works
                // stream: Supabase.instance.client
                // .from('table:type=eq.0')
                // .stream(['id']).execute(),

                // this doesn't work
                stream: Supabase.instance.client
                    .from(
                        'table:date=eq.${DateFormat('MM/dd/yyyy').format(DateTime(2022, 04, 24))}')
                    .stream(['id']).execute(),
                builder: (BuildContext context,
                    AsyncSnapshot<List<Map<String, dynamic>>> snapshot) {
                  if (snapshot.hasError) {
                    return Text(snapshot.error.toString());
                  } else if (snapshot.connectionState ==
                      ConnectionState.waiting) {
                    return const CircularProgressIndicator();
                  } else if (snapshot.hasData) {
                    return Column(
                      children: snapshot.data!
                          .map((e) =>
                              Text('name: ${e['name']} --- date: ${e['date']}'))
                          .toList(),
                    );
                  }
                  return const Text('other');
                },
              ),
            ),
          ),
        ],
      ),
    );
  }
}

Screenshots
Here is the table definition (it's name is 'table')

Also replication is enabled for all the tables

Thank you for creating such detailed issue. We are looking into this issue and will get back with a fix hopefully soon.

I was able to confirm that this works in yyyy/MM/dd format or yyyy-MM-dd format like this.
supabase
   .from('random')
   .stream(primaryKey: ['id'])
   .gte('date_type_column', '2023/01/01');


memory leak

Problem
There is a race conditon that causes a SocketAdder to not be removed from the of available sockets if it is removed from the list of available servers. This has the side-effect of creating a memory leak because it will continually try to connect, but fail.
Modifications
After a SocketAdder errors out five times it will no long add itself to the list of active factories.
Result
No more memory leak, and after 5 errors the SocketAdder is removed from the list.

I think this is a work around the memory leak, it should be ok to infinitely try to connect on an invalid ip address.

Probably a slightly better way is to check for factory availability. If it isn't > 0.0 then do not add it back to active factories.

@NiteshKant the loadbalancer (most of the time) won't select the factory if the availability is 0, it will only do it if there are no other available factories.
The bug is that there's a period (while we're connecting to a host), when the factory is not in activeFactories and not yet in activeSockets. If the server is removed from discovery at that time, the factory will never be removed. This may lead to unbounded attempts to connect to that host.
I agree that this is a bug, but disagree that it is the cause of the memory leak.

@stevegury thanks for the explanation of the bug!
I was just wondering whether that is a better condition than checking for 5 magical error number :)
Since, one would decorate the factory with ReactiveSocketClients.detectFailure() hence changing availability, it also makes it configurable.
Anyway, if this change looks good to you, please approve!

@NiteshKant I think we should merge this, and add an issue to address this properly.

@robertroeser Agreed.

I think the work around is acceptable for now.
👍


GO build no field or method Reader/Writer/Blobs

Output of docker version:
Docker version 1.10.1, build 9e83765

Additional environment details (AWS, VirtualBox, physical, etc.):
Running on a 32 core physical server on a disconnected private network so access to docker.io, github.com/..., and any other repo sites is not an option in builds
Steps to reproduce the issue:

Install docker-engine and dependencies. Import a base image (only RHEL and derivatives are an option, the base image used has basic build tools (C,C++, Java, make) available if needed.
Import the golang and lint tools for go build deps, docker, and docker-distribution to build a newer version of the registry than rpms have available
run docker build on the distribution dockerfile (noting the Docker files were shifted to an available centos7.2 image base with build tools added to the install at first stages).

Describe the results you received:
Everything start out fine, during the final stages of the go compiling (I assume), I get:
#github.com/docker/distribution/registry/storage/driver/base
registry/storage/driver/base/regulator.go:85: r.StorageDriver.Reader undefined (type driver.StorageDriver has no field or method Reader)
registry/storage/driver/base/regulator.go:85: not enough arguments to return
registry/storage/driver/base/regulator.go:92: undefined: driver.FileWriter
registry/storage/driver/base/regulator.go:96: r.StorageDriver.Writer undefined (type driver.StorageDriver has no field or method Writer)
#github.com/docker/distribution/registry/storage
registry/storage/garbagecollect.go:20: undefined: distribution.RepositoryEnumerator
registry/storage/garbagecollect.go:37: cannot use named (type reference.Named) as type string in argument to registry.Repository
registry/storage/garbagecollect.go:47: undefined: distribution.ManifestEnumerator
registry/storage/garbagecollect.go:104: registry.Blobs undefined (type distribution.Namespace has no field or method Blobs)
I have checked those files from my tarballs that get imported to the image, and those functions seem to be defined as they are being used.
Describe the results you expected:
I properly built docker image to run as a registry.
Additional information you deem important (e.g. issue happens only occasionally):
If I do not import the main docker/docker tarball, many more such errors occur. I assume this is some go issue with some versioning, but not sure what steps are necessary to correct it. I have go 1.6.3 being installed to the image, but have also tried 1.5.3 with similar results.
For reference, the Dockerfile being used inplace of the default in the docker/distribution:
FROM local-registry:5000/centos7

ADD go1.6.3.linux-amd64.tar.gz /usr/local

ENV PATH /go/bin:/usr/local/go/bin:$PATH
ENV GOPATH /go:/go/src/github.com/docker/docker/vendor
ENV DOCKER_BUILDTAGS include_oss include_gcs

#add the docker.git repo files:
ADD docker.tar.gz.orig /go/
#add the docker/distribution repo files:
ADD distribution.tar.gz /go/src/github.com/docker/distribution/
#dependencies of go file on AdRoll's goamz needed to be added:
ADD goamz.tar.gz /go/src/
#go build deps: tools/golang and lint added into godevel.tar.gz
ADD godevel.tar.gz

#install make:
RUN yum install --assumeyes make

WORKDIR /go/src/github.com/docker/distribution

RUN  \
GOPATH="$GOPATH/Godeps/_workspace:$GOPATH" \
 && make PREFIX=/go clean binaries

NOTES:
command tried from docker/Dockerfile also produced same error after pulling in the cloned repos:
go build -o /usr/local/bin/registry-v2 github.com/docker/distribution/cmd/registry
running in the image itself (well, the image that remains after attempting to build, doing a
go test github.com/docker/distribution/cmd/registry
also gives the same error

My guess would be that there's something wrong with one or more of these tarballs, such as mixing files from different versions.
Perhaps you could try installing git in the Dockerfile and checking out the source from the git repository.
I don't know what's in docker.tar.gz.orig and goamz.tar.gz, but I suspect these aren't necessary. distribution vendors all of the packages that are necessary for it to build.

Those files are direct git clones of github.com/docker, github.com/docker/distribution, and github.com/AdRoll/goamz that I then tarballed and brought onto my server.
Installing git in my dockerfile would be of no benefit - if you read my setup I am in a completely internet disconnected environment, i.e. there is not link between my server and the www world.

Can you try removing the ADD lines for goamz and docker? Perhaps the tar of github.com/docker contains some files that conflict with the distribution tar.

BTW, if lack of internet connectivity is an issue, one option would be to build the image on a machine with an internet connection, then use docker save and docker load to transport it to the disconnected server.

The issue with that is the official one uses a non rhel base -- and this is not an option due to some security issues I am required to adhere to.

Without goamz and the docker clones I get:
registry/storage/driver/s3/s3.go:29:2: cannot find package "github.com/AdRoll/goamz/aws" in any of:
/usr/local/go/src/github.com/AdRoll/goamz/aws (from $GOROOT)
/go/src/github.com/AdRoll/goamz/aws (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/AdRoll/goamz/aws
/go/src/github.com/AdRoll/goamz/aws
/go/src/github.com/docker/docker/vendor/src/github.com/AdRoll/goamz/aws
registry/storage/driver/middleware/cloudfront/middleware.go:13:2: cannot find package "github.com/AdRoll/goamz/cloudfront" in any of:
/usr/local/go/src/github.com/AdRoll/goamz/cloudfront (from $GOROOT)
/go/src/github.com/AdRoll/goamz/cloudfront (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/AdRoll/goamz/cloudfront
/go/src/github.com/AdRoll/goamz/cloudfront
/go/src/github.com/docker/docker/vendor/src/github.com/AdRoll/goamz/cloudfront
registry/storage/driver/s3/s3.go:30:2: cannot find package "github.com/AdRoll/goamz/s3" in any of:
/usr/local/go/src/github.com/AdRoll/goamz/s3 (from $GOROOT)
/go/src/github.com/AdRoll/goamz/s3 (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/AdRoll/goamz/s3
/go/src/github.com/AdRoll/goamz/s3
/go/src/github.com/docker/docker/vendor/src/github.com/AdRoll/goamz/s3
registry/storage/driver/azure/azure.go:19:2: cannot find package "github.com/Azure/azure-sdk-for-go/storage" in any of:
/usr/local/go/src/github.com/Azure/azure-sdk-for-go/storage (from $GOROOT)
/go/src/github.com/Azure/azure-sdk-for-go/storage (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/Azure/azure-sdk-for-go/storage
/go/src/github.com/Azure/azure-sdk-for-go/storage
/go/src/github.com/docker/docker/vendor/src/github.com/Azure/azure-sdk-for-go/storage
registry/registry.go:12:2: cannot find package "github.com/Sirupsen/logrus" in any of:
/usr/local/go/src/github.com/Sirupsen/logrus (from $GOROOT)
/go/src/github.com/Sirupsen/logrus (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/Sirupsen/logrus
/go/src/github.com/Sirupsen/logrus
/go/src/github.com/docker/docker/vendor/src/github.com/Sirupsen/logrus
registry/registry.go:13:2: cannot find package "github.com/Sirupsen/logrus/formatters/logstash" in any of:
/usr/local/go/src/github.com/Sirupsen/logrus/formatters/logstash (from $GOROOT)
/go/src/github.com/Sirupsen/logrus/formatters/logstash (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/Sirupsen/logrus/formatters/logstash
/go/src/github.com/Sirupsen/logrus/formatters/logstash
/go/src/github.com/docker/docker/vendor/src/github.com/Sirupsen/logrus/formatters/logstash
registry/registry.go:14:2: cannot find package "github.com/bugsnag/bugsnag-go" in any of:
/usr/local/go/src/github.com/bugsnag/bugsnag-go (from $GOROOT)
/go/src/github.com/bugsnag/bugsnag-go (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/bugsnag/bugsnag-go
/go/src/github.com/bugsnag/bugsnag-go
/go/src/github.com/docker/docker/vendor/src/github.com/bugsnag/bugsnag-go
registry/storage/driver/oss/oss.go:29:2: cannot find package "github.com/denverdino/aliyungo/oss" in any of:
/usr/local/go/src/github.com/denverdino/aliyungo/oss (from $GOROOT)
/go/src/github.com/denverdino/aliyungo/oss (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/denverdino/aliyungo/oss
/go/src/github.com/denverdino/aliyungo/oss
/go/src/github.com/docker/docker/vendor/src/github.com/denverdino/aliyungo/oss
manifest/schema1/config_builder.go:12:2: cannot find package "github.com/docker/libtrust" in any of:
/usr/local/go/src/github.com/docker/libtrust (from $GOROOT)
/go/src/github.com/docker/libtrust (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/docker/libtrust
/go/src/github.com/docker/libtrust
/go/src/github.com/docker/docker/vendor/src/github.com/docker/libtrust
registry/storage/cache/redis/redis.go:11:2: cannot find package "github.com/garyburd/redigo/redis" in any of:
/usr/local/go/src/github.com/garyburd/redigo/redis (from $GOROOT)
/go/src/github.com/garyburd/redigo/redis (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/garyburd/redigo/redis
/go/src/github.com/garyburd/redigo/redis
/go/src/github.com/docker/docker/vendor/src/github.com/garyburd/redigo/redis
registry/handlers/blob.go:11:2: cannot find package "github.com/gorilla/handlers" in any of:
/usr/local/go/src/github.com/gorilla/handlers (from $GOROOT)
/go/src/github.com/gorilla/handlers (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/gorilla/handlers
/go/src/github.com/gorilla/handlers
/go/src/github.com/docker/docker/vendor/src/github.com/gorilla/handlers
context/http.go:13:2: cannot find package "github.com/gorilla/mux" in any of:
/usr/local/go/src/github.com/gorilla/mux (from $GOROOT)
/go/src/github.com/gorilla/mux (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/gorilla/mux
/go/src/github.com/gorilla/mux
/go/src/github.com/docker/docker/vendor/src/github.com/gorilla/mux
registry/storage/driver/swift/swift.go:34:2: cannot find package "github.com/mitchellh/mapstructure" in any of:
/usr/local/go/src/github.com/mitchellh/mapstructure (from $GOROOT)
/go/src/github.com/mitchellh/mapstructure (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/mitchellh/mapstructure
/go/src/github.com/mitchellh/mapstructure
/go/src/github.com/docker/docker/vendor/src/github.com/mitchellh/mapstructure
registry/storage/driver/swift/swift.go:35:2: cannot find package "github.com/ncw/swift" in any of:
/usr/local/go/src/github.com/ncw/swift (from $GOROOT)
/go/src/github.com/ncw/swift (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/ncw/swift
/go/src/github.com/ncw/swift
/go/src/github.com/docker/docker/vendor/src/github.com/ncw/swift
registry/registry.go:23:2: cannot find package "github.com/spf13/cobra" in any of:
/usr/local/go/src/github.com/spf13/cobra (from $GOROOT)
/go/src/github.com/spf13/cobra (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/spf13/cobra
/go/src/github.com/spf13/cobra
/go/src/github.com/docker/docker/vendor/src/github.com/spf13/cobra
registry/storage/blobwriter_resumable.go:15:2: cannot find package "github.com/stevvooe/resumable" in any of:
/usr/local/go/src/github.com/stevvooe/resumable (from $GOROOT)
/go/src/github.com/stevvooe/resumable (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/stevvooe/resumable
/go/src/github.com/stevvooe/resumable
/go/src/github.com/docker/docker/vendor/src/github.com/stevvooe/resumable
registry/storage/blobwriter_resumable.go:18:2: cannot find package "github.com/stevvooe/resumable/sha256" in any of:
/usr/local/go/src/github.com/stevvooe/resumable/sha256 (from $GOROOT)
/go/src/github.com/stevvooe/resumable/sha256 (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/stevvooe/resumable/sha256
/go/src/github.com/stevvooe/resumable/sha256
/go/src/github.com/docker/docker/vendor/src/github.com/stevvooe/resumable/sha256
registry/storage/blobwriter_resumable.go:19:2: cannot find package "github.com/stevvooe/resumable/sha512" in any of:
/usr/local/go/src/github.com/stevvooe/resumable/sha512 (from $GOROOT)
/go/src/github.com/stevvooe/resumable/sha512 (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/stevvooe/resumable/sha512
/go/src/github.com/stevvooe/resumable/sha512
/go/src/github.com/docker/docker/vendor/src/github.com/stevvooe/resumable/sha512
registry/registry.go:24:2: cannot find package "github.com/yvasiyarov/gorelic" in any of:
/usr/local/go/src/github.com/yvasiyarov/gorelic (from $GOROOT)
/go/src/github.com/yvasiyarov/gorelic (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/github.com/yvasiyarov/gorelic
/go/src/github.com/yvasiyarov/gorelic
/go/src/github.com/docker/docker/vendor/src/github.com/yvasiyarov/gorelic
registry/auth/htpasswd/htpasswd.go:9:2: cannot find package "golang.org/x/crypto/bcrypt" in any of:
/usr/local/go/src/golang.org/x/crypto/bcrypt (from $GOROOT)
/go/src/golang.org/x/crypto/bcrypt (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/golang.org/x/crypto/bcrypt
/go/src/golang.org/x/crypto/bcrypt
/go/src/github.com/docker/docker/vendor/src/golang.org/x/crypto/bcrypt
context/context.go:7:2: cannot find package "golang.org/x/net/context" in any of:
/usr/local/go/src/golang.org/x/net/context (from $GOROOT)
/go/src/golang.org/x/net/context (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/golang.org/x/net/context
/go/src/golang.org/x/net/context
/go/src/github.com/docker/docker/vendor/src/golang.org/x/net/context
registry/storage/driver/gcs/gcs.go:33:2: cannot find package "golang.org/x/oauth2" in any of:
/usr/local/go/src/golang.org/x/oauth2 (from $GOROOT)
/go/src/golang.org/x/oauth2 (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/golang.org/x/oauth2
/go/src/golang.org/x/oauth2
/go/src/github.com/docker/docker/vendor/src/golang.org/x/oauth2
registry/storage/driver/gcs/gcs.go:34:2: cannot find package "golang.org/x/oauth2/google" in any of:
/usr/local/go/src/golang.org/x/oauth2/google (from $GOROOT)
/go/src/golang.org/x/oauth2/google (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/golang.org/x/oauth2/google
/go/src/golang.org/x/oauth2/google
/go/src/github.com/docker/docker/vendor/src/golang.org/x/oauth2/google
registry/storage/driver/gcs/gcs.go:35:2: cannot find package "golang.org/x/oauth2/jwt" in any of:
/usr/local/go/src/golang.org/x/oauth2/jwt (from $GOROOT)
/go/src/golang.org/x/oauth2/jwt (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/golang.org/x/oauth2/jwt
/go/src/golang.org/x/oauth2/jwt
/go/src/github.com/docker/docker/vendor/src/golang.org/x/oauth2/jwt
registry/storage/driver/gcs/gcs.go:36:2: cannot find package "google.golang.org/api/googleapi" in any of:
/usr/local/go/src/google.golang.org/api/googleapi (from $GOROOT)
/go/src/google.golang.org/api/googleapi (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/google.golang.org/api/googleapi
/go/src/google.golang.org/api/googleapi
/go/src/github.com/docker/docker/vendor/src/google.golang.org/api/googleapi
registry/storage/driver/gcs/gcs.go:37:2: cannot find package "google.golang.org/api/storage/v1" in any of:
/usr/local/go/src/google.golang.org/api/storage/v1 (from $GOROOT)
/go/src/google.golang.org/api/storage/v1 (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/google.golang.org/api/storage/v1
/go/src/google.golang.org/api/storage/v1
/go/src/github.com/docker/docker/vendor/src/google.golang.org/api/storage/v1
registry/storage/driver/gcs/gcs.go:38:2: cannot find package "google.golang.org/cloud" in any of:
/usr/local/go/src/google.golang.org/cloud (from $GOROOT)
/go/src/google.golang.org/cloud (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/google.golang.org/cloud
/go/src/google.golang.org/cloud
/go/src/github.com/docker/docker/vendor/src/google.golang.org/cloud
registry/storage/driver/gcs/gcs.go:39:2: cannot find package "google.golang.org/cloud/storage" in any of:
/usr/local/go/src/google.golang.org/cloud/storage (from $GOROOT)
/go/src/google.golang.org/cloud/storage (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/google.golang.org/cloud/storage
/go/src/google.golang.org/cloud/storage
/go/src/github.com/docker/docker/vendor/src/google.golang.org/cloud/storage
configuration/parser.go:12:2: cannot find package "gopkg.in/yaml.v2" in any of:
/usr/local/go/src/gopkg.in/yaml.v2 (from $GOROOT)
/go/src/gopkg.in/yaml.v2 (from $GOPATH)
/go/src/github.com/docker/docker/vendor/Godeps/_workspace/src/gopkg.in/yaml.v2
/go/src/gopkg.in/yaml.v2
/go/src/github.com/docker/docker/vendor/src/gopkg.in/yaml.v2
make: *** [/go/bin/registry] Error 1

I think the problem is an incorrect GOPATH. It should just be /go, and it shouldn't modified in the make command. Go should automatically pick up the vendored packages from /go/src/github.com/docker/distribution/vendor. Does this directory exist?

I have tried with and without the GOPATH as part of the script (and had done so prior to posting the original issue). It does not seem to make a difference whether that is there or not.

Seems it finally built. Had to explicitly have /go/src/github.com/docker/distribution/Godeps/_workspace at the end of the GOPATH - it must not have been picking up the full directory structure as it is supposed to?

Are you using an old checkout of the source tree? Godeps/_workspace was moved to vendor several months ago. Nevertheless, glad you got it working.

I didn't think I was because it was a fresh clone - I had not even attempted to use v2 of the registry yet and had never checked out the github branches for either docker or docker/distribution. But lack of /vendor files must have somehow gotten an old copy, no idea how.


Add monitoring scope to default GCE config.

This will allow Heapster to run GCM-based monitoring on the nodes.

Cluster comes up as expected. Note that there is no alias for the monitoring scope which is why we use the full scope name.

LGTM


package for Debian

To make deployment and usage easier, we should create a Debian package for debiman.

As a first step, I’ve created a git repository to hold the packaging: https://anonscm.debian.org/cgit/collab-maint/debiman.git/

Let’s postpone this until the setup has stabilized.

shouldn't the debian package be here, in the upstream source? it's a native package after all... not sure why we would diverge in Debian.
furthermore, if this gets packaged, I wonder if we should ship the dman client with the package - maybe as a separate binary package, and if it should be re-written in go.
or should we, in the long run, go towards integrating dman functionality in man itself...

Ideally, debiman would not be specific to Debian, but also useful for other distributions (see also issue #56). Hence, I don’t think it should be a native package.
With regards to dman, I think the man package would be better — it’s already installed on many more machines, and is a better philosophical fit (it’s an implementation detail that manpages.debian.org is produced by debiman).

What's the progress on the Debian package?

dman is now shipped in the debian-goodies package. there is, as far as i know, no progress on packaging debiman itself.

That’s correct. @bdrung, I assume we’re still talking about your in-house instance of debiman. Would a package make your life easier?

Yes. I prefer to have all code running in production come from Debian packages. That makes managing it easier (simpler salt states and faster to reproduce the instances). Bonus point: Having the package in Debian unstable.

Status update: pault.ag/go/archive and its dependency pault.ag/go/blobstore are now in the NEW queue, and pault.ag/go/debian has been updated.
Once all of these are in, I can package debiman itself.

Status update: debiman is now in the NEW queue.

Status update: debiman cleared the NEW queue. It should be picked up by the 07:52 UTC dinstall run, i.e. should be available on mirrors within a few hours.
Closing this issue. If there are problems with the packaging, please open specific issues.


DIDCommMessaging

There's not actually going to be that much code here. Most of the task is determining what we want the interface to look like.

This interface will likely resemble:
https://github.com/Indicio-tech/cloud-mediator/blob/9eb720773e2141dc6214184d0d002d232d71319f/src/cloud_mediator/core/didcomm.py#L225
This also needs to define what the metadata will look like that gets returned from pack and unpack operations. Something similar to what is used by didcomm-python is probably a good starting point.