Delete docs/operating/installation/setup_kubernetes.md

The document deletion is requested in  https://neonlabs.atlassian.net/browse/DOPS-617 as the content is outdated and duplicates outer documentation https://docs.k0sproject.io/head/install/

Straight forward file delete PR - no issues found.


Python logging page missing usage examples

This page (https://googlecloudplatform.github.io/google-cloud-python/latest/logging/usage.html) does not provide any information on using the TextEntry objects returned by the logger's list_entries() method. I could not find any other documentation online to describe the attributes or methods for this object. Would it be possible to flesh out the documentation to include an example or two related to the logging entries?

@waprin Do you know if there are docs for this?

@stew-r @dhermes is this helpful? https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry

That matches up pretty closely with the attributes of the TextEntry object, though not perfectly (e.g., "insertId" vs. "insert_id"). My point was simply regarding capturing a common use case in documentation.


chore: add basic badges to readme

If we would like to add a test coverage badge, we would need to utilize some 3rd part service like Codecov or Coveralls.

I was using coveralls for a few years, and I am not ready to step into that shithole again, their platform keeps failing randomly (breaking builds for no reason), and the UI/UX is weird/ugly at best. Moved to covecov some time ago, and its much better, I am fine with that.


Not able to read body params in RecordAuthWithPasswordEvent

PocketBase JS SDK's authWithPassword function allows you to send bodyParams and queryParams
const authData = await pb
    .collection('users')
    .authWithPassword(
      'test',
      'test',
      { captchaFromBody: 'hello world' },
      { captchaFromQueryParam: 'hello world' },
    );

Here in the Go code, I'm trying to read those body params
app.OnRecordBeforeAuthWithPasswordRequest().Add(func(e *core.RecordAuthWithPasswordEvent) error {

   	// Get request body
   	bodyParams := GetJSONRawBody(e.HttpContext)

   	// Get request params
   	queryParams := e.HttpContext.QueryParams()

   	log.Printf("%v", bodyParams)
   	log.Printf("%v", queryParams)

   	return nil
   })

func GetJSONRawBody(c echo.Context) map[string]interface{} {
   jsonBody := make(map[string]interface{})
   err := json.NewDecoder(c.Request().Body).Decode(&jsonBody)
   if err != nil {
   	return nil
   }
   return jsonBody
}

In the CLI, the queryParams are arriving as expected, while the request body is an empty map.

I assume this is because the body was read before the RecordAuthWithPasswordEvent was emitted, and the body parameters were not passed to the event.
https://github.com/pocketbase/pocketbase/blob/0c5305c1744f2041b135d963c684c0a3369c6a42/apis/record_auth.go#L268-L279

You can't read the body once it is already read because it is a stream (the hooks are fired after loading and initializing the corresponding request action).
You can use the apis.RequestInfo() to get a copy of the previously read request body.
I'll consider documenting it better sometime later next week.


replace and and or with && and ||

Add changes from version 0.8

@max-sixty is it correct that and and or are removed as keywords?

@max-sixty is it correct that and and or are removed as keywords?

Yes correct! It's a straight swap.


Doesn't work with 10.0.22631 Build 22631

I used this patch for some time, but now I see round corners again. Re-Applying dones't work eighter. The Output tells me a success, but after a restart I still see round corners.
My Windows version is 10.0.22631 Build 22631.

Still works for me, I'm also running build 22631, you should not have to restart for the program to work.
Maybe an issue with your Defender/Anti-Virus software?

Thanks for the feedback! I use Sophos as virus scanner, but unfortunately I don't have access to the settings.
If it still works for you, then something on my computer must be preventing the patch from working.


1D dynamic Convolution

why there is no implementation to 1D Dynamic Convolution?

Hello,
Implementing 1D Dynamic Convolutions was not needed for our purposes. However, the 2D code can easily be adapted to do 1D convolutions. Please feel free to implement it and submit a pull request.


error

Hello, there may be some errors in your code about Y-Net. When calculating the Dice of the fluid, if there is no truth value and prediction image, the Dice calculated by your code is 2. By correcting your code, I got 0.66 for Dice for Duke datasets fluid.
def per_class_dice(y_pred, y_true, num_class):
avg_dice = 0
y_pred = y_pred.data.squeeze() #.cpu().numpy()
y_true = y_true.data.squeeze() #.cpu().numpy()
dice_all = np.zeros(num_class)
for i in range(num_class):
GT = y_true[:,:,i].view(-1)
Pred = y_pred[:,:,i].view(-1)
#print(GT.shape, Pred.shape)
inter = (GT * Pred).sum() + 0.0001
union = GT.sum()  + Pred.sum()  + 0.0001
t = 2 * inter / union
avg_dice = avg_dice + (t / num_class)
dice_all[i] = t
return avg_dice, dice_all

I found the same error and I got 0.66 for Dice for Duke datasets fluid too.

Same doubt. Is it correct?

This is definitely an error and leads to false average Dice scores for the validation and test. Dice loss, however, should be computed correctly. Check out my pull request for a fix: https://github.com/azadef/ynet/pull/6


CI testing - automatic code coverage reports

This PR investigates adding code coverage reports to the CI.
Included in this PR:

Switch to pytest (previously unittest was used)
Generate code coverage reports (using pytest-cov)
Uploads code coverage to codecov.io
Reduces duplication of CI runs, by adjusting the triggers for the github actions workflow
Switches to micromamba for the CI (instead of miniconda combined with mamba). This creates our test environment in about half the time that miniconda did. It saves about a quarter of the overall CI job time (there aren't a lot of tests right now, so the environment setup is a large proportion of the CI runtime)

When this PR is ready to merge:

We'll need to add a secret key to the repository, so the upload to codecov.io can happen automatically, and
We should absolutely consider squash merging this PR, the commit history is very messy

We'll need to add a secret key to the repository, so the upload to codecov.io can happen automatically.

Ok! Do you have enough permissions here to do this, or do I need to create the key?

No, I don't have permissions to do that. You'd need to go into this section of the settings to add a CODECOV_TOKEN repository secret, the contents of the secret is whatever codecov tells you when you set up the repository: https://about.codecov.io/product/getting-started/
But his is all a bit premature, because for some reason I can't get codecov to actually find and upload the file! Here's me testing things unsuccessfully: https://github.com/GenevieveBuckley/micro-sam/pull/1#issuecomment-1736890023

Thanks for the link @GenevieveBuckley , I will add the token at some point today.

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

Ok, I figured out the problem, and now it's working well. This PR is now ready for review & merge.
Test coverage of the micro_sam directory is ~16%. You can play around with the results here: https://app.codecov.io/github/GenevieveBuckley/micro-sam/pull/1/tree/micro_sam
You can also run pytest on your local repository, and it will generate the coverage.xml output automatically. Then you can use the VSCode Coverage Gutters extension (or similar) to easily see which lines of code are not covered by the tests.

Hi @GenevieveBuckley ,
I have added the codecov secret now:

so I think codecov should be able to upload the test reports once we merge this.
From my end this can be merged once the conflict is fixed and the commits are squashed. Let me know if you need anything from my end for this!

Fixed! I think this is ready for merge now @constantinpape

Hmm, I don't love that codecov isn't already uploading the coverage information. I think that should be happening now, even before merging.

Details (click to expand)
Codecov report uploader 0.6.3
[2023-10-16T01:31:05.677Z] ['info'] => Project root located at: /home/runner/work/micro-sam/micro-sam
[2023-10-16T01:31:05.679Z] ['info'] -> No token specified or token is empty
[2023-10-16T01:31:05.689Z] ['info'] Searching for coverage files...
[2023-10-16T01:31:05.749Z] ['info'] => Found 1 possible coverage files:
  ./coverage.xml
[2023-10-16T01:31:05.750Z] ['info'] Processing ./coverage.xml...
[2023-10-16T01:31:05.755Z] ['info'] Detected GitHub Actions as the CI provider.
[2023-10-16T01:31:05.946Z] ['info'] Pinging Codecov: https://codecov.io/upload/v4?package=github-action-3.1.4-uploader-0.6.3&token=*******&branch=codecov-report&build=6527844768&build_url=https%3A%2F%2Fgithub.com%2Fcomputational-cell-analytics%2Fmicro-sam%2Factions%2Fruns%2F6527844768&commit=d44878227ddd77920ec487ec1b5ecb46e34c38d9&job=test&pr=214&service=github-actions&slug=computational-cell-analytics%2Fmicro-sam&name=&tag=&flags=&parent=
[2023-10-16T01:31:06.139Z] ['error'] There was an error running the uploader: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}

It works! 🎉 🎉 🎉
You can see it on codecov here. Your new secret token works.
Note: this is purely for information - the CI build will not fail if codecov fails to upload the results, and we also won't flag any PRs that decrease code coverage. But it will be useful in the future, to see what to target to improve the test suite most effectively.

Lessons learnt: it is better to pass your secret token in to the with argument, and not env.
Like this (which is actually how they say you should use it):
      - name: Upload coverage reports to Codecov
        uses: codecov/codecov-action@v3
        with:
          token: ${{ secrets.CODECOV_TOKEN }}
          file: ./coverage.xml
          verbose: false
          fail_ci_if_error: false


Optimizing User Experience: Implementing Hyperlinks with New Tab Functionality.

Incorporating hyperlink functionality in the comment section. When users click on the provided link, it should seamlessly direct them to the associated webpage, opening in a new tab for a smoother browsing experience.
How to reproduce.

Hey @hkirat
I have implemented comments with hyperlinks here: https://github.com/code100x/cms/pull/128
please check the PR, Thank you

I'm able to login with the provided userid and password from readme but its not fetching the courses.


Read-only mode doesn't play well with GraphQL

It should be able to handle updates on the fly. Currently, initialConfig forces it to take the first and ignore the rest. There should be an easy built-in way (maybe)

I don't think we want to make such a large breaking change now. Closing for now.


Disable S3 tests

We currently have some problems with our S3 test account, which won't get resolved for at least a few days, and are blocking some important PRs.

lgtm


Using Conductor.Collection.AllActive for multiple unique user controls

I am attempting to use Conductor.Collection.AllActive to house multiple unique UserControls within one screen.
When binding to the Items collection of a conductor, how can I specify which VM will be used in a ContentControl?
This seems to work:
<ContentControl s:View.Model="{Binding Items[0]}" />
However, when I close the screen, I get this error:
System.Windows.Data Error: 17 : Cannot get 'Item[]' value (type 'IScreen') from 'Items' (type 'BindableCollection`1'). BindingExpression:Path=Items[0]; DataItem='MainViewModel' (HashCode=48883615); target element is 'ContentControl' (Name=''); target property is 'Model' (type 'Object') ArgumentOutOfRangeException:'System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: index'

My assessment from the error is that the VM is being deleted before the View, and it's trying to directly access an array element that doesn't exist any more. I don't get a crash, just an error in the console.
My main view is a UserControl split into sections which each house its own UserControl. I want to be able to specify which Item from the Conductor's Items collection each UserControl uses. Is there a better/safer way than accessing the Items collection at a specific element?

I think your assessment is correct.
If you're not binding Items to an ItemsControl (and you're instead binding UI controls to specific child VMs), I wouldn't bother with a conductor. I'd do:
public class MainViewModel : Screen
{
    public SomeViewModel SomeViewModel { get; }
    public OtherViewModel OtherViewModel { get; }

    public MainViewModel(...)
    {
        SomeViewModel = ...;
        SomeViewModel.ConductWith(this);

        OtherViewModel = ...;
        OtherViewModel.ConductWith(this);
    }
}

Then bind directly to SomeViewModel and OtherViewModel.

Oh, that's beautiful. It works perfectly.
This might be worth mentioning on the Conductors wiki page, because wow, that is so useful.
Thank you for this awesome framework!

That's fair, I'll update the wiki page.
(That particular bit of functionality was copied from Caliburn.Micro)


Update AzureLoginView.js

Webview is being removed from React Native core and to a separate library - https://facebook.github.io/react-native/docs/webview

Would be great to get this merged as the web view being imported from react-native breaks the build now.  Great package, by the way, super helpful.


Try-it UI issues

 Issue by NatashaWso2
Tuesday Nov 21, 2017 at 04:37 GMT
Originally opened as https://github.com/ballerina-lang/composer/issues/4673

Description:
The UI issues of Try-it are referenced here.

[ ] Adjust the response view layout when window is resized

[ ] Fix adding and deleting of headers

[ ] Disable method body for GET request

[ ] Adjust the input text when the service name is lengthy

Suggested Labels:
Bug
Affected Product Version:
0.95.1
Related Issues:
#3670
#3710
#4512
#4597

Fixed in 0.973.0


Breakpoints + Wraparound Not Working with Dynamic List Length

Bug Description
I upgraded vue3-carousel in my project from v0.3.1 to v0.9.0 yesterday, and it is causing an infinite loop that crashes my computer if the number of items in the carousel is equal to the max amount of items visible.
I am using ajax calls to load carousel slide data from server side, so I had written the breakpoints as a computed property since the number of slides may be different for each user. This worked perfectly fine before I upgraded my version, but after upgrading I have found that if the number of items available to the user is 4 or less, the carousel component will cause a runtime error in an infinite loop.
I have isolated the problem, and it seems like there may be something conflicting between the breakpoints and having wrapAround turned on. I tested using static breakpoint values with no wrapAround, and it seemed to work, and I tested using wrapAround with no breakpoints and it works fine, but even if I use static breakpoints with wrapAround, I am experiencing the infinite loading.
I have confirmed that if I test the feature using an account with more than 4 items available, the Carousel component works exactly as expected. I did see this feature request in the issues already, so I'm assuming this may be a known issue, but I am already performing validation on the breakpoints to ensure that the value of itemsToShow does not exceed the number of items available and I am still experiencing this problem. I also tried loading the page with the window already resized to see if it would work if the initial width of the Carousel was smaller than the max width of the items, and it still caused the runtime issue.
To Reproduce
Steps to reproduce the behavior:

Install vue3-carousel in Vue/Vite project
Follow basic vue3-carousel example for setting up a Carousel component with Navigation.
In the settings config for the Carousel component, include wrapAround: true and values for the breakpoints property.
Load the Carousel with a data object containing a number of items that is equal to the maximum value defined for itemsToShow.
Build project and deploy to development environment.

Expected behavior
The Carousel should display a number of Slides based on the width of the viewport and the Carousel should wrap around to the first Slide if it reaches the last Slide in the list. Carousel should disabled wrap around only if the total number of Slides is equal to the maximum value of itemsToShow, and should enable wrap around if the viewport is resized to a width that correlates to a breakpoint with a value for itemsToShow that is less than the total number of Slides.
Console Error
I get thousands of instances of this type of error in the console when the page tries to load:
TypeError: can't access property "vnode", n[((s + n.length) % n.length)] is undefined
Desktop (please complete the following information):

OS: Windows 10
Browser: Firefox Developer Edition
Version: vue3-carousel [v0.9.0], vue [v0.9.0], vite [v6.0.3], @vitejs/plugin-vue [v5.2.1]

Additional context
Here are is a full example of my code (with any identifying specifics removed) that was working as expected prior to updated to v0.9.0.
I apologize for the long block of code, but the reason I have so many breakpoints is because the slides need to remain the same width even if the width of the carousel changes, and the values jump around because the layout of the page changes at different screen sizes.
<template>

Title

			<select
				ref="itemsFilter"
				class="filter"
				v-on:change="filterItems"
			>
				<option value="newest">Newest</option>
				<option value="oldest">Oldest</option>
				<option value="type">Type</option>
				<option value="alpha-az">Alphabetical A-Z</option>
				<option value="alpha-za">Alphabetical Z-A</option>
			</select>

			<Carousel ref="myCarousel" v-bind="settings" v-model="selectedItem" :breakpoints="breakpoints">
				<Slide v-for="slide in filteredItems" :key="slide">

				</Slide>

				<template #addons>
					<Navigation>
						<template #next>

						</template>
						<template #prev>

						</template>
					</Navigation>
				</template>
			</Carousel>

</template>

I left in both the computed breakpoints and the hard-coded breakpoints, however please note I am experiencing this error even if I use hard-coded breakpoints and remove the ':breakpoints="breakpoints"' from the Carousel component. If I comment out either the wrapAround or the breakpoints property of the settings, it works and still loads, but with both of them together it does not work.
Before updating to v0.9.0, if the user clicked one of the items in the Carousel, it would automatically slide to that item, which worked with the wrapAround property because there were cloned slides. Although the wrapAround may not necessarily be needed if only 4 items are present (and I have classes denoting which item is selected) it would be nice if the carousel could still work in the same way even for 4 or less items because the breakpoints are still necessary if the user resizes the window.
I am open to any suggestions or corrections to my code if anyone can tell me how to make this work!
Edit:
Okay I actually had an epiphany just now that I can sort of get around it by changing my validation function to
const getItemsToShow = function(numShown) {
	return numItems > numShown ? numShown : numItems - 1
}

And this (almost) Works! I can load the page and it shows 3 out of 4 items, but if I resize the window, then it triggers the bug again... Regardless, I would still be submitting this as a bug even if the almost-solution worked perfectly because I would like to be able to show the maximum amount of viewable Slides if there is enough space to do so and not have to reduce the itemsToShow by 1 just to avoid this extreme bug.
If there is anything that can be suggested to help me solve this problem until this issue has been patched, I would greatly appreciated it as this is a live feature and I we have pending releases for it, so I need to solve it quickly and hope that it can work exactly as it did before the update!

I was able to get a working solution for the time being, although it is not exactly what I was hoping to achieve but it is certainly close enough and I have been wasting too much time on this so it will do for now until a better fix can be implemented!
I turned the wrapAround property into a computed property as well (not sure why it took me so long to think of that!) so that it's only set to true if the value of itemsToShow is less than the number of items in the data list.
I also implemented a fix that I found here from AndreyMyagkov, I'm not actually sure if it's even helping anything or if my new computed properties fixed it alone, but I don't want to bother with it anymore so I'm leaving it in for now!
(I also had to change some stuff about the way I was doing the slide selection on click, but that is unrelated to this bug report)
Updated Carousel component:
<Carousel ref="myCarousel" v-bind="settings" v-model="selectedItem" :wrapAround="wrapAround" :breakpoints="breakpoints">
	<Slide v-for="(slide, key) in filteredItems">

	</Slide>

	<template #addons>
		<Navigation>
			<template #next>

			</template>
			<template #prev>

			</template>
		</Navigation>
	</template>
</Carousel>

Added this outside the export function (from AndreyMyagkov)
const debounce = function (fn, delay) {
  let timerId;
  return function (...args) {
    if (timerId) {
      clearTimeout(timerId);
    }
    timerId = setTimeout(() => {
      fn(...args);
      timerId = null;
    }, delay);
  };
}

Updated data:
data: function() {
  return {
		isMounted: false,
    search: '',
    // carousel settings
    currentSlide: 0,
    settings: {
			itemsToShow: 1,
      snapAlign: 'center',
	    wrapAround: false,
	    gap: 6,
		}
  }
}

Added this under computed properties:
wrapAround() {
	if (!this.isMounted) return
	return this.$refs.petCarousel.data.config.itemsToShow < this.filteredPets.length
}

I reverted the getItemsToShow '-1' fix from my original edit, because it was no longer needed!
And then updated and added some more stuff:
methods: {
	selectPet(petName, index) {
		this.currentSlide = index
		this.$emit('load', petName)
	},
	filterPets(e) {
		this.search = e.target.value
		this.$refs.petCarousel.slideTo(0)
	},
	onResize() {
    if (!this.$refs.petCarousel) {
      return
    }
    this.$refs.petCarousel.updateSlidesData()
  }
},
mounted() {
	this.isMounted = true
  window.addEventListener('resize', debounce(this.onResize, 200), {
    passive: true,
  })
  setTimeout(() => {
    this.onResize();
  }, 500)
},
beforeUnmount() {
  window.removeEventListener("resize", this.onResize)
}

Now what it does is set wrapAround to false as long as the value of itemsToShow is greater than or equal to the number of slides. I don't love that it doesn't work exactly as it did before, but it works well enough and it is fine!
I still feel that there is a bug to be fixed here, as even with the validation checking I was performing on itemsToShow, I could only get it to work as long as itemsToShow < slidesCount, it was not working when itemsToShow = slidesCount as long as wrapAround was set to true.

Pretty sure this was fixed in #450

@dinahcoe v0.10.0 has been released, please confirm if this issue has been resolved

@dinahcoe v0.10.0 has been released, please confirm if this issue has been resolved

IT WORKS PERFECTLY NOW THANK YOU SO MUCH!
This was a very fast response! Granted, I think you were already working on these fixes before I posted, but it is just very nice to see problems being addressed in real time, thank you so much for your hard work! ^^


Update player details function to new api

Api 1.1.0 has a different way of getting player_details, change the bot to reflect this

fixed by changing api back to fit the bot


how to set the minimum possible reading distance, from the python script (L515)

Required Info

Camera Model
{L515}

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win10

Platform
PC

SDK Version
<IP_ADDRESS>2

Language
python

Segment
others

Issue Description
Hello, i'm working with L515 and python pyrealsense2. My question is related to tuning the camera to see the closest object possible. In the specs it's said around 25cm, but when i change some tunings in the viewer (short range mode, min distance slider, etc.), we get to see objects as close as ~5cm on the 3d viewer. It seems to me that I have to change the setup manually in the viewer, and then the camera saves it when run from python...  But I coulnd't find any example in python on how to do this directly from the code. Are there any examples of such code?
Thanks

I'm also looking for this issue.
In Viewer, you can see the depth image close by adjusting the Min Distance.
However, it cannot be checked when executed in Python code.
I would like to know the code to change this.

I'm also looking for this issue.
In Viewer, you can see the depth image close by adjusting the Min Distance.
However, it cannot be checked when executed in Python code.
I would like to know the code to change this.

I used that code that seems to work:
        import pyrealsense2 as rs
        pipeline = rs.pipeline()
        profile = pipeline.get_active_profile()
        profile.get_device().query_sensors()[0]  # 0 for depth sensor, 1 for camera sensor
        sensor.set_option(rs.option.min_distance, 0)
        sensor.set_option(rs.option.enable_max_usable_range, 0)

This, and maybe for a real close measurement, one might want as well to reduce the laser power below 50% (sensor.set_option(rs.option.laser_power, 80)) and keep receiver_gain rather high value (18 for me).
This reproduces some of the differences between the default mode and the close range mode.

Thanks agenis! That actually worked for me!
just one typo, instead of:
profile.get_device().query_sensors()[0]  # 0 for depth sensor, 1 for camera sensor
should be
sensor = pipeline_profile.get_device().query_sensors()[0]
again, thanks a lot!


intermittent assert failure (panic: not reached) in envoy

Bug description
I noticed istio proxy container restarting on my cluster. Looking at the log revealed:
[...]
2020-10-01T09:10:00.913518Z	info	Version 1.6.4-58f551e08f08addfd81783e1c2ed1eabeb836168-dirty-Modified
[...]
2020-10-01T09:10:03.923066Z	info	Envoy proxy is ready
2020-10-01T09:12:02.855677Z	critical	envoy assert	[external/envoy/source/server/connection_handler_impl.cc:79] panic: not reached
2020-10-01T09:12:02.855676Z	critical	envoy assert	[external/envoy/source/server/connection_handler_impl.cc:79] panic: not reached
2020-10-01T09:12:02.855734Z	critical	envoy backtrace	[bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] Caught Aborted, suspect faulting address 0x53900000010
2020-10-01T09:12:02.855740Z	critical	envoy backtrace	[bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
2020-10-01T09:12:02.855743Z	critical	envoy backtrace	[bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:92] Envoy version: 80ad06b26b3f97606143871e16268eb036ca7dcd/1.14.3-dev/Clean/RELEASE/BoringSSL
2020-10-01T09:12:02.904267Z	info	transport: loopyWriter.run returning. connection error: desc = "transport is closing"
2020-10-01T09:12:02.904288Z	info	sds	resource:default connection is terminated: rpc error: code = Canceled desc = context canceled
2020-10-01T09:12:02.904287Z	info	sds	resource:ROOTCA connection is terminated: rpc error: code = Canceled desc = context canceled
2020-10-01T09:12:02.904318Z	error	sds	Remote side closed connection
2020-10-01T09:12:02.904320Z	error	sds	Remote side closed connection
2020-10-01T09:12:02.904737Z	error	Epoch 0 exited with error: signal: aborted (core dumped)
2020-10-01T09:12:02.904748Z	info	No more active epochs, terminating

[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Does not crash.
Steps to reproduce the bug
:man_shrugging:
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
Not using istioctl. See proxy version string in log above.
$ kubectl version --short
Client Version: v1.19.1
Server Version: v1.17.11

How was Istio installed?
Through a kubeaddon.
Environment where bug was observed (cloud vendor, OS, etc)
Cluster created with konvoy 1.5.2

Full log attached.

Thank you for the report!
There is some unexpected update between generations of listener config.
The istio version is a little bit out of control:
2020-10-01T09:10:00.913518Z	info	Version 1.6.4-58f551e08f08addfd81783e1c2ed1eabeb836168-dirty-Modified
Depends on the underlying change, I am not fully sure where the unexpected is introduced.
Could you enable the envoy log level to trace so that we can track the config update?

@lambdai can you please clarify what you mean by:

istio version is a little bit out of control

AFAICT that binary came from a pristine istio image:
      image: docker.io/istio/proxyv2:1.6.4
      imageID: docker.io/istio/proxyv2@sha256:d9a8b340277c2a063117b3d438be2bb74474da7612e0c2612c52b2a0fc6dd8d2

Indeed:
porridge@beczulka:~$ docker run docker.io/istio/proxyv2:1.6.4 proxy versoin
Unable to find image 'istio/proxyv2:1.6.4' locally
1.6.4: Pulling from istio/proxyv2
d7c3167c320d: Pull complete
131f805ec7fd: Pull complete
322ed380e680: Pull complete
6ac240b13098: Pull complete
3aa85e7f6f52: Pull complete
c3700f3065fb: Pull complete
dcc6a60b3821: Pull complete
590317d8a83e: Pull complete
72f8b212c00e: Pull complete
32b49ca16f4d: Pull complete
6d88242ccf74: Pull complete
2f7057ec79ca: Pull complete
7840bd6fe42f: Pull complete
1b5aadc52a11: Pull complete
Digest: sha256:d9a8b340277c2a063117b3d438be2bb74474da7612e0c2612c52b2a0fc6dd8d2
Status: Downloaded newer image for istio/proxyv2:1.6.4
Error: Invalid role Type: versoin
2020-10-02T06:51:42.688035Z	info	FLAG: --concurrency="0"
2020-10-02T06:51:42.688062Z	info	FLAG: --disableInternalTelemetry="false"
2020-10-02T06:51:42.688067Z	info	FLAG: --domain=""
2020-10-02T06:51:42.688071Z	info	FLAG: --help="false"
2020-10-02T06:51:42.688074Z	info	FLAG: --id=""
2020-10-02T06:51:42.688077Z	info	FLAG: --ip=""
2020-10-02T06:51:42.688080Z	info	FLAG: --log_as_json="false"
2020-10-02T06:51:42.688083Z	info	FLAG: --log_caller=""
2020-10-02T06:51:42.688086Z	info	FLAG: --log_output_level="default:info"
2020-10-02T06:51:42.688088Z	info	FLAG: --log_rotate=""
2020-10-02T06:51:42.688092Z	info	FLAG: --log_rotate_max_age="30"
2020-10-02T06:51:42.688094Z	info	FLAG: --log_rotate_max_backups="1000"
2020-10-02T06:51:42.688098Z	info	FLAG: --log_rotate_max_size="104857600"
2020-10-02T06:51:42.688101Z	info	FLAG: --log_stacktrace_level="default:none"
2020-10-02T06:51:42.688106Z	info	FLAG: --log_target="[stdout]"
2020-10-02T06:51:42.688110Z	info	FLAG: --meshConfig="./etc/istio/config/mesh"
2020-10-02T06:51:42.688113Z	info	FLAG: --mixerIdentity=""
2020-10-02T06:51:42.688116Z	info	FLAG: --outlierLogPath=""
2020-10-02T06:51:42.688119Z	info	FLAG: --pilotIdentity=""
2020-10-02T06:51:42.688122Z	info	FLAG: --proxyComponentLogLevel="misc:error"
2020-10-02T06:51:42.688124Z	info	FLAG: --proxyLogLevel="warning"
2020-10-02T06:51:42.688127Z	info	FLAG: --serviceCluster="istio-proxy"
2020-10-02T06:51:42.688130Z	info	FLAG: --serviceregistry="Kubernetes"
2020-10-02T06:51:42.688133Z	info	FLAG: --stsPort="0"
2020-10-02T06:51:42.688136Z	info	FLAG: --templateFile=""
2020-10-02T06:51:42.688140Z	info	FLAG: --tokenManagerPlugin="GoogleTokenExchange"
2020-10-02T06:51:42.688143Z	info	FLAG: --trust-domain=""
2020-10-02T06:51:42.688163Z	info	Version 1.6.4-58f551e08f08addfd81783e1c2ed1eabeb836168-dirty-Modified
2020-10-02T06:51:42.688171Z	error	Invalid role Type: "versoin"
2020-10-02T06:51:42.688179Z	error	Invalid role Type: versoin
porridge@beczulka:~$

@lambdai I'd be happy to enable trace logging in envoy if you point me at some hint on how to do it :-)
I guess I'd need to configure the webhook which injects the container to add an additional flag? :thinking:

Unfortunately I've been unable to reproduce this again on another instance of my ephemeral cluster so far.
Posting the recipe for grabbing the logs to make others' life easier:

bump envoy logging verbosity by specifying the following in your helm chart values:

            global:
              proxy:
                logLevel: trace

alternatively, use the sidecar.istio.io/logLevel: trace annotation on the pod
get namespaces and names of pods with failing istio-proxy containers with something like kubectl get pods --all-namespaces -o json | jq -r '.items[] |  select ( .status.containerStatuses[] | select(.name == "istio-proxy")| .restartCount > 0 ) | .metadata | .namespace + " " + .name'
grab their logs with kubectl logs -n $ns $name -c istio-proxy


Open With Code context menu does not appear in Windows 11

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

VS Code Version: 1.84.1 (didn't work with the versions from 2 weeks ago too)
OS Version: Windows 11 Enterprise 64bit, 22H2, Build 22621.2283, Windows Feature Experience Pack 1000.22662.1000.0

This issue seems to have been reported before in #127365 (and several other issues), but even though it was closed as fixed, it still doesn't work for me.
Steps to Reproduce:

Install VS Code, check both "Add 'Open With Code' action..." checkboxes in the setup wizard.
After the setup finishes, right click on a file or directory:
Expected: "Open With Code" context menu is present
Actual: "Open With Code" context menu is missing. The menu appears in the "old" context menu.

I shot a short video showing what's happening: installing-vs-code.zip
Additional info:

My user is not administrator
When I run the setup as administrator, it complains that it is not designed to run as administrator, and the result is the same
To get administrator rights we use some software for elevation - "Admin by Request"
Both of my drives are encrypted with bit locker
This is a corporate computer, and it has applied administrative policies. If a policy is preventing VS Code from adding the context menu, let me know which one could be the problem and I can argue with our admins to disable it
Apparently Windows Terminal and WinRar are able to add context menus (as seen on the video)

AFAIK https://github.com/microsoft/vscode/issues/127365#issuecomment-1288635483 still applies, and only Insiders will insert an entry into the first-level Windows 11 context menu.
Pinging @joaomoreno for confirmation and perhaps a status update about when Stable will catch up.

Any idea when it is planned to be added for regular VSCode?

Adding the feature to stable is tracked under https://github.com/microsoft/vscode/issues/183297, please follow that issue for updates.
In the meantime, please check if you are able to get the menu added successfully with our insiders version https://code.visualstudio.com/insiders


flatcam: pin shapely at 1.8.4

Description of changes
Alternative to marking it broken: closes https://github.com/NixOS/nixpkgs/pull/216108

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Fine by me, if people are still using it and willing to put in the effort to keep it working.

Fine by me, if people are still using it and willing to put in the effort to keep it working.

I'm not using it. I'll remember to remove it if it breaks again.

Sorry for the delayed review. Longer term I think we will switch to their fork flatcam-beta, since indeed upstream is dead. That branch too is still on the older shapely, but it has a higher likelihood of switching in the future.


How to debug: Template format error: Resource name License 2 is non alphanumeric ?

I repatedly get the error: Template format error: Resource name License 2 is non alphanumeric after doing a few amplify push
I don't do anything special. Just small changes in the schema or a function. Then when it's time too push the update this error keeps coming up.
In transform.conf.json I can see things like:
{
    "Version": 5,
    "ElasticsearchWarning": true,
    "StackMapping": {
        "LicensemanagersResolver": "ConnectionStack 2",
        "ManagerlicenseResolver": "ConnectionStack 2",
        "LicenseTable": "License 2",

...

Why does this happen ? How do I debug this ? How do I fix it ?
Could a sync service like iCloud be responsible ?
My current schema:
enum InstitusjonsType {
  ungdomsskole
  vgs
  annen
}

type License @model
  @auth(rules: [
    { allow: public, provider: iam, operations: [read] },
  ])
{
  id: ID!
  eier: String
  gyldigFraDato: AWSDate
  aktiv: Boolean
  ressursnummer: String
  institusjonsType: InstitusjonsType
  kontaktperson: String
  kontaktpersonEpost: AWSEmail
  adresse: String
  postnummer: String
  sted: String
  brukerantall: Int
  betalt: Boolean
  managers: [Manager] @connection(name: "LicenseManagers", sortField: "name", limit: 20)
}

type Manager @model
  @auth(rules: [
    { allow: public, provider: apiKey },
    { allow: groups, groups: ["Admin"], operations: [create, update, delete, read] }
  ])
{
  id: ID!
  name: String!
  email: AWSEmail!
  license: License @connection(name: "LicenseManagers")
}

 amplify --version 4.24.1
node --version v10.17.0
os: mac

Transferring this to the Console repo, given that the issue is only happening on Console bulids.

Could you please share your appId and region?
And if possible could you share any steps to reproduce the issue (i.e. I cloned sample repo "X" and made these changes then ran amplify push)?

After moving my local repo outside icloud (no longer backed up by icloud, google drive, dropbox etc), I have not experienced this problem. If it coourc again, I will report to this hread.

I've been experiencing this issue too. I'll try @kjetilge suggested.

The problem also went away for me after doing the same thing in a non iCloud synced folder.
I think using an iCloud synced folder is the issue. @kjetilge

I am facing the issue despite moving the project to a non iCloud synced folder.
I started seeing this issue while running amplify push for the first time after deploying

@293nav , try deleting all the generate files and re-creating the amplify resources. you probably still have a bunch of the duplicate files in the amplify backend folder.

I have the same issue with amplify --version 4.32.1 on Mac Os Big Sur
it only started after I added sms notifications


Add mutation to clear user roles and facilities

BACKEND PULL REQUEST
Related Issue

Part of cleanup effort for bug introduced by #7828 where I was saving role and facility information for site admins when they ghosted into an organization

#7969 stopped saving site admin facility and role info when ghosting into orgs

Changes Proposed

Introduces a mutation that takes a user's email and marks their ApiUserRole and ApiUserFacility entries as deleted

Additional Information

Left the mutation flexible to be called on any user, but wrote a comment about the repercussions of calling the mutation on a non-site-admin user

will be ok to call this while the feature flag is off because user role and facility info will be repopulated but if this is called after the transition it will be an issue

Testing

deployed on dev2
call this mutation on a user that has role and facility entries populated, check in metabase they are deleted

mutation ($username: String!) {
    clearUserRolesAndFacilities (
        username: $username
    ) {
        nameInfo {
            firstName
        }
    }
}

@mehansen method has been renamed -- ready for rereview!

Paired with @mehansen to remove roles and facilities of prod site admin users on 08/05/2024.


#6 can integration

The PR follows the issue #6 and requests for CAN support. The PR allows all radar sensors along with all the user-interfaces to be connected with either ethernet, CAN or both. The PR requires new release and the binaries are not yet available hence the build would not pass.

The PR is ready to be reviewed.


Add Highlight option to ScrollService

The library implements highlighting for the SearchService but not for the ScrollService. Here is an addition for that.

Thanks. I will need to port this to 7.x as well.

@olivere https://github.com/olivere/elastic/pull/1190

Added to both 7.0.7 and 6.2.24.


Fix deprecation warnings for stdlib

This PR updates the standard library dependency and fixes the deprecation warnings, adding the gleam_regexp package instead of using gleam/regex

Thank you so much!! Looks like formatter is failing though

Fixed!

Thanks! 💜


Is it possible to run test coverage without installing node modules

I have already installed all the node modules in before running test coverage so can we skip the node module installation part

This issue as well as #20 was resolved thanks to @taschetto!
For now, until version 2.0 was released, you can try it by using @master version with this configuration:
name: 'coverage'
on:
    pull_request:
        branches:
            - master
jobs:
    coverage:
        runs-on: ubuntu-latest
        env:
            CI_JOB_NUMBER: 1
        steps:
            - uses: actions/checkout@v1
            - uses: artiomtr/jest-coverage-report-action@master
              with:
                  github-token: ${{ secrets.GITHUB_TOKEN }}
                  skip-step: all


Dependencies between issues

User story

As a SM
I want / need to know how to connect/create dependencies between issues
So that the project work of the whole team is structured more clearly.

Acceptance criteria

do research
inform POs asap

@codingwithelijah It seems not clear to me. What do you mean of issues? Issues in Product backlog or?

@cynthiachen28: Yes, I refer to issues in the product backlog or sprint backlog. Sometimes there are dependencies content wise. Could you check if you can link or connect certain issues? That we know: "Oh, Issue #33 belongs also to issue #22 and so on".

All right! I get it. Thanks.

@cynthiachen28: Did you already find something out? :)

@cynthiachen28: Did you already find something out? :)

Yes, you can directly reference another issue in the content of a certain issue by just type "#+number of issue".
After some research work, I found Github itself hasn't had function to manage the dependencies among issues.
Thus, I would recommend, if two or more issues have dependencies, we could

add a title "Prerequisite(Dependencies)" before "User Story", and link the related issues there.
Or add a tag shows "Prereq/Depend #1", and it would easy to filter these issues out.

@cynthiachen28: Great! Thank you very much, this helps a lot :)


Auto-fuzz: Fix logic for call depth filtering

This PR fixes the logic for call depth filtering and change the default ratio after source folder filtering has been added to the frontend processing in #1101.

This PR needs rebase after #1103 is merged in.


Chunked ingestion

Add initial support for ingestion of images in chunks to limit memory requirements.
The current API is minimal: an optional boolean chunked parameter in ImageConverter.to_tiledb that when true, each image level is read in chunks, where each chunk is a single tile region in TileDB. Later this may be extended to allow chunks larger than a single tile.
To enable chunked reading, the base ImageReader and all its subclasses have been extended:

level_image now takes an optional tile parameter for reading a subregion of the image
new level_shape method to return the shape of the image at the given level
new level_dtype method to return the dtype of the image at the given level

Implementation notes:

This PR allows chunked ingestion only if the original axes are preserved (either due to preserve_axes=True or because the original axes happens to be already in canonical order). A subsequent PR will lift this constraint.
The chunked read support for OME-Tiff requires zarr since tifffile doesn't support random access directly.

Merged into #50


vexctl add subcommand

This PR creates a new vexctl add subcommand. This new subcommand lets users add new vex statements to an existing document. This frees them from having to deal with updating dates, etc.
vex add will output the updated document to STDOUT or optionally can write to a new file or edit documents in place.
Note: Before merging needs https://github.com/openvex/vexctl/pull/110 and a rebase
Signed-off-by: Adolfo García Veytia (Puerco<EMAIL_ADDRESS>

This should be ready as the prereqs are merged. @luhring @cpanato  ptal.


Fix the SmsMode support

The SmsMode support is broken as the access token is not sent.
This PR fixes the problem and adjusts the related test.
I'm wondering if this support has ever worked.

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

Backported to: https://github.com/apereo/cas/pull/5584


About hot configuration reload

Hi there,
Recently, I'm working on the hot configuration reload on some of our projects. I wonder if Notary need this feature as well?
One scenario is: when in production, the log should not be set as debug, but when something bad happens, the Ops may want some more detail via log on the debug level. Since they couldn't stop the running process, they wish to have the feature of hot reloading.

I actually had this in a very early version and tore it out because we didn't need it and it added a lot of complexity. I think it would be great to add and if you'd like to take that on it would be appreciated.

I completely agree with you that it may cause a lot of unnecessary complexity especially when we want hot reload everything.
I'll send you a draft before doing it the other day.

To implement this, maybe we could:

find a way to monitor the change of the config file
when the change happen,  try to parse the new config file
find out whether the new config file contains those item we can reload
replace the old with the new one

At a simpler level, it would be acceptable to send a signal to the running application to tell it to reload the configuration. I'd probably approach this in 3 steps, with the final one being optional:

Graceful shutdown. When sent a signal, the server will stop accepting connections and finish serving any active requests before shutting down. It can then be restarted with the new configuration.
Triggered hot restart. A signal is used to tell the application to reload it's configuration. The way this is generally implemented is the current instance of http.Server stop listening for connections but is allowed to finish servicing any requests it has already accepted. As soon as the previous http.Server stops listening, a new http.Server, with the new configuration, is started to accept connection.
Automatic hot restart. Basically the same as 2, but the trigger is some automatic detection of a changed configuration.

In 2 and 3 it's important to cleanly handle a bad configuration. The previous server should be left running until we've done as much work as possible to ensure a new server can be started to take its place.

by (3), maybe the latest viper can do that. There is a handler viper.OnConfigChange() to watch the events when configuration changed. It was supported by "github.com/fsnotify/fsnotify", but since we use viper, we needn't to reinvent the wheel.

Yeah, I saw your PR updating viper. Kind of disappointed how many files that adds to support one simple use case but I agree, we shouldn't waste time building it ourselves.

yeah, too many additional files

Have talked to some colleague again, I think maybe we are a little bit over-designed?
Hot reload the debug level is more important than the other configuration items for them , because the log level will be set to default as info which may not recording enough information when something bad happens.
For other configuration, like the TLS, it's quite enough to shut down the relative node and reboot another one as long as it can be done gracefully.
So I think maybe the graceful shutdown signer and server are the one which should be in our roadmap?
Thoughts? @endophage @cyli @riyazdf

That definitely makes sense. I'd suggest using SIGUSR1 and SIGUSR2 to increment and decrement the logging level. That will allow it to be turned up or down as much as desired by sending the appropriate signal multiple times.

@HuKeping Would it be alright to close this?  Your awesome logging fix has been merged, and as per the conversation above, restarting so long as we have graceful shutdown (#712 and #711) would be sufficient to reload other configuration.

sure, closing


Multiple copies of a node in a flow

Added generation of unique name for multiple nodes of the same type within a flow. Fixed usage of Kafka consumerGroupId in client - multiple nodes of same type will have different consumerGroupIds but replicas of the same container will share a consumerGroupId.
@matzew This may conflict with your handling of dockerhub images...

will take a look in a a bit


Split HashFunction in two interfaces

Split equals(T, T) and hash(T) methods

https://github.com/data-streams/data-streams/commit/a93bc9109ea443a11924236e722ab63d851b2068


Fix/#24

fix #24

Codecov Report

Merging #26 into beta will increase coverage by 0.05%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##             beta      #26      +/-   ##
==========================================
+ Coverage   78.31%   78.37%   +0.05%
==========================================
  Files         169      169
  Lines        4663     4670       +7
  Branches      554      554
==========================================
+ Hits         3652     3660       +8
+ Misses        790      789       -1
  Partials      221      221

Impacted Files
Coverage Δ

...ages/pandora/src/application/ProcfileReconciler.ts
79.29% <93.33%> (+1.28%)
: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 0c64921...762d56f. Read the comment docs.


Ripcord indicator doesn't turn off if rip reciever destroyed

To duplicate set drone in sector away from TP, start drone rip (observe cyan caption), destroy TP station.  The caption remains cyan.
Imported from trac ticket #188,  created by Xynth on 07-28-2010 at 02:13, last modified: 02-25-2012 at 16:26

r844
Trac comment by Xynth on 07-29-2010 at 00:06


⚠ Turnos 24x7 has degraded performance

In ae224aa, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 914 ms

Resolved: Turnos 24x7 performance has improved in abefb78.


[1.10.2, bug, annoying] multiblock doesn't share information across the chunk borders (server restart always fixes it)

we have an induction matrix that stands in 4 different chunks (unintentionally). If one clicks on a block you only get the information about in/output that occurs in the same chunk. So if you have an input in chunk X and an output in chunk Y you and click on a block in chunk Z, you won't get any information at all, if you click on a block that is in chunk X you'll only get the input and for Y you'll only get the output.
Edit: A server restart solved the problem temporarily.
Guess: chunkloading problems

I  believe this is related to mine? #4451

rebuild in single chunk. multi block structures should never cross chunk border due to neighbor chunk load/unload behaviour

I've not been able to reproduce in the latest 1.12 releases, please send a minimal test world if you are still able to reproduce


Added plugin for Visual Studio Code

Added a plugin to enable triggering Visual Studio Code from the command line. Nothing fancy.
p.s. Not sure why the changes from Feb 2015 are included here. I thought they'd already been merged. I've rebased from the original, but I'm not that hot with Git, so not sure what's going on there.

Can you please remove the Atom file and squash your commits?
As far as I can tell this only works for OSX at the moment, can you maybe add support for linux?
You can take a look at other plugins (e.g. Atom, Sublime Text, etc.)

I don't know how to remove files from the pull request. I wouldn' have included them in the first place if I could have seen a way to avoid it.
I'd rather not add support for stuff I can't test.

I'm going to close this pull request and start over with a fresh fork. Will try to support platforms other than OS X when I do.

@wyldphyre: take a look at this function:
https://github.com/robbyrussell/oh-my-zsh/blob/master/lib/functions.zsh#L18
And for the file: just remove it, commit your changes and then squash all commits.

Repository is gone now. Will do it again at some point.

oh, forgot to say, thanks for pointing me to open_command.


fix the version problem, el use 0.0.18 but the nrepl with wrong version.

The 0.0.18 has problem el and nrepl have different version. It will break the color feature. So fix it.

Do you mean you get some warning because the versions are different?

Do you mean you get some warning because the versions are different?

Not the warning. The 0.0.18 el is not compatible with the 0.0.17 repl. It will break the color feature for the sayid buffer.  Most because the commit https://github.com/clojure-emacs/sayid/commit/4d03803e7cd4638ff401aeaed5aabb600e26520d.

Hmm, even if we bump those versions we already cut sayid 0.0.18, so I guess we'll need to bump the version again.

On a more general note - instead of hardcoding the version we should extract it from the project.clj, as we do in cider-nrepl (e..g. https://github.com/clojure-emacs/cider-nrepl/blob/master/src/cider_nrepl/plugin.clj#L60)  It's pretty easy to forget to update a version in several places, which caused the current issue.


Merging rank 256 LoRA weights takes forever

Hi!
I'm using you workflow with lora dimension (orbit left).
The Merging rank 256 LoRA weights step takes forever (i'm on A100) is there a way to speed up the process?

The node should have choice for load device, it's slow on CPU but should not take long at all on GPU (main_device), it's like 1-2 seconds for me on 4090.
It's not necessary to fuse it unless you want to also use torch.compile, in that case you'd set the strength to (1 / rank), which would be 0.0039


Build failure: cava-0.10.2

Steps To Reproduce
Steps to reproduce the behavior:

build cava-0.10.2

Build log

Build Log
Using versionCheckHook
Running phase: unpackPhase
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking source archive /nix/store/7n3i4i7mf29fwap22m4srqy73c8vv55n-source
source root is source
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: autoreconfPhase
@nix { "action": "setPhase", "phase": "autoreconfPhase" }
autoreconf: export WARNINGS=
autoreconf: Entering directory '.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
aclocal: warning: couldn't open directory 'm4': No such file or directory
configure.ac:306: error: _AX_CHECK_GL_MANUAL_LIBS_GENERIC: argument must not be empty
lib/m4sugar/m4sh.m4:690: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:697: AS_IF is expanded from...
/nix/store/fvdsb9i4vb8ca77s8lh60cil33m36dmk-autoconf-archive-2024.10.16/share/aclocal/ax_check_gl.m4:187: _AX_CHECK_GL_MANUAL_LIBS_GENERIC is expanded from...
lib/m4sugar/m4sh.m4:595: AS_CASE is expanded from...
/nix/store/fvdsb9i4vb8ca77s8lh60cil33m36dmk-autoconf-archive-2024.10.16/share/aclocal/ax_check_gl.m4:253: AX_CHECK_GL is expanded from...
lib/m4sugar/m4sh.m4:697: AS_IF is expanded from...
lib/m4sugar/m4sh.m4:697: AS_IF is expanded from...
configure.ac:306: the top level
autom4te: error: /nix/store/ab13djpkv4pyii8lvz4106bimy62db59-gnum4-1.4.19/bin/m4 failed with exit status: 1
aclocal: error: /nix/store/wky99hgy2w2nb3a6hzgk96yqdbi95zsj-autoconf-2.72/bin/autom4te failed with exit status: 1
autoreconf: error: aclocal failed with exit status: 1

Metadata

system: "x86_64-linux"
host os: Linux 6.11.7, NixOS, 24.11 (Vicuna), 24.11.20241111.dc460ec
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.24.10
channels(root): "nixos"
nixpkgs: /nix/store/4r8s42c9mwfvgdlxv0izb1cmlzrsb5nz-source

Notify maintainers

@offlinehacker
@mirrexagon

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Cava seems to have already been fixed by https://github.com/NixOS/nixpkgs/pull/355948, although the fix is not yet in nixos-unstable.

fix in unstable now, no issue for me anymore


#970: Fixing OS dependent paths related to / in path.

Signed-off-by: jzonthemtn<EMAIL_ADDRESS>Description
Fixes OS-specific paths by changing from Path.of to File.toPath. No new functionality.
Issues Resolved
#970
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed with a real name per the DCO

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

Nice find here! Thank you @jzonthemtn !


Add trackConsentGiven method

@yalisassoon to specify the arguments to be provided. Guessing there will be some kind of consentDocumentId and something around age/is-minor in there...

Nudge @yalisassoon

Hey @alexanderdean @mhadam
So I think we need these underlying schemas:
{
	"$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
	"description": "Schema for consent document context",
	"self": {
		"vendor": "com.snowplowanalytics.snowplow",
		"name": "consent_document",
		"format": "jsonschema",
		"version": "1-0-0"
	},

	"type": "object",
	"properties": {
		"id": {
			"type": "string",
      "maxLength": 36
		},
    "version": {
			"type": "string",
      "maxLength": 36
		},
		"name": {
			"type": "string",
      "maxLength": 60
		},
    "description": {
      "type": "string",
      "maxLength": 10000
    }
	},
	"required": ["id", "version"],
	"additionalProperties": false
}

The consent_granted event would be sent with at least one consent document context. (You could in theory send this with multiple documents if a person consented to multiple things at the same time.) There'd only be one event-specific field in the consent_granted event: an optional expiry date:
{
	"$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
	"description": "Schema for consent granted",
	"self": {
		"vendor": "com.snowplowanalytics.snowplow",
		"name": "consent_granted",
		"format": "jsonschema",
		"version": "1-0-0"
	},

	"type": "object",
	"properties": {
    "expiry": {
      "type": "string",
      "format": "date-time"
    }
	},
	"additionalProperties": false
}

The trackConsentGiven method would then take the following arguments:

document_id (required)
document_version (required)
document_name
document_description
expiry_date

LGTM - @mhadam can you create the associated tickets in Iglu Central?


Import packages from external golang source code

I want to import package from external golang source.
This pull request enables that by -include option.
$ cd $GOPATH/src/github.com/motemen/gore
$ gore -include main.go
gore version 0.0.0  :help for help
gore> homedir.Dir()
"/Users/tcnksm"
nil
gore>

I'm not sure implicit vs. explicit import  (cf. https://github.com/motemen/gore/pull/2)
But for me, session should be what I expected like ruby's irb.
This is just proposal.

I want to use with multiple files or directory

So this PR enables importing packages which are imported by a file specified. Seems good, but I think capability of using functions or variables defined in external files, not only importing packages, would be better (though I don't know we can achieve it). How about that? And would you show me what behavior of irb you want in gore, as I am not familiar with it?

multiple files or directory

and

capability of using functions or variables defined in external files, not only importing packages, would be better

are great I think (I'm also not sure I can implement importing function).
And about irb, what I want to say is explicit import (in ruby it is require) would be better.

I've finished.
This PR enables us to include external golang sources and,

Include packages from external golang sources
Enable to execute function defined in external golang sources

Here is example usages, https://gist.github.com/tcnksm/46a7eefcfe63f2930082

Thank you for the pull request and sorry for such a late reply.
Mostly looks good, but one point: we need a good reason to import packages imported by the included files in the repl session, as including files does not mean importing packages used by them. (I guess it helpful for repl users, so let's keep the behavior as is.)
Then, how about changing the -include=file,... flag to -context=file,..., which I think fit better to what it does? Can I apply that change (and some small fixes) and merge this PR?

we need a good reason to import packages imported by the included files in the repl session

For me, include package one by one is tired, I want to try packages in some go source file which currently I'm developing.

how about changing the -include=file,... flag to -context=file,...

-include=file is more intuitive UI for me. But this is just my opinion so -context is ok I think.

Finally merged it :smile:  Thanks a lot!

Thanks :ok_woman:


Add support for type parameters.

Heya, I added support for types with type parameters.
I've also got tests for them in diff-struct, shall push that soon.

Hey, thanks! I'll review tonight

oh yes, there's a bug with tuples with generics, I'll push a fix tonight

pushed :+1: (here and on https://github.com/BenHall-7/diff-struct/pull/8)

ah good catch -- I normally write trait bounds separately out of habit. I'll probably work on it this weekend

heya, got that part to work and added tests as well :v:


Correct edge in resource dependency graph for BackupBucket and BackupEntry

How to categorize this PR?

/area security
/kind bug
What this PR does / why we need it:
According to https://github.com/gardener/gardener/blob/master/docs/deployment/gardenlet_api_access.md#implementation-details:

An edge from vertex u to vertex v in this graph exists when (1) v is referred by u and v is a Seed, or when (2) u is referred by v.

This rule was not implemented correctly for the relationship between BackupBuckets and BackupEntrys. Earlier, there was an edge from BackupEntry (u) to BackupBucket (v), however, this violates above rule (case (2)) as the BackupEntry is not referred by the BackupBucket (it's the other way round).
This PR corrects this. This revealed an issue in the tests (missing expectations for seed Namespaces to the corresponding Seed vertices) which is also corrected. On the way, I added some helpful output in the expectPaths functions in the graph_test.go which helped me debugging the test issues.
Which issue(s) this PR fixes:
Part of #1723
Special notes for your reviewer:
/cc @plkokanov
Release note:

NONE

/invite @timuthy

@timuthy In #4154, the graph is already updated (also contains the changes of this PR, i.e., it inverts the edge) - once it's merged I'll rebase this PR.


Model Uncertainty

Hello, I don't seem to see the implementation part of Model Uncertainty in your code. I would like to ask if you have implemented this part of the code.

Hi Zerkoar, sorry about the delay. The evaluation only includes accuracy and IoU. I did not evaluate the uncertainty of the model. I hope this answers your question.


Handoff between sidecar shutdown and user application needs to be orderly

See this improvement proposal which could address the issue: https://github.com/kubernetes/enhancements/issues/753

Marco finds this one interesting...  (The akkaserverless-with-new-operator code adds a webhook for injecting the sidecar that could be very useful here I think.)


Scam website?

Is www.tibia-lyzer.com your website? Because i downloaded tibialyzer from there and when i execute the program nothing happens. The version from github works. Have I been scammed?

i forgot to mention that when i typed "tibialyzer" on google it was an advertisment

Mytherin stated that this (github page) is the ONLY official website so yeah probably. I suggest you uninstall the program and run exstensive anti virus / anti rootkit scans as well as malware scans just to be sure. For virus scan you can use the AVG free and for malware you can use the free Malwarbyte program. Also do you have use an Authenticator to log in? Then you should not really have to be worried to get hacked but I would still suggest changing the password etc.
Goodluck!

I do not use authenticator to log in. I scanned all computer files with Avira Antivirus and it showed me like 10 infected files but there were not releted files to fake tibialyzer. Of course i changed my password immidietly when i noticed it could be a scam. I changed it on my mobile and didnt log in yet on my computer.

If your antivirus didn't find anything related to fake TbiaLyzer your PC still might be infected. First of all you should update your antivirus definitions (I think thats what it's called) then scan PC again. If it still won't find anything just try with different software.
Also you should really start using 2FA. I think it's worth spending like lets say extra 1 min every login to keep your account safe.

Use a strong antivirus like Avira, GData, BitDefender or Kaspersky to fully scan your computer, memory and so on.


EN-17476 Improve logging

This makes the request logging in Spandex mirror that of Cetera.

This build looks good.


Delete old plugin files on fisher update

If a plugin releases a new version with deleted or renamed files, fisher update may result in duplicate files and unexpected functionality from plugins.
Would perhaps be a good idea to clean a plugin's previous files before linking new ones.

From conversation https://github.com/fisherman/done/issues/12#issuecomment-278049153.

Would this be as simple as doing fisher uninstall automatically before performing fisher install?

@aristidesfl 🤔 Maybe, but that'd be unacceptably slow.

Because of the plugins which don't need to be updated?

No, that's okay, you can always specify the name of the plugin/s you want to update.
Because removing the files will take some time, that's why. Probably, not too slow.

@franciscolourenco Fixed in fisher/releases/tag/3.0.0~!  🎉:tada:
It works similarly as you originally suggested. Before installing any package, we'll remove it. This should remove old files (including files that no longer exist in a new version of the package).


Ability for users to submit report of sensors built into their device

As title says, users have the ability to submit a report of their device's sensors so others can use this data to see which common devices has sensors such as barometer, gyroscope, and magnetometer built in without having to buy the device and find out that is doesn't have a specific sensor. For example, Samsung Galaxy A13 5G & A14 5G are listed to have a barometer but Galaxy A15 5G not have one listed specifically.  I'm personally looking to purchase a new phone and want to get the 3 main sensors above but not sure which ones have them all or not. Not sure if this could be done offline within trail sense.

Hi, while I don't think there's a way I can add this directly to Trail Sense, I can support this by doing the following:

[ ] Add a button to copy all device sensor types (with device model) on the sensor details tool
[ ] Add a link to a discussion on GitHub where people can post their device details

Also, for reference I have a Galaxy A13 5G and it has all 3 of those sensors and seems to be pretty good quality (a little slow compared to the Galaxy A52 and Pixel 7A, but it seemed to work fine with Trail Sense). I also recently bought a Galaxy A52 5G and it is great (and has all 3 sensors). I can't speak to the A14/A15 though.

As a start, I've created this page for the devices I've tested on: https://kylecorry.com/Trail-Sense/devices.html
I'll make it easier for people to contribute to that list in the future.

Okay, thank you. With the introduction of the copy/paste of available sensors that should make it much easier to add information to the list.


fix app purge not discovering uninstalled apps

Ignore this, file explorer wasn't updating for some reason...


Fix account testing logic for regression.

See commits for details.

Coverage decreased (-0.3%) to 73.805% when pulling 9957d5c2549f8409a8b1d3de0ff452b780fd1013 on sorpaas:master into 5a34f7d410f9e6a985356cd87adaba69eef75f20 on ethereumproject:master.


[meshery server]Sqlite migration | CU-1h1xjj2

Description
This PR fixes #4270
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@Revolyssup, a conflict for you to resolve. Also please remove the "draft-pr" and "do-not-merge" tags in case the PR is ready to be merged.


A NUL byte in a script will crash Wren

From u/sponkemonke.

maybe ask him a little more data. I only got the crash with my fix attempt of #430.
I did try a script with a NUL byte between 2 statements, the 2nd statement was not executed.
I then put it inside a string, got the "unterminated string" error.
Then inside a method name "fiber.yie[NUL]d()": Error at end of file: Expect '}' at end of block.

I was the one who found the crashes using American Fuzzy Lop. I've attached a zip containing a few of the files that cause wren to crash.
crashes.zip

Thanks @gordonshieh94, I manage to find something. The NUL byte is not the error, it shows that wren don't handle unclosed scopes in some cases.
{
System

gives *** Error in `./wrend': free(): invalid next size (fast): 0x00000000011fbc80 ***
{
  System.print("hello")

gives *** Error in `./wrend': double free or corruption (out): 0x0000000001190580 ***
The following codes don't crash.
// removing the carriage return
// Error at end of file: Expect '}' at end of block.
{ System

// adding a dot
// Error at end of file: Expect method name after '.'.
{
  System.

// adding dot and method name
// System metaclass does not implement 'print'.
{
  System.print


compute: fix autoscaler tests

Fixes #1659
Our Autoscalers tests were failing because we weren't providing enough resources for an autoscaler to be created.

Changes Unknown when pulling 6901e5f4283d9fcd706eaa4253895a97ce5c4212 on stephenplusplus:spp--1659 into ** on GoogleCloudPlatform:master**.

Changes Unknown when pulling 6901e5f4283d9fcd706eaa4253895a97ce5c4212 on stephenplusplus:spp--1659 into ** on GoogleCloudPlatform:master**.

@stephenplusplus maybe we should add the instance group manager & instance image APIs to our todo list?

I think they are!


Convert sigcache to context free populated tx cache

This PR was rolled back from master since this cache scheme is attackable.


$host.version is not the correct way to determine powershell engine version

In readme.md, it is suggested to check $host.version for the engine version. This is only reliable for the native powershell.exe. Other hosts (powergui, powershellplus, etc.) will return the host (product) version which is different than the engine version. The correct way to determine the engine is to examine $psversiontable.psversion.

Good one! Fixed in the dev branch.


btm_api.h linkage issue (Bluedroid BTM)

Having a linkage issue with Bluedroid BTM:
#include <btm_api.h>
// ...
  if (BTM_IsDeviceUp()) {
    ESP_LOGI("BT", "BTM says device is up!");
  } else {
    ESP_LOGE("BT", "BTM says device is down :-(");
  }
// ...

Error message:
libmain.a(bluetooth_scanner.o):(.literal._ZNK16BluetoothScanner4scanEv+0xc): undefined reference to `BTM_IsDeviceUp()'

Here's my sdkconfig:
#
# Automatically generated file; DO NOT EDIT.
# Espressif IoT Development Framework Configuration
#

#
# SDK tool configuration
#
CONFIG_TOOLPREFIX="xtensa-esp32-elf-"
CONFIG_PYTHON="python"

#
# Bootloader config
#
# CONFIG_LOG_BOOTLOADER_LEVEL_NONE is not set
# CONFIG_LOG_BOOTLOADER_LEVEL_ERROR is not set
# CONFIG_LOG_BOOTLOADER_LEVEL_WARN is not set
CONFIG_LOG_BOOTLOADER_LEVEL_INFO=y
# CONFIG_LOG_BOOTLOADER_LEVEL_DEBUG is not set
# CONFIG_LOG_BOOTLOADER_LEVEL_VERBOSE is not set
CONFIG_LOG_BOOTLOADER_LEVEL=3

#
# Security features
#
# CONFIG_SECURE_BOOT_ENABLED is not set
# CONFIG_FLASH_ENCRYPTION_ENABLED is not set

#
# Serial flasher config
#
CONFIG_ESPTOOLPY_PORT="COM4"
CONFIG_ESPTOOLPY_BAUD_115200B=y
# CONFIG_ESPTOOLPY_BAUD_230400B is not set
# CONFIG_ESPTOOLPY_BAUD_921600B is not set
# CONFIG_ESPTOOLPY_BAUD_2MB is not set
# CONFIG_ESPTOOLPY_BAUD_OTHER is not set
CONFIG_ESPTOOLPY_BAUD_OTHER_VAL=115200
CONFIG_ESPTOOLPY_BAUD=115200
CONFIG_ESPTOOLPY_COMPRESSED=y
# CONFIG_FLASHMODE_QIO is not set
# CONFIG_FLASHMODE_QOUT is not set
CONFIG_FLASHMODE_DIO=y
# CONFIG_FLASHMODE_DOUT is not set
CONFIG_ESPTOOLPY_FLASHMODE="dio"
# CONFIG_ESPTOOLPY_FLASHFREQ_80M is not set
CONFIG_ESPTOOLPY_FLASHFREQ_40M=y
# CONFIG_ESPTOOLPY_FLASHFREQ_26M is not set
# CONFIG_ESPTOOLPY_FLASHFREQ_20M is not set
CONFIG_ESPTOOLPY_FLASHFREQ="40m"
# CONFIG_ESPTOOLPY_FLASHSIZE_1MB is not set
CONFIG_ESPTOOLPY_FLASHSIZE_2MB=y
# CONFIG_ESPTOOLPY_FLASHSIZE_4MB is not set
# CONFIG_ESPTOOLPY_FLASHSIZE_8MB is not set
# CONFIG_ESPTOOLPY_FLASHSIZE_16MB is not set
CONFIG_ESPTOOLPY_FLASHSIZE="2MB"
CONFIG_ESPTOOLPY_FLASHSIZE_DETECT=y
CONFIG_ESPTOOLPY_BEFORE_RESET=y
# CONFIG_ESPTOOLPY_BEFORE_NORESET is not set
CONFIG_ESPTOOLPY_BEFORE="default_reset"
CONFIG_ESPTOOLPY_AFTER_RESET=y
# CONFIG_ESPTOOLPY_AFTER_NORESET is not set
CONFIG_ESPTOOLPY_AFTER="hard_reset"
# CONFIG_MONITOR_BAUD_9600B is not set
# CONFIG_MONITOR_BAUD_57600B is not set
CONFIG_MONITOR_BAUD_115200B=y
# CONFIG_MONITOR_BAUD_230400B is not set
# CONFIG_MONITOR_BAUD_921600B is not set
# CONFIG_MONITOR_BAUD_2MB is not set
# CONFIG_MONITOR_BAUD_OTHER is not set
CONFIG_MONITOR_BAUD_OTHER_VAL=115200
CONFIG_MONITOR_BAUD=115200

#
# Partition Table
#
CONFIG_PARTITION_TABLE_SINGLE_APP=y
# CONFIG_PARTITION_TABLE_TWO_OTA is not set
# CONFIG_PARTITION_TABLE_CUSTOM is not set
CONFIG_PARTITION_TABLE_CUSTOM_FILENAME="partitions.csv"
CONFIG_PARTITION_TABLE_CUSTOM_APP_BIN_OFFSET=0x10000
CONFIG_PARTITION_TABLE_FILENAME="partitions_singleapp.csv"
CONFIG_APP_OFFSET=0x10000
CONFIG_OPTIMIZATION_LEVEL_DEBUG=y
# CONFIG_OPTIMIZATION_LEVEL_RELEASE is not set

#
# Component config
#
# CONFIG_AWS_IOT_SDK is not set
CONFIG_BT_ENABLED=y
CONFIG_BLUEDROID_ENABLED=y
CONFIG_BTC_TASK_STACK_SIZE=3072
# CONFIG_BLUEDROID_MEM_DEBUG is not set
CONFIG_CLASSIC_BT_ENABLED=y
CONFIG_GATTS_ENABLE=y
CONFIG_GATTC_ENABLE=y
CONFIG_SMP_ENABLE=y
# CONFIG_BT_STACK_NO_LOG is not set
CONFIG_BT_ACL_CONNECTIONS=4
CONFIG_BTDM_CONTROLLER_RUN_CPU=0
CONFIG_BT_RESERVE_DRAM=0x10000

#
# ESP32-specific
#
# CONFIG_ESP32_DEFAULT_CPU_FREQ_80 is not set
CONFIG_ESP32_DEFAULT_CPU_FREQ_160=y
# CONFIG_ESP32_DEFAULT_CPU_FREQ_240 is not set
CONFIG_ESP32_DEFAULT_CPU_FREQ_MHZ=160
CONFIG_MEMMAP_SMP=y
# CONFIG_MEMMAP_TRACEMEM is not set
# CONFIG_MEMMAP_TRACEMEM_TWOBANKS is not set
# CONFIG_ESP32_TRAX is not set
CONFIG_TRACEMEM_RESERVE_DRAM=0x0
# CONFIG_ESP32_ENABLE_COREDUMP_TO_FLASH is not set
# CONFIG_ESP32_ENABLE_COREDUMP_TO_UART is not set
CONFIG_ESP32_ENABLE_COREDUMP_TO_NONE=y
# CONFIG_ESP32_ENABLE_COREDUMP is not set
# CONFIG_ESP32_APPTRACE_DEST_TRAX is not set
# CONFIG_ESP32_APPTRACE_DEST_UART is not set
CONFIG_ESP32_APPTRACE_DEST_NONE=y
# CONFIG_ESP32_APPTRACE_ENABLE is not set
# CONFIG_TWO_UNIVERSAL_MAC_ADDRESS is not set
CONFIG_FOUR_UNIVERSAL_MAC_ADDRESS=y
CONFIG_NUMBER_OF_UNIVERSAL_MAC_ADDRESS=4
CONFIG_SYSTEM_EVENT_QUEUE_SIZE=32
CONFIG_SYSTEM_EVENT_TASK_STACK_SIZE=4096
CONFIG_MAIN_TASK_STACK_SIZE=4096
CONFIG_NEWLIB_STDOUT_ADDCR=y
# CONFIG_NEWLIB_NANO_FORMAT is not set
CONFIG_CONSOLE_UART_DEFAULT=y
# CONFIG_CONSOLE_UART_CUSTOM is not set
# CONFIG_CONSOLE_UART_NONE is not set
CONFIG_CONSOLE_UART_NUM=0
CONFIG_CONSOLE_UART_BAUDRATE=115200
# CONFIG_ULP_COPROC_ENABLED is not set
CONFIG_ULP_COPROC_RESERVE_MEM=0
# CONFIG_ESP32_PANIC_PRINT_HALT is not set
CONFIG_ESP32_PANIC_PRINT_REBOOT=y
# CONFIG_ESP32_PANIC_SILENT_REBOOT is not set
# CONFIG_ESP32_PANIC_GDBSTUB is not set
CONFIG_ESP32_DEBUG_OCDAWARE=y
CONFIG_INT_WDT=y
CONFIG_INT_WDT_TIMEOUT_MS=300
CONFIG_INT_WDT_CHECK_CPU1=y
CONFIG_TASK_WDT=y
# CONFIG_TASK_WDT_PANIC is not set
CONFIG_TASK_WDT_TIMEOUT_S=5
CONFIG_TASK_WDT_CHECK_IDLE_TASK=y
CONFIG_TASK_WDT_CHECK_IDLE_TASK_CPU1=y
# CONFIG_ESP32_TIME_SYSCALL_USE_RTC is not set
CONFIG_ESP32_TIME_SYSCALL_USE_RTC_FRC1=y
# CONFIG_ESP32_TIME_SYSCALL_USE_FRC1 is not set
# CONFIG_ESP32_TIME_SYSCALL_USE_NONE is not set
CONFIG_ESP32_RTC_CLOCK_SOURCE_INTERNAL_RC=y
# CONFIG_ESP32_RTC_CLOCK_SOURCE_EXTERNAL_CRYSTAL is not set
CONFIG_ESP32_RTC_CLK_CAL_CYCLES=1024
CONFIG_ESP32_DEEP_SLEEP_WAKEUP_DELAY=2000
# CONFIG_ESP32_XTAL_FREQ_40 is not set
# CONFIG_ESP32_XTAL_FREQ_26 is not set
CONFIG_ESP32_XTAL_FREQ_AUTO=y
CONFIG_ESP32_XTAL_FREQ=0
CONFIG_WIFI_ENABLED=y
CONFIG_SW_COEXIST_ENABLE=y
CONFIG_ESP32_WIFI_STATIC_RX_BUFFER_NUM=10
CONFIG_ESP32_WIFI_DYNAMIC_RX_BUFFER_NUM=32
# CONFIG_ESP32_WIFI_STATIC_TX_BUFFER is not set
CONFIG_ESP32_WIFI_DYNAMIC_TX_BUFFER=y
CONFIG_ESP32_WIFI_TX_BUFFER_TYPE=1
CONFIG_ESP32_WIFI_DYNAMIC_TX_BUFFER_NUM=32
CONFIG_ESP32_WIFI_AMPDU_ENABLED=y
CONFIG_ESP32_WIFI_NVS_ENABLED=y
CONFIG_PHY_ENABLED=y

#
# PHY
#
CONFIG_ESP32_PHY_CALIBRATION_AND_DATA_STORAGE=y
# CONFIG_ESP32_PHY_INIT_DATA_IN_PARTITION is not set
CONFIG_ESP32_PHY_MAX_WIFI_TX_POWER=20
CONFIG_ESP32_PHY_MAX_TX_POWER=20
# CONFIG_ETHERNET is not set

#
# FAT Filesystem support
#
CONFIG_FATFS_CODEPAGE_ASCII=y
# CONFIG_FATFS_CODEPAGE_437 is not set
# CONFIG_FATFS_CODEPAGE_720 is not set
# CONFIG_FATFS_CODEPAGE_737 is not set
# CONFIG_FATFS_CODEPAGE_771 is not set
# CONFIG_FATFS_CODEPAGE_775 is not set
# CONFIG_FATFS_CODEPAGE_850 is not set
# CONFIG_FATFS_CODEPAGE_852 is not set
# CONFIG_FATFS_CODEPAGE_855 is not set
# CONFIG_FATFS_CODEPAGE_857 is not set
# CONFIG_FATFS_CODEPAGE_860 is not set
# CONFIG_FATFS_CODEPAGE_861 is not set
# CONFIG_FATFS_CODEPAGE_862 is not set
# CONFIG_FATFS_CODEPAGE_863 is not set
# CONFIG_FATFS_CODEPAGE_864 is not set
# CONFIG_FATFS_CODEPAGE_865 is not set
# CONFIG_FATFS_CODEPAGE_866 is not set
# CONFIG_FATFS_CODEPAGE_869 is not set
# CONFIG_FATFS_CODEPAGE_932 is not set
# CONFIG_FATFS_CODEPAGE_936 is not set
# CONFIG_FATFS_CODEPAGE_949 is not set
# CONFIG_FATFS_CODEPAGE_950 is not set
CONFIG_FATFS_CODEPAGE=1
CONFIG_FATFS_MAX_LFN=255

#
# FreeRTOS
#
# CONFIG_FREERTOS_UNICORE is not set
CONFIG_FREERTOS_CORETIMER_0=y
# CONFIG_FREERTOS_CORETIMER_1 is not set
CONFIG_FREERTOS_HZ=100
CONFIG_FREERTOS_ASSERT_ON_UNTESTED_FUNCTION=y
# CONFIG_FREERTOS_CHECK_STACKOVERFLOW_NONE is not set
# CONFIG_FREERTOS_CHECK_STACKOVERFLOW_PTRVAL is not set
CONFIG_FREERTOS_CHECK_STACKOVERFLOW_CANARY=y
# CONFIG_FREERTOS_WATCHPOINT_END_OF_STACK is not set
CONFIG_FREERTOS_THREAD_LOCAL_STORAGE_POINTERS=1
CONFIG_FREERTOS_ASSERT_FAIL_ABORT=y
# CONFIG_FREERTOS_ASSERT_FAIL_PRINT_CONTINUE is not set
# CONFIG_FREERTOS_ASSERT_DISABLE is not set
CONFIG_FREERTOS_BREAK_ON_SCHEDULER_START_JTAG=y
# CONFIG_ENABLE_MEMORY_DEBUG is not set
CONFIG_FREERTOS_ISR_STACKSIZE=1536
# CONFIG_FREERTOS_LEGACY_HOOKS is not set
CONFIG_FREERTOS_MAX_TASK_NAME_LEN=16
# CONFIG_SUPPORT_STATIC_ALLOCATION is not set
CONFIG_TIMER_TASK_PRIORITY=1
CONFIG_TIMER_TASK_STACK_DEPTH=2048
CONFIG_TIMER_QUEUE_LENGTH=10
# CONFIG_FREERTOS_DEBUG_INTERNALS is not set

#
# Log output
#
# CONFIG_LOG_DEFAULT_LEVEL_NONE is not set
# CONFIG_LOG_DEFAULT_LEVEL_ERROR is not set
# CONFIG_LOG_DEFAULT_LEVEL_WARN is not set
CONFIG_LOG_DEFAULT_LEVEL_INFO=y
# CONFIG_LOG_DEFAULT_LEVEL_DEBUG is not set
# CONFIG_LOG_DEFAULT_LEVEL_VERBOSE is not set
CONFIG_LOG_DEFAULT_LEVEL=3
CONFIG_LOG_COLORS=y

#
# LWIP
#
# CONFIG_L2_TO_L3_COPY is not set
CONFIG_LWIP_MAX_SOCKETS=10
CONFIG_LWIP_THREAD_LOCAL_STORAGE_INDEX=0
# CONFIG_LWIP_SO_REUSE is not set
# CONFIG_LWIP_SO_RCVBUF is not set
CONFIG_LWIP_DHCP_MAX_NTP_SERVERS=1
# CONFIG_LWIP_IP_FRAG is not set
# CONFIG_LWIP_IP_REASSEMBLY is not set
CONFIG_TCP_MAXRTX=12
CONFIG_TCP_SYNMAXRTX=6
CONFIG_LWIP_DHCP_DOES_ARP_CHECK=y
CONFIG_TCPIP_TASK_STACK_SIZE=2560
# CONFIG_PPP_SUPPORT is not set

#
# mbedTLS
#
CONFIG_MBEDTLS_SSL_MAX_CONTENT_LEN=16384
# CONFIG_MBEDTLS_DEBUG is not set
CONFIG_MBEDTLS_HARDWARE_AES=y
CONFIG_MBEDTLS_HARDWARE_MPI=y
CONFIG_MBEDTLS_MPI_USE_INTERRUPT=y
CONFIG_MBEDTLS_HARDWARE_SHA=y
CONFIG_MBEDTLS_HAVE_TIME=y
# CONFIG_MBEDTLS_HAVE_TIME_DATE is not set

#
# OpenSSL
#
# CONFIG_OPENSSL_DEBUG is not set
CONFIG_OPENSSL_ASSERT_DO_NOTHING=y
# CONFIG_OPENSSL_ASSERT_EXIT is not set

#
# SPI Flash driver
#
# CONFIG_SPI_FLASH_ENABLE_COUNTERS is not set
CONFIG_SPI_FLASH_ROM_DRIVER_PATCH=y

I'm interested in performing a Bluetooth Classic scan for Bluetooth Device Addresses, and it looks like I may find my way stitching together some functions in the btm_api.h header.
Is there an easier way? It looks fairly easy to subscribe to BLE advertisements, but I cannot find working examples of scanning for Bluetooth Classic devices. Alternately, why can I not link in the Bluedroid components?

This function is of particular interest (from btm_api.h):
/*******************************************************************************
**
** Function         BTM_StartInquiry
**
** Description      This function is called to start an inquiry.
**
** Parameters:      p_inqparms - pointer to the inquiry information
**                      mode - GENERAL or LIMITED inquiry
**                      duration - length in 1.28 sec intervals (If '0', the inquiry is CANCELLED)
**                      max_resps - maximum amount of devices to search for before ending the inquiry
**                      filter_cond_type - BTM_CLR_INQUIRY_FILTER, BTM_FILTER_COND_DEVICE_CLASS, or
**                                         BTM_FILTER_COND_BD_ADDR
**                      filter_cond - value for the filter (based on filter_cond_type)
**
**                  p_results_cb   - Pointer to the callback routine which gets called
**                                upon receipt of an inquiry result. If this field is
**                                NULL, the application is not notified.
**
**                  p_cmpl_cb   - Pointer to the callback routine which gets called
**                                upon completion.  If this field is NULL, the
**                                application is not notified when completed.
** Returns          tBTM_STATUS
**                  BTM_CMD_STARTED if successfully initiated
**                  BTM_BUSY if already in progress
**                  BTM_ILLEGAL_VALUE if parameter(s) are out of range
**                  BTM_NO_RESOURCES if could not allocate resources to start the command
**                  BTM_WRONG_MODE if the device is not up.
**
*******************************************************************************/
//extern
tBTM_STATUS  BTM_StartInquiry (tBTM_INQ_PARMS *p_inqparms,
                               tBTM_INQ_RESULTS_CB *p_results_cb,
                               tBTM_CMPL_CB *p_cmpl_cb);

By any chance, are you trying to call these functions from a C++ application?

@nkolban why, yes! I anticipate that name mangling is the source of my problem here since you asked the question?
Thanks for the book, by the way :)

@JLospinoso , sorry for delay. In design, application shouldn't include BTM_xxx.h or BTA_xxx.h. Application should only include esp_xxx.h of bluedroid.
The missing thing is that some of the demo keep the '#include "BTA_xxx.h"', it is incorrect. In the newest master, we will remove these "#include" line.


Feature request: Monitor retry frequency

When setting up monitoring, it would be nice to be able to add (optionally) a retry frequency.
Right now, when a monitor responds with an error (whether it's due to a timeout, or a response code >= 400), and I have set up my monitor to attempt to get a successful response more than 1 time, it retries again immediately, which results in a monitor notification via a channel or email very shortly after the 1st attempt failed.
So, to avoid that, and to give the service a chance to get back on its feet again, before sending a new ping, it would be nice to either stick to the monitoring frequency that is set, or to add an option to define a re-attempt/retry frequency.
Maybe my monitoring frequency is set to 10s, but if I run into an error, I want it to retry every 5 seconds until I reached my attempts-limit.

Thanks for writing this up after our discussion.
I'll take a look at this 👍


Optimised overlay render logic

Currently the IntroStepBuilder renders overlay on the left side even when there is more space on the right, because the getOverlayPosition function inside _StepWidgetBuilder verifies if there is more space on the sides compared to top and bottom spaces but it doesn't exactly calculate which side has more space.
Before:
https://github.com/user-attachments/assets/00e861ee-42b5-463f-bd6b-44d9bf40f198
After:
https://github.com/user-attachments/assets/f5ce0d88-4888-42a7-9403-af5ee104f612
to reproduce the issue add padding to the right above centre widget here in the example
https://github.com/minaxorg/flutter_intro/blob/c73af8c1e0f9406c4a4c8dd27b2dd20721f49d99/example/lib/group_usage.dart#L4-L12
Like this:
      appBar: AppBar(),
      body: Padding(
        padding: const EdgeInsets.only(right: 100),
        child: Center(
          child: Column(

Thanks!!!


Coverage badge

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@006a483). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 8d0751b differs from pull request most recent head 85fe205. Consider uploading reports for the commit 85fe205 to get more accurate results

@@           Coverage Diff           @@
##             main      #27   +/-   ##
=======================================
  Coverage        ?   56.70%
=======================================
  Files           ?        9
  Lines           ?      358
  Branches        ?        0
=======================================
  Hits            ?      203
  Misses          ?      108
  Partials        ?       47

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 006a483...85fe205. Read the comment docs.


Set up CircleCI test summary [npmcollaborators]

See https://circleci.com/docs/2.0/collect-test-data/
This provides a list of failed tests in the Circle UI and a summary of which tests have failed. It should make interpreting test results easier
It also provides information about how frequently individual tests fail:

These seem particularly helpful in the daily service tests, which will also need a couple tweaks made: https://circleci.com/gh/badges/daily-tests/33
I'm not sure if it's possible to access these totals through the API, though if it is, it would be cool to show how many service tests have failed. That would make it a little more fun to keep on top of them. 😉
Example failures:
https://circleci.com/gh/badges/shields/29091

https://circleci.com/gh/badges/shields/29100

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against 83ef124bfeff9b97bba4a189af91845754286cb3

https://circleci.com/docs/api/#test-metadata
I remember looking for this API a while back and found nothing so I think this may be relatively new. Seems like it may now finally be possible to have a Test Results badge for Circle (akin to Appveyor, Jenkins, Azure DevOps, etc.)!

I appreciate the reviews, from both of you!


If a mutation in the bundle is unmeasured, throw away data for all variants with mutations at this site

Here is my reasoning for doing this, which I've added to the SI (for context see "Reckoning mutations with respect to the reference experiment"):

If there is an unmeasured mutation in the bundle, our strategy for removing this mutation from the summation term of Eq.(1) is to completely ignore this site when analyzing the data.
This involves ignoring all variants with mutations at this site.
Although this can result in throwing away data, it is necessary for the math to work out.
For instance, in the above example where Y30A is missing from the non-reference experiment and A30Y is missing from the reference experiment, $\alpha_d$ will be used to capture the effect of A30Y when modeling the latent phenotype of the wildtype sequence from the non-reference experiment.
If a variant from the non-reference experiment has a Y30G mutation, this mutation will be included in the summation term of Eq.(1) as A30G.
However, since $\alpha_d$ is a constant offset used to compute the latent phenotype of \emph{all} variants from experiment $d$, and since $\alpha_d$ includes the effect of A30Y, Eq.(1) would effectively be adding the effects of both A30G and A30Y when computing the latent phenotype of this particular variant, which does not make sense.
Because of this problem, we choose to ignore all data at such sites.

@jgallowa07: if you agree with this logic, I think the thing to do would be to include these sites in the list of disallowed sites that gets used to identify variants to discard. This would only apply to sites where the forward mutation is missing from the reference experiment and the reverse mutation is missing from the non-reference experiment.

My thoughts:

it is necessary for the math to work out

seems ambiguous. And it's not about the math per se, is it? Like it's "working" just fine without doing this, currently.

I think the thing to do would be to include these sites in the list of disallowed sites that gets used to identify variants to discard.

What do you mean, exactly?. If there is not both a forward and a reversion, do I then identify which one is missing and only throw that from the respective condition? Do we remove it from the bundle? Can you clarify (or submit a PR)?

Er, did you mean throw everything at that site?

since $\alpha_d$ includes the effect of A30Y, Eq.(1) would effectively be adding the effects of both A30G and A30Y when computing the latent phenotype of this particular variant, which does not make sense.

Just to clarify,  you're saying if either the forward or the reversion exists, then the double mut counting is not a problem bc:

if the forward mut is there (A30Y), then we have an effective beta for this mutation and then $\alpha_d$ need not model it (is this really the case :thinking: )
If the reversion is there, then we have an effective shift to model it, and again, $\alpha_d$ need not model it.

It seems a little hand-wavy and maybe too confident about the role of $\alpha_d$ is. Is there any evidence that the double counting site mut counting thing is actually a problem? We should be able to investigate this with the current results somehow ...

Not that I disagree with the logic, but it seems like this is purely a theoretical problem a this point and thus maybe not as high priority ...

I agree if just the forward mutation is there it's a bit strange. And same thing for just the reverse mutation. So there may be an argument for excluding the site in those cases as well.
I think you're right that it isn't currently a problem with the spike data since I think all forward and reverse mutations in the bundle are sampled in the libraries (excluding indels). I think if we made the change I suggested, there wouldn't be much or any additional data that gets thrown out and the overall results wouldn't change.
But, I think it is a theoretical problem for future users. It seems like an easy fix, and it makes it easier to describe a general strategy for dropping mutations from the summation term when they are missing from the data.
Whether $\alpha_d$ is actually capturing what we want it to is one question. But it does have a well-defined purpose in the mathematical model -- in theory, it is the only parameter that should be able to uniquely capture the effects of missing mutations in the bundle. And we can show that the math doesn't work out in the case that I outlined above, so I think it's a clear problem that needs addressing.
For priority, I think it's probably something we'd want to update before posting the paper. But let's discuss on Monday. I know you have a lot on your plate!

I think I understand the logic above, but to me it seems like another symptom of our approach to modeling unobserved mutations, which is to not model them. While this approach avoids assuming some additional prior information, it results in an overly brittle model. The other main symptom of this is that we've convinced ourselves—erroneously, I've argued—that we can't do out-of-sample prediction.
I'll record below how I would deal with unobserved mutations, since this is tangentially relevant to what you decide for this issue:
It is not unusual for a statistical model on categorical data to have to cope with features that end up being constant over a training set, but variable in a test set.
There are standard approaches for dealing with this kind of modeling challenge via flavors of ridge penalty (see issue #51), possibly with grouping (I think the polyclonal project from the Bloom lab did this with a site-level baseline model). These address the issue by sharing information in a few possible ways, all of which can be viewed as adding some weak prior information:

Global ridge penalty (issue #51): shared info among all mutations, so that an unobserved mutation is encouraged to have an effect of a typical mutation.
Site-wise ridge penalty: shares info among all mutations at a site, so that an observed mutation at a given site is encouraged to have an effect of a typical mutation at that site. For example: site 1 is tolerant to mutations, site 2 is not.
AA-wise ridge penalty: shares info among all mutations from a given AA to a given AA, so that an observed mutation is encouraged to have an effect of a typical mutation with the same starting and ending AA states. For example: alanine-to-proline mutations are bad.

Thanks, Will. I agree that these are neat ideas.
For the purposes of getting something out the door this week, my suggestion would be to have our base model be something that throws out the problematic variants described above, so that users could opt to avoid making assumptions if they wish. But, then to include your suggested approaches for estimating the effects of unobserved mutations as optional features that we could add onto the base model in future versions of multidms.

@jgallowa07: just pinging this thread since in my opinion it would be good to resolve this issue in version 1.0.
To sum up our above convo, I'd suggest using the draft code we already wrote to:

identify mutations in the bundle that are missing from either the reference experiment (forward mutation) or the non-reference (reverse mutation) experiment or both.
flagging the corresponding sites as invalid
tossing variants with mutations at the invalid sites

This is likely to have zero or very minimal effect on the spike data, as well as other datasets from the Bloom lab. But, it helps to avoid problems in the future and provides a concrete strategy for dealing with the basic issue described above.
But let me know if you disagree.


Rename supportbundle package as diagnostics and fix path

Description of changes:
Package supportbundle was in folder support. Fixing that and also renaming to diagnostics as @danbudris suggestion
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: g-gaston
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [g-gaston]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: g-gaston, TerryHowe
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [TerryHowe,g-gaston]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


DApp browser cann't open Uniswap in a right way

When I open "https://app.compound.finance", demo can auto connect wallet.
When I open "https://uniswap.tokenpocket.pro/#/swap", demo Cnann't auto connect wallet.

@CYC666 Have you got the solution??

@CYC666 Have you got the solution??

@CYC666 Have you got the solution??

还没，你解决了吗？

@CYC666 Have you got the solution??

还没，你解决了吗？

@CYC666 Have you got the solution??

还没，你解决了吗？

No

@CYC666 Have you got the solution??

还没，你解决了吗？

No

@CYC666你有解决方案吗？？

还没有，你解决了吗？

不

同样的问题..

I'm facing the same issue...

Duplicate of #321 #