Tested Numbers on Home Page shows blank even though data is available

Bug Description
The homepage of https://www.covid19india.org/, on it's initial load, doesn't show any tested numbers even though tested data of many states are available.

Expected behavior
Since data for almost all of the states are available (even if some of them are 3-4 days old), we should display the number of people tested as well on the initial load. Expected behaviour is to sum up all the number of tested people from all of the states and display it there.
Additional context

Since the tested box has a last updated field and a link field, I guess the initial load should not display those.
Why is it important?
The amount of people tested for Covid-19 is extremely significant. The lower the number of people tested, higher is the chance that there is a significant number of people with Covid-positive, unreported. The website provides, as of now, no way to see the total number of people from India who have been tested. Even if some data is a few days old, many state's data of reported Covid-cases, recovered and deaths are old as well. Since those fields are summed up and shown, the tested field must also be summed up and shown.

I think, this number should be number of sample tested, not number of people tested. As per ICMR update, as of April 16 number of sample tested are 3,02,956, where as number of people tested is 2,86,714. I think this site https://www.worldometers.info/coronavirus/ is also reporting number of samples tested for all countries.

The site now reflects the Total Tested reported by ICMR. Thanks for reporting.
@kbpatel1 , since the other numbers reflect each individual, isn't it better to have parity with that and report the total individual tested?


DRY in generate log

Signed-off-by: Eric Windisch<EMAIL_ADDRESS>

Coverage decreased (-25.1%) to 62.5% when pulling 2a66e6ac44fb4f4e41ed28451adeaee490d0a5e1 on ewindisch:promise-cleanup into afb05c117c703875b6d1326ca64f8820cfb3b950 on iopipe:master.

Coverage decreased (-25.1%) to 62.5% when pulling 377d3a35e0792a9ca1d262d4a39ff41883f8e284 on ewindisch:promise-cleanup into afb05c117c703875b6d1326ca64f8820cfb3b950 on iopipe:master.

Coverage decreased (-24.5%) to 63.107% when pulling 60728fe37a08c41dc97bbe8421bb3ae71e13ab9d on ewindisch:promise-cleanup into afb05c117c703875b6d1326ca64f8820cfb3b950 on iopipe:master.

Coverage decreased (-24.5%) to 63.107% when pulling 80a11e54c1754ae88686aaeab1789e318394427a on ewindisch:promise-cleanup into afb05c117c703875b6d1326ca64f8820cfb3b950 on iopipe:master.

Coverage increased (+0.8%) to 88.406% when pulling 87ddf2aa0bd4130abe26e2ca4d392824d77d38a5 on ewindisch:promise-cleanup into afb05c117c703875b6d1326ca64f8820cfb3b950 on iopipe:master.

Coverage increased (+0.5%) to 88.119% when pulling a23c0ab725417401cd25207a2a0ef007d5c72bac on ewindisch:promise-cleanup into afb05c117c703875b6d1326ca64f8820cfb3b950 on iopipe:master.

👍  yay smaller functions!


feat: Add bootstrap_extra_args to managed node group submodule

PR o'clock
Description
Add the ability to set bootstrap args for managed node groups
#730
Checklist

[X] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-eks/#doc-generation

something like this is potentially addressed in https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1577
Lets keep this open and I will review both PRs

Similar feature was merged as part of https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1577


About TUM

Thank you for a wonderful paper.
I want to try implementing M2Det. But there are two things I do not know.
TUM has six outputs, how are they handled and entered in the next TUM?
The second one, please tell me more about backbones. What kind of processing is done on backbone? Thanks.

You can leave an email address for me and I send the google drive URL for you.

<EMAIL_ADDRESS>Thank you.


Change icon location to mipmap

As in the title, change the icon location to mipmap vs drawable.  Or provide the option?

I believe only the Launcher icon (ic_launcher) should be in the mipmap folders. I have a hard time finding a case where someone would want to use a single material icon as their launcher icon. Google guidelines say:

It’s best practice to place your app icons in mipmap- folders (not the drawable- folders) because they are used at resolutions different from the device’s current density. For example, an xxxhdpi app icon can be used on the launcher for an xxhdpi device.

For all other icons, they should be placed in their respective drawable folders so that the device picks the right icon for it's display density.

You are right, I misunderstood the reason for the mipmap folder.
On Jul 13, 2015 09:44, "Andy Horner"<EMAIL_ADDRESS>wrote:

I believe only the Launcher icon (ic_launcher) should be in the mipmap
folders. I have a hard time finding a case where someone would want to use
a single material icon as their launcher icon. Google guidelines say:
It’s best practice to place your app icons in mipmap- folders (not the
drawable- folders) because they are used at resolutions different from the
device’s current density. For example, an xxxhdpi app icon can be used on
the launcher for an xxhdpi device.
For all other icons, they should be placed in their respective drawable
folders so that the device picks the right icon for it's display density.
—
Reply to this email directly or view it on GitHub
https://github.com/konifar/android-material-design-icon-generator-plugin/issues/27#issuecomment-120932383
.

I guess this one can be closed then?


[SC] Added unsupported token standard

Proposed changes
Added a description for unsupported token standard.
Reference: https://github.com/klaytn/klaytn/pull/1445
Types of changes
Please put an x in the boxes related to your change.

[ ] Minor Issues and Typos
[ ] Major Content Contribution
[ ] Others

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to reach out. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING GUIDELINES
[ ] I have signed the CLA
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Related issues

Please leave the issue numbers or links related to this PR here.

Further comments
If this is a relatively large content contribution, kick off the discussion by explaining why you would suggest the content contribution, etc...

@aidan-kwon, Okay. I pieced in this content to reference/value-transfer.md file.

Already incorporated into new Klaytn docs which is available after migration.


Fix DropdownItem onClick handler. Add supporting test.

Fixes issue #559

This patch is valid but it turns out that this is insufficient.  DropdownItem's onClick is called after Dropdown's toggle.  The onClick is not actually invoked unless toggle has been changed to prevent closing.

My click processing problem was due to my introduction of ShadowDOM into my project. Since the dropdown event listener is bound to the document its target checking logic was unable to get the information it needed.
I'll update this patch to just contain the test.


Remove hard coded vals for jobs vector. Implement FCFS with queue

@Kablamz Check out the changes made.
Using your code for queuing in FCFS. Also pass value of jobs.txt instead of hard coding.

Pulled down and merged RR with non hard coded FCFS


Missing "Type" property when using C# package AdaptiveCards  version="1.0.0-beta08"

After upgrading the nuget package "AdaptiveCards" to version="1.0.0-beta08" on my C# bot, I've noticed that the "Type" property of the elements AdaptiveOpenUrlAction, AdaptiveSubmitAction and AdaptiveTextBlock
Follows an example o the json object received using directline-js where it's missin the "type" property on the elements inside "body" node (witch in this case are  AdaptiveTextBlock elements
and on "actions" node where I have instaces of AdaptiveOpenUrlAction and AdaptiveSubmitAction
{
  "type": "message",
  "id": "Fm35n3ObmngC64BmrhmP8P|0000006",
  "timestamp": "2017-11-27T17:23:54.5005579Z",
  "localTimestamp": "2017-11-27T17:23:52.7168207+00:00",
  "channelId": "directline",
  "from": {
    "id": "Toro",
    "name": "Toro Assistant"
  },
  "conversation": {
    "id": "Fm35n3ObmngC64BmrhmP8P"
  },
  "membersAdded": [],
  "membersRemoved": [],
  "text": "",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "content": {
        "version": "1.0",
        "body": [
          {
            "text": "Sem problemas, essas coisas acontecem. Vamos resgatar sua senha rapidinho:\r\n\r\n"
          },
          {
            "text": "Se não conseguir ou tiver qualquer problema, é só falar com um de nossos assessores."
          }
        ],
        "actions": [
          {
            "url": "http://www.toroinvestimentos.com.br/esqueciminhasenha",
            "title": "Resgate sua senha"
          },
          {
            "data": "Existe algum custo?",
            "title": "Existe algum custo?"
          },
          {
            "data": "Está demorando para abrir a conta.",
            "title": "Está demorando para abrir a conta."
          },
          {
            "data": "Voltar",
            "title": "Voltar"
          }
        ]
      }
    }
  ],
  "entities": [],
  "replyToId": "Fm35n3ObmngC64BmrhmP8P|0000005"
}

As a workaround I' using this:
var title = item.Extract("[", "]");
var url = item.Extract("(", ")");

var action = new AdaptiveOpenUrlAction
{
    Title = title,
    Url = new Uri(url),
};

///Workaround here
action.AdditionalProperties.Add(new KeyValuePair<string, object>("type", AdaptiveOpenUrlAction.TypeName));

openUrlActions.Add(action);```

Hi @ederbond, thanks for taking the time to report this issue and workaround. We resolved it over the weekend and the fix is in master. A beta09 package will be published today with the fix. Please let us know if you still have issues with the new package!

Thanks @matthidinger, package beta009 is working fine. 👍


Move to npm orgs?

Library Affected:
all
See https://docs.npmjs.com/misc/orgs
I can see the benefit of grouping all the "official" modules under @workbox.
It would also be nice to manage permissions on the organization level, rather than having to manually add all the folks who potentially might need to publish to npm to each individual package.

Drive-by thoughts:

Are there user perceivable benefits or downsides to this change? Is switching to an org mainly for our own reasoning + permissions management needs.

If we want to do this, we should do it for launch imo. It can get confusing for users (or has in other cases) when some of your community articles talk about npm install foo and official docs say npm install @foo/bar. I experienced this quite a bit when Angular made the shift to orgs.

I'm personally not in favor of this because of the mental overhead for developers (i.e. remembering the org name followed by module name: workbox/*)

I don't feel strongly either way—was just throwing it out there.
@gauntface's negative stance means it's worth leaving things un-organiz-ed.

Just for reference, you can use npm orgs without using scoped packages (@workbox/*). I have for example a chalk org to ease permission maintenance, but none of the packages are scoped.

@jeffposnick it's back in the game.
@sindresorhus is it relatively easy to set up / anything we should be aware of?

@sindresorhus Oh super neat. I had no idea the orgs could be used without packages themselves being. With that in mind, I'd be down with us going down that path here.
Totes aside: how did you even come across this issue? :D.

@gauntface The only slight annoyance is that the person that originally published the npm package is the one that has to add it to the org. At least it was like that a month ago.
This is the command you use to add a package to an org:
npm access grant read-write org-name:developers package-name

Totes aside: how did you even come across this issue? :D.

I was bored, so I stalked your recent activity.

We're live with 12 packages owned by the @workboxjs org: https://www.npmjs.com/org/workboxjs


Refactored JSON output to use nlohmann/json

Solves #39. There may be a few small instances of JSON output remaining, but this should be the bulk of it.

main_validator.cpp is the other big one (it generates the json file for the student's results folder "submission.json")
missing files that contain json file writing:
[] main_configure.cpp - generates the json file for each assignment when you install homework
[] main_validator.cpp - generates the JSON file for when student submits an assignment
[*] tokens.cpp - generates the JSON file for testing for blank error files (only time I've seen it generated, I have no idea what's the actual requirements for it to be generated)
Additionally, generally, you don't want to check in commented out code (that's exists in previous revisions). We can easily get to it if we need it for some reason.

Thank you for the feedback, I converted those files.


No Audio button on Web (Safari and Chrome)

The audio button doesn't appear in the web version of my app, when used in mobile browsers

YoutubePlayerController(
      initialVideoId: widget.tutorialVideoArgs!.url!,
      params: YoutubePlayerParams(
          showControls: true,
          autoPlay: true,
          showFullscreenButton: true,
          mute: true,
          desktopMode: true,
          enableCaption: true,
          enableJavaScript: true,
));

Hi, this is a limitation with smaller screens, nothing I can do.


Migrate CI from Travis CI to GitHub Actions

Since June 15th, 2021, the building on travis-ci.org is ceased.
We can migrate to travis-ci.com, but I found this comment from https://github.com/tigrish/devise-i18n/pull/291#issuecomment-794624186.

We're gonna have to move off of Travis as it's no longer free.

This PR migrates CI from Travis CI to GitHub Actions.

Build passes; thanks for this.


Typo in readme

What happened?
Example didn't work
What did you expect to happen?
It to work
Minimal Complete Verifiable Example
import tempfile
from pywbt import whitebox_tools
from pathlib import Path

with tempfile.TemporaryDirectory(dir=".") as work_dir:
    shutil.copy("dem.tif", work_dir)
    wbt_args = {
        "BreachDepressions": ["dem.tif", "--fill_pits", "-o=dem_corr.tif"],
        "D8Pointer": ["-i=dem_corr.tif", "-o=fdir.tif"],
        "D8FlowAccumulation": ["-i=fdir.tif", "--pntr", "-o=d8accum.tif"],
        "ExtractStreams": ["--flow_accum=d8accum.tif", "--threshold=600.0", "-o=streams.tif"],
        "StrahlerStreamOrder": ["--d8_pntr=fdir.tif", "--streams=streams.tif", "-o=strahler.tif"],
    }
    whitebox_tools(wbt_args, work_dir=work_dir)
    shutil.copy(Path(work_dir) / "strahler.tif", "strahler.tif")

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue.
[ ] Complete example — the example is self-contained, including all data and the text of any traceback.
[ ] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output
CalledProcessError: Command '['WBT\\whitebox_tools.exe', '--run=BreachDepressions', '--wd=tmpumdyrc8h', '--compress_rasters=false', '--max_procs=-1', 'elevation.tif', '--fill_pits', '-o=dem_corr.tif']' returned non-zero exit status 101.

RuntimeError: thread 'main' panicked at whitebox-raster\src\lib.rs:1361:69:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Anything else we need to know?
Fix by changing -i=dem.tif in the BreachDepressions args, rather than just dem.tif
Environment

async-retriever        0.17.0
pygeoogc               0.17.0
pygeoutils             0.17.0
py3dep                 0.17.0
pynhd                  N/A
pygridmet              N/A
pydaymet               N/A
hydrosignatures        N/A
pynldas2               N/A
pygeohydro             N/A
aiohttp                3.10.5
aiohttp-client-cache   0.11.1
aiosqlite              0.20.0
cytoolz                0.12.3
ujson                  5.10.0
defusedxml             0.7.1
joblib                 1.4.2
multidict              6.0.5
owslib                 0.31.0
pyproj                 3.6.1
requests               2.32.3
requests-cache         1.2.1
shapely                2.0.5
url-normalize          1.4.3
urllib3                2.2.2
yarl                   1.9.4
geopandas              1.0.1
netcdf4                1.7.1.post1
numpy                  1.26.4
rasterio               1.3.10
rioxarray              0.16.0
scipy                  1.14.0
xarray                 2024.6.0
click                  8.1.7
pyflwdir               0.5.8
networkx               3.3
pyarrow                16.1.0
folium                 N/A
h5netcdf               1.3.0
matplotlib             3.9.2
pandas                 2.2.2
numba                  0.60.0
bottleneck             N/A
py7zr                  N/A
pyogrio                0.9.0

Thanks for reporting the issue! Just fixed it. BTW, a new version has been released with breaking changes that streamlines running the function even more!


Support full object definitions for valid values in schema

Currently, valid values (i.e., enums) for objects in the schema are written as lists. However, in some cases, we also want to have each value defined, and perhaps even summarized in a separate table. As an example, take the channels file for MEG data. Each of the valid values for the type column has a description, which is currently rendered  with a hardcoded table, but which could be incorporated into the schema directly.

As an example, here's this idea applied to the "volume_type" column for ASL context files:
volume_type:
  name: volume_type
  description: |
    The `*_aslcontext.tsv` table consists of a single column of labels identifying
    the `volume_type` of each volume in the corresponding `*_asl.nii[.gz]` file.
  type: string
  enum:
  - control:
      name: Control Image
      description: |
        The control image is acquired in the exact same way as the label image,
        except that the magnetization of the blood flowing into the imaging region has not been inverted.
  - label:
      name: Label Image
      description: |
        The label image is acquired in the exact same way as the control image,
        except that the blood magnetization flowing into the imaging region has been inverted.
  - m0scan:
      name: M0 Image
      description: |
        The M0 image is a calibration image, used to estimate the equilibrium magnetization of blood.
  - deltam:
      name: deltaM Image
      description: |
        The deltaM image is a perfusion-weighted image, obtained by the subtraction of `control` - `label`.
  - cbf:
      name: Cerebral Blood Flow Image
      description: |
        The cerebral blood flow (CBF) image is produced by dividing the deltaM by the M0,
        quantified into `mL/100g/min` (See also [doi:10.1002/mrm.25197](https://doi.org/10.1002/mrm.25197))


drivers: spi: gd32: support interrupt-driven mode

Add supporting interrupt-based asynchronous operation for GD32 SPI.
Signed-off-by: TOKITA Hiroshi<EMAIL_ADDRESS>

@soburi Please help to add this two state check, It will help to improve the transfer stability. Thanks!
diff --git a/drivers/spi/spi_gd32.c b/drivers/spi/spi_gd32.c
index 5a5b18b41e..14baf1db52 100644
--- a/drivers/spi/spi_gd32.c
+++ b/drivers/spi/spi_gd32.c
@@ -161,6 +161,10 @@ static int spi_gd32_frame_exchange(const struct device *dev)
 	struct spi_context *ctx = &data->ctx;
 	uint16_t tx_frame = 0U, rx_frame = 0U;

+	while ((SPI_STAT(cfg->reg) & SPI_STAT_TBE) == 0) {
+		/* NOP */
+	}
+
 	if (SPI_WORD_SIZE_GET(ctx->config->operation) == 8) {
 		if (spi_context_tx_buf_on(ctx)) {
 			tx_frame = UNALIGNED_GET((uint8_t *)(data->ctx.tx_buf));
@@ -242,6 +246,10 @@ static int spi_gd32_transceive_impl(const struct device *dev,
 #endif
 #endif

+	while (SPI_STAT(cfg->reg) & SPI_STAT_TRANS) {
+		/* Wait until last frame transfer complete. */
+	}
+
 	spi_context_cs_control(&data->ctx, false);

 	SPI_CTL0(cfg->reg) &= ~SPI_CTL0_SPIEN;
--
2.34.1

@soburi There have a CI failure, cause by others. Maybe a rebase from main branch can fix it.

@cameled

@soburi There have a CI failure, cause by others. Maybe a rebase from main branch can fix it.

Rebase done, and Fix CI failure. Thanks for notify.


Question on extending codebase to new CSP instances

Hi,
I want to start by thanking you for making your source code public and for a well-written paper that I found fairly impressive and novel (especially the constraint value graph modelling)! I want to try and use your approach to solve a CSP that models an important math problem regarding fast matrix multiplication algorithms. I have played around a bit with the codebase but wanted to ask a few questions before delving deep into this idea.
Here is some background of the CSP that I want to solve ( also presented in this recent paper https://arxiv.org/abs/2306.01097 )

Variables: three sets of variables (all with domain {-1,0,1}) defined by matrices U, V and W (i.e the variables of the CSP are the entries in the U,V,W matrices).
Constraints: The CSP only has constraints of the form   U_i,j * V_i,j *W_i,j = a where a is known value in {0,1}  i.e multiplication of three variables that equals to 0 or 1
Objective: None, pure constraint satisfaction

Given that this CSP does not have linear constraints (because of the multiplication of three variables), would ANYCSP be a suitable approach for this CSP or could this be an issue (perhaps with the "re-labelling" process for edges in the constraint value graph)?
Additionally, where should I start if I wanted to extend the source code to my new CSP problem? I assume I need to modify the CSP_Data class and Constraint_Data classes to handle the non-linear constraints, is this correct?
Thank you,
Arnaud Deza

Hello Arnaud,
we greatly appreciate the interest in our work.
This seems like a CSP that ANYCSP is suited for.
Do you have an estimate for how many variables and constraints these instances have?
Training is only feasible for up to a few thousand constraints per instance, although during evaluation ANYCSP can handle much more.
To model these instances as CSP for our code I suggest you use the XCSP format (https://www.xcsp.org/) and model the constraints as "extension" constraints. These simply list the allowed or disallowed value combinations for each constraint. If the domain size and arity is always three this should be feasible and is by far the simplest way to get instances into ANYCSP.
For an example of this file format you can check out the Model RB and Coloring instances we provide on google drive.
Regards,
Jan


Fix friendly name not being set & error w/ empty string

In order to retain the friendly name on fresh registrations, check the workflowActivity.FriendlyName. Also added emtpy string check as that isn't allowed - multiple empty spaces are OK though - go figure

Published in https://www.nuget.org/packages/spkl/<IP_ADDRESS>


Change SalesChannelContext to extend Context

1. Why is this change necessary?

The SalesChannelContext is currently its own object based only on the Context through the context property field.
Several methods are currently duplicated in the SalesChannelContext just to allow easier access to the Context's methods.
In many places where the Context is needed, if we have the SalesChannelContext but need the underlying Context, we have to use $salesChannelContext->getContext() to access it.
The PR changes the SalesChannelContext to extend the Context, which provides all the Context properties and allows us to use the SalesChannelContext directly in places where we previously needed $salesChannelContext->getContext(), since we can now just write $salesChannelContext.

2. What does this change do, exactly?

Changed Shopware\Core\System\SalesChannel\SalesChannelContext to now extend Shopware\Core\Framework\Context instead of using use the Context as a field
Removed duplicate methods from Shopware\Core\System\SalesChannel\SalesChannelContext which are now directly provided by the extended Shopware\Core\Framework\Context

3. Describe each step to reproduce the issue or behaviour.

/

4. Please link to the relevant issues (if any).

/

5. Checklist

[X] I have rebased my changes to remove merge conflicts
[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
[X] 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 fulfill them.

hey @akf-bw
thanks again for your contribution!
Looking at the changed files, you can already see how profound your change is. While we can see the benefits of the SalesChannelContext really extending the Context and not only having it as property, we on the other hand also fear, that this could be misused. Means, this could lead to unexpected side effects, if the the whole SalesChannelContext is passed into the depth of the system.
The idea of the Context is, that we have the minimal needed data for the DAL to operate. On the other side, the SalesChannelContext contains much more information, which should be globally available, while acting as customer in the Storefront.
Happy do discuss this further :slightly_smiling_face:

The idea of the Context is, that we have the minimal needed data for the DAL to operate.

The DAL part of the core components already uses a another abstraction of the context, the WriteContext (which handels everything around the DAL), which uses the context as a property and is not affected by this PR change.
So I don't thing this would have any effect on the internals of the Shopware core.

Means, this could lead to unexpected side effects, if the the whole SalesChannelContext is passed into the depth of the system.

What kind of side effects and where do you have this in mind?

I see much more advantages here due to the simpler use and the removal of duplicate methods. Currently, some methods only exist on the context and not on the SalesChannelContext, which is why sometimes one has to be accessed and sometimes the other.

@mitelg The tests are now all successful again.
I also improved the Generator::createSalesChannelContext to remove a lot of useless code from many test classes. This change allowed me to delete many lines in test files in this PR while maintaining / improving the usability of tests using the SalesChannelContext.

thanks for the work @akf-bw it is really appreciated!
The DAL was just an example how deep the context is passed through.

So I don't think this would have any effect on the internals of the Shopware core.

What kind of side effects and where do you have them in mind?

that is the problem we have with the change :slightly_smiling_face: We do not really know which impact and implications it has.
Right now we have a pretty strict line between "this only works in sales channel context" and "this works everywhere". We would pretty much weaken that distinction. We also think it can get really complicated over time, if stuff only requires a normal context, but suddenly behaves differently if a SalesChannelContext is passed.

We also think it can get really complicated over time, if stuff only requires a normal context, but suddenly behaves differently if a SalesChannelContext is passed.

There should be no problem if a SalesChannelContext is passed as the SalesChannelContext (after the PR change) does not behave differently in its methods or fields which are contained in the normal context, because the SalesChannelContext methods would now just be the exposed methods of the extended context.
The only difference these two context classes would have after the PR change would be the amount of information contained.
Any possible side effects that would be set on the SalesChannelContext via a method such as "setTaxState" would, as before, only affect the Context, since the method is only contained in the Context part of the class.

hey @akf-bw and also @aragon999
thanks for taking part in the discussion and also directly implementing feedback :ok_hand:
Nevertheless, we are still leaning towards declining your proposed change. Beside the already mentioned concerns we would like to stick with the Composition over inheritance principle in this case


[BUG] move button not work in production version

Describe the Bug
In move token page, when click move button, there is no response.

Expected experience
The performance should be same as dev version.
Steps To Reproduce

Go to previewnet.
Go to flow token page.
Go to move token page.
input move token amount
click move button

Environment
-ios prod version:1.0.0(15)

The move button works well now in ios prod version 1.0.0(17)
https://github.com/Outblock/FRW-iOS/assets/87978227/38da8186-f418-456b-86c6-20dd50f6248d
.
The demo video attched below.


fix(directionality): complete dir change observable

Since it's most likely to use the Dir.change observable programmatically, rather than through an event binding, we should complete it in order to ensure that everything is cleaned up.

Please check lint errors

Sorted out the lint warning.


Unsolicited refactor of FlatList.getItem

Summary
This should be the same, but I think it is prettier.
.filter(item => item != null) might be simply .filter(item => item), but this looks to be intentional for handling when the item is the empty string '' from a90d0e3614c467c33cf85bcbe65be71903d5aecc
Changelog
[Internal][Changed] - Refactored FlatList getItem.
Test Plan

Existing test cases still pass
Benchmarked performance characteristics with Node 16.13.2 on an M1/arm64 (https://gist.github.com/philihp/1c821a7f1bd3056c0256e055a60967b1)

testFiltery x 4,707,602 ops/sec ±0.13% (99 runs sampled)
testControl x 4,707,246 ops/sec ±0.10% (95 runs sampled)

notice me, senpai

Hey @philihp, thanks for this PR. @yungsters brought up some good points that this change doesn't seem obviously easier to read and it also allocates an additional array (one for slice, one for filter). FlatList._getItem() is a relatively hot path so memory concerns are extra important here.

@charlesbdudley @yungsters word up. As the maintainers of the code, I can respect your preference for the existing imperative code.


Update documentation to clarify when to use --jit

I'm going to merge this PR, as it only involves documentation changes.


Mirror Distributed Strategy

I'm facing issues when I tried to run model using mirror distributed strategy.
I want to run multiples model one by one in a loop using distributed strategy. First model runs well but is shows error before start the next model.
Collective ops is aborted by: Shape mismatch in the collective instance 100. Op at device /job:localhost/replica:0/task:0/device:GPU:2 expected shape [28678440] but another member in the group expected shape [39166184]. This is likely due to different input shapes at different members of the collective op.
The error could be from a previous operation. Restart your program to reset.
	 [[{{node CollectiveReduceV2_2}}]] [Op:__inference_train_function_51026]

Here is my code-

strategy = tf.distribute.MirroredStrategy()
# Set up model within scope
with strategy.scope():

    model = Create_model()

    optimizer = SGD(learning_rate=0.01, weight_decay=1e-4,momentum=0.9)
    model.compile(loss='sparse_categorical_crossentropy', optimizer=optimizer, metrics=['sparse_categorical_accuracy','sparse_top_k_categorical_accuracy'])

checkpoint = ModelCheckpoint('Best_model.h5',
                          monitor='val_loss',
                          save_best_only=True,
                          mode='min',
                          verbose=0)
lr_reduce = ReduceLROnPlateau(
    monitor='val_loss',
    factor=0.1,
    patience=5,
    verbose=0,
    mode='min',
    )

model.fit(train_generator,validation_data=valid_generator,steps_per_epoch=len(train_generator),\
    validation_steps=len(valid_generator), epochs = 50,\
    callbacks=[checkpoint,lr_reduce], verbose=1
    )

Hi @hafizuriu ,
In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here and version also.
Thank you!

I'm using tensorflow version 2.14

Hi @hafizuriu ,
In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here.
Thank you!


API Gateways dropdown box does not adjust to text size

Description:
When I added the following code in the <API-M_HOME>/repository/conf/api-manager.xml file I noticed that the dropdown box had a fixed length and did not adjust based on the size of the Environment name. It will be better if the "API Gateways" dropdown box can adjust to the text as required.
<Environment type="production" api-console="true">       			<Name>Production Gateway</Name>       			<Description>Production Gateway Environment</Description>       			<ServerURL>https://localhost:9444/services/</ServerURL>       			<Username>admin</Username>       			<Password>admin</Password>       			<GatewayEndpoint>http://localhost:8281,https://localhost:8244</GatewayEndpoint>    		</Environment>    		<Environment type="hybrid" api-console="true">       			<Name>Production and Sandbox Gateway</Name>       			<Description>Hybrid Gateway Environment</Description>       			<ServerURL>https://localhost:9445/services/</ServerURL>       			<Username>admin</Username>       			<Password>admin</Password>       			<GatewayEndpoint>http://localhost:8282,https://localhost:8245</GatewayEndpoint>    		</Environment>
Suggested Labels:
Suggested Assignees:
Thilini Shanika
Affected Product Version:
APIM 2.5.0 RC 4=GA
OS, DB, other environment details and versions:
Mac OS, Safari
Steps to reproduce:
Related Issues:

This issue is addressed with 3.x product.


Add Campbell County Schools

@sanelson2000 Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


build(ios): podspec file name and s.name needs to be same as library name

for ios, podspec file name and s.name needs to be same as library name, otherwise pod install will fail, giving error can't find get_video_thumbnail

Hello, I am a newbie. The package works great on the web, but I am running into this issue on iOS when running "pod install" command:
[!] No podspec found for get_thumbnail_video in .symlinks/plugins/get_thumbnail_video/ios" Is there a workaround?
Is there a workaround for iOS? Do I need to modify Podfile in any ways? Would somebody advise please...

this fixes that, you can just point your pubspec.yaml to my repo in the mean time
get_thumbnail_video: # ^0.6.1
    git:
      url: https://github.com/agufagit/video_thumbnail
      ref: master

@agufagit thank you kindly! The fix above worked, and I can build on iOS now! I just wanted to make sure I understand the process... Is it possible to deploy in this way to PROD (on Apple App Store), or will this not work for deployment? Or is it not advisable?

yes, it's the same process.

You download packages from pub.dev, you download git repo from github
you build your product
you release your product

Is something missing to get this merged?

sttill facing issue to run on ios , version 0.6.1 , any update about this issue.

@agufagit Any chance you're interested in forking and taking over? It seems like @Alberto-Monteiro might be done with it. No responses, no merges, etc.

it looks like this repo is maintaining it, https://github.com/Andrew-Bekhiet/video_thumbnail

If you have problem with android conflicting with old video_thumbnail package(for example if you are using get_stream package), temporary u can grab:
  get_thumbnail_video:
    git:
      url: https://github.com/followthemoney1/video_thumbnail
      ref: dev_d


Social icons are linking wrong

I have replaced the line in footer.hbs with:
< a class="social__icon social__icon--fb" href="www.facebook.com/myprofilename/">Facebook
(intentional space added at <a)
But the issue is, the icon on the website is linking it to: www.myblogaddress.com/www.facebook.com/myprofilename/
instead of just
www.facebook.com/myprofilename/

You need to include http:// before the link otherwise it does what you are seeing. This is how the href attribute works in HTML and is not something associated with the them or blog platform.
Change your link to the following and it should work fine:
< a class="social__icon social__icon--fb" href="http://www.facebook.com/myprofilename/">Facebook</a>

Oh yeah :( .


Missing images in tutorial 12

For the jupyter notebook named "tutorial12_bottlenecks", I can't find the images used in the 1st cell, there are named "bottleneck.png" and "capacity_curve.png", it was report in #770

Actually, it is not only the 1st cell but also all the other cells where images are referenced

It's a fact that three years later, there are still no pictures available today🤣


63: Patching for userspace breakage.

The kernel patch by<EMAIL_ADDRESS>in kernel hash 47894e0f changed the ioctl return for SNP_GET_EXT_REPORT to succeed instead of returning an error when encountering an invalid certificate length. This was done to keep the cryptography safe. Because of this, any kernel before this hash (5.19, etc) is broken, and we need to patch the way the API handles the error response.
resolves: #63
EDIT 2023-02-21
Adding Links for Context:

LKML Discussion and PR
Github Context

@larrydewey Hm. Only keeping for kernels before 47894e0f? How do we go about this? Is somebody supposed to remove this for kernels after 47894e0f?

It is an error check which is only needed for kernels running before that hash was up-streamed; which happened in kernel v6.1. So everything between v5.19.[0-17] - v6.0.[0-19] will need the error check, but >= v6.1 removes the error code response. We talked briefly about it on a call, but I have run through the kernel versions to isolate that it wasn't merged until exactly 6.1


Updated the meshkit error in mesh_ops_handler

Signed-off-by: sayantan1413<EMAIL_ADDRESS>Description
Updated the meshkit error for mesh_ops_handler
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #3373 (878fd12) into master (05cda78) will decrease coverage by 0.75%.
The diff coverage is 0.31%.

@@            Coverage Diff            @@
##           master   #3373      +/-   ##
=========================================
- Coverage    7.02%   6.27%   -0.76%
=========================================
  Files          23      35      +12
  Lines        1409    2743    +1334
=========================================
+ Hits           99     172      +73
- Misses       1303    2549    +1246
- Partials        7      22      +15

Flag
Coverage Δ

integrationtests
?

unittests
6.27% <0.31%> (-0.76%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/config/config.go
1.11% <0.00%> (-1.12%)
:arrow_down:

mesheryctl/internal/cli/root/perf/perf.go
50.00% <ø> (ø)

mesheryctl/internal/cli/root/system/check.go
1.94% <0.00%> (ø)

mesheryctl/internal/cli/root/system/start.go
1.53% <0.00%> (-0.01%)
:arrow_down:

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (ø)

mesheryctl/internal/cli/root/system/stop.go
1.08% <0.00%> (-0.07%)
:arrow_down:

mesheryctl/pkg/utils/auth.go
0.00% <0.00%> (ø)

mesheryctl/pkg/utils/error.go
0.00% <0.00%> (ø)

mesheryctl/pkg/utils/formatter.go
0.00% <0.00%> (ø)

mesheryctl/pkg/utils/healthcheck.go
18.75% <0.00%> (ø)

... and 16 more

Continue to review full report at Codecov.

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


Using sets does not work

I'm using the transformers with import '..._serialization_rules.dart'. I'm not supplying a format field to the Serialization constructor to use the default.
Lists and Maps are serialized just fine. Sets aren't. I get the below stacktrace when trying to serialize an object that has a Set.
Exception: Uncaught Error: Unsupported operation: Attempted to serialize type without a defined rule {}. This is not supported in basic serialization, either define a rule for this type or use serialization_mirrors
Stack Trace:
#0      Serialization.addRuleFor (package:serialization/serialization.dart:309:6)
#1      Serialization.rulesFor (package:serialization/serialization.dart:426:34)
#2      Writer._process (package:serialization/src/reader_writer.dart:109:48)
#3      Trace.traceAll (package:serialization/src/reader_writer.dart:536:47)
#4      Writer.write (package:serialization/src/reader_writer.dart:76:19)
#5      Serialization.write (package:serialization/serialization.dart:353:35)

Any suggestions?

Like the error says, there isn't a rule for Set and you're using the non-mirror version, so it can't just define one. It would not be unreasonable for the basic system to define a rule for Set.
To define your own, a reasonable one would be something like
class SetRule extends CustomRule {
appliesTo(x) => x is Set;
getState(x) => x.toList();
create(state) => new Set();
setState(obj, state) => obj.addAll(state);
}

This rule worked just fine, thank you. It's just that Maps and Lists working made me expect Sets to work as well. Thanks!


Fix Wizard not using latest step values on rerenders

If you use the Wizard inside of a component that re-renders and passes in new step values, the new step values will not be respected.
For example, a basic component like this won't work at all. The input's value prop will be locked as the empty string (because Wizard forever remembers the value of first from the initial render) so the input won't be editable.
function NameWizard(props) {
  const [name, setName] = useState('');
  return (
    <Wizard
      initial="first"
      first={({next}) =>

          <input type="text" value={name} onChange={e => setName(e.target.value)} />
          <button onClick={next}>Next</button>

      }
      second={() =>

Hi {name}

      }
    />
  );
}

This is because componentsRef is stored inside of a Map that's calculated on the initial render only inside of a useRef call:
  const componentsRef = React.useRef(
    new Map(stepsList.map((key) => [key, props[key]] as const))
  );

Changing the useRef call to a useMemo call so that it's re-calculated whenever stepsList is updated fixes this:
  const componentsRef = React.useMemo(
    () => new Map(stepsList.map((key) => [key, props[key]] as const)),
    [stepsList]
  );

Once this is fixed, a new issue pops up: whenever a component using Wizard re-renders and passes in new step values, the steps are entirely remounted as new components, causing all state inside of them to be lost and for brand new DOM nodes to be created (losing any uncontrolled component/DOM state including scroll position, text highlighting, focus, etc).
This happens because the step prop values are being used as components (return (<Component ... />); where Component is a dynamic value like a prop that doesn't necessarily have a stable value), which will be entirely remounted if a new value is passed in. The render-props pattern (return renderStep({ ... });) avoids this issue and should almost always be used rather than accepting components as props. The API for users of Wizard is still basically identical (the typescript types are slightly different) and all of the documented examples of Wizard will still keep working as-is.

This PR fixes both issues and also adds tests for each of them.

Initially, this was exclusively used with the thought of each step being a static react component, but I like this because it allows for a shared state, so, I will take a look and if it's good to go, I will merge and publish a new version. Thank you!


more information

it would be helpful if we could include information for low production (hard to find) parts..
for example: where would someone source the low profile adhesive foam from?
re: https://github.com/foostan/crkbd/blob/master/corne-light/doc/v2/buildguide_low_edition_en.md#parts

Also why is it written in the requirements about the plate and the bottom part, if in this case they are not used? Or are they still needed?

And can I use plates for the standard Corne or do I need another plate for the low edition?

And can I use plates for the standard Corne or do I need different plate for the low edition?

@Eloren1 the only specific for the plates for a low profile choc build is that they should be 1.2-1.5mm thick.

Based on some reddit comments and personal research, I'm leaning towards a soft silicone or polyurethane foam, and intuitively, I'm thinking open-cell foams will conform to the diodes / switch prongs.
In the photos, the foam appears to be about the same thickness as the PCB which is ~1.6mm or ~1/16". I measured the diodes on one of my boards and they sit about 1.15mm high. The leads from the pro-micro are ~1.3mm high.
I've got a few silicone foam samples on order and will post back if they seem to fit the bill, but it would be great if @foostan can quickly weigh in on this :).

This form is this https://jp.misumi-ec.com/vona2/detail/110300286150/?HissuCode=PRGCS3-400-300
Sorry, I have information about Japanese store only.

Ok, so it's 3mm thick rubber foam (easily found it on AliExpress)

Thanks @foostan!
And for others, The MiSUMi appears to have other distribution centers globally as well. Here's a link to the same product on their US site:
https://us.misumi-ec.com/vona2/detail/110300286150/?HissuCode=PRGCS3-400-300&PNSearch=PRGCS3-400-300&searchFlow=results2type&KWSearch=PRGCS3-400-300
Just ordered some and it looks like it will get shipped from California.

Thank you for your information!


Black

This PR enables black, the opinionated, uncompromising code formatter.
It's a good thing, and I've bought into the hype. Needless to say, so have many other leading scientific python packages, such as dask, xarray, and pandas. If you need more convincing,

take a read of Matt Laymans blog
or try out the interactive black playground
or find out more @ psf/black

... and it even has editor and IDE integration support :grinning:
This PR also incorporates support for pre-commit git hooks, which when enabled will allow the developer to ensure that all iris code in the repository is black compliant, by automatically executing black whenever a git commit command is performed. Note that, the pre-commit hooks run only against the code changed/new to the PR, and not over the whole iris repository - so it's not an expensive act.
In addition to enabling the black pre-commit git hook, other hooks I've deemed useful have also been enabled. For a list of supported hooks, see here.
Note that, black is also now part of our travis-ci workflow, to ensure that developers are actually committing black compliant code as part of their PR.

Still to do...

[ ] black format docs.
[ ] black format tests.
[x] decide whether it's sensible for stickler-ci at v18.9b0 to also perform black checks - we're targeting v19.10b0.

drop it, the stickler-ci version is too old

[x] decide whether to disable stickler-ci

disable it, adopt flake8 pre-commit hook instead

[ ] tidy/drop iris.tests.test_coding_standards.TestCodeFormat and iris.tests.test_coding_standards.StandardReportWithExclusions.
[ ] review the .flake8 files that we explicitlyexclude.
[ ] make the code base flake8 compliant (perhaps in a follow-up PR).
[ ] update .github/CONTRIBUTING.md and/or developer notes to provide relevant pre-commit configuration details.

I couldn't find a .stickler.yml file in this repository. I can make one for you, or you can create one by following the documentation.

I couldn't find a .stickler.yml file in this repository. I can make one for you, or you can create one by following the documentation.


ES6 support

Hello, do you plan ES6 support?
If you will apply code transformer - I can hook into it with BabelJS

ES6 support is natively implemented in JDK9: https://bugs.openjdk.java.net/browse/JDK-8066046
You could try to install that version of Java, and see if it works.

I'm on the list of notifications for OpenJDK issues. Based on what I've seen, I don't think 1.9 will be used in general production for a while. It's just not mature enough. Most people are still considering migration from 1.7 to 1.8 or learning the nuances of 1.8. So my vote for now would be to hold on support for 1.9. It's just not necessary to jump into that pool of dirty water yet.

FYI : v1.7 is dead. v1.9 isn't here yet. So I'm building with JDK 1.8.141+
I'm also transitioning the code to be Nashorn-specific, rather than getting a generic "javascript" engine.

You can code with ES6 using this: https://blog.magikcraft.io/how-to-mod-minecraft-without-java-f076ddaec01c
Including executing ES6/TypeScript at the server console.


Add "whats new"

Show the "whats new" information from Gemma in Gembrow

Possibly this can be moved to be on the home page rather than taking up space on the GemBrow interface.

Good. We'll eventually port the homepage to GemBrow and make those statistics available from the REST API.


Compression tests do not work in CI only

When running under CI tests that use Apple's Compression framework cause a complete crash of the test run.

Fixed by #1


The missing link

You're saying that because the link is used by many other articles, it's not needed here. That logic assumes a reader lands on this page when reading a series of articles. But most developers I know will land on this page via search. On the web, context is fluid.

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

ID: d678cb66-3b9e-3ade-fe25-15957b6b2537
Version Independent ID: 76e7e206-4da3-f543-8766-d157eb57c03e
Content: If Condition activity in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/control-flow-if-condition-activity.md
Service: data-factory
GitHub Login: @djpmsft
Microsoft Alias: daperlov

@sartoris . Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .
Cam I request you to please elaborate a bit more on "You're saying that because the link is used by many other articles" ?

I thought I was adding to this issue - not creating a new one:
https://github.com/MicrosoftDocs/azure-docs/issues/54938
On Sat, Sep 5, 2020 at 7:51 AM himanshusinha-msft<EMAIL_ADDRESS>wrote:

@sartoris https://github.com/sartoris . Thanks for the feedback and
bringing this to our notice . At this time we are reviewing the feedback
and will update the document as appropriate .
Cam I request you to please elaborate a bit more on "You're saying that
because the link is used by many other articles" ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/62153#issuecomment-687621525,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2NVV3G2SR7EJY5JDY5EV3SEJGA3ANCNFSM4Q27KIJA
.

Thanks @sartoris  for clarifying that . I am going ahead and closing the issue for now . You can always re-open the issue if you think that appropriate .


Warn users when a new session is opened while working in an current active session

Is your feature request related to a problem?
I see that VAPOR auto saves the current session. However, I would expect the software to warn the me when I attempt to open a new session while already working in an existing session.
Describe the solution you'd like.
I accidentally opened a new session and VAPOR opened one without any prompts. Unfortunately, the auto save did not capture all my changes. A simple warning pop-up when someone opens a new session would have prevented this.
Impact
(Please click check boxes AFTER submitting ticket)

[X] High - User productivity significantly improved
[ ] Medium - User productivity partially improved
[ ] Low - User productivity trivially improved

Vapor already does this but it is disabled for debug builds.

Yes! I see it. I was using the application built from source previously. Thanks!

Yes! I see it. I was using the application built from source previously. Thanks!


UNSAT in Uberon

causing the build and TG to fail
cc @hattrill

There seems to have been changes made in Oberon that are not yet reflected in GO, e.g.:
In GO; reproductive structure is equivalent to 'anatomical structure'
and ('part of' some 'reproductive system')
In Uberon,  reproductive structure is equivalent to 'multicellular anatomical structure'
and ('part of' some 'reproductive system')

Fixed in r38696

Thanks Chris!


-Y flag is applied inconsistently between bash and C tests

The C app correctly only applies the -Y flag to the mdtest write phases, while the io500_fixed.sh script applies it to all phases of mdtest, which skews the results (at least for certain filesystems) away from the SC19 results.
I believe this is the section of io500_fixed.sh that is incorrect:
183   params_md_easy="-F -P -Y -d $io500_workdir/mdt_easy -n $io500_mdtest_easy_files_per_proc $io500_mdt    est_easy_params -x $io500_workdir/mdt_easy-stonewall -N 1" 184   result_file=$io500_result_dir/$phase.txt
I believe that the -Y flag should be added in the if [[ "$1" == "write ]]; then section in order to maintain consistency with SC19 testing and the C app.
The mdtest_hard section has the same issue.

This is fixed in io-500-dev commit 3de4e2d795 to remove the -Y flag from the read phases, which was unintentional.


Parsing of definition.json in spk infra generate

As a:
Developer
I want:
I want to be able to go through end-to-end to generate of an spk infra generate.
So that:
I can generate Terraform files for a cluster based on a local environment source template.
Describe the solution you'd like:
End-to-End (Iteration I)
Upon generation, spk infra generate (e.g. spk infra generate west)should:

[ ] Verify definition.json in the project folder
[ ] Verify the tag is reflective of the current local repo
[ ] Check the path to the environment template is valid
[ ] mkdir generated & copy files from an environment template
[ ]  Parse the definition.json file to retrieve the inputs and create a spk.tfvar

Acceptance Criteria:
spk infra generate should be able to go end to end with implementation.
Does this require updates to documentation?:
Yes

After caling spk infra generate with args for the terraform repo and repo version we look at the definition.json file in the spk-template-repo
spk-template-repo
    |- definition.json

In the definition.json we find information about the version of the terraform repo and validate that local git repository. Next we created a spk-template-repo-generated directory that is a sibling to spk-template-repo
spk-template-repo
    |- definition.json
spk-template-repo-generated/

Next, we look copy over items from the terraform repo into the spk-template-repo-generated directory.
Our code will generate the spk.tfvars file by evaluating what is inside definition.json
spk-template-repo
    |- definition.json
spk-template-repo-generated/
     |- main.tf
     |- variables.tf
     |- spk.tfvars (generated by SPK infra generate)

@NathanielRose correct?

@andrebriggs Correct, Adding to issue as well.


No devices in Devices list

Thanks for your work! Just trying out the WIP. Is it my configuration problem or is a bigger problem?
I do not get to see any devices on devices list. I tried with wildcard and by specifying ID-s. Device is being tracked nicely by Home Assistant mqtt_room sensor when I configure by ID. On MQTT companion is online. Also I see devices updating on MQTT espresense/devices/#
I have the following config.

# MQTT Connection, if empty will query and use hassio provided mqtt
mqtt:

# How long before device considered stale
timeout: 30
# How long before device is considered away
away_timeout: 120

# Floors w/ the points to draw it in meters
floors:
  - id: first
    name: First Floor
  # Bounds (x,y,z) of map in meters
    bounds: [[-20, -20, -20], [20, 20,20]]
    rooms:
      - name: Labor
        points:
          - [0, 0]
          - [13.983, 0]
          - [13.983, 4.974]
          - [0,4.974]

# Locations of espresense nodes in meters
nodes:
  - name: pre2
    point: [13.983, 4.974, 2.6]
    floors: ["first"]
  - name: pre1
    point: [0, 4.974, 2.6]
    floors: ["first"]
  - name: pre3
    point: [13.983, 0, 2.2]
    floors: ["first"]

# Devices to track
devices:
  - id: "*"
  - id: "f6affb4f354f"
    name: "Beacon1"

Log:
[14:47:20 INF] Loading /config/espresense/config.yaml
[14:47:22 WRN] Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
[14:47:22 INF] Executing Query: pragma table_info("DeviceHistory")
[14:47:22 INF] Executing: create  index if not exists "IX_DeviceHistory_When" on "DeviceHistory"("When")
[14:47:22 INF] Executing: DROP TRIGGER IF EXISTS DeviceHistory_RollingData;
[14:47:22 INF] Executing: CREATE TRIGGER DeviceHistory_RollingData AFTER INSERT ON DeviceHistory
   BEGIN
     DELETE FROM DeviceHistory WHERE `When` <= (NEW.`When`-1296000000000);
   END;
[14:47:22 WRN] No XML encryptor configured. Key {3c0d68w2-4919-4b3b-ae6b-ebb6c3b00css} may be persisted to storage in unencrypted form.
[14:47:22 INF] Now listening on: http://[::]:8267
[14:47:22 INF] Application started. Press Ctrl+C to shut down.
[14:47:22 INF] Hosting environment: Production
[14:47:22 INF] Content root path: /App
[14:47:23 INF] Connecting to mqtt server at core-mosquitto:1883...
[14:47:23 INF] Connecting to mqtt server at core-mosquitto:1883...
[14:47:23 INF] MQTT connected {"primary": true}
[14:47:23 INF] MQTT connected {"primary": false}

I believe this is fixed!


Nodehun not compatible with node 0.12 and iojs

I can't seem to build nodehun on node 0.12 and iojs.
I'm guessing this is because of an updated V8?

Yeah, I'll be getting to this soon (hopefully this weekend or next).

this is done

Cool. I don't mean to offend in any way, but have you considered using https://github.com/rvagg/nan for abstracting the differences between versions?
Right now it's hard to depend on this project because basically we will be forced to follow the same scheme as you, requiring a given version of node for a given version of our modules.

This is a not to myself:
https://github.com/rvagg/nan/blob/master/nan.h
I'm going to use node_version.h to build the two different versions based on using ifdef pragmas in the compiler.

I'm not using NAN, but users shouldn't have to worry about versions anymore

Thanks Nathan, that's great! Thank you for your hard work 👍


Add elbhiruni file

created a branch, created a file and made a commit, and opened a pull request

Good


Feature/subscribe to new study created gdev 366

Title for squash and merge:
Subscribe to new-study-created message (GDEV-366, GDEV-284)

Description for squash and merge:
Subscribed to new-study-created message
Extract file information from message
Write file information to upload-controller database

template_repo needs to adapt the copyright year, then static files won't fail

Tests will be added in a future PR

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@94262e6). Click here to learn what that means.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##             dev       #2   +/-   ##
======================================
  Coverage       ?   14.19%
======================================
  Files          ?       16
  Lines          ?      155
  Branches       ?        0
======================================
  Hits           ?       22
  Misses         ?      133
  Partials       ?        0

Impacted Files
Coverage Δ

upload_controller_service/__init__.py
100.00% <ø> (ø)

upload_controller_service/__main__.py
0.00% <ø> (ø)

upload_controller_service/api/__init__.py
100.00% <ø> (ø)

upload_controller_service/api/main.py
100.00% <ø> (ø)

upload_controller_service/config.py
100.00% <ø> (ø)

upload_controller_service/core/__init__.py
0.00% <0.00%> (ø)

upload_controller_service/core/main.py
0.00% <0.00%> (ø)

upload_controller_service/dao/__init__.py
0.00% <0.00%> (ø)

upload_controller_service/dao/db.py
0.00% <0.00%> (ø)

upload_controller_service/dao/db_models.py
0.00% <0.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@94262e6). Click here to learn what that means.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##             dev       #2   +/-   ##
======================================
  Coverage       ?   14.19%
======================================
  Files          ?       16
  Lines          ?      155
  Branches       ?        0
======================================
  Hits           ?       22
  Misses         ?      133
  Partials       ?        0

Impacted Files
Coverage Δ

upload_controller_service/__init__.py
100.00% <ø> (ø)

upload_controller_service/__main__.py
0.00% <ø> (ø)

upload_controller_service/api/__init__.py
100.00% <ø> (ø)

upload_controller_service/api/main.py
100.00% <ø> (ø)

upload_controller_service/config.py
100.00% <ø> (ø)

upload_controller_service/core/__init__.py
0.00% <0.00%> (ø)

upload_controller_service/core/main.py
0.00% <0.00%> (ø)

upload_controller_service/dao/__init__.py
0.00% <0.00%> (ø)

upload_controller_service/dao/db.py
0.00% <0.00%> (ø)

upload_controller_service/dao/db_models.py
0.00% <0.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@94262e6). Click here to learn what that means.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##             dev       #2   +/-   ##
======================================
  Coverage       ?   14.19%
======================================
  Files          ?       16
  Lines          ?      155
  Branches       ?        0
======================================
  Hits           ?       22
  Misses         ?      133
  Partials       ?        0

Impacted Files
Coverage Δ

upload_controller_service/core/__init__.py
0.00% <0.00%> (ø)

upload_controller_service/core/main.py
0.00% <0.00%> (ø)

upload_controller_service/dao/__init__.py
0.00% <0.00%> (ø)

upload_controller_service/dao/db.py
0.00% <0.00%> (ø)

upload_controller_service/dao/db_models.py
0.00% <0.00%> (ø)

upload_controller_service/models.py
0.00% <0.00%> (ø)

...load_controller_service/pubsub/schemas/__init__.py
0.00% <0.00%> (ø)

..._controller_service/pubsub/schemas/read_schemas.py
0.00% <0.00%> (ø)

upload_controller_service/pubsub/subscribe.py
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Having no peers connected should not prevent users to interact with their bee node

Maybe we should introduce some orange state and not prevent interactions if the bee node has no peers. At minimum this is good for development, you can just run one bee node and don't have to wait for the peers to be connected.

I agree that this should not be a blocker. Once you have connection to your node (or even the debug API) it would be good if you could access the tabs, maybe with the actions disabled.


Fast DOM

Does Angular use techniques such as that used in FastDOM ( https://github.com/wilsonpage/fastdom )? Does that apply to Angular?
Hope this idea might be helpful. Regards.

I'm not sure how useful it is to keep this issue open - perf improvement tasks are probably better tracked with more granular issues.

I agree. Thanks @wesleycho


Release on conda-forge?

Can I release this on conda-forge?

Maybe? It's a weird project since it relies on an external docker and docker-compose install, as well as externally hosted docker images. I personally think it's not up-to-snuff for conda-forge's standards, and for a testing dependency I think installing from pypi is just fine. What's your use case?

Use case is 100% just not wanting to install from pypi for testing purposes


sendMessage method shouldn´t check message to be a string

Since toString method can be overriden in any function, wouldn´t it be nice allow sendMessage to accept a wider range of types for message argument?
function Foo()
{
}
// toString override added to prototype of Foo class
Foo.prototype.toString = function()
{
return "Im Foo";
}
sendMessage(new Foo(), null);

Thank you manis, you are free to make a pull request.

The issue was fixed in the version 1.0.2. Closing the issue.
Thanks for reporting.


I need another photo

Challenge Name

Issue Description

Browser Information

Browser Name, Version:
Operating System:
Mobile, Desktop, or Tablet:

Your Code

Screenshot

@bilancostel do not spam the issue tracker.


Fix: While receiving cards by a particular player

There seems to be some issues still while consuming cards. But seems like cards are set properly


Fix(docs): sudoku-solver.js accepts valid inputs with no upper limit

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #48687

Originally increased recursion limit to 250,000 iterations. Then, to ensure, all puzzles could be completed, removed recursion limit and instead check if there are any empty squares left.

Thank you, for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason

... as this is run on the server, and the server could serve dozens of Campers at the same time, it cannot be increased to the point of being able to brute force the examples given.
https://github.com/freeCodeCamp/freeCodeCamp/issues/48687#issuecomment-1515130152

Thank you, and happy coding.


Properly (hackishly) handle commits without parents

Closes #13

Not sure if I don't want to redo this entirely as it is a bit too hacky for my taste. This project was quite clean and easy to reason about before and this changes that quite a bit 😅
(Alternatively the issue is closed as won't fix)

If this isn't something that is needed during normal use of Git, then I don't see a valid reason to add complexity.

Depends on wether creating a repo with this action already configured would count as "during normal use of git". It is quite the rare event that a repo is created and everything configured, but this is also the first interaction you might have with this action :/
I specifically don't want to deal with things like having multiple "initial commits", but dealing with the one that always exists could count as a requirement. Right now I tried to integrate this into the normal flow of the action but I might go ahead and just detect this and exit early with appropriate data (version bump to what is contained in the last commit)


GPU-Specific Inconsistency in XLA Compiled Model with tf.nn.atrous_conv2d, tf.cos, and tf.multiply

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
2.15.0
Custom code
Yes
OS platform and distribution
Ubuntu 22.04.3 LTS
Mobile device
No response
Python version
3.10
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
cuda : 12.2 / cudnn 8.9.04
GPU model and memory
Tesla V100S-PCIE-32GB
Current behavior?
There are significant discrepancies in the model's output under XLA compilation when running on a GPU device, as indicated by the failed assertions. The differences are not minor, suggesting a deeper issue in TensorFlow's compiled execution path, specifically in the context of GPU-accelerated computation.
Before run below stand-alone code, please download the pickle file and replace YOUR_PICKLE_FILE_PATH with youre pickle file path.
Standalone code to reproduce the issue
import tensorflow as tf
import pickle
import os
import numpy as np

class Model1(tf.keras.Model):
    def __init__(self):
        super().__init__()
        self.p0 = tf.random.uniform(shape=[18, 14, 14, 4], dtype=tf.float32)

    @tf.function(jit_compile=True)
    def __call__(self, inp, inp1):
        astconv = tf.nn.atrous_conv2d(self.p0, inp1, rate=1, padding="VALID")
        _cos = tf.cos(astconv)
        mul = tf.multiply(_cos, astconv)
        return astconv, _cos, mul

model1 = Model1()
device = "gpu"
print(f'=========RUNNING WITH PICKLE FILES===========')
pickle_file_path = 'ast_cos_mul.pickle' #YOUR_PICKLE_FIlE_PATH
if not os.path.exists(pickle_file_path) :
    print(f'Pickle file not exist')
else :
    with open(pickle_file_path, 'rb') as f :
        inputs = pickle.load(f)
    inputs = [tf.convert_to_tensor(arr) for arr in inputs]
    with tf.device(device):
        tf.config.run_functions_eagerly(True)
        out1 = model1(*inputs)
        out2 = model1(*inputs)
        print(f'=========eager_output(version:{tf.__version__})================')
        try :
            for i in range(min(len(out1),len(out2))):
                np.testing.assert_allclose(out1[i].numpy(), out2[i].numpy(), rtol=0.001, atol=0.001, err_msg=f'at checking {i}th')
            print("XLA_eager does not trigger assertion")
        except AssertionError as e:
            print("XLA_eager triggers assertion")
            print(e)
        tf.config.run_functions_eagerly(False)
        out1 = model1(*inputs)
        out2 = model1(*inputs)
        print(f'=========compiled_output(version:{tf.__version__})================')
        try :
            for i in range(min(len(out1),len(out2))):
                np.testing.assert_allclose(out1[i].numpy(), out2[i].numpy(), rtol=0.001, atol=0.001, err_msg=f'at checking {i}th')
            print("XLA_complie does not trigger assertion")
        except AssertionError as e:
            print("XLA_complie triggers assertion")
            print(e)

Relevant log output
=========eager_output(version:2.15.0)================
XLA_eager does not trigger assertion
2023-11-27 18:39:00.683604: I external/local_xla/xla/service/service.cc:168] XLA service 0x55a6d3345b50 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2023-11-27 18:39:00.683633: I external/local_xla/xla/service/service.cc:176]   StreamExecutor device (0): Tesla V100S-PCIE-32GB, Compute Capability 7.0
2023-11-27 18:39:00.687057: I tensorflow/compiler/mlir/tensorflow/utils/dump_mlir_util.cc:269] disabling MLIR crash reproducer, set env var `MLIR_CRASH_REPRODUCER_DIRECTORY` to enable.
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1701110341.197440  963817 device_compiler.h:186] Compiled cluster using XLA!  This line is logged at most once for the lifetime of the process.
=========compiled_output(version:2.15.0)================
XLA_complie triggers assertion

Not equal to tolerance rtol=0.001, atol=0.001
at checking 2th # indicates that removing one of operators will not trigger the error
Mismatched elements: 40 / 13104 (0.305%)
Max absolute difference: 0.14808655
Max relative difference: 0.0466534
 x: array([[[[ 4.319121e+02,  5.756997e+01, -1.646362e+02, ...,
           1.929362e+02,  4.481723e+01,  5.383195e+02],
         [ 2.320642e+02, -6.552701e+01,  1.128223e+02, ...,...
 y: array([[[[ 4.319121e+02,  5.756836e+01, -1.646362e+02, ...,
           1.929362e+02,  4.479507e+01,  5.383195e+02],
         [ 2.320521e+02, -6.552701e+01,  1.128223e+02, ...,...

Hi,
Could you please provide the code in a simplified format without the need of pickle file, it would help us to debug faster. Thanks!

Hi, @sachinprasadhs
This issue can only be reproduced with the specific inputs.


Needs to be a warning when the style parameter is used

Feedback from one of the users:

Needs to be a warning when the style parameter is used unless another (special) parameter is specified to override the warning.
That is: https://maputnik.github.io/editor/?style=X.json should warn folks that their cached style is avoid to be written over.  For apps, folks should have https://maputnik.github.io/editor/?style=X.json&warning=no.

Lets break this ticket down into multiple stages to make it more approachable, and a 'good first issue'. Rather than using a modal we can use https://developer.mozilla.org/en-US/docs/Web/API/Window/confirm which will block the javascript event loop, meaning that we don't need to deal async javascript right now.
Change this block of code to prompt the user
https://github.com/maputnik/editor/blob/012e4b670eb50552a0a90984239b6b3be99bc0c0/src/components/App.jsx#L150-L153
Also add a function in here https://github.com/maputnik/editor/blob/master/src/libs/urlopen.js to remove the style= querystring parameter from the url (see https://nodejs.org/api/url.html)


CModule Logs

Hello
I have question please: I want to visualize the CModule's logs to see what is happening.  I can't find a way to see the messages sent from the downstream device are actually received by the gateway neither in visual studio code nor  using  ""iotedge logs CModule"" command
Thank you

@anfelbeghoura can you raise your request at https://github.com/azure/iotedge? If you routes the message to one module, you can print some logs when the module receives the message. Otherwise some support from runtime is required for your scenario.

@marianan pls closed this

@marianan pls closed this


support Android obb?

yes, suport it as zip file by ApkDiffPatch;

now need  pacher update it as a zip file;  (can use ApkDiffPatch same as apk)

add demo


@azure/identity-cache-persistence overwrites Microsoft.Developer.IdentityService entry in the keychain across different applications.

Package Name: @azure/identity-cache-persistence
Package Version: 1.1.0
Operating system: Mac OS
[x] nodejs

version: 18.19.1

[ ] browser

name/version:

[x] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
@azure/identity-cache-persistence overwrites Microsoft.Developer.IdentityService entry in the keychain across applications.
To Reproduce
Scenario: There are two different applications using @azure/identity-cache-persistence. Application A has the following configuration;
export const tokenCachePersistenceOptions: TokenCachePersistenceOptions = {
enabled: true,
name: 'appA',
};
Application B has the following config:
export const tokenCachePersistenceOptions: TokenCachePersistenceOptions = {
enabled: true,
name: 'appB',
};
User runs the app A, authentication happens and the token gets stored in the KeyChain with the entry name: Microsoft.Developer.IdentityService
User runs the app B, @azure/identity-cache-persistence reads the KeyChain with the entry name: Microsoft.Developer.IdentityService and authentication fail (or interactive auth happens again) because this entry stored by app A.
Expected behavior
Each application should have its own entry in the KeyChain regarding the configuration. ie: Microsoft.Developer.IdentityService-appA and Microsoft.Developer.IdentityService-appB

Hello @altinokdarici, can you confirm if this is happening on Windows as well?


Upgrade simple-slack-api to 1.2.x

https://github.com/Ullink/simple-slack-api/releases/tag/1.2.0

https://github.com/masahitojp/botan-core/pull/13 upgraded


[5.7] remove temporary variable

removes temporary variable, and makes the method consistent with assertDatabaseHas() and assertSoftDeleted()

Hmm, I preferred the original.

Me, too

👎 The original is way clearer.

Thanks for the PR, but I think we don't need to change this. :)

I guess I would prefer the consistency, because the other 2 assertions are written the same as my change.

@browner12 maybe a PR in that direction then ;)


Add fetch tests

extracts test helpers (OpsRecorder, etc) from the cmd/update tests for usage with other cmds
adds unit tests for cmd/fetch for the following scenarios:

empty-file
empty-deps
self-referential
mutually-recursive

A few minor comments left.
I think the big one is that there is no test for transitive dependencies being handled correctly, as I noted.


RFC: Intent to implement stable Svelte bindings

Summary
Currently I see our current @urql/svelte package and its past and current implementation as nice experiments which helped check the boundaries of Svelte and test APIs and the understanding of users.
The latest PR allowed all modes of Svelte's stateful stores to be used somehow, with similar semantics to the other bindings, See #862
It's becoming increasingly clear that this is confusing and doesn't feel idiomatic to Svelte.
The next implementation of @urql/svelte should start from a clean slate and be idiomatic to Svelte and intuitively avoid confusion. It is allowed to stray away from feeling like the urql and @urql/preact bindings, even forgoing permanent state memory if necessary.
Problems with the approach
The current approach attempts to allow three modes of usage:

Store usage without memoised state
Store usage with memoised state via an intermediate factory function
Async-await/Promise usage

The last option of these feels idiomatic to Svelte but should be discouraged. We never aim to show results that can never reactively update. This is objectively bad.
The memoised usage is confusing and Svelte simply does not have a full reactivity model that allows us to observe changes. The user can do this manually and this may feel wrong to us, trying to implement complex hooks flows in Svelte, however this is not our problem to solve.
Bugs to avoid

Unmounting issues, which may be inherent to our implementation: #948, #979
Incorrect promise behaviour #932

❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤ ❤

An update has been published as<EMAIL_ADDRESS>


Make a non-access modifier local variables.

Codecov Report

Merging #966 (a386f48) into master (b6d39a4) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #966   +/-   ##
=========================================
  Coverage     91.99%   91.99%
  Complexity     7432     7432
=========================================
  Files           189      189
  Lines         15664    15664
  Branches       2907     2907
=========================================
  Hits          14410    14410
  Misses          677      677
  Partials        577      577

Impacted Files
Coverage Δ

...java/org/apache/commons/lang3/text/StrBuilder.java
94.46% <ø> (ø)

.../org/apache/commons/lang3/time/FastDateParser.java
94.83% <ø> (ø)

.../main/java/org/apache/commons/lang3/Functions.java
89.13% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Multiple test fix

I think the poolsize on this needs to be turned down to work reliably in a testing environment

I agree that this makes sense, but the default value of poolsize=5 in most of those functions was mostly a placeholder that we could change if we have issues.  Changing how all of the multiprocessing tests default might be a better solution (and avoid making more commits like this in the future.

i've made it configurable now (assuming these tests pass)

Looks good!  I have opened #30 as a reminder based on our discussion earlier today.


Drop the non-Python images

Removes the plain Debian and Alpine images without Python/PyPy.
We haven't used these in a long time. None of our current images are based on them.

:+1:


Because during training, I saw that the code added a starting character like  in the first position. Should we also add this character during inference to maintain consistency with training?

Because during training, I saw that the code added a starting character like
<s>

in the first position. Should we also add this character during inference to maintain consistency with training?

Usually this is not too important when you have prompts so either way is fine.

But some of the models I trained, whether or not they include  during inference has a significant impact on the results. What do you think could be the reason for this?
The json format of the training data is
{"input": "user:xxxx\ngpt:", "output": "yyyy"}
train scripts is
...
--train_dataset.text_processor.fields='[input],output' \
--train_dataset.text_processor.add_eos_token=True \
...

Ideally, the BOS token should be added at the test time to match the training time. Maybe some models are not very sensitive so it it okay either way. If your model is sensitive to this, I think adding the BOS token during inference would be a good idea.

ok， thank you~


feat: Add Todo List App UI Mobile Design

This PR Adds the Todo List App UI Mobile Design following the Todo List App Guide and design layout of the assignment link of TheOdinProject and Front-End Mentor
This PR begins with the Todo List App's mobile view, uses dummy placeholders with Tailwind CSS, and makes some elements interactive by implementing hover effects.

Frontend Mentor Design
Current Design

This PR Adds the Todo List App UI Mobile Design following the Todo List App Guide and design layout of the assignment link of TheOdinProject and Front-End Mentor
This PR begins with the Todo List App's mobile view, uses dummy placeholders with Tailwind CSS, and makes some elements interactive by implementing hover effects.
Frontend Mentor Design	Current Design

Please update the current design also the PR description isn't good enough, and lets remove the dummy placeholder


IPS alerts part 3 - paging

Continuation of https://github.com/opnsense/core/issues/4753
Now there some glitch in paging or alerts enumeration.
Same steps to setup environment.
Waiting few hours to collect some alerts.
115 alters collected.

Paging set to greater than 115, like 500.
All 115 are enumerated ok.
At the end of page is paging

7 pages? Why?
If I switch to second page it is empty

It could be related to fact, that there was great amount of alerts, they were deleted using this button

but some COUNT of alerts is not reset.

Ah, maybe it is not problem of delete button.
Further testing - no matter of what is selected here

Paging still uses number 7

Number 7 is selected in dropdown at page initial load. So dropdown is filling table with correct number of alerts, but does not update paging.

it can't know the number of pages, some background https://docs.opnsense.org/manual/gui.html#page-navigation

Ah, ok, so Im closing this. Thanks for response.


Fix for vulnerability GHSA-cxww-7g56-2vh6 reported by GitHub on 2024-09-03

Updated to upload-artifact@v4  (from upload-artifact@v3)
Updated to download-artifact@v4  (from download-artifact@v3)

Merging now, the tests will not pass because of some things we need to improve (Not related to this PR)


stdlib: Make Unsafe{Mutable,}BufferPointer @_fixed_layout to work around rdar://18157434

This was causing the resilient build on Linux to hang when building swiftpm, because of a peculiar usage of nested types:
private struct JSONReader {
    struct UnicodeSource {
        let buffer: UnsafeBufferPointer<UInt8>
    }

    let source: UnicodeSource
}

@swift-ci Please smoke test and merge


Error occurs when adding a widget

When I add a frame or want to see a preview an error occurs (See below).
All I have to do to get this is to start wxGlade and add a frame to the application which will show the error below.
After this clicking on a widget is enough to get the error again, except when clicking on a sizer.
ERROR   : None
An unexpected error occurred!
Exception type:      <class 'TypeError'>
Exception details:   Sizer.SetItemMinSize(): arguments did not match any overloaded call:
overload 1: argument 3 has unexpected type 'float'
overload 2: argument 2 has unexpected type 'int'
overload 3: argument 1 has unexpected type 'ExpandoTextCtrl'
overload 4: argument 1 has unexpected type 'ExpandoTextCtrl'
overload 5: argument 1 has unexpected type 'ExpandoTextCtrl'
overload 6: argument 1 has unexpected type 'ExpandoTextCtrl'
Application stack traceback:
File "/usr/lib64/python3.10/site-packages/wx/core.py", line 2254, in Notify
self.notify()
File "/usr/lib64/python3.10/site-packages/wx/core.py", line 3410, in Notify
self.result = self.callable(*self.args, **self.kwargs)
File "/usr/lib/python3.10/site-packages/wxglade/main.py", line 136, in edit_properties
self.create_editor(edit_widget)
File "/usr/lib/python3.10/site-packages/wxglade/main.py", line 196, in create_editor
property_instance.create_editor(current_page, current_sizer)
File "/usr/lib/python3.10/site-packages/wxglade/new_properties.py", line 1390, in create_editor
hsizer.SetItemMinSize(self.text, 100, h * 1.5)
Date and time:       2022-01-08T12:04:35.030025
Python version:      3.10.1
wxPython version:    4.0.7
wxWidgets platform:  WXGTK
wxGlade version:     1.0.3

Please try wxGlade 1.0.4. This is caused by a change in Python 3.10.
(Duplicate of issue #504.)


Add 4 new devices codes to the DMP

WP3 would like to enable uploads of IDF-TEQ (Technology Experience Questionnaire) and Interview Transcripts data to the DMP.
The plan is to use "fixed manually defined device IDs" across all sites that clearly encode the general category of the
data (the participant IDs included in file names will still clearly encode the study site):
InterviewTranscriptsDeviceIDEncodigs:

IDE-FGX3N3 (German transcripts)
IEN-DZSSAX (English transcripts)
INL-GN65GH (Dutch transcripts)

IDF-TEQDeviceIDEncoding:

TEQ-CKQAGP

Can these codes be included as valid device IDs so that data can be uploaded accordingly?

Solved in this PR #324

Add some more Device IDs


docs: how to use new ESM support in Cloud Functions

Cloud Functions has recently added support for ESM. It is enabled in functions/package.json and therefore applies to all functions.
This adapter converts SvelteKit server to CJS by default but you can configure this output with the esbuild options. We should document this, write tests for ESM and also have an example in the docs for ESM.

closed in #137


Remove cover and timezone from the Facebook user tests

Moved to https://github.com/thephpleague/oauth2-facebook/pull/59


[BUG] Revamp the footer.

Describe the bug
We can remove the projects and our team section for now from footer.
Screenshots

Expected behavior
Remove the Support section completely by

Moving our team section to header
Removing the projects section

Related to - #13

Okh. The sequence will be About-->Projects--->Team--->Contact in the header. If it works for you or you want the sequence to be otherwise. Assign it to me, please.

sequence will be About-->Projects--->Team--->Contact in the header.

Looks great!! Go ahead @Ritik-Bhasarkar .

@AdarshRawat1 I opened the PR. Check it out and contact me if needed.

@Ritik-Bhasarkar link the PR to this issue. So that we can track the progress.

Hey there, I would like to enhance the footer and contribute. Could you please assign me this if it's still open ?

@AdarshRawat1 Please review it.

@AdarshRawat1 Okay, if he fails to do it give me the chance to enhance it

@AdarshRawat1 Okay, if he fails to do it give me the chance to enhance it

He won't fail 😅,but you can improve his design once his PR gets merged.

@AdarshRawat1 Okay, if he fails to do it give me the chance to enhance it

I'll make sure to assign the next issue to you. Waiting for your valueable contributions.

@AdarshRawat1 Okay thanks

@AdarshRawat1 Okay thanks

The footer section PR have been merged so now you can open a new issue suggesting improvement. @Lokesh-MV

Okay thanks

@AdarshRawat1 I've opened a new Issue, could you please check it?

@Lokesh-MV sure


Adding pik

See https://github.com/google/pik/issues/6.

Hi! 👋 Thanks for the PR!
I haven’t added words from non-English languages, so this is a first. I’m not sure if it’s feasible to do that (P.S. I’m Dutch), for one (or many?) languages!
One downside: we probably need to duplicate the project to get good coverage, doubling it in size.
Another: it would result in a lot of wrong matches: some normal words in English are profane in Dutch, and some that are normal in Dutch are profane in English.

:wave:
Have you looked at http://wordsafety.com/? They might have a good list to check. I think that this is important, too. Perhaps an option for other languages besides English?

That looks cool! Albeit not open source?
We still need lists for Dutch / Danish (in this case) to make other languages work.
If projects for other languages are created, I can work on supporting this in alex itself!

@RichardLitt Some languages done!

:)


Mappings table is case sensitive

Describe the bug
The config table is getting merged with misc.merge, which is case-sensitive.
Two keys with different cases are kept as different entries. If you map for example <c-n>, both <c-n> and the default <C-n> are in the mapping table.

But core.on_keymap compares the keymaps with keymap.equals, which uses vim.api.nvim_replace_termcodes. In this case <c-n> and <C-n> are the same.
So the plugin matches the first entry it finds in the mapping table, which is random.
So on every start of Neovim, either the user-defined function or the default is mapped.
Minimal config based on this
require "cmp".setup {
	mapping = {
		["<c-n>"] = function() print("hello") end,
	}
}

To Reproduce

restart Neovim a couple of times
about half of the time the default mapping for <C-n> is mapped, the other half print("hello") is mapped

Expected behavior
The mappings table should not be case-sensitive.
misc.merge should probably merge that one using vim.api.nvim_replace_termcodes

might be related to #475 :thinking:

It's weird.
I already normalized the key sequence. see https://github.com/hrsh7th/nvim-cmp/blob/main/lua/cmp/config.lua#L97

This problem couldn't be reproduced in my environment and was a headache. It would be great if the cause was known.
google translated

I think the problem is here https://github.com/hrsh7th/nvim-cmp/blob/9b5d64d90654618461abeddbb1e07b440d362744/lua/cmp/config.lua#L26
this one is not normalized

Ahhhhh, indeed! Why did I overlook this? Thank you very much.


Automation: ensure the focus effect on the selected option in the namespace filter is visible.

Based on work done in https://github.com/rancher/dashboard/issues/7757, let's write an automated test to check that the highlighted option in the namespace filter dropdown isn't invisible.
This dropdown is also used in a few other places, such as the burger menu --> Global Settings --> Performance --> enable Require Namespace Filtering and reduce threshold. Previously, the focus effect on the selected option didn't change the font and icon colours.
@bisht-richa can offer guidance based on her work there.
To Reproduce

Click on Namespace filter and choose an option.

Result
Focus effect on the selected option doesn't change the font and icon colours.
Expected Result
Focused option should be clearly distinguishable from the other ones.

A test is already present for this issue.
https://github.com/rancher/dashboard/pull/8625/files#diff-e99a689a68e03beac725cc7ba111a7c5c275da598f995cdf0870bf8ba0100322

This is again completely a cosmetic test which requires a new definition in order to be tested.


Add a watch queue like on Youtube

Is your feature request related to a problem? Please describe.
When wanting to watch multiple videos after each other, one need to either add them to the "watch later" playlist or in another browser tab (on desktop).
Describe the solution you'd like
Instead, a watch queue like on YouTube could be added. It could look the same as when playing a playlist, but more integrated into normal viewing. Basically just copy what YouTube does, or something similar.
Additional context

Just like this

Thanks for the suggestion! I know we had something similar filed as a feature request, will try to dig it up, and if not, we'll keep this one.