Maya: bug fix the playblast without textures

Changelog Description
Bug fix the texture not being displayed when users enable texture placement in the OP/AYON setting
Additional info
It causes additional time for playblasting if users have tons of UDIMs texture.
Testing notes:

Go to project_settings/maya/publish/ExtractPlayblast/ to add profiles
Go to project_settings/maya/publish/ExtractPlayblast/profiles/0/capture_preset/Viewport Options/textures
Enable it
Go to project_settings/maya/publish/ExtractPlayblast/profiles/0/capture_preset/Viewport Options/reloadTextures
Enable this also
Launch Maya
Create Review while creating some other instances from other families
Publish.

Gives me following error during Publish of the Review on Extract Playblast
Traceback (most recent call last):
  File "C:\Work\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 527, in __explicit_process
    runner(*args)
  File "C:\Work\REPO\OpenPype\openpype\hosts\maya\plugins\publish\extract_playblast.py", line 219, in process
    self._capture(preset)
  File "C:\Work\REPO\OpenPype\openpype\hosts\maya\plugins\publish\extract_playblast.py", line 52, in _capture
    preset.pop("reloadTextures")  # not supported by `capture`
KeyError: 'reloadTextures'

@LiborBatek the latest commit should fix the KeyError

I like the code de-duplication a lot. However, there's still quite a bit that's duplicated.

Both do maintained_time,
both do this https://github.com/ynput/OpenPype/pull/5942/files/008f78e6a095f9c3c4af3b3f9fac7150705f1670..f9603bb0a5514e5fb28c60d56a50c26a1409e8ec#diff-34078a2a4bf0a4e1e51eda1d039f05d7557621c0a8346706b30967647c9d12b8R138-R143
both do this https://github.com/ynput/OpenPype/pull/5942/files/008f78e6a095f9c3c4af3b3f9fac7150705f1670..f9603bb0a5514e5fb28c60d56a50c26a1409e8ec#diff-34078a2a4bf0a4e1e51eda1d039f05d7557621c0a8346706b30967647c9d12b8R117-R121 which is likely a workaround for some BUG or issue but unfortunately no comment in the code describes WHY that is done so it's hard to know whether that could with recent code changes already be resolved, I have a feeling that it originally had to do with textures not being loaded yet as well.

I feel like at the core both these extractors do 90% the same thing, one exports a sequence of images, the other a single frame. Then the thumbnail only has a different present and slightly different overrides (e.g. no pan/zoom). Based off of that I'd expect there to be two relatively simple plug-ins that just do:
preset = self.get_preset(instance)
files = capture_with_preset(preset)

We don't have to streamline it completely of course - but both plug-ins appear to be using almost exactly the same thing but the code is already differing a bit just because the code was duplicated and not built to be maintained in a singular place for easier development.
Now we're moving that into lib I'd recommend looking into what else could be part of that function that is basically the same for both (and thus currently all cases)

I like the code de-duplication a lot. However, there's still quite a bit that's duplicated.

Both do maintained_time,
both do this https://github.com/ynput/OpenPype/pull/5942/files/008f78e6a095f9c3c4af3b3f9fac7150705f1670..f9603bb0a5514e5fb28c60d56a50c26a1409e8ec#diff-34078a2a4bf0a4e1e51eda1d039f05d7557621c0a8346706b30967647c9d12b8R138-R143
both do this https://github.com/ynput/OpenPype/pull/5942/files/008f78e6a095f9c3c4af3b3f9fac7150705f1670..f9603bb0a5514e5fb28c60d56a50c26a1409e8ec#diff-34078a2a4bf0a4e1e51eda1d039f05d7557621c0a8346706b30967647c9d12b8R117-R121 which is likely a workaround for some BUG or issue but unfortunately no comment in the code describes WHY that is done so it's hard to know whether that could with recent code changes already be resolved, I have a feeling that it originally had to do with textures not being loaded yet as well.

I feel like at the core both these extractors do 90% the same thing, one exports a sequence of images, the other a single frame. Then the thumbnail only has a different present and slightly different overrides (e.g. no pan/zoom). Based off of that I'd expect there to be two relatively simple plug-ins that just do:
preset = self.get_preset(instance)
files = capture_with_preset(preset)

We don't have to streamline it completely of course - but both plug-ins appear to be using almost exactly the same thing but the code is already differing a bit just because the code was duplicated and not built to be maintained in a singular place for easier development.
Now we're moving that into lib I'd recommend looking into what else could be part of that function that is basically the same for both (and thus currently all cases)

I actually agree with this, I think we need to put them into library as if we do in 3dsmax. (3dsmax has its own script for review animation btw)
I refactored all these capture presets and playblast capture into the functions respectively and put them into lib.py in the updated commit.

@LiborBatek Can you please test again? I haven't included the material loading mode into the enter_context options to testwhether the issue has been fixed.

@BigRoy thank you for helping out on the clean up and I have commented #6081. Just want to hear your thought on that. Otherwises it will be good to merge with this PR and ready for another test.

@LiborBatek can you please test again? Thanks!
@antirotor can you do the check on the code?

@LiborBatek I have updated the testing notes and codes regarding to your suggestion in discord. Can you please test it? Thanks!

@LiborBatek can you possibly test again? This ticket needs your approval so that it can be merged, Thanks!


Bug: OpenAPI schema does not generate file upload form in Swagger

Describe the bug
Using UploadFile, the generated docs don't produce the expected Swagger file upload form component.
To Reproduce
The following standalone app:
import logging

from starlite import Body, RequestEncodingType, UploadFile, post, Starlite

logger = logging.getLogger(__name__)

@post(path="/upload", cache=False, tags=["Collection"])
async def handle_collection_upload(
    data: UploadFile = Body(media_type=RequestEncodingType.MULTI_PART),
) -> dict[str, str]:
    """Upload a file"""
    logger.info("Processing Uploaded File")
    return {
        "status": "file uploaded",
    }

app = Starlite(route_handlers=[handle_collection_upload])

produces this Swagger UI:

But we expect an upload form, similar to that generated by FastAPI.
Additional context
This appears to be a regression of #396.

annoying. ill check it out.


Only provide .busy file attribute when true

The previous ObjC implementation only set the .busy attribute value when true and omitted the key when false. This restores the historic behavior for compatibility with existing clients.

@swift-ci please test


Add Redox FD_* function-macros and Android AI_* constants

I'm not sure if I'm allowed to add multiple, separate APIs in the same PR, but I guess they're both for uncommon/exotic platforms?
The AI_* constants were taken from usr/include/netdb.h on my Termux install; the FD_ functions were taken from linux_like/mod.rs.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @gnzlbg (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

The force push was just to fix a type for not properly qualifying c_int.

I'm not really sure why CI is failing; it just says that it's been cancelled because it ran too long but I'm not sure why that is.

@gnzlbg do you have any idea why CI might be failing?

Closing and re-opening to re-run CI.

@bors r+

:pushpin: Commit aa6f5e2b38dc1d70b8b79543f4b84bb97856c92f has been approved by gnzlbg

:hourglass: Testing commit aa6f5e2b38dc1d70b8b79543f4b84bb97856c92f with merge 74ff41223979af191278f53334fc81c645916d93...

:sunny: Test successful - checks-cirrus-freebsd-10, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, status-azure
Approved by: gnzlbg
Pushing 74ff41223979af191278f53334fc81c645916d93 to master...


[feature] Display exposed port number of objects in UI along with IP address

The Rancher web interface, when viewing Stacks, Hosts or Containers, should display any public-exposed port numbers next to the Service/Container in question, for reference.  It already displays the IP address nect to containers; I think the port number on containers (and the public port number on a Service/Load Balancer) is even more useful.
This will be particularly useful when randomly-assigned service ports becomes an option, as it makes the information immediately visible without having to click down into the object view to see it.
This could be displayed in the same section as the linked Service name on Load Balancers, for example.

In next release:


Update protobuf to v3.7.1

PTAL

PTAL
bazel build //... fails, but it also fails on the master branch.

bazel build //... is happy now!
PTAL


rename x86_script_file to test_script_file.

Signed-off-by: Stewart Smith<EMAIL_ADDRESS>

This change is

Superseded by https://github.com/open-power/op-test-framework/pull/56


feat: dynamic data dictionary .yml generation

.py file that connects to mongodb database, and generates .yml files for all desired bigquery datasets. should be ready for automation and virtualization.

Closing in favor of https://github.com/opensource-observer/oso/pull/2515


[FEATURE] Per-project channels

Is your feature request related to a problem? Please describe.
I am working in a playwright suite that uses projects to represent each app. I'd like a way to send Slack notifications to different channels depending on the project(s) being tested. This would allow me to have different teams triage those issues without things getting noisy for folks who didn't work on a specific project.
I was able to get it working with environment variables, but that is non-standard and I'd like to be able to support this workflow with standard npx playwright --project=app1 style commands.
Describe the solution you'd like
Given a project config like:
export default defineConfig({
  ...
  projects: [
    { name: "app1", ... },
    { name: "app2", ... }
  ]
});

I'd like a way to do something like:
export default defineConfig({
  reporter: [
    [
      './node_modules/playwright-slack-report/dist/src/SlackReporter.js',
      {
        channelsByProject: {
          app1: ["#app1-alerts"],
          app2: ["#app2-alerts"],
        },
        onFailureChannelsByProject: {
          app1: ["#app1-failures"],
          app2: ["#app2-failures"],
        },
        onSuccessChannelsByProject: {
          app1: ["#app1-success"],
          app2: ["#app2-success"],
        },
      }
    ],
    ["list"],
  ]
});

If there's a creative way to do this today I am happy to try that. I did attempt adding a reporter key in the project definition but Playwright doesn't seem to support that.

@itspriddle can you try creating a config file per project?
e.g. npx playwright --config=playwright.config.app1.ts
npx playwright --config=playwright.config.app2.ts
and then have whatever reporting config you need per config file ?
would this help you at all?

That would work in theory. I was kind of hoping for something more automatic that wouldn't require extra knowledge outside of the Playwright docs for others to work with the suite.
My initial attempt with environment vars was something like:
const channels = {
  app1: "#app1-alerts",
  app2: "#app2-alerts",
}

export default defineConfig({
  reporter: [
    [
      './node_modules/playwright-slack-report/dist/src/SlackReporter.js',
      {
        channels: [channels[process.env.APP]],
        ...
      }
    ]
  ]
});

I only really need Slack notifications in CI so I can just stick with that. I'd just hoped to be able to use standard Playwright commands rather than relying on env variables.

I ended up writing my own reporter since I wanted full control of everything. If you did want to implement this here, the magic for me was detecting the project from test.titlePath()[1] inside the reporter's onTestEnd() method; eg:
onTestEnd(test, result) {
  const project = test.titlePath()[1];
}

Thank you for putting together this project! It was very helpful to see how things worked to be able to write my own ❤


$or operator?

What about the $or operator? I would like to get documents with series 'Mario' or 'F-Zero'. How can I do this? Many thanks!
P.S.: Maybe this functionality will be integrated in the coming $in operator. When can we expect this functionality?

Not implemented yet. :) In the meantime you can run two separate queries.

Closing as $or is now in master.


Fix getRepair method in checkVolume command

Description
This PR fixes the getRepair method in checkVolume command

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9058

@blueorangutan test

@sureshanaparti a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-9625)
Environment: kvm-alma9 (x2), Advanced Networking with Mgmt server a9
Total time taken: 54367 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8840-t9625-kvm-alma9.zip
Smoke tests completed. 129 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

@blueorangutan test matrix

@borisstoyanov a [SL] Trillian-Jenkins matrix job (centos7 mgmt + xenserver71, rocky8 mgmt + vmware67u3, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-9636)
Environment: xenserver-71 (x2), Advanced Networking with Mgmt server 7
Total time taken: 46001 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8840-t9636-xenserver-71.zip
Smoke tests completed. 128 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_volume_usage
Error
90.65
test_usage.py

[SF] Trillian test result (tid-9637)
Environment: vmware-67u3 (x2), Advanced Networking with Mgmt server r8
Total time taken: 65846 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8840-t9637-vmware-67u3.zip
Smoke tests completed. 125 look OK, 4 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_02_balanced_drs_algorithm
Failure
157.54
test_cluster_drs.py

test_02_internallb_roundrobin_1RVPC_3VM_HTTP_port80
Error
789.87
test_internal_lb.py

test_02_internallb_roundrobin_1RVPC_3VM_HTTP_port80
Error
789.91
test_internal_lb.py

test_02_vpc_privategw_static_routes
Error
380.12
test_privategw_acl.py

test_03_vpc_privategw_restart_vpc_cleanup
Failure
361.28
test_privategw_acl.py

test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL
Error
646.61
test_vpc_redundant.py

test_02_redundant_VPC_default_routes
Failure
153.16
test_vpc_redundant.py

test_02_redundant_VPC_default_routes
Error
153.17
test_vpc_redundant.py


Search in the correct bundle for resource bundle

If CTFeedback is built as a framework, the resource bundle will be in the framework and not the main bundle. The code has been updated to find the correct bundle containing the resource bundler.

@sirnacnud Thank you for your PR!


Using vscode unit tests environment on travis build system.

I all, I'm currently playing with VSC extensions and create a very simple one in typescript as learning experience about managing nuget packages for project.json - nuget4code, https://github.com/fforjan/nuget4code.
When learning, I'm always trying to do a full slice, including unit testing and build environment.
As I'm using GitHub, I've also link it to the Travis build system.
My npm test action  is currently configure compile only, so I can catch build error which could have been missed on my computer (more likely none ;))
I got some unit tests working on my computer, they are really unit tests, I don't trigger any UI actions or other things, but they are doing import * as vscode from "vscode", use some vscode.Uri and thus require a vscode environment setup to run.
Do you have any idea how to configure Travis to be able to run unit tests ?

I think I heard @dbaeumer and @bpasero discussing about how a Travis CI should look like for extensions.

:+1: same question

Planned for next release and we make sure its documented!

Documented here: https://code.visualstudio.com/docs/extensions/testing-extensions#_running-tests-automatically-on-travis-ci-build-machines

Already used pre3 last week and it's working fine ;)
(i.e. the documentation was online before the package being finally release, this is why I've used pre3...)

Great :)


update readme

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (b3b7f18) 83.67% compared to head (08623af) 83.67%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   83.67%   83.67%
=======================================
  Files          39       39
  Lines        1335     1335
=======================================
  Hits         1117     1117
  Misses        218      218

Flag
Coverage Δ

pytest
83.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


v0.8.4_06: Links are overlapping

SEVERITY: Major
MODULE:  Mountain Chart
Platform: iPhone-5 (iOS 7.1)
RELEASE: v0.8.4
STEPS TO REPRODUCE:

Navigate URL: http://static.gapminderdev.org/vizabi/release/v0.8.4/preview/mountainchart.html
Mountain chart page will be loaded
Note that y axis description is overlapping with the data warning option

ACTUAL RESULTS:
Y axis description is overlapping with the data warning option
EXPECTED RESULTS:
Links should not overlap
SCREENSHOT:

https://github.com/Gapminder/vizabi/pull/765

Retest Result: Pass
Testing Environment - DEVELOP: http://static.gapminderdev.org/vizabi/develop/preview/mountainchart.html


The loss value of softDTW is inf when choosing bandwidth values

Hello @Maghoumi ,
I have tried the example codes you provided as follows, and I noticed that when choosing bandwidth = 1 or 2, the loss values are all inf. Could you please help me solve this issue?
Sample codes:
from soft_dtw_cuda import SoftDTW
batch_size, len_x, len_y, dims = 8, 15, 12, 5
x = torch.rand((batch_size, len_x, dims), requires_grad=True)
y = torch.rand((batch_size, len_y, dims))
sdtw = SoftDTW(use_cuda=False, gamma=0.1, bandwidth=2)
loss = sdtw(x, y)
loss
--- OUTPUT:
tensor([inf, inf, inf, inf, inf, inf, inf, inf], grad_fn=<_SoftDTWBackward>)
sdtw = SoftDTW(use_cuda=False, gamma=0.1, bandwidth=1)
loss = sdtw(x, y)
loss
--- OUTPUT:
tensor([inf, inf, inf, inf, inf, inf, inf, inf], grad_fn=<_SoftDTWBackward>)
Thank you very much.
Regards,

Thanks for posting and example @educationunion! This issue was previously reported in #8 but I didn't have a good minimal example to try. I had a quick look, and I think this is caused by the condition check around here that fails to work as expected when the length of the two sequences being compared is different. This is perhaps the result of adding support for such sequences in (this commit).
I think the condition has take the length of each sequence into account before skipping the calculation.


Update documentation for how to perform rollbacks

Fixes

I noticed that some documentation was out of date or slightly unclear while performing a deploy recently.
Description

This PR updates some documentation around rollbacks following the changes to the release process in https://github.com/WordPress/openverse/pull/3755/files. It also tries to clarify some ambiguity I found confusing (in general, referring to "the workflow" without specifying deployment vs release-app).
Testing Instructions

Read through the documentation and confirm that the updates are accurate. I've left a few questions in comments about things I was not 100% sure of, so please correct me!
Checklist

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

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

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

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

Developer's Certificate of Origin 1.1

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

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

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

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

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

@sarayourfriend Thank you so much for responding so thoroughly!

What do you think, Staci? Would that clarify the ideas? It adds a step to updating production to the latest code, but prevents any possibility of confusion between tagging an image with a "stable release" tag, and the deployment of the app. I think we could delete a fair bit of documentation and remove basically all the caveats that aren't just referncing zero-downtime.

I'm not opposed to separating them out, but I don't know that I would remove much documentation afterward. For me the confusion in the docs was related entirely to ambiguity in phrasing "the process" or "the workflow" etc.
Colloquially we use the phrase "deploying" a service to mean the process of publishing the release and then actually deploying it, and I think we would still do so even if that work required two steps instead of one. When the documentation for a rollback uses language like "repeat the deployment process", to me that really sounds like it's saying to repeat all the steps. The phrases "workflow", "deployment workflow", and "deployment process" all could be interpreted as referring to (1) the actual deployment - <env> <service> workflows in the infra repo, (2) the release-app workflows in the monorepo, or (3) the general process of deploying at a higher level (since you're right, 'publishing', 'process', and 'workflow' are all unfortunately loaded terms).
For me all the confusion is immediately cleared up just by specificity. I read "repeat the deployment process" to mean that I should be publishing a new release somehow, and was immediately confused because that doesn't seem right! If we specify that we mean to use Run Workflow in the infra repo to run just the deployment workflow that immediately makes sense.

Colloquially we use the phrase "deploying" a service to mean the process of publishing the release and then actually deploying it

I read "repeat the deployment process" to mean that I should be publishing a new release somehow

I see, I didn't understand that that was the point of ambiguity, but I see now that my suggestion wouldn't address that, basically at all. Ideally we would not use deployment as a catch-all, but you're right that we do, and there's not much we can really do to just change the language. Thanks for clarifying where the confusion was coming from, and sorry I misunderstood it!


Update sbt, scripted-plugin to 1.3.11

Updates

org.scala-sbt:sbt
org.scala-sbt:scripted-plugin

from 1.2.8 to 1.3.11.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt" } ]

labels: library-update, semver-minor

Coverage remained the same at 87.736% when pulling bd09ceb361db65fa4046be75b842fced4a985246 on scala-steward:update/sbt-1.3.11 into f23bb5b045ec88530ffbd3bf9c03aae033642d1c on iheartradio:master.


Powerwall Firmware Upgrade 22.26.1-foxtrot 4d562eaf - Animation Issues

The latest Powerwall upgrade (22.26.1-foxtrot 4d562eaf) may have resulted in the animation to stop/flash and may require pypowerwall to be restarted:
# restart pypowerwall
docker restart pypowerwall

It also renders something different.  It now has a "compliance" text link in the graphic:

An issue has been opened to see if this can be addressed in the pyPowerwall Proxy: https://github.com/jasonacox/pypowerwall/issues/24

This is fixed with latest pypowerwall proxy release (0.6.0 build t19).  The upgrade.sh script should upgrade this for you.


Smaller Sum

If you can Find what's wrong Debug the following code and make a PR
Problem link

My Solution:
class Solution{
public:
#define ll long long

    vector<long long> smallerSum(int n,vector<int> &arr){
        int mx = INT_MIN;
        priority_queue<int, vector<int>, greater<int>>pq;
        for(auto &it : arr)
        {
            if(it > mx)mx = it;
            pq.push(it);
        }
        vector<ll>v(mx + 1, -1);
        ll sum = 0;
        while(pq.size())
        {
            int t = pq.top();
            pq.pop();

           if(v[t] == -1) v[t] = (int)sum;
            sum += (t *1LL);
        }
        vector<long long>ans;
        for(auto &it : arr)
        {
            ans.push_back(v[it] *1LL);
        }
        return ans;

    }
};

Hey @sceary-expert please assign this task to me.


Add a list of download buttons for each episode to the LTI series list

Download button dropdown on the LTI series list
Adds a dropdown to each episode in a series. Clicking an entry in the dropdown
will download the corresponding video file. @wsmirnow
This pull request is intended as a quick change to r/8.x and will very likely be overwritten in r/9.x.
Expected result:

Your pull request should…

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch (features can only go into develop)
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated testing
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits
[ ] have appropriate tags applied

Note that this likely conflicts with #1289

Not all institutions want to make it so easy to download the video files. Can this be made configurable?

This is also pointed at develop, which would be 9.x.  You likely want to point this at r/8.x.

This is also pointed at develop, which would be 9.x. You likely want to point this at r/8.x.

Not sure if we really want to bring this in before #1289? This should at least go by the release managers (@karendolan, @rrolf). We are not only putting a feature in 8.x this time but deliberately breaking another pull request (we do that, correct? I'm actually just assuming that.). But then… it's not my pull request so I care less then I would otherwise ;-P

IMO #1289 takes priority since its larger and been around too long. I have it built, was going to look at it in the next couple of days.
I was only commenting on the branch target since the description mentions 8.x. I don't really care where this goes, or if it goes in at all :)

The pull request is too specific to be merged into any main branch.


Tidy up doc build

Our current doc build fails if we turn on the strict option in makedocs. This happens because of three things:

Missing docstrings
Some functions with docstrings aren't referenced in the documentation.
Failed scripts
The zoom lens example needs to be removed or fixed. I think some of the latest changes also added some broken scripts.
Duplicate references
I don't think that ref.md is a suitable solution to the missing docstrings problem, as Documenter.jl expects each docstring to be rendered in one place only. For example, this breaks the reference to AcceleratedParametricSurface in the surfaceintersection docstring. Removing ref.md will likely introduce a lot of missing docstrings, so this fix will require a significant amount of work. But I think it'll improve the quality of our documentation in the long run.

I started out trying to fix this in PR #83, but the scale of work in item 3 requires a separate PR.

I also noticed the CSG example seems to be broken

If the zoom lens example hasn't already been removed then go ahead and remove it.

I'm removing it in PR #83. I may be able to work with chdf to reintroduce it later (see #57).

@alfredclwong is this issue still active or has it been addressed by a PR that has been merged, in which case we can close this issue.

If you look in the logs for the Documentation builds, there are a load of warning messages. They're allowed through because we haven't set the strict = true option in makedocs. But they should really be build failures, as they're allowing a lot of broken docs through.
For example, the Transform link in Emitters (NEW) is broken, as is the OpticSim link in Examples, as well as the first two links in makemesh, to name a few. The first two errors are confusing because the doc build works differently on the remote server compared to locally.
I'll try to get to the meeting on Thursday to talk about that last point - really sorry about missing the last few. But yes, the issue is still active.

Low priority issue - closing for now.


Light Theme - Nav Section shows selected tab in black

secondary color is black in Light theme, so 'projects' when selected isn't highlighted in blue
blue looks better

Fixed in pull req

Fixed in ed53065


Clarification on the reference strain used

Hi!
I am trying to run PlasmidSeeker against a dataset that contains strains from different species of the same genus to investigate plasmid distribution across at the genus level.
Would it be better to use a single reference strain for all the runs or I should use a different reference strain (that is closer to the specific species) every time I interrogate a different species.
Could you conceptually explain how the reference strain is used by the algorithm so I can understand your response better?
Thank you very much for all your help.
Leonardos

Hi!
One of the goals for PlasmidSeeker is estimating the copy number per cell of the identified plasmid. Since there are multiple bacterial cells with multiple copies of plasmids in the sample we need the ratio of plasmid to genomic to get the copy number per cell estimate (assuming that the bacterial genome is 1 copy per cell). This is also the reason for the isolate requirement because in case of a mix of species we cannot say from which cell the plasmid originates and therefore cannot calculate the ratio and copy number.
Please refer to the paper for additional information (https://peerj.com/articles/4588/).
I can't see how using different bacterial reference genomes yields any meaningful abundance information because the same plasmid can be in different species in varying copy numbers resulting in a single signal which can't be separated.
That being said, choosing one species and running PlasmidSeeker should output which plasmids are in the sample. In this case all abundance info should be regarded critically or to be safe, discarded.
Hope it helps,
Mihkel

Mihkel thank you very much for your reply.
I have to admit that I am still a bit confused. From your reply and your paper I understand that the reference chromosomal isolate given with the -b option should be as close as possible to the query isolate.
So lets suppose I have 10 Klebsiella pneumoniae strains and 10 Klebsiella oxytoca strains that I want to interrogate using your algorithm. And lets suppose I want to use the abundance information for each plasmid. Then I should use a  Klebsiella pneumoniae reference strain for my 10 Klebsiella pneumoniae isolates and a Klebsiella oxytoca strain for the other 10 Klebsiella oxytoca strains. Do I get this correctly?
What happens if I use the assembly of the query isolate itself as reference? Would that be a good practice as in my head this should be the perfect reference for the query isolate?
Apologies for my confusion but I would like to make this clear so I can understand what I am doing.
Thank you very much for your help.
Leonardos

Hi
If you have a sample (1 fastq) containing only 1 strain then yes, you can use a Klebsiella pneumoniae reference strain for all 10 Klebsiella pneumoniae samples. The requirement is that there is only one strain in the mix. If the sample strains are quite different, you might need to identify a close reference strain for each of them individually (using for example http://bioinfo.ut.ee/strainseeker/).
Though the query isolate assembly might be the perfect reference (and this applies also to any reference), be sure that there are no plasmids in the assembly. If you'd just assemble the raw sequences without any cleaning, you will have plasmids in your assembly. Removing plasmid sequences might also prove a bit cumbersome, so I'd suggest identifying a suitable reference first and then running PlasmidSeeker.
If, on the other hand, you have a mix of different strains/species (all in one fastq), there are problems with estimating abundance as discussed above.
Mihkel

Plasmidseeker uses the closest bacterial genome to estimate bacterial genome coverage by looking at k-mers shared by your reads and the assembly.
If you are using a remote strain, some of the k-mers from the bacterium in your reads would be missing from the remote one and some might be doubled. The more remote the assembly is, the more bias you introduce.
In short - using the same species as the closest strain should be OK for most purposes.


Renaming the project

Hello!
I was wondering if you would not mind renaming your project, I think there could be some confusion at this point because both projects have slightly different options now.

I have been thinking about it as well but it seems to be pretty hard at this moment.
This tool is widely used and renaming the binary will break a lot of users. It is such a shame that boom was supposed to be a reference program only but it is also actively used.

I am wondering why you kept my project name for your fork though. You made the mistake to use my project name to publish your fork, you should go through the pain of renaming it - not me...
By refusing to rename it, you are basically hijacking it this point, what makes me cringe the most is your "copyright google" in there.
Not cool, this is not how open source works.

I am sorry. I am not happy with the current name neither trying to keep it. The situation is renaming things just won't take the history back, such as it won't change the existing references to this project or the articles on the Internet. The confusion will keep being there. This is what I want to address first.
It is not cool that you are attacking me by calling it a "hijack". When I published this tool, I let you know and the README gave credit to your project credit from the very beginning. https://twitter.com/rakyll/status/419939763404435456
It is probably my fault I haven't renamed it when it attracted people.
I am very disappointed in your response above and escalation of this issue on Twitter.

I am wondering why you kept my project name for your fork though

This repo is not derived from your work. It is a port not a fork.

The confusion will keep being there

You have created the confusion.

It is not cool that you are attacking me by calling it a "hijack"

If you keep the same name it is a hijack. Nothing else.

I let you know and the README gave credit to your project credit from the very beginning

Yes, and I was very happy that your forked the project. But I did not know you were going to publish it under the exact same name. EVEN THE COMMAND LINE IS THE SAME NAME

I am very disappointed in your response above and escalation of this issue on Twitter.

It's not personal, it's just the consequence of your unwillingness to rename the project, which demonstrates the fact that you made the decision to own my project name when I am telling you I don't want you to do it.
I was pretty sure you have good intents, until you said "no" to the renaming. If you want to do the right thing, you need to rename it. If you don't rename it, you being the bad guy, not me.

This repo is not derived from your work. It is a port not a fork.

It's not a port. You added different options. It's a different project now, and you are using my project name. Which is the only issue here. It's called a hijack.

But I did not know you were going to publish it under the exact same name. EVEN THE COMMAND LINE IS THE SAME NAME

It was already PUBLIC(*) when I wrote it to you. I haven't "published" it. Someone shared it on Reddit and that's how it got popular. I am not maintaining this project since then.
Whatever you are complaining about is not the actual story and I haven't said "no". I haven't closed the issue. Read my comments above and see the occurrence of "no"s. I explained the case and the problem because of the name collision.
This project is not a fork of your project. It is not derived from your work. You are trying to claim copyright on interfaces.

Because yelling at people makes your argument stronger.

If it is not clear from my initial response, I am trying to understand the impact on the existing users.
non-breaking:

go gets will be redirected
the repo will be redirected

breaking:

all references to boom will not work
the binary name will change
docker hub image needs to be updated

I will update the list as more significant items come to my mind.

I haven't said "no"

Ah ok, sorry I have interpreted this as a no: "it seems to be pretty hard at this moment. This tool is widely used and renaming the binary will break a lot of users"

Whatever you are complaining about is not the actual story

why are you trying to argue when the thing is super simple ? you are using 'boom' as a name for your tool.

You are trying to claim copyright on interfaces.

Interfaces ?  I am not sure what you are talking about. I am not claiming any specific stuff about
whatever you do in your project. My claim is simple, I am asking you to rename it.
If you are willing to do it, e.g re-release it under a new name, then the argument is over.
I apologize if you feel that I am attacking you, or if I am overreacting. But try to think for a second from my point of view: when I asked you to rename it, your answer did not sound at all like a yes to me and my reaction was to think that you are not going to do it.
If we can work this out then, cool.

why are you trying to argue when the thing is super simple ? you are using 'boom' as a name for your tool.

I am not arguing. You are arguing with me and escalating things to public even though I want to fix this problem. Please stop blaming me for your poor communication skills.

Interfaces ? I am not sure what you are talking about.

"EVEN THE COMMAND LINE IS THE SAME NAME" I am trying to understand what you mean here.
I kindly request you to apologize me in public for your misunderstanding and unnecessary reaction.
I will rename the project right after getting done with the list at https://github.com/rakyll/boom/issues/130#issuecomment-244308044.

Please stop blaming me for your poor communication skills.

I don't think you're better than me in communication skills. We would not be doing all this argument otherwise. The project would already be renamed.

"EVEN THE COMMAND LINE IS THE SAME NAME" I am trying to understand what you mean here.

To use the tool, the command line to call in your shell is "boom", e.g.
$ boom
which means that if people install mine and yours, I am not even sure which one prevails

I kindly request you to apologize me in public for your misunderstanding and unnecessary reaction.

I did, before I even saw this request :)

How about forking current boom project(go version), renaming it to something like "gboom" or "boomg" and keeping the existing one with a deprecation / forward notice?
So nothing will be broken for anyone, go version will have a new name.

re: gboom

g'ing things kinda resembles Google stuff. Given copyright is also shared with Google. I think we should never g name. goboom might be ok but very mouthful.
I have another suggestion at https://github.com/rakyll/boom/pull/131. Not sure that it will be fine.

Ah, ab+ is an invalid import path to begin with. Not going to work. Suggestions are welcome.

boomg was short for (bo-OMG), I meant 'g' as abbreviation to go, not google, but fair enough, maybe a 'boom' like name is not a good idea anymore.

How about forking current boom project(go version), renaming it to something like "gboom" or "boomg" and keeping the existing one with a deprecation / forward notice?

As long as we don't change the import path, people won't move. I am not sure what's the percentage of people who are visiting the project README. They see the go get github.com/rakyll/boom on the wild Web and copy paste into their terminal.
These cases are what I wanted to investigate before jumping on a solution that is not going to fix anything.

As long as we don't change the import path, people won't move. I am not sure what's the percentage of people who are visiting the project README. They see the go get github.com/rakyll/boom on the wild Web and copy paste into their terminal.

You can put the deprecation notice into code. Something like:
$boom
*** boom is deprecated, please use  from  **
...usual boom output...

You can put the deprecation notice into code. Something like:

SGTM
I will also migrate the issues to the new repo.

maybe a 'boom' like name is not a good idea anymore.

I'd prefer something distinct and short. I was thinking about a word around salutation. "hey" could be nice.

The project lives under https://github.com/rakyll/hey now.


generated code is not valid when there is no namespace (foreign class is in root scope)

https://github.com/StefH/ProxyInterfaceSourceGenerator/pull/21


Detected as Trojan:Script/Wacatac.B!ml by Windows Defender

Windows Defender basically puts your computer into panic mode when you try to run this. And it also deleted the file imediatelly

Windows Defender basically puts your computer into panic mode when you try to run this. And it also deleted the file imediatelly

For now you can add a exclusion https://support.microsoft.com/en-gb/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26#:~:text=Go to Start > Settings > Update,%2C file types%2C or process.

I was able to add an exclusion, but it's pretty annoying.
GStudiosX @.***> escreveu (sexta, 17/05/2024 à(s)
18:34):

Windows Defender basically puts your computer into panic mode when you try
to run this. And it also deleted the file imediatelly
For now you can add a exclusion
https://support.microsoft.com/en-gb/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26
—
Reply to this email directly, view it on GitHub
https://github.com/face-hh/webx/issues/4#issuecomment-2118090999, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ3M5XUPN7X3R7UUCHE3RDLZCY5RVAVCNFSM6AAAAABH4PBRXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGA4TAOJZHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

The reason why this happens is because Windows Defender flags WinRar self-extracting archives as viruses for some reason. (They're probably used a lot for distributing malware)
It should be fixed by next release, which will hopefully have a different installer 🙂

This has been fixed in v1.2.0


Add @DelegatesTo on the groovy dsl pact builders to allow IDE code co…

…mpletion.
This may not be the most ideal solution to this problem but it was the most straightforward.

Nice! I didn't know about the @DelegatesTo annotation.


Swagger merges two different models with the same name

I have two namespaces for example:
export namespace Ns1 {
    export class Create {
        abc: string;
    }
}

export namespace Ns2 {
    export class Create {
        xyz: string;
    }
}

When i use them with actions:
create(@BodyParams() params: Ns1.Create) {
    return true;
}

create2(@BodyParams() params: Ns2.Create) {
    return true;
}

Swagger creates one common model called Create that's got the following structure:
{
    abc: string,
    xyz: string
}

Not sure how much it's easy to fix, but would be awesome. Thanks :)

Hum the problem come fron jsonschema which store the shema by te class name abd not from the symbol. Not easy ro fix that. I’ll try to fix that in future.

Ok, thanks!
Maybe an additional decorator can solve it that allows to set a custom name. Like @SwaggerName('Create2') or something like that.

@Name is available for that :)


Update ruby version & re-activate schema checker

This upgrades the version of Ruby used by the site-building tools to 2.6.4, which is listed as the latest stable version on https://www.ruby-lang.org/en/downloads/ .  It also re-enables the schema checker that was part of #168 but removed in #174 due to an incompatibility between the Gemfile and the Netlify preview and deployment scripts.  (I still don't know what the specific problem was, but upgrading Ruby fixes it in my tests.)
If you've previously installed Ruby (e.g. per our README.md), you will need to install the latest version of Ruby.  If you followed the README's previous install instructions to use rvm, you can do this with a single command:
rvm install ruby-2.6.4

After it's installed, rvm will automatically select the correct ruby when you enter the repository top-level directory (if you're already in the directory when the ruby version changes, you can use cd . to switch).
This change in ruby versions should not produce any meaningful content differences in the site, so the testing procedure I recommend is:
rvm install ruby-2.6.4
git blah blah ## checkout this branch
cd . ## use correct ruby (new ruby version)
make  ## build site and run tests
cp -a _site _new_site ## backup new site content
git reset --hard HEAD^^ ## throw away this PR's changes
cd . ## use correct ruby (old ruby version)
make
diff -ru _site _new_site | colordiff | less -R  ## see what's changed

For me, the new ruby caused a bunch of JSON associative arrays to have a different sort order, which is annoying to scan through but not a functional change.  All other content was unaffected.
Note: normally I'd upgrade Ruby in a separate PR from adding dependencies (the revert commit) but I think it's better to do both together here to ensure upgrading Ruby truly eliminates the dependency problem.
My thanks to @schmidty for making the Netlify build logs public.

For info, Ruby 2.7.0 will be released around Christmas time as per the Ruby major release tradition.

Removed make test instructions from the README.  (The tests were recently split into two parts, those that can be run before site build and those that can be run after.  Both parts are automatically run in the correct sequence by make without a specific target.)

tACK f8eff5a3aaacfbb14be921de090b1f4419e05d38


topic update for first post vacation meeting

Any other suggestions for upcoming meetings?
Should the meetings in workshop weeks be related to the workshop happening? Or just short check-ins without topic?

Thanks! Probably good to have the meetings during workshops weeks to relate to the workshops.


Update documentation for FileInfo/DirectoryInfo

Summary of the new feature / enhancement
Issue copied from https://github.com/MicrosoftDocs/PowerShell-Docs/issues/8505
Due to the addition of ResolvedTarget in issue https://github.com/PowerShell/PowerShell/issues/13366 and PR https://github.com/PowerShell/PowerShell/pull/16490, and the lack of any mention of PowerShell on the C# page for FileInfo and DirectoryInfo, it may make sense to create a separate page for these objects in the PowerShell documentation, so they may have the aforementioned ResolvedTarget property, which doesn't exist outside of PowerShell.
Proposed technical implementation details (optional)
.NET API documentation must be updated in the PowerShell source code.

Maybe ResolveLinkTarget?
PS >  [IO.FileInfo]::new("$pwd\file.ext") | gm *Target

   TypeName: System.IO.FileInfo

Name              MemberType    Definition
----              ----------    ----------
Target            AliasProperty Target = LinkTarget
ResolveLinkTarget Method        System.IO.FileSystemInfo ResolveLinkTarget(bool returnFinalTarget)
LinkTarget        Property      string LinkTarget {get;}

ResolveLinkTarget and ResolvedTarget are a bit different:
ResolveLinkTarget resolves the link target and returns null if the file isn't a symbolic link
ResolvedTarget resolves the link target, but returns a path to itself if it isn't a symbolic link


Static website using GitHub Pages showing details about the project. (Readme Content)

Readme Content to be shown on the home page for WarpSQL.

Readme Content to be shown on the home page for WarpSQL.

I would like to work on the issue. I just forked and cloned the repository but firstly it said checkout failed.

then on running 'git status' command all the files were staged and deleted.

Is the problem with my system. I am currently restoring them but if you would satisfy my query .

Created a Pull Request #95 .
Please review it.


[Linked Account] Add account list tab in send page

This feature already add in ios prod version 2.1.8(1)


Api docstrings

Added explanation for the _score value returned when searching the Hestia database

@TimoDiepers what's the file to create the csv about? Did you intend to add it or is it an oversight?

@tfardet Chris asked for the script I used to generate the csv file - he thought about adding additional columns I believe


BMI calculator

Body mass index (BMI) is a value derived from the weight and height of a person. BMI indicates weather person is having over or under weight or not so person have an idea of health issue or not. Can I work on this issue @Srijita-Mandal ?

Hey @Srijita-Mandal waiting for response.


WebAssembly served with incorrect MIME type

WebAssembly (.wasm) files served with incorrect MIME type, it would make sense for simplehttpserver to serve them with the correct MIME type out of the box as the server is intended for debugging purposes.
Steps to reproduce:

Acquire or create a web assembly file (".wasm" extension)
Run simplehttpserver in the folder containing the .wasm file
Make a http GET request for the wasm file

Observed: WebAssembly .wasm files are served with "application/octet-stream" MIME type
Expected: WebAssembly .wasm files are served with "application/wasm" MIME type

Added the out of the box support for .wasm mime type in release 0.3.0.
This version also contains support for defining custom mime types.


Format the doc

Changes

Fix a typo in Subjects of source-code-version-control
Fix typos in continous-integration
Fix a link

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has the primer doc been updated if a design decision is involved
[ ] Have the JSON schemas been updated if the specification changed
[ ] Has spec version and event versions been updated according to the versioning policy
[x] Meets the CDEvents contributor standards

@t-kikuc, please sign the commits in this PR so we can merge it.

@e-backmark-ericsson
Sorry,  I fixed 👍


async/await checks are too aggressive and even escape type: ignore

I happen to use a third-party library (Mandrill) that has various functions that take the async keyword:
https://mandrillapp.com/api/docs/index.python.html
The error is this, and it applies even if you add a type: ignore on the affected line:
/tmp/foo.py:1: error: 'async' and 'await' will become reserved keywords in Python 3.7
def foo(async=True):
    pass

foo(async=False)  # type: ignore

You get the same thing with even this:
x = dict(async=False)  # type: ignore

Other keywords don't have this problem (x = dict(type=False) works fine), so I think this is just a bug with this new friendly check for new keywords.
This is basically a blocker for upgrading to mypy 0.501 for us, since I don't think there's a clean workaround (I could change to passing **{'async': False'}, but that's kinda absurd).

Oops was meant to be against the mypy repo.


Does not support the ARM

First many thanks to the great contributors for making such an amazing project. Thank you for your efforts! 🍺
Reproduce steps:

git clone https://github.com/dohooo/node-usb-reproduction.git
yarn
yarn watch

You will then see this error on the console, The code is here /Users/zhaodonghao/code/temp/vite-electron-builder/packages/preload/src/sha256sum.ts
Logs:

localhost-1643350529203.log
Does it look like the ARM compiled version is not found??  This mistake gives me a headache and I hope I can get help

@thegecko 🙏

Related with https://github.com/electron/electron/issues/32662

Thanks for noticing this, it was an oversight


Increase timeout for stopAfterSecondaryTransition test

Failures seen in CI builds for this test all indicate the thread isn't joining after 10s (the previously configured timeout). Increasing the timeout should solve the issue if the code is working correctly. Otherwise, if the test is still failing after increasing the timeout, then there is a logic bug somewhere when transitioning states

Codecov Report

Merging #13472 (af62871) into master (92653af) will decrease coverage by 26.38%.
The diff coverage is n/a.

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

@ZacBlanco Can you try relaunching tests few times and see if this change improves test stability?


Does not work with Rust

I already checked if rust-mode is being detected and it is. By doesn't work i mean that it did show up in discord when i was editing a lisp file, (.emacs), but it does not update when I switch to a Rust file

What major mode are you using for editing Rust files?

how do i check?

When in a rust file. you can do
M-: RET major-mode RET
to check the value of major-mode (that is, Alt+Shift+Colon, then type major-mode)

it says rust-mode

now it picked it up

Oh, is it working?
elcord updates every so often (15 seconds until recently and now it's customizable)
so it may not pick it up right away. This is following the update guidelines here: https://discordapp.com/developers/docs/rich-presence/how-to
which says to update every 15 seconds

it started updating just now, I have installed it a few days prior, it never worked, so I looked into it just now and it started working. ¯_(ツ)_/¯
Thanks for the help, if something breaks, I'll let you know. Oh and this package is great when compared to the other one.

Great!
Let us know if run into any trouble.


Gradle 7.1 + IntellJ Ultimate 2021.2.1 -> Error: could not find or load main class while running java application on usb / removable drive.

Expected Behavior
Gradle should build and run the java application on any drive.
Current Behavior
Error: could not find or load main class: <main_class_name> , when running project from a removable drive (USB).
Context
Every time I try to run my Java application which is stored on a removable drive (usb, FAT32), I get this message. Same project works great on main drives (NTFS).
Steps to Reproduce

Create a new Gradle project with SDK 14 on a removable drive / USB on IntellJ Ultimate edition 2021.2.1 . (Not tested with other IDEs)
Create package and main class.
Add the correct class name to the build.gradle options file.
Run the gradle task to run the application.
First time should work.
Retry.
Gradle cannot find the main class.
All tasks works (even build), but not run.

Workarounds
Workaround 1

Modify the main class name in the build.gradle options file to anything you want.
Run the gradle task to run the application.
Gradle cannot find the main class (Expected since we changed the main class name in the options).
Modify the main class name in the build.gradle options file to the correct class name.
Step 2.
It works. Spoiler: Retrying after gives the same error and it is back to step 1.

Problem: Inconvenient when wanting to test code effectively.
Workaround 2:

Put project on main drive.

Problem: Inconveniant when project needs to be constantly accessed and moved on different computers which don't have necessarily internet connection available (No git project then). Putting the project on the desktop main drive ruins the portability of said project.
Your Environment
Windows 10
Intellj IDEA Ultimate 2021.2.1
Gradle 7.1
Build scan URL: <Would post if the scan was not that much invasive into unecessary data collection (ex: IP, Usernames, etc..)>

Should be fixed in 7.2, pls. give that a try. If the problem persists, pls. reply here.

Fixed in #17551


[Theme Request] Focalors

Who/What do you want to be featured?
Focalors / Furina
What do they look like?

What type of theme?

[ ] Dark Theme

Additional Information (Optional)
no idea i just love your themes and want her to be in this hall of fame as well


Merge in WIP/NoDS

For #

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #14436 into main will increase coverage by 6.01%.
The diff coverage is 51.82%.

@@            Coverage Diff             @@
##             main   #14436      +/-   ##
==========================================
+ Coverage   59.90%   65.92%   +6.01%
==========================================
  Files         696      535     -161
  Lines       38473    24376   -14097
  Branches     5534     3423    -2111
==========================================
- Hits        23047    16069    -6978
+ Misses      14243     7655    -6588
+ Partials     1183      652     -531

Impacted Files
Coverage Δ

src/client/activation/common/activatorBase.ts
14.41% <0.00%> (+1.19%)
:arrow_up:

...rc/client/activation/jedi/multiplexingActivator.ts
17.74% <0.00%> (ø)

src/client/activation/node/languageServerProxy.ts
26.58% <0.00%> (ø)

src/client/activation/refCountedLanguageServer.ts
41.30% <0.00%> (ø)

src/client/activation/types.ts
100.00% <ø> (ø)

...t/common/application/webviewPanels/webviewPanel.ts
10.52% <0.00%> (ø)

src/client/common/application/webviews/webview.ts
16.00% <0.00%> (-3.24%)
:arrow_down:

src/client/common/configSettings.ts
69.55% <ø> (+0.26%)
:arrow_up:

src/client/common/experiments/groups.ts
100.00% <ø> (ø)

src/client/common/experiments/manager.ts
95.86% <ø> (-0.14%)
:arrow_down:

... and 165 more

Continue to review full report at Codecov.

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


Implement string conversion methods

Both MultiwordInt and FixedPoint should have methods to convert them to strings, possibly with the usual floating-point modifiers for FixedPoint (i.e. precision and printing as scientific/engineering/...)

Hi. I want to take this issue.

Awesome! I think the best way to do this here would be to have to_string() methods on both classes that each return a std::string - std::to_string doesn't allow you to have options like the precision, and using a std::stringstream feels a bit heavy.
Something like
MultiwordInteger::to_string() const;
FixedPoint::to_string(unsigned precision);

should work fine, possibly with some optional enum parameter for the FixedPoint version that lets you select scientific/engineering/etc notations, like the %e, %f, %g specifiers for printf, if you don't think that it's too much work. Maybe do it in a second pull request :)
I haven't thought about the implementation details too much, but I'd use a (for MultiwordInteger) char[size/3+2] as buffer and create and return an std::string from that.
For FixedPoint numbers, the needed string length should not be larger than integralWidth/3+fractionalWidth+2.
Please do let me know if anything's unclear :)

... The entries in MultiwordInteger::v are little-endian, i.e. with uint8_t as backing storage type 256 would be stored as [0, 1].


Change camera icon position in list

Version information

Device: iPhone 12 Pro max
OS:  iOS 14.4
Package Version: wechat_assets_picker: ^6.1.2 ,  wechat_camera_picker: ^2.4.2
Flutter Version: v2.5.0

Is your feature request related to a problem?
i want to set icon of capture image from camera in first item or row.
you can see i have attached one screen shot, camera icon is show in last item.
Additional context

final List<AssetEntity> resultList = await AssetPicker.pickAssets(
        context,
        textDelegate: EnglishTextDelegate(),
        specialItemPosition: SpecialItemPosition.prepend,
        requestType: RequestType.image,
        specialItemBuilder: (BuildContext context) {
          return GestureDetector(
            behavior: HitTestBehavior.opaque,
            onTap: () async {
              final AssetEntity result = await CameraPicker.pickFromCamera(
                context,
                textDelegate: EnglishCameraPickerTextDelegate(),
              );
              if (result != null) {
                final AssetPicker<AssetEntity, AssetPathEntity> picker =
                    context.findAncestorWidgetOfExactType();
                if (picker != null) {
                  final DefaultAssetPickerProvider p =
                      picker.builder.provider as DefaultAssetPickerProvider;
                  await p.currentPathEntity.refreshPathProperties();
                  p.switchPath(p.currentPathEntity);
                  p.selectAsset(result);
                }
              }
            },
            child: const Center(
              child: Icon(Icons.camera_enhance, size: 42.0),
            ),
          );
        },
      );

This is by design, since the assets grid is reversed in the iOS Gallery app and also in the WeChat.

@AlexV525  any other options to make camera option in first item for ios

@AlexV525 any other options to make camera option in first item for ios

We do have other way to make reverse it back, which is extended the DefaultAssetPickerBuilderDelegate, and treat the grid same as Android.
https://github.com/fluttercandies/flutter_wechat_assets_picker/blob/19e6058fb700747204d2cc11174133e34b2acc41/lib/src/delegates/asset_picker_builder_delegate.dart#L939

You can use shouldRevertGrid when picking after you upgraded to v6.2.0 .


Constraints to insert static numbers

🚀 Feature
prims operations should be able to insert contraints on prologue trace.
Motivation
Issue first brought up here: https://github.com/Lightning-AI/lightning-thunder/issues/262#issuecomment-2127729530

problem arising from slice -> dynamic shape support?

Looking at the computation trace here for a slice_prim:
    # t18 = prims.slice_prim(a, [0, 0, 0], [8, 16, i8], [1, 1, 1])  # t18: "cuda:0 f32[8, 16, [IntegerProxy name=i17, value=2]]"

We notice that the output TensorProxy has a shape of [8, 16, [IntegerProxy name=i17, value=2]], where the last dimension with size i17 is not produced in the trace. This is because prim has arithmetic operation defined inside meta functions, as defined here:
https://github.com/Lightning-AI/lightning-thunder/blob/b7154dc77b5bf8a02bcbc2e56310c62fd75808ff/thunder/core/prims.py#L3102
Ideally we would want to expose that logic in the trace in order to support dynamic shape, we should lift the shape logic to clang instead of meta. (See note 1 in alternatives)

operations that would to insert static constraints

operations should be able to insert constraints by marking certain NumberProxy/TensorProxy dimensions as static shaped. e.g. axes args for a reduction operation could be a dynamic NumberProxy, which would instead want to bake in as static.
This would also allow us to temporarily resolve issue regarding prim operation which we have not yet added dynamic shape support.
In the slice_prim example above, we could have marked i8 as a static and adding a constraint as i8 == 2. This would allow us to have slice working without proper dynamic shape support. Which would be nice to keep #262 moving forward.
Pitches
We can use check_number_type_and_value prim for the check. The challenge here is to propagate the proper check into prologue trace.
Taking the slice example above, the operation would want to check_number_type_and_value(i8, pyval(i8)). But there's not guarantee that it's legit operation in prologue trace, which would require i8 to be a direct input. So we would want to project static_constraints from i8 to its producers, which could be NumberProxy as well as TensorProxy's attributes.
Alternatives
note 1:
(Alternatively we can think about having logic to trace through prim_meta functions.)

Another example coming from https://github.com/Lightning-AI/lightning-thunder/pull/575#issuecomment-2161257731
import thunder
import torch

def foo(dev, idx):
    return torch.ones(1, device=torch.device(dev, idx))

# jfoo = thunder.jit(foo)  # works
jfoo = thunder.jit(foo, cache=thunder.CACHE_OPTIONS.SYMBOLIC_VALUES)
print(jfoo("cuda", 0))  # fails as our current implementation can't handle `IntegerProxy`.
print(jfoo("cuda", 1))

# print(thunder.last_prologue_traces(jfoo)[-1])
# print(thunder.last_traces(jfoo)[-1])

brainstorm to myself:
I'm thinking about adding a flag to numberproxy to mark them as static_constraint.
i.e. for control flow, we need to insert those constraints on proxies as we see fit. As the example above with
if flag > 5:

Which translate to something like
  5           0 LOAD_FAST                0 (flag)
              2 LOAD_CONST               1 (5)
              4 COMPARE_OP               4 (>)

https://github.com/Lightning-AI/lightning-thunder/blob/main/thunder/core/interpreter.py#L5082
We need to pop the stack. inspect for proxy and modify its static_constraint flag before wrapped it as a python value to bake in control flow.

So our idea was to make "evaluate to bool" the time when we record the constraint, i.e. for this, we would check if flag > 5 and record flag > 5 or not (flag  > 5) as a constraint. (Unfortunately, not (flag > 5) is true more often than flag <= 5 due to NaN and might be overriden.
Note that it we absolutely need to implement mapping comparison ops to __lt__ and firends to jit through them. (And then you can use lookasides.)

Started #586 to fix the control flow stuff. it seems to have this example working now.
https://github.com/Lightning-AI/lightning-thunder/issues/463#issuecomment-2161242845

Since resnet issue is also resolved (regarding grad transform. I'm closing this PR)


St Finians Community College

@RyanForan19 First stage of verification passed, official domain is stfinianscc.ie as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@philipto Thank you for the feedback, I hope to hear for the final decision soon. Would you require any other information about the school?

Hello @RyanForan19,
I can see in the contact of the website a different domain —<EMAIL_ADDRESS>So could you please provide us with a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students?

Hi @KiraBobyleva, the reason why the contact of the school is<EMAIL_ADDRESS>is because the school is ran by the Dublin and Dun Laoghaire Education and Training Board (DDLETB). One thing I wanted to note is, the schools email system is set up to receive emails on same-domain. I am unsure how I can relate the domain of ddletb.ie and stfinianscc.ie, but I have attached a screenshot of my school emails, and am hoping that suffices.

Hi @RyanForan19,
Thank you! Pull request merged.


New log out of Status

Final draft of "Log out of Status"

Thanks for the docs update, @cheny0 !
After reviewing your document and implementing the changes, you don't need to send a new PR for a second review. You can go ahead and merge into develop + merge into master to publish the doc :)


Add dotnet-core-buildpack BOSH release

Add src/dotnet-core-buildpack-release submodule
Add job, package symlinks
Update spec fixtures
Update templates
Upload dotnet-core-buildpack v1.0.3 blob

[#131997427]
Signed-off-by: Jacques Chester<EMAIL_ADDRESS>

@sesmith177 It looks like this PR got rebased (instead of merged) by mistake, but you can see that the commit is on develop: https://github.com/cloudfoundry/cf-release/commit/9f456dd29c330be0cb621f50b17a458086939fca
@jaresty && @staylor14, does this sound right?
If we've confirmed that all the necessary changes are in develop, can @sesmith177 close the PR?

@dsabeti That sounds correct.  Thanks!


docs: add clarification to the info on UserAccount

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fix documentation clarity on what BlobCache.UserAccount do
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements

[ ] The commit follows our guidelines: https://github.com/Akavache/Akavache/blob/master/CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

@appbureauet excellent, thanks!


Require 'foundation' before the rest of the JS files

Trying to require other JS files before "foundation" results in JS errors when those files try to reference "Foundation".

:+1: This is a real problem.

yep, have been bitten by this, too.

yes, there is a problem "Can't find variable: Foundation"

:+1:
Should be released soon :blue_heart:
Thanks

Finally I found out why closing alert boxes didn't work any longer ;)

Great! waiting for the release.

This hasn't been released on rubygems yet.. https://rubygems.org/gems/foundation-rails

You could use:
gem 'foundation-rails', github:'zurb/foundation-rails', tag:'v<IP_ADDRESS>'
in your Gemfile for now and run bundle update foundation-rails for now if I'm not mistaken.
The version number will still be <IP_ADDRESS> but I guess the maintainers will do this as soon as they deem the <IP_ADDRESS> version ready for the public.

Sorry guys for the delay. I don't have access rights to push this to RubyGems myself. I only tagged <IP_ADDRESS> to let you use it in your Gemfiles.
I tried to reach @arthurzurb by email asking him to push it, and also asking for access rights if possible.
Help me in reaching @zurb/owners folks. Looks like the Yeti ate them all :yum:
Here is my email sent the 26/03, if it helps

Hello Arthur,

I am sorry to bother you by email. I can’t find a better way :)
I just tagged a new version for foundation-rails, fixing bas JS loading in Rails. https://github.com/zurb/foundation-rails/releases/tag/v<IP_ADDRESS> (follow up to https://github.com/zurb/foundation-rails/pull/117)
Can you pls push it to RubyGems?

Speaking of that, I can maybe help you guys with this, by taking care of foundation-rails from end to end.
Mark gave me push access to the repo last year after some work I’ve done triaging issues and some humble contributions.
I’ve continued since then moderating some of the PRs and pruning the issues as you can see, but we always took too much time to push new releases to the community, as I had to ping you guys on twitter or GitHub issues like for the last one 3 weeks ago or today (https://twitter.com/mehlah/status/496107457006280704, https://twitter.com/mehlah/status/537300292715700225)

If you think it’s a good idea, I’ll be very happy to be able to push myself releases when needed.
Let me know ;-)

Have a nice day

Mehdi

@mehlah Hey, sorry I had sent that to Brandon the Foundation Lead after mentioning your email to him. I am assuming he did not get around to it. I will be adding you shortly. Thank you very much for your contributions! :D

Thanks @arthurzurb
:tada: guys, time to bundle update foundation-rails ;-)

This hasn't fixed 'Uncaught ReferenceError: Foundation is not defined' for me: https://codequest-poker.herokuapp.com/

@pjar Are you sure you updated the gem properly? Because looking at your application.js it seems that the JS files inclusion order is still messed up.

@ayaman my application.js looks like this:
//= require jquery
//= require jquery_ujs
//= require foundation
//= require cos
$(function() {
  $(document).foundation();
});

@pjar I just checked the link you sent again and it seems the issue is gone, so I'm guessing it was a gem version issue.

@ayaman I've resigned from foundation-rails gem and went with bower. Yet I didn't spent time on trying to figure out what was wrong, could be that I got something wrong along the way.

"Can't find variable: Foundation" again with latest release <IP_ADDRESS> :(


Required fixes

[ ] [Recipe Landing page]

Cards sizes are uneven below 600px

Recipe (main heading) - to be changed to red color and reduce font size as on original site

[ ] Product Landing Page - Left align headings for listed products  (desktop view)

@sselvara @mkbansal1 please take a look at these


Http -> HttpClient

I believe HttpClient is what we should use under Angular 4.3
Bad thing is that it affects effects, service & service.spec templates.
Also option for configurable template base path would be awesome.

you can add the following line to your package.json
{
 "ngrxGen": {
   "basePath": "./src/app", // optional - this should be relative to your root package.json file
 }
}


Npm scripts PR command and include workspaces repo

fixed the PR script. Also now does a push first to associate the branch on the remote before the PR request is lodged, hopefully avoiding user interaction
added workspace into git and version commands. Added script for setting upstream when branches become out of sync with origin

fixed the PR script. Also now does a push first to associate the branch on the remote before the PR request is lodged, hopefully avoiding user interaction
added workspace into git and version commands. Added script for setting upstream when branches become out of sync with origin

Nice one!


[Bug] daily_history model and enhanced model producing different values for the same field name

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
The main problem is that we are seeing different values for the same field (issue_type) between the jira__daily_issue_field_history table and the jira__issue_enhanced table. It appears that jira__issue_enhanced reflects the raw.jira.issue_type.name value, while daily_issue_field_history reflects the raw.jira.field_option.name value - possibly because both have the same ID.
The results of this query provide an example:
select
    i.id as issue_id
    , t.id::string AS issue_type_id
    , t.name AS issue_type_name
    , fh.value AS field_history_value
    , fo.id as field_option_id
    , fo.name AS field_option_name
    , e.issue_type_id::string AS enhanced_issue_type_id
    , e.issue_type AS enhanced_issue_type
    , d.issue_type AS daily_history_issue_type
from raw.jira.issue i
left join raw.jira.issue_type as t
    on t.id = i.issue_type
left join raw.jira.issue_field_history fh
    on fh.issue_id = i.id
left join biz.dbt.jira__issue_enhanced e
    on e.issue_id = i.id
left join biz.dbt.jira__daily_issue_field_history d
    on d.issue_id = e.issue_id
left join raw.jira.field_option fo
    on fo.id = i.issue_type
where i.id = 183458
    and fh.field_id = 'issuetype'
GROUP BY 1,2,3,4,5,6,7,8,9

Results:

ISSUE_ID
ISSUE_TYPE_ID
ISSUE_TYPE_NAME
FIELD_HISTORY_VALUE
FIELD_OPTION_ID
FIELD_OPTION_NAME
ENHANCED_ISSUE_TYPE_ID
ENHANCED_ISSUE_TYPE
DAILY_FIELD_HISTORY_ISSUE_TYPE

183458
10736
Delivery Site
10736
10736
Internal Quality Issue
10736
Delivery Site
Internal Quality Issue

According to @fivetran-avinash , this could be because Currently our data logic coalesces the field option name over the initial column name if it exists. [You can see this logic in action in Line 119 here.](https://github.com/fivetran/dbt_jira/blob/main/models/jira__daily_issue_field_history.sql#L119).
Relevant error log or model output
No response
Expected behavior
Ideally, we would be able to track both fields separately within the daily table. In other words, our end-users need to be able to filter on both Delivery Site issues and Internal Quality Issue issues separately. Also, ideally the issue_enhanced table values would match the daily_history table values for fields of the same name - right now the difference is causing some confusion.
dbt Project configurations
models:
jira:
schema: dbt
jira_source:
schema: dbt_stg
...
vars:
jira_database: raw
jira_schema: jira
jira:
issue_field_history_columns: [
'Activity'
,'Activity Date'
,'Affects versions'
,'Approved By'
,'Assignee'
,'Battery Serial Number'
,'BIS Link'
,'BIS Issue Type'
,'BIS Application'
,'BIS Root Cause'
,'Body Serial Number'
,'Cold Chain equipment type and model'
,'Complaint Source'
,'Complaint Type'
,'Components'
,'Containment Status'
,'Contributing factors during delivery'
,'Created'
,'Creation Reason'
,'Creator'
,'Critical Incident Count'
,'Current Customer Trust Level'
,'Customer Account'
,'Customer Issue Type'
,'Customer Type'
,'Customers Impacted'
,'Department'
,'Date and Time'
,'Delivery Issue Type'
,'Description'
,'Donors'
,'ECO #'
,'Epic Link'
,'Equipment Failure'
,'Equipment Status'
,'Exception Name'
,'Failure Category'
,'Failure Type'
,'Fix versions'
,'Flight ID'
,'Grounded Status'
,'Human injury caused by package'
,'Impact'
,'Impact on customer/patient'
,'Incident Timestamp'
,'Internal/External'
,'Issue Category'
,'Issue Category Label'
,'Issue Summary'
,'Issue Type'
,'Labels'
,'Location Relative to Nest'
,'Logs'
,'Loss product description'
,'LRU'
,'Make it Right Level'
,'Mission Stage'
,'Nest'
,'New Part Number'
,'Operator Report'
,'Order ID'
,'Order Types'
,'ORN'
,'OSD Checkboxes'
,'Other failure selection'
,'Package Drop location'
,'Package ID'
,'Parent Link'
,'Part Number'
,'People Reached'
,'Priority'
,'Product Risk'
,'Project'
,'Property damage caused by package'
,'Quantity'
,'Rank'
,'Released In'
,'Request participants'
,'Request Type'
,'Required Approvers'
,'Resolution'
,'Resolution Reason'
,'Resolved'
,'Root Cause'
,'Root Cause Category'
,'Root Failure'
,'Safety Performance Target Affected'
,'Satisfaction'
,'Serial Number'
,'Severity'
,'SLA'
,'Stakeholders'
,'Status Category Changed'
,'Story Points'
,'Sub-tasks'
,'Summary'
,'Supplier'
,'Time to approve normal change'
,'Time to first response'
,'Time to close after resolution'
,'Time to resolution'
,'Troubleshooting Results'
,'Unit ID'
,'Updated'
,'Viable Units'
,'Vehicle Generation'
,'Wing Serial Number'
,'Yes/No'
,'Yes/No/Unsure'
,'Zip Number'
,'Zone'
]
Package versions
packages:

package: fivetran/jira
version: 0.14.0

What database are you using dbt with?
snowflake
dbt Version
Core:

installed: 1.3.1

Additional Context
Initial convo about the issue here: https://getdbt.slack.com/archives/C01D1R2JLLA/p1693234610157279
Are you willing to open a PR to help address this issue?

[ ] Yes.
[X] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Hi @kenzie-marsh, thanks for opening this issue! I'm curious more about your expected/ideal outcome.

Ideally, we would be able to track both fields separately within the daily table. In other words, our end-users need to be able to filter on both Delivery Site issues and Internal Quality Issue issues separately. Also, ideally the issue_enhanced table values would match the daily_history table values for fields of the same name - right now the difference is causing some confusion.

If you were to have both fields/versions of the field in one model, how would you interpret them differently? Also, for the field_option version, what is the name of its corresponding field in the jira.field table? Is it also issue type?

Thanks for looking into this @fivetran-jamie!
I essentially proposed having both fields in one model as a compromise solution, because Avinash (on the Slack thread) mentioned that other customers would expect to see the field_option value. We really only need the issue_type value (Delivery Site in the example above). In fact, in the Jira UI itself, I can't find any field that reflects Internal Quality Issue on the example issue that we've been looking at, but I have an ask out to the team to see if they can show me where that field may have come from in the UI.
On the second question, I don't believe the field_option table corresponds to the field table. Based on this documentation, it sounds like it can only be joined to ISSUE and ISSUE_<FIELD>_HISTORY. I've also put some screenshots below where I attempted to check if the field table has any corresponding values, and it doesn't appear so.

Let me know if this is helpful and/or what you think. Thank you again!

Thanks for your response! It seems like we need to be treating issue_type basically the same way we treat status and components (whose values are stored in their respective source tables instead of field_option) in https://github.com/fivetran/dbt_jira/blob/main/models/jira__daily_issue_field_history.sql and potentially some intermediate models
Are there any other fields where you see this or other strange behavior? @kenzie-marsh

@fivetran-jamie that sounds right to me!
I just double checked if there are any other fields that don't match between the daily table and the issue enhanced table, and issue_type appears to be the only one.
Thank you again, please let me know if you need anything else from me!

Hi @kenzie-marsh, to update you, I have picked up this task and will aim to send you a test branch to try out in the next few days.

Hi @kenzie-marsh, I have a branch that is proving out on our end and would love to get your feedback on it. Below is the test branch to replace the regular dbt_jira package if you are able to try it out!
packages:
- git: https://github.com/fivetran/dbt_jira.git
  revision: bug/issue-type
  warn-unpinned: false

Thanks so much @fivetran-catfritz! I just tested it out with a full-refresh and got this error:
17:02:57  Finished running 18 view models, 25 table models, 6 incremental models in 0 hours 1 minutes and 57.55 seconds (117.55s).
17:02:57
17:02:57  Completed with 1 error and 0 warnings:
17:02:57
17:02:57
17:02:57  Database Error in model jira__daily_issue_field_history (models/jira__daily_issue_field_history.sql)
17:02:57    002028 (42601): SQL compilation error:
17:02:57    ambiguous column name 'DESCRIPTION'
17:02:57    compiled Code at target/run/jira/models/jira__daily_issue_field_history.sql

We do have the following in our project variables, my guess is that's causing the issue? Maybe we don't need to set this as a custom field if it's already getting included?
jira:
issue_field_history_columns: [
      ,'Description'

LMK what you think. Thank you!

@kenzie-marsh Thanks for trying this out and flagging! I also got the same error when adding in 'description'. It looks like we needed to add some logic to make sure all columns get fully qualified in certain CTEs.
I just pushed an update to the test branch that worked out on my end. Would you mind giving this another try?

That appears to have worked! Models ran successfully and I'm no longer seeing the original issue.
Thank you so much for your help!!

Hooray! Thanks again for testing it out! Hopefully this will get released in the next week but will keep you posted.

Confirming this latest release has been published to dbt hub. https://hub.getdbt.com/fivetran/jira/latest/


⚠ GitLab Server has degraded performance

In 27abc04, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 10320 ms

Resolved: GitLab Server performance has improved in 99e69ef.


DataParallel error -> RuntimeError: Caught RuntimeError in replica 0 on device 0

I am not able to use your code with multi GPU training using nn.(DataParallel) error. The code is running fine when I do -
model = torch.nn.DataParallel(model.cuda()) ----> model = model.cuda()
Have you tried using the code with DataParallel enabled?
Log snippets -
output = net(feat, coord, offset, batch, neighbor_idx)
File "/home/prem/anaconda3/envs/alpha/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
return forward_call(*input, **kwargs)
File "/home/prem/anaconda3/envs/alpha/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 168, in forward
outputs = self.parallel_apply(replicas, inputs, kwargs)
File "/home/prem/anaconda3/envs/alpha/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 178, in parallel_apply
return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
File "/home/prem/anaconda3/envs/alpha/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 86, in parallel_apply
output.reraise()
File "/home/prem/anaconda3/envs/alpha/lib/python3.7/site-packages/torch/_utils.py", line 425, in reraise
raise self.exc_type(msg)
RuntimeError: Caught RuntimeError in replica 0 on device 0.

Thanks for your interest in our work. Currently, the code only supports DDP.


[improvement](session variable)Add enable_file_cache session variable.

Proposed changes
Issue Number: close #xxx
Problem summary
Add enable_file_cache session variable, so that we can close file cache without restart BE.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

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

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.46 seconds
load time: 492 seconds
storage size:<PHONE_NUMBER>1 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230131021143_clickbench_pr_87372.html


Update @balena/jellyfish-core from 16.0.7 to 16.0.9

Change-type: patch
Signed-off-by: Josh Bowling<EMAIL_ADDRESS>

@balena-ci I self certify!


fix(STADTPULS-476): fix filter behaviour when switching tabs

WIP

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: