Can not update or change anything.  Readonly database? wtf.

SQLSTATE[HY000]: General error: 8 attempt to write a readonly database (SQL: update "user_permissions" set "solder_full" = 1, "solder_users" = 0, "mods_create" = 0, "mods_manage" = 0, "mods_delete" = 0, "updated_at" = 2015-05-22 00:01:01, "solder_keys" = 0, "solder_clients" = 0, "modpacks_create" = 0, "modpacks_manage" = 0, "modpacks_delete" = 0 where "id" = 1)
I was talking to @GenPage on irc, but it must have been late for him as he was come and go.  Need to figure out this issue.
Using sqlite.  Been all day installing this, to not be able to use it.

http://stackoverflow.com/questions/3319112/sqlite-read-only-database

Okay, so what do I need to do to set the perms?  That link doesnt help.

@MasterWolfeh, you have to chmod production.sqlite (the SQLite database). Sorry if this is old and my answer won't get noticed, but here's the solution anyway.

Navigate to your Solder Installation
While located in your Solder Installation path, go to the app folder
Go to the database folder
Run the command "chmod 600 production.sqlite" (enter it without the quotes).
Fixed!

@MetalBreaker Wrong, Not fixed.

Try chown -R youruser:www-data SolderInstallFolder/ & chmod -R 776 SolderInstallFolder/. Let me know if this helps/doesn't work.

@MasterWofleh, sorry if I was being rude and like "HERE'S MY SOLUTION! IT'S BETTER THAN ANYONE ELSE'S!!! IT WORKS 100%". Really sorry for that. Hmmm... I could set it up for you, since I already set up 3 Solder installations for my friends. I can do that on a free host, and I'll do that for you for free. If you want to discuss about it, add me on steam, MetalBreaker, the TF2 spy picture.
@TheDoctorsLife, hmmm... Interesting solution. Could you explain what the chown command does? I'll explain the chmod one:
Chmod is a terminal command used by Linux and Mac (by Unix systems). It sets the permissions of files. Possible permissions are: Read, Write, Execute, and possible user groups are: Owner, Group and Others. The -R command TheDoctorsLife posted means recursive (meaning that it will chmod the directory, along with the files in the directory, subdirectories, subdirectories of subdirectories, files of subdirectories, files of subdirectories of subdirectories etc...). I also use chmod frequently. :)

chown changes the owner, so change owner or chown, -R means it'll be recursive

@TheDoctorsLife, thanks for the explanation! I don't think people like executing commands that they don't know what they do :D  :+1:

/me looks at his perfectly running VPS & home pc, where he has run many, many untested commands.
I do make plenty of backups though, so I can afford it.

@MetalBreaker Will be sending you a friend request shortly. I have my own VPS so, that's where it will be installed.
@TheDoctorsLife I am going to attempt this method first to see if that cures the issue.

Fixed by @GenPage


quantity button change

Would it be better to have +1 +10 +100 buttons in the shops?
a lot of time you are buying hundreds of cheese, salt, etc
Or if space were an issue then maybe have a plus / minus toggle button and then 1 5 10 100 as buttons in middle and max at end?
Not sure why we would use negative buttons that much anyway?

You're absolutely right, this is a great change.


Consider using go-cmp to simplify implementation of Equals

It turns out that go-cmp slows down generation sufficiently that we don't want to use it.


FFMPEGCV cannot process grayscale videos

Describe the bug
FFMPEGCV in video-editor script cannot process grayscale videos.
To Reproduce
Steps to reproduce the behavior:

Send grayscale video to the script.
FFMPEGCV bugs out with KeyError: 'nb_frames' error on this line cap = ffmpegcv.VideoCapture(video_path).

Additional context
Using cv2.VideoCapture instead works fine. Consider switching back to cv2 for reading frames?

@akonanykhin @marcbelmont
The KeyError is resolved by upgrading ffmpegcv==0.3.8 at it was also the cause of #154
However i lack a grayscale video that could reproduce the issue. Have tried converting using ffmpeg but no KeyError.
https://stackoverflow.com/a/32385256/3320006

@danleyb2 I used this video for testing:
https://drive.google.com/file/d/1RahC8Qr9tv4D4vUQ6-cpVSjyeQbS3nMR/view?usp=sharing
It seems KeyError is indeed resolved in 0.3.8.


Datepicker issue multiple course offering

Datepicker Issue in Create Event Modal
Fixes #1333

The issue was when trying to use the datepicker to choose a date on an event with multiple offerings, the date picker would show below the modal. Initially, the assumption was the datepicker in the modal was triggering the datepicker outside of the modal. After hours of investigation, I concluded that the the correct datepicker was being displayed, but there was a z-index issue with the native datepicker module.

Changes

Disabled the default browser date picker.
Increased the z-index of the datepicker in the modal.

Testing

I verified the code works for both Chrome and Firefox, two major browsers.
I verified the responsiveness by adjusting the screen.

However, there's another issue that needs to be fixed in another ticket. The dynamically added events in the modal refer to the first event.

There are merge conflicts and causing the main page to not open properly. The initial issue also does not seem to be resolved, the datepicker is not working properly for multiple offering events. For example, if I add another event and I try to change the datpicker, it changes it for the first event always. I am not sure if this is because of the merge conflicts.

It seems like there have already been changes made to the date picker inside of multiple time offering on development since this PR was started.


Support to apply styles to node title

Thanks for awesome library!
Is there any way to apply styles to nodes title as in the below attached image? We can append text to node and format the string but no styles?
node.append("text").text(()=>{return "string"})

@mbostock @Fil @jfsiii @mbostock @jasondavies

@CaptSadaf you can attach a div based on your current mouse pointer position using .on('mouseover', () => { /* append div with custom html with styles */})


Sampler object support

Feature request
One very useful feature we are missing is sampler objects. It's so much easier to control texture parameters and they are also pretty much required for gltf scenes.
I might take a stab at this some time in the future. It's really just an object you bind with glBindSampler(location, sampler_id), so it might not even need to include any C code at all.
glSamplerParameter*, MAX_TEXTURE_MAX_ANISOTROPY, TEXTURE_MAX_ANISOTROPY are on the short list of fuctions/attribs needed.
Possible Implementation

Sampler python class storing each sampler parameter
sampler = Context.sampler(<sampler parameter) -> Sampler
sampler.use(location=0)

Wost case this approach can always be changed to a version with C code in the future without breaking compatibility. Might not be a good idea to expose glSamplerParameter* on the python side.
If this sounds like a good idea, I can jump on pretty fast.
(sampler object is GL 3.2+)
Version info
5.2.1

Been playing around with samplers a bit locally. There was actually one case I had to use samplers to read the depth texture with sampler2D because the Context.depth_texture function is currently hard coding in texture compare mode.

are you sure? the compare function was added earlier. not sure when

As far as I know, you can't change GL_TEXTURE_COMPARE_MODE, so It doesn't matter if you can  change GL_TEXTURE_COMPARE_FUNC.

MGLTexture_set_compare_func could for example be set to None to disable it.
Optionally a separate MGLTexture_set_compare_mode with a boolean parameter setting GL_COMPARE_REF_TO_TEXTURE if True and GL_NONE if False.

exposing GL_TEXTURE_COMPARE_MODE is a good idea.
I would go with the first suggestion. Will all the valid settings be covered?

@einarf I think we could try to add Sampler object support in the next release. If this requires too much time then we will postpone it. What do you think? How can I help?

I'll see what I can do today. It's the last remaining feature that requires me to use PyOpenGL, so the motivation is definitely there.

As a side note: I see a lot of missing entries exposing getters/setters for things like max_samples, max_integer_samples, max_texture_units, default_texture_unit. I was adding a max_anisotropy attribute and got a bit confused. All these missing attributes are also in the docs, so I assume they need to be added. I can fix that in my PR as well while I'm at it.
https://github.com/cprogrammer1994/ModernGL/blob/c67149a53cfde14e0a045d9f8d05c7952fee12b0/src/Context.cpp#L1212-L1230

merged #215


Remove the action 'Attach Database Account…' under Attached Database Accounts

Repro steps:

Make sure there is no attached account.
Expand 'Attached Database Accounts' node.

Expect:
Remove the action 'Attach Database Account...' because there are two actions on the attached context menu.
Actual:
Display an extra action 'Attach Database Account...' under 'Attached Database Accounts' node.

Closing as this "bydesign".  We think that the user could be confused when expanding the Attached Database Accounts tree item and not seeing anything under it.  Even though it's in the context menu, it's nice to have it in the tree view for extra discoverability 😃


Improvements and additions to Swift SIL infrastructure

This PR contains a whole set of swift SIL infrastructure additions and improvements.
For details see the commit list.
This is in preparation for a new optimization to optimize ObjectiveC bridging

@swift-ci smoke test


Add capitalization settings support for useTextField

Closes https://github.com/adobe/react-spectrum/issues/4832
For now, I've implemented this only for textField. As mentioned in the issue comments, if this implementation seems fine, I'm thinking of extending it to others as well.

Seems like a reasonable addition to me. I think if we do this, we should also make this apply to other input fields as well (SearchField, Combobox, SearchAutocomplete, etc.)

✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[x] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[x] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

📝 Test Instructions:
To test this pull request, please provide the autoCapitalize prop in the useTextField storybook and observe its reflection in the attribute. For comprehensive testing, it is recommended to try this on iOS Safari to confirm the behavior aligns with expectations.
🧢 Your Project:

I hope you don't mind me adding an extra story for easier testing. Otherwise, thanks for the PR!

GET_BUILD

I wanted to share that I've submitted a correction to MDN, and it has been successfully merged.
https://github.com/mdn/content/pull/30645.


Fix typos in doc/code comments (tem->item, etc)

Mind dropping the changes to crc32c.c? that's an upstream files and that just makes merge conflicts if I ever need to update it again :) Rest look good.

Mind dropping the changes to crc32c.c? that's an upstream files and that just makes merge conflicts if I ever need to update it again :) Rest look good.

Done


Add new post-processing stages

🚧 Work in progress 🚧
Addresses https://github.com/appleseedhq/blenderseed/issues/523

For what it's worth your patch looks good so far.


hotfix/WIFI-964: Fixed alignment of Radio Columns on AP Status page

JIRA: WIFI-964
Description
Summary of this PR
Fixed the alignment of Radio Columns on AP Status Page when values are missing. Used a grid layout instead of a flex layout.
Before this PR
Screenshots of what it looked like before this PR

After this PR
Screenshots of what it will look like after this PR

Undo the styling changes you made, and make it display "N/A" for the missing values instead


[cleanup][functions] Fix some javadoc issues

Motivation
cleanup
Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
cleanup

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

/pulsarbot rerun-failure-checks


Dataset

please where can i find the dataset for this program

https://salient360.ls2n.fr/datasets/training-dataset/

i keep getting pop ups to sign i with username and password to download the
dataset. i send an image of the message i get.
On Tue, 7 Apr 2020 at 19:25, Tejo<EMAIL_ADDRESS>wrote:

https://salient360.ls2n.fr/datasets/training-dataset/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/V-Sense/salnet360/issues/3#issuecomment-610331390,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALBFLFCLCLOJVAPXQDRSY7TRLMETLANCNFSM4MC4HXTA
.


Quiz App using Dart and Flutter Framework

An Quiz app for asking Question and after that Gives an remark

@ASVKVINAYAK Please see my PR


Testing commands

Pyrogram describes using the Test servers to test the application. It should speed up the development process if implemented successfully.

Well, yes. Testing is crucial, and I desire to create automated tests for all the modules within the bot.
However, I haven't focused on tests, mainly due to the other higher priority things, such as the Locale and Database module.
Once the API for these modules is somewhat stable, I will be able to get working with tests.


Player not working with yutube music

I tried using cleartext with youtube music. I have installed both the browser extension and the plugin, but the player doesn't seem to work.

I am having the same problems with youtube. One of the things I am seeing in the Rainmeter logs is:
"Unable to locate GPMDP settings file, you will need to use an authenication skin to get playback controls and custom theme colors will be unsupported"
Using rainmeter <IP_ADDRESS>01 beta 64bit, and Cleartext 6.0
I think the WebNowPlaying plugin doesn't cooperate well with Brave Browser (as compared to Chrome and etc.)

Yeah, I'm having the same problem on Edge (chromium version).

Having the same issue on Chrome


feat: support originalFilename

Description
Adds support for originalFilename feature that is added by https://github.com/rollup/rollup/pull/5596.

@sapphi-red What do you think about releasing this in a patch? We're unlikely to cut a minor now as we're starting the major beta pretty soon. This PR seems safe enough though

I think we can release this in a patch as this PR isn't so big.

Definitely need this. It might as well be the answer to people asking for an assetsFlatten : false option (https://github.com/vitejs/vite/pull/17626)
Having the originalFilename feature allow to easily preserve some folder structure if needed.

Any idea when this will be published as part of 5.4.2 release?


Custom snapshot console colors (A11Y)

Clear and concise description of the problem

Colors work differently in different editors/consoles/terminals/shells/CI's/etc.
Some people have different visual, or cognitive impairments that make certain color combinations frustrating or difficult to discern.

Suggested solution
The default red/green approach is fine by me, and probably good for the majority of users. But it would be nice if there was a vite.config.js option for customizing the colors used by Vitest, particularly in snapshot failures.
import chalk from 'chalk';
import { defineConfig } from 'vite';

export default defineConfig({
  test: {
    diff: {
      // I'm not sure what the API would look like here, So I'll just use what
      // jest-diff documents for this example. The following is copied directly from
      // https://github.com/facebook/jest/tree/main/packages/jest-diff#options
      aAnnotation: 'Expected',
      aColor: chalk.green,
      aIndicator: '-',
      bAnnotation: 'Received',
      bColor: chalk.red,
      bIndicator: '+',
      changeColor: chalk.inverse,
      changeLineTrailingSpaceColor: string => string,
      commonColor: chalk.dim,
      commonIndicator: ' ',
      commonLineTrailingSpaceColor: string => string,
      compareKeys: undefined,
      contextLines: 5,
      emptyFirstOrLastLinePlaceholder: '',
      expand: true,
      includeChangeCounts: false,
      omitAnnotationLines: false,
      patchColor: chalk.yellow
    }
  }
});

By exposing all options, it empowers communities to create their own commonly recommended settings, like so:
import { defineConfig } from 'vite';
import diff from 'vitest-deuteranopia-diffs';

export default defineConfig({ test: { diff } });

import { defineConfig } from 'vite';
import diff from 'vitest-cognitive-diffs';

export default defineConfig({ test: { diff } });

import { defineConfig } from 'vite';
import diff from 'vitest-win-cmd-diffs';

export default defineConfig({ test: { diff } });

etc.
There could even be an awesome-vitest-diffs repo with screenshots of each library, so users can more easily choose what works best for them or their teams. This could all be community-lead, but we need Vitest to allow for this.
Alternative
No response
Additional context
This same feature request was submitted to Jest, and approved for PR.

https://github.com/facebook/jest/issues/12576

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Yes, I'd really appreciate this. I find it hard to read red text on a black background and would love to be able to use a slightly different colour.

Yes please!

We now use the same diff method that jest uses, so it should be possible to reuse the same config. PRs to implement this are welcome. Please, note that the new option should be a string that references a module with a default export containing this config.
It should be loaded inside a test context and passed down to the diff method.


"Not in your wallet", "revoked" and other error text isn't read with voiceover on

Description of problem
With VoiceOver or Taslkaback on and when receiving a proof request asking for credentials a person does not have, or revoked credentials, or credentials that not meet requirements, the "not in your wallet", "revoked", and "requirements not met" text does not get read.
Expected behavior

The error text when a proof request does not have the necessary credentials/attributes should be read outload when Talkback or VoiceOver is enabled

Steps to reproduce

Turn on voiceover
Receive a proof request asking for credentials a person does not have, or revoked credentials, or requirements aren't met
tap on card to read the content with voiceover

Screenshots and/or log output
Environment

[X] Occurs on Android
[X] Occurs on iOS

Build #: 1527
Android Device Model: Google pixel 8
iOS Device Model: iPhone 12
Workaround
none
Severity

[ ] High
[X] Medium
[ ] Low

estimated at 3.


CU-a4hkh6_Set-up-Mixpanel-to-learn-more-about-user-behavior_Spencer-Lyon

WIP: starting mixpanel metrics

Task linked: CU-a4hkh6 Set up Mixpanel to learn more about user behavior


New release required as master is ahead of latest 0.2.0 release

What happened?
Running Ansible role fails when set to the latest release, in this case 0.2.0. Running without specified versions or with 'master' is successful, as new commits in master fix this. New release needs to be published to the repo, in order to reflect changes, e.g. 0.3.0.
Did you expect to see some different?
Playbook finishing.
How to reproduce it (as minimally and precisely as possible):
Running latest release, e.g.
  - name: process_exporter
    src: https://github.com/cloudalchemy/ansible-process_exporter.git
    version: 0.2.0

Environment

Role version:

0.2.0

Ansible version information:

ansible [core 2.11.0]
  config file = None
  configured module search path = ['/Users/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/homebrew/Cellar/ansible/4.0.0/libexec/lib/python3.9/site-packages/ansible
  ansible collection location = /Users/user/.ansible/collections:/usr/share/ansible/collections
  executable location = /opt/homebrew/bin/ansible
  python version = 3.9.5 (default, May  3 2021, 19:12:05) [Clang 12.0.5 (clang-1<IP_ADDRESS>)]
  jinja version = 3.0.1
  libyaml = True

Ansible playbook execution Logs:

TASK [process_exporter : Get checksum list from github] ************************************************************************************************************************************************************
task path: /Users/user/.ansible/roles/process_exporter/tasks/preflight.yml:43
fatal: [ec2-ip.regioncompute.amazonaws.com]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'url'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Received HTTP error for https://github.com/ncabatoff/process-exporter/releases/download/v0.7.5/process-exporter_0.7.5_checksums.txt : HTTP Error 404: Not Found"}

This role has been deprecated in favor of a the prometheus-community/ansible collection.


Syncer logs errors while trying to sync p-cluster only resources to KCP

Describe the bug
If a resource exists in the physical cluster but not in KCP, the syncer will try to sync it to KCP and log an error that it can't find a corresponding KCP resource. It should instead ignore all resources for which it is not responsible.
To Reproduce
Steps to reproduce the behavior:

Install a workload cluster
Observe periodic error messages in the syncer pod as it tries to find and update non-existent resources in KCP based resources that exist only locally.

Expected behavior
The syncer skips p-cluster only resources.

It might be fixed by the upcoming PR https://github.com/kcp-dev/kcp/pull/942.

/transfer-issue contrib-tmc


Input validation in forms

Check is date formats are correct, if not try to recover and display suggestions nonetheless.

ed0c93dfb6cf33bb518b0d9b0c69892112226059


Extend By Size tooltip

when editing disk you can extend the size by xyz GB. That's all good, but people may not realize it doesn't resize the filesystem. It would be great to have a tooltip explaining that after the resize you are responsible to grow the filesystem inside the guest.

@lwrigh @sjd78 @bond95 What do you think the text is supposed to be?

@lwrigh  Where do you think the tooltip should be?(ignore the text content, its for demonstration)

And is it right for it to be also in the creation window? I think that letting the user know he supposed to do it later on, its important as well.

@michalskrivanek ?

For the "Edit Disk" modal, we can add an info tip next to the "Extend Size By" label and the info tip text could say, "You can extend the size of the disk but it does not resize the filesystem. After resizing the disk you must expand the file system inside the guest separately." @michalskrivanek Does that sound accurate?

@michalskrivanek @lwrigh @yodem
(1) Why we need this tool-tip added in vm portal and not in webadmin as well?
(2) Will the VM portal's user know how to expand the file system? I would add to the tool-tip something like: "...you will probably need to use the fdisk utility for resizing the partitions and file systems as required. Please refer your administrator for more information on how to do that."

@lwrigh @sjd78 @bond95
#846 Can I combine these two issues in the same PR?
Please see https://github.com/oVirt/ovirt-web-ui/issues/846#issuecomment-522634332

Yotam, your text lgtm

@lwrigh - To be consistent with the rest of the dialog, shouldn't the new text be a Field Level help (the circle-i icon) next to the "Extend Size by" field?  That way it'll match the storage domain and disk type fields.

@sjd78 Yup that sounds good to me so it matches storage domain and disk type.


Issue v3.1.6 when compiling after update from 2.3.6

I just decided to update the nuget from the app after everything worked fine with both Android and iOS.
The issue is that when I tried to compile with new version 3.1.6. it crashed my app. The error said that Firebase was not initialized at the moment of calling "FirebasePushNotificationManager.Initialize(this,true);" or directly subscribing the app to a topic.
I tried deleting Bin and Obj from all my project folders, so it worked once for me. but this time , this solution didn´t work.
I tried initializing Firebase via : FirebaseApp.initializeApp(this); but neither it worked.
The only solution was to downgrade again to 2.3.6 because the app is in "production".
Version Number of Plugin: 3.1.6
Device Tested On: Xiaomi mi 9t
Simulator Tested On: iOS Simulator
Version of VS: 8.3.11

I have the same issue, Any support?

I have the exact same issue.

See https://github.com/CrossGeeks/FirebasePushNotificationPlugin/issues/284.

See #284.

It worked for me as well, thank you.


Initial Switch From Travis CI to GitHub Actions

All CI(test automation) has been swtiched to use GitHub Actions instead
of Travis CI. The CD automation will be converted in the near future.
First part of #4

All the CI checks are working. I'll do a separate PR to convert the CD automation to use GH actions.


Support multi zerotier networks

Also drop dependency on external script

Codecov Report

Merging #157 into 1.1.0-alpha will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           1.1.0-alpha     #157   +/-   ##
============================================
  Coverage        16.73%   16.73%
============================================
  Files               15       15
  Lines             1034     1034
============================================
  Hits               173      173
  Misses             850      850
  Partials            11       11

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 e8ab1b9...26de338. Read the comment docs.


Test in a new scene

Hello, I want to know whether the pre-trained model can be used to estimate the absolute depth map in a new scene, such as inputting an rgb image or a video sequence. If so, how can the scale information of multiple depth maps estimated by the pre-trained model be obtained? I want to splice multiple depth maps into a point cloud, as your video demo shows.  Do you have any suggestions? I would appreciate it very much.

Hi @JOP-Lee. All predictions made by our evaluation pipeline are in metric scale. Metric scale is recovered through matched features in the overlapping regions of the calibrated multi-camera system (see Sec. 3.2. in the paper). Furthermore, the prior of the completion network is also in metric scale because it was trained with metric scale poses resulting from the former. Thus, you can combine the resulting depth maps into a point cloud as follows ...

Run evaluate.py and save the predicted depth maps and poses
Unproject depth maps by using the respective camera intrinsics
Transform points from the camera reference frame to the world reference frame with the estimated poses
(Optional) Filter outliers

@AronDiSc
Thank you for your response. Can you provide a script for testing a single image or multiple camera new scenes? It seems that evaluate.py is used for evaluating the DDAD and nuScenes datasets, and it requires masks and poses. However, for beginners testing new scenes, it would be very convenient to synthesize depth maps from single images (similar to monodepth2).


Add anchor in place of

Articles generated by Hugo miss anchor to scroll to the place of the article where summary ends.
Use-case: I read article on the main page, click lint to read more.
I expect to continue reading from the place where summary ended.
But instead article is opened from the beginning.
I'm thinking about fixing this by generating html in place of  tag

The name is yet to discuss. It could be _cut , _readmore, or something like that.
Then in index page it'll be
Read More…
Or it can even be a new variable {{ .ReadMoreLink }}.
I'd be willing to implement, but at first, what do you think of that feature?

I think this should be solved by adding a ContentAfterSummary field on Page. There is a issue about that somewhere -- there was even a PR at some point, but it never finished. After my latest summary refactorings, such a field should be trivial to add.
Please shout if there are issues here I'm not getting, but in my head this is a template responsibility, son in single.html:
{{ .Summary }}

{{.ContentAfterSummary }}

This issue has been automatically marked as stale because it has not been commented on for at least four months.
The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still valuable, please open a proposal at https://discuss.gohugo.io/.
This issue will automatically be closed in four months if no further activity occurs. Thank you for all your contributions.

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.
If this is a bug and you can still reproduce this error on the latest release or the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.


Prevent overwriting of function default arguments object

This will allow you to use strict-mode without problems.

Running strict mode globally in Node is strongly discouraged except for testing purposes, but sure yeah patch LGTM

what @yoshuawuyts said

1.3.5


Flow "forgets" results of checks for existence of property

You can reproduce it here
Expected result: no flow errors in the snippet.

Looks like a regression in v38. Works in 37.4.

This is expected behaviour. Calling functions invalidates refinements

@vkurchatkin thanks for your response!
But shouldn't flow know that call to querySelector will not change document.head in the example above? It's standard DOM API.

"What if someone will change native api".
Well, I get your point, thanks.
From another hand, what if someone will replace Math.floor, for example, so it will return a string?
Should we add checks everywhere that the result of Math.floor is a number?

It's up the the library interface to define if it's nullable. In this case, document.head has been defined as nullable: https://github.com/facebook/flow/blob/master/lib/dom.js#L628 & Math.floor has not: https://github.com/facebook/flow/blob/master/lib/core.js#L159.
You're right that there is a balance to strike for interface files (as to whether methods / properties should be marked as potentially nullable), but it seems weird to special case refinements just for library interfaces because they are "mostly stable".

That would require flow to enforce typing all side effects.

Can't we mark functions as without side effects somehow?

Can't we mark functions as without side effects somehow?

Ideally, yes. There is an open issue for this somewhere

#2715
Thanks for the discussion, guys!


Ability to reinit GitFlow on demand

Hello,
Could you please tell how can I reinit GitFlow?
On first run I was able to use Init dialog to setup branches and prefixes?
For now, structure and prefixes are subject to change. However, I cannot reinit extension.
Remove / reinstall does not help.
Thanks,
Vlad

In the .git folder the file "config" (text content) contains all the information from the Init GitFlow dialog (gitflow prefix). It can be changed.

Busy adding a new menu options to trigger the UI again for easy editing!

Grab the new release! 🚀


Support for Xcode16

Hello everyone!
Problem
In my project, one of my dependencies is the pod LyraPaymentSDK, which depends on this project. I recently upgraded my Xcode to Xcode 16 and found out that I couldn't build iOS apps anymore.
This is because of this issue : Sentry below v3.33.0 doesn't work with Xcode 16 😢
So I would need the dependency to Sentry to be bumped, so that the pod LyraPaymentSDK can then be updated too
what I did in this PR

Bumped Sentry to 3.36.0 (3.33.0 would fill my needs but I took the last existing version)
Updated the pod's version to 4.0.2

points of attention

I'm not sure I could properly test the behavior with this new version of Sentry, please be careful while reviewing or indicate some steps to test this
I didn't update any changelog, I don't know what are your standards here, but I would gladly do it if you provide some more info

Don't hesitate to give me some feedback if you see something I missed, or handle this bump in an other branch and close this PR if it's easier for you 😁
Closes https://github.com/lyra/sentry-client-cocoa/issues/1

I see that the bump done on the last version, so I'll close this PR
Thanks for the quick update!


Have ng g c [name] generate inline-template and inline-style automatically from config

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [X] feature request

Versions.

master
Repro steps.

ng new delete-me-quickly
cd delete-me-quickly/src/app
ng g c hello
cd hello && ls
Contains html and css files, instead of them being inline.
The log given by the failure.

Desired functionality.

If the functionality is specified in ng new using -is or -it, a respective setting should be saved in .angular-cli.json and stick in generation of new Components and/or Directives.
Mention any other details that might be useful.

I came up with it during research I'm doing for #6480, where I'm updating the documentation for ng new.
I would like to further contribute by adding this feature myself and PRing it. Would that be acceptable? Is this feature even discussed? I would very much like to contribute in the cli, especially something that is more code than docs.
EDIT
After additional research, I did find that .angular-cli.json has such configuration, as specified here:
    /* blueprints/component/index.ts */
    options.inlineStyle = options.inlineStyle !== undefined ?
      options.inlineStyle : CliConfig.getValue('defaults.component.inlineStyle');

    options.inlineTemplate = options.inlineTemplate !== undefined ?
      options.inlineTemplate : CliConfig.getValue('defaults.component.inlineTemplate');

But it is not set during ng new.

@Brocco WDYT?

@filipesilva @Brocco It's good option to have on the other side I think it should be on the component also as when creating small components which only are containers or have few lines would like to have those inline.

@sumitarora what you're talking about exists. My thought process behind this change is that if someone specifies in lines on new, I believe they want it for the entire app. If someone wants a particular component with inlines, the g c command accepts inlines already, and they are given priority over defaults, as you can see in the snippet above

To understand, you wish to make the change that when a user creates an app using --inline-template or --inline-style that the setting be persisted to .angular-cli.json for future generations for that app?
Current state, just the app component will get inlined, no setting saved to .angular-cli.json
Proposed: set the inline flag(s) when used during ng new
Issue: What if the dev wants to only inline their app component as it typically is very light but not all subsequent components?
Suggestion: Add new flags to clearly state the desire to have all components inlined...
--inline-style-all (-isa)
--inline-template-all (-ita)

The result of using these flags would be to set it for the current run and set the value in angular-cli.json
Thoughts?

@Brocco I like the suggestion. Also I think that the existing flags documentation should be updated to explain they only cause AppComponent to be inline.

@filipesilva @sumitarora @Brocco So it's agreed that -all is the right way to go? Can I go on and implement? Implementation would be an update to my existing PR #6571

@Brocco, @gioragutt I just gave some thoughts and in my opinion a good "logic" soluton would be:
1- When creating a new project, a setting wiil be saved to .angular-cli.jsony
2- This setting can be changed anytime by the dev in ng set defaults.inline="true/false"
3- when the dev generates a component, pipe, etc.. the cli will generate according to the defaults inline unless he specifies otherwisse with the current "-is" flag  or with one new flag to be created "-nis" no inline.
4- If the dev specifies the "-is" or "-nis" this configuration will override the defaults but only for this component/pipe, etc.
What do you think?

@ampgular this is how it works today.  Except that it just doesn't save it in .angular-cli.json, which is what my PR changes. You can see in the generate command, that it checks both the setting in .angular-cli.json, and the setting from the command line arguments given in the command, giving priority to the command line argument setting.

+1


⚠ ClamAV has degraded performance

In e625ae6, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 70 ms

Resolved: ClamAV performance has improved in c397835.


pango: fix building on darwin

Motivation for this change
#102020
Run-time dependency freetype2 found: YES 23.4.17
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency xft found: NO (tried pkgconfig and framework)
meson.build:352:0: ERROR: Dependency "xft" not found, tried pkgconfig and framework
A full log can be found at /private/var/folders/r4/k85s52jx3555ckj0wty615s00000gp/T/nix-build-pango-1.47.0.drv-0/pango-1.47.0/build/meson-logs/meson-log.txt

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

LGTM, xft is a feature option and from the description I assume that it only works with X11 anyway, so disabling it makes sense.

It should be disabled on auto but that somehow broke on the last update.

It should be disabled on auto (the default value) but that somehow broke on the last update I think.

IMO that would be strange, it should be enabled by default. At least on Linux we use -Dauto_features=enabled for quite some time now (enables all features, previously we disabled them by default). But I'm not sure if we have any Darwin hacks for this.

Apparently the breakage happened as the result of GNOME/pango@8485a34055837fe2b8f58814c0bd3c25f97d610b

Hope ofborg evals no rebuilds for linux.


Variable arguments

Variable arguments could be implemented as a special kind of wildcard that substitutes instructions of the same name.

Check if the function signature contains a variable.
Push the value to a variable stack in a tuple (name, value).
If a variable exists on the variable stack with same name, check for equality in value, fail pattern matching if they are not equal.
When pushing instructions, substitute variable names with the value from the variable stack.

This requires an additional stack for variables to be synchronized with the call stack.

One problem is that a variable can in theory match against a path, which propagates the property to the expression of the variables. For example, if adding an item to a list increases by the length by 1, then adding all items from a list of M items increases the length of the list by M. Computing with [len] [:] X in a loop will give the same result as if the function had a path to [len] [:].
So, variables could in principle match against all instructions until the next path, but if a function has declared a path it needs to be put before the variable to ever be matched against.

The problem with matching against a path seems to be solvable by sorting functions such that variables are put last.

An alternative to synchronize a variable stack with the call stack is to push all instructions temporarily to a stack. This might not be viable for nested calls.


Page redirected to the same page

@Abhijit2505 From SWOC2021, As I was visiting the webpage I found we do not have programs for 1> Mathematic problems, 2>Hashmap and 3> OOP design.
I want to work on these topics. If we can discuss, do let me know how can I get going to add interesting program for above mentioned topics

Well, we know we have no problems on these sections, if you want to add problems, please make an issue stating the problems.
Don't create an issue setting a department of problems like Hashmap or OOP Designing.

Well, we know we have no problems on these sections, if you want to add problems, please make an issue stating the problems.
Don't create an issue setting a department of problems like Hashmap or OOP Designing.


Negative inline-margin for .row can be a problem

The-flex-grid is awesome, I use it all the time.
The negative inline-margin for .row is bugging me often though. For example when using a background color for the row, it extends it's container.
The connected inline padding for the .col-x has it's drawbacks as well with regard to background color.
I think a flexbox grid should use column-gap for spacing between columns, although I'm not sure how the flex-basis for the different column widths should be set.

Hi Esger, thanks for your request! And also great to hear that you are using it! I agree that we might be able to solve this easier nowadays. I'll pick this up in the next few weeks since this is still a side project for me.


[Suggestion] Categories

It would be nice to have "virtual" categories, like:
modpack
├── mods
│   ├── api
│   │   ├── .index.toml
│   │   └── fabric-api.toml
│   └── client
│       ├── .index.toml
│       └── modmenu.toml
├── index.toml
└── pack.toml

And something like categories = ["mods/api", "mods/client"] or with [[categories]] in index. With only [[files]] allowed in .index.toml or recursive indexes without hash-format.
And handle [[files]] from category index like they in parent of category dir
Just for convenient mods organization
Will need installer changes too
// no one in their right mind will set mod id to .index, right? But potentially possible

Also a little offtopic: is Rust port still in plans?

I had a few existing ideas for this, curious to see what you think:

A .htaccess-like file that, when placed in a directory, configures default settings for files in that folder (including being able to specify that the whole folder should be installed in the parent directory)
Something similar to the .htaccess file, but specified entirely in the pack file (so no extra files are needed)
Pack dependencies, so you can import another pack.toml (as a local or remote file) so that all it's contents become those of your pack - and letting you override them where necessary. Might be a bit annoying to cd into the folder if you're installing mods for categories (unless I add a way of referencing a dependency when installing a mod?) but would be somewhat more flexible.

I'll probably make the index always top-level; since I want to make it only necessary for serving with HTTP and ignored by default in git repos. All the other metadata that index.toml stores will be moved elsewhere (requiring a specific file extension for metadata files).
Regarding the Rust port: I'm not sure at this point, as it will require a fair time investment. However I have some ideas to refactor packwiz CLI internally, which might make sense to do at the same time as rewriting in Rust anyway.

I would say 1st now and 3rd maybe later. Dependencies for categories it's overkill
Splitting client / server / both for different packs it's also mod deps duplication, or even conflicts. Same for optional mods separation (expected '.htaccess' feature, I suppose)
But with '.htaccess' there need to be cli way to deal deps duplicate for different dirs. Example - installing mod in 'server' dir with dep, that already installed in 'client'. As a cross-dependency flag in '.htaccess' which true by default and error with suggestion to move that dep(s)


Houdini: Enhance ABC publishing

Add automatic path attribute on creation, automatic output node connection.

If s@path  attribute does not exist, or not present on all primitives, generate automatic path where missing (on creation) - auto path would be constructed like this: {parent_node_name}/{output_node_name} (this behavior will have to be a bit more refined in the future)
if Output_SOP connector does not exist, create one, connecting it to the node with render flag on, and display it (display flag on).

[cuID:OP-1798]

If s@path attribute does not exist, or not present on all primitives, generate automatic path where missing (on creation) - auto path would be constructed like this: {parent_node_name}/{output_node_name} (this behavior will have to be a bit more refined in the future)

Would this be a Validator that adds in the extra nodes in Repair? Or when would this occur?

if Output_SOP connector does not exist, create one, connecting it to the node with render flag on, and display it (display flag on).

Could you elaborate slightly more about why this is needed?

Would this be a Validator that adds in the extra nodes in Repair? Or when would this occur?

Yeah, I think Repair action si the right place for it.

Could you elaborate slightly more about why this is needed?

This is currently required by validators (so again, it would be probably Repair action). I think Output is good to have to bring some order into what's going out - at least visually.

@BigRoy  @moonyuet
Can move the discussion here about the details of Houdini point cache enhancement ?
I'm sorry I should have done that earlier.
Here are the details I can think of :
this code related to these files

houdini\plugins\create\create_pointcache.py
houdini\plugins\publish\validate_primitive_hierarchy_paths.py
houdini\plugins\publish\validate_sop_output_node.py

Current behavior

on creation: it will set sop_path parm of the abc ROP to selection whether it's an ObjNode or SopNode
if selection is SopNode

sop_path will be set to a SopNode path
on publishing: if no path attribute (path_attrib of the abc ROP to be specific ), these validators will log.error

validate_abc_primitive_to_detail.py
validate_primitive_hierarchy_paths.py

if selection is ObjNode and it has a child of type "output"

sop_path will be set to that "output" sop node path which yields to the previous case

if selection is ObjNode

sop_path will be set to an ObjNode path
on publishing: these validators will raise this error  AttributeError: 'ObjNode' object has no attribute 'geometry'

validate_abc_primitive_to_detail.py
validate_primitive_hierarchy_paths.py

After applying quick fix (checking not hasattr(output_node, "geometry"))
on publishing: validate_sop_output_node.py will log.error

"Output node %s is not a SOP node. "
Note that it doesn't force a specific SOP node type

Desired behavior

Disclaimer: I personally don't know what could deliver a better user experience for artists, and I will appreciate any recommendations

on creation:
if selection is SopNode
- if it's not a node of type "output", an output node will be created and set its input to the selected node
- on publishing: if no path attribute (path_attrib of the abc ROP to be specific )
- a repair action on  validate_primitive_hierarchy_paths.py will
- create a name node with the same attribute as path_attrib in ROP
- add a default value {parent_node_name}/{output_node_name} or  {parent_node_name}/{name_node_name}
- it can be connected before or after the assigned node in sop_path, it depends on the node whether it's of type "output" or any other type.
- ANY RECOMMENDATIONS
if selection is ObjNode and it has a child of type "output"

sop_path will be set to that "output" sop node path which yields to the previous case

if selection is ObjNode

sop_path will be set to an ObjNode path
Assuming I made the quick fix mentioned above
on publishing: validate_sop_output_node.py will log.error
- a repair action to fix it, which will set the sop_path of the ROP to the selected node (which is a general solution for all cases)
- which yields to the first case

conclusion
See things from this perspective, I can understand why a sop "output" node is not a mandatory.
Connecting the name node before won't be a good thing if the node in sop_path is a multi-input node like "merge" node
if it's a sop "output" node, then the name node must be connected before it
Using the 'output' sop-node and attaching the name-node before it satisfies the problem description above, which is what I was originally trying to achieve.
Let me know what do you think ?

For desired behavior:
Other than sopNode, it will be great to also include dopNode for selection although user usually cache as bgeo and use file cache to get the related bgeo into SOP level to do the alembic export. Adding dopNode for selection just in case that users may want to export the alembic within the DOP network.  You can read this reddit post: https://www.reddit.com/r/Houdini/comments/f6oefh/i_have_a_simple_dop_simulation_that_i_want_to/
It can show that you can do alembic export for the DOP network.
Some comments on Output Node
Not quite sure about the standard workflow but I personally dont use output nodes except for rendering. Usually I use null nodes at the end of all creation. If the purpose of the point cache are to export and do comparison between several same objects with different fracturing levels, it is okay to create output node and hook it into the node..(but you can preview these fracturing objects quickly with exploded view node for sure)
Path Attribute Repair Action
As more I look at the issue (and PR), more questions come in my mind regarding to repair action(It can be that I overthink too). As mentioned in the PR, the path attributes can be created with different attribute-related nodes. Not only attribute-create node shown in the PR, you can create path attributes with string data by connectivity node.

Many options can be choosed for storing the attributes data in Houdini, meaning that the nodes and the parameter which links to the string datacan be varied. E.g. The relative reference of parm is chs("prefix") for connectivity, while chs("string1") in attribute create and   chs("name1") in the name attribute.
In more complicated case, I am not sure if users use attribute promote (promoting point to primitive etc.) too. The repair action is only helpful for the occassion when there is no path attribute in the scene.
By this, it may be better idea to have one invalid options to show the user doesn't include string data in the path attribute, recommend what to use for the string data: i.e. 'opname("..")/opoutput(".", 0)'

As far as I understood, Here are the suggested edits:

houdini\plugins\create\create_pointcache.py
It's better to leave it as it was, plus we may do this

if selection is ObjNode , if output node wasn't present, the node with the active display flag will be used

houdini\plugins\publish\validate_primitive_hierarchy_paths.py
adding a repair action to add a node with a default path value

node name AUTO_PATH
there are 4 possibilities: name, attribute create, connectivity, vex wrangle
connectivity is better as it will increment prefix and all connected primitives will share the same number

attribute value
opname('..')/opname('..')Shape_

node comment
something similar to this, so that it will be clear for artists
  auto path node created automatically by repair action
  Feel free to modify or replace it.

node connection
connect before if the output sop node of type output or null
connect afterwards for other types, set sop_path to it

houdini\plugins\publish\validate_sop_output_node.py
adding a repair action to set sop_path to the selected node

if SopNode is selected, set its path to sop_path
if ObjNode is selected, follow same logic as create_pointcache

applying quick fix (checking not hasattr(output_node, "geometry"))

validate_abc_primitive_to_detail.py
validate_primitive_hierarchy_paths.py

Regarding including dopNode
I think it can be possible during the creation process
if selected is dopNode then I would do this:

create a new geo node
create dop import
create unpack node
use unpack  instead of the selected node, continue default execution flow

Creator
I agree that we should leave it as it is for current stage.
Validator
For validate_primitive_hierarchy_paths.py, there is repair action for sure but there are more than four possibilities to create primitive attribute. So we need to do accurate and more general checks on it.
If there is no primitive attribute named path in the network, it wont pass the validation. Rather than doing a check on just four certain nodes.
Repair action can't repair anything as the relative references of parameters to store attribute values vary from node to nodes.
But still it needs to be inside the validator for creating a new name node for storing the path attribute and connects to the node if the selected network doesn't have path attributes.
For current stage, maybe try not to touch validate_sop_output_node.py as it is not only pointcache using but other families like vdbcache involving.
DopNode
I dont have so much objection on that. but I think you can check the see if the dop nerwork from the dop import has the pack nodes.
Any thoughts? @BigRoy @antirotor

@BigRoy,I admit that it is getting more and more confusing.
I am actually talking about the string value where stores the opname('..')/opname('..')Shape. So basically the nodes such as attribute_create or connectvity can store path primitive attributes with string value. But the relative references of the string value are different. e.g. the one from the attribute_create is chs("string1") while that from connectivity is chs("prefix"). Maybe the screenshot can explain more than words. Repair action may not fix all the errors as the relative references from nodes to nodes are different.

I am actually talking about the string value where stores the opname('..')/opname('..')Shape. So basically the nodes such as attribute_create or connectvity can store path primitive attributes with string value. But the relative references of the string value are different. e.g. the one from the attribute_create is chs("string1") while that from connectivity is chs("prefix"). Maybe the screenshot can explain more than words. Repair action may not fix all the errors as the relative references from nodes to nodes are different.

I still don't see the issue unfortunately. We never validate those particular nodes - we only validate the output and whether it's geometry is ok or not. If not, then I believe currently this issue proposes to add repair actions which "insert" some nodes above the output node that add a path entry. That repair has full control over the nodes it generates and thus it should be trivial to set the right values. Right?

Let's take a few steps back: To clear up some misconceptions, correct me if I'm wrong
the original objective of this issue was to:

add path repair action
create output sop node if not present

ouptut sop node + my ignorance, they added few complexity
my apologies.

let me summarize this discussion:
enhancement 1 : path repair action
if no path attribute,  A connectivity node with

attribname same as path_attrib  in the ROP node
prefix like this opname('..')/opname('..')Shape_
Connected as follows

before output node if the output node's is type null or output
otherwise after output node and set sop_path accordingly

because output node may be a merge or copy node and connecting before will lead to un-desired results

P.S.
I prefer connectivity as it will increment for each connected piece
In maya it will the same object with many shapes inside it, we can discuss if this will be sufficient for now.
enhancement 2 :  output repair action
because Validate Output Node requires a sop node set in sop_path in the ROP node
this validator will error for many reasons
a general repair action to set it to the selected sop node
I suggest to extend it allow selecting obj nodes as well  and using the same logic to get the correct output node

this repair action will affect these families pointcache, vdbcache

enhancement 3 : create point cache
bear in mind that Validate Output Node requires a sop node
this code doesn't correctly detect the output node whether it's an output node with the smaller outputidx
or the node with the display flag
also, it allows all node types e.g. I can create an alembic subset while selecting a dop node, an artist may wonder why it's allowed despite publisher will error
# try to find output node
for child in self.selected_nodes[0].children():
    if child.type().name() == "output":
        parms["sop_path"] = child.path()
        break

bug fix : validators error (crash)
it happens when this line is executed as for many reasons, the output node may not have geometry
geo = output_node.geometryAtFrame(frame)
this bug happens in

validate_abc_primitive_to_detail.py
validate_primitive_hierarchy_paths.py

a quick fix to add a check like this: to skip if not hasattr(output_node, "geometry")

this fix may be irrelevant to this issue however I needed to fix it to test these enhancements

Let me know that do you think ?
@moonyuet @BigRoy @antirotor

Thanks for the breakdown

enhancement 1 : path repair action

I think this can be a nice feature. Definitely a PR on its own... but there are so many edge cases that I'm still wondering whether it's worth it.
In many cases, Connectivity is NOT the way to do it. In many case, single name is NOT the way to do it. Etc. what if connectivity changes over time? etc.
The highest priority is that the Validator explains the issue to the artist in a way that is understandable. What data is missing, why and how can I fix it? Then having a repair is secondary to that. If you feel artists get stuck 90% of the time, our priority is improving the reports output so they know what to do.
Once that's done, then we can look into tooling that can provide some out of the box options which will be INVALID 90% of the time: Set path by connectivity, Set single path, Set path by attribute X, etc. but we will need to keep in mind that these are just "helpers" and not a full blown repair since there are so many cases where it's NOT the intended export design for your particular case in production.

enhancement 2 :  output repair action

this repair action will affect these families pointcache, vdbcache

Since this influences VDBCaches as well we can't use the same logic for both unfortunately - since afaik we should never set an object level path. Which actually makes me think allowing obj level path (as described in enhancement 3 below) should just be disallowed from OP point of view. It's just much more complex, and by still allowing explicit SOP level paths we still allow it to export the same things. (We're not losing features by requiring a SOP path instead - we're solely making it more explicit)
Having a repair action that updates the SOP path using the selection can be nice. However, we'll need to make sure that the action's label is not "Repair" but something like "Update sop path from selection" or alike because with "Repair" you wouldn't know it'll be using your selection. Which makes me think, isn't it much clearer if we just LOG very clearly what the user should end up doing (setting a valid SOP path in the SOP Path parameter) and maybe just having a "Select invalid" action on the plugin. The log then clearly mentions:
"The SOP Path is not set to an existing SOP path, make sure to update it on the ROP node." and then you can just select the ROP node to do it yourself. I'm not sure a "Set from selection" is going to be that much clearer for the artist especially compared to how much code might need to be written to write it and maintain it over time. Is it worth it?
enhancement 3 : create point cache

bear in mind that Validate Output Node requires a sop node

Yes.

this code doesn't correctly detect the output node whether it's an output node with the smallest outputidx
or the node with the display flag

This might be a language barrier in your wording, but it doesn't have to be an output node with the smallest id NOR does it need to have the display flag. The preferred way pipeline-wise would be to have it point to a SOP path on the ROP node, but apparently Houdini Alembic ROP supports putting an OBJ path in the SOP path parm - confusing, but hey, let's support it.
As such, output SOP node becomes:
output_node = = instance.data["output_node"]
if isinstance(sop_node, hou.SopNode):
    # all ok
    sop_node = output_node
elif isinstance(sop_node, hou.ObjNode):
    # convert to relevant sop path
    sop_node = get_obj_output(output_node)
    if not sop_node:
        sop_node = get_obj_display_output(output_node)
        # Technically this could still be None if there are no nodes in the geometry node to begin with

However, as I mentioned in Enhancement 2 we're likely better of disallowing ObjNode paths to begin with and forcing SopNode paths.
As you can clearly see - even a simple case like this becomes way more complicated now ;) As such I'd recommend taking each of the enhancement you mention here into separate PRs since each likely involves code changes quite isolated plus already quite lengthy each.

also, it allows all node types e.g. I can create an alembic subset while selecting a dop node, an artist may wonder why it's allowed despite publisher will error

I think logic wise maybe it just makes sense to set any SOP path from selection if found, if not found set the OBJ node path (since apparently that works in Houdini) and if not found then set nothing from selection with maybe logging a warning that no valid selection was found.
selection = self.selected_nodes
path = None
preferred_node_types = [hou.SopNode, hou.ObjNode]
for type in preferred_node_types:
    if path is None:
        for node in selection:
            if isinstance(node, type):
                path = node.path()
                break

Not the prettiest code, but it shows the idea. We don't need to redirect to "output" nodes, etc.

bug fix : validators error (crash)

Yes, let's add the fix. Could even be a PR of its own since it doesn't change much about the enhancements.

Sounds good. Let's draft each of those and go from there.

There are many PRs related to this issue!
enhancement 1: Validate Prims Hierarchy Path(ABC)
Enhancement/houdini add path action for abc validator
enhancement 2 : Validate Output Node
Houdini: add select invalid action for ValidateSopOutputNode
enhancement 3 : create point cache
on my way
bug fix : validators error (crash)
Houdini: Add geometry check for pointcache family
Houdini: Add geometry check for VDB family

it's not related to this issue however it shares the same bug as the point cache.


Queues and sleep option

By default, the sleep option is set to 3 seconds. In some scenarios, setting it to lower values can decrease the time it takes for workers to do pending jobs.
Currently, you can't set it lower than 1 second, since sleep() function is used, instead of usleep().
Say you're developing a search engine, and you spin up 10 workers that listen for incoming jobs. Supervisor will ensure jobs are up and running, and we set the sleep value to 1 second. Once 50 jobs have been created, workers will start to consume them. But if a worker has already started sleeping while the job was created, it has to wait for up to a second before it sees new jobs as available.
The statistical chances of all workers being on the same time horizon is small. So a worker can already work on those 50 jobs while some 9 workers are still asleep (that 1 second).
In average, this affects the search engine performance with up to a second. An extra second for a user waiting for results to show is a lot.
Can you allow sleep to be lower than 1? I understand that in doing so, the CPU load can increase. But a value of, say 0.2 is still fine.

We don't sleep in between jobs. We only sleep if nothing happened the last time.

If your jobs take less than 0.02 seconds to run, you probably don't need to worry about this.

jobs usually take 0.2 - 0.3 seconds. Their number, could be in the range of, 50 - 100. This sleep parameter can affect the total duration with up to a second. Say now I press "Search", the system creates 50 jobs that need to be worked on. All workers are still sleeping (since no previous jobs were executed) and won't wake up for a second. This extra second is time we cannot optimise now.
Even if not all workers are sleeping, the number of the ones that are awake is too small to compensate.

I had exactly same issue and ended up by implementing custom worker that can sleep in sub-second precisions:
<?php

namespace App;
use Illuminate\Queue\Worker;

class Ph4Worker extends Worker
{
    /**
     * Sleep the script for a given number of seconds.
     *
     * @param  int   $seconds
     * @return void
     */
    public function sleep($seconds)
    {
        usleep(floatval($seconds) * 1e6);
    }
}

Then just register it in custom QueueServiceProvider:
<?php

namespace App\Providers;

use App\Ph4Worker;
use Illuminate\Support\ServiceProvider;
use Illuminate\Contracts\Debug\ExceptionHandler;

class QueueServiceProvider extends ServiceProvider
{
    /**
     * Define your route model bindings, pattern filters, etc.
     *
     * @return void
     */
    public function boot()
    {
        $this->app->singleton('queue.worker', function () {
            return new Ph4Worker(
                $this->app['queue'], $this->app['events'], $this->app[ExceptionHandler::class]
            );
        });
    }
}

sounds great, will try this out

I'm bit late to the party,
but you can just open a database connection in your queue worker job and do:
select sleep(1);

It would look something like this:
// in your handle function
        $results = DB::select('select sleep(1)');


Add a tool to migrate testsettings to runsettings

Description
Adding a tool to migrate testsettings to runsettings

using System;

Follow the standards for commenting and using statements

Refers to: src/SettingsMigrator/TestSettingsNodes.cs:1 in 6922920. [](commit_id = 6922920b4aa2a4be6d30a2dd2ad1dee7dc6f6bf1, deletion_comment = False)

Overall looks good. @smadala @mayankbansal018  Can you take a look?

@dotnet-bot Test Ubuntu14.04 / Debug Build

@dotnet-bot test Windows_NT / Release Build please


Impove logging in  server.ts

Hi,
Trying to run dbos in a docker container I faced some issues with starting up the server.
One of them turned out to be that I had not configured my docker service to allow ipv6 addresses which I managed to solve.
In the mean time I was getting error messages that did not make sense.
After reading httpServer/server.ts I figured what my problem was and also that this piece of code needs some improvement
so as to provide meaningful error messages.
The code of  listen consolidates two errors in one.
This is the one that confused me enough so as to have to read the code.
Also the result of checkPortAvailability is ignored.
If you think there is a point in fixing this I would happily prepare an MR if you point me at what the desired result should behave like.
Thanks a lot.

Hello! Thanks for your feedback. We create a PR to improve error logging: https://github.com/dbos-inc/dbos-transact/pull/383
Does it address your issue?

It certainly does!


Fix Typo in Convex Hull

Checklist

[x] I've looked at the contribution guidelines.
[x] This pull request is complete and ready for review.

Description

Fixes a typo in Convex Hull README

Thanks for the fix!


Update bot to remove needs triage label once an area is assigned

Clear and concise description of the problem
We should update our bot to remove the needs triage label when an area is assigned.
We should also re-add the needs triage if all area labels are removed.
Checklist

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

pri: 1


ENS support shouldn't use a whitelist

Currently ENS support uses a whitelist of ENS TLDs. However, we plan to expand ENS support to many new DNS-based TLDs in the future, and whitelisting is impractical.
A better solution would be to simply try resolving any name containing a dot - if it resolves, it's a valid ENS name!

Thanks for raising this - I tried to avoid network/service roundtrips - but yea I should value future-compatibility more than that (especially in current times where network/service roundrips are not as expensive anymore - still being a bit too old-school here) - change contained in 8acd970 and will be released via  0.84.2 today.


Introduce new property to handle functions call exprs and action call exprs returning error

Purpose
$subject
Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

@hasithaa this commit will address the function params with type inclusions issue.

@hasithaa this commit will address the function params with type inclusions issue.

We need a property to add key value pairs when there is a rest type in the record type definitions and also when the params are coming from a type inclusion we need to mark them with a flag to generate the source as named args. These things need to be discussed and implement.


feat: add default_headers to Gemini model

Description
Similar to OpenAI, allow default_headers for Gemini model as well
Type of Change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] I stared at the code and made sure it made sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

@logan-markewich can you please review?

Left a comment about documentation.

Thanks. Accepted.

Bumped the version so integration will be released on merge.


sign out functions now

had one conflict with dan's push on home.js, i canceled my code on that file and kept dan's instead


How to remove usingPUT?

1, How to remove ALL usingPUT/usingPOST/UsingGET1/using* at the end of the suspend fun?
2, How to remove header:
"X-Operation-ID: blabla"?
3, How to generate responses under models/responses and requests under models/requests?
BTW, Thanks for the library!

2, is solved

2, is solved

1, solved sorry it was in the spec file: "operationId"
I just simple removed that chars

1, solved sorry it was in the spec file: "operationId"
I just simple removed that chars

3, What is the class that can I refactor/update to create that two responses/requests directories?
I think this is possible, because we know what is the Request classes and what is the Response classes, so in this way we can seperate it...

3, What is the class that can I refactor/update to create that two responses/requests directories?
I think this is possible, because we know what is the Request classes and what is the Response classes, so in this way we can seperate it...

3, What is the class that can I refactor/update to create that two responses/requests directories?

It's the KotlinGenerator class https://github.com/Yelp/swagger-gradle-codegen/blob/master/gradle-plugin/plugin/src/main/java/com/yelp/codegen/KotlinGenerator.kt

3, What is the class that can I refactor/update to create that two responses/requests directories?

It's the KotlinGenerator class https://github.com/Yelp/swagger-gradle-codegen/blob/master/gradle-plugin/plugin/src/main/java/com/yelp/codegen/KotlinGenerator.kt

Thanks, I will try it

Thanks, I will try it

I'll close this issue as it's a mixture of questions. Should you need further support on point 3, please open another issue 👌

I'll close this issue as it's a mixture of questions. Should you need further support on point 3, please open another issue 👌


Suppress exhibitor migration script stdout during upgrade

High Level Description
This prevents the upgrade script from printing scary-looking messages when the Exhibitor API isn't available, which is expected immediately following an upgrade.
Related Issues

DCOS-14046 Upgrade Procedure for 1.9 Findings

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

@BenWhitehead @orsenthil Ready for review.

Closing in favor of #1276. This PR is going to need to be rebased once #1276 is merged, and it's a small change, so it makes more sense to include it with the other fixes in that PR.


Only automatically set resources that do class X < Chef::Resource

not X = Class.new(Chef::Resource)
This fixes #3524

Parens fixed :)  I'll take a look at start_with tomorrow.


Feature request: Timestamps instead of incrementing ids

This library looks super cool, thanks for building it.
I work in a large engineering org with multiple teams. We use migratus which uses timestamps as the migration "number". This means that no matter how many people generate migrations on separate branches, there's no conflicts when they're merged to main.
Is there planned support for using timestamps (ISO 8601) as the number instead of a padded integer?

@NoahTheDuke Hi! Thank you for the feedback and for creating the first issue!
I considered using timestamps instead of incremented integers as the number of a migration version when I was building this part of the library, but decided to go with integer numbers. The reason involves a couple of considerations:

from my point of view, the application order of migrations should be predictable and explicit;

with timestamps, there's a possible scenario where a merged and already applied migration in the main branch has a more recent timestamp than the migration from a PR; in this case, the migration with the older timestamp would be applied in the wrong order according to the timestamps;

this approach (with an unfixed order of migration application) works well if migrations don't depend on each other, for example, for different tables; but sometimes if migrations relate to the same table or same columns, they must be applied in a particular order; the approach with incremented integer numbers guarantees this, whereas with timestamps you have to track it on your own;
the integer number of a migration is useful for the explain command and for migrating in forward or backward directions to a particular migration.

The downside is that before merging a PR, we have to ensure that there is no clash in migration numbers. The good part is that Automigrate has validation for this and will notify about duplicated migration numbers.

I think, we can keep this issue for a while in case there are other solutions on this to consider or discuss.

The downside is that before merging a PR, we have to ensure that there is no clash in migration numbers.

For our use-case, this would be a massive issue. We merge changesets to main 10+ times a day, and any number of them will have migrations. If we had to rebase/update every time someone merged, we'd be significantly slowed down.
I don't see us switching either way, we're tied to migratus, so don't rush to make any changes for us. I just want to make you aware of the trade offs here.


Codegen support for int8 model with fusion of dequantize and conv ops

We need to fuse the dequantize and conv kernels in Unet int8 model in order to achieve memory bandwidth improvement on AMD GPUs.  This issue is created for tracking the discussion about the possible ways of Codegen.
Here's the example IR taken from the Unet. And after generalizing the conv and some other preprocessing, we have moved the dequantize and conv into a single dispatch (IR).
We are currently taking the implicit GEMM path for Codegen, but other ideas and suggestions are also welcome.

@mattwalsh @MaheshRavishankar  Please add anyone who should be involved in this discussion.

(sigh.. another P1 bug...) Added myself to discussion... I dont think we are at a stage where we can have actionable work on this... its still in exploration stage... I can work with Quinn on this.

From discussion yesterday, there are two things going on here. First, this is essentially a convolution with quantized weights (very similar to the quantization happening in #12859, but for conv instead of matmul). Similarly the focus is on SPIR-V as well for this.
The first issue is forming the correct dispatch and whether to fuse the conv and dequant before hand or keep them separate. Keeping them separate makes the matching easier in the backend but complicates things up through Flow. The solution is to put the two ops in their own dispatch in advance and make sure the backend can generate the right code.
The second difficulty comes from the fact that the quantization scheme is "pre-packing" the input channels without actually moving the data. This is essentially the frontend trying to pick a data layout way in advance. Packing can be done with tensor.pack, the question is when/how to apply the packing. There are two options for this:

Do it in advance as a pre-processing pass (I have something experimental for that kind of packing on NCHW convolutions and can push it if wanted) but that will do propagation and essentially makes all of the convolutions become generic ops.
Use some sort of attribute to indicate the packed layout of the convolution and dequantization and only materialize the packing dispatches immediately before lowering to the  backend (@MaheshRavishankar correct me if I interpreted that wrong). This would push along pack/unpack codegen in the SPIR-V backend as a nice bonus.

The last part is doing codegen for the quantized convolution. I'm planning to open an updated PR for implicit gemm codegen next week (similar to #12806) which could be used to prototype codegen for blocked convolutions (contingent on some img2col improvements that I have yet to push upstream). Alternatively we can improve direct convolution to support blocked convolutions (probably worth doing anyway).

Do it in advance as a pre-processing pass (I have something experimental for that kind of packing on NCHW convolutions and can push it if wanted) but that will do propagation and essentially makes all of the convolutions become generic ops.
Use some sort of attribute to indicate the packed layout of the convolution and dequantization and only materialize the packing dispatches immediately before lowering to the  backend (@MaheshRavishankar correct me if I interpreted that wrong). This would push along pack/unpack codegen in the SPIR-V backend as a nice bonus.

We could use what is done today with data tiling path. If you try iree-compile --iree-flow-enable-data-tiling on a matmul example you should see the encoding we use for tensor types to represent pack layout at Flow level, and then how it gets materialized in backend... this seems like we need something similar.

Do it in advance as a pre-processing pass (I have something experimental for that kind of packing on NCHW convolutions and can push it if wanted) but that will do propagation and essentially makes all of the convolutions become generic ops.
Use some sort of attribute to indicate the packed layout of the convolution and dequantization and only materialize the packing dispatches immediately before lowering to the  backend (@MaheshRavishankar correct me if I interpreted that wrong). This would push along pack/unpack codegen in the SPIR-V backend as a nice bonus.

We could use what is done today with data tiling path. If you try iree-compile --iree-flow-enable-data-tiling on a matmul example you should see the encoding we use for tensor types to represent pack layout at Flow level, and then how it gets materialized in backend... this seems like we need something similar.

How would this interact with putting the dequant + conv in their own dispatch before Flow? I don't see how it would generate these set_encoding dispatches due to the surrounding dispatch, e.g.
  %5 = flow.dispatch.workgroups(%2) : (tensor<1024x512xf32>) -> tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>> =
      (%arg3: !flow.dispatch.tensor<readonly:tensor<1024x512xf32>>, %arg4: !flow.dispatch.tensor<writeonly:tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>>>) {
    %9 = flow.dispatch.tensor.load %arg3, offsets = [0, 0], sizes = [1024, 512], strides = [1, 1] : !flow.dispatch.tensor<readonly:tensor<1024x512xf32>> -> tensor<1024x512xf32>
    %10 = iree_linalg_ext.set_encoding %9 : tensor<1024x512xf32> -> tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>>
    flow.dispatch.tensor.store %10, %arg4, offsets = [0, 0], sizes = [1024, 512], strides = [1, 1] : tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>> -> !flow.dispatch.tensor<writeonly:tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>>>
    flow.return
  } count() -> (index, index, index) {
    %x, %y, %z = flow.dispatch.workgroup_count_from_slice
    flow.return %x, %y, %z : index, index, index
  }

But AFAIK there isn't any mechanism to break up an existing dispatch. Or would we have to create those set_encoding/unset_encoding dispatches in advance as well.

Do it in advance as a pre-processing pass (I have something experimental for that kind of packing on NCHW convolutions and can push it if wanted) but that will do propagation and essentially makes all of the convolutions become generic ops.
Use some sort of attribute to indicate the packed layout of the convolution and dequantization and only materialize the packing dispatches immediately before lowering to the  backend (@MaheshRavishankar correct me if I interpreted that wrong). This would push along pack/unpack codegen in the SPIR-V backend as a nice bonus.

We could use what is done today with data tiling path. If you try iree-compile --iree-flow-enable-data-tiling on a matmul example you should see the encoding we use for tensor types to represent pack layout at Flow level, and then how it gets materialized in backend... this seems like we need something similar.

How would this interact with putting the dequant + conv in their own dispatch before Flow? I don't see how it would generate these set_encoding dispatches due to the surrounding dispatch, e.g.
  %5 = flow.dispatch.workgroups(%2) : (tensor<1024x512xf32>) -> tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>> =
      (%arg3: !flow.dispatch.tensor<readonly:tensor<1024x512xf32>>, %arg4: !flow.dispatch.tensor<writeonly:tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>>>) {
    %9 = flow.dispatch.tensor.load %arg3, offsets = [0, 0], sizes = [1024, 512], strides = [1, 1] : !flow.dispatch.tensor<readonly:tensor<1024x512xf32>> -> tensor<1024x512xf32>
    %10 = iree_linalg_ext.set_encoding %9 : tensor<1024x512xf32> -> tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>>
    flow.dispatch.tensor.store %10, %arg4, offsets = [0, 0], sizes = [1024, 512], strides = [1, 1] : tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>> -> !flow.dispatch.tensor<writeonly:tensor<1024x512xf32, #iree_linalg_ext.encoding<MATMUL_F32F32F32_RESULT>>>
    flow.return
  } count() -> (index, index, index) {
    %x, %y, %z = flow.dispatch.workgroup_count_from_slice
    flow.return %x, %y, %z : index, index, index
  }

But AFAIK there isn't any mechanism to break up an existing dispatch. Or would we have to create those set_encoding/unset_encoding dispatches in advance as well.

We can chat on GVC but the set_encoding op is what lowers to the pack op... the other dispatches will see the same packing... as long as you interpret the encoding in a consistent way, all dispatches will see the same state. In your IR dump you can see before and after the MaterializeEncoding pass.

We can chat on GVC but the set_encoding op is what lowers to the pack op... the other dispatches will see the same packing... as long as you interpret the encoding in a consistent way, all dispatches will see the same state. In your IR dump you can see before and after the MaterializeEncoding pass.

Happy to chat on GVC (whenever you have time, will follow up elsewhere + will pull in @yzhang93). I'm just seeing a conflict between the solution to the fusion problem and the packing problem.

Leaving a belated summary of the discussion here:
There are two parts of the discussion, first being handling the codegen part and second getting the correct ops to fuse in the way we want. For codegen we most likely will want to keep the convolution in its packed generic form, with a fused leading dequantization on the filter, e.g.
  flow.executable private @example_dispatch_2 {
    flow.executable.export public @example_dispatch_2_generic_2x320x64x64x20x3x3x16_f16 workgroups(%arg0: index, %arg1: index, %arg2: index, %arg3: index) -> (index, index, index) {
      %x, %y, %z = flow.dispatch.workgroup_count_from_dag_root %arg0, %arg1, %arg2, %arg3
      flow.return %x, %y, %z : index, index, index
    }
    builtin.module {
      func.func @example_dispatch_2_generic_2x320x64x64x20x3x3x16_f16(%arg0: !flow.dispatch.tensor<readonly:tensor<320x20x16x3x3xi8>>, %arg1: !flow.dispatch.tensor<readonly:tensor<320x20x3x3xf16>>, %arg2: !flow.dispatch.tensor<readonly:tensor<2x20x66x66x16xf16>>, %arg3: !flow.dispatch.tensor<readonly:tensor<320xf16>>, %arg4: !flow.dispatch.tensor<writeonly:tensor<2x320x64x64xf16>>) {
        %cst = arith.constant 0.000000e+00 : f16
        %0 = flow.dispatch.tensor.load %arg0, offsets = [0, 0, 0, 0, 0], sizes = [320, 20, 16, 3, 3], strides = [1, 1, 1, 1, 1] : !flow.dispatch.tensor<readonly:tensor<320x20x16x3x3xi8>> -> tensor<320x20x16x3x3xi8>
        %1 = flow.dispatch.tensor.load %arg1, offsets = [0, 0, 0, 0], sizes = [320, 20, 3, 3], strides = [1, 1, 1, 1] : !flow.dispatch.tensor<readonly:tensor<320x20x3x3xf16>> -> tensor<320x20x3x3xf16>
        %2 = flow.dispatch.tensor.load %arg2, offsets = [0, 0, 0, 0, 0], sizes = [2, 20, 66, 66, 16], strides = [1, 1, 1, 1, 1] : !flow.dispatch.tensor<readonly:tensor<2x20x66x66x16xf16>> -> tensor<2x20x66x66x16xf16>
        %3 = flow.dispatch.tensor.load %arg3, offsets = [0], sizes = [320], strides = [1] : !flow.dispatch.tensor<readonly:tensor<320xf16>> -> tensor<320xf16>
        %4 = tensor.empty() : tensor<2x320x64x64xf16>
        %5 = tensor.empty() : tensor<320x20x3x3x16xf16>
        %6 = linalg.fill ins(%cst : f16) outs(%4 : tensor<2x320x64x64xf16>) -> tensor<2x320x64x64xf16>
        %7 = linalg.generic {indexing_maps = [#map2, #map3, #map4], iterator_types = ["parallel", "parallel", "parallel", "parallel", "parallel"]} ins(%0, %1 : tensor<320x20x16x3x3xi8>, tensor<320x20x3x3xf16>) outs(%5 : tensor<320x20x3x3x16xf16>) {
        ^bb0(%in: i8, %in_0: f16, %out: f16):
          %10 = arith.sitofp %in : i8 to f16
          %11 = arith.mulf %10, %in_0 : f16
          linalg.yield %11 : f16
        } -> tensor<320x20x3x3x16xf16>
        %8 = linalg.generic {indexing_maps = [#map5, #map6, #map7], iterator_types = ["parallel", "parallel", "parallel", "parallel", "reduction", "reduction", "reduction", "reduction"]} ins(%2, %7 : tensor<2x20x66x66x16xf16>, tensor<320x20x3x3x16xf16>) outs(%6 : tensor<2x320x64x64xf16>) {
        ^bb0(%in: f16, %in_0: f16, %out: f16):
          %10 = arith.mulf %in, %in_0 : f16
          %11 = arith.addf %out, %10 : f16
          linalg.yield %11 : f16
        } -> tensor<2x320x64x64xf16>
        %9 = linalg.generic {indexing_maps = [#map8, #map9, #map8], iterator_types = ["parallel", "parallel", "parallel", "parallel"]} ins(%8, %3 : tensor<2x320x64x64xf16>, tensor<320xf16>) outs(%4 : tensor<2x320x64x64xf16>) {
        ^bb0(%in: f16, %in_0: f16, %out: f16):
          %10 = arith.addf %in, %in_0 : f16
          linalg.yield %10 : f16
        } -> tensor<2x320x64x64xf16>
        flow.dispatch.tensor.store %9, %arg4, offsets = [0, 0, 0, 0], sizes = [2, 320, 64, 64], strides = [1, 1, 1, 1] : tensor<2x320x64x64xf16> -> !flow.dispatch.tensor<writeonly:tensor<2x320x64x64xf16>>
        return
      }
    }
  }

From here there is a reasonable path to get to codegen with existing interfaces where the dequantize will just be treated like a leading elementwise op. For getting to this fusion though, for now the plan is to put these ops in their own dispatch as a preprocessing step and then use that to get around undesirable fusions (i.e. fusing the conv and dequant into a single generic). A less ad-hoc solution will probably rely on being able to infer something about what a dequantization operation is (two options for the input below with what currently will happen to them today).

linalg.conv(tensor.collapse_shape(dequant)) (dequant and matmul will form different kernels)
linalg.generic(dequant) (already expanded, this will get fused into a single generic which isn't ideal)


Rename gem to insights-api-common

@bdunne @agrare @gtanzillo @gmcculloug @syncrou Please review.
😱

All tests passed...not sure if that means 100% coverage though

@Fryguy do we want all of the change log to say insights_ vs manageiq_ for all the entries including those in the past? Possibly track the name change in the change log?
Sent with GitHawk

This PR has the name change on the changelog but I didn't go back and change old entries.  Not sure if I should...I debated it.  Curious what others think

I don't think we should go back and change old CHANGELOG entries, :+1: for what you have here

@bdunne After this is merged, I'd like to release this as a major version bump.  Then, the apps can update accordingly.  We can move the repo anytime after merge since if teams are using the gem, the code location really doesn't matter.

Is Insights the proper name to switch our modules and other items to?
I realize the repo name we are moving to is RedHatInsights but that name was selected when the platform was referred to as Insights.  Now the platform is commonly referred to as Cloud Services or Cloud Platform or cloud.redhat.com and an application uses the Insights name.
I'm fine if we want to keep Insights but thought it was worth pointing out.

It's a good question, and that did occur to me as well, but I can't think of what else to call it.  As you said, insights is the org, so that seemed ok to me.

What do you all think of RedHatCloudServices::Api::Common & red_hat_cloud_services-api-common ?
@bdunne @gtanzillo @syncrou @gmcculloug @agrare ?

That works too, most of the platform repos there are still called insights- though so I don't think its a big deal either way.

most of the platform repos there are still called insights-

that was actually one of the other reasons I went with insights, but I think insights is still a "product" that is a subset of cloud.redhat.com

The thing is that it will probably change multiple times over the life of this repo so either one is fine.
Actually, "insights" is probably safer because it is an existing product, as you mentioned, and there are existing repos with that name.

but I think insights is still a "product" that is a subset of cloud.redhat.com

Oh yeah not disagreeing with that at all, just noting that most of the repos from "that platform formerly known as insights" are still called "insights-" even if they aren't for "inisghts, the app"

I'm leaning towards keeping it insights- personally, aside from the naming, it's just shorter.

:+1:

I'm also fine with "insights-"

@Fryguy Sorry for the merge conflict.  I had to release a new version before we renamed.

@bdunne I removed all of the namespace manipulations and put them back, so this is now just a pure rename.


Different typing in vscode than in TS Playground

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.67.2
OS Version: KDE Neon 20.04

Steps to Reproduce:

install zod using npm install zod or an equivalent
create a TS file with the following content :

import { z } from "zod"

const transformer = <T extends { test: z.Schema }>(value: T): T => value
const test = z.object({ test: z.string() })
export const value = transformer(
  class Test {
    static test = z.object({ test: z.string() })
  }
);
export type value = any

over static test in class Test

Test is shown as being of type any. If you remove the type export, it’s shown properly:

And it also work if you define test using the schema defined just before:

Strangely, there is no problem when doing the same test on the TS playground: https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzgLzgXzgMyhEcBEyEAJvgLABQlAxhAHYDO8MUAho5tCAKZRwC8cADwAVONwAeMbnWINEcaUwBcKAHQBlagAtuIVugB8ACgBurADYBXbqpEBKOwMNxz17jXpNF3b4ORqEABGAFbc1DDGSEowqgFMUMB0AObG9uj2lJKQsHC0jPBuNgKKbBxcvMaUcHkWrAzyIr7wCNU1cEysMMDUPn7qwWERUX2x6glJqelomRQ1aJT2ANxZEjnMAJ5g3K6WxYLsG5RAA
That seems to indicate this is not a TS bug. I thought it was at first.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Oops, I posted by mistake and got the version wrong. This is now fixed. I was in fact using the last version of VS Code.

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[vivado ip] reorganize IP GUI layout

Hi!
So I used the approach in #1058 to make m_axi bus optional, and made some parameters editable depending on other parameters. (e.g. XBUS_CACHE_EN is editable only when XBUS_EN is set)
I also reorganized the IP GUI by splitting parameters into pages and groups, which maybe look more neat and is easier to use.

The attributes for JTAG ports doesn't compile in GHDL, not sure if it's a bug of it.🤔

Sure! And I'm closing this PR to make it convenient.


Window title flickering

When I hover mouse cursor over window title on panel, it starts to flicker after several seconds I hold cursor over it. As far as I can see, it's caused by tooltip. Somehow tooltip is being interpreted by panel as separate window and tries to show it's own title.

Yeah, it's a known issue #63, it didn't do it until a sway/wlroots update, I'd have to look where it came from.


Enable VSCode extension APIs for opening notebooks.

These changes enable the following VSCode extension APIs, which are needed for .NET Interactive support:
vscode.workspace.openNotebookDocument
vscode.window.showNotebookDocument
I also moved all the notebook conversion classes to a common folder to reduce clutter, as well as moving several utility functions to a dedicated file.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.209%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
14713

Relevant Lines:
28977

💛  - Coveralls