Fetch doesn't download any file

Hi!
I'm using this library in my project, I'm using the Fetch option, because i need to charge the data only when i click button. The thing is, the call makes it perfectly but no file is downloaded in my computer.
I noticed that when I click the button with fetch option, the data is saved. Then, if I create another button that not include fetch but has :data the download starts, but I need to do all only in one click.
Is there any chance to make fetch call and get file downloaded at the same time with one button?
Thanks in advice!
<download-excel
  v-if="!json_csv_ok"
  class="btn btn-outline-primary"
  :fetch="getUsers"
  :fields="json_fields"
  :before-finish="finishDownload"
>
  Generate CSV
</download-excel>
<download-excel
  v-if="json_csv_ok"
  class="btn btn-outline-primary"
  type="csv"
  name="Users.csv"
  :data="users_csv"
>
  <i class="bi bi-file-arrow-down-fill" />
  Download CSV
</download-excel>

json_fields: {
  'Complete name': 'name',
  'Email': 'email',
  'Geography': 'geography',
  'Registration date': 'registration_date',

async getUsers() {
  usersService.get_users({ limit: -1, offset: 0, filters: {} }).then((response) => {
        this.users_csv = []

        let aux = response.data.data
        if (aux.length !== 0) {
          for (let i in aux) {
            this.users_csv.push({
              name: aux[i].name,
              email: aux[i].email,
              geography: aux[i].geography.name,
              registration_date: aux[i].registration_date
            })
          }
        }
        this.json_csv_ok = true
        return this.users_csv
  })
}

Hi @missmay4,
Please refer below code.

<template>
  <q-page class="">
    <download-excel
      class="btn"
      :fetch="fetchData"
      :before-generate="startDownload"
      :before-finish="finishDownload"
      type="xlsx" worksheet="My Worksheet"
      name="filename.xlsx"
    >
      Download Excel (you can customize this with html code!)
    </download-excel>
  </q-page>
</template>

<script>
import {defineComponent} from 'vue';
import JsonExcel from "vue-json-excel3";
import axios from 'axios';

export default defineComponent({
  name: 'IndexPage',
  components: {
    downloadExcel: JsonExcel
  },
  data() {
    return {
    }
  },
  methods: {
    async fetchData() {
      let repoUrl = 'https://jsonplaceholder.typicode.com/users';
      return axios.get(repoUrl)
        .then((response) => {
          console.log(response.data)
          return response.data;
        })
        .catch((error) => {
          this.persons = error.response.statusText;
        });
    },
    startDownload() {
      alert('show loading');
    },
    finishDownload() {
      alert('hide loading');
    }
  }
});
</script>

Hi again!
Thanks for the quick response.
I tried it but, still the same... call is done no file is downloaded in my computer.
I'm using Google Chrome, maybe could be the problem? Thanks.

Hi @missmay4,
Please refer below code.

<template>
  <q-page class="">
    <download-excel
      class="btn"
      :fetch="fetchData"
      :before-generate="startDownload"
      :before-finish="finishDownload"
      type="xlsx" worksheet="My Worksheet"
      name="filename.xlsx"
    >
      Download Excel (you can customize this with html code!)
    </download-excel>
  </q-page>
</template>

<script>
import {defineComponent} from 'vue';
import JsonExcel from "vue-json-excel3";
import axios from 'axios';

export default defineComponent({
  name: 'IndexPage',
  components: {
    downloadExcel: JsonExcel
  },
  data() {
    return {
    }
  },
  methods: {
    async fetchData() {
      let repoUrl = 'https://jsonplaceholder.typicode.com/users';
      return axios.get(repoUrl)
        .then((response) => {
          console.log(response.data)
          return response.data;
        })
        .catch((error) => {
          this.persons = error.response.statusText;
        });
    },
    startDownload() {
      alert('show loading');
    },
    finishDownload() {
      alert('hide loading');
    }
  }
});
</script>

These same code is working fine for me. Make sure you have not blocked the download.

Yah it should work is there any error in console can you try with static data it's working ?

Negative, no errors appears :(

Can you share any sample vue repo so I can check with sample data ?

Closing issue bcz of inactive


igluctl: consider master static command

Command that performs whole usual workflow as single step:

lint
static generate --with-json-paths
static push to Iglu Server (possibly several)
static s3cp schemas to Static Registry (possibly several)
static s3cp JSONPaths to S3
Optional: deploy new table (new subcommand)

Command can short-circuit on first failed step (e.g. lint is not good enough) and be idempotent. List of registries (as well as linting rules) can be defined in a separate config file.

Awesome idea!
A couple of notes/things to consider:

We might consider another master-test command which pushes to SP Mini - in my experience people will generally follow the path of least resistance with this tool, so there's a risk of people pushing untested schemas if we make that easier than testing.

The lint portion of the command should default to skip the description check - a lot of users forgo the field descriptions, and really that isn't a necessity for a schema. It could be quite a frustrating UX if they're blocked by this.

On the above point but not strictly this use case: I think the lint command should default to skip the description check when run individually too - for the same reasons (let me know if that should be a discussion elsewhere/another issue).

I think the idea here is great but as @colmsnowplow says, we need to be careful about blurring the dev-test cycle and the prod cycle into one.

Hey @colmsnowplow, all your points are actually covered by idea of configuration file:

Users might want to have separate config for Snowplow Mini, where only Mini's address specified in registries array
Config file would have array of enabled/disabled checks
...which means individual file will be able to disable description-check

Basically user will have two separate config files production.json and mini.json

Scheduled this for R10 static deploy. Please feel free to advice on better name if someone have any suggestions.

Fully agree with not blurring the testing / dev cycle into one! Some other ideas:

One thing that'd be nice on the QA side would be to automate the clearing of the cache when updating existing schemas. It's quite easy to forget to do this when you're rolling out tracking and it can be quite confusing when you expect the events to land in Mini.

When using static generate --with-json-paths it would make sense if the command also deleted the pre-existing jsonpath file and replaced it with the new one. If you don't delete the file manually you get a message which says that the file already exists.

@keanerobinson

When using static generate --with-json-paths it would make sense if the command also deleted the pre-existing jsonpath file and replaced it with the new one. If you don't delete the file manually you get a message which says that the file already exists.

This functionality exists with the --force argument I believe (which overwrites the files). Agree that it should be taken into consideration in the next version.

good point - I've gotten so used to just manually deleting the file beforehand. It feels like --force should be run by default for the jsonpaths or be set in the mentioned config filea.

Hey @keanerobinson! Thanks for the feedback! But unfortunately I cannot do anything regarding both issues you've raised.

Igluctl knows nothing about Snowplow mini and its cache. It works with Iglu Server directly which is an independent Snowplow Mini component. To be honest, I understand how annoying it can be, but cannot even think of what component can be responsible for automatic cache clearing. Probably something in Snowplow Insights, but we're far away from it
--force by default is a very dangerous behavior. We'll break much more things if Igluctl will be able to mutate existing assets for any smallest change. But on a very bright side - we should start working on removing JSONPaths altogether so a lot of related issues should go away with it.

or be set in the mentioned config files

Although, this can be an option!

re 1: good to know!
re 2: Looking forward to not having to worry about jsonpaths! Being able to set with-json-paths to delete and replace existing jsonpaths in the config file would also still be a time saver.
One final note on the proposed master-test. I think this command should:

lint
static push

I'm not sure if it makes sense to static generate the DDL / jsonpaths at this stage as a QA session with SP Mini often entails further schema changes. Again, this could also be a configurable command.

what component can be responsible for automatic cache clearing

Probably a Snowplow Control Plane API call eventually.

Probably a Snowplow Control Plane API call eventually.

Sure, but I mean on client-side

Few points on configuration file (leaving here as https://github.com/snowplow/iglu/issues/383 will likely be merged into this ticket):

As @colmsnowplow mentioned - we need to consider igluctl configuration file as a definition of particular deploy process. However user would like to separate his Test/Mini and Prod environments should be reflected in two separate configs
Therefore, as @keanerobinson proposed - it also should include list of commands. E.g. a separate array that in igluctl_mini.json would contain  "steps": ["lint", "static push"] and without any S3 buckets for JSONPaths and without options specific to static generate
In igluctl lint we decided to skip checks because this is how users could always have strictest possible linting by default. But in static deploy it could be other way round (include) because configuration files could be just copied around and users wouldn't have to remember all possible checks and add them every time

in static deploy it could be other way round (include)

This makes sense because then a deploy process doesn't suddenly break because of an Igluctl upgrade (because the existence of a new check won't matter until config files are updated to make use of it).

Can we set out exactly how the new functionality will be used? An example would be ideal. Reading this thread to try to understand that is quite confusing...


Seperate view life cycle method

finalize onCreateViewHolder, onBindViewHolder , this fix #3
make onCreateHeaderViewHolder, onCreateFooterViewHolder, onBindHeaderViewHolder, onBindFooterViewHolder not abstract, since headers and footers are optional, users may ignore to override those method.
seperate onFailedToRecycleView to onFailedToRecycleHeaderView, onFailedToRecycleItemView, onFailedToRecycleFooterView
seperate onViewAttachedToWindow to onHeaderViewAttachedToWindow, onItemViewAttachedToWindow, onFooterViewAttachedToWindow
seperate onViewDetachedFromWindow to onHeaderViewDetachedFromWindow, onItemViewDetachedFromWindow, onFooterViewDetachedFromWindow
seperate onViewRecycled to onHeaderViewRecycled, onItemViewRecycled, onFooterViewRecycled
update robolectric dependency to 3.0
update mockito dependency 1.10.19
update junit dependency to 4.12
add powermock 1.6.4 dependency
seperate test base class to PowermockTest, RobolectricTestWithMockito, RobolectricTestWithPowermock. Because I can't get spy() work with RobolectricTestWithPowermock, while it's really useful to mock final methods.

I have tested my change in Unit test, in the example project, and in one of my own project.

Thanks for your PR @cmicat!! I'l continue reviewing your code once you apply the comments I've posted.

@flipper83 can you also review this PR, please? I need two confirmations.

Since I changed a lot of things, according to advices of @pedrovgs, I rewrite what I did as following.

Finalize onCreateViewHolder, onBindViewHolder , this fix #3
Make onCreateHeaderViewHolder, onCreateFooterViewHolder, onBindHeaderViewHolder, onBindFooterViewHolder not abstract, since headers and footers are optional, users may ignore to override those method.
Seperate onViewRecycled to onHeaderViewRecycled, onItemViewRecycled, onFooterViewRecycled.
Update robolectric dependency to 3.0
Update mockito dependency 1.10.19
Update junit dependency to 4.12
Add powermock 1.6.4 dependency
Seperate test base class to PowermockTest, RobolectricTest. Because I need to mock android.support.v7.widget.RecyclerView.ViewHolder.getAdapterPosition() in android support library, but it's a final method, Robolectric don't support to mock it. I have tried to use Powermock and Robolectric together, but it's problematic, and always fail for some reason. EG: Both Powermock and Robolectric use a custom classloader, and they will have conflicts.

Just one comment pending to be reviewed!!! Replace the DebugHelper class with a simple log and we are done!!

Ok, done. Thank you for your excellent work with this library.

Thanks @cmicat you have my :+1:

@flipper83 do you want to add something else?

yo have my :+1: too


Sema: Correct availability for @inlinable global var accessors bodies

The bodies of unavailable functions should be typechecked as if they would always run at the deployment target, even if they are @inlinable. This was not the case in the bodies of unavailable @inlinable global var accessors, though, because the availability of the accessor, rather than enclosing var, was being queried. The fix is to use getSemanticUnavailableAttr().
Resolves rdar://113642576

@swift-ci please test

@swift-ci please smoke test


On-the-fly spacy language model downloading requires allowing access to a lot of GitHub IP addresses

The Spacy language model is downloaded dynamically for PII classification. In our kubernetes setup, this required a network policy to allow access to a long list of GitHub IP addresses. We would strongly prefer not to have such an open connection from our private network, for data security reasons obviously.
I noticed this dependency was initially built-in but removed in https://github.com/open-metadata/OpenMetadata/pull/1362.
Can we consider adding it back again? Perhaps there is a way to speed up builds.
Or would there be an alternative way to provide the package without having to connect to GitHub?

we are not using spacy anymore, cc @pmbrull can you confirm and close this out

Can you confirm which NLP model you are using right now?

hi sorry missed this one. We still use spacy as the way to run the presidio NLP model here https://github.com/open-metadata/OpenMetadata/blob/main/ingestion/src/metadata/pii/scanners/ner_scanner.py#L53

@svroonland I believe that you might be able to just write on top of our Ingestion image and download the model on your own. For us it's important to keep the package as small as possible, since not all users would want this functionality. Downloading this by default makes the resulting images quite big

That is indeed what we did to resolve this issue. Thanks for considering.

@pmbrull I have understood the presidio NLP model and we just added some entities in ner.py which are supported by presidio (see below). But when we ran Profiler ingestion after that it didn't tag related entities.
#India
IN_PAN = TagType.SENSITIVE.value
IN_AADHAAR = TagType.SENSITIVE.value
IN_VEHICLE_REGISTRATION = TagType.SENSITIVE.value
We changed the code for our virtual env so it should work or we need to make changes somewhere else also.
And if you can help in how we can write column name regex for the above entities and all related changes that would be great.

hi @sharmalokeshk, having this on the enum you mentioned should be good enough, thanks!. Feel free to open a PR with this change. I am not sure having those into regex might be the best approach since it can become very complicated very easily. Might be safer to rely on presidio's scan of sample data to detect these entities. Note how on the regex rules, we do very basic validations while relying on presidio for complex stuff, such as IBAN codes or other national IDs


Parameters Pass for "Optimal Savings III: Occasionally Binding Constraints"

Not much going on in this one; there was one struct that wasn't mutated.
#135

See if everything is good. Made a note of the missing maximize pass.

I am arguing that the Setup include should be right before the using Test cell (right before the first code cell) instead of currently where it stands before the markdown cells explaining the lesson and the start of the code cells.

@Nosferican checked with Jesse, and I don't think he minds too much. So this should be fine. Will merge now.


Add informatica job to lower environment(s)

There is no informatica job in the lower environments. This affects the ability to test CBS changes to plant and unit data that is logged to INVENTORY_STATUS_LOG.

Review other informatica tickets.
Discuss with Mark to see if there are any tables that need to be added.


[FEATURE REQ] Azure.Messaging.ServiceBus_7.0.0 - Add maxWaitTime parameter to ReceiveMessagesAsync

Library or service name.
Azure.Messaging.ServiceBus_7.0.0
Is your feature request related to a problem? Please describe.
We are using Azure.Messaging.ServiceBus to write integration tests that check the rules we have set on our subscriptions.
Some of these tests are checking that unintended messages are not received by a subscription.
To do this we're using public virtual IAsyncEnumerable<ServiceBusReceivedMessage> ReceiveMessagesAsync([EnumeratorCancellation] CancellationToken cancellationToken = default) by passing a CancellationToken that uses a TimeStamp.
However it seems that the CancellationToken is not enough, because the method calls under the hood public virtual Task<ServiceBusReceivedMessage> ReceiveMessageAsync(TimeSpan? maxWaitTime = null, CancellationToken cancellationToken = default); without passing any maxWaitTime.
This means that even if we want to use the CancellationToken to wait at most 5 seconds for a message to not be received, it will actually wait 1 minute (the default value of maxWaitTime).
Our current workaround was to create an extension that takes the maxWaitTime parameter as well, however it would be nice to have this part of the SDK.
This is our extension:
        // Existing method doesn't allow passing maxWaitTime
        // https://github.com/Azure/azure-sdk-for-net/blob/6adff9084cf51a0f082e813ee8d7b7daef117642/sdk/servicebus/Azure.Messaging.ServiceBus/src/Receiver/ServiceBusReceiver.cs#L290
        public static async IAsyncEnumerable<ServiceBusReceivedMessage> ReceiveMessagesAsync(this ServiceBusReceiver self, TimeSpan? maxWaitTime = null, [EnumeratorCancellation] CancellationToken cancellationToken = default)
        {
            while (!cancellationToken.IsCancellationRequested)
            {
                var msg = await self.ReceiveMessageAsync(maxWaitTime, cancellationToken).ConfigureAwait(false);

                if (msg == null)
                {
                    continue;
                }

                yield return msg;
            }

            // Surface the TCE to ensure deterministic behavior when cancelling.
            cancellationToken.ThrowIfCancellationRequested();
        }

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

The maxWaitTime parameter wasn't included on the IAsyncEnumerable because this method is most useful when you want to keep receiving messages indefinitely without needing the finer level of control that the ReceiveMessageAsync or other ReceiveMessagesAsync overload offer. Would either of those work for your scenario?

Based on our use case ("trigger" a message that doesn't match the rules on the subscription and make sure that in a given period of time it isn't received) the IAsyncEnumerable method is the best candidate for us.
We can't use the other ones because we also want to handle the scenarios when unrelated messages (from other manual or automated testing going on at the time of running the test). This means that we continue to receive messages and filter them based on a test controlled customId as per the example below:
        public static async Task<ServiceBusReceivedMessage> ReceiveMessageAsync(this ServiceBusReceiver self, string customId, TimeSpan maxWaitTime)
        {
            var cancellationToken = new CancellationTokenSource(maxWaitTime).Token;

            await foreach (var message in self.ReceiveMessagesAsync(cancellationToken))
            {
                if (message.ApplicationProperties["customId"].Equals(customId))
                {
                    return message;
                }
            }

            // This is never reached because of the exception caused by maxWaitTime
            return null!;
        }

And this is how we use it:
            Func<Task> receiveFunc = async () => await serviceBusReceiver.ReceiveMessageAsync("someTestControledId", DefaultDontReceiveMaxWaitTime);
            receiveFunc.Should().Throw<TaskCanceledException>();

I agree that our use case is not really common, so I understand if the suggested feature doesn't make sense from a broader perspective.
However, as mentioned initially, if we use a CancellationToken instantiated with a TimeSpan shorter than the default maxWaitTime then that CancellationToken won't trigger any timeout.
I understand that the intended use case is not to pass CancellationToken instantiated with a TimeSpan, so I guess it makes sense to keep it as is.

Thanks for the additional context. I think we can leave this issue open for now to track this feature request.


Entity Framework and SQL profiler

Dear,
Amazing library!!
There is possibility to measure EFCore and SQL query like miniprofiler do?

Thanks, glad you like it!
Yeah I've thought about that, I think a metrics collection agent would be better for this type of job.

I agree, the ideal could be to having a DASHBOARD about WEB RESPONSIVENESS (Apdex and around), a DASHBOARD for AUTHENTICATION (oauth and around), and a new DASHBOARD for DATA RELIABILITY (bottleneck, query N+1, worst top 10 queries, etc.)


feat: Added support for ALB trust store

Description
Closes: https://github.com/terraform-aws-modules/terraform-aws-alb/issues/342
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/mutual-authentication.html
https://aws.amazon.com/blogs/aws/mutual-authentication-for-application-load-balancer-to-reliably-verify-certificate-based-client-identities/
Motivation and Context
https://github.com/terraform-aws-modules/terraform-aws-alb/issues/342
Breaking Changes
No.
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

we might want to just wait for 5.33 for this bugfix https://github.com/hashicorp/terraform-provider-aws/pull/35289 - should be out tomorrow (thursday) - we can raise the MSV to 5.33 for this


Add a tx only and a rx only serial instance

This also makes the serial stuff in https://github.com/stm32-rs/stm32f0xx-hal/pull/27 obsolete.
Additionally by virtue of how it works also implements https://github.com/stm32-rs/stm32f4xx-hal/pull/49 here.
Not sure how we should handle the release method. It currently works but you get a () for the unused pin back.
Currently untested

I have some thoughts on this, will put together an actual review in a bit, kinda busy atm


Update prometheus jobs when trino configurations updated.

Everytime trino configuration updated, trino coordinator and workers in the dedicated trino cluster will be rollout restarted.
At that time, all the endpoints of trino coordinator and workers will get new addresses for their pods, so these changed endpoints addresses of trino coordinator and workers will be updated as prometheus jobs to prometheus configmap.

https://github.com/cloudcheflabs/dataroaster/pull/31


Push live

Microsoft Reviewers: Open in CodeFlow

Docs Build status updates of commit 26b97b2:
:warning: Validation status: warnings

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/react-native/theme-config.md
:warning:Warning

Details

AdaptiveCards/resources/partners.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/react-native/getting-started.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/toc.yml
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/react-native/theme-config.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 1, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 1, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

AdaptiveCards/resources/partners.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

AdaptiveCards/sdk/rendering-cards/react-native/getting-started.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 836b8cd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/resources/partners.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/react-native/getting-started.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/react-native/theme-config.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Issue GUI-3: Grafana Weighted Triangles Algorithm

@veronikaKochugova, looks like your comments have been addressed. Could it be approved?


IRGen: Add code to support building fragile resilient protocol witnesses

We don't currently support building resilient relative protocol witness tables. One might want to build with relative witness tables but not need resilient protocols. Allow for that scenario.
Add a test configuration to test library-evolution + fragile resilient protocols + relative protocol witness tables.

@swift-ci test

@swift-ci test

@swift-ci test


TypeError: 'module' object is not callable

Receiving error while using the library as below
from uniswap import uniswap
account_1="..."
private_key="..."
uniswap_wrapper = uniswap(account_1, private_key, version=2)  # pass version=2 to use Uniswap
the error is
" uniswap_wrapper = uniswap(account_1, private_key, version=2)  # pass version=2 to use Uniswap
TypeError: 'module' object is not callable"
pls advise the solution

Your import statement is incorrect. It needs to be from uniswap import Uniswap.


MLVPN uses Salsa20, not Chacha20.

This is a trivial change, but MLVPN uses Salsa20, not ChaCha20.

That's correct. Thank you for the merge request, really appreciate it.


BE custom msg instead of generic errors

Use this ONLY for reporting bugs. For requesting new features check this link.

Expected Behavior
You should show what happens if you have it in response.
Current Behavior
Registration form on the sign in modal. When you are trying to register the same email address BE is responding with custom msg and we are showing general error try to reload the page.
Possible Solution
Use custom msg from the response.
Steps to Reproduce

Click Manage my booking modal in the navbar sign in modal will pop up.
Choose option register.
Fill the form with existing email address.
Submit.

Screenshot
http://take.ms/5Ct6A

Invalid, should be reported in nitrolib.


[astro-purgecss] All CSS gets removed

Describe the bug
A clear and concise description of what the bug is.
I'm importing a CSS file into my Layout,astro (only in this file) like this: import "../styles/bulma.css", but the integration doesn't seem to recognize external CSS files and just dicards them.
To Reproduce

Create a CSS file in src/styles/
Import the file into the central Layout file (Layout.astro): import "../styles/file.css"
add purgecss integration to astro.config.mjs
build project

Expected behavior
Removal of some of the CSS, so the file is as small as possible
Screenshots

(1. purgecss removed all CSS)
(2. Expected Look)
(3. Style import into Layout)
(4. Integration)

@the-dijkstra
yes, pretty much every element uses one of the css file's classes.

After some closer inspection, it seems as if every styling, apart from the styling in the main layout file (in this case: App.astro), is being removed.

do you have a link where I can reproduce this?
yes, I just uploaded a demo repository with steps to reproduce this

any news on this @the-dijkstra ?

Thanks for the answer.
I settled with vite-plugin-purgecss now, which seems to work fine


Docker remote run

This adds an option to the run.sh script to use the remote image from github (and downloading it if it doesn't exist) rather than using a locally built one. This could save some hassle from having to build the image locally.
TODO

[x] add a few sentences to the docs
~- [ ] add a quickstart section to the base readme~ already there under usage

The documentation change seems mostly good to me, but it also removed the note that the Docker run.sh requires your host OS to be native Ubuntu. Is that not a valid note anymore?
If it makes sense to keep the note, it might be good to move it earlier in the process. (In general, system requirements should come early so people don't start the process then get disappointed partway through when they realize they can't finish.)
It might also make sense to explain a bit why the restrictions are there. Like in theory a user could modify the run.sh script pretty easily to support other Linux flavors, right, might just involve tweaking commands related to X forwarding or something? And the requirement to run the Docker container in a native host OS rather than a VM is related to GPU acceleration? I feel like explaining it is good because one of the main selling points of Docker is that the containers are portable, so it's counter-intuitive that our approach is not portable, but I'm sure it makes sense once you go through it.

I mostly removed it because I didn't understand the restrictions. I'm not sure there is anything special about Ubuntu which makes it a requirement, as far as Linux distros go. And likely, anyone on a different distro likely has the skillset you mention. This doesn't even preclude someone using WSL, with X11 forwarding.
Basically, in my opinion, native Ubuntu is not a requirement. I agree that it may be informative to change the verbage rather than deleting it.

I mostly removed it because I didn't understand the restrictions. I'm not sure there is anything special about Ubuntu which makes it a requirement, as far as Linux distros go. And likely, anyone on a different distro likely has the skillset you mention. This doesn't even preclude someone using WSL, with X11 forwarding.
Basically, in my opinion, native Ubuntu is not a requirement. I agree that it may be informative to change the verbage rather than deleting it.

I like how you put it simply in your updated text, especially useful that you link to good additional resources.
If there is anything to change, it might be "Ubuntu" -> "native (non-VM) Ubuntu". (Unfortunately, working in a VM is what all of our interns think of trying first on their locked-down government laptops. If we know it won't work, we should tell them up front.)

Good point, fixed!


Better composePrism for POptional

Motivation: POptional composed by current inplementation is unable to set a value properly if it points to None, because it calls modify underhood. reverseGet of PPrism always returns a valid value to set, so it's better not to convert PPrism to POptional for composition.
Please tell, if it is necessary to open a separate PR agains cats branch (I actually use cats version).

@danslapman Thanks, could you add an example/test to show the issue

@julien-truffaut sure
sealed trait AB
case object A extends AB
case object B extends AB

object AB {
  val a: Prism[AB, A] = ...
}

case class Bar(foo: Option[AB])
object Bar {
  val foo: Optional[Inner, AB] = ..
}

..

val barA = Bar.foo ^<-? AB.a

val bar = Bar(None)

barA.set(A)(bar) //Currently will do nothing

I will fix composeIso shortly as well.

Thanks unfortunately this is the intended (lawful behavior). I am on my phone but I believe you will get an error if you check your Optional is lawful.

@julien-truffaut thank You, got it.

@danslapman please let me know if you want a more detail explanation. Almost everyone gets bitten by this.

@julien-truffaut in fact it's pretty convenient to have a composasble Optional-like optic, that is able to set a value, Lens[A, Option[B]] does not compose. Maybe intoduce some lawless "OptionalInsert" in monocle-unsafe?

IMO this law is one of the most fundamental, so I would rather not include this kind of lawless Optional.

Okay

@julien-truffaut then, maybe add some optic that can only set?

it would not integrate with the existing optic stack. E.g. A Setter[S, A] cannot be transformed to a SetOnly[S, A] because it is set will have a different behaviour.
Optics are abstractions to zoom into 0, 1, n values of the same type. They follow the Functor / Traverse law that says that an Optic / Functor / Traverse cannot affect the structure, only the value. Here you are trying to update the structure because you want to "create" something. The only way to do that with optics is if you have an Optic[S, Option[A]] in this case you case set(Some(a))

Setter[S, A] cannot be transformed to a SetOnly[S, A]
but it can be composed

I mean something like that:
abstract class PInjector[S, T, A, B] extends Serializable { self =>
  /** set polymorphically the target of a [[PInjector]] with a value */
  def set(b: B): S => T

  def ^|-:[W, G](other: PLens[W, G, S, T]): PInjector[W, G, A, B] =
    b => other.modify(set(b))
}


Add null as valid binding type

This change allows null into the bindings parameter of .raw() to typecheck properly
@lorefnon could you verify if this is the correct way to fix this

@Naddiseo Thanks for your PR. Yes, not having null in binding types was an oversight.

Released in 0.21.3


unclear sentence

Section Number <IP_ADDRESS>
Issue  I cannot parse this sentence: Typically in health related environments, a healthcare professional accesses patients or organization related data (resources) for which the healthcare professional is not the "legal owner", but may access according to the access policies of the environment. To avoid any misunderstandings related to the OAuth term "resource owner" and the term "legal owner", this profile uses the term "user" instead.
Proposed Change  Can't suggest a change until I understand it

The intention of this statement is: It's a well known problem that OAuth uses the term "resource owner" for the user, who authorizes the application access to the data. The term "resource owner" suggests, that the user has the property rights on the data, can determine who has access to the data, etc. While this might be the case if you use Google and want to allow other applications to access your Google data, this is not true in general. The property rights on health data are assigned to the patients concerned (e.g, in the EU) or to the hospital the user is employed. To avoid this confusion, IUA uses the term "user" only.


Disk Space

Hi
i am using 40GB Disk Space and i just sent 70K email and now it's shows there is no space and showing error 500
What will be the problem ?

You need to log in to your server with SSH and use the du command to figure out which directory is too big.

Hi
I remove all log fine the now it's working.. remove from postal/log
do i need to remove regularly ? or there is something wrong ?

Just go to Advance Setting in Postal and change the-
Message retention days & Raw message retention days to less days. It will eventually remove logs after those days

If your logs were responsible for filling up your hard drive, you almost definitely have a problem.
If your database was the main problem then you will need to change your retention settings.

I did retention setting to 1 day but still i can see this much of GB used..if i keep 1 day this it should be 0 after a day am i right ?
i am talking about postal top of the right side GB details

That should be the way it happens yes. Can you send some screenshots if it isn't happening?

https://imgur.com/a/xrk8e

You are sending quite a lot of emails and if they have attachments or embedded imagery, that would take up a fair amount of space.
Out of curiousity, can you try setting it to 2 days and see what happens?
Also please read https://github.com/atech/postal/issues/353 as there can be accidental deletion of unsent messages as the size limit setting takes priority over the day limit setting.

40GB is really not much disk space, but should definitely be sufficient. The best thing to do would be to use du to determine where the space is used. In particular, it might be used by the app (by logs) or by MySQL. the solution may depend on where the space is being used.


Really exciting but I'm itchin for that youtube tutorial

I've figured out a few things but there's not a lot of chatter at all yet about creating new maps. I can't figure out how to get any assets from the game to load alongside this stuff. I am a bonehead novice but this seems super cool

Agreed, the Youtube tut would be awesome! Do you have a discord peeps can join for help too?

I'll open a discord if the mod and sdk works well

you should open a thread in the actual modding discord for this game the one thunderstore links on their page https://discord.gg/XeyYqRdRGC

I can’t even get it to work. I made moons than doesn’t work.  Can you explain better for me?  I use Unity daily anwyays, so I know how Unity works.  Just the read me is confusing to me lol.

I just trying to make custom moons with the scene builder you provided.
Sent from my iPhone
On Dec 11, 2023, at 4:19 PM, DENIEL-VALERO Ewan @.***> wrote:

I can’t even get it to work. I made moons than doesn’t work. Can you explain better for me? I use Unity daily anwyays, so I know how Unity works. Just the read me is confusing to me lol.
Make a video where you show every object of your mod in inspector, i will tell you if something is wrong
I still have a lot to do, fix or add before to make a video tutorial
—
Reply to this email directly, view it on GitHubhttps://github.com/HolographicWings/LethalSDK-Unity-Project/issues/1#issuecomment-1850904671, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYX3CAIKCEC7BC7VUNIW43LYI52FRAVCNFSM6AAAAABAL577NGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJQHEYDINRXGE.
You are receiving this because you commented.Message ID: @.***>

I just trying to make custom moons with the scene builder you provided.

Yes, but i need an overall video of what you done


Problem from applying pipeline parallel with Tutel's cumsum

I just got an error when applying Torch pipeline parallel with Tutel's cumsum. The problem is caused by the non zero return value of cuLaunchKernel in tutel/tutel/custom/custom_kernel.cpp. To investigate the issue, I added printf to tutel/tutel/custom/custom_kernel.cpp to print that return value and found that the value is (CUDA_ERROR_INVALID_HANDLE == 400)
From NVidia's docs, I found that the following information about CUDA_ERROR_INVALID_HANDLE,
This indicates that a resource handle passed to the API call was not valid. Resource handles are opaque types like CUstream and CUevent
Here is the sample code to reproduce the problem,
from tutel.jit_kernels.gating import fast_cumsum_sub_one
from torch.distributed.pipeline.sync import Pipe

import torch

def _initialize_pipeline_parallel(num_nodes, nstages):
    '''
    Initialize pipelining framework.
    Args:
      nstages : Total number of pipeline stages.
    '''
    #print("==> inside initialize-pipeline_parallel :")
    assert num_nodes == 1, "Only single node pipeline parallelism is supported right now"
    from torch.distributed import rpc
    import tempfile
    tmpfile = tempfile.NamedTemporaryFile()
    rpc.init_rpc(
        name="grid_worker",
        rank=0,
        world_size=num_nodes,
        rpc_backend_options=rpc.TensorPipeRpcBackendOptions(
            init_method="file://{}".format(tmpfile.name)
        )
    )

class CumsumModule(torch.nn.Module):
    def __init__(self):
        super(CumsumModule, self).__init__()
        self.param = torch.nn.Parameter(torch.ones(5, 5))
    def forward(self, x):
        x = x + self.param
        x_cumsum = fast_cumsum_sub_one(x, dim=0)
        return x_cumsum

_initialize_pipeline_parallel(1, 2)

input = torch.randint(0, 5, (5, 5), device='cuda:0')
cumsum_module0 = CumsumModule().to(device='cuda:0')
cumsum_module1 = CumsumModule().to(device='cuda:1')
model = torch.nn.Sequential(cumsum_module0, cumsum_module1)
model = Pipe(model)
output = model(input)

The following is the error messages,
Traceback (most recent call last):
  File "Reproduce.py", line 42, in <module>
    output = model(input)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/distributed/pipeline/sync/pipe.py", line 362, in forward
    self.pipeline.run(batches)
  File "/opt/conda/lib/python3.8/site-packages/torch/distributed/pipeline/sync/pipeline.py", line 117, in run
    self.compute(batches, schedule, skip_trackers)
  File "/opt/conda/lib/python3.8/site-packages/torch/distributed/pipeline/sync/pipeline.py", line 257, in compute
    raise exc_info[0].with_traceback(exc_info[1], exc_info[2])
  File "/opt/conda/lib/python3.8/site-packages/torch/distributed/pipeline/sync/worker.py", line 79, in worker
    batch = task.compute()
  File "/opt/conda/lib/python3.8/site-packages/torch/distributed/pipeline/sync/worker.py", line 60, in compute
    return self._compute()
  File "/opt/conda/lib/python3.8/site-packages/torch/distributed/pipeline/sync/pipeline.py", line 222, in compute
    return batch.call(partition)
  File "/opt/conda/lib/python3.8/site-packages/torch/distributed/pipeline/sync/microbatch.py", line 70, in call
    return Batch(function(self.value))
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/container.py", line 119, in forward
    input = module(input)
  File "/opt/conda/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "Reproduce.py", line 32, in forward
    x_cumsum = fast_cumsum_sub_one(x, dim=0)
  File "/home/chutsai/.local/lib/python3.8/site-packages/tutel/jit_kernels/gating.py", line 83, in fast_cumsum_sub_one
    return get_cumsum_kernel(data.size(0), data.size(1))(data)
  File "/home/chutsai/.local/lib/python3.8/site-packages/tutel/jit_kernels/gating.py", line 72, in optimized_cumsum
    base_kernel(mask1.to(torch.int32).contiguous(), locations1)
  File "/home/chutsai/.local/lib/python3.8/site-packages/tutel/impls/jit_compiler.py", line 41, in func
    tutel_custom_kernel.invoke(inputs, __ctx__)
RuntimeError: (0) == (cuLaunchKernel(gm.hFunc, gm.blocks.x, gm.blocks.y, gm.blocks.z, gm.threads.x, gm.threads.y, gm.threads.z, 0, nullptr, ppargs.data(), nullptr)) INTERNAL ASSERT FAILED at "/tmp/pip-req-build-u7pfjlvx/tutel/custom/custom_kernel.cpp":146, please report a bug to PyTorch. CHECK_EQ fails.

Please help me to solve this issue or tell me if did not use the Tutel correctly. Thanks.

Thanks for showing this requirement. The current JIT compilation only handles "1 program accessing 1 self-owned device" which doesn't work for other environments.
There is a temp fix for your requirement, can you try this branch: https://github.com/ghostplant/tutel/tree/fix_jit


PR: Algo Jump search in Python

@Abishethvarman Added a document for this as well, as the content was similar.

No description provided.

add description

Can be closed?


openafs: 1.8.10 → 1.8.11, patch for Linux kernel 6.8

Description of changes
Firstly, upgrade OpenAFS from 1.8.10 to 1.8.11 (dropping patches now included upstream).
Secondly, add the upstream patches for Linux kernel 6.8. This is required for building with linuxPackages_latest.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.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.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3687


OOM

Increasing the content of this gridview a memory overflow, increased memory and will not be released, the question whether there is notice?

Out of memory
Increasing the content of this gridview a memory overflow, increased memory and will not be released, the question whether there is notice?

Please provide a more descriptive issue and a sample project to help reproduce, if possible. There is not much that can be done based on this description.


update deprecated warn(), py 3 strings, whitespace

tests all pass (eventually)

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (f97d8b9) 86.71% compared to head (ccc7eb2) 86.97%.
Report is 23 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #337      +/-   ##
==========================================
+ Coverage   86.71%   86.97%   +0.25%
==========================================
  Files           2        2
  Lines         256      261       +5
==========================================
+ Hits          222      227       +5
  Misses         34       34

Files
Coverage Δ

pipreqs/__init__.py
100.00% <100.00%> (ø)

pipreqs/pipreqs.py
86.82% <90.00%> (+0.26%)
:arrow_up:

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


Add extra options to scrape config (scheme, basic_auth, tls_config)

Enhancement Proposal
I am trying to integrate prometheus-k8s with the Juju controller charm, to make it easy for COS Lite to observe Juju controllers. This involves implementing the prometheus_scrape library on the controller charm.
The Juju controller's metrics endpoint requires the following scrape-jobs config (see e.g. here):
- job_name: juju
  metrics_path: /introspection/metrics
  scheme: https
  static_configs:
    - targets:
      - '<controller-ip>:17070'
      labels:
        juju_model: controller
        host: controller-0
  basic_auth:
    # Need a user "foo" that has read access to controller
    username: user-foo
    password: 1234
  tls_config:
    ca_file: /path/to/juju-ca.crt

However, I notice that the MetricsEndpointProvider doesn't accept the fields scheme, basic_auth or tls_config (these are not in ALLOWED_KEYS and so will get removed from the passed-in jobs). I have tested manually with prometheus2 and verified that all these keys are necessary.
Hence, I would like to request an implementation of scheme, basic_auth and tls_config in the jobs config, as per the yaml above.

This should not require more than adding the allowed keys to work. One question though; how do we get the cert into the scraper (prometheus or grafana agent)?

Good question, I was just thinking about that. In this case, it should be stored on the controller machine somewhere. I'll consult the team and get back to you.

Will this work for you?

That should work, I also like that you're not suggesting using the  actual name of the config option (ca_file) as that is requiring a path rather than the file content. This way we are distinguishing our somewhat special way of passing it from the official implementation.

The official (upstream) tls_config has the following fields: ca_file, cert_file, key_file.
I think I would probably opt for keeping the same key name as upstream for consistency, but either way is probably fine.

The official (upstream) tls_config has the following fields: ca_file, cert_file, key_file.
I think I would probably opt for keeping the same key name as upstream for consistency, but either way is probably fine.

As I said, that field expects a path to a file, not file contents, so trying to aim for consistency would rather end up being misleading in my opinion. :)

@barrettj12 I am looking into this now.
Before writing tests I would like to first poke around manually.
How do I curl the controller? I tried the following but it didn't work.
$ juju controllers --format json | jq '.controllers.uk8s."api-endpoints"'
[
  "<IP_ADDRESS>:17070"
]

$ juju controller-config ca-cert > /tmp/juju-ca.crt

$ juju add-user prometheus
$ juju change-user-password prometheus
$ juju grant prometheus read controller

$ curl -u prometheus:prom -X GET --cacert /tmp/juju-ca.crt https://<IP_ADDRESS>:17070/introspection/metrics
curl: (60) SSL: no alternative certificate subject name matches target host name '<IP_ADDRESS>'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

When I check what juju is saying, I don't see Juju server certificate:
(Note: this is from a disposable test env)
$ openssl x509 -text -noout -in /tmp/juju-ca.crt -subject
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            0e:26:bc:8f:b3:33:b5:2b:72:88:3b:bf:e9:d2:fb:05:b5:1f:bf:09
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: O = Juju, CN = juju-ca
        Validity
            Not Before: Aug 31 04:36:04 2022 GMT
            Not After : Aug 31 04:41:04 2032 GMT
        Subject: O = Juju, CN = juju-ca
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (3072 bit)
                Modulus:
                    00:bc:50:83:be:91:6b:b3:34:c4:c3:c5:d9:a9:13:
                    1c:18:4b:d0:15:45:45:49:ce:f9:bd:ec:18:1c:b7:
                    a7:0c:e1:be:05:8c:8f:e8:c3:b3:ed:af:e7:49:84:
                    e3:0d:b1:6d:1c:a5:06:ca:8d:36:58:2f:14:09:6c:
                    ad:99:7b:9f:55:2b:15:d4:f8:33:50:7e:e3:08:ab:
                    97:53:08:7f:cc:aa:97:1a:f6:e9:e0:de:ce:e4:b5:
                    be:f6:d4:46:d0:99:2d:4f:dd:f0:e7:43:b3:c3:c1:
                    ce:d2:7c:1c:a6:2f:3f:f5:2c:77:44:16:6b:9c:8f:
                    4b:bf:99:44:27:5b:50:23:94:c5:ba:69:fc:77:aa:
                    96:18:e7:fb:92:83:0e:f9:a5:91:2d:a8:94:ed:72:
                    60:a7:0e:fb:6f:37:41:f8:b8:36:7d:71:57:26:98:
                    c0:3c:06:2b:c2:9b:4d:54:e5:06:85:ce:7b:77:4b:
                    69:1c:56:88:fe:e6:f3:3b:52:36:d5:77:f6:50:12:
                    e1:d4:07:5a:40:40:f0:5c:61:49:84:19:1d:1d:46:
                    b1:11:fb:9b:06:01:e1:b8:42:55:25:3c:42:e5:63:
                    d4:f5:03:e5:83:5c:7c:f4:c2:1d:83:fd:2e:7b:7f:
                    fc:8d:9f:f3:8c:3f:16:9b:33:16:cc:c0:82:cf:d5:
                    77:d6:99:51:59:9b:0b:b2:49:02:e0:32:30:dc:14:
                    fe:ec:6f:d3:bf:16:45:a3:84:e2:43:75:2d:39:b0:
                    78:b8:3a:25:13:59:cf:cc:ee:40:91:fd:37:d4:5b:
                    f0:5c:a2:fb:70:fd:6c:5a:b3:27:f5:e2:35:f2:b8:
                    26:ad:87:f4:b9:6f:5a:ff:7d:d8:cf:15:42:0d:45:
                    52:23:13:70:2b:63:1c:7d:77:f2:0b:a1:7c:33:47:
                    59:9a:56:fc:99:85:33:6f:a0:5c:da:c7:a1:4f:21:
                    19:ae:10:ac:e9:5f:9c:70:ba:d3:d6:25:1b:f9:41:
                    a7:d5:82:0d:77:d6:45:d4:61:87
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment, Certificate Sign
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Key Identifier:
                CF:4A:B7:47:84:2C:86:9A:68:6C:6C:98:3E:98:20:2B:AE:76:AA:F8
    Signature Algorithm: sha256WithRSAEncryption
    Signature Value:
        7b:ac:ff:73:0d:2f:3d:cd:6c:00:fe:0b:b0:45:a1:94:da:6a:
        06:b9:c6:f2:a9:8e:dd:14:7a:9f:1d:ab:a0:76:eb:94:a7:8b:
        7d:75:59:2f:d8:1f:d0:7e:a3:7d:de:2c:e6:a7:b9:f9:f0:07:
        b5:11:b3:b8:ec:74:4d:bd:c7:e7:83:a9:4b:26:36:81:83:8f:
        9f:a0:94:ed:28:7f:d8:d2:86:7d:a7:f0:53:ad:3e:ad:c1:8c:
        ee:77:8d:24:af:c8:e6:1f:8e:39:ec:81:a4:ca:01:7f:5d:f2:
        0c:e4:ea:e9:2c:5e:50:d7:de:b8:47:19:1b:86:a5:89:a3:47:
        6c:40:69:47:a3:c9:1e:84:8c:87:32:06:ac:d2:fe:78:35:78:
        a8:f2:b0:de:fb:ce:6a:31:49:00:1d:50:81:e4:ac:3d:3c:73:
        99:97:7f:7e:e3:00:c1:21:e9:d4:e6:df:94:7f:a2:b9:9d:b4:
        0a:b6:c4:ff:8f:5d:45:04:3d:60:ee:9e:4f:ea:3f:97:42:cf:
        3b:ef:7d:77:5b:8f:4d:2b:2e:7b:48:82:97:40:3e:49:3e:0d:
        a3:68:70:7d:fe:98:32:cc:9a:0d:76:e9:37:c4:6a:5b:ab:53:
        27:dd:5b:34:97:ac:16:05:23:bb:64:4d:f7:fd:46:24:2d:f1:
        4e:3b:c8:cf:cd:bd:b5:b1:47:a7:16:f4:38:cd:d0:4f:54:e4:
        6c:1e:57:07:24:b0:a8:43:50:1b:dc:67:1f:74:c6:0a:e6:38:
        aa:8e:85:9f:41:db:2a:91:5d:87:cb:88:bb:56:7f:a6:48:63:
        46:ad:49:d7:81:c9:52:9d:a8:ea:f2:fa:67:7c:94:4f:3c:d7:
        f3:af:ad:4f:3b:48:8b:bd:4f:b6:78:02:4a:5f:0a:6d:de:06:
        c4:a1:d9:9f:4b:5b:49:29:de:15:ca:04:24:5b:a2:78:5d:e3:
        57:d8:fa:02:b9:13:13:64:68:89:30:05:8b:76:12:60:d2:57:
        fd:32:23:24:28:76
subject=O = Juju, CN = juju-ca

cc: @simskij

$ openssl s_client -connect <IP_ADDRESS>:17070 -showcerts </dev/null 2>/dev/null | openssl x509 -outform PEM > /tmp/juju-cert.pem

# Added <IP_ADDRESS> juju-apiserver to /etc/hosts

$ curl -vk https://juju-apiserver:17070/introspection/metrics -u prom:prom --cacert /tmp/juju-cert.pem
*   Trying <IP_ADDRESS>:17070...
* Connected to juju-apiserver (<IP_ADDRESS>) port 17070 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: O=Juju; CN=Juju server certificate - controller; serialNumber=e20ce9be-052c-4b31-8f53-cd29472445e0
*  start date: Aug 31 04:36:05 2022 GMT
*  expire date: Aug 31 04:41:05 2032 GMT
*  issuer: O=Juju; CN=juju-ca
*  SSL certificate verify result: self-signed certificate in certificate chain (19), continuing anyway.
* Server auth using Basic with user 'prom'
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET /introspection/metrics HTTP/1.1
> Host: juju-apiserver:17070
> Authorization: Basic cHJvbTpwcm9t
> User-Agent: curl/7.81.0
> Accept: */*
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 401 Unauthorized
< Content-Type: text/plain; charset=utf-8
* Authentication problem. Ignoring this.
< Www-Authenticate: Basic realm="juju"
< X-Content-Type-Options: nosniff
< Date: Fri, 02 Sep 2022 14:36:30 GMT
< Content-Length: 49
<
authentication failed: "prom" is not a valid tag
* Connection #0 to host juju-apiserver left intact

Try user-prometheus as the username. No idea why Juju needs this user- prefix.

Thanks @barrettj12, this works.
curl https://juju-apiserver:17070/introspection/metrics -u user-prometheus:prom --cacert /tmp/juju-cert.pem

Now I can try adding an integration test.

Without insecure_skip_verify: true I am getting
"lastError": "Get \"https://<IP_ADDRESS>:17070/introspection/metrics\": x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs"

@barrettj12 would you be able to share how to generated the file for tls_config.ca_file?

I am using the certificate stored in my JUJU_DATA directory. For a standard Juju installation, this should default to ~/.local/share/juju. So something like
~/.local/share/juju/lxd/client.crt

(assuming you are using LXD).


Alchemistry

Btw, if you are on discord I can help you with setting up git so you can create larger commits at once (I think you currently only use the GH web user interfaces?)

Nah I have git  installed. I’m been doing most smaller stuff on mobile and the first commit was done on my desktop client via my GPG Key

I’ll close this and squash it all tomorrow

Well close it after I finish

#275


Write connection log entry directly to output stream [run-systemtest]

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

We need to fix the timing sensitive access log tests first. Some test assumes entries are immediately available (which is no longer the case after fixing buffering).

We need to fix the timing sensitive access log tests first. Some test assumes entries are immediately available (which is no longer the case after fixing buffering).


chore: introduce release script

This commit automates our release process. It takes care of a couple of things:

Bumps version number in package.json as needed, see below
Generates changelog based on commit history
Create release commit
Tags release commit
Pushes release commit including tags to upstream repository
Publishes release on npm

There are a couple of options supported. The base command is run like this:
npm run release

This will do a minor bump and try to push to origin on master. However,
this can be altered with the following options.
npm run release -- --dry-run

Can be used to perform dry run and not actually committing, tagging, pushing,
publishing anything.
npm run release -- --release-as <something>

Something can be minor, major, patch or anything you want foo, 1.0.0 etc.
npm run release -- --prerelease alpha

Will create a prerelease version a la 4.0.0-alpha.x.
npm run release -- --sign

Signs the release commit (you need to have PGP setup for that).
npm run release -- --repo-origin pascal --repo-branch foo/bar

Pushes the release commit into pascal/foo/bar.

npm run release
This will do a minor bump and try to push to origin on master. However,

You mean that it will look at commit history and do the relevant bump correct?

I've rebased this on top of #1084 so we can test this. Seems to work fine. I'll update this PR, once the final comments have been addressed in #1084

This PR was rebased again #1084, but should also be rebased and tested against #1090 and/or #1098.


Only part of nodes have label, how to construct my input?

❓ Questions & Help
Hi, Sorry to bother you with this question. In my train and validation datasets, only part of nodes have label, how can I construct the input y when I use the model GCN or GAT?

I suggest holding a mask for each graph which holds information whether a label is present for a node. You can then compute the loss via
out = model(...)
loss = F.nll_loss(out[data.y_mask], data.y)

Thanks for your reply, it works, and thanks for your great work!


[CSL-1081] Refactor Pos.Block

This PR brings a new portion of refactoring. The task is not finished yet, but it's getting there. Again, I don't want to diverge too much, hence I created this PR.
Notable changes:
• moved more core stuff into core;
• made smart constructors for block/header more consistent with other code;
• split Pos.Block.Logic into multiple modules;
• made some constraints in Pos.Block.Logic less strict;
• introduced MonadDBPure and MonadBlockDBGeneric.
Addition of MonadDBPure and MonadBlockDBGeneric is the most notable change. You can read rationale behind these classes in Pos.DB.Class. The main reason I did it was that soon we will want to test some functionality from Pos.Block which uses MonadDB a lot and we can't use MonadDB in pure tests (which are our current goal).
I made some experiments and that's the result. It's not ideal, but I think it's the right direction.
For example, Pos.Block.Logic.Header doesn't use MonadDB at all as a result.
Addition of MonadBlockDBGeneric should also be useful for @neongreen to be able to get block/header from some block component without knowledge of type of block/header.

Travis failed more than 10 times in a row (two different travises together) with either OOM or hanging tests. I would like to stop monitoring this page constantly and restarting build every hour, so I am merging it.


Register deepseek model

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily receiving feedbacks. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Register deepseek model
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit tests to ensure the correctness.
If the modification has a dependency on downstream projects of a newer version, this PR should be tested with all supported versions of downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

之前已经有一个PR了，合入到了rope-linear-scale分支了。


Auth: Fix bug on app creds caching

Pull Request Test Coverage Report for Build 79830

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+1.4%) to 81.222%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/OAuthPrompt.cs
1
56.41%

/libraries/Microsoft.Bot.Builder.Azure/CosmosDbStorageOptions.cs
2
50.0%

Totals

Change from base Build 79619:
1.4%

Covered Lines:
3603

Relevant Lines:
4436

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.3.1


Unicode module can't be load

What did you expect to happen?
It loads and works.
What actually happened?
When I've uncommented :ui unicode and after doom sync -u emacs fails to starts.
Describe your attempts to resolve the issue
No response
Steps to reproduce

Uncomment :ui unicode
run doom sync -u
restart emacs
it fails with error: Error (doom-init-ui-hook): Error running hook "+unicode-init-fonts-h" because: (void-variable ...)

System Information
https://pastebin.com/VfkXctqH

:warning: This issue was closed and marked for deletion for the checked reasons below:

[X] Issue cannot be acted on or investigated further because:

[X] Could not be reproduced in vanilla Doom on any of our test environments.
[X] Not enough information to act on.
[X] Vital information was omitted or inaccessible. (A backtrace)
[ ] Explanations are too vague or issue is too open ended.
[ ] It's unclear what you are trying to say.

[X] The following possibilities are more likely explanations and haven't been ruled out:

[X] A pilot error.
[X] Private configuration.
[ ] A third-party package is behaving correctly, but in a manner you're not expecting.
[ ] A corrupt or broken Emacs installation.
[ ] Your system environment (hardware issues, the OS, shell environment, missing system dependencies, etc).

This ruling is not absolute and can be reversed if you follow up with enough information to further investigate this issue. Our How to Debug Issues guide can help you find out more about it (note: our discourse currently requires an account).
If you still feel lost after reading our debugging guide, raise your issue on our Discord or Discourse -- there may be others who have experienced it. Otherwise, this issue will be automatically deleted after 14 days.

I apologize if this is inconvenient or you feel lost, but it takes a lot of time to review issues by myself. The complexity and extensibility of Emacs tends to produce a lot of false positive or open ended bug reports, so I've restricted our issue tracker to issues that are actionable, immediately reproducible in vanilla Doom, or can be investigated in a reasonable amount of time.


Created SETUP.md file

Adding setup instructions to help people to set up development environment on local machines!!

Add gifs to this to make it interesting

Add gifs to this to make it interesting

okay !!


Improvements/fixes for WASM builds

No reason, I didn't realize 3.1.1 wasn't the latest while doing this whole
thing :)
On Wed, 11 May 2022, 09:47 Eugene Kliuchnikov, @.***>
wrote:

@.**** commented on this pull request.
In .github/workflows/build_test.yml
https://github.com/libjxl/libjxl/pull/1411#discussion_r869978599:

   BUILD_TARGET: wasm32

 EM_VERSION: 3.1.1

Why lower EM version?
—
Reply to this email directly, view it on GitHub
https://github.com/libjxl/libjxl/pull/1411#pullrequestreview-968834432,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOPAIZCAD7C67Q4TSHVHBTVJNQZZANCNFSM5VR6IZXA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix httplib2 version in changelog

What does this PR do?
Fix changelog httplib2 version 0.18.0 to 0.18.1
See #6702
Motivation
Additional Notes
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Note: httplib2 has been since removed in https://github.com/DataDog/integrations-core/pull/7247


Add PyQt6

Please add the following dependency to the rosdep database.
Package name:
PyQt6
Package Upstream Source:
PyPI
Purpose of using this:
For building GUI applications within the ROS 2 ecosystem.

When a pip package is also available from platform package managers, the preference should be to add that key.  This allows for downstream binary-packaged ROS packages to depend on them.
In this case, pyqt6 is available here: https://packages.ubuntu.com/noble/pyqt6-dev

Thanks for feedback on this @mjcarroll, I have added this to my task list for tomorrow and will push the requested change then.

I am just realising that the package release for the bindings for PyQt6 only supports the latest operating systems (I am working on Jammy). I'll add these here but I guess I'll need to continue to pip install for my application.

I see there are a number of packages released for pyqt (python bindings, core library etc.) and I also saw for previous versions of pyqt the python.yaml has a number of different package sources listed.
I haven't gone through these and updated pyqt6 mostly due to time constraints on my side. The above is a basic draft for Ubuntu and Fedora, note I didn't add python3-pyqt6 as this seems to be a dependency of pyqt6-dev-tools so I believe apt should resolve this dependency.
If I find the time and am in the process of cleaning up package dependencies for my ROS packages I will look to formalize the above some more.

Thanks for feedback, next time I submit one of these I'll be sure to take into consideration any of the points raised in this pr.


Updated installation requirements

matplotlib>=3.0.0

Coverage remained the same at 98.007% when pulling 132305f49787511879c61e2fcfa65de3e803b953 on dev_1.0.1 into 2204bb63e6502343f9f238ecd0391f49d238245b on master.


ESP32 stucks on "HomeKit: Configuring mDNS"

I am trying to run the "EspHapLed" example with my ESP32 device. But when i upload the code the logs are here:

Connecting to Superbox_WiFi_2.4GHz_98E3
.........
WiFi connected
IP address:
<IP_ADDRESS>
init_hap_storageReaded bytes ->1409
HomeKit: init_storage_ex size 0x581
Home Integration: hap_services added chararacteristic  0: 00000023-0000-1000-8000-0026BB765291
Home Integration: hap_services added chararacteristic  1: 00000025-0000-1000-8000-0026BB765291
Home Integration: homekit_is_paired 0
HomeKit: Starting server
HomeKit: Using existing accessory ID: FC:0C:53:BD:2E:D1
HomeKit: Configuring mDNS

And it stucks on there. I debugged the server.c code and i understood that, in this line server.c:3380 the 'triggered_nfds' variable is returning 0 value. So the for loop is going to infinity loop.
I use ESPHap 1.1 version. With the esp8266 its completely working.

Hi, I do not see any stucks on your logs. ESP is running and waiting for pairing.
Regarding server.c:3380 it's up to design , this is infinity loop (when server run) for incoming TCP connection.
triggered_nfds will be not zero, when some connection come

Hi, I do not see any stucks on your logs. ESP is running and waiting for pairing. Regarding server.c:3380 it's up to design , this is infinity loop (when server run) for incoming TCP connection. triggered_nfds will be not zero, when some connection come

thank you so much, i didnt think to look at homekit for add the device. I just thought this is a bug. Thank you again for this awesome library, have a good day.


Add package nim_seq

why not dna_seq? this is name is half redundant, half misleading.

So whats wrong with the travis status report?

It's not my package so I have no idea, but I would agree that its a perfect name, but dna_seq also would not fit since we plan to implement a lot more bioinformatics related file formats which do not have anything todo with dna.
But anyways there was a way to define a different name for the nimble package, and not use the git one, wasnt there?

But anyways there was a way to define a different name for the nimble package, and not use the git one, wasnt there?

the name of the package is the name of nimble file.

I will make the changes and make a new pull request


Unable to build: use of undelcared type 'ObserverOf'

Hi!
I'm getting this build error "Use of undeclared type 'ObserverOf'" on Request extension in all rx_ methods, e.g.:
Request.swift
line 26: return create { (observer: ObserverOf<NSData>) -> Disposable in
Currenlty I installed Alamofire v2.0.1 and RxSwift 2.0.0-beta via cocoapods v 0.39.0
How could I fix this error?

Hi @m-revetria,
RxSwift 2.0.0-beta requires Alamofire 3.0+ to work.
If you need to use 2.0.1 with RxSwift 2.0.0-beta you need to change (observer: ObserverOf<NSData>) -> Disposable in to observer -> Disposable in.

Hi @m-revetria,
do you still need help?


Bootstrap main branch development

Which issue is resolved by this Pull Request:
Resolves #76
Description of your changes:

Created main repo README. Open to suggestions for improving content on this
Made changes to README under docs/deployment
Added documentation and kustomization for vanilla deployment under docs/deployment/vanilla and made DLC based jupyter notebooks as default
Moved storage options under add-ons to clarify they can be used with any deployment
Disabled istio sidecar injection for secrets mount pod (ref: #83)
Refractored components, overlays, readmes and tests related to aws modified components according to the following directory structure:

├── awsconfigs
│   ├── apps
│   │   ├── jupyter-web-app
│   │   ├── katib-external-db-with-kubeflow
│   │   └── pipeline
│   ├── common
│   │   ├── aws-alb-ingress-controller
│   │   ├── aws-istio-envoy-filter
│   │   ├── aws-secrets-manager
│   │   └── istio-ingress
│   └── infra_configs
├── docs
│   └── deployment
│       ├── add-ons
│       ├── cognito
│       ├── cognito-rds-s3
│       ├── rds-s3
│       └── vanilla
├── tests
│   └── e2e
│       ├── __pycache__
│       ├── fixtures
│       ├── resources
│       ├── tests
│       └── utils

Added issue and PR templates

Testing:
Tested with Kubeflow-v1.4.1

[x] e2e tests: cognito, efs, fsx, sanity
[ ] WIP: RDS-S3 e2e test is failing with https://github.com/awslabs/kubeflow-manifests/issues/69#issuecomment-1030850754
[ ] Add code in e2e tests to clone upstream

Pending

Add unit tests
Add canary scripts

Since this is a fairly large PR, please help with reviewing sections(docs, manifests and related tests). We will do a bugbash later for further validation.
@rrrkharse: RDS and S3
@ryansteakley: Cognito
@akartsky: Vanilla
@mbaijal: Storage

Great work, is the KFServing doc to setup with API Gateway missing or will it be added in another PR?

@AlexandreBrown It will be a separate PR

Thanks for all the reviews

This is good work @surajkota and team


Zperf tcp download stalls with window size becoming 0 on Zephyr side

Describe the bug
Zperf tcp download stalls with window size becoming 0 on Zephyr side
Please also mention any information which could help others to understand
the problem you're facing:

Tested on qemu-x86 and esp32
Verified the packets using tcpdump. Figured out that the window size on Zephyr becomes 0.

To Reproduce
Steps to reproduce the behavior:

~/.local/bin/west build -b qemu_x86 -s samples/net/zperf -- -DOVERLAY_CONFIG=overlay-e1000.conf
Testing:
Zephyr    -> zperf tcp download 5001
Linux/mac -> iperf -l 1K -V -c <IP_ADDRESS> -p 5001
Check packets using tcpdump/wireshark. Verify that the window size is reported as 0 from Zephyr.

Expected behavior
Window size should be increased as application gets a recv_cb.
Impact
Zperf tcp download run stalls.
Logs and console output
NA.
Environment (please complete the following information):

Tested with client running on both Linux and Mac.

Additional context
N/A

I came across this bug recently on the mainline.
I have a patch here:
https://github.com/zephyrproject-rtos/zephyr/compare/main...mohankumarkumar:fix_zperf_tcp?expand=1
Please take a look. Thanks!

This is handled in 43379.