The scope of DBContext of Identity

We are using identity beta-8 for a project. When use AddClaimAsync in RoleManager, it gives error  "[Some Class]" cannot be tracked because another instance of this type with the same key is already being tracked.
The dbcontext was injected in Startup.cs
services.AddEntityFramework()
                .AddSqlServer()
                .AddDbContext<HemaIdentityContext>(options =>
                {
                    options.UseSqlServer(Configuration["Data:DefaultConnection:ConnectionString"]);
                }
            );

            services.AddSingleton(_ => Configuration);

            services.AddIdentity<HemaUser, HemaRole>()
                .AddEntityFrameworkStores<HemaIdentityContext, Guid>()
                .AddDefaultTokenProviders();

Nothing is special here. I wonder any Jedi master here can show me some force to light the road for me.
I know by default the IdentityDbContext was injected as scope and some source code use attach method to attach entity to be tracked without check whether the entity already inside context. This is where the error comes from.
I don't know why EF decide not handle duplicate check inside attach method.

I found a closed ticket #536 which changed to scope from transient, which is good. However, it may brings issue when we use attach method in our code without check whether entity is already in the context

Can you please send us the snippet of code for this "When use AddClaimAsync in RoleManager"?

It is very easy to replicate. Any time, the second call to userManager, roleManage related to a same entity will fail. For example, the ResetAccessFailedCountAsync is OK, but SetLockoutEndDateAsync will fail, because user is already in tracker.
var result = await userManager.ResetAccessFailedCountAsync(user);
                if (result.Succeeded)
                {
                    await userManager.SetLockoutEndDateAsync(user, null);
                }

@HaoK maybe we have a bug. Can you please look into it?

I didn't observe the issue again after upgrade to RC1. I believe this may be an issue of EF instead of Identity. I will keep an eye on it.


"true custom firmware"

This was already possible with A9LH. This kinda implies only B9S is capable of doing this.

That line is extremely old and has been around for at least a year.


Fixed a small error in German localization

[ ] Have you signed the Contributor License Agreement?
[ ] Are you working against an Issue?

There is a small mistake in German localization.
Microsoft Reviewers: Open in CodeFlow

Thanks, submitted 33657797 internally to apply the fix.

Should be fixed by #1462, closing this tracking PR.


[#156926972] upgraded npm deps

Warnings

:warning:

Please include a description of your PR changes.

Affected stories

⚙ #156926972: Aggiornare le dipendenze del repository digital-citizenship

  Generated by :no_entry_sign: dangerJS


buildStackProject can not be used an an imported nix buildInput

Describe the bug
When a shell (say outer.nix) uses another nix expression that is imported as a buildInput, and that other nix expression uses buildStackProject instead of mkDerivation, the build fails due to network activity in the build phase. It looks like this:
$ nix-shell
these derivations will be built:
  /nix/store/n448wi8w0rj5x6f907frwryvismj4930-impureMatlabEnv.drv
building '/nix/store/n448wi8w0rj5x6f907frwryvismj4930-impureMatlabEnv.drv'...
patching sources
configuring
no configure script, doing nothing
building
Writing implicit global project config file to: /build/.stack/global-project/stack.yaml
Note: You can change the snapshot via the resolver field there.
HttpExceptionRequest Request {
  host                 = "s3.amazonaws.com"
  port                 = 443
  secure               = True
  requestHeaders       = [("Accept","application/json"),("User-Agent","The Haskell Stack")]
  path                 = "/haddock.stackage.org/snapshots.json"
  queryString          = ""
  method               = "GET"
  proxy                = Nothing
  rawBody              = False
  redirectCount        = 10
  responseTimeout      = ResponseTimeoutDefault
  requestVersion       = HTTP/1.1
}
 (ConnectionFailure Network.Socket.getAddrInfo (called with preferred socket type/protocol: AddrInfo {addrFlags = [AI_ADDRCONFIG], addrFamily = AF_UNSPEC, addrSocketType = Stream, addrProtocol = 0, addrAddress = <assumed to be undefined>, addrCanonName = <assumed to be undefined>}, host name: Just "s3.amazonaws.com", service name: Just "443"): does not exist (Name or service not known))
builder for '/nix/store/n448wi8w0rj5x6f907frwryvismj4930-impureMatlabEnv.drv' failed with exit code 1
error: build of '/nix/store/n448wi8w0rj5x6f907frwryvismj4930-impureMatlabEnv.drv' failed

To Reproduce

create inner.nix using buildStackProject
create outer.nix using inner.nix as an imported buildInput
nix-shell outer.nix

Expected behavior
I would expect the shell to execute since calling nix-shell inner.nix is not an issue.
Additional context
An example of inner.nix.
Rough sketch of an outer.nix:
with import <nixpkgs> {};
let
  gurobiPlatform = "linux64";
  myGurobi = (import nix/packages/gurobi/default.nix);
  myMatlab = (import nix/shells/MATLAB/default.nix);  # here is the `inner.nix`
  cobraToolboxLocal = stdenv.mkDerivation {
    name = "cobraToolbox-local";
    src = fetchgit {
      url = "https://github.com/opencobra/cobratoolbox.git";
      rev = "92518352da3dc1f63b7ef781345786f5cf73034c";
      sha256 = "0dsz2046vjxv89imifacv15jkv6avg8xrssig6n7kxsv98i1rm29";
    };
    buildInputs =  [ ];
    builder = builtins.toFile "builder.sh" ''
      source $stdenv/setup
      mkdir -p $out
      cp -R $src/* $out/
    '';
  };
in
haskell.lib.buildStackProject {
  name = "cobraMatlabHaskellEnv";
  dontUnpack = true;
  buildInputs = [
    makeWrapper
    myMatlab
    zlib
  ];

  src = null;
  shellHook = ''
    # Copied or modified from MATLAB's default.nix:
    export MATLAB_PATH=${myMatlab.matlabPath}
    export PATH=$PATH:$MATLAB_PATH/bin
    source ${./nix/shells/MATLAB/patchMATLAB.sh}
  '';

Metadata

system: "x86_64-linux"
host os: Linux 4.19.113, NixOS, 19.09.2350.d011e474945 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.3
channels(nixos): ""
channels(root): "nixos-19.09.2350.d011e474945"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

@bbarker Sorry you're having trouble with this.
buildStackProject is not expected to work to actually build derivations (unless you disable sandboxing).  It is really only to support stack's native nix-support.
What you have to do is add all the required packages to your stack.yaml (in the extra-deps section?).  The top-level buildStackProject should be passed buildInputs that are necessary for the given package, and all dependencies.  This is quite unlike a normal packaging style in nixpkgs.
If you have trouble getting this working, please feel free to post a simple, reproducible example for me (or someone else) to take a look at.
I'd suggest looking at stack's nix documentation, as well as https://github.com/cdepillabout/post-about-nix-and-haskell/blob/master/2019-08-03-q-and-as-about-nix-for-haskellers.md.
I'm going to close this, since buildStackProject is not supposed to be used this way, but please feel free to re-open if I've misunderstood what you're asking.


Docker entrypoint prevents to run as a task

Hi!
I think would be useful to allow to run this program as a task.
At this moment docker-entrypoint.sh prevents to run this program as single task or in a cronjob, since the entrypoint has no way to terminate in a controlled way.

Hey @RobertoBochet :wave:

I think would be useful to allow to run this program as a task.

That was not intended use-case yet, but I completely agree!

At this moment docker-entrypoint.sh prevents to run this program as single task or in a cronjob, since the entrypoint has no way to terminate in a controlled way.

I will have a look at your PR right away!

Thanks again, merged and released @RobertoBochet :pray:


[Phase 4] New Runes: Hunter

#829

List of P4 hunter changes:
Runes
New runes:
- Resourcefulness = Trap mana cost -100% cd from 15 to 9s
- Cobra Slayer = 5% chance per auto for MB proc, +5% for each auto. 100% on dodge. +40% AP on MB
- Kill Shot = 100% weap dam + 138.435. 15s cd. Insta reset on 20% or lower
- Wyvern Strike = 100% weap damage, 8s cd, Bleed for (3 / 100 * 8 * Attack power) over 8s
Deleted runes:
	- Heart = baseline +200 mAP, Kill command, Invigoration

Old rune changes:
	- TNT = Explo initial increase 50% of mAP. Immo dot increase 50% of mAP
	- Catlike Reflexes = Kill command gone
	- Rapid Killing = Also 40% Melee AS (CD -80%)
	- Check Melee Specialist
	- Check Steady Shot (100%)
	- Check DW Spec
	- Check Chimera
	- Check Explosive
	- Flanking strike = 5% all damage increase 10s, 3 stack max, pet auto 33% reset chance
	- Carve = 65% + 50% on primary (so 97,5 total)
	- Check Beast Mastery
	- Lone Wolf = 40%
	- Cobra Strike = now also from all Strikes and Mongoose Bite

Talents
MM:
- Efficiency = Also for Raptor, Flanking, Wyvern
- Lethal Shots = also for all melee, possibly all crit though
- Mortal Shots = also for MB, Raptor, Wing clip, Flanking, Wyvern
- Trueshot = only rAP (200 rAP)
Gear
- Tier 0, 0.5, 1 sets
Other Notes:
- Faster OH will be better for Dual wield cause of Mongoose procs (no daggers cause of normalization)

Created a new PR for some of the easier changes #834

Have a new PR to address the minor rune changes, Rapid Fire and Cobra Strikes as well as update efficiency, lethal shots, and mortal shots talents. #839

V - Flanking strike = 5% all damage increase 10s, 3 stack max, pet auto 33% reset chance
Does not reset off of pet autos - it resets off claw/bite similar to Focus Fire

Created a PR to add Wyvern Strike, pretty sure the implementation is correct but wouldn't mind getting a second set of eyes on it.
link: #841

Unless I am mistaken only Kill Shot and baseline mAP of heart of the lion are left open.

Unless I am mistaken only Kill Shot and baseline mAP of heart of the lion are left open.

I think the heart of the lion ap buff is already live: https://github.com/wowsims/sod/blob/51fcbd868e76e793316e216339ba65a08ebf22fc/sim/core/buffs.go#L850
Gonna start on kill shot today

Apparently in the sim explo overwrites the immo dot. Immo dot should run its full duration while explo dot is active in the background. When Immo ends the explo dot gets active for its remaining time. Immo always takes priority.

Apparently in the sim explo overwrites the immo dot. Immo dot should run its full duration while explo dot is active in the background. When Immo ends the explo dot gets active for its remaining time. Immo always takes priority.

Hmmm I guess I misunderstood the log I was looking at, It looked to me like it was just overwritten. So the correct interaction would be:
You cast Immolation Trap and 10s later Explosive trap, then immo does damage for its full duration, explosive trap causes initial damage and applies its DoT (but DoT doesn’t do damage). Immo trap wears off at 15s and explosive trap DoT has 15s left of duration so it starts doing its DoT damage?

Apparently in the sim explo overwrites the immo dot. Immo dot should run its full duration while explo dot is active in the background. When Immo ends the explo dot gets active for its remaining time. Immo always takes priority.

Hmmm I guess I misunderstood the log I was looking at, It looked to me like it was just overwritten. So the correct interaction would be: You cast Immolation Trap and 10s later Explosive trap, then immo does damage for its full duration, explosive trap causes initial damage and applies its DoT (but DoT doesn’t do damage). Immo trap wears off at 15s and explosive trap DoT has 15s left of duration so it starts doing its DoT damage?
more simply immo trap and explosive trap DoTs can exists at the same time however explosive trap DoT can only do damage if there is no immo DoT

You're on the dot

It looks like with the latest addition of Kill Shot, the Cobra Slayer rune has disappeared from sim

It looks like with the latest addition of Kill Shot, the Cobra Slayer rune has disappeared from sim

Looks like it was a casualty of #856

Another bug found- it doesn't look like the Trap Mastery talent (https://www.wowhead.com/classic/spell=19377/trap-mastery) is implemented in the current sim. Testing different variations of the sim with VS without the talent doesn't lead to any differences in the miss rate of either immolation or explosive trap.

The to do list has now been completed. I'm working on APL's now but already noticed some bugs/issues. Ill make a checklist for those here.
Issues
		- Raptor Strike queue time seems to be affected by both Ranged and Melee swings. Should only be melee. (speculation)
		- Movement seems to be a little bit too slow. This makes it hard to make a weaving rotation
		- Even though minimum ranged range is 8 yd, the sim only allows proper spell cast at 9 yd

Nevermind. I think in the end you can ignore it.
Got an APL thats based on p1 weaving from someone and it works with some auto attack markers which for some reason completely fix the issue. Odd, but it all works now

https://github.com/wowsims/sod/pull/862 Trap mastery fix
https://github.com/wowsims/sod/pull/864 Cobra slayer fix

One more thing that has to happen is either a toggle in settings to turn bite off, or add a condition to the Focus Fire and Cobra Slayer runes where it disabled pet specialability when you have the rune activated.
I tried to look into it but couldn't figure it out.

New issue discovered: Sniper Training currently doesnt properly lose or gain stacks in the sim on movement.

To do:
- Fix Lion AP
- Readjust OH Raptor/Carve
- Fix ammo damage
- Add Bite toggle


way to get timestamps?

Is there anyway you could also add getting timestamps or durations from the video?

@Donald646 Here
`type Response = {
text: string | undefined;
start: number;
end: number;
};
const fetchTranscript = async (
videoId: string,
lang: string
): Promise<(Response | undefined)[] | undefined> => {
const youtube = await Innertube.create({
lang: lang,
location: "US",
retrieve_player: false,
});
try {
const info = await youtube.getInfo(videoId);
const transcriptData = await info.getTranscript();
return transcriptData?.transcript?.content?.body?.initial_segments.map(
(segment) => ({
text: segment.snippet.text,
start: Number(segment.start_ms),
end: Number(segment.end_ms),
})
);
} catch (error) {
console.error("Error fetching transcript:", error);
throw error;
}
};`

Is there anyway you could also add getting timestamps or durations from the video?

hi yea I'll look into this, thanks for suggestion


Update lru, regex and thread_local

polkadot companion: https://github.com/paritytech/polkadot/pull/5217

bot merge


spontaneous field is quoted if it is a 1, not quoted if zero

Description of the issue:
It is just annoying when you read it in, you have to do some formatting, convert to number etc.
Expected feature/value/output:
Current feature/value/output:
Reproducing these results:
I hereby confirm that I have:

[ ] Tested my code on my own computer for running the model
[ ] Done this analysis in the master branch of the repository
[ ] Checked that a similar issue does not exist already

Note: replace [ ] with [X] to check the box. PLEASE DELETE THIS LINE

just to be clear, no quotes would be preferrable

@johan-gson the spontaneous  info was introduced by #162 as a numeric field

you will get the field as double type, if using the importTsvFile function provided by Human-GEM.

@johan-gson is right, the file currently has quotes around 1s. Someone must have accidentally modified this at some point.
It should be easily fixable by importing/re-exporting using the importTsvFile and exportTsvFile functions, respectively.

So, I can use the proper import function, I just think it is weird, and it messes things up a bit if you want to load it in R or something.

Yes, it's not supposed to be like that, and should be fixed such that they're all numeric.

Ah, that's weird.
Some considerations:

Add introduction of tsv structure and manipulation to README
Add tests to tsv structure in sanityCheck

With a bit of git bisect, it looks like the extra quoates slipped through in commit 98eb520aac6137aa013265f37f29fb490c669226 . @Hao-Chalmers good idea to also test the tsv files.

resolved in #263


dashboard enhancements

Is there a good place to discuss dashboards around?  Perhaps Wiki or Discussions?
I've taken the data provided here and made a dashboard that I found more useful for my own needs.  I wanted to share it with others in case anyone is interested.

Interactive example:  https://snapshot.raintank.io/dashboard/snapshot/8FO8GbRlK4G6hGKtASVQlJ9NnmyDaIVo
Dashboard for import:
Starlink Statistics.json.zip

I can open up either Wiki or Discussions if you want. Honestly, most interactive discussion to date has been in issue reports, which is probably not ideal. Wiki is probably not great for discussion, either, but might be a good place to showcase what's available, like the screenshot you just posted. I guess Discussion would make more sense for... well... discussion, but I've never actually seen a GitHub project use it. I'm willing to give it a go if people are interested, though. You're not the first person to ask.

I've only seen Discussions in use in the tesla API thing where there's actually a lot of people trying to work on building APIs for interacting with tesla backends and bug discussions get out of control in such a way that makes the bug status less helpful.
Wiki might be OK.  I don't want to leave junk in bugs that can't be closed or project forks or whatever just to have peripheral contribution.  This is along the lines of "look at stuff that can be done with this project" and not so much the project itself.  The project enables so much great stuff.

OK, I have opened up the Wiki section of this project so that anyone with a GitHub login should be able to add or edit pages. At some point, I'll try to at least add an overview page that doesn't just duplicate the README, but feel free to add pages in the mean time.

I made https://github.com/sparky8512/starlink-grpc-tools/wiki/Dashboards where I could drop the dashboard I'm using and hopefully bait other people to do interesting things.


Trying to understand how methods executing in different threads are aggregated during Sampling

Hi, I am trying to understand how does methods executing in different threads are aggregated by Async profiler to generate the final results.
For some of the applications, we can at times have 100's of threads which could be executing at the same time and when the profiler takes a sample,I assume the method invocation stack snapshot is taken for all these threads. If this is the what is taking place, how are the method invocation snapshots merged to generate the visualisation? or does this process look different?

@apangin Thanks a lot for the clarification. Just trying to improve my clarity on the use case when per thread mode option is not provided.
Let's say we have a program which contains a method "methodA" and there are 4 threads which are executing concurrently. All of these 4 threads are executing "methodA" only.
Now, if we sample for 100 seconds at a 1 second interval, will this translate to "methodA" being counted as 100 samples or 400 samples?

400 samples (assuming that methodA is 100% cpu-bound, and there are at least 4 cpu cores).

Thanks a lot @apangin
That provides clarity to what I have been thinking.
Closing this issue :)


[Bug] Decouple cluster and namespace navigation

Hello,
Right now each time you want to choose another namespace, you need to choose once again the cluster.
Can we decouple the processes so we can choose namespace freely without going through the cluster choice.

Forgot to update this, but this has been possibly through the Command Palette for quite some time now ;)


Update ESP-NTP-MQTT V0.4

Update string handling, fix memory leak causing reboots.

There are branch conflicts here (the file was renamed by me to take out version information on the file name).
I will manually commit changes now.
Thank you for the changes!!

No problem :)
You might want to take note 1 out of the readme.md , since it now polls the NTP server more reasonably.
Cheers,
Matt
From: Johnny Moore @.>
Sent: 05 October 2021 10:48
To: JXGA/ESP8266-NTP-Clock @.>
Cc: Matthew Kent @.>; Author @.>
Subject: Re: [JXGA/ESP8266-NTP-Clock] Update ESP-NTP-MQTT V0.4 (#6)
There are branch conflicts here (the file was renamed by me to take out version information on the file name).
I will manually commit changes now.
Thank you for the changes!!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/JXGA/ESP8266-NTP-Clock/pull/6#issuecomment-934247881, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC3AC27T5YMFEKF63ZHJZN3UFLCWPANCNFSM5FLIEA6Q.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Refactor: Reduce disk size of git history

At time of writing, cloning the repo involved downloading ~165MB of data, which is large for a git repository. In addition, by far the largest culprit is the .git/ directory, which would imply that there is a lot of relatively large files which were committed in the past but are no longer part of the project. Give the high number of data files stored in this repository, I suspect them to be the main source of this bloat.
I don't suggest we do anything about this yet, but once the repository starts approaching a state in which it looks most like the finished thing, we can look at refactoring the git history to remove this bloat.
For posterity, here are some links to potential solutions:

https://www.perforce.com/blog/vcs/git-beyond-basics-using-shallow-clones
https://stackoverflow.com/questions/45864180/how-can-i-reduce-the-size-of-git-folder-with-huge-history-of-commits#comment78697675_45864411

I've found a few tools and strategies to clean the history:

Do an --orphan checkout and push to a new main branch after removing the old one. Apparently this option doesn't preserve any history.
Wonder if a shallow clone and then a new main branch would have a similar effect but with the option to preserve up to a few commits.
BFG looks like a tool that does exactly what we are looking for. But I have no idea what the side effects in terms of commit history are.
git filter-branch which I think is the native tool which operates similarly to BFG.

I'm not particularly worried about losing the commit history. Specially now at such an early stage.
The takeaway message, I imagine, is that any new large data commit has to be done through a PR with a disposable branch and possibly squashing commits to simplify the git history.

Ok, I was able to reduce the size to about 100MB using BFG to remove old revisions of large files in the git history.
This leaves every last commit of a file untouched.
If in addition we remove some unnecessary data from the repo to close #21 (there is a population .csv which is ~20MB and we don't really need it) then we should be good.

Great options for de-bloating the commit history - I wasn't aware of BFG or git filter-branch! As you have tested, best to try this on a fork of the repo and make absolutely sure there are no undesirable side-effects.
Regarding JOSS, what are there requirements regarding a git history? Might be worth checking before we push any lighter history to the main branch


govendor get github.com/gohugoio/hugo is erroring out

I even remove all directories, try to fresh install.  No luck.
Is there any other way to install the dependencies?  I would do so one-by-one, if necessary.
Windows 10 Pro - Avoiding choco.
$ govendor get github.com/gohugoio/hugo
# cd .; git clone https://github.com/gohugoio/hugo C:\Users\Steven\Development\Go
\src\github.com\gohugoio\hugo
fatal: could not create leading directories of 'C:\Users\Steven\Development\Go
\src\github.com\gohugoio\hugo': Invalid argument
Error: failed to create repo "https://github.com/gohugoio/hugo" in "C:\\Users\\Steven\\Development\\Go\n\\src\\github.com\\gohugoio\\hugo" exit status 128

Please use https://discourse.gohugo.io/ for questions/troubleshooting. Also see  Hugo Documentation.


Example wrap file ?

An example of "how to use this" in the README would be useful for newcomers...

I had the same issue and think it would be good to add a hint to every readme (at first I thought these repos were all empty because they use branches for the versions :D)
so this should be helpful https://mesonbuild.com/Using-the-WrapDB.html

That's a good point, thank you. I will update https://github.com/mesonbuild/mesonwrap/blob/master/mesonwrap/tools/repoinit.py#L32-L35


Spacing on the Account Overview tab is way off after Graph integration

Describe the bug (required)
The spacing between the recent transactions is enormous on the Overview tab of the account pages in the explorer in the graph integrated version.
Expected behavior (required)
The recent txns should not have nearly this much space between them.
To Reproduce (required)
Steps to reproduce the behavior:

Go to http://explorer-staging.livepeer.org.s3-website-us-east-1.amazonaws.com/accounts/0x50d69f8253685999b4c74a67ccb3d240e2a56ed6/overview
View the space between the recent txns

Device (required):

Macbook Pro, OS X, Brave Browser

Screenshots (optional)
https://cl.ly/12896b6bd8a7

Hmmm, I wonder about this. Seems we're using an outdated version of rmwc which this feature depends. I wonder if that is causing this bug, because I now realise that the options menu in the Navbar which also depends on rmwc is not opening either.

@dob  @Randy1Burrell I've confirmed this is due to a breaking change in the rmwc package. Let's freeze that dependency version at 1.6.2.


TrackScheme - Paint vertices and edges according to feature value.

TrackScheme can be painted according to feature values.

Superseded by the screen-entitites-color branch, that branched from this one and fixed a crash.


Validate on form submit instead of input focus out

Hello, I have used AvField for login validation.
There are some checks that it is ok for validation to be triggered on input focus out, but I would like to get the validation result on form submit and also to add an extra custom check from backend.
Is there any way to do this?

Is there any way to validade the form from a function?

Is there any way to validade the form from a function?

Is there any for this this in existing library for this behaviour


Do not set "selected" from the database.

{{#autoForm collection="Parents" id="autoFormParent" type="update" doc=doc}}
    {{> afQuickField name='elements' select2Options=select2Options}}
{{/autoForm}}

ParentsSchema = new SimpleSchema({
    elements: {
        type: [String],
        defaultValue: [],
        autoform: {
            type: "select2",
            afFieldInput: {
                multiple: true
            }
        }
    }
});

Template.autoFormParent.helpers({
    select2Options: function() {
        return {
            data: lodash.map(Elements.find().fetch(), function(element) {
                return { id: element._id, text: element.name, selected: true };
            })
        };
    }
});

The list of options is displayed. Already set the tags are not displayed.
The database changes are saved.
Where is my mistake? Or is it a bug?

same here - how to fix it?
I noticed that the original select-ultiple dosent work too with autoform 5.7.1

label: "Majors",
type: [String],
optional: true,
allowedValues: ['Physics', 'Math', 'Biology', 'Chemistry'],
autoform: {
  type: 'select-multiple',

afFieldInput: {
multiple: true
}
}
}

If anyone still has this problem, updating to the 4.0.3 release of select2 fixed this problem for me.

Updating to 4.0.3 doesn't solve the problem.
Setting type="select" and calling elt.select2(options) in the onRender() handler does work.


[Bug]: Only One FAQ Item Should Remain Open at a Time

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When opening a new FAQ, the previously opened FAQ item does not close automatically. This causes multiple FAQ items to stay open simultaneously, which affects the user experience and can lead to a cluttered view. I want to Implement functionality to automatically close the previously opened FAQ item whenever a new one is opened.
Add ScreenShots

please assign this to me under hacktoberfest and gssoc-ext @visheshrwl
What browsers are you seeing the problem on?
No response
Record

[X] I agree to follow this project's Code of Conduct
[ ] I'm a WOB contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

Hi @sezallagwal , I have assigned this task to you. Kindly complete within 2 days. Also add a 30 sec demo video. Good luck!

ok will do

Hi @sezallagwal , I have assigned this task to you. Kindly complete within 2 days. Also add a 30 sec demo video. Good luck!

Already done

Hey @sezallagwal ! 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! 😇

Gentle Reminder 🚨🚨
GSSoC-Ext 24 is going to complete in 2 Days. '
Complete your assigned Issues and PR reviews before time to get Points on Leaderboard. '
It was a great experience working with you all, Don't forget to ⭐ star the Repo (only 12 with 62 forks 💔) .
Thanks💗 for your valuable contributions!

Gentle Reminder 🚨🚨
PA and Mentor nominations have been started for GSSoC-Ext 2k24. '
Do share your experiences and connect on Socials. '
It was a great experience working with you all
Thanks💗 for your valuable contributions!


Move all cookie storage to local storage

This is a change I'm considering and would like some input on. It moves all storage to local storage when available and namespaces the storage with the api key.
It's better to not send the cookie data across the wire since the server isn't consuming it. The user properties can get large and I've run into cases where the server complains about cookie size when properties gather up over time.
If we have more than one chrome browser extension for the same domain (e.g., gmail) running on the same client, the storage data will collide and cause havoc. I'd rather not have an untraceable bug in the future from this.
It does rely heavily on local storage being available. That's a fairly safe assumption, but there are clients that don't have it. The code falls back to cookies (and limits the amount of data stored). In that case, it's at least as good as what we had before, but still not awesome.
It does require a data upgrade method that will need to stay in the library for a long time and could have issues in edge cases (though it's fairly simple and well tested).
Anyway, let me know what you think about the direction this takes.

Closed due to merging of https://github.com/amplitude/Amplitude-Javascript/pull/33


⚠ Bofrost.lu has degraded performance

In f641f81, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1434 ms

Resolved: Bofrost.lu performance has improved in 169edf6.


Friend mutes

Currently players can still used friend messaging when muted in servers.
Tasks

[ ] Add option to mute a player.

Will be implemented with version 3.6.0


"Upload New Form Definition" dialog with the Dataset and a property changed in a form.

Problem description
When a dataset and a property is changed in a form, the "Upload New Form Definition” dialog shows information about the changed property which might be misleading (no information about the changed dataset). Other properties weren’t changed but belong to the new Dataset so all of the properties are new for the Dataset.
URL of the page
https://staging.getodk.cloud/#/projects/20/forms/basic_entity
Steps to reproduce the problem

Upload and publish a form creating a Dataset (entity with properties). e.g.basic entity form version<PHONE_NUMBER>37898 in https://staging.getodk.cloud/#/projects/20/forms/basic_entity/versions
In the form add/remove a property and change the name of the Dataset (e.g. basic entity form version<PHONE_NUMBER>3 in https://staging.getodk.cloud/#/projects/20/forms/basic_entity/versions)
Upload the new version of a form and check the "Upload New Form Definition” dialog.
Click "Upload anyway”.
Check if the Dataset and properties are new in the draft section.
Publish the draft and check the dialog.

Screenshot
I checked it on staging and cloud server and there is a difference in the draft section.
Staging:

Cloud (in the draft section properties aren't new- without +, not mentioned in publish draft dialog):

Expected behavior
I’m not sure what should be the expected result (e.g. no dialog/ information about changing dataset) but the information about the changed property might be misleading as the changed Dataset is the major change in the form.
Central version shown in version.txt
https://test.getodk.cloud/
versions:
906addf66af230735e501ad73a1269012fdd7a5a (v2023.3.1)
+330132cf1ecb824b1fb88894287cb8edb5acefa5 client (v2023.3.0-2-g330132cf)
ba6ee474f431b48e885fb035c9266792f06d0ad7 server (v2023.3.1)
https://staging.getodk.cloud/
versions:
versions:
f78da7a8b7a132ad2baa794a656da6ba8e40754a (v2023.3.1-6-gf78da7a)
+ad92f1148c2fd32d0faaac9c3571410a6c31094b client (v2023.3.0-13-gad92f114)
+0fb4ebd78afb8c31d8f16d8ad38183111ece264f server (v2023.3.1-31-g0fb4ebd7)
Browser version
Chrome 114.0.5735.198, Firefox 116.0.2

@ktuite, do you think this behavior changed with getodk/central-backend#933?

The dialog doesn't show information about changes in Dataset or their properties (saveto).
The information shown in the dialog is correct because "thirdproperty" field was removed from the 2nd version

The information shown in the dialog is correct because "thirdproperty" field was removed from the 2nd version

I think this is something we might want to talk about with the rest of team - if some previous version of a form populates a dataset property that later gets removed, that earlier version could still be out there accepting submissions and creating entities with that property, but there would be no indication in the Central UI that that form and that property were (historically) linked.

What stood out to me most of all is that the behavior seems to have changed: different things are shown on test as opposed to staging.

Hmm, looking into the differences between staging and test.

I'm not 100% sure what is up with the new green plusses missing from the properties when the dataset itself is supposedly new. This is only seen on test, right?  I think there may be a draft or deleted or otherwise unpublished form or something with those properties, which is why the dataset looks new but the properties don't.  I wasn't able to exactly recreate it but I did get into this other state (https://test.getodk.cloud/#/projects/445/forms/basic_entity_2/draft) where the dataset basic2 is new and there are 5 out of 6 properties shown except there should only be 5 new ones.

Part of the diff response looks like:
    {
        "name": "third.property",
        "isNew": true,
        "inForm": false
    }

I think/hope this is fixed with the update I made to the dataset-diff endpoint. You can tell which is before/after the update by looking carefully at whether the property names are in alphabetical or not.

I have an underwhelming technical explanation for why that one modal mentions deleted fields but not dataset properties. There are modals at two stages:
a) when the form is uploaded. we check for deleted properties and DON'T actually save the form. They have to press the "upload anyway" button to re-POST it. we don't do dataset checks until the form draft is successfully uploaded.
b) the second modal is the publish confirmation modal. that should show the new dataset properties.

I'm not sure if we can/should compute dataset info in time for that first upload modal. Well.. if we did do something, it would likely go in Forms.checkStructuralChange.

Trying to clarify what I think this issue is about:

seeing a warning on form upload about a property being deleted, but no other dataset information available in the same modal

difference on staging vs. test between what is shown about dataset name and properties (getodk/central-backend#933 did change this, so as long as staging works, this should be ok)

The steps in test.getodk.cloud were in https://test.getodk.cloud/#/projects/436 . I looked for an already created dataset, deleted, or draft form but it's not present in the project. One difference that I might have accidentally introduced is started testing changes not only in xlsx forms but also xml. So steps probably contained first xml , then xlsx with the new dataset form.

I followed the repro steps in staging after creating a new project: https://staging.getodk.cloud/#/projects/37/forms/basic_entity/draft. I thought I'd add a few thoughts.

One difference that I might have accidentally introduced is that I started testing changes not only in xlsx forms but also xml.

XLSForms are converted to XML XForms anyway, so it shouldn't be a big deal. I took a look at the changes to the XML, and I didn't see anything surprising.

When a dataset and a property is changed in a form, the "Upload New Form Definition” dialog shows information about the changed property which might be misleading (no information about the changed dataset).

When I uploaded the second version of the form, which deleted a form field and changed the entity list, I saw a warning about the field. I didn't see a warning that the form will no longer save to any of the properties of the first entity list. In other words, we warn when a field is removed, but not when an entity list or property is removed.
The reason why it's so important to mention the deletion of a field is that the field will no longer appear in the submission data by default. There is an effect on the structure of the form. People sometimes try to rename a field, but Central doesn't understand renaming and sees it as one field being deleted and another being added. It's partly because of this mismatch in the mental model that we show this warning.
Things are a little different with entity lists and properties. There's no way to delete an entity list or a property. If you try to rename an entity list or property, that will just create more things. You'll see what those changes would be when you go to publish the draft.
I do think there's some awkwardness here: the fact that some information is shown when you first upload the form, while other information is shown after you upload the form. I'm CCing @issa-tseng in case she has thoughts about ways we might improve that flow. That said, we haven't heard of users running into problems with renaming entity lists or properties. I'm sure we'll start hearing about such problems at some point, and users' feedback at that time may guide the changes we want to make.

if some previous version of a form populates a dataset property that later gets removed, that earlier version could still be out there accepting submissions and creating entities with that property, but there would be no indication in the Central UI that that form and that property were (historically) linked.

I agree that there is potential for confusion here. @issa-tseng might have ideas about more information we could add to the UI about this. I also think we could wait to see how often and in what ways users encounter it: that might influence where we decide to show that information.

I checked it on staging and cloud server and there is a difference in the draft section.

In my repro, I saw:

Under "Entity List is updated by this Form:", the properties of basic2 all have a plus next to them. That's different behavior from production, and I'm glad you realized that, @dbemke. I think this new behavior is also OK though.
When I click "Publish Draft", I see a list of the properties of basic2. That's again different behavior from production, but I actually think it might be helpful to see the properties there.

I'm not 100% sure what is up with the new green plusses missing from the properties when the dataset itself is supposedly new. This is only seen on test, right? I think there may be a draft or deleted or otherwise unpublished form or something with those properties, which is why the dataset looks new but the properties don't.

I think this is probably clear at this point, but just to be explicit, the plusses are expected to be missing in production. The test server is very similar to production currently, which is why we see them missing there. I don't think it's due to the state of the form.

I did get into this other state (https://test.getodk.cloud/#/projects/445/forms/basic_entity_2/draft) where the dataset basic2 is new and there are 5 out of 6 properties shown except there should only be 5 new ones.

That's exciting! I didn't see that in my repro. Did you first just rename basic to basic2, then change the properties in a second draft? I actually see a difference in test vs. staging when I do the following:

Create a new project.
Create a draft form that would create an entity list with some properties.
Upload a new draft that would create the same entity list, but renames one of the properties.
On test, I see the old name of the property in addition to the new, but on staging, I just see the new.

Do you think this was changed in getodk/central-backend#933? The behavior on staging seems like an improvement.

To summarize, I think the changes on staging are an improvement. Unless @issa-tseng can think of other improvements to make, I think we can close this issue. @dbemke, does that sound right? This discussion has been very useful: this change in behavior isn't something I had seen before.


Authentication with Azure services using workload identity

Currently, azure sdk for cpp does not support workload identity as a credentials provider. When can be this implemented?

This is tracked by #4471

@nomanyaqub what is the scenario in which you need workload identity credential?
As I am working on this, it would be helpful to know the specifics of your use case. Thanks!


add a check for serviceURL

currently we allow all service URL to login through auth server, we only want only want to provide this service to devclub sites only.

Yes, later what we could do is have a database of the sso clients registered and when they make request to the auth server they will include an authorization header, which will be verified by the auth server. So basically we would have jwt's for the sso clients as well.

Do we still need this? Because now without the public key they can't use the auth anyway.


Add a flag to configure the subnet lease renewal margin.

This adds the command-line flag --subnet-lease-renew-margin, specified as
a number of minutes, instead of relying on the hard-coded default of 1h.

Could you add some documentation for this? At least a small update to the README but the more the better.

Hey Tom! Thanks for the feedback. I added a line for the new flag and a small section on the subnet lease duration and timing. Let me know if you think it should be expanded.

LGTM - merging


Autocomplete not working for this in derived class

With flow v0.21.0, whenever I try to define a derived class, this autocompletion stops working, both in constructor and methods. However flow check correctly reports 0 errors. Sample code:
/* @flow */
class Test {
  prop: number;

  constructor(prop: number) {
    this.prop = prop;
  }
}

class ExtendTest extends Test {
  extended: string;

  constructor(extended: string) {
    super(10);
    this.extended = extended;
  }

  method() {
    this.prop = 12;
    this./* here */
  }
}

Output with flow v0.21.0
$ flow autocomplete --strip-root src/app/components/_test/test2.js 20 10 < src/app/components/_test/test2.js
# No hints

and
$ flow autocomplete --json --strip-root src/app/components/_test/test2.js 20 10 < src/app/components/_test/test2.js
{"result":[]}

Output with flow v0.19.1 (the latest one working with this test case)
$ flow autocomplete --strip-root src/app/components/_test/test2.js 20 10 < src/app/components/_test/test2.js
extended string
method () => void
prop number

and
$ flow autocomplete --json --strip-root src/app/components/_test/test2.js 20 10 < src/app/components/_test/test2.js
[{"name":"extended","type":"string","func_details":null,"path":"src/app/components/_test/test2.js","line":11,"endline":11,"start":13,"end":18},{"name":"method","type":"() => void","func_details":{"return_type":"void","params":[]},"path":"src/app/components/_test/test2.js","line":18,"endline":21,"start":3,"end":3},{"name":"prop","type":"number","func_details":null,"path":"src/app/components/_test/test2.js","line":3,"endline":3,"start":9,"end":14}]

I'd like to give help, however I'm still pretty new to OCaml. l'll give a try to check the code.

I'm attaching here the log from flow server:
Couldn't autocompleteFile "src/typing/flow_js.ml", line 5975, characters 4-10: Assertion failed

The line is in the Autocomplete module.

Sorry this one slipped through the cracks. I'll take a look ASAP.

Debugging the code I've found that the problem is in flow_js.ml line 6173. While matching pattern TypeAppT, instantiate_poly_t is called with t of type ThisClassT, triggering assert false, because function is expecting only a PolyT type.
I've tried adding the following pattern just to test:
...
and instantiate_poly_t cx t types =
  match t with
  ...
  | ThisClassT t -> t (* here *)
  | _ ->
    assert false

Now autocomplete returns results for "ExtendedTest" (derived class) members, but not for parent class members.
Hope this helps. If anyone can point me to some test I can do or explain me some logic to follow in order to better understand this part, I'll be glad to dig deeper and eventually find a solution.
Thanks!

I've found that adding
and instantiate_poly_t cx t types =
  match t with
  ...
  | ThisClassT _ -> t (* here *)
  | _ ->
    assert false

results in correct behaviour (all tests passing), however I still don't understand deeply the codebase, so I'm looking for further ideas:
From my tests on the extract_member, I can see that:

if Bar does not inherits from Foo (class Bar {}):

Type is Bar (InstanceT)
super is MixedT (here)
extract_member provides Bar members

if Bar inherits from Foo:

Type is Bar (InstanceT)
super is ThisTypeAppT (with c as ThisClassT) (here)
extract_members continues recursion and steps into ThisTypeAppT pattern matching
with patched instantiate_poly_t, successive instantiate_type call returns InstanceT (Foo)
extract_members continues recursion on InstanceT (now Foo), terminating the cycle and providing Foo and Bar members

I'd like to ask, especially for my personal understanding, if:

Is it safe to change in this way instantiate_poly_t? I did only a fast check on the code, so I'm not sure about potential side effects.
Maybe we can just change extract_members matching and handling specifically ThisTypeAppT, something like:| ThisTypeAppT (c, _, ts) ->
   ...
   (* let inst_t = derive t from c, matching, another modified `instantiate_poly_t` function *)
   let inst_t = instantiate_type inst_t in
   extract_members cs inst_t

I don't know if this is correct, however I didn't find ThisAppTypeT with cdifferent from ThisClassT, but I'd like to know if this idea is valid from flow devs

Thank you!

On it.

@leonardfactory Your initial recommendation on adding a case to instantiate_poly_t is correct, and I'll put up a fix shortly following that. The reason is that post 0.20, which introduced this types, empty type args can arise for non-polymorphic classes, in which case the shape of the class being instantiated legitimately doesn't have a PolyT wrapper. So basically the fix amounts to checking types = [] and doing nothing if that's the case.


[TensorBoard] load data from relative path

To embed tensorBoard the data needs to be loaded from a relative directory, not /data.

We would need more details to know what kind of issue you are having.

we embed TensorBoard in our platform and mount the wsgi app under a certain path, eg. /extension/tb/12345/. So TB should get its data from /extension/tb/12345/data instead of /data

I'm pretty sure we still need more details, but @dandelionmane may have a clearer idea.

I believe removing the leading slash here would fix it?
Do you want to submit a pull request?
n.b. currently Bazel doesn't compile TensorBoard. We're actively fixing this right now. But until the next release, you will need to recompile the TensorBoard frontend yourself to test the fix.

Hi!
Yes, thats it! I removed the slash from the compiled js code and it works. Preparing a PR. Thanks!

okay, will not prepare an PR since i would have to undergo all the CLA for just one character.

Haha, I can do it on my end :)

@dandelionmane
Another place that still has the similar problem is the request of project plugin data in Embeddings panel,
e.g.  /data/plugin/projector/runs still requests in a absolute path.
I found the code  here
There is a leading slash for the route-prefix property in vz-projector-dashboard.
If it's correct, I will submit a PR. Thanks!
Another question is when will the tensorboard be recompiled. As now in version 1.0 these features are not included.


Feature/Poisson_Log_GLM

Submission Checklist

[x] Run unit tests: ./runTests.py test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary:
Adds primitive for Poisson regression with Log link function.
Intended Effect:
Speed up Poisson regressions. It currently is faster than a Poisson regression implemented using poisson_log_lpdf by a factor 11, based on my testing.
How to Verify:
Run unit test. It also has a performance test in it.
Side Effects:
Documentation:
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Matthijs Vákár
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Jenkins, ok to test.

Hi @seantalts , as far as I'm concerned, this can be merged.

cpplint on test for this one too http://d1m1s1b1.stat.columbia.edu:8080/job/Math Pipeline/job/PR-647/2/execution/node/23/log/

OK, cpplint is now also satisfied for the test.

Jenkins, retest this please.

I've made the requested changes and this is now ready to be merged as far as I'm concerned.


Sort plugin search results with better text matches higher in search results

Resolves https://github.com/runelite/runelite/issues/11520

Introduce SearchablePlugin and extract plugin search code to PluginSearch, which is now used by both internal and external plugin searches
Order search results using a few heuristics such that exact or close text matches occur higher up in the results

I tried using JaroWinklerDistance but it didn't have very good results, probably due to the varying name-length of plugins, so I settled on more human heuristics.

In discord raiyni requested a comparision with the current approach.
Currently all matching results are ordered alphabetically by name, with pinned items first.
So for the three searches in the original post, assuming no pinned items, we would have:
Search: statu

Master
Proposed

Discord
Status Bars

Fishing
Discord

Hunter
Fishing

Item Stats
Hunter

Smelting
Item Stats

Status Bars
Smelting

XP Updater
XP Updater

Search: gran

Master
Proposed

Bank
Grand Exchange

Chat Commands
Bank

Grand Exchange
Chat Commands

Ground Items
Ground Items

Item Prices
Item Prices

Search: bank va

Master
Proposed

Bank Heatmap
Bank Value Tracker

Bank Screenshot
Bank Value

Bank Value
Bank Heatmap

Bank Value Tracker
Bank Screenshot

High Alch Profit Highlighter
High Alch Profit Highlighter

It seems unlikely to me that we require this much complexity to do a simple search when we are also pulling in commons-text, are you sure theres nothing there that is useful?

I think the changes are warranted, the PR does two things:

Extracts search functionality across both plugin lists so that the same search is used for both
Orders search results more logically

In fact the set of things returned from a search is identical to the set in master.
There are three new classes, PluginSearch, SearchablePlugin, and SearchablePluginComparator. Each piece is actually quite simple, so I'd push back on the argument that this is complex. The plugin search solution in this pr is now neatly composed of small classes.

PluginSearch is where the search is glued together. Previously this was spread across the two list classes, now they both just have a PluginSearch and query it when they need to search
SearchablePlugin is a simple "value" (almost) object which just houses the things relevant to searching that are common: a name, keywords
SearchablePluginComparator is the bulk of the change, it implements the sorting of search results

I looked into the options from commons-text. We're using commons-text to decide the set of plugins to return (that's unchanged). I experimented with options for implementing the comparator with commons-text, but nothing worked very well. The distance functions are designed for strings that are all about the same length, rather than a 'name' and a set of keywords. Nevertheless I've tried to make the comparator clear by composing smaller comparators

As an example of how I think this approach is simpler:
Previously we would compute search results in two passes with showMatchingPlugins(boolean pinned, String text): the first pass would add the matching pinned plugins, the second would add the matching non-pinned plugins. With this PR, we find the matching results, then sort them with the comparator. Conceptually I think it's easier to reason about

Thanks for all the comments @abextm, I found them very helpful. Learnt a thing a two; I think I don't reach for interfaces often enough.
I've updated the PR resolving all of your comments


Error Message on DEMO Page

There is an error message on the demo page:
http://demo.getgrav.org/landio-skeleton/

Fixed, had an out of date admin plugin there.

great!


feat: Add placeholder support for images

This PR adds support for a placeholder to the gatsbyImageData resolver. 🎉
I've added 3 options for the placeholder, they are:

BLURRED
  Generates a very low-resolution version of the image and displays it as a blurred background (default)

DOMINANT_COLOR
  The dominant color of the image used as a solid background color.

TRACED_SVG
  Generates a simplified, flat SVG version of the source image, which it displays as a placeholder.

Additional context:
I think it's necessary to add this support under a beta tag, or alpha, so users can try it out and report any bugs before adding it as a stable feature.
Closes #172.

@notrab Quick note, you'll need to update the branches configuration for semantic-release if your intention is to publish this as a prerelease.

@ynnoj sounds great! I'll get that added. Thanks!

Will merge. Hopefully the prerelease works!

@all-contributors please add @jpedroschmitz for code, example, ideas

@jpedroschmitz we're trying this out now on our website, and will see how it goes before we merge next into main here.
Thank you for such an awesome feat addition! 🚀
PS. I've added you as a contributor to the package README 🥇

That's awesome, thanks! Let me know if there's an issue with the placeholder feature =D

We had a report earlier from someone implementing this

ERROR
[gatsby-source-graphcms] In order to use the traced svg placeholder, you need to install gatsby-plugin-sharp
despite having
"gatsby-plugin-sharp": "3.1.2"
in the project dependencies

I haven't yet tried to replicate this @jpedroschmitz but will report back when I do.

Unable to duplicate. It must a local user error. Works fine for me in a new, and existing project with all placeholder types.

That's weird. The plugin was added on the gatsby-config file?
If it was, maybe deleting the node_modules and yarn.lock, alongside with gatsby clean, can fix the issue.


Added revision and stock item QR code URL for label creation

@SchrodingersGat I wanted to code the stock item absolute URL directly into the QR code, so a phone can open the link directly.
In the label template, this will generate the QR code URL:
<img class='qr' src='{% qrcode qr_url %}'>

I also added the part revision in the context data so I could create some sweet labels like:

Fantastic! Please also add a short note to the revision info in the docs :)

@SchrodingersGat See https://github.com/inventree/inventree-docs/pull/100!


How to change the transaction cost of side chain DAPP?

You can't set the transaction cost on your side chain. You can set the cost of a custom contract on the side chain to a fixed value.


Setting page title shows no I18n information.

Jason file isn't translated on user setting page in the latest version.
jhipster-vuejs/generators/client/templates/vue/src/main/webapp/app/account/settings/settings.vue.ejs
User settings for [{{username}}]
should be changed to:
User settings for [{{username}}]
the fix works for me.
FYI.

Thanks for reporting this @china-fengguan
FYI, Vue.js has been integrated to main generator-jhipster
So I apply your fix there: https://github.com/jhipster/generator-jhipster/pull/12141


Migrate expression index from data pipeline to ETL

Currently the ETL uses the output of the data pipeline.
The data pipeline is dismissed so we need to migrate the process from data pipeline to ETL.

Updated PIS with a specific step (hpa)

https://github.com/opentargets/platform-etl-backend/pull/171
Major reviews and checks:

the complete list of genes and labels
The "protein" arrays has max level but the cell_type has a specific level.
reliability true/false value


<'foo'> linking shorthand omits the quotes from the output

The <'foo'> autolink represents a production equivalent to a property's grammar. It's meant to display the same as it is written, as <'foo'>; instead, it currently displays as <foo> with the center word linked. This is incorrect.
(Reported in the wild at https://github.com/w3c/csswg-drafts/issues/7109)

Nm, it was bad markup (it should have been <<'foo'>> in the source)


java.security.NoSuchAlgorithmException: AES/CBC/PKCS5PADDING

Hi,
we are using spongycastle as provider in out Android app (we switched from bouncycastle). On some devices we encounter a NoSuchAlgorithmException when calling Cipher.getInstance() with "AES/CBC/PKCS5PADDING" as algorithm and "SC" as provider. The call fails on following devices:

ME302C
GT-I8200N
GT-I9305
YD206
GT-N7100
...

As far as we now, the call never succeeds on those devices. We are using <IP_ADDRESS>.
Thanks for your work!

+1

Small update: The issue can be reproduced on a Nexus 5 AVD with Android 4.4.4.
Using "AES/CBC/PKCS7Padding" solves the issue.


Feature Request: Sort Graph Legend

Summary
Given a query which results in multiple lines, it would be nice if there was an option to sort the legend by a summary statistic, i.e., sort the legend by max, min, avg, etc.
Example
Imagine we want to identify the node with the highest latency. In this example, it would be nice if we could sort the legend by max value and have the first entry in the legend be the node with the highest latency.

I want to get some feedback on how this would work. Right now the legend is ordered based on the order on the stack and for expressions that have multiple results (group by) sorted by the legend text. The reason for this is to make it easy for someone to understand where an expression will show up in the legend.
Option 1
Consider a common alert visualization:
http://localhost:7101/api/v1/graph?s=e-1d&q=
  120e3,threshold,:legend,
  name,sps,:eq,(,nf.cluster,),:by,:dup,
  :max,120e3,:gt,30,:alpha,:vspan,trigger,:legend,:swap,
  $nf.cluster,:legend

For this type of visualization, I think it is desirable to have the threshold and trigger lines pinned to the top of the legend. However, this would not be true if the legend for a given axis was sorted by stat like max. This would imply we would need to do the sort per expression, something like:
name,sps,:eq,(,nf.cluster,),:by,max,:rsort

For now I'm assuming :sort and :rsort (reverse sort) that takes one of the named stats. Probably also allow a value like legend so that the current default mode could be explicit.
Option 2
If we only allow sorting by expression, then a sequence of expressions that cannot be represented as a group by cannot be sorted. Example:
http://localhost:7101/api/v1/graph?s=e-1d&q=
  name,sps,:eq,:sum,1e3,:div,
  name,requestsPerSecond,:eq

This would imply specifying the sort at a higher level like one of the url parameters for an axis.
&sort.0=max

Option 3
Allow both. I can argue for both option 1 and option 2 behavior, but I'm not sure how it would work to support both. Typically we have tried to follow a pattern where the most specific setting would take precedence, e.g. a line style in the expression will override the url param &stack=1. This case is a bit more difficult because the more specific setting cannot win without breaking the more general setting for other expressions.
So what should the behavior of something like this be:
http://localhost:7101/api/v1/graph?s=e-1d&sort=max&q=
  name,sps,:eq,:sum,(,nf.cluster,),:by,1e3,:div,max,:rsort,
  name,requestsPerSecond,:eq

I feel like silently picking either would be confusing so it should probably add a warning to the chart. Other than that I would like to prefer the most specific option. So I guess I would suggest if any sub-expression is explicitly sorted it disables the sort setting on the axis (with warning to user).
Thoughts? cc @tregoning @svachalek

Added in #350.


When closing a channel the wrong channel is removed from the UI.

Describe the bug
When closing a channel the wrong channel is removed from the UI.
To Reproduce
Steps to reproduce the behavior:

Open two channels with the same node.
Close channel A.
Notice that channel B is removed from the UI.
Close zap (force close on iPhone) and reopen.
Notice that channel B is the only one displaying (channel A did close correctly).

Expected behavior
Channel A should be removed from the UI.
Screenshots
If applicable, add screenshots to help explain your problem.
Your environment
iPhone SE

should be solved by new alpha


On the sample OnMenuItemClickListener should be onOptionsItemSelected to support lower api's

Title ^^
(If i'm not mistaken)

Hello @PedroBarbosaPT !
Oops, it was an artifact, 'cause both of methods was already in activity class. I've fixed this now.
Thanks for remark!


feat: add vitepress folder icon

Closes #2587
Added VitePress folder icon.

Add a new entry for .vitepress in folderIcons array in src/core/icons/folderIcons.ts.
Add folder-vitepress.svg and folder-vitepress-open.svg to the icons directory.

For more details, open the Copilot Workspace session.

I was wondering if it's better when we align the lightning with the grid:

ah, and this one:

We could also elaborate how it would look like if we give the lightning a yellow color. I know it's not following our rules, but maybe it looks a little better, not sure.


HomeBridge on Windows - moving installation to another PC

Hello.  Have homebridge running on WIndows thanks to this awesome guide here - thanks very much for creating!!  https://github.com/nfarina/homebridge/wiki/Install-homebridge-on-Windows
Would anyone know what components are required if I wanted to move the homebridge implementation to another PC?  So all running on my laptop where I 'built' the solution using Visual Studio etc.. but wondering if i can possibly install NodeJS/Python and whatever other core components are needed and then move the compiled homebridge (and associated) folders under C:\Users\xxx\AppData\Roaming\npm to another machine and execute there?
Any help greatly appreciated..

Hello. Have homebridge running on WIndows thanks to this awesome guide here - thanks very much for creating!! https://github.com/nfarina/homebridge/wiki/Install-homebridge-on-Windows

You are Welcome :)

Would anyone know what components are required if I wanted to move the homebridge implementation to another PC?

The same question already went me through my mind. If I had more time, I would experiment a little. Maybe, you can give me a answer later ;)
Greeting
Patcher

Think im 99% sorted.
I just started moving and installing bits until i got some joy :)
I have one issue that maybe isnt an issue due to moving the deployment but will document that below.
Here are the steps i followed to move the deployment and the 'gotcha' i struggled with.. maybe someone can comment on how to get round this too.
I moved this to an HP i5 Laptop running Windows 10.
The firewall was already off on this PC.. so i presume if your firewall was on youd need to open port 51.. that homebridge uses?
My laptop also had GIT installed on it as well.  Again, not sure if this is needed but it was on the laptop anyway so i left it there.
I copied the C:\Users\xxx.homebridge folder (with the config file) from the machine i built the solution on initially to the new laptop in the same place.
I also copied the C:\Users\xxx\AppData\Roaming\npm folder (and its contents) to the new laptop as well.
I then tried to start homebridge and obviously got errors as dependencies were missing so i kept installing the bits below and running until i had some luck.
Nodejs v5.0.0 32BIT (https://nodejs.org/en/download/releases/)
Python 2.7.11 32BIT (https://www.python.org/downloads/)
Open SSL 1.0.2h 32BIT (http://slproweb.com/products/Win32OpenSSL.html)
Bonjour for Developers <IP_ADDRESS> (https://developer.apple.com/bonjour/)
I am not 100% sure if i needed Bonjour - homebridge actually started before instaling Bonjour but i had an issue with my phone seeing it, hence why i thought maybe some mDNS bit was missing..
When i went to start homebridge on the new laptop, it did start but i realised, i should change the name and the ID in the config file so i know im dealing with the new implementation not the old.
I tried searching for new accessories, nothing.  I added a new house and tried searching for accessories.. nothing.
I then blitzed my homebridge config on my phone and retried setting up.. i then realised homebridge was still running on the old PC.  So i stopped it and tried again, and viola.. i saw the new homebridge accessory.  I connected and was away!!
So, i think by copying the implementation from oid to new, there was 'seomthing else' that was common between old and new install that was conflicting when i had both old and new bridges running???  i thought chaning the name and the id at the top of the config file would have been enough?  anyways, i dont plan to run the old implementation now as it is now living on the laptop i want to run it on for ever more.  Maybe someone can explain what needs to change so both bridges could run.. and the new bridge could be truly unique and run in parallel on the same LAN..
Last trick i had, and this may be nothing to do with the install.. is that with my config from my old pc, the start up crashed on this line in my basic light setup.
"status_url":  "http://localhost/status/100059",
It tried to check localhost - and got a Connection Refused <IP_ADDRESS>:80 and homebridge crashed in the homebridge-http module.
This may very well be something on my new laptop listening and refusing the conection on Port 80.. as i wasnt using the status_url, i just removed the bogus URL and all is well.
So homebridge may have crashed at this stage if i had built the solution here..
Anyways, i moved the install and im happy.. im just not 100% sure i havent got some gremlins becuase of my hack move ;)


Allow to exclude robots.txt file from generation, add tests, fix typos.

I use vite-ssg-sitemap library, which is based on sitemap-ts library. I was surprised when I discovered that my own robots.txt file was replaced with some other file. After investigation, I realized your library not only provides the sitemap generation but also automatically creates a robots.txt file, which is really cool for those who are not familiar with SEO basics. However, there is no way to disable that generation, so I decided to add that option, with remained true (enabled) value by default.
robots.txt file is actually something that you don't change that much - you mainly copy/paste that file from old projects, so for me, it's easier to just put that file in the public folder and don't generate it on each build. That's the main reason for disabling that generation. Moreover, I didn't find some options that I want to add to robots.txt file (they are non-standard, btw) - so a manual fix is required anyway.
BTW, since I encountered some issues with my IDE/config file, please check my MR locally before merging.

@mikezotovdev You can upgrade vite-ssg-sitemap to v0.5.0 and you will be able to use generateRobotsTxt param. Thanks for your contribution


ARROW-3404: [C++] Make CSV chunker faster

This speeds up multi-threaded CSV reads by removing the serial bottleneck of detecting newlines when no newlines can be present in CSV values.
On this machine (8-core AMD processor), the speed of reading a CSV file of text column data goes from 600 MB/s (before this patch) to 1.2 GB/s.

Very nice speedup!


Trying to access 'https://epiphany.pub/@seisvelas/' gives me 'no content found.'

I was wondering if I could share my 'profile' or a catalog of my posts by using 'https://epiphany.pub/@seisvelas/', but instead attempting to access that URL I get the message 'no content found.'
Not sure if there is a different way to do this, but either way I imagine this is not the intended behavior when someone accesses that URL! Haha.
Screenshot attached:

Thank you! this is fixed now. https://epiphany.pub/@shi-yan/
There was a bug that doesn't recognize the last slash '/'
I made sure all variations work
https://epiphany.pub/@shi-yan
https://epiphany.pub/@shi-yan/
https://epiphany.pub/@shi-yan/inverse-kinematics-explained-interactively
https://epiphany.pub/@shi-yan/inverse-kinematics-explained-interactively/

Thanks! Not sure if this is worth fixing but I notice when I access an author's profile with this url format (@user) it just redirects me to a monster URL based on the user id. For example, https://epiphany.pub/@shi-yan redirects to https://epiphany.pub/profile?authorId=faa2ff7436b15877418252219f4f1042029a75e42a4851e9b8d6af949d1a6756
Couldn't the user be found just as easily with the username vs this huge id? Very minor, I realize, but seems like it would be better if the default URL of a profile was just the @user format.

Thank you very much for the feedback! Yes, I take your feedback seriously. using the id isn't ideal. I will fix it this week!
reopen

This issue should be resolved now. The profile page doesn't need id anymore.
Thanks!
https://epiphany.pub/@shi-yan


added Adams orc

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.176%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
6324

Relevant Lines:
7172

💛  - Coveralls


Add mandatory metadata in LogEntry if exists.

Add static metadata _integration : azure .
Add event metadata for following keys :
level -> severity, operationName -> activity_type, resourceId -> azure_resource_id, category -> category .

Please add the local.settings.json file as well

LGTM


[Playground] Make new python examples runnable

Several of the new examples for Playground were not runnable by the Playground as they were missing the invocation of the example function itself, however they were executed fine in tests.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Python_Runners PreCommit

Run Python_Integration PreCommit

lgtm thanks!


apps/ecparam: Avoid crash when parameters fail to load

Added missing check for NULL EVP_PKEY returned from load_keyparams().

This partially fixes the #13338

This pull request is ready to merge

Merged to master. Thank you for the review.


Gunicorn timeouts not working

Describe the bug
Gunicorn timeouts are not working. It's supposed to kill gevent threads taking more than 60 seconds, but it's not working as we see responses on Kibana taking longer than that

I've been reading the docs and timeout is working, but I understood it wrong:

As long as there's connection between gunicorn and the web worker, there's no timeout
As we are using light threads (gevent), as long as we don't block the event loop there's always connection between gunicorn and the web worker
I only see timeouts when the event loop is blocked, and in that case thy are working

As currently if there's any issue with the web worker kubernetes with the healthiness probe will take care of it, I would close this issue. WDYT @gnosis/safe-services ?
I would close this issue

cc @rmeissner @fmrsabino @luarx @jpalvarezl


[ISSUE #4700]Optimize print information when the  rocketmqHome variable not set

Make sure set the target branch to develop
What is the purpose of the change
Fix #4700
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #4703 (f0e1e9f) into develop (8504abf) will decrease coverage by 0.22%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             develop    #4703      +/-   ##
=============================================
- Coverage      44.68%   44.45%   -0.23%
+ Complexity      7540     7496      -44
=============================================
  Files            977      977
  Lines          67594    67597       +3
  Branches        8927     8928       +1
=============================================
- Hits           30207    30053     -154
- Misses         33669    33815     +146
- Partials        3718     3729      +11

Impacted Files
Coverage Δ

.../apache/rocketmq/controller/ControllerStartup.java
0.00% <0.00%> (ø)

...rg/apache/rocketmq/common/stats/StatsSnapshot.java
84.61% <0.00%> (-15.39%)
:arrow_down:

...apache/rocketmq/broker/longpolling/PopRequest.java
31.03% <0.00%> (-13.80%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-13.44%)
:arrow_down:

.../apache/rocketmq/common/stats/MomentStatsItem.java
38.09% <0.00%> (-9.53%)
:arrow_down:

...q/namesrv/routeinfo/BrokerHousekeepingService.java
72.72% <0.00%> (-9.10%)
:arrow_down:

...ache/rocketmq/common/stats/MomentStatsItemSet.java
39.13% <0.00%> (-8.70%)
:arrow_down:

...a/org/apache/rocketmq/logging/inner/SysLogger.java
28.57% <0.00%> (-5.72%)
:arrow_down:

...ava/org/apache/rocketmq/filter/util/BitsArray.java
58.11% <0.00%> (-5.13%)
:arrow_down:

...va/org/apache/rocketmq/common/stats/StatsItem.java
50.00% <0.00%> (-5.00%)
:arrow_down:

... and 22 more

Help us with your feedback. Take ten seconds to tell us how you rate us.

Coverage increased (+0.1%) to 48.857% when pulling f0e1e9f97212460c67f5f64aad0b7bac69cc819f on mxsm:rocketmq-4700 into 8504abfafcf763be6fc593183edb1a2f8f061e51 on apache:develop.


rbenv-init shell detection fails from a su'ed session

In FreeBSD, the shell detection fails when issued from a su'ed session.  This issue was introduced in #730:
As root:
# su - user
$ echo $SHELL
/usr/local/bin/bash

From rbenv-init https://github.com/rbenv/rbenv/pull/730/files#diff-d54a534ce5e26cc4f4cbcffbff76ce3eR25:
$ shell="$(ps -p $$ -o 'args=' 2>/dev/null || true)"
$ echo $shell
-su (bash)
$ shell="${shell%% *}"
$ echo $shell
-su

Causes rbenv init - to set su as the shell:
$ rbenv init -
...
export RBENV_SHELL=su
...

Obviously, if we revert:
$ shell="$(ps c -p $$ -o 'ucomm=' 2>/dev/null || true)"
$ echo $shell
bash

Not really a big issue, as this can be worked around by specifying the shell (i.e. rbenv init - bash).

This issue is also present in Linux systems (Debian):
$ su - user
$ ps -p $$ -o 'args='
-su

Thanks for reporting! This is really a nasty issue 😞 I'm not sure how we can improve the shell detection to avoid this.

Closing as stale. I don't know the solution, and we already have a workaround (always specify the shell).


Sync terminal position (presentation) with selected problemMatcher generated problems

When a problem is generated from terminal output (via a custom problem matcher) the applicable terminal output at the error point is often indispensable in diagnosing the problem. The VS code problem can only provide so much information (esp given limitations disuccsed in #9635)
It would be extremely useful to have a presentation option in the problem matcher config that, when set, causes the terminal to scroll to and (possibly) highlight the output that triggered the problem when the problem is clicked (or 'Go to next problem', etc.)
To provide a concrete example, our project uses Python's doctest scheme, which we run using our own test runner. We're using tasks to run tests, which are defined in Markdown formatted documents. This approach falls outside the purview of the mainstream Python test frameworks PyTest and unittest.
The scenario we're dealing with is outlined here.
We're able to detect test failures and generate problems easily enough - but without the ability to "go to" the source of the error in output, it's quite hard to diagnose and fix the problem. Imagine pages of terminal output with dozens of test failures. Clicking a problem takes us to the test definition in source code but without also highlighting the terminal output we don't have the full picture of the failure.

Sort of related #172742

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Action Transmission channels should be flexible on number of spaces

This probably ends up being solved by using GDS wiring and then exporting those relations to action transmission channels

We can still use them as single and it actually works better this way


Minor doc fix

Fixed two minor documentation issues

The first reported in the swift forums in documentation for function OrderedDictionary.updateValue. changing updateOrInsertValue(_:forKey:at:) to updateValue(_:forKey:insertingAt:)
The second reported in https://github.com/apple/swift-collections/pull/6#issuecomment-813865398 , the default new pull request templet has an incorrect link to the Contribution Guidelines

Checklist

[ x] I've read the Contribution Guidelines
[ x] My contributions are licensed under the Swift license.
[ x] I've followed the coding style of the rest of the project.
[ x] I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
[ x] I've updated the documentation if necessary.

@swift-ci test


[ch47158] Release/1.0

All function in modules under python-lib
improved tokenizing with 38 dependent-tokenizer modules from Spacy (should be leveraged for other NLP plugins)
UX harmonized with other NLP plugins
language detection with cld3 instead of langid

Clubhouse integration: ch47158

@DamienJacquemart I just finished the 2nd review and left comments inline.
We are mostly good on the UX, although we can simplify language choosing and add a parameter for the user to control the correction max edit distance.
On the backend, there are several important simplifications and optimizations to bring. In particular, the spaCy tokenization needs proper bundling and pipelining. We also need to dig to the bottom of the issue with Korean. It's important we get the tokenization library right, as it will be used by all other plugins.
For the autocorrection part, it seems mostly OK from a code perspective (only a few enhancement suggestions). However, I have a question on dictionaries: Are we using https://github.com/wolfgarbe/SymSpell#frequency-dictionaries-in-other-languages or only https://github.com/hermitdave/FrequencyWords?

@StanislasGuinel I let you review the PR again, as I brought quite a few changes following my previous review

@StanislasGuinel I passed a few small changes, I let you tell me if it's good to go when you come back from vacation!


pkgr: auth errors aren't shown to the user

if your token is invalid, there is no error shown to the user.

Bisected the regression to 48e8547


archive

I have followed every step of the readme file and other guides.
but i keep getting the following error when i try to run the main.py
\main.py", line 10, in
from gpt_engineer.db import DB, DBs, archive
ImportError: cannot import name 'archive' from 'gpt_engineer.db'
i have also tried deleting it and doing everything over.

same trouble here, I checked content  of this DB.py file at the environment folder, my path was: C:\ProgramData\anaconda3\envs\gpt-engineer\Lib\site-packages\gpt_engineer\db.py
It did not have this part of code:
def archive(dbs: DBs):     timestamp = datetime.datetime.now().strftime("%Y%m%d_%H%M%S")     shutil.move(         str(dbs.memory.path), str(dbs.archive.path / timestamp / dbs.memory.path.name)     )     shutil.move(         str(dbs.workspace.path),         str(dbs.archive.path / timestamp / dbs.workspace.path.name),     )     return []
maybe that is the issue?
Although after adding that definition, same error persists.

Same issue here. I was using version 0.0.3 before and it was working. The issue occurred only when I pull the latest repository (V 0.0.7)

Same issue!

Same too

#MeToo

Came to say the same!

Can you please try pip uninstall gpt-engineer and then install again and let me know if it helps? (to install, either pip install gpt-engineer or pip install -e .)

See #487

Just fix the damn program and update the files...

Just fix the damn program and update the files...


Update devcontainer image: v1.0.0-alpha.0

Automated changes by create-pull-request GitHub action

Will close as we already have bumped to a custom container with new rust version.


update data backup

Pull Request instructions:

Please follow the update protocol
Answer the questions below in detail. Your responses will be emailed to experimenters.
If the experimenters must do anything new, provide detailed step by step instructions on the wiki
If computer maintainers need to manually update anything, provide detailed step by step instructions
Use markdown syntax in order for your comments to be rendered reliably in the email: "1." instead of "1)", use four spaces for indents.
If you use the keyword "skip email" in the title, it will skip the email updates
Merges from "develop" into "production_testing" should use the keyword "production merge" in the title for reliable indexing of updates
Merges from "production_testing" into "main" should use the keyword "update main"

Describe changes:
Save data in the main thread.
What issues or discussions does this update address?
I speculate that the occasional crashes are related to the conflicting interaction between the different threads (between backup saving and _GenerateATrial).  Here, I moved the backup to after the GeneratedTrials._GenerateATrial(self.Channel4) to avoid simultaneous running of these two functions.
https://github.com/AllenNeuralDynamics/aind-behavior-blog/issues/605#issuecomment-2342288067
Describe the expected change in behavior from the perspective of the experimenter
No
Describe any manual update steps for task computers
No
Was this update tested in 446/447?
Tested on my own computer.

But if saving takes .5s, that means the GUI will be unresponsive for .5s after every trial. This is not ideal

But if saving takes .5s, that means the GUI will be unresponsive for .5s after every trial. This is not ideal

You are right. I updated it to still use a separate thread. And moved the backup to after the GeneratedTrials._GenerateATrial(self.Channel4)  as I found the conflict is mainly caused by interaction with _GenerateATrial.

@alexpiet Do you have extra concerns about this PR?


Achievements Page Mobile View

Description
Closes #2150
Reorganised the achievements page so that its mobile-friendly. The layout has been adjusted to ensure better readability and interaction on smaller screens. Components are now stacked vertically and wrap properly when the screen size does not allow for horizontal alignment.
Type of Change

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

How to Test

Navigate to the achievements page on a mobile device or use a browser's mobile view functionality.
Verify that all components are stacked vertically and are responsive to changes in viewport size.

Please provide any additional steps or configurations if applicable.
Checklist

[x] I have tested this code on various mobile screen sizes.

Could you provide a screenshot of the UI in the PR description?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 2 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.006%) to 36.305%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/achievement/AchievementManualEditor.tsx
0
1
0.0%

src/pages/achievement/subcomponents/AchievementDashboard.tsx
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.006%

Covered Lines:
4997

Relevant Lines:
12866

💛  - Coveralls

Found another issue while testing the Achievements View, more specifically in the control page. The preview was not formatting the achievements correctly, I'm not too sure if this is also the case in production as I do not have admin access.

Have edited so now it would reflect what its supposed to look like in the achievements page.


Question about scope of tslint-config-prettier...

This project is not about using rules from tslint.json for prettier formatting, right?
It is only about conflicts? If the answer it yes - is there anything available which uses tslint.json for configuration of prettier?

It's for avoiding conflicts, and honestly have no idea if there is something for what you want. It doesn't make much sense, since the idea is to let Prettier handle the formatting.

If you want lint errors if your code doesn't conform to prettier rules, you will want to use the prettier plugin for tslint: https://github.com/ikatyang/tslint-plugin-prettier


Add Column Range Support to MSBuild ProblemMatcher

This updates the format supported by parseLocationInfo to handle
column ranges. MSBuild canonical errors can be of the form
<line>,<start>-<end>.
https://github.com/dotnet/msbuild/blob/94c28cca4cdb22f2cac279e3fd8d86aa4d061848/src/Shared/CanonicalError.cs#L12-L51

This PR fixes #154053

I've updated this to support <line>-<line> ranges too.
The previously supported formats were:

<line>
<line>,<col>
<line>,<col>,<line>,<col>

The new formats added are

<line>-<col>
<line>,<col>-<col>

This should be a superset of the previously supported locations. MSBuild only allows a range of columns on a single line, or a range of lines. This should be guaranteed by the regex in both parseLocation and the MSBUild (msCompile) problem matcher.

Squashed down to a single commit.

Is there anything more that I can do to help out with this feature?

@iwillspeak sorry about the delay, we'll try look at this during next debt week (starting 1st of August)

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


[WIP] take snapshot by event name

If you have big events sometime, it would be useful to create also a snapshot if this event occurs. I want to discuss this feature, before I complete it.
The reason against to create a new plugin e.g. SnapshotEventNamePlugin is, that if the event name occurs at the same time if version step is reached, two snapshosts will be executed. And maybe to avoid performance issues because of double checks. I see no possibility to stop propagation, because other plugins can be exists.

[ ] Add/Fix unit tests
[ ] Update docs

UnitTests fail because the Mock from EventStore are not available. How can be this resolved?
Aggregate root class ProophTest\EventStore\Mock\User can not be found

Composer install --prefer-source
Am 15.10.2016 17:04 schrieb "Sandro Keil"<EMAIL_ADDRESS>
UnitTests fail because the Mock from EventStore are not available. How
can be this resolved?
Aggregate root class ProophTest\EventStore\Mock\User can not be found
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prooph/snapshotter/pull/14#issuecomment-253972184,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYEvIPiqPQRCSLYK_4OVfDv6Si6nP7lks5q0Jb-gaJpZM4KXp9R
.

looks good so far, SnapshotPluginFactory needs update

Will do it!

@prolic I'm ready.

Can it wait until friday? I'm off the next three days.
Am 18.10.2016 04:07 schrieb "Sandro Keil"<EMAIL_ADDRESS>
@prolic https://github.com/prolic I'm ready.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prooph/snapshotter/pull/14#issuecomment-254318012,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYEvOUAkHxfFku5Sm4RUoOZZlkXa9ptks5q09VogaJpZM4KXp9R
.

released with https://github.com/prooph/snapshotter/releases/tag/v1.2.0


Implement Environment.MachineName on Unix

Currently the implementation return PNSE for UWP. We have to get GetComputerName win32 api supported on Store profile or find other suitable API. This issue also tracks porting the Unix implementation using gethostname in coreclr to corert.
cc @joshfree @jkotas

This issue should be just about the Unix implementation...

will look at this.

In CoreCLR how can we get ComputerName on Unix type machine ?? Envoirnment.MachineName is available there ?

Environment.MachineName will be available in System.Runtime.Extensions <IP_ADDRESS> contract. The work is being tracked here: dotnet/corefx#5428

This is done by the PR https://github.com/dotnet/corert/pull/795


Registration API health resource - spec not matching BBC implementation

The health resource POST is specified as follows:
/health/nodes/{nodeId}:
  displayName: Node health
  post:
    description: Update Node health
    responses:
      200:
        body:
          example: !include ../examples/registrationapi-v1.0-health-post-200.json
      404:
        description: Returned when the requested Node does not exist or has been garbage collected`

However, the VM provided on box to incubator members behaves differently, responding with a 204 No Content with no body. I think the RAML specification should be:
/health/nodes/{nodeId}:
  displayName: Node health
  post:
    description: Update Node health
    body:
      example: !include ../examples/registrationapi-v1.0-health-post-200.json
    responses:
      204:
        description: No content successful response.
      404:
        description: Returned when the requested Node does not exist or has been garbage collected`

This was discovered during a side-by-side comparison of ledger's registration service with the bbcrd VM (bbcrd_ipstudio_exportable_headless_discovery_amd64_master_2016-02-06.ova).

I'd suggest that as things stand this is actually an error in the provided implementation. The intention is that the server side provides the health timestamping rather than the client given there's a chance their clocks might not be in sync with each other. As a result the POST should be performed with an empty payload, with the 200 response to that giving the same response payload as the corresponding GET request.
I have a patch for the issue in the implementation which I'll provide via usual incubator channels shortly.


Reskin Deprecated Components

Codecov Report
Attention: Patch coverage is 43.41564% with 275 lines in your changes are missing coverage. Please review.

Project coverage is 71.35%. Comparing base (f114994) to head (ca2ede3).

Files
Patch %
Lines

src/components/twitch-wheel/OptionsMenu/index.jsx
11.11%
112 Missing :warning:

src/components/twitch-wheel/PlayerSelect/index.jsx
49.16%
91 Missing :warning:

...mponents/twitch-wheel/ImportedMainScreen/index.jsx
3.92%
49 Missing :warning:

src/pages/main-screen/index.jsx
38.88%
11 Missing :warning:

src/components/game-code-form/index.jsx
84.09%
7 Missing :warning:

src/pages/authenticated-app/index.jsx
75.00%
3 Missing :warning:

src/utils/index.jsx
95.12%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
- Coverage   71.80%   71.35%   -0.45%
==========================================
  Files          26       26
  Lines        4210     4301      +91
  Branches       50       54       +4
==========================================
+ Hits         3023     3069      +46
- Misses       1187     1232      +45

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


exclude link categories from sitemap

1. Why is this change necessary?
Currently, all categories are submitted to the sitemap. Those that are external links as well. They return code 404 in the sitemap.
2. What does this change do, exactly?
I've added a condition that excludes link categories.
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-21613
Please use this issue to track the state of your pull request.

The PR has been merged. Thank you for your contribution 🎉 💙


Update nanoid version to at least >=3.1.31

Update nanoid version to at least >=3.1.31 due to the CVE-2021-23566
https://nvd.nist.gov/vuln/detail/CVE-2021-23566

released in<EMAIL_ADDRESS>


Release of www on 7 Dec 2020

Deployed on

ome-www-dev
ome-www

All seems to have worked fine, the deployment looks good.
cc @sbesson @joshmoore

Travis failure is unrelated. Merging to keep playbook in sync with the current deployment state. As discussed separately, we will likely be moving away from ome.deploy_archive imminently to manage the release frequency of www.openmicroscopy.org


feat(metriken): rewrite metrics library

A clean reimplementation of the metriken metrics library. That makes some slightly different design choices. Metrics may now have associated metadata and an associated formatter. This allows for adding scoped metrics and to define a particular formatter for each metric.
Overall this adds a lot of flexibility through a richer metrics representation.

Closing this as the changes needed were made across several smaller PRs.


Yes

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[x] Filename in the lowercase format
[x] Image format: png
[x] Image size: 256 by 256 px

Merged here https://github.com/TrustWallet/tokens/pull/650