Highcharts IRuby notebook : load dependent JS

Dependent JS files :

Initial

for 3d plotting

data.js dependencies when load data from html table/csv

exporting download button at the right corner of the chart

area range chart, bubble chart, bubble-3d chart type dependency

for drilldown

There are many other JS files present but I think above these are enough.

In new notebook file it works fine. But when we run #show_in_iruby method again and again it stops showing the charts.

trying this :
http://nbviewer.jupyter.org/github/Shekharrajak/daru-view/blob/nyaplot_highcharts/spec/dummy_iruby/Highcharts - line graphs2.ipynb

Maybe you need to clear the browser cache?

Now I am loading just two JS files highcharts.js and highcharts-3d.js , then it works fine.

Is it not working with the other data and exporting files?

I hope this is not a issue now. I am able to load data.js in this PR https://github.com/Shekharrajak/daru-view/pull/38/files#diff-a18ff768a909830ffbda6057a73df42bR6


Create extractive_summarizer.py

This is the python code for an extractive text summariser that will use classical NLP techniques like TF-IDF to generate a summary for the given text
This is the Python file that was asked for before starting with the creation of proper tutorial
Closes issue

[ ] My project tutorial topic has already been aproved by the Codédex team
[ ] My project tutorial file renders properly in mdx
[ ] The content written is my own, and not plagiarized from other sources
[ ] All code written is commented or documented thoroughly
[ ] I have already completed a self-review of the project tutorial
[ ] I will comply with changes from the Codédex team about my project tutorial

@Bobliuuu this is the pull request providing py file as discussed for issue #24,can you please review it and suggest the required changes

@Bobliuuu thanks for the review,I will make the suggested changes and then start with the tutorial as per the template

Hey @SparshRastogi, any updates on the project tutorial?

@Bobliuuu sorry wasn't able to work upon it due to a hectic schedule past month,will try to complete it soon

Hey @SparshRastogi, how's the project going?


Graphical question type

By this is meant a question type which has a user input which cannot be edited directly by the user, but only changed using interaction with, for example, a JSXGraph diagram and moving things around in that. Since Numbas can already fill up user entry fields with values from such interactions and process them, there would seem to be two options: 1) Show the value created  to the user, but no editing allowed or 2)Do not display the value created.

There's no generic solution here.


fix: Remove relative position of both radio groups' root (fieldset)

When adding a RadioGroupMinimal to my project I noticed the text label (<legend>) was missing. Removing position: relative from the root (<fieldset) made the text label appear. I took a look at both <RadioGroup and <RadioGroupMinimal and from what I can tell I don't think position: relative is needed. Removing relative positioning didn't seem to have any visual changes in stories across Chrome, Firefox and Safari.
@ynotdraw can you confirm if we need relative positioning or not? These components are leveraging <fieldset> and <legend> so there might be something I'm missing.

RELATIVE POSITION / LABEL HIDDEN
POSITION UNSET / LABEL VISIBLE

Hey sorry for the delay here. Yeah, I think this is probably fine. I don't see any children of the root element relying on position: 'absolute', so unless consumers are doing something strange and absolutely positioning things inside of the radio group, we should be okay 👍
For a quick sanity check as well, may be able to try yarn linking to PHC and double-check all is good there. I imagine everything will be just fine. @HaleyWardo may know where exactly in the app we're using these components.

I've personally used them in the Insight module settings, Subject Viewer Program Progress module, and Subject Search

Looks like we're good. I found four examples when I yarn linked PHC (2 w/ label and 2 w/o labels). You can see position: relative has been removed from fieldset in bottom right of every screenshot.


add axis arrows to main view and side view

The conventions for interpreting geometry in the side view and main view are a bit convoluted, and buried somewhere in the README text. It is particularly tricky if "invert y axis" is selected, since the z axis must also be inverted, or the perspective must be switched, so that now we imagine the side view is looking from right to left in the main view (instead of from left to right as it normally is).
It would be easier to follow what's going on if these ideas were explicitly displayed in the side view and main view, using cartesian axis arrows, and possibly some representation somewhere of what the side view represents relative to the main view (i.e., an eye looking in one direction left or right at a depiction of a design).

Hi Professor, just wanted to confirm that you wanted us to remove the "eye" portion of this feature.

Hi Professor, just wanted to confirm that you wanted us to remove the "eye" portion of this feature.

Yes, it's not particularly clear what it means, and I can't think of a way to make it clearer.


chore(ci): cache build output

Got a bit annoyed waiting for go build.

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

Project coverage is 55.10%. Comparing base (5e1e31e) to head (e92fac9).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #96      +/-   ##
==========================================
+ Coverage   54.83%   55.10%   +0.26%
==========================================
  Files          10       10
  Lines        1147     1147
==========================================
+ Hits          629      632       +3
+ Misses        441      439       -2
+ Partials       77       76       -1

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


Repush fix to prevent Contribute dropdown cutoff

Fixes https://github.com/cockroachdb/docs/issues/7806
Previously fixed with https://github.com/cockroachdb/docs/pull/7189

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a46f24d6d2a23d1ba4cdfc3b3463930486f68d2d/


Issue 382 guidance and examples

see https://github.com/microbiomedata/nmdc-schema/issues/382
Updated 4 terms.

I'd like this PR to be merged before I make any changes.
All additional updates require some conversation


PLAT-99881: Support item DOM element wrapper

Checklist

[x] I have read and understand the contribution guide

[x] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[x] Documentation was added or is not needed

[x] This is an API breaking change

Issue Resolved / Feature Added
In this PR, we'd like to support a DOM element wrapper for each list item for the following reasons.
There has been a desire to have an easier way to set the style of list items for both vertical and horizontal VirtualList from app developer side.
We need an approach that doesn't interfere with internal VirtualList logic, such as setting transform style to each list item.
Also, we, as VirtualList developers, had a concern that each app has a duty to pass props which are mandatory to make VirtualList work, such as key.
Resolution
Among several feasible approaches mentioned in PLAT-86356, we've decided to add a DOM element wrapper to fulfill the above consideration.
We can explicitly hide internal prop and logic from app developers and also they can define styles more intuitively.
Additional Considerations
While implementing, I've also considered un-nest the classes. So I moved listItem class out of virtualList. I couldn't un-nest others because others are used in the child of the DOM which has virtualList.
Also, I've considered rename childProps to itemProps for clarity.
Links
PLAT-99881
Comments

LGTM


Add Japanese translation for v3.0.2

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
I added Japanese translation for Node-RED v3.0.2.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 68.197% when pulling d0d22c333c3d9479d19544b3726bff73fa5738fc on kazuhitoyokoi:master-addjpn into<PHONE_NUMBER>e21df74b339a399e854ed89af6394f on node-red:master.


successPercentage not working correctly, tests not showing up in report

I had an issue when trying not to have group-dependent tests skipped, when using retries and parallel execution. It's a rather complicated example, so explaining with words doesn't really make sense, but I could boil it down to a test not showing up in the report when I tag it with successPercentage. I would love to include my small self contained Gradle sample project.

No sample found in this issue and could not also locate the email on the mailing list which contains the project. Closing this issue for want of a sample. If this is still a problem using the latest released version of TestNG (7.1.0 as of today), comment with a reproducible sample and we can have this issue re-opened.


Added Toastify Message

Hello Project Admin
I Added Toastify Message - Solved #607
Kindly Please go through this PR @himanshu-03
https://github.com/Anushkabh/krishiconnect/assets/161804629/c8afce69-617a-41f6-b567-e76b30475e78

@himanshu-03 Thank you :)


Add Michael Johnston and Marc Wagner to mailing lists for the MOC events…

From: Krieger, Orran<EMAIL_ADDRESS>Date: Tuesday, October 25, 2022 at 12:57 PM
To: Wagner, Marc K<EMAIL_ADDRESS>Cc: Johnston, Michael K<EMAIL_ADDRESS>Monkman, Sophia<EMAIL_ADDRESS>Subject: Re: Connecting Orran-Michael

https://massopen.cloud/contact-us/


Updated Developer Documentation

This patch updates the project's developer documentation.

Codecov Report

Merging #430 into release/0.5.0 will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release/0.5.0     #430   +/-   ##
==============================================
  Coverage          31.06%   31.06%
==============================================
  Files                 29       29
  Lines               1751     1751
==============================================
  Hits                 544      544
  Misses              1149     1149
  Partials              58       58

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0fc9f95...4c1c3b6. Read the comment docs.


Setting initial error state for a form field

Modular Forms provides the ability to specify initial form field values via the FormOptions object: initialValues.
I need the ability to set the initial state of a specific field as an error.
Imagine a scenario where I redirect to a form that verifies uniqueness on the server, and I need to render the form with one field marked as not unique.
What is the right way to achieve this:

Should Modular Forms support FormOptions.initialErrors?
Should users use setError and setResponse? Would be nice to see an example code snippet in the docs (do I need to use batch() etc)
Is there another recommended approach?

I think the only option we have at the moment is to use setError or setResponse.


Added link to container-lang programming language

Added my own esoteric programming language. I hope you like it!

Hi @odddollar
Great work at your language!.
I've carefully read your docs (they are quite good and detailed, btw) and I'm not sure this language fits in this list. I may have missed something (please, let me know if that is the case), but your language feels more like an actual usable language (although, admittedly a bit extreme with the BASIC-like line numbering) rather than an esoteric one (i.e. "weird ideas, to be hard to program in, or as a joke").
And please, let me know if you make another esolang (or make this one weirder), I love the effort and docs you have put into this language (and Leafscript)

All good, thanks


Remove: SmartProjects.IsoBuster version 4.9.1

## Vanity URL - Newer version in repo
Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: https://www.isobuster.com/downloads/isobuster/isobuster_install.exe
OK
(Automated message - build 888)


SqlServerEndpointPermission: Fix long path issue for examples

Pull Request (PR) description

Changes to SqlServerEndpointPermission

Now the examples files have a shorter name so that resources will not fail
to compile in Azure Automation (issue #934).

This Pull Request (PR) fixes the following issues:
Fixes #934
Task list:

[x] Change details added to Unreleased section of CHANGELOG.md?
[x] Added/updated documentation, comment-based help and descriptions in .schema.mof files where appropriate?
[x] Examples appropriately updated?
[ ] New/changed code adheres to Style Guidelines?
[ ] Unit and (optional) Integration tests created/updated where possible?

This change is

Codecov Report

Merging #935 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            dev   #935   +/-   ##
===================================
  Coverage    96%    96%
===================================
  Files        32     32
  Lines      3515   3515
===================================
  Hits       3395   3395
  Misses      120    120

Closing and reopening to kick off the tests again.

Again. Closing and reopening to kick off the tests again.

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


[AutoComplete] Use dataSourceConfig.text instead of value when rendering MenuItems from objects

[ ] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

We were using itemValue instead of itemText which made the AutoComplete menu render the wrong property as primaryText when using arrays of objects as a data source.
Using this dataSource config...
dataSourceConfig = {
	text: 'name',
	value: 'id',
}

... and an array with simple id + name objects rendered this

With this PR we now render

@matiaslarsson Good catch, the docs example is broken too.

@matiaslarsson Thanks 👍 . It would have been even better with a unit test.


Auto-fill recipes with plankWood is not working

Issue description:
Auto-fill recipes with plankWood is not working either for crafting grid, and crafters are 🤔 there is no wood in system if attempt to craft a recipe with is oredict enabled and there is plankWood in recipe
What happens:
https://i.dbot.serealia.ca/2017/11/7bdcb36ec8_%25pn_-2017-11-20_07-19-08.webm
What you expected to happen:
Auti-refill works in crafting grid and crafters craft stuff
Steps to reproduce:
watch video
Version:

Minecraft: 1.12.2
Forge: almost latest build (2538)
Refined Storage: 1.5.22

Does this issue occur on a server? yes

There is a limit on how much "oredicted" wood RS can send over the network for oredicted recipes (to avoid overflowing the network packet). Unfortunately, on larger packs this limit is easier to reach.


updating error handler to be more HTML friendly

I've removed the 404.html page and renamed the 500.html page to error.html.
The error handler now redirects to /error which, renders the error.html page and uses JavaScript to parse the error code and message from the query string. The default code and message is the 404 page so there is also a vanity route /404.
So it will now show all errors and not just a 500. Much more user friendly.

Why did this need to be changed? I'm not sure if error redirects are the best solution. The server and the browser loose all context and there is no way to know where that error came from to e.g. print a stack trace or send an error report.

Without adding a template engine to the mix, this is the only way to get the actual error messages and codes onto the error page. Having just a 500 and 404 wasn't good enough because a bunch of different errors could occur and if it wasn't a 404 it would just show a 500. Which is confusing.
The stack traces still get logged, and if it is a JSON response, get sent in development mode. You can also send error reports by just adding a middleware before the error handler.
We can revert if need be and I'm open to other ideas but I think this is a better solution than what was previously there.

What I am wondering is if this should be pre-generated or something everybody should take care of themselves. Basically my assumption with the old setup was that if you do not use a view engine it is very unlikely that anybody will ever hit an error other than a 404 in the browser.
Without a view engine you're probably running an API only server (maybe with a public folder for your frontend). Personally I wouldn't give more information other than a general error page to a user that tries to hit your API endpoints directly in the browser.

@daffl fair points. My only concern really, and this is where the confusion came from, is authentication errors. Currently if you hit an endpoint that requires validation you get a 500.html, which is very confusing.
For the most part you have convinced me to revert, but maybe we should also have a 401.html?

I was thinking we could create an errors/ folder where you can add pages by status code and it'll serve that. But maybe just adding a 401.html is best. If you want better browser error handling than plain HTML pages you'll probably change the error middleware to use a view engine anyway.


[kmac] Add EDN synchronizer

This PR adds newly introduced prim_edn_req primitive into KMAC Entropy interface.
This requires to define EDN clock (it is synchronous to KMAC clock) in KMAC, which results in re-generating TOP.

Good point Mark. I thought KMAC doesn't have to use FIPS compliant entropy source. But worth to check with @cdgori or other crypto expert team members.

On Jan 8, 2021, at 8:38 AM, mwbranstad<EMAIL_ADDRESS>wrote:
@mwbranstad commented on this pull request.
In hw/ip/kmac/rtl/kmac.sv https://github.com/lowRISC/opentitan/pull/4771#discussion_r554054848:

@@ -765,13 +768,37 @@ module kmac

// Entropy Generator
if (EnMasking == 1) begin : gen_entropy

logic entropy_req, entropy_ack, entropy_fips;
logic [MsgWidth-1:0] entropy_data;
logic unused_entropy_fips;
assign unused_entropy_fips = entropy_fips;
Is this a temporary setting, or will the entropy_fips indication never be referenced?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/lowRISC/opentitan/pull/4771#pullrequestreview-564405321, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJDG3XF5ZC3EORM6SA4UATSY4YINANCNFSM4VZPSF2Q.

Good point Mark. I thought KMAC doesn't have to use FIPS compliant entropy source. But worth to check with @cdgori or other crypto expert team members.

On Jan 8, 2021, at 8:38 AM, mwbranstad<EMAIL_ADDRESS>wrote:
@mwbranstad commented on this pull request.
In hw/ip/kmac/rtl/kmac.sv https://github.com/lowRISC/opentitan/pull/4771#discussion_r554054848:

@@ -765,13 +768,37 @@ module kmac

// Entropy Generator
if (EnMasking == 1) begin : gen_entropy

logic entropy_req, entropy_ack, entropy_fips;
logic [MsgWidth-1:0] entropy_data;
logic unused_entropy_fips;
assign unused_entropy_fips = entropy_fips;
Is this a temporary setting, or will the entropy_fips indication never be referenced?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/lowRISC/opentitan/pull/4771#pullrequestreview-564405321, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJDG3XF5ZC3EORM6SA4UATSY4YINANCNFSM4VZPSF2Q.

Sorry I just am getting back to this.  I am not sure if KMAC needs potentially FIPS-compliant entropy as I am not aware of all of the (potential) use cases - I can imagine some but am not sure if they are valid.  Probably @moidx needs to comment.

Sorry I just am getting back to this.  I am not sure if KMAC needs potentially FIPS-compliant entropy as I am not aware of all of the (potential) use cases - I can imagine some but am not sure if they are valid.  Probably @moidx needs to comment.

No need to use FIPS entropy for countermeasures. If the entropy is used as part of a cryptographic service (e.g. key generation as a service), then we have to evaluate in more detail. Please let me know if you have further questions.

No need to use FIPS entropy for countermeasures. If the entropy is used as part of a cryptographic service (e.g. key generation as a service), then we have to evaluate in more detail. Please let me know if you have further questions.

Sorry I didn't get to this, but hopefully that comment from @moidx is clear.  I would expect that the FIPS-compliant entropy will largely be consumed by Ibex (e.g. as source material for key generation), and possibly OTBN and KeyMgr.

Sorry I didn't get to this, but hopefully that comment from @moidx is clear.  I would expect that the FIPS-compliant entropy will largely be consumed by Ibex (e.g. as source material for key generation), and possibly OTBN and KeyMgr.


New Project - I'm the creator & owner - Cannot add myself to project or create release

Hello!  I created a new Imhotep Project, I am the owner.  I'm getting errors when trying to add release & project member.

Hi @njacobs125!  Yes, a couple of customers have reported this in some other channels, I forgot to log this as a Github issue.  This occurs occasionally when creating a brand new project.  I'm working on a fix in the next release - for now, the easiest thing to do is delete the project and create a new one.  It doesn't seem to happen back-to-back.  Sorry for the trouble!
For reference, the issue appears to be caused by an order of execution issue in the flow - the initial backlog release and project member records aren't created because the project record isn't finished being created.  It doesn't appear to happen often, but I'll post back when an updated package with the long-term fix is ready.

Mitch

Thanks for the fast response, Mitch!  I deleted the project and created a new one.  Same experience.  Is there any possible chance of getting on a quick call?  I'm happy to try whatever.  I've been at this for an hour :-/

@njacobs125 gotcha - well I suppose "occasionally" is no longer accurate, I'm sorry about that.  A system administrator can still create a project member record manually - from App Launcher, go to the Project Members tab.  Use the New button to create a project member (selecting your project and choosing Owner/Lead for the role).  The sharing rules will be automatically applied.
If that doesn't work, I can jump on a quick call.

Trying now... thank you!
On Fri, Oct 11, 2024 at 8:37 AM Mitch Lynch @.***>
wrote:

@njacobs125 https://github.com/njacobs125 gotcha - well I suppose
"occasionally" is no longer accurate, I'm sorry about that. A system
administrator can still create a project member record manually - from App
Launcher, go to the Project Members tab. Use the New button to create a
project member (selecting your project and choosing Owner/Lead for the
role). The sharing rules will be automatically applied.
If that doesn't work, I can jump on a quick call.
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/Imhotep-App-Builder/issues/7#issuecomment-2407326025,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BL7EUMZUSXUMFICN65Y52TTZ27A7TAVCNFSM6AAAAABPYZFN2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBXGMZDMMBSGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*Nancy Jacobs *| Senior Delivery Manager & Sales Support Specialist
Schedule a Call https://calendar.app.google/rYqHNKbhwre8FJae6
Confidentiality Notice: The contents of this email and any attachments may
contain confidential and/or proprietary information, and are intended only
for the person/entity to whom it was originally addressed. Any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this email in error please notify the
sender immediately by return e-mail and delete this message and any
attachments from your system.

That worked!  Thank you!!!!
On Fri, Oct 11, 2024 at 8:37 AM Nancy Jacobs @.***>
wrote:

Trying now... thank you!
On Fri, Oct 11, 2024 at 8:37 AM Mitch Lynch @.***>
wrote:

@njacobs125 https://github.com/njacobs125 gotcha - well I suppose
"occasionally" is no longer accurate, I'm sorry about that. A system
administrator can still create a project member record manually - from App
Launcher, go to the Project Members tab. Use the New button to create a
project member (selecting your project and choosing Owner/Lead for the
role). The sharing rules will be automatically applied.
If that doesn't work, I can jump on a quick call.
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/Imhotep-App-Builder/issues/7#issuecomment-2407326025,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BL7EUMZUSXUMFICN65Y52TTZ27A7TAVCNFSM6AAAAABPYZFN2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBXGMZDMMBSGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
*Nancy Jacobs *| Senior Delivery Manager & Sales Support Specialist
Schedule a Call https://calendar.app.google/rYqHNKbhwre8FJae6
Confidentiality Notice: The contents of this email and any attachments may
contain confidential and/or proprietary information, and are intended only
for the person/entity to whom it was originally addressed. Any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this email in error please notify the
sender immediately by return e-mail and delete this message and any
attachments from your system.

--
*Nancy Jacobs *| Senior Delivery Manager & Sales Support Specialist
Schedule a Call https://calendar.app.google/rYqHNKbhwre8FJae6
Confidentiality Notice: The contents of this email and any attachments may
contain confidential and/or proprietary information, and are intended only
for the person/entity to whom it was originally addressed. Any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this email in error please notify the
sender immediately by return e-mail and delete this message and any
attachments from your system.

@njacobs125 whew!  Sorry again!  I'm trying to use as much configuration as possible in the app so that the flows can easily be rewired by a non-developer who wants to tailor them for their own processes... so I need to rework the New Project flow to make sure this doesn't occur and fight the desire to write any Apex :).  Thanks for bearing with me - this issue came up well after beta testing, which makes me feel like something became much more performant in Flow in the Summer '24 release (which is a good problem to have, I suppose!).


Indices on Fields in Composite Types: Client & Query Engine

A unique or fulltext index in a model can point to a field that is in a singular composite type:
type FooFoo {
  bar Int
}

model Foo {
  id  Int    @id
  foo FooFoo

  @@unique([foo.bar])
}

Or it can point to a field in an array of composite types:
type FooFoo {
  bar Int
}

model Foo {
  id  Int      @id
  foo FooFoo[]

  @@unique([foo.bar])
}

The composite type field can be just a part of the index which includes fields directly from the model too.
We should enable findUnique operations, and fulltext operations to these fields if corresponding indices are defined correctly.
If the unique index points to an array of composite types, with the following data:
{
  "name": "Musti",
  "addresses": [{ "city": "Berlin" }, { "city": "Helsinki" }]
}

And our PSL says:
type Address {
  city String
}

model User {
  name      String
  addresses Address[]

  @@unique([addresses.city])
}

All of these writes will lead to unique constraint violation:
{ "name": "Musti", "addresses": [{ "city": "Helsinki" }] }
{ "name": "Musti", "addresses": [{ "city": "Berlin" }] }
{ "name": "Musti", "addresses": [{ "city": "Helsinki" }, { "city": "Berlin" }] }

And the client can find the record from the collection with two different queries:
findUniqueRecord({
  where: {
    "name": "Musti",
    "addresses": { "city": "Berlin" }
  }
});

findUniqueRecord({
  where: {
    "name": "Musti",
    "addresses": { "city": "Helsinki" }
  }
});

Dependencies
The PSL issue must be merged before starting to work with this one.
Full proposal
Private document in Notion

This will be released in 4.3.0

Fixed by https://github.com/prisma/prisma-engines/pull/3107.


Handle EVENT_INTERVAL in HttpSM::state_raw_http_server_open and HttpSM::state_http_server_open

In the #9366 we stopped handling EVENT_INTERVAL in HttpSM::state_raw_http_server_open and HttpSM::state_http_server_open, but we've been seeing some unexpected aborts recently. This adds back the handling for that event.

Cherry-picked to v10.0.x


Change repository to package repository instead of template

A PyPI package should have its own dedicated repository. A template would be a separate thing since you would install the package instead of forking its source code.

[x] Change repository to non-template
[x] Move source code from src to src/phyal folder
[x] Create pyproject.toml

@SalladShooter how exactly can I do this, what contents would I need in the pyproject.toml. Should I remake the Repo to fix it?

You do not need to remake the repo.
First, pick a build backend to manage things easier.
Here's some info on python build backends:
https://sinoroc.gitlab.io/kb/python/packaging_tools_comparisons.html#build-back-ends
https://www.reddit.com/r/Python/comments/166a9br/pyprojecttoml_buildbackend_statistics/
You should probably use poetry because that is what replit uses. Now, on your local machine use poetry init to create a pyproject.toml for an existing project, PHYAL.
Poetry also helps publish your package.
Take a look at my own github pypi package, pyriak, for reference.
(I recently moved from replit to github + local machine. I am an inactive TL3 in ask replit right now.)
There are still many improvements you can make after this, I will post some issues later.

@aatle thank you so much for the resources, looking forward to future ideas.

The last two tasks do not seem to be fixed yet. This issue should be reopened.


ppo2.py not updating act model policy from old policy

why there is no update policy from old policy for new round of data in update for loop of learn function

act_model and train_model share parameters because reuse=True in the second declaration:
https://github.com/openai/baselines/blob/f2729693253c0ef4d4086231d36e0a4307ec1cb3/baselines/ppo2/ppo2.py#L17-L18
So only train_model needs to be updated and act_model is automatically updated too. The update is conducted by calling this function in the for loop here.

@brett-daley correct. Closing this.


WIP: Pytides submodule

This PR might replace #3, and also https://github.com/clawpack/geoclaw/pull/532,  following some offline discussion about how best to organize things.
This includes pytides as a submodule, with some modifications to make the import statements work in Python3.  Similar changes have been suggested in an open PR on the original site, but  original pytides does not seem to be actively developed.
These changes are also implemented in other forks, e.g.

https://github.com/titoconte/pytides
https://github.com/drf5n/pytides

but these seem to have some other potential problems, and also do not seem to be actively developed, so I suggest we just maintain our own fork within this module.
There are also some other changes that have been implemented in the forks above and/or suggested in open PRs on pytides that we might want to consider, in particular at least one typo in a value for K2.
This PR includes a local tidetools.py with the utilities from tide.py in https://github.com/clawpack/geoclaw/pull/532, and some additional utilities we have developed for other projects.  There is also a pytides_tools.py that maybe should be combined with tidetools.py.
Currently this PR also contains a couple notebooks illustrating usage:

pytides_examples/demo_noaa_constituents.ipynb: Adapted from an example on the pytides wiki, with some additional plots an illustration of using tidetools to download the constituents,
pytides_examples/Tide_Module_Examples_pytides.ipynb: Adapted from the notebook in #3, now using the local tidetools and pytides.

More examples to come.

@socoyjonathan what are your thoughts regarding these changes?

@mandli I like these changes to make pytides as a submodule and work around that package! may we schedule a meeting to discuss how I can best contribute to this project further!
@rjleveque I am reviewing your comments on Tide_Module_Examples_pytides.ipynb! thank you for your excellent feedback!

Just a quick update on this.  @socoyjonathan is looking into incorporating this module and his into the tide-examples (this repository).  Waiting to make sure this seems to work well.

@rjleveque I have refactored tidetools.py to adequately incorporate our work and improved comments on Tide_Module_Examples_pytides.ipynb (now named Tidetools_Module_Examples).
I would like to contribute these changes to your PR so that your PR can be approved, however I don't know if that is the best option. Or should I open my own PR on clawpack/tidal-examples repository and submit my changes there to be reviewed separately?

@socoyjonathan: Thanks for doing this!  I think it's simplest if I go ahead and merge this PR, and then you can do a new PR with the improvements.  Will that work for you?

@rjleveque: Yes that would be perfect! Thank you!


Make config file location configurable under windows

This request is related to #2755. In https://github.com/dbeaver/dbeaver/issues/2755#issuecomment-513260791 the default config file location for linux was placed under ${XDG_DATA_HOME}/DBeaverData but for windows, it is still a (somewhat) fixed directory %AppData%/DBeaverData.
Here is the use case:

I have multiple Windows computers, and I work on all of them.
I have a common config directory that is synchronized between all of them
I use many programs that are able to use custom config directories, and their configurations are always synchronized between all computers that I use
DBeaver cannot do this, because its config dir is not configurable.

Of course, I could setup a separate directory synchronization just for this single config directory, but that is very clumsy.
I know that this is a very narrow use case, but I think it would be a small change to use something like $DBEAVER_CONFIG_DIR env instead of %AppData%/DBeaverData (when set).

Hi @nagylzs. I synchronize DBeaver workspaces between my Windows machines using Dropbox. To do that, I created a different workspace under the directory I share between my devices. You can do that by clicking File -> Switch Workspace -> Other. Does this solution work for you?

I just moved my workspace folder inside a synchronized folder, and I could switch to it. Everything seems to be working. I'm not sure what will happen if I leave open DBeaver on one computer and open it on another one at the same time. But So far so good.


Rerun submission when a task used is deleted

@ mention of reviewers
@Didayolo
A brief description of the purpose of the changes contained in this PR.
Previously, when a task was disconnected from a competition but it was used in a submission: Rerunning such submission would result in a submission stuck in submitted status.
Now, when task/tasks are deleted, a warning message is shown to the user:

If a user tries to rerun submission with its task deleted, the following error message is shown:

Issues this PR resolves

#1179
#1182 -> Re-run submission on deleted task

A checklist for hand testing
For single-task phase

[x] Create a competition with one task A per phase,
[x] upload a submission and wait for its success,
[x] add a new task B in resource interface
[x] remove task A from phase
[x] connect task B to this phase
[x] delete task A from resource interface
[x] rerun the submission and check if you get an error

For multi-task phase

[x] repeat the above but make sure to create multi-task phase

Checklist

[x] Code review by me
[x] Hand tested by me
[x] I'm proud of my work
[x] Code review by reviewer
[x] Hand tested by reviewer
[x] CircleCi tests are passing
[x] Ready to merge

Nice job!


Allow for manual opt-out of CAS features

I've been working on a bare metal platform lately that does not have CAS (specifically ARMv4 bare metal), and this is not caught by the CPU detection logic in the build.rs. This PR adds a flag that allows for manual specification to avoid CAS features.

Thanks for the PR and sorry it took me so long to get to it.
Ideally, I would like to use the output of rustc --print cfg (see the rustc-cfg crate) here:
$ rustc --print cfg thumbv6m-none-eabi
debug_assertions
target_arch="arm"
target_endian="little"
target_env=""
target_feature="mclass"
target_feature="v5te"
target_feature="v6"
target_has_atomic_load_store="16"
target_has_atomic_load_store="32"
target_has_atomic_load_store="8"
target_has_atomic_load_store="ptr"
target_os="none"
target_pointer_width="32"
target_vendor=""

$ rustc --print cfg --target thumbv7m-none-eabi
debug_assertions
target_arch="arm"
target_endian="little"
target_env=""
target_feature="mclass"
target_feature="v5te"
target_feature="v6"
target_feature="v6k"
target_feature="v6t2"
target_feature="v7"
target_has_atomic="16"
target_has_atomic="32"
target_has_atomic="8"
target_has_atomic="ptr"
target_has_atomic_load_store="16"
target_has_atomic_load_store="32"
target_has_atomic_load_store="8"
target_has_atomic_load_store="ptr"
target_os="none"
target_pointer_width="32"
target_vendor=""

target_has_atomic indicates the CAS support; target_has_atomic_load_store indicates support only for atomic loads and stores. However, that output seems to be nightly-only for now (I believe there are no immediate plans to stabilize that part of the output):
$ cargo +beta --print cfg --target thumbv7m-none-eabi
debug_assertions
target_arch="arm"
target_endian="little"
target_env=""
target_os="none"
target_pointer_width="32"
target_vendor=""

As that can't be used, using Cargo features is the next best option. However, Cargo features must be additive (*); meaning that instead of an opt-in no_cas feature we should have an opt-out cas feature that makes the SPSC API available. The cas feature needs to be enabled by default to release it under a new patch version and not break existing users.
(*) To see what can go wrong with no_cas imagine a crate A uses heapless::spsc::Queue then in your crate you enable the no_cas feature of heapless and add A as a dependency; cargo build-ining your crate will fail to build the A dependency.

I've inverted the logic here, and tried to add some helpful diagnostics:
cd heapless
cargo build --target thumbv7em-none-eabihf # works
cargo build --no-default-features --target thumbv6m-none-eabi # works
cargo build --target thumbv6m-none-eabi # doesn't work
cargo build --no-default-features --target thumbv6m-none-eabi --features cas # doesn't work

In this PR, by inverting the features here, I believe this is now a breaking change, as any users who were intentionally or unintentionally setting no-default-features would lose access to mpmc and pool.
With the no_cas feature, this would not be a breaking change in my opinion.

I believe this is now a breaking change, as any users who were intentionally or unintentionally setting no-default-features would lose access to mpmc and pool.

You are correct. This is in principle a breaking change. However, the crate currently has zero default features so the number of people using no-default-features should also be zero as that configuration is a no-op.
Thanks!
bors r+

@japaric back to you.

Thanks!
bors r+

@japaric I missed you added a feature at the end of the file in my merge. This should work now.

bors r+


Bug Report:  FAQ On Capturing all GA Outdated

Expected Behavior
When going to https://www.amundsen.io/amundsen/faq/#how-to-capture-all-google-analytics it shouldn't point to a dead link, and it shouldn't embed <script async src="https://my-proxy-domain/MASKEDGOOGLETAGAMANAGERURL"></script> in the HTML
Current Behavior
NA
Possible Solution
Update FAQ with current instructions on how to capture all GA data
Steps to Reproduce
NA
Screenshots (if appropriate)
NA
Context
It hasn't, just noticed it while reading the docs.
Your Environment
NA

do you want to upstream the fix?


Updated: postman-canary 7.1.1-canary04

Newer version of postman-canary (7.11.0-canary01) is now available in master.


Slow recipe generation prevents scaling

Now that I am more seriously thinking about scaling this recipe up, I wanted to start a conversation about the performance issues I foresee.
Currently we generate a dictionary of recipes in serial via a for loop. Each recipe makes an API query and then generates some keyword arguments that need to be passed to the recipe generation.
If we want to scale this up to thousands or more of recipes we should spend some time understanding which parts of this machinery take the most time and how we could maybe avoid this.
Some preliminary thoughts:

Can we create the recipes in parallel or asyncronous?
Is there a way to 'batch' requests to the ESGF API.
Or could we work out some sort of 'cache' for recipes, so that only the ones that have changed get rebuilt/need to send an API request (I believe this is not trivially possible, since we need to build the recipe first to compare hashes @cisaacstern ?)

I intend this to be a loose conversation for now, so if anyone has ideas, please feel free to discuss.

I think I made some significant progress in #13, which is now able to scale up to ~100 recipes in a reasonable time.


releasing training script and config file

Hi, thank you for your awesome work. Could you please release training script and config file as well so we test on our data? Its a bit challenging to register this model in detectron2 and then train it.

Any directions/docs on training with this is appreciated!
Even if it is related to Detectron2, it will be a great.


fix: 4123 - question image full page improvements

What

The questions image full page used a floating action button for the "close" action, which was not appropriate.
Now we use a standard AppBar with its standard "close" button.
Now that we have an AppBar, we also have the text of the question.

Screenshot

question card
question page
question page (zoomed)

Part of

#4123

Impacted files

question_card.dart: minor refactoring
question_image_full_page.dart: now we use the standard close button and display the question text
question_image_thumbnail.dart: minor refactoring

Codecov Report

Merging #4137 (2a032cc) into develop (55b4894) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##           develop    #4137   +/-   ##
========================================
  Coverage    10.91%   10.91%
========================================
  Files          277      277
  Lines        13536    13536
========================================
  Hits          1477     1477
  Misses       12059    12059

Impacted Files
Coverage Δ

...ooth_app/lib/pages/hunger_games/question_card.dart
0.00% <0.00%> (ø)

...b/pages/hunger_games/question_image_full_page.dart
0.00% <0.00%> (ø)

...b/pages/hunger_games/question_image_thumbnail.dart
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

In terms of UI, the black one from the photo editor could be better here, with a translucent AppBar.
Any suggestions on this @teolemon?

@g123k I have no special interest in UI, and I won't be offended if we close this PR and you create another one.
I coded this PR quickly to address the anti-pattern you detected yesterday.
The added value of a standard app bar is that we can display the question texts. As a hunger games user, I can say that it's useful.

You're both right. We can merge that and it's an improvement over the current situation, and we can refine for more consistency in a subsequent PR as well.

Thank you @teolemon for your review!
I would even enjoy a completely different UI for hunger games card: directly a full page with the image as big as possible on top (zoomable), and then the product name+brands+quantity and the possible answers. That would spare the user the need to click on a thumbnail.
That may mean the image, then some alpha background, and the product name on top.
But that's another story.


Remove ununsed local variables

Some variables where unused. Removing them allows for less clutter and
also prevents rubyist that have warnings enabled to have those warnings
printed out.

This is superseded by #822, but thanks!


"ace_jump_word" doesn't work with cyrillic

ace_jump_word command doesn't work with cyrillic letters, instead the plugin reopens the panel without showing results. Strangely ace_jump_char does work. The file encoding I tried this with is UTF-8, and it is the latest version of ST3.
It would be a nice touch if the labels were in cyrillic too if a cyrillic char is used (ordered according to the russian alphabet as the most used cyrillic alphabet, or this could be made user modifiable for serbian, ukranian alphabets etc.) so a user wouldn't need to change the keyboard layout every time if working with an all-cyrillic text.

The regex currently used by word mode (\b{}) , allows only for alphanumeric characters, that's why you're having the issue. I tried experimenting with it but I wasn't happy with the results so far. As soon as a satisfactory, alternative solution is found, I'll change it.
As for changing the labels, I see this could help and I think I might have a not so complicated soliution, however I lack the time to write it at the moment, so just create another ticket for 'multiple labels sets'.


Looks like degree/minute/second coordinates aren't working anymore?

Go to the demo page and click on one.

Fixed


Fix simphony-lammps version (0.1.3)

uses simphony-lammps 0.1.3 (it was missing from PR #37)
fixes simphony-jyulb version in README

@itziakos ,  i noted some things that had to be done before 0.1.3 release.
I will do the PR for the 0.1.3 release after this is reviewed/merged

:+1:


Update es-ES.coffee

Hey, can you sign the CLA here: https://codecombat.com/cla
I can review the code after that, sorry for the delay.

closing this for now, please open once cla is signed


Cloud not load xgboost model into spring boot service

hi,
I have serialized a xgboost-spark pipeline model in bundle format, but I could not load it into spring boot service because of "xgboost.classifier" op is not supported. I found that mleap-xgboost-runtime is released now. It seems loading xgboost-spark pipeline should be accessible. Would you help me about how to add dependency of mleap-xgboost-runtime into mleap-spring-boot ? Or update the docker with xgboost model support?

hi, I have add it as a dependency in our build.sbt, but it does not work,
project mleap-runtime build.sbt:
import ml.combust.mleap.{Dependencies, Common}
Common.defaultMleapSettings
Common.defaultMleapXgboostSparkSettings
Dependencies.runtime(scalaVersion)
The error is “Exception in thread "main" java.util.NoSuchElementException: key not found: xgboost.classifier
at scala.collection.MapLike.default(MapLike.scala:235)”

hi, I have add it as a dependency in our build.sbt, but it does not work,
project mleap-runtime build.sbt:
import ml.combust.mleap.{Dependencies, Common}
Common.defaultMleapSettings
Common.defaultMleapXgboostSparkSettings
Dependencies.runtime(scalaVersion)
The error is “Exception in thread "main" java.util.NoSuchElementException: key not found: xgboost.classifier
at scala.collection.MapLike.default(MapLike.scala:235)”

Can you provide a more complete stacktrace?
My only thought right now is that the mleap runtime can't find the correct op used to load the bundle.  This could occur if you have a resources.conf file in your project and aren't having mleap's reference.conf appended to your project's reference.conf.  E.g., if you are using sbt-assembly plugin, then you might need
assemblyMergeStrategy in assembly := {
  case "reference.conf" => MergeStrategy.concat
  case _ => MergeStrategy.first
}

But a complete stacktrace will help to confirm/deny this.


what's the est timeline for releasing Context Parallel and 3D Pipeline

Many interesting topics are mentioned in coming soon section, I'm wondering do we have a estimated/targeted releasing date? Thanks again for the great work.

Most topics in the "coming soon" are already included in main. We will update the README.
Basic PP is ready and we are still adding more advanced features/variants (e.g. zero-bubble PP).
CP is available in #433. @fegin to share more on progress.

Awesome! thx


configure mkdocs

[x] Basic configuration
[x] automatic reference generation from docustring
[ ] integrate to makefile

It depends on #111


proxy.golang.org: @v/list can become stale

Here's an example of everything working as planned:
$ curl -s https://proxy.golang.org/golang.org/x/text/@latest | jq -r .Version
v0.3.5
$ curl -s https://proxy.golang.org/golang.org/x/text/@v/list | sort -Vr | head -n 1
v0.3.5

Here's an example of things not going as planned:
$ curl -s https://proxy.golang.org/golang.zx2c4.com/wireguard/@latest | jq -r .Version
v0.0.0-20210216200525-4e439ea10e32
$ curl -s https://proxy.golang.org/golang.zx2c4.com/wireguard/@v/list | sort -Vr | head -n 1
v0.0.20201118

In the first example @latest==max(@v/list) but in the second example @latest!=max(@v/list). How could this be? Because I've removed all tags from my repository. I did this because tagging versions didn't make sense for it (just as it doesn't make sense for x/sys, while it does make sense for x/text). The intended effect was that go get ... would then give people the latest commit, rather than the latest tag. Unfortunately, due to the above weirdness, it gives people an old no longer existing tag.
The solution here is for @v/list to stop displaying removed tags. Note that that is different from removing old zips -- by all means, keep old zips so that people's dependencies don't break -- but @v/list should not display phantom tags.
CC @FiloSottile

Please use the new retract feature to remove undesirable versions.
The list endpoint is supposed to return a list of all known versions. Since the proxy knew about v0.0.20201118, it's returning that. This is necessary to implement the -retracted flag.

The proxy should stop listing non-existent versions. Retract is further consequences than what this issue is about and not desirable here. This only concerns @v/list, not anything elsewhere.

The version v0.0.20201118 still exists in the abstract regardless of any change to the upstream tags: for example, its checksum won't disappear from the https://sum.golang.org database.
Extraneous versions in the /@v/latest endpoints should be mostly irrelevant to the go command. If you retract all of the versions in that list, then versions of the go command that support retraction (Go 1.16+) should fall back to the pseudo-version for the latest commit as you expect.

The version v0.0.20201118 still exists in the abstract regardless of any change to the upstream tags: for example, its checksum won't disappear from the https://sum.golang.org database.

I'm not requesting that you stop serving v0.0.20201118.zip. What I'm asking is that @v/list stop serving stale information.

Extraneous versions in the /@v/latest endpoints should be mostly irrelevant to the go command. If you retract all of the versions in that list, then versions of the go command that support retraction (Go 1.16+) should fall back to the pseudo-version for the latest commit as you expect.

This doesn't appear to be the case. So far as I can tell, it downloads the latest tag from @v/list, and since that old non-existent version doesn't have a retract statements, it doesn't see anything to retract.

The retract directive does need to be in the semantically-highest listed version of the module, yes.
One way to make that work is to temporarily tag a higher version containing a retract directive that retracts both itself and the unwanted previous versions. Then go mod download that higher version via the proxy, so that it also becomes the highest tag in the proxy's list. Once that's done (and successfully ingested into the proxy), you can purge the erroneous tags so that users running with GOPROXY=direct won't bother checking the self-retracted version.

Thanks! That seemed to work indeed. @v/list still shows all the versions, but I guess it now downloads the bogus one I just pushed, and then removes itself as an acceptable candidate along with all the others an then does another download operation to @latest?

Exactly — and that should work even if the user has other (private) proxies that are also still serving cached versions.

Couldn't you incorporate this step serverside, to remove entries from @v/list based on retract statement parsing, to prevent the extra downloads and latency and also sort of shoehorn pre-1.16 compatibility?

In theory, yes — although that would cause Go 1.15 users to suddenly observe very different behavior, for which they may or may not be prepared.
Users upgrading from one Go release to another are generally at least somewhat prepared for changes in the tooling and underlying infrastructure, and can refer to the release notes to figure out what changed (especially if anything in their workflow breaks). OTOH, existing Go 1.15 users probably aren't expecting the behavior of go commands (even proxied ones) to suddenly change overnight.

It sounds like we can close this issue? We are not going to delete formerly published versions from the proxy storage, nor from the @v/list, which is how programs access that storage.

The retract directive does need to be in the semantically-highest listed version of the module, yes.
One way to make that work is to temporarily tag a higher version containing a retract directive that retracts both itself and the unwanted previous versions. Then go mod download that higher version via the proxy, so that it also becomes the highest tag in the proxy's list. Once that's done (and successfully ingested into the proxy), you can purge the erroneous tags so that users running with GOPROXY=direct won't bother checking the self-retracted version.

Reopening this issue because this technique doesn't work on pkg.go.dev. Specifically, the highest-version logic still chooses the highest tag, despite the retract statements. While it might still make sense to serve retracted documentation when explicitly requested, the "default view" should certainly take into account the retract statements, so that it mirrors the actual API people are using with go get'd modules. CC @julieqiu

pkgsite change to support retract is already tracked in https://github.com/golang/go/issues/43265 etc. So no need to reopen and change the subject of this issue.

Thanks, good to know.


feat: add new set of programs handled for vmware vsphere

Add new types of vsphere:
source
program:esxupdate
program:healthd
program:ConfigStore
program:crond
program:kmxa
program:crx-cli
program:backup.sh
program:configStoreBackup
program:heartbeat

Closes #1838

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


Transposition Cipher

Where's the PR template? And your PR has conflicting files as well correct it. @RC2208


Can I record output of AKSampler?

Hi. I'm creating an application which uses the AKSampler and an sfz file to play beats based off of the noteNumber. I want to be able to hit record and begin recording the output of the AKSampler and be able to play it back on a click of a button. Is this possible?

In the past when creating beats I used an OscillatorBank, AKMusicTrack, AKSequencer and the AKKeyboardDelegate to record and playback beats. I would like to do something similar with the AKSampler.

Hi there, I am not sure what the issue with AudioKit you are trying to address is.  You should be able to do what you describe.  As this is not necessarily a specific problem with AudioKit but rather an implementation question, I really want to encourage you to ask the questions on StackOverflow.


No Configs Given

It's annoying when you try to log in and it won't let you.  I got this app so I could speak to my friends, but now it seems pointless if it won't work

what issues?
On Sat, Apr 27, 2019 at 11:05 AM duplicate-issues[bot] <
<EMAIL_ADDRESS>wrote:

Hey @Lijjy https://github.com/Lijjy,
We did a quick check and this issue looks very darn similar to

#930 - suhoshi http://930
#929 - No configs given http://929
#928 - no config given http://928

This could be a coincidence, but if any of these issues solves your
problem then I did a good job 😄
If not, the maintainers will get to this issue shortly.
Cheers,
Your Friendly Neighborhood ProBot
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ifedapoolarewaju/igdm/issues/931#issuecomment-487272947,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL52DBRJH5TS7WTR4LNNVYLPSQQOLANCNFSM4HI34QBA
.

my igdm is not working, it says no configs given

same

same

how can fix it ??????

me too

same :(

anyone know how can i fix it??

same.. and today is a day that I reallyyy need to be able to check my messages so I hope it gets fixed soon

Já está assim há mais de 24 horas.

anyone know how can i fix it?

I don't understand this website at all, but once mine was able to update itself, it stopped working with the No Configs message.

same!


[Tests] Add block manager and scheduler tests

This upstream unit tests inside Anyscale that test block manager and scheduler. Several new features that will be upstreamed will update this file (e.g., chunked prefill).

cc @simon-mo

This PR is ready to be reviewed.

Will this PR conflict with #2762?

@zhuohan123 does it change the behavior of scheduler and block manager? I can merge the latest master

Seems to still pass tests after merging the latest master!


Task 3 4 5

@kurubabullesairam
Task -3
Code verified.
Task -4
Code verified. Pending with flow  code
Task -5
Code verified. Provide annotations.
Task -6
Code verified.
Task -7
Code verified. Provide annotations
Task -8
Code verified. Provide annotations
Task -9
Code verified.


Visual signature support

I am testing this library/utility and noticed support for visual signatures, however when attempting to sign a sample PDF, the visual signature doesn't appear at least in the latest version of Adobe.  Has this been tested?

There is a test case for visual signatures:
sign/pdfvisualsignature_test.go
I don't have tested myself this recently. Can you do a test based on the unit test (including) the file?

It doesn't show because the Rect is 0 0 0 0.
However even if I change the Rect I see nothing, I think because there is no reference to any other visual object...?

Ahhh that's because it's AcroForm stuff, so I would also need to set appearance and /AP object... ugh no. AcroForms = hell. :D

If you have a working example it would be great to add this to the documentation!

I don't think it can be done just with this library; if I look at other PDFs with visual signatures (made by Acrobat I think), it has AP appearence streams, and I am not sure this library can do it.
Maybe if it is somehow used with conjunction with pdfcpu https://github.com/pdfcpu/pdfcpu ... but that gets me thinking it would be maybe better to add the signing functionality into pdfcpu

@karelbilek I’ve just released a new version with some improvements and new signature types. Unfortunately, it doesn’t include support for visible signatures yet. However, I believe we can add basic support for features like an image or handwritten name in the future. Before we can do this, I need to refactor some code to make it easier to add new objects to the document. Please understand that this is not a high priority and it might take some time before I can work on it.

@karelbilek I have just pushed an update with initial support for visual signature appearance.
	err = SignFile(inputFilePath, outputFilePath, pdf.SignData{
		Signature: pdf.SignDataSignature{
			Info: pdf.SignDataSignatureInfo{
				Name:        "John Doe",
				Location:    "Somewhere",
				Reason:      "Test with visible signature",
				ContactInfo: "None",
			},
			CertType:   pdf.ApprovalSignature,
			DocMDPPerm: pdf.AllowFillingExistingFormFieldsAndSignaturesPerms,
		},
		Appearance: pdf.Appearance{
			Visible:     true,
			LowerLeftX:  350,
			LowerLeftY:  75,
			UpperRightX: 600,
			UpperRightY: 100,
		},
		DigestAlgorithm: crypto.SHA512,
		Signer:          pkey,
		Certificate:     cert,
	})

This is an initial implementation, known limitations include:

The signature shown is the SignData.SignDataSignatureInfo.Name

How flexible does this need to be?
Should we include "Digitally signed by", Date/Time, Location, Reason and ContactInfo when present?

The signature appearance is currently text based.

[ ] Add support for custom (background) images

The font is currently hard-coded in appearance.go

[ ] If the default font would be a nice handwitten style font.
[ ] It would be great if you could load a custom font and re-use when already present

The signature will not be shown in documents using an xref stream

[ ] The updatedXrefEntries entries (page object) needs to be added to xref stream similar like currently done in the xref table

I'm also considering to change the API to something like this:
 file := pdf.New()
 file.Load(reader)
 file.SetVisualSignature(rectangle, bytes)
 file.Sign(signer, certificate, options)
 file.TimeStamp(url, options)

OH WOW thanks!


Header structure name assumptions limit MSG abstraction capability

Is your feature request related to a problem? Please describe.
The MSG library is supposed to offer a complete abstraction of the header format, but in practice there are still some direct references to header structure members in Caelum which limit this capability.
In particular, when converting a local message buffer to a CFE_MSG_Message_t pointer, when passing into any CFE_SB API, the code references a sub-member, such as:
https://github.com/nasa/cFE/blob/64a6a59456fa9e47dc93e4bb9cecacc3d86d1862/modules/es/fsw/src/cfe_es_task.c#L396
While this was nice in that it is fully type-safe, it limits the header abstraction in two important ways:

It assumes/requires that the buffer itself contains a TlmHeader member.
It assumes/requires that the TlmHeader structure, in turn, contains a .Msg member.

For item (2) above, the TLM header is a structure controlled/defined by the CFE_MSG module, and there is no guarantee that a "Msg" member exists.  This will be a problem if an alternate MSG module is used, where the CFE_MSG_Message_t member is not called "Msg".  (The whole point of MSG is to make these structures free-form, and no assumptions should be made as to their internal structure, so this reference somewhat defeats that purpose).
Describe the solution you'd like

Convert this to a cast instead, e.g. (CFE_MSG_Message_t*)&CFE_ES_Global.TaskData.HkPacket
Have CFE_MSG provide a macro/inline function to implement this conversion/cast

Describe alternatives you've considered
Just document what the names need to be, and make it a requirement to name things in this manner.
Major issues with that - mainly that it is not friendly to automated tools which might be used to generate these headers/structures from a CMD/TLM database.
Additional context
There is no real convention to the names that exist today.  It would be more viable to do that if a specific convention/reasoning was followed, such as the CFE_MSG_Message_t member being called Message (i.e. without the CFE_MSG_ prefix or _t suffix).  This way a tool would know what name to call things in the generated files.  But as it is, there is simply no naming consistency in these members, a tool would have to hard-code "special" member names for each structure, for no good reason other than that's what a human had used for an abbreviation at one point.
But furthermore, even if a name convention was follwed prevents an additional layer of headers to be added.  For example, the "TlmHeader" is assumed contain a "Msg" member directly.  However in some implementations a user might want an intermediate header, where it would become .TlmHeader.Intermediate.Msg instead.  There is no way to accommodate a third layer with the current assumptions in the code.
Regarding suggested casts -- by casting, it can be converted without knowing what the member is specifically named, nor knowing how deep within the structure the Message structure lies.  This is not as bad as it sounds, and not really going back to being type-unsafe, because it is being cast to a CFE_MSG_Message_t*, not a void* as previous CFE versions had done here.  Because of this, and the fact that CFE is compiled with strict aliasing rules enabled, it will trigger an alias violation if the structure is not actually cast-able to a CFE_MSG_Message_t type.  While this is not quite as robust as the current type safety, it is much more flexible, and user errors/mismatches should still be caught.
Requester Info
Joseph Hickey, Vantage Systems, Inc.

Also worth noting that the SB code still has some references to CCSDS_SpacePacket_t around, which also limits the abstraction.  These should probably be fixed to reference CFE_MSG_Message_t instead.

Another "compromise" option might be to enforce a name convention, but only on the first/top level element, and make it work with a type safe inline function, without resorting to casts.
For example, if the convention was used where the name of the member is prescribed as the name of the MSG type without the CFE_MSG_ prefix nor the _t suffix, all CFE code would then need to define its member as CommandHeader and TelemetryHeader, respectively.  This would be a change to all modules (most use TlmHeader, but SB uses just Hdr - this would have to all be corrected to follow convention).
Then, a pair of type-safe inline conversion functions can be made, to convert a CFE_MSG_TelemetryHeader_t or CFE_MSG_CommandHeader_t to a CFE_MSG_Message_t.  This conversion would be part of MSG, so it would correlate to however MSG has defined the headers.


Merge developer branch to main branch (#2)

Update README

add new scripts and update readme

re-upload scripts and readme

update readme

re-update readme

modified:  README.md

update loss_functions and readme

add unfinished network object

update scripts and experimentation


Why is the generator loss continuously increasing instead of decreasing? Is continuous increase correct?

I'm also seeing this issue. My generator loss is following the same path as the screenshots in the repository (increasing), but it still doesn't seem right.


UWP Compilation Error

When you add the Microsoft.AspNetCore.WebUtilities package to a UWP App project, it does a build error:
C:\Users\UserName\.nuget\packages\Microsoft.AspNetCore.WebUtilities\1.1.1\lib\netstandard1.3\Microsoft.AspNetCore.WebUtilities.dll : error MSB3103: Invalid Resx file. Stream is not a valid resource file.
Steps to reproduce:

Create a project Blank App Universal Windows
Add the dependency "Microsoft.AspNetCore.WebUtilities": "1.1.1"
Build project

Tried with Visual Studio 2015 and 2017, same result.

This is a bug with how our cli was embedding .resx file from source dependencies and affects WebUtilities and DataProtection.Abstractions. We need to fix this in the next FTS patch. Note that this refactoring was only done in FTS so LTS packages (1.0.x) will work.
There's no real workarounds for this. There is only one string in the .resx file so the easy fix is to just move it out into the .cs file which is what we did in 2.0 anyway. The fix will be in the Common repo.

Issue has been proposed for a patch in https://github.com/aspnet/Common/issues/203.


chore: change add to import

LGTM, thanks!

Hm.. this PR updates label in dialog shown after clocking "Add"→"From IPFS path".
Should we also rename the "Add" button in the top corner?

Yes @lidel, sorry about that. I totally forgot about updating that.
I've changed both the Modal title (previously "Add from IPFS") and the Button ID & Text
Please review again 🙏


Task - Browse OTUs - OTU results seem arbitrary

Feature or enhancement
When browsing/typing an OTU (in any OTU field throughout TW) the dropdown menu does not display OTUs alphabetically and does not show obvious results.
For example, typing "Camponotus al" for "albipes" does not begin to yield the ~16 species of Camponotus that begin with "al".
The results show morphospecies first as opposed to valid species names first and will include the wrong genus name. See screenshot for whole list of results for "Camponotus al".
Fix: drop down menu should yield results alphabetically as each character is typed. If whole genus name is included, do not include other genus names. Similar issue with collector's names discussed in #3231 and #3216
@bpescador, @chrisgrinter, @rich-keller
Location
Task - Browse OTUs
Screenshot, napkin sketch of interface, or conceptual description

Your role
No response

For the collector, please use the last name and inicials format. It was tuned very well and and works in most of cases. For the otu name, the name of OTU indead uses the preference. It was done intentionally. I personally more often use Browse nomenclature interface, where the search is optimized by TaxonName. From there you can quickly jump to Browse OTU if needed. As a general rule, if you do not see a result, please keep typing probably one letter for a species name will be enough to find the right taxon. In most cases. a single letter abbreviation for the genus name and few letters for species work for me.

Thanks for the response.
I am having a very different experience with the results. I expect when I type "Camponotus al" (for Camponotus albipes) that the initial results displayed would include all Camponotus species beginning with "al" so I can choose. I get more relevant results typing "Camponotus a" , but still, the species beginning with "a" are not alphabetical and also do not include "albipes". The same issue of holds true in Browse nomenclature (see first screenshot for Camponotus albipes). Also, if I am entering data directly into TW I would not use the Browse nomenclature feature as it would be an extra step in our workflow.
And still, entering the last name of a collector first does not include all collectors with that last name so I will eventually just need to type in the whole name (see second and third screenshot for Johnson, R.A., and Fisher, B.L. respectively). This makes the dropdown menu somewhat irrelevant. If the dropdown menu was truly alphabetical as one types it would be quicker, visually less cluttered, and have less room for error. Otherwise, it would be quicker and visually less cluttered if I entered names by hand to avoid all incorrect names.

could you give me the server name and the project?

SANDBOX - build build e002b057b on 2023-02-01T11:13:48Z
and the project name is called Mar Antweb Import

I do not see it on sandbox.speciesfile.org, it shold be a different one, could you please copy the address line

https://github.com/SpeciesFileGroup/taxonworks/tree/e002b057b

sorry, not github. we have multiple sandbox databases. In the browser address line: sandbox.speciesfile.org; sandstorm.speciesfile.org, sandcastle.speciesfile.org and few more.

https://sandwich.taxonworks.org/hub is the main address
https://sandwich.taxonworks.org/projects/69 is the address when I click on Project

Thank you.
So yes I am looking in browse OTU. Yes, the name is out of search. And even if we sort the list alphabetically, it will be out, because the name has a subgeneric name. It is extremely hard to predict all possible search criteria. Especially for common names like 'alba'. But if in browse OTU I search "Cam albip" I get a single name. I just need to find a unique combination for the name. And keep typing before I get a result. In my experience, abbreviated genus name and more complete species name works better. In your list, you can see that each name has 'al' inside. What happens, I do not always have a correct spelling of the name lets say, the the name is 'albonotata' and the name is spelled as 'albinotata' in the paper. I have to do partial search to find it. To make it more complicated, I do not know what is misspelled, the genus or species epithet. I have to do partial search. An partial search do not always start with initial letter. Actively editing the DB of Auchenorrhyncha for several years, I found that the search interfaces are very efficient in TW, although, there are some marginal cases which are more difficult to find than the others.
Same for the authors. "Fisher" is so many Fisher in the DB, that if I simply alphabetize by the string, you will get "Fisher" without initials at the top of the list. The author list is optimized by the number of uses in the database. It is not always intuitive. But it is very efficient. If I need to search for "Dmitriev, Dmitry Alexandrovich" I will make a search for "Dmitriev, D.A." and will get a result, and again, all depends how common the name is. Dmitriev is not a common last name, I will get it with partial search, but with Fisher, adding one letter of initial returns your more precise list. In some extreme cases, more than one letter is needed. Please remember, that all authors are shared across the projects. We have almost 150.000 people already recorded across all projects. The search also prioritize the people previously used in the existing project. Sandboxes also has a lot of duplicates. The situation is little bit better in the production database.

Closing as out of date.  We've iterated on autocompletes in other issues, and they will certainly evolve, but the collective seems to like how they work now.


User Input

Implement a way for the user to submit a pdf while giving the foreman a way to approve or decline it.

see main page issue

PDF submit is connected to database and AWS. Approve and decline functions placed in icebox


you should make a requirements.txt instead of showing it on the README file

run
pip freeze > requirements.txt

while in your virtual environment to quickly grab all your packages and push it to the remote repository

so true bestie

bro's the python pedant

Thank you for your responses

bro's the python pedant

Just helping with open source contribution. Please be more respectful towards others next time, Mr. Yelloo5191.


Bad version reported for Dell BMC

On a Dell BMC iDrac 7.10.30, version reported is 7.10.00.
# ipmitool mc info
Device ID                 : 32
Device Revision           : 1
Firmware Revision         : 7.10
IPMI Version              : 2.0
Manufacturer ID           : 674
Manufacturer Name         : DELL Inc
Product ID                : 256 (0x0100)
Product Name              : Unknown (0x100)
.....
Aux Firmware Rev Info     :
    0x00
    0x1e
    0x1e
    0x00

The code is there:
https://github.com/packethost/packet-hardware/blob/master/packethardware/utils.py#L535
So we can see that the .30 is in fact in aux bytes 1 and 2, and in hex format 0x1e.
In fact, it seems to be .30.00 because reported version in iDrac is <IP_ADDRESS> so perhaps it's encoded in hex, bytes 2 and 3, and mirrored for similar use on little- and big-endian processors.
Original code assumed BCD format on byte 0.
I'm not sure how this should be handled. Perhaps version decoding should be handled differently according to Manufacturer ID.

Although I guess that wouldn't work for the few dell hosts we have disabled host OS access to the BMC from...

Fixed by #76


Vue code inside package

Is it possible to exclude vue code from the vue-grid-layout.min.js or npm package?

Vue is a dev dependency so it's not on the minified file...unless I'm seeing this wrong.


Fix data in assets

Without the data/<ServiceBindings|ServiceInstances>.json files the broker will not work so adding defaults. Also, since it makes little sense to have two paths for data JSON files, we are moving the assets/catalog.json to data and fixed the default assets/config.json to point to the data dir.

I think this is necessary. I will wait for any input from @xingzhou and @zhang-hua in case they have other kind of feedback.
Otherwise I will merge. @midoblgsm and I will be making many more changes to this code to reuse and improve, so keep that in mind. Ping me or respond here if you have different opinion, otherwise, I will merge.

I don't see any comments to the contrary so merging.


Feature/hero tooltip

Fixes #29

Changes proposed in this Pull Request:

Add a enableToolTip prop on Hero component
Add a ToolTipProps prop on Hero component for any MUI ToolTip overrides
Add knobs in 'Full Config' story, and 'Within a Banner' Story

Here's a picture of what it looks like when using the ToolTipProps to override the defaults.

Can you talk to Kyle to see if we have any standard designs for Tooltips (default)?

Can you talk to Kyle to see if we have any standard designs for Tooltips (default)?

Kyle said we're using the default MUI tooltip for now, but we might establish some custom defaults when we look further into the ToolTip design pattern.  The default for mobile needs some special attention.

Are we going to provide any special stylings for dark themes?

Can you talk to Kyle to see if we have any standard designs for Tooltips (default)?

Kyle said we're using the default MUI ToolTip for now, but we might establish some custom defaults when we look further into the ToolTip design pattern. The default for mobile needs some special attention.

If we don't have a defined design style around this does it make sense to do it now, or wait until then? Should we be making a separate component (like MUI Tooltip) that we update in one place. Assuming we have tooltip options on all of our components, I don't think we would want to have duplicated code everywhere.
How do our components work if you just wrap them with a MUI Tooltip component now?

Can you talk to Kyle to see if we have any standard designs for Tooltips (default)?

Kyle said we're using the default MUI ToolTip for now, but we might establish some custom defaults when we look further into the ToolTip design pattern. The default for mobile needs some special attention.

If we don't have a defined design style around this does it make sense to do it now, or wait until then? Should we be making a separate component (like MUI Tooltip) that we update in one place. Assuming we have tooltip options on all of our components, I don't think we would want to have duplicated code everywhere.
How do our components work if you just wrap them with a MUI Tooltip component now?

If we wrap the entire Hero will the tooltip, the only difference is that the entire Hero would show the tooltip, not just the label.  Right now I only wrapped the label part of the Hero because that's the element that commonly overflows.  If you want to wrap the entire Hero with a tooltip, we shouldn't be adding this functionality to the Hero component; just wrap the Hero with a ToolTip.
We should only make a separate PX Blue ToolTip if there are enough customizations to justify one.  Regardless of whether we use the MUI or a wrapper for the tooltip, the Hero API should remain unchanged since we accept ToolTipProps at the Hero level.
Also, I don't think our PX Blue themes have any ToolTip styles.

Closing this because this might be an unnecessary feature.   There is a branch 'experiment/hero-tooltip' that can referenced to.


Bump version to 3.1.1

@jtomaszewski @mjbellantoni Do you think we're OK to do a micro bump, or do we need a minor bump?

I want to remove the dependency on mbj/devtools, it's installing a huge number of gems we don't need at build time.

Micro is fine IMHO

I did an immediate bump to 3.1.1 from master. I'll update this for a minor bump to 3.2.0 next.


coordinator and maker processes crash due to Electrum error

During just all, we start the coordinator and maker binaries. In my experience, these processes usually (9 in 10 times) crash because of what seems like a timing issue due to Electrum not being ready yet.
2023-03-20 04:23:56  WARN electrum_client::client: call 'block_headers_subscribe_raw' failed with EOF while parsing a value at line 1 column 0, retry: 1/1
2023-03-20 04:23:58  INFO electrum_client::client: Succesfully created new client
2023-03-20 04:23:58  WARN electrum_client::client: call 'block_headers_subscribe_raw' failed after 2 attempts
Error: BDK wallet error

Caused by:
    Electrum(AllAttemptsErrored([JSON(Error("EOF while parsing a value", line: 1, column: 0))]))

One can work around this issue by manually restarting the processes via just coordinator and just maker after they fail to start during just all. In my experience, restarting them manually always succeeds, which further supports the timing-issue theory.

After a discussion with Philipp:

The issue in production is not so important because there coordinator and maker are started as docker containers which are already instructed to restart: unless-stopped. Eventually, electrs will be ready and the restarts will succeed. I considered better alternatives, but it seems like docker compose doesn't have good support for this. I tried a couple of approaches locally and none worked. This SO thread may provide some context on how this feature is no longer supported.
The issue for the dev environment should be fixed with https://github.com/get10101/10101/pull/295.


superset Flask CLI fails to launch in Debug mode: Refusing to start due to insecure SECRET_KEY

After #23186 , the superset Flask cli no longer starts unless a non-default SECRET_KEY is configured.
How to reproduce the bug

Checkout PR #23186
Enable Flask Debug: export FLASK_DEBUG=True
Run superset --help
See error: Refusing to start due to insecure SECRET_KEY

Expected results
superset CLI prints out the help page
Actual results
error: Refusing to start due to insecure SECRET_KEY
Environment
(please complete the following information):

browser type and version: NA
superset version: PR #23186
python version: 3.10
node.js version: NA
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

UPDATE As a workaround when only using built-in Flask commands, substituting superset for flask will fix the problem.

Refusing to start due to insecure SECRET_KEY
Same issue when I run docker-compose -f docker-compose-non-dev.yml up

Another more reliable workaround is to add TESTING = 1 into your custom superset config file, which is probably more suitable for docker container folks.

Can you not just set the secret key to something more custom, as it's warning you to do?

Assuming you have set your own SECRET_KEY for your environment, if the cli still fails this probably mean the cli is not picking up your config override with your SECRET_KEY
example:
export SUPERSET_CONFIG=superset_config; superset

Nope. I am not setting my own SECRET_KEY. Sorry if that wasn't clear from the original description.
The problem is that PR #23186 does not seem to work as advertised when running in Flask Debug mode.

Seems like this is all good now and should've been closed. Let me know if I'm mistaken, and we can re-open with updated context.