Issue with Loading The Index.html resource

I have a few packages that I am testing out before I integrate the project with my main project. I can verify that the the uploading of the courses are successful and that the database updates accordingly, but when I try to launch these courses, I get a blank screen. Under the network tab, I see that a call is made to load the index.html file, but that resource is returning with a 404 error

This is a very common error. It means that the virtual folder you specified
in Appsettings isn't pointing to the actual content folder.
How to fix:
Look at the url in the network tab.
Does the folder it is referencing exist in your application?
If not, change the value in AppSettings to match the folder where you
actually store your content.
On Wed, Nov 24, 2021 at 12:51 PM Jared @.***> wrote:

I have a few packages that I am testing out before I integrate the project
with my main project. I can verify that the the uploading of the courses
are successful and that the database updates accordingly, but when I try to
launch these courses, I get a blank screen. Under the network tab, I see
that a call is made to load the index.html file, but that resource is
returning with a 404 error
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dhodges47/SCORM-LearningManagementSystem/issues/22,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5OFWCT7DJ4RKUTKF2HTDUNUQ2XANCNFSM5IWVIUHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

The above suggestion fixed my issue. I was zipping the folder instead of just the content inside of the folder and the program was confused to why the index file wasn't found


Fix legend text wrapping in IE.

IE9-11 and Edge 12-13 can be completely fixed using box-sizing: border-box; max-width: 100%, but IE8 will still experience some issues as “the min-width property applies to content-box even if box-sizing is set to border-box” cite.
IE8-11 can be fixed using the 456 Berea St fix display: table; white-space: normal, but this fix will not work at all for Edge 12-13.

We have a legend style override in https://github.com/alphagov/govuk_elements/blob/master/public/sass/elements/_forms.scss#L22 already. Presumably this code would be better placed there? Also, can you link to a page on 456berastreet in the commit?

I think it should sit in the reset stylesheet.
I need to test this (which is why it hasn't been merged yet), ideally L22 from forms.scss would be moved into the reset stylesheet too (or removed if not required).
I'll investigate later today.

I'd place it as a reset, it's included in normalize.
@robinwhittleton How to line wrap text in legend elements, even in IE

I think it really helps to see screenshots with fixes like this.
Here's a screenshot before:
Win10 Edge 13

Here's what Normalize uses to fix text wrapping in Edge and IE
legend {
  box-sizing: border-box; /* 1 */
  color: inherit; /* 2 */
  display: table; /* 1 */
  max-width: 100%; /* 1 */
  padding: 0; /* 3 */
  white-space: normal; /* 1 */
}

Here's a screenshot after:
Win10 Edge13


Question: Does Acrylic move out of the OS into ProjectReunion

The WinUI team have had to drop support for HostBackdrop Acrylic due to it being tied up with the OS code.
So does Project Reunion allow for this Acrylic code to get updated in time for WinUI 3.0 release at the end of the year?

I hope so, but at the same time the project is trying to decouple from the OS too so it’s not really clear...

I hope so, but at the same time the project is trying to decouple from the OS too so it’s not really clear...

This project will have some lower level APIs taken out of the OS - so if Acrylic needs lower level code to work - this could be how its done.

Can you ask this on the WinUI3 repo?
Also, can you tell us more about how you're using HostBackdrop in your app?

Can you ask this on the WinUI3 repo?
Also, can you tell us more about how you're using HostBackdrop in your app?

The AcrylicBrush used for sidebars or Calculator's background - requires the Host Backdrop.  WinUI has said they are having difficulty separating it from the OS.
So I wondered if it is within the scope of this wider Project Reunion codebase.

Thanks for the suggestion! You're right, Acrylic is a super important part of the Fluent design we want to bring to all apps.  We're working on some things here for the future. For now, @stevewri  assigned to track.

I don't understand why WinUI is trying to decouple Acrylic backgroundbrush from the OS. It's not possible, as it needs the functionality of the DWM and DirectComposition engine to render content behind the application window.

Like Jon said, we're looking at some ideas for this. The thread has gone fairly quiet, so I'll close it for now. Please feel free to open it back up, and/or we'll tag it with a pointer to a proposal if/when we can flesh out those ideas.

A thought that occured to me in another repo...
I wonder if going back to Windows 7 - WinUI/Reunion could provide a driver, which provides the Rendered layer needed to handle Acrylic.  WinUI apps on deployment and new OS versions could include the driver which provides the base layer render visual, via the Store.
Windows 7 and Vista before it must have had the capability for the Aero Glass rendering.  Windows 8/8.1 had the Visual Composition Layer.  So perhaps this is more of a Reunion ask, but if the driver handled the OS dependent stuff, the rest could all remain User level right?


Misc. perf improvements:

Remove unused infos

Avoid String copies in String lookup

Fix parallel to allow more than one background thread

Checked on linux in-ram fs. Looks good: +20-30%.


'Add to Watch' is broken for C#

This is an issue with VS Code, but tracking here as we will eventually need to do work to light up the right experience depending on how the VS Code team decides to fix this. The VS Code issue is https://github.com/Microsoft/vscode-debugadapter-node/issues/73.
Steps to reproduce
Install .NET Core, VS Code, and the C# extension (see http://aka.ms/vscclrdebugger for instruction)
Create hello world with dotnet new
Debug hello world and stop at the first line
Look at the locals window
Right click on args and invoke 'Add to Watch'
Expected  behavior
VS Code adds args to the watch window
Actual behavior
VS Code adds args [string[]] to the watch window, which can't be evaluated since that isn't valid C#.

The VS Code part of this issue is tracked with https://github.com/Microsoft/vscode/issues/13877

This issue will be fixed with the next inserted debugger.


Add falqon algorithm to qiskit-terra

Summary
To add the Feedback-based quantum optimization (falqon) algorithm (arxiv.)
Details and comments
I lack the falqon algorithm in qiskit. I've written my own little version based on other implementations and I would like to adjust it so I can contribute do qiskit-terra. I am asking for suggestions on the next steps to be taken.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi. At present the existing algorithms in Qiskit Terra are being refactored to use the primitives (samplers and estimators) that have been introduced to Qiskit (existing algorithms are all being marked pending deprecation and will later be deprecated and removed). For instance VQE, QAOA are refactored here #8702 and #8669 and you might like to take a look to see if/how this algorithm you have implemented can be done using such primitives. Also as a minimum eigen solver the algorithm should implement the MinimumEigensolver interface to allow any upper level applications to use the algorithm in a standard way via that interface. You can see this in the referenced PRs where VQE etc implement this interface and pass back a given result type, although they can extend the result class and add algorithm result specifics.


[terra-menu] Added keyboard navigation and selected/unselected instructions

Summary
What was changed:

Added submenu arrow key navigation instruction context to first item only.
Added selected/unselected instruction instead of checked/unchecked for menu items ( JAWS ).

Why it was changed:

keyboard arrow key navigation instruction is missing in sub menu.
User might got confusion if SR reading checked/unchecked on menu items.

Testing
This change was tested using:

[ ] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[x] Accessibility review
[ ] Functional review

Additional Details
This PR resolves:
UXPLATFORM-9315
UXPLATFORM-9369

+1 for UX accessibility changes.


Fragment support

Already running into cases where fragment support is needed. A simple example is an "hoc" component where it just renders out the children property. Currently you have to wrap the children in another element like a div.

Fragment support would be a good to have, certainly.
Now this might require a bit of rework, since forgo assumes an outer/wrapper node (instead of an array of nodes) and tracks/attaches component state on that node. Now it would be possible to attach this information to the first node in a list (and mark it as say 'fragment start') - but there would be changes to be made in many places.
Definitely a feature I'd consider worth having.

Fragment support would be a good to have, certainly.
Now this might require a bit of rework, since forgo assumes an outer/wrapper node (instead of an array of nodes) and tracks/attaches component state on that node. Now it would be possible to attach this information to the first node in a list (and mark it as say 'fragment start') - but there would be changes to be made in many places.
Definitely a feature I'd consider worth having.

Forgo is now less than 2KB minified + gzipped. So whatever we do, we gotta be within the size budget as well.

Forgo is now less than 2KB minified + gzipped. So whatever we do, we gotta be within the size budget as well.

In the meanwhile, you can work around lack of fragment support for many purposes with a div assigned the style display: contents, which instructs the browser to replace the element with its children. The div will still show up in DevTools, but for rendering and styling purposes it seems like it behaves more or less like fragment support built into the browser.

In the meanwhile, you can work around lack of fragment support for many purposes with a div assigned the style display: contents, which instructs the browser to replace the element with its children. The div will still show up in DevTools, but for rendering and styling purposes it seems like it behaves more or less like fragment support built into the browser.

Implemented in 0.0.36. There are likely to be some bugs - required quite some changes.

Implemented in 0.0.36. There are likely to be some bugs - required quite some changes.

I'll close this for now. Fragements are probably still buggy, but we'll track bugs separately.

Work's keeping me too busy to do rigorous testing, but I did a quick find/replace in my app of my <div className="contents"> with <> and it looks like the new fragment support works right. Thanks!

Thanks for the test, appreciate it.
I expect it to be a bit buggy for now; a lot of the innards have changed. The earlier code worked under the assumption that every Custom Component would result in a single container DOM node, and it was a good place to hold state. Now that doesn't hold any longer - so there's some new code in there.


PHP degraded in 9.x?

I went to update my site from 8.4 to 9.3 and noticed that PHP highlight lost details. Seems to no longer recognize variables (maybe more?).
See screenshot before/after:

Example, screenshot was taken from, live here http://www.rarst.net/code/dependency-injection/ (still on 8.4 hadn't pushed 9.3 up).

Dropping highlighting of regular variables was deliberate, this is a design decision. We should bring back $this though as it is special…

I've fixed $this and have gone ahead and fixed the whole issue, as it is unlikely we revert to highlighting plain user-defined variables.

Why so?.. Variable seems to be pretty staple thing to highlight.
Loosely related — I also find it very nifty in IDE when variables and passed arguments are treated separately for highlight, easy to distinguish what is passed into function and what is created inside of it.

The reason is two-fold.
First, we just want to be consistent across languages. Most highlighters don't highlight local variables in other languages simply because they're not syntactically distinguishable. In PHP (and, say, Perl) they're easy to highlight because of the $ sign. But "because we can" is not reason enough.
Second, one of our design guidelines is to keep the bulk of code plain and only highlight things that are semantically significant, and highlighting them will add to code readability (all of this highly subjective and fuzzy, of course). Thus, we don't highlight many things that others do: UPPERCASE_CONSTANTS, CamelCaseNames, .method_calls().

I also find it very nifty in IDE when variables and passed arguments are treated separately for highlight

This we can't do because a highlighter has to work at the syntactic level, it can't keep track of the meaning of identifiers, for example.

Fair enough, thanks for the fix on $this at least.  :)

Looked for something in older post and PHP highlight is nearly gone in some snippets.

Without variables, properties, methods... Not much of highlight, it's nearly plain text.

It actually does look good to me, honestly. I understand it's subjective but that's how it is.


feature: configure codegen to add @sharable directive in PageInfo type

Please read our contributor guide before
creating an issue. Also consider discussing your idea on
the discussion forum first.
Describe the Feature Request
Add custom directives like @cacheControl(maxAge: 30) @shareable @tag(name: "public") to generated types when using codegen to types like Pageinfo and other Connection Types and reflect in the SDL of a running graphql project/server
the generated PageInfo Type should look like below in the SDL:
type PageInfo @cacheControl(maxAge: 30) @shareable @tag(name: "public"){
    hasPreviousPage: Boolean!
    hasNextPage: Boolean!
    startCursor: String
    endCursor: String
}

Also can the Connection Type can have 1 more additional field totalCount so that the SDL can look like below:
Connection{
  edges:[Edge!]
  pageInfo:PageInfo!
  totalCount:Int!
}

This will be beneficial to show in UI something like showing results 1-10 out of 500(totalCount) records
Describe Preferred Solution
Allow configuration in pom file in pom or gradle to mention to add @sharable tags in PageInfo tags while generating it and result it in the final SDL
Describe Alternatives
None as such

@kilink can we have something like this?
Ultimately i want to generate the Connection types with custom directives on those in SDL so that it can be used in a federated supergraph in codegen, as defining relay based pagination types and managing them in all the subgraphs is not helping when we have to write the logic manually all over again for each query

@srinivasankavitha

HI - codegen is not used to generate SDL. It only generates POJOs based on a statically defined SDL. The framework handles basic dynamic generation of SDL for pagination. If you require more custom logioc, directives, it would be better to manually add that to your SDL rather than using the @connection directive.
Hope this helps.

I think for your custom PageInfo, you should just add it yourself to your schema. The pagination support will only add a PageInfo type if one doesn't already exist.
For the Connection types, I could see an argument for adding a flag to the directive to have it generate the totalCount field. Probably in the meantime you could add a @DgsTypeDefinitionRegistry provider that transforms the Connection type and adds the field?

Closing this issue because we want to avoid adding more flags and customization to Codegen whenever possible to avoid complexity of the plugin. Since there is a workaround for this issue we shouldn't add it to codegen.


Automata being listed in the app

The course "Automata" is still listed in the app, however it's not available anymore and isn't in the github page either.

@GregoryGoncalves thanks for report this. I'll close that issue because we already have others opened here related with this.


Can't find stylesheet to import

After the update from v1.2.0 to v1.5.1 I get this error in my tests and in my app (Ruby on Rails):
Failure/Error: <%= stylesheet_link_tag 'mirror', media: 'all', 'data-turbolinks-track' => true %>

      ActionView::Template::Error:
        Can't find stylesheet to import.
      # /usr/local/bundle/gems/sassc-embedded-1.5.2/lib/sassc/embedded.rb:51:in `rescue in render'
      # /usr/local/bundle/gems/sassc-embedded-1.5.2/lib/sassc/embedded.rb:14:in `render'
      # /usr/local/bundle/gems/sassc-rails-2.1.2/lib/sassc/rails/template.rb:40:in `block in call'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/utils.rb:141:in `module_include'
      # /usr/local/bundle/gems/sassc-rails-2.1.2/lib/sassc/rails/template.rb:39:in `call'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:84:in `call_processor'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:66:in `block in call_processors'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `reverse_each'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `call_processors'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:22:in `block in <class:CompositeProcessor>'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:33:in `call'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:84:in `call_processor'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:66:in `block in call_processors'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `reverse_each'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `call_processors'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:182:in `load_from_unloaded'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:59:in `block in load'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:337:in `fetch_asset_from_dependency_cache'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:43:in `load'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/cached_environment.rb:44:in `load'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/bundle.rb:27:in `call'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:84:in `call_processor'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:66:in `block in call_processors'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `reverse_each'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `call_processors'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:182:in `load_from_unloaded'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:59:in `block in load'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:337:in `fetch_asset_from_dependency_cache'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:43:in `load'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/cached_environment.rb:44:in `load'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/bundle.rb:32:in `block in call'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/bundle.rb:31:in `call'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:84:in `call_processor'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:66:in `block in call_processors'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `reverse_each'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/processor_utils.rb:65:in `call_processors'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:182:in `load_from_unloaded'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:59:in `block in load'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:337:in `fetch_asset_from_dependency_cache'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/loader.rb:43:in `load'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/cached_environment.rb:44:in `load'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/base.rb:81:in `find_asset'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/base.rb:88:in `find_all_linked_assets'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:125:in `each'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:125:in `to_a'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:125:in `block (2 levels) in find'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/executor/safe_task_executor.rb:24:in `block in execute'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/synchronization/mutex_lockable_object.rb:47:in `block in synchronize'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/synchronization/mutex_lockable_object.rb:47:in `synchronize'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/synchronization/mutex_lockable_object.rb:47:in `synchronize'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/executor/safe_task_executor.rb:22:in `execute'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/promise.rb:564:in `block in realize'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/executor/immediate_executor.rb:29:in `post'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/promise.rb:563:in `realize'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/promise.rb:250:in `execute'
      # /usr/local/bundle/gems/concurrent-ruby-1.1.10/lib/concurrent-ruby/concurrent/promise.rb:297:in `execute'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:124:in `block in find'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:123:in `map'
      # /usr/local/bundle/gems/sprockets-4.0.3/lib/sprockets/manifest.rb:123:in `find'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/railtie.rb:53:in `each'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/railtie.rb:53:in `map'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/railtie.rb:53:in `precompiled_assets'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/railtie.rb:38:in `asset_precompiled?'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/railtie.rb:266:in `block (3 levels) in <class:Railtie>'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:368:in `precompiled?'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:372:in `raise_unless_precompiled_asset'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:338:in `digest_path'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:326:in `asset_path'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:103:in `block in resolve_asset_path'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:243:in `block in resolve_asset'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:242:in `each'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:242:in `detect'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:242:in `resolve_asset'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:102:in `resolve_asset_path'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:80:in `compute_asset_path'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/helpers/asset_url_helper.rb:203:in `asset_path'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/helpers/asset_url_helper.rb:348:in `stylesheet_path'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/helpers/asset_tag_helper.rb:161:in `block in stylesheet_link_tag'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/helpers/asset_tag_helper.rb:160:in `map'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/helpers/asset_tag_helper.rb:160:in `stylesheet_link_tag'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:186:in `block in stylesheet_link_tag'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:184:in `map'
      # /usr/local/bundle/gems/sprockets-rails-3.4.2/lib/sprockets/rails/helper.rb:184:in `stylesheet_link_tag'
      # ./app/views/layouts/mirror.html.erb:10:in `_app_views_layouts_mirror_html_erb___3220360303617532381_520720'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/base.rb:247:in `public_send'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/base.rb:247:in `_run'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/template.rb:154:in `block in render'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/notifications.rb:203:in `block in instrument'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/notifications.rb:203:in `instrument'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/template.rb:345:in `instrument_render_template'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/template.rb:152:in `render'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/renderer/template_renderer.rb:72:in `block in render_with_layout'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/notifications.rb:203:in `block in instrument'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/notifications.rb:203:in `instrument'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/renderer/template_renderer.rb:70:in `render_with_layout'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/renderer/template_renderer.rb:55:in `render_template'
      # /usr/local/bundle/bundler/gems/solidus_multi_domain-3f888260801a/app/decorators/lib/solidus_multi_domain/action_view/template_renderer_decorator.rb:9:in `render_template'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/renderer/template_renderer.rb:11:in `render'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/renderer/renderer.rb:61:in `render_template_to_object'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/renderer/renderer.rb:29:in `render_to_object'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/rendering.rb:117:in `block in _render_template'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/base.rb:273:in `in_rendering_context'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/rendering.rb:116:in `_render_template'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/streaming.rb:218:in `_render_template'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/rendering.rb:103:in `render_to_body'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/rendering.rb:52:in `render_to_body'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/renderers.rb:142:in `render_to_body'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/abstract_controller/rendering.rb:25:in `render'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/rendering.rb:36:in `render'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/instrumentation.rb:46:in `block (2 levels) in render'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/core_ext/benchmark.rb:14:in `ms'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/instrumentation.rb:46:in `block in render'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/instrumentation.rb:86:in `cleanup_view_runtime'
      # /usr/local/bundle/gems/activerecord-6.1.5/lib/active_record/railties/controller_runtime.rb:34:in `cleanup_view_runtime'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/instrumentation.rb:45:in `render'
      # ./app/controllers/mirrors_controller.rb:68:in `index'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/abstract_controller/base.rb:228:in `process_action'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/rendering.rb:30:in `process_action'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/abstract_controller/callbacks.rb:42:in `block in process_action'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/callbacks.rb:117:in `block in run_callbacks'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/core_ext/time/zones.rb:66:in `use_zone'
      # ./app/controllers/mirrors_controller.rb:219:in `use_time_zone'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/callbacks.rb:126:in `block in run_callbacks'
      # /usr/local/bundle/gems/actiontext-6.1.5/lib/action_text/rendering.rb:20:in `with_renderer'
      # /usr/local/bundle/gems/actiontext-6.1.5/lib/action_text/engine.rb:59:in `block (4 levels) in <class:Engine>'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/callbacks.rb:126:in `instance_exec'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/callbacks.rb:126:in `block in run_callbacks'
      # /usr/local/bundle/gems/react-rails-2.6.1/lib/react/rails/controller_lifecycle.rb:31:in `use_react_component_helper'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/callbacks.rb:126:in `block in run_callbacks'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/callbacks.rb:137:in `run_callbacks'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/abstract_controller/callbacks.rb:41:in `process_action'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/rescue.rb:22:in `process_action'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/instrumentation.rb:34:in `block in process_action'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/notifications.rb:203:in `block in instrument'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/notifications.rb:203:in `instrument'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/instrumentation.rb:33:in `process_action'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal/params_wrapper.rb:249:in `process_action'
      # /usr/local/bundle/gems/activerecord-6.1.5/lib/active_record/railties/controller_runtime.rb:27:in `process_action'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/abstract_controller/base.rb:165:in `process'
      # /usr/local/bundle/gems/actionview-6.1.5/lib/action_view/rendering.rb:39:in `process'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal.rb:190:in `dispatch'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_controller/metal.rb:254:in `dispatch'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/routing/route_set.rb:50:in `dispatch'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/routing/route_set.rb:33:in `serve'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/journey/router.rb:50:in `block in serve'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/journey/router.rb:32:in `each'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/journey/router.rb:32:in `serve'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/routing/route_set.rb:842:in `call'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in `call!'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in `call'
      # /usr/local/bundle/gems/bullet-7.0.1/lib/bullet/rack.rb:15:in `call'
      # /usr/local/bundle/gems/http_accept_language-2.1.1/lib/http_accept_language/middleware.rb:14:in `call'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in `call!'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in `call'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in `call!'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in `call'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in `call!'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in `call'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in `call!'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in `call'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in `call!'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in `call'
      # /usr/local/bundle/gems/omniauth-2.0.4/lib/omniauth/builder.rb:45:in `call'
      # /usr/local/bundle/gems/dragonfly-1.4.0/lib/dragonfly/middleware.rb:14:in `call'
      # /usr/local/bundle/gems/dragonfly-1.4.0/lib/dragonfly/middleware.rb:14:in `call'
      # /usr/local/bundle/gems/rack-attack-6.6.0/lib/rack/attack.rb:103:in `call'
      # /usr/local/bundle/gems/rack-attack-6.6.0/lib/rack/attack.rb:110:in `call'
      # /usr/local/bundle/gems/warden-1.2.9/lib/warden/manager.rb:36:in `block in call'
      # /usr/local/bundle/gems/warden-1.2.9/lib/warden/manager.rb:34:in `catch'
      # /usr/local/bundle/gems/warden-1.2.9/lib/warden/manager.rb:34:in `call'
      # /usr/local/bundle/gems/rack-2.2.3/lib/rack/tempfile_reaper.rb:15:in `call'
      # /usr/local/bundle/gems/rack-2.2.3/lib/rack/etag.rb:27:in `call'
      # /usr/local/bundle/gems/rack-2.2.3/lib/rack/conditional_get.rb:27:in `call'
      # /usr/local/bundle/gems/rack-2.2.3/lib/rack/head.rb:12:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/http/permissions_policy.rb:22:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/http/content_security_policy.rb:19:in `call'
      # /usr/local/bundle/gems/rack-2.2.3/lib/rack/session/abstract/id.rb:266:in `context'
      # /usr/local/bundle/gems/rack-2.2.3/lib/rack/session/abstract/id.rb:260:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/cookies.rb:689:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/callbacks.rb:98:in `run_callbacks'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/callbacks.rb:26:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/executor.rb:14:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/actionable_exceptions.rb:18:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/debug_exceptions.rb:29:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
      # /usr/local/bundle/gems/railties-6.1.5/lib/rails/rack/logger.rb:37:in `call_app'
      # /usr/local/bundle/gems/railties-6.1.5/lib/rails/rack/logger.rb:26:in `block in call'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/tagged_logging.rb:99:in `block in tagged'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/tagged_logging.rb:37:in `tagged'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/tagged_logging.rb:99:in `tagged'
      # /usr/local/bundle/gems/railties-6.1.5/lib/rails/rack/logger.rb:26:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
      # /usr/local/bundle/gems/request_store-1.5.1/lib/request_store/middleware.rb:19:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/request_id.rb:26:in `call'
      # /usr/local/bundle/gems/rack-2.2.3/lib/rack/method_override.rb:24:in `call'
      # /usr/local/bundle/gems/rack-2.2.3/lib/rack/runtime.rb:22:in `call'
      # /usr/local/bundle/gems/activesupport-6.1.5/lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/executor.rb:14:in `call'
      # /usr/local/bundle/gems/dragonfly-1.4.0/lib/dragonfly/cookie_monster.rb:9:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/static.rb:24:in `call'
      # /usr/local/bundle/gems/rack-2.2.3/lib/rack/sendfile.rb:110:in `call'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/middleware/host_authorization.rb:142:in `call'
      # /usr/local/bundle/gems/rack-cors-1.1.1/lib/rack/cors.rb:100:in `call'
      # /usr/local/bundle/gems/railties-6.1.5/lib/rails/engine.rb:539:in `call'
      # /usr/local/bundle/gems/rack-test-1.1.0/lib/rack/mock_session.rb:29:in `request'
      # /usr/local/bundle/gems/rack-test-1.1.0/lib/rack/test.rb:266:in `process_request'
      # /usr/local/bundle/gems/rack-test-1.1.0/lib/rack/test.rb:119:in `request'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/testing/integration.rb:279:in `process'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/testing/integration.rb:16:in `get'
      # /usr/local/bundle/gems/actionpack-6.1.5/lib/action_dispatch/testing/integration.rb:372:in `get'
      # /usr/local/bundle/gems/rails-controller-testing-1.0.5/lib/rails/controller/testing/integration.rb:16:in `block (2 levels) in <module:Integration>'
      # ./spec/requests/mirrors_spec.rb:14:in `block (3 levels) in <top (required)>'
      # /usr/local/bundle/gems/webmock-3.14.0/lib/webmock/rspec.rb:37:in `block (2 levels) in <top (required)>'
      # ------------------
      # --- Caused by: ---
      # Sass::CompileError:
      #   Can't find stylesheet to import.
      #   /usr/local/bundle/gems/sass-embedded-1.3.2/lib/sass/embedded/protofier.rb:16:in `from_proto_compile_response'

I've had a look at which version I see this error for the first time and right after v1.2.0 (in v1.3.0) I have another one (Sprockets::FileNotFound) and from v1.3.1 I have the error in the title.
Thank you for your support.
Let me know if you need other info to solve the issue.

1.5.3 has been released to address an issue where importing filename with dot would fail: e.g. @import "foo.bar" would fail to load foo.bar.scss.
@afdev82 Can you please try and see if this fixes your issue?

Now it's fixed, thank you!
It's strange, because the file I was importing doesn't have the dot in the name.
The source path is: app/assets/stylesheets/mirror.scss
The entry in my app/assets/config/manifest.js: //= link mirror.css
The import statement is: stylesheet_link_tag 'mirror', media: 'all', 'data-turbolinks-track' => true

If you mean other files that were imported by @import inside the main file, at some point in one imported file there was
@import '../fonts/weathericons';

maybe this was the problem, I don't know.


front: refactor AgentUserRelation

There was a few things to refactor:

Naming: AgentUserRelation the table remains the same but the column is listStatusOverride
userListStatus on AgentConfigurationType now simply says whether the agent is in list or not
endpoint to work with it is also simplified
Major problem with AgentUserRelation which was pointing to agentConfigurationId as a foreign key which is not an agentConfiguration but an agentConfiguratio version. Moved to pointing to the sId instead.

cc @lasryaric for query optimization (aligned with what we've done so far + removed at list one JOIN as a result)
Deploy plan:

run init_db.sh on front-edge
deploy front
(note that this table is empty in production)

Unrelated - Now I see the no-op "Test" button when removed from my list => I had scoped that separately since it's not a priority; maybe don't display it for now?

console.log removed and Test button removed.
I think it's fine to have 2 queries here given preFetch, we can revisit in the future of course, but I'm in favor of not pushing sequelize too much given how not great it is.


Add material with more features

Commit
issues
project
collaborators

Move it to project.

Combined the lesson sheet with presentations


Bug 500 error when invalid url

Fixes #824

@jhatmaker sorry for delay getting this in. Could you please resolve the conflict and add a line to the CHANGELOG file, mentioning your fix? I'll get it in ahead of upcoming release.


bootstrap.min.3.3.5.js can be remove

we have import bootstrap-3.3.7.min.js, so bootstrap.min.3.3.5.js can be removed?

Fixed by https://github.com/skydive-project/skydive/pull/1851

Thanks


Is maggy applicable to my use case?

Hi, I've just found this library and it seems great, but wanted to quickly double-check if it's applicable to my use case. Namely, I have a large amount of tabular data stored in Spark DataFrames (so the data is distributed on multiple machines) on databricks and I'm using a Spark ML model. Will I be able to run trials in parallel with such setting using maggy?

Hey!
Thanks for your interest! Maggy is very applicable to your use case, however, at this point in time it is very much tied to Hopsworks. If you want to try it out on Hopsworks, you can get access to a free demo instance on hopsworks.ai or you can deploy an entire Hopsworks instance to your own AWS account.
We are working on making Maggy more general, but it will take few more weeks for it to be ready for use on any Spark Cluster.
We are planning to release a standalone version of Maggy for the Data+AI Summit Europe in two weeks, or shortly thereafter.
Please come back and check the repo for any new releases!
In the meantime if you want to know more about Maggy as a research project, we have some blogposts (here and here. And also a paper at the MLOps Workshop of this years MLSys conference.
Hope that answers your questions!
I will ping you here, once we made another release!

Thanks for a comprehensive response and all the references. In this case, I will wait for the standalone version. Looking forward to it!

Hi @moritzmeister, I was wondering what's the status of Maggy, did you manage to make it standalone? :)

@moritzmeister I am also interested on this response.
Also, I was wondering how Maggy knows how to contact Spark's driver to make the RPC calls in another Spark infrastructure that is not Hopsworks or atleast how to "you can deploy an entire Hopsworks instance to your own AWS account". The reason behind this question is because in this example here (https://github.com/logicalclocks/maggy/blob/master/examples/maggy-ablation-titanic-example.ipynb), a spark session is created but I cannot explicitly see the point where Maggy hands over/submits jobs to Spark.  Thanks for your interest! We're working on it but it's not there yet. Hope to get it done by mid January.

@moritzmeister Thank you for the response. Will it be published somewhere?

@moritzmeister Thank you for the response. Will it be published somewhere?

Any updates on this?

Hey @crakama, sorry I must've missed your previous message! With increasing interest we are now working towards a major 1.0 release. So we are getting there but it will still take some time.

Hi @blazejdolicki, hi @crakama,
it took us a while, but we just published a 1.0.0rc0 release candidate on PyPi. Give it a try on your Spark clusters. I suspect there are still a few bugs, but we are working on fixing them until the main release.
To get people started, there are a bunch more example notebooks now in
https://github.com/logicalclocks/maggy/tree/master/examples
Also we are redesigning/rewriting the documentation, so keep an eye on www.maggy.ai :)
And we wrote some Blog posts, which can serve as a kind of documentation until then:

https://www.logicalclocks.com/blog/distributed-ml-experiments-with-databricks-and-maggy
https://www.logicalclocks.com/blog/from-100-to-zero-pytorch-and-deepspeed-zero-on-any-spark-cluster-with-maggy

Feel free to open new issues here on GitHub if you have specific questions or encounter any bugs.
I am closing this issue here. Looking forward to any feedback you might have!

Thanks for letting us know!

Hi,
Unfortunately when I install maggy from pip I get this error : ERROR: Could
not find a version that satisfies the requirement maggy==1.0.0rc0 (from
versions: 0.0.1, 0.1, 0.1.1, 0.2, 0.2.1, 0.2.2, 0.3.0, 0.3.1, 0.3.2, 0.3.3,
0.4.0, 0.4.1, 0.4.2, 0.5.0, 0.5.1, 0.5.2, 0.5.3)
ERROR: No matching distribution found for maggy==1.0.0rc0
Catherine .N. Rakama.
MS.Software Engineering of Distributed Systems | KTH Royal Institute of
Technology
SKype: crakama | +46 738760582
On Tue, May 25, 2021 at 6:35 PM blazejdolicki @.***>
wrote:

Thanks for letting us know!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/logicalclocks/maggy/issues/69#issuecomment-848034372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD7UVCVDKY4363B7ONLOWDLTPPGVBANCNFSM4TEX2O3Q
.

Hi @crakama,
that is very strange, what kind of python environment are you using and which version of pip? The release is on pypi: https://pypi.org/project/maggy/1.0.0rc0/. Alternatively, I also uploaded the wheel to the release tag here on github https://github.com/logicalclocks/maggy/releases/tag/1.0.0rc0
I just tested it with Python 3.8.8 and Pip 21.1.1 and I can install it as expected:
(test-maggy) moritzmeister@ ~ () $ pip install maggy==1.0.0rc0
Collecting maggy==1.0.0rc0
  Downloading maggy-1.0.0rc0-py3-none-any.whl (154 kB)
     |████████████████████████████████| 154 kB 8.2 MB/s
Collecting scikit-optimize==0.7.4
  Using cached scikit_optimize-0.7.4-py2.py3-none-any.whl (80 kB)
Collecting numpy==1.19.2
  Using cached numpy-1.19.2-cp38-cp38-manylinux2010_x86_64.whl (14.5 MB)
Collecting statsmodels==0.11.0
  Using cached statsmodels-0.11.0-cp38-cp38-manylinux1_x86_64.whl (8.7 MB)
Collecting scipy==1.4.1
  Using cached scipy-1.4.1-cp38-cp38-manylinux1_x86_64.whl (26.0 MB)
Collecting scikit-learn>=0.19.1
  Downloading scikit_learn-0.24.2-cp38-cp38-manylinux2010_x86_64.whl (24.9 MB)
     |████████████████████████████████| 24.9 MB 13.3 MB/s
Collecting pyaml>=16.9
  Using cached pyaml-20.4.0-py2.py3-none-any.whl (17 kB)
Collecting joblib>=0.11
  Using cached joblib-1.0.1-py3-none-any.whl (303 kB)
Collecting patsy>=0.5
  Using cached patsy-0.5.1-py2.py3-none-any.whl (231 kB)
Collecting pandas>=0.21
  Downloading pandas-1.2.4-cp38-cp38-manylinux1_x86_64.whl (9.7 MB)
     |████████████████████████████████| 9.7 MB 8.5 MB/s
Collecting python-dateutil>=2.7.3
  Using cached python_dateutil-2.8.1-py2.py3-none-any.whl (227 kB)
Collecting pytz>=2017.3
  Using cached pytz-2021.1-py2.py3-none-any.whl (510 kB)
Collecting six
  Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting PyYAML
  Using cached PyYAML-5.4.1-cp38-cp38-manylinux1_x86_64.whl (662 kB)
Collecting threadpoolctl>=2.0.0
  Using cached threadpoolctl-2.1.0-py3-none-any.whl (12 kB)
Installing collected packages: six, numpy, threadpoolctl, scipy, PyYAML, pytz, python-dateutil, joblib, scikit-learn, pyaml, patsy, pandas, statsmodels, scikit-optimize, maggy
Successfully installed PyYAML-5.4.1 joblib-1.0.1 maggy-1.0.0rc0 numpy-1.19.2 pandas-1.2.4 patsy-0.5.1 pyaml-20.4.0 python-dateutil-2.8.1 pytz-2021.1 scikit-learn-0.24.2 scikit-optimize-0.7.4 scipy-1.4.1 six-1.16.0 statsmodels-0.11.0 threadpoolctl-2.1.0


onFailure no being called

Hi there,
I'm having the problem that when the webservice responds with a 401 error and returns unknown content, neither onSuccess nor onFailure gets called. Shouldn't either of the two always be called? Or am I missing something in my code?
Please note that onSuccess gets called when the webserver responds with a 200 status code. An both onStart and onFinish also get called in any case, failure or not. So the general setup seems to be fine.
        httpClient.get(myUrl, null, new JsonHttpResponseHandler() {
            @Override
            public void onSuccess(JSONObject response) {
                Log.i(response.toString());
            }

            @Override
            public void onFailure ( Throwable e, JSONObject errorResponse ) {
                String msg = "Object *" + e.toString() + "*" + errorResponse.toString();
                Log.i("onFailure: " + msg);
            }

            @Override
            public void onFailure ( Throwable e, JSONArray errorResponse ) {
                String msg = "Array *" + e.toString() + "*" + errorResponse.toString();
                Log.i("onFailure: " + msg);
            }

            @Override
            public void onFailure ( Throwable e, String errorResponse ) {
                String msg = "String *" + e.toString() + "*" + errorResponse;
                Log.i("onFailure: " + msg);
            }

            @Override
            public void onFinish() {
                Log.i("onFinish");
                }
            }
            @Override
            public void onStart() {
                Log.i("onStart");
            }
        });

Thanks for any pointers or ideas!

Encountered the same issue today. All callback method works except onFailure.
Finally, I had to go for AsyncHttpResponseHandler as a workaround.

I have solved the problem by overriding JsonHttpResponseHandler.onFailure(int statusCode, Header[] headers, String responseString, Throwable throwable) in the response handler. Please see JsonHttpResponseHandler.onFailure(final int statusCode, final Header[] headers, final byte[] responseBytes, final Throwable throwable) method.

This issue still exists. This is really not well designed....
For whomever that is still looking for an work around
You need to override the other two onFailure method to catch it. One of the three onFailure will get fired but by default, you are provided the one that is not fired during no internet connections. So do this
@Override
public void onFailure(int statusCode, Header[] headers, Throwable throwable, JSONArray errorResponse) {
	your codd
}

@Override
public void onFailure(int statusCode, Header[] headers, Throwable throwable, JSONObject errorResponse) {
	//your code
}

Personally, I like to handle all failures in one call back. So use this trick to wire the other two failures to the default onFailure method
@Override
public void onFailure(int statusCode, Header[] headers, Throwable throwable, JSONArray errorResponse) {
	onFailure(statusCode, headers, throwable.getLocalizedMessage(), throwable);
}

@Override
public void onFailure(int statusCode, Header[] headers, Throwable throwable, JSONObject errorResponse) {
	onFailure(statusCode, headers, throwable.getLocalizedMessage(), throwable);
}


dio.interceptors.add show error,dio duplicated defined ,why?

I've seen it, too. Have you solved it？


Sign in - Update copy for magic link page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

In sign in page, enter an email that does not have a Expensify account.
Click continue

Expected Result:
Message should be something like "Please check your email for the email we just sent you" and not mention to enter the email or phone number again.
Actual Result:
The text says "Welcome to the New Expensify! Enter your phone number or email to continue."
Workaround:
None needed, content issue.
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.0.98-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @mananjadhav
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1631363898189100
View all open jobs on GitHub

Triggered auto assignment to @MariaHCD (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

I had proposed a solution for this in Slack. Will need help with Spanish translation.
https://expensify.slack.com/archives/C01GTK53T8Q/p1631364912189600?thread_ts=1631363898.189100&cid=C01GTK53T8Q

Triggered auto assignment to @dylanexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

On this now!

Job posted! 🎉
Internal: https://www.upwork.com/ab/applicants/1437771593050058752/job-details
External: https://www.upwork.com/jobs/~01531041eaf457ae01

Triggered auto assignment to @thienlnam (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@mananjadhav Could you please copy/paste the proposal into this Github issue?

@mananjadhav Thanks! Your proposal looks good. 🟢 Please apply to the upwork job and I'll work on getting you the spanish translations

Done.

@dylanexpensify Could you please hire @mananjadhav in Upwork and then assign him to the job when that is complete?

As for the Spanish translation:
Resend the link to login to your Expensify Account -> Reenviar el enlace para acceder a tu cuenta de Expensify

@kadiealexander Is this PR merge also delayed with the n6 release?

on hold

@dylanexpensify just a heads up - I underpaid @mananjadhav for https://github.com/Expensify/App/issues/4544 by mistake and as that contract ended in Upwork, I'm tapping his owed amount onto this issue as a bonus. You don't need to action anything here - I'm just using the "pay bonus" function so I don't have to create another Upwork job. Thanks

Sounds good @laurenreidexpensify! Thanks for the heads up!

Please refer to this post for updated information on the n6 hold, we've raised the bonus to $250 for all issues where a PR is created before the N6 hold is lifted.

Discussing internally on how to handle this as the changes are no longer applicable


I just just changed my column to row with the same code and it throws an error

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

@TheMadbhai can you please add minimal code to reproduce the issue
followed by the output of flutter doctor by running
flutter doctor -v

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Respect Rule.valueOfField()

valueOfField takes a path and it returns a reference to a value that the validations should be able to handle. We could handle this.

I don't think this is possible. If field A is using valueOfField(B), it would need the type of the overall object to be able to find field B. But to have that type, we'd need the type of field A... which is what we're defining. type of field A => valueOfField(B) => type of object => type of field A. Without some external manual typing, I don't see how we accomplish this.
There's still work to do. Field references (the return type of valueOfField()) should essentially have no effect on the type, not break the whole thing as it currently does.


Domain Controller template is broken on Zabbix 3.2

FYI, the Domain Controller template fails on import to Zabbix 3.2 (probably all 3.x versions) with the following:
Incorrect item value type "Numeric (unsigned)" provided for trigger function "str(OK)".
I am trying a few things to fix it, if I figure it out will post the solution.

Got all the items working for 3.2, pulling data from Server 2012 R2 hosts:
new-ad-template.txt
May still need some tweaking as I'm kind of stabbing in the dark for some of these. Changed triggers for all the DCDiag script checks as well as the performance counter keys for NTLM and Kerberos authentication.
At least for me, it's working 100% now. Hope this helps someone.


Autocomplete options not always visible

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When opening Autocomplete options with little (or zero at all) space at the bottom of the page and multiple options already selected (which makes selected chips list huge), options opens outside of user view (at the top of the page)
Expected Behavior 🤔
Autocomplete options list is always visible right after open triggered.
Steps to Reproduce 🕹
https://codesandbox.io/s/material-demo-forked-w6j6o
Steps:

Try to open options list

Context 🔦
Make user not thinking where the options are.
Your Environment 🌎

Tech
Version

Material-UI core
v4.11.0

Material-UI  lab
v4.0.0-alpha.56

React
16.13.1

Browser
chrome 86

TypeScript
3.8.3

etc.

Related to #21661

Related to #19137. IMHO, the correct solution is to render smaller tags and give the autocomplete more space. I'm not aware of any alternative. I would be leaning toward "won't fix".


Add init tweaks

Coverage increased (+26.7%) to 76.667% when pulling 2cee7b68a3aa8b40e2e2156dfd59b1887189e955 on add-init-tweaks into c8375cd0383e58021c0b65054c0840b5bdfe0b6d on master.


Fa rework

Codecov Report

Merging #10 (8f0e9d7) into main (140e332) will decrease coverage by 0.39%.
The diff coverage is 0.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff            @@
##            main     #10      +/-   ##
========================================
- Coverage   0.38%   0.00%   -0.39%
========================================
  Files          6       6
  Lines        262     262
========================================
- Hits           1       0       -1
- Misses       261     262       +1

Files Changed
Coverage Δ

src/ConvergenceCriteria.jl
0.00% <0.00%> (ø)

src/FEBuffer.jl
0.00% <0.00%> (ø)

src/FEDefinition.jl
0.00% <0.00%> (ø)

src/FerriteProblems.jl
0.00% <0.00%> (-1.93%)
:arrow_down:

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


Add support for Xamarin.Forms 4.6

Xamarin.Forms 4.6 has been released yesterday.
It contains 2 new controls: Expander and RadioButton as well as support for AppTheme (Light and Dark).
I added samples for those 3 in the AllControls sample.

/azp run full build

Not sure how AppTheme is supposed to work.
Tested it on both iOS and Android, and it doesn't work.
iOS never triggers Application.Current.RequestedThemeChanged when the phone theme changed.
Android recreates the activity hosting XF/Fabulous, thus resetting the state of the app to 0.

Apologies for replying to an old issue but it came up in my search. I'm currently trying to figure out how to get light/dark themes working with my full Elmish style Fabulous app (multi-page, somewhat following the model of the FabulousContacts example app). I've managed to get the themes sorted out, mainly by the F#-coded styling approach, plus some native styling that I needed to do in the Android project (via values and values-night, etc). The F# code is simple, for example:
module Style =
    let isDarkTheme = Application.Current.RequestedTheme = OSAppTheme.Dark

    let TabBackgroundColor = if isDarkTheme then Color.FromHex("#2d2d30") else Color.FromHex("#f6f6f6")
    let TabUnselectedColor = if isDarkTheme then Color.FromHex("#d0d0d0") else Color.FromHex("#949594")

And these values are used within the various view functions to set colours on elements.
The themes are working, except that I can't apply them at runtime, e.g. if the theme changes automatically due to time of day or if the user manually changes the theme while the app is still running. The theme is only set when the app starts. I was hoping to use the Application.Current.RequestedThemeChanged event to dispatch a message (in conjunction with the approach discussed under Triggering Commands from External Events) as I assumed that I would need to somehow trigger an update of the pages in the app for the F#-coded styling approach to reapply the different colours to the view elements. But as @TimLariviere mentions here, the Application.Current.RequestedThemeChanged event does not seem to fire.
If anyone could give any info or examples on how they have managed dynamically applying light/dark themes at runtime for Fabulous, that would be much appreciated.


Adding a base directory specification feature to runners

Hi there,
Thanks to this, i conveniently configured github actions. 🙏🏻
I have a question regarding the runner directory. Is it possible to specify a custom directory for the runners instead of using the default /home directory?
Any information or guidance on this matter would be greatly appreciated.
TY

Hi,
Thank you for your praise.
Currently the runner will be installed under $HOME/runner/ of each runner-dedicated Linux user to minimize the Linux permission issues. And the "Linux user to runner 1-1 mapping" was designed because we need to not only isolate different runners' building environment (such as caches under ~/.some-dir/), but also to start the runner as an user level systemd service.
I'm not sure if you encountered some storage limit of the system-disk, could you please try mount the data-disk as /home?

I wanted to manage it in an external storage at first, but after using it for a few days, I think it's okay since it doesn't bother me.

I was going to ask same thing and also thank you for this tool.
In my use case, our standard machine deployment has all extra storage in /opt, so having a base directory of /opt would be ... "optimal" :)
so the ask would be to change
../multi-runners/mr.bash:        && run::log sudo useradd -m -s /bin/bash -G 'runners,docker' "$user" >&2 || return $?

to
../multi-runners/mr.bash:        && run::log sudo useradd -d "$base"/"$user" -m -s /bin/bash -G 'runners,docker' "$user" >&2 || return $?

Where $base defaults to /home, but could be overridden on the mr.bash command line.

I've made a PR
https://github.com/vbem/multi-runners/pull/15


Add Local Regression Tests topic

fix #218
Most of the introductory stuff for Regression was already included in the Introduction to testing, and Test Matrix sections. Added a single page on local regression tests.

There're some problems with this part:

The link is an abolute one (http://www.boost.org/development/tests/master/developer/summary.html) and points to a page in the old website that will be unavailable after migration.
Additionally, the linked page is just one of the four pages collectively comprising the dashboard:

Develop branch: Summary, Unresolved Issues
Master branch: Summary, Unresolved Issues

So, we need to replace this single link with four links as described above, probably using a layout similar to this:

(The "Developers" header may be changed to something more pertinent such as "Results"). Now, the location of these four links in the new backend are:

https://regression.boost.io/develop/developer/summary.html
https://regression.boost.io/develop/developer/issues.html
https://regression.boost.io/master/developer/summary.html
https://regression.boost.io/master/developer/issues.html

These, again, are absolute links, and boost.io is not the final domain. We can include them in a couple of ways:

As

https://regression.boost.org/develop/developer/summary.html
https://regression.boost.org/develop/developer/issues.html
https://regression.boost.org/master/developer/summary.html
https://regression.boost.org/master/developer/issues.html
This will work once we migrate to boost.io, but will 404 in the meantime.

Via relative URLs redirected to the proper regression.*/xx absolute URLs

@kennethreitz, @sdarwin which option do you think is best? Or maybe there's a better solution I haven't thought of.
Thank you,

Probably the right approach here is to use the four links that work for
now, merge the PR, then file a reasonably high priority issue to change to
the four new links when the migration is done and tested?
By doing this the information gets out there and there is no pressure to
rush the migration if or when issues arise?

Peter T

On Sat, Apr 27, 2024 at 2:38 AM joaquintides @.***>
wrote:

There're some problems with this part:
imagen.png (view on web)
https://github.com/boostorg/website-v2-docs/assets/3283164/1029162a-ed18-440f-930d-d2e5ae68cac8

The link is an abolute one (
http://www.boost.org/development/tests/master/developer/summary.html)
and points to a page in the old website that will be unavailable after
migration.
Additionally, the linked page is just one of the four pages
collectively comprising the dashboard:

Develop branch: Summary
https://www.boost.org/development/tests/develop/developer/summary.html,
Unresolved Issues
https://www.boost.org/development/tests/develop/developer/issues.html
Master branch: Summary
https://www.boost.org/development/tests/master/developer/summary.html,
Unresolved Issues
https://www.boost.org/development/tests/master/developer/issues.html

So, we need to replace this single link with four links as described
above, probably using a layout similar to this:
imagen.png (view on web)
https://github.com/boostorg/website-v2-docs/assets/3283164/ed6419e1-5881-4748-9cb0-5abb5e39aa77
(The "Developers" header may be changed to something more pertinent such
as "Results"). Now, the location of these four links in the new backend are:

https://regression.boost.io/develop/developer/summary.html
https://regression.boost.io/develop/developer/issues.html
https://regression.boost.io/master/developer/summary.html
https://regression.boost.io/master/developer/issues.html

These, again, are absolute links, and boost.io is not the final domain.
We can include them in a couple of ways:

As

https://regression.boost.org/develop/developer/summary.html
https://regression.boost.org/develop/developer/issues.html
https://regression.boost.org/master/developer/summary.html
https://regression.boost.org/master/developer/issues.html
This will work once we migrate to boost.io, but will 404 in the
meantime.

Via relative URLs redirected to the proper regression.*/xx absolute
URLs

@kennethreitz https://github.com/kennethreitz, @sdarwin
https://github.com/sdarwin which option do you think is best? Or maybe
there's a better solution I haven't thought of.
Thank you,
—
Reply to this email directly, view it on GitHub
https://github.com/boostorg/website-v2-docs/pull/221#issuecomment-2080432592,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEIBS2JVIXS3TWW6WRCCLJLY7NWZVAVCNFSM6AAAAABGXQNRNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGQZTENJZGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi Peter, yes, let's do as you propose. Other solutions are probably too complicated for what's esentially a one-time event (the migration).

@joaquintides OK - done!

Merged, thank you!


NavigationRailDestination without hover

Is it possible to remove NavigationRailDestination holder like in the screenshot?

I want to help, but don't really seem to understand.
Can you please show us 'what happens' VerSus 'what you expect/want to achieve'?
Thanks..

I want to help, but don't really seem to understand. Can you please show us 'what happens' VerSus 'what you expect/want to achieve'? Thanks..

I mean remove it:

I don't think it's possible, but you can implement your own navigation rail using other Flet primitives like container, text, buttons.


Include the DOI of the published article in the metadata blob

If a user enters a DOI during submission, it ought to be captured in the metadata blob.  Prior to CMF implementation, DOI was captured, and some agents may expect it to be there.
This is the case with respect to the NIH package provider: it will include the article DOI in package metadata when preparing and depositing a package to NIHMS.
For reference, the DOI is documented in the global schema.
If we opt not to capture the DOI, we should discuss the rationale and document it here.

Current UI behavior will trim Crossref data to only those fields that are directly defined by schemas from the schema service. Since not all global properties may appear in these schemas, some global properties such as DOI are removed from the blob.
As a short-term fix, we can modify the UI behavior to include all global properties

Ember impl note:
services/metadata-schema#getFields is used to trim Crossref data. There are more fields that appear in the allOf validation rule set that come from the global schema.

I currently see two possible workarounds for this:

Inspect the schemas we get from the schema service. The schemas include a reference to the global schema as a validation requirement, with the global schema embedded in the schema's allOf field. The properties can be used when deciding which Crossref fields to keep. This option will "just work" in other environments/instances, however it is not guaranteed that any set of schema used during a submission will include a "global" schema in their validation rules, as described here
Due to a recent change that added $schema to the metadata blob, the Ember app is aware of the global schema in it's configuration. We can explicitly load the global schema and use it to determine which Crossref fields to keep. This approach guarantees that all "global" fields are included without relying on the fields to be present in validation rules of other schema, but requires that Ember have knowledge of the instance's "global" schema - for example, a pilot instance would need to know the correct global schema.

We need to define precisely how crossref data should be mapped to the metadata blob and how that is influenced by the schema service.

but requires that Ember have knowledge of the instance's "global" schema - for example, a pilot instance would need to know the correct global schema

@jabrah can you elaborate on this?  What do you mean by "know the correct global schema" or "knowledge of the instance's 'global' schema"?  Do you mean that the metadata blob must carry $schema and its value must be a schema that contains the properties to be included in the blob?


Replace TextField with dropdown in signup for college details

Is your feature request related to a problem? Please describe.
To reduce the ambiguity of college entries in the database. Only registered colleges should appear for the user to select when signing up in the app.
Describe the solution you'd like
Replace TextField with dropdown in signup for college details so that the user can select the details from there.
The registered colleges will have the following database.

Additional context
Open to suggestions. Anyone willing to work on this issue under GSSOC21 may comment below and I'll assign it to you. If you need more explanation / guidance, do tell.

The data for the drop-down should be fetched from Firebase?

The data for the drop-down should be fetched from Firebase?

Yes, you can use a StreamBuilder or FutureBuilder

I can try my hand at this, can I please?

I can try my hand at this, can I please?

Yes sure, go ahead @D-Ajay-Kumar ! I'll assign this to you.

Where can i find the google services file?

Its already in the repo. https://github.com/avinashkranjan/Friday/blob/master/android/app/google-services.json

yup found it

The stream/future builder will wrap the whole form and till the data loads I should a circular progress indicator right?

The stream/future builder will wrap the whole form and till the data loads I should a circular progress indicator right?

Yes.

Okay thank you very much.

How do these look?

Done. Please check the code :)

Done. Please check the code :)

Good work bro

Good work bro

Thanks man!


Fixes to work correctly with Windows

In Windows the CTRL-CMD-P does not work: added Windows specific keymap CTRL-ALT-P
The path substitution for the PNG filename was Mac/Linux specific. Replaced hard coded path delimiter (/) with path.sep

Thx, sorry for the delay as I was on vacation.


[2013-03-14] Combine ConfigManifest and ClassManifest to reduce memory footprint

created by: @chillu (ischommer)
created at: 2013-03-14
original ticket: http://open.silverstripe.org/ticket/8320

Architecturally they should be separated, but pragmatically they can't because of a massive duplication: Each PHP file is read and tokenized twice (via token_get_all()). The file access is not a big deal due to opcode caches, but the tokenizing is causing a lot of overhead.
Just for comparison, an uncached homepage request in 3.0 used 28MB peak, in 3.1 uses 42MB peak (without any opcode caches). WIth a primed APC, that goes down to 35MB, but I'm really just interested in the maximum SS needs to get started. We recommend 48MB memory_limit in our docs, given those numbers above that no longer seems realistic.
Note: We could also include the same per-file modification time caches in ConfigManifest that are placed in ClassManifest, but that doesn't reduce the maximum memory footprint on cache priming.
Hamish/Sam: I haven't assigned a milestone to this for now. If we don't get around to it, we need to make an announcement on the increased memory requirements of 3.1 on the mailinglist and in the upgrading notes.

We've replaced classmanifest with a php-parser based soluton and configmanifest just uses reflection. I think we can close this ticket.


Please give me back my data!

Give me back the data of my 300k users app I lost without motive when migrating to Heroku. Waiting for a response.

I'm closing out this issue as it is not related to Parse Server. For migration assistance, please visit https://parse.com/help#report

If I would be Parse I wouldn't bother so much about responsiblity after discontinuing my services.
Is this how you treat lovely developers? With contract loopholes?
Please give my data back: there are 300k users waiting.
Thx

if you would explain what happened when you migrated to heroku, i may be able to help.
Was data lost when migrating away from parse? Did your database crash and lost all data?

Exactly, I was moving out from Parse, but the transfer process didn't go as expected. I followed everything step exactly but at the end I didn't had data neither in Heroku or in Parse.

Where did you setup your database? What do you mean by didn't go as expected? Did you abort it? Did it fail mid-way? The parse.com/help may be your best chance here as the team responsible for parse.com migrations is not responsible for parse-server.

I setup MongoDb on mLab (Heroku Addon).
Parse Migration was all green at the end, but most of the tables were missing. I didn't abort it, I waited until the Finalize button appeared and then clicked it.
ok for parse.com/help but I really need to solve this quickly.. do you have a forecast for this kind of problems?

Did you check the data consistency before hitting finalize? So not all the data is lost right?

The most important is lost unluckily, the Recipe table. Only some tables (not useful and only for tracking purposes) transferred. I can't even recover that table in the Parse dashboard... :|

On that point, like Hector said, there is nothing much I can do on this side.
So your recipe table was not missing at the time you migrated to mLab. Did you use the shared plan or a dedicated hosting?

No it was not missing. Shared plan for mLab.

So that's a problem for mLab, not Parse.
I know mLab provide daily backups on shared plans, you may wanna look with them and find a backup that contains your data.

But if this (much probably) a bug in the migration tool, are you really sure I shouldn't deserve some time of backup copy for my table? Really you don't have it? Even an old JSON would be ok..
Will check with mLab too..

You just told me that before hitting finalize, your Recipe table was properly imported in mLab.
Also, when you decide to migrate your database and hit finalize, the data is migrated to the new provider.
And I can't say if the table is still saved somewhere as I don't work for Parse. I'm just a contributor, trying to help.
In any case, given that your Recipe table was properly imported once to mlab, you should have a daily snapshot available from them.

@thestubborndev I closed out this issue specifically because the Parse Server repository is not the right place to discuss Parse.com data migrations, as this repository is managed by a community of collaborators.
The Parse team has provided some additional information in the ticket you opened earlier today through the Parse.com Help page: https://developers.facebook.com/bugs/608100202693122/


Add support for procs and method calls in inclusion validation dropdown resolution

Add support for a few variations of inclusion constraints.
The motivating factor behind this is to be able to resolve to a list of classes that can only be resolved at runtime.
For example, this is not stable, it depends in which order the classes are loaded:
validates :model, inclusion: { in: ActiveRecord::Base.descendants.map(&:name) }

It needs a lambda:
validates :model, inclusion: { in: ->() { ActiveRecord::Base.descendants.map(&:name) } }

However, stateful lambda are prohibited, because they depend on the task instance:
validates :model, inclusion: { in: ->() { |task| task.some_method } }

While at it, this PR also adds support for bounded enumerables:
validates :timeout, inclusion: { in: (0..30).step(5) }

See the update test and comments for a full explanation.

So what are stateful constraints by the way? Lambdas that take the record? Also in: :some_method? We do have the object handy (although it's only initialized with its defaults obviously).
I guess they raise more issues, but I wonder why we wouldn't support that as well at this point.

Yeah, validations are designed to run within the context of the object with the values at the right place, so adding that limitation seems fair to me.
If someone wants to call a method, they can do so in a proc:
validates :model, inclusion: { in: ->() { MyClass.allowed_model_values } }

Do we need to deal with potential exceptions raised from the lambda? Before we were just getting a value from the task, now we're calling code, so I guess there's more potential for failure here.

Indeed, but if the code is throwing an exception, I think it's perfectly reasonable to let it raise unhandled

We should also document the dropdown feature (and the scope of the support for views with this PR) in the README as well. I guess that could be an indicator that the feature is too complex if we need too many words to explain it. Before: "if you have an inclusion validator on your parameter, if the allowed values is a Array, it will be used to build a dropdown". Now we'll need to add some more words.

Yeah, I can do that once we settle 👍🏼

Also just realized that if there's an if: or unless: on a validation, we're not respecting that (and ignoring the validation altogether), and always forcing the values to be in the allowed list with the dropdown, when the validation might not apply.

That's a valid concern, but it's also already true today. I don't think this PR makes the status quo any different.

Perhaps I picked up something?

It's reproducible on main so not related to the PR

@etiennebarrie fixed to support arity-one procs / lambdas appropriately, and I also tweaked this to support callable objects, since that is supported in the Validations::ResolveValue module you linked.


Passing input to LSTM layer in a network twice

I am recently working on a problem where I have LSTM layer in network. After LSTM, DNN layer is placed. I want to pass the input twice through the LSTM layer, once just to generate prior without any output. During second pass of the same input to LSTM, now LSTM shall generate the output sequence. This output after two passes over same LSTM, will be sent to the DNN layer. As keras provides so much less flexibility in sequential model and LSTM, I am not getting how can I handle this situation.
Thanks

Make your LSTM layers stateful (stateful=True). Then, pass your data through the network twice (e. g. with model.train_on_batch(...); the LSTM layers will keep their memory in between) and use only the output of the second pass. Before you feed in the next input, run model.reset_states() to reset the memory of the LSTM layers.
More on statefulness here, here and in #98 (I recommend scanning through that issue as the official docs are rather imprecise).

Just came to my mind: During training, you should use model.predict_on_batch(...) for the first pass and model.train_on_batch(...) only for the second pass. This way, the first pass initializes your LSTM memory without changing the weights/biases of the network.

Thanks @jrieke  ... I will try both these approaches and will get back to you ..

@jrieke  the problem that I have with this approach is .. I have DNN layer at the end of LSTM. During the first pass of input I want the LSTM layer to just maintain the memory. No training. So the weights during first pass shall not change. When the second pass is made now the output of LSTM layer shall be propagated to DNN and backpropagation  is carried out.
Thanks

@rajendramishra18 If you use predict_on_batch for the first pass, it doesn't change the weights (i.e. it doesn't train the network, but initializes the LSTM state in just the same way as the train_on_batch method does).

@jrieke  OK thanks I got it ... it will work .. Thanks


Improve the widget generation wizard to support Pubsub

Description:
Currently, widget generation wizard allows users to generate widgets with only basic functionalities. But we need to improve the widget generation wizard to generate widgets with some rich capabilities such as pubsub configurations, query templating and etc.
As the improvements for the widget generation wizard, we will provide support for collecting data based on external inputs (eg:- timestamps, time ranges) and publishing data to outside based on the user events (eg:- onClick) in widgets.

Fixed with https://github.com/wso2/carbon-dashboards/pull/903


update k8s versions to 1.10.11 1.11.5 and 1.12.3

Signed-off-by: André Martins<EMAIL_ADDRESS>

This change is

test-me-please

Coverage decreased (-0.2%) to 43.302% when pulling 545e0f48b63ed11de3081a7dd800e04e1e7f46d2 on pr/update-k8s-versions into a78b5e18336bd388a7f93d10c855045031a8401c on master.

test-me-please

test-me-please


Add string methods for classes for easier printing

Add the str() and repr() methods to the Device classes to make it easier to print and show these objects.
Example:
def __str__(self):
    object_type = str(type(self))
    return object_type + ": This is a Contact Device str."

def __repr__(self):
    object_type = str(type(self))
    return object_type + ": This is a Contact Device repr."

This has been resolved in commit fc254e2083608ebc348e8749e6b9df00fbba933b.

This has been resolved in commit fc254e2083608ebc348e8749e6b9df00fbba933b.


Add idempotent retries of updating the replica queue in ZooKeeper

Hello,
Looking to this PR doesn't seems 100 % correct. Now we moved the ReplicationMergeTree to not use any longer dedicated threads per table and instead a pool of threads.
And in this PR if I understand correctly it's inserted an infinite loop:
for (size_t num_tries = 0; ; ++num_tries)

Which blocks the thread until zookeper operation succeeds. I'm wonder if instead doing this you can schedule this operation in pool for later execution until completes
Silviu

@silviucpp yes you are right... The code will become much more convoluted though – we would need to save the fact that we must retry the ZooKeeper operation on the next iteration somewhere in the object state and then have two branches of code based on whether we should retry or not.
In fact the problem is present in a milder form for all blocking operations. E.g. if a thread is stuck waiting for a response from ZooKeeper (that could be tens of seconds), it doesn't do any useful work and just occupies a slot in the thread pool. That is why I am not a fan of using a thread pool for the replication tasks. It would work great if we converted all operations to async style, but that's a lot of work.

@ztlpn what we need to convert to async is the zookeeper interaction, from what I see it's the only one that can block the threads for long time

Probably the simpliest solution is to mark queue as dirty and re-initialize it in next iteration.

Problem https://github.com/yandex/ClickHouse/issues/1546 seems not fixed by this patch

@alexey-milovidov good idea, will do.
@silviucpp yes, it is another bug. Still, it is a good thing that you have reviewed this patch :)


Update starter template to reflect changes in 1.0

This PR updates the documentation to reflect changes in the 1.0 django-councilmatic release. Substantive changes include:

Add stronger guidance on populating the database
Add light documentation for containerizing Solr
Remove references to the OCD API
Reference Haystack

Questions:

Should I add a blurb on proxy models? If so, I'm inclined to copy/paste the Approach section (with light edits) from this comment: https://github.com/datamade/django-councilmatic/pull/240#issuecomment-503221198

I think that I wouldn't add blurb on proxy models here. I could see value of add the "Approach" section to a README or other doc file on django-councilmatic and link to that from here.
It's a little out of scope, but I would also recommend removing all guidance on SOLR options except for the docker option.

Added info on approach to django-councilmatic in https://github.com/datamade/django-councilmatic/pull/251, made the requested changes here!

we'll continue to host these changes on the 1.0 branch, consistent with our development stream over in django-councilmatic. as that's the current working branch, i'll "merge" this by closing this pr.


Schema/database changes now restart the GraphQL server.

Closes #13.

This almost works, except for that the app server never gets shut down between schema changes. Does anyone want to commandeer this PR and finish it up? @flipside?

@steveluscher I'm swamped for the next month at least

Closed by #83.


Adding FastAPI tags to metrics route

Is there a way to customize where the metrics route is tagged in the generated FastAPI docs?  I'm using tags to group routes, but my instrumented routes ('/metrics') always ends up in "default".

Hey @chisaipete, this is currently not possible and I must say that the tags feature is new to me. It should be pretty easy to add (just another parameter 😄), but in the mean time you can skip the expose() and add the endpoint yourself. Here is how it could look like:
from prometheus_client import REGISTRY, CONTENT_TYPE_LATEST
from starlette.requests import Request  # or import it from FastAPI
from starlette.responses import Response  # or import it from FastAPI

@app.get("/metrics", tags=["whatever"])
def metrics(request: Request):
    resp = Response(content=generate_latest(REGISTRY))
    resp.headers["Content-Type"] = CONTENT_TYPE_LATEST
    return resp

I think I'll add support for tags over the next weekends when I find the time

Great! It's not a huge blocker right now, just an annoyance. Thanks for the workaround, looking forward to the enhancement!

That was fast.

Okay I added the passthrough of tags parameter to the expose() in version 5.6.0 here. Just 2 lines so I did not want to wait. I think I will refactor it to also pass through arbitrary args / kwargs (in addition to the hardcoded ones) once I have more time.
@Kludex, he caught me right before going to bed, so good timing

Oh wow! Let me confirm this is working.

Umm, I'm not sure this is out in PyPi yet, I tried to check for package updates but I'm still seeing 5.5.1
TypeError: expose() got an unexpected keyword argument 'tags'

Nevermind, that was a PyCharm weirdness, I was able to explicitly set the version to 5.6.0 and pull the new version.  Works great, thanks!


Python: Add change note for new taint-tracking configuration API.

Needs links to full documentation added.

Thanks for the change note. It'll be good to have something we can publish, if necessary, while you're finalizing the tutorial that will eventually be linked to from this note.


Questions about protobuf protocols

I'm implementing the missing protobuf protocols and i think that the documentation here  is incorrect as it should be:

oneof message {
SendToGroupMessage send_to_group_message = 1;
EventMessage event_message = 5;
JoinGroupMessage join_group_message = 6;
LeaveGroupMessage leave_group_message = 7;
SequenceAckMessage sequence_ack_message = 8;
}

Is also not clear to me what is the role of the WriteMessage override since it is never called.
Plan to contribute with a PR once implementation will be completed.

Got confirmed that WriteMessage is not used at the moment, so just the documentation has to be fixed now.


Spec file for config.json or YAML in prompt functions

Hi everybody,
I've been looking for a specification file to create a prompt function (either YAML or not) but I can't find it.
For now, I'm copying and pasting from the examples and it works fine, but shouldn't there be documentation on what I can and can't write in the YAML file?
For example, If I'm using Azure DevOps pipelines I can use the specification to build it https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/?view=azure-pipelines and event I can validate it
Is there any similar specification or is it planned to have it in the short-term?
Maybe I'm missing something, if so I'm sorry.

Hi @panicoenlaxbox
thanks for creating this issue. We are updating our documentation in this area and I will make sure we include a YAML schema reference.


Any reason not to move to Java 8?

Java 6 is roughly 10 years old.
Performance in general has been improved in later versions of the JDK.
Anything in particular that keeps you from upgrading?

I think its the man power.

Some of the reasons that keep me from upgrading:

Some of ta4j users are still running java 6.
Streams/lambdas/optionals are really nice to work with. But the added value is very low in our case (even in the indicators) since we don't have very complex pieces of code that would need to be more "readable".
Performance in general has been improved in Java 8. But lambdas (which are often used with streams) are performance killers by design (inner classes). For now I don't want to support their usage in the indicators.
Java 8 don't have any killer feature that would counterbalance those drawbacks.

But I agree: in general all my new projects run on Java 8.


Version 6.8 has a PHP requirement incompatible with your PHP version, PHP extensions and Composer version

Deployer version: 6.8
Deployment OS: windows
php 8.0.3
symfony 5.2
composer v2

When: composer require deployer/deployer ^6
Console message:
Package deployer/deployer at version 6.8 has a PHP requirement incompatible with your PHP version, PHP extensions and Composer version

Voici le trace:
PS C:\Users\SoS Consoles\Desktop\ouebsite> composer require deployer/deployer ^6.8 -vvv
Reading ./composer.json (C:\Users\SoS Consoles\Desktop\ouebsite\composer.json)
Loading config file C:/Users/SoS Consoles/AppData/Roaming/Composer/config.json
Loading config file ./composer.json (C:\Users\SoS Consoles\Desktop\ouebsite\composer.json)
Checked CA file C:\Users\SoS Consoles\AppData\Local\Temp\opeB9A6.tmp: valid
Executing command (C:\Users\SoS Consoles\Desktop\ouebsite): git branch -a --no-color --no-abbrev -v
Reading C:/Users/SoS Consoles/AppData/Roaming/Composer/composer.json (C:\Users\SoS Consoles\AppData\Roaming\Composer\composer.json)
Loading config file C:/Users/SoS Consoles/AppData/Roaming/Composer/config.json
Loading config file C:/Users/SoS Consoles/AppData/Roaming/Composer/composer.json (C:\Users\SoS Consoles\AppData\Roaming\Composer\composer.json)
Reading C:\Users\SoS Consoles\Desktop\ouebsite/vendor/composer/installed.json (C:\Users\SoS Consoles\Desktop\ouebsite\vendor\composer\installed.json)
Reading C:/Users/SoS Consoles/AppData/Roaming/Composer/vendor/composer/installed.json (C:\Users\SoS Consoles\AppData\Roaming\Composer\vendor\composer\installed.json)
Loading plugin PackageVersions\Installer
Loading plugin Symfony\Flex\Flex
Running 2.0.10 (2021-02-23 16:11:37) with PHP 8.0.3 on Windows NT / 10.0
Reading C:/Users/SoS Consoles/AppData/Local/Composer/repo/https---flex.symfony.com/aliases.json from cache
Downloading https://flex.symfony.com/aliases.json if modified
[200] https://flex.symfony.com/aliases.json
Writing C:/Users/SoS Consoles/AppData/Local/Composer/repo/https---flex.symfony.com/aliases.json into cache
Downloading https://repo.packagist.org/packages.json
[200] https://repo.packagist.org/packages.json
Writing C:/Users/SoS Consoles/AppData/Local/Composer/repo/https---repo.packagist.org/packages.json into cache
Reading C:/Users/SoS Consoles/AppData/Local/Composer/repo/https---repo.packagist.org/provider-deployer~deployer.json from cache
Downloading https://repo.packagist.org/p2/deployer/deployer.json if modified
Reading C:/Users/SoS Consoles/AppData/Local/Composer/repo/https---repo.packagist.org/provider-deployer~deployer~dev.json from cache
Downloading https://repo.packagist.org/p2/deployer/deployer~dev.json if modified
[304] https://repo.packagist.org/p2/deployer/deployer.json
[304] https://repo.packagist.org/p2/deployer/deployer~dev.json
Reading C:/Users/SoS Consoles/AppData/Local/Composer/repo/https---repo.packagist.org/provider-deployer~deployer.json from cache
Reading C:/Users/SoS Consoles/AppData/Local/Composer/repo/https---repo.packagist.org/provider-deployer~deployer~dev.json from cache

  [InvalidArgumentException]
  Package deployer/deployer at version 6.8 has a PHP requirement incompatible with your PHP version, PHP extensions and Composer version

Exception trace:
 () at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Command/InitCommand.php:749
 Composer\Command\InitCommand->findBestVersionAndNameForPackage() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Command/InitCommand.php:443
 Composer\Command\InitCommand->determineRequirements() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Command/RequireCommand.php:189
 Composer\Command\RequireCommand->execute() at C:\Users\SoS Consoles\Desktop\ouebsite\vendor\symfony\flex\src\Command\RequireCommand.php:54
 Symfony\Flex\Command\RequireCommand->execute() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/vendor/symfony/console/Command/Command.php:245
 Symfony\Component\Console\Command\Command->run() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/vendor/symfony/console/Application.php:835
 Symfony\Component\Console\Application->doRunCommand() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/vendor/symfony/console/Application.php:185
 Symfony\Component\Console\Application->doRun() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Console/Application.php:310
 Composer\Console\Application->doRun() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/vendor/symfony/console/Application.php:117
 Symfony\Component\Console\Application->run() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/src/Composer/Console/Application.php:122
 Composer\Console\Application->run() at phar://C:/ProgramData/ComposerSetup/bin/composer.phar/bin/composer:63
 require() at C:\ProgramData\ComposerSetup\bin\composer.phar:24

Resolved by require "deployer/deployer": "^7.0",


Complete writing tasks on overleaf

See TODO's in overleaf

[x] Abstract
[x] Introduction
[ ] Implementation overview
[ ] Comparison and interaction with other packages
[ ] Usage: elementary examples
[ ] Conclusion

Let's remove the conclusion: we do not have enough space for it. I'll tick the box in your checklist.