Use constructor name to determine if a function is a generator function

If we are using a polyfill runtime for generators, the constructors might not be identical. Using the name is a bit hacky, but it's the best we got.

A preview package of this pull request has been released to NPM with the tag generator-function-by-constructor-name.
You can try it out by running the following command:
$ npm install effection@generator-function-by-constructor-name

or by updating your package.json to:
{
  "effection": "generator-function-by-constructor-name"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against ee4b07de8ce6c138335ea1c16f297414ad72ec33

A preview package of this pull request has been released to NPM with the tag generator-function-by-constructor-name.
You can try it out by running the following command:
$ npm install effection@generator-function-by-constructor-name

or by updating your package.json to:
{
  "effection": "generator-function-by-constructor-name"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 5683f69d67a4412e3a913ec8e1416613bdea58d2

A preview package of this pull request has been released to NPM with the tag generator-function-by-constructor-name.
You can try it out by running the following command:
$ npm install effection@generator-function-by-constructor-name

or by updating your package.json to:
{
  "effection": "generator-function-by-constructor-name"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 131b1c8528cc6fb22cbdbd595939fdadd98a186a


ARROW-3728: [Python] Merging Parquet Files - Pandas Meta in Schema Mismatch

Merging tables with schemas identical field-wise but different in metadata fails.

Can you explain the issue in the PR description? Thank you :)

Do We want to provide an API for merging parquet files?

Codecov Report

Merging #3029 into master will increase coverage by 1.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3029      +/-   ##
==========================================
+ Coverage   86.99%   88.03%   +1.04%
==========================================
  Files         494      425      -69
  Lines       70410    64819    -5591
==========================================
- Hits        61253    57066    -4187
+ Misses       9061     7753    -1308
+ Partials       96        0      -96

Impacted Files
Coverage Δ

python/pyarrow/parquet.py
93.89% <100%> (+0.19%)
:arrow_up:

python/pyarrow/tests/test_parquet.py
97.39% <100%> (+0.02%)
:arrow_up:

cpp/src/arrow/util/thread-pool-test.cc
98.91% <0%> (-0.55%)
:arrow_down:

rust/src/record_batch.rs

go/arrow/array/table.go

rust/src/array.rs

go/arrow/math/uint64_amd64.go

go/arrow/internal/testing/tools/bool.go

go/arrow/array/bufferbuilder.go

go/arrow/internal/bitutil/bitutil.go

... and 64 more

Continue to review full report at Codecov.

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

Could you clarify what you mean by "merging parquet files"? Like reading multiple files and writing out a new file? It might be useful, feel free to open a JIRA issue


Settings for point values being worth X money, deduct from a user's wallet

I was thinking about adding "expenses" against Rule Violations that are paid out of the Pilots "Wallet"
so if you break a rule it has a $ value, out of the pilots pocket
as right now there is no "Use" for the Pilot Wallet, except bragging rights

While looking at the code I ended up finding this following snippet from the '\app\Services\Finance\PirepFinanceService.php'
        $this->financeSvc->debitFromJournal(             $pirep->airline->journal,             $pilot_pay,             $pirep,             $memo,             'Pilot Pay',             'pilot_pay'         );
        $this->financeSvc->creditToJournal(             $pirep->user->journal,             $pilot_pay,             $pirep,             $memo,             'Pilot Pay',             'pilot_pay'         );
I think this could be used to Debit a Pilots Wallet and Credit the Airlines, so each Violation would cost the Pilot some Money,
and Pay the Airline that Money for the Violations or Damage to a Plane for Hard Landing and so on...

Yeah, I was also thinking it should come out from the pilot's wallet and go to the airline.

Since violations only arrear from Acars PIREPs, this additional code function could be added to the existing PirepFinanceService.php
You/We would only need to add a New "Tick Box" as well as an Input Box in the "pireps" Settings in admin panel, the
Tick Box to enable the feature, and the Input Box to enter the "Cost" of each violation.

And also modifying and including additional integration tests to cover this case

I was going to start looking into this soon(tm)
I think I can get it working without much of an issue with a hard coded Cost for each violation, the thing I would need to learn would be adding the settings to the Admin Settings, that is what I was thinking of trying to find in the code, and see if I can replicate the current code to do as I want it to.

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
jaconey, @paulschmeida, @mskalra, @inguelberth, @4adamu, @kranthisai, @bbodien, @crazy-choose, @ltoshea, @trevex, @ncoelho, @Enigma10, @xfo-0, @hkjels, @agdolla, @nidhigadhavi, @51396, @IsaacBell, @geduardcatalindev, @htadashi, @nonamez, @rotkreis, @tommuhm, @jmlucjav, @MasonStone, @plck1, @matteoscurati, @donpdonp, @woojae-jang, @telemakhos, @theodesp, @aakritishroff, @ivanlemeshev, @shuklaravi, @oiovoyo, @sandroci, @titmy, @samholt, @stopyellingatme, @ryan-shaw, @sensarliar, @refugeesus, @yijun-lee, @ecoinomist, @Rookie39, @pushkarnagle, @datagutt, @kznmft, @viktorbezdek, @panayi


Sitemap index: split sitemap for large projects

This implements #49 as described in issue.

@Matzu89 thank you for this feature! But you create your from master in your form to master in this repository. It's not correct. Can you create new branch from develop, move your changes into new branch and create new PR from your develop branch to develop branch in main repository?

Will do


optype.numpy.To{}ND false negatives in mypy

@pavyamsiri discovered in https://github.com/jorenham/scipy-stubs/pull/195#issuecomment-2495831247 a false negative in mypy with recursive sequences. This causes e.g. onp.ToFloatND = "huh" to be accepted by mypy.
I raised this in https://github.com/python/mypy/issues/18184.
In the meantime we'll need a workaround, as this directly affects a very large portion of the  annotations in scipy-stubs.

import numpy._typing as _npt
import optype.numpy as onp

def f_np(x: _npt._ArrayLikeFloat_co) -> None: ...
def f_onp(x: onp.ToFloatND) -> None: ...

f_np("duck")  # OK: rejected
f_onp("duck")  # FAIL: accepted (mypy only; pyright rejects)


Plugin upgrade behavior is undefined

This plugin author couldn't find any TouchPortal developer documentation that outlines what happens when the same plugin .tpp file is reimported when it was already installed before (whether same version, newer version, or downgrade).  Therefore, the behavior is undefined.
Anecdotally, it works fine, but sometimes in development the currently running plugin instance doesn't stop in time, and TP doesn't actually get it uninstalled correctly when over-installing the new one.  This results in the reinstall failing to complete.  The workaround is to just reinstall it again.  It can be avoided by first going to the plugin settings and stopping the plugin instance, before doing the upgrade.
All issues can be avoided by opening the TP application settings, going to Plugin section, select this plugin on the right, and use the trash can icon to uninstall.  The next import will be successful, and you won't lose any settings (you will lose your old plugin debug logs though).

TouchPortal plugin-general chat on Discord indicates that a reinstall of the same plugin name will completely replace the plugin's folder contents.  As stated above, informally it should work, but if any trouble arises, safest to uninstall and reinstall the plugin (all settings will be retained automatically).


Tag/Category shouldn't be case-sensitive

Example: https://myblog.com/category/Advice
Should be non-case sensitive, and allow advice, ADVICE, or any mix thereof, aDVicE

Fixed in 715a7b9

Undone in 094c6a0 for now...
Ultimately, tags should be shown exactly how they are saved in CouchDB. Fixing the sensitivity requires aggregating a view like tag-published/?keys=["JAVA","java","Java"] with multiple key variations and removing duplicate results. Possibly with ArrayList -> HashMap and back to ArrayList. (But that's a serious waste of resources.)


Test files do not have the correct filetype under (abnormal?) conditions

test files are not being have the correct filetype detected If you have a .t file in a directory other than a directory called t and you have something like the following:
BEGIN { use Test::Most; skip_all => 'author tests' unless $ENV{AUTHOR_TESTING} }
eval { require Test::CheckDeps };
plan skip_all => 'Test::CheckDeps required' if $@;
...

or even spread it out
BEGIN {
  use Test::Most;
  skip_all =>  'author tests' unless $ENV{AUTHOR_TESTING}
}
eval { require Test::CheckDeps };
plan skip_all => 'Test::CheckDeps required' if $@;
...

if you move the 'use' line so it's in the first column then the above filetype would be detected correctly, or if you have a use later in the file on the first column, the file it would be detected correctly as well.
$VIM/vim74/filetype.vim:2061-85 explains why this is happening.
Basically, the following checks are made.
If the directory name the file is in is named 't', then it's a perl file, set and return.
If the first line and the first column of the file contains a '#' and the first line contains the work perl, then it's a perl file, set and return.
if there is a line that looks like '^use\s\s*\k' and can be found in the first 30ms of searching, it's a perl file, set and return.

It looks like this will not work for
use
  Some::Module;

either.
We could mimic the checking done here and add somethin like
if expand("%:e") == 't' && expand("%:p:h") =~ '/xt/'
  setf perl
  return 1
endif

But I'm not sure where. would it a good idea to even include this?

I was able to make the following work in after/ftdetect/perl.vim:
function! IsPerlTestFile()
  if expand("%:e") == 't' && expand("%:p:h") =~ '/xt/'
    set filetype=perl
  endif
endfunction

au BufNewFile,BufRead *.t call IsPerlTestFile()

@harleypig I've seen that too, but I don't remember the filetype that was mistakenly used.  Do you know what it is? That might help to create a more encompassing solution.

After digging into the filetype.vim distributed with Vim 7.4.738, it looks like .t files are set to nroff or tads unless some specific conditions are met (one of which is residing within a directory named t/).  We should probably include xt and send a patch upstream.

Can we reasonably assume that 'xt' anywhere in the path constitutes a test file? As opposed to the last directory in the path being 't' ...
I'm seeing a lot of cpan modules with xt/{author,release,smoke}/*.t files, and a few other arbitrary names in places. I've even seen deeper structures.
It's not a problem until and unless a test file is created with those particular parameters I mentioned, which is why I'm not sure if it's a valid thing to suggest  upstream (what else does this affect?) or to keep it in vim-perl, even if just as a contrib file.

@harleypig That seems reasonable.  Let's start with a contrib file, and merge it into ftdetect if enough people use it.


Parameters required for generating dynamic segments

After upgrade to 0.5.0-beta.10, I start getting the below errors:
"Assertion Failed: You attempted to define a `{{link-to "enterprise.index"}}` but did not pass the parameters required for generating its dynamic segments. There is no route named enterprise.index"

Going back to 0.5.0-beta.9. My all dependencies below:
{
  ...
  "devDependencies": {
    "broccoli-asset-rev": "~2.5.0",
    "ember-ajax": "~2.5.5",
    "ember-cli": "~2.12.0-beta.1",
    "ember-cli-app-version": "~2.0.1",
    "ember-cli-babel": "~5.2.4",
    "ember-cli-dependency-checker": "~1.3.0",
    "ember-cli-eslint": "~3.0.2",
    "ember-cli-htmlbars": "~1.1.1",
    "ember-cli-htmlbars-inline-precompile": "~0.3.6",
    "ember-cli-inject-live-reload": "~1.6.1",
    "ember-cli-qunit": "~3.1.1",
    "ember-cli-sass": "~6.1.1",
    "ember-cli-shims": "~1.0.2",
    "ember-cli-sri": "~2.1.1",
    "ember-cli-uglify": "~1.2.0",
    "ember-cli-webfont": "~0.0.3",
    "ember-data": "~2.12.0-beta.4",
    "ember-engines": "~0.5.0-beta.9",
    "ember-export-application-global": "~1.1.1",
    "ember-load-initializers": "~0.6.3",
    "ember-resolver": "~2.1.1",
    "ember-simple-auth": "~1.2.0",
    "ember-simple-auth-token": "~2.1.0",
    "ember-source": "~2.12.0-beta.2",
    "ember-truth-helpers": "~1.3.0",
    "loader.js": "~4.2.2"
  },
  "engines": {
    "node": ">= 6.10.0"
  }
  ...
}

Can you put together a demo repo for us to look at?  Are you saying that things worked properly on 0.5.0-beta.9, but not on 0.5.0-beta.10?  Any other dependencies change?
The changes from -beta.9 to -beta.10 were almost exclusively related to CSS handling. I'm not sure why those changes would trigger this error.

Is a corporative project. I know now that is a issue with another addon. Thanks @rwjblue 👍

@rwjblue, I put a demo on https://github.com/brunowego/ember-site-engine. If have a time, try debug this.

Just change 0.5.0-beta.10 to 0.5.0-beta.9and will work.

This issue occur too in Routeable Engine demo.

@trentmwillis can you help me with this? Thanks!

I finded my mistake. I am trying to test the routable engine inside the dummy app, only thing I forgoten is create the application.js and application.hbs inside the dummy app.
After this everthing works.
Thanks and sorry for disturbing...


New CosmicEmu branch

This is almost the same as the old cosmic emu branch. The only difference is in the latest merge with master, which incorporates CMBlensing and was causing trouble in the previous branch. @philbull opened a new branch where merge conflicts with master are now (almost) resolved.

I've now fixed up the remaining issues (to do with how errors causing integration errors are passed through to Python). This is now ready for a final review.

Just one last comment on that: you can set Omega_nu=0 in the emulator,
in which case you would have massless neutrinos.
On 12/22/17 9:46 AM, Danielle Leonard wrote:

@c-d-leonard requested changes on this pull request.
So after speaking with @katrinheitmann
https://github.com/katrinheitmann about the emulator, my
understanding from her is that the total number of neutrinos should be
fixed 3.04. In some places, we seem to have specified that the total
number of massless neutrinos be 3.04; this will cause some
discrepancies. Lets fix this before merging.

In tests/ccl_sample_pkemu.c
https://github.com/LSSTDESC/CCL/pull/296#discussion_r158508350:

+#include "ccl.h"
+#include <math.h>
+#include <stdio.h>
+#include "ccl_params.h"

+int main(int argc, char * argv[])
+{

int status=0;
double Omega_c = 0.25;
double h = 0.7;
double Omega_b = 0.022/h/h;
double normp = 0.8; //2.1e-9
double n_s = 0.96;
double Omega_k = 0.;
double Neff = 3.04;
double Nmass = 1;

I think that in speaking to Katrin we established that the emulator
requires the total number of neutrinos to be fixed to 3.04. This sets
the total number to 4.04 so I think it will give incorrect results.

In tests/ccl_test_emu_nu.c
https://github.com/LSSTDESC/CCL/pull/296#discussion_r158508884:

+CTEST_DATA(emu_nu) {

double N_nu_rel;
double N_nu_mass;
double mnu[4];
double sigma_8[4];
double Omega_c[4];
double Omega_b[4];
double n_s[4];
double h[4];
double w_0[4];
double w_a[4];
+};

+CTEST_SETUP(emu_nu) {
+

data->N_nu_rel=3.04;

Again, I think this will set the total number of neutrinos to 4.04.

In tests/ccl_test_pyccl_interface.py
https://github.com/LSSTDESC/CCL/pull/296#discussion_r158508975:

@@ -29,17 +29,25 @@ def reference_models():
p5 = ccl.Parameters(Omega_c=0.27, Omega_b=0.045, h=0.67, sigma8=0.8, n_s=0.96)
cosmo5 = ccl.Cosmology(p5,transfer_function='eisenstein_hu')

Emulator Pk

p6=ccl.Parameters(Omega_c=0.27, Omega_b=0.022/0.67**2, h=0.67, sigma8=0.8, n_s=0.96,N_nu_rel=3.04,N_nu_mass=0.,m_nu=0.)
cosmo6 = ccl.Cosmology(p6,transfer_function='emulator',matter_power_spectrum='emu')

Emulator Pk w/neutrinos

p7=ccl.Parameters(Omega_c=0.27, Omega_b=0.022/0.67**2, h=0.67, sigma8=0.8, n_s=0.96,N_nu_rel=3.04,N_nu_mass=1,m_nu=0.06)

Again, concerned about setting total number of neutrinos to 4.04.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/LSSTDESC/CCL/pull/296#pullrequestreview-85334447,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMQ9jGujz-0PYJDDdEPQsUoMY7wTz4TSks5tC865gaJpZM4Q3lUh.

@katrinheitmann @elikrause @christianel:
@c-d-leonard and I have been discussing this issue and here’s the summary of the situation:

CCL implements the cosmic emulator of Lawrence et al. for the power spectrum with massive neutrinos.
We need to make sure that our set-up of the cosmology that we pass the emulator via CCL is consistent with what was used for the original emulator. This is important because we want distances obtained by CCL to use the same cosmology as the emulator team used.
In the case of neutrinos, we believe that the original configuration was 3.04 massive neutrino species and 0 massless neutrinos, in a manner consistent with the CAMB implementation (which we are not very familiar with).
But we can’t really pass non-integer massive neutrinos to CCL.

So, given CCL options:
What values of N_nu_rel (number of massless neutrinos) & N_nu_mass (number of massive neutrinos) should we pass to the ccl_parameters_create routine to get cosmologies consistent with emulator set-up?
And what value of Neff should we pass to the Omeganuh2 routines in ccl_neutrinos.c? Normally, this should be consistent with N_nu_mass, but the emulator configuration would suggest using 3.04.

So case for massless neutrinos is perfect now, thanks! I am still wondering though if it is more accurate to say for the massive case (3.0, 0, m_nu). I checked with CAMB, it basically doesn't make any difference for the transfer function and that's the only place where the N-body code gets to know about N (otherwise, it's Omega_nu that's entering). What do you you think?

The difference would be in distances and growth, particularly at high redshift. If we set (3.0, 0, m_nu), we don't guarantee 3.04 (actually, 3.046) in the early universe. Do you think this is more consistent with the emulator neutrino cosmologies? (The paper, Lawrence+, says Neff=3.04, that's why we enforced this it.)


time: fix for "AddDate() should use UTC if loc is nil" does not seem to actually fix the issue

The fix for issue #15852 time: AddDate() should use UTC if loc is nil does not seem to actually fix things. See the following snipped in golang play:
package main

import "fmt"
import "time"

func main() {
	t1 := time.Date(2017, 1, 1, 0, 0, 0, 0, time.UTC)
	fmt.Printf("%+v\n", struct{s time.Time}{t1})
	t2 := t1.AddDate(0,0,0)
	fmt.Printf("%+v\n", struct{s time.Time}{t2})
}

results in
{s:{wall:0 ext:63618825600 loc:<nil>}}
{s:{wall:0 ext:63618825600 loc:<nil>}}

See https://play.golang.org/p/InvEKjzB5b
Supposedly this was fixed in https://go-review.googlesource.com/c/go/+/23561
Am I missing something?

@tve, what's the problem?
You added 0 years, 0 months, and 0 days to t1 and got the same time.
As far as our API promises, we did exactly what you asked.
Discussing internal state is out of scope, unless it impacts the package's ability to deliver on its documented API. And it's not even clear what internal state you want to see, since you deleted the issue template which asks that question.

Hmmm, two answers:

the purpose of https://go-review.googlesource.com/c/go/+/23561 (initially raised as #15852) was specifically to make an application of AddDate(0,0,0) to a time object cause the location field to be non-nil. As far as I can tell, even though a fix was merged and a test written for it, it doesn't accomplish what was stated. You may say "we cared to fix it back then but we no longer care", fine.

The reason I ended up stumbling into this is because I use reflect.DeepEqual in tests to compare actual vs. expected for deeply nested structures and I end up with a discrepancy due to some time objects having nil in the location. And  so far I don't manage to create a simple static time object that has a UTC zone and doesn't have nil in the location field, I'm sure I'm missing something obvious. E.g. time.Date(2017, 1, 1, 0, 0, 0, 0, time.UTC) results in a nil location. Doing simple things like .AddDate(0,0,0) doesn't fix the nil. Again, I assume you'll say "don't use DeepEqual"...

the purpose of https://go-review.googlesource.com/c/go/+/23561 (initially raised as #15852) was specifically to make an application of AddDate(0,0,0) to a time object cause the location field to be non-nil.

What text in either that code review or that bug makes you think this is about changing the internal values? As I read it, that bug was about making a nil Location mean the same thing as UTC, and not crashing on a nil pointer dereference.

The reason I ended up stumbling into this is because I use reflect.DeepEqual in tests
...
I assume you'll say "don't use DeepEqual"...

Sorry, but yes. This is just one of the traps of DeepEqual, and is why we're increasingly moving towards using https://github.com/google/go-cmp instead.

Thanks for the responses! Time to look at go-cmp.


Bio and picture for ddobrin

@BrianMMcClain - saw your note only now, as I am on PTO.
Added picture and index.md as a separate PR, as the original PR was already approved.

Thanks @ddobrin! Apologies, I hadn't seen that you were on PTO until after I had tagged you. I went ahead and added the bio in #191 to make it one PR, which we'll merge today and get the blog live. Thanks!


Rationalise TLSConfiguration construction.

Motivation:
Currently whenever we add new config to TLSConfiguration, we add a new
static factory function that needs to provide the field. This is because
we currently allow configuration primarily by way of initializers. This
is increasingly not scaling, leading to a proliferation of almost
identical static factory functions.
We can replace this proliferation by having only "default" constructions
that default basically everything, and then having users use
getters/setters to initialize things. This also works well when we have
multiple ways of interacting with config, e.g. with the various cipher
suite operations.
Modifications:

Deprecate all existing factory functions.
Replace with two: forClient() and
forServer(certificateChain:privateKey:). These configure only the
mandatory things for each mode.
Replace all uses of the deprecated initializers with the new ones,
configuring fields manually as needed.

Result:
More consistent configuration objects.

@swift-nio-bot test this please

@swift-nio-bot test this please

@swift-nio-bot test this please

@swift-nio-bot test this please


Use enum class for input enums

Likely fixes #51641
This is a lot, but see the below comments for some things I'd like to point out.

Tested indeed fixes the undefined behaviour!

Needs another rebase though.

Sorry I created a conflict again... this PR is really conflict heavy :|
Will merge it in priority after next rebase.

Thanks!


@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/476
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v5.0.3 -m "<description of version>" 55589cd975f4a8bcd8cab1cd3d5c08e6deec4c16
git push origin v5.0.3

TagBot tag


Test for attributes from contract

@freekmurze is that enough for approval?

Well, it reinforces my thought that both the tests and the changes aren't really needed as everything is already working as expected.

@freekmurze

first run tests with changes in file src/RouteRegistrar.php
second run without changes


Bundle asan/tsan/msan runtime into the app bundle when engine is built with those

For iOS
This requires work on both the engine and the tool side of things.
On the engine side, when flutter/tools/gn is run with --[a,m,t,ub]san flag set, the produced Flutter.framework needs to contain the runtime dylib (e.g, libclang_rt.asan_ios_dynamic.dylib for asan).
On the framework side, when building using a local engine we need to check for the sanitizer runtime dylib and then:

Code sign it.
Bundle it with the app bundle.

https://github.com/flutter/flutter/issues/78076#issuecomment-800671699 has detailed instructions.
non-iOS platforms
Additional investigation needs to happen to determine the exact steps.

For local engine builds, where do we look for this dylib?

The codesigning can happen in the same place the Flutter.framework is signed:
https://github.com/flutter/flutter/blob/891511d58f6550ce9e9b03b8d7c6a602caa97488/packages/flutter_tools/lib/src/build_system/targets/ios.dart#L291
Embedding in the app happens in bash, unfortunately:
https://github.com/flutter/flutter/blob/891511d58f6550ce9e9b03b8d7c6a602caa97488/packages/flutter_tools/bin/xcode_backend.sh#L221-L223

For local engine builds, where do we look for this dylib?

This is found in $ENGINE_SRC/buildtools/mac-x64/clang/lib/clang/13.0.0/lib/darwin/libclang_rt*.dylib. I think engine build rules should ensure that this dylib will be placed in Flutter.framework directory, for example: $ENGINE_SRC/out/ios_debug_unopt/Flutter.framework/libclang_rt.asan_ios_dynamic.dylib, and the tool can sign it.

@iskakaushik Can we have the build rules put it in $ENGINE_SRC/out/ios_debug_unopt/ instead of the Flutter.framework bundle? The top level of the .framework directory isn't where dylibs are supposed to go (macOS is even more opinionated about that file structure)

Started looking into this, filed https://github.com/flutter/flutter/issues/108469


[AppService] az webapp up: add optional params os, runtime

Description

Add optional parameters (os, runtime) to override az webapp up os & runtime detection
Updated some runtime values

Testing Guide

az webapp up --resource-group MyRg --name MyWebapp --runtime "node|12-LTS" --os "windows"

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

AppService

hi @qwordy could you pls help to review? thanks

@calvinsID I am sure you already validated - all the existing scenarios.
What happens with for an existing Windows app, if a user run --os to Linux - hoping we will fail gracefully
what happens if an existing app is runtime is different from what they are using in --runtime, do we just update the runtime - & if so do we need any validation or error handling  like some python versions are supported on a specific OS only or does API throw useful errors here?

@panchagnula Yes lemme make sure I cover those cases in the webapp_up tests as well

@panchagnula Yes lemme make sure I cover those cases in the webapp_up tests as well

Ready to merge?

@panchagnula Yes lemme make sure I cover those cases in the webapp_up tests as well

Ready to merge?

I'm gonna add a few more test cases first


I found bug

Description of the problem or steps to reproduce
Specifications

When i open bracket and write my if condition the starting bracket don't highlighted

It does in my device what device are you on?

#1457 is the same thing and i am facing it too

Parsing shell scripts is a herculean task! Consider this:
printf "%s\n" \
    "${HOME:+$(
        mkdir -p a/b
        echo 'hey!'
        test -c /dev/null && {
            echo '/dev/null exists.'
            > ff
            test -d /proc && {
                echo ${PWD:-I do not know where I am.}
                echo 'aint this a somewhat big program?'
                exit 1
            }
        }
    )}"

Guess what? That's a perfectly valid shell script.
Inside a variable expansion, you can find ─recursively─ [more] variable expansions, process substitution, doubly-quoted strings, single-quoted strings, etc...
My point is that you can't correctly highlight it with just plain regular expressions (unless they are applied recursively). The only thing in micro that matches patterns recursively is regions. However, as you have noticed, they are kind of broken, as they mess the highlighting of patterns (for more information about regions and patterns, read this).
If you can write a syntax highlighter based entirely on regions, then you may have solved this!

highlight problems when quote marks are used inside the if condition, see below image.

On a mac-os and using micro
Version: 2.0.4
Commit hash: c5b0c2d
Compiled on May 23, 2020

Changing sh.yaml file from this
- special: "(\\{|\\}|\\(|\\)|\\;|\\]|\\[|`|\\\\|\\$|<|>|!|=|&|\\|)"

to this
    - special: "[-+/*=<>!~%&|^]"
      # Brackets
    - special.brackets: "(\\{|\\})"
    - special.brackets: "(\\(|\\))"
    - special.brackets: "(\\[|\\])"

seems to work.

Any idea of why it works? :eyes:

@luis-lavaire
After looking into it you are right issue #1457 has problems with region doing random unhighlighting of some characters but not all.

I'm also having the same problem with my own syntax file I'm working on.
For example I have a preproc called "fn", a type called "\$" and single/double quotes defined as constant.string.
With "fn" including the quotes anywhere on the line is fine.
With "$" characters, it unhighlights any instance coming BEFORE the quotes, but not after. This happens regardless of how I define "$", I've tried using it as a preproc, type, special, and statement to no avail.
The solution in #1457 of doing "constant.string: ""."|'.'|.*"" works, but I don't understand why it's necessary.

I think that this can be solved if patterns span across newlines. If you use constant.string: "\".*\"|'.*'" to highlight strings, it doesn't work for multiline strings. So it's just a partial solution.
What I try to do these days is to avoid regions as much as possible.

Documentation is very unclear that region are broken.
I spent a lot of time trying to change my mind and use regions since the docs sounded as it was the road to go :-(
Hope a fix on this will come :
When there's quotes or double quotes on a line, highlights for strings with $ are no more honored.
As a side note, trying to have it with "error" paints almost everything in that color except brakets, quotes, double-quotes... And some parts of some words starting with $. The words that wasn't highlighted are colored with "error".
I tried to match $ with reserved regex but with no luck (might be wrong, it's late over here).
- type: "[^0-9a-zA-Z!#\"%&'()*+,-./:;>=<?@[{]}\\^_|~]+[[:alnum:]]*"`


feat: add url filter and localize method for docs

This adds a localize method to documents which fixes a bug where !pod.doc yaml type was used, a document in the pod's default locale would be returned rather than a (better default) where the current document's locale is returned.
Adds an extremely useful url nunjucks filter which adds the functionality from here to core

Why do you use the relative url for the |url?

Why do you use the relative url for the |url?

It's mainly there as a "sane default". Since sometimes staging or testing environments mount the site with a path other than the root, using relative URLs allows the staging/testing/dev sites to work without modifying all other URLs.
I think we should make the usage of relative (and localize) optional, so I'll add options to the URL filter to enable or disable those features, but using a default of relative (and localized, and fingerprinted) is a good choice for the majority of URLs.

OK, this is updated and a bit better now.

Broke the logic out from Nunjucks and moved it to a static method on the Url object
Naming it a "common" URL, aka the URL you'd most commonly use
Added a bunch of tests

Abandoning this as we are shifting focus to React, no longer needing Nunjucks filters as part of the tooling


Deleting all CP14 guns proto

About the PR
"God created men, Colt made them equal..."
#330

Textures also pls


Spark-TsFile:  value tsfile is not a member of org.apache.spark.sql.DataFrameReader

scala> import org.apache.iotdb.spark._
import org.apache.iotdb.spark._
scala> val wide_df = spark.read.tsfile("/Users/qiaojialin/Desktop/test.tsfile")
:26: error: value tsfile is not a member of org.apache.spark.sql.DataFrameReader

Should be:
import org.apache.iotdb.spark.tsfile._


HF energy difference between old and new versions

I reran a script for Cr2 in the cc-pvdz-dk basis with the x2c Hamiltonian using the latest version of pyscf and found that it gives slightly higher HF energies than we got with an older version of pyscf (more than one year ago). See data below for various geometries.
Any thoughts on what the reason could be would be appreciated.
New:
cr2-1.50.out:972:converged SCF energy = -2098.60241286689
cr2-1.55.out:844:converged SCF energy = -2098.59136668619
cr2-1.60.out:831:converged SCF energy = -2098.57365339832
Old:
cr2-1.50.out:1055:converged SCF energy = -2098.60243249516
cr2-1.55.out:1055:converged SCF energy = -2098.5913865761
cr2-1.60.out:999:converged SCF energy = -2098.57367352078
Here is the script:
#!/usr/bin/env python
import os
import numpy
from pyscf import gto
from pyscf import scf

os.system("rm -rf /dev/shm/*")

ehf = []
emc = []

def run(b, dm):
    mol = gto.Mole()
    mol.verbose = 5
    mol.output = 'cr2-%3.2f.out' % b
    mol.atom = [
        ['Cr',(  0.000000,  0.000000, -b/2)],
        ['Cr',(  0.000000,  0.000000,  b/2)],
    ]
    mol.basis = 'ccpvdzdk'
    mol.symmetry = 1
    mol.build()
    mf = scf.sfx2c1e(scf.RHF(mol))
    mf.level_shift = .4
    mf.max_cycle = 100
    mf.conv_tol = 1e-9

    ehf.append(mf.scf(dm))  # do HF

    return mf.make_rdm1()

dm = None
for b in [1.50, 1.55, 1.60, 1.68, 1.80, 2.00, 2.25, 2.50, 2.75, 3.00, 3.25]:
    dm = run(b, dm)

Hi Yuan,
I tested pyscf-1.6. It has the same results as the latest version. Pyscf-1.5
gives the one close to your old results. From 1.5 to 1.6, the treatment for
diffused functions in x2c is different.
Best,
Qiming
On Thu, Nov 12, 2020 at 07:53:09PM -0800, Yuan Yao wrote:

I reran a script for Cr2 in the cc-pvdz-dk basis with the x2c Hamiltonian using the latest version of pyscf and found that it gives slightly higher HF energies than we got with an older version of pyscf (more than one year ago). See data below for various geometries.
New:
cr2-1.50.out:972:converged SCF energy = -2098.60241286689
cr2-1.55.out:844:converged SCF energy = -2098.59136668619
cr2-1.60.out:831:converged SCF energy = -2098.57365339832
Old:
cr2-1.50.out:1055:converged SCF energy = -2098.60243249516
cr2-1.55.out:1055:converged SCF energy = -2098.5913865761
cr2-1.60.out:999:converged SCF energy = -2098.57367352078
Here is the script:
`#!/usr/bin/env python
import os
import numpy
from pyscf import gto
from pyscf import scf
os.system("rm -rf /dev/shm/*")
ehf = []
emc = []
def run(b, dm):
mol = gto.Mole()
mol.verbose = 5
mol.output = 'cr2-%3.2f.out' % b
mol.atom = [
['Cr',(  0.000000,  0.000000, -b/2)],
['Cr',(  0.000000,  0.000000,  b/2)],
]
mol.basis = 'ccpvdzdk'
mol.symmetry = 1
mol.build()
mf = scf.sfx2c1e(scf.RHF(mol))
mf.level_shift = .4
mf.max_cycle = 100
mf.conv_tol = 1e-9
ehf.append(mf.scf(dm))  # do HF

return mf.make_rdm1()

dm = None
for b in [1.50, 1.55, 1.60, 1.68, 1.80, 2.00, 2.25, 2.50, 2.75, 3.00, 3.25]:
dm = run(b, dm)
`
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/pyscf/pyscf/issues/761

--

Thanks Qiming!
Could you give more details on how things have changed with diffuse functions? Should I take it that the new energies are better than the old ones?

when computing X matrix, basis are de-contracted and linear dependency may be found in these uncontracted basis functions. In old pyscf versions (< 1.6), some attempts are made to remove the linear dependency, including discarding smooth basis functions, or binding the most smooth basis to the less smooth basis. Although linear dependency is largely avoided with these attempts, it introduces uncertainty and reproducibility issue. In later versions, basis decontraction is carried out the regular way. All primitive GTOs are kept. Noticing that linear dependency is almost only associated to the matrix S in S^{-1/2}, a different strategy is used. The spirit of new strategy is basically to transform basis to the eigenvectors of S.  X matrix equations are solved with the new basis and finally x matrix is transformed back to regular AO basis. Linear dependency is removed when building the eigenvector basis of S.
In the code, these transformations are reformulated so as to remove some unnecessary forward and backward transformations.


[Bug]: is "ua" in "output.polyfill" useless?

Version
latest

Details
"ua" is a public option to user, but not documented in https://rsbuild.dev/config/output/polyfill. And it behaves the same as "off". Is it for some compatibility consideration, or can be removed?

Reproduce link
N/A
Reproduce Steps
N/A

It is used by Modern.js, we should remove it and extend the typing in Modern.js


Classification

Hi @lucidrains !
Do you have any idea/insight on how to supervise classification (let's say, for example, MNIST digits classification) after having trained GLOM in an unsupervised way as a denoising autoencoder?
In the paper that seems to be the final goal.
However, it's not clear to me which columns and/or levels should be used for the classification. Also, since GLOM it's dealing with patches, how can single black patches vote towards a certain digit?
In other words, after training GLOM as a denoising autoencoder on MNIST, what we have is:

p X p columns, where p is the number of patches per dimension (e.g. 7X7=49 patches)
6 levels for each column, where the top-most levels should in theory represent higher-level entities, so it seems natural to search for the digit information in these layers
6*2=12 iterations, to allow for information to be passed by both top-down and bottom-up networks

Just by applying dimensionality reduction on the top-most level at different iterations does not seem enough to make the digit clusters emerge. So I'm wondering if you (or anybody else) have some insights on this.
Cheers!

Hi @A7ocin
Did you find the answer to your question? I'm also thinking how to use GLOM for classification. Also, are your results  convincing for the denoising task when you visualize the output? Mine is producing random  images!
Parnian


styles: Remove overrides for KaTeX line-height and white-space

Commit ba66dfe977f3f4d2d532095bc5e125585960c222 incorrectly inflated the specificity level of these rules by moving them inside .rendered_markdown “entirely for readability”. KaTeX has its own rules that work better, so just delete ours.
Testing Plan: Dev server with these test cases and others.

Great, merged, thanks @andersk!  I suspect those rules were a workaround for some older KaTeX bug.


Initial support for esplog binary format

This is the parsing code for the upcoming new binary format for esp-gyrologger, which is briefly described here https://github.com/VladimirP1/ebin-encoder-rs
This won't decode the data written by the current firmware from the master branch - this is for the no-interp, which is not yet ready for general use, so probably it is too early to put it into the supported formats list.
Here is a sample log - about 9 hours long, but with close to no motion - I left it on over night. It can be truncated to any length by just taking first n bytes with dd for example.
X.zip

Looks good to me, do you want to merge this now or wait for more development on the esp-log side?

I think you can merge now


SAML Configuration

Basic adjustments to enable SAML authentication in VarFish. Most parts of the code are copied from the respective sodar-core files.
Note that for a working SAML authentication, it is very likely that users have to change the ATTRIBUTES_MAP fields in the saml config for the specific names. Therefore these fields should most likely be configurable through env as well.

@brand-fabian build failure is a known timing issue in CI here, will restart.

Please also add documentation to the manual on how to configure, maybe link to sodar-core docs where appropriate.

Also, please add change to HISTORY.

Currrently, we are still missing a way to configure the different values of the ATTRIBUTES_MAP field (as I posted in my original comment to #145). This is likely critical, since IDP's other than keycloak are excluded if they use other field names/field ids.

@stolpeo @mikkonie I think you need to take this over.
What we need to decide:

do we limit ourselves to Keycloak only?
if not, we need a way to specify the mapping in environment variables (e.g., JSON serialized Python dict)

Then we need to make this work for VarFish but also in sodar-cor or even SODAr.
I don't know what the best way forward is. Maybe we could make it work for @brand-fabian now (Keycloak, VarFish only) and create appropriate tickets for sodar-core and SODAR. Once we generalize the support and documentation we could push it to Varfish.

@brand-fabian internal discussion yields that you should be able to make ATTRIBUTES_MAP come through env.dict. Would that work here?

Indeed, you should be able to do this by editing base.py as follows:
SAML2_AUTH = {
    # ...
    'ATTRIBUTES_MAP': env.dict(
        'SAML_ATTRIBUTES_MAP',
        {
            'email': 'Email',
            'username': 'UserName',
            'first_name': 'FirstName',
            'last_name': 'LastName',
        },
    )
}

.. and then modify the value by providing a dict to SAML_ATTRIBUTES_MAP env var.
The only thing I'm not sure about is what's the best thing to have there as the default value. @stolpeo, any ideas?

I just added these env options to the base.py. Please take a look and check whether they are suitable. I have included my keycloak-based attributes map as default, but obviousy thats open to debate. If there are many use cases for Shibolleth or other SAML2 IDP's, then I can change it again.
Additionally, I moved over the login page changes from the corresponding Sodar-core file, to be able to have the SSO button on the login page.

Thanks, I'll get @stolpeo and @mikkonie check the parts that I know little of.

The CI fails with
django.core.exceptions.ImproperlyConfigured: Set the SAML_NEW_USER_GROUPS environment variable

Please use defaults for all introduced settings.

Hi @brand-fabian, one note about the login template. It seems you have copied it from django-sodar-core v0.10.x, while VarFish is still on v0.9.x. That means at least the icons will not work as expected. Until VarFish is bumped to the current SODAR Core version, I recommend copying the template changes from here instead.


React admin integration

[x] Login to react-admin
[x] Manage users

[x] Create user

[x] Delete user

[x] Edit user

[x] List users

[x] Github action for react-admin
[x] User type on login to decide if user is an admin #204

Issue #159 is required for this pr

Is it everything that we need? @HubertBalcerzak

blocked by #198

blocked by #207


wasm: update Proxy-Wasm C++ Host to latest.

Signed-off-by: Piotr Sikora<EMAIL_ADDRESS>

/lgtm deps


selectize is not a function

EvaluationDetailsComponent.html:90 ERROR TypeError: $(...).selectize is not a function
Im using angular 5 with angular-cli, i dont really know why this is happening.

I have the same problem here :|

You need to install packages, needed for selectize.
"Dependencies
jquery (1.7 and greater)
sifter (bundled in "standalone" build)
microplugin (bundled in "standalone" build)"
https://github.com/selectize/selectize.js

If Inside Angular2, easiest way is to:

add CSS to the index.HTML
add NgSelectizeModule to some of your modules
inside component:
import 'selectize'; // NOTE yes, you need to add npm i selectize too
import {NgSelectizeComponent} from 'ng-selectize'


reverse array when remove multi groups from array

See this issue I opened in https://github.com/evanphx/json-patch/issues/106
and the PR https://github.com/evanphx/json-patch/pull/107
I used this library(CreatePatch) to crate a jsonPath for K8s webhook.  When the K8s internal logics apply the patch, we meet invalid index.
This PR reverses the order when when should remove multi items.

@mattbaird isn't there an issue when removing and adding elements from an array ? I mean as we removed some elements, the index used when computing the path for subsequent add could be wrong right ?

Is this expected that:
SRC: [1, 4, 5]
DST: [4, 1]

Will only remove element /2 ?
The result will be [1, 4] not [4, 1].
cc @mattbaird


AUSCERT cerificate location

resolution_fixed   |    by ibc599

We are getting SSL errors when trying to look at the website from accessdev, e.g.
$ curl -L http://accessdev.nci.org.au
curl: (60) Peer certificate cannot be authenticated with known CA certificates
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

The issue seems to be that the AUSCERT certificate file needs to be explicitly added (perhaps it is in the wrong location?)
$ curl -L --capath /etc/pki/tls/certs/CA http://accessdev.nci.org.au
<!DOCTYPE html PUBLIC "-_W3C_DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

Issue migrated from trac:71 at 2024-01-31 17:30:16 +1100

<EMAIL_ADDRESS>changed status from new to assigned

<EMAIL_ADDRESS>changed owner from `` to cma900

ibc599 commented

This is the cause of the problem in ticket https://accessdev.nci.org.au/trac/ticket/49

<EMAIL_ADDRESS>commented

Fixed in core framework (changeset:457772c/puppet)

<EMAIL_ADDRESS>changed status from assigned to closed

<EMAIL_ADDRESS>changed _comment0 which not transferred by tractive

<EMAIL_ADDRESS>changed reviews which not transferred by tractive

ibc599 changed status from closed to reopened

ibc599 commented

This doesn't work from other servers like raijin and Bureau's machine. Works only for machines on the cloud.

<EMAIL_ADDRESS>changed resolution from `` to fixed

ibc599 changed resolution from fixed to ``

<EMAIL_ADDRESS>removed milestone (was Future)

<EMAIL_ADDRESS>changed status from reopened to closed

<EMAIL_ADDRESS>changed resolution from `` to fixed

<EMAIL_ADDRESS>commented

Milestone Future deleted

<EMAIL_ADDRESS>commented

Since I was fixing the cert chain issues on the climate-cms server I also added the chain to accessdev's apache config. curl -L http://accessdev.nci.org.au now works from Raijin.


Mouse move DPI on Input Events? (please change it to a better name!)

Godot version:
v.3.2.1 Stable
OS/device including version:
Macbook Pro 2017 13'' default model (macOS Mojave)
Issue description:
I have configured a mouse event to paint a Tilemap.
However, depending on the speed of your mouse movement, you can see several gaps between the painted tiles.
The greater is the speed, the greater is the number of Gaps.
Here's a video showcasing the issue:
https://share.getcloudapp.com/P8ueB6Qg

Steps to reproduce:

Execute the project.

Now try to draw a very fast line.
You should gap between the draw event.

Minimal reproduction project:
camera_drag_plus_set_tile.zip
Obs
Initially, I thought it was some issue with my mouse precision or something, but then I've noticed that when I'm painting in Tilemap with the Godot editor, I don't have this problem:
https://share.getcloudapp.com/mXuAePGZ

Hey, I was looking to other examples of people implementing "draw" events, and I found a Demo with the same problem in the Templates tab of Godot window. The demo implements a simple paint editor, you can find it searching for called GD Paint:

Entirely expected, Godot does not simulate the traversal of the mouse from one point to another, as that would have undesired consequences for many applications.
The solution, is for you to remember the position of the mouse of the previous frame, then draw a line from there to its current position. Instead of only at its current positions. Mice teleport, they don't move gradually.
This is caused by the speed at which the OS provides mouse information to Godot. Not necessarily related to frames rendered, but a faster system with unlocked main loop tick rate will perform better.

Hey @TheDuriel !
Thanks for the quick response!
So do you mean Godot editor actually implements this system you are talking when we draw in the editor?
https://share.getcloudapp.com/mXuAePGZ
As I shared in my initial post, I don't have this problem when I'm drawing in the Godot editor.
To be honest, I didn't quite get your idea of the algorithm, so I wanted to ask you if you could point me to some examples. Don't need to be in GDScript, any language would suffice, I just wasn't to understand the idea.

The editor will likely be implementing it.
In rough:
Every Frame:
if  the button is held
get the mouse position
create an imaginary line from the current to the previous position
place tiles on every cell this line crosses
replace the previous mouse position with the current position

What @TheDuriel describes is called Bresenham's line algorithm. It's already implemented in the TileMap editor but not in the GridMap editor yet.

Thanks so much for the explanations @Calinou and @TheDuriel , you guys are doing an amazing work!


haskellPackages.sensei: patch flaky test

Description of changes
Fixed sensei broken build by adding a patch for the test.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Set up to merge into #266650

How about this?

I was getting hash mismatches when trying to build locally to test:
error: hash mismatch in fixed-output derivation '/nix/store/s05rzrdad9rd2wig3cyvzj0kny33r7hh-5c11026fa48e13ea1c351ab882765eb0966f2e97.patch.drv':
         specified: sha256-zmHZ3pjNxfzTCkP728GYjz0ok2rtjCcQNh5rBZ+6AVg=
            got:    sha256-eUCDvypj2bxTRnHLzrcembLMKHg5c3W3quNfclBDsso=

I've fixed this and tried pushing to your branch, but that didn't work for some reason, so I instead pushed directly to haskell-updates.  I've replace your replacing commit be36bce31c5b with d1235fcaecc88dfb6, which has been merged into haskell-updates in https://github.com/NixOS/nixpkgs/pull/266650 as merge commit 0126d4c46f0806.
Can you try building sensei from the new top of haskell-updates just to make sure that it looks good?

Oh, apparently fetchpatch strips out the entire header. I made a mistake in thinking it was suitable to use alongside nix-prefetch-url. Rookie mistake!
Anyway, haskell-updates' sensei builds and runs great. Thanks.


In the Asset Depreciation Ledger, Asset Depreciations and Balances and Fixed Asset Register Reports  assets, asset categories, and cost centers should be filtered based on the selected company. It shows values of all the companies

In the Asset Depreciation Ledger, Asset Depreciations and Balances and Fixed Asset Register Reports  assets, asset categories, and cost centers should be filtered based on the selected company. It shows values of all the companies

Reference Ledger

Completed-Pr 27,29,30

Completed Hence Closing


PMM-11609 migrated generic cli tests to playwright

https://github.com/Percona-Lab/pmm-submodules/actions/runs/6977154478


Move from glide to dep

dep is production-ready and supposedly better. it also has vendor pruning built in so we can use that instead of having people use the third-party glide-vc tool to keep the vendor dir size down

I'm glad to help

fyi @MartinForReal https://github.com/kubernetes-incubator/external-storage/pull/533/files was WIP but nobody was around to review it. ping @hzxuzhonghu sorry nobody could review it, we can continue working on it now as I will be available.

thank you again to @MartinForReal for your offer and @hzxuzhonghu for writing and updating the gopkg.toml, this is done!


Sync pauses unexpected in Docker container on Synology DSM (/sys/class/power_supply missing)

Describe the bug
Every time I edited or added a new file the sync status changed to paused.
Log:
2023-04-15 10:09:15 manager INFO: Up to date
2023-04-15 10:09:17 manager ERROR: Unexpected error
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/maestral/manager.py", line 802, in _handle_sync_thread_errors
    yield
  File "/usr/local/lib/python3.10/site-packages/maestral/manager.py", line 650, in download_worker
    if self._should_rebuild_index():
  File "/usr/local/lib/python3.10/site-packages/maestral/manager.py", line 400, in _should_rebuild_index
    ac_state = get_ac_state()
  File "/usr/local/lib/python3.10/site-packages/maestral/utils/integration.py", line 84, in get_ac_state
    supply_entry = list(os.scandir(LINUX_POWER_SUPPLY_PATH))
FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/power_supply'
2023-04-15 10:09:17 manager INFO: Shutting down threads...
2023-04-15 10:09:17 sync INFO: Sync aborted
2023-04-15 10:09:17 manager INFO: Paused

It appears to be caused by the missing '/sys/class/power_supply'.
Potential Fix:
I changed line 84 in src/maestral/utils/integration.py to:
try:
    supply_entry = list(os.scandir(LINUX_POWER_SUPPLY_PATH))
except FileNotFoundError:
    return ACState.Undetermined

That has fixed the issue for me.

To Reproduce
Create and run a docker container from maestraldbx/maestral:1.7.1 on Synology DSM 7.0.1 - or any other system that does not provide '/sys/class/power_supply'.
After initial sync - Check status -> Up to date
Create a new file in dropbox. - Check status -> Paused
Logs show the error message above.
Expected behaviour
Expected not to pause sync.
System:

Maestral version: 1.7.1
Python version: 3.10
OS: Synology DSM 7.0.1

Thanks the report, this should indeed be handled better. Since you already have a fix, care to submit a PR?

Thanks the report, this should indeed be handled better. Since you already have a fix, care to submit a PR?

I am unfamiliar with git and github - so I don't know how to do a pull request.
But I will look into it and figure it out 👍


C/C++ syntax highlighting

I use C/C++ and really like your color schemes but the C and C++ highlighting is quite... minimalistic.
I hope you can add support soon.

Do you use a plugin for C/C++ (like this) or just out-of-the-box vim syntax highlighting?

Currently I'm using the vanilla neovim highlighting with your colorschemes until I find a plugin written in lua (I heard that neovim has better lua support and it is better for some reason).
I'm switching from vscodium to neovim and don't know yet how everything works. So I'm sorry if what I wrote doesn't make any sense... :)

Hey!
So I've had some time to look into the issue.
It looks like this isn't an issue with the theme itself, but the vanilla neovim experience. There apparently isn't any thing out of the box that parses the language and adds highlighting to it.
So I installed nvim-treesitter on my nvim 0.6.1 and the latest doki-theme-vim.

Before
After

It doesn't look like the official Doki Theme syntax highlighting scheme, but it is more colorful. I don't use vim for development, so I'm not going to invest any time into making the tree sitter look official.
I'm going to close this issue. Let me know if you need anymore information on how to get that setup.
By the way, just vim and vim-cpp-modern looks okay-ish. At least more like the official highlighting scheme.


[TRIVIAL] Allow gcc 12 compilation

Compiling with gcc 12 on manjaro (arch variant) had compilation errors without adding an additional include file.

Already merged in 1.9.4 https://github.com/XRPLF/rippled/pull/4302


Migrated support-logging to Config V2

Created api/v1/config endpoint, fixed log directory
Removed logging-specific Mongo implementation, added to impl found
in internal/pkg/db/mongo
Because of the above, also removed internal/support logEntry model
and extended pkg/models/logEntry
Renamed persistence interface to DBClient for consistency, renamed
methods where appropriate for inclusion into larger DBClient type
Tested via blackbox tests

Signed-off-by: Trevor Conn<EMAIL_ADDRESS>

Looks like Delete and FindLog are also new functionality?

Looks like Delete and FindLog are also new functionality?

No, they used to be named differently -- "remove" and "find" respectively. Since these method signatures had to be part of the larger Mongo DB type, they needed to be qualified to express what they're trying to remove and find -- thus "FindLog" and "DeleteLog".

I'm considering redoing this PR without the data layer refactoring. Perhaps I was getting off-topic with this effort.

Maybe this data layer refactoring is off-topic, but should be done, and now you already have done half of the effort :)


Ordinals smart contract proposal

Add 3 mimetypes

deploy (This opcode is the deployment contract opcode)
send (This opcode changes the contract status)
call (This operation code is to read the contract status)

When the opcode is send or call
{     kid: 'kind Id',     method: 'method name',     params: [...params], }
it looks like this
const script = [     'Your Pubkey',     'OP_CHECKSIG',      'OP_0',      'OP_IF',      ec.encode('ord'),      '01',      ec.encode('send' || 'deploy'),      'OP_0',      ec.encode(source code || data),     'OP_ENDIF' ]
When people put the operation code on the chain through Segregated Witness, the indexer deploys the contract or loads the contract to perform the corresponding operation.
We can fully realize the same functions as the Ethereum smart contract in this form. If there is a contract that manages tokens belonging to the user on the chain, this will greatly reduce gas expenses and the number of transactions, and can complete n transactions in one transaction. Token transfer can also realize GameFi, Dex and other scenarios
We can also use musig2 to submit immutable transactions on behalf of users through nodes, multi-signature groups to increase user interaction speed.
Regarding the issue of data trust, we can use ChainLink's off-chain reporting scheme to provide weighted aggregated data responses to users to increase data credibility.

I think this is just out-of-scope due to complexity, as well as potentially introducing MEV on Bitcoin, if it has an ethereum-like execution environment. If people want to use runes with smart contracts, I think they'll need to bridge them to L2s.


Documentation error

This is what I get when I follow the documentation on this link.
https://dotnet.microsoft.com/en-us/learn/ml-dotnet/get-started-tutorial/train
See screenshot and the log file attached.
log.txt

Hi @csdhall,
I was able to train using the dataset from the tutorial. Here is my setup:

VS Version: VS2022 (17.1.1)
Model Builder Version: <IP_ADDRESS>0302

Few things I want to confirm.

After you download the file, the dataset you used is the yelp_labelled.txt.
For the "Column to predict" dropdown, you selected col1. The screenshot you posted shows col0 has been set as the label. col0 should be your features, or the input you're using to predict the sentiment in col1.

I'm using VS 2022 and 1.6 version of Model Builder.
I tried both columns separately as there are only two columns.
Neither of the two can be trained.
For I tried col1 to predict. Didn't work.
Then I tried col0 (just to see if that works), and it didn't either.
Yes, I used this  for training is yelp_labelled.txt.
Unfortunately, I don't have VS 2017.
Please let me know if it works for you on VS 2022?

That's odd. No need to test on VS2017 since Model Builder only works on VS2019 and VS2022.
Which version of Model Builder are you using? You can check using the Extension Manager.

@csdhall your model builder version 1.6 is pretty old one  could you update the model builder to the latest version

@csdhall I think you selected the "Value prediction" scenario instead of "Data classification".

If "Data Classification" scenario doesn't work please ping me and we will troubleshoot!


WIP: generate new new files

Initial commit which notifies when .new.new files are generated

Closing this since it's meant to be temporary and the work is done.


Refactor/properties panel

This refactors the whole properties panel.

Not static anymore
Each section of the panel is it's own class that defines the properties, layout, and functionality
Each section automatically updates its values when needed
Each section has a minimize option now

Very nice update.
The minimize button improves the UI in a nice subtle way, reducing clutter.
Just wow! the panelProperties refactor. It will be way more easier to add properties now.
And my typos :), how those typos have escaped Radu and I for several weeks I don't know, lol.
Thank you Pieter.

I just noticed a small mistake in the way we called 2 functions, in
FiltersSection.changeChromaKey and FiltersSection.changeChromaThreshold
what we want is
viewport.getSelectedShapes().forEach((s) => s.filters[index].setKeyFromHex(value, save));

and
viewport.getSelectedShapes().forEach((s) => s.filters[index].setThreshold(value, save));

not
viewport.getSelectedShapes().forEach((s) => s.filters[index].setKeyFromHex(value), save);

We also may need to change the Chroma.setKeyFromHex and Chroma.setThreshold method signatures to take in the save parameter.
BTW, this mistake has been there even before this PR.

I just noticed a small mistake in the way we called 2 functions, in FiltersSection.changeChromaKey and FiltersSection.changeChromaThreshold what we want is
viewport.getSelectedShapes().forEach((s) => s.filters[index].setKeyFromHex(value, save));

and
viewport.getSelectedShapes().forEach((s) => s.filters[index].setThreshold(value, save));

not
viewport.getSelectedShapes().forEach((s) => s.filters[index].setKeyFromHex(value), save);

emphasis on where the save argument is passed.
We also may need to change the Chroma.setKeyFromHex and Chroma.setThreshold method signatures to take in the save parameter.
BTW, this mistake has been there even before this PR.

Yes, this was just copied over during the refactoring.
I've updated the code to reflect your proposed changes

I just noticed a small mistake in the way we called 2 functions, in FiltersSection.changeChromaKey and FiltersSection.changeChromaThreshold what we want is
viewport.getSelectedShapes().forEach((s) => s.filters[index].setKeyFromHex(value, save));

and
viewport.getSelectedShapes().forEach((s) => s.filters[index].setThreshold(value, save));

not
viewport.getSelectedShapes().forEach((s) => s.filters[index].setKeyFromHex(value), save);

emphasis on where the save argument is passed.
We also may need to change the Chroma.setKeyFromHex and Chroma.setThreshold method signatures to take in the save parameter.
BTW, this mistake has been there even before this PR.

Yes, this was just copied over during the refactoring. I've updated the code to reflect your proposed changes

We may also need to change the Chroma.setKeyFromHex and Chroma.setThreshold method signatures to take in the save parameter, so it will be consistent with other shape modifying methods.
Thank you Pieter.

Wow. Amazing update!


test: refactor abi coder coders tests

Related to #753 , this PR increases the overall test quality and coverage of all the coders in the @fuel-ts/abi-coder package. This PR will act as a topic branch, and individual test files will be reviewed into this one first before reviewing to master.
This PR will:

Move all coder unit tests to individual files, refactoring the loop used currently and bringing more understanding of coverage to these tests
Create separate test cases for encode and decode functions per coder
Remove snapshot tests and bring expectations into the same test file
Remove redundant test cases that are testing TS more than our own logic and improve code coverage report
Increase verbosity of tests to enable easier debugging
Bring 100% coverage across coders

Closing to create a cleaner topic branch, and will cherry-pick coder tests into individual PRs


feat: native helm support

Fixes no issue
Description

helm values, Chart, and templates are refactored/improved to provide more native helm support and improve usability
helm and app versioning are properly seperated

:warning: WIP NOTES:

[ ] Discuss using appVersion as v2.2.0 instead of 2.20
[ ] Consider further version definitions e.g. k8s
[ ] ADR 8 on Helm versioning
[ ] docs

[ ] new quick start
[ ] new getting started
[ ] add versioning notes on start page

[ ] cleanup helm/values.yaml (adjust defaults, take out examples)
[ ] add improvements by @annekebr

Checklist

[ ] PR is rebased to/aimed at branch develop
[ ] PR follows Contributing Guide
[ ] Added tests (if necessary)
[ ] Extended README/Documentation (if necessary)
[ ] Adjusted versions of image and Helm chart in values.yaml and Chart.yaml (if necessary)

Codecov Report

Merging #430 (a1de50a) into develop (bf4de6f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #430   +/-   ##
========================================
  Coverage    94.47%   94.47%
========================================
  Files           22       22
  Lines         1105     1105
========================================
  Hits          1044     1044
  Misses          61       61

Continue to review full report at Codecov.

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

no longer applicable with golang switch


oversubscription[fast-downward] claims to be optimal on suboptimal solution

Problem depots2.py.txt has no metric set and the optimal solution length is 15.  Still oversubscription[fast-downward] gives a plan with 16 actions and PlanGenerationResultStatus.SOLVED_OPTIMALLY.
Is this a bug or do I misinterpret the optimality guarantee?

I had a look into the code of oversubscription_planner.py. If the subsolver solves the problem with all subgoals then oversubscription sets the result status to SOLVED_OPTIMALLY, independently of whether the subsolver gives this guarantee. It should be a one-liner to add the additionally required check.

Ah, correct, it depends on the metric. I am not sure whether SOLVED_SATISFICING is the right choice in all cases without metric. Do you assume there is no such thing as an optimal plan in an instance without metric? In the classical setting, PDDL defaults to minimizing plan length if no metric is specified.

No, I don't want to reopen the discussion but it means that Ipotentially need to adapt the Fast Downward planning engine and the test cases. Where are the intended semantics documented?

Adding the semantics documentation will be part of #251.


Add a earning coins method (linkvertise)

uh i accidently made the pull request. This is not tested or good quality of code. I cant test it as i dont have a ptero panel


Ignore reserved units for av1 decoder

case:android.mediav2.cts.AdaptivePlaybackTest#testAdaptivePlayback
In some av1 videos, it contains reserved units. We should ignore it instead of returning an error.
Tracked-On: OAM-102526
Signed-off-by: zhangyichix<EMAIL_ADDRESS>

@dyang23 @TianmiChen @YuanjunHuang @Shao-Feng Could you pls help me to take a review?

For better track this issue, can you add the AV1 spec link, with sections information.

I real world I don't think the 0(reserved) should be exist, if so it's the encoder's bug. We cannot say take reserved obu as error is wrong, but per CTS requirement,  it should takes 0 as none error, at least cannot report error, so I would suggest change handle process according the CTS result, and case by case.

I real world I don't think the 0(reserved) should be exist, if so it's the encoder's bug. We cannot say take reserved obu as error is wrong, but per CTS requirement, it should takes 0 as none error, at least cannot report error, so I would suggest change handle process according the CTS result, and case by case.

yes, I agree with you, that why I only dealt with the case of 0.

Hi all,
I have found below logic from libgav1 which is referenced by google software codec.
https://github.com/Richard-li/libgav1/blob/338d966effe8c641c79bb964b3eb464a20096a0e/src/obu_parser.cc#L2836
They also ignore reserved units for av1 decoder. So I think this patch is necessary.


Bugfix/427 back button doesnt work when activity launched

close #427
Bug:
Clicking back on a screen that shows an alert dialog with Camera and Gallery would do nothing.
Cause:
The dialog is non dismiss-able so the back button is is ignored.
Reproduce
Open the crop image screen which shows the non dismiss-able alert dialog with the options Camera and Gallery.
Click back and nothing happens.
How the bug was solved:
Added an OnKeyListener to the non dismiss-able alert dialog to detect back key pressed. On back key detected the onBackPressed is triggered.
Also fixed the issue where on cancelling/pressing back when intending not to edit/crop the image it would open a screen with an empty image view.

@Canato When will be new version updated with these fixes.

@Canato  Thanks for the instant release of the new version with fixes.

Ohh my message yesterday didn't whent!
But thanks for the reminder. We need to find a way to automate snapshot generations until we do a release.
Was my bad that I forgot before!
@devpathare


Modal windows don't close when pressing the esc button

Steps to Reproduce

Launch Ketcher
Click on "Settings"/"Help"/"About" button
Click the Esc hot key button

Expected behavior
The modal window is closed

Actual behavior
The modal window remains open

Desktop:

OS: MacOS
Browsers:

Safari: 14.1.1
Chrome: 91.0.4472.114
Firefox: 89.0.2
Edge: 91.0.864.67

Release/2.3 The issue is closed as fixed.


account.signOut while offline

Hi,
First of all I don't know if considered as an issue, you should tell me.
I am working on an offline electron's app and Hoodie seems to be great for that but
account.signOut
seems to be rejected with this error
{"status":0,"name":"unknown","message":"getCheckpoint rejected with "} while offline,
that sounds wierd to have to be connected to sign out, I am missing something ?
account.signOut works great when server is up
Here is me logout method ignoreLocalChanges param changes nothing
logout: () => {
    return hoodie.account.signOut({ignoreLocalChanges: true})
}

package.json
"@hoodie/client": "^10.1.1",
"pouchdb-browser": "^6.3.4",

I’m sorry I didn’t get to it today. Long day was long ... I did not forget about it, I’ll try again tomorrow. Maybe someone else will be able to help out quicker

Of course no problem ! I hope you'll find something
Here is my Hoodie  initialisation
import Hoodie from '@hoodie/client'
import PouchDB from 'pouchdb-browser'
const hoodie = new Hoodie({
  url: 'http://localhost:8080',
  PouchDB
})

thanks a lot, I was able to reproduce the issue 👍 I’ll investigate.
Would you be interested in contributing a fix? I’d help you out to find your way around and also help to figure out the bug and the fix, but always happy to onboard new contributors and empower folks to help themselves in future :)

Nice ! Sure I can try to help to contribute hope I will find my path :)

great :) I need to give this some thought first but I’ll get back to you next week.
To give you some background already: we have split up Hoodie into many smaller modules, mostly to force us to create self-contained modules with good APIs, documentation, tests but above all to make contribution easier. So now we have logic for hoodie.account in this repository while we have logic for hoodie.store in the hoodie-store-client repository.
The challenge is now that hoodie.account.signOut() should behave differently based on wether there are local changes in the store or not, so that check would need to go into the hoodie-client repository which combines the two :D In order to make that work for hoodie-client we need ways to "hook" into the signout process from outside the hoodie-account-client, we already have that: https://github.com/hoodiehq/hoodie-account-client#hooks
So now we need to put it all together, I’ll figure this out and then walk you through it. Here is some more info on the overall Hoodie architecture if you are interested: http://docs.hood.ie/en/latest/about/architecture.html

I’m sorry I didn’t get back to you yet. I’m heads down with work and preparing http://offlinefirst.org/camp/, but I will get back to you after the event, I promise


Renamed kav's board.json file and customDevice types

Rename board.json file for KAV's displays and rename accordingly the device types in the device.json file

Fixed also a wrong MF type in generic I2C


UI changes - Profile

Address the following:
User interface (buttons, links, and visual styling)
Interaction design
Labels, headlines, and written text
Navigation structures and content classification
Accessibility (contrast, visual focus indicators, text alternatives, etc.)

For now we'll have the user's profile basic info but maybe in the future we can add groups, roles, and scopes.


Check multiline comments and multiline strings

https://github.com/quantumlib/Cirq/blob/8481f78b468c6335b1ba3b5cfeee457246d4feda/dev_tools/incremental_coverage.py#L184

Covered in #2968


Spotify stops playing: Error sending packet OS

Hey guys! So after using Raspotify for about 3 weeks already I have encountred an issue that has to do with #112, issue that I posted but didnt really know what it was, after seeing what the log said I encounted with a problem that says Error Sending Packet OS, anyone knows what I could be?
pi@MediaCenter:~ $ journalctl --system _SYSTEMD_UNIT=raspotify.service
-- Logs begin at Mon 2019-04-01 12:46:55 EDT, end at Mon 2019-04-01 16:15:42 EDT. --
Apr 01 12:47:08 MediaCenter librespot[435]: INFO:librespot: librespot (raspotify v0.12.0) ef28df6 (2019-03-14). Built on 2019-03-14. Build ID: BFEig1gv
Apr 01 12:47:09 MediaCenter librespot[435]: WARN:: error sending packet Os { code: 99, kind: AddrNotAvailable, message: "Cannot assign requested address" }
Apr 01 12:47:09 MediaCenter librespot[435]: INFO:librespot_core::session: Connecting to AP "guc3-accesspoint-b-467m.ap.spotify.com:4070"
Apr 01 12:47:09 MediaCenter librespot[435]: INFO:librespot_core::session: Authenticated as "hotelabyt" !
Apr 01 12:47:09 MediaCenter librespot[435]: INFO:librespot_playback::audio_backend::alsa: Using alsa sink
Apr 01 12:47:09 MediaCenter librespot[435]: INFO:librespot_core::session: Country: "MX"
Apr 01 13:00:02 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "The Joke" with Spotify URI "spotify:track:37nD8NJhod8BEZ6EGYo2gT"
Apr 01 13:00:04 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "The Joke" loaded
Apr 01 13:02:20 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Is That Alright?" with Spotify URI "spotify:track:172e82oK9vGoBPvc6SqMm5"
Apr 01 13:02:21 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Is That Alright?" loaded
Apr 01 13:05:32 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Hold Your Head Up High - Recorded at Spotify Studios NYC" with Spotify URI "
Apr 01 13:05:32 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Hold Your Head Up High - Recorded at Spotify Studios NYC" loaded
Apr 01 13:09:06 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "No One's Gonna Love You (Stockholm Version)" with Spotify URI "spotify:track
Apr 01 13:09:06 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "No One's Gonna Love You (Stockholm Version)" loaded
Apr 01 13:12:55 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Sign of the Times" with Spotify URI "spotify:track:5ELRkzdzz0HvGpMDlfZHkV"
Apr 01 13:12:55 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Sign of the Times" loaded
Apr 01 13:18:35 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "If You Ever Wanna Be In Love - James Bay Spotify Session 2015" with Spotify
Apr 01 13:18:35 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "If You Ever Wanna Be In Love - James Bay Spotify Session 2015" loaded
Apr 01 13:22:32 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Lonesome" with Spotify URI "spotify:track:0j3v2MeAl14a7I1F3vvewM"
Apr 01 13:22:32 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Lonesome" loaded
Apr 01 13:26:22 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Waking Up Slow - Piano" with Spotify URI "spotify:track:7E9QA6hL8Ebk0yHXeV1U
Apr 01 13:26:22 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Waking up Slow - Piano Version" loaded
Apr 01 13:30:03 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Remedy" with Spotify URI "spotify:track:7GgQi7JTG4b6J4iEF4RTjF"
Apr 01 13:30:03 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Remedy" loaded
Apr 01 13:34:09 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Don't Let Me Down" with Spotify URI "spotify:track:6oqlWkAUCqBXjvorIRSm54"
Apr 01 13:34:09 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Don't Let Me Down" loaded
Apr 01 13:37:09 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "What A Wonderful World" with Spotify URI "spotify:track:2a2gJ4YinLgIovY75zA0
Apr 01 13:37:09 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "What A Wonderful World" loaded
Apr 01 13:42:02 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "I Get to Love You" with Spotify URI "spotify:track:3CV4lFELdziNM1OnHU8nwz"
Apr 01 13:42:03 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "I Get to Love You" loaded
Apr 01 13:46:02 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "The Best You Had - Acoustic Version" with Spotify URI "spotify:track:1JyMina
Apr 01 13:46:02 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "The Best You Had - Acoustic Version" loaded
Apr 01 13:46:36 MediaCenter librespot[435]: WARN:: error sending packet Os { code: 99, kind: AddrNotAvailable, message: "Cannot assign requested address" }
Apr 01 13:46:38 MediaCenter librespot[435]: WARN:: error sending packet Os { code: 99, kind: AddrNotAvailable, message: "Cannot assign requested address" }
Apr 01 13:46:45 MediaCenter librespot[435]: WARN:: error sending packet Os { code: 99, kind: AddrNotAvailable, message: "Cannot assign requested address" }
Apr 01 13:49:20 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Too Good At Goodbyes" with Spotify URI "spotify:track:3VlbOrM6nYPprVvzBZllE5
Apr 01 13:49:20 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Too Good At Goodbyes" loaded
Apr 01 13:52:41 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Make You Feel My Love" with Spotify URI "spotify:track:7rPLZ8Krm6CZIbraFUlnW
Apr 01 13:52:41 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Make You Feel My Love" loaded
Apr 01 13:56:13 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "A Thousand Years" with Spotify URI "spotify:track:6lanRgr6wXibZr8KgzXxBl"
Apr 01 13:56:13 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "A Thousand Years" loaded
Apr 01 14:00:58 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "All On My Mind - Acoustic" with Spotify URI "spotify:track:4piJ8pnoRvC5sqMEp
Apr 01 14:00:58 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "All On My Mind - Acoustic" loaded
Apr 01 14:04:47 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Somewhere Only We Know" with Spotify URI "spotify:track:0ll8uFnc0nANY35E0Lfx
Apr 01 14:04:48 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Somewhere Only We Know" loaded
Apr 01 14:08:44 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Stitches" with Spotify URI "spotify:track:3Jy394MtpM2xciRBTzxBlg"
Apr 01 14:08:44 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Stitches" loaded
Apr 01 14:12:50 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "In a New Bed" with Spotify URI "spotify:track:4Or1Yp4i3VANJE6E39ys91"
Apr 01 14:12:50 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "In a New Bed" loaded
Apr 01 14:16:31 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Helium" with Spotify URI "spotify:track:4S6fv0puLCsfYjyBTPDb9k"
Apr 01 14:16:31 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Helium" loaded
Apr 01 14:20:43 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "The Scientist" with Spotify URI "spotify:track:75JFxkI2RXiU7L9VXzMkle"
Apr 01 14:20:44 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "The Scientist" loaded
Apr 01 14:25:53 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Stone" with Spotify URI "spotify:track:6cRExfWfj87zhACU30aW7l"
Apr 01 14:25:53 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Stone" loaded
Apr 01 14:29:29 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "hate u love u" with Spotify URI "spotify:track:6ATgDc6e4sPn84hvJsAmPt"
Apr 01 14:29:30 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "hate u love u" loaded
Apr 01 14:32:25 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Liability" with Spotify URI "spotify:track:4JyLFq2mHC8JPFTXHwYPWD"
Apr 01 14:32:25 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Liability" loaded
Apr 01 14:35:16 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Like I'm Gonna Lose You" with Spotify URI "spotify:track:2pV8RpdLemcyMWko8dA
Apr 01 14:35:17 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Like I'm Gonna Lose You" loaded
Apr 01 14:39:09 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Not Ready to Say Goodbye" with Spotify URI "spotify:track:37qQafvqJgEou8nZXF
Apr 01 14:39:09 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Not Ready to Say Goodbye" loaded
Apr 01 14:42:59 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Don't Forget About Me" with Spotify URI "spotify:track:4gVZhkcsZcwQ4mU1gEeXE
Apr 01 14:42:59 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Don't Forget About Me" loaded
Apr 01 14:47:27 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Speechless" with Spotify URI "spotify:track:2PjDWdGvvbLQfRRTQIZPmv"
Apr 01 14:47:28 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Speechless" loaded
Apr 01 14:51:58 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "If I Ain't Got You" with Spotify URI "spotify:track:3XVBdLihbNbxUwZosxcGuJ"
Apr 01 14:51:58 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "If I Ain't Got You" loaded
Apr 01 14:55:47 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Elastic Heart - Piano Version" with Spotify URI "spotify:track:0udoMICxzaUbN
Apr 01 14:55:47 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Elastic Heart - Piano Version" loaded
Apr 01 14:55:47 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Lay Me Down" with Spotify URI "spotify:track:6x69yrZAJvsYxhk0CJS4uT"
Apr 01 14:55:48 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Lay Me Down" loaded
Apr 01 14:59:27 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Brighter Than Sunshine" with Spotify URI "spotify:track:3W6UA36h0zahjxU709wL
Apr 01 14:59:27 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Brighter Than Sunshine" loaded
Apr 01 15:03:29 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Waves" with Spotify URI "spotify:track:5TBEr7fXO6cjnOHG3RQENk"
Apr 01 15:03:30 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Waves" loaded
Apr 01 15:06:43 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "No Matter - Acoustic" with Spotify URI "spotify:track:14OWlpPcJxsBvSGI4W65Hl
Apr 01 15:06:43 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "No Matter - Acoustic" loaded
Apr 01 15:09:37 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "13 Beaches" with Spotify URI "spotify:track:4mq14Qa6OehdiyZFtHcdCH"
Apr 01 15:09:37 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "13 Beaches" loaded
Apr 01 15:14:32 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Chandelier - Piano Version" with Spotify URI "spotify:track:1F42Ox5sB2wHdy3a
Apr 01 15:14:33 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Chandelier - Piano Version" loaded
Apr 01 15:18:33 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Cringe - Stripped" with Spotify URI "spotify:track:6TpowNTagUJ7f8ctFFCVN8"
Apr 01 15:18:33 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Cringe - Stripped" loaded
Apr 01 15:22:12 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Quiet - Stripped" with Spotify URI "spotify:track:60oCAd3gei66GObniGX4wV"
Apr 01 15:22:12 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Quiet - Stripped" loaded
Apr 01 15:25:40 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Over And Over Again" with Spotify URI "spotify:track:1X6kxrjWVWiKMqulM8XZpj"
Apr 01 15:25:41 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Over And Over Again" loaded
Apr 01 15:29:48 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Say Something" with Spotify URI "spotify:track:78TKtlSLWK8pZAKKW3MyQL"
Apr 01 15:29:48 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Say Something" loaded
Apr 01 15:33:38 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "When I Was Your Man" with Spotify URI "spotify:track:0nJW01T7XtvILxQgC5J7Wh"
Apr 01 15:33:38 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "When I Was Your Man" loaded
Apr 01 15:37:11 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Somewhere Only We Know" with Spotify URI "spotify:track:3DDGhkxq3FeUorZppSge
Apr 01 15:37:11 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Somewhere Only We Know" loaded
Apr 01 15:40:39 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Woman Go Wild" with Spotify URI "spotify:track:020YsiW7gnBiqTAmEg7eTc"
Apr 01 15:40:40 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Woman Go Wild" loaded
Apr 01 15:44:38 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Don't Kill My Vibe - Acoustic" with Spotify URI "spotify:track:48pYiPPXFoC8l
Apr 01 15:44:39 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Don't Kill My Vibe - Acoustic" loaded
Apr 01 15:47:45 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "What a Good Woman Does" with Spotify URI "spotify:track:1NnYLKwyk4PjliVayy4O
Apr 01 15:47:45 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "What a Good Woman Does" loaded
Apr 01 15:51:12 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "I Will Be Found (Lost At Sea)" with Spotify URI "spotify:track:05Ez6KwjICksc
Apr 01 15:51:12 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "I Will Be Found (Lost At Sea)" loaded
Apr 01 15:55:13 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Stay With Me" with Spotify URI "spotify:track:5Db9VIdDsN5yu3Eu7CT0i4"
Apr 01 15:55:13 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Stay With Me" loaded
Apr 01 15:58:06 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "All of Me" with Spotify URI "spotify:track:3U4isOIWM3VvDubwSI3y7a"
Apr 01 15:58:06 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "All of Me" loaded
Apr 01 16:02:35 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Great American Novel" with Spotify URI "spotify:track:6pdOd8gMlo8WcDQYSwXCDe
Apr 01 16:02:35 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Great American Novel" loaded
Apr 01 16:06:31 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Breathe (2 AM)" with Spotify URI "spotify:track:5auMzVHFr5Zfw6IbKarZ56"
Apr 01 16:06:31 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Breathe (2 AM)" loaded
Apr 01 16:11:11 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Shelter" with Spotify URI "spotify:track:1sLxooNd8EKRLDs0YiwbZF"
Apr 01 16:11:11 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Shelter" loaded
Apr 01 16:15:41 MediaCenter librespot[435]: INFO:librespot_playback::player: Loading track "Blackout" with Spotify URI "spotify:track:0bqQuzIX7tpY4IBllPHDqF"
Apr 01 16:15:42 MediaCenter librespot[435]: INFO:librespot_playback::player: Track "Blackout" loaded

I have the same issue

Might you try the most recent version?

Same issue here
Aug 08 00:40:45 pi4 librespot[911]: [2020-08-07T19:10:45Z WARN  libmdns::fsm] error sending packet Os { code: 99, kind: AddrNotAvailable, message: "Cannot assign requested address" }

Same issue.

This is clearly and upstream issue. I would update to the latest version of Raspotify and if the issue persists file a bug report upstream with librespot.


Ability to specify full file path (not just file name) in command line

In the Wiki for the command-line, there is a note:
Note: There is a known bug err "limitation" that you can only specify the name of the file (not the path). Therefore if there are multiple instances of the file inside the msi with the same name and you want to extract that file there is no way to specify which file to extract. If this is a problem for you report an issue and if I know it is important to someone I'll take the time to make that work.
I could use this capability, as our installers have dlls with the same name (in separate folders), for different languages, and I need the ability to extract all of them.
Thanks in advance.

@TheBudman Thank you for leaving your feedback. I really appreciate it! I'll try to find some time to take a look at this over the holidays. Of course, we welcome pull requests from others, and I personally will go above and beyond to review and help others get pull requests merged in here.

relevant docs: https://github.com/activescott/lessmsi/wiki/Command-Line/_edit#command-x---extract

Would love to see this merged. I am trying to build a small tool that fixes an issue in Mass Effect 3's physx installer (what a PITA this piece of software is) and I need to extract a few files from it's bundled msi into a certain dirrectory, but they're all named the same, just in different subfolders by version number.

I really need it on my current project. I would really appreciate it if you could merge it !

@TheBudman any chance you still have a patch you could upload here? A zip or whatever you have would be great!

@srebilla @Mgamerz Do you have a link to an .msi with duplicates and the name of the files that you’re trying to get out to at don’t work? Or upload an .msi to this thread.


Implement selection of visualization options

UI and service for:
Nature of data

sequential
diverging
categorical

Color Scheme
Just the name, not the color display.

https://github.com/locationtech/geotrellis/blob/a00c35b928e96083188d91734252d66574e3b4a7/raster/src/main/scala/geotrellis/raster/render/ColorRamps.scala


Vite

Hey @c4lyp5o , just checked it out, its amazing how fast this builds and I'm seriously impressed.
Just a few things I noticed however, it seems some assets are missing like the Jellystat Icon for example, some styles don't load or have weird color issues and I also see that image resources aren't being loaded (I'm checking the network calls and it seems to be an issue with how its being proxied when its trying to retrieve the images from the proxy epi endpoint).
Im not really familiar with how vite works so i was hoping you can sort those out,

Thank you for checking it out @CyferShepard. Yeah, i was amazed too at the speed of vite. Its definitely a boost. I will work on the issues as soon as i can. I'll ping you when its done.

Hi @CyferShepard. Ive added some changes for you to evaluate. The problem with the font is remedied by making the global font color white. Ive also made some housekeeping.

Hey @c4lyp5o , just had a quick look and all seems good, fixed a minor issue where vite proxies are case sensitive so some api calls for images where calling Proxy instead of proxy causing images to fail to load. Will test more in-depth by the end of the day when im back from work.

@CyferShepard oh yeah, i noticed that too about the /Proxy api call but since its on the backend, i thought its better if you take charge of it. but really glad to hear that everything is working fine. ive also modified the docker build process. my testing shows its working as it should. maybe you could take a second look if there is anything amiss. thank you again.

hey @c4lyp5o , will do, i attempted to make a few test builds last night but was having issues, simple stuff like which run command it was trying to execute (it was just starting the server and not the front end) plus a weird bug where the built version just returns a white page(this seems to be more of a react issue as i tested with the old build and had the same issue). Once iv got it successfully built il merge to unstable

Hey @c4lyp5o , i just had to make some changes, it looks like everything is in working order, i just was having issues where image kept failing to build when it was running the npm build part. i reverted the Dockerfile and now that seems to have done the trick. im not sure if you want to take a look at it and see if you could get your Dockerfile  to work or if your happy with it as is so i can merge whenever your ready.

@CyferShepard hi cyfer. thanks for reviewing. i think we might be missing 'npm run build' in the package.json? because vite has to build the static html first.
the code now is
"start": "cd backend && node server.js"
i think it should be
"start": "npm run build && cd backend && node server.js"
what do you think?

So it actually builds it first when the container is being built so itl have the static files when the container is created. if you add build itl rebuild the static files every time the container is run which seems wastefull

@CyferShepard hi cyfer. sorry for my late reply. holidays around my parts. i see, now that you explained it. i have reverted my last commit and i think it is ready to be merged. thank you.

hey @c4lyp5o , its cool, i also got abit busy this weekend, there's a few merge conflicts, youl need to resolve those on your branch before i can merge to unstable on my side

@CyferShepard hi cyfer. i synced the branches. i think we can merge now