Add "join table" for visits

In this pull request, I introduce significant changes to the database structure, including the creation of the vets, specializations, and visits tables. These changes facilitate the representation of relationships between vets, species, and animals, as well as tracking visits and specialties. SQL queries have been written to address specific questions related to these tables. Screenshots of the query results have been included in the Pull Request description for reference.
Changes Made:

Created a table named vets with columns: id (autoincremented PRIMARY KEY), name (string), age (integer), and date_of_graduation (date).
Created a "join table" named specializations to handle the many-to-many relationship between vets and species.
Created a "join table" named visits to handle the many-to-many relationship between animals and vets, including the date of the visit.
Inserted data into the vets table for four veterinarians with their respective information.
Inserted data into the specializations table to represent the specialties of certain vets.
Inserted data into the visits table to represent visits of various animals to different vets.

Screenshots:
Please reference comments for updated screenshots

Please reference below for updated screenshots
1. Who was the last animal seen by William Tatcher?

2. How many different animals did Stephanie Mendez see?

3. List all vets and their specialties, including vets with no specialties.

4. List all animals that visited Stephanie Mendez between April 1st and August 30th, 2020.

5. What animal has the most visits to vets?

6. Who was Maisy Smith's first visit?

7. Details for most recent visit: animal information, vet information, and date of visit.

8. How many visits were with a vet that did not specialize in that animal's species?

9. What specialty should Maisy Smith consider getting? Look for the species she gets the most


#844 fix tuple index out of range error

See #844

That's how Django wraps execute and callproc as well, so let's make this change.


Adding bashhub

Bashhub provides
Super command search by using context about how commands are executed.
Unlimited detailed terminal history stored in the cloud.
Support across systems. Access to your terminal history from anywhere.

Great! Thank you


Publish doesn't work on build 0.16.19969

When using AL:Publish with build 0.16.19969 I get an error message

Messages in the debug console:
[2018-07-11 15:55:30.68] Sending request to http://bcsandbox:7049/nav/dev/apps?SchemaUpdateMode=synchronize
[2018-07-11 15:55:31.75] Success: The package 'Default publisher_ALProject49_<IP_ADDRESS>.app' has been published to the server.
[2018-07-11 15:55:31.83] Error: An internal error has occurred

At the same time, Publish without debugging works fine. So it seems to be related to the debugger.
Reproduced both on local sandbox and on Azure VM.
Build 0.16.19969 (microsoft/sandbox)

Hi @ajkauffmann,
Do you have anything in the event viewer?

Checked that as well, nothing found.
I can share a VM if that helps.

Hi @ajkauffmann,
You could send them to thpeder and I'll have a look.

Can confirm with the june developer preview on Azure.
Have just created the AL: Go! example and gotten the same error message as @ajkauffmann when trying to debug.

Hi all,
I have the same exact issue with a newly created D365BC trial...

There is a problem with the docker image but we are trying to locate the problem and provide a new image once we know the cause.

Same issue here, any news about this issue?

any news about this?
Thks

This is the problem on the Nav server in the 12.2 builds. Debugger fails to launch when UsernamePassword authentication method is used.
The issue should be already resolved on bcinsider builds (12.3).


[Feature Request] (auto resolution): add fallback setting

Is your feature request related to a problem? Please describe.
Just a minor issue, but when using the auto resolution feature on videos that don't support the one you set, it defaults to the highest one available (usually 1080p, which takes ages to buffer).
Describe the solution you'd like
I think having a "fallback resolution" setting with the option of the closest available resolution (higher or lower) would be the best solution.
For example with 480p you would get 720p (closest higher) or 360p (closest lower)

@Mabra51 can you provide more information about how you want this fallback strategy to work.
I was thinking about how I can implement this and came to the conclusion it isn't practical. If you select 480p and it isn't available the quality can only be lower. I've never seen a video have a quality level missing if it has higher quality it has the lower levels.

@Mabra51 How the automatic quality feature functions currently is as follows:
If the preferred quality is available it is applied if not the preferred quality is used to find the closest quality available on the video.

You mean it's already supposed to do that ?
I have it set to 480, but when a video doesn't have it it just goes to 1080, instead of 720 or 360.

You mean it's already supposed to do that ?
I have it set to 480, but when a video doesn't have it it just goes to 1080, instead of 720 or 360.

Yes it is. Can you provide a link to a video so I can test this behavior.

Here's the most recent video i watched that lacks 480p.
https://youtu.be/9NgfV_KAV0s?si=VauPuGeNRWuuCtPt

@Mabra51 I will start to work on this tomorrow

I'm going to add a fallback mode that the user can configure the options will be higher and lower. If the desired resolution isn't available one lower or higher resolution will be picked based on the setting

@Mabra51 how does this look? Do you understand the meaning of the label and title

@Mabra51 how does this look? Do you understand the meaning of the label and title

Yes, that's what i had in mind. 👍

@Mabra51 how does this look? Do you understand the meaning of the label and title

Yes, that's what i had in mind. 👍

Thanks for replying. I'll commit the code and merge it to dev branch later today.

@all-contributors please add @Mabra51 for ideas

@all-contributors please add @Mabra51 for ideas

@Mabra51 this feature has been released in version 1.26.0


Fix EXIF GPS metadata extraction on mobile

This fixes https://github.com/josephfrazier/Reported-Web/issues/361. Here's the whole saga:
Here's an example image that works on desktop, but not mobile: https://photos.app.goo.gl/AcEfSrYTMqgp6JfX8
Using eruda to see the JS console with this branch, I see this on desktop:
Extracted GPS latitude/longitude location from EXIF metadata Object {latitude: 40.717019444444446, longitude: -73.99356388888889}

but this on mobile:
Extracted GPS latitude/longitude location from EXIF metadata Object {latitude: "NaN", longitude: "NaN"}

Seems like this issue might be within the exifr library: https://github.com/MikeKovarik/exifr

To rule out the possibility that the EXIF metadata is getting stripped when uploaded from my phone, I logged out the md5sum of the image right before parsing the metadata, and it is<PHONE_NUMBER>08457705bf09a8ee3c1093 on both desktop and mobile, yet the GPSLatitude and GPSLongitude arrays are [NaN, NaN, NaN] on mobile, but [40, 43, 1.27]and [73, 59, 36.83] on desktop, respectively.

related exifr issue: https://github.com/MikeKovarik/exifr/issues/64

I logged out the md5sum of the image right before parsing the metadata, and it is<PHONE_NUMBER>08457705bf09a8ee3c1093 on both desktop and mobile

Ugh, it looks like the package I chose to use might have a bug that causes this value to show up for ArrayBuffers: https://github.com/pvorb/node-md5/issues/49

If I switch to object-hash, I get a sha1 of b287c307cd89cfd2ce779b975b961b4824f2714a on desktop, but it crashes on my phone, so I guess I need something less resource-intensive...

Seems like Android is stripping GPS from EXIF after all, when the <input> element has an accept attribute specifying images, but removing the attribute does the trick for me.

related exifr issue: https://github.com/MikeKovarik/exifr/issues/64

I logged out the md5sum of the image right before parsing the metadata, and it is<PHONE_NUMBER>08457705bf09a8ee3c1093 on both desktop and mobile

Ugh, it looks like the package I chose to use might have a bug that causes this value to show up for ArrayBuffers: https://github.com/pvorb/node-md5/issues/49

If I switch to object-hash, I get a sha1 of b287c307cd89cfd2ce779b975b961b4824f2714a on desktop, but it crashes on my phone, so I guess I need something less resource-intensive...

It seems like there's still problems with EXIF metadata on an iPad running iOS 16.5, copy/pasting details from slack so I can still find them after slack deletes the messages: https://reportedcab.slack.com/archives/C9VNM3DL4/p1687400617485609

RM
1 day ago
@Joseph Frazier
my photo lookup problem appears to be limited to iPad (not iPhone), which is very strange (details in thread)
16 replies
RM
1 day ago
I take photos on a Sony camera (which pulls location from my phone in my pocket, via Bluetooth). Photos are uploaded to the iPad with location data intact.
RM
1 day ago
If I look at a photo on the iPad (in the Photos app), I see the location, but only AFTER I tap the “i” info button. (Here are before and after, note the “Today” at the top of the before, no location showing.)
2 files
Image from iOS
Image from iOS
RM
1 day ago
After I tap, the location “sticks.”
RM
1 day ago
If I look at any of the same photos on the iPhone (synced via iCloud), even at the same time, the location is always visible whether I tap first or not.
RM
1 day ago
If I initiate a report with one of these photos from the iPad (web app, Chrome), the lookup fails (perhaps because the location data is being stripped on upload, but i don’t know where/by what). Lookup failure is instantaneous, as though no location data is present. (edited)
RM
1 day ago
If I initiate a report with THE VERY SAME PHOTO from the iPhone, lookup works normally
RM
1 day ago
The next thing to try: upload a photo from the camera to the iPhone (not the iPad), let it sync via iCloud to the iPad, then try a report from the iPad
RM
1 day ago
Yep, the problem is the iPad
RM
1 day ago
Photo transferred directly from camera to iPhone does location lookup fine from the iPhone; once it syncs via iCloud to the iPad, it doesn’t do it on the iPad. (After syncing, doing a report with the very same photo from the two devices results in different lookup behavior.) (edited)
RM
1 day ago
IPhone is 16.1.1
RM
1 day ago
IPad is 16.5
RM
1 day ago
I wonder if something broke in the later dot release
RM
1 day ago
(If it’s a known iOS issue)
RM
1 day ago
I googled but I'm not very good at it so i couldn’t find evidence that it was
RM
1 day ago
No named fixes/changes in the interim releases appear related to this https://support.apple.com/en-us/HT213407
Apple SupportApple Support
About iOS 16 Updates
iOS 16 brings a redesigned Lock Screen with new ways to customize and widgets for information at a glance. Link your Lock Screen to a Focus and use Focus filters to filter out distracting content in apps.  Visual Look Up lets you lift the subject of an image from the background and copy and paste it in apps like Mail and Messages. iOS 16 also includes new updates to Mail, Maps, Wallet, Health, News, and more.
For information on the security content of Apple software updates, please visit this website: https://support.apple.com/kb/HT201222
Joseph Frazier
4 minutes ago
thanks for tracking that down,
RM
. If the problem is happening only with the iPad, my best guess is that it must be stripping the EXIF metadata from the image when uploaded, whereas the iPhone must not be. If this is the case, there's nothing I can do about it, unfortunately, unless there's another way I can tweak the  element to convince iOS not to strip the metadata, like I did for Android in https://github.com/josephfrazier/reported-web/pull/360
Joseph Frazier
< 1 minute ago
I googled ios 16.5 exif strip input element and found https://developer.apple.com/forums/thread/678109, where other people are reporting location getting stripped when uploaded into a browser

iOS seems to have stopped stripping EXIF GPS metadata as of version 17.1.2, see https://reportedcab.slack.com/archives/C9VNM3DL4/p1704407110590749:

Locations are extracting again from photos uploaded to the webapp via iOS

Confirmed to work on iOS 17.1.2 with both photos taken with the phone, and photos taken with an external camera (that included GPS info) and then transferred to the phone  (edited)

I thought that iOS had forcibly disabled location sharing on upload

But if so it’s been undisabled


avx2: added copyright information in avx2.h

avx2: added copyright information in avx2.h

I'll merge this after updating it. Since this branch is on the main repo, it will be faster if we don't use a PR for things that don't need review as the CI runs twice otherwise


UI Flicker when closing Store Modal Popup

Hey,
I do notice some flickering when I use the "done" button on the presented appstore modal.
It also happens, when I tap outside. Seems like it momentarily switches to full-screen and then back to the correct size and animates the close-animation...
Any idea how to fix this?
EDIT:
I've tried this on iPad

Hi 👋 @albatrosify , thanks for the issue reporting , can you share the screen record and which iPadOS version are you using?

Thanks for your quick reply :)
Here you go:
https://github.com/akshaynjarangal/appstore_info/assets/64252708/4365a5cd-0787-4b3b-8059-e5b1790815f8
Freeze-Frame:

Very nice :) I can confirm this has been fixed. Thanks a lot for the excellent package!

You're welcome! @albatrosify 🤗, I'm glad to hear that everything is working well for you now , Thank you for the kind words! 😍, please share this plugin to your area developer community


feat: Update Mariner Kata VHDs to use marketplace image

What type of PR is this?

/kind feature
What this PR does / why we need it:
This change configures the Mariner Kata VHD builds to use the cbl-mariner-2-kata Marketplace image instead of the static imported image. This is updating the version of several nested virtualization boot path components, along with ensuring that future base image changes can be automated.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

lgtm assuming it's been tested thoroughly with the mariner suite (though I seem to remember there being limited testing availability for kata)

Ran it through the test piplines and the build looked good. Working with my teammates to smoke test the image now and confirm all included components are the expected versions.


Enhance ecr viewer

PULL REQUEST
Summary
Show all ECR data in the file dynamically
Related Issue
Fixes https://github.com/CDCgov/phdi/issues/983
Additional Information
demo video

pretty ticky-tacky, but the startCase does not / will not properly render EICR-related fields and RR id.
Otherwise, looks good to me and was replicable.

Great catch, I went ahead and added some formatting to the header for the obvious cases

pretty ticky-tacky, but the startCase does not / will not properly render EICR-related fields and RR id.
Otherwise, looks good to me and was replicable.

Great catch, I went ahead and added some formatting to the header for the obvious cases

lgtm!


Javascript best practises.

These following problems should be solved in my code.
Index.js file

In line 21. My form has an action attribute but it is empty so it would be better to remove it.
In lines 14 and 87 I have comments and they should be deleted.

style.css file

Lines 46 and 69 use the same code so it would be good to combine them.

Also, I haven't used arrow functions in my code.

Issues solved


Latest version not translating anything (for me)

Hi there,
Since January that I haven't used this (awesome) tool. Meanwhile I formatted the computer so I did the usual npm install -g ember-i18n-csv which installed the latest version. When using the latest version I could not get the CSV file be created at all. I tried to diagnose the problem with node-debug and stepping through the code but could not really see what is wrong. I think it was probably something related to loading the js file and the require function.
I decided to try and instal version 0.0.2 using npm install -g<EMAIL_ADDRESS>and that worked flawlessly.
If there's any information that I could provide to help diagnose the issue on the latest version let me know.
Again, a big thanks for this great tool.
Fred

Seems to be working fine now with the latest version as well.


Spyder not showing all the variables generated by Pytorch tutorial

I am using spyder 3.2.8, installed via conda, using pythong 3.6. im on ubuntu 16.04
I am trying this example
https://pytorch.org/tutorials/beginner/blitz/cifar10_tutorial.html
and i see spyder still not showing all the variables, i also marked the option exclude unsupported data type, but still a lot of variable in the loop are missing, e.g. i cannot see inputs, labels,outputs,loss, running_loss

Thanks for reporting. We'll take a look at this in a future release.

I think you can remove "generated by Pytorch tutorial" from the title. Simply create a set and a list in the IPython console:
In [1]: a = {3,4,5}
In [2]: b = [3,4,5]

Only the list shows up in the variable explorer. Possibly also happens with other data types, but found this all the time with any set that I try.
Spyder version 3.3.1

Maybe related to #7943 and #7880?

Simply create a set and a list in the IPython console

@almarklein, support for sets is already available in master.

Maybe related to #7943

Support for Enums has to be implemented because we didn't consider them before (we have to support objects in a case by case basis).

and #7880?

This issue is unrelated and easily fixable. The variable explorer fails because it's trying to fetch more data from a Dataframe (we fetch rows and columns in demand) while it's closed.

Is this still relevant for Spyder 4 @dalthviz ?

I'm sure Pytorch arrays are still not supported by us.


Fix strategy overallocations

Reported by @gordonwatts
When using LocalProvider with strategy='simple', the provider does not track the status of submitted blocks properly-- it therefore thinks it needs to submit more blocks, resulting in a run-away submission of blocks. This is especially bad for htex, where each manager is using ~100% CPU (see #599).
2018-12-12 02:59:40 parsl.dataflow.strategy:125 [DEBUG]  Scaling strategy: simple
2018-12-12 02:59:42 parsl.dataflow.strategy:202 [DEBUG]  Executor remote_ipp_tev02.phys.washington.edu has 1 active tasks, 0/0/0 running/submitted/pending blocks, and 0 connected engines
2018-12-12 02:59:42 parsl.dataflow.strategy:256 [DEBUG]  Requesting 1 more blocks
2018-12-12 02:59:49 parsl.dataflow.strategy:202 [DEBUG]  Executor remote_ipp_tev02.phys.washington.edu has 1 active tasks, 0/0/0 running/submitted/pending blocks, and 2 connected engines
2018-12-12 02:59:49 parsl.dataflow.strategy:256 [DEBUG]  Requesting 1 more blocks
2018-12-12 02:59:55 parsl.dataflow.strategy:202 [DEBUG]  Executor remote_ipp_tev02.phys.washington.edu has 16 active tasks, 0/0/0 running/submitted/pending blocks, and 3 connected engines
2018-12-12 02:59:55 parsl.dataflow.strategy:256 [DEBUG]  Requesting 16 more blocks
2018-12-12 03:02:39 parsl.dataflow.strategy:202 [DEBUG]  Executor remote_ipp_tev02.phys.washington.edu has 31 active tasks, 0/0/0 running/submitted/pending blocks, and 19 connected engines
2018-12-12 03:02:39 parsl.dataflow.strategy:256 [DEBUG]  Requesting 31 more blocks
2018-12-12 03:13:47 parsl.dataflow.strategy:202 [DEBUG]  Executor remote_ipp_tev02.phys.washington.edu has 31 active tasks, 0/0/0 running/submitted/pending blocks, and 50 connected engines
2018-12-12 03:13:47 parsl.dataflow.strategy:256 [DEBUG]  Requesting 31 more blocks
2018-12-12 03:36:02 parsl.dataflow.strategy:202 [DEBUG]  Executor remote_ipp_tev02.phys.washington.edu has 18 active tasks, 0/0/0 running/submitted/pending blocks, and 81 connected engines
2018-12-12 03:36:02 parsl.dataflow.strategy:256 [DEBUG]  Requesting 18 more blocks
2018-12-12 04:01:47 parsl.dataflow.strategy:202 [DEBUG]  Executor remote_ipp_tev02.phys.washington.edu has 5 active tasks, 0/0/0 running/submitted/pending blocks, and 99 connected engines
2018-12-12 04:01:47 parsl.dataflow.strategy:256 [DEBUG]  Requesting 5 more blocks
2018-12-12 04:24:37 parsl.dataflow.strategy:202 [DEBUG]  Executor remote_ipp_tev02.phys.washington.edu has 2 active tasks, 0/0/0 running/submitted/pending blocks, and 104 connected engines
2018-12-12 04:24:37 parsl.dataflow.strategy:256 [DEBUG]  Requesting 2 more blocks
2018-12-12 04:34:55 parsl.dataflow.dflow:808 [INFO]  Terminating flow_control and strategy threads
2018-12-12 04:46:37 parsl.dataflow.strategy:202 [DEBUG]  Executor remote_ipp_tev02.phys.washington.edu has 2 active tasks, 0/0/0 running/submitted/pending blocks, and 106 connected engines
2018-12-12 04:46:37 parsl.dataflow.strategy:256 [DEBUG]  Requesting 2 more blocks

I have also noticed scaling up beyond max_blocks in a configuration of slurm/htex. From a brief scan of the code I could not see where max_blocks was properly enforced, and so maybe the whole scaling up infrastructure needs a good code review.

PR #907 claims to fix this


Fixes xcode beta 6 compile errors #319

Fixes xcode beta 6 compile errors
Issue: #316

Line example changed to test some features.


Prioritize llvm-amdgpu if exists on OpenCL Backend

Usually llvm-amdgpu doesn't exist in HCC environment, but HCC sometimes exists in HIP-Clang environment. However, HCC compiler may have mismatches with llvm-amdgpu libraries. Let's prioritize clang++ in llvm. This doesn't affect HIP/HCC environment.

It does affect HIP/HCC environment. This will break on our CI because clang++ is always installed with hcc, so it will pick clang++ first instead of hcc.
At least when building MIOpen, hcc should not be installed with hip-clang.

HCC isn't removed yet in hip-clang due to other dependencies, we are working on that. So we should set a -DMIOPEN_HIP_COMPILER=/opt/rocm/llvm/bin/clang++ in our environment?

@aaronenyeshi But HCC will be removed following 3.5 release, is that correct?

So we should set a -DMIOPEN_HIP_COMPILER=/opt/rocm/llvm/bin/clang++ in our environment?

If hcc is installed yes.

We've already set -DHIP_CXX_COMPILER= in the CI, are they different?

That variable is never used.

Okay I will fix the CI to that variable instead, thanks.


Billboards sometimes appear even though show flag is false

The billboard.show flag does not appear to be implemented correctly.  Transitioning from 3D to 2D causes some billboards to appear even though the show flag is false.
Suggest adding a check somewhere in BillboardCollection.prototype.update for show being false.
NOTE: the show flag is checked for the collection, but doesn't seem to be quite right for individual Billboards.

@bmr74 Could you put together a quick Sandcastle example that reproduces the problem?  That would help us track this down.  Thanks!

closing due to inactivity


SimpleWebServer: Content-Length appears twice in the response

curl -I http://x.x.x.x/x/test.jpg
HTTP/1.1 200 OK
Content-Type: image/jpeg
Date: Thu, 24 Nov 2016 08:25:04 GMT
Access-Control-Max-Age: 151200
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS, HEAD
ETag: 51d86932
Content-Length: 496305
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: origin,accept,content-type
Access-Control-Allow-Origin: *
Accept-Ranges: bytes
Connection: keep-alive
Content-Length: 496305
Some http clients doesn't work at all, when the response has two Content-Length headers.

This is happening both here: https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/org/nanohttpd/protocols/http/response/Response.java#L240
and here: https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/org/nanohttpd/protocols/http/response/Response.java#L259
Looks like someone was coding drunk, either in our team or even yourself. Will investigate and fix when possible.

@jtn-d please check if this still happens, should be fixed now.


Google fit extension?

I love the fitbit extension for your dash clock. Is there a comparable extension for Google fit steps?

I've released one today: https://play.google.com/store/apps/details?id=org.c99.dashclockfit


Document philosophy of events in MWC

Need to write down what our naming scheme, reasoning for bubbling/composing, and general philosophy on what actions should fire events for MWC.

This is mostly obsolete in M3, which follows native event conventions


Supabase auth Google OAuth2 flow 403 disallowed_useragent in browser responsive emulation mode

Bug report
Describe the bug
When initiating a Google OAuth2 flow via the Supabase web SDK in responsive mode (in my case in MS Edge browser, with iPad responsive emulation), Google blocks the request as a "403 disallowed_useragent".
When disabling the responsive device emulation, everything works again.
To Reproduce

Follow the steps as described in the documentation.
Open the browser dev tools
Enable responsive mode and choose a device (in my case, an iPad Pro 11")
Initiate a Google OAuth2 flow with:

supabase.auth.signIn({
  provider: 'google',
});

Expected behavior
When initiating an OAuth flow in a mobile device (as a responsive emulation in the browser), Google should not reject the request, just like it does without responsive device emulation.
Screenshots
This is the error screen I'm getting from Google.

System information

OS: Windows 10
Browser (if applies): Microsoft Edge
Version of supabase-js: 1.21.0
Version of Node.js: 16.6.1

Additional context
Leads
This seems to be related to recent changes in the Google OAuth2 policy that disallow webview user agents to perform OAuth2 requests.
Workarounds
I have none in that case, I am developing a PWA that must be installed on an iPad but must also be available in the browser.
If you aren't developing a PWA, disabling responsive device emulation works fine.

Closing since I don't think there's anything we can do about an auth provider imposing such restrictions.


Bookmark link is only visible for a fraction of a second

Working on an internal model, I tried to use the "Bookmark link" feature to create a self-containing link. Both in Firefox and Chrome, this link is displayed for a fraction of a second in the address bar, but directly changes back to "https://research.ng-london.org.uk/modelling/". Is this a bug, or am I doing something wrong?

Sorry, I missed this one.
The Bookmark Link is simply a link so if you want to copy it you can hover over the menu option right click and copy the link.
There is a redirect type step when data is sent to the modeller via the url - basically it decodes the data and resubmits it just like a user clicking refresh. So the data is sent via a POST process so the URL does then revert tot he simple plain URL.
The "Mermaid Code" option in the same menu just copies it to the clipboard - do you think this would be a better behaviour for the link as well?


InstallAppleCertificate: Please allow installing p12 from source (read desc before you judge me!)

Question, Bug, or Feature?
Type: Feature
Enter Task Name: InstallAppleCertificate
Environment

Azure Pipelines (cloud). No specific project / build.
Hosted Agent, MacOS 10.15

Issue Description
TL:DR; The InstallAppleCertificate task only works for secure files. Please add an option to install the certificate from a local working directory instead, as part of the normal execution phase.
We use a custom bash task early in the pipeline to populate the environment variables and download/decode some secure files based on our external secrets storage service (We use doppler.com but this could also apply to hashicorp vault or any other non-azure secure file service).
When building and signing iOS .ipa files, this process falls down because the InstallAppleCertificate task will ONLY work with azure pipeline secure files.
At the moment our temporary solve is to keep a copy of the p12 file in azure secure files, as well as our external vault. We also have to copy the password twice too, since the InstallAppleCertificate runs pre-job-execution before our external vault script has populated any variables. So, not ideal!
Thanks in advance 👍

Not stale, still an issue :(

Agreed pulling from disk should be an option.
We are trying to work around this issue by uploading to secure file during the pipeline using this hack .  I am also going to look at the source for this task and see if there is an easy way to add this.

This is still a valid request.

Hi @toddwalstad-eaton thanks for reporting! We are working on more prioritized issues at the moment, but will get back to this one once be able to. This would probably require additional checks from the point of security.

I would like to suggest this issue is actually expanded to allow the task to work secrets from KeyVault, either directly fetching from Key Vault or using an output variable from the AzureKeyVault task.

Agree with @asdaandrewhaigh. Support for certificates/identities store in Key Vault and/or using the output of AzureKeyVault task step would be logical improvements.

In order to grab it from KeyVault your AzureKeyVault task would need to set
runAsPreJob=true and you'd need to base64 decode if you stored it as a
secret.
If you stored the certificate and key and password as a secret separately
to assemble a p12 you'd need openssl or similar to create the bundle and
I'm not sure if that is supported by Apple.
I have been able to store the name of a certificate in Secure Files in a
Variable group backed by a KeyVault, but in the pipeline I had to export a
variable that tricked the variable group execution of the Get Secrets Key
Vault task to use runAsPreJob=true even though that isn't present in the
UI, the trouble was it sets that for all future references to the Get
Secrets task.
On Tue, Jan 24, 2023, 12:09 PM Jeremy Reichman @.***>
wrote:

Agree with @asdaandrewhaigh https://github.com/asdaandrewhaigh. Support
for certificates/identities store in Key Vault and/or using the output of
AzureKeyVault task step would be logical improvements.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/azure-pipelines-tasks/issues/13913#issuecomment-1402373561,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADXCXQKNBZOW2BNVIVNTFTWUALEHANCNFSM4TZIQKSQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Any chance this could be worked on?


is dst_mac always set to ff:ff:ff:ff:ff:ff?

Hi - in Wireshark my ARP packets all have a broadcast destination. In packet.js should pkt.dst also be set to macToArr(pktObj.dst_mac) as pkt.dst_mac is?
Thanks!

You are right. Thanks for noticing this. Can't imagine we missed this. The master branch has the latest fix.

@davidchatting Also here is the latest npm package: https://www.npmjs.com/package/arpjs/v/1.2.0
https://www.npmjs.com/package/arpjs/v/1.2.0

Excellent - glad to be of help - thanks for the super useful package!

What is the answer to the question in the title of this issue?
Is dst_mac optional or compulsory?  If latter, is it always ff:ff:ff:ff:ff:ff?

It’s resolved here. You can configure your dest Mac.
On Sat, Aug 10, 2019 at 4:07 AM RevealedFrom<EMAIL_ADDRESS>wrote:

What is the answer to the question in the title of this issue?
Is dst_mac optional or compulsory? If latter, is it always
ff:ff:ff:ff:ff:ff?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/skepticfx/arpjs/issues/14?email_source=notifications&email_token=AAGEI3WGJFXMG4PQTWTH3GDQD2ONTA5CNFSM4HHJ7RD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ALLSY#issuecomment-520140235,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGEI3WSAXLBLLUJOELOK6DQD2ONTANCNFSM4HHJ7RDQ
.


Disable forwarding proto stream by default in node_grpc_main.cc

...and use LoadStateFromFile from MapBuilderStub.
Solves problems with the gRPC message size limit when loading large state files.

Merge requested by authorized user gaschler. Merge queue now has a length of 1.


Added UI file for screens smaller than original UI file was designed …

…for. Should let you see all the important things.

I added a check in the trajectory viewer code to select the right ui based
on screen size - worth checking to see if it works on your computer with
the smaller screen. (I set the threshold to use the small ui at a screen
size of 900 px high)
On Tue, Oct 25, 2016 at 1:07 PM, tom-f-oconnell<EMAIL_ADDRESS>wrote:

…for. Should let you see all the important things.
You can view, comment on, or merge this pull request online at:
https://github.com/florisvb/multi_tracker/pull/2
Commit Summary

Added UI file for screens smaller than original UI file was designed
for. Should let you see all the important things.

File Changes

A multi_tracker_analysis/trajectory_viewer_small_screens.ui
https://github.com/florisvb/multi_tracker/pull/2/files#diff-0 (446)

Patch Links:

https://github.com/florisvb/multi_tracker/pull/2.patch
https://github.com/florisvb/multi_tracker/pull/2.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/florisvb/multi_tracker/pull/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPCPDSdgCcuv7Z-QTIhjOpIQFQFTRwcks5q3mGUgaJpZM4KgbQC
.

--
Floris van Breugel
Postdoctoral Researcher at Caltech
Department of Biological Engineering
Science: http://www.florisvanbreugel.com
Wildlife and Landscape Photographer
Galleries: http://www.ArtInNaturePhotography.com/
Blog: http://www.ArtInNaturePhotography.com/wordpress/


Pod disruption budget: tekton-pipelines-webhook issue

Hi, experienced this w/ 0.18.1 on Azure AKS during an rolling upgrade of k8s on the cluster via AKS's platform.
I was having troubles not being able to upgrade any cluster; AKS provisions a new node, drains one then upgrades and on and on. The entire process was hanging and failing, and it turned out due to the PodDisruptionBudget for tekton-pipelines-webhook. Is this expected? What should be the recommended procedure for avoiding this situation? Deleting the PDB prior to these kind of operations?
Name:           tekton-pipelines-webhook
Namespace:      tekton-pipelines
Min available:  80%
Selector:       app.kubernetes.io/component=webhook,app.kubernetes.io/instance=default,app.kubernetes.io/name=webhook,app.kubernetes.io/part-of=tekton-pipelines
Status:
    Allowed disruptions:  0
    Current:              1
    Desired:              1
    Total:                1
Events:                   <none>

or i guess just scaling it prior to an upgrade would solve it

Duplicate of #3654 -- I'll comment over there


Minor changes to parser and troubleshooting guide

Changes:
1)  Show BGP summary parser - w/o IP address
2)  Additional Troubleshooting for Pyez data

@pythonmagic
Thanks a lot for this pull request, it's great to get external contributions.
I agree the BGP parser needs to be clean-up, it should not have an IP address define in the query.
I see few things that needs to be updated before we can merge this request. I'll provide my comments inline in the code
Thanks
Damien

Made the changes to bgp parser and troubleshooting doc.

Hi @pythonmagic
Strangely the tests are failing now, I noticed that you have a mistake on the file show-system-resource-monitor-summary.parser.yaml, at the beginning, you remove the p or parser.
Please could you try to add it back to see if this help ?
Also,  I'm not sure to understand the changes in show-system-resource-monitor-summary.parser.yaml, please could you explain what you are trying change in this file.
thanks
Damien


fixes: #10604: json viewer not loading properly

Describe your changes:
fix owner assignment issue on entity page
fix the refresh token frame timeout issue
improve tier card: fixed issue: https://github.com/open-metadata/OpenMetadata/issues/10543#issuecomment-1480814581

Remove clear all button
add remove button at tier level fix: #10604

https://user-images.githubusercontent.com/12962843/229137871-89159bbf-e6f3-48f7-8084-44fefc62149f.mov
https://user-images.githubusercontent.com/12962843/229142532-920ed400-5411-4cb0-b0ec-21f3cde6a40c.mov

Type of change:

[x] Bug fix
[x] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@chirag-madlani if the user is set as owner, we should show the user tab first. Otherwise it would be confusing to click the owner filed and see nothing selected in Teams tab. You would know by the entity reference if the owner is team or user

@chirag-madlani if the user is set as owner, we should show the user tab first. Otherwise it would be confusing to click the owner filed and see nothing selected in Teams tab. You would know by the entity reference if the owner is team or user

@harshach fixed it, updated the recording


fix issue #251: isort removes newlines before standalone comments if …

With this tested commit, I'd like to give the User the ability to choose if he wants to use default Black's behavior or wants to use it with Isort, accepting its behavior. Run test:
pytest ./tests/test_black.py -k 'test__maybe_empty_lines'
For using with Isort  it's just enough to add in command line option --import-mode=1

How do you see for any refactor? I suppose that black.py is too big to support. When some contributors are solving different issues in one module at the same time merge issues can occur. And not only that

We're generally not interested in adding command-line flags that affect formatting based on user preferences. The isort project is apparently interested in releasing a Black-compatible configuration, which would be a better solution.


Added Name as a contributer

Hello, thanks for signing up as a reviewer!
Running into some CLA bot issues ...
I verified you signed the CLA with your email, but since the commit is not using that same email, address the bot is getting confused.
Would you be able to create another pull request using the email you signed the CLA with? That should fix things for future contributions.
Thanks

@lamberta  Thank you for the quick response.
I'm using the same email for both github and CLA account, so i'm little bit confused.
Would trying with a new request and CLA help?
Thanks

It's difficult to see in GitHub's UI, but in the commit history the author email is set to<EMAIL_ADDRESS>(not your CLA email).
I believe this can be configured within the GitHub settings. If editing locally, you can configure your email/name in the .gitconfig file.

@lamberta I understand.
That's because i had the email display set to private on my Github account.
It's updated to public now, I think it should work.
Thank you


[WIP] Upgrade to rails 6.rc1

I just ran
rails app:update

and the selected overwrite for any file conflicts
we will need to revert any changes that got removed erroneously (I am
thinking the ActionMailer change will need some custom work along
with the config.read_encrypted_secrets = true removal)

Upgrading from Rails 5.2 to Rails 6.0
Ruby on Rails 6.0 Release Notes

Current Heroku CI failure:
-----> Fetching heroku/ruby buildpack...
       buildpack downloaded
-----> Fetching https://github.com/heroku/heroku-buildpack-chromedriver buildpack...
       buildpack downloaded
-----> Fetching https://github.com/heroku/heroku-buildpack-google-chrome buildpack...
       buildpack downloaded
-----> Ruby app detected
-----> Setting up Test for Ruby/Rails
-----> Using Ruby version: ruby-2.6.3
-----> Installing dependencies using bundler 2.0.2
       Running: bundle install --without development --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
       Activating bundler (2.0.1) failed:
       Could not find 'bundler' (2.0.1) required by your /app/Gemfile.lock.
       To update to the latest version installed on your system, run `bundle update --bundler`.
       To install the missing version, run `gem install bundler:2.0.1`
       Checked in 'GEM_PATH=/app/vendor/bundle/ruby/2.6.0', execute `gem env` for more information

       To install the version of bundler this project requires, run `gem install bundler -v '2.0.1'`
       Bundler Output: Activating bundler (2.0.1) failed:
       Could not find 'bundler' (2.0.1) required by your /app/Gemfile.lock.
       To update to the latest version installed on your system, run `bundle update --bundler`.
       To install the missing version, run `gem install bundler:2.0.1`
       Checked in 'GEM_PATH=/app/vendor/bundle/ruby/2.6.0', execute `gem env` for more information

       To install the version of bundler this project requires, run `gem install bundler -v '2.0.1'`
 !
 !     Failed to install gems via Bundler.
 !


Added overview and installation information.

Hi @machacekondra,
Can we please get someone to review this for me? I've managed to test the install on a downstream 4.1.5 environment, but I'm not 100% sure about upstream. Especially the part about installing the package.
Kind regards,

ci build please


Windows CrashHandler: Create a thread for separate stack

On Windows, every thread has a separate stack space. It is possible to create a separate thread to do the exception handling job without having to mess with the stack pointer. Therefore we can happily remove any inline assembly.
Special thanks to sigatrev for inspiration.

This seems good to me.
My only minor nitpick is, since we're handling the (However unlikely) scenario of not being able to start the thread (I would guess because there's no memory for the stack? No idea), shouldn't we also output something mentioning why we're terminating (A message box, console msg, or log entry)? I'm not actually sure if attempting that with the current stack is a good idea, and just terminating ASAP in this case seems fine to me anyways because of the stuff mentioned in the comment.
This seems strictly better than what we had anyways since we were ignoring the stack issues in x86-64. I do wonder how spinning a new thread interacts with sigatrev's concern for OOM exception handling (Won't that also fail to allocate the stack for the thread? I honestly have no idea. It's not like there's much we can do anyways)
I'm guessing this is a backport (Or forward port? No idea what the term is since we're the fork :P) of your PR in the sm repo. I just wanna thank you for it :yum:
cc @poco0317 in case you're interested in looking at this before merging (Also, would this warrant a changelog entry? It's not something a user would ever be concerned with but I'm unsure of what the criteria is)

According to sigatrev, we should have enough remaining stack memory to launch a thread. Perhaps even enough for crash handling. So if CreateThread also fails, I seriously do not think there will be anything else we can do. Just let it crash.
This is indeed a port from my PR in StepMania repo, because some Etterna players I know recently found that PR and asked me to do the port. Maybe you should go thank them :)

Every change warrants a changelog entry. Since one doesn't exist for .67 yet I'll just have to add it later when reviewing everything.
Will merge later assuming everything goes smoothly (I was the one who saw the PR and mentioned to the guy who probably talked to you)

I have just finished revising VDI format for x64 symbol lookup on StepMania repo. Concerning that you have already moved to using ILK, do you expect me to port it here?

hello im alive

I've honestly never looked at SM's VDI format thing, but any fixes/improvements are always welcome. Though maybe a separate PR would be a good idea, if you do decide to do so. Do you mind if we go ahead and merge this one as-is? (Probably after some testing just because)

I am fine with merging this one.


Minor fix for clean instructions

🙋 Documentation Request
The instructions to force a full rebuild in the readme are incorrect:
yarn clean && yarn cache clean && rm node_modules && rm yarn.lock

should be:
yarn clean && yarn cache clean && rm -r node_modules && rm yarn.lock

Otherwise, the rm node_module will fail because node_modules is a directory and the yarn.lock file will not be removed.

🧢 Your Company/Team
Adobe/STLab

Fixed here: https://github.com/adobe/aio-theme/commit/0a4126f2627add892aee7d86f0b8f0c0ccfb6fe9


Remove -ti in docker build to allow automation run the build.

Remove -ti in docker build to allow automation run the build.

CLA signed.


getStatus()的几种状态，哪里能看到

找了好久，不知道是不是我漏掉了。

public class FileDownloadStatus {
// [-2^7, 2^7 -1]
// by very beginning
/**
* When the task on {@code toLaunchPool} status, it means that the task is just into the
* LaunchPool and is scheduled for launch.
*
* The task is scheduled for launch and it isn't on the FileDownloadService yet.
/
public final static byte toLaunchPool = 10;
/*
* When the task on {@code toFileDownloadService} status, it means that the task is just post to
* the FileDownloadService.
*
* The task is posting to the FileDownloadService and after this status, this task can start.
*/
public final static byte toFileDownloadService = 11;
// by FileDownloadService
/**
 * When the task on {@code pending} status, it means that the task is in the list on the
 * FileDownloadService and just waiting for start.
 *

 * The task is waiting on the FileDownloadService.
 *

 * The count of downloading simultaneously, you can configure in filedownloader.properties.
 */
public final static byte pending = 1;
/**
 * When the task on {@code started} status, it means that the network access thread of
 * downloading this task is started.
 *

 * The task is downloading on the FileDownloadService.
 */
public final static byte started = 6;
/**
 * When the task on {@code connected} status, it means that the task is successfully connected
 * to the back-end.
 *

 * The task is downloading on the FileDownloadService.
 */
public final static byte connected = 2;
/**
 * When the task on {@code progress} status, it means that the task is fetching data from the
 * back-end.
 *

 * The task is downloading on the FileDownloadService.
 */
public final static byte progress = 3;
/**
 * When the task on {@code blockComplete} status, it means that the task has been completed
 * downloading successfully.
 *

 * The task is completed downloading successfully and the action-flow is blocked for doing
 * something before callback completed method.
 */
public final static byte blockComplete = 4;
/**
 * When the task on {@code retry} status, it means that the task must occur some error, but
 * there is a valid chance to retry, so the task is retry to download again.
 *

 * The task is restarting on the FileDownloadService.
 */
public final static byte retry = 5;

/**
 * When the task on {@code error} status, it means that the task must occur some error and there
 * isn't any valid chance to retry, so the task is finished with error.
 *

 * The task is finished with an error.
 */
public final static byte error = -1;
/**
 * When the task on {@code paused} status, it means that the task is paused manually.
 *

 * The task is finished with the pause action.
 */
public final static byte paused = -2;
/**
 * When the task on {@code completed} status, it means that the task is completed downloading
 * successfully.
 *

 * The task is finished with completed downloading successfully.
 */
public final static byte completed = -3;
/**
 * When the task on {@code warn} status, it means that there is another same task(same url,
 * same path to store content) is running.
 *

 * The task is finished with the warn status.
 */
public final static byte warn = -4;

/**
 * When the task on {@code INVALID_STATUS} status, it means that the task is IDLE.
 *

 * The task is clear and it isn't launched.
 */
public final static byte INVALID_STATUS = 0;

参考 FileDownloadStatus.


fix(): keep loading the page on networks where subgraph is not available ex. Matic

Fixes #1582
Changes proposed

Add try catch so that it does not block the page from loading.
Future - Based on demand, add a subgraph for matic and other networks.

@ChaituVR is there any subgraph for polygon?

https://github.com/snapshot-labs/snapshot-strategies/blob/3b7e8fb5a680321fdc8e7f59dfcdcc10124c00e7/src/utils/delegation.ts#L4-L14
@midgerate Yes, maybe I think we can copy other network's subgraphs too

@midgerate the spacing doesn't seem right here. Can we add more space on the left and reduce sapce on the right between the icon and"Learn more"?

Feel free to merge after you have made that change!


grad transform introduces reduction operation with NumberProxy in axes

🐛 Bug
Found this issue in #286 , see comment https://github.com/Lightning-AI/lightning-thunder/pull/286#discussion_r1597889447
two issues that I want to raise regarding this:

NumberProxy shouldn't show up in trace. (look at the trace from torch executor.

@no_autocast
def backward_fn(saved_for_backward, cotangents):
  # saved_for_backward: "Collection"
  # cotangents: "Collection"
  C0, C1, = saved_for_backward
  clear_collection(saved_for_backward)
  del saved_for_backward
  t83, = cotangents
  clear_collection(cotangents)
  del cotangents
  t11, t15, t25, t26, t28, t38, t48, t52, t54, t58, t62, t64, t65, t66, t67, t70, \
  t71, t72, t74, t78, t79, t80, t_attn_c_attn_weight, t_attn_c_proj_weight, \
  t_mlp_c_fc_weight, t_mlp_c_proj_weight, = C0
  clear_collection(C0)
  del C0
  f40, f44, f67, f69, f71, i51, i6, = C1

  t411 = torch.sum(t409, i51, True, dtype=None)  # t411: "cuda:0 f32[2, 12, 1024, 1]"
    # t411 = ltorch.sum(t409, i51, True, dtype=None)  # t411: "cuda:0 f32[2, 12, 1024, 1]"
      # t552 = prims.sum(t409, (3,))  # t552: "cuda:0 f32[2, 12, 1024]"
      # t411 = prims.broadcast_in_dim(t552, [2, 12, 1024, 1], [0, 1, 2])  # t411: "cuda:0 f32[2, 12, 1024, 1]"
  del t409, i51

Nvfusion isn't handling reduction axes properly. Look at the trace from nvfuser executor, how i51 is not used in prims.sum and it instead baked it in as constant number.

  [t415] = nvFusion3(i51, t406, t48)
    # t30 = prims.iota(1024, start=0, step=1, device=devices.Device("cuda:0"), dtype=dtypes.int64)  # t30: "cuda:0 i64[1024]"
    # t31 = prims.broadcast_in_dim(t30, [1024, 1], [0])  # t31: "cuda:0 i64[1024, 1]"
    # t32 = prims.iota(1024, start=0, step=1, device=devices.Device("cuda:0"), dtype=dtypes.int64)  # t32: "cuda:0 i64[1024]"
    # t33 = prims.broadcast_in_dim(t32, [1, 1024], [1])  # t33: "cuda:0 i64[1, 1024]"
    # t34 = prims.add(t31, 0)  # t34: "cuda:0 i64[1024, 1]"
    # t35 = prims.broadcast_in_dim(t34, (1024, 1024), (0, 1))  # t35: "cuda:0 i64[1024, 1024]"
    # t36 = prims.broadcast_in_dim(t33, (1024, 1024), (0, 1))  # t36: "cuda:0 i64[1024, 1024]"
    # t37 = prims.ge(t35, t36)  # t37: "cuda:0 b8[1024, 1024]"
    # t38 = prims.broadcast_in_dim(t37, (2, 12, 1024, 1024), (2, 3))  # t38: "cuda:0 b8[2, 12, 1024, 1024]"
    # t409 = prims.mul(t48, t406)  # t409: "cuda:0 f32[2, 12, 1024, 1024]"
    # t410 = prims.sum(t409, (3,))  # t410: "cuda:0 f32[2, 12, 1024]"
    # t411 = prims.broadcast_in_dim(t410, [2, 12, 1024, 1], [0, 1, 2])  # t411: "cuda:0 f32[2, 12, 1024, 1]"
    # t412 = prims.broadcast_in_dim(t411, (2, 12, 1024, 1024), (0, 1, 2, 3))  # t412: "cuda:0 f32[2, 12, 1024, 1024]"
    # t413 = prims.sub(t406, t412)  # t413: "cuda:0 f32[2, 12, 1024, 1024]"
    # t414 = prims.mul(t48, t413)  # t414: "cuda:0 f32[2, 12, 1024, 1024]"
    # t415 = prims.where(t38, t414, 0.0)  # t415: "cuda:0 f32[2, 12, 1024, 1024]"
  del i51, t406, t48

To Reproduce
pytest thunder/tests/test_examine_memory.py -s -v -k test_nanogpt_block
Might want to print out bw_extrace and verify the backtrace.
Reproduced on commit
commit d6237c88d26aa4a5541f3ad2e955140264afb068 (HEAD -> main, origin/main, origin/HEAD)
Author: Ivan Yashchuk<EMAIL_ADDRESS>Date:   Fri May 10 18:26:46 2024 +0300

    Fix flaky test_prim_inplace_copy_fwd (#399)

triage review —

we think we can change the backward trace to use constant numbers instead of number proxies for now
but we do want number proxies in the backward trace soon, so we should carefully consider their integration with nvfuser and grad, and imposing restraints like "this must be a constant value"
maybe nvFuser's cache could detect the value of the NumberProxy?

so we should carefully consider their integration with nvfuser and grad, and imposing restraints like "this must be a constant value"

Imposing those constraints universally in thunder is what I'm planning to do.
When you mentioned explicitly about integration, I'm under the impression that you are trying to allow backend to propose constraints. I'm open to that discussion and have an issue opened already. That might be a bit trickier to plumb through back to prologue trace.
Meanwhile, I think an easy way to unblock us for now is to just let integration reject things when seeing NumberProxy on those that must be a constant value. i.e. reduction axes for example.

NumberProxy shouldn't show up in trace.

Do you think NumberProxies shouldn't be used in traces, in general, today and in the future, or only today because of how it's not dynamic and only a wrapper around a constant today?
It's possible to modify the trace to unwrap all NumberProxies into actual values by modifying backward_trace after this line https://github.com/Lightning-AI/lightning-thunder/blob/4663b87e67955edec371c6f37a763a7ec358d835/thunder/core/transforms.py#L3961C5-L3961C49.

Do you think NumberProxies shouldn't be used in traces, in general, today and in the future, or only today because of how it's not dynamic and only a wrapper around a constant today?

I should be more careful with my wording :laughing:
Yes NumberProxies should be used in the trace in general. There're some rough corners (i.e. nvfuser's handling of baking in static number from proxies), but we should just patch those.
But I'm surprised to see NumberProxy show up with thunder.jit today. IIUC, that's what TestExecutor.make_callable uses for compilation. Current default caching logic is CONSTANT_VALUES, I thought that means everything gets baked in as static and I'm not sure where the NumberProxy is coming from.
Totally not pointing finger at grad transform. But I think in general NumberProxy should be treated differently with a plain Number. i.e. A NumberProxy means dynamic value and that should be respected by transforms.

I'm closing this issue since I now understands where the number proxy is coming from in grad transform.
Looking forward to #231 fixing the issue.


Support query string in a pipeline url

The operator does not support a pipeline URL with a qury string. For example, here is an error message from a stack:
url: https://github.com/mchenggit/kabanero-pipelines/blob/issue267v3/ci/assets/eventing-kabanero-pipelines.tar.gz?raw=true
status: active
statusMessage: Can not decode file type of file for Pipeline . Must be .tar.gz
or .yaml.
version: 0.2.10

@mchenggit - Is there a particular release this is needed by?

@marikaj123 I can work around it, but fixing it definitely helps improves pipeline development experience.

This is fixed by #625 and will be available in the first 0.9.0 alpha or rc release.


mssql bug

reasult cannot copy,

VSCode Version: Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:23:26.125Z)
OS Version: Darwin x64 17.2.0
Extensions:

Extension
Author (truncated)
Version

xml
Dot
1.9.2

beautify
Hoo
1.1.1

html-css-class-completion
Zig
1.14.0

code-gnu-global
aus
0.2.2

vscode-eslint
dba
1.4.3

vs-code-xml-format
fab
0.1.5

vscode-clang
mit
0.2.2

mssql
ms-
1.2.1

python
ms-
0.8.0

cpptools
ms-
0.14.2

csharp
ms-
1.13.1

Steps to Reproduce:

Reproduces without extensions: Yes/No

Reading your description it seems that the issue originates from an extension and not VS Code itself. Thereby I will close this issue and kindly ask you to report this issue against the extension repository.
Most extensions are on GitHub as well so it should be easy to file it against the extension. If you open an extension on the market place, click on the Support link to find out more.

Thanks again for your feedback!


Support Qiskit Backend.jobs() and related attributes

Feature request
Support Qiskit Backend.jobs() and related attributes.
User story
My Qis Job program qasm_job.py can fetch job info using Qiskit Backend.jobs() and related methods.
qasm_job.py supports Quantum Inspire as a provider.
However calls to  Backend.jobs() fail as follows:
be_jobs = BACKEND.jobs(limit=JOBS)
AttributeError: 'QuantumInspireBackend' object has no attribute 'jobs'

Where BACKEND is correctly instanced to the Quantum Inspire default Backend and JOBS is instance to an integer.
Acceptance criteria
This snippet from my qasm_job.py with consts/vars correctly instanced works correctly with Qiskit for other providers:
    f_string = "Job {} {}"
    if JOBS:
        PROVIDER = account_fu(TOKEN, URL)
        BACKEND = PROVIDER.get_backend(BACKEND_NAME)
        be_jobs = BACKEND.jobs(limit=JOBS)
        for a_job in be_jobs:
            print(f_string.format(str(a_job.job_id()), str(a_job.status())))
        sys.exit(0)

    elif JOB_ID:
        PROVIDER = account_fu(TOKEN, URL)
        BACKEND = PROVIDER.get_backend(BACKEND_NAME)
        a_job = BACKEND.retrieve_job(JOB_ID)
        print(f_string.format(str(a_job.job_id()), str(a_job.status())))
        sys.exit(0)

    elif JOB_RESULT:
        PROVIDER = account_fu(TOKEN, URL)
        BACKEND = PROVIDER.get_backend(BACKEND_NAME)
        a_job = BACKEND.retrieve_job(JOB_RESULT)
        print(f_string.format(str(a_job.job_id()), str(a_job.status())))
        PP = pprint.PrettyPrinter(indent=4, stream=sys.stdout)
        PP.pprint(a_job.result().to_dict())
        sys.exit(0)

@QFer or other members of the QI team will be taking a look at it. Hang tight @jwoehr. :-)

We took a look at the ibmqbackend. A few methods are added to the ibmqbackend that are not in the interface of BaseBackend. You mentioned jobs() and retrieve_job(jobid).
Our backend has a method retrieve_job() with a slightly different signature (job_id is string instead of int).
Our api has a method to get all the jobs. api.get_jobs() which returns a list of jobs and a method get_job to get a specific job, given the job id.
Are these sufficient for your usage or is the compliance to the ibmqbackend interface important for you?

We took a look at the ibmqbackend. A few methods are added to the ibmqbackend that are not in the interface of BaseBackend.

Ah, right. I had not considered that subtlety.

You mentioned jobs() and retrieve_job(jobid).
Our backend has a method retrieve_job() with a slightly different signature (job_id is string instead of int).
Our api has a method to get all the jobs. api.get_jobs() which returns a list of jobs and a method get_job to get a specific job, given the job id.
Are these sufficient for your usage or is the compliance to the ibmqbackend interface important for you?

Entirely sufficient. Thank you. Shall I close the issue?


[WIP] Add a Docker registry/pull-through cache

What is the problem that this PR is trying to fix?
The purpose of this PR is to reduce egress for Docker Hub.
What approach did you choose and why?
This PR:

adds a GCE instance to serve as a Docker read-only registry/pull-through cache, and
sets the registry-mirrors to the above instance on the Docker config of the default GCE build image

Addresses https://github.com/travis-ci/team-blue/issues/858

Planning to just use Container Registry's Docker Hub mirror.


Implement Target Metadata

What
Describe what the change is solving
Implement propagating the target metadata (annotations and labels) to the target service created by BoundEndpoint
How
Describe the solution
Add util.ParseHelmDictionary()
Use util.ParseHelmDictionary() for --ngrok-metadata
Add serviceAnnotations and serviceLabels flags to api binary
Propagate target metadata to target service
Breaking Changes
Are there any breaking changes in this PR?
No.

#477  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hjkatz and the rest of your teammates on  Graphite

@jonstacks I chose not to factor out the config file for the api binary for simplicity in implementing the metadata for now.
We can always go back and use a config file for settings.

@jonstacks I chose not to factor out the config file for the api binary for simplicity in implementing the metadata for now.
We can always go back and use a config file for settings.

Sounds good to me. I've logged https://github.com/ngrok/ngrok-operator/issues/478 for simplifying the config

Merge activity

Oct 30, 12:40 PM EDT: A user started a stack merge that includes this pull request via Graphite.


Fix edit start date bug for makeup lesson

fix #249

Codecov Report

Merging #250 (3c6041c) into master (4a1d686) will increase coverage by 1.95%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #250      +/-   ##
============================================
+ Coverage     67.68%   69.63%   +1.95%
- Complexity     1049     1051       +2
============================================
  Files           136      136
  Lines          3676     3580      -96
  Branches        474      469       -5
============================================
+ Hits           2488     2493       +5
+ Misses          980      879     -101
  Partials        208      208

Impacted Files
Coverage Δ

...eedu/address/logic/commands/LessonEditCommand.java
73.91% <100.00%> (+0.32%)
:arrow_up:

src/main/java/seedu/address/ui/CommandBox.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/CenterPanel.java
0.00% <0.00%> (ø)

.../seedu/address/model/lesson/CalendarEntryList.java
89.58% <0.00%> (+2.08%)
:arrow_up:

Continue to review full report at Codecov.

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

would be good to add tests in LessonEditCommand also


Bug: The Hacktoberfest Label is misspelled in the repository tags

In the about tab of the repository, the hacktoberfest word is misspelled as hactoberfest

Thanks for raising this issue. I have fixed it.


Fixes resize() and fill()

Previously neither function did what they were supposed to.

@verbalshadow Hey, this looks great. Thanks! Can you squash the commits and then I'll approve the merge?

Thanks!


Fix deeper nesting wiki page for new ToC

@lord Are you able to give me a hint of how to get this working again prior to cutting the next release? I upgraded to the dev branch to fix the issue with the logo margin and lost the h3's in my TOC.

It's a bit convoluted — in the mean time before I have some time to fix it, you may just want to port the margin fix over to your fork of the master branch. The change is quite small — see https://github.com/lord/slate/commit/e7f5144e4c091b57ae2be5a8357e8ec04b7477a9

Thanks @lord , I moved back to master and selectively pulled in the changes from dev.

@lord So it looks like there's 3 parts to this

Another level of nesting in the layout.html.erb
css for toc-link-h3 (added in step 1)
changes to _toc.js to add the active class

I'm currently held up trying to make the js changes because of some confusion around the best variable.
As far as I can tell right now, some changes have to be made to include children here:
        $best.parents(tocListSelector).addClass("active");
        $best.siblings(tocListSelector).addClass("active");

Can you confirm?

@bc-AlyssNoland that's close I think? I think loadToc is called in all_nosearch.js, and if you just change the '.toc-list-h2' say '.toc-list-h2, .toc-list-h3', I think that should be enough for the js changes. Then, all that'd need to happen would be adding the extra nesting level in layout.html.erb.
If you or anyone else codes a complete solution and has a spare moment, it'd be awesome to post it here/in the wiki for others to find!

@lord So after quite a bit of testing and playing around with it, I believe I'll need to refactor or add a new function to support adding the active class to h3 ul elements.

  <% toc_data(page_content).each do |h1| %>

      <a href="#<%= h1[:id] %>" class="toc-h1 toc-link" data-title="<%= h1[:content] %>"><%= h1[:content] %>
      <% if h1[:children].length > 0 %>

          <% h1[:children].each do |h2| %>

              <a href="#<%= h2[:id] %>" class="toc-h2 toc-link" data-title="<%= h1[:content] %>"><%= h2[:content] %>
              <% if h2[:children].length > 0 %>

                  <% h2[:children].each do |h3| %>

                      <a href="#<%= h3[:id] %>" class="toc-h3 toc-link" data-title="<%= h1[:content] %>"><%= h3[:content] %>

                  <% end %>

              <% end %>

          <% end %>

      <% end %>

  <% end %>

  .toc-list-h3 {
    display: none;
    background-color: $nav-subitem-bg;

    .tocify-focus {
      a {
        background: url('../images/slash.svg') no-repeat;
        background-position: 13px 8px;
        background-size: 10px;
      }
    }
  }

Still working on the javascript bit, but I'll post it when I'm done. Can you provide some commenting on _toc.js for lines 53 to 70? I am probably good for the most part but I'm still a little fuzzy on $best.

:+1: :+1: looks awesome! @bc-AlyssNoland

Looks like you updated the wiki yesterday, so I guess we can consider this issue closed. Thanks so much for the help!

Just so there's a record of my change elsewhere from the wiki, I wanted to point out how it was helpful to also add
 // the div is the tocify hidden div for placeholding stuff
 & > h1,
 & > h2,
+& > h3,
 & > div {
   clear: both;
 }

to line 377 of screen.css.scss to the wiki page. The deeper nesting instructions covered everything but keeping code samples tied to the appropriate sections when there are large code samples, but this change fixed that (related to #631 )

The following class may also be added to screen.css.scss (right after the .toc-list-h3 definition) to provide hierarchical styling for h3 in the left nav:
.toc-h3 {
  padding-left: $nav-padding + ($nav-indent * 2);
  font-size: 12px;
}

Hi I tried the solution in the wiki but my TOC is not responding Please check if the wiki is correct or if there are any fixes to it

@yashu2001 do you see any JavaScript or CSS errors in your browser debug console?

Hi I see a j query error with undefined expression # on line 4040 in all.js


Figure out the best way combination of sharding/gradient checkpointing for throughput

I've played around with this and the best I can come up with is the obvious default. blocked gradient checkpointing makes things slower


Error upgrading to exec-maven-plugin version 3.1.0

Describe the bug
When updating the exec-maven-plugin version to 3.1.0 in the pom, the build fails with mkdir: missing operand. I'm pretty sure this comes from here:
https://github.com/apache/accumulo/blob/78142d74f3ed1a23a374f5bd5fdbd7f245a16721/core/pom.xml#L344-L348
The second argument must not be behaving as expected. I can replicate this error in my terminal by not passing another argument i.e. mkdir -p with nothing after it.
Versions (OS, Maven, Java, and others, as appropriate):

Affected version(s) of this project: 2.1.0-SNAPSHOT

To Reproduce
Steps to reproduce the behavior (or a link to an example repository that reproduces the problem):

udpate exec-maven-plugin to 3.1.0
run mvn clean package -DskipTests

I wonder if it is related to https://github.com/mojohaus/exec-maven-plugin/issues/334 , which also seems related to https://github.com/mojohaus/exec-maven-plugin/issues/75 . exec-maven-plugin seems to perpetually be confused regarding anything with -p, due to assumptions that it's related to a Java modulepath, even if the executable is entirely different.
It would be good to just put in an inline XML comment like the one we used to have for 1.6.0:  https://github.com/apache/accumulo/blob/631386de49bbc351411ce0e3c49982f1df998fe9/pom.xml#L742

Just for context, the workarounds others have suggested in the ticket do work. Both "-p" and --parents

Just for context, the workarounds others have suggested in the ticket do work. Both "-p" and --parents

I'd rather wait for the upstream bug to be fixed, rather than use these workarounds. Hacking the quote parsing for the short option seems fragile, and using the long option won't work on non-GNU systems like BSD. There's no reason the plugin should be doing anything with the arguments passed to the executable at all. We can leave this at the current version for now.


Non-Issue: Just wanted to compliment you on your solution

I was looking at dabbling into some card/boardgame mechanics and thought solitaire would be a good start. As I got into it, I quickly realized it wasn't going to be straight forward due to mouse handling events. I tried a few different things but couldn't land on a solid implementation. I was about to go with a solution where I adjusted the hitbox to just the visible area depending on where it was in the stack. I think it would have worked for solitaire but felt it would come up short when I started working on other card games and mechanics. I started looking around for other ideas and came across your project and was pleasantly surprised by your solution. Processing all cards clicked and determining topmost is a clever way to deal with Area2D hover challenges. Just got started so looking forward to learning more from your project. Thanks for sharing it. I'll be watching for sure. Let me know if your on itch.io or twitter.

Thank you for the compliment, you made my day. This was my second Godot project and this was an issue I spent so much time trying to fix as I didn't see any elegant solutions online. I created this repository in the off-chance that it would help someone and I'm glad it did. By the way, this is my itch.io profile :)


Android - support HLS/DASH audio streaming on ExoPlayer

Android MediaPlayer is not support m3u8 which is HLS or DASH streaming.
Google ExoPlayer is good alternative.
https://github.com/google/ExoPlayer
https://github.com/florent37/Flutter-AssetsAudioPlayer/blob/master/android/src/main/kotlin/com/github/florent37/assets_audio_player/playerimplem/PlayerImplemExoPlayer.kt
https://github.com/luanpotter/audioplayers/issues/545

There is an alternative plugin with the almost same api on exoplayer2.
https://pub.dev/packages/flutter_exoplayer


Request: Start/End Dates, Airing data in user lists

Currently there does not appear to be a non-abusive way of gathering all the start/end dates for items. Airing data is less of an issue thanks to the browse API covering all shows of interest but it would still be nice to be able to get it from list requests.

Yeah the small data models are just too restrictive at the moment, and other no customizability for additional fields like start/end date, something I do want to change. I'm super busy at the moment so I don't know when I'll be able to look into this, but even when I do I'm not sure its something we can much about with the current API setup.
The API was kind of intentionally made restrictive with things like dates and full data models in an effort to stop people from creating super quick anichart clones, but I'm not sure that was the best idea in hindsight and I don't think the cloning issue is that big of a worry anymore.
Anyway I think this may be something we have to leave until APIv2, which won't be until after we open source, probably Q1 next year, sorry.

No worries, hope to see it next year!


⚠ Bofrost.fr has degraded performance

In 81c4678, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1187 ms

Resolved: Bofrost.fr performance has improved in 02115cf after 6 minutes.


Offer monthly subscription

Saas version should allow user to subscribe on a monthly basis
This require to update current paiment method improve the integration within strip.

Let's focus on making the app great first. Closing now.


Support TLS client certificates

As in the RabbitMQ input plugin, the output plugin should supprt client certificates as well:
https://github.com/logstash-plugins/logstash-input-rabbitmq/issues/27

That fact is surprised me. +1, of course.
I had to use rabbitmq shovel plugin instead.


Is it "TOKEN" or "GH_TOKEN"?

The code and my failed workflow seems suggesting me to use "TOKEN", while the doc says "GH_TOKEN".
I think it should be "TOKEN" per the code?

Hi @iveney
Thank you for your using this action. And for the "TOKEN", you should follow below:
About how we to provide permissions for this action to push to the gh-pages branch:

Create a Personal Token with repos permissions and copy the value.
Go to your repository’s Settings and then switch to the Secrets tab.
Create a token named GH_TOKEN (important) using the value copied.

Thanks and regards

Hi @iveney
Thank you for your using this action. And for the "TOKEN", you should follow below:
About how we to provide permissions for this action to push to the gh-pages branch:

Create a Personal Token with repos permissions and copy the value.
Go to your repository’s Settings and then switch to the Secrets tab.
Create a token named GH_TOKEN (important) using the value copied.

Thanks and regards

Thanks! Somehow it didn't work at the first try. GH_TOKEN does work for me now.

Thanks! Somehow it didn't work at the first try. GH_TOKEN does work for me now.


[ENH] refactored ColumnConcatenator, rewrite using pd-multiindex

This PR is a rewrite of the ColumnConcatenator, using pd-multiindex.
Originally in https://github.com/alan-turing-institute/sktime/pull/2369.
The conversion issues are fixed now, should all be good to go.

from first post:
Unfortunately, this has dredged up all kinds of issues with type casting and conversion, so I am isolating it to one PR and removing it from #2369.
The failures in this refactor are linked to the failures in the conversions here: https://github.com/alan-turing-institute/sktime/pull/2375, since in the tests we make conversions between the nested data frame format and the pd-multiindex format.

Test failure is due to #1290 - the old ColumnConcatenator with its byzantine code was apparently able to cope with repeated instance indices, whereas the pandas native functionality breaks. Fix in #3029.


click on search result showing 404 error

when I search and click on one of the result it will go to a link like this https://syntax.fm/shows/448/potluck-multi-tenant-apps-js-sprinkles-kids-coding-server-error-handling
I need to change shows => show to make the page display. https://syntax.fm/show/448/potluck-multi-tenant-apps-js-sprinkles-kids-coding-server-error-handling

Ah another victim of the /shows/ show/ switch on it.

Didn't mean to close, but a fix is going up now.


To dataframe

Proposed changes
Pandas dataframes are very efficient and are the standard for many visualisations, statistics and machine learning librairies.
Therefore, I added a to_dataframe method, which plays nicely with the update_misc method:
DATA_PATH = Path('your_data_path')
emgs_list = pd.concat(
    [
        Analogs3d.from_c3d(ifile, names=["delt_ant"])
        .update_misc({"group": "female", "filename": ifile.stem})
        .to_dataframe(add_misc=True)
        for ifile in DATA_PATH.glob("*.c3d")
    ]
)

Which outputs a single dataframe for all of the file present in the DATA_PATH dir:
      delt_ant   group   filename
0    -0.258042  female  12kg_H2_3
1     0.494952  female  12kg_H2_3
2     0.423346  female  12kg_H2_3
3     0.446372  female  12kg_H2_3
4     0.480231  female  12kg_H2_3
5     0.397767  female  12kg_H2_3

Types of changes
What types of changes does your code introduce?

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
You can also fill these out after creating the PR. This is simply a reminder of what we are going to look for before merging your code.

[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Codecov Report

Merging #46 into dev will not change coverage.
The diff coverage is 0%.

@@        Coverage Diff        @@
##           dev   #46   +/-   ##
=================================
  Coverage    0%    0%
=================================
  Files        6     6
  Lines      684   688    +4
=================================
- Misses     684   688    +4

Impacted Files
Coverage Δ

pyomeca/frame_dependent.py
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


'View Release Notes' action doesn't show on the update notification when running 'StorageExplorer.exe --add-update-group=CTI' to open Storage Explorer

Storage Explorer Version: 1.37.0-dev (103)
Build Number: 20241117.1
Branch: main
Platform/OS: Windows11/Linux Ubuntu 22.04/MacOS Sequoia 15.1(Apple M1 Pro)
Architecture: arm64/x64/arm64
How Found: From running test cases
Regression From: Previous release (1.36.2)
Steps to Reproduce

Install Storage Explorer on Windows.
Open cmd, navigate to where the Storage Explorer executable is located, run "StorageExplorer.exe --add-update-group=CTI".
Storage Explorer opens -> The update notification appears.
Check whether 'View Release Notes' action shows on the update notification.

Expected Experience
'View Release Notes' action shows on the update notification.

Actual Experience
'View Release Notes' action doesn't show on the update notification.

Additional Context
This issue also reproduces on Linux and Mac.

Due to a remote configuration issue. This has been mitigated.

Verified this issue on the build 20241119.1. Fixed.


Add ability to check version syntax

Description:
Add an optional input named valid-syntax which if used, will check that the version is following a particular syntax.
Use the npm package Glob to see if it can be used to see if it matches the pattern.

Acceptance Criteria:

[ ] If the version pulled from the project file matches, then action passes

Example: The action input valid-syntax value of 'v2.*.\0' for a version of v2.2.0 would pass

[ ] If the version pulled from the project file does not match, then the action fails

Example: The action input valid-syntax value of 'v1.*.*' for a version of v2.2.0 would fail

Closed.
Will be implemented with issue:

#10


Fix concurrent data race problem

Data race test failed when in concurrent systems.
The test code can be found here: #74

Can you fix this without using locks? In most cases, these things are initialised first thing and doesn't require locks.

Please fix this. We are using go-logging, and this issue keeps coming up for us. We use golang for the concurrency. There is a race condition flagged in the concurrent read/write access to the map. One module is trying to log a stmt(multi.go line 25 function Log, which calls IsEnabledFor), while another is initializing its logger (multi.go line 51, which calls SetLevel). There is a concurrent read/write to the map (level.go line 65, levels map[string]Level in type moduleLeveled struct). The library works awesomely, other than the intermittent failure it causes our application because of this race condition.

In implementation of glog includes(C++, Golang), the vmoudle is fixed in running time.In C++ version glog, they use macro to make static anonymous variable in every module to store the log level.So i think if you want to fix this, change the moudle usage and some tricky technology should be required.


bundle: update autogenerated files

commit the changes produced with
make
make manifests
make bundle

Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

/lgtm


cannot import name 'Deque'?

Been using websockets on my PC for a while, no problems.
Had to briefly test something on another colleague's PC, told him to also install this package, but he's having a weird exception, just when trying to import websockets. Here's the trace:
>>> import websockets
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\%username%\AppData\Roaming\Python\Python36\site-packages\websockets\__init__.py", line 3, in <module>
    from .auth import *
  File "C:\Users\%username%\AppData\Roaming\Python\Python36\site-packages\websockets\auth.py", line 15, in <module>
    from .server import HTTPResponse, WebSocketServerProtocol
  File "C:\Users\%username%\AppData\Roaming\Python\Python36\site-packages\websockets\server.py", line 49, in <module>
    from .protocol import WebSocketCommonProtocol
  File "C:\Users\%username%\AppData\Roaming\Python\Python36\site-packages\websockets\protocol.py", line 18, in <module>
    from typing import (
ImportError: cannot import name 'Deque'

We're both using Python 3.6. I was using websockets 7.0 before, but the colleagues installed the newest 8.0.2. I then also updated to the newest version, yet I still have no problems, while the colleague does.
Any idea what that could be?

Perhaps this is the same issue as #664? If your colleague has Python 3.6.0 and you have 3.6.1 or later, that would explain the problem.


Add Solid logo

Solid is an exciting new project led by Prof. Tim Berners-Lee, inventor of the World Wide Web, taking place at MIT. The project aims to radically change the way Web applications work today, resulting in true data ownership as well as improved privacy.
https://solid.mit.edu/assets/img/solid-logo.svg

Added in a339cabb020a1fc0d9f9df7cf55dd7d5802a55d9
Thanks


Fixes build on unixes by swapping sprintf_s to snprintf.

Recent updates introduced dependency on API available only on windows. PR addresses the issue and ImGuizmo now builds on unixes once again. Also had to swap abs to std::abs as on some platforms that failed to compile as well. Builds are passing on windows/linux/macos with these changes.

Thanks!


fzf cannot find any files

Installed both fzf and fzf.vim on a friend's device using vim-plug. fzf is not able to find any files. The list of files is always 0/0. Tried from both shell and vim, same result. Tried different directories, same result.
Opening Tags from inside vim works. It shows the list of tags from ctags file and I'm able to search through them.
What can be wrong here?

When $FZF_DEFAULT_COMMAND is not set, fzf uses find command to list the files. Check if this command works as expected:
find . -path '*/\.*' -prune -o -type f -print -o -type l -print 2> /dev/null | sed s/^..//

FZF_DEFAULT_COMMAND is set in bashrc like following.
export FZF_DEFAULT_COMMAND='if [ -f cscope.files ]; then cat cscope.files; else find ./ -type f ; fi'
I tried your command too, it works.
Is there any debugging that can be enabled to collect more information?

So, does it work when you unset the variable?

Turns out $SHELL was defined to /bin/csh instead of /bin/bash. I fixed that and everything's working fine.
Thanks.

Just wanted to stop by to say the $SHELL -c "$FZF_DEFAULT_COMMAND" helped me debug this as well. My FZF_DEFAULT_COMMAND was set up to use ripgrep but I was passing in an invalid argument.
My FZF_DEFAULT_COMMAND was set up as:
export FZF_DEFAULT_COMMAND='rg --files --hidden --smartcase --follow --glob "!.git/*"'
Which produced this following error:
error: Found argument '--smartcase' which wasn't expected, or isn't valid in this context
    Did you mean --smart-case?

Changing it to use the correct --smart-case argument fixed the issue.


cherry pick recent fixes

Cherry-picking recent fixes for validation and hopefully shipping.
@KevinPi @KevinR @cartermp

Yes, loc freeze was 7/21.


Pipelining and continuous deployment support grayscale releases [blue-green, canary]

What is version of KubeSphere DevOps has the issue?
v3.2.1、v3.3.0-rc、All versions
How did you install the Kubernetes? Or what is the Kubernetes distribution?
install by kubeasz tool
Describe this feature
After the image is built, switch from DevOps project to project, open the grayscale release page, and enter the image name to create the blue-green deployment and canary release tasks. I don't think it's more convenient to use the grayscale publishing process this way.
Planning to integrate blue-green deployments and canary releases into continuous deployment to string together the entire release process? That is, every time the pipeline is executed, when the release step is reached, the blue-green or canary release can be selected.
Additional information
No response

this was duplicated with https://github.com/kubesphere/ks-devops/issues/682
Considering these two issues both come from you. And #682 has more details. I'm going to close this one.
/close


de-assoc-v-lex should allow adjectives and verbs

verb -> +vj
fix after submitting!

It should also probably have a qeq in there to allow for quantifier scope


Insomnia Docs Endpoint Error

The documentation here describes a GET request that returns a book based on a user-specified book ID variable:
app.get("/api/book/:id", (req, res) => {
 let book = books.find((book) => book.id === req.params.id);
 res.send(book);
});

This endpoint does not work for me because req.params.id is a string while book.id is an int.
Changing req.params.id to an int like so fixes the issue:
app.get("/api/book/:id", (req, res) => {
 let book = books.find((book) => book.id === parseInt(req.params.id));
 res.send(book);
});

The same issue appears in the DELETE request section:
app.delete("/api/book/:id", (req, res) => {
 books = books.filter((book) => book.id !== req.params.id);
 res.send(books);
});

should be:
app.delete("/api/book/:id", (req, res) => {
 books = books.filter((book) => book.id !== parseInt(req.params.id));
 res.send(books);
});


feat: add --set and --values options to 'helm package'

When 'helm package --set stringsArray' is run, this will set/override values
in the packaged chart. 'helm package --values valueFiles' uses one or more
value files to achieve the same.
Closes #3141
Signed-off-by: Arash Deshmeh<EMAIL_ADDRESS>

@bacongobbler Thanks. I have rebased the PR.

Because this is a size/L I'll have to grab another core maintainer to review before we merge. @SlickNik and @thomastaylor312, would one of you be available to review this?

We need to back this out. It introduces a serious backward-compatibility breaker, and renders the values.yaml file worthless as a source of documentation.
Because it parses values.yaml with the standard parser, all comments are removed from values.yaml before it is packaged. The primary point of the values.yaml file is to document for the chart user what values they can set, and what those values do. So a typically values file looks something like this:
# Name of the project, in the form "user/project"
project: "deis/empty-testbed"

# Domain/Org/Project
repository: "github.com/deis/empty-testbed"

# The definitive clone URL. This can be any Git-supported URL format.
# You may set this to "" for no clone URL.
cloneURL: "https://github.com/deis/empty-testbed.git"

# OPTIONAL: initGitSubmodules will recursively initialize all submodules in the repository. Default: false
# initGitSubmodules: "false"

# OPTIONAL: defaultScript is the brigade.js used by default when your VCS repo misses a brigade.js
# in it.
# defaultScript: |
#   const { events, Job } = require("brigadier")
#   function run(e, project) {
#     console.log("hello default script")
#   }
#   events.on("run", run)

# Used by GitHub and other services to compute hook HMACs.
sharedSecret: "IBrakeForSeaBeasts"

# OPTIONAL: Use this to have Brigade update your project about the build.
# This is REQUIRED for the GitHub gateway, but optional otherwise.
github:
#   token: "github oauth token"
#   ENTERPRISE: For enterprise GitHub customers, set both of these as well.
#   baseURL: "https://internal.github.url/foo"
#   uploadURL: "https://internal.github.url/foo"

# OPTIONAL: Use this for private repositories
# This is the PRIVATE key that Brigade will use to clone a private repo.
# You should generate a special key for this. Don't reuse another one.
# sshKey: |-
#  -----BEGIN RSA PRIVATE KEY-----
#  IIEpAIBAAKCAg1wyZD164xNLrANjRrcsbieLwHJ6fKD3LC19E...
#  ...
#  ...
#  -----END RSA PRIVATE KEY-----

# OPTIONAL: Items in the 'secrets' array can be mounted as environment variables by
# the brigade.js
#
# Example:
#
# In JS, do this:
#
#   events.push = function(e, p) {
#     j = new Job("example")
#     j.env= {"MY_ENV_VAR", p.secrets.myVar}
#   }
#
# And here, add this:
#
#   secrets:
#     myVar: "super awesome"
#
# Inside of the job's pod, $MY_ENV_VAR = "super awesome"
secrets:
  # Example:
  # username: hello

# OPTIONAL: Namespace into which builds will be deployed.
# Using this has implications for what you can access, so don't set this unless
# you know what you are doing.
# namespace: "default"

# OPTIONAL: vcsSidecar is the image that fetches a repo from a VCS
# The default sidecar uses Git to fetch a copy of the project.
#
# If this is not supplied, `deis/git-sidecar:VERSION` will be used, where VERSION
# is the version of this chart.
#
# If this is set to NONE, no sidecar is used.  This may improve performance
# very slightly, but will break some gateways or cause the default script to
# be used.
vcsSidecar: "deis/git-sidecar:latest"

# OPTIONAL: buildStorageSize is the size of the shared storage space used by the jobs
# buildStorageSize: "50Mi"

# Allow Jobs to run in privileged mode. This will allow features like
# Docker-in-Docker. This must be set to true before turning allowHostMounts
# on.
allowPrivilegedJobs: "true"

# OPTIONAL: Use this to allow host mounted docker sockets in your jobs.
# This is a big security risk if your project is public-facing; enable at your own risk.
# allowHostMounts: "true"

# Kubernetes-specific configuration options.
kubernetes:
  # OPTIONAL: Override the storage class used for storing job caches. This must
  # point to a readWriteMany volume provisioner.
  #cacheStorageClass: default
  # OPTIONAL: Override the storage class used for build storage. This must
  # point to a readWriteMany volume provisioner.
  #buildStorageClass: default

###
# ADAVANCED
###

# OPTIONAL: specify an alternative command that the worker pod should run on startup.
# For example, if you want the typescript compiler to re-run, replace this with
# 'yarn build-start'. The default is 'yarn -s start' (-s is for silent).
# Uncomment the line below to increase logging verbosity.
# workerCommand: "yarn start"

# OPTIONAL: Project-specific worker settings which takes precedence over brigade-wide settings
# Useful when you want a specific brigade-worker image for running brigade.js of this project.
worker:
  #registry: deis
  #name: brigade-worker
  #tag:
  #pullPolicy: IfNotPresent

But with this patch, the above is transformed into:
allowPrivilegedJobs: "true"
cloneURL: https://github.com/deis/empty-testbed.git
github: null
kubernetes: null
project: deis/empty-testbed
repository: github.com/deis/empty-testbed
secrets: null
sharedSecret: IBrakeForSeaBeasts
vcsSidecar: deis

That version of the values.yaml is then written into the package. That means all of the documentation on setting values is completely lost in the package.
Now, the point of helm inspect values was to dump the values file pre-install so that people could configure a chart before it was merged:
$ helm inspect values foo > my-values.yaml
$ # edit my-values.yaml
$ helm install foo -f my-values.yaml

In order to use that flow, we now need some other extrinsic source of documentation, and it's not clear exactly what that source of documentation would be.
Consequently, this PR needs to be backed out until the documentation issue is 100% fixed in a backward-compatible way.

Thanks for catching this @technosophos! Unfortunately, I didn't realize that this was a side effect of the fix when I took a look at it earlier. 😐
Also thanks for the quick update with the revert fix @bacongobbler!

Looks like there should be additional unit tests to verify that package preserves comments in values files.

hey @nprogers-WPE, our team is quite small so we're primarily focused on ensuring there are regular releases of Helm, though if someone were to address @technosophos's concern that would be a good start. :)

Hi @bacongobbler
do you think it will be reasonable to create a new file (pkg-time-values.yaml) instead of merging/rewriting existing values.yaml. we can then merge this new file with original values.yaml file at install/upgrade time? that way it will be backward compatible as well as support new feature.
do you have other ideas in mind about how else it could work. will be great to hear them.
Many Thanks
Rajat Jindal

The chart spec for Helm 2 is set in stone at this point, so we could not add another file. Doing so would, in fact, be backward compatibility breaking, since installing the same chart with Helm pre-patch and post-patch could have drastically different outcomes.
Additionally, adding another file will introduce some new UX issues. For example, what does helm inspect values output in this scenario?
You could try to merely append the --set params to the end of the file, but that will have some odd side effects (like nested objects having pieces overwritten).
I suppose you could remove support for --set and just support -f, in which case you could completely overwrite (replace) the values.yaml instead of merging. It would place more work on the person doing helm package, but that seems like a worthwhile trade-off when it comes to not breaking anything.
FWIW, for Helm 3 you could still get in a feature request for your pkg-time-values.yaml idea.

That seems an overly restrictive view of backward compatibility. With that policy it would not be possible to ever extend the chart format within a minor version. It would also prevent fixing any bugs in the implementation of chart reading, as installing the same chart with Helm pre-fix and post-fix could have drastically different outcomes.
A more practical policy would recognize that artifacts relying on a feature added to a format are intended to be used only with readers that have added support for the feature. It would be good if the format allowed for extension in a way that permitted old readers to detect that they shouldn't handle objects using the unrecognized extension, but the Helm 2 chart format appears to be missing that ability.

Has it been released ?

Was it released?
This command packages a chart into a versioned chart archive file. If a path
is given, this will look at that path for a chart (which must contain a
Chart.yaml file) and then package that directory.

Versioned chart archives are used by Helm package repositories.

To sign a chart, use the '--sign' flag. In most cases, you should also
provide '--keyring path/to/secret/keys' and '--key keyname'.

  $ helm package --sign ./mychart --key mykey --keyring ~/.gnupg/secring.gpg

If '--keyring' is not specified, Helm usually defaults to the public keyring
unless your environment is otherwise configured.

Usage:
  helm package [CHART_PATH] [...] [flags]

Flags:
      --app-version string       set the appVersion on the chart to this version
  -u, --dependency-update        update dependencies from "Chart.yaml" to dir "charts/" before packaging
  -d, --destination string       location to write the chart. (default ".")
  -h, --help                     help for package
      --key string               name of the key to use when signing. Used if --sign is true
      --keyring string           location of a public keyring (default "/home/damian/.gnupg/pubring.gpg")
      --passphrase-file string   location of a file which contains the passphrase for the signing key. Use "-" in order to read from stdin.
      --sign                     use a PGP private key to sign this package
      --version string           set the version on the chart to this semver version

Global Flags:
      --debug                       enable verbose output
      --kube-apiserver string       the address and the port for the Kubernetes API server
      --kube-as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups.
      --kube-as-user string         username to impersonate for the operation
      --kube-ca-file string         the certificate authority file for the Kubernetes API server connection
      --kube-context string         name of the kubeconfig context to use
      --kube-token string           bearer token used for authentication
      --kubeconfig string           path to the kubeconfig file
  -n, --namespace string            namespace scope for this request
      --registry-config string      path to the registry config file (default "/home/damian/.config/helm/registry/config.json")
      --repository-cache string     path to the file containing cached repository indexes (default "/home/damian/.cache/helm/repository")
      --repository-config string    path to the file containing repository names and URLs (default "/home/damian/.config/helm/repositories.yaml")