Failed at the<EMAIL_ADDRESS>install script.

 System Linux 4.15.0-48-generic
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/sharp
gyp ERR! node -v v12.3.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle false
npm verb lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/lib/node_modules/sharp/node_modules/.bin:/usr/lib/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
npm verb lifecycle<EMAIL_ADDRESS>CWD: /usr/lib/node_modules/sharp
npm info lifecycle<EMAIL_ADDRESS>Failed to exec install script
npm timing action:install Completed in 438ms
npm verb unlock done using /home/USER/.npm/_locks/staging-a072192f34a17023.lock for /usr/lib/node_modules/.staging
npm timing stage:rollbackFailedOptional Completed in 88ms
npm timing stage:runTopLevelLifecycles Completed in 6504ms
npm verb stack Error<EMAIL_ADDRESS>install: (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
npm verb stack Exit status 1
npm verb stack     at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
npm verb stack     at EventEmitter.emit (events.js:200:13)
npm verb stack     at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
npm verb stack     at ChildProcess.emit (events.js:200:13)
npm verb stack     at maybeClose (internal/child_process.js:1021:16)
npm verb stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
npm verb pkgid<EMAIL_ADDRESS>npm verb cwd /home/USER/PROJECTS/MMMM/MMMMM-XXXXXX-IV4
npm verb Linux 4.15.0-48-generic
npm verb argv "/usr/bin/node" "/usr/bin/npm" "i" "-g" "sharp" "--verbose"
npm verb node v12.3.1
npm verb npm  v6.9.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm verb exit [ 1, true ]
npm timing npm Completed in 6938ms
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/USER/.npm/_logs/2019-07-29T02_25_38_387Z-debug.log

What is the output of running npx envinfo --binaries --languages --system --utilities?
npx: installed 1 in 2.002s

System:
OS: Linux 4.15 elementary OS 5.0 Juno
CPU: (4) x64 Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
Memory: 8.77 GB / 11.64 GB
Container: Yes
Shell: 4.4.19 - /bin/bash
Binaries:
Node: 12.3.1 - /usr/bin/node
npm: 6.9.0 - /usr/bin/npm
Utilities:
Git: 2.21.0 - /usr/bin/git
Languages:
Bash: 4.4.19 - /bin/bash
Java: 1.8.0_212 - /usr/bin/javac
Perl: 5.26.1 - /usr/bin/perl
Python: 2.7.15 - /usr/bin/python
Ruby: 2.5.1 - /usr/bin/ruby

Have you ensured the platform and version of Node.js used for npm install is the same as the platform and version of Node.js used at runtime?

I don't know how to do that.

My observations.

The path " /sharp/6613-libvips-8.7.4-linux-x64.tar.gz " does not exists as the line does reference " ERR! sharp EACCES: permission denied, open '/usr/lib/node_modules/sharp/6613-libvips-8.7.4-linux-x64.tar.gz' ".

Hi, if you have to use sudo with npm install then you also need to pass it the --unsafe-perm flag. It's better to avoid needing to use sudo/root in the first place if you can.

Nice! thanks a lot!

Why would you need to use --unsfafe-perm in the first place?

Hi, if you have to use sudo with npm install then you also need to pass it the --unsafe-perm flag. It's better to avoid needing to use sudo/root in the first place if you can.

Why would you need to use --unsfafe-perm in the first place?


Question

Hi Caio,
Did you try to put this algo in production?
Best,
Thiago

No, although I have kept studying RL for trading in other projects, including this one.


k3os: Unable to connect to the server: x509: certificate has expired or is not yet valid

Version (k3OS / kernel)
k3os version v0.9.0-rc5
5.0.0-37-generic #40~18.04.1 SMP Wed Jan 15 04:09:29 UTC 2020
Architecture
x86_64
Describe the bug
All of a sudden my cluster started to complain:
Unable to connect to the server: x509: certificate has expired or is not yet valid
Based on the investigation, it seems that cert folder has certain certs exactly one year old (3rd of Feb 2020, now is 2021):
/var/lib/rancher/k3s/server/tls
To Reproduce
Cannot exactly define, based on dates looks like "exactly one year old cluster" quite cause it.
Expected behavior
Defined behavior to manually solve and/or automatic renewal of certs properly.
Actual behavior
Cluster out of reach.
Additional context
Running the K3OS on Hyper-V VM. No issues beforehand.
There seems to be several issues (some open and some closed) about same x509 certificate issues; some/most are on fresh installs. Mine broke all of a sudden, based on dates it did not renew the certs (they're dated 3rd of Feb 2020, as today is same day but 2021).
I tried to wipe TLS folder entirely, which causes new certs to be created, but apparently the error persists (or cluster config would be invalid - is there automatically fresh config to apply after certs recreation?)

I proceeded with various tests nuking the /var/lib/rancher/k3s folder entirely, grabbing the fresh tls certs from it, and making sure server/tls and agent folders have matching new ones (although the agent folder seems to get them from server/tls too).
I'm failing to start the single node cluster that is, where the agent is located within the master node.

I've hit the same issue it's a year and a bit past the install date
$ echo | openssl s_client -servername k3s-master -connect k3s-master:6443 2>/dev/null | openssl x509 -noout -dates
notBefore=Jan  7 19:04:15 2020 GMT
notAfter=Feb  5 19:35:51 2021 GMT

upgrading to v0.19.5-rc.1 did fix the issue
export K3OS_VERSION=v0.19.5-rc.1
/usr/share/rancher/k3os/scripts/k3os-upgrade-rootfs
/usr/share/rancher/k3os/scripts/k3os-upgrade-kernel
reboot

Thank you, got the cluster up and running now!
Apparently the upgrade tossed some wrenches to my existing Dashboard etc, but that's my problem to figure out. I need to study the changes - most of my pods are running whereas some aren't :-).

Ok it's somewhat related, but might be the versions in between also changed the default authentication/authorization structures.
My failing services/pods are complaining about service credentials in various forms. For example dashboard is logging:
2021/02/06 11:43:42 Starting overwatch
2021/02/06 11:43:42 Using namespace: kubernetes-dashboard
2021/02/06 11:43:42 Using in-cluster config to connect to apiserver
2021/02/06 11:43:42 Using secret token for csrf signing
2021/02/06 11:43:42 Initializing csrf token from kubernetes-dashboard-csrf secret
panic: Unauthorized
Need to dig out more, is the upgrade or the cert renewal (as a part of the upgrade) the cause of this.

@kallex I had a few pods that also wouldn't come up, the auth changed due to the upgrade and needed to figure out how to fix the permissions.

@daemonp cool, exactly my case as well. Did you figure them out, was it straightforward?
I'm running Dashboard, Rook-Ceph, Prometheus and Grafana; not expecting any major issues - just have to tackle them service by service I suppose.

Something smells fishy here; k3os-system / system-upgrade-controller complains being unauthorized.
So; the upgrade managed to fix/renew certs to be valid, but it didn't recover itself from using the old certs? I get it, that the expired secrets and certs on existing services requrire renewal.
But I do consider k3os-system namespace being able to deal with the core security themselves.

NOTE! I have no idea if this has any further BAD consequences!
I read about Rook Ceph issues with K8S certificate renewal and proceeded to delete all their Service Account secrets. They got recreated automatically and the services started to pop up one by one. Then I repeated same procedure with Prometheus - namespace and my Prometheus + Grafana stack started to work.
Now I'm in the stages of trying (cautiously) repeat the same procedure on kube-system namespace, to get certain failing system services (such as local path provisioner) hopefully work.
 Only one I left intact was default-* token in default namespace.
^^ Doing this invalidated many of my PODs; in my case all the pods are deployment-controlled so I could just delete all the pods to let them recreate their new service account tokens upon creation.
Doing above YOU WILL LOSE YOUR POD DATA. That shouldn't be a problem in the first place, as Pods are epheremeal, and you should store their data on persistent volume. Apparently my Grafana-setup didn't have volume configured (just learned; I knew my Prometheus did have), so I lost all my dashboard customizations.

Had the same issue on my lattepanda (x86 single board computer without a cmos rtc battery). Installed the os using a cloud init yaml config while connected on lan, turned it off and unplugged it. Deployed it on the field with wifi, but k3s wouldn't start even though the correct time was retrieved with NTP (2012 -> 2021). Sent a reboot via ssh and k3s started fine automatically.
I'm not very familiar with the boot process, but could it be (in my particular case, i don't know how this would apply to a VM) that k3s starts before the ntpd service, and due to the power loss and the lack of the battery the datetime is not correct?

I assume correct timezone must be set on OS level before installation (specifically before certificates generation step)
TZ="Europe/Riga"
sudo ln -snf /usr/share/zoneinfo/$TZ /etc/localtime


elasticsearch Write problem

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[V] elastic.v7 (for Elasticsearch 7.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
I hope to insert data into elasticsearch
Please describe the actual behavior
I am using the docker container to build an elasticsearch environment and a golang environment.
The version of elasticsearch is 7.1.1
Elasticsearch only added network.host: <IP_ADDRESS> in the configuration file elasticsearch.yml
The connection is normal,Webpage  http://<IP_ADDRESS>:9200/ opens normally
	url := "http://elasticsearch:9200" 	client, err := elastic.NewClient(elastic.SetURL(url), 		elastic.SetSniff(false)) 	if err != nil { 		fmt.Println(err.Error()) 		os.Exit(-1) 	}
No abnormal connection to Elasticsearch
But use
client.Index(). 		Index("sns"). 		Type("post"). 		BodyJson(p.post). 		Do(context.Background())
Card for a long time, then an error
elastic: Error 503 (Service Unavailable): blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];[SERVICE_UNAVAILABLE/2/no master]; [type=cluster_block_exception]
Any steps to reproduce the behavior?

The problem seems to be unrelated to the library. If you misconfigure Elasticsearch on Docker, it might return internal IPs, which will be picked up by the library in a process called sniffing. Simply disable sniffing if you don't need load-balancing (elastic.SetSniff(false) and elastic.SetHealthcheck(false)) and see if this solves your issues.
See also https://github.com/olivere/elastic-with-docker for a (rather old) example illustrating different issues around Docker and Elasticsearch and Elastic.


Added contribution section to Readme

The readme was missing links to the bug tracker/mailling list etc..

This was merged, but @asfgit somehow forgot to close this issue. Could you close it for me, @binfalse ?


v0.0.19 broke TypeScript stories types on combineStories

Hello all,
Describe the bug
Since v0.0.19, combineStories is returning any for all the stories :

The component exported here is :
const Template: Story = () => (
  <CreateProjectDrawer>
    <DrawerTrigger as={Button}>Create a project</DrawerTrigger>
  </CreateProjectDrawer>
);

const Default = Template.bind({});

To Reproduce

Export any story
Use combineStories and you can see the stories are no longer typed

Expected behavior
combineStories should return typed stories (v0.0.18 here) :

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
v0.0.18 is the last version where it works, all later release are broken.
I'm using storybook 6.3.5.

I’ve got the same issue with the latest version 0.0.21. This problem seems to be caused by the mismatching of a peer dependency @storybook/addons.
In @storybook/addons published as latest on npm, a type named BaseStoryFn is not exported.  Since the type definition of composeStories's return value is depending on BaseStoryFn, TS could not resolve the proper type and returns any instead.
I could circumvent this issue by installing exact same version of @storybook/addons that is specified in the devDependencies of @storybook/testing-react.
yarn add<EMAIL_ADDRESS>--dev

Hey @jgoux @neet, thanks for this discussion and sorry for the inconvenience!
I'm currently in a conumdrum. Support for CSF 3.0 was requested in #31, and in order to properly support it I needed types from storybook 6.4. I didn't think much about it, and now it's difficult to find a solution that both supports the older types AND the new types in the same function. I'm not sure how to do that, so I'd say for now you can take either route:
1 - Downgrade @storybook/testing-react to v0.0.18 and fix it until Storybook 6.4 is released and upgrade it when you upgrade Storybook 6.4. The only difference between versions 18 and 21 is CSF3 support.
2 - Upgrade to Storybook 6.4 (e.g. npx sb@next upgrade --prerelease) and it should just work. Not only you get to try cool new features in SB 6.4 but you can give some feedback to Storybook :p
In the meantime, I'll try to think of a solution. If you have any ideas to help, they're greatly appreciated!

I think the best course of action would have been to release a major of this package maybe?
I don't know for the others, but we rely heavily on renovate/dependabot to automatically upgrade our deps if they're minor/patch releases, and if this isn't something fixable in those channels then maybe it could be considered a breaking change?
Having to upgrade to a non stable release (6.4) doesn't seem like a proper solution to me (even if I love being at the bleeding edge and testing new things early).
For now we fixed the version to v0.0.18 but I really think you shouldn't be afraid of bumping a major in those situations. 👍

Hey @jgoux thanks for your opinion. For now I reverted the support for CSF3 in v0.0.22 so most users should be able to use it without issues. I'm still thinking about how to approach getting support back, and it might likely be in a major release. Please update and let me know if things went fine!

Hey everyone, I just made a prerelease that supports CSF3.
If you're not using CSF3, you should be using v0.0.22 without any issues.
If you're using CSF3, please install v1.0.0-next.0 and try it out, but keep in mind you need Storybook 6.4 if you're using typescript.
I'll be closing this issue, and feel free to reopen in case this did not fix your situation!


EF7/MVC 6 update of the Contoso University sample web app

http://www.asp.net/mvc/overview/getting-started/getting-started-with-ef-using-mvc/creating-an-entity-framework-data-model-for-an-asp-net-mvc-application
Work will start about 22 Feb 2016 and will take 3 weeks to complete.
@tdykstra to lead effort.

@Rick-Anderson What does the Contoso University tutorial cover that the existing MVC tutorial we have doesn't cover?

Possible duplicate of https://github.com/aspnet/Docs/issues/977?

The EF 6 MVC 5 CU tutorial series is a long one that covers a number of topics.  It's not a duplicate of 977 because one thing it doesn't cover is auth.  Beyond basic CRUD it covers related data extensively, data model attributes and fluent API extensively, connection resiliency, command interruption, stored procedures, concurrency, inheritance, performing raw SQL, no-tracking, debugging, and a number of other subjects related to working with relational data.

Fixed by #1893


is_simplify_report_closure_enabled integrated

API Changes for simplify_report_closure.

@labhvam5 please review and assign it to me once you've approved it


Rewrite in Typescript

Watson Developer Cloud Node SDK (Renamed to ibm-watson in npm recently) is implemented in Typescript.
The next version of Botkit is implemented in Typescript too (It will be released in a few weeks time).
I think that it makes perfect sense to implement new major version of this library in Typescript too.

Fixed as part of 2.0.0


Using react-komposer with react-native

Has anyone gotten this to work? I am trying to use mantra-core with react-native but get the error that mantra core can't load 'react-composer'. Installing react-composer without mantra-core still causes the same issue.
To replicate, create blank react-native app. Install react-composer and import (import {createApp} from 'react-composer';)  it in index.ios.js.
I'm getting the following issue. Already tried the following:

The suggested solution on the screenshot.
Installing module using npm 2 and 3 and deleting node_modules and installing again.

I'm also seeing it. Will try to fix.

@arunoda ok thanks. Let me know if you need any help. Would like to use mantra on a react-native project.

Yes. We need some help. If you can find the problem and fix it to work on ReactNative, that's super awesome.

@superandrew213, what do you suspect?

@smooJitter not sure. Maybe something to do with babel?

+1 for react-native support

Has anyone made any progress on this?

@arunoda could it have something to do with the html tags (like Loading...)

Adding mantra-core and react-composer src manually to project seems to make react-composer available. However now I'm getting this:

Removing the option in .babelrc of react-display-name module dose remove the error and mantra-core seems to work.

@superandrew213 can you explain which option did you removed ?

@yanivnizry make sure you are using react-display-name v0.0.1. Latest version is using babel 6 and removing the option doesn't work.
react-display-name v0.0.1  has two options. Remove them both.

@superandrew213 thank you.
@arunoda can you please fix this issue in the next versions ?

Yeah. We can.
@superandrew213 send me a PR

I would love to use Mantra via react-native.  I know you guys are busy but it would be nice to at least have a small list of complication that would need to be addressed. This repo ( spencercarli/react-native-meteor-boilerplate) provides a framework for connecting to meteor from a react-native client via node-ddp.  I also looked at Kadira React Native Demo with GraphQL, which sounds promising but Apollo is still in early stages.  For those considering  Meteor + Mantra + React-Native prototypes, It would be nice to have a little direction regarding Mantra compatible client / server technologies to support GraphQL and routing (e.g., react-native-router-flux, exNavigator, ExperimentalNavigation). Furthermore how would "context" configurations change.

@arunoda it's just a hack. I manually added both mantra-core and react-komposer source into project root dir and imported the manually added react-komposer in mantra-core.
After doing that I got the error with react-display-name babel options. So I went into the module and just removed the options. (Note you have to downgrade react-display-name to v0.01 if it is higher. It doesn't work with the new version).

@superandrew213 Hmm. If that's the issue, let's try to remove react-display-name. I'll try with it.

@arunoda adding "react-native": "./dist/index.js", to package.json fixes everything.
Still need to remove react-display-name from react-simple-di.
Sent you pr's.

That's cool. I'll take this.
May be we can remove that package from react-simple-di.
I'll do a release now and ping you.

yep removed it already and sent you pr.

FYI: Updated mantra-core with updated react-komposer and react-simple-di.
So, you could simply use mantra-core in React native right away.

hmm I expected that the react p component would cause an error

@superandrew213 what are you using for reactivity instead of Tracker ? did you tried https://github.com/aleclarson/tracker

Not yet but will check it out. Right now I'm using redux.

For now you can set your own react-native loading and error components like so: https://github.com/kadirahq/react-komposer#change-the-loading-component
@arunoda maybe we can use navigator.product === 'ReactNative' to check. What do you think?

Yeah. We should try to detect that and load appropriate Loading components in RN.
If navigator.product === 'ReactNative' works, we should try to use it.

Yes it works, it was added in react-native v0.17.0.
https://github.com/facebook/react-native/releases/tag/v0.17.0
However to show react-native views and text components we might need to add react-native as a dependency.

Can't we simply get that RN Text component? If not, we should try to add RN as a peer-dependancy.

I'm not sure whether you can get the Text component only.
What you think about this?
https://github.com/superandrew213/react-komposer/commit/64c51e73d0e1f771d35c0fb1764116735e1b9a02

Closing this since, we already support RN. But, we need to provide loading components manually. That's bit of an issue. We could fix this with #8


[opentitantool] Add EEPROM primitives to SPI trait

This PR introduces a new method on the spi::Target trait, for doing SPI transactions following the EEPROM format, that is, consisting of a few bytes of command/address, followed by a chuck of data to be either read or written, optionally followed by repeated polling a status bit, to see if the operation is complete.
A default implementation of the new method is provided for transport backends which support generic SPI read/write transactions, in effect moving part of the code from the existing SpiFlash struct into the spi::Target trait.
Going forward, transports that do not implement generic SPI transactions, but supports only EEPROM/Flash-style protocol, can provide their own implementation of the new trait method, and leave the existing generic Spi transaction method either unimplemented, or severely restricted.

I have verified that I can still program my CW310 using HyperDebug with this code change (after fixing endian-ness of address bytes.)  Next step will be adding Dediprog support (in a separate commit/PR.)

I have seen the first few SPI requests coming out of the Dediprog using code on top of this PR:
https://github.com/lowRISC/opentitan/compare/master...jesultra:opentitan:dediprog

I know that you just approved this PR, but during the course of my Dediprog driver work, I realized that further tweaks to the representation of dummy cycles were warranted.
Now, the SFDP read "3-byte address followed by a dummy byte" is directly represented in the eeprom::Cmd.


Fixed active state of navigation element in site header

I think we need to refactor header menu to use react router dom's NavLink. It automatically adds some attributes to anchor tag when it matches the current URL.


gimp: Update to version 2.10.22

update to 2.10.22

/verify

help needed, I'm not good with powershell

32bit installation does not work

But that’s unrelated to the version bump, yes? Should we accept this, and open another ticket re the install fail?


[Question] Validation Provider: Errors missing the field name

Sorry to bother you again, but
I am using the Validation Provider like this:
<ValidationProvider
        v-for="(field, index) in formFields"
        :key="index"
        v-slot="{ errors }"
        :rules="field.rules"
        mode="lazy"
      >
        <FormField
          v-model="form[field.name]"
          :error-messages="errors"
          :name="field.name"
          :label="field.label"
          :type="field.type"
          :title="field.title"
        />
      </ValidationProvider>

Now within my FormField component:
If I display
{{ errorMessages[0] }}
I will get something like this:
{field} must be a valid Email address.  (just translated from my localized German version).
Then thing is, that {field} is not the name of my field (in this case 'Email').
How can this be passed to the errorMessages array?
Your example here
<ValidationProvider vid="confirm" rules="required" v-slot="{ errors }">
  <VTextField v-model="passwordConfirm" type="password" :error-messages="errors" />
</ValidationProvider>

Seems to be doing the exact same thing, or am I missing something?
Thank you in advance.
Cheers

ValidationProvider can take a name prop which will replace the {field} placeholder.
<ValidationProvider
        v-for="(field, index) in formFields"
        :key="index"
        :name="field.name" <----- The field name
        v-slot="{ errors }"
        :rules="field.rules"
        mode="lazy"
      >
        <FormField
          v-model="form[field.name]"
          :error-messages="errors"
          :name="field.name"
          :label="field.label"
          :type="field.type"
          :title="field.title"
        />
      </ValidationProvider>

On point. thank you again. 👍🏼


Change "lower-case to "lowercase" in xml comments

Fix xml docs
Addresses #17445
Please review
Thank you in advance

Thanks!


Unused and confusing variable name in csr_excl_item.sv file

Hi,
A harmless, minor issue - very confusing though. In file

opentitan/hw/dv/sv/dv_base_reg/csr_excl_item.sv

Line 30 in 23b8820

   csr_excl_s csr_excl_item;

I don't see that variable being used. But more importantly (from readability aspect) this variable has the same name as its enclosing class name. Though legal, this can be misleading.
Cheers

Thanks for finding this. Fixed at #4435


can't buy emote

why i can't buy emotes it say canceled order

Sorry for the late response, but it's possible you have the config set to only be able to purchase emotes with "emote credits". The default used to be that you could only do it that way, but I thought I changed it so the default would also let you use group credits.


i18n(es-ES): translated astro-syntax

[x] astro-syntax translated into Spanish

Thanks @juanburg98! This PR looks fine to me, but there are a few broken links, could you please take the time to solve them so we can merge it? 💜

@Yan-Thomas Everything is ready

thanks everyone! @juanburg98, @Waxer59 and @Yan-Thomas 💜


navigation bar overlaps status bar

Hello, I am experiencing such a problem in the present view. Has anyone encountered it? Thank you

any fix you found for this issue?  @wisisimon


Update for latest ver?

Plz?

Adding a little more... Appreciative request for an update.
I've been using this plugin for a while and I do really appreciate it. Do you have any plans on updating it?
I can see a lot of changes being updated and it's been worked on the passed week but I do hope you're planning on updating this plugin, it's awesome and there is no alternative that I have found.
Thank you for all your hard work regarding all of your plugins!

it... is updated?

Update works for DT release, however this update (<IP_ADDRESS>) doesn't seem to include Viper or Pictomancer as options in the Add Job drop down menu.

would be cool to add hide weapon options based on location (ex. hide weapon while in cities)


Install on Firefox?

I see that you have a download for Firefox on the release page. Can this be installed on Firefox, and if so - how? I extracted the Firefox download, but it doesn't seem to be able to be installed.

I also tried to manually install the zip file in Librewolf (a Firefox variant) and got an error:
Manage Extensions > Install Add-On from File... > Selected Firefox release zip file > get error "This add-on could not be installed because it appears to be corrupt".


50%-segment fractions and similar metrics incorrect for sectorized graphs

Cannot properly calculate this without adding # hits as a hit feature

Blocked by #263


Rework datamodels to run with latest stpipe and stdatamodels

@astrobc1 ok, I got at least 1 test working, so I know all the pieces work together fine.
Now I suggest we proceed like this:

you run the test locally pytest liger_iris_pipeline/tests/test_dark.py and make sure it works (report back here when done)
you review code changes in this pull request and provide some feedback, high level, at the moment I would like to make sure you understand what I implemented, we will improve the code later on. Please do not make code modifications yet, I would like to finalize this PR, merge it into main, then we can spin-off from there multiple pull requests.

in the meantime I am trying to fix Github Actions.

@zonca test_dark.py passes now. I'm working on #2 as well as understanding the logic for instantiating a DataModel. I will report back here early this week.

@zonca Overall the changes make sense and appear correct.

2767799 If the FITS keyword "DATAMODL" is stored in all headers, can't we always rely on datamodels.open instead of the class explicitly so long as they are registered?

fcc9cd0 How did you solve the output_ext not defined error?

44e285d Will we eventually swap out jwst.stpipe.core.JwstStep for stpipe.step.Step?

701a431 I see how this stems from an assumption that get_reference_file expects a filename, not a DataModel. Should we override get_reference_file to accept both?

@astrobc1 thanks for the feedback, best way to give feeback is to do a review and reference the line of code instead of the commit itself, doing it from the https://github.com/oirlab/liger_iris_pipeline/pull/58/files files view.

@zonca Overall the changes make sense and appear correct.

2767799 If the FITS keyword "DATAMODL" is stored in all headers, can't we always rely on datamodels.open instead of the class explicitly so long as they are registered?

Until I have a good understanding of the code and know better, I always prefer to follow what JWST is doing.
For some reason I don't know yet, JWST is now using the actual classes, see https://github.com/spacetelescope/jwst/blob/10501f22def0460b15df65cd5261601c6a71d7cf/jwst/dark_current/dark_current_step.py#L29 so I do the same.

fcc9cd0 How did you solve the output_ext not defined error?

Yes, I think it comes from here:
https://github.com/spacetelescope/jwst/blob/10501f22def0460b15df65cd5261601c6a71d7cf/jwst/stpipe/core.py#L20-L24

44e285d Will we eventually swap out jwst.stpipe.core.JwstStep for stpipe.step.Step?

Yes, if we can we want to get rid of all dependencies on jwst, but it is not too bad, so for now let's go forward like this

701a431 I see how this stems from an assumption that get_reference_file expects a filename, not a DataModel. Should we override get_reference_file to accept both?

There is something I do not understand here, maybe you can track it down,
see here:
https://github.com/spacetelescope/jwst/blob/10501f22def0460b15df65cd5261601c6a71d7cf/jwst/dark_current/dark_current_step.py#L32
they are doing the same, feeding the input model to get_reference_file, why does it work for them and not for us?
I think that at some point in the class hierarchy we are using different classes but have not understood where.

@astrobc1 I created a dedicated issue about the get_reference_file problem and I am merging this PR.
We will track it down later.


Need a bit more help from the Readme.md on Firebase setup

Hi,
I'm trying to get my own copy working on my box but I'm not clear on how to get the API key from firebase.
I have setup a firebase project.  If I choose [Settings Gear] -> [Project settings]:

I can find a Web API Key under General.
I can find Server Key, Legacy Server Key, and Sender ID under cloud messaging.

Which settings do I use to populate the firebaseInitialization.js file, most specifically, apiKey?
Thanks!

You no to click on "Add firebase to your web app"

And copy everything into firebaseInitialization.js.
I hope that helps you.


Include a Java REPL

Use case: Demo/try out Javaslang online.
Requirements:

Java 8 conform
Loadable jars
Embeddable

The Java REPL looks promising.

See also https://www.pgrs.net/2015/09/14/java-repl-with-jshell-and-bazel/


Add Ideographic Engine

When Ideographic language, or unmanage language by Slugify, the slug comes empty. This fix provides an engine that will generate a 12 chars random string.

I get what this is supposed to do, and what problem it is supposed to solve: turn ideographic languages like Japanese, Korean, etc. into "slugs" by just creating a random string.
However, I wouldn't call this a "universal solution" for the package.  Some people may be happy with the random strings, some may prefer incrementing digits, some may prefer an imperfect transliteration.
I think something like the toAscii() method of Patchwork\Utf8 might be a better approach.
In any case, this is something I'm not keen to add to the official package ... although I do appreciate the PR!


Homework/Assignment/Assessment 8

POST ->

GET ->

PUT ->

DELETE ->

MOST/LEAST EXPENSIVE ->

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
3

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


APC rework and improvements

[FEATURE]
Description
When unlocked by an engineering ID it should give access to toggling the main breaker as well as lights and machinery independant of eachother. To save getting your ID out of your PDA like is SS13 maybe have on right click APC > examine, lock / unlock.
Power priorities is also desirable so per APC we can set environment (atmos and doors) to turn off last after lights and machines.
Checklist

[x] APC is lockable (engineering access permission)
[ ] APC toggle switches for lights, machines & main breaker
[ ] APC priorities

Is this still in play?

I have some scratch notes for power channels and power prioritization . APCs already have some of the code to implement 3 power channels (named Environment, Lights, Equipment internally), there are mockups for the UI... tl;dr this issue is still relevant and thought about


zombienet provider reads json provider before fully written

E.g. here. Introduced in #554

Fixed by #615


Improved example converter

Stats
Baseline      1101 API locations with examples
Provider:     google-beta
Success rate: 94.94% (14457/15228)
Converted 93.74% of csharp examples (2379/2538)
Converted 93.70% of go examples (2378/2538)
Converted 97.64% of java examples (2478/2538)
Converted 93.74% of python examples (2379/2538)
Converted 93.74% of typescript examples (2379/2538)
Converted 97.08% of yaml examples (2464/2538)
Experimental  1101 API locations with examples
Provider:     google-beta
Success rate: 96.77% (14880/15377)
Converted 96.73% of csharp examples (2481/2565)
Converted 96.69% of go examples (2480/2565)
Converted 96.69% of java examples (2480/2565)
Converted 96.73% of python examples (2481/2565)
Converted 96.73% of typescript examples (2481/2565)
Converted 97.06% of yaml examples (2477/2552)

/release patch


Headers for TSV files are not formatted correctly

The headers shows in lowercase for booknames and for resource name(OBS) and are non-bolded.
Develop branch:

Screenshot from Production:

Looks good in translationCore Create - v1.4.2 build 132-29815c0


App crash on starup

App crashes on startup after building for release

Was able to fix my issue
In your android/build.gradle ; used 4.0.1 for my gradle plugin


AQL Graph traversal returns null in array

My Environment

ArangoDB Version:        3.2.10
Storage Engine:             MMFiles
Deployment Mode:       Single Server
Deployment Strategy:   Manual Start in Docker
Configuration:
Infrastructure:               AWS | Mac
Operating System:        MacOS 10.13.4
Total RAM in your machine:
Disks in use:
Used Package:               Docker - official Docker library

Component, Query & Data
Affected feature: AQL, Graph
AQL query (if applicable):
FOR vertex, edge IN 0..2 OUTBOUND "skills/APPLICATION_HIERARCHY" skill_skill return edge
AQL explain (if applicable):
With no values present:
Query string:
FOR vertex, edge IN 0..2 OUTBOUND "skills/APPLICATION_HIERARCHY" skill_skill return edge
Execution plan:
Id   NodeType        Est.   Comment
1   SingletonNode      1   * ROOT
2   TraversalNode      1     - FOR vertex  /* vertex /, edge  / edge / IN 0..2  / min..maxPathDepth / OUTBOUND 'skills/APPLICATION_HIERARCHY' / startnode */  skill_skill
3   ReturnNode         1     - RETURN edge
Indexes used:
By   Type   Collection    Unique   Sparse   Selectivity   Fields               Ranges
2   edge   skill_skill   false    false       100.00 %   [ _from, _to ]   base OUTBOUND
Traversals on graphs:
Id   Depth   Vertex collections   Edge collections   Options                                   Filter conditions
2   0..2                         skill_skill        uniqueVertices: none, uniqueEdges: path
Optimization rules applied:
none
With data:
Query string:
FOR vertex, edge IN 0..2 OUTBOUND "skills/MM" graph 'skills_hierarchy' return edge
Execution plan:
Id   NodeType        Est.   Comment
1   SingletonNode      1   * ROOT
2   TraversalNode      1     - FOR vertex  /* vertex /, edge  / edge / IN 0..2  / min..maxPathDepth / OUTBOUND 'skills/MM' / startnode */  GRAPH 'skills_hierarchy'
3   ReturnNode         1     - RETURN edge
Indexes used:
By   Type   Collection    Unique   Sparse   Selectivity   Fields               Ranges
2   edge   skill_skill   false    false        61.70 %   [ _from, _to ]   base OUTBOUND
Traversals on graphs:
Id   Depth   Vertex collections   Edge collections   Options                                   Filter conditions
2   0..2    skills               skill_skill        uniqueVertices: none, uniqueEdges: path
Optimization rules applied:
none
Dataset:
https://gist.github.com/RHSman/07ed64ded3c4d7a02d955668224767e4
https://gist.github.com/RHSman/a922c49c4ddece024e518ba3fe33abf3
Size of your Dataset on disk:
Little
Replication Factor & Number of Shards (Cluster only):

Steps to reproduce

Create 1 document collection (skills), create edge collection (skill_skill)
Create graph (skills_hierarchy)
run AQL: FOR vertex, edge IN 0..1 OUTBOUND "skills/MM" graph 'skills_hierarchy' return edge._to
currently if running depth greater than 1 it will just run and run

Output:
[
null,
"skill_skill/13670969",
"skill_skill/13671707",
"skill_skill/13671407",
"skill_skill/13671239",
"skill_skill/13671155",
"skill_skill/13671017",
"skill_skill/13671005",
"skill_skill/13670987"
]
Problem:
inserts a null value into an array which then seems to break the logging system and lengths of arrays are not correct and its unreliable
Expected result: AQL result should not return null results

Looks like the intended behavior to me... Let me explain:
In a minimal graph A --y--> B --z--> C, you may traverse from A in outbound direction with a variable depth of min=1 and max=2. If you return the emitted vertex, then the output would be B and C: The traversal starts at A, follows the edge to B and emits it, continues to C and emits it. If you return the emitted edge instead, then you would get y and z.
If you want to return the vertices including the start vertex A, then you can set the min depth=0, so that it gets emitted as first vertex. The result would then be A, B and C. If you return the edges instead however, what you get is null, y and z. The reason should be obvious: no edge leading to the start vertex A is followed which could be returned. While there might be edges connected to A in your graph, but they are not traversed if A is the starting point. Returning a random edge would make no sense. Because there is no value, a null value is given.
If all you want to do is to return the traversed edges, then use a minimal depth of 1, not 0:
FOR vertex, edge IN 1..1 OUTBOUND "skills/MM" graph 'skills_hierarchy'
  RETURN edge._to

ok, so what about SHORTEST path returning a null entry? That really doesn't make any sense
FOR vertex, edge IN INBOUND SHORTEST_PATH 'skills/MM-PUR' TO 'skills/SCOPE_ITEM' GRAPH 'skills_hierarchy' return edge
[   null,   {     "_key": "13714256",     "_id": "skill_skill/13714256",     "_from": "skills/2R7.KP.7",     "_to": "skills/MM-PUR",     "_rev": "_YX6uQTy---",     "type": "app_scope"   },   {     "_key": "13713352",     "_id": "skill_skill/13713352",     "_from": "skills/2R7",     "_to": "skills/2R7.KP.7",     "_rev": "_YX6uPvK---",     "type": "child"   },   {     "_key": "13713185",     "_id": "skill_skill/13713185",     "_from": "skills/SCOPE_ITEM",     "_to": "skills/2R7",     "_rev": "_YX6uPny---",     "type": "child"   } ]

Note that a path with n vertices has n-1 edges. The shortest path query returns all vertices along the path, each together with its incoming edge on the path. But the start vertex does not have such an edge; it is always null.
So say you execute the query FOR v, e IN OUTBOUND SHORTEST_PATH s TO t GRAPH 'G' RETURN {v, e}, and the path returned is A --y--> B --z--> C. Then this would return [ {v: A, e: null}, {v: B, e: y}, {v: C, e: z} ].
So the reason here is the same as in the traversal.

Hmm, Ok.
It makes sense I suppose but isn't very intuitive to me. Thanks for the explanation.


dubbo demo中没有用到dubbo-registry-kubernetes，而且dubbo-config中没有k8s的对接

Environment

Dubbo version: 3
Operating System version: kubernetes3
Java version: 8

Steps to reproduce this issue

dubbo3的dubbo-demo中，没有找到dubbo-registry-kubernetes
dubbo3的dubbo-demo中，没有找到dubbo-configcenter(如何与k8s对接)

Pls. provide [GitHub address] to reproduce this issue.
Expected Result
和spring-cloud-kubernetes一样，解决了两个注册中心、两个配置中心的问题

You can find a demo usinig dubbo-registry-kuubernetes in the project "apache/dubbo-samples".

dubbo3 has not implemented the config center through the k8s.Maybe dubbo3 will implement the config center through the k8s.However,it seems not nesscessary to use the config center directly on k8s.Since the version 2.7.6,dubbo use Service Introspection(服务自省).One of the reason is decentralization(去中心化).The metadata is used to store in the registry before 2.7.4.Now dubbo provide a way to store the metadata in the provider,and one of the way for the consumer to get the metadata of providers is to use rpc to invoke the MetadataService of the providers.This way will reduce stress of the config center.However,using the MetadataService will stress the k8s much.It is recommented to use nacos or appolo as the config center in the production environment.

You can refer to the content of this project：https://github.com/apache/dubbo-samples
The above answer should solve your problem


PyFerret STOP on loading color palettes

Reported by ansley b manke on 11 Oct 2017 17:02 UTC
For some combinations of color palettes and color levels, drawing a second color plot causes a STOP in PyFerret,
yes? let fcn = 0.5*COS(J[fill/pal=land_sea_values/lev=vc 7000*fcn

yes? fill/pal=ocean_temp_bounds/lev=(-2,35,2)  18/5* fcn
STOP FGD_GSCR: Invalid redfrac

In Ferret, this same issue is seen but we just get several gks messages, and the plot is drawn successfully.
...
yes? fill/pal=ocean_temp_bounds/lev=(-2,35,2)  18/5* fcn
gsetcolourrep()   96 Colour is outside range [0,1](j=1:100]/30)+SIN(K[k=1:100]/20)
yes?)
gsetcolourrep()   96 Colour is outside range [0,1]
...

On starting a color plot, Ferret goes and loads the colors from the palette into data structures and also loads the color levels if they've been set and associates colors from the palette with color levels. Information from the first plot, with 26 distinct color levels is being incorrectly re-used in the setup stages for the second plot which is going to have just 19 color levels.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2564

This was fixed in plt/disp_prep.F


plantseg boundaries

Hi,
We are having quite nice plantseg boundaries, but it seems that ultrack sometimes produces a "funny" segmentation:

Do you have a suspicion why the cell in the center could only be segmented half?

Awesome! min_frontier sounds super useful!

I'll leave this open until we add to the FAQ


Add documentation for new Transfer info feature

The new feature needs to be well documented. Add docs to readme and official docs.

Resolved in https://github.com/paraspell/xcm-tools/commit/7754941e639f75d0e3882cc627103c0881d0c148


new project is created in current working directory instead of new folder

Summary
Maybe this is by design but just in case it's not...
When I create a new app I would expect a new folder to get created for that app, but the app is created in cwd.
Steps To Reproduce:
cd ~
npx lwc-create-app my-app

Expected result
New project is created at ~/my-app
Actual result
New project is created at ~

Does that happen to you outside of the home folder?

The error message in #2 is related to that.

@muenzpraeger Yes, I just used ~ as an example, I actually used /Users/wes/source/repos and still hit this issue

I just ran the command and can't reproduce it. Is that on Linux or Mac?

This is on macOS.  Figured out the problem, I was using node v8.11.3
After updating to node v10.15.3 this issue and #4 were fixed.
Maybe the tool should hard block if the node version is below 10?

BTW, I selected "node" instead of "yarn" originally... I just tried again on node v8.x and selected yarn and now I see there are many errors shown that make it apparent this version of node won't work, but if you select NPM there is 1 small error shown that gets scrolled off the screen, so that's why I missed it.
When selecting yarn:

When selecting node (this gets scrolled off the screen immediately):

In both cases the tool continues, I'm thinking maybe just have the tool do a node version check right up front and exit if not 10+... @muenzpraeger would you like me to open an issue for that feature request?

Thanks for digging that, @wes566! I'm working already on a PR with another change, so I'll add that check.


AIOC and SVXLINK

Hello all,
I'm trying AIOC with Svxlink repeater software,
AIOC is detected and audio level on alsamixer are available and /dev/hidraw0 is present on my Raspberry Pi.
For RX config is for a CM108 and SQUELCH(COS) detection on VOL_DW pin 48.
HID_DEVICE=/dev/hidraw0
HID_SQL_PIN=VOL_DN
SQL_DET=HIDRAW
For TX config:
PTT_TYPE=Hidraw
HID_DEVICE=/dev/hidraw0
HID_PTT_PIN=GPIO3
I have this error:
Wed Sep 11 10:04:09 2024: *** ERROR: unknown/unsupported sound chip detected...
Wed Sep 11 10:04:09 2024: *** ERROR: Squelch detector initialization failed for RX "Rx1"
Wed Sep 11 10:04:09 2024: *** ERROR: Could not initialize RX "Rx1"
Wed Sep 11 10:04:09 2024: *** ERROR: Could not initialize Logic object "SimplexLogic". Skipping...
Have you an idea to resolve this problem?
Maybe HID_SQL_PIN=VOL_DN isn't correct for AIOC.

Hi!,
Thanks for your reply.
I'll try and report back on this thread.

Hi,
I have AIOC on SvxLink, and I can confirm the solution from G1LRO works.
I have also tried aioc-fw-1.3.0-rc.2.bin and setting the VID and PID to "Bus 001 Device 006: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter" with the Python script provided in the release notes: write(aioc, Register.USBID, (0x0d8c << 0) | (0x000c << 16)) also works!
Thanks @F8ASB for the settings provided:
Rx settings:
HID_DEVICE=/dev/hidraw0
HID_SQL_PIN=VOL_DN
SQL_DET=HIDRAW
Tx settings:
PTT_TYPE=Hidraw
HID_DEVICE=/dev/hidraw0
HID_PTT_PIN=GPIO3
It works, but with both solutions, when the station stops transmitting, I get Rx triggered after approximately 500ms, and the signal (silence) lasts around 300ms. (Rx is sending a short silence to SvxLink, and the AIOC green light is brighter, indicating it is receiving something.)
Why is Rx getting triggered (immediately) after Tx?
My current, not-so-good workaround/solution is to have two Rx settings and use "Voter" where I can set VOTING_DELAY=600.
P.S.: SvxLink runs in userspace as the user "svxlink", so it needed permissions to use /dev/hidraw0, like this:
cat /etc/udev/rules.d/99-hidraw.rules
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0660", GROUP="plugdev"
#Or if I would allow only (ID 0d8c:000c)
#KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="0d8c", ATTRS{idProduct}=="000c", MODE="0660", GROUP="plugdev"

sudo usermod -aG plugdev svxlink

sudo udevadm control --reload-rules
sudo udevadm trigger


Allow for version arguments to accept version matching operators

Hi 👋
It was brought up to my attention in this discussion https://github.com/fastlane/fastlane/issues/20866#issuecomment-1319016098 that xcversion and xcodes version resolvers work different. I started wondering whether xcodes accepts Ruby's Pessimistic Operator or an equivalent behavior (even if with a different syntax). If not, is this something we'd be interested in developing? It seems like there are users interested in it.
Thanks in advance!

👋 Hi y'all
I posted about ~> in the Fastlane repo.
My two cents: This is not a required feature. I mentioned it only in the context of backward compatibility with the pre-xcodes behavior in the ensure_xcode_version Fastlane action.
The way I look at xcodes and its .xcode-version is the same as a lockfile such as Package.resolved or Podfile.lock. They define a specific version that the tool can use to ensure different machines will operate with the same version tools. Under that assumption, allowing users to specify a range of versions would not achieve the desired purpose, because there would be no way to ensure every machine runs the same version.
For what is worth, rbenv does not support the operator. I mention rbenv because it is a tool a non trivial portion of xcodes users would be familiar with because of the still relevant presence of Ruby tooling (e.g. Fastlane and CocoaPods).
# .ruby-version with content...
~> 2.7

# ...will throw the following error
rbenv: version `~>' is not installed (set by /work/directory/.ruby-version)


ParetoNBDModel population distribution sampling and save/load test

This PR is a prerequisite to use the plotting functions in https://github.com/pymc-labs/pymc-marketing/issues/326 for the ParetoNBDModel. I also added a test for the save/load functionality.
This PR is still a draft until I figure out why pytest can't detect the customer_id column in the test dataset. More importantly, the rtol is failing for the distribution tests. Could this have something to do with HalfFlat priors being used for posterior predictive sampling? ParetoNBDModel uses Weibull priors by default.
Also, the naming conventions here are slightly different compared to the equivalent methods in other models. I'm not sure how I feel about including 'new_customer' in the name because these distributions were estimated from existing customers.

:books: Documentation preview :books:: https://pymc-marketing--327.org.readthedocs.build/en/327/

Could this have something to do with HalfFlat priors being used for posterior predictive sampling?

Those are just dummy variables in Posterior predictive, that are replaced by the draws from the trace. Some explanations in this blogpost: https://www.pymc-labs.io/blog-posts/out-of-model-predictions-with-pymc/  Look for Flat uses in it.

More importantly, the rtol is failing for the distribution tests.

Isn't your rtol just too restrictive. If you sample two identical Gamma with those parameters and sample size doesn't it fail as well?

Tests pass when N is increased to 10,000. If there are any objections to setting it that high let me know, but after a visual inspection, heavy-tailed distributions are pretty common with this model. I'd prefer a large sample size so users don't run into similar issues.

10k seems pretty extreme. If users do the normal fit with 4k draws, that's what they get back.
For tests purposes it's fine to have a higher rtol

After adding some plots to the dev notebook, I noticed the X-axis for these PDFs didn't quite look right. I think pm.Gamma needs to be parametrized with mu and sigma instead of alpha and beta, in which case https://github.com/pymc-labs/pymc-marketing/pull/303 will also need to be revised.
Using mu and sigma requires dramatically larger tolerances. I had to set rtol=0.5, N=4000 just to get these tests to pass.

I'm not sure how I feel about including 'new_customer' in the name because these distributions were estimated from existing customers.

The posterior population distribution is the prior distribution for a new customer after inference. The distribution for the observed customers should actually be different and are unlikely to still be a Gamma. You don't have access to them because they were marginalized during sampling. I think the new_customer suffix makes sense in this light.

The population distribution you are sampling is the posterior predictive distribution for a new customer after doing inference on your current customers. That is, your updated prior, for what a new customer might be like.

After considering the distributions for individual customers, this makes sense. I'm about to leave for the weekend, but I'll change the names after I get back. Adding dedicated plotting functions for these distributions would require standardizing method names across all models, but I'm sure how advantageous this would be over just using something like arviz.plot_dist.
I'll also try using arviz.plot_dist with these methods instead of seaborn.

I don't know if the ParetoNBDModel has closed form solutions that allow you to recover the individual posteriors, but those would belong to a separate method.

It does, and it's on my list of things to add:
https://github.com/pymc-labs/pymc-marketing/pull/327#issuecomment-1636122278

Method names have been changed and tests are passing with N=4000 and rtol=0.05 with the conversion from scale to rate. I've also added a variety of plotting options to the dev notebook.
I noticed this warning for the save/load functionality which is also impacting BetaGeoModel:
tests/clv/models/test_pareto_nbd.py::TestParetoNBDModel::test_save_load_pareto_nbd
  /python3.8/site-packages/arviz/data/inference_data.py:152: UserWarning: fit_data group is not defined in the InferenceData scheme
    warnings.warn(

I realized yesterday the ParetoNBD distribution block can also be included in _distribution_new_customers to simulate customer transactions! I'll get this added to the PR.
I'm also wondering if _distribution_new_customers should be extended to support sample_prior_predictive. There is a property for this in the base class, but I haven't found a way to use it for these purchase and dropout distributions.

I'm also wondering if _distribution_new_customers should be extended to support sample_prior_predictive

Sounds like a good idea

I'm also wondering if _distribution_new_customers should be extended to support sample_prior_predictive

Sounds like a good idea

Does this mean CLVModel.sample_prior_predictive and CLVModel.prior_predictive can both be removed after _distribution_new_customers supports this for all models? If so I'll do that in a future PR.

I am not sure about removing prior predictive. What does it do now?

Reduced N to 1k and widened the rtol a bit so these functions sample faster for end users. The notebook is a mess of ideas I need to clean up before merging.
Please look over my latest commit: It's a work-in-progress refactoring for prior predictive sampling and eliminating _distribution_new_customers. How important is it that the returned object be an xarray.Dataset?

It could also permit prior sampling from the purchase and dropout rate distributions if those variables are added to ParetoNBDModel.model, but sampling would be much slower in that scenario, so it's better to leave them in _distribution_new_customers.

We don't have to use the model in build_model for prior / posterior predictive checks. There is little reason to do so in these CLV models with marginalized variables. Still it then raises the question of what should sample_prior_predictive do. If it's too ambiguous for users / there are many things they would want, then using the specialized methods like distribution_new_customers sounds like a better approach.
Note that you can use pm.sample_posterior_predictive to do prior predictive as well. Just pass an empty trace and you'll get prior predictive draws. That way you may be able to reuse the same code more easily?
However, prior_predictive will fail with default HalfFalt priors because those can't be taken draws. Not a problem for this model, but something to keep in mind for others.

How important is it that the returned object be an xarray.Dataset?

Quite important for consistency and visualization with arviz

Note that you can use pm.sample_posterior_predictive to do prior predictive as well. Just pass an empty trace and you'll get prior predictive draws. That way you may be able to reuse the same code more easily?

I'd prefer this approach over attempting to reinvent the wheel to save a few lines of code. What does passing an empty trace look like? I tried this, It seems the trace argument is required:
with self.model:
    self.idata.extend(pm.sample_posterior_predictive())

Oh sorry I meant calling pm.sample_prior_predictive() on the same model where you would call sample_posterior_predictive to get the same kind of draws

Oh sorry I meant calling pm.sample_prior_predictive() on the same model where you would call sample_posterior_predictive to get the same kind of draws

Would this still work properly with the dummy HalfFlat priors though? I thought the priors would need to match that of base_model for a prior predictive check.

Still it then raises the question of what should sample_prior_predictive do. If it's too ambiguous for users / there are many things they would want,

I've been thinking about this, and honestly don't see it coming up a lot in practice. We can already do both prior and post predictive checks with the ParetoNBD block, which is far more important because it pertains to the frequency of purchases and will be used for model evaluations. I'd rather not hold up this PR trying to get prior checks to work with the rate distributions, so I'll archive the code I wrote in that last commit in case anyone requests this in the future.

I've cleaned up the dev notebook and decided to go with the existing code convention that is also used in other models.
I'm not sure how useful a prior predictive check is for the customer purchase and dropout distributions since there is no observable data to compare against. There's an example in the dev notebook on how to do this plot, but adding this functionality to the CLV module is enough work to warrant a separate PR.
I'll save the customer purchase sampling/simulation for another PR as well to keep this one more focused. There's a lot of code relevant to the customer purchase distribution in the notebook already, so I'll work on that PR next.
Lastly, the shape_kwargs = {} line in the if/else block isn't being covered by the tests (it requires an arviz.idata object with chain and draw > 1) but I worked with a fitted MCMC model in the notebook, so it's not causing any problems. If that's cool, I think we're good to merge.

We can go ahead and merge this if you want, but I've decided to append the prior predictives for the purchase and dropout rate distributions to the returned xarray.Dataset containing the posterior predictives for those respective methods.
Also gonna add the population ParetoNBD class to _distribution_new_customers and give it its own similar method with prior and posterior predictives (it could call BaseModel.sample_posterior_predictive under the hood).
Lastly, I think _distribution_new_customers should be expanded and renamed to what it basically is: _sample_posterior_predictive, with an arg to extend to self.idata.

That failing test was for the work we decided to move to a future PR. I've backed it up in a new branch and removed it from this one.


enhance org-mode faces

This is the screenshot which doom-one theme has issue that some org-mode headlines are not colored.
And some org-mode faces like org-priority are not customized.
Hope you can add support to all org-mode faces from customize-group org-faces.

You're correct, this is due to how I used org-mode at the time. I'll fix this soon.

I've made headline colors more consistent and added org-priority. I'll investigate other org faces.
Are there any particular ones that stand out to you?

Seems like the issue is fixed. Thanks @hlissner


Resolve bugs in generated single op tests

Fixes https://github.com/tenstorrent/tt-forge-fe/issues/643

Add input node dtypes as data member in Operation class
In _determine_node_dtype function before checking framework_dtype is N/A, add a condition to check whether the framework_dtype key is present in the node attrs because the kernel/op node doesn't have framework_dtype as key inside the node attrs.
In write_pytest_function method in python_codegen.py file, currently we are creating rand input tensor for all the dtypes, instead for floating dtype we will use torch.rand function and for integer datatype we will use torch.randint with high value equal to 1000.
Note: For torch.randint high value is set to 1000 instead of the respective integer dtype max value because there is some special case like passing input_ids to embeding op and input_ids will be integer datatype. In that case there is possibility of generating higher integer value by torch.randint which is greater than vocab_size in embedding op, which leads error in embedding op execution.
In generated pytest function by write_pytest_function method, framework_output will be of TensorFromTrace, converted the TensorFromTrace to the particular framework and then passed to the compare_with_golden function
Instead of passing dumping input tensor to the forge module forward function, if all the inputs for the particular op is parameter or const, we will pass the parameter/const as input to the forge module forward function and in the pytest function instead generating rand values for the parameter/const as input to the forge module forward function, will load the actual values from the model parameter/buffers.For the particular op, if only the some inputs are parameter/const, we will not pass parameter/const as input to the forge module forward function. Eg: For matmul op, if operand_A is forward function input and operand_B is parameter, it will remain same for single generated op.

@nvukobratTT  FYI, the unique op generation has some changes with respect to this PR in write_pytest_functions in ForgeWriter. will update the PR with above comments and unique op generation too.

@nvukobratTT FYI, the unique op generation has some changes with respect to this PR in write_pytest_functions in ForgeWriter. will update the PR with above comments and unique op generation too.

Sure, just make sure to link this PR to both issues :))

@chandrasekaranpradeep what is the state of this PR?

@nvukobratTT Bug fixing in the generation of single op test is merged into main in  this PR, so closing this issue


Remove localized links

See #686

If anyone can find non-localized URL variants for the links mentioned in #686, will be pretty helpful.


Add support for over-riding 'wildfly' user home directory. Added test…

… to exercise

Coverage remained the same at 74.385% when pulling c503671d590b4b963fff70c4c3750df8a5191aba on weareact:support_setting_homedir into 7ea34d96103c203e743dbffcf3c9c50c63247698 on biemond:master.


built and uploaded successfully but loading forever on microros

Hello, Hope yall have a nice a day
i`ve followed the steps to build for my esp32-wroom and builded successfully and i uploaded the hex on my esp which went successfull as well I run:
ros2 run micro_ros_agent micro_ros_agent serial --dev /dev/ttyUSB0 --baudrate 921600
which gave me this:

i.e im using ubuntu mate 20.04 , esp32-wroom , mpu9250 which i configured in /custom/esp32_config.h
and I tried to run the bringup using serial port /dev/ttyUSB0 (without connecting the lidar as you mentioned) and im getting this output as well which also continue running forever

Please use copy & paste the screen output. It will be clear as my eyes are not so good with screen captured. :)

In your first message, the micro-ros is not connected.
In your second message, the rplidar driver got error. which model do you use?

So, we shall focus on the micro-ros connection first. Please comment out the IMU setting in esp32_config.h. This is step 2 in the workflow described in my wiki. Make sure the micro-ros is connected and the topics are checked.
https://github.com/hippo5329/linorobot2_hardware/wiki#test-micro-ros-agent-connection-before-wiring-and-building-the-robots---recommended

After the micro-ros connection test success, proceed to step 3 in workflow, wire and enable the IMU. Add two 2k resistors pull up to 3.3 on the sda and scl lines. Run the test_sesnors.
https://github.com/hippo5329/linorobot2_hardware/wiki#connect-the-imu-and-test_sensors
Then follow the workflow step-by-step.
In step 8, robot bringup, you will need to use the long by-path device names.
https://github.com/hippo5329/linorobot2_hardware/wiki#esp32-with-serial-transport-and-lidar-on-the-robot-computer

hello again, i followed your discussion in this issue solved the first problem and now my imu is working well and tested it with esp32 but , for the second part im still getting this issue:
[rplidar_composition-5] [ERROR] [1717896175.095175069] [rplidar_composition]: Error, operation time out. RESULT_OPERATION_TIMEOUT!
and this is my command:
ros2 launch linorobot2_bringup bringup.launch.py
base_serial_port:=/dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0-port0
lidar_serial_port:=/dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0-port0
reinstalled my linorobot2 and still getting this error also im on ros foxy and followed the wiki where you mentioned this https://github.com/hippo5329/linorobot2_hardware/wiki#install-linorobot2-on-ubuntu-2004-and-foxy

What is your lidar model? What is the laser_type you used to install linorobot2?
For rplidar a1m8, use a1.
For rplidar a2m8, use a2m8.

https://github.com/Slamtec/sllidar_ros2
Please try the launch to view lidar in rviz.
eg, for a1,
ros2 launch sllidar_ros2 view_sllidar_a1_launch.py serial_port:=< your by-path>
this->declare_parameterstd::string("serial_port", "/dev/ttyUSB0");
I will check the bringup launch later.

well i runned it and gave me this:
[INFO] [launch]: All log files can be found below /home/mobile/ros_logs/2024-06-09-04-52-07-218499-MOBILE-4332
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [sllidar_node-1]: process started with pid [4337]
[INFO] [rviz2-2]: process started with pid [4339]
[sllidar_node-1] [INFO] [1717897928.381700731] [sllidar_node]: SLLidar running on ROS2 package SLLidar.ROS2 SDK Version:1.0.1, SLLIDAR SDK Version:2.1.0
[rviz2-2] [INFO] [1717897930.769481769] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] [INFO] [1717897930.770111339] [rviz2]: OpenGl version: 2.1 (GLSL 1.2)
[sllidar_node-1] [ERROR] [1717897930.888376671] [sllidar_node]: Error, operation time out. SL_RESULT_OPERATION_TIMEOUT!
[ERROR] [sllidar_node-1]: process has died [pid 4337, exit code 255, cmd '/home/mobile/linorobot2_ws/install/sllidar_ros2/lib/sllidar_ros2/sllidar_node --ros-args -r __node:=sllidar_node --params-file /tmp/launch_params_rsz4_6fs'].
[rviz2-2] [INFO] [1717897930.941909150] [rviz2]: Stereo is NOT SUPPORTED
and this is rviz:

Do you use rplidar a1?

yes im using a1m8 and specified a1 during installation also i know that the a1 works with 115200 baudrate and checked my usb port baudrate and was 115200 + i replaced the cables to ensure that its not hardware problem

Let focus on the lidar, unlpug both esp32 and lidar.  Close all launch. Then plug the lidar. It will become ttyUSB0, the default port. Run the view launch.

ros2 launch sllidar_ros2 view_sllidar_a1_launch.py

same output:

and
[INFO] [launch]: All log files can be found below /home/mobile/ros_logs/2024-06-09-05-03-06-300402-MOBILE-8107
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [sllidar_node-1]: process started with pid [8109]
[INFO] [rviz2-2]: process started with pid [8111]
[sllidar_node-1] [INFO] [1717898586.685857693] [sllidar_node]: SLLidar running on ROS2 package SLLidar.ROS2 SDK Version:1.0.1, SLLIDAR SDK Version:2.1.0
[rviz2-2] [INFO] [1717898588.284313932] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] [INFO] [1717898588.284992264] [rviz2]: OpenGl version: 2.1 (GLSL 1.2)
[rviz2-2] [INFO] [1717898588.405806314] [rviz2]: Stereo is NOT SUPPORTED
[sllidar_node-1] [ERROR] [1717898589.195244969] [sllidar_node]: Error, operation time out. SL_RESULT_OPERATION_TIMEOUT!
[ERROR] [sllidar_node-1]: process has died [pid 8109, exit code 255, cmd '/home/mobile/linorobot2_ws/install/sllidar_ros2/lib/sllidar_ros2/sllidar_node --ros-args -r __node:=sllidar_node --params-file /tmp/launch_params_a6hg_7j7'].

Check it on a PC, ubuntu 22.04 Humble. or  ubuntu 20.04 Foxy.
Follow the readme to install, build and test view.
https://github.com/Slamtec/sllidar_ros2

No linorobot2. Just slamtec along.

same output as linorobot

[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [sllidar_node-1]: process started with pid [16147]
[INFO] [rviz2-2]: process started with pid [16149]
[sllidar_node-1] [INFO] [1717900157.064414454] [sllidar_node]: SLLidar running on ROS2 package SLLidar.ROS2 SDK Version:1.0.1, SLLIDAR SDK Version:2.1.0
[sllidar_node-1] [INFO] [1717900157.574401167] [sllidar_node]: SLLidar S/N: D9E999F6C9E59AD4C5E59CF7253B3414
[sllidar_node-1] [INFO] [1717900157.574556904] [sllidar_node]: Firmware Ver: 1.29
[sllidar_node-1] [INFO] [1717900157.574610143] [sllidar_node]: Hardware Rev: 7
[rviz2-2] [INFO] [1717900158.629105244] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] [INFO] [1717900158.629738763] [rviz2]: OpenGl version: 2.1 (GLSL 1.2)
[rviz2-2] [INFO] [1717900158.754220721] [rviz2]: Stereo is NOT SUPPORTED
[sllidar_node-1] [ERROR] [1717900159.574791862] [sllidar_node]: Error, cannot retrieve SLLidar health code: 80008002
[ERROR] [sllidar_node-1]: process has died [pid 16147, exit code 255, cmd '/home/mobile/ros2_ws/install/sllidar_ros2/lib/sllidar_ros2/sllidar_node --ros-args -r __node:=sllidar_node --params-file /tmp/launch_params_w9za907z'].

If it doesn't work on PC, then it maybe problem of the lidar.

I already tested before getting into the esp32 part and it worked well idk what happened, will try few solutions hoping it will work, thank you for your precious time I will an update once I reach out something

Ok. Please note I forced updated the foxy branch on hippo5329/linorobot2. Now all ros2 branches use the same code. Please remove ~/linorobot2_ws and reinstall.

hello again, I did some hardware checkups and changes and reinstalled from the main repo:
https://github.com/linorobot/linorobot2
I tested the lidar alone using ros2 run rplidar_ros rplidar_composition --ros-args -p serial_port:=/dev/ttyUSB0 -p frame_id:=laser_frame and it went well and showed up in rviz then I connected my esp32 and run the same bringup command but its still stuck at this point:
[rplidar_composition-5] [INFO] [1717928299.702748488] [rplidar_composition]: Firmware Ver: 1.29
[rplidar_composition-5] [INFO] [1717928299.702845507] [rplidar_composition]: Hardware Rev: 7
[rplidar_composition-5] [INFO] [1717928299.704417308] [rplidar_composition]: RPLidar health status : '0'
[rplidar_composition-5] [INFO] [1717928300.248326987] [rplidar_composition]: current scan mode: Sensitivity, max_distance: 12.0 m, Point number: 7.9K , angle_compensate: 2, flip_x_axis 0

This is another rplidar driver, which does not take serial port parameter.
    Node(
        condition=LaunchConfigurationEquals('sensor', 'rplidar'),
        name='rplidar_composition',
        package='rplidar_ros',
        executable='rplidar_composition',
        output='screen',
        remappings=[('scan', LaunchConfiguration('topic_name'))],
        parameters=[{
            'serial_port': '/dev/ttyUSB0',
            'serial_baudrate': 115200,  # A1 / A2
            'frame_id': LaunchConfiguration('frame_id'),
            'inverted': False,
            'angle_compensate': True,
        }],
    ),

In later humble update,
def launch_rplidar(context, *args, **kwargs):
lidar_str = context.perform_substitution(LaunchConfiguration('sensor'))
rplidar_sensors = [
'a1',
'a2',
'a3',
'c1',
's1',
's2',
's3',
]
if lidar_str in rplidar_sensors:
    launch_file = f'sllidar_{lidar_str}_launch.py'
    return [IncludeLaunchDescription(
        PythonLaunchDescriptionSource(PathJoinSubstitution(
            [FindPackageShare('sllidar_ros2'), 'launch', launch_file]
        )),
        launch_arguments={
            'serial_port': '/dev/rplidar',
            'frame_id': LaunchConfiguration('frame_id'),
        }.items()
    )]
else:
    return []

So sllidar uses /dev/rplidar . Check udev rules. Can you find /dev/rplidar ?

I changed the serial port in my fork.
'serial_port': LaunchConfiguration('lidar_serial_port'),

If there is /dev/rplidar, try lidar_serial_port:=/dev/rpliar in my fork.

# set the udev rule , make the device_port be fixed by rplidar
#
KERNEL=="ttyUSB*", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", MODE:="0777", SYMLINK+="rplidar"

I recalled that all the lidars use mostly the same usb id 10c4:ea60. So they all mixed up with esp32 usb port. That's why I added the lidar_serial_port parameter, which is not merged to linorobot/linorobot2 yet. I did send the PR.
For foxy, the old rplidar_composition drive might work better. I am not sure if the new sllidar driver works, though foxy is shown on their pages.
The linorobot/linorobot2 foxy branch does not have serial port parameter. I will add it when I have time.

I  added lidar_serial_port parameter to hippo5329/linorobot2 foxy branch, forced updated. Please try out.

hello again, I found out that my lidar work 1 time out of 5 times and when i try to do so it gives me the same error or error 800800 or 8008002 but when spamming the command it worked few times and i was able to bringup the robot successfully and everything was going well

even tested creating a map and saving it successfully

I will try the fixed branch tho and give you update soon

I found this on rplidar error. "So I identified the problem was primarily due to the inadequate power from the usb ports. Once I switched to a external powered usb hub, it was solved."

ubuntu@humble:~/ros2_ws$ ros2 launch sllidar_ros2 view_sllidar_a1_launch.py
[INFO] [launch]: All log files can be found below /home/ubuntu/.ros/log/2024-06-11-15-27-23-060774-humble-4039
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [sllidar_node-1]: process started with pid [4040]
[INFO] [rviz2-2]: process started with pid [4042]
[sllidar_node-1] [INFO] [1718144843.457328743] [sllidar_node]: SLLidar running on ROS2 package SLLidar.ROS2 SDK Version:1.0.1, SLLIDAR SDK Version:2.1.0
[sllidar_node-1] [INFO] [1718144843.483534427] [sllidar_node]: SLLidar S/N: 858AED93C0EA98C7A0E69BF515544560
[sllidar_node-1] [INFO] [1718144843.483681046] [sllidar_node]: Firmware Ver: 1.29
[sllidar_node-1] [INFO] [1718144843.483709158] [sllidar_node]: Hardware Rev: 7
[sllidar_node-1] [INFO] [1718144843.485836082] [sllidar_node]: SLLidar health status : 0
[sllidar_node-1] [INFO] [1718144843.485888857] [sllidar_node]: SLLidar health status : OK.
[rviz2-2] [INFO] [1718144844.275075450] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] [INFO] [1718144844.276877201] [rviz2]: OpenGl version: 4.5 (GLSL 4.5)
[rviz2-2] [INFO] [1718144844.495324669] [rviz2]: Stereo is NOT SUPPORTED
[sllidar_node-1] [ERROR] [1718144845.495982716] [sllidar_node]: Can not start scan: 80008000!

So rplidar usb power is critical.
tested rplidar a1m8 on foxy pc.
bringup
ubuntu@mint-tiger:~$ ros2 launch linorobot2_bringup bringup.launch.py \

base_serial_port:=/dev/ttyUSB1 lidar_serial_port:=/dev/ttyUSB0

[INFO] [launch]: All log files can be found below /home/ubuntu/.ros/log/2024-06-12-01-35-41-903361-mint-tiger-18450
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [ekf_node-1]: process started with pid [18453]
[INFO] [micro_ros_agent-2]: process started with pid [18455]
[INFO] [joint_state_publisher-3]: process started with pid [18457]
[INFO] [robot_state_publisher-4]: process started with pid [18459]
[INFO] [rplidar_composition-5]: process started with pid [18462]
[micro_ros_agent-2] [1718156142.090901] info     | TermiosAgentLinux.cpp | init                     | running...             | fd: 3
[micro_ros_agent-2] [1718156142.091073] info     | Root.cpp           | set_verbose_level        | logger setup           | verbose_level: 4
[rplidar_composition-5] [INFO] [1718156142.122183538] [rplidar_composition]: RPLIDAR running on ROS 2 package rplidar_ros. SDK Version: '1.12.0'
[robot_state_publisher-4] Parsing robot urdf xml string.
[robot_state_publisher-4] Link base_link had 7 children
[robot_state_publisher-4] Link camera_link had 1 children
[robot_state_publisher-4] Link camera_depth_link had 0 children
[robot_state_publisher-4] Link front_caster_wheel_link had 0 children
[robot_state_publisher-4] Link imu_link had 0 children
[robot_state_publisher-4] Link laser had 0 children
[robot_state_publisher-4] Link left_wheel_link had 0 children
[robot_state_publisher-4] Link rear_caster_wheel_link had 0 children
[robot_state_publisher-4] Link right_wheel_link had 0 children
[robot_state_publisher-4] [INFO] [1718156142.136250728] [robot_state_publisher]: got segment base_footprint
[robot_state_publisher-4] [INFO] [1718156142.136356299] [robot_state_publisher]: got segment base_link
[robot_state_publisher-4] [INFO] [1718156142.136369812] [robot_state_publisher]: got segment camera_depth_link
[robot_state_publisher-4] [INFO] [1718156142.136378387] [robot_state_publisher]: got segment camera_link
[robot_state_publisher-4] [INFO] [1718156142.136386626] [robot_state_publisher]: got segment front_caster_wheel_link
[robot_state_publisher-4] [INFO] [1718156142.136395282] [robot_state_publisher]: got segment imu_link
[robot_state_publisher-4] [INFO] [1718156142.136403042] [robot_state_publisher]: got segment laser
[robot_state_publisher-4] [INFO] [1718156142.136410710] [robot_state_publisher]: got segment left_wheel_link
[robot_state_publisher-4] [INFO] [1718156142.136418574] [robot_state_publisher]: got segment rear_caster_wheel_link
[robot_state_publisher-4] [INFO] [1718156142.136426435] [robot_state_publisher]: got segment right_wheel_link
[micro_ros_agent-2] [1718156142.302477] info     | Root.cpp           | create_client            | create                 | client_key: 0x0D65C523, session_id: 0x81
[micro_ros_agent-2] [1718156142.302513] info     | SessionManager.hpp | establish_session        | session established    | client_key: 0x0D65C523, address: 0
[micro_ros_agent-2] [1718156142.320683] info     | ProxyClient.cpp    | create_participant       | participant created    | client_key: 0x0D65C523, participant_id: 0x000(1)
[micro_ros_agent-2] [1718156142.324658] info     | ProxyClient.cpp    | create_topic             | topic created          | client_key: 0x0D65C523, topic_id: 0x000(2), participant_id: 0x000(1)
[micro_ros_agent-2] [1718156142.326522] info     | ProxyClient.cpp    | create_publisher         | publisher created      | client_key: 0x0D65C523, publisher_id: 0x000(3), participant_id: 0x000(1)
[micro_ros_agent-2] [1718156142.329121] info     | ProxyClient.cpp    | create_datawriter        | datawriter created     | client_key: 0x0D65C523, datawriter_id: 0x000(5), publisher_id: 0x000(3)
[micro_ros_agent-2] [1718156142.332579] info     | ProxyClient.cpp    | create_topic             | topic created          | client_key: 0x0D65C523, topic_id: 0x001(2), participant_id: 0x000(1)
[micro_ros_agent-2] [1718156142.334490] info     | ProxyClient.cpp    | create_publisher         | publisher created      | client_key: 0x0D65C523, publisher_id: 0x001(3), participant_id: 0x000(1)
[micro_ros_agent-2] [1718156142.336925] info     | ProxyClient.cpp    | create_datawriter        | datawriter created     | client_key: 0x0D65C523, datawriter_id: 0x001(5), publisher_id: 0x001(3)
[micro_ros_agent-2] [1718156142.340485] info     | ProxyClient.cpp    | create_topic             | topic created          | client_key: 0x0D65C523, topic_id: 0x002(2), participant_id: 0x000(1)
[micro_ros_agent-2] [1718156142.342470] info     | ProxyClient.cpp    | create_publisher         | publisher created      | client_key: 0x0D65C523, publisher_id: 0x002(3), participant_id: 0x000(1)
[micro_ros_agent-2] [1718156142.344817] info     | ProxyClient.cpp    | create_datawriter        | datawriter created     | client_key: 0x0D65C523, datawriter_id: 0x002(5), publisher_id: 0x002(3)
[micro_ros_agent-2] [1718156142.347509] info     | ProxyClient.cpp    | create_topic             | topic created          | client_key: 0x0D65C523, topic_id: 0x003(2), participant_id: 0x000(1)
[micro_ros_agent-2] [1718156142.349492] info     | ProxyClient.cpp    | create_subscriber        | subscriber created     | client_key: 0x0D65C523, subscriber_id: 0x000(4), participant_id: 0x000(1)
[micro_ros_agent-2] [1718156142.351918] info     | ProxyClient.cpp    | create_datareader        | datareader created     | client_key: 0x0D65C523, datareader_id: 0x000(6), subscriber_id: 0x000(4)
[joint_state_publisher-3] [INFO] [1718156142.533176447] [joint_state_publisher]: Waiting for robot_description to be published on the robot_description topic...
[rplidar_composition-5] [INFO] [1718156144.630289598] [rplidar_composition]: RPLIDAR S/N: 858AED93C0EA98C7A0E69BF515544560
[rplidar_composition-5] [INFO] [1718156144.630421859] [rplidar_composition]: Firmware Ver: 1.29
[rplidar_composition-5] [INFO] [1718156144.630460166] [rplidar_composition]: Hardware Rev: 7
[rplidar_composition-5] [INFO] [1718156144.631959186] [rplidar_composition]: RPLidar health status : '0'
[rplidar_composition-5] [INFO] [1718156145.176588721] [rplidar_composition]: current scan mode: Sensitivity, max_distance: 12.0 m, Point number: 7.9K , angle_compensate: 2, flip_x_axis 0
ros2 topic hz /scan
WARNING: topic [/scan] does not appear to be published yet
average rate: 6.922
min: 0.135s max: 0.148s std dev: 0.00552s window: 8
average rate: 6.938
min: 0.134s max: 0.148s std dev: 0.00567s window: 15
average rate: 6.913
min: 0.134s max: 0.148s std dev: 0.00537s window: 22

slam
[INFO] [launch]: All log files can be found below /home/ubuntu/.ros/log/2024-06-12-01-37-45-781303-mint-tiger-18669
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [async_slam_toolbox_node-1]: process started with pid [18671]
[INFO] [rviz2-2]: process started with pid [18673]
[async_slam_toolbox_node-1] [INFO] [1718156265.944474008] [slam_toolbox]: Node using stack size 40000000
[async_slam_toolbox_node-1] [INFO] [1718156265.969043758] [slam_toolbox]: Using solver plugin solver_plugins::CeresSolver
[async_slam_toolbox_node-1] [INFO] [1718156265.969482815] [slam_toolbox]: CeresSolver: Using SCHUR_JACOBI preconditioner.
[async_slam_toolbox_node-1] Registering sensor: [Custom Described Lidar]
[rviz2-2] [INFO] [1718156266.227360181] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] [INFO] [1718156266.227530153] [rviz2]: OpenGl version: 4.6 (GLSL 4.6)
[rviz2-2] [INFO] [1718156266.261902970] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-2] Parsing robot urdf xml string.
[rviz2-2] [INFO] [1718156270.978455640] [rviz2]: Trying to create a map of size 24 x 44 using 1 swatches
[rviz2-2] [ERROR] [1718156270.985567155] [rviz2]: Vertex Program:rviz/glsl120/indexed_8bit_image.vert Fragment Program:rviz/glsl120/indexed_8bit_image.frag GLSL link result :
[rviz2-2] active samplers with a different type refer to the same texture image unit
[rviz2-2] [INFO] [1718156276.477405452] [rviz2]: Message Filter dropping message: frame 'laser' at time<PHONE_NUMBER>.468 for reason 'Unknown'

The laser scan displayed in rviz correctly.

hello again, found out I was powering the raspberry with 15w power supply which was bit confusing since rpi 4 need 15w also I ordered an official adapter and my pcb will be offering the 15w as well I will be testing the whole system on both of  them the next few days when i finish the assembly, I really think since its power related problem as you say since everything worked fine few times.

I think 15W power for rpi4 is fine. The problem is the power output voltage. Please check the 5V on the rpi4 with a multi-meter. There will be voltage drop from USB protection circuit. I used 5.25V power for rpi. You may check the VM on the tiny rplidar adapter.  You should use short USB cable. USB cables with fast charge support may have thicker wires. When the voltage on the rplidar is lower than 4.9V, it may not work well. This is a product design issue. I don't understand why their did not fix it. LD19 does not have such issue.
There is another issue in Slamtec sllidar_ros2 driver. The recent update has bug so most useful laser scan was discarded. I sent a pull request. I don't know when it will be merged. I am preparing another update on linorobot2 to resolve this.

I updated hippo5329/linorobot2. Please follow the updated wiki to install linorobot2. The sllidar issue is fixed. There is no need to use the old rplidar_ros package.


[feature request] transparent avatars in backers & sponsors widget

I'm placing backers & sponsors widget on a page with dark background, and find out that some avatars are not transparent, like this:

Could this widget embeds png format avatar images so that the white corner is removed? Or am I missing some control parameters?

closing this for lack of activity. Feel free to comment for re-opening.

Well I did not file a PR because I'm not familiar with the image processing service that OC uses (and seems it's paid). Given the green light I could have a try myself

For now the requested image format is determined by original extension:
https://github.com/opencollective/opencollective-images/blob/c4157bdb9c8ffcc5ed16d2da442d5b421a4af466/src/server/lib/utils.js#L22
If we want to avoid jpeg files, according to cloudary's doc, we could simply pass the format png regardless of its original.
Thoughts?

Hey @KagamiChan thanks for reporting this. I have not been able to reproduce the issue, in my tests transparency works properly when uploading a png file.

Could you try uploading your image files again?
If it doesn't solve the problem it would be really helpful if you could send me the original files you're using for me to reproduce the issue locally :slightly_smiling_face:

@Betree Sorry I should have made myself clearer. The issue only happens when the avatars are with .jpg extension. As the transformed images are also in jpeg format, the white margin outside the circle border will be white
This is not a problem when container background is also white (e.g. github pages), but when we want to show them on a page with background other than white, they could be easily observed
for example, webpack's backer list on blue background (some avatars fail to load, but it is irrelevant)

We could not make every user use png or gif format avatars, but this issue is important in terms of consistent appearance.


Add controller options to set reconciler DemoteFunc

Expected Behavior
Being able to set DemoteFunc when creating a controller.
Actual Behavior
Not possible.
Steps to Reproduce the Problem

Additional Info
Receive adapter internal state must be updated when demoting a bucket

/assign

/cc @mattmoor
First step to remove the leader election fork in eventing.


fix(@angular/build): simplify disabling server features with --no-server via command line

fix(@angular/build): simplify disabling server features with --no-server via command line
When outputMode is configured, --prerender and --app-shell become no-ops, making server feature disabling difficult without modifying the configuration.
This commit introduces the --no-server option, which can be used with --output-mode static to fully disable all server features.
ng build --output-mode static --no-server

fix(@angular/build): add warning when --prerendering or --app-shell are no-ops
Both options are ineffective when used with outputMode, so a warning is now issued.

The changes were merged into the following branches: main, 19.0.x


clustering with a strong backbone

Hi Yang Lei, may I ask another question?
the cluster problem will become easier with a stronger backbone( the face feature extractor ),  with the perfect backbone the similarity score between positive pairs would always be 1.0 and 0 for those negative pairs.
so I reckoned with the gap between the simple CW method and the GCN-V would be small before training, and then I found the results were almost identical...  to be clear, I didn't test it on a large dataset yet.
but that raises the questions here: what backbone and loss function did you used during the training?  Will the advantage of this method go away if you use a stronger backbone?
thanks!

Hi @yyang2xin , thanks for the question.
(1) For the ideal scenario, if the features are separable, then there exist several algorithms that can guarantee a perfect solution. As you suggested, both methods work well under that situation. We can consider another extreme situation that each data sample belongs to a different cluster, then if we apply a high threshold for all methods to partition each sample to a cluster, then we can obtain the same perfect results.
(2) If the feature extractor is not perfect, the performance gap depends on the data. Stronger features are likely to produce both better baseline and better learning-based clustering models. As the power of feature extractor increases, the performance gap may first enlarge and then decrease.
(3) As stated in the paper, we use standard ResNet-50 and softmax in our experiments. CDP gives an analysis on stronger backbone, which shows that stronger backbone brings further performance gain.


TextView "tap" sometimes not fired when links are used

Problem description
When anchor tags are used in TextViews and tapping on the text view on a part of the text that is not a link, it will never trigger (or delegate to its parent) a "tap" event.
Expected behavior
When tapping on a non-link part of a TextView, it should always trigger a "tap" event.
Environment

Tabris.js version: 3.6.0
OS: 13.7

Code snippet
Tap on the non-link part of the text views:

In the upper text view, "tap" event will not (or very rarely) fire.
In the lower text view, "tap" will always fire as expeted.

import {TextView, contentView, app, Composite, Layout, ConstraintLayout} from 'tabris';

contentView.append(
  <$>
    <TextView markupEnabled left top right font='24px' padding={16} onTapLink={e => console.log('textview1 link tapped')} onTap={() => console.log('textview1 tapped')}>
      View documentation

      View source code

      Write us <a<EMAIL_ADDRESS>email
    </TextView>
    <TextView markupEnabled left top='prev() 8' right font='24px' padding={16} onTap={() => console.log('textview2 tapped')}>
      View documentation

      View source code

      Write us an email
    </TextView>
  </$>
);

Exact dupliate of #2103, did I click the "Submit new issue" button twice?


Snake Game Using HTML,CSS,JS

In this we have sound features and u can feel the real game vibe
So I would like to add some Background realistic sounds and background

Already there check live link @MonishRaman

ya but this is new model

https://github.com/dhairyagothi/50_days_50_web_project/assets/140420819/17fd9f0f-efaa-4257-bf97-61411cb4418a


Avoid coding: utf-8 in Python 3 scripts

As far as I know, only Python 3 is supported. Therefore, get rid of coding: utf-8 in generated scripts, as UTF-8 is the default.
Also, it could be that module or import_name are not ASCII, but then I would rather add tests with non-ASCII module and function names.

This is not really valid, since you can use installer as library and make it install a wheel into Python 2 environment (in which case, IIRC, the coding info is needed).

This is not really valid, since you can use installer as library and make it install a wheel into Python 2 environment (in which case, IIRC, the coding info is needed).

If Python 2 target environments are supported, then yes, it's best to keep this as is for non-ASCII module and function names.
I may be mistaken, but I cannot find details about support for Python 2 environments in the documentation.

There might not be a mention of that in the docs. No matter that, I would leave the coding comment in place. It doesn't hurt us to keep it there.


telomere cap is not a DNA packaging complex

telomere cap complex (GO:0000782)
has parent
[DNA packaging complex]
it is 'protecting DNA' but it isn't really packaging is it?
although to be fair we should probably just remove
a [DNA packaging complex]
because most of the children have nothing to do with DNA packaging? (i.e NMS,  Ndc80 single-stranded DNA-dependent ATP-dependent DNA helicase complex, telomere cap)
(and it is defined
A protein complex that plays a role in the process of DNA packaging.
which isn't very helpful.
I would obsolete rather than try to define, since we don't have a "DNA packaging" process term.

See also #23212

This will be fixed by obsoletion of DNA packaging complex, see
#23212


WIP Cross Everything

The massive cross compilation. Let's try ghcjs and windows for now.
Windows will fail due to no plugin logic, but we can see how far we get without plugins.
GHCJS will also fail, so we'll be playing whack-a-mole for a while.

We have:

quite a bit of vendored stuff in contrib; this will eventually turn into patches in the haskell module.
quite a few changes in the cabal.project, which I think we can move into the cabal.project.local file that's generated on the fly for ghcjs.
a cardano-base bump, to get rid of the zlib dependency via digest (it's gone in cardano-base now...)
Killing of ANN HLint instructions replacing them with HLINT; this does not trigger the TH pipeline, which ANN does.

I intent to graft fixes required to get larger hydra coverage on top of this.

 Even though quite a bit is working hydra is choking on a lot.

I don't think we have realistic options to cross compile agda, so we'll need to disable that outright for cross compilation.

Maybe we should start trying to cross compile a few things and work up, rather than trying everything and working down? :sweat_smile:
Especially since we really don't need to cross-compile everything e.g. we definitely don't need to cross-compile plutus-metatheory.

Maybe we should start trying to cross compile a few things and work up, rather than trying everything and working down? 😅
Especially since we really don't need to cross-compile everything e.g. we definitely don't need to cross-compile plutus-metatheory.

@michaelpj I'm not going for all, but having all in there is showing systemic challenges :-)

Lovely, now we have cardano-api in the dependencies of plutus-pab

Closed in favour of #3800


Test with latest and make semver explicit

Updates the version range of OTel to be semver compliant requiring a minimum of 1.14 (metrics stability) and excluding versions 2.0 or above (potentially breaking).
Updates the example project to use 1.20.1 (latest)

@pirgeo so from your comments it seems you think it should be ok to compileOnly with strict [1.14.0, 2.0[? Then in example do implementation?
If I try this the tests fail because there is no implementation. Do I also need to add a separate test implementation declaration?


[Bug]: New menu item titles are misaligned

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When we add new menu items in the Button Group widget, they are not aligned with the rest of the menu items by default.

Steps To Reproduce

D&D a Button Group widget.
In the property pane click on the settings for the More button.
Click on Add a new Menu Item.

Public Sample App
No response
Issue video log
No response
Version
Cloud

@dhruvikn assigning this to you since you fixed it in menu button. Can we close it this sprint? don't want to keep this hanging.


axis nametextstyle overflow truncate not working HELP ASAP

Version
5.0.2
Steps to reproduce
I used this options
option = {
    xAxis: {
        type: 'category',
        data: ['Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat', 'Sun']
    },
    yAxis: {
        show: true,
        name: 'bhemmmmmmmmmmmmmm gfdsmmmmmmmmmmmmmmmmmmmmmmmmmmm',
        type: 'value',
        nameTextStyle: {
            overflow: 'truncate',
            width: 10
        }

    },
    series: [{
        data: [150, 230, 224, 218, 135, 147, 260],
        type: 'line'
    }]
};

What is expected?
I am expecting the axis name to be truncated at a specific width
What is actually happening?
It is not getting truncated, I think the width property is not working

Version
5.0.2
Steps to reproduce
I used this options
option = {
    xAxis: {
        type: 'category',
        data: ['Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat', 'Sun']
    },
    yAxis: {
        show: true,
        name: 'bhemmmmmmmmmmmmmm gfdsmmmmmmmmmmmmmmmmmmmmmmmmmmm',
        type: 'value',
        nameTextStyle: {
            overflow: 'truncate',
            width: 10
        }

    },
    series: [{
        data: [150, 230, 224, 218, 135, 147, 260],
        type: 'line'
    }]
};

What is expected?
I am expecting the axis name to be truncated at a specific width
What is actually happening?
It is not getting truncated, I think the width property is not working

Am facing the same issue. Any solution mate?

The nameTruncate property will do this job, Notice this proprety in /echarts/src/coord/axisDefault.js
option = {
    xAxis: {
        type: 'category',
        data: ['Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat', 'Sun']
    },
    yAxis: {
        show: true,
        name: 'bhemmmmmmmmmmmmmm gfdsmmmmmmmmmmmmmmmmmmmmmmmmmmm',
        type: 'value',
        nameTruncate: {
            maxWidth: 100,
            ellipsis: '...',
        }
    },
    series: [{
        data: [150, 230, 224, 218, 135, 147, 260],
        type: 'line'
    }]
};

thanks

@Jagan-P  & @jackielan66
nameTruncate works for me.
But i wanted to break the name, so it can appear as complete in next line ?
any solution for that.
nameTextStyle: {
overflow: 'break-all' | 'break',
width: 10
}
Not working either

Actually here insists a bug that the overflow didn't work in nameTextStyle,

Actually here insists a bug that the overflow didn't work in nameTextStyle
But here has a way to solve the issue:
name: '{a|Test'+'\n'+'Break}',
nameTextStyle: {
    rich:{
        a:{
            ...
        }
    }
}

same problem，is this a bug?