added resource-timeline plugin

Additional functionality for resource-timeline plugin added to support timeline-scheduler include

Hi, thanks for your contribution.
Resource Timeline is a premium plugin for FullCalendar. How you're configuring it? And how it behaves for people not using it?

Configuration variables as follows in the config/filament-fullcalendar.php
return [
    'timeZone' => config('app.timezone'),

    'locale' => config('app.locale'),

    'resources' => [],

    'plugins' => ['dayGridPlugin, timeGridPlugin, listPlugin, resourceTimelinePlugin, interactionPlugin, momentPlugin, momentTimezonePlugin'],

    'initialView' => 'resourceTimelineMonth',

    'headerToolbar' => [
        'left' => 'prev,next today',
        'center' => 'title',
        'right' => 'timelineMonth,timeGridMonth,timeGridWeek,timeGridDay,listMonth'],

    'views' => [
        'timelineMonth' => [
          'type' => 'resourceTimeline',
          'duration' => [ 'month' => 1 ],
          'buttonText' =>'Resources',
            ],
        ],

    'navLinks' => true,

    'editable' => true,

    'dayMaxEvents' => true,
    'selectable' => true,

];

It's simply not used for people who don't want to utilize it.

Sorry for the delay.


update auth service to manage as REST API

In the same spirit of #206, update wis2box-auth to manage the SQLite3 database via CRUD through a REST API.  This will complete the removal of shared files across containers.

Implemented in #301 and https://github.com/wmo-im/wis2box-auth/pull/1


Add RIGHT and LEFT gravities to support RTL in old SDKs

In RTL languages (such as Persian, Arabic, etc.) on old SDKs, the Gravity of a TextView should be forced to RIGHT. If you used END gravity for RTL, in old SDKs the text would be on right, whereas in new SDKs (supporting RTL), the text would be on left.
So LEFT and RIGHT were added to GravityEnum class and gravityIntToGravity method of MaterialDialog class. Now LEFT and RIGHT could be passed to titleGravity and contentGravity methods of MaterialDialog.Builder subclass.

Thanks, but I made this a little easier. It'll automatically apply left/right gravity instead of start/end below API 17.
https://github.com/afollestad/material-dialogs/commit/965ab656e522b728a60cc2abb79a4f380dff9602

Thank you for considering my request. Below API 17 using RIGHT instead of END makes the text to be on right, however on API 17+ using END puts the text on left because the END and START in RTL has the opposite effect. I tested your change and it did not work properly. I think it would be better to have LEFT and RIGHT in GravityEnum as I mentioned.

RTL layout support didn't exist on Android until API 17. This is the best work around for pre-Jellybean-MR1.

I'll look into any issues with it though.


prisma lift squash

TBD

Personally a fan of this idea, provides a few things:

ability to do an occasional cleanup, lining up with major milestones on a project from which there is no going back.
i run unit tests within which each test context bootstraps a db with the db migrations. minimising their workload is appealing.

An extension of this feature would be to allow squashing of a specific range of migrations, which may be handy in the case of feature branch development, allowing squashing a set of migrations into a single migration that represents the feature prior to merge.


Epi 0.5.15 - Set demiurgeMode and dsuFabricMode to sso-direct

This PR removes the configuration options config.demiurgeMode and config.dsuFabricMode in order to prevent misconguration by accident. sso-direct is being used all the time as aligned in the tech call at Jan-17 2023 at 13:00 CET.
Also documentation is being added to choose the a Volume Snapshot class with deletionPolicy: Retain for pre-upgrade and final snapshot.

Hi @tgip-work, I have 2 comments to this version:

I would not remove ability to have a different mode in values. When using deployments to env where I do not have SSO, I have to inject whole js files, therefore I propose to keep mode and just make "sso-direct" default only if not set ?
can we change "appBuildVersion": {{ required "config.epiVersion must be set" .Values.config.epiVersion | quote}} to take default from runner.image.tag ? Because generally releases are directed by runner version container anyway ?


Added rl section

(not super confident all rewards are still correct, I just copied it over from the oct1 report)

could not build


vale: 2.24.3 -> 2.24.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/vale/versions.
meta.description for vale is: A syntax-aware linter for prose built with speed and extensibility in mind
meta.homepage for vale is: https://vale.sh/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.24.4 with grep in /nix/store/1rqc552vwv3p8vvcc0vpkn85w15v0z31-vale-2.24.4
found 2.24.4 in filename of file in /nix/store/1rqc552vwv3p8vvcc0vpkn85w15v0z31-vale-2.24.4

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
vale

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1rqc552vwv3p8vvcc0vpkn85w15v0z31-vale-2.24.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A vale https://github.com/r-ryantm/nixpkgs/archive/4e0f98c33bb736cd6bf2ebb7abe4fa06fcb4a671.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1rqc552vwv3p8vvcc0vpkn85w15v0z31-vale-2.24.4
ls -la /nix/store/1rqc552vwv3p8vvcc0vpkn85w15v0z31-vale-2.24.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

vale

Maintainer pings
cc @marsam for testing.

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

2 packages built:

vale
vale.data


[C-787] Typo in default report Members

→ Leaderboard
From SyncLinear.com | C-787

@jonathimer I get this error after running the script command


Port #195 to lwaftr_rambutan

A port of #195.

LGTM.

Generally I don't think we will be able to avoid making all apps VLAN-aware. Sometimes you want to carry VLAN-tagged packets through the app network instead of tagging/untagging at egress/ingress.
This is biting us in Snabb NFV soon. VMs should be able to transmit/receive tagged frames all the way to the network. That means every app along the path needs to be prepared to handle encapsulated packets e.g. checksum offload in Virtio-net, packet filtering in PcapFilter, etc. Currently you can't configure those scenarios in our OpenStack binding but one thing coming soon is for L2TPv3 packets to be VLAN tagged so that the VM can discriminate between multiple remote softwires.
This will later bite even harder when people want to use more encapsulations like QinQ and MPLS and for apps to operate on such traffic in interesting ways.
Gonna have to fix this at the lib.protocol level?


Because a thank you issue is always worth having :)

Recently implement a single subscription system for my React Native App.
Really appreciated using your module, especially with the ES next examples with async/await which make async calls so readable ! (which made me refactor all my codebase for the good :D )
Took me some time to find a way to get my subscription ids from Google Play. But got everything working in the end.
So, thx for the great work !

@HadrienPierart Could you share how you manage to get everything working? I find it hard to find any detailed guide explaining how to go through all the steps really, like the signed APK etc.. Would be really awesome to have a guide. Maybe a medium post!

Hey there,
Sorry for the delay, as this is a "thank you" issue, I didnt think to check it when I got the notification...
I followed this tutorial to get everything up and running : https://tokenvolt.gitbooks.io/react-native-payments-integration/content/android-payment-integration.html
If you have any issue, do create another issue ;)


Bugs in advanced indexing of Cupy's getitem when indexes are list

There is a inconsistency between NumPy and CuPy's advanced indexing when input is a list.
import numpy
import cupy
x = numpy.arange(24).reshape(2, 3, 4)
x_gpu = cupy.arange(24).reshape(2, 3, 4)
print(x[[1]].shape)   # (1, 3, 4)
print(x[[[1]]].shape)   # (1, 3, 4)

print(x_gpu[[1]].shape)  # (1, 3, 4)
print(x_gpu[[[1]]].shape)  # (1, 1, 3, 4)

This happens because NumPy handles list type indices differently based on its contents.
When indexes = [int_1, ..., int_n], the indexing is equivalent to the case when eq_indexes = (indexes,).
However, when indexes contain anything other than integers (e.g. indexes=[[1]], which is isinstance(indexes[0], list) == True), the indexing is equivalent to the case when eq_indexes = (indexes[0], indexes[1], ..., indexes[n-1]).

Solved


wsl files inclusion in powertoys run search results

Description of the new feature / enhancement
Showing wsl files/folders alongside windows in the search results in powertoys run
Scenario when this would be used?
Would greatly improve the workflow of wsl users, being able to quickly search files instead of navigating through the file explorer.
Supporting information
No response

Great suggestion! We'll have to investigate implementation details and prioritization for our general stability push.


Purpose of wrapping returned object with n

I've noticed this before, but I didn't bother to ask what it was for since I wrote some code to avoid it. Still, recently I started testing some of my models and I've run into the issue of needing to manually re-cast the object into proper form in order to do tests on it.
Here is an example
Suppose a simple pocketbase collection of just a title field as a string.
Here are some types
//model/title.ts

export interface DatabaseAddons {
  collectionId: string;
  collectionName: string;
  updated: string;
  created: string;
  id: string;
  expand: {};
}

export type InsertableAltTitles = {
  title: string;
};
export type AltTitlesCollection = InsertableAltTitles & DatabaseAddons;

export const createAltTitle = async (data: InsertableAltTitles) => {
  try {
    return await getAltTitle(data.title);
  } catch (error) {
    if (error instanceof ClientResponseError)
      return await altTitleCollection.create<AltTitlesCollection>(data);
    logger.error(
      `Error while trying to create altTitle for ${data.title}`,
      error
    );
    process.exit(1);
  }
};

And here is the test file
const validator: { [key in keyof AltTitlesCollection]: Vi.ExpectStatic } = {
  id: expect.any(String),
  title: expect.any(String),

  collectionId: expect.any(String),
  collectionName: expect.any(String),

  created: expect.any(String),
  updated: expect.any(String),
  expand: expect.any(Object),
};

describe('Model cache', () => {
  const altTitle: InsertableAltTitles = { title: 'example title' };

  it('create new title', async () => {
    await expect(createAltTitle(altTitle)).resolves.toBe(validator);
  });
});

But this doesn't pass, because the returned object is wrapped in a n:{}
What is the purpose of this, and what is the preferred way of easily getting the data out of it?

I'm not sure that I understand the example and what do you mean.
Could you give an example with the exact error message and where is failing?
I guess the n is from the minification, but the name of the exported classes should be preserved.

Here is a simple example
let name = 'example genre'

const result = pb.collection('genre').getFirstListItem<GenreCollection>(
      `name='${name}'`
);

console.log(result)

Output:

n {
  collectionId: '99axzqout4huda7',
  collectionName: 'genre',
  created: '2022-12-09 07:32:19.789Z',
  id: 'qfmm36eqjqaa1b6',
  name: 'example genre',
  updated: '2022-12-09 07:32:19.789Z',
  expand: {}
}

Also, on a side note, is there an option to increase the timeout of the requests? I'm making a lot of them inside of an async pool of workers and most of them get dropped. Also, I'm not sure if this is expected, but the query time on a table of 1.5m records with a few columns is over 11 seconds for me. Are indexes supported?

I'm sorry, I still don't understand what is the issue here.
import PocketBase, { Record } from "pocketbase";

const pb = new PocketBase(...)

const record = pb.collection("examples").getOne("RECORD_ID");

console.log(record instanceof Record); // true
console.log(record.constructor.name); // some minified variable

We can adjust the mangling of the terser minification and enable the keep_classnames and keep_fnames props, but I don't see why this could cause an error in your case. It shouldn't really matter unless you are checking the constructor or function prototype name.

Also, on a side note, is there an option to increase the timeout of the requests? I'm making a lot of them inside of an async pool of workers and most of them get dropped.

Could you provide the exact error message?
The SDK doesn't really set any timeouts explicitly. The dropped requests could be either because of the autocancellation or of issue https://github.com/pocketbase/pocketbase/issues/1187 (later today there will be a v0.9.1 release with a fix for it).

Also, I'm not sure if this is expected, but the query time on a table of 1.5m records with a few columns is over 11 seconds for me. Are indexes supported?

Currently you can't set indexes from the Admin UI (see https://github.com/pocketbase/pocketbase/issues/345 and https://github.com/pocketbase/pocketbase/issues/544), but you could define index in a migration. With v0.9 we support JS migrations too:
// 1. Run ./pocketbase migrate create "new_index"
//
// 2. This will create a blank migration and you can add the following content:
migrate((db) => {
  db.NewQuery(`CREATE INDEX your_index_name ON your_collection_name (field1, field2)`).Execute();
}, (db) => {
  db.NewQuery(`DROP INDEX IF EXISTS your_index_name`).Execute();
})

I'm not familiar with the details of your project, but please keep in mind that we inherit some of the limitations of SQLite and if you really on high concurrent writes PocketBase may not be suitable for your use case. For more info you could check https://www.sqlite.org/whentouse.html.

@Fractal-Tess If the failing test is the toBe call and this is from the JEST suite then it is possible that your test is failing because JEST's toBe as stated in the documentation is using Object.is which based on https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/is considers 2 objects to be equal only if they reference the same object. For example this will not work:
var a = {"test": 1}
var b = {"test": 1}

Object.is(a, b) // false, even if they have the same props

It is also possible that it is expecting POJO (aka. plain object), but the SDK returns a custom Record object. You can try converting it to POJO by calling record.export() or use structuredClone(record)

@Fractal-Tess If the failing test is the toBe call and this is from the JEST suite then it is possible that your test is failing because JEST's toBe as stated in the documentation is using Object.is which, based on https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/is, considers 2 objects to be equal only if they reference the same object. For example this will not work:
var a = {"test": 1}
var b = {"test": 1}

Object.is(a, b) // false, even if they have the same props

It is also possible that it is expecting POJO (aka. plain object), but the SDK returns a custom Record object. You can try converting it to POJO by calling record.export() or use structuredClone(record)

I see,
Thank you very much for the replay.
Perhaps this is even my bad since I'm not very experienced with the testing frameworks and might've missed this.
I opted to use Zod to verify the shape, but I think I'll even get rid of that test.
Anyway, I was just wondering on why exactly the returned record is wrapped on this n:{} object like I mentioned above.

n in this case is the Record class. It is not "wrapped", it's just not a POJO (Plain Old JavaScript Object). Without the terser minification this probably would look like Record: {}. But this shouldn't really matter for the end user because the exported n is aliased to Record (this is why the record instanceof Record is working).
Once again, we can enable the "real" class names but there shouldn't be a need for that unless you need record.constructor.name or Function.prototype.name to print the "real" class name.
I'll close the issue, but if you are still experiencing it, please provide the actual error message and I'll investigate it in more details.


Svelte 5: compiler's "warn" is reported as "error" by the plugin

Before You File a Bug Report Please Confirm You Have Done The Following...

[X] I have tried restarting my IDE and the issue persists.
[X] I have updated to the latest version of the packages.

What version of ESLint are you using?
9.3.0
What version of eslint-plugin-svelte are you using?
2.39.0
What did you do?

Configuration
import eslintPluginSvelte from 'eslint-plugin-svelte';
export default [
...eslintPluginSvelte.configs['flat/recommended'],
];

Check the console output of the following commands in StackBlitz-Demo.
// "reproduce": "vite build && eslint ."
npm run reproduce

Also in Svelte5-REPL.
What did you expect to happen?
"eslint-plugin-svelte" should report the same error level as the svelte compiler.
What actually happened?
❯ npm run build

><EMAIL_ADDRESS>build
> vite build

3:57:34 PM [vite-plugin-svelte] You are using Svelte 5.0.0-next.143. Svelte 5 support is experimental, breaking changes can occur in any release until this notice is removed.
work in progress:
 - svelte-inspector is disabled until dev mode implements node to code mapping

vite v5.2.12 building for production...
transforming (1) index.html3:57:35 PM [vite-plugin-svelte] src/App.svelte:6:5 `constVar` is updated, but is not declared with `$state(...)`. Changing its value will not correctly trigger updates (warn)
✓ 76 modules transformed.
dist/index.html                 0.46 kB │ gzip: 0.30 kB
dist/assets/index-DPDjIYFo.css  1.00 kB │ gzip: 0.54 kB
dist/assets/index-DuTKyy1k.js   7.24 kB │ gzip: 3.29 kB
✓ built in 465ms

~/projects/vitejs-vite-snxrvp 3s

❯ npm run eslint

><EMAIL_ADDRESS>eslint
> eslint .

/home/projects/vitejs-vite-snxrvp/src/App.svelte
  6:6  error  `constVar` is updated, but is not declared with `$state(...)`. Changing its value will not correctly trigger updates(non_reactive_update)  svelte/valid-compile

✖ 1 problem (1 error, 0 warnings)

Link to GitHub Repo with Minimal Reproducible Example
This is easy to reproduce, everything is configured as default.
If you don't want to fix it, feel free, I'm reporting this issue for the third time.
Sorry, I don't have more time to make a GitHub repository for you.
(Also, please don’t ask for "minimal reproduction" TWICE in the issue template and demand for the GitHub Repo the second time!)
Additional comments
Related issue: https://github.com/sveltejs/svelte/issues/11818

recommended config is just recommended rule set. Feel free to change the settings if you are unhappy with them in you eslint config file.
The Svelte compiler sometimes uses the warning level because it also need to consider about backwards compatibility and other considerations.

The svelte compiler throws an error when the code can not compile.
ESLint throws an error when a user wants to throw.
The semantics of error differs between the Svelte compiler and ESLint.

shouldn't the plugin be passed to eslint the same warning level produced by the svelte compiler?

This is possible within the ESLint plugin code, but users can not do fine-grained configure.
So, at present, everything is set to error/warn.
If there is a problem, you should disable the ESLint rule and make the warning from the Svelte compiler an error, which can be achieved with the onwarn option in vite-plugin-svelte.
https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/config.md#config-file


phase-link

This PR adds a new workflow to estimate wrapped phase series. This module named "phase-link" tries to estimate the wrapped phase series for a given neighborhood based on EMI estimation. If the coherence matrix is positive definite and computing inverse is doable, the EMI estimation proceeds. If the coherence is not positive definite and computing its inverse is not doable, instead of giving up with any estimate, here we switch the gear to EVD (Eigenvalue and Vector Decomposition) of Covariance matrix. This significantly improves the estimation and gives wrapped phase estimates for many pixels which EMI alone may miss. In practice the positive definiteness check for the coherence matrix can fail even for cases with very high coherence. I experienced many examples where the coherence matrix is not positive definite and therefore the EMI estimation is not doable while falling back to evd leads to reliable phase estimate with very high temporal coherence of more than 0.9.
Here is an example of a coherence matrix which EMI fails to give an estimate because the coherence is not positive definite. Obviously the coherence is very high and we should provide an estimate.

The results of the new module (EMI + EVD) compared with the EMI estimation for one example dataset can be seen here where the first plot shows EMI only and the second plot shows EMI + EVD from phase-link module:

Note that the light blue pixels are all those pixels that no estimation is provided for by EMI. The example is for one ministack. This improvement is even more critical for workflows which would run on many mini-stacks. If randomly bunch of pixels are unnecessarily masked in each mini-stack estimation, the final results will have a lot more pixels excluded.
In this PR I have not bothered to regularize the coherence matrix when it is not positive definite. Down the line we need to evaluate how efficient the regularization is and what is the gain compared to simply falling back to EVD when coherence is not positive definite. Nevertheless we know that regularization is not always doable and we will still need to fall back to EVD in many cases.
Currently a lot of code is duplicated from evd. I had to make a choice with code duplication or modifying evd. I didn't want to make evd over complicated. Moreover I have relaxed the checks on the coherence and covariance matrices. The only checks that I have kept in phase-link are checking the positive-definiteness of the coherence matrix and check if Lapack can estimate the EVD of Covariance matrix. The rest of the checks seem un-necessary to me and were leading to skipping the estimation for many highly coherent neighborhoods. I think it is ok for short term to have the code duplication. Over long term it would be nice to have EMI and EVD core modules which can be called from phase-link.cpp or evd.cpp. Such changes coupled with handling rasters outside the modules will be a future clean up. Anyways for now I chose the code duplication for further testing the new workflow against the existing estimators in evd.cpp.

This seems good in my testing so far. There seems to be an very noticeable difference between the MLE-only version and this new version on L-band data (higher long-term coherence) with larger stack size (needs more multilook samples to have a positive definite covariance matrix).
In this example, the left side of the image is a rocky mountainous area with the highest coherence, and the bottom right is city. The MLE version is dropping most of the good pixels in those areas, while this PR look much better.

This seems good in my testing so far. There seems to be an very noticeable difference between the MLE-only version and this new version on L-band data (higher long-term coherence) with larger stack size (needs more multilook samples to have a positive definite covariance matrix).
In this example, the left side of the image is a rocky mountainous area with the highest coherence, and the bottom right is city. The MLE version is dropping most of the good pixels in those areas, while this PR look much better.

Thanks @scottstanie for trying this PR.


trying to import Quick Steps but no folder to import to

hi,
i've exported my quick steps from one mailbox but when i try to restore them to another mailbox, there's no Quick Steps Settings folder to import into

any advice?
TIA
K

This is not the proper forum for discussing random articles that give steps to perform in mfcmapi. You should be discussing those issues with the authors of those articles.


Update smithy4s-aws-http4s, ... to 0.18.7

About this PR
📦 Updates

com.disneystreaming.smithy4s:smithy4s-aws-http4s
com.disneystreaming.smithy4s:smithy4s-sbt-codegen

from 0.17.19 to 0.18.7
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.disneystreaming.smithy4s" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.disneystreaming.smithy4s" }
}]

labels: library-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #109.


The hell? COmpile doesn't work on download?

This just happened. It's a fresh download of 0.6.3 with no changes. What the hell

Duplicate Issue

There could be a PR that fixes this
this issue as it only occurs on flixel 5.0.0 and over

Lower your flixel version to 4.11.0

i had the same error but then this happened
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:94: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:142: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:150: characters 18-19 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:151: characters 18-19 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:413: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:419: characters 21-22 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:420: characters 21-22 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:423: characters 21-22 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:424: characters 21-22 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:426: characters 21-22 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:427: characters 21-22 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:429: characters 21-22 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:429: characters 44-45 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:430: characters 21-22 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:430: characters 44-45 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:450: characters 20-21 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:456: characters 20-21 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:493: characters 30-31 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:494: characters 30-31 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:191: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:209: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:212: characters 19-20 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:221: characters 19-20 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:262: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:312: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:316: characters 19-20 : flixel.util.FlxAxes has no field x
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:325: characters 19-20 : flixel.util.FlxAxes has no field y
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:182: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes
source/TitleState.hx:329: characters 58-61 : Float should be flixel.util.FlxAxes
source/TitleState.hx:329: characters 58-61 : ... For optional function argument 'repeatAxes'
help??

What is your flixel version ?

go to main.hx, go to where it says game = (someshit) remove the zoom from it.

use flixel 5.0.1

or just replace line 85
addChild(new FlxGame(gameWidth, gameHeight, initialState, #if (flixel < "5.0.0") zoom, #end framerate, framerate, skipSplash, startFullscreen));

yes

well now i have this...
source/TitleState.hx:329: characters 58-61 : Float should be flixel.util.FlxAxes
source/TitleState.hx:329: characters 58-61 : ... For optional function argument 'repeatAxes'

i had the same error but then this happened
C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:94: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:142: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:150: characters 18-19 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:151: characters 18-19 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:413: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:419: characters 21-22 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:420: characters 21-22 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:423: characters 21-22 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:424: characters 21-22 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:426: characters 21-22 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:427: characters 21-22 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:429: characters 21-22 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:429: characters 44-45 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:430: characters 21-22 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:430: characters 44-45 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:450: characters 20-21 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:456: characters 20-21 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:493: characters 30-31 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:494: characters 30-31 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:191: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:209: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:212: characters 19-20 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:221: characters 19-20 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:262: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:312: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:316: characters 19-20 : flixel.util.FlxAxes has no field x C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:325: characters 19-20 : flixel.util.FlxAxes has no field y C:/HaxeToolkit/haxe/lib/flixel-addons/3,0,0/flixel/addons/display/FlxBackdrop.hx:182: characters 7-25 : flixel.FlxType should be flixel.util.FlxAxes source/TitleState.hx:329: characters 58-61 : Float should be flixel.util.FlxAxes source/TitleState.hx:329: characters 58-61 : ... For optional function argument 'repeatAxes'
help??

Psych Engine doesnt support Flixel Addons 3.0.0, try a lower version.

seeing if this works brb

EVERYONE HERE: I have a new issue
source/Achievements.hx:132: characters 30-54 : Warning : FlxCamera.defaultCamerasis deprecated, useFlxG.cameras.setDefaultDrawTarget instead C:\Users\PROJECT-GlFnd\Downloads\Reset\export\debug\windows\obj>setlocal enabledelayedexpansion Error: 64bit is not automatically supported for this version of VC. Set HXCPP_MSVC_CUSTOM and manually configure the executable, library and include paths Error: Error: 64bit is not automatically supported for this version of VC. Set HXCPP_MSVC_CUSTOM and manually configure the executable, library and include paths
Hwat now

EVERYONE HERE: I have a new issue
source/Achievements.hx:132: characters 30-54 : Warning : FlxCamera.defaultCameras is deprecated, use FlxG.cameras.setDefaultDrawTarget instead C:\Users\PROJECT-GlFnd\Downloads\Reset\export\debug\windows\obj>setlocal enabledelayedexpansion Error: 64bit is not automatically supported for this version of VC. Set HXCPP_MSVC_CUSTOM and manually configure the executable, library and include paths Error: Error: 64bit is not automatically supported for this version of VC. Set HXCPP_MSVC_CUSTOM and manually configure the executable, library and include paths
Hwat now
Edit: here's an image of there. Keep in mind, fresh, clean copy of 0.6.3, using flixel-addons 3.0.0

The warning doesn't mean anything. You need to install MSVC. Also don't use flixel-addons 3.0.0 if you're using Flixel 4.11.0, use 2.11.0

@ACrazyTown I installed flixel-addons 2.11.0 and it's still deprecated
what now

@ACrazyTown I installed flixel-addons 2.11.0 and it's still deprecated
what now

Like I said, it's a warning. It wont affect compiling, you dont have to edit anything

@ACrazyTown it affected compiling, I have to edit something

I tried the flixel-addons 2.11.0 and it worked

@ACrazyTown it affected compiling, I have to edit something

Install MSVC

how do I do that?

should that have done something

should that have done something

No that's a VSCode extension. You need to install MSVC thru the Visual Studio Installer

found
downloading

well now i have this...
source/TitleState.hx:329: characters 58-61 : Float should be flixel.util.FlxAxes source/TitleState.hx:329: characters 58-61 : ... For optional function argument 'repeatAxes'
run haxelib install flixel-addons 2.11.0 in cmd prompt and set it as current flixel addons version


Roll Flutter Engine from 8aa2e6516af1 to 7bf0d33afe62 (5 revisions)

https://github.com/flutter/engine/compare/8aa2e6516af1...7bf0d33afe62
2023-07-07<EMAIL_ADDRESS>Roll Skia from adf5b9c27c33 to 7a3a89fadc25 (1 revision) (flutter/engine#43462)
2023-07-07<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 3D0ft09qP4-Hp_3mQ... to MPy31yjgPV-d_YJq0... (flutter/engine#43460)
2023-07-07<EMAIL_ADDRESS>Roll Skia from 57dc2a31bf26 to adf5b9c27c33 (2 revisions) (flutter/engine#43459)
2023-07-07<EMAIL_ADDRESS>Roll Skia from 11a2eefe4c61 to 57dc2a31bf26 (1 revision) (flutter/engine#43456)
2023-07-07<EMAIL_ADDRESS>Manual roll Dart SDK from 2d98d9e27dae to 0b07debd5862 (21 revisions) (flutter/engine#43457)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from 3D0ft09qP4-H to MPy31yjgPV-d
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC aaclarke@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Can't create iso image #10 is still a problem

Issue #10 is still a problem.
The problem still happens on 11.2 OS and 11.2 from a mounter DMG made via installinstallmacos.py.
output from script is
"-- Converting macOS installer disk image to .iso format.
hdiutil: convert failed - Resource temporarily unavailable"
Funnily enough my hacked code from Issue #10 still works fine if used at line 174

Also happens on 11.3.1.  @Lotusshaney's fix still works.

Unable to reproduce.


Page "Data - Timeline" looks corrupted

Web UI Chrome, Win11
Page looks corrupted

The upper graph should be fixed now. Not sure about the one at the bottom.

Much better, but:

Date a bit truncated on upper graph
second looks not so bad, but I don't know the spec ;-) Some text appears but not really readable...

Fixed!


Failed to discover

I am coming from the homebridge-tuya plugin which I had working just fine.  When I try to configure this plugin I get "Failed to discover Hallway Light<PHONE_NUMBER>0d8e539137) in time but will keep looking."  I can't get the device to show up at all.  Here is a copy of my config file:
{   "bridge": {     "name": "Homebridge",     "username": "0C:2B:3B:C9:FA:0C",     "port": 46385,     "pin": "048-67-101"   },   "description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",   "platforms": [     {       "platform": "TuyaLan",       "devices": [         {           "name": "Hallway Light",           "type": "Outlet",           "manufacturer": "Cotify",           "model": "Smart Wifi Bulb Socket E26",           "id": "80881651840d8e539137",           "key": "fc27ee198e967e13"         }       ]     }   ] }

I was able to resolve this by removing and adding some of my devices in the tuya app.

@twistedindustries I'm also receiving this issue. To clarify, do you mean that you removed and readded devices in the Tuya app on your phone?

@miltykiss Yes to clarify further, I removed the device from the Tuya app and then readded them.  You'll have to run the setup again because the key will have changed.  For good measure I also changed the pin and username in my config and deleted /persist and /accessories folders.  After taking those steps my setup has been stable so far.  Hope that helps

I completely forgot about this and randomly remembered. I tried what you did (including changing the pin/username as well as deleted the persist and accessories folders) and it still fails to discover. :(


storetestcases: fix find tests without pagination limit

#230 was not compatible with #231 since the pagination limit must be specified in the segment filter from now on.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable


BOM triggers invalid CSS exception

Using gulp-sass in the following way is causing an error with single line comments in imports:
gulp.task('build:sass', function () {
    return gulp.src('./wwwroot/theme/**/*.sass', { base: './' })
        .pipe(sass({
            precision: 6,
            sourceMap: true,
            includePaths: [
                './wwwroot/css',
                './wwwroot/lib'
            ]
        }).on('error', sass.logError))
        .pipe(gulp.dest('./'));
});

test.sass
@import config

// =================================================== //
// EDIT THIS FILE                                      //
// =================================================== //

$background: red

body
    background: $background

_config.sass
// =================================================== //
// DO NOT EDIT THIS FILE                               //
// =================================================== //

$background: black

Log
[16:23:02] Using gulpfile C:\Projects\ReadySet\Gulpfile.js
[16:23:02] Starting 'build:sass'...
Error in plugin 'sass'
Message:
    wwwroot\theme\_themeTemplate\css\_config.sass
Error: Invalid CSS after "": expected 1 selector or at-rule, was "{}// =============="
        on line 1 of wwwroot/theme/_themeTemplate/css/_config.sass
[16:23:02] Finished 'build:sass' after 42 ms
>>  {}// =================================================== //
   ^
Process terminated with code 0.

I am unable to reproduce this with the latest node-sass. Please make sure you're running at least<EMAIL_ADDRESS>You can use the following command to make sure you're up to date.
npm outdated

@xzyfer Awe... I see the issue is the BOM. Shouldn't node-sass account for the possible BOM?
I'm using the latest version.

Shouldn't node-sass account for the possible BOM

Yes. Can you confirm if this issue is present when using the SCSS syntax?

No. The issue isn't present in the SCSS syntax.

Thanks @roydukkey this suggest the issue is in the sass2scss library used inside of LibSass cc @mgreter

Created https://github.com/saper/node-sass-issue-1619/ and filed https://github.com/mgreter/sass2scss/issues/44


weight_bounds=(0.15, 0.35) not working

Robert,
First of all, nice job you did there.  I tried to understand your code and congrats for what you wrote.
Still, when trying it, I encountered issues when trying to fix the weight bounds for having diversified portfolios but not too much.  Assuming the investor don't have millions to invest, it is necessary to limit the weight bounds so that he do not have to buy one share of each instrument.
So, I tried with 73 shares, calculated expected returns and built a covariance matrix.
Then I tried the EfficientFrontier with weight_bounds and received the error to use another solver or adjust the constraints.  Here, error is well managed same if not any of the solvers of cvxopt is giving a result (I tried them all).
When using the CAL optimizer, it came out with a bound error into the initialization of cla.py (line 126) because, after the loop, it tries to access b[73] which do not exist as its shape is 73.  This is because it did not entered the loop and never did the i-=1 I assume.
When using weight_bounds(0, 1) everything works fine but,  as I wrote, with 73 shares as input, result is too diversified.  There are weights on every shares.
But, somewhere, you answered to this post into the #243 when you say that portfolio optimisation is not assets selection.  I can play with the gamma on a restricted set of shares (to reduce very small weights) but still a bit disappointing that weight_bounds is not working.  I assume it is not working because every allocations calculated are out of the bounds specified (it is what I observed when looking at the generated weights without specifying bounds).  So, my conclusion is that it is better to first select a small number of assets and then calculate weights for those assets.
Operating system and python version:
Windows 10, python 3.7

Hi @MarcelDelhez,
The reason that you are receiving a bug is that your lower weight bound is too high. You have put 15% as a minimum, but you said you have 73 assets. 73 * 15% is well above 100%.
In otherwords, there does not exist a portfolio that satisfies your constraints (weights sum to one and minimum is 15%), let alone an optimal one. You should decrease the lower weight bound, eg:
ef = EfficientFrontier(mu, S, weight_bounds=(0.005, 0.1))
ef.min_volatility()

gamma won't help you here, because it is meant to increase diversity (see #257 for discussion about decreasing diversity). #254 might be more appropriate: it forces the optimiser to give either zero weight or a minimum weight.
Best,
Robert

Hi @MarcelDelhez,
The reason that you are receiving a bug is that your lower weight bound is too high. You have put 15% as a minimum, but you said you have 73 assets. 73 * 15% is well above 100%.
In otherwords, there does not exist a portfolio that satisfies your constraints (weights sum to one and minimum is 15%), let alone an optimal one. You should decrease the lower weight bound, eg:
ef = EfficientFrontier(mu, S, weight_bounds=(0.005, 0.1))
ef.min_volatility()

gamma won't help you here, because it is meant to increase diversity (see #257 for discussion about decreasing diversity). #254 might be more appropriate: it forces the optimiser to give either zero weight or a minimum weight.
Best,
Robert

Yes of course …
I was for sure drunk that day.  Not able to calculate that … shame on me
https://be.linkedin.com/in/marceldelhez?trk=profile-badge-name Marcel Delhez
Domain Architect - Project Manager - Agile Scrum Master – Chapter Lead
Phone : 0485/90.14.09
e-mail<EMAIL_ADDRESS><EMAIL_ADDRESS>https://be.linkedin.com/in/marceldelhez?trk=profile-badge-cta View profile
From: Robert Martin<EMAIL_ADDRESS>Sent: lundi 18 janvier 2021 02:19
To: robertmartin8/PyPortfolioOpt<EMAIL_ADDRESS>Cc: Marcel Delhez<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [robertmartin8/PyPortfolioOpt] weight_bounds=(0.15, 0.35) not working (#258)
Hi @MarcelDelhez https://github.com/MarcelDelhez ,
The reason that you are receiving a bug is that your lower weight bound is too high. You have put 15% as a minimum, but you said you have 73 assets. 73 * 15% is well above 100%.
In otherwords, there does not exist a portfolio that satisfies your constraints (weights sum to one and minimum is 15%), let alone an optimal one. You should decrease the lower weight bound, eg:
ef = EfficientFrontier(mu, S, weight_bounds=(0.005, 0.1))
ef.min_volatility()
gamma won't help you here, because it is meant to increase diversity (see #257 https://github.com/robertmartin8/PyPortfolioOpt/issues/257  for discussion about decreasing diversity). #254 https://github.com/robertmartin8/PyPortfolioOpt/issues/254  might be more appropriate: it forces the optimiser to give either zero weight or a minimum weight.
Best,
Robert
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/robertmartin8/PyPortfolioOpt/issues/258#issuecomment-761921654 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ADGIMOMRWMPX6236F5YSW3LS2OD75ANCNFSM4WGIBUPQ .  https://github.com/notifications/beacon/ADGIMOKCDTD343ZCCEFHQ43S2OD75A5CNFSM4WGIBUP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFVVAA5Q.gif

Yes of course …
I was for sure drunk that day.  Not able to calculate that … shame on me
https://be.linkedin.com/in/marceldelhez?trk=profile-badge-name Marcel Delhez
Domain Architect - Project Manager - Agile Scrum Master – Chapter Lead
Phone : 0485/90.14.09
e-mail<EMAIL_ADDRESS><EMAIL_ADDRESS>https://be.linkedin.com/in/marceldelhez?trk=profile-badge-cta View profile
From: Robert Martin<EMAIL_ADDRESS>Sent: lundi 18 janvier 2021 02:19
To: robertmartin8/PyPortfolioOpt<EMAIL_ADDRESS>Cc: Marcel Delhez<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [robertmartin8/PyPortfolioOpt] weight_bounds=(0.15, 0.35) not working (#258)
Hi @MarcelDelhez https://github.com/MarcelDelhez ,
The reason that you are receiving a bug is that your lower weight bound is too high. You have put 15% as a minimum, but you said you have 73 assets. 73 * 15% is well above 100%.
In otherwords, there does not exist a portfolio that satisfies your constraints (weights sum to one and minimum is 15%), let alone an optimal one. You should decrease the lower weight bound, eg:
ef = EfficientFrontier(mu, S, weight_bounds=(0.005, 0.1))
ef.min_volatility()
gamma won't help you here, because it is meant to increase diversity (see #257 https://github.com/robertmartin8/PyPortfolioOpt/issues/257  for discussion about decreasing diversity). #254 https://github.com/robertmartin8/PyPortfolioOpt/issues/254  might be more appropriate: it forces the optimiser to give either zero weight or a minimum weight.
Best,
Robert
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/robertmartin8/PyPortfolioOpt/issues/258#issuecomment-761921654 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ADGIMOMRWMPX6236F5YSW3LS2OD75ANCNFSM4WGIBUPQ .  https://github.com/notifications/beacon/ADGIMOKCDTD343ZCCEFHQ43S2OD75A5CNFSM4WGIBUP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFVVAA5Q.gif


How to use taskiq without global variables?

Hello!
I found your project very useful and it fits as a replacement for synchronous celery, but unfortunately I didn't find in the documentation a description of the way to run taskiq without global variables.
Here is an example with global variables:
from taskiq import InMemoryBroker

broker = InMemoryBroker()

@broker.task
async def some_task():
    pass

I made a small wrapper class above AsyncBroker and AsyncTaskiqDecoratedTask that act like fastapi.Router to avoid creating a global broker and allow its replacement on already initialized tasks (usage example).
I would like to know if there are any in-house tools to create something like this in taskiq, and if not, is it planned?
Also, it would be nice to have a --factory option in the taskiq worker command, like in uvicorn, to solve this problem. That is, so that startup can be done as taskiq worker --factory project.tasks:broker_factory and combined with TaskGroup.
project/tasks.py:
from taskiq import InMemoryBroker, AsyncBroker
from .image_tasks import group as image_group

async def broker_factory() -> AsyncBroker:
    broker = InMemoryBroker()
    image_group.setup_broker(broker)
    await broker.startup()
    return broker

I am willing to help with the implementation of this functionality if there is a need for it.
Thank you in advance for your answer!

Hi and thanks for raising this issue. Ca you please provide an example how non-global broker can be used? Because currently I don't see a possible usecase for such scenario.
Factory method is not a bad idea, but it would be hard to define tasks this way. You already can define tasks that are not bound to a specific broker using async_shared_broker.

So, here's how you can do the same thing you did in the example.
import asyncio
from asyncio import sleep

from taskiq import InMemoryBroker, async_shared_broker

class AwaitableBroker(InMemoryBroker):
    async def wait_all(self) -> None:
        for task in list(self._running_tasks):
            await task

@async_shared_broker.task()
async def test_task(s: int) -> None:
    await sleep(s)
    print("Hello World")

async def main():
    broker = AwaitableBroker()

    await broker.startup()

    await test_task.kicker().with_broker(broker).kiq(1)
    await test_task.kicker().with_broker(broker).kiq(2)
    await test_task.kicker().with_broker(broker).kiq(3)
    await test_task.kicker().with_broker(broker).kiq(4)

    await broker.wait_all()

    await broker.shutdown()

if __name__ == "__main__":
    asyncio.run(main())

It does literally the same thing. But I await for all tasks to complete at the end. In order to add such function, I created a broker that can wait for all tasks to complete.

Can you please provide an example how non-global broker can be used? Because currently I don't see a possible usecase for such scenario.

The usage is exactly the same as a normal broker, just without declaring a global variable and increasing the flexibility of the library. I agree that it's a bit more complicated, but it's still better to have both on hand. For example with task group I can have several different types of wokers with common tasks.
Also thanks for the async_shared_broker example, I'd rather use the standard library tools without major modifications.

Close?

If you fully agree that issue can be considered as closed, please close it.


State not visible when injecting router.

Hey guys,
We use Angular 2.0 + ngrx in our app.
For some reason we can not see the local variables of our component when the component gets the Router injected..
Here is an example:

This seems to extend to any components that depend on Router, directly or indirectly - if the Router is in the dependency tree state is not visible.

@smith64fx Is this still an issue? I've attempted to reproduce it without any luck. I injected the router into a component, and I can see it, plus all other state in the state panel. Can you give it a quick re-test?

@tiagoroldao Can you speak to this still being an issue or not?

Closing this now with the assumption that it no longer occurs. Please comment if that turns out to not be the case, and we can reopen.

@stevenkampen This error still occurs, at least for me using Version 1.2.5 of Augury.
I have two Components, which get rendered inside a router-outlet:

A gets a router injected
B doesn't get a router injected

When i navigate to Component B, everything is fine, i can see and manipulate the state of the Component.
But when i navigate to Component A, i cannot see the state (and yes it has state!), but i can still see the Providers and Dependencies (which i can see on both Components).
Hope this helps finding the Bug

This has been fixed in version 1.2.9 which was just released.

I think this or a similar issue is still present -- after updating to 1.2.9 I still can't see the state for components which have Router and ActivatedRoute injected.

@Sabartius, @amellnik Ok I'll look into this again.

@amellnik I am not able to reproduce the issue with your example repo.

@Sabartius Are you seeing this still? I can't reproduce it it seems. If you can create a single component app where this error exists I'll try again at reproducing it, but for now I'll close this. Thanks.

@stevenkampen somehow the issue vanished today, and i don't know what i did differently. I'm sorry that i bothered you.

Not sure if i was supposed to just comment here, but i created a new bug here:
https://github.com/rangle/augury/issues/1283


Unexpected std.extVar error

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
What happened:
I used std.extVar("foo")  within components/params.libsonnet, invoked ks using "ks show default -V foo=bar" and got an error "ERROR find objects: RUNTIME ERROR: Undefined external variable: foo"
What you expected to happen:
I expected std.extVar("foo") to evaluate to the string "bar"
How to reproduce it (as minimally and precisely as possible):
$ ks init test
INFO Using context "euwest-cluster" from kubeconfig file "/home/paul/.kube/config"
INFO Creating environment "default" with namespace "javascript-proxy-qa", pointing to cluster at address "https://api.euwest-cluster.aws.grapeshot.co.uk"
INFO Generating ksonnet-lib data at path '/tmp/test/lib/v1.8.0'
paul@paul-laptop2:/tmp$

Now edit components/params.libsonnet so that it reads:
$ cat components/params.libsonnet
{
  global: {
    // User-defined global parameters; accessible to all component and environments, Ex:
      // replicas: 4,
    foo: std.extVar("foo"),
  },
  components: {
    // Component-level parameters, defined initially from 'ks prototype use ...'
    // Each object below should correspond to a component in the components/ directory
    test: {}
  },
}

and add components/test.jsonnet as follows:
$ cat components/test.jsonnet
local params = std.extVar("__ksonnet/params");

{
  xxx:  params.global.foo,
}

Then:
$ ks show default -V foo=bar
ERROR find objects: RUNTIME ERROR: Undefined external variable: foo
	<builtin>	builtin function <extVar>
	<std>:1136:66-74	thunk <null_fields> from <function <anonymous>>
	<std>:1165:25-26	thunk from <thunk <ta> from <function <anonymous>>>
	<builtin>	builtin function <type>
	<std>:1167:29-31	thunk from <function <anonymous>>
	<builtin>	builtin function <primitiveEquals>
	<std>:1167:8-36	function <anonymous>

	<builtin>	builtin function <flatMap>
	<std>:1147:43-54	thunk from <function <anonymous>>
	<std>:1126:12-13	thunk from <function <anonymous>>
	<std>:1126:5-24	function <anonymous>
	<std>:1147:18-55	function <anonymous>
	<builtin>	builtin function <flatMap>
	<builtin>	builtin function <$objectFlatMerge>
	applyGlobals:3:42-78	function <applyGlobal>
	<std>:229:14-29	object <anonymous>
	During manifestation

Anything else we need to know?:
Not sure - it appears that std.extVar("foo") works as expected within components/test.jsonnet, so maybe it's to do with the 'std.extVar("__ksonnet/params")'
Environment:

ksonnet version (use ks version):

$ ks version
ksonnet version: 0.10.2
jsonnet version: v0.10.0
client-go version: 1.8

Kubernetes version (use kubectl version):

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:22:21Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4", GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T05:17:43Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Bitten by the same issue.


How do I get append calc_script_data_hash() to TxBody before txbuilder.build()?

"transaction submit error ShelleyTxValidationError ShelleyBasedEraBabbage (ApplyTxError [UtxowFailure (FromAlonzoUtxowFail
(WrappedShelleyEraFailure (MissingScriptWitnessesUTXOW (fromList [ScriptHash \"79dc2cb93b706af32fe1ef3b3fb014b98ef83be6b5c1a0c6e9aa8f83\"])))),UtxowFailure (FromAlonzoUtxowFail
(PPViewHashesDontMatch (SJust (SafeHash \"8f2eb3a7b5ad1450bab819e063a6c174943c4544d8ca03d18f3d13b0b34e2a96\")) SNothing))])"

I've tried the hash_script_data as well as calc_script_data_hash. but still no dice. Is there a better way?
calc_script_data_hash is no longer apart of transactionbuilder, and I can only set it after I build out to transactionbody

I realize now that these are two separate errors here.

MissingScriptWitnessesUTXOW (fromList [ScriptHash "79dc2cb93b706af32fe1ef3b3fb014b98ef83be6b5c1a0c6e9aa8f83"

Im not sure how to fix this error im using cip30 to sign the transaction and fill the TransactionWitnessSet

PPViewHashesDontMatch SJust SafeHash "8f2eb3a7b5ad1450bab819e063a6c174943c4544d8ca03d18f3d13b0b34e2a96" SNothing

I added the exunit mem and step from the contract posted on cardanoscan to build out the correct hash with TxRedeemerBuilder.set_exunits()
for some reason cant get the ogmios evaluate Tx to send back anything other than an empty object, which makes me think something is missing, I use draftTx() to build what it can to be evaluated by the ogmios api

@SebastienGllmt


RUMM-834 Introduce the DefaultConsentAwareDataHandler

What does this PR do?
This PR introduces the ConsentAwareDataHandler interface and its default implementation: DefaultConsentAwareDataHandler. All the other dependencies except for the ConsentProvider are not implemented for now and they will follow in the next PRs.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #401 into master will increase coverage by 0.14%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #401      +/-   ##
============================================
+ Coverage     90.99%   91.13%   +0.14%
- Complexity     1167     1190      +23
============================================
  Files           138      140       +2
  Lines          3929     3970      +41
  Branches        461      462       +1
============================================
+ Hits           3575     3618      +43
+ Misses          207      204       -3
- Partials        147      148       +1

Impacted Files
Coverage Δ
Complexity Δ

...al/data/batching/DefaultConsentAwareDataHandler.kt
100.00% <100.00%> (ø)
18.00 <18.00> (?)

...re/internal/data/privacy/PrivacyConsentProvider.kt
100.00% <100.00%> (ø)
5.00 <5.00> (?)

...tadog/android/tracing/internal/data/TraceWriter.kt
83.87% <0.00%> (-9.68%)
9.00% <0.00%> (-2.00%)

...nternal/tracking/OreoFragmentLifecycleCallbacks.kt
89.47% <0.00%> (-5.26%)
14.00% <0.00%> (-1.00%)

...oid/rum/tracking/NavigationViewTrackingStrategy.kt
84.31% <0.00%> (-3.92%)
13.00% <0.00%> (-2.00%)

...internal/tracking/JetpackViewAttributesProvider.kt
89.47% <0.00%> (ø)
9.00% <0.00%> (ø%)

...roid/rum/internal/domain/scope/RumResourceScope.kt
96.80% <0.00%> (+0.80%)
39.00% <0.00%> (+1.00%)

...l/net/info/BroadcastReceiverNetworkInfoProvider.kt
81.05% <0.00%> (+1.05%)
28.00% <0.00%> (+1.00%)

... and 3 more


Update umami docker image url

The  umami docker image url  ghcr.io/umami-software/umami:postgresql-latest was not found, use docker.umami.is/umami-software/umami:postgresql-latest (copied form README.md) instead.

There is nothing wrong with that URL. You have a typo, hcr.io instead of ghcr.io

oh, my mistake

There is nothing wrong with that URL. You have a typo, hcr.io instead of ghcr.io


How to get a list of all collections in order to search for icons?

Hey there!
I was wondering how you made the search function on your documentation website.
I want to create a custom Advanced Custom Fields field (for WordPress) where users can search for icons in Iconify, similar to the existing FontAwesome Field add-on:

We have our own API set up. I'd like to know if there are any functions available in Iconify to get a list of all available collections. Do you just search for icons whose names contain the search parameter and return them?

Search engine is not part of public API. I do plan to create script for searching icons, so it can be integrated into any software. It should have been ready by now according to my original plan, but its taking longer than expected.
When its ready it will be published here: https://github.com/iconify/icon-finder

Hi !
Some updates about this ?
Thanks !

It is in development.
I've implemented it as Figma plug-in (see https://github.com/iconify/iconify-figma/tree/master/ui/src ), currently working on separating that code into separate reusable library. I think it will be published in January.

API queries are now part of documentation: https://docs.iconify.design/sources/api/queries.html


Should we add an MIT license to this?

Something like this:
The MIT License (MIT)

Copyright (c) SKYCATCHFIRE<EMAIL_ADDRESS>(skycatchfire.com)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Yes!

On Jul 8, 2016, at 7:19 PM, Zachary Minner<EMAIL_ADDRESS>wrote:
Something like this:
The MIT License (MIT)
Copyright (c) SKYCATCHFIRE<EMAIL_ADDRESS>(skycatchfire.com)
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Add some post-install tips since it created some confusion

Adding in the ReadMe the instructions send via email and in issue #1 https://github.com/juriansluiman/groceri.es/issues/1

@povode Thanks for this submission. Unfortunately I was absent for a long period, but I intend to pick things up shortly and remove the requirement to load the fixture data this way!


chore: use latest image to deploy windows e2e vmss

What type of PR is this?

What this PR does / why we need it:
Use latest image to deploy windows e2e vmss.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on junjiezhang/use-prod-image-to-deploy-windows-e2e-vmss at 60.739%

Totals

Change from base Build<PHONE_NUMBER>:
60.7%

Covered Lines:
2582

Relevant Lines:
4251

💛  - Coveralls


link to sky.lea.moe github from SkyCrypt Discord

🤔 how does this relate to discord

Oh I mean GitHub


Updating readme from branch example

##Updates
I updated the readme file. Please review and accept.

Thoughts
I probably shouldn't, but okay 👍


Create find_path.java

In this code rat have to find shortest way to reach from starting corner to opposite ending corner which is shortest path to reach and i am applying recursion to solve it

@DhananjayDogne Nice Work, please star the repository.


Allow anything that can be parsed as an IP as a DNS

As reported in https://github.com/smallstep/cli/issues/605, the CLI didn't allow IPv6 addresses (without brackets) as the DNS.
This change allows anything that can be parsed as an IP as a DNS in the CLI.

@dopey: I found one other usage in https://github.com/smallstep/step-sds, but that also seems to accept IP addresses, so I think we're good in that respect.
I did hit an issue with how this integrates with the rest of the Step toolchain, however: https://github.com/smallstep/cli/issues/605#issuecomment-1009953011.


Action Possibility on Local Users

As a developer I want to extend the workflow for local users that authenticate in ZITADEL so I am able to extend my register and login flow for my custom needs.
Acceptance criteria

[x] I want to be able to add an action on local authentication
[x] I want to be able to trigger the action Post Authentication
[x] I want to be able to trigger the action Pre Creation
[x] I want to be able to trigger the action  Post Creation
[x] I want to be able to create the same actions as we have on external authentication

@adlerhurst TODOS:

[ ] add example
[ ] docs


Windows 10 java.lang.UnsatisfiedLinkError: ..\AppData\Local\Temp\ojgl-x64.dll: Can't find dependent libraries

I develop my project on two PCs one with Windows 11 and one with Windows 10. Both have Java 17 LTS installed but on my Windows 10 PC I can't get the lib to work correctly (I use LWJGL). During canvas initialization the project crashes with an UnsatisfiedLinkError and I have no idea why?  The full stacktrace is this
java.lang.UnsatisfiedLinkError: C:\Users\Test\AppData\Local\Temp\ojgl-x64.dll: Can't find dependent libraries
        at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)
        at java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(NativeLibraries.java:388)
        at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:232)
        at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:174)
        at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2389)
        at java.base/java.lang.Runtime.load0(Runtime.java:755)
        at java.base/java.lang.System.load(System.java:1953)
        at com.huskerdev.ojgl.GLPlatform.<clinit>(GLPlatform.kt:33)
        at com.huskerdev.ojgl.GLContext$Companion.create(GLContext.kt:21)
        at com.huskerdev.openglfx.core.implementations.InteropImpl.onNGRender(InteropImpl.kt:73)
        at com.huskerdev.openglfx.OpenGLCanvas$NGOpenGLCanvas.renderContent(OpenGLCanvas.kt:178)
        at javafx.graphics/com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2072)
        at javafx.graphics/com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1964)
        at javafx.graphics/com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:480)
        at javafx.graphics/com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:329)
        at javafx.graphics/com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.java:92)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
        at javafx.graphics/com.sun.javafx.tk.RenderJob.run(RenderJob.java:58)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at javafx.graphics/com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:126)
        at java.base/java.lang.Thread.run(Thread.java:833)

The funny thing is when I look into the path the dll is right there, no typo or anyting. And like I said it works on my other PC with Windows 11 perfectly fine? I checked and the dll is not locked by any other process or something like that. Do you have any ideas whyt might be wrong? Any other dependencies which needs to be installed?
And another minor issue or hint, in your InteroptImpl.kt file you set the initialized variable to true and in the next line you create the GLContext but that fails with the UnsatisfiedLinkError. This leads to the fact that you have now a null context variable and initialized set to true. This will cause NullPointerExceptions on every onNGRender call then. But not sure how to handle that as it should not come to an UnsatisfiedLinkError in the first place.

Bingo, I found out why it is not working. I spent the last couple of hours figuring out what could be the difference and the difference was that there are some dependency problems inside the ojgl-x64.dll. In specific the dependency problem was because following dll was missing on my PC "VCRUNTIME140_1D.dll" I figured that out by using the dependency walker tool
Here is a screenshot of the issue
I also found an interesting stackoverflow  answer about this (or at least a similar) issue. The question is how can this be avoided in the future when people are using this library. To use the lib it requires to have some kind of Microsoft Visual C++ Redistributable installed, the question is which? Maybe you can add some more information in the Readme? This is for sure helpful if someone wants to build an installer for their application. On my other PC I have Visual Studio 2019 installed and on the PC where this problem occured I only had Visual Studio 2017. The missing dll was added to the system32 folder on my machine once I have installed Visual Studio 2019. Not sure for what you are using this dll exactly but maybe this dependency can be removed totally?

Yes, you are right. By default, compiling a C++ .dll in VisualStudio requires a dependency on the Visual C Runtime. I completely forgot about it as it didn't cause any problems on my computer.
As internet says, the option /NODEFAULTLIB should fix the problem.
I am going to add this fix as soon as I can

Awesome, yes on my other development PC I did not notice anything either as I have everything installed so it was quite a coincidence that I figured that out. Thanks

I noticed once it reached my testers. I'm glad you're already on it though.
Will any of the other system32 dependencies be removed along with this? I noticed that there is a dependency on msvcp140d-dll
according to this stack post i can't legally redistribute that dll with my application
https://stackoverflow.com/questions/51437963/msvcp140d-dll-missing-is-there-a-way-around
could it be linked to the release version?

As the dll you are referring has a "d" suffix it means it's a debug dll. If the lib is built as release version all these references to these debug dlls should be gone.

Fixed in release 3.0.5

@husker-dev btw the version is now 3.05 but I guess it should be  3.0.5 (missing dot)?

@grill2010 Yes, thanks


Unknown "document_rootwp" variable error in certain environments

Nginx gives an error nginx: [emerg] unknown "document_rootwp" variable when in staging environment.

This was quite misfortunate timing. Yesterday evening I pushed breaking change into the docker-wordpress-server and it seems to have cached that broken image for you. I noticed this after 20minutes and pushed new version.
If errors like this happen try rebuilding with --pull flag for the docker build.


Exception when sorting by "Disease Status" column

In the UCSC dev environment, click on the "Disease status" column and see the following error:

Add sortColumnKey to disease table config for v2 environments.

@theathorn this is on cgl dev for your review.
https://dev.singlecell.gi.ucsc.edu/explore/projects?filter=[{"facetName":"genusSpecies","terms":["Homo sapiens"]}]
Cheers,
D

It doesn't crash any more, but doesn't appear to sort in any order that I can discern..


open project causes error

for me the open project button gives a white screen and some errors
[1722:0831/124444:INFO:CONSOLE(15)] "Popup:", source: file:///Users/zachlieberman/Desktop/pgElectron/js/semantic.min.js (15)
[1722:0831/124444:INFO:CONSOLE(2)] "Uncaught TypeError: Cannot read property 'replace' of undefined", source: file:///Users/zachlieberman/Desktop/pgElectron/js/jquery.min.js (2)
[1722:0831/124444:WARNING:ipc_message_attachment_set.cc(37)] MessageAttachmentSet destroyed with unconsumed descriptors: 0/1
will dig into this a bit.   (and move this to the dialog after the generate or update action has completed)

With the "open project button" you mean "import" ?
I can't reproduce that error...

this button doesn't seem to work for me:

Oh, indeed, something went wrong... fixed in 39ee1f9
Btw, I'm wondering if it works on non-unix systems as it uses a shell command, like the link to ofxAddons.

But I didn't see the same error, not sure if I fixed the right thing. #needsconfirmation

this seems fixed, closing...


dialog: use monospace for ASCIIdoc output

This makes the output look better aligned

Yes, I agree plain text look better with monospace font.


Contribution of puppet-forge to incubator Charts

For a couple days now the CircleCi results have not been displaying. All I get when I try to look at the report of what failed is just a spinning icon. It seems to indicate that it failed lint of the chart, but I get linting of the chart to pass.
$ helm lint puppet-forge
==> Linting puppet-forge
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, no failures

The following is the failure:
Linting the Chart.yaml and values.yaml files at incubator/puppet-forge
incubator/puppet-forge/values.yaml
  29:11     error    trailing spaces  (trailing-spaces)
  61:1      error    too many blank lines (1 > 0)  (empty-lines)

I can tidy this up now.

Ah. Thank you. Was not evident from helm lint. I was just about to push another commit to fix these when I notice you had done so. So another thank you very much :-)

/ok-to-test


Add specificity to react-native link

Make sure to add your changes to versioned docs
Thanks for opening a PR!
The docs cover several versions of react-navigation, and in some cases there are several files (for version 1, version 2 and etc.) that all describe single page of the docs (eg. "Getting Started").
Please make sure that the edit you're making in docs/file-you-edited.md is also included in the file for the correct version, eg. website/versioned_docs/version-3.x/file-you-edited.md for version 3. :+1:

makes sense, thanks


/proc should not be bind mounted

should mount new  proc.  The container running in a new pid namespace would see inaccurate content in /proc for all the processes that "don't exist".
mount a new proc.  This would give the same data, except for things like processes, which would be tailored to the container environment rather than reflect the parent system.
There may be similar considerations for /sys, but I'm not 100% sure.  Might err on the side of doing new mount for sys if I had to choose personally.

sorry, didn't look more carefully...

You raise an interesting question for /sys. That deserves some research!

Yeah, I can't think of anything concretely, but I was just doing it as a new mount 'just because' sys didn't have any complexity and seemed to double mount fine, and erred on the side of caution.  There might be no good reason, but it didn't seem harmful either.

Can you do a cursory check to see if there are any obvious differences between the two sysfs file systems? Thanks!

I didn't see anything, unless I unshare the network namespace...  For singularity that wouldn't matter because an unshared network is precisely the PITA that singularity would avoid...
It does show that sysfs is at least somehow sensitive to namespaces in some way, but at the moment, I didn't see anything concrete relevant to singularity use case.

I think on principal, I will mount sysfs properly and let the kernel deal with any namespace specifics that maybe necessary (or not).
Thanks again for pointing this out Jarrod!


github: update osbuild-ci container image

Includes libdnf5 for running the osbulid-depsolve-dnf5 tests.

tools/test/test_depsolve.py::test_depsolve[test_case0]
[gw0] [ 12%] PASSED tools/test/test_depsolve.py::test_depsolve[test_case0]
tools/test/test_depsolve.py::test_depsolve[test_case1]
[gw0] [ 25%] PASSED tools/test/test_depsolve.py::test_depsolve[test_case1]
tools/test/test_depsolve.py::test_depsolve[test_case2]
[gw0] [ 37%] PASSED tools/test/test_depsolve.py::test_depsolve[test_case2]
tools/test/test_depsolve.py::test_depsolve[test_case3]
[gw0] [ 50%] PASSED tools/test/test_depsolve.py::test_depsolve[test_case3]
tools/test/test_depsolve.py::test_depsolve_dnf5[test_case0]
[gw0] [ [62](https://github.com/osbuild/osbuild/actions/runs/8704112733/job/23871683501?pr=1736#step:3:63)%] SKIPPED tools/test/test_depsolve.py::test_depsolve_dnf5[test_case0]
tools/test/test_depsolve.py::test_depsolve_dnf5[test_case1]
[gw0] [ 75%] SKIPPED tools/test/test_depsolve.py::test_depsolve_dnf5[test_case1]
tools/test/test_depsolve.py::test_depsolve_dnf5[test_case2]
[gw0] [ 87%] SKIPPED tools/test/test_depsolve.py::test_depsolve_dnf5[test_case2]
tools/test/test_depsolve.py::test_depsolve_dnf5[test_case3]
[gw0] [100%] SKIPPED tools/test/test_depsolve.py::test_depsolve_dnf5[test_case3]

still being skipped.  Checking.

What seems to be happening here is that libdnf5 doesn't exist in the environment set up by tox (even if I add it to the deps in tox.ini), so the has_dnf5() that's running in test_depsolve.py is returning false.  But the actual osbuild-depsolve-dnf5 script is running outside that environment, in the system one, which does have libdnf5 installed so it does work if the check is removed or ignored.

The (new?) autopep8 in the ci container is picking up some new issues.  Some are ok
--- original/stages/test/test_mkfs_xfs.py
+++ fixed/stages/test/test_mkfs_xfs.py
@@ -71,9 +71,9 @@
     output = subprocess.check_output([
         "xfs_admin", "-l", "-u", fake_disk_path], encoding="utf-8")
     assert f'UUID = {fake_uuid}' in output, \
-           f'expected UUID not found in: {output}'
+        f'expected UUID not found in: {output}'
     assert f'label = "{fake_label}"' in output, \
-           f'expected label not found in: {output}'
+        f'expected label not found in: {output}'

though this one should just be
--- a/stages/test/test_mkfs_btrfs.py
+++ b/stages/test/test_mkfs_btrfs.py
@@ -70,10 +70,8 @@ def test_mkfs_btrfs_integration(tmp_path, stage_module):
     assert os.path.exists(fake_disk_path)
     output = subprocess.check_output([
         "btrfs", "filesystem", "show", fake_disk_path], encoding="utf-8")
-    assert f'uuid: {fake_uuid}' in output, \
-           f'expected UUID not found in: {output}'
-    assert f'Label: \'{fake_label}\'' in output, \
-           f'expected label not found in: {output}'
+    assert f'uuid: {fake_uuid}' in output, f'expected UUID not found in: {output}'
+    assert f'Label: \'{fake_label}\'' in output, f'expected label not found in: {output}'

some I don't necessarily agree with but whatever, like
--- a/test/run/test_mount.py
+++ b/test/run/test_mount.py
@@ -178,8 +178,8 @@ def create_image_with_partitions(tmp_path):
         ["parted", "--script", img, "mklabel", "msdos"],
         ["parted", "--script", img, "mkpart", "primary", "ext4", "1MiB", "10Mib"],
         ["parted", "--script", img, "mkpart", "primary", "ext4", "10MiB", "19Mib"],
-        ["mkfs.ext4", "-F", "-E", f"offset={1*1024*1024}", img, "9M"],
-        ["mkfs.ext4", "-F", "-E", f"offset={10*1024*1024}", img, "9M"],
+        ["mkfs.ext4", "-F", "-E", f"offset={1 * 1024 * 1024}", img, "9M"],
+        ["mkfs.ext4", "-F", "-E", f"offset={10 * 1024 * 1024}", img, "9M"],
     ]:
         subprocess.check_call(cmd)
     return tree, img.name

but some are downright bizarre, like
--- original/stages/org.osbuild.debug-shell
+++ fixed/stages/org.osbuild.debug-shell
@@ -10,7 +10,8 @@

     unit = f"""
 [Unit]
-Description=Early root shell on {tty} FOR DEBUGGING ONLY
+Description=Early root shell on {
+        tty} FOR DEBUGGING ONLY
 DefaultDependencies=no
 IgnoreOnIsolate=yes
 ConditionPathExists={tty}

Closing in favour of #1744


Improve filename-based hash algorithm detection

When checking a hash file without a hash algorithm specified on the
command line, RHash checks whether the hash file's extension matches
the name of one of the supported hash algorithms, accepting case
differences and a dash here and there, so it recognizes both
"foo.sha256" and "BAR.SHA-256".
However, hash files are often enough named e.g. "sha256sums" [1], and,
unfortunately, RHash doesn't recognize the hash algorithm in those
cases, because:

RHash only considers the extension, i.e. the part of the file
name after the last '.', but in that case there is no extension.

The "sums" suffix prevents a match to any known hash algorithm.

Handle this case by updating file extension matching to:

Consider the whole file name if there is no extension, fixing (1).

Allow trailing characters after a matching hash function is found,
fixing (2).  Note that this essentially allows any suffix: while I
don't recall ever seeing any suffix other than "sums", I don't
think it's worth it to impose any restrictions.  However, take
care to allow trailing characters only when matching a file
extension, but disallow them while parsing the content of a
BSD-style hash file.

[1] E.g. https://releases.ubuntu.com/20.04.4/SHA256SUMS or
https://cdimage.debian.org/debian-cd/11.2.0/amd64/iso-dvd/SHA256SUMS

That int allow_trailing_chars parameter added to bsd_hash_name_to_id() acting as a boolean flag kept haunting me...  So here is an update replacing that with named constants from a new enum.

Thank you for the patch!


Add version stamp to generated source

Add a version stamp to the generated source, so when the time comes when we do have the change things we can make it an explicit compile error instead of a cascade of errors.

Fixed by #234


Upgrade terraform-provider-aws to v5.23.1

This PR was generated via $ upgrade-provider pulumi/pulumi-aws.

Upgrading terraform-provider-aws from 5.23.0  to 5.23.1.
Fixes #2934

/release minor

Release is minor because https://github.com/pulumi/pulumi-aws/pull/2931 is unreleased.


make ui more app real

add air config for handling frontend ui changes
move logs to sidebar and make map live

Features

Logs are now rendered using a drawer
Map is live with some hardcoded coords it will react as any other driver request app.
Show toast when user request a drive

https://github.com/user-attachments/assets/6f415075-3fee-4132-a7a6-a1baab16362a

LGTM, please merge when you're done with your changes and you think it's ready to go


Make environment variables available in the manifest

I really really really want to be able to do this:
name: HELLO
version: 0.1.0
description: "An example Porter configuration"
invocationImage: "{{porter.build.env.user}}/porter-hello:latest"

Then when I build the bundle the invocation image would be built using my current user to carolynvs/porter-hello:latest.

A couple options come to mind on how to do this:

Do a templating pass during porter build and the porter.yaml stored in the bundle would have {{porter.build.env.user}} replaced with the build value. So the porter.yaml locally and the porter.yaml in the bundle would look different. A problem with this is that I'm not sure the templating engine lets you ignore and leave in unconsumed mustache's.
Inject parameters into the bundle (like we do for porter-debug) to handle these porter build variables. So porter.build.env.user would be injected into bundle.json as porter.build.env.user (I'm thinking of switching to porter.debug for consistency), then when we do replacements, we look for parameters that are "ours" and fill them in during templating.

Seems like #2 is the way to go?


Skip reading the revision meta when requesting a specific revision

Summary
This one is a less frequent request path but I thought I'd log it anyway. Typically when a user requests a document, we execute two reads in FDB: one read to get the revision identifier of the current winning revision, and a second to get the body of that revision.
When a user requests a specific revision I think we can omit the first read and jump straight to the ?DB_DOCS space. But we don't. Here's a trace of me requesting a specific revision of a document; the first read GetRange call still goes to the revisions subspace:

(the two orange elements are checking metadata versions; I've filed separate issues to address them).
Desired Behaviour
When a user requests a specific revision on its own we should be able to retrieve that with a single GetRange request.
Possible Solution
I believe the current code for retrieving specific revisions is here:
https://github.com/apache/couchdb/blob/ff2cdb84f639ea26ac7b1ad85abb0a49c5141c74/src/fabric/src/fabric2_db.erl#L513-L550
There's a lot of extra work, retrieving all revisions of a document and building a couch_key_tree in memory in order to compute the revision identifier, before finally requesting the revision body at L540:
https://github.com/apache/couchdb/blob/ff2cdb84f639ea26ac7b1ad85abb0a49c5141c74/src/fabric/src/fabric2_db.erl#L540
The fix here would involve some streamlining of that function. There's a decent amount of subtlety there with options like latest=true.
Additional context
This optimization is probably mostly useful for the replicator, which does make requests for specific document revisions all the time.

The first bit of subtlety is that there's a significant difference between "revision that's not a leaf" vs "I don't know of this revision" which means any time you get a not_found when doing a direct lookup you'll fall back to having to search every revisions rev_path.
That said, I'd still think it'd probably be worth adding the optimization as the replicator should theoretically be requesting the latest revisions most of the time.
Also while staring at this thinking of optimizations:

revs=all could be a single scan of the revision space
we should investigate building the tree once and then searching for each revision vs just searching each rev_path for the given revision. Though that also means we have to be a bit careful to match couch_key_tree:get_* functions.


[Feature Request] Support Nutanix natively without kubevirt

Hi,
Please implement cluster API for Nutanix provider.
kubevirt can be  workaround, but we need the direct integration with Nutanix.

Hi, any news after 3 months ?


composer update causes ReflectionException  Class html does not exist

Hi,
After composer update i get the following error in my website. I am using Yii2 basic
reflection

This works on my local server where I have not done the composer update yet.
Does anyone knows what is this issue?

How to reproduce it?

Is this a case-sensitivity issue? In the pic the class name is lowecase.

If you have a basic Yii2 setup update the composer dependencies. Then try to access the url that is not allowed for the non members(login users). You will get the above error.
e.g logout is allowed only if user is logged in to the system. So if i go to my website and type the url  mywebsite.com/site/logout it gives the above error.
If I use the url  mywebsite.com/site/login it do not show any error

Can you show your controller code?

Below is my controller SiteController.php
user->isGuest) {
        if(in_array($this->action->id ,['logout','sales'])){
            return $this->redirect(Url::to(['site/login']));
        }
    }

    if(!\Yii::$app->session->has('checkinuser')){
        if(in_array($this->action->id ,['sales'])){
            Yii::$app->base->redirectOnLogin();
        }
    }

}

public function init() {
    $this->layout = "main";
    $this->setMain("login");
    parent::init();
}

public function actions()
{
    return [
        'error' => [
            'class' => 'yii\web\ErrorAction',
        ],
        'captcha' => [
            'class' => 'yii\captcha\CaptchaAction',
            'fixedVerifyCode' => YII_ENV_TEST ? 'testme' : null,
        ],
    ];
}

public function actionLogout()
{
    Yii::$app->user->logout();
    return $this->goHome();
}

public function actionLogin(){
    $this->setMain("login");
    if (!\Yii::$app->user->isGuest) {
        Yii::$app->base->redirectOnLogin();
    }
    $model = new LoginForm(['scenario' => 'login']);
    if ($model->load(Yii::$app->request->post())) {
        if ($model->login() && $model->validate()) {
            //on sucess redirect users to page that he has access to or support page
            Yii::$app->base->redirectOnLogin();
        }else{

            $model->errors;
            foreach($model->errors as $key => $val){
                if($key=="device_id" && $val[0] == "error.notfound"){
                    return  Yii::$app->response->redirect(Url::to(['site/activate']));
                }
            }
           return $html = $this->render('login', ['model' => $model]);
            //return Json::encode($html);
        }
    } else {
        return $html = $this->render('login', ['model' => $model,]);
        //return Json::encode($html);
    }
}

}
public function actionSupport(){
    $this->setMain("support");
    $model = new LoginForm(['scenario' => 'resetpassword']);
    return $this->render('support');
}

public function actionHome(){
    return $this->render('index');

}
}

The behaviors method should return an array.
What you're trying to do is documented here, http://www.yiiframework.com/doc-2.0/guide-security-authorization.html


Missing type in the spec

For some reason, the key type is not listed in the generated markdown file, for both generic RDF and model RDF, e.g.: https://github.com/bioimage-io/spec-bioimage-io/blob/gh-pages/model_spec_latest.md
@FynnBe

the new user docs have it: https://github.com/bioimage-io/spec-bioimage-io/blob/gh-pages/user_docs/model_descr_v0-5.md#type-literalmodel--model


Implement GCP FastCheck upon container start

@r-orzechowski you probably should rebase your changes on master, because of the merge you've made it looks like your PR has 17 commits, which already are in master.


⚠ Samsung has degraded performance

In 4535932, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2622 ms

Resolved: Samsung performance has improved in e26a4ef.


Delivered_amount updates needed

Two issues with delivered_amount:

If you request a ledger with expanded transactions, delivered_amount is not included. It should be.
For ledgers before the cutoff, we should not report delivered_amount as unknown if the partial payment flag isn't set – the payment must have delivered the full amount.
Do a sanity check on all other areas that should have delivered_amount - and fix any missing delivered_amount.

Exported from RIPD-1232

Regarding concern 1, I just submitted the following query to a local node that was running 2.0.0-rc4  ...
{
    "id" : wsid,
    "command" : "ledger",
    "ledger_index" : 84368639,
    "binary" : False,
    "expand" : True,
    "transactions" : True
}

The returned Payment transactions included delivered_amount fields.  So it looks like concern 1 has been addressed already.
Regarding concern 2, the cutoff referred to in that sentence is during February of 2014.  That cutoff is almost 10 years ago now.  The response is, "unavailable".  We could potentially look at the flags for very old transactions to see if the tfPartialPayment flag is set.  But is the change worth it for transactions that are 10 years old or older?  This question should be answered for both clio and rippled, since both would require the change.


validationRules support

Would be awesome!
I see that graphql-http supports Deno and also validationRules, but I'm being lazy at the moment and don't feel like changing my GraphQL setup.

A PR with implementation of this feature is welcome!

I think gql needs a decent rewrite, by porting code from graphql-http and adapting Deno APIs, after this validationRules should be working

See #21

Word, this is great! I'll test in a bit.