Feature Extraction Causing Export ERRORS

Hi Everyone,
So I have noticed an issue when exporting due to the feature extraction. I am guessing that even if you are not using the image recognition part of the policy it still sets up those nodes in the graph. Now the issue arises when you want to export this to an ARM processor. tfcompile will automatically pickup that there is some sort conv network due to the nodes and require the arm compute library even though you do not neet it and thus making the hex much larger for no reason and in most cases the hex will not fit the arm mcu.
Any help into removing these and or way to turn that part off would be great thank you.

I am not sure why "feature extraction" would cause issues per-se, but I understand if convolutional layers would do this.
In any case, you might want to take a look at exporting models documentation. I recommend you only extract the network weights with agent.get_parameters(), and on your target machine re-create the network manually and then assign those parameters to correct places.

@Miffyli Thank you for your quick response. I am not experienced enough to recreate the network manually at the moment but is there is a way to remove them. If you can you point me in the correct way and or help me. I would be able to create the docs for exporting into ARM devices and or C/C++

Unfortunately I am not familiar working with NNs in such platforms. However, if your network only consists of 1D input, 1D output and fully-connected layers ("MlpPolicy"), then you only need functions for matrix multiplication and any activation functions (tanh, in the case of stable-baselines), as well any processing needed for the output (e.g. softmax for discrete actions).  You can google for "Neural network in C++" or "MLP in C++" to find tutorials on this. Note that you do not need the "gradient" or "backpropagation" part (nor the derivatives), you can assume you already have the weights.

@Miffyli  I am using PPO2, MLB, tanh, continuous action space. Can you point me to the source where the network gets initialized i was just looking at tensorboard and I think it's the flatten function at is invoking tfcompile to think this is a conv network?

Ok so after digging some more I figured out the issue. There is no way to bypass the conv part of the policy initialization. The issue is arising from CNN and the MLP_Extracter in the policy.py so when tfcompile sees those parts in the graph it assumes its a conv network and asks for the libraries to be put into the compiled hex file and there is no space to add that library.
Anyone know a workaround to not have them initials in the model.
This makes this library unusable in most cases on small STM32 ARM processors which is very bad because this has great potential.

Again, I am not familiar with tfcompile and how it works, but you could try modifying the code by removing all references to convolutional networks (i.e. all imports of convolutional operations). If you only use "MlpPolicy", this should be rather easy. Other than that I do not have ideas to share.

@Miffyli Exactly the case can you help me understand how to bypass that part i have been trying for paste 4 hours now. ANy suggestions would be very useful and it will also me to make a PR on exporting model.

I would suggest you to use SB3, the PyTorch version of SB, currrently in beta: https://github.com/DLR-RM/stable-baselines3
I have successfully installed it on a raspberry pi.
You can also compile the C++ lib only and easily export trained network to c++ with pytorch (cf pytorch doc).
In the documentation, we show also how to export Stable-Baselines2 models to pytorch: https://stable-baselines.readthedocs.io/en/master/guide/export.html
In the past, I also wrote some code to use trained cnn model in C++, using eigen or pytorch c api.
However, I was still using pybind11 to pass python objects to the c++ code.

@Miffyli I would love too however I am constrained with the TF version and AOT tfcompile. If i change my setup it will set me back a couple of months.

So if i override the policy with a custom one like this it should work, correct me if I'm wrong.
I found this custom policy as a template but i would need to remove the flatten part and should in theory not build any sort image processing node within the network.
`class KerasPolicy(ActorCriticPolicy):
def init(self, sess, ob_space, ac_space, n_env, n_steps, n_batch, reuse=False, **kwargs):
super(KerasPolicy, self).init(sess, ob_space, ac_space, n_env, n_steps, n_batch, reuse=reuse, scale=False)
    with tf.variable_scope("model", reuse=reuse):
        flat = tf.keras.layers.Flatten()(self.processed_obs)
        x = tf.keras.layers.Dense(64, activation="tanh", name='pi_fc_0')(flat)
        pi_latent = tf.keras.layers.Dense(64, activation="tanh", name='pi_fc_1')(x)

        x1 = tf.keras.layers.Dense(64, activation="tanh", name='vf_fc_0')(flat)
        vf_latent = tf.keras.layers.Dense(64, activation="tanh", name='vf_fc_1')(x1)

        value_fn = tf.keras.layers.Dense(1, name='vf')(vf_latent)

        self._proba_distribution, self._policy, self.q_value = \
            self.pdtype.proba_distribution_from_latent(pi_latent, vf_latent, init_scale=0.01)

    self._value_fn = value_fn
    self._setup_init()

def step(self, obs, state=None, mask=None, deterministic=False):
    if deterministic:
        action, value, neglogp = self.sess.run([self.deterministic_action, self.value_flat, self.neglogp],
                                               {self.obs_ph: obs})
    else:
        action, value, neglogp = self.sess.run([self.action, self.value_flat, self.neglogp],
                                               {self.obs_ph: obs})
    return action, value, self.initial_state, neglogp

def proba_step(self, obs, state=None, mask=None):
    return self.sess.run(self.policy_proba, {self.obs_ph: obs})

def value(self, obs, state=None, mask=None):
    return self.sess.run(self.value_flat, {self.obs_ph: obs})`

@DroneMesh Again, I do not know what is required to make this work, but to you should be able to get rid of all CNN stuff by removing references in policies (leave only MlpPolicy and remove all "cnn" stuff/set to None. Also remove nature_cnn) and remove conv stuff in tf_layers. That should be all cnn-related operations. Not sure why these would be included in the compiling if they are not used, but I am not familiar with tfcompile.

@Miffyli  I ended up removing everything related to CNN stuff however it turns out the issue is with the tensor values and nodes. tfcompile thinks there are long long int in the graph so I thought maybe the tensors are np.float64 but that was not the case. So i am digging some more into it now.

Solved it was an LLVM bug


[Neoforge 1.21.3] balloon disappears when hit

I crafted a balloon, placed it, but wanted to move it. I tried hitting it once, and it disappeared without leaving any balloon item.

Hi! Thanks for reporting this.
It's been a while since I worked on this datapack (blame my lack of free time and motivation)
Probably some issue with the hitting detection. The original code tries to check if the player is in creative or not to decide to drop the item, but I now see that it causes issues.
When I have enough time I'll fix it!

The issue has been fixed on the new available patch on modrinth and her on github. Any other problem you can always report here S2.


Events are fired before listeners are added

To listen to and respond to events, one has to setup listeners as follows:
var r = request.post(postOptions);

r.on('close', function() {
    // Do something
});

r.on('data', function(data) {
    // Do something
});

r.on('end', function() {
    // Do something
});

To configure listeners, you have to initiate the request in order to get a Request object. If the request is running, isn't it entirely possible for one or more events to be fired before the corresponding listener is added? To solve this there should be a way retrieve the Request object, add listeners and then initiate the request.

no.
for one thing, the actual http request isn't even created until nextTick(), but even if it was those events will never fire until after nextTick() :)


Filter batch 01

ic circles pythagoras
ic kitties
ic snakes

Looked things over on the deployment preview this morning and these 3 collections all look good to me.


Train custom dataset ?

I want to train in my language . What is config i must modify ?
if label_convertor['dict_type'] == 'DICT90':     PAD = 92
What is pad = 92 mean .

I want to train in my language . What is config i must modify ? if label_convertor['dict_type'] == 'DICT90': PAD = 92 What is pad = 92 mean .

First, you should build your character dictionary, like DICT90, and use your custom dictionary in your config file.
PAD is a special symbol of MASTER, which is out of DICT90 but will be used in MASTER Decoder. Other like SOS/EOS, is also MASTER's special symbol.
PAD is mean this token will been use to pad the sequence to max_length.

@JiaquanYe Thank you for reply . Can model recognition space ? I want to add space character in DICT90.

@JiaquanYe Thank you for reply . Can model recognition space ? I want to add space character in DICT90.

Sure, you can add space character in your custom dictionary, and apply it in the training config.

@ThorPham did you train this model without failure? I am facing errors during training.


Using @export_category using the same name as a variable will overwrite the first variable in the category.

Godot version
4.0.2.stable.mono
System information
Windows 10 - 4.0.2.stable.mono - Any Renderer
Issue description
In a script with an @export variable (with a non-default value), Godot will replace the first variable in the category with the same name. For example, if you're exporting a variable called "Vector", and the value is set to a non-default value, the first variable in the category called "Vector" will also be changed to the same value.
Steps to reproduce
Attach said script to a node:
extends Node

@export var Vector: Vector2
@export_category("Vector")
@export var Var2: float = 1

func _process(delta):
	print(Var2)

When changing the value of the Vector export variable, the variable Var2 will contain the same value. This does not happen when the @export_category has a different name.
Minimal reproduction project
N/A

Also reproducible on 4.0.3.stable for me.

Should having a same name as a category be allowed in the first place (especially with the same casing)?

I would have expected categories and variable names to not affect each-other at all, and simply be for organization in the editor, since besides this they don't really change anything in the code. This came up when I had an import for Camera, and I also had a category for camera settings also called "Camera", and my sensitivity property was being overwritten by my Camera object.

The way groups and categories are implemented is such that they are also properties, albeit with special flags. Which is how you can define them with the _get_property_list override. So this is indeed an expected limitation.

This should be better documented then.

It should script error, like defining any other variable twice does

I disagree, for me category/group/subgroup names are just text that shouldn't interfere with variables and classes. It is logical that you can use the same subgroups in different groups.
Also the documentation says that you can use @export_group("") to end the current group. In the current implementation, you can only do this once, otherwise bugs occur (see #68030). "" is a real property or just text?
See https://github.com/godotengine/godot/pull/78254#issuecomment-1598571931.


Prevent style insert

The styles are inserted inline in the head, how can I prevent?
Thanks in advance
clemens

Why do you want to prevent it? If you just don't want to use the default styles I just added support for disabling them. This still loads the style files but they don't have any effect so you can use your own styles. So with 0.9.0 version there is two new inputs:
useDropzoneClass: When set to false then the default styles of dropzone library are not used.
useDzWrapperClass: When set to false then the styles of the wrapper library are not used.

I will close this, but if you have a good reason why you want to prevent the styles loading then I can look into that.


long integer values displayed incorrectly

Originally reported on Google Code with ID 297
The server returns:
{"id":7329270081369170538,"name":"arya.irani","tickets":[]}

Advanced Rest Client displays the correct raw string:
{"id":7329270081369170538,"name":"arya.irani","tickets":[]}

but totally wrong data in the formatted Json page, which is the default display:
{
  id:<PHONE_NUMBER>369171000
  name: "arya.irani"
  tickets: [0]
}

JSON numbers have arbitrary precision, so you can't represent a JSON number as a Javascript
Number, or you get bugs like this. :-\

On what operating system, browser and browser version?
OS X 10.10.1
Chrome 64-bit 39.0.2171.95

Reported by arya.irani on 2015-01-12 17:30:07

That's the tricky one. Numbers between -(2^53 - 1) and 2^53 - 1 are considered safe in JavaScript.  Your number is higher than that so it loose precision resulting with different value.
What I can do about it? Pretty much nothing. When the response is ready it is a string at first. But, when the app recognize it as a JSON it will use native JSON.parse function. If the response from the server contains such of number which isn't a string the error will occur and the app will never know about it.
There are two possible solutions:

Custom JSON parser
Some prediction algorithm which will detect numbers > Number.MAX_SAFE_INTEGER and try recover it from the source string.

First one it's not a good idea since this parser must be maintained by me which is not a part of this project. Second however is possible but not error proof.
I'll keep the issue report opened but there will be no immediate action on it.

Duplicate of #234


🐛 [Bug]: ActionSheet组件使用时报错

Which React Vant packages are impacted?

[ ] react-vant (React Vant core)
[ ] react-vant-icons(React Vant Icon)

What version of React Vant are you using?
3
Reproduce live demo(codesandebox or stackblitz)?
No response
Descripition
react-vant(3.3.5），
1.在ActionSheet组件使用时报错：@react-refresh:267 Warning: Failed prop type: The prop timeout is marked as required in Transition2, but its value is undefined.导致需要主动声明duration={300}，防止报错
2.closeable和closeIcon，设置无效，一开始以为设置description导致，可是去掉description，同样无法显示

react-vant(3.3.5），在ActionSheet组件使用时报错：@react-refresh:267 Warning: Failed prop type: The prop timeout is marked as required in Transition2, but its value is undefined.导致需要主动声明duration={300}，防止报错

/


Correcting cert retrieval issues for multiple user scenarios

Signed-off-by: John McCrae<EMAIL_ADDRESS>Description
Reference Bug - https://chefio.atlassian.net/browse/INFC-407
Reference Bug - https://github.com/chef/chef/issues/13402#issuecomment-1401633050
Updated - 2/5/2023 - This PR takes over from ~#13539
We moved to allowing private keys to be stored in a secure manner as part of a "no certs on disk" initiative. So client.pem gets stored somewhere safely.
That initially meant for windows users that we would store the private key as part of a pfx object into a certificate store. Then we would extract the private key and use that as the client secret to connect to Chef Server with. But as part of that process, Windows requires you to use a password to export the private key with. That meant potentially storing a secret in plain-text in a registry key. We didn't like that so we opted to encrypt that password.
The recent problem with our initial approach was that we were using ConvertTo-SecureString and ConvertFrom-SecureString in PowerShell as parts of the encrypt/decrypt processes for that password. Those 2 cmdlets rely on DPAPI which itself is reliant on the calling users password to do it's work. This meant that in a multi-user scenario, the first user would initialize the chef-client and create a password to secure the nodes private key with. However the second user would receive an error message because the secret was encrypted with a user-specific password. For example, an Admin user connects to the node and runs commands to bootstrap that node. This process causes the creation of the node pfx object and an Admin specific password to secure the private key with. Then that person sets up a scheduled task using the NT Authority\System account (could be any other user account, it's the same problem). The first time that task tries to run, it fails because it is attempting to call either of those methods above using a different password than what the Admin account used.
Side Note: Testing showed that the Admins group and NT Authority\System accounts always have access to both the certificate store where the cert was registered and to the registry key where the encrypted password was stored.
The new approach in this PR is to use more granular crypto settings that use both a Key and an Initialization Vector. By encrypting this way, we store two additional values in the registry: The key and the vector in addition to the encrypted password. This provides a user-agnostic method to set and retrieve certificates and passwords with.
This approach was tested in Azure using a Server 2019 Windows VM. The chef-client was set to run every 30 minutes using the System account and was correctly able to read and decrypt the password for the private key as well as retrieve the certificate used to authenticate the node to chef-server with.
This solution now addresses a couple of key issues. The first is that the code now allows for a multi-user scenario as well as an Admin/System scenario. In the first case, this update allows for 2 or more people to use the same system and allow for them to have separate certificates and private keys to authenticate to Chef Server with. In the second scenario, an Admin can connect to the node and setup cert-based security and then pass control to a system account to run Chef Client on a schedule.
Related discussion - https://github.com/chef/chef/pull/13407
Phil rightly points out the problems with trying to use the HKEY_CURRENT_USER hive on Windows in a multi-user scenario. If Bob and Steve used the same PC and you wanted them both to be managed, using multiple node objects et al is mandatory. However, this is now addressed with the changes in place.
Related Issue
Reference Bug - https://chefio.atlassian.net/browse/INFC-407
Reference Bug - https://github.com/chef/chef/issues/13402#issuecomment-1401633050
Related discussion - https://github.com/chef/chef/pull/13407
Types of changes
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Chore (non-breaking change that does not add functionality or fix an issue)
Checklist:
I have read the CONTRIBUTING document.
I have run the pre-merge tests locally and they pass.
I have updated the documentation accordingly.
I have added tests to cover my changes.
All new and existing tests passed.
All commits have been signed-off for the Developer Certificate of Origin.

AdHoc builds  here - https://buildkite.com/chef/chef-chef-main-omnibus-adhoc/builds/1996

does chef-cli or knife in workstation and chef-client share the cert auth code for storing node pem in windows OS cert store?

This may also have implications with chef-cli in the latest chef-workstation release with chef-client 18.0.185 and this issue that has come up for windows users https://github.com/chef/chef-cli/issues/218


node-gyp links to node version of hdr_histogram, not local version

node version 11.10.0+
Linux 4.15.0-48-generic #51-Ubuntu SMP  x86_64 x86_64 x86_64 GNU/Linux
gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04)
My node addon uses the C++ node-addon-api to wrap a (primarily C) library supplied as a .so file. The library contains a number of dependencies including hdr_histogram. The problem I am having is that the library's hdr_* symbols are being resolved by the version built into node (.../node/deps/histogram/). Histograms were added in node 11.10.0 and their availability as global symbols causes my program to fail because the two implementations diverge in how the counts are allocated.
My first thought was that there must be a way to partially resolve external symbols by linking my modules together into a combined module. I've tried ld -r modules*.o -o combined.a, and gcc -shared modules*.o -o combined.so as well as various permutations on those, While i understand linking and loading I don't have in depth knowledge of the gnu tool chain nor node-gyp, so I may be missing something obvious.
If there is a way to tell node-gyp to search my libraries before using symbols provided by node that would be a nice quick fix.
Any ideas on how I can address this problem would be very much appreciated.

This is related to nodejs/node#27664 because I'm fairly sure those symbols aren't supposed to be exported by the node binary (cc @jasnell)
Is it an option for you to compile your C library from source to a static library and link against that?
If not, can you check if env LD_LIBRARY_PATH=/path/to/dir/containing/your/lib node app.js works? If yes, adding -Wl,--rpath,... to your 'ldflags': [...] stanza should do the trick.

i've tried both these approaches and have not had success.
we currently produce a static library as well (10x bigger than the shared version) but using it the node version was still loaded. it's possible that the library build system (which i only started looking at yesterday) is not being built in a way that causes the symbols to resolved because it seems like that ought to work. i'll continue digging into what's going on there.
the second approach works in a small test app where i explicitly load the hdr_histogram library as a dependency. but it doesn't work when i'm trying to load our library.so that contains the hdr_histogram library. one alternative would be to distribute the hdr_histogram library separately but as my code is not the only package using our library that will take further evaluation.

ok, i know a lot more about ld, nm, readelf, ldd, and the like. i believe i can work around this; i think that the reason we're ending up with the problem is that our shared library does not do partial linking at times when it can.
i appreciate your suggestions - they started me down the right path.


Strong name

Can you please consider strong naming your assembly so that it may be used by projects that use a strong name?

Fixed, will be released in version 4.0.0 in a couple of minutes.

That's awesome, thanks @tompazourek!


redmine 5.1

hello mr @xel1045
im install your plugin but  dont know how i use it or where i can configure it or enable it?
plz put describition to know how its working

There was a bug that prevent it from being display in the query form. If you update the plugin to v1.4.2, you should now see a checkbox in the query creation/edition form to enable the feature:


Refit and Rx

Can Refit be used with Rx?

Yeah mate. You just need to set the methods up to return IObservable<Foo> instead of Task<Foo>. See https://github.com/paulcbetts/refit#retrieving-the-response.
Also, observables are cold (i.e. do nothing until subscribed and issue a new request each time). See https://github.com/paulcbetts/refit/releases/tag/2.0.0 for more info.


neucoind: sendfrom doesn't allow me to spend an entire account

$ neucoind listunspent
[
    {
        "txid" : "c81b2815cacd7e37d1d436b8c85a104eda00a882ce26969f051307fff09c7339",
        "vout" : 1,
        "address" : "Ng8V6A9XoWuoryrPm8SmFTc4tb5QannkZh",
        "account" : "ccbib-invest",
        "scriptPubKey" : "210353dfc679bcbdc3e30fb23df93c6783ece8337b79705fdbc1e503c612cf940c23ac",
        "amount" : 21183.75327900,
        "confirmations" : 2921
    }
]
$ neucoind sendfrom ccbib-invest NdgVrpAGwi5KVk5FkqnKyXe5EJFsFSzhFJ 21183.73327900
error: {"code":-6,"message":"Account has insufficient funds"}

Note that above I have left a margin of 0.02 NEU, which should be more then enough for the fee of 0.01 NEU ...

After closer investigation it looks like sendfrom doesn't allow to spend stake rewards.


Trivial loop throws KeyError

The following trivial loop causes a compilation error:
julia> using LoopVectorization

julia> function foo!(z, x)
    @turbo for i = 1:1
        z[1] += x[1]
    end
end
ERROR: LoadError: KeyError: key Symbol("###RHS###3###") not found

This comes up as a special case from some automatically generated code. Strictly speaking it satisfies the requirements for @turbo and should probably not error out.

Duplicate of https://github.com/JuliaSIMD/LoopVectorization.jl/issues/331

Well, accept that it's z[1] += x[1] instead of z[1] += x[i], so maybe not an exact duplicate.

PRs welcome. THe same approach mentioned in the linked thread works, even though we also have x[1] instead of x[i].
julia> using LoopVectorization

julia> function foo_noturbo!(z, x)
            @inbounds for i = 1:1
               z[1] += x[1]
           end
       end
foo_noturbo! (generic function with 1 method)

julia> function foo_noturbo!(z, x)
            @inbounds for i = 1:1
               z[1] += x[1]
           end
           z
       end
foo_noturbo! (generic function with 1 method)

julia> function foo!(z, x)
           s = zero(eltype(z))
           @turbo for i = 1:1
               s += x[1]
           end
           @inbounds z[1] += s
       end
foo! (generic function with 1 method)

julia> x = rand(1)
1-element Vector{Float64}:
 0.9754894452989981

julia> z = zero(x);

julia> foo_noturbo!(z,x)
1-element Vector{Float64}:
 0.9754894452989981

julia> foo!(z,x)
1.9509788905979961

julia> z[1]=0;

julia> foo!(z,x)
0.9754894452989981


Error with Unity version 2021.3.10f1

The shader you developed works great in Scene view, but it gives me some troubles in Game view.
I'm trying to overlap a 3d model, with shadows, to a background image imported in Canvas as a Raw Image. Of course, I don't want the plane where the shadow is received to be visible, so that I get the effect of my object casting shadow directly on the background.
However, with this shader, the plane is still visible by the camera, and I see the whole plane overlapped to the background.
I provide a sample project to reproduce my issue (I can't provide the original project since I signed an NDA):
https://github.com/frettore/ErrorSample

Hello @frettore,
Thank you for reporting the issue. I can confirm this issue from your sample project.
I think the problem is caused by the rendering order of the canvas and the shadow plane.
Because in default the canvas is rendered after the shadow plane is done. The rendering procedure would be like:

Draw the shadow plane. Alpha blend with background color.
Draw the canvas. This will not trigger alpha blending, because the canvas is behind the shadow plane.

The solution is to switch the rendering order of the canvas and the shadow plane:

Create a material named "UIMat" or whatever.
Set the render queue of "UIMat" to "Geometry" or "2000"
Apply it to your "RawImage" game object
If this still not work, try to change the render queue of the shadow plane to "2500".

Another solution is to use the 3D plane or quad instead of UI canvas.
Left: before
Right: after

Thank you very much @Ending2015a !!!!!
That was exactly the problem and now everything works perfectly. You literally prevented me from getting mad!


Install django-flags

Changes in this PR:
Following instructions from https://cfpb.github.io/django-flags/
This requires access to the admin UI, enabling which exposed a couple of issues:

The admin urls in urls.py need to come before the redirect to remove the trailing slash, as the trailing slash is required in the admin urls (otherwise it tries to redirect to  eg /adminlogin instead of /admin/login for some reason)

The ADMIN_URL needs to not have a preceding slash

The django default templates need to be loaded for the admin UI to display

This PR fixes all the above, new flags can be added to FLAGS in setttings/base.py as required, then enabled in the admin.
Trello card / Rollbar error (etc)
https://trello.com/b/OYgnaYZc/1-caselaw-beta

Do we want django-flags or django-waffle? Flags doesn't support progressive roll-out, but it does have a cleaner implementation for templating and forces us to keep flags defined in one place.

Hmm, i'm pro django-flags for the reasons you give - is progressive
roll-out something we're likely to want?
On Wed, 19 Apr 2023 at 13:09, Nick Jackson @.***> wrote:

Do we want django-flags or django-waffle? Flags doesn't support
progressive roll-out, but it does have a cleaner implementation for
templating and forces us to keep flags defined in one place.
—
Reply to this email directly, view it on GitHub
https://github.com/nationalarchives/ds-caselaw-public-ui/pull/645#issuecomment-1514708082,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAABBN2PFSY4XHS5KIHZL3TXB7PZBANCNFSM6AAAAAAXBNYPFM
.
You are receiving this because you authored the thread.Message ID:
@.***>

I think it's something we're likely to want eventually, but it's pretty low-effort to migrate between flag libraries so I'm happy with this.


Readme Updates and Add Contributing Documentation

Motivation

I was asked to provide feedback on the readme
Since this is open source, a direct link to the license and any rules for contributing seemed like a solid add

Modification
Used an open source readme template to split the readme into how to use it, what features it currently has, what features we'd like to add, and other various items such as license, contributors, and etc.

/merge


Make it easier to create aliases for commands

The Problem
 I would love it if you could make it easier to add aliases without overriding commands. I think it would make life easier for quite a few people.
The Ideal Solution
 Add a command for it (!jsk alias [command] [allias])
The Current Solution
 Currently you need to make your own cog or edit the source code (which is tedious since you'll have to redo it every time there is an update)
Summary
 Make it easier to add aliases without overriding commands.

This seems like a rather niche use-case for something that can be easily done with a custom command:
@commands.command()
async def alias(self, ctx, cmdname, alias):
	cmd = ctx.bot.get_command(cmdname)
	cmd.aliases.append(alias)
	# register the modified command
	ctx.bot.remove_command(cmdname)
	ctx.bot.add_command(cmd)

Fair enough, thanks!


Fix the mysql tests on travis.

You can check my travis build results here: https://travis-ci.org/TrangPham/geocoder
Links to #937

Amazing! Thank you.


Send anonymous stats to server

@otrebski - Please provide an overview of the anonymous stats that are being sent to the mothership?  Also, would it be possible to have an opt-out feature for this for folks that have privacy concerns?
Thanks.

During first use wizard you are asked if you want to send stats. But you are right that it is missing option in preferences to turn it off. I have create 2 issues:
https://github.com/otros-systems/otroslogviewer/issues/509
https://github.com/otros-systems/otroslogviewer/issues/510


Centering SVG

Is your feature request related to a problem?
I didn't see any configuration for centering SVG.

Describe the solution you'd like
Should we add a configuration option?
Describe alternatives you've considered
No response
Additional Context
No response

Thanks for your feedback :raised_hands:
I'm not sure this is the responsibility of the plugin to handle this case as we could say the same for every images or block in Markdown and Markdown itself does not really care about any positioning.
As HTML is totally valid in Markdown, an author could for example use the following syntax to center a diagram:
<p align="center">

```d2
grid-columns: 3
Astro
Starlight
Studio {
  style.stroke-dash: 3
}
```

</p>

Which would render as:


Portus registry data cleared while pushing an image

Portus interface shows no available repositories while pushing an image to the registry. Once the push ends, crono fill the db with update registry data again.
Tested on commit #ea5a398f38c0a4c103ea9890aaa1256c2deacd9c with docker-compose

Hi @gbisheimer, this seems related to #441. That is, it seems that the docker-compose setup is broken when it comes to communicate with the registry... I'll fix this as soon as possible.

This should be fixed by now. Make sure:

To use the current master or v2, since there are some fixes regarding the set DOCKER_HOST.
Cleanup any previous generated files: docker/environment and docker/registry/config.yml.
Make sure that you are using docker-compose 1.5.2. Compose 1.5.0 and 1.5.1 are known to contain a bug in which the env_file directive was not properly parsed (and therefore the DOCKER_HOST was not properly set in the Portus container).
If you are using openSUSE and you are having problems, disable the firewall and restart the docker daemon, since SUSE's firewall might be messing with docker's networking.

I'll try to update the docs about all this, but I'd prefer to get some confirmations first :)

I'm closing this for now. If it turns out that the issues are still reproducible after taking the above steps, feel free to reopen this with additional information.


Postgres-exporter service and port selection

Hi, I use the PrometheusOperator to manage my Prometheus instance (externally from timescale charts) and scrape the postgres-exporter endpoint. However, I couldn't select the correct port to scrape either in my PodMonitor or my ServiceMonitor objects because the postgres-exporter service has no specific label and its ports either in the Statefulset or in the service are unnamed.
Currently, my workaround is to patch the service created by the chart with a new label to be able to select it.
I created a PR(#233) to fix this. The PR adds labels to the service and name the ports so it shouldn't break anything.

Closing as https://github.com/timescale/helm-charts/pull/233 is already merged.


use object form of Boolean for avoiding unneeded conversions and boxing

I didn't know that about Groovy, thanks!


MacOS share extension called "Share Extension" instead of app name

This seems to only happen on MacOS - on iOS its named as expected.

Not sure if I missed a setting.

I've never tested it on MacOS, but I'm sure there's a configuration for that.
but that's not really the target of this package. Do you really use react native on the desktop, or it's just a compatibility matter as users can now do it ?

Are you building with EAS? In my app.json I have the following entry:
"eas": {
  "build": {
    "experimental": {
      "ios": {
        "appExtensions": [
          {
            "targetName": "ShareExtension",
            "bundleIdentifier": "com.robinheidenis.hephaestus.share-extension",
            "entitlements": {
              "com.apple.security.application-groups": [
                "group.com.robinheidenis.hephaestus"
              ]
            }
          },
          {
            "targetName": "ShareExtension",
            "bundleIdentifier": "com.robinheidenis.hephaestus.share-extension"
          }
        ]
      }
    }
  },
  "projectId": "xxx"
}

Perhaps changing the name here from ShareExtension to something else might help? I don't have an IOS device, so I can't test it myself

@achorein not MacOS exactly, I think technically an iPad OS with MacOS support.  Some users do it, but this is not that important to me.
@RobinHeidenis  I do use EAS but my understanding is that we should ommit what you've included as build, leaving it as
 "extra": {
      "eas": {
        "projectId": "xxx"
      }
   },

for me.
I dont recall from where I got that idea, but it seems to work.

the eas.build.experimental have to be removed, this is mention in the FAQ in the related issue :)
@joshmohrer for your problem in macOS share menu, can you try to edit the generated ios/ShareExtension/ShareExtension-Info.plist with this ?
<key>CFBundleDisplayName</key>
<string>TESTNAME Share Extension</string>

@joshmohrer do you know how to test this share menu in local ? without an eas build

I think so -- but can I launch the ipad version of the app as a MacOS app via Expo Go or development build? I'm not sure you can?

it cannot be tested without shipping a version on test flight :/

@joshmohrer can you try with this patch in your patches/ directory for install script ?
expo-share-intent+1.4.0.patch

Will do @achorein -- do I need to do this if im using 1.4.1 already?

Or perhaps I should roll back to 1.4.0?

  Info:
    Patch file: patches/expo-share-intent+1.4.0.patch
    Patch was made for version: 1.4.0
    Installed version: 1.4.1

---
patch-package finished with 1 error(s).

1.4.1 does not include this change, so yes for testing purpose rollback to 1.4.0.

v2.1.1 includes an attempted correction but has not been tested in real conditions


Owned objects attached with wrong state

If I have a entity with some owned object and I attach this entity to the context, the entity get State "Unchanged", but the owned entity got status "Added", which lead to exception:
The entity of type 'OwnedType' is sharing the table 'TableName' with entities of type 'EntityType', but there is no entity of this type with the same key value '{PK: Value}' that has been marked as 'Added'.
I would expect, that owned entity gets status "Unchanged".
Further technical details
EF Core version: 2.1.4

More details:
`public class ParentEntity {
public int Id {get;set;}
public Entity Entity {get;set;}
}
public class Entity {
public int id {get;set;}
public OwnedObject OwnedObject {get;set;}
}
public class OwnedObject {
public string Value {get;set;}
}
`
If I add a Parent entity first and then attach an Entity, OwnedObject  get a wrong state and I get the exception. If I Attach the Entity first and then add ParentEntity everything works fine.

@Rubbiroid Does this capture what you mean by "add a Parent entity first and then attach an Entity,"
var parentEntity = new ParentEntity
{
    Entity = new Entity
    {
        id = 1,
        OwnedObject = new OwnedObject()
    }
};

context.Add(parentEntity);
context.Attach(parentEntity.Entity);

context.SaveChanges();

@ajcvickers yes.

@Rubbiroid The reason this is happening is that calling Add with parentEntity causes the entire graph to be tracked in the Added state. The Attach call on the other hand sees that the referenced entity is already tracked and changes its state but does not change the state of the owned entity. This is currently by-design, but we are looking into two changes in this area:

Changes to handling of store generated keys: #13575
Improved behaviors for aggregates: #1985

I'm closing this, but referencing the scenario from those two places.


Investigate what it means to support the notion of trust for virtual workspaces

Started with this PR. However, I'm going to move some of the discussion and thinking to this issue.
Start with Resolver API
When creating Workspace Trust, we needed a solution for handling URIs in remote windows. e.g. Dev Containers open local folders within dev containers that then have strange workspace URIs the user was asked to trust separately. To improve the user experience, we introduced the canonical URI api for resolvers. https://github.com/microsoft/vscode/blob/6a76c62232208f54bc85f22572013b382e39cf9e/src/vs/vscode.proposed.d.ts#L161-L166
The purpose of this API is to allow each resolver to provide us with a re-usable URI that we can trust. In the Dev Container example, this can be mapped to a local file path. WSL could do the same when it makes sense. Codespaces could (but does not) remap the URI to a GitHub https URI.
Considering RemoteHub
After introducing this API to the limited set of resolvers, we saw a similar need for RemoteHub which happened to be a file system provider. RemoteHub already had internally a re-mapping exactly like the resolver API but no way to provide it to core. Hence, we created the PR to introduce the same API to file system providers. Before releasing Workspace Trust, we could not take this API so late, and there were too many file system providers out in the wild that might conflict with workspace trust so we decided to handle RemoteHub in core and avoid the conflict with other virtual file system providers.
Concerns with the File System Provider API

We are duplicating the API. This is true; however, currently resolvers work quite differently than file system providers in when they are loaded. For resolvers, we need to handle the URI transformation prior to resolution of the workspace which in turn means prior to loading other extensions. We might be able to skirt this requirement in file system providers.

The name of the API is confusing in a File System Provider. It does not make it clear the purpose of this API. The API is very specifically needed only for Workspace Trust and doesn't serve much other purpose. It is also not a traditional FS-type API.

If we do want to remap the URIs of File System Providers prior to activating extensions, we need some rethinking. Separating this API into something that can be loaded early is worth exploring.

Updated Proposal
Rename the API to something workspace trust specific. e.g. WorkspaceTrustUriProvider with a function getTrustableUri(uri) or getUriAlias(uri). These would be registered to a given scheme (not the file scheme). We could consider additional restrictions e.g. only for schemes your extension registers other providers for, only one provider per scheme, etc.
Example Extensions
RemoteHub
RemoteHub is the de-factor virtual workspace provider today. It allows you to connect to a GitHub repo without cloning. It would like to convert vscode-vfs URIs to https URIs.
GitLens
GitLens doesn't exactly provide a complete workspace but adds folders to a workspace when browsing an open repository at a specific commit. It would like to convert gitlens URIs to local file URIs.
Docker
Docker allows you to browse and open files from a running container. The most secure approach would probably be to treat these as loose files that are not trusted.
Kubernetes
Based on my understanding of the extension, this is similar to Docker.
GitHub PRI
The virtual file system is intended to browse issues and does not seem to pose any risk.
Azure Databases
The file system provides a way to update cosmos db items. It isn't a full workspace but you can open editors with contents. However, practically, this is not a security risk and you don't typically connect to arbitrary cosmos dbs.
SSH FS
I haven't tested the URI structure, but this one would likely mimic a blend of SSH remote + RemoteHub giving a readable URI to trust and edit.
Remote FS
Works with sftp or ftp to provide virtual file system. I doubt any remapping would be necessary, but a proper implementation would require trust.
Gist Pad
Allows opening arbitrary gists on GitHub. Opening them is similar to RemoteHub except it follows more of a loose file flow. I would expect to be able to trust https uris.
Zip FS
I would expect this to resolve URIs to the local paths which really means just changing the scheme.
DEV Community
This extension auths into dev.to communities allowing you to edit posts. Due to the auth step here, and them being your posts, I don't expect a trust prompt.

This is quite difficult. What we do for resolvers is IMHO not doable in general. Resolvers activate before the vscode API is fully functional. So various things do not work by design. Resolvers have been like that since day 1 and they are prepared for that. While resolving, they don’t exercise those unavailable APIs or have workarounds in place. IMHO we cannot take any extension and activate it so early, as that would cause unforeseen bugs since the API has holes.
IMHO such a method would still belong to the FS provider. For example, suppose both extension A and extension B register the same schema hello: and only extension B registers the proposed workspace trust provider. I’m not 100% certain how the FS provider API behaves, maybe it is possible that due to activation ordering or interleaved execution, that FS provider from A gets to “win”, so the hello: FS is serviced by extension A. But if there is a distinct workspace trust provider API, it is possible that we will end up in the situation where extension B provides the trust aliases for files that are serviced by extension A by accident. So this hints strongly to me that the correct thing to do in order to make sure the same extension drives both the trust provider API and the FS provider API is to register these two APIs together, either as an option or as a method of the FS provider.
I’m also not sure what you’d want from the extension host infrastructure… If I understand FS providers correctly, they can come in 20minutes after a window is up and running, via user gestures (e.g. suppose there is a FS provider that is used to implement jump to definition). When the user jumps to definition, they end up with the first time with a csharp-def: URI and this could lead to the activation of an extension that defines that FS provider. So however you want this to work, IMHO this needs to work at any time in the extension host lifecycle, not just when things start up. I think computing trust for a given URI must become async, and be implemented by awaiting the activation event onFileSystem:X and then checking if the FS provider was registered together with a trust URI provider and then calling that.
cc @jrieken

When the user jumps to definition, they end up with the first time with a csharp-def: URI and this could lead to the activation of an extension that defines that FS provider

That's a good sample because these lightweight things are usually not file system providers but just document content provider. Is that something that also needs to be enrolled in trust and also need to support uri aliasing?

But if there is a distinct workspace trust provider API, it is possible that we will end up in the situation where extension B provides the trust aliases for files that are serviced by extension A by accident

I see where you are coming wrong but in a way it's also desirable to decouple trusted workspaces from file system provider. Assume, I use a simple SSH file system, like https://marketplace.visualstudio.com/items?itemName=Kelvin.vscode-sshfs, why should it bother and how would it know that some.machine is actually localhost. Isn't that the job of whom opens the workspace?

So however you want this to work, IMHO this needs to work at any time in the extension host lifecycle, not just when things start up.

The non-startup case is much less of an issue for us. At that point, we have the luxury of everything being available for us to await on. The query trust API for a specific URI is already async so we could await the providers registration if we know its coming.
The startup case is primarily important for file system providers that provide workspace contents (i.e. a workspace uri belongs to its scheme) and gets dicey because our current startup flow (which tells us the startup value of workspace trust) likes to finish before all extensions are loaded.
After that, if workspace uris change, we await the necessary information before updating the trust state and firing off the event.

That's a good sample because these lightweight things are usually not file system providers but just document content provider. Is that something that also needs to be enrolled in trust and also need to support uri aliasing?

Practically, this is usually no because the content seems to be either related or depended upon by the existing workspace. So, in most cases, you expect to trust to match the open workspaces.

why should it bother and how would it know that some.machine is actually localhost. Isn't that the job of whom opens the workspace?

I'm not sure I understand where this question is leading. For the sshfs extension, I believe its paths should be considered during trust calculations because it is very similar to the ssh remote scenario. I wouldn't expect it or a user to care about remapping the uris to localhost if that were the case, just having a reusable trustable uri: sshfs://machinename/path/to/trusted. Their scheme may already be in a trustable format, but they do need a way to tell us that the uris should be considered in the calculation.

Practically, this is usually no because the content seems to be either related or depended upon by the existing workspace. So, in most cases, you expect to trust to match the open workspaces.

That means theoretically yes? To some extend file system providers and virtual document providers are very similar. E.g said sample of  csharp-def file is often (and historically) virtual documents but can be implemented with a readonly file system. So, providing a file system doesn't mean that you provide a workspace but file system providers can be used to provide workspace folders. Sorry to ask again but what problem are we trying to solve? Is this about trusting workspace folders that are backed by file system providers or any virtual file/document?

There are indeed 2 types of items that could require trust and you list them there:

Virtual Workspace Folders
Virtual Files or Documents

While in a perfect world we handled both of these with great UX, the second one can be a lot trickier due to the ways we allow that to happen and the variety of virtual documents that might have nothing to do with trust.
Workspace Folders are much more obviously related to workspace trust and we have our own extensions that would like to take advantage of some API.
So solving both would be great, but I wouldn't want to get hung up on 2 if it makes things awful when 1 is much more immediately relevant.

Is this still actual or in for a :lock: ?


[docs] Document linting instructions

Until we get 2.0 done and make the shape annotations uh valid type annotations, we need to document how to make it not blow up your linter.
The rule violation is F22: https://docs.astral.sh/ruff/rules/forward-annotation-syntax-error/
which is a pretty basic one - it's an error that's sort of rare and hard to make, but it's also a rule that is so basic that we shouldn't be violating it (hence 2.0).
Document how to make linters not get annoyed

[ ] ruff
[ ] pyright
[ ] mypy
[ ] what else?

Careful it looks like you made a typo, calling it F22 in your comment here instead of F722 (in case that typo makes its way into the docs). To help with documenting the pyright case, I've documented some examples copy/pasted from VSCode's Pylance warnings below, but pyright also reports the same.
I've found that it fires a reportInvalidTypeArguments error on the first parameter to numpydantic.NDArray and numpydantic.Shape with the following form:

Expected no type arguments for class "{class}" Pylance(reportInvalidTypeArguments)

where {class} is Shape in the case of numpydantic.Shape. In the case of numpydantic.NDArray it fires errors simultaneously for the following {class}es: H5ArrayPath, H5Proxy, Path, VideoCapture, VideoProxy, and ZarrArrayPath.
It also fires simultaneous errors on numpydantic.NDArray itself for the {type}s Tuple[Path | str, str] and ndarray[Unknown, Unknown], reporting an error of the following form:

Type "{type}" is already specialized Pylance(reportInvalidTypeArguments)

Super helpful, and needing to do that on every line is absolutely abysmal on my part.
Proper type annotations using Protocol are coming, i just need to find a day or two to make a small PR upstream to pydantic (i think) and then it should be no problem to switch over and then mark the old form for deprecation (i'll give a full major version's warning before removing the string-based syntax).
Thanks for, uh, seeing through the thicket of linter errors for the time being.

Glad I could help! If you end up working it into a larger documentation PR to explain some of the other linter behaviors as well, of course feel free to copy/paste/modify any of the language I used above.

Thanks for, uh, seeing through the thicket of linter errors for the time being.

I guess it's a price that I'm willing to pay for using things like numpydantic! There's an alternate universe me who's using older, stable tools to do the same work, and I wonder if they're getting things done faster than me, without all the gaslighting by type checkers trying to statically analyze the black magic that things like numpydantic enable.

Lovely :):):) I would love a review once I make those changes. And yes a docs pr is due in the meantime


Error looking for openssl in previously installed ruby?

First off I'll admit this is a bit of a contrived situation, but I can't find where in the code this is happening – so I'm creating this issue in the hopes that someone can point me in the right direction. Mostly for my curiosity, then to see if a solution should/can be created.
I had previously installed 2.5.5 with Homebrew<EMAIL_ADDRESS>then uninstalled<EMAIL_ADDRESS>Next step was to run rbenv install 2.6.0-dev. Got the following error in the log:
...
Configuring OpenSSL version 1.1.0j (0x101000afL)
...
Cloning into 'ruby-2.6.0-dev'...
Updating files: 100% (9038/9038), done.
/var/folders/rg/0v_97xsx6gj600wz5jq6_6440000gn/T/ruby-build.20191109121454.90268.rqoqTW/ruby-2.6.0-dev /var/folders/rg/0v_97xsx6gj600wz5jq6_6440000gn/T/ruby-build.20191109121454.90268.rqoqTW ~/Projects/homebrew-core
checking for ruby... /Users/gfguthrie/.rbenv/shims/ruby
*** using http instead of https ***
downloading config.guess ... /Users/gfguthrie/.rbenv/versions/2.5.5/lib/ruby/2.5.0/openssl.rb:13:in `require': dlopen(/Users/gfguthrie/.rbenv/versions/2.5.5/lib/ruby/2.5.0/x86_64-darwin17/openssl.bundle, 9): Library not loaded<EMAIL_ADDRESS>(LoadError)
  Referenced from: /Users/gfguthrie/.rbenv/versions/2.5.5/lib/ruby/2.5.0/x86_64-darwin17/openssl.bundle
  Reason: image not found - /Users/gfguthrie/.rbenv/versions/2.5.5/lib/ruby/2.5.0/x86_64-darwin17/openssl.bundle

I had previously installed 2.5.5 with Homebrew<EMAIL_ADDRESS>then uninstalled<EMAIL_ADDRESS>
You had broken your ruby 2.5.5, and then you tried to use it to build 2.6.0-dev (the latter needs a host ruby to install). This resulted in an error.
Since you are on macOS, you always have a working system ruby by default. You can use it to install 2.6.0-dev:
RBENV_VERSION=system rbenv install 2.6.0-dev

Figured it was something like "needs a working ruby to install" – thanks!


test: Updated assertions for API Bug sepc

RCA:
TED api used was pointing to cloud service which is incorrect
Also the validations needs to be rechecked.

Summary by CodeRabbit

Bug Fixes

Enhanced API tests to verify image URLs, message lengths, and types for responses related to cat images, dog images, number facts, and cocktails.
Updated test spec for limited tests in the ServerSide/ApiTests directory.

/ci-test-limit


Fix ingress examples for the new API

The Ingress resource structure is a little bit different between extensions/v1beta1 and networking.k8s.io/v1, so a few of our examples are now invalid since changing to networking.k8s.io/v1.
Signed-off-by: irbekrm<EMAIL_ADDRESS>

/lgtm
/approve
/ok-to-test


Make sequence number big-endian

Fix #2166.
Signed-off-by: Steven Bellock<EMAIL_ADDRESS>

@jyao1 tests need to be fixed but you can start reviewing the change.

We need wait for feedback from SPDM WG.


chore/deprecate prs

ci: add codecov
ci(codecov): build before tests
chore: deprecate prs

Codecov Report

Merging #34 (a210a07) into main (4c6b279) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head a210a07 differs from pull request most recent head 839a7d6. Consider uploading reports for the commit 839a7d6 to get more accurate results

@@           Coverage Diff           @@
##             main      #34   +/-   ##
=======================================
  Coverage   15.30%   15.30%
=======================================
  Files          37       37
  Lines        1477     1477
  Branches      101      101
=======================================
  Hits          226      226
  Misses       1232     1232
  Partials       19       19

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 4c6b279...839a7d6. Read the comment docs.


Fix Fix memtable memory limiter tigger flush log

Proposed changes
Fix memtable memory limiter tigger flush log, "reached the load hard limit" is error.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


[AMHACK][Intermittent] WARN -  Going to buffer response body of large or unknown size when login to API publisher with tenant domain

Description:
Intermittently observed server warning when log in to API Publisher with tenant user
Suggested Labels:
Bug
Affected Product Version:
APIM wum updated - wso2am-<IP_ADDRESS>0928473100.zip
OS, DB, other environment details and versions:
Standalone
DB - H2
Browser - Chrome Version 58.0.3029.96 (64-bit)
Steps to reproduce:

Log in to management console
Create tenant domain
Log in to API Publisher with tenant domain

Observations
Observed the following warning logs in the terminal
[2017-11-21 19:01:47,581]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}
[2017-11-21 19:01:47,814]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}
[2017-11-21 19:01:48,024]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}
[2017-11-21 19:01:48,126]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}
[2017-11-21 19:01:48,234]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}
[2017-11-21 19:01:48,445]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}
[2017-11-21 19:01:48,624]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}
[2017-11-21 19:01:48,773]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}
[2017-11-21 19:01:48,849]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}
[2017-11-21 19:01:48,954]  WARN -  Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. {org.apache.commons.httpclient.HttpMethodBase}

The warning means that a response body could potentially be very large (such as a search returning a large response, etc.).
This warning message is not visible in the latest AM 2.6.0 and it is fixed in this verion.


The action items on the context menu of one SAS attached storage account are incorrect

Storage Explorer Version: 1.25.0-dev
Build Number: 20220608.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Monterey 12.4 (Apple M1 Pro)
Architecture ia32\x64
How Found: From running test cases
Regression From: Previous release (1.24.2)
Steps to Reproduce

Select one storage account -> SAS attach one storage account.
Right click the attached storage account.
Observe the action items on the context menu are correct.

Expected Experience
The action items on the context menu are correct.

Actual Experience
The action items on the context menu are incorrect.

Additional Context

This issue reproduces for storage accountS connected by 'Connection string (SAS) & Shared access signature URL (SAS)'.
An error dialog pops up when refreshing the 'Queues/Tables' node under the SAS attached storage account.
The screenshot for Queues:

Verified this issue on the build main 20220609.2. Fixed.


Clarify handling of logger, error and exceptions

SCT has used several ways to communicate and raise exceptions (sct_utils.printv, sct_utils.log, logger module, sct_utils.class Error, try/except). The purpose of this issue is to establish convention and update the code and wiki accordingly.
A prototype of the proposed solution is available here.
Fixes #2213

Typo, + have you checked all the callers of printv()?

Not yet, any particular reason for doing so? (the current goal is to come back to the pre-logging state of printv, i.e., use print with color feature, which was working fine).

the current goal is to come back to the pre-logging state of printv, i.e., use print with color feature, which was working fine
OK


Something's fishy about the AmphibiaWeb resource

@eliagbayani   AmphibiaWeb is a connector, right?  Something went wrong with this resource.  It looks like a lot of the species articles are now associated with genus names, so we have multiple genera listed in their hierarchy.  For example, check out this page: http://eol.org/pages/45883912/overview
There are 7 different versions of the Fejervarya page, each with content for a different Fejervarya species.  Could you please check if the problem is on their end or ours?  Thanks!

Sure, will check this one today @KatjaSchulz .

I saw the problem. The XML structure of their XML dump has changed.
They’re now using genus+specificepithet instead of genus+species in the past.
I’ve now updated the connector, committed it, sent pull-request.
I’ve also now uploaded latest EOL DWC-A resource to our server so we can re-harvest this anytime to fix the problem the soonest.
Resource now ready for the harvest queue.
Statistics
http://eol.org/schema/reference/reference:4920
http://eol.org/schema/agent/agent:578
http://purl.org/dc/dcmitype/Text: 7694
http://rs.tdwg.org/dwc/terms/taxon:2172
http://rs.gbif.org/terms/1.0/vernacularname:1955

Thanks Eli!

Apparently, AmphibiaWeb has been reharvested, but this problem persists.  We still have multiples of genera in this hierarchy: http://eol.org/pages/45884370/names
Possibly the wrong version of the resource was harvested?

Hi @JRice , may I request loading of my pull-request here:
https://github.com/EOL/eol_php_code/pull/154
Code here will fix the problem on AmphibiaWeb. Thanks.

Hi @KatjaSchulz , I've uploaded the correct dwc-a resource before but that seems not enough. The old connector overwrote it. I will just run the connector from server once latest connector is loaded. Will keep an eye on this one. Thanks.

Thanks @JRice, I saw the changes now reflected.

I ran the connector from the server and correct dwc-a resource now generated.
Hi @jhammock, may we request another queuing of this resource:
http://eol.org/content_partners/7/resources/21
We should be able to get the right resource this time. Thanks.

Everything looks great now.  Species have their own pages. Thanks!

@KatjaSchulz @jhammock
Glad to hear that. Thanks everybody.


Add a new contiguous allocator strategy option

Also fix an error in port allocator.  I'm using contiguous allocation for a UID
and SELinux label allocator in OpenShift but will be backporting it post 1.0.
@justinsb something I missed during your code review or @thockin

I'm very wary of reusing IPs or ports too quickly... my fear is that pod2 comes up on the same IP or port as pod1 was on, and sees traffic meant for pod1.
Admittedly randomizing just makes the problem less likely, but this strategy will expose it every time if it is a genuine problem.  As for whether that is a good thing or a bad thing, I don't know :-)
No objection to the code, though I don't really get where it is going.
And thank you for catching the dropped err retval (again!)

This doesn't change existing call sites, it just adds the new option.  For security related allocations which are much larger than 10k (average service subnet) it limits the amount of contiguous storage needed.  For instance, the selinux allocator with two labels is 535k possible values.
I would rather expose overlap issues early for security related items.  That's much more dangerous.

On May 28, 2015, at 1:15 AM, Justin Santa Barbara<EMAIL_ADDRESS>wrote:
I'm very wary of reusing IPs or ports too quickly... my fear is that pod2 comes up on the same IP or port as pod1 was on, and sees traffic meant for pod1.
Admittedly randomizing just makes the problem less likely, but this strategy will expose it every time if it is a genuine problem. As for whether that is a good thing or a bad thing, I don't know :-)
No objection to the code, though I don't really get where it is going.
And thank you for catching the dropped err retval (again!)
—
Reply to this email directly or view it on GitHub.

@smarterclayton do you hope to get this into 1.0?

Yes, it introduces no changes to running function, and makes reuse easier.  It should be a simple merge.

On Jun 1, 2015, at 12:03 PM, Eric Tune<EMAIL_ADDRESS>wrote:
@smarterclayton do you hope to get this into 1.0?
—
Reply to this email directly or view it on GitHub.

OK, thanks for clarifying.  LGTM, though the PR where we switch this on will have some interesting security discussions!

Here's how the contiguous allocator is being used today: https://github.com/openshift/origin/pull/2544/files#diff-3999d64b0b8fa9423b47f9feb61db2b0R1007

On Jun 1, 2015, at 12:26 PM, Justin Santa Barbara<EMAIL_ADDRESS>wrote:
OK, thanks for clarifying. LGTM, though the PR where we switch this on will have some interesting security discussions!
—
Reply to this email directly or view it on GitHub.

LGTM, just a nit I don't understand.

LGTM


Fixed incorrect import under python3

Fixed issue when importing tensorframes under python3.

cc @thunterdb

@mariusvniekerk I merged a separate PR that also includes continuous integration. Thanks for your fixes!

Thanks


python311Packages.uproot: 5.3.1 -> 5.3.2

Description of changes
Changelog: https://github.com/scikit-hep/uproot5/releases/tag/v5.3.2
cc @veprbl

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

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

10 packages built:

python311Packages.coffea
python311Packages.coffea.dist
python311Packages.dask-awkward
python311Packages.dask-awkward.dist
python311Packages.mplhep
python311Packages.mplhep.dist
python311Packages.uproot
python311Packages.uproot.dist
python312Packages.uproot
python312Packages.uproot.dist

Result of nixpkgs-review pr 299315 run on aarch64-darwin 1

10 packages failed to build:

python311Packages.coffea
python311Packages.coffea.dist
python311Packages.dask-awkward
python311Packages.dask-awkward.dist
python311Packages.mplhep
python311Packages.mplhep.dist
python311Packages.uproot
python311Packages.uproot.dist
python312Packages.uproot
python312Packages.uproot.dist

Result of nixpkgs-review pr 299315 run on x86_64-darwin 1

10 packages failed to build:

python311Packages.coffea
python311Packages.coffea.dist
python311Packages.dask-awkward
python311Packages.dask-awkward.dist
python311Packages.mplhep
python311Packages.mplhep.dist
python311Packages.uproot
python311Packages.uproot.dist
python312Packages.uproot
python312Packages.uproot.dist

Result of nixpkgs-review pr 299315 run on x86_64-darwin 1

4 packages failed to build:

python311Packages.coffea
python311Packages.coffea.dist
python311Packages.dask-awkward
python311Packages.dask-awkward.dist

6 packages built:

python311Packages.mplhep
python311Packages.mplhep.dist
python311Packages.uproot
python311Packages.uproot.dist
python312Packages.uproot
python312Packages.uproot.dist

Result of nixpkgs-review pr 299315 run on aarch64-darwin 1

4 packages failed to build:

python311Packages.coffea
python311Packages.coffea.dist
python311Packages.dask-awkward
python311Packages.dask-awkward.dist

6 packages built:

python311Packages.mplhep
python311Packages.mplhep.dist
python311Packages.uproot
python311Packages.uproot.dist
python312Packages.uproot
python312Packages.uproot.dist

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

10 packages built:

python311Packages.coffea
python311Packages.coffea.dist
python311Packages.dask-awkward
python311Packages.dask-awkward.dist
python311Packages.mplhep
python311Packages.mplhep.dist
python311Packages.uproot
python311Packages.uproot.dist
python312Packages.uproot
python312Packages.uproot.dist

Result of nixpkgs-review pr 299315 run on aarch64-linux 1

10 packages built:

python311Packages.coffea
python311Packages.coffea.dist
python311Packages.dask-awkward
python311Packages.dask-awkward.dist
python311Packages.mplhep
python311Packages.mplhep.dist
python311Packages.uproot
python311Packages.uproot.dist
python312Packages.uproot
python312Packages.uproot.dist

Thank you
!


False Negative on Conventional PR?

Overview
I'm using Conventional PR to prevent commits with bad messages to be merged to the main branch. I'm using the default conventional commit pattern
^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)
However, it seems commit messages like test commit is still considered to be valid. It seems like the conventional PR doesn't filter commit messages correctly.
Expected Behavior
The pull request should be considered as invalid, since test commit does not conform the regex.
Actual Behavior
The pull request is considered as valid.

Thanks for filing an issue!
The pattern you submitted seems fine, can you post the action workflow file here?

Sure, here you go
name: Check PR semantics

on:
  pull_request_target:

jobs:
  cpr:
    runs-on: ubuntu-latest
    steps:
      - name: Check PR semantics
        uses: Namchee/conventional-pr@latest
        with:
          access_token: ${{ secrets.ACCESS_TOKEN }}
          title_pattern: ^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)

/add-knowledge

/delete-knowledge

Seems like the LLM keeps finding the solution for no reason.
For comparison, here's ChatGPT direct answer:
Identify the solution from the following problem-solution conversation.

Present the solution in form of simple suggestion. Interaction between conversation participants will be separated by '---'.

Conversation have a title or a link to a reproduction attempt that can be used to understand the context of the conversation.

If no solutions in the conversation are found, reply with \`Not Found\`.

Title: False Negative on Conventional PR?

---
@Namchee: ## Overview

I'm using Conventional PR to prevent commits with bad messages to be merged to the main branch. I'm using the default conventional commit pattern

`^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)`

However, it seems commit messages like `test commit` is still considered to be valid. It seems like the conventional PR doesn't filter commit messages correctly.

### Expected Behavior

The pull request should be considered as invalid, since `test commit` does not conform the regex.

### Actual Behavior

The pull request is considered as valid.
---
@Namchee: Thanks for filing an issue!

The pattern you submitted seems fine, can you post the action workflow file here?
---
@Namchee: Sure, here you go

```yaml
name: Check PR semantics

on:
  pull_request_target:

jobs:
  cpr:
    runs-on: ubuntu-latest
    steps:
      - name: Check PR semantics
        uses: Namchee/conventional-pr@latest
        with:
          access_token: ${{ secrets.ACCESS_TOKEN }}
          title_pattern: ^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)

ChatGPT: Not Found

This is due to Output Indicator Solution:  that forces the model to try as hard as possible to find the solution that doesn't exist yet.


Adding copy current address functionality

I have added a basic way to copy the current addresses for easy multi-address testing through smart contracts. Instead of using the toast library, I am just utilizing windows.alert for low dependency problems and to notify if the user copied the address and what address. Please let me know if something I should modify or add.

@nikita-fuchs I have pushed new changes which makes the copy button responsive and available at 2 positions as discussed on discord. I have also corrected package.json for any dependency problem that I found during the process. Please let me know if something needs to be updated.
thank you.

Implemented in https://github.com/aeternity/fire-editor/commit/c95f7f79d1e4b060163d29d2aa14a175dc7333f6, thanks a lot ! ping me on discord please, I owe you some good feedback ! :)


Add watches for CloudStack resources to controller

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve


[$1000] Duplitcate record is created on LHN when sending an IOU

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Precondition: Sender and recipient shouldn't have an existing chat
Action Performed:

Sign in with account A
Send an IOU to account B
Shift to the tab where account B is signed in
Observe two LHN records are created for Sender account A, and Recipient account B on the sender and recipient side

Expected Result:
Duplicate records shouldn't be created on LHN
Actual Result:
Duplicate records are created on LHN
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.14-9
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/bb540e07-5ecb-4897-9b99-2af70b707527
https://github.com/Expensify/App/assets/43996225/176dbfc8-12cf-469d-be17-6c8d698746e5
Expensify/Expensify Issue URL:
Issue reported by: @natnael-guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684140542624389
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e6465336f99ff325
Upwork Job ID:<PHONE_NUMBER>223650304
Last Price Increase: 2023-05-16

Looks good!

@slafortune I think there is a similar issue raised on this GH issue  and it was agreed that it is an expected behavior to have a duplicate chat in LHN

@slafortune I think there is a similar issue raised on this GH issue  and it was agreed according to this comment that it is an expected behavior to have a duplicate chat in LHN

Thanks @Natnael-Guchima, this is expected behavior now, closing it out since the linked issue will update the test rails


Upgrade to sbt-native-packager 1.1.1. Fixes #76.

The upgrade includes this fix https://github.com/sbt/sbt-native-packager/pull/169

Just tested - this also fixes https://github.com/sbt/sbt-launcher-package/issues/28.

Didn't mean to close.

LGTM


Fixed UI issues of neetoEditor on a neetoUI Pane

Fixes #99

Increased z-index of suggestion popups to appear above neetoUI Pane component: mentions, emoji suggestion, emoji picker, variables, slash commands, and bubble menu.
Removed position: relative from neetoUI button component.

@amaldinesh7 _a please have a look: https://vimeo.com/657373699/6579a3a5c7
cc: @rishavkr08

@goutham-subramanyam _a Could you please review the changes?


Update VersionedLayerClient and VolatileLayerClient

Update error handling strategy in the getData method for incorrect quadKey for VersionedLayerClient and VolatileLayerClient
Add unit tests to handle mentioned cases

Resolves: OLPSUP-9376
Signed-off-by: ashevchu<EMAIL_ADDRESS>

Codecov Report

Merging #163 into master will increase coverage by 0.1%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master    #163     +/-   ##
========================================
+ Coverage    64.8%   64.9%   +0.1%
========================================
  Files          51      51
  Lines        1344    1344
  Branches      156     158      +2
========================================
+ Hits          871     873      +2
  Misses        437     437
+ Partials       36      34      -2

Impacted Files
Coverage Δ

...dataservice-read/lib/client/VolatileLayerClient.ts
96.3% <100%> (+1.8%)
:arrow_up:

...ataservice-read/lib/client/VersionedLayerClient.ts
95.6% <100%> (+1.4%)
: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 c4a323f...00e8384. Read the comment docs.


Added react-router v4 with async load of components

Hi @Kikobeats I have added to the boilerplate react-router v4, I have added async load components for routing with needed (code splitting). I have added a NotMatch route too (https://reacttraining.com/react-router/web/example/no-match)
I would like to add in a future a more consistent router file.

Done @Kikobeats !! I will work this week i18n translations and a better code splitting with sass/less/css for production.

In a future you could need two entry points, dont you think?

make sense 👍

Need to add react-router-dom as dependency!

I need a little of time for understand better this PR.
Until this moment this project was feedback for another project:
https://github.com/windtoday/windtoday-marketplace
while I explore a feature, I add the feature in the boilerplate.
Definetly code splitting is 👌, but I'm a completly noob (because currently in my project I don't need it, I have just one view)
so sorry if I don't merge this quickly, I want to explore it 😄

Of course!! I will try docuemnt in a better way, next week ;) dont worry!!
On Sat, 18 Mar 2017 at 12:47, Kiko Beats<EMAIL_ADDRESS>wrote:

I need a little of time for understand better this PR.
Until this moment this project was feedback for another project:
https://github.com/windtoday/windtoday-marketplace
while I explore a feature, I add the feature in the boilerplate.
Definetly code splitting is 👌, but I'm a completly noob (because
currently in my project I don't need it, I have just one view)
so sorry if I don't merge this quickly, I want to explore it 😄
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Kikobeats/react-boilerplatinum/pull/72#issuecomment-287539293,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWseXYpohtVAqYELq5NtYgIFswajAovks5rm8RDgaJpZM4MgfYO
.

Now with project wiht jquery is another project 😂

This is just for testing ;) I don't know why this was a pull request!! hahahaha


Feature : Option to limit what controls a user can have when building form

Is there a possibility to hide certain controls from the designer? For example, I might not want to give the user access to a calendar/file uploder or something else. if there is a feature in global configuration that would be great. don't you think?
Looking at the current documentation it is not possible out of the box

@mkgn atm VueFormBuilder only has some basic permissions. Is this one really needed? Looks to me, like specific business requirements from your app.
In my opinion, the designer should be able to use all controls, if you don't want them to use some specific controls (because of any reason), then you can give them a note, which is totally better and VueFormBuilder doesn't need to add more checking logic.
VueFormBuilder is born to do its best job - Configure and Render the Form. Feel free to fork this project and extend it by your need.
Thanks


Minor doc fixes

What does this PR do?
Fixed #4650, part of #5099, and some other doc fixes I found while reading.

Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?
Make sure you had fun coding 🙃

@tchaton @williamFalcon mind review?

@tchaton mind review as code-owner? 🐰


mupdf: Add Darwin application

Description of changes
This adds the desktopToDarwinBundle hook so an application is synthesize for Darwin. This would allow association PDF files to open with MuPDF, for example. A nice quality of life improvement for Darwin users.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 165118 run on aarch64-darwin 1

1 package marked as broken and skipped:

beamerpresenter

9 packages failed to build:

img2pdf (python39Packages.img2pdf)
mcomix3
mupdf
ocrmypdf (python39Packages.ocrmypdf)
paperless-ng
python310Packages.img2pdf
python310Packages.ocrmypdf
python310Packages.pikepdf
python39Packages.pikepdf

Result of nixpkgs-review pr 165118 run on aarch64-darwin 1

1 package marked as broken and skipped:

beamerpresenter

3 packages failed to build:

ocrmypdf (python39Packages.ocrmypdf)
paperless-ng
python310Packages.ocrmypdf

6 packages built:

img2pdf (python39Packages.img2pdf)
mcomix3
mupdf
python310Packages.img2pdf
python310Packages.pikepdf
python39Packages.pikepdf


[modify] event part calendar event_display

Coverage decreased (-0.6%) to 77.933% when pulling 946b06f53ed34ac7b3fc28f1667dd69910c9ef68 on ShinjiTanimoto:calendar into cd12e6a9c9728e706f20f14375d7118cf05d016e on shirasagi:master.


[Deploy] Outlook

 Similar to Office 365 Outlook
Service
Outlook Live
Link to your repository
https://github.com/woutervs/MeetFranz-Outlook
Additional Information
Notifications on inbox work

I've discovered a few issues when checking the recipe:

package.json: Change name to: Outlook
icon: Please provide a png as well
license: is referencing Adam Birds

Updated and checked in.

Deployed, thanks for your contribution.


Error during Routing using FastRoute

While trying to use Openlane flow for the Aardonyx SoC designed at IIT Madras, there is a crash encountered during the routing process using FastRoute.
The error message reads as below:
terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
[ERROR]: during executing: "openroad -exit /openLANE_flow/scripts//openroad/or_route.tcl |& tee >&@stdout /openLANE_flow/designs/aardonyx/runs/10-08_13-50//logs/routing/fastroute.log"
[ERROR]: Last 10 lines:
child killed: SIGABRT
FastRoute Log:
fastroute.log
Configuration details:
set ::env(CLOCK_PERIOD) 11
set ::env(ROUTING_STRATEGY) 0
set ::env(GLB_RT_ADJUSTMENT) 0
set ::env(GLB_RT_L1_ADJUSTMENT) 0.99
set ::env(GLB_RT_L2_ADJUSTMENT) 0
set ::env(GLB_RT_MINLAYER) 1
set ::env(GLB_RT_MAXLAYER) 6
set ::env(GLB_RT_UNIDIRECTIONAL) 1
set ::env(GLB_RT_ALLOW_CONGESTION) 0
set ::env(GLB_RT_OVERFLOW_ITERS) 50
SoC Verilog Source Directory:
aardonyx_soc.tar.gz
Kindly look into the issue. Do let me know if I need to provide any further details.

You're running out of RAM.

@smunaut Is there any workaround for this?

Thanks for the info @smunaut . I circumvented the crash by increasing the swap size of my Ubuntu system.


Request for the pca_path

Hi!
Thank you very much for open-sourcing this work! It seems that pca_path is necessary for training diffusion model
    if pca_path is not None:
        self.pca = PCA(pickle.load(open(pca_path, "rb")))

    # post pca

    if not self.target == "pca":
        a_center_traj = self.pca.forward(
            self.pca.forward(a_center_traj.reshape(a_center_traj.shape[0], -1)),
            inverse=True
        ).reshape(a_center_traj.shape)

but I don't know how to get it. Could you please provide it?

Here in the scripts, we provide tools for generating pca parameters and an example parameter generated from part of training set of WOMD.


Upgrade on code for clarify

Hello Alba4k,
I made upgrade on your code.
This is my upgrade

Explanatory Comments: Added comments to clarify the purpose of each section, making it easier to understand.
Emoji in the Title: Included a 🚀 emoji in the project description to give it a modern and visual appeal.
Formatting and Structure: Enhanced indentation and separated various sections with whitespace for better readability and navigation.

Improvements Made

Explanatory Comments: Added comments to clarify the purpose of each section, making it easier to understand.
# This Nix expression imports the flake-compat package
(
  import
  (
    let
      # Load the flake.lock file and parse it as JSON for dependency management
      lock = builtins.fromJSON (builtins.readFile ./flake.lock);
    in
      # Fetch the tarball of flake-compat using the locked revision and its SHA256 hash
      fetchTarball {
        url = "https://github.com/edolstra/flake-compat/archive/${lock.nodes.flake-compat.locked.rev}.tar.gz";
        sha256 = lock.nodes.flake-compat.locked.narHash;
      }
  )
  # Specify the current directory as the source for the import
  { src = ./.; }
)
.defaultNix

Consistent Indentation: Enhanced indentation for better readability.

Descriptive Variable Names: Maintained clear naming conventions for clarity.

Improvements Made

Enhanced Structure: Organized sections with clearer headings.
Descriptive Bullets: Added bullet points for better readability and quick scanning.
Emojis: Included relevant emojis to enhance visual appeal and emphasize changes.

Changes and Improvements:

Comments: All comments have been translated to English for better understanding.
Reorganization: Some parts of the code have been reorganized for improved readability.
Use of //: The union operator // is used to merge legacy packages more clearly.
System Logic: The logic for assigning legacy packages based on the current system has been simplified.

Changes and Improvements:

Comments: Added comments to explain the purpose of each section, making it easier to understand the code.
Clarity: The structure remains the same, but the comments help clarify the intent behind each line.
Maintainability: The use of inherit statements is preserved for flexibility, allowing for easy updates or changes in the future.

Changes and Improvements Made:

Size Constants: Defined constants for string sizes (CAPACITY_MAX_LEN, STATUS_MAX_LEN, BUFFER_SIZE) to make the code more readable and easier to modify.

Memory Management: Ensured that the strings are properly null-terminated to avoid potential buffer overflow issues.

Improved Comments: Made the comments clearer and more contextual, better explaining the sections of the code.

Result Formatting: Simplified the logic for formatting the result, improving clarity.

Use of tolower: Maintained the lowercase conversion for the battery status but slightly restructured the code to enhance readability.

Changes and Improvements Made in bios.c :

Buffer Size Constant: Defined a constant (BUFFER_SIZE) for easier adjustments and improved code readability.

Memory Management: Removed dynamic memory allocation in favor of stack-allocated buffers for vendor and version, reducing memory management overhead and potential leaks.

String Reading: Replaced manual reading and null termination with fgets, which simplifies the code and ensures safety against buffer overflows.

Newline Removal: Added logic to remove the newline character from the read strings to ensure clean output.

Error Handling: Maintained clarity in error handling with concise checks for data availability.

call me up when this is ready to be merged

Additionally, you may want to define buffer size in a different header (like info.h) instead of per-file as it will be constant
and you would also be able to use it in main.c

I have replaced old code for new commit

I made a fix for a couple of vulnerability in cpu.c:
[{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 63,
"startColumn": 18,
"endLineNumber": 63,
"endColumn": 26
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strchr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 67,
"startColumn": 22,
"endLineNumber": 67,
"endColumn": 30
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 102,
"startColumn": 22,
"endLineNumber": 102,
"endColumn": 30
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 104,
"startColumn": 22,
"endLineNumber": 104,
"endColumn": 30
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 106,
"startColumn": 22,
"endLineNumber": 106,
"endColumn": 30
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 108,
"startColumn": 22,
"endLineNumber": 108,
"endColumn": 30
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 110,
"startColumn": 22,
"endLineNumber": 110,
"endColumn": 30
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 112,
"startColumn": 22,
"endLineNumber": 112,
"endColumn": 30
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/DerefNull",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Dereference of a NULL Pointer: A pointer is possibly assigned the return value of a standard library...",
"source": "Snyk Code",
"startLineNumber": 115,
"startColumn": 10,
"endLineNumber": 115,
"endColumn": 13
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 119,
"startColumn": 26,
"endLineNumber": 119,
"endColumn": 34
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 121,
"startColumn": 31,
"endLineNumber": 121,
"endColumn": 39
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strstr after it may already have been freed with...",
"source": "Snyk Code",
"startLineNumber": 123,
"startColumn": 31,
"endLineNumber": 123,
"endColumn": 39
},{
"resource": "/c:/Users/maule/Desktop/Github/albafetch/src/info/cpu.c",
"owner": "generated_diagnostic_collection_name#4",
"code": {
"value": "cpp/UseAfterFree",
"target": {
"$mid": 1,
"path": "/scan-using-snyk/snyk-code/snyk-code-security-rules",
"scheme": "https",
"authority": "docs.snyk.io"
}
},
"severity": 4,
"message": "Use After Free: Use after free. cpu_info is used in strncpy after it may already have been freed wit...",
"source": "Snyk Code",
"startLineNumber": 127,
"startColumn": 19,
"endLineNumber": 127,
"endColumn": 27
}]


Making go back button in alert section working and it will take us to home page.

@surajondev  pls assign it to me and letter on I will add more section .

Not the only one with issues, the Cards go back also doesn't work, if you are able to fix it, would be cool. I tried fixing it myself but I am quite a mess with links xD

@xMrAfonso I will be happy to help.