Hub tries to create PR against upstream remote automatically. Origin & Upstream owned by same owner.

So I've been reading and found that hub does some magic using the "upstream" remote as the default remote for doing a PR. In all the cases where someone has asked about this, they are told to use the verbose OWNER:branch syntax... In this case, my organization owns both the upstream AND the origin repositories. The usecase is like this... We have a custom "Pantheon Upstream" for our drupal sites. We also build our drupal sites. I'm trying to automate the pull of the pantheon upstream into all the sites. It so happens I use the name "upstream" and was expecting this to go to origin or at least the remote the branch was tracking against...
Is there any way to specify the remote specifically or at least the repository?
This is different than #1618 and the comment in https://github.com/github/hub/issues/381#issuecomment-23617252 is flat out wrong when you have this usecase.

FYI, the work around here is rename my remotes from upstream to drupal_upstream and it goes about it's business using origin. Since this is scripted... this isn't a big deal but usability and workflow that has been establish has to change for the tool to work.

Do you have at least hub version 2.7.0? If "upstream" is pointing to a repository that's not on GitHub, then it will be ignored. If Drupal upstream is indeed a URL to GitHub, then it's true: the only way for you to choose a different remote, unfortunately, is the -b OWNER:branch syntax (or rename the "upstream" remote, which I don't recommend because it breaks your existing conventions).
I hope that some sort of configuration option exists for this in the next release, but I haven't yet been inspired on how to properly implement this.

Yes both repos are on github under the same owner "fourkitchens" in this case. I'll make it work and only have the remote name change for scripted instances and just make sure it's a documented process that of they use hub for cli PRs that this is the current case.
For clarity a facsimile of my situation is as follows
Upstream is git@github.com:fourkitchens/upstream.git
Origin is git@github.com:fourkitchens/origin.git

Any chance this is getting picked up again? I'm running into the exact same issue, but simply renaming upstream isn't a desirable workaround for me. Maybe this could be solved by a simple flag eg. hub pull-request --force-remote "origin" as an intermediary solution?
Thanks.


fantastic Microsoft advertising mail

I think an important note is missing, any time after creating a group on SharePoint, Microsoft send to all people of this group a fantastic advertising e-mail to congratulate with all this people for buying a 365 lincenses, no matter if in this group you have thousands of users.

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

ID: 5f7a4070-1be8-5f1f-0092-68fb6b9e2305
Version Independent ID: cd34312f-b507-affe-555e-1e0c63e7d494
Content: Rules for dynamically populated groups membership - Azure AD
Content Source: articles/active-directory/enterprise-users/groups-dynamic-membership.md
Service: active-directory
Sub-service: enterprise-users
GitHub Login: @curtand
Microsoft Alias: curtand

@alessio-businaro
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for the feedback and apologies for the inconvenience! Welcome emails are enabled by default but you should be able to disable these via the  -UnifiedGroupWelcomeMessageEnabled switch.
https://docs.microsoft.com/en-us/powershell/module/exchange/set-unifiedgroup?view=exchange-ps
I made a pull request to update the instructions and will leave it open for review by @curtand.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/186666


FermionicOp initializes successfully but throws IndexError on method call

Environment

Qiskit Nature version: e39594b8ede4533af7d22b2b121f29d624e569ed
Python version: 3.9
Operating system: RHEL 8.5

What is happening?
FermionicOp initializes successfully but throws IndexError on method call.
How can we reproduce the issue?
Code:
op = FermionicOp([("+_1", 1.0), ("", 1.0)])
print(op)

Result:
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-58-3a1c34389858> in <module>
      1 op = FermionicOp([("+_1", 1.0), ("", 1.0)])
----> 2 print(op)

~/projects/qiskit-nature/qiskit_nature/operators/second_quantization/fermionic_op.py in __str__(self)
    370         )
    371         ret = "  " + "\n+ ".join(
--> 372             [f"{coeff} * ( {label} )" if label else f"{coeff}" for label, coeff in self.to_list()]
    373         )
    374         if FermionicOp._truncate and len(ret) > FermionicOp._truncate:

~/projects/qiskit-nature/qiskit_nature/operators/second_quantization/fermionic_op.py in to_list(self, display_format)
    464                 for label_data, coeff in self._data
    465             ]
--> 466         return self._to_dense_label_data()
    467
    468     def to_matrix(self, sparse: Optional[bool] = True) -> Union[csc_matrix, np.ndarray]:

~/projects/qiskit-nature/qiskit_nature/operators/second_quantization/fermionic_op.py in _to_dense_label_data(self)
    589                 char = "+" if fer_label.is_creation else "-"
    590                 index = fer_label.index
--> 591                 if (label_list[index], char) in _ZERO_LABELS:
    592                     break
    593                 label_list[index] = _MAPPING[(label_list[index], char)]

IndexError: list index out of range

What should happen?
No error should occur.
Any suggestions?
It seems to have something to do with the identity term (empty string label). If the register length is specified, then it works fine, e.g.
op = FermionicOp([("+_1", 1.0), ("", 1.0)], register_length=2)
print(op)

I'm actually surprised that the initialization of FermionicOp([("+_1", 1.0), ("", 1.0)]) is working. It should not.
When using sparse labels, you have to specify register_length, otherwise the operator cannot know it's size. Thus, your suggestion at the end is actually the only way that this should work.
I'm leaving this open as a bug until we raise the correct error upon initialization.

I don't think you should be forced to specify a register length when initializing a FermionicOp using sparse labels.

The register_length is supposed to be inferred automatically (the largest index + 1), so I assume it is not working.
In any case (regardless of whether it is inferred or given,), register_length is required.


Add AI based image tagging extension

AI Image Tagging
This extension enables automatic tagging of images. To use, configure it in the
Sidebar of a content type that includes two fields at minimum:

A Media field to serve as the image source
A Short text, list field to store the generated tags

To use, just add an image to your image field and click Auto-tag image. The generated
tags should be added to your tags field once ready.

In general it would be nice to use prettier for the consistent codestyle: https://gist.github.com/Mohamed3on/840b34ecb7e9abf06ace035183b7f1fc


Send '100 Continue' response automatically via Server

As preparation for the upcoming PSR-7 feature, this PR will remove the expectsContinue and writeContinues methods from the Response and Request classes, because it is not compatible with the ResponseInterface and the RequestInterface of PSR-7.
The server sends now a the HTTP/1.1 100 Continue response automatically.
The possibility to handle this behavior is removed, but will be added again after the PSR-7 implemantation is completed.
Some of the details are already discussed in #109.

Ping @clue . Updated the documentation.


Dapr Workflow pacakge || Update the dependency 'System.Text.Json' to the latest version

Describe the proposal
Current scenario
Given a solution in .NET,
when the user executes the following command
dotnet add package Dapr.Workflow --version 1.14.0

then the system shows a warning
warn : NU1903: El paquete "System.Text.Json" 6.0.0 tiene una vulnerabilidad de gravedad alta conocida
Workaround
Update the package with the command:
dotnet add package System.Text.Json

PS: Albert0 (from Discord).

This is already covered in the master branch as part of the .NET 9 support.


curl user reports timeouts on receiving response

As reported in https://github.com/curl/curl/issues/11644, curl with quiche v0.17.2 sometimes times out after sending a request to an NGINX server. There is a qlog file attached to the issue which might shed some light on what is going on.
Maybe we are holding it wrong in curl. Would appreciate if someone could take a look.

Holding the qlog file agains the light and squinting my eyes, this looks like a broken UDP path where the server never acks any packets beyond the first one. Would you agree? Thanks.

Looking at the supplied qlog, there is no handshake_done message being returned by the server. Not sure why that is happening. That indicates a problem in the server QUIC statemachinery rather than UDP.

Thanks, @LPardue, will forward that to the reporter.

Looks like a simple url, you can try quiche-client to the nginx server to see if it can be isolated to quiche or curl.

User reports that issue also happen for them with curl+ngtcp2. This strongly points to a server issue.
Closing this, thanks for the help!


Feat: 🚀 Prepared addon for Keda

Update workflow to automate the keda readme file creation.

please remove this variable in kube-state-matrics

 please remove this variable in kube-state-matrics

I have not worked on this addons, but I can remove this if gets the permission to remove from the owner of this addon
should I remove?

 please remove this variable in kube-state-matrics

I have not worked on this addons, but I can remove this if gets the permission to remove from the owner of this addon should I remove?

I've worked on it. you can remove it.

KEDA outputs are missing in output.tf, please add them.

KEDA outputs are missing in output.tf, please add them.

Done


Adding Mouseover to Adaptive Card Button

Hi Team, Do we have a way to add tooltip or mouseover text to the Submit buttons in adaptive card. I know we can do it from the webchat frontend but that will fail in teams. I want something which we can implement directly in Adaptive cards.

@thakursarvesh - It is not currently possible to add tooltips to cards in Teams, but there's a tooltip feature proposed here: https://github.com/microsoft/AdaptiveCards/issues/1788
I will close this as unrelated to Composer

@thakursarvesh - It is not currently possible to add tooltips to cards in Teams, but there's a tooltip feature proposed here: https://github.com/microsoft/AdaptiveCards/issues/1788
I will close this as unrelated to Composer


Sync compiler version with v4-core

Component
General design optimization (improving efficiency, cleanliness, or developer experience)
Describe the suggested feature and problem it solves.
Right now, the solc version of v4-periphery is using is ^0.8.19, however, the solc version in v4-core is ^0.8.20
It caused some inconvenient when we add both repos to the lib of a new repo (by forge install) and import those .sol files from both repos, especially, the interfaces files
This is going to be helpful for improving the developer experience.
Describe the desired implementation.
Change all the compiler versions in v4-periphery to ^0.8.20
Describe alternatives.
No response
Additional context.
We need also to ensure those changes are not going to have a bad impact on the v4-periphery repo, due to it being a small change, I believe it's not going to be a big problem.

closing as we've pinned solc_version = "0.8.24" and evm_version = "cancun" in foundry.toml for both v4-core and v4-peirphery


Quote paths in add package command

PR fixes https://github.com/microsoft/azuredatastudio/issues/19348
We weren't quoting the path so any paths with spaces in them weren't working

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-bindings/src/common/azureFunctionsUtils.ts
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
27943

Relevant Lines:
62182

💛  - Coveralls

@Charles-Gagnon can you confirm whether this issue is fixed: https://github.com/microsoft/azuredatastudio/issues/19348

It does indeed!


Netty - PooledByteBufAllocator and Unpooled.wrappedBuffer method - potential bug?

After allocating some direct buffers and trying them to be combined into a wrapped buffer,
the referenced initial buffers become unusable / freed. Example:
    ByteBufAllocator pbba = PooledByteBufAllocator.DEFAULT;
    BUFFERS.add(0, pbba.directBuffer(32, 32));      // buffer of fixed size  32 bytes - header 1
    BUFFERS.add(1, pbba.directBuffer(128, 128));    // buffer of fixed size 128 bytes - header 2
    BUFFERS.add(2, pbba.directBuffer(256));         // buffer of minimum size 256 (can grow) - for data of various size

                                                    // Combine 2 buffers - indexes: 0 and 2
    BUFFERS.add(3, Unpooled.wrappedBuffer(BUFFERS.get(0), BUFFERS.get(2)));

If we now do:
ByteBuf bb0 = BUFFERS.get(0);
System.out.println(bb0.refCnt());    // returns 0  !!!
bb0.writeBytes(headerPrefix);        // throws exception;   headerPrefix = 4 bytes array

bb0 is shown by debugger as 'freed',  .refCnt() returns 0,  and the next line -  bb0.writeBytes(x) throws exception:
io.netty.util.IllegalReferenceCountException: refCnt: 0
BUT, if we write some data into the buffer before we call the wrappedBuffer(...) method,
all appears to be working fine:
HEADER_BUFFERS.get(0).writeBytes(headerPrefix);   // headerPrefix = 4 bytes array
Unpooled.wrappedBuffer(BUFFERS.get(0), BUFFERS.get(2));
ByteBuf bb0 = BUFFERS.get(0);
System.out.println(bb0.refCnt());              // returns 1  !!!

BUT, since we did not write any data to the 2nd buffer, the problem remains there.
ByteBuf bb2 = BUFFERS.get(2);
System.out.println(bb2.refCnt());              // returns 0  !!!
Perhaps this is a feature to auto-release unused memory, but in this case it presents itself rather as a bug. Hopefully it is something Netty designers/insiders could clear up for us.

@felixunivers I am not sure if I correctly understand the problem but if I understood it correctly you are surprised that calling Unpooled.wrappedBuffer(...) with an "empty buffer" will release the "empty buffer" right away.  I think this works as "designed" as once you call this method the ownership is transferred and in this case it will just release the buffer directly as its empty.
I can see why this may be confusing and could lead to surprising and hard to debug code. Let me do a pr to change this and discuss with the other developers in this pr.

@felixunivers so actually after thinking a bit more about it and reading our java docs again I think it works as expected... Changing it would be surprising to people that expect it to work like documented.
That said we just deprecated these methods in favour of using Unpooled.wrappedUnmodifiableBuffer(...). The new method will work exactly how you expected.
WDYT?

See also https://github.com/netty/netty/pull/8040 and https://github.com/netty/netty/pull/8096

Norman's explanation and further experiencing the design shows that one really has to pay attention to how buffers are used in the code and complement with .retain() where needed.
Unpooled.unreleasableBuffer(...) appears also useful for similar situations. However, it raises a question regarding potential memory leak:
If I declare in my class:
   ByteBuf fixedBuf = Unpooled.unreleasableBuffer(PooledByteBufAllocator.DEFAULT.directBuffer(64, 64));
This should reserve a 64 bytes chunk of off-heap memory. As documented, Netty ignores here the 'release()' and 'retain()' functionality, therefore, the chunk remains allocated throughout the life of my class. What will happen to the allocated off-heap memory chunk once my class gets out of scope? Will JVM/GC release it? If not, or if I want to discard the 'fixedBuf ' programatically, how can I best deallocate the claimed memory blocks for such ByteBuf objects?
Would you please also point to  explanation(s) / example(s) / best practice for avoiding any memory leaks and issues on ByteBuf objects?

Perhaps, when you Netty gentlemen get bored - a "DynamicWrappedBuffer" that reflects all changes in the member buffers dynamically / instantly could be a cool buffer to add. (Likely a bit PITA to design though).

They take contributions FYI. They probably hardly get bored. 😄

Closing as it seems like all is working as designed


Webp images fail to open

Webp images (both animated and still) do not open for some reason, either when specified on command line or in directory opening.

If libwebp is not installed on the system, then the Qt Image Formats add-on (qt5-image-formats-plugins on Ubuntu ) must be installed.

If libwebp is not installed on the system, then the Qt Image Formats add-on (qt5-image-formats-plugins on Ubuntu ) must be installed.


fix: test remove element from max heap failing as expected

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #47401

I tested locally with code provided in the issue, it now fails as expected. I rewrote the code to increase the index at each function call and changed else if isDefined(child2) && etc.. to if and it now passes as expected:
 this.remove = () => {
    const removed = this.heap[1];
    this.heap[1] = this.heap[this.heap.length - 1];
    this.heap.splice(this.heap.length - 1, 1);
    const place = (index) => {
      if (index === this.heap.length - 1) return;
      const child1Index = 2 * index;
      const child2Index = child1Index + 1;
      const child1 = this.heap[child1Index];
      const child2 = this.heap[child2Index];

      if (
        (!isDefined(child1) || this.heap[index] >= child1) &&
        (!isDefined(child2) || this.heap[index] >= child2)
      ) {
        return;
      }
      if (isDefined(child1) && this.heap[index] < child1) {
        [this.heap[index], this.heap[child1Index]] = [
          this.heap[child1Index],
          this.heap[index],
        ];
      }
      if (isDefined(child2) && this.heap[index] < child2) {
        [this.heap[index], this.heap[child2Index]] = [
          this.heap[child2Index],
          this.heap[index],
        ];
      }
      place((index += 1));
    };
    place(1);
    return removed;
  };

Could you share the complete code for your MaxHeap? I'm asking, because while pasting it into current seed code, it passes the test, but remove method doesn't behave correctly with the rest of code.
Changed test is not checking at any point if the element removed from maxheap is actually the greatest one.

Could you share the complete code for your MaxHeap? I'm asking, because while pasting it into current seed code, it passes the test, but remove method doesn't behave correctly with the rest of code.

I copied and pasted adelink's code from issue I only changed the else if and increased the parameter passed into the recursive call, this is what I used:
`const isDefined = (value) => value !== undefined && value !== null;
var MaxHeap = function () {
// Only change code below this line
this.heap = [null];
this.insert = (value) => {
this.heap.push(value);
const place = (index) => {
  const parentIndex = Math.floor(index / 2);
  if (parentIndex <= 0) return;
  if (this.heap[index] > this.heap[parentIndex]) {
    [this.heap[parentIndex], this.heap[index]] = [
      this.heap[index],
      this.heap[parentIndex],
    ];
    place(parentIndex);
  }
};
place(this.heap.length - 1);

};
//
this.print = () => {
return this.heap;
};
//
this.remove = () => {
const removed = this.heap[1];
this.heap[1] = this.heap[this.heap.length - 1];
this.heap.splice(this.heap.length - 1, 1);
const place = (index) => {
  if (index === this.heap.length - 1) return;
  const child1Index = 2 * index;
  const child2Index = child1Index + 1;
  const child1 = this.heap[child1Index];
  const child2 = this.heap[child2Index];

  if (
    (!isDefined(child1) || this.heap[index] >= child1) &&
    (!isDefined(child2) || this.heap[index] >= child2)
  ) {
    return;
  }
  if (isDefined(child1) && this.heap[index] < child1) {
    [this.heap[index], this.heap[child1Index]] = [
      this.heap[child1Index],
      this.heap[index],
    ];
  }
  if (isDefined(child2) && this.heap[index] < child2) {
    [this.heap[index], this.heap[child2Index]] = [
      this.heap[child2Index],
      this.heap[index],
    ];
  }
  place(index+1);
};
place(1);
return removed;

};
// Only change code above this line
};`

Changed test is not checking at any point if the element removed from maxheap is actually the greatest one.

True let me fix that now.

To be honest checking just single value might not be enough to ensure it's always removing the greatest element, and heap is keeping max heap property after the removals.
What do you think about augmenting it a bit:

Instert all elements from val.
Remove from MaxHeap elements one by one, pushing them to new array, checking after each one heap is still isHeap.
When all elements are removed compare if order of removed elements is matching the order from greatest to lowest.

@gikf i agree with you this is the solution that i would follow. verifying the heap property at each step and check if the array of the removed elements is sorted at the end.

To be honest checking just single value might not be enough to ensure it's always removing the greatest element, and heap is keeping max heap property after the removals.
What do you think about augmenting it a bit:

Instert all elements from val.
Remove from MaxHeap elements one by one, pushing them to new array, checking after each one heap is still isHeap.
When all elements are removed compare if order of removed elements is matching the order from greatest to lowest.

sure we can do it, just to clarify so you dont care anymore that the one removed is the max? (removed from the top). because you left that part out of these instructions, but it bothered you before.

To be honest checking just single value might not be enough to ensure it's always removing the greatest element, and heap is keeping max heap property after the removals.
What do you think about augmenting it a bit:

Instert all elements from val.
Remove from MaxHeap elements one by one, pushing them to new array, checking after each one heap is still isHeap.
When all elements are removed compare if order of removed elements is matching the order from greatest to lowest.

Ive done as advised. though as a sidepoint, I believe we dont have to fill an entire array. We can set a variable to infinity and if is not less than the previous just return early. would that not work?

To be honest checking just single value might not be enough to ensure it's always removing the greatest element, and heap is keeping max heap property after the removals.
What do you think about augmenting it a bit:

Instert all elements from val.
Remove from MaxHeap elements one by one, pushing them to new array, checking after each one heap is still isHeap.
When all elements are removed compare if order of removed elements is matching the order from greatest to lowest.

Ok ive done this, see above commit, however rather than filling an array we can just return early if the current is not less than the previous yes?


[Feat] Image occlusion

I honestly don't see how we can do image occlusion without cluttering up the notes a lot. We have to store the position of the occlusion box, say [x1, y1, x2, y2] at the bare minimum, for all boxes we have. And then store scheduling information for each of those occlusions.
Pull requests on this are welcome though.

Oops, closed wrong issue.

I honestly don't see how we can do image occlusion without cluttering up the notes a lot. We have to store the position of the occlusion box, say [x1, y1, x2, y2] at the bare minimum, for all boxes we have.

Couldn't the data be stored in metadata?
Then hide it.
https://forum.obsidian.md/t/can-you-hide-the-metadata-box-when-previewing-a-note-with-yaml-metadata/21931/8
Or use the hider plug-in.

Just spitballing here, but maybe the amount of clutter could be limited by storing the coordinate data as a serialized number like 01234567 instead of an array like [[0, 1, 2, 3], [4, 5, 6, 7]].

I have seen plugins do this
<!--
JSON Data Here
-->

that hides it from view mode.
I have also seen an annotation plugin that stores JSON in a separate file with  extension e.g this could be docname.occ By default these files would be hidden and I suppose the plugin can add it to a hidden file list, if obsidian has one , just to make sure.
Values in the memory would need to be ordered lists or key pair.
JSON the standard supposedly stats the order should be preserved with arrays, however, in practise you cannot not guaranteed the order is preserved between different JSON parsers (even some browsers)  so would probably have to use key pair and have the key state the order.

There is a plugin for logseq that can do image occupation.
it uses a block of properties which a little configuration they can be hidden on the page.

Sorry to necro this, but is there a way to leverage excalidraw or canvas? Make occlusions there, and add some syntax over the occluding element that tells the plugin to include it in the queue?

https://github.com/st3v3nmw/obsidian-spaced-repetition/issues/162
If this feature is added, image occlusion data will be prevented from corrupting the notes, right?

As mentioned in #1035 there is the possibility of integrating this with excalidraw, previously its developer has integrated compatibility with another PDF++ plugin. Although it has the possibility of hiding words easily with text as well as cloze
https://youtu.be/ZnCcMtWj8CA?si=hEOGwlOy5KHEGtj2
But there are no easy, good, hard buttons to save the review data.
Just to mention one possibility, the boxes that will be hidden could be selectable and when clicking the show answer button, said element will lower its opacity to zero, that is, making it invisible

https://github.com/TrillStones/obsidian-image-occlusion/tree/main
A new Solution by Using Excalidraw, templater, and obsidian_to_anki plugins.


Fixed folllow/unfollow not using the correct response in ChannelsService

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: MJRLegends sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


nccopy -w output not written to disk on releases > 4.6.1.

Environment Information
Platform: Archlinux 64-bit, kernel 5.0.0
Build sytstem: autotools
Sample netCDF: attached
Summary of Issue
When using nccopy (v4.6.2-rc1, v4.6.2-rc2, v4.6.2, and v4.6.3) with the -w option on a netCDF classic and netCDF4 files the output is never written to disk. If the input file has compression (i.e. deflate level 1) no message is printed, while using an uncompressed file gives the following error on v4.6.2 (v4.6.3 remains silent):
double free or corruption (!prev)
Aborted (core dumped)"

Steps to reproduce the behavior

configure and make

cd into ncdump directory

./nccopy -w testfile.nc outfile.nc

Sample files
testfile.nc.gz
testfile.nc4.gz
Other files give the same results.
Thanks!

At some point (presumably in 4.6.1) we changed the diskless handling
of flags and added a new NC_PERSIST flag. Looks like we did not fix
all occurrences of the old flag set. Also looks like we need a new/better
test for this option. In any case, I will fix.

Thanks for your reply Dennis. I've double checked and it seems that while 4.6.1 creates the file, it's not doing it in memory, as the output its constantly being written to while the processing is going on, and the memory usage never spikes.

Fixed by issue https://github.com/Unidata/netcdf-c/pull/1366


external access interface

Error description:
I install in aws ec2 server. After that when i use digital ocean server or standalone server everthing work well
Can't start nginx docker container after change IP in .env file to server_ip
Docker version 19.03.6-ce, build 369ce74
Error result
WARNING: Found orphan containers (nginx-proxy_nginx-proxy-letsencrypt_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
Starting nginx-web ...
nginx-gen is up-to-date
nginx-letsencrypt is up-to-date
Starting nginx-web ... error

ERROR: for nginx-web  Cannot start service nginx-web: driver failed programming external connectivity on endpoint nginx-web (f49213a1572d914e3aedaf6cb1966e8693d272eadcf2ca5cd5b4f206201e3ad9): Error starting userland proxy: listen tcp xxx.xxx.xxx.xxx:443: bind: cannot assign requested address

ERROR: for nginx-web  Cannot start service nginx-web: driver failed programming external connectivity on endpoint nginx-web (f49213a1572d914e3aedaf6cb1966e8693d272eadcf2ca5cd5b4f206201e3ad9): Error starting userland proxy: listen tcp xxx.xxx.xxx.xxx:443: bind: cannot assign requested address
ERROR: Encountered errors while bringing up the project.

you need to use the internal ip address in the proxy... check the network using  $ ip address show and get the internal ip address for the ec2.


Question about the sizes of cache L2 & L1

Hi, Dolu.
I succeeded to simulate naxriscv with 4 cpu cores by using litex under your guidance. But later on I noticed that the size of cache L2 doesn't seem to be bigger than L1(I suppose "sram:8kb" represents the size of cache L1).
Could you tell me if I forgot to specify something? Just as a reminder, I used "litex/litex/tools/litex_sim.py --cpu-type=naxriscv --with-sdram --sdram-data-width=64 --sdram-init images/boot.json --cpu-count=4" to simulate.

Hi,
That's ok, that L2 cache is internal to litex and NaxRiscv will not read memory through it. Nax coherent infrastructure has its own l2 coherent cache which is 128 KB by default normaly.
Idealy, i would need to have it disabled automaticaly for Nax/Vexii cpus targets in litex.

Oh, I see. So the "l2" option in this case is actually related the wishbone stuff. I'll disable it. Thank you very much.

Hi ^^
Always 64 bytes

Got it! I'll remember it in my heart : )

Hi, @Dolu1990. Thank you for the help all the time.
I've finished several tests on the naxriscv and everything goes well.
But I do have one question and maybe few more in the future about the cache 😅
Given that l2 has total size as 128kb, cache line size as 64 kb and 8 ways by default, can I say that the number of sets are 256 by default? Do we decide the total size, line size and number of ways of l2 cache first, and then the number of sets can be calculated naturally?

sets are 256 by default?

256 is correct

Do we set the total size, line size and number of ways of l2 cache first,  and then the number of sets can be calculated automatically?

yes right

L1 L2

L1 are 4 way 64 sets
L2 is 8 way 256 sets


Display function arguments after autocomplete

The auto-complete is fantastic, but the one major thing missing is help filling in arguments. Right now, after I press enter to insert a function name, I immediate go to definition on the function to see its arguments. Then I go back and try to fill them in. And this gets tedious if the argument is a complex type with lots of constructor arguments.
It would be really great if you could display these to the user after they auto-complete a function name.

I've implemented the signature help popup in the pull request Fiona referenced (if using ST3 build 3070 or later).  There is also an overloads panel (which works on ST2 also) which shows all signature overloads, and if one is selected, will insert the parameters as snippets that can be typed over.  You can trigger this via Command Palette, or type a '?' inside the opening paren of the argument list.  Details in the README.md.


Fix CHANGELOG on main

The [Unreleased 3.0] section of the CHANGELOG on main had lots of entries for items that were backported and released in 2.5. This commit attempts to fix all these issues so that the [Unreleased 3.0] section only contains items that have not been backported.
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #5942 (9a19e1d) into main (6309611) will decrease coverage by 0.55%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #5942      +/-   ##
============================================
- Coverage     71.31%   70.77%   -0.55%
+ Complexity    59124    58685     -439
============================================
  Files          4770     4770
  Lines        280743   280743
  Branches      40539    40539
============================================
- Hits         200223   198690    -1533
- Misses        64394    65740    +1346
- Partials      16126    16313     +187

Impacted Files
Coverage Δ

...adonly/AddIndexBlockClusterStateUpdateRequest.java
0.00% <0.00%> (-75.00%)
:arrow_down:

...readonly/TransportVerifyShardIndexBlockAction.java
9.75% <0.00%> (-58.54%)
:arrow_down:

...n/admin/indices/readonly/AddIndexBlockRequest.java
17.85% <0.00%> (-53.58%)
:arrow_down:

...cluster/coordination/PendingClusterStateStats.java
20.00% <0.00%> (-48.00%)
:arrow_down:

...opensearch/persistent/PersistentTasksExecutor.java
22.22% <0.00%> (-44.45%)
:arrow_down:

...adcast/BroadcastShardOperationFailedException.java
55.55% <0.00%> (-44.45%)
:arrow_down:

...rch/client/transport/NoNodeAvailableException.java
28.57% <0.00%> (-42.86%)
:arrow_down:

...indices/readonly/TransportAddIndexBlockAction.java
20.68% <0.00%> (-41.38%)
:arrow_down:

...h/action/ingest/SimulateDocumentVerboseResult.java
60.71% <0.00%> (-39.29%)
:arrow_down:

...cluster/coordination/PublishClusterStateStats.java
33.33% <0.00%> (-37.51%)
:arrow_down:

... and 437 more

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


Tests

Add tests for all functions/classes.

Class tests mostly done, just toRegex methods to do.

Also want to test all attributes for IP and Subnet classes.

One last test to add.


feature/password reset

BTW, you only get the email in production.
In develop, it will log a link to a preview of the email from console on the server.
Just run docker logs backtalk-api and you should see it.


consider switching from toml to tomli

Is your feature request related to a problem? Please describe.
pip is moving from toml to tomli https://github.com/pypa/pip/pull/10035 coveragepy should consider following suit

pip: https://github.com/pypa/pip/pull/10035
build: https://github.com/pypa/build/issues/308
black: https://github.com/psf/black/pull/2301
pytest: https://github.com/pytest-dev/pytest/issues/8789

pytest has now switched to tomli, meaning that installing pytest-cov requires toml and tomli


HelperExtensions.cs

Good afternoon. I am trying to use this library in my program, but when I try to get data, I get the error:
"The debugger could not find the source file"C:\Code\Hilres .Yahoo.ApiClient\Hilres.Yahoo.ApiClient\HelperExtensions.cs"."

I tried to duplicate the error by creating a quick console app.   I used Visual Studio IDE v17.2.5
using Hilres.Yahoo.ApiClient;
var client = new YahooClient();
var result = await client.GetPricesAsync("msft", new(2022, 1, 3), new(2022, 1, 8));
Console.WriteLine($"Successful = {result.IsSuccessful}");
Console.WriteLine($"Count = {result.Prices.Count()}");

But did not get any errors stepping through the code.  The "C:\Code" is the location I do my development in.  All 21 test cases still passed.  Not sure what's going on.

Unable to reproduce.


Revert "Add dependencies to the internal_kubernetes_deploy_experimental job (#30595)"

This reverts commit 4991a56b77d41f7c27f5f2859c15fec43ad85a35.

What does this PR do?
Motivation
The original PR uncovered issues with the windows job and it prevents us from deploying the beta build. Reverting it until we fix the windows job
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Book.descriptionHTML not well formatted

Hello,
I was using the API and I discovered that most of the book description contains a list at the end with items about what people should learn from the book. But all of the lists are not well formatted, there is only one

 and other items start by -.
It looks like the HTML should be fixed.

Ok so after investigation, we are parsing the description written in markdown here with the marked lib at this place in the code.
So for the moment I guess it's either a problem with the markdown or a problem with the lib (but I guess their lib is well written so let's check first what's on our side).
So we are getting our book here from the file book.yml.
We are parsing the yml file here using the yamllib: https://github.com/FullStackBulletin/fullstack-books/blob/main/scripts/build.ts#L43
There might be an issue with the result of the parsing, I'll check that using the debuger.
Ok, so that's what I was expecting when parsing the file the description text is kind of put on a single line of text so we loose all the indentation usefull for markdown to be parsed.
For example, this :
JavaScript lies at the heart of almost every modern web application, from social apps like Twitter to browser-based game frameworks like Phaser and Babylon. Though simple for beginners to pick up and play with, JavaScript is a flexible, complex language that you can use to build full-scale applications.

    This much anticipated and thoroughly revised third edition of Eloquent JavaScript dives deep into the JavaScript language to show you how to write beautiful, effective code. It has been updated to reflect the current state of JavaScript and web browsers and includes brand-new material on features like class notation, arrow functions, iterators, async functions, template strings, and block scope. A host of new exercises have also been added to test your skills and keep you on track.

    As with previous editions, Haverbeke continues to teach through extensive examples and immerses you in code from the start, while exercises and full-chapter projects give you hands-on experience with writing your own programs. You start by learning the basic structure of the JavaScript language as well as control structures, functions, and data structures to help you write basic programs. Then you'll learn about error handling and bug fixing, modularity, and asynchronous programming before moving on to web browsers and how JavaScript is used to program them. As you build projects such as an artificial life simulation, a simple programming language, and a paint program, you'll learn how to:

    - Understand the essential elements of programming, including syntax, control, and data
    - Organize and clarify your code with object-oriented and functional programming techniques
    - Script the browser and make basic web applications
    - Use the DOM effectively to interact with browsers
    - Harness Node.js to build servers and utilities

    Isn't it time you became fluent in the language of the Web?

Is becoming that 😞 :
JavaScript lies at the heart of almost every modern web application, from social apps like Twitter to browser-based game frameworks like Phaser and Babylon. Though simple for beginners to pick up and play with, JavaScript is a flexible, complex language that you can use to build full-scale applications.
This much anticipated and thoroughly revised third edition of Eloquent JavaScript dives deep into the JavaScript language to show you how to write beautiful, effective code. It has been updated to reflect the current state of JavaScript and web browsers and includes brand-new material on features like class notation, arrow functions, iterators, async functions, template strings, and block scope. A host of new exercises have also been added to test your skills and keep you on track.
As with previous editions, Haverbeke continues to teach through extensive examples and immerses you in code from the start, while exercises and full-chapter projects give you hands-on experience with writing your own programs. You start by learning the basic structure of the JavaScript language as well as control structures, functions, and data structures to help you write basic programs. Then you'll learn about error handling and bug fixing, modularity, and asynchronous programming before moving on to web browsers and how JavaScript is used to program them. As you build projects such as an artificial life simulation, a simple programming language, and a paint program, you'll learn how to:
- Understand the essential elements of programming, including syntax, control, and data - Organize and clarify your code with object-oriented and functional programming techniques - Script the browser and make basic web applications - Use the DOM effectively to interact with browsers - Harness Node.js to build servers and utilities
Isn't it time you became fluent in the language of the Web?

I'm gonna check the lib if we can do something about it.

Thanks for this detailed investigation @PFayoux, let me know if you manage to do some additional progress. I won't have much time to spend on investigating this in the coming weeks, unfortunately. But if you can find a solution and submit a PR that would be awesome

Ok I found a way to fix it, basically we have to fix the markdown. I'm gonna submit a PR as soon as I finish it ;)

@lmammino I'm sorry if I didn't respected any expected format for the PR, I just did what seems good for me. I don't know if you expected something particular 😁

Thanks a million for this contribution! Included in v1.2.0


Added 0.12.0 release

this is the second pr to add 0.12.0 — someone hit a merge button, please

Merged the previous pull request


Hi

Just to let you know, I've deleted my github repository due to no one will ever use it.

This project is also quite useful and nice to use. Thinking about making a website where it pushes webhooks to Discord that would be neat too.

This issue was not needed


LightmapGI: Reduce warnings and increase probe accuracy

Fixes #82642
The issue
It's very common to get warnings when baking LightmapGI and it's easy to get tens of thousands of them in a single scene.
If the scene is smaller than about 100x100 meters, these warnings are often harmless and don't have a noticeable effect on the indirect lighting of dynamic objects. But for larger scenes, the effect is very much noticeable.
The warnings and the bad accuracy have three causes:

A float precision problem in Plane.
A common and valid scenario where a partitioning plane can't be found for the BSP tree.
Delaunay3D can create invalid triangulation with overlapping tetrahedra in scenes covering a large area.

I made #90701 a separate PR for the last issue since Delaunay3D can be accessed directly from GDScript so that change isn't strictly isolated to LightmapGI.
Increased tolerance for Plane::has_point()
When creating a Plane from a triangle that spans hundreds of meters, Plane::has_point() can give false negatives when applied to the second and third point of the triangle with the default epsilon. And is_point_over() can return either true of false in these cases.
This wreaks havoc on BSP partitioning.
I've done tests on MRPs and scenes with randomly placed probes over 1000x1000x100m. The precision errors are always a power of two and the largest one I've been able to produce is 1/(1<<13) so I'm using that for tolerance when calling has_point(). It is 12x the current tolerance of 1e-5 but still small enough that it shouldn't matter. False positives with this magnitude should not have any effect.
A better partitioning fallback
Probe tetrahedra are recursively sorted into a BSP tree. All the faces of the tetrahedra are candidate planes to be used for partitioning. As long as the remaining tetrahedra in a subtree have at least two that share an edge or a face, this method will always find a plane that cleanly separates at least one into each new subtree.
But the final two (or very rarely three) tetrahedra in a branch are often either disjoint or share only a single vertex. In this scenario, it is no longer guaranteed that one of the faces is also a separating plane. This is common cause of warnings.
With this knowledge, we can handle this specific case explicitly in a way that always succeeds (as long as the triangulation from Delaunay3D is valid).
Bonus: Smaller BSP tree
When the chosen BSP separating plane intersects tetrahedra, they are not split but instead moved into both the subtrees.
The current scoring system to find the best plane only rewards balance. If a plane has one tetrahedron over it, one under and 20 intersecting then it gets a perfect score because 1/1 is perfect balance. This makes the BSP tree much larger than it needs to be.
Reduz actually had a better solution but he commented it out. I took it and I made it more extreme. The scoring now penalizes planes for the number of tetrahedra they intersect.
"Worst" case, the tree is now 30% smaller. Best case, 97% smaller.
I can go into details about why I'm not worried that this will create unbalanced trees, if someone is interested. I've also verified that the max tree depth on all my test scenes is less than before. I expect that lookup times at runtime in general should "always" be improved. And when there are many probe nodes, bake time is also noticeably reduced.

Maybe I was too modest in naming this PR. To be clear, I expect that this together with #90701 will take care of all warnings under all normal circumstances (at least until someone finds a new way to break Delaunay3D).

Thanks!


⚠ Bofrost.be has degraded performance

In 060b901, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 3109 ms

Resolved: Bofrost.be performance has improved in e0bc0c9.


Default stories show up as roots

Describe the bug

To Reproduce
# Create our application:
npx create-react-app taskbox
cd taskbox

# Add Storybook:
npx -p @storybook/cli@next sb init

False alarm. This was due to the 5.0.0-debug.3 version hanging about. If you fix the version, it works fine:

The root issue will be resolved as soon as we release rc, and promise never to release a debug version again ;)


move fastboot CP into util

I was having a look at what I could do to help with #1619. I don't really get the full scope of how we could move away from mixins, but I did notice that isFastBoot method was repeated 5 times, so I moved it to a util function.

Added assertions for both of those things. @marcoow is an assertion correct or should I do more i.e. throw an Error?

and the assertions cause the tests to fail so I'll have to look into that later.

In tackling some deeper refactoring, I'm finding that there's significant value in having an isFastboot function in addition to the CP. Maybe we can

export function isFastBoot(container) { container.lookup('service:fastboot') .... }

export function isFastbootProp() {
    return new Ember.computed( .... )
}

I updated this to throw an Error if fastboot service is not present. @marcoow please can you check it over, because this is a behaviour change I do not understand. I am not really sure what the fastboot service is. Does this mean people running ESA in an app must also have a fastboot service? That doesn't make sense to me.

@mike-north I'll add a function for isFastBook() in a separate PR after this gets merged. Or you can do it if you want. I'm on a ⛵ for the next 12 days and I don't know if this means I'll have more or less time to contribute....

@geekygrappler: I only now realize that we had the behavior where it falls back to returning true previously as well and you just copied that over. ~I still think it makes sense to keep the assertion though as we're likely to only hide other errors of we leave it out.~ (see below 😞)
The fastboot service is a service that ember-cli-fastboot adds to the app and that can be used to check and access all kinds of things, e.g. the isFastBoot property which is true when running in Node and false in the browser or for reading headers etc. That said, I realize that we cannot even add the above assertion as that would essentially make ember-cli-fastboot a dependency of ESA which of course we don't want. Sorry for the confusion 🙏

I changed this back to just return false if the fastboot service doesn't exist.


Target URI doesn't exist after pubspec get

I'm getting an error after pubspec get that says target URI doesn't exist

I think you need to include full dir of the file, mine looks like this import 'package:blue_thermal_printer/blue_thermal_printer.dart'; if still happen maybe try to do some pub get

it is still displaying error, btw this file is autogenerated so you shouldn't tamper with it right ?

Turns out, Solution has been addressed in #102 , the library does not yet support flutter web so need to exclude the file in the analysis


Can you provide the userdata scripts more easily?

Hi, This is a great project and post that goes with it. However I find it cumbersome (and confusing) to have to launch a cloud9 environment, run configure.sh, then wait a few minutes,  just to be able to see the Userdata scripts.
It would be great if you could provide those scripts directly here.

Hello! The user data scripts are accessible directly from the CloudFormation templates for each example that has them. Take a look at the link below and let me know if this is what you’re after. Otherwise, I can definitely look into making those easier to find. https://github.com/aws-samples/amazon-ec2-auto-scaling-group-examples/blob/main/features/lifecycle-hooks/userdata-managed-linux/template.yaml

Hi Scott, thanks for the quick reply! Yes, I did eventually find the CloudFormation templates, and deciphered them. But I still think it is worth making simpler to find.
BTW when I tried using the complete-lifecycle-action CLI in my userdata I came across a bug (as confirmed by support) that if you make the call to soon (like when the instance moves from the warm pool to the ASG) it fails and reports "No active Lifecycle Action found". Thus I needed to put the complete-lifecycle-action in a retry loop in order for it to work.


Add a way to customize the shown --test message

Right now when you run ghcid with --test=... it shows:
Running test...

just before the "test" is run.
In our case we are starting a web server in --test, so seeing "Running test..." just before bringing up the web server (which might take a while) is a bit strange. Also, for developers joining our project and running our shake commands we have to explain them "This is not actually running any test".
Do you think it would be a good idea to customize this message? It could be something like --test-message="Starting web server...". I know it might feel a bit redundant to pass a message to be shown right next, but it makes sense if the command runs as part of other commands.

To me, the value seems marginal, but given it seems a pain point for you, and the ongoing maintenance cost should be pretty tiny, I'm happy to take a patch. Exactly as you describe seems reasonable.

@ndmitchell Great! And thanks for the super fast reply. I will work on a patch then, though I'm not sure how to compile the project (but I can try to figure that out).

cabal install or stack install should be sufficient. You can also ghcid to develop it (that's how I do it).


fix: add build to Lazy LuaSnip declaration

I got errors when listing 'L3M0N4D3/LuaSnip' as a dependency without also including the build explicitly.
Checklist

[ ] Used only camelCase variable names.
[ ] If functionality is added or modified, also made respective changes to the
README.md (the .txt file is auto-generated and does not need to be modified).

thx! But tbh, I think I'll switch the readme example to nvim-snippet instead, since it's the better option when people just want snippets. (iirc, Lazyvim switched to it as well.)


Add sched_get/setparam and sched_get/setscheduler to Solarish

Also define scheduling constants for illumos.

r? @JohnTitor
(rust-highfive has picked a reviewer for you, use r? to override)

It's very likely that the scheduling constants I've added for illumos are also accurate for Solaris. However, I've been unable to verify this myself (the Solaris man pages list the constant names, but not their numeric values).
If someone with more familiarity with Solaris could confirm their numeric values, I'd be happy to promote the constants up a level.

checked on solaris 11 they are the same ;-)

Thanks @devnexen!

Looks good, thanks both!
@bors r+

:pushpin: Commit 0904320c928ec98b3afea7874b29c7902490c836 has been approved by JohnTitor

:hourglass: Testing commit 0904320c928ec98b3afea7874b29c7902490c836 with merge 9ddea3cdb33e779e2a5b8f01de458ba3cd80c783...

:broken_heart: Test failed - checks-actions

@JohnTitor the build failure looks unrelated to the changes in this PR.

Thanks for the ping! I'm on mobile currently and I'll take a look later.

@bors retry

:hourglass: Testing commit 0904320c928ec98b3afea7874b29c7902490c836 with merge 200345c97b929d72030ff21afc3c03fd17abf505...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: JohnTitor
Pushing 200345c97b929d72030ff21afc3c03fd17abf505 to master...


Aborted (core dumped) in tf.raw_ops.IRFFTND\RFFTND\FFTND\IFFTND

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tf 2.16
Custom code
Yes
OS platform and distribution
Linux Ubuntu 22.04.3 LTS (x86_64)
Mobile device
No response
Python version
3.12.3
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
When the fft_length and axes parameter of tf.raw_ops.IRFFTND\RFFTND\FFTND\IFFTND than or equal to 0, it will trigger a crash, resulting in Check failed.
Standalone code to reproduce the issue
import tensorflow as tf
input1 = tf.random.normal([10,10,10,10,10], dtype=tf.float32)
input2 = tf.random.normal([10,10,10,10,10], dtype=tf.float32)
input3 = tf.complex(input1,input2)

tf.raw_ops.IRFFTND(input=input3,fft_length=(1,1),axes=-1,Treal=tf.dtypes.float32)     #crash
# tf.raw_ops.RFFTND(input=input2,fft_length=(1,1),axes=-1,Tcomplex=tf.dtypes.complex64) #crash
# tf.raw_ops.FFTND(input = input3,fft_length=-3,axes=-3)   #crash
# tf.raw_ops.IFFTND(input = input3,fft_length=(1,1,1),axes=-1)  #crash

Relevant log output
2024-05-25 10:04:17.096394: I tensorflow/core/util/port.cc:113] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-05-25 10:04:17.138470: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-05-25 10:04:17.732064: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
2024-05-25 10:04:18.435334: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1928] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 12867 MB memory:  -> device: 0, name: NVIDIA GeForce RTX 3090, pci bus id: 0000:18:00.0, compute capability: 8.6
2024-05-25 10:04:18.435959: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1928] Created device /job:localhost/replica:0/task:0/device:GPU:1 with 22453 MB memory:  -> device: 1, name: NVIDIA GeForce RTX 3090, pci bus id: 0000:af:00.0, compute capability: 8.6
2024-05-25 10:04:18.650709: F tensorflow/core/framework/tensor_shape.cc:45] Check failed: NDIMS == dims() (1 vs. 0)Asking for tensor of 1 dimensions from a tensor of 0 dimensions
Aborted (core dumped)

@x0w3n,
Looks like this is the issue #67098 which is already addressed and assigned to the Developer. Could you please confirm and close this issue, since it is already being tracked there. Thank you!

@x0w3n,
As mentioned please move this issue to the closed status, https://github.com/tensorflow/tensorflow/issues/68648#issuecomment-2135026372 since it is already being tracked there. Thank you!


[FEAT] standardise names for functions

We should rename maybe these two but I am not sure how.

tools.plot_vertical_speeds_with_histograms
tools.plot_combined_velocity_profiles

I think those are fine names! Doesn't matter if they're long, they are descriptive

This will resolve #99


fix set function to allow falsy values

Description
It was reported that set function does work with any falsy values (see https://github.com/rayepps/radash/issues/257). I have adjusted it so that it now accepts all values except for undefined.
Checklist

[x] Changes are covered by tests if behavior has been changed or added
[x] Tests have 100% coverage
[x] If code changes were made, the version in package.json has been bumped (matching semver)
[x] If code changes were made, the yarn build command has been run and to update the cdn directory
[ ] If code changes were made, the documentation (in the /docs directory) has been updated

Resolves
https://github.com/rayepps/radash/issues/257

Any updates on this?!


Show current Imba version in the navigation bar

Clicking the version should open new tab on GitHub for the latest release.

It's nice to have but not necessary.


BUG: 'BootstrapResult' object has no attribute 'bootstrap_distribution'

Describe your issue.
After running a paired bootsrap, I cannot access bootstrap distribution. I understood this was solved in https://github.com/scipy/scipy/pull/16454/files
What am I doing wrong?
Reproducing Code Example
import numpy as np
from scipy.stats import bootstrap

rng = np.random.default_rng()

n = 100
x = np.linspace(0, 10, n)
y = x + rng.uniform(size=n)

def my_statistic(x, y, axis=0):
    s1 = np.mean(x, axis=axis)
    s2 = np.mean(y, axis=axis)
    return s1 - s2

res = bootstrap((x, y), my_statistic, random_state=rng, paired=True, method='BCa', axis=0)

res.bootstrap_distribution

Error message
AttributeError: 'BootstrapResult' object has no attribute 'bootstrap_distribution'

SciPy/NumPy/Python version information
1.9.2 1.23.4 sys.version_info(major=3, minor=8, micro=6, releaselevel='final', serial=0)

Hi @david26694, thank you for reporting. This is just not released yet. SciPy is making a feature release every 6 months and this change is due for 1.10.
If you need this now, you can use a development version. We have wheels for conveniency https://anaconda.org/scipy-wheels-nightly/scipy

@david26694 it may be possible to install from weekly builds. https://pypi.anaconda.org/scipy-wheels-nightly/simple/scipy/

Oops I didn't see that you already wrote that @tupui!


QR Code for Room

https://github.com/codebude/QRCoder/wiki/Advanced-usage---Payload-generators#319-url


Allow to create working self-contained sdist packages

Added option to create sdist packages:

Include both Cython sources and plain Cython-generated C++ sources in sdist archives with proper MANIFEST.in template,

Add option to install imgui with Cython compilation using extras_require:
pip install imgui[Cython]

With this extras option Cython package will be included as requirements. If it is available during imgui sdist package instalation then setuptools will compile Cython sources (.pyx, .pxd files) to C++ sources and only then perform final compilation.

Add helper makefile target that will be used during actual code distribution on PyPI,

This change has small caveat: it will work as intended (Cython will be used with extras uption during sdist installation) only if user does not have wheel package installed. Still, this shouldn't be an issue because:

Our main goal is to ship fully working wheels and not sdists. The sdists distributions are just a fallback mechanism for certain some OS/environments where our wheels may not work properly.
The users of wheel package will in most cases download wheels without knowing that there is sdist distribution
The sdist distribution includes generated C++ sources too so the final compilation is possible even without Cython installed.

@stuaxo, could you take a look at this as a follow-up to #39?

Coverage remained the same at 47.969% when pulling 4da7f909b28539cf3f5bf0e25c683736efd24980 on feature/self-contained-sdist-packages into 96b8bd61046502569bb999573edd6503226fbe96 on master.

Should get some time on the weekend.  I guess we need tests for both kinds (with and without cython).  I don't know enough about python use with native libraries to know if the extra effort is worth it, but it does seem to be recommended for cython based libraries?

OK, so let's test and review it later. The best way to see if it works is to finally release it on PyPI and see if users have any troubles with installing the package on their machines. I have waited too long with initial official release.

Definitely - I don't want to delay anything + am especially keen to have something to test from Pypi.

Great. I have just released it officially.


Delegates which are not defined within middleware dispatching systems!?

Why does the delegate conflict with middleware?
…
The implementation of delegate should be defined within middleware dispatching systems.

I've reread this sentence multiple times from different points of view and I'm asking myself:

Is it anyhow possible that a delegate is not defined within middleware dispatching system?

I mean, if $d instanceof DelegateInterface, then $d can be used to dispatch middlewares, thus $d is part of the middleware dispatching system, isn't it?
Note: I must admit, the word within above does not make much sense to me in a packagist.org world.

No longer a concern with #71.


HBASE-28969 Move HFileLink file creations to SFT

Post HBASE-28564, HStoreFile creation is SFT aware and Reference file creations are moved to SFT.
Current change refactors all HFileLink file creations to SFT, so as to support Virtual links creation via FSFT in HBASE-27826

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 18s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m  1s

master passed

+1 :green_heart:
compile
2m 56s

master passed

+1 :green_heart:
checkstyle
0m 38s

master passed

+1 :green_heart:
spotbugs
1m 32s

master passed

+1 :green_heart:
spotless
0m 45s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 36s
/patch-mvninstall-root.txt
root in the patch failed.

-1 :x:
compile
1m 37s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

-0 :warning:
javac
1m 37s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 35s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 1 new + 58 unchanged - 1 fixed = 59 total (was 59)

-1 :x:
spotbugs
0m 43s
/patch-spotbugs-hbase-server.txt
hbase-server in the patch failed.

-1 :x:
hadoopcheck
1m 53s

The patch causes 16 errors with Hadoop v3.3.6.

-1 :x:
hadoopcheck
3m 47s

The patch causes 16 errors with Hadoop v3.4.0.

+1 :green_heart:
spotless
0m 40s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m  9s

The patch does not generate ASF License warnings.

19m 42s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6459

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 8427ceefc195 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 4eac13e14cf88db7745cac8d0f354c1e8be86127

Default Java
Eclipse Adoptium-17.0.11+9

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/1/artifact/yetus-general-check/output/patch-javac-3.3.6.txt

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/1/artifact/yetus-general-check/output/patch-javac-3.4.0.txt

Max. process+thread count
83 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/1/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 17s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m  5s

master passed

+1 :green_heart:
compile
2m 59s

master passed

+1 :green_heart:
checkstyle
0m 37s

master passed

+1 :green_heart:
spotbugs
1m 35s

master passed

+1 :green_heart:
spotless
0m 43s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 50s

the patch passed

+1 :green_heart:
compile
2m 55s

the patch passed

+1 :green_heart:
javac
2m 55s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 37s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 1 new + 58 unchanged - 1 fixed = 59 total (was 59)

+1 :green_heart:
spotbugs
1m 38s

the patch passed

+1 :green_heart:
hadoopcheck
10m  1s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 56s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 20s

the patch passed

+1 :green_heart:
compile
0m 58s

the patch passed

+1 :green_heart:
javac
0m 58s

the patch passed

-0 :warning:
javadoc
0m 29s
/results-javadoc-javadoc-hbase-server.txt
hbase-server generated 2 new + 61 unchanged - 0 fixed = 63 total (was 61)

+1 :green_heart:
shadedjars
5m 34s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
406m 13s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

442m 51s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/2/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6459

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 18ea321912dd 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 356d620553ad27483af7c11f7b796167dac8cff9

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/2/testReport/

Max. process+thread count
4734 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 22s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 18s

master passed

+1 :green_heart:
compile
2m 55s

master passed

+1 :green_heart:
checkstyle
0m 36s

master passed

+1 :green_heart:
spotbugs
1m 36s

master passed

+1 :green_heart:
spotless
0m 43s

branch has no errors when running spotless:check.

-0 :warning:
patch
0m 49s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 40s

the patch passed

+1 :green_heart:
compile
2m 38s

the patch passed

+1 :green_heart:
javac
2m 38s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 33s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 1 new + 58 unchanged - 1 fixed = 59 total (was 59)

+1 :green_heart:
spotbugs
1m 34s

the patch passed

+1 :green_heart:
hadoopcheck
9m 39s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 40s

patch has no errors when running spotless:check.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 38s

the patch passed

+1 :green_heart:
compile
0m 52s

the patch passed

+1 :green_heart:
javac
0m 52s

the patch passed

-0 :warning:
javadoc
0m 27s
/results-javadoc-javadoc-hbase-server.txt
hbase-server generated 2 new + 61 unchanged - 0 fixed = 63 total (was 61)

+1 :green_heart:
shadedjars
4m 49s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
188m 27s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

211m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/3/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6459

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux c072968666b9 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 689010e279810dc116aead311be3f36d7e1609c0

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/3/testReport/

Max. process+thread count
5849 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/3/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 18s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 55s

master passed

+1 :green_heart:
compile
2m 35s

master passed

+1 :green_heart:
checkstyle
0m 33s

master passed

+1 :green_heart:
spotbugs
1m 25s

master passed

+1 :green_heart:
spotless
0m 40s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 37s

the patch passed

+1 :green_heart:
compile
2m 33s

the patch passed

+1 :green_heart:
javac
2m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 33s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 1 new + 58 unchanged - 1 fixed = 59 total (was 59)

+1 :green_heart:
spotbugs
1m 30s

the patch passed

+1 :green_heart:
hadoopcheck
9m 21s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 40s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 35s

the patch passed

+1 :green_heart:
compile
0m 52s

the patch passed

+1 :green_heart:
javac
0m 52s

the patch passed

-0 :warning:
javadoc
0m 27s
/results-javadoc-javadoc-hbase-server.txt
hbase-server generated 2 new + 61 unchanged - 0 fixed = 63 total (was 61)

+1 :green_heart:
shadedjars
4m 50s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
204m 56s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

227m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/4/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6459

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 2be0e1366f0b 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / bc9a60b129fe0a5d1c7cc2fed7cb200e71a0b39d

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/4/testReport/

Max. process+thread count
5139 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/4/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 44s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 54s

master passed

+1 :green_heart:
compile
2m 36s

master passed

+1 :green_heart:
checkstyle
0m 33s

master passed

+1 :green_heart:
spotbugs
1m 28s

master passed

+1 :green_heart:
spotless
0m 41s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 38s

the patch passed

+1 :green_heart:
compile
2m 35s

the patch passed

+1 :green_heart:
javac
2m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 33s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 1 new + 58 unchanged - 1 fixed = 59 total (was 59)

+1 :green_heart:
spotbugs
1m 32s

the patch passed

+1 :green_heart:
hadoopcheck
9m 26s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 42s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 46s

the patch passed

+1 :green_heart:
compile
1m 16s

the patch passed

+1 :green_heart:
javac
1m 16s

the patch passed

-0 :warning:
javadoc
0m 43s
/results-javadoc-javadoc-hbase-server.txt
hbase-server generated 2 new + 61 unchanged - 0 fixed = 63 total (was 61)

+1 :green_heart:
shadedjars
7m 50s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
209m 21s

hbase-server in the patch passed.

241m 32s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/5/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6459

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 31b8b37daddc 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 81bda0104db46331af2d62bff2cea370d17710ee

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/5/testReport/

Max. process+thread count
4528 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6459/5/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


Check for new updates

I need to add a way not to check for updates everytime the script is used.
Maybe touch ~/.dockerc or some other file and check the modified time.
An option to disable the check would be nice too.

Version is only checked when dockerc --version is run.
Version check is disabled in dockerc --version -n or dockerc --version -q is run.

Just added dockerc -v shorthand for dockerc --version.


Connection utilization

Hello,
I wanna have total control of the connections of hasura, but I don't understand how to connections works.
If I make a query in my server of hasura, this makes 2 or 4 connections, but I don't understand why.
Someone know what is it? How I can control these connections? I wanna only open a connection, make a query, and close it immediately. There run out of the purpose of the GraphQL hasura?
I very worry about free connections limitation of hasura. Someone have some experince about this here and wanna share here?
thank you!

The hasura connect make in theory just 1 connection.
Hasura has no connections Limit


Added an enabled monitor label to file_sd

Sometimes, we want to temporary disable the scrape on some specific targets. The idea is to add a label check to file_sd, whenever a label named enabled has the value "false", the targetGroup will be ignored.

Thanks for your PR. This is business logic, which doesn't belong in an SD implementation. You can do this with relabelling.

But relabeling will not work. For example, in one file we have hundreds of targets with different sets of labels, how would you relabel to disable scraping some targets for some time (1hour, 1 day, etc.). Moreover, relabeling requires configuration reloading or prometheus restarting while changing properties of labels does not.

Thanks for your PR. This is business logic, which doesn't belong in an SD implementation. You can do this with relabelling.

But relabeling will not work. For example, in one file we have hundreds of targets with different sets of labels, how would you relabel to disable scraping some targets for some time (1hour, 1 day, etc.). Moreover, relabeling requires configuration reloading or prometheus restarting while changing properties of labels does not.

This is all possible, but this isn't the best place to discuss it.
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


Revert "Ignore special files on deploy (#115)"

This reverts commit 1de3b40fc438011ccfd4e92e56e6bdc51c9b4c7a.
Fixes #127

Please hold on until we have a real fix for #127


Some books of riak2.0+ to recommand? [JIRA: RIAK-1623]

Some books of riak2.0 to recommand?

The little riak book? https://github.com/coderoshi/little_riak_book/commits/master

Use @gglanzani's suggestion, but this is really a question better for the mailing list than for the issue tracker.


SSAO

I'd like to report maybe a bug or something? SSAO seems not working in all version of CS1.6. I tried in 3 different client, 2 clients are heavily modded (CSPB & Hellstrike), and the other is CS1.6 client 8684. SSAO only works in CSPB, but not in Hellstrike or 1.6 build 8684.
This is what SSAO looks like in CSPB

No SSAO in Hellstrike

No SSAO in CS 1.6 build 8684

is this the same issue ? https://github.com/hzqst/MetaHookSv/issues/464

is this the same issue ? #464

yeah i guess it is. but the weird thing is in CSPB the r_vertical_vof is set to 0, and the viewmodel_fov is 0 too, but the SSAO works.

is this the same issue ? #464

yeah i guess it is. but the weird thing is in CSPB the r_vertical_vof is set to 0, and the viewmodel_fov is 0 too, but the SSAO works.

it depends on actual fov sent from server (maybe amxx?) then.


Add subtitle to homepage

We should add a subtitle to the homepage to provide additional context for user testing:
"An experimental platform for multiple communities to provide post-publication peer review of scientific research. Learn more about the platform."
'Learn more about the platform' should link to the About page.

I used a <p> and added no style other than the default, anyone feel free to improve on it. Shortly available in staging.

Styling we can improve later depending on how quickly we deplete To Do

Available in staging.


Example to use mutates with a non-primitive Type

I would like to use the mutates functionality with a struct reference. But I cannot get it to work, inside of the closure the mutable reference does not have a type. Can you give an example for mutates with a non-primitive type?

An example of something that works can be found in https://docs.rs/unimock/0.5.7/src/unimock/mock/core.rs.html#10, the mock implementation for core::fmt::Display.
The f parameter in fmt is &mut core::fmt::Formatter, and can be used like this:
            DisplayMock::fmt
                .next_call(matching!())
                .mutates(|f, _| write!(f, "u"))

The test for this is in https://github.com/audunhalland/unimock/blob/e9430092357031567c80b0ba17ea24e6bafba7ec/tests/it/std.rs#L14.

Ok, my entrait function has a generic type paramater, that seems to cause the issue. As soon as I introduce that, the error appears.
This does not compile, as soon as I remove the generic parameter, it compiles without issues.
    trait MyTrait {}

    struct MyStruct;

    impl MyTrait for MyStruct {}

    struct MyFoo {
        baz: u32,
    }

    #[entrait::entrait(pub MyEntrait, no_deps, mock_api=MyEntraitTest)]
    pub fn my_entrait<T>(nasty: T, foo: &mut MyFoo)
    where
        T: MyTrait,
    {
    }

    #[test]
    fn test_my_entrait() {
        let mocked_deps = Unimock::new(
            MyEntraitTest
                .with_types::<MyStruct>()
                .some_call(matching!(_))
                // https://docs.rs/unimock/latest/unimock/#mutating-inputs
                .mutates(|m, _| {
                    m.baz = 34;
                }),
        );
    }

The error is
no field `baz` on type `&mut <impl unimock::MockFn<Inputs = (methods::execute::router::tests::MyStruct, unimock::PhantomMut<&'__i methods::execute::router::tests::MyFoo>), Response = unimock::output::Owned<()>> as unimock::MockFn>::Mutation<'_>`

I also cannot replace T with &mut impl MyTrait because of https://github.com/audunhalland/entrait/issues/27.

Thanks! https://github.com/audunhalland/unimock/pull/38 should fix that.


CONFIG.JSON does not allow for re-run of pipeline with altered sample list

Problem
There was a corrupted sample in my project. I went and removed that sample from the input dir, which I had been giving to RENEE. I then attempted to resume the pipeline without the sample and the pipeline is failing because the FQ file is missing.
The reason for this is that the config.json file has my sample info included. Because this is not being re-generated, the project will only ever run the samples included in the initializtion.
Solution
Without having a major re-write, I'm thinking the easiest solution is to have an option where we can call a re-run command or something similar? Alternative would be to create a new json each deployment but I have concerns with that, since users could alter portions of that file (another 'wish list' would be to get rid of this file all together).
Thoughts @kelly-sovacool  @kopardev

Maybe we can figure out how to fix this without adding a new subcommand?
Could we just document somewhere that if you run renee again from the same directory after removing a sample, you'll also need to manually edit the config.json?

ideally: you would do nothing other than change the inputDIR or the input manifest file (this is how CARLISE and ASPEN are set up)
next ideal: you tell it to recreate the json file with a subcommand
next ideal: you edit the json yourself
The json file would require users to edit three locations (albeit they are close to one another) for every sample add/removal. I'm worried that if a user makes an error in the json file that they won't be able to recover from it, since there is no way to recreate the file without re-initalizing. What I imagine is going to happen is that users would just re-run the whole pipeline which seems wasteful, but probably easier?

Oof, this really underscores how much we need to get rid of config.json in our future redesign.
Another question: does resuming the snakemake workflow from this stage have any benefits? e.g. would it prevent rerunning certain steps of the pipeline that run for each sample (e.g. adapter trimming), or would it have to rerun those steps anyway?

Yes, in an ideal world.
Ideal: You tell Snakemake to resume. Snakemake looks at the file list (given from the updated json file) and it thinks "I forgot this sample" and deploys only the rules which are needed to recreate the final outputs. It would run trimming on SampleNew, but not on SampleOld. It would re-run any step downstream though that has an input of SampleNew AND SampleOld though, like the RNA Report, which is what we want.
Current (add a new sample): You tell Snakemake to resume. Snakemake looks at the file list (still the old json file) and it thinks "I'm done", so nothing happens.
Current (delete a sample): You tell Snakemake to resume. Snakemake looks at the file list (still the old json file) and it thinks "there's a sample missing here - ERROR!" which is what happened in my actual use case. A sample was corrupted, I deleted that sample and re-ran, it errored because the sample it expected wasn't there. In my case about 50 jobs had already completed and I didn't want to start from scratch.

Also a note: I'm not sure where in this script, but the pyparser is still somehow grabbing the deleted sample and passing it to the final output file.
The pipeline failed at the RNA Report because the values for the deleted sample are zero, and therefore it's having an issue with determining variance. Feels like this is a larger issue since the python script is just grabbing anything in output directories, rather than having this information controlled by Snakemake. Might be a separate issue, depending on how we address this one...

@slsevilla , I believe Skyler's logic is too convoluted and this problem is encountered rarely. Plus, this will be fixed with the eventual transition to NF where we will use a manifest approach rather than grab all FQs willy-nilly. IMO, we should:

acknowledge the bug in the documentation and add to a plausible solution (NOT manually edit the config file as @kelly-sovacool suggested [too much for an average user], but just re-run from scratch without the unwanted sample(s)... that is much cleaner and these are RNAseq samples wont take too long)
not make any effort on fixing it as it will not even exist in the NF implementation.

@kopardev I created a label wait_for_nxf just now so we can keep track of issues that are specifically on the back-burner because we will fix them when we reimplement the pipeline in nextflow. What do you think?


Suggestion

Hair grade only seen it done once. It was part of a tattoo shop script for ESX. Just don’t feel like paying the dude $50 again for it on QBCore. If done I’ll give ya something as a show of appreciation.

@ItsAegeus what do you mean hair grade? Can you please elaborate?

@TheiLLeniumStudios Yeah, so hair grade is basically a fade. GTA online does it for specific hairs so you are not bald. Ill post some photos of it from the old script I used.
Before:

After:

@ItsAegeus Thanks for the reference. I did notice that problem. I'm not an expert of setting player appearances but it seems like its related to hair decorations. I will see what I can do to fix the issue

@ItsAegeus Thanks for the reference. I did notice that problem. I'm not an expert of setting player appearances but it seems like its related to hair decorations. I will see what I can do to fix the issue

Alright! The way he did it was just added a slider with the options to the tattoo shop but I'm sure you could think of a better place to put it lol.

@ItsAegeus Fixed by https://github.com/iLLeniumStudios/fivem-appearance/commit/b69b413312adc7888f1d2cc66782bf32ba56058e
Please get the latest version and let me know if it works for you. Feel free to re-open if there are still issues


Issues pane, "Everywhere" list gets cleared after saving

Description
In the Issues pane, when you choose the Everywhere button, and pan around the map, the list of issues grows and grows. This can be very helpful on occasions. However, when you save your changes, the list is cleared, and only the issues currently in view are listed. The Everywhere radio button is still selected and the list will grow again as you pan around, but it's annoying that the existing list is cleared.
If this is intentional, to give a way to clear the "everywhere" issues list from time-to-time, I would prefer for there to be a separate "clear list" button, rather than it being rolled into the Save mechanism.
Screenshots
Before saving:

After saving:

After discussion of a similar issue in #9042, I can see that there is a good reason for the current behaviour, so I'll close this.


Harmonising the new navigate field + icon throughout all relevant widgets

This action is part of the pages/widgets clean up effort.
As already discussed with @chinmehta, we need to apply the new navigate (cred set) field +icon+link to all relevant widgets.
These widgets still have old version of column in PPP-dev:

Variant page - molQTL Credible Sets widget - first column -  replace with navigate +icon+link
Cred set page - GWAS/MolQTL Colocalisation widget- first column -  replace with navigate +icon+link
Cred set page - GWAS Colocalisation widget- first column -  replace with navigate +icon+link
Study page - GWAS Credible Sets table (below the plot) - first column -  replace with navigate +icon+link

Same exercise for the L2G score slider visualisation, also to be added to:

Study page - GWAS Credible Sets table (below the plot) - L2G score - add slider [to be propagated to plot tooltip]

following up with the "harmonisation" theme,
i just realised some widgets allow sorting by beta and some don't e.g. :https://partner-platform.dev.opentargets.xyz/variant/12_6333477_C_T.
All widgets with beta value should allow sorting by beta


Exclude: libfontconfig1-dev

I was just about to create FreeCAD related PR. To remove FreeType from the FreeCAD recipe and have seen this:
https://github.com/AppImage/AppImages/pull/323
I can confirm we where affected by the mentioned issue too. In addition we use libfontconfig1-dev package as a workaround on PPA (for not having to create a symlink). I guess it is harmless if it is added to the AppImage. But as it doesn't do anything from the AppImage perspective. Likely best to remove it altogether.
https://forum.freecadweb.org/viewtopic.php?f=10&t=15525&start=190#p222348

I guess you will still need the pretend line.

Due to libfontconfig1 being in the excludedeblist. It doesn't get added anyway:
https://github.com/AppImage/AppImages/blob/master/excludedeblist
Regardless of the pretend line. And as fontconfig wasn't added to the AppImage but FreeType was added until now. That is where the issue with FreeType originated from. At least that is the case with FreeCAD. Newer version of fontconfig on system in combination with older version of FreeType library in AppImage.

Thanks.

Shouldn't https://github.com/AppImage/AppImages/blob/master/recipes/FreeCAD.yml be changed as well, then?

Likely that would need to happen once FreeCAD 0.17 gets released and the situation around updating stable/daily PPA settles.
I can take a look in the following days when time permits. And do some tests. To see if FreeCAD 0.16 AppImage (recipe) would be worth updating. Likely indeed some issues reported and fixed in FreeCAD 0.17 dev AppImage are affecting currently available FreeCAD 0.16 AppImage.

I can happily report that with this change it still runs fine on Xubuntu 16.04.

Note that this change affected mostly users on rolling releases. They are usually hit by such potential issues first. On distributions like Ubuntu and Fedora majority of users where not affected ATM.
Some reports on FreeCAD forums:
https://forum.freecadweb.org/viewtopic.php?f=10&t=15525&start=180#p220234
https://forum.freecadweb.org/viewtopic.php?f=4&t=27771


Feature request: terraform task should be able to recurse over directories and apply

It would be nice if the terraform task was able to recurse over subdirectories and run the command over all subdirectories, and even better if we could support glob patterns while doing so. Given that the bash script is getting more and more complex, it might be an idea to write a small Go binary and bake it into a docker image.
In order to be backwards compatible we'd need to have multiple Dockerfiles in the repository, one per terraform version, and rebuild everything on merge to master 😂

I think multiple subdirectories are a bit of an edge case since the majority of projects will deploy to a single account. That said we have several pipelines that does require this.
Another this that we should take into consideration is how we can run things in parallell, the serial approach we are running now does not scale. Should this be a part of this Go binary?

That is a good point!

Yes and how would we handle access/secret keys? Maybe this is outside the scope for this task but we should make sure we have a plan for this before we start implementing this.

Yes and how would we handle access/secret keys?

The easy solution would be that we run all the terraform actions (e.g. apply) with the same set of credentials. So one task could do multiple apply's at once if they were destined for the same account.

Yes and how would we handle access/secret keys? Maybe this is outside the scope for this task but we should make sure we have a plan for this before we start implementing this.

Agreed. I think doing parallel apply (or whatever) needs some more thinking. Should we go ahead and get a POC up and running for a sample Go version?

Oh damn. Access keys and secret keys affect the feature request in the issue as well...  🤔

We've ended up using shell-scripts inside a Taskfile to do this for pull request testing. And for actual plan/apply I think it's better to be explicit instead of recursing 😅 I.e., will not implement.


Zarr V2 vs V3

What needs to be done here?

Ideally we would be able to import Zarr objects from zarr-python that help us navigate the differences between v2 and v3

So Zarr v3 was released last week (it's on PyPI, and can be installed by specifying --pre with pip install). This means we can start the process of refactoring virtualizarr to use the v3 zarr-python library for some internal abstractions.
In particular I want to replace the virtualizarr.zarr.ZArray class. I haven't really looked at the v3 code much at all yet, but I'm hoping there is some drop-in for the ZArray class that can smoothly handle the difference between Zarr v2 and v3 arrays for us. (And if there's not we should be making suggestions upstream.)


Fix linker flags for MSYS2 clang64 builds

MSYS2 clang64 uses the lld linker which does not support --as-needed.
The normal GNU ld uses that linker option with ELF targets but ignores
it for PE targets (.exe, .dll), so it can be removed.
Remove also the -Wl, which is only needed when linker options are
passed to the compiler but not when they are directly passed to the
linker.
Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

MSYS2 currently requires a patch for building: https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-tesseract-ocr/tesseract-no-as-needed.patch. This commit makes that patch unnecessary fro future Tesseract releases.


Remove incorrect test

Not sure why login would give the same as refresh

Codecov Report

Merging #591 (bf72a52) into develop (8be362f) will decrease coverage by 0.09488%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##             develop        #591         +/-   ##
===================================================
- Coverage   98.29222%   98.19734%   -0.09489%
===================================================
  Files             86          86
  Lines           2108        2108
===================================================
- Hits            2072        2070          -2
- Misses            36          38          +2

Impacted Files
Coverage Δ

backend/src/app/routers/login/login.py
85.00000% <0.00000%> (-2.50000%)
:arrow_down:

backend/src/app/utils/dependencies.py
89.13043% <0.00000%> (-1.08696%)
:arrow_down: