booleans with "is" prefix are not persisted through Parceler

I created a simple project to show this.  But if you have a parceler object where you give a boolean primitive an "is" prefix to its name, it doesn't seem to be persisted by parceler.
In the example I set both booleans to true and they are persisted.  Upon return only the boolean with out the "is" prefix is correctly restored.
I had to use the Don't Keep Activities developer setting in order to trigger the onSaveInstanceState.  I used parceler 1.0.4 in this case.
ParcelerNameTest.zip
Does this fall under the non-standard getter/setters spoken about here?  https://github.com/johncarl81/parceler/issues/105

Ah, thanks for the example, that makes it so easy to understand the issue.
Looks like your isSelected boolean does not have a matching getter / setter.  The property name must match, prepended with either get or is matching to a method prepended with set.  In your example your getter is named setIsSelected.  Renaming this to just setSelected should do the trick:
@Parcel(value = Parcel.Serialization.BEAN)
public class MyObject {
    private boolean legitSelected;
    private boolean isSelected;

    public boolean isSelected() {
        return isSelected;
    }

    public void setSelected(boolean selected) {
        isSelected = selected;
    }

    public boolean isLegitSelected() {
        return legitSelected;
    }

    public void setLegitSelected(boolean legitSelected) {
        this.legitSelected = legitSelected;
    }
}

By the way, you don't need to define the implementations or `analyze parameters as those configurations represent no change to Parceler's default configuration.

Its just poor naming convention on the boolean member I guess.  Interestingly enough, if you change the getter to isIsSelected() instead of just isSelected() it works again (as the getter and setter match like your example).  Either way the default getter/setter generation in Android studio will generate code that Parceler doesn't recognize (and therefore won't persist) and its not something anyone will realize until weird behavior in their app causes them to question it.
Not saying that this is a bug (now that I fully understand), but just documenting it in case people run into this issue in the future.  Thanks!

I went ahead and added a unit test to demonstrate this behavior also:  https://github.com/johncarl81/parceler/commit/37d2dc22c67720deccb1a9f9f73e9abc6933eb90

Sorry @johncarl81 , i'm new to this library and this is awesome library, just want to confirm, so prepended "is" instead of "get" are still acceptable to a boolean value ?
ex:
boolean inStock;
public setStock(boolean inStock) {this.inStock = inStock};
public isInStock() {return inStock};

If that above sample is correct, i think this little cheap explanation should be added into your doc.

Yes, this is supported following the Java bean standard.  Would you like to
update the README and website with a pull request?
On May 8, 2017 7:51 AM, "Siagian"<EMAIL_ADDRESS>wrote:

Sorry @johncarl81 https://github.com/johncarl81 , i'm new to this
library and this is awesome library, just want to confirm, so prepended
"is" instead of "get" are still acceptable to a boolean value ?
ex:
boolean inStock;
public setStock(boolean inStock) {this.inStock = inStock};
public isInStock() {return inStock};
If that above sample is correct, i think this little cheap explanation
should be added into your doc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/johncarl81/parceler/issues/162#issuecomment-299872463,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKMqQFuLlhrJBmInVAGJzAnsyWdRc87ks5r3x3agaJpZM4Hlk21
.

Soon, will do it later on my freetime and thanks.

Pull request has been done on this ticket #284 Feel free to review @johncarl81


added gilcu3.website

Finally managed to create a small and efficient website using hugo
https://radar.cloudflare.com/scan/fd0d0288-f339-4e7b-8436-d595d5897756/

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the Cloudflare report
[ ] This site is not an ultra minimal site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: gilcu3.website
  url: https://gilcu3.website/
  size: 38.81
  last_checked: 2024-04-12

Cloudflare Report: https://radar.cloudflare.com/scan/fd0d0288-f339-4e7b-8436-d595d5897756/

Thanks!


Question About Volume Scattering

Hello,
I am trying to understand the volume scattering of LuxCore. The below line is hard to understand to me, wish you could help.
What does this random value represent for?
https://github.com/LuxCoreRender/LuxCore/blob/37863b23eac2cd8f875d668ef4ef9f994bbf1dc3/src/slg/scene/scene.cpp#L558
What does this proposedScatterDistance represent for? And why is this equation?
https://github.com/LuxCoreRender/LuxCore/blob/37863b23eac2cd8f875d668ef4ef9f994bbf1dc3/src/slg/volumes/homogenous.cpp#L57
Why is scatter to be false if the  proposedScatterDistance is higher?
https://github.com/LuxCoreRender/LuxCore/blob/37863b23eac2cd8f875d668ef4ef9f994bbf1dc3/src/slg/volumes/homogenous.cpp#L59
Thank you.
Besides, if you would give a brief description about the background theory for how Scene::Intersect and Volume::Scatter work with each other, the would be of great help. Thanks.

For any one who are interest in this, I would recommend PBRT Volume Rendering .


Build Issues on macOS 11

Trying to run the tests on macOS Big Sur fails with a linking error that is basically unable to find any of the symbols in keychain_services::attr::KeyAttr.
I dug through the Security framework in the dyld cache and I didn't see them there. The references I can find to these are that they are an enum but the code seems to suggest they are CFStringRefs.
Any help on getting this compiling would be helpful!

Commenting out the function works but I wonder where those symbols went, or if they were ever there?

It's been awhile since a build has succeeded in CI. It's possible something has changed.
We haven't actively used this library in awhile and it may no longer be working on recent builds of macOS.
It'd be good to get the CI moved over to GitHub Actions.


Fody Issues

Hi, I am having too many issues with Fody failing or corrupting, Can i get a DLL to use?

Severity	Code	Description	Project	File	Line	Suppression State
Error		Fody: No configured weavers. It is possible you have not installed a weaver or have installed a fody weaver nuget into a project type that does not support install.ps1. You may need to add that weaver to FodyWeavers.xml manually. eg. . see https://github.com/Fody/Fody/wiki/SampleUsage	FUGSTwitch

Are you obtaining the library through NuGet, or cloning through Github? I would strongly recommend pulling it from NuGet.

I'll build you a DLL here in a few hours of it turns out your NuGet isn't working.

NuGet. Whenever it stuffs up I just remove all dependencies and reimport, but its working for now fine.

This seems to be resolved now:)


Added Rescheduler documentation

ref https://github.com/kubernetes/features/issues/62, https://github.com/kubernetes/kubernetes/issues/29023

This change is

I'm not done reviewing but some other higher-priority stuff popped up, so this will be delayed. Please wait to make changes until I'm done reviewing, otherwise it will be too confusing.

ok done reviewing now

@davidopp 's comments addressed any issues I had for Docs LGTM. Once he gives his LGTM, I'm good, too.

@davidopp comments addressed. PTAL

Comments applied. PTAL

Thank you, @piosz ! Merging now.


release 0.14.3

These steps should be taken in order to create a new release![^release-refs]
Double check for quality-control

[x] There are no open issues with a block-release label

Prepare the codebase for a new version

[x] Bump __version__ in __init__.py
[x] Update our version switcher .json file with the new version
[x] Make a release commit: git commit -m 'bump: 0.1.9 → 0.2.0'
[x] Push the RLS commit git push upstream main
[x] If a release candidate is needed, tick this box when we're now ready for a full release.

Make the release

[x] Start a new GitHub release

Call the release the current version, e.g. v0.2.0
In the Choose a Tag: dropdown, type in the release name (e.g., v0.2.0) and click "Create new tag"
In the Target: dropdown, pin it to the release commit that you've just pushed.
Add release notes in the field below (if it's a minor/major version bump)[^github-activity]

[x] Confirm that the release completed

The publish github action job has completed successfully in the actions tab.
The PyPI version is updated

[x] Celebrate, you're done!

[^release-refs]: Taken from the release checklist in our wiki. See the release documentation for an overview of release processes.
[^github-activity]: If you wish, use github-activity to generate a changelog, eg github-activity pydata/pydata-sphinx-theme --since v0.2.2 --until v0.3.0.

@blink1073 could you confirm 0.14.3 is solving your issue ?

Confirmed, thank you!


Display usage instructions on wrong repo name

When writing whatever#1, it will behave just as #1 or godot#1. It should instead display usage instructions listing the valid repo identifiers.
Depends on #2.

Implemented in 9eb40e9


OverrideTransient is implemented with OverrideNamed instead of OverrideNamedTransient in v2.0.0-beta.5

func OverrideTransient[T any](i Injector, provider Provider[T]) {
	name := inferServiceName[T]()
	OverrideNamed[T](i, name, provider)
}

Then the instances when calling Invoke multiple times are always identical.

Thanks for the feedback. I just made a fix.


Misc ip-masq-agent improvements

This PR adds some improvements to the BPF ip-masq-agent:

Allows to configure ip-masq-agent in JSON.
Fixes the race condition in the unit tests.
Use fsnotify instead of polling the config file.

Reviewable per commit.
Fix #11289.

test-me-please

test-me-please

Coverage decreased (-0.02%) to 44.44% when pulling 6c26f53e5a5986e6826e4db58868ef53ef2289cf on pr/brb/ipmasq-improvements into 4bdb3617786dd7c3a6f2de78923f5981cdbfc8a6 on master.

test-me-please

test-me-please

test-me-please

test-me-please


Remove Input Upload repeat in Denoise step

Currently, the Denoise step repeats the Input Upload step again (the inputs are both a manifest file). Instead, the Denoise step should be taking the qza that's the output of the input upload step as its input.

We found out that the manifest file from the Input Upload step is required for the Denoise step. You can't just only input a qza into Denoise.
Because a manifest can contain multiple runs, it’s possible for there to be multiple qza files created as the result of the Input Upload step. Because of this, I’m going to keep the input for the Denoise step a manifest file instead of a single .qza since AXIOME need the runIDs in the manifest file to keep track of the files in case of multiple runs (the path Denoise will search for will be something like outputdir/{runID}_paired_end_demux.qza).
From looking at the code, the multiple run import would produce multiple qza files (one per run), not a single one: run1_paired_end_demux.qza,  run2_paired_end_demux.qza, etc. If the manifest only contains one run, the the qza would just be paired_end_demux.qza without mention of the runID. （已编辑）
11:46
The reason runIDs is needed in Denoise, is because the names of the qza files contains the runIDs, and the only piece of data that contains the runIDs is the manifest. Of course, I think in the future once we could create a AXIOME config file that could hold the runIDs, but I think that would be later when we get to implementing the new session management.
Denoise step also does merging of demux files.


Sometimes //undo doesn't remove all blocks

Can't reproduce consistantly

Switching from FAWE API to WorldEdit API


NoMethodError: undefined method `args' for Chef::Resource::ChocolateyPackage

Cookbook version
[Version of the cookbook where you are encountering the issue]
1.2.1
Chef-client version
[Version of chef-client in your environment]
13.2.20
Platform Details
[Operating system distribution and release version. Cloud provider if running in the cloud]
Windows 7 SP1 with latest updates
chefdk 2.0.28
PowerShell 5.1
Microsoft Visual C++ 2010 x64 and x86
Scenario:
[What you are trying to achieve and you can't?]
Trying to pass some arguments for installing a package.
Steps to Reproduce:
[If you are filing an issue what are the things we need to do in order to repro your problem? How are you using this cookbook or any resources it includes?]
chocolatey_package 'docker-toolbox' do
  args '/COMPONENTS="docker,dockermachine,dockercompose,kitematic"'
end

Expected Result:
[What are you expecting to happen as the consequence of above reproduction steps?]
To pass the args to installer
Actual Result:
[What actually happens after the reproduction steps? Include the error output or a link to a gist if possible.]
NoMethodError
-------------
undefined method `args' for Chef::Resource::ChocolateyPackage

System Info:
------------
chef_version=13.2.20
platform=windows
platform_version=6.1.7601
ruby=ruby 2.4.1p111 (2017-03-22 revision 58053) [i386-mingw32]
program_name=C:/opscode/chefdk/modules/chef/../../bin/chef-client
executable=C:/opscode/chefdk/bin/chef-client

Can somebody dig this and fix it?
The same thing is happening when I use:
chocolatey 'docker-toolbox' do
  args '/COMPONENTS="docker,dockermachine,dockercompose,kitematic"'
end

The result is:
    ================================================================================
    Error executing action `install` on resource 'chocolatey[docker-toolbox]'
    ================================================================================

    NoMethodError
    -------------
    undefined method `new' for Chocolatey:Module

    chocolatey("docker-toolbox") do
      action [:install]
      default_guard_interpreter :default
      declared_type :chocolatey
      cookbook_name "cookbook_name"
      recipe_name "docker"
      args "/COMPONENTS=\"docker,dockermachine,dockercompose,kitematic\""
      package "docker-toolbox"
    end

    System Info:
    ------------
    chef_version=13.2.20
    platform=windows
    platform_version=6.1.7601
    ruby=ruby 2.4.1p111 (2017-03-22 revision 58053) [i386-mingw32]
    program_name=C:/opscode/chefdk/modules/chef/../../bin/chef-client
    executable=C:/opscode/chefdk/bin/chef-client

On chef 13, you want to use the chocolatey_package resource and use it's options property. It does not have an args property. See https://docs.chef.io/resource_chocolatey_package.html for it's documentation.


copy parameter file of CRYPTO_mem_debug_* functions ?

It makes sense to copy the file string passed to CRYPTO_mem_debug_* functions, to facilitate usage from languages other than C.
Currently file is expected to remain valid even after function returns (static storage class, as guaranteed by __FILE__ C macro). But when we call for example CRYPTO_free from non-C language, the value we pass is usually allocated dynamically. Creating global values is not very convenient.
Here is an example in Common Lisp - as a workaround I just allocate global value "unknown file" and pass to CRYPTO_free: https://github.com/cl-plus-ssl/cl-plus-ssl/pull/30#issuecomment-196114925

You're doing the right thing -- it's the responsibility of the wrappers to maintain the C-like string lifetimes.


libmxml.a: error adding symbols: File format not recognized

When i am using compiled libxml.a on linux 64 bit . and use it in esp-idf. its says
libmxml.a: error adding symbols: File format not recognized

What does "file libmxml.a" report?

Thanks @michaelrsweet  , Solved it.

@Pratikhyadav : how were you able to solve? I'm facing similar issue in some other library.


Challenge: Override Styles in Subsequent CSS

Issue Description
Challenge: Override Styles in Subsequent CSS
The lesson says that the second declaration takes precendence over the first, however this is not the case in my browser. In my browser, the first declaration has precedence over the second, rendering pink text.
 You define classes like this: class="class1 class2".
Please make sure you ask in our (main)[https://gitter.im/FreeCodeCamp/FreeCodeCamp] chat if you actually have a bug before opening an issue.
Happy Coding :smile:


Fix text formatting with colon - part 1

Why:
This PR is the part 1 of the addressed issue in #35361.
Closes: none

What's being changed (if available, include any code snippets, screenshots, or gifs):
This PR fixes the text formatting with colon.

Check off the following:

[ ] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
[x] The changes in this PR meet the docs fundamentals that are required for all content.
[x] All CI checks are passing.

@akordowski Reviewing part 1 now! 💛

@akordowski Part 1 approved 💛 getting this merged now!

Hi am Elon how are you doing


Mixed content error if using https

causes uniprot, etc annotations not to be shown.
Discussed at PSI meeting - best solution might be to let JAMI retrieve the annotations using JAMI-Bridges  and write them in the JSON object we consume. (i.e. move retreiving annotations outside viewer.)

Intermine is moving to HTTPS so we need this as well, and to support the Chord Digram.

duplicate of #121


Updates Cycle.js implementation details

Cycle.js supports all kind of streams related libraries but it's now built using xstream(http://staltz.com/xstream/) which is not that heavy (nos as heavy as RxJS).

Thanks!


Load obsolete GO terms: GODag("go.obo", load_obsolete=True)

Hello,
I am parsing the go.obo file by:

obodag = GODag("go.obo")
go_name = obodag.get(go_id#).name
go_namespace = obodag.get(go_id#).namespace

I get a key error because some of the terms(GO ids) are not included in the obodag dictionary (obodag).
That terms are not included because they are deprecated/obsolete, but they are in the go.obo file, for example:

[Term]
id: GO:0044444
name: obsolete cytoplasmic part
namespace: cellular_component
def: "OBSOLETE. Any constituent part of the cytoplasm, all of the contents of a cell excluding the plasma membrane and nucleus, but including other subcellular structures." [GOC:jl]
comment: Note that this term is in the subset of terms that should not be used for direct gene product annotation.  Direct annotations to this term may be amended during annotation QC.
subset: gocheck_do_not_annotate
synonym: "cytoplasm component" EXACT []
is_obsolete: true
consider: GO:0005737

Do you know some way to include them in the "obodag = GODag("go.obo")" dictionary?
Also they provide another GO term to consider (GO:0005737 in this case). Do you know how to get if by the deprecated term?
Many regards

Hello @AgustinPardo,
Thank you for your interest in GOATOOLS and taking the time to write and thank you for the great question.
Yes, you can load obsolete GO terms by setting the GODag argument, load_obsolete=True. By default it is False. It would look like this:
obodag = GODag("go.obo", load_obsolete=True)

This is a terrific question and we should have a Jupyter notebook showing how to do this. I will add one shortly.

Thanks for the quick answer!

Hello,
I am having problems trying to capture the "consider" key of the GO terms that are obsoletes in the go.obo file:
For example this term:

[Term]
id: GO:0000067
name: obsolete DNA replication and chromosome cycle
namespace: biological_process
def: "OBSOLETE. (Was not defined before being made obsolete)." [GOC:ai]
comment: This term was made obsolete because it has been superseded by more accurate terms to represent the biological processes occurring, and it is not clear that this term represents a useful entity.
synonym: "DNA replication and chromosome cycle" EXACT []
is_obsolete: true
consider: GO:0006260
consider: GO:0007059
consider: GO:0051276

So I try:

obodag["GO:0000067"].is_obsolete
True

That is ok, so:

obodag["GO:0000067"].consider
AttributeError: 'GOTerm' object has no attribute 'consider'

How could I get the "consider" information of the terms?
Regards

Can you open a new issue for this question? We can track the issues better that way.

Done! Many thanks!


[AutoPR machinelearning/resource-manager] typo: asscociation -> association

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5252

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/1377


We choose to go to the Moon

The story of this started with Liyuan's persistence on the issue of CSI driver policies of the demo, which required a different set of APIs of the node groups that was introduced in a pretty late version of Crossplane. As nowadays people are blaming modifying CRDs directly on the dev env, the only choice seems to be to adopt the changes on our downstream.
After wasting several hours trying to only cherry-pick a few files related to the node groups, I found out that the complexity of the dependencies is far beyond the ability of my poor intelligence, so I decided to upgrade aggressively - so we got up-to-date APIs with a single PR, so no need for CPs over and over again. This proved to be way more difficult than I thought originally, mostly because of our unpreserved mania on laying out "what I want" on the codebase without carefully the possible debt of maintenance.
Anyway, this tiny PR is done with the following steps:

git rebase -X theirs v0.23.0, which rebase our downstream changes onto the latest upstream version. The term "theirs" is a bit confusing here as it basically keeps our files - so the changes critical to our system won't be lost (and nobody wants to resolve those conflicts commit by commit)
make it buildable. This is why we have the last commit (exclude the merge one), and this is the commit that our reviewers should really care about. 99% of those changes are made by simple regex replacement, with very few changes made manually by human beings (me). I'm pretty sure the test of controller/peering is broken as my gopls server crashes over and over again, I'll let Jiajin and Fangfang finish the mission impossible.

Please review the files that you care about or authored previously. Appreciated :)

Gorgeous...with the respect of all the efforts, I would still suggest another possibility that we run both the forked provider-aws and the upstream provider-aws simultaneously. The forked one continues to reconcile the currently used CRDs and the upstream one only reconcile the newly introduced ones. And we may gradually migrate the owner of CRDs from the forked one to the upstream one, until we completely offline the forked one. How do you like? @lorqor

Another issue is, do we really need to remove the unused CRs? @aylei @tennix @zjj2wry? Basically, if a CR is not used then we can just ignore it, but if we disable them in our fork, then this change can never be taken by upstream thus we have to keep out fork, what do you think?

I agree we should keep the CRDs as is.

Gorgeous...with the respect of all the efforts, I would still suggest another possibility that we run both the forked provider-aws and the upstream provider-aws simultaneously. The forked one continues to reconcile the currently used CRDs and the upstream one only reconcile the newly introduced ones. And we may gradually migrate the owner of CRDs from the forked one to the upstream one, until we completely offline the forked one. How do you like? @lorqor

Another issue is, do we really need to remove the unused CRs? @aylei @tennix @zjj2wry? Basically, if a CR is not used then we can just ignore it, but if we disable them in our fork, then this change can never be taken by upstream thus we have to keep out fork, what do you think?

I agree we should keep the CRDs as is.

Do we have any previous discussions on this topic? I don't carefully consider this option, but it seems the CRs provisioned by a controller can be managed by another controller, and they'll have different understanding and expectations on the CR (either change on the lifecycle logic or it could be different versions of APIs), also we'll have to carefully check the ownership of each CR which is another issue... I'm open to off-line discussion (especially this is a public repo...) if you're interested.
I personally believe what we really need is:

Change the current model for the downstream. We should cherry-pick our changes onto the upstream branch, not the other way around.
We make sure the test is not broken and we have proper test cases when our internal changes are added.

For reviewers' convenience, here is the link for the two commits that you should care about:
https://github.com/tidbcloud/provider-aws/pull/37/files/c880fc4091b09db07aa4bd0f7a6f0161a593c975..480577a1d1c252e909972923ccb43e38d91c17fb


Long-distance doesn't display red box

Scenario:
-long-distance trip
-passenger doesn't like VW Caddy
-ride is allocated to a VW Caddy

Expectation:
-the border line should display as red
Hunch:
-the order of colors in css

This has been fixed in commit https://github.com/TIXI24/sfitixi/commit/2ada67771b9ed98568ce94dd2161de76adbdb727


presenterm: 0.6.0 -> 0.6.1

Description of changes
Changelog: https://github.com/mfontanini/presenterm/releases/tag/v0.6.1
cc @MikaelFangel

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] 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/)
24.05 Release Notes (or backporting 23.05 and 23.11 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package built:

presenterm


Cannot successfully close child channel that has never had a frame sent on it.

When closing a child channel that was locally constructed, if that channel has never had a frame sent on it then the close will never complete. This is because the attempt to send a RST_STREAM frame will fail.
We should keep track of whether we have ever received a stream created event, because if we haven't we can insta-close the channel.

Resolved by #124 and #123.


More backend validations

After quick look it's fine to me, maybe @RuslanHamidullin wants to take a look as is more competent in this domain.

yeah,gonna take a look

Looks good :+1:


Added production enviornment

I think it's valuable to be able to run the npm start script with either a production or development environment set. It's pretty common in production-level Node applications.
I also switched the default production port to 80, I thought it was strange my production app was running on 3000.

Thanks for your PR. However, running npm deploy is much easier than NODE_ENV=production npm start.

Sounds reasonable, thanks for taking a look!


Update to work with the latest TTS REST API

Switched to the new API URLs
Use requests to make the requests
Added support to choose the API region

thanks!


For Equipment/Weapon with quantities >1, display it in the character sheet Container entry

Equipment and Weapon now will show up in front of item name, as long as they are higher than 1.


az keyvault create failed on cloudshell

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az keyvault create
Errors:
400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token
Traceback (most recent call last):
python3.6/site-packages/knack/cli.py, ln 215, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 631, in execute
    raise ex
cli/core/commands/__init__.py, ln 695, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
...
python3.6/site-packages/msrestazure/azure_active_directory.py, ln 486, in get_msi_token
    result.raise_for_status()
python3.6/site-packages/requests/models.py, ln 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az keyvault create --location {} --name {} --resource-group {} --sku {} --enable-soft-delete --debug

Expected Behavior
Environment Summary
Linux-4.15.0-1077-azure-x86_64-with-debian-stretch-sid
Python 3.6.5
Installer: DEB

azure-cli 2.4.0 *

Additional Context

The same command works when executed from local desktop. Using local desktop is not an option as the command must be provided to external parties.

hi @astapell did you meet the error on CloudShell? If yes this is a known issue at CloudShell. You can run azure CLI locally to workaround the issue. We're following up on the issue.

hi @yungezz  thanks for your input. I did it already but as we could not always get the credentials on behalf of the end user I'd like a solution to run from the portal. Do you think additional az login there (in cloudshell) as a workaround (which seems to work), is reliable and won't have sort of side effects?

Hi @yungezz , the issue was gone on cloudshell for a time , I am not sure this was a result of the az (re)login command. It does now re-occurs for us since yesterday. As you were following up on the issue, can you tell me a bit more on it and if this can be a periodic issue?

Hi @yungezz, my impression is that a certain time after first user login to cloudshell , oauth2 token expires and causes issues to some objects creation as the keyvault. Using az login again renews this token and fixes the issues for another period. Can you confirm I am correct?

@astapell this should be fixed in Cloud Shell.  Can you see if it is fixed your your scenario?
If so, please close the issue.
If not, please provide an update here.

I'm still seeing the error.
Commands run in the Cloud Shell.  (Within Windows Terminal on Windows 10.)
export AZURE_DEFAULTS_LOCATION=westeurope
export AZURE_DEFAULTS_GROUP=managedIdentityLab
keyvault=msiLab$(head -c256 /dev/urandom | tr -dc "a-z0-9" | head -c 16)
az keyvault create --name $keyvault --resource-group managedIdentityLan --location westeurope

Looks like a token issue in Cloud Shell for this command. Extracted from the full az.log
183 : 2020-08-13 15:02:20,699 : DEBUG : urllib3.connectionpool : Starting new HTTP connection (1): localhost:50342
183 : 2020-08-13 15:03:00,723 : DEBUG : urllib3.connectionpool : http://localhost:50342 "POST /oauth2/token HTTP/1.1" 400 124
183 : 2020-08-13 15:03:00,724 : DEBUG : msrestazure.azure_active_directory : MSI: Retrieving a token from http://localhost:50342/oauth2/token, with payload {'resource': 'https://graph.windows.net/'}
183 : 2020-08-13 15:03:00,724 : WARNING : msrestazure.azure_active_directory : MSI: Failed to retrieve a token from 'http://localhost:50342/oauth2/token' with an error of '400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token'. This could be caused by the MSI extension not yet fully provisioned.
183 : 2020-08-13 15:03:00,728 : ERROR : cli.azure.cli.core.util : The command failed with an unexpected error. Here is the traceback:
183 : 2020-08-13 15:03:00,728 : ERROR : cli.azure.cli.core.util : The command failed with an unexpected error. Here is the traceback:
183 : 2020-08-13 15:03:00,729 : ERROR : cli.azure.cli.core.util : 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token

az version:
{
  "azure-cli": "2.9.1",
  "azure-cli-command-modules-nspkg": "2.0.3",
  "azure-cli-core": "2.9.1",
  "azure-cli-nspkg": "3.0.4",
  "azure-cli-telemetry": "1.0.4",
  "extensions": {}
}

Can we close this as a dupe of https://github.com/Azure/azure-cli/issues/11749?

Please close as a dupe :)


[WebView] scrollEnabled={false} doesn't work for .pdf in a WebView

I'm trying to disable scrolling inside a WebView that is showing a .pdf file. However, scrollEnabled  set to false does not disable it.
I've created a simple Snack example to demonstrate this: https://snack.expo.io/r1drA0Rt-
Versions I'm using

react-native: v0.47.0 (edit by @hramos: updated this to 0.47, as your Snack repro is using Expo 20.0 which is itself based on RN 0.47)
node v7.9.0
npm v4.2.0

Platform: iOS
OS: macOS Sierra 10.12.6

I was able to confirm that the repro occurs when a PDF is loaded, but not when a webpage is loaded (I used the RN website as an example).
I assume this is a case where iOS is taking over the display of the PDF, and the underlying UIWebView is unable to lock scrolling.
WebView is not currently owned by anyone, so a PR to fix this would be appreciated.


WIP: Adding support for warmstart CoreML in DC

This is a WIP PR to checkpoint the code for supporting loading warmstart CoreML model and plumbing through to C++ train().

What feedback are you looking for, with this WIP PR?

What feedback are you looking for, with this WIP PR?

Nothing yet. As I mentioned this is just to checkpoint where I am on this effort. Once the relevant pieces go in, I can test these changes. (In the meantime I'll context switch to help with SC)

For future reference, there's no need to open a PR if you just want to have a branch with your WIP

Please feel free to add reviewers when you want someone to review this

solve here. Could you merge master and then sanity check what happens when you train with the option enabled? And what is the state of the unit tests after this change?

Yes just merged master and resolved conflicts. I'll run the unit tests and check.

turicreate/test/test_drawing_classifier.py ............xxxx....................xxxx....................xxxx........


Added missing functions to moment.d.ts

Added missing isSameOrAfter and isSameOrBefore functions to typings

Thank you. Will be released in next version.

@ichernev when the next release is planned?

Merged in 5f93a8acc8a7ff57d7fb0ab9b7d703c4539f38c2


Change node addition and removal integration test to use maintenance mode

Node addition and removal with restarts should be done under maintenance mode.
We should also change accordingly in the integration test

PR #94


[Group 6][Accessible Pressable] Migrate AvatarCropModal

HOLD on https://github.com/Expensify/App/issues/16988
Description
Migrate AvatarCropModal to use PressableWithoutFeedback

Triggered auto assignment to @sakluger (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero process steps for feature requests for more details.

Can you assign me to this one, please?

I want to work on it.

I can work on this!

@tungmt Sorry, we've already hired someone to work on this. Please feel free to review our contributing guidelines and look for any issues that still have the Help Wanted label.

Hey @Skalakid looks like there are some outstanding change requests on the PR. Can you give an update on when you'll be able to resolve these?

Reapplying the Bug label to get another BZ member on this while I am OOO til June 30. Thanks @joekaufmanexpensify,  I'll grab this back from you when I return!

Sounds good!

The only payment that will be due here is $250 to @abdulrahuman5196

Not overdue. Waiting on PR approval from internal engineers.

PR merged yesterday

All set to issue $250 payment after regression reporting period on 2023-06-30!

All set to issue payment here! The PR here did take longer than 9 business days. However, it was approved by @abdulrahuman5196 within 9 business days. It got pushed beyond 9 business days while waiting for an internal review, so there'd be no penalty here.

@abdulrahuman5196 $250 sent and contract ended!

Closing as this is all set, thanks everyone!


[Compatibility] Chopdown Updated

A few people now have asked me to make my mod work with your trees to let the trees fall over.
Unfortunately as you handle the collapse of the tree before my mod can interrupt this is not so easy, also I am guessing there are a reasons you handle the trees collapse.
Could you have a look to see if there is a better solution than just me overriding your collapse method?
Curse page: https://minecraft.curseforge.com/projects/chop-down-updated

Having the trees fall over is on my todo list.  I highly recommend letting me implement it and telling those few people know that I will implement it on my side.  Thanks!

Sweet, the code I use is available on the git, if you want to view. Though as you have access to the actual tree shape you can probably implement a bit more defined method.
https://github.com/Shovinus/ChopDownUpdated

My plan is to capture the tree shape at the harvest event and make an entity from the data.  Then simply animate the entity falling over.  Once it hits the ground it will drop it's goodies and remove itself from the world.

Ahh I handle it differently because the whole point was to stop easy harvesting of trees like vein miner chopper mods do, instead just making it as immersive as possible, so you don't get any drops, the logs just fall to the ground, also deals with the issue of climbing large trees.

Yeah.  I get why your mod operates as it does.  It's probably the best idea for that paradigm.  I have to take a different approach for obvious reasons.

Can you add a config to stop the auto breaking of the tree? So I can try making fall?
On 25 Jun 2018 14:01, Ferreus Veritas<EMAIL_ADDRESS>wrote:
Yeah. I get why your mod operates as it does. It's probably the best idea for that paradigm. I have to take a different approach for obvious reasons.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/ferreusveritas/DynamicTrees/issues/92#issuecomment-399943532, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOYvhYfuuHGf6cnp-5Cc8T6ofZ4Mzbz1ks5uAN8mgaJpZM4U1vVi.

The problem is that Dynamic Trees does a summation of the wood volume for the entire tree(or cut off portion) to quantify the number of logs needed for the drop.  Also, the nodes of the tree must not come into contact with nodes from other trees.  So if you were to reassemble the tree sideways on the ground with all of its nodes being the right size and position without touching other trees you're going to have a hell of a time.  The best I could offer is to have a method to pass along the number of resulting logs to you somehow and you could make the horizontal falling trunk stack you use.  I caution that it would look weird though.

Here's how I would do it if I were you..
Dynamic Trees will send out a fireBlockHarvesting event on harvest.  This can be seen in com.ferreusveritas.dynamictrees.blocks.BlockBranch.java #removedByPlayer(...) line 315.
Simply subscribe to this event. If the event's blockstate is an instanceof DynamicTrees's BlockBranch then count and remove the log items in the list of itemStacks from the event and use the count to build your trunk made of falling log blocks.  You can determine the fall direction by the player position and the block position in the event.
If you do it properly then you won't need to include a hard dependency for dynamic trees and you won't have to break my mod in the process.

I will have to check that out, thank you,it is a hard problem to get around, maybe if I convert the blocked to a felled version and subsequent breaks return logs or sticks merely base on the size, i.e. above x drop a log, or else drop a stick or 2.
Which if you were actually chopping a tree is probably close, possibly smaller ones could actually just drop planks or "smaller logs" which create less planks per craft.

That's all fine and everything but it's a lot of complicated potentially bug prone craziness and a lot of work.  My suggestion could be done in about 20 minutes, wouldn't involve special blocks, would be more compatible and it would work just like the users of your mod expect and then you can move on to other things.  Eventually I'll make my trees fall anyway and you'll likely be disabling all the work you did.  At least implement my suggestion and decide later if you want to dig your own grave. :)


Eliminate OpenGL ES driver errors

Can you rebase and rename this PR to contain only the new changes, not those that were part of the previous PR?
FYI for the future it's a good idea to keep different PRs on different branches, that way if you're doing more work or independent changes then you can PR them separately without interference. If you have multiple chunks of work that build on each other, you can still keep working on a separate branch and then rebase it once the first PR is merged.

@baldurk I've rebased this branch. Thanks for your suggestion, I'll keep that in mind.

Manually merged.


Error installing: ValueError: numpy.dtype size changed

Having a lot of trouble installing FormFyxer on a fresh virtual env. Below is the error

    File "/tmp/pip-build-env-jyabgwzo/overlay/lib/python3.10/site-packages/thinc/backends/__init__.py", line 17, in <module>
     from .cupy_ops import CupyOps
  File "/tmp/pip-build-env-jyabgwzo/overlay/lib/python3.10/site-packages/thinc/backends/cupy_ops.py", line 16, in <module>
     from .numpy_ops import NumpyOps
   File "thinc/backends/numpy_ops.pyx", line 1, in init thinc.backends.numpy_ops
 ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

Related to https://github.com/explosion/spaCy/issues/13528, but I seem to be having the same error when I fix the version of numpy to below 2.0.0. Not sure why the obvious fix isn't working, but pip runs all of it in a temporary dir that gets deleted, so I can't see what actual code is being run there.
Workaround is just to remove the entire InstallSpacyModelCommand:
https://github.com/SuffolkLITLab/FormFyxer/blob/fce844760001c8998a3d40765bf894cf4f7d50cd/setup.py#L9-L14
That workaround won't fly for our situation, but I'll have to see if it breaks our GH actions as well, or if it's just on my machine.

An example of the build failure: https://github.com/SuffolkLITLab/FormFyxer/actions/runs/9540258846/job/26291740248?pr=136

Figured out a local fix: from the thinc docs, you can specify build constraints. I think since we're running spacy while building/installing formfyxer, the normal fix of "just use numpy<2.0.0" doesn't work because of how pip installs dependencies when building packages. Can't fully articulate, but if you run:
PIP_CONSTRAINT=build-constraints.txt pip install . --no-cache-dir

with build-constraints.txt as:
numpy==1.26.4

it works.
Happy to hear additional approaches, but I think the best way to fix this at the moment is to patch ALActions to have a similar build-constraints.txt in it, and then use it when building everything. It shouldn't matter for most repos, but I think this spacy / thinc / numpy issue will pop up in a few different places.

Okay, with https://github.com/SuffolkLITLab/ALActions/pull/26, this should be fixed on CI/CD.  Not sure if we should add something to the docs saying that pip install . won't work though.
TBH, I'm sure this will start affecting a few people come this week, and spacy and thinc might come up with better workarounds, so I might keep this open just to wait for those.


train.csv and valid.csv could not be found in the repo

Dear Authors,
I wanted to train the model on the PMC-OA dataset, but I couldn't locate train.csv and valid.csv in the codebase. There was no explanation on this in the documentation so, could you please elaborate more on this?
Thanks,
Kidus

Hi @kidus-admassu , the train.csv and valid.csv is to illustrate the training and validation set. We refer you to PMC-OA Dataset which is released for PMC-CLIP pretraining.

Notice that PMC-OA is a rather large dataset, if you just want to validate the code, you could use ROCO as input data.


Document contribution guide and related activities

Description
This PR adds a CONTRIBUTORS.md file, updates the README with useful information for developers, and updates the provided Taskfile.yml.
Testing
Refer to the README's new Quick Reference section and ensure the listed commands work as-described.
Manual tests for Reviewer

[ ] Added steps to test feature/functionality manually

Checklist

[x] Provided ticket and description
[x] Provided testing information
[x] Provided adequate test coverage for all new code
[x] Added PR reviewers

Looks great! Just some suggestions relative to CONTRIBUTING.md. It's a good practice to ventilate prose, or write one sentence per line, because the raw text is clearer for reviewing. The other good thing is that the file will look the same when previewed.

Thanks for the review and excellent feedback, @CelesteChang! I applied all of your suggestions; the call-out for ventilated prose is especially useful – something I wasn't previously familiar with but makes a lot of sense. I've always been focused on line-length for markdown changes, but after looking at the results, I'd agree this is much easier to read 😄
Thanks again!


Enhancement: Update vimeo/psalm

This pull request

[x] updates vimeo/psalm
[x] runs make static-code-analysis-baseline

Codecov Report
Base: 80.32% // Head: 80.32% // No change to project coverage :thumbsup:

Coverage data is based on head (3edd692) compared to base (1bde397).
 Consider uploading reports for the commit 76ebcac to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #265   +/-   ##
=========================================
  Coverage     80.32%   80.32%
  Complexity      749      749
=========================================
  Files            55       55
  Lines          2602     2602
=========================================
  Hits           2090     2090
  Misses          512      512

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


depthEqual Proposal

Proposal for a new shouldComponent helper called depthEqual
I have a situation where I'd like to be able to efficiently pass nested object literals to a component, here's a contrived simple example:
<Point position={{x: this.state.pointX, y: this.state.pointY}} />

Ideally the Point component could have a shouldComponentUpdate method that would prevent re-rendering if props.position.x and props.position.y remained the same, even if the props.position reference changed. This is a bit difficult with the current API.
This PR adds a new function called depthEqual to the API, which is just like shallowEqual except that it allows you to pass a third argument depth which specifies how many nested object layers should be checked for reference equality. depthEqual(a, b, 0) is equivalent to a === b, and depthEqual(a, b, 1) is equivalent to shallowEqual(a, b). The default depth argument is 1.
This would allow the Point class to implement a shouldComponentUpdate like:
class Point extends React.Component {
  shouldComponentUpdate(nextProps) {
    return !depthEqual(this.props, nextProps, 2);
  }
}

Generally you would want to optimize performance by checking some props shallowly and some deeply, using something like _.pick and _.omit, but this is just a simple example. Hopefully you think this is useful - object literal props are an anti-pattern sometimes but I think they have legitimate use cases too.
A couple notes - I added a unit test but I couldn't get it to work using import depthEqual from 'recompose' like the other unit tests do. It seems like that syntax imports from the npm installed version, how do you test your code in development? Do you npm link it to itself or something? I just used ../ syntax for now to get it to pass.
Also I updated shallowEqual to call depthEqual but left the existing unit tests in place, so there may be some duplication there. Feel free to clean some of these out if you think it's appropriate.
Thanks for taking a look!
-dan

Current coverage is 100.00%

Merging #120 into master will not affect coverage as of 9c0bb93

@@            master    #120   diff @@
======================================
  Files           42      43     +1
  Stmts          312     316     +4
  Branches         0       0
  Methods          0       0
======================================
+ Hit            312     316     +4
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 9c0bb93

Powered by Codecov. Updated on successful CI builds.

Thank you, as I know it is not well known equality check, and can cause some misunderstanding.
recompose allows you to make your checks without this addition

just use recompose shouldUpdate HOC to prevent update if point values has not changed

Also you could not change object reference if it properties has not changed - in most situation you could easily avoid your behavior on data level.

Thanks for the PR! Because, as @istarkov says, it's fairly easy to implement this type of helper using shouldUpdate, I would prefer not to add to the API.
Perhaps additional docs around shouldUpdate would be helpful, though.

I wrote a depth equal using shallowEqual here - https://github.com/acdlite/recompose/issues/440

I only ever needed depth of 0 or 1 so got rid of the above in favor of this:
export depth0Or1Equal(obj1, obj2, depth1Keys={}) {
    // depth1Keys is objecect of keys you want to test at depth of 1, by default test depth of 0. value can be anything.
    const keys1 = Object.keys(obj1);
    const keys2 = Object.keys(obj2);
    if (keys1.length !== keys2.length) return false;

    for (const key of keys1) {
        if (!(key in obj2)) return false;

        const val1 = obj1[key];
        const val2 = obj2[key];
        if (key in depth1Keys) {
            if (!shallowEqual(val1, val2)) return false;
        } else {
            if (val1 !== val2) return false;
        }
    }

    return true;

}

Usage:
depth0Or1Equal({a:[]}, {a:[]}) === false
depth0Or1Equal({a:[]}, {a:[]}, {a:1}) === true


[Bug]: Build fails with a fresh project

Describe the bug
The build fails with a unchanged new project.
Steps to Reproduce

Install the Evidence vsCode extension
Create new project
Install dependencies
Build project

Logs
node:internal/event_target:1012
  process.nextTick(() => { throw err; });
                           ^
Error: 500 /api//explore/console/evidencemeta.json (fetched from /explore/console/)
To suppress or handle this error, implement `handleHttpError` in https://kit.svelte.dev/docs/configuration#prerender
    at file:///workspaces/Backend-API/Evidence/node_modules/@sveltejs/kit/src/core/config/options.js:202:13
    at file:///workspaces/Backend-API/Evidence/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:65:25
    at save (file:///workspaces/Backend-API/Evidence/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:403:4)
    at visit (file:///workspaces/Backend-API/Evidence/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:260:4)
Emitted 'error' event on Worker instance at:
    at [kOnErrorMessage] (node:internal/worker:300:10)
    at [kOnMessage] (node:internal/worker:311:37)
    at MessagePort.<anonymous> (node:internal/worker:212:57)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:737:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)

Node.js v18.16.0
Build failed

file:///workspaces/Backend-API/Evidence/node_modules/@evidence-dev/evidence/cli.js:190
                        throw `Build process exited with code ${code}`;
                        ^
Build process exited with code 1
(Use `node --trace-uncaught ...` to show where the exception was thrown)

Node.js v18.16.0

System Info
Node.js v18.16.0
npm v9.5.1
Inside Github codespaces

Severity
blocking all usage of Evidence
Additional Information, or Workarounds
I'm vetting new BI tools and I really liked Evidence. But with the build failing on a fresh unchanged project, I don't know how to move forward

Hi @RoeeEidan i haven’t been able to reproduce this using the template repo in GitHub.
can you try creating a project from the use template button here and see if that’s different? https://github.com/evidence-dev/template

Thanks for the quick response @hughess!  I tried the template and it didn't fix it.
Although, I did make some progress getting to the bottom of this.
I'm currently experiencing the issue in my github codespace mono repo, and I can confirm that the issue is not happening on my local machine.  So it must be either because of the monorepo, or the codespace.
I'll try the mono repo on my local to check what it is.

It worked inside a monorepo on my local machine, so its something to do with my codespace setup

This is also happening when I try to build the template in production..
Here is the output when running npx evidence build --debug
Evidence running with debug logging
vite v5.4.6 building SSR bundle for production...
✓ 1448 modules transformed.
vite v5.4.6 building for production...
transforming (42) ../../node_modules/svelte/src/runtime/store/index.jsUpdating Parquet URLs
transforming (996<EMAIL_ADDRESS>failed

file:///home/ec2-user/Backend-API/Evidence/node_modules/@evidence-dev/evidence/cli.js:190
                        throw `Build process exited with code ${code}`;
                        ^
Build process exited with code null
(Use `node --trace-uncaught ...` to show where the exception was thrown)

Node.js v18.20.4

When I run it in AWS CodeBuild, I get the following output

><EMAIL_ADDRESS>build
--
60 | > evidence build
61 |
62 | vite v5.4.6 building SSR bundle for production...
63 | transforming...
64 | ✓ 1448 modules transformed.
65 | rendering chunks...
66 | vite v5.4.6 building for production...
67 | transforming...
68 | ✓ 4447 modules transformed.
69 | rendering chunks...
70 | computing gzip size...
71 | .svelte-kit/output/client/_app/version.json                                                                 0.03 kB │ gzip:     0.05 kB
72 | .svelte-kit/output/client/_app/immutable/assets/wordmark-gray-800.CnzB_64T.png                             11.87 kB
73 | .svelte-kit/output/client/.vite/manifest.json                                                              32.75 kB │ gzip:     3.09 kB
74 | .svelte-kit/output/client/_app/immutable/assets/Spectral-ExtraLight.HPQmpGpQ.woff2                         55.57 kB
75 | .svelte-kit/output/client/_app/immutable/assets/Spectral-ExtraLightItalic.xW7ezc0a.woff2                   58.00 kB
76 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Regular.BE1HJwUh.woff2                            58.09 kB
77 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Italic.wSPWDyg7.woff2                             58.78 kB
78 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Light.TIhg4DnI.woff2                              58.91 kB
79 | .svelte-kit/output/client/_app/immutable/assets/Spectral-ExtraBold.DeRaT2m-.woff2                          59.18 kB
80 | .svelte-kit/output/client/_app/immutable/assets/Spectral-ExtraBoldItalic.MQ9B1Gco.woff2                    59.74 kB
81 | .svelte-kit/output/client/_app/immutable/assets/Spectral-LightItalic.zW0f9iJS.woff2                        60.67 kB
82 | .svelte-kit/output/client/_app/immutable/assets/Spectral-SemiBold.zu1TM2FZ.woff2                           60.88 kB
83 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Medium.NsGaEaui.woff2                             61.13 kB
84 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Bold.BwJz_A1v.woff2                               61.29 kB
85 | .svelte-kit/output/client/_app/immutable/assets/Spectral-MediumItalic.BvSK_s7Y.woff2                       61.88 kB
86 | .svelte-kit/output/client/_app/immutable/assets/Spectral-SemiBoldItalic.D3fgUf4W.woff2                     62.13 kB
87 | .svelte-kit/output/client/_app/immutable/assets/Spectral-BoldItalic.CQC_WCFZ.woff2                         62.16 kB
88 | .svelte-kit/output/client/_app/immutable/assets/Spectral-ExtraLight.HAWHIZWB.woff                          69.52 kB
89 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Regular.C0aqGnDS.woff                             72.05 kB
90 | .svelte-kit/output/client/_app/immutable/assets/Spectral-ExtraLightItalic.C9nFbxmj.woff                    72.68 kB
91 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Light.DBct1VnS.woff                               72.94 kB
92 | .svelte-kit/output/client/_app/immutable/assets/Spectral-ExtraBold.Dm6k0JyR.woff                           73.01 kB
93 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Italic.3s0_PsVL.woff                              73.28 kB
94 | .svelte-kit/output/client/_app/immutable/assets/Spectral-ExtraBoldItalic.SZr5i_vZ.woff                     74.36 kB
95 | .svelte-kit/output/client/_app/immutable/assets/Spectral-SemiBold.CCUIByHq.woff                            75.12 kB
96 | .svelte-kit/output/client/_app/immutable/assets/Spectral-LightItalic.B3o_X74d.woff                         75.20 kB
97 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Medium.BZl4fq6u.woff                              75.20 kB
98 | .svelte-kit/output/client/_app/immutable/assets/Spectral-Bold.C57huwyI.woff                                75.81 kB
99 | .svelte-kit/output/client/_app/immutable/assets/Spectral-MediumItalic.De40Wj9n.woff                        76.62 kB
100 | .svelte-kit/output/client/_app/immutable/assets/Spectral-SemiBoldItalic.DjbDqXej.woff                      76.77 kB
101 | .svelte-kit/output/client/_app/immutable/assets/Spectral-BoldItalic.CQquRzSI.woff                          76.91 kB
102 | .svelte-kit/output/client/_app/immutable/assets/Inter-Regular.CKDp9E3C.woff2                               98.87 kB
103 | .svelte-kit/output/client/_app/immutable/assets/Inter-Thin.CSJ_owlW.woff2                                  99.63 kB
104 | .svelte-kit/output/client/_app/immutable/assets/Inter-Black.DgUKMdlB.woff2                                102.87 kB
105 | .svelte-kit/output/client/_app/immutable/assets/Inter-ExtraLight.egkqWonf.woff2                           104.23 kB
106 | .svelte-kit/output/client/_app/immutable/assets/Inter-Light.CdXm_ABL.woff2                                104.33 kB
107 | .svelte-kit/output/client/_app/immutable/assets/Inter-SemiBold.Ctx7G98q.woff2                             105.80 kB
108 | .svelte-kit/output/client/_app/immutable/assets/Inter-Medium.P1cOs5ep.woff2                               105.92 kB
109 | .svelte-kit/output/client/_app/immutable/assets/Inter-ExtraBold.B0QOs-T2.woff2                            106.11 kB
110 | .svelte-kit/output/client/_app/immutable/assets/Inter-Bold.CuhepTt8.woff2                                 106.14 kB
111 | .svelte-kit/output/client/_app/immutable/assets/Inter-ThinItalic.B6FKq6qK.woff2                           106.50 kB
112 | .svelte-kit/output/client/_app/immutable/assets/Inter-Italic._3PMmu0i.woff2                               106.88 kB
113 | .svelte-kit/output/client/_app/immutable/assets/Inter-BlackItalic.ZFcDzO3e.woff2                          108.75 kB
114 | .svelte-kit/output/client/_app/immutable/assets/Inter-LightItalic.COmGGTuG.woff2                          111.33 kB
115 | .svelte-kit/output/client/_app/immutable/assets/Inter-ExtraLightItalic.Bf25KIHs.woff2                     111.39 kB
116 | .svelte-kit/output/client/_app/immutable/assets/Inter-ExtraBoldItalic.OErwaGem.woff2                      111.71 kB
117 | .svelte-kit/output/client/_app/immutable/assets/Inter-BoldItalic.R15IsAnq.woff2                           111.81 kB
118 | .svelte-kit/output/client/_app/immutable/assets/Inter-SemiBoldItalic.BNz1Al2H.woff2                       112.05 kB
119 | .svelte-kit/output/client/_app/immutable/assets/Inter-MediumItalic.DWiIAHvp.woff2                         112.18 kB
120 | .svelte-kit/output/client/_app/immutable/assets/Inter-Regular.DJOZHnwz.woff                               133.84 kB
121 | .svelte-kit/output/client/_app/immutable/assets/Inter-Thin.CVMZtQER.woff                                  135.92 kB
122 | .svelte-kit/output/client/_app/immutable/assets/Inter-Black.DtxVgCT8.woff                                 138.76 kB
123 | .svelte-kit/output/client/_app/immutable/assets/Inter-Light.CG9upfZ4.woff                                 140.63 kB
124 | .svelte-kit/output/client/_app/immutable/assets/Inter-ExtraLight.CbFdmbHh.woff                            140.72 kB
125 | .svelte-kit/output/client/_app/immutable/assets/Inter-Medium.oHczPpWt.woff                                142.55 kB
126 | .svelte-kit/output/client/_app/immutable/assets/Inter-ExtraBold.B8imQN9B.woff                             142.92 kB
127 | .svelte-kit/output/client/_app/immutable/assets/Inter-SemiBold.BHlX_6qk.woff                              142.93 kB
128 | .svelte-kit/output/client/_app/immutable/assets/Inter-Bold.2PT7Q-hu.woff                                  143.21 kB
129 | .svelte-kit/output/client/_app/immutable/assets/Inter-Italic.Ci_5KQU1.woff                                144.37 kB
130 | .svelte-kit/output/client/_app/immutable/assets/Inter-ThinItalic.B2bFwwDp.woff                            145.48 kB
131 | .svelte-kit/output/client/_app/immutable/assets/Inter-BlackItalic.CkZ-ktDH.woff                           146.82 kB
132 | .svelte-kit/output/client/_app/immutable/assets/Inter-ExtraLightItalic.B3gY-m5W.woff                      150.00 kB
133 | .svelte-kit/output/client/_app/immutable/assets/Inter-LightItalic.C2ZuFZOC.woff                           150.09 kB
134 | .svelte-kit/output/client/_app/immutable/assets/Inter-ExtraBoldItalic.Bt8eprh6.woff                       150.63 kB
135 | .svelte-kit/output/client/_app/immutable/assets/Inter-MediumItalic.8laNK8GF.woff                          150.99 kB
136 | .svelte-kit/output/client/_app/immutable/assets/Inter-BoldItalic.C906RMVC.woff                            151.05 kB
137 | .svelte-kit/output/client/_app/immutable/assets/Inter-SemiBoldItalic.CxeAX7g8.woff                        151.18 kB
138 | .svelte-kit/output/client/_app/immutable/workers/duckdb-browser-eh.worker-DT-uzeza.js                     262.80 kB
139 | .svelte-kit/output/client/_app/immutable/workers/duckdb-browser-mvp.worker-DgEo6Ag5.js                    315.60 kB
140 | .svelte-kit/output/client/_app/immutable/assets/duckdb-eh.Bbw6HAmJ.wasm                                18,105.92 kB
141 | .svelte-kit/output/client/_app/immutable/assets/duckdb-mvp.IKz61icS.wasm                               22,092.38 kB
142 | .svelte-kit/output/client/_app/immutable/assets/0.Cc7Yja0k.css                                             67.47 kB │ gzip:    12.17 kB
143 | .svelte-kit/output/client/_app/immutable/assets/VennDiagram.BUbR3Yec.css                                   75.66 kB │ gzip:    16.92 kB
144 | .svelte-kit/output/client/_app/immutable/chunks/index.BrBg7kRw.js                                           0.04 kB │ gzip:     0.06 kB
145 | .svelte-kit/output/client/_app/immutable/entry/start.76WJIjt9.js                                            0.07 kB │ gzip:     0.08 kB
146 | .svelte-kit/output/client/_app/immutable/chunks/duckdb-eh.CFvZubNE.js                                       0.10 kB │ gzip:     0.12 kB
147 | .svelte-kit/output/client/_app/immutable/chunks/duckdb-mvp.CbpRbetm.js                                      0.10 kB │ gzip:     0.12 kB
148 | .svelte-kit/output/client/_app/immutable/chunks/duckdb-browser-eh.worker.Cbrkkz2F.js                        0.17 kB │ gzip:     0.16 kB
149 | .svelte-kit/output/client/_app/immutable/chunks/duckdb-browser-mvp.worker.Bw9aQXtH.js                       0.17 kB │ gzip:     0.16 kB
150 | .svelte-kit/output/client/_app/immutable/nodes/2.DQdzPajs.js                                                0.27 kB │ gzip:     0.22 kB
151 | .svelte-kit/output/client/_app/immutable/chunks/stores.B1iul3T9.js                                          0.29 kB │ gzip:     0.18 kB
152 | .svelte-kit/output/client/_app/immutable/nodes/3.BHdo2M7c.js                                                1.02 kB │ gzip:     0.61 kB
153 | .svelte-kit/output/client/_app/immutable/chunks/preload-helper.C1FmrZbK.js                                  1.14 kB │ gzip:     0.68 kB
154 | .svelte-kit/output/client/_app/immutable/chunks/updater.D06dw969.js                                         1.30 kB │ gzip:     0.73 kB
155 | .svelte-kit/output/client/_app/immutable/chunks/prism-python.DhmbaUsA.js                                    2.11 kB │ gzip:     1.09 kB
156 | .svelte-kit/output/client/_app/immutable/chunks/prism-svelte.DAwacStd.js                                    2.97 kB │ gzip:     0.96 kB
157 | .svelte-kit/output/client/_app/immutable/chunks/prism-sql.AgAyy5H_.js                                       3.26 kB │ gzip:     1.85 kB
158 | .svelte-kit/output/client/_app/immutable/chunks/prism-markdown.4MKFcK2x.js                                  5.24 kB │ gzip:     2.01 kB
159 | .svelte-kit/output/client/_app/immutable/chunks/prism-bash.DTkDXsAh.js                                      6.15 kB │ gzip:     3.04 kB
160 | .svelte-kit/output/client/_app/immutable/chunks/Button.CI11lQC2.js                                          8.05 kB │ gzip:     2.25 kB
161 | .svelte-kit/output/client/_app/immutable/chunks/Prismjs.C5ZtoCO9.js                                         8.44 kB │ gzip:     3.79 kB
162 | .svelte-kit/output/client/_app/immutable/chunks/index.BapEyOSa.js                                           9.40 kB │ gzip:     4.41 kB
163 | .svelte-kit/output/client/_app/immutable/nodes/1.Co-yTk3D.js                                               10.65 kB │ gzip:     3.78 kB
164 | .svelte-kit/output/client/_app/immutable/nodes/5.CDKhf8_H.js                                               10.88 kB │ gzip:     3.80 kB
165 | .svelte-kit/output/client/_app/immutable/chunks/scheduler.0nfGLaU7.js                                      11.26 kB │ gzip:     4.47 kB
166 | .svelte-kit/output/client/_app/immutable/nodes/6.D_na9QlM.js                                               12.42 kB │ gzip:     4.45 kB
167 | .svelte-kit/output/client/_app/immutable/entry/app.8ib1bsjj.js                                             14.28 kB │ gzip:     3.68 kB
168 | .svelte-kit/output/client/_app/immutable/chunks/entry.BK231WYM.js                                          33.67 kB │ gzip:    13.40 kB
169 | .svelte-kit/output/client/_app/immutable/chunks/button.D8cXa4Nh.js                                         40.48 kB │ gzip:    14.31 kB
170 | .svelte-kit/output/client/_app/immutable/chunks/AccordionItem.Bccw-NmC.js                                  50.94 kB │ gzip:     9.95 kB
171 | .svelte-kit/output/client/_app/immutable/nodes/7.yKK0c9_Z.js                                              239.95 kB │ gzip:    62.88 kB
172 | .svelte-kit/output/client/_app/immutable/nodes/0.DSj2T-l4.js                                              454.79 kB │ gzip:   101.08 kB
173 | .svelte-kit/output/client/_app/immutable/nodes/4.D0e8oO2D.js                                              520.56 kB │ gzip:    91.24 kB
174 | .svelte-kit/output/client/_app/immutable/chunks/VennDiagram.svelte_svelte_type_style_lang.Dfv6cJ0R.js   2,588.12 kB │ gzip:   788.22 kB
175 | .svelte-kit/output/client/_app/immutable/chunks/index.C6bJmPCA.js                                       5,163.93 kB │ gzip: 2,003.06 kB
176 |
177 | (!) Some chunks are larger than 500 kB after minification. Consider:
178 | - Using dynamic import() to code-split the application
179 | - Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
180 | - Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
181 | ✓ built in 49.06s
182 |
183 | node:internal/event_target:1062
184 | process.nextTick(() => { throw err; });
185 | ^
186 | Error: 500 /api//explore/console/evidencemeta.json (fetched from /explore/console/)
187 | To suppress or handle this error, implement `handleHttpError` in https://kit.svelte.dev/docs/configuration#prerender
188 | at file:///codebuild/output/src3688105107/src/github.com/Carbon-Neutral-Club/Evidence/node_modules/@sveltejs/kit/src/core/config/options.js:202:13
189 | at file:///codebuild/output/src3688105107/src/github.com/Carbon-Neutral-Club/Evidence/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:65:25
190 | at save (file:///codebuild/output/src3688105107/src/github.com/Carbon-Neutral-Club/Evidence/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:403:4)
191 | at visit (file:///codebuild/output/src3688105107/src/github.com/Carbon-Neutral-Club/Evidence/node_modules/@sveltejs/kit/src/core/postbuild/prerender.js:260:4)
192 | Emitted 'error' event on Worker instance at:
193 | at [kOnErrorMessage] (node:internal/worker:314:10)
194 | at [kOnMessage] (node:internal/worker:325:37)
195 | at MessagePort.<anonymous> (node:internal/worker:225:57)
196 | at [nodejs.internal.kHybridDispatch] (node:internal/event_target:786:20)
197 | at exports.emitMessage (node:internal/per_context/messageport:23:28)
198 |
199 | Node.js v18.20.3
200 | Build failed
201 |
202 | file:///codebuild/output/src3688105107/src/github.com/Carbon-Neutral-Club/Evidence/node_modules/@evidence-dev/evidence/cli.js:190
203 | throw `Build process exited with code ${code}`;
204 | ^
205 | Build process exited with code 1
206 | (Use `node --trace-uncaught ...` to show where the exception was thrown)
207 |
208 | Node.js v18.20.3

It seems like it build the project, but then fails to save it

Here's the error in --debug mode
{
  "error": {
    "message": "ENOENT: no such file or directory, open '/codebuild/output/src3395401549/src/github.com/Carbon-Neutral-Club/Evidence/.evidence/template/src/pages/explore/console/+page.md'",
    "errno": -2,
    "code": "ENOENT",
    "syscall": "open",
    "path": "/codebuild/output/src3395401549/src/github.com/Carbon-Neutral-Club/Evidence/.evidence/template/src/pages/explore/console/+page.md"
  },
  "event": {
    "cookies": {
      "get": "[Function: get]",
      "getAll": "[Function: getAll]",
      "set": "[Function: set]",
      "delete": "[Function: delete]",
      "serialize": "[Function: serialize]"
    },
    "fetch": "[Function (anonymous)]",
    "getClientAddress": "[Function: getClientAddress]",
    "locals": {},
    "params": {
      "route": "/explore/console"
    },
    "platform": null,
    "request": {
      "[Symbol(realm)]": "[Object]",
      "[Symbol(state)]": "[Object]",
      "[Symbol(signal)]": "[AbortSignal]",
      "[Symbol(headers)]": "[HeadersList]"
    },
    "route": {
      "id": "/api/[...route]/evidencemeta.json"
    },
    "setHeaders": "[Function: setHeaders]",
    "url": {
      "href": "http://sveltekit-prerender/api//explore/console/evidencemeta.json",
      "origin": "http://sveltekit-prerender",
      "protocol": "http:",
      "username": "",
      "password": "",
      "host": "sveltekit-prerender",
      "hostname": "sveltekit-prerender",
      "port": "",
      "pathname": "/api//explore/console/evidencemeta.json",
      "search": "",
      "searchParams": {},
      "hash": ""
    },
    "isDataRequest": false,
    "isSubRequest": true
  },
  "status": 500,
  "message": "Internal Error"
}

Turns out this issue happens when NODE_ENV is set (to development in Codespaces, and staging in CodeBuild).
I was able to get the build working by removing the NODE_ENV variable.
It might be more of an issue with svelte as opposed to evidence

Closing this issue as it's been resolved by removing the NODE_ENV variable.
I think it would be a nice addition if the build would have thrown a clear error, or even a warning.
I enjoy using evidence and likely going to hear from me again 😄
Happy halloween 🎃


Allow bb to be sf object

Allow user to pass sf object instead of vector for defining bb

Added as_bb() function will handles the conversion of spatial bounding box objects from terra and sf to [left, right, bottom, top].


integrationtests: fix numpy version problem (broken Jenkins)

During px4tools installation the latest version of pandas is installed, which requires numpy>=1.9.0. Pandas installs the required version, however, due to the presence of the old numpy in the docker image, the present version 1.8.2 is used, which leads to an error when importing pandas. It's one of the causes of Jenkins SITL fails.
This PR fixes the problem explicitly upgrading numpy with pip before px4tools installation.
@dagar, please review.

Thank you!


Configure query class as follows?

Hello,
I am just switching to yii2 from yii1, so it might be that I have a general problem of understanding.
You write "Configure query class as follows". But I do not have a query class.
I am using the advanced yii2 template.
Can you give me a hint where that has to be put?
Thanks,
gb5256

So you should create a class like this
https://github.com/Mihai-P/yii2-core/blob/master/components/NestedQuery.php
And in the actual model you should declare something like this https://github.com/Mihai-P/yii2-core/blob/master/models/Menu.php
see the behaviors, transactions and find functions.
The NestedQuery allows you operations like
$leaves = Menu::find()->leaves()->all();
$children = $countries->children()->all();

Thanks for this.
The missing point was where to put it and to use
use core\components\NestedQuery;
inside the model.
PS: I am a very happy user of your yii1 nested set (and now also of this one as it seems...)
Thanks again,
gb5256


issues with event-driven tutorials

Please leave feedback on tutorials here:

mistakes
missing steps
missing tutorials
changing a method to an improved version

Personally, I find a bit difficult reading the README of the documentation because of the many new lines. I understand the intention of highlighting the links to the tutorials, but the line breaking looks un-natural and the links are already sufficiently visible thanks to the different text colouring.
I would prefer something like this, instead:
Hardware

Hardware could include sensors: ATIS, event-driven skin, cochlea, or IMU, as well as acquisition boards based on zynq chips: ZCB or z-turn. We'll assume the hardware is correctly connected and powered. However, you may need to set-up an sd-card for a ZCB or z-turn.

If the system should be already ready-to-go, and you just need the board to start acquisition, you can follow these instructions to connect to the ZCB or z-turn.

Once you have a connection to the board, you need to set-up the yarpserver to correctly communicate between your laptop and the board.

Finally you will need to run zynqGrabber.

At this point, if you have checked your hardware is streaming events, you can start to read and process them, once your software is correctly installed on the laptop as well.

There is a styling issue in line 27 of 1viewer.md.
Instead of using blockquotes:

yarp namespace /

It would be better to use code blocks:
yarp namespace /<yourname>

In this way, code is nicely highlighted (not YARP related keywords, tough) and special symbols should not disappear due to markdown styling.

On the Testing your install with the viewer tutorial 1viewer.md.
The first commands seem to be for both testing with the dataset and camera:
download the sample dataset from here and unpack to a location of your choosing.
set the yarp namespace
yarp namespace /
run a yarpserver
yarpserver --write
These commands could be moved to the section Using actual hardware/camera? Skip ahead. Using a dataset? Follow these instructions:

For easy changes (e.g. adding link, typos, etc.), I would suggest to make a new branch with the suggested changes and see the difference with respect to cmake_update branch by making a PR. In this way, as long as someone else checks the PR, half of the work is already done!
I tried to do so for 1viewer.md, see PR #30.
What do you think about it @arrenglover?

On Writing an example module for event-driven tutorial example_module.md
While personalizing the project, a command to change the name of the example-module.ini file is missing:
mv example-module.ini <my-module-name>.ini

For easy changes (e.g. adding link, typos, etc.), I would suggest to make a new branch with the suggested changes and see the difference with respect to cmake_update branch by making a PR. In this way, as long as someone else checks the PR, half of the work is already done!
I tried to do so for 1viewer.md, see PR #30.
What do you think about it @arrenglover?

It's a good idea. feel free to put all changes into a PR. I would like to perform the update to devel tomorrow.

While personalizing the project, commands to change the name of the example-module.ini and app_example-module.xml are missing:
mv example-module.ini <my-module-name>.ini
mv app_example-module.xml app_<my-module-name>.xml

@lsrosa I think I applied the changes you suggested in PR #30, could you please double check?

While personalizing the project, commands to change the name of the example-module.ini and app_example-module.xml are missing:
mv example-module.ini <my-module-name>.ini
mv app_example-module.xml app_<my-module-name>.xml

@lsrosa I think I applied the changes you suggested in PR #30, could you please double check?

@aikolina great. However, maybe we can change the three lines

mv <my-module-name>/example-module.cpp <my-module-name>/<my-module-name>.cpp
mv example-module.ini <my-module-name>.ini
mv app_example-module.xml app_<my-module-name>.xml

to
rename '~s/example-module/<my-module-name>/g' *, if rename is not installed: sudo apt-get install rename
We can suggest to sed the lines on the CMakelists and .cpp files as well, but sed is dangerous (regex are not reversible) and I think that is good for the user/developer to spot where these definitions are in the code.

On the Writing an example module for event-driven tutorial
There are some definitions in the example-module that were not updated to , resulting in both names mixed in the yarpmanager. It follows the extra necessary modifications:

Add line 24 to the list of lines to be changed on .cpp file

On line 7, 19, and 124 change the class, constructor and declaration to .
ctrl+o, ctrl+x

Add to change the first line of file .ini
name /example-module → name /<my-modulo-name>

Add to change all entries of file app_.xml, here the sed command will be useful
sed -n  's/example-module/<my-modulo-name>/g' <my-modulo-name>.xml

After this, the entries in the yarpmanager display the correct name (<my-module-name>)

@lsrosa Can you make all the changes you suggested to the Writing an example module for event-driven tutorial on the PR I'm working on too? Thanks!

Thanks @aikolina  and @lsrosa. I've pulled in your changes up to here. I made a change to the install process. Can someone check the new version works?


Duplicate installation due to user install

Is there a way to disable user installation or to redirect it to normal installation ?

This is an gem issue not bundler.

Oh I mixed both in my head sorry ;)


GPU metric

When would GPU metrics be available for Virtual Machines, I only se it being available for Machine learning workspaces

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

ID: a0a586c4-71fd-e60b-9c4c-1a3eb2443c74
Version Independent ID: 2f3706cc-073b-a310-8da4-2a5a90da6473
Content: Azure Monitor supported metrics by resource type - Azure Monitor
Content Source: articles/azure-monitor/platform/metrics-supported.md
Service: azure-monitor
Sub-service: metrics
GitHub Login: @anirudhcavale
Microsoft Alias: ancav

Is there a way to log GPU Metrics of N Series Azure VMs into Log Analytics Workspaces? If so, how?
If not, how to do collect GPU Metrics using API or Azure CLI/Powershell Commands?

@EarthlyAlien Please open a new issue or post a question here https://social.msdn.microsoft.com/Forums/azure/en-US/home?forum=opinsights

@vrat87 Generally new features are announced in Azure updates https://azure.microsoft.com/en-in/updates/  you can filter by services.
Since this feature is not there already, you can submit a feedback here https://feedback.azure.com/forums/216843-virtual-machines
Product teams looks into these items and build their backlog.  Community can vote for this feature as well.

I will close this out for now. If you need additional help please open a new issue


API for adding classes/properties at runtime

I'd like a way to add classes and properties to cromulent.model at runtime. This would be akin to what would happen if I added rows to crm_vocab.tsv, but with the flexibility to do it conditionally (dependent on the calling code, specific script being run, etc.).
The code in cromulent.model that builds the classes does not seem to be easily extended to incrementally add classes or properties. It is rather tightly coupled with the TSV parsing/loading code, and also seems to depend on ephemeral data that is loaded from the TSV file, but not persisted once the class building process is done. If this code could be decoupled and improved to allow incremental class building, new data could be provided either as an additional TSV file (or equivalent without having to actually touch the filesystem), or in an already-processed form similar to what the process_tsv function produces.

On the property customization side of this, recently I needed to adjust the domain / range or multiplicity of a property without necessarily changing it for all classes. Since props are carried in class instance scope and validation happens at prop assignment we used a runtime patch that reconfigured the prop while we were using the off-book definition:
def unsafe_set_crom_prop(prop: str, entity: Any, value: Any, predicate: str, inverse_property=None, inverse_predicate=None, multiple_okay=True, profile_okay=1):
    entity._all_properties[prop] = model.PropInfo(property=prop, predicate=predicate, range=type(value), inverse_property=inverse_property, inverse_predicate=inverse_predicate, multiple_okay=multiple_okay, profile_okay=profile_okay)
    setattr(entity,prop,value)
    del entity._all_properties[prop]

Not pretty but it was nice to know we could keep things in the runtime since I found reasoning about the TSV table beyond my skills at the time. Might warrant a belt-and-suspenders approach to model customization (ie, both TSV configs and patches)?


the game does'nt init because an error appears

You have likely imported the library incorrectly, or have upgraded from an older version of Input incorrectly. Delete the entire Input folder in your project and re-import.


1.26.0 upgrade: Add tool_resources to assistants and threads

Examples:

asst = client.beta.assistants.create(
    name="Data visualizer",
    description="You are great at creating beautiful data visualizations. You analyze data present in .csv files, understand trends, and come up with data visualizations relevant to those trends. You also share a brief text summary of the trends observed.",
    model="gpt-4-turbo",
    tools=[{"type": "code_interpreter"}],
    tool_resources={
        "code_interpreter": {
            "file_ids": [file.id]
        }
    }
)

{
  "id": "asst_bZp7SmCiEcggjtXCltxx6IJp",
  "created_at":<PHONE_NUMBER>,
  "description": "You are great at creating beautiful data visualizations. You analyze data present in .csv files, understand trends, and come up with data visualizations relevant to those trends. You also share a brief text summary of the trends observed.",
  "instructions": null,
  "metadata": {},
  "model": "gpt-4-turbo",
  "name": "Data visualizer",
  "object": "assistant",
  "tools": [
    {
      "type": "code_interpreter"
    }
  ],
  "response_format": "auto",
  "temperature": 1.0,
  "tool_resources": {
    "code_interpreter": {
      "file_ids": [
        "file-Qltz9KN7HqcNdxnrXkg6w8Mo"
      ]
    },
    "file_search": null
  },
  "top_p": 1.0
}

thread = client.beta.threads.create(
    messages=[
        {
            "role": "user",
            "content": "Tell me what doesnt make sense with the two files considering what theyr corresponding columns represent",
            "attachments": [
                {
                    "file_id": file2.id,
                    "tools": [{"type": "code_interpreter"}]
                }
            ]
        }
    ],
    tool_resources={
        "code_interpreter": {
            "file_ids": [file2.id]
        }
    }
)

{
  "id": "thread_jOwF3zUVSgBvsrgKtpCVlLfu",
  "created_at":<PHONE_NUMBER>,
  "metadata": {},
  "object": "thread",
  "tool_resources": {
    "code_interpreter": {
      "file_ids": [
        "file-5CEH4I9WkXyBawZLWPaFJVa3"
      ]
    },
    "file_search": null
  }
}

#33 (excludes code_interpreter)


Unreachable code: can't decide kind: Type

=== Clang: clang version 7.0.1-8 (tags/RELEASE_701/final)
Generated: bioinspired
Generated: bgsegm
Generated: aruco

--- stderr
=== Crate version: Some("0.43.1")
=== Environment configuration:
===   OPENCV_HEADER_DIR = None
===   OPENCV_PACKAGE_NAME = None
===   OPENCV_PKGCONFIG_NAME = None
===   OPENCV_CMAKE_NAME = None
===   OPENCV_CMAKE_BIN = None
===   OPENCV_VCPKG_NAME = None
===   OPENCV_LINK_LIBS = None
===   OPENCV_LINK_PATHS = None
===   OPENCV_INCLUDE_PATHS = None
===   OPENCV_DISABLE_PROBES = None
===   OPENCV_CLANG_STDLIB_PATH = None
===   CMAKE_PREFIX_PATH = None
===   OpenCV_DIR = None
===   PKG_CONFIG_PATH = None
===   VCPKG_ROOT = None
=== Enabled features:
===   BINDING_GENERATOR
===   BUILDTIME_BINDGEN
===   CLANG
===   JOBSERVER
===   OPENCV_34
=== Probing OpenCV library using pkg_config
=== OpenCV library configuration: Library {
    include_paths: [
        "/usr/local/include/opencv",
        "/usr/local/include",
    ],
    version: "3.4.10",
    cargo_metadata: [
        "cargo:rustc-link-search=native=/usr/local/lib",
        "cargo:rustc-link-lib=opencv_stitching",
        "cargo:rustc-link-lib=opencv_superres",
        "cargo:rustc-link-lib=opencv_videostab",
        "cargo:rustc-link-lib=opencv_aruco",
        "cargo:rustc-link-lib=opencv_bgsegm",
        "cargo:rustc-link-lib=opencv_bioinspired",
        "cargo:rustc-link-lib=opencv_ccalib",
        "cargo:rustc-link-lib=opencv_dnn_objdetect",
        "cargo:rustc-link-lib=opencv_dpm",
        "cargo:rustc-link-lib=opencv_highgui",
        "cargo:rustc-link-lib=opencv_videoio",
        "cargo:rustc-link-lib=opencv_face",
        "cargo:rustc-link-lib=opencv_freetype",
        "cargo:rustc-link-lib=opencv_fuzzy",
        "cargo:rustc-link-lib=opencv_hfs",
        "cargo:rustc-link-lib=opencv_img_hash",
        "cargo:rustc-link-lib=opencv_line_descriptor",
        "cargo:rustc-link-lib=opencv_optflow",
        "cargo:rustc-link-lib=opencv_reg",
        "cargo:rustc-link-lib=opencv_rgbd",
        "cargo:rustc-link-lib=opencv_saliency",
        "cargo:rustc-link-lib=opencv_stereo",
        "cargo:rustc-link-lib=opencv_structured_light",
        "cargo:rustc-link-lib=opencv_phase_unwrapping",
        "cargo:rustc-link-lib=opencv_surface_matching",
        "cargo:rustc-link-lib=opencv_tracking",
        "cargo:rustc-link-lib=opencv_datasets",
        "cargo:rustc-link-lib=opencv_text",
        "cargo:rustc-link-lib=opencv_dnn",
        "cargo:rustc-link-lib=opencv_plot",
        "cargo:rustc-link-lib=opencv_xfeatures2d",
        "cargo:rustc-link-lib=opencv_shape",
        "cargo:rustc-link-lib=opencv_video",
        "cargo:rustc-link-lib=opencv_ml",
        "cargo:rustc-link-lib=opencv_ximgproc",
        "cargo:rustc-link-lib=opencv_xobjdetect",
        "cargo:rustc-link-lib=opencv_objdetect",
        "cargo:rustc-link-lib=opencv_calib3d",
        "cargo:rustc-link-lib=opencv_imgcodecs",
        "cargo:rustc-link-lib=opencv_features2d",
        "cargo:rustc-link-lib=opencv_flann",
        "cargo:rustc-link-lib=opencv_xphoto",
        "cargo:rustc-link-lib=opencv_photo",
        "cargo:rustc-link-lib=opencv_imgproc",
        "cargo:rustc-link-lib=opencv_core",
    ],
}
=== Found OpenCV library version: 3.4.10 in headers located at: /usr/local/include
=== Using OpenCV headers from: /usr/local/include/opencv2
=== Generating code in: /home/pi/Desktop/opencv/target/debug/build/opencv-53e71e3be2caf7e6/out
=== Placing generated bindings into: /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/opencv-0.43.1/bindings/rust/opencv_34
=== Clang command line args: [
    "-isystem/usr/bin/../lib/gcc/aarch64-linux-gnu/8/../../../../include/c++/8",
    "-isystem/usr/bin/../lib/gcc/aarch64-linux-gnu/8/../../../../include/aarch64-linux-gnu/c++/8",
    "-isystem/usr/bin/../lib/gcc/aarch64-linux-gnu/8/../../../../include/c++/8/backward",
    "-isystem/usr/include/clang/7.0.1/include",
    "-isystem/usr/local/include",
    "-isystem/usr/include/aarch64-linux-gnu",
    "-isystem/usr/include",
    "-I/usr/local/include",
    "-I/home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/opencv-0.43.1/src_cpp",
    "-DOCVRS_PARSING_HEADERS",
    "-includeocvrs_resolve_types.hpp",
]
thread '<unnamed>' panicked at 'internal error: entered unreachable code: Can't decide kind: Type {
    kind: Half,
    display_name: "__fp16",
}', /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/opencv-binding-generator-0.16.0/src/type_ref.rs:397:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error<PHONE_NUMBER>

Are you compiling it directly on Pi? Wait kind of distro are you running? And how did you install OpenCV and LLVM?

I'm running on a Pi 3b+ bit with the experimental 64-bit OS. I built OpenCV (3.4.10) from source, and installed sudo apt-get install -y llvm-dev libclang-dev clang.

Hey, I've pushed a possible fix (just ignoring the __fp16 type) to the no_half branch, can you check it out?

It compiles. thanks.

Fixed in 0.43.2


Episode length

Hello:
If I'm not mistaken, in the training phase, in all the tasks, the episode length is 64.
But intuitively there should be some differences between the different tasks, right?
What's more, at the testing stage, why is the maximum value of the length of the episode 360, and not 64?
Thank you so much!

The episode length in the training data is set to 64. While the max step in evaluation is set to 360, which is same as in the previous CALVIN baselines.


New Device: ELEGRP DPR10 Single Pole Rocker Dimmer Switch

Attached is the dump for the ELEGRP DPR10 Single Pole Rocker Dimmer Switch.
Thank you for adding it!
dump_elegrp-intuitive-dimmer.bin.zip

Added as ELEGRP DPR10 Single Pole Rocker Dimmer Switch


allow for wp users use invoices

Checklist

[x] I have read the CONTRIBUTING guide
[x] Good naming, keep simple
[x] Tested desktop/mobile
[x] Tested bright/dark
[x] Tested en/ru
[ ] Affects money; I checked the functionality once again
[x] I checked the PR once again

Original issue

https://github.com/swaponline/MultiCurrencyWallet/issues/3877
Video / screenshot proof


Recover password in-app partial integration

missing:

mobile wasn't tested at all
reset does not have a success screen
lots of blinking when you restart the flow
paper key input works, but you can't change the password (white screen)

before merge make sure to disable the new flag!

Start service with --features env_autoreset to test


bio fix: pass flags on BIO_ctrl to make flush retriable

This PR fixed a wrong wbio pointer usage on SSL_get_error.
The bug will cause SSL_get_error to return SSL_ERROR_SYSCALL even after BIO_set_retry_write in some cases such as BIO_CTRL_FLUSH. Without this fix, when BIO_CTRL_FLUSH, if BIO writer gets a WOULD_BLOCK error, it calls BIO_set_retry_write and returns 0, it will not work and openssl will return a failure.
Previous review is in #20919 , I reopened this PR to trigger CLA checking.

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

Hi everyone, is everything alright?

This pull request is ready to merge

Merged to master. Thank you for your contribution!


Add Sirclo / Ecommerce

Website:

https://www.sirclo.com/
https://store.sirclo.com/

Examples:

https://sabriamilan.com/id
https://www.hicayuofficial.com/id
https://karcher-store.sirclo.me/id
https://www.littlefolkapparel.com/id
https://www.joatelier.com/id
https://www.pavettiaskincare.com/id
https://www.kfoutdoorindo.com/id
https://bajubaju.com/id
https://maisonfeerie.com/id
https://pasarbodega.co.id/id
https://amongtheodder.com/id

Thanks!


Update party.js to keep the rendering always on top

As I told you on the "issue"
please review this for a possible change on the code. I have tested locally and it works and this is easier thing to do I presume.
Thanks for the library.

Thanks for the contribution! I just briefly modified the comment you added and added a minified version.

Thanks for the contribution! I just briefly modified the comment you added and added a minified version.


[MM-14303] Able to copy channel header and purpose

Summary
Able to copy channel purpose and header when long press
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/11262
Checklist

[x] Includes text changes and localization file updates

Device Information
Huawei P10, Android 9

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

@enahum seems a build failure ^

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-2923/Mattermost_Beta.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-2923/Mattermost_Beta.plist

@tekminewe this needs to be updated with the latest master

@tekminewe It looks like you're including changes from your other PR here. Can you revert that?

sorry @migbot already reverted the changes and pull from master

Tested and it works according to the specs. Removing  QA Review label.

Error trying doing the automated Cherry picking
exit status 1

@cpanato error cherry-picking, do you want to take a look or should I cherry-pick manually?

@enahum  manual cherry pick or wait when i  come back to check

ok @cpanato  I'll cherry pick manually

Thanks @ogi-m!  I did some testing as well both on iOS and Android and it worked as expected.  Tested with regular text on header and purpose, with markdown and with multiple newline before the actual text, and all original text is copied.


travis-ci.org is ceased

See https://travis-ci.org/github/twogood/unshield:
Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on.
See https://docs.travis-ci.com/user/migrate/open-source-repository-migration for an overview on how to migrate to travis-ci.com

Yeah I know... I'd like to use GitHub actions instead.

How do you feel about the AppVeyor integration?
The configuration in the main branch looks differently from what is actually executed in a pull request and on the other hand it is failing.
It seems it could also be replaced by GitHub actions (https://docs.github.com/en/actions/using-jobs/choosing-the-runner-for-a-job).
Instead of having three different CI pipelines, GitHub actions could be the one and only (From my naive standpoint I could not find something which is not supported in comparison to the other two).

@kratz00 I pretty much hate AppVeyor, so Windows builds should definitely also run on GitHub Actions.

Fixed by https://github.com/twogood/unshield/commit/71c96a21c31a87e9ede5008cdf5dbc460792ecb7


[GUI] GUI doesn't write new config files to correct dir

GUI doesn't properly create new config files when attempting to add an integration.  Appears to try to write to conf.d/<check>.yaml rather than conf.d/<check>.d/conf.yaml.

Fixed with https://github.com/DataDog/datadog-agent/pull/887


Add customizable images from config

Add custom_images config option to populate seldon configmap images
Add integration tests

LGTM. Let's resovle pending conversations.

@misohu Commits need to be signed for this repo, otherwise we won't be able to merge this PR into main.

Signed commits in this PR @i-chvets https://github.com/canonical/seldon-core-operator/pull/198 thanks