nbsphinx and ipython

Until a month ago we were using our own hacked together sphinx confluence builder extension to publish jupyter notebooks to confluence. We saw that it is natively supported now within this repository in 2.0 so we tried it out, looks like it was able to write the output for our jupyter notebooks but we are getting two warnings now after it writes them.
preparing documents... done
writing output... [ 25%] docking_pipeline/P3DOCK_requests
writing output... [ 33%] docking_pipeline/RNAComposer_requests
...
WARNING: unsupported code language for confluence: ipython3

WARNING: unsupported code language for confluence: ipython2

(Neither of these are being used within our jupyter notebooks, as far as I know)
Not sure if we are missing something with compatibility with this new feature and our notebooks, any advice would be greatly appreciated.
As a side note. I do see that ipython is not supported in confluence builder editor v1 or v2, so can't this new extension just use python as the code block instead?

Unknown off hand what specific directives used will result a final doctree with ipython2 and ipython3 styled code blocks. I would imagine any directive type which would expect to produce an IPython-like block would be the "offending" directive.
While the Confluence builder extension does provide improved support for this third-party extension, I would believe it is still proper that unregistered code types like ipython2 and ipython3 should still generate warnings (since Confluence cannot properly render an interactive Python block). That being said, you do make a good point that for a case such as this, it may be ideal to fallback the "unsupported" Python-like code style to Python (instead of the default none). We may also want to add a generic configuration flag to operate styling in a relaxed/suppressed mode, for users who understand syntax limitations with Confluence, and are fine with whatever appropriate style is used.
For now, you could use the confluence_lang_transform configuration and add the following in your documentation's configuration to convert the IPython styles to a python style:
def translation_override(lang):
    if lang in ['ipython', 'ipython2', 'ipython3']:
        lang = 'python'

    return lang

confluence_lang_transform = translation_override

Thanks, that did the trick. didn't realize that transform override existed till now. Super good to know. Wasn't sure if i should close this ticket or leave it open for the Python fallback piece but feel free to close this issue if you would prefer to have that as a separate ticket.

We can leave this open to as a reference to cleanup the code language types.
A quick overview of the planned changes:

Create an additional code-style dictionary for extra fallback styles -- at the minimum, supporting interactive Python code stylings to fallback to Python code stylings.
When confluence_lang_transform is used, allow the call to support returning a None value to indicate to use the default color mapping.
Investigate the use of Sphinx's suppress_warnings configuration to suppress unknown code language (and maybe other) warnings (if not already supported).

Adjustments outlined in #769 and #770 have been merged into the development tree. These two pull requests cover the above enhancement points made in the previous comment. For users wishing to take advantage of these changes before a release is made, the development version of this extension can be installed.
The following shows an example of suppressing code warnings for projects who may not care about unsupported or non-direct language types:
suppress_warnings = [
    'confluence.unsupported_code_lang',
]

v2.1 is now available on PyPI -- marking as closed.


Go to subtasks 'i' + 's' does not work on Mac/Chrome

On Mac Chrome Version 102.0.5005.115 (Official Build) (x86_64) + version 152. I can hit 'i' to go into the task view, but hitting 's' does not bring the focus to the subtasks.

Hey!  Sorry about that, the shortcuts sheet hadn't been updated to reflect recent changes.  Since Todoist no longer has different sections for these, there is no longer an s shortcut in the task view.
Subtask management from the task view is not currently planned - see discussion in #210


Atom has crashed and now impossible to display it - Unexpected StringWithInterpolations - New v1.46.0

Hi,
Since I have updated my atom (v1.46.0), I have bug (not always) when I create a new file.
Atom has crashed and now, it's impossible to restart it.
When I start Atom, in tools menu of macOS I see "Atom" -> Quit only.
No windows appear.
Version :

Atom    : 1.46.0
Electron: 4.2.7
Chrome  : 69.0.3497.128
Node    : 10.11.0

When I run atom --foreground :
2020-05-07 17:23:04.145 Atom[3607:20657] Syntax error on line 61, column 14: Unexpected StringWithInterpolations 2020-05-07 17:23:04.146 Atom[3607:20657] SyntaxError: Syntax error on line 61, column 14: Unexpected StringWithInterpolations     at transformNode (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/cson-parser/lib/parse.js:214:13)     at Value (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/cson-parser/lib/parse.js:97:12)  [........]
List of my packages :

├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├── packages
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
If I run atom in sudo mode, all it's OK...
Regards

I found the source of the problem
In my config.cson I have plugin for customize my touche bar in MacOS.
In this plugin I have create bouton with label "#{x}". Symbol # in config.cson makes Atom crash at startup.

Hey @deleage-tanguy, thanks for reaching out.
I am glad you were able to resolve the issue :)


Generalize -XepPatchChecks command line parsing

This is a minimal (?) fix for #595. It adds support for:

-XepPatchChecks arguments combining built-in and Refaster rules.
-XepPatchChecks arguments listing multiple Refaster rules.

Open points and questions:

Is this approach acceptable at all?
If so, I'll add some tests.
Right now Refaster is treated specially in both ErrorProneOptions and BaseErrorProneJavaCompiler; a nicer solution would entail making Refaster a first-class citizen. That'd be more work, but if you provide some pointers on the desired "end goal" or boundaries of the design space, I'm willing to have a crack at that, too. (In the context of a separate PR, ideally.)

Rebased the branch and resolved a conflict. What does the Error Prone team think of this approach?

Hi @Stephan202,
Thanks for the PR! I was taking a fresh look at this, it seems like a nice thing to support.
I was trying to think a bit about how this interacts with #947 and #4028, I wonder if we should decide what the semantics should be for #4028 first and then figure out how to make the refaster patch options consistent with that.


Update poster src

Link to related issue (if applicable)
#1335
Summary of proposed changes
Use i.ytimg.com instead of img.youtube.com as poster source. Since the latter sends third-party cookies.
Checklist

[x] Use develop as the base branch
[x] Exclude the gulp build (/dist changes) from the PR
[x] Test on supported browsers

All good now, @sampotts

Perfect! Thanks @ar31an 👍


Create lautech.txt

please can u help us to Ladoke Akintola University of Technolgy....and validate my student<EMAIL_ADDRESS>

Duplicate: #584. Closing.


Cykhash package: Fix recipe (do not use noarch)

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Fixing the recipe as the package is mainly written with Cython (no noarch).

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.

Why are you removing the noarch: python?

@conda-forge-admin , please rerender

@marcelotrevisani Hi! Because, this is a Cython package and I was advised to do so. I asked about this in Gitter a few moments ago: https://gitter.im/conda-forge/conda-forge.github.io
Is this okay?

@marcelotrevisani Hi! Because, this is a Cython package and I was advised to do so. I asked about this in Gitter a few moments ago: https://gitter.im/conda-forge/conda-forge.github.io
Is this okay?

Yes, I just saw that you are using the compilers and cython and I deleted my comment :grimacing:

You will need to rerender the feedstock, I just called the bot, lets wait for it

@marcelotrevisani Okay, good thanks! This is the first time I do these things, so still learning.. So thanks for double-checking! 🙂

@marcelotrevisani Okay, it seems that all the checks passed and the builds were successful. Is it now okay for me to merge this pull request, or should someone from the conda-forge team do it (such as you)? Just trying to understand the full workflow..

You can go ahead and merge it. As you are the maintainer of this project you can merge whenever you are satisfied with the modifications :)

@marcelotrevisani Perfect! Thanks a lot for your help! 💪


Support .XLS(Excel97-2003)

Describe the feature
Describe the feature you requested...
hi,
Is it possible to support lower version of Excel. (*.XLS(Excel97-2003)).
Which edition of ReoGrid is targeted

Windows Form

It is a big project to support the binary format xls file. I appreciate it if anyone can help on this.


Adding an option to pass --extra-arg to clang-tidy

For a header-only library I'm maintaining the clang-tidy checks fail with warnings about c++17 features being used. This is most likely cause by clang-tidy assuming C++14 for the header files (since it's the default). Running clang-tidy manually with  --extra-arg="-std=c++17" fixes (most) problems. You can the library at cda-tum/dd_package#104
Could you add a parameter to cpp-linter to pass along extra arguments to clang-tidy?

sounds reasonable. Does your generated database not have the -std arg in it?

The generated database has the -std flag, but it seems clang-tidy doesn't pick it up automatically for the headers.
Just for completeness, the database for the source files looks like this
cat build/compile_commands.json
[
{
  "directory": "/home/runner/work/dd_package/dd_package/build/test",
  "command": "/usr/bin/clang++-14  -I/home/runner/work/dd_package/dd_package/include -O3 -DNDEBUG -Wall -Wextra -pedantic -fno-math-errno -ffinite-math-only -fno-trapping-math -mtune=native -march=native -std=c++17 -o CMakeFiles/DDPackage_example.dir/main.cpp.o -c /home/runner/work/dd_package/dd_package/test/main.cpp",
  "file": "/home/runner/work/dd_package/dd_package/test/main.cpp"
}, ...


Test goto definition enhancements

[x] any os - @sandy081

#5893
We have improved the go to definition behaviour when a symbol as multiple definitions. When having multiple definitions, make sure that

we reveal the first definition and show the peek window with further definitions
the first definition is the nearest wrt to position and file path
selecting an item in the peek window tree (enter/double-click) reveals that definition and closes the peek window
other peek feature (cmd+click, etc) still work

Done with testing.. it works as expected. Closing.


Problem during build with home-manager.users.kcynk.programs.wezterm.enable = true;

Describe the bug
Problem during build with home-manager.users.kcynk.programs.wezterm.enable = true;
Today after rebuild wezterm can't be compiled and build will fail

Seconding the issue, wezterm currently cannot compile on nixos-unstable.  This is presumably due to Rust Stable 1.80 not being able to compile the code anymore.

duplicate of https://github.com/NixOS/nixpkgs/issues/334650


Importer error

I tried to get Visa data and got an Importer error.

Hi,
This is probably due to this bug  eshaham/israeli-bank-scrapers#602,
Once it is resolved, we will release another version

There issue are fixed in Israel scraper repo..


iOS 8 Crash in SSWAnimator

First, congrats for your great job, iOS 9+ working perfectly. It's a shame that in iOS 8 (8.3.0 and 8.4.0) is crashing sometimes, it would be great if you could have a look at it and help us!
Crash details:
SSWAnimator.m line 114
__33-[SSWAnimator animateTransition:]_block_invoke.70.
Crashed: com.apple.main-thread
0  libobjc.A.dylib                0x1972dfbd0 objc_msgSend + 16
1  UIKit                          0x18a1953a4 -[UINavigationController navigationTransitionView:didEndTransition:fromView:toView:] + 1168
2  UIKit                          0x18a26c5d0 __49-[UINavigationController _startCustomTransition:]_block_invoke + 200
3  UIKit                          0x18a1eaf64 -[_UIViewControllerTransitionContext completeTransition:] + 132
4  21 Buttons                     0x1000b7150 __33-[SSWAnimator animateTransition:]_block_invoke.70 (SSWAnimator.m:114)
5  UIKit                          0x18a100708 -[UIViewAnimationBlockDelegate _didEndBlockAnimation:finished:context:] + 408
6  UIKit                          0x18a100270 -[UIViewAnimationState sendDelegateAnimationDidStop:finished:] + 188
7  UIKit                          0x18a100178 -[UIViewAnimationState animationDidStop:finished:] + 104
8  QuartzCore                     0x189a0962c CA::Layer::run_animation_callbacks(void*) + 296
9  libdispatch.dylib              0x197949954 _dispatch_client_callout + 16
10 libdispatch.dylib              0x19794e20c _dispatch_main_queue_callback_4CF + 1608
11 CoreFoundation                 0x1856077f8 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 12
12 CoreFoundation                 0x1856058a0 __CFRunLoopRun + 1492
13 CoreFoundation                 0x1855312d4 CFRunLoopRunSpecific + 396
14 GraphicsServices               0x18ef8f6fc GSEventRunModal + 168
15 UIKit                          0x18a12ef40 UIApplicationMain + 1488
16 21 Buttons                     0x100232bf8 main (main.m:14)
17 libdyld.dylib                  0x197976a08 start + 4

Thank you. Do you have – by any chance – steps to reproduce this crash on devices with iOS 8?


Proxy Settings for Browsers

We are behind a corporate firewall and browsers use proxy to connect to Internet.
In selenium we generally use profiles and capabilities to setup proxy details.
I see there are options in Gemini to setup capabilities. But there are no clear document on setting up proxy details.
Any suggestions?

@Purus there is no proxy support in gemini.
As a suggestion I may propose this plugin. It establishes ssh connection to some host in a way that all requests for this host:port will be redirected to localhost:localport. Hope this may help.

Closing due to no reaction from contributor: https://github.com/gemini-testing/gemini/blob/master/CONTRIBUTING.md


fix: Misalignment of share image in order fragment

programitically setting the scale type of share button of fragment_order fragment
fixes: #807

The alignment was not missing and there was no problem in fragment order


SkyProperties -> DimensionEffects

Following some confusion about this on Fabricord and with a Fabric API PR, this should be renamed to DimensionEffects.

It's stored in the effects property of the dimension type codec.
It doesn't only apply to the sky and includes other things like fog, cloud height and lighting.
DimensionEffects is to DimensionType what BiomeEffects is to Biome.

In addition to this, DimensionType.skyProperties should be renamed to effects along with any related getters to match the better class name and the serialised name.

Looking at the commit history, this is probably a match between good and misleading when they performed a refactor (we still have such ambiguous names, like AreaHelper that was once nested in NetherPortalBlock)


migrate from xyk to cl pools

tasks:

https://p2pvalidator.atlassian.net/browse/NTRN-516

this PR:

moves current version of reserve contract to a separate file in a dedicated folder;
adds a migration test file which prepares xyk and CL NTRN/ATOM and NTRN/USDC pairs, allocates xyk LP tokens for the reserve contract and processes reserve contract step-by-step migration;
adds helpers for contracts migration and cw20 balance querying.

https://github.com/neutron-org/neutron-tests/actions/runs/5320356880

https://github.com/neutron-org/neutron-tests/actions/runs/5786838812


Handle null fields comparisons in Rules processor

Currently, in Rules processor we allow users to create a rule. One of the conditions that users could could want is field <> null. Since it translates to storm sql under the hood we need to make sure that the rule translates to field is not null rather than field <> null so that it works correctly. Currently, it throws a runtime exception and we are unable to create such rules

Discussed this with @HeartSaVioR and seems that best way to address this is add two more dropdown items to dropdown in Rule creation dialog which says field is NULL and field is not NULL


Is it possible to search using advanced query string?

I'd like to do some advanced search. Is it possible?
Example: 'car -airplane', 'car and bike -motorbike'

This is not currently possible, the query interface is very basic, all the words in the string must be present in a document for the document to match.
I have plans to enable more powerful search queries, but it is something that requires a decent amount of  thought and re-work in the internals of lunr that are not going to land anytime soon I'm afraid.


add code coverage report into PRs

As discussed in PR #415, we should add code coverage reports into PRs as part of the test workflow.
possible implementation with Code Coverage Report:
            - name: Produce the coverage report
              uses: insightsengineering/coverage-action@v2
              with:
		path: coverage.xml
		# Publish the rendered output as a PR comment
		publish: true
		# Create a coverage diff report.
		diff: true
		# Branch to diff against.
		diff-branch: next
		# This is where the coverage reports for the
		# `diff-branch` are stored.
		diff-storage: _xml_coverage_reports
		togglable-report: true

this issue is currently blocked due to bots lack of permissions


Add support for new release commit review requirement bypass

I am labeling it as bug as this is a part of a fix for a bug in our release process.

I've learned a bash feature with this...

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged to master and 3.0 branches. Thank you.

When your work with openssl/tools#115 is merged, this probably needs to be undone in favor of adding --release to all the addrev commands


Fail to install lombok-1.18.14.jar in Eclipse Version: 2020-09 (4.17.0)

The regular process to install lombok in Eclipse (https://projectlombok.org/setup/eclipse) fail .
Works OK with lombok-1.18.12.jar and previous versions.
My environment:

Eclipse installation is done using eclipse-java-2020-09-R-win32-x86_64.zip .
Java installation is done using openjdk-15_windows-x64_bin.zip
The workspace is fresh.
Windows 10

@rspilker @rzwitserloot
The current release version breaks eclipse. The error log shows NoClassDefFoundError: lombok/launch/PatchFixesHider$Transform.
Root cause: https://github.com/rzwitserloot/lombok/commit/1b534d17d39f687d42ebab733327a59c3466a949#r43072163

@rspilker @rzwitserloot
The current release version breaks eclipse. The error log shows NoClassDefFoundError: lombok/launch/PatchFixesHider$Transform.
Root cause: 1b534d1#r43072163

Indeed.....
!ENTRY org.eclipse.core.resources 4 2 2020-10-09 10:23:57.705
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
java.lang.NoClassDefFoundError: lombok/launch/PatchFixesHider$Transform
at org.eclipse.jdt.internal.compiler.parser.Parser.endParse(Parser.java:11685)
at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:12878)
at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:13102)
at org.eclipse.jdt.internal.compiler.parser.Parser.parse(Parser.java:13059)
at org.eclipse.jdt.internal.compiler.parser.Parser.dietParse(Parser.java:11446)
at org.eclipse.jdt.internal.compiler.Compiler.internalBeginToCompile(Compiler.java:850)
at org.eclipse.jdt.internal.compiler.Compiler.beginToCompile(Compiler.java:394)
at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:444)
at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:426)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:386)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.compile(BatchImageBuilder.java:214)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:318)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:79)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:275)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:192)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:832)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:220)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:263)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:316)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:319)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:371)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:392)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:154)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:244)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.lang.ClassNotFoundException: lombok.launch.PatchFixesHider$Transform cannot be found by org.eclipse.jdt.core_3.23.100.v20200916-1304_JAVA15_PATCH
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:516)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:171)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
... 27 more

+1

+1

Hi, confirming this bug. I would just add that this is most probably not specific to a concrete Eclipse or Java version, as I have just tested it with Eclipse 2020-06 and Java 11 with the same results.
Plus a suggestion - as this issue is a show-stopper for Eclipse users, couldn't be the Lombok download page changed, so that it somehow takes this into account? It still offers downloading this broken version without a warning.

Confirmed as well, using Eclipse 2020-09 and Java 11 (also using SonarLint if that even matter).

Confirming, too. Same issue - installed the SonarLint plugin and - boom! My Eclipse setup was screwed. :-(
Uninstalled SonarLint, but the bug remained. Can't open a single Editor-window. :-((
Started Googling and read that newer Lombok-versions (I had originally 1.18.8 installed) should fix the issue. Installed the newest (1.18.14) but still had the issue. Then I read that 1.18.12 did not show the problem and - indeed - with 1.18.12 I am up and running again. YMMV...

@mmoser18, yes, your experience is de-facto confirmed by what is already told in the issue description. :)

Hello Lombok team,
Is there any new development with this pesky bug ?
Regard.

I haven't seen any activity yet from maintainers or our resident bug fixer since the release.
@rspilker @rzwitserloot @Rawi01

Also confirmed this bug for MacOS.

Confirmed as well, using Eclipse 2020-09 and Java 8 in MacOS.

I have same bug with Eclipse 2020-09 and Java 11

Same issue over here:

OpenJDK 11 (Linux)
Eclipse 2020-06
Spring Tool Suite 4.8.0

Same error reported.
Environment used to generate the issue :

macOS Catalina (10.15.5)
Eclipse 2020-06

$ java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_265-b01)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.265-b01, mixed mode)

The workspace is empty without any previous load of binaries.

Confirming this issue on
OS: Windows 10
Eclipse:
Version 2020-09 (4.17.0)
Build id: 20200910-1200
Plugins:
SonarLint 5.4.0
Lombok 1.18.14
Java:
openjdk version "11.0.8" 2020-07-14
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.8+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.8+10, mixed mode)

@biswarup81 and others, I think it's nice that you confirm the bug.
Yet, I think just clicking the "thumbs up" at the issue description and optionally clicking "Subscribe" should by enough if you've got nothing really new to add to help to resolve the issue. I hope you see my point, thanks! :)

Same error reported.
Environment used to generate the issue :

macOS Catalina (10.15.5)
Eclipse 2020-06

$ java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_265-b01)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.265-b01, mixed mode)

The workspace is empty without any previous load of binaries.

Caused by: java.lang.ClassNotFoundException: lombok.launch.PatchFixesHider$Transform cannot be found by org.eclipse.jdt.core_3.22.0.v20200530-2032

Same error reported.
Environment used to generate the issue :

macOS Catalina (10.15.5)
Eclipse 2020-06

$ java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_265-b01)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.265-b01, mixed mode)

The workspace is empty without any previous load of binaries.

Caused by: java.lang.ClassNotFoundException: lombok.launch.PatchFixesHider$Transform cannot be found by org.eclipse.jdt.core_3.22.0.v20200530-2032

After have been seeking for the lombok jars binaries on my Eclipse IDE launcher path : /Applications/Eclipse.app/Contents/Eclipse/ , I finally concluded on delete them to figure out the side effects of an abrupt uninstallation of the malicious plugin, lombok in our case.
Once I did it, I tried to relaunch my eclipse but it went instantly closed without any error message begin reported.

Same error reported.
Environment used to generate the issue :

macOS Catalina (10.15.5)
Eclipse 2020-06

$ java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_265-b01)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.265-b01, mixed mode)

The workspace is empty without any previous load of binaries.

Caused by: java.lang.ClassNotFoundException: lombok.launch.PatchFixesHider$Transform cannot be found by org.eclipse.jdt.core_3.22.0.v20200530-2032

After have been seeking for the lombok jars binaries on my Eclipse IDE launcher path : /Applications/Eclipse.app/Contents/Eclipse/ , I finally concluded on delete them to figure out the side effects of an abrupt uninstallation of the malicious plugin, lombok in our case.
Once I did it, I tried to relaunch my eclipse but it went instantly closed without any error message begin reported.

You can try to uninstall lombok from eclipse using its own installer, it has a Uninstall from my IDE option.

We'll release a new version in a few hours.

The cause of the problem has been identified. We have a boolean to distinguish between Eclipse and ecj, the standalone java compiler. They share most of the code, but Eclipse has some extra features (a user interface for instance).
There was no code to automatically detect what environment was being used. We did have explicit parameters, but they would default to Eclipse.
When we were working on our test infrastructure, we changed that.  Turned out we didn't. We now always use the ecj code, instead of the Eclipse code.
We're working on a solution and new release right now.

We've just releases 1.18.14, that contains a fix for this problem. We've also updated the old versions page, and no longer link to the broken release, and updated the changelog to indocate that 1.18.14 should not be used.

@rspilker , could you also please enable the link https://projectlombok.org/downloads/lombok-1.18.16.jar ?
Thank you!

@Musikolo I've also faced the same problem. So I made wrong issue... 😢

It is working !!!!
Thank you and keep safe.

Yeh, the download link on Lombok page still points to 1.18.14.
I was able to get the latest version from maven central and it seems to be working.
https://search.maven.org/search?q=lombok

https://search.maven.org/remotecontent?filepath=org/projectlombok/lombok/1.18.16/lombok-1.18.16.jar

If anybody find this helpful. I removed even this last version from pom.xml. Installed lombok on my sts, put it in build path, exit, turn on and that removed every possible problem. I userd version 1.18.16 from @rspilker from comment above.

well, here it works!

Now our website serves the right jar file.


Invalid data received for ERC721Storage

Hello, I was rewriting my contract and came across with this issue.
useNft seems to be requesting a uri method which isn't present in ERC721 storage and this results in an error.
Reproduction
Here's the contract code:
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.6;

import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import "hardhat/console.sol";

contract MyNFT is ERC721, Ownable, ERC721URIStorage {
    event Mint(uint256 id);
    event Claim(uint256 id);

    uint256 public constant MAX_TOKENS = 50;

    uint256 private constant PRICE =<PHONE_NUMBER>0000000;

    using SafeMath for uint256;

    using Counters for Counters.Counter;

    Counters.Counter private _tokenIds;

    constructor() ERC721("MyNFT", "MNFT") {}

    function _burn(uint256 tokenId)
        internal
        override(ERC721, ERC721URIStorage)
    {
        super._burn(tokenId);
    }

    function tokenURI(uint256 tokenId)
        public
        view
        override(ERC721, ERC721URIStorage)
        returns (string memory)
    {
        return super.tokenURI(tokenId);
    }

    // Mint an NFT and add URI to it
    function mint(string memory tokenURI_) public onlyOwner returns (uint256) {
        _tokenIds.increment();

        uint256 tokenId = _tokenIds.current();

        _safeMint(msg.sender, tokenId);

        require(tokenId <= MAX_TOKENS, "Sold out!");
        console.log(tokenId);

        _setTokenURI(tokenId, tokenURI_);

        return tokenId;
    }

    // Claim and mint NFT
    function claim(uint256 id) external payable {
        require(msg.value == PRICE, "Claiming an NFT costs 0.05 ETH");
        require(id <= MAX_TOKENS, "Cannot claim non-existent token");

        // Transfer to seller
        safeTransferFrom(address(this), msg.sender, id);

        emit Claim(id);
    }

    // withdraw bobux
    function withdraw() public onlyOwner {
        uint256 balance = address(this).balance;
        payable(msg.sender).transfer(balance);
    }

    function transferTo(address acc, uint256 id) public onlyOwner {
        safeTransferFrom(msg.sender, acc, id);
    }
}

Dapp code:
import React, { useEffect } from 'react'
import { Contract, utils } from 'ethers'
import { useOnboard } from 'use-onboard'
import { useNft, NftProvider } from 'use-nft'

const contractAddress = 'COPY_ADDRESS_FROM_HARDHAT_DEPLOY_SCRIPT'

function NFT() {
  const { loading, error, nft } = useNft(contractAddress, '1')

  console.log(nft)

  // nft.loading is true during load.
  if (loading) return <>Loading…</>

  // nft.error is an Error instance in case of error.

  if (error || !nft) return <>{error.message}</>

  // You can now display the NFT metadata.
  return (

{nft.name}

{nft.description}

Owner: {nft.owner}

Metadata URL: {nft.metadataUrl}

  )
}

const App = () => {
  const { selectWallet, address, isWalletSelected, disconnectWallet, balance, provider } = useOnboard({
    options: {
      networkId: 1337,
      networkName: 'localhost'
    }
  })

  return (

      {
        <button
          onClick={async () => {
            if (isWalletSelected) disconnectWallet()
            else await selectWallet()
          }}
        >
          {isWalletSelected ? 'Disconnect' : 'Connect'}
        </button>
      }

Address: {address}

Balance: {balance} ETH

      {isWalletSelected && provider && (
        <NftProvider
          fetcher={[
            'ethers',
            {
              ethers: { Contract },
              provider
            }
          ]}
        >
          <NFT />
        </NftProvider>
      )}

  )
}

export default App

The error I see:
eth_call
  Contract call:       MyNFT#<unrecognized-selector>
  From:                0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266
  To:                  0x2e13f7644014f6e934e314f0371585845de7b986

  Error: Transaction reverted: function selector was not recognized and there's no fallback function

Workaround
I came up with this function to fetch NFTs:
async function fetchNFTs(provider: Web3Provider, address: string) {
  const signer = provider.getSigner()

  const account = await signer.getAddress()

  const contract = new Contract(contractAddress, abi, provider)

  const balance = await contract.balanceOf(account)

  console.log(balance.toNumber())

  const data = []
  for (let i = 0; i < balance.toNumber(); ++i) {
    let tokenURI = await contract.tokenURI(1)
    data.push(tokenURI)
  }

  return data
}

I used to check with supportsInterface() before calling either tokenURI() or uri(), but it was having a few downsides, see https://github.com/spectrexyz/use-nft/pull/90. I changed the behavior so that both methods are now called in parallel, with the first successful one being accepted.
The failing one should be ignored though: https://github.com/spectrexyz/use-nft/blob/83820bb14cba6d3babe375476cc031e3123610e2/src/fetchers/ethers/standard-nft.tsx#L27-L30
And in this example, the call to tokenURI() should work :thinking:
I’m going to investigate more and let you know!


Add documentation to support beta resources

See #415 for an example of what this looks like in a new Beta Resource


⚠ Jenkins Plugins Artifactory has degraded performance

In 4a181a2, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1404 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 71b0545 after 12 minutes.


[Question] Cann't get task instance log detail

Describe the question
My cluster has 2 worker nodes named ds1,ds2.
After run process, ds1 can get   the task instance log on UI ，but ds2 cann't get log detail  .
I queried the table t_ds_task_instance by the task instance id ,  the file  path to  field log_path  exists on the host .
Which version of DolphinScheduler:
-[1.3.6]
Additional context
Add any other context about the problem here.

Is the logger service started in ds2?

The logger server is running on ds2  , listen port 50051

@usretyn you can check that whether there is firewall or iptalbe rules to stop you accept the connection on 50051 on ds2.
you can check by this:

go the api server's machine
telnet ip_of_ds2 50051.


Fix support for custom control classes in selectfieldset

Fixes https://github.com/ulion/jsonform/issues/20

Cool, thanks.


Custom query parameter

I could go into the details of the issue without thanking the owner(s) of this package for sharing this package with the world! Thanks a lot everyone who contributed!
Here is my issue:
I'm using this package in combination with JWT authentication. Therefore, I need to send a valid authentication token as a request parameter to authenticate the user who is requesting data. However, the RestrictiveQueryChecker does not allow any unrecognized parameters (as they are called in this package) to be part of the query parameters unless I explicitly set $allowUnrecognizedParameters = true. I think this implies that I'm allowing every parameter to be part of the request data which, I guess, defeats the purpose of all other query validations. Is there a way to whitelist only certain query parameters I explicitly allow to be part of the request?

Thanks for the feedback!
I totally agree with the intent of your issue... we also use JWT and have to also set allowUnrecognizedParameters to true. The query parsing is done by the underlying neomerx/json-api package, and that only allows that setting to be true or false.
Note that this does not disable parsing or validation of any of the "official" JSON API query paramets. By "unrecognised parameters", what the neomerx package is referring to is ones that are not in the JSON API spec. So even if you set that to true, the official ones such as filter, page still get processed.
Does that answer the question or were you hoping for something about the implementation to be changed? Just let me know!

I was not aware of the fact the other query validations would still be processed. That is a good thing to hear.
Do you know if allowing unrecognized parameters to be in the request data has security implications?

I don't think it matters because if you get the query parameters from the Laravel request, you'd get them all anyway. It's more a JSON API thing... it's talking about parameters that the encoder won't recognise because they're not in the spec.
Will close this issue for the moment but feel free to ask any more questions!

Great! Thanks for your quick response!


Genesis hash constant & tests for block hash display byte order

Trivial. Strange we hadn't it before

Strange we hadn't it before

We nearly had it ^^ In 2018 I wrote a wayyy too over-engineered constants crate in a futile attempt not to boot Bitcoin clone chains from this library and make it extensible (I was way too lenient with shitcoins back then). As a result it was way over-complicated and in retrospect I'm happy it didn't get integrated. Maybe a second attempt that focuses on BTC and its test/reg/signet would be nice.

I'm not against having a test that parses a random particular hash hex and checks it with the expected binary..
But we definitely shouldn't have the genesis hash as a public constant, it should be just local to the test.

Closing since we indeed have blockdata::constants::genesis_block() which I missed


Analyze Business Seasonals (WeekOfMonth and derivatives)

For business daily data the signal may be better analyzed by crossing dayOfWeek and week index in month.
This can be made by dividing the work month in weeks and analyzing WeekOfMonth.
WeekOfMonth = dayOfMonth * // 7
(This is only an approximation, not to be confused with WeekOfYear, which is already analyzed by PyAF)
An important derivative is DayOfNthWeekOfMonth, a crossing of DayOfWeek and WeekOfMonth
DayOfNthWeekOfMonth = WeekOfMonth * 7 + DayOfWeek
This pattern captures concepts like 'first Monday of month' , 'last Tuesday' etc.

Check if this can capture religious holidays (Easter , Holy Week etc)

Avoid WeekOfMonth approximation (increasing ordinal values should be guaranteed)
    def get_week_of_month(self, series):
        lFirstDayOfMonth = series - pd.to_timedelta(series.dt.day - 1, unit='D')
        return series.dt.weekofyear - lFirstDayOfMonth.dt.weekofyear + 1

Closing


[main] Format Go code

Cron -knative-prow-robot
/cc knative/productivity-wg-leads
/assign knative/productivity-wg-leads
Produced by: knative-sandbox/knobots/actions/update-gofmt
Details:

Closing - this is formatting vendored code


bug: Side menu left closes when popover show

Type: bug
Platform: android 4.4 webview
I have expose-aside-when on the left menu and it works great. But when it's on portrait mode, if I click on the side left popover, the menu content will be shown without expect it. I have done a codepen to show it. To check, it:
Put it on portrait mode.
Click the button who shows the left menu.
Click the popover which is on the footer.
(the left menu will be closed)
How can I solve it? I want my menu opened when I see the popover.
http://codepen.io/sgg90/pen/bdGgwV
Thank you so much!!

Greetings @sgg90!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

This behaviour forced by expose-aside-when directive. Try to temprorary remove it.

Temporary "solved" with a timer:
    function openPopover( event, isAside )
	{
		$scope.sourcesPopover.show( event );
		if (!isAside)
		{
			$timeout(
				function ()
				{
				    $ionicSideMenuDelegate.toggleLeft(true);
				}, 1000
			);
		}
	}

Greetings @sgg90!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


[feature] development-env-in-vagrant

using openstack-helm vagrant for armada

What is the purpose of this pull request?:
What issue does this pull request address?: Fixes #38
Notes for reviewers to consider:
Specific reviewers for pull request:

@gardlt This work looks good.  I'll add my thoughts here as well.
I agree with @v1k0d3n, in that we don't want to maintain separate tracks of the same work (in this case, the kubeadm-aio Vagrant provisioning guide in OpenStack-Helm).  I'd rather link to the kubeadm-aio guide in OpenStack-Helm, but really we just need a kubernetes cluster to use for development, not the OpenStack-Helm specific parts.  I'd like to see that called out in the guide.  The Armada specific parts are fine.  I think a good next step would be to develop an Armada image followed by a Helm chart if this is to be run in-cluster, although I feel this would run "alongside" the Helm client outside of the targeted cluster.
At the end of the day, we really do want to keep Armada decoupled from OpenStack-Helm.  We're using it to deploy OSH, but like @v1k0d3n mentioned, we want it to be a solution for anyone to use to deploy an application and manage that application's entire lifecycle.

@wilkers-steve @v1k0d3n  I like it i think that the division is good. Armada is a component that should work w/ or w/o OSH. General charts and examples is actually that I am trying to strive for. I do not think that the addition or subtraction of the vagrant file will blur the vision. Docker is the way that we should sell as the main form of deployment for our application this is in terms of local or architectural usage. All the vagrant was suppose to facilitating is a minikube like environment. If the Vagrantfile in OSH comes out of the repo and into its own i would be more inclined to remove it from the PR, because then its an generic kubernetes development enviroment for all. Since it wasn't that is why i brought it here and mod it for armada needs. For now i think i will leave the PR up, and i will put a do not merge label. Thank you for your input.


Scan radius now 70m and scan delay is 10s

In the last few days and hours, Niantic has changed how the client receives info about pokemon from the server.
First of all the sight radius decreased to 70m from 100m. From the readme I see that you still use the old 100m sight radius. Will you fix that soon? Can I adjust some options to use your algorithm already until then?
Secondly, A few days ago Niantic changed the scan delay from 1s to 5s. This morning it was increased once again to 10s (see, for example here ). Can you adjust that as well please, or tell me again what options might account for this?
Thanks!

Please check out releases page before opening an issue.


PFP scaling algorithm is wrong when downloading

Compare the avatar on the preview image (screenshot from browser):

to the downloaded result:

This was my result on Firefox 97.0.2 on Ubuntu

I think it is caused by image-rendering: optimize-contrast; property.


Add feature requirement info to image loading docs

Objective

Add "Available on crate feature  only." for docs of image format related types/functions
Add warning "WARN bevy_render::texture::image: feature "" is not enabled" on load attempt
Fixes #13468 .

Solution

Added #[cfg(feature = "")] for types and warn!("feature "" is not enabled"); for ImageFormat enum conversions

Testing
ran reproducing example from issue #13468 and saw in logs
WARN bevy_render::texture::image: feature "exr" is not enabled
generated docs with command RUSTDOCFLAGS="-Zunstable-options --cfg=docsrs" cargo +nightly doc --workspace --all-features --no-deps --document-private-items --open and saw

that docs contain Available on crate feature <image format> only. marks

I added the breaking change label because some enum variants of ImageFormat may no longer be available due to feature gates. (The same may be true for the modules, I'm not sure.)

Shouldn't we use module-level feature gates for e.g. ktx.rs?

ktx2 module already has feature gate, but rust compiler isn't smart enough to mark all inner items of module with feature mark, that's why I marked explicitly

Oh? That's surprising to me. What happens if it's ommitted? Do you have any references to bugs etc for this?

What happens if it's ommitted?

Before my commit there already was attribute on ktx2 module and functions were not marked in docs. Now if attribute on module exists, but for function it was removed, then there is no mark in doc, if attribute on function exists, but for module it was removed, then mark in doc for function exists. I assumed that higher level attribute could reduce binary size, that is why i kept them both.

Do you have any references to bugs etc for this?

I didn't see any related issue earlier, and I didn't find it now. I just reacted to compiller behaviour. If I made an incorrect changes, I'm open to any corrections.

Sounds good :) I'll file something for the rustdoc team reporting this!


Is it necessary to override window.print()?

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version:
Operating system and its version:
PDF.js version:2.5.207
Is a browser extension:chrome

Steps to reproduce the problem:

i use window.print()

What is the expected behavior? (add screenshot)
i can use window.print().
What went wrong? (add screenshot)
it overrides window.print(),so i will get error when i use window.print().
that is 'The overlay manager has not yet been initialized'
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

PDF.js version:2.5.207

That version is no longer supported, please find the latest releases at https://mozilla.github.io/pdf.js/getting_started/#download

I use window.print()

WFM, when executing window.print() manually in the console at https://mozilla.github.io/pdf.js/web/viewer.html

Unfortunately printing isn't well supported across browsers and we're forced to resort to some hacks in order for things to mostly work, this includes overwriting window.print.
Please also note https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.


Init pre-commit eslint/prettier setup & fix errors

Pull Request
Description
Finish setup of pre-commit and configure to run eslint and prettier before each commit.
Closes #210
How Has This Been Tested?
Threw up a good few errors, almost all of which were fixed automatically by eslint --fix as part of the pre-commit hook.
UPDATE: pre-commit package is definitely less used for JS/node stuff, so removed from this repo and replaced with:

Existing Vercel hooks/build runs full ESLint/prettier checks and fails the build of the Preview branches on Errors (not Warnings, those are okay)
Added Husky and lint-staged for the pre-commit hook functionality on local side; should prevent commit if linting fails, no build step here as on balance I think it takes too long. Maybe can consider this as a final check on git push later on.

Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[x] I have checked my code and corrected any misspellings

Im not sure why, but the pre-commit.ci seem to bring up an error about babel -   0:0  error  Parsing error: Cannot find module 'next/babel'

do you know what the error for rendering 404 page is about?

@peterdudfield @rachel-labri-tipton btw this should be good to go/review now! Amended description 👍

if possible could you put this PR in the project WP3 in September iteration? That just helps us keep track of a few thigns


Update 400_tutorial.md

after creating table have added the  sample items into the todo

This section here is misleading as select * from todos; does not actually return the result shown below.
Instead revert this back to DESC todos;


[CELEBORN-588] Remove test conf's category

What changes were proposed in this pull request?
Remove test conf's category to avoid make user confused.
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?

ping @pan3793

ping @pan3793


d435i gravity removal

Hi.
I'm using D435i, and I want to estimate pose by imu sensor inside D435i.
Before I start to estimate, I finished calibration by tutorial uploaded in Intel website.
I learned we need to remove gravity from accelerometer value to estimate pose, so I have questions.
After I calibrated my IMU sensor by tutorial, should I remove gravity from value myself? If I must do, how can I do?
For example, I got these values after calibrated my imu sensor
Writing files:
accel_A and B.txt
gyro_A and B.txt
[-0.00216658 -0.00114198 -0.00042399]
[1000 1000 1000 1000 1000 1000]
using 6000 measurements.
[[ 1.02186281  0.03536714 -0.00926439]
[ 0.02256644  1.01664358  0.05166774]
[-0.00436534 -0.0454576   1.01037547]
[ 0.00597615  0.02938021  0.33118931]]
residuals: [ 51.3077819   85.60967507<PHONE_NUMBER>4]
rank: 4
singular: [443.57067753<PHONE_NUMBER>4<PHONE_NUMBER>2  77.32178072]
norm (raw data  ): 9.651282
norm (fixed data): 9.802097 A good calibration will be near 9.806650
Would you like to write the results to the camera's eeprom? (Y/N)Y
Writing calibration to device.
Device PID:  ****
Device name:  Intel RealSense D435I
Serial number:  ************
Firmware version:  <IP_ADDRESS>
SUCCESS: saved calibration to camera.
Done.
Please Help me!
Thanks.

Only the T265 Tracking Camera, which has the same IMU component as the D435i, has built-in support for 6 degrees of freedom (6-DOF) pose.

It is possible though to get pose on a D435 camera by using OpenCV or ROS.
https://github.com/IntelRealSense/realsense-ros/issues/1026#issuecomment-566029045

Dear @MartyG-RealSense
Thanks a lot! It makes sense!

You're very welcome, I'm glad I could help.  Good luck!   :)


Authorization prompt=none has only openid scope, not scopes from settings

It appears that no matter what scopes I specify in the settings, when the prompt=none request fires it only contains openid scope. The original sign in authorization contains the scopes from the settings, just not the prompt=none. Is this intended, any suggestions?

It appears that no matter what scopes I specify in the settings, when the prompt=none request fires it only contains openid scope. The original sign in authorization contains the scopes from the settings, just not the prompt=none. Is this intended, any suggestions?

This is only done for the queryStatus, IIRC (and this is used as part of the monitor session feature). signinSilent should use the full scope.

What is the difference between the two? It looks like the lib is triggering prompt none as soon as I am redirected back and complete the code exchange. But the new token is missing scopes.

One just queries, whereas the other establishes a session based on the results. As for your STS, not sure. Seems odd that you can't just request openid.

I think what's happening is on the redirect back from sign in, the session monitoring is doing its prompt=none and triggering a code exchange from that code before the app does the code exchange from the redirect code. I am seeing this on your code-identityserver-sample.html.

You can disable the session monitoring then on the callback page. There's a flag on the settings.

I see the flag, I want session monitoring enabled on the callback page, I just don't want it making prompt=none requests and possibly generating tokens before the app calls signinCallback to generate a token from the url. Is there a method to essentially startSessionMonitoring on UserManager?

https://github.com/IdentityModel/oidc-client-js/blob/dev/src/UserManager.js#L603-L609

Sorry, nothing like that. The callback page should only be run to process the result and then redirect to whatever page your app is.

Cool thanks

Reopening this. I wanted to go back to the original question about prompt=none not having all the scopes from the settings.

It appears that no matter what scopes I specify in the settings, when the prompt=none request fires it only contains openid scope. The original sign in authorization contains the scopes from the settings, just not the prompt=none. Is this intended, any suggestions?

This is only done for the querySessionStatus, IIRC (and this is used as part of the monitor session feature). signinSilent should use the full scope.

Are you saying we can't use the session monitoring feature because our idp requires more than just openid to get a token? Curious why it doesn't just contain all the scopes from the settings?

Curious why it doesn't just contain all the scopes from the settings?

Because the response only needs an id_token to do its job. It's too much to also request (and receive) an access token.

Does the spec have access_token as optional from a successful token response for the auth code flow? Looking here seems to indicate it is always part of the successful response.

Yea you are correct in that the authorization server should be able to handle only openid, but a little unsure why any prompt=none call wouldn't contain the other scopes from settings. Perhaps there's something else going on here I'm not understanding. https://accounts.nike.com/.well-known/openid-configuration

Sorry, not sure. Perhaps ask the token server vendor/developer why?


multi select support

Digging though the code its unclear how to implement multi select,
Seems that you would need something along the lines of getFieldAsList
Thanks

Hello, yes it's a missing piece. Implementation would require:

Form.getFieldAsStringList
A new Field value for MultiSelect in Form.Field module, along with asStringList value getter
Implementing Form.Input.multiSelectInput

Ok, ill try to figure it out and add it, hopefully resulting in a pull request
Thanks

Great! Let me know if you're stuck.

Oh my, I just love to see an issue already open for stuff I was looking for :smile:

Hey @amitaibu I'm working on it https://github.com/narkisr/elm-simple-form/tree/multiselect :)
I hope to have it ready for upstream in a couple of days

To confirm, is this issue about having a field with multiple number of instances. That is, a field I could add a "add another" button to it?

Hi, no it's about having a <select multiple> AFAIK.

closing due to inactivity and utility of select multiple now low with #60 in the coming.


[stable/nfs-server-provisioner] fix deployment when not creating storage class

Signed-off-by: Tomas Ostasevicius<EMAIL_ADDRESS>tagging @kiall for review, thanks!
What this PR does / why we need it:
With the current chart, if .Values.storageClass.create is false, the parameters and mountOptions were still rendered in the template, thus making the chart undeployable (since the manifest is not complete).
This PR simply moves the else clause of the .Values.storageClass.create to the end of the file, so that the rendered template is completely empty (no-op), and the deployment succeeds.
Which issue this PR fixes
(I did not create an issue for this, as the fix is trivial)
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test

/lgtm


当边缘节点机器连接不上时，应中断这一个步骤安装，并给提示

In GitLab by @cuiaq123 on Aug 11, 2020, 03:12

In GitLab by @luotian-github on Aug 25, 2020, 01:01
will fix it in the next version


NodeJS project

I want to contribute to this project.

I also want to contribute to this project.


hwmv2: Change board names to vendor prefixes

I think in nearly all cases this makes things much worse but there you go

CC @mah-eiSmart @jadonk

CC @wm-eisos Please keep notice of that

@golowanow this has a commit which fixes up intel_adsp

@golowanow this has a commit which fixes up intel_adsp

@nordicjm, thank you

Architecture WG:

Aligning folder names for vendors with vendor-prefixes.txt is accepted, no objections


Add Select Box For Number of Rows Per Page

Please add an option to display a select box to choose the number of rows/records per page.
E.g. Add I could set an array of 5, 10, 25, 50, 100
I should then be able to set the selected value programmatically too (or via a binding)

Please be more specific clear what you are asking for.

I am paging data in a grid. I want to give the user the option of selecting the number of rows that are displayed at a time.
See this example with datatables https://datatables.net/examples/advanced_init/length_menu.html however, I would like the drop down to be next to the pagination.
See this example with UI-Grid http://ui-grid.info/docs/#/tutorial/214_pagination
See also this question on stackoverflow http://stackoverflow.com/questions/33990460/add-control-to-bootstrap-pagination-for-rows-per-page

In this case, the pagination is just a simple standalone component - it is up to the user to wire it up with a select box for modifying the number of items displayed per page, and that is by design since the pagination should be agnostic to however the user decides to implement such a select box.


Make schema name optional

SQLAlchemy / Alembic does not set a default schema name for Postgres, nor does it require that objects set a schema. Without setting a schema, the Postgres search_path setting determines where objects are created.
However, alembic_utils requires that all objects it defines have a schema set. This makes it hard to support running a migration against an environment where the schema is set with SET schema TO ....

I'm familiar with postgres search_path but I don't follow how it being set interacts with requiring an explicit schema in ReplaceableEntity.
I've seen sqlalchemy's optional schema cause enough difficult-to-follow behavior that making it required in alembic_utils was an intentional design choice.
If you have a concrete example of where the value of search_path causes unexpected behavior with an explicit ReplaceableEntity.schema I'm happy to take a look, but if the goal convenience, I prefer to keep it as required.

The goal was adaptability. I can deploy my migrations onto a PG installation where the DBA has set the search_path for the account, and everything runs correctly except for the ReplaceableEntity objects, which have a hard-coded schema name.

I ran into a related issue; I have a few tests that use do a Base.metadata.drop_all() on cleanup. Since I startd explicitly defining some schema's, this is broken because SQLAlchemy  tries to delete items in the wrong order, leading to conflicts. I can manually override the drop order, but this is quite a hassle.

@tdamsma this is a different issue than Martijn described

alembic_utils does not register entities against a sqlalchemy Metadata instance so Base.metadata.drop_all() would not interact.
If you have e.g. defined a PGView that refers to a sqlalchemy table, its possible that the dependency is preventing the drops from succeeding if that method does not issue a DROP ... CASCADE.
But if that was the issue, changing the table drop order would not have resolved it.
If you think its worth documenting for other users, please open a new issue and provide a reproducible example and stacktrace.

Unrelated to this problem, if you're dropping and recreating tables between tests to make sure the database is in an empty state, you should consider running tests in a transaction that rolls back after each test. It is significantly faster and parallel safe if you ever need to parallelize a large test suite.
unittest transactional test setup
pytest transactional test setup

I agree using transactions is a much better pattern, but the test suite is not fully migrated (yet?).
I think I was not entirely clear what I meant, but because alembic-utils requires explicit schema's, my other tables that are operated on by PGFunctions now also need explicit schema's as to not throw off alembic. And then that (maybe?) causes the resolution order of of dependencies in SQLAlchemy to break. Not 100% sure, but I strongly suspect some part of Alembic and/or SQLAlchemy does not like it if half the tables have the schema name implicitly set to public, and the other half has it set explicitly. Now I have the options:

Use explicit schema names everywhere
Deal with the fall out (manually adding schema names to alembic migrations, manually tune Base.metadata.drop_all() order, etc )
Not use explicit public schema calls anywhere

I would prefer the last, so that is how it related to this issue

Got it
I'm happy to help you get set up but I won't be able to assist without a concrete reproducible example.

If you'd like explicitly set a schema="public" for all tables associated with your Base.metadata you can set it globally on the metadata instance https://docs.sqlalchemy.org/en/14/core/metadata.html#sqlalchemy.schema.MetaData rather than adding it to __tableargs__ for every table.
e.g.
from sqlalchemy import MetaData
from sqlalchemy.orm import declarative_base

metadata = MetaData(schema="public")
Base = declarative_base(metadata)

class MyTable(Base):
    ...

Thanks for the offer! I didn't know about the option to set a schema globally, learned something already. I decided to give option 3 a try, see #54
I browsed through the issues, and as #41 also is about resolution order it might be related to the behaviour I ran into that when a single table is referred to as both some_table and public.some_table this sees to confuse SQLAlchemy/Alembic somehow

Resolution order in #44 refers to the order in which entities must be rendered in a migration upgrade/downgrade block for the migration to succeed. It does not relate to runtime DDL statements.

I appreciate the effort required to open a PR, but as I noted previously, requiring a schema was a deliberate design decision. I will not consider any changes until I have a reproducible example so that I can understand the issue you're facing.

Well it's your library. I can't create a decent minimal example detailing the wonkiness I experienced in having mixed optional and default schema use I experienced with Alembic/SQLALchemy, so I understand ,my case is not very convincing. I just want to make the point that SQLAlchemy and Alembic do not require schema's to be set explicitly, and this extension to alembic does. This design decision creates (for me at least) some ripple effects when adding a few triggers to and existing applications with alembic-utils. It is not so important to me as want to figure out the exacpt root cause, and it may very well be that there is a deeper problem in my application but that is not the point; I just wanted to add a trigger, and now I had make some tweaks to seemingly unrelated test-fixtures and table definitions.
Perhaps you can better document this design decision as it is a bit unexpected for an extension to alembic to pose additional contraints (explicit schema's) not really related to the core added functionality (support for migratable triggers and functions.


templates.mae is required by Findcoordgen.cmake but never used

Description:

RDKit Version: 2019.3
Platform: Debian

Upstream coordgen does not install templates.mae but Findcoordgen.cmake insists on finding it as coordgen_TEMPLATE_FILE - I guess that is fine for the locally built one in External/Coordgen but means that find_package(coordgen) won't work for finding a system-installed coordgen even if coordgen shipped a cmake file (see https://github.com/schrodinger/coordgenlibs/issues/31).
Is templates.mae used by RDKit and/or RDKit's use of maeparser/coordgenlib? If not, maybe it needs not be installed and/or coordgen_TEMPLATE_FILE can be removed?

I believe that templates.mae is important to the proper functioning of coordgen. Not installing that is probably a bug/oversight in the upstream.

I was looking at an earlier coordgen release, the current one does install it, so closing this.


Knowledge Base

DO NOT MERGE, THIS IS NOT READY YET.
This is a migration of the documentation Nodejitsu built over the last 5 years or so. Before we can merge I'll have to finalize the transfer of copyright from Nodejitsu/GoDaddy to the foundation.
This work would provide a nice starting point for a knowledge base we can continue to build and iterate on as a community.
I also removed author information. IMO having the initial author noted for each article is a barrier to others editing and maintaining those pages.
Things still to do:

[ ] Improve the template so that it suggests other content.
[ ] Create a directory page that shows all content.
[ ] Find a good way to expose and link to this content from the main docs page.

/cc @indexzero @nodejs/documentation

+1 here on the Copyright transfer. We'll work to get that sorted with legal folks so it can transfer from Nodejitsu to the foundation.
What are thoughts on putting this in a separate repo and including it as a module?

@indexzero this repo is already setup for auto-deploy and has a localization system attached, and will soon have localizers and doc writers as write access members. It's going to get pretty complicated to do an additional repo with all of that. Not to mention this repo has contributors already making style improvements and whatnot. This is the path of least resistance for sure.

Great stuff! This'll really help to seed the Docs WG content. I'd be happy to help out with that todo list. :smile:

@Qard go ahead and send pull requests to the knowledge-base branch to help out :)

@mikeal 10-4. We'll follow-up offline about the next steps w.r.t. copyright transfer. I assume this will be a topic at the November 2nd board meeting?

Please also check how this content relates to #217, #218. It's a bit confusing at the moment.

@mikeal @indexzero Is there any progress on this? Would love to hand this over to @nodejs/documentation.

@fhemberger agreed. Nodejitsu would love to hand this over to @nodejs/documentation as well! I believe the next step here was for this to be discussed during the last foundation legal WG call. I do not sit on the legal committee, but I know @mikeal is aware of the minutes. Hopefully he can give status.
Due an unavoidable work conflict at GoDaddy next Monday I will have to miss most of the Node.js Foundation board call.
@mikeal if this will be part of the public or private session I will make myself available at the pleasure of the board while it is discussed.

hey @indexzero I think it would help if you could add an MIT/BSD compatible license to the original work on https://github.com/nodejitsu/docs/

@mikeal done. It is now MIT. https://github.com/nodejitsu/docs/commit/a4800be5a70b1c8a356772a7907cdabf851ec42e

werd, ok, we can merge this now. we'll work out the details of the copyright transfer later, now that it's permissively licensed we can put it in the tree.

Resisting the urge to push the "Merge" button so hard at the moment. All sentimental. Holding off for the final ok from @fhemberger: are we good to go here?

@mikeal Should we merge it without the Handlebars templates, so @nodejs/documentation can integrate the docs into their content structure first?

@fhemberger Nodejitsu plans to redirect all traffic from http://docs.nodejitsu.com to the final pages on the nodejs.org site so we will have to do the redirect dance a little no matter what.
Obviously once is better than twice, we could move this into a "draft" area if one exists where it would not get rendered or served yet. Given how old these tutorials are that's probably the best way to approach this: stage them somewhere and publish them one at a time as they are reviewed for correctness.

Our staging area at the moment is called "push it without linking it on the site" ;)

@fhemberger great. So this can be safely merged then?

@indexzero I had to fix a few things:

the missing 'docs-menu' partial in layouts/docs.hbs and layouts/knowledge-base-index.hbs was breaking the the build.
I excluded the knowledge base index file from the listing and fixed markdown headlines in two documents
I removed "Downloads" (linking to Node.js 0.4.1 ;)) and 'Hosting, Conferences and More!' (we have a event listing already and some links were broken). I hope that's ok for you.

Merged via d02b8a2.

\o/


Cannot export both types and values from CJS

🔎 Search Terms
verbatimModuleSyntax, commonjs, require, export, export type,
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about CJS export syntax and verbatimModuleSyntax release notes.

⏯ Playground Link
https://www.typescriptlang.org/play/?moduleResolution=99&target=99&module=199&verbatimModuleSyntax=true&ts=5.8.0-dev.20241225#code/KYDwDg9gTgLgBDAnmYcBiEJwLxwM4xQCWAdgOZwA+cJArgLYBGwUA3AFDsDGANgIZ48cAEJ8ocAN4BfTqEiwcIsayA
💻 Code
I wanted to convert a *.ts file that gets interpreted as CJS (due to package.json "type" field) to use verbatimModuleSyntax for explicitness.
The file previously looked like this
// index.ts
export type Foo = string | number;
export const Bar = 42;

and could be imported like so
// foo.ts
import { type Foo, Bar } from './index';

const x: Foo = 42;
const y = Bar;

After enabling verbatimModuleSyntax, it seems no longer possible to export both Foo and Bar from index.ts. Some attempts:
type Foo = string | number;
const Bar = 42;

export = { Foo, Bar }; // error; Foo is a type but used as a value

This is ok,
export type Foo = string | number;
const Bar = 42;

but this is not
export type Foo = string | number;
const Bar = 42;
export = { Bar }; // An export assignment cannot be used in a module with other exported elements. (TS2309)

nor this
type Foo = string | number;
const Bar = 42;
export type { Foo };
export = { Bar }; // An export assignment cannot be used in a module with other exported elements. (TS2309)

tsconfig:
{
    "compilerOptions": {
        "verbatimModuleSyntax": true,
        "target": "ESNext",
        "module": "NodeNext",
        "strict": true,
    }
}

package.json: has "type": "commonjs"
🙁 Actual behavior
Can't find a way to export both types and values using CJS import/export syntax required by verbatimModuleSyntax
🙂 Expected behavior
There is a way to export both types and values using CJS import/export syntax
Additional information about the issue
Perhaps this is possible, and if so I'd ask it be added to the documentation. Without this, a currently-functioning CJS module cannot straightforwardly be converted to use verbatimModuleSyntax.
FWIW, if it's not possible, I don't see why at least one of the following wouldn't be allowed (specifically due to the use of export type to ensure only one value export exists)
export type Foo = string | number;
const Bar = 42;
export = { Bar }; // not a problem; only one value export

or
type Foo = string | number;
const Bar = 42;
export type { Foo };
export = { Bar };

Followup, I have come across the following excerpt from https://github.com/microsoft/TypeScript/pull/52203:

We knew this would be a bit of a burden for imports, but I didn’t realize what a pain it would be for exports. The problem here is that you can no longer sidecar-export a type:
export type T = {};
export = { hello: "world" };
// ^^^^^^^^^^^^^^^^^^^^^^^^
// An export assignment cannot be used in a module with other exported elements.(2309)

To accomplish this, you’d have to merge a namespace declaration containing the types:
const _exports = { hello: "world" };
namespace _exports {
  export type T = {};
}
export = _exports;

These limitations make it really unattractive to use the flag in CJS-emitting TypeScript. I discussed this with @DanielRosenwasser, and ultimately decided that it’s not worth worrying about too much—the flag is opt-in, and we expect the users interested in using it to write mostly ESM-emitting TypeScript.

Given this information it's apparently a known issue that CJS export syntax is painful. I'd consider this issue a request to make it less painful.
While the quoted excerpt above implies that CJS is not a first-class citizen of verbatimModuleSyntax, I did not get that takeaway from the release notes, which I actually understood to be encouraging verbatimModuleSyntax-with-CJS to avoid confusion, particularly this part:

While this is a limitation, it does help make some issues more obvious. For example, it’s very common to forget to set the type field in package.json under --module node16. As a result, developers would start writing CommonJS modules instead of ES modules without realizing it, giving surprising lookup rules and JavaScript output. This new flag ensures that you’re intentional about the file type you’re using because the syntax is intentionally different.

Similarly on the issue proposal:

This import is legal under --module esnext, but an error in --module commonjs. (In node16 and nodenext, it depends on the file extension and/or the package.json "type" field.) If the file is determined to be a CommonJS module at emit by any of these settings, it must be written as
import fs = require("fs");
instead. Many users have the impression that this syntax is legacy or deprecated, but that’s not the case. It accurately reflects that the output will use a require statement, instead of obscuring the output behind layers of transformations and interop helpers. I think using this syntax is particularly valuable in .cts files under --module nodenext, because in Node’s module system, imports and requires have markedly different semantics, and actually writing out require helps you understand when and why you can’t require an ES module—it’s easier to lose track of this when your require is disguised as an ESM import in the source file.

My personal initial impression working with verbatimModuleSyntax is that it is super-super worth it for CJS. The minutiae of node's CJS/ESM interop are extremely nuanced and it is extremely easy to lose track of what's happening at all once you throw TS's module syntax transformations into the mix. I've wasted many hours this way, before even realizing that half my assumptions were wrong because I was unknowingly writing CJS (like the release notes mention!). Once I realized that, I wasted many more hours 🙃.
Anyways, so I would strongly request some improvements around DevX. Ideas for making type exports better:

allow "sidecar" type-only exports
allow export type  { Foo as Bar }; syntax in CJS, where you can supply named type exports.

Both of these would be equivalent to the "merged namespace" approach.
With CJS it's very important IMO to be extremely clear what the exported value is. So I'm happy for types and values not to be allowed to mix in the exports. But I don't see any reason why type-only export syntax which is currently banned should not be allowed to exist in parallel to the value export syntax. Users don't expect type-only syntax to have runtime impact, so I don't see the possibility for confusion.
Similarly, on the importing side of it, I'd propose

import type { Foo, Bar } from './foo.cts' be allowed (including from cts file) (but NOT import { type Foo } from './foo.cts', even if all the imports are type-only. Only import type.
allow destructuring syntax in import = require() syntax.  require type modifiers for types under verbatimModuleSyntax, and prohibit a statement which does not have at least one destructured (non-type) value.import { value, type FooType } = require('./foo.cts');

to allow colocating type and value imports (and generally improve the runtime const { namedValue } = require('./foo.js'); situation)


cmd/go: "unrecognized import path" for local packages after updating to go1.13

What version of Go are you using (go version)?

$ go version
1.13

Does this issue reproduce with the latest release?

I attempted to go run an application as before, but ran into an unrecognized import path error. Previously with 1.12 I did not have an issue. These are imports from sub packages within a main package.
running
go get -u ./...
returns:
package _/*/src: unrecognized import path "_/*/src" (import path does not begin with hostname)
What did you expect to see?
That local packages don't need a hostname, and they don't fail to "get".
What did you see instead?
"import path does not begin with hostname"

That error message comes from here:
https://github.com/golang/go/blob/aae0b5b0b26bf4fd26cad0111535d703691a9083/src/cmd/go/internal/get/vcs.go#L774

Can you provide a concrete source file that reproduces the issue? There were certainly changes around that code path in 1.13 that may be related, but my understanding (from https://github.com/golang/go/issues/26645#issuecomment-408572701 and other previous discussions) is that relative imports have never worked with go get.
This may also be related to #12385.

@nichoriverae just to confirm, is it correct that are you not using modules?
One change in Go 1.13 is GO111MODULE=auto (which is the default value if not explicitly set) now turns on module mode whenever you are running the go command inside of a directory tree with a go.mod file — even if the current directory is within GOPATH/src. This means module mode happens in more cases than in Go 1.12. (See the Go 1.13 release notes for more details).

@thepudds the project is using modules
@bcmills I'm attempting to recreate the error using a fresh directory now, I'll post a gist when I get it to the same state. Just to reaffirm, there are no relative imports and the failure point is on submodules within the main package.

go vet seems to be looking in GOPATH and GOROOT:
        /usr/*/github.com/golang-migrate/migrate/v4/database/mysql (from $GOROOT)
        /Users/*/github.com/golang-migrate/migrate/v4/database/mysql (from $GOPATH)```

$ and a simple go get ./...
package <package>/src/config: unrecognized import path "<package>/src/config" (import path does not begin with hostname)

@bcmills this repo repoduces the error. Granted, it's not using the import that is failing, but the go get command gives me the same error.
https://github.com/nichoriverae/Go-Issue-34117

@nichoriverae Thank you for putting that repo together.
For that repo, what is the exact command sequence that fails, and what is the error you currently get?
go get github.com/nichoriverae/Go-Issue-34117 fails complaining about a mismatch with parsing go.mod: module declares its path as: main, but that's expected, and I think not the error in question here.
Doing git clone https://github.com/nichoriverae/Go-Issue-34117, cd'ing to the resulting directory, and doing go get ./... and go get -u ./... do not seem to complain, so I am probably doing something wrong.

I'm under the impression these issues are happening because of GOPROXY and my corporate network settings. I changed the environment variable to "direct" and that solved most of my issues.
@thepudds I tried the repo on another machine that had a fresh go1.13 install and it didn't give me any problems either, which makes me assume that it is indeed the corporate settings.

Can you provide a concrete source file that reproduces the issue? There were certainly changes around that code path in 1.13 that may be related, but my understanding (from #26645 (comment) and other previous discussions) is that relative imports have never worked with go get.
This may also be related to #12385.

I am testing the qor package and just created the main.go file exactly like the link here https://doc.getqor.com/get_started.html. After that, running go get -u ./... will give the same issue

@bubuzzz, that issue seems unrelated. If you're still seeing a problem, please open a new issue.

@nichoriverae, I'm having a bit of trouble following the discussion here, but please let us know if there is anything we still need to resolve.

Hi, my project is organized in GOPATH. I upgrade go from go1.12 to go1.14.
conf
src
  |-- source files

when I run GO111MODULE=off go get -v ./..., it reports unrecognized import path ....  import path does not begin with hostname.
It looks like the same problem. Does the behavior change from Go1.13 when GO111MODULE=off?

@hitzhangjie Make sure there aren't source files directly in a $GOPATH/src directory. They should be in subdirectories not in $GOPATH/src itself.
Also, make sure any imports outside the standard library start with a hostname, for example, github.com/go-sql-driver/mysql. The import posted above was main/salut. That won't work because go get can't resolve it to a repository.


Remove exposed image path in Edit profile

Can serve as a means for XSS

Please assign me to this.


TypeError: Illegal invocation error is thrown when using  queryAssignedNodes with text nodes

Description
queryAssignedNodes throws A "TypeError: Illegal invocation" when slotted content contains text nodes.
Live Demo
https://webcomponents.dev/edit/FXrFMojSYzYa8eJNaJzh
Steps to Reproduce

Create my-element with child nodes containing text.

Expected Results
No error is throw
Actual Results
TypeError: Illegal invocation is thrown
Browsers Affected (Haven't tested in other browsers)

[x ] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari 11
[ ] Safari 10
[ ] IE 11

Versions
Uses the default/current version in https://webcomponents.dev

Acknowledged. This is due to a typo in the code and there's obviously not a good test for this. We'll work on getting it fixed. Thanks.


add vagrant module

Follow instructions here:

https://wiki.archlinux.org/index.php/Vagrant
https://wiki.archlinux.org/index.php/VirtualBox

Vagrant plugins to be installed:

vagrant-libvirt
vagrant-lxc

VirtualBox modules need to be included in /etc/modules-load.d/virtualbox.conf


Remove non-existing features for AndroidManifest from README

"camera2" features are non-existing. Adding them to AndroidManifest caused the app to be incompatible with any device in Play Store.
Resolves #411

Merged. I did a fix in readme because you forgot to close the last line.


Missing library?

Hey, cool extension. I tried to compile and run it from source, but vscode complains about not being able to find 'operationTree/nodeAtRange' and 'syntaxTree/nodeAtRange'.
I noticed that the extension downloaded from the store has two dlls:
Microsoft.CodeAnalysis.CompilerDeveloperSdk.dll , which I was able to build
and
Microsoft.CodeAnalysis.ExternalAccess.CompilerDeveloperSDK.dll for which I don't see the source code in the repo.
After copying external access dll into my project folder, it works as expected again and I'm able to make some changes. But not being super familiar with LSP or vscode extensions, I'm not sure if this will stop me from adding new features at some point.
Anyway, am I missing something? Or could you upload the source for that second dll pretty please?

The second dll comes from roslyn. If you want to do local development, what is been doing is copying both the external access dll and the sdk dll from the bin folder of the sdk around as needed.
What are you looking to contribute?

I'm going to close this out. Feel free to ask any more questions if you have them.


Feature added - Detect when vim is in edit mode

Because (see #39):

Is not clear enough when you are on insert mode (Vim)

This commit:

Is a start of getting the state of Vim

Create a setting property that includes vim stuff (now, only mode)

Wants to get some feedback

Excellent job! I just made one adjustment to make sure the mouse cursor is the + for the entire editor in insert mode. Only additional thing I would do is use a different keyboard cursor color for insert mode, too.

Thank you!
Pretty cool idea, well done!


How to dynamically control parameters when using RedisSearch

I need to dynamically control parameters such as Verbatim, Highlight, Slop... when using RedisSearch, but it is difficult for me to define a type to receive a value, because the type of the value returned by each method is different, and the most important thing is that the type is not exported.
This is how I expected it to be written:
var c cmds.Completed
c := cmds.Completed(r.B().FtSearch().Index(index).Query(text))
if opt.Verbatim{
	val,_ := c.(cmds.FtSearchQuery)
	c = cmds.Completed(val.Verbatim())
}
if opt.Highlight{
	val,_ := c.(cmds.FtSearchVerbatim)
	c = cmds.Completed(val.Highlight())
}
...

Hello @Angry-Chick
Probably you are looking for this: https://github.com/rueian/rueidis/blob/e806b49ff57094e14eb87ecb0c94b5bd4f4d1464/cmds.go#L19

Hi @Angry-Chick,
I plan to export cmds.Completed in the future release (https://github.com/rueian/rueidis/pull/122). However cmds.FtSearchQuery and cmds.FtSearchVerbatim will still be private.
For constructing the command conditionally, you can use the https://github.com/rueian/rueidis#arbitrary-command:
cmd := c.B().Arbitrary("FTSEARCH").Keys("xxx_index")
if opt.Verbatim {
	cmd = cmd.Args("...", "...")
}
if opt.Highlight {
	cmd = cmd.Args("...", "...")
}
client.Do(ctx, cmd.Build())

Hi @Angry-Chick,
Are you still bothered by this issue?

Hi @Angry-Chick, please reopen this or create a new issue if you still need some help.


Git Merge: Cannot merge with conflicts without committing

I cannot submit to the mailing list. The mailing host refuses to accept my e-mail address:

vger.kernel.org gave this error:
Hello [40.92.*.*], for your MAIL FROM address<EMAIL_ADDRESS>policy > analysis reported:
Your address is not liked source for email

So, I don't have no choice than to post my feature request here:

In the process of merging two branches with merge conflicts, it's not possible to prevent a commit in order to inspect the result first. If I enter git merge --continue --no-commit, I get an error message.
After performing a comprehensive merge with merge conflicts, it should be possible to inspect the result first before committing. I know, I can eventually update the commit using git commit --amend --no-edit --reset-author, but I don't think that's a reasonable path to follow.

So, I don't have no choice than to post my feature request here:

Just because one venue does not work does not mean that another venue is actually going to be a good one. Almost nobody will see your message here.
That said:

After performing a comprehensive merge with merge conflicts, it should be possible to inspect the result first before committing.

I don't know what you mean by "inspect", but after updating the conflicted files with git add <file> or git add -u, you can see the diff of what is about to be committed with git diff --cached.

Just because one venue does not work does not mean that another venue is actually going to be a good one. Almost nobody will see your message here.

I agree.  I just took a chance here. It's the only related channel I could think of. The only suggested channel is blocked. No way to change that. If there'd been a better approach I certainly would have used that.

I don't know what you mean by "inspect"

I mean: Inspect in a developer IDE, like Visual Studio Code.
This sequence currently doesn't work:
> git merge B --no-commit
   conflicts in ....
> git mergetool
> git merge --continue --no-commit
   successfully merged
> code .
> git commit -m "done"

The 3rd step won't execute.

If there'd been a better approach I certainly would have used that.

There's a git-users list hosted separately which might be less picky about your domain. There's also irc. See https://git-scm.com/community for links.

This sequence currently doesn't work

I still don't understand what you're trying to accomplish. How does one continue a merge except by making a commit? What is it in the state before running that command that you want to change? Is it just that you have some entries marked as unmerged in the index, and you want stage the resolutions? I'd use git add -u for that.

Thank you for pointing me, @peff.

I still don't understand what you're trying to accomplish

Well, the reason for the --no-commit option is obvious: Merge code bases into the working directory but don't commit the result, so manual amendmends to the code will be possible before finally commiting in a separate step.
The same process should simply be true for merge operations that had been interrupted by a merge conflict.

I understand why you'd want --no-commit in the first command. But what do you expect merge --continue --no-commit to do, if it is not creating a commit?

Hmm ... Now I'm in doubt ... Isn't the following workflow sequence true:

supposed behaviour:

You eventually have to merge --continue to make the final commit (or just run git commit; they are synonyms, see 367ff694281ce569edd8f6e444fc770f92f5d215). But before then, you are just collecting changes in the working tree (and in the index, if you ran git add or if the changes applied without conflict) that will go into that commit. After you've run git mergetool, your working tree should contain the resolutions, and you can use normal tools to look at them. Git-aware tools like vscode might look at the index, too, so you probably want to mark the resolved paths using git add.

I was able to reproduce this. Thank you for enlightening me.


Re-running dependency_table produces error

and then running it again produces a different error:

I just tested this after freshly cloning teal using the 28renv@main branch of staged.dependencies.
I also repeated it for tern and get no error.
Maybe this error was also solved by the topological sort issue that you referenced above, although I had the impression that it was also working before.
> staged.dependencies::dependency_table()
                                        repo               host       type       branch
1                   insightsengineering/tern https://github.com    current local (main)
2                              Roche/rtables https://github.com   upstream         main
3             insightsengineering/utils.nest https://github.com   upstream         main
4                   insightsengineering/scda https://github.com   upstream         main
5              insightsengineering/test.nest https://github.com   upstream         main
6              insightsengineering/scda.2021 https://github.com   upstream         main
7                   insightsengineering/teal https://github.com downstream         main
8             insightsengineering/teal.devel https://github.com downstream         main
9  insightsengineering/teal.modules.clinical https://github.com downstream         main
10  insightsengineering/teal.modules.general https://github.com downstream         main
11           insightsengineering/teal.osprey https://github.com downstream         main
12          insightsengineering/teal.goshawk https://github.com downstream         main
13     insightsengineering/random.cdisc.data https://github.com      other         main
14                insightsengineering/osprey https://github.com      other         main
15               insightsengineering/goshawk https://github.com      other         main
16                insightsengineering/hermes https://github.com      other         main
17         insightsengineering/ggplot2.utils https://github.com      other         main
18   insightsengineering/teal.modules.hermes https://github.com      other         main

Running it twice gives the same output.

The error might come from fs::dir_copy(local_dir, repo_dir) although I make sure that repo_dir does not exist before executing this operation. Can you track this down to the function that causes this error (e.g. with options(error = recover))? Unfortunately, I don't have Windows, and I think it might be due to this.

Yes I'll dig into it - I have to keep deleting my cache everytime :( - can you check without the packages being added to local.yaml and see if that works fine for you as well?

So on Windows it isn't deleting the local cached version directory (unlink is silently failing)

Replacing unlink(repo_dir, recursive = TRUE) with fs::dir_delete(repo_dir) seems to fix it - my suspicion is this is something to do with long path names in Windows - I'll put a PR in for you to test @maximilianmordig


Unexpected redirect from 80 port

I'm opening the following page:http://ip/terminal/
And receive the following output:
WebSocket connection error (ws://ip:57776/WebTerminal.Engine.cls). Trying to connect again in 10 seconds...

WebSocket connection closed. Code 1006, reason: .

So why 57776 port?
Expected behavior:

if port is in url, connect to the same port
if no port is present in url

if protocol is http connect to 80 port
if protocol is https connect to 443 port

Confirmed! Because of this line in the project's sources: the output after build would be
this.server = new CacheWebTerminalServer(
    this, (location.protocol === "https:" ? "wss:" : "ws:"), location.hostname,
    location.port || "57776"
  );

And the location.port can be equal to "".
Thanks, Edward.

Fixed by 46ad598dc1428575fdcccc7e53cb6509f0ee0189 (3.2.2), please, confirm problem solved and close the issue.
Wondering why nobody has never submit their issues about this.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter reolink for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ioBroker.reolink
   -

ERRORS:

[ ] :heavy_exclamation_mark: [E162] js-controller 3.3.19 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E204] Version "1.0.0" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.

WARNINGS:

[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence

This issue has been replaced by new isse #96
This issue can be closed.
your
ioBroker Check and Service Bot


changes to pkg:dart2js_info that affect dart2js binary do not propagate on rebuild of the sdk

Repro:

Compile SDK locally
Compile JS with dump info
Change pkg/dart2js_info in a way that affects dump info output
Recompile SDK
Recompile JS with dump info
Notice that dump info DOES NOT CHANGE

@sigmundch thinks there are some missing dependencies in gn files or similar

I haven't tried to repro, but looking at the .d files I noticed that:

The dart2js.dart.dill (created as a step for the application_snapshot rule) has dart2js_info files in the dart2js.dart.dill.d deps file

However, dart2js.dart.snapshot.d is practically empty and didn't mention the dat2js.dart.dill used as an input to it.

I'm probably misreading something or missing some detail. FWIW, our team hasn't noticed that the snapshots don't get updated, so potentially something else is at play here.