VTK8 - Locally running trunk (3.0) behaves differently on OSX if XQuartz/Grab are running

I finally built trunk on my OSX system using build_visit build_visit buildmode Debug required optional allio fortran parallel thirdparty-path /Users/miller86/visit.new/thirdparty/3.0 \ debug noadios2 nofastbit nofastquery nonektarpp no-pyside The 5 trailing no-xxx args were to disable things that were preventing build_visit from completing successfully. However, I noticed that I am seeing that same build behave differently depending on whether or not I have other applications running such as XQuartz or sometimes Grab. I've attached two pictures one with and one without XQuartz running. However, this isn't always reproducible. Sometimes, even when I quit XQuartz, I still see the bad behavior. Also, am noticing this on stderr, for both good and bad cases, when running... dlerror() = dlopen(libospray_module_ispc.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_native_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_avx2_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_avx_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_sse4_float.dylib, 10): image not found #osp: INITIALIZATION ERROR > could not open module lib ospray_module_ispc Running: engine_ser dv idletimeout 480 host <IP_ADDRESS> -port 5600 dlerror() = dlopen(libospray_module_ispc.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_native_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_avx2_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_avx_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_sse4_float.dylib, 10): image not found #osp: INITIALIZATION ERROR > could not open module lib ospray_module_ispc
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 3266
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: VTK8 - Locally running trunk (3.0) behaves differently on OSX if XQuartz/Grab are running
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 11/20/2018
Due date:
% Done: 0%
Estimated time:
Created: 11/20/2018 01:23 pm
Updated: 11/27/2018 06:52 pm
Likelihood: 4 - Common
Severity: 4 - Crash / Wrong Results
Found in version: 2.12.3
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
I finally built trunk on my OSX system using build_visit build_visit buildmode Debug required optional allio fortran parallel thirdparty-path /Users/miller86/visit.new/thirdparty/3.0 \ debug noadios2 nofastbit nofastquery nonektarpp no-pyside The 5 trailing no-xxx args were to disable things that were preventing build_visit from completing successfully. However, I noticed that I am seeing that same build behave differently depending on whether or not I have other applications running such as XQuartz or sometimes Grab. I've attached two pictures one with and one without XQuartz running. However, this isn't always reproducible. Sometimes, even when I quit XQuartz, I still see the bad behavior. Also, am noticing this on stderr, for both good and bad cases, when running... dlerror() = dlopen(libospray_module_ispc.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_native_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_avx2_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_avx_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_sse4_float.dylib, 10): image not found #osp: INITIALIZATION ERROR > could not open module lib ospray_module_ispc Running: engine_ser dv idletimeout 480 host <IP_ADDRESS> -port 5600 dlerror() = dlopen(libospray_module_ispc.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_native_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_avx2_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_avx_float.dylib, 10): image not found dlerror() = dlopen(libospray_module_ispc_sse4_float.dylib, 10): image not found #osp: INITIALIZATION ERROR > could not open module lib ospray_module_ispc
Comments:

with xquartz running

without xquartz running


Issue#38 : Header Navigation Fixed

After changes 👇🏻

@SoumyadeepOSD this is not a required as per design. Please follow the designs do not think overhead. It was just alignment that was required

@SoumyadeepOSD this is not a required as per design. Please follow the designs do not think overhead. It was just alignment that was required

Okay @varun-singhh  I'll now work on only alignment


Reverse the scrolling actions

Hi Mike
I'm aware of settings but it would be ideal to reverse the scroll actions. On a mobile device or a small screen the left arrow should scroll the available tabs to the left instead. It might be good to have an option to reverse the scrolling setting, just my 2 cents!
Cheers
B

Good suggestion. I'll add that option.

For v0.2.0 I added a reverse-scroll option. Just pass in option reverseScroll: true.
Details in the README here.


Hydration issue when rendering dynamic head element

Describe the bug
When using the @sveltejs/adapter-static and appending a script tag with application/ld+json type to svelte:head, it won't show up in the build version of your site/app. It shows up correctly when you're developing, but npm run build loses it from head tag.
Code sample:
<script>
const item_title = 'Hello world!';

const schema = {
    "@context": "http://schema.org",
    "@type": "Article",
    "@name": item_title
  };
</script>

<svelte:head>
  {@html '<script type="application/ld+json">' + JSON.stringify(schema) + '</script>'}
</svelte:head>

To Reproduce
Append script tag with application/ld+json attribute on svelte:head and build/export site using static adapter.
Expected behavior
Added script tag / ld json schema should be visible in head tag after exporting the site as static.
Information about your SvelteKit Installation:

Diagnostics
System:
OS: Windows 10 10.0.18363
CPU: (4) x64 Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Memory: 2.39 GB / 7.95 GB
Binaries:
Node: 15.12.0 - C:\Program Files\nodejs\node.EXE
npm: 7.6.3 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 89.0.4389.114
Edge: Spartan (44.18362.449.0)
Internet Explorer: 11.0.18362.1
npmPackages:
@sveltejs/kit: next => 1.0.0-next.74
svelte: ^3.29.0 => 3.37.0
vite: ^2.1.0 => 2.1.5
Static adapter.

Severity
Mediumish

After more testing, looks like the application/ld+json is indeed in place if you navigate to your desired page by clicking via on-site navigation buttons.
For example;

Land on front page
Navigate to blog/article-slug by using on-site navigation
application/ld+json tag is in place

Now if you refresh the page here or come with a direct link (e.g. yoursite.com/blog/article-slug) the application/ld+json will not be in place and has disappeared.
If you navigate back to front page and then again to blog/article-slug, the application/ld+json won't be in place anymore either.
So it seems to work only once per session when landing to a page that has application/ld+json, as long as you navigate to the page manually and not with a direct link. 🤔

You may need to preserve ld+json tags in svelte-preprocess in your config:
// svelte.config.cjs
const sveltePreprocess = require('svelte-preprocess');

module.exports = {
  preprocess: sveltePreprocess({
    preserve: ['ld+json'],
    // ...
  }),
  // ...
};

Thanks @hobbes7878
Tried this after your suggestion and it does not fix the issue :/

You need to do the preserve option and also just put the contents of the script directly in <svelte:head> instead of wrapping in @html

Hmm. The HTML option enables to put dynamic content there. Something like this wouldn't work without it:
<script>
  const schema = {
      "@context": "http://schema.org",
      "@type": "Article",
      "@name": item.title,
      "datePublished": new Date(item.date_gmt).toISOString(),
      "dateModified": new Date(item.modified_gmt).toISOString(),
      "image": item.featured_image,
      "articleBody": item.content.rendered
    }
</script>

<!-- shows up in HTML code exactly as written in head tag -->
<svelte:head>
  <script type="application/ld+json">
     {schemaObject}
  </script>
</svelte:head>

<!-- expected output is the schema object provided -->

As you can't reference to the variables within the script tag. The HTML method was suggested here for Sapper which presumably works in it: https://github.com/sveltejs/svelte/issues/2438#issuecomment-542166747
Could you double confirm support for that method indeed dropped in SvelteKit?

I verified that this is static adapter related issue. When running and deploying app with vercel adapter there is no issues with application/ld+json not showing up after build. ping @benmccann

Hmm. I have a pre-rendered SvelteKit site using ld+json deployed to http://c3.ventures/ and it works just fine. My schema is static instead of dynamic so I didn't have a need for the @html. If @html works elsewhere I don't know of anything that would make it break in SvelteKit. That was just the only thing I noticed different between your example and what I'm doing
I noticed in the example you posted that you have two closing braces for schema. I wonder if that might be causing trouble?

Hey, the typo was only in the example - not my actual code. The issue seems to only happen with static adapter.
Did again some further testing and I've noticed that sometimes it works and sometimes not.

Coming with direct link does not usually load ld+json to head
Navigating via on-app links most-likely loads ld+json to head
Refreshing page sometimes loses ld+json from head

Following along with this discussion, the issue being dynamic data in <svelte:head />, the only form that seems to work as of<EMAIL_ADDRESS>is the @html injection method. After many tests in development and build it appears to be consistently working.
<svelte:head>
	{@html '<script type="application/ld+json">' + JSON.stringify(schemaObject)}
</svelte:head>

Just chiming in as I'm facing similar issues. As a recap, in my understanding the current state seems to be:
This is the most intuitive approach:
<svelte:head>
  <script type="application/ld+json">
     { "@context": "http://schema.org", ... }
  </script>
</svelte:head>

To make it work, preprocess({ preserve: ['ld+json'] }) has to be set in svelte.config.js. (Might be addressed in https://github.com/sveltejs/svelte-preprocess/issues/305 ?!)
Unfortunately there is a huge downside: the schema object cannot be created dynamically. To address this problem, there is this workaround:
<svelte:head>
    {@html `<script type="application/ld+json">
        ${ JSON.stringify({ '@context': 'https://schema.org', ...schema }) }
    </script>`}
</svelte:head>

Now TypeScript is giving me pretty weird errors for the whole file (see screenshot) and Svelte Prettier is doing strange stuff too (converting the script tag to something like [...]tion/ld+json" ✂prettier:content✂="JHsgSlNPTi5zdHJp[...]).

Though, someone on Stack Overflow found another workaround to keep TypeScript and Prettier happy:
<svelte:head>
    {@html `<script type="application/ld+json">${schema + "<"}/script>` }
</svelte:head>

This seems to do the trick, but looks and feels rather hacky.
BUT, again there is an issue: Now the JSON-LD script tag is included twice in the header. Even worse, the initial one won't go away when navigating your website. That means

e.g. Google will parse two identical JSON-LDs (I verified it via their testing tool)
Search engines might get confused as an incorrect/outdated JSON-LD will be served while browsing the website.
I suspect these issues will do the opposite and even affect SEO negatively

Can someone verify that the dynamic tag is included twice (and one of them doesn't update)? What can we do to solve this?

Hey @kvn-shn, did you try my example above, I'm running both typescript and sveltest prettier plugin and it's all working for me. Initially, I tried something similar to you on my first attempt. I think the issue is using variables in a string literal inside a compiled injector.

I investigated this a bit and filed an issue for it over in the Svelte core repo https://github.com/sveltejs/svelte/issues/6463. I'm closing this bug in favor of that one

Hey @kvn-shn, did you try my example above

Yes, I did. But for me (using Firefox) the missing closing script tag caused the script to "eat up" other tags SvelteKit was adding below. So I didn't investigate further.

A work around for this for anyone using google  structured data, is to include it the body and not the head, since google doesn't mind: https://www.youtube.com/watch?v=lI6EtxjoyDU&t=94s


[DIR-1491] Improve metrics

Description
This updates the metrics visualization with data categories from the new notifications endpoint.
The way percentages were calculated previously was a bit off. Now it will do the following:

The text below the visual will only say "NN% success rate".
complete will be compared to failed + crashed to calculate success rate.
complete, failed + crashed will be shown in the visual, so they will be consistent with the %. Pending and Cancelled workflows will not be reflected.

Crashed instances will be rendered in pink. I don't have a test case to produce this. The next screenshot was made by hard-coding the value in src/pages/namespace/Explorer/Workflow/Overview/utils.tsx.

I also refactored the code to make it easier to follow (and maintain) what data we aggregate and how it is passed into the Donut component.
Checklist

[x] Documentation updated if required
[x] Test coverage is appropriate

Checklist Internal

[x] Linear issue linked (e.g. [DIR-XXXX] pull request title)
[x] Has the PR been labeled

Thanks @stefan-kracht , good find with the NaN percentage. I needed to restructure the conditions and rely on early returns to finally get it all right. I also moved that code to a new component -- and removed the other proxy component as suggested.


Catching input

SUIT does not "catch" mouse input (in the sense that say a click on a button will still result in a mouseclicked event for the rest of the program) and I can't see any feature to turn it on. Is there at least a way to know if a certain mouseclick was registered by SUIT? If the player presses a button, I don't want my game to react to that.

Intercepting mouse clicks is not in the spirit of SUIT (there are no "events", only state). Mouse clicks are handled by the widgets themselves and they signal a mouse hit in their return state. I can see that this is a bit inconvenient.
What would be a good interface to query if a mouse click was catched by a widget?

I'm currently using the AnyHovered function with pretty good results, but I imagine there are edge cases where it would cause wrong behavior. What I'd like is something similar that could be queried on whether the last mouse press event caused any widgets to return true on their hit, as I could then ignore that event on my game input. Would that be doable?

anyActive() (mouse pressed on any widget) is straightforward to implement, and anyHit() (mouse pressed and released on any widget) should also be possible. Will that solve the edge cases?

I think that should cover it, yes. The edge cases I had in mind were if the user pressed on a button and quickly moved off it, or maybe pressed outside of it and moved on before I had time to call AnyHovered(). I don't know enough about how you handle mouse events to see if that is actually realistic or possible, but AnyHovered() feels dirty to use when you're actually asking about the last click.

Especially anyHit() is what I would use.

Also, is there a function like suit.has_keyboard_focus()?

I found suit.keyboardFocus, but it is always nil.

@buckle2000 There is suit.hasKeyboardFocus(id). Note that you can only only access keyboardFocus from suit instances, but not from the default instance.
For the default instance, you can get the id that currently has keyboard focus with suit._instance.keyboardFocus.


V3.0.0

Finger crossed!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

We have 22 tests failing on Linux :-/
@sodre are you familiar with the tests here?


Logging option for smbv1 connections missing

Hi,
it would be very useful to include in this article the instructions how to really log and detect smbv1 connections like in one of our blogs:
https://secureinfra.blog/2018/12/17/step-by-step-safely-disabling-smb-v1-from-your-production-environment/
Otherwise customers are often not aware that there is an option to really track the connections and upgrade the client systems before disabling smbv1
Kind regards
Tanja

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

ID: 8a91db45-ca3c-7a2e-3f32-2f5b57837b03
Version Independent ID: b83cbaab-c0df-d6e7-a67f-f4c99a46e30a
Content: How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows
Content Source: WindowsServerDocs/storage/file-server/Troubleshoot/detect-enable-and-disable-smbv1-v2-v3.md
GitHub Login: @Deland-Han
Microsoft Alias: delhan

#assign:xelu86

Hello @Azaraya,
We'd like to express our gratitude for your commitment to our documentation. Unfortunately, we’ve fallen short of our usual standards in addressing documentation concerns in a timely manner and offer our apologies for any inconvenience we’ve caused.
Because this issue is now outdated, we’re closing this request. If we've addressed the documentation issue, this thread will also be closed. However, if you believe there’s still a documentation concern, you're encouraged to open a new GitHub issue. We welcome any suggestions for improving our documentation to provide a more satisfactory experience in the future. Thanks for your understanding and continued support.
#please-close


$reindex does not update lucene / elastic index

Describe the bug
The $reindex operation does not recreate the resourcetable index when advancedHSearchIndexing is enabled. Even though data is being indexed when writing resources using POST / PUT.
To Reproduce
Steps to reproduce the behavior:

Set up a server with elasticsearch index (using jpa starter enable: advanced_lucene_indexing, elasticsearch.*, hibernate.search.backend.type: elasticsearch)
Create some Resources (e.g. using POST / PUT)
Delete data from the elasticsearch index (or switch the options from above on at this point)
POST to /fhir/$reindex
Da a search e.g. using _contents

Expected behavior
It should return matching results after reindex, even though they have been manually removed from the index.
Environment (please complete the following information):

HAPI FHIR Version: jpa starter master (7.0.2)
OS: MacOS
Browser: n/a

Additional context
I did some debugging already. When updating an entity the lucene indexer creates a new elasticsearch document when
https://github.com/hapifhir/hapi-fhir/blob/master/hapi-fhir-jpaserver-base/src/main/java/ca/uhn/fhir/jpa/dao/BaseHapiFhirResourceDao.java#L2282
		return myTransactionService
				.withRequest(theRequest)
				.withTransactionDetails(theTransactionDetails)
				.withRequestPartitionId(requestPartitionId)
				.onRollback(onRollback)
				.execute(updateCallback);

is being called inside the update method.
During reindex this dos not happen. reindex calls reindexSearchParameters which correctly updates the index tables but does not write the resource itself. Thus never reaching the search index logic.

I have the same problem. Any update on this?


Missing "ほう***" entries

I've got them automatically and fixed them manually.
Maybe there are some mistakes and you need to calculate the scores.
Check "tmp.hou" please.

e.g.
======================================================
うりばのほう  2235    2399    6828    売り場のほう
おくさんのほう   2235    2399    6172    奥さんのほう
======================================================

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 9 Nov 2010 at 8:00
Attachments:

tmp.hou

What types of misconversions can be fixed by adding them?  What is the expected
results?

Original comment by<EMAIL_ADDRESS>on 10 Nov 2010 at 7:00

Original comment by<EMAIL_ADDRESS>on 1 Apr 2012 at 2:25

Added labels: Type-Conversion
Removed labels: Type-Defect

Original comment by<EMAIL_ADDRESS>on 1 Apr 2012 at 2:29

Added labels: OpSys-All


Modifying process.env.NODE_ENV breaks React

React has some places where it conditionally defines and calls functions. In the compiled version of React, the condition used is process.env.NODE_ENV === 'production'. Since _modifyProcessEnv() changes this value at runtime, React can wind up not defining the function, but then later attempting to call it. This seems to be the root cause of facebook/nuclide#1172 and steelbrain/linter-ui-default#212.

Humm... According to this line https://github.com/PEM--/meteor-helper/blob/v0.29.0/lib/meteor-helper-view.coffee#L194, process.env.NODE_ENV is only modified when you specify it in your configuration.

And from what I recall from React's source, code is only skipped when process.env.NODE_ENV !== 'production'. Hence, if you're passing any specific NODE_ENV except production, you should be good to go.

Wow, thanks for the quick response @PEM--! 😊
Did you see the React links in the OP? The first one defines a function when process.env.NODE_ENV !== 'production' and the second calls the function on the same condition. However, it's reevaluated each time so if the value changes from 'production' to something else, it's going to try to call a function that hasn't been defined.

Indeed, I've seen it. Nuclide should not be shipped in development mode if they rely on React.

Same stuff for linter-ui-default 😉
What's surprise me is that I don't get this issue on my setup... Anyway, shipping code in dev mode seems a bit... well... humm... anyway 😄

Hm…Well, Nuclide isn't shipping code "in dev mode," really (it's a runtime switch in React). But I see where you're coming from. Ideally, switching wouldn't be possible I suppose. But practically, I think this is the best choice for Nuclide if we want to have dependencies that require React. (Bundling would be a big overhead.)
Can I ask why meteor-helper has to change the current process's NODE_ENV? Couldn't it just pass a modified version to the BufferedProcess?

Q: Can I ask why meteor-helper has to change the current process's NODE_ENV?
R: My users are using it to trigger different Meteor build.
Q: Couldn't it just pass a modified version to the BufferedProcess?
R: Indeed doable though that does not solve the nuclide usage of React in development package. Installing its dependencies with npm --production would solve all their problem and would avoid shipping code not used by their users. As a side effect, they would not have issues anymore caused by other package which are toying with process.env.NODE_ENV.

Will do 😉
Pretty stoked on the fact that Atom's will be using React. Nice move 👍


Issue launching the Musicbot

Please tick all applicable boxes.

[x] I am using Python 3.5.3 or higher (run python --version on the command line)
[x] I have followed the official guides to install the bot for my system
[x] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[ ] The latest master version (release-260419)
[ ] The latest review version

What type of issue are you creating?

[ ] Bug
[ ] Feature request
[x] Question

Description of issue
[INFO] launcher: Starting sanity checks
[INFO] launcher: Checking for Python 3.5+
[INFO] launcher: Checking console encoding
[INFO] launcher: Setting console encoding to UTF-8
[INFO] launcher: Ensuring we're in the right environment
[INFO] launcher: Adding local bins/ folder to path
[INFO] launcher: Required checks passed.
[INFO] launcher: Optional checks passed.
[INFO] launcher: Moving old musicbot log
[ERROR] launcher: Error starting bot
Traceback (most recent call last):
File "C:\Users\User\OneDrive\Documents\GitHub\MusicBot\run.py", line 367, in main
from musicbot import MusicBot
File "C:\Users\User\OneDrive\Documents\GitHub\MusicBot\musicbot_init_.py", line 7, in
from .utils import _get_variable
File "C:\Users\User\OneDrive\Documents\GitHub\MusicBot\musicbot\utils.py", line 3, in
import aiohttp
ModuleNotFoundError: No module named 'aiohttp'
[INFO] launcher: Attempting to install dependencies...
Collecting pynacl==1.2.1
Using cached PyNaCl-1.2.1.tar.gz (3.3 MB)
Collecting discord.py[voice]==1.2.5
Using cached discord.py-1.2.5-py3-none-any.whl (655 kB)
Requirement already up-to-date: pip in c:\users\user\appdata\local\programs\python\python39\lib\site-packages (from -r requirements.txt (line 3)) (20.2.4)
Collecting youtube_dl
Using cached youtube_dl-2<IP_ADDRESS>-py2.py3-none-any.whl (1.8 MB)
Collecting colorlog
Using cached colorlog-4.4.0-py2.py3-none-any.whl (14 kB)
Collecting cffi
Using cached cffi-1.14.3-cp39-cp39-win_amd64.whl (179 kB)
Collecting six
Using cached six-1.15.0-py2.py3-none-any.whl (10 kB)
Processing c:\users\user\appdata\local\pip\cache\wheels\4d\b9\64\93e895a06acf653b24f528f16003ca62551660fe57e028244b\aiohttp-3.5.4-py3-none-any.whl
Collecting websockets<7.0,>=6.0
Using cached websockets-6.0.tar.gz (70 kB)
Collecting colorama; sys_platform == "win32"
Using cached colorama-0.4.4-py2.py3-none-any.whl (16 kB)
Collecting pycparser
Using cached pycparser-2.20-py2.py3-none-any.whl (112 kB)
Collecting multidict<5.0,>=4.0
Using cached multidict-4.7.6.tar.gz (50 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing wheel metadata ... done
Collecting chardet<4.0,>=2.0
Using cached chardet-3.0.4-py2.py3-none-any.whl (133 kB)
Collecting async-timeout<4.0,>=3.0
Using cached async_timeout-3.0.1-py3-none-any.whl (8.2 kB)
Collecting yarl<2.0,>=1.0
Using cached yarl-1.6.2-cp39-cp39-win_amd64.whl (127 kB)
Collecting attrs>=17.3.0
Using cached attrs-20.2.0-py2.py3-none-any.whl (48 kB)
Collecting idna>=2.0
Using cached idna-2.10-py2.py3-none-any.whl (58 kB)
Using legacy 'setup.py install' for pynacl, since package 'wheel' is not installed.
Using legacy 'setup.py install' for websockets, since package 'wheel' is not installed.
Building wheels for collected packages: multidict
Building wheel for multidict (PEP 517) ... error
ERROR: Command errored out with exit status 1:
command: 'C:\Users\User\AppData\Local\Programs\Python\Python39\python.exe' 'C:\Users\User\AppData\Local\Programs\Python\Python39\lib\site-packages\pip_vendor\pep517_in_process.py' build_wheel 'C:\Users\User\AppData\Local\Temp\tmpvzl6yaej'
cwd: C:\Users\User\AppData\Local\Temp\pip-install-kbvs3y8t\multidict
Complete output (40 lines):

Accellerated build *

running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-3.9
creating build\lib.win-amd64-3.9\multidict
copying multidict_abc.py -> build\lib.win-amd64-3.9\multidict
copying multidict_compat.py -> build\lib.win-amd64-3.9\multidict
copying multidict_multidict_base.py -> build\lib.win-amd64-3.9\multidict
copying multidict_multidict_py.py -> build\lib.win-amd64-3.9\multidict
copying multidict_init_.py -> build\lib.win-amd64-3.9\multidict
running egg_info
writing multidict.egg-info\PKG-INFO
writing dependency_links to multidict.egg-info\dependency_links.txt
writing top-level names to multidict.egg-info\top_level.txt
reading manifest file 'multidict.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '*.pyc' found anywhere in distribution
warning: no previously-included files found matching 'multidict_multidict.html'
warning: no previously-included files found matching 'multidict*.so'
warning: no previously-included files found matching 'multidict*.pyd'
warning: no previously-included files found matching 'multidict*.pyd'
no previously-included directories found matching 'docs_build'
writing manifest file 'multidict.egg-info\SOURCES.txt'
copying multidict_init_.pyi -> build\lib.win-amd64-3.9\multidict
copying multidict_multidict.c -> build\lib.win-amd64-3.9\multidict
copying multidict\py.typed -> build\lib.win-amd64-3.9\multidict
creating build\lib.win-amd64-3.9\multidict_multilib
copying multidict_multilib\defs.h -> build\lib.win-amd64-3.9\multidict_multilib
copying multidict_multilib\dict.h -> build\lib.win-amd64-3.9\multidict_multilib
copying multidict_multilib\istr.h -> build\lib.win-amd64-3.9\multidict_multilib
copying multidict_multilib\iter.h -> build\lib.win-amd64-3.9\multidict_multilib
copying multidict_multilib\pair_list.h -> build\lib.win-amd64-3.9\multidict_multilib
copying multidict_multilib\views.h -> build\lib.win-amd64-3.9\multidict_multilib
running build_ext
building 'multidict._multidict' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
ERROR: Failed building wheel for multidict
Failed to build multidict
ERROR: Could not build wheels for multidict which use PEP 517 and cannot be installed directly
[CRITICAL] launcher: You may need to run as admin to install dependencies.
[INFO] launcher: All done.
C:\Users\User\OneDrive\Documents\GitHub\MusicBot>
Steps to reproduce

i don,t know what should i do plzz help

Log file
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here. If you do not include your log file, you WILL be asked to provide one.
musicbot.log

We do not support Python 30.9, please downgrade to 3.7.


Error with latest neovim and dein.vim

When i run my nvim i got this one:
no notification handler registered for "/Users/cellinho/.vim/.dein/rplugin/python3/deoplete:function:_deoplete"
i reinstalled neovim and dein.vim i didn't work for me please help. thanks.

I was dumbass the path was totally wrong.

I cannot reproduce it in the latest neovim.
Please update it to the latest version.

I think you should kill the python process or reboot your machine.
The old Python process seem alives.

https://github.com/neovim/neovim/pull/4599


Set the workflow instance ready state to running in failover

Purpose of the pull request
close #15573
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

hi @ruanwenjun If do this, the historical state added in the method  processServiceImpl#constructProcessInstance will be different from the actual one. Can I modify the command_type of Recover_Tolerance_fault_process in the method `` processServiceImpl#constructProcessInstance``` to solve this problem?

LGTM

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (43a0652) 38.36% compared to head (8728ed5) 38.36%.

:exclamation: Current head 8728ed5 differs from pull request most recent head 28d30a6. Consider uploading reports for the commit 28d30a6 to get more accurate results

Files
Patch %
Lines

...nscheduler/service/process/ProcessServiceImpl.java
0.00%
1 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##                dev   #15572      +/-   ##
============================================
- Coverage     38.36%   38.36%   -0.01%
  Complexity     4744     4744
============================================
  Files          1305     1305
  Lines         44830    44797      -33
  Branches       4803     4782      -21
============================================
- Hits          17200    17186      -14
+ Misses        25759    25739      -20
- Partials       1871     1872       +1

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


Prev/Next button on remote do nothing in leanback mode

When using the SDK in leanback mode the prev/next buttons on the remote do nothing. They should behave same as the onscreen buttons. Note that this is required for Amazon certification
To Reproduce:

Play a video in leanback mode
Press "Next" on the remote

Expected:
Same as selecting the next button in leanback UI and pressing "enter" (skip ~10secs)
Actual
Nothing happens
Tested on

Fire OS <IP_ADDRESS>
Android TV Emulator (Android 8)

Hi @toto ,
thanks for your post. Could you please check again with v 3.1.8?
And also please regard the requirement for Android TV (onKeyEvent) in your Player Activity as described in the corresponding section


List of Tables?

Does the List of Figures differentiate between the tables and figures list currently? If not, I would like to make an educated guess that it would be very similar to the List of Figures code where figures tag is replaced with the tables tag.
Love the app so far. Thanks for your contribution.

a label manager much like paperpile would be terriffic! Right now I use a notepad tab to keep track of all my labels.

I'm back on this project and will look into creating list of tables soon

List of tables is now released

The documentation doesn't currently with how to use it.
"Cross Reference can create a list of figures akin to Docs' own table of contents. This feature is found under Add-ons→Cross Reference→List of figures. It inserts the list at the cursor or updates the existing list."
I don't have the option "List of figures", only configuration, so no list of figures or tables is inserted. Any tips?

I am facing the same issue as RFRIEDM, I do not see the option "List of figures":


RECOVERY COMPANY TO HIRE WHEN YOU FALL FOR FRUAD  - SPYWARE CYBER

I'm not the only one singing the praises of  Spyware Cyber. Testimonials from satisfied clients speak volumes about the exceptional service and results delivered by these digital wizards. If you ever find yourself in a Bitcoin bind, trust me,Spyware Cyber is the beacon of hope you need in the murky waters of cyberspace. When it comes to recovering lost Bitcoin, it's not all magic spells and wizardry. Expert recovery services like Spyware Cyber often rely on the power of data analysis and forensic investigation to track down missing cryptocurrencies. By digging into transaction histories, wallet addresses, and other digital breadcrumbs, these professionals can uncover clues that lead to the recovery of lost Bitcoin. In the world of cryptocurrency, the blockchain is like a digital paper trail that records every transaction ever made. Recovery specialists at Spyware Cyber harness the power of blockchain tracking to trace the movement of lost Bitcoin. By dissecting the blockchain data and employing sophisticated recovery methods, they can follow the virtual money trail and bring back those elusive Bitcoins to their rightful owners. To prevent the heart-wrenching experience of losing your Bitcoin, it's crucial to secure your digital wallet with best practices. This includes using strong passwords, enabling two-factor authentication, and storing backups in secure locations. By taking proactive steps to protect your Bitcoin wallet, you can significantly reduce the risk of loss or theft. In the volatile world of cryptocurrency, risks are as common as memes on Reddit. To safeguard your investments, consider implementing risk mitigation strategies such as diversifying your holdings and setting up contingency plans in case of emergencies. Having backup plans in place can provide peace of mind and ensure that you're prepared for any crypto curveballs that come your way. In the wild west of the cryptocurrency world, lost Bitcoin can feel like a modern-day treasure hunt. Recovery services like Spyware Cyber play a crucial role in navigating the digital wilderness and helping crypto enthusiasts reclaim their lost fortunes. By combining cutting-edge techniques with a sprinkle of magic, these experts showcase the value of their skills in recovering valuable assets in the cryptoverse. So, if you find yourself in a Bitcoin bind, remember that expert help is just a wand wave away.
<EMAIL_ADDRESS>Telegram:Spyware Cyber
Website:https://cybegal.net

Let's kick things off by showing some love to the unsung heroes of the digital world - the wizards at TECHNOCRATE RECOVERY. These folks deserve a round of applause for their magical skills in helping folks like us recover lost treasures in the form of Bitcoin. Trust me, they're the real MVPs. You wake up one day, log into your Bitcoin wallet, and realize that your precious digital coins have vanished into thin air. Panic sets in, and you're left wondering if there's any way to reclaim what's rightfully yours. That's where TECHNOCRATE RECOVERY swoops in with their capes fluttering, ready to save the day! Now, you might be thinking, "It's just virtual money, what's the big deal?" Well, hold on to your hats because losing Bitcoin is no joke. It's not just about the money but also the principle of retaining ownership of your assets in the wild west of the internet. Plus, who wouldn't want a chance to turn those lost coins into real-world treasures? Think of Bitcoin recovery as a digital scavenger hunt with high stakes. It's not just about finding lost coins; it's about reclaiming your autonomy in the ever-evolving realm of cryptocurrency. So, if you've lost your Bitcoin, don't lose hope - the wizards are here to sprinkle some magic dust on your digital conundrum! What sets TECHNOCRATE RECOVERY apart from your average tech wizards is their laser-focused expertise in the art of recovering lost Bitcoin. These folks have honed their skills to perfection, making them the go-to gurus for all things related to digital asset recovery. Behind every successful recovery story is a team of brilliant minds working tirelessly to make it happen. The wizards at TECHNOCRATE RECOVERY are no exception. With a blend of technical expertise, problem-solving prowess, and a touch of magic, they're the dream team you want on your side when the digital chips are down. Now, let me take you on a journey through my own rollercoaster ride with TECHNOCRATE RECOVERY. Spoiler alert: It ends with a pot of digital gold at the end of the rainbow! It all started with a desperate email to TECHNOCRATE RECOVERY, outlining my woes of lost Bitcoin and praying for a miracle. The response was swift, the assessment thorough, and I knew I was in good hands with these modern-day magicians. As the recovery process unfolded, I witnessed firsthand the dedication and expertise of the TECHNOCRATE RECOVERY team. It was like watching a high-stakes heist movie, but with a happy ending where the good guys win, and I walk away with my recovered Bitcoin securely back in my digital wallet. Do contact TECHNOCRATE RECOVERY on:
EXPERTISE CONTACT INFORMATIONS
WEB: w w w.technocraterecovery .site
SEND EMAIL: t e c hnocratrecovery@ contractor(.)net
TELEGRAM: @TECHNOCRATE_RECOVERY

I'm thrilled to share my remarkable experience with Trek Tech Corp and how they came to my rescue when I lost $210,000.00 USD in Bitcoin due to a scam. Initially feeling hopeless, Trek Tech Corp stepped in and tirelessly worked to recover my precious cryptocurrency.
Their team of experts demonstrated utmost professionalism, efficiency, and profound knowledge in cryptocurrency recovery. Throughout the process, they maintained clear communication with me, leaving no stone unturned in their endeavor to retrieve my lost funds.
I am profoundly thankful to Trek Tech Corp for their exceptional service and unwavering commitment to assisting individuals like myself in recovering from cryptocurrency scams. I wholeheartedly recommend anyone facing a similar situation to contact Trek Tech Corp via their email addresses<EMAIL_ADDRESS>/<EMAIL_ADDRESS>Trust me, they are genuine experts who will spare no effort to help you reclaim your lost funds.
Trek Tech Corp truly stands out as the premier Cryptocurrency Recovery Expert.


pre-trained model

Thanks for your work！Could you please share a pre-trained model? Thank you very much.

hi, you can find and download the pretrained model on the Readmd.md
thank you!


Add SourceSocket

The Windows only counterpart to SourceFd.
All commits in #1182 are in the pr as well.
Updates #880.

The CI will fail with the same failure as in #1182.

I'll try to redo this at some point when I have some time.


Firebase corrupts UserProfile.PhotoUrl on iOS

Unity editor version: 2018.3.9f1
Firebase Unity SDK version: 5.6.0
Additional SDKs you are using (Facebook, AdMob, etc.): No
Platform you are using the Unity editor on (Mac, Windows, or Linux): Mac
Platform you are targeting (iOS, Android, and/or desktop): iOS
The following problem happens on iOS device, in Mac Editor there is no such problem.
I am trying to change user profile picture.

I upload picture to FirebaseStorage and receive a valid download Uri like this: https://firebasestorage.googleapis.com/v0/b/payback-app-ad5e5.appspot.com/o/XUURz6wN5BVmtKJCH3KmIPCCm7C3%2Fprofile_picture.jpg?alt=media&token=0bb2585b-446e-40d8-8708-f69cba23dffa
Then I wish to update user's UserProfile with Uri to the new picture:

var profile = new UserProfile();
profile.PhotoUrl = downloadUri; // downloadUri is valid
user.UpdateUserProfileAsync(profile);

Next time I'm accessing FirebaseAuth.DefaultInstance.CurrentUser.PhotoUrl I am getting corrupted (escaped?) Uri:
https://firebasestorage.googleapis.com/v0/b/payback-app-ad5e5.appspot.com/o/XUURz6wN5BVmtKJCH3KmIPCCm7C3%252Fprofile_picture.jpg?alt=media&token=0bb2585b-446e-40d8-8708-f69cba23dffa

Which leads me to 404 error page

Problem: after going through UserProfile update process Uri now includes extra characters (52 in the above case).
Current workaround for me is to store user's photoUrl separately in Realtime Database.

@GeorgeFedoseev
Thank you for reporting this issue.
I think the problem is that profile.PhotoUrl setter converts the uri incorrectly.
So at the meantime, RT DB would be your best bet.
I'll keep you posted when the fix is released.
Shawn

This bug should be fixed in the 5.7.0 version of the Firebase Unity SDK.
Let us know if you're still experiencing the issue!
--Patrick

Great, I'll check!


correct naming of rosie o'donnel

Don't leave doubt in anyones mind about who Rosie O'donnel is!

Please submit a test file along with this PR to show it working.

See a76f078


[BUG] Gallery does not display properly with flex

Describe the bug
Gallery does not display properly when inside element where display: flex
How to reproduce

      <SfGallery :images="product.images" />

This bug is also appears in the storybook:
https://storybook.storefrontui.io/?path=/story/pages-product--common
Devices

@storefront-ui : 0.7.1
Browser: Version 81.0.4044.113 (Official Build) (64-bit)
OS: Mac OS 10.11.6

@AdamPawlinski please check this issues :)

Just found a quick and dirty fix. I noticed that if window gets resized, SfGallery component now displays correctly. So triggering a resize event just after mounting fixes the problem:
mounted() {
    this.$nextTick(() => {
      window.dispatchEvent(new Event('resize'))
    })
  },

fixed on 0.7.2

visible on the smallest screens

Hi, I'm still experiencing the same problem. Is there a solution yet?
Thanks!

@scferrada  I couldn't reproduce this error, so could please let me know when it appears and what version of SfUI are you using?

@AdamPawlinski  here's my code:

           <SfGallery             :images="images"/>

I have SfUI "0.7.18", the latest found with yarn.
Here's an image of the behaviour (the main image only appears after a resize event):

I'm sorry but still have no idea how to figure it out. Is that happen only on certain browser or system or on all versions?


saveDatabase() error when invoked too quickly

I am writing an app in Node that uses LokiJS.
I am manually calling saveDatabase() every time I insert an object. If I create multiple objects quickly, the saveDatabase method is invoked multiple times in a short period of time and after the first call it complains because it cannot rename the dbName~ file. The problem is that the fs.writeFile and fs.rename (lokijs.js lines 2020 - 2025) are executed asynchronously so in some cases, when the code tries to rename dbname~ to dbname, dbname~ does not exist any longer because it was already renamed in a previous callback.
I fixed the issue by making sure the temp db name is unique by changing lokijs.js line 2019 from:
var tmpdbname = dbname + '~';
to
var tmpdbname = dbname + Date.now();
The way I am calling saveDatabase is not efficient and should probably use the autoSave feature.
The reason I do it this way is because my code does not write often, so I wanted to avoid having the autosave timer function running periodically (though it may be cleaner to do so).
Would you like me to submit a pull request?

Yea loki is mostly synchronous except most persistence adapters are asynchronous (for good reason).  Ideally you would pass a callback to saveDatabase and wait for it to notify you the save was completed.
I think the best way to handle this might be to async throttle database saves to occur only after you have yielded the thread (perhaps as an option?).
We could take this standalone logic :
var db = new loki('test.db');
var coll = db.addCollection('coll');

var saveQueued = false;

function throttleSave() {
  if (saveQueued) return;

  saveQueued = true;

  setTimeout(function() {
    db.saveDatabase(function(err) {
       console.log('save completed');
    });
  }, 1);
}

coll.insert({a:1, b:2});
// this will queue up the save for when we yield thread
throttleSave();

coll.insert({a:2:, b:3});
// this will detect a save is already queued
throttleSave();

// now that we yield thread, our timeout will fire and save (once)

Test it and if needed add it to our Loki.saveDatabase.  So basically you call saveDatabase and keep crunching data and it wont actually save until you are done... at which point the timeout will fire and save once.
If you prefer multiple saves (not sure why but maybe use case) you could clone the LokiFsAdapter and replace all asynchronous filesystem calls with their equivalent synchronous versions.  We do have a few synchronous adapters like LokiLocalStorageAdapter and LokiMemoryAdapter and those would behave as you are expecting our node fs adapter to behave.

Thanks @obeliskos for your reply. I am including a code snippet that triggers the issue I mentioned (my real case involves multiple calls from remote clients, so even if I wait for the db.saveDatabase callback I still get errors due to timing issues as the requests are not serialized):
`
var loki = require('lokijs');
var db = new loki('loki.json');
var children = db.addCollection('children');
var s = 0;
function insert() {
console.log('Inserting: ' + s);
children.insert({name:'' + s, legs: 8});
s++;
db.saveDatabase();
}
for(var i = 0; i < 100; i++) {
setTimeout(insert, 100);
}
`
At the end of the run you get:
/lokijs/src/lokijs.js:2158
throw err;
^
Error: ENOENT: no such file or directory, rename 'loki.json~' -> 'loki.json'
I tried your throttleSave approach and worked. I just had to make a minor change to your code. I added another flag called saveRequested. If you call throttleSave and saveQueued is set, instead of returning, I set saveRequested to true. This way, in the db.saveDatabase callback, if I see someone tried to save while we were saving, I call throttleSave again. Otherwise, there are cases where we don't save the latest version of the Db (I have a code snippet that triggers the error in case you are interested)
I made the changes to the code and had to update some of the tests because they were failing (mostly tests that save and then load the db immediately). Unfortunately I have one test error that I am not able to resolve. Would you mind having a look?
I tried to upload my changes to a new throttlesave branch but I don't have permissions. What is your policy for submitting changes? Should I fork the project first?
Thanks again for your help.

Yes that makes sense if you kick off an async save, yield thread, and (via event?) grab the thread again to modify and save before the first save finished.
Sure go ahead and fork and I will take a look at it... we are in the process of merging changes from master to 2.0.0 so maybe once we finalize your p.r. it can be once that is complete.  At that point we may want to duplicate that fix on newer 2.0.0 version.

Exactly, that was the issue with saving but missing a later update.
Will fork an upload the code into a branch.
BTW, great work with the Db I find it very useful.

Ok, submitted the pull request

@mromanbcn Nice elaboration in the first comment... I'm facing the same issue

Thanks @ohenepee. I have been working with @obeliskos and we are almost done with a set of changes that will fix the issue. The pull request is almost ready

Described now in wiki here :
https://github.com/techfort/LokiJS/wiki/LokiJS-persistence-and-adapters#high-frequency-save-throttling

Thanks @obeliskos!

@obeliskos, when do you plan to release a new package (1.4.3?) with the new throttle save functionality?
Thanks

techfort will do a release whenever he finds time and we bug him enough...  I would think we would give people a chance to test out a week or so and I will need to update a few tests / jsdocs but we can look to do it after then

Fair enough, I agree about the testing. I will update my package.json so I use the latest git version for now and then will use the release version when it comes out

I have updated the throttling wiki entry to cover new additions I just made.
Basically I was adding unit tests and figured I would add method to wait for queue to drain.
Then I figured I would add that logic to loadDatabase (to wait for save queue to drain) to turn this into more of a high level contention management that works within a single loki instance.  Multiple loki databases saving to the same file or multiple node processes saving to the same file can still conflict with each other, but with a single loki instance this should be managed to avoid conflict.
This option is made default for upcoming 1.43 release, anyone wishing to report any issues with latest master src, feel free to report before we update npm and releases.

I just experienced this issue, it seems like it solved my problem, Looking forward for the release.
in the mean time working with master

techfort released 1.4.3 today, so npm has this now


Boilerplate: Update to 5fea264b458ec33913afb04eda6ff87d8013d9f4

Conventions:

openshift/golang-osd-operator: Update

https://github.com/openshift/boilerplate/compare/180f2994b9c9068136c0ca131cb3bf8bb1a23e96...5fea264b458ec33913afb04eda6ff87d8013d9f4
commit: e6753c2a4252695328187dad83370e63f308e355
author: Christopher Collins
Updates the version of the openshift-operator-registry image
Updates the version of the openshift-operator-registry image to 4.8.0,
to address several high vulnerabilities found in the 4.7.0 image.
 Fix up the test (case & project) accordingly.
Also add test loops for missing supported asdk versions. Not sure when
we missed those.
Also fix the backing image -- it was hacking the go lib/cache
permissions too early.
Also make it possible to override the backing image used by
container-make, to ease debugging when writing commits like this.
commit: 0acfc9d8d31942977df26f49ec043038d2fd3320
author: Rob Rati
Update to use golang 1.16
commit: c49cf6f755ffab5c6e2ce6e4118b743e83093248
author: Eric Fried
Fix unbound local variable error
...noted in https://ci.int.devshift.net/job/app-sre-deployment-validation-operator-gh-build-master/60/console
commit: 3bcb750bd6dc9120f5458aa44d82fff6973d2171
author: Eric Fried
Improve subscriber report release
This commit improves the subscriber report release tool in the
following ways:

It now requires a list of subscribers, or ALL, with the same
semantics as subscriber propose update.
It now produces a diff with which you can patch -R what's in the
release repository to make it conform.

commit: 9062716c4df7b01b72ba4308e106b4c932ab5649
author: Christopher Collins
Adds .gitattributes to unacceptable_deltas "ignores" list
With a recent update to boilerplate, a .gitattributes file is created
during the bootstrap process.  This is causing failures in the
"framework/04-update-from-master-and-revert" test, which currently
doesn't expect the .gitattributes file to exist, uncommitted, after the
test bootstrap.
This adds the .gitattributes file to the "ignores" list in the
unacceptable_deltas function of boilerplate/update.
Also runs ./boilerplate/_lib/boilerplate-commit to "clean" before the
next test run.
Signed-off-by: Christopher Collins<EMAIL_ADDRESS>

lgtm from boilerplate.
Reviewers, please note the two significant changes here:

Your operator will build against go 1.16 (was: 1.13)
Your OLM catalog will build against registry 4.8 (was: 4.7.0)

/lgtm


modify using localtime for retrieving modified domains

Problem
ZMS uses MySQL Connector/J for DB connections. MySQL Connector/J converted to DB's time zone until 5.x, but from 8.x, it doesn't convert to DB's time zone.

5.x (expected behavior): MySQL Connector/J converts GMT to JST when the DB time zone is JST.
8.x (Unintended behavior): MySQL Connector/J will not convert GMT even if the DB time zone is JST

When retrieving modified domains from database server, ZMS generates the query with GMT, but the time zone of database is not GMT, so I cannot retrieve modified domains.
Is there any way to convert GMT to localtime when retrieving modified domains?
Fix
This is an idea to solve this problem.

For example, is it necessary to use a calendar object in the following code?https://github.com/yahoo/athenz/blob/8a2db8f8407c21e706048594e827d2f2ddeaa6d4/servers/zms/src/main/java/com/yahoo/athenz/zms/store/jdbc/JDBCConnection.java#L3819

For example, is it necessary to use a calendar object in the following code?
https://github.com/yahoo/athenz/blob/8a2db8f8407c21e706048594e827d2f2ddeaa6d4/servers/zms/src/main/java/com/yahoo/athenz/zms/store/jdbc/JDBCConnection.java#L3819

the value on line must match the value set on the following one:
https://github.com/yahoo/athenz/blob/8a2db8f8407c21e706048594e827d2f2ddeaa6d4/servers/zms/src/main/java/com/yahoo/athenz/zms/store/jdbc/JDBCConnection.java#L3879
because you might have multiple servers sending notifications, you want one server to mark some as its own and then process them - this is how we use the timestamp and server attributes. so it's not necessary to use the calendar object but those two lines must match.


[Android] Native stack navigator crashes on quick transitions

I've been recently testing new react-navigation v5 with native navigation stack and it works fine in most cases but when I start moving quickly between the screens eventually app crashes. Here is a sample video and stack trace that I got in Android Studio.
2020-02-07 13:49:14.511 11275-11275/com.reactnavigationrnd E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.reactnavigationrnd, PID: 11275
    java.lang.IllegalStateException: Restarter must be created only during owner's initialization stage
        at androidx.savedstate.SavedStateRegistryController.performRestore(SavedStateRegistryController.java:58)
        at androidx.fragment.app.Fragment.performCreate(Fragment.java:2585)
        at androidx.fragment.app.FragmentManagerImpl.moveToState(FragmentManagerImpl.java:838)
        at androidx.fragment.app.FragmentManagerImpl.addAddedFragments(FragmentManagerImpl.java:2100)
        at androidx.fragment.app.FragmentManagerImpl.executeOpsTogether(FragmentManagerImpl.java:1874)
        at androidx.fragment.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManagerImpl.java:1830)
        at androidx.fragment.app.FragmentManagerImpl.execPendingActions(FragmentManagerImpl.java:1727)
        at androidx.fragment.app.FragmentManagerImpl$2.run(FragmentManagerImpl.java:150)
        at android.os.Handler.handleCallback(Handler.java:883)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:214)
        at android.app.ActivityThread.main(ActivityThread.java:7356)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)

We have same issue. Any idea where to start looking in the source code?

Thanks @kantorm for reporting this. Would be great if you could link a workable app that I could run to reproduce this problem.

@kmagiera here is the repo: https://github.com/armata007/rn-screens-issue-back-project if you have any issues reproducing let me know

@kmagiera here is a snack with a code that produced this error. For me, it was much easier to reproduce on an emulator than a real device.
https://snack.expo.io/@kantorm/d12b36

Thank you all for your reports and comments. This issue has been resolved as of 2.0-beta.6. Please give it a try and if you still experience the issue, comment here or start a new one.


Add API docs

Description

Adds the skeleton of the API docs that will be rendered on the NeMo Framework User Guide. Some existing docstrings are outdated or incomplete, but those will be addressed in another PR. I did modify a few though to see how they would render on the autodoc output, so that's why a few random files have been changed.
Usage

N/A
Checklist

[x] I am familiar with the Contributing Guide.
[x] New or Existing tests cover these changes.
[x] The documentation is up to date with these changes.

Thanks @sarahyurick. I think I addressed all your comments.


Read-only View

Issue
Resolves #377
What was done

[x] Disallow access to any post, put or delete endpoint in read only view
[x] Disallow access to get endpoints in read only view that have a requested date other than today
[x] Disable UI for editing a space in read only view

How to test

Go to a space not in your space dashboard
Make sure you cannot edit that space in anyway
Make sure you cannot view data for dates other than today

FOR DEVS
Feature URL: See feature branch
FOR APPROVAL
Approval URL: See Approval branch

Merged https://github.com/FordLabs/PeopleMover/pull/580 into stage, then reverted because of caching issues. Will merge this back in once those caching issues are resolved.


Updates for React Native 0.60

update *Dependencies in generated package.json - update not needed since generated package.json already has a range that covered 0.60; it is desired to drop support for 0.59 when it is not needed someday in the future
[x] use a newer Android tools version such as 3.4.1 in build.gradle (as proposed in PR #24)
[x] test without —view option on iOS & Android
[x] test with —view option on iOS & Android

Note that use with React Native 0.60 is not yet expected to work with react-native-windows, which seems to be stuck on 0.58 for .NET and 0.59 for C++ 0.59 for both .NET and C++ (see #23) or Expo.

Closing as resolved


ADD ISSUE_TEMPLATE

Hello there,
I would like to add an issue template for your repository. This template would have four issues namely bug, documentation, feature, proposal. Kindly assign me this issue as a part of DWOC.
THANK YOU

Not required

Not required


merge package template from arlac77/npm-package-template

.npmignore

chore(npm): update .npmignore from template

Coverage remained the same at 85.014% when pulling 02366a3a717d3d533b175c3fcbaa2b9b36ad523e on template-sync-1 into a0e50f5dae9c8da8a3c30563c1f4b8b4c84f548b on master.

Codecov Report

Merging #54 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #54   +/-   ##
=======================================
  Coverage   84.21%   84.21%
=======================================
  Files          19       19
  Lines         304      304
=======================================
  Hits          256      256
  Misses         48       48

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 a0e50f5...02366a3. Read the comment docs.


fix:[PLG-287]Single Shipper installer/job changes

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List
any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Chore (no code changes)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also
list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] My commit message/PR follows the contribution guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] 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

Other information:
List any documentation updates that are needed for the Wiki

LGTM @AnandPaladin please next time fill the description section. Check proper boxes, add couple words about what has been changed and why. And if when review PRs and see that description is bad - comment about it and encourage others to do such thing :)

Sure @mkinchin-paladin  thanks for valuable feedback

I will raise another PR


FTPS support

Is FTPS support available and if not, can it be added?

Yes, FTPS support already exists. SFTP support however, requires a different module (e.g. ssh2).

Thanks!

I would like to add that the options "secureOptions" isn't documented very well. I don't know the internals of it or what parameters we can pass to it, can that be expanded? See also ref issue https://github.com/mscdex/node-ftp/issues/153

ok, sorry, found it: https://nodejs.org/api/tls.html#tls_tls_connect_options_callback


No instructions to install private extensions

I am developing a new extension, and it's still private until I finish the development. I'd like to install it on a Server instance so I can test on that environment. However, following the instructions above get me stuck just after clicking "Get" on the marketplace page. It shows a never-ending loading indicator.
Is this an issue, or is there any limitations to installing private extensions?

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

ID: 46849bf5-07ed-62cd-66a5-2ebabe449855
Version Independent ID: d12ad05e-4348-f13a-ea35-7bb4761c3b0b
Content: Install extensions for on-premises servers - Azure DevOps
Content Source: docs/marketplace/get-tfs-extensions.md
Product: devops
Technology: devops-marketplace
GitHub Login: @chcomley
Microsoft Alias: chcomley

@ez-ms Thank you for the question.
You can refer to Why can't I install extensions? in the FAQ for possible solutions, or find additional information here and/or by running through the extensions quickstart.
Please note our support options provided in the documentation forum are limited to the provided scenarios.
For additional support, please see:

Azure DevOps Support
Azure DevOps on StackOverflow

Having the same issue, never ending loading when trying to install private extension on a premise server. I am able to install public extensions fine.


IPNS and DNSLink fail to load in the explore tab

Describe the bug
When typing things like /ipns/k51..., /ipns/ipfs.io into the browse/inspect bar if you hit inspect it'll take you to the explore page and will error.
This bug might be related to explore.ipld.io more than here, but since we depend on similar components I'm filing here. Feel free to move or redirect.
There are a variety of errors depending on the mutable identifier type:

/ipns/k51... -> Error: No resolver found for codec "libp2p-key"
/ipns/12D3... -> HTTPError: invalid path "12D3K...": selected encoding not supported
/ipns/Qm... -> Seems to hang/break things (but could be mistaken)
/ipns/ipfs.io -> Error: invalid character '.' in 'ipfs.io'

To Reproduce
Steps to reproduce the behavior:

Go to Status Page
Click on Browse bar
Type in one of the paths above and click the Inspect button
See error

Expected behavior
IPNS resolution should work (i.e. resolve the IPNS path to the IPFS path and continue as normal). Alternatively some error like "IPNS not supported" would work and turn the rest of this into a feature request.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windowsd 10
Browser: Chrome
Version 96

This is a sensible feature.
At the very minimum, anything other than CID or /ipfs/CID/... should get resolved to an immutable content path.

related: https://github.com/ipfs/ipfs-webui/issues/1076

closing in favor of https://github.com/ipfs/ipld-explorer-components/issues/400


指定地区为日本无法获取到云服务器

日志提示：
{"name":"alispot","hostname":"DESKTOP-IA9P0NV","pid":16140,"level":60,"err":{"message":"The resource is out of stock in the specified zone. Please try other types, or choose other regions and zones., URL: https://ecs.ap-northeast-1.aliyuncs.com/","name":"OperationDenied.NoStockError","stack":"OperationDenied.NoStockError: The resource is out of stock in the specified zone. Please try other types, or choose other regions and zones., URL: https://ecs.ap-northeast-1.aliyuncs.com/\n    at httpx.request.then.then (C:\ShadowsocksR-4.7.0-win\node_modules\@alicloud\pop-core\lib\rpc.js:205:19)\n    at process._tickCallback (internal/process/next_tick.js:68:7)","code":"OperationDenied.NoStock"},"msg":"The resource is out of stock in the specified zone. Please try other types, or choose other regions and zones., URL: https://ecs.ap-northeast-1.aliyuncs.com/","time":"2020-10-29T05:55:02.995Z","v":0}

那个1核1G的实例不是在所有地区节点都有的，不过我看最近上线了一种新的1核1G机型，也可能当地有，你可以手动登阿里云后台看下该地域是否有其它合适的实例类型ID，然后修改config.json的以下字段
"InstanceType": "ecs.xn4.small"

确实是没有那种类型的机器了，所以我修改了"InstanceType": "ecs.xn4.small"为"InstanceType": "ecs.t5-c1m1.large"阿里云显示有的，
但是出现{"name":"alispot","hostname":"DESKTOP-IA9P0NV","pid":12056,"level":60,"err":{"message":"Specified CIDR block overlapped with other subnets., URL: https://ecs.ap-northeast-1.aliyuncs.com/","name":"InvalidCidrBlock.OverlappedError","stack":"InvalidCidrBlock.OverlappedError: Specified CIDR block overlapped with other subnets., URL: https://ecs.ap-northeast-1.aliyuncs.com/\n    at httpx.request.then.then (C:\ShadowsocksR-4.7.0-win\node_modules\@alicloud\pop-core\lib\rpc.js:205:19)\n    at process._tickCallback (internal/process/next_tick.js:68:7)","code":"InvalidCidrBlock.Overlapped"},"msg":"Specified CIDR block overlapped with other subnets., URL: https://ecs.ap-northeast-1.aliyuncs.com/","time":"2020-10-29T06:28:35.007Z","v":0}

这个我还真没见到过，可能是重复调用CreateVpc了，你可以登上去把脚本创建的VPC和安全组都删掉，再试试

你说的是对的， 现在已经可以成功启动了


:bug: [#711] Don't reuse cache for differently configured class finder instances

Context: #711
/cc @oprypkhantc @SCIF

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

Project coverage is 95.19%. Comparing base (53f9d49) to head (edb14f5).
Report is 95 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #712      +/-   ##
============================================
- Coverage     95.72%   95.19%   -0.54%
- Complexity     1773     1826      +53
============================================
  Files           154      174      +20
  Lines          4586     4933     +347
============================================
+ Hits           4390     4696     +306
- Misses          196      237      +41

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles

Makes sense; I thought to add something of the kind, but didn't think there was a real use case for that.


Update New Relic stubs to extension >= 9.8

Extensive (90%+) reworking of the New Relic stub:  PHP 8 return types and parameter typing; updated link URIs; added "since" annotations; copy new documentation phrasing from New Relic website; add additional function definitions for newer extensions versions; deprecate functions as needed.

The errors are for an extension-defined class: https://docs.newrelic.com/docs/agents/php-agent/php-agent-api/newreliccreatedistributedtracepayload-php-agent-api/#return-values
Should I define that class in the docs too to prevent this error?

Qodana complained about a deprecated class that is supposed to be deprecated. Looks like it still passes.

Also tests say that StubsMap should be regenerated (docker-compose -f docker-compose.yml run php /usr/local/bin/php /opt/project/phpstorm-stubs/generate-stub-map)

Also tests say that StubsMap should be regenerated (docker-compose -f docker-compose.yml run php /usr/local/bin/php /opt/project/phpstorm-stubs/generate-stub-map)

Ah, yes. I put in the new class and forgot to rerun that.
As well as reordering of functions I guess and that's really pity :( Review changes is much harder now. May be it's possible to move DistributedTracePayload to the bottom of file and restore old order of functions to avoid 100% git change?
Let me give that a try.

@isfedorov I put everything back in order, but it only helps some. newrelic_notice_error() had such an extensive rewrite that git did that wonderful "shift everything down" change that makes it pretty difficult to follow after that. All new functions and the class are at the end. Looking at the C code for the class, I can't see any explicit deprecation, so I removed that notice. The function that returns that class is still deprecated, just not the class itself.

@MarkG-IEL thank you for the update! At the first glance it's actually better now.


Python automatically associated with the use of tab key to complement when an error occurred

This issue has been moved from a ticket on Developer Community.

[severity:It bothers me. A fix would be nice]
Sometimes automatic complement can not be associated, sometimes automatic association after the use of tab key to complement when there is an error. For more information, see the video
The code is as follows:
import datetime
print ('Current year:'str')

[2021-10-07-22-06-55.mp4] (https://aka.ms/dc/file?name=Bdefa1f61ed7a41a4995f11515d10d698637692126431676415_2021-10-07-22-06-55.mp4&tid=defa1f61ed7a41a4995f11515d10d698637692126431676415)
Visual studio 2019 version number used: 16.11.4

Original Comments
Feedback Bot on 10/8/2021, 03:27 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Original Solutions
(no solutions)

Hi there, could you verify if you are still experiencing the same issue on VS2022? Thanks! 😊

Going to close this out. If the issue still persists, please reopen with the information requested. Thanks😊


Naresh

Added Issues Addressed Analysis under Analytics for base pages

base_home.html
2.Dashboard_Extension.html

@manushah17
Also added new commit with changes in following files
1.home/Issueaddressanalaysis.html
2.home/register_tags.py
3.home/views.py
4.unocpi/sqlfiles.py

@manushah17  @dmishra2904
Please Merge this PULL Request after accepting Model changes from Devanshika as I send  our Model changes are sent to Devanshika

merged changes,


Different intervals between iOS and Android devices

We're currently using the cordova-background-geolocation-services plugin within OutSystems (https://www.outsystems.com/forge/component/1623/background-location-plugin/). So far this is working out well for us, however on Android devices we see different behaviour when compared to iOS devices. On iOS devices intervals are happening every 900 seconds, on several tested Android devices the intervals range between 0 and approx. 400 seconds. Furthermore when an Android device is not being used for a longer period (for example during nighttime) intervals are about 15000 seconds.
I've traced this down to the configure block which takes several parameters ($parameters being the name of global variables being passed to this block of code):
//Configure Plugin
window.plugins.backgroundLocationServices.configure({
//Both
desiredAccuracy: $parameters.desiredAccuracy, // Desired Accuracy of the location updates (lower means more accurate but more battery consumption)
distanceFilter: $parameters.distanceFilter, // (Meters) How far you must move from the last point to trigger a location update
debug: $parameters.debug, // <-- Enable to show visual indications when you receive a background location update
interval: $parameters.interval, // (Milliseconds) Requested Interval in between location updates.
useActivityDetection: $parameters.useActivityDetection, // Uses Activitiy detection to shut off gps when you are still (Greatly enhances Battery Life)
//Android Only
notificationTitle: $parameters.notificationTitle, // customize the title of the notification
notificationText: $parameters.notificationText, //customize the text of the notification
fastestInterval:$parameters.fastestInterval // <-- (Milliseconds) Fastest interval your app / server can handle updates
});
interval has a value of 900000 / 60000 (= 15 min / 1 min)
useActivityDetection has a value of False (always)
distanceFilter has a value of 5 / 1
fastestInterval has a value of (same as interval)
If above needs to be clarified I'm willing to provide more details. Thanks in advance for any help provided.

Some additional information in addition to above:

We use the cordova-background-geolocation-services as a plugin in the OutSystems environment
We have seen this behaviour on different Android devices using OS 7 or 8.

If any help can be provided on this issue it would be appreciated.

Just a clarification/updated description: Within our OutSystems application we are using the cordova-background- geolocation-services-plugin. This works well on iOS, where we see a mostly regular interval of 15 minutes between each location update.
However, on Android devices we see different behavior. Here the location updates:

Are between 0 and approx. 1000 seconds.
Only happens when a device is being moved
Do not take place at longer periods of inactivity on the device

We use the following configuration values:
Android and iOS:

desiredAccuracy: 0
distanceFilter: 5
debug: False
interval: 900000
useActivityDetection: False

Android only:

notificationTitle: "Background Location Services"
notificationText: "Tracking"
fastestInterval: 900000

If possible, any help on explaining the erratic behavior on Android would be appreciated.


Fixed small error

[x ] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #d28cc50

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.


Data Browser software architecture diagram

Need
Engineers not familiar with the Data Browser can understand how its software is designed.
Definition of done
Diagram a high-level, "boxes and arrows" overview of the infrastructure and modules that make up the Data Browser.

first draft has been shared

@Bento007 Looks good.


CLOUD-481 1.3.0 release prepwork

Test name
Status

scaling
passed

self-healing
passed

recreate
passed

init-deploy
passed

big-data
passed

scaling-proxysql
passed

storage
passed

demand-backup
passed

self-healing-advanced
failed

upgrade
failed

operator-self-healing
passed

limits
passed

monitoring
passed

upgrade-consistency
passed

one-pod
passed

monitoring-2-0
passed

affinity
passed

auto-tuning
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed


[feat] allow chaining of handle hooks

Hi svelte kit team,
This is my first PR on this wonderful project.
Problem
I tried svelte kit on some internal projects and I noticed something that was missing. It was not possible to compose the handle hook with middlewares.
Middlewares allow to better compose and reuse handlers and ensure Single Responsibility Principle. I noticed that some contributors already built some package to handle cookies, session, auth... (eg: svelte-kit-session) but it is hard to make different modules works together.
Solution
That's why I would like to introduce, in this PR, the concept of middleware.
Now you can write the handle hook like this:
export const handle = [
    ({ request, resolve }) => {
        request.locals.first = true;
        return resolve(request);
    },
    ({ request, resolve }) => {
        request.locals.second = true;
        return resolve(request);
    },
    ({ request, resolve }) => {
        console.log(request.locals); // print { first: true, second: true }
        return resolve(request);
    }
];

Of course, this is an example, a better way would be to separate middlewares in modules like this:
import session from "./middlewares/session";
import auth from "./middlewares/auth";
import i18n from "./middlewares/i18n";

export const handle = [session, auth, i18n];

You can notice that the signature of a middleware is exactly the same as the signature of the handle hook. It allows to use a middleware directly as the handle hook if you do not need to compose it with others middlewares.
Any middleware can respond directly by returning a ServerResponse object. eg:
export default function auth_middleware({ request, resolve }) {
    if (isAuthenticated(request)) {
        return resolve(request);
    }

    return {
        status: 401,
        body: ""
    };
}

UPDATE 1
After some discussion on this PR, the API changed. Now, a sequence method is exported by @sveltejs/kit/hooks. It allows to chain Handle functions.
import { sequence } from '@sveltejs/kit/hooks';

export const handle = sequence(
  ({ request, resolve }) => {
    request.locals.first = true;
    return resolve(request);
  },
  ({ request, resolve }) => {
    request.locals.second = true;
    return resolve(request);
  },
  ({ request, resolve }) => {
    console.log(request.locals); // print { first: true, second: true }
    return resolve(request);
  }
);

Technical details
For now, this implementation has an issue, the middleware code is duplicated in src/runtime/hooks.js and src/build/index.js.
Do you have any idea to avoid this duplication?
Also, I don't have a good understanding of the testing framework in the project. Can you help me writting a test suite?

Before submitting the PR, please make sure you do the following

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[X] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Note: I will add the changeset after changes are reviewed to ensure that the changeset is targetting the good commit

Isn't this the same as calling those functions inside handle?

Isn't this the same as calling those functions inside handle?

That was my initial reaction as well. But I think that it's not quite the same. E.g. what if you want one of the functions to sometimes redirect and sometimes continue on to the next function. I'm not sure you'd be able to easily do that by calling the functions yourself inside handle?

Thank you for your first comments.
@JeanJPNM, This is not the same because a middleware always return a response. How can you ensure that you should respond or continue with the next middleware?
export async function handle({ request, resolve }) {
  const response = middleware({ request, resolve });
  // Sould I respond or go to the next middleware?
}
//or
export async function handle({ request, resolve }) {
  const next1 = (request) => middleware2({ request, resolve: next2 });
  const next2 = (request) => middleware3({ request, resolve: next3 });
  const next3 = (request) => resolve(request);

  const response = await middleware1({ request, resolve: next1 });
  return response;
}

@benmccann, you're right, this is different and not so easy to handle it manually as shown above.

@rmunn, you're right, svelte-kit-cookie-session allows you to pass a function to control the next behavior. However, it has to do this because there is no middleware handling in svelte-kit. Moreover, if we assume that all svelte-kit-middleware-like-packages are following the same architecture, it will become very hard to compose them (famous-callback-hell):
export const handle = middleware1({ secret: "s3kr3t" },
  middleware2({ ...options },
    middleware3({ ...options },
      async function ({ request, resolve }) {
        const response = await resolve(request);
        if (response.headers["content-type"] === "text/html") {
          let theme = request.locals.session.data?.theme ?? "light";
          response.body = (response.body as string).replace("%session.theme%", theme);
        }
        return response;
  }
)));

I think something like this would be more apropriate:
export const handle = [
  middleware1,
  middleware2,
  middleware3,
  async function ({ request, resolve }) {
    // ...
  }
];

// Your exemple would become

import { handleSession } from "svelte-kit-cookie-session";
import { handleAuth } from "some-other-library";

export const handle = [
  handleSession({ secret: "s3kr3t" }),
  handleAuth({ authParams: "foo" })
];

Agree that it makes sense to be able to chain handlers. I'm not personally a huge fan of APIs like Handle | Handle[] though — it's better to have a simple, consistent API. We can have our cake and eat it too with something like this:
import { sequence } from 'somewhere';

export const handle = sequence(
  ({ request, resolve }) => {
    request.locals.first = true;
    return resolve(request);
  },
  ({ request, resolve }) => {
    request.locals.second = true;
    return resolve(request);
  },
  ({ request, resolve }) => {
    console.log(request.locals); // print { first: true, second: true }
    return resolve(request);
  }
);

Or maybe the API looks slightly different:
import { sequence } from 'somewhere';

export const handle = sequence(
  ({ request }, next) => {
    request.locals.first = true;
    return next();
  },
  ({ request }, next) => {
    request.locals.second = true;
    return next();
  },
  ({ request, resolve }) => {
    console.log(request.locals); // print { first: true, second: true }
    return resolve(request);
  }
);

Perhaps returning nothing from something in the middle is equivalent to calling next():
import { sequence } from 'somewhere';

export const handle = sequence(
  ({ request }) => {
    request.locals.first = true;
  },
  ({ request }) => {
    request.locals.second = true;
  },
  ({ request, resolve }) => {
    console.log(request.locals); // print { first: true, second: true }
    return resolve(request);
  }
);

In other words this can easily be solved in userland today. The real question is whether this is something worth including in Kit itself (import { sequence } from '@sveltejs/kit/hooks'?), and if so what the ideal API is.

The last API suggestion makes the most sense to me

@Rich-Harris, @benmccann, Thank you for your suggestions.
I like the idea of having an utility function exported as part of @sveltejs/kit. It avoids the weird Handle | Handle[] configuration and it avoids duplicating the function. I will try to make changes for this.
I also like the Rich's first and third suggestions but I prefer staying on the first. I think middlewares should have the same signature as a classic Handle to allow them to be used standalone or as part of a sequence depending on your use case.
I will update my PR soon to apply this changes.
Do you agree?

I don't understand the first suggestion. resolve computes the entire page HTML. Why would you be doing that three times? Or does it mean next() the first two and then resolve() the last one? I really wouldn't like that API at all where it means different things at different times

I don't understand the first suggestion. resolve computes the entire page HTML. Why would you be doing that three times? Or does it mean next() the first two and then resolve() the last one? I really wouldn't like that API at all where it means different things at different times

If I'm understanding it correctly, the first suggestion would rely on sequence to set things up so that resolve would essentially mean next() the first two times and resolve() the last time, but the user code wouldn't have to know anything about that. And that, I think, is important, because the fact that it means different things at different times becomes an internal implementation detail. User code just needs to know "Hey, we're handing you a function called resolve, call it when you're done setting things up, and then when it's done you can do things to the result". The user code doesn't need to know, or care, whether that resolve is Svelte-Kit's resolve function, or a middleware function from another layer wrapped around Svelte-Kit's resolve.
Then each layer of the middleware can do its own operation without caring what other layers are doing, and (crucially) there's no way to skip layers by returning early. That way you can't have maliciousMiddleware() doing an early return and skipping the part where securityMiddleware handles the JSON output and strips out any passwords that were missed. (Contrived example, but you get the point). If the API is set up so that you have to either call next() or call resolve(request) depending on where you are in the middleware stack, then there's too much room for error. Even a non-malicious middleware could be written to not call next() on certain classes of errors, but then a higher-level middleware (that could have handled those errors gracefully) gets skipped. So having the API be consistent no matter where you happen to be sitting in the middleware stack is important, IMHO, and I prefer Rich's first API suggestion.

I just updated this PR with two major changes:
First, a sequence function is now exported by the (new) module @sveltejs/kit/hooks. To create a Handle chain, you have to import the module:
import { sequence } from '@sveltejs/kit/hooks';

export const handle = sequence(
  ({ request, resolve }) => {
    request.locals.first = true;
    return resolve(request);
  },
  ({ request, resolve }) => {
    request.locals.second = true;
    return resolve(request);
  },
  ({ request, resolve }) => {
    console.log(request.locals); // print { first: true, second: true }
    return resolve(request);
  }
);

Next, I added a test case packages/kit/test/apps/hooks. For some reason, I can't run it through pnpm test on my computer because of some incompatibility with playwright. I ran it manually and it seems to work well.
Note: I also have an issue with import in my test. It seems that vite is not able to resolve @sveltejs/kit/hooks. I had to import it from the dist folder. Do you have an idea about this?

I don't understand the first suggestion. resolve computes the entire page HTML. Why would you be doing that three times? Or does it mean next() the first two and then resolve() the last one? I really wouldn't like that API at all where it means different things at different times

I think that Handle functions does not have to know if they are executed in a sequence or standalone. They should be interchangeable.

I don't understand the first suggestion. resolve computes the entire page HTML. Why would you be doing that three times? Or does it mean next() the first two and then resolve() the last one?

Yes, resolve() is actually next() in the first two cases.

I really wouldn't like that API at all where it means different things at different times
Simple solution: alias next() to resolve() as a third argument in the sequence. So you would have "best of both world". @SomaticIT what do you think?

Btw, I extracted sequence() for test-purposes and it works like charm! Well done, @SomaticIT!

@benbender
Thank you!
I like your suggestion of having a next method that is a simple alias to resolve(request).
I just made a little improvement of this PR to allow this.
Now, when using the sequence utility, you can:
import { sequence } from '@sveltejs/kit/hooks';

export const handle = sequence(
  ({ request, next }) => {
    request.locals.first = true;
    return next();
  },
  // or
  ({ request, resolve }) => {
    request.locals.second = true;
    return resolve(request);
  },
  // both are same
  ({ request, resolve }) => {
    console.log(request.locals); // print { first: true, second: true }
    return resolve(request);
  }
);

It allows best of both worlds: you can make a Handle that can work independantly or in a sequence by keeping the resolve(request) syntax or you can use the next shortcut when you known you are working in a sequence.
What do you think?

@SomaticIT simply perfect! Exactly what I had in mind.
Will update my "ripoff" of your code later. If there are any issues, I will report them here (even if I don't think so).

@Rich-Harris, thank you for your review, you're totally right. request should always be passed to resolve.
I also removed the next shortcut.

thank you! merged via #2222

Thank you for merging this PR.
I'm happy to have contributed to this wonderful project!


Test: Discover Git Repositories - Unsure how to list all changes again

Testing #161797

I'm in this state and it's unclear how to get back to the view where you see all of the changes in all repos. I was initially thinking that clicking outside of the viewlet would restore that view, but it seems that selection remains within the viewlet and the listing of the single repo's changes is still there.

@andreamah, the "Source Control Repositories" view that contains the list of repositories supports multi-select using either SHIFT or Ctrl. The "Source Control" view will show all the repositories that are selected in the "Source Control Repositories" view.


Support keyboard-interactive authentication

While implementing 2-factor login in my app, I noticed that swift-nio-ssh is missing support for keyboard-interactive authentication. I can create a pull request to add it to the NIOSSHAvailableUserAuthenticationMethods: OptionSet and make the client recognize keyboard-interactive messages. However, I am concerned that this change may cause issues on the server-side. So I created this issue to ask if you have any plans to support keyboard-interactive authentication in the future.

We can absolutely add support for keyboard-interactive authentication. We should implement both sides of the flow, but we don't need to actually have the server do anything so long as it can defer the implementation to the delegate that already exists.

We can absolutely add support for keyboard-interactive authentication. We should implement both sides of the flow, but we don't need to actually have the server do anything so long as it can defer the implementation to the delegate that already exists.

I'm trying to implement keyboard-interactive authentication, but there are some troubles I met
In the SSH standard, message type SSH_MSG_USERAUTH_INFO_REQUEST and SSH_MSG_USERAUTH_PK_OK has the same value 60, reference to https://epaul.github.io/jsch-documentation/javadoc/constant-values.html#com.jcraft.jsch.UserAuth.SSH_MSG_USERAUTH_INFO_REQUEST, but in the implement of readSSHMessage, readUserAuthPKOKMessage will try to read if it's SSH_MSG_USERAUTH_PK_OK and mov readerIndex which will cause SSH_MSG_USERAUTH_INFO_REQUEST does not work
code here
case SSHMessage.UserAuthPKOKMessage.id:
                guard let message = try self.readUserAuthPKOKMessage() else {
                    return nil
                }
                return .userAuthPKOK(message)

what I'm trying is to add code here
case SSHMessage.UserAuthInfoRequestMessage.id:
                guard let message = try self.readUserAuthInfoRequestMessage() else {
                    return nil
                }
                return .userAuthInfoRequest(message)

of course UserAuthPKOKMessage will take care of the flow instead of UserAuthInfoRequestMessage, so there is a conflict need to be solved which will cause a major code modification

Yeah, this will require a substantial chunk of work. It will be necessary to pass some context information into the parser so that it is able to tell what it is likely to be decoding.


Compatibility with JupyterLab 0.32

I got this extension a few weeks back I think. And I recently had to update Jupyterlab to 0.32 but it seems that the theme is no longer compatible.
Is this being addressed (or probably has already been addressed already and I missed this)?

Thanks for the issue - I hadn't noticed the new release.
I had a quick look at the changelog, but it's not obvious yet why the addon's broken. I'll try and take a look sometime this week.


[2] Import SplatNet's JSON format

[ ] Create a column for ID-number on battle2 table like "battle2"."splatnet" to reduce duplicate
[ ] Add fields on the API

[ ] SplatNet's ID-number
[ ] SplatNet's JSON

[ ] JSON parser

Hi I've been playing with the two tools you provided on the homepage. So the result is that I got double * 50 battles. 😭 Will the battle start_time or battle_number be used as something like primary key to reduce duplicate?

Please wait until implementing the "battle2"."splatnet"...

Note: sort order https://github.com/frozenpandaman/splatnet2statink/issues/6