make-derivation.nix: lib.warn if drv.__spliced missing

This should wait until after 23.11, but I'd like to try to merge it fairly promptly thereafter.
Right now when an unspliced package appears as a dependency, we just silently do the wrong thing, cross our fingers, and hope for the best.  This is the reason why troubleshooting cross compilation is such a headache.
This PR adds a lib.warn for this situation when cross compiling.  So we still do the wrong thing, but at least we tell the user that something is probably wrong.  The warning will also cause CI to fail.  I fixed about a dozen of these failures.  The list-of-shame provides an escape hatch for urgent situations.
The list-of-shame currently has (about) two dozen of these splicing failures; these are ignored in order to get CI to pass.  The idea is to get a check like this in place to prevent even more of these bugs from occurring while we work to eliminate the ones that are already there.  Since lib.warn causes CI failures this will prevent people from introducing any more of these bugs (or else force them to add their stinky deeds to the list of shame).

[x] CI passes
[x] No mass rebuild (14 packages rebuilt, due to fixing splice failures)

Proof that we are not splicing Rust hooks: check out this PR, then run:
nix-instantiate . -A pkgsCross.aarch64-multiplatform.fd

in the output you'll see:
trace: warning: derivation fd:
                     unspliced dependency /nix/store/99jm62fd7xh1yzjys0z3r70d1vvra51r-cargo-build-hook.sh
                       build=x86_64-unknown-linux-gnu
                       target=aarch64-unknown-linux-gnu

trace: warning: derivation !!no pname!!:
                     unspliced dependency /nix/store/cxxbmvm5dsjif4v4d82q0mb7ympp8jlc-aarch64-unknown-linux-gnu-cargo-1.72.1
                       build=x86_64-unknown-linux-gnu
                       target=aarch64-unknown-linux-gnu

trace: warning: derivation fd:
                     unspliced dependency /nix/store/84aap5fr5s6yblga5w6fbx71j21l591a-cargo-check-hook.sh
                       build=x86_64-unknown-linux-gnu
                       target=aarch64-unknown-linux-gnu

trace: warning: derivation fd:
                     unspliced dependency /nix/store/0796vgahxgg8n7w1gr2pdb9sd3kibk13-cargo-install-hook.sh
                       build=x86_64-unknown-linux-gnu
                       target=aarch64-unknown-linux-gnu

trace: warning: derivation fd:
                     unspliced dependency /nix/store/qppx46087vy5xx8j3jajbzbqsjhvcp2b-cargo-setup-hook.sh
                       build=x86_64-unknown-linux-gnu
                       target=aarch64-unknown-linux-gnu

Is similar to https://github.com/NixOS/nixpkgs/pull/204387

Is similar to #204387

Well, I think they're sort of orthogonal (and both are a good idea).  It looks like checkExecutableOnBuild  always succeeds when the __spliced attribute is missing even if it should be there -- whereas the point of this PR is to emit a warning in exactly that situation.  Currently it takes way too long to figure out if a problem is caused by splicing not happening.
You should merge yours first since mine isn't done and is easier to rebase.

Befofe merge there should be a way to fix the warning.
We should find out a way to splice or work around the lack of splicing when a function that returns derivation(s) is used (without adding it to be reachable from top-level).
Maybe a callPackage like func which internally calls with the various sets callPackage's, but a issue would still be what the user passes if it was not already spliced (eg overrideAttrs was used).

always succeeds when the __spliced attribute is missing even if it should be there

Explicitly used sets like buildPackages won't have a __spliced in packages

We should find out a way to splice or work around the lack of splicing when a function that returns derivation(s) is used (without adding it to be reachable from top-level).

The way to do that is to have all derivations be spliced, always, all the time.  Then we don't have to worry about it.

Explicitly used sets like buildPackages won't have a __spliced in packages

I think that's the point.  Those should never be used in depsFooBar.
They should only be used when you need to interpolate into a string, like "${buildPlatform.lndir} ..."

Befofe merge there should be a way to fix the warning.

See 083501cc7f7b

Force-push has cleanup, dropped the stuff that I moved to other PRs.
I think 23888fe might actually pass CI.

Yeah it's gonna pass CI.

Woo hoo, CI passed!
Now about those rebuilds...

Sweet.  CI=ok, only 14 packages rebuilt (due to fixing splicing failures).  Reviews are now useful.

Fixed merge conflict.

@amjoseph-nixpkgs can we merge this soon?

@amjoseph-nixpkgs What do you think about merging this so that it forces the issue of fixing packages for cross? I would personally like it so that I can hunt down the cross issues in all of my out of tree packages.

@amjoseph-nixpkgs 23.11 branched off a while ago. Can we merge this?

@amjoseph-nixpkgs why close this? I found this useful when trying to figure out why some of my cross pkgs were broken.

@kjeremy I think this PR was closed in in the light of https://github.com/NixOS/nixpkgs/issues/50105#issuecomment-1902682831. While not necessary, Adam closed some of their open PRs (which is of cause okay if they like to do so).


Add support for colorscheme URL query param

Currently, colorscheme URL query param is not supported.
https://github.com/badges/shields/blob/master/server.js#L4363
It will be great a colorscheme URI param something like:
https://img.shields.io/bower/v/bootstrap.svg?style=flat-square &colorscheme=blue
Regards

Thanks for the suggestion!
There is a similar PR that adds colorA / colorB. Would it cover your use-case?

Related: #349, #547.
Feel free to reopen if you'd like to discuss further.


solana: upgrade matching engine and fix migrate instruction

Custodian has a serialization change, which is incorporated in the migrate method.
After upgrade, fix the migrate method and upgrade manager tests.

Also need to keep in mind serialization change on Auction Config in the latest changes. We will need to enact a proposal for new auction parameters that incorporate security deposit parameters.


Rk4 integrator

This PR adds an RK4 integrator that has been coded following the structure in https://github.com/loco-3d/crocoddyl/blob/4708428676f596f93ffe2df739faeb5cc38d2326/unittest/python/crocoddyl/integrated_action.py#L89.
I've found that in the reference python code there was a *dt missing in the cost computation (this is probably the only difference besides the use of Jtransport method).
It would be nice that you put special attention in the following items since I've had some doubts when implementing them:

Inside calc() and calcDiff() the code that has to be inside the enable_integration_ if clause.
Inside calc() the code that has to be inside the with_cost_residual_ if clause.
checkData method
quasiStaticmethod
Also take a look on the data I've declared to store all auxiliary computations for the method: both the naming as well as the kind of container I've used.

I've checked several examples using this integrator and comparing it with the Euler solution and the results are close. Also, I've compared the c++ code with the python integrator (adding the change that I mentioned above) and both are the same.
I'm also adding the python bindings. Let me know if you want me to implement some tests for this integrator.

Thanks @PepMS for this work!
We currently lack the infrastructure to test integrators. Meanwhile, once you update the bindings, I think it would be nice if you can

Modify the unittest/python/test_rk4.py to reflect the new c++ version.
Add your test comparing the current implementation against the legacy implementation that I did.

I've just  pushed all the requested changes.
Regarding the test against legacy code. I've done as we discussed. That is, I've changed the legacy python code inside unittest to crocoddyl_legacy. Also, I've done some minor changes to the legacy RK4 integrator to make it compaitble with the current bindings. Besides, I've added a python script named test_rk4_comp.py that containts the comparison for the quadrotor example and the arm manipulation example.
I think that this is all. If any further change is needed, let me know please.

Ok, next try:

I've reverted all the crocoddyl_legacy code to crocoddyl
I've included the legacy RK4 integrator into the bindings/utils/__init__.py
I've used the testing structure in unittest/bindings/test_actions.py to create two more tests related to the RK4 integrator.
all test passed when make test

I hope this is the right direction.

Thanks for the work @PepMS ! If @cmastalli is satisfied, we can merge this.

Great! It's a pleasure! :)


Nick: Watch techintegrations.net

Nick requests the watch of the watch_keyword techintegrations\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

techintegrations\.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Cody Gray in Charcoal HQ


[cinder-csi-plugin] Wrong DevicePath returned to VolumeAttachment.status.attachmentMetadata.

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Because of known misbehaviour in cinder (see #1065 #150) controllerserver reports wrong DevicePath to csi-attacher in ControllerPublishVolumeResponse.
What you expected to happen:
One of the following:

DevicePath is set to the right device path.
DevicePath is not set  or there is note on this behaviour in the docs.

How to reproduce it:
I don't know exact steps to reproduce but on my system it happens quite often. Possibly one can find steps to reproduce in previous mentioned issues.
Anything else we need to know?:
I read the CSI spec but didn't find any good solution for this problem.
One idea could be to update VolumeAttachment from the nodecontroller, but design doc requires VolumeAttachment to be owned by csi-attacher and that no other entities should update it.
Another solution could be to controllerserver request real device path from nodecontroller but as i understand nodecontroller listens only on unix socket so is not available from the controllerserver. And i don't know any way for nodecontroller to communicate real device path to the controllerserver.
I'll be happy to make a PR for this bug if you can guide me to appropriate solution.
Environment:

cinder-csi-plugin version: docker.io/k8scloudprovider/cinder-csi-plugin-amd64:v1.24.0
OpenStack version: Nova - Stein, Cinder - Wallaby
Others:

unfortunately we can't change version of openstack because we receive it from our cloud provider. but as i see by your link and in relevant issues in openstack issue tracker there was no progress on this issue.
do you know any possible solution for this in case  we can't rely on openstack?. can we somehow communicate device path from nodecontroller to controllerserver ?

I reviewed #1065 again and with comment
https://github.com/kubernetes/cloud-provider-openstack/issues/1065#issuecomment-627898467
I think the issue I talked above not exist any more (sorry remember wrong stuff)
except the NodeExpandVolume case but I think you are not using it?
looks like this is the function get the DevicePath
https://github.com/kubernetes/cloud-provider-openstack/blob/master/pkg/csi/cinder/nodeserver.go#L576
and I tried to produce this in #1065 also not able to reproduce
so can you confirm you are using Expand case ? (see #1065 for detailed discussion)

I'm not using expand case. The problem is with ControllerPublishVolume method (in this line). This method reports to csi-attacher and after that it publishes wrong device path in the VolumeAttachment resource.
For example:
apiVersion: storage.k8s.io/v1
kind: VolumeAttachment
metadata:
  annotations:
    csi.alpha.kubernetes.io/node-id: e8db4dbf-12e5-46c3-9d29-08d46dd21708
  creationTimestamp: "2022-09-20T04:39:50Z"
  finalizers:
  - external-attacher/cinder-csi-openstack-org
  name: csi-e0c2d695e8a71b5d7f413488433bff8988656e095036bc6ad9743db5b420ba6d
  resourceVersion: "2760435477"
  uid: 0e8a0141-85f3-4813-992b-2bbe3783e3c7
spec:
  attacher: cinder.csi.openstack.org
  nodeName: k8s-node-default-043
  source:
    persistentVolumeName: pvc-d71380c1-7686-4128-96cd-691017957cd2
status:
  attached: true
  attachmentMetadata:
    DevicePath: /dev/sdi

Here you can see that device path is reported as /dev/sdi but on the server i can check that real path is /dev/sdg. I can see it in the lsblk output:
sdg       8:96   0    1G  0 disk /var/lib/kubelet/pods/578f2dbd-0eb5-40e0-817c-404a7e798750/volumes/kubernetes.io~csi/pvc-d71380c1-7686-4128-96cd-691017957cd2/mount
                                 /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-d71380c1-7686-4128-96cd-691017957cd2/globalmount

It's the single place left in the code where we use openstack to determine device path. Expand case is working fine because of your old fix - no problem with it.
My use case is that i want to build io usage metrics for pvc's and for that i want to join node_exporter (like node_disk_io_time_seconds_total ) metrics (that has device label) with kube-state-metrics metrics (kube_volumeattachment_status_attachment_metadata has metadata_device_path and volumeattachment and there is some other metrics that allows me to get pvc name from device and node labels).
I have a workaround right now to make own exporter that will export info metric with volume name and corresponding device, but still i think i'll be better to fix it here or at least document this behaviour, that you can't trust attachmentMetadata in the VolumeAttachment resource.


[frameit] add support for new iPhone 12-family devices and their new colors

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

Add support for new iPhone 12 devices (12, 12 Pro, 12 Pro Max, 12 Mini) to frameit
Description

Add support for new iPhone 12 devices (12, 12 Pro, 12 Pro Max, 12 Mini) to frameit

added 2 new colors in frameit/devices_type.rb (Graphite & Pacific Blue)
added 4 new devices in frameit/devices_type.rb (iPhone 12, iPhone 12 Pro, iPhone 12 Pro Max, iPhone 12 Mini)

Note: iPhone 12 Mini device screen size doesn't match the official Apple screen specification but the size of the screenshot generated with a iPhone 12 Mini simulator (1125x2436 instead of 1080x2340). When using official size, frameit doesn't match the screenshot with iPhone 12 Mini frame.
Related: https://github.com/fastlane/frameit-frames/pull/15
Testing Steps

To test this branch, modify your Gemfile as:
gem "fastlane", :git => "https://github.com/nimau/fastlane.git", :branch => "nimau-frameit-iphone12-devices"

And run bundle install to apply the changes.

Hey @nimau 👋
Thanks for contributing to fastlane! Could you sign the CLA as asked by the bot up there? 🙏

In order to fully add support for iPhone 12 Pro and iPhone 12 Pro Max we probably need to add it to another map as well:
https://github.com/fastlane/fastlane/blob/cbfd2724de7b524f680be3e80a708c36297dbf3e/snapshot/lib/snapshot/reports_generator.rb#L87

When I try out this fix I get:
[✔] 🚀
[16:36:13]: Using device frames version 'latest'
[⠋] Framing screenshot './screenshots/sv-SE/iPhone 12 Pro Max-0_CalendarsLaidOut.png' [16:36:13]: Unfortunately device type 'Apple iPhone 12 Pro Max' is not available in Pacific Blue, falling back to Graphite...
[16:36:13]: Couldn't find template for screenshot type 'Apple iPhone 12 Pro Max Graphite'
[16:36:13]: Please run `fastlane frameit download_frames` to download the latest frames
[⠋] Framing screenshot './screenshots/sv-SE/iPhone 12 Pro-0_CalendarsLaidOut.png' [16:36:13]: Unfortunately device type 'Apple iPhone 12' is not available in Pacific Blue, falling back to Black...
[16:36:13]: Couldn't find template for screenshot type 'Apple iPhone 12 Black'
[16:36:13]: Please run `fastlane frameit download_frames` to download the latest frames
[⠋] Framing screenshot './screenshots/en-US/iPhone 12 Pro Max-0_CalendarsLaidOut.png' [16:36:13]: Unfortunately device type 'Apple iPhone 12 Pro Max' is not available in Pacific Blue, falling back to Graphite...
[16:36:13]: Couldn't find template for screenshot type 'Apple iPhone 12 Pro Max Graphite'
[16:36:13]: Please run `fastlane frameit download_frames` to download the latest frames
[⠙] Framing screenshot './screenshots/sv-SE/iPhone 12 Pro Max-0_CalendarsLaidOut.png' [16:36:13]: Unfortunately device type 'Apple iPhone 12' is not available in Pacific Blue, falling back to Black...
[16:36:13]: Couldn't find template for screenshot type 'Apple iPhone 12 Black'
[16:36:13]: Please run `fastlane frameit download_frames` to download the latest frames

Please run fastlane frameit download_frames to download the latest frames

@everlof this is likely because this PR is also dependent on merging this PR: https://github.com/fastlane/frameit-frames/pull/15
That should fix that issue I think 🤔

In order to fully add support for iPhone 12 Pro and iPhone 12 Pro Max we probably need to add it to another map as well.
This map here that defines a mapping:
https://github.com/fastlane/fastlane/blob/cbfd2724de7b524f680be3e80a708c36297dbf3e/snapshot/lib/snapshot/reports_generator.rb#L87

@everlof could you share what key/value pairs you added to this file to make it work for you (since you already tested it)? 😊
So that we can apply this change to this PR still. 🙏

@rogerluan Here's the fix that solved it for me:
+        'iPhone 12 Pro Max' => "iPhone 12 Pro Max",
+        'iPhone 12 Pro' => "iPhone 12 Pro",

@rogerluan Here's the fix that solved it for me:
+        'iPhone 12 Pro Max' => "iPhone 12 Pro Max",
+        'iPhone 12 Pro' => "iPhone 12 Pro",

But to be clear, I still got the errors above when I tried to use the new device-colour ("pacific blue").

This is because https://github.com/fastlane/frameit-frames/pull/15 is not merged yet. When you execute fastlane frameit download_frames it download the frames from the master branch @ https://github.com/fastlane/frameit-frames/tree/gh-pages/latest, which does not include the iPhone 12 frames yet.
One way to solve it (for now) is:

Find the folder where fastlane keeps the downloaded frames (for me that was /Users/**username**/.fastlane/frameit/latest
Replace that folder with the contents of https://github.com/fastlane/frameit-frames/pull/15/files

@rogerluan Here's the fix that solved it for me:
+        'iPhone 12 Pro Max' => "iPhone 12 Pro Max",
+        'iPhone 12 Pro' => "iPhone 12 Pro",

But to be clear, I still got the errors above when I tried to use the new device-colour ("pacific blue").

This is because https://github.com/fastlane/frameit-frames/pull/15 is not merged yet. When you execute fastlane frameit download_frames it download the frames from the master branch @ https://github.com/fastlane/frameit-frames/tree/gh-pages/latest, which does not include the iPhone 12 frames yet.
One way to solve it (for now) is:

Find the folder where fastlane keeps the downloaded frames (for me that was /Users/**username**/.fastlane/frameit/latest
Replace that folder with the contents of https://github.com/fastlane/frameit-frames/pull/15/files

@googlebot I fixed it.

@googlebot I fixed it.

@nimau could you fix the CLA issues? 🙏

@nimau could you fix the CLA issues? 🙏

@googlebot I signed it!

@googlebot I signed it!

@googlebot I consent.

@googlebot I consent.

@googlebot I consent.

@googlebot I consent.

@googlebot I signed it!

@googlebot I signed it!

@googlebot I signed it!

@googlebot I signed it!

@nimau could you fix the CLA issues? 🙏

Sorry, there is a commit with my work email address. I've add it to my GitHub account and as a secondary email address to my google account, I've signed again the CLA but googlebot still don't want it.
I've no idea on how to fix this myself.

@nimau could you fix the CLA issues? 🙏

Sorry, there is a commit with my work email address. I've add it to my GitHub account and as a secondary email address to my google account, I've signed again the CLA but googlebot still don't want it.
I've no idea on how to fix this myself.

@googlebot I consent.

@googlebot I consent.

@nimau not sure either, maybe add your work email to your GitHub account as a secondary email?
If that doesn't work, you could open a new PR with the same content (but committed by yourself) 😅
Thanks for understanding and getting back to us! 🤗

@nimau not sure either, maybe add your work email to your GitHub account as a secondary email?
If that doesn't work, you could open a new PR with the same content (but committed by yourself) 😅
Thanks for understanding and getting back to us! 🤗

@rogerluan I've just pushed a new PR #17940  (same one with proper @author email address).
I'll cancel this one.

@rogerluan I've just pushed a new PR #17940  (same one with proper @author email address).
I'll cancel this one.

Pull request closed (recreated #17940 with correct @author email address to match CLA)

Pull request closed (recreated #17940 with correct @author email address to match CLA)


ARTEMIS-1832 HAAutomaticBackupSharedStoreTest::basicDiscovery misconfigured

HAAutomaticBackupSharedStoreTest::basicDiscovery is creating
queues on not existing nodes and is not setting up any SessionFactory
on the existing ones.

@jbertram Not sure about it, but it just seems a test configuration issue, makes sense?

Your changes will make the test pass, but the whole class seems incomplete. It looks like a test which was started and never finished.

This test was ignored for a while until it was re-enabled at https://github.com/apache/activemq-artemis/commit/aa730fdaa72b0530a7e5d901c5bf7016b67a35e7

@jbertram @franz1981 I vote to remove this test.. FailoverTest is already testing for Shared storage conditions.. I think this is a dead test.

@clebertsuconic, I agree.

It's gone then.. I'm sending a commit, with a close to this PR


dungeon libraries not working with fairy lights

hello, I found a "compatibility" problem of fairy lights with dungeons libraries, apparently the lights cannot be put because they disappear quickly, but to work again when uninstalling dungeos libraries
info:
dungeons_libraries-1.19.2-3.0.9-beta.jar
fairylights-6.0.0-1.19.2

If you can manage to provide a log, I may be able to get this in for the current round of fixes.


[zh-cn]Update version-skew-policy.md

Oh, it's synced by another PR.

#35664

Thanks, but we have to close this.
/close


feat(requester pays): GCS and S3

Resolves #40

This is a great feature Nico! Can you show an example of how to use it?

For people following along, here's the documentation for:
GCS: https://cloud.google.com/storage/docs/using-requester-pays#storage-disable-requester-pays-python
S3: https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html

Lastly, would you be able to add some documentation to the README?

Done.

Thank you Nico!


Testing: provide a single refresh button test controllers could handle

See: https://github.com/microsoft/playwright-vscode/issues/97 for a screenshot.
Playwright Test extension does a good job at tracking the workspace, but things happen and we have a 'Refresh tests' button in the test view that reloads it, just in case. It seems like Python extension does the same thing for the same reasons. I wonder if we could get a single refresh button that we would all handle. I understand that this necessity suggests imperfections in the extensions and in the test controller, but it also is pragmatic, so why not.
// @connor4312

Sounds like you want #139737 for which the API has finalized in this iteration.


migration table

hi, did u have some example for migration table? i can't find doc explain for migration table

Did you see  https://floor.codes/migrations/ already ?

Thanks for providing a link to the documentation!


Misc doc changes

Besides other changes, this commit ensures the generated HTML doc for
HexDocs.pm will become the main source doc for this Elixir library which
leverage on ExDoc features.
List of changes:

Use common source url
Refactor project config
Update license year
Fix markdowns
Set and use latest ex_doc
Update matching Elixir version
Update gitignore
Add formatter config
Set output format to html
Badge and more badges!
Revise content

Screenshot:

@danhper Any updates on this?


Handling node failures

Currently if a node crashed or shutdown, node status will be unready (failed status). Right after node failure, etcd pod wouldn't be deleted, its phase would be still Running, and status would become unready or unknown.
After some timeout (default 5m), etcd pods would get evicted. Check:

Taint Based Evictions: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ and https://github.com/coreos/etcd-operator/issues/1117
--pod-eviction-timeout: https://kubernetes.io/docs/reference/generated/kube-controller-manager/

There are two problems here: a node could have restarted before eviction, and node unready status is not a good indication of etcd pod health.
Node restart
After node restart, etcd pod would just die because it uses empty-dir to store data and empty-dir is not persistent in this case. See issue  https://github.com/coreos/etcd-operator/issues/1839.
We could solve this store data on more persistent volume. Check:

persistent etcd cluster issue: https://github.com/coreos/etcd-operator/issues/1323
PV etcd data proposal: https://github.com/coreos/etcd-operator/blob/master/doc/design/persistent_volumes_etcd_data.md

Fine-grained health checking and timeout
Even though node unreadiness might indicate etcd pods on it being unhealthy, but this is not fine-granular enough: kubelet could have bug but etcd process is fine, node is fine but etcd process could crash, etc.
For above reasons, we need application level health checking to detect unhealthy etcd processes and add custom toleration policies for unhealthy members.
A simple readiness probe has been added in https://github.com/coreos/etcd-operator/issues/1320 which could be used as health check.
We will need to add custom toleration policies like how long can I tolerate an etcd member being unhealthy and what cases could be tolerated (e.g. data corruption could not). After toleration period, etcd-operator would replace unhealthy members onto other nodes.

When node is cordoned, pods won't get deleted: https://github.com/kubernetes/kubernetes/issues/51333. We might need to take this into account.


[Script]: Lyrics Finder

Aim
The aim of the "Lyrics Finder" script is to provide users with a convenient way to fetch the lyrics of a song by providing the song title and artist name as input. The script will then use an appropriate API or web scraping technique to search for and retrieve the lyrics of the specified song. The lyrics will be displayed to the user, allowing them to easily access and read the song's lyrics.
Details
Input: The script will prompt the user to enter the following input:
Song title: The title or name of the song they want to search for.
Artist name: The name of the artist or band who performed the song.
API or Web Scraping: The script will use an API or web scraping technique to search for the lyrics of the specified song. There are several websites and APIs available that provide lyrics data, and the script can choose the most suitable one for fetching the lyrics.
Error Handling: The script will handle various scenarios gracefully, such as when the input song title or artist name is not found or when there is an issue with the API/web scraping request. It will display a meaningful error message to the user in such cases.
Output: Once the lyrics are successfully retrieved, the script will display the lyrics to the user in a readable format on the console or in a pop-up window.
User Experience: To enhance the user experience, the script may include some features, such as allowing the user to retry the search, providing suggestions for similar song titles, or displaying additional information about the song or artist.
External Libraries: The script may utilize external libraries, such as requests for API calls, BeautifulSoup for web scraping, or other related libraries to streamline the process of fetching the lyrics.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

/assign


Handle Semester Delete Exception

Handle exception which is raised when someone tries to delete a semester for which there's a project present already.

Critical issue, needed sanity check.


Image Overlay with v-for not updating when removing elements from array

As opposed as the v-for v-marker behaviour, in which I can add and remove markers of an array and the map updates accordingly, if I do the same with v-for v-image-overlay and add and then remove the image, the layer won't update and the old image remains rendered forever.
Is there a method for forcing to redraw the map or at least redraw the layer?
Thanks.

I think the good way to manage this is to remove image overlay from layers in the before destroy event.
It's not even well manage for the marker as is it simply hidden and not removed.
Work should be done to test adding/removing components for all components.
Don't have much time for this at the moment.

Hi @fergardi,
Do you have an example reproducing this issue?
The Vue2Leaflet version v0.0.55 includes beforeDestroy methods that should correctly remove ImageOverlay from the map.
Cheers,
Mickaël

@fergardi,
I did some tests around it and it seems to work correctly with the last version of Vue2Leaflet.
Here is the working version with Vue2Leaflet 0.0.55.
Here is the version reproducing the bug with Vue2Leaflet 0.0.53.
I'm closing this for now. Feel free to reopen it if you still have troubles.
Cheers,
Mickaël


Enforce maximum length in generate seed examples

This calculates a maximum number of characters per seed instruction example based on the configured server context size as passed to ilab generate. Before starting the generation, we verify that none of the examples we're going to use exceed this limit. If they do, we fail generation with a helpful error message.
When adding generated responses to our list of seed examples, we do a similar check of the response length. If the response is too long, we skip adding that particular response to our list of seed examples so that we don't end up adding really long machine-generated responses to our seed examples and blowing our context size that way.
Helps #1024 but doesn't entirely fix all sources of exceeding our context.

Marking as draft based on some conversations in Slack where at minimum more documented is needed here on the what/why we're doing this, where these calculations come from, and improvements we need to keep making.

Ok, unmarking this as draft as this should substantially reduce how often we exceed the server's context size. And, at least with the default ilab generate that uses llama_cpp_python, this should entirely eliminate any fatal generation errors from exceeding context size and instead we'll just log a warning when that happens but keep generating.
Things are not perfect in the calculations here, and I tried to leave enough breadcrumbs in the added code comments so that as we continue to improve this based on user feedback/experience others will understand how and why we're calculating the maximum seed example length today.

is this a GA blocker for RHEL AI?

For some additional context on why I use this, I cannot successfully complete any sufficiently long (say 500+ instructions) ilab generate run without this patch. Ultimately, the model ends up exceeding server's context window at some point during the run and the process aborting. With this change, it exceeds the generation window less and recovers gracefully when that happens, as long as the backend server hosting the teacher model is llama.cpp or vLLM.
Theoretically this isn't needed if your teacher model's context window is large enough that you never exceed it. In practice, with 4k and 8k context window teacher models I need this because inevitably one of the generated teacher question and answer pairs is really long and when that randomly gets selected back into my prompt for a future iteration of the generation loop the context window gets exceeded and the client aborts the generation loop.

is this a GA blocker for RHEL AI?

Ibid comment in #1107

This will need changes if #1107 merges, since that greatly expands our system prompt that we'll need to now account for in these calculating when determining the maximum length of seed examples.

I don't have anything else planned here, and the requested changes (squashing that 1 commit into another plus explicitly specifying a small context size in the test vs relying on the default to be small forever) have been made. So, please proceed :)


Fix bug with imported macros and template globals

Fixes #688

Added parameter to _get_default_module to take in the current context and make a new module if template globals are found
Added self.globals to the Context class to differentiate between template variables from render variables.

_get_default_module is sort of misnamed now, since it will get a default module, or a new module for a new import. :thinking:


[DRAFT] #845 Added No. Series Where-Used

Summary
This is a Draft PR. There's still a lot to do.

[x] Adding tables manually (like in the G/L Account) or search for all "Table Relations Metadata" with "Related Table ID" + "Related Field No." set to No. Series / Code (this is my prefered way).
[ ] Fix PageManagement so that the user can open the page from the Where-Used results.
[ ] Obsolete
[ ] Field with TableRelation = No. Series has value or not
[ ] (Optional) Count
[ ] automated tests

Manually transfered from https://github.com/microsoft/BusinessCentralApps/pull/427

Work Item(s)
Fixes #845

Hi @christianbraeunlich,
we've been discussing your PR a little and we're now having some doubts about its validity. While it makes a ton of sense to be able to see where a No. Series is used, we're not sure that this feature should be build in the way it's being built right now. In AI, "where used" is a rather prominent capability, which must be generally available for all entity relationships. You will probably see some advancements in this area in the near future, and I hence think it makes sense to wait to add this capability, until we know what the future holds here.
If you agree, I'd suggest to close this DRAFT for now and pick it up again, once we know more.
What do you say?

I completely 100% agree. Once I moved the code into the business foundation layer, everything felt out of place, and even before that, there's a need for more general functionality that would benefit all the other modules. So a WhereUsed module would make perfect sense. The same goes for the approval workflows imho, but I'll get to that in the otter PR.

Good to hear that  you've made the same observations 😊 Let's see what the future holds!


Text alignment

Thank you for helping out with embedded-graphics development! Please:

[ ] Check that you've added passing tests and documentation
[ ] Add a CHANGELOG.md entry in the Unreleased section under the appropriate heading (Added, Fixed, etc) if your changes affect the public API
[ ] Run rustfmt on the project
[ ] Run just build (Linux/macOS only) and make sure it passes. If you use Windows, check that CI passes once you've opened the PR.

PR description
This PR adds vertical and horizontal text alignment settings to MonoTextStyle. The default vertical alignment is now Baseline instead of Top and all builtin fonts now set the baseline.
I've also changed the implementation of MonoTextStyleBuilder to be more similar to the PrimitiveStyleBuilder. All settings can now be changed using setters and it's no longer required to pass the font to the new constructor.

The docs aren't great and some of this implementation might change when I implement BDF support. But if you find anything that needs additional documentation please add a note to #480 or #511.

I'd prefer to have the explicitly required parameters (font, in this case) to remain in the builder object's constructor. One less thing I can forget about while using the API. Was this change made so that all the style builders have a parameterless new()?

Was this change made so that all the style builders have a parameterless new()?

Yes.

But in this case, since I must specify a font, the actual "constructor" a user has to call in more like MonoTextStyle::new().font(Font). While it's cleaner in terms of "hey, what's that parameter?", I think the API should prevent me creating an invalid style by omitting the font call.

... I think the API should prevent me creating an invalid style by omitting the font call.

What is your definition of an "invalid style"? One that cannot be used at all, because of the type, or one that isn't useful, because it doesn't draw anything?
The API doesn't allow build to be called, if no font was sent previously, so that it isn't possible to build an invalid MonotTextStye. But we could also change the behavior of the builder so that you would always be able to call build by setting a default font. The default font could be a dummy empty font or one of the built in ones. Do you think this would be better?

The API doesn't allow build to be called, if no font was sent previously

Sorry, I missed that. I guess that makes my comment a lot less valid (and my problem a lot more subjective), then. Still, I'd like to ramble some more, just in case I make some sense.
On the objective side, I definitely prefer not allowing to create a style without a font. If something is obviously incorrect, let the compiler complain, instead of surprising the user by drawing nothing. So in this regard, what you made is something I would look for.
(This will probably be a bit weak, as the API is simple enough.) On the subjective side, and thinking as a user, if I have to set a font to draw a piece of text, I would be surprised to see an API that seemingly lets me not do that. I am allowed to write the following piece of code, that is syntactically correct, and not have it compile:
let my_style = MonoTextStyle::new().build();

I would be greeted with a message that (grain of salt applies, I didn't check explicitely and I can't remember these things) build() is not implemented for the MonoTextStyle struct. The error message would, I guess mention UndefinedFont somewhere in the type, but not that I have to call font() to fix the issue. In this regard, I think I would prefer a missing argument error - I think it makes it easier to spot the mistake.

On the objective side, I definitely prefer not allowing to create a style without a font. If something is obviously incorrect, let the compiler complain, instead of surprising the user by drawing nothing. So in this regard, what you made is something I would look for.

We also allow users to build empty PrimitiveStyles (which would be hard to prevent on the type level). So it would also be reasonable to apply the same logic to MonoTextStyle and allow missing a missing font setting. Perhaps setting a default font would be a good compromise. It would draw something, as long as the text_color is set and it should be obvious if the font isn't correct. And this would make sure that build can always be called.

The error message would, I guess mention UndefinedFont somewhere in the type, but not that I have to call font() to fix the issue.

It would be nice to be able to provide a better error message for this, but I don't think that it's possible.

I think I would prefer a missing argument error - I think it makes it easier to spot the mistake.

It would, but I prefer consistency between the builders in this case.
Setting the font in the new constructor would mean that there are two methods of setting the font, which could also be confusing. It would make the API different for new styles vs styles that are based on an existing style:
// with new argument
let style = MonoTextStyle::new(Font6x8).build();
let other_style = MonoTextStyle::from(&style).font(Font12x16).build();

// without new argument
let style = MonoTextStyle::new().font(Font6x8).build();
let other_style = MonoTextStyle::from(&style).font(Font12x16).build();

It [...] should be obvious if the font isn't correct.

I guess there are arguments both for and against a default font, but I don't want to be the one who guesses which font that should be. I would personally go with not providing a default - the iteration time is shorter with a compile error, compared to a manual test ("hmm, that doesn't look right") especially if the text in question is buried under a lot of necessary interactions.
Let's leave this as is, then and thank you for explaining your reasons :)

I would personally go with not providing a default

Agreed

@jamwaffles Is there anything I can do to help to get this merged? If you don't have time to review it at the moment I can find other things to work on, but the text improvements are blocked by this PR.


Please enable GitHub discussions for Q/A

odmantic is just awesome. rather magical!
but new users like me have lots of things to ask from time to time. I think Gh discussions is a better place than gitter for specific Q/A. Otherwise, for casual chat or general talks, gitter is fine.
For gh disc, You just need to tick a box (enable from repo settings), nothing else. For more info https://docs.github.com/en/discussions/quickstart
Imo Benefits of gh disc:

questions don't get lost in conversations
you know how many questions are not yet answered
stack overflow styled "accept as answer"
issues that are not bugs/feature requests can be converted into discussions
new issue can be created easily from discussions that talk about a bug/feature request
gh discussions integrate and plays well with the gh ecosystem
personally, I feel it more natural and easy to read. things tend to get lost in (discord/slack/gitter) style

Thanks a lot for spending your time reading my request.
thanks again 😊🙏
Also thanks a lot to @AntonDeMeester for helping me out on gitter chat !

Thanks a lot for everything !
I enabled GH discussions, still need to make some communication about it on the docs and readme but feel free to use it 😄


Firmware Initialization, Project Structure setup and DWM3000 API setup

This PR includes the following

Initializing the firmware and code to test USB Serial debugging and reading DWM3000 device ID through SPI
Setting up project structure, inspiration and structure taken from platform-espressif examples
Setup the DWM-3000 API provided by Makerfabs

Proof of working:

Prints Device ID every 10 seconds

Ran the branch on my device and it was working fine. Only comments are:

Lines 11, 20, and 23 of READ.ME

Line 33 of hello_world_main.cpp, should have \n at the end of the print statement


How to use QRscanner with typescript Angularjs web application ???

Hi all,
from the documentation i couldn't get exactly,
how to make use of this library after installation of this package under angularjs web application
w.r.t. "@angular/cli": "~7.1.0",
here documentation shows with javascript usage,
but withlatest angularjs we need to use with typescript, which is not shared here,
please let me know if anybody have ideas, as i am new to this technology.
thank you

So the library is written in typescript so it should "just work". Can you not import it like described here - specifically
import jsQR from "jsqr";

We use typescript at my employer and importing it like this works correctly.

Closing this issue due to lack of activity - @vasuvuggu if you're still having issues and can provide more details to help debugging please comment/re-open.


Ui Issues - Home Screen

PFA

,

@summikhan11 @antuz123 is there a figma file for the designs I can look at? so I get the correct dimensions?

we use xd, I'll attach a link here
https://xd.adobe.com/view/be4bd2ea-118c-4aff-959f-e3243e25ca8f-eb18/screen/0e3ab21b-d16c-4387-a762-2251d4675ddf/

thanks

I don't see this fixed in dev app 2.0.68 (418)

Verified this issue on dev app v2.0.75(469)


Missing sender IP

You are sending inbound mail from <IP_ADDRESS>/16 but only <IP_ADDRESS>/15 is mentioned in the Docs.
You should update the documentation

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

ID: 077406d8-bff1-496e-3ea2-b38558fd9355
Version Independent ID: 57db3dec-2250-2dee-fd1a-ec6656911798
Content: Office 365 URLs and IP address ranges
Content Source: Enterprise/urls-and-ip-address-ranges.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@Bernskov I have forwarded this information to the product team, who will evaluate and update the address ranges as needed in the next update. Thanks for letting us know.


Add tests for shorthand

Description
When searching for if a shorthand has been used, the order of the search is important. As an example: in typst-syntax/src/lexer.rs, the rows
            '<' if self.s.eat_if("-->") => SyntaxKind::Shorthand,
            '<' if self.s.eat_if("--") => SyntaxKind::Shorthand,

must be in this order, else the shorthand for "⟷" will be converted to "⟵>".
Use Case
Tests ensures that changes such as adding more shorthands or rewriting code will not break anything.

More tests could be added here: https://github.com/typst/typst/blob/main/tests/typ/compiler/shorthand.typ


Update ngx-bootstrap

The current ngx-bootstrap dependency is locked at 1.8.0. This is because our unit tests break with version 1.9.3. That is, anything that tests an ngx-bootstrap drop down.
We had a problem with this before and added fixture.detectChanges() before each test as a workaround. That forces the drop down to render. Otherwise, the drop down is not available and the test fails. Essentially, the previous workaround is no longer valid.
In order to update ngx-bootstrap to use versions '^1.8.0', we would have to fix our unit tests first.

Oops, forgot to close this issue! The two PR's mentioned above resolved it.

please i am having this issue BsDropdownConfig as a provider  on ngx-bootstrap 6.0.1, I need help in resolving it


[KYUUBI #3688] add rest_api and kyuubi-admin docs for admin delete/li…

…st engine operation

Why are the changes needed?

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

@turboFei

thanks @lightning-L , @Yikf @yaooqinn , merging to master


Fails to validate Bee Waggle data

Hi,
upon running "make", I am getting the following error:
tcpd.bee_waggle_6.ValidationError: Validating the file './datasets/bee_waggle_6/bee_waggle_6.json' failed.
Please raise an issue on the GitHub page for this project if the error persists.
make: *** [collect] Error 1
Can I do this dataset manually?

BTW, bee waggle is the only one failing! I successfully got the rest.

Hi @siamakz, thank you for your interest in the dataset and thanks for reporting this issue! This is really helpful. There are a few possible things that could cause this error. I'd appreciate your help in tracking it down so I can improve the script for everyone.
First, was the psslds.zip file downloaded correctly? It should be in the datasets/bee_waggle_6 directory. If it's not, please see the steps below under "downloading psslds.zip". If it is, you can run python get_bee_waggle_6.py and it should generate the bee_waggle_6.json file.
If this still fails, it might be because of rounding errors. Could you upload the resulting bee_waggle_6.json file (you can attach a file to your comments here on Github)? You may need to remove the @validate(MD5_JSON, MD5_JSON_2) line from get_bee_waggle_6.py and run the script again.
Downloading psslds.zip
You can manually download the dataset by following these steps:

Download the psslds.zip file from this url: https://web.archive.org/web/20191114130815if_/https://www.cc.gatech.edu/~borg/ijcv_psslds/psslds.zip
Place the file in datasets/bee_waggle_6
Go to that directory (cd datasets/bee_waggle_6) and run python get_bee_waggle_6.py. If you've used virtualenv make sure to activate that first. This should generate the bee_waggle_6.json file.

Please let me know if the steps above worked! In the meantime I'll try to find out how to make this process more robust.

Hi @GjjvdBurg. Thanks for your great effort for this truly needed benchmark!
The zip file is downloaded but get_bee_waggle_6.py still raises the same error. Github doesn't allow me to attach a json file. However, here is a couple of lines (copied from different places) from it, if this helps with checking rounding error:
"label": "y",
"type": "float",
"raw": [
300.0,
297.745134994,
290.737164696,
293.705045364,
"label": "sin(theta)",
"type": "float",
"raw": [
-0.7682212795972521,
-0.8013976703636214,
-0.629299000646184,
"label": "cos(theta)",
"type": "float",
"raw": [
0.6401843996646285,
0.5981319034592291,
0.7771632825769074,
0.6302977772506493,

Thanks for the swift response! Good call on adding a few lines! The value  0.5981319034592291 is 0.598131903459229 in my version, so that's probably the cause of the error.
Could you email me the json file? I can then add it as a alternative outcome to the script. My email is on my website.
I'm preparing a Dockerfile which should be a more reproducible way of recreating the exact dataset, and I'll look into dealing with these rounding errors from within Python as well. Thank you!

Sure! Just sent it to you. Thanks for looking into it!

Thanks again for reporting this issue @siamakz! I've added your file as a possible outcome of the script, with a note that there are minor differences due to rounding. I've further replaced the validation error with a warning, as I expect other systems will have yet other possible rounding outcomes.


Misspelling

Hi
I saw DALI 3 written in the text
I assume it should be DALL-E 3

Thanks, corrected.


İm Cannot Send Message

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshot or app console output
If applicable, add screenshots to help explain your problem.
Whole command used to start the app
Please insert the whole command you used to start the app.
Censoring ip address is recommended.
Additional context
Add any other context about the problem here.

Please follow the steps in the template or I will delete this issue.


Uncaught Error: EISDIR: illegal operation on a directory, read

[Enter steps to reproduce below:]

...
...


[Feature] Option to disable sorting for a table widget column

Summary
Option to disable sorting for a table widget column
Additional Context
On sort the selected row state is lost

The solution should be to not lose selected row state not to disable sorting right? @rishabhsaxena

The solution should be to not lose selected row state not to disable sorting right? @rishabhsaxena
Actually, I wasn't sure if it makes sense to keep the selected index same as the previously selected one after sorting. Or if resetting on sorting is a feature.

#5640 already addressing this. Can we close this?


failed to list packages and views in newly created feeds

As far as I know, Microsoft changed the scope of Azure Artifacts feeds from sometime in Nov2019. By default, the newly created feeds are project-scoped, only when the project is made public, its scoped feeds become public.
Details can be seen from https://docs.microsoft.com/en-us/azure/devops/artifacts/feeds/project-scoped-feeds?view=azure-devops
Given that, this task needs to be updated to adapt to that change.

+1

I still see the feed in the project feed. Can you explain a bit more what you mean?

Hi,
I'm seeing a similar issue. Newly created feeds are automatically set as 'Project scoped' on creation (I can't seem to find a way to change this). The 'Release Views' dropdown in the step is not populated for these feeds. I also tried to manually enter the name of the desired view instead of selecting it but this causes the following error when executing the release:
System.Net.WebException: The remote server returned an error: (404) Not Found.
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()at Get-FeedId, D:\a\_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\2.0.5\vsts-promotepackage-task.ps1: line 46
at Set-PackageQuality, D:\a\_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\2.0.5\vsts-promotepackage-task.ps1: line 135
at Run, D:\a\_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\2.0.5\vsts-promotepackage-task.ps1: line 280
at <ScriptBlock>, D:\a\_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\2.0.5\vsts-promotepackage-task.ps1: line 286
at <ScriptBlock>, <No file>: line 1
at <ScriptBlock>, <No file>: line 22
at <ScriptBlock>, <No file>: line 18
at <ScriptBlock>, <No file>: line 1

Is the release views dropdown not populated in the project where the feed is created or another project ?
Verstuurd vanaf mijn iPhone
Op 18 dec. 2019 om 15:37 heeft Wouter Roos<EMAIL_ADDRESS>het volgende geschreven:

Hi,
I'm seeing a similar issue. Newly created feeds are automatically set as 'Project scoped' on creation (I can't seem to find a way to change this). The 'Release Views' dropdown in the step is not populated for these feeds. I also tried to manually enter the name of the desired view instead of selecting it but this causes the following error when executing the release:
System.Net.WebException: The remote server returned an error: (404) Not Found.
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()at Get-FeedId, D:\a_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\2.0.5\vsts-promotepackage-task.ps1: line 46
at Set-PackageQuality, D:\a_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\2.0.5\vsts-promotepackage-task.ps1: line 135
at Run, D:\a_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\2.0.5\vsts-promotepackage-task.ps1: line 280
at , D:\a_tasks\rvo-vsts-promotepackage-task_7ca5869f-a901-4012-a50d-d0f9d436ffec\2.0.5\vsts-promotepackage-task.ps1: line 286
at , : line 1
at , : line 22
at , : line 18
at , : line 1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frenevanosnabrugge%2Fvsts-promotepackage-task%2Fissues%2F38%3Femail_source%3Dnotifications%26email_token%3DABOH2WWB6RIQMDROIG46UG3QZIYR7A5CNFSM4JTPBWY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHGJ4AQ%23issuecomment-567057922&data=02|01||527edf4cd8da494e9a0a08d783c7c9de|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637122766410697645&sdata=xPghA%2FC9rS0aKkh4Kfkr9u1%2BoJ%2FFf2tWyFe218FDkUY%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABOH2WQQXDSJE5DDR6OSQHLQZIYR7ANCNFSM4JTPBWYQ&data=02|01||527edf4cd8da494e9a0a08d783c7c9de|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637122766410707656&sdata=qSC1E2XyuLFLUKzBCxhVYM%2FXkoAZUQPEpi86Z6YqqKw%3D&reserved=0.

Same project.

Ok. I managed to reproduce the issue. However, I feel it is an issue with the MS task lib.  https://github.com/microsoft/azure-pipelines-extensions/blob/master/docs/authoring/endpoints/tfs-vsts-endpoints.md
In the code I refer to
"endpointId": "tfs:feed",
"endpointUrl": "{{endpoint.url}}/_apis/packaging/feeds",
Endpoint should contain the url with ""project" in it. If this is the case, it all works.. I am raising an issue with MS

https://github.com/microsoft/azure-pipelines-extensions/issues/755

Even if the feed url for the task.json was proper, the powershell script does not account for the adjustment in the url.
I created a local (private) copy of the extension for testing and it seems to work, with the exception that the release drop down still does not populate. I'll create a pull request so that the script itself at least works.

I'm  not sure how to go about contributing my changes, I don't seem to have permissions to create a new branch so that I can make a pull request.

Create a fork and make a PR
Thanks !!
Verstuurd vanaf mijn iPhone
Op 3 jan. 2020 om 15:30 heeft amrock-my<EMAIL_ADDRESS>het volgende geschreven:

I'm not sure how to go about contributing my changes, I don't seem to have permissions to create a new branch so that I can make a pull request.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frenevanosnabrugge%2Fvsts-promotepackage-task%2Fissues%2F38%3Femail_source%3Dnotifications%26email_token%3DABOH2WVROWPXTTFOWK4EYSDQ35DWVA5CNFSM4JTPBWY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIBHTZQ%23issuecomment-570587622&data=02|01||46c030695f35479a2af908d790596c13|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637136586047318200&sdata=Biq9Q8%2BO7zvQ%2Fp7BNh148MHDrMGL0xVdLeR6ZQDUiDY%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABOH2WWWWBKZZU3SZABK7R3Q35DWVANCNFSM4JTPBWYQ&data=02|01||46c030695f35479a2af908d790596c13|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637136586047328211&sdata=bpwXsyWfv4Lj1%2BrbMDPtmdbKldoXmC5%2BcLLKMDbiszI%3D&reserved=0.

Fixed in the UI now too.

Fixed in
https://github.com/renevanosnabrugge/vsts-promotepackage-task/pull/54

@renevanosnabrugge Great, thanks!


Where are .NET Event Source stored?

This needs more information. I have a Windows VM, I've set up the Azure Diagnostics extension, I'm running a simple console app that writes some events using the EventSource class but those events are nowhere in the selected storage account.

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

ID: 0d1ee470-5d0c-4281-edac-d3b88287caab
Version Independent ID: c3eb4829-1139-b5e8-7e18-960c2cbcc652
Content: Overview of the Azure Diagnostics extension
Content Source: articles/azure-monitor/platform/diagnostics-extension-overview.md
Service: azure-monitor
GitHub Login: @rboucher
Microsoft Alias: robb

@eparizzi Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@eparizzi are you looking in the tables as called out in https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostics-extension-to-storage ?  I can add something to the docs if we have another table, but if they are not appearing at all you'll need to contact support.

I see the following tables in the Storage account set:

This page says that .NET Event Source can be collected. But I don't see any table for them.

Hi @eparizzi
Sorry for the long wait.
If you configure WAD to collecting eventsource or tracelogging events, you should see a container that contains the event name in the config if you are using the JSON blob format.
If you use XML format,

the table name should be based off the configured eventName and prefixed with "WAD". If the configured event name is TraceEvents, the storage entity should be WADTraceEvents.

If you do not supply an eventName (it's optional) the code hashes the provider name to build the event name. Therefore, we encourage you to add it so events don’t get logged using hard to read md5 hashes.

XML example.
Notice the eventName="ServiceFabricReliableServiceEventTable"
  <EtwProvider duration="PT5M" name="Microsoft-ServiceFabric-Services" format="EventSource">
    <AdditionalHeaderFields>
      <Field>RelatedActivityId</Field>
    </AdditionalHeaderFields>
    <DefaultEvent storeType="Central" priority="Normal" retryTimeout="PT60M" diskQuotaInMB="2152" dontUsePerNDayTable="true" dontUseNPartitionSpread="true" eventName="ServiceFabricReliableServiceEventTable" />
  </EtwProvider>

Vs some config where you leave the eventName blank and the code adds this..

That said, I'm wondering if the events are in the storage account somewhere.  If not, I would suggest going through this article https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostics-extension-troubleshooting

Reopen this issue if this is still a problem.

#please-close

Closing as per comments


[HOLD for payment 2023-06-28] [$1000] When sending h_ello_ , only ello is sent

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

Action Performed:

Open ND
Open any chat and send message h_ello_

Expected Result:
Normal text h_ello_ is sent
Actual Result:
Italic text ello is sent
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

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

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

Version Number: 1.3.22-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/b6d473ed-21e9-44c9-b7b2-7bddf3a96307
https://github.com/Expensify/App/assets/43996225/0c023e07-cdaa-487a-929e-3ca170fe5b57
Expensify/Expensify Issue URL:
Issue reported by: @s-alves10
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1685635565083259
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0182558b3d97b80b80
Upwork Job ID:<PHONE_NUMBER>552652288
Last Price Increase: 2023-06-05

Proposal
Please re-state the problem that we are trying to solve in this issue.
When sending h_ello_ , only ello is sent.
What is the root cause of that problem?
The root cause of this issue is that the regex
/(?!_blank")[^\W_]?_((?![\s_])[\s\S]*?[^\s_])_(?![^\W_])(?![^<]*(<\/pre>|<\/code>|<\/a>|_blank))/g

of italic rule match a character of [a-zA-Z0-9] through regex piece [^\W_]? before the italic syntax.
See regex test screenshot below

What changes do you think we should make in order to solve the problem?
To fix this issue we can use a capture group to wrap [^\W_]? and save the character captured back to the start of the  tag.
We can change  the regex
/(?!_blank")[^\W_]?_((?![\s_])[\s\S]*?[^\s_])_(?![^\W_])(?![^<]*(<\/pre>|<\/code>|<\/a>|_blank))/g

of italic rule to
/(?!_blank")([^\W_]?)_((?![\s_])[\s\S]*?[^\s_])_(?![^\W_])(?![^<]*(<\/pre>|<\/code>|<\/a>|_blank))/g

So, the group 1 is the legal character before italic syntax and the group 2 is the text of italic syntax, see regex test screenshot

We also change the replacement method from
replacement: (match, g1) => (g1.includes('
') || this.containsNonPairTag(g1) ? match : `<em>${g1}</em>`),

to
replacement: (match, g1, g2) => (g2.includes('
') || this.containsNonPairTag(g2) ? match : `${g1}<em>${g2}</em>`),

By doing so, the input
h_ello_

is translated into html
hello

and won't break existing unit test cases of expensify-common.
What alternative solutions did you explore? (Optional)
N/A

@eh2077 We shouldn't parse h_ello_. It should be sent as is.

@s-alves10 Yes, I was just doing markdown syntax comparing on other Apps. Many of them, like Slack and Github don’t parse it. So I covered it if we don't want to parse it also.

@eh2077 I feel it should be reverted back to /(?!_blank")\b_((?!\s).*?\S)_\b(?![^<]*(<\/pre>|<\/code>|<\/a>|_blank))/g which was there in older version of expensify-common. Old regex match only when word starts and ends with _  otherwise not.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01b7fc496875b2b3dd

Reproduced and added External label.

@tjferriss thanks for the ping! I’ll give it feedback soon!

@tjferriss @amyevans I have tested the @eh2077 and the proposal looks good to me!
🎀 👀 🎀 C+ reviewed!

Bump @tjferriss @amyevans

Hi @amyevans, I'm waiting for assignment if you agree with @mollfpr 's https://github.com/Expensify/App/issues/20111#issuecomment-1582814669
I also pre-prepared a PR https://github.com/Expensify/expensify-common/pull/546 for Expensify-common FYI.

Apologies for the slow response! The proposal looks good, I'll get the correct assignees onto the PR for review.

Not overdue - expensify-common PR has been merged and App PR is being drafted

It looks like we're just waiting for this PR to hit prod https://github.com/Expensify/expensify-common/pull/546

[@mollfpr] The PR that introduced the bug has been identified. Link to the PR:
[@mollfpr] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

I don't think we have offended PR. Instead, this is an improvement.

[@mollfpr] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

The regression step should be enough.

[@mollfpr] Determine if we should create a regression test for this bug.

Yes!

[@mollfpr] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression step:

Open a chat with any user
Send a message h_ello_ to the user
Verify that the message sent is h_ello_ and not display as italic
Send a message _he_llo__ to the user
Verify that an underscore in the first and last of the word is omitted and the message sent is he_llo_ in italic
👍 or 👎

Shouldn't the automated tests be sufficient to catch any regressions in this case, instead of introducing a manual regression test?

Friendly bump @tjferriss

@s-alves10  = $250
@mollfpr  = $1000 (no bonus based on this)
@eh2077 = $1000 (no bonus based on this)
I'll send out the offers in UW.

@mollfpr and @eh2077 I can't find you in UW can you send me your profile name here? Thanks!

Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:

when @eh2077 got assigned: 2023-06-12 17:23:34 Z
when the PR got merged: 2023-06-15 14:24:40 UTC
days elapsed: 3

On to the next one 🚀

@flaviadefaria Thanks for checking the payment. I think bonus should be applicable based the timeline above. It looks like Kelvin had a bug then. Can you search Eric Han for my UW profile?

Can you search Eric Han for my UW profile?

I did and couldn't find it, can you link it here?

@flaviadefaria Here's the link https://www.upwork.com/freelancers/~0184a9d594d4a0e25a

https://www.upwork.com/freelancers/~01de3ccafd86e0bce0

Offers sent, I'll add the bonus once the offer is accepted.

Accepted the offer, thank you @flaviadefaria

@flaviadefaria  Accepted the offer thanks!

Paid!

@flaviadefaria
I wasn't paid for this issue. I'm the issue reporter

I'll close this again now and will pay you as soon as you accept the offer :)

@flaviadefaria
Offer accepted. thanks


Commit 573617a breaks pip installation

Summary
The lookup of requirements.txt breaks pip.
Reproduction Steps
pip install github
Yields:
  Downloading github-1.2.6.tar.gz (14 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [18 lines of output]
      Traceback (most recent call last):
        File "/Users/flow3d/work/env/newco/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
          main()
        File "/Users/flow3d/work/env/newco/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/Users/flow3d/work/env/newco/lib/python3.8/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 130, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/private/var/folders/2k/2z863nrj47s2myzfzgccq6b80000gn/T/pip-build-env-qoa8uz88/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 177, in get_requires_for_build_wheel
          return self._get_build_requires(
        File "/private/var/folders/2k/2z863nrj47s2myzfzgccq6b80000gn/T/pip-build-env-qoa8uz88/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 159, in _get_build_requires
          self.run_setup()
        File "/private/var/folders/2k/2z863nrj47s2myzfzgccq6b80000gn/T/pip-build-env-qoa8uz88/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 281, in run_setup
          super(_BuildMetaLegacyBackend,
        File "/private/var/folders/2k/2z863nrj47s2myzfzgccq6b80000gn/T/pip-build-env-qoa8uz88/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 174, in run_setup
          exec(compile(code, __file__, 'exec'), locals())
        File "setup.py", line 4, in <module>
          with open('requirements.txt') as f:
      FileNotFoundError: [Errno 2] No such file or directory: 'requirements.txt'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.```

### Minimal Reproducible Code

_No response_

### Expected Results

package installed

### Actual Results

package not installed

### Checklist

- [X] I have searched the open issues for duplicates.
- [X] I have shown the entire traceback, if possible.
- [X] I have removed my token from display, if visible.

### Additional Context

_No response_

seems to work now on my end


Sources for the website?

Hi, nice lib, does the netlify site have a public repo as well? The code examples look broken.

Aha, I see it is in the v2 branch. Above issue only in Firefox btw, Chrome renders the code just fine.


Update requirements.txt

temp patch for altair v4 for streamlit as v5 is incompatible

Looks like it worth to update accelerate as well: https://github.com/abhishekkrthakur/diffuzers/issues/31#issuecomment-1809651194


Queries Regarding functionality of extra_mask

Hi @qkaren
Thanks for open-sourcing the code
I am a little confused regarding why an extra mask is needed as it contains the position ids for the non-stop words in z/ zz while the y_logits vector has been created wrt to x. Why are the two are being combined? Whats the exact use of extra_mask ?
Following the reference code lines
https://github.com/qkaren/COLD_decoding/blob/15476186bb2590375fd5af9e0bbc9db654931d60/cold_decoding.py#L163-L166
https://github.com/qkaren/COLD_decoding/blob/15476186bb2590375fd5af9e0bbc9db654931d60/cold_decoding.py#L241
Thanks!

Thanks for the question. The extra_mask is to implement this description below Eq.(6) in the paper:
In practice, to ease the satisfaction of certain constraints (e.g. n-gram similarity), we expand the candidate set V^k_t
to include constraint tokens.


feat(tutorial): complete step 2 - Austin

complete step 2

👍 Looks good - I have recorded your completion of this step!


BUG: _retry_read_url retries connection even if successful

this should be posted in https://github.com/pydata/pandas-datareader instead.


Issue with theme

for the last couple weeks I had to remove this from rofi because I was getting css errors.
"Failed to resolve variable 'urgent-foreground' in: element normal urgent { text color: var (urgent foreground);}
something similar ignore typos because I had to copy this manually.

Hi, I'm the maintainer of the project.
I haven't had time to look into it recently, this has been a recurring problem in the last few months, Rofi has constantly been changing it's API so the theme is constantly breaking.
I'll see what has to be changed.

@RaphGL thank you, let me know if you can fix it so I do a pull with the changes. thanks

Hi, @r3k2. Sorry for the very late reply. I've tried it on rofi 1.7.3 and everything seems to be working fine. does the problem still persist for you?

I started getting this error today on rofi 1.7.4-1

I fixed it by defining  urgent-foreground: @drac-red; to the list of variables


Hotfix to reinstate old notification class

Task/Issue URL: https://app.asana.com/0/361428290920652/1118493496977133
Description:
Hotfix to reinstate old notification class, fixes java.lang.ClassNotFoundException.
@CDRussell I'm releasing this as an asap hotfix so I'm sending it to you for retrospective review. No rush to review though, it can wait until your return.
Steps to test this PR:

Run version 5.20.0 of the app, setting notification in NotificationScheduler time to 1 minute
Install (but do not run!) this version over the top
Wait a minute, notification should show. Same test with 5.21.1 leads to a background crash.

Internal references:
Software Engineering Expectations
Technical Design Template

Merged via git/flow release.


ENH: Add per-user crypto factories.

Adding simple implementations of the notebook encryption/decryption interfaces, allowing straightforward use just by providing an encryption password. Also adding a test for the new functions.

The Travis failure (iPython 4 only) appears to be a general problem whenever the iPython 4 test is run. I get it on my machine when testing master.

LGTM


Img2Vid workflow

Hi,
I've been exploring your txt2img workflow and it's great! I'm curious, is there a feature for converting an image into a video? Looking forward to any info on this.
Thanks for your amazing work!

The best way to do it is to use ComfyUI for different flows
You can use sparseCtrl model to inject an initial image


MySQL 2 Hive operator

@askeys @artwr @jeremyclover
New operator. The HiveCliHook.load_file method should be pretty useful too

@mistercrunch this looks very useful.  It would be good to make it clear in the docs that this stores the table as a textfile, and so typically you would add another hive operator to create a faster table.

@askeys I took the time to improve the docs
I'm happy with how HiveCliHook.load_file should be useful on its own and gets reused for all the ".*ToHiveTransfer" operators.

Efficiency :+1:

Good catch, I meant it to be a comma assuming the adhoc csv use case for the hook. I'll replace by a comma now. The default for the operator is ^A (chr(1))

@artwr , I push a commit straight to master here:
https://github.com/mistercrunch/Airflow/commit/d01c4c8560f520c9c9755026cf88a7baff6300e3


Setting user in test cases

Is there a simple method to set the user for test cases? Currently I'm using django.test.TestCase and it used to be possible to use self.client.force_login(...). A workaround that I've found is subclassing the following helper library. It follows the style used by Graphene's GraphQLTestCase class
from django.test import TestCase
from django.contrib.auth import get_user_model
from strawberry.channels.context import StrawberryChannelsContext
from strawberry.channels.handlers.http_handler import GraphQLHTTPConsumer

class GraphQLTestCase(TestCase):
    def setUp(self):
        # Reset logged in user
        self.user = None
        super().setUp()

    def query(
        self,
        query,
        operation_name=None,
        input_data=None,
        variables=None,
        headers=None,
    ):
        # Only handling query. Other parameters to be handled
        request = GraphQLHTTPConsumer(schema)
        request.scope = {"user": self.user} if self.user else {}
        context = StrawberryChannelsContext(request=request)
        response = schema.execute_sync(query, context_value=context)
        return response

    def setQueryUser(self, user) -> None:
        self.user = user

class OrganizationTestCase(GraphQLTestCase):
    def setUp(self):
        self.user_a = get_user_model().objects.create(id=uuid.uuid4(), username="UserA")
        self.user_b = get_user_model().objects.create(id=uuid.uuid4(), username="UserB")
        self.setQueryUser(self.user_a)

    def test_organization_query(self):
        base_query = """
        { allOrganizations { edges { node {
            id, isUsersActive, createdAt, modifiedAt
        } } } }"""

        response = self.query(base_query)
        self.assertFalse(response.errors)

# extract of types.py
@gql.django.type(Organization, filters=OrganizationFilter)
class OrganizationGQLNode(relay.Node):
    name: gql.auto
    created_at: gql.auto
    modified_at: gql.auto

    @gql.django.field
    def is_users_active(self, root: Organization, info: Info) -> bool:
        """Whether this is the user's active organization."""

        user = info.context.request.scope["user"]
        return root.pk == user.profile.active_organization_id

    @classmethod
    def get_queryset(cls, queryset: QuerySet[Organization], info: Info):
        return queryset.by_member_of(info.context.request.scope["user"].pk)

I'll share with you something I use in my projects:
class GqlTestClient(BaseGraphQLTestClient):
    async def request(
        self,
        body: dict[str, object],
        headers: dict[str, object] | None = None,
        files: dict[str, object] | None = None,
    ):
        path = "/api/graphql/"

        kwargs: dict[str, object] = {"data": body, "headers": headers or {}}
        if files:
            kwargs["format"] = "multipart"
        else:
            kwargs["content_type"] = "application/json"

        return await self._client.post(path, **kwargs)

    async def query(
        self,
        query: str,
        variables: dict[str, Any] | None = None,
        headers: dict[str, object] | None = None,
        asserts_errors: bool = True,
        files: dict[str, object] | None = None,
    ) -> Response:
        body = self._build_body(query, variables, files)

        resp = await self.request(body, headers, files)
        data = self._decode(resp, type="multipart" if files else "json")

        response = Response(
            errors=data.get("errors"),
            data=data.get("data"),
            extensions=data.get("extensions"),
        )
        if asserts_errors:
            assert response.errors is None

        return response

    def _build_body(
        self,
        query: str,
        variables: dict[str, Any] | None = None,
        files: dict[str, object] | None = None,
    ) -> dict[str, object]:
        if variables is not None:
            variables = _resolve_input_types(variables)

        return super()._build_body(query, variables, files)

    @contextlib.asynccontextmanager
    async def login(self, user: User):
        await sync_to_async(self._client.force_login)(user)
        yield
        await sync_to_async(self._client.logout)()

I use ASGI, so I had to adapt it to support async. The main part for you is the login function, which in case you are not using ASGI you can define it as a sync context manager.
Then use it with async with self.login(user):, and while inside that context all calls to the api will be authenticated

Looks really helpful. Might open an MR to add it to the library to help others test their APIs

What happens in the _resolve_input_types method?

Haha, just found the BaseGraphQLTestClient class :joy: Hadn't seen it in the documentation or examples :sweat_smile: Here's a link if anyone else is looking: https://github.com/strawberry-graphql/strawberry/blob/main/strawberry/test/client.py


Added New Contributors Page

Description
This PR introduces a new Contributor Page designed to showcase contributors to the project. The page is built with responsiveness in mind, ensuring a seamless experience across both desktop and mobile devices. Additionally, the design is compatible with both light and dark modes, maintaining visual consistency regardless of user preferences.

Closes #820

Features

Responsive Design: The layout adjusts fluidly to different screen sizes, enhancing usability on both desktop and mobile devices.
Light and Dark Mode Compatibility: The page automatically adapts its color scheme based on the user's selected theme, providing a consistent user experience.
Consistent Design: The design follows the specifications provided for uniformity across the application.

Changes Made

Revampedcontributors/pages.tsx
Revamped ContributorCard.tsx component.
Added CSS styles for responsiveness and theme adaptation.

The given design

Video
https://github.com/user-attachments/assets/cb4e9939-5978-464d-8985-6a1283138d43
Checklist

[x] Code is clean
[x] Responsive design is implemented and tested.
[x] Light and dark mode compatibility is ensured.

@mdazfar2 hope you like the implementation, and please mention if you have any other issue up for grab. Happy to contribute :)

Hey @IkkiOcean Right now, there is a deployment error with your pull request. Please check the screenshot below as proof.
When I merged your PR, the changes didn't reflect on our deployed site. Did you check npm run lint while committing?
I hope you read our contributing guidelines.

Hey @IkkiOcean Right now, there is a deployment error with your pull request. Please check the screenshot below as proof.
When I merged your PR, the changes didn't reflect on our deployed site. Did you check npm run lint while committing?
I hope you read our contributing guidelines.

I will fix it right away, it's a minor bug

@mdazfar2 check now

@IkkiOcean Wow, that's amazing! You created exactly what I wanted, but there are a few changes needed. I'll explain below.
Write Open-Source Contributor everywhere instead of contributions number which you kept Check out the screenshot below for better understand.

And one more thing, add some space between the username and the profile pic, and just write Contributions 135. Make sure not to create any boxes; simply write Contributions with the number for each contributor, fetched from GitHub. Check out the screenshot below for reference.

And kindly convert all the images to .webp format.

[!NOTE]
And Vivek, the most important thing is that the fetching doesn't seem to be working correctly from the GitHub contributors. Please check our contributors after clicking the Contributors button. Open our Ezyshop repository, click on Contributors, and then compare it with your fetched contributor page which you create now. I hope you find what I noticed. See the screenshot below.

Add a hover effect on each contributor's profile image, and make sure that clicking on a profile redirects to the contributor's GitHub profile. Hope you understand.

& write valid commit message.

Don't worry take your time to complete all these.

@mdazfar2 okay. I dont know whats wrong with the GitHub api to fetch contributors list but I will try to fix it, and the other issues you mentioned

one more thing:
you want structure like this right:

Contributions 135
Name of the contributor
Open Source Contributor

Exactly @IkkiOcean, but there is no box for contributor 135. Just write it simply and add a cursor pointer on it.

one more thing:
you want structure like this right:

Contributions 135
Name of the contributor
Open Source Contributor

Exactly @IkkiOcean, but there is no box for contributor 135. Just write it simply and add a cursor pointer on it.

and cursor pointer redirecting to GitHub profile on clicking? sam with the profile pic right?

and cursor pointer redirecting to GitHub profile on clicking? sam with the profile pic right?

No @IkkiOcean, it should open every contributor's page to show what type of things they contributed. Check out the link below for reference.
https://www.helpopshub.com/team

When you open the link above, scroll down and click on "Contributions." You’ll understand. I’m also sharing a screenshot below showing where to check after clicking.

Let me know if there is any queries regarding this.

https://github.com/user-attachments/assets/1657bb90-0891-4702-9a9c-36f184d528d7
Updates:

Profile hover effect with redirection on click
"Open-Source Contributor" Label
Clicking on contributions redirects to the commits of the contributor.
@mdazfar2 check it now.

@mdazfar2  I will find out about the issue you are facing with GitHub providing old data through the api tomorrow. For now, if you dont have any issue with the implementation, please merge it. Hope you liked it.

@IkkiOcean It is nice, but give more space between "Contributions" and the contributor's name.

@IkkiOcean It is nice, but give more space between "Contributions" and the contributor's name.

Okay

@IkkiOcean, apply the hover effect you used on the top 3 to all other contributor profiles as well.
Tell me one thing: is it also fetching for the top 3 contributors? Suppose someone contributes more than the current top 3; they should appear in the top 3, right?

@IkkiOcean, apply the hover effect you used on the top 3 to all other contributor profiles as well.
Tell me one thing: is it also fetching for the top 3 contributors? Suppose someone contributes more than the current top 3; they should appear in the top 3, right?

It's fetching for the contributors only but I have filtered the top three as it's better to not use another get request, as it will increase load time

It will dynamically put top 3 contributors while also ignoring you

@IkkiOcean
Right now Rajdeep has a total of 17 contributions. If, in the future, you complete 18 contributions, will you automatically appear in the top 3 contributors?

Yeas. It's simply based on the ranking provided by the github @mdazfar2

Yeas. It's simply based on the ranking provided by the github @mdazfar2

Ohw! Thank's, I wanted to confirm this.

Usually GitHub takes time to update the info in this API(as a rate limit) ,but your repo isn't receiving correct info. You might wanna check your insight section or smtg. I will also look into it as its also happening in another repo

@mdazfar2 pushed the commit with same effect and space between name and contributions

@mdazfar2 I actually made it responsive for mobile and desktop view so it automatically accommodates the profiles per row.But I can implement 4 per row logic in the next issue if you want with the .webp format conversion also

@mdazfar2 do let me know, if you have any other issues up for grab, or anything you wanted to implement.

@IkkiOcean 🔊
https://github.com/user-attachments/assets/0de74fc1-c614-477f-8fa3-e0fa96ab3bd6

@IkkiOcean 🔊
https://github.com/user-attachments/assets/0de74fc1-c614-477f-8fa3-e0fa96ab3bd6

Sure i will raise the issue


Storybook is broken ("Gt is not defined" on all stories)

Select which package(s) are affected
Mainly @storybook/react
Describe the bug
I wanted to explore the storybook to better understand the individual components, as i'm investigating into a migration of an existing app that had its components modeled after https://github.com/livekit/livekit-react – also i was hoping to find good approaches to improve our own stories for those components and possibly find a working simulateParticipants() example, as that method is barely documented and all initial tries with it failed.
So i tried both pnpm dev:storybook and also build:storybook, firing up a dev server to view docs/storybook/storybook-static/index.html with the latter.
The Storybook itself renders, but all stories show up like this

Reproduction
git clone git@github.com:livekit/components-js.git
cd components-js
pnpm install
pnpm dev:storybook

Wait until this box appears:
@livekit/component-docs-storybook:dev: ╭──────────────────────────────────────────────────────────────────────────────────────────╮
@livekit/component-docs-storybook:dev: │                                                                                │
@livekit/component-docs-storybook:dev: │   Storybook 7.6.19 for react-vite started                                                │
@livekit/component-docs-storybook:dev: │   3.94 s for manager and 9.75 s for preview                                              │
@livekit/component-docs-storybook:dev: │                                                                                │
@livekit/component-docs-storybook:dev: │    Local:            http://localhost:6006/                                              │
@livekit/component-docs-storybook:dev: │    On your network:  http://<IP_ADDRESS>:6006/                                         │
@livekit/component-docs-storybook:dev: │                                                                                │
@livekit/component-docs-storybook:dev: │   A new version (8.4.7) is available!                                                    │
@livekit/component-docs-storybook:dev: │                                                                                │
@livekit/component-docs-storybook:dev: │   Upgrade now: npx storybook@latest upgrade                                              │
@livekit/component-docs-storybook:dev: │                                                                                │
@livekit/component-docs-storybook:dev: │   Read full changelog: https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md   │
@livekit/component-docs-storybook:dev: │                                                                                │
@livekit/component-docs-storybook:dev: ╰──────────────────────────────────────────────────────────────────────────────────────────╯

then open up a browser and go to http://localhost:6006/
Logs
No response
System Info
System:
    OS: Linux 6.12 Manjaro Linux
    CPU: (4) x64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz
    Memory: 3.05 GB / 7.64 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    Node: 20.7.0 - /run/user/1000/fnm_multishells/2019_1735143515825/bin/node
    npm: 10.1.0 - /run/user/1000/fnm_multishells/2019_1735143515825/bin/npm
    pnpm: 9.12.1 - /run/user/1000/fnm_multishells/2019_1735143515825/bin/pnpm
    bun: 1.1.42 - /usr/bin/bun
  Browsers:
    Chromium: 131.0.6778.204
  npmPackages:
    livekit-client: ^2.5.7 => 2.6.0

Severity
blocking an upgrade
Additional Information
No response

I just tested with git co<EMAIL_ADDRESS>and can report that with that version the stories do render fine. Cross-checked with git co<EMAIL_ADDRESS>where they are broken, so it was one of the 2.6 patch releases that broke it.
BTW – v.2.5.0 showed this sleek and practical "design" when running pnpm dev:storybook – would be great to keep that as it greatly increases visibility by concerns due to the vast amounts of log output:

Manual Bisect results:
2.6.3 	✔ ("-")
2.6.4 	❌ (q ist not defined)

OK i could pin it down to commit 6ef4005 – if i revert that in my test setup stories render fine again. So, if we're lucky it's just adding in @storybook/builder-vite to make it work, will give it a go...


BuyLimit with "ConditionType"

i use bittrex API 1.1 and 2.0 for trading client (Delphi).
how use method BuyLimit with "ConditionType" and "Target" parameters?
this sample dont work? :
https://bittrex.com/api/v2.0/auth/market/tradebuy?&nonce=1502481723&MarketName=BTC-BCC&OrderType=LIMIT&Quantity=0.0005&Rate=0.10271362101&TimeInEffect=IMMEDIATE_OR_CANCEL&ConditionType=GREATER_THAN&Target=0.10271362101&__RequestVerificationToken=********

@trojanhost Sorry, I'm not affiliated with Bittrex in any way. Please contact the Bittrex support or head over to the appropriate forum at bitcointalk.org


[BUG] Databases ingestion does not run with parallelization

Describe the bug
Running DatabaseExporter with max_n_cpu>1 fails with a DuplicateError. Specifically, it fails when doing the secondary inserts (e.g. inserting a night that does not exist while inserting a raw exposure).

We should be doing a try/except for this


Update and test server selection logic for $out/$merge aggregation pipelines

JAVA-4380

Implemented logic from https://github.com/mongodb/specifications/pull/1095


Sorting

how i sort my node alphabetical after adding new node there, and if there any function to insert at?

Please sort nodes by your self.  You can move node use zTreeObj.moveNode() function.


Import new version of forked controller-tools

The manually created tag v0.6.2-1 is used in place of automatically generated v0.3.1-0.20230718144332-69030211a4bc (which was not intuitive).
It is required by https://github.com/cilium/cilium/pull/26646

/test


Flag users for invalid tokens, instead of checking it every time

At the time being, every time a new message occurs the clockify auth token is checked not only for absence, but also for online validity (via API). This means a call to Clockify + a call to the KV for every message, on average for no use at all.
I suggest we remove the check, and take any non null token as valid. If an exception occurs, we flag the user and ask it for a new token in some way

Duplicate of #59


Section B.5.2.1. FPT_TUD_EXT.2 Bold Text

FPT_TUD_EXT.2.2 If revocation information is not available for a certificate in the trust chain that is not a trusted certificate
designated as a trust anchor, the TSF shall [selection: not install the update, allow the Administrator to choose whether to accept the certificate in these cases].
Is there a reason why the entire paragraph in bold text? Fix if not

Fixed in editorial-v3_0-typos


enhance: Mark output details as diffs in markdown templates

Fixes #1678

💰 Infracost estimate: monthly cost will increase by $113 (+15%) 📈

Project
Previous
New
Diff

infracost/infracost/examples/terraform
$743
$856
+$113 (+15%)

Infracost output
```diff
Project: infracost/infracost/examples/terraform
~ aws_instance.web_app
+$113 ($743 → $856)
~ Instance usage (Linux/UNIX, on-demand, m5.4xlarge)
  +$93.44 ($561 → $654)

~ root_block_device

    ~ Storage (general purpose SSD, gp2)
      +$1.00 ($5.00 → $6.00)

~ ebs_block_device[0]

    ~ Storage (provisioned IOPS SSD, io1)
      +$13.00 ($125 → $138)

    ~ Provisioned IOPS
      +$5.60 ($52.00 → $57.60)

aws_lambda_function.hello_world2
Monthly cost depends on usage

Requests
Monthly cost depends on usage
+$0.20 per 1M requests

Duration
Monthly cost depends on usage
+$0.0000166667 per GB-seconds

Monthly cost change for infracost/infracost/examples/terraform
Amount:  +$113 ($743 → $856)
Percent: +15%
──────────────────────────────────
Key: ~ changed, + added, - removed
3 cloud resources were detected:
∙ 3 were estimated, all of which include usage-based costs, see https://infracost.io/usage-file
</details>


maven cache is not found

Description:
I am having an issue on my workflows because they are saving the cache at the Post Set Up Java but the cache is not found in the next time this workflow is being triggered.
I have three workflows and all three are behaving the same.
Set Up Java:
Run<EMAIL_ADDRESS>Installed distributions
Creating settings.xml with server-id: ossrh
Writing to /home/runner/.m2/settings.xml
Importing private gpg key
maven cache is not found

Post Set Up Java:
Post job cleanup.
Removing private key from keychain
/usr/bin/tar --posix -cf cache.tzst --exclude cache.tzst -P -C /home/runner/work/jumble-juggler/jumble-juggler --files-from manifest.txt --use-compress-program zstdmt
Cache Size: ~21 MB (22524066 B)
Cache saved successfully
Cache saved with the key: setup-java-Linux-maven-2ce1e5c635a93fe6e2777be9e471759542e7a1e7c394f7baf484fee1a0985f95

Task version:
Specify the task version
Platform:

[X] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[X] Hosted
[ ] Self-hosted

Repro steps:
It is a public repository: https://github.com/jumble-juggler/jumble-juggler
The three YAML file are in .github/workflows
Expected behavior:
Should use the cache maven.
Actual behavior:
maven cache is not found and it is saving the cache every time which takes a lot of time.

Hi, @hajjoujti 👋 Thanks for the bug report, we will take a look!

Because of this problem, my build time has doubled 😢.

same problem when using cache: 'gradle' option

Same here, cache is being created in post-action step but not being found in next run...

Hello @hajjoujti 👋,
Thank you for your report. I couldn't replicate the cache issue you mentioned and the caching mechanism working as intended.
To help resolve the issue, I suggest considering the following aspects:

Cache Invalidation: It's worth noting that the caching mechanism in workflows often uses the hash of certain files like pom.xml as part of the cache key. If these files are modified, it changes the hash and hence the cache key, which could be causing the cache recognition discrepancies you're observing. To ensure consistent caching, make sure these files stay the same across workflow runs.
Parallel Workflow Runs: In the instance of multiple workflows operating concurrently, there's a possibility of cache overlaps which can cause conflicts. A potential solution for this is to strategically schedule your workflows to prevent them from running simultaneously. This way, each workflow can efficiently utilize the cache without the risk of overwriting another's cache data.

Additionally, there have been similar reports about the maven cache not being used when workflows have different targets. Please see if this issue is relevant to your situation.
If you're having issues with the gradle cache, please refer to this issue and see if the discussion there is relevant to your case.
I hope this information is helpful.

Hello @hajjoujti, Just checking in to see if you had a chance to review the suggestions provided earlier regarding the cache issue in your workflows. Please let us know if the information was helpful or if you need further assistance. Thank you!

Hello,
Sadly I didn't have the time to check it out and it's been a while I didn't work on this project. I'm not sure when I will have the time to check it out.
I think it is safe to close this issue and I will recomment here if when I check it out again.

Hello @hajjoujti 👋,
Thank you for the update. I'll go ahead and close this issue for now. Please feel free to reopen it or comment here if you have any updates or encounter the problem again.
Thank you for your understanding and cooperation:)


setCheckedTogglePosition without notify listener

Can you add method setCheckedTogglePosition(int position, boolean notifyListener) to ToggleSwitch to decide if we want to notify listeners about toggle changed?

Fixed in release 1.2.2 :)


Upgrade to Humble

Update dependencies to ROS2 new version Humble. Fix compilation issues.
Ran example locally, all work as expected.

@rdelfin @dmweis Is about to upstream the ros2 changes, would love to have your eyes before pushing.

Thx @robin-wayve, @rdelfin went over it as well. I will proceed with upstream but we can always modify again if more issues are brought up.