[Bug]: MarkerViews become 'unfixed' from their coordinate and float around the map

Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
iOS
@rnmapbox/maps version
10.0.0-beta.59
Standalone component to reproduce
import MapboxGL, { Camera, MapView, RegionPayload } from "@rnmapbox/maps";

const Component = () =>  (
        <MapboxGL.MapView
          compassEnabled
          ref={mapRef}
          style={{ flex: 1, opacity: overlay ? 0 : 1 }}
          styleURL={styleUrl}
          projection="mercator"
          scaleBarEnabled={false}
          onRegionIsChanging={updatePins}
          onDidFinishLoadingMap={() => {
            setOverlay(false);
            updatePins();
          }}
          regionDidChangeDebounceTime={100}>
          <Camera
            ref={cameraRef}
            animationMode="flyTo"
            animationDuration={0}
            zoomLevel={7}
            centerCoordinate={
              userLocation
                ? [
                    parseInt(userLocation.longitude, 10),
                    parseInt(userLocation.latitude, 10),
                  ]
                : undefined
            }
          />
          {pins.length
            ? pins.map(({ waterbody, Pin }) => (
                <MapboxGL.MarkerView
                  key={waterbody.id}
                  allowOverlap
                  coordinate={[waterbody.lng, waterbody.lat]}
                  style={{ zIndex: waterbody.fishing_reports_count || 1 }}>
                  <Pressable onPress={() => onSelectMapPin(waterbody)}>
                    <Pin height={50} width={50} />
                  </Pressable>
                </MapboxGL.MarkerView>
              ))
            : null}
        </MapboxGL.MapView>
)

Observed behavior and steps to reproduce
Here's a video of the behavior we encounter:
https://user-images.githubusercontent.com/24562987/219132205-d065db5a-fb9b-4ff8-bc4b-d14cec169291.mp4
As you can see above, on occasion, the MarkerViews we use become unfixed from their coordinates and remain at a fixed place on the screen until we move the map outside the bounds of where the pins should be displayed and they're un-rendered.
This is not something that is consistently reproducible, but does pop up with some consistency. I only included our Mapbox code because I figured the other component code wasn't related to the bug. Happy to post more code if helpful reproducing
Expected behavior
The expected behavior is that MarkerViews remain pinned to their coordinates
Notes / preliminary analysis
We're using the new mapbox implementation and encountering the above issue. Apologies if this has already been reported or resolved. The other MarkerView issues seemed to not be exactly what I'm encountering.
One thing to note is that I am 10 patch versions behind the latest beta - I can't update from .59 -> .69 because we're on Expo 45 and you require Expo 47 for the latest beta.
In case it's pertinent, here's my code for generating and updating the data we render into MarkerViews:
const updatePins = useCallback(
      async (props?: GeoJSON.Feature<GeoJSON.Point, RegionPayload>) => {
        let bounds: GeoJSON.Position[] | undefined;
        let zoom;
        if (props) {
          bounds = props.properties.visibleBounds;
          zoom = props.properties.zoomLevel;
        } else {
          bounds = await mapRef.current?.getVisibleBounds();
          zoom = await mapRef.current?.getZoom();
        }

        if (bounds && bounds.length && zoom) {
          const waterbodies = await callFetchPins({
            ...deriveBoundsFromPosition(bounds),
            zoom,
            limit: 20,
          });
          if (waterbodies) {
            const inViewFavs = favoriteWaterbodies.filter(
              ({ lat, lng }) =>
                lat <= bounds[0][1] &&
                lat >= bounds[1][1] &&
                lng <= bounds[0][0] &&
                lng >= bounds[1][0]
            );
            const mapPins = generateMapPins({
              waterbodies,
              favoriteWaterbodies: inViewFavs,
              selectedPin,
            });
            setPins(mapPins);
          }
        }
      },
    [favoriteWaterbodies, selectedPin]
  );

Thank you for your time!
Additional links and references
No response

Can you try a more recent beta? https://github.com/rnmapbox/maps/pull/2589 was fixed since beta 59. So pls retest with latest beta (beta-69)


maybe you can provide a alipay or wechat-pay account to donate

i think this tool is so great

I don't think these are available where I live but I appreciate your support anyway ✌

I don't think these are available where I live but I appreciate your support anyway ✌


Entity splitting with left join

I am currently working on a business project with extremely little control over the database structure. The database has the following tables: Item, ItemProperties, ItemFlags, et cetera.
When there are no extra properties no record is made in the ItemProperties table instead of a record with all NULLs. I would very much like to use entity splitting so my output is a nice clean class: Item. This poses a problem as Entity Framework uses INNER JOIN when using entity splitting.
The SQL output is also not what I would expect. I would expect the first table to be mapped to be the first in the query. Instead the other table is queried first, which poses a second problem because there is actually no record in this table for that id.
SELECT
[Extent1].[ItemId] AS [ItemId],
[Extent1].[PropertyOfItemProperties1] AS [PropertyOfItemProperties1],
[Extent2].[PropertyOfItem1] AS [PropertyOfItem1]
...
FROM  [dbo].[ItemProperties] AS [Extent1]
INNER JOIN [dbo].[Item] AS [Extent2] ON [Extent1].[ItemId] = [Extent2].[ItemId]
WHERE  [Extent1].[ItemId] =  @p__linq__0
I've read this is by design, so I would probably be wasting my time asking for a change? Instead I will ask: is there a workaround for these two problems?

@bdebaere we discussed this and we believe that

Yes, it is by design, and changing the assumption that the dependent row always exists would involve prohibitively expensive changes. E.g. we would need to track whether the row exists in the database to decide whether and update on the entity level should generate an INSERT or an UPDATE operation against the table.

We think that the simplest workaround would be perform the entity splitting by hand in your code. This means:

Have two separate entities mapped to Item and ItemProperties tables and a navigation property

Create unmapped properties on the .NET type for Item that delegate to the related entity

Make sure you configure the relationship as 1:0..1

E.g. the Item entity would look somewhat like this:
public class Item
{
    int Id { get; set; }
    string LocalProperty { get; set; }
    string ItemProperties Properties {get; set; }
    [NotMapped]
    string DelegatedProperty
    {
        get
        {
            return Properties?.DelegatedProperty;
        }
        set
        {
            if (value != null && Properties == null)
            {
                Properties = new ItemProperties();
            }
            Properties.DelegatedProperty = value;
        }
    }
}

@divega Thank you for your time. This does not seem to give the output that I want. The JSON output lacks the DrawingId, even for Items which clearly have one. Did I forget something? What am I missing?
Also, as far as I'm aware, this will make 3 extra database queries when I have 3 mapped entities? If this is correct then this is a method I would like to avoid and hope that you have another suggestion?
This is my code (the setter or getter never get executed):
public class Item
{
       [NotMapped]
        public int? DrawingId {
            get
            {
                return ItemDrawing?.DrawingId;
            }
            set
            {
                if (value == null)
                    return;

                if (ItemDrawing == null)
                    ItemDrawing = new ItemDrawing();

                ItemDrawing.DrawingId = value.Value;
            }
        }
        public virtual ItemDrawing ItemDrawing { get; set; }
}

dbModelBuilder.Entity<Item>()
                .HasOptional(property => property.ItemDrawing)
                .WithRequired(property => property.Item)
                .WillCascadeOnDelete();


Don't print stack when cancelling CLI extension install

VSCode Version: Code - Insiders 1.19.0-insider (6bc5a14bf34e44b3af5508350cc1221fcc999ceb, 2017-12-05T06:08:29.821Z)
OS Version: Darwin x64 17.2.0
Extensions: the listing length exceeds browsers' URL characters limit

This is fixed.


Clara: TextFlow: fixed issue with word wrapping

The issue with word wrapping was that in case that m_pos + width was
greater or equal to m_end it fallbacked to m_end-m_pos branch which
caused that printed string was greater than configured width.
Also caused duplication of words as in next iteration m_len was
added to m_pos this was less then m_end.
Originally reported in https://github.com/catchorg/Catch2/issues/1400

You should also add tests that show the bug and protect against regressions.

Yes i thought about them. But I was not sure if I should add them here or to textflowcpp repository :) So i will probably add tests here and also copy existing ones from the textflowcpp repo.

Oh, right.
I'll think about the best solution to this, maybe I should pester Phil to move textflow to catchorg as well.

In that case my pull requests should be done against the textflowcpp repo. either way compilation of its tests is failing without iterator_traits pull request :)

Thanks @JoeyGrajciar. I've applied this fix, along with a test based on your associated issue, to the TextFlowCpp project:
https://github.com/philsquared/textflowcpp/commit/1538b0cea716f9fabd85974fe654a501afc8c1a7
I'll get that merged into Clara soon.

@philsquared thank you :) Closing this pull request.


iOS: Login status not maintained

I've noticed this in the last couple of betas, but only since I installed iOS 13.4b1, so not sure if it's an iOS thing or a NNW thing. When I follow a link in NNW to an article on a site that requires a login (e.g., Wired, where I have a subscription), normally I sign in once, check the "Remember Me" box, and then NNW does not prompt me again for future articles. However, right now, even if I sign in, go back to the article list, and then try reading the same article again, I'm already signed out. Login information is never remembered—but it was a couple of weeks ago. I've seen this on at least two different sites, on both iPhone and iPad running 13.4b1.

Unfortunately, I believe this is entirely out of our control, and there’s nothing we can do to change that behavior. (That view is provided by the system.)
However, I’ll leave this open for now in case somebody knows something I don’t know. :)


port edit

should show better loading indicator/grey out >?
port move and also port rename

especially on big subpatches like stid blob

also when creating ports (e.g. by dragging onto port...)

maybe bring back modal loading in a different form ?


react-router-config matchRoutes does not match properly when query parameter is present

react-router-config's matchRoutes does not return all matches if the url contains a slash followed by a query string.
Version
<EMAIL_ADDRESS><EMAIL_ADDRESS>Test Case
Steps to reproduce
export const routes = [
  {
    component: App,
    routes: [
      {
        path: '/',
        exact: true,
        component: Home
      }
    ]
  }
];

const matches = matchRoutes(routes, '/?foo=bar');

Expected Behavior
matches should contain matches for both App and Home. This is the case when we remove the query parameter.
[
  {
    route: { component: [Object], routes: [Object] },
    match: { path: '/', url: '/', params: {}, isExact: true }
  },
  {
    route: { path: '/', exact: true, component: [Object] },
    match: { path: '/', url: '/', isExact: true, params: {} }
  }
];

Actual Behavior
matches only contains a record for App
[
  {
    route: { component: [Object], routes: [Object] },
    match: { path: '/', url: '/', params: {}, isExact: true }
  }
]

The same happens for /foo. For /foo, or /foo?bar=baz, the expect behavior occurs. However, for /foo/?bar=baz, the actual behavior occurs.
Additional information: for root URLs, chrome (59.0.3071.115) automatically puts / between the host name and query parameters. i.e. localhost:3000?foo=bar becomes localhost:3000/?foo=bar.
Any ideas?

Our underlying matching library does not handle query strings. So, you should put in only the pathname to matchRoutes().


python310Packages.jellyfin-apiclient-python: 1.8.1 -> 1.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.jellyfin-apiclient-python is: "Python API client for Jellyfin"
meta.homepage for python310Packages.jellyfin-apiclient-python is: "https://github.com/jellyfin/jellyfin-apiclient-python"
meta.changelog for python310Packages.jellyfin-apiclient-python is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.9.1 with grep in /nix/store/3mczi2vpbm2wvw538kfgjrhnrg2f8bzm-python3.10-jellyfin-apiclient-python-1.9.1
found 1.9.1 in filename of file in /nix/store/3mczi2vpbm2wvw538kfgjrhnrg2f8bzm-python3.10-jellyfin-apiclient-python-1.9.1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.jellyfin
jellyfin-mpv-shim
python310Packages.jellyfin-apiclient-python
python39Packages.jellyfin-apiclient-python

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3mczi2vpbm2wvw538kfgjrhnrg2f8bzm-python3.10-jellyfin-apiclient-python-1.9.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.jellyfin-apiclient-python https://github.com/r-ryantm/nixpkgs/archive/4f66e4fdd806185de9a8e3decfdc29f2e63a8164.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3mczi2vpbm2wvw538kfgjrhnrg2f8bzm-python3.10-jellyfin-apiclient-python-1.9.1
ls -la /nix/store/3mczi2vpbm2wvw538kfgjrhnrg2f8bzm-python3.10-jellyfin-apiclient-python-1.9.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

home-assistant-component-tests.jellyfin
jellyfin-mpv-shim
python310Packages.jellyfin-apiclient-python
python39Packages.jellyfin-apiclient-python

Maintainer pings
cc @jojosch for testing.

Result of nixpkgs-review pr 188485 run on x86_64-linux 1

4 packages built:

home-assistant-component-tests.jellyfin
jellyfin-mpv-shim
python310Packages.jellyfin-apiclient-python
python39Packages.jellyfin-apiclient-python


Fragment names as "magic strings" (no hard references)

Is your feature request related to a problem? Please describe.
I've been concerned by the fact that we can't embed fragments with template string interpolation, as it breaks TypeScript type-inference, as mentioned in the documentation of gql-tag-operations.
Currently, the suggested approach is to spread fragments as "magic strings", meaning there's no hard reference to the fragment itself. We need to find the right name (and make sure of it!), be aware that fragments are generated with a Fragment suffix, then spread it. All fragments are defined "globally" or within the same file (graphql.ts), so all fragments are accessible.
const allFilmsWithVariablesQueryDocument = graphql(/* GraphQL */ `
  query allFilmsWithVariablesQuery($first: Int!) {
    allFilms(first: $first) {
      edges {
        node {
          ...FilmItem
        }
      }
    }
  }
`);

It is worth mentioning that spreading a non-existing fragment will lead to an error within the codegen step. However, not having hard references (e.g., importing the fragment) could hurt the application's maintainability.
Another concern is that name conflicts between operations or fragments are possible, but again, the codegen will warn us against it. My concern is mainly for grown applications, it could be possible to spread the wrong existing fragment via a typo (e.g., WorkspacesCard instead of WorkspaceCard).
I would like to have the ability the rely on hard references for fragments, I don't mean to make it mandatory, but having the ability to would be interesting.
Describe the solution you'd like
Currently, there's no way to easily extract the name of a generated fragment.
One solution could be to make that possible so that we could at least rely on a hard reference on the name rather than the fragment definition (to mitigate the related issue). So implementing a helper to extract the fragment's name from the DocumentNode object via some AST utils.
E.g., with the following helper: getFragmentName(), return the name of the generated fragment as a string so we can compose fragments or queries with it.
import { graphql, getFragmentName } from './gql';

export const FilmFragment = graphql(/* GraphQL */ `
  fragment FilmItem on Film {
    id
    title
    releaseDate
    producers
  }
`);

const fragmentName = getFragmentName(FilmFragment); // 'FilmItemFragment'
//    ^? const fragmentName = "FilmItemFragment"

Note: There's still an unanswered question about how to expose fragment names?

We could either:

export it as a const
expose fragments as before (via imports), and call getFragmentName from consumers
Use Apollo Client's naming convention to retrieve a component's fragments given the component, but instead of retrieving fragment definitions, it will be exposing fragment names

So we could do something like:
const allFilmsWithVariablesQueryDocument = graphql(/* GraphQL */ `
  query allFilmsWithVariablesQuery($first: Int!) {
    allFilms(first: $first) {
      edges {
        node {
          ...${getFragmentName(FilmItemFragment)}
        }
      }
    }
  }
`);

See the proposed implementation in https://github.com/dotansimha/graphql-code-generator/pull/9056.
Describe alternatives you've considered
I've considered looking into why we can't embed fragments and what we could do not to make them "global", but I felt like it was not moving this project in the right direction and settled on adding an optional utility for people that share my concern.
Is your feature request related to a problem? Please describe.
No response

Our team shares your concern and its hindering us from adopting the tool without causing issues. People believe you can accidentally delete fragment if theyre not being used in the code. Please let me know if getFragmentName can land?


Dont use colons in Valestrom or valec CLI

Windows paths (like C:\whatever) interfere with them.

Done in #314!


BIGTOP-3446. Fix toolchain task failure due to undefined variable in renv.pp.

This if follow-up of  BIGTOP-3443 / #697 .

+1, verified it on Ubuntu 16/18 and Fedora-31.

Thanks, @guyuqi .


Removed fmt.Println on plugins

fixes #615

LGTM, @idanl21 @swoehrl-mw can you please take a look.


Format code breaks plain text inside P tags for no apparent reason

Copied from https://github.com/Microsoft/vscode/issues/31050 at their request:
Steps to Reproduce:

Take a simple paragraph of text, such as

Our forms for collecting address-related information follow a standard design. Specific input elements will vary according to the form’s audience and purpose.

Run "Format Document" (shift-option-F)
You get

Our forms for collecting address-related information follow a standard design. Specific input elements will vary
              according to the form’s audience and purpose.

I don't see why this is.  I would expect the text inside the p tags to remain as is.

@smlombardi
I tried running your example using v1.8.0-rc2 using the following settings:
{
  "indent_size": "4",
  "indent_char": " ",
  "max_preserve_newlines": "5",
  "preserve_newlines": true,
  "keep_array_indentation": false,
  "break_chained_methods": false,
  "indent_scripts": "normal",
  "brace_style": "collapse",
  "space_before_conditional": true,
  "unescape_strings": false,
  "jslint_happy": false,
  "end_with_newline": false,
  "wrap_line_length": "80",
  "indent_inner_html": false,
  "comma_first": false,
  "e4x": false
}

And got the following:

Our forms for collecting address-related information follow a standard design.
    Specific input elements will vary according to the form’s audience and purpose.

This may be fixed.

MacKLess is referring to the web page - jsbeautifier.org. The settings are less important than the using the latest rc.


Button radius

Is it possible to have rounded corner on buttons ?

This issue was moved to zurb/ink#164


Updating Magisk

How to update Magisk on GammaOS? It always brings up an error.

I have the same issue with gamma os 1.5.1.
tried to update it but fail.

I canc onfirm this is also an issue for me. I'm on the latest full GammaOS.


The 'Access-Control-Allow-Origin' header contains multiple values, but only one is allowed.

I'm running into this issue while requesting api in my ionic application.
Removing two lines in stack-cors package:
$response->headers->set('Access-Control-Allow-Origin', $request->headers->get('Origin'));
solves my problem, but there has to be a better solution.
I'm using default config/cors.php file

You probably have header("Access-Control-Allow-Origin: *"); somewhere, or something similar in your .htaccess file?

It turned out i was using dev-master version of laravel-cors, beacause there is no 0.7.x as readme says. I installed 0.6.x, added provider in app, middleware and route middleware in kernel, and now it works like a chram.
But going back to this issue, I removed all acces-control-allow-origin in my project and left only those in default config, but problem still occured.

I found that my nginx config in my docker container had add_header lines in it. Removing these fixed my problem.

Access to XMLHttpRequest at 'https://web123.com/Ajith/login2.php' from origin 'http://localhost:8100' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed.
how solve this error.....pls

Header always set Access-Control-Allow-Origin: "*"


Time for a new release?

It has been well over a year since 4.0.30 was released (2020-02-08) and there have been 52 PRs merged since then.
Can we please take care of a few more high-value open PRs – specifically #703, #856, #903, and #904 – and create a new release?

I think you are correct.  Let's add any issues we want closed to the milestone I just created and attached to this issue and make a release.

Great. Curious, though: why .37 and not .31 @mkleehammer ?

Oops.  Probably as you expected - it was a typo.  Corrected.
BTW, I was hoping to make a release with anything that causes a crash or memory corruption to eliminate security issues.  If you see anything, add those also.  I have found a crash I need to reproduce and open an issue for.

https://pypi.org/project/pyodbc/4.0.31/


bug: aliased transitive dependency names do not work

We have a dependency on plotly.js, which uses an aliased version of one of its dependencies:
https://github.com/plotly/plotly.js/blob/e0a5f13a4c9b8e2f74204499168d12b2d0bab285/package.json#L110
When adding a dependency like this, the pnpm lockfile has a version marker that matches the pnpm name:
  /plotly.js/2.12.1:
    resolution: {integrity: sha512-XbZ3w3jSl+ihZPMXWwblmjinqbzdd+vT+3XKZpyffxmlMmTp/3vY1ewpQDuNyufUoiT0o0ekCqa80Qlzi7jwlA==}
    dependencies:
      ...
      probe-image-size: 7.2.3
      regl<EMAIL_ADDRESS>      regl-error2d: 2.0.12

The issue presents itself first as an error with iterating through the deps in transitive_dependencies.bzl:
ERROR: An error occurred during the fetch of repository 'npm':
   Traceback (most recent call last):
        File "/home/alex.torok/.cache/bazel/_bazel_alex.torok/080e6abb1a3d3304a3cf19fc0f4ef9c1/external/aspect_rules_js/npm/private/npm_translate_lock.bzl", line 319, column 33, in _impl
                lockfile = _process_lockfile(rctx)
        File "/home/alex.torok/.cache/bazel/_bazel_alex.torok/080e6abb1a3d3304a3cf19fc0f4ef9c1/external/aspect_rules_js/npm/private/npm_translate_lock.bzl", line 145, column 43, in _process_lockfile
                return translate_to_transitive_closure(lockfile, rctx.attr.prod, rctx.attr.dev, rctx.attr.no_optional)
        File "/home/alex.torok/.cache/bazel/_bazel_alex.torok/080e6abb1a3d3304a3cf19fc0f4ef9c1/external/aspect_rules_js/npm/private/transitive_closure.bzl", line 114, column 34, in translate_to_transitive_closure
                gather_transitive_closure(
        File "/home/alex.torok/.cache/bazel/_bazel_alex.torok/080e6abb1a3d3304a3cf19fc0f4ef9c1/external/aspect_rules_js/npm/private/transitive_closure.bzl", line 34, column 36, in gather_transitive_closure
                package_info = packages[utils.pnpm_name(name, version)]
Error: key<EMAIL_ADDRESS>not found in dictionary

I thought an easy fix could be to handle the version number differently if we detect a full path:
@@ -27,6 +29,9 @@ def _strip_peer_dep_version(version):
diff --git a/npm/private/utils.bzl b/npm/private/utils.bzl
index b05d467..2289ac3 100644
--- a/npm/private/utils.bzl
+++ b/npm/private/utils.bzl
 def _pnpm_name(name, version):
     "Make a name/version pnpm-style name for a package name and version"
+    if version.startswith("/"):
+        # Strip leading '/'
+        return version[1:]
     return "%s/%s" % (name, version)

This seems to address the issue seen when iterating over the transitive deps, but then I hit an issue with the link package names not being correct:
ERROR: /home/alex.torok/code/av/BUILD.bazel:8:22<EMAIL_ADDRESS>missing input file<EMAIL_ADDRESS>ERROR: /home/alex.torok/code/av/BUILD.bazel:8:22: 1 input file(s) do not exist

Looking in my external repo directory, it appears that the plotly.js does not gain a dep on the correct link target:
$ rg store_link__regl___@ npm*__links/
npm__react-plotly.js__2.5.1__plotly.js_2.12.1_react_16.14.0__links/defs.bzl
85<EMAIL_ADDRESS>379<EMAIL_ADDRESS>
npm__plotly.js__2.12.1__links/defs.bzl
78<EMAIL_ADDRESS>366<EMAIL_ADDRESS>648<EMAIL_ADDRESS>
I got to this point and feel like the fix for this is over my head, so I'm hoping someone with more familiarity of the whole data flow from lockfile parsing to generated link targets can help out.

Sorry, just realized this is a duplicate of #86

Thanks for the detailed summary of the issue. I started to look at just now and the code needs a bit of refactoring to support these link aliases in npm_import and npm_translate_lock. I'll pick it up again tomorrow.

Even with #171, I'm still seeing this issue when a transitive dependency is given an alias. I have a reproduction at https://github.com/alex-torok/rules_js/pull/2.

Even with #171, I'm still seeing this issue when a transitive dependency is given an alias. I have a reproduction at alex-torok#2.

Thanks for the repo. I'll work on a fix for transitives case today.

Cut https://github.com/aspect-build/rules_js/releases/tag/v0.12.2 which includes the fix


[T4A2][F09-B2] Xu Chen

Ready for review.

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


Regression: Dump Database Feature Causes Performance Issues and Wrong Dump File Options in Version 24.2.0

Description
I recently upgraded from DBeaver version 24.1.5 to 24.2.0 and encountered several issues with the dump database feature that were not present in the previous version.
Issues:

Result Dump Printed in Dump Process Tab: In version 24.2.0, the content of the result dump file is printed in the dump process tab. This change introduces a few problems:

I can no longer disable this feature, which was possible in previous versions.
When dumping a large database, the dump file can become enormous, causing the pop-up to lag and become unresponsive at times.

Incorrect Dump File Options: After dumping a database, the generated dump file contains incorrect options. Specifically, the file includes a LOCK TABLE command, even though I did not select this option in the Export configuration tab. This renders the dump file unusable for restoring on another machine, resulting in failed restores.

Steps to Reproduce:

Upgrade DBeaver from version 24.1.5 to 24.2.0.
Use the "Dump Database" feature to export a database.
Observe that the dump result is printed in the dump process tab, with no option to disable it.
Attempt to restore the generated dump file on another machine, and note the incorrect options in the dump file (e.g., LOCK TABLE).

Expected Behavior:

There should be an option to disable printing the dump file content in the dump process tab.
The dump file should not include incorrect options such as LOCK TABLE when the user has not selected them in the Export configuration.

Actual Behavior:

The dump process tab prints the content of the dump file, causing performance issues when dealing with large databases.
The generated dump file contains incorrect options that prevent successful restoration on other machines.

Workaround:
I downgraded to version 24.1.5, where the dump feature works as expected.
Environment:

DBeaver Version: 24.2.0 (issue present)
DBeaver Version: 24.1.5 (working)
Database Type: MariaDB
Operating System: Window 10

Please investigate this regression as it severely impacts the usability of the dump and restore process in the latest version.
DBeaver Version
Community Edition 24.2.0
Operating System
Window 10
Database and driver
Database: 10.3.39-MariaDB-0ubuntu<IP_ADDRESS>
Driver: MariaDB JDBC driver - org.mariadb.jdbc:mariadb-java-client:RELEASE - 3.3.2
Steps to reproduce
No response
Additional context
No response

Thank you for the bug report.
I'm closing it as it's a duplicate of #35421


Add proxy test

Codecov Report

Merging #11 (ad944c2) into main (a075138) will decrease coverage by 0.38%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files

Impacted Files
Coverage Δ

packages/yasdk-koa/src/proxy.ts
96.05% <100.00%> (ø)

packages/yasdk-koa/src/router/index.ts
85.08% <100.00%> (ø)

packages/yasdk-koa/src/router/codecs.ts
100.00% <0.00%> (ø)

packages/yasdk-koa/src/router/handlers.ts
100.00% <0.00%> (ø)

packages/yasdk-koa/src/common.ts
100.00% <0.00%> (ø)


Volume incorrectly restored on Samsung

Galaxy A54. When volume is restored after ad in Spotify, it is higher than before ad.
I have enabled setting in Samsung Sound Assistant to see the numerical sound level and tested. Also experimented with step in SA.
When I set volume manually to 4, step 1, the volume jumped to 7 after ad. For manual volume 12 step 5, it jumped to 25.

Hi there, this issue seems to be device-specific. Have you noticed the same behavior when using the mute plugin?
Troubleshooting might be challenging since I don't own a Samsung A54 to replicate the issue.
If you are a developer, feel free to tinkle with it and submit a pull request.
cheers.


toRaw throws if the message was decoded from external ByteBuffer

Steps to reproduce:
npm install protobufjs
npm install bytebuffer

This ensures there are two separate installations of ByteBuffer (each with their own Long).
var ByteBuffer = require('bytebuffer');
var ProtoBuf = require('protobufjs');

var CMsgGameserverCrash = ProtoBuf.loadProto(
'message CMsgGameserverCrash {\n' +
'  optional uint64 match_id = 1;\n' +
'}').build('CMsgGameserverCrash');

var crash1 = new CMsgGameserverCrash({
  match_id: 1234
}).toBuffer();

var bb = ByteBuffer.wrap(crash1);
var crash2 = CMsgGameserverCrash.decode(bb);
console.log(crash2);
crash2.toRaw(false, true);

Output:
{ match_id: { low: 1234, high: 0, unsigned: true } }
/home/drkoljan/reproduce-protobufjs/node_modules/protobufjs/dist/ProtoBuf.js:2949
    clone[i] = cloneRaw(value, binaryAsBase64, longsAsStrings, field.type, fie
                                                                    ^
TypeError: Cannot read property 'type' of undefined
    at cloneRaw (/home/drkoljan/reproduce-protobufjs/node_modules/protobufjs/dist/ProtoBuf.js:2949:97)
    at cloneRaw (/home/drkoljan/reproduce-protobufjs/node_modules/protobufjs/dist/ProtoBuf.js:2949:44)
    at MessagePrototype.toRaw (/home/drkoljan/reproduce-protobufjs/node_modules/protobufjs/dist/ProtoBuf.js:2964:28)
    at Object.<anonymous> (/home/drkoljan/reproduce-protobufjs/test.js:16:8)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)

Should not happen with ProtoBuf 4.X. Which version are you using?

ProtoBuf.js version 4.0.0.

I'm still having this with the latest master version. Any ideas?

Have you been able to reproduce the crash using the steps provided?

Shouldn't crash anymore with that fix. However, there is still an issue with Longs from different packages that might prevent such objects to be properly converted to strings when the option is set. This needs a fix in Long.isLong itself.

I confirm that it no longer crashes, but it doesn't convert the Long to a string either.

Can you test this with Long.js master? Basically, just replace dist/Long.js under bytebuffer/long and protobuf/bytebuffer/long.

It converts correctly now.

Thanks, going to push a release soon.

I am having this issue in 5.0.1, can you please confirm this? What is the workaround for this?

Closing this for now.
protobuf.js 6.0.0
Feel free to send a pull request if this is still a requirement.


sdnotify-wrapper: init at unversioned

Motivation for this change
A small CLI utility around libsystemd’s sd_notify feature. Useful for daemons that should not depend on libsystemd.
I decided to commit the few lines of source code because upstream is an unversioned HTTP endpoint.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build sdnotify-wrapper


Is there a way to assign "workload"?

Every task I created has been automatically assigned 2 workload. Is there a way to determine workload manually?

I found the solution here


docs: remove GoldenEye ref in general.go

Description
remove GoldenEye ref in general.go
Tick the relevant boxes:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Examples / tests (addition or updates of examples or tests)
[x] Documentation update
[ ] CI related update (pipeline, etc)

Checklist:

[ ] If relevant, a test for the change has been added / updated as part of this PR.
[ ] If relevant, documentation for the change has been added / updated as part of this PR.

Merge:
Merge using "Squash and merge" and ensure to use a relevant conventional commit message based on the PR contents (this ultimately determines if a new version of the modules needs to be released, and if so, which semver number should be used).

:tada: This PR is included in version 1.0.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[FLINK-26270] Flink SQL write data to kafka by CSV format , whether d…

…ecimal type was converted to scientific notation

What is the purpose of the change
To solve csv serialization , avoiding decimal conversion to scientific notation
Brief change log

CsvFormatOptions add write-bigdecimal-as-plain, Optional whether write bigdecimal using scientific notation
csvMapper.configure(JsonGenerator.Feature.WRITE_BIGDECIMAL_AS_PLAIN, plain)

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (yes)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

Hi @sunshineJK, I can take a look on Friday, sorry, a very busy week.

Hi @sunshineJK, I can take a look on Friday, sorry, a very busy week.

OK,thank you

hi @afedulov Please review it again

Thank you , I'm going to modify it a little bit.

Thanks, @sunshineJK. LGTM.
@afedulov Thank you for your advice. I have gained a lot.

Hi @MartijnVisser , What should I do next

Hi @afedulov @MartijnVisser @PatrickRen What are the next steps? Do I need to do any more operations


Update SODA project tags for Jerba RC1 release

What type of PR is this?
Update SODA project tags for Jerba RC1 release
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Test Report Added?:

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind TESTED
/kind NOT-TESTED

Test Report:

Special notes for your reviewer:

Checked nbp and csi versions
LGTM

Multi-cloud : LGTM


Feature Request: restore External Link directive

Is your feature request related to a problem? Please describe.
The {:target="_blank"}{: .externalLink} directives previously added an arrow icon/emoji  that indicated that the link would launch a new tab to an external website (and leave the OH documentation).
The OH docs have hundreds of these directives sprinkled throughout the Markdown pages.
This feature was lost / dropped during one of the theme migrations.
Can we bring it back?
Describe the solution you'd like.
No response
Describe alternatives you've considered
No response
Additional context.
No response

Thanks for bringing back the launch glyphs. The pages are looking great. 🔥

LMK if you want the ones in the side nav to match

Actually I like the glyph in the Nav bar better.

OK, that one's white.  I'll see if it takes on the color of the surrounding theme context.  If so, we can swap out the other and use this everywhere.  I'll open a separate ticket for that.  Thanks, @johnwalicki


Please confirm the default OS drive size

in this doc, "When you create a new virtual machine (VM) in a resource group by deploying an image from Azure Marketplace, the default OS drive is often 127 GB (some images have smaller OS disk sizes by default)."; however, in doc: https://docs.microsoft.com/en-US/troubleshoot/azure/virtual-machines/default-size-images-changed-30-gb, it shows "When you deploy a Windows Server virtual machine (VM) in Microsoft Azure, the default size of the OS disk is 30 GB instead of 128 GB, as expected. This behavior occurs regardless of whether the disk is managed or unmanaged."
Please confirm the default OS drive size for Windows Server virtual machine (VM) in Microsoft Azure.

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

ID: ccc58c74-7913-f1f6-8681-1823bbd8f050
Version Independent ID: c11bab28-a82a-29a1-84bf-fb3dfb9a5cb2
Content: Expand the OS drive of a Windows VM in an Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/expand-os-disk.md
Service: virtual-machines-windows
Sub-service: disks
GitHub Login: @kirpasingh
Microsoft Alias: kirpas

@HannahHsiao -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

@HannahHsiao -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

Thank you for the heads-up! I cannot verify the behavior implied in https://docs.microsoft.com/en-US/troubleshoot/azure/virtual-machines/default-size-images-changed-30-gb. Just as a simple test,  I created a Windows Server VM and the OS disk size was 64gb. I believe it varies based on the selected SKU. Please verify the recommendation in aforementioned doc i.e. does it (OS disk size of 30gb) occurs under specific conditions etc.? At this time, I don't see a compelling reason to update this doc as further investigation is required.

Thank you for the heads-up! I cannot verify the behavior implied in https://docs.microsoft.com/en-US/troubleshoot/azure/virtual-machines/default-size-images-changed-30-gb. Just as a simple test,  I created a Windows Server VM and the OS disk size was 64gb. I believe it varies based on the selected SKU. Please verify the recommendation in aforementioned doc i.e. does it (OS disk size of 30gb) occurs under specific conditions etc.? At this time, I don't see a compelling reason to update this doc as further investigation is required.

@kirpasingh  - Thank you for providing your insights.
@HannahHsiao  - I hope @kirpasingh has answered your question.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@kirpasingh  - Thank you for providing your insights.
@HannahHsiao  - I hope @kirpasingh has answered your question.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Improve market order import job to backfill

Save all versions of orders based on their timestamps. Must save status of which files have been imported.
Depends on #79.

I have no idea what this is.


Add support for SemVer prereleases

Closes #20

@mmun This is implemented as you describe in your comment on #20, with the exception that I did not include a --prepatch option since it's redundant and uncommon.
Ultimately I decided that the situation I described is not a big deal, and certainly not worth holding back support for prereleases any longer.

Sweet! Looks great.

:+1: - LGTM

As an aside (this is unrelated to logic in this repo), it does seem slightly odd to me that ember release --premajor beta or ember release --prerelease starts at 0 (instead of 1).  Again, doesn't matter much, just surprised me that that was the semver packages incr result.

@rwjblue that surprised me too, but only because I was used to the Ember convention of starting at 1. Do you know where that came from?  It looks like it goes all the way back to the 1.0.0-pre days.
I debated changing it to start at 1 for consistency, because after all this addon is part of an opinionated framework that already seems to have an opinion on the subject. The downside is it's not vanilla SemVer, although it's such a minor thing that I can't imagine it really throwing off someone new to Ember.
Thoughts?

I'm 100% happy to follow the semver package here. It's pretty trivial to just specify the next version on the command line (likely what I would do anyways vs looking up the right --presomething command).
TBH, I'm not sure where our convention of starting with beta.1 came from, but I vaguely feel like most non-ember related packages that I've seen do the same (could just be my own internal confirmation bias though).

SGTM.

@rwjblue I totally agree. Some of the semver default behaviours are not intuitive.


Add AT URIs as alternate links

[!NOTE]
I'm not sure how to test this or if this is where the change needs to actually go. I've pattern matched against the received HTML in prod and found these files, so let me know if it's incorrect and I'll rework this!

See https://github.com/likeandscribe/frontpage/pull/172 for the description of why I'd like to make this change.
Some extra discussion here: https://bsky.app/profile/did:plc:2xau7wbgdq4phuou2ypwuen7/post/3l7esaih44s2s

I'm default ok with this, though it feels a bit under-specified. Should there be a type field, and if so what value?
There is a small related tension with AT URIs not quite being valid "URL" syntax, following WHATWG standards: https://url.spec.whatwg.org/
The issue is that there are multiple colons in the DID in the "authority" segment of the URI. I think there is a path to relaxing the spec to allow this specific pattern (DIDs in that part of URL), but it will be a delicate conversation: browsers have tons of noisy inbound requests and it is important to be diplomatic and make a clear case.
Anyways, probably none of that is a reason not to go ahead with this. Be bold!

shouldn't profiles link to app.bsky.actor.profile record?
it seems very ambiguous, because it can mean many things:

am I linking to my account's repository?
am I linking to my Bluesky profile?
am I linking to my linkat.blue page?
am I linking to my 's profile?

@mary-ext I think that at://<identifier> definitely does not imply anything bsky specific. An atproto account (identified by DID or handle) definitely could mean any or all of the things you mentioned.
I don't think that having a <link rel="alternative"> pointing to an overall account in this way would imply an equivalency of the account with the page itself. It does make sense to me to link something like a bsky profile view page to the "overall account".
In practical terms, it does probably make more sense to tie https://bsky.app/profile/<identifier> to a profile record (so full AT URI), if nothing else because it includes the account identifier anyways.
(note that this codebase could be forked/white-labeled to run on other domains; in that case the relevant thing is still probably the app.bsky.actor.profile record)

FWIW, I think it would also be fine/appropriate to have both a ref to the bsky profile record, and the atproto account identifier. Or even just the bare DID.

Aren't brackets acceptable for URLs? Like, an ipv6 URL looks like http://[::1]. Personally, I don't see any issue with at://[did:plc:tgudj2fjm77pzkuawquqhsxm]/events.smokesignal.calendar.event/3kxbvxj7blk2t.


fix[]:a weird var name

Every other var has a name matches its region except for this one, AFAmazonS3APNortheast2Region but s3-ap-northeast-1.

Copy-pasta error. Thanks, @moshoujingli.


Crash when entering a dimension , can't launch my map anymore :<

Hey @Katkarh, I can only help with technical problems if you provide a crash log and description. For basic support, please visit our Discord at #openterraingen. When you have enough information to post an issue and have checked if an issue doesn't already exist, feel free to open another issue.


Bumped djl to 0.25.0

Description
Bumped djl to 0.25.0 and onnxruntime to 1.16.0
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@owaiskazi19, can you explain the reason why bump version to 0.25? This may break BWC

@owaiskazi19, can you explain the reason why bump version to 0.25? This may break BWC

Makes sense. We can restrict the gson version to avoid the vulnerability.


Re: Challenge: Implement a cool custom monitor (#3)

I saw #3 and try bring UX for monitor.

less space
more readable
JSON formats for readability

Before:

After:

Nice, especially the readability

Thanks for the effort! In the end we went with #48 because it has a tree inspector.

@gaearon yep, awesome job.


[Apple Reminders] Unabale to set priority

Extension
https://www.raycast.com/raycast/apple-reminders
Description
When you open "My Reminders" and select a task, press cmd+k, choose "Set Priority," and then set a priority arbitrarily, a prompt will appear in the bottom left corner indicating "Unable to set priority."
Steps To Reproduce

macOS 14.2.1,  Raycast 1.65.1
Open 'My Reminders', select a task, press cmd+k, choose "Set Priority", set any priority, a prompt will appear in the bottom left corner indicating "Unable to set priority."

Current Behaviour
Unable to set priority
Expected Behaviour
The priority should be set

I can't reproduce that. Could you send a recording to see what happens in detail?

Sure, this is it
https://github.com/raycast/extensions/assets/47599849/e74b83e4-1bb6-44b9-86c9-1a917c160d6d

Alternatively, could you tell me where I can view the debug logs? I can upload them.

Thanks for the recording. I'll take a look at that during the week.

OK, thank you!


"It's not working"

After 'brew install battery' and 'open /Applications/Battery.app', I get these two errors:

Whatever I configure, my M1 stays charging :(

The command line program gives no error:

Any help? :)

I noticed that mine did stop before charging to a full 100% so that's good. But still it won't stop charging when it reaches the percentage I want it to be maintained to, but rather somewhat more.

I'm getting the same error on an m2 macbook air running Ventura. Charging also continues despite the limit :-(

My battery is back at 100% Is there some secret to get this to work?

Thanks for looking at this, Mentor. Unfortunately, I seem to be stuck in exactly the same situation as described above. I took a look at the three lines you have edited yesterday in battery.sh (you've added path + some administration). Can  you explain why you think that this should have solved the issue?
I figured out your script uses 'smc' under the hood. The two commands smc -k CH0B -w 02 and smc -k CH0C -w 02 should do the trick and stop the charging, if I understand battery.sh correctly. Running these two commands however don't seem to do anything :(
Can you explain why you think the exact above two commands should stop the charging? Any idea what can be wrong?
Thanks!


added remove button in coop UI

Maybe if I feel like it, I can help out with some refactoring. Just let me know what needs improvement/assign me a ticket.


Add A New Code Snippet

Add atleast one new code snippet with appropriate styling and make changes to the main table in README.md file too.

Hi, I'd love to help with this issue

@apoorva1999 please go ahead 👍🏼


Dashboard graph additional details

update:
Packets Transferred
to
Packets Transferred (last 24 hrs, updated every 5 minutes)

Addressed by commit ed8669f2716156ddcbb1537cea18b2021f1566b2


[Feature] Broken Link Checker - Github Action

Description
I believe that it will be a great idea to setup a GitHub action that runs periodically and checks for broken links.
I just implemented it in my project and I would like to share my knowledge and received feedback to make it better.
Screenshots
here is an example from my own project:

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)

That seems possible @JuanPabloDiaz. @rupali-codes, @Anmol-Baranwal, @aftabrehan, thoughts?

That seems possible @JuanPabloDiaz. @rupali-codes, @Anmol-Baranwal, @aftabrehan, thoughts?

it seems great though, but how does that actually work @JuanPabloDiaz ?

That seems possible @JuanPabloDiaz. @rupali-codes, @Anmol-Baranwal, @aftabrehan, thoughts?

it seems great though, but how does that actually work @JuanPabloDiaz ?

It will be a Github action to check for broken links in Markdown, HTML, and text files using Lychee, a fast link checker written in Rust.
Here is a full example of a GitHub workflow file:
It will check all repository links once per day and create an issue in case of errors.
name: Links

on:
  repository_dispatch:
  workflow_dispatch:
  schedule:
    - cron: "00 18 * * *"

jobs:
  linkChecker:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Link Checker
        id: lychee
        uses: lycheeverse/lychee-action@v1

      - name: Create Issue From File
        if: env.lychee_exit_code != 0
        uses: peter-evans/create-issue-from-file@v4
        with:
          title: Link Checker Report
          content-filepath: ./lychee/out.md
          labels: report, automated issue

@rupali-codes
The URLs is in json files (this codebase), so maybe try this in a sample private repo to see if it works.

Project implementations:

documentation.breadnet.co.uk ---> GitHub action
freeForGeeks ---> GitHub action

I'd like to share my experience with Lychee. I came across it yesterday and integrated it into my project. While it was helpful in identifying some broken links, it also generated some false positives (links that appear broken but function correctly). I'm still exploring the tool's functionality to potentially fine-tune its accuracy.
On a separate note, I encountered a permissions issue when trying to open new issues.
I hope this helps

@JuanPabloDiaz do you wanna work on it?

@JuanPabloDiaz do you wanna work on it?

Sure.
How can we test it? It will need to be merge to see what happens.

@JuanPabloDiaz do you wanna work on it?

Sure. How can I test it? I understand that GitHub actions will need to be merge to see them in action. Is there a way to test them in development @rupali-codes ?

Yeah, we can test them in the forked repo

You are absolutely right lol
But does it work from any branch, or does it have to be in the main branch of the forked repo @rupali-codes ?

You are absolutely right lol
But does it work from any branch, or does it have to be in the main branch of the forked repo @rupali-codes ?

I figured it out. It has to be in the main brand of the forked repo

Errors in CONTRIBUTING.md
[404] https://github.com/CBID2/LinksHub-my-version-/blob/main/CODE_OF_CONDUCT.md | Failed: Network error: Not Found
[404] https://github.com/rupali-codes/LinksHub/blob/maintainers_info/README.md#maintainers- | Failed: Network error: Not Found

71? That number seems low.
I include JSON files in the link checker and the number went up to:
https://github.com/JuanPabloDiaz/LinksHub/actions/runs/9306836967

There are some false positive. After double checking the list of 29 errors. Here are some resources that should be removed:

Errors in database/resources/e-book.json
"name": "Learning REACT"
[404] https://drive.google.com/file/d/1AZwshgVyazeIJ95ng6Pg1zUbVQoYX93t/view?usp=share_link | Failed: Network error: Not Found

Errors in database/youtube/web-development.json
"name": "Easy Tutorials"
[404] https://www.youtube.com/@EasyTutorialsVideo/ | Failed: Network error: Not Found

Errors in database/ai_tools/design.json
"name": "Adobe Firefly"
[TIMEOUT] https://www.adobe.com/in/products/firefly.html | Timeout
"name": "Designs.ai",
[ERR] https://designs.io/ | Failed: Network error: error sending request for url (https://designs.io/)

Errors in database/youtube/web3-metaverse.json
"name": "LearnWeb3 DAO"
[404] https://www.youtube.com/@LearnWeb3DAO | Failed: Network error: Not Found

Errors in database/frontend/colors.json
"name": "ColorWave AI"
[ERR] https://www.colorwave.dev/ | Failed: Network error: error sending request for url (https://www.colorwave.dev/)
"name": "UI Color Picker"
[ERR] https://uicolorpicker.com/ | Failed: Network error: error sending request for url (https://uicolorpicker.com/)

Errors in database/resources/blogs.json
"name": "JavaScript Tricks-Raj's Blog"
[ERR] https://resourcegallery.live/blog/JavaScript Top 10 Tips & Tricks/ | Failed: Network error: error sending request for url (https://resourcegallery.live/blog/JavaScript Top 10 Tips & Tricks/)

Errors in database/cybersecurity/web_application_security.json
"name": "Certified Web Application Penetration Tester (CWAPT) Certification"
[404] https://mile2.com/web-application-penetration-tester-cwapt.html | Failed: Network error: Not Found

You are absolutely right lol
But does it work from any branch, or does it have to be in the main branch of the forked repo @rupali-codes ?

It would be best to do it from the forked repository.

May I have additional support here. I am not an expert with GitHub actions. How can I improve my workflow?

May I have additional support here. I am not an expert with GitHub actions. How can I improve my workflow?

Let me do it in the PR...

Let me do it in the PR...

After I sent that message, I deleted everything and started over. I did it with the best of my abilities.
Please review it and let me know (in the PR)


Azure Pubsub REST API Example

Describe the bug
I'm trying to use the Rest API to send a message, but the documentation is a bit unclear on where to pass the primary key?
Is the key provided inside of the Azure portal suppose to be placed in the header or body?
To Reproduce
POST XXX.webpubsub.azure.com/api/hubs/test/:send
BODY:
{
"message": "test"
}
Further technical details
I'm using the REST api because our system is built using PHP and there isn't an SDK currently.

[ ] Add the Auth part to the documentation

A sample broadcast request:
POST https://demo.webpubsub.azure.com/api/hubs/chat/:send?api-version=2021-05-01-preview HTTP/1.1
Host: demo.webpubsub.azure.com
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYmYiOjE2MzEwODA3MTAsImV4cCI6MTYzMTA4MTAxMCwiaWF0IjoxNjMxMDgwNzEwLCJhdWQiOiJodHRwczovL2RlbW8ud2VicHVic3ViLmF6dXJlLmNvbS9hcGkvaHVicy9jaGF0LzpzZW5kP2FwaS12ZXJzaW9uPTIwMjEtMDUtMDEtcHJldmlldyJ9.xxx
Content-Type: text/plain
Content-Length: 5

hello

The required header is the Authorization header that uses the JWT bearer token to auth the request. For example for the above sample request, the token contains the below header and payload. The aud should be exactly the same as the request URL.

Also here is a sample code generating the JWT token in JavaScript

That worked right away! Thank you for the help!


HQQ OOMs on large models

Hey, I have a machine with two 4090 GPUs (24 GB VRAM each). When I try to run HQQ quantization of Llama-2-70B:
from hqq.engine.hf import HQQModelForCausalLM, AutoTokenizer

#Model and setttings
model_id      = 'meta-llama/Llama-2-70b-chat-hf'
compute_dtype = torch.float16
device        = 'cuda:0'

#Load model on the CPU
######################
model     = HQQModelForCausalLM.from_pretrained(model_id, torch_dtype=compute_dtype)
tokenizer = AutoTokenizer.from_pretrained(model_id)

#Quantize the model
######################
from hqq.core.quantize import *
quant_config = BaseQuantizeConfig(nbits=4, group_size=64)
model.quantize_model(quant_config=quant_config, compute_dtype=compute_dtype, device=device)

the first half of the layers seem to work fine, but then it OOMs, presumably because it tries to put the entire quantized model on a single GPU device. For Llama-2-70B, I could try renting an A100 machine and that should work, but for even larger models (eg. Grok-1) it would be impossible to fit the entire thing on a single GPU. Is splitting quantization across multiple GPUs supported, or planned to be supported in the future? Thanks :)

Hi @rationalism, yeah unfortunately loading automatically to multiple GPUs is not supported. Maybe you can try:

Splitting the model into two parts and quantize each one on a different GPU. This is the patching function that replaces the linear layer with HQQLinear: https://github.com/mobiusml/hqq/blob/master/hqq/models/base.py#L219C13-L219C26 . You also would need to transfer the rest of the layers to the right GPU, and make sure to add a call that transfers the output to the right GPU (only at the end of the first model part).
Use Mixtral instead, with meta-data CPU offloading. This one runs on a single 24GB and is very close to the original model (71.10 llm eval score vs. 72.62): https://huggingface.co/mobiuslabsgmbh/Mixtral-8x7B-Instruct-v0.1-hf-attn-4bit-moe-3bit-metaoffload-HQQ

Otherwise, I can take a stab at it and see how to do it on 2 GPUs

Hey, I have a machine with two 4090 GPUs (24 GB VRAM each). When I try to run HQQ quantization of Llama-2-70B:
from hqq.engine.hf import HQQModelForCausalLM, AutoTokenizer

#Model and setttings
model_id      = 'meta-llama/Llama-2-70b-chat-hf'
compute_dtype = torch.float16
device        = 'cuda:0'

#Load model on the CPU
######################
model     = HQQModelForCausalLM.from_pretrained(model_id, torch_dtype=compute_dtype)
tokenizer = AutoTokenizer.from_pretrained(model_id)

#Quantize the model
######################
from hqq.core.quantize import *
quant_config = BaseQuantizeConfig(nbits=4, group_size=64)
model.quantize_model(quant_config=quant_config, compute_dtype=compute_dtype, device=device)

the first half of the layers seem to work fine, but then it OOMs, presumably because it tries to put the entire quantized model on a single GPU device. For Llama-2-70B, I could try renting an A100 machine and that should work, but for even larger models (eg. Grok-1) it would be impossible to fit the entire thing on a single GPU. Is splitting quantization across multiple GPUs supported, or planned to be supported in the future? Thanks :)

Same problem.

@mobicham Thanks. With larger models like DBRX coming out this year, I think being able to split across multiple GPUs will be an important feature to manage that
https://www.databricks.com/blog/introducing-dbrx-new-state-art-open-llm

@mobicham I have rtx 4090 and 128gb ram, is it possible to load the original mixtral instruct and quantize it using HQQ ? Currently my script gets killed while loading as in the example file, I suppose I need to use your already quantized mixtral you linked , the 2-bit 4-bit , right?

I managed to solve it by increasing WSL memory allocation and page swap file, nice! :)

Yeah increasing the swap should do it, but it's gonna be  slow.
Otherwise, you can use this branch of transformers that supports on-the-fly loading and HQQ quantization, so you don't need a lot of ram: https://github.com/huggingface/transformers/pull/29637/
Soon it will be integrated into transformers and you wouldn't face this memory issue, I just need to fix a couple of things for the pull request.

Would love to be able to actually use this model lol: https://huggingface.co/catid/cat-llama-3-70b-hqq
Need support for device_map="auto"

Yeah I am aware of this, there should be a simple fix but I've been very busy with other things. I hope I will have the time to take a look at it in the next days. Sorry for the delay!

You can now shard quantized models on multiple gpus. Just pass the list of devices as a list like this:
model.quantize_model(quant_config=quant_config, compute_dtype=compute_dtype, device=['cuda:0', 'cuda:1'])

You still need to have the main model on CPU before quantizing. Will see how to dynamically dispatch directly to the gpu.

@catid making it work with "from_quantized" would require some additional work. But if you quantize directly it should work fine, as long as it's an official HF model that follows the same layer naming logic.

Closing this since HQQ now is integrated with transformers: https://github.com/huggingface/transformers/pull/29637


Publish VSCode extension to Open VSX

Description
Currently you publish the VSCode extension to the official Visual Studio Marketplace (which is already very nice :blush:). It would be great if you also make the app available on Open VSX which is an open-source registry for VS Code extensions and managed by the Eclipse foundation.
Thus users of VSCodium could also use the app seamlessly.
Suggested solution
The publishing process is described in their wiki.
Alternative
No response
Additional context
No response

will do this today!

looks like they are having some issues, but once that resolved, ill publish it

Thx 😍

Ah sorry. Didn't see it is already requested in the correct project https://github.com/marimo-team/vscode-marimo/issues/26

It has be published: https://open-vsx.org/extension/marimo-team/vscode-marimo, and extension verification in progress (https://github.com/EclipseFdn/open-vsx.org/issues/2653)


Update delete_hanging.py

Maybe you dont want to share this...

Oops.. thanks.. forgot to add it into .gitignore.. thank... Removing it from history.