Build failure on react-native init app

Hi, forgive my inexperience working with iOS. Following the instructions in the README (a few times now, by my count and as a check against human error), I am unable to build successfully.
My versions for React Native are as follows:
react-native-cli: 2.0.1
react-native: 0.59.5
Code from my sample project is here: https://github.com/tryboppity/react-native-share-extension-boilerplate
The only modifications I've made have been those prescribed in the README of this guide plus tweaking the build scheme. Prior to the latter, builds fail and I get error messages in XCode:

After adding React to the top of the scheme and unchecking the "parallelize" option, the warnings above go away, but I am still unable to build, getting this slew of errors:

Are the instruction in this README out of date? Is there something simple I'm missing?
Thanks!

Fixed via https://github.com/facebook/react-native/issues/23183


Android build error in PackageList.java

I'm getting the following error when running react-native run-android
/Users/.../android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:41: error: package com.lugg.ReactNativeConfig does not exist
import com.lugg.ReactNativeConfig.ReactNativeConfigPackage;
                                 ^
/Users/.../android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:136: error: cannot find symbol
      new ReactNativeConfigPackage(),
          ^
  symbol:   class ReactNativeConfigPackage
  location: class PackageList

What I did:

yarn add react-native-config
Added this line apply from: project(':react-native-config').projectDir.getPath() + "/dotenv.gradle" to android/app/build.gradle
react-native run-android

Versions:
react-native: 0.63.3
react-native-config: 1.4.1

Any news on this ? getting similar...

I'm getting a similar problem with another lib, looks like it didn't link the native files

What have worked for me was uninstaling the package, then reinstaling again with a --save.
After that i run a gradlew clean  in the android folder and a npx react-native run-android at the root folder

Anyone manage to solve this? (I tried the above but no joy), getting the same error error: cannot find symbol           packges.add(new ReactNativeConfigPackage());

I had this issue, it was connected to #727 - I somehow had both the new and old import statement in my MainApplication.java


Add regular and semibold typefaces of Inter font

As requested by @GBKS.

Concept ACK.
To reduce risk of conflicts during syncing with the main repo I'd refrain from the first commit.


helm-tool lint doesn't detect values that are in functions

In https://github.com/cert-manager/approver-policy/pull/387#issuecomment-1971424168 I noticed some helm-tool lint warnings which seem like false positives:
$ make verify-helm-values
/home/richard/projects/cert-manager/approver-policy/_bin/tools/helm-tool lint -i deploy/charts/approver-policy/values.yaml -d deploy/charts/approver-policy/templates -e deploy/charts/approver-policy/values.linter.exceptions
value missing from templates: tolerations
value missing from templates: affinity
value missing from templates: nodeSelector
Could not lint: values.yaml and templates are not in sync
make: *** [make/_shared/helm///helm.mk:106: verify-helm-values] Error 1

The template looks like this:
$ make verify-helm-values
/home/richard/projects/cert-manager/approver-policy/_bin/tools/helm-tool lint -i deploy/charts/approver-policy/values.yaml -d deploy/charts/approver-policy/templates -e deploy/charts/approver-policy/values.linter.exceptions
value missing from templates: tolerations
value missing from templates: affinity
value missing from templates: nodeSelector
Could not lint: values.yaml and templates are not in sync
make: *** [make/_shared/helm///helm.mk:106: verify-helm-values] Error 1

For clarity, it does detect values in functions, just not all functions.

helm-tool now detects much more variables.
eg. the case discussed here has been fixed
The tool might still not be perfect, please open a new issue when you find new issues.


[Addition]: Self witnessing spoofing farm

Hotspot b58 Addresses
113GX5wsG1we6M4zgTbBt2egEc2SwdQugesLDwuvossWxR8Ussy
11dREjDkgftuMcKodWLW9HWx8T19xditNCBH3QtZBSaSGeRQzau
11gGytWaGawk2ecTy1CdtiegX5Ctj3sJ91SxyVbJdpcUeLZmKUg
11HLXmEPkaK47TXCwC5xsdwdzZ48F3iTRopwe9qNYMqnC5Yo2px
11LwQ7CTJXPV7EfxoJcAvdssq3Vbbi2JJVRHomUa84zFZnMTaSD
11MdYNt8wn7NkcsfNftghebMcuwRi65AJ96SyJPuYGej58PjHJQ
11VMd1QpebWK5EDu5v3JibGdavB5kRTmGi1m4wQshjwZVcpcVUa
Discord Handle
No response
Reason(s)
all 7 hotspots belong to the same wallet. same location and only self witnessing

High clustering co and clique size.

Also on top of previously denylisted hotspots which seems to be a theme.


[MultiSelect] Encountered two children with the same key

When i use the MultiSelect component and i select multiple items withe the same labelfield, but with a different valuefield, i get this warning Encountered two children with the same key 'Name of label field'.
I think the problem is, that you have set the labelfield as a key, instead of valuefield inside the renderSelectedItems.

hi @TommysG ,
Maybe your data has duplicate id.

Yes I have data with duplicate labelField. But should label be unique or only value?

I'm facing the same issue, don't know why this was marked as completed.
If you serve this data array, for example, to the MultiSelect component you'll received
const myJ = [
  {Name: "GenericName", Id: 1},
  {Name: "GenericName", Id: 2}
]

<MultiSelect
data={myJ]
labelField="Name"
valueField="Id"
renderSelectedItem={(item, unSelect) => (
          <TouchableOpacity onPress={() => unSelect && unSelect(item)}>
            <View style={styles.selectedStyle}>
              <Text style={styles.textSelectedStyle}>{item.Nume}</Text>
              <Image style={{width: 20, height: 20, tintColor: "white"}} source={IMAGES.xCircle}/>
            </View>
          </TouchableOpacity>
        )}
/>

So I believe @TommysG is right. Shouldn't the Id field be used?


Small screen resolution precision

It appears that the branch '{% octicon "git-branch" aria-label="The branch icon" %}' gets removed past a certain resolution and this tutorial, altho correct, becomes somewhat of a big question mark.
I have never had the issue happen until i started using this 15 inches NEC monitor SIDEWAYS as a second monitor on my current dev stack in order to test out somewhat accurately some odd resolutions mobiles have and their effects on browsing.
I couldn't figure out why i had been able to delete branches from the web gui for all i can remember and now, very very confusingly, couldnt figure out it for the life of me. Even so i had to google it because it killed my chi.
Decided to add to the docs, please feel free to do whatever you want with that and, thanks!

Why:
caused an issue as described when using small resolution screens which hide the subject
Closes #13662
What's being changed:
just a precision within a NOTE block
Check off the following:

[X] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[X] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

This is the result of command xrandr on the computer i'm using with regards to the monitor in question.
VGA-1 connected 768x1024+1920+0 right (normal left inverted right x axis y axis) 304mm x 228mm
   1024x768      75.03 +  70.07    60.00*
   832x624       74.55
   800x600       72.19    75.00    60.32    56.25
   640x480       75.00    72.81    66.67    59.94
   720x400       70.08

It is rotated to the right. and is part of a larger display server of (1920+768)=2688 px
Thanks!

Could also mention that the thing can be accessible via url /branches within a project

@mathieu-aubin
Thanks so much for opening a PR! I'll get this triaged for review :zap:

I think that we should fix this bug instead of documenting the workaround.  🤔  Let me pass this on to the engineering team.

@mathieu-aubin, thanks for doing this! I agree with @ethomson above that we should treat this as a bug to fix so that the workaround wouldn't be necessary.

Thanks for weighing in! I'm going to close out this PR since we will fix the bug instead of documenting this, but we hope to see more contributions from you in the future @mathieu-aubin !

Great. All i hoped for was some kind of resolution. But... is this fair to call this a BUG? I mean... it seems the site IS functionnal yet, the DOCS dont take the programming into consideration. Is this a bug or an omission, a mishap in writting docs, maybe not writting as universally as it best would be.
Dont get me wrong, i will, again, repeat; im all about resolution on issues that might pose new users or heck, all for any kind of resolution.

I appreciate whatever input you have on my concern, no matter opinionated with regards to me being 'pulling hairs' or bein anal about a docs group being accurate.
That being said, its all 'write' with me, i wont loose sleep over it as i dont do much of that lately!
Cheers and may the shwartz be with j00


Make boiling oil engineers pour automatically.

It is hard to use boiling oil pot engineers as a human player, you have to manually pour the oil in a certain direction which makes them a poor option for defence compared with fire throwers, as it takes a lot of time to manually make several oil pot throwers use their oil, when there may be other things you need to do with castle defense such as recruiting new troops. It would be good if you could have the option to put oil pot engineers on aggressive mode and they would automatically pour the oil if units were in range, then they would automatically return and get oil and go back to their position.

Actually, you can do that!
On aggressive mode, they will pour their oil as soon as 1 enemy unit is in range, and on defensive mode they will pour their oil as soon as 3 enemy units are in range.
Right after they emptied their oil pot, they will run back to the oil smelter, get their pot filled up again and then return to their previous position on some wall/tower/gate.

Oops, had the original pre-Warchest version of Stronghold Crusader where the oil engineers didn't appear to autopour and haven't used oil engineers since, didn't realise this was fixed now officially!


plugin/git: fix errors inside bare repo

Hi there!
Sometimes you need to go into a bare repository, and then you get an error:

As you see, the git plugin is executing commands that it should not run here.
I tried to fix that. Now it displays a symbol instead, indicating you're in a bare repo:

Color & symbol can be set by the user.
Please tell me if you have any suggestions :)

Is it suitable like this?


Advantage/Differences vs trpc

What are the differences/advantages compared to trpc?

I’ve written about this on the wiki (here ), but to summarize - they’re different solutions to a similar problem. Importantly, Tempo is not limited to Typescript <-> Typescript communication. It will ultimately support RPC across language domains, so if you have a browser client and a Rust backend that use case is supported.

I just read it now and I'm very curious on how Bebop works under the hood to guarantee runtime type checking in JavaScript.
Does it work similarly to Zod?


Tina CMS

Notes

We must use cms function as middleware to prevent fetching Tina CMS data layer:

SSR should get data directly from filesystem always than possible;
No client-side hydration for CMS data at all (excepting on /admin/ obviously 😄 );
Tina CMS client imported only on admin preferably (not even bundled on storefront scripts);

We need a subpath (__preview/** 🤔 ) to identify preview on CMS for some SSRed-only components, specially content heavy ones:

{!isPreview && <Content />}
{isPreview && <Content client:only />}

For Tina Cloud to work (I think) tina folder must be committed on store repository instead (currently getting no branches found error);
Must edit Home.astro (or something) to test with <Post client:only />;
Needs workaround for CJS/ES error https://github.com/tinacms/tinacms/issues/3764 ;

Inspired by https://github.com/tinacms/tinacms/pull/3260

https://twitter.com/leomp1208/status/1641596449795260418

Só resta testar comitando as devidas alterações no https://github.com/ecomplus/store (branch tinacms), verificar se o build pro Tina Cloud funciona com isso...


Point clouds

Fixes ZED pointcloud quality issue #25
ColoredPointCloudType replaced by PointCloud dataclass
Open3D integration
Tutorial notebook
Low confidence point removal and cropping to a 3D bounding box

@Victorlouisdg, I'm afraid my refactor of #105  has caused some merge conflicts

Should be easy to fix, I'll have a look next Monday.


⚠ PrivateHD has degraded performance

In ea24686, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1480 ms

Resolved: PrivateHD performance has improved in 72a98a7.


tomlkit incorrectly parses pyproject.toml

[x ] I am on the latest Poetry version.
[ x] I have searched the issues of this repo and believe that this is not a duplicate.
[ x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: MacOS High Sierra 10.13.6
Poetry version: 0.11.4
Link of a Gist with the contents of your pyproject.toml file:

Issue

The tomlkit library incorrectly parses table arrays in the tool namespace. The above-mentioned pyproject.toml should produce the following json:
{
  "tool": {
    "poetry": {
      "name": "blogify",
      "version": "0.1.0",
      "description": "",
      "authors": [
        "Stephan Fitzpatrick<EMAIL_ADDRESS>      ],
      "dependencies": {
        "python": "*",
        "shell_utils": "^0.6.0",
        "jupyterlab": "^0.33.6",
        "watchdog": "^0.8.3",
        "toml": "^0.9.4",
        "tomlkit": "^0.4.0"
      },
      "dev-dependencies": {
        "pytest": "^3.0"
      }
    },
    "foo": [
      {
        "name": "first"
      },
      {
        "name": "second"
      }
    ]
  }
}

tomlkit deserializes it into the following structure
{'tool': [{'foo': [{'name': 'second'}]}],
 'tool': [{'foo': [{'name': 'second'}]}]}

If this issue is restricted to TOML Kit and not specific to Poetry, shouldn't you file this over on TOML Kit's issue tracker?

Perhaps, but I figured it would have more visibility here. I don't know that any other library authors are using tomlkit

I just released tomlkit 0.4.1 which should fix the issue.


Add exception handling to dataframe generation

Codecov Report

Merging #146 into master will decrease coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #146      +/-   ##
==========================================
- Coverage   53.06%   53.06%   -0.01%
==========================================
  Files         343      343
  Lines       25778    25781       +3
  Branches     3345     3345
==========================================
+ Hits        13680    13681       +1
- Misses      11402    11404       +2
  Partials      696      696

Impacted Files
Coverage Δ

lib/python/treadmill/reports.py
83.55% <50%> (-1.02%)
:arrow_down:

Continue to review full report at Codecov.

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


Image alt text (test content?)

This issue can probably be closed right away since I think it's only a symptom of adding some quick test content. But the alt text should describe the image. It is currently the title of the ebook which isn't helpful for understanding the image.
Eg. https://ebooks.lullabot.com/ebooks/jponch-sample/chapters/chapter-1/
Current alt text: Why your CMS project will fail
Better alt text: A cartoon of a person crawling out of a browser window surrounded by various icons including an image icon, a notification bell, and a checklist.

hrm, no it is relevant even to real content as we haven't really given thought to alt text, or how to enter that for an image. @huntermacd what do you think? possibly use front-matter for this, since the image is defined in front-matter already?


Multiple Reward Token Harvesting

Make it possible for strategies to sell more than one type of reward token. This will be used initially for our Convex strategy, which earns CRV and CVX but is currently limited to harvesting CRV only.

@sparrowDom This is implemented, right?
https://github.com/OriginProtocol/origin-dollar/blob/0d30731f7167da0f410db469baaaf74897408cf6/contracts/contracts/harvest/Harvester.sol#L343
Closing - pleas re-open if I'm missing something...

yup, thanks!


Error booting 'Apollo OS' 0.0.2 floppy in QEMU

Dear @primis , first of all thank you very much for releasing Apollo OS as a floppy (which could be installed in coreboot/SeaBIOS ROM and booted from there) But before doing that I tried booting your 0.0.2 floppy in QEMU with the following command:
qemu-system-x86_64 -L . -m 256 -fda ./floppy.img -usbdevice tablet -vga vmware -localtime
and only see
GRUB Loading stage2.........
Press 'ESC' to enter the menu... 0

followed by
Booting 'Apollo OS'

root (fd0)
 Filesystem type is fat, using whole disk
kernel /Apollo/sys.mod

and after that QEMU reboots. If there is a way to collect more debug information, please tell me and I will try to provide it

The floppy image is outdated. It needs to be updated
On Mon, Dec 17, 2018 at 3:25 PM informer2016<EMAIL_ADDRESS>wrote:

Dear @primis https://github.com/primis , first of all thank you very
much for releasing Apollo OS as a floppy (which could be installed in
coreboot/SeaBIOS ROM and booted from there) But before doing that I
tried booting your 0.0.2 floppy
https://github.com/primis/Apollo/archive/0.0.2.zip in QEMU with the
following command:
qemu-system-x86_64 -L . -m 256 -fda ./floppy.img -usbdevice tablet -vga
vmware -localtime
and only see
GRUB Loading stage2.........
Press 'ESC' to enter the menu... 0
followed by
Booting 'Apollo OS'
root (fd0)
Filesystem type is fat, using whole disk
kernel /Apollo/sys.mod
and after that QEMU reboots. If there is a way to collect more debug
information, please tell me and I will try to provide it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/primis/Apollo/issues/4, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABflg9cPpwEuJ1JaPSW2DfYTIut1xfaqks5u5_2ogaJpZM4ZXEmM
.

@primis Would be nice if you could make a new release, then I could test it, maybe as a part of BIOS if it works in QEMU

@primis Happy coming New Year ! :christmas_tree: :santa: :gift:

Floppy image (bin/floppy.img) is now current image and will continue to be updated regularly -- Closing Issue.


Include project name/path into "Products" group ID generation logic

Resolves https://github.com/tuist/XcodeProj/issues/538
Short description 📝
Add referenced project name or path whichever is available to the permanent "Products" group ID generation logic.
Solution 📦
The solution doesn't break the reproducibility of permanent ID generation and produces different ID for each added referenced project

I am not sure why Changelog fails, please let me know if anything needs fixing.

Thanks @pepibumur ! Changelog is updated please check.

😅Would you mind solving the conflicts @damirdavletov? We can merge afterward.

@pepibumur Done!

Hi @pepibumur! Would you help me getting this PR merged? Do I need to do anything else?

Sure! I forgot about this PR completely. Thanks for the reminder :)

Thanks @pepibumur ! Nice gif! 😊


fix: return "unknown command" instead of "no help topic" error when unknown (sub)command is passed

Follow-up to #312

@danxmoran LGTM, thanks for taking this over and merging it


Obvious way to create new fiddle from scratch

Right now I think the only way to create new fiddle is to go to https://studio.nearprotocol.com
We should have more explicit action somewhere.

Fixed already, there is "New" button


[ISSUE] Possible incompatibility issue with Quilt

https://gist.github.com/Sunconure11/7a10bbf66d91eb57f7bc6efb5b79a94c

Testing now.

Let me know if it does/doesn't work

Noticing a crash, but it is one that is unrelated to your mod.

Okay, just making sure before I close the issue, are there any other questions/feedback that you may want to give in relation to this issue?

No.


#48 applying INTENT on share , feedback and other option

rate us click open play store
share click show pop with all sharing option of app link
feedback open mail
privacy policy open play store

@maityamit can you please review this PR.


[Event Request] Codeunit 423 "Change Log Management" - OnBeforeLogModification

Hi, would it be possible to get an OnBeforeLogModification event in codeunit 423 (Change Log Management), like this:
    procedure LogModification(var RecRef: RecordRef)
    var
        xRecRef: RecordRef;
        FldRef: FieldRef;
        xFldRef: FieldRef;
        i: Integer;
        IsReadable: Boolean;
    begin
        OnBeforeLogModification(RecRef); // New Event
        if RecRef.IsTemporary then
            exit;

        if not IsLogActive(RecRef.Number, 0, 1) then
            exit;

        xRecRef.Open(RecRef.Number);
        xRecRef."SecurityFiltering" := SECURITYFILTER::Filtered;
        if xRecRef.ReadPermission then begin
            IsReadable := true;
            if not xRecRef.Get(RecRef.RecordId) then
                exit;
        end;

        for i := 1 to RecRef.FieldCount do begin
            FldRef := RecRef.FieldIndex(i);
            xFldRef := xRecRef.FieldIndex(i);
            if IsNormalField(FldRef) then
                if Format(FldRef.Value) <> Format(xFldRef.Value) then
                    if IsLogActive(RecRef.Number, FldRef.Number, 1) then
                        InsertLogEntry(FldRef, xFldRef, RecRef, 1, IsReadable);
        end;
    end;

    [IntegrationEvent(false, false)]
    local procedure OnBeforeLogModification(var RecRef: RecordRef);
    begin
    end;

#12532
Thanks!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Add macro for finding an existing snapshot

Potential implementation for #199

Closed as the original issue is resolved.


User.Identity.Name empty when implementing Azure B2C in Blazor WebAssembly

This issue is about the following doc page:
Secure an ASP.NET Core Blazor WebAssembly hosted app with Azure Active Directory B2C
Description
When trying to access HttpContext.User.Identity.Name in the Server project inside an API that is protected by the [Authorize] attribute, the name will appear empty. This while I am logged in at the name is shown in the Client application just fine.
Fix
I had to add the following snippet in Startup.cs to fix this.
services.AddAuthentication(AzureADB2CDefaults.JwtBearerAuthenticationScheme)
		.AddAzureADB2CBearer(options => Configuration.Bind("AzureAd", options));

services.Configure<JwtBearerOptions>(AzureADB2CDefaults.JwtBearerAuthenticationScheme, options =>
{
	options.TokenValidationParameters = new Microsoft.IdentityModel.Tokens.TokenValidationParameters()
	{
		NameClaimType = "name"
	};
});

I am not sure if this is the right place to report it, not even sure if it is something that should be fixed. At most it will hopefully help other people that come across the same issue and save them some time.

Can you create an issue from the doc page? That will connect the doc to the issue. Go to the bottom of the page and select This page .


Nonexistent signal: frame_pre_draw

Godot version:
Godot 3.2 alpha 3
OS/device including version:
Ubuntu 19.10
Issue description:
When I run project with Softbody node I have this error:
ERROR: _disconnect: Nonexistent signal: frame_pre_draw.
   At: core/object.cpp:1518.

Minimal reproduction project:
ZRW.tar.gz

The problem is here, if the mesh is not valid the signal is disconnected, even if it was never connected in the first place:
https://github.com/godotengine/godot/blob/aaa9751de3ef6b39217113aa26f018b25d5878e8/scene/3d/soft_body.cpp#L455-L465
There might be similar issues around other uses of this signal:
$ rg frame_pre_draw
servers/visual_server.cpp
2299:   ADD_SIGNAL(MethodInfo("frame_pre_draw"));

servers/visual/visual_server_raster.cpp
100:    VS::get_singleton()->emit_signal("frame_pre_draw");

doc/classes/VisualServer.xml
3935:           <signal name="frame_pre_draw">

scene/2d/cpu_particles_2d.cpp
1035:           VS::get_singleton()->connect("frame_pre_draw", this, "_update_render_thread");
1040:           VS::get_singleton()->disconnect("frame_pre_draw", this, "_update_render_thread");

scene/3d/cpu_particles.cpp
1123:           VS::get_singleton()->connect("frame_pre_draw", this, "_update_render_thread");
1127:           VS::get_singleton()->disconnect("frame_pre_draw", this, "_update_render_thread");

scene/3d/soft_body.cpp
459:            VS::get_singleton()->connect("frame_pre_draw", this, "_draw_soft_mesh");
463:            VS::get_singleton()->disconnect("frame_pre_draw", this, "_draw_soft_mesh");

scene/resources/texture.cpp
2173:   VisualServer::get_singleton()->connect("frame_pre_draw", this, "_update_proxy");

Hi I proposed some fix- it's my first contribution, so any tips are welcome :)

Fixed by #33147.


Add ext2 fs support to devmapper snapshotter

This PR adds support for ext2fs for devmapper snapshotter.
We have a use-case (NetBSD) where ext4 or xfs is not an option and since adding ext2 support could be a configurable parameter (fs_type = "ext2" in config.toml), and not that intrusive, it didn't seem like such a bad idea.
FYI, we are building a custom handler to boot unikernels -- we are trying to minimize the steps to prepare the storage part, and if we could give the snapshot directly to the unikernel, that would save us the time from generating an image file or doing some other kind of hack.

thanks for your prompt response!
we run NetBSD-based unikernels on Linux, so no need. The rationale is to be able to use the DM block device directly from the unikernel.


Add support for resolving UUIDs from assigned names

e.g. https://www.bluetooth.com/specifications/gatt/services

This is supported in each of the Uuid classes (Services, Characteristics and Descriptors)


Issue3762

[X] Tests added / passed

(astroconda3) nmiles@nathan:dask$py.test dask/array/tests/test_array_core.py::test_stack_errs --verbose
============================================================== test session starts ===============================================================
platform darwin -- Python 3.6.5, pytest-3.6.2, py-1.5.3, pluggy-0.6.0 -- /Users/nmiles/miniconda3/envs/astroconda3/bin/python
cachedir: .pytest_cache
rootdir: /Users/nmiles/dask, inifile: setup.cfg
plugins: remotedata-0.3.0, openfiles-0.3.0, doctestplus-0.1.3, arraydiff-0.2
collected 1 item

dask/array/tests/test_array_core.py::test_stack_errs PASSED                                                                                [100%]

============================================================ 1 passed in 0.19 seconds ============================================================

[x] Passes flake8 dask

closes #3762

Thanks for submitting this @nmiles2718 !
A couple points:

We should add a test for this behavior.  Typically when testing exceptions I use the pytest.raises context manager
with pytest.raises(ValueError) as info:
    # do something bad
assert 'informative message' in str(info.value)

When we were talking at SciPy (I assume that this is the same person, please correct me if I'm wrong) we brought up the idea of suggesting that perhaps the user meant to use concatenate instead.  Good idea?  Bad idea?  Thoughts?

@mrocklin yep, same person from SciPy!

If you take look at #3762, I noted exactly this but was ensure if it was worth editing the pre-existing test. In short, info.value returns the entire error message whereas str(info) (which is currently used) only returns the error message up to the first '\n' character it finds.

To be honest, I had intended to include that but just forgot because I went off on this tanget of "why is this assertion failing when it definitely shouldn't." I don't see any harm in omitting though. The only reason I ran into trouble with it was because I just quickly copy-and-pasting an example about reading datasets from hdf5. As soon as I saw the error it was pretty clear to me that I should be concatenating into a single array, as opposed to, stacking the arrays along a new dimension. The trouble was I had to scroll up pretty far to actually see the error message because the shapes of all ~10,000 datasets I had attempted to stack were printed out.

If you take look at #3762, I noted exactly this but was ensure if it was worth editing the pre-existing test. In short, info.value returns the entire error message whereas str(info) (which is currently used) only returns the error message up to the first '\n' character it finds.

The test suite previously didn't catch the project's poor behavior here.  We should add a test to ensure that this fix continues into the futue.  If someone were to revert your fix, they should get a failing test telling them what they've done that was wrong.  Would something like the following work?
with pytest.raises(ValueError) as info:
    # bad thing
assert len(str(info.value)) < 200  # or something similar

Ok, so what you're saying is that we should:

Maybe fix (all) the assert statement(s) to use info.value attribute rather than the overloaded __str__() method on the ExceptionInfo object?
Add an additional test so that moving forward no one gets away with using str(info) vs info.value for checking if something is in the actual error message?

Possibly.  For this PR all we need is a single test that tests that the error for da.stack is not absurdly long.  If there is a test within the test suite now that can be modified to accomplish this then yes, lets modify that (and only that).  Otherwise lets write a new test.  Hopefully this is something like a five-line addition to your current PR here.

Ok sounds good. I'll just modify the existing test function test_stack_errs() to check the length of the message. I'll have to increase the number of arrays used so that it will fail the tests if someone reverts the fix because my error message is longer than the one currently in master. Thankfully, the length of mine is roughly fixed and so I can just set that (plus some padding) to be the upper limit for the length of the error message. That way if they go back to printing the shapes of each individual array it will fail the length check.

@mrocklin, not sure why it is failing now. Looking at the logs it seems to be an issue with the build timing out.

Looks good to me.  Merging.  Thanks @nmiles2718 !


Cloning your project doesn't work because of the  file.

Trying to cloning your repository works, but checking out either of the branches currently doesn't because git throws an error.

> git checkout -q main
error: invalid path 'app/libs/'

On Windows 11.
Running
git config core.protectNTFS false fixes the issue but it is not something one wants to have to disable I guess?

Cloning through WSL worked for me.  I did not have to change my git configuration on Windows.  Then you can remove or replace the offending file.


memo field does not exist for Transaction

Description
TransferTransaction doesn't have a function for setting memo.
Steps to reproduce
Try to write code as below additional context with memo.
Additional context
let response = try await TransferTransaction()
                    .hbarTransfer(AccountId.fromString(coinWallet.getWalletAddress()), sendAmount * -1)
                    .hbarTransfer(AccountId.fromString(toAddress), sendAmount)
                    .memo("memo test") // <- cannot set memo for now
                    .execute(client)

Hedera network
mainnet
Version
0.14.0
Operating system
macOS

Hi! Thanks for reaching out
This is a known limitation currently, I can prioritize it getting added before the next release


Expand Machine Code Analysis page in the performance guide

This is a tracking issue for expanding upon the machine code analysis part of the perf guide.
To do

[ ] how to emit assembly from Rust code (e.g. cargo-asm)
[ ] how to emit IACA / llvm-mca markers with inline assembly
[ ] give an example on how to intepret results, in the context of one of the example benchmarks

References

IACA homepage
"What is IACA and how to use it?" on StackOverflow
TheIronBorn's usage of IACA with movmsk.c
LLVM MCA docs

I made a crate last year that makes using IACA slightly easier: https://github.com/hdevalence/iaca-marker-macros


Add fee estimation before transaction

To calculate the cost of gas for a transaction, you need to use TVM. At the moment, TVM development is under heavy development in branch: https://github.com/andreypfau/ton-kotlin/tree/tvm

Is it possible now to estimate fee before transaction? I couldn't figure out how to use TVM for fee estimation


rangenet.launch运行报错问题

我的配置是ubuntu20.04，GTX950M，CUDA11.3 CUDNN8.8.0 tensorrt<IP_ADDRESS> libtorch1.10
编译正常，跑rosbag.launch也没问题，但是跑rangenet.launch时报以下错误：
[07/28/2023-10:51:11] [W]  - Subnormal FP16 values detected.
[07/28/2023-10:51:11] [W] If this is not the desired behavior, please modify the weights or retrain with regularization to reduce the magnitude of the weights.
[07/28/2023-10:51:11] [W] Weights [name=node_of_582 + node_of_583.weight] had the following issues when converted to FP16:
[07/28/2023-10:51:11] [W]  - Subnormal FP16 values detected.
[07/28/2023-10:51:11] [W]  - Values less than smallest positive FP16 Subnormal value detected. Converting to FP16 minimum subnormalized value.
[07/28/2023-10:51:11] [W] If this is not the desired behavior, please modify the weights or retrain with regularization to reduce the magnitude of the weights.
[07/28/2023-10:51:11] [W] Weights [name=node_of_585 + node_of_586.weight] had the following issues when converted to FP16:
[07/28/2023-10:51:11] [W]  - Subnormal FP16 values detected.
[07/28/2023-10:51:11] [W]  - Values less than smallest positive FP16 Subnormal value detected. Converting to FP16 minimum subnormalized value.
[07/28/2023-10:51:11] [W] If this is not the desired behavior, please modify the weights or retrain with regularization to reduce the magnitude of the weights.
[07/28/2023-10:51:11] [W] Weights [name=node_of_585 + node_of_586.bias] had the following issues when converted to FP16:
[07/28/2023-10:51:11] [W]  - Subnormal FP16 values detected.
[07/28/2023-10:51:11] [W] If this is not the desired behavior, please modify the weights or retrain with regularization to reduce the magnitude of the weights.
[07/28/2023-10:51:22] [E] 1: [wrapper.cpp::plainGemm::206] Error Code 1: Cublas (CUBLAS_STATUS_NOT_SUPPORTED)
[07/28/2023-10:51:22] [E] 2: [builder.cpp::buildSerializedNetwork::636] Error Code 2: Internal Error (Assertion engine != nullptr failed. )
terminate called after throwing an instance of 'std::runtime_error'
what():  failed to build tensorrt engine
[ros1_demo-2] process has died [pid 98179, exit code -6, cmd /home/liangyuyao/Lidar/rangetnet_pp/devel/lib/rangenet_pp/ros1_demo __name:=ros1_demo __log:=/home/liangyuyao/.ros/log/5d531702-2cf1-11ee-ba9b-bdc9299ca300/ros1_demo-2.log].
log file: /home/liangyuyao/.ros/log/5d531702-2cf1-11ee-ba9b-bdc9299ca300/ros1_demo-2*.log
请问怎么解决呢。我的launch文件的model_dir也已经进行了对应的修改

1）首先，TensorRT 会生成后缀为 .trt 的 engine 文件，你这个 what(): failed to build tensorrt engine，表示没有生成成功
2）再看你这个日志 Error Code 1: Cublas (CUBLAS_STATUS_NOT_SUPPORTED)，非我这边的问题，有较大的可能是你配置的环境存在问题
PS：早上审错题了，我以为是没有找到对应的模型文件路径，结果是还没生成出来就 GG 了

我寻思你使用 ROS1 catkin build 的话，把 logs/rangenet_pp/build.cmake.log post 一下

感谢回复，这是我的build.cmake.log，麻烦看一下:
Not searching for unused variables given on the command line.
-- The C compiler identification is GNU 9.4.0
-- The CXX compiler identification is GNU 9.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found CUDA: /usr/local/cuda (found version "11.3")
-- Using CATKIN_DEVEL_PREFIX: /home/liangyuyao/Lidar/rangenet_pp/devel/.private/rangenet_pp
-- Using CMAKE_PREFIX_PATH: /home/liangyuyao/Lidar/rangenet_pp/devel;/opt/ros/noetic
-- This workspace overlays: /home/liangyuyao/Lidar/rangenet_pp/devel;/opt/ros/noetic
-- Found PythonInterp: /home/liangyuyao/anaconda3/bin/python3 (found suitable version "3.9.13", minimum required is "3")
-- Using PYTHON_EXECUTABLE: /home/liangyuyao/anaconda3/bin/python3
-- Using Debian Python package layout
-- Found PY_em: /home/liangyuyao/anaconda3/lib/python3.9/site-packages/em.py
-- Using empy: /home/liangyuyao/anaconda3/lib/python3.9/site-packages/em.py
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /home/liangyuyao/Lidar/rangenet_pp/build/rangenet_pp/test_results
-- Forcing gtest/gmock from source, though one was otherwise available.
-- Found gtest sources under '/usr/src/googletest': gtests will be built
-- Found gmock sources under '/usr/src/googletest': gmock will be built
-- Found PythonInterp: /home/liangyuyao/anaconda3/bin/python3 (found version "3.9.13")
-- Using Python nosetests: /usr/bin/nosetests3
-- catkin 0.8.10
-- BUILD_SHARED_LIBS is on
-- Using these message generators: gencpp;geneus;genlisp;gennodejs;genpy
-- [INFO] CMAKE_BUILD_TYPE：
-- [INFO] ROS1 is available!
-- Found CUDA: /usr/local/cuda (found version "11.3")
-- Caffe2: CUDA detected: 11.3
-- Caffe2: CUDA nvcc is: /usr/local/cuda/bin/nvcc
-- Caffe2: CUDA toolkit directory: /usr/local/cuda
-- Caffe2: Header version is: 11.3
-- Found CUDNN: /usr/local/cuda/lib64/libcudnn.so
-- Found cuDNN: v8.8.0  (include: /usr/local/cuda/include, library: /usr/local/cuda/lib64/libcudnn.so)
-- /usr/local/cuda/lib64/libnvrtc.so shorthash is 8aa72235
-- Automatic GPU detection failed. Building for common architectures.
-- Autodetected CUDA architecture(s): 3.5;5.0;5.2;6.0;6.1;7.0;7.5;8.0;8.6;8.6+PTX
-- Added CUDA NVCC flags for: -gencode;arch=compute_35,code=sm_35;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_52,code=sm_52;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_86,code=compute_86
-- Found Torch: /home/liangyuyao/software/libtorch/lib/libtorch.so
-- Checking for module 'eigen3'
--   Found eigen3, version 3.3.7
-- Found Eigen: /usr/include/eigen3 (Required is at least version "3.1")
-- Eigen found (include: /usr/include/eigen3, version: 3.3.7)
-- Checking for module 'flann'
--   Found flann, version 1.9.1
-- Found FLANN: /usr/lib/x86_64-linux-gnu/libflann_cpp.so
-- The imported target "vtkParseOGLExt" references the file
"/usr/bin/vtkParseOGLExt-7.1"
but this file does not exist.  Possible reasons include:

The file was deleted, renamed, or moved to another location.
An install or uninstall procedure did not complete successfully.
The installation package was faulty and contained
"/usr/lib/cmake/vtk-7.1/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkRenderingPythonTkWidgets" references the file
"/usr/lib/x86_64-linux-gnu/libvtkRenderingPythonTkWidgets.so"
but this file does not exist.  Possible reasons include:

The file was deleted, renamed, or moved to another location.
An install or uninstall procedure did not complete successfully.
The installation package was faulty and contained
"/usr/lib/cmake/vtk-7.1/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtk" references the file
"/usr/bin/vtk"
but this file does not exist.  Possible reasons include:

The file was deleted, renamed, or moved to another location.
An install or uninstall procedure did not complete successfully.
The installation package was faulty and contained
"/usr/lib/cmake/vtk-7.1/VTKTargets.cmake"
but not all the files it references.

-- The imported target "pvtk" references the file
"/usr/bin/pvtk"
but this file does not exist.  Possible reasons include:

The file was deleted, renamed, or moved to another location.
An install or uninstall procedure did not complete successfully.
The installation package was faulty and contained
"/usr/lib/cmake/vtk-7.1/VTKTargets.cmake"
but not all the files it references.

-- Checking for module 'libusb-1.0'
--   Found libusb-1.0, version 1.0.23
-- Found USB_10: /usr/lib/x86_64-linux-gnu/libusb-1.0.so
-- OpenNI found (include: /usr/include/ni, lib: /usr/lib/libOpenNI.so)
-- OpenNI2 found (include: /usr/include/openni2, lib: /usr/lib/libOpenNI2.so)
-- Found libusb-1.0: /usr/include
-- OpenNI found (include: /usr/include/ni, lib: /usr/lib/libOpenNI.so)
-- OpenNI2 found (include: /usr/include/openni2, lib: /usr/lib/libOpenNI2.so)
-- Found Qhull: optimized;/usr/lib/x86_64-linux-gnu/libqhull.so;debug;/usr/lib/x86_64-linux-gnu/libqhull.so
-- QHULL found (include: /usr/include, lib: optimized;/usr/lib/x86_64-linux-gnu/libqhull.so;debug;/usr/lib/x86_64-linux-gnu/libqhull.so)
-- OpenNI found (include: /usr/include/ni, lib: /usr/lib/libOpenNI.so)
-- Found PCL_COMMON: /usr/lib/x86_64-linux-gnu/libpcl_common.so
-- Found PCL_KDTREE: /usr/lib/x86_64-linux-gnu/libpcl_kdtree.so
-- Found PCL_OCTREE: /usr/lib/x86_64-linux-gnu/libpcl_octree.so
-- Found PCL_SEARCH: /usr/lib/x86_64-linux-gnu/libpcl_search.so
-- Found PCL_SAMPLE_CONSENSUS: /usr/lib/x86_64-linux-gnu/libpcl_sample_consensus.so
-- Found PCL_FILTERS: /usr/lib/x86_64-linux-gnu/libpcl_filters.so
-- Found PCL_2D: /usr/include/pcl-1.10
-- Found PCL_GEOMETRY: /usr/include/pcl-1.10
-- Found PCL_IO: /usr/lib/x86_64-linux-gnu/libpcl_io.so
-- Found PCL_FEATURES: /usr/lib/x86_64-linux-gnu/libpcl_features.so
-- Found PCL_ML: /usr/lib/x86_64-linux-gnu/libpcl_ml.so
-- Found PCL_SEGMENTATION: /usr/lib/x86_64-linux-gnu/libpcl_segmentation.so
-- Found PCL_VISUALIZATION: /usr/lib/x86_64-linux-gnu/libpcl_visualization.so
-- Found PCL_SURFACE: /usr/lib/x86_64-linux-gnu/libpcl_surface.so
-- Found PCL_REGISTRATION: /usr/lib/x86_64-linux-gnu/libpcl_registration.so
-- Found PCL_KEYPOINTS: /usr/lib/x86_64-linux-gnu/libpcl_keypoints.so
-- Found PCL_TRACKING: /usr/lib/x86_64-linux-gnu/libpcl_tracking.so
-- Found PCL_RECOGNITION: /usr/lib/x86_64-linux-gnu/libpcl_recognition.so
-- Found PCL_STEREO: /usr/lib/x86_64-linux-gnu/libpcl_stereo.so
-- Found PCL_APPS: /usr/lib/x86_64-linux-gnu/libpcl_apps.so
-- Found PCL_IN_HAND_SCANNER: /usr/include/pcl-1.10
-- Found PCL_POINT_CLOUD_EDITOR: /usr/include/pcl-1.10
-- Found PCL_OUTOFCORE: /usr/lib/x86_64-linux-gnu/libpcl_outofcore.so
-- Found PCL_PEOPLE: /usr/lib/x86_64-linux-gnu/libpcl_people.so
-- [INFO] PCL_VERSION is 1.10.0
-- [INFO] CUDA is available!
-- [INFO] CUDA Libs: /usr/local/cuda/lib64/libcudart.so
-- [INFO] CUDA Headers: /usr/local/cuda/include
-- [INFO] CUDNN is available!
-- [INFO] CUDNN_LIBRARY: /usr/local/cuda/lib64/libcudnn.so
-- [INFO] TensorRT is not installed through DEB package, should specify the environment parameter TENSORRT_DIR explicitly
-- [INFO] NVINFER: /home/liangyuyao/software/TensorRT-<IP_ADDRESS>/lib/libnvinfer.so
-- [INFO] NVPARSERS: /home/liangyuyao/software/TensorRT-<IP_ADDRESS>/lib/libnvparsers.so
-- [INFO] NVINFER_PLUGIN: /home/liangyuyao/software/TensorRT-<IP_ADDRESS>/lib/libnvinfer_plugin.so
-- [INFO] NVONNX_PARSER: /home/liangyuyao/software/TensorRT-<IP_ADDRESS>/lib/libnvonnxparser.so
-- [INFO] TensorRT is available!
-- Configuring done
-- Generating done
-- Build files have been written to: /home/liangyuyao/Lidar/rangenet_pp/build/rangenet_pp

或显存不够
1）根据第二段日志，发现环境配置没有问题
2）根据第一段日志，发现是引擎优化时出现报错，然后退出，请查看自己的显卡是否有足够的显存来生成引擎（如文档所述大概为 3G 左右，但那个应该是初始的时候，后面优化到一定程度后就上 5G了）
PS：通过 watch -c nvidia-smi 查看运行时占用情况

感谢回复，我看了下占用情况
|   0  NVIDIA GeForce GTX 950M        Off | 00000000:01:00.0 Off |                  N/A |
| N/A   51C    P8              N/A / 200W |     1486MiB /  2048MiB |      99%      Default |
|                                         |                      |                  N/A |
大概1500MB的时候程序就终止了，终端报错如下：
[07/29/2023-16:52:12] [E] 1: [wrapper.cpp::plainGemm::206] Error Code 1: Cublas (CUBLAS_STATUS_NOT_SUPPORTED)
[07/29/2023-16:52:12] [E] 2: [builder.cpp::buildSerializedNetwork::636] Error Code 2: Internal Error (Assertion engine != nullptr failed. )
terminate called after throwing an instance of 'std::runtime_error'
what():  failed to build tensorrt engine

嗯，那大概率就是显卡的显存完全不够用了。一方面可以充钱解决硬件的问题。另一方面，我后续看看有没有可以在优化时减少显存的方案...

好的，感谢大佬
| |
L
|
|
@.***
|
---- 回复的原邮件 ----
| 发件人 | Huang @.> |
| 发送日期 | 2023年07月29日 17:13 |
| 收件人 | Natsu-Akatsuki/RangeNetTrt8 @.> |
| 抄送人 | yuyaoliang @.>,
Author @.> |
| 主题 | Re: [Natsu-Akatsuki/RangeNetTrt8] rangenet.launch运行报错问题 (Issue #9) |
嗯，那大概率就是显卡的显存完全不够用了。一方面可以充钱解决硬件的问题。另一方面，我后续看看有没有可以在优化时减少显存的方案...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


supabase.auth.logout() throws "Invalid user" error.

I found this to only happen sometimes, but couldn't figure out why:

@kiwicopple have you seen this before?

The only thing I could think is that the token is expired when you try to log out. A couple of questions:

Is the browser left open, and then you try to log out after >3 hours?
There is a logout network call about 10 requests above the erroneous network call. Did you hit the button twice? Perhaps you're logged out already and the redirect to the home screen failed for some reason

Is the browser left open, and then you try to log out after >3 hours?
I'm able to reproduce this multiple times within a time window of less than 1h

There is a logout network call about 10 requests above the erroneous network call. Did you hit the button twice? Perhaps you're logged out already and the redirect to the home screen failed for some reason
Yes, there are times where the logout call is successful. You can see in the network comms though that after the logout there is a login (token?grant_types=password, right?). So don't think it's that.

@thorwebdev are you just using the OG slack clone example here?

@awalias yes, I'm able to observe this also on the official https://supabase-slack-clone.vercel.app/

could be here: https://github.com/supabase/supabase/blob/1e49eaeb7e0540c9cc1e4dad627e779a33b0500f/examples/slack-clone/pages/_app.js#L43

issue is when a user instantiates two or more supabase clients - fix is to always check localStorage before adding this.accessToken as an auth bearer token to see if there is one on the browser

It's gotrue logout api bug. The cookie is cleared before calling getUserFromClaims .

On slack-clone app, after an Invalid user error fires, I can login and logout successfully!!!
However the next login/logout will trigger Invalid user error again.

Oh we didn't update this issue after meeting @thorwebdev last week about this.
The issue here is that Slack-clone app uses two different supabase client instances, and supabase-js only reads from local storage on initiation, and manages it's own state of which user is logged in after that point - so multiple clients can easily get out of sync on current user state
Our options here are:

supabase-js should check local storage before each call to see if there has been a change in user auth by a different client instance. This may be expensive

we direct people to only init a single supabase client if they're using auth

we make createClient return a singleton

any other?

@awalias what you describe seems to be another issue related to front-end.
The original error reported by @thorwebdev is from gotrue logout api. It can be reproduced easily.

start your test supabase project, run slack clone quick start to create required tables
pull slack clone app, update env with your test project keys
login and logout multiple times, you can see the error

I already check logout api on gotrue.
Before
it works properly, because the claim is retrieved before clearing token
https://github.com/netlify/gotrue/blob/47cc9ce137a24c96985ee3e742b0f0adfb6f146c/api/logout.go

After
https://github.com/netlify/gotrue/blob/8304885327eb93a7346f4b27658f470499c39107/api/logout.go

I think the response from gotrue is actually correct in this instance, if you look at the request headers on the slack clone app, you will see that the apikey and auth bearer headers are the same, in this case the jwt being (mistakenly) sent is the anon key:

for comparison here is an example of a successful logout, with decoded jwt below:

The bug seems to be that the supabase-js client calling logout does not have the current user token, since it was already cleared from the client by the other instance
the "double logout" seems to be coming from here: https://github.com/supabase/supabase/blob/fed822f48c5e441eb867fa756443e362ac47423f/examples/slack-clone/components/Layout.js#L59
and here: https://github.com/supabase/supabase/blob/fed822f48c5e441eb867fa756443e362ac47423f/examples/slack-clone/pages/channels/[id].js#L16

also as a side note - we actually don't make use of the cookies set by go-true, we manage these ourselves using local storage inside supabase-js

Thanks @awalias for clarification. After modify slack clone example to use a single Supabase client, everything works properly.

Currently, supabase-js persists accessToken, refreshToken and currentUser to localstorage while also keeps them as class params inside supabase.auth. When we have multi supabase clients, these params can be out of sync.
We should use localstorage as the source of true and don't keep these as class params. It's the same as how we get authHeader to supply PostgrestClient. What do you think? @kiwicopple

is it inefficient to fetch from local storage every time?
what about server-side / node

maybe keep track of them internally but always check local storage first (if it exists?)

right now everytime you call a request with postgrest client, it will read localstorage for accessToken to include in the header. It works ok until now. So i think it's efficient enough.

for server-side, accessToken should included in the header. To get refreshToken and currentUser we can call gotrue /user endpoint with accessToken


Cache@2 is unable to use cache from main scope.

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Question(bug?)
Enter Task Name: cache@2
list here (V# not needed):
https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/CacheV2
Environment

Server - Azure Pipelines

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:

Account: dev-mc
Project: Minecraft
definitionId=2770
build numbers:
11841620 - Original Main run
11843424 - Run on working/feature branch
11843789 - Rerun on Main

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name:
Pool: Azure Pipelines
Image: internal-macos-11
Agent: Azure Pipelines 23

Issue Description
When running the cache@2 task, runs on working/feature branches are not able to pull from the main scope.
Based on the description here: https://learn.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops#ci-manual-and-scheduled-runs
I would expect that after the original run on main for CI, that a follow-up pipeline is able to pull from the main scope.
I've seen from previous issues that this should be available i.e. https://github.com/microsoft/azure-pipelines-tasks/issues/13666,  https://github.com/microsoft/azure-pipelines-tasks/issues/12503, https://github.com/microsoft/azure-pipelines-tasks/issues/11374.
Most of these use the master terminology for the default/branch head. Our repository, which is a github repository has main as the default/head. Our pipeline definition also has this set as their default branch for runs. Is it possible this is the cause of the inability to grab the cache from the existing scope?
Our use case is for a large amount of relatively short-lived branches that get pr'd and ran on CI in main, and the cache savings are in order of magnitude multiple hours.
Is there anything that we can change to enable the behavior?
Task logs
They should be available for the posted follow-up build id's (not the original main run.)
Original Main Run.txt
Feature Run.txt
ReRun on main.txt, truncated

I think there might be a gap where integration with GitHub is not propagating the default branch and so we default back to master.

I did a few test runs with a temporarily created master branch and it does seem to have the cache fallback behavior.
Publish configuration builds only:
Definition id: 3504
Run id: 11953938
Run id: 11954761
Is there anything we can do on our end to propagate the default branch?
We are using main as our default as part of our efforts to remove harmful terminology within our owned codespaces.
If there is not a way to propagate the intended default branch are there viable solutions within the azure-task/ server side such as:

Adding main as a fallback branch similar to how master behaves, where if not found under master, main is queried? I imagine this will become a more frequent issue as more repositories default to main, especially those hosted by github as it is the new default.

Adding a "read_scope" field to the cache@2 such that the task can be configured to read from any branch scope? I imagine this could wind up tricky to do, but would offer a lot of flexibility for different repository configurations.

I think there might be a gap where integration with GitHub is not propagating the default branch and so we default back to master.

Per D&I, we are supposed to default to main these days, as GitHub itself does when you create a new repository.  Is this going to be fixed anytime soon?  If it would help, we can submit a PR, if you'll tell us where to find the appropriate repo.
Chris BeHanna
<EMAIL_ADDRESS>Minecraft Bedrock Build Engineering Lead

@johnterickson any update on this?

I'm working on a PR for this:

Adding main as a fallback branch similar to how master behaves, where if not found under master, main is queried? I imagine this will become a more frequent issue as more repositories default to main, especially those hosted by github as it is the new default.

This one is trickier:

Adding a "read_scope" field to the cache@2 such that the task can be configured to read from any branch scope? I imagine this could wind up tricky to do, but would offer a lot of flexibility for different repository configurations.

The scopes are provided by the server and the client is untrusted - otherwise a fork PR build could include a change in the YAML giving itself access to things it shouldn't.  Main worry there is write access, so there's a possibility to do something with read access - hmm...


Improve command history tooltip layout

Resolves #415
Makes separate scroll panes for code and result.

For long error messages (DHE), I still want the elapsed time accessible without scroll. I could pin it separately, but that seems unnecessary.

How about just adding something for balance:


Fix all Clippy warnings

To run perf on a criterion benchmark, you have to use the full path to the benchmark binary, e.g.:
/home/dennis/Projects/rust/Graphite/target/release/deps/compile_demo_art-c71307254ef46547 --profile-time 5 --bench
With the profile-time and --bench flags. The help command no longer seems to work in the newer version of criterion


Cannot submit a package

Hi there,
I'm trying to submit my first haxelib, and unfortunately I'm getting this error:
$ haxelib submit fossil-delta.zip
This is your first submission as 'Endel Dreyer'
Please enter the following information for registration
Email<EMAIL_ADDRESS>Fullname : Endel Dreyer
Password :
Confirm :
Error: Invalid user name, please use alphanumeric characters

I've created an account a while back, and I'm not sure if this can be a password issue?
My user name is: https://lib.haxe.org/u/endel
Any help is appreciated. Cheers

My package is super small btw: only 7kb

Looks like you've put "Endel Dreyer" in the haxelib.json "name" field, which should be the username, but not fullname. Try change it to your username "endel".

@andyli oops, that's right! Thanks a lot. It works!


fix(tests): win32 support for paths

Running npm run jest resulted in path errors under win32 systems.  This PR should address those problems found in start.test.ts.  Regression testing was done against Ubuntu to ensure tests still pass on other platforms.
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

Thank you so much for this!


Auto Detect the version of Elastic Runtime and OpsManager Tiles

When running cfops backup and restore to a PCF 1.6 environment it is critical that the operator sets the ER_VERSION=1.6 environment variable otherwise the following error is seen
$ cfops restore -d /staging/pcf-swdctest0224/ --tile elastic-runtime
2016/02/26 09:58:29 E0226 09:58:29.835868 20849 createCliCommand.go:42] there was an error: invalid director credentials running restore on elastic-runtime tile:&{{/staging/pcf-swdctest0224/ false 0xc820428620} /tmp/installation.json366910325 {map[MysqldbInfo:0xc8202375c0 DirectorInfo:0xc820440000 NfsInfo:0xc8204400b0]} [0xc8204400b0 0xc8202375c0] <nil> cf-5221d796caae9224f717 }

This is easy to forget. Can cfops auto detect the target PCF environment eliminating the need to set this ER_VERSION env variable.
I believe this will be a major usability enhancement and improve first time user experience.

latest version supports this feature


Problem entering insert mode after split cursors

Hi,
thank you for creating this plugin. I tried to recreate your example for the "Split" and I cannot get the insert to work.
I have the following
def baz(x, y, z):
    pass

I do visual selection inside the parenthesis, do split on ,, it then generates three cursors as shown in here

Afterwards, I try pressing i or a and it does not work. c works, but it will then remove the letters under the cursor.
is there something that I am doing wrong or something missing in my configuration?

Splitting the visual selection creates multiple visual selections. Try pressing <esc>. Let me know if this does not fix your issue.

Splitting the visual selection creates multiple visual selections. Try pressing <esc>. Let me know if this does not fix your issue.

Thanks for the explanation. That did the trick. I did not realize that it kept me in visual mode after the split.


Update assignment-1

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

Hi, I have uploaded ipynb file in the participation folder. Please use the link: 02_activities/assignments/participation/Assignment-1 code.ipynb


Unmarshal error during login

Hi, I'm trying to run login example but it's falling with:
error during login: error decoding login resp: json: cannot unmarshal array into Go value of type map[string]interface {}
I've changed the code of the library a bit in order to check what's inside the response and looks like the format has changed:
["Cmd",{"type":"update"}]

I got the same issue when trying this

@adzimzf It's working, indeed! Thanks! Looks like the examples still need to be fixed.


Preview html is broken

Hi
It seems the html generated markup is broken in some place:
<div class="dz-error-mark' + this.errorIcon + '

https://github.com/rowanwins/vue-dropzone/blob/vue2/src/index.vue#L116

Cheers, Sebi

Thanks for the report @sebestenyb , this was addressed by @bryanjamesmiller .
I've just published the update to npm as version 2.1.7.
Let me know if you run into any further issues.

It's still a bit weird, I don't have any special css, but the error message covers the remove button.
Actually it's the same on the demo page: https://rowanwins.github.io/vue-dropzone/dist/index.html
And if I use the font-awesome set, the error icon is still:

 error

So it displays the word error instead of the icon.
Thanks!

Have you loaded the material icons?
    <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">

Yes, the icon issue was my cache, that's why I crossed it out :)
But had to do some css overrides for the error tooltip, so it doesn't cover the close button.
I use the font-awesome option.
Thanks, Sebi


Update to androidx.core 1.10.0-rc01

Codecov Report

Merging #840 (2d81576) into main (03b06ae) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #840      +/-   ##
==========================================
+ Coverage   64.85%   64.87%   +0.01%
==========================================
  Files         130      130
  Lines        6380     6380
  Branches     1223     1223
==========================================
+ Hits         4138     4139       +1
  Misses       1425     1425
+ Partials      817      816       -1

see 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fixed a few errors in the translation.

There were a few typos/mistakes in the PT translation.
By the way, is your intention to have different translations for PT-BR and PT? Just wondering if the file should be renamed/duplicated for that case.

Thanks @lucabezerra for the typo fixes :+1:


Iron Web Framework gives some phantom error

I am using iron. Most of time like 99.* % all is good. But sometimes I get error like Error was: ErrorImpl { code: EofWhileParsingString/List/Object, line: 1, column: 8186 } or InvalidUnicodeCodePoint. I am printing request in log and when i try that request every thing goes well. I also have server written in Golang receiving same request and they never have parsing or json to MyStruct conversion problem.
struct RequestBody;
impl typemap::Key for RequestBody {
    type Value = RefCell<Vec<u8>>;
}
    struct ResponseTime;
impl typemap::Key for ResponseTime {
    type Value = u64;
}

impl BeforeMiddleware for ResponseTime {
    fn before(&self, req: &mut Request) -> IronResult<()> {
        req.extensions.insert::<RequestBody>(RefCell::new(Vec::new()));
        req.extensions.insert::<ResponseTime>(precise_time_ns());
        Ok(())
    }
}

impl AfterMiddleware for ResponseTime {
    fn after(&self, req: &mut Request, res: Response) -> IronResult<Response> {
    fn catch(&self, req : &mut Request, err : IronError) -> IronResult<Response> {
        let ref byte_req = *req.extensions.get::<RequestBody>()
                        .unwrap()
                        .borrow();
        //just to make sure uft8 is not causing some issue.
        let payload  = unsafe {
            str::from_utf8_unchecked(&byte_req)
        };
        //but when i send request body all comes good
        error!("Error {} for Body {}", err, payload);
        Err(err)
    }
}

fn iron_handler(req : &mut Request) -> Result<Response, CustomError>{
    let mut buffer = req.extensions.get::<server::RequestBody>()
                        .unwrap()
                        .borrow_mut();
    req.body.read_to_end(&mut buffer)?;
    // not seeing InvalidUnicodeCodePoint after this.
    let payload = String::from_utf8_lossy(&buffer);
    //some request throw error
    let my_struct_obj : MyStruct = serde_json::from_str(&payload)?;
    Ok(Response::with((iron::status::Ok, "Final Response")))
}

Need help to figure out how to identify problem.
Have same problem on stackoverflow : https://stackoverflow.com/questions/45384452/rust-iron-web-framework-gives-some-phantom-error

Used Rocket framework to do same and it is giving same error. Looks like problem is either with serde-json or hyper as both use them.


Running Futures example is invalid

As displayed in the example code:
let handle = system.run(async move {
    "someval".to_string()
});

assert_eq!(block_on(handle), "someval".to_string());

This will not even build because run() returns Result<RemoteHandle...> and block_on() expects a non-Result argument.

If you try to unwrap() and run block_on(handle.unwrap()) then riker will crash with:
thread 'pool-thread-#0' panicked at 'cannot execute LocalPool executor from within another executor: EnterError',
stack backtrace:
thread 'pool-thread-#4' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime'

Any news on this?
I'm having the exact same issue

@knepe the riker project is abandoned. The original maintainer vanished without saying anything. It's probably better to migrate towards a different actor framework.
For the problem itself:
block_on must be called from a tokio context. That means, you need to run your app as a tokio app and run block_on from there.

Ah damn :( Thanks!

@knepe github.com/slawlor/ractor perhaps :)


Report styling

Standard styling for report HTML elements
Adding standard styles for HTML elements in reports: section-title, chart-caption, warning, and notes.
Printing Improvements
Printed reports now include a header on each page, and reports now have a print-only break option so the designer can control where page breaks fall in printing. Other visual tweaks to improve the appearance in Chrome (e.g., for param buttons). For non-Chrome browsers, the header suggests printing in Chrome instead.

Included in #283 . closing


No need to plan or submit workflow if no job added

Otherwise you might get error
Pegasus.client._client.PegasusClientError: Pegasus command: ['/usr/bin/pegasus-plan', '-Dpegasus.metrics.app=XENON', '-Dpegasus.data.configuration=nonsharedfs', '-Ddagman.retry=2', '-Ddagman.maxidle=100000', '-Ddagman.maxjobs=100000', '-Dpegasus.transfer.threads=4', '-Dpegasus.monitord.encoding=json', '-Dpegasus.catalog.workflow.amqp.url=amqp://friend:donatedata@msgs.pegasus.isi.edu:5672/prod/workflows', '--cluster', 'horizontal', '--sites', 'condorpool', '--output-sites', 'local', '--staging-site', 'condorpool=staging-davs', '--dir', '/scratch/xudc/workflows/dx_cevns-discovery_power-202409071328', '--relative-dir', 'runs', '--cleanup', 'none', '-vvv', '/scratch/xudc/workflows/dx_cevns-discovery_power-202409071328/generated/workflow.yml', '--json'] FAILED

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 91.429%

Totals

Change from base Build<PHONE_NUMBER>8:
0.06%

Covered Lines:
1664

Relevant Lines:
1820

💛  - Coveralls


[New game]: PICKR 👾

🎮 Game Request
Game logic and basic description

A multi-gradient color picker game.

Point down the features
Game points
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

/assign

Hey @0xabdulkhalid !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @0xabdulkhalid ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


🚀 [FEAT]: IMPROVE ACCESSIBILITY, BEST PRACTICES OF SITE

Fixes Issue
Closes #191
Changes proposed

Added essential meta elements for markup which improves SEO & Improves accessibility
Then, we added aria-label attribute for social anchors like github & twitter
The aria-label attribute is important for screen readers because it provides a text label for an object, such as a with social icons. When a screen reader encounters the object, the aria-label text is read so that the user will know what it is.
This is important for people who are blind or have low vision, as they rely on screen readers to access the web.
Added title attribute, because the title attribute is intended to provide additional information to screen reader users.
And along with that we added rel for the anchors which are lacking them to ensure best practices for crawlers
Because adding the rel="noopener noreferrer" attribute can help to protect this website from security vulnerabilities and improve performance. It is a good practice to use this attribute on all external links.
Overall this PR is intended to make necessary changes to meet best practices for crawlers along with improving accessibility of site

Screenshots

We can't take screenshots of accessibility changes rather than code changes, Accessibility changes are often invisible to the user because it's intended to guide disabled people

Looks good @0xabdulkhalid , Thank you for your contribution.


⚠ AsianCinema has degraded performance

In 0cc1b0f, AsianCinema ($ACM) experienced degraded performance:

HTTP code: 200
Response time: 2562 ms

Resolved: AsianCinema performance has improved in 9faa985.


remove docker.yml symlinks

This commits removes these two symlinks.
They were there for backward compatibility and were marked deprecated as
of stable-4.0
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test playbook syntax

jenkins test centos-non_container-all_daemons


Ignite 514

Add sorting procedure if client call putAll method with non sorted map. Work with only binary or only objects keys.

IGNITE-514
Closed


Allow selecting Jupyter Server per notebook / Interactive Window

Would be useful for notebooks as well the interactive window to support being able to pick a server per notebook/interactive window session (like we allow picking kernels).
Originally posted by @rchiodo in https://github.com/microsoft/vscode-python/issues/3104#issuecomment-655041391

Yeah it's just a limitation of our current implementation, but something that would be good to support. We'll prioritize in triage. Thanks for filing the issue.


Types.ps1 needs comments

Much of the code is uncommented and it is not immediately apparent what it's function is.
Example:
 [Cluster] NewChildCluster() {
        $indexes = ($this.GetChildren() | % {[Cluster]::new($_)}).Index
        for ($index = 0; $index -in $indexes; $index++) {}
        $cluster = [Cluster]::new("$this-$index")
        $cluster.Create()
        return $cluster
    }

All good now.  thanks.


pull request for e2e test at 12/01/2016 00:26:05

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Publish Microsoft Authored templates to azure samples browser

Update metadata, and publish serverless-chat-langchainjs template to azure samples browser.
@hemarina and @sinedied for notification.

@Menghua1 The sample is already published, and the metadata is available in this file: https://github.com/Azure-Samples/serverless-chat-langchainjs/blob/main/docs/readme.md
We do not want to add metadata to the main readme to keep it more readable.

Here is the published page on sample browser: https://learn.microsoft.com/en-us/samples/azure-samples/serverless-chat-langchainjs/serverless-chat-langchainjs/


Changing damage type with the modular trait's dropdown menu on the Strikes page picks up the Strike (in Firefox)

In Firefox (113.0.1) on Arch Linux, when you change the damage type using the new dropdown menu on the PC's Strikes page, you pick up the HTML element for the strike as well. This doesn't do anything or cause any bugs as far as I could see, it just looks weird.
The same issue does not exist on Chromium 113.0.5672.92.
https://github.com/foundryvtt/pf2e/assets/43446478/fe3bd2e9-7e58-4d64-8bea-a7482d009dff

Does "pick up" mean it triggers the dragstart listener?

Unsure, I could only really test after work.
But I can say it does call the dropActorSheetData hook when you click away afterwards, so it's not just something graphical.

Cannot repro on firefox on windows, but this is amazing.

Fixed by #7936


mrh

Before you create a new issue, please search for similar issues. It's possible somebody has encountered this bug already. PLEASE REMOVE THIS LINE TO ACKNOWLEDGE THAT AN ISSUE DOESN'T ALREADY EXIST FOR THIS BUG
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Android Version: [e.g. API 30]
Device: [e.g. Emulator or One Plus 9]
Browser [e.g. chrome, safari] <- only applicable for app switches or fallback situations
SDK Version [e.g. 0.1.0]

Additional context
Add any other context about the problem here.

Hello,
Please add more details to the bug report so we can investigate.

Hey @MRHVSC - I'm going to close out this issue. Please open a new issue and provide details so we can investigate. Thanks!


Analyzing React.lazy loaded components

Hi,
really awesome project! Thanks!
Any chances there is a way / plan to add a feature to analyze React.lazy() loaded components?
For example:
import React, { Suspense } from 'react';

const OtherComponent = React.lazy(() => import('./OtherComponent'));

function MyComponent() {
  return (

      <Suspense fallback={
Loading...
}>
        <OtherComponent />
      </Suspense>

  );
}

I would like to have 'OtherComponent' code analyzed.

Dynamic imports should already work, but I assume you faced a bug. I'll look into it these days.

Thanks, will check :)


Base quality filtering

Hi, thanks for responding so promptly to these issues! I have the pipeline working, but I was wondering does XICRA have any quality filtering parameters that we can specify to remove low quality bases? Thanks!

Thank you again Jose for your help!


Added applyEncoderCTL & applyDecoderCTL

Created methods ApplyEncoderCTL and ApplyDecoderCTL

@Rantanen plz notice this

Oh damn. This had completely gone past me. Thanks for highlighting.
Sorry @aemino!

🎉


Improving APIM Internal/Patch Issue Dashboard to Meet New Requirements

Problem
Currently Dashboard does not support the Label "Type/Other"
Solution
Change the Scripts, Datasets and Dashboard to support "Type/Other"
Affected Component
APIM
Version
No response
Implementation
No response
Related Issues
No response
Suggested Labels
No response

Got a duplicated version of current Dashboard to do the changes in order to avoid losing data. Then changed the data sources for the Dashboard to a new sheet.

Changed

all-table-monthly
all-table-weekly
live-table-monthly
live-table-weekly

Scripts to ignore "Type/Other" when retrieving Patch and Internal Issue data counts and links

Changed

all-table-monthly
all-table-weekly
live-table-monthly
live-table-weekly

Scripts to retrieve open and closed "Type/Other" Issue data counts and links

Ran "all-table-monthly" script from 2022-11-28 to 2022-02-01 and updated the dataset

Ran "all-table-weekly" script from 2022-11-28 to 2022-02-01 and updated the dataset

Replaced current Dashboard's source data with newly generated data

Created HyperLinks for "Type/Other" Data

Implemented the Dashboard page for "Open & Close Other Issues"

Closing the issue since the task is done


Using a configuration file

When trying to quickly reduce last week's TOO I realized that the potential of the pipeline, that we initially intended, is there, in other words, the functions or methods are capable of doing more than what is currently being requested by the intelligence implemented on the pipeline, (this is in general).
There are several ways to exploit these capabilities.

Add more intelligence to the pipeline which is time consuming and should be left to the end (I agree  with @b1quint on this one)
Add more command line arguments in which case we could end up having potentially hundred of them, which again is not desired
The last option is to use a configuration file. I initially though using a conf.py file but after reading this post I'm more inclined to using json.

Finally, if we successfully evolve the command line pipeline into a GUI version this would work very good because it would let us modify the parameters from the GUI itself. I'm sure there are many possible ways to do this, so I would appreciate some feedback.

I believe that having a .json or a .xml configuration for each run could be very productive and I would like to support that decision.
That would make it easier to implement future GUI(s). In any case, that would require our software to handle these config files and to have default parameters well implemented. I believe that python and other languages have wrappers to deal with JSON/XML files so I believe that it would be a good strategy.

I agree. I would go for the JSON format, since its much simpler than XLM with all of the markup tags, hence easier to use and create/edit with a plain text editor like VI,Emacs, NotePad or whatever flavour one prefers. Its already in use to setup observations for DECam and the Mayall MzLS Survey, which means an increasingly larger community of users is already getting used to JSON files.

I agree. I would go for the JSON format, since its much simpler than XLM with all of the markup tags, hence easier to use and create/edit with a plain text editor like VI,Emacs, NotePad or whatever flavour one prefers. Its already in use to setup observations for DECam and the Mayall MzLS Survey, which means an increasingly larger community of users is already getting used to JSON files.

I'm reopening this issue because we need it for feedback.

For now, let's have it defined the JSON as our future standard for configuration files.
The issue shall remain open until the use of configuration files is implemented.

#129

We have to define a format and just stick with it. When it works, we can try other formats. JSON is easy for users to create/edit.

Again, let's just use JSON.  Unless somebody convinces me of the need for something else I vote for JSON.

I think we've got really far without a configuration file, adding one now would just disrupt the development process too much.


[Enhancement] Set the memory profiling sample interval to 2m bytes instead of time

Why I'm doing:
Set the sampling interval for memory profiling to 2M bytes, which will be more accurate than profiling by time interval.
What I'm doing:
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@mergifyio backport branch-3.1


As a user, I want the main page to present a CTA to sign up/log in

I'll work on this.
Will add root route and call to action. Do we have Bootstrap or anything installed? If not, are we using it or something similar?

I don't think we've talked about the frontend much. We certainly want the site to look good, and I'm not sure we want to spend too much time doing anything from scratch.
So, I think Bootstrap would be fine. Other options: Foundation, Bulma, Material
Anyone have a preference or argument for one over the others?

Personally Bootstrap would be easier as it's the only one I've used before, but I'm happy to use whichever if there are benefits to others that are out there.

Ok so I've finally got my setup working. A few questions for this story:

If I create the root route, I need to give it a controller. Normally I'd create a PagesController and then have the root route go to the index action. Is this approach ok, or is there another way I should do this?
What tests should I create for this? Request, View, Controller, Feature? A mixture?

We are going for a VERY vanilla outline for this first project. The most I would personally be willing to use is a mixin lib like bourbon.io or comparable softwares.

I feel Pages controller is a little generic. Is there maybe a way to name the controller in order to specify that "All routes within the controller are within the "you don't have to log in" section of the site" IE if we added an "about us" piece.
So what can we name it to make it more clear that the entire controller is made to be unauthed


support Windows

This PR makes jam works on Windows.
You should get a dependency before building on Windows, with this command:
go get -v -u github.com/koron/go-waveout

It crashes with the message "failed to create waveout: device ID out of range"
I'm using windows XP x64 in a virtual machine

although, I'm building on linux

I apologize, that's probably because my virtual machine is not configured to work with sound properly

thx!


explain the lts naming scheme

s/simple/actual description/ :)
cc @jasnell & @nodejs/website

LGTM

Picky picky picky...:-) LGTM

LGTM. Merging now that 2 owner and 2 collaborators saw it.

Is there a good document that describes LTS and the difference between v4 and v5?

@mikeal I believe nodejs/LTS#44 is the right place from where such document should appear.
BTW, if anyone interested, for me personally, this article by @rvagg is an example of what this document should describe.

aside: https://www.npmjs.com/package/periodic-table


Implementing a Dry-Run Mode

What feature do you want to see added?
Current Situation
Currently, our tool immediately applies recipes and creates a pull request (PR) without any intermediate steps.
Problem
This approach can lead to several issues:

Inability to review changes before PR creation
Potential for sending unfinished or problematic PRs to plugin maintainers
Risk of creating out-of-date PRs

Proposed Solution: Dry-Run Mode
We should implement a dry-run feature similar to other command-line tools like updatecli. This would involve two main modes:
1. Dry-Run Mode (similar to updatecli's diff)

Run recipes without creating a PR
Display potential code changes
Allow users to review modifications
Provide an opportunity to build and test the plugin locally
Add an option to build the plugin after the changes

2. Apply Mode (similar to updatecli's apply)

Create the PR with the changes

Benefits

Quality Control: Users can review and refine changes before submitting PRs
Respect for Maintainers: Reduces the risk of sending incomplete or problematic PRs
Flexibility: Allows for local testing and validation before PR creation
Alignment with Best Practices: Follows the pattern of established tools in the ecosystem

Example Scenario
Recently, an automated PR was sent to a plugin maintainer that was not up-to-date with the main branch code. A dry-run mode could have prevented this situation by allowing for a pre-submission review.
Conclusion
Implementing a dry-run mode would significantly improve our tool's usability and reliability. It would provide users with more control over the modernization process and help maintain good relationships with plugin maintainers by ensuring higher quality PRs.
Upstream changes
No response
Are you interested in contributing this feature?
No response

Hey @gounthar, we already have --dry-run option (Available CLI options) which generated patch files and no PRs

Reopening because having an output that lists the changes could be helpful.
java -jar plugin-modernizer-cli/target/jenkins-plugin-modernizer-999999-SNAPSHOT.jar --dry-run --plugins badge-plugin,build-timestamp-plugin --recipes AddPluginsBom,AddCodeOwner
Picked up JAVA_TOOL_OPTIONS: -XX:+UseContainerSupport -XX:ActiveProcessorCount=1
Starting Plugin Modernizer
Picked up JAVA_TOOL_OPTIONS: -XX:+UseContainerSupport -XX:ActiveProcessorCount=1
Plugins: [badge-plugin, build-timestamp-plugin]
Recipes: [AddPluginsBom, AddCodeOwner]
GitHub owner: gounthar
Forking and cloning badge-plugin locally
Repository already forked to personal account gounthar
Invoking clean phase for plugin: badge-plugin
Invoking rewrite plugin for plugin: badge-plugin
Skipping commit and pull request creation for badge-plugin
Forking and cloning build-timestamp-plugin locally
Repository already forked to personal account gounthar
Invoking clean phase for plugin: build-timestamp-plugin
Invoking rewrite plugin for plugin: build-timestamp-plugin
Skipping commit and pull request creation for build-timestamp-plugin

I will leave this issue open. Dry run is implemented but can be optimized
For example I don't think we should run rewrite in dry run mode (to create the patch) but always apply changes on the local repo.

The dry-run doesn't fork the repo anymore but clones/fetch from original repo
The dry-run doesn't commit changes anymore (so it means we can easily do a diff on the local repo to debug)
The dry-run compile the plugin after rewrite. Which is useless for now because no changes is never made to the local repo

Conclusion we need never should running the rewrite plugin in dry-mode (or have a separate CLI option different from --dry-run)
@sridamul What do you think about this approach ?

Overall seems like a good idea.

Conclusion we need never should running the rewrite plugin in dry-mode (or have a separate CLI option different from --dry-run)

Maybe we can change the option to something like --rewrite-dry-run instead of removing the existing option.

Closed by https://github.com/jenkinsci/plugin-modernizer-tool/pull/169 feel free to open a new issue for more improvement for dry-run mode


verify_irqbalance

This test case ensures that IRQ rebalancing is taking place.

@kamalca the case passed in canonical 0001-com-ubuntu-server-focal 20_04-lts-gen2 20.04.202307240, is it expected?

canonical 0001-com-ubuntu-server-focal 20_04-lts-gen2 20.04.202307240

@LiliDeng This image had irqbalance package version 1.6.0-3ubuntu1 so it is expected to pass.

@LiliDeng LGTM

@LiliDeng This test case should fail with Ubuntu 22.04 images before 10/4.
I tested Canonical 0001-com-ubuntu-server-jammy 22_04-lts-gen2 22.04.202309190 to confirm.

@LiliDeng This test case should fail with Ubuntu 22.04 images before 10/4.
I tested Canonical 0001-com-ubuntu-server-jammy 22_04-lts-gen2 22.04.202309190 to confirm.

make sure it fail and pass as expected to make sure the case logic is what we expects, thanks!


fixed: docs error, change read:any to read:own

Coverage remained the same at 96.871% when pulling 8989e758b5c37aab97a9211df1cfbbc7dc99c3ca on billgo:master into c91eb6796b4a0e127a99b26f2fceb54d1f3353d4 on onury:master.


Variable undefined issue in pform.f

When compiling the FEAPpv source code for the x86 platform, my student chose the "integer4" folder under the "include" folder, then we got an error saying the variables "ht1", "ht2", and "ht3" are undefined in the subroutine "pform.f". Thus, I think the file "hdata.h" should be defined as follows so that we have those three variables.
integer           nh1,nh2,nh3,ht1,ht2,ht3                     !int 4
common /hdata/    nh1,nh2,nh3,ht1,ht2,ht3

See also https://github.com/keweili/feappv/blob/master/include/integer4/hdata.h
With this change, the 32-bit executable file worked on my machine.

Ooops.  I've fixed the error.  We have debated deleting integer4 altogether but have not yet made a decision.  Would it not be rare for anyone (compiling code) to still be working on a 32-bit only machine?

My student had a 64-bit machine, but somehow she chose to compile the code for the x86 (Win32) platform in Visual Studio (Maybe that is the default option). Then, we found this error. After the change, it worked well, so I would keep the folder.

fyi. i put the bug fix on both the master and the devel branches.

Sanjay Govindjee, PhD, PE
Horace, Dorothy, and Katherine Johnson Professor in Engineering
779 Davis Hall
University of California
Berkeley, CA 94720-1710
Voice:  +1<PHONE_NUMBER>
FAX:    +1<PHONE_NUMBER>
<EMAIL_ADDRESS>http://faculty.ce.berkeley.edu/sanjay
Books:
Engineering Mechanics of Deformable Solids
http://amzn.com/0199651647
Engineering Mechanics 3 (Dynamics) 2nd Edition
http://amzn.com/3642537111
Engineering Mechanics 3, Supplementary Problems: Dynamics
http://www.amzn.com/B00SOXN8JU
NSF NHERI SimCenter
https://simcenter.designsafe-ci.org/
On 6/11/19 11:35 AM, Dr K Li wrote:

Closed #2 https://github.com/sanjayg0/feappv/issues/2.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sanjayg0/feappv/issues/2?email_source=notifications&email_token=ADIUN4Q6D4XIISTEVFYV4RDPZ7V73A5CNFSM4HW7BTZKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOR5NTGYY#event-2405118819,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADIUN4TKI3QBAXCKI635SFDPZ7V73ANCNFSM4HW7BTZA.


[BUG]: [DIFFUSION]: While marked as closed issue #2204 still persists,

🐛 Describe the bug
Issue #2204 while the main issue was solved the other that cropped up and was marked closed by pull request #2356 seemed to be a solution that was implemented onto the Dreambooth area, and not the main diffusion one, is this get static torch model a solution that we should be manually implementing into the Diffusion one and it will fix it or was the fix simply for the same type of problem but affecting dreambooth, as still finetuning diffusion does not produce discernable results and only makes random noise.
Environment
No response

We have updated a lot. Please check the latest code. This issue was closed due to inactivity.
If you have further questions, please open another new issue and provide details. Because everyone's issue details may be different. Thanks.


Multiple environments (RouDis)

Hi what's the recommended path of running two separate iceoryx environments on the same box if possible ?
I rather not send under separate topics and share RouDi. I see that Roudi can start with an unique Id but the PoshRuntime can't register per runtime Id...   -I suspect I'm missing something.
Please advice.
Thanks!

As @elfenpiff wrote, we currently do not support this. The unique ID for RouDi is a first step and supporting this is definitely on the wish list for a 2.1 or 3.0 release. What exactly is your use case @niclar?

@burus I want to run two separate systems / stacks (production-staging, production) on the same machine (different prio etc.). Until this feature is in place I'll just publish under different topics (instanceIds) and share RouDi.

@niclar would it be an option to run the production-staging RouDi in a docker environment?

We don't run docker and that would introduce discrepancies wrt networking, latencies etc.


Repo and Artifact labels not present

For the request metrics (jfrog_rt_data_download_total, jfrog_rt_data_upload_total and jfrog_rt_req_total) the repo and artifact labels are always empty.
I am trying to use this with the artifactory-ha chart version 107.27.9.
Looking at the fluentd.conf.rt it seems to expect the repo related calls to have a request uri that beings with /api/download . However this does not appear to be how downloads look in the request log. Here is an example one from my logs:
2021-12-04T00:13:57.470Z|12a8601c7feea529|<IP_ADDRESS>|anonymous|GET|/api/npm/npm-remote/bower/-/bower-1.8.13.tgz|200|-1|4376294|78|npm/3.10.10 node/v6.17.1 linux x64

Any updates on this JFrog? Same issue.

Affected by this as well.
More things to point out:
nuget/chocolatey repos have a lot of artifact="Package()" or artifact="Search()" artifact="$metadata" or even artifact=""
Ruby repos have "artifact=dependencies"
Etc.
We're using artifactory 7.33.12 and the config file provided in the repository. Is the state of that file expected to be this bad?

Samr issue here, any updatey? :persevere:

Same issue here, any updates?


remove recursive call

remove recursive call, not sure about performance improvement but at least it is cleaner code.

test this please

test this please

I ran some performance test with this patch and without this patch. As expected, it is almost identical. (check how many same queries done within 1 seconds) But code is cleaner with this.

Sorry Alan, I missed your comments. Actually, this has conflict with my other patch. I will update that patch and fix the pylint as well.


feat: link instance group with organization

Add the possibility to attach or detach an instance group from an organization
FYI @vaxvms
rework of #58

Code tested :
resource "awx_organization" "orga" {
  name = "default"
}

resource "awx_instance_group" "default" {
  name               = "default"
  is_container_group = true
  pod_spec_override  = <<EOF
apiVersion: v1
kind: Pod
metadata:
  namespace: awx
spec:
  serviceAccountName: awx
  automountServiceAccountToken: true
  containers:
    - image: quay.io/ansible/awx-ee:latest
      name: worker
      args:
        - ansible-runner
        - worker
        - '--private-data-dir=/runner'
      resources:
        requests:
          cpu: 250m
          memory: 100Mi
EOF
}

# attach orga to new instance_group
resource "awx_organization_instance_group" "attached" {
  organization_id   = awx_organization.orga.id
  instance_group_id = awx_instance_group.default.id
}


Remove pluggable agent tests from build

Part of Epic TestCentric/testcentric-gui#971
By including tests of pluggable agents in the engine build, we create what amounts to a cyclical dependency.

The agents all depend upon a particular engine build and include references to assemblies from that build.
At the same time, the engine's tests need a particular engine build in order to run

By testing pluggable engines only in their own project builds and doing so thoroughly, we break that cycle and can proceed to make improvements in one project at a time.

:tada: This issue has been resolved in version 2.0.0-alpha8 :tada:
The release is available on:

GitHub Release
NuGet Package


Bug with PDFs and Acrobat Reader

So this is more of a heads up / tip: for those of you having issues with merged letters in PDFs when opening in Adobe Acrobat Reader, I was able to fix it by adding a zero-width non-breaking space character (0xFEFF) between every single letter of the page. This produced the exact same rendering when viewing a PDF in Chrome and viewing it in Adobe Acrobat.

Note: this "bug" only happens in Adobe Acrobat for any webfonts used in a page.

Does the same thing happen if you print to pdf from Chrome?

@JoelEinbinder yep!

Thanks for the heads up. I'll close this as not a Puppeteer specific issue, but feel free to discuss workarounds here. If it's a Chromium bug, you can file an issue on crbug.com. If it's a problem with Adobe Acrobat I don't know where you file that.


New version: Google.Chrome.Beta version 120.0.6099.5

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

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

Microsoft Reviewers: Open in CodeFlow

It seem failed to track the object because winget list -m did not work.