Enalbe fast creation of virtual environments with pip-tools

I have added a minimum setup that facilitates the creation and update of a virtual environment for bark project. I have tried to keep it as simple as possible:

it only adds pip-tools for virtual environment management.
I have added a Makefile with commands to perform a fast setup of the project with make setup and also for updating virtual envioronments in case they evolve with time.

Hi @jruizaranguren, thanks for the PR.
The PR is very specific to the Python version, env of choice though. There are files that are generated with Python version 3.11 but I'd imagine there are users with 3.10, 12 etc. It would be great to keep the main repo generalizable across different development envs. I'd recommend making some changes in this PR that remove the auto-generated files.

@tongbaojia you are right. I wanted to make it as simple as possible, but requiring a specific python version is a hard constraint.
I see two alternatives:

remove requirements.txt, dev-requirements.txt from source control and take python version from environment. It assumes that each user will fork the repository, will invoke make setup and they will upload their *.txt files to their branch for convenience.
add tox to the mix, so we can effectively manage different environments. I doubt is worth the effort.
What do you think?

@jruizaranguren My 2 cents: I think a flexible package should support multiple envs/developers. The less constraint there is, the easier different users could interact with it.
For example, consider pandas, you don't want all pandas to have a vital requirement on dependencies -- different versions of pandas may require a min version of numpy and that's fine, but requiring a requirement file with fixed versions of dependencies is too much (this will cause headaches for developers to resolve dependency issues in python).  Creating virtual envs & pip tool management, should not be the user/engineer's job and done on the backend, rather than a pip-installable pkg.
So I don't think that this diff needs to be landed into the main repo. You should instead maintain all these requirement.txt etc in your dev project that uses bark. That would be an optimal solution.

Agree. Closing pull request.


Can't extend/set inset

Hi,
I'm new using Tailwind. Thanks for this, It's just freaking awesome !
I have an issue. I'm trying to extend inset values, like this  :
module.exports = {
  theme: {
    spacing: {
      "0": "0rem",
      "1": "0.25rem",
      "2": "0.5rem",
      "3": "0.75rem",
      "4": "1rem",
      "5": "1.5rem",
      "6": "2rem",
      "7": "3rem",
      "8": "4rem",
      "9": "6rem",
      "10": "8rem",
      "11": "12rem",
      "12": "16rem",
      "13": "24rem",
      "14": "32rem",
      "15": "40rem",
      "16": "48rem"
    },
    extend: {
      inset: theme => theme("spacing"),
    }
  },
  variants: {},
  plugins: []
};

I also tried this :
module.exports = {
  theme: {
    extend: {
      inset: {
        "42": "42px",
      }
    }
  },
  variants: {},
  plugins: []
};

Nothing appears to work. Am I doing something wrong or is this a bug ?

Ok, I had to restart rerun : yarn run serve to see changes.


Ambiguous use of 'each'

I'm not sure why, but on each i get an Ambiguous use Error
var buttons = [UIButton]()
$.each(buttons, callback: println)

other functionality on the dollar namespace works, only each gives an Ambiguous use Error

You can currently do so as such:
var buttons = [UIButton]()
buttons.append(UIButton())
$.each(buttons, callback: { print($0, $1) })

Closing this issue.

The Ambiguous use Error is because you need specify which overloaded each function you are using.
var buttons = [UIButton]()
buttons.append(UIButton())
$.each(buttons, callback: { (btn: UIButton) -> () in print(btn) })


Resize multiple charts

I have 3 charts on 1 page, but resizing works only in the last one and works only for extending width, not when i resize browser window to smaller width. Can you please suggest a solution?

@pissang I think this is a bug that echarts should try to fix. because flexbox layout is now popular.

@Kopyov thanks for that!

I was having the same issue. But there was flebox container. As a solution, during initialization, I stored each chart  to charts array.  And, on window.resize() , I looped the array and invoked resize() on each chart object.
  charts: [],
  initalizeChart(data) {
    const values = [];
    const timestamps = [];
    const self = this;

    data.forEach((item) => {
      values.push(item.value);
      timestamps.push(item.timestamp);
    });

    const option = this.setupOptions(values, timestamps);
    const chart = document.querySelector(`#${this.elementId} .chart`);
    **const myChart = window.echarts.init(chart);**

    **self.charts.push(myChart);**

    **window.onresize = function() {
      self.charts.forEach((obj) => {
        obj.resize();
      });
    };**

    myChart.setOption(option);
  },

I've fixed in this way:

I was using the grid for showing multiple charts, and made it responsive in this way:
In app.js (inside resources/js) I've added this part of code:
window.allCharts = []; window.onresize = function () {     allCharts.forEach((chart) => {         chart.resize();     }) };
and then inside the files I've write this part of code:

@tnt-freskim-veliu how can I use Echarts on a Laravel Livewire  project.

These solutions weren't working for me. What did work was an adaptation of code posted by @plainheart at https://github.com/apache/echarts/issues/13004. I don't know how it works exactly, but it first hides all the charts, then resizes, then shows them again. In the code, charts should contain all echarts instances.
function showChartDom(chart, visible) {
  chart.getZr().painter.getViewportRoot().style.display = visible ? "" : "none";
}

window.addEventListener("resize", resize);
function resize() {
  charts.forEach((chart) => showChartDom(chart, false));
  charts.forEach((chart) => chart.resize());
  charts.forEach((chart) => showChartDom(chart, true));
}


Add a helper function to resolve module import text to a file

currently resolving a context for the language service requires calling ts.preProcessFile on all files in the context, and following references. resolving triple-slash references is simple, resolving modules is a bit more complicated, as it involves searching in containing directories until a matching .ts file is found.
As a work around, here is the resolution logic:
function resolveImport(moduleName: string, souceFilename: string, fileExists: (filename: string) => boolean): string {
        var searchPath = ts.getDirectoryPath(souceFilename);

        while (true) {
            var filename = ts.normalizePath(ts.combinePaths(searchPath, moduleName));
            if (fileExists(filename + ".ts")) return filename + ".ts";
            if (fileExists(filename + ".d.ts")) return filename + ".d.ts";

            var parentPath = ts.getDirectoryPath(searchPath);
            if (parentPath === searchPath) break;

            searchPath = parentPath;
        }

        return undefined;
    }

This should be handled by #1735

The wiki links to this page.

Something that is currently missing, and should be added in next release, is a built-in way to resolve imports. ts.preProcessFile returns import text, and the caller needs to resolve that to a .ts file path. Issue #1793 tracks fixing it.

Should that be updated?

Should that be updated?

i think so.

@mhegazy Is there updated documentation that shows how this can be done? I'm looking to implement some custom module-resolution logic. I have it working with tsc, but I'd like the IDE to be able to resolve these modules as well without them showing up as errors.

@mhegazy Is there updated documentation that shows how this can be done? I'm looking to implement some custom module-resolution logic. I have it working with tsc, but I'd like the IDE to be able to resolve these modules as well without them showing up as errors.

IDE's use tsserver. the only way you can change the behavior there is if you create a language service plugin. you can find more docs about LS plugins in https://github.com/Microsoft/TypeScript/wiki/Writing-a-Language-Service-Plugin


{app-name} variable no longer applies

Currently the {app-name} property is set for each booster runtime as a property to be replaced in various doc usage.
Unfortunately the boosters are now using {project.artifactId} in their builds which means the name for {app-name} is entirely dependent on what the user specifies in the Launchpad UI.

@rhoads-zach It looks like {app-name} is now substituted with PROJECT_NAME:

Which seems wrong.
@kenfinnigan Why does  {project.artifactId} changes when booster are cloned through the launchpad? Overall this change seems to do more damage than good to me.

@rhoads-zach Should we reopen this one to revisit the problem?

Another example from the current docs:

@heiko-braun this change is necessary because the ${project.artifactId} is not fixed when cloned through the Launchpad.
Each user gives the project a unique name


Allow the user to emit extra fake modules

A common annoyance for browsers is that we have a bunch of pages allocated by the JIT in a range of memory that is effectively a secret self-modifying module. One of the simplest and cleanest ways to make everything down the line understand this would be to allow the crashing process to tell minidump-writer about such "secret modules"
For spidermonkey's purpose, literally all that matters is the location+size, and a name. Things like codefiles/debugfiles could be junk/magic, but I would need to test that.

In the breakpad clients, I see an AddMappingInfo that looks like the same concept.
https://searchfox.org/mozilla-central/rev/6ec440e105c2b75d5cae9d34f957a2f85a106d54/toolkit/crashreporter/breakpad-client/linux/handler/exception_handler.h#218-222


Updating README to meet unified gcloud-* format.

@jgeewax PTAL
Holding off on Authorization until we finalize this behavior and unify across services.
Styled after https://github.com/GoogleCloudPlatform/gcloud-node
See https://github.com/dhermes/gcloud-python/blob/standardize-readme/README.rst for updated version.
Partially addresses #591.
Needs #668 to be done among other things before Authorization can be documented (not a very unified approach right now)

Coverage remained the same at 100.0% when pulling 1b0c45f396e56659346a07f6a04d702846c537e8 on dhermes:standardize-readme into 56f60bb94b313c397f5aeadee1f0e1f6e5b5290c on GoogleCloudPlatform:master.

:+1:


Fix bindings

Fix for https://github.com/software-mansion-labs/cairo/commit/7abdc3261c9ab2885a3cebe534f19108ce7391b3

closing in favor of #1503


.github: re-enable configurations in e2e-upgrade

Some tests got out of sync with conformance-e2e. As conformance-e2e got removed from our CI, this commit is updating e2e-upgrade to have the same configurations used in the conformance-e2e.
Fixes https://github.com/cilium/cilium/issues/30717
Fixes https://github.com/cilium/cilium/issues/34219

1/9 runs failed, the failure unrelated with the changes https://github.com/cilium/cilium/actions/runs/10790978461

/test


[Harvesters - WMS] GeoNode resources are not correctly defined

Some defaults are missing, like the ows_url and the detail_url
Be careful, we cannot use an internal workspace, currently the Remote Services define a special internal workspace in order to avoid clashes with the internal GeoServer ones
The Remote Services generate different defaults and different workspaces in case the WMS is CASCADED or INDEXED; a CASCADED WMS service is basically proxied by a GeoServer cascade datastore. This is done in the case the remote service does not support GeoNode internal projections and therefore we rely on GeoServer in order to reproject the GetMap outputs

Please check the current code here:
https://github.com/GeoNode/geonode/blob/master/geonode/services/serviceprocessors/wms.py#L252-L323

see https://github.com/GeoNode/geonode/pull/8149


Makefile,Scripts: support Palladium simulation

To add extra Macros when pldm-build, use PLDM_EXTRA_MACRO="..."
To add extra Args when make pldm-run/pldm-debug, use PLDM_EXTRA_ARGS="..."
Use RELEASE_WITH_ASSERT to specify Palladium simulation without Software.

Sure. I'll try to hide internal information.

Better to provide clear interface to specify the required arguments/paths. Only to hide internal paths but external users can still use this repo to run simulation

The scripts may be added later. At that time we should provide a clear interface file which can be user defined for simulation. The only thing external users (and us) need to do is set the user defined paths in this file.


mimelib dependency

Wrong enconding because is (suspect) "mimelib-noiconv":"*", until friday (0.1.3) was another version and now (0.1.4) is broken.

Dang! Thats a huge one :S
Restored mimelib-noiconv to previous state and bumped version to 0.1.5 so npm update should resolve it.


Different algorithms are implemented depending on target pointer width

This crate actually contains two (weak) encryption algorithms, but only conditionally compiles one of the two based on the target's pointer width.
Both 32-bit and 64-bit machines should have access to both algorithm implementations.

The algorithm was same. The 64-bit implementation was applying the algorithm in the group of 8 bytes whereas 32-bit and lower implementation was applying the algorithm on each byte.
Could have been useful for embedded or IOT stuffs, but anyway I have remove other implementations and now only 64-bit version supported.


PromQL editor is crashing after going to the next line and pressing multiple space

Thanos, Prometheus and Golang version used:
Thanos: v0.20.0
What happened:
I started to type an expression then go to the next line and press multiple times space. The PromQL editor is crashing as you can see below in the gif.

What you expected to happen:
The PromQL editor doesn't crash
I compared today the code between Prometheus and Thanos regarding this specific topic and I didn't find what is the diff that would cause that.
It's working fine in Prometheus.

Hi @Nexucis, thanks for reporting this bug. Do you have the experimental editor checkbox enabled in prometheus as well? Also, what version of prometheus did you compare with?
Thanks in advance for the info!

yes I have the checkbox enabled in Prometheus. I tried with the last version (v2.26.0) and also with the prometheus demo: https://prometheus.demo.do.prometheus.io/

ah that's interesting, when I'm running the react app with yarn start, the bug doesn't appear. This is sooooo weird :o

ok so the good thing is the bug isn't related to the PromQL extension. it's only related to codemirror.
The bad thing is I don't really get why the build step would break something. But clearly there is something happening at this moment since when launching the UI through yarn start, nothing wrong is happening with codemirror.

ah it could come on how the assets are built. That's not the same way used in Prometheus and that's the only difference I found between Prometheus and Thanos regarding the build of the UI.

or not ....
I build the react-app and use a static server to serve it and the bug is there. So the problem is really when the react-app is built.
Back to understand and find what is the difference between the build of the react-app in Prometheus and in Thanos


Revert migrating autofill to modern js communication mechanism

Revert "Migrate Autofill to modern javascript communication mechanism (#4360)"
This reverts commit df1f9644d53ab5e0faa450eecc75770af647b2fe.
Revert "Add warning to password management screen for incompatible WebViews (#4406)"
This reverts commit 8aad2b5f4812d5987b063cf0e8d5a9875536a118.
Task/Issue URL: https://app.asana.com/0/0/1207285177763151/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4533  👈
develop

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

Join @CDRussell and the rest of your teammates on  Graphite

Still testing this, but sharing now. This should be:

reverting the big PR which migrates to the new JS comms approach
some small tweaks for the survey which came along afterwards

cc @GioSensation , @cmonfortep, @aitorvs

Closing; see https://github.com/duckduckgo/Android/pull/4536 instead


Section menus for lazy blogger seems broken

Not sure what and when, but it needs some (more) tests to make sure it doesn't happen again.

The menu entries gets URL "/section" should be "/section/", not sure when it happened ...

Hmm ... I guess it never worked 100%, OK never to late to fix.

OK, this was introduced in https://github.com/spf13/hugo/commit/d35d82060fce24533fc29a04a3e341869f196172
Hmm, must read the PRs better.


Error Adding Tina to a Gatsby

Description
Hello,
I'm following the tutorial  Adding Tina to a Gatsby Website and having problems getting it done. I would appreciate some help!
I first ran into this error :
If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
        - install 'path-browserify'

and applied this fix that got me to the actual problem.
Now I use gatsby develop and I get the following error :
Error in function Ee in ./node_modules/tinacms/build/index.js:1
The `cms` prop must be an instance of `TinaCMS`.
./node_modules/tinacms/build/index.js:1

Steps to reproduce
You should be able to copy this repository https://github.com/patbranchaud/gatsby-tina-error
yarn global add gatsby-cli
git clone https://github.com/patbranchaud/gatsby-tina-error
cd gatsby-tina-error
npm install
gatsby develop
Expected result
Starter blog with a pencil to open the TinaCMS editor.
Actual result
Navigate to http://localhost:8000/ and you should see the error.
Environment
Tinacms Package Versions

├──<EMAIL_ADDRESS>

Tools

Tool
Version

browser
Version 92.0.4515.159 (Build officiel) (arm64)

os
MacOS 11.4 (20F71)

node
v14.16.1

npm
7.20.5

I think my problem is similar to #1763
Thank you in advance for your help!

By adding manualInit: true, in gatsby-config.js and
import React from 'react'
import { TinaProvider, TinaCMS } from 'tinacms'
export function wrapRootElement(
    { element }
  ){
    window.tinacms = new TinaCMS({
      enabled: true,
      sidebar: true,
      toolbar: true,
    });
    return <TinaProvider cms={window.tinacms}>{element}</TinaProvider>
  }

to gatsby-browser.js it finally worked
I wonder if the TinaCMS could officially fix this in future :)


Column number support

This is currently needed for precise error messages in both https://github.com/graphql-elixir/graphql and https://github.com/absinthe-graphql/absinthe.

I also miss column number support.

Hmm, is the first character in a line in column 0 or 1? And do you treat tabs as one character or "pad" them out to the next 8th position? Just thinking out loud really.

Don't know if it is still relevant, but I've implemented column number support as this year's Spawnfest project.
Started counting columns at 1 and I've set the default tab size to 8, but left the possibility to configure it to your needs.
The project can be found here. Any feedback is very welcome :D


Feature to programmatically change App launcher Icon.

I'm fairly new to Flutter but have found that it fits most of my design needs for iOS and Android. But, I've been unable to find a way to dynamically change the app icon.

In Swift and Android, you were able to change the app icon from inside the actual app allowing for some pretty neat customization.

Use case
In my app I Integrated multi-theme. I would like to change AppIcon based on user selected Theme (I have different colored icon for Each theme) or Device theme itself.

This was discussed in this issue: fluttercommunity/flutter_launcher_icons#177

@Kishan-Dhankecha
Assuming you are using flutter_launcher_icons plugin, I suggest you to follow-up in the above referred issue to get updates on your issue.
I am closing this from here. If you disagree, write in comments and I'll reopen it.


images to hero

add content and images to hero
check bugs while scrolling as there are visibility issue
code redundancy check
code optimization

Deadline 08-10-2024


Does verbose work?

The verbose parameter, specifically in project_volume_data, doesn't seem to have any effect. e.g.:
surf = project_volume_data(vol, hemi, reg,
                               smooth_fwhm=1, projarg=(.5, .5, 1),
                               verbose=verbose)

Prints (to stderr, based on the Jupyter css color) INFO level log information no matter whether I set verbose to False or "DEBUG".
Do I not understand how to use it, or is this parameter being ignored?

That function is missing the @verbose decorator

Easy fix :) #161


Print Simon Platform

https://drive.google.com/a/ncsu.edu/?tab=wo#folders/0B93g4TjHMS2pZ0NubEFBTWxJZTA

Printed

Forgot to add a mounting hole.


When getting a named worksheet the Dimension defaults to A1:AF2 but the whole range of the sheet is A1:BA2. If I save the work book, it works correctly

hello,
I have an issue when getting a named worksheet the Dimension defaults to A1:AF2 but the whole range of the sheet is A1:BA2. If I save the work book, it works correctly
The following code:
$ExcelFilePath = "C:\Users\<xxx>\code\<xxx>\<xxx>\AllSqlServersV2.xlsx"
$Excel = Open-ExcelPackage -Path $ExcelFilePath
$Excel.Recommended_for_instances.Dimension

Returns this:
Start   : OfficeOpenXml.ExcelCellAddress
End     : OfficeOpenXml.ExcelCellAddress
Table   :
Address : A1:AF2 <=== 👀🛑
IsName  : False
Rows    : 2
Columns : 32 <=== 👀🛑

But if I open the workbook, press enable editing and then ctrl s and run the code again I get the expected result:
Start   : OfficeOpenXml.ExcelCellAddress
End     : OfficeOpenXml.ExcelCellAddress
Table   :
Address : A1:BA2 <=== 👀✅
IsName  : False
Rows    : 2
Columns : 53 <=== 👀✅

Please see this Stack overflow post I posted for all the details:
https://stackoverflow.com/questions/75943288/powershell-module-importexcel-only-returning-up-to-column-af2-when-many-other-co
I have attached the Excel file for you convenience:
AllSqlServersV2 (3).xlsx

Is sounds like it is getting created and those cells may have nulls or empty values. Editing and saving, I think Excel has an option that strips those out when you save and that is why it then has the correct values.

I have received an update and acceptable answer relating to this issue on Stack Overflow here: https://stackoverflow.com/a/75948801/992495
Which contains thorough details of the reason this is happening. I am not an Excel expert (I hardly ever use it) but not sure if it is something you want to look at handling at your end? Maybe not.


NuxtConfig typescript not detecting modules options

Environment

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.2.2
Nitro Version:    2.2.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, i18n
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>@pinia/nuxt
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-ly14ux?file=nuxt.config.ts,package.json,README.md
Describe the bug

Installing this 3 modules seem to trigger the bug, could be one individually (i18n, apollo, pinia)
defineNuxtConfig when we add, for example, i18n options says that those options don't exist inside the NuxtConfig type.

Additional context
https://discord.com/channels/473401852243869706/1077187385667899422
Logs
Argument of type '{ modules: string[]; i18n: { noTypescriptWorkingHere: string; }; }' is not assignable to parameter of type 'NuxtConfig'.
  Object literal may only specify known properties, and 'i18n' does not exist in type 'NuxtConfig'.(2345)

Solution: After upgrading to i18n-edge version the issue dissapeared this may be related with an issue they have with the vue-i18n package. Still, its weird the nuxi prepare is not failling on the reproduction

After creating a new Nuxt application and installing the latest packages, I'm having trouble with TypeScript in "nuxt.config.ts" for "i18n". The command "pnpm dlx nuxi prepare" doesn't help. Deleting the ".nuxt" directory doesn't help either. For object literals, you can only specify known properties, and the "i18n" property does not exist in type "InputConfig<NuxtConfig, ConfigLayerMeta>".
nuxt: 3.10.2,
nuxtjs/i18n: 8.1.1
Updating to edge did not solve the problem.

@martio This issue was closed almost a year ago. Would you create a new issue with a reproduction? 🙏

It started working and I don't know how I did it. It seems to be OK. Sorry for the confusion :confounded:

After creating a new Nuxt application and installing the latest packages, I'm having trouble with TypeScript in "nuxt.config.ts" for "i18n". The command "pnpm dlx nuxi prepare" doesn't help. Deleting the ".nuxt" directory doesn't help either. For object literals, you can only specify known properties, and the "i18n" property does not exist in type "InputConfig<NuxtConfig, ConfigLayerMeta>".
nuxt: 3.10.2, nuxtjs/i18n: 8.1.1
Updating to edge did not solve the problem.

I recently created a new project and this error message appeared after adding i18n for the first time, but after running npm run dev once, this error will disappear. This seems to be a problem with type checking.

It’s expected you need to run dev server or nuxi prepare to update the types.


Petty automatic updates

Changes
When running tests, linting, etc, some files are automatically modified by tooling. Rather than locally reverting them over and over or just ignoring them, I figured I'd make a PR to roll them up.
Checklist

[ ] An issue to be fixed by this PR is listed above.
[ ] New tests are added to ensure new features are working. End-to-end tests are usually in the ./frb_example/pure_dart example, more specifically, rust/src/api.rs and dart/lib/main.dart.
[ ] The code generator is run and the code is formatted (via just precommit).
[ ] If this PR adds/changes features, documentations (in the ./book folder) are updated.
[ ] CI is passing.

Remark for PR creator

Justfile is a task runner for the command line interface that allows you to run shell commands from a file named justfile in your project directory. You can use Justfile after installing it. Note that commands written in justfile of this repository are expected to be run in bash, not cmd or powershell. Running just ... commands in cmd or powershell will produce errors as the syntax is not compatible. On Windows, you can use git bash if you have Git installed.
If fzyzcjy does not reply for a few days, maybe he just did not see it, so please ping him.

@fzyzcjy It looks like pub get is coming to a different conclusion on my computer than it is in CI? Any idea what's going on there?

Hmm what's your local flutter version? (flutter --version). And check the version in CI.
Btw would be great to setup fvm, so everyone is in the same version automatically

Ha it is 0 line of change now!

Ha it is 0 line of change now!

Yeah, didn't know if you want the chmod +x. If not this can be closed.

Oh I did not realize that since I just look at the github page :) If there is this change, surely it can be merged.

Oh I see, it is there ;)
(Btw I guess github should somehow notify this in the headline, e.g. "+2files-2files")


Exec tachikoma update<PHONE_NUMBER>3321

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

great @pazjacket


Added a white helm logo for dark mode

as asked in https://github.com/meshery/meshery/issues/7506
Notes for Reviewers
This PR fixes #7506
Signed commits

[x] Yes, I signed my commits.

Thanks, @souravpy. Will you confirm that this has been followed? https://docs.meshery.io/project/contributing/contributing-ui#static-files-icons-and-images

Thank you @Chadha93 and @leecalcote for the feedback I'm looking right into it 👌

I made the prescribed logo but failed to use the icon with the dark mode logic, Ive come up with a few solutions:

help me with the logic, how to do it
or merge the logo, and create a new good first issue that has the dark mode logic part
I'm eager to work on the issue if helped out with logic @leecalcote , @Chadha93

hi @souravpy if you go through other logos which are present there is a dark mode logic applied to all of them so you can refer those and do changes accordingly

hi @souravpy if you go through other logos which are present there is a dark mode logic applied to all of them so you can refer those and do changes accordingly

I've made the logo, let's figure out the logic, keep me updated if you learn something new about it

Its, Sourav Biswal

hi @souravpy if you go through other logos which are present there is a dark mode logic applied to all of them so you can refer those and do changes accordingly

I've made the logo, let's figure out the logic, keep me updated if you learn something new about it

i surely will get back to you, please mention your slack username it would be convenient to keep you updated on it there.

It's Sourav Biswal, let's connect 👍

Sure, thank you @vishalvivekm

Hey @souravpy you take reference from this on SVG color change on theme change

Really thanks @duckling69 , checking it out 😃

Does this work now?

@souravpy you don't really have to make new a logo you just need to update the color of SVG on theme change

Does this work now?

@souravpy you don't really have to make new a logo you just need to update the color of SVG on theme change

How can I?

Does this work now?

@souravpy you don't really have to make new a logo you just need to update the color of SVG on theme change

How can I?

Like its been done here

you can give the parent div some classname and target img tag in it and change it's fill color to something like
props => props.theme.blue0f1689Towhite
correct me if i'm wrong here @vishalvivekm

This bug has been an issue for too long. @duckling69 if you can get this done correctly, please do.

Does this work now?

@souravpy you don't really have to make new a logo you just need to update the color of SVG on theme change

How can I?

 Like its been done here  you can give the parent div some classname and target img tag in it and change it's fill color to something like props => props.theme.blue0f1689Towhite
correct me if i'm wrong here @vishalvivekm

@duckling69 it might work this way.

Getting this done asap


Is it possible to rename the Malduino

Hey so I just bought the Malduino and everytime I plug it into a computer it says that a Malduino elite is connected.
Is it possible to rename it?

+1 I'd also like to know of this, did you ever come up with a solution @CarsterX ?


xtensa: make it work with DTLB misses during interrupt handling

If there is a data TLB misses during interrupt handling, the double exception vector will be triggered for the miss and the EXCCAUSE overwritten. The DTLB miss will be handled and execution returned to the original vector code. Because of this, the EXCCAUSE read in the C handler thus is not the one that triggered the original vector code (for example, level-1 interrupt). So stash the EXCCAUSE and use it in this scenario such that we can process it correctly.
Note that the moving of assembly in the vector code is due to space constraint in the vector area. Or else it would be too large to fit there.

Also, would be good to have a test case for this.  Might be as simple as "flush the TLB and irq_offload()".  If EXCCAUSE gets clobbered by the resulting entry code then the offload callback would presumably never happen.  I'm specifically thinking about this in the context of call0, which will want regression tests to look at the same kinds of failures.

Hm, that's a good catch. Wouldn't it make more sense to handle this on the other side, though? Cache the "original" EXCCAUSE in the level 1 handler in assembly before entry to the handler (while running vector code in pinned a TLB page) and stash it in a SR (or just in the CPU struct, gen_zsr.py is going to start running out of registers soon).
Basically, as I'm understanding it: the value in EXCCAUSE can't ever be trusted in general C code because it's subject to being clobbered at any given moment by a TLB refill. And that can still happen here, in the instructions before this fixup. So close the gap before entry to general C code?

The EXCCAUSE is stashed at beginning of the user exception vector (aka. _Level1RealVector). It is not the earliest due to space constraint, but should be at a point where there is no memory access (and thus won't generate TLB misses).
I think you see the checking of is_dblexc and assumed it is being handled as a double exception. Actually, is_dblexc being true is a side effect of handling DTLB miss in the double exception vector as DEPC is not cleared in that case (while other causes would go through the C handler and DEPC cleared before the end). So going in the C handler, as DEPC is not zero and it assumes it is dealing with a double exception. Though it turns out to be a good way to catch this exact scenario: DEPC != 0 and (fake) EXCCAUSE == DTLB miss.

I will try to create a test for this.

I have modified the flow a bit so that EXCCAUSE_DTLB_MISS would never be propagated to the C handler under normal circumstances. If we see that in C handler, it means we are hitting this scenario. After unmasking EXCM, any TLB misses would be handled in the early vector code and will never be saved in ZSR_EXCCAUSE_SAVE.

Further tweaking it to avoid using another scratch register. And also stash DEPC for use in C handler (similar to stashing EXCCAUSE). This version should be a lot simpler, but might be a bit more confusing.

Tighten the stashing code a bit by using XSR.

This is actually not really enough, and I am working on another set of patches. So closing this one.


(maint) Remove rubygems_version from gemspec.

Removing rubygems_version from gemspec as it breaks under the most
recently released version of bundler.
From the documentation this should not be set and is instead generated
by rubygems at packaging.

Hmm, should probably target this at stable.


Make it easier to find the global options if you're looking at specific pub build help options

I didn't know there was a --verbose. pub build --help does not show it. Can we add it? It could help in debugging:
sethladd:~/tmp/speed$ pub build --help
Apply transformers to build a package.
Usage: pub build [options]
-h, --help    Print usage information for this command.
    --mode    Mode to run transformers in.
              (defaults to "release")
    --all     Build all buildable directories.

This issue has been moved to dart-lang/pub#902.


HCE mode

I'm just wondering if there is a way to perform an Hosted Card Emulation in Android (http://developer.android.com/guide/topics/connectivity/nfc/hce.html) using the cordova plugin.
PS: My projects with Reader and P2P mode works just fine in 4.x apps i've developed using your plugin. I've also emulated a pseudo-HCE via P2P share/unshare functions and they are fairly good for simple services unless the boaring "push to send" message that can't be avoided progamatically to share my "legacy" NDEF record type.
Bye from Italy

I love this plugin, but also hopes that HCE will be implemented. I´ve got a couple of apps which communicate with each other and are "accepted" to send data over and over. But a.t.m. the sender needs to tap the screen which is unfortunate.

Also looking for this feature here. Currently, POS terminals (e.g. Verifone) only recognize HCE. Has there been any movement on implementing this?
Plug-in does work great like many others have said. My POC and beta testing has been flawless, but my next release relies on HCE. Much appreciated!

@billygrossman I don't have near term plans to add HCE to this plugin. When a client needs HCE I'll need to evaluate if code belongs here or in a separate plugin.

I've written a new plugin that supports HCE https://github.com/don/cordova-plugin-hce
/cc @mork80 @troyblank @tsukasa1989 @billygrossman

Great Don,
I'll test it as soon as possible.
Il lunedì 7 dicembre 2015, Don Coleman<EMAIL_ADDRESS>ha
scritto:

Closed #122 https://github.com/chariotsolutions/phonegap-nfc/issues/122.
—
Reply to this email directly or view it on GitHub
https://github.com/chariotsolutions/phonegap-nfc/issues/122#event-484613417
.

Hi,
We have been trying to use the plugin but the application always ends in the "Loyalty cards" part of Android NFC applications and not in the "Payment cards" part ...
Any idea about what causes this would be more than welcome.
Thanks for help

Note sure what you mean by 'application always ends in the "Loyalty cards" part of Android NFC applications and not in the "Payment cards" part'.
This plugin lets you read, write, send, and receive NDEF messages.
If you want to loyalty cards with HCE try https://github.com/don/cordova-plugin-hce


[SPARK-31320] fix release script for 3.0.0

What changes were proposed in this pull request?

The release script stops working after https://github.com/apache/spark/commit/d5865493ae71e6369e9f3350dd7e694afcf57298 , as we require mkdocs 1.0.0.
This PR upgrades mkdocs from <IP_ADDRESS> to 1.0.4. To do that ruby is also upgraded to 2.5.
This PR also fixes some small issues.
Why are the changes needed?

to make RC
Does this PR introduce any user-facing change?

no
How was this patch tested?

tested by 3.0.0-rc1

cc @dongjoon-hyun @HyukjinKwon @nchammas

Note that we should forward port this to the master branch. It was done at branch-3.0 as the policy is to use the script of the corresponding branch to do the RC.

Test build #120663 has started for PR 28088 at commit a2c711b.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25362/
Test PASSed.

cc @rxin and @gatorsmile

Test build #120663 has finished for PR 28088 at commit a2c711b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120663/
Test PASSed.

Merged to master and branch-3.0.

Merged to master and branch-3.0.


Added the teachers email domain for SintLucas.

Added the domain for teachers of SintLucas. The students already had the domain sintlucasedu.nl added but teachers have emails that use the sintlucas.nl domain.

@davidjonas merged, thank you.


Having a sass-only option for Foundation

I am EmberJS Web Developer and using Foundation for Apps on one of my prototype apps successfully so far.
I don't really need any of the Angular specific stuff, i.e. components and animations, since ember has a lot of this stuff by itself but it would be great to still get the great grid system, helper classes, menubar, fonts etc.
It is quite easy to customise the needed components through https://github.com/zurb/foundation-apps/blob/master/scss/foundation.scss. But it would be great to get a bower version that is angular-dependency free.

You can still install the package and just ignore everything in the js folder. If you're using a tool like wiredep, you can configure it to ignore all of the JavaScript that our library depends on.
To be sure, Foundation for Apps has quite a few dependencies, so it is sort of lame that you have to install seven other things you probably won't use. (Although FastClick and the viewport units buggyfill are both nice.) If you check your dependencies into version control, you can ignore them in .gitignore, and if you don't, simply ignoring the folders is easy enough.
Bower 1.4 might add the ability to ignore dependencies, although there's been no word on it recently. Here's the pull request: bower/bower#1394


add support for some of the FourLetter words

I have a need for polling the Zookeeper instance with some of the four-letter words. In this PR te following words are implemneted with tests:

srvr
cons
ruok

srvr get some stats about the server (connections, latencies, leader/follower mode, etc.)
cons gets detailed information about the individual connections and their sessions
ruok is actually mostly useless, but specifies whether the server has returned imok when prompted with ruok
I'm not sold on the name of the public API functions, FLWCons(), and would happily change them to something better.

Really minor doc issues but otherwise looks great. Thanks!

@samuel wow, those are really lame typos. Sorry about not catching them previously.
I've pushed a single commit to address the feedback. Let me know if you need anything else.

No worries. Sorry to be picky. Looks good.


Fix tabs toolbar content alignment

Pull Request
🤨 Rationale
SLE bug: Nimble | nimble-tabs-toolbar | alignment of the child elements has been altered.
👩💻 Implementation
Just added styling that will expand the end slot to fill the rest of the space of the Tabs width.
🧪 Testing
There is a Chromatic test in place that is already checking this case, but I must have glossed over that change when examining it for the scrollable tabs submission.
✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

Bypassing Jesse and marking autocomplete for trivial change and updated stories look good


added getAlbum function

Hi @scottmfisher :wave:.
Many thanks for your pull request! I have merged it and published your changes in 1.1.0.


[Testing] Unbreak minimal Swift builds

#36975 broke minimal Swift builds.

@swift-ci please smoke test

@swift-ci please smoke test


⚠ Roblox Devforum has degraded performance

In f478ddc, Roblox Devforum (https://devforum.roblox.com) experienced degraded performance:

HTTP code: 504
Response time: 11417 ms

Resolved: Roblox Devforum performance has improved in 44666fa.


Official Browserify plugin ?

Since any valid JS file is supposed to be a valid TS file too it should be possible to use a standard babelified webapp project and just switch it to use TS (e.g using tsify). Sadly that is not possible right now   since there are some issues on requiring/importing dependencies and actually getting TS to emit anything (in a DI reliant project at least).
I think it would be helpful if the TS team would devote some time to setup official documentation similar or even extended to what the opensource babeljs team has done (https://babeljs.io/docs/setup/) with enough starters how to migrate their existing projects to TS. An official browserify plugin might also be helpful.
Specifically just exchanging babelify to tsify doesnt work right now even though both implement the ES6 features used (of course if one doesnt implement a specific feature proposed that wouldnt work).

Definitely hear you on the suggestions for more docs on migration strategies.
What would a browserify plugin actually do? Just run tsc for you with the settings from the local tsconfig? The babelify plugin seems convenient but not really unblocking anything unless I'm misunderstanding how it works. For example we use browserify ourselves to package up our test suite into something suitable for running the browser. We just run tsc as normal to generate some js and then package it with browserify as you normally would for any set of js files.

We would want a TS plugin to actually translate the files on the fly in the same fashion as babelify does it without generating intermediate files. With intermediary files there are always instances were devs accidentally edit the wrong file.
basically it should be possible to add typescriptify or whatever to the pipeline and allow for added .ts files anywhere. Those files should be able to simply import other files even when those are normal e.g commonjs javascript files (with module.export = ...) as well as be importable from other normal javascript files using require.
It should be possible to import another module with sideeffects without using the returned variable etc (i read this should be possible now did not get it running though yet in our project setup)
It should be possible to still use require for other purposes (e.g. css/html via cssify or stringify etc) (which i think wouldnt be a problem provided the declaration file is correct but that should be documented in the readme of such plugin)

@matthiasg, how about https://github.com/Microsoft/TypeScript/wiki/Integrating-with-Build-Tools#browserify? can you let us know what is missing, and how can we make it better?

i am on vacation now so i wont write a lot or re-check, but last time i tried using tsify etc they all failed on me. They work when i start from scratch but not when trying to partially start with ts inside a larger existing project. with babelify there was no issue at all. i just added it and was able to use es6/7 features everywhere i wanted with full compatibility to existing es5 code.

I couldnt just rename a file to .ts and re-build. it started complaining about missing declarations which goes against what anders promised (every valid js file is a valid ts file)
after declaring the globals (e.g in the config file i hear but we did it in the file itself) files with sideeffects (angular) didnt work (when used from another ts file they where compiled out) . i wanted to re-check using just import 'path'
importing without specifying the ts exension didnt work (or i was overtired, because sometimes i thought it did work)
importing a ts file from a non ts file didnt work
using async/await did not work (of course, not part of ts) but no clear understanding whether this will ever be possible and how to set that up (e.g parse it but expect another generator such as babelify to pick that up later)

@thanks @matthiasg for the input. looks like we need a sample here, at least to discover integration pains.
//CC @smrq from tsify.

I would like to have an example of browserify + tsify + babelify with source maps :)

PRs to https://github.com/Microsoft/TypeScriptSamples are always welcomed

@DanielRosenwasser is working on a sample here.

This issue was moved to Microsoft/TypeScript-Handbook#165


Update versions of smoke tested plugins

@bot-gradle test AST

I've triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

I've triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you.


Physics Hands - Improved finger wrapping and better heuristic flow

Summary
Needs #1397 to be merged first.

Dynamically adjusts the fingers when there is enough space between them and the object

There are some issues with finger jitter every now and then but the overall result is much better
Two handed swapping no longer bumps outwards due to this
You can now move fingers off of objects, adjust your finger, and then retouch, without letting go of the whole object

Adds distance calculations to each bone
Moves all of the heuristic and helper steps into WaitForFixedUpdate which occurs after the physics simulation, meaning that the calculations are correct before update.
Adds per finger pinch distance to hand utils.
Adjusts physics grasp helper to work better with any type of two finger pinch.
Reverts more spherical -> revolute joint changes introduced in #1378

These introduced more issues than they solved, primarily when grabbing objects

Before / After vids of finger limiting.
https://user-images.githubusercontent.com/6281246/218797196-8b77f56a-8309-4123-b900-57d1a1dc89d3.mp4
https://user-images.githubusercontent.com/6281246/218797336-acf1799e-3d0e-4e51-ac62-b6dd9a568097.mp4
Contributor Tasks
These tasks are for the merge request creator to tick off when creating a merge request.

[ ] Pair review with a member of the QA team.
[x] Add any release testing considerations to the MR for the next release.
[x] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.
[x] If this MR closes a Jira issue, make sure the fix version on the JIRA issue is set to the correct one.

Reviewer Tasks
Add any instructions or tasks for the reviewer such as specific test considerations before this can be merged.
Use emojis in review threads to communicate intent and help contributors.

[x] Code reviewed.
[x] Non-code assets e.g. Unity assets/scenes reviewed.
[x] Checked and agree with release testing considerations added to MR for the next release.

Closes JIRA Issue
If this MR closes any JIRA issues list them below in the form Closes PROJECT-#

@rorygames
Based on the videos there's a marked improvement in finger wrapping although it'd be good to see how this works with curved objects too.
If you can grab a video and post it i'd be happy with that otherwise I'll take a look after lunch.

@Greg-UL heres a video of testing with curved surfaces, it feels very good
https://user-images.githubusercontent.com/60962475/220920778-e3fe1419-b545-43f0-b0b2-4b7b0b8d099a.mp4

Cool, thanks Matt.
I'm happy with this. I'll start building on the Phys Hands tests on Zephyr from now on.


[Improvement] splice() support

I tested the performance of reproxy-rs with iperf3 and proxychains-ng and it reaches ~12000 mbps in my system. On the other hand, testing a socks5 server (3proxy) that uses splice() I get about 25000 mbps.
If implemented in redproxy-rd it would double its performance.
This is my suggestion.
There are some packages here in Github implementing splice() (it could serve as a basis):
https://github.com/ArniDagur/InstantTee
https://github.com/mre/fcat

Thanks for your advice, I think the main troubles are:

splice() is linux only
it can not work with TLS enabled sockets

But I think there could be a way to overcome these problems by falling back to normal copying functions.
I'll do some more research later.

I think this feature is very relevant as redproxy-rs is designed mainly to provide Linux transparent proxies, in Windows should be useful when serving QUIC UDP proxies and forward ports.
But doubling redproxy-rs performance would be very welcomed.


Attachment 3847 is broken

Stucks at ~98%
curl reproducer
curl -N 'http://lms.nthu.edu.tw/sys/read_attach.php?id=3847' > /dev/null

Belongs to http://lms.nthu.edu.tw/course.php?courseID=98&f=doc&cid=5246

Looks like the HTTPS endpoint is not broken.
The following doesn't fail:
curl -N 'https://lms.nthu.edu.tw/sys/read_attach.php?id=3847' > /dev/null


Generate Report to pdf or csv

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature
🔖 Feature description
a tools from ui that can generate report uptime to pdf or csv
✔ Solution
to make easy when we need report
❓ Alternatives
No response
📝 Additional Context
No response

Hey! I want to do this. Before that I would like to know how to update the docker image with our changes in local. Could you help me how to do that?

I think this is a duplicate of #366
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^


Mistyped features in feature-expressions evaluate as true

com.rmn.version-qualified.qualifiers.feature/eval-feature-expr walks a feature expression and replaces features with true or false, then evals the expression. If a (for example) keyword is found in the expression which is not a known-feature?, it will not be replaced. The effect of this is that when evaling the expression, the keyword will basically evaluate as true in boolean logic expressions.
In this case, we should probably warn the user that we found a keyword but it was not a known feature, or just error out completely. The latter would cause problems if they legitimately wanted to put a keyword in the expression but did not mean it to refer to a version.
We should be cognizant that not all feature names are keywords
Example expression
(and :feature1 (not :faeture2))

Assuming that :faeture2 is a typo of :feature2, this will expression will always be false

In these expressions, it may be safe to assume that the first form in a list is always some boolean operator, and the rest of the non-list forms refer to versions -- this could be keywords, symbols, strings, etc..
Perhaps we should assert that non-list, non-first-element-of-a-list forms are all known-feature? by default, and then allow the user to add metadata to the feature-expression to turn off this check.
^:com.rmn.version-qualified.qualifiers.feature/skip-known-feature-check
(and :feature1 (not :faeture2))


[task][Widget] Set the bg color of text widget properly in auto layout mode

This was a limitation during Auto height implementation where the bg color only applues to the text size and not thru the entire boundary boxes of the widget
this can be replicated in production as well.
Creating this task to discuss if we should fix this or not

@kamakshibhat-appsmith This is what I see now. It doesn't feel like an issue to me right now.

the problem looks prominent with single line text only. do you think we should proceed with this ? @aswathkk

This is due to the minHeight defined for text widget is being 40px where as the line height of the text is being 20px.
@shastry-gg What should we do here?

@kamakshibhat-appsmith This got fixed in the linked PR.


BIGTOP-3310: URL of maven and ant package list page is changed

bigtop_toolchain uses packages list page hosted on
https://www.apache.org/dist/ to detect latest version of maven and ant.
This url has been moved to https://downloads.apache.org/ and latest_*_binary
functions need to be updated to reflect this.
To adapt to future URL change,'-L' option is added too.
Change-Id: Ia732be3c79f5d54b3db0eaa010adbfc8ff0d7395
Signed-off-by: Jun He<EMAIL_ADDRESS>

Verified with local bigtop-slaves image building on both x86 and arm64.


"An unexpected error was caught" when calling async callback

this code will trigger:
    require('vows').describe('vows').addBatch({
    	'foo' : {
    		topic : function(){
		this.callback(1)
    		}
    		, 'bar' : function(x){
    			assert.equal(x, 1)
    		}

    	}
    }).run()

gives:
    $ node test.js
    ✗

      foo
        ✗ bar
          » An unexpected error was caught: 1
    ✗ Errored » 1 errored (0.004s)

Hello
Not sure this will help you, but I just ran into the same issue. It seems that the callback in some or all cases interprets the first argument as an error. I think if you try
this.callback(null,1)
it might work
Perhaps it helps
Peter

Yeah. Confirmed here in the tests. Someone should update the documentation on the vows website. Very misleading.


Update findp, listp and link in User guide

Codecov Report

Merging #109 (64e0a54) into master (d80f865) will decrease coverage by 0.32%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #109      +/-   ##
============================================
- Coverage     54.56%   54.23%   -0.33%
+ Complexity      456      452       -4
============================================
  Files            92       92
  Lines          1926     1934       +8
  Branches        225      227       +2
============================================
- Hits           1051     1049       -2
- Misses          810      820      +10
  Partials         65       65

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/AddressBook.java
46.49% <0.00%> (-3.51%)
:arrow_down:

...ava/seedu/address/model/internship/Internship.java
28.57% <0.00%> (-2.39%)
:arrow_down:

...address/model/internship/UniqueInternshipList.java
43.47% <0.00%> (-2.18%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

looks good


Failing for even a minimal attempt

import { StatusBar } from 'expo-status-bar';
import { FlatList, StyleSheet, Text, TextInput, View } from 'react-native';
import { KeyboardProvider, KeyboardAwareScrollView } from "react-native-keyboard-controller";

const data = Array.from({ length: 100 }).map(_ => "Lorem ipsum dolor sit amet, consectetur adipisicing elit. Alias, eveniet.")

export default function App() {
  return <KeyboardProvider>
    <View style={{ flex: 1 }}>
      <FlatList
        data={data}
        renderItem={({ item }) => <Text>{item}</Text>}
        renderScrollComponent={props => <KeyboardAwareScrollView {...props} />}
      />
      <TextInput />
    </View>
  </KeyboardProvider>
}

I think it's because you embed your TextInput outside of KeyboardAwareScrollView, right?
In your case I believe you should use KeyboardAvoidingView instead of View and it should work.
Let me know if it doesn't 🙏

Yes, if the TextInput are inside KeyboardAwareScrollView, it works perfectly fine. For my case, I have no other choice but to use a KeyboardAvoidingView

@useEffects you may also consider using the KeyboardStickyView component for sticky TextInput.
Or if you are building a chat-like app, then you can clone an example app to see advanced examples on how to use library primitives to deliver the best possible experience to the user (like interactive keyboard or just to see how to build simple UI for chat-like apps using functionality of this library) 😊


Update sql-database-elastic-scale-get-started.md

Hi @TyNev, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


feat: date range filter for questions

New Requirement: Providing user an option in filters section on Questions list page to filter Questions asked between specific date range.
I am ready to work on this feature if you think this is good to have feature.

Hey, sounds like a good idea! If you come up with a PR, I am more than happy to welcome contributions!

Working on it, attached design screenshots. Please let us know in case any concern.

@kedaroh-bh looks very nice, thanks!

Closing this as it's merged and released


Update README.md

Link to working GH action code.
I think this would be very helpful for people.

Dude Yoast is literally a extremely popular WordPress plugin. Add a line of something, why would it be confusing?  Every PHP coder knows what WP is and can still look at the code and copy pasta it to have a great starting point for a GH workflow ...
Just trying to help. I guess I won't next time.

@nextgenthemes Please mind your manners. Your comment is offensive and does not address the concerns I raised. This kind of behaviour is not acceptable here.


Inconsistent Reporting of Vulnerable Certs

Hi there, I've noticed an inconsistency in the reporting of vulnerable certs.
When using certipy find -enabled -vulnerable, certificates are only reported as vulnerable if the account used to check has enrollment rights. This differs to the provided BloodHound custom queries which will report ALL certs that are technically vulnerable even if not (in my opinion) usefully exploitable aka only DA/EA/DC accounts have enrollment rights.
I think it would be useful to update the find command to include reporting certificates as vulnerable for non DA/EA/DC accounts especially something like Domain Computers.
I can make the changes and submit a PR. Any thoughts?
Here I have an example of a cert that is vuln to ESC1 via Domain Computers but is not reported as such unless bloodhound is used.

If I interpret the code right, vulnerable templates where domain computers have enrollment rights are only reported as vulnerable by the Python tool if the machine account quota is positive. See: https://github.com/ly4k/Certipy/blob/main/certipy/lib/ldap.py#L357
And that's true in the sense that you first need to compromise one computer. However, that's often not a big hurdle. Besides, it represents a clear escalation path from tier 2 to tier 0, so there is value in reporting it.
Perhaps an argument like --ignore-maq or so would make sense? Or report any such templates where users other than domain admins/enterprise admins can enroll? Or maybe introduce some Possibly vulnerable flag?
Then again, these kind of almost-possible escalation paths are hard to determine and would be much easier to make apparent in BloodHound on a case-by-case basis by the user.


Post Visibility Preference seems to be out of sync

Describe the bug
I have two Mastodon account : one that is private and has private post visibility enabled as default and the other one is public and has public post visibility enabled.
Weirdly, on phanpy.social and dev.phanpy.social, I have a bug that is bothering me a lot : When I switch to my private account, the preferences of the public account are applied, and when I switch to the public account, this is the preferences of the private account that are applied.
I have checked it times and times again. I have three Phanpy icons on my homescreen, Phanpy.social, Dev and a local instance. I can't seem to reproduce it on my local dev env (of course). I was checking the code and according to settings.jsx:46, there may be a caching issue with the endpoint.
This issue caused me to post stuff in public that wasn't meant to and I fear I'm not alone.
Also, this issue is mainly for tracking, I'm going to check what's happening and I'm gonna try to fix it. :)
To Reproduce
Get two account on the same instance with the supplied setup discussed above.
Use it in an iOS PWA.
Add both account to Phanpy.
Switch between accounts.
Expected behavior
The right preference of the account should show up.
Smartphone (please complete the following information):

Device: iPhone 15 Pro Max
OS: iOS 17.5.1
Browser Safari
Version : latest (sorry I'm not sure how to check)

Additional context
I did not reproduced it on Firefox Desktop but I did reproduced it on Safari Desktop.

@AdamasFR in your reproduction steps, how do you know that the post visibility pref is wrong? Open Settings and check 'Default visibility' setting?

I did not reproduced it on Firefox Desktop but I did reproduced it on Safari Desktop.

If it's browser-specific, could be some race condition in the code 🤔 Will need to investigate.

@cheeaun No, I just go directly to posting and I look at the globe or the lock! And I also checked the preference json in Safari's Dev panel, it was also wrong 🤔

This issue has been fixed, I can't reproduce it on iOS 18.0.1 with Phanpy 2024.10.15.e3df9ff


Support WebSockets

I think it would be nice, if this adapter would support websockets that can be handled from within a sveltekit app.
Maybe with the new filestructure, we can use routes/ws/+websocket.js files.
I guess we would need to create a vite plugin, to support websockets in dev mode.
How a +websocket.js file could look like:
// routes/example/+websocket.js
export function OPEN({ ws }: { ws: WebSocket }) {
}

export function MESSAGE({ ws, message, isBinary }: { ws: WebSocket; message: ArrayBuffer; isBinary: boolean }) {
}

export function CLOSE({ ws, code, message }: { ws: WebSocket; code: number; message: ArrayBuffer }) {
}

OR a default export of the WebSocketBehavior type
// routes/example/+websocket.js
/** @type import('uWebSocket').WebSocketBehavior */
export default {
  open(ws) {},
  message(ws, message, isBinary) {},
  close(ws, code, message) {},
};

But it would be good to have the app available in these functions as well, to publish a message. Or maybe just a publish function that is passed as parameter to these functions.

Yes, this feature is already planned but before I focus on implementing additional features I wan't to make sure everything already implemented works nice and smooth. This is still in Preview/Alpha stage and although it mostly works there are still some significant bugs/not implemented behavior.
For example I'm currently working on POST/PUT/DELETE/etc. requests as we don't support them right now. It's challenging implementing these kinds of features without dropping the performance gain due to how sveltekit exposes itself to adapters.
Anyhow it's planned and will be included before we hit an release candidate! :)

Okay. I thought all features are implemented already.


Black linter

Added black as a linter and reformatted the existing code.

Looks good, let's merge!


QG 4 checks Release 3.2

QG checks
Please keep this issue open until QG 3.2 is concluded and will be managed by the Issue Creator!
We will inform you about finding and proposals in separated issues, this issue here is for the Overview of the Checks!
Product Name: Digital Product Pass
Helm Chart Version:
App Version:
QG5 Approval: yes/no
Check of Tractus-X Release Guidelines
This QG x Check is depending on the mandatory information from our current Release Guidelines.
TRG 1 Documentation

[x] TRG 1.01 appropriate README.md
[x] TRG 1.02 appropriate INSTALL.md
[x] TRG 1.03 appropriate CHANGELOG.md

TRG 2 Git

[x] TRG 2.01 default branch is named main

[x] TRG 2.03 repository structure

Checks within TRG 2.03

[x] TRG 2.03 /docs directory contains detailed product related documentation for the Tractus-X product
[x] TRG 2.03 /charts directory contains the Helm chart for the Tractus-X product IF available
[x] TRG 2.03 AUTHORS.md file (optional) (TRG 2.03)
[x] TRG 2.03 CODE_OF_CONDUCT.md file (TRG 2.03)
[x] TRG 2.03 CONTRIBUTING.md file (TRG 2.03)
[x] TRG 2.03 DEPENDENCIES file(s) with up to date content (Dash tool generated) (TRG 2.03)
[x] TRG 2.03 LICENSE file (TRG 2.03)
[x] TRG 2.03 NOTICE.md file (TRG 2.03)
[x] TRG 2.03 SECURITY.md file (TRG 2.03)

[x] TRG 2.04 Leading product repository

Checks within TRG 2.04

[x] TRG 2.04 repository name must be productname without prefix or suffix
[x] TRG 2.04 should contain the release
[x] TRG 2.04 references/urls to the product's other repositories
[x] TRG 2.04 might contain product helm chart(s)
[x] TRG 2.04 README.md: contains the urls for the underlying applications

[x] TRG 2.05 .tractusx metafile in a proper format

TRG 3 Kubernetes

[x] TRG 3.02 PersistentVolume and PersistentVolumeClaim is used when needed

TRG 4 Container

[x] TRG 4.01 semantic versioning and tagging

[x] TRG 4.02 top level README.md file, that contains information about the used base image

[x] TRG 4.03 Image has USER command and Non Root Container

Checks within TRG 4.03

[x] TRG 4.03 deployment.yaml has runAsUser and allowPrivilegeEscalation: false properly set

[x] TRG 4.05 released image must be place DockerHub as mandatory container registry; remove GHCR references

[x] TRG 4.06 Notice File for DockerHub has all necessary information

Checks within TRG 4.06

[x] TRG 4.06 Link to the source of your base image (Container registry and GitHub if available)
[x] TRG 4.06 Link to your product image on DockerHub
[x] TRG 4.06 Link to your repository on GitHub
[x] TRG 4.06 Direct link to the Dockerfile used to build your image
[x] TRG 4.06 Link to LICENCE file in your repo as Project License (make clear, that this is the PROJECT licence, not an image license

TRG 5 Helm

[ ] TRG 5.01 Helm chart must be released

Checks within TRG 5.01

[x] TRG 5.01 appropriate semantic versioning for version and appVersion has to be used in Chart.yaml
[ ] TRG 5.01 must not contain any environment specific values-xyz.yaml
[ ] TRG 5.01 values.yaml file must contain proper default values/placeholders
[ ] TRG 5.01 No hostname provided for ingress
[ ] TRG 5.01 Ingress is disabled
[ ] TRG 5.01 No references to any secret engine service (e.g.: Hashicorp Vault)
[ ] TRG 5.01 Dependencies should be prefixed with the nameOverride and/or fullnameOverride properties
[ ] TRG 5.01 Image tag is set to the Chart.yaml appVersion property
[ ] TRG 5.01 must be deployable to any environment without overwriting default values with a simple helm install command
[ ] TRG 5.01 dependencies have to be declared in Chart.yaml NOT requirements.yml

[ ] TRG 5.02 Helm chart location in /charts directory and correct structure

Checks within TRG 5.02

[ ] TRG 5.02 each file must contain the Apache 2.0 Licence
[ ] TRG 5.02 latest tag is not used in helm chart be default

charts/
    chartNameA/
      Chart.yaml
      ...
    chartNameB/
      Chart.yaml
      ...
AUTHORS.md
DEPENDENCIES.md
LICENCE
README.md

[ ] TRG 5.04 CPU and memory limits and requests are properly set

[ ] TRG 5.06 application must be configurable through the Helm chart

[ ] TRG 5.07 dependencies are present in the Chart.yaml they are properly configured

[ ] TRG 5.08 a product has a single deployable helm chart that contains all components

Checks within TRG 5.08

[ ] TRG 5.08 name of the Chart should be just the product-name without prefix or suffix
[ ] TRG 5.08 values file should contain all available variables (even from subcharts) with default values and comments about what they do
[ ] TRG 5.08 helm install command should successfully install the chart to any supported Kubernetes version cluster (without overwriting default values)
[ ] TRG 5.08 helm test runs without errors

[ ] TRG 5.09 Helm Test running properly

Checks within TRG 5.09

[ ] TRG 5.09 A GitHub action exist which builds or uses the helm chart which gets released
[ ] TRG 5.09 The GitHub action can be triggered manually through Github WebUI manually running a workflow
[ ] TRG 5.09 Helm test verifies that the application is up and running

[ ] TRG 5.10 Products need to support 3 versions at a time

Checks within TRG 5.10

[ ] TRG 5.10 latest (K8s version 1.25)
[ ] TRG 5.10 latest - 1 (K8s version 1.24)
[ ] TRG 5.10 latest - 2  (K8s version 1.23)

[ ] TRG 5.11 Upgradeability PRERELEASE

Checks within TRG 5.11

[ ] TRG 5.11 Based on the Helm test workflow, you must provide a GitHub action which takes the latest released helm chart, does an installation of it and then execute the upgrade to the current / new version.

TRG 6 Released Helm Chart

[ ] TRG 6.01 Released Helm Chart

TRG 7 Open Source Governance

[ ] TRG 7.01 Legal Documentation

[ ] TRG 7.02 License and copyright header

[ ] TRG 7.03 IP checks for project content

[ ] TRG 7.04 IP checks for 3rd party content

Checks within TRG 7.04

[ ] TRG 7.04 DEPENDENCIES file is up-to-date and reflects the current use of the 3rd party content
[ ] TRG 7.04 all libraries listed there should have the status "approved"
[ ] TRG 7.04 no libraries with status "rejected"
[ ] TRG 7.04 for libraries with status "restricted", the according IP issues must be present (issue number in the source column)

[ ] TRG 7.05 Legal information for distributions

[ ] TRG 7.06 Legal information for end user content

[ ] TRG 7.07 Legal notice for documentation

Hints
Information Sharing

Hi @matbmoser and @saudkhan116,
i don't have any info from release management regarding the digital-product-pass version, that should be included in the 3.2 releaese. Is it the 1.0.0-alpha? Will you release it as 1.0.0 if the release guideline checks are passed?

Hi @SebastianBezold,  We will release a release candidate for 1.0.0 today. It contain all the Quality Gates requirements as documented in GitHub. The release v1.0.0 does not contains the complete requirements.  Because of this we did not contacted with you yet.

@SebastianBezold the released was not created before in the feature freaze because of some architecture requirements that were pending to be tested.

https://github.com/eclipse-tractusx/digital-product-pass/issues/33 We have this already created and checked here 👍🏻

Hi @matbmoser,
ok thanks for the input. I created the issue, since we where triggered by Release management.
So v1.0.0-rc1 is the "ready" version?

After the E2E Tests worked and all the security requirements are completed a version v1.0.0 will be created, and will be the one ready for QG4. From a this perspective this version v1.0.0-rc2 should contain all the TRG requirements, and all that is in this version will be included in the v1.0.0

@SebastianBezold  v1.0.0 is released after passing our internal E2E tests! https://github.com/eclipse-tractusx/digital-product-pass/releases/tag/v1.0.0

Hi @matbmoser,
I think I don't want to create an issue for it, but maybe for consideration:
There is an avp key in your Charts values. Not sure, if in DPP context, AVP does make sense, but if you use it as Argo CD Vault Plugin I would rename it.
This is too heavily tied to a specific deployment tooling

Hi @matbmoser, I think I don't want to create an issue for it, but maybe for consideration: There is an avp key in your Charts values. Not sure, if in DPP context, AVP does make sense, but if you use it as Argo CD Vault Plugin I would rename it. This is too heavily tied to a specific deployment tooling

Ok, thank you for making this visible, we will refactor it for the next release.

Hi @matbmoser, I linked the issue #122 here, because I don't really understand the Chart testing workflow here. Could you or anyone else from the team please take a look and clarify?

Ok we fixed the problem now everything is up and running in the release v1.0.0

Current status: I want to test the changes made in v1.0.0-rc4, but the Docker images don't seem to be release yet

Hi @SebastianBezold,
as far as I know, the license dash tool is down and we are not able to publish docker images for the latest release version v1.0.0. Yesterday, the release version v1.0.0 was updated.

@saudkhan116,
did you dependencies change for the -rc4 changes, or what do you need dash for in regards to docker build?
Does the update of v1.0.0 include the changes done for -rc4?

We didn't change any dependencies, there was a hotfix #125 yesterday that got merged into the v1.0.0 . Due to this, we need to run the dash tool to scan the dependencies check again and afterwards publish the images.

@SebastianBezold  the new docker images are now published here:

https://hub.docker.com/r/tractusx/digital-product-pass-backend
https://hub.docker.com/r/tractusx/digital-product-pass-frontend

Hi @saudkhan116 and @matbmoser,
almost all the checks are passed. Thanks for the fixes!
There is just one last thing, which is legal notice in documentation TRG 7.07. I linked it to the specific section.
TL;DR on what is missing.
The docs, that you have in the /docs folder should also contain a notice to the License they are put under (In your case most likely Apache-2.0. This section should be readable by the end user. This means no comment like in the source code files but plain markdown.
It would be enough, if the "Entrypoint" to the documentation does contain that notice. In case you have different types of docs (i.e. Arc42, User Guide, Admin Guide, etc.) then every "Entrypoint" to this docs should have the Notice.
If you add these Notices, then I'll conclude the QG checks, you also do not need to build a new version for that change. main is fine here

Sorry small update @matbmoser and @saudkhan116, I was wrong here.
Since the files are rendered separately when viewing, we actually need the ## Notice section in every file

Sorry small update @matbmoser and @saudkhan116, I was wrong here. Since the files are rendered separately when viewing, we actually need the ## Notice section in every file

Hi @SebastianBezold, thank you for your feedback. We will have look into the TRG 7.07

Reopened the issue  #60 which was closed due to not enough clarification.

Hi @SebastianBezold, the requested TRG requirement is implemented in PR #127. Please have a review.
Thanks!

Thank you very much @SebastianBezold 👍💯

Hi @saudkhan116, thanks a lot! I guess you can close #60 with the merge of #127 as well. CC-BY-4.0 is definitely needed for KIT docs on the adoption view. For all other products, you can choose to put more docs under CC-BY, but it's not mandatory.
With this done, the QG 4 checks from my side are done :) congrats 👍 🚀

Thank you Sebastian for the review! 🥇


[Feature] Option to disable Muxing and language TAGS

I think an option to not perform muxing after download/decryption would be interesting.
Another thing related to language tags, leave it original, for example:
"zzz.en-US.ass "
"zzz.es-419.ass"
"zzz.es-ES.ass"
"zzz.it-IT.ass"

Muxing takes about 90 seconds on audio only downloads.. (I'm going back to download English dubs) It's taking forever.. I'm trying to download the project to do a PR but it seems to be missing the csproj file


feat: add sidebar menu

:tada: This PR is included in version 1.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use the right name for @LongLink entries

These seem to be found with a name of ././@LongLink, however
copy_path_into emits that as @LongLink. This is more tricky to fix
because Path::components() collapses that into ./@LongLink. For now,
just special-case them.
The implementation here is not ideal since it will change the behavior
for non-GNU entries.
Fixes #76

Thanks! I wonder if though this could just directly set the bytes of the header here with .as_gnu().unwrap().name?

Hmm. I can try that tomorrow.

Is this the right way to copy elements from one array to another? :worried:

Fine by me, thanks!


Suggestion: Getting Item

Is there a way to get the displayed item in the advancement?

Not yet, but I can add it in the next update

@emmanuelvlad Check the last update, now you can get the ItemStack object of the advancement item.
Tested in 1.17.1 and 1.16.5, it will help if you can test that in other versions.


panic in related to Bind with a pointer

Describe the bug
Panic when running wire ./...
To Reproduce
Sorry, I can't give a specific repro because

I worked around it as soon as I ran into it
There's a lot of proprietary code involved and it would have been pretty hard to isolate

The error was related to a bind statement:
	wire.Bind(new(Interface), new(*Concrete)),

I don't know what was unusual about this bind statement. There was New function that returns a pointer to Concrete and *Concrete implements Interface. In 0.2.2, I was able to use new(Concrete), but I had to change that to new(*Concrete) after upgrading to 0.3.0 and that's when the panic happened.
I hope that the following stack trace helps. If not, we might want to wait for someone to run into this again and provide a repro.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x64488d]

goroutine 1 [running]:
go/types.(*Package).Path(...)
        /home/<user>/.go/src/go/types/package.go:30
github.com/google/wire/internal/wire.(*objectCache).get(0xc03b480880, 0x76bb60, 0xc00008cc30, 0x0, 0x0, 0x0, 0x0, 0x0)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:464 +0x7d
github.com/google/wire/internal/wire.(*objectCache).processExpr(0xc03b480880, 0xc03a9324b0, 0xc000cfdce0, 0x5b, 0x766e60, 0xc03a9394c0, 0x0, 0x0, 0x0, 0x0, ...)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:523 +0xfd3
github.com/google/wire/internal/wire.(*objectCache).processNewSet(0xc03b480880, 0xc03a9324b0, 0xc000cfdce0, 0x5b, 0xc03a9c1980, 0x0, 0xc03a905620, 0xf, 0xc000656ec0, 0x58632c, ...)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:592 +0x18a
github.com/google/wire/internal/wire.(*objectCache).processExpr(0xc03b480880, 0xc03a9324b0, 0xc000cfdce0, 0x5b, 0x766a60, 0xc03a9c1980, 0xc03a905620, 0xf, 0xf, 0xc000026500, ...)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:535 +0x519
github.com/google/wire/internal/wire.(*objectCache).get(0xc03b480880, 0x76bd40, 0xc03a9331d0, 0x0, 0x0, 0x0, 0x0, 0x0)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:489 +0x42e
github.com/google/wire/internal/wire.(*objectCache).processExpr(0xc03b480880, 0xc03b4684b0, 0xc0003737a0, 0x51, 0x7671a0, 0xc03b441b60, 0x0, 0x0, 0x68c340, 0xc03b4e1320, ...)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:523 +0xfd3
github.com/google/wire/internal/wire.(*objectCache).processNewSet(0xc03b480880, 0xc03b4684b0, 0xc0003737a0, 0x51, 0xc03b466e40, 0x0, 0xc03b4432a0, 0x16, 0xc0006573e8, 0x58632c, ...)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:592 +0x18a
github.com/google/wire/internal/wire.(*objectCache).processExpr(0xc03b480880, 0xc03b4684b0, 0xc0003737a0, 0x51, 0x766a60, 0xc03b466e40, 0xc03b4432a0, 0x16, 0x16, 0xc000026500, ...)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:535 +0x519
github.com/google/wire/internal/wire.(*objectCache).get(0xc03b480880, 0x76bd40, 0xc03b468550, 0x0, 0x0, 0x0, 0x0, 0x0)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:489 +0x42e
github.com/google/wire/internal/wire.(*objectCache).processExpr(0xc03b480880, 0xc03b468e10, 0xc0002f6eb0, 0x49, 0x7671a0, 0xc03b4770a0, 0x0, 0x0, 0x6b2cc0, 0xc039982600, ...)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:523 +0xfd3
github.com/google/wire/internal/wire.(*objectCache).processNewSet(0xc03b480880, 0xc03b468e10, 0xc0002f6eb0, 0x49, 0xc03b467680, 0xc03b4808e0, 0x0, 0x0, 0x0, 0x0, ...)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:592 +0x18a
github.com/google/wire/internal/wire.generateInjectors(0xc03b469f90, 0xc000da5770, 0x2, 0xc0393f10a0, 0x69, 0x0, 0x0, 0xc00000c0b0)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/wire.go:176 +0xaaf
github.com/google/wire/internal/wire.Generate(0x767ca0, 0xc0000120d8, 0xc000020004, 0x40, 0xc000010c00, 0x59, 0x59, 0xc00000c0b0, 0x1, 0x1, ...)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/wire.go:99 +0x412
main.(*genCmd).Execute(0xc000047eb0, 0x767ca0, 0xc0000120d8, 0xc00005a180, 0x0, 0x0, 0x0, 0x7f97cf1e8008)
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/cmd/wire/main.go:131 +0x249
main.main()
        /home/<user>/go/pkg/mod/github.com/google/wire@v0.3.0/cmd/wire/main.go:71 +0x4a1
exit status 2

Expected behavior
No panic
Version
0.3.0
Additional context
Sorry, too much proprietary code. Hope there's something obvious that recently changed and the stack trace helps.

@shantuo 	can you take a look? Maybe add a new testcase with this?

Hi @gracenoah , is your Interface a Go built-in type?

In this example Interface is an interface with some methods. I really don't know what's special about it because the panic happens in this one scenario, but I've used wire.Bind elsewhere without it panicking. Sorry that I can't be more helpful.

No worries, from what I can tell in the stack trace you provided, I don't think this is a bug in Bind, but maybe in NewSet, as the panic happens while it is processing the out layer NewSet function. Also, the panic happens when it is trying to get the import path of one of the providers in your argument list you are passing into NewSet by calling "go/types".Object.Pkg().Path(), the Pkg() call returns nil "for labels and objects in the Universe scope", which means you might have some argument in the same NewSet call that is a built-in type, or a wrapper of one, maybe?

I think you might be right. I tried to reproduce the issue again by adding back the Bind an changing the constructor to return the struct type and I couldn't. Since, this is all the information we have, I'd be happy with a fix that just adds a better error message whenever this edge case is triggered. Hopefully if it happens again, the error will help me understand the source of the issue.

It happened to me when I forgot a wire.Struct call. I have created a provider like this:
wire.Build(new(CreateServiceWithMocks), "*")

instead of
wire.Build(wire.Struct(new(CreateServiceWithMocks), "*"))

Just got a very similar looking panic. This is the exact repro:
package main

import "github.com/google/wire"

type A struct {
	B string
}

func makeA(string) A {
	panic(wire.Build(wire.Struct(new(*A), "*")))
}

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x57f376]

goroutine 1 [running]:
go/types.writeType(0xc0024a15f0, 0x776540, 0x0, 0x0, 0xc0002353a8, 0x1, 0x8)
        /home/gracenoah/.go/src/go/types/typestring.go:120 +0x6a6
go/types.WriteType(...)
        /home/gracenoah/.go/src/go/types/typestring.go:75
go/types.TypeString(0x776540, 0x0, 0x0, 0xc0001ccb40, 0x25)
        /home/gracenoah/.go/src/go/types/typestring.go:67 +0xb1
github.com/google/wire/internal/wire.processStructProvider(0xc0000ea280, 0xc002486aa0, 0xc00247d100, 0x6, 0x1, 0x75)
        /home/gracenoah/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:806 +0xb11
github.com/google/wire/internal/wire.(*objectCache).processExpr(0xc0021b3880, 0xc002486aa0, 0xc0001d6450, 0x5, 0x778ec0, 0xc00247d100, 0x0, 0x0, 0x20, 0x6d88a0, ...)
        /home/gracenoah/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:556 +0xb6e
github.com/google/wire/internal/wire.(*objectCache).processNewSet(0xc0021b3880, 0xc002486aa0, 0xc0001d6450, 0x5, 0xc00247d140, 0xc0021b38c0, 0x0, 0x0, 0x0, 0x0, ...)
        /home/gracenoah/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/parse.go:592 +0x18c
github.com/google/wire/internal/wire.generateInjectors(0xc002486f50, 0xc0001dcd20, 0x2, 0xc00113f590, 0x29, 0x0, 0x0, 0xc0000ac010)
        /home/gracenoah/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/wire.go:176 +0x9f4
github.com/google/wire/internal/wire.Generate(0x77a080, 0xc00008e000, 0xc000016064, 0x1d, 0xc000102000, 0x60, 0x60, 0xc0000ac010, 0x1, 0x1, ...)
        /home/gracenoah/go/pkg/mod/github.com/google/wire@v0.3.0/internal/wire/wire.go:99 +0x411
main.(*genCmd).Execute(0xc000077e78, 0x77a080, 0xc00008e000, 0xc0000a4120, 0x0, 0x0, 0x0, 0x30)
        /home/gracenoah/go/pkg/mod/github.com/google/wire@v0.3.0/cmd/wire/main.go:131 +0x247
main.main()
        /home/gracenoah/go/pkg/mod/github.com/google/wire@v0.3.0/cmd/wire/main.go:71 +0x4dc
exit status 2

@gracenoah and @anton-dessiatov, it seems like that Struct issue is unrelated to @gracenoah's original issue with Bind. I wasn't able to find anything more on that particular failure, but I have a fix ready for the other issue. I've opened #219 to track the Struct issue.

Thanks for investigating and making a separate issue.


(freecad) adding erroraction continue

This will allow this package to pass verification
@AdmiringWorm @majkinetor @gep13 @pascalberger

This package .portable has been stuck in verification limbo since April 19th, 2020. I had asked if this or that should be done to get this package to pass verification. The answer was always not familiar with it will get back to you.
Description

The use of the Get-Version cmdlet causes grief if the package AU is not installed. Since all Core Packages have $ErrorActionPreference = 'Stop'; This was causing a HARD Stop and thus causing the verification to Fail.
The cmdlet of Get-Command has -erroraction as a choice of parameters. Setting this to Continue will allow the package to complete the if..else lines
Motivation and Context

How Has this Been Tested?

Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[ ] The changes only affect a single package (not including meta package).

Original Location

Original Repository
Open Issues Add the different issues underneath, and tick those that are fixed in this PR

[x] Issue 1 link
[ ] Issue 2 Link

[ ] Include the link to the opened PR that removes the package from the original location
[ ] The migration guidelines have been followed

:white_check_mark: Package verification completed without issues. PR is now pending human review

:white_check_mark: Package verification completed without issues. PR is now pending human review

@majkinetor
I have removed the Get-Version check all together. It really wasn't needed all all. Thanks for the review


is this production ready ?

this looks very similar to laravel schedule. when you think it will be in stable form ?

I'm using it in production for a few months, on multiple projects.


GATT MTU Callback

It appears there's an automatic call to bt_gatt_exchange_mtu going on except there's no real way in my application to get that mtu value as the only callback available is the connect callback. The exchange for mtu hasn't happened at that point.
It would be nice to be able to register a callback to find out what the exchanged mtu was in my application so I can size my notifications appropriately.

You can read the MTU size at any point with use  of bt_gatt_get_mtu.


Use DateTime->set_locale instead of ->set to change the locale

Requires DateTime 1.04+

Note that using ->set this way will start warning in a future version of DateTime

Coverage increased (+0.002%) to 90.802% when pulling bdde12a6bb2914533f62532af30da1d85cac88e1 on autarch:autarch/no-set-locale into e07c46a69daefd579e621ef46186bd22cf722bdf on theory:master.

Thanks Dave!


update txt metadata

What
Update txt download for BYO
Trello - https://trello.com/c/JkyoYKdQ/6077-update-txt-download-for-byo
How to review
Confirm changes match the requested changes in Trello ticket
Who can review
Anyone

I'm going to merge to develop for now as this ideally needs to be ready for "go live" tomorrow. I will work on the requested changes afterwards


Show all hunks

Sorry, I was experimenting my local repo, just mistake to send this messy PR, sorry!
And thanks for this great pkg!


Automatically build and release the CLI for the windows-386 build target

This updates our release process to build each of our CLIs for x86 Windows devices (i.e. just about anything that isn't x64 or ARM!).
At this time, we don't have a way to test that these binaries work as part of our CI/CD process. Nevertheless, we think it's better to distribute a binary that should work than to offer nothing to users who want x86 support! If people run into any problems, they can create an issue and we will, of course, look into it.
Fixes https://github.com/github/gh-gei/issues/796.

[ ] Did you write/update appropriate tests
[x] Release notes updated (if appropriate)
[ ] Appropriate logging output
[x] Issue linked
[ ] Docs updated (or issue created)

@dylan-smith I'm seeing the Windows integration test fail - I guess I've broken something! - but looking at the test output, I can't find the line that is actually failing. I can just see that the exit code is wrong.
Could you take a look for me? Pretty sure I'm just being stupid... 😓

Ignore me! It passed with another try.


Remove mode parameter?

It doesn't seem like the mode parameter actually does anything. If I'm correct, it should be removed, as it is misleading.

Nevermind, I was missing a key line


orderBy order the data asc without mention the direction

I'm trying to order data using orderBy but I found that without mentioning the direction the data are ordered in an ascendant way:
.select('place.*', 'user.name as userName')
    .join('user', 'place.user_id', 'user.id')
    .skipUndefined();
  if (req.query.name) {
    userBuilder
      .where(raw("to_tsvector('english',??) @@ to_tsquery('english',?)", ['place.name', `${req.query.name}:*`]))
      .orderBy(raw("ts_rank_cd(to_tsvector('english',??), to_tsquery('english',?)) ", ['place.name', `${checkNameQuery(req.query.name)}:*`]))

sql: 'select "place".*, "user"."name" as "userName" from "place" inner join "user" on "place"."user_id" = "user"."id" where to_tsvector(\'config\',"place"."name") @@ to_tsquery(\'config\',?) order by ts_rank_cd(to_tsvector(\'config\',"place"."name"), to_tsquery(\'config\',?))  asc' }

orderBy — .orderBy(column, [direction])
Adds an order by clause to the query.
knex('users').orderBy('name', 'desc')
Outputs:
select * from "users" order by "name" desc

I didn't know if it is normal and this function order the data asc if nothing was mentioned.

Default for orderBy is ascend.


Add edu Institution

https://www.ilc.edu.tw/
If you need more info please tell me.

@Feleys First stage of verification passed, official domain is ilc.edu.tw as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Feleys I am sorry, this domain seems to represent an umbrella institution, not a specific single university or a college. Please apply for free educational license with an official document which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
I have to close the request without merging.
Thank you for the understanding!


optional fields were marked required

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65afe6587cf64303032c635e--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65afe77d06d76703cdc578f5--harness-developer.netlify.app