Testing API Routes

Is your feature request related to a problem? Please describe.
I'm thinking about how to approach testing API routes built with this lib. With the older functional style I'd test API routes like this, but that's a little harder with the decorators and classes.
Describe the solution you'd like
Any thoughts or pointers on a good approach. Once again, thanks for this awesome library!

You can do it in the same way! The only difference is to pass the url property correctly. This is a test that I sketched now for /examples/route-matching/pages/api/users/[[...params]].ts:
import { createMocks } from 'node-mocks-http';
import handleUsers from './[[...params]]';

describe('/api/users/[[...params]]', () => {
  test('Fetches a user', async () => {
    const { req, res } = createMocks({
      method: 'GET',
      url: '/api/users/101',
    });

    await handleUsers(req, res);

    expect(res._getStatusCode()).toBe(200);
    expect(res._getData()).toEqual(
      expect.objectContaining({
        id: 101,
      }),
    );
  });

  test('Returns 404', async () => {
    const { req, res } = createMocks({
      method: 'GET',
      url: '/api/users/101111',
    });

    await handleUsers(req, res);

    expect(res._getStatusCode()).toBe(404);
    expect(JSON.parse(res._getData())).toEqual(
      expect.objectContaining({
        message: "No user found with ID '101111'.",
      }),
    );
  });
});

Amazing, thank you!

@ggurkal I followed your example, some simple tests worked great!
However, it seems to be a little tricky to get route matching to work.
I can't get a request to a page like pages/api/something/[id], keep getting
 {"statusCode":404,"message":"Cannot GET /api/something/test","error":"Not Found"}

when i try creating a mock like:
const testId = 'test';
const { req, res } = createMocks({
  method: 'GET',
  url: `/api/something/${testId}`,
  query: {
    id:  testId,
  },
  params: {
    id testId,
  },
});

Despite the fact that the API route exists and works in production 😟

Hey @tn12787
Sorry for the late reply, been quite busy lately.
What's the full path of your handler file? I just tested the mock you posted above with a filepages/api/page/[id].ts and worked without any issues.


API Commands / Execute REST API - the http methods are missing, only get and post are present

the command only supports get and post while in previous versions such as: <IP_ADDRESS> there are also DELETE, PUT, etc.

Sorry, I must have mistakenly erased those.
DELETE and PUT are now available in v<IP_ADDRESS>.


Integrate rpcbench from tensorflow into gRPC's benchmark suite and dashboards

Integrate rpcbench
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/distributed_runtime/rpcbench_test.cc
from tensorflow into gRPC's benchmark framework.

Comments:

Consult with @jhseu to enable this to integrate TF and gRPC master
Explore adding larger message tests
Dashboard relevant tests from this suite
Intention is to only enable this at master but will consider doing this for PRs if needed

Current status update:

Integration of grpc master with TF is blocked on merger of #10971
There is a viable branch for benchmarking TF at vjpai/tensorflow in the branch grpc-patch . This branch is based on tensorflow/tensorflow#7466 and is currently pinned to grpc on the branch associated with #10971 . When the gRPC branch merges, I will update the TF branch to be pinned to grpc-master
The true integration of TF master with gRPC master is blocked until gRPC resolves its large message issues on Windows as stated in #10161 and which is being resolved using #10716
As soon as possible, we should try to git bisect an answer to when the Windows large message tests started breaking. They are fine at the gRPC commit that TF is currently pinned to ( d7ff4ff40071d2b486a052183e3e9f9382afb745 ) but are failing at master.

All of the issues related to TF integration were resolved several months ago and we are now on track for TF to regularly upgrade its gRPC pin. Need to revisit the issue of installing dependences on the performance worker and automating/dashboarding this.
Reassigning...

@ncteisen  please remove P1 label if appropriate.

We have this dashboarded internally. That is sufficient


Other Meetings at This Address

The "Other Meetings at this Address" block of the single-meeting view currently lists "One Day at a Time" hard-coded, as far as I can tell. Let's get this working dynamically.

Work in progress: https://github.com/FlipperPA/react/commits/feature/meetings-at-address
I'm starting to figure out ReactJS a bit, @joshreisner :)

Fixed by #7 .


Neural Network Feature (Wish) List

Neural Network Feature (Wish) List
These are the basics:

[x] Basic 2-layer network with bias
[x] Activation functions which reuse the activation on the backwards pass (sigmoid, tanh, ReLU)
[x] MSE cost function
[x] Adjustable learning rate
[ ] Additional examples and tests
See #41 and #66 and #76.

These would be interesting to add:

[ ] Multiple hidden layers
Per #61.
[ ] Semi-arbitrary activation functions
Per #70 and #75.
[ ] Arbitrary cost functions
See here.
[ ] Automatically adapting learning rate (Momentum)
Per #65. Also see here via here.
[ ] Multiple initial weighting strategies
See here.
[ ] Convolution layers
See here. Also see here via here.
[ ] Simple RNN
See here via here.
[ ] Advanced optimization
See here.

The two big ones for me are the additional examples and the multiple hidden layers.
Those two things open the door for lots of other possibilities.
The additional example can be used for testing community contributed features.
The multiple hidden layers open the door for convolution layers and the like.
Which then opens the door for some really cool art.


Update active-directory-application-proxy-silent-installation.md

I'm working on integrating blog post content, and noticed this is a doc that would benefit from including this information here.

Hi @laschultz, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Lori Goff (Steyer Associates Inc)). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@kgremban Hi Kelly. Please review these proposed changes. Thanks.


problem running findtirs

Hello,
I run tephra all and obtain an error at the findtirs step:
INFO - Command - 'tephra findtirs' started at: 10-08-2019 04:52:59.
ERROR - 'gt tirvish' failed exit value: 1. Here is the output: warning: terminal_inverted_repeat_element (generated, line 0) is too short to be translated (0 nt), skipped domain search

When running findtirs alone:
'gt tirvish' failed exit value: 1. Here is the output: warning: terminal_inverte
d_repeat_element (generated, line 0) is too short to be translated (0 nt), skipp
ed domain search
/root/.tephra/gt/bin/gt tirvish: error: query seqid 'chrlg1' could match more th
an one sequence description

The other steps look fine based on the output files. This is the log:
root@bp:~/tephra/db# grep "Output\|Command" tephra_full.log
Command - 'tephra findltrs' started at: 06-08-2019 12:38:21.
Command - 'tephra findltrs' started at: 06-08-2019 12:38:39.
Command - 'tephra findltrs' completed at: 08-08-2019 14:42:41.
Output files - /db/genome_v2_tephra_ltrs.gff3
Output files - /db/genome_v2_tephra_ltrs.fasta
Command - 'tephra maskref' for LTRs started at: 08-08-2019 14:42:41.
Command - 'tephra maskref' completed at: 08-08-2019 18:27:24. Final output file:
Output files - /db/genome_v2_tephra_masked.fasta
Command - 'tephra findtrims' started at: 08-08-2019 18:27:24.
Command - 'tephra findtrims' completed at: 09-08-2019 16:39:19.
Command - 'tephra classifyltrs' started at: 09-08-2019 16:39:24.
Command - 'tephra classifyltrs' completed at: 09-08-2019 18:19:09.
Output files - /db/genome_v2_tephra_ltrs_trims_classified.gff3
Output files - /db/genome_v2_tephra_ltrs_trims_classified.fasta
Command - 'tephra age' started at: 09-08-2019 18:19:09.
Command - 'tephra age' completed at: 09-08-2019 18:20:09.
Output files - /db/genome_v2_tephra_ltrages.tsv
Command - 'tephra maskref' for classified LTRs/TRIMs started at: 09-08-2019 18:20:09.
Command - 'tephra maskref' completed at: 09-08-2019 20:22:53. Final output file:
Output files - /db/genome_v2_tephra_masked2.fasta
Command - 'tephra sololtr' started at: 09-08-2019 20:22:53.
Command - 'tephra sololtr' completed at: 09-08-2019 21:38:58.
Output files - /db/genome_v2_tephra_sololtrs.gff3
Output files - /db/genome_v2_tephra_sololtrs_rep.tsv
Output files - /db/genome_v2_tephra_sololtrs_seqs.fasta
Command - 'tephra illrecomb' started at: 09-08-2019 21:38:58.
Command - 'tephra illrecomb' completed at: 10-08-2019 00:05:24.
Output files - /db/genome_v2_tephra_illrecomb.fasta
Output files - /db/genome_v2_tephra_illrecomb_rep.tsv
Output files - /db/genome_v2_tephra_illrecomb_stats.tsv
Command - 'tephra findhelitrons' started at: 10-08-2019 00:05:24.
Command - 'tephra findhelitrons' completed at: 10-08-2019 04:30:59.
Output files - /db/genome_v2_tephra_helitrons.gff3
Output files - /db/genome_v2_tephra_helitrons.fasta
Command - 'tephra maskref' for Helitrons started at: 10-08-2019 04:31:01.
Command - 'tephra maskref' completed at: 10-08-2019 04:52:59. Final output file:
Output files - /db/genome_v2_tephra_masked3.fasta
Command - 'tephra findtirs' started at: 10-08-2019 04:52:59.
Command - 'tephra findtirs' completed at: 10-08-2019 05:32:57.
Command - 'tephra classifytirs' started at: 10-08-2019 05:32:57.

Tephra docker version was used:
tephra (Tephra) version 0.12.4 (/usr/local/bin/tephra)

Thanks for your help
Regards,
Jenny

Hi,
It looks like you have some duplicate IDs in your genome file perhaps. We can check that with the commands below:
grep ">" genome.fas | sed 's/>//' | sort -u | wc -l

and
grep -c ">" genome.fas

If the output of those are different there may be duplicates or some other issue. Seeing the ID format would be helpful too.
grep ">" genome.fas | head

Thanks.

Thanks for your reply,
There seems to be no duplicated IDs, I am not sure if ID is the real issue because the shortened/edited IDs do not solve the problem. It is also probably not one particular sequence causing this, as the same error was obtained using both the full set/subset.
What could be other possibilities? The run halted when the IDs were listed to the gff, there are 809 IDs in total and it stopped at 631.
Best regards,
Jenny

Hi Evan,
Sure, I've shared the file "genome.fasta.gz" through fex via your email at evanstaton.com
Thanks for your help!
Best regards,
Jenny

Just FYI, I can recreate the error. This is something in the GenomeTools library and not Tephra, so it's not immediately clear how to resolve it. I will likely have to reduce the error to the problematic sequence and raise the issue to that group, but I will keep this issue updated as I find out more.
Thanks,
Evan


fix a detail in :read doc

I wonder if we should add a cpo option for controlling this behaviour, or something similar

I never noticed. Thanks. Not sure if this warrants an extra cpo option. I would think if one is using ex-mode, it is fine to follow traditional vi behaviour here

I never noticed. Thanks. Not sure if this warrants an extra cpo option. I would think if one is using ex-mode, it is fine to follow traditional vi behaviour here

I see,  though I arrived here curious if there was a variant to do :read and have cursor at the end of the pasted text.. (I see one can still `]).. there would be room for a :read! command, like we have :put and :put! to paste above and below


:) Parser eats all initial ":" characters in message text

Inappropriate use of lstrip(":") in parse.py parser() munges any messages which actually do begin with ":" character(s) -- they're stripped off too.
Example input message text
:)

Yields output message text
)

Note also that every lstrip() call in parse.py is likewise inappropriate.  They're all trying to remove "exactly one of a character", which is not what lstrip() does.  Those other instances of lstrip() maybe won't manifest given normal protocol traffic.  Maybe.

@kamalmostafa This PR has broken whisper parsing which will need to be addressed.

Thank you for the follow-up fix @chillymosh (oops, sorry for the breakage)!
This looks like its probably okay... But the lstrip() is overzealous and would mis-parse channel names that actually do start with a '#', same as the original problem with stripping too many ':' characters.   (That might not currently occur for Twitch IRC, but it's not unusual in "regular" IRC.)
-        channel = result.group("channel")
+        channel = result.group("channel").lstrip("#")

The goal is really to chop off exactly one '#' character, so how about this instead?:
+        channel = result.group("channel")[1:]

Thanks again, and also for TwitchIO :smiley:

channel = result.group("channel")[1:] would most likely work but channel names are usernames which are not allowed to contain any symbols other than an underscore, so starting with a # is not possible.
Twitch uses a customised version of IRC v3 so bringing up "regular" IRC is not relevant as we will never connect to anything outside of Twitch.


[5.0.1] Readme rendering broken at PyPI hsluv — release created with setuptools <38.6.0?

Hi @boronine,
could it be that you ran setup.py sdist for hsluv 5.0.1 in an environment with setuptools older than version 38.6.0?
I'm asking because the markdown readme rending is broken at https://pypi.org/project/hsluv/ and my guess is that the setuptools used to create the release was too old to understand the explicit markdown mimetime that is needed for markdown to be rendered on PyPI. What do you think?
Best, Sebastian
PS: This is what I see on PyPI:

Hi @hartwork, I saw that yesterday too. I am using this automation to publish: https://github.com/hsluv/hsluv/blob/master/default.nix#L332-L334
I just upgraded nixpkgs (and was forced to also upgrade Haxe), now testing!

Hi @hartwork, I saw that yesterday too. I am using this automation to publish: https://github.com/hsluv/hsluv/blob/master/default.nix#L332-L334

Is that nixpkgs of branch master i.e. file https://github.com/raboof/nixpkgs/blob/master/pkgs/development/python-modules/setuptools/default.nix ? I know NixOS to be rather bleeding edge but setuptools 41.2.0 is ~18 months old — I have 53.0.0 here, for comparison.

I just upgraded nixpkgs (and was forced to also upgrade Haxe), now testing!

You could upload to the testing instance of PyPI, if you wanted to. (I recommend against ever installing from it for security reasons though.)

PS: I saw you deleted release 5.0.1 on PyPI now. Please note that you cannot (and should not) re-upload different content under the same version and that removing releases from PyPI can easily break user builds — reverse dependencies —, e.g. everyone who was quick to bump their pinning to hsluv==5.0.1 already using some automated bumping solution. I would totally understand if someone came here angry, just so you know.

PPS: Any chance that python at https://github.com/hsluv/hsluv/blob/6b279ae16a29cdeebe4705c4a16e19fc2a6a8b7e/default.nix#L128 is actually Python 2.7? I'll shut up know, let me know what you'll find :smiley:

@hartwork yep just learned the hard way that I cannot reupload. PyPI test worked using upgraded nixpkgs automation: https://test.pypi.org/project/hsluv/
PyPI test automated here: https://github.com/hsluv/hsluv/blob/master/default.nix#L336-L338
The python binary wasn't an issue but I updated it to python3 in master anyways.
Now going to publish v5.0.2 with fixed markdown

@hartwork hurray! https://pypi.org/project/hsluv/5.0.2/
@dvzrv this release should be package-able for you as well.

@hartwork yep just learned the hard way that I cannot reupload. PyPI test worked using upgraded nixpkgs automation: https://test.pypi.org/project/hsluv/

Was it setuptools that needed updating?

PyPI test automated here: https://github.com/hsluv/hsluv/blob/master/default.nix#L336-L338

In see!

The python binary wasn't an issue but I updated it to python3 in master anyways.

Cool! :+1:

Now going to publish v5.0.2 with fixed markdown

Looks great, thank you! :tada:

Was it setuptools that needed updating?

I believe so but I didn't actually look into the specific versions. I just know that our nixpkgs was pinned about 2 years old: https://github.com/NixOS/nixpkgs/commit/3ab38ef086947822fbe2cffea071e1c508811990

Was it setuptools that needed updating?

I believe so but I didn't actually look into the specific versions. I just know that our nixpkgs was pinned about 2 years old: NixOS/nixpkgs@3ab38ef

Then that's the answer:
# git show 3ab38ef086947822fbe2cffea071e1c508811990:pkgs/development/python-modules/setuptools/default.nix | fgrep "version ="
  version = "38.4.0";

38.4.0 is older than the >=38.6.0 we need.

Oh nice one-liner!


Generalize test output for all test providers

Description:
Unify the test results by JMeter, TestNG etc for a single format.

Closing this issue since resolved with PR #87


fix: Missing '*' in kwargs forward syntax

Thank you :-)

When looking to write a test about this function, I realized it was not used, even by the fork command. So I decided to remove it. Do you happen to use it, if so, could you tell me how and why so that we could derive a proper documentation for it?

I add that exact same code locally, so just tried to use the one from clk instead when I found it.
Waiting for the fix I moved to clk.overloads.entry_point which seems to do the same and more. Given that you just removed main_command from clk I'll probably stick with entry_point unless there is another recommended way.


public macros depend on private macros

The public mock_trait! macro (and probably others too) depends  on the private __private_mock_trait_new_impl and __private_mock_trait_default_impl macros.  That wasn't a problem in Rust 2015 when macros are imported all or nothing.  But it is a problem in Rust 2018 where macros are imported like any other symbol.  Those private macros should either be public and documented, or else truly private.

Ack.

I fixed this issue as part of this PR: https://github.com/DonaldWhyte/double/pull/22.
Note that the fix involved adding the $crate:: prefix where the "private" macros are used. This means end users no longer need to explicitly import the private module when importing the macros in the Rust 2018 way. For example, this is now possible:
extern crate double;

use double::mock_method;
use double::mock_trait;

trait Calculator: Clone {
    fn multiply(&self, x: i32, y: i32) -> i32;
}

mock_trait!(
    MockCalculator,
    multiply(i32, i32) -> i32);
impl Calculator for MockCalculator {
    mock_method!(multiply(&self, x: i32, y: i32) -> i32);
}

One unfortunate aspect of this is that, as far as I know, the __private macros in macros.rs still need to be made public using [macro_export]. It is not possible for the private macros to be "truly" private. I could be wrong about this though. If you believe otherwise, let me know. I'm happy to add another change in to make them truly private.

The fix for this has been published to crates.io as part of version 0.2.4 of the double crate. Also note that going forward, the git sha of all crate versions will be marked using git tags.


Means to know all AT responses have been received

We are using an ANNA-B112 module with u-connectXpress for BLE. We are talking to the ANNA-B112 over uart using the ublxlib (https://github.com/u-blox/ubxlib) at_client, registering callbacks through uAtClientSetUrcHandler.
The problem we are encountering is that when we issue AT commands like AT+UBTGDCS to discover all of the characteristics for a given service, there are multiple responses followed by an OK.
For example this is what the command and responses look like using extended data mode to discover all the characteristics:
---><00><17><00>DAT+UBTGDCS=0,7,65535<0D>U
<---<00>6<00>E<0D><0A>+UBTGDCS:0,8,28,9,245468008B8511E48FBD0002A5D5C51BU
<---<00>8<00>E<0D><0A>+UBTGDCS:0,11,28,12,245468108B8511E48FBD0002A5D5C51BU
<---<00>8<00>E<0D><0A>+UBTGDCS:0,14,20,15,245468118B8511E48FBD0002A5D5C51BU<00>8<00>E<0D><0A>+
<---UBTGDCS:0,17,02,18,245468028B8511E48FBD0002A5D5C51BU<00>8<00>E<0D><0A>+
<---UBTGDCS:0,19,02,20,245468038B8511E48FBD0002A5D5C51BU<00>8<00>E<0D><0A>+
<---UBTGDCS:0,21,02,22,245468048B8511E48FBD0002A5D5C51BU<00><08><00>E<0D><0A>O
<---K<0D><0A>U
At the end of each response “U”, a callback from the at_client occurs as it should.
However, it appears there is no way to know when all of the characteristics have been received (When “OK” is received), and the module doesn’t respond to any further commands until it is has finished sending all responses.
Is there a mechanism that we are missing in the at_client to know when all responses have been received, or would we have to just know there are 6 characteristics to be discovered?

Hi there, and thanks for posting the issue.  It may be that there is more that can be said about this specific AT command (my colleagues from the BLE side of the business may respond on that) but I can answer for the general case of an AT command with a multi-line response with an unknown number of lines, which is that it is not easy to handle!
You can see an example of a similar case on the cellular side in the activateContext() function in u_cell_net.c.  In this case the cellular module sequence is:
AT+CGACT?
+CGACT: x,y
+CGACT: x,y
...
OK

...and, while the number of responses is bounded, in every case the number of responses received is smaller than the bound, and so it is a bit similar to your case.
As you can hopefully see from the code there, what we do is to lock the AT client, set a shorter timeout then usual (just to avoid hanging around unnecessarily) and issue uAtClientResponseStart() in a loop.  The loop exits either when get the thing we were looking for or there is a timeout.
Now there might be a better strategy in this specific case, I'll let my colleagues comment on that, but basically this is a scenario which is not well handled by our AT client APIs.  Very happy to consider any suggestions for improvement.

Project is discontinued


no longer works with current version of youtube

please update or remove from chrome store

Thanks for the report, at this time I have no time to work on it, PR's welcome, thanks.


New version: Appest.TickTick version <IP_ADDRESS>

This pull request is automatically generated by 🥟 Dumplings in #2930
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run


Fixing detection of HDD/SSD without partition

fixing that after #1297 the blitz.datadrive.sh script was not detecting hdd/ssd without any partiotion anymore

+cp into dev branch


The version isn't passed to to the app during InitChain for v0.34.x

on v0.34.x-celestia, but not main I don't think, the version is filtered when converting types
https://github.com/celestiaorg/celestia-core/blob/5a5e689942a700bb08d369b1821e28443b829619/types/protobuf.go#L100-L109
This causes InitChain to not pass the version, which causes the app to not store the param. Fortunately, this should only have an effect on new networks since existing networks are not on v2, and the version will be set after the upgrade.

@ninabarbakadze I already had this commit from running testground tests, so just pushed


[BUG] addDeveloperProduct throws an error.

Before posting a bug, be sure that someone else has not posted it already and it is an actual bug with noblox.js and not other frameworks like discord.js
Describe the bug
When calling addDeveloperProduct with the appropriate arguments, an error is thrown saying "You are not logged in!". I did some investigation in my own and found out that jar is undefined in checkDeveloperProductName.js
To Reproduce
Steps to reproduce the behavior:

Login using a token.
Call addDeveloperProduct with the appropriate args and wrap it around a try..catch and console.log the error.
Look in the console.

Expected behavior
I expected it to create a developer product and return a DeveloperProductAddResult

You must be authenticated to create a developer product. That error is because you are not calling and awaiting setCookie() before calling addDeveloperProduct(). This would be the case for any of our authenticated methods.
Using snippets from the documentation's Getting Started, and method examples:
const noblox = require('noblox.js')
const COOKIE = ''

async function startApp () {
  await noblox.setCookie(process.env.COOKIE || COOKIE)
  const { UniverseId } = await noblox.getPlaceInfo(6480087726) // Replace with the placeId you want to create the developer product in
  const developerProduct = await noblox.addDeveloperProduct(UniverseId, 'Developer Product Name', 1234, 'A developer product made using noblox')
  console.log(developerProduct)
}

startApp()

should return a response along the lines of:
{
  universeId:<PHONE_NUMBER>,
  name: 'Developer Product Name',
  priceInRobux: 1234,
  description: 'A developer product made using noblox',
  productId:<PHONE_NUMBER>
}

You only need to call setCookie() once, and it must be before calling an authenticated endpoint.

NOTE: It appears our current implementation doesn't support images yet. The method is using a www. endpoint, and they generally lack stability/documentation. I'll look into reverse engineering how images are handled for it and likely make a PR for that.

I found out what I was doing wrong. I put the universe ID incorrectly. Sorry!


aws_db_instance requires license_model parameter for some engines

https://www.terraform.io/docs/providers/aws/r/db_instance.html#license_model
The license model param is required for some db engines (oracle, sqlserver) but isn't accounted for in the resource in the module.
This will fail if you use the module to stand up a sqlserver SE instance, for example.

@shushry thanks for reporting! If you want to open a PR for this, we'll promptly review. We don't have any customers using SQL Server SE.

addressed in #26


MDCard - Need new event

Description of the Feature
Please enable users to use on_press and on_release events for MDCard.

@Kulothungan16
from kivy.lang import Builder

from kivymd.app import MDApp

KV = '''
MDScreen:

    MDCard:
        size_hint: None, None
        size: "280dp", "180dp"
        pos_hint: {"center_x": .5, "center_y": .5}
        on_press: print("on_press")
        on_release: print("on_release")
'''

class TestCard(MDApp):
    def build(self):
        return Builder.load_string(KV)

TestCard().run()


chore: clippy fixes

What
Add a clippy check to CI and make initial pass at fixing clippy errors.
At first the number of lints was way too high to tackle all at once.  However, disabling some that could be debatable allowed a lot of the obvious fixes to be done.
In future PRs the disabled lints can be addressed in batches to ensure so that it's not too overwhelming.
Why
Currently the only repo that requires that clippy is the CLI and this repo seems more important to have standard coding practices. Clippy can even help catch some logic errors.
Known limitations
[TODO or N/A]

One other thing to note.  Currently it should fail when run for the first time.  The reason is that the latest commit to main added two methods which return a result, but will never return an error. I kept it in partly as a check that CI should fail the first time and unlike the initial batch of changes it is an API change to remove the Result.

CI fails with error: rustup is not installed at '/home/runner/work/rs-soroban-env/rs-soroban-env/.cargo/ci/config.toml'
I'm not sure I understand how to fix it, but I suppose the reason has something to do with the newly introduced config.toml

@dmkozh fixed it. Was an ENV VAR for cargo home, which was from a previous attempt to have the clippy lints in a file.

Seems like there are some failures in guest library.

@dmkozh I also seem to get the following error if I ran that command locally:
cargo clippy --locked --target wasm32-unknown-unknown --no-default-features

I get:
error[E0152]: found duplicate lang item `panic_impl`
  --> soroban-env-common/tests/no_std/src/lib.rs:17:1
   |
17 | fn handle_panic(_: &core::panic::PanicInfo) -> ! {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: the lang item is first defined in crate `std` (which `soroban_env_common` depends on)
   = note: first definition in `std` loaded from /Users/willem/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libstd-a9c931054ca2959f.rlib
   = note: second definition in the local crate (`test_no_std`)

For more information about this error, try `rustc --explain E0152`.

@dmkozh I also seem to get the following error if I ran that command locally:
cargo clippy --locked --target wasm32-unknown-unknown --no-default-features

I get:
error[E0152]: found duplicate lang item `panic_impl`
  --> soroban-env-common/tests/no_std/src/lib.rs:17:1
   |
17 | fn handle_panic(_: &core::panic::PanicInfo) -> ! {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: the lang item is first defined in crate `std` (which `soroban_env_common` depends on)
   = note: first definition in `std` loaded from /Users/willem/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/wasm32-unknown-unknown/lib/libstd-a9c931054ca2959f.rlib
   = note: second definition in the local crate (`test_no_std`)

For more information about this error, try `rustc --explain E0152`.

That's likely because you're missing --features testutils (probably that should be fixed separately...)

Hey @willemneal sorry for the delay (and inevitable bitrot).
I've merged a run of cargo clippy --fix in https://github.com/stellar/rs-soroban-env/pull/790 and turned on clippy in CI without the style group in https://github.com/stellar/rs-soroban-env/pull/796. So that accomplishes maybe half or a third of what this PR was trying to do, but lays groundwork. Assuming you want to enable all of the extras (or even all the way to enabling the full style group) I'd recommend refreshing this PR in stages -- doing a handful of new lints at a time, since it's easier to review a small or medium-sized PR than a giant one.


types are not publishing to npm

The typescript definition file does not contain the Hooks.d.ts file specified in the package.json:

Thanks we already have an issue for that. Will try to get this fixed soon

https://github.com/react-navigation/hooks/issues/7#issuecomment-504774001


[language][move] Restrict "break" and "continue" to be top-level expressions

"break" and "continue" can be treated like "return" and "abort".
There is no reason to support things like "0 + break".
Motivation
Allowing break and continue as expression terms lets some strange inputs get through the parser: "&break", "-continue", "*break", "break.f", etc. Later phases of the compiler report error messages but they don't always make sense. It is better to be more restrictive about what gets parsed.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Adjusted tests to remove expressions that are no longer supported.

:umbrella: The latest upstream changes (presumably 75128d748266e958c0986fc341bfeeb36967fad0) made this pull request unmergeable. Please resolve the merge conflicts.

I'm going to close this. I've come to realize that the distinction between things in "Term" vs "Exp" has more to do with the presence of whitespace. "break" and "continue" do not have any whitespace-separated arguments, so they can stay in "Term". Eventually @tnowacki would like us to get to a grammar where we can intermix all expressions without parenthesis, but I'm not sure what it will take to get there.


Not able to use this module

I did all given in the readme page. But not working
What shal i do ?

hmm... what did you do? how are you using it?

Now it worked as i mentioned the flag-icon.css in angular.json file. Which
was not mentioned in readme page
On Mon 2 Jul, 2018, 8:36 PM Lipis<EMAIL_ADDRESS>wrote:

hmm... what did you do? how are you using it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lipis/flag-icon-css/issues/472#issuecomment-401836431,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGuJoATG28n5kUmIOZrsLcuw7Mrq62_Oks5uCjbpgaJpZM4U_X4V
.


closes: #1

Updated validations,py python script.
Fixed the behavior of the validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

@googlebot I signed it!


RPP Box filter HOST support

Adds optimized support for kernel size 3, 5, 7, 9 for U8, I8, F16, F32 bitdepths
Adds generic kernel support to handle any kernel size

@r-abishek
Addressed all review comments
Please take a look and let me know if any further changes needed


consumer return  RECONSUME_LATER but not get retry message

QAQ help me Why my consumer return  RECONSUME_LATER but no  get retry message;
but same code in my friend's computer can get retry message

Could you tell me which version you are using, it seems there is no issue with the latest version in my environment.

I will close the Issue first, but please feel free to reopen it if you have any other issues.

V4_3_0 and V4_7_0 all have this question

Have any properties can control  not  retry message ?
In my computer I try 3 version all have this question
but in my friend's computer can retry
his computer's rocketmq   version is same as me
why?

we encounter this question too，the rocketmq version is 4.5.1。
But when we install the version  to another server，the question goes away，interesting。

we encounter this question too，the rocketmq version is 4.5.1。
But when we install the version to another server，the question goes away，interesting。
Did you slove it?

After two day later, we sloved it。
The question is about delayOffset.json。As you know，the broker process persist SCHEDULE_TOPIC_XXXX offset to delayOffset.json。When we drop the store folder，we didn't noticed it generate a store/config folder automatic by broker。Whereafter，we reset broker，but the offset from delayOffset not matched the offset from SCHEDULE_TOPIC_XXXX，so the message in SCHEDULE_TOPIC_XXXX cannot enter %RETRY% topic。

Thank for your explanation
I do not slove it
How can i do to sloved the problem
Drop store folder and Reinstall rocketMq?

No need to reinstall, just to stop broker, drop store folder, and then start broker。Actually, you can check the rocketmq log, find that are there warn log like "Offset not matched. Request offset"。The relevant logic you can find from ScheduleMessageService 271 line。
Wish it helpful to you

I just encounter this question, but I'm not sure if they are the same question:
1、consumeGroup=ORDER-CONFIRM receive A Message TOPIC = "TDTP" key = "5279213024614400", After  consume fail, the code "return ConsumeConcurrentlyStatus.RECONSUME_LATER;", but not receive retry any more.
2、on the MQ console, use condition TOPIC = "RETRY%ORDER-CONFIRM" and key = "5279213024614400"  , can't find this message
3、on the MQ console, use condition TOPIC = "TDTP" and key = "5279213024614400", find this message, and this message was marked "CONSUMED"
before encounter this question, I upgrade rocketmq 4.1.x to 4.3.2,
1、 I install rocketmq-4.3.2 to anther directory,
2、 stop old  rocketmq-4.1.x
3、move rocketmq-4.1.x/store to rocketmq-4.3.2/store(the path configured in broker-x.properties)
4、start rocketmq-4.3.2
Are they the same question?

sounds the same question, you can check the rocketmq log, find that are there warn log like "Offset not matched. Request offset".

question

Yes, there are many log like this, and at the same time the message consume fail, the rocketmq had one log:
"storeerror.log:2021-02-06 16:26:28 WARN FlushConsumeQueueService - Offset not matched. Request offset: 354000000, firstOffset: 348000000, lastOffset: 354000000, mappedFileSize: 6000000, mappedFiles count: 1"
How to solve this problem without loss of messages (do not drop store folder),  upgrade to newest version? @spiritsx

maybe you could modify the delayOffset.json in store/config

maybe you could modify the delayOffset.json in store/config

@spiritsx
How to modify the delayOffset.json file? Leave it blank object like this?
{
"offsetTable":{}
}

I think it is ok，but I suggest you can try it in no prod environment. Leveling it blank will lead to reconsume all consume failed message, it seems like a simple way to slove it if you donot care repeat consume.

I think it is ok，but I suggest you can try it in no prod environment. Leveling it blank will lead to reconsume all consume failed message, it seems like a simple way to slove it if you donot care repeat consume.

thanks, I'll try it.


Port mapping does not work and 403 Forbidden

Good day,
I followed the instructions exactly, and then when the container was built and started, I saw I can not get to the web server via the IP address.
a netstat -tulpen then confirmed to me that port 80 was not mapped correctly
docker container ls ->
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
34d424847473 nginx:alpine "/docker-entrypoint...."   28 seconds ago Up 26 seconds <IP_ADDRESS>:32773->80/tcp, :::32773->80/tcp wsc-dockerized-nginx-1

f6313e90ded6 wsc-dockerized-php-fpm "/bin/sh -c 'start-c..."   28 seconds ago Up 26 seconds 9000/tcp wsc-dockerized-php-fpm-1

0d6ae048950f mysql:8 "docker-entrypoint.s..."   28 seconds ago Up 27 seconds 33060/tcp, <IP_ADDRESS>:32771->3306/tcp, :::32771->3306/tcp wsc-dockerized-mysql-1

978b1805c9b2 docker.dragonflydb.io/dragonflydb/dragonfly "entrypoint.sh drago..."   28 seconds ago Up 27 seconds (health: healthy) <IP_ADDRESS>:32772->6379/tcp, :::32772->6379/tcp wsc-dockerized-redis-1

netstat -tulpen ->

tcp 0 0.0.0:32770 <IP_ADDRESS>:* LISTEN 0<PHONE_NUMBER>3/docker-proxy
tcp 0 <IP_ADDRESS>:32769 <IP_ADDRESS>:* LISTEN 0<PHONE_NUMBER>5/docker-proxy
tcp 0 <IP_ADDRESS>:32768 <IP_ADDRESS>:* LISTEN 0<PHONE_NUMBER>1/docker-proxy
tcp6 0 0 :::22 :::* LISTEN 0 24554 2459/sshd: /usr/sbi
tcp6 0 0 :::32770 :::* LISTEN 0<PHONE_NUMBER>0/docker-proxy
tcp6 0 0 :::32769 :::* LISTEN 0<PHONE_NUMBER>3/docker-proxy
tcp6 0 0 :::32768 :::* LISTEN 0<PHONE_NUMBER>8/docker-proxy

I could not find any errors in the container either, which indicates that.
When I tried to connect to the website via http://IP:32770/, I got a 403 Forbidden HTTP Error.
I am not sure if this error is caused by the port mapping problem.

I solved the Port Mapping Problem by replacing this
ports:
- "80"

with this
ports:
- "80:80"

The Problem with "403 Forbidden" ist probably caused by public/WCFSetup.tar.gz
Unfortunately, after tar -xf WCFSetup.tar.gz i got the WCF-Master.tgz which is not unzipable
tar -zxvf WCF-master.tgz                                                                                2 ↵ ──(Tue,May09)─┘

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

Port 80 was probably in use already. To make it beginner friendly, i decided not to use dynamic port mapping for the Webserver.
As for the zip problem... That's strange. We use this by ourselves without any problems. Maybe it helps, if you start from scratch? The error looks like it wasn't able to download the tar all.

Port 80 was not bound. The port was just not mapped in the docker compose file from the container to the system.
I am unsure about the zip problem. Could you tell me the command you use to unzip the .tgz?

No Problem. :D
Here you can see what commands i executed
┌─(~/docker/wsc-dockerized/public)────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(ROOT@k8s-node1:pts/0)─┐
└─(15:26:47 on main ✹ ✭)──> ls                                                                                ──(Tue,May09)─┘
WCFSetup.tar.gz
┌─(~/docker/wsc-dockerized/public)────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(ROOT@k8s-node1:pts/0)─┐
└─(15:26:48 on main ✹ ✭)──> tar -tf WCFSetup.tar.gz                                                                                ──(Tue,May09)─┘
WCF-master.tgz
┌─(~/docker/wsc-dockerized/public)────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(ROOT@k8s-node1:pts/0)─┐
└─(15:26:58 on main ✹ ✭)──> tar -xvf WCFSetup.tar.gz                                                                                ──(Tue,May09)─┘
WCF-master.tgz
┌─(~/docker/wsc-dockerized/public)────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(ROOT@k8s-node1:pts/0)─┐
└─(15:27:03 on main ✹ ✭)──> tar -xvf WCF-master.tgz                                                                                ──(Tue,May09)─┘
tar: This does not look like a tar archive

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

wsc-dockerized-php-fpm-1  | gzip: invalid magic
wsc-dockerized-php-fpm-1  | tar: Child returned status 1
wsc-dockerized-php-fpm-1  | tar: Error is not recoverable: exiting now
When executing the docker compose, the first message from the wsc-dockerized-php-fpm-1 that appears is this.

Ah. I see the problem, I guess.


Menu is not responsive

The menu is not scrollable:

Reference:
https://pages.corifeus.tk
The whole:

For example in Bootstrap is scrollable:

@kara thoughts on this?

Any updates or work-arounds for this? Unfortunately this makes md-menu tough to use if there are more than a few options included. Thanks in advance!

it is still not working :(

Tracking this via #4270.
I'm working on a solution


Configurable Firewall Controller Version

Current situation

the firewall-controller version used in a cluster is not included in the shoot spec
it is not easily visible which firewall-controller version is
it is hard to further develop the firewall-controller because of the long loop: firewall-controller, metal-images, gepm

Wanted

controllerVersion should be fully configurable by the user with the shoot spec
there should be an additional field controllerVersionAutoUpdate which indicates whether gepm manages the controllerVersion field
gepm holds a default version in its imageVector

Constraints

if there are api changes in the objects btw. firewall-controller and gepm (FirewallSpec) those need to be visible with the version number! - we'll use semver for that
a gepm release supports only minor / patch level changes of the firewall-controller (cluster update with a new major release will be declined)
controllerVersion must be a released GitHub artifact of https://github.com/metal-stack/firewall-controller

How can we initially introduce this feature?

you need to get a new firewall image that has the firewall-controller self replacement enabled
older firewall-images work as expected (because the controllerVersion field will be omitted if empty during serialization)
you may enable the auto update to the firewall-controller version mentioned in gepm's imageVector with controllerVersionAutoUpdate: true
reconcilation works for clusters having the feature enabled as well as those that don't have it

How to do major version upgrades?

use the new firewall-controller in metal-images and release it
exchange firewalls and release gepm with the new major version of firewall-controller containing the api changes
Problem: reconcilation of existing clusters with old firewall-controllers will fail
ALTERNATIVE:
versioning the Custom Resource Definition for firewalls and support multiple versions in gepm

The gardener-resource-manager update has to be mentioned in our release notes.


Allow returning any error that implements std::error::Error

This allows the fetch handler to return any error type that implements std::error::Error. This will allow the user to choose how they want to handle errors (use worker::Error, anyhow, thiserror, etc.).
This also changes some behavior slightly:

If respond_with_error is enabled, this now uses Display to stringify the error instead of to_string.
The error logged is now stringified with Debug and with console_error instead of console_log.

cc @avsaase

Just wondering - would it make sense to get rid of respond_with_errors?
I guess that question is more related to the change in https://github.com/cloudflare/workers-rs/pull/524, but at the end of the day - it's now pretty trivial for application code redact all errors before returning from the handler (and it's a bit unexpected for that redaction to be the default)
Even if y'all agree, not sure what the policy is about breaking backwards compatibility is though, consider it a curiosity question rather than a hard push :)

Just wondering - would it make sense to get rid of respond_with_errors?
I guess that question is more related to the change in #524, but at the end of the day - it's now pretty trivial for application code to redact all errors before returning from the handler (and it's a bit unexpected for that redaction to be the default)
Even if y'all agree, not sure what the policy is about breaking backwards compatibility though, consider it a curiosity question rather than a hard push :)

I think its still useful for people to control whether and Error is returned to client. Its true that they may control this now via axum and IntoResponse for their error type, but I dont think that will apply to everyone.

Oké


Frequent issue with ambiguous language

Type: Bug
Failed to save 'FILENAME': The content of the file is newer. Do you want to overwrite the file with your changes?
I get this often, for some reason. The worst part is the ambiguity.
Is the content I'm seeing in front of my eyes the content that will be overwritten, or is that the content that will overwrite some other content? And either way, what is the "other"? Is there a way to see the diff? Is this recoverable in any way? As it is I'm afraid to choose either option because I have no clue what I am actually choosing.
VS Code version: Code 1.72.2 (d045a5eda657f4d7b676dedbfa7aab8207f8a075, 2022-10-12T22:16:26.920Z)
OS version: Linux x64 5.15.0-52-generic snap
Modes:
Sandboxed: No

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.73.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Fix actions

What this PR does / why we need it:
Which issue (if any) this PR fixes:
Fixes #
Any other useful info:

Fixed already


Use ISO-8601 dates in the changelog

The changelog dates should use leading zeroes for month and day.
Currently changelog entries look like this
## 3.1.18 (2023-9-1)

That is, the month and the day are without leading zeroes.
It would be nice if they would have leading zeroes.
## 3.1.18 (2023-09-01)

This would make dates compatible with ISO-8601 and more importantly with Common Changelog format which requires use leading zeroes in dates.

I think the relevant code is here. https://github.com/versionize/versionize/blob/02797afb5531174c53b14c7c0866cbf04c29a973/Versionize/Changelog/ChangelogBuilder.cs#L60


starterkit-mustache-demo are always fetch on init

Add a check if starter kits are already present in node_modules

@bmuenzenmeyer This one fails because require('starterkit-mustache-demo') cannot find starterkit-mustache-demo as a module. We had the same problem with edition-node – because those modules likely do not have an entry point, in which case require doesn't recognize the module being already present in node_modules

confirmed - https://github.com/pattern-lab/starterkit-mustache-demo/blob/master/package.json
on it

@raphaelokon please retest.
note every starterkit will need this same fix applied to it

Cheers. Will do!

This saved it … we probably need a better check in future but it is good to go for now. Thanks @bmuenzenmeyer


Trust both DOD and commercial certs when connecting to DMDC

DMDC's Identity Web Services recently changed from presenting a certificate signed by DISA to a certificate signed by Entrust. As a result, SSN<->EDIPI conversions required by both the Orders Gateway and by the DPS-to-login.gov bridge stopped working. The error Get https://pkict.dmdc.osd.mil/appj/rbs/rest/{more URL components}: x509: certificate signed by unknown authority appears in the logs.
So, instead of trusting only DOD-signed certs when connecting to DMDC, or trusting only commercial certs, trust both. That way, if DMDC changes its mind about using a commercial cert, especially when the current cert expires in March of 2020, our code will continue to work.

@chrisgilmerproj do you know what CAs are in our AWS environments? @jamesatheyDDS testing in experimental might be helpful

@jamesatheyDDS or @chrisgilmerproj can you add tests to make sure we don't have any regressions moving forward and to illuminate what's actually happening here?

Agreed, I'd also like to see some tests here.

@chrisgilmerproj do you know what CAs are in our AWS environments? @jamesatheyDDS testing in experimental might be helpful

@aileendds - I don't know what CAs are in AWS.  I'd have to introspect the secure migrations to figure it out.

@chrisgilmerproj @kahlouie What would a test look like for this integration with DMDC? They only allow specific client certificates to connect to their API - in our case, our staging and experimental DOD-signed certs can connect to their Contractor Test environment, while our production DOD-signed cert can connect to their production environment.
Do we have other unit tests that require network connectivity? Is it fair to block someone from committing if DMDC's servers are down?

This seems more like a monitoring issue than a unit test issue. What kind of health alert or monitoring thing can we set up to check the connection to DMDC in our environments?

@chrisgilmerproj @kahlouie What would a test look like for this integration with DMDC? They only allow specific client certificates to connect to their API - in our case, our staging and experimental DOD-signed certs can connect to their Contractor Test environment, while our production DOD-signed cert can connect to their production environment.

I would say we should have some kind of dummy DoD cert package to test this code with. Specifically something we can pipe into dodCACertPackage to make sure parsing is happening and we're getting the certs added to the x509 cert pool.

Do we have other unit tests that require network connectivity? Is it fair to block someone from committing if DMDC's servers are down?

We don't have unit tests against network connectivity. That being said, we should gracefully handle this kind of situation in the code. So if RBS is down we shouldn't be throwing 5XX errors in the app. I'd prefer we throw a 421 Misdirected Request.

The 421 (Misdirected Request) status code indicates that the request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.

And something we should address in another PR: in the case that we can't get the EDIPI what should be the fallback behavior of our app?

This seems more like a monitoring issue than a unit test issue. What kind of health alert or monitoring thing can we set up to check the connection to DMDC in our environments?

We should put this on the Infra backlog. We could probably create a Route53 health check. We also have an outstanding issue to create a custom health check Lambda for things that Route53 can't check for us.

@chrisgilmerproj - The documentation for 421 does not match this situation, so I don't think it's an appropriate response. That is meant to refer to the original request, not the secondary request to the 3rd party. This situation is closer to a proxy, and the documentation explicitly states that it should not be returned by a proxy.
The fact that we're calling RBS is an internal implementation detail, which the caller doesn't necessarily need to know about so I think 5xx makes sense. If RBS provides more detailed error codes, we can return a 503 instead of a 500 if it's a temporary issue.

@aileendds I agree. We should know when our dependencies are down, so we should give 500 level errors, but we should add more info so we can change the alert to go off separately from the 500 errors that are caused in our application.

@chrisgilmerproj It is reasonable to have a unit test that the DOD CA cert package file is being parsed and loaded correctly. At some point in the future, new DOD CAs will be created and the package will need to be updated.
The DOD CA package is not touched by this PR, so is adding a unit test for that a blocker? I need this PR accepted to demo the Orders Gateway to RADM Clarke...

@chrisgilmerproj It is reasonable to have a unit test that the DOD CA cert package file is being parsed and loaded correctly. At some point in the future, new DOD CAs will be created and the package will need to be updated.

Yeah, that's good enough I think.

The DOD CA package is not touched by this PR, so is adding a unit test for that a blocker?

I'm just saying we need a unit test for the change to the method you're updating. If there's an existing test that covers this then that's great. If not then we've been implementing new test-coverage rules that mean we need to add a test here before merge.

I need this PR accepted to demo the Orders Gateway to RADM Clarke...

I'd be willing to provisionally accept this with a promise we get a test in a follow up PR.

@chrisgilmerproj - The documentation for 421 does not match this situation, so I don't think it's an appropriate response. That is meant to refer to the original request, not the secondary request to the 3rd party. This situation is closer to a proxy, and the documentation explicitly states that it should not be returned by a proxy.
The fact that we're calling RBS is an internal implementation detail, which the caller doesn't necessarily need to know about so I think 5xx makes sense. If RBS provides more detailed error codes, we can return a 503 instead of a 500 if it's a temporary issue.

My experience is that 5XX means there was an error we were unable to handle. We ought to handle this type of situation and return a better code so the client can do something about it.  Also, 5XX errors will end up paging the application on-call. If the application on-call cannot do anything about this then they ought not be paged, which I think is the case here.  Again, returning a 4XX so a client can handle the problem gracefully would be better in my opinion.

@aileendds I agree. We should know when our dependencies are down, so we should give 500 level errors, but we should add more info so we can change the alert to go off separately from the 500 errors that are caused in our application.

We can't differentiate 5XX errors at the ALB -> PD level. So any 5XX will get bundled up to page the on-call.  Again, if Truss has no power to handle this issue then we need to communicate to the requesting client what needs to happen next.

5xx means the server failed to process a valid request. 4xx means the client provided an invalid request. In this specific situation, it was an issue on our end that the on-call should have been notified of and fixed (i.e. with this PR). There is nothing the client could have done to their request to make the server return a valid response.
If in the future RBS is temporarily down and we can identify that it's temporary, then we can handle it differently. @jamesatheyDDS do you know if RBS returns granular error codes? I still think this should be 503 and not 4xx though.

@aileendds @chrisgilmerproj Testing in experimental successful; at least for DMDC's current cert, experimental had the right CA in its system bundle.

@aileendds Yes, RBS does have some granular error codes, but they are not HTTP status codes. Instead, the body of the response is an XML document rooted with <RbsError>. The iws package you and I wrote does parse this, but doesn't do anything different for different RBS error codes.
If the documentation is to be believed, here are the possible codes:

5xx means the server failed to process a valid request. 4xx means the client provided an invalid request. In this specific situation, it was an issue on our end that the on-call should have been notified of and fixed (i.e. with this PR). There is nothing the client could have done to their request to make the server return a valid response.
If in the future if RBS is temporarily down and we can identify that it's temporary, then we can handle it differently. @jamesatheyDDS do you know if RBS returns granular error codes? I still think this should be 503 and not 4xx though.

I'd like to change our code so that we can process the request by returning some kind of valid information to the client so the client can smartly handle this. I'm sure we can all hop on a zoom sometime and have a technical discussion about what to do. But I'd prefer that we handle the RBS return codes and also gracefully manage it if RBS is down or not taking requests from us.
Can either @jamesatheyDDS or @aileendds follow up on this? I'd love to get some resolution.  And in the meantime I have added a task to my backlog to figure out how we monitor these services.


Update base to 20211130

https://github.com/msys2/msys2-installer/releases/tag/2021-11-30

Thanks!


multiple instances

can this program be run with multiple sound cards simultaneously?

Time permiting, I'll test and see.  I suspect it will work.  I use multiple instances of WSJT-X all the time.  Only problem might be the All_WSPR.txt path.  I had some difficulty getting FSKView to run (initially) and surmise it was a path problem.

I tested running two instances with different audio streams.  Suprisingly, I could not get it to work despite WSJT-X and Argo running fine in that configuration.  Two instances of FSKView will run using the same sound stream, but I don't see a need for that.

Two instances of the same FSKview.exe are running well on my system using two different audio inputs
Importantly, to use them as grabbers they must be configured to save with different filenames (arrow)
Since this is tested/working, I'll close this issue


Config for Pre-Release 2 Content and Bug Fixes

-Changed Flora Behaviour config to Miscellaneous
-Added config for Fire Charge Explosions
-Added a config for the Cured Jerky Effect

-Fixed the issue with biome seed changing between server restarts (I think)


Add ability to "lock deployments"

A small group of users (i.e. those with a separate permission setting) should have the ability to lock/unlock environments for deployment.
It would be good if the locking could be set for a scheduled time (e.g. "please lock between 1pm and 3pm"). Also it would be good if the locking could be set up as a repeating weekly schedule.
Optionally, people without the permission could click "request deployment" and the person that locked the environment could approve one a case-by-case basis.
Use cases:

A client needs to lock their UAT environment because they're using it for a big demo and doesn't want it broken
Prevent Friday deployments without approval

@sminnee Is this a good case for a module? Functionality like this seems less useful for most users.


Fix/Separate gendc bin file

Context or motivation
Similar as https://github.com/fixstars/ion-kit/issues/266
Gendc buffer from two sensors will split and store into two bin file
Goal
we want save one in each
TODO

[x] separate them and store one in each bin file,
[x] add prefix to determine filename (eg. prefix = "gendc_0" --->  bin file name:  gendc_0.bin)

resolve in https://github.com/fixstars/ion-kit/pull/268


Add comment field for need help option

For https://trello.com/c/CJRdMIYn/40-allow-text-comments-to-be-left-when-a-user-needs-help-tagging-this-and-display-this-comment-in-flagged-view
See screenshots below

Before

After

Yeah, as briefly discussed offline, the main reason is probably that we don't know how long the text comment would be, and it might look strange when it goes over multiple lines. I've add some warning alert styling to the comment to make it pop a bit more, but will discuss with Luke about what her prefers...

I've deploy this to integration, perhaps we also want to include the styling for the "Suggested topic" flag? See the screenshot below with items with each flag.

@tomsabin sounds good, I'll give it a go as it would be nice to standardise the styling


Invalid selector generated for psuedo-elements with default config

Describe the bug
When using the default settings for the isolateInsideOfContainer strategy, an invalid selector is generated for pseudo-elements, e.g:
*:where(#somecontainer,#somecontainer *),
::before:where(#somecontainer,#somecontainer *),
::after:where(#somecontainer,#somecontainer *) {
  box-sizing: border-box; /* 1 */
  border-width: 0; /* 2 */
  border-style: solid; /* 2 */
  border-color: #e5e7eb; /* 2 */
}

::before:where(#somecontainer,#somecontainer *),
::after:where(#somecontainer,#somecontainer *) {
  --tw-content: '';
}

Apparently, not all pseudo-classes can be compounded with a pseudo-element. This appears to include :where:
https://www.w3.org/TR/selectors/#pseudo-element-states
It seems that as of now, the only pseudo-classes that should be considered valid are the following:
https://www.w3.org/TR/selectors/#useraction-pseudos
As a result, Tailwind's utilities for pseudo-elements as outlined below do not work as expected, especially when not specifying content-:
https://tailwindcss.com/docs/hover-focus-and-other-states#pseudo-elements
Expected behaviour
There are workarounds (e.g. using remove or ignore or adding content-), but I didn't see anything in the documentation about this behaviour, so it would be good to highlight it there. Maybe this particular preflight style could also be handled differently by default, but I'm not really sure what the best option is there.
Screenshots
Given the following, we expect a blue square:

should have blue square after

With ignore: ["::before", "::after"]:

Default settings (without ignore):

Hello, I've fixed this issue!
This is what I've done:
I have identified the issue with the invalid selector generation for pseudo-elements in the isolateInsideOfContainer strategy. The problem was that the :where pseudo-class was being incorrectly combined with pseudo-elements like ::before and ::after. To fix this, I've modified the isolateInsideOfContainer function in the src/strategies.ts file to handle pseudo-elements separately.
Here's a summary of the changes:

Added a function to detect pseudo-elements.
Modified the isolateInsideOfContainer function to handle pseudo-elements differently.
Updated the selector generation logic to ensure proper handling of pseudo-elements.

These changes should resolve the issue with invalid selectors for pseudo-elements while maintaining the existing functionality for other selectors.
I also created pull request: https://github.com/Roman86/tailwindcss-scoped-preflight/pull/59

[!CAUTION]
Disclaimer: This fix was created by Latta AI and you should never merge before you check the correctness of generated code!

This bug was fixed for free by Latta AI - https://latta.ai/ourmission

hi @iranana and thanks for reaching out! Had no time to dive into it yet. Will be carefully reviewed and fixed.
Fixed. I tested the case you provided - it's good now. Although tests pass well, please check the beta version and confirm that there is no any degradations on your side:
npm i tailwindcss-scoped-preflight@beta

npm i<EMAIL_ADDRESS>

@Roman86 thank you for all your work on this library :smile:

hi @iranana ! My fix caused another issue with pseudo-elements: #60
Just fixed it. The latest tag temporarily moved back to v3.4.6. Please try the latest fix.
npm i<EMAIL_ADDRESS>
or
npm i tailwindcss-scoped-preflight@beta

This fixed versions is not yet tagged as latest. Until confirmed.


Anchira MissingFieldException

Source information
Achira 1.4.5
Source language
English
Steps to reproduce

Go to sources
Press Anchira

Expected behavior
Should show list of manga and be able to read them.
Actual behavior
It keeps saying that Missing Field Exception and won't load.
Mihon/Tachiyomi version
0.15.3
Android version
Android 12
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Update your extension. The current version is 1.4.11

I just updated it 1.4.5 though. How fast was the new update?


Using stash with array index

This is a simple question about usage and if you think this should rather be asked on Stackoverflow, let me know. On SO you get at least some reputation points for answering :-)
I'd like to store values I got on the value stack in the global stash for later availability. I have a C++ class wrapper for such values and am thinking about how to store the managed value. I could convert the wrapper address to a string and use this as property name. However, what if I'd use the address (or a hash made of that) like an array index? Would that internally create a huge array? Something like this:
void ScriptingContext::stashValue(duk_idx_t index, void *reference) const {
  index = duk_normalize_index(_ctx, index);
  duk_push_global_stash(_ctx);
  duk_dup(_ctx, index);

  auto hash = std::hash<void *>{}(reference);
  duk_put_prop_index(_ctx, -2, static_cast<duk_uarridx_t>(hash));

  duk_pop(_ctx);
}

The internal array implementation has two different storage approaches:

A flat array of tagged values (duk_tval) with no explicit keys. This is for typical dense arrays.
A plain key/value storage with explicit string keys. This is used for very sparse arrays.

If you use random indexes, the array will fall back to the second storage approach so it won't become huge. However, the per entry cost will be larger than for a normal dense array because the key is stored explicitly, and the key is coerced to a string.

This is a simple question about usage and if you think this should rather be asked on Stackoverflow, let me know. On SO you get at least some reputation points for answering :-)

In general my hope is that this repo would be for issues regarding changes to Duktape itself, and SO and other programming sites for "how to do X" questions. Of course, sometimes that line is not clear, e.g. when a question leads to some development ideas. So it's not a big deal either way.

I see - in that case I can also just use a property and avoid the hash computation. Thanks.
Re: posting questions, I'll try to follow your advice!

I see - in that case I can also just use a property and avoid the hash computation. Thanks.

That's the situation right now.
The answer might be different if the Duktape internal code was able to store non-string keys without coercion. The main challenges with that are:

Keys take more space than they do now (they are plain duk_hstring pointers at present). This might not be an issue if duk_tval was a tagged pointer as it would take the same space.
All keys must behave "as if" they were strings, so property lookups need to be able to find the key in any format, from any input format. This is easiest if the partition is strictly defined, e.g. all keys looking like integer strings are always stored as integers, other keys as strings (or symbols).

There's also the question of the ES2015 Map datatypes. I've hoped to use the same data structure for them, so maybe if that succeeds, then sparse integer keyed objects would behave better too.

@mike-lischke If I understand your use case right, you're trying to pin heap pointers, in which case you don't even have to hash, you can just use the pointer as a key directly.  The pointer is guaranteed not to change over the lifetime of the object.
Here are my refcounted functions to do what you want to do:
ref: https://github.com/fatcerberus/minisphere/blob/v4.8.6/src/minisphere/utility.c#L212-L255
unref: https://github.com/fatcerberus/minisphere/blob/v4.8.6/src/minisphere/utility.c#L301-L337
See also #176.

Seems we all end at the same solution, some sooner, some later :-D. Yes, this is essentially what I'm doing here. Using the heap ptr is a good idea, if there were add_ref and dec_ref functions in duktape/C.


Fix compile with -DLOVR_ENABLE_HEADSET=NO

The event code was using one of the headset string tables, so there was a link error.
Tested this on mac and it seems to work.

Thanks!


Windows bootcamp docs?

Problem description
Should there be any docs for Docker-For-Windows running on a Mac using Bootcamp?
There's an odd/not-officially-documented procedure to get virtualization enabled and perhaps it could be of value to make a separate doc pertaining just to bootcamp and not pollute main documentation with the procedure or any guidance
ex.
Problem location

Other: No documentation

Project version(s) affected
n/a
Suggestions for a fix
If it makes sense to be included, add docs about how Docker for Windows does indeed work on Windows Bootcamp but there is an actual step that needs to be taken from the MacOS side
ex.
### Virtualization on Windows Bootcamp (Mac)

If you are on a capable Mac machine using [Bootcamp](https://support.apple.com/en-us/HT201468) to run Windows10 Pro, you can enable virtualization by setting Bootcamp/Windows as the system startup disk:

(Apple Menu in top left) > System Preferences > Target Disk > Bootcamp

cc: @akimd

This oddly works!

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


Fix undefined planid type error.

The reason for the error is because back button is clicked before the plan is done loading.
When clicking back button, we set selectedPlanId in store to undefined.
And for loading a plan, we dispatch below three actions:
PlanDirectory/SelectPlan
EpicTimeline/PortfolioItemsReceived
PlanDirectory/UpdateProjectsAndTeamsMetadata
So if the back action is completed before all actions take place, our program will try to find the plan to update with an undefined plan id, thus the type error.
In this PR. I have done two things.

disable back button if loading status is not yet loaded.
use the planToUpdate's id instead of selected plan id when updating a plan.

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


add pigment cell differentiation terms

Please add leucophore differentiation, erythrophore
differentiation and cyanophore differentiation as
children of pigment cell differentiation (sensu
vertebrata)GO:0043358.  All of the regulation children
as applied to iridiphore differentiation and
xanthophore differentiation may be applied similarly.
Definitions:
leucophore differentiation
The process whereby a relatively unspecialized cell
acquires the specialized features of a leucophore cell.
Leucophores are pigment cells derived from the neural
crest containing uric acid or other purine crystals,
deposited in stacks called leucosomes giving them a
white appearance.
erythrophore differentiation
The process whereby a relatively unspecialized cell
acquires the specialized features of an erythrophore
cell. Erythrophores are pigment cells derived from the
neural crest containing pteridine and/or carotenoid
pigments in structures called pterinosomes or
erythrosomes, giving them an orange to red appearance.
May be synonymous with xanthophores, but designated by
their coloration.
cyanophore differentiation
Cyanophores are pigment cells derived from the neural
crest containing a blue pigment of unknown chemical
composition, found in fibrous organelles termed cyanosomes.
erythrophore differentiation
The process whereby a relatively unspecialized cell
acquires the specialized features of an erythrophore
cell. Erythrophores are pigment cells derived from the
neural crest containing pteridine and/or carotenoid
pigments in structures called pterinosomes or
erythrosomes, giving them an orange to red appearance.
Update xanthophore differentiation GO:0050936 definition:
The process whereby a relatively unspecialized cell
acquires the specialized features of a xanthophore
cell. Xanthophores are pigment cells derived from the
neural crest containing pteridine and/or carotenoid
pigments in structures called pterinosomes or
xanthosomes, making them yellow to orange in
appearance. May be synonymous with erythrophores, but
designated by their coloration.
Update iridophore differentiation GO:0050935 definition:
The process whereby a relatively unspecialized cell
acquires the specialized features of an iridophore.
Iridophores are pigment cells derived from the neural
crest containing guanidine or other purine crystals
deposited in stacks called reflecting platets or
iridisomes, giving them a silver, gold, or iridescent
appearance.
Reported by: mellybelly
Original Ticket: "geneontology/ontology-requests/3174":https://sourceforge.net/p/geneontology/ontology-requests/3174

thanks www.movied.org


Fix SDK Playground Export

Summary
Next 14 removed the next export command in favor of the output: export in the next.config file
How did you test your changes?
yarn build

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


fix: correctly analyse exported endpoint methods during build

fixes https://github.com/sveltejs/kit/issues/10984
Previously, the endpoint metadata would never be populated as described in the issue. However, I think it was only used in the Vercel adapter to fire off some warning https://github.com/sveltejs/kit/blob/20d2fe7dc5b9d181788889c45aea1e3745222c82/packages/adapter-vercel/index.js#L562-L593
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

would it be too hard to add a test for this one?

However, I think it was only used in the Vercel adapter to fire off some warning

IIRC the history here is that the arc.codes adapter needed to know which methods existed on each route. It was complicated and no-one was actually using it so we stopped maintaining it long before SvelteKit went stable, but kept the metadata around. Not super valuable but probably not worth killing off either


Help needed - empty report is generated

Thank you for sharing the code with the community!
I am unable to get this script working on my git repo.
Would you be able to share "Invoke-FourKeyMetricsReportGeneration" invocation sample? I am guessing that some of my parameters are incorrect/wrong format but I am not sure which.

You're very welcome @jzoran05! Apologies for the slow reply.
Here's an example taken (almost) directly from one of our internal products:
$CheckoutLocation = Resolve-Path "C:\Checkouts\RepositoryRoot"
$ReportVersionNumber = Get-Date -UFormat "%y.%m.%d%H%M%S"

Invoke-FourKeyMetricsReportGeneration `
            -OctopusFeedApiKey $OctopusFeedApiKey `
            -CheckoutLocation $CheckoutLocation `
            -ProductName "Exciting Product" `
            -ReleaseTagPattern "releases/*.*" `
            -FixTagPattern "releases/*.**/fix" `
            -ReportPackageName "FourKeyMetrics-ExcitingProduct" `
            -ReportVersionNumber $ReportVersionNumber `
            -StartDate "01/01/2018" `

Does that help at all?

Thanks! It is working now!

That's excellent news.
Can I ask what you had to change to get it working?
Perhaps I'll be able to make it clearer for other people who try to pick this up.


Research: Storing generated subgraph docs on IPFS

which Filecoin integration would be easiest to leverage? the most cost-efficient?

ETHGlobal Guides

https://ethglobal.com/guides/verifying-storage-on-filecoin-tw629#incentivized-decentralized-storage
https://ethglobal.com/guides/introduction-to-libp2p-odsqg

Filecoin Storage on-ramps

https://boost.filecoin.io/
https://estuary.tech/
https://web3.storage/
https://nft.storage/
https://www.lighthouse.storage/

Retrieval market

Saturn

Start storing

Applied for access to Estuary


fix: Menu drop to generate token on console.

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description

Adding an option at the drop down menu for the user to generate the bearer token on the console.
Related Tickets & Documents

fix #364
Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

@open-sauced/triage

LGTM


[VL] Read OrcFile error when schema in Orc file and the table file don't consist

Backend
VL (Velox)
Bug description
when the schema in Orc file is different from the table schema(especially the field name), the gluten read error. as follows:
schema in ORC file:

the user table is:
CREATE TABLE parquet_test
(
treatment TINYINT,
numerator DOUBLE,
denominator TINYINT,
numerator_pre BIGINT,
denominator_pre TINYINT,
Y DOUBLE,
X1 INT,
X2 INT,
X3 INT,
X3_string STRING,
X7_needcut BIGINT,
X8_needcut BIGINT,
weight DOUBLE,
distance DOUBLE
)
then execute the query:
val df = spark.sql( "SELECT count(Y) from udf_table")
a incorrect value returns,

but use query: val df = spark.sql( "SELECT count(_col5) from udf_table")
return ok;

Spark version
None
Spark configurations
No response
System information
No response
Relevant logs
No response

Low version hive-orc file not contain field name, only with field index. I will try to fix it.

Low version hive-orc file not contain field name, only with field index. I will try to fix it.

you are right, mainly compact for lower version. thx!

Low version hive-orc file not contain field name, only with field index. I will try to fix it.

velox has already support using different schema(table schema and file schema )，user need to add a schema to create hive table handle

https://github.com/apache/incubator-gluten/blob/main/cpp/velox/substrait/SubstraitToVeloxPlan.cc#L1094

Yes, we can pass the table schema parameter (dataColumns) when creating a HiveTableHandle, but currently it's set to nullptr.
https://github.com/apache/incubator-gluten/blob/main/cpp/velox/substrait/SubstraitToVeloxPlan.cc#L1129
https://github.com/apache/incubator-gluten/blob/main/cpp/velox/substrait/SubstraitToVeloxPlan.cc#L1094

@liujp @kecookier Any solution for this? I also met this problem.

@liujp @kecookier Any solution for this? I also met this problem.

Now I add a schema table to ReadRelNode, and serialize it to Protobuf LocalFiles. gluten deserialize the schema in LocalFiles, and the pass the schema to HiveTableHandle. But for ORC file, this schema is only the top level, for the columns which has child type, this schema is not unabridged. For this condition, ORC reader should reuse the parquet reader.

@ccat3z


Not able to export the value of an object from a response-body array

Description
Not able to the access the exported value from another spec file when i am trying to export the value of an object from a response-body which is having data-type as array.
Steps to reproduce

Create a Spec file and add And export objectValue = response-body.array[0].object in tryStub.spec after response body and add the path in specmatic.json file.
Create another Spec(try2Stub) file to import the response and add this file in the specmatic.json file.
Run this script: specmatic test --host=localhost --port=5000 --env=local.

Expected behavior
response-body.Array[0].object should return value of the object.
Screenshots
In the screenshot i am exporting the response.

In the screenshot i am import the response.

Added the files in baseUrl and in specmatic.json

Error on running the 2 files.

System Information:

OS & version: [ubuntu 20.04]
Browser & version: [chrome - Version 92.0.4515.131 (Official Build) (64-bit)]
Specmatic version: [0.28.5]
JDK version: [11.0.11]

Thanks for reaching out @Vinstan-gif .
Apologies for the delayed response.
We'll have a look at this, but also want to check if you are still facing this issue

@Vinstan-gif apologies for the long radio silence on this. We have since
The capability you are using (export) was built for Authentication where we wanted to use the token from a auth response in making API calls.
We have since moved from Gherkin based DSL to OpenAPI specification which has inbuilt support security schemes. Here is a detailed overview about how we handle authentication and authorisation for OpenAPI.
https://specmatic.in/documentation/authentication.html
Closing for now. Please feel free to reopen if you have any more related questions.


MQTT Lock Topic Option is not available

I am running version 1.3.1 with the official blue board, under the hardware setting, I could not find MQTT relay topic to set to.
I have tried to upload all the different .bin available under release of 1.3.1
Please advice.
Thanks again for great project.

MQTT documentation covers this. My apology.
https://github.com/esprfid/esp-rfid/blob/dev/README-ADDON.md


support GET /2/users/me #183

Closes #183

Codecov Report

Merging #184 (b53295e) into main (9dde482) will decrease coverage by 0.11%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##             main     #184      +/-   ##
==========================================
- Coverage   92.22%   92.11%   -0.12%
==========================================
  Files          49       49
  Lines        1994     2016      +22
==========================================
+ Hits         1839     1857      +18
- Misses        117      121       +4
  Partials       38       38

Impacted Files
Coverage Δ

users/types/user_lookup_parameter.go
92.00% <80.00%> (-2.29%)
:arrow_down:

users/types/user_lookup_response.go
100.00% <100.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 9dde482...b53295e. Read the comment docs.


show tile marking manually detected players

as a player i would like to see all the players that i have manually reported with tile markers

This should be customizable. When 15 bots are stacked on top of each-other i have to use entity-hider to hide reported bots...

Such a feature might get rejected if PR'ed to the hub, see this comment on a different plugin with generic player highlighting.

Such a feature might get rejected if PR'ed to the hub, see this comment on a different plugin with generic player highlighting.

Good find. Important to take this into account.

Good find. Important to take this into account.

perhaps hiding reported players instead of highlighting?

Good find. Important to take this into account.

perhaps hiding reported players instead of highlighting?

There is no way to selectively hide players in Runelite's API.

I currently use entity hider and my ignore list.
That’s my advise ?
On Mon, Apr 26, 2021 at 1:38 PM Cyborger1 @.***> wrote:

Good find. Important to take this into account.
perhaps hiding reported players instead of highlighting?
There is no way to selectively hide players in Runelite's API.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Bot-detector/bot-detector/issues/22#issuecomment-827023598,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFWKSR6Q33OIELUZIR5BKDTKWQKHANCNFSM43LHVBQA
.

--
--Jesse D. Stein


Bump Homebrew from v0.2.14 to v0.2.59

Codecov Report

Merging #993 (bb2f556) into main (2c9f4c2) will increase coverage by 0.47%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #993      +/-   ##
==========================================
+ Coverage   94.27%   94.74%   +0.47%
==========================================
  Files         327      323       -4
  Lines       15656    15516     -140
  Branches       12        0      -12
==========================================
- Hits        14759    14700      -59
+ Misses        897      816      -81

Flag
Coverage Δ

dotnet
94.74% <ø> (-0.10%)
:arrow_down:

typescript
?

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

Impacted Files
Coverage Δ

...cep.Core.UnitTests/FileSystem/FileResolverTests.cs
79.31% <0.00%> (-20.69%)
:arrow_down:

.../Bicep.Core.UnitTests/Assertions/BaselineHelper.cs
63.63% <0.00%> (-15.91%)
:arrow_down:

src/Bicep.Core.UnitTests/Utils/CompilerFlags.cs
20.00% <0.00%> (-13.34%)
:arrow_down:

src/Bicep.Core/FileSystem/PathHelper.cs
96.15% <0.00%> (-3.85%)
:arrow_down:

...Bicep.Core.UnitTests/FileSystem/PathHelperTests.cs
100.00% <0.00%> (ø)

src/vscode-bicep/src/utils/telemetry.ts

src/vscode-bicep/src/extension.ts

src/vscode-bicep/src/utils/logger.ts

src/vscode-bicep/src/language/client.ts


Expaandable cards nchhabra25 branch

Developer Checklist

[ ] Followed guidelines mentioned in the readme file.
[ ] Followed directory structure. (e.g. ProjectName/{USERNAME}/...yourfiles)

Summary
These are cards which expand when you click on them, this is also the first challenge of brad traversy's 50 days 50 Javascript projects
Screenshot

@Nchhabra25 change firectory name from ExpandableCard to ExpandableCard/Nchhabra25, thank you.

Hey, done it!

Adding a good README.md, I think will go on a long way as a consistent practice.


[feature] Add custom headers to explorer-api request

What problem does this new feature solve?
Adds user-agent and referer headers in explorer-api requests
Describe the solution you'd like

user-agent that follows the pattern <web3modal version>/<core sdk version>/<operating system>
referer containing the name provided in the sdk metadata (with no spaces)

example:
headers: {
 user-agent: 'w3m-flutter-1.0.0/flutter-core-1.5.7/ios-16.5',
 referer: 'ExampleAppName'
}

This is done as of 1.2.0


Upgrade to minimum iOS version 10.0

What
Where/Who

JIRA Issue
JIRA_TICKET_ID

People Involved
@via-guy

Notes on PR descriptions
Background
Sorry, I can't open tickets or anything, I just needed to create this change for our project and was hoping we could update directly at the source.
I had a compilation issue but it was with an older version of Leanplum-iOS-SDK and it looked like a good idea to upgrade the project to min SDK iOS 10. Seems that wasn't really necessary, but if you'd like to do it then here's how. 🤷
Implementation

Deleted any code that was marked as deprecated in iOS 10.0
Deleted any code that supported pre-iOS 10.0
Removed redundant markings of API_AVAILABLE(ios(10.0))
Updated podspec and project files to iOS 10.0 deployment target

Testing steps
N/A
Is this change backwards-compatible?
No, hence incrementing the major version in sdk-version.txt.

@nzagorchev how can I push this forward? I think it will clean up the code base significantly.

FYI: https://github.com/via-guy/mparticle-apple-integration-leanplum/actions/runs/6264835345/job/17012380706

Thank you @via-guy for this contribution. Is this blocking your integration? Are you integrating with mparticle and what is the impact?

@nzagorchev no, it's not blocking me anymore. I thought that it was, originally, but I managed to resolve the issue. Still, seems a bit unnecessary to continue backwards-supporting so far.
The original issue itself was in NotificationsProxy.swift with
@objc @available(iOS 10.0, *)
public lazy var pushNotificationPresentationOption:UNNotificationPresentationOptions = []

Some compiler didn't like the combination of @available with lazy var. Upgrading the minimum target seemed like the easiest solution.

@nzagorchev the only thing we're blocked with is upgrading to a newer version of Leanplum. Using the mParticle integration we're stuck on 4.1. We need this fix implemented and released so that my other pull request can be merged.

@nzagorchev seems it's not blocking us anymore. I think it'll still be nice to upgrade anyway, just to clean the code. Supporting iOS 9 is pretty excessive at this point.

@nzagorchev any update?


Add column on microcontroller architecture

Possibly most initiatives will use some sort of digital microcontroller.
Maybe it would be useful to have a column to indicate whether it's Arduino or something else?

Good idea. I have done. There of course is much more to an architecture than that, but this won't hurt.


Running Installer when already Installed

Microsoft PowerToys version
0.55.2
Running as admin

[X] Yes

Area(s) with issue?
Installer
Steps to reproduce
When I run the installer with an existing version or high already installed the installer returns exit code 1 which doesn't tell me anything.
✔ Expected Behavior
Exit code of either 1638 (ERROR_PRODUCT_VERSION) or 1604
❌ Actual Behavior
Exit code 1
Other Software
No response

Hi there! Can you attach the log file from the installer? Also, please try out release 0.56.1 which was just released! /needinfo

PowerToysSetup-0.55.2-x64.log
I tried using version 0.56.1, which instead gives an elevation prompt, even though nothing is needed. Log attached for 0.56.1 too.
PowerToysSetup-0.56.1-x64.log

Error here seems to be:
[4E78:6168][2022-02-28T19:02:06]i360: Creating a system restore point.
[4E78:6168][2022-02-28T19:02:06]w363: Could not create system restore point, error: 0x80070422. Continuing...

But that's not impeding install. Now I get it, this is about returning other error codes. Guess WixBootstrapper doesn't work like that, it tries to install everything. If everything is fine, it sees that as a success.

Could we change this?

Is this still an issue with the latest version?

Version 0.63 returns exit code zero for already installed. Not great but works. If I try to install 0.62 when 0.63 is already installed it still returns 1


fix(client): PodMeEpisode from_json → from_dict

Not sure if this version of podme_api is WIP, but sharing a fix I needed for pasjonsfrukt 🤗

Thanks! Yes, it's most definitely WIP as of right now. Currently writing tests for the entire client class 👍
Speaking of; are you refactoring pasjonsfrukt to async? (I'm thinking of putting in a legacy sync alternative).

Thanks! Yes, it's most definitely WIP as of right now. Currently writing tests for the entire client class 👍 Speaking of; are you refactoring pasjonsfrukt to async? (I'm thinking of putting in a legacy sync alternative).

Nice :+1:
Yes, pasjonsfrukt is now updated to use the async methods. Now I'm just trying to iron out the bugs preventing the core functionality. Schibsted auth throttling is a pain 😅

Yes, pasjonsfrukt is now updated to use the async methods.

Awesome 👍

Now I'm just trying to iron out the bugs preventing the core functionality. Schibsted auth throttling is a pain 😅

Really? What's your experience..? I hammered quite hard last night while building the new auth flow, and didn't run in to any throttling issues at all 🤔

Really? What's your experience..? I hammered quite hard last night while building the new auth flow, and didn't run in to any throttling issues at all 🤔

Hmm, strange. I just got a Forbidden response from time to time. When attempting to login from the browser with the same account, it just said something like "try again in 5 minutes". So not terrible throttling considering this will run like once every hour, but not great for development. Seems like you were luckier though 🤔

Closing this since you seem to have fixed this in the latest version 🤗


Fixing corner radius of sim play button overlay

What are we looking at?

the corners aren't currently rounded, so it shades the background


Fix CJK input on ios platform

Fix CJK input on ios platform
And Animated show soft keyboard
Code from cocos2d-x 2.1.2
TODO:  Move up current INPUT control, if soft keyboard showed, bottom screent's area are invisible, controls on bottom screen will been hidden

Assigning to @punto- for review.

@punto- Could you check this PR for 2.1? It needs to be rebased, but it might nevertheless still be relevant for us.

No answer, closing as old. Feel free to cherry-pick this commit, rebase it and make a new pull request if interested.


R language

I am working in R language and I have this issue can anybody help me.
if(LCL == 0){Pin1 <- sum(dbinom(LCL:UCL, n, P1, False))}
Warning message:
In if (LCL == 0) { :
the condition has length > 1 and only the first element will be used

@ambreen578 Seems you posted this on the wrong project


force cache clear not working using clearCache method.

Hi Team,
We have react application and I am using createSelector function from redux/toolkit to create memoize selector to select data provided by React Context provider. On Component load in useEffect i am calling selector.clearCache(), but its not working.
its still returned cache data if component unloaded and loaded again and selector provided with same input arguments
Here is the code.
Memoize selector
import { createSelector } from '@reduxjs/toolkit';

trying to clear cache in component first time render -

Redux toolkit version -

I think the issue here is that the memoize function gets used twice internally: once to memoize against the incoming arguments, and then again to memoize the actual extracted values vs the final result.
That results in two different .clearCache functions: selectThing.clearCache, and selectThing.memoizedResultFunc.clearCache.
Try calling selectThing.memoizedResultFunc.clearCache() instead and see what happens.


Enable go to type definition.

Let the client know that we support Go to Type Definition.
Motivation

Release Go to Type Definition.
Test plan

See included automated tests.

Without setting this boolean, VS Code doesn't display "Go to Type Definition" as an available action.


fix block in close()

In case that close() is called while doing
read operation, the close() call is blocked and whole application
is stucked.

Hi and thank you for your contribution.
Please fix a few moments:

Rebase your branch from master, I've fixed CI to run builds from PRs.
Use [fix] as a prefix for your commit message.
Update CHANGELOG.md using template: your_text, #11 by @richard78917

LGMT! Thank you for your contribution. I will release a new version of package this weekend.

New version of package just published:

https://github.com/Gr1N/nats-python/releases/tag/0.7.0
https://pypi.org/project/nats-python/0.7.0/

@richard78917 enjoy!


Set up github workflows

We want to add the following workflows:

[x] Run yarn build-npm-modules on affected projects when a PR is updated
[x] Publish site packages when commits are pushed to main

Partially addressed with https://github.com/VEuPathDB/web-monorepo/pull/9.
Note that build-npm-modules is not defined for packages in the sites directory, so that will need to be fixed.
Initially, this issues said to call yarn test. As the build evolves, we may do that, since we're considering doing away with intermediate build steps (e.g., we can have webpack read directly from src of packages).

Completed with #18


Add Docker Support

This PR adds the ability to run this (awesome!) tool in Docker, which saves the effort of having to manually install PHP, php-snmp, net-snmp-utils, and your web server daemon of choice.
The most notable change is the re-location of the PDU configuration from index.php into a standalone config.php file. Since index.php gets copied into the image at build time, with the configuration values inside that file it's not possible to make any changes without rebuilding the image. Having config.php mounted as a volume (via docker compose) allows it to be updated as needed while index.php remains static in the image. I've done my best to update README.md accordingly for this.

Hello @RossIV,
Happy New Year and many thanks for your pull request. Awesome work! 👏
Based on feedback #2 here, I've already made significant changes to the code (e.g. moving out credentials part and much more) which will be released in Q1 this year. Docker support has already been considered, as the "one file for all" concept doesn't seem to appeal to everyone.
If you have any other suggestions for improvements that you would like to see in version 2, please let me know.
Keep up the good work!
Thank you,
disisto