Inconsistencies in Expr operator code.

Problem
Some operations are implemented both directly on Expr and as built-in traits (here's an example: trait impl compared with type impl).
As far as I can tell, these implementations could (and should) use the same underlying logic (the trait impls should use Expr's). Instead, the logic is duplicated at both sites (as you can see in from the snippets I linked). This increases the potential for bugs as it would be very easy to introduce changes in say in one of Expr's methods and not the corresponding trait impl (or vice-versa).
Another inconsistency is that Expr's methods don't have the same name as the corresponding trait methods, so we end up in a situation where, for example, bitwise_and (type impl), bitand and & (trait impl) all do the same thing. This can cause confusion for users since it's not immediately clear that these are in fact intended to be the same.
Finally, the Not trait implementation is located in the expr module (here), while all other operator trait impls are located in the operator module.
Potential solution
In my opinion, the Expr impl should not duplicate built-in operator trait methods. The duplicated methods should be removed from Expr, and only the trait impls be kept. This is more in line with idiomatic Rust code, removes duplication, and reduces potential user confusion.
Likewise, the Not trait impl should be moved to the operator module and the corresponding type method be removed.
Alternatives
If the duplicated type impls won't be removed, then the trait impls should be derived from the Expr methods to at least remove the duplication in implementation.
Discussion
Please let me know what you think. It's possible that I misunderstood why the code is laid out this way.
If there is in fact a problem, then I'm prepared to make a PR to solve this after we've discussed of the appropriate solution.

In my opinion, the Expr impl should not duplicate built-in operator trait methods. The duplicated methods should be removed from Expr, and only the trait impls be kept. This is more in line with idiomatic Rust code, removes duplication, and reduces potential user confusion.

I agree a single Rust idomatic pattern sounds good to me.
I wonder if it might cause issues for python bindings, or other non rust users -- @andygrove  or @jdye64  do you have any insight?
Thank you for working on cleaning this up 🙏

Likewise, the Not trait impl should be moved to the operator module and the corresponding type method be removed.

I agree

@alamb thanks for checking. @LouisGariepy proposal will not cause any issue on the Python bindings side (however good to know so we can expect and adjust for the change). However I can't speak for other non-rust bindings.


Monitor dbt run results

How to retrieve run timings from .json file

Hi @Akanksha120701 ,
Elementary does not retrive run times from JSON files. It does it from the dbt results Python object.
You can take a look at the dbt package code who is responsible for it:
https://github.com/elementary-data/dbt-data-reliability


[KYUUBI #6097][KYUUBI #6098] Upgrade Flink 1.16.3 and 1.18.1

:mag: Description
Issue References 🔗

This pull request fixes https://github.com/apache/kyuubi/issues/6098, https://github.com/apache/kyuubi/issues/6097
Describe Your Solution 🔧
Upgrade flink from 1.16.2 to 1.16.3 and 1.18.0 to 1.18.1
Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Thanks, merged to master


avro Date format exception

When I switch to loadDataFormat=Avro
I get an error when I have DataFrame with Date column
org.apache.avro.AvroRuntimeException: Unknown datum type java.sql.Date:
thanks,
Aleks

Hello, Alex.
The Avro format does not support the writing of TIMESTAMP and DATE types.
As a result, the SingleStore Spark Connector currently does not support these types with Avro serialization.
https://docs.singlestore.com/v7.1/third-party-integrations/spark-3-connector/#data-type-conversion-remarks

@bolcman is there anything else we could help you with?

@bolcman closing this issue for now - please reopen if you will need some additional help with Avro serialization.


Improvements

After forking this project I have made a few improvements that I think should be in by default, e.g. markdown/HTML responses and better logging. I haven't opened a PR because I don't know if they would be accepted, being a "starter" kit, or if anyone who can merge changes is still active.

I will update the sample not to use simsimi since it is not working anymore. As for other features I don't want to include it, the reason being it a starter kit.

can I still make a PR for better logging? all it does is put the messages on one line so as not to clutter up the log viewer: https://github.com/Walkman100/telebot/commit/4f6697b9d975948ce612f964ae25abd50c3a5f76


make some changes for launch

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

👍 @gsans ? / @benlesh

BEN WHY ARE YOU NOT TAGGABLE

@JAYPHELPS please lint my code.

@ladyleet for reasons unknown, Ben is @blesh on Github, not @benlesh

@blesh 👍 ?

@gsans 👍 💯 ?

@jayphelps ohai

@jayphelps i'm practicing bikeshedding like you taught me.

Overall solid.

@gsans you gerard you want to merge my pr?

merged my own.

REBASE FOR ALL THE REBASE GODS!

Well... I'll leave that to your imagination =)


clean repo

This PR is to clean the repo. This is ongoing work to sanitize the Branches repo.

Only @dmitrisaberi can do this for now.


MINOR: [Archery] Add collaborators to list of roles with access to trigger bot tasks

I've been added as triager but now if I try to trigger crossbow tasks they fail with permissions issues:
https://github.com/apache/arrow/pull/14715#issuecomment-1326243342
Only contributors can submit requests to this bot. Please ask someone from the community for help with getting the first commit in.
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/3539688563

This should fix the issue

I didn't know about the "collaborator" role. This looks good to me. @kou What do you think?

@pitrou for reference: https://github.com/apache/arrow/pull/14719

+1


Default Hyde mobile theming

The default Hyde theme looks fine IMO, however it is not responsive at all to mobile devices. It would be great if the default theme laid the site out better on mobile.
I'm going to be updating it for mobile myself, will send a PR if wanted.

Better mobile support by the default theme, hyde, is certainly welcome. When you send the PR, if you can, attach screenshots of how a site looks before and after the changes

Thanks @juszczakn!


Message Component position

What problem does this feature solve?
When it is necessary to display a Message Component not only on the top of the screen but also in the bottom, on the left or right side.
What does the proposed API look like?
Example
{   ...NZ_MESSAGE_CONFIG,   nzPlacement: 'top' | 'bottom' | 'left' | 'right'  }

@MykhayloBondacrhuk Hi. ng-zorro-antd implements Ant Design. Could you please open a similar feature request there, explaining why it should be supported?

Closed because no implementation or plan seen on Ant Design.


TokenRequest API update

https://harness.atlassian.net/browse/CDS-48575
https://harness.atlassian.net/browse/CDS-56719
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[x ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/CDS-48575
https://harness.atlassian.net/browse/CDS-56719

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Use simple accessor when metadata and data drivers are the same

Coverage decreased (-0.01%) to 82.242% when pulling cd357bff829bd1da37beb03e6189ccfb607135a1 on adericbourg:fix_bg_driver into c0d8ef5335139870af1c3a3334f27571f0a5fd22 on criteo:master.


[NEXT] Adapt to UCAN 0.9

This PR aims to bring the UCAN 0.9 to the SDK. The prototype version of UCAN we currently have is mixed into a lot aspects of the SDK. Because of this I have disabled and removed a lot functionality, such as most importantly, device linking, but more on that later.
Goals of this PR
UCAN
Ideally we'd upgrade directly to UCAN v0.10. But we can't do that just yet (waiting on libs to upgrade), so I opted for 0.9 for now. That said, it should be quite straightforward to upgrade to the next version.
File System
The next branch is already using rs-wnfs primarily, but you can't make an app with it yet. This PR builds further on that and connects various pieces. Most importantly here is the private node mounting system. Which is where you take a private ref to load a private node using rs-wnfs. These secrets need to be passed from device to device in order to gain access to various parts of the private file system.
Linking
The SDK also has this delegation system (auth lobby). We've gradually abstracted this lobby system more and more, and this PR takes another step further. Because device linking and app-to-app linking is so similar, we've decided to merge the APIs and the channel over which the UCANs and secrets are transferred.
I've completed the initial API surface which you can see in various places, but it's not finished just yet. The idea is to do this:
// authority
const program = await odd.program(config, "authority")

program.access.provide()
program.access.on("query", ...)

// delegate
const program = await odd.program(config, "delegate", {
  request: [ odd.access.fileSystem("read", path) ]
})

program.access.request()
program.access.on("challenge", ...)

This'll be implemented using two components: access & channel
Other things to check out: src/access/query.ts
Accounts & Identifiers
The account system and identity layer have been abstracted. We currently have usernames mixed in everywhere, this PR gets rid of that. Also very important, @hugomrdias had the great idea to always delegate from the identifier to the agent, which this PR implements. I'm using the naming "identifier" here instead of "identity" because that's @bmann his preferred naming which I agree with. Humans have multiple identifiers, not identities.
This makes implementing various identifier systems much easier. There will always be a delegation from the identifier to agent, and the agent delegates to the account system. Account and identifier systems can be implemented using their relevant components (account & identifier). The first account system to be implemented will be the new Fission server.
@hugomrdias also made the suggestion to add a login hook. The way I've implemented this, is where the delegation from identifier to delegation happens. You'll be able to do the following:
program.login()

Registering an account has changed a bit because of the abstraction:
// Instead of passing the username directly, this now depends on the component implementation.
// But it'll always be an object you pass in.
const formValues = { username: "example", email: "..." }
const { ok } = await program.canRegister(formValues)
const { ok } = await program.register(formValues)

If either ok is false, there will be reason attached to it so you know why it failed.
Depot
I've added a flush method to the Depot component. This is part of separating the data from the account layer. This should make it possible to for example use Web3Storage as the file system block storage (or in addition to Fission's storage).
The way this works is, you have two components that are called when a mutation is made in the file system (after a short debounce). You have the account system which is responsible for the data root and the depot, which is responsible for the IPLD block storage. Whenever the data root is going to be updated, flush is called. So you could use this to boot up your IPFS node in the browser, setting up a bitswap connection. Or to gather the changed IPLD blocks, package them up in a CAR file and push them to Web3Storage.
Smaller Changes

Replaces user session objects with program.isConnected()
Removed the DID code, uses @hugomrdias his libraries
Removed keystore-idb
Removed DIDs from the Program object, these don't really make sense anymore. Agent DID should never be used anymore by the developer, always use identifier DID. Sharing/exchange DID needs to be rethought, will be implemented later together with private-data sharing.
Removed the crypto component, doesn't make sense anymore to have this as a component. Every JS language supports the web crypto API now anyway. Less references to pass around. Agent keys can still be customised using the agent component.
Reference component has been removed, functionality has been moved to other components or into their own component.
Username availability check is now done through DNS to avoid fetch errors in browser.
Cleans up various unused common code.
Account UCAN is no longer stored separately
Storage locations have changed so it will not cause a conflict with older versions of the SDK
Simplified the debugging config, debug and debugging config params have been merged.
Backwards compatibility with older Webnative clients has been removed

To do
In this PR

[ ] Finish up login behaviour/implementation
[ ] Update comments in index
[ ] Fix tests

In other PRs
Things that are missing, need to re-implemented or still need to be fixed:

Linking (access component implementation)
Extensions
Private data sharing
File system versioning
File system recovery
Predefined components in index.ts file (eg. odd.storage.memory())

Looking the linking API:
// authority
const program = await odd.program(config, "authority")

program.access.provide()
program.access.on("query", ...)

// delegate
const program = await odd.program(config, "delegate", {
  request: [ odd.access.fileSystem("read", path) ]
})

program.access.request()
program.access.on("challenge", ...)

Love how this is coming along, "request... access" reads great to me. ❤
One question here is whether or not this supports a delegate requesting access from another delegate. In the past, @expede has mentioned that we would like to support multiple levels of subdelegation.
Would that work with this API? Does putting the request into the program initialization make it difficult to declare who we are requesting access from?

This makes implementing various identifier systems much easier. There will always be a delegation from the identifier to agent, and the agent delegates to the account system. Account and identifier systems can be implemented using their relevant components (account & identifier). The first account system to be implemented will be the new Fission server.

This hierarchy sounds great for supporting interoperability. 💯

Replaces user session objects with program.isConnected()

Nice! Like the "connected" naming.

Username availability check is now done through DNS to avoid fetch errors in browser.

Is there a risk for race conditions here? Say a user registers a name, and a second user comes along and wants the same name. If we are waiting for DNS to propagate, could the username check fail? This might be alright, as I imagine registration itself would fail.

Backwards compatibility with older Webnative clients has been removed

Yes, bon voyage 👋 . When we have a rough timeline for next, we should announce this in Discord to give folks a heads up.

One question here is whether or not this supports a delegate requesting access from another delegate. In the past, @expede has mentioned that we would like to support multiple levels of subdelegation.

@bgins Yeah good point. I don't know if you saw the recent discussion about that on Discord. But I'd like some well-defined use cases for this, otherwise I don't know really how to shape the API. But maybe we opt to make it generic instead?
I'd like to avoid roping the initialisation into this, but not sure how. With these changes when you run your program in authority mode, you get a register and login function on your program. Because, based on the lobby model, you would only register an account or do device linking in the lobby (the authority), not the "delegate". Then there's also the question of how isConnected() should function, it'll need different functionality based on the mode it's operating in (authority or delegate). Right?
There's something here about specific use cases. We assume there's an "authority" which requires full read & write access to the file system and a "delegate" which could operate with a very small subset of that (eg. only read portion of file system). But is that always the case? 🤷♂
Maybe we could do something like this instead?
const program = await odd.program(config)

// authority
await program.account.register()
await program.account.login()

await program.account.isConnected()
// NOTE: Could check if UCAN has been delegated with full write access and if we can update the data root.
//             Also should potentially check if the configured account system has all the capabilities it needs.

// delegate
await program.access.request({
  from: ...,
  query: [ ... ]
})

await program.access.isGranted(query)

Thoughts?

Is there a risk for race conditions here? Say a user registers a name, and a second user comes along and wants the same name. If we are waiting for DNS to propagate, could the username check fail? This might be alright, as I imagine registration itself would fail.

Blaine is setting up some DNS magic which will make it look up the values in the database directly, so propagation will be faster I assume. That said, I think it'll be fine too, the registration itself would indeed fail.

But I'd like some well-defined use cases for this, otherwise I don't know really how to shape the API. But maybe we opt to make it generic instead?

Yeah, it would be nice to have use cases. Not sure what they are, and I can see how this makes it more challenging to design an API.

I'd like to avoid roping the initialisation into this, but not sure how. With these changes when you run your program in authority mode, you get a register and login function on your program. Because, based on the lobby model, you would only register an account or do device linking in the lobby (the authority), not the "delegate".

I'm agreed that there is a fundamental difference between an authority and a delegate, and I think it's a good design to only expose what one or the other needs.

Then there's also the question of how isConnected() should function, it'll need different functionality based on the mode it's operating in (authority or delegate). Right?

Are there cases where a delegate could start with a local-only file system that later gets merged into a file system granted by an authority? If so, I think isConnected() works for both. I think this works for offline use cases, where a delegate app may want to store some data then later request access to persist and sync it.
The way these would function differently is the method of requesting authority. The authority gets it by registering an account, and the delegate gets it from the authority.

const program = await odd.program(config)

// authority
await program.account.register()
await program.account.login()

await program.account.isConnected()
// NOTE: Could check if UCAN has been delegated with full write access and if we can update the data root.
//             Also should potentially check if the configured account system has all the capabilities it needs.

// delegate
await program.access.request({
  from: ...,
  query: [ ... ]
})

await program.access.isGranted(query)

Yes, I think this has potential. It would make the request for access more flexible. It might be possible to retain the distinction between authority and delegate? An authority will never need to request access, and a delegate won't need to register or login.

I was discussing a use cases for multiple levels of subdelegation with @QuinnWilton today, and I think we have a good example.
Suppose we have the following apps:

An auth lobby (an authority)
Diffuse, a music player (a delegate)
Notify, another music player (a delegate)
MetaFixer, an app that applies metadata to music files (a delegate)

Diffuse and Notify request access from the auth lobby to access public/music and public/notify, respectively. These are the directories where they store music.
MetaFixer is a secondary app that is accessible from Diffuse and Notify. It doesn't do much on its own, but on requesting access from Diffuse or Notify, it will look up metadata and store it with your music.
Diffuse and Notify have a button that starts linking directly with MetaFixer, subdelegating access to the music directories they have access to.
Alternatively, the user could be redirected to the MetaFixer where they request permission from the auth lobby. The disadvantage to this approach is the user loses context when they request access from the auth lobby.
Also, MetaFixer could request access to directories that it doesn't need. The user may not be aware that MetaFixer is asking for more, whereas requesting from Diffuse or Notify guarantees MetaFixer can only request what it needs.
Note also that MetaFixer will get access on an as needed basis. A user can start by applying metadata to music in public/music for Diffuse without access to public/notify. Later, they can request access through Notify for public/notify. In each case, they retain context for the access they are granting.

👋 I just read through this thread too, and I have one more thought on a possible use-case for sub-delegation:

We assume there's an "authority" which requires full read & write access to the file system and a "delegate" which could operate with a very small subset of that (eg. only read portion of file system). But is that always the case? 🤷♂

I actually don't think this is necessarily always the case, even if in the current world it is! Baked into this sentence is the assumption that WNFS is the only service for which an authority may delegate access to, but there's a possible future where apps built using OddSDK may integrate with other UCAN enabled services too, for things like message buses, email, or SMS.
If these services are third-party, then the Fission auth lobby isn't likely to serve as an authority for all of them, and so some applications may require delegations from multiple different authorities. This means that it actually becomes possible for individual applications to hold more capabilities than any individual authority, and so the ability to sub-delegate from that rights-amplified application reduces the friction involved in sharing those capabilities with other applications.
In practice, this might show up as something like a Heroku or AWS style dashboard that accumulates capabilities from disparate, possibly third-party services, and can then further attenuate those capabilities to other applications.
Anyway, this is just me spitballing about another instance where sub-delegation shows up, and I understand that this isn't how things work today, so this isn't me suggesting that it's a use-case to be targeted by you in this refactor.

I was discussing a use cases for multiple levels of subdelegation with @QuinnWilton today, and I think we have a good example.

Thanks you two! And for picking an example I can relate to ❤ Sounds like a great use case.

This means that it actually becomes possible for individual applications to hold more capabilities than any individual authority, and so the ability to sub-delegate from that rights-amplified application reduces the friction involved in sharing those capabilities with other applications.

Makes sense yeah. I'm actually getting very close to this, so I'll start working in that direction for the API 👍

Removed DIDs from the Program object, these don't really make sense anymore. Agent DID should never be used anymore by the developer, always use identifier DID.

I think this information could still be useful to developers for understanding authorization flows. They may want to log the agent DID to track which agent they are working in, and we might want to show this information in the browser extension. We will eventually extend the browser extension to display UCANs, so this information will be good context for that as well.

File system is not loaded automatically anymore.

Yep, agreed it will be better to require developers to handle this explicitly. 👌

@bgins Added back the DID shorthand methods, except for the sharing one, because that still needs to be figured out.


Https bump (#3637)

Docker build change to bump to https

Dependency changes

Fixing urls

(cherry picked from commit 6bd490fec13fa690ab9ce1d36bfa8793ae82dadb)

What does this PR (Pull Request) do?

Cherry picking https bump.

[x] This PR is not related to any Issue

Which Traffic Control components are affected by this PR?

CDN in a Box
Traffic Monitor
Traffic Ops
Traffic Portal
Traffic Router
Traffic Stats

What is the best way to verify this PR?

If this is a bug fix, what versions of Traffic Ops are affected?

The following criteria are ALL met by this PR

[ ] This PR includes tests OR I have explained why tests are unnecessary
[ ] This PR includes documentation OR I have explained why documentation is unnecessary
[ ] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[ ] This PR includes any and all required license headers
[ ] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[ ] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Can one of the admins verify this patch?

add to whitelist


[Bug | Crash] Ender IO Teleporter GUI causes crash when interacting with it.

Hi @tterrag1098 & Other EIO Devs
Found a bug/crash with the new telepad UI.
Minecraft 1,7,10
Forge <IP_ADDRESS>8
EnderCore <IP_ADDRESS>_beta
Ender IO <IP_ADDRESS>2_beta
Crash report: http://paste.ee/p/coMj0
Steps to repeat...

Create the telepad multiblock (3x3x1)
Open it's UI
Crash and burn!
Eat cookies?

Fixed via SleepyTrousers/EnderIO/28d0627cf7118b392b3deeb4289f9f3c236ce8ba


Update local storage docs with 1.9 status and statefulset examples

Updated:

feature summary as of 1.9
1.9 steps for setting the feature gates and scheduler predicates
gce/gke config files
statefulset examples using pod affinity and pod anti-affinity

Fixes #464

/assign @saad-ali, @jsafrane, @ianchakeres, @dhirajh

/area local-volume

/assign @jsafrane, @ianchakeres, @dhirajh

Updated

/lgtm


Add bundles 1.5.0 and 2.4.0. Removed 1.4.0 and 2.3.0

Updating bundle versions
Versions added

1.5.0
2.4.0

Versions removed

1.4.0
2.3.0

PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] If applicable, the PR references the bug/issue that it fixes in the description.
[ ] New Unit tests were added for the changes made and CI is passing.

/azp run

@yojagad - Please revert the change from 2.0-upgrade images.

@divyagandhii Reverted the upgrade images.

pinging for reviews/approvals, please. Is there anything else that needs to be updated ?


How to pass in config to sails.io.js so socket.io connects to another port?

I have a client and server running on different ports:

client: 8080
server: 1337

This leads to an expected 404 on : http://localhost:8080/socket.io/1/?__sails_io_sdk_version=0.10.0&__sails_io_sdk_platform=browser&__sails_io_sdk_language=javascript&t=1401903892072
Instead I want to configure sails.io.js so that  socket.io connects to localhost:1337 instead.
How to do this?
The logical solution would be to pass a custom io parameter to SailsIOClient(io) but on line 817 of sails.io.js SailsIOClient is called without the option to pass in a custom io. See the below snippet:
  // Otherwise, try to instantiate the client:
  // In case you're wrapping the socket.io client to prevent pollution of the
  // global namespace, you can replace the global `io` with your own `io` here:
  return SailsIOClient();

Now the comments seem to refer to the thing I want to do (pass in my own io) but, again, it's unclear to me how exactly to do this.
Anyone?

This worked for me:  In sails.io.js, in the "io.sails" section, I added a "url: ..."
io.sails = {
   url: "http://<address>:1337",  // or localhost
.
.
.

In the version of sails I use, this is at around line 1350
This still doesn't feel quite right to have to modify this file.
Can anyone recommend something better?


Proper way to provide libfswatch on Ubuntu 20.04

After shards install, when trying to compile the Crystal code example provided on README, with:
crystal build src/liven.cr --release --no-debug

I'm getting the following error:
/usr/bin/ld: cannot find -lfswatch (this usually means you need to install the development package for libfswatch)
collect2: error: ld returned 1 exit status
Error: execution of command failed with code: 1: `cc "${@}" -o /home/coghi/projects/liven/liven  -rdynamic -L/usr/bin/../lib/crystal -lfswatch -lz `command -v pkg-config > /dev/null && pkg-config --libs --silence-errors libssl || printf %s '-lssl -lcrypto'` `command -v pkg-config > /dev/null && pkg-config --libs --silence-errors libcrypto || printf %s '-lcrypto'` -lpcre -lm -lgc -lpthread -levent -lrt -ldl`

I'm on Ubuntu 20.04 and libfswatch-dev is not provided anymore (was provided up to 18.04), so the only package I was able to install was fswatch. But after installing it, the same error still occurs when trying to compile.
It seems that if I compile fswatch from source the problem will be solved, but I would like to provide Crystal libraries that use crystal-fswatch with no manual compilation needed from the user side.
Do you know if the libfswatch changed its name from Ubuntu version 20.04 onwards?

The shard.yml is:
name: liven
version: 0.1.0

authors:
  - Paulo Coghi<EMAIL_ADDRESS>
dependencies:
  live_reload:
    github: bcardiff/live_reload.cr
  fswatch:
    github: bcardiff/crystal-fswatch

crystal: ">= 1.3.0"

license: MIT

Looking on the details of fswatch package on Ubuntu 20.04, we can see it provides a shared library on
/usr/lib/x86_64-linux-gnu/libfswatch/libfswatch.so.11.0.1

But it doesn't seem to be found

Great. Things are a bit messy it seems.

libfswatch-dev package was merged into fswatch package in some of the recent distros. As you mention, the https://packages.ubuntu.com/impish/amd64/fswatch/filelist includes the library.
Crystal relies on pkg-config to find libraries. For that to work there should be a .pc file in a location known by pkg-config or at least include the location of the .pc file in the PKG_CONFIG_PATH.
Unfortunately the fswatch package does not include such .pc file. See for example the contents of libgc-dev for a package that includes it.
fswatch source code has all the needed pieces to create a .pc file, but a) that does not guarantees the linux packages will include that file. b) this was introduced in 1.15 ref

So, how we can make things work in ubuntu impish for example.

Install the fswatch package
Create a fswatch.pc file with the following content, this files could be in the working directory of your project.

Name: libfswatch
Description:
Version:
Libs: -L/usr/lib/x86_64-linux-gnu/libfswatch -lfswatch

Put location of fswatch.pc in the PKG_CONFIG_PATH variable, assuming the .pc file is in your working directory that would be:export PKG_CONFIG_PATH=/path/to/project. With this you should be able to compile your app that depends on this shard.

But your app will not run probably. The libfswatch.so is a shared library in a non default location. If your does not run with a message complaining that libfswatch was not found that means that LD_LIBRARY_PATH needs to be tweaked.
See how libfswatch is found by ldd after LD_LIBRARY_PATH is set.
$ ldd your_compiled_app
        linux-vdso.so.1 (0x00007ffcf2bdf000)
        libfswatch.so.11 => not found
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fa2ddd08000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa2ddc24000)
        libevent-2.1.so.7 => /lib/x86_64-linux-gnu/libevent-2.1.so.7 (0x00007fa2ddbce000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa2ddbb4000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa2dd98c000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fa2ddfd0000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa2dd985000)

$ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/libfswatch

$ ldd 01_monitor_curdir
        linux-vdso.so.1 (0x00007fff3eb0c000)
        libfswatch.so.11 => /usr/lib/x86_64-linux-gnu/libfswatch/libfswatch.so.11 (0x00007f80465f8000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f804657f000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f804649b000)
        libevent-2.1.so.7 => /lib/x86_64-linux-gnu/libevent-2.1.so.7 (0x00007f8046445000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f804642b000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8046203000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f8046891000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f80461fc000)
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f8045fe3000)

libfswatch seems to not have many users. People uses the app directly it seems.
Using libraries with the state of the art distribution has it's hiccups unfortunately.
Some other considerations:

when distributing your app as linux packages you can choose to link some libraries statically. This will simplify distribution and you can use newer versions if needed
if shared libraries are used dealing with .pc files is only needed for building the app, users would suffer less probably
I mostly used this in osx, and attempt to make it work on linux
If you target only linux give https://github.com/petoem/inotify.cr a try, since that does not requires libraries.

For additional help on how to deal with libraries in general use the forum were more wise people will probably collaborate.

Thank you a lot, Brian!


Add FineTune DTO docstrings

Note that after @squeakymouse finishes renaming the server DTOs, we'll want to merge things (as in, docstrings from these client DTOs, etc.)

Considering this as a supplement to https://app.shortcut.com/scaleai/story/782418/documentation-for-fine-tuning-should-contain-examples-for-all-sections
See #45


:point_right: Use common CI scripts

There are 2 related PR's required to make the common CI scripts work with the connecting to services CI build.
https://github.com/nhsuk/nhsuk-rancher-templates/pull/14
https://github.com/nhsuk/ci-deployment/pull/4
There are some hacks used to allow testing.

The submodule used by this PR is pointing at the ci-deployment feature branch feature/remove-profile-specificity (instead of master)
The rancher_pr_deploy.sh script is pulling the docker-compose.yml & rancher-compose.yml files from the feature/changes-for-ci-script branch (instead of master) of the nhsuk/nhsuk-rancher-templates repo

If the changes proposed are OK then these hacks will have to be removed once the changes for each PR have been merged.
There are lots of improvements we can make to the scripts but at this point in time it works.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling d0d0f3a60286571177da01f594acacaedceb1325 on feature/use-common-ci-scripts into 50fe14ba93e43923b62b50a5f1f3a9efb5787477 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 77c2f712fc481501903865e457beac1208807e3e on feature/use-common-ci-scripts into 50fe14ba93e43923b62b50a5f1f3a9efb5787477 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 398ae8d10e1c26d653c3fff41ab6ab0fc3d6f8c0 on feature/use-common-ci-scripts into 50fe14ba93e43923b62b50a5f1f3a9efb5787477 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 8d490cdfea54c9b7ea88e0ee4521c5bcbcdac038 on feature/use-common-ci-scripts into 50fe14ba93e43923b62b50a5f1f3a9efb5787477 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 5f05fc13a2a0c189d77b170ee7a8b305625ad873 on feature/use-common-ci-scripts into 50fe14ba93e43923b62b50a5f1f3a9efb5787477 on master.

Adding WIP label until PR nhsuk/nhsuk-rancher-templates#14 is complete.
See https://github.com/nhsuk/nhsuk-rancher-templates/pull/14#issuecomment-279985585 for additional info

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 03b7dfacf6dd36948ed962ddd6fc58a0f6cd1aa9 on feature/use-common-ci-scripts into 14098c01b98856a43e707301ef861fe7026a2615 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 03b7dfacf6dd36948ed962ddd6fc58a0f6cd1aa9 on feature/use-common-ci-scripts into 14098c01b98856a43e707301ef861fe7026a2615 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling cdd1fed06ae2cdd0420d428ab160b2df2de336ae on feature/use-common-ci-scripts into 14098c01b98856a43e707301ef861fe7026a2615 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 1e1013e952495eecb9117c923f126254b6076f88 on feature/use-common-ci-scripts into 14098c01b98856a43e707301ef861fe7026a2615 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 07729c288e140ec2074c584a3f984c5bd4743438 on feature/use-common-ci-scripts into 14098c01b98856a43e707301ef861fe7026a2615 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling f60fbc006491ba2c57dbbd717c924d03e18590a8 on feature/use-common-ci-scripts into 14098c01b98856a43e707301ef861fe7026a2615 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 9ae5e1e7538c811c365040b16023106ab588465a on feature/use-common-ci-scripts into 14098c01b98856a43e707301ef861fe7026a2615 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

Coverage remained the same at 98.897% when pulling 969a442f7acb4fdb3601faa2937e9991ac151c93 on feature/use-common-ci-scripts into 14098c01b98856a43e707301ef861fe7026a2615 on master.

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

test

test

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:rocket: deployed to http://connecting-to-services-pr-260.dev.c2s.nhschoices.net

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:warning: deployment of 260 for nhsuk/connecting-to-services failed

:warning: deployment of 260 for nhsuk/connecting-to-services failed

Awaiting merge of work in #267 to fix snyk vulnerability

The Snyk failure gives us an interesting situation. PR #267 won't have a successful build till these changes are included. And this PR wont successfully run all checks until #267 has been merged.
Perhaps these should be merged?

Based on the comment above, I've combined the changes from PR #267 and this one to get to a point where everything that needs to be done to get a passing build is in once place. that place being PR #269
If that works it will supersede this one and this can be closed.

PR #269 is looking pretty good from the POV of the build checks being successful and the deployment happening. Closing this.


Scroll Wheel event listener goes off from scroll box position.

I constructed a scrollBox with boxWidth and boxHeight I wanted. Then I gather the items that I want to show in the scroll box in a PIXI.Container and add into scrollBox.content. Everything works fine, but the scroll wheel listener not follow scrollBox position and goes off.
I tried to .resize() and .update() the scrollBox again after added in items containers, but not work either.
Can someone help me with this?
Thanks.

How are you moving the scrollbox?

I tried two way. First is normal way scrollbox[ .x & .y ] equal to number. Second is scrollbox.position.set().

I'm aslo getting this issue on mouse wheel.


Too much files need to download to start playing

When you connect to the server first time you will download around 53 Mb and this size only will raise and it could easily raise to 100 Mb in future which is a problem.

I think it could be done as download first 5 - 10 mb then play whilst you are downloading rest of the stuff that is needed but it might not work thou depending on scripts and stuff that are in use

I dont see why it would raise any further. Most of it can be streamed in later i guess. The scripts itself arent big.

It will raise because we upload more and more horns

Oh right, i forgot about that. Still we could stream horns, or let them download after joining.

That and race_fix are about the biggest files on the server right?

https://github.com/JarnoVgr/Mr.Green-MTA-Resources/commit/7357d916c1f13ab538971c36d7b4aa0d116ececd Thats 13mb less download when joining, we can reduce it more.

Very nice! It works :)


CSS: fix menu layout on older mobile devices

The current flexbox styling (wrap specifically) doesn't work 100% as intended on older versions of Safari on iOS (see screenshot below). This minor update defines the nav element to properly render under the title.
Issue (left), Fixed (right)

Thank you! I don't have an iPhone to test on.
Maybe I'll reduce a bit the font-size for smaller screens too.

No problem!
Personally I think the font size you have currently is great :smiley:


Allow support for Python 3.12

Python 3.12 was released on 2023-10-02, and this extension should work in the new version without any code changes. The configuration for the project, however, doesn't allow it to be installed on Python 3.12, but this fixes that.
Note: This doesn't remove support for Python 3.7 even though that has reached end-of-life. Let me know if you'd like me to remove support for that here as well.

The CI run at least shows frozenlist needs to be updated - which requires dropping Python 3.7 support, otherwise, Poetry won't select the latest version of the package because they have dropped 3.7 support. I, by the way, noticed b1e949a84cc4fa4d5a49a0d579650a9095c96871, so I guess dropping support for Python 3.7 is okay since it's not being tested anyway.
yarl also needs to be updated. https://github.com/aio-libs/yarl/pull/881 has been merged to add support for Python 3.12 but there's no release with those changes yet, so I guess this probably will have to wait until they have made a new release.

@Tenzer, we can drop 3.7 support. It was already removed from the Thumbor main project.
Thanks for the contribution.

@Tenzer , I'm removing Python 3.7 on #153

I got a bit further with this now but hit a couple of other roadblocks:

Scipy needs to be updated to at least version 1.11.2 for wheels to be available for Python 3.12 (release). It has, however, already dropped support for Python 3.8, meaning we also need to drop Python 3.8 support, otherwise, Poetry won't allow Scipy 1.11.2 to be installed.
aiohttp is a dependency of aiobotocore. They do have Python 3.12 support but it's only available as a prerelease in version 3.9.0b0. They are working on getting that released properly, tracked in https://github.com/aio-libs/aiohttp/issues/7675.

I have rebased the changes and dropped Python 3.8 support in order to get the updated Scipy that works with Python 3.12. Tests are successful for me now.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.545%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
314

Relevant Lines:
343

💛  - Coveralls

Good idea. I have kept the version range the same for Python 3.8 support for now, but we can bump that if you want. Python 3.9+ are using the version of NumPy and SciPy that has 3.12 support.

Thanks for the contribution @Tenzer

You're welcome!


Default installation location is missing in Getting Started section for linux

Description:
In Getting started [1], under the section "Installing on Linux" does not include the default installation location (i.e. /opt/ballerina)
But for other  OS types default location is mentioned. Also in the section "Uninstalling Ballerina", the default location is given as /usr/local/ballerina for linux.
[1] https://ballerina.io/learn/getting-started/

Resolved via https://github.com/ballerina-platform/ballerina-www/pull/1059


Installation with install.sh freezes

Issue Description
I experience an issue when I start the install.sh script. At first it seems to work fine but then always freezes when synchronizing pipenv, I reproduced the error multiple times on different virtual machines
Reproduction Steps

Start install.sh
just wait

Environment Details

Ubuntu 19.04 VM (Virtual Box), Kali 2018 VM (Virtual Box)
King Phisher Version: 13
Error Details / Stack Trace
obviously no error Detail, but this is the last information in the terminal window before the installation freezes:
"INFO: Synchronizing King Phisher's pipenv environment"

How long are you waiting? There's a lot of data for it to pull down so depending on your network connection, it could take up to 20 minutes.

I am aware of that, but I waited for more than 3 hours one time and it
always freezes exactly at this point.
Spencer McIntyre<EMAIL_ADDRESS>schrieb am Di., 7. Mai 2019,
18:40:

How long are you waiting? There's a lot of data for it to pull down so
depending on your network connection, it could take up to 20 minutes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/securestate/king-phisher/issues/370#issuecomment-490157396,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJFJAO4SFIOIVBVD43YO3PTPUGWJTANCNFSM4HLKIPIQ
.

@wolfthefallen what's the recommendation here? Run pipenv manually to get more details? Are we aware of any issues in regards to Ubuntu 19.04 and the install script?

This looks related to #357 only with Ubuntu 19.04 instead of 18.04.

are you running behind a proxy?

@wolfthefallen no, but the install script eventually worked after a lot of trials. It only took around 10 minutes and didnt freeze at all. Thanks for the help and the good work.

Weird, thanks for letting us know though and closing out the issue.


Fish completion doesn't silence warnings

In fish, when typing tldr t<Tab>, I get additional output printed to stderr:
tldr tThe cache hasn't been updated for 34 days.
 The zsh script avoids this by redirecting 2>/dev/null, the bash one either has the same problem or bash completions automatically silence this, I haven't checked. I suppose 2>/dev/null is okay, but I would expect --quiet to suffice for this and prefer using that instead.

I can confirm this is a problem with the bash completion as well:
$ source completion/bash_tealdeer
$ touch -d '31 days ago' ~/.cache/tealdeer/tldr-pages
$ tldr tThe cache hasn't been updated for 31 days.
You should probably run `tldr --update` soon.

FWIW, -q doesn't suppress the "Cache not found. Please run tldr --update." message.


feat: Biometry options

Acceptance Criteria

Enable fingerprint and face id biometry options

Security Checklist

[ ] Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

Tests in iOS devices:
iPhone 7 with touch ID:
https://user-images.githubusercontent.com/3298774/168912206-06ef9cd1-7f9f-4898-b55e-d7c138b5bc57.MP4
iPhone 13 mini with face ID:
https://user-images.githubusercontent.com/3298774/168912168-2842be10-1198-4559-b8b1-d286ad12a4de.MP4

Android (Moto G9 Plus)
https://user-images.githubusercontent.com/15909384/168935322-37ec401d-bc02-41fd-9b6d-856c249b94f4.mp4


Rails 3.1 Deprecation warning

Hi,
When I do :
acts_as_geocodable :address => {:street => :street_1, :locality => :city}
I get :
DEPRECATION WARNING: class_inheritable_attribute is deprecated, please use class_attribute method instead. Notice their behavior are slightly different, so refer to class_attribute documentation first.
With Rails 3.1.rc8 and ruby 1.9.2

v2.0.3 is out with this update.


Error log content not useful / extension update download

Issue Type: Bug
At times, extension (update) download fails, and it fails with an error message which lacks any clarity why it fails:
[2021-11-24 09:56:28.792] [renderer2] [error] XHR failed: Error: XHR failed
    at XMLHttpRequest.b.onerror (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:21:24141)
[2021-11-24 09:56:48.436] [renderer2] [error] XHR failed: Error: XHR failed
    at XMLHttpRequest.b.onerror (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:21:24141)
[2021-11-24 09:56:50.258] [renderer2] [error] ["Error: XHR failed","    at XMLHttpRequest.b.onerror (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:21:24141)"]
[2021-11-24 09:56:50.323] [renderer2] [error] XHR failed: Error: XHR failed
    at XMLHttpRequest.b.onerror (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:21:24141)

Right now, I am sitting in a very peculiar networking environment where Visual Studio Code emits the above error, and I'd like to discover what exactly failed.
I'd then (probably) be enabled to get that peculiar networking environment fixed.
Alas, the above error log content is not suitable for diagnostics; there is no specific data, no pointing to additional log files, nothing. It just says "network no good" (sort of), which can be anything.
FWIW, I do know that this is a network environment problem, because this is Visual Studio Code running inside a virtual machine; when the VM host is connected to different network environments, all is good. Personally, I suspect some kind of DNS or IPv6 configuration problem on the network environment, but with Visual Studio Code not telling me what it is doing...
VS Code version: Code 1.62.3 (ccbaa2d27e38e5afa3e5c21c1c7bef4657064247, 2021-11-17T08:00:36.721Z)
OS version: Linux x64 5.14.18-200.fc34.x86_64
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2904)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 0

Memory (System)
31.31GB (26.38GB free)

Process Argv
--unity-launch --crash-reporter-id 80e0ae97-0bc4-4a76-8337-f435f2ec1554

Screen Reader
no

VM
100%

DESKTOP_SESSION
/usr/share/xsessions/plasmax11

XDG_CURRENT_DESKTOP
KDE

XDG_SESSION_DESKTOP
KDE

XDG_SESSION_TYPE
x11

Extensions (15)

Extension
Author (truncated)
Version

path-intellisense
chr
2.5.0

xml
Dot
2.5.1

gitlens
eam
11.7.0

rest-client
hum
0.24.5

Ionide-fsharp
Ion
5.10.1

vscode-docker
ms-
1.18.0

csharp
ms-
1.23.16

vscode-dotnet-pack
ms-
1.0.4

remote-containers
ms-
0.205.2

remote-ssh
ms-
0.66.1

remote-ssh-edit
ms-
0.66.1

remote-wsl
ms-
0.58.5

vscode-remote-extensionpack
ms-
0.21.0

vscode-xml
red
0.18.1

vscode-yaml
red
1.2.0

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
dockerwalkthru:30377721
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsqsis300:30402085
vsaa593:30376534
vssld246:30401890
vscexrecpromptt1:30404947
vscop804cf:30404767
vs360:30404995

Logs are showing whatever network stack (request) is providing. @deepak1556 is it possible to get more information?
@shoffmeister You can also diagnose network requests as follows:

Open Shared process using the command from command pallette Developer: Toggle Shared Process
Go to network/console tab and see the failing requests

@shoffmeister if you can launch with --log-net-log=<path>/netlog.json where <path> some absolute path on your system. Once the network issue happens, you can quit the application and view the log file from the above path under https://netlog-viewer.appspot.com/#import for additional information on what failed in the network stack.


"Thousands" grouping broken

Hi! Great job porting this to JavaScript. It's a lot more convenient than the standard format function.
Anyway, it looks like the regexp for grouping thousands on line 186 isn't quite right. For example,
> var strs = [1, 12, 123, 1234, 12345, 123456, 1234567, 12345678,
              123456789,<PHONE_NUMBER>].map(function(n) { return ''+n; });
> var re = /(?=\d(?:\d{3})+$)/g;
> strs.map(function(s){return s.replace(re, ',');});
[ '1',
  '12',
  '123',
  ',1234',
  '1,2345',
  '12,3456',
  ',123,4567',
  '1,234,5678',
  '12,345,6789',
  ',123,456,7890' ]

I think you want this: /(?=(?!^)(?:\d{3})+$)/g:
> var strs = [1, 12, 123, 1234, 12345, 123456, 1234567, 12345678,
              123456789,<PHONE_NUMBER>].map(function(n) { return ''+n; });
> var re = /(?=(?!^)(?:\d{3})+$)/g;
> strs.map(function(s){return s.replace(re, ',');});
[ '1',
  '12',
  '123',
  '1,234',
  '12,345',
  '123,456',
  '1,234,567',
  '12,345,678',
  '123,456,789',
  '1,234,567,890' ]

I'll submit a pull request. I just wanted to open an issue to give it some context.

Fixed by #3.


Expose write_with method for Node.js binding

Currently, the write_with method doesn't get properly exposed in Node.js binding.

@Xuanwo I want to do this

@Xuanwo I want to do this

Thanks a lot, have fun!

Happy to see it was resolved. When can we get this feature released?

Happy to see it was resolved. When can we get this feature released?

I plan to have a release in next week.


Handle tagging with different prefix during charm publish

When publishing the charms to latest/edge, tag the repo with multiple tags, one for each charm revision.

@bschimke95 I think this fixes what you spotted last week on merges to publishes to charmhub.


Formula not working into dynamically added row?

How can I use formula of previous row into dynamically added row ?
If I have three row in my table, In last column is for total  and I am adding new row by press of enter key then How can i add sum formula for 4th row ?

You can drop one email to<EMAIL_ADDRESS>asking assistance on this one.

https://jsfiddle.net/paulhodel/36f1p2nz/


Using local data with tree grid generates propTypes warning

When using the demo grid code the following PropTypes error is generated when trying to use the tree with local data.
Warning: Failed prop type: Invalid prop dataof typeobjectsupplied toGrid, expected an array.
Here's the provider.jsx setup I used to run the demo code:
import React from 'react';
import { Provider } from 'react-redux';
import { Grid, Store, applyGridConfig } from '../src';

import {
    columns,
    data,
    pageSize,
    plugins,
    events,
    dataSource,
    treeDataSource,
    stateful,
    height,
    stateKey,
    treeData,
    examplePromiseDataSource
} from '../demo/demoData';

const config = {
    columns,
    //data,
     data: treeData,
    // dataSource: treeDataSource,
    // infinite: true,
    stateful: false,
    //dataSource: examplePromiseDataSource,
    // dragAndDrop: true,
     gridType: 'tree',
    pageSize,
    plugins,
    events,
    stateKey
};

export default (
    <Provider store={ Store }>
        <Grid { ...config } />
    </Provider>
);

I suspect this is caused by the following in the Grid.jsx component:
        data: arrayOf(object),

Yeah we should fix this


MongoDB Atlas Vector Store Support

Holding off squashing/documentation further until I get some eyes on it.
This implements a VectorStore on MongoDB Atlas. This does NOT work with MongoDB hosted outside of Atlas as using vector search requires creating a search index through Atlas.
More on how that works under the hood here: https://www.mongodb.com/docs/atlas/atlas-search/atlas-search-overview/
As for configuration, I figured we could provide some defaults, but ideally allow users to set the following themselves as much of it is reliant on whatever they have setup in Atlas.
path: The field you are using for your index in the Atlas Vector Search Index
vector_index: The name of the vector search index
vector_collection_name : The name of the collection your index was created on
num_candidates : Number of nearest neighbors to use during the search. Value must be less than or equal to (<=) 10000. You can't specify a number less than the number of documents to return (limit).
metadataFieldsToFilter: The metadata fields you want to be able to filter with.

We query the database using an aggregation search and preform a post-filter in the pipeline to filter out anything below the threshold value.
https://www.mongodb.com/docs/atlas/atlas-vector-search/vector-search-stage/#mongodb-pipeline-pipe.-vectorSearch
One thing I have noticed (and why I have a terrible sleep(5000) in the test for now....) is that the indexing does not happen instantly.

This is great! thanks for contributing @Kirbstomper !

Added some more documentation and a builder.
I'm thinking of renaming the module to mongodb-atlas-vector-store to make it more obvious that this is not just for run of the mill mongo db, it will also differentiate it from if we ever create a VectorStore for something like Azure Cosmo DB for Mongo as that has some vector storage support too.

To be consistent with the other store names you should use the spring-ai- prefix. E.g. vector-stores/spring-ai-mongodb-atlas.
I've noticed that MongoDB Atlas provides  filtering support.  Perhaps we can map our metadata filtering to it.
We have done it for most of the other stores. If you have time (and interest) you can investigate this. But it is not critical. We can leave it of later improvements.
I'm busy with other stuff until our 0.8.1 milestone release (coming week). But will try to review your contribution for next milestone (1.0.0-M1).

@tzolov
Implemented filtering, and creation of the search index if it doesn't exist. The search index will be created using the configured collection name, metadataFieldsToFilter, pathName, and vectorIndexName. If the search index does exist, then from what I can tell the operation just doesn't do anything.
Ideally I want to be able to check if this search index already exist and then update the index instead, but the updateSearchIndex operation doesn't seem to work very well with vector search index definitions.

Hey @Kirbstomper , thanks for your contribution. Good stuff.
I've reviewed and made some small fixes before merging it.
Here are the left overs if you are interested to continue with them.

https://github.com/spring-projects/spring-ai/issues/455
https://github.com/spring-projects/spring-ai/issues/456

Rebased, squashed and merged at 5f0123cc9228b1befff8bbf5fd76411f7683c14e
Follow up actions:
https://github.com/spring-projects/spring-ai/issues/455
https://github.com/spring-projects/spring-ai/issues/456


Which software did you use to create the "flow" schema ?

Like this one

@lynndylanhurley any help ?

looks like OmniGraffle

Also, you can use Gliffy

Good recommendations. Closing this!


Implement deno compile and/or deno pack once they become available

See issues:

https://github.com/denoland/deno/issues/16632
https://github.com/denoland/deno/issues/15960

Using deno pack we should be able to speed up by bundling and converting to JS. But the real improvement would be with deno compile allowing us to drop the deno installation requirement and also being faster because its just an executable.

Moved away from deno because running it unbundled and uncompiled was slow, node is ~3x faster because it can create a bundle.


Argo UI cronworkflow not running

Checklist:

[y] I've included the version.
[y] I've included reproduction steps.
[y] I've included the workflow YAML.
[n] I've included the logs.

What happened: I am trying to submit a cron workflow that has nesting dag but it does not work on the UI.
What you expected to happen: cron workflow should run, as this same workflow run on normal workflow (using workflowspec definition)
How to reproduce it (as minimally and precisely as possible): run the attached yaml to cron workflow in Argo UI
Anything else we need to know?:
Environment:

Argo version:

2.6.1

Kubernetes version :

$ kubectl version -o yaml

Other debugging information (if applicable):

workflow result:

argo get <workflowname>

executor logs:

kubectl logs <failedpodname> -c init
kubectl logs <failedpodname> -c wait

workflow-controller logs:

kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)

Logs
argo get <workflowname>
kubectl logs <failedpodname> -c init
kubectl logs <failedpodname> -c wait
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)

Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
argoworkflowcron2dagsEcho.zip

I saw the issue on my end, I will close. thanks


PIP INSTALLATION STILL FAIL

Hey dear contributors,
the pip installation still fails to install ctcdecode on windows.
I've tried to do:
git clone --recursive https://github.com/parlance/ctcdecode.git
cd ctcdecode && pip install .
but nothing seems to work.
This is the error being raiced while trying to install the module:
Building wheels for collected packages: ctcdecode
  Building wheel for ctcdecode (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: 'C:\Users\supre\anaconda3\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\supre\\AppData\\Local\\Temp\\pip-req-build-qj51rq8f\\setup.py'"'"'; __file__='"'"'C:\\Users\\supre\\AppData\\Local\\Temp\\pip-req-build-qj51rq8f\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d 'C:\Users\supre\AppData\Local\Temp\pip-wheel-sr3gd52g'
       cwd: C:\Users\supre\AppData\Local\Temp\pip-req-build-qj51rq8f\
  Complete output (20 lines):
  No CUDA runtime is found, using CUDA_HOME='C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0'
  C:\Users\supre\anaconda3\lib\distutils\extension.py:131: UserWarning: Unknown Extension options: 'package', 'with_cuda'
    warnings.warn(msg)
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build\lib.win-amd64-3.8
  creating build\lib.win-amd64-3.8\ctcdecode
  copying ctcdecode\__init__.py -> build\lib.win-amd64-3.8\ctcdecode
  running build_ext
  C:\Users\supre\anaconda3\lib\site-packages\torch\utils\cpp_extension.py:304: UserWarning: Error checking compiler version for cl: [WinError 2] Das System kann die angegebene Datei nicht finden
    warnings.warn(f'Error checking compiler version for {compiler}: {error}')
  building 'ctcdecode._ext.ctc_decode' extension
  error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
  Error in atexit._run_exitfuncs:
  Traceback (most recent call last):
    File "C:\Users\supre\anaconda3\lib\site-packages\colorama\ansitowin32.py", line 59, in closed
      return stream.closed
  ValueError: underlying buffer has been detached
  ----------------------------------------
  ERROR: Failed building wheel for ctcdecode
  Running setup.py clean for ctcdecode
Failed to build ctcdecode
Installing collected packages: ctcdecode
    Running setup.py install for ctcdecode ... error
    ERROR: Command errored out with exit status 1:
     command: 'C:\Users\supre\anaconda3\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\supre\\AppData\\Local\\Temp\\pip-req-build-qj51rq8f\\setup.py'"'"'; __file__='"'"'C:\\Users\\supre\\AppData\\Local\\Temp\\pip-req-build-qj51rq8f\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record 'C:\Users\supre\AppData\Local\Temp\pip-record-po3wgzez\install-record.txt' --single-version-externally-managed --compile --install-headers 'C:\Users\supre\anaconda3\Include\ctcdecode'
         cwd: C:\Users\supre\AppData\Local\Temp\pip-req-build-qj51rq8f\
    Complete output (20 lines):
    No CUDA runtime is found, using CUDA_HOME='C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0'
    C:\Users\supre\anaconda3\lib\distutils\extension.py:131: UserWarning: Unknown Extension options: 'package', 'with_cuda'
      warnings.warn(msg)
    running install
    running build
    running build_py
    creating build
    creating build\lib.win-amd64-3.8
    creating build\lib.win-amd64-3.8\ctcdecode
    copying ctcdecode\__init__.py -> build\lib.win-amd64-3.8\ctcdecode
    running build_ext
    C:\Users\supre\anaconda3\lib\site-packages\torch\utils\cpp_extension.py:304: UserWarning: Error checking compiler version for cl: [WinError 2] Das System kann die angegebene Datei nicht finden
      warnings.warn(f'Error checking compiler version for {compiler}: {error}')
    building 'ctcdecode._ext.ctc_decode' extension
    error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
    Error in atexit._run_exitfuncs:
    Traceback (most recent call last):
      File "C:\Users\supre\anaconda3\lib\site-packages\colorama\ansitowin32.py", line 59, in closed
        return stream.closed
    ValueError: underlying buffer has been detached
    ----------------------------------------
ERROR: Command errored out with exit status 1: 'C:\Users\supre\anaconda3\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\supre\\AppData\\Local\\Temp\\pip-req-build-qj51rq8f\\setup.py'"'"'; __file__='"'"'C:\\Users\\supre\\AppData\\Local\\Temp\\pip-req-build-qj51rq8f\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record 'C:\Users\supre\AppData\Local\Temp\pip-record-po3wgzez\install-record.txt' --single-version-externally-managed --compile --install-headers 'C:\Users\supre\anaconda3\Include\ctcdecode' Check the logs for full command output.

It would be very very nice if this could be fixed.
Thank's for every help in advance;)

hello all,
after spending a certain amount of time i found the problem. in my case, the development packages of python (python-dev and python3-dev) were not installed. after installing them on Ubuntu-18.04 using: sudo apt install python-dev && sudo apt install python3-dev, i was able to install ctcdecode without a problem.
however, this may not be the exact case for you so i recommend you to check whether you have the following packages/libraries (also giving the versions i am using):

essential packages for building debian packages: sudo apt install build-essential
torch==1.9.0
gcc and g++ version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)

hope these help!

Same problem here on MB Pro M1, I tried to pip install . but didn't work even after many times trying to install the third_party dependencies (Boost, OpenFst) with several different versions. I think the problem was on the g++ compiler. Any idea to resolve this?


REQUEST: New Reviewer for

GitHub Username
e.g. CoderPoet
Requirements

[x] Committer for at least 1 month
[x] Primary reviewer for at least 5 PRs to the codebase()
[x] Reviewer for, or author of, at least 10 substantial PRs to the codebase, with the definition of substantial area to the maintainer's discretion (e.g. refactors/adds new functionality rather than one-line pulls)
[x] Sponsored by a subproject maintainer
[x] With no objections from other maintainers
[x] May either self-nominate, be nominated by an maintainer in this subproject

List of contributions to CloudWeGo

Committer for 12 months

PRs with new functionality

kitex-contrib/obs-opentelemetry
hertz-contrib/obs-opentelemetry
kitex-contrib/xds
cloudwego/biz-demo:bookinfo
cloudwego/hertz-examples
cloudwego/kitex-examples

PRs reviewed

kitex-contrib/obs-opentelemetry(7)
hertz-contrib/obs-opentelemetry(7)
https://github.com/cloudwego/biz-demo/pull/29

Issues responded to

https://github.com/cloudwego/kitex/issues/461
https://github.com/cloudwego/kitex/issues/849
https://github.com/hertz-contrib/obs-opentelemetry/issues/17
https://github.com/hertz-contrib/obs-opentelemetry/issues/16
https://github.com/kitex-contrib/obs-opentelemetry/issues/7

Other

kitex-proxyless-practice-traffic-lane-implementation-with-istio-and-opentelemetry
https://github.com/cloudwego/community/issues/58

1

+1

+1  Congratulations ! 🎉🎉🎉

+1

+1 Congratulations ! 🎉🎉🎉

Strongly support! Thanks for your big contribution!

+1, welcome~

Hi, your request has been reviewed by the CloudWeGo community maintainer team and passed with majority approval.
You have been promoted as a member of Kitex Reviewer Team in CloudWeGo. Your certificate is here.
Please check Responsibilities and privileges for more details.
Congratulations !


Internal Server Error

Dear @ksugar,
I am trying to train a model with Cellsparse-api, in Qupath. I created annotations with the SAM-api, which I assigned to the Foreground and Background classes with no issues but when I want to run Cellsparce>StarDist>training I get an internal server error.
This happens on a single-plane greyscale image. I've set up SAM and cellsparse on different ports.
Below is the error I get in my console:
INFO:     Started server process [28052]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
INFO:     <IP_ADDRESS>:62580 - "POST /stardist/ HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\uvicorn\protocols\http\httptools_impl.py", line 435, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\uvicorn\middleware\proxy_headers.py", line 78, in __call__
    return await self.app(scope, receive, send)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\fastapi\applications.py", line 276, in __call__
    await super().__call__(scope, receive, send)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\starlette\applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\starlette\middleware\errors.py", line 184, in __call__
    raise exc
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\starlette\middleware\errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\starlette\middleware\exceptions.py", line 79, in __call__
    raise exc
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\starlette\middleware\exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\fastapi\middleware\asyncexitstack.py", line 21, in __call__
    raise e
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\fastapi\middleware\asyncexitstack.py", line 18, in __call__
    await self.app(scope, receive, send)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\starlette\routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\starlette\routing.py", line 276, in handle
    await self.app(scope, receive, send)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\starlette\routing.py", line 66, in app
    response = await func(request)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\fastapi\routing.py", line 237, in app
    raw_response = await run_endpoint_function(
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\fastapi\routing.py", line 163, in run_endpoint_function
    return await dependant.call(**values)
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\cellsparse_api\main.py", line 144, in stardist
    return run(
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\cellsparse_api\main.py", line 42, in run
    img = normalize(decode_image(b64img), 0, 100, axis=(0, 1))
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\cellsparse_api\main.py", line 30, in decode_image
    return np.array(Image.open(io.BytesIO(base64.b64decode(b64data))))
  File "C:\Users\LPUoO\anaconda3\envs\cellsparse-api\lib\site-packages\PIL\Image.py", line 3280, in open
    raise UnidentifiedImageError(msg)
PIL.UnidentifiedImageError: cannot identify image file <_io.BytesIO object at 0x00000158029F9B70>

Am I making a mistake?
Thanks a lot!

I notice now that similar errors may have been reported in the two issues below:
cellsparse-api/issues/2
qupath-extension-cellsparse/issues/3

Hi @LPUoO, thank you for reporting the issue.
Did you try it with a multi-channel image? Unfortunately, Cellsparse currently supports only grayscale images.

Thank you @FabianaMoresi, for reporting the issue!
It seems that the error happened when it tried to decode the image.
If you use an image with multi-channels, this error may happen.
I will work on solving it as soon as possible and will let you know once it's done.
For the moment, only grayscale images will work properly. If you want to test how it works, please try it with the grayscale images.

Originally posted by @ksugar in https://github.com/ksugar/cellsparse-api/issues/2#issuecomment-1601118330
I will work on supporting it as soon as possible.

Did you try it with a multi-channel image?

This happened on a single-plane greyscale image.
Thanks!

Dear @ksugar,
First a big thank you for your work. I install SAM and Cellsparse with GPU. But I recieve error from Cellsparse
SAM have the port 8000
Cellspare port 18000
I train a model with Cellpose but I can't load it
I tried to train a model Stardist or use inference but I recieve the 500 Internal server Error

2023-07-11 12:40:41.509574: W tensorflow/core/common_runtime/bfc_allocator.cc:491] <allocator contains no memory>
INFO:     <IP_ADDRESS>:49816 - "POST /stardist/ HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\uvicorn\protocols\http\httptools_impl.py", line 435, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\uvicorn\middleware\proxy_headers.py", line 78, in __call__
    return await self.app(scope, receive, send)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\fastapi\applications.py", line 276, in __call__
    await super().__call__(scope, receive, send)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\starlette\applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\starlette\middleware\errors.py", line 184, in __call__
    raise exc
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\starlette\middleware\errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\starlette\middleware\exceptions.py", line 79, in __call__
    raise exc
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\starlette\middleware\exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\fastapi\middleware\asyncexitstack.py", line 21, in __call__
    raise e
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\fastapi\middleware\asyncexitstack.py", line 18, in __call__
    await self.app(scope, receive, send)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\starlette\routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\starlette\routing.py", line 276, in handle
    await self.app(scope, receive, send)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\starlette\routing.py", line 66, in app
    response = await func(request)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\fastapi\routing.py", line 237, in app
    raw_response = await run_endpoint_function(
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\fastapi\routing.py", line 163, in run_endpoint_function
    return await dependant.call(**values)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\cellsparse_api\main.py", line 144, in stardist
    return run(
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\cellsparse_api\main.py", line 47, in run
    pred = runner._eval([img], modelname)[0]
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\cellsparse\runners\stardist_runner.py", line 106, in _eval
    model = StarDist2D(self.config, name=description, basedir=self.basedir)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\stardist\models\model2d.py", line 296, in __init__
    super().__init__(config, name=name, basedir=basedir)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\stardist\models\base.py", line 223, in __init__
    super().__init__(config=config, name=name, basedir=basedir)
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\csbdeep\models\base_model.py", line 111, in __init__
    self.keras_model = self._build()
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\stardist\models\model2d.py", line 312, in _build
    pooled_img = Conv2D(self.config.unet_n_filter_base, self.config.unet_kernel_size,
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\keras\utils\traceback_utils.py", line 70, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "C:\Users\Alex\miniconda3\envs\cellsparse-api\lib\site-packages\keras\backend.py", line 2100, in random_uniform
    return tf.random.stateless_uniform(
tensorflow.python.framework.errors_impl.FailedPreconditionError: {{function_node __wrapped____EagerConst_device_/job:localhost/replica:0/task:0/device:GPU:0}} Failed to allocate scratch buffer for device 0


Chore: Remove prepare script before publishing package

set-script works from npm v7 and we are on node v14 and npm v6
we are removing prepare script with husky install because it is
a lifecycle script that is runned before publish
we are publishing from ./dist directory where are no deps installed

Fixing my problem because I've used node v17 with npm v7 when developing this and didn't notice that we use node v14 in CI pipeline.
🤔 Maybe we should switch to node v16 which is active LTS.

🤔 Maybe we should switch to node v16 which is active LTS.

Would it mean we could use npm set-script instead of manipulating package.json?
Also, I think shift to v16 should be started in all LMC projects then.

Would it mean we could use npm set-script instead of manipulating package.json?

Yes, we can use npm set-script but it also manipulates package.json.


AEM 6.2

Is it time to start updating developer tools so that they work seamlessly with AEM 6.2?

do you have something specific in mind? This lazybones template has been able to generate 6.2 projects for a while.


The latest "interactive" extension (0.4.3) outputs an error in the latest CLI (2.0.75)

Command Name
az interactive
Errors:
az>> Exception in thread Thread-1:
Traceback (most recent call last):
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\threading.py", line 916, in _bootstrap_inner
    self.run()
...

To Reproduce:
Just run az interactive.
Expected Behavior
Interactive mode should start without errors.
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
Shell: cmd.exe

azure-cli 2.0.75

Extensions:
azure-devops 0.13.0
interactive 0.4.3
resource-graph 1.0.0

Additional Context

@jiasli this is an issue raised by Aleksandar. Please take a look.

The most inner error is ModuleNotFoundError: No module named 'azure.mgmt.apimanagement.models.api_management_client_enums'. @zikalino, could you take a look at this packaging issue?

Just a moment ago, I executed az interactive for the first time and received the following:
E:\> az interactive
This command is in preview. It may be changed/removed in a future release.
Installing the Interactive extension...
The installed extension 'interactive' is in preview.
The command failed with an unexpected error. Here is the traceback:

No module named 'prompt_toolkit.interface'
Traceback (most recent call last):
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-rtk110ve\knack\knack\cli.py", line 206, in invoke
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-rtk110ve\azure-cli-core\azure\cli\core\commands\__init__.py", line 603, in execute
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-rtk110ve\azure-cli-core\azure\cli\core\commands\__init__.py", line 661, in _run_jobs_serially
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-rtk110ve\azure-cli-core\azure\cli\core\commands\__init__.py", line 654, in _run_job
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-rtk110ve\six\six.py", line 693, in reraise
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-rtk110ve\azure-cli-core\azure\cli\core\commands\__init__.py", line 631, in _run_job
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-rtk110ve\azure-cli-core\azure\cli\core\commands\__init__.py", line 305, in __call__
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-rtk110ve\azure-cli-core\azure\cli\core\__init__.py", line 485, in default_command_handler
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-rtk110ve\azure-cli\azure\cli\command_modules\interactive\custom.py", line 41, in start_shell
  File "C:\Users\marck\.azure\cliextensions\interactive\azext_interactive\__init__.py", line 10, in start_shell
    from .azclishell.app import AzInteractiveShell
  File "C:\Users\marck\.azure\cliextensions\interactive\azext_interactive\azclishell\app.py", line 27, in <module>
    from prompt_toolkit.interface import Application, CommandLineInterface
ModuleNotFoundError: No module named 'prompt_toolkit.interface'

To open an issue, please run: 'az feedback'

E:\> az --version
azure-cli                         2.0.70 *

command-modules-nspkg               2.0.3
core                              2.0.70 *
nspkg                              3.0.4
telemetry                          1.0.3 *

Extensions:
interactive                        0.4.3

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\marck\.azure\cliextensions'

Python (Windows) 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)]

Legal docs and information: aka.ms/AzureCliLegal

You have 3 updates available. Consider updating your CLI installation.

I attempted to upgrade but the Azure CLI wizard failed doing so.

@fengzhou-msft to take a look.

should be fixed with https://github.com/Azure/azure-cli/pull/10623, will release with next version (scheduled next week).


[REVIEW] vishalda

GitHub Profile Link
https://github.com/vishalda

Awesome profile! I liked it a lot. 😄👍
I have made a pull request in your repository for
some minor improvements in the README.md file.
Thanks for sharing your amazing profile with us! 😉

with the changes of @Panquesito7 its looking really good for me 🚀

@schmelto agree

Awesome profile! I liked it a lot. smile+1
I have made a pull request in your repository for
some minor improvements in the README.md file.
Thanks for sharing your amazing profile with us! wink

Thank you for the pull request! 😄

Looks great, some thoughts

Animated heading does not work well in lightmode
100% commits, suggestion doing issues, pull requests and reviews

Review live stream https://www.youtube.com/watch?v=NxxJ_5nyG9E


Replace future with six

This will remove a package dependency on future, which few people will have installed.

future (as in https://pypi.python.org/pypi/future) is used in places, instead of __future__ (https://docs.python.org/2/library/future.html)?

Correct, it's actually imported as past, which is a part of the future package. It's mostly for string-related issues.


Proposal: Strict ACL validation such that agents can detect and reject unsupported ACLs

Some of the current proposals (in particular https://github.com/solid/authorization-panel/issues/92) would introduce a breaking change.
This means that, in general, we need to think about the consequences of the freedom that RDF provides. In other words: what should agents do when they encounter an unknown predicate or otherwise unknown triple in an ACL document?
I propose that agents should validate ACL documents against a strict shape before trying to enforce or modify them.

👍  to this. @RubenVerborgh can you confirm whether this use case supports this proposal, and/or whether you would see the need for expansion or adjustment?

I propose that agents should validate ACL documents against a strict shape before trying to enforce or modify them.a

I think currently the storage (Resource Server) enforces access control rules. We should avoid situations where storage would accept access control rules if it is not capable to fully enforce. In that case only check on create (including restoring data from backup) or update seems needed.

This is part of a recurring issue. See https://github.com/solid/specification/issues/169 . But I'm not sure if this panel is observing the issues in solid/specification.


Calling 'vim.diagnostic.goto_next()' inactivates lightline

I'm using Neovim with LSP plugins namely neovim/nvim-lspconfig.
There's functions that moves cursor to next/previous diagnose called vim.diagnostic.goto_next() and goto_prev().
Here's how I configured:
vim.keymap.set('n', '[d', vim.diagnostic.goto_prev)
vim.keymap.set('n', ']d', vim.diagnostic.goto_next)

You can find out more at their github.
Problem is, moving to next/previous diagnose inactivates Lightline.

Initial state, everything is fine

Moved cursor by calling goto_next

Now my Lightline is disabled oh no

Moving to other buffer or reopening the buffer reactivates it but this is a little bit disturbing :(
asdf@asdarf ~ $ nvim --version
NVIM v0.9.2
Build type: Release
LuaJIT 2.1.0-beta3

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/opt/homebrew/Cellar/neovim/0.9.2/share/nvim"

Run :checkhealth for more info

I figured out it's not related to goto_next, it's caused by opening floating window.
It has been discussed already, and there's a plugin implementing it using Neovim's laststatus feature, but it's limited to Neovim.

Are you using the latest version of lightline? I recently accepted a Neovim related patch so make sure to update. If it is the latest, please create a precise steps to reproduce the issue. Just lua vim.diagnostic.goto_next() warns No more valid diagnostics to move to.

Thanks for checking out,
I'm using latest commit
commit f11645cc6d37871244f2ea0ae972d3f6af9c8f73 (HEAD -> master, origin/master, origin/HEAD)
Merge: b1e91b4 3d10b50
Author: itchyny<EMAIL_ADDRESS>Date:   Sun Sep 3 19:09:07 2023 +0900

    Merge pull request #659 from 4513ECHO/fix/neovim-floatwin

    fix: Make not to skip floatwin if it is focusable

I have checked, opening floating window actually does not inactivates lightline, I used below command to check
:call nvim_open_win(0, v:false, { "relative": "editor", "width": 40, "height": 20, "col": 0, "row": 20})

I think goto_next does some more work just opening window.
To reproduce, we need working LSP environment which includes,

Neovim
Neovim LSP config
Dev environment and an language server

I used Typescript tsserver for the example, so npm and Typescript compiler is required.# assume npm is already installed and $PATH is configured
npm install --global typescript
npm install --global typescript-language-server

Link to tsserver configuration doc for nvim-lspconfig

Assume now you have working LSP config, make a directory and init Typescript projectnpm init -y
npx tsc --init

Type some erroneous code, below code should sufficefunction foo() {
  throw new Error("oh no");
  console.log("bar")
}

Invoke goto_next

I attached my minimal Typescript project for case if you have trouble creating project.
ts.tar.gz

@4513ECHO Would you help us fixing this?

Please try this workaround. Maybe this is bug of Neovim itself...
https://github.com/itchyny/lightline.vim/pull/659#issuecomment-1704032081

Ah, okay, thanks. Is there any bug report to Neovim?

@4513ECHO Yup I tried the patch and it works well now.
It looks like it's default behavior, (i.e. it's not a bug) so I think it won't be changed.
@itchyny We may conclude this issue invalid and close, but new users would face this issue later on so documenting it would be helpful. If you mind cluttered README file with troubleshooting methods, Github Wiki might come in handy.


Auto-detected frameworks cannot use the static server

Describe the bug
If a framework has an entry in framework-info it disables the static server, meaning that any framework that needs this cannot use auto-detection, so misses out on the other benefits of auto-detection, such as build command.
To Reproduce
Cannot be reproduced because it would require adding a framework to framework-info, but the code is here:
https://github.com/netlify/cli/blob/main/src/utils/detect-server-settings.js#L260
This is related to #3654, and could be fixed with a similar solution to that, or more simply by starting the static server if the framework specifies no dev command and/or target port.

My comment here is relevant for this issue to

@ascorbic I opened https://github.com/netlify/framework-info/issues/657.
Once we have that I think this issue will be about adding useStaticServer: true here https://github.com/netlify/cli/blob/f5323c45fec92c3a1e4604f472ea6ee9e468b67b/src/utils/detect-server-settings.js#L295 when a command/port is missing.