Svelte preprocess build error (npm run dev works fine)

this is my package.json
{   "name": "core",   "version": "0.0.1",   "author": {     "name": "Abhijit Gujar",     "email"<EMAIL_ADDRESS> },   "keywords": [     "csa-template"   ],   "scripts": {     "dev": "snowpack dev",     "build": "snowpack build",     "test": "web-test-runner \"src/**/*.test.js\""   },   "dependencies": {     "cesium": "^1.78.0",     "ol": "^6.5.0",     "svelte": "^3.30.0",     "tabulator-tables": "^4.9.3",     "tailwindcss": "^2.0.1"   },   "devDependencies": {     "@snowpack/app-scripts-svelte": "^1.8.4",     "@snowpack/plugin-dotenv": "^2.0.4",     "@snowpack/plugin-svelte": "^3.3.0",     "@snowpack/web-test-runner-plugin": "^0.1.4",     "@testing-library/jest-dom": "^5.11.4",     "@testing-library/svelte": "^3.0.0",     "@web/test-runner": "^0.10.0",     "@zerodevx/svelte-toast": "^0.1.4",     "autoprefixer": "^10.0.4",     "chai": "^4.2.0",     "husky": "^4.2.5",     "jest": "^26.4.2",     "lint-staged": "^10.2.13",     "postcss": "^8.1.10",     "postcss-load-config": "^3.0.0",     "prettier": "^2.2.1",     "prettier-plugin-svelte": "^1.4.1",     "rollup-plugin-buble": "^0.19.8",     "snowpack": "^2.17.1",     "svelte-preprocess": "^4.1.1"   },   "husky": {     "hooks": {       "pre-commit": "lint-staged"     }   },   "lint-staged": {     "*.{js,css,md}": "prettier --write"   } }
This is error when i build (NOT when in development)
[snowpack] ! building source…
[snowpack] ✘ /home/abhijit/projects/alpha_projects/frontend_selection/map_3d/src/core/src/Components/SlideViewer/Map.svelte
Error: Cannot find module './transformers/css'
Require stack:

/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/svelte-preprocess/dist/autoProcess.js
/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/svelte-preprocess/dist/index.js
/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/svelte.config.js
<EMAIL_ADDRESS>/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/snowpack/lib/config.js
/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/snowpack/lib/build/build-pipeline.js
/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/snowpack/lib/commands/build.js
/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/snowpack/lib/index.js
/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/snowpack/index.bin.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:965:15)
at Function.Module._load (internal/modules/cjs/loader.js:841:27)
at Module.require (internal/modules/cjs/loader.js:1025:19)
at require (internal/modules/cjs/helpers.js:72:18)
at /home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/svelte-preprocess/dist/autoProcess.js:50:77
at async Object.exports.runTransformer (/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/svelte-preprocess/dist/autoProcess.js:50:29)
at async /home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/svelte-preprocess/dist/autoProcess.js:111:29
at async script (/home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/svelte-preprocess/dist/autoProcess.js:136:33)
at async /home/abhijit/projects/alpha_projects/frontend_selection/map_3d/node_modules/svelte/compiler.js:28626:32
at async Promise.all (index 0)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: snowpack build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

I believe that this is fixed in #2707, would love your help testing to confirm! (you can test out that PR via npm install snowpack@next)


403 forbidden issue happened

Issue description
It seems like there are issues when using playUrl(),
error shows as below
Error: 取得的 Hichannel 頻道名稱「ASIAFM 亞洲電台」廣播電台 m3u8 網址檢查失敗：Request failed with status code 403
at HiNetHichannel.playUrl (/node_modules/hinet-hichannel-taiwan-radio/src/HiNetHichannel.js:68:19)

How to reproduce
Just run the following code
const { HiNetHichannel } = require("hinet-hichannel-taiwan-radio");

const hichannel = new HiNetHichannel('ASIAFM 亞洲電台');

hichannel.loadApi().then(() => { //加載 HiNet hichannel API
  hichannel.playUrl().then(playUrl => {
      console.log(playUrl); //HiNet hichannel m3u8 串流網址 (string)
  }).catch(e => {
      console.error(e);
  });
}).catch(e => {
  console.error(e);
});

Remark
Thank you for your project, your project really helps me a lot for recording radio programs!

New version released!


Plugin removed from store?

as the title says the plugin seems to have been removed/disabled from the Shopware store. Is this because of missing 6.5 support? or by accident? the v5 is still there though.
https://store.shopware.com/adyen70424242359f/adyen-payments-fuer-shopware-6.html
results in an extension disabled error.

it is available in the store again.


Update grunt-sass dep to ^1.1.0

v0.14.0 does not work because it has node-sass v0.9.0 as a dependency which does not install correctly with current node and npm versions. I just tested this with the current grunt-sass version and it works perfectly.

@kahlil, thank you. This is part of v0.5.8.


Sync?

Trying to confirm. Will this sync an ICS calendar with discord on a schedule? or is it just a one-time push?

Good question - I just added an FAQ to the README. TL;DR one-time push.


Return constraint violations for plotting

In traj opt, collect all the constraint functions and evaluate them at the solution for plotting. Even better, add a callback function to evaluate them at each iteration.

Made a simple way to evaluate the constraints at the solution at arbitrary times using the interpolated state and input, but it has some non-negligible overhead (~5ms for 1 phase and 20 knot points on HURON). It should probably be reserved for debugging.
Callback functions which evaluate the constraints at each iteration are probably unnecessary for two reasons:

We will be doing MPC, so we are only evaluating a single iteration anyways.
gnuplot does not seem to support trivial dynamic plotting.


Edits: consistency and clarity

Added some points of clarification and sub headings for easier skimming

Things get weird after 9pm. I think things should pass CI now 🐎


created discount area on details page

What
Adding the capabilities for adding discount on draft order details page
Why
Currently users can only add discounts when creating the draft order initially, not once actually created.
How
Reusing the code for a new draft order.
Testing
User testing

Closed #325


Migrate to stageless Schedule v3 module

Huge thanks to @maniwani, @devil-ira, @hymm, @cart, @superdump and @jakobhellermann for the help with this PR.
Objective

Followup #6587.
Minimal integration for the Stageless Scheduling RFC: https://github.com/bevyengine/rfcs/pull/45

Solution

[x]  Remove old scheduling module
[x] Migrate new methods to no longer use extension methods
[x] Fix compiler errors
[x] Fix benchmarks
[x] Fix examples
[x] Fix docs
[ ] Fix tests
[ ] Verify that no new bugs were introduced (hopefully)

Changelog
Added

a large number of methods on App to work with schedules ergonomically
the CoreSchedule enum
App::add_extract_system via the RenderingAppExtension trait extension method
the private prepare_view_uniforms system now has a public system set for scheduling purposes, called ViewSet::PrepareUniforms

Removed

stages, and all code that mentions stages
states have been dramatically simplified, and no longer use a stack
RunCriteriaLabel
AsSystemLabel trait
on_hierarchy_reports_enabled run criteria (now just uses an ad hoc resource checking run condition)
systems in RenderSet/Stage::Extract no longer warn when they do not read data from the main world
RunCriteriaLabel
transform_propagate_system_set: this was a nonstandard pattern that didn't actually provide enough control. The systems are already pub: the docs have been updated to ensure that the third-party usage is clear.

Changed

System::default_labels is now System::default_system_sets.
App::add_default_labels is now App::add_default_sets
CoreStage and StartupStage enums are now CoreSet and StartupSet
App::add_system_set was renamed to App::add_systems
The StartupSchedule label is now defined as part of the CoreSchedules enum
.label(SystemLabel) is now referred to as .in_set(SystemSet)
SystemLabel trait was replaced by SystemSet
SystemTypeIdLabel<T> was replaced by SystemSetType<T>
The ReportHierarchyIssue resource now has a public constructor (new), and implements PartialEq
Fixed time steps now use a schedule (CoreSchedule::FixedTimeStep) rather than a run criteria.
Adding rendering extraction systems now panics rather than silently failing if no subapp with the RenderApp label is found.
the calculate_bounds system, with the CalculateBounds label, is now in CoreSet::Update, rather than in CoreSet::PostUpdate before commands are applied.
SceneSpawnerSystem now runs under CoreSet::Update, rather than CoreStage::PreUpdate.at_end().
bevy_pbr::add_clusters is no longer an exclusive system
the top level bevy_ecs::schedule module was replaced with bevy_ecs::scheduling
tick_global_task_pools_on_main_thread is no longer run as an exclusive system. Instead, it has been replaced by tick_global_task_pools, which uses a NonSend resource to force running on the main thread.

Migration Guide

Calls to .label(MyLabel) should be replaced with .in_set(MySet)
Stages have been removed. Replace these with system sets, and then add command flushes using the apply_system_buffers exclusive system where needed.
The CoreStage, StartupStage, RenderStageandAssetStage enums have been replaced withCoreSet, StartupSet, RenderSet and AssetSet. The same scheduling guarantees have been preserved.

Systems are no longer added to CoreSet::Update by default. Add systems manually if this behavior is needed, although you should consider adding your game logic systems to CoreSchedule::FixedTimestep instead for more reliable framerate-independent behavior.
Similarly, startup systems are no longer part of StartupSet::Startup by default. In most cases, this won't matter to you.
For example, add_system_to_stage(CoreStage::PostUpdate, my_system) should be replaced with
add_system(my_system.in_set(CoreSet::PostUpdate)

When testing systems or otherwise running them in a headless fashion, simply construct and run a schedule using Schedule::new() and World::run_schedule rather than constructing stages
Run criteria have been renamed to run conditions. These can now be combined with each other and with states.
Looping run criteria and state stacks have been removed. Use an exclusive system that runs a schedule if you need this level of control over system control flow.
For app-level control flow over which schedules get run when (such as for rollback networking), create your own schedule and insert it under the CoreSchedule::Outer label.
Fixed timesteps are now evaluated in a schedule, rather than controlled via run criteria. The run_fixed_timestep system runs this schedule between CoreSet::First and CoreSet::PreUpdate by default.
Command flush points introduced by AssetStage have been removed. If you were relying on these, add them back manually.
Adding extract systems is now typically done directly on the main app. Make sure the RenderingAppExtension trait is in scope, then call app.add_extract_system(my_system).
the calculate_bounds system, with the CalculateBounds label, is now in CoreSet::Update, rather than in CoreSet::PostUpdate before commands are applied. You may need to order your movement systems to occur before this system in order to avoid system order ambiguities in culling behavior.
the RenderLabel AppLabel was renamed to RenderApp for clarity
App::add_state now takes 0 arguments: the starting state is set based on the Default impl.
Instead of creating SystemSet containers for systems that run in stages, simply use .on_enter::<State::Variant>() or its on_exit or on_update siblings.
SystemLabel derives should be replaced with SystemSet. You will also need to add the Debug, PartialEq, Eq, and Hash traits to satisfy the new trait bounds.
with_run_criteria has been renamed to run_if. Run criteria have been renamed to run conditions for clarity, and should now simply return a bool.
States have been dramatically simplified: there is no longer a "state stack". To queue a transition to the next state, call NextState::set

TODO

[x] remove dead methods on App and World
[x] add App::add_system_to_schedule and App::add_systems_to_schedule
[x] avoid adding the default system set at inappropriate times
[x] remove any accidental cycles in the default plugins schedule
[x] migrate benchmarks
[x] expose explicit labels for the built-in command flush points
[x] migrate engine code
[x] remove all mentions of stages from the docs
[x] verify docs for States
[x] fix uses of exclusive systems that use .end / .at_start / .before_commands
[x] migrate RenderStage and AssetStage
[x] migrate examples
[x] ensure that transform propagation is exported in a sufficiently public way (the systems are already pub)
[x] ensure that on_enter schedules are run at least once before the main app
[ ] resolve all internal ambiguities
[ ] re-enable opt-in to execution order ambiguities
[ ] test all examples

[x] unbreak directional lights
[ ] unbreak shadows (see 3d_scene, 3d_shape, lighting, transparaency_3d examples)
[ ] game menu example shows loading screen and menu simultaneously
[ ] display settings menu is a blank screen
[ ] without_winit example panics

[ ] ensure all tests pass

[ ] SubApp doc test fails
[x] runs_spawn_local tasks fails

[ ] polished FixedTime API to match Time

Points of Difficulty and Controversy
Reviewers, please give feedback on these and look closely

[ ] default sets, from the RFC, have been removed. These added a tremendous amount of implicit complexity and result in hard to debug scheduling errors.
[ ] The outer schedule controls which schedule is run when App::update is called.
[ ] I implemented Label for Box` for our label types. This enables us to store schedule labels in concrete form, and then later run them. I ran into the same set of problems when working with one-shot systems. We've previously investigated this pattern in depth, and it does not appear to lead to extra indirection with nested boxes.
[ ] SubApp::update simply runs the default schedule once. This sucks, but this whole API is incomplete and this was the minimal changeset.
[ ] time_system and tick_global_task_pools_on_main_thread no longer use exclusive systems to attempt to force scheduling order
[ ] Details of the exact strategy used with fixed timesteps
[ ] AssetStage was migrated to AssetSet without reintroducing command flush points. These did not appear to be used, and it's nice to remove these bottlenecks.
[ ] migration of bevy_render/lib.rs and pipelined rendering. The logic here is unusually tricky, as we have complex scheduling requirements.
[ ] migration of  `prepare_lights system: this may need an extra command flush to keep working

Future Work (ideally before 0.10)

Add a derive macro to states, and likely a EnumIter trait of some form
Figure out what exactly to do with the "systems added should basically work by default" problem
Improve ergonomics for working with fixed timesteps and states

[ ] add IterableEnum macro and trait (different PR please)
one question about it: does that mean you want a derive macro which generates a iterator over an enum where fields don't have any types?
Like

#[derive(IterableEnum)]
enum Alphabet {
   A,
   B,
   C,
}

let mut iter = Alphabet::enum_iter();
assert_eq!(iter.next(), Some(Alphabet::A));
assert_eq!(iter.next(), Some(Alphabet::B));
assert_eq!(iter.next(), Some(Alphabet::C));
assert_eq!(iter.next(), None);

or do i get it wrong? just asking out of interest 😅

one question about it: does that mean you want a derive macro which generates a iterator over an enum where fields don't have any types?

Yes, precisely. See https://github.com/Leafwing-Studios/Emergence/blob/main/emergence_macros/src/iterable_enum.rs for example, although strum has one too.

Okay, this is compiling! Nowhere near ready to merge, but it's ready for others to start playing with it and catching bugs and dumb migration mistakes that I've made.

Threw together some quick example fixes here: https://github.com/alice-i-cecile/bevy/pull/99
If its stepping on your toes / messes with changes you're currently making, feel free to ignore. Only merge if its helpful.

There's currently a bug where the render worlds exclusive systems run on the main thread instead of the render thread.

I'll think about this and try to submit a fix for it.

Test systems::test::panic_when_hierarchy_cycle is not stopping for the last 3 days - https://github.com/bevyengine/bevy/actions/workflows/ci.yml?query=branch%3Astage-yeet

Test systems::test::panic_when_hierarchy_cycle from bevy_transform is not stopping for the last 3 days - https://github.com/bevyengine/bevy/actions/workflows/ci.yml?query=branch%3Astage-yeet

Yep, this will be fixed in #7448, which should be merged first.

(We need to fix docs first ... doing that now)

bors r+

Blocked on https://github.com/KyleMayes/clang-sys/issues/154

bors r+

bors try

bors r+

Spotted a small mistake in the migration guide:

Instead of creating SystemSet containers for systems that run in stages states, simply use .on_enter::<State::Variant>() or its on_exit or on_update siblings.

I believe this is only true for on_update. "on enter" or "on exit" systems are added using App::add_system_to_schedule.


Oded/per 4980 replace winston with pino for nextjs1

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

All tests are passed in the branch.


Issue152 blockindexing

This should address issue #152 concerning the incorrect blockindexing when the blocksize changes due to machine memory constraints. https://github.com/wadpac/GGIR/issues/152

Codecov Report

Merging #154 into WhitehallProcessingDec2018 will decrease coverage by 0.58%.
The diff coverage is 22.54%.

@@                      Coverage Diff                       @@
##           WhitehallProcessingDec2018     #154      +/-   ##
==============================================================
- Coverage                       63.64%   63.06%   -0.59%
==============================================================
  Files                              56       56
  Lines                            7235     7269      +34
==============================================================
- Hits                             4605     4584      -21
- Misses                           2630     2685      +55

Impacted Files
Coverage Δ

R/g.cwaread.R
0% <ø> (ø)
:arrow_up:

R/g.report.part4.R
91.66% <ø> (-0.09%)
:arrow_down:

R/g.getmeta.R
65.84% <100%> (+0.11%)
:arrow_up:

R/g.calibrate.R
76.43% <100%> (+0.2%)
:arrow_up:

R/g.readaccfile.R
15.18% <16.12%> (-0.57%)
:arrow_down:

R/g.part4.R
55.11% <50%> (-0.02%)
:arrow_down:

src/numUnpack.cpp
4.54% <0%> (+0.19%)
:arrow_up:

src/resample.cpp
7.69% <0%> (+0.54%)
:arrow_up:

Continue to review full report at Codecov.

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

The disadvantage of the current approach is that it automatically reduces memory usage when more than 4GB is used even when  much more than that is available, I am now looking into how we can do this more cleverly.

I have made some important enhancemets to this today:

I have added function updateBlocksize which updates the blocksize value depending on available memory. So, now the blocksize is increased if there is a lot of memory and reduced if there is too little memory.
I have added supporting documentation and a test.
I fixed a bug in the pageindexing for the Actigraph CSV format, where 10 rows were skipped after after block. Therefore, I also had to update the test values.
I intentionally avoided using function updateBlocksize in g.calibrate because in this function because we want it to always reads the same part of the file for reproducibility.


No license for bsphere/le_go library

Description

There appears to be no license for the logentries log driver vendored as github.com/bsphere/le_go.  I filed a github issue upstream but have not received a reply yet.
Technically this means you can't distribute this code with Docker, but if upstream responds I'm sure they will assign it a BSD or Apache license and everything will be OK.
Steps to reproduce the issue:
n/a
Describe the results you received:
n/a
Describe the results you expected:
n/a
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
n/a
Output of docker info:
n/a
Additional environment details (AWS, VirtualBox, physical, etc.):
n/a

Thanks for the report.
A license is now added in https://github.com/bsphere/le_go/commit/7a984a84b5492ae539b79b62fb4a10afc63c7bcf


Hide/unhide toggle to blanks out chart

When trying to hide/unhide lines, the rendering fails and the chart blanks out
The data has very large and small numbers, is something running out of range?
http://jsfiddle.net/swwg3ceh/
I also tried to add the following in data, which also blanks out the chart
hide: ['M0', 'area',],
Nice library! thanks

It seems like c3js does not like column names to have numerals in it 'M0'


django-stubs: Improve typing with more assertions

This is a part of #18777.

This is great, merged, thanks @PIG208!


GPU implementation

Hello,
Is there GPU implementation for this algorithm? if NOT will be any plan in future to support GPU?
Thanks in advance

No plan for GPU implementation. As you mentioned this, highly recommend the deep learning method to solve the face detection problem.


write frontend part using rust

For now, this is not a top priority. For now, the Python version will do.


Cosmetic rules don't work into iframes with desktop programs

Cosmetic rules don't work into iframes with desktop programs.
For example in iframes where user marked ads in this issue:
https://github.com/AdguardTeam/AdguardFilters/issues/66827
AG for Mac version: <IP_ADDRESS>3 nightly (CL-1.7.134)

@sfionov a bug?

@ameshkov No, CoreLibs limitation. More tricky blocking method should be used

@sfionov is it ok that HTML-rules and scriptlets don't work there too?


net/siproxd: fixed model and save buttons

@fichtner can you help me with the save buttons?

It's not in the middle, I'm not sure why:

It's working with the save buttons, but I left formid as general, is this ok?

able to merge now :)

As always: thanks!


failed to load translations (deploy vercel)

It works on my local machine, but fails when deploying to vercel with the following error:
[15:29:42.597] Cloning completed: 640.336ms [15:29:43.045] Restored build cache [15:29:43.102] Running "vercel build" [15:29:43.756] Vercel CLI 28.10.0 [15:29:44.520] Error: add site dependencies: load resources: loading translations: "/vercel/path0/themes/etch/i18n/en.toml:1:1": failed to load translations: unable to parse translation #0 because invalid plural category title [15:29:44.520] map[id:posts translation:map[date:map[other:Jan 2, 2006] title:map[other:Posts]]] [15:29:44.535] Error: Command "hugo -D --gc" exited with 255
My hugo version is:
hugo v0.109.0-47b12b83e636224e5e601813ff3e6790c191e371+extended linux/amd64 BuildDate=2022-12-23T10:38:11Z VendorInfo=snap:0.109.0

Per https://github.com/CaiJimmy/hugo-theme-stack/discussions/413#discussioncomment-3271397, it seems likely that this error is because the version of Hugo that Vercel is using is too old. Is the Hugo version you posted the version you have locally, or the version on the Vercel machine?
Can you try updating the Hugo version to 109 by following https://github.com/vercel/vercel/discussions/5834#discussioncomment-2547277

Yeah, that's worked!
Thanks to answer so quickly.
Happy Holidays!


Naming convention bug?

I have two stages "2 - Implementation" and "2 - Implementation - NBI" … each is used in a separate workflow.  However, my workflow using 2 - Implementation has picked up the 2 - Implementation - NBI stage somehow and will not let me select the intended 2 - Implementation stage.  This is a bug

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

ID: e5410984-75f1-cd6c-353b-f6d8c7457715
Version Independent ID: 8819df4b-1fb4-a8b4-2a15-acac18f114aa
Content: Best practices for creating phases and stages
Content Source: ProjectOnline/best-practices-for-creating-phases-and-stages.md
Service: project-online
GitHub Login: @efrene
Microsoft Alias: efrene

@wobailey  - thank you for submitting feedback.
Thanks for finding this potential bug. Thank you for your efforts. Support will be able to handle this case and escalate it to resolution. I want to make sure this gets resolved and the issues in GitHub are for the documents.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.


Pricing

The information about the pricing, for the users/groups connected aren't clear or missing.
DevOps has a payment structure per users, if I connect my AD with existing users (1000 example), I will pay the fees for the users into DevOps, or not ?

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

ID: 031380a0-4f04-4105-199a-81715b42c653
Version Independent ID: 570b2795-90ad-32b4-7ad0-1fceb186ffa3
Content: Connect organization to Azure Active Directory - Azure DevOps Services
Content Source: docs/organizations/accounts/connect-organization-to-azure-ad.md
Product: devops
Technology: devops-accounts
GitHub Login: @chcomley
Microsoft Alias: chcomley

Hi @kallsu, Thanks for reaching out for clarification. You will only pay for the users you invite to collaborate in Azure DevOps and if you assign them a Basic license. Thanks and have a great day!


Adjust cannonball rates

Currently the rates for cannonballs are way off, this pr adjusts the rates to match in game. With access to shilo village furnace and double ammo mould, this gives 5.3k cannonballs an hour the current rates are around 7.9k an hour. https://www.youtube.com/watch?v=GIfinzK4wYE

[x] I have tested all my changes thoroughly.

I think it's better to move cballs to smelting same as ingame. I assume that's one of the reasons it's inaccurate atm.


Safer transformation of NSURLFromNSString

e.g. this will handle white spaces in string (convert to %20) instead of returning a nil object.

will merge for next fix release this month


I need to embed the editor to a nestedscrollview,but it has initialize a scrollcontroller already, so it don't work

because I have some other fields in a page, I try to wrap them in a nestedscrollview,if set the scrollable to false,the editor bring cursor to view was not work,

It's possible to disable scroll behavior on the editor. Have you tried this?

Closed, since no feedback was provided.


Google Outbound connector

Please update the doc matching with the blog: https://chanikaruchini-16.medium.com/wso2-identity-server-integration-with-google-for-outbound-provisioning-a95954f15cad

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


chore: filter ux adjustments

Implements the following changes:

Ensure all spaces between filter groups = 16px
Ensure all spaces between filter label and filter values = 8px
reduce radio buttons and checkboxes to have size 14x14px
space between radio buttons and checkboxes = 4px
Modify question mark icon size from 16x16 to 14x14
Reduce spacing between tooltip icon and label to 6px

@Chriscbr Good callout - the default spacing on the Radio elements was 8px instead of 4. Also noticed in your screenshot that the radio's checked state was misaligned on chrome so I snuck in a fix for that as well


Unable use EF tools after updating Visual Studio to 16.4 (.Net Core 3.0 > 3.1)

I am unable trying to run any EF tools CLI commands after updating Visual Studio and .NET Core versions, receiving the following error each time:
The specified task executable "dotnet" could not be run. System.ComponentModel.Win32Exception (193): The specified executable is not a valid application for this OS platform. [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
This is after updating .NET Core Tools and using Version 3.1
I am able to compile and publish projects targeting 3.0 and 3.1 in both development and production without issue, it only seems that EF builds have issue.
Everything is fine using EF 3.0 and .NET Core 3.0, however as soon as Visual Studio and tools are updated no EF Tools commands function, despite working on 3.0 with the exact same code.

Steps to reproduce
What steps can we follow to reproduce the issue?
Have existing .NET Core 3.0 project with EF Core 3.0
Install Visual Studio 2019 Update 16.4.2
Update EF Core Tools
Attempt to run any EF Tools command e.g. dotnet ef migrations add test
PM> dotnet ef migrations add test -v
Using project 'C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj'.
Using startup project 'C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj'.
Writing 'C:\_Development\Projects\CoreTaskEngine\obj\TaskEngine.csproj.EntityFrameworkCore.targets'...
dotnet msbuild /target:GetEFProjectMetadata /property:EFProjectMetadataFile=C:\Users\ME\AppData\Local\Temp\tmpF435.tmp /verbosity:quiet /nologo C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj
Writing 'C:\_Development\Projects\CoreTaskEngine\obj\TaskEngine.csproj.EntityFrameworkCore.targets'...
dotnet msbuild /target:GetEFProjectMetadata /property:EFProjectMetadataFile=C:\Users\ME\AppData\Local\Temp\tmpFA12.tmp /verbosity:quiet /nologo C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj
Build started...
dotnet build C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj /verbosity:quiet /nologo
  wwwroot/js/core/datatables/datatables.js was not found
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003: The specified task executable "dotnet" could not be run. System.ComponentModel.Win32Exception (193): The specified executable is not a valid application for this OS platform. [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at System.Diagnostics.Process.Start() [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands) [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at Microsoft.AspNetCore.Razor.Tasks.DotNetToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands) [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.Execute() [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]

Build FAILED.

C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003: The specified task executable "dotnet" could not be run. System.ComponentModel.Win32Exception (193): The specified executable is not a valid application for this OS platform. [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at System.Diagnostics.Process.Start() [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands) [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at Microsoft.AspNetCore.Razor.Tasks.DotNetToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands) [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
C:\Program Files\dotnet\sdk\3.1.100\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.CodeGeneration.targets(99,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.Execute() [C:\_Development\Projects\CoreTaskEngine\TaskEngine.csproj]
    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:04.01
Microsoft.EntityFrameworkCore.Tools.CommandException: Build failed.
   at Microsoft.EntityFrameworkCore.Tools.Project.Build()
   at Microsoft.EntityFrameworkCore.Tools.RootCommand.Execute()
   at Microsoft.EntityFrameworkCore.Tools.Commands.CommandBase.<>c__DisplayClass0_0.<Configure>b__0()
   at Microsoft.DotNet.Cli.CommandLine.CommandLineApplication.Execute(String[] args)
   at Microsoft.EntityFrameworkCore.Tools.Program.Main(String[] args)
Build failed.

Further technical details
EF Core version: 3.1
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: .Net Core 3.1
Operating system: Windows Server 2016
IDE: Visual Studio 2019 16.4.2

@Stephen-Gibson Have you [installed as a global tool}(https://docs.microsoft.com/en-us/ef/core/what-is-new/ef-core-3.0/breaking-changes#the-ef-core-command-line-tool-dotnet-ef-is-no-longer-part-of-the-net-core-sdk)? This is new for EF Core 3.

@ajcvickers Hi, yes I've got tools installed:
PM> dotnet tool list -g
Package Id      Version      Commands
--------------------------------------
dotnet-ef       3.1.0        dotnet-ef
PM>

Have been using the global successfuly with 3.0 EF Tools on projects using 3.0 SDK,

I'm experiencing the same issue. As a workout, I'm using ef tools 3.0.0 and I'm able to run my project.

@Stephen-Gibson @axelmaldonado We think this may due to using a 32-bit installation on a 64-bit system. Can you do a where donet on the command line to see where it is being pulled from?
Also, try installing the 64-bit SDK if you haven't already done so.

@ajcvickers it looks like thi was indeed the problem - somehow a 0kb dotnet file (with no extenstion) was located at C:\Windows\System32\dotnet. Possibly an issue with the visual studio update process?
I deleted this file and tried to run the build again, and it worked correctly. Thanks for your help!
@axelmaldonado might be worth checking to see if this solution works for yourself.

Interestingly enough, this only took effect after the update to 3.1 - I checked and the file was still present in backup from the previous version, however it seemed that EF Build Tools ignored it in 3.0.


johndanz/ch10030/add-legal-disclaimer-to-ui

Clubhouse Story
This is not the final text
Submitter checklist

[ ] Test covering functionality added/fixed in
Check the linked story includes the following:

[ ] Steps to reproduce
[ ] Screenshot (If applicable)

Reviewer Checklist

[ ] Test/lint pass

This needs some style adjustments, stand by.

Nvm go ahead and pull this in, since it's urgent.


Error to install credentials in docker image

I've just pulled jenkins from the docker official repository. After trying to install suggested plugins, I'm getting this error

Steps I did
I run the following command:
docker run -p 8080:8080 -p 50000:50000 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts-jdk11

After I've got many errors in installation, I've tried to install them (plugins) manually and I got the errors above.
I'm using fedora 38

Being tracked at https://issues.jenkins.io/browse/INFRA-3067


Homebridge-hue does not start if one light of a resourcelink is not reachable

Hi,
I'm running deConz v2.5.25 (v2.5.27 is not yet available on the ubuntu /beta repository) and homebridge-hue v0.9.3.
If one of the lights belonging to a resourcelink is not reachable (turned off from an electrical point of view) when deconz starts, then homebridge-hue won't start and complains as the attached log. As soon as the light is reachable again, everything works fine.
Note that while homebridge-hue is waiting for the gateway to initialise, this latter is working.
[2018-5-23 20:59:57] [Hue] conBee: /resourcelinks/6: /lights/42: not available
[2018-5-23 20:59:57] [Hue] conBee: gateway not yet initialised - wait 1 minute

This is by design.  The alternative would be that homebridge-hue starts without exposing the light, so it would be removed from HomeKit.

While I understand the design choice from a homebridge-hue perspective, could you advice on a config strategy to minimize issues like this? For example, I have a whitelist setup as it's the easiest approach for me with a couple of multi-light 'lights', and some sensors bound to Phoscon created rules.
But, since the deconz rest api seems to be very aggressive in making devices no longer available, I run into this issue more than I would like. For example, a light was physically turned off by someone (the horror!), but all I know is the number, so I have to check all lights to see which one is the culprit. Not funny with over 40 lights.
But it gets worse, as I now have a 'missing' sensor. It's number 15, and I don't know which one it is.
So I guess what I am looking for is the deconz flag to keep a device visible until I hard delete it, with the appropriate availability flag set.

Historically, deCONZ handles sensors differently than lights.  Sensor resources are restored from the database on startup and marked reachable when the corrsponding node is discovered.  Lights are only restored after the node has been discovered.

a light was physically turned off by someone (the horror!)

Send these barbarians back to the 20th century!

but all I know is the number

That’s the onky info info available to homebridge-hue through the REST API (in the resourcelink).  Either renumber the lights, so the number makes sense (it helps when, like me,  you’re still recovering from OCD), or make a list (they’re managing companies in Excel, so why not a simple home; a simple ph get -al /lights | grep /name: will give you the info you need, once all lights have been found).  Without these, you’re best option is to look in the database.

I now have a 'missing' sensor

As far as I know, than can happen only when the sensor resource has ben deleted, through the REST API.  Again, best check the database - the record should still be there, with status “deleted”.

Every time I have tried to remove a light (or in this case an ikea outlet) I get the problem:
phoscon homebridge[20819]: [2019-12-11 20:30:04] [Hue] Phoscon-GW: /resourcelinks/9: /lights/4: not available
phoscon homebridge[20819]: [2019-12-11 20:30:04] [Hue] Phoscon-GW: gateway not yet initialised - wait 1 minute
I have tried waiting but nothing happens.
Homebridge won't work and I have to restore to my backup sd-card. What can I do if I want to remove an outlet but not mess up my homebridge?

Running ph lightlist -v and ph outlet -v fixed the problem. Guess i have to do this everytime I want to remove a light or switch.


feat: App Bar Navigation component

This PR adds a Top level Navigation component.

Published as part of version 4.1.0 😄


To save model in HF format after supervised-fine-tune-qlora

Hello @yukang2017 , I used supervised-fine-tune-qlora.py and did get the checkpoints at path_to_saving_checkpoints. After this step, I tried to run - merge_lora_weights_and_save_hf_model.py on the last checkpoint as I did not get the final model files (pytorch_model.bin) in path_to_saving_checkpoints. Did I miss something or is this the correct way to save hf model?
!python3 merge_lora_weights_and_save_hf_model.py \ --base_model "meta-llama/Llama-2-13b-hf" \ --peft_model "../path_to_saving_checkpoints/checkpoint-6000" \ --context_size 8192 \ --save_path "../path_to_saving_merged_model"
I also tried to find zero_to_fp32.py, somehow I could not find this script in the code. Is it necessary to run this script OR just the merge_lora_weights_and_save_hf_model.py is sufficient?
After merge_lora_weights_and_save_hf_model.py, I tried inference as below, which seems to be referring some.txt in the answers so I am assuming my steps are okay, please do let me know if I have missed any important step here.
!python3 inference.py
--base_model "../path_to_saving_merged_model"
--question "some question"
--context_size 32768
--max_gen_len 512
--flash_attn True
--material "some.txt"
Thank you again!

@MyBruso hi, have a look at #123 and specifically to the workaround of grimulkan which should be the best option. Unfortunately as far as I know you will need to repeat the training.

Hello @gianlucamacri Thank you, I did check #123.  Is saving model using model.base_model.save_pretrained(training_args.output_dir) different than merge_lora_weights_and_save_hf_model.py? I did notice the difference; however I see pytorch_model.bin files are getting generated using merge_lora_weights_and_save_hf_model.py.  It is loading PEFT model and then saving it; however I am curious to know the reason you are suggesting to explicitly add model.base_model.save_pretrained() in supervised-fine-tune-qlora.py.

Hello @gianlucamacri Thank you for sharing #123. Is saving model using model.base_model.save_pretrained(training_args.output_dir) different than merge_lora_weights_and_save_hf_model.py? I did notice the difference; however I see pytorch_model.bin files are getting generated using merge_lora_weights_and_save_hf_model.py. It is loading PEFT model and then saving it; however I am curious to know the reason you are suggesting to explicitly add model.base_model.save_pretrained() in supervised-fine-tune-qlora.py.

Yeah the difference is in the fact that ’model.base_model.save_pretrained(training_args.output_dir)’ is saving the model weights as they are in the base model augmented with the Lora layer since it will only bypass the Lora model object-wrapper (that's the cause of the .base_model notation), since calling the save method on the model itself would only save the weights of the Lora adapters (which is what the trainer does under the hood). This will allow you to store the modified weights of the model as well as all the others but in an "unmerged structure". On the other hand using ’merge_lora_weights_and_save_hf_model.py’ you are required to provide also the trainable parameters that are not saved by the Lora adapters, i.e. normalization and embedding layers that in the basic configuration of the script are left trainable.
However note that the workaround I suggested in #123 was rather rudimental, indeed the solution of grimulkan is much more elegant and convenient as it works seamlessly with a variety of configurations (while mine worked just for the 8-bit quantization) and allows to save multiple usable checkpoints with a reduced memory footprint as it stores just the trainable parameters. So I would strongly suggest to use that solution 😄

Thank you @gianlucamacri for sharing these insights. I tried #123's approach to save trainable_params.bin on_train_end. After this I ran merge_lora_weights_and_save_hf_model.py to generate pytorch_model.bin files. Now this script is able to use the trainable_params. One of the observation is - with this model, inference quality is deteriorated. Do you think I should try the intermediate checkpoints to generate the final model? OR With no trainable_params.bin supplied, merge_lora_weights_and_save_hf_model.py skips the model.load_state_dict(torch.load(trainable_params, map_location=model.device), strict=False) and loads the model from path path_to_saving_checkpoints. Is it fine if I use this loaded model for inference?

So I assume you used grimulkan-like code on #123, but reporting it here may be helpful in finding any possible issues.
Regarding the first issue, what do you mean that the inference quality has deteriorated? Did you make sure to compare the performance on the same data? I ask this since you may usually expect performances to be worse on data that was unseen during the training process but on the same data (train or validation) the model should perform the same (or better based on authors choice to switch to full-attention rather than s2 attention for the inference) if the model weights are the same, which should happen with a correct merge. Another trivial check would be to make sure to use the correct base model and checkpoint folder.
Regarding the second point I would say that it may be useful to try a previous checkpoint only if you saved the trainable weights for it, which I assume is not the case based on what you wrote, otherwise it would make very little mathematical sense to use weights derived from different time steps.

Thank you @gianlucamacri for sharing these insights. I tried #123's approach to save trainable_params.bin on_train_end. After this I ran merge_lora_weights_and_save_hf_model.py to generate pytorch_model.bin files. Now this script is able to use the trainable_params. One of the observation is - with this model, inference quality is deteriorated. Do you think I should try the intermediate checkpoints to generate the final model? OR With no trainable_params.bin supplied, merge_lora_weights_and_save_hf_model.py skips the model.load_state_dict(torch.load(trainable_params, map_location=model.device), strict=False) and loads the model from path path_to_saving_checkpoints. Is it fine if I use this loaded model for inference?

So I assume you used grimulkan-like code on #123, but reporting it here may be helpful in finding any possible issues.
Regarding the first issue, what do you mean that the inference quality has deteriorated? Did you make sure to compare the performance on the same data? I ask this since you may usually expect performances to be worse on data that was unseen during the training process but on the same data (train or validation) the model should perform the same (or better based on authors' choice to switch to full-attention rather than s2 attention for the inference) if the model weights are the same, which should happen with a correct merge. Another trivial check would be to make sure to use the correct base model and checkpoint folder.
Regarding the second point, I would say that it may be useful to try a previous checkpoint only if you saved the trainable weights for it, which I assume is not the case based on what you wrote, otherwise it would make very little mathematical sense to use weights derived from different time steps.

yes, I did use #123 like approach and did save trainable_params on_save as well as on_train_end.
Here are my observations -
what do you mean that the inference quality has deteriorated? - I see with same training data and inference on selected samples (from training data), I used to get better output without using 'trainable_parameters.bin'  in merge_lora_weights_and_save_hf_model.py.  The output was in context with its supplied source while answering the question at inference time.
With 'trainable_parameters.bin'  passed to merge_lora_weights_and_save_hf_model.py, I see the same questions are missing the main details from the supplied context.
This is how I tried merging and inference -
!python3 merge_lora_weights_and_save_hf_model.py
--base_model "meta-llama/Llama-2-13b-hf"
--peft_model "path_to_saving_checkpoints"
--context_size 32768
--save_path "path_to_saving_merged_model"
answer = !python3 inference.py
--base_model "path_to_saving_merged_model"
--question "sample question"
--context_size 32768
--max_gen_len 8096 \ # I am trying various options here from 1024 ..
--flash_attn True
--material "some.txt"

My apologies for the late update.
I re-ran the training and this time I did get zero_to_fp32.py in the "path_to_saving_checkpoints/checkpoint-<>" folder.
So I followed the sequence given on ReadMe as below-

!python3 zero_to_fp32.py  -t path_to_saving_checkpoints/checkpoint-<>/global_step<>  .  pytorch_model.bin
This did create pytorch_model.bin file in the same checkpoint folder.

Then I used get_trainable_weights.py to get the trainable_params.bin -
!python3 get_trainable_weights.py --checkpoint_path path_to_saving_checkpoints/checkpoint-<> --trainable_params "embed,norm"
Query : Can I rely on the trainable_params.bin generated using this script or I need to use #123's approach only?

Finally I used merge_lora_weights_and_save_hf_model.py to merge the weights -

!python3 merge_lora_weights_and_save_hf_model.py \
        --base_model "meta-llama/Llama-2-13b-hf" \
        --peft_model "path_to_saving_checkpoints/checkpoint-<>" \
        --context_size 8192 \
        --save_path "path_to_saving_merged_model"

Query : Now can I assume my merging of weights (LORA and base model) is properly done?
Note : checkpoint-<> - This is the last checkpoint, exactly same as on_train_end. I updated save_steps to achieve it.


Add Linux/ARM64 support to Incubator-Heron

Hi Team,
I am interested in adding Linux/ARM64 support to incubator-heron and Linux/ARM64 jobs to the Travis-CI.
As mentioned in the .travis.yml file, bazel for x86_64 is installed via installer script. However, that
installer script is not available for the ARM64 platform. But according to the docs, we can certainly install bazel via “bazelisk” for ARM64 as well.
So, I think we can replace the bazel script with this ‘bazelisk’ utility in Travis, to make it work similarly for both the platforms.
But I have seen that the Travis-CI takes around 2 hrs 35 mins to build for the AMD64 architecture. To add Linux/ARM64 jobs to the Travis-CI, it will surely take equivalent or maybe a little more time to build for ARM64 platform on Travis-CI.
If you are interested in adding Linux/ARM64 jobs to the Travis-CI, I am happy to contribute.
Please share your opinion on this.

Sounds good~ Thanks!
Travis is the current CI but the plan is to move to Jenkins CI in Apache
infra. Is there a similar util in Jenkins?
On Mon, Jan 11, 2021 at 11:32 PM odidev<EMAIL_ADDRESS>wrote:

Hi Team,
I am interested in adding Linux/ARM64 support to incubator-heron and
Linux/ARM64 jobs to the Travis-CI.
As mentioned in the .travis.yml file, bazel for x86_64 is installed via
installer script. However, that
installer script is not available for the ARM64 platform. But according to
the docs
https://github.com/bazelbuild/bazel/blob/master/site/docs/install-ubuntu.md#installing-bazel-on-ubuntu,
we can certainly install bazel via “bazelisk” for ARM64 as well.
So, I think we can replace the bazel script with this ‘bazelisk’ utility
in Travis, to make it work similarly for both the platforms.
But I have seen that the Travis-CI takes around 2 hrs 35 mins to build for
the AMD64 architecture. To add Linux/ARM64 jobs to the Travis-CI, it will
surely take equivalent or maybe a little more time to build for ARM64
platform on Travis-CI.
If you are interested in adding Linux/ARM64 jobs to the Travis-CI, I am
happy to contribute.
Please share your opinion on this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-heron/issues/3662, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQPBH6YMOBXSRDCVSMNVPLSZP3JXANCNFSM4V6YY6MA
.

Sounds good~ Thanks!
Travis is the current CI but the plan is to move to Jenkins CI in Apache
infra. Is there a similar util in Jenkins?
On Mon, Jan 11, 2021 at 11:32 PM odidev<EMAIL_ADDRESS>wrote:

Hi Team,
I am interested in adding Linux/ARM64 support to incubator-heron and
Linux/ARM64 jobs to the Travis-CI.
As mentioned in the .travis.yml file, bazel for x86_64 is installed via
installer script. However, that
installer script is not available for the ARM64 platform. But according to
the docs
https://github.com/bazelbuild/bazel/blob/master/site/docs/install-ubuntu.md#installing-bazel-on-ubuntu,
we can certainly install bazel via “bazelisk” for ARM64 as well.
So, I think we can replace the bazel script with this ‘bazelisk’ utility
in Travis, to make it work similarly for both the platforms.
But I have seen that the Travis-CI takes around 2 hrs 35 mins to build for
the AMD64 architecture. To add Linux/ARM64 jobs to the Travis-CI, it will
surely take equivalent or maybe a little more time to build for ARM64
platform on Travis-CI.
If you are interested in adding Linux/ARM64 jobs to the Travis-CI, I am
happy to contribute.
Please share your opinion on this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-heron/issues/3662, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQPBH6YMOBXSRDCVSMNVPLSZP3JXANCNFSM4V6YY6MA
.


Dupe found with Quark

Recently found a dupe with Quark that works somewhat consistently. Using a pickarang on top of an infusion altar with any storage block (ex: chest) next to it by throwing the pickarang to that block will duplicate both the block and its contents. Testing it seems it doesn't work (or works less often) when the pickarang has efficiency.

explained here


bug in payment

[x] new payment creation not working

[x] edit not working

[x] user not able to create new payment by inputting amount manually - (without tick checkbox - pay full amuont)

[x] search using date not working

[x] while creating new payment, payment showing "NEW"

[x] remove normal search

[x] after creating new payment,we have to refresh each time to get updated data on listing page

[x]  in payment mode , credit option is not needed

[x] rename received full amount to pay full amount

[x] rename Amount received  to amount paid under unpaid invoices

[x] if we enabled the check box in previous payment creation , ,the checkbox remains same the same as on the new payment creation page

[x] pay in full option is needed

[x] confirmation message is not showing ,while input amount manually in payment made field

[x] we have to refresh the page to get data on listing page after creation of payment

[x] payment not mentioned in listing page and description page

[x] response message for delete

[x] remove sort option - purchase invoice number , last modified time

[x] rename name to vendor name & voucher number to payment#

[x] sort not working

[x] remove all filter except All

[x] keyboard overlapping the fields in advance search

[x] if no data is entered into the reference field during creation ,the reference field displays null

[x] advance search not working with - **payment , reference ,payment method , date range from to to , total range min to max

[x] remove  - credit option from payment method(advance search)

[x] if supplier has amount zero, then pass a message under unpaid invoice

[x]  if supplier has amount zero, then the checkbox shouldn't show

[x] rename supplier : vendor in payment listing page

issue closed


[core] Don't bail out early if docs:api fails

Instead of exiting early as soon as a single component crashes yarn docs:api we continue building and list the errors at the end. This ensures that we don't create a big git diff if a single file fails. Ideally I'd get rid of the rimraf to reduce the git noise to a minimum but cleaning up is not that trivial so I'm sticking with the crude approach.
Basically where yarn docs:api would remove the full directory when a single file changes it now only removes the files that failed. Hopefully that helps working with docs:api.
Also did some refactoring to new node APIs.

This ensures that we don't create a big git diff if a single file fails.

I have been there too 😆, solving this pain will be appreciated


Remove the "_OPT" path prefix for optional config

When configuring an Option[A], it is currently necessary for the configurer to add "_OPT" path prefix. There is no real reason for this other than the explicit everything philosophy.
Remove this requirement in favour of easier use.

Implemented, not yet merged


fix-get-endpoints-default-return-value

Codecov Report

Merging #243 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #243      +/-   ##
==========================================
- Coverage    59.2%   59.18%   -0.02%
==========================================
  Files          40       40
  Lines        3250     3251       +1
  Branches      390      390
==========================================
  Hits         1924     1924
- Misses       1220     1221       +1
  Partials      106      106

Impacted Files
Coverage Δ

vmpool/platforms.py
64.15% <100%> (+0.22%)
:arrow_up:

core/auth/custom_auth.py
65.21% <0%> (-2.18%)
:arrow_down:

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 32c6076...104b1f4. Read the comment docs.


initial commit of CloudFoundry Loggregator Spring Cloud Dataflow source

Provides a Cloud Foundry Loggregator Source.
I'm not entirely sure how to test this. I have environment variables on my machine,  CF_ORG, CF_SPACE, CF_USER, CF_PASSWORD, and CF_API that work in this test. Also, I happen to know that I have an application called configuration-service available.
I think the right approach is to make sure to download cf in Travis, then use it to cf push a new simple Spring Boot CLI application called foo-service. We can have that app do almost nothing, just print things to the log. As soon as a single log entry's received, the test is a success.
In my builds that use Travis and cf, the installation is as follows in the next script. ~/bin and ~/.m2/repositories could be cached through CI runs.
#!/bin/bash

CF_USER=$1
CF_PASSWORD=$2
CF_ORG=$3
CF_SPACE=$4

function install_cf(){
    mkdir -p $HOME/bin
    curl -v -L -o cf.tgz 'https://cli.run.pivotal.io/stable?release=linux64-binary&version=6.13.0&source=github-rel'
    tar zxpf cf.tgz
    mkdir -p $HOME/bin && mv cf $HOME/bin
}

function validate_cf(){

    cf  -v || install_cf

    export PATH=$PATH:$HOME/bin

    cf api https://api.run.pivotal.io
    cf auth $CF_USER $CF_PASSWORD
    cf target -o $CF_ORG -s $CF_SPACE
    cf apps
}

validate_cf

This source is useful because we can do smart things based on what our logs are telling us. I want to contribute an ElasticSearchSource and another that acts as a syslog:// drain. Structured logs are a thing and for many applications they serve as an event plane and structured data. Tools like Kibana make analyzing this stuff as though it were schema dead simple.

I would think the best approach for the tests would be to not run integration tests that require access to a separate service/server by default. Similar to the gpfdist sink app here - https://github.com/jvalkeal/spring-cloud-stream-modules/commit/928b8206126a539bdeeb4302845f5a0497edce44#diff-6bcafa72fc357aeb2e6a8ac20294c7a5R68

Would be helpful to provide a small test app that could be deployed to CF, maybe a Boot Groovy app so it doesn't have to be compiled

Hi there @trisberg I've added a simple it-test.sh script and a it-teardown.sh script and updated the PR for your consideration

Merged via commit 020cd08d1bd6a14ee9bbbd2723064fe8b414d703
Some polishing/changes via commit 31ab8137433401de9a66a0937acd73d5c16b0004


Help stale Open Source projects become active again by giving them democracy!

Just reviewed a couple of my PRs on various open source problems, most of which didn't get any comment/attention from the project maintainers. This made me think about Chaosbot again, and I think that many OS projects can really benefit from giving contributers some more influence over merging PRs/managing issues, etc.
We already had a nice thing going on, what if we try to move it towards a SaaS solution aimed at helping out OS projects on Github, maybe even publishing it at the GH marketplace if we're successful?
We'd need to have a good functional design first, and this project should then really aim at creating a finished/usable product instead of having more of a focus on being an experiment.
Just a thought... maybe with some combined development time we can actually make something useful!
@andrewda, @xyproto, @rhengles, @PlasmaPower, @eukaryote31, @rudehn, @MUCHZER, @mark-i-m, @phil-r, @hongaar, @md678685, @Smittyvb, @Swizz, @Redmega, @mpnordland

I think this was one of the original plans for ChaosBot v2. I think one of the reasons that v2 never materialised was that many people didn't feel the same way about the brand new, heavily-discussed piece of software compared to the chaotic experiment of the original ChaosBot, and so fewer people were interested in investing the time to work on building the new version from the ground up.
That's not to say I don't approve of the idea - I'm all for it, but I'm concerned that there won't be enough interest to make it sustainable, and it's unlikely to be the fun, attention-gathering experiment that the first ChaosBot was.

I think the v1 of ChaosBot was a success because all the core was here.
OSS contributors are sometimes afraid about making the thing from scratch. This is always more easy to make a PR to update one thing. Pretty hard to coordinate a thing from scratch.
Lot of the most famous OSS projects were at the start built from one man.

After some thought, my conclusion is that this would only work under a few conditions:

The project is very thoroughly tested, and tests are required before any merge: this forces good code quality. One of the reasons I think we (especially me :P) broke chaosbot so many times was that we did not strongly test most things. Personally, I would be unwilling to use any project in my codebase that breaks every few commits...

The owner is willing to let others determine the fate of the project. One way around this would be for you to fork the project and setup the chaosbot yourself. In fact, you can already fork the repo and improve it yourself. One question is how does chaosbot improve over this paradigm?

Users are honest. Checking for power grabs is hard and exhausting. And it only takes one malicious contributor to break lots of stuff. I don't know how to make chaosbot byzantine fault-tolerant without lots of voters/reviewers. One idea is to require an approved github review to vote for an issue (i.e. the only way to vote for something is to review changes) and keep the 👎 reaction on the PR for voting against.

There is enough interest in the project for a vote. I don't think this will solve the problem mentioned by @hongaar in the opening comment unless there are a lot of people that similarly want a given change enough to review and vote for it.

@md678685 I agree that it will be more difficult to find developers wanting to donate the time for a project with a more rigid goal. It won't attract much attention (at least not compared to the v1 experiment) but I don't agree that it can't be fun, we'll be working on something which could be used for many real-world projects.
@Swizz true point, and it will be challenging! Even better if we can show it can be done in a different way!
@mark-i-m respectively:

100% agreed. GitHub let you control this in a nice way already, by using merge checks on CI containing tests + code coverage analysis.
Collaboration. Forking and improving doesn't give back to everybody. Discovering notable forks on GH is a pan.
Something along those lines, combined with a meritocracy (which worked pretty well I think, maybe with more emphasis on recorded contributions to a project). Also, protected branches in GH could help? So i.e. only certain users can merge to the master branch.
Chicken and egg? As soon as contributors can have more direct influence, their involvement with the project might increase, the project evolves faster, and more users (and potential contributors) are attracted.

@hongarr At least from my perspective, it will be easier to attract developers because we would have a defined goal, which makes it easier to show people how they can help.  The easier it is for someone to contribute the more devs we'll have. I think this is a great idea.

@mpnordland I suppose you're right - I was thinking more short term, but having a clear goal would probably attract more long term contributors.

Something along those lines, combined with a meritocracy (which worked pretty well I think, maybe with more emphasis on recorded contributions to a project). Also, protected branches in GH could help? So i.e. only certain users can merge to the master branch.

I guess one thing I would change is that rather than making it a meritocracy, maybe contributors can be elected a "review commission" or something after they have contributed a PR (or some other minimal requirements)... We could also have the ability for an elected reviewer to step down. The idea would be to try to involve more people in the reviewing process and reduce burden on those who might have other time commitments...

I think that with Chaosbot we develop an interest system voting. But, I felt that it didn't have a goal. We have to make a list of goal for the future. What do you think?

I love these ideas and reviving Chaos, I've been so busy with work the past few weeks/months I've barely had time for the OSS repos I maintain, let alone this project. Hopefully things will change soon.

I personally think we should do something involving decentralization. Since the idea of chaos is to be self governing, the fact that it relies on a single cloud container is sort of a shame.

blockchain bot!

I made a Node.js version: Chaosthebot/chaos2. Right now, it only works when I run on on my computer, because it hasen't been put on the cloud server, and we need a OAuth token from @chaosbot.

I don't think the server is still around, so we'd need a new server to run the bot on.

I think any of us could get a free-tier AWS or Azure instance...
On Nov 6, 2017 1:54 AM, "md678685"<EMAIL_ADDRESS>wrote:
I don't think the server is still around, so we'd need a new server to run
the bot on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Chaosthebot/Chaos/issues/574#issuecomment-342071371,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIazwEOAlFM1uCCrR3p-99qIhN7uiXLvks5szrtFgaJpZM4QOa2N
.

And how about the OpenShift "free for open source" plan ?
https://www.openshift.com/grants/

I think we should make it decentralized, running it on a single cloud container makes it a lot more vulnerable.

Still, if we have to do it on cloud, I could run an f1-micro for it.

@chaosbot @amoffat Can you get an OAuth token for @chaosbot? Preferably, one with all permissions.

@Smittyvb I really like the idea of developing this in Node.js! 👏


remove 'dbpedia' directory from 'hefquin-base'

See https://github.com/LiUSemWeb/HeFQUIN/issues/356#issuecomment-2316901615 and the following comment.

I have moved this directory to hefquin-engine now because I moved the corresponding test class.


webpack does not support inlining CSS in HTML

Environment
Nuxt CLI v3.0.0-rc.6                                                                                02:18:49
RootDir: C:\projects\self\nuxt-webpack-css-loader-fail                                                                                02:18:54
Nuxt project info:                                                                                02:18:54

Operating System: Windows_NT
Node Version:     v14.17.1
Nuxt Version:     3.0.0-rc.6
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      builder, build, ssr, css, webpack
Runtime Modules:  -
Build Modules:    -

Reproduction
Minimal Reproduction from https://github.com/mannok/nuxt-webpack-css
Please see the commit log, expected the body will be applied background-color: darkcyan;, but Webpack cannot load the css so all styles in the page are broken.
Describe the bug
css cannot be loaded while using Nuxt3 with Webpack
Additional context
No response
Logs
No response

Let's track in https://github.com/nuxt/nuxt/issues/14777


Docker-compose up fails on first time

(user) got a problem when I run docker-compose -f docker-compose.yml up of skygear-server first time
p_1    | time="2016-09-26T04:17:23Z" level=error msg="Unable to begin transaction for schema migration: dial tcp <IP_ADDRESS>:5432: getsockopt: connection refused" logger=skydb
app_1    | time="2016-09-26T04:17:23Z" level=error msg="Failed to start skygear: failed to open connection: skydb/pq: unable to connect to database because of a network error = dial tcp <IP_ADDRESS>:5432: getsockopt: connection refused"

Skygear Server Date/Version: 0.17.1
Application Platform:
[x] Is this a regression?
[ ] Attached logs, screenshots

Expected Results
First run will work.
Actual Results
Second run will work.
Steps to reproduce

Checkout skygear-server
docker-compose -f docker-compose.yml up

This is not a regression.

There are a couple of solutions to this problem:

change the docker image so that skygear-server will restart on fails
introduce a delay before skygear-server is run
skygear-server wait for longer before giving up

pick one


Implement Disclosure Validation

https://github.com/rgb-org/rgb-core/blob/4e29b8082c0a69cc906fa8d4f604f2980dad17f5/src/stash/disclosure.rs#L360

Not applicable: no more disclosures in v0.12


Question: Way to get the full AppiumAUT XML tree?

Is there a way to get the full XML tree of the current AppiumAUT object?
Reason is that I'd like to paste the XML tree into an editor so I can play around with the XPath (in addition to what's already in the inspector in terms of the XPath Helper)
The XML is loaded anyway so there should be an easy way to get a handle to it, right?

Unfortunately, there is no such possibility in the current build, but I can add it if needed

that would be cool. I noticed that the raw XML gets stored in Inspector.prototype.onTreeLoaded on the Inspector object's xml property already so it could be grabbed from there.

@lambourn I have just added the "Copy XML To Clipboard" button and pushed the changes to master. Enjoy!

Sweet!


Update config file for local and HPC cluster execution

This PR introduces updates to the configuration file to enable local execution as well as compatibility with High-Performance Computing (HPC) clusters such as SGE and PBS. Tests has been conducted on SGE and PBS clusters.
Changes

Updated the configuration file to support local execution and HPC clusters (SGE and PBS);
Conducted tests on SGE and PBS clusters to ensure compatibility.

OBS: Users are required to specify the correct path to their Conda environment in the configuration file, within the specific profile for each cluster.
e.g. my conda environment on SGE: ~/.conda/envs/nextflow/
My config profile for SGE:
profiles {

    sge {
        process.executor              = 'sge'
        process.queue                 = 'all.q'
        process.clusterOptions        = '-S /bin/bash -pe smp 1 -cwd -V'
        process.conda                 = '~/.conda/envs/nextflow'

Thanks a lot, @felipevzps !


Add second timestamp to chat messages (and remove month in turn to limit...

... the length of the date prompt).
I'm often annoyed by the lack of seconds in the timestamps, especially when comparing shown messages with the XMPP debug log. On the other hand, I find the "month" display a bit pointless.
What do you think about merging this change?

again a piece which should be in the user configuration...


Tweaks to docs for 1.10

I am currently going through the notebooks to make sure they work correctly with 1.10. This PR makes a number of small fixes and tweaks.
One issue I found in the gridded data user guide:

Edit: Fixed in https://github.com/ioam/holoviews/pull/2545

I'm going to update this notebook to use the .opts method. That said, two examples aren't working:
This is isn't being linked:

The tap example isn't working either:

@jbednar I can't see a change moving this slider in the Large Data user guide:

I also don't quite get why matplotlib is being used here?

In the Streaming Data user guide, the call to clear seems to have no effect:

In the dashboards user guide I am seeing our favorite warning:

Everything seems to be working regardless except for the last example. Moving the slider generates these warnings:

You can't see it now, but in the "Installing and Configuring" user guide, running:

Sometimes shows a parameter warning about setting the state of AdjointLayout.show_frame.

The tabs don't seem to be working in the 'Plotting with Bokeh' user guide. Preliminary investigation suggests it might be a bokeh issue:

In Plotting with Bokeh, only the diagonal seems to update:

In the Plotting with Matplotlib user guide, I get an error rendering to mp4:

Now I'm going through the examples.  I'm getting some really weird behavior in box_draw_roi_editor.ipynb:
Initially it displays but box select doesn't do anything:

If you run it again:

In hex movie ratings:

In iris density grid (bokeh):

Note this is after rebasing with #2547.

The matplotlib measles example demo is broken:

In route_chord.ipynb there is a problem getting the airports dataset:

End of the traceback:

There is also a problem getting the matplotlib sample data for topographic_hillshading.ipynb (both bokeh and matplotlib versions):

Matplotlib heatmap isn't working in the us_unemployment.ipynb example:

I'm going to update this notebook to use the .opts method

Why .opts and not .options?

@jbednar I can't see a change moving this slider in the Large Data user guide:

Yes, I already reported that to @philippjfr, who said that he'd update something about bokeh indexes, I think?

I also don't quite get why matplotlib is being used here?

I used matplotlib just to match the previous much larger set of examples (where I didn't want to make the load time for the page huge) and so I wouldn't have to explain that the data would be dynamically updated if you have a live Python server.  But that's only a minor concern; feel free to change it to Bokeh if you prefer.

Important: It looks like upgrading to matplotlib 2.2.2 fixed a large number of unit tests running locally.

Should we pin matplotlib to >= 2.2.2?

Why .opts and not .options?

That would require more work and thought. The goal was just to quickly get rid of the deprecation warnings about using __call__ and get through testing all the example notebooks manually.
The good news is that .opts( is easy to grep so we can convert it to .options in a separate PR if we have time.

Should we pin matplotlib to >= 2.2.2?

I would rather we didn't have to but fixing things to be backwards compatible might be more effort than it is worth.

Yes, I already reported that to @philippjfr, who said that he'd update something about bokeh indexes, I think?

@jbednar As far as I can tell it's not a HoloViews bug but directly related to your example, not 100% sure though.

Should we pin matplotlib to >= 2.2.2?

I think matplotlib>=2.1 should be sufficient.

@philippjfr I see a number of errors in the sri_model.ipynb topic example.

@philippjfr I see a number of errors in the sri_model.ipynb topic example. e.g hitting play does nothing:

Worth checking the scrubber widget works elsewhere, I'll do that tomorrow morning.


Feature request: Provide kWh consumed through API

It might exceed the processing power of the ESP32, but would it be possible to provide a (calculated) value for "EV charged kWh" and "EV total kWh"?
In my setup (without a seperate kWh meter with modbus) these values now stay empty.

If you dont have a kWh meter that measures the power, how would SmartEVSE know how much power is charged?
The charging current that is shown is the MAXimum current the EV us allowed to draw, the EV can easily slow charging down or even stop it without letting the EVSE know.
That kind of info should be given by the EV, not the EVSE.

I think you might have a point there ;-)  I did not think about the fact the EVSE does not know the power actually used to charge. It is just aware of the status of MAINS instead which is the sum of all things connected and not just the EV.
Guess you can close this one :-)


Xcode 6.3

I know it was released out of the beta just yesterday, but I'm having some errors when opening with Swift 1.2 and Xcode 6.3. Some errors are easily fixed with the new as! syntax but some are not. Here are the two errors that I couldn't fix:
HTMLNode.swift:

Cannot assign to 'nodeType' in 'self'

MyViewController.swift (when I try to initialise var parser = HTMLParser(html: html, encoding: encoding, error: &err))

Cannot find an initializer for type 'HTMLParser' that accepts an argument list of type '(html: NSString!, encoding: UInt, error: inout NSError?)'
Overloads for 'HTMLParser' exist with these partially matching parameter lists: (html: String, encoding: UInt, error: inout NSError?)

Any ideas on what they might be or how to fix them?
Thanks,
Beno

Sorry, but the issue in the HTMLNode.swift was that somehow nodeType was a let and not a var. But I'm still getting the error when trying to init the HTMLParser.

Fixed the other error. I was passing an NSString as apparently thats not allowed anymore. Had to change it to a String. Sorry for the issue.


Add auto merge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/social-analyzer-feedstock#2.


feat: Add support for proxies in HttpConfig

This PR allows users to set a proxy URL without needing to use the deprecated VonageClient.Builder#httpClient method. This can instead be configured directly in HttpConfig without exposing details of the underlying HTTP client implementation.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.00%. Comparing base (fe06b81) to head (6f3b27f).
Report is 71 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #556      +/-   ##
============================================
+ Coverage     95.60%   96.00%   +0.39%
- Complexity     3427     3754     +327
============================================
  Files           513      564      +51
  Lines          8141     8704     +563
  Branches        451      497      +46
============================================
+ Hits           7783     8356     +573
+ Misses          198      175      -23
- Partials        160      173      +13

Files with missing lines
Coverage Δ

...rc/main/java/com/vonage/client/AbstractMethod.java
100.00% <100.00%> (+22.22%)
:arrow_up:

src/main/java/com/vonage/client/HttpConfig.java
93.93% <100.00%> (+21.59%)
:arrow_up:

src/main/java/com/vonage/client/HttpWrapper.java
100.00% <100.00%> (ø)

... and 32 files with indirect coverage changes


⚠ Bofrost.be has degraded performance

In 2e546d0, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2843 ms

Resolved: Bofrost.be performance has improved in 374187e after 6 minutes.


pj  causes (eval):1: parse error near `&'

❯ pj ......
(eval):1: parse error near `&'
(eval):1: parse error near `&'

Can you state more details for your configuration? installed plugins/dotfiles/os?
For me this error doesn't happen.

You probably have something wrong with your $PROJECT_PATHS variable because the pj completion function is really basic:
function _pj () {
    typeset -a projects
    projects=($PROJECT_PATHS/*)
    projects=$projects:t
    _arguments "*:file:($projects)"
}

Nevermind, I find the problem. This happens if there are directories or files under $PROJECT_PATHS containing &. A patch is on the way.

PR #5296 should fix this. Please test.

I've tested it and my issue is fixed. However we have lost the ability to go to the folder I set as $PROJECT_PATHS

That was a side effect of a bug when no project was specified. What should the behavior be if $PROJECT_PATHS has more than one directory? The bug made it go always to the first one, so it doesn't seem to be worth it having the old behavior. What do you think?

As far as I know there was never any intention of having that ability. The pj plugin is very limited in that sense.

Anyhow, I'm merging that. Thanks.


avEditorFinished event not catched

Hi,
I've just installed and tried your module in an app, and everything works fine to launch the editor with an image, edit the image, but when I click Apply, the avEditorFinished event is not catched by the app.
Here's what I'm doing:
function adobeEditor() {
	var photo_editor = require("com.kosso.tiadobecreativesdk");
	var tools = ["kAFOrientation", "kAFCrop", "kAFAdjust", "kAFSharpness", "kAFText", "kAFDraw"];
	var adobe_client_id = "xxxxx";
	var adobe_client_secret = "xxxxx";
	photo_editor.newImageEditor({apikey:adobe_client_id, secret:adobe_client_secret, image:$.imageView.toBlob(), tools:tools});
	photo_editor.addEventListener('avEditorFinished', function(e) {
		Ti.API.info('avEditorFinished event: '+e);
		Ti.API.info('avEditorFinished image: '+e.image);
        // Some other processing
        photo_editor = null;
	});
}

Forget that, sorry. Typo in the code.

I reopen this issue, because it seems that sometimes, the event is catched, and sometimes not.
After some tests, it seems that if I only do little edit (let's say just Saturation) then tap "Done", everything is fine, and the event is catched, but if I do several edits (Saturation, Text, Orientation, Crop) one after the other and then tap "Done", nothing happens, no event catched.
Is there other event than avEditorFinished that needs to be listened? An option to change?…

I'm experiencing same issue although for me it appears to be random, can't isolate what triggers it


Ignore types unrelated to the configuration in the summarize plugin

This fixes a segfault in the summarize transform step when its configuration caused all fields to be dropped from the table.
:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
Run this on our testbed and check that we encountered that same issue there. The unit test this adds crashes without the additional changes to the plugin and to libvast.

The second bugfix still needs a changelog entry, though.

Good point. I've added a second one.
Thanks for testing on the testbed @lava.


How to import 3rd party modules like firebase, etc and make use of the types.

Currently I am using ui5 project shims to add in the resources folder.
"ui5": {
"dependencies": [
"ui5-middleware-livereload",
"firebase"
]
},
"dependencies": {
"firebase": "^8.7.0"
}

specVersion: '2.1'
kind: extension
type: project-shim
metadata:
name: thirdparty # this can be your project shim name
shims:
configurations:
firebase: # name as defined in package.json
specVersion: '2.1'
type: module # Use module type
metadata:
name: firebase
resources:
configuration:
paths:
/resources/__firebase/: ''  # location where modules are stored
But not able to utilize the TS types as the import for them happens during runtime and design time have to refer to node_modules.
Any suggestions?

Addressed in https://github.com/SAP/openui5/issues/3297


Franz account not found after paying for a month.

Current Behavior
I created an account with the Franz application using my email. I then went to purchase the subscription for one month, where the charge went through for 4 EUR. I then opened the dev version of the application and tried to log in, only to receive an, "Account not found" warning, and when I recreated with the same email, I was able to but didn't retain the subscription I paid for.
Screenshots (if appropriate):

Steps to Reproduce (for bugs)

Create a free account in Beta app.
Upgrade to the 1-mo. subscription.
Download and install dev app.
Fail to log in with same credentials.
Create account with same credentials as before.

Your Environment

Franz Version used: Beta + Master
Operating System and version: MacOS High Sierra

The dev app and live app do not access the same API. If you want to run the dev version with the live API please start Franz with $ yarn start:live
I'll add a notice in the next beta to highlight this.


Remove Aspect Ratio

Hi there, just wondering if it is possible to remove the aspect ratio, so that when the page is resized, the height stays the same, but the width changes? Thanks heaps.

hi @trentgil24 have you found any solution for this issue ? thanks


DOC-2593 Remove service dependency from yaml examples

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Starts downloading OneDrive files on-demand

Issue Type: Bug
Out of nowhere VS Code started downloading my files from OneDrive. I have not even opened any file that is stored in OneDrive I just randomly received notification "Code started downloading files"... I don't want VS Code to download any files on-demand that I have not opened to work on. I am using VS Code for Mac OS.
VS Code version: Code 1.36.1 (2213894ea0415ee8c85c5eea0d0ff81ecc191529, 2019-07-08T22:56:38.504Z)
OS version: Darwin x64 18.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (0.12GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

xml
Dot
2.5.0

vs-code-xml-format
fab
0.1.5

php-intellisense
fel
2.3.10

gc-excelviewer
Gra
2.1.32

ftp-simple
hum
0.7.0

eml
lei
0.3.2

saml-extension
mca
0.0.8

powershell
ms-
2019.5.0

debugger-for-chrome
msj
4.11.6

vscode-react-native
msj
0.10.2

I can not reproduce this.
Please file with reproducable steps
Also can you reproduce with vscode insiders https://code.visualstudio.com/insiders/


[dev brunch] TilemapLayer rendering and collision detection are not consistent?

This Issue is about

A bug in the API

(dev brunch)
TilemapLayer render uses scroll(_scrollX,_scrollY) to determine tiles that need to be rendered, but TilemapLayer collision system uses tilemapLayer.position and does not take into account scroll. I try to use the following configuration:

tilemapLayer.fixedToCamera = false (so it is fixed in the "world")
tilemapLayer.position = (0,0) (and it is fixed\constant)
tilemapLayer.scrollFactorX = 1
tilemapLayer.scrollFactorY = 1

Now, when camera position changes (for example, when camera follows moving sprite), tile collision gets broken: character falls through the map or "stands" in the middle of tiles.
I tried every possible combination of described parameters(scrollFactor = 0, fixedToCamera = true, etc), but it gave wrong results. The best was:

tilemapLayer.fixedToCamera = false
tilemapLayer.scrollFactorX = 0
tilemapLayer.scrollFactorY = 0

But with these values rendering is broken: it renders only top left part of the tilemap (I think it is because scrollX,scrollY do not change so render method thinks there is nothing to rerender. But actually camera position changes!
What is a supposed way now to get a fixed in world tilemap with camera following character so that collisions work too?
In 2.4.7 version I used default configuration and it worked:

tilemapLayer.fixedToCamera = true (default)
tilemapLayer.position = (0,0) (and it is fixed\constant)
tilemapLayer.scrollFactorX = 1 (default)
tilemapLayer.scrollFactorY = 1 (default)

Dispite of fixedToCamera = true, tileLayer really was scrolling when camera moves because of scrollFactor, and tilemapLayer collision system did not use tileLayer.position. Now it uses tileLayer.position https://github.com/photonstorm/phaser/commit/4a3e8f2b4aaa6975e4b3ada8151785e29b3728b1 and maybe that is a cause of inconsistency?
Also maybe tilemapLayer rendered should use camera position (not scrollX,scollY) to determine renderable tiles?

This is almost certainly a result of the recent commits by @Upperfoot to try and get tilemaps rendering when 'stitched' together, rather than how they should be by default (i.e. fixedToCamera). I'll probably revert back to the original code today, and then reintroduce the changes bit by bit until I find out what's breaking it.

@SergeyFromHell Just doing some digging, can you post a demo at all? TilemapLayer.position is only used if it's off from default 0, 0 it doesn't replace what scrollX and scrollY does, it just incorporates it into the calculation for collision and in fixX and fixY only if it's the following.
Collision:
https://github.com/photonstorm/phaser/blob/dev/src/physics/arcade/TilemapCollision.js#L133
If the TilemapLayer.position is 0,0 it wouldn't affect that line, and it wouldn't affect any of the others that use TilemapLayer.position.
(number - 0 = number)
Render:
https://github.com/photonstorm/phaser/blob/dev/src/tilemap/TilemapLayer.js#L424-L433
Again ifor the TilemapLayer.position is off from standard then it isn't used.
Something else is going on I believe, perhaps I need to include the TilemapLayer.position in the calculation for fixX here https://github.com/photonstorm/phaser/blob/dev/src/tilemap/TilemapLayer.js#L435 and fixY here https://github.com/photonstorm/phaser/blob/dev/src/tilemap/TilemapLayer.js#L479
But you stated that your scrollFactorX and scrollFactorY where either 0 or 1 which means it would never have hit that line.
Thoughts?

The code in the repo, as it stands now, doesn't work in any of the Tilemap examples in the Phaser Examples repo either. It starts off fine, but as soon as it scrolls the collision is gone. So @SergeyFromHell is right, there's definitely something up, and I don't think it's fixedToCamera related, but something else. I'll have a dig into this as soon as I can, but to see it happening @Upperfoot just try out any of the Phaser examples like map collide or sci-fly.

@SergeyFromHell Can you try this out? https://github.com/photonstorm/phaser/pull/2546
Basically what was happening was that if fixedToCamera is set to true, it was changing the tilemapLayer position to follow the camera, which interacted with collision.
What I've done is added a conditional check to only incorporate the tilemapLayer.position in the collision if fixedToCamera is set to false, otherwise it doesn't need to incorporate the tilemapLayer.position in the collision calculations as they are already accounted for.

@Upperfoot It works after the last commit. Thank you. But...
I think there is some rendering issue left. And maybe it is related to the discussed stuff.
It is only a slightly visible offset of tilemap(a few pixels) in the direction of camera movement. When camera movement stops, offset is decaying back to zero. It is visible when, for example, some things are rendered on top of tilemap(in my case that is a path lines from player to some point). I tried 2.4.7 and there is no such a thing. So it is only in the dev brunch. Maybe I should capture some video or screenshots? I'll try to give more info later...

@SergeyFromHell Could you try 2.4.8 and compare against this https://github.com/photonstorm/phaser/blob/1b7dcd9cbb85f803de35cf9b13f78c692b7f5632/build/phaser.min.js

@Upperfoot I've tested it.
2.4.8: no rendering bug.
https://github.com/photonstorm/phaser/blob/1b7dcd9cbb85f803de35cf9b13f78c692b7f5632/build/phaser.min.js: has rendering bug.

You should really test it by building a release, the pre-built files are
always out of date.
I have tested every Tilemap example last night and they all work fine, with
no rendering bugs at all. So I'm happy this is fixed unless someone can
show me a test case proving otherwise.
On Friday, 10 June 2016, SergeyFromHell<EMAIL_ADDRESS>wrote:

@Upperfoot https://github.com/Upperfoot I've tested it.
2.4.8: no rendering bug.
https://github.com/photonstorm/phaser/blob/1b7dcd9cbb85f803de35cf9b13f78c692b7f5632/build/phaser.min.js
http://url: has rendering bug.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/photonstorm/phaser/issues/2544#issuecomment-225111994,
or mute the thread
https://github.com/notifications/unsubscribe/AAKCfN6o6z_NIDok6CX9_6P8QyH9wY5Kks5qKRGUgaJpZM4Iwuoc
.

--
Photon Storm Ltd.
http://www.photonstorm.com
Skype: richard.davey
Twitter: @photonstorm
Registered in England and Wales.
Company ID: 8036404
VAT Number: 136 4333 27

@photonstorm Sure, I have built git versions. I thought however that npm-hosted releases (2.4.7, 2.4.8 ...) do not need to be rebuilded.
Anyway, I think this issue is finished.

npm releases don't need to be rebuilt, but it was the dev branch that needed testing - and that definitely does need building each time.

I found the commit that fixed rendering bug.
https://github.com/photonstorm/phaser/commit/5415d9b603112e7d74863510d86d07d50ae6838a

Yeah. Just need to fix camera shake now though :)


Generic TypeDef does not work with custom class

Steps to Reproduce

Maybe this is more a dart specific issue, but since I found this while developing flutter app so I decided to post it here. I have written a small example try to reproduce the issue.
So basically I want to create a generic class(Test<T, F>) but with some variable(_cellBuilder) has an external typedef type(CellBuilder) outside the class. testA with String assigned runs fine, but testB failed just as the screenshot shows.
And when I remove <Product> from testB, I get a different error.
"type '(Product) => Widget is not a subtype of type (dynamic) => Widget"
Quite confusing. Any help please?

void main() {

  testA<String>(String content) {
    print(content);
  }

  Widget testB<Product>(Product item) {
    print(item.a);
  }

  testWidgets('Counter increments smoke test', (WidgetTester tester) async {
    Test<int, Product> c = Test(testA, testB);
    c.eval();
  });
}

class Product {
 final String a;
 Product(this.a);
}

typedef CellBuilder<F> = Widget Function(F item);
typedef testString<T>(T text);

class Test<T, F> {
  final testString _f;
  final CellBuilder _cellBuilder;
  Test(testString this._f, CellBuilder this._cellBuilder);
  eval() {
    _f("hello");
    _cellBuilder(Product("world"));
  }
}

Logs

Look at these lines:
  final testString _f;
  final CellBuilder _cellBuilder;

If you don't pass type parameters they get some default values - in this case dynamic. So what you wrote means:
  final testString<dynamic> _f;
  final CellBuilder<dynamic> _cellBuilder;

Now this error type '(Product) => Widget is not a subtype of type (dynamic) => Widget should make more sense to you: indeed _cellBuilder has type (dynamic) => Widget.
You probably want something like this:
  final testString<T> _f;
  final CellBuilder<F> _cellBuilder;

Types with type parameters are kinda like functions, you need to pass type arguments explicitly if you want some specific ones. Just because some type parameters have the same names (e.g. testString is has type parameter named T and class Test has type parameter named T) that does not mean that they will get substituted implicitly.
Also in general I recommend using StackOverflow for questions like this.


templating EPSON component inklevel sensors failing

Home Assistant release with the issue: 0.93.0

Last working Home Assistant release (if known): 0.92.2
Operating environment (Hass.io/Docker/Windows/etc.): HASSIO

Component/platform:  EPSON Workforce https://www.home-assistant.io/components/epsonworkforce/

Description of problem:  Using templates to get the state of sensor.inklevel_black (or any other inklevel color), returns "none", even though the sensor has a state.   I have attached a screenshot showing the template editor returning "none" for the black ink sensor, and right below it you see the States dev tool for the same entity is showing a state value of "84".

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):  Here is the component configuration:
#EPSON Workforce
- platform: epsonworkforce
  host: <IP_ADDRESS>
  monitored_conditions:
  - black
  - yellow
  - magenta
  - cyan
  - clean

Traceback (if applicable):

Additional information:

Did you miss the breaking change in 0.93? The sensor name was updated to fix a typo.

Did you miss the breaking change in 0.93? The sensor name was updated to fix a typo.

I certainly did!   I did a quick ctrl + F search of the blog post, but failed to expand ("READ ON") to expose the breaking changes section, which is how I missed.
Thanks for pointing that out.


frontend: upgrade angular to v16

[x]  upgrade angular to v16
[x] update dependencies
[x] update Jest config
[x] make adjustments as needed

Also changed TypeScript version used in the backend to match the one in the frontend.

The update to Angular v17/v18 will be done at a later point in time.