Unable to extract video url

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Unable to extract video url
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
yt-dlp.exe -vU https://www.instagram.com/reel/C3o_qFLPLN5/?utm_source=ig_web_copy_link
[debug] Command-line config: ['-vU', 'https://www.instagram.com/reel/C3o_qFLPLN5/?utm_source=ig_web_copy_link']
[debug] Encodings: locale cp936, fs utf-8, pref cp936, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [f10589e34] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.14393-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: none
[debug] Optional libraries: Cryptodome-3.19.1, brotli-1.1.0, certifi-2023.11.17, mutagen-1.47.0, requests-2.31.0, sqlite3-3.35.5, urllib3-2.1.0, websockets-12.0
[debug] Proxy map: {'http': 'http://<IP_ADDRESS>:7890', 'https': 'http://<IP_ADDRESS>:7890', 'ftp': 'http://<IP_ADDRESS>:7890'}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1798 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
ERROR: Unable to obtain version info (HTTP Error 403: rate limit exceeded); Please try again later or visit  https://github.com/yt-dlp/yt-dlp/releases/latest
[Instagram] Extracting URL: https://www.instagram.com/reel/C3o_qFLPLN5/?utm_source=ig_web_copy_link
[Instagram] C3o_qFLPLN5: Setting up session
[Instagram] C3o_qFLPLN5: Downloading JSON metadata
WARNING: [Instagram] unable to extract username; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
ERROR: [Instagram] C3o_qFLPLN5: Unable to extract video url; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "yt_dlp\extractor\common.py", line 718, in extract
  File "yt_dlp\extractor\instagram.py", line 487, in _real_extract
  File "yt_dlp\extractor\common.py", line 1409, in _og_search_video_url
  File "yt_dlp\extractor\common.py", line 1302, in _html_search_regex
  File "yt_dlp\extractor\common.py", line 1266, in _search_regex

Duplicate of #5967


Fix focus handling in multi-window applications

This took some time to debug - starting with an application that opens a popup window, wherein the user should be able to tab between items and press a key to select and close the popup.  Focus handling did not work at all in the popup window.
It turned out to be three separate issues:

window_handle.process_central_messages() would discard any messages for Views with a different root than its own, so they would never be processed, so focus requests would be discarded if the main window queried the queue first
ViewId attempted to cache the root view id, but would just cache the deepest parent found - so if you do something that generates an update message during construction of a tree of views, the cached value would not actually be the root view for the (not yet existing) window, and it would always return None from window_id() which relies on the (in this case bogus) root to map it to a window - so a call to request_focus() on a view too early would leave it with garbage as its root id, and no window handle would ever recognize and process it with the wrong root
Not quite as strictly a bug, but I can't imagine why it would be by design: FocusGained and FocusLost events caused by a call to ViewId.request_focus()would be delivered to listeners, but a View would never receive them via event_before_children() or event_after_children() - so this one had a workaround, but the workaround - a view attaching listeners to itself - would be much less readable than a straightforward implementation of one of the event handler methods

The fix for 3. I am the least sure about:

It is a bit ugly (swapping an EventCx for an UpdateCx to call unconditional_view_event() and then recreating the UpdateCx)
It is not clear if there are other kinds of events which have the same problem of non-delivery to the view itself
ViewId.apply_event() might be a cleaner place to implement it (though it would mean a bunch of calling back and forth between WindowHandle and ViewId which might be less than ideal)
I do not stop propagation of events if event_*_children() returns EventPropagation::Stop - as long is this is about focus events, I think it is probably harmful to be able to block propagation of focus events at all - window focus events more so, since it's unlikely that one view in a tree knows for sure that none of its siblings need to know about the window losing focus - but the same logic applies more weakly to plain view focus events - it's a recipe for hard-to-diagnose focus bugs.

Since I'm a proud member of the 1990's println school of debugging, UpdateMessage now implements Debug - needed it to prove that retained messages really were eventually processed, and it will probably be useful in the future.

Ignore the fact that Expose View::default_compute_layout appears to be one of the commits here - I did this on my branch containing that commit, but the commit that applies here reverts it.

Noted in comments, but will mention this here:  Retaining messages for unrecognized view roots has the potential to leak ViewIds if it there is any situation where it is normal to publish messages to a ViewId that either will never be owned by a window root, or which was but the window was closed before the message was encountered.  I.e. if you just called ViewId::new().request_focus() you would add a focus request permanently to CENTRAL_UPDATE_MESSAGES.
You know more about the common use-cases for Floem than I do - is this likely to be a problem?
If so, the simplest gc-like solution would just be to wrap messages in a struct that keeps a counter, increment the counter each time the same message is seen in the queue but not processed, and if it crosses some magic threshold number, don't put it back.  Any other solution would involve diffing collections and could get expensive, while if a message hangs out in the queue unprocessed for 100 events (or whatever number seems right), that's not going to have a big impract.
I think probably only implement a solution if we find out that it's actually a problem - fiddling with ViewIds and abandoning them is surely an application-level bug for the most part, although I could imagine a minor case or two where a view races with window removal (like, a click action dispatches request_focus but something else intercepts the click and decides to close the window).

Just in case you're wondering what on earth I'm doing that I'm running into these sorts of issues, here's a screen shot of a prototype of the DSP plugin UI:
(Actually plumbing this thing, given need to interoperate with pointers handed to me over FFI as if they were RwSignal is a remaining challenge)

Not quite as strictly a bug, but I can't imagine why it would be by design: FocusGained and FocusLost events caused by a call to ViewId.request_focus()would be delivered to listeners, but a View would never receive them via event_before_children() or event_after_children()

I think is a regression after the ECS pr

Not quite as strictly a bug, but I can't imagine why it would be by design: FocusGained and FocusLost events caused by a call to ViewId.request_focus()would be delivered to listeners, but a View would never receive them via event_before_children() or event_after_children()

I think is a regression after the ECS pr

Not familiar with that PR.  Is there a less invasive (or at least less clunky) fix, then?


cmd: update pending target arg descriptions

Extracted from https://github.com/iterative/dvc.org/pull/1384#issuecomment-657744994

Need to double check the following commands to see whether their targets support files/dirs ... repro, run, (un)freeze, remove, unprotect, update, and metrics/plots show

[ ] May imply core repo output string updates as well.

@jorgeorpinel I checked the above commands with file/dirs:

repro: currently being worked on in #1861
For  unfreeze, freeze, remove, when I tried them with files/dirs as targets this was the output:
ERROR: failed to freeze/remove `foobar`- "Stage `foobar` not found inside `dvc.yaml` file"
update: directories were working when  used with dvc update -R else same error as above
unprotect already excepts files/dirs
Similarly metrics show  also accepts metrics files as targets.
run: doesn't have targets argument

Does this require updating targets description in the update command or rather just the -R option desc.

Similarly metrics show also accepts metrics files as targets.
What about plots show? I'll look into that.

Does this require updating targets description in the update command

No, that cmd ref seems to have complete info about -R and dir targets already.
Looks like no major changes are needed...


[Reopening the issue #7158] : After the latest node upgrade on azure devops , lerna with an older version 3.22.1 fails to work. Its considering the latest version 6.5.1

Description
After the latest upgrade , the build pipelines are breaking with an older node version 10.16.3 and lerna 3.22.1 . The global packages have the latest version and refuse to get uninstalled and run on the specific version . This is causing the build pipeline to break as our code is incompatible with the new versions .
Request to provide a way to get this working to unblock us
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[X] Windows Server 2019
[ ] Windows Server 2022

Image version and build link

The Image where this does work

We have tried to use the setup-node to specify the version we need

Is it regression?
yes
Expected behavior
If we try to use the node 10.16.3 and lerna 3.22.1 version it should install and allow the system to use the specified version rather than imposing the latest version
Actual behavior
It always uses lerna 6.5.1 even if you try to uninstall and install the version you require i.e 3.22.1.
It is able to pick the node version supplied i.e '10.16.3'  but with lerna its not picking the version supplied i.e 3.22.1. Request you to help here
Request you to please not close the issue
Repro steps
Have a task to install node 10.16.3
Then add a task to install the lerna version 3.22.1 in monorepo directory
add another powershell task and try to execute the script 'lerna bootstrap --hoist" . It throws the below error

Find the dependencies that we installing

Hello @geetikaharlalka22, we will take a look.

Hello @sergei-pyshnoi  we have managed to get our build pipeline working . The issue here was the Lerna 6.5.1 expects a new syntax i.e npx lerna bootstrap --hoist . Which was throwing off the pipeline . On adding that it is now able to pick up the version specified in package.json and build our packages . Hence closing the issue .


2.0.25 and 2.0.26 introduced breaking regression

Hey guys,
Not sure what changed as I am on vacation, but looks like the last 2 patch changes introduced breaking changes. useDecimal is no longer a function.
 At least npm says You can no longer unpublish this version. Please deprecate it instead.
I have just contacted npm support to unpublish it for me. As a workaround you can (suggested) either upgrade to 3.0.0 which requires some work (probably an afternoon or more) or as a temporary workaround pin the version to 2.0.24 by replacing "geolib": "^2.0.0" in your package.json with "geolib": "2.0.24".

I think it would help to publish a new patch version (2.0.27) restoring the code to what it was in 2.0.24, to stop breakage for everyone installing with ^2.0.0 or similar.

Yes. That would be an alternative but I'd like to avoid that because that gives the impression that there was anything new/fixed/patched, which was not. I'll wait for 24 hours for npm to respond and (hopefully) unpublish the package or otherwise I will publish it as 2.0.27.

Thanks. I fixed the version to 2.0.24 for the time being until we have time to upgrade to ^3.0.0


Footer multilingual

Providing fix to have a multilingual footer
Fix #2
Test URLs:

Before: https://main--elco-aerotop-sg--hlxsites.hlx.page/
After: https://footer-multilingual--elco-aerotop-sg--hlxsites.hlx.page/

@cuzuco2 great that you copied the footers to the language folders in Sharepoint. You can remove the footer.docx in the root.

@cuzuco2 each PR should trigger the PageSpeed Insight check (google lighthouse scoring). This is achieved by editing the PR description to include the URLs to check. See https://github.com/hlxsites/elco-aerotop-sg/pull/1 for an example.

Hi I made the changes needed, could you approve them?

@cuzuco2 there seems to be a linting error - other wise great work!

@ekremney I got rid of the unnecessary import, please review


try this sync from SO

https://stackoverflow.com/a/57624824/10971650

/// TODO: reconverge the warp: https://stackoverflow.com/questions/54055195/activemask-vs-ballot-sync
/// Same as syncwarp
flushPipeline__ = !(__ballot_sync(ALL_LANES,active));

// the ugly part :(

fix-71-sync-try


Toast Warning Message if OpenSearch base map is used in conflicting regions

Description
Display warning message as toast notification if OpenSearch base map is used in conflicting regions.
https://user-images.githubusercontent.com/89161683/230252637-dca25d89-ff5f-4a61-82f3-4846fe604672.mov
Issues Resolved
https://github.com/opensearch-project/dashboards-maps/issues/251
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@704bb13). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 559afc4 differs from pull request most recent head 2032db9. Consider uploading reports for the commit 2032db9 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #382   +/-   ##
=======================================
  Coverage        ?   72.41%
=======================================
  Files           ?       25
  Lines           ?      638
  Branches        ?       98
=======================================
  Hits            ?      462
  Misses          ?      150
  Partials        ?       26

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

The dataURL also need verification before use. https://github.com/opensearch-project/dashboards-maps/blob/9e8fa3094e0d5be0945dcd610ce65ceceb2b9550/public/model/map/layer_operations.ts#L285
OSM layer generation steps: we firstly adds layer sources by requesting dataURL, then format OSM style by styleURL.


Stick the Docker images BASE_VERSION with major, minor and patch

Today, we are using only the major and the Debian version code name to stick our BASE_VERSION to build the template containers. This is wrong because the Toradex Debian packages and containers can publish new versions, with the same major, that may crash the flow.

Fixed from #79


Fixed seed variable concatenation pointer.

Description
This request fixes a minor issue with random number generation in CTR_DRBG_Resees.  The current implementation places the nonce value at the same starting location as the just retrieved seed value.  However, the seed size if still incremented, resulting in a section of zeroes the same length as the nonce at the end of the seed.
This fix just moves the nonce to where it is supposed to be in the concatenated seed.  I am not aware of a way to test this because the seed is immediately hashed with block_cipher_df before the call returns.
Status
READY
Backports needed?
NO - the feature with the problem is not present in any of the LTS branches.
Steps to test or reproduce
The self-test was updated to include nonce concatenation and expected results.

Hi @stroebeljc and thanks for your contribution! Indeed the current behaviour of the code does no seem intentional: overwriting entropy with other entropy does not make sense, and is in direct contradiction with the documentation of mbedtls_ctr_drbg_seed() which clearly states that the outputs of the two calls to f_entropy are concatenated. Thanks for spotting that!
I'm taking the liberty of editing the PR description to add that backports are not needed, as the feature is not present in any of the LTS branches.

I took a look at NIST DRBG test vectors to see if the CTR_CRBG algorithm is working as expected, but do not see alignment.  Whenever one of the Generate steps is executed, the results don't match up.  However, Instantiate and Reseed seem to match with the test vectors.  I'm not sure why this is happening.  Also, is there some testing that is run using NIST test vectors?  If so, where is that being performed?

Now the next step is for another team member to review, which is unlikely to happen this week as most of the team is on leave, but hopefully some time next week.


[UIFlow 1.0] [JP] UI-Label+

Translate the "Label+" in UIFlow 1.0 under the UI category into Japanese.

Translation is finished.


DRILL-7095: Expose table schema (TupleMetadata) to physical operator (EasySubScan)

Add system / session option store.table.use_schema_file to control if file schema can be used during query execution. False by default.
Added methods in StoragePlugin interface which allow to create Group Scan with provided table schema.
EasyGroupScan and EasySubScan now contain table schema, also they are able to serialize / deserialize it along with other scan properties.
DrillTable which is the main entry point for schema provisioning, has method to store schema and later uses it to create physical scan.
WorkspaceSchema when returning Drill table instance will get table schema from table root if available and if store.table.use_schema_file is set to true.

This PR is the next step for Schema Provisioning project which currently exposes schema only for text reader.
Jira: DRILL-7095.

@paul-rogers please review.

@paul-rogers you are right, I should not have modified plugin. I have updated the code and addressed other code review comments, please review.


Error on call floating.enable on AppLifecycleState.hidden

Hi.
When I try to call floating.enable() on lifecycleState == AppLifecycleState.hidden, it throws an exception "Activity must be resumed to enter picture-in-picture". It works almost well on AppLifecycleState.incative, but the issue is triggering floating.enable() even if Quick Settings panel is shown. Any ideas how to use it exactly on hidden?

Yea, I have the same problem.
When I show the Quick Settings Panel on my app runnig in Flutter 3.13 (and 3.22 too), the app changes to AppLifecycleState.incative, but my app is not changing to minimize.
And also, you only can call  floating.enable() when the app is in AppLifecycleState.incative or AppLifecycleState.resume.
This did not happen in version 3.10.6. But soon I will have to update.

Took a while, but will be available in 3.0.0 via .enable(AutoEnable());.

AutoEnable does avoid the problem between the 'inactive' state and showing Quick Settings for Android versions that support automatic mode (SDK 31+). Unfortunately, for Android versions that do not support this mode (SDK's less than 31), they will have to call the manual PiP function in the inactive state.
The problem is the new AppLifeCycle, since the 'inactive' state is activated when the Quick Settings are displayed on Android, changing to PiP mode without the action of 'minimizing' the app.
Just to finish, I understand that this is a change made by the Flutter team and not a Floating Plugin issue, but any information on this would be appreciated.

@FranciscoVenegas Do you found a solution?


Reflecting structured-buffer with a basic type error

Declaring this - StructuredBuffer<float4> gStructBuff; - causes Falcor to crash.
The culprit is the reflection, specifically doing this:
            const auto& pElementLayout = pSlangType->getElementTypeLayout();

pElementLayout is a basic type, but calling getScalarType() returns None and and rows/columns is 0.

Yeah, that sounds fishy.

Fixed by #731 and shipped in v0.11.14.


Update style-sherpa.md

I think there is a mistake in the docs. You’re writing about using tabs (which could be cool btw), but there is only vertical menu.

@rafibomb can you take a look at this?

This should target the develop branch.

Well, the description here on github says, that stuff about docs should go to master. Am I wrong?

Oh. Maybe I'm wrong. 😊

ping @rafibomb can you check this and merge if it seems right to you?

Yes - we used to use tabs but menu is right. Thanks for the PR!


Generated migration not completely compatible for rails 5+ apps

The migration that is generated inherits from ActiveRecord::Migration instead of ActiveRecord::Migration[5.2].
Here is the error I get:
$ rake db:migrate
rake aborted!
StandardError: An error has occurred, this and all later migrations canceled:

Directly inheriting from ActiveRecord::Migration is not supported. Please specify the Rails release the migration was written for:

  class DeviseAuthyAddToCredentials < ActiveRecord::Migration[4.2]

Easy fix on my end, but maybe the edge version should support rails 5.2?

Why is this issue closed? I am facing the same issue now.
Generated migrations use this syntax:
class DeviseAuthyAddToUsers < ActiveRecord::Migration

Which then trigger this error:
$ bin/rails db:migrate
rails aborted!
StandardError: An error has occurred, this and all later migrations canceled:

Directly inheriting from ActiveRecord::Migration is not supported. Please specif
y the Rails release the migration was written for:

Using rails <IP_ADDRESS>

@DannyBen I thought I'd fixed it. It should generate a migration with the correct version (based on this code). What version of devise-authy are you using?

Hmm... I am using the latest version 1.11.1.
Not sure what happened, but I definitely had to add the [6.0].

I'll open this back up and have a look through. Sorry this didn't work for you.

Found the problem! The initial fix for this checked that the Rails version was version 5. There has been an update to check that the version is 5 or greater, but that has not been released yet. Sorry!
Will work towards a release this week that brings this all up to date.

@DannyBen I have pushed the latest as version 2.0.0 (major bump because of updates to devise/rails dependencies, which probably don't affect your codebase these days). But this should work now.

Excellent! Thanks for the quick fix.


Workflow (offcial) plugin job doesn't keep parameters under actions

In case if somebody run into it, the new CloudBee's WorkFlow plugin
https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
It's job doesn't have parameterDefinitions under "actions", but rather under "property"
The rest of my regular jobs also have their property definitions under property
To handle has_params exception I have to do this in job.py
return any("parameterDefinitions" in a for a in (self._data["actions"] or self._data["property"]) if a)

Please submit this as a pull request.

Here are we go #347

There is another usage of parameterDefinitions in get_params
If you like, you can use this PR #348 to look into property as well

Merged. Thanks!


Remote rendering in Node

For the longest time I've wanted a more lightweight alternative to Electron for making internal devops UI apps.
I was excited when I discovered remote-dom because I was hoping I could render a React app in Node and stream the changes to a browser over a local websocket.
Is there any way to do that?  Unfortunately it seems impossible right now, because when I try to create a RemoteMutationObserver in Node to observe changes on the polyfilled DOM, it errors out because the base MutationObserver polyfill is just a stub.
The only alternative I can see right now would be to make remote wrappers for every one of my react components.  But that would defeat the purpose of what I'm trying to do.

Hey @jedwards1211, sorry I missed this issue being opened originally.
Yes, what you are describing is indeed possible. I prepared a little example demonstrating the basic setup here: https://github.com/lemonmade/24-07-03-remote-dom-websocket-test. The key is to import @remote-dom/core/polyfill in the Node server, which establishes a DOM polyfill that will automatically communicate its changes to the "host" environment (in this case, the browser on the other end of the websocket). This @remote-dom/core/polyfill import is an alternative to using RemoteMutationObserver, meant for cases like Node or Web Workers where there is no native DOM API. RemoteMutationObserver is only meant for cases where a real DOM exists (like an iframe element).
I am still not sure if it will do exactly what you are after, based on the rest of your message, but hopefully this gives you a reasonable spot to jump off from if you're interested in exploring more.

Awesome, thank you!  I'll check it out soon

@lemonmade Okay I tried wrapping the button in your example with a div (h('div', {}, h('ui-button', ...))) and as I figured, that doesn't work.
How possible do you think it would be, within the architecture of remote-dom, for me to implement a mode where I could render any normal DOM element in Node like
s, s, <button>s, etc, and the remote connection would render the corresponding element in the browser?
For what I'm trying to do it would be ideal not to have to define any custom elements, which does seem counter to remote-dom's goals.
It's probably not possible to do everything I'd hope for anyway though.  For example I'm assuming an infinite scroll component running in Node wouldn't have access to all the correct sizes and scroll positions computed by the browser to function correctly.


User Dashboard

Description

Created a user dashboard and tab panel that displays team members and and overview tabs
Created team members tab to map over mock data that would be returned from the Lambda Labs API
Connected the dashboard to the public Github API to pull in member images based on Github ID returned from Labs API

Fixes # (issue)
Type of change

[X] New feature (non-breaking change which adds functionality)
[X] This change requires a documentation update

Change Status

[X] Complete, but not tested (may need new tests)
[X] Incomplete/work-in-progress, PR is for discussion/feedback

Checklist

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[X] There are no merge conflicts

Github says to use the command line to merge into dev but the command line says I can't merge into dev without reviewers... I'm going to change all of the files to match dev to resolve any conflicts.

Files I will need to go back and edit once merged:

App.js
admin-dashboard/DashboardHome
admin-dashboard/Product
admin-dashboard/ProductList

No more conflicts! 😅


Create tag for every version update

Motivations
Git tags are used to keep track of changes.
Solution
Whenever a commit contains a version change and that version is greater than the published one, create a new tag.
If it is a workspace, the format of the tag should be package-vx.y.z.
The tag cannot be created in the release-plz update subcommand, so probably another subcommand is needed.

Probably this can be done by other projects, such as cargo-release or cargo-workspace.

I verified that tags can already be created with cargo-release. I documented this in README in #68

I reopen this because cargo-release and cargo-workspaces don't work well in CI. See See this and this :disappointed:
Probably it's better if we embed tag creation and publishing in release-plz.
The publishing process can be taken from cargo-workspaces (invoke it as a library?).


stream: Improve sinking stability further

I found other cases that resulted in unstable sinking behavior. Use a more principled formulation of sinking stability.

Test should be fixed now.


us-co-rifle

http://www.rifleco.org/index.aspx?nid=74

emailed<EMAIL_ADDRESS>

Hi Justin,
Thank you for your interest in the City of Rifle and our City data.  The parcel data with ownership information is officially managed by Garfield County. You can reach their offices in Glenwood Springs at<PHONE_NUMBER>.
Thank you,
Erica Gentry

called; they said parcels are open data - left voicemail with gis technician in assessors office

https://github.com/openaddresses/openaddresses/issues/4269will fix this


Columns for virtual attributes not selected

When a model has virtual attributes that depend on columns that aren't being selected the virtual attributes cause the resolver to return null. This can be "fixed" by adding return null here. Would it be possible to make _filterForSelects() optional?

Sorry, I have totally missed your pull requests. Thank you for them! I'll take a look at them as soon as I can. I'm on a vacation so it may take a day or five 😀

@koskimas (from here)

An option like selectFiltering sounds like a reasonable solution to this.

I just saw your edit now. I'll work on adding this to this pull.

From here:

I don't like the idea that users need to remember things like "if I use fragments, I need to call this arbitrary selectFiltering(false) method".

^ I totally agree. Is there a way that we could avoid a similar What?! for virtual attributes? Would it be better if the method was named like allowVirtualAttributes(true)? How can we communicate that there's a connection between selectFiltering and virtual attributes that reference columns? Wdyt about logging a warning if a model has virtual attributes and select filtering is not disabled?

@koskimas I think this is ready for review now.


Fix target in Photos Podfile

While going through your samples I found pod install not working for the Photos Sample due to a wrong target.

Thank you!


more unit testing of the token contract

need a lot more testing around the delegation functions, which were whipped up in a hurry

i would like to help with this, do you have any specific edge cases that you want to test?

i would like to help with this, do you have any specific edge cases in mind that you want to get tested?

Would love some help, don't have specific edge cases in mind but reviewing test coverage and filling in blanks would be helpful

okay, will go through the contract and think about what kind of tests could be added during the weekend.

This still up for grabs?

This still up for grabs? Am looking for Cairo tasks

Reviewing and testing the code always helpful, but closing this because it's too vague


SQL Agent: Job Steps Missing

SQL Operations Studio Version: 0.31.4
SQL Server Agent: 0.31.4
SQL Server : 13.0.5026.0
Steps to Reproduce:

1.Edit Job
Expected: Steps to be displayed
Actual: Only the General tab is filled in
Validated that the same user can see the steps in SSMS

Closing this as the same issue is being tracked here - https://github.com/Microsoft/sqlopsstudio/issues/2064

Not the same issue, that looks like a partial load this is no steps are displaying at all

@Tarig0 You're right, this feature is still in preview (should be indicated in next insider build), and thus isn't fully functional. Sorry about the confusion.


Feature logic generates nextPageToken at wrong layer

The features iterator in sequenceAnnotations.py:Gff3DbFeatureSet.getFeatures returns a (feature, nextPageToken) tuple ... it has the nextPageToken logic at the wrong layer of abstraction
Revise the tests in tests/unit/test_data_interface.py appropriately
Discovered in #1219

I wouldn't worry too much about fixing the layering --- the paging logic is being shoved down the stack in the SQL Alchemy refactor. If you see access patterns that are different to the rest of the API please flag them with comments and we'll hopefully make everything more uniform once the refactor has been completed.

@jeromekelleher You should consider using SQL alchemy for the sequence annotations backing, if you are not. I don't believe there's anything that wouldn't be done better that way, instead of our own sqlite backing.

Yeah, I agree @david4096. I think we should do this once we've changed over the main registry code to the SQL alchemy stuff in master. We can also think about storing other stuff (like variants) in a SQL DB.

I think this might need to be fixed sooner as I'm getting a 500 trying to page through results on 1kgenomes now.
[Mon Aug 01 13:48:28.729660 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112] Traceback (most recent call last):
[Mon Aug 01 13:48:28.729664 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]   File "/srv/ga4gh/ga4gh-protobuf/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
[Mon Aug 01 13:48:28.729667 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]     rv = self.dispatch_request()
[Mon Aug 01 13:48:28.729670 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]   File "/srv/ga4gh/ga4gh-protobuf/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
[Mon Aug 01 13:48:28.729673 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]     return self.view_functions[rule.endpoint](**req.view_args)
[Mon Aug 01 13:48:28.729675 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]   File "/srv/ga4gh/ga4gh-protobuf/lib/python2.7/site-packages/ga4gh-0.2.3.dev269+ngbb55ded-py2.7.egg/ga4gh/frontend.py", line 577, in searchFeatures
[Mon Aug 01 13:48:28.729678 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]     flask.request, app.backend.runSearchFeatures)
[Mon Aug 01 13:48:28.729681 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]   File "/srv/ga4gh/ga4gh-protobuf/lib/python2.7/site-packages/ga4gh-0.2.3.dev269+ngbb55ded-py2.7.egg/ga4gh/frontend.py", line 440, in handleFlaskPostRequest
[Mon Aug 01 13:48:28.729683 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]     return handleHttpPost(flaskRequest, endpoint)
[Mon Aug 01 13:48:28.729686 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]   File "/srv/ga4gh/ga4gh-protobuf/lib/python2.7/site-packages/ga4gh-0.2.3.dev269+ngbb55ded-py2.7.egg/ga4gh/frontend.py", line 315, in handleHttpPost
[Mon Aug 01 13:48:28.729688 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]     responseStr = endpoint(request.get_data())
[Mon Aug 01 13:48:28.729691 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]   File "/srv/ga4gh/ga4gh-protobuf/lib/python2.7/site-packages/ga4gh-0.2.3.dev269+ngbb55ded-py2.7.egg/ga4gh/backend.py", line 1076, in runSearchFeatures
[Mon Aug 01 13:48:28.729693 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]     self.featuresGenerator)
[Mon Aug 01 13:48:28.729696 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]   File "/srv/ga4gh/ga4gh-protobuf/lib/python2.7/site-packages/ga4gh-0.2.3.dev269+ngbb55ded-py2.7.egg/ga4gh/backend.py", line 776, in runSearchRequest
[Mon Aug 01 13:48:28.729698 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]     for obj, nextPageToken in objectGenerator(request):
[Mon Aug 01 13:48:28.729701 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]   File "/srv/ga4gh/ga4gh-protobuf/lib/python2.7/site-packages/ga4gh-0.2.3.dev269+ngbb55ded-py2.7.egg/ga4gh/datamodel/sequenceAnnotations.py", line 485, in getFeatures
[Mon Aug 01 13:48:28.729704 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112]     nextPageToken += 1
[Mon Aug 01 13:48:28.729707 2016] [:error] [pid 45174:tid<PHONE_NUMBER>30112] TypeError: unsupported operand type(s) for +=: 'NoneType' and 'int'```

Fixed in #1370


LimeTextExplainer - incorrect displaying "Text with highlighted words" for cyrillic letters

Hi,
I'm trying to use LimeTextExplainer for the text classification model, our data is russian text.
I'm using the following code to test lime functionality:
from lime.lime_text import LimeTextExplainer
explainer = LimeTextExplainer()
exp = explainer.explain_instance('test example', grid_search.predict_proba)
exp.show_in_notebook()

where grid_search is the best model which we find during grid search (in this example I used LogisticRegression model to probability prediction)
And it is working fine, in "Text with highlighted words" section we have highlighted text: "text example"
However if I try to use russian text for testing in the same code (just replace the first argument of explainer.explain_instance to 'тестовый пример'):
from lime.lime_text import LimeTextExplainer
explainer = LimeTextExplainer()
exp = explainer.explain_instance('тестовый пример', grid_search.predict_proba)
exp.show_in_notebook()

Then in "Text with highlighted words" section we have the following: "|#1090;|#1077;|#1089;|#1090;|#1086;|#1074;|#1099;|#1081; |#1087;|#1088;|#1080;|#1084;|#1077;|#1088;"
But the barchart with russian class names (middle column in the visualization) correctly displays class names and relevant words.
Does lime currently support only latin characters to display "Text with highlighted words" section correctly?
Is there any workaround how to display cyrilic letters correctly?
Thank you.

After restarting Jupyter Notebook, this section is displayed correctly for cyrillic letters.


Not very graceful exit from CTRL-C

I used CTRL-C to stop sim-ln and got a bunch of panics:
2023-09-11T14:01:59.526Z ERROR [sim_lib] Simulation results producer task exited with error: task 4566 panicked
2023-09-11T14:01:59.526Z ERROR [sim_lib] Simulation results producer task exited with error: task 4571 panicked
2023-09-11T14:01:59.526Z ERROR [sim_lib] Simulation results producer task exited with error: task 4576 panicked
2023-09-11T14:01:59.526Z ERROR [sim_lib] Simulation results producer task exited with error: task 4581 panicked
2023-09-11T14:01:59.526Z ERROR [sim_lib] Simulation results producer task exited with error: task 4586 panicked
2023-09-11T14:01:59.526Z ERROR [sim_lib] Simulation results producer task exited with error: task 4591 panicked
2023-09-11T14:01:59.526Z ERROR [sim_lib] Simulation results producer task exited with error: task 4596 panicked
2023-09-11T14:01:59.526Z ERROR [sim_lib] Simulation results producer task exited with error: task 4601 panicked
2023-09-11T14:01:59.526Z ERROR [sim_lib] Simulation results producer task exited with error: task 4606 panicked

Hm, I suspect that this may be because we need to merge #75 and you were running with CLN activity - will check it out!

Can we confirm this @maxwedwards?

I can confirm I was running CLN as well as LND. If you need I can try it without a CLN node.

Oh no, I mean if you can try it out now that #75 is merged

I'm struggling to get it to run now. I keep getting:`
2023-09-15T11:59:44.191Z INFO [sim_cli] Connected to<PHONE_NUMBER>5b6ebaa457 - Node ID:<PHONE_NUMBER>5b6ebaa45726c8d7b15e6df00f7802b347abc34216535881d6a82ef4.
2023-09-15T11:59:44.197Z INFO [sim_cli] Connected to BIZARREFEED-v23.08-modded - Node ID: 026ba0f8fd6d39f5dfd59cbfcb58dbe828512d97ee3a2f5c17736497e28c3b8a34.
2023-09-15T11:59:44.198Z INFO [sim_lib] Running the simulation forever.
Error: Lightning Error: GetNodeInfoError("Get node info error status: NotFound, message: \"unable to find node\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\"} }")

Caused by:
    Get node info error Get node info error status: NotFound, message: "unable to find node", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }

I've stared at the config file and limited it to just one activity and checked and rechecked the pubkeys and they seem correct to me. What am I missing? My config:
{
  "nodes": [
    {
      "LND": {
        "id": "03842469335b6ebaa45726c8d7b15e6df00f7802b347abc34216535881d6a82ef4",
        "address": "https://localhost:28103",
        "macaroon": "/Users/max/source/sim-ln/auth/carol/admin.macaroon",
        "cert": "/Users/max/source/sim-ln/auth/carol/tls.cert"
      }
    },
    {
      "CLN": {
        "id": "026ba0f8fd6d39f5dfd59cbfcb58dbe828512d97ee3a2f5c17736497e28c3b8a34",
        "address": "https://localhost:28101",
        "ca_cert": "/Users/max/source/sim-ln/auth/alice/ca.pem",
        "client_cert": "/Users/max/source/sim-ln/auth/alice/client.pem",
        "client_key": "/Users/max/source/sim-ln/auth/alice/client-key.pem"
      }
    }
  ],
  "activity": [
    {
      "destination": "026ba0f8fd6d39f5dfd59cbfcb58dbe828512d97ee3a2f5c17736497e28c3b8a34",
      "source": "03842469335b6ebaa45726c8d7b15e6df00f7802b347abc34216535881d6a82ef4",
      "interval_secs": 1,
      "amount_msat": 2000
    }
  ]
}

I suspect that this has something to do with gossip sync - when running on the regular settings there's a lot of time and block based rate limiting that goes on that's suuuper annoying for local dev. Building CLN in dev mode with --dev-fast-gossip  helps a lot, but (afaik) LND doesn't have a similar setting.
Should be able to confirm that issue with: cl listnodes | grep {pubkey}?
On the sim-ln side, I think that we should expand our wait logic to more gracefully handle this by adding some backoffs / retry loop. Where we won't be able to address this is if it's a block height based local sync problem, but we can at least prompt that.


Add support for Stable Diffusion WebUI Forge

Currently neutral-prompt is not working on Stable Diffusion WebUI Forge because combine_denoised is no longer used and replaced with forge_sampler.forge_sample in forge.

Thanks for reporting. I'm busy right now but I'll try to take a look this week, I think it's important to support forge too.


NYB addresses in localities uk

Description
Issue

What

dev: Address uk nyb info
fix: specify scope of fields=geometry
How

had to separate geometryField between /address and /localities
Related PRs

Woosmap/localities#708
Testing
Automated tests

[ ] Unit Tests cover the change
[ ] Smoke Tests cover the change

Steps to test or reproduce

Deployment
Strategy

[ ] This is a standard deployment

Migrations

Yes/No.

/update-dist


Update to be compatible to vaadin version 8

I have updated the project to be compatible with vaadin 8.
I updated the maven dependencies and cleaned up the pom.xmls to use parent pom informations.
i also fixed bugs #32 #33 #34. this has to be validated.
if you have any questions or want to give some feedback don't hesitate to contact me<EMAIL_ADDRESS>

first of all thank you very much!
i have released 2.0.0 and created a branch vaadin8 for this :)
thanks again!


[BEAM-12507][BEAM-12508] Fix release content blockers

Fixes the release blockers.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @ihji
cc: @kennknowles


Automated cherry pick of #3064: add: 支持创建安全组时同时创建规则

Cherry pick of #3064 on release/2.11.
#3064: add: 支持创建安全组时同时创建规则

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@065356b). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #3066   +/-   ##
==============================================
  Coverage                ?   7.16%
==============================================
  Files                   ?     476
  Lines                   ?   76734
  Branches                ?       0
==============================================
  Hits                    ?    5499
  Misses                  ?   70772
  Partials                ?     463

Flag
Coverage Δ

#aFlag
7.16% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/secgrouprules.go
3.91% <0%> (ø)

pkg/compute/models/secgroups.go
2.29% <0%> (ø)

Continue to review full report at Codecov.

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

/lgtm

/approve


Overhaul of pseudofamily identifiers and tarballs

The current identfier system is a little confusing and not fully consistent.
Moreover current artefacts don't contain the pseudofiles under a consistent name either (e.g. the HGH ones sometimes contain two pseudopotential files for one element --- one for fullcore and one for semicore).
Both needs to be harmonised here and in https://github.com/JuliaMolSim/PseudoLibrary.

@unkcpz We discussed names for pseudopotentials by mail at some point. Have you guys at SSSP / Aiida reached a conclusion on that front ?

@mfherbst, at the moment I change the schema to partially as you suggested (more detail to metadata and only distinguishable arguments in the filename). Next week I'll have a in person meeting with Nicola, and will confirm on it. I'll keep you updated.

Thanks @unkcpz . Any news ?

Had the meeting yesterday, I reply the decision on email.
The typical naming will be: Si.nc.pbe.4E.dojo.v0_4_1.oncvpsp3.std.upf. Where after the version, fields are optional as additional infos.

Ok, so we will use the same for families, but just dropping the element-specific aspects.


Could not get "migration_base_class" to work

Hi, I have been trying to get new migrations to extend my own class instead of "AbstractMigration", and according to 0.13v documentation, it states that I can do so by specifying it like migration_base_class: BaseMigration. I specified it under the "development" environment in my phinx.php and configured my autoloading yet no matter what, it still extends "AbstractMigration".
phinx.php:
'development' => [
    'adapter' => 'mysql',
    'host' => 'localhost',
    'name' => 'TEST',
    'user' => '',
    'pass' => '',
    'port' => '3306',
    'charset' => 'utf8mb4',
    'collation' => 'utf8mb4_unicode_ci',
    'migration_base_class' => 'db/common/BaseMigration',
],

composer.json:
"autoload": {
    "psr-4": {
        "App\\": "app/",
        "Db\\Common\\": "db/common/"
    },

My "BaseMigration.php" is located in db/common/BaseMigration.php where "db" is sitting at my root directory. Now, when I run a verbose migration command: php vendor/bin/phinx create Test -vvv, I can still see that it is using "AbstractMigration".
So, is this migration_base_class outdated or something?

The issue is solved now. Apparently, the migration_base_class should be placed outside of environments, in its own section that is, and not inside the environment, like:
'paths' => [
    'migrations' => '%%PHINX_CONFIG_DIR%%/db/migrations',
    'seeds' => '%%PHINX_CONFIG_DIR%%/db/seeds'
],
'migration_base_class' => 'Db\Common\BaseMigration',


How to validate file extension (.mp3, wmv)

how to validate file extension with Celebrate Joi,
My Joi schema is like this
   body: Joi.object().keys({         Audio: Joi.string().regex(/\.(?:wav|mp3)$/i).optional().options({ language: { any: { allowOnly: 'request id is required' }, label: 'audio file' } }).label('please provide [.mp3] or [.wav] file'),         indexname: Joi.string().required()     })
in audio my file is attached
curl -X POST --header 'Content-Type: multipart/form-data' --header 'Accept: application/json' -F<EMAIL_ADDRESS>-F indexname=1222  'http://<IP_ADDRESS>:3000/api/v1/audio'
so how can i validate file format with the help of joi regex function

Is this an issue with celebrate, or a general support question about using joi? If it's about using joi, I'd suggest experimenting with the schema at https://npm.runkit.com/joi, or asking on the joi issue tracker. Also, see https://github.com/continuationlabs/celebrate#issues.
Thanks, and good luck.

You could try me but I have no idea how express' payload parser ends up converting it, so you're on your own.

Thanks @Marsup i solve this issue.


[FEATURE] Dedicated storage network configuration guide

Is your feature request related to a problem? Please describe.

We'll have a dedicated storage network feature in v1.1.0, before https://github.com/harvester/harvester/pull/2706 is done, we need a guide to tell users how to enable it.
Describe the solution you'd like

Create a guide in the Harvester doc.
Describe alternatives you've considered

Additional context

Related issue: https://github.com/harvester/harvester/issues/1055

Close this since we have the controller. We can use this as a reference in the future.
@tjjh89017 Could you mention this PR in the HEP? Thanks.

Update HEP
mentioned PR in HEP


Tabs and spaces are mixed, let's choose one !

This project is using sometimes tabs[1] and sometimes spaces[2].
It makes this mix more difficult to contribute.
I propose we adopt only spaces as recommended by pep8
https://www.python.org/dev/peps/pep-0008/#tabs-or-spaces
[1] https://github.com/jleclanche/django-push-notifications/blob/master/push_notifications/models.py
[2] https://github.com/jleclanche/django-push-notifications/blob/master/tests/test_models.py

The project uses tabs. Some files I PR'd in use spaces because I didn't catch it at the time. It can be fixed at any point though so I didn't bother with it yet.

Would be great if you can put a note in the README that points to this article.

Added contributing guidelines in 1a0a8a536b2b3b22c0669fdefd810a7764553428.

:+1:


Windows build instructions

Hello,
What are the instructions for building and running the server on a windows machine? The build.sh script does not seem to work either on Windows 7 or Windows 10. I have tried with various Unix shells but could not successfully build it.  I always get the following error on npm install stage:
.><EMAIL_ADDRESS>preinstall c:\Users\ausumezbas\Documents\ONR_3DModeling\ScanNet\sstk
.> ./getdata.sh
'.' is not recognized as an internal or external command, operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>preinstall: ./getdata.sh
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR!      C:\Users\ausumezbas\AppData\Roaming\npm-cache_logs\2018-05-15T15_34_35_420Z-debug.log
Thanks!

Please try the updates on the dev branch, which enable building under windows, and let us know if you encounter any issues.  We will merge these changes into master for an upcoming release.
Note that:

You will need to run in a bash shell with administrator privileges (necessary because creation of symlinks requires privileges in windows) -- we tested using the git bash shell.
If you encounter build errors, you may need to set the path to an installation of Python 2.7 using: npm config set python C:\path\to\python27\python.exe

@msavva: I got it working but I had to set the path to Python in UNIX notation (/c/path/to/python27/python.exe) in the git bash shell.
Also maybe it is worth mentioning somewhere in the readme file that it only works with Python 2.7? I wasted some time trying to make it work with Python 3 before I saw this post :)

Sorry what do you mean by updates on the dev branch? I simply couldn't find it.


[SMD-309] require an Other Funding Source row if FHSF

https://dluhcdigital.atlassian.net/browse/SMD-309
Change description

adds validation that requires a single Other Funding Sources row over any project if FHSF

[X] Unit tests and other appropriate tests added or updated

[X] README and other documentation has been updated / added (if needed)

[X] Commit messages are meaningful and follow good commit message guidelines (e.g. "FS-XXXX: Add margin to nav items preventing overlapping of logo")

How to test
If manual testing is needed, give suggested testing steps
Screenshots of UI changes (if applicable)

Content and lack of cell index to be checked with design.


Can't install Nokogiri because of libxml2 dependency

I get this error.
Installing nokogiri <IP_ADDRESS> with native extensions

Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

    /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb --use-system-libraries
checking if the C compiler accepts ... yes
checking if the C compiler accepts -Wno-error=unused-command-line-argument-hard-error-in-future... no
Building nokogiri using system libraries.
libxml2 version 2.6.21 or later is required!
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Some experimentation may be necessary for your particular setup but recently I have been able to successfully install the latest nokogiri on OS X 10.11 (El Cap) plus AppStore install Xcode. No homebrew libraries were necessary. Using only the Xcode CLI tools was not sufficient.

Thanks @aramprice. I changed my shell from zsh back to bash and it worked for reasons that aren't immediately obvious to me.

Hi @ClayShentrup ,
Thanks for following up—I'm glad things are working for you. I'd like to keep this issue open as a note to look at running sprout on zsh. As long as bash is available, there's no reason immediately obvious to me why sprout-wrap should not be able to be executed from zsh.
Do you know if anything else in your environment changed from the failed run to the successful run? Did you upgrade any rubies and/or gems?

@wendorf I'll get back to you on this as soon as possible. Thanks.

@wendorf I've reinstalled oh-my-zsh but the installation still succeeds. I unfortunately don't know what might have changed. Thanks for your concern and I'm sorry I couldn't be more helpful.


Preserve context when calling log functions

This fixes a rare issue where the built-in sails.log object is overridden with a custom logging implementation which uses functions that depend on a particular value of this.
For example, if a sails.log.verbose() function is called like this:
var log = sails.log.verbose

log(‘test message’)

The value of this within this function will be either undefined (strict mode) or the global object, instead of the expected sails.log object.

For the sake of interest, I have replaced the logger with a bunyan logger, which is implemented this way.

sorry, didn't mean to close this.


use onPreResponse instead of onPostHandler to log all requests

If a response is generated from an onPreHandler extension point, then
onPostHandler won't be invoked.

Is this project still maintained?


Change forms guidance

Delete introduction page and put the content into the hub page instead.
Amend the side-nav-mobile file.
Delete intro page from site map.
Change link on Understand the problem page.
Also tweak contact-panel include.

Merged. Thanks @sarawilcox


Error/s occurred when starting the app

`webpack compiled with 1 error
ERROR in src/components/Scrollbar/index.tsx:16:6
TS2786: 'Scrollbars' cannot be used as a JSX component.
Its instance type 'Scrollbars' is not a valid JSX element.
The types returned by 'render()' are incompatible between these types.
Type 'React.ReactNode' is not assignable to type 'import("C:/Users/Andrew/Repositories/tokyo-free-white-react-admin-dashboard/node_modules/@types/react-transition-group/node_modules/@types/react/index").ReactNode'.
Type '{}' is not assignable to type 'ReactNode'.
14 |
15 |   return (

16 |     <Scrollbars
|      ^^^^^^^^^^
17 |       autoHide
18 |       renderThumbVertical={() => {
19 |         return (

ERROR in src/content/applications/Messenger/index.tsx:86:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
84 |   return (
85 |     <>

86 |
|        ^^^^^^
87 |         Messenger - Applications
88 |
89 |

ERROR in src/content/applications/Transactions/index.tsx:12:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
10 |   return (
11 |     <>

12 |
|        ^^^^^^
13 |         Transactions - Applications
14 |
15 |

ERROR in src/content/applications/Users/profile/index.tsx:28:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
26 |   return (
27 |     <>

28 |
|        ^^^^^^
29 |         User Details - Management
30 |
31 |       <Container sx={{ mt: 3 }} maxWidth="lg">

ERROR in src/content/applications/Users/settings/index.tsx:38:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
36 |   return (
37 |     <>

38 |
|        ^^^^^^
39 |         User Settings - Applications
40 |
41 |

ERROR in src/content/dashboards/Crypto/AccountBalance.tsx:219:18
TS2786: 'Chart' cannot be used as a JSX component.
Its instance type 'ReactApexChart' is not a valid JSX element.
The types returned by 'render()' are incompatible between these types.
Type 'React.ReactNode' is not assignable to type 'import("C:/Users/Andrew/Repositories/tokyo-free-white-react-admin-dashboard/node_modules/@types/react-transition-group/node_modules/@types/react/index").ReactNode'.
217 |                 alignItems="center"
218 |               >

219 |                 <Chart
|                  ^^^^^
220 |                   height={250}
221 |                   options={chartOptions}
222 |                   series={chartSeries}

ERROR in src/content/dashboards/Crypto/index.tsx:15:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
13 |   return (
14 |     <>

15 |
|        ^^^^^^
16 |         Crypto Dashboard
17 |
18 |

ERROR in src/content/dashboards/Crypto/WatchListColumn.tsx:220:12
TS2786: 'Chart' cannot be used as a JSX component.
Its instance type 'ReactApexChart' is not a valid JSX element.
218 |
219 |

220 |           <Chart
|            ^^^^^
221 |             options={chartOptions}
222 |             series={chart1Data}
223 |             type="area"

ERROR in src/content/dashboards/Crypto/WatchListColumn.tsx:295:12
TS2786: 'Chart' cannot be used as a JSX component.
Its instance type 'ReactApexChart' is not a valid JSX element.
293 |
294 |

295 |           <Chart
|            ^^^^^
296 |             options={chartOptions}
297 |             series={chart2Data}
298 |             type="area"

ERROR in src/content/dashboards/Crypto/WatchListColumn.tsx:370:12
TS2786: 'Chart' cannot be used as a JSX component.
Its instance type 'ReactApexChart' is not a valid JSX element.
368 |
369 |

370 |           <Chart
|            ^^^^^
371 |             options={chartOptions}
372 |             series={chart3Data}
373 |             type="area"

ERROR in src/content/dashboards/Crypto/WatchListRow.tsx:209:14
TS2786: 'Chart' cannot be used as a JSX component.
Its instance type 'ReactApexChart' is not a valid JSX element.
207 |
208 |

209 |             <Chart
|              ^^^^^
210 |               options={Box1Options}
211 |               series={Box1Data}
212 |               type="line"

ERROR in src/content/dashboards/Crypto/WatchListRow.tsx:278:14
TS2786: 'Chart' cannot be used as a JSX component.
Its instance type 'ReactApexChart' is not a valid JSX element.
276 |
277 |

278 |             <Chart
|              ^^^^^
279 |               options={Box1Options}
280 |               series={Box2Data}
281 |               type="line"

ERROR in src/content/dashboards/Crypto/WatchListRow.tsx:347:14
TS2786: 'Chart' cannot be used as a JSX component.
Its instance type 'ReactApexChart' is not a valid JSX element.
345 |
346 |

347 |             <Chart
|              ^^^^^
348 |               options={Box1Options}
349 |               series={Box3Data}
350 |               type="line"

ERROR in src/content/overview/index.tsx:20:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
The types returned by 'render()' are incompatible between these types.
Type 'React.ReactNode' is not assignable to type 'import("C:/Users/Andrew/Repositories/tokyo-free-white-react-admin-dashboard/node_modules/@types/react-transition-group/node_modules/@types/react/index").ReactNode'.
18 |   return (
19 |

20 |
|        ^^^^^^
21 |         Tokyo Free White React Typescript Admin Dashboard
22 |
23 |

ERROR in src/content/pages/Components/Accordions/index.tsx:23:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
21 |   return (
22 |     <>

23 |
|        ^^^^^^
24 |         Accordions - Components
25 |
26 |

ERROR in src/content/pages/Components/Avatars/index.tsx:52:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
50 |   return (
51 |     <>

52 |
|        ^^^^^^
53 |         Avatars - Components
54 |
55 |

ERROR in src/content/pages/Components/Badges/index.tsx:44:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
42 |   return (
43 |     <>

44 |
|        ^^^^^^
45 |         Badges - Components
46 |
47 |

ERROR in src/content/pages/Components/Buttons/index.tsx:21:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
19 |   return (
20 |     <>

21 |
|        ^^^^^^
22 |         Buttons - Components
23 |
24 |

ERROR in src/content/pages/Components/Cards/index.tsx:64:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
62 |   return (
63 |     <>

64 |
|        ^^^^^^
65 |         Cards - Components
66 |
67 |

ERROR in src/content/pages/Components/Forms/index.tsx:71:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
69 |   return (
70 |     <>

71 |
|        ^^^^^^
72 |         Forms - Components
73 |
74 |

ERROR in src/content/pages/Components/Modals/index.tsx:99:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
97 |   return (
98 |     <>

99 |
|        ^^^^^^
100 |         Modals - Components
101 |
102 |

ERROR in src/content/pages/Components/Tabs/index.tsx:62:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
60 |   return (
61 |     <>

62 |
|        ^^^^^^
63 |         Tabs - Components
64 |
65 |

ERROR in src/content/pages/Components/Tooltips/index.tsx:20:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
18 |   return (
19 |     <>

20 |
|        ^^^^^^
21 |         Tooltips - Components
22 |
23 |

ERROR in src/content/pages/Status/ComingSoon/index.tsx:102:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
100 |   return (
101 |     <>

102 |
|        ^^^^^^
103 |         Status - Coming Soon
104 |
105 |

ERROR in src/content/pages/Status/Maintenance/index.tsx:32:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
30 |   return (
31 |     <>

32 |
|        ^^^^^^
33 |         Status - Maintenance
34 |
35 |

ERROR in src/content/pages/Status/Status404/index.tsx:44:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
42 |   return (
43 |     <>

44 |
|        ^^^^^^
45 |         Status - 404
46 |
47 |

ERROR in src/content/pages/Status/Status500/index.tsx:54:8
TS2786: 'Helmet' cannot be used as a JSX component.
Its instance type 'Helmet' is not a valid JSX element.
52 |   return (
53 |     <>

54 |
|        ^^^^^^
55 |         Status - 500
56 |
57 |

ERROR in src/content/pages/Status/Status500/index.tsx:106:12
TS2786: 'Hidden' cannot be used as a JSX component.
Its element type 'ReactElement<any, any> | Component<any, any, any>' is not a valid JSX element.
104 |
105 |

106 |
|            ^^^^^^
107 |             <GridWrapper
108 |               xs={12}
109 |               md={6}

ERROR in src/index.tsx:11:4
TS2786: 'HelmetProvider' cannot be used as a JSX component.
Its instance type 'HelmetProvider' is not a valid JSX element.
The types returned by 'render()' are incompatible between these types.
Type 'React.ReactNode' is not assignable to type 'import("C:/Users/Andrew/Repositories/tokyo-free-white-react-admin-dashboard/node_modules/@types/react-transition-group/node_modules/@types/react/index").ReactNode'.
9 |
10 | ReactDOM.render(

11 |
|    ^^^^^^^^^^^^^^
12 |
13 |
14 |

ERROR in src/layouts/SidebarLayout/Header/Buttons/Search/index.tsx:153:18
TS2786: 'Hidden' cannot be used as a JSX component.
Its element type 'ReactElement<any, any> | Component<any, any, any>' is not a valid JSX element.
Type 'Component<any, any, any>' is not assignable to type 'Element | ElementClass'.
Type 'Component<any, any, any>' is not assignable to type 'ElementClass'.
The types returned by 'render()' are incompatible between these types.
Type 'React.ReactNode' is not assignable to type 'import("C:/Users/Andrew/Repositories/tokyo-free-white-react-admin-dashboard/node_modules/@types/react-transition-group/node_modules/@types/react/index").ReactNode'.
151 |
152 |

153 |
|                  ^^^^^^
154 |
155 |                     <Avatar
156 |                       sx={{

ERROR in src/layouts/SidebarLayout/Header/Buttons/Search/index.tsx:192:18
TS2786: 'Hidden' cannot be used as a JSX component.
Its element type 'ReactElement<any, any> | Component<any, any, any>' is not a valid JSX element.
190 |               <Divider sx={{ my: 1 }} component="li" />
191 |

192 |
|                  ^^^^^^
193 |
194 |                     <Avatar
195 |                       sx={{

ERROR in src/layouts/SidebarLayout/Header/Buttons/Search/index.tsx:230:18
TS2786: 'Hidden' cannot be used as a JSX component.
Its element type 'ReactElement<any, any> | Component<any, any, any>' is not a valid JSX element.
228 |               <Divider sx={{ my: 1 }} component="li" />
229 |

230 |
|                  ^^^^^^
231 |
232 |                     <Avatar
233 |                       sx={{

ERROR in src/layouts/SidebarLayout/Header/Userbox/index.tsx:83:10
TS2786: 'Hidden' cannot be used as a JSX component.
Its element type 'ReactElement<any, any> | Component<any, any, any>' is not a valid JSX element.
81 |
82 |

83 |
|          ^^^^^^
84 |
85 |             {user.name}
86 |

ERROR in src/layouts/SidebarLayout/Header/Userbox/index.tsx:91:10
TS2786: 'Hidden' cannot be used as a JSX component.
Its element type 'ReactElement<any, any> | Component<any, any, any>' is not a valid JSX element.
89 |
90 |

91 |
|          ^^^^^^
92 |           <ExpandMoreTwoToneIcon sx={{ ml: 1 }} />
93 |
94 |

ERROR in src/theme/ThemeProvider.tsx:20:6
TS2786: 'StylesProvider' cannot be used as a JSX component.
Its element type 'ReactElement<any, any> | Component<any, any, any>' is not a valid JSX element.
18 |
19 |   return (

20 |
|      ^^^^^^^^^^^^^^
21 |       <ThemeContext.Provider value={setThemeName}>
22 |         {props.children}
23 |       </ThemeContext.Provider>`

I have fixed that issue.
You have to use the version of node 16.
After you should delete the  node_modules folder and you should run npm install command


Error installing project dependencies

An error with the package logging occurs when installing the project dependencies.
root@abb3a1c513e0:/Egyscan# pip install -r requirements.txt
Collecting logging
  Downloading logging-<IP_ADDRESS>.tar.gz (96 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 96.0/96.0 KB 1.6 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [19 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 14, in <module>
        File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 16, in <module>
          import setuptools.version
        File "/usr/lib/python3/dist-packages/setuptools/version.py", line 1, in <module>
          import pkg_resources
        File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 77, in <module>
          __import__('pkg_resources.extern.packaging.specifiers')
        File "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/specifiers.py", line 24, in <module>
          from .utils import canonicalize_version
        File "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/utils.py", line 8, in <module>
          from .tags import Tag, parse_tag
        File "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/tags.py", line 5, in <module>
          import logging
        File "/tmp/pip-install-g5v88z1v/logging_64aa7193546a4653aa69d837c01460a5/logging/__init__.py", line 618
          raise NotImplementedError, 'emit must be implemented '\
                                   ^
      SyntaxError: invalid syntax
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Hello and Thanks For The Feedback however the problem is not with Egyscan itself
but a library used in it Called "logging"
some systems cant install it automaticlly because of updates
so i suggest to install it manually from here
https://pypi.org/project/logging/
Download the Package
Extract it
python setup.py install
Rerun Egyscan
Good luck :)


CAA Support

I see you have support for CAA in master. Is there any chance we can get a timeframe on a tagged release? We have some things that are depending on it and want to see when we can rollout CAA records in our infrastructure.
Thanks

Needed to wrap up https://github.com/github/octodns/pull/105 first. Now that's in place I can go ahead and cut a release.

Nice. Thanks @ross

Hiccup getting it into pypi, but it's there now.


从0.64升级到0.69 appcenter的依赖被忽略

System:
OS: macOS 12.4
CPU: (8) arm64 Apple M1
Memory: 103.44 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.5.0 - /opt/homebrew/bin/node
Yarn: 1.22.10 - /opt/homebrew/bin/yarn
npm: 7.19.1 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: Not Found
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK:
API Levels: 29, 30, 31
Build Tools: 29.0.2, 29.0.3, 30.0.2, 31.0.0
System Images: android-29 | Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7583922
Xcode: 13.4/13F17a - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_292 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.69.0 => 0.69.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

warn Package appcenter has been ignored because it contains invalid configuration. Reason: "dependency.platforms.ios.podspecPath" is not allowed
warn Package appcenter-analytics has been ignored because it contains invalid configuration. Reason: "dependency.platforms.ios.podspecPath" is not allowed
warn Package appcenter-crashes has been ignored because it contains invalid configuration. Reason: "dependency.platforms.ios.podspecPath" is not allowed
warn Package rn-fetch-blob has been ignored because it contains invalid configuration. Reason: "dependency.hooks" is not allowed


Remove errorCodeIfNone capability from normalizeError

normalizeError is a function which takes an unknown error as input and returns a valid Fluid Error, optionally annotating it with IFluidErrorAnnotations.  One annotation type is errorCodeIfNone, which will stamp the given fluidErrorCode on the resulting error if it wasn't already a valid Fluid Error.
Looking back at my notes from the design process that lead to this point, there's not necessarily a clear purpose this serves, other concepts morphed into it in the end.  And revisiting the idea, I expect it to lead to ambiguity and confusion when trying to interpret the logs.  Perhaps the point was to try to get everything with an error code? But it's actually kind of nice to have errors that we didn't raise ourselves left with no error code.  Gives a much cleaner semantic around what fluidErrorCode means.

By the way - this is related to https://github.com/microsoft/FluidFramework/issues/7763 in that any error that's lacking fluidErrorCode is more than likely "not our fault".  So then we can focus on using errorSource for valid Fluid Errors.


Use inherited docstring from super or abstract base class for implementation methods with no docstring

Sphinx and other documentation generators output the docstring associated with the super class method if the sub class implementation doesn't have a docstring.
See other discussion in general on StackOverflow and again.
It would be great to have this as a feature, so when hovering or completing a sub class method, the user can see the docstring from the superclass.
Thanks!

This issue has been fixed in version 2021.3.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202130-3-march-2021


Icons aren't showing

Spamming the buttons removes the icons, can anyone confirm this?

Can you set up a JSFiddle and instructions so other can replicate this?


Comprehensibility issues

Hi,
I had to read the tutorial at least 5 times in order to get a handle on what is done where and give feedback to the company owner of the application. And judging by comments from others, I doubt that many people will be able to keep content apart. It is simply confusing.
I think a restructuring needs to be done. Preferably by dividing the document into several documents. There is simply too much here.
We need to divide by least by workday and connector actions. Then the less technical people can understand more of this.

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

ID: 799c371a-a17e-08aa-ef56-86eef2395f7e
Version Independent ID: 1339cc93-712c-3a32-8321-dfd016a50ed4
Content: Tutorial: Configure Workday for automatic user provisioning with Azure Active Directory
Content Source: articles/active-directory/saas-apps/workday-inbound-tutorial.md
Service: active-directory
GitHub Login: @cmmdesai
Microsoft Alias: chmutali

@Tarjei99 Thank you for your feedback . We will investigate and update this thread.

@Tarjei99 Thank you for your feedback! As content owner, I apologize that it took multiple reads to get a handle on the content. Your feedback is very timely, as I'm working on improving the structure of this article by dividing the content. Look out for an update by mid-April.
#please-close

@Tarjei99 feel free to write to me at Chetan[dot]Desai[at]Microsoft[dot]com if you have further questions regarding this connector or its usage.

@Tarjei99 As per the reply by @cmmdesai we will be closing this issue for now.


Failed to upload files from qeta page to s3

I have the following settings in my app-config.yaml:
qeta:
  allowAnonymous: true
  allowMetadataInput: false
  entities:
    kinds: ['Component']
    max: 3
  tags:
    allowCreation: true
    allowedTags:
      - aws
      - github
      - ci/cd
    max: 5
  storage:
    disabled: false
    type: s3
    maxSizeImage: 2500000
    folder: /tmp/backstage-qeta-images
    # allowedMimeTypes:
    #   - png
    #   - jpg
    #   - jpeg
    #   - gif
    bucket: ${BUCKET}
    accessKeyId: ${S3_ACCESS_KEY_ID}
    secretAccessKey: ${S3_SECRET_ACCESS_KEY}
    region: ${AWS_REGION}
    # sessionToken: ${AWS_SESSION_TOKEN}

When I'm adding the attachment, I'm getting the below error:
qeta error Request failed with status 500 attachment.created.toUTCString is not a function type=errorHandler stack=TypeError: attachment.created.toUTCString is not a function
Did I miss something, or is this a bug ?

Closing this.
It didn't work only from the local.


Ordering of authors on publish page does not reflect ordering in edit authors panel or project page

Describe the bug
Authors are ordered here:

Other ordering is shown here: https://nmrxiv.org/publish/347

Correct ordering ish shown here: https://nmrxiv.org/dashboard/projects/229

Expected behavior
Same ordering of authors on publish page as on project page and edit author panel.
Best,
Tillmann

The dataset got published https://nmrxiv.org/P55 .
The ordering of authors changed again.

We store the sort_order, not sure if we are using this on the front end. Can you please check @NishaSharma14

Dear @tilfischer this works fine for me. Are you trying the same way as I tried here?
screen-capture (21).webm

I confirm the issue:

[ ] viewing on unpublished items can get distorted when changing data in other fields, but if the user reloads the page they see correct order.
[ ] In published projects, the order is not correct

The most interesting thing about this issue is that the ordering was set in the edit authors panel and shown that way on the project page. Other ordering is shown on the publish page. After the project got published, it showed the wrong ordering as on he publish page but not the ordering set in the edit authors panel, was was shown the right way on the project page.

Dear @tilfischer,
We have found the root cause now & it will be fixed soon.


Unstable CI - bugfix

Description
CI test with SIngularity appears to pass/fail in a non-deterministic manner...
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have not reduced the existing code coverage

I saw the build page that failed in dev. On searching about it, It seems like a known issue in snakemake, see https://github.com/snakemake/snakemake/issues/303

OK, I have updated snakemake version. "All checks have passed" here - builds with no problems. I will merge again and hopefully no errors arise this time.


MuhammadFareezIqmal.IIUMSchedule version <IP_ADDRESS>

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Does your manifest conform to the 1.1 schema?

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

Microsoft Reviewers: Open in CodeFlow

Blocking https://github.com/microsoft/winget-pkgs/issues/68845#issuecomment-1216812029

Thanks

@wingetbot run

/azp run

@wingetbot run

Any suggestion on how to fix the Validation-Executable-Error error?


Help with NLP example in fastai

Hi,
I am trying to use LIME (<IP_ADDRESS>) with fastai NLP classifier. I was following the multi-class example, and reading the doc on classifier_fn.
exp = explainer.explain_instance(valid_df.iloc[2][1], pred_batch, num_features=6, labels=[0, 13])

my classifier_fn pred_batch will return a np.array of [d,k] as specified.
def predict_fn(txt):
  y_hat, y_hat_tensor, y_softmax = learn_smooth.predict(txt)
  return y_softmax.cpu().detach().numpy()

def pred_batch(texts):
  for i, txt in enumerate(texts):
    output = predict_fn(txt)
    print(output)
    if i==0:
      preds=output
    else:
      preds = np.concatenate((preds,output), axis=0) #preds.shape is (17,), where 17 is len(class_names)
    return preds.reshape(-1, len(class_names))

I'm seeing this error right now.
/usr/local/lib/python3.6/dist-packages/lime/lime_text.py:114: FutureWarning: split() requires a non-empty pattern match.
  self.as_list = [s for s in splitter.split(self.raw) if s]
[0.00725745 0.0095798  0.00716048 0.00727127 0.00712212 0.00990204
 0.01164983 0.00460478 0.00859626 0.00784894 0.00683739 0.8718843
 0.00905153 0.00636076 0.01033731 0.00694667 0.00758902]
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-78-d1d639d790bb> in <module>()
      1 idx = 1340
----> 2 exp = explainer.explain_instance(valid_df.iloc[2][1], pred_batch, num_features=6, labels=[0, 13])

8 frames
/usr/local/lib/python3.6/dist-packages/lime/lime_text.py in explain_instance(self, text_instance, classifier_fn, labels, top_labels, num_features, num_samples, distance_metric, model_regressor)
    430                 data, yss, distances, label, num_features,
    431                 model_regressor=model_regressor,
--> 432                 feature_selection=self.feature_selection)
    433         return ret_exp
    434

/usr/local/lib/python3.6/dist-packages/lime/lime_base.py in explain_instance_with_data(self, neighborhood_data, neighborhood_labels, distances, label, num_features, feature_selection, model_regressor)
    185                                                weights,
    186                                                num_features,
--> 187                                                feature_selection)
    188         if model_regressor is None:
    189             model_regressor = Ridge(alpha=1, fit_intercept=True,

/usr/local/lib/python3.6/dist-packages/lime/lime_base.py in feature_selection(self, data, labels, weights, num_features, method)
    133                 n_method = 'highest_weights'
    134             return self.feature_selection(data, labels, weights,
--> 135                                           num_features, n_method)
    136
    137     def explain_instance_with_data(self,

/usr/local/lib/python3.6/dist-packages/lime/lime_base.py in feature_selection(self, data, labels, weights, num_features, method)
     74             return np.array(range(data.shape[1]))
     75         elif method == 'forward_selection':
---> 76             return self.forward_selection(data, labels, weights, num_features)
     77         elif method == 'highest_weights':
     78             clf = Ridge(alpha=0.01, fit_intercept=True,

/usr/local/lib/python3.6/dist-packages/lime/lime_base.py in forward_selection(self, data, labels, weights, num_features)
     58                     continue
     59                 clf.fit(data[:, used_features + [feature]], labels,
---> 60                         sample_weight=weights)
     61                 score = clf.score(data[:, used_features + [feature]],
     62                                   labels,

/usr/local/lib/python3.6/dist-packages/sklearn/linear_model/_ridge.py in fit(self, X, y, sample_weight)
    764         self : returns an instance of self.
    765         """
--> 766         return super().fit(X, y, sample_weight=sample_weight)
    767
    768

/usr/local/lib/python3.6/dist-packages/sklearn/linear_model/_ridge.py in fit(self, X, y, sample_weight)
    545                          accept_sparse=_accept_sparse,
    546                          dtype=_dtype,
--> 547                          multi_output=True, y_numeric=True)
    548         if sparse.issparse(X) and self.fit_intercept:
    549             if self.solver not in ['auto', 'sparse_cg', 'sag']:

/usr/local/lib/python3.6/dist-packages/sklearn/utils/validation.py in check_X_y(X, y, accept_sparse, accept_large_sparse, dtype, order, copy, force_all_finite, ensure_2d, allow_nd, multi_output, ensure_min_samples, ensure_min_features, y_numeric, warn_on_dtype, estimator)
    763         y = y.astype(np.float64)
    764
--> 765     check_consistent_length(X, y)
    766
    767     return X, y

/usr/local/lib/python3.6/dist-packages/sklearn/utils/validation.py in check_consistent_length(*arrays)
    210     if len(uniques) > 1:
    211         raise ValueError("Found input variables with inconsistent numbers of"
--> 212                          " samples: %r" % [int(l) for l in lengths])
    213
    214

ValueError: Found input variables with inconsistent numbers of samples: [5000, 1]

Please help clarify.

Is valid_df.iloc[2][1] a single string?  That is certainly a problem, the output shape should be (2, 17)

Ugh, copy-paste issue with indents.
>> pred_batch(['John is a man', 'Lorem Ipsum'])
array([[0.018254  , 0.0287193 , 0.00983582, 0.01473297, 0.01410102,
        0.23285404, 0.42372432, 0.01859927, 0.01005701, 0.00928846,
        0.01846664, 0.03480202, 0.03841193, 0.01163836, 0.08270189,
        0.01756956, 0.01624339],
       [0.02495235, 0.02630385, 0.01634027, 0.02060439, 0.01779184,
        0.0972065 , 0.15644194, 0.02681249, 0.01201311, 0.01035838,
        0.02608175, 0.03298733, 0.31189927, 0.02127631, 0.13273412,
        0.0309938 , 0.03520232]], dtype=float32)

>> pred_batch(['John is a man', 'Lorem Ipsum']).shape
(2, 17)

OK, my original code is running something now, but since I am only sending one single sentence, I am surprised it is taking so long (5 minutes)
>> exp = explainer.explain_instance(valid_df.iloc[2][1], pred_batch, num_features=6, labels=[0, 13])
/usr/local/lib/python3.6/dist-packages/lime/lime_text.py:114: FutureWarning: split() requires a non-empty pattern match.
  self.as_list = [s for s in splitter.split(self.raw) if s]

It shows a progress bar and then it keeps 'blinking'

Looks like it's working. The default number of perturbed instances is 5,000


conda install -c conda-forge gxx=11 gcc=11

i got PackagesNotFoundError
then i use:
conda search --channel conda-forge gcc
conda search --channel conda-forge gxx
and then (after i got results)
i used:
conda install -c conda-forge gcc=13.2.0=hc382ac0_10
conda install -c conda-forge gxx=13.2.0=hc382ac0_10
its ok?

I think it should be fine as long as gcc/g++ >= 11

Since there are no further replies to the issue, I will close it. Feel free to reopen it if the problem persists.


Explicitly initialize plugins (fixes #38)

This allows a user to import plugins on local development environments which do not have access to AWS metadata without stalling the process at boot time.
Each of the three plugins will need to be imported and initialized manually.
The API will safeguard against multiple requests but it's not goroutine safe.

why not surround the init code with sync.Once to make them concurrent safe?

why not surround the init code with sync.Once to make them concurrent safe?

That's a very good point, I'll update the PR to reflect this, thank you!

Yah, this is a better way of doing it.  init forces it to be at starttime and can cause conflicts occasionally.

Yah, this is a better way of doing it. init forces it to be at starttime and can cause conflicts occasionally.

This is not why I wanted to change this, please read #38.


Michael/fix exit no test

Need to merge #64 first.
Close #62
We can't use Promise.race because runTests does not await for tests to complete (this is what the drained event is for..)

@mikicho I push what I think is the correct fix. please squash this into a single commit?

@mikicho can you please amend the commit message? fix: don't exit when no tests on initial run
the commit messages are used for the release notes

@MoLow PTAL


Art Station support

Ripme version: 1.5.2
Java version (output of java -version):
Operating system: MacOs Sierra
Exact URL you were trying to rip when the problem occurred: https://www.artstation.com/artist/yangqi917
Please include any additional information about how to reproduce the problem:

Expected Behavior
the expected behavior is that it is supposed to download the files.
Actual Behavior
"Can't rip this URL: com.rarchives.ripme.ripper.rippers (null) does not appear to be a valid package"

This is a request for a new ripper. Closing with link to #38 (catch-all issue for requests).
Thanks for your request!


Switch from API contract version to IsMethodPresent (#6886)

This change adds IsMethodAvailble() to WindowsApiChecker and marks the UniversalApiContractV#_IsAvailble properties as obsolete.
References tot he contract version check in MRTK have been updated to use the new method.
Fixes: #6886

/azp run

/azp run


Make adding track process to set interpolation type on creating RESET

When creating the RESET track by key insertion, the angle property defaults to Linear Angle at some point, but when creating the RESET track, the interpolation_type setting is lacking, so the warning is always generated due to those discrepancies. Fix them to match.

Thanks!


global no_addtional_properties too strong

demo here http://hkuclion.com/demo/JsoneditorDemo/no_additional_properties.html
When using no_addtional_properties in jsoneditor initialization, it will make all sub objects unable to add properties.
And with schema, I could use 'additionalProperties':true to make an object have custom properties to be added.
Further more, if the property that added to this object itself is another object, I have no ways to make it have a custom property. since it has no schema, and global options fobid additional properties.
Can there be an solution to this?

further question:
when readOnly, the form element is disabled, thus its value disappears  from the form;
when use Only the getValue from the EditorAPI, the formname add a lot of unneccessary data.
can readOnly items be only readonly instead of disabled?


Fix typos

This pull request addresses minor grammatical issues for improved clarity and correctness:

Added a comma after "Currently" in the README.md to improve sentence structure.
Corrected "ethers" to "ether" in lib.ts to properly align with grammatical usage.

Changes include:

In README.md, updated "Currently supported network values..." for better readability.
In lib.ts, fixed the usage of "ethers" to "ether" to follow proper grammar rules.

These changes improve the overall clarity and accuracy of the documentation and code.

We are not accepting PRs of this for now.


support latest pytorch

Since the original code does not work well with Pytorch 0.4 or later, regard this concern,
I reimplement the CNN part that supports the latest Pytorch, and the code is available at
https://github.com/MandyMo/DARTS.

does work -> does not work ?

does work -> does not work ?

thank you.

I also improved the code to make it compatible with PyTorch 1.1 while allowing multi-GPU training on both RNN and CNN experiments.~ you can refer: https://github.com/alphadl/darts.pytorch1.1

@alphadl Hi, I tried your multi-GPU code, but it doesn't seem to work effectively. Could you help me?

I also improved the code to make it compatible with PyTorch 1.1 while allowing multi-GPU training on both RNN and CNN experiments.~ you can refer: https://github.com/alphadl/darts.pytorch1.1

hi, the weight in your code should require grad.
However after I change this line, I still cannot reprodcue rnn result in this paper.


Remove permission length check

In some Hadoop clusters, users enable some extensions, such as ACLs.

At this time, libhdfs will report an error, which cannot be bypassed without modifying the cluster configuration.

Similar checks are not done in hadoop code

Ok, looks reasonable.