EC <IP_ADDRESS> linked to GO:0000810 has now been transferred to EC <IP_ADDRESS>

EC <IP_ADDRESS> linked to GO: 0000810 has now been transferred to EC <IP_ADDRESS>. The Rhea reaction linked to the EC numbers remains the same. The transfer will be part of the freeze taking place next Wednesday and should go public in release 2022_05 December 7.

Parent change 3.1.3.- to 3.6.1.- hydrolase activity, acting on acid anhydrides  but current parent pyrophosphatase activity, a child of 3.6.1.- So keep.
Keep RHEA
Metacyc is already updated.
Done.


Documentation for deploying Graph Explorer in Amazon ECS

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Looks good..Thanks


Uses the dockerfileInspector in the runmount strategy.

Identifies the runmount images by BUILD_OUT and SOUS_RUNSPEC_PATH environment variables.
Builds on #809

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

          1 Warning

:warning:
Big PR: 1187 lines of code changed

  Generated by :no_entry_sign: Danger

Codecov Report

Merging #810 into master will increase coverage by 0.07%.
The diff coverage is 87.58%.

@@            Coverage Diff            @@
##           master    #810      +/-   ##
=========================================
+ Coverage   52.73%   52.8%   +0.07%
=========================================
  Files         277     277
  Lines       16487   16507      +20
=========================================
+ Hits         8694    8717      +23
+ Misses       7098    7096       -2
+ Partials      695     694       -1

Impacted Files
Coverage Δ

ext/docker/dockerfile_buildpack.go
34.78% <ø> (ø)
:arrow_up:

ext/docker/splitcontainer_splitbuilder.go
68.93% <ø> (ø)
:arrow_up:

config/config.go
63.07% <0%> (ø)
:arrow_up:

ext/docker/selector.go
0% <0%> (ø)
:arrow_up:

ext/docker/splitcontainer_buildpack.go
61.22% <100%> (+6.05%)
:arrow_up:

ext/docker/runmount_builder.go
74.15% <100%> (+0.44%)
:arrow_up:

util/restful/router.go
72.31% <75%> (+0.15%)
:arrow_up:

ext/docker/runmount_buildpack.go
33.33% <86.36%> (+10.38%)
:arrow_up:

ext/docker/dockerfileinspector.go
87.87% <87.87%> (ø)

... and 2 more

Continue to review full report at Codecov.

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


feat: project name must be lowercase

Restrict project names to lowercase, and to be within the permitted length for hostname segments: 63 chars. Additionally, restrict using underscores in a project names, as it's not valid in hostnames.
Note: when we merge this we can remove the ad-hoc validation in gateway: https://github.com/shuttle-hq/shuttle/blob/main/gateway/src/service.rs#L464-L475

@oddgrd , how should we approach this? It's still relevant?

Closing in favor of #1223


Fix type in config.cfg in pipelines.md

The file extension given didn't match the examples

Thanks a lot :)


Add printer extension

Please add an extension that works with printers. Here's a mockup of what that could look like.

Interesting

i believe all the browser will let us do is open up your browser's printing menu but not really read anything from there

Yeah, all we can do is use print() with some tiny parameters, we really can't make this a reality.

Oh well


Show system name on login and header

Add eSaúde logo on login and header.

 Show system name on login and header

Coverage decreased (-0.3%) to 42.157% when pulling 8b3d02529c890824b810ae4ff7038bdce4f1ef35 on ynurmahomed:login into 28c226e27ad73aed36838f82eb365ba3384d1d84 on esaude:master.

Coverage decreased (-0.2%) to 42.244% when pulling 91577b36abee40f6dd660499c177be1e62ff79ae on ynurmahomed:login into 98f43c062f8c7e0244b1039e31264ad95188ef10 on esaude:master.

Coverage increased (+0.01%) to 42.508% when pulling 00cfdd05aaa05046a2ec09e682a61cb60c57bcd2 on ynurmahomed:login into 98f43c062f8c7e0244b1039e31264ad95188ef10 on esaude:master.

Coverage increased (+0.01%) to 42.508% when pulling cdc32615d9601a25a6ac6495331e9a8896ce1920 on ynurmahomed:login into 98f43c062f8c7e0244b1039e31264ad95188ef10 on esaude:master.


Finalizer cleanup

What this PR does / why we need it:

corrects issues with finalizers that's been holding over since early railgun prototypes
improves consistency on object deletions
adds tests to prove new finalizer logic works appropriately

Which issue this PR fixes
fixes https://github.com/Kong/kubernetes-ingress-controller/issues/1515

flagging as do not merge because before we merge this I want to do some rebasing.

tl;dr

This looks probably fine, and the changes other than the finalizer template code change itself look definitely fine.
While this fixes any issues with Secrets by simply not attaching finalizers to them, I can't see why they were affected before but other resources weren't. Would that issue not also affect Ingresses, which still have finalizers?
Do we think we need finalizers at all? After not really knowing about them, I've done research and discovered that they have ALL SORTS OF COMPLICATIONS. We didn't have them in 1.x and it doesn't appear that their use case is truly justified for us. Do we want to continue using them at all?

The commits not directly related to the finalizer stuff look fine, but I have many questions about the finalizers.
Do we know why this was a problem for Secrets specifically? While this does remove our finalizer from them, it remains on other resources (e.g. Ingresses), and I'd expect that those also block namespace deletion if not removed--AFAIK the problem is that K8S won't allow deletion of namespaces without deleting its contents, and while it cascades these deletes automatically, the cascaded deletes won't finish until all finalizers are cleared from those objects.
The original section of the reconciler code in the current tip of next did add our finalizer to everything, but it also apparently removed it from everything being deleted. Was there some reason that Secrets failed timestamp condition there, or consistently resulted in an error when we called err := r.Proxy.DeleteObject(obj)? The latter seems more possible (it's our code and it's more complex), but a brief review of that code indicates it's only deleting from cache, which should succeed.
That all said, this and the error Jimin encountered (which is caused by me not properly adding permissions in #1457) makes me question whether we need the finalizers at all. The kubebuilder example includes some logic we don't have to confirm the presence of the finalizer before doing things:
        if containsString(cronJob.GetFinalizers(), myFinalizerName) {
            // our finalizer is present, so lets handle any external dependency
            if err := r.deleteExternalResources(cronJob); err != nil {

but we don't: we simply delete all deleting resources from our cache before stripping the finalizer, without any check to see if the finalizer is present. We still do that in the proposed version, though with additional logic to requeue.
We won't remove our finalizer on resources that still include it until the proxy delete actually succeeds (because the requeue return precedes the finalizer clear), but we'll requeue indefinitely until the proxy delete does in fact succeed whether or not the finalizer is set.
The class annotation distinction between resources that get finalizers and those that don't seems rather arbitrary, as anything we reconcile influences Kong proxy configuration. For example, Ingresses (which need class annotations and will get a finalizer) result in routes, whereas KongPlugins attached to a Service (which do not need class annotations and will not get a finalizer) result in a plugin on a Kong service. It's not clear why we'd block resource deletion on one but not the other.
Kubernetes guidance on when and why to use finalizers is unfortunately rather unclear, but my rough takeaway is that you use them when:

You really want to avoid deleting something until some other condition is met (e.g. deleting a PV with an active PVC is almost certainly a bad idea).
You really want to ensure some action elsewhere (e.g. failing to delete a cloud provider load balancer bound to a LoadBalancer means it sits around costing you money until you realize deletion failed and destroy it manually).

For us:

We don't do anything like the first case currently, though we could do something like add a finalizer to a KongPlugin after we see an annotation referencing it on an Ingress: you would not be able to remove KongPlugins until you remove references to them.
Our deletions are like the second case, though the justification is quite weak IMO. We do (now) try to eventually remove the object from the cache (which will in turn purge it from config) and in the worst case, can fix cases where retries never succeed by just restarting the controller, which will build a fresh cache from extant resources only. Furthermore, removing an object from the cache is no guarantee that the config is not still active, since it's quite possible to remove from cache, regenerate a config, and fail to apply config because the proxy rejects it.

In general, the UX for finalizers also seems poor:

Finalizers basically just hang kubectl (since the delete never finishes) or leave the resource in place until the finalizer clears (if you get bored and terminate the hung kubectl). It doesn't appear that there's any indication that the finalizer is what blocks it--there are no messages in kubectl delete output, even at V6, and no events in kubectl describe that refer to them)--beyond the presence of the finalizer in the YAML itself.
Finalizers don't provide information about deletion failures on resources themselves. You have to know to go check the finalizer owner's logs to see why it's not being removed, which is what we'd instruct users to do anyway if config is stuck (which usually happens because config is rejected, not because resources are stuck in cache).
It's furthermore not clear to me what should/does happen if you stop the controller and then want to remove something it finalized. It doesn't look like we remove the finalizer on shutdown, only on resource deletion. You're just stuck with those resources until you restart the controller.

tl;dr
* This looks probably fine, and the changes other than the finalizer template code change itself look definitely fine.

* While this fixes any issues with Secrets by simply not attaching finalizers to them, I can't see why they were affected before but other resources weren't. Would that issue not also affect Ingresses, which still have finalizers?

This was happening due to a race condition: the tests weren't verifying that their namespaces were properly torn down, so the controller would be shut down before it could process all finalizers.
This is now fixed with the namespace teardown code.

* Do we think we need finalizers at all? After not really knowing about them, I've done research and discovered that they have ALL SORTS OF COMPLICATIONS. We didn't have them in 1.x and it doesn't appear that their use case is truly justified for us. Do we want to continue using them at all?

The commits not directly related to the finalizer stuff look fine, but I have many questions about the finalizers.
Do we know why this was a problem for Secrets specifically? While this does remove our finalizer from them, it remains on other resources (e.g. Ingresses), and I'd expect that those also block namespace deletion if not removed--AFAIK the problem is that K8S won't allow deletion of namespaces without deleting its contents, and while it cascades these deletes automatically, the cascaded deletes won't finish until all finalizers are cleared from those objects.
The original section of the reconciler code in the current tip of next did add our finalizer to everything, but it also apparently removed it from everything being deleted. Was there some reason that Secrets failed timestamp condition there, or consistently resulted in an error when we called err := r.Proxy.DeleteObject(obj)? The latter seems more possible (it's our code and it's more complex), but a brief review of that code indicates it's only deleting from cache, which should succeed.
That all said, this and the error Jimin encountered (which is caused by me not properly adding permissions in #1457) makes me question whether we need the finalizers at all. The kubebuilder example includes some logic we don't have to confirm the presence of the finalizer before doing things:
        if containsString(cronJob.GetFinalizers(), myFinalizerName) {
            // our finalizer is present, so lets handle any external dependency
            if err := r.deleteExternalResources(cronJob); err != nil {

but we don't: we simply delete all deleting resources from our cache before stripping the finalizer, without any check to see if the finalizer is present. We still do that in the proposed version, though with additional logic to requeue.
We won't remove our finalizer on resources that still include it until the proxy delete actually succeeds (because the requeue return precedes the finalizer clear), but we'll requeue indefinitely until the proxy delete does in fact succeed whether or not the finalizer is set.
The class annotation distinction between resources that get finalizers and those that don't seems rather arbitrary, as anything we reconcile influences Kong proxy configuration. For example, Ingresses (which need class annotations and will get a finalizer) result in routes, whereas KongPlugins attached to a Service (which do not need class annotations and will not get a finalizer) result in a plugin on a Kong service. It's not clear why we'd block resource deletion on one but not the other.
Kubernetes guidance on when and why to use finalizers is unfortunately rather unclear, but my rough takeaway is that you use them when:
* You really want to avoid deleting something until some other condition is met (e.g. deleting a PV with an active PVC is almost certainly a bad idea).

* You really want to ensure some action elsewhere (e.g. failing to delete a cloud provider load balancer bound to a LoadBalancer means it sits around costing you money until you realize deletion failed and destroy it manually).

For us:
* We don't do anything like the first case currently, though we could do something like add a finalizer to a KongPlugin after we see an annotation referencing it on an Ingress: you would not be able to remove KongPlugins until you remove references to them.

* Our deletions are like the second case, though the justification is quite weak IMO. We do (now) try to eventually remove the object from the cache (which will in turn purge it from config) and in the worst case, can fix cases where retries never succeed by just restarting the controller, which will build a fresh cache from extant resources only. Furthermore, removing an object from the cache is _no guarantee that the config is not still active_, since it's quite possible to remove from cache, regenerate a config, and fail to apply config because the proxy rejects it.

In general, the UX for finalizers also seems poor:
1. Finalizers basically just hang kubectl (since the delete never finishes) or leave the resource in place until the finalizer clears (if you get bored and terminate the hung kubectl). It doesn't appear that there's any indication that the finalizer is what blocks it--there are no messages in `kubectl delete` output, even at V6, and no events in `kubectl describe` that refer to them)--beyond the presence of the finalizer in the YAML itself.

2. Finalizers don't provide information about deletion failures on resources themselves. You have to know to go check the finalizer owner's logs to see why it's not being removed, which is what we'd instruct users to do anyway if config is stuck (which usually happens because config is rejected, not because resources are stuck in cache).

3. It's furthermore not clear to me what should/does happen if you stop the controller and then want to remove something it finalized. It doesn't look like we remove the finalizer on shutdown, only on resource deletion. You're just stuck with those resources until you restart the controller.

I totally feel you on this.
Long story short? When this was originally written the intention was to ensure the relevant configurations in the proxy were actually removed before letting the objects delete. Technical limitations regarding our integration with the Kong Admin API make this really hard to pull off right now so this didn't actually get implemented as originally intended.
So ultimately given the feasibility issues to make good use of them, I'll pull them all out, we can add them back later if we find solid use cases to do so. :+1:

@rainest check 1553b0fad3866dc9ba12b03ec109077c4c306f02 and let me know what you think :+1:

gonna get things working and then re-open :+1:

Fixed and working locally now :+1:


How to get character bbox annotation?

this project is very helpful for generating synth text for scene text recognition, and it seem to generate text image by combine several character images, but the outputs doesn't contain information of each character, is it possible to get character annotation, for example, each character and its location?

Hi,
It generates images by rendering several characters, but can't get character bboxes because transformation is applied after merging characters.
It needs to change rendering process to get character bboxes.
I'll try to improve rendering process to get character bboxes (and text mask).
Thanks.

@moonbings
Hi,
Do you have any plan to make code to get text box? Or is this project over?
Thanks

I ask if I can get the word or sentence bbox

Hi,
Sorry for the late reply.
Unfortunately, I can't maintain this project because of personal reasons. 😢
You can modify https://github.com/clovaai/synthtiger/blob/master/examples/synthtiger/template.py#L177-L190 this code to get character/word bbox.
For character bboxes, you can get it by making temporary copied character layers. Apply same transformation to temporary character layers and then return these bboxes.
For word bbox, you can get it by merging character bboxes.
Note that, this bbox is an world coordinates, so you need to change coordinates.
Here's an example.
def _generate_fg(self, color, style):
    ...

    char_layers = [layers.TextLayer(char, **font) for char in chars]
    self.shape.apply(char_layers)
    self.layout.apply(char_layers, {"meta": {"vertical": self.vertical}})

    layer = layers.Group(char_layers).merge()
    self.color.apply([layer], color)
    self.texture.apply([layer])

    self.style.apply([layer], style)
    self.style.apply(char_layers, style) # added

    transform = self.transform.sample() # added
    self.transform.apply([layer], transform) # changed
    self.transform.apply(char_layers, transform) # added

    self.fit.apply([layer])
    self.fit.apply(char_layers) # changed

    self.pad.apply([layer])
    out = layer.output()

    # change coordinates
    for char_layer in char_layers:
        char_layer.topleft -= layer.topleft

    # get bboxes
    char_bboxes = [char_layer.bbox for char_layer in char_layers] # [[left, top, width, height], ...]
    word_bbox = utils.merge_bbox(char_bboxes) # [left, top, width, height]

    return out, label, char_bboxes, word_bbox

And then, you need to modify this part to save bboxes.
https://github.com/clovaai/synthtiger/blob/master/examples/synthtiger/template.py#L132-L153
Thanks.

Now, we can get character bboxes and text mask.
Character bbox data is in coord.txt file and mask data is in masks directory.
The format of coord.txt is <image_path>\t<bbox>\t<bbox>\t<bbox>.... (<bbox>=<xmin>,<ymin>,<xmax>,<ymax>)
Check out the latest code.

Thanks.


Allow to specify path

Describe your feature request
I use rocksdb as surrealdb backend so would be good if we can specify optional path when starting the surrealdb server.
surreal start -u root -p root -s file:///home/prabir/app/path_to.db

Are you willing to contribute this feature?
No

Seems like works already.

Hey, this is already possible by changing the local database storage on the settings screen. You'll be able to input a path once selected

I can see it now. Thanks.


[IMP] Add datadir to .gitignore

Having a data directory inside an Odoo instance based on waft makes it easy to have self-contained deployments, which is especially handy for local development environments.
This change just enables a local data directory, it changes nothing in the default installation location.

@thomaspaulb I think it is for filestore directory
@NL66278
the long answer is: it is okay for me if you like to use this way in your laptop, but not in the containers in our servers, because it is not a variable in our system yet, and for all containers in our system, we use the default path (${Home}/.local/share/Odoo/filestore/)
and we use this path in nightly scripts and in backups rules and in ansible too, so, I will merge it, but, don't use it in our containers until we update our system to have this feature.
the short answer: accepted in personal use.

@thomaspaulb @Hussam-Suleiman It is indeed for personal use.
I have data_dir = ${ODOO_WORK_DIR}/datadir in common/conf.d/test-odoo.cfg
In my $HOME directory I have a directory projecten (projects). For each customer / project I have a waft deployment branch under that directory. I a project is no longer needed, I can just rm -fr the whole thing and be done with it. I is also easier to maneuver between the data directory and the other directories in the project.

You'll still have to dropdb the database though

@NL66278 it is a good idea to make waft more flexible, I moved the ignored directory in waft repository because here will not effect the main folder.
Regards!

You'll still have to dropdb the database though

I know ;-)


Fix ESLint linting errors

Assuming there are any, this may just need to be closed if we find there aren't many once configured.

This is why we lint.... this test was not even doing what it appeared to be doing.

C:\Users\chadb\code\videospeed-refactoring\src\lib\logger.test.js
  46:34  error  Matchers must be called to assert  jest/valid-expect
  51:34  error  Matchers must be called to assert  jest/valid-expect
  58:34  error  Matchers must be called to assert  jest/valid-expect

✖ 3 problems (3 errors, 0 warnings)

Fixed in https://github.com/ChadBailey/videospeed-refactoring/commit/52c2b59a3b861c2aaa82a670a1036fc31795147c


is there anyway to set metadata content-type on upload?

im serving some webfiles from a bucket without an extension (.html), id like to be able to ensure the content-type metadata property is preserved as (text/html), It seems to be removed after sync.

https://cloud.google.com/storage/docs/metadata?authuser=1&_ga=2.155380219.-118707203.1677198202&_gac=1.83826020.1684438279.Cj0KCQjwmZejBhC_ARIsAGhCqnf7m5EDZlDn-_mexwW0MXytBQTKQRDlefE9_-bsTkjW1w_l4RYgBqIaAhlaEALw_wcB#content-type

Seems like when its uploaded the content is scanned and google takes a guess at the content type.

Right now there is no way to configure a default content type for files without a file extension.
Maybe a workaround like this could fix your issue: https://github.com/patrickwyler/gcs-bucket-sync-action/issues/5#issue-1599678460

thanks for your response, this is helpful
it looks like ill need to use gsutil to set it manually in a follow up task.


Field "OR" is not defined by type UserWhereUniqueInput

Describe the bug
Trying to do
const user = await ctx.db.query.user({
        where: {  OR: [
            { facebookUserId: id },
            { email: email },
          ], },
 });

causes prisma to error with:
Variable "$_v0_where" got invalid value<EMAIL_ADDRESS>Field "OR" is not defined by type UserWhereUniqueInput

To Reproduce
Steps to reproduce the behavior:
Create a User schema, and make sure WHERE fields use @unique
type User {
  id: ID! @unique
  username: String! @unique
  email: String! @unique
  password: String!
  name: String!
  facebookUserId: String @unique
  googleUserId: String @unique
  createdAt: DateTime!
  updatedAt: DateTime!
  posts: [Post!]!
  listings: [Listing!]! @relation(name: "ListingsByUser" onDelete: CASCADE)
}

Try calling within a Mutation
async facebookLogin(parent, { appId, token, redirectUrl }, ctx) {

    const facebookSecret='XXXXXXXX';

    const fields = `id,name,email,first_name,last_name,birthday,locale,gender,picture`;
    const accessEndpoint = `https://graph.facebook.com/v3.1/oauth/access_token?client_id=${appId}&redirect_uri=${redirectUrl}&client_secret=${facebookSecret}&code=${token}`;
    const userEndpoint = `https://graph.facebook.com/v3.1/me?fields=${fields}`;

    try {
      const getAccessToken = await axios.get(accessEndpoint);
      const { access_token } = await getAccessToken.data;
      const data = await axios.get(`${userEndpoint}&access_token=${access_token}`);

      console.log('$$$ DATA', data.data);

      const { id, name, email } = await data.data;

      const user = await ctx.db.query.user({
        where: {  OR: [
            { facebookUserId: id },
            { email: email },
          ], },
      });

     ...the rest

Expected behavior
It should return a user based on the facebookUserId, or email address
Versions (please complete the following information):

OS: Windows 10
prisma CLI: prisma/1.13.4 (windows-x64) node-v8.11.1
Prisma Server: prismagraphql/prisma:1.8
graphql-cli, prisma-binding, graphql-yoga

I just updated to latest prismagraphql/prisma:1.13, same error

The where of the user query only exposes unique fields.
Instead, you can either use the users query, or send two user queries - one using the facebookId and one using the email unique filter.

Ah ok, that makes sense. I'll give it a try, thanks.

I'm getting this error now.
OR in where is not working
I'm following this tutorial: https://www.howtographql.com/graphql-js/8-filtering-pagination-and-sorting/
However I'm using latest prisma install locally in docker container with MongoDB


Named Routes in Multi Auth Route files

whenever i create a new route in a guard route, when i call the route name from my controller, it throws errror saying the route name is undefined
Route [nameOfRoute] not defined.
Please assist me to solve this issue

Show me your code.

in routes/userauth.php
Route::get('home', 'Userauth\MainController@index')->name('index');
in app/Http/Controllers/Userauth/MainController.php
return redirect()->route('index')->with('message','user settings Updated Successfully ');
where Userauth is the name of a created guard and MainController is the controller in the Userauth folder, now when i give a return to redirect and link the index route name, it says Route [index] not defined.

When you name route "index" in your {guard}.php file the name of route will be:
{guard.}index

Route with Controller not working for Admin


Add new way of authentication

Example usage:
base_url = "https://sandbox-sdwan-2.cisco.com/"
username = "devnetuser"
password = "RG!_Yw919_83"

s = requests.Session()
s.auth = vManageAuth(base_url, username, password, verify=False)
s.verify = False

response = s.get("https://sandbox-sdwan-2.cisco.com/dataservice/device")
print(response.json()['data'])
>>> [{'deviceId': '<IP_ADDRESS>', 'system-ip': '<IP_ADDRESS>', 'host-name': 'vmanage', 'reachability': 'reachable', ...}]

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/26


use only 400 and 700 font-weight

PR Type
Bugfix
Context
Closes #8060
Had issue bounty label?

[x] Fill up your KSM address: Payout

cc @exezbcz

thanks!
pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 5.71 USD/DOT ~ 3.503 $DOT
🧗 16SpvdDgKNiQ3c53DxX7refnQcKUD3uRNim3Z1HBJLNGrtSP
🔗 0x8cee05233ddea4a8a884c85df89cc07df5f3759fd0926bc2fc8f931ae67298b8
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


FTP PORT

If you want I can close the matter here and not bother you anymore.
However, the problem remains open because, using your wonderful library, everything works until I try to change the FTP access port. This isn't about the Arduino or the code used because I use the calls that your library provides.
So assuming that:

The provider provided me with access port 2201
2)Filezilla correctly accesses the selected FTP area through this port
The call of your library:
ESP32_FTPClient ftp (FTP_SER,FTP_POR,FTP_USR,FTP_PWD, 5000, 2);
works only if FTP_POR = 21.
The code used here has nothing to do with it.
If you can kindly send me a concrete example of code that I can understand, I would be grateful.
If you need to intervene on ESP32_FTPClient.cpp or ESP32_FTPClient.h tell me how to do it.
My impression is that the call is not made where the FTP port is specified.
If you want to help me I would be infinitely grateful otherwise, as they say where I come from, thanks anyway and have a good life.

If you can kindly send me a concrete example of code that I can understand, I would be grateful.

No, I can not send a concrete example of the code you can understand because this is subjective and as I mentioned if you would like to understand how C++ and Arduino works, there are resources out there that would help you on that.
The port is set here: https://github.com/ldab/ESP32_FTPClient/blob/master/src/ESP32_FTPClient.cpp#L142


Optimization of MPI layer

Original issue: https://charm.cs.illinois.edu/redmine/issues/23

Revisit MPI layer and possibly rewrite to improve performance.

Original date: 2013-02-06 06:29:03

I've heard through the grapevine (not to be confused with Harshitha's LB strategy) that Ralf has achieved near-parity with some native layer in his work at Argonne for Pavan. Marking it 'in-progress' accordingly.

Original date: 2013-02-11 22:24:31

Quoting Ralf's Email on this-
As for MPI, we've found something that apparently makes it be as fast as gemini_gni-crayxe, and the same seems to be true of ibverbs. We're testing this on intrepid & vesta as well. Pavan doesn't care about tcp (i.e. MPI over sockets) at all, where the difference in performance is biggest (almost 4x).

Original date: 2017-01-17 03:29:53

It looks like none of the work mentioned above was ever merged...

Original date: 2018-04-29 22:45:56

Small optimization to use MPI-3's MPI_Mprobe and MPI_Mrecv where possible: ~~https://charm.cs.illinois.edu/gerrit/#/c/charm/+/2785/~~ https://github.com/UIUC-PPL/charm/commit/f7fbaaaae1088ee65988c1345203da3ed55abcc4
Edit: we ended up reverting this because support for MPI_Mprobe is spotty and not really detectable at configure time in a portable manner.

I reached out to Ralf in 2018 about these patches and they are presumed lost. However he did mention that "IIRC the code was mostly using MPI3 RMA operations in a fairly natural way."

wow.. it was not even saved on a branch?

Not if it was never pushed out of his local repository.

On Mar 12, 2020, at 9:38 AM, Laxmikant Kale<EMAIL_ADDRESS>wrote:
wow.. it was not even saved on a branch?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/UIUC-PPL/charm/issues/23#issuecomment-598224031, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3HFH57UJHEM4RWEAC5UKLRHDXWXANCNFSM4HIHQJYA.

Here's some minor MPI layer optimizations we've done in the recent-ish past with some notes on their status / motivations:
Add build-time option to use MPI_Alloc_mem inside CmiAlloc. This will potentially speed up messaging but is off by default pending more performance testing and may need more pooling of messages: https://github.com/UIUC-PPL/charm/commit/724b2a02084e288bbd6cbdd22b60891b504ec333
Allow enabling preposted receives with build-time flag. This is potentially an improvement for small/medium sized messages, but may require more tuning of parameters. This is off by default still: https://github.com/UIUC-PPL/charm/commit/868e39ad0738dbb3a32cca651919819cd1064a10
Add MPI_Info assertion on Charm communicator that Charm does not require MPI msg ordering. If an MPI implementation optimizes for this, it may exploit it, but no known implementations optimize for this yet: https://github.com/UIUC-PPL/charm/commit/cb4d760c4eaf478d80e2873e4dfd243933042744
Use MPI-3 matching Mprobe/Mrev functions. This potentially decreases MPI queue access times, but it was found to be implemented incorrectly in multiple MPI implementations so we had to revert it for correctness. Also, since we are almost always doing wildcard receives our MPI queue access times are actually minimal since we just take whatever is at the head of the queue: https://github.com/UIUC-PPL/charm/commit/f7fbaaaae1088ee65988c1345203da3ed55abcc4


Bundler: Platform is wrongly removed

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
Bundler
Package manager version
Bundler 2.4.10
Language version
Ruby 3.2
Manifest location and content before the Dependabot update
https://github.com/Shopify/ruby-lsp/blob/main/Gemfile
dependabot.yml content
https://github.com/Shopify/ruby-lsp/blob/main/.github/dependabot.yml
Updated dependency
sorbet and releted gems
What you expected to see, versus what you actually saw
Dependabot is removing the x64-mingw-ucrt platform for some reason. It should not.
Native package manager behavior
Platforms are unchanged.
Images of the diff or a link to the PR, issue, or logs
https://github.com/Shopify/ruby-lsp/pull/1191/files
Smallest manifest that reproduces the issue
No response

Thanks for reporting!
This is an upstream regression. I just merged the fix at https://github.com/rubygems/rubygems/pull/7170. Will release it and pick up the fix in Dependabot as soon as possible.

https://github.com/rubygems/rubygems/pull/7170 will actually make it remove x64-mingw32 as well - as that's what the original code was intended to do. It's supposed to remove both x64-mingw-ucrt and x64-mingw32 as they are not valid platforms since sorbet-static doesn't support them, but a bug made it so only one was being removed.
I suppose it depends what the mingw platforms are supposed to be targetting here. If the idea of that lockfile is to support BUNDLE_WITHOUT=development, then I've separately described and reported that at https://github.com/rubygems/rubygems/issues/7169.

Oh, you're totally right, my bad!
For now this is indeed expected, so closing. if this behavior is biting you too @andyw8, feel free to chime in at https://github.com/rubygems/rubygems/issues/7169.
Once Dependabot picks up the fix I pointed to before, Dependabot will also remove x64-mingw32 as @Bo98 pointed out.


unoconv PDF: unix process error: wait for unix process: exit status 5

When using gotenberg:7 and the endpoint forms/chromium/convert/html with the additional multipart data pdfFormat=PDF/A-1a the following error ocurred (Convert HTML to PDF/A-1a):
{"level":"error","ts":1664889966.8094878,"logger":"api","msg":"convert HTML to PDF: convert PDF: convert PDF to 'PDF/A-1a' with multi PDF engines: convert PDF to 'PDF/A-1a' with PDFcpu: method not available; convert PDF to 'PDF/A-1a' with PDFtk: method not available; convert PDF to 'PDF/A-1a' with QPDF: method not available; convert PDF to 'PDF/A-1a' with unoconv: unoconv PDF: unix process error: wait for unix process: exit status 5","trace":"a4b50916-7779-4b54-b14a-883469dc98dc","remote_ip":"<IP_ADDRESS>","host":"converter:3000","uri":"/forms/chromium/convert/html","method":"POST","path":"/forms/chromium/convert/html","referer":"","user_agent":"ReactorNetty/1.0.17","status":500,"latency":2274155848,"latency_human":"2.274155848s","bytes_in":-1,"bytes_out":21}

Especially the part: convert PDF to 'PDF/A-1a' with unoconv: unoconv PDF: unix process error: wait for unix process: exit status 5
This happened using a gotenberg container, which was running for about 3 weeks in total. I guess the unoconv-service / listener failed / crashed and didn't recover? Either way, this shouldn't be the case I guess.

Small status update: Seems like this is no issue with long-term runs only, but happens on freshly restarted containers after 2 hours now as well :/

Hello @PierreSchwang,
Do you use the default value for --uno-listener-restart-threshold (i.e., 10)? You may try to reduce this value so that the long-running LibreOffice instances are restarted more often or go stateless with --uno-listener-restart-threshold=0.

Hello @PierreSchwang,
Do you use the default value for --uno-listener-restart-threshold (i.e., 10)? You may try to reduce this value so that the long-running LibreOffice instances are restarted more often or go stateless with --uno-listener-restart-threshold=0.

Hi - No, we're running gotenberg with the default configuration. I guess using the stateless mode isn't that good of an idea, as this would increase the time for the conversion tremendously?

It depends on your use case 😊 for instance, batch conversions may actually finish quicker, because a long-running instance cannot handle concurrent conversions. Of course one could mitigate this by spawning multiple Gotenberg instances, but you get the idea.

The instance is only reachable using a proxy, but handles many single operations rather than few batches :/

What does the health check returns in your case? https://gotenberg.dev/docs/modules/api#health

Reproduced it on a different machine, health returns ok-results:
{"status":"up","details":{"uno":{"status":"up","timestamp":"2022-10-05T20:08:46.2204444Z"}}}

Can be reproduced by running gotenberg without any additional configuration, and calling the chromium-convert enpoint (basically trigger the PDF/A-1a conversion):
curl \
--request POST 'http://localhost:3000/forms/chromium/convert/html' \
--form<EMAIL_ADDRESS>\
--form 'pdfFormat=@"PDF/A-1a"' \
-o my.pdf

At the beginning that will work flawlessly, after the container ran without any commands for a bit, that'll fail

Our current workaround is, by disabling the pdf-A conversion.
I reproduced it after about half an hour without commands, iirc

Hi @PierreSchwang, same problem here with version 7.6.1.
Process:

Up the instance of docker
Convert files with call /forms/libreoffice/convert
File pdf generated
Call /health, API up
Convert files with call /forms/libreoffice/convert
File pdf generated
Call /health, API up
Wait 10 minutes
Convert with call /forms/libreoffice/convert
Error convert to PDF: unoconv PDF: unix process error: wait for unix process: exit status 5
Call /health, API up
restart the instance
Convert with /forms/libreoffice/convert
File pdf generated

I don't understand. Ater few minutes without activity, the error appear without PDF/A-1a.

@ytilotti thanks for the details. Maybe the garbage collector is the culprit here, as it deletes files in /tmp after some time (i.e., if they are older than the allowed process time of a request). That being said, I've tested it many time and it did no cause any issues. Maybe something has changed with the latest version of LibreOffice.
In the meantime, could you go stateless? (--uno-listener-restart-threshold=0). I'm confident it will solve the issue, even if performance will drop.

@gulien I'm on already in testing --uno-listener-restart-threshold=0. Current in waiting period of 10 minutes :)

@ytilotti Your feedback was based on the stateless mode? If that's the case, it looks like the latest version of LibreOffice is the culprit...

My feedback was without stateless mode. After new test with stateless mode (--uno-listener-restart-threshold=0) it's working. More slow but working.

I also have this issue, i cannot convert epub files.
docker run --rm -p 3000:3000 gotenberg/gotenberg
curl -X POST 'http://localhost:3042/forms/libreoffice/convert' -F<EMAIL_ADDRESS>-o test.pdf

Results in the error message:
{"level":"error","ts":1667908795.8060749,"logger":"api","msg":"convert to PDF: unoconv PDF: unix process error: wait for unix process: exit status 5","trace":"0f13fdf3-7067-475b-b0ca-0e2b260300aa","remote_ip":"<IP_ADDRESS>","host":"localhost:3042","uri":"/forms/libreoffice/convert","method":"POST","path":"/forms/libreoffice/convert","referer":"","user_agent":"curl/7.86.0","status":500,"latency":136665529,"latency_human":"136.665529ms","bytes_in":886127,"bytes_out":21}

I have tried many epub files, the one in this example was taken from here.

The issue is still occuring with the latest 7.7.1

@PhE @cars10  @PierreSchwang @ytilotti  could you try the image gulnap/gotenberg:libreofficefix? It's using a downgraded version of LibreOffice (7.0.4) but with the Gotenberg 7.7.1 codebase.

@PhE @cars10  @PierreSchwang @ytilotti  could you try the image gulnap/gotenberg:libreofficefix? It's using a downgraded version of LibreOffice (7.0.4) but with the Gotenberg 7.7.1 codebase.

Hi! After quick testing with multiple requests with a bit of a time difference (13:54, 14:24, 14:44) it seems to work so far. Do you know the culprit?
I'll try to test further but looks promising so far, thanks!

@PierreSchwang Looks like newer versions of LibreOffice are the culprit (or the related Debian packages).

@PierreSchwang Looks like newer versions of LibreOffice are the culprit (or the related Debian packages).

Would be great to know the commit which introduced the (seemingly) bug. Was searching through gerrit for a bit but haven't found anything. Tho I'm not sure if it may be changed due to a mistake in implementing another feature.

Would be great to know the commit which introduced the (seemingly) bug.

👍 yep, downgrading is indeed a temporary solution.

Release 7.7.2 is now available with the fix. Please open a new issue if the problem still persist 😄

Release 7.7.2 is now available with the fix. Please open a new issue if the problem still persist 😄

Deployed the update on our dev system and will monitor the behavior. I'll keep you updated!

Thanks @PierreSchwang!

Thanks @ytilotti!

An issue was sended to LibreOffice? 7.0.4 seems to be old.

Yes and no, the latest version available in Debian 11 is 7.4.3, so no so far away from 7.0.4. I wonder if it’s an issue with LibreOffice or the Debian package from backports channel.

Maybe related to https://bugs.documentfoundation.org/show_bug.cgi?id=146807
A crash could explain why the document is Null when attempting to load via unoconv. But I can't be sure sadly - If anyone want's to investigate further into that, I'd be glad. Will try to research and test further with 7.7.1 - maybe with "bisecting" there are new information to be found :/

I did a bit of research and came to the following result with a simple binary search:

Working
Not Working
Release Date

7.7.1 (<IP_ADDRESS>)
03.12.2022

7.6.1 (<IP_ADDRESS> 40(Build:2))
03.10.2022

7.6.0 (<IP_ADDRESS> 30(Build:2))

01.09.2022

7.5.4 (<IP_ADDRESS>)

7.5.3 (<IP_ADDRESS>)

07.06.2022

The version in brackets represents the used LibreOffice version in each gotenberg version.
That might explain the sudden issue on our end, as we used gotenberg/gotenberg:7 as the image. I've created this issue on the 04th of October, and the update with the broken version of LO was released on the 03rd of October. Our CI/CD pipeline most certainly did a docker-compose pull which updated to the named version and explains the sudden error(s).
So, basically - the culprit is on of 1.185 commits between v<IP_ADDRESS> and v<IP_ADDRESS> (https://github.com/LibreOffice/core/compare/libreoffice-<IP_ADDRESS>...libreoffice-<IP_ADDRESS>) - fun to debug tbh


Missing spaces

Maybe a line break is not so bad either, or as a small table. I'm not very good at graphics, but the space is missing.

The text will be replaced with icons. You may see that in the mockup on Figma. The text will be used as android:contentDescription for users with impairments (e.g. blind users). @arafaatqureshi will finish it soon and it will be updated in the next release.

@amarradi this was just the functionality check, will be replaced with the icons and contentDescription in the next push InshaAllah.

Ah okay i understand


Do api supports  the file thumbnail?

How do I use api to get the image's thumbnail

This issue tracker is for issues related to the sample code. For general Q&A please see the support page: https://developers.google.com/drive/android/support


[mmlspark] JVM crash caused by LGBM_BoosterSaveModelToStringSWIG

Environment info
Operating System: Windows 10 x64, version 10.0.18362.388
Java: Java HotSpot(TM) 64-Bit Server VM (build 25.221-b11, mixed mode)
CPU/GPU model: AMD Ryzen 7 2700X
LightGBM version or commit hash:

"com.microsoft.ml.spark" %% "mmlspark" % "0.18.1"
"com.microsoft.ml.lightgbm" % "lightgbmlib" % "2.2.350" via https://github.com/Azure/mmlspark/blob/v0.18.1/build.sbt#L27

Error message
[info] [LightGBM] [Warning] Starting from the 2.1.2 version, default value for the "boost_from_average" parameter in "binary" objective is true.
[info] This may cause significantly different results comparing to the previous versions of LightGBM.
[info] Try to set boost_from_average=false, if your old models produce bad results
[info] [LightGBM] [Info] Number of positive: 232, number of negative: 8245
[info] [LightGBM] [Info] Total Bins 5466
[info] [LightGBM] [Info] Number of data: 8477, number of used features: 41
[info] [LightGBM] [Info] [binary:BoostFromScore]: pavg=0.027368 -> initscore=-3.570625
[info] [LightGBM] [Info] Start training from score -3.570625
[info] #
[info] # A fatal error has been detected by the Java Runtime Environment:
[info] #
[info] #  EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) at pc=0x00007ff8eee3a839, pid=18188, tid=0x0000000000003da4
[info] #
[info] # JRE version: Java(TM) SE Runtime Environment (8.0_221-b11) (build 1.8.0_221-b11)
[info] # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.221-b11 mixed mode windows-amd64 compressed oops)
[info] # Problematic frame:
[info] # C  [KERNELBASE.dll+0x3a839]
[info] #
[info] # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
[info] #
[info] # An error report file with more information is saved as:
[info] # C:\repos\SparkPlayground\hs_err_pid18188.log
[info] #
[info] # If you would like to submit a bug report, please visit:
[info] #   http://bugreport.java.com/bugreport/crash.jsp
[info] # The crash happened outside the Java Virtual Machine in native code.
[info] # See problematic frame for where to report the bug.
[info] #
[error] Nonzero exit code returned from runner: 1
[error] (Compile / runMain) Nonzero exit code returned from runner: 1
[error] Total time: 27 s, completed Oct 9, 2019 4:09:47 AM

Link to hs_err_pid18188.log: https://pastebin.com/8TgKB61c
Reproducible examples

Steps to reproduce

Clone https://github.com/REASY/spark-playground/
Switch to branch lightgbm-0.18.1-crash-repro
Save to the local disk input file part-00000-711560fe-8fdd-4777-a379-b52996fd212d-c000.gz.parquet: https://drive.google.com/open?id=1iE2ptX9O4x5vn1KjDdZYVuSIuLgzyLbJ
Replace the path in https://github.com/REASY/spark-playground/blob/lightgbm-0.18.1-crash-repro/src/main/scala/spark/playground/LigthGbmUsage.scala#L13 by your local path (sorry for this, it could be done as app args)
Run sbt "runMain spark.playground.LigthGbmUsage" in console (expecting that you have installed SBT
From time to time it crashes

@imatiach-msft Please take a look

@REASY @StrikerRUS sorry about the trouble you are having.  Indeed, this was a bug and it should already be fixed with this PR:
https://github.com/microsoft/LightGBM/pull/2364
This issue should no longer appear in the latest master branch, although it is still an issue in 0.18.1 since it doesn't include the fix yet.  Sorry about the inconvenience.

also see the corresponding mmlspark fix:
https://github.com/Azure/mmlspark/pull/676

Thanks, @imatiach-msft. I'll try with snapshot version!

@REASY Glad to hear that your problem has been solved! Thank you for the feedback!
@imatiach-msft Thanks a lot!


Update to use GITHUB_STATE

Fixes

(hopefully) Fixes #1937 by @obulat
Description

This PR is replacing deprecated command to use GITHUB_STATE.
Testing Instructions

There should be no warnings about deprecated set-state command. I'm not sure how to check if this doesn't break the actual workflow, though :)
Checklist

[ ] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Closing this PR as it's using an incorrect way of gettingGITHUB_STATE from a python script. Also, most of the warnings seem to come from setup_node action, which has recently merged the PR fixing it, but it's not released yet.


As a USER I would like the ability to select an answer from a pre-defined set of answers

Based on https://github.com/britishcouncil/react-quiz/pull/1. To see what's changed, [see comparison](https://github.com/britishcouncil/react-quiz/compare/project-setup...solas-5208-select-answer?expand=1
).
Please don't review the styling as this component is "styleless". We apply some styling in the included demo app for testing purposes. There's an upcoming story to enable styling the quiz (e.g. using the British Council SUI CSS library).
To start demo app:
npm start

To run unit tests:
npm test

Internal JIRA story

Hiya @robinedman I had to clone the repo first, but all went fine and it looks as expected. 👍

npm test

Reviewing this one too ...

@robinedman I checked on deferents browsers such as Chrome, Firefox, Safari and IE9 above. It looks good. Also I checked on couple of devices as ipads and smartphones. 👍

Looks good 👍


No brackets needed when setting UsageGuidelinesUrl

We don't need angle brackets at Step 4 to set UsageGuidelinesUrl. When we enclosed the usage guideline value in angle brackets, the link did not work.
Page Title: Azure Active Directory cmdlets for configuring group settings
URL: https://docs.microsoft.com/en-us/azure/active-directory/active-directory-accessmanagement-groups-settings-cmdlets
4.Then update the usage guideline value:
$setting["UsageGuidelinesUrl"] = "https://guideline.com"

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

ID: 4cd7a703-534a-5fbd-6470-5d29bf512fd2
Version Independent ID: 4f70ed16-6a1c-c0be-3c5e-d56e1b7c7275
Content: Configure group settings using PowerShell in Azure Active Directory
Content Source: articles/active-directory/active-directory-accessmanagement-groups-settings-cmdlets.md
Service: active-directory
GitHub Login: @curtand
Microsoft Alias: curtand

@naminakao Please note that the value of UsageGuidelinesURL i.e. URL is not with angular bracket. The setting to which value is assigned follow that format - $settings["SETTING NAME"] = "value". Once you assign URL as value to  UsageGuidelinesURL it works fine. e.g.
$settings["GuestUsageGuidelinesUrl"] = "https://domain.sharepoint.com/sites/intranet/Pages/Groups-Guest-Usage-Guidelines.aspx"

Please delete < and > from the command sample on Step4.

@naminakao Thanks again for pointing this out. The PR for the fix has been created and it will be merged soon. Please open a new issue to let us know if there is something else that we can help you with.


Unnecessary request information sent to console and logs

Regarding the following commit: 8ff831e1a9b99ce1f43b5dd96b8ed878be41787b
The change has led to unnecessary logs. With Django's mail_admins() enabled, it causes double the emails sent, and even sends an email for every 4xx error.
Console:

Email received (empty traceback):

@horkong I will look into it

@horkong fix will be available on next release

@horkong check: https://github.com/eadwinCode/django-ninja-extra/releases/tag/0.15.6
thanks


Multidimensional queries support for composite queries

Currently composite indexes support range queries in which all field values are equal and only last one is different.
The reason of such behavior is the way how we concatenate keys. key1 + key2 + key3.
But if  we will interleaving binary representations of keys http://en.wikipedia.org/wiki/Z-order_(curve) we can implement multidimensional queries support.
It is relatively easy to do because can be implemented on the base of SB-Tree by providing new serializers for composite keys and comparator + changes in SQL engine.

It would be good to see more advanced geo spatial queries like bounding box, radius etc... e.g. PostGIS/Geocouch features.
This is likely a big undertaking, but good to put out to see what level of support there is.

Hi guys, Is there any progress on this?

Hi, not yet. We are concentrated now multi core scalability.
On Fri, Oct 2, 2015 at 8:06 AM Yaismel Miranda<EMAIL_ADDRESS>wrote:

Hi guys, Is there any progress on this?
—
Reply to this email directly or view it on GitHub
https://github.com/orientechnologies/orientdb/issues/1288#issuecomment-144922547
.


Bug in the docs

I think the documentation has become somewhat inaccurate:
const userEventStore = new EventStore({
  eventStoreId: 'USERS',
  eventTypes: [
    userCreatedEventType,
    userRemovedEventType,
    ...
  ],
  reducer: usersReducer,
});

this seems to be written as this now:
const userEventStore = new EventStore({
  eventStoreId: 'USERS',
  eventStoreEvents: [
    userCreatedEventType,
    userRemovedEventType,
    ...
  ],
  reduce: usersReducer,
});

There's also an issue on this page: https://github.com/castore-dev/castore/blob/main/packages/inmemory-event-storage-adapter/README.md
import { DynamoDbEventStorageAdapter } from '@castore/inmemory-event-storage-adapter';

should become
import { InMemoryStorageAdapter } from '@castore/inmemory-event-storage-adapter';

Hi @neochief ! Thanks for the feedback, will fix this ASAP :)

Fixed by https://github.com/castore-dev/castore/pull/32


failed to load the Compile library

I tried to save the Compile library from f3 in tvm/topi/tests/python/test_topi_depthwise_conv2d.py
base_path="/home/aries/tvm/apps/test/lib"
dylib_path = os.path.join(base_path, "test_relu.so")
f3.export_library(dylib_path)
syslib_path = os.path.join (base_path, "test_relu.o")
f3.save (syslib_path)
And it works well.
But when I want to try ./run_example.sh to prove the saved .so files work well.
I edited the makefile:
#The code library built by TVM
#lib/test_addone_sys.o: prepare_test_libs.py
#python prepare_test_libs.py
Because I want to use the .so and .o files outputted by f3.
And actually, My Cuda is enabled. Why?  [17:47:14] /home/aries/tvm/dmlc-core/include/dmlc/./logging.h:308: [17:47:14] ../../src/runtime/module_util.cc:31: Check failed: f != nullptr Loader of cuda(module.loadbinary_cuda) is not presented.
~/tvm/apps/test$ ./run_example.sh
Build the libraries..
g++ -std=c++11 -O2 -fPIC -I/home/aries/tvm/include -I/home/aries/tvm/dmlc-core/include -I/home/aries/tvm/dlpack/include  -o lib/cpp_deploy_pack  cpp_deploy.cc lib/test_addone_sys.o lib/libtvm_runtime_pack.o -L/home/aries/tvm/lib -ldl -lpthread
g++ -std=c++11 -O2 -fPIC -I/home/aries/tvm/include -I/home/aries/tvm/dmlc-core/include -I/home/aries/tvm/dlpack/include  -o lib/cpp_deploy_normal  cpp_deploy.cc lib/test_addone_sys.o -L/home/aries/tvm/lib -ldl -lpthread -ltvm_runtime
Run the example
Run the deployment with all in one packed library...
[17:47:14] /home/aries/tvm/dmlc-core/include/dmlc/./logging.h:308: [17:47:14] ../../src/runtime/module_util.cc:31: Check failed: f != nullptr Loader of cuda(module.loadbinary_cuda) is not presented.
Stack trace returned 7 entries:
[bt] (0) lib/cpp_deploy_pack() [0x4076d9]
[bt] (1) lib/cpp_deploy_pack() [0x418780]
[bt] (2) lib/cpp_deploy_pack() [0x418bdc]
[bt] (3) lib/cpp_deploy_pack() [0x4172e6]
[bt] (4) lib/cpp_deploy_pack() [0x404612]
[bt] (5) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fc7afb70830]
[bt] (6) lib/cpp_deploy_pack() [0x405929]
terminate called after throwing an instance of 'dmlc::Error'
what():  [17:47:14] ../../src/runtime/module_util.cc:31: Check failed: f != nullptr Loader of cuda(module.loadbinary_cuda) is not presented.
Stack trace returned 7 entries:
[bt] (0) lib/cpp_deploy_pack() [0x4076d9]
[bt] (1) lib/cpp_deploy_pack() [0x418780]
[bt] (2) lib/cpp_deploy_pack() [0x418bdc]
[bt] (3) lib/cpp_deploy_pack() [0x4172e6]
[bt] (4) lib/cpp_deploy_pack() [0x404612]
[bt] (5) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fc7afb70830]
[bt] (6) lib/cpp_deploy_pack() [0x405929]
./run_example.sh: line 10: 16001 Aborted                 (core dumped) lib/cpp_deploy_pack
Run the deployment with all in normal library...
[17:47:14] cpp_deploy.cc:58: Verify dynamic loading from test_addone_dll.so
[17:47:14] /home/aries/tvm/dmlc-core/include/dmlc/./logging.h:308: [17:47:14] cpp_deploy.cc:14: Check failed: f != nullptr
Stack trace returned 4 entries:
[bt] (0) lib/cpp_deploy_normal() [0x403751]
[bt] (1) lib/cpp_deploy_normal() [0x402095]
[bt] (2) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f90d6ce0830]
[bt] (3) lib/cpp_deploy_normal() [0x4024a9]
terminate called after throwing an instance of 'dmlc::Error'
what():  [17:47:14] cpp_deploy.cc:14: Check failed: f != nullptr
Stack trace returned 4 entries:
[bt] (0) lib/cpp_deploy_normal() [0x403751]
[bt] (1) lib/cpp_deploy_normal() [0x402095]
[bt] (2) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f90d6ce0830]
[bt] (3) lib/cpp_deploy_normal() [0x4024a9]
./run_example.sh: line 13: 16003 Aborted                 (core dumped) lib/cpp_deploy_normal

I think the problem is the difference between:
tvm.build(s, [A, B], "llvm --system-lib", name="addonesys")
f3 = tvm.build(s3, [Input, Filter, Scale, Shift, Relu], device)
But I cannot change device to be "llvm --system-lib".
Traceback (most recent call last):
File "/home/aries/tvm/topi/tests/python/test_topi_depthwise_conv2d.py", line 221, in
test_depthwise_conv2d()
File "/home/aries/tvm/topi/tests/python/test_topi_depthwise_conv2d.py", line 202, in test_depthwise_conv2d
depthwise_conv2d_with_workload_nchw(1, 728, 64, 1, 3, 1, "SAME")
File "/home/aries/tvm/topi/tests/python/test_topi_depthwise_conv2d.py", line 110, in depthwise_conv2d_with_workload_nchw
check_device("cuda")
File "/home/aries/tvm/topi/tests/python/test_topi_depthwise_conv2d.py", line 42, in check_device
f3 = tvm.build(s3, [Input, Filter, Scale, Shift, Relu], "llvm --system-lib")
File "/home/aries/tvm/python/tvm/build_module.py", line 342, in build
assert not fdevice
AssertionError
What else can I do ?

update the questions in new issue. close this


document fee payment and event queue for place order

Can you send this into v3.3.0 branch? If I merge into main it will mess up the line numbers for people debugging issues on mainnet

ok added to v3.3.0


Docs: Bad links for issues and contributing guidelines in README

Link issues:

The link to submit an issue still goes to the old repo, that this repo was preivously a part of.
The link to the contributing guidelines is not defined, so it just says [contrib] next to the link text.

Steps to reproduce

Look at the end of the README and try to follow either of the two aforementioned links

I have a branch with fixes for these links ready to go. I just noticed that the contributing guidelines say to submit an issue and discuss solutions first.

Feel free to send a pr. I recently moved this package into its own repository and missed some of those links.


'whereHas' and 'has' seem to ignore $morphClass and morphMap

Laravel Version: 5.3 (worked in 5.2)
PHP Version: 7.0.0

Description:
whereHas ignores morphClass and morphMap
Steps To Reproduce:
Clone https://bitbucket.org/skintillion/morphclass
Run migration and seed
Open page
Should see "Company" instead of "App\Models\Company"
This worked in 5.2

I understand that morphMap has been removed and you should use
    Relation::morphMap([
        'Company' => App\Models\Company::class,
    ]);

But that doesn't work either.

You HAVE to have  a \ before the class.
Relation::morphMap([
'Company' => \App\Models\Company::class,
]);

Documentation should be updated.


Complete SDK usage example

refer to examples in qingstor-sdk-go  and qingstor-sdk-python

examples completed @ #105


Recognizing objects using adaptive thresholding or Canny edge detection

I am doing object recognition using adaptive thresholding or Canny edge detection. Both work without problems, but in the case of adaptive binarization, a lot of noise occurs, and in the case of Canny edge, when received in real time, the edge line is disconnected. I want to do object recognition (buoy, tree, etc.) neatly using these two methods. Can you give me some advice on how to do it neatly?

Hi! Thanks for using VRX. Generally speaking, this issue tracker is for reporting bugs or requesting features for the VRX environment code or documentation. For advice about solving autonomy problems in simulation, you may want to try posting on the Gazebo Community forum. For suggestions specifically about these two computer vision techniques, you might also try asking on the opencv forum.
Unofficially, in my personal opinion: it's very challenging to get robust object recognition working with these techniques!


Knative v0.31.0

In order to use ConfigMap watcher for adapters logging configuration hot-reload we need to update Knative to v0.31.0.
[!] This PR sets Kubernetes minimal required version to v1.22

/hold
Controller will crash due to the k8s version requirement. I leave it up to @sameersbn to unhold when our clusters are ready.

(I'm writing this here because I don't know where else to write it)
One important note about enabling ConfigMap watchers in all components by default:
This requires explicitly granting components access to the Kubernetes API using a ClusterRole associated with their ServiceAccount (via a RoleBinding).
ServiceAccounts are dynamically created by the TriggerMesh controller in the RBAC reconciler, so that part is already covered.
However, the RoleBinding can only be created if the corresponding ClusterRole exists.

Prior to #133 (and corresponding PR) we used to maintain a bunch of empty ClusterRoles corresponding to each TriggerMesh component type, just so that we could bind ServiceAccounts to something. This was tedious.
Luckily, we isolated the minority of components which actually needed a ClusterRole (multi-tenant adapters), and got rid of the dozens of other ClusterRoles.
With this story, we might need to get back to the pre-#133 status of having one ClusterRole per component type, with an added twist: each of them needs permissions to list and watch ConfigMaps.
Nothing complicated, but definitely maintenance heavy without proper YAML tooling in the long run. So before jumping head first, I would question whether "I want to change the log level without restarting Pods" really is a strong enough incentive for this.
I have a feeling that most users will be happy just setting loglevel.foo-adapter: debug centrally, inside triggermesh/config-logging. How many users expressed the will to repeatedly switch from one log level to another at runtime? Creating a new ConfigMap for each component just to be able to adjust the logger's config is also not that intuitive.

Alternative to maintaining a bunch of identical ClusterRoles: ship a single triggermesh-config-reader ClusterRole with TriggerMesh and programmatically bind all ServiceAccounts to it in the RBAC reconciler (regardless of multi-tenancy).

It was mentioned in the "TriggerMesh Logging" document that config hot-reload is optional as switching between levels is expected to happen mostly in the integration development phase where pod restart is not a problem. I'm fine with leaving it out of the scope although I believe that the introduction of the triggermesh-config-reader role and triggermesh-specific configmap is probably a question of time.

Controller will crash due to the k8s version requirement. I leave it up to @sameersbn to unhold when our clusters are ready.

@tzununbekov @antoineco please note that staging has been updated to k8s 1.22 and knative 1.4.

I believe that the introduction of the triggermesh-config-reader role and triggermesh-specific configmap is probably a question of time.

@tzununbekov @odacremolbap FYI once #924 gets merged all receive adapters will automatically be granted read access to ConfigMaps, so components can start injecting ConfigMapWatcher via the shared main and things will just work™.


[Docs]: Query/API Response Larger Than 5 MB

https://app.intercom.com/a/apps/y10e7138/inbox/inbox/conversation/164629100140461#part_id=comment-164629100140461-16197088722

Create a new page (Query Errors) >> Troubleshooting and add details.


Create Touch control GUI

Add the actual images for a gamepad (with button sensors that are touch or click sensitive)

Create GUI with these controls built in - closing as complete


help: Could it run in simulator without entitlements from Apple?

I have not got the required entitlements from apple. So I tried to run it in simulator. However, It seems httpproxy extenstion does not run.

啊，好像是中国人，我就是想问，不去找苹果要entitlements的话，能不能在模拟器里运行起来，我目前的尝试是失败的。


Improve Reference Window styling

Its a bit under styled and there is a lag when the window first renders


Convert YouTube errors into text, to improve error reporting.

To give a clear error message on screen in video.js, the error code needs to be converted to a string.

Awesome thank you! (sorry about the delay)


does not add a webhook to github

It doesn't add a webhook to my github repository when I select my project repo to sync with linear.app, it loads, but when I go back to github I don't see a webhook added.
synclinear.com

GitHub settings

PS: The first one did add a webhook, but then I deleted it and re-synced my repo, but this time it no longer added a webhook.

Thanks for raising this @abrahamcalsin. To clarify, the first one added a webhook, meaning Linear or GitHub the first time?
Also, do you know if there was an error in the console? No worries if not
Will try to replicate this and push a fix

Thanks for raising this bug @abrahamcalsin
To clarify, when you say "the first one added a webhook", do you mean Linear or GitHub had the webhook?
Also, did you manually delete the GH webhook by chance?
These will help to troubleshoot then push a fix!

Well, the first time, it added me a webhook in github.
More on linear added me as an Authorized Application just that.
Yes, in github the webhook I deleted it manually, and when I try to sync again it doesn't recognize that I deleted it and that's why it doesn't add me a new webhook.

Thanks for clarifying, @abrahamcalsin. I'll look into adding a guardrail for manually-deleted webhooks.
In the meantime, to fix your sync, feel free to manually add the webhook back:

Endpoint: https://synclinear.com/api
Content type: application/json
SSL verification: Enable
Events: Let me select individual events -> issues, issue comments, labels

Please let me know if that doesn't work!

Thanks for clarifying, @abrahamcalsin. I'll look into adding a guardrail for manually-deleted webhooks.
In the meantime, to fix your sync, feel free to manually add the webhook back:

Endpoint: https://synclinear.com/api
Content type: application/json
SSL verification: Enable
Events: Let me select individual events -> issues, issue comments, labels

Please let me know if that doesn't work!

Well I tried to manually add a webhook and I get a 500 error, so it doesn't work.
Could it be that I am missing the secret?

I met exactly the same issue here 🙌 Thanks for the authors looking into it

@tedspare
I had the same problem.
Webhooks were added when first synchronizing.   They will not be added when manually removed and then synchronized again.
Secret is missing on GitHub if I fill it in manually, so how do you get secret or can you automatically add it again when synchronizing after detecting the deleted webhooks?


[ISSUE #4904]Optimize store module test cases to reduce execution time

Make sure set the target branch to develop
What is the purpose of the change
close #4904
Brief changelog
-Optimize store module test cases to reduce execution time
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #4908 (53e6aa0) into develop (2a46dbe) will decrease coverage by 0.16%.
The diff coverage is n/a.

:exclamation: Current head 53e6aa0 differs from pull request most recent head 9fee8fa. Consider uploading reports for the commit 9fee8fa to get more accurate results

@@              Coverage Diff              @@
##             develop    #4908      +/-   ##
=============================================
- Coverage      43.32%   43.15%   -0.17%
+ Complexity      7707     7676      -31
=============================================
  Files            994      994
  Lines          68938    68938
  Branches        9132     9132
=============================================
- Hits           29865    29751     -114
- Misses         35330    35450     +120
+ Partials        3743     3737       -6

Impacted Files
Coverage Δ

...a/org/apache/rocketmq/store/StoreStatsService.java
39.22% <0.00%> (-10.50%)
:arrow_down:

...apache/rocketmq/store/queue/ConsumeQueueStore.java
53.41% <0.00%> (-5.56%)
:arrow_down:

...etmq/namesrv/routeinfo/BatchUnRegisterService.java
94.73% <0.00%> (-5.27%)
:arrow_down:

...e/rocketmq/store/ha/autoswitch/EpochFileCache.java
77.08% <0.00%> (-4.17%)
:arrow_down:

...ache/rocketmq/store/AllocateMappedFileService.java
39.28% <0.00%> (-2.39%)
:arrow_down:

...org/apache/rocketmq/store/DefaultMessageStore.java
53.40% <0.00%> (-2.06%)
:arrow_down:

...mq/store/ha/autoswitch/AutoSwitchHAConnection.java
73.02% <0.00%> (-1.91%)
:arrow_down:

...ava/org/apache/rocketmq/filter/util/BitsArray.java
58.11% <0.00%> (-1.71%)
:arrow_down:

...he/rocketmq/client/trace/AsyncTraceDispatcher.java
81.42% <0.00%> (-1.43%)
:arrow_down:

...mq/client/impl/consumer/RebalanceLitePullImpl.java
69.86% <0.00%> (-1.37%)
:arrow_down:

... and 18 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Removed unnecessary SemaphoreSlims

Fixes https://github.com/dotnet/aspnetcore/issues/22043
The underlying issue with the ordering was fixed and we no longer need this.

Has the real fix made it into VSMaster yet?

Has the real fix made it into VSMaster yet?

Wasn't the ordering issue fixed a long time ago?

Wasn't the ordering issue fixed a long time ago?

No I think it was recent.

Verified that the fix for the underlying issue is in VSMaster already.


Redesign the Leaderboard to Improve Performance

Start with investigating improvement to current use of getstats, and go from there.
Discuss with @ewang2002

Changed the flow of getstats so that when the userdoc is already available, use the logs from that doc rather than polling from mongo each time.
/leaderboard has the userdocs available and uses this abbreviated getStatsWithDoc.
/stats uses a helper getStats() that obtains the userdoc and then calls the abbreviated getStatsWithDoc.


[Automation] BMC driver version info

Every test run should log the version at least to differentiate what test result the log from.
This also will helpful to populate the database field from the log.

Pre requisite for
https://github.com/openbmc/openbmc-test-automation/issues/217


[feature] make a sideload app to boot in second or the first ios

I don't understand could you explain Better please

like a sideloaded app that allow you to boot to second ios

on both ios

instead of use --boot command on mac/linux you can so i straight from the device


Commonize tagging for hash and sort aggregates

Currently hash and sort aggregates have completely separate code for tagging the plan despite both being translated to use GpuHashAggregateExec as the backend GPU implementation.
This updates the tagging code to be common and also cleans up the code (using withResource, proper indentation in places, etc.).  Happy to separate out some of these changes if desired.
Notable changes include the removal of some tagging restrictions for sort aggregate since they weren't there in hash aggregate.  String literals are no longer restricted and hasNans doesn't have to be set to false for aggregations on floating point types.

build


start and stop methods have been added to Node class.

start and stop methods have been added to Node class.
Description
Node class has been extended with methods start and stop for more convenient usage of Node objects

Codecov Report

Merging #1364 into trunk will decrease coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##            trunk    #1364      +/-   ##
==========================================
- Coverage   86.34%   86.34%   -0.01%
==========================================
  Files         372      372
  Lines       76156    76160       +4
  Branches     6971     6971
==========================================
+ Hits        65755    65757       +2
- Misses       7605     7607       +2
  Partials     2796     2796

Impacted Files
Coverage Δ

libcloud/compute/base.py
92.77% <50%> (-0.63%)
:arrow_down:

Continue to review full report at Codecov.

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

Thank for the contribution, this has now been superseded and resolved by changes in #1375.


.zshenv doesn't get sourced on a tty

Please check the existing issues to make sure you're not duplicating a report.
For bug reports, please provide the following information:
In a terminal, run zimfw info and paste the output below:
kronikpillow at susanoo in ~
$ zimfw info
Zim version:  1.0.1 (previous commit is 28e4345)
ZIM_HOME:     /home/kronikpillow/.config/zsh/.zim
Zsh version:  5.7.1
System info:  Linux susanoo 5.4.10-1-ck-ivybridge #1 SMP PREEMPT Thu, 09 Jan 2020 21:32:48 +0000 x86_64 GNU/Linux

gist of .zimrc: the default one, no modifications
gist of .zshrc: the default one, no modifications

Description
I installed the latest zimfw by running
curl -fsSL https://raw.githubusercontent.com/zimfw/install/master/install.zsh | zsh
when i switch to tty prompt (ctrl+alt+F2) I get the following error
[1] 1759
/home/kronikpillow/.config/zsh/.zshrc:source:90: no such file or directory: /init.zsh
/home/kronikpillow/.config/zsh/.zlogin:source:6: no such file or directory: /login_init.zsh

Steps to reproduce
install latest zimfw and switch to tty, login to your standard user
Images or other information
when I manually source .zshenv from ~/.config/zsh/.zshenv
and then manually source .zlogin and .zshrc it starts to work ... so I come to the following
for some reason, when I go to a tty, it doesn't source .zshenv even thou on my PC it sources it with no problems ...

By the error messages, it seems that $ZDOTDIR was not set in .zshenv as indicated at https://github.com/zimfw/install/blob/d4d894bbe8d67633dcdd2b1924759a272d78cb9e/src/templates/zshenv#L7
When you say that yout .zshenv lies at ~/.config/zsh/.zshenv, how is ZSH supposed to find it? It must be ~/.zshenv. Then all other files may lie inside ~/.config by setting $ZDOTDIR in .zshenv.

$ZDOTDIR was defined in my .zprofile

This thread explains the load order of the various configuration files.

I guess this can be closed? Everything mentioned in https://github.com/zimfw/zimfw/issues/365#issuecomment-619112635 is correct and explains why $ZDOTDIR needs to be set in a .zshenv file auto-loaded by zsh.


Shift + Enter creates an entirely new block on mobile

Hi there, love what you guys are doing with the editor. I really wanted to thank you for all of your hardwork.  One issue I have is Shift + Enter on mobile goes into a directly new block (the one where you get a double space and a new slash command). This doesn't seem like the case for desktop. So I'm thinking this is a bug?
Also by any chance, are draggable checkboxes possible and is that something you guys are planning to incorporate in the future?

Hi, I'm wondering how can I input Shift + Enter on mobile?
As for the draggable checkboxes, all blocks are draggable for now on desktop, what you need is use Cmd/Ctrl + left click on the block you want to drag, then you can drag it where you want.

Sorry I meant to say Shift + Return, On iOS it would be the Arrow Up + Return.
And I didn't know that in regards to the draggable. Can't wait to see it on mobile :)

I see, is there a way to fix and register the shift + return on mobile to behave the same way on desktop?

I think it depends on the native mobile keyboard, as far as I know, it doesn't support compose key bindings like Ctrl/Cmd + V, so I think for mobile, you may need an additional toolbar or some input rules to make it works.


corrupted example Image

Not a big issue but for me the example image picture.jpg could not be rendered correctly.
Eye of GNOME 3.36.3 (Ubuntu default image viewer) gives the error message:
Error reading JPEG file (Not a JPEG file: starts with 0x0a 0x0a)
The problem persists when viewing the resume.pdf with Evince 3.36.10, Libre Office Draw 7.3 and Inkscape 0.92.5.
This causes the pdf to be displayed without the image in the top right.
Weirdly enough Firefox and Chromium were able to display the pdf correctly.
It took me a while to figure out that the issue was with the picture.jpg itself and not with my pdf viewers or the LaTex environment I used.
Hope this saves someone some time.
I fixed my issue by converting the  with Gimp.
You may consider to swap out the example picture.jpg with the converted file:

Interesting. Thank you for providing a fixed file.
I created the original file with Pixelmator on macOS and did not experience any errors on macOS or Windows. Good to know that this can happen.


Strange behaviour when intersecting walls

The algorithm for the wall subivision does not work well when there are coincident walls

Fixed with d01d00cd44fd21e269b2dbc8c0ea615e76219971


Integrating Mediapipe to an existing C++ project

I am trying to use mediapipe in an  existed C++ project in Qt. I already built the "libmediapipe.so" and added it to my project. Now I am trying to run the same code which is written in demo_run_graph_main.cc in Qtcreator, but there is a problem while is running this part of the code:
 MP_RETURN_IF_ERROR(graph.AddPacketToInputStream(         kInputStream, mediapipe::Adopt(input_frame.release())                           .At(mediapipe::Timestamp(frame_timestamp_us))));
And it appears following errors:
INVALID_ARGUMENT: Graph has errors:  Calculator::Open() for node "holisticlandmarkcpu__poselandmarkcpu__posedetectioncpu__inferencecalculator__holisticlandmarkcpu__poselandmarkcpu__posedetectioncpu__InferenceCalculator" failed: ; Can't find file: mediapipe/modules/pose_detection/pose_detection.tflite Calculator::Open() for node "holisticlandmarkcpu__poselandmarkcpu__poselandmarkbyroicpu__poselandmarkmodelloader__LocalFileContentsCalculator" failed: ; Can't find file: mediapipe/modules/pose_landmark/pose_landmark_full.tflite
I would appreciate any help.

Hi I was able to integrate the mediapipe as a lib (libmediamediapipe.so) and using in c++ Qt project, while running the application I have following error while adding input packet to graph
// Send image packet into the graph.*/
size_t frame_timestamp_us = static_cast<double>(cv::getTickCount()) / static_cast<double>(cv::getTickFrequency()) * 1e6;
absl::Status st = graph.AddPacketToInputStream("input_video",
                    mediapipe::Adopt(input_frame.release()).At(mediapipe::Timestamp(frame_timestamp_us))
                );

qWarning() << "Status: " << st.ToString().c_str();

any help is appreciated?
QWARNING {} (null): Init graph:  OK
QWARNING {} (null): Run graph:  OK
QWARNING {} (null): Status: Graph has errors

I have similar issue with Selfie Segmentation model.
In my case, I wanted to change default path to my project path, actually did.
I think something in pbtxt points to tflite model.
how can i change default path to my project path?

I have similar issue with Selfie Segmentation model. In my case, I wanted to change default path to my project path, actually did. but error raised.
Calculator::Open() for node "selfiesegmentationcpu__selfiesegmentationmodelloader__LocalFileContentsCalculator" failed: ;

Can't find file: mediapipe/modules/selfie_segmentation/selfie_segmentation.tflite

I think something in pbtxt points to tflite model. how can i change default path to my project path?

I don't know if it's a good solution or not, but I could solve this error by changing the model_path  of the .tflite files in the .pbtxt files.


Templating - import with a prefix issue in various handlebar files

Description
Background Info

I am generating the SDK client as a subpackage (not a package)

e.g. root directory of the repo is mlp and the generated code is under mlp/gen/

Because this is a subpackage, I used author template to get all the handlebar files.  I then modified any .hbs files with from {{packageName}}... or import {{packageName}}... and added them to a template folder (mlp/gen_templates/)
Essentially the handlebar changes I made:

e.g. from {{packageName}}... -> from mlp.gen.src.{{packageName}}...

Handlebar Issues

After generating the SDK client, there are various scripts in the src/paths/ directory with the missing prefix (mlp.gen.src.) in the import statements
These are the the following handlebar scripts added (emphasis on paths/ as that's the issue):

These are the following paths files which are not generating properly with the prefix (mlp.gen.src.):

/paths/*/request_body/content/application_json/schema.py
paths/*/post/operation.py
paths/*/put/parameters/parameter_0/__init__.py
paths/*/put/path_parameters.py

openapi-generator version
v3.0.0
Command line used for generation
Command used to download handlebar files:
java -jar openapi-json-schema-generator-cli.jar author template -g python

Command used to generate the SDK:
java -jar openapi-json-schema-generator-cli.jar generate \
    -i mlp/openapi.yaml \
    -g python \
    -o mlp/gen \
    -t mlp/gen_templates

Suggest a fix/enhancement
After using author template to get all handlebar files, I can't find the handlebar script(s) associated with the 4 paths/ patterns described above.
Do I need to create new handlebar files for gen_templates/paths/?  Otherwise is there a better approach to tackling this problem?

Have you considered including the prefitin packageName? Why is packageName not set in your invocation?

@spacether - Very good idea!  I'll test this out today and report back here 😄

If I add the prefix mlp.gen.src to package-name as such:
java -jar openapi-json-schema-generator-cli.jar generate \
      -i mlp/openapi.yaml \
      -g python \
      -o mlp/gen \
      --package-name mlp.gen.src.mlp_client

While this fixes the import statements in the generated scripts, the pathways now look like this:

How about using mlp.gen.mlp_client as the package name? Otherwise src will appear twice.
Also the init file will be missing from mlp.gen.mlp_client and possibly the src folder and it will need to be added there. It is easier to package the generated client as it's own package in its own repo, then have your mlp repo install and use it.

@spacether - I tried mlp.gen.mlp_client as the packageName and that did not resolve the issue (mlp/gen/src/mlp/gen/mlp_client/).  I will package the generated client as its own package in its own repo then have mlp repo install and use it as a sub-package.  Thank you for the guidance 😄 👍

You're welcome. Thank you for your flexibility in considering other installation layouts


⚠ TADA Partner API has degraded performance

In 349b07d, TADA Partner API ($BRIDGE_API_TADA_PARTNER_URL) experienced degraded performance:

HTTP code: 504
Response time: 29493 ms

Resolved: TADA Partner API performance has improved in b5dd86e.


[MINOR][DOCS] Update dataframe.py

Updated the documentation for the melt function as it requires the values argument, and it is not optional.
Proposed Changes
This pull request proposes updating the documentation to reflect that the values parameter in the .melt() method is required and not optional, as previously indicated. The documentation will now specify that values can be a str, Column, tuple, or list and must be explicitly provided.
Justification for Changes
The change is necessary because the current documentation incorrectly states that the values parameter is optional. This has led to confusion and runtime errors, as the parameter is actually required for the function to execute properly.
User-Facing Changes
This change affects the documentation only. It corrects the description of the values parameter from optional to required, providing clarity to users. This change will ensure users are aware that they need to specify the values parameter when using the .melt() method.
Testing of Changes
No new tests are required for this documentation update, as it does not affect the code's functionality. This update aims to clarify existing functionality and prevent user errors.
Use of Generative AI
No

@HyukjinKwon
hello, I am sorry for the ping but I have made the necessary changes


possible documentation error

endCommand seems to be none existent, end() worked fine for me

You are right, thanks! :)


Take a screenshot example

That's something people often ask
Would be good if that can be done in few lines

(and we can reuse the code or #81 )

done

done


OpenStack: Set security group for Packer image build instance

Use security group from startnode configuration.
This should avoid the Packer image build instance from using the project's default security group (fixes #147).

I have not had a chance to test building a new compute node instance with the updated Ansible-deployed configuration due to some issues with the Digital Labs prototype OpenStack control plane. I'll try an image build using the update Packer configuration once this is resolved.


Fixes for firefox

I'm using firefox and don't have the chrome driver installed. This throws a ModuleNotFound error at this line
from webdriver_manager.chrome import ChromeDriverManager

I've fixed it by only having this line execute when a custom driver is not provided.
Also, when doing messenger.send_message on Firefox, only 1 character was being sent. Resolved this by chaining the send_keys and Shift+Enter operations.

@mukund109, please, follow the guidelines provided by @Kalebu. Feel free to PR the updated version whenever possible. For now, this one is closed due to the lack of activity.


Save?

Hi,
Why is there no :w to be able to save?
Thanks, Ali

I suspect this is because commands in general aren't implemented yet.

Hey yes I've been busy as of late, i manage other VS Code extensions  and maintain a JS engine  plus a full time job so this has fallen a bit in priority. I'm happy to help you add this feature if you want to have a go, it should be straight forward to be honest.
Lets look at how search works (because command mode will be similar)
Typing ? puts us into search mode, see here: https://github.com/jasonwilliams/vscode-helix/blob/ad779c6282ae3e96a81c9f5723ea41ea831527d7/src/actions/actions.ts#L62-L65
Every key stroke goes to the type handler, but because we're in search mode you can see it goes down a different path (it calls addChar and returns)
https://github.com/jasonwilliams/vscode-helix/blob/ad779c6282ae3e96a81c9f5723ea41ea831527d7/src/type_handler.ts#L9-L11
addChar is handled by the search class
https://github.com/jasonwilliams/vscode-helix/blob/main/src/search.ts#L45-L64
So, we already have a commandLine class which is a bit bare at the moment. You could do something similar.
When someone types : you could enter commandLine mode (which would be added here), then have characters added, then on enter check what command has been ran. If w has been ran you can call the vscode command https://code.visualstudio.com/api/references/vscode-api#workspace (save)

Hi, sorry I did not mean to come off as unappreciative of your work. It's a great extension! I was curious if it was a design decision or something. Thanks for the directions! I'll try and work on it if I have time.
Thanks for all your work again!


Stashes API leaks a file handle

The stashes API doesn't make sure to close the file handle to log/refs/stash which can mean it is held open, which on Windows can make it impossible to delete the repo.

The relevant code hasn't change I don't think, https://github.com/ruby-git/ruby-git/blob/master/lib/git/lib.rb#L602
That just needs to get moved to a block form.

Still a bug AFAIK.

@coderanger
I will look into it.
To verify based on time drift, the line in question is now.
https://github.com/ruby-git/ruby-git/blob/master/lib/git/lib.rb#L605

Yep, that should be more like:
File.open(filename) do |f|
  f.each_with_index do |line, i|
          m = line.match(/:(.*)$/)
          arr << [i, m[1].strip]
    end
end

@coderanger Sorry for the spam from our bots. 😉 The idea is to get rid of inactive issues where the original requester is no longer participating in the discussion/issues that might have been resolved/issues where no-one cares about the resolution any more. The "pinned" label can be applied by the contributors to flag an issue for "do not close automatically".


#196 Publish a global dotnet tool

Description
tool to generate an asyncApi spec from a startup assembly.
Implementation inspired by https://www.nuget.org/packages/Swashbuckle.AspNetCore.Cli
I already took the freedom to upload to nuget: https://www.nuget.org/packages/AsyncAPI.Saunter.Generator.Cli
Uses the Lego AsyncApi.net nuget packages to also export yml spec files.
Related issue(s)
#196

I'm happy to comply with the new formatting style rules or with changes from PRs like #201
@yurvon-screamo is it possible to assign issues to me? #196 #197 #207 (Or can you assign rights if I may do that myself?)

don't rush too much, I'm finishing the translation to the LEGO library, better wait for it so as not to solve a million conflicts...

I didn't know you were working on the LEGO migration, just saw your draft PR. Very nice to see!
If any more conflicts arise, I'll resolve them too.

I think all remarks have been addressed. All the working parts are unit tested. I've also made changes to the ci workflows to run all tests (not just the 2 projects that already existed.) and to also release based on the solution, not just the main Saunter csproj (release pipeline changes are not tested)

@yurvon-screamo Any idea when this might get merged and added?

@smoerijf Your prerelease version on NuGet does not work with function apps. They do not have a standard Startup.cs file, and it seems to be having issues with that.

@smoerijf Your prerelease version on NuGet does not work with function apps. They do not have a standard Startup.cs file, and it seems to be having issues with that.

Thank you for trying the prerelease. I've never worked with function apps, is that the same as Azure functions? Don't those apps have a Main or ServiceProvider?
How this tools works: Inspect the DLL to find the main entrypoint and build the IServiceProvider. That IServiceProvider is used to create instances of Saunter's IAsyncApiDocumentProvider class. This is the same approach as Entity Framework Migrations (I'm using an EF nuget package to extract the IServiceProvider from the DLL). So this tool should support the same type of apps as EF does.
As I've no experience at all with function apps, I've no idea how they are structured or how Saunter library integrates with them. If they work with EF migrations, could you share a (minimal) example with Saunter?

@smoerijf Your prerelease version on NuGet does not work with function apps. They do not have a standard Startup.cs file, and it seems to be having issues with that.

Thank you for trying the prerelease. I've never worked with function apps, is that the same as Azure functions? Don't those apps have a Main or ServiceProvider?
How this tools works: Inspect the DLL to find the main entrypoint and build the IServiceProvider. That IServiceProvider is used to create instances of Saunter's IAsyncApiDocumentProvider class. This is the same approach as Entity Framework Migrations (I'm using an EF nuget package to extract the IServiceProvider from the DLL). So this tool should support the same type of apps as EF does.
As I've no experience at all with function apps, I've no idea how they are structured or how Saunter library integrates with them. If they work with EF migrations, could you share a (minimal) example with Saunter?

Here's a minimal example: https://github.com/7CLewis/SaunterFunctionApp. If you Build that and then try to run dotnet asyncapi tofile [path_to_repo]\bin\Debug\net6.0\SaunterFunctionApp.dll --format "json", it'll give that error I mentioned.
Azure Function apps do not have a normal Startup like regular apps, as you can see from that example. I haven't tried EF Migrations with AzFuncs, so I can't speak to that.

@smoerijf when u do ef core in AzF where startup doesn't exists you have to offer up a Design Time Factory as doc'd here https://learn.microsoft.com/en-us/ef/core/cli/dbcontext-creation?tabs=dotnet-core-cli#from-a-design-time-factory
could something similar be done in saunter where before looking for startup stuff...it would look for a specific public type implementing an interface.


Emulate script.timer() using 2d model timer

Sadly AbstractTimer's API is not 1 for 1 with QTimer, but it is close enough.
With this change, timers in js scripts created by script.timer() should be using 2d model time.

Codecov Report

Merging #1772 into master will increase coverage by <.01%.
The diff coverage is 20%.

@@            Coverage Diff             @@
##           master    #1772      +/-   ##
==========================================
+ Coverage   26.86%   26.87%   +<.01%
==========================================
  Files        2002     2002
  Lines       82366    82391      +25
  Branches     1257     1257
==========================================
+ Hits        22125    22139      +14
- Misses      60164    60175      +11
  Partials       77       77

Impacted Files
Coverage Δ

...ommon/include/trikKitInterpreterCommon/trikbrick.h
0% <ø> (ø)
:arrow_up:

plugins/robots/utils/include/utils/realTimer.h
100% <ø> (ø)
:arrow_up:

...ots/common/twoDModel/src/engine/model/modelTimer.h
100% <ø> (ø)
:arrow_up:

plugins/robots/utils/include/utils/abstractTimer.h
50% <0%> (-50%)
:arrow_down:

plugins/robots/utils/src/realTimer.cpp
58.33% <0%> (-5.31%)
:arrow_down:

...s/common/twoDModel/src/engine/model/modelTimer.cpp
95% <0%> (-5%)
:arrow_down:

...rikKitInterpreterCommon/src/trikQtsInterpreter.cpp
24.21% <11.11%> (-1.38%)
:arrow_down:

...preters/trikKitInterpreterCommon/src/trikbrick.cpp
14.36% <36.36%> (+1.48%)
:arrow_up:

...src/interpreter/details/sensorVariablesUpdater.cpp
90.78% <0%> (+7.89%)
:arrow_up:

...tBase/src/robotModel/robotParts/abstractSensor.cpp
100% <0%> (+37.5%)
:arrow_up:

Continue to review full report at Codecov.

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


Reels do not embed, but can be embedded with simple url fix

Ex: I just shared https://www.ddinstagram.com/reel/C71eninSbNj/
This does not embed, however
https://www.ddinstagram.com/p/C71eninSbNj/ does.
It's not too hard as a user to fix, but it's be nice to fix on your end.

Honestly this issue didn't seem all too consistent but yeah, right now dd Instagram hasn't been working for me

This should work now, sometimes Discord/Telegram cache the old version and you need to change the url. Please reopen if InstaFix always failed to embed