Unable to check axios calls on vitest "0.15.0"

Describe the bug
Hello,
I'm a beginner with vitest, I hope I did not make a mistake.
I try to test my vuex store on my vuejs project. It works perfectly for getters and mutations but fore my actions I have an issues to check if axios is call or not.
this is my tag.js file to test:
const actions = {
  async fetchTags({ commit }) {
    try {
      const response = await axios.get(
        CONST_CONFIG.VUE_APP_URLAPI + "tag?OrderBy=id&Skip=0&Take=100"
      );

      commit("setTags", response.data);
    } catch (error) {
      console.log(error);
      return;
    }
  },
};

And there this is my code  for test:
import tag from "../../../../src/store/apiObjects/resources/tag.js";
import { expect } from "chai";
import { vi } from "vitest";
import axios from "axios";

vi.mock("axios", () => {
  return {
    default: {
      get: vi.fn(),
    },
  };
});

describe("tag", () => {
 test("actions - fetchTags", async () => {
    const users = [
      { id: 1, name: "John" },
      { id: 2, name: "Andrew" },
    ];
    axios.get.mockImplementation(() => Promise.resolve({ data: users }));
    axios.get.mockResolvedValueOnce(users);

    const commit = vi.fn();
    await tag.actions.fetchTags({ commit });

     expect(axios.get).toHaveBeenCalledTimes(1);
    expect(commit).toHaveBeenCalledTimes(1);
  });
});

and this is the mistake:
FAIL  tests/unit/store/apiObject/tag.spec.js > tag > actions - fetchTags
AssertionError: expected "spy" to be called 1 times
❯ tests/unit/store/apiObject/tag.spec.js:64:24
62|     await tag.actions.fetchTags({ commit });
63|
64|      expect(axios.get).toHaveBeenCalledTimes(1);
|                        ^
65|     expect(commit).toHaveBeenCalledTimes(1);
66|   });

Expected   "1"

Received   "0"

I guess the mock is not working
Thanks in advanced for your answer.
I allready check the issue https://github.com/vitest-dev/vitest/issues/1274
I think I'm not the only ones with this issus : https://stackoverflow.com/questions/72442750/axios-get-mockresolvedvalue-is-marked-as-problem-in-testfile-test-ts-vue-vite
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-nyks4u?file=test/tag.spec.js
System Info
OS Name	Microsoft Windows Server 2016 Standard
Version	10.0.14393 Build 14393
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	SV03487
System Manufacturer	VMware, Inc.
System Model	VMware Virtual Platform
System Type	x64-based PC

 "dependencies": {
    "@handsontable/vue": "12.1.0",
    "@okta/okta-vue": "3.1.0",
    "@progress/kendo-data-query": "1.6.0",
    "@progress/kendo-drawing": "1.16.3",
    "@progress/kendo-licensing": "1.2.2",
    "@progress/kendo-theme-default": "5.5.0",
    "@progress/kendo-vue-animation": "3.4.1",
    "@progress/kendo-vue-data-tools": "3.4.1",
    "@progress/kendo-vue-dateinputs": "3.4.1",
    "@progress/kendo-vue-dialogs": "3.4.1",
    "@progress/kendo-vue-dropdowns": "3.4.1",
    "@progress/kendo-vue-grid": "3.4.1",
    "@progress/kendo-vue-indicators": "3.4.1",
    "@progress/kendo-vue-inputs": "3.4.1",
    "@progress/kendo-vue-intl": "3.4.1",
    "@progress/kendo-vue-popup": "3.4.1",
    "axios": "0.26.1",
    "core-js": "3.6.5",
    "dayjs": "1.11.1",
    "file-saver": "2.0.5",
    "handsontable": "12.1.0",
    "jest-mock-axios": "^4.6.1",
    "masonry-layout": "4.2.2",
    "moment": "2.29.3",
    "vee-validate": "3.4.14",
    "vite-plugin-require": "1.0.0",
    "vue": "2.6.14",
    "vue-demi": "0.12.4",
    "vue-i18n": "8.27.0",
    "vue-masonry": "0.12.0",
    "vue-router": "3.2.0",
    "vuetify": "2.6.0",
    "vuex": "3.6.2"
  },

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Sorry I found the solution, it was my mistake I had to add config.js file inside vitest.cinfig.ts:
`import { config } from "@vue/test-utils";
import { defineConfig } from "vitest/config";
import { resolve } from "path";
var configApi = require("./public/config.js");
const { createVuePlugin } = require("vite-plugin-vue2");
const r = (p: string) => resolve(__dirname, p);
export default defineConfig({
test: {
globals: true,
environment: "jsdom",
},
define: {
CONST_CONFIG:  configApi,
},
plugins: [createVuePlugin()],
resolve: {
alias: {
"@": r("."),
"~": r("."),
},
// alias: {
//   "@": fileURLToPath(new URL("./src", import.meta.url)),
// },
},
});`


Why is the download so slow?

Download speed is 1 kb in korea

Download speed of what? This isn't a utility for downloading things.

If you are having issues downloading files from GitHub, please contact GitHub support.


How to set form-wide configuration per type

I am working on a project where the schema is not known ahead of time and whose properties can vary.  So far I'm just using "*" as the form definition because I don't know the schema properties.  Is there a way to specify a configuration based on the property type that will apply to all properties from the schema?
For example, say I want to configure all booleans to use radio buttons instead of a checkbox, along with some custom labels.  I see how to do this if I know the property name but I'd like to apply that to all boolean fields.
The only thought I had was inspecting the schema and generating the form definition programatically.  Is that the recommended approach or is there a way to do configuration based on the property type?

Hi @dwikle, you can change the default rules for form definition if you like, or rather add new ones.
It is the schemaFormProvider (and its corresponding service schemaForm)  that decides what a schema should have as "default" form definition.
It works like this:

First we match the type of the schema (i.e. object, string, number etc) against a map of types to arrays, you can see it defined here: https://github.com/Textalk/angular-schema-form/blob/development/src/services/schema-form.js#L232
Then we loop over the array and call each function in turn until one of them returns a form definition, then that's the one we use.

So for you to change that you just need to prepend functions (so they get called first) onto the right arrays in schemaFormProvider.defaults. You can use the function schemaFormProvider.stdFormObj to take care of most of the common things a form object needs. Check the code for the other types for inspiration.
Ex: String with maxLength larger than 32 should be a textarea
angular.module('myModule', ['sfSchema']).config(['schemaFormProvider','sfPathProvider', function(schemaFormProvider, sfPathProvider) {

  schemaFormProvider.prependRule('string', function(name, schema, options) {
    // Schema type is either a type or an array with null + a type (see JSON Schema docs)
    if (schema.type === 'string' || (Array.isArray(schema.type) && schema.type.indexOf('string') !== -1)) {
      var f = schemaFormProvide.stdFormObj(name, schema, options);
      f.key  = options.path;
      f.type = 'textarea';
      options.lookup[sfPathProvider.stringify(options.path)] = f;
      return f;
    }
  });

}]);

Answered, closing.


Improve way to enable Disquss

It would be great if we can set disqus-id from environment variable :)
s.src = 'https://test-apkdzgmqhj.disqus.com/embed.js';

https://github.com/TryGhost/Casper/blob/master/post.hbs#L87
and also if we could enable discuss from environment variable too rather than manually editing the code :).

You wouldn't be able to set it via an environmental variable since that line is frontend javascript; themes don't have access to any of the backend js 😉

Thnks @vikaspotluri123
may be we could try something as ghostium. changing in partials/custom/config.hbs file
https://github.com/oswaldoacauan/ghostium#configuring
Ex:
https://github.com/oswaldoacauan/ghostium/blob/master/partials/custom/config.hbs#L5

Hi @prashanthmadi
Thanks for the idea!
We only keep Github issues open for bugs and in-progress feature work. I'll add the idea to our internal ideas board. As soon as the feature gets requested often enough, we discuss and schedule the feature for an upcoming sprint.


Could you add the product part in the database again its not there

What part(s) of the documentation would you like to see updated?

Which Program are you part of?

[ ] DCP21
[ ] Any other

Additional information

N


Shape inconsistent error while using SoftmaxCrossEntropyLoss

Hi, I'm following this tutorial.  Running
L = gluon.loss.SoftmaxCrossEntropyLoss()
loss = L(output, labels)

results in the following exception:
mxnet.base.MXNetError: Shape inconsistent, Provided = [100,2], inferred shape=[100,1]

The shapes of the labels and output seem consistent:
labels.shape:  (100, 2)
output.shape:  (100, 2)

The model is defined as follows:
model = mx.gluon.nn.Sequential()
with model.name_scope():
    model.add(mx.gluon.rnn.LSTM(256, dropout=0.2, layout='NTC'))
    model.add(mx.gluon.rnn.LSTM(128, dropout=0.2, layout='NTC'))
    model.add(mx.gluon.nn.Dense(2, flatten=True))

Any clues on what I might be doing incorrectly here? Thanks!

Solved by following this


Pallets docs links broken

Links for pallet docs are broken at
https://substrate.dev/docs/en/conceptual/runtime/frame
https://www.substrate.io/kb/runtime/frame
e.g
https://substrate.dev/rustdocs/master/pallet_assets/index.html
https://substrate.dev/rustdocs/master/pallet_authority_discovery/index.html
https://substrate.dev/rustdocs/master/pallet_babe/index.html

cc @JoshOrndorff and @danforbes

Closing in favor of substrate-developer-hub/knowledgebase#41, which I have assigned to myself and will prioritize. Closing this issue in favor of that one. Thanks for the heads up, Shawn :+1:

@qalqi - the changes have been merged in...thank you!


Implement TLS on authenticator server and client SDK

FWIW, here is the TLS config exposed by Vault. Not that we need to do it the same way, just as a reference for deciding what we want to do.

I've found a very helpful guide here: https://itnext.io/practical-guide-to-securing-grpc-connections-with-go-and-tls-part-1-f63058e9d6d1
Also, there are some of these elements located in an example config here.

I've assigned this to myself because in order to check whether the GRPC server is healthy, I'll need to implement this.


Add support for vagrant proxyconf plugin.

Make sure the openshift service is using the proxy environment configuration that is injected by the vagrant proxyconf plugin.

@iconoeugen Can you expand of what would this enable? As far as I know there's also some more configuration that would be required in master-config to properly support proxies, like adding a buildOverrides, so that builds will also use proxies.
If this is an important topic, we can think on adding the whole feature in, but this would be a build time setting (vagrant provisioning) and nothing that could be later changed. Similar to the IP.


chore(main): release 0.1.1

:robot: I have created a release beep boop
0.1.1 (2024-03-24)
Bug Fixes

use spacing between form title and description (2d91446)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/commonhorizoncommun/design-system/releases/tag/v0.1.1 :sunflower:


Is there a file size limit?

Hi,
just installed the app using docker-compose and synced a couple of devices.
It seems that some files are missing. Probably because there is a file size limit. For example, I had a zip file in the root with 1.4Gb size and it wasn't synced at all. Size 0KB
Is this configurable ?

Hi, just installed the app using docker-compose and synced a couple of devices. It seems that some files are missing. Probably because there is a file size limit. For example, I had a zip file in the root with 1.4Gb size and it wasn't synced at all. Size 0KB
Is this configurable ?

The plug-in does not limit the size of synchronized files, but the backend limits uploaded files to no more than 10GB. If reverse proxy software such as nginx is used, the size of uploaded files may be limited by these software.


TreeSand load improvement

This PR contains:

Release of TreeSitter documentation
Correction of Node#pretty_print signatures (sorbet)
A change in the default printing device, of TreeStand::Utils::Printer from a StringIO created each time we call pretty_print, to something fixed in the printer class, and configurable as well, through TreeStand.config.io.
Add some sane defaults to load parsers automagically if no config is provided.

@DerekStride I did these changes while working with TreeStand, and I acknowledge the fact they could be broken into different PRs, but I just did them in a single one for convenience.
I would love to have your feedback, as I did some things on the spot and I might be missing something.

I redid the commits since they were very rough and incoherent.


Create Scroll UX improvements

There's a create scroll button at the end of the md editor:

Suggestion: clicking this would put the focus to the PREVIEW md renderer and another "CREATE SCROLL" button. Motivation: this let's the user read the preview and check if everything is ok.
The No results, Clear filters and See all realms components should not be at the bottom of the previewer

Yes great idea, all for it

Yes, I spotted it as well but was focusing on Revisions. If you fix it - that would be perfect!

I did not implement an inbetween button directly under the editor. This because hovering off the button causes a state refresh and it pulls in all data from graphql


Add index uniqueness for several relations

including:

hasOne
belongsTo (inversed to hasOne)
morphedHasOne
belongsToMorphed (inversed to morphedHasOne)

refers to cycle/schema-builder#5 and spiral/framework#250


packages.v2

Codecov Report

Merging #126 (60e7b53) into main (45c52e1) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #126      +/-   ##
==========================================
+ Coverage   94.13%   94.18%   +0.05%
==========================================
  Files          14       15       +1
  Lines        5674     5723      +49
==========================================
+ Hits         5341     5390      +49
  Misses        255      255
  Partials       78       78

Impacted Files
Coverage Δ

packages/imp.go
100.00% <100.00%> (ø)

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 45c52e1...60e7b53. Read the comment docs.


babel-standalone: ReferenceError: exports is not defined

Although Plotly React works properly in the browser with babel-standalone, React-pivottable throws
ReferenceError: exports is not defined:

Repro:
<!DOCTYPE html>

        <title>Plotly/React/PivotTables in browser compilation</title>

I'm not that familiar with babel-standalone, and this project's distribution system wasn't really designed with it in mind but from a glance at their documentation, it seems like you need to add type="text/babel" and possibly a data-presets attribute to the script tags you want babel-standalone to process...

the above already sets the type "text/babel" and babel-standalone is already doing its thing.
Problem is PivotTableUI doesn't load properly.
If you try the above code as is from any browser, you will see Plotly working fine but an exception from PivotTableUI.
Since the react-plotly component works with babel standalone, I was expecting the same for PivotTable.


sharing datasets for development

@chenlingantelope has an interesting dataset in which the batch mixing problem isn't solved. It might be interesting for @maxime1310 and I to investigate new harmonizing methods on that instance.
I had a piece of code I wondered if I could include it a a GeneExpressionDataset method:
    def export(self, filename):
        col_attrs = {"BatchID": self.batch_indices, "ClusterID": self.labels}
        row_attrs = dict()
        file_attrs = dict()
        if hasattr(self, "gene_names"):
            row_attrs["Gene"] = self.gene_names
        if hasattr(self, "cell_types"):
            file_attrs["CellTypes"] = self.cell_types
        loompy.create("data/" + filename, self.X.T, row_attrs, col_attrs, file_attrs=file_attrs)

That might be convenient for exchanging datasets in the .loom format.

This might especially be useful as long as there is preprocessing to the "harmonization" task (and not simply the concatenation of already existing datasets). For instance for my latest PBMCs experiments I labelled cell types from cite seq according to epitopes level, and in particular the CD4 label I extracted had a much lower level of granularity that on purified populations where subcell types were also identified. So I merge the CD4 labels on the purified samples, and only kept the cell types appearing in both datasets, which gives me a convenient subsampled version of a dataset with batch and labels preannotation on which we know harmonization should work.

I don't think anything in GeneExpressionDataset should be specific to loom. What about just pickling the dataset object and sharing it with each other that way?

If Chenling has a good dataset for testing, could we post it (in loom format, or in whatever format) at https://github.com/YosefLab/scVI-data
That's the kind of thing @imyiningliu might work on for issue #78

Let's use pickle serialization for now.


How to use Plan Variables?

In the example project b, the build.gradle.kts has:
    planVariables = mapOf("example" to "ciao")

However I can't see this being used in the project-b-1.tf. Is it supposed to be?
So the simpler question is, how do I use planVariables once I declare them? :-)

I understand now that these are used as the default value for variables you declare in your *.tf files.
Perhaps the example should include something to make that obvious like:
build.gradle.kts:
planVariables = mapOf("myExampleVar" to "ciao")
Main.tf:
variable "myExampleVar" {}

Indeed, the variables are passed using command line. I will update the examples.


Create Dockerfile for container build

Tbd:

Do we build FROM https://github.com/cloudnative-pg/postgres-containers or fork it?
Do we build pgvecto.rs in a builder stage, or beforehand (outside of docker) in github actions?

The Dockerfile should probably take the postgres/pgvecto.rs/etc version as build args.

See https://github.com/tensorchord/pgvecto.rs/blob/main/docs/installation.md for pgvecto.rs build instructions.


Error to add in Add-on Store

Ok... I really don't know what's happening, but:
https://user-images.githubusercontent.com/29582865/148108183-7fa2533d-0fdf-493b-a3c0-d90bc0200a02.mp4
Am I missing something? Looking forward to use your add-on. Thank you!

I'm having the same issue

Thanks for raising the issue. This repository is the specific development repository for the add-on. There is a separate repository, which is formatted as a proper HomeAssistant Add-On Repository, which is including this add-on (and potentially others in the future). Please use this:
https://github.com/brenner-tobias/ha-addons
I acknowledge that this is pretty confusing and will think about a simpler solution.
Please open again if this does not help you.

A simple way to fix is to perhaps add a note about it in the README of this repo.
Thank you for pointing me at the right direction!


Warning: toRefs() expects a reactive object but received a plain one

Hi @wingkwong,
When using the Watermark component, I get the following warning

[!WARNING]
toRefs() expects a reactive object but received a plain one

I created a reproducible example here: https://playcode.io/1760402
I am not 100% sure, but my best guess is that it is caused by one of these two lines:
https://github.com/watermarkify/vue-watermark/blob/93d770df9012222c74a7ef15d726208f15c1a82f/src/components/Watermark.ts#L41-L42
Another thought: I wonder if it would make more sense to use Vue's computed() functionality instead of toRefs().

Thanks for reporting. I can reproduce in playground also. Will take a look.


Spaces after commas in RGB HSL etc.

Can you please add a config option to add spaces after commas in color formats which use them?  Some lint styles prefer spaces after commas.

There is, already!
**Abbreviate Color Values**: If possible, abbreviate color values, like for example “0.3” to “.3”, “#ffffff” to “#fff” and “rgb(0, 0, 0)” to “rgb(0,0,0)”.

If this is not what you wanted, please let me know.

I see.  I would not consider the comma space/no space as an "abbreviation".  I would consider the first two abbreviations but the last a code style.
The default settings for stylelint and scss-lint expect the other abbreviations (e.g. ".3") but not the lack of spaces. So, If I un-tick "use abbreviations" the other will be flagged as errors.


Allow for custom relative output path in .refitter

This change allows for a relative output path to be specified in the .refitter config files similar to the --output option available in the CLI tool.
Example:

{
  "openApiPath": "../Resources/V3/SwaggerPetstore.json",
  "namespace": "Refitter.Tests.CustomGenerated",
  "output": "../CustomGenerated"
}

@All-contributors please add @Noblix for code

@Noblix actually, let's just get this in and I'll fix the minor details myself

This contribution is now released in v0.8.1


🐛 Pagination doesn't get the correct page when use routing after relodad

🐛 Current behavior
After navigate with the pagination, for example to the page 2, and reload the page the pagination will show the page 1  instead of page 2 that is the truly page that is requested (when use routing with Next)
🔍 Steps to reproduce

In the index click in "Go to the brand Samsung"
Click in the page 2 https://hnivvj-3000.csb.app/brands/samsung?instant_search[page]=2
Refresh the page
You will see the page 1 as active but the URL show the page two as active

Live reproduction
https://codesandbox.io/p/sandbox/algolia-next-static-get-server-state-bug-hnivvj
💭 Expected behavior
When a url contains the active page, this is the one that should be displayed
Package version
eact-instantsearch-hooks-web: 6.41.0
Operating system
macOS 13.3.1
Browser
Firefox 112.0.2
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hello @RodrigoTomeES!
Server side rendering on Next.js using createInstantSearchRouterNext() is not supported with getStaticProps().
In static mode, you can't retrieve the query parameters because pages are generated at build time, thus the serverUrl is not correct.
You can use getServerSideProps() instead as shown here: https://github.com/algolia/instantsearch/blob/master/examples/react-hooks/next/pages/index.tsx#L85-L99
Hope that's clear!

Hi @FabienMotte ,
Thanks for your quick response but I am not sure about that createInstanceSearchRoute is only compatible with SSR because we have working filters with this method, I can make a demo that you see it's working.
I think the expected behavior is the sever return the static search and in the client is checked the query params to load the correct page or filters if isn't the default.
Thanks

Hi @RodrigoTomeES,
Thanks for your message. It's great to hear that you've been able to use the createInstanceSearchRoute() function with filters even without SSR. However, I wanted to clarify that our routing system is based on query parameters, and getStaticProps() doesn't provide query parameters out of the box (https://github.com/vercel/next.js/discussions/17269). While it may be possible to work around this limitation in custom ways, we don't officially support such approaches. I updated our documentation to clarify the support of getStaticProps().
If you have any further questions or concerns, please don't hesitate to reach out.

Hi @FabienMotte ,
We don't have customice nothing, with filters just work you can see it in the demo that I made. Look:
https://user-images.githubusercontent.com/13077343/236157531-5489b78e-f674-4e77-9886-31627d4aeac7.mov
Maybe this behavior is a bug but for every one that use routing with SSG is a great feature! Because we have the server state that return the default state an algolia read the parameters an load the current filters requested. Even more in dev mode Next JS is load in SSR so in codesandbox the pagination should be work so I still think that it is an error that the pagination does not work correctly.
Thanks

@FabienMotte could you review it?

@RodrigoTomeES Hey, I found this issue, but it's closed.
Did you find a workaround? I'm experiencing the same; after reloading, the refinements (filters) are kept selected and show up in the URL but it doesn't work for the pagination; it gets lost after reloading.

@RodrigoTomeES Hey, I found this issue, but it's closed. Did you find a workaround? I'm experiencing the same; after reloading, the refinements (filters) are kept selected and show up in the URL but it doesn't work for the pagination; it gets lost after reloading.

No sorry 😔


Improve e2e test fixture objects

Changes made by this Pull Request

Use objects for fixtures and not the json files

#119 has to be merged first (sorry for not squashing)

"Fix/e2e-tests": Have they not worked beforehand? 🙈 😅

"Fix/e2e-tests": Have they not worked beforehand? 🙈 😅

Haha, the new title is way better :D

Codecov Report

Merging #132 (d94fb65) into dev (0fa8f2c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #132   +/-   ##
=======================================
  Coverage   93.38%   93.38%
=======================================
  Files          20       20
  Lines         423      423
=======================================
  Hits          395      395
  Misses         28       28

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 0fa8f2c...d94fb65. Read the comment docs.


Demo walkthrough

Issue #, if available:
Description of changes:
Based off #124.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Since this branch consists of information related to features that have not been merged in (like SMS, Shopper select), please make sure to get James to review them and merged only after the other changes are merged.

Closing as this was merged as part of #142.


error in one Hook.Fire() prevents subsequent hooks from firing

The loop in LevelHooks.Fire() is interrupted when there is an error, which is undesirable in our use case. This is different behavior from the doc comment:

// Fire all the hooks for the passed level.

Our workaround is to LevelHooks.Add() the hooks in order of increasing likelihood of an error so that the loop will not terminate prematurely.
We think it is preferable to allow all of the hooks in LevelHooks to attempt to fire. This can be accomplished by using go-multierror to capture errors as they arise, and then return the collective error after the loop has fired all the hooks for a log level. I'm happy to submit a PR if this seems like a desirable change.
Thanks!

Great issue. I don't think we need a full import of multierror. Something simpler should be OK.

up


Sounds fantastic @julieqiu and it's really awesome how much the feedback is being taken into account on this.

Sounds fantastic @julieqiu and it's really awesome how much the feedback is being taken into account on this.
A suggestion I have on the redirect is to do it a little like Go Modules: first opt-in, then opt-out, then full switchover.  Right now you have the ability to opt-in to always redirect using a cookie, so for the next stage you could redirect unless a specific cookie is set.
I think this would be a very gentle way of going about it, and might spark a final round of useful feedback as the whole community adapts to the change (while still being able to browse the legacy version).
If the percentage of traffic opting-in to the redirect is very high, this suggestion may be unnecessary, but I wanted to throw it out there.
Originally posted by @tooolbox in https://github.com/golang/go/issues/39144#issuecomment-632486887

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


Redo A&S 100 and 120 Credit Minimum Requirements

Summary

[x] Creates 120 Total Credit requirement for A&S and write checker to exclude courses that are not allowed.
[x] Excludes transfer (including AP) credits from counting for the required 100 credits from Arts and Sciences.

Please read the test plan before testing thanks!
The A&S Degree Requirements page links to a website with information about the credit requirement, including exclusions for 100 & 120 requirements:

The College of Arts and Sciences does not grant credit toward the degree for every course offered by the university. Courses in military training, service as a teaching assistant, physical education, remedial or developmental training, precalculus mathematics, supplemental science and mathematics, offered by the Learning Strategies Center and English as a second language are among those for which degree credit.

Courses that do not count toward the 100 required Arts and Sciences credits include credits earned in other colleges at Cornell (except in the cases specifically noted in this section), transfer credits earned in any subject at institutions other than Cornell, and advanced placement/test credits. AP/test credits count as part of the 120 credits required for the degree but not as part of the 100 Arts and Sciences credits and may not be applied to distribution requirements. AP credits are posted on the transcript. If, subsequently, a student takes the course out of which they had placed, the AP credit will be removed because of the overlap in content.

Test Plan

Check that all credits (except for courses numbered 1000 - 1099 and PE classes) count for the 120 Total requirements.
Ensure that AP credits are not counted towards the 100 A&S credits. Note that this PR was made before #684 was merged into master, so AP credits are disabled by default for every requirement. Therefore, you must make sure to run GK.enableAPIBFulfillment() in the console first, and it would be helpful to make sure that your AP credits still count for something they should (like AP Computer Science A for Computer Science major in A&S).
Ensure that only classes that count for the 120 Total Credits can count for the 100 A&S Credits. The 100 A&S Credits must come from the 120 Total Credits.

Notes

I don't currently include all the courses from the Courses That Don't Count website.
I'm not sure about the wording for the descriptions.
I'd like to link to the Courses That Don't Count website, but our source ("Learn More" link) usually goes to a more general page, not a page of exclusions.
I only added the 120 total credit requirement to the current A&S college. Do I also add it to pre 2020?

is this better suited by compound requirement? i think it's helpful for the user to see both the 100 and 120 but they do share a lot of courses


Add Pandas API notebook to Explanation for the docs

Is this a duplicate of  #163?

Resolved in another merge request addressing multiple linking issues with Explanation


Prediction using learned weights

I'm trying to transfer a neural network to an R package I wrote, but I can't figure out how to reproduce the predict function using the learned weights. The net1 layout is this:

n
name
size

0
input
23050

1
dropout1
23050 (p=0.85)

2
hidden
2500 (nonlinearity=very_leaky_rectify)

3
dropout2
2500 (p=0.5)

4
output
11525 (nonlinearity=None)

Here is what I tried:
W1 = net1.get_all_params_values()['hidden'][0]
W2 = net1.get_all_params_values()['output'][0]

# X is matrix I would like to get predictions for
z2 = np.dot(X, W1)
a2 = np.maximum(1./3*z2, z2)
z3 = np.dot(a2, W2)
yhat = z3

This gives me a result close to net1.predict(X) though slightly off. What am I missing? I suspect it has something to do with the vectors net1.get_all_params_values()['hidden'][1] and net1.get_all_params_values()['output'][1]?
Thank you for the AWESOME package!

I think I figured it out. I needed to add net1.get_all_params_values()['hidden'][1] to z2 and net1.get_all_params_values()['output'][1] to z3. Still not exactly sure what they are though.

Hi Alex, I'm glad you figured it out on your own. Those additional parameters are the "biases", search for "neural network weights biases" and you will find plenty of explanations.


Nothing Happened When Start Discovering (0 Device)

Hello everyone, When I press my button to scan nearly Bluetooth devices nothing happened

My code :
using Plugin.BLE;
using Plugin.BLE.Abstractions.Contracts;
using System;
using System.Collections.ObjectModel;
public partial class DashboardPage : ContentPage
{
IBluetoothLE ble;
IAdapter adapter;
public  ObservableCollection Devices { get; set; }
    public DashboardPage()
    {
        InitializeComponent();
        ble = CrossBluetoothLE.Current;
        adapter = CrossBluetoothLE.Current.Adapter;
        Devices = new ObservableCollection<IDevice>();
    }

    private async void SearcheBtn_Clicked(object sender, EventArgs e)
    {
        try
        {
            var state = ble.State;
            if (state == BluetoothState.On)
            {
                adapter.ScanTimeout = 30000;
                Devices.Clear();
                adapter.DeviceDiscovered += (s, a) =>
                {
                    Devices.Add(a.Device);
                };
                if (!ble.Adapter.IsScanning)
                    await adapter.StartScanningForDevicesAsync();
            }
            else
            {
                await Application.Current.MainPage.DisplayAlert("Attention", "Bluetooth is off", "Ok");
            }
        }
        catch (Exception ex)
        {
            await Application.Current.MainPage.DisplayAlert("Attention", "Error => "+ ex.Message, "Ok");
        }

    }
}

Android permissions:

Steps to reproduce

Search nearly devices

Connect to One specific device

Send Data (Text to print for ex)

Expected behavior
I should get get a list of devices
Actual behavior
Nothing happened
Crashlog
No crashes
Configuration
Version of the Plugin => 2.1.1
Platform: Android 10.0 API 29
Device: Xiaomi M2007J20CG

Hi @Boukri,
I'm the friendly issue checker.
It seems like (37.50 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message.
But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!

Android permissions:

I figured that i should turn on my device location , I don't' why working with bluetooth requires location

I figured that i should turn on my device location , I don't' why working with bluetooth requires location

Well, it's simply required on Android. There is nothing we can do about it.
Note that this is mentioned in the README. So I'll just close this issue.


[4.0.0] Missing config in Product REST APIs quick start documentation

Description:
Product REST APIs quick start consists of a postman collection.

Invalid URL for generate access token request
Missing URL in Add API.

https://apim.docs.wso2.com/en/latest/reference/product-apis/overview/
Affected Product Version:
APIM 4.0.0

@Mariangela Please check.

@YasasRangika , can you please provide your feedback in this regard, and share the details that needs to go into the doc.

Related to: https://github.com/wso2/product-apim/issues/12315

Related to
https://github.com/wso2/docs-apim/issues/5251

This will be fixed with https://github.com/wso2/product-apim/issues/12315


ci: test against LLVM 17

Bump the "bleeding edge" test to LLVM 17, the "stable latest releases" test to 16.

Does this seem ok?

So which clang versions will CI be exercising now?

Clang or LLVM?
With this test, I believe our CI will test against llvm (for JIT) with every major version from 9 to 17, inclusive. (That actually feels like unnecessarily many, maybe it's time to raise the minimum for future OSL 1.14+ releases?)
But our CI only builds with a few versions of clang: 9, 13, and 14 (on Linux), and 15 (on Mac). Most of our build matrix uses gcc, plus the icc & icx tests. It would be unwieldy to expand the CI tests to make every combination test against every compiler, so we kind of sample. Historically, we have rarely or never found much sensitivity to building against one or another version of clang, as long as they both support the same level of C++ standard.
The one exception is that sometimes newer versions monotonically add new warnings, so we should always be doing one build with the very latest clang to make sure we compile cleanly with no warnings. I'll amend this PR to make sure one build uses the latest clang 17 to ensure we have full coverage there.

Amended: Test clang 17 compilation with MacOS-13 build


[REQUEST]

could you please add the scrappey.com captcha service?

By skimming through their docs, I don't see any API that can solve captchas, only one tied to the browser service they provide. Feel free to prove me wrong if you find some docs for a captcha service.
https://wiki.scrappey.com/getting-started


Correction for raw affiliation Univ Lyon, ENS de Lyon, Univ Claude Bernard, CNRS UMR 5239, INSERM U20, Laboratory of Biology and Modelling of the Cell, 46 Allée d’Italie Site Jacques Monod, F-69007, Lyon, France

Correction needed for raw affiliation Univ Lyon, ENS de Lyon, Univ Claude Bernard, CNRS UMR 5239, INSERM U20, Laboratory of Biology and Modelling of the Cell, 46 Allée d’Italie Site Jacques Monod, F-69007, Lyon, France
raw_affiliation_name: Univ Lyon, ENS de Lyon, Univ Claude Bernard, CNRS UMR 5239, INSERM U20, Laboratory of Biology and Modelling of the Cell, 46 Allée d’Italie Site Jacques Monod, F-69007, Lyon, France
new_rors: 029brtt94;04zmssz18;02feahw73;02vjkv261;01bj4fd12
previous_rors: 029brtt94;04zmssz18;02feahw73;02vjkv261
works_examples: W2952344515
contact: 166e0017abe3c92250f618fb31cd8681:2dc4817300e2f8d65f84a6499851 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


add ws support

we add DefaultTransports https://github.com/StreamSpace/ss-ipfs-lite/blob/1fe527ad868f7221d82c3697ae3436cd7e43c61a/util.go#L34, which adds ws and tcp both


update n8n logo

The n8n logo was redesigned in 2022, and this PR updates the corresponding graphic files to align with the new design.

Thank you for your PR !


Pipeline updates

Problem
We need a way to perform post deployment activities.
Solution
Create a new tooling pipeline '/06-post-installation-tooling.yaml' to host tooling tasks.
Tests

Notes

Note:
curl -H Metadata:true --noproxy "" "http://<IP_ADDRESS>/metadata/instance?api-version=2021-02-01" | jq > . vm.json
must be
curl -H Metadata:true --noproxy "" "http://<IP_ADDRESS>/metadata/instance?api-version=2021-02-01" | jq . > vm.json


my fix for ?&

Despite the latest regex/query param change i'm still seeing issues with query parameters and stray &.  (referencing #442 and #445 )
Specifically, seeing GETs like this:
GET /RESOURCE?&guid=039467b3-d779-493c-91ec-7137395a9582
Note the ?&.
Upon inspection I expected your regex to catch this case, but wasn't able to adapt what you have.  I'm simply adding a .Replace("&?", "?") in the interim, and that's doing the trick for me.
I'm sure there's a cleaner fix to this, but I wanted to surface the issue to you nonetheless.
@kenal-microsoft  @amareshbAtMicrosoft

ah. I figured it out.
"\\?&*$|&*$|(\\?)&|(&)&+"; needs to be "\\?&*$|&*$|(\\?)&*|(&)&+";

star on & after the ?


Add direct register access I/O for AY-3-8910

The FCS80 supports 16-ports access to simplify the creation of new programs, while also supports 3-ports access for simplify the porting of programs with using legacy AY-3-8910 register access.

$A0~$A2: General AY-3-8910 register access port
$D0~$DF: Direct AY-3-8910 register access port

I'm going to change the implementation of example to direct access and merge it after testing.


Allow issuing challenges at the domain apex

Allow issuing a challenge when deSEC only hosts the _acme-challenge subdomain, rather than the full domain. This allows the rest of the DNS zone to be hosted elsewhere, reducing the potential impact if the server running Certbot were to be compromised.
Additionally, allow the .dedynauth file to be stored in the same directory as the hook script, for ease of use when running in a cron job or other automation where the current directory may not be easily accessible.

nice, this looks good to me. Thanks for the contribution!

Any chance you could label this PR with the hacktoberfest-accepted tag so it counts toward Hacktoberfest for me?

I labelled repo and PR to my best understanding of hacktoberfest, please let me know if you need other/further action. Thanks again!

That's all I needed - thanks for the quick review!


provide backgroundImage option

In my current terminal app that I am using I have custom image as background. I'd like to use Hyperterm and I want to have custom background here as well.
After this change, you will be able to add custom background  in configuration:
module.exports = {
   backgroundImage: 'url(file://path-to-file)',
};

Probably best done with CSS? Since electron doesn't support this natively.

Makes sense, I will try.
But anyway it is necessary to set hterm background as transparent, because it is in iframe and cannot be styled.

Try use termCSS?
On Tue, Aug 9, 2016 at 8:42 AM Boris Serdiuk<EMAIL_ADDRESS>wrote:

Makes sense, I will try.
But anyway it is necessary to set hterm background as transparent, because
it is in iframe and cannot be styled.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zeit/hyperterm/pull/585#issuecomment-238477797, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAC5s9LPTtvmjUu4Nx6Wt0UoYdYViSWgks5qeC9TgaJpZM4JeevO
.

--
James Hall
Director
Parallax Agency Ltd
M.<PHONE_NUMBER>0

Well, I could make my styling with the following CSS.
module.exports = {
    css: `
       .terms_terms {
         background: url(file://path-to-file) center;
         background-size: cover;
       }
    `,

    termCSS: `
      x-screen {
        background: transparent !important;
      }
    `
};

Thanks everybody for help!

But the thing is that hterm uses inline styles to set background, so I have to use !important to override it.
So I changed my pull request, now it makes iframe with hterm transparent. I think it's better anyway, because now you don't need to set background color twice, it's enough to set it for body at main document.
@rauchg what do you think about it?

I have another PR which does this, so I'm closing it.

Thank you!

For future reference, this will be done in #524


Make external modules of type 'this' work with module concatenation

Fixes #11724.
Changes how the object lookup is wrapped in an IIFE to avoid hiding the left side of the assignment inside a function.
When concatenating modules, the module exports are assigned to a local variable, not to module.exports. Therefore, the generated code of the module is:
(function() { const lodash_namespace = this['lodash']; })();

But because the local variable is scoped inside the function, it's not visible outside it and can't be used by other modules.
If the assignment is to module.export, wrapping inside a function doesn't do any harm, that's why it always worked before external modules concatenation started to be supported.
After this patch, the IIFE wraps only the object lookup:
const lodash_namespace = (function() { return this['lodash']; })();

The second change is that the external module of type this is forced to be in non-strict mode .That's the only mode where the this lookup has any meaningful behavior, accessing the global object. In strict mode the default this is undefined and the external lookup never works.

Added a test case confirming that importing the this external really works. Modeled after a similar test for the global external type in the externals/global directory.
I confirmed that, in the TDD spirit, the test failed before the fix and starts to pass after the fix is applied.


UT checking calls to OS_printf

Is your feature request related to a problem? Please describe.
Many unit tests are checking the calls to OS_printf().  But typically all syslog/printf type messages are not fulfilling any sort of requirements, they are just informational in nature.
So AFAIK there isn't really a strong justification to specifically check for certain syslog messages, but the fact that the UT does check for these means that any time the syslog messages are changed or refactored in any way, one gets a bunch of nuisance UT failures.  As a result we spend a lot of time fixing UT tests for things that aren't really relevant to the operation of the code.
Describe the solution you'd like
At least remove checks for number of times OS_printf() was called in a given path.  This is really quite irrelevant to pass/fail.
The UT_PrintfIsInHistory tests might be OK to keep, but an actual return code should be preferred.  If there is no return code then this is probably OK - its also less volatile because it just checks format string and confirms that a specific path was taken.
Requester Info
Joseph Hickey, Vantage Systems, Inc.

Agreed!


How to convert Google Colab notebook into python modular programming as individual file scripts

Hi Folks, greetings of the day to y'all.
I have successfully tried to run the code in the notebook with adding few other functionality to it  and it works fantastic on colab.
However, now I want this to run on my local machine with VScode IDE as modules. Please guide me through this. It would be deeply appreciated.

Can you please share the code?

Hi @AGRocky, I have problems with running on the local host too, maybe we can help each other. Where are you get stuck?

@Quanult Hi thanks for the reply. I am able to run it on google colab but no idea how to integrate it as modular structure in VScode

@AGRocky yes, i know it, but you have to tell me what is your problem is so I can discuss with you about that. The setup, installation or something? :D

for the installation of packages it doesn't take the versions

try following this issue 166


No Documentation for $NewPolicy or $UpdatedPolicy

Hi
The DLP commands New-DLPPolicy and Set-DLPPolicy have parameters $NewPolicy and $UpdatedPolicy respectively which define the new DLPPolicy or the Updated DLPPolicy is..  But I cannot find any examples of what a $NewPolcy Object or an $UpdatedPolicy look like..
Thanks
Nigel

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

ID: 02f1be79-2b3a-31da-7a7d-ace1eac5d1f1
Version Independent ID: fa7c7450-15a6-edc8-5671-f45763267ca6
Content: PowerShell support (preview) - Power Platform
Content Source: power-platform/admin/powerapps-powershell.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@NPrice99
We've recently published the following. Check to see if it provides what you're looking for.
https://docs.microsoft.com/en-us/powershell/module/microsoft.powerapps.administration.powershell/?view=pa-ps-latest


[KeyVault-Keys] Eslint should be good now

Good, up to date eslint on Key Vault Keys.
Fixes #7147

/azp run js - keyvault - ci

Once #8478 is approved & merged with the pipeline fix we should be good here.


Miscellaneous: Sparse Table (Min, Max, And, Or, Gcd, Lcm)

Description
This Sparse Table efficiently performs range queries like Min, Max, GCD, LCM, AND, and OR based on the provided string parameter. It preprocesses the input array for faster query responses, making it ideal for static datasets.
Complexity

Preprocessing Time Complexity: O(n log n), where n is the size of the array. This accounts for building the Sparse Table with logarithmic layers.
Query Time Complexity: O(1) for each range query, as the table allows constant-time lookups.
Space Complexity: O(n log n), as the table stores intermediate results for each range and logarithmic level.

Checklist

[x] Added the files sparse_table.py, sparse_table.java and sparse_table.cpp in the corresponding directory
[x] My code aligns with the specified structure.
[x] Updated RoadMap.md

Good work


Update plugin-svgr.mdx

去掉多余标点
Summary
Related Links

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

 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.

Thanks!


refactor math

[x] structure color akin to vector
[ ] extract bvec into extra file
[ ] extract all lib functions to a f32 file

bvec wont be extracted into extra file, because vecs often return it


Remove quotes

Very late breaking requirement for https://trello.com/c/kMYuzoge/75-create-the-become-a-supplier-page-2

Wait wait. Hardcoded framework names?! 😲


Allow nesting > 2 for updateconf/updatedseconf, persist and read dse_config_options

This does a bunch of little things which may not be useful in the general case, but is good to have:

Previously with updateconf/updatedseconf, someone could specify a nested structure, i.e.:
ccm updateconf "client_encryption_options.enabled: true"

This would update cassandra.yaml with:
client_encryption_options:
  enabled: true

In the general case this is more than enough, but there were a few problems:

It would update in place for updateconf (i.e. if there are other options under client_encryption_options, those would remain unchanged), but not with updatedseconf (it'd blow away all children except the newly added element), reconciled that logic into common#merge_configuration.

You couldn't nest > 2 deep, i.e. "spark_application_info_options.driver.sink:true" would not update:
spark_application_info:
  driver:
    sink: true

Instead it would do:
spark_application_info.driver.sink: true

Commit 37afe6a reconciles this.

Configuration for updatedseconf at both the cluster and node level was not being read in when loading the cluster/nodes.   It was also not being persisted at the node level (my mistake since I added that capability).  Commit 201694f reconciles this.
An example to experiment with this:
Update and cluster level with a delete, and then the node level undoing the delete with nested values:
ccm updatedseconf "spark_application_info_options.driver.sink:true" "spark_application_info_options.driver.jvmSource:"
ccm node1 updatedseconf "spark_application_info_options.driver.jvmSource:true"

sink should be true in dse.yaml for all nodes, jvmSource should be present in node1, but not the rest of the nodes.

I'm running dtest with your changes, to confirm it breaks nothing there.

I'm running dtest with your changes, to confirm it breaks nothing there.

Cool, thanks!  Definitely will be nice to exercise it :)

Hello, How to update the seed_provider and the respective seeds IPs of a node through updadeconf command?

Hello, How to update the seed_provider and the respective seeds IPs of a node through updadeconf command?

You will need to use the --yaml/-y option to pass in literal yaml to accomplish this, this would do it:
ccm updateconf -y "seed_provider: [{class_name: org.apache.cassandra.locator.SimpleSeedProvider, parameters: [seeds: '<IP_ADDRESS>,<IP_ADDRESS>']}]"

After the xrange --> range fix, I'm good to merge.

Thanks for reviewing!  I've addressed your feedback in ea25a6c


EZ-SSH on containers not working for not Peer owner users

When other users from Hub are using Peer, can't SSH on containers.

Postponed to be merged after RC14 release

Fixed. Before testing, pls make sure you have updated a test peer.


Visual Studio 2017: Test Adapter 2.1.0 can't find tests in Test Explorer

In Visual Studio 2017 with the latest NUnit Nuget Packages the discovering of new tests doesn't work.
You can try it yourself:
Make a new Solution and a test project in Visual Studio 2017. Then add the latest Nuget Packages:

NUnit 3.6.1
NUnitTestAdapter 2.1.0

Write a simple TestFixture class, build the project. The Test Explorer can't find any tests.
While reading the issues here, I found a workaround:
Downgrade from NUnit version 3.6.1 to version 2.6.4, rebuild -> Discovering of Tests successfully!

NUnit 3.* requires NUnit3TestAdapter .  See https://github.com/nunit/docs/wiki/Visual-Studio-Test-Adapter
So instead of downgrading NUnit, upgrade the adapter instead :-)

Thank you - it works! The Nuget top list was misleading.


fix(longevity): 'to' commit may be computed wrongly for deleted lines…

do not add lines for deleted files since their lines will be added when a diff is processed (double addition)

Should this PR be closed?

no, why?

Because #30 contains the commit from this PR and new commit. Why did you split #29 and #30 ?

Right, it's on top of this branch. That's a thing I don't like about git, you cannot work on on top of other work and hide that fact from your reviewer and probably not confuse him :)
I follow 'one problem - one pull request' rule, it's much easier for tracking, reviewing and all.
So is my understanding correct that you approved both pull requests by approving #30?

Approved both.


UAC password error should prompt instead of close

PC-1-screen0.webm
should prompt like this.

This behavior is coming from sudo I think, and we won't mess with its source code.
Please comment if you know another way to implement this. Thanks.


add z-index utils for simple layout fix

Proposed Changes

Potential Breaking Changes

Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Codecov Report

Merging #1392 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1392   +/-   ##
=======================================
  Coverage   99.23%   99.23%
=======================================
  Files         476      476
  Lines        9960     9960
  Branches     2278     2278
=======================================
  Hits         9884     9884
  Misses         76       76

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 9e13ccf...225c835. Read the comment docs.


add LIVEBOOK_FORCE_SSL env

#983
Is that right?

 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.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


unzip with password

unzip with password is supported by introducing "github.com/alexmullins/zip".
And the no-password-unzip is not affected.

Seriously. who's pushing proprietarily encrypted zip files to the Internet for people to consume? Tell them to knock it off. Zip doesn't support passwords, it's all junk they added on later.

I need to know more about the use case before accepting this contribution. The primary problem I have with it is the lack of updates to the zip package you've chosen to replace the standard lib. It has not been updates in 6 years while the standard lib has received a number of fixes. Like this one. Please provide more info, and/or choose a better maintained library for this critical functionality.


Release/v2.8.0

This release is the first release in months that needed an update based on the changes in the enviroment. In general, the Litewallet code base is bloated with 1000's of lines of unused code and this makes debugging and adding new features very difficult. In addition, the requirements of iOS 14 and the plan to move from UIKit to a SwiftUI+Combine architecture means subsequent PRs will reflect a more streamlined codebase.
Tech Debt

Also have watch xcscheme added per upgrade
Added Issue templates (#122)

Bug Report
Feature Request

Updated key for RemoteRunnable in xcscheme
remove unused fonts
run code on main thread
update cocoapods firebase
update addresses + event

Improvements

compute QR code only once

Soft launch for Import QR Code

Bugfixes

fix crash: window required

Temporary Workarounds
The proxy server the supports buying LTC is being refactored and so no mobile clients can use the Simplex service
* Disabled Simplex / Added temp message
- Was causing crashes when return messages were happening.
- Will update in the next cycle with an updated UI
- Added a Analytics:  DID TAP BUY TAB marker
- Added Coming Soon label to the tableview background view for a temporary sign
- Added all translation for the coming soon message
Authors
Kerry Washington<EMAIL_ADDRESS>Mohamed Barry<EMAIL_ADDRESS>

Agree @mosadialiou if you agree go ahead and approve but I won't merge until


Badges font alignment

I want to confirm that line-height is correct for all badges.
In Zeplin the font of the badge is not on the same line as the font of the containing element, but it seems to be that way in the implementation. I want to confirm this as correct?

The Badges in Zeplin were vertically aligned to the Label's Text Box, based on line height. I don't see it as an issue. @pmmck, your call. Thx

@fuhton @jdrf-digitaldesigner in Zeplin the badges are vertically centered within the line-height.  In the implementation, they are aligned to the baseline.  This looks fine at some sizes but not others.

For the badges inside buttons, a -1px margin has been applied to help with alignment.  I'm not sure if that has been applied with adjustments to all the various button sizes.

@pmmck @jdrf-digitaldesigner
To clarify, the issue we're discussing is that the text inside the labels/badges aren't always on the same baseline as the content outside of it to the left?
So we want to ensure it's always on the baseline regardless of size? Is there an example where we're not seeing it line up? Here's a screenshot of the demo site:

cc: @fuhton

@RachelRVasquez My eyes are playing tricks on me.  You are correct!  Thanks.


Unexpected value of the 'create' constant

I was playing with flags and fsevents.Constants, and found out that kFSEventStreamEventFlagItemCreated has a value of 16. Which is unexpected, since in source code it is declared with 0x00000100 value.
What am I missing here?
var fsevents = require('fsevents');

console.log('kFSEventStreamEventFlagNone 0x00000000 ', fsevents.Constants.kFSEventStreamEventFlagNone);
console.log('kFSEventStreamEventFlagMustScanSubDirs 0x00000001 ', fsevents.Constants.kFSEventStreamEventFlagMustScanSubDirs);
console.log('kFSEventStreamEventFlagUserDropped 0x00000002 ', fsevents.Constants.kFSEventStreamEventFlagUserDropped);
console.log('kFSEventStreamEventFlagKernelDropped 0x00000004 ', fsevents.Constants.kFSEventStreamEventFlagKernelDropped);
console.log('kFSEventStreamEventFlagEventIdsWrapped 0x00000008 ', fsevents.Constants.kFSEventStreamEventFlagEventIdsWrapped);
console.log('kFSEventStreamEventFlagHistoryDone 0x00000010 ', fsevents.Constants.kFSEventStreamEventFlagHistoryDone);
console.log('kFSEventStreamEventFlagRootChanged 0x00000020 ', fsevents.Constants.kFSEventStreamEventFlagRootChanged);
console.log('kFSEventStreamEventFlagMount 0x00000040 ', fsevents.Constants.kFSEventStreamEventFlagMount);
console.log('kFSEventStreamEventFlagUnmount 0x00000080 ', fsevents.Constants.kFSEventStreamEventFlagUnmount);
console.log('kFSEventStreamEventFlagItemCreated 0x00000100 ', fsevents.Constants.kFSEventStreamEventFlagItemCreated);
console.log('kFSEventStreamEventFlagItemRemoved 0x00000200 ', fsevents.Constants.kFSEventStreamEventFlagItemRemoved);
console.log('kFSEventStreamEventFlagItemInodeMetaMod 0x00000400 ', fsevents.Constants.kFSEventStreamEventFlagItemInodeMetaMod);
console.log('kFSEventStreamEventFlagItemRenamed 0x00000800 ', fsevents.Constants.kFSEventStreamEventFlagItemRenamed);
console.log('kFSEventStreamEventFlagItemModified 0x00001000 ', fsevents.Constants.kFSEventStreamEventFlagItemModified);
console.log('kFSEventStreamEventFlagItemFinderInfoMod 0x00002000 ', fsevents.Constants.kFSEventStreamEventFlagItemFinderInfoMod);
console.log('kFSEventStreamEventFlagItemChangeOwner 0x00004000 ', fsevents.Constants.kFSEventStreamEventFlagItemChangeOwner);
console.log('kFSEventStreamEventFlagItemXattrMod 0x00008000 ', fsevents.Constants.kFSEventStreamEventFlagItemXattrMod);
console.log('kFSEventStreamEventFlagItemIsFile 0x00010000 ', fsevents.Constants.kFSEventStreamEventFlagItemIsFile);
console.log('kFSEventStreamEventFlagItemIsDir 0x00020000 ', fsevents.Constants.kFSEventStreamEventFlagItemIsDir);
console.log('kFSEventStreamEventFlagItemIsSymlink 0x00040000 ', fsevents.Constants.kFSEventStreamEventFlagItemIsSymlink);

gives:
kFSEventStreamEventFlagNone 0x00000000  0
kFSEventStreamEventFlagMustScanSubDirs 0x00000001  1
kFSEventStreamEventFlagUserDropped 0x00000002  2
kFSEventStreamEventFlagKernelDropped 0x00000004  4
kFSEventStreamEventFlagEventIdsWrapped 0x00000008  8
kFSEventStreamEventFlagHistoryDone 0x00000010  16
kFSEventStreamEventFlagRootChanged 0x00000020  32
kFSEventStreamEventFlagMount 0x00000040  64
kFSEventStreamEventFlagUnmount 0x00000080  128
kFSEventStreamEventFlagItemCreated 0x00000100  16
kFSEventStreamEventFlagItemRemoved 0x00000200  512
kFSEventStreamEventFlagItemInodeMetaMod 0x00000400  1024
kFSEventStreamEventFlagItemRenamed 0x00000800  2048
kFSEventStreamEventFlagItemModified 0x00001000  4096
kFSEventStreamEventFlagItemFinderInfoMod 0x00002000  8192
kFSEventStreamEventFlagItemChangeOwner 0x00004000  16384
kFSEventStreamEventFlagItemXattrMod 0x00008000  32768
kFSEventStreamEventFlagItemIsFile 0x00010000  65536
kFSEventStreamEventFlagItemIsDir 0x00020000  131072
kFSEventStreamEventFlagItemIsSymlink 0x00040000  262144

It seems that it was changed in 10098b9 for some reason, I don't know why.

The parent of that one https://github.com/strongloop/fsevents/commit/26a1b7392116a5b46e69507ce2f14df18759e184 seems to offer a tiny bit more perspective as to the reason.
@pipobscure if you see this and have any idea, any insight would be appreciated

This might have happened, because around that time a new version of OS-X was released where newwhich led to this being defined on some machines and not others.
So this is a backwards compatibility thing. I think I might have copied it wrong from the header files and that could be the cause. I'm on my phone right now, so I can't check, but I believe some very early issue about not being able to compile were about this.
Cheers


Difficulty determining confidence intervals on median survival times of left-censured data

I am trying to determine the confidence intervals on the median on some left-censured data.  For some reason I keep getting inf when I run median_survival_times(kmf1.confidence_interval_). Below is the code where I am trying to estimate the median CI at 0.95 and 0.84 (1 sigma).  I do get an estimate from the kmf plot, but I don't understand why the values are so similar.  Here's the data file and code.
import pandas as pd
from lifelines import KaplanMeierFitter
from lifelines.utils import median_survival_times
test_df = pd.read_csv("out.csv")
T, E = test_df['loggasfrac'], test_df['lf_censor']
kmf1=KaplanMeierFitter().fit_left_censoring(T,E,label="0.95 cf")
kmf2=KaplanMeierFitter().fit_left_censoring(T,E,alpha=0.16,label="0.84 cf")
median_ci1_test1 = median_survival_times(kmf1.confidence_interval_)
print(median_ci1_test1)
median_ci1_test2 = median_survival_times(kmf2.confidence_interval_)
print(median_ci1_test2)
median_ci_idx1 = kmf1.confidence_interval_.index.get_loc(kmf1.median_survival_time_,
method='nearest')
median_ci1 = kmf1.confidence_interval_.iloc[median_ci_idx1]
median_ci_idx2 = kmf2.confidence_interval_.index.get_loc(kmf2.median_survival_time_,
method='nearest')
median_ci2 = kmf2.confidence_interval_.iloc[median_ci_idx2]
print(median_ci1)
print(median_ci2)
kmf1.plot()
kmf2.plot()
out.csv.zip

Hi @mikekoss -
Ah, this is an inconsistency in the API that I should make more clear. For left censored data, confidence_interval_ returns the  CIs for the CDF, not the survival function (1-CDF). Try
median_survival_times(kmf.confidence_interval_survival_function_)

Ah great that solve my issue. Thanks!


Comprehensive Enhancements to Dependency-Track Helm Chart w/o 3rd party dependencies

🛠 Helm Chart Enhancement

Ingress Template Rewrite: Overhauled the Dependency Track Ingress Template to align with the Bitnami common format, enabling detailed customization and expanded base service definitions. Reimplemented without 3rd party dependencies.
New Template Introductions: Added new templates (dependencytrack.tpl.render, dependencytrack.namespace, dependencytrack.secrets.lookup, dependencytrack.ingress.certManagerRequest) to encapsulate common operations and boost chart maintainability.
Custom Resource Deployment: Implemented a method for deploying additional Kubernetes resources through a custom Helm chart, offering users more flexibility to extend the chart with personal specifications.

🔐 TLS Support

TLS Secrets Management: Introduced a new template for managing TLS Secrets, streamlining certificate handling and enhancing security.
Enhanced Certificate Logic: Updated certificate management to differentiate between auto-generated certificates and those provided by the user, improving flexibility.
TLS Configuration Fields: Enhanced values.yaml with new fields related to TLS configuration, providing clear options for setup.

📖 Documentation

Detailed Annotations: Annotated Ingress and TLS related values in values.yaml extensively, adhering to Helm-docs standards to aid user comprehension.
Updated README: Revised the README document to reflect the recent changes and additions to the chart.

📁 Repository and Codebase Maintenance

Repository Clean-up: Updated .gitignore with new patterns to exclude system generated files and specific IDE/system files.
Helm Packaging: Introduced a .helmignore file to limit contents packaged into the Helm chart.
Extra Deployment Options: Added extraDeploy.yaml to allow specification of extra Kubernetes resources, enhancing the chart's customization and extension capabilities.

🧪 How to Test

Deploy and Validate: Deploy the updated chart in a controlled environment. Validate all new functionalities and custom configurations.
TLS and Certificates: Test the TLS configurations extensively to ensure certificates are handled correctly, whether auto-generated or user-provided.
Documentation Review: Verify that the documentation accurately reflects the chart's capabilities and setup instructions.
Extended Customization: Test the deployment of additional resources via extraDeploy.yaml to confirm functionality and integration without impacting core components.

📅 Impact
As a result of these updates, the Dependency-Track Helm chart is not only more extensible and customizable but also aligns with industry standards and best practices. These improvements significantly enhance usability and potential use cases, ensuring that the chart remains relevant and robust in diverse environments.
Please review the extensive changes and provide feedback. Due to the broad scope of updates, extensive testing is recommended to ensure there are no unforeseen issues.
Closes #17

I am a big fan of this.
Moreover I would appreciate the ability so specify additional volumes and volume mounts. My use case is the Secrets Store CSI driver which allows mounting secrets only after they are mounted as a volume first.


Update toml library from toml-j0.4 to<EMAIL_ADDRESS>

Summary
Closes #2144
Test plan
This is a drop in replacement for the existing toml parser, but I have added a new test for dates.
Here's a cute cuttlefish (well I think it's cute):

Awesome, thanks @cetra3!


pre-commit hook for "check_format" failed a new mixer (text) file

and it's a very bad idea to run astyle on a mixer definition file.
Ask me how I know :)

All this new magic....
Is it astyle alone on the commit hooks?
BTW: Once I am convinced it should not muck with a file I just use
git commit --no-verify

I persist in using Eclipse's git integration, and that just makes for more magic.
BTW @dagar 's Eclipse project works great, but the one generated by cmake for Eclipse-Ninja is now useless for anything but posix builds. It was OK too up to a few months ago, but I was unable to fathom the changes which broke it.

Can you walk me through exactly what happened, where the file was, etc? make check_format is supposed to be a warning only with no files touched.
@davids5 Yes, it's just astyle, but we limit it to the src/ folder and still exclude some things.https://github.com/PX4/Firmware/blob/master/Tools/files_to_check_code_style.sh

@dagar
It does not look like astyle - with blank EOF warnings on initial commits some files with vim tags.
Next time I get one I will capture it here.

Oh, right it also does git diff --check
--check
Warn if changes introduce whitespace errors. What are considered whitespace errors is controlled by core.whitespace configuration. By default, trailing whitespaces (including lines that
solely consist of whitespaces) and a space character that is immediately followed by a tab character inside the initial indent of the line are considered whitespace errors. Exits with
non-zero status if problems are found. Not compatible with --exit-code.

@dagar
Don't get me wrong I love ALL the new magic - Thank you for it!
It is just sometimes, usually at the end of a long day, it becomes a rabbit hole I have to go down and in the true fashion of a "rabbit hole"  I never know - how deep it is or where it will come out. But you are super good at helping to teach this old dog new tricks.
ug...did I really just use that many metaphors :)

I hit this again yesterday trying to do a commit using Eclipse. I had added new sourcefiles (see https://github.com/PX4/Firmware/pull/5821).  I shifted to a bash shell, deleted the pre-commit hook and committed manually. It may be that new files are not handled properly by the format checker.

@kd0aij
It look like the hooks run a diff test for EOL, and EOL on an  empty line at the end of a file when a new file first committed.
So it should be simple to reproduce the error on a test branch.

Oh, okay so it's just the pre-commit hook checking whitespace errors on all
files here - https://github.com/PX4/Firmware/blob/master/Tools/
pre-commit#L50
It should only be running astyle (without modifying) on appropriate files
in src/.
On Tue, Nov 8, 2016 at 9:19 AM, David Sidrane<EMAIL_ADDRESS>wrote:

@kd0aij https://github.com/kd0aij
It look like the hooks run a diff test for EOL, and EOL on an empty line
at the end of a file when a new file first committed.
So it should be simple to reproduce the error on a test branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/issues/5726#issuecomment-259147978, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFK6MTqxITwoiACIRRcp3di3D-HTAoYks5q8ITfgaJpZM4Kd4LW
.

I understand it was a bit confusing to have it pop up in eclipse, but is git diff --check ever wrong? It's supposed to only error if you introduce whitespace errors.
On the command line you can always do git commit --no-verify.

I didn't now about git diff --check but it doesn't complain now.

There would have to be a current diff (something not yet committed or staged).

I had a bunch of unstaged changes when I ran the diff.

Right, but previously if you had stumbled across a particular problematic case that change is no longer around to test.
Do you still think there's a problem here?

I can't reproduce it at the command line. No complaints from git diff --check or make check_format

Alright, ping me on gitter or skype if you hit a problem again and we'll take a closer look.


link-to within Engine not working

I am not able to get link-to working within the engine for any route other than index. Here is a sample engine that demonstrates the issue: https://github.com/lmcardle/sample-ember-engine. The link-to is added inside the engine and is linking to a route, 'people', which is also inside the engine. The error I am getting says "there is no route named people."

seems like you have to use sample.people and sample.index. not sure why
https://github.com/lmcardle/sample-ember-engine/blob/master/addon/templates/application.hbs#L6

Seems as though this commit needs porting back to the 0.3.x.
Updating to 0.4.0 should fix your issue but I believe that release requires Ember v2.10.0+.


fixing: unable to add any extension with options

In current configuration i am unable to add any extensions that require own options, e.g.:
markdown_extensions:
    - toc:
        anchorlink: true

As it fails on build due to lack of configs key in configuration.

LGTM

Thanks.


[Marker.io] pointer is not changing to hand icon on hovering over the tiles or arrow buttons in the "our solutions" section

Steps to reproduce:

go to our solutions section
hover over the tiles and the buttons

Actual result: pointer does not change to hand icon suggesting that they are clickable
Expected result: it should change to hand icon on hovering over the tiles ( since button color is changing suggesting tile should be clickable also)
and also on hovering over arrow button

Reported by: vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://proav-stg.webflow.io/
Issue details: Open in Marker.io
Device typedesktopBrowserChrome <IP_ADDRESS>Screen Size1366 x 768OSWindows 10 (10.0.0)Viewport Size1366 x 641Pixel Ratio@1x

🤖 Marker.io bot - This issue was marked as ✅ Resolved in Marker.io


readme fix

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.27%. Comparing base (2137b68) to head (9e101d3).
Report is 14 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage   99.27%   99.27%
=======================================
  Files           1        1
  Lines         276      276
  Branches       65       65
=======================================
  Hits          274      274
  Misses          1        1
  Partials        1        1

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


feat(RhmiConfig): add a watch to the rhmiconfig in the settings page

Motivation
Improve usability by watching for changes in the RHMIConfig CR instead of waiting for the user to refresh the page to view the changes
What
Add a watcher to the RHMIConfig CR endpoint
Why
Improve usability
How
Polling the RHMIConfig CR endpoint and in case of changes updating the state of the settings page
Verification Steps

Install the webapp
Run the webapp against your cluster. See how to do here
Go to the settings page by clicking on the cog icon (located in the top right corner of the webapp)
Change the spec block of the RHMIConfig CR and verify if the change has appeared in the webapp

Checklist:

[x] Code has been tested locally by PR requester
[ ] Changes have been successfully verified by another team member

Progress

[x] Finished task
[ ] TODO

/lgtm
/approve


Mock up health-status screen

Figma:
https://www.figma.com/file/8CiUNS9zH2NUm74VEicn64/Unity-screen-flows?type=design&node-id=2098%3A6287&mode=design&t=rgYJcTtn4jFHHLXh-1

show list of services that are installed
for each, show status (good / bad / warn?)
for each, have a link to a web view if applicable
for each, have a link to an endpoint if applicable

initially, we won't have the links to the services/webview as of right now, i think we should remove that from the AC.

https://www.figma.com/file/8CiUNS9zH2NUm74VEicn64/Unity-screen-flows?type=design&node-id=2098%3A6287&mode=design&t=rgYJcTtn4jFHHLXh-1

@mike-gangl the landing-page links are in now, correct?

Can we remove kion? in a perfect world, users won't need access to that as they'll have unity accounts, not AWS accounts.

Also, might be worth sorting by health status- unhealthy services pushed to the top for attention? Maybe color coded (red? what else?)

That is just a mockup so I was trying to think of everything that could possibly go there. For now if we're driving the list off the health list, the navbar will include everything.
And yes you can sort/filter on any column and we could default to health status as the sort-order.

Some sort of icon or color-tag may help scan the list, yes.
I prefer using a colored icon because it avoids issues with foreground/background contrast of the letters, and helps with color blindness by using shape as an additional communication method.
In this case I right-aligned it so the text is still in a column but it's probably better to left-align the icon in the health column and still keep the text left-aligned (it's just time-consuming to fix the mockup components to do this cleanly, so I stuck it on the right. it's easier in code :p )

(to be clear: removing/adding kion or any other thing will depend on the contents of the health json response. the UI won't have any business logic to choose how to organize/filter the services/links )

(Which, I just realized, means the health dashboard itself needs to be in that response unless we hard-code it)

done


cosmic-silverblue image does fails to start

I just installed fedora silverblue 40, then ran the first command in the readme here to rebase to the cosmic-silverblue image.
I get this error on boot:
2024-07-26T22:54:08.288042Z ERROR cosmic_comp::config: Failed to read config 'workspaces': NoConfigDirectory
2024-07-26T22:54:08.288136Z ERROR cosmic_settings_config: Failed to read local shortcuts config "system_actions": NoConfigDirectory
2024-07-26T22:54:08.288213Z WARN cosmic_settings_config::shortcuts::ram: Key-binding {"Comma"} only matched case insensitive for "comma"
2024-07-26T22:54:08.288229Z WARN cosmic_settings_config::shortcuts::ram: Key-binding {"Comma"} only matched case insensitive for "comma"
2024-07-26T22:54:08.288245Z WARN cosmic_settings_config::shortcuts::ram: Key-binding {"Period"} only matched case insensitive for "period"
2024-07-26T22:54:08.288260Z WARN cosmic_settings_config::shortcuts::ram: Key-binding {"Comma"} only matched case insensitive for "comma"
2024-07-26T22:54:08.288275Z ERROR cosmic_settings_config::shortcuts: Failed to become owner of name "org.cosmic.ConfigDaemon": Unable to acquire bus name: { "name": "org.cosmic.ConfigDaemon", "error": NotFound, message: "No such file or directory" }}
2024-07-26T22:54:08.380925Z WARN [libgbm|backend/egl/context]: Ignoring requested context priority, EGL_IMG_context_priority not supported priority=High
2024-07-26T22:54:08.380973Z WARN [libgbm|backend/egl/context]: Ignoring requested context priority, EGL_IMG_context_priority not supported priority=High
2024-07-26T22:54:08.384149Z WARN [libgbm|backend/egl/context]: Ignoring requested context priority, EGL_IMG_context_priority not supported priority=High
2024-07-26T22:54:08.397825Z WARN [libgbm|backend/egl/context]: Ignoring requested context priority, EGL_IMG_context_priority not supported priority=High
2024-07-26T22:54:08.415073Z WARN cosmic_comp::wayland::compositor: Preferred format ARGB not available: NoSupportedPixelFormat
2024-07-26T22:54:08.415132Z WARN cosmic_comp::wayland::compositor: Preferred format ARGB not available: NoSupportedPixelFormat
2024-07-26T22:54:08.529562Z ERROR panic: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error::NoDevices(DrNode { dev: 57984, ty: Render })': src/backend/kms/surface/mod.rs:313
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: <unknown>
12: <unknown>
13: <unknown>
14: <unknown>
15: __libc_start_call_main
16: __libc_start_main_impl
17: <unknown>

2024-07-26T22:54:08.529552Z ERROR panic: thread 'surface-Virtual-1' panicked at 'called `Result::unwrap()` on an `Err` value: PoisonError { .. }': /buildir/build/BUILD/cosmic-comp-f44e46fa4493dcacbf656a6cfeb5dbe7dced55c5/vendor/smithay/src/desktop/space/mod.rs:69
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: <unknown>
12: <unknown>
13: <unknown>
14: <unknown>
15: <unknown>
16: start_thread
17: __clone3

Anyone faced this before? Is there a way for me to install it and run?

I opened issue on Cosmic repo https://github.com/pop-os/cosmic-epoch/issues/456

I think it's just a config parsing error, might need to reset your configs

the issue is that the user "cosmic-greeter" and "greetd" is not in "/etc/passwd" file, also the corresponding groups where not populated, at least it was the issue for me:
This is how I resolved it:
$ grep -E '^greetd:' /usr/etc/passwd | sudo tee -a /etc/passwd
$ grep -E '^cosmic-greeter:' /usr/etc/passwd | sudo tee -a /etc/passwd
$ grep -E '^greetd:' /usr/etc/group | sudo tee -a /etc/group
$ grep -E '^cosmic-greeter:' /usr/etc/group | sudo tee -a /etc/group

I hope it helps

Did you rebase from another image?
On Sun, Aug 4, 2024, 5:43 PM Alexej Kowalew @.***>
wrote:

the issue is that the user "cosmic-greeter" and "greetd" is not in
"/etc/passwd" file, also the corresponding groups where not populated, at
least it was the issue for me:
This is how I resolved it:
$ grep -E '^greetd:' /usr/etc/passwd | sudo tee -a /etc/passwd
$ grep -E '^cosmic-greeter:' /usr/etc/passwd | sudo tee -a /etc/passwd
$ grep -E '^greetd:' /usr/etc/group | sudo tee -a /etc/group
$ grep -E '^cosmic-greeter:' /usr/etc/group | sudo tee -a /etc/group
I hope it helps
—
Reply to this email directly, view it on GitHub
https://github.com/ublue-os/cosmic/issues/48#issuecomment-2267722365,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQPNFFOKYO4XK2B55V4HNWDZP2OABAVCNFSM6AAAAABLRVJDWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRXG4ZDEMZWGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Did you rebase from another image?

yes, from silverblue

I see. Yeah, same as swapping from kde to gnome or back and forth. You also will need to add to /etc/shadow as well.

This was not necessary, at least for me.

This sounds like a mistake on this image or the greetd package. These shouldn't be in /usr/etc/passwd and so on (only populating correctly if these don't exist from a previous image), but handled via systemd-sysusers, so the user would get created correctly and automatically, when rebasing.

This sounds like a mistake on this image or the greetd package. These shouldn't be in /usr/etc/passwd and so on (only populating correctly if these don't exist from a previous image), but handled via systemd-sysusers, so the user would get created correctly and automatically, when rebasing.

I just was able to rebase without a problem to my cosmic image and didn't have to modify /etc/passwd. There was some issue on the VM I tried but worked fine on hardware
Greetd was extremely verbose on the console while using console on hardware.

the issue is that the user "cosmic-greeter" and "greetd" is not in "/etc/passwd" file, also the corresponding groups where not populated, at least it was the issue for me:
This is how I resolved it:
$ grep -E '^greetd:' /usr/etc/passwd | sudo tee -a /etc/passwd
$ grep -E '^cosmic-greeter:' /usr/etc/passwd | sudo tee -a /etc/passwd
$ grep -E '^greetd:' /usr/etc/group | sudo tee -a /etc/group
$ grep -E '^cosmic-greeter:' /usr/etc/group | sudo tee -a /etc/group

I hope it helps

That helped me. Thanks a lot! Right after that i tried to start cosmic-greeter service again and got this error:

But after restart it was ok. I then managed to login to the system and finally try cosmic desktop!


Feature store code coverage report as build artifacts

Archive code coverage html report with actions/upload-artifact@v2

Codecov Report

Merging #11 (04ff08a) into master (d48430d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines           53        53
  Branches         1         1
=========================================
  Hits            53        53

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 d48430d...04ff08a. Read the comment docs.


[pulsar-storm] allow option to configure queue size of pulsar-spout-consumer

Motivation
Allow option to configure queue size of pulsar-spout-consumer when spout handles higher msg-rate

run cpp tests


Update to spdlog 1.12 and fmt 10.1.1

Description

Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The cmake-format.json is up to date with these changes.
[x] I have added new files under rapids-cmake/

[ ] I have added include guards (include_guard(GLOBAL))
[ ] I have added the associated docs/ rst file and update the api.rst

There's an ongoing migration in conda-forge in moving all packages to using spdlog v1.12 and fmt v10. This will eventually cause issues solving environments unless rapids libraries support these versions as well.
Probably need to test downstream libraries especially for the fmt upgrade before we can merge this.
Related RMM issue: https://github.com/rapidsai/rmm/issues/1356
Related conda-forge PR to bring the spdlog patch for nvcc into the 1.12 builds: https://github.com/conda-forge/spdlog-feedstock/pull/59

/ok to test

@robertmaynard I'll open PRs to test these versions on RAPIDS repos soon. @kkraus14 Thanks for the upstream fix and the backport for conda-forge packages. That helps a lot.

FYI -- RMM 23.10 had its tests built successfully in conda-forge: https://github.com/conda-forge/librmm-feedstock/pull/58

Yeah we should test nvbench as well. Since it it used by cudf that allows us to test when we gave consumers that use both configurations ( header-only vs library)On Nov 2, 2023, at 9:37 PM, Bradley Dice @.***> wrote:
Testing PRs:
rapidsai/rmm#1374
rapidsai/cudf#14355
rapidsai/ucxx#117
rapidsai/raft#1957
rapidsai/cuml#5640
I think these are all the RAPIDS repos that use spdlog/fmt.
The only downstream user I'm not sure about is nvbench. Do we need to test it too? https://github.com/NVIDIA/nvbench/blob/57c4d42ba505d525a1a3815d2b2560450a4f83dd/cmake/NVBenchDependencies.cmake#L10
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Update: conda C++ builds with fmt 10 / spdlog 1.12 are failing for cudf. https://github.com/rapidsai/cudf/pull/14355
I've updated the fmt/spdlog pinnings in rapids-cmake and in cudf, and it's using RMM artifacts with the correct pinnings as well. The conda environment is pulling spdlog 1.12 and fmt 10, so we're getting the build environment that we want. The C++ build shows this failure in the logs:
sccache $BUILD_PREFIX/bin/x86_64-conda-linux-gnu-c++ -DCUFILE_FOUND -DFMT_HEADER_ONLY=1 -DJITIFY_PRINT_LOG=0 -DKVIKIO_CUFILE_BATCH_API_FOUND -DKVIKIO_CUFILE_FOUND -DLIBCUDACXX_ENABLE_EXPERIMENTAL_MEMORY_RESOURCE -DRMM_LOGGING_LEVEL=LIBCUDF_LOGGING_LEVEL -DSPDLOG_ACTIVE_LEVEL=SPDLOG_LEVEL_INFO -DSPDLOG_FMT_EXTERNAL -DTHRUST_DEVICE_SYSTEM=THRUST_DEVICE_SYSTEM_CUDA -DTHRUST_HOST_SYSTEM=THRUST_HOST_SYSTEM_CPP -Dcudf_EXPORTS -I$SRC_DIR/cpp/build/_deps/dlpack-src/include -I$SRC_DIR/cpp/build/_deps/jitify-src -I$SRC_DIR/cpp/include -I$SRC_DIR/cpp/build/include -I$SRC_DIR/cpp/src -I$PREFIX/include/rapids/libcudacxx -I$SRC_DIR/cpp/build/_deps/thrust-src -I$SRC_DIR/cpp/build/_deps/thrust-src/dependencies/cub -I$SRC_DIR/cpp/build/_deps/cuco-src/include -I$BUILD_PREFIX/include -isystem $PREFIX/include/gdeflate -fvisibility-inlines-hidden -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem $PREFIX/include -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/libcudf-split- -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix  -I$PREFIX/targets/x86_64-linux/include -I$BUILD_PREFIX/targets/x86_64-linux/include  -L$PREFIX/targets/x86_64-linux/lib -L$PREFIX/targets/x86_64-linux/lib/stubs -L$BUILD_PREFIX/targets/x86_64-linux/lib -L$BUILD_PREFIX/targets/x86_64-linux/lib/stubs -O3 -DNDEBUG -std=gnu++17 -fPIC -Wall -Werror -Wno-unknown-pragmas -Wno-error=deprecated-declarations -Wno-deprecated-declarations -pthread -MD -MT CMakeFiles/cudf.dir/src/io/utilities/datasource.cpp.o -MF CMakeFiles/cudf.dir/src/io/utilities/datasource.cpp.o.d -o CMakeFiles/cudf.dir/src/io/utilities/datasource.cpp.o -c $SRC_DIR/cpp/src/io/utilities/datasource.cpp
In file included from $PREFIX/include/spdlog/fmt/fmt.h:31,
                 from $PREFIX/include/spdlog/common.h:50,
                 from $PREFIX/include/spdlog/spdlog.h:12,
                 from $SRC_DIR/cpp/include/cudf/utilities/logger.hpp:19,
                 from $SRC_DIR/cpp/include/cudf/detail/utilities/logger.hpp:19,
                 from $SRC_DIR/cpp/src/io/utilities/config_utils.hpp:18,
                 from $SRC_DIR/cpp/src/io/utilities/datasource.cpp:24:
$PREFIX/include/fmt/core.h: In instantiation of 'constexpr fmt::v10::detail::value<Context> fmt::v10::detail::make_arg(T&) [with bool PACKED = true; Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; T = const cudaError; typename std::enable_if<PACKED, int>::type <anonymous> = 0]':
$PREFIX/include/fmt/core.h:1808:51:   required from 'constexpr fmt::v10::format_arg_store<Context, Args>::format_arg_store(T& ...) [with T = {const cudaError, const char*}; Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; Args = {cudaError, const char*}]'
$PREFIX/include/fmt/core.h:1826:18:   required from 'constexpr fmt::v10::format_arg_store<Context, typename std::remove_cv<typename std::remove_reference<T>::type>::type ...> fmt::v10::make_format_args(T& ...) [with Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; T = {const cudaError, const char*}]'
$PREFIX/include/spdlog/logger.h:374:75:   required from 'void spdlog::logger::log_(spdlog::source_loc, spdlog::level::level_enum, spdlog::string_view_t, Args&& ...) [with Args = {const cudaError&, const char*}; spdlog::string_view_t = fmt::v10::basic_string_view<char>]'
$PREFIX/include/spdlog/logger.h:90:13:   required from 'void spdlog::logger::log(spdlog::source_loc, spdlog::level::level_enum, fmt::v10::format_string<T ...>, Args&& ...) [with Args = {const cudaError&, const char*}; fmt::v10::format_string<T ...> = fmt::v10::basic_format_string<char, const cudaError&, const char*>]'
$SRC_DIR/cpp/src/io/utilities/datasource.cpp:197:7:   required from here
$PREFIX/include/fmt/core.h:1576:63: error: 'fmt::v10::detail::type_is_unformattable_for<const cudaError, char> _' has incomplete type
 1576 |     type_is_unformattable_for<T, typename Context::char_type> _;
      |                                                               ^
$PREFIX/include/fmt/core.h:1580:7: error: static assertion failed: Cannot format an argument. To make type T formattable provide a formatter<T> specialization: https://fmt.dev/latest/api.html#udt
 1580 |       formattable,
      |       ^~~~~~~~~~~
$PREFIX/include/fmt/core.h:1580:7: note: 'formattable' evaluates to false

It seems like we need some C++ updates to make this code compile, but I haven't been able to identify exactly what is needed yet. I think it's failing to format logging messages involving cudaError at compile time? I'll pick up this investigation again soon, but more eyes would be welcome if someone has time.

CPM was having trouble finding fmt because the version was reported incorrectly (10.1.0 instead of 10.1.1). I fixed it with this PR: https://github.com/conda-forge/fmt-feedstock/pull/38.

/ok to test

CPM is now correctly picking up the fmt package with the version fix. I'm rerunning CI (rmm is complete, now cudf and raft, ...). I'm also attempting to rebuild all of RAPIDS locally with devcontainers.

We're making progress! cudf passes CI now. I am rerunning the last few repos. I am hoping to merge this by the end of the week, ideally tomorrow.

All builds succeeded. Reviews have been requested. Merging soon.

/merge


Fixed a markdown error in the Manual install steps

The markdown in the Manual Installation section had an error that messed up the formatting of command and regular text. This commit fixes it.
I know this is a simple PR; but I am excited because this is my first one!

Looks like this was taken care of #2031. Thanks anyway! Cheers! 🍻


Improve component test spec

[kind/Enhancement]

Which functionality do you think we should update/improve?
Test spec for component test
Why is this needed?
To add more test coverage

Improve how?
This needs a better definition of what needs to be done.

Improve how?
This needs a better definition of what needs to be done.

Will update as per our last discussion

Improve how?

It depends what impact the code brings to the local system and the cluster aswell. For example
component creates involve

Create local config (Local config data need to be verified because it is created by odo)

Need to push the changes what is created in local config to confirm that it should work or not

For successful push, local config should reflect in the cluster in dc level (Same dc data need to be verified)

Expected end result

App end point should work (need to be verified)

These steps in each scenario should be verified to confirm pass and failure status. Other than this there are many flag to test along with component command.

This needs a better definition of what needs to be done.

Updated the above points from our last 1-1 discussion.

@amitkrout Can you please break this down into smaller tasks that can be addressed in a sprint?
Or modify the description with more information what exactly is required

@amitkrout Can you please break this down into smaller tasks that can be addressed in a sprint?
Or modify the description with more information what exactly is required

[ ] Test should run for component and component shortcut commands

[ ] verify the local config after component creation

[ ] If flags are used other than default then verify the local config along with the changes done in dc

[ ] Verify the component create UTs and fix those missing cases if any so that we can minimize the integration test coverage with respect to UTs.

[ ] Add negative cases for user facing cases

[ ]  App route should work after each component create followed by a push

https://github.com/openshift/odo/issues/2256#issuecomment-558949843
@prietyc123 I can see the pending task here. So reopen it.


Keyboard shortcuts not working on Windows

Describe the bug
I'm unable to pull up the control panel in Windows. In fact, all of these don't work:

command-k: Toggle control panel
command-shift-enter: Start presentation (from first slide)
command-enter: Resume presentation (from active slide)
command-shift-f: Toggle full-screen mode
command-.: End presentation

To Reproduce
Open the demo site in Windows and try any of the shortcuts above. Nothing happens
Expected behaviour
The action associated with each shortcut happens
Screenshots
Desktop (please complete the following information):

OS: Windows 11
Browser Chrome, Edge, and Firefox

I'm assuming in Windows command should be replaced by ctrl. Is that right?

Maybe? Mac has both, and I thought windows did too? It sounds to me like we should maybe re-open #3 and make sure we have a proposed set of shortcuts that work everywhere.

Windows keyboards don't have Cmd; just Ctrl, Alt, Shift and the Windows key (also called Super in Linux). I would expect Ctrl to work in Windows as Cmd does in Mac, that's how I've always seen apps do it

For context: here are the shortcuts for Windows and Mac for VS Code

Sounds good to me. Something you want to implement?

Yep, will do 👍

Shortcuts discussion in this issue: https://github.com/oddbird/slide-deck/issues/3


added animation and shadow effect to testimonial cards

added animation and shadow effect to testimonial cards and changed image

@Akayush-17 pull recent changes in the website and ping me on discord and here

@Akayush-17 pull recent changes in the website and ping me on discord and here

@Susmita-Dey I have already made pull request.

@Akayush-17 ???


Corrects Laravel version listed in README

Version 1 of Voyager supports Laravel 5.5.

Whoops, good find! We actually support 5.4 and 5.5, so I changed the wording myself. Thanks for finding it!


Testing, please ignore. (zkqxey)

This is a bug bounty test. Please ignore.. Please DO NOT APPROVE THIS! (zkqxey)

@magniv1 Could you clarify what this PR relates to?


Session error message when starting phpmyadmin

I'm getting this error message session_write_close(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/sessions) when opening phpmyadmin in browser.
It's seems that the session files are created but they are empty.
How can i fix this issue?
Here is my system information:

Host: Windows 7 64b
Docker toolbox: 1.12
Laradock: 4..0

@appleboy

This also happened to me, seems to be related to symfony but couldn't find anything there. https://github.com/symfony/symfony/issues/17845

Found the error!!! You have to unmount sessions, you can do this easily with the help of kitematic by pressing remove and it will look like below. Would open a pull request for this but I am still a newbie with dockers.

I updated to latest version and it seems to be fixed.

@mbasfour Could you close this issue?