Es extract array

Hi Srikanth, here is a PR that will cause some impact.

es:extract-array is a new function.  Like es:optional, I pulled it out from generated code into the main entity services module.
fixes  #149
editorconfig is a plugin that enforces things like tabs and spaces for ones proejct.
updates ml-gradle.
took out DMSSK dependency in examples and added java client api, which now includes DMSDK.

e2e will have to mirror #5.  there are some key updates.

Oh, I also included the commits from your PR #164, ready to merge with this one.

Looks like a great PR. Will .editorconfig override the tab/spacing set in my eclipse?

I think you need a plugin in Eclipse to use editorconfig.

Got it. Thanks @jmakeig
Please go ahead and merge @grechaw . Once merged I will absorb changes and create a PR with my tests for #149 .


Changes to make crate std compatible.

Adds std feature that is enabled by default
Adds std module to import dependencies from std (for std) and alloc / core (for no-std)
Removes dependency thiserror because it relies on std

 ssz_rs git:(feat/no-std) ✗ cargo build --release
   Compiling ssz_rs v0.7.0 (/Users/claravanstaden/IdeaProjects/ssz_rs/ssz_rs)
    Finished release [optimized] target(s) in 1.20s
ssz_rs git:(feat/no-std) ✗ cargo build --release --no-default-features
   Compiling ssz_rs v0.7.0 (/Users/claravanstaden/IdeaProjects/ssz_rs/ssz_rs)
    Finished release [optimized] target(s) in 1.16s


feat: add FFTBatch benchmark

Description
This PR adds FFTBatch benchmark of Tachyon and Plonky3. It seems there is a lot of rooms for improvement in Tachyon :100:

docs(bench): introduce FFTBatch benchmark should be typed with test

I think

feat(benchmark): introduce Config and Vendor and feat(benchmark): introduce FieldType for specifying which field to use should be typed with refac.


preview flickering

Preview becomes zero sized during its updating
set css height dynamically just after processallmathdelayed
setting min-height on method would fix height dropping
Preview also does unnecessary reflow on changes
 *ngif="mdhtmls"

onko tämä TIM issue

periaatteessa joo


Text box for SourceExpression in Table settings Refresh Policy

The text box to write SourceExpression in Table settings under Refresh Policy would be really handy to have since the Power Query expressions contain usually multiple rows. Currently copy-pasting Power Query expressions without modifications is impossible since the SourceExpression doesn't allow line breaks.
This kind of text box is already available for Description in Table settings under Basic settings so the implementation should be quite straightforward.

Fixed in 2.16.1.


[PPP-4660] - Use of Vulnerable Component: Components/jackson-databind:<IP_ADDRESS>

@smmribeiro
@bcostahitachivantara
@renato-s

:x: Build failed in 29s
Build command:
mvn clean verify -B -e -Daudit -amd

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message

:x: Build failed in 38s
Build command:
mvn clean verify -B -e -Daudit -amd

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message


Move away from Alpine base image

The newest version of Jekyll Sass Converter uses sass-embedded for stylesheets, and it seems like that just isn't available on Alpine Linux (see e.g. https://github.com/sass/dart-sass-embedded/issues/85, https://github.com/sass/dart-sass-embedded/issues/106).

I had to downgrade to Jekyll 4.2 (and work around #335 again) because I can't deploy my websites anymore.
The docker image is broken. Jekyll 4.2 doesn't work out of the box because of #335 and 4.3 doesn't work because of this sass-embedded problem.

If you're looking for a non-stale docker image for jekyll development, I've since switched to https://github.com/BretFisher/jekyll-serve, which is more up to date and is built on Debian.

Similar Issue https://github.com/envygeeks/jekyll-docker/issues/363


Decide procedure(s) to handle CI failures

The current state of CI seems unsatisfactory for a well-maintained project:

In the absence of strong maintainer presence (hopefully I don't have to apologize for my own absences now :-) this issue it to suggest creating a procedure to avoid this from re-occurring:

Designate which sub projects have to be "CI green" on "main" branch within a day of turning red. Arguably needs a decision on https://github.com/open-quantum-safe/tsc/issues/2 ; I'm willing to move that issue forward regardless as per the discussion there if the TSC finds this unnecessary to look into/resolve. I personally think this needs resolution as it impacts user decisions as to which OQS sub projects one can depend on (or not).
Designate responsibilities for fixing CI. I'd normally say that should be the maintainers (or committers in their absence) of projects designated in "maintained" state. Right now this is only documented for liboqs and oqs-provider. Both are currently "CI red" pointing to a need to improve. For oqs-provider, can I ask @thb-sb whether it's OK for you to be listed as maintainer (and then assume responsibility to look into such things in any future absences of myself)?
If there is general acceptance that "red CI state" is OK for some projects (?), this is to suggest documenting this decision in the README of each such sub project, maybe together with a public call searching for a maintainer (if not already declared to be EOL).

If there is someone else beyond "designated sub project maintainers" (@vsoftco @dstebila @thb-sb @baentsch) willing to take ownership for this, please chime in.

I do get emails when CI builds fail, but at this point they've become background noise and I have a hard time distinguishing when it's a failure we need to pay attention to or not.
Any recommendations @ryjones from other projects on how they handle monitoring of ongoing CI status?  I know that the theory would be that ensuring things are green on a PR before it's merged would mean that CI on main is also green, but that doesn't seem to hold true for us.

1. Designate which sub projects have to be "CI green" on "main" branch within a day of turning red. Arguably needs a decision on [OQS sub projects: Which ones to drop for good #2](https://github.com/open-quantum-safe/tsc/issues/2) ; I'm willing to move that issue forward regardless as per the discussion there if the TSC finds this unnecessary to look into/resolve. I personally think this needs resolution as it impacts user decisions as to which OQS sub projects one can depend on (or not).

Yes, this seems sensible: our commitment to keeping CI green should be tied to which subprojects we deem supported.  I'll chime in on https://github.com/open-quantum-safe/tsc/issues/2 right after this comment.

@dstebila you could set quality gates for an auto merge. Basically, if (some list of jobs fail don't) and (has the votes needed to merge) and (all conversations are resolved)

@dstebila you could set quality gates for an auto merge. Basically, if (some list of jobs fail don't) and (has the votes needed to merge) and (all conversations are resolved)

I was asking more about getting auto-alerted if a weekly job fails.  Basically, does Github have anything that would cover the same type of functionality we have on https://openquantumsafe.org/dashboard.html?

Yes, you could do that. Basically, a weekly job that checks those statuses and files an issue or a new discussion item and tags people. you could use something like this with the first step being checking the build status list as appropriate.

You seem to be knowledgeable in this @ryjones, right? Would you be willing to take on doing such automation? As to which sub projects this should apply to: Only those with GOVERNANCE.md files, agreed @dstebila ?


Fix webapp target name

fix swig.target.name which was being used by other swig task to construct the assets paths (e.g. public/js/{swig-target-name}), previously using the directory name. This was identified when somebody cloned the repo to a folder which had a name differing from the project name in the package.json.

@k4sbasia Fixes the issue you saw with bundling assets

:-1:  since the target name is already being set on line 130 (see commit comment), that's where it should be changed.
   var basename = path.basename(target); // obvi this should be declared up top
    swig.target = {
      path: target,
      // keeping this around bc it may be useful
      basename: basename,
      name: swig.argv.module || swig.pkg.name || basename,
      repo: swig.argv.repo || path.basename(swig.cwd)
    };

Rebased the branch in my last commit

:hamburger: :fries:


[stdlib][Part 1] De-gyb almost everything

See here: https://forums.swift.org/t/struggling-to-find-things-in-the-new-stdlib-for-5-0-e-g-where-is-addingreportingoverflow-implemented/18612/7
This is part 1 in a 4 part series.
This removes most .gyb files from the stdlib. Commits titled de-gyb ... are the product of copying and pasting the de-gybbed version over. I have a post de-gyb formatting commit that cleans up some of the messy formatting from gyb.
cc: @airspeedswift @stephentyrone @lorentey @xwu

@airspeedswift and I just talked about this briefly. We'd like to do this, but want to be a bit more gradual about it. In particular, Ben wants to keep the .gyb files around (because they're better for editing--at least once you're used to them), but add a test that validates that the result of expanding the gyb matches the non-gyb source.
In cases where there isn't too much duplication, removing gyb entirely makes sense, but we should do those one file-per-commit, I think.

Understandable. I read "all in" from Ben and I was ready to go "all in" 😅 I imagine we might one day get around to de-gybbing IntegerTypes which might allow us to break up the integers into separate files, Int8.swift, Int16.swift, etc. How would we go about testing this split in files with IntegerTypes.swift.gyb? (Assuming we want to do something like that instead of just testing against a IntegerTypes.swift with everything in it)

@Azoy let's leave IntegerTypes and FloatingPointTypes alone for the time being, since they're a bit more involved than the others (but: we would simply run the test multiple times with different arguments to validate).
I think the other thing worth doing here is either to more clearly document how to generate the .swift files from the .swift.gyb (probably via a comment line at the top the .gyb file that has exactly the required invocation(s)).

which might allow us to break up the integers into separate files, Int8.swift, Int16.swift

I'd rather leave them all in one big file than clutter the folder with lots of near-identical files. The goal of degybbing is to improve search ability of the source code (the "where on earth is xxx declared" question on the forum that led to this idea), to allow stepping through the std lib, allow an LSP server to parse the whole std lib etc, all of which works from the single file approach. These files are probably rarely going to be touched in future so making them easier to navigate/read for editing purposes isn't that important.

I only bring up splitting them up because the gyb file itself is almost 2k LoC, and a single ungybbed IntegerTypes.swift would be about 20k LoC. Some editors/IDEs/github even would have some trouble handling a buffer that large which might decrease ability to efficiently search for source code.

@Azoy @airspeedswift Also worth noting that as the generics story and compiler optimizations get better, we can move progressively more and more integer stuff out of gyb and into default implementations, so the gyb piece will gradually get smaller.

While looking for gyb comments in ExistentialCollection.swift, I made some more minor formatting changes which might need a quick review.

@Azoy Could you rebase this one more time?

@CodaFi I've successfully rebased! @airspeedswift @stephentyrone I know it's been a WHILE, but I would love another look to make sure this is good to go!

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 861e0f79a63884bce7b5e4f96eb81153cfdeec34

@CodaFi sigh sorry bout that one... it should be good now.

It happens. Let’s give it another go.

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - c9966192a45f01871072e2576571f754fef27a2d

Ignore the macOS result. There’s an infrastructure problem here.

@CodaFi I've rebased and now this should be ready.

@swift-ci please test

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 0a1c30e9655d9d67738f4e65c0a0835831b8e174

macOS failure unrelated?

Ugh, infrastructure failure.  Let's try again
@swift-ci please test macOS platform

Build failed
Swift Test OS X Platform
Git Sha - 0a1c30e9655d9d67738f4e65c0a0835831b8e174

Another infrastructure problem again? x)

I think this one’s an actual failure

api-digester/dump-module.swift

Suggests you might have changed the ABI surface of stdlib.

The conformances of Int (to MirrorPath, CVarArg, and CustomReflectable) in the cake test module have been reordered, possibly due to your CMakeLists.txt changes.
There's a comment in dump-module.swift which might be relevant:

// The input JSON files need to be modified when standard library declarations
// are reordered. This is expected behavior and we simply shouldn't run the test
// when automatically evolving the standard library.

@benrimmington thanks so much for the help.
@CodaFi I've tested locally and this test passes now. We should be good to go.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 0a1c30e9655d9d67738f4e65c0a0835831b8e174

Build failed
Swift Test Linux Platform
Git Sha - 0a1c30e9655d9d67738f4e65c0a0835831b8e174

@CodaFi all tests have passed!

⛵


Master

I might be overlooking it, but I don't see anything new in here. Is this maybe just a failed rebase?

Actually I didn't mean to send that through was showing a friend how to use github and didn't mean to send that
On Nov 29, 2015 2:43 PM, tcld<EMAIL_ADDRESS>wrote:I might be overlooking it, but I don't see anything new in here. Is this maybe just a failed rebase?
—Reply to this email directly or view it on GitHub.

Well, then you might want to show your friend how to close a PR, too.^^

Hi @pow450 these things happen :) I am closing this PR but I hope in the future you will want to collaborate on WorldEngine! Enjoy GitHub


MAKE.EXE hangs on circle target

Hi!
Put this to MAKEFILE and run MAKE.EXE.
all: all

Make will run forever now.
Cheers,
Robert

Thanks, Robert!
Looks like a "make-bomb" :-))
I'll fix it.
PS: This is just a brainless toy-tool for >= 386 PC (and great possibility for dinosaurs)

Fix is ready. I'll play with this version in my local env (i want see possible side-effects, i think one week) and then - push it to git.


Potential Logic Error in UCOB - UCU Nael Fireball 4

Hello beautiful people,
Please refer to this trigger:
https://github.com/quisquous/cactbot/blob/triggers/04-sb/ultimate/unending_coil_ultimate.js#L876
On Nael's fourth fireball, if I took three fireballs, I would expect to get an alert text telling me to avoid the 4th fireball. However, in the video below, I did not get such an alert text. (Note: I am overriding that trigger, however, that aspect of it should not be affected.)
However, I believe I understand why this trigger is not working... I think data.tookThreeFireballs (the variable which drives the alert text) will never be populated because preRun() runs before delaySeconds().
If I understand the fireball triggers correctly, because the target of the tether cannot (currently) be calculated, four triggers listen to an event near the beginning of the phase, and set a delay from there, one for each tether at a predetermined interval. Since, at the time of this initial event, zero fireballs have gone out, and since preRun() runs before delaySeconds(), I would therefore think that it is impossible for data.tookThreeFireballs to be populated at this time.
Video: https://drive.google.com/file/d/1KqBSlkMp_Rw0Jjct9VufqQg3wuBOrXlc/view?usp=sharing
Log: https://drive.google.com/file/d/1v_IBjWQ2p_JixkgNBJGIq83WuB0vgMLN/view?usp=sharing
User file: https://drive.google.com/file/d/1gJxqLv5lL8St-Vl1ZP0io9caw0H14tVW/view?usp=sharing
That's all I got! Thank you very much for your time,
Data

Your assessment makes sense, and seems to be right. I used the log you provided (thank you!) in the emulator and it appears to be fixed with the suggested change.


fix: remove keep_history for docs github action

Removes all previously built files in gh-pages and pushes the latest ones.
Fixes the issue where old docs files are still accessible

Will merge this later, but going to keep the old pages for a bit with a warning saying about the new docs

merged here https://github.com/MirageNet/Mirage/commit/2a2a8a54a992104f95dfc243aa29fc3465c71cb6


Json fillable not working properly

Laravel Version
11.34.2
PHP Version
8.3.10
Database Driver & Version
MySQL 8
Description
protected $fillable = [
    'name',
    'email',
    'data',
    'password',
    'data->some_value'
];

No matter what keys I allow for the data field, they will be successfully added, ignoring $fillable.
Steps To Reproduce

Clone repo https://github.com/projct1/laravel-json-casts
Change key (or add) in $fillable in User model from data to data->allowed_field
Run php artisan migrate
Run php artisan serve
Open link.

And you will see that the key which is not specified in $fillable will be added successfully.

protected $fillable = [
    'data', // This means you can assign any value to `data`, including `custom_value`.
    'data->some_value',
];

You should remove data from fillable if you want to be strict.

protected $fillable = [
    'data', // This means you can assign any value to `data`, including `custom_value`.
    'data->some_value',
];

You should remove data from fillable if you want to be strict.

In this case, the field is ignored completely, even when a specific key is allowed. Just try:
protected $fillable = [
    'name',
    'email',
    'data->custom_value',
    'password',
];

App\Models\User::create([
    'name' => 'Test',
    'email' =><EMAIL_ADDRESS>    'password' => Hash::make('password'),
    'data' => [
        'custom_value' => 1
    ]
]);

As result will be this, data ignored completely despite $fillable allowing custom_value:
{
"name": "Test",
"email"<EMAIL_ADDRESS>"updated_at": "2024-12-11T12:13:35.000000Z",
"created_at": "2024-12-11T12:13:35.000000Z",
"id": 2
}

@crynobone Dude, can you check again plz? I commented above.


Update version to v0.7.0 of cert-manager

0.7.0 is not aailable in any of the chart repos when installing and enabling cluster wide TLS causing


Unpermitted parameters | configure_permitted_parameters

+1 https://github.com/lynndylanhurley/devise_token_auth/issues/897
devise (4.3.0)
devise_token_auth (0.1.42)
class ApplicationController < ActionController::API
  include DeviseTokenAuth::Concerns::SetUserByToken
  before_action :configure_permitted_parameters, if: :devise_controller?
  respond_to :json

  protected

  def configure_permitted_parameters
    devise_parameter_sanitizer.permit(:sign_up, keys: [:name])
  end
end

It's still not working here.
Any solution?

Hi there @aristeuroriz    ,
In an effort to cleanup this project and prioritize a bit, we're marking issues that haven't had any activity in a while with a "close-in-7-days" label. If we don't hear from you in about a week, we'll be closing this issue. Obviously feel free to re-open it at any time if it's the right time or this was done in error!
If you are still having the issue (especially if it's a bug report) please refer to our new Issue Template to provide some more details to help us solve it.
Hope all is well.

@aristeuroriz  can you tell when you are getting the error, in response?


Update now that boot2docker is deprecated?

This needs an update because boot2docker is no longer supported by the docker team.  Tried with "docker-machine start" syntax but something is broken.  I'd actually prefer not to have Maven to all kinds of magic for me.  I'm anxious to use compute / managed vm capabilities in the Google Cloud offering.

What is broken for you?
On Sun, Oct 4, 2015 at 9:55 AM, unitydynamics<EMAIL_ADDRESS>wrote:

This needs an update because boot2docker is no longer supported by the
docker team. Tried with "docker-machine start" syntax but something is
broken. I'd actually prefer not to have Maven to all kinds of magic for me.
I'm anxious to use compute / managed vm capabilities in the Google Cloud
offering.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/appengine-java-vm-guestbook-extras/issues/16
.

Did you check the Docker web site?  The Java walkthrough for Managed VMs is
essentially broken now....  I will attempt to use Managed VMs with Java
again today and let you know where I get stuck today or tomorrow.
On Mon, Oct 5, 2015 at 10:45 AM, ludovic Champenois <
<EMAIL_ADDRESS>wrote:

What is broken for you?
On Sun, Oct 4, 2015 at 9:55 AM, unitydynamics<EMAIL_ADDRESS>wrote:

This needs an update because boot2docker is no longer supported by the
docker team. Tried with "docker-machine start" syntax but something is
broken. I'd actually prefer not to have Maven to all kinds of magic for
me.
I'm anxious to use compute / managed vm capabilities in the Google Cloud
offering.
—
Reply to this email directly or view it on GitHub
<
https://github.com/GoogleCloudPlatform/appengine-java-vm-guestbook-extras/issues/16
.

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/appengine-java-vm-guestbook-extras/issues/16#issuecomment-145552642
.

Lodovic I respectfully plead for your help.  I've spent the entire day
trying to get the tutorial running again. I recognize that you probably
don't use Windows 7 SP1 and that's the reason for most of my pain I'm sure.
On the guest book demo this is where I'm stuck now (Deploy Your
Application-- stage 1):
https://github.com/GoogleCloudPlatform/appengine-java-vm-guestbook-extras#deploy-your-application
So I have managed to build and run it locally just fine. The error when
deploying is "ERROR: (gcloud.preview.app.deploy) Unable to copy
certificates."  I've traced this to line 158 of docker_util.py.  Not sure
what I need to do to fix this situation though.  I tried taking out the
--quiet flag from the gcloud invocation but that didn't help.  Also read this
related posting
https://groups.google.com/forum/#!topic/google-appengine-go/oCvmx_x9HOs
but that didn't seem to help either.  I have made sure I tried "gcloud auth
login" and "gcloud compute config-ssh" before deployment... didn't help.
Attached is the full log from gcloud:deploy.  I believe I'm running the
latest version of everything.  Any help greatly appreciated.
-Robert Fox
demo version
ce06167af010be753aabeecb280a2ff4b473379b
https://github.com/GoogleCloudPlatform/appengine-java-vm-guestbook-extras
gcloud version
Google Cloud SDK 0.9.88
app-engine-java 1.9.28
app-engine-php
app-engine-php-windows 2015.11.16
app-engine-python 1.9.28
beta 2015.10.08
bq 2.0.18
bq-win 2.0.18
core 2015.11.25
core-win 2015.11.24
gcloud
gsutil 4.15
gsutil-win 4.15
windows-ssh-tools 2015.09.21
Separate note....
Also just FYI I've tackled a few hurdles that are not documented in the
tutorial... maybe this can be my contribution to the
documentation...Windows 7 specific?

I added the following to the pom.xml

<gcloud_directory>C:\Program Files (x86)\Google\Cloud
SDK\google-cloud-sdk</gcloud_directory>
<gcloud_project>app-id</gcloud_project>

I didn't change the default directory when I installed the Cloud SDK....
C:\Program Files (x86)... is where it will install by default.  I believe
the defaults assume the Cloud SDK is installed to C:\Program Files...
(without the (x86)).

To run gcloud:deploy I had to add<EMAIL_ADDRESS>in
the Permissions section on my account.

On Thu, Nov 5, 2015 at 1:33 PM, Robert Fox<EMAIL_ADDRESS>wrote:

Did you check the Docker web site?  The Java walkthrough for Managed VMs
is essentially broken now....  I will attempt to use Managed VMs with Java
again today and let you know where I get stuck today or tomorrow.
On Mon, Oct 5, 2015 at 10:45 AM, ludovic Champenois <
<EMAIL_ADDRESS>wrote:

What is broken for you?
On Sun, Oct 4, 2015 at 9:55 AM, unitydynamics<EMAIL_ADDRESS>wrote:

This needs an update because boot2docker is no longer supported by the
docker team. Tried with "docker-machine start" syntax but something is
broken. I'd actually prefer not to have Maven to all kinds of magic for
me.
I'm anxious to use compute / managed vm capabilities in the Google Cloud
offering.
—
Reply to this email directly or view it on GitHub
<
https://github.com/GoogleCloudPlatform/appengine-java-vm-guestbook-extras/issues/16
.

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/appengine-java-vm-guestbook-extras/issues/16#issuecomment-145552642
.


Wrong type since JS-Controller 3.3

v1.0.0

synology.0
2021-08-07 14:31:22.994
info
(19060) State value to set for "synology.0.DiskStationManager.vol_info.volume_1.used_size" has to be type "number" but received type "string"

| synology.0	2021-08-05 21:47:48.906	info	(19060) State value to set for "synology.0.DiskStationManager.info.uptime" has to be type "string" but received type "number"
-- | --

Edit
Nach heutigem Neustart des Adapters sind leider noch etliche Fehlermeldungen dazugekommen
`

|   |   |
-- | -- | -- | --
synology.0 | 2021-08-08 12:00:01.275 | info | (18123) State value to set for "synology.0.DiskStationManager.vol_info.volume_1.used" has to be type "number" but received type "string"
synology.0 | 2021-08-08 12:00:01.273 | info | (18123) State value to set for "synology.0.DiskStationManager.vol_info.volume_1.total_size" has to be type "number" but received type "string"
synology.0 | 2021-08-08 12:00:01.270 | info | (18123) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_4.capacity" has to be type "number" but received type "string"
synology.0 | 2021-08-08 12:00:01.267 | info | (18123) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_4.ebox_order" has to be type "string" but received type "number"
synology.0 | 2021-08-08 12:00:01.240 | info | (18123) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_3.capacity" has to be type "number" but received type "string"
synology.0 | 2021-08-08 12:00:01.234 | info | (18123) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_3.ebox_order" has to be type "string" but received type "number"
synology.0 | 2021-08-08 12:00:01.220 | info | (18123) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_2.capacity" has to be type "number" but received type "string"
synology.0 | 2021-08-08 12:00:01.213 | info | (18123) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_2.ebox_order" has to be type "string" but received type "number"
synology.0 | 2021-08-08 12:00:01.023 | info | (18123) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_1.capacity" has to be type "number" but received type "string"
synology.0 | 2021-08-08 12:00:01.013 | info | (18123) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_1.ebox_order" has to be type "string" but received type "number"
synology.0 | 2021-08-08 12:00:01.008 | info | (18123) State value to set for "synology.0.DiskStationManager.info.upgrade_ready" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 12:00:01.005 | info | (18123) State value to set for "synology.0.DiskStationManager.info.is_system_crashed" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 12:00:01.000 | info | (18123) State value to set for "synology.0.DiskStationManager.info.memory_size" has to be type "string" but received type "number"
synology.0 | 2021-08-08 11:59:46.609 | info | (18123) State value to set for "synology.0.FileStation.info.uid" has to be type "string" but received type "number"
synology.0 | 2021-08-08 11:59:46.604 | info | (18123) State value to set for "synology.0.FileStation.info.support_virtual.enable_remote_mount" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 11:59:46.603 | info | (18123) State value to set for "synology.0.FileStation.info.support_virtual.enable_iso_mount" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 11:59:46.602 | info | (18123) State value to set for "synology.0.FileStation.info.support_vfs" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 11:59:46.601 | info | (18123) State value to set for "synology.0.FileStation.info.support_sharing" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 11:59:46.600 | info | (18123) State value to set for "synology.0.FileStation.info.support_file_request" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 11:59:46.599 | info | (18123) State value to set for "synology.0.FileStation.info.items.2" has to be type "string" but received type "object"
synology.0 | 2021-08-08 11:59:46.598 | info | (18123) State value to set for "synology.0.FileStation.info.items.1" has to be type "string" but received type "object"
synology.0 | 2021-08-08 11:59:46.596 | info | (18123) State value to set for "synology.0.FileStation.info.items.0" has to be type "string" but received type "object"
synology.0 | 2021-08-08 11:59:46.596 | info | (18123) State value to set for "synology.0.FileStation.info.is_manager" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 11:59:46.594 | info | (18123) State value to set for "synology.0.FileStation.info.enable_list_usergrp" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 11:59:46.591 | info | (18123) State value to set for "synology.0.DiskStationManager.info.temperature_warn" has to be type "string" but received type "boolean"
synology.0 | 2021-08-08 11:59:40.909 | info | (18123) Connecting to Synology <IP_ADDRESS>:5000
synology.0 | 2021-08-08 11:59:40.858 | info | (18123) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.synology, node: v12.22.2, js-controller: 3.3.15

`

hier auch

fixed in 1.1.1

I'm sorry, but after updating to v1.1.1, the same log entries sometimes appear again.
I stopped the adapter and deleted all data points on the objects. The v1.1.1. installed via GitHub Link over it and restarted the adapter 2x. What did 1 wrong?
`

synology.0
2021-08-09 11:48:00.704
info
(30961) State value to set for "synology.0.DiskStationManager.vol_info.volume_1.used_size" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.654
info
(30961) State value to set for "synology.0.DiskStationManager.vol_info.volume_1.total_size" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.653
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_4.capacity" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.648
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_4.ebox_order" has to be type "string" but received type "number"

synology.0
2021-08-09 11:48:00.646
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_3.capacity" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.645
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_3.ebox_order" has to be type "string" but received type "number"

synology.0
2021-08-09 11:48:00.640
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_2.capacity" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.639
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_2.ebox_order" has to be type "string" but received type "number"

synology.0
2021-08-09 11:48:00.631
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_1.capacity" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.630
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_1.ebox_order" has to be type "string" but received type "number"

synology.0
2021-08-09 11:48:00.624
info
(30961) State value to set for "synology.0.DiskStationManager.info.upgrade_ready" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:48:00.623
info
(30961) State value to set for "synology.0.DiskStationManager.info.is_system_crashed" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:48:00.621
info
(30961) State value to set for "synology.0.DiskStationManager.info.memory_size" has to be type "string" but received type "number"

synology.0
2021-08-09 11:47:42.968
info
(30961) State value to set for "synology.0.FileStation.info.uid" has to be type "string" but received type "number"

synology.0
2021-08-09 11:47:42.966
info
(30961) State value to set for "synology.0.FileStation.info.support_virtual.enable_remote_mount" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.964
info
(30961) State value to set for "synology.0.FileStation.info.support_virtual.enable_iso_mount" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.963
info
(30961) State value to set for "synology.0.FileStation.info.support_vfs" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.962
info
(30961) State value to set for "synology.0.FileStation.info.support_sharing" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.961
info
(30961) State value to set for "synology.0.FileStation.info.support_file_request" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.959
info
(30961) State value to set for "synology.0.FileStation.info.items.2" has to be type "string" but received type "object"

synology.0
2021-08-09 11:47:42.958
info
(30961) State value to set for "synology.0.FileStation.info.items.1" has to be type "string" but received type "object"

synology.0
2021-08-09 11:47:42.925
info
(30961) State value to set for "synology.0.FileStation.info.items.0" has to be type "string" but received type "object"

synology.0
2021-08-09 11:47:42.918
info
(30961) State value to set for "synology.0.FileStation.info.is_manager" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.916
info
(30961) State value to set for "synology.0.FileStation.info.enable_list_usergrp" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.914
info
(30961) State value to set for "synology.0.DiskStationManager.info.temperature_warn" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:41.584
info
(30961) DSM 6

synology.0
2021-08-09 11:47:36.166
info
(30961) Connecting to Synology <IP_ADDRESS>:5000

synology.0
2021-08-09 11:47:36.060
info
(30961) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.synology, node: v12.22.2, js-controller: 3.3.15

synology.0
2021-08-09 11:47:12.205
info
(24661) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

`


Plugin creates separate Poetry environment, although one already exists

Describe the bug
The plugin seems to be creating a separate environment, even though a Poetry environment already exists.
This is probably related to bug #287 and to https://github.com/python-poetry/poetry/issues/2419 where it may be using a different case or different path
To Reproduce
Have a terminal with color codes, either ConEmu, Windows Terminal and enable clink and Powerline stuff for Windows
Expected behavior
The existing environment should be used, another one should not be created.
Screenshots

The dtt-swC1WwXO-py3.9 is created by Poetry PyCharm plugin, dtt-xc0anUwY-py3.9 is created and used by Poetry itself.
Environments (please complete the following information):

IDE: PyCharm Professional 2021.2.2
OS: Windows 10 x64
Poetry Version 1.1.11
Plugin version : latest master

Additional context
I've tried modifying the runPoetry function to add some environment variables to disable colors, but that didn't work for me.

When the plugin is running various commands and I click on the image for more details I can see escape sequences at the start of the commands, so I think that the output from Poetry command line has escape sequences and it messes with the plugin.

I would say that everybody using escape codes (on Windows) is affected. How can I/we raise an issue there ?


where and what is the preprocessing code exactly?

I have no idea about this even I open https://github.com/moses-smt/mosesdecoder/tree/master/scripts.

Use tokenizer/tokenizer.perl and tokenizer/lowercase.perl


dashing start throwing errors

Hi,
I have install ruby 2.1 with rvm,  but while starting dashing throwing below errors, please  let me know how to fix this.
[root@localhost monitorama]# dashing start
/usr/local/rvm/gems/ruby-2.1.0/gems/execjs-2.0.2/lib/execjs/runtimes.rb:51:in autodetect': Could not find a JavaScript runtime. See https://github.com/sstephenson/execjs for a list of available runtimes. (ExecJS::RuntimeUnavailable) 	from /usr/local/rvm/gems/ruby-2.1.0/gems/execjs-2.0.2/lib/execjs.rb:5:in module:ExecJS'
from /usr/local/rvm/gems/ruby-2.1.0/gems/execjs-2.0.2/lib/execjs.rb:4:in <top (required)>' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require'
from /usr/local/rvm/gems/ruby-2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require_with_backports' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/coffee-script-2.2.0/lib/coffee_script.rb:1:in <top (required)>'
from /usr/local/rvm/gems/ruby-2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require_with_backports'
from /usr/local/rvm/gems/ruby-2.1.0/gems/coffee-script-2.2.0/lib/coffee-script.rb:1:in <top (required)>' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require'
from /usr/local/rvm/gems/ruby-2.1.0/gems/backports-3.6.8/lib/backports/std_lib.rb:9:in require_with_backports' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/dashing-1.3.4/lib/dashing/app.rb:5:in <top (required)>'
from /usr/local/rvm/gems/ruby-2.1.0/gems/dashing-1.3.4/lib/dashing.rb:3:in require' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/dashing-1.3.4/lib/dashing.rb:3:in <top (required)>'
from config.ru:1:in require' 	from config.ru:1:in block in '
from /usr/local/rvm/gems/ruby-2.1.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in instance_eval' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/rack-1.5.5/lib/rack/builder.rb:55:in initialize'
from config.ru:1:in new' 	from config.ru:1:in '
from /usr/local/rvm/gems/ruby-2.1.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:33:in eval' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/thin-1.6.4/lib/rack/adapter/loader.rb:33:in load'
from /usr/local/rvm/gems/ruby-2.1.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:182:in load_rackup_config' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/thin-1.6.4/lib/thin/controllers/controller.rb:72:in start'
from /usr/local/rvm/gems/ruby-2.1.0/gems/thin-1.6.4/lib/thin/runner.rb:200:in run_command' 	from /usr/local/rvm/gems/ruby-2.1.0/gems/thin-1.6.4/lib/thin/runner.rb:156:in run!'
from /usr/local/rvm/gems/ruby-2.1.0/gems/thin-1.6.4/bin/thin:6:in <top (required)>' 	from /usr/local/rvm/gems/ruby-2.1.0/bin/thin:22:in load'
from /usr/local/rvm/gems/ruby-2.1.0/bin/thin:22:in <main>' 	from /usr/local/rvm/gems/ruby-2.1.0/bin/ruby_executable_hooks:15:in eval'
from /usr/local/rvm/gems/ruby-2.1.0/bin/ruby_executable_hooks:15:in `'

You need a JavaScript runtime of some sort, probably just install NodeJS. therubyracer gem is another option to look into.
Previous answer: https://github.com/Shopify/dashing/issues/20

thx working fine now


Fix switch fall-through warning

Clang with -Wimplicit-fallthrough enabled shows a warning here without
the break. See http://clang.llvm.org/docs/AttributeReference.html#fallthrough-clang-fallthrough

Thanks!


Add physical properties to mbari_wec model

I've put properties from François in a spreadsheet. These should be added to the mbari_wec model and/or accounted for in plugins.
mbari_wec_properties.xlsx

Thanks for compiling and sharing this!
Making sure if I'm reading the values correctly, the added mass (closed/open) is in z-direction right? Also could you please help me identify the individual terms of Inertia (kg*m^2).

I'm going to work on the Inertia, weight and CoG properties for all links in a standalone PR now. It would help me with #26 so I can work with more realistic dynamics while updating the cable. And it should help your buoyancy efforts too, @quarkytale .

could you please help me identify the individual terms of Inertia (kg*m^2). I'm assuming its the 3x3 rotational inertia matrix with the format:

I'm going with this same assumption and will verify visually if it looks reasonable.

the added mass (closed/open) is in z-direction

correct!

3x3 rotational inertia matrix with the format:

also correct!

Some values we're currently estimating but could need more precise numbers in the future:

Piston moments of inertia
Have cone inertia without Trefoil
Trefoil inertia

For record-keeping, we've moved the CoB of the buoy a bit up to 2.46 m instead of 2.16 m in #33 so the box volume matches the shape of the buoy a bit better. We may want to tweak this in the future.


Fixes emotes and also obama.

#1863 lowercases v in tokens in createChatMessage.ts which will make all emotes go out as lowercased even if you typed out with uppercases so it won't matter what the emote menu gets wrong on casing.
Also fixes obama emote, for some reason the emote menu was putting :obama: in the text field when :obamium: is needed to actually display emote, so I just changed name so it would match the short_name and now it will work with :obama:

as i mentioned here I've already fixed this im just fixing another thing with baklava and will push my fixes after its done. the obamium -> obama change seems unnecessary

When you click it in the emote menu :obama: will show up and that isn't the correct word for it to display the emote.

When you click it in the emote menu :obama: will show up and that isn't the correct word for it to display the emote.

i didn't quite get you but go ahead and make a separate pr ill have a look into it soon


Renaming !

This is a "let's see what if" PR that rename thing, Quick&dirty, completely incomplete and full of error:

[x] Err => Outcome
[x] Err::Error => Failure
[x] Err::Failure => Invalid
[ ] Needed => Hint https://github.com/Geal/nom/issues/1365#issuecomment-903171045
[x] IResult => ParseResult
[x] ErrorKind => ParserKind
[x] VerboseErrorKind => VerboseParserKind
[x] Error => Context
[x] VerboseError => VerboseContext
[x] ParseError => ParseContext (meh)
[ ] Add PResult shortcut
[ ] Rewrite error guide
[ ] make a script to reproduce this (or mostly)
[ ] rename error module to context or outcome

Partial Fix of https://github.com/Geal/nom/issues/1356

Some diff feel very nice:
let e: ErrorKind = ErrorKind::Tag;
Err(Err::Error(Error::from_error_kind(i, e)))

to
let e: ParserKind = ParserKind::Tag;
Err(Outcome::Failure(Context::from_parser_kind(i, e)))

@Lucretiel what do you think ? there is still missing rename I think but what are you opinion for now ?

? Why close ?

I do not wish to work on nom anymore, I let my "small" PR open but this one is too much big work to keep up to date, feel free to reuse ideas/work.

I'm sorry to here that, I was personally excited to see the changes that you were pushing around for nom!
You know, this is the internet, even though there are code of conducts, they are not always easy to enforce, so some people are going to say bad things or react in a potentially offending way to you..
It shouldn't stop you from trying to do great things!

Si tu lis ce message Antoine (@Stargateur), ya une phrase que j'ai retenu d'un stage sur l'estime de soi fait il y a qq mois, qui pourrait peut-etre t'aider:

A l'extrème, il n'existe pas de paroles/réactions blessante. Elles deviennent blessante quand on les accepte / quand on les prend pour nous. Si on les bloquent, ce sont juste des paroles/réactions...

:point_right: A toi d'apprendre à bloquer les mauvaise choses :upside_down_face:


add deno target

adds a new OutputMode for Deno.
Exports and js-imports are generated like OutputMode::Web or OutputMode::Node { experimental_modules: true }.
wasm-files cannot be imported directly, so the file is read at runtime. If embedding the file as a base64 string or similar is preferable, I can try to do that.

looks like the test finally passes.
I copied the import_js example, because that way imports and exports are being tested, and modified it a little bit to include passing a string to a function.
If anything else should be tested, I can add that.

I'm not sure what would need to be done to run the test suit in deno.
Add a new file similar to crates/cli/src/bin/wasm-bindgen-test-runner/node.rs for deno and add wasm_bindgen_test_configure!(deno)?

Something like that would work, yeah, although since it's so similar to node it might be best to control with an env var rather than in the code itself. Either way though it's not the most urgent thing in the world. Running the full test suite would provide a lot of confidence that the wrapper generation here is working for all use cases, but since this is a new feature it doesn't have to do everything right out of the gate.

also all the tests use exports.foo = ... and require.

All looks great to me, thanks!

I know this has already been merged, but why does --target web not work?
Why can't you just do await init(Deno.readFileSync("path/to/foo_bg.wasm"));?

To be honest I didn't quite understand why the init function was needed and thought there were some changes to be done anyway because for Deno the file wouldn't be fetched but Deno.readFileed instead. But I just tried await init(Deno.readFileSync("path/to/foo_bg.wasm")); and it works perfectly...

maybe wasm-pack can instead have a deno target using --target web which generates a mod.ts with
// @deno-types=foo.d.ts
export * from "./foo.js";
import init from "./foo.js";
init(Deno.readFileSync(import.meta.url logic));

@jakobhellermann The init function accepts string, Request, Url, ArrayBuffer, Uint8Array, or WebAssembly.Module.
If you pass in an ArrayBuffer, Uint8Array or WebAssembly.Module then it will not fetch. This allows you to handle all of the loading yourself (such as with Deno).

maybe wasm-pack can instead have a deno target using --target web which generates a mod.ts

That won't work, because then you cannot access the exports of the Rust code:
import init, * as exports from "./foo.js";

init(Deno.readFileSync("./foo_bg.wasm")).then(() => {
    // Use exports...
});

Instead, I recommend using our Rollup plugin, which will automatically call init for you. You can customize the loading behavior like this:
rust({
    importHook: function (path) {
        return "Deno.readFileSync(" + JSON.stringify(path) + ")";
    },
})

I think it might still makes sense to have a deno target for "it works similarly to node" where it auto-inits, but perhaps the generated could could be refactored to use top-level await like @Pauan mentions so it's basically --target web but with one extra line?

@alexcrichton I'm okay with that, though I'm a bit concerned that it might create a precedent for other targets.

It's true yeah I don't want to create a proliferation of too many targets, and @Pauan if you'd like I think it's fine if we revert this and continue discussion on an issue (sorry should have consulted first!)


Update to use Suave v1.0

Awesome! Did you indeed check that those changes make it work with Suave 1.0 ?
This repo will have to be updated as well, I still need to come up with a best way to do that.
For now, we'll have to mark that all permalinks to git tags (e.g. here at the end of file) show version 0.28.1

Yes, I worked through the book with the updated code and made sure the changes worked.

Cool, can we please temporarily add (Suave 0.28.1) after every such git tag permalink? There should be 10 of them for each language. That's just to make the reader less confused

Links added


chore(fix): added files/dirs to cleanup

Preview: https://patternfly-next-pr-2699.surge.sh

:tada: This PR is included in version 2.63.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update readme.md

add MarzViteTemplate to marzban too

`### Sub Templates

ACLover by @AC-Lover
MuhammadAshouri by @MuhammadAshouri
sina by @x0sina
MarzViteTemplate by @MatinDehghanian

API

Marzban API Client by @oXIIIo
Marzban API by @sm1ky
Marzbanpy by @gunsh1p
Marzpy by @mewhrzad

🔥 Awesome Marzneshin
Sub Templates

FULL LIST by @MatinDehghanian
Template 1 by @MatinDehghanian
Template 2 by @MatinDehghanian
Template 3 by @MatinDehghanian
MarzViteTemplate(Template 4) by @MatinDehghanian
Template 5 by @MatinDehghanian
Template 6 by @MatinDehghanian
`

Please choose appropriate names for all of them. Sincerely


Unable to install environment that lists cuda-specific features when on macOS

Checks

[x] I have checked that this issue has not already been reported.

[x] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
pyproject.toml file:
[project]
name = "pixi-cuda-environment"
version = "0.1.0"
description = "Add a short description here"
authors = [{name = "Eric Ma", email =<EMAIL_ADDRESS>requires-python = ">= 3.11"
dependencies = ["pandas"]

[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"

[tool.pixi.project]
channels = ["conda-forge"]
platforms = ["linux-64", "osx-arm64"]

# Feature Definitions
[tool.pixi.feature.cuda]
platforms = ["linux-64"]
system-requirements = {cuda = "12"}

[tool.pixi.feature.cuda.dependencies]
jaxlib = { version = "*", build = "*cuda12*" }

# Environments
[tool.pixi.environments]
cuda = ["cuda"]

When running pixi install, I get this error:
❯ pixi install
  × Unable to solve pypi dependencies for the cuda environment because no compatible python interpreter can be installed for the current
  │ platform
    ╭─[15:13]
 14 │ channels = ["conda-forge"]
 15 │ platforms = ["osx-arm64", "linux-64"]
    ·             ────────────┬────────────
    ·                         ╰── even though the projects does include support for 'osx-arm64'
 16 │
 17 │
 18 │ [tool.pixi.tasks]
 19 │ test = "pytest"
 20 │
 21 │ [tool.pixi.dependencies]
 22 │ ruff = ">=0.5.5,<0.6"
 23 │ pytest = ">=8.3.2,<8.4"
 24 │ ipython = ">=8.26.0,<9"
 25 │ jax = ">=0.4.28"
 26 │ pytest-cov = ">=5.0.0,<6"
 27 │
 28 │ # Feature Definitions
 29 │ [tool.pixi.feature.cuda]
 30 │ platforms = ["linux-64"]
    ·             ──────┬─────
    ·                   ╰── feature 'cuda' does not support 'osx-arm64'
 31 │ system-requirements = {cuda = "12"}
    ╰────
  help: Try converting your [pypi-dependencies] to conda [dependencies]

Issue description
It appears that I cannot install environments when I specify my pyproject.toml as above.
My goal is to support both osx-arm64 and linux-64 environments, and I want the CUDA environment to be installed only on linux-64. An additional requirement is that my project is also a distributable Python package, and I need to be able to specify dependencies in the project.dependencies section rather than tool.pixi.dependencies section, so that when others pip-install the package they can also pull in the necessary dependencies.
Expected behavior
Based on my mental model, pixi should have just proceeded with the install. After all, I have defined the cuda feature to be linux-64 only!

I'll note that when I move the dependencies to the from the project table to the tool.pixi.dependencies table, solving works, but this means my project no longer can be reliably distributed to across macOS, linux(+CUDA), and linux(-CUDA) as a pypi-installable package.

(Apologies for many posts, I'm quite literally thinking while writing on issue trackers.)
I realize I have a self-contradiction here based on my own dependency specification. Runtime dependencies, which are what I desire to pull in from pypi, should be specified under the [project] table, and this will include jaxlib. In other words, I need to separate out the [cuda] dependencies via optional dependencies rather than by pixi, I think.

Hey @ericmjl, thanks for your report. This issue is well known and we've actually just prepared a design to conquer this: https://github.com/prefix-dev/pixi/issues/1340
If you that correctly fixes your issue, could you then close this issue in favor of that?


Openseadragon with openSeaDragonFabricJsoverlay plugin issue on rotate with drawer annotation

am using openseadragon , openseadragonfabricoverlay plugin, I have successfully integrate with angular 10 its working fine. I can draw rectangle, circle, line, polyline , etc.., on the images, and also panning, zooming is working excellent with annotation, but the issue is rotate the select single tile (image)  from multiple images with  annotation like rectangle, circle, etc.. when rotating the image the annotation is not  positioned correctly.

how to get center point for each images for rotation.

--> please help resolve this issue, and if you have and example code regarding this issue please forward the link
Note: I can able to rotate single image tile with annotation, its working fine

Looks like this issue might be relevant: https://github.com/altert/OpenseadragonFabricjsOverlay/issues/9


[WIP] MVP Metrics Explorer leaderboard component

This WIP implements the basic leaderboard components:

anyone can check this out if they have a duckdb db with interesting tables in it. See ./scripts/dev/generate-leadeboards.js to generate data based off of an existing duckdb database, looking at the VARCHAR columns and essentially treating them as dimensions. This will give you the count(*) metric for these leaderboards.
this PR has a basic storybook view if you generate the data. Go to localhost:3000/dev/leaderboard/basic to see.

What is primarily implemented is the component design. It is meant to have these features:

the container components – these are the "shells" where we can add actual functionality.
a "big bar" underlay on each LeaderboardListItem. This should give some visual indication of "how big" the metric value is.

Remaining work:

[ ] get a design review on basic component functionality. This should be metabolizing most of what we talked about during the all-hands.
[x] fix the basic "other values"  / "hidden selected value" design & interactions.
[ ] design the tooltips.
[ ] bring in Inter in this PR. I don't think we should be shipping a monospace version of the leaderboards.

Out of scope:

doesn't implement the masonry flow. Given that it's just using CSS grid, there may be some noticeably weird perf issues. This is due to how grid works, not how these components work. So please bear with what's here.
this PR doesn't implement any humanizing formatting here. This will be done in a follow up.

Main feedback so far:

don't make gray bars disappear
what does a bar actually represent? need to make this crisper.
hard to get a sense of what the bar is in relation to., exactly. Would be good for us to have a non-count metric: a sum of some kind and an average. That should cover the range of possibilities.

This PR has been superceded; closing


WIP: socket IO support

This is a start, we need more sugaring, but we need to dig deeper inside library behaviour. Ugly hack to parse json, then print, then parsing again... But circe is definitely better! @mukel

The wrapper is nice, except that it JSON-parses None as "null". I tried again but I couldn't manage to call other function than "peer" (e.g. getroom). Did you succeed with other methods?

I managed to implement all models and a few methods; can post and receive messages to rooms.
Started working on a barebones /speakup command.

I'll give priority to finishing and shipping "member search" and put this on hold FTM.


More pythonic

I closed the last pull request and corrected a mistake

@tttturtle-russ 我们是不是先 merge 到 refactor 分支上面？

可以，但这个PR审核起来有点麻烦，我晚上找个时间看一下

The code looks fine. But you need to rename the my_module.py to another good name, also reopen a new pr, and set the target branch to factor instead of master


API refreshVersions.rejectVersionIf { ... }

About #343
Sometimes hundreds of dev versions are proposed by refreshVersions
It's what I had implemented in the Gradle Versions plugin
and it works well there
https://github.com/ben-manes/gradle-versions-plugin

I don't think this is the right design route because it makes it easy to filter all dependencies, potentially throwing the baby out with the bath water.
Also, regarding the example, it's important to note that we have a built-in way to know the stability level of a version.
Let's talk about it later and write all the options we could provide so we make.

Yup, let's talk about it and see what are the use cases for such a feature

@LouisCAD have a look at the updated PR, I improved the design and find it both simple and powerful
The filter is now not only declared but also implemented
I've tried it out on the kotlin-libraries-playground  https://github.com/LouisCAD/kotlin-libraries-playground/commit/e3838f16bb0cda35caadad030b8198742ff12bfb

One thing we could do is automatically add a comment in the versions.properties when there's code affecting the versions "acceptance".
For example:
## NOTE: Some versions are filtered by the rejectVersionsIf predicate. See the settings.gradle.kts file.

The .kts part would be dropped if we see the settings file is using Groovy DSL.
That way, people won't be surprised about versions not showing up, even if they just landed in the project.

I'm fine with that!
On July 29, 2021, Louis CAD @.***> wrote:

One thing we could do is automatically add a comment in the
versions.properties when there's code affecting the versions
"acceptance".
For example:
NOTE: Some versions are filtered by the rejectVersionsIf predicate.
See the settings.gradle.kts file.
The .kts part would be dropped if we see the settings file is using
Groovy DSL.
That way, people won't be surprised about versions not showing up,
even if they just landed in the project.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/jmfayard/refreshVersions/pull/347#issuecomment-
889228668>, or unsubscribe
<https://github.com/notifications/unsubscribe-
auth/AADQFSHXZINZW7D22LAFSD3T2FVSJANCNFSM443KE73Q>.

@LouisCAD Thinking about it it might be better to put the warning in the console log instead of the header.
As you said the header is only read once when it changes. If multiple people work on a project, only one will see the change, versus everyone if it's in the console log.
Also I'm pretty sure I can give the number of filtered versions instead of saying "some versions"
NOTE: 172 versions are filtered by the rejectVersionsIf predicate. See the settings.gradle.kts file.

@jmfayard I didn't say only one person would see it, I said once you see it in a project, you ignore it for next times.
I also think logs are more likely to be ignored than a comment, which can also be seen into the git diff.
I think adding a comment as I initially suggested is very important, and an informational or warning log could be a good addition if it tells how many version entries are affected, and how many newer versions are filtered out (as you implied with your example). That'd make it easy to spot if the predicate affects more version entries than expected.

@LouisCAD I've implemented both the file comment and the log comment, ready to review

I added the docs, this is ready to merge IHMO @LouisCAD


cargo binstall not working with prereleases of the CLI

Problem
Cargo binstall should allow us to pull down alpha versions of the CLI. However, the release flow we have setup isn't pushing the CLI artifact up. This should be an easy-enough fix, and something we can test when cutting the 0.5.0-alpha.1 release.
Environment:

Dioxus version: [e.g. v0.17, master]
Rust version: [e.g. 1.43.0, nightly]
OS info: [e.g. MacOS]
App platform: [e.g. web, desktop]

Questionnaire

[ ] I'm interested in fixing this myself but don't know where to start
[x] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

Fixed!


Modsecurity is not compiling (bool modsecurity::Utils::GeoLookup::lookup Error)

Describe the bug
Modsecurity is not compiling
Logs and dumps
utils/geo_lookup.cc: In member function ‘bool modsecurity::Utils::GeoLookup::lookup(const string&, modsecurity::Transaction*, std::function<bool(int, const std::__cxx11::basic_string<char>&)>) const’:
utils/geo_lookup.cc:124:32: error: invalid conversion from ‘const MMDB_s*’ to ‘MMDB_s*’ [-fpermissive]
         r = MMDB_lookup_string(&mmdb, target.c_str(), &gai_error, &mmdb_error);
                                ^~~~~
In file included from ../src/utils/geo_lookup.h:22,
                 from utils/geo_lookup.cc:25:
/usr/local/include/maxminddb.h:204:66: note:   initializing argument 1 of ‘MMDB_lookup_result_s MMDB_lookup_string(MMDB_s*, const char*, int*, int*)’
     extern MMDB_lookup_result_s MMDB_lookup_string(MMDB_s *const mmdb,
                                                    ~~~~~~~~~~~~~~^~~~
make[3]: *** [Makefile:3119: utils/libmodsecurity_la-geo_lookup.lo] Error 1
make[3]: Leaving directory '/root/ModSecurity/src'
make[2]: *** [Makefile:3413: all-recursive] Error 1
make[2]: Leaving directory '/root/ModSecurity/src'
make[1]: *** [Makefile:1200: all] Error 2
make[1]: Leaving directory '/root/ModSecurity/src'
make: *** [Makefile:1027: all-recursive] Error 1

To Reproduce
Compile it from source
git clone --depth 1 -b v3/master --single-branch https://github.com/SpiderLabs/ModSecurity
			cd ModSecurity
			git submodule init
			git submodule update
			./build.sh
			./configure
			make
			make install

Used, above command from this script: https://github.com/OptimBro/OptimStack/blob/master/OptimStack.sh
Expected behavior
A clear and concise description of what you expected to happen.
Server (please complete the following information):

ModSecurity version (and connector): latest
WebServer: [N/A]
OS (and distro): [e.g. Debian 10]

Additional context
Guess: MaxMind has stopped providing GEOIP files, now asking for license and key, that could be the problem, if ModSecurity uses it, I guess. I can see in the above logs.
PS: I'm not good at reporting bugs, so pardon me, if I presented in an unprofessional way.
Thanks :)

I think (if you definietly want to use the current master) you have to replace this line with
LIBMAXMINDDB_VER=1.4.2

Looks like the ABI had changed in libmaxminddb in version 1.4.2, and there is an affected change which caused this error.
Another solutions: use 3.0.4, or go back to cd9b8a:
git checkout cd9b8a

(The next commit is 4f13fe, which makes const the lookup() method.)
@zimmerle - it would be good to collect and listed the minimal library versions. There isn't any information about this.

Hi @OptimBro,
That is happening because of you may have an outdated version of lbmaxmind. You may want to use the latest version for libmaxmind. If upgrade is not an option, you may want to disable the libMaxMind dependency using --with-maxmind=no.

hello,
just upgraded to the latest nginx 1.17.10 and had to recompile. Same problem

Hi @albgen,
Make sure you have the newest version of ModSecurity.
Check the advise that was stated above: upgrade your libmaxmind or try to disable it by using --with-maxmind=no as ./configure option.

Hi zimmerle,
Yes, i compiled removing the libmaxmind library.
Thanks


Add python scripts to install Premake

Describe the issue (if no issue has been made)
This PR doesn't fix any issue.
This PR adds a python script to check and automatically download Premake5.exe if the file is not presented.
PR impact
List of related issues/PRs this will solve:

Impact
Issue/PR

Issues this solves
None

Other PRs this solves
None

Proposed fix
Another script, Premake.py, is called during setup. It will check if Premake5.exe is presented in the specified vendor/premake/bin directory. If the file is not presented, it will attempt to download from the specified URL and extract the file here.
Additional context
Currently, the script will attempt to download v.5.0.0-alpha16 (which is the latest) Windows version of Premake.
Since I don't own any other platform, I can not test on them. Theoretically the script should works on other platform as well.
I have put a platform check so currently the script only try to download Premake if you are on Windows, so if you are running Hazel on other platform, you need to remove the checking first before running the script.

I don't think this is necessary for Linux (and Mac, maybe?). Since we have package managers, installing premake is as easy as:
# pacman -S premake

or
# apt-get install premake

Maybe throw an error if premake is not on the user's path? let them know that they should have it installed?

I am wondering why we need to install premake on windows? We just use premake without installation? The only think that could be checked is if the exe is present (as in the repository is cloned recursively)... Am I wrong?

Premake is not a submodule, so the exe should be preset even with a shallow clone. (unless if the user has deleted it, in that case it's their problem!).

Ah yes, my bad! I don't think this PR is a bad thing, as people dislike having binaries inside github... For that matter, I believe it would be nice to have such a script to run in the setup (since we have that now).
I won't merge it yet, as I do want to refactor some of the setup script as of now, since it is quite messy.

Sorry for late reply.

Ah yes, my bad! I don't think this PR is a bad thing, as people dislike having binaries inside github... For that matter, I believe it would be nice to have such a script to run in the setup (since we have that now).

I also think that binaries should not be commit along with source code, that's why I made this PR, trying to throw the binaries problem to the user.

I won't merge it yet, as I do want to refactor some of the setup script as of now, since it is quite messy.

In this PR I also follow the current setup script format. After they are refactored them I will also update the PR to match the new format.

I don't think this is necessary for Linux (and Mac, maybe?). Since we have package managers, installing premake is as easy as:
...
Maybe throw an error if premake is not on the user's path? let them know that they should have it installed?

With this approach, I'm trying to make installing Hazel one-click-only. But you're right, I forgot that Linux has package manager.
In the meantime, I will keep this code as it is. When Hazel officially supports Linux, I think this piece of code will change, or be removed.

With this approach, I'm trying to make installing Hazel one-click-only. But you're right, I forgot that Linux has package manager.

There are also third party package managers on windows (scoop, choco) and soon an official package manager (winget I think?)

I don't think this is necessary for Linux (and Mac, maybe?). Since we have package managers, installing premake is as easy as:
# pacman -S premake

or
# apt-get install premake

Maybe throw an error if premake is not on the user's path? let them know that they should have it installed?

iirc, premake5 can't be installed via package managers

iirc, premake5 can't be installed via package managers

iirc, premake5 can't be installed via package managers

If you go to https://premake.github.io/download only two options are available, either build from source. or download compressed prebuilt binaries

Because the distribution packages are probably maintained by the community and not premake's maintainers.
And, i checked. premake5 is not available on ubuntu (premake4 is though sudo apt-get install premake4), that's a bummer!
premake5 is available on Arch though.
Arch wins...Again! ( jk :) )

I won't merge it yet, as I do want to refactor some of the setup script as of now, since it is quite messy.

In this PR I also follow the current setup script format. After they are refactored them I will also update the PR to match the new format.

#438 has been merge. Please create a SetupPremake.py file similar to SetupVulkan.py to download the premake binaries to the correct location.

#438 has been merge. Please create a SetupPremake.py file similar to SetupVulkan.py to download the premake binaries to the correct location. For now I would only create a setup for windows as discussed above.

Sorry for late update.
I have just update SetupPremake.py to match other scripts.
I've tested it for a while and it seems good on my end, but please let me know if there is any problems.

This PR seems to have alot of file changes, I think something went wrong, as I see that this PR still tries to add scripts/Premake.py AND scripts/SetupPremake.py.. seems like the old files are not deleted.
Another thought I had, why does the script try to change directories twice?
https://github.com/TheCherno/Hazel/blob/9aaa6fe6da2bc2d88fdba6ae5b54087df5229eca/scripts/Setup.py#L11-L13
https://github.com/TheCherno/Hazel/blob/9aaa6fe6da2bc2d88fdba6ae5b54087df5229eca/scripts/Setup.py#L15-L19
Shouldn't it look something like
from SetupPremake import PremakeConfiguration as PremakeRequirements
from SetupVulkan import VulkanConfiguration as VulkanRequirements

os.chdir('./../') # Change from devtools/scripts directory to root

PremakeRequirements.Validate()
VulkanRequirements.Validate()

Looking at the flow of the script, I would think it has to be first installing Vulkan, then premake, and finally run the premake script?
from SetupVulkan import VulkanConfiguration as VulkanRequirements
from SetupPremake import PremakeConfiguration as PremakeRequirements

os.chdir('./../') # Change from devtools/scripts directory to root

VulkanRequirements.Validate()
PremakeRequirements.Validate()

# Run the premake script

This PR seems to have alot of file changes, I think something went wrong,
When I fetch from upstream (TheCherno/Hazel) then merge into this branch, it also applied new commits from TheCherno/Hazel as well. I know there was something wrong in merging process, but don't know what was wrong, and I also don't like those commits being stacked here.
Is there any way to fix it?

I see that this PR still tries to add scripts/Premake.py AND scripts/SetupPremake.py.. seems like the old files are not deleted.
Thanks for pointing out. For some reason I forgot to remove the old script.

Another thought I had, why does the script try to change directories twice?
In a rush moment I've copy-pasted the two lines (for consistency in naming style) and forgot to remove one.

Looking at the flow of the script, I would think it has to be first installing Vulkan, then premake, and finally run the premake script?
I think installing Premake first or Vulkan first (the installing order) has no difference... Or, Premake is for the build system, Vulkan is an engine dependency, so Premake should be installed first, right (Python (tool) -> Premake (tool) -> Vulkan (library))

This PR seems to have alot of file changes, I think something went wrong,

When I fetch from upstream (TheCherno/Hazel) then merge into this branch, it also applied new commits from TheCherno/Hazel as well. I know there was something wrong in merging process, but don't know what was wrong, and I also don't like those commits being stacked here.
Is there any way to fix it?

The simples thing would be to copy paste the script files to a separate branch corresponding with a new PR... but that does not matter... just make sure the old files are deleted. I know which changes are already in master and which aren't...

Looking at the flow of the script, I would think it has to be first installing Vulkan, then premake, and finally run the premake script?

I think installing Premake first or Vulkan first (the installing order) has no difference... Or, Premake is for the build system, Vulkan is an engine dependency, so Premake should be installed first, right (Python (tool) -> Premake (tool) -> Vulkan (library))

That seems resonable.

I've deleted the old Premake.py file, and remove redundant directory selection line in Setup.py.
I still can do nothing about the number of file changed though, the only files that I have touched are Setup.py and SetupPremake.py.

Thank you a lot for your suggestion.
I also put a check in the (main) script Setup.py so it won't attempt to call Win-GenProject script if Premake is not detected.


Q: how to add field to edge(relation)?

This looks great.. quite amazing.
It's a newbie question.
I have User / Groups entity. Users can join multiple groups, and groups can have multiple users. So I think it is M:M relation.
When I define edge between to entitys. user_groups table is automatically generated (mysql).
I need some thing like "role" data ( a user is admin in group ) between user - groups.
I think It is good to be included in user_groups(edge) table.
But I just can't find a way to add field to the edge. Do I have to create another entity for role?

@aca, you currently can't add fields to edges (see v1 roadmap).
An possible alternative is to define additional edge between users / groups:
func (Group) Edges() []ent.Edge {     return []ent.Edge{         edge.To("users", User.Type),         edge.To("admins", User.Type).Required() // group must have at least one admin,     } }

@alexsn missed that one. thanks.
What I need is super_admin(which can be multiple) / admin / user  kind of things.
I've tried workaround you provided / creating role entity but generated results are disappoint.
Too sad I think I should give up this great library for current project..
Is there anyone working on this issue ?

It's not our immediate focus at this time. Note that another possible workaround is to add a new ent in between user / group (user <-> role <-> group) which contains the fields you need. Then you could query as follows: user.QueryRoles().Where(role.Name("admin"))QueryGroups().All(ctx)

I tried to add new entity, and this is the result. namespace is the group.
absolutely unnessary table for are generated
user_roles, namespace_roles.
Is this what you are mean?
What about just adding "role" column to the user_groups table and use raw sql query,
until it is fixed? It will be ugly but, It will make it easier to migrate when this issue is fixed.

We only create edges table for a M:N relation while others get a foreign key. You can mark the role ent as having a unique edge to both user / group so no extra tables will be created for its edges.

@alexsn Oh Great!
https://github.com/aca/kcreg/tree/master/ent/schema
I think I got what I needed. Thanks for your help!

@alexsn Oh Great!
https://github.com/aca/kcreg/tree/master/ent/schema
I think I got what I needed. Thanks for your help!

What is your solution? The link is no longer accessible

@sohaha Ent still doesn't support adding field to edges.
The problem I had was fixed by this

We only create edges table for a M:N relation while others get a foreign key. You can mark the role ent as having a unique edge to both user / group so no extra tables will be created for its edges.

func (User) Edges() []ent.Edge {
	return []ent.Edge{
		edge.To("rolebindings", RoleBinding.Type).StructTag(`json:"-"`),
	}
}

func (Namespace) Edges() []ent.Edge {
	return []ent.Edge{
		edge.To("rolebindings", RoleBinding.Type).StructTag(`json:"-"`),
	}
}

func (RoleBinding) Edges() []ent.Edge {
	return []ent.Edge{
		edge.From("namespace", Namespace.Type).Ref("rolebindings").Required().Unique().StructTag(`json:"namespace"`),
		edge.From("user", User.Type).Ref("rolebindings").Required().Unique().StructTag(`json:"user"`),
	}
}

@aca  thank you :)

the same question: two entity, message and user, user can read messages, and message can be read by users, so it is a m:m relation, my question is what about I want mark a message is read by a user, if the generated table have a column named read, thing become easy.


how to show top bar in hours format in Gantt chart

I think the customized view can solve your problem
for reference example:
http://gantt.ngnice.com/components/custom-view
https://github.com/worktile/ngx-gantt/tree/master/example/src/app/gantt-custom-view
Because the minimum unit before is day, the dragging of the minute view may be affected, and we may improve this in the future

Could you please give a demo for hours format in a day in Gantt chart? That's to say add a hour view type, thanks very much.


-std=c++11 flag not working

Hi,
I am new to c++ and learning the language from the book "Programming: Principles and Practice Using C++ " by Bjarne Stroustrup. He uses a header file "std_lib_facilities.h". When I open this header file in atom, a 20 something errors appear.But when I compile it using command prompt with c++11 flag no errors are shown.Also when i include this file it says the file does not exist,although its present with the source file in the folder
Thanks in advance.

Thanks a lot,Hebaishi. The issue is fixed.But what about errors coming in "std_lib_facilities.h".Can you please look into that too.

That does not look like a standard header file to me. This is a problem with your code and not with linter-gcc itself.

Thanks a lot, Hebaishi.


marathon can't resolve hostnames locally after adding long line in /etc/hosts

Marathon can't resolve hostnames locally after adding long line in /etc/hosts.
versions:

Marathon 0.13.0 (also checked 0.8.2)
Mesos 0.25.0
docker 1.9.1

steps to reproduce:

add long (more than 3kb) line in /etc/hosts
add your zk hostnames to /etc/hosts
run marathon in docker container with --net=host (so docker will mount /etc/hosts from host)

Now, marathon  cycling forever in Zookeper connection cycle, just can't resolve their names. As described in issue #1345
If i pass ZK ip address instead hostnames (or zk hostnames not mentioned in hosts), marathon can start, but can't resolve anything mentioned in /etc/hosts.

Hi @aaaler,
Thanks for your bug report. At first read, this sounds rather like a Docker issue rather than a Marathon-specific issue.
As I don't have access to your exact configuration, can you try testing this and verifying that Docker containers are normally able to resolve names from such a line /etc/hosts?

I think this problem is related to the OS or the JVM you are running. My suggestion is to use shorter host names. There is nothing we can do in Marathon.

testing this and verifying that Docker containers are normally able to resolve names from such a line /etc/hosts?

the problem is, that marathon can't resolve any hostname mentioned in /etc/hosts. Not only names from long line.
yes, i can resolve that hostnames in marathon's container.

How i can check hosts names resolving with JVM?

 Your question how to resolve hostnames with the JVM can be answered with google pretty well: http://lmgtfy.com/?q=How+i+can+check+hosts+names+resolving+with+JVM%3F


[BUG] PVC created from Rancher will have empty spec.storageClassName

Describe the bug
To Reproduce

Go to cluster → Storage → Persistent Volumes
Click on Add PV
Select Volume Plugin Longhorn
Give in other required parameters including replica count.
Click on Save.
Verify test-1 PV is created
Go to Cluster → Project (default) → Workloads
Deploy a workload
In the Volumes section → Add a New Volume Claim → Use an existing persistent volume → Select test-1 from PV dropdown.
Click on Define
Enter Mount Point.
Click on create workload
Workload stuck in ContainerCreating state
Volume will not be created on Longhorn
PVC spec.storageClassName is empty

Expected behavior

Workload is created successfully.
Volume gets attached to the pod in the workload
User is able to view the volume attached to the workload in the UI

Log
kubectl get pv -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: PersistentVolume
  metadata:
    annotations:
      field.cattle.io/creatorId: user-bbsfs
      pv.kubernetes.io/bound-by-controller: "yes"
    creationTimestamp: "2020-05-20T20:10:37Z"
    finalizers:
    - kubernetes.io/pv-protection
    - external-attacher/driver-longhorn-io
    labels:
      cattle.io/creator: norman
    name: pv-test-1
    resourceVersion: "16545"
    selfLink: /api/v1/persistentvolumes/pv-test-1
    uid: 8090b0ea-d8b2-467e-a981-6f13a5856071
  spec:
    accessModes:
    - ReadWriteOnce
    capacity:
      storage: 10Gi
    claimRef:
      apiVersion: v1
      kind: PersistentVolumeClaim
      name: pvc-test-1
      namespace: default
      resourceVersion: "16522"
      uid: 6fbec7eb-0a5b-4f69-b8f6-7f5a2e48ef04
    csi:
      driver: driver.longhorn.io
      volumeAttributes:
        numberOfReplicas: "3"
        size: 2Gi
        staleReplicaTimeout: "20"
      volumeHandle: pv-test-1
    persistentVolumeReclaimPolicy: Retain
    volumeMode: Filesystem
  status:
    phase: Bound
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

kubectl get pvc -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
    annotations:
      field.cattle.io/creatorId: user-bbsfs
      pv.kubernetes.io/bind-completed: "yes"
    creationTimestamp: "2020-05-20T20:11:38Z"
    finalizers:
    - kubernetes.io/pvc-protection
    labels:
      cattle.io/creator: norman
    name: pvc-test-1
    namespace: default
    resourceVersion: "16526"
    selfLink: /api/v1/namespaces/default/persistentvolumeclaims/pvc-test-1
    uid: 6fbec7eb-0a5b-4f69-b8f6-7f5a2e48ef04
  spec:
    accessModes:
    - ReadWriteOnce
    resources:
      requests:
        storage: 10Gi
    storageClassName: ""
    volumeMode: Filesystem
    volumeName: pv-test-1
  status:
    accessModes:
    - ReadWriteOnce
    capacity:
      storage: 10Gi
    phase: Bound
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

pod events:
Events:
  Type     Reason              Age                  From                             Message
  ----     ------              ----                 ----                             -------
  Normal   Scheduled           <unknown>            default-scheduler                Successfully assigned default/wk-test-1-bb69c9f65-8v92d to meldafrawi-longhorn-01
  Warning  FailedMount         3m19s (x7 over 16m)  kubelet, meldafrawi-longhorn-01  Unable to attach or mount volumes: unmounted volumes=[pvc-test-1], unattached volumes=[pvc-test-1 default-token-k2vjb]: timed out waiting for the condition
  Warning  FailedMount         63s                  kubelet, meldafrawi-longhorn-01  Unable to attach or mount volumes: unmounted volumes=[pvc-test-1], unattached volumes=[default-token-k2vjb pvc-test-1]: timed out waiting for the condition
  Warning  FailedAttachVolume  38s (x17 over 19m)   attachdetach-controller          AttachVolume.Attach failed for volume "pv-test-1" : rpc error: code = NotFound desc = ControllerPublishVolume: the volume pv-test-1 not exists

Environment:

Rancher Version: 2.4.3
Longhorn version: v1.0.0-rc1
Kubernetes version: v1.16.9  (imported cluster)
Node OS type and version: Ubuntu 18.04

Additional context
Add any other context about the problem here.

When Creating a PV , Volume Handle should refer to an existing Longhorn Volume.
No fix is needed
Closing the issue.


Need default clang-format file location

It's very annoying to create serval clang-format file in each project.
If there is a possible way to specify a global one?

I think this is covered by #805
Current technique available for accomplishing this is to place the .clang-format file in an ancestor directory shared by your projects


Add constructor for Local Bot API Server

This is need to use Local Bot API Server (https://core.telegram.org/bots/api#using-a-local-bot-api-server) or for use a reverse proxy.

It is already implemented in 5.0+ version
It is not working correctly with files.

It is not working correctly with files.
Not working correctly with files in 5.0+ version? or in my request?

In your PR.
Cuz with --local you will get local path to file on your PC instead of https link to telegram servers and that will break few method in the library

ok. i got it. sorry.


Refactor awsiot source to use Knative's adapter package

Should include necessary changes to Makefile, CI conf, and docs.
To be decided: is it worth rewriting from Python to Go?

@sebgoa it seems like the AWS IoT source remained at the stage of prototype. Right now it's just a piece of Python code lying in its own directory, disconnected from the rest. It's not even mentioned in the README.
I think it's time to decide whether we want to:

Commit to supporting AWS IoT properly and write a source in Go which is part of our standard release flow
Remove that code

Any thoughts?

@sebgoa it seems like the AWS IoT source remained at the stage of prototype. Right now it's just a piece of Python code lying in its own directory, disconnected from the rest. It's not even mentioned in the README.
I think it's time to decide whether we want to:

Commit to supporting AWS IoT properly and write a source in Go which is part of our standard release flow
Remove that code

Any thoughts?

removed in https://github.com/triggermesh/aws-event-sources/pull/300


Buffer pollution in Tmux

Platform Linux
Terminal software Tmux
The scrollback buffer is frequently updated/filled merely by navigating through tab completions, or hiding/showing the software keyboard in Termux. The Android device that took the screenshots was remotely connected to an x86_64 machine running Tmux. No command line input has actually been submitted in the following screenshots; enter was only pressed once to accept a tab completion after pressing down a couple times. The last screenshot is what happens when showing/hiding the software keyboard.
Steps to reproduce

Possibly just run Nushell in a Tmux session; not sure if the Android terminal emulator plays into it, but it doesn't happen outside of Tmux (changing nothing else). In my testing, Tmux can be involved locally, remotely, or both.

Screenshots/Screencaptures

Yeah that looks gnarly.
There are separate issues to investigate:

The soft keyboard will trigger a vertical resize, which reedline still doesn't handle gracefully.
The completion content remains on screen after rejecting/accepting.
Too much completion content/vertical space used. Should be displayed more compact
Unsure if that's an issue: Maybe the completion menu triggers the painting mode for totally exceeding the screen. And its scroll up operation will most likely mess up the scrollback buffer


Fixed the repeated labeled elements issue

Summary Change Description
See the comments in the issue description for what the problem turned out to be.
Affected Issues/Pull Requests

Resolves #894
Merges into main

Review Notes

See comments in-line.
Checklist

This pull request will be merged once the following requirements are met.  The
author and/or reviewers should uncheck any unmet requirements:

Review requirements

Minimum approvals: 1
No changes requested
All blocking issues resolved by reviewers
Specific reviewers: @add_username_here

Review period: 2 days

Associated issue/pull request requirements:

[x] All requirements in affected issues marked "resolved" are satisfied
[x] All required pull requests are merged (or none)

Basic requirements

[x] All linters pass
[x] All tests pass
[x] All conflicts resolved

Overhead requirements

[x] New/changed method tests implemented/updated (or no change)
[ ] Updated Unreleased section of changelog.md (or no change)
[x] Migrations created & committed (or no change)

After talking over this issue with Fan and then Michael this morning, we decided that the repeated elements (e.g. C,N, C) was not a bug.  It was intended to convey combinations of elements existing among the tracers, which Michael recalled and agreed was useful.  So the problem isn't the repeated elements.  Rather, it is how the information is presented.  Michael suggested 2 things:

Rename the column header to Tracer Elements
Instead of commas for the combos, use +.  E.g. Instead of C,N, C, use C+N, C

I will close this PR and the related issue and create a new issue for the suggested resolution.


Upgrade command

It would be nice, but probably a fair amount of work, if we had an upgrade command that would bring 1.0 users up to 2.0 compatibility (at least to the point where they can use 2.0 generators). At a minimum we would want to generate some config files, the all-out option would be to move existing screens around and such. My vote would be to do at least the minimum.

I think structurally, not much is changing in how we build things.  This should be very doable.
Good on ya for thinking about this.

Right, but some things the generator commands depend on won't be there if the app was generated with v1.

So I'd like to solicit more feedback, from @GantMan in particular, about this issue. @derekgreenberg too. My recommendation is that we build a very specific guide upgrading from Ignite 1.x to 2.0, but don't spend the time on a script. What we should be able to do is hand this guide off to someone new to Ignite, like @codeithuman or @robinheinze , and they can do the following:
$ npm install -g react-native-ignite
$ ignite new UpgradeMe
$ npm uninstall -g react-native-ignite
$ npm install ignite-cli

...then follow the guide and have a working app that is functionally identical to spinning up a new app with Ignite 2.
Discuss.

Yes, I bet a lot of people would find that helpful. Since Ignite give so much flexibility, we may just need to compare and contrast what the differences between 1.x and 2.0 are. This would then allow devs to walk through the sections of their specific app to upgrade.

Also, what's ignite-cli? Doesn't ignite-cli ship with react-native-ignite?

We should also list the library versions we're upgrading. For example, "You will need at least React Native 41 to use Ignite 2.0", etc.

Also, what's ignite-cli? Doesn't ignite-cli ship with react-native-ignite?

In Ignite 1, react-native-ignite was the way you would run ignite.  It was the CLI part.  It relied on another generator-ignite package to fetch and bootstrap your ignite app from our repo (specifically on master and the ignite-base directory).
In Ignite 2, this has been replaced with ignite-cli which is your new ignite cli.  By default this will download the ignite boilerplate from ignite-unholy-app-template, but now this configurable.  Github is no longer a part of the equation anymore.

at least React Native 41

Agreed.  The dependency is<EMAIL_ADDRESS>installed globally.  Which react-native you use with your project does matter too, but it's up to the app template.  For unholy we support 0.40.0 and up.  For minimal we support down to the 20's.  (please don't install react native 20).
One awkward thing about Ignite 2 is, because it's so flexible, it's dependencies are flexible.
We should capture the spirit of this ^ in our docs (minus my babbling of course).

What kevin suggested would be gold plating it.  I would LOVE to have a command simply do the work, but I think that's too much.   Let's let the tickets come in first to make sure it's needed.
I think a doc on upgrading and updating would both be very valuable.

I'm working on a project built from Ignite 1 for an IR client (kipmobile). I can test the upgrade path to Ignite 2.0 with this project if it is helpful and offer feedback. I'd do this in a separate repo, so it would have no impact on the project as far as the client is concerned.

@derekgreenberg That would be fantastic.

I'm upgrading from 1 to 2 RIGHT NOW. ('scuse the shouting). I'll doc anything else I find here on this issue.
eg. if you want generator goodness restored, install the ignite-ir-boilerplate-2016 module from npm and import the ignite.json and ignite folder from a fresh 2.0 project, and you're good to go with generators.

@juddey I hate to make you think back two months, but can you recall if there were any difficulties in this process?

@kevinvangelder No, I think that was about it on the ignite front iirc. React Native upgrades is where I've had more trouble.
Haven't tried ir-next 'tho as I'm in too deep with RNRF.


ShadowManager: Use Assigned Devices for Shadow sync from Cloud -> Greengrass

Feature Description
Specialize the ShadowManager at runtime (specifically for Cloud -> Core shadows).
Also see brief discussion on re:Post
Use Case
The ShadowManager currently requires explicitly calling out every shadow to sync from Core -> Greengrass. This seems acceptable when targeting a single Greengrass-Instance with a handful of devices, but when targeting a group of instances or an instance with a lot of devices, this becomes cumbersome and may push the limits of configuration-document size. We're in search of a configuration that's generic at the group level, and defer the specialization to runtime, once the component is on an instance.
Proposed Solution
Each core device already has an Associated client devices list which could be used to allow the ShadowManger to specialize itself to each core device at runtime.
I'd expect a configuration like:
{
    ...
    "synchronize": {
        "assignedDevices": {
            "classic": true,
            "namedShadows": [ ... ],
        }
    }
    ...
}

[x] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

Hey @cBiscuitSurprise , thanks for opening this issue.
Being able to automatically sync the classic shadows for associated client devices makes sense to me. Some portion of that functionality would likely live in our Client Device Auth component, but we can start the discussion here.
For named shadows, are you expecting all your client devices to have named shadows with the same name?

We're not currently using named shadows. But trying to put myself in someone's shoes that is, I'd imagine it could go either way.
{
    ...
    "synchronize": {
        "assignedDevices": {  # example: ["thingA", "thingB"]
            "classic": true,
            "namedShadows": ["commonNamedShadow"],
        }
        "shadowDocuments": [
            {
                "thingName": "thingB",
                "classic": true,
                "namedShadows": ["specialNamedShadowJustForB"]
            }
        ]
    }
    ...
}

So in that example whatever is in shadowDocuments would overlay on top of what's defined on assignedDevices. I guess the question you're asking though is then namedShadows a union or just an overwrite of whats in shadowDocuments... I can't answer that. Initially, I'd guess it's a union and if commonNamedShadow doesn't exist, that's already error-handled, so things would "just work" (?).

请问这个功能增强发布了吗？
我现在需要配置一组不同物品名称的客户端设备影子同步，但是我不想指定每个物品名称，请问可以做到吗？

@ArvinSpace. This issue is still open, it is not implemented.


Make Run & Compile Run - Double Window

Whenever I run either command it opens two command windows... no other method of running the file results in this even with other plugins
and right after I submitted this I ran the plugin again and got 3 windows and now 4.... and now 5...
Ok Figured it out everytime I uninstall/disable and re-enable plugin I get an additional window popping up
fixed it by uninstalling then closing atom then re-installing

Same issue.  Uninstalling and Reinstalling results in multiple calls to make when 'make run' is selected from the contex menu.

sorry for a bit late 😅

found the cause:
when deactivate the package, did not dispose the subscribed editor commands
thus when reactivating, it registered the editor commands again ...
will fix it when i have time


Zig 0.13.0 support

Any chance of updating to support zig v0.13.0 by default? This new zig version uses .zig-cache as it's cache directory name instead of zig-cache

Thank you. This tool is great


add policy gradient in Jax

Hello, recently I am learning Jax and haiku and I would like to contribute a Jax version of policy gradient methods (which seem to be missing). The results on the catch env suggest that under the same parameter setting here the Jax version of A2C converges faster:

But I find my current Jax implementation runs ~6x the tf version.... I think the tricky thing is the policy network and value network share the same torso body. So what I did is to assign different optimizers for different parts of the network params. Not sure if it is the best way to utilize the Jax functions

I like this auspicious PR# btw :smiley:


Planets without "Contributes to Research" checkbox enabled do not show leftover production resources in research dialog or planet modal tooltip until their production queue gets updated

IDK whether the extra resources actually go towards research or not (I'd presume they do), but either way fun bug.

I need to assume all resources are "leftover" if a planet has no production queue

@sirgwain sorry to be a bother but this still happens with finished autobuild orders.

Next round.


Compiler passes not initialized instance variable. And causes segfault.

version: Crystal 0.10.2 [b2b2d93] (Wed Jan 13 17:00:14 UTC 2016)
Compiler passes below code.
class Hoge
  def initialize
    @hoge :: String
  end

  def hoge
    @hoge.size
  end
end

p Hoge.new.hoge

And causes segfault.
% crystal instance_variable_test.cr
Program exited because of a segmentation fault (11)

If I  move instance variable definition from constructor to class context, compiler causes build error. (I expect this behavior)
class Hoge
  @hoge :: String

  def initialize
  end

  def hoge
    @hoge.size
  end
end

p Hoge.new.hoge

% crystal instance_variable_test.cr                                                                                [~/work/crystal]
Error in ./instance_variable_test.cr:12: instantiating 'Hoge#hoge()'

p Hoge.new.hoge
           ^~~~

type must be String, not String?
...

The error is totally unrelated.
:: is unsafe. It has no effect on the value's type, but it's uninitialized (as you already know).
I think the latter is an error because @hoge isn't initialized in initialize, so it is now nillable.

As @kirbyfan64 says, this is expected behaviour, although right now the syntax is confusing. In the next release the first code will become:
class Hoge
  def initialize
    @hoge = uninitialized String
  end

  def hoge
    @hoge.size
  end
end

which is a bit more clear.