Module build failed (from ./node_modules/eslint-loader/index.js):

Version
3.4.0
Environment info
Environment Info:

  System:
    OS: macOS 10.14
    CPU: (4) x64 Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
  Binaries:
    Node: 10.12.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.7.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 73.0.3683.86
    Firefox: Not Found
    Safari: 12.0
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0-beta.3
    @vue/babel-plugin-transform-vue-jsx:  1.0.0-beta.3
    @vue/babel-preset-app:  3.5.5
    @vue/babel-preset-jsx:  1.0.0-beta.3
    @vue/babel-sugar-functional-vue:  1.0.0-beta.3
    @vue/babel-sugar-inject-h:  1.0.0-beta.3
    @vue/babel-sugar-v-model:  1.0.0-beta.3
    @vue/babel-sugar-v-on:  1.0.0-beta.3
    @vue/cli-overlay:  3.5.1
    @vue/cli-plugin-babel: ^3.0.3 => 3.5.5
    @vue/cli-plugin-eslint: ^3.0.3 => 3.5.1
    @vue/cli-service: ^3.0.3 => 3.5.3
    @vue/cli-shared-utils:  3.5.1
    @vue/component-compiler-utils:  2.6.0
    @vue/preload-webpack-plugin:  1.1.0
    @vue/web-component-wrapper:  1.2.0
    shards-vue: ^1.0.7 => 1.0.7
    vue: ^2.5.17 => 2.6.10
    vue-clickaway:  2.2.2
    vue-eslint-parser:  2.0.3
    vue-hot-reload-api:  2.3.3
    vue-loader:  15.7.0
    vue-router: ^3.0.1 => 3.0.3
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.5.17 => 2.6.10
    vue-template-es2015-compiler:  1.9.1
    vuejs-datepicker:  1.5.4
  npmGlobalPackages:
    @vue/cli: 3.4.0

Steps to reproduce
?
What is expected?
Smooth running of npm run serve
What is actually happening?
Error: Cannot find module '@vue/eslint-config-airbnb'

vue-cli-service serve

INFO  Starting development server...
98% after emitting CopyPlugin
ERROR  Failed to compile with 1 errors                                                                                4:55:59 PM
Module build failed (from ./node_modules/eslint-loader/index.js):
Error: Cannot find module '@vue/eslint-config-airbnb'
Referenced from: /Users/michaelroberts/Developer/repos/hug-front-end/.eslintrc.js
at ModuleResolver.resolve (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/util/module-resolver.js:74:19)
at resolve (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config/config-file.js:479:28)
at load (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config/config-file.js:551:26)
at configExtends.reduceRight (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config/config-file.js:425:36)
at Array.reduceRight ()
at applyExtends (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config/config-file.js:403:26)
at loadFromDisk (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config/config-file.js:523:22)
at Object.load (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config/config-file.js:559:20)
at Config.getLocalConfigHierarchy (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config.js:227:44)
at Config.getConfigHierarchy (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config.js:179:43)
at Config.getConfigVector (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config.js:286:21)
at Config.getConfig (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/config.js:329:29)
at processText (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/cli-engine.js:163:33)
at CLIEngine.executeOnText (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/@vue/cli-plugin-eslint/node_modules/eslint/lib/cli-engine.js:620:17)
at lint (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/eslint-loader/index.js:263:17)
at transform (/Users/michaelroberts/Developer/repos/hug-front-end/node_modules/eslint-loader/index.js:237:18)
You may use special comments to disable some warnings.
Use // eslint-disable-next-line to ignore the next line.
Use /* eslint-disable */ to ignore all warnings in a file.

Hi
Thanks for filing this issue! Could you please provide a small reporduction on jsfiddle.net so we can debug this without trying to replicate this ourselves?`
That would be very helpful, thanks!

It sounds as if this package is defined as a dependency but not actually installed.
Have you tried to install it?

Closing due to inactivity. Please open a new issue with a reference to this one if you can follow up with more information.

This is an issue for me as well

Well we can reopen it if you can provide a reproduction as is required.

Hello, same here.
I use vue cli version 3.6:

vue create myproject
choose default settings
cd myproject
npm run serve
And get this error

 INFO  Starting development server...
 98% after emitting CopyPlugin

 ERROR  Failed to compile with 1 errors

Module build failed (from ./node_modules/eslint-loader/index.js):
Error: Cannot find module '/Users/toto/Documents/programming/VueProjects/myproject/node_modules/eslint/lib/api.js/package.json'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.module.exports (/Users/mcz/Documents/programming/VueProjects/myproject/node_modules/eslint-loader/index.js:170:23)

You may use special comments to disable some warnings.
Use // eslint-disable-next-line to ignore the next line.
Use /* eslint-disable */ to ignore all warnings in a file.

I use this yesterday and everythings worked fine.
tested on 3.6.3 & 3.7.0
Any idea

See #4231


Unified author names in commits

Hello all,
As we have seen, we all have multiple aliases in our commits, which makes statistics about who did what very unclear.
Moreover, it is likely to get worse as time goes on.
To solve this problem, I propose a to use a .mailmap file which should solve the problem of multiple aliases per author.
I have developed such solution in the authors branch.
As this solution needed a complete rewrite of the history, we cannot simply merge this branch onto the master one, but we have to create a new master branch. Further commits should be automatically renamed thanks to the .mailmap file.
Here is a summary of git shortlog -sne --all before/after.
From:
  1150  Gilles Poncelet<EMAIL_ADDRESS>   313  Jerome Eertmans<EMAIL_ADDRESS>   294  Gilles Poncelet<EMAIL_ADDRESS>   274  dependabot-preview[bot]<EMAIL_ADDRESS>   207  Louis Navarre<EMAIL_ADDRESS>   192  louisna<EMAIL_ADDRESS>   177  Gilles Poncelet<EMAIL_ADDRESS>   173  jeertmans<EMAIL_ADDRESS>   158  Gilles Poncelet<EMAIL_ADDRESS>   121  Eertmans<EMAIL_ADDRESS>    14  louisna<EMAIL_ADDRESS>    12  Jérome Eertmans<EMAIL_ADDRESS>    11  Jerome<EMAIL_ADDRESS>     2  Gilles Poncelet<EMAIL_ADDRESS>     1  Louis Navarre<EMAIL_ADDRESS>
To:
  1781  Gilles Poncelet<EMAIL_ADDRESS>   630  Jerome Eertmans<EMAIL_ADDRESS>   414  Louis Navarre<EMAIL_ADDRESS>   274  dependabot-preview[bot]<EMAIL_ADDRESS>

Closing since this branch became the new "main"


Hook in GA to capture Split Testing Results

In order to push data from a split test into GA, we'll need to add our GA site tag in order to capture the data from the tests we run.

I'm marking this as a 2 point ticket. Originally, I had it as a 1 pointer (just add the GA code), but I recognize that there is an opportunity to refactor the configuration code a little bit more so that it's easier to work with.

After speaking with split and reviewing the metrics their platform uses, we have decided that we can probably use their platform to gain insights into our A/B tests. I'm going to rename this ticket to reflect this decision.


File/Folder TTL & Resurrection

I have a use-case where I'm storing all my files in compressed and serialized form. The first pipeline will have to decompress them first.
The decompressed files must be stored on PFS in order to be accessible to other pipelines. This defeats the whole purpose of compressing the files in the first place.
A user can currently either decompress the files in every pipeline or store both the compressed and uncompressed forms.
What we can do instead is provide a mechanism for setting Time To Live on a file or folder in PFS. After an object has passed it's TTL it will be deleted but the metadata about the object will remain.
All objects with TTL will be lazily evaluated. If they are not present pachyderm will retrigger all the pipelines that came before it to reproduce it and it will be transparently provided to the current executing pipeline.
A version of this feature without lazy evaluation can be implemented by verifying that all objects are present and reproduce the missing files.

Definitely see the use case and think that this is something we'll want to service. I'm not sure that TTL is a good abstraction for this though, because we should be able to know the lifetime of the files ahead of time, since they're being consumed by downstream pipelines. I think #546 is probably a better implementation path for this functionality.

#546 and this issue are similar but will be used in different use-cases.
In my use-case, the compressed files are only accessed once during their entire lifetime so theoretically #546 fits unless I'm experimenting. In this case, you don't want to decompress again and again.
In the future, multiple pipelines will use the same file which will also require repeated decompression if I use #546.
This is why TTL is a good addition.

stale


[crashpad] Support more targets and cross-compile for Android

Updates Crashpad port to build for Windows, OSX, Linux, and allows those hosts to cross-compile for Android. Also introduces generate-dump feature to optionally build and install generate_dump tool for live-process-dump-creation.

What does your PR fix?
Fixes #22891
Fixes #25197

Which triplets are supported/not supported? Have you updated the CI baseline?
Supports:

x64-windows-static
x86-windows-static
arm64-windows-static
x64-linux
x64-osx
x64-android
x86-android
arm64-android
arm-android

CI baseline is updated.

Does your PR follow the maintainer guide?
Yes, I believe so.

Yes

Question: should I include some sort of readme about how to actually integrate Crashpad? A usage file? What would be recommended? When figuring out how to integrate Android crashpad, I relied on https://docs.bugsplat.com/introduction/getting-started/integrations/mobile/android quite a bit.

@vejmartin / @JackBoosY, please review

Is it possible to add arm64-windows as well?

Is it possible to add arm64-windows as well?

@janisozaur , yes, and I just got a local build of it to work

@LilyWangLL / @JackBoosY , is there a way to get clang installed on the CI x64-linux machine? I would've wanted to use vcpkg_find_acquire_program(CLANG), but currently that just tells you to run sudo apt-get install clang. I think I could mimic downloading a release from the LLVM GitHub project, but not sure if we're okay with that approach or not.

@BillyONeal Request clang in Linux image.

@LilyWangLL / @JackBoosY , is there a way to get clang installed on the CI x64-linux machine? I would've wanted to use vcpkg_find_acquire_program(CLANG), but currently that just tells you to run sudo apt-get install clang. I think I could mimic downloading a release from the LLVM GitHub project, but not sure if we're okay with that approach or not.

Ports don't get to be that opinionated about which compiler is used; they need to use what the triplet selected.

@BillyONeal Request clang in Linux image.

I'm nervous about doing that because we explicitly want to prevent this kind of thing.

@bold84, any chance you can help with validation of arm64-OSX locally? My machine's too old to validate that. Also, were you able to successfully build arm-windows? When I try to build that, I get issues related to a missing toolchain.

What I'm particular do you mean by "validation"?
I'll try a Windows arm64 build and let you know. Give me an hour or two.

What I'm particular do you mean by "validation"?

@bold84, I effectively mean that you are able to build successfully. I was able to build arm64-windows fine. I wasn't able to build arm-windows and arm64-osx. Since your recent change to the vcpkg.json broadened the scope of supported targets for OSX & Windows, I need some help validating if those builds succeed.
With your original change, I assume you were able to build all the new permutations of triplets that weren't supported before (i.e., arm, arm64, x86 for windows and arm64-osx).

@bold84, sorry for not being clearer; I was hoping you could validate if my changes specifically still build for those triplets. Would you be able to clone my fork/branch and rerun the same tests? Sorry for any inconvenience, but this will be very helpful.
Also, I'm okay with saying crashpad doesn't build for arm-windows for now.

So I'm assuming we can review this PR and no one is against this now?

So I'm assuming we can review this PR and no one is against this now?

Yes, this PR should be final now.

crashpad:x64-windows:/debug/lib/base.lib
crashpad:x64-windows:/debug/lib/client.lib
crashpad:x64-windows:/debug/lib/common.lib
crashpad:x64-windows:/debug/lib/util.lib

Can we accept this or will there be file conflicts?

Thanks for the improvements! Main thing I'm "request changes" over is the duplicated toolset selection, the other things are nitpicks :)

@BillyONeal, thanks for the review. I've made updates and added comments. Your nits were a little more than nits IMO; they pointed out real issues I needed to think more about and do a decent bit of testing for. Thanks again.

@vicroms @ras0219 and I discussed this in person today. We are torn on the path forward. We don't necessarily want to say that there is no path forward for such ports that are this opinionated about their tools. We're also working on vcpkg artifacts which are likely to provide additional paths for ports to declare that they want a specific toolchain.
On the other hand, we also have lots of controls for users to customize which toolchain is used for all ports: this is a user setting.
We still aren't sure exactly what path to suggest for you right now, although we are sure that directly including toolchain files and stuff like that (rather than consuming the already digested values) isn't the right approach, and I see you've already started to look at that.
Paths we discussed:

Use the port's build tools:

We treat this port as 'another language' e.g. assembly or rust, it can download its whole toolchain but can't be assumed to necessarily work with anything else. (Requires API review to see that it effectively only exposes C API symbols to a C++ linker, doesn't have standard library conflicts, etc.)

Use our build tools:

Force override the upstream build system's attempt to force override the build toolset with ours.
Detect mismatch and emit an error.

Thanks for your contribution and sorry that we don't have a concrete path forward yet.

@BillyONeal, now that I am not including toolchains directly, would you still consider approving this approach? We can create an issue to follow up on all the GN ports perhaps that may behave like this w.r.t. using specific compilers. But since this port and probably others already behave like this, I'm asking for approval so that the community can benefit from these positive new features (i.e., cross-compiling for Android on Windows), which I think outweigh the negatives.

The whole team is still thinking about this; I expect next time it won't be until next Thursday we seriously respond. Sorry for the delay; you've just touched a really complex thing.

@ras0219-msft / @BillyONeal , any updates regarding the ability to move forward with this PR?

I don't believe anything has changed or is likely to change soon, no.

After reading through the current discussions, I'm still trying to understand what is the current blocker. Is it related to the changes adding support for more targets or purely having the port using an external toolchain?
The crashpad port seems to not be working as it's missing some generated headers (see https://github.com/microsoft/vcpkg/issues/25197). Therefore, unless there is a workaround, the community will need to use 2022.04.12.
Knowing that the port was already using an external toolchain before (if I understand @jason-ortiz comments), does it mean that any attempt of fixing the port would be rejected unless a solution is found through one of the ideas that have been suggested in https://github.com/microsoft/vcpkg/pull/23827#issuecomment-1132212149?

After reading through the current discussions, I'm still trying to understand what is the current blocker. Is it related to the changes adding support for more targets or purely having the port using an external toolchain?

The problem is that we make the compiler to use a user setting. vcpkg says "you WILL use the compiler the user says" and this port is trying to say "NO, I will ignore you and use Clang instead" which isn't OK in general.

Knowing that the port was already using an external toolchain before (if I understand @jason-ortiz comments)

I don't see the current port using an external toolchain. In fact there's a lot of stuff in there trying to ensure user settings are respected. That may be imperfect but we certainly were not downloading clang before.

This PR seems to be the best chance to resolve https://github.com/microsoft/vcpkg/issues/25197 and at this point, I'm wondering if I'm the only Crashpad's port user running into building errors with the current port on Windows :sweat_smile: I did double check this is still the case with the latest vcpkg release.
Therefore, I'm wondering if you could have a look at the latest comment @jason-ortiz and how does that connect with the work that has been done in https://github.com/microsoft/vcpkg/pull/25864?

Ping @jason-ortiz for reply.

Hi everyone
Jason is no longer working in this code unfortunately. At this point, anyone who is willing to take over the change and get it over the finish line is super welcome to, but we don't have the resources on our side to finish this off

Convert to draft since there is no reply.

Any progrees here?

Drop vcpkg-team-review until this PR has any progress.

Closing this PR since it seems that no progress is being made. Please ping me to reopen if work is still being done.


Revert "build: Include a basic setup.py to allow editable installs during development (#370)"

It seems that hings are more complicated than that. This shim setup.py does
allow the project to be pip -e installed but you don't get the entrypoints,
making it completely useless.
This reverts commit 915183dd181fc2c5619765e245c465a1765102fd.

Sorry for the noise. :(

Sorry to hear that 😕. I've done a bit of searching for ways to editable-install Poetry projects and it seems the only supported way is by using Poetry itself to manage whatever environment you're installing it to. It's possible to generate a fully-complete setup.py from the pyproject.toml but we'd have to find a way to automate keeping it up to date. Maybe with a periodic GitHub Action or something?

Sounds quite overkill to me, alas.


Update CITATION.cff

Summary of changes

Update citation

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:loudspeaker: Thoughts on this report? Let us know!


DefaultScalesMixin cannot read property '0' of undefined.

I'm attempting to use this charting library for my dataset of about 15,000 points; I want a simple scatter graph. My data is in the format:
...
{
      "label": "label1",
      "x": -2.84194509027,
      "y": -0.758540839391,
      "r": 0.0,
      "g": 1.0,
      "b": 0.0,
      "cmc": 4
    },
    {
      "label": "label2",
      "x": 1.54194586524,
      "y": 0.253299257011,
      "r": 0.588235294118,
      "g": 0.294117647059,
      "b": 0.0,
      "cmc": 1
    }, ...

where x and y are the [x,y] coords, rgb are colour components, and label is what I want on the tooltip. My code is pretty damn simple:
import React from 'react';
import ReactDOM from 'react-dom';
var R3D = require('react-d3-components');
var ScatterPlot = R3D.ScatterPlot;

var margin = {top: 10, bottom: 50, left: 50, right: 10};
var data = require('./data/data.json');

var CosinePlot = React.createClass({
	render: function() {
		return <ScatterPlot
			data={data}
			width={400}
			height={400}
			margin={margin}/>;
	}
});

export default CosinePlot;

However, when I attempt to load this on my page I get an error on line 72 of DefaultScalesMixin.js; "Uncaught TypeError: Cannot read property '0' of undefined". Is there a way to specify to the ScatterPlot that I want the x and y values to be the [x,y] coordinates?

Going from this sample:
data = [{
    customLabel: 'somethingA',
    customValues: [[0, 3], [1.3, -4], [3, 7], [-3.5, 8], [4, 7], [4.5, 7],  [5, -7.8]]
}];

var labelAccessor = function(stack) { return stack.customLabel; };
var valuesAccessor = function(stack) { return stack.customValues; };
var xAccessor = function(element) { return element[0]; };
var yAccessor = function(element) { return element[1]; };

React.render(<ScatterPlot
                data={data}
                width={400}
                height={400}
                margin={{top: 10, bottom: 50, left: 50, right: 10}}

                label={labelAccessor}
                x={xAccessor}
                y={yAccessor}
                values={valuesAccessor}/>,
            document.getElementById('location'));

Each stack is 1 element of the data array. It has customLabel and customValues fields.
In your case since the layout is flat... maybe try
var valuesAccessor = function(stack) { return stack; }; // since it's not a field but the object itself

and
var xAccessor = function(element) { return element.x; };
var yAccessor = function(element) { return element.y; };

Didn't have time to test it but maybe it gives you an idea.

OK, so now my code is:
var ScatterPlot = R3D.ScatterPlot;

var margin = {top: 10, bottom: 50, left: 50, right: 10};
var valuesAccessor = function(stack) { return stack; };
var xAccessor = function(element) { return element.x; };
var yAccessor = function(element) { return element.y; };

var CosinePlot = React.createClass({
	render: function() {
		return <ScatterPlot
			data={cardData}
			width={400}
			height={400}
			margin={margin}
			x={xAccessor}
			y={yAccessor}
			values={valuesAccessor}/>;
	}
});

export default CosinePlot;

I put a breakpoint in the valuesAccessor return, and on page load it seems to work; it shows me one data point with all 7 attributes. However, it fails on the xAccessor, saying that 'element' is undefined and therefore unable to find x. How does one define 'element' for those two functions?

OK, the problem is in DefaultScalesMixin.js, still line 72. It has:
if (typeof x(values(data[0])[0]) === "number") {

data[0] gives me one of my data objects with its 7 properties. values returns the same thing (since valuesAccessor just returns what was passed to it). The issue is that (data[0])[0] is undefined, since it's trying to find the first element of an object, not an array.

I am glad to hear you figured out the accessors.
About the performance question... I have to think about it. Not so easy to answer. Do you know exactly when it slows down? Redraw?

It's slow at all points. Just having the 15,000 points on the page is making all other elements animate/respond slowly.


{AKS} Fix aks byo appgw test case

This checklist is used to make sure that common guidelines for a pull request are followed.
Fix aks byo appgw test case test_aks_byo_appgw_with_ingress_appgw_addon. See sibling PR #22608 in azure-cli.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

Queued a pipeline to test this case.


Should have given credit at least.

These guys at https://team-gpt.com/ are using the same open script chatbot-ui, but they did not give credit. They should have at least mentioned it.

Thank you for bringing this to our attention, @shashicpontentwriter.
We at Team-GPT greatly appreciate the open-source community and the valuable work done by the creators of projects like Chatbot-UI. In fact, we have acknowledged the use of Chatbot-UI in our Terms of Use page, where we have provided appropriate credit to the original authors and contributors.
While it's true that we have utilized elements from Chatbot-UI in our initial MVP, our product has since evolved significantly, incorporating new features and functionality, including collaboration capabilities not present in the original project. Nonetheless, we remain grateful for the foundational work provided by Chatbot-UI and its developers.
Once again, we appreciate your vigilance in ensuring that open-source projects are given proper credit. We are committed to supporting and fostering the open-source community, and we will continue to recognize the contributions of the projects and individuals that have played a role in our development.
We value the open-source community and always strive to follow best practices when it comes to giving credit and complying with licensing requirements. If you have any further concerns or suggestions, please feel free to let us know.

Thank you for bringing this to our attention, @shashicpontentwriter.
We at Team-GPT greatly appreciate the open-source community and the valuable work done by the creators of projects like Chatbot-UI. In fact, we have acknowledged the use of Chatbot-UI in our Terms of Use page, where we have provided appropriate credit to the original authors and contributors.
While it's true that we have utilized elements from Chatbot-UI in our initial MVP, our product has since evolved significantly, incorporating new features and functionality, including collaboration capabilities not present in the original project. Nonetheless, we remain grateful for the foundational work provided by Chatbot-UI and its developers.
Once again, we appreciate your vigilance in ensuring that open-source projects are given proper credit. We are committed to supporting and fostering the open-source community, and we will continue to recognize the contributions of the projects and individuals that have played a role in our development.
We value the open-source community and always strive to follow best practices when it comes to giving credit and complying with licensing requirements. If you have any further concerns or suggestions, please feel free to let us know.

Thank you for taking the time to read and respond to my message. I'm glad to hear that you appreciate my commitment to supporting and giving credit to open-source projects.
I understand that using open-source software for business or personal purposes can be a great way to save time and money while also benefiting from the contributions of the wider community. As you mentioned, it's essential to give credit to the original authors and contributors, as well as comply with any licensing requirements.
I'm glad to hear that you appreciate my efforts to acknowledge the contributions of the creators of Chatbot-UI and other open-source projects. I believe that recognizing the efforts of the community is an essential part of supporting and fostering the growth of open-source software.
Once again, thank you for your response, and I appreciate your support for open-source projects.

From I can tell, this team-gpt is an online saas, only uses 3.5-turbo, and somehow interfaces with OpenAi so that it handles billing and invoices? I am confused about team-gpt handing the the invoicing and billing.

@kacher y'all might want to change your tool's name
https://openai.com/brand


Expose Event Router metrics

This PR exposes the metrics port of the event tailer.
It is up to users to scrape them or not.
On large "moving" clusters, the cardinality of the metrics can be huge.

@h4wkmoon thanks for the contribution!
Please signoff your commit with your email address as reported by the DCO check:
https://github.com/kube-logging/logging-operator/pull/1629/checks?check_run_id=20192975222
Also please run make fmt as described in https://github.com/kube-logging/logging-operator/blob/master/CONTRIBUTING.md#opening-a-pull-request-pr


fixed a version for play-services-vision

com.google.android.gms:play-services-vision trying to get the latest version, causes issue when newest arent supported or conflicts with some other library

hey, lets just create a new release, looks like the release wasn't merged back into master


How to print the "perf counters" when I use the FPU variant?

Hi! I know that if I want to show the "perf counters" in a RV32I architecture, I can easily use the "Perf Cfu" variant. However, now I want to  use a FPU supported RISCV CPU, namely that I cannot use "Perf Cfu" and "Fpu Cfu" at the same time. I want to see the cycles of some floating-point operations. How to print the "perf counters" when I use the FPU variant? Thanks!

Hello @yoooyeah , we would need to create a new VexRiscv variant that combines those two features!    They both requires some amount of resources --- do you have plenty of extra space on your target FPGA?
There are some instructions here (be warned, this is expert-level stuff, so not many contributors have attempted it, and we might have missed some stuff in the documentation): https://github.com/google/CFU-Playground/blob/main/soc/vexriscv/README.md
Basically, look at the Makefile in that directory, and create a new target that combines the flags for FPU and perf counters.    There are a few other places in the system that you need to inform about the new variant.
Can you give it a try?


refactor(ValidationViewStrategy): pull apart view strategies

The main goal of this refactoring is to pull apart the existing ValidateCustomAttributeViewStrategy into its component parts, and provide a means to support multiple strategies. Specifically:

ValidateCustomAttributeViewStrategy => ValidationViewStrategy
Move bootstrap specific view strategy to its own file
Update tests accordingly

NOTE: There is more work to be done here (specifically that twbootstrap is the default and embedded in the configuration, so this is less modular per se), but this is mostly meant to be a starting point for a discussion.

So to recap the goals -

Extract TWBS / associated DOM manipulation from the 'happy path' that's included for all developers consuming the plugin
Improve naming conventions of strategies

Does that mean that foreseeably some other CSS frameworks would have their own strategy?  Is strategy the proper term to describe this added functionality?
I think it makes sense for sure just want to get the broader picture and understanding.

Yeah, for instance I'm using semantic-ui in my project so the expectations are all totally different (this can vary from simply the name of classes to look for, to expectation of nested DOM elements, all the way to philosophical differences about WHERE to actually show messages).  I think that a "strategy" is a decent name for it, it's a class that informs the validation plugin about what the heck to do with the results of its validation: sounds like a strategy to me :smile:
The changes merged in previously were pretty dramatic, I'm just prepping a new PR (since this would take far less time than manually merging and changing files in my existing commits)

closed in favor of #143


Adapt structure to allow separation of multiple organizations

Is your feature request related to a problem?

Artemis is currently been used in projects where an instance is hosted for multiple universities and other educational organizations. Some difficulties occur to provide a meaningful separation between them (ex. Students self registration to courses of their own organization, allow instructors to view only users of the same organization, ..).
Describe the solution you'd like

A possible solution would be to map an additional column to the user's entity representing the relative organization. This would provide additional data needed to solve the separation problem previously described.
Describe alternatives you've considered

Currently, regex pattern over the login and email of users is used to retrieve the needed information (ex. the email's domain includes the information about the user's organization). Unfortunately, this is by far not an optimal solution.
Additional context

Proposal of the user's and course's mapping to an organization

I think those database changes make a lot of sense, I would only do some minor changes:

Organisation -> Organization
add emailPattern to Organization to automatically add users to organizations during startup and to add organization to users when those are created
logo should be stored as string (i.e. a url). You can use the same implementation as for the course icon

To be discussed: should the many to many relationships be ordered (Set vs. List). I would say no. Using a Set will be much easier.

I think those database changes make a lot of sense, I would only do some minor changes:

Organisation -> Organization
add emailPattern to Organization to automatically add users to organizations during startup and to add organization to users when those are created
logo should be stored as string (i.e. a url). You can use the same implementation as for the course icon

To be discussed: should the many to many relationships be ordered (Set vs. List). I would say no. Using a Set will be much easier.

Thanks for the suggestions :+1: The diagram has now been adapted

Thanks for the suggestions :+1: The diagram has now been adapted

@krusche can we close this issue?


Is there pretrained model of R50+ViT_16 for 512x512 input?

Hi, thanks for the great work.
I just wonder that you have the pretrained models of R50+ViT_16.
In your article, you said all R50 and ViT are pretrained on ImageNet and you showed the experimental results for 512x512 input.
But I can't find the pretrained models for ViT of 512x512 input.

@gwang-kim  did you get the solution or way to train 512x512 as the paper was based on 512x512?


Added the target revisions scaling down into the Spec.StageTargetRevisions

Changes

If over-consumption-ratio is set to 100, add the initial revisions or the revisions in the status into Spec.StageTargetRevisions, marking them as scaling down.
If there is only one pod running for the old revision, there is nothing to improve, as the DeletionTimestamp is not available for the pod, we cannot force-delete the pod. Kubernetes in this case, may take longer time to add the DeletionTimestamp.

/kind

Fixes #191

Release Note

Docs

/cherry-pick release-1.14


Evaluating the function 'FlaUI.Core.AutomationElements.Window.ContextMenu.get' timed out

FlaUI.Core: v1.3.0
When debugging in Visual Studio the FlaUI.Core.AutomationElements.Window.ContextMenu is timed out.

Is there some other information that I can provide?

Keep in mind that if you debug and set a breakpoint, the context menu will immediately close when the breakpoint is hit (because the application with the context menu looses focus and visual studio gets the focus). Might this be the issue?

What I´m trying to do is to see what objects are available on a "main" window level.
So if I break after attaching to the process and try to expand the Window object I get the timeout.
This means the menu have never been expanded, so I guess there should not be any objects under the Window context menu.
By the way, I really like the framework and thank you for all the work put into it!


Use the kernels merge_config.sh instead of generate-config.pl

Per information I've been given, we should probably be using https://github.com/torvalds/linux/blob/60bef52c7a68257048f34ce32b8300def71a3de0/scripts/kconfig/merge_config.sh to merge our extra kernel configuration options into the kernel configuration, instead of whatever we do in generate-config.pl.
Is there any reason this was avoided or is it coincidental?
cc @teto @Infinisil @edolstra
I'm told generate-config is naive and it's an existing problem that dependencies of settings will not be enabled when you enable a setting, leading to somewhat obscure errors mostly of the form:
Error in reading or end of file.

when configuring the kernel, in the linux-config derivation.
Edit:
I wouldn't call it naive, I am sure that these problems can be fixed with the script. The actual issue is the dependency handling, so that should be fixed. Whether it is done by changing the script for fixing the current one doesn't matter.

Eelco has observed generate-config appears to predate merge_config.sh.

Not stale, getting rid of generate-config.pl would make enabling LTO'd kernels easier.

I'm working on this during OceanSprint and it's highly nontrivial, the issue being that merge_config.sh doesn't support the autoModules thing we use, which happens to be load-bearing.
Without autoModules nothing works and work is needed to refactor commonConfig to also enable all the dependencies for what it needs.


ci: add ci/skip/multi-arch-build label

If the ci/skip/multi-arch-build label is set on a PR, the GitHub
Workflow only builds for the local architecture. This makes it possible
to merge PRs faster.

Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

/retest ci/centos/<job-name>: retest the <job-name> after unrelated
failure (please report the failure too!)
/retest all: run this in case the CentOS CI failed to start/report any test
progress or results

@nixpanic its a good addition.. however what are the classifications here to build only for local arch?

@nixpanic its a good addition.. however what are the classifications here to build only for local arch?

What do you mean with "classifications"?


Daniil: Watch +44 7404 024203

Daniil requests the watch of the watch_number +44 7404 024203. See the MS search here and the Stack Exchange search here.

Approved by Makyen in Charcoal HQ


a small bug in "experiments/movingmnist/mnist_rnn_main.py"

In the function "train" line 120, when creating a moving mnist factory,  the parameter ctx_num is omitted, while the parameter batch_size is still divided by the number of gpus. This will cause dimension mismatch when running the file with multiple gpus.

Yeah, thanks for pointing out this bug. I haven't tried using multiple GPUs for the MovingMNIST experiments.


pkgs

nitch isn't displaying the packages correctly on gentoo.
it says pkgs: >3

using st terminal

I will add packages count for gentoo in the near future.

Great! It also complained about me not having an /etc/hostname file, since hostname is usually defined at /etc/conf.d/hostname in openrc, but that was easily solvable.

I will add packages count for gentoo in the near future.

Does the same thing on my Raspberry Pi running ArchLinuxARM


Some confusion on Cyber RT's ShareMemory communication mechanism

Hi, folks
I've learned Cyber RT recently, got some information about its message transport mechanisms. Shared memory, as one of them, is used often. But I have some questions concerning to it, detailed as below:

In file */cyber/transport/shm/shm_conf.h, some code snippet as follows:
// Extra size, Bit
static const uint64_t EXTRA_SIZE;
 // State size, Bit
static const uint64_t STATE_SIZE;
// Block size, Bit
 static const uint64_t BLOCK_SIZE;
// Message info size, Bit
 static const uint64_t MESSAGE_INFO_SIZE;

The "Bit" in the comment is meaning the minimum information bit or byte?
If it means bit, I think the code snippet below (from shm_conf.cc) should be corrected.
uint64_t ShmConf::GetBlockBufSize(const uint64_t& ceiling_msg_size) {
return ceiling_msg_size + MESSAGE_INFO_SIZE;
}
void ShmConf::Update(const uint64_t& real_msg_size) {
ceiling_msg_size_ = GetCeilingMessageSize(real_msg_size);
block_buf_size_ = GetBlockBufSize(ceiling_msg_size_);
block_num_ = GetBlockNum(ceiling_msg_size_);
managed_shm_size_ =
EXTRA_SIZE + STATE_SIZE + (BLOCK_SIZE + block_buf_size_) * block_num_;
}
Statement return ceiling_msg_size + MESSAGE_INFO_SIZE; should be change to return ceiling_msg_size + MESSAGE_INFO_SIZE << 3;
Member variable managed_shm_size_ should be assigned to EXTRA_SIZE << 3 + STATE_SIZE << 3 + (BLOCK_SIZE << 3 + block_buf_size) * block_num_;_

Under most circumstances, I think the Segment object created should not be remapped, since the parties need to use it can not know the changes unless by others notifications, but now Cyber RT seems couldn't let other parties to be notified when co-mmaped Segment's block size is changed.

In my case, I changed SysV share memory API shmget series to POSIX version shm_open series, and the default message size is MESSAGE_SIZE_16K, evidence: ShmConf::ShmConf() { Update(MESSAGE_SIZE_16K); }, compiled and run apollo, it coredumped often. I changed this argument to MESSAGE_SIZE_128K, the phenomenon also exists, but less frequency. I changed to MESSAGE_SIZE_1M or MESSAGE_SIZE_8M, the phenomenon disappeared, and the apollo run normally as before. During debug the core file, I find the code crashed many times from the remap operation, so I suspect it may be the cause.
Any ideas or insights, thanks in advance!
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04):Linux Ubuntu 16.04
Apollo installed from (source or binary):source
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0):3.5

Sorry for typo, all "<< 3" should be ">> 3".

Hi, folks
I've learned Cyber RT recently, got some information about its message transport mechanisms. Shared memory, as one of them, is used often. But I have some questions concerning to it, detailed as below:

In file */cyber/transport/shm/shm_conf.h, some code snippet as follows:
// Extra size, Bit
static const uint64_t EXTRA_SIZE;
   // State size, Bit
static const uint64_t STATE_SIZE;
// Block size, Bit
 static const uint64_t BLOCK_SIZE;
// Message info size, Bit
 static const uint64_t MESSAGE_INFO_SIZE;

The "Bit" in the comment is meaning the minimum information bit or byte?
If it means bit, I think the code snippet below (from shm_conf.cc) should be corrected.
uint64_t ShmConf::GetBlockBufSize(const uint64_t& ceiling_msg_size) {
return ceiling_msg_size + MESSAGE_INFO_SIZE;
}
void ShmConf::Update(const uint64_t& real_msg_size) {
ceiling_msg_size_ = GetCeilingMessageSize(real_msg_size);
block_buf_size_ = GetBlockBufSize(ceiling_msg_size_);
block_num_ = GetBlockNum(ceiling_msg_size_);
managed_shm_size_ =
EXTRA_SIZE + STATE_SIZE + (BLOCK_SIZE + block_buf_size_) * block_num_;
}
Statement return ceiling_msg_size + MESSAGE_INFO_SIZE; should be change to return ceiling_msg_size + MESSAGE_INFO_SIZE << 3;
Member variable managed_shm_size_ should be assigned to EXTRA_SIZE << 3 + STATE_SIZE << 3 + (BLOCK_SIZE << 3 + block_buf_size) * block_num_;_

Under most circumstances, I think the Segment object created should not be remapped, since the parties need to use it can not know the changes unless by others notifications, but now Cyber RT seems couldn't let other parties to be notified when co-mmaped Segment's block size is changed.

In my case, I changed SysV share memory API shmget series to POSIX version shm_open series, and the default message size is MESSAGE_SIZE_16K, evidence: ShmConf::ShmConf() { Update(MESSAGE_SIZE_16K); }, compiled and run apollo, it coredumped often. I changed this argument to MESSAGE_SIZE_128K, the phenomenon also exists, but less frequency. I changed to MESSAGE_SIZE_1M or MESSAGE_SIZE_8M, the phenomenon disappeared, and the apollo run normally as before. During debug the core file, I find the code crashed many times from the remap operation, so I suspect it may be the cause.
Any ideas or insights, thanks in advance!
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04):Linux Ubuntu 16.04
Apollo installed from (source or binary):source
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0):3.5

Hi Tony,
Thank you very much to point out the wrong comment in shm_conf.h! We will correct it as soon as possible.
For question 2, maybe you need check the process of Recreation after replacing the SysV with POSIX.
Thanks again for your contribution to the Apollo!

@gruminions Thank you very much for quick reply！

Closed for now.
Please reopen if you have further questions!


Document outline

Home
Application

Introduction
How to use

Videos
Requirements and User Stories

Requirements
User Stories

Hardware Setup

Overview
Sensor
Required Module Setup

Software Design

Program Structure
GUI Design
UnitTest

Team Contribution

Document done.


Update WSUB_ExtData.yaml

Added correction for L72. A better fix would select the folder depending on vertical resolutionn.

Added correction for L72. A better fix would select the folder depending on vertical resolutionn.

@dbarahon I believe @bena-nasa has something in his todo list to 'template' the vertical bits of these files, but for now, we have bits in scripting that substitute in the right level numbers.


Cant log in - #<NoMethodError: undefined method `current_sign_in_at' for #User:0x000055e053c79c58>

I can't seem to be able to sign in, even though creating users works without a problem.
I added the gems into my Gemfile:
gem 'devise'
gem 'devise_token_auth'

I run the following commands:
$ bundle
$ rails generate devise:install
$ rails generate devise_token_auth:install User auth
$ rails db:migrate

This is my routes then:
$ rails routes
                  Prefix Verb   URI Pattern                                            Controller#Action
        new_user_session GET    /auth/sign_in(.:format)                                devise_token_auth/sessions#new
            user_session POST   /auth/sign_in(.:format)                                devise_token_auth/sessions#create
    destroy_user_session DELETE /auth/sign_out(.:format)                               devise_token_auth/sessions#destroy
       new_user_password GET    /auth/password/new(.:format)                           devise_token_auth/passwords#new
      edit_user_password GET    /auth/password/edit(.:format)                          devise_token_auth/passwords#edit
           user_password PATCH  /auth/password(.:format)                               devise_token_auth/passwords#update
                         PUT    /auth/password(.:format)                               devise_token_auth/passwords#update
                         POST   /auth/password(.:format)                               devise_token_auth/passwords#create
cancel_user_registration GET    /auth/cancel(.:format)                                 devise_token_auth/registrations#cancel
   new_user_registration GET    /auth/sign_up(.:format)                                devise_token_auth/registrations#new
  edit_user_registration GET    /auth/edit(.:format)                                   devise_token_auth/registrations#edit
       user_registration PATCH  /auth(.:format)                                        devise_token_auth/registrations#update
                         PUT    /auth(.:format)                                        devise_token_auth/registrations#update
                         DELETE /auth(.:format)                                        devise_token_auth/registrations#destroy
                         POST   /auth(.:format)                                        devise_token_auth/registrations#create
     auth_validate_token GET    /auth/validate_token(.:format)                         devise_token_auth/token_validations#validate_token

If I try to login with wrong credentials, I get this message:
{
    "success": false,
    "errors": [
        "Invalid login credentials. Please try again."
    ]
}

But if I try to login with the right credentials, I get this message:

    "status": 500,
    "error": "Internal Server Error",
    "exception": "#<NoMethodError: undefined method `current_sign_in_at' for #<User:0x00007f6bf80e4640>>",
    "traces": {
        "Application Trace": [],
        "Framework Trace": [
            {
                "id": 0,
                "trace": "activemodel (5.2.3) lib/active_model/attribute_methods.rb:430:in `method_missing'"
            },
            {
                "id": 1,
                "trace": "devise (4.6.2) lib/devise/models/trackable.rb:21:in `update_tracked_fields'"
            },
            {
                "id": 2,
                "trace": "devise (4.6.2) lib/devise/models/trackable.rb:39:in `update_tracked_fields!'"
            },
            {
                "id": 3,
                "trace": "devise (4.6.2) lib/devise/hooks/trackable.rb:9:in `block in <top (required)>'"
            },
            {
                "id": 4,
                "trace": "warden (1.2.8) lib/warden/hooks.rb:15:in `block in _run_callbacks'"
            },
            {
                "id": 5,
                "trace": "warden (1.2.8) lib/warden/hooks.rb:10:in `each'"
            },
            {
                "id": 6,
                "trace": "warden (1.2.8) lib/warden/hooks.rb:10:in `_run_callbacks'"
            },
            {
                "id": 7,
                "trace": "warden (1.2.8) lib/warden/manager.rb:52:in `_run_callbacks'"
            },
            {
                "id": 8,
                "trace": "warden (1.2.8) lib/warden/proxy.rb:191:in `set_user'"
            },
            {
                "id": 9,
                "trace": "devise (4.6.2) lib/devise/controllers/sign_in_out.rb:53:in `sign_in'"
            },
            {
                "id": 10,
                "trace": "devise_token_auth (1.1.0) app/controllers/devise_token_auth/sessions_controller.rb:32:in `create'"
            },
            {
                "id": 11,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'"
            },
            {
                "id": 12,
                "trace": "actionpack (5.2.3) lib/abstract_controller/base.rb:194:in `process_action'"
            },
            {
                "id": 13,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/rendering.rb:30:in `process_action'"
            },
            {
                "id": 14,
                "trace": "actionpack (5.2.3) lib/abstract_controller/callbacks.rb:42:in `block in process_action'"
            },
            {
                "id": 15,
                "trace": "activesupport (5.2.3) lib/active_support/callbacks.rb:132:in `run_callbacks'"
            },
            {
                "id": 16,
                "trace": "actionpack (5.2.3) lib/abstract_controller/callbacks.rb:41:in `process_action'"
            },
            {
                "id": 17,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/rescue.rb:22:in `process_action'"
            },
            {
                "id": 18,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/instrumentation.rb:34:in `block in process_action'"
            },
            {
                "id": 19,
                "trace": "activesupport (5.2.3) lib/active_support/notifications.rb:168:in `block in instrument'"
            },
            {
                "id": 20,
                "trace": "activesupport (5.2.3) lib/active_support/notifications/instrumenter.rb:23:in `instrument'"
            },
            {
                "id": 21,
                "trace": "activesupport (5.2.3) lib/active_support/notifications.rb:168:in `instrument'"
            },
            {
                "id": 22,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/instrumentation.rb:32:in `process_action'"
            },
            {
                "id": 23,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/params_wrapper.rb:256:in `process_action'"
            },
            {
                "id": 24,
                "trace": "activerecord (5.2.3) lib/active_record/railties/controller_runtime.rb:24:in `process_action'"
            },
            {
                "id": 25,
                "trace": "actionpack (5.2.3) lib/abstract_controller/base.rb:134:in `process'"
            },
            {
                "id": 26,
                "trace": "actionpack (5.2.3) lib/action_controller/metal.rb:191:in `dispatch'"
            },
            {
                "id": 27,
                "trace": "actionpack (5.2.3) lib/action_controller/metal.rb:252:in `dispatch'"
            },
            {
                "id": 28,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/route_set.rb:52:in `dispatch'"
            },
            {
                "id": 29,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/route_set.rb:34:in `serve'"
            },
            {
                "id": 30,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/mapper.rb:18:in `block in <class:Constraints>'"
            },
            {
                "id": 31,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/mapper.rb:48:in `serve'"
            },
            {
                "id": 32,
                "trace": "actionpack (5.2.3) lib/action_dispatch/journey/router.rb:52:in `block in serve'"
            },
            {
                "id": 33,
                "trace": "actionpack (5.2.3) lib/action_dispatch/journey/router.rb:35:in `each'"
            },
            {
                "id": 34,
                "trace": "actionpack (5.2.3) lib/action_dispatch/journey/router.rb:35:in `serve'"
            },
            {
                "id": 35,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/route_set.rb:840:in `call'"
            },
            {
                "id": 36,
                "trace": "warden (1.2.8) lib/warden/manager.rb:36:in `block in call'"
            },
            {
                "id": 37,
                "trace": "warden (1.2.8) lib/warden/manager.rb:34:in `catch'"
            },
            {
                "id": 38,
                "trace": "warden (1.2.8) lib/warden/manager.rb:34:in `call'"
            },
            {
                "id": 39,
                "trace": "rack (2.0.7) lib/rack/etag.rb:25:in `call'"
            },
            {
                "id": 40,
                "trace": "rack (2.0.7) lib/rack/conditional_get.rb:38:in `call'"
            },
            {
                "id": 41,
                "trace": "rack (2.0.7) lib/rack/head.rb:12:in `call'"
            },
            {
                "id": 42,
                "trace": "activerecord (5.2.3) lib/active_record/migration.rb:559:in `call'"
            },
            {
                "id": 43,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/callbacks.rb:28:in `block in call'"
            },
            {
                "id": 44,
                "trace": "activesupport (5.2.3) lib/active_support/callbacks.rb:98:in `run_callbacks'"
            },
            {
                "id": 45,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/callbacks.rb:26:in `call'"
            },
            {
                "id": 46,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/executor.rb:14:in `call'"
            },
            {
                "id": 47,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/debug_exceptions.rb:61:in `call'"
            },
            {
                "id": 48,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'"
            },
            {
                "id": 49,
                "trace": "railties (5.2.3) lib/rails/rack/logger.rb:38:in `call_app'"
            },
            {
                "id": 50,
                "trace": "railties (5.2.3) lib/rails/rack/logger.rb:26:in `block in call'"
            },
            {
                "id": 51,
                "trace": "activesupport (5.2.3) lib/active_support/tagged_logging.rb:71:in `block in tagged'"
            },
            {
                "id": 52,
                "trace": "activesupport (5.2.3) lib/active_support/tagged_logging.rb:28:in `tagged'"
            },
            {
                "id": 53,
                "trace": "activesupport (5.2.3) lib/active_support/tagged_logging.rb:71:in `tagged'"
            },
            {
                "id": 54,
                "trace": "railties (5.2.3) lib/rails/rack/logger.rb:26:in `call'"
            },
            {
                "id": 55,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/remote_ip.rb:81:in `call'"
            },
            {
                "id": 56,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/request_id.rb:27:in `call'"
            },
            {
                "id": 57,
                "trace": "rack (2.0.7) lib/rack/runtime.rb:22:in `call'"
            },
            {
                "id": 58,
                "trace": "activesupport (5.2.3) lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'"
            },
            {
                "id": 59,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/executor.rb:14:in `call'"
            },
            {
                "id": 60,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/static.rb:127:in `call'"
            },
            {
                "id": 61,
                "trace": "rack (2.0.7) lib/rack/sendfile.rb:111:in `call'"
            },
            {
                "id": 62,
                "trace": "rack-cors (1.0.3) lib/rack/cors.rb:95:in `call'"
            },
            {
                "id": 63,
                "trace": "railties (5.2.3) lib/rails/engine.rb:524:in `call'"
            },
            {
                "id": 64,
                "trace": "puma (3.12.1) lib/puma/configuration.rb:227:in `call'"
            },
            {
                "id": 65,
                "trace": "puma (3.12.1) lib/puma/server.rb:660:in `handle_request'"
            },
            {
                "id": 66,
                "trace": "puma (3.12.1) lib/puma/server.rb:474:in `process_client'"
            },
            {
                "id": 67,
                "trace": "puma (3.12.1) lib/puma/server.rb:334:in `block in run'"
            },
            {
                "id": 68,
                "trace": "puma (3.12.1) lib/puma/thread_pool.rb:135:in `block in spawn_thread'"
            }
        ],
        "Full Trace": [
            {
                "id": 0,
                "trace": "activemodel (5.2.3) lib/active_model/attribute_methods.rb:430:in `method_missing'"
            },
            {
                "id": 1,
                "trace": "devise (4.6.2) lib/devise/models/trackable.rb:21:in `update_tracked_fields'"
            },
            {
                "id": 2,
                "trace": "devise (4.6.2) lib/devise/models/trackable.rb:39:in `update_tracked_fields!'"
            },
            {
                "id": 3,
                "trace": "devise (4.6.2) lib/devise/hooks/trackable.rb:9:in `block in <top (required)>'"
            },
            {
                "id": 4,
                "trace": "warden (1.2.8) lib/warden/hooks.rb:15:in `block in _run_callbacks'"
            },
            {
                "id": 5,
                "trace": "warden (1.2.8) lib/warden/hooks.rb:10:in `each'"
            },
            {
                "id": 6,
                "trace": "warden (1.2.8) lib/warden/hooks.rb:10:in `_run_callbacks'"
            },
            {
                "id": 7,
                "trace": "warden (1.2.8) lib/warden/manager.rb:52:in `_run_callbacks'"
            },
            {
                "id": 8,
                "trace": "warden (1.2.8) lib/warden/proxy.rb:191:in `set_user'"
            },
            {
                "id": 9,
                "trace": "devise (4.6.2) lib/devise/controllers/sign_in_out.rb:53:in `sign_in'"
            },
            {
                "id": 10,
                "trace": "devise_token_auth (1.1.0) app/controllers/devise_token_auth/sessions_controller.rb:32:in `create'"
            },
            {
                "id": 11,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'"
            },
            {
                "id": 12,
                "trace": "actionpack (5.2.3) lib/abstract_controller/base.rb:194:in `process_action'"
            },
            {
                "id": 13,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/rendering.rb:30:in `process_action'"
            },
            {
                "id": 14,
                "trace": "actionpack (5.2.3) lib/abstract_controller/callbacks.rb:42:in `block in process_action'"
            },
            {
                "id": 15,
                "trace": "activesupport (5.2.3) lib/active_support/callbacks.rb:132:in `run_callbacks'"
            },
            {
                "id": 16,
                "trace": "actionpack (5.2.3) lib/abstract_controller/callbacks.rb:41:in `process_action'"
            },
            {
                "id": 17,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/rescue.rb:22:in `process_action'"
            },
            {
                "id": 18,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/instrumentation.rb:34:in `block in process_action'"
            },
            {
                "id": 19,
                "trace": "activesupport (5.2.3) lib/active_support/notifications.rb:168:in `block in instrument'"
            },
            {
                "id": 20,
                "trace": "activesupport (5.2.3) lib/active_support/notifications/instrumenter.rb:23:in `instrument'"
            },
            {
                "id": 21,
                "trace": "activesupport (5.2.3) lib/active_support/notifications.rb:168:in `instrument'"
            },
            {
                "id": 22,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/instrumentation.rb:32:in `process_action'"
            },
            {
                "id": 23,
                "trace": "actionpack (5.2.3) lib/action_controller/metal/params_wrapper.rb:256:in `process_action'"
            },
            {
                "id": 24,
                "trace": "activerecord (5.2.3) lib/active_record/railties/controller_runtime.rb:24:in `process_action'"
            },
            {
                "id": 25,
                "trace": "actionpack (5.2.3) lib/abstract_controller/base.rb:134:in `process'"
            },
            {
                "id": 26,
                "trace": "actionpack (5.2.3) lib/action_controller/metal.rb:191:in `dispatch'"
            },
            {
                "id": 27,
                "trace": "actionpack (5.2.3) lib/action_controller/metal.rb:252:in `dispatch'"
            },
            {
                "id": 28,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/route_set.rb:52:in `dispatch'"
            },
            {
                "id": 29,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/route_set.rb:34:in `serve'"
            },
            {
                "id": 30,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/mapper.rb:18:in `block in <class:Constraints>'"
            },
            {
                "id": 31,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/mapper.rb:48:in `serve'"
            },
            {
                "id": 32,
                "trace": "actionpack (5.2.3) lib/action_dispatch/journey/router.rb:52:in `block in serve'"
            },
            {
                "id": 33,
                "trace": "actionpack (5.2.3) lib/action_dispatch/journey/router.rb:35:in `each'"
            },
            {
                "id": 34,
                "trace": "actionpack (5.2.3) lib/action_dispatch/journey/router.rb:35:in `serve'"
            },
            {
                "id": 35,
                "trace": "actionpack (5.2.3) lib/action_dispatch/routing/route_set.rb:840:in `call'"
            },
            {
                "id": 36,
                "trace": "warden (1.2.8) lib/warden/manager.rb:36:in `block in call'"
            },
            {
                "id": 37,
                "trace": "warden (1.2.8) lib/warden/manager.rb:34:in `catch'"
            },
            {
                "id": 38,
                "trace": "warden (1.2.8) lib/warden/manager.rb:34:in `call'"
            },
            {
                "id": 39,
                "trace": "rack (2.0.7) lib/rack/etag.rb:25:in `call'"
            },
            {
                "id": 40,
                "trace": "rack (2.0.7) lib/rack/conditional_get.rb:38:in `call'"
            },
            {
                "id": 41,
                "trace": "rack (2.0.7) lib/rack/head.rb:12:in `call'"
            },
            {
                "id": 42,
                "trace": "activerecord (5.2.3) lib/active_record/migration.rb:559:in `call'"
            },
            {
                "id": 43,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/callbacks.rb:28:in `block in call'"
            },
            {
                "id": 44,
                "trace": "activesupport (5.2.3) lib/active_support/callbacks.rb:98:in `run_callbacks'"
            },
            {
                "id": 45,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/callbacks.rb:26:in `call'"
            },
            {
                "id": 46,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/executor.rb:14:in `call'"
            },
            {
                "id": 47,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/debug_exceptions.rb:61:in `call'"
            },
            {
                "id": 48,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'"
            },
            {
                "id": 49,
                "trace": "railties (5.2.3) lib/rails/rack/logger.rb:38:in `call_app'"
            },
            {
                "id": 50,
                "trace": "railties (5.2.3) lib/rails/rack/logger.rb:26:in `block in call'"
            },
            {
                "id": 51,
                "trace": "activesupport (5.2.3) lib/active_support/tagged_logging.rb:71:in `block in tagged'"
            },
            {
                "id": 52,
                "trace": "activesupport (5.2.3) lib/active_support/tagged_logging.rb:28:in `tagged'"
            },
            {
                "id": 53,
                "trace": "activesupport (5.2.3) lib/active_support/tagged_logging.rb:71:in `tagged'"
            },
            {
                "id": 54,
                "trace": "railties (5.2.3) lib/rails/rack/logger.rb:26:in `call'"
            },
            {
                "id": 55,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/remote_ip.rb:81:in `call'"
            },
            {
                "id": 56,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/request_id.rb:27:in `call'"
            },
            {
                "id": 57,
                "trace": "rack (2.0.7) lib/rack/runtime.rb:22:in `call'"
            },
            {
                "id": 58,
                "trace": "activesupport (5.2.3) lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'"
            },
            {
                "id": 59,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/executor.rb:14:in `call'"
            },
            {
                "id": 60,
                "trace": "actionpack (5.2.3) lib/action_dispatch/middleware/static.rb:127:in `call'"
            },
            {
                "id": 61,
                "trace": "rack (2.0.7) lib/rack/sendfile.rb:111:in `call'"
            },
            {
                "id": 62,
                "trace": "rack-cors (1.0.3) lib/rack/cors.rb:95:in `call'"
            },
            {
                "id": 63,
                "trace": "railties (5.2.3) lib/rails/engine.rb:524:in `call'"
            },
            {
                "id": 64,
                "trace": "puma (3.12.1) lib/puma/configuration.rb:227:in `call'"
            },
            {
                "id": 65,
                "trace": "puma (3.12.1) lib/puma/server.rb:660:in `handle_request'"
            },
            {
                "id": 66,
                "trace": "puma (3.12.1) lib/puma/server.rb:474:in `process_client'"
            },
            {
                "id": 67,
                "trace": "puma (3.12.1) lib/puma/server.rb:334:in `block in run'"
            },
            {
                "id": 68,
                "trace": "puma (3.12.1) lib/puma/thread_pool.rb:135:in `block in spawn_thread'"
            }
        ]
    }

I am using ruby 2.5.1 and rails 5.2.3
What is wrong??

I solved this by installing version one of the gem as:
gem 'devise_token_auth', '1.0.0'

I run the following commands:
$ bundle install
$ rails generate devise_token_auth:install User auth
$ rails db:migrate

Note that you don't have to install devise yourself.

Just got this error, too. Tried downgrading to '1.0.0' but no luck yet

@farverio

It appears Devise might have made some breaking changes that require trackable by default

Are you sure? Check https://github.com/plataformatec/devise/pull/4857
I removed that field and it worked for me so you might be using the trackable module

@enriquemorenotent What devise version do you have? What devise modules do you have?

Devise no longer includes Trackable in its model generator. If you need Trackable, generate a migration with the fields mentioned by @farverio. Otherwise, remove :trackable devise configuration option from your user class.


Bypass mandrill for local installation?

Hey, this project seems pretty cool!
  I was able to get the server running locally, but I don't have a Mandrill account.  Do you happen to know of a quick tweak I could make to bypass the Mandrill requirement?  Maybe I can hardcode a single account, for instance?
Thanks for your time.

@ajhyndman Yes, you can. You can set a single account to active using Mongol (or some other tool) quite easily. You could also change the Mail URL to use a different service, such as Postmark.

(Speaking of which, now that Mandrill has shut down its free plans, I should switch to Postmark or Mailgun.)

Thanks for the response!  I'll give it a shot.


Test PR for the ci centos

[test]

@hectorj2f snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1996-fabric8-planner.int.rdu2c.fabric8.io

Closing this PR! We don't need it anymore


Roslynator discussion

Setup errors when rules are broken or just warnings: https://github.com/JosefPihrt/Roslynator/blob/master/src/Analyzers/README.md
Setup refactorings or not: https://github.com/JosefPihrt/Roslynator/blob/master/src/Refactorings/README.md

Still awaiting a proper answer to the issue...
https://github.com/JosefPihrt/Roslynator/issues/775

Opened a new issue for this:
https://github.com/jokk-itu/PythonKindergarten/issues/113


Use serenata_toolbox whenever possible

https://github.com/datasciencebr/serenata-toolbox was created to keep code shared between different Serenata de Amor projects. If the script is already there, the code should be removed from here and used from the package.

I think we should add this to the README file so we can ask people to use it, letting it on an issue is not so accessible as it must be.

Almost agree, but CONTRIBUTING.md is where this info is gonna be added IMHO
On Wed, 7 Dec 2016 at 11:25 Vinicius Mesel<EMAIL_ADDRESS>wrote:

I think we should add this to the README file so we can ask people to use
it, letting it on an issue is not so accessible as it must be.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/datasciencebr/serenata-de-amor/issues/143#issuecomment-265446163,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEg385rT091n7cznd47SH8OiSD05f3x0ks5rFrPCgaJpZM4K4GKI
.

I was willing to give this a shot but it seems that the package is not on pypi yet, any recommendations on how to leverage that here? (git submodules, wget, something else...)

We can install directly from GitHub with the -e argument ; )
On Fri, 9 Dec 2016 at 13:23 Fabio Rehm<EMAIL_ADDRESS>wrote:

I was willing to give this a shot but it seems that the package is not on
pypi yet https://pypi.python.org/pypi/serenata_toolbox/, any
recommendations on how to leverage that here? (git submodules, wget,
something else...)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/datasciencebr/serenata-de-amor/issues/143#issuecomment-266039795,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEg38-ugzmwBmDv_uegaK99i3XsT7tzSks5rGXJ_gaJpZM4K4GKI
.

Talking with @Irio what's missing:

Add the serenata-toolbox to requirements.txt
We need to use serenata-toolbox in the notebooks

@jtemporal

feedback:

[x] Add the serenata-toolbox to requirements.txt
[x] Make sure that serenata toolbox works on the notebooks
[ ] Remove from src all code that is already in the toolbox
[ ] Check/Update documentation


Does the test set for the Semantic3D dataset have no label?

Does the test set for the Semantic3D dataset have no label? Do I have to do an online test to get the final prediction miou？

Exactly.

Exactly.

Thanks


Add Typescript declarations, alias Provider as TranslationProvider

Coverage remained the same at 100.0% when pulling 4ba57881fb0d8f10a6eaa15f89934bfa937911f9 on typescript-declarations into d954bf8d3e983bffe6507789feb919b174b57544 on master.

Looks lovely, thank you. I'd also be happy to just convert codebase to typescript as well next time we need to make some changes, it's a tiny tiny codebase.

@Tankenstein I did actually start doing this, in the hope that it would automatically produce the type declarations that we needed. Unfortunately it doesn't seem to be the case with webpack builds, writing the declarations file manually is the most practical way to achieve it.


Create fake datasets for the Tag entity

Objective
Using the tag schema created by the team, create 20 or more database entries to act as “potential” internship tags for students/users to view from our database.
Requirements

Must follow the schema for tags
Must be entered into our database

Issue
So I tested the .csv files to see if I could copy them into our database and receive the following results:

.csv files can indeed be copied into our postgres database
[issue] the columns/attributes you've created aren't matching the schema's that were created for their respective entities.

For Example: tag.csv -> tag Schema
.csv file reads: (tag_id,semester)
schema reads: (tag_id, description)
Because we are missing a column like "description" the .csv file will fail to copy.
SIDE NOTE: id's must match across the different files i.e (tag_id for an entry must contain the same value in every file it's used.)
Reference


chore(Data/Int/Cast): fix confusion between OfNat and Nat.cast lemmas

This renames

Int.cast_ofNat to Int.cast_natCast
Int.int_cast_ofNat to Int.cast_ofNat

I think the history here is that this lemma was previously about Int.ofNat, before we globally fixed the simp-normal form to be Nat.cast.
Since the Int.cast_ofNat name is repurposed, it can't be deprecated. Int.int_cast_ofNat is such a wonky name that it was probably never used.

Could you also rename AddGroupWithOne.intCast_ofNat? It refers to Nat.cast, I just checked.

Let's do that in a separate PR, to avoid picking up more conflicts.

Looks good, thanks!
bors merge


Using this in Lovelace "mini-media-player"

Has anyone tried to use this as a media_player entity in the "mini-media-player" Lovelace addon?
Having trouble with two things...

When trying to use the power toggle, in either mode, it fails with error.  Not sure if this is due to "mini-media-player" or "ha_hatch".

I can't seem to get "sound_mode" from the Hatch device attribute to come across in any way into "mini-media-player".  Ideally, it would be a dropdown showing a "track list" of the sound options... but at least displaying what the current "track"/"sound_mode" is set to would be great.

Any assistance, insights, etc would be greatly appreciated.

I think I got point 2 worked out...  and I guess point 1 is moot in the end.
Here's my YAML.
- entity: media_player.bess_media_player
name: Hatch
icon: mdi:sleep
type: custom:mini-media-player
sound_mode: full
mini-media-player-overlay-color-stop: 10%
hide:
source: true
info: true
power_state: true
icon_state: false
volume_level: false
power: true
sound_mode: false
mute: true
next: true
prev: true
progress: true
play_pause: true
play_stop: false
state_label: true


Bump analyzer to ^6.0.0

I'm using riverpod_lint in my project and it declares analyzer: ">=6.0.0 <7.0.0"

New version is live: 2.0.2


inlay hints: add the option to always show constructor inlay hints

This PR adds a config to disable the functionality in #10441.
I actually really like inlay hints always showing up, and it helps a lot as a teaching tool too, and also it's quite reassuring to know that r-a indeed understands the code I've written. This PR adds the option rust-analyzer.inlayHints.hideNamedConstructorHints (i can also invert this to be rust-analyzer.inlayHints.showNamedConstructorHints, just let me know.)

I'm totally cool with changing the default to always show inlay hints. I think it is confusing if inlay hints sometimes show and do not show. But I also didn't want to essentially erase the functionality in 10441 by making it the non-default (most people don't really change config.)
But if you agree that always showing inlay hints is a more sensible default (and I concur with this), I'll flip the default.

While we do want to make everthing as much as discoverable we should still keep sensible defaults in mind imo, and this one is one of them. I feel like people would not easily realize that a type hint is missing because of a constructor(in fact even though I implemented that feature I at times wondered why the type hint was missing for a moment), I personally think this feature is more confusing than helpful as well, though I can see why someone would maybe want it.

Done!

Thanks!
bors r+


Upgrade asv to 0.6.1.

https://github.com/airspeed-velocity/asv/issues/1323
There were some warnings/errors in the workflow which are now gone after the upgrade:
Couldn't load asv.plugins.mamba because
No module named 'mamba'
Couldn't load asv.plugins.virtualenv because
No module named 'packaging'
· No information stored about machine 'fv-az740-515'. I know about nothing.

Couldn't load asv.plugins.mamba because
No module named 'mamba'
Couldn't load asv.plugins.virtualenv because
No module named 'packaging'

See: https://github.com/django/django-asv/actions/runs/7135574098/job/19432587240
If we're lucky this might fix the daily run

OK. Let's try it.


cluster-capi/v3: spec.topology failure

I updated the e2e provisioning to use cluster-capi/v3 (which I tagged after https://github.com/nephio-project/nephio-example-packages/pull/22 merged) and now I get this failure when ConfigSync tries to apply the cluster-capi-kind package:
          KNV2009: failed to apply Cluster.cluster.x-k8s.io, default/edge1-cluster: admission webhook "validation.cluster.cluster.x-k8s.io" denied the request: Cluster.cluster.x-k8s.io "edge1-cluster" is invalid: spec.topology: Forbidden: can be set only if the ClusterTopology feature flag is enabled

I am going to go back to cluster-capi/v2 for now.
/assign @electrocucaracha @henderiw

ok I already know the root cause here as I changed this by hand in the package. To user our features for kind we need to enable topology=true
which by default is set to false. Example below

--feature-gates=MachinePool=false,ClusterTopology=true

PR that should fix it
https://github.com/nephio-project/nephio-example-packages/pull/40

Fixed


Friendship methods

Fixes #4 with 4 methods.

exists_friendship()
show_friendship()
friends_ids()
followers_ids()

Feel free to let me know if there's anything I could've done better. Thanks for your help and I appreciate your promptness in answering my questions.

This looks good, thanks for the help!  I think we just have one more issue to be worked on (status methods), @FreddieV4 is working on the direct messages and looks to be close to finished, and I'm wrapping up the list methods, then we can do an initial release.


Bug report / バグ報告:

** Describe the bug **
A clear and concise description of what the bug is.
Please write what kind of bug is occurring.
the automatic bones/bone choices never show a bones
** To Reproduce / How to reproduce a bug **
Steps to reproduce the behavior:

Go to Vrm addon
Click onHuminoid'
Scroll down to automatic bones productions'
See error and click any bones ** Describe the bug / About bugs **
A clear and concise description of what the bug is.
no bones appear when you select automatic bones
Please write what kind of bug is occurring.
missing bones being able to be selected

** Expected behavior **
A clear and concise description of what you expected to happen.
Please write how you would like the bug fixed.
I would like to show every single bone, so I could choose the right bones rather than being frustrated because I could not see any bones to choose :(
** Screenshots / Screenshots **

If applicable, add screenshots to help explain your problem.
Please attach any screenshots that may be helpful.
** Desktop (please complete the following information) / PC environment information ** Nitro AN5
--OS: [e.g. Windows, macOS, Ubuntu Linux, ...] windows
--Blender [e.g. 2.93.5, 3.1.2, ...] 2.90
--Addon Version [e.g. 2.3.8] 2.3.1
Additional context / なにか他に書いておきたいことはこちらへ
Add any other context about the problem here.
I want to be able to see every single bone to select to assign them to hips and or other things, please

Hi !
VRM has a parent-child relationship for bones in the specification. The addon only shows a drop-down selection of bones that satisfy the relationship. If the bones you want to set in your hips are not showing, even though they meet the specifications, it may be a bug.
If you feel this is a bug, please send me your .blend file. Thanks!

OH OK. let me check

here please look at this https://drive.google.com/file/d/1UqGVhXDRaX5jXeML0amN8-Wr-NAaOlLs/view?usp=sharing

The download is complete. I'll investigate!

OK
Your hips will not be VRM Hips.

VRM spec says
https://vrm.dev/en/univrm/humanoid/humanoid_overview#id3
(root) - hips - spine - chest - upper chest
              + left upper leg
              + right upper leg

Your model is
(root) - hips - chest - upper chest
       + spine + left upper leg
               + right upper leg

It's not a bug.

it is? oh I am sorry terrible sorry I'm new to blender

OK
Your hips will not be VRM Hips.

VRM spec says
https://vrm.dev/en/univrm/humanoid/humanoid_overview#id3
(root) - hips - spine - chest - upper chest
              + left upper leg
              + right upper leg

Your model is
(root) - spine - chest - upper chest
       + hips + left upper leg
              + right upper leg

It's not a bug.

@saturday06 I've made sure to follow this bone hierarchy spec in the attached file and still have no hip bone showing up.

https://drive.google.com/file/d/1m5-KZmnZegjiKiqt7g4MZ43YFPz3llPU/view?usp=sharing

@tdw46 Has the problem been resolved? I opened your blend file and it appears to have the "Hips" set correctly.


add gtex info and logo

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

Create a folder under /tokens, folder name is your token symbol in the lowercase format

Uploade your logo in your folder

[ ] Filename in the uppercase format with suffix
[ ] Image format: png
[ ] Image size: 256 by 256 px

Upload a json file for additional info. File name is your token symbol in the uppercase format with suffix

asset must be your token's symbol
asserMap must be your token's symbol without suffix
display's default value is true, which means the information will be available in the explorer

The following contacts are supported in contact:

Twitter
Facebook
Reddit
Instagram
Medium
Steemit
Coinmarketcap
Binance Info
Youtube
Telegram
Discord
Linkedin
Github

Note: you must use the right key name

Example:
{
    "asset":"NOW-E68",
    "assetMap":"NOW",
    "officialSiteUrl":"https://changenow.io/",
<EMAIL_ADDRESS>    "display":true,
    "contact":{
        "Telegram":"https://t.me/NOWtoken_Bounty",
        "Reddit":"https://www.reddit.com/user/ChangeNow_io",
        "Medium":"https://medium.com/",
        "Youtube":"https://www.youtube.com/channel/UCpnkFY4kom0q3RJnhHiuMnw",
        "Twitter":"https://twitter.com/ChangeNOW_io",
        "Facebook":"https://www.facebook.com/ChangeNOW.io/"
    }
}

thank you
On Thu, Jul 4, 2019, 11:07 PM huangsuyu<EMAIL_ADDRESS>wrote:

Merged #14 https://github.com/binance-chain/tokens-info/pull/14 into
master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/binance-chain/tokens-info/pull/14?email_source=notifications&email_token=AIANHWSDOTE3Q5MTOHWCHUTP523GNA5CNFSM4H53LOMKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSK4PD6A#event-2461594104,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIANHWXMJPS4WCIDAYYLS23P523GNANCNFSM4H53LOMA
.


README screenshots

Please make the screenshots a bit smaller in size. They're huge!

@alias-rahil
You can make them like 50-60% width and centre them. Even the logo maybe.

I don't remember getting a notification for this issue xD, on it!


CDR processing, third try

Three phase CDR processing, some IT work remains to be done.

Not quite ready!
I'm still working on decoupling the quick verifying of the file (handled during the POST from IMI) from the long verifying of the individual summary records (handled in a separate MOTECH event)

I'll re-open when ready.


feat: Tabs Component

Codecov Report
Base: 64.61% // Head: 63.41% // Decreases project coverage by -1.19% :warning:

Coverage data is based on head (a083b85) compared to base (ad9e733).
Patch coverage: 36.94% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #9      +/-   ##
==========================================
- Coverage   64.61%   63.41%   -1.20%
==========================================
  Files          43       44       +1
  Lines        4052     4209     +157
  Branches      195      195
==========================================
+ Hits         2618     2669      +51
- Misses       1433     1540     +107
+ Partials        1        0       -1

Impacted Files
Coverage Δ

packages/core/src/components/Tabs.ts
36.53% <36.53%> (ø)

packages/core/src/components/index.ts
100.00% <100.00%> (ø)

packages/core/src/renderer/render.ts
69.09% <0.00%> (-3.64%)
:arrow_down:

packages/core/src/renderer/text.ts
51.82% <0.00%> (-1.46%)
:arrow_down:

packages/core/src/utils/index.ts
82.89% <0.00%> (-1.32%)
:arrow_down:

packages/core/src/focus/FocusManager.ts
78.03% <0.00%> (-0.94%)
:arrow_down:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


winget missing URL

To Reproduce
Steps to reproduce the behavior:

clone repo
docker build . -t "necesse-server"

Console:
=> [base 1/4] FROM docker.io/library/alpine:3@sha256:b89d9c93e9ed3597455c90a0b88a8bbb5cb7188438f70953fede212a0c4394e0                                                                                0.0s
=> CACHED [base 2/4] RUN apk --update add wget unzip                                                                                0.0s
=> CACHED [base 3/4] RUN apk add openjdk8 --repository=http://dl-cdn.alpinelinux.org/alpine/edge/community                                                                                0.0s
=> CACHED [base 4/4] RUN rm -rf /var/cache/apk/*                                                                                0.0s
=> ERROR [build 1/3] RUN wget ${url}                                                                                0.8s

[build 1/3] RUN wget ${url}:
0.517 wget: missing URL
0.517 Usage: wget [OPTION]... [URL]...
0.517
0.517 Try `wget --help' for more options.

Dockerfile:42
40 |
41 |     # Install necesse server files.
42 | >>> RUN wget ${url}
43 |     RUN unzip necesse-server-linux64-${version}-${build}.zip
44 |     RUN rm -rf ${dir}/jre
ERROR: failed to solve: process "/bin/sh -c wget ${url}" did not complete successfully: exit code: 1
Raspberry Pi 4B

Seems like you are missing build args.
See the workflow file for the building of the image for an example.
      - name: Build and export to Docker hub
        uses: docker/build-push-action@v3
        with:
          push: true
          context: .
          file: ./Dockerfile
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          build-args: |
            url=${{matrix.url}}
            version=${{matrix.version}}
            build=${{matrix.build}}

Or simply use the pre-build docker image: https://hub.docker.com/r/brammys/necesse-server


reverse slice out of range index bug

if the index is out of range, it should be treated as either start or end of the string, just like regular slice, but in reverse slice, the index is modulo of slice length.
'0123'[..>=-6] should be '3210', but it's '32'

I believe regular slices are also treated modulo the index, because of how String.prototype.slice and Array.prototype.slice work.
'hello'[..-2] → 'hello'.slice(0, -1) → 'hell'
'hello'[...-1] → 'hello'.slice(0, -1) → 'hell'

Same in CoffeeScript
Personally I find this useful: if you want to strip the last 5 characters, you use s[...-5] or s[..<-5]


Add HBW-LC4-IN4-DR

Fixes #1438

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

Comparison is base (ec5d62b) 90.42% compared to head (18f935b) 90.46%.
Report is 11 commits behind head on devel.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##            devel    #1440      +/-   ##
==========================================
+ Coverage   90.42%   90.46%   +0.04%
==========================================
  Files          49       49
  Lines        6037     6074      +37
==========================================
+ Hits         5459     5495      +36
- Misses        578      579       +1

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


Trim Whitespace from Outputfields

I think it would improve config readability if whitespace was trimmed from the output fields list so elements can spaced out in config files. Currently whitespace is used as part of the tuple fieldname. That said I'm not too familiar with yaml conventions so if whitespace is typically excluded from list values then perhaps it's better left alone.
https://github.com/salesforce/storm-dynamic-spout/blob/26e0643fb24ee7eeffbee2dd6041e3f819081b44/src/main/java/com/salesforce/storm/spout/dynamic/DynamicSpout.java#L239

Resolved in #35, note the preferred strategy will be to move to a list.
I will push a snapshot to maven central, should be there in a little bit.


Reproducible builds: override or leave out build_time in EifBuildInfo

I am working on a project that builds an eif image, by way of the nitro-cli build-enclave CLI tool. I have determined that the reason our eif image build is not reproducible is that this crate sets the build_time field in EifBuildInfo to UTC::now on each execution: https://github.com/aws/aws-nitro-enclaves-image-format/blob/main/src/utils/identity.rs#L21 . We want to have a reproducible build for our eif image because that is an important step in attestation that our system is running the desired code.
Can you please provide some mechanism for overriding the value in this field, or leaving this build_time field out of the created eif binary? This could be as simple as checking for e.g. a EIF_BUILD_TIME_OVERRIDE environment variable and using that value instead, or any number of other mechanisms.

Hi Pat,
thanks for bringing this up to us. We are currently working towards getting the whole story around EIF creation into better shape, with focusing on better documentation and reproducibility of the binaries we provide as part of the nitro-cli.
The point you are making is very valid and we will have a closer look at this.
In the meantime I am wondering if this field in particular should be that concerning. The metadata section is not part of the computation of any of the measurements (PCR values) for an image file. You should be able to verify the identity of the functional components of the EIF (kernel binary, kernel cmdline, ramdisk) through PCRs 0-2 and the signing certificate through PCR8.
The metadata section is there to identify specific build environments an image was build from. On the other hand I understand that if two builds are functionally identical there is no real value in having the build time and CRC be the only difference.

Thanks, I had not understood that the measurements for the image were of just certain sections. In that case, this build reproducible issue is only a concern for our build system and not attestation. We currently work around this problem with checks that check the image contents haven't changed by other means than the eif file staying the same, but it would be great to not have to maintain that whole extra set of checks.

@pchickey We've recently open sourced a nix-based EIF builder which might be of interest to you: https://github.com/monzo/aws-nitro-util


Support PNG/JPG on mobile

The API supports three formats: PDF, PNG and JPG. The mobile should support all of them too!

Example of a PNG poster
PDF: The Value Proposition of Libraries in Research Information Management

This is fixed on iOS, and almost fixed on Android (we should only allow zoom on Android for images).


Build download problem

I am using the following command:
appcenter build download -t build -i "my-id" -a "my-app-name" --token "my-token"
and I'm getting this error message:
failed with exception "Can't find end of central directory : is this a zip file ? If it is, see https://stuk.github.io/jszip/documentation/howto/read_zip.html"
If I try this command without specifying the app-name I get error message:
failed with exception "End of data reached (data length = 71699727, asked index =<PHONE_NUMBER>). Corrupted zip ?"
I am able to download symbols and logs for the same build but I cannot download build.
appcenter version 1.0.5

Hi @emrah-dautbegovic-sn - I think we have already touched on your request in App Center support but I also wanted to give an update here: Thanks for reporting this. We have identified the issue on our end and will be rolling out a fix. I am very sorry for causing these troubles for you.

Hi @emrah-dautbegovic-sn , we have rolled out a fix for this. Let us know if you're still facing any issues with this! (cc @ranterle)

Hi @ranterle  and @amchew
Thank you for your time and this issue is really fixed.
There is one new issue that I'm faced with and I hope so you can help me to fix that because I think it can be connected to this one.
I'm trying to execute UITest tests on Appcenter through appcenter-cli.
I've downloaded the application build from appcenter and when I'm executing tests, I'm getting the following error message:
Preparing tests... done.
Validating arguments... done.
Creating new test run... done.
Validating application file... failed.
Error: End of data reached (data length = 45061548, asked index = 45080808). Corrupted zip ?
Further error details: For help, please send both the reported error above and the following environment information to us by going to https://appcenter.ms/apps and starting a new conversation (using the icon in the bottom right corner of the screen)
Can you please take a look and let me know if there is some quick fix for this?
Thank in advance

I am experiencing this issue today. I did a debug build, I downloaded the build zip file, but I can't unzip it. This issue needs to be reopened.

@RominHalltari Thanks for notifying us and sorry this is happening for you. Can you share what error you're seeing with us and ideally reach out to our customer support with your app information and the build you were trying to download?

@matthiaswenz I am also not able to download a build from app center. Worked last week on the 5th. Tried again today the 11th, not working. Tried on both Windows and Mac. Seems like the download is slow and the size of the zip is different every time. Error message is Unable to expand "build.zip" into "Downloads" (Error -1 - Undefined error: 0.)

Whoops I guess I was confused by the dates. Its 2020 now not 2019. I can start a new thread...