RFC: How should a digest_size > hash function's output be handled?

How should a multihash implementation handle a call where the digest is longer than the specified output of that hash function? E.g. (pseudocode)
// The provided digest is 26 bytes long,
// but SHA1 can't produce a digest longer than 20 bytes
mh = multihash.encode(digest='abcdefghijklmnopqrstuvwxyz', code=Codes['sha1'])

Conversely, is the following multihash valid? (hex encoded, spaces added for legibility)
11 1a<PHONE_NUMBER>666768696a6b6c6d6e6f707172737475767778797a

The code field declares the hash function is SHA-1 (0x11). The length field declares the digest is 26 bytes long, and the received digest field is 26 bytes long. However SHA-1 can't produce 26-byte digest.
When a multihash library is called to encode/decode such an input it could:
a. Signal an error, and stop encoding/decoding?
b. Set the length field to len(digest), then continue with processing?
c. Truncate the digest field, before continuing with processing?
The behaviour is currently unspecified, i.e. implementations can do whatever they want. AFAICT go-multihash does b. I'd like to propose that a. as a required behaviour for standards conforming implementations.
What do you think? Have I missed a specification document? Would you prefer I sent this to a mailing list (e.g. ipfs-users)?

Thanks for this, great bug catch. I think this should probably be an error. Though we could define all extra bytes to always be zeros. that way can compare sha1 and sha256 at same lengths or something.

we could define all extra bytes to always be zeros. that way can compare sha1 and sha256 at same lengths or something

I don't follow. What would be the use case for comparing digests from two different algorithms?

@moreati oh for example in a DHT for XOR distance between digests.

Kademlia DHT for XOR distance between digests

How niche (or otherwise) a use case are those? Would you really use a multihash encoded digest directly in a DHT, given the biasing that occurs in the first two bytes?
I'm worried that if padding bytes are introduced then it will lead to some vulnerability or error based on a false sense of security. I would very much prefer that behaviour a, (i.e. abort/signal an error) be the only conforming behaviour, or at leastt the strongly encouraged default behaviour.
If padding is to be allowed by the standard it should be an explicit choice such as passing a flag padding=true, or invoking encode_padded() instead of encode()

How niche (or otherwise) a use case are those?

it's not uncommon.
im not sure either way, yet. but i hear you, re errors and not creating a misleading level of bit security. that's likely the right answer.

+1 as @moreati for returning an error when lenght > lenght_of_digest_algorithm, both when computing a Sum() (as the utility function is called in the go-multihash implementation) and when packing a digest into a multihash value.
Padding should be handled by the application that requires comparison of hashes of different lenghts.
If indeed padding is what's needed. For instance, Kademlia implementations could decide to:

rehash all multihashes in order to get a uniform hash length for keying and computing distances.
pad a hash with itself instead of with zeroes. This would not add entropy, but would avoid clustering of shorter hashes.
etc.

another option is to actually produce that many bytes of hash. for example, the "111 byte (888 bit) sha1 hash of 'foobar' "
x := "foobar"
buf := make([]byte, 111) // 888 bits.
copy(sha1(x), buf[0:20]) // 160 bits of sha1(x)
copy(sha1(x + "1"), buf[20:40]) // 160 bits of sha1(x + "1")
copy(sha1(x + "2"), buf[40:60]) // 160 bits of sha1(x + "2")
copy(sha1(x + "3"), buf[60:80]) // 160 bits of sha1(x + "3")
copy(sha1(x + "4"), buf[80:100]) // 160 bits of sha1(x + "4")
copy(sha1(x + "5"), buf[100:111]) // 88 bits of sha1(x + "5")

@jbenet But you can only do that when you have the blob (in this case, "foobar"), so it's useless for, for instance, doing Kademlia comparisons when looking for the content corresponding to a sha1 multihash.

Well usually one ends up with a hash by finding it-- it was always generated by someone with the data. And most times the hash used for DHTs and so on is a hash of some data structure (the dag, not "the file"), which needs to be found as well. I'm not sure that use case precludes the thing I mentioned.
But I'm not sure the thing I mentioned is useful in any case

I feel like a fool for arguing with you about this. I'm going to put a pin in it as "maybe I need to understand it better".

Not at all, all of this is useful discussion.

cc @eternaleye for feedback

Honestly, if you need variable-length output longer than the hash, you fundamentally don't want a hash. You want a KDF. @jbenet, your Nov 19 post was basically an attempt at constructing a KDF from scratch, which I strongly recommend against.
Once that's recognized, the sensible options collapse to two, depending on usage:

PBDKF2 - if you're hashing user-sourced passwords for storage, currently aging out in preference to memory-hard functions (Argon2 just recently won the PHC, and is being finalized)
HKDF - HMAC-based Key Derivation Function. Efficient (does only one pass over the IKM), supports both "context" and "salt" parameters, can produce arbitrary length, can be instantiated with any hash.

For the use cases multihash is intended for, HKDF seems to be the only real option.
In addition, I consider it essential that multihash include the target length in the input to the KDF - the reason for this is that, without doing so, an attacker can silently truncate a multihash in order to permit incorrect data to pass undetected.
Honestly, anything that is part of the multihash syntax (and thus out-of-band) should be included in the calculation (in HKDF, as part of the context) to avoid truncation attacks, multi-target attacks on algorithms, algorithm substitution attacks, etc.
Another benefit of using HKDF: It uses a staged API, in which one calls two functions:

Extract(IKM, salt) -> PRK // Extract a fixed-size pseudorandom key from a variable-sized input keying material and a salt
Expand(PRK, context) -> OKM // Expand the PRK into arbitrary-length output keying material, bound to a specific context

This allows doing the expensive part (hashing the data) to be done once, and the cheap part (generating relatively short outputs) to reuse the result of that.

@eternaleye is there a way to do what you described with the following constraints:

all current multihashes remain valid as they are
functions that define how to "get more bits" use that as a default
functions that dont define how to "get more bits" use a well-defined HKDF

Sounds to me like no, given that you think we should add lengths to the input to avoid silent truncation.
BTW silent truncation still has to run up against the expected length value. If the attacker can both modify the expected length value, and truncate it, then they could also modify the hash digest too, so not sure what's won. (in practice there may be attacks that depend on being able to modify only one byte (make the len tiny) instead of many (replace the whole digest with an attacker-chosen one).

Maybe TRTTD here is to define a different function "Multihash HKDF", give it a multihash code and all, which, given some other secure multihash function, constructs a HKDF. the function can embed the multihash code of the sub-function it's using in its digest. For example:
<fn-code-of-mhkdf><length-k><fn-code-of-subfn><digest-of-len-k-minus-1>

As for the original question, "how should a digest_size > hash function's output be handled?", it looks like an error for now.

Maybe TRTTD here is to define a different function "Multihash HKDF"

I would agree with that assessment.

By now the "hash function's output length" is not explicitly known so implementations can't do anything about this case (see #114 for a fix). Given this information I'd say

either multihashes MUST fill the digest length bytes that exceed the hash function's output length with 0x00 bytes and add an explicit warning.
or make this multihashes illegal by definition
or explicitly allow any kind of values in the additional bytes and add an explicit warning.


Big update to R packages!

Added Bioconductor data (annotation and experiment) packages, updated all R package lists, and added a shell script to automate future updates. It seems to work but is big and messy, so may need debugging. I tried not to step on anybody's toes, but did refactor the IRKernel stuff a little to make the format match the others so the script updates it properly. Also renamed the update-related files to update-r-packages.{nix,R,sh} for clarity.
One thing I haven't done yet is run the script on the entire package set, because my machine is terribly slow. Would appreciate if someone could try it and update/report back!

Just noticed I clobbered some changes to generate-r-packages.R involving extra info like snapshotDate. Will work on fixing that.

Apparently there's also been a switch away from CRAN, so more updating will be needed...

Obsoleted by https://github.com/NixOS/nixpkgs/pull/14144.


Add Classpert C++ online course catalog to Videos

This commit adds Classpert to the section “Videos”, with a comprehensive selection of ~ 200 C++ courses (free and paid) from top e-learning providers like Udacity, Coursera, Pluralsight, Udemy, Edx, Treehouse, and Skillshare.

Thank you so much for sharing all this wonderful information !!!! It is so appreciated!! You have good humor in your blogs. So much helpful and easy to read!
Java Training Institute in Pune


Change W605 autofix to use raw strings if possible

Fixes #5061

I'm a little confused about how testing works. Why do both W605_0.py and W605_1.py exist? The line and column numbers in those comments don't seem to be checked. Also I'm assuming ruff magically deduplicates the autofix via #875 or whatever.

I'm a little confused about how testing works. Why do both W605_0.py and W605_1.py exist? The line and column numbers in those comments don't seem to be checked. Also I'm assuming ruff magically deduplicates the autofix via https://github.com/astral-sh/ruff/pull/875 or whatever.

I believe W605_1.py uses CRLF line-endings and so exists as a special-case to ensure that rule handles universal line endings.
The comments in the test files purely exist as documentation -- we only enforce correctness via the checked-in snapshots.

This looks good to me, thank you!


What is the point of this? [React]

Having a  Component is great for handling the UI of initializing the OAuth request. But there's no clear example here on what to do with the response.
Should there be a onAuthStateChange listener in a AuthProvider that wraps around our App? I can't get my AuthProvider to successfully listen for that change in this case.
How else would we listen for a callback using these UI components?

FWIW I wrote a blog post that addresses this: https://medium.com/@seojeek/protected-routes-in-react-router-6-with-supabase-authentication-and-oauth-599047e08163


Ability to Scroll to a Position

It'd be great if there was the ability to scroll to a particular x or y co-ordinate, when a button is clicked, for example.

Usage:
$('.scroll').scrollable().moveY(value);
$('.scroll').scrollable().moveX(value);


Supporting k8s labels as filters

I think adding a filter to accept a key / value pairs based on a kubernetes label and its value to the PolicyReports and ClusterPolicyReports might be a good feature.
Our desired use case is to enable e.g. filtering issues by teams or by applications assuming we have an owner and an app labels on the report objects.
What do you think?

Related to https://github.com/kyverno/policy-reporter/pull/230
The UI implementation would look like:
Configuration:
labelFilter: ["app", "owner"]

@fjogeleit any news on the next release date?

Hey, sorry for the delay. I finalize another feature. So it will be in the next two days


Update links to the slf4j-api Javadoc

It should have been updated in v0.10.43, but overlooked.

Thanks!


Add support for 'in' and 'sqrt' operators in expressions

This PR implements two new operators taken from the MapBox style spec:

in takes two arguments: a "needle" and a "haystack", and will return true if the haystack contains the needle; currently has the following limitations:

cannot be used to check the presence of a substring in a string
only supports array literals as haystack:

for instance, this is valid since it can be identified as a number array:
['in', ['get', 'factor'], [2, 5, 10]]
this will fail because a string array can either be an array literal or an expression:
['in', ['get', 'type'], ['road', 'path', 'street']]
to disambiguate a string array literal, use the literal operator:
['in', ['get', 'type'], ['literal', ['road', 'path', 'street']]]
lastly, this will throw an error since dynamic haystacks are not yet supported:
['in', ['get', 'type'], ['var', 'supportedTypes']]

sqrt: self explanatory

The current limitations on the in operator will be really hard to work around with the current system. On the other hand, the approach introduced in #14780 will give much more flexibility and should help remove this limitations. As a result I figured I would not invest too much efforts in the current system, and the in operator as it is should already be very helpful for static filtering.
Addresses https://github.com/openlayers/openlayers/issues/11765, https://github.com/openlayers/openlayers/issues/11308, https://github.com/openlayers/openlayers/issues/13739
Replaces https://github.com/openlayers/openlayers/pull/11839

The layer-mapbox-vector rendering test was failing, it was apparently close to the threshold for a while. I assume this is because of various improvements related to style parsing in ol-mapbox-style, so I updated the expected render. @ahocevar does that make sense to you?

I re-read https://docs.mapbox.com/mapbox-gl-js/style-spec/expressions/#type-system and I'm realizing that we're drifting away from the type system used in mapbox styles. For example in this PR the in operator shouldn't just assume that the haystack is a literla array, there should be a literal operator to declare that explicitly, otherwise later on we will not be able to support dynamically-computed haystacks (e.g. ['in', ['get', 'type'], ['var', 'allowedTypes']]).
Would be curious to hear other's opinions on this!

I re-read https://docs.mapbox.com/mapbox-gl-js/style-spec/expressions/#type-system and I'm realizing that we're drifting away from the type system used in mapbox styles. For example in this PR the in operator shouldn't just assume that the haystack is a literla array, there should be a literal operator to declare that explicitly, otherwise later on we will not be able to support dynamically-computed haystacks (e.g. ['in', ['get', 'type'], ['var', 'allowedTypes']]).
Would be curious to hear other's opinions on this!

My opinion is that we should require that literal operator, just like plain Mapbox style.
As you said, that is a requirement to support haystacks defined by an expression.

My opinion is that we should require that literal operator, just like plain Mapbox style.
As you said, that is a requirement to support haystacks defined by an expression.

Changed the implementation to require disambiguation in case of a string array literal, using literal as per the Mapbox spec. This is all a little bit hackish for now, as I said I'm looking forward to switching to the approach in #14780 to have greater flexibility in implementing operators.

Thanks for the work on this.


How to get figure6 in the paper?

Hi, @yzd-v
How you draw figure 6 in the paper? can you give me some suggestions on it?
Do you draw this figure by mmdet's tool? Because this style figure has been appeared in previous papers too.
Thanks

You can use the codes in tools/analysis_tools to draw it.


📝 (Loki): Add loki example and template to standalone conf

I forgot to add it from in previous PR

up :)

@claudusd seems safe to merge


🐛 [cloud firestore] Unable to connect to firestore when adding google_ml_kit on pubspec.yaml.

Bug report
When I add google_ml_kit to pubspec.yaml, my firestore project is unable to connect to firebase. Firebase auth is still working but I cannot get/set any data to firestore. It's said that my phone is offline and it's getting data from my local cache. I haven't used anything from google_ml_kit in my code, only adding it to my pubspec.yaml and pub get. This is the message I got:
W/Firestore(12540): This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.
Steps to reproduce
Steps to reproduce the behavior:

Make a firestore project with flutter.
Make sure that your project has been connected to firestore and can obtain any data from it.
Add google_ml_kit package to your pubspec.yaml.
Pub get.
Recompile the app and run.

Sample project (Only 1 page: main.dart)
import 'dart:developer';

import 'package:cloud_firestore/cloud_firestore.dart';
import 'package:firebase_core/firebase_core.dart';
import 'package:flutter/material.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();

  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);
  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      debugShowCheckedModeBanner: false,
      home: MainPage(),
    );
  }
}

class MainPage extends StatelessWidget {
  const MainPage({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: ElevatedButton(
            onPressed: () async {
              DocumentSnapshot doc = await FirebaseFirestore.instance
                  .doc('users/eAOtmr9GxQRyTEb3bqQK') // Change the path with any of your firestore document path
                  .get();
              log('${(doc.data()! as Map<String, dynamic>)['name']}');
            },
            child: const Text('Get Data')),
      ),
    );
  }
}

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.0.1, on Microsoft Windows [Version 10.0.22000.675], locale en-ID)
[√] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[√] Chrome - develop for the web
[X] Visual Studio - develop for Windows
    X Visual Studio not installed; this is necessary for Windows development.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2021.1)
[√] VS Code (version 1.67.2)
[√] VS Code, 64-bit edition (version 1.67.2)
[√] Connected device (4 available)
[√] HTTP Host Availability

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.17.1
Flutter SDK 3.0.1
test_project 1.0.0+1

dependencies:
- cloud_firestore 3.1.17 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cupertino_icons 1.0.5
- firebase_core 1.17.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- google_ml_kit 0.11.0 [flutter google_mlkit_barcode_scanning google_mlkit_digital_ink_recognition google_mlkit_face_detection google_mlkit_image_labeling google_mlkit_object_detection google_mlkit_pose_detection google_mlkit_selfie_segmentation google_mlkit_text_recognition google_mlkit_entity_extraction google_mlkit_language_id google_mlkit_translation google_mlkit_smart_reply]

dev dependencies:
- flutter_lints 2.0.1 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]

transitive dependencies:
- async 2.8.2 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- characters 1.2.0
- charcode 1.3.1
- clock 1.1.0
- cloud_firestore_platform_interface 5.5.7 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 2.6.16 [cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- collection 1.16.0
- fake_async 1.3.0 [clock collection]
- firebase_core_platform_interface 4.4.0 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.6.4 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- google_mlkit_barcode_scanning 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_commons 0.2.0 [flutter]
- google_mlkit_digital_ink_recognition 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_entity_extraction 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_face_detection 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_image_labeling 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_language_id 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_object_detection 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_pose_detection 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_selfie_segmentation 0.0.1 [flutter google_mlkit_commons]
- google_mlkit_smart_reply 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_text_recognition 0.3.0 [flutter google_mlkit_commons]
- google_mlkit_translation 0.3.0 [flutter google_mlkit_commons]
- js 0.6.4
- lints 2.0.0
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.4
- meta 1.7.0
- path 1.8.1
- plugin_platform_interface 2.1.2 [meta]
- sky_engine 0.0.99
- source_span 1.8.2 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.0 [charcode source_span]
- term_glyph 1.2.0
- test_api 0.4.9 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- vector_math 2.1.2

This probably need to be reported in dedicated repo: https://github.com/bharat-biradar/Google-Ml-Kit-plugin/issues.
Also, for the error you are getting, refer this : https://github.com/firebase/flutterfire/issues/2753
Closing from here. If you get redirected here or think this is an issue with cloud_firestore plugin, write in comments and I'll reopen it.


Error in readme -> Parse and verify token exemple

In Parse and verify token exemple line 12.
is actually golang err = verifier.Verify(token) but is doesn't work because Verify Need two arguments.
We can replace with golang err = verifier.Verify(token.Payload(), token.Signature())

Hi @DipandaAser sorry for the trouble. Yes, I've merged README for the upcoming v4 slightly earlier, so for now (v3) it's verifier.Verify(token.Payload(), token.Signature()) as you've mentioned.
I will update README or if you want to you can make a PR.

Hi @DipandaAser sorry for the trouble. Yes, I've merged README for the upcoming v4 slightly earlier, so for now (v3) it's verifier.Verify(token.Payload(), token.Signature()) as you've mentioned.
I will update README or if you want to you can make a PR.

Okay i will make a PR @cristaloleg

Okay i will make a PR @cristaloleg


Translation

How cool would be a site translated to your own language?
Imagine OpenSprites in Hebrew? If your native language is Hebrew, why not translate it to your own language? Well its not possible right now.
We should create a transifex for our site so people can translate it. https://www.transifex.com/

Someone move this to JIRA please.
Good idea though.

I could help with French. :P


Support issuing requests to a known SocketAddr

Client currently only supports issuing requests to Uris (which must be parsed from strings), and automatically performs DNS resolution on them. While this is convenient, in some applications the exact address of the remote host is already known. For those cases, passing in a SocketAddr directly would be considerably less error-prone and more efficient.

You can stick the IP address into the URI and no DNS resolution will be performed.

Sure, but this is Rust; we shouldn't have to round-trip that information through a string.

I mentioned in #1174 that we're probably under-utilizing the ClientProto onion, which should probably allow getting a transport for anywhere, and into hyper's Client. If we can figure out how to improve on that without breaking changes to tokio or hyper, we could move towards that within hyper 0.11!
I really want number 1 to happen, but for the moment, the string conversion and back is pretty small compared to the network IO.

Would it make sense to repurpose this issue to track what I said about the ClientProto onion?

I really want number 1 to happen, but for the moment, the string conversion and back is pretty small compared to the network IO.

It's not about performance so much as robustness. There are far fewer moving parts if you keep data in its native format.

Would it make sense to repurpose this issue to track what I said about the ClientProto onion?

If you think that's the way to go and it subsumes this specific concern, I have no objection to that.

I've given this some more thought, and don't see a solution to this, really.
Assuming the server identifies as the socket address, the string version needs to be sent as the Host header in HTTP/1, and as the :authority header in HTTP/2. If the server identifies as a domain instead, then you need to include the domain in the Uri so hyper can write it. Either way, a Uri is needed.
Considering that, and that resolving and connecting to a socket isn't actually something hyper is particularly interested in (it just wants to implement HTTP over some IO object, connectors can be implemented to do anything), I don't see a specific problem that this issue would be solving.


Refactor v0.2 - hand over control to the user

The various parameters each API provider expects can vary greatly (i.e. prompt caching in anthropic, min_p sampling methods in vllm, etc.).
I'm expecting the supported spec differences between API providers to diverge even further (especially when small local or self-hosted models get good eventually)
The key idea is to make it as easy as possible to retrieve data, pipe it straight into an API, and send the outputs somewhere in your nvim buffer without shooting yourself in the foot with the quirks of nvim.

want a new feature? write your own variation of invoke_llm
want better api features? add a new preset with custom options
want better prompts? write your own templates (or pipe some more data into a custom make_data_fn)

after rewriting this plugin literally 5 times by now, it's now very clear that model + prompts + api spec + feature set are all very tightly coupled together. what I actually want for myself is a simple way to implement the whole stack of sub-components from scratch and package it together in a preset.
With this refactor, it's relatively easy to add entirely new features without touching the core of the plugin. (i.e. prompt caching, custom params, or fast + slow retrieval)

Vim(undojoin):E790: undojoin is not allowed after undo stack traceback

never have to see this mf again 🔫

+300 LOC from adding separate specs
+100 LOC from the vllm chat template (it sucks and i need to fix it)
+100 LOC from listing out all the presets
all in all, it's more concise and less messy to read now that all the state stuff is handled in presets.lua


Changeset shows part of a way twice / once as new way

Preamble: This tickets probably belongs to either "OSMCha python library" or to "OSM Compare" but I don't know which so I will add it here, frist. Please feel free to move it to the right repository.

(Maybe) Bugreport:

The changeset edits a longer street which is also part of a bus relation https://osmcha.mapbox.com/changesets/75630467/?aoi=aa999729-e5f4-408a-914b-b7318f6b2b16.
The "TAG CHANGES" summary shows only changes, nothing new.
But the map shows a segment of road as green
When I click this segment, the "tag details" inspector shows all tags in green – as if its a new segment

However (its a bug?)

In the editor, everything looks fine https://www.openstreetmap.org/edit?way=734230432#map=18/52.47722/13.44959 > I cannot see the two overlapping ways?
In archavi everything looks fine https://overpass-api.de/achavi/?changeset=75630467&relations=true > I dont see the newly added way that osmcha shows

However (its not a bug?)
On the other hand …

I can see both new segments that osmcha shows in deephistory as new roads https://osmlab.github.io/osm-deep-history/#/way/734230431, https://osmlab.github.io/osm-deep-history/#/way/734230432 > Apparently they are there but iD and Archavi don't show them?

Conclusion
Can someone see what is going on here.
Depending on the answer there are possible follow ups to improve the UIs.
Thanks

Update
I think with the help of !bm I understand now, what I missunderstood before:
Example: https://osmcha.mapbox.com/changesets/75632823/
When I change a geometry, OsmCha shows the previous (yellow) and the new (teal) line/way.
In those cases, the yellow includes also the teal.
Thats why it looked to me, if there are now two overlapping highways.

I will close this, since its not a bug, just me not understanding things fully :-).


Understand & implement code coverage for the library

Done with https://github.com/Azure/azure-sdk-for-js/pull/1132


Cannot run with sound null safety

Error: Cannot run with sound null safety, because the following dependencies
don't support null safety:
package:flutter_audio_query

If you still wish to run the app without sound null safety you can add this line to your project's lib/main.dart file where your main() function exist, once the package is upgraded to null safety you can remove this line.
// @dart=2.9
Here's an example;
// @dart=2.9
import 'src/my_app.dart';
main() {
//...
}


ADAP ALigner

Basic information

My operating system and version: Windows 11
My MZmine version: MZmine 3.9.0

What happened

Please describe what happened and how it differs from what you expected to happen: I am trying to align my feature lists using the ADAP aligner (GC) and I get an error ... I am running GC-msd data (low resolution) from Agilent, which I converted into .mzML format. I am novice with MZmine, so I hope the parameters I selected based on online documentation are acceptable ...

Please include all parameter values for the MZmine modules you used : Here the parameters I used for every steps ...

Please upload screenshots of any errors and your log/mzmine.log file.

Please upload a standalone MZmine project file (or a batch + raw files) that demonstrates the problem you are reporting.** You can use Google Drive, Dropbox, or a similar repository to upload the project.
I will download it later if required if it is OK for you!

Issues opened without an example project are unlikely to be processed

@Pamou14160 Thank you for reporting this. I'll check this bug.

Do you think I can move forward with my data without alignment? That is, can I continue with the annotation? Thanks!

@Pamou14160 I just saw your message. If you continue the workflow without the alignment, then you'll 81 files with mass spectra, and up to 81 different annotations for each signal. So I wouldn't recommend continuing without the alignment, unless you are prepared to deal with multiple annotations.
As an alternative, you can try running "Hierarchical aligner (GC)" instead of "ADAP aligner (GC)", while I'm working on fixing the algorithm.

@Pamou14160 I tried running the same steps on my own data, and the alignment complete successfully with no errors.
Could you share your raw data, so I could reproduce the error?


Access to all props

It would be nice to have access to all props at this point to expose arbitrary state, e.g. Flux context.
https://github.com/rackt/react-router/blob/master/modules/experimental/AsyncProps.js#L232

like what?


When there are Chinese characters in the route param, the route navigation does not behave as expected

Environment

Operating System: Windows_NT
Node Version:     v18.16.1
Nuxt Version:     3.7.3
CLI Version:      3.9.0
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      modules, colorMode, gtag, googleFonts, i18n, routeRules, nitro, build
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-uxy1hj?file=pages%2Fsearch%2F[keyword].vue
Reproduction Steps

Go search page
Enter English word and click Search button
Enter another English word and click Search button again
Click "Go back" button twice to Home page
Go search page again
Enter Chinese word(你好) and click Search button
Enter another Chinese word(有问题) and click Search button again
Click "Go back"

At this time, no matter how many times I click, I can’t return to the home page.
Not only that, but if I enter any other text to search, nothing happens.
If I delete strategy: 'no_prefix' in nuxt.config.ts, it's work.
Another Reproduction
https://stackblitz.com/edit/nuxt-starter-jrhocc?file=pages%2Fsearch%2F[keyword].vue
Reproduction Steps

Click the button to switch language, and make sure there is a cookie with key lang
Click "Go search page"
Enter something and click Search button

Nothing to change, if set detectBrowserLanguage.useCookie to false, it's work, or if the route param is an English word, it's work too.
Describe the bug
See Reproduction Steps
Additional context
No response
Logs
No response

This issue seems to be fixed by #2518, updated reproduction here. Let me know if you're still experiencing this issue after installing the edge channel!

It's work, thanks


Update libcrowds-viewer ... Help.vue to be aware of config options for e.g. edit selection

Also check it's working for e.g. browse tasks

Moved to the next milestone so as not to delay today's release!


column is of type timestamp but expression is of type character varying

Environment
Knex version: 0.14.6
Database + version: Redshift
OS: AWS
Bug
I am selecting rows from tableA and inserting the resulting rows into tableB, using knexJS. Both tableA and tableB have identical schemas in a Redshift database.
Column names and types
id - int
created_date - timestamp without timezone

Code

knex(tableB)
  .insert(function() {
      this.select()
          .from(tableA)
          .whereRaw('id=?', ['12345']);
  });

Error
This code runs into the error below
error: column \"created_date\" is of type timestamp without time zone but expression is of type character varying

How to fix this in code?

What kind of query are you trying to create?
maybe this one:
knex('b')
  .insert(knex.raw("?", [
      knex.select().from('a').whereRaw('id=?', ['12345'])
    ])
  ).toSQL();

https://runkit.com/embed/swe24d21lh8g
closing as knex seems to create expected query here.


unable to setup indexers","error":"no matches for kind "Tenant" in version "capsule.clastix.io/v1beta1"","stacktrace":"main.main\n\t/workspace/main.go:228\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:225

It doesn't look like I can access Clastix slack workspace, as announced here.
Bug description
Controller manager doesn't want to start due to liveness probe failing
How to reproduce
Brand new helm installation following the instructions (after helm uninstall.... of an old capsule version)
Expected behavior
to just deploy fine
Logs
  Normal   Scheduled  31m                  default-scheduler  Successfully assigned capsule-system/capsule-controller-manager-7f778445cf-ppwcd to ops-k1n03t.domain.de
  Normal   Pulling    31m                  kubelet            Pulling image "quay.io/clastix/capsule:v0.1.0"
  Normal   Pulled     30m                  kubelet            Successfully pulled image "quay.io/clastix/capsule:v0.1.0" in 5.966040477s
  Warning  Unhealthy  30m                  kubelet            Liveness probe failed: Get "http://<IP_ADDRESS>:10080/healthz": dial tcp <IP_ADDRESS>:10080: connect: connection refused
  Normal   Killing    30m                  kubelet            Container manager failed liveness probe, will be restarted
  Normal   Created    30m (x4 over 30m)    kubelet            Created container manager
  Normal   Pulled     30m (x3 over 30m)    kubelet            Container image "quay.io/clastix/capsule:v0.1.0" already present on machine
  Normal   Started    30m (x4 over 30m)    kubelet            Started container manager
  Warning  Unhealthy  30m (x4 over 30m)    kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:10080/readyz": dial tcp <IP_ADDRESS>:10080: connect: connection refused
  Warning  Unhealthy  30m (x3 over 30m)    kubelet            Liveness probe failed: Get "http://<IP_ADDRESS>:10080/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Warning  BackOff    56s (x138 over 30m)  kubelet            Back-off restarting failed container

Additional context

Capsule version: 0.1.0
Helm Chart version: capsule-0.1.3	0.1.0
Kubernetes version:

[root@ops-k1m01t ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7", GitCommit:"132a687512d7fb058d0f5890f07d4121b3f0a2e2", GitTreeState:"clean", BuildDate:"2021-05-12T12:40:09Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7", GitCommit:"132a687512d7fb058d0f5890f07d4121b3f0a2e2", GitTreeState:"clean", BuildDate:"2021-05-12T12:32:49Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}

Hi @titansmc, please, reach out to me using any social (Twitter or LinkedIn) so we can give access to our Slack workspace!
I think this could be a duplicate of #408, or at least related: the helm uninstall doesn't clean up the Custom Resource Definitions, and that's good since that would mean you're going to delete all the Tenant and with that all the Namespaces attached to it.
However, when performing a new installation of Capsule, since the CRDs are already there, these are not going to be updated: this process must be performed manually due to some design decision put in place by Helm.
This discussion occurred here and with #408 we're planning to document the migration process. If it's ok for you, I would close this and eventually suggest you follow the new issue which will lead to a new PR with all the detailed steps for this topic.

you are right. For now I have just manually deleted the CRD and start over, I just need to keep going , in order to test the product


Route not defined, even if it is.

Ia have this line in routes.php
Route::resource('travel_management', 'TravelMangementController');
| GET|HEAD                       | travel_management                                      | travel_management.index        | App\Http\Controllers\TravelManagementController@index         | localeSessionRedirect,localizationRedirect,auth  |
| POST                           | travel_management                                      | travel_management.store        | App\Http\Controllers\TravelManagementController@store         | localeSessionRedirect,localizationRedirect,auth  |
| GET|HEAD                       | travel_management/create                               | travel_management.create       | App\Http\Controllers\TravelManagementController@create        | localeSessionRedirect,localizationRedirect,auth  |
| GET|HEAD                       | travel_management/{travel_management}                  | travel_management.show         | App\Http\Controllers\TravelManagementController@show          | localeSessionRedirect,localizationRedirect,auth  |
| DELETE                         | travel_management/{travel_management}                  | travel_management.destroy      | App\Http\Controllers\TravelManagementController@destroy       | localeSessionRedirect,localizationRedirect,auth  |
| PUT|PATCH                      | travel_management/{travel_management}                  | travel_management.update       | App\Http\Controllers\TravelManagementController@update        | localeSessionRedirect,localizationRedirect,auth  |
| GET|HEAD                       | travel_management/{travel_management}/edit             | travel_management.edit         | App\Http\Controllers\TravelManagementController@edit          | localeSessionRedirect,localizationRedirect,auth  |

and, when I use this code
{{ link_to_route('travel_management.show', $travel->name, $travel->id) }}
I got this error
Route [travel_management.show] not defined.

Did you recacache the routes|?

What do you mean?
I didn't do anything special.

Where abouts do you write that code please?

Where I write the code with link_to_route? In resources\views\company\travel_management\show.blade.php
By the way, I noticed the problem comes from putting routes into this route group
Route::group(['prefix' => LaravelLocalization::setLocale()], function() {
    Route::resource('travel_management', 'TravelManagementController');
});

Seems that it makes a conflict with LaravelLocalization package.

I think the prefix is changing the name.

You can't call LaravelLocalization there. because the routes are evaluated once, before the request comes in, infact, at CLI.

Is there a way to not prepend the prefix in the route names?


There is no docs_src folder

ah, ok, the README.md was outdated. Fixed now. Please proceed to  https://github.com/fastai/fastai.


Export: KHR_materials_specular and KHR_materials_ior

Adds support for the specular, specular tint and ior properties of the Principled BSDF node. The values are converted to KHR_materials_specular (KhronosGroup/glTF#1719) and KHR_materials_ior (KhronosGroup/glTF#1718). The conversion is explained in this comment.
This is more a proof-of-concept prototype than an actual implementation. Baking several properties into textures doesn't seem to fit nicely into the codebase at the moment, it probably needs to be refactored a bit.

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

@proog128 Did you see that some automatic tests failed?

I rebased to master. It should work, but it still lacks testing and refactoring.
Especially test scenes with different combinations of textures on/off per slot would be nice. This is definitely a weak spot in the current (hacky, proof-of-concept) implementation.
So far, the exporter had to rewrite texture channels to match the glTF spec (e.g., metallic into B channel, roughness into G, and so on). With the new glTF PBR extensions, this becomes more complicated. It's not only about copying channels, but also applying some math and doing that conditionally based on whether a texture slot is filled or empty. This is (obviously) not well supported in the current architecture of the exporter, so a refactoring from someone more familiar with the exporter code base would be highly appreciated! I am happy to answer any questions.

@proog128

So far, the exporter had to rewrite texture channels to match the glTF spec (e.g., metallic into B channel, roughness into G, and so on)

Do you mean that there is currently some case where we export some non valid glTF files, not following the spec? Do you have some example?

Do you mean that there is currently some case where we export some non valid glTF files, not following the spec? Do you have some example?

No, the exporter writes spec-conformant glTF files, without and with this pull request. It just becomes more complicated when taking specular and IOR into account. Reason is that the mapping from Blender's specular parameters to glTF's specular parameters involves some computations, not just channel mapping.
For the non-textured case, the mapping is rather simple, it can be found in gltf2_blender_gather_materials.py, line 434. For the textured case the mapping is in gltf_blender_gather_images.py, where I added the FillSpecularColor class for this purpose. The textures are collected here and later, in the encode step, the same equations as before are applied to the textures via numpy, see line 289.

Hey, I would also love for this to be added! Is there any time frame for getting this in and is there anything I can do to assist? Thanks!

Hello,
Some update from my side, and some questions:

I just wrote a generic way to manage complex numpy calculation. Currently, there is only one way to manage texture : Mapping channels from source to destination. I added some generic way to get data from source (Image and/or scalar), and use them to generate an image. Regarding list of sockets, solution used (mapping or specific) is chosen. (code not pushed yet)
Next step is now to fit the specular calculation into this generic system.

Some question about @proog128  's implementation:

I can see specularColorFactor and specularColorTexture, but what about specularFactor and specularTexture ?

Seems there are not implemented in current PR
Because specularColorTexture is RGB and specularTexture is A, is that a good idea to export a single RGBA texture?

Let's open the discussion about how we are going to manage importing KHR_materials_specular extension ...

@julienduroure Really great that you are picking this up!

I can see specularColorFactor and specularColorTexture, but what about specularFactor and specularTexture ?
Seems there are not implemented in current PR

Both specular and specular color are implemented, see for example here and here. But there were multiple changes in the spec while and after I wrote the code. Therefore, there could be naming issues (e.g. sometimes specular color is called specular tint).
Btw. here is a comment in which I wrote up how to convert from Principled to glTF. Maybe it helps in understanding what the code does. Not sure if it is still up-to-date, but it definitely captures the general idea.

Because specularColorTexture is RGB and specularTexture is A, is that a good idea to export a single RGBA texture?

Splitting the texture into specular and specular color textures was a late addition to the spec. Nevertheless, even though the spec allows to have separate textures, it encourages the use of a single texture if both specular color and specular are textured. This is possible because specular is stored in A and specular color in RGB channels.

Thanks @proog128 for feedback.
What I mean about "not implemented" is that, in your current draft implementation,  Blender specular, Blender specular tint, Blender IOR and Blender transmission are used to calculate glTF specularColorFactor and glTF specularColorTexture.
But it seems that glTF specularFactor and/or specularTexture are never exported.
I am not really confident about my understanding of rendering equations/conversion, so I am not sure exactly how it works, and I would like to understand why these 2 parameters are not exported.
For info, here is the PR with current implementation (with basic conversion based on your own PR) : #1646

Blender Principled BSDF does not have an equivalent for glTF specular. Therefore, the exporter keeps glTF specular at its default of 1.
specular in Blender Principled BSDF modifies f0 of the Fresnel equation.
specular in glTF modifies the overall (directionally independent) strength of the reflection effect. When using a Schlick Fresnel (as it is done in most glTF PBR implementations), this corresponds to modifying f0 and f90 simultaneously.
glTF also has the option to modify only f0, but it is called specular color. Thus, Blender specular is mapped to glTF specular color.

Ok, thanks @proog128 .
You answer leads to another question: How to handle import :

glTF can use RGB specular color, where Blender uses only tint. So there will no 100% compatibility. What I did currently:

For texture, use RGB to BW node (I didn't check how this is done internally)
For Factor, use luminence to convert from Vec3 to scalar

SpecularColor import conversion probably need some update to be more accurate ?
How to handle glTF specularFactor and glTF specularTexture?

Is there a way to manage it correcty, or how can we approximate as best as possible?
Some example : How to manage specularFactor 0.0 ?

I created a notebook showing the conversions here  (Interactive notebook on Colab). Maybe it helps!

SpecularColor import conversion probably need some update to be more accurate ?

Using luminance is ok, I guess. Maybe it's possible to optimize the perceived conversion result, but I haven't thought about it yet.

How to handle glTF specularFactor and glTF specularTexture?

In the general case: not possible. For some edge cases it can be approximated, for example if specular_gltf == 0 and transmission_gltf == 0, then specular_blender = 0. But that's only a special case if specular is near zero. In the general case, specular_gltf cannot be mapped to Blender.
Special handling for these edge cases breaks round-trip conversion and may look strange in combination with textures, so I am not sure if it's a good idea...

Thanks a lot. I will have a look soon

We can now close this PR, as specular is now managed in master by merging #1646


docs: Browser setup: Add working webpack 5 setup

@janpieterz Do we still need this? Is Webpack going to be an issue with the removal of wasm bundling of Okapi?

@janpieterz Do we still need this? Is Webpack going to be an issue with the removal of wasm bundling of Okapi?

In theory, no we won't need it. I'll add that confirmation to my milestone.


hover_node.jstree {html: true}

what is the proper way to make the tooltip show as html?
}).on("hover_node.jstree", function (e, data) {
$("#{0}".format(data.node.id)).prop({title: data.node.text, html: true});
}

This is not jstree related - it depends on what tooltip library  you use. As far as I know the built in browser tooltips can not contain HTML.


Update the design for this website?

Hi, I'm a strong supporter of BEM methodology and I'd like to contribute to spreading the word about this approach.
I'm a UX Designer with front-end skills and I'd be really do a small lifting for the website, so that it communicates the BEM idea even better.
Here are some suggestions that I'd like to implement

rebuild the site in static html so that it can be hosted directly on GitHub pages, so that it's more easy to update and maintain
redesign the frontpage so that it immediately feels like code-related site
-- more screenshots
-- more to-the-point examples of classic CSS vs. Bem, provide real-life cases when bem is better
-- show visually how to use it with SASS
-- advertise how good it is for RWD
expose the logo better
use BEM correctly on the website code itself, as I noticed there are some small non-BEM styles in the current website CSS

I'm a strong supporter of BEM methodology in practice, so I'm sure I can contribute and provide small tweaks to the methodology itself.
@floatdrop @iamstarkov let me know if you're open to such contributions.

I would like this update too. When I google for BEM to show someone quickly what is it and I land on http://getbem.com/ - there is zero useful information there plus it's really not obvious that I've landed on a proper page. What I would prefer to see this piece of code example on top of the page:
.parent-block__child-element--fancy-modifier

Because it is pretty easy to display most of the BEM features with just a single selector.


[WIP] Logic, Model, UI: New find format + clickable tags

This pr aims to introduce a new find format. It is an AND find.
find n/NAME p/PHONE e/EMAIL a/ADDRESS t/TAG

It supports multiple arguments ie find t/friend t/colleague
It allows for white space ie find n/Nicholas Chua t/scrub
comparison follows field.toLowerCase().contains(keyword.toLowerCase()

TODO:

Testing for GUI, im sorry i'm going to KO. But we can demo this

Coverage increased (+0.2%) to 89.329% when pulling 4e081c8619c88331daf07b89eb6285fed5faa934 on nicholaschuayunzhi:find-details into 9587ae58bc7dfdc3463594ca7171421b4137c6a4 on CS2103AUG2017-W11-B4:master.

Coverage increased (+0.6%) to 89.699% when pulling 90c53a94e53761782048e0690f6f91f82f94b970 on nicholaschuayunzhi:find-details into 9587ae58bc7dfdc3463594ca7171421b4137c6a4 on CS2103AUG2017-W11-B4:master.


PieCharts disappear

Worked nicely, but there is an issue.
PieChart.Series = new ObservableCollection
{
//if you add more than one serie to pie chart, they will be overridden
new PieSerie
{
PrimaryValues = new ObservableCollection { 8 },   // Only one component
Labels = standardLabels
}
};
=> Then the chart animates and disappears.

this fixed the problem, but now we got a new issue because I think we should get a full circle not this;

I will let this issue open so we can review that later. thanks

I will close this since is a opinion based enhancement, and not a primary goal


fix: mv and cp for renaming with single source

Summary
Previous PR accidentally removed cp (and mv) functionality to rename the file when given a single source file. Added more testing examples to more rigorously test this.
Continues work for #109

Added check to see if the number of arguments is sufficient to attempt renaming the file
Change the destination directory to be everything except the renamed file

Test Plan
https://user-images.githubusercontent.com/13056466/209738825-9e753222-3768-4220-961a-e175a0f6c922.mov
More rigorous testing (Potato quality because video too large, sorry)
https://user-images.githubusercontent.com/13056466/209739573-083df171-4d71-49bd-8613-4362e44182a9.mov

Wait don't merge this yet or even review it! Still broken after some testing. Will be fixing

Wait don't merge this yet or even review it! Still broken after some testing. Will be fixing

Fixed! Let me know if you see any issues.


BDI - Help text mapping with a valid core object prefix with an invalid field name will return an error when processing

If an invalid helptext mapping is created, the DIs fail to process even if that field is not used.
Having a help text mapping with a valid core object prefix such as Opportunity or Payment, but an invalid field name, BDI will return an error when processing a DI, even if the field isn’t being used in your DI. The error from that failing DI is appearing on every other DI on batch
Pre-conditions:

Having an invalid help text mapping

Steps:
1- Create a new DI
2- Save
3- Attempt to process
Expected result: Before, we were letting the DI process with no errors but the value wasn’t being mapped due to the invalid help text mapping
Actual result: Unfriendly error from image, DIs fail in batch and the error is added to other DIs in batch.

Edited by CCE - CO

**lurch: attach W-035654

**lurch: attach W-035654

Tracking W-035654

Closed as help text mapping has been deprecated in favor of Advanced Mapping.


Adopt proposed telemetry API

I had to set the log level to trace before the telemetry output channel showed. @lramos15 is it supposed to work this way? The message at the start of the output channel makes me think that the channel is always supposed to be there, just mostly empty until you set trace:
2022-11-29 11:29:07.529 [info] Below are logs for extension telemetry events sent to the telemetry output channel API once the log level is set to trace.
2022-11-29 11:29:07.529 [info] ===========================================================

I had to set the log level to trace before the telemetry output channel showed. @lramos15 is it supposed to work this way? The message at the start of the output channel makes me think that the channel is always supposed to be there, just mostly empty until you set trace:
2022-11-29 11:29:07.529 [info] Below are logs for extension telemetry events sent to the telemetry output channel API once the log level is set to trace.
2022-11-29 11:29:07.529 [info] ===========================================================

It's supposed to work this way, the same way the core telemetry channel works


Terminal: Add Find next/previous key bindings. Fixes: #29661

@Tyriar

Tried my best at naming nomenclature not perfect but matches most things
Went through terminal services like focus and hide commands
Testing both Windows and OS X

Fixes: #29661

Just left a tiny comment about keybindings, it looks good from my side.

OS X Key bindings matched.

See new PR #32074


I have two custom elements extending
:
<polymer-element name="adjl-home-page" extends="article" noscript>
...

<polymer-element name="adjl-about-page" extends="article" noscript>
...

The following fails to render them:
...
<template repeat="{{page in pages}}">

</template>
...

...
this.pages = ['Home', 'About'];
...
toLowerCase: function(value) {
  return value.toLowerCase();
}
...

But inspecting the DOM tree shows that they do get written (it's just that nothing appears):
...

...

My current workaround is to instantiate them individually:
...

...

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


Error

How i need to fix this error?
Running command 'run' for instance 'main'
2017-02-13 22:19:35: start
2017-02-13 22:19:35: Running /home/steam/ARK/ShooterGame/Binaries/Linux/ShooterGameServer TheIsland?RCONEnabled=True?RCONPort=32330?SessionName=ARK\ Server\ Tools?Port=7777?QueryPort=27015?ServerPassword?ServerAdminPassword=keyboardcat?MaxPlayers=70?listen
/home/steam/ARK/ShooterGame/Binaries/Linux/ShooterGameServer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/steam/ARK/ShooterGame/Binaries/Linux/../../../Engine/Binaries/Linux/libsteam_api.so)
2017-02-13 22:19:35: Server PID: 7224
2017-02-13 22:19:40: Bad PID ''; expected '7224'
2017-02-13 22:19:40: exited with status 0

https://github.com/FezVrasta/ark-server-tools/wiki#lib64libcso6-version-glibc_214-not-found

Where can i find? GameUserSettings.ini

and idk i did all the other thing on thad page and still nothing working

Not having at least glibc 2.14 suggests you are using Debian 7 or older, CentOS / RHEL 6 or older, or Ubuntu 11.10 or older.
You need either a more recent distribution (e.g. Debian 8 [Jessie], CentOS 7, or Ubuntu 12.04 or newer), or to compile a newer version of glibc and libgcc.

Is there Not a other way I use debian 7.11

The ARK server requires glibc 2.14
Debian 7 (which was end-of-lifed in April 2016) only comes with glibc 2.13
Therefore either you need to upgrade to Debian 8, or compile glibc 2.14 or newer yourself.

Idk how

https://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html

Is this now good?

Distributor ID: Debian
Description:    Debian GNU/Linux 8.7 (jessie)
Release:        8.7
Codename:       jessie

With your distribution upgraded, ARK should now work.

Server online :D ty for it!


[NEW FEATURE] Added UnsupportedElementName exception

Added a check to ensure the element(s), section name cannot start with a no_. This will raise a UnsupportedElementName exception.

this is my first PR ever, please be gentle :slightly_smiling_face: Please let me know your feedback, happy to make changes and learn. :slightly_smiling_face:

Ok, so we've got it to a state where it's ok. But ironically you've still developed it feature first instead of test first (But that's ok for a first contribution).
So now we have our warnings we have to do 2 more things.
Ensure the warnings are fired, and create a test to validate this. Making sure to use shared examples.
Whilst the files are incorrectly structured. You'd probably want to insert the spec here: https://github.com/site-prism/site_prism/blob/master/spec/site_prism/element_spec.rb#L33 and ensure you test both xpath and css using shared examples - This will be done for you if you use the correct nesting there.

Help: For capturing messages written to an output location use this helper: https://github.com/site-prism/site_prism/blob/master/spec/spec_helper.rb#L35-L42
An example of which is here: https://github.com/site-prism/site_prism/blob/master/spec/site_prism/deprecator_spec.rb#L26-L29

Seems good. You still need to get into the habit of running bundle exec rake locally before pushing, as there's still issues with rubocop

Hi @anuj-ssharma are you still working on this?
If so can you rebase, and fix up the remaining issues. I've also started adding a few more small tasks to the Issues section, if you want to get involved there also.

ping @anuj-ssharma

Hey, @luke-hill  Sorry I just saw your message, apologies for the late response!
Unfortunately haven't been able to work on this, been crazy at work and also my focus has been on python for some time now and didn't really get a chance to jump onto this and complete it.

Ok no worries. Do you think you'll be able to finish this as there's no much left to do.

I've pushed in a commit that resolves the rubocop errors. There's still a cucumber scenrio that fails but I'm not exactly sure why.
https://travis-ci.com/github/site-prism/site_prism/jobs/314239723#L1135


added docs via doxygen

added doxygen documentation
using css from https://jothepro.github.io/doxygen-awesome-css/ (direcly copied to the docs src)
added "examples" logic st. an example section can be added
added ci workflow to:

build the documentation as artifact
upload the documentation to github pages when changes to main are maide

Considerations:

also install documentation
remove examples and add them in different PR or add meaningfull example
consider running examples in CI
Write a bit of text what this repo is about

The docs can be downloaded from the CI summary https://github.com/man-group/sparrow/actions/runs/9710061973?pr=122


Documentation suggests I can do something I cannot

The documentation says,

Calling validate spected(validationRules, inputData) should return

Which would suggest I can do something like this,
const spected = require('spected')

const isGreaterThan = num => num > 5
const hasCapitalLetter = text => /[A-Z]/.test(text)

const validationRules = {
  name: [
    [ isGreaterThan(5),
      `Minimum Name length of 6 is required.`
    ],
  ],
  random: [
    [ isGreaterThan(7), 'Minimum Random length of 8 is required.' ],
    [ hasCapitalLetter, 'Random should contain at least one uppercase letter.' ],
  ]
}

const inputData = { name: 'abcdef', random: 'z'}

const res = spected(validationRules, inputData)

console.log(res)

However, spected is not a function
Just a little kink in the onboarding, which would be good to solve with better documentation!

Ah, I realise this is probably because I did require('spected') instead of require(spected`).default

Yes, require('spected').default should solve the problem. Let me know if there is still trouble.

Thanks @busypeoples! I am encountering an error, but I have created a separate issue for that (easier for newcomers to search)


Clean xWindowsFeatureSet, xWindowsOptionalFeatureSet, and xProcessSet and add tests

Cleaning the remaining Set resources for #160.
Added and updated the integration tests, documentation, and examples for these resources as well.

This change is

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

README.md, line 135 at r1 (raw file):

#### Examples

* [Add members to multiple groups](https://github.com/PowerShell/xPSDesiredStateConfiguration/blob/dev/Examples/Sample_xGroupSet_AddMembers.ps1)

Just noticed that these examples for group need to be updated

README.md, line 435 at r1 (raw file):

#### Parameters

* **[String] Name** _(Key)_: The names of the roles or features that you want install or uninstall. This may be different from the display name of the feature/role. To retrieve the names of features/roles on a machine use the Get-WindowsFeature cmdlet.

'that you want to install or uninstall.'

README.md, line 438 at r1 (raw file):

* **[String] Ensure** _(Write)_: Specifies whether the feature should be installed or uninstalled. To install features, set this property to Present. To uninstall features, set this property to Absent. { Present | Absent }.
* **[Boolean] IncludeAllSubFeature** _(Write)_: Specifies whether or not all subfeatures should be installed or uninstalled alongside the specified roles or features. If this property is true and Ensure is set to Present, all subfeatures will be installed. If this property is false and Ensure is set to Present, subfeatures will not be installed or uninstalled. If Ensure is set to Absent, all subfeatures will be uninstalled.
* **[PSCredential] Credential** _(Write)_: The credential of the user account under which to install or uninstall the role or feature.

'roles or features.'

README.md, line 495 at r1 (raw file):

The following parameters will be the same for each Windows optional feature in the set:

* **[String] Ensure** _(Write)_: Specifies whether the Windows optional features should be enabled or disabled. To enable the features, set this property to Present. To disable the features, set this property to Absent. { *Present* | Absent }.

It looks like Present isn't a default here.

DSCResources/xWindowsFeatureSet/xWindowsFeatureSet.schema.psm1, line 30 at r1 (raw file):

    .PARAMETER Credential
        The credential of the user account under which to install or uninstall the role or feature.

'roles or features.'

Tests/Integration/xWindowsOptionalFeatureSet.Integration.Tests.ps1, line 99 at r1 (raw file):

            foreach ($windowsOptionalFeatureName in $wofSetParameters.WindowsOptionalFeatureNames)
            {
                $windowsOptionalFeature = Dism\Get-WindowsOptionalFeature -Online -FeatureName $windowsOptionalFeatureName

newline before 'It'

Comments from Reviewable

Review status: all files reviewed at latest revision, 6 unresolved discussions.

README.md, line 135 at r1 (raw file):
Previously, mbreakey3 (Mariah) wrote…
Just noticed that these examples for group need to be updated

Huh? This is xGroupSet, not xGroup.

README.md, line 435 at r1 (raw file):
Previously, mbreakey3 (Mariah) wrote…
'that you want to install or uninstall.'

Done.

README.md, line 438 at r1 (raw file):
Previously, mbreakey3 (Mariah) wrote…
'roles or features.'

Done.

README.md, line 495 at r1 (raw file):
Previously, mbreakey3 (Mariah) wrote…
It looks like Present isn't a default here.

Done.

DSCResources/xWindowsFeatureSet/xWindowsFeatureSet.schema.psm1, line 30 at r1 (raw file):
Previously, mbreakey3 (Mariah) wrote…
'roles or features.'

Done.

Tests/Integration/xWindowsOptionalFeatureSet.Integration.Tests.ps1, line 99 at r1 (raw file):
Previously, mbreakey3 (Mariah) wrote…
newline before 'It'

Done.

Comments from Reviewable

Reviewed 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

README.md, line 135 at r1 (raw file):
Previously, kwirkykat (Katie Keim) wrote…
Huh? This is xGroupSet, not xGroup.

nevermind

Comments from Reviewable


Modify text summarization taskflow doc

PR types

Modify taskflow.md
PR changes

Docs
Description

修改了文本摘要taskflow的文档，增加了参数说明

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.fuyanhe seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


16 vulnerable packages

npm audit responds with this:
found 16 vulnerabilities (1 low, 4 moderate, 11 high) in 17109 scanned packages
run npm audit fix to fix 16 of them.

Closing this since it's out of date, and not really an issue with the repo (per se ...)


can @biesbjerg/ngx-translate-extract be installed globally?

Hi
can @biesbjerg/ngx-translate-extract be installed globally?

Sure, that should work

I tried it and it’s not working... keeps asking for dependencies to be installed

Oh, I think I know what's up.
Global install is not supported because it can't reliably parse source code, since it depends on the version of typescript and angular compiler used in the project
More details here:
https://github.com/biesbjerg/ngx-translate-extract/issues/173#issuecomment-609665560

how can I use ngx-translate-extract without it being installed in scripts?

It is not a feature I am going to support for the reasons I linked to. Sorry!


Update packaging to include util and plotting scripts

Should update the package structure to make it easier to access util and plotting scripts.

Updated the installation process, and merged it with the mwlmc branch.


Output of qpfunction is nan

Hello!
I'm trying to add qpth into my learing method. But in traing stage, after a few steps, the output of qpFuntcion is all nan.
But I tried to call qpth in another script and set the input paramater as same as nan's input, the output now is right.
So I want to konw why?
Thanks.

Same with you.


⚠ Bofrost.be has degraded performance

In 42c7ed7, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1424 ms

Resolved: Bofrost.be performance has improved in f13ba04.


runc in version 1.0.2

opencontainers/runc present some security issues (https://github.com/opencontainers/runc/releases), notably CVE  2019-16884 and CVE 2019-19921.
Could you please update it to version 1.0.2 and make a new release ? Thanks.

Hi. This project isn't directly dependant on opencontainers/runc, but it is on fsouza/go-dockerclient, from where comes the dependency. Unless they fix their own dependency on opencontainers/runc, I don't know if we there is something we can do.

I agree on master but tag v0.7.7 https://github.com/nginx-proxy/docker-gen/blob/0.7.7/go.mod tells otherwise. So?

It seems that fsouza/go-dockerclient in version 1.7.2 includes the correct version of docker/docker (v20.10.3) despite listing incorrect version of opencontainers/runc as indirect.
I’m not familiar with go deps. Does this indirect mention have a real impact on what is bundle or is it there just for reference?
If it does have an impact, then yes I will open a issue in fsouza/go-dockerclient about it.
Also why such difference between last tag 0.7.7 and main in go.mod? Do you think it’ll be a good idea to make another release when the runc version is resolved?

Also why such difference between last tag 0.7.7 and main in go.mod ? Do you think it’ll be a good idea to make another release when the runc version is resolved?

Because of #362 that has been merged to main but isn't included in a released version yet. The use of go.mod for this project is relatively new, and we inherited some crap when moving from godeps to go.mod.
I wanted to further clean the structure before releasing this as 0.8.0.

Fixed in versions >= 0.8.1.


Allowing name input for New MultiModels projects through w2prompt (W2UI 1.5) dialogs

Hey @idhugo.
I will launch the application using the branch during the weekend.
I have left a few comments on the naming

Hey @idhugo.
I will launch the application using the branch during the weekend.
I have left a few comments on the naming

A few things:

I think you should remove "Project" from "Multi-Model Project".
If you press cancel when creating a new Multi-Model, then it creates a file called null
If the name already exists, then spawn the prompt again with the possibility of naming the file.

@CThuleHansen  Please check new changes!

@idhugo looks good! Ready to merge from my point of view
@lausdahl @ldcouto looks ok?
@ldcouto will you do the merge?


Cannot find runtime 'node' on PATH.

VSCode Version: Code 1.4.0 (6276dcb0ae497766056b4c09ea75be1d76a8b679, 2016-08-04T16:45:31.680Z)
OS Version: Windows_NT ia32 10.0.10586

Steps to Reproduce:

Open VS
Launch Project

Cannot debug node application. Reinstalled node and VS, added node to PATH. nothing worked.

@UVk could you please launch the 'integrated terminal' in VS Code and  run where node in it. What does it show?

#14229

Im getting this issue now as well.

@wprater could you please launch the 'integrated terminal' in VS Code and run where node (Windows) or which node in it. What does it show?

Getting this issue as well.

Launch VSCode 1.10.0
Click the 'Start Debugging' button on the Debug tab

Mac OSX 10.11.5
Using /bin/zsh as my default shell
Using nvm
Using /bin/zsh in my "terminal.integrated.shell.osx" User Settings.
Doing a which node in the integrated terminal results in : /Users/MNannola/.nvm/versions/node/v4.5.0/bin/node

Same issue on Linux Ubuntu using nvm.
which node
/home/mao/.nvm/versions/node/v6.9.1/bin/node

same issue with VS Code 1.10.2 on MacOS Sierra
$ which node
/usr/local/bin/node

@sebsto @devmao what shell are you using?

@sebsto @devmao @weinand I think the problem is that VS Code doesn't load a fresh environment (eg. run ~/.bash_profile) for each instance of VS Code.  Even when you close all instances of VS Code it will use a cached environment unless you right-click->quit the application.
If you have changed the node version using a manager such as NVM you need to do either of the following:

Quit VS Code completely and re-launch.
Go to the integrated terminal (View->Integrated Terminal) and run the following:
source ~/.bash_profile

I would say this is a bug as you would expect VS Code to reload the environment every time you launch a new window.

VS Code does the right thing. It reads the environment from .bashrc. Verify this by opening Developer Tools and running process.env from the Console.

@joaomoreno Yes is does the right thing (read .bashrc) but wrongly only does this once at startup and not for every new window?

Got it. Duplicate of #15452

@joaomoreno I don't believe this ticket covers this issue.
The ticket explicitly accepts the current behaviour and states "that [new] window will inherit the current process env (which is normal OS X behaviour)".
Although this is not normal behaviour; when you open a new tab on any terminal program you get a fresh environment.

Note that Code isn't a terminal program.
But sure: created an issue for this #23649

I am using nvm and I fixed the issue by adding
"runtimeExecutable": "/Users/x/.nvm/versions/node/v8.1.3/bin/node",
to launch.json.
to find nvm node executable path run which node

Above solution work for me.


Unsubscribe from pubsub when stream disconnect.

Issue
When a client stream disconnect on any listening API, the pubsub should be unsubscribe.
One concerned API: https://github.com/mesg-foundation/core/blob/dev/api/core/listen_result.go#L13

@ilgooz can you confirm that we can close this issue ?

I confirm we have this now. @NicolasMahe can you also confirm!

👍


error display

Type: Bug
in the vscode display there is a dotted libe which is very annoying
VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz (12 x 2688)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
7.77GB (0.87GB free)

Process Argv
--crash-reporter-id 3ab74fef-3474-4690-9a71-e9aa7b96b7d9

Screen Reader
no

VM
0%

Extensions (34)

Extension
Author (truncated)
Version

vscode-color
ans
0.4.5

vscode-tailwindcss
bra
0.9.4

postcss
css
1.0.9

dart-code
Dar
3.56.0

flutter
Dar
3.56.0

prettier-vscode
esb
9.10.3

auto-close-tag
for
0.5.14

isort
ms-
2022.8.0

python
ms-
2022.20.1

vscode-pylance
ms-
2023.1.10

jupyter
ms-
2022.11.1003412109

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.12

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

live-server
ms-
0.4.4

powershell
ms-
2022.12.1

color-highlight
nau
2.5.0

indent-rainbow
ode
8.3.1

material-icon-theme
PKi
4.23.1

vscode-css-peek
pra
4.2.0

java
red
1.13.0

LiveServer
rit
5.7.9

highlight-matching-tag
vin
0.10.1

intellicode-api-usage-examples
Vis
0.2.6

vscodeintellicode
Vis
1.2.30

vscode-java-debug
vsc
0.47.0

vscode-java-dependency
vsc
0.21.1

vscode-java-pack
vsc
0.25.7

vscode-java-test
vsc
0.37.1

vscode-maven
vsc
0.40.2

quokka-vscode
Wal
1.0.520

json
Zai
2.0.2

html-css-class-completion
Zig
1.20.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vscaac:30438847
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
2e4cg342:30602488
iaj6b796:30613358
89544117:30613380
fim-prod:30623723

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Notion Children Length exceeded when parsing large HTML

Notional Version: 0.7.3
Description
On parsing a large HTML document to notion content, I get the following error:
notion_client.errors.APIResponseError: body failed validation: body.children.length should be ≤ 100, instead was 123.
A clear and concise description of what the bug is.
Steps To Reproduce
If html is a reasonably large (eg blog article sized) document, we can reproduce this error like this:
from notional.parser import HtmlParser
parser.parse(html)

Expected Behavior
The html is correctly parsed to notion

@dominiczy Notion doesn't allow you to send >100 children per API request. Use the Append Block Children api and send the content in chunks.


Document versions for load balancer annotations

Is your feature request related to a problem?/Why is this needed

/kind docs
Describe the solution you'd like in detail

Not all annotations are available for all versions, we should document the kubernetes versions for each annotation.
Describe alternatives you've considered

Additional context

Added in #163.


cvc:Email:username should be claimable (creadentialItem:true)

as cvc:Email:domain is claimable (creadentialItem:true), so cvc:Email:username as well. Or am I missing something here?

Wrong assumption, actualy cvc:Email:username is not a creadentialItem, so creadentialItem:false is correct


[KOGITO-239] - Error after building springboot application with lates…

…t ubi8 images
Signed-off-by: Filippe Spolti<EMAIL_ADDRESS>

@spolti have you tested with the s2i CLI as well?

@ricardozanini yes, both working.

Looks good to me (not tested by myself). In case of free time I can try to build and run images tomorrow, but if you want to merge it sooner feel free to do so.

I am working on bahave tests, we can simulate the s2i build.
For openshift we can, maybe, add a pipeline to do some tests on ocp.


keyspace events in a clustered environment

I'm trying to use keyspace events with ioredis in a cluster environment with 2 machines and 4 instances per machine. From what i've read the expired events are emitted on the local node in the cluster and are not broadcasted to the whole cluster, so i'm enumerating every node in the cluster, update the configuration and subscribe to the event. This works if i try to connect  on a dev environment with only one machine, but when I try to connect to the prod environment i get the exception below.
If I wait for the 'ready' event everything seems to work fine.
Does this mean that the connection retry and buffering logic does not work for individual nodes?
How about the auto resubscription on connection failure?
redisSub.on("pmessage", subscriber);
return Promise.all(redisSub.nodes('master').map(function (node) {
  return node.config('SET', "notify-keyspace-events", "Ex").then(function () { <- here
    return node.psubscribe('__keyevent@0__:expired');
  });
})).then(function () {

Error: Connection is closed.
    at close (project\common\node_modules\ioredis\lib\redis\event_handler.js:101:21)
    at Socket.<anonymous> (project\common\node_modules\ioredis\lib\redis\event_handler.js:76:14)
    at Object.onceWrapper (events.js:316:30)
    at emitOne (events.js:115:13)
    at Socket.emit (events.js:210:7)
    at TCP._handle.close [as _onclose] (net.js:549:12)
From previous event:
    at Command.initPromise (project\common\node_modules\ioredis\lib\command.js:63:18)
    at new Command (project\common\node_modules\ioredis\lib\command.js:51:8)
    at Redis.psubscribe (project\common\node_modules\ioredis\lib\commander.js:131:29)
    at project\session\gc.js:68:21
From previous event:
    at project\session\gc.js:67:65 <- here
    at Array.map (native)
    at project\session\gc.js:66:49
    at runCallback (timers.js:781:20)
    at tryOnImmediate (timers.js:743:5)
    at processImmediate [as _immediateCallback] (timers.js:714:5)

A Cluster will create multiple Redis instances, each instance connecting to a Redis server of the cluster. Every instance has retryStrategy set to null, which means ioredis won't auto reconnect when the connection is closed. Instead, ioredis will refresh the nodes in the cluster and create the new instance connecting to the new server.
You may want to listen to the -node and +node event to know when a node is destroyed or created.


[staging] "Results must include all selected file types:" is missing in [Available Files] dropdown filter

Steps to Reproduce

Locate filter panel
Click on [Available Files] filter
Compare dropdown to design

Actual Results
"Results must include all selected file types:" label is missing in dropdown
Expected Results
"Results must include all selected file types:" should be displayed in dropdown
Design

Evidence

label is now displayed in staging, closing this bug... thank you!!!


Create Social sharing options for books.

Create React Social Share Component for Books so as to share them on various social networking sites such as Facebook, WhatsApp, Twitter, etc.
Please assign me the task under GSSOC 23.

we don't need that for now


Add ability to install runtime only

Description:
Added ability to select to install runtime only instead of SDK. It utilizes built-in features of the dotnet-install script by conditionally passing -Runtime/--runtime flag.
Related issue:
https://github.com/actions/setup-dotnet/issues/352
Check list:

[x] Mark if documentation changes are required.
[x] Mark if tests were added or updated to cover the changes.

This switch is cool, but I have another opposite idea, add a sdk-only switch.
Right now by default the runtime is always installed first, then the sdk.
When one wishes to install sdk only, there's really no need to install runtime separately before, since sdk already includes runtime.


Binary size optimizations

This spits the crate into a couple different crates:

encoder: contains everything necessary to encode operations
prebuild: contains a macro to encode the operations into a &'static [u8]. ElementBuilder has a large binary size so this allows users to get the benefit of ElementBuilder but without any of the binary size. This is mostly an example project; any downstream crate will probably use there own macro to generate edits.
web: contains the bindings and re-exports some of

This PR + running swc on the wasm-bindgen generated js files makes the binary size of sledgehammer roughly equal to the wasm-bindgen implementation.


console show error info

Reference to a Thread object object was lost while the thread is still running...

DEBUG: KBEngine::login_loginapp(): connection to <IP_ADDRESS>:20013 successful!
DEBUG: KBEngine::Client_onHelloCB: verInfo(1.2.7), scriptVersion(0.1.0), srvProtocolMD5(E9D9E23CC3D26C5D139E11940870EF79), srvEntitydefMD5(96131AD9DD596C18E9F009B491229B26), + ctype(2)!
DEBUG: KBEngine::onImportClientMessagesCompleted: successful! currserver=loginapp, currstate=login
DEBUG: KBEngine::login_loginapp(): sending login! username=123123a
DEBUG: KBEngine::Client_onLoginSuccessfully: accountName(123123a), addr(<IP_ADDRESS>:20015), datas(0)!
DEBUG: NetworkInterface::reset(), closed socket from <IP_ADDRESS>
Reference to a Thread object object was lost while the thread is still running...
DEBUG: will begin connecting to <IP_ADDRESS>:20015 ...
At: core/bind/core_bind.cpp:2491
DEBUG: NetWorkInterface::_asyncConnect(), will connect to <IP_ADDRESS>:20015 ...


Best Repo EVER!

I am a 'medium' hacker, programmer and OSINT 'hacker'! i was trying hardly to decompress everything to see how the tool was made, speedx knew if the tool was going to be open source, the sms bombing will stop cuz the server overload and security measurings... this repo, made my absolutely MONTH! xD You have my respect!

I appreciate your support, it really means a lot to me. I have to thank you~


Added parameter mq_use_mqcsp_authentication. Check the String value a…

…nd set the corresponding boolean MQConstants.USE_MQCSP_AUTHENTICATION_PROPERTY. Updated README with this parameter.

Hi @freddyschoeters
Sorry for the delay to review it pull request.
I reviewed it and looks good only see some comments lines that we need to remove but I can do it on my branch.
Thank you to be the first person to contribute mqmeter and also to use it.
Regards.


/keybase/Contents is not a keybase folder error

Keybase GUI Version: 1.0.17-20160913233827+18b5a25
Action:
Keybase menu bar icon > Menu > Open folders
Keybase then opens the folders in finder but also sends a notification with the message:
/keybase/Contents is not a keybase folder error. All folders begin with /keybase/private or /keybase/public...

This will be fixed in the next release, thanks.


<EMAIL_ADDRESS>extract_dir error

Receiving this error trying to install git:
PS C:\Users\andre\scoop\buckets\extras> scoop install git
Installing 'git' (2.21.0.windows.1) [64bit]
Loading PortableGit-2.21.0-64-bit.7z.exe from cache
Checking hash of PortableGit-2.21.0-64-bit.7z.exe ... ok.
Extracting dl.7z ... ERROR Exception calling "Start" with "0" argument(s): "The directory name is invalid"

Please try again or create a new issue by using the following link and paste your console output:
https://github.com/lukesampson/scoop/issues/new?title=git%402.21.0.windows.1%3a+extract_dir+error

Similar error happened with alacrity as well.

This usually mean that 7z is having some troubles. Could you normally use it in console?
Something like cd $env:SCOOP\cache; 7z x 'somefile' -o"directory" -y

I suspect it was a broken download. I erased the cache folder and tried again and it worked. Will close this issue. For a while I thought there was something wrong with the recipe.


cabalJs can't find Cabal_1_22_0_0

I have picked transformers as it is the most simple package i could think of to try building with ghcjs. You can find a gist of my default.nix and the output of runing nix-build --show-trace bellow
default.nix
let
  # Here <git> is just some place on my harddrive where i have cloned nixpkgs.
  pkgs = import <git> {};
  hp = pkgs.haskellPackages;
in hp.cabalJs.mkDerivation (self: {
  pname = "transformers";
  version = "<IP_ADDRESS>";
  sha256 = "0a364zfcm17mhpy0c4ms2j88sys4yvgd6071qsgk93la2wjm8mkr";
  noHaddock = self.stdenv.lib.versionOlder self.ghc.version "6.11";
  meta = {
    description = "Concrete functor and monad transformers";
    license = self.stdenv.lib.licenses.bsd3;
    platforms = self.ghc.meta.platforms;
  };
})

output
error: while evaluating the attribute ‘nativeBuildInputs’ of the derivation ‘haskell-transformers-ghcjs7.8.4-<IP_ADDRESS>-shared’ at "/home/eli/Upstream/nixpkgs/pkgs/build-support/cabal/ghcjs.nix":62:13:
while evaluating the attribute ‘buildInputs’ at "/home/eli/Upstream/nixpkgs/pkgs/build-support/cabal/ghcjs.nix":42:17:
while evaluating anonymous function at "/home/eli/Upstream/nixpkgs/pkgs/build-support/cabal/ghcjs.nix":42:49, called from undefined position:
while evaluating the attribute ‘ghc.parent.Cabal_1_22_0_0’ at "/home/eli/Upstream/nixpkgs/pkgs/development/compilers/ghc/wrapper.nix":84:10:
attribute ‘ghc.parent.Cabal_1_22_0_0’ missing, at "/home/eli/Upstream/nixpkgs/pkgs/build-support/cabal/ghcjs.nix":84:32

Any ideas what could be causing this?

turns out that hp.cabalJs is not the way to build ghcjs things. the way to go is to use haskellPackages_ghcjs.cabal


Change parser to allow parsing two script tags on <script setup>

This PR modifies the parser so that it can parse SFCs with two script tags.
However, the parser parses the two scripts only if the SFC has both <script setup> and plain <script>.
<script>
  performGlobalSideEffect()
  export const named = 1
</script>

<script setup>
  let count = 0
</script>

Related to #78

Hmm. Can't parse the following SFCs well.
<script>
export let count = 42
</script>

<script setup>
let count = 42
</script>

The current PR implementation is a parse error because it parses as a single script.
export let count = 42

let count = 42

We need to parse it as a separate script, but I don't know how to merge the ScopeManager generated by @typescript-eslint/parser.

I also considered adding {} to the <script setup> script to make it look like block scope, but we can't do this because of the import statement.
<script>
export let count = 42
</script>

<script setup>
let count = 42
</script>

↓
export let count = 42

{
let count = 42
}

But the next SFC is an error.
<script>
export let count = 42
</script>

<script setup>
import Comp from './comp.vue'
let count = 42
</script>

↓
export let count = 42

{
import Comp from './comp.vue'
let count = 42
}

Changed to parse <script setup> and split it into import statements and other statements to build source code.
For example:
<script>
export let count = 42
</script>

<script setup>
import MyComponent from './MyComponent.vue'
let count = 42
</script>

↓
export let count = 42
;
import MyComponent from './MyComponent.vue';
{
let count = 42
}


Sails not working on Ubuntu 14.04

Sails seems not to be working on the newest LTS version of Ubuntu - 14.04.
When running 'which sails' in command line nothing is returned.
Searched for sails in the /usr/bin folder and sails is not there (not sure if it should be listed here but wanted to mention this).
Also did a global system search for the term 'sails' and these are the results:
./usr/lib/node_modules/sails
./home/gjorge/.npm/sails
./home/gjorge/.npm/registry.npmjs.org/sails

This seems to be working:
/usr/lib/node_modules/sails/bin/sails.js new projectName

Any ideas on how can I make a sails command to point there?

Rather than add in in .bashrc, you can create a soft link using ln -s command.
I am also facing this same issue on 14.04. For me even '/use/lib/node_modules/sails/.bin/sails.is new test' is also not working. Its throughing error.

If it can still helps someone I found this that worked for me
Not really sure why, but uninstalling node and following the guide on the sails.js site worked...
sudo apt-get install python-software-properties python g++ make
sudo add-apt-repository ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install nodejs
sudo npm -g install sails

ubuntu 16.+
alias sails="~/.npm-global/lib/node_modules/sails/bin/sails.js"


GH-41287: [Java] ListViewVector Implementation

Rationale for this change
Apache Arrow format defines ListView and this has been introduced into other language bindings and the objective of this PR is to provide the initial ListView support to Java by adding ListViewVector.
Non-Goals
The following list of issues propose the extended work depending on this PR. They were separated to streamline the implementation process.

[ ] https://github.com/apache/arrow/issues/41272
[ ] https://github.com/apache/arrow/issues/41286
[ ] https://github.com/apache/arrow/issues/41290
[ ] https://github.com/apache/arrow/issues/41288
[ ] https://github.com/apache/arrow/issues/41289
[ ] https://github.com/apache/arrow/issues/41269
[ ] https://github.com/apache/arrow/issues/41291
[ ] https://github.com/apache/arrow/issues/41292
[ ] https://github.com/apache/arrow/issues/41270
[ ] https://github.com/apache/arrow/issues/41293
[ ] https://github.com/apache/arrow/issues/41294
[ ] https://github.com/apache/arrow/issues/41569
[ ] https://github.com/apache/arrow/issues/41570
[ ] https://github.com/apache/arrow/issues/41584
[ ] https://github.com/apache/arrow/issues/41585

Are these changes tested?
Yes
Are there any user-facing changes?
No

GitHub Issue: #41287

@lidavidm @danepitkin This PR is ready for reviewing. Also it may need running the CIs. (I am not sure what happened there after marking ready for review).

@lidavidm I updated the PR and left some comments too. Ready for another round of reviews.

@lidavidm PR is ready for another round of reviews :slightly_smiling_face:

@lidavidm updated the PR and left a few comments.

@lidavidm Java JNI seems to be failing due the C++ issue came across: https://github.com/apache/arrow/pull/41628#issuecomment-2106448958

Can we get a C++ maintainer to take a look?

@felipecrv would you mind reviewing this PR?

@felipecrv would you mind reviewing this PR?

No, I mean get a C++ reviewer to look at the C++ build failures.

@lidavidm sorry I misunderstood.

@lidavidm should we rebase and run CIs again. It seems that there was PR to fix the breaking Gandiva issue?
And any other changes you would expect here?

let's just rebase and see

@lidavidm CIs are passing!


Collapsable Clusters

The UCSD HIV-TRACE viz app includes collapsible clusters. This seems potentially useful.

Mirrored App at http://aaboyles.github.io/hivtrace-viz


docs : readme.md

🎯 [Documentation Issue] : docs #11

Closes #11

🗒 Checklist:

[] I have mentioned the issue number in my Pull Request.
[]  I have gone through rules of when PR will get merged.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md
[] I have followed proper file structure.
[] I have gone through

Thank you for contributing!❤
Don't forget to show some support by ⭐ the repository!

Hello @Puskar-Roy2, thank you for your pull request! We will review it shortly. 😇❣
Your contributions help us grow and improve our project. Please make sure you have read and followed our CONTRIBUTING GUIDELINES.
Your efforts are appreciated, and we value your participation in our community. Don't forget to ⭐ our repository!
Happy coding!✨

Hey @Puskar-Roy2! We're excited to let you know that your pull request has been merged into the APIverse🚀🎁
Your commitment, effort, and expertise have greatly influenced our project, and we're incredibly thankful for your contributions.😇
Your code is now part of our expanding ecosystem, assisting developers worldwide in creating exceptional APIs.❣🔥
Happy Coding! ✨ We look forward to seeing you again soon!❣


Missing fade out animation when FloatingArrow used with FloatingDelayGroup

Describe the bug
There's a missing fade-out animation on Tooltips if you use FloatingArrow inside of a FloatingDelayGroup due to FloatingArrow's invocation of platform.isRTL.
To Reproduce

Go to https://codesandbox.io/p/sandbox/clever-mahavira-3g74fx
Hover over Ref 1
Hover over Ref 2
Hover out
Notice that the fade out animation didn't trigger

Expected behavior
The fade out animation should have triggered. (If you only hover over Ref 1 and then hover out, it correctly triggers)
Context:

OS: Mac
Browser Firefox, Chrome

Additional context
I've tracked this down to the usage of the const isRTL = platform.isRTL(floating) line in FloatingArrow. If you comment that line out, the animations work as expected.

It seems like sticking the isRTL check in a layout effect instead fixes the issue.


[PullRequest] log senders login ID if name == null

If a github user has no name the log shows [null] Added comment:.
With this change it will fallback to the nickname.

updated test cases

@benpatterson updated

Thanks @Rechi !


Add more info for get pods cmd

Now, conduit get pods only returns pods name. That's not enough, I need to know whether the pod was added to the mesh, and other info.

Hey @zhuguihua sorry about the delay on this PR. We agree with you that get is an important command, and will soon be doing a second pass on it. I would very much appreciate your comments on the RFC here: #355 to make sure we understand and cover your use cases (you might also want to signup to the developers mailing list: https://groups.google.com/forum/#!forum/conduit-dev )
I am closing this PR in favor of the RFC's changes for the moment, please let me know if you think this isn't the best thing to do.