Spritesheet and Audio convert Base64

first thank you @photonstorm my previous issue “fixes #3972” has been resolved
after that i have issue when I encode a spritesheet  and audio file it will not work .
here is my code
function perload(){
        var audio = 'base:audio/mp3 base64 , base64data';
        game.load.audio('keyaudio', 'assets/audio/sound.mp3');
        game.load.spritesheet("anykeyName", "filepath/imagename.png", {
             frameWidth: 400,
             frameHeight: 300,
             endFrame: 1,
             startFrame: 0,
             margin: 0,
             spacing: 0
         });

}
function create(){
     function functionName() {
         varA = game.add.sprite(400, 300, "anykeyName");
         varA.setScale(0.9);
        var anyFrames = tempGame.textures.get('anykeyName').getFrameNames();
         var animFrames = [];
           anyFrames.forEach(function(frameName) {
          animFrames.push({
            key: 'anykeyName',
            frame: frameName
        });
    });
    game.anims.create({
        key: 'anyKeyValue',
        frames: animFrames,
        repeat: 12,
        frameRate: 8,
         hideOnComplete: true,

    });
      varA.play('anyKeyValue');
}
   // Audio Files
   var music = game.sound.add('keyaudio');
    music.play();
}
When i use this it will directly show the image but this was an animation in spritsheet
SO i want example for spritesheet with base64 with animation

<bountysource-plugin>

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/62550094-spritesheet-and-audio-convert-base64?utm_campaign=plugin&utm_content=tracker%2F283654&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F283654&utm_medium=issues&utm_source=github).
</bountysource-plugin>

Sure i will see
On Fri 24 Aug, 2018, 5:54 PM Richard Davey<EMAIL_ADDRESS>wrote:

I cannot stress enough, there's no reason to use base64 for any of this.
Please, change your workflow. It will cripple your game.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/photonstorm/phaser/issues/3975#issuecomment-415743355,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQh4N8Y3Izzu6HsrSudJpuFkoEAIl2EHks5uT_CTgaJpZM4WKxxD
.

Here, this should help: http://phaser.io/news/2018/08/data-uri-tutorial

Thanks.
On Sat 25 Aug, 2018, 4:30 AM Richard Davey<EMAIL_ADDRESS>wrote:

Closed #3975 https://github.com/photonstorm/phaser/issues/3975.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/photonstorm/phaser/issues/3975#event-1808691646, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQh4N18I-Xne3StEE0ISehalUSAIGq1kks5uUIWCgaJpZM4WKxxD
.

I am getting this error for first time while loading spritesheet using
datauri and after refresh again it will automatically remove and images
will load .
But first or after clearing this history it will not load the images.
On Sat 25 Aug, 2018, 9:13 PM Shubham Seth<EMAIL_ADDRESS>wrote:

Thanks.
On Sat 25 Aug, 2018, 4:30 AM Richard Davey<EMAIL_ADDRESS>wrote:

Closed #3975 https://github.com/photonstorm/phaser/issues/3975.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/photonstorm/phaser/issues/3975#event-1808691646, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQh4N18I-Xne3StEE0ISehalUSAIGq1kks5uUIWCgaJpZM4WKxxD
.


exec-desktop & exec-once-desktop

Description
They should take a desktop entry and execute them.
Or better, they can have a DIR where desktop entries are present and can be executed.
Initial thought was that it will be nice for ~/.config/autostart/<appname>.desktop but if hyprland gets these entries, it will make it easier to launch any desktop entry using hyprctl

use something like exec-once = gtk-launch name.desktop for that

use something like exec-once = gtk-launch name.desktop for that

don't remember exactly but last time i faced a error while trying to run an desktop file

pointless, tbh.


Bluetooth device integration within the BTHOME integration

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
The integration does not include bluetooth connected devices at all, which are integrated within the core BTHOME integration
https://www.home-assistant.io/integrations/bthome
Describe the solution you'd like
I have a number of Shelly devices (for example Shelly BLU devices - door and window magnets) that I have working in HA, but the Battery Notes add-on can't find them.

The devices have a published battery status.

My most common device is Shelly BLU Door & Window (SHELLY-BLU-DW-W)
1× 3V CR2032

Describe alternatives you've considered
Can such integrated devices be included in automatic detection? How to proceed? Is there any work-around yet?
Additional context
Can such integrated devices be included in automatic detection? How to proceed? Is there any work-around yet?

FYI: It is interesting that, for example, this device (and two others) was found automatically and offered by the integration for addition. The other 17 pieces (exactly the same) were not.

Author of BTHome integration (core of HA):
BTHome sensor is a default name shown if the model is not a known model, as you wrote besides the name everything will work the same. I have started working on some infra to allow easier adding of model names, I hope to finish it soon. I will link to this issue when it is ready.
Me: And is there any way to user-complement this hardware to make it known for integration?
You can just rename the device, there is nothing else other than the name

That's very odd, I just don't see how it would pick those devices up as they aren't in the library.
Hopefully BTHome will get more specific with it's device identifiers, it would be good to have these detected.
The manufacturer, model and model id are all set by the integration at the time of discovery, whilst these are in the core.device_registry json file I think most integrations set/overwrite these at startup so I don't think there's a permanent way to change/complement this yourself.


Add validator for emails with TLDs

The email validator currently present in svelte-use-form doesn't force a TLD (as discussed https://github.com/noahsalvi/svelte-use-form/issues/59).
This PR adds an email_with_tld validator which is very similar to the email validator but forces a TLD component to the email host name.

@noahsalvi do you have any CICD that I should run?

@noahsalvi do you have any documentation on getting dev environment set up for testing? I swear before I went on vacation, npm run tests was working fine, but now it gives me errors like:
[WebServer] error when starting preview server:
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/[...]/svelte-use-form/.svelte-kit/output/server/index.js' imported from<EMAIL_ADDRESS>
Not sure exactly what changed or what the issue is. I wonder if specifying next for @sveltejs/kit is contributing to instability. What version do you have installed locally?

I just found out what caused this! I recently separated the build step from the test call meaning that you now need to run npm run build before calling npm run test...
I changed this so that when adding tests, you wouldn't need to repeatedly build the project. Is this bad DX?

🤦 Of course. Now that you mention it, I had figured that out prior to my vacation but forgot afterwards.
It'd be better if the error message said to go build instead of the more obscure message it shows now. Not sure if it's something that you can influence.
Does npm run build actually build if none of the source has changed? If so, then I don't think forcing a build prior to running tests would hurt (and would be a good idea). If NPM is not smart enough, then I would say what you have now is good.

After spending a few more minutes on this, I think because the build time is so quick for this package, you should consider always building before tests. Changing something about the page (like id of an element) used for tests will cause tests to fail, and it's unclear why it's failing until you realize you need to rebuild.

I've made all the changes. Should be ready for final review/tests!


Add build for ppc64le

As requested in  https://github.com/conda-forge/tensorstore-feedstock/issues/31#issuecomment-2143707982 .

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

To not clutter the other issue:
To answer: potential users in Summit and Sierra. @traversaro

Thanks! I put some wrong line endings by doing copy&paste in vscode online from windows, as soon as I am back at the laptop I will check that.

Build is failing with:
# Execution platform: @local_config_platform//:host

  Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
  cc1: error: bad value 'power8' for '-mtune=' switch
  Building wheel for tensorstore (pyproject.toml): finished with status 'error'
  ERROR: Failed building wheel for tensorstore
Failed to build tensorstore
ERROR: Could not build wheels for tensorstore, which is required to install pyproject.toml-based projects
Exception information:
Traceback (most recent call last):
  File "$BUILD_PREFIX/venv/lib/python3.10/site-packages/pip/_internal/cli/base_command.py", line 180, in exc_logging_wrapper
    status = run_func(*args)
  File "$BUILD_PREFIX/venv/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", line 245, in wrapper
    return func(self, options, args)
  File "$BUILD_PREFIX/venv/lib/python3.10/site-packages/pip/_internal/commands/install.py", line 429, in run
    raise InstallationError(
pip._internal.exceptions.InstallationError: Could not build wheels for tensorstore, which is required to install pyproject.toml-based projects
Removed build tracker: '/tmp/pip-build-tracker-onc_yidg'
Traceback (most recent call last):
  File "/opt/conda/bin/conda-build", line 11, in <module>
    sys.exit(execute())
  File "/opt/conda/lib/python3.10/site-packages/conda_build/cli/main_build.py", line 590, in execute
    api.build(
  File "/opt/conda/lib/python3.10/site-packages/conda_build/api.py", line 250, in build
    return build_tree(
  File "/opt/conda/lib/python3.10/site-packages/conda_build/build.py", line 3638, in build_tree
    packages_from_this = build(
  File "/opt/conda/lib/python3.10/site-packages/conda_build/build.py", line 2506, in build
    utils.check_call_env(
  File "/opt/conda/lib/python3.10/site-packages/conda_build/utils.py", line 405, in check_call_env
    return _func_defaulting_env_to_os_environ("call", *popenargs, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/conda_build/utils.py", line 381, in _func_defaulting_env_to_os_environ
    raise subprocess.CalledProcessError(proc.returncode, _args)
subprocess.CalledProcessError: Command '['/bin/bash', '-o', 'errexit', '/home/conda/feedstock_root/build_artifacts/tensorstore_1717382737744/work/conda_build.sh']' returned non-zero exit status 1.

The problem is that the wrong compiler is used, the x86_64 instead of the ppc64le:
2024-06-03T02:49:41.7735097Z     /home/conda/feedstock_root/build_artifacts/tensorstore_1717382735348/_build_env/bin/x86_64-conda-linux-gnu-gcc -MD -MF bazel-out/k8-opt-exec-2B5CBBC6/bin/external/com_google_protobuf/upb/mem/_objs/mem/arena.d '-frandom-seed=bazel-out/k8-opt-exec-2B5CBBC6/bin/external/com_google_protobuf/upb/mem/_objs/mem/arena.o' '-DBAZEL_CURRENT_REPOSITORY="com_google_protobuf"' -iquote external/com_google_protobuf -iquote bazel-out/k8-opt-exec-2B5CBBC6/bin/external/com_google_protobuf -isystem /home/conda/feedstock_root/build_artifacts/tensorstore_1717382735348/_build_env/include '-mcpu=power8' '-mtune=power8' -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O3 -pipe -isystem /home/conda/feedstock_root/build_artifacts/tensorstore_1717382735348/_build_env/include '-fdebug-prefix-map=/home/conda/feedstock_root/build_artifacts/tensorstore_1717382735348/work=/usr/local/src/conda/tensorstore-0.1.60' '-fdebug-prefix-map=/home/conda/feedstock_root/build_artifacts/tensorstore_1717382735348/_build_env=/usr/local/src/conda-prefix' -DNDEBUG '-D_FORTIFY_SOURCE=2' -O2 -isystem /home/conda/feedstock_root/build_artifacts/tensorstore_1717382735348/_build_env/include -g0 '-std=c99' -Wall -Wstrict-prototypes -c external/com_google_protobuf/upb/mem/arena.c -o bazel-out/k8-opt-exec-2B5CBBC6/bin/external/com_google_protobuf/upb/mem/_objs/mem/arena.o)

Apparently, that compilation unit is compiled with the x86_64 compiler also in aarch64, but there there is no incompatible flag in the CFLAGS (just by chance I guess).

Removing -mtune=power8 and -mcpu=power8 from the options works fine (as in https://github.com/conda-forge/nwchem-feedstock/blob/e1fa893922dd9abb8f2d80de6680ef2ffa9c1ebc/recipe/build.sh#L88), but that is a workaround.

Superseded by https://github.com/conda-forge/tensorstore-feedstock/pull/30 .


arch: reorg stacktrace dependencies & add arch_stack_walk() for x86 & arm64

[!NOTE]
Expected to conflict with #77457

Fixes #76706
Fixes #74713
Includes #76044 & #76042, obsoletes #75865

If an arch implements arch_stack_walk() ARCH_HAS_STACKWALK should be selected.
If the above is enabled, ARCH_SUPPORTS_STACKWALK indicates if the dependencies are met for arch to enable stack walking. This Kconfig replaces <arch>_EXCEPTION_STACK_TRACE
If the above is enabled, then, ARCH_STACKWALK determines if arch_stack_walk() should be compiled.
EXCEPTION_STACK_TRACE should build on top of the ARCH_STACKWALK, stack traces will be printed when it is enabled.
EXCEPTION_STACK_TRACE_MAX_FRAMES  will be removed as it is replaced by ARCH_STACKWALK_MAX_FRAMES

CONFIG_EXCEPTION_STACK_TRACE_SYMTAB is also removed in this PR, as it doesn't really make sense to save a few bytes, when a lot of bytes went into the symbol table when CONFIG_SYMTAB=y

Squashed the x86 & arm64 's changes in this commit into where it happened, added a commit to document the API in Architecture Interface

Updated release note


06, added githubmodels-app.py, updated githubmodels-assignment.ipynb

Add the azure-ai-inference to the requirements.txt

Already resolved. @koreyspace


⚒ increase nfts displayed in collection

I find it annoying to have an empty box
PR type

[x] Bugfix

What's new?

[x] Increase number of nfts displayed in /collection/:id by 1

Screenshot (same for 2 column)
before

after

Lol though it's something complex 😂


Auto hide right bar

We could display the right bar and make it slide to the right after 5 seconds

Closing, new WebUI will handle this
https://github.com/skydive-project/skydive-ui


Sauce gem always fails with uninitialized constant Sauce::RSpec::Spec

I'm using rspec 3.3 and the sauce_ruby gem always fails with uninitialized constant Sauce::RSpec::Spec. I added a trace point and tracked the issue down to sauce_ruby's rspec_one_support
Why is rspec 1 even supported? The last rspec 1 release was April 11, 2011.
begin
  require 'spec'
  module Sauce
    module RSpec
      class SeleniumExampleGroup < Spec::Example::ExampleGroup
    module RSpec
rescue LoadError
  STDERR.puts "Exception occured: #{e.to_s}"
Exception occured: uninitialized constant Sauce::RSpec::Spec
  exit 1

Adding if defined?(Spec::Example::ExampleGroup) made it crash in a different way.

<top (required)>': undefined method webdriver_method=' for Sauce:Module (NoMethodError)

The gem works if bundle exec is used. Pretty frustrating to have this crash the tests on startup with no backtrace.

In RSpec 3 the example group class is RSpec::Core::ExampleGroup so I'm not sure how this code works when the class name is wrong.

ExampleGroupFactory (referenced in rspec_one_support.rb) is an ancient relic from 2011 era RSpec. I think old RSpec support needs to either be removed or updated to not conflict with modern RSpec.

I confirm that #339 fixes the uninitialized constant issue for me. The webdriver_method error was an unrelated problem in my Gemfile.


[Bug] Release 5.196.2 broke Custom Tabs Android Login support

Describe the bug
In our app we use Custom tabs for Android. However this 5.196.2 release forced the web page to open in Duck Duck go. This is a problem with our login feature specifically as all 4 of our login services that we support send us a callback url that we listen for to complete our login process and obtain our refresh token. As a result this either forces us to force the user to use chrome or another supported browser otherwise they can no longer login. There should be a flag to specifically disable this for this use case.
How to Reproduce
Have an app that requires a web browser for login. Try to login to that app with Duck Duck go as the default browser. No longer able to login as it is impossible to pass the login result back to the app.
Expected behavior
There should be a flag to turn on or off this behavior so that login/oauth processes still work for apps.
Environment
- DDG App Version: 5.196.2
- Device: All
- OS: Android

@Sparowhawk Thank you for raising the issue.
In the How to reproduce section, you specified Have an app that requires a web browser for login. Could you please provide an example of such an app so that we can investigate further?

The VA Health and Benefits app is one such app. Any other VA app also uses the same web/oauth login.
The reason is they use id.me/dslogon or 2 other services that are rarely used. The issue is all those authentication services use web url redirects to pass back a token for further use in other api's.
So by opening up the url direct in the browser instead of the app it severs the callback nature allowing web logins to work.

Any veterans with only duck duck go as a browser on their device with the new update can no longer log in. If they have it as default with other browsers installed they currently can't login until they change their default until one of their prs get merged ignoring duck duck go if another browser is installed.

Thank you for the details, we acknowledge the situation.
I noticed that an exception for DuckDuckGo has already been incorporated into the VA app code CustomTabsIntentModule.kt#L96-L106.
We'd like to address this on our end, but we require access to an app for testing purposes. Since the VA app needs a US Government login which we do not have access to, we are unable to proceed with the fix until we find a suitable testing app.

Thanks @FaqatZubair1! This is very useful.

Try any mastodon client (as in my case is mastify). When you try to login on mastodon.social, it will redirect to oauth url.

@FaqatZubair1 This is now fixed in the latest version. Thanks for reporting.


[Feature] Add license filtering for code modules

Search before asking

[X] I searched the issues and found no similar issues.

Component
Transforms/code/code_quality
Feature
Capability to filter by permissive licenses for any new code data as a new module.
Are you willing to submit a PR?

[x] Yes I am willing to submit a PR!

Needed for release 1

@Bytes-Explorer i caved on proglang_select, but now we're repeating this pattern for a different column name?  We can't have a new transform for every attribute we want to annotate/filter on.  I recommend 1 of the following

Change filter transform so that instead of removing rows, it keeps all rows, but adds a new column that is set to True for what "would have been filtered. cc: @cmadam
Create a new transform that generalizes with proglang_select does for an arbitrary column and set of values.

I would strongly recommend one of these alternatives to creating a new special purpose transform.  We're a toolkit after all.

These are two separate functionalities and we need to think from a view of how an end user will use it. There can be many transforms that will use filtering at the end to filter. However coupling all the functionalities together may make it hard for an end user to use the toolkit, esp when the number of functionalities grow.

This is in progress in PR #257


Movie Render Queue

Is this compatible with UE4 Movie Render Queue? I have a Sequence in my level that plays back a poseai capture fine in Play mode, not Editor mode. But the character is entirely missing from renders

Hi, we don’t have any in-house experience with that aspect of UE4 so the specific use case is untested.
if you are playing back a precaptured fbx than it should work fine.  Maybe check what value was recorded for root position/hips if your character is missing? (Could your character just be moved well off camera?)
Otherwise if you are combining them live, if UE4’s LiveLink plug-in is compatible with the MovieRender Queue than I would expect our plug-in to work (as we are just providing a LiveLink Source).

Closing due to lack of reply.


FEATURE: Image Preview inside Preview Window

Did you check the docs?

[X] I have read all the docs.

Is your feature request related to a problem? Please describe.
We had some discussions here: https://github.com/nvim-neo-tree/neo-tree.nvim/discussions/831#discussioncomment-7291028 and thought of introducing image preview into neo-tree.
As I stated here: https://github.com/nvim-neo-tree/neo-tree.nvim/discussions/831#discussioncomment-7352011, the author of image.nvim added a feature to preview images inside a buffer using the kitty graphics protocol.
This is a good building block for image preview inside the preview window, and I thought of start working on it.
I already got a proof-of-concept working and will be submitting a PR once I'm able to test it thoroughly.
https://user-images.githubusercontent.com/41065736/277180763-b7152637-f310-43a5-b8c3-4bcba135629d.mp4
I made this issue to log my progress and maybe guide people who googled for image preview support in neovim here.
Any suggestion or advice is also appreciated.
Describe the solution you'd like.
I'll be working on this as soon as I got some spare time.
Describe alternatives you've considered.
No response
Additional Context
No response

Update: ready for the code when these issues get resolved.

https://github.com/3rd/image.nvim/issues/60
https://github.com/3rd/image.nvim/issues/61

@cseickel
I am thinking of adding a config option as follows. Do you agree with this change?
Modified       lua/neo-tree/defaults.lua
@@ -366,7 +366,7 @@ local config = {

-      ["P"] = { "toggle_preview", config = { use_float = true } },
+      ["P"] = { "toggle_preview", config = { use_float = true, use_image_nvim = false } },

TODO

[ ] Add some docs somewhere

@pysan3 I don't think the config option is needed. I think it would be enough to test for the existence of the image.nvim plugin and automatically enable the integration if the module can be loaded. Do you think there may be a situation where someone has the plugin installed but does not want to use it for previews in neo-tree?

Well actually there's a different image.nvim: https://github.com/samodostal/image.nvim which is also pcall(require, "image") == true.
How about keeping the config option and defaulting it to true?

Well actually there's a different image.nvim: https://github.com/samodostal/image.nvim which is also pcall(require, "image") == true.

🤦🏼 We should try to distinguish if it's the right one before we use it. There must be some property or method that we can use to determine whether it is the correct one.

How about keeping the config option and defaulting it to true?

Sure, if you think it might be needed then go ahead and add it.

There must be some property or method that we can use to determine whether it is the correct one.

Ok, will do 👍


Crash with the Latest version of the mod

latest.log

it somehow blames GregTech but it has nothing to do with it

Can confirm, only using FTB Quests + Optimizer mod & the required addons.
Logs: https://gist.github.com/Gbergz/da9ec4a636f9c66608c20bf1e1715ab6

interestingly, it also makes the mod Artifacts crash at launch
something about a missing item: night vision goggles

Nah that's just a fake error. Real error is the one I posted above.

thanks for the report, I'll check and fix it today

@TexBlock related to your pull request?

@TexBlock related to your pull request?

yes，Maybe we'll have to mixin both the forge and fabric side all over again?

@Gbergz pls check this version
FTBQuestsOptimizer-forge-1.1.1-1.20.1.zip

But I still couldn’t reproduce the problem with the same list of mods, tell me the details, do you install the mod on the server or client?

@bigenergy That version you posted above works.

@bigenergy That version you posted above works.

Thank you, I uploaded the corrected version to curseforge


after update 3.3.2 to 3.5.0 run dev  Named export 'stringify' not found at ModuleJob._instantiate

Environment
Nuxi 3.5.0                                                                                15:06:23
15:06:24
RootDir: E:/workspace/GuYi_production/display-shop-new-version                                                      15:06:24
Nuxt project info:                                                                                15:06:24

Operating System: Windows_NT
Node Version:     v18.14.2
Nuxt Version:     3.5.0
Nitro Version:    2.4.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      imports, app, css, vite, typescript
Runtime Modules:  -
Build Modules:    -

👉 Report an issue: https://github.com/nuxt/nuxt/issues/new                                                         15:06:24
👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new
👉 Read documentation: https://nuxt.com
Reproduction
Local operation without connection
Describe the bug
After upgrading from version 3.3 to version 3.5 npm install
run dev

I tried 3.4.3 again, everything is normal
I opened the configuration file again and found that all types reported errors, which did not appear in previous versions

Additional context
No response
Logs
1、
(property) autoImport: boolean
Argument of type '{ imports: { autoImport: boolean; }; app: { head: { title: string; meta: ({ charset: string; } | { name: string; content: string; } | { hid: string; name: string; content: string; })[]; link: { rel: string; type: string; href: string; }[]; noscript: { ...; }[]; }; }; css: string[]; vite: { ...; }; typescript: { ...;...' is not assignable to parameter of type 'InputConfig<NuxtConfig, ConfigLayerMeta>'.
  Object literal may only specify known properties, and 'imports' does not exist in type 'InputConfig<NuxtConfig, ConfigLayerMeta>'.ts(2345)
2、
[worker reload] [worker init] Named export 'stringify' not found. The requested module 'file://E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
                                                                                14:59:38
import pkg from 'file://E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js';
const { stringify, uneval } = pkg;

  import { stringify, uneval } from 'E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js';
  ^^^^^^^^^
  SyntaxError: Named export 'stringify' not found. The requested module 'E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js' is a CommonJS module, which may not support all module.exports as named exports.
  CommonJS modules can always be imported via the default export, for example using:

  import pkg from 'E:/workspace/GuYi_production/display-shop-new-version/node_modules/devalue/dist/devalue.umd.js';
  const { stringify, uneval } = pkg;

  at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)  at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)

Would you provide a reproduction? 🙏

Hi @danielroe @mokurofuzo, it looks like there is problem with nuxt/i18n module, we can reproduce problem with those steps:

Init new app npx nuxi@latest init my-app
Before npm i add new package: npm i -D @nuxtjs/i18n
npm i
npm run dev
Error from images above displays

installing edge version of i18n seems to fix problem.

@MrEraxd thankyou，let me try right now

@danielroe @MrEraxd thankyou guys，i fixed it by @nuxt/i18n 8.0.0-beta12，there is also a bug usecookie  can not be used in i18nconfig

I made the same mistake.

Remove node_modules folder and your dependencies lockfile and install your project again.
... Then restart volar/ts server.
🤞

I also got the same error.

In defineNuxtConfig, VSCode prompts me that I can only use these.

Same here with 3.5.3.
Only dropping this in helps
  experimental: {
    renderJsonPayloads: false
  },

Thank you. I have fixed it. It was the inconsistency between TS and the dependent version in my workspace that caused this error. 😁

@evanlong0926 could you provide a full example about what you did?

@evanlong0926 could you provide a full example about what you did?

The TS development dependency is installed in the dependency, and the TS global dependency is also installed locally. When you use ts, you'll see two version options:

If one of the ts files uses such a version:

Another ts file uses this version again:

The type errors I mentioned before will occur, but I think this problem is very unscientific, maybe VSCode brought.

I had the same error recently while starting to migrate from nuxt 2 to nuxt 3.
I can confirm that setting renderJsonPayloads (https://nuxt.com/docs/api/nuxt-config#renderjsonpayloads) to false fixed the issue for me.
export default defineNuxtConfig({
  // ...
  experimental: {
    renderJsonPayloads: false,
  },
  /// etc
 })


merge package template from arlac77/npm-package-template

Updated standard to latest version

Coverage remained the same at 76.744% when pulling 0bd66dda318cb71bb86bf75907f969c23b3dde1c on template-sync-1 into 5a633f05f8658fb8a4844b1d0c5b45cc1d9717d8 on master.

Codecov Report

Merging #86 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #86   +/-   ##
=======================================
  Coverage   76.74%   76.74%
=======================================
  Files          13       13
  Lines          86       86
=======================================
  Hits           66       66
  Misses         20       20

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 5a633f0...0bd66dd. Read the comment docs.


"Warn on shim overwrite" does not work ?

I've had shim for xargs from unxutils and it was replaced by shim from findutils
This merge is not working anymore ?
https://github.com/lukesampson/scoop/pull/2033

#2033 is working fine, but the unxutils.json doesn't contain any information about the available binaries. It just gets added to the %PATH% and just has higher priority if installed last. You could flip the directories in your PATH to fix it for now.
The unxutils manifest could be changed to include all binaries.

@r15ch13 oh yeah, this was the case, thank you. I don't know why this feature even exists, scoop shouldn't pollute PATH like this.


Ensure only code approved by appropriate reviewers gets merged into the DCP

We will use a service/tool called "Pull Approve" to achieve this (https://www.pullapprove.com/).
Overview:
The DevSecOps team are going to sign up for a pullapprove account.
PullApprove Overview
Enabling required status checks - GitHub
┆Issue Number: HCAB-411

Applies to DCP/1 only. If the need arises to implement this for future compliance/certification, we'll open a new ticket.


createAndSignTx return  Request failed with status code 404

as to this demo code, it works, but if change the URL and chainId to mainnet, get this error message, (node:44672) UnhandledPromiseRejectionWarning: Error: Request failed with status code 404
const terra = new LCDClient({
  URL: 'https://rpc-columbus.keplr.app',
  chainID: 'columbus-5',
});

import { LCDClient, MsgSend, MnemonicKey } from<EMAIL_ADDRESS>
// create a key out of a mnemonic
const mk = new MnemonicKey({
  mnemonic:
    'notice oak worry limit wrap speak medal online prefer cluster roof addict wrist behave treat actual wasp year salad speed social layer crew genius',
});

// connect to bombay testnet
const terra = new LCDClient({
  URL: 'https://bombay-lcd.terra.dev',
  chainID: 'bombay-12',
});

// To use LocalTerra
// const terra = new LCDClient({
//   URL: 'http://localhost:1317',
//   chainID: 'localterra'
// });

// a wallet can be created out of any key
// wallets abstract transaction building
const wallet = terra.wallet(mk);

// create a simple message that moves coin balances
const send = new MsgSend(
  'terra1x46rqay4d3cssq8gxxvqz8xt6nwlz4td20k38v',
  'terra17lmam6zguazs5q5u6z5mmx76uj63gldnse2pdp',
  { uluna: 1000000, ukrw: 1230201, uusd: 1312029 }
);

wallet
  .createAndSignTx({
    msgs: [send],
    memo: 'test from terra.js!',
  })
  .then(tx => terra.tx.broadcast(tx))
  .then(result => {
    console.log(`TX hash: ${result.txhash}`);
  });

I think https://rpc-columbus.keplr.app is not for LCD.

switch to those LCD endpoints, also get same problem

is the error from LCD 404? not 400?

is the error from LCD 404? not 400?

ah, sorry, when use the LCD endpoint, it change to "Request failed with status code 400", if use rpc endpoint, it's 404

did you use that mnemonic? you have to use your own mnemonic key (and derived address from it) or use testnet to confirm script works.

Can you try to catch the error for debugging?

did you use that mnemonic? you have to use your own mnemonic key (and derived address from it) or use testnet to confirm script works.

when use my own mnemonic, it works at mainnet. But if change the message from transfer token to delegate ust to anchor procotol', the error is Request failed with status code 400`.
hm, also already catch the error
 const mk = new MnemonicKey({
        mnemonic: req.body.mnemonic
    });

    const terra = new LCDClient({
        URL: TERRA_URL,
        chainID: 'columbus-5'
    });

    const wallet = terra.wallet(mk);

    const msg_1 = new MsgSend(
        wallet.key.accAddress,
        'terra1jnp8ez0nlen24hr8npmjhefd2facq0x4s6lnyp',
        { uusd: 10 }
    );

    const msg = new MsgExecuteContract(
        wallet.key.accAddress,
        'terra1sepfj7s0aeg5967uxnfk4thzlerrsktkpelm5s',
        {
            deposit_stable: {},
        },
        {
            uusd: req.body.amount,
        },
    )

    console.log(msg);
    try {
        const tx = await wallet.createAndSignTx({ msgs: [msg] });
        console.log(tx);

        const result = await terra.tx.broadcast(tx);
        console.log(result);

        res.json({tx_id: result})

    }
    catch(exception) {
        console.log(exception.message);
       res.json({error: exception.message})
    }

@seaify console.log(exception);, not exception.message

@seaify console.log(exception);, not exception.message

=> {"error"=>{"message"=>"Request failed with status code 400", "name"=>"Error", "stack"=>"Error: Request failed with status code 400\n    at createError (/home/ubuntu/cointest/releases/6179/node_modules/@terra-money/terra.js/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/home/ubuntu/cointest/releases/6179/node_modules/@terra-money/terra.js/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/home/ubuntu/coindtest/releases/6179/node_modules/@terra-money/terra.js/node_modules/axios/lib/adapters/http.js:293:11)\n    at IncomingMessage.emit (events.js:215:7)\n    at endReadableNT (_stream_readable.js:1184:12)\n    at processTicksAndRejections (internal/process/task_queues.js:80:21)", "config"=>{"transitional"=>{"silentJSONParsing"=>true, "forcedJSONParsing"=>true, "clarifyTimeoutError"=>false}, "transformRequest"=>[nil], "transformResponse"=>[nil], "timeout"=>30000, "xsrfCookieName"=>"XSRF-TOKEN", "xsrfHeaderName"=>"X-XSRF-TOKEN", "maxContentLength"=>-1, "maxBodyLength"=>-1, "headers"=>{"Accept"=>"application/json", "Content-Type"=>"application/json", "User-Agent"=>"axios/0.24.0", "Content-Length"=>367}, "baseURL"=>"https://lcd.terra.dev", "method"=>"post", "url"=>"/cosmos/tx/v1beta1/simulate", "data"=>"{"tx_bytes":"CqsBCqgBCiYvdGVycmEud2FzbS52MWJldGExLk1zZ0V4ZWN1dGVDb250cmFjdBJ+Cix0ZXJyYTE2aDNjZ2gwZ2x5dzltY3h1cGMwbHp3Z3hxbHh1ZDg0dm0yZHkwNxIsdGVycmExc2VwZmo3czBhZWc1wfewfewOTY3dXhuZms0dGh6bGVycnNrdGtwZWxtNXMaFXsiZGVwb3NpdF9zdGFibGUiOnt9fSoJCgR1dXNkEgExElQKUApGCh8vY29zbW9zLmNyeXB0by5zZWNwMjU2azEuUHViS2V5EiMKIQJV/2QHBapKLGljbO/GgUPwZm3xaHc90HTn8C2JsdIvGhIECgIIARgxEgAaAA=="}"}, "status"=>400}}

Hi, @seaify
Did you fix that error Request failed with status code 400?
I faced that issue, so I'd like to know how to solve that issue
Thanks.

that

sorry, nope

timeout"=>30000  ，I also encountered the same problem, and they all appeared frequently

switch to those LCD endpoints, also get same problem

Hello, have you met this problem, too? I've met this problem for months. Have you solved it?

Terra Network Live Support.
We received your complain kindly visit the official website to chat With a live support CLICK HERE

seem to be having a very similar issue. Looks to be some issue when simulating the transaction with the node to get the gas prices I believe. Have tried using different LCD endpoints. Any help appreciated

Found the issue,
The 400 error masks the actual underlying error from the endpoint.
So you need to more deeply inspect the returning message.
Creating a raw post message from that error output and looking at that might be the easiest way to do see it, if you can't inspect from your code editor.
In my case I was sending a larger value than my balance, so the gas simulation transaction was failing on that.
e.g.
{
"code": 3,
"message": "failed to execute message; message index: 0: 996465uluna is smaller than 1000000uluna: insufficient funds: invalid request",
"details": [
]
}

Found the issue, The 400 error masks the actual underlying error from the endpoint. So you need to more deeply inspect the returning message. Creating a raw post message from that error output and looking at that might be the easiest way to do see it, if you can't inspect from your code editor.
In my case I was sending a larger value than my balance, so the gas simulation transaction was failing on that.
e.g.
{ "code": 3, "message": "failed to execute message; message index: 0: 996465uluna is smaller than 1000000uluna: insufficient funds: invalid request", "details": [ ] }

hi, thanks for your remind, finally it works.
if use javascript, check  exception.response.data for detailed error message.
now attach the working code, mainly need to add fee
    const mk = new MnemonicKey({
        mnemonic: req.body.mnemonic
    });

    const terra = new LCDClient({
        URL: TERRA_URL,
        chainID: 'columbus-5'
    });

    const wallet = terra.wallet(mk);

    const msg = new Terra.MsgExecuteContract(
        wallet.key.accAddress,
        'terra1sepfj7s0aeg5967uxnfk4thzlerrsktkpelm5s',
        {
            deposit_stable: {},
        },
        {
            uusd: req.body.amount,
        },
    )

    const fee = new Terra.Fee(800000, { uluna: '10000' })

    try {
        const tx = await wallet.createAndSignTx({ msgs: [msg], fee: fee });
        const result = await terra.tx.broadcast(tx);
        res.json({tx_id: result})
    }
    catch(exception) {
       res.json({error: exception.response.data})
    }


Change entitlement check to return future.success only if authorized.

pg3/157.

rebased to master.

Merged as de9cc68db54499eee8dc802ecf34a67c2ce56f33


get.docker.com installs docker-engine instead of docker-ce

http://get.docker.com still installs docker-engine instead of docker-ce.
Is that normal?

ping @andrewhsu

There is a new package name, repository, GPG key, etc.:
https://docs.docker.com/engine/installation/linux/ubuntu/#install-using-the-repository

Yes, get.docker.com will install the docker-engine packages in a manner as it always has.
For new installations, it is recommended to use the new repository as pointed out by @RRAlex

@RRAlex: I know, hence my question
@andrewhsu: so, does that mean that get.docker.com is deprecated from now on? it's still recommended here: https://docs.docker.com/engine/getstarted/linux_install_help/
Just to be clear, it would not make sense to me that boths ways are recommended. It'd be either docker-ce from now on or docker-engine, but not both.

@andrewhsu: ping :-)

Yes, the download.docker.com repository should be used going forward. The get.docker.com repository is maintained to not break existing installs, but eventually no new packages will be published there (I don't think a definitive date was set for that yet).

@Silex would you be interested in opening a pull request in the documentation repository to update that page in the documentation?

You mean a PR to update https://docs.docker.com/engine/getstarted/linux_install_help ? Sure, but what should be done? Add a deprecate notice or replace the installation method so it uses the new repositories?

@Silex yes, that would be great! We should replace it with instructions for the new repositories. Hm, actually; that page does not seem to be linked from the menu, and this page links to the various installation instructions https://docs.docker.com/engine/getstarted/step_one/. How did you arrive on that page? Is it linked somewhere, through search? Perhaps it's an old page and needs to be removed
ping @mstanleyjones do you know about that page?

The link is at https://docs.docker.com/engine/getstarted/step_one/#docker-for-linux at line 82 (source https://github.com/docker/docker.github.io/blame/master/engine/getstarted/step_one.md#L82)

oh, you're right, hm Wondering if it should link to the general installation instructions instead. I'll leave that decision to @mstanleyjones for now 😊

@mstanleyjones: ping

I'm on it.

See https://github.com/docker/docker.github.io/pull/2354. I'll close this issue in favor of that PR.

I just want to clarify, why is https://get.docker.com/ being deprecated? I just found it yesterday and was very excited to find an officially maintained script to install docker on most distros. I work on a dockerized solution which gets installed on-prem for our customers, it's very disappointing to see that this would get deprecated. I want to give our customers the options of using whatever linux distro they want.
I really hope you reconsider, that script has incredible value for these kinds of use-cases. Being able to script installations much more easily is very important to us. I can't expect some of our customers with a lesser understanding of linux to use the steps here https://docs.docker.com/engine/installation/linux/ if they want to get set up quickly. Those steps are a huge speedbump that the script at https://get.docker.com/ almost entirely removes.
Thanks

IIUC get.docker.io was an automated way of executing whatever the installation instructions are (at the time). So if the installation instructions have changed to use a new repo (and new pkg name), then get.docker.io should be updated to reflect these.
Is/was the contract around get.docker.io different from what I just described?

I concur with the above. We have "install Docker" as a step in our Discourse install guide and get.docker.com made it easy. Why not just update get.docker.com as needed, so everyone can benefit from an easy one step install? The manual install instructions are way more daunting than the simple get.docker.com one liner.

If the decision ends up being to deprecate get.docker.com, please can the script be modified to output a deprecation warning? Otherwise people will silently install older versions if this ends up being true:

The get.docker.com repository is maintained to not break existing installs, but eventually no new packages will be published there (I don't think a definitive date was set for that yet).

Many thanks!

I echoed these concerns internally, and I think work is in progress for this, but /cc @andrewhsu

Hum, http://get.docker.com changed and installs docker-ce now.
Is this intended? was this communicated somewhere?

cc/ @andrewhsu

The commit that introduced this seems to be https://github.com/docker/docker-install/commit/87d90102ffa62ed157886a397d7ef24a79536fa7

The get.docker.com script always installed the latest version of docker, given that the docker-engine packages are no longer updated, and have been replaced by the docker-ce packages, the script was updated to install those packages.

Great, that's good to hear.
It's just that there was some very confusing messaging going on about this issue.

Apologies for that; plans were to no longer have an install script, and only have the manual installation steps. I put up some fights to convince people that that would be a bad idea, and in the end succeeded :tada:
For production (i.e.; custom configuration needed, specific version to install, etc.) the manual steps, or a script/playbook customised to your needs is still recommended, but the get.docker.com "express install" is here to stay

Does the https://get.docker.com/ script (and any scripts underlying it) correspond to any files on GitHub?

@impredicative yep, https://github.com/docker/docker-install/blob/master/install.sh


Scrimmaging Record API Improvements

After creating a new Battlecode 2025 episode, it appears that the Scrimmaging Record API has an internal error. As the endpoint already needed a refactor, now is a great time to dig into the endpoint and make sure it is ready for the new frontend release. There are two tasks for this issue, which are each explained in detail below... please reach out with any questions as this will be a big task.

[ ] Scrimmaging record API bug fix

[ ] Open the frontend. An error toast should pop up on your home screen :fearful:
[ ] Navigate to your terminal that is running your backend. Find the network request which is returning status 500 (example below)
[ ] Read the error output to find the path to the file that is generating the error! Take a glance around, maybe throw the file into an AI assistant to have it explain what the file is for and how it fits into a Django API. You should probably stop here and have a senior Webinfra dev explain how teh Django works (roughly)
[ ] Fix the bug! I think it should be pretty easy

[ ] Scrimmaging record API refactor

[ ] Currently, the API schema has separate endpoints for RANKED/UNRANKED/ALL. This is implemented as an OpenAPI Parameter (I believe? I could be wrong tbh). We would like to refactor this so that this is back under one endpoint, with W/L/T counts for each type of match. A before and after of the schemas is below.
[ ] Once you have implemented the new schema, you will need to run generate_types.sh to update our auto-generated API
[ ] After updating our types, you should fix the frontend API functions that will inevitably have many errors. NOTE: here you should probably stop and meet/hop on a zoom with me (Lowell) to discuss wtf a query factory/key/function is and how it will be impacted by this change 😄
[ ] Now, fix the frontend errors and make use of your glorious singular endpoint 🥳
[ ] Now, ask serena or Lowell for help with creating a breaking API release, and you're done!

Current schema:
compete/scrimmaging_record/
│
├── Ranked/
│   ├── wins:   ████ 42
│   ├── losses: ████ 18
│   └── ties:   ████ 5
│
├── Unranked/
│   ├── wins:   ████ 30
│   ├── losses: ████ 12
│   └── ties:   ████ 3
│
└── All/
    ├── wins:   ████ 72
    ├── losses: ████ 30
    └── ties:   ████ 8

New (desired) Schema:
compete/scrimmaging_record
│
└── {
    "Ranked": {
        "wins":   ████ 42
        "losses": ████ 18
        "ties":   ████ 5
    },
    "Unranked": {
        "wins":   ████ 30
        "losses": ████ 12
        "ties":   ████ 3
    },
    "All": {
        "wins":   ████ 72
        "losses": ████ 30
        "ties":   ████ 8
    }
}

Example of the server error in the log (note the trace :smiley:):

@beshrislambouli Instructions are all updated! Please reach out to the slack or a specific person (me/nour) with any questions you have or with help getting started with any of the numerous code sections you'll be nuking 🙃


create 1682 folder for MIT course

Also adds solar UAV model

I'm planning to merge this so students can use it right away; if there's feedback we can address it in new commits or issues.

Sounds good to me!


K8SPS-73 - Add haproxy test

Test name
Status

demand-backup
failed

auto-config
failed

init-deploy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
failed

service-per-pod
failed

sidecars
failed

limits
failed

version-service
failed

tls-cert-manager
failed

config
failed

gr-demand-backup
failed

one-pod
failed

scaling
failed

haproxy
failed

users
failed

We run 17 out of 17

commit: https://github.com/percona/percona-server-mysql-operator/pull/249/commits/cc17a4f5b57b6c43162328cc86061db0cb9eb225
image: perconalab/percona-server-mysql-operator:PR-249-cc17a4f

Test name
Status

auto-config
passed

demand-backup
passed

init-deploy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

config
passed

service-per-pod
passed

gr-demand-backup
failed

sidecars
passed

one-pod
passed

limits
passed

haproxy
failed

version-service
passed

tls-cert-manager
passed

scaling
passed

users
passed

We run 17 out of 17

commit: https://github.com/percona/percona-server-mysql-operator/pull/249/commits/0c9c2d460b7f88cab6e89586c7a10a3c24749d32
image: perconalab/percona-server-mysql-operator:PR-249-0c9c2d4

Test name
Status

auto-config
passed

init-deploy
passed

demand-backup
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

config
passed

service-per-pod
passed

gr-demand-backup
failed

sidecars
passed

limits
passed

one-pod
passed

version-service
passed

haproxy
passed

tls-cert-manager
passed

scaling
passed

users
passed

We run 17 out of 17

commit: https://github.com/percona/percona-server-mysql-operator/pull/249/commits/bd5527a64981941a2cffbbbbf2b4078ae1e395fc
image: perconalab/percona-server-mysql-operator:PR-249-bd5527a

Test name
Status

demand-backup
passed

gr-demand-backup
failed

auto-config
passed

config
passed

one-pod
passed

init-deploy
passed

haproxy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

service-per-pod
passed

sidecars
passed

limits
passed

version-service
passed

tls-cert-manager
passed

scaling
passed

users
passed

We run 17 out of 17

commit: https://github.com/percona/percona-server-mysql-operator/pull/249/commits/bd5527a64981941a2cffbbbbf2b4078ae1e395fc
image: perconalab/percona-server-mysql-operator:PR-249-bd5527a


[bug] fitler on change status does not work

Describe the bug
Exploring moon's filtering to replace lint-staged githook and want to filter based on the status of the files changed. Unfortunately, the filtering on change status does not work.
Steps to reproduce

Create a dummy root level task in //moon.yml

  ls:
    command: ls
    platform: system

Make sure there are changed files in git with various status such as modified or staged.

Run the task with the status filter as documented $ moon run root:ls --status staged

Expected behavior
The status filtering on staged should match the files that git shows are staged.
Environment
System:
OS: Linux 5.11 Ubuntu 21.04 (Hirsute Hippo)
CPU: (4) x64 Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz
Memory: 17.67 GB / 30.75 GB
Container: Yes
Shell: 5.1.4 - /bin/bash
Binaries:
Node: 18.11.0 - /usr/bin/node
npm: 8.15.0 - ~/.local/bin/npm
Managers:
Apt: 2.2.4 - /usr/bin/apt
Cargo: 1.64.0 - ~/.cargo/bin/cargo
pip3: 20.3.4 - /usr/bin/pip3
Utilities:
Make: 4.3 - /usr/bin/make
GCC: 10.3.0 - /usr/bin/gcc
Git: 2.30.2 - /usr/bin/git
FFmpeg: 4.3.2 - /usr/bin/ffmpeg
Virtualization:
Docker: 20.10.14 - /usr/bin/docker
VirtualBox: 6.1.26 - /usr/bin/vboxmanage
IDEs:
Nano: 5.4 - /usr/bin/nano
VSCode: 1.72.2 - /usr/bin/code
Languages:
Bash: 5.1.4 - /usr/bin/bash
Go: 1.16.6 - /usr/bin/go
Perl: 5.32.1 - /usr/bin/perl
Python3: 3.9.5 - /usr/bin/python3
Rust: 1.64.0 - /home/tom/.cargo/bin/rustc
Browsers:
Firefox: 96.0

Additional context
terminal output

```shell
$ git status
On branch ci/tune-up-eslint
Your branch is up to date with 'origin/ci/tune-up-eslint'.
Changes to be committed:
(use "git restore --staged ..." to unstage)
modified:   configs/ts-node-config/README.md
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified:   .vscode/extensions.json
modified:   configs/eslint-config-skipa/package.json
modified:   configs/jest-config/package.json
modified:   configs/ts-config/package.json
modified:   eslint.config.js
modified:   package.json
modified:   pnpm-lock.yaml
modified:   towel.ts
modified:   tsconfig.json
Untracked files:
(use "git add ..." to include in what will be committed)
.github/workflows/issues.yml
.moon/
apps/docs/bob.ts
apps/docs/eslint-print-config.json
moon.yml
renovate.json
scratch.js
tsconfig.options.json
$ moon run :ls --status modified
▪▪▪▪ root:ls (cached)
apps
configs
eslint.config.js
moon.yml
node_modules
package.json
packages
pnpm-lock.yaml
pnpm-workspace.yaml
README.md
renovate.json
scratch.js
towel.ts
tsconfig.json
tsconfig.options.json
turbo.json
Tasks: 1 completed (1 cached)
Time: 16ms ❯❯❯❯ to the moon
$ moon run :ls --status staged
▪▪▪▪ root:ls (cached)
apps
configs
eslint.config.js
moon.yml
node_modules
package.json
packages
pnpm-lock.yaml
pnpm-workspace.yaml
README.md
renovate.json
scratch.js
towel.ts
tsconfig.json
tsconfig.options.json
turbo.json
Tasks: 1 completed (1 cached)
Time: 12ms ❯❯❯❯ to the moon
$ moon run :ls --status untracked
▪▪▪▪ root:ls (cached)
apps
configs
eslint.config.js
moon.yml
node_modules
package.json
packages
pnpm-lock.yaml
pnpm-workspace.yaml
README.md
renovate.json
scratch.js
towel.ts
tsconfig.json
tsconfig.options.json
turbo.json
Tasks: 1 completed (1 cached)
Time: 14ms ❯❯❯❯ to the moon
</details>

@tomdavidson All of the subsequent calls are cached, so it just hitting that.
If you pass --log trace, what are the git commands that are running?

@milesj  OK sounds like I misunderstand the status filter. When I filter on status=changed, Im expecting to see the same files git status would show changed. When I filter on staged, I expect to see the same file git status shows are staged.
In this example, I filter on status=staged but it kinda looks  like the output of git status --porcelain --untracked-files -z  is not being filtered for stage and I am all the files from the git cmd.... and the list is the same regardless if I filter on status=modified, etc.
$ moon --log trace run root:ls --status staged
...
[debug 10:42:35] moon:action:run-target Running target root:ls
[trace 10:42:35] moon:utils:process Running command git hash-object --stdin-paths - .moon/project.yml .moon/workspace.yml package.json (in /media/tom/toms-data/Projects/ramlaw/webapps)
[trace 10:42:35] moon:utils:process Running command git ls-tree HEAD -r . (in /media/tom/toms-data/Projects/ramlaw/webapps)
[trace 10:42:35] moon:utils:process Running command git status --porcelain --untracked-files -z (in /media/tom/toms-data/Projects/ramlaw/webapps)
[debug 10:42:35] moon:action:run-target Generated hash 356a55ff98e12240e1b41acc5e231da364804a17f136b2f9af9da7b8b0de7e3e for target root:ls
[debug 10:42:35] moon:action:run-target Cache hit for hash 356a55ff98e12240e1b41acc5e231da364804a17f136b2f9af9da7b8b0de7e3e, reusing previous build
▪▪▪▪ root:ls (cached)
apps
configs
eslint.config.js
moon.yml
node_modules
package.json
packages
pnpm-lock.yaml
pnpm-workspace.yaml
README.md
renovate.json
scratch.js
towel.ts
tsconfig.json
tsconfig.options.json
turbo.json
...

@tomdavidson Ok, so I completely missed this, but you also need to pass --affected. https://moonrepo.dev/docs/run-task#filtering-based-on-change-status
However, --status doesn't change the "hash inputs" (which you can see at .moon/cache/hashes), so subsequent runs will still hit the cache if the files in the working tree haven't changed status since the last run.
On a side note, I'll look into making those CLI args exclusive.

@milesj interesting. I intentionally did not use --affected thinking it checks to see if files have changed and without it I could look at what --status does on its own. No that have used --affected --status staged no files are in the output at all and from the trace logging, git is not invoked. When I change a file and stage it, moon --log trace run root:ls --affected --status staged still shows no files. Also no change when I rm .moon/cache/hashes/*

@tomdavidson Is this available anywhere to test? If not, I can try and reproduce locally.

@milesj thanks for being willing to dig in on this - Im clearly not figuring it out.  Here is a copy that can be public https://github.com/tomdavidson/moon-status-filter and I invited you as a collaborator.
I set the task to local and did not observe a difference.

@tomdavidson Awesome, will take a look.
While I'm digging into this, can you outline exactly what you are trying to achieve? And what the flow would look like.

There is a handful of other filtering but the git based ones are:
precommit
Fast/light linting and formatting. Run prettier --write  and eslint --fix task filter to only files that have status=staged (and git add)
prepush
Before pushing the changes, Run prettier --check  and eslint as in precommit, but with env CI=true to enable the heavy eslint rules. Also run unit tests filtered to workspaces with changed files & their dependents.
CI
I would like to only run tasks in workspaces with files that have changed compared to main@HEAD (assuming a cloned working branch).  I'm not sure if --affected --upstream does this because I have first been paying around with the githook workflows.

@tomdavidson I have noticed a few issues. I think it has to do with it being a root level project. I'll look into it as part of 0.19 work.
With that being said, there may be a bit of an misunderstanding in how this works. So the --affected/--status logic determines whether to run the task or not. It won't filter down the file list. So for example, if only 1 file was modified in a project, the eslint/prettier would still run on the entire project, not that 1 file. I have some ideas on how to solve this in the future using tokens (https://moonrepo.dev/docs/concepts/token) but it doesn't exist yet.
For your precommit/prepush scenarios, a current solution could be using moon query touched-files (https://moonrepo.dev/docs/commands/query/touched-files). This returns a list of files that can then be passed to prettier and eslint directly. This would by pass the moon task flow, but is a stopgap solution.
For CI, that's exactly what the moon ci command is for. https://moonrepo.dev/docs/guides/ci

@milesj
--affected (a cross all commands) is a diff with the 3 potential comparisons where as --status  is filtering affected (hence one uses --affected with --status)?
The task filtering does not output list of changed files.... That is how I expected it to work, but I feel a bit dumb (and apologetic) here. My dummy task to check things out calls ls and I started expediting the list of files to be the filtered files or workspace dirs.
Im currently running prettier as a root level task (partly because prettier can not find .editorconfig otherwise ) but eslint as a workspace level task (as with unit tests because it can be much more involved than formatting.  moon query is a perfect for the root level prettier-like tasks (and eslint if Iit has the same usage). moon query looks very nice and I had overlooked it. I think the token or token functions to provide query output as input for the task workflow would be awesome.
But I am hopping to replace some of my scripts used run eslint and unit tests in each workspace that has changed files and be able to include dependents so Ill look for to 0.19 and hope I can do something like  moon run lint --affected --status staged in a precommit hook.
moon ci is just right, I love it.

Yeah, I'll look into adding the $affectedFiles token in the next month or two. This should pair nicely with moon run  :lint --affected --status staged as the pre hook and get you exactly what you want.

Was able to figure out the problem, and it was with root only projects. https://github.com/moonrepo/moon/pull/423

#423  nice, thanks for finding a solution so quickly.

Yeah, I'll look into adding the $affectedFiles token in the next month or two. This should pair nicely with moon run :lint --affected --status staged as the pre hook and get you exactly what you want.

niiiiiicce! Seriously, even though Im only poking around with moon on side, I am really diggin it. Thanks @milesj

I'll probably throw $affectedFiles into the next release, since it's rather light.

The token approach wouldn't work, but still got something working: https://github.com/moonrepo/moon/pull/424

Ya defining the query/filtering in the task definition would be quick slick but I think #424 is pretty great and will be perfect for my case.

@tomdavidson This has landed in the 0.19 release.


prevent direct calls to sdag entry functions

Original issue: https://charm.cs.illinois.edu/redmine/issues/738

Calls to sdag entries from within "serial" blocks of sdag entries return immediately (or at the first unfulfilled "when" block), like a message send, rather than integrating into the sdag workflow.  This is not the expected behavior.  Giving the function that implements an sdag entry method a different name than the entry method itself would prevent this, so it would be impossible to accidentally call mysdag() rather than thisProxy->mysdag().
This issue was reported by one of the speakers at the Charm++ workshop.

Original date: 2015-05-21 18:30:38

This is a serious issue of ease of use and principle of least surprise that we need to work out. We'll discuss it, and try to find something to do about it.

Original date: 2015-06-25 19:33:00

Figure out how to handle the case where the user really wants this functionality vs the case where someone stumbles into unexpectedly by nesting.

Original date: 2015-06-25 19:35:26

Per core meeting discussion, this is a semantic issue that needs to be worked out carefully, not just a coding task. Meeting between Phil, Jonathan, & Eric M to work out what to do about this.

Original date: 2017-02-06 20:59:36

Modified every sdag entry method to be implemented in .C as "sdag" + entry method name
In a .ci file if there's an entry method called mysdag() that is used with the when construct, it is implemented with a function "_sdag_mysdag". This prevents direct calls made to "mysdag()".
Gerrit:  ~~https://charm.cs.illinois.edu/gerrit/#/c/2205/~~ https://github.com/UIUC-PPL/charm/commit/7c127d8c5473a4aee6622cc0c167731570a4a5a5

Original date: 2017-06-05 18:44:12

Changed the prefix for sdag entry methods to "sdag_fnc" as "_sdag_init" is an already generated xi function.

Original date: 2017-06-13 20:49:50

Proposed API change, lots of corresponding code to change, not a priority for getting the release out.

Original date: 2017-11-09 16:16:53

Phil's note 2 years ago said "is a semantic issue that needs to be worked out carefully" and suggested a meeting. Is this a correct, consensus decision? (A minor issue is projections will show unexpected EP name. But that is easy to handle).

Original date: 2017-11-09 17:22:01

Fix: Gerrit: ~~https://charm.cs.illinois.edu/gerrit/#/c/2205/~~ https://github.com/UIUC-PPL/charm/commit/7c127d8c5473a4aee6622cc0c167731570a4a5a5
The current implemented fix is where an sdag entry method that contains when statement(s) gets renamed to "sdag_fnc"+name and thereby cannot be directly called. Sdag entry methods without when statements can still be directly called.
We did discuss it in core a few months back, but it'll be worthwhile to bring it up again esp because OpenAtom uses direct sdag calls and those will have to change.
Openatom build failure: (http://ppl-jenkins:8080/job/test-openatom/9872/console)

Original date: 2017-11-09 17:41:20

Ideally, charmxi should also produce an error message (in case the function name fname doesn’t match, but _sdag_fnc_fname matches) telling the programmer not to call sdag. Is that easy/hard/too hard?

Original date: 2017-11-09 18:41:32

Didn't entirely understand the example. Do you mean when the user declares an SDAG Entry method in the .ci as "fname" and then calls the xi generated method "_sdag_fnc_fname" directly? (instead of calling proxy.fname();)

Original date: 2017-12-08 18:17:34

This is waiting on the changes to be made on Openatom. (~~https://charm.cs.illinois.edu/gerrit/#/c/2205/~~ https://github.com/UIUC-PPL/charm/commit/7c127d8c5473a4aee6622cc0c167731570a4a5a5)

Original date: 2018-03-20 20:57:36

I have made changes to Openatom to convert direct sdag calls to proxy calls and have this change on a branch called nitin/sdag_changes in the Openatom repository. Need an openatom expert to review and merge this.

Original date: 2018-04-02 19:53:36

Openatom changes corresponding to this bug fix have been merged: https://charm.cs.illinois.edu/gerrit/#/c/openatom/+/3917/


Compute vs storage

Hey!
I really like what you are doing with versatiles. Thank you so much for your efforts!
I was looking into ways to provide vector maps myself in the past for a commercial product and did similar stuff to you in the generation phase, but chose a different approach for serving them.
I figured S3-Storage would be cheaper (and faster) then running a server that serves the tiles and pregenerated all zoom levels (up to 13 I believe). The biggest downside is that updating takes a very long time. So I would not have daily dumps of OSM.
Did you have thoughts about this too? I'm just curious about your considerations.
Edit:/ Just to make sure.. By storage I mean storing the pbf-files as they are being consumed by maplibre-gl and co. My understanding is that shortbread is, itself, also an intermediate format. But maybe I am wrong about that?

If you want to use VersaTiles only with AWS S3, you can:

Extract all tiles to a folder (versatiles convert --bbox ... --max-zoom ... "https://download.versatiles.org/osm.versatiles" ./folder/) and synchronise them, but this could take a long time.
Alternatively, you can convert them to a *.pmtiles container (versatiles convert ... "https://download.versatiles.org/osm.versatiles" osm.pmtiles) and use the Protomaps MapLibre Plugin, but I think the latency of loading the map tiles might be an issue for you.

I would suggest a third option:

Upload the osm.versatiles to AWS S3
Use AWS Lambda with NodeJS and e.g. @versatiles/server to serve the tiles from the bucket container to an AWS CDN.

We use a similar approach in Google Cloud and it works really well. Basically your only cost is the CDN traffic cost as Lambda is almost free.
But we haven't tested it in AWS yet. So we might have to tweak it a little bit, but I would be happy to help you with that... depending on your timeline ...


Initialize NewRelic before Rails' config-initializers

Before, the initializer for NewRelic did not specify any ordering. In some situations, Rails will order its load_config_initializers before NewRelic's newrelic_rpm.start_plugin. This is a problem if NewRelic is called in a config-initializer (e.g. when defining method tracers) and will output the following warning:
Agent unavailable as it hasn't been started.

This change ensures that newrelic_rpm.start_plugin always gets loaded before config-intiializers are.
The problem is detailed and the fix is demonstrated here: https://github.com/tonyta/newrelic_warning/pull/1

An unrelated dependency loading issue is fixed in https://github.com/newrelic/rpm/pull/279/commits/cc9f74a53c1f2f3d9a4d05a48418b15dfcf22952 to allow tests to pass.

The changes between https://github.com/newrelic/rpm/pull/279/commits/4b3c20034093961c0e9c48f073fadb72d857f8fe and https://github.com/newrelic/rpm/pull/279/commits/cc9f74a53c1f2f3d9a4d05a48418b15dfcf22952 don't seem to account for the new test failures (which might be related to issues on the Rubygems server). The failures are likely nondeterministic and could probably just be retried. ¯\(ツ)/¯
Hope this helps!


Develop

Coverage increased (+0.9%) to 54.641% when pulling d03e1e7c87e6d2c4fe03c5e6252a3b7138e4ce0b on develop into 65d430ee4224051d14a00846090c20e5f9f9f643 on master.


Jenkins sending PR details

I am using this system to send coveralls data from a Jenkins CI instance, passing in a coverage.xml file.
I have found that the push to Coveralls misses some useful detail about the build such as:

It reports the PR ID instead of the branch name. This is due to how Jenkins mutlibranch git handling works. Instead of using git branch it's necessary to inspect the Jenkins envvar CHANGE_BRANCH which contains the real branch name.
The field service_build_url is currently sending the URL of the server, whereas it should send the Jenkins envvar BUILD_URL which links to the specific build
I have been told by Coveralls support that to send this as a PR rather than a "push" action it needs the field service_pull_request set; this can come from the Jenkins envvar CHANGE_ID

As far as I can see for the second two changes we could make these in CliEnvVarsCollector but for the first I am unsure how to override the git branch name. I'm happy to make a PR if we can figure out the best way to achieve it.

Hello!
This is James from coveralls.io. I'm available to help sort out the details in terms of what JSON the Coveralls API expects/requires in the body of POSTs to the https://coveralls.io/api/v1/jobs endpoint.
I have subscribed to this issue. Feel free to at-mention me, or reach out to<EMAIL_ADDRESS>


Add GitHub Action build workflow

Add the build and test GitHub Action workflow.
This PR will be follow up by one for linting and one for codecov.
Added the ros2.repos list so that it includes the repos used by Travis as well.
Signed-off-by: Anas Abou Allaban<EMAIL_ADDRESS>

I am not sure I follow why we need the ros2.repos file. I would prefer not hardcoding this list as it might change. Is there a way we can use the upstream one from ros2/ros2?

I would prefer not hardcoding this list as it might change.

I agree, this is a WIP to verify that having this repo file does in fact result in a successful build. I will update this to use the workflow suggested here:
# Run the generator and output the results to a file.
- run: |
    rosinstall_generator <package-name> --rosdistro <target-distro> \
    --deps-only --deps --upstream-development > /tmp/deps.repos

@piraka9011 any news on this? I would be happy to have at least the set of linters be part of the repo in order to iterate faster on existing PRs.

Sorry about the delay, see #33.

Is this ready for merging? The ros2 repos files is a little unfortunate but do you see how we could rid of it in the future?

Is this ready for merging? The ros2 repos files is a little unfortunate but do you see how we could rid of it in the future?

Let me try the rosinstall_generator workflow. Otherwise, I'll use the repos file.

Any conclusion on this?

There's is this on the way: https://github.com/ros-tooling/action-ros-ci/pull/121
That would be a little bit more handy as we had to specify the ros2 upstream repos file plus an overlay one which only holds the ros-controls packages.


Virtual functions?

Why are all of these functions marked as virtual?
I can't imagine any reason that they would be imported into another contract, so no need to mark them as virtual.
https://github.com/EBOGDAO/og-dapp/blob/0a2e2ecfae21dc4677f6c4cc6a17992286c2f362/contracts/Agreement.sol#L74-L111

Issue is addressed PR: https://github.com/EBOGDAO/og-dapp/pull/12
Won't close until merged


chore: auto-publish docker images

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1373  👈 (View in Graphite)
#1372
#1371
#1361
#1363
#1370
#1369
#1368
#1367
#1366
#1365
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Does it accept grammars with epsilon?

Does it accept grammars with epsilon? If yes, then how do I input it?

I think for epsilon we need to use ^

@megablazikenabhishek Yes it does accept grammars with epsilon using the ^ symbol - I've mentioned it under the Grammar Syntax section of the README: ^ is treated as the null symbol.


Allow to recompile object in different database

... via object editor's interface - it is suitable when I want to sync object in a number of databases (e.g. test and prod). It could be implemented as shown

Thank you for the idea.


Provide an action to automatically squash the commits belonging to the given branch

...and use the message of the first commit of the branch as the resulting message.
This can be realized as an interactive rebase onto fork point (#598)... but actually, most cases when the interactive rebase TODO list is edited is just exactly that - squashing the commits. This can possibly be implemented in a simpler way, e.g. by git commit-tree with tree = HEAD@{tree} and parent commit = current branch's parent branch tip.

For the details, just see how git machete squash is implemented (git commit-tree + git update-ref). Not sure if it's gonna be easy to mimic with JGit, tho.


Update readme.md with new pictures of the app screens

Is your feature request related to a problem? Please describe.

Currently readme.md contains the old version app photos.

Describe the solution you'd like

Update those with new pictures

@Akshatji800 please add first timer only tag to this issue. Thanks!

@Akshatji800 please add first timer only tag to this issue. Thanks!

@Sudhanva-Nadiger do you want to take this issue or should I assign it to @Adiii1436 ?

Assign this to @Adiii1436 ! No problem

Yes please assign me the issue @Akshatji800

I can update readme.md with new pictures of the updated app, can you please assign this issue to me?

Just send a PR.

Is it okay if I work on this since no PR is submitted yet?

Is it okay if I work on this since no PR is submitted yet?

Go ahead if you think you can send a PR quickly.
Currently I am not assigning this issue to anyone as it is a very basic job. The first PR will be considered as  a legit PR.

Are just normal screenshots okay or do you want them displayed in an emulator skin?

Are just normal screenshots okay or displayed in an emulator skin?

Are just normal screenshots okay or displayed in an emulator skin?

See if you can make something like the images under Application Preview in this repo readme.
https://github.com/Akshatji800/Relive

Are just normal screenshots okay or displayed in an emulator skin?

See if you can make something like the images under Application Preview in this repo readme. https://github.com/Akshatji800/Relive

Canva was used to make this

Okay got it. I'll start working on this

Hey @Akshatji800, I've updated the screenshots. They are in a bit different format but we can add some sort of text at the top of the images if that's what is required.
Let me know your views.

Okay sure, I'll make the changes and send the PR.

Hey @Akshatji800, I've committed new screenshots to the PR. Please take a look.

Hey @Akshatji800, I've committed new screenshots to the PR. Please take a look.

Again the same issue continues. Weird alignment of the screenshot inside the emulator border component

Please check the updated screenshots.

Hey @Akshatji800, Please take a look at the updated screenshots.

Hey @Akshatji800, Please take a look at the updated screenshots.

Hey @virajbhartiya ig there is still a lot of scope of improvements. You can use this website to create the mockups and then combine them in canva. Also make sure you include all the features included in the previous readme along with adding the new features

Hey @Akshatji800, I've updated the screenshots. I haven't made a collage of them so they can be aligned as per the screen size on the readme. But I've set their size in which they'll be visible in the readme
Please review it

Hey @Akshatji800, I've updated the screenshots. I haven't made a collage of them so they can be aligned as per the screen size on the readme. But I've set their size in which they'll be visible in the readme Please review it

@virajbhartiya can you please use black frame mockup device and keep the full screenshot without cropping it from top and bottom.
For example:

Sure @Akshatji800, I've made the changes, black frame, no notch, even the camera isn't overlapping with the screenshot, and it's the full screenshot
Please review it


Keyword: Pi -> Fn, λ -> fn

These symbols are too likely to be used as a variable name for mathematicians and type theorists.
Note: one can still use \ for lambda abstraction.

Why the coverage was harmed this much

Why???

Let me guess: the producer no longer hits Fn A → B wdyt @imkiva

Let me guess: the producer no longer hits Fn A → B wdyt @imkiva

I don't know. I didn't replace all Pi with \forall. There still exists Fn in test sources.

Codifier looks unreachable in tests.

bors merge


'Bring your own vnet' for admin offer

Changes:

UX: group networking related configurations under 'Networking' tab.
Disable DNS configuration when deploying to an existing VNET.
Not to create NSG when deploying to an existing VNET.
Use 'StorageV2' Storage account to enable private endpoint, then mount file share with private IP address to avoid networking issues

Testing:
Manually tested with private offer, with&without SSL using new&existing VNET
Stay as draft because we are collecting feedbacks from partners

Review notes from 2022-05-18 meeting

On the Networking tab, make it so the VNET control is hidden behind a show/hide yes/no radio button.  Set to No by default.  Text "Customize the virtual network for this deployment".  Tooltip, "If yes, you can customize the virtual network into which the offer will deploy the WebLogic Server VM.  If no, the offer will create a new virtual network."


Change the name of the Keyboard

It's currently nice!60, change it to leftboard  in all files

done


Include asset swap in deal ticket

Story
As a user
I want the system to detect if I have a swappable asset and perform that swap automatically on the deal ticket
So that it saves me the extra clicks of converting it
Acceptance Criteria

[ ] The deal ticket detects if I have none of the asset required for the market BUT do have some of another asset which could be swapped using a spot market
[ ] If this is the case the deal ticket shows an info box

[ ] Box explains that I can swap from asset X into the required asset in order to make this trade
[ ] Box tells me the expected slippage on that swap

[ ] If the user clicks the submit button the system sends a batch transaction that first swaps the asset and then performs the desired trade

Issues

[ ] The system somehow deals with slippage here ... ultimately you will not know the exact amount that is going into the resulting order until the first TX has executed ... which presents a problem
[ ] Might be this needs to be a two click operation in reality ... swap first ... then execute trade

Tasks

[ ] UX (if needed)
[ ] Design (if needed)
[ ] Team and stakeholder review
[ ] Specs reviewed and created or adjusted
[ ] Implementation
[ ] Testing (unit and/or e2e)
[ ] Code review
[ ] QA review

Sketch
Additional details / background info

There is not enough spot liquidity on the network currently for this to be remotely viable


Puppet Agent Certificate Request Not Working

Hi,
While following along with the instructions from README from the repo. At step [Playing nice with others] (https://github.com/rfkrocktk/docker-puppetmaster#playing-nice-with-others) I got an issue as the output for signing the agent certificate is Warning: Setting manifest is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1141:in `issue_deprecation_warning')
![Signing Agent Certificate] (http://i.imgur.com/pq1Sjxr.png)
I will have to manually log into the puppet node and invoke the puppet agent with root@dockerduck:~# puppet agent --server ultramaster --waitforcert 60 --test to make the certificate request to puppetmaster.
Any idea why this happens?

That's not a bug, it's a deprecation warning. I wanted to still support the old syntax, so the deprecation warning comes from the default configuration that ships from Puppet's own package from their Debian repository.
Refer to the Puppet docs about this. The problem you're reporting also happens with Puppet and a Puppet Master outside of a container, it's just Puppet's policy for security. Puppet uses PKI, so every agent must have its own client-side SSL certificate that is signed by the CA that is hosted by the Puppet Master.


chore: askem model representation update

Summary
Update to model-representation schema
TODO list, roughly in sequence

[x] Copy model schemas from https://github.com/DARPA-ASKEM/Model-Representations
[x] Create converter to go from AMR-Petri to IGraph for rendering/editing
[ ] Update to petrinet-renderer (AMR -> Graph)
[ ] Update model-page to use new schema

[ ] Model page update
[ ] Discussion on parameter vs config as first-class citizens in TDS when creating new config/parameters

[ ] Second round of updating and refinement of schemas from https://github.com/DARPA-ASKEM/Model-Representations, because some things are likely to change...
[ ] Update to data explorer

[ ] Breaking changes to facets
[ ] Breaking changes to search
[ ] Breaking changes to search items

[ ] HMI Server cleanup, remove unneeded entities and classes
[ ] HMI Client cleanup, typing and things

TODO list, can do in parallel

[ ] TA1 Equation API changes
[ ] TA1 model extraction API changes
[ ] TA2 Stratification changes. in model-service

[ ] Check stratification can take in new model format
[ ] Check the result of stratification can be converted back into new format

[ ] TA3 Simulation service API changes

[ ] Check new model format is supported
[ ] Check if we can reset ENABLE_TDS flag back to true

Superseded by https://github.com/DARPA-ASKEM/Terarium/pull/1181


example1 correct pumping power?

Per @kfbeckers via email:
Are we sure GEOPHIRES example 1 is still calculated correctly?
We are producing 50 MW of heat but only get 1 MW of net power because the pumping power is so high. I was wondering why that is? Originally, example 1 had lower pumping power I believe but I know some updates have recently been implemented that may have changed the pumping power? I increased the wellbore diameter and the injectivity/productivity index but they had limited impact.

@kfbeckers The pumping power increased from 0.21MW to 4.37MW when we updated calculations to account for pressure, see:
https://github.com/NREL/GEOPHIRES-X/blob/48f15b4705be0a03532d061a90a8959eb0c33f8a/src/geophires_x/WellBores.py#L358-L368
Do these calculations look correct to you?

Yes, it appears the vapor pressure equation of water is not correct. Right now, we have CP.PropsSI('P','T','P') which will just return the 'pressure' we provide to the function. By definition, the vapor pressure is the pressure at which the fluid starts boiling for a given temperature, and hence solely depends on temperature. The equation we have in the "else" statement ((quantity(CP.PropsSI('P', 'T', celsius_to_kelvin(Twater_degC), 'Q', 0, 'Water'), 'Pa')
.to('kPa').magnitude))
is the correct one. Maybe using that one should should fix the pumping power?

@kfbeckers I staged a PR for my fork with the change you suggest - can you take a look at the effect on the example outputs and see if it looks right? View at https://github.com/softwareengineerprogrammer/GEOPHIRES-X/pull/19/files#diff-3649ae9ab87dcc5ad182ea6a25b745e05b9cf05f17b8d7ad468d4b0ab525e2b7 (you will probably need to press "Load Diff" for each of the .out files to see the difference)


Second Entry not constrained to stay in window

Second Entry draggable is not constrained to stay in window.

done


add heos to latest

GitHub: https://github.com/withstu/ioBroker.heos
Forum: https://forum.iobroker.net/topic/10420/vorlage-denon-heos-script
Please review and add to Latest.

RE-CHECK!

Automated adapter checker
ioBroker.heos

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "heos" in latest repository

Add comment "RE-CHECK!" to start check anew

@GermanBluefox @Apollon77 Any updates here? Can I support you somehow?

mega sorry ... in the next days

Hey,

please make sure thall all Timeouts (also https://github.com/withstu/ioBroker.heos/blob/0ad694a5e3a8b04a92eaa9504f37023a6590a7a6/lib/heos-player.js#L798 ) are reset in onUnload!
please make sure only to use desfined roles! see https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/stateroles.md#media
after all sleep you need to check that the adapter was not "unloaded" in between ... https://github.com/withstu/ioBroker.heos/blob/0ad694a5e3a8b04a92eaa9504f37023a6590a7a6/lib/heos-player.js#L1448

@Apollon77 Thanks for the feedback. I've fixed the following in the version 1.6.1:

clear timeouts and intervals before unload
adapt all roles to the defined role list
remove the sleep in the tts module completely

Thank you for the fast reponse, welcome in the repo


fix not to check tag and variable placeholders when configured as secondary

out_file has been used as plugin to dump data in secondary for a long time, and
that configuration looses consistency about chunk keys (even in v0.12).
But increment placeholder of out_file can create another file name (by just numbering) for such cases.
This change makes v0.14 to work with such configuration...

@repeatedly could you review this change?

LGTM.
Further improvement, how about warning message like "For secondary, using secondary_file instead of file is recommended"?

It's not bad but a bit troublesome to show that message only when primary plugin is NOT out_file plugin.


Add app.createRouter function

Added the functionality from #2564
(Initial PR here: #3620)

I see this is being targeted at the 5.0 branch. I don't see any breaking change here, or am I missing something? If it's just a new non-breaking feature, we should land in 4.

@dougwilson I'll make sure to incorporate the requested changes. It could probably land in 4.x. Should I target against master or the 4.x branch in that case?
And I don't know if I'm stupid or something but the linter doesn't complain about my code at all:

The linter doesn't check for Standard JS style, because we're still converting the project. Only new code needs to follow it. From the guidelines:

Follow the JavaScript Standard Style and npm run lint.

It says to follow the JavaScript Standard Style and npm run lint. You have to do both, not just one :)

PR'ed thes changes against master instead and fixed everything you asked for.


Updated user-guide

Fixes issue #678. As we no longer supports setting provider by environment
variable, this PR will remove documentation for the same.

@cdrage review please :)


Issue with string concat and decoding the value

Environment information

OS: macOS
Python Version: 3.7
ape and plugin versions: latest

What went wrong?
OK, so this is a bit of weird edge case that I found.
I have a solidity method like this:
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.4;

contract ShouldFail {
    string public concatres = "";

    function methodB1(bytes32 lolol) public {
        string memory converted_lols = string(abi.encodePacked(lolol));
        string memory result = string.concat(converted_lols, " Captain Janeway");
        concatres = result;
    }
}

It takes a bytes32, converts it to a string, and then concats another string (" Captain Janeway") to the end of it.
Then, it stores it in a public string getter.
I go to check the result in my Pythons and this is what happens:
contract_b.methodB1("aabb", sender=owner)  # Succeeds
contract_b.concatres()  # Fails

Failure message:
DecodingError: ('utf-8', b'\xaa\xbb\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00 Captain Janeway', 0, 1, 'The returned type for this function is string which is expected to be a UTF8 encoded string of text. The returned value could not be decoded as valid UTF8. This is indicative of a broken application which is using incorrect return types for binary data.')

Solidity seems to pad my arguments before doing the concat.
How can it be fixed
I am not sure

Further experimentation has shown that Solidity code does not even compile in Remix:
Invalid type for argument in the bytes.concat function call

and thus this may be a problem with solc

I will close this as soon as I figure out where to open the issue in Solc

I added a comment here: https://github.com/ethereum/solidity/issues/12087 for now


Request Camera permission, necessary for 7.1

Fixes:

crash on Android if targetted with SDK 7.1 (android:targetSdkVersion="25")

Changes Proposed in this pull request:

Runtime request of Camera permission, necessary for 7.1

There is no need for the camera permission as your application is not the application that is accessing the camera.

@jamesmontemagno please, try with android:targetSdkVersion="25" on app manifest and you can look a strange behaviour regarding camera permission. The app crashes because has no camera permissions, also if the picture is taken with the external camera application. I know that it's strange, but I've tested on OnePlus 3 (Android 6) and LG G6 (Android 7).
Thanks for your time.

While I investigate I recommend that you use the permission plugin to handle the permissions yourself as that is highly recommended.

I just ran it against compile & target SDk of 25 on my Nexus 6P and had no issues at all.
https://developer.android.com/training/camera/photobasics.html
Can you put your stack trace and logcat into gist.github.com

@jamesmontemagno yes, I'm using your plugin to request the permissions, using the code included in my pull request
This is the stack trace:
https://gist.github.com/MarcorOnline/948590ccc56c86d757f49871d10fac7f
This is my sdk declaration in the manifest:

Thanks for your support

Can you share your manifest? Did you add a camera permission to it? You shouldn't need to at all, nor does this library.

@jamesmontemagno of course, I've just replaced my package id
https://gist.github.com/MarcorOnline/bbd8ae5c552927f3e6d3069b6509232a
Thanks

Yes, so if you have the camera permission in your manifest then you would need to request the permission.
Although you don't need it, so remove it and it will work just fine.

I have an idea on this to help optimize.

When I've found the bug I didn't have the CAMERA permission on manifest. I've added it to try to solve the problem.
I know that it's a very strange bug... but thats it.
To be sure I've retried:

uninstalling the app
removing the CAMERA permission from manifest
deleting bin and obj
cleaning and rebuilding

The crash persist...

Here it is from the source:
https://developer.android.com/reference/android/provider/MediaStore.html#ACTION_IMAGE_CAPTURE
Note: if you app targets M and above and declares as using the CAMERA permission which is not granted, then atempting to use this action will result in a SecurityException.
As you can see it is not required. However, the next beta will now check to see if you did mark the camera permission and try to request.
However you should attempt to check this with the permission plugin.

Here is also a good SO on it: http://stackoverflow.com/questions/32789027/android-m-camera-intent-permission-bug

@jamesmontemagno yes, I've followed the same your stackoverflow link to understend how to fix my problem. I'm happy to hear that you will introduce a double check for this issue.
Thanks again for your fast support


Context

Browser: Chrome
Server OS: MacOSX
PHP version: [e.g. 7.4]

Additional details
Appears to be cause by   value: @entangle($formComponent->name).defer, found in rich-editor.blade.php line 42

Hey! I will write some documentation on this... but it happens when you use components in the Filament\Forms\Components namespace rather than the Filament\Resources\Forms\Components namespace.
Components in the second namespace automatically prepend record. to the name of the field, so they can be used to write to the $record property on the Livewire components that create and update records. If you'd like to try it for yourself - change the name to record.description and watch the error disappear.
The namespace definitely needs clarifying in the docs though 👍


i change store default data，but vuex-persistedstate  not  update sesseionStorage data

vuex-persistedstate version:^3.0.1
node version:12.16.2
npm (or yarn) version:

Relevant code or config
// store.js
import persistedState from 'vuex-persistedstate'
persistedState({ storage: window.sessionStorage })

// modules product.js
  specificList: [
    {
      agencySalePrice: null,
      amount: 8573,
      cost: 23.66,
      id: '1910151158559620003',
      material: { id: '1904250309340100000', parentId: '0', name: '钻石', },
      list: 1,
      name: '钻石',
      orderNum: 30,
      parentId: '0',
      priceType: 0,
      productId: '1910151158559620001',
      putaway: 1,
      qrCode: '45645645645',
      remarks: '',
      salePrice: 50.33,
      saleUniformFee: null,
      specification: null,
      totalWeight: null,
      uniformFeeType: 0,
      updateTime: '2020-05-11 14:52:39',
      weight: null
    }
  ]

What you did:
i change modules product.js as:
specificList: [
    {
      agencySalePrice: null,
      amount: 8573,
      cost: 23.66,
      id: '1910151158559620003',
      material: { id: '1904250309340100000', parentId: '0', name: '钻石', },
      list: 1,
      name: '钻石',
      orderNum: 30,
      parentId: '0',
      priceType: 0,
      productId: '1910151158559620001',
      putaway: 1,
      qrCode: '45645645645',
      remarks: '1121212',// i change this key to 1121212, it origin value is ''
      salePrice: 50.33,
      saleUniformFee: null,
      specification: null,
      totalWeight: null,
      uniformFeeType: 0,
      updateTime: '2020-05-11 14:52:39',
      weight: null
    }
  ]

What happened:
i change remarks  from '' to '1121212''
but sessionStorage data is not update ,the remarks key still empty,not update from store

Reproduction sandbox:

Problem description:
Suggested solution:

Keep in mind you need to navigate away from the current page to see your session storage get updated.  Whilst on the same page, your Vuex store lives in memory.

@rfox12 thanks for answering