new tabs part 1 (widgetry demo, jump-to-time, and trips table)

We have several "tab" like systems in the app.
This PR works on consolidate those implementations, and incorporates some of the new designs.
As a reminder, here's the tab spec from figma:

The active tab has dark text, while the inactive tabs which you can switch to have faded text.
I chose to diverge from figma a bit, primarily because the "inactive" tabs were tough to read with the low-contrast text styling, especially on the translucent background in a way that wasn't obvious from figma.
before
The "finished", "canceled", "unfinished" tabs:

The time warp:

after

increasing contrast
One other thing I did, which might be controversial...
Previously the panel_bg and the panel_section were the same colors, but the panel_bg had some opacity applied. This often looked good, but if the map behind the panel has a bunch of content which is almost panel colored, then the contrast between panel_bg and panel_section is lost.
In particular, this could make the tabs hard to differentiate.
To address this, I doped the panel_bg to be a bit farther away from the section color. Compare the tab outline in the left image (doped) vs. right (pure).

The info panel behomoth, and a few other places we do tab-ish things (challenge picker, scenario picker) are still TODO, but I wanted to have an opportunity to check in on direction before going further - though these changes are intended to be mergeable as is.

Reviewing the changes functionally (digging into the code next): this looks great! I love how the trip table now retains state as you click between different tabs. Before, if I fiddled with filters and sorting, switched tabs, then returned, everything would be reset. It's much more intuitive to remember where we left off -- nice!
I noticed a regression with buttons on the scenario picker:

increasing contrast

This change is easier to read/distinguish, so SGTM.

I noticed a regression with buttons on the scenario picker:

I agree it looks pretty bad, but to my eye, not worse than the current look:

Can you clarify what change you'd like to see here?
Is it that you want the buttons to continue to have a visible border/background rather than appearing as "plain"?

Is it that you want the buttons to continue to have a visible border/background rather than appearing as "plain"?

The current look definitely is jarring. But yes, just looking like plain text makes it less clear it's a button. Wouldn't a slight outline or background work?

I'm a bit confused about what this is doing. Why is the first member of the row or column special and worth swapping out?

I've renamed this method and its params and added a docstring.

LGTM! Thanks for the PR. Let me know if you want to talk over how to apply this to info panels.


DNaseI_hypersensitive_site (SO:0000685) misspelled

DNAseI_hypersensitive_site is spelled two different ways, and it's breaking my scripts.
This is the type of a feature in the NCBI GFF file:
DNaseI_hypersensitive_site
https://ftp.ncbi.nlm.nih.gov/genomes/H_sapiens/GFF/
The type in SO is spelled with a different case:
DNAseI_hypersensitive_site
http://www.sequenceontology.org/browser/current_svn/term/SO:0000685
Which one is correct? I did a quick google search, and most papers refer to DNase I. I understand that this is not conclusive! :)
Thanks!

Hi SO -- could you add a synonym for this one? That seems like a straightforward solution for the ambiguity in proper capitalization.
-Terence

Hi @julie-sullivan and @murphyte,
Thank you for bringing this to our attention. This has been updated and the term spelling and INSDC qualifier should now be consistent with the NCBI GFF file.
Thanks,
Dave


Incorrect replaced cmdlets for AzApiManagementProperty

The document describes that the Get-, New-, Remove-, Set-AzApiManagementProperty cmdlets have been replaced with Get-, New-, Remove-, Set-AzureApiManagementNamedValue cmdlets but these are unknown cmdlets
The replaced cmdlets should be Get-, New-, Remove-, Set-AzApiManagementNamedValue respectively

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

ID: afa781d9-4768-24c5-09b8-b707dc75db8a
Version Independent ID: eab00b44-ad2a-fffd-7042-e6133009b357
Content: Migration guide for Az 4.1.0
Content Source: docs-conceptual/azps-4.6.1/migrate-az-4.1.0.md
GitHub Login: @mikefrobbins
Microsoft Alias: mirobb

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

@RoelDG -
Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Some errors are not properly captured in the logs

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

create a report where the context size is too big for GP4
bug

Expected behavior
The error section of the pipeline step should display the actual error
Actual behavior
It simply shows "ERROR" and the error is in the console

Done.


Add benchmarks for ACVM execution speed

We're moving all Noir benchmarks out of zk_bench (https://github.com/noir-lang/zk_bench/issues/5) so we need to benchmark ACVM execution speeds in this repo. This is needed anyway in order to get feedback on performance regressions on PRs.

Best to:

Use the same suite of benchmarking candidates in https://github.com/AztecProtocol/aztec-packages/tree/master/noir/noir-repo/test_programs/benchmarks
Support running the benchmarks in local environments (i.e. not just on Mainframe), if this is to supersede Noir benchmarks in https://github.com/noir-lang/zk_bench


Response Headers: Make RetryAfter Public instead of Internal

Is your feature request related to a problem? Please describe.
When using streaming methods (DeleteItemStreamAsync), exceptions are not used for throttling (status code 429). The only place to currently get the RetryAfter TimeSpan (to help limit the requests sent to the backend) is in the CosmosException. Headers.cs internally has RetryAfter, but it is never exposed to the user.
Describe the solution you'd like
Make Headers.RetryAfter public so users of the Cosmos SDK can handle customized throttling.
Describe alternatives you've considered
We can use DeleteItemAsync, which returns CosmosExceptions with the RetryAfter property, but that degrades performance due to exception handling.
Additional context
Pull request can be found here: https://github.com/Azure/azure-cosmos-dotnet-v3/pull/1373

The retry after can be accessed with the following code.
if (response.Headers.TryGetValue("x-ms-retry-after-ms", out string retryAfterStringValue))
{
     long retryIntervalInMilliseconds = 0;
     if (long.TryParse(retryAfterStringValue, NumberStyles.Number, CultureInfo.InvariantCulture, out retryIntervalInMilliseconds))
     {
          return TimeSpan.FromMilliseconds(retryIntervalInMilliseconds);
     }
}

The only response header that my process returns (at least from a DeleteItemStreamAsync call that had status code 429) is x-ms-substatus (which was 3200). Looking internally into the response Headers while debugging I could confirm that the internal RetryAfter field had a value. Does that indicate any other issues? The call is being made against a 100 GB collection with around 40k RU/s.

RetryAfter obtains the value from the Headers, check out this test: https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos/tests/Microsoft.Azure.Cosmos.Tests/HeadersTests.cs#L153
What you are saying is that if you read the x-ms-retry-after-ms header, you are getting no value?

@cgelon I verified it that the code does work. I created a PR with a sample to get the value.

Please re-open if the provided workaround/samples do not work.


Add option to dispatch activity tasks locally

The activity dispatch optimization feature to allow worker to dispatch activity tasks through local tunnel after decisions are made. If the activity execution fails the retry(if any) goes the regular path(poll from server).
This is a performance optimization to skip activity scheduling efforts.
The corresponding server pr https://github.com/uber/cadence/pull/3609
How did you test it?
tbd
Potential risks
No risk. It is off by default

Pull Request Test Coverage Report for Build 046acdbd-a666-4f38-9588-0ca5ff940822

54 of 172 (31.4%)  changed or added relevant lines in 2 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.7%) to 73.976%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/internal_worker.go
46
71
64.79%

internal/internal_task_pollers.go
8
101
7.92%

Files with Coverage Reduction
New Missed Lines
%

internal/internal_task_pollers.go
2
64.47%

internal/internal_worker.go
2
82.58%

Totals

Change from base Build 5ee44be9-ac0e-4485-8239-5acd33dfa605:
-0.7%

Covered Lines:
9378

Relevant Lines:
12677

💛  - Coveralls


New comment

Dear human,
Here's a new entry for your approval. :tada:
Merge the pull request to accept it, or close it to send it away.
:heart: Your friend Staticman :muscle:

Field
Content

message
Shahars's sticky sidebar is great on firefox, but doesn't work on Safari. I haven't tested other browsers.

name
Matthew Dorey

email
69b0700825ff5bf5df1d9d2d6582cc5e

url
https://mattischrome.com

hidden

date
2018-05-30T14:21:00.032Z

tags

timestamp
1527690060

aeb4742


Finished all documentation related fixes, finished cats study, and upgraded study base

Code integrated. Thanks @drishya-nair !!!


Publishing new Versions of API's with "Deprecate Old Versions" throws a DB error.

Description:
Publishing new Versions of API's with "Deprecate Old Versions" throws a DB error.

Suggested Labels:
Suggested Assignees:
Affected Product Version:
2.6.0
OS, DB, other environment details and versions:
MAC , H2
Steps to reproduce:
Create a New API and publish, Subscribe few users from the store.
Create a new version of the same API.
In the Life Cycle tab, you will see the order as follows
Deprecate Old Versions
Require Re-Subscription
Check the Deprecate Old Versions and click on Publish
Related Issues:

Developer testing record
Followed the steps in issue and. New version added without any error.


[flake8] Resolving E2?? errors

This PR resolves all the E2?? violation codes related to missing or extra whitespace.
to: @mistercrunch

Coverage remained the same at 71.445% when pulling 93f3e2261ed9821710db13cc25fdbeee3cab2d7c on john-bodley:john-bodley-flake8-E2 into 70c7315ae012a16c5c9c2b8fbd30780809f1932a on apache:master.


DOCS Mention the option of Environment files for WAMP users

Once you get a few sites under your belt most devs would likely turn to using environment files to names DB credentials. This introduces this a bit earlier to get them used to the simple idea of an environment file.
Eventually I'd like to rewrite the installer to generate this over storing in the _config.php.

@camfindlay you can update point 3 to go to the recent docs about how to fix that issue see #3905

Sure, I can put that in a separate PR if you merge this one.

you cut a hard bargain


How to get original image size?

❓ Questions and Help
Since the box predict by model is resized,is there anyway to get original size?

I suppose you have found an answer to your question?


Add support for creating a horizontally-tiling MenuBar

Prereqs:

[x] https://github.com/ppy/osu-framework/pull/1007

Follows the example built in the PR above to create a bar that contains a collection of menus.

Closing for rewrite as discussed.


Array.prototype.reduce return type incorrectly inferred as 'any' when Array has type any[]

TypeScript Version:  3.6.3

Search Terms: Array reduce type inferred bad|incorrect|any
Code
const s: Array<any> = []
const x = s.reduce((a, c) => a + '*', '')

Expected behavior: x should be inferred to be of type string
Actual behavior: x is inferred to be any
However, x is is correctly inferred to be type string, if using [].reduce(... as opposed to s.reduce(....
Compare:

with

Inferring x's type even if s is polymorphic is possible and works in other languages:

Playground Link:
Related Issues:
#21061

The overloads of reduce() are in a suboptimal order when the array type is very wide like any or unknown, if the initial value is assignable to it.  If the generic call signature were moved to the front, this issue would not arise:
interface Array<T> {
  reduce<U>(callbackfn: (previousValue: U, currentValue: T, currentIndex: number, array: T[]) => U, initialValue: U): U
  reduce(callbackfn: (previousValue: T, currentValue: T, currentIndex: number, array: T[]) => T): T;
  reduce(callbackfn: (previousValue: T, currentValue: T, currentIndex: number, array: T[]) => T, initialValue: T): T;
}

const s: Array<unknown> = []
const x = s.reduce((a, c) => a + '*', ''); // string

Playground link
I'm not sure if this rises to the level of "bug"; in any case, you could always locally merge in the above declarations in your code base to resolve it (actually you only need the generic one).

Thank you!
Then I think this is a duplicate of #7014.


Uncaught ReferenceError: global is not defined

Hi Team.
When I try to install the package to Vite React app, then run the website, it kept saying: Uncaught ReferenceError: global is not defined.
Here is my packages.json
{
  "name": "bautd-json-translator",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "tsc -b && vite build",
    "lint": "eslint .",
    "preview": "vite preview"
  },
  "dependencies": {
    "@parvineyvazov/json-translator": "^3.2.2",
    "react": "^18.3.1",
    "react-dom": "^18.3.1"
  },
  "devDependencies": {
    "@eslint/js": "^9.9.0",
    "@types/react": "^18.3.3",
    "@types/react-dom": "^18.3.0",
    "@vitejs/plugin-react-swc": "^3.5.0",
    "eslint": "^9.9.0",
    "eslint-plugin-react-hooks": "^5.1.0-rc.0",
    "eslint-plugin-react-refresh": "^0.4.9",
    "globals": "^15.9.0",
    "typescript": "^5.5.3",
    "typescript-eslint": "^8.0.1",
    "vite": "^5.4.1"
  },
  "engines": {
    "node": "20"
  }
}

Here is the code (I just imported the package but it's not working)
import { useState } from 'react'
import './App.css'
import { translateObject } from '@parvineyvazov/json-translator'

function App() {
  const [value, setValue] = useState('')
  const [result, setResult] = useState('')

  const handleSubmitValue = () => {
    console.log(`🆘 src/App.tsx`); // eslint-disable-line
    console.log(translateObject); // eslint-disable-line
    console.log('%c => translator ', 'background: #0095FF; color: #fff'); // eslint-disable-line
    console.log(new Date()); // eslint-disable-line
    try {
      const format = JSON.parse(value)

    } catch {
      alert('Invalid JSON')
    }
  }

  return (
    <>

        <textarea value={value} onChange={e => setValue(e.currentTarget.value)} name="" id=""></textarea>
        <button onClick={handleSubmitValue}>
          Submit
        </button>

          {JSON.stringify(result)}

    </>
  )
}

export default App

Thank you for the package :D I just want to create a miniapp using this package by react

Hi @tranduybau, thank you for reporting,
Unfortunately, jsontt structure is not eligible right now for UI development/frameworks because of some modules.
I will try to spend time in the future to make it available for UI for some translation modules.
Currently it is best for node app and as CLI.

Thank you. I will close the issue. But when it's ready, please tell me :D love the package!


[BUG] New nodes in cluster not recognized by all others

Describe the bug
I'm running keydb 6.3.3 with flash enabled. In cluster mode when a master node is added after initial creation, the new node is not acknowledged by all other nodes.
To reproduce
Create three keydb master instances in cluster mode. Add another master node using command ex. keydb-cli -p 7000 --cluster add-node <IP_ADDRESS>:7003 <IP_ADDRESS>:7000, only the node running on 7000 port acknowledge new 7003 node. Cluster configuration files of nodes on ports 7001 and 7002 does not have 7003 added. This causes errors during rebalance operations.
Node <IP_ADDRESS>:7001 replied with error: IOERR error or timeout reading to target instance
Expected behavior
All nodes should acknowledge new master node automatically. In redis 7 this is working as expected.
Additional information
All nodes are running in docker containers with host network mode. Platform arm64

root@keydb-dev:/data# keydb-cli -a okyes -p 7000 --cluster add-node <IP_ADDRESS>:7003 <IP_ADDRESS>:7000
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
>>> Adding node <IP_ADDRESS>:7003 to cluster <IP_ADDRESS>:7000
>>> Performing Cluster Check (using node <IP_ADDRESS>:7000)
M: 5140f5c16c90b2a9f04bee97ba03178855390305 <IP_ADDRESS>:7000
   slots:[5461-10922] (5462 slots) master
M: 69a283502922046b576f7d69ee0107b76fcabba6 <IP_ADDRESS>:7001
   slots:[0-5460] (5461 slots) master
M: 335cce9c01df9189bde3bb38d0985beef9c25475 <IP_ADDRESS>:7002
   slots:[10923-16383] (5461 slots) master
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node <IP_ADDRESS>:7003 to make it join the cluster.
[OK] New node added correctly.
root@keydb-dev:/data# keydb-cli -a okyes -p 7000 --cluster info <IP_ADDRESS>:7000
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
<IP_ADDRESS>:7000 (5140f5c1...) -> 32513 keys | 5462 slots | 0 slaves.
<IP_ADDRESS>:7003 (74124202...) -> 0 keys | 0 slots | 0 slaves.
<IP_ADDRESS>:7001 (69a28350...) -> 32244 keys | 5461 slots | 0 slaves.
<IP_ADDRESS>:7002 (335cce9c...) -> 32459 keys | 5461 slots | 0 slaves.
[OK] 97216 keys in 4 masters.
5.93 keys per slot on average.
root@keydb-dev:/data# keydb-cli -a okyes -p 7000 --cluster rebalance <IP_ADDRESS>:7000 --cluster-use-empty-masters
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
>>> Performing Cluster Check (using node <IP_ADDRESS>:7000)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Rebalancing across 4 nodes. Total weight = 4.00
Moving 1366 slots from <IP_ADDRESS>:7000 to <IP_ADDRESS>:7003

Node <IP_ADDRESS>:7000 replied with error:
IOERR error or timeout writing to target instance
root@keydb-dev:/data#


Skip creation of empty files if there are no mocks to generate

What did you do?
Run mockolo -s <SOURCE> -d <DESTINATION> on the source folder which doesn't have protocols with mockable annotation.
It generated a file without any mocks.
What did you expect to happen?
I'd expect the empty file won't be created. Or at least having a flag which allows to skip creation of those empty files.
I recognise that the tools also will need to remove the destination file in that case which adds some complications but still, arguable it's worth it.
What is the use-case
If in a modularised project the script is executed once per module, modules which not yet added mock annotation will end up having empty files which is not ideal.
Mockolo Environment
Mockolo Version: 2.0.1
Dependency Manager: Homebrew
Xcode Version: 15.0

An empty file implies an empty output.
Is there a problem, or is it just a matter of feelings?


Reverse/recursive regex matching

Hi, my extension matches [string1]{string2} pattern. I'd need to match the same pattern or similar (that includes characters that break other patters) nested like this:
Nested with [some [text]{inside}<-M1 ]{and [a nested]{text inside}<-M2 }<-M3 pattern.

in the inside out order, so that it first evaluates match1 and match2 then match3 with replaced values of match1 and match2.
Nested with [ some M1]{and M2} pattern.

and finally
Nested with M3 pattern.

I was hoping that it can be done with the order of the extensions?
Another idea was to match the outermost match M3 and then call the matching on its content, convert to a string and filter out <tags/> to get the innerText, but it seems like not the right approach.
Here are my extensions:
{
      rule1: {
        order: SimpleMarkdown.defaultRules.em.order + 0.5 // +
      , match: function(source) {
          return /^\[([^\[\}]*\]\{[^\[\}]*)\}/.exec(source)
        }
      , parse: function(capture, parse, state) {
          return {
            content: parse(capture[1], state) // group drops first '[' and last '}'
          }
        }
      , react: function(node, output) {
          return
        }
      }
    , rule2: {
        order: SimpleMarkdown.defaultRules.em.order - 0.5 // -
      , match: function(source) {
          return /^(\[[^\[\}]*\]\{[^\[\}]*aaa\})/.exec(source)
        }
      , parse: function(capture, parse, state) {
          return {
            content: parse('matched_rule2', state) // directly replacing
          }
        }
      , react: function(node, output) {
          return
        }
      }

    }

the following will replace with rule2:
[as []{aaa} fd]{sdf} => [as matched_rule2 fd]{sdf}
and this with rule1:
[as fd]{sdf} => as fd]{sdf
what it'd need to do is first replace with rule2, so that it remove the brackets that break rule1 pattern, and then replace with rule1.
so expected would be:
[as []{aaa} fd]{sdf} => as matched_rule2 fd]{sdf
Thanks in advance

The way I would try to structure this usually is so that the outer M3 match gets captured first, and then recurse with parse onto the text inside the [] and {}, capturing M1 and M2.
This gets tricky mostly because we need the outer regex to not end at the first ] or }, since those close M1.
To solve this, I think it would be easiest to avoid using a regex matcher at all, but to build our own that uses a stack or integer counts to figure out when the outer match ends. If you check out https://github.com/Khan/perseus/blob/master/src/perseus-markdown.jsx#L27 , Perseus does something similar to what we need for matching TeX in $$ (like $x + 1$), because TeX can itself have $s in it.
If we wanted to bold the inside of the []s and italicize the inside of the {}s, this would look something like:
var SimpleMarkdown = require("simple-markdown");
var _ = require("underscore");

var specialRule = {
    // This doesn't matter so much, we just need to make sure our syntax isn't
    // stolen by something else. Putting it before links seems reasonable because
    // links use `[]`s too. It would be fine later too, though, since none of
    // the default rules should match []{}
    order: SimpleMarkdown.defaultRules.link - 0.5,

    match: function(source, state, prevCapture) {
        // Match has to start with [
        if (source[0] !== '[') {
            return null;
        }

        // Look for the appropriate closing ]:
        var openBracketCount = 0;
        var loc = 1;
        while (loc < source.length && source[loc] !== ']' || openBracketCount > 0) {
            if (source[loc] === '[') {
                openBracketCount++;
            } else if (source[loc] === ']') {
                openBracketCount--;
            }
            loc++;
        }

        // If we didn't find the closing ], no match:
        if (loc >= source.length) {
            return null;
        }

        // Save the closing ] location:
        var firstPartCloseIndex = loc;
        // Move past the closing ]:
        loc++;

        // Look for the opening {:
        if (loc >= source.length || source[loc] !== '{') {
            return null;
        }
        // Move past the opening {:
        loc++;

        // Look for the closing {:
        openBracketCount = 0;
        while (loc < source.length && source[loc] !== '}' || openBracketCount > 0) {
            if (source[loc] === '{') {
                openBracketCount++;
            } else if (source[loc] === '}') {
                openBracketCount--;
            }
            loc++;
        }

        // If we didn't find the closing }, no match:
        if (loc >= source.length) {
            return null;
        }

        // We found everything! Match! Return an array of the useful parts,
        // like a regex match:
        return [
            source.slice(0, loc),
            source.slice(1, firstPartCloseIndex),
            source.slice(firstPartCloseIndex + 2, loc)
        ];
    },

    parse: function(capture, parse, state) {
        return {
            firstContent: parse(capture[1], state),
            secondContent: parse(capture[2], state),
        };
    },

    react: function(node, output, state) {
        return [
            "{output(node.firstContent)}",
            "{output(node.secondContent)}"
        ];
    },

    html: function(node, output, state) {
        return "" + output(node.firstContent) + "" +
            "" + output(node.secondContent) + "";
    },
};

var rules = _.extend({}, SimpleMarkdown.defaultRules, {
    special: specialRule,
});

var rawBuiltParser = SimpleMarkdown.parserFor(rules);
var parse = function(source) {
    var blockSource = source + "\n\n";
    return rawBuiltParser(blockSource, {inline: false});
};
// You probably only need one of these: choose depending on
// whether you want react nodes or an html string:
var reactOutput = SimpleMarkdown.reactFor(SimpleMarkdown.ruleOutput(rules, 'react'));
var htmlOutput = SimpleMarkdown.htmlFor(SimpleMarkdown.ruleOutput(rules, 'html'));

var ast = parse("Nested with [some [text]{inside}<-M1 ]{and [a nested]{text inside}<-M2 }<-M3 pattern.");

console.log(htmlOutput(ast));

Awesome. Works perfectly. Thanks a bunch!


Update bundle, cloudwatch, sdk-core, ses, sns, ... to 2.25.35

About this PR
📦 Updates

software.amazon.awssdk:bundle
software.amazon.awssdk:cloudwatch
software.amazon.awssdk:sdk-core
software.amazon.awssdk:ses
software.amazon.awssdk:sns
software.amazon.awssdk:sqs
software.amazon.awssdk:ssm

from 2.25.15 to 2.25.35
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #3176.


Backend Services: Implement APIs/Services in Prod Environment

[x] In AWS Prod account, create API that will accept POST for scanned barcode data, use JWT authorizer (Student PID, barcode id, datetime of scan, user ID/email, first and last name not in current API)

[x] In AWS Prod account, create API that will read scanned barcode data based on Student ID, auth method is API Key on AWS, "QRScannerAPIKey"

[x] In AWS Prod account, create Lambda in the UCSD Campus VPC that will call the HANA Stored Procedure, PUT_SCAN_DATA, use JWT authorizer

[x] In AWS Prod account, create Lambda in the UCSD Campus VPC that will call the HANA Stored Procedure, GET_SCAN_DATA, auth method is API Key on AWS, "BarcodeScanDataAPIKey"

[ ] Migrate exsiting WSO2 API to Prod

Just waiting on DIS to migrate to Prod.


groups < out_channels is redundant

I think the if-else statement is redundant? Since if the groups parameter is greater than out_channels, an error(out_channels must divisible by groups) will be raised when we define the original convolution layer which above these lines.
if groups < out_channels:
     self.dbb_avg.add_module("conv", nn.Conv2d(in_channels=in_channels, out_channels=out_channels, kernel_size=1, stride=1, padding=0, groups=groups, bias=False))
     self.dbb_avg.add_module('bn', BNAndPadLayer(pad_pixels=padding, num_features=out_channels))
     self.dbb_avg.add_module('avg', nn.AvgPool2d(kernel_size=kernel_size, stride=stride, padding=0))
     self.dbb_1x1 = conv_bn(in_channels=in_channels, out_channels=out_channels, kernel_size=1, stride=stride,
                                       padding=0, groups=groups)
else:
     self.dbb_avg.add_module('avg', nn.AvgPool2d(kernel_size=kernel_size, stride=stride, padding=padding))

Hi, I just found the paper has mentioned about this part, however, for depthwise convolution, shouldn't we check for groups == in_channels instead of groups == out_channels in the code above?


Compilation with Cuda 9.1 Cudnn 7.0.5, In python3, "help(tensorflow)" caused core dump

Have I written custom code: No
OS Platform and Distribution: Ubuntu 16.04 Server
TensorFlow installed from: source cloned from current branch
TensorFlow version: 1.9.0-rc2 the active version from the master branch
Bazel version: 1.5.0, a most recent release
CUDA/cuDNN version: 9.1/7.0.5
GPU model and memory: NVIDIA GTX 1080Ti 11GB
Test Environment: Python 3.5
Exact command to reproduce: python3 -c "import tensorflow; help(tensorflow)"
If this could help....
Code Version: v1.9.0-rc2-205-g216887d 1.9.0-rc0
Hello guys,
I recently cloned the bench and compiled with all (Y/n) set to y and (y/N) set to n. while the Cuda is set to yes.
The cuda environment is 9.1 and cudnn is 7.0.5.
The compilation succeeded, and I tried some subtle code to run tensorflow on gpu, it also returns.
Then I tried to read some help, but when I typed "help(tensorflow)" python halted and crushed.

Segmentation fault (core dumped)

I'm wondering why this happened? Could you lend some help?
The template data is filled up, If you require a snapshot of installed python packages, I would make a list.
Currently I have no idea what's happening, There is no error report, only a core dump....
Fine, after all I'll try an earlier version of tensorflow.
Today I rebuilt with tensorflow 1.8.0 release source code, it works. It might imply there was something wrong with the 1.9.0 source

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

I've edited, so that you may see more details

Nagging Assignee @asimshankar: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @asimshankar: It has been 30 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @asimshankar: It has been 50 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @asimshankar: It has been 66 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @asimshankar: It has been 81 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @asimshankar: It has been 96 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @asimshankar: It has been 111 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @asimshankar: It has been 126 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @asimshankar: It has been 141 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@Heermosi This is a stale issue. I think this was resolved in recent TF versions.
Also, there is no support for TF1.x.
I am closing this issue as this was resolved in recent TF versions. Please feel free to test with TF2.x and open a new issue If the issue persists with recent TF versions. Thanks!


parent.set is not iterable

macOS  chrome  108.0.5359.98
maybe chrome upgrades and has special optimize for circular reference，below tag define will push itself into tag.set makes
circular reference。
    /// Define a new tag. If `parent` is given, the tag is treated as a
    /// sub-tag of that parent, and
    /// [highlighters](#highlight.tagHighlighter) that don't mention
    /// this tag will try to fall back to the parent tag (or grandparent
    /// tag, etc).
    static define(parent) {
        if (parent === null || parent === void 0 ? void 0 : parent.base)
            throw new Error("Can not derive from a modified tag");
        let tag = new Tag([], null, []);
        tag.set.push(tag);
        if (parent)
            for (let t of parent.set)
                tag.set.push(t);
        return tag;
    }

while debugging in chrome，strange things happened

then next line, init name with Tag.define, it turns out with  Object[object] , not an instance of  Tag

and go on, jserror

I can run @lezer/highlight without trouble in Chrome 108. Can you be a bit more specific about how to trigger the problem?

I can run @lezer/highlight without trouble in Chrome 108. Can you be a bit more specific about how to trigger the problem?

Did u try @lezer/highlight/dist/index.js ? I finally found it's my esbuild config packing with the dist/index.js file occured this problem, I just solve this by modify my esbuild config while requiring dist/index.cjs。
But I think problem still exists

I can't see this happening except if Tag.define is called with an argument that's not a Tag, and the code in the package definitely doesn't do this. Going to close this until I have a working way to reproduce it.


Update pihole/pihole Docker tag to v2023.01.10

This PR contains the following updates:

Package
Type
Update
Change

pihole/pihole
final
patch
2023.01 -> 2023.01.10

Release Notes

pi-hole/docker-pi-hole
v2023.01.10
Compare Source

Who had 10 in the sweepstake?

Patches for the occasional 503 errors and a security advisory on web
What's Changed

Don't declare VIRTUAL_HOST as an empty string in Dockerfile by @PromoFaux in https://github.com/pi-hole/docker-pi-hole/pull/1304

Full Changelog: https://github.com/pi-hole/docker-pi-hole/compare/2023.01.9...2023.01.10
Also Includes:
Core v5.15.3: What's Changed

Change lighttpd options min_procs value to 1 by @rdwebdesign in https://github.com/pi-hole/pi-hole/pull/5149

Full Changelog: https://github.com/pi-hole/pi-hole/compare/v5.15.2...v5.15.3
Web v5.18.3: What's Changed

Fix insecure persistent login token by @4n4nk3 d31cf9d (https://github.com/pi-hole/AdminLTE/security/advisories/GHSA-33w4-xf7m-f82m)

Full Changelog: https://github.com/pi-hole/AdminLTE/compare/v5.18.2...v5.18.3
v2023.01.9
Compare Source
JANUARY IS SUPPOSED TO BE A QUIET MONTH...
What's Changed

Revert "Ensure that the directory /run/lighttpd exists by @PromoFaux in https://github.com/pi-hole/docker-pi-hole/pull/1300 [patched upstream]
Configure FTL's MACVENDORDB setting to "/macvendor.db" on startup by @PromoFaux in https://github.com/pi-hole/docker-pi-hole/pull/1301 [fixes an issue found in#1299]

Full Changelog: https://github.com/pi-hole/docker-pi-hole/compare/2023.01.8...2023.01.9
v2023.01.8
Compare Source
One more time... (We don't talk about 2023.01.7)
What's Changed

Ensure that the directory /run/lighttpd exists, and that it is owned by www-data by @PromoFaux in https://github.com/pi-hole/docker-pi-hole/pull/1298
Add support for changing admin bind address indepentendly of $FTLCONF_LOCAL_IPV4 by @n6g7 in https://github.com/pi-hole/docker-pi-hole/pull/1293

New Contributors

@n6g7 made their first contribution in https://github.com/pi-hole/docker-pi-hole/pull/1293

Full Changelog: https://github.com/pi-hole/docker-pi-hole/compare/2023.01.6...2023.01.8
Also includes:
https://pi-hole.net/blog/2023/01/22/pi-hole-web-v5-18-2-and-core-v5-15-1-released/
Web 5.18.2: What's Changed

Add default value for $ver in func.php by @yubiuser in https://github.com/pi-hole/AdminLTE/pull/2497
Show two decimals on doughnutTooltip if total share shown is less than 1% by @yubiuser in https://github.com/pi-hole/AdminLTE/pull/2502
Tweak deleting message by @yubiuser in https://github.com/pi-hole/AdminLTE/pull/2498
Attenuate non-domain warning by @yubiuser in https://github.com/pi-hole/AdminLTE/pull/2507
remove hard-coded /admin/ path by @gstrauss in https://github.com/pi-hole/AdminLTE/pull/2461
Do not return 'false' if IDNA<->UNICODE conversion fails by @yubiuser in https://github.com/pi-hole/AdminLTE/pull/2479

New Contributors

@gstrauss made their first contribution in https://github.com/pi-hole/AdminLTE/pull/2461

Full Changelog: https://github.com/pi-hole/AdminLTE/compare/v5.18.1...v5.18.2
Core 5.15.1: What's Changed

Include mod_accesslog with new config by @PromoFaux in https://github.com/pi-hole/pi-hole/pull/5121
Run updatechecker after gravity by @yubiuser in https://github.com/pi-hole/pi-hole/pull/5137
Only remove the server.modules+= from new config if lighttpd version is < 1.4.56 by @PromoFaux in https://github.com/pi-hole/pi-hole/pull/5133
Cleanup if startup failed by @yubiuser in https://github.com/pi-hole/pi-hole/pull/5052
Reduce number of false positives when gravity unable to import domains - change the wording of the output by @PromoFaux in https://github.com/pi-hole/pi-hole/pull/5128
Change php socket path back to /run/lighttpd/ from /tmp by @PromoFaux in https://github.com/pi-hole/pi-hole/pull/5139
Always set lighttpd config dir permissions by @yubiuser in https://github.com/pi-hole/pi-hole/pull/5038

Full Changelog: https://github.com/pi-hole/pi-hole/compare/v5.15...v5.15.1
v2023.01.6
Compare Source
Well the builds start coming, and they don't stop coming...
Fixes https://github.com/pi-hole/docker-pi-hole/issues/1289
What's Changed

Disable provenance in the build-push-action - should solve issues downloading the image on some systems by @PromoFaux in https://github.com/pi-hole/docker-pi-hole/pull/1290

Full Changelog: https://github.com/pi-hole/docker-pi-hole/compare/2023.01.5...2023.01.6
v2023.01.5
Compare Source
It's been a busy few days...
What's Changed

Allow for empty strings to be passed into FTLCONF_ environment variables by @PromoFaux in https://github.com/pi-hole/docker-pi-hole/pull/1288

Full Changelog: https://github.com/pi-hole/docker-pi-hole/compare/2023.01.3...2023.01.5
v2023.01.4
Compare Source
Nothing Docker specific in this release, tagging to include PADD v3.10.1

PADD v3.10.1:  What's changed

Add action to close stale PR by @rdwebdesign in https://github.com/pi-hole/PADD/pull/323
Tweak visuals by @yubiuser in https://github.com/pi-hole/PADD/pull/327
Add version bump workflow by @yubiuser in https://github.com/pi-hole/PADD/pull/316
Issue 314 📝 update 'how to run PADD in docker container' by @thomasmerz in https://github.com/pi-hole/PADD/pull/315
Use padd.sh URLs by @dschaper in https://github.com/pi-hole/PADD/pull/213
Export LOCALE by @yubiuser in https://github.com/pi-hole/PADD/pull/335
Do not show update notices if padd is being run from the docker container by @PromoFaux in https://github.com/pi-hole/PADD/pull/325

New Contributors

@PromoFaux made their first contribution in https://github.com/pi-hole/PADD/pull/325

Full Changelog: https://github.com/pi-hole/PADD/compare/v3.10.0...v3.10.1
v2023.01.3
Compare Source
"They're a lot like London Buses" edition.

What's Changed

lighttpd does not like it if VIRTUAL_HOST and FTLCONF_LOCAL_IPV4 are duplicate values... by @PromoFaux in https://github.com/pi-hole/docker-pi-hole/pull/1286

Full Changelog: https://github.com/pi-hole/docker-pi-hole/compare/2022.01.2...2023.01.3
v2023.01.2
Compare Source

What's Changed

Modify the 15-pihole-admin.conf file in the correct path.... by @PromoFaux in https://github.com/pi-hole/docker-pi-hole/pull/1284

Full Changelog: https://github.com/pi-hole/docker-pi-hole/compare/2023.01.1...2023.01.2
v2023.01.1
Compare Source

What's Changed

Remove the PHP_ENV_CONFIG variable from the Dockerfile by @PromoFaux in https://github.com/pi-hole/docker-pi-hole/pull/1281 (Fixes https://github.com/pi-hole/docker-pi-hole/issues/1275)

Full Changelog: https://github.com/pi-hole/docker-pi-hole/compare/2023.01...2023.01.1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

running in production

I'm going to merge this this weekend :-)

I was about ready to give up on the .01.x releases and wait for .02.x
release at the rate things have been re-fixed this month.
But I'm fine with merging 01.10, let me make sure I've tried it in
production cause I think I'm still on 01.7.
On Fri, Jan 27, 2023, 6:51 p.m. Roddie Hasan @.***>
wrote:

I'm going to merge this this weekend :-)
—
Reply to this email directly, view it on GitHub
https://github.com/klutchell/balena-pihole/pull/199#issuecomment-1407198509,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4CWIAWMACD2NKL4XF3LE3WURNQRANCNFSM6AAAAAAT7JSHPU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Sounds good - I've been upgrading with each patch and haven't had any issues so far.

All good on my end!
On Fri, Jan 27, 2023, 7:09 p.m. Roddie Hasan @.***>
wrote:

Sounds good - I've been upgrading with each patch and haven't had any
issues so far.
—
Reply to this email directly, view it on GitHub
https://github.com/klutchell/balena-pihole/pull/199#issuecomment-1407207264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4CWIFQI2E6UKE2S5PJX6TWURPVPANCNFSM6AAAAAAT7JSHPU
.
You are receiving this because you commented.Message ID:
@.***>


NextJs Compress mode or Minify process is disabled when JsAst is enabled

Type

[ ] Incorrect Class Name Extraction
[ ] Incorrect JavaScript Obfuscation
[ ] Incorrect HTML Obfuscation
[ ] Incorrect CSS Obfuscation
[x] Others

Checklist

[x] Updated the package to the latest version
[x] Read all documentation
[x] No related issue
[x] Meaningful issue title (hope so...)

Environment

Package Version: v.2.2.5
Node Version: v.20.x (Vercel)

Describe the bug
NextJs Compress mode or Minify process is disabled when enable JsAst.
To Reproduce
Steps to reproduce the behavior:

Local:

Turn enableJsAst to true in next-css-obfuscator.config.cjs
npm run build in Terminal
Check every js file in .next/static
See error (not minified)

Deploy to Vercel (thru GitHub repo case):

Turn enableJsAst to true in next-css-obfuscator.config.cjs
Commit to GitHub
After successfull deploy in Vercel, visit the website
Ctrl + U or right click -> View page source
Ctrl + Shift + R to hard reload
Find and click a .js file in the window
Ctrl + Shift + R multiple times to hard reload again (Just to be sure)
See error (not minified)

Expected behavior

Screenshots

Config
module.exports = {
    enable: true, // Enable or disable the plugin.
    mode: "random", // Obfuscate mode, "random" or "simplify".
    buildFolderPath: ".next", // Build folder of your project.
    classConversionJsonFolderPath: "./css-obfuscator", // The folder path to store the before obfuscate and after obfuscated classes conversion table.
    refreshClassConversionJson: false, // Refresh the class conversion JSON file.

    classLength: 6, // Length of the obfuscated class name.
    classPrefix: "n", // Prefix of the obfuscated class name.
    classSuffix: "", // Suffix of the obfuscated class name.

    classIgnore: [
        "dark",
        "light",
        "no-transition",
        "opa-hidden",
        "big",
        "small",
        /os-scrollbar*/,
    ], // The class names to be ignored during obfuscation.

    allowExtensions: [".jsx", ".tsx", ".js", ".ts", ".html", ".rsc"], // The file extensions to be processed.

    contentIgnoreRegexes: [/\.jsxs\)\("\w+"/g], // The regexes to match the file content to be ignored during obfuscation.

    whiteListedFolderPaths: [], // Only obfuscate files in these folders

    blackListedFolderPaths: ["./.next/cache"], // Don't obfuscate files in these folders

    enableMarkers: false, // Enable or disable the obfuscate marker classes.
    markers: ["obf"], // Classes that indicate component(s) need to obfuscate.
    removeMarkersAfterObfuscated: true, // Remove the obfuscation markers from HTML elements after obfuscation.

    removeOriginalCss: true, // Delete original CSS from CSS files if it has a obfuscated version.

    generatorSeed:<PHONE_NUMBER>8, // The seed for the random generator.

    //! Experimental feature
    enableJsAst: true, // Whether to obfuscate JS files using abstract syntax tree parser (Experimental feature)

    logLevel: "info", // Log level
};

Related files

Demos (if any)
N/A
Additional context
I'm not sure if JsAst new mode does anything different than without it enabled, even though I've read the documentation, but maybe it's giving an error now.

However, I turned on JsAst mode a few days ago and noticed that my website's first load suddenly became slow, now I know 🐧

Not solved yet


Increase security tests timeout to 15 seconds

On real Android devices, it may take longer than 5 seconds to receive pairing events due to physical and system latency(in many cases, BT may not be ready yet when test starts).
It is intended and should not be considered error or failure.

Once https://github.com/google/avatar/pull/58 merge we can rebase this PR.


Royal Ghost bad image

http://www.clashapi.xyz/images/cards/royal-ghost.png
The image is not cropped properly and has a purple glowing effect around it.

Duplicate #95


i can't run the demo

when i npm run demo and npm install it's throw me an error
npm-debug.txt

Hi,
thanks for the report. Unfortunately I'm not sure what's exactly causing the installation to fail. Can you please retry with the latest release. If this does not solve it, could you try running the commands the npm run demo performs (as described in the Readme) manually to narrow down which if them fails.
Regards
Sebastian

I had the same issue.
Running:
- node v4.50
- npm 3.10.7

it fails on "npm run compile" at the main project.
to solve the demo app you have to change the package.json from:
"ng2-page-scroll": "file:../",

to:
"ng2-page-scroll": "3.1.0",


Move the rest of rekor-server over.

Some changes:

import names (app -> api, logging -> log)
Commands package (cmd -> app)

LGTM, merging


Documentation Request: Working Example of Page Redirect instead of Pop-Up for Angular

Please follow the issue template below. Failure to do so will result in a delay in answering your question.
Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Documentation location

[ ] docs.microsoft.com
[ ] MSAL.js Github Wiki
[ ] README file
[ ] Other (please fill in)
[x] Documentation does not exist

Description
Basically what the title says. While it initially appears to be JUST a flag, the flow of the application is entirely different and not explained in the setup so far.

@akleimrey Our MSAL Angular samples demonstrate how to do popup and redirect based authentication: https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-angular-samples
Is there something specific you would like more clarification on? Thanks!

@jasonnutter Works for my case! It was less of a coding issue than a configuration one. Redirect works much better than pop up on almost all fronts.


Improve the home page

Expected changes to be done to improve the home page:

Improve the nav bar
Currently, the whole blog post is being displayed for each post. Make it so that only part of it should be displayed. After opening a specific blog post it should display the whole content.
Make all the blogs to be displayed in the form of grid.
Add footer
You can make other changes too to make it awesome. You can check some of the developer's blog website for reference.

@deepak2431 can I work on this issue ?

@snehalkhandve Sure, have a go!

@snehalkhandve Are you working on this issue?

@deepak2431 yes I am working on the issue . Will upload the screenshot of home page before generating pr.

@snehalkhandve Sure, thanks!

This is the screenshot of home page after the changes I have done.Can I generate the pull request now ?

@snehalkhandve The color used for the background looks cool to me. But I would suggest you to make the sidebar color consistent with the homepage. Also please make some editing to navbar according to you. Rest is fine for me. You can open a PR after that.

Yup changed the color for sidebar


Repos in asset unables

Issue Type: Feature Request
Attribute only statement only main.. and framework so plug-in or template parameter: sync this boolean test if run so also tour changes feed last member.
VS Code version: Code 1.49.0 (e790b931385d72cf5669fcefc51cdf65990efa5d, 2020-09-10T13:22:08.892Z)
OS version: Windows_NT x64 10.0.17134

Sorry, I don't understand what you mean. Can you add more description and steps and maybe a screenshot?

desing.. this above time and figth town-- andwer only process so remember attribute if sequense out-line

Closing the issue due to lack of details provided. Please add complete steps and descriptions of what you see and what you expect.


Sherlock web service failing

Gareth
The API is not running sherlock properly. This is as far as I can push it, since I don't know how your webserver is set up. I think these requests are properly formatted:
ubuntu@lasair-ztf-sherlock-0:~$ curl "http://localhost/object/ZTF21aapvmcu"
{"message": "The browser (or proxy) sent a request that this server could not understand."}
ubuntu@lasair-ztf-sherlock-0:~$ curl "http://localhost/query?ra=123&dec=23"
{"message": "The browser (or proxy) sent a request that this server could not understand."}

ubuntu@lasair-ztf-bootstrap:~/lasair-deploy$ curl -H "Content-Type: application/json" -d '{ "lite": true, "ra": "1.2", "dec": "2.3" }' "http://lasair-ztf-sherlock-0/query"
{"classifications": {"transient_00000": ["ORPHAN", "No contexual information is available for this transient"]}, "crossmatches": []}
ubuntu@lasair-ztf-bootstrap:~/lasair-deploy$ curl -H "Content-Type: application/json" -d '{ "lite": true }' "http://lasair-ztf-sherlock-0/object/ZTF21aapvmcu"
{"classifications": {"ZTF21aapvmcu": ["SN", "The transient is possibly associated with NGC6660; an r=14.53 mag galaxy found in the NED_D/PS1/LASR catalogues. It's located 52.76\" S, 48.77\" E (14.7 Kpc) from the galaxy centre. A host distance of 42.1 Mpc(z=0.014) implies a m - M = 33.12."]}, "crossmatches": [{"transient_object_id": "ZTF21aapvmcu", "association_type": "SN", "catalogue_table_name": "NED D/PS1/LASR", "catalogue_object_id": "NGC6660", "catalogue_object_type": "galaxy", "raDeg":<PHONE_NUMBER>67, "decDeg": 22.90967, "separationArcsec": 71.84, "northSeparationArcsec": "52.75514", "eastSeparationArcsec": "-48.76661", "physical_separation_kpc": 14.66, "direct_distance": 42.1, "distance": 61.17, "z": 0.01, "photoZ": null, "photoZErr": null, "Mag": 14.53, "MagFilter": "r", "MagErr": 0.0, "classificationReliability": 2, "major_axis_arcsec": null}]}

In the past, the internal Sherlock service was a GET service
https://github.com/lsst-uk/lasair4/blob/main/webserver/lasairapi/serializers.py
lines 113 and 141
Above you demonstrate that the POST works well. Would it be possible to also make the GET service work again, so I don't need to write new code for POST.

It looks like the fundamental problem here is that the Sherlock API is built using flask-restful (https://github.com/flask-restful/flask-restful), which is not really being actively maintained any more and an underlying package has changed it's default behaviour, which in turn means that the reqparse component of flask-restful can no longer automatically convert everything on the fly.
I see three possible solutions:

Replace reqparse with another package such as webargs.
Re-write the calling code to send the request as JSON.
Work out how to integrate the Sherlock API into the main API so we're not maintaining two sets of API code.

I think 3 is the best (only?) long term solution, and we should probably consider it as part of the web refresh, but it also doesn't help in the short term.
I would normally suggest 1, except that I might not have time to do it this week and then I'm away for a bit.
How much work would 2 be?


bitswap in large populations

In the book algorithmic game theory by nissan on page 595 it says:

Of course, there is no guarantee that two peers will engage in multiple transactions
with each other in their lifetimes. Even if they do, there is no guarantee that they will do
so with a proper reversal of client and server roles to facilitate reciprocity or retaliation.
In a large dynamic population with random matching of players, the probability of
repeat interactions between players may be too small to cast an effective “shadow of
the future,” and free-riding might prevail.
Figure 23.1, taken from a simulation study of a p2p file-sharing game (Feldman et al.,
2004), illustrates the inability of a reciprocative strategy to scale to large populations.

since you can't see the figure: a large population means a 120 peers in this case. so it seems like bitswap is ineffective. the reason why bittorrent works is because it forces repeat interactions inside a swarm.

actually bitswap is only a mechanism, and there is nothing preventing it from being used with a shared history (on a dht or blockchain). after beeing rather depressed yesterday after reading about all these hard and unsolved problems in p2p systems, [0] turns out to actually have some solutions.

[0] Robust Incentive Techniques for Peer-to-Peer Networks

Can someone move this issue to ipfs/notes? People in the rust-ipfs riot have an interest in a public discussion after I mentioned it.


Add support for lookup_transfers

TigerBeetle currently supports the following operations;

create_accounts
create_transfers
commit_transfers
lookup_accounts

There is a requirement to lookup an existing transfer via id (lookup_transfers(u128).
Although the state_machine already supports transfer lookups via get_transfer, the operation is not exposed.
Furthermore the https://github.com/coilhq/tigerbeetle-node repo needs to be updated to support transfer retrieval.

PR's for Issue;
https://github.com/coilhq/tigerbeetle/pull/64
https://github.com/coilhq/tigerbeetle-node/pull/21

Thanks @koekiebox awesome to have this done already.


Is it possible to support HTTPs ?

看了一下源码用的标准http库，可以在serve里增加https支持，会不会更好些

I looked at the source code and it seems shiori is using standard http server. I think it will be better if you can add https support in the serve.

I don't think shiori need to support HTTPs. The reasons are :

I think most of the time shiori is only used as cli or in localhost, which doesn't need HTTPs.
If used in server, shiori can be used behind another web server like caddy (which already provide HTTPs by default) or nginx.


[2023b] RHOAIENG-8299: Fix CentOS Stream 8 download location

Previously used location is now unavailable and returns 404 error. This is because CentOS Stream 8 has been EOLd
This new location is an archive and is no longer receiving updates.
(cherry picked from commit 8e19ee21b8d4086fa9fec4fa4efa3c4df28b0cef)

Description

How Has This Been Tested?

Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

@atheo89, can't do, the cherrypick does not apply cleanly and the bot refuses to create PR because of

https://github.com/opendatahub-io/notebooks/pull/554#issuecomment-2173947534

@atheo89, can't do, the cherrypick does not apply cleanly and the bot refuses to create PR because of

RHOAIENG-8299: Fix CentOS Stream 8 download location #554 (comment)

Ohh you had done this already, sorry i didn't arrived to the bottom of the PR :face_holding_back_tears:
OK then let's do it this way.
/lgtm
/approve

/retest


Fixed .NET SDK style project slowness in the editor

This was something; took quite a bit of time tracking down, but now it's starting to make sense.
In our language service, the F# project options always got a new Stamp value, even though invalidateConfig was false, thus when it came to FSharp compiler's services' MruCache, it would see the stamps are different and rebuild chunks of the world. It did this as you typed something. This was causing slowness as the compiler services were just reading tons of assembly data over and over again; GC was going ham too.
The fix, simply put, we re-use the recently used stamp value when invalidateConfig is false. This prevents rebuilding big parts of the world.
Also, on top of this fix, there is another fix where we don't invalidate on document open; this also prevents rebuilding chunks of the world when you open a document.
The reason why this never happened in legacy projects was because in non-CPS style projects, it would go down a slightly different code path, see textView.GetBuffer() and this.UpdateProjectInfoWithProjectId in LanguageService.fs for the differences.
In the non-CPS style projects, they never called UpdateProjectInfo when you opened a document or changed a document.

Nice 👍

This code deserves a small unit test :)

But first merge it so that it's going into 15.7.2 ;-)

Great work.

Could you take a while to think how to put this under automated test? It's important never to regress this...
The test suite has oodles of tests to check we dont reconpute/invalidate, counting number of parses, checks etc. But that only works if you get the project options right.

I agree we should put a test here so we don't regress. At the top of my head, I'm not sure how to accomplish this as it's really in the middle of a lot of stuff. Unless we already have mocks, this will be quite a bit of work to do.
At some point we are going to refactor parts of the integration with the workspace. Perhaps during that time we can design something that is testable, isolated from the language service and workspace.

I'll try to think of something.

As for UpdateProjectInfo, @KevinRansom will have more context on why it's done the way it's done.

As for UpdateProjectInfo, @KevinRansom will have more context on why it's done the way it's done.

I wrote the code originally, so I know the context.  Looking at the code now.
Do you have a callstack for when UpdateProjectInfo is being called during standard editing?

I don't on hand. I can get one next time I go into the office.

Your best bet is to look at the workspace events and see how it eventually calls UpdateProjectInfo.

Oh I see, yes.  The following path from OnDocumentChanged to UpdateProjectInfo is just plain wrong - we should never have been updating the project info on every change to the document.
May I mention that I asked this question when reviewing this code, when @cartermp proposed a fix for another manifestation of this problem in https://github.com/Microsoft/visualfsharp/pull/4121:
    member private this.OnDocumentChanged(projectId:ProjectId, documentId:DocumentId) = projectInfoManager.UpdateDocumentInfoWithProjectId(projectId, documentId, "OnDocumentChanged", invalidateConfig=false)

    member this.UpdateDocumentInfoWithProjectId(projectId:ProjectId, documentId:DocumentId, userOpName, invalidateConfig) =
        if workspace.IsDocumentOpen(documentId) then
            this.UpdateProjectInfoWithProjectId(projectId, userOpName, invalidateConfig)

    member this.UpdateProjectInfoWithProjectId(projectId:ProjectId, userOpName, invalidateConfig) =
        let hier = workspace.GetHierarchy(projectId)
        match hier with
        | null -> ()
        | h when (h.IsCapabilityMatch("CPS")) ->
            let project = workspace.CurrentSolution.GetProject(projectId)
            if not (isNull project) then
                let siteProvider = this.ProvideProjectSiteProvider(project)
                let projectSite = siteProvider.GetProjectSite()
                if projectSite.CompilationSourceFiles.Length <> 0 then
                    this.UpdateProjectInfo(tryGetOrCreateProjectId, projectId, projectSite, userOpName, invalidateConfig)
        | _ -> ()

@KevinRansom Do you know why we are doing anything at all for DocumentChanged? Was there a particular case that motivated this? e.g. why do we need to call UpdateDocumentInfoWithProjectId at all for OnDocumentChanged?

However I got no reply - @KevinRansom please make sure to keep track of questions like this and make sure they get a reply?
Anyway, I strongly believe that we that we should simply not be updating the project info on DocumentChanged.  The only case where we might do that is for scripts, but they are handled differently.

Anyway, I believe the correct fix is just to delete the event handler for OnDocumentChanged.  And if that isn't a correct fix (I think it is) then we really need to work out why the event handler is needed....

Deleting it would be ideal. We should also delete it from the textView.GetBuffer as well of we can. Opening a document shouldn't so that either, legacy doesn't.

@vasily-kirichenko

Can it result with loss of updating project options for FSX files when #r directives added/deleted?

Good question. Script files are covered by this code in TryGetOptionsForDocumentOrProject:
            // The options for a single-file script project are re-requested each time the file is analyzed.  This is because the
            // single-file project may contain #load and #r references which are changing as the user edits, and we may need to re-analyze
            // to determine the latest settings.  FCS keeps a cache to help ensure these are up-to-date.
            match singleFileProjectTable.TryGetValue(projectId) with
            | true, (loadTime, _, _) ->
                ...

But the behaviour you mention should be checked as part of validating the fix .

We should also delete it from the textView.GetBuffer as well if we can.

@TIHan do you have a link for that?

@vasily-kirichenko that's an interesting point. I wonder if adding #r's with the current fix will work or not.
For script files, we should be using the MiscellaneousFilesWorkspace which we are currently not. If we used that workspace, we could at least separate its specific behavior from the workspace for projects.

It's not super clear but:
This is the legacy path: https://github.com/TIHan/visualfsharp/blob/a6fc8525b8fec6affdef69361d3847829b9d4314/vsintegration/src/FSharp.Editor/LanguageService/LanguageService.fs#L669
And this is the CPS path:
https://github.com/TIHan/visualfsharp/blob/a6fc8525b8fec6affdef69361d3847829b9d4314/vsintegration/src/FSharp.Editor/LanguageService/LanguageService.fs#L671

For script files, we should be using the MiscellaneousFilesWorkspace which we are currently not. If we used that workspace, we could at least separate its specific behavior from the workspace for projects.

Yeah, there are a couple of glitches with script files (e.g. loss of colorization on save-as file rename) that can likely be fixed by updating script file options on changes like these, or by doing things differently in the first place
            | WorkspaceChangeKind.AdditionalDocumentAdded
            | WorkspaceChangeKind.AdditionalDocumentReloaded
            | WorkspaceChangeKind.AdditionalDocumentRemoved

Re SetupNewTextView - perhaps that is just the wrong place to be setting up the options for our-of-project files and scripts, and that doing it in response to the events above will be more complete and accurate (and more portable too - we'd like to eventually use FSharp.Editor in VS for Mac, so the less VS-specific code the better. Roslyn and Roslyn CPS-specific code is ok).

Yeah, there are a couple of glitches with script files (e.g. loss of colorization on save-as file rename) that can likely be fixed by updating script file options on changes like these, or by doing things differently in the first place

Then this fix needs to evolve a bit more. Sorry I didn't test that case.
Does the AdditionalDocument refer to files that are not part of the project, such as our script files maybe?

doing it in response to the events above will be more complete and accurate

This is exactly what we need to do. We should always listen to the workspace to give us what we need. Right now we rely on HandleCommandLineArgs method until we figure out how to get rid of it. We need to integrate with the evaluation/design-time builds.

We should also delete it from the textView.GetBuffer as well if we can.

OK, I understand now. I added some comments to clarify the existing code here.  Could you check the comments, particularly this one?
Let me explain a bit about useUniqueStamp. This stems from the time when ProjectSitesAndFiles.fs was shared between FSharp.Editor and FSharp.LanguageService.  For FSharp.Editor this is always true, (and for the legacy FSharp.LanguageService this was always false).  So the meaning of the flag is "are we using the unique stamping facility at all".  Since we no longer share this file we can remove this flag, assuming it always to be true.

Yeah, there are a couple of glitches with script files (e.g. loss of colorization on save-as file rename) that can likely be fixed by updating script file options on changes like these, or by doing things differently in the first place

Then this fix needs to evolve a bit more. Sorry I didn't test that case.

Oh, they are existing glitches, not glitches in this PR.  See https://github.com/Microsoft/visualfsharp/issues/1944

Does the AdditionalDocument refer to files that are not part of the project, such as our script files maybe?

I believe so, but should be checked.

@TIHan I removed the useUniqueStamp flag as part of https://github.com/Microsoft/visualfsharp/pull/4891, to clarify.

@saul Am I correct in thinking that WorkspaceChangeKind.AdditionalDocumentAdded/Removed is the correct thing, rather than watching MiscellaneousFilesWorkspace per se?  That is

scripts that are part of a project and not Compiled will get "AdditionalDocument" events in a normal workspace
scripts that are part of a project and marked Compiled be get normal "Document" events in a normal workspace
scripts that are not part of a project will be "AdditionalDocument" in "MiscellaneousFilesWorkspace"

@TIHan FWIW I don't think any changes to do with scripts need be part of this PR, which should focus on the problem with DocumentChanged event within projects first

@dsyme I’m not too sure. Unfortunately I haven’t looked at this in about a year.

PR is updated. I'm going to add a generated netcore solution so we can easily test this.

Tests have been added.

test Windows_NT Release_ci_part2 Build please

So the solution was to delete code that was already flag with weird comment?

@cartermp it's too late for 15.7.2?

@forki It's highly likely that it's too late for 15.7.2. Approvals for bugs we wanted to take for that went out last week.

Another valueable one to user test is SQLProvider: https://github.com/fsprojects/SQLProvider
It's definitely suffering today

@cartermp Are nightlies now usable with dev 15.7?  We should put out some kind of announcement when that switch happens? (I'm not on dev 15.7 yet)

Yes for both: https://dotnet.myget.org/feed/fsharp/package/vsix/VisualFSharp
We're producing 15.7.x versions for master and a build of a VSIX ought to do the same.

Doing some more testing today. So the MruCache for incremental builder is still getting invalidated, but this time after we get completions/intellisense. Something else is causing this, I'm going to investigate this.

Ok, I think I know what's happening from my last comment.
It's because of multi-targetting. Mutli-targetted projects, are treated as two separate logical projects in the workspace. My hypothesis is that FCS only keys off of the project file name, rather than project file name and TFM. When this happens, there could be a race condition, and depending on the race condition will kick off invalidation and rebuild the world.
So this is a bug already today and is not from our current changes made here. Perhaps I can make another PR to fix multi-targeting.

Just a note about AdditionalFiles - they are not files that are outside of projects like scripts.  Instead they are "extra" files added to to the compilation to be used as input to analyzers.  Things like the "PublicAPI.unshipped.txt" in the roslyn repo.
As @saul said, we should definitely be hooking into MiscellaneousFilesWorkspace instead of doing this in SetupNewView.

Couple of questions:

If the test code is just generated boilerplate, why not generate it on each run instead of checking it in?
What's with the C# only solutions?
Can you point me to where this stuff is actually exercised, or is that still a manual process?

The advantage of checking it in is that contributors usually have it easier
to use it. Also we have history of it (which can also be seen as a downside
;-))
Will Smith<EMAIL_ADDRESS>schrieb am Mo., 14. Mai 2018, 18:24:

We should probably not check in generated projects now that I'm thinking
about it.
I think the C# solutions are there for us to test against the F# ones to
see if we match perf.
All of this is a manual process. You just run fsi on the script.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/pull/4889#issuecomment-388877933,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNHEUd-0K-9fJl5RrT__FQ6eokPU2ks5tya_LgaJpZM4T8PFR
.

I'm removing the generated projects. I think it is fine to run the generation manually by invoking fsi. This keeps the commits much clearer than seeing 100s of generated files being committed. If we really want the generated projects to be committed, we can make a separate PR.

I'm removing the generated projects. I think it is fine to run the generation manually by invoking fsi. This keeps the commits much clearer than seeing 100s of generated files being committed. If we really want the generated projects to be committed, we can make a separate PR.

Yes make a separate PR please. The huge advantage of having them in the tree is that everyone, everywhere has exactly the same baselines to test against for VS perf, without any effort. That's incredibly valuable.

As said above +1 for checking them in. We already saw benefits of checked in test projects in older issues.

I’m for checking them in too. Another reason: the generation script does not work on Mac out of the box due to the windows style slashes in paths.


Cannox exit "idle" mode

Sometimes the displayed activity is stuck on "idle" mode

The transition from "idling" to the real activity takes a long time but I can't reproduce a case where it never transition :(
I will take a look on why it takes so long tho


HttpRequestException is thrown when AmazonClientException expected

Describe the bug
I'm calling method ListBucketsAsync while service is not accessible.
It throws unexpected exception:
System.Net.Http.HttpRequestException: No such host is known.
 ---> System.Net.Sockets.SocketException (11001): No such host is known.
   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean allowHttp2, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.DiagnosticsHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
   at Amazon.Runtime.HttpWebRequestMessage.GetResponseAsync(CancellationToken cancellationToken)
   at Amazon.Runtime.Internal.HttpHandler`1.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.RedirectHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.Unmarshaller.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.S3.Internal.AmazonS3ResponseHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.ErrorHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.ErrorHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.CredentialsRetriever.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.S3.Internal.AmazonS3ExceptionHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.ErrorCallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.MetricsHandler.InvokeAsync[T](IExecutionContext executionContext)
   at BSH.MES.Archiver.Models.EcsStorage.BSH.MES.Foundations.Common.IHealthcheckProvider.Check() in C:\Users\jinek\Repo\mes-platform\services\BSH.MES.Archiver\Models\EcsStorage.cs:line 44

Expected Behavior
AmazonClientException is thrown
Current Behavior
HttpRequestException is thrown
Reproduction Steps
Make a call to ListBucketsAsync for which server is unknown
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK <IP_ADDRESS>
Targeted .NET Platform
.NET Core 5
Operating System and version
Windows 10

@jinek  Could you please elaborate calling method ListBucketsAsync while service is not accessible? Are you not using the public S3 endpoint(s)? Under what scenario you get this error?

Before I gathered all this information. My complain is about wrong exception type. Exception must be AmazonClientException rather than HttpRequestException.
Does this make sense?

* Elaborate `calling method ListBucketsAsync while service is not accessible`?

Server is down, for example, when we try to list all buckets

* Are you not using the public S3 endpoint(s)?

Correct, that is not public s3

* Under what scenario you get this error?

S3 server is down, for example, when we try to list all buckets

* Share the sample code.

await new AmazonS3Client(
                new BasicAWSCredentials(environmentVariablesS3AccessKey, environmentVariablesS3SecretKey),
                new AmazonS3Config
                {
                    ForcePathStyle = true,
                    ServiceURL = environmentVariablesS3Url,
                    SignatureVersion = "2",
                    SignatureMethod = SigningAlgorithm.HmacSHA1,
                    UseHttp = false
                }).ListBucketsAsync();

* Share the detailed verbose logs.

How to do that?

* Are you using local stack (or any other virtualized environment)? We do not officially support these environments.

Yes, local, but that does not make difference I believe.

The error clearly states that the destination host is not accessible, may be due to network issue.
Exactly, that is network issue.

@jinek As per my understanding, the AmazonClientException would be thrown if there is any error response from the service while processing the request and the response unmarshalled. Here there is a socket error while connecting to the endpoint while obtaining connection from Http connection pool.

Documentation states "Exception thrown by the SDK for errors that occur within the SDK" here https://docs.aws.amazon.com/sdkfornet1/latest/apidocs/html/T_Amazon_Runtime_AmazonClientException.htm
Consumer can not know whether AmazonS3Client uses HttpClient, Socket or File IO or anything else, it's internal encapsulated functionality, which can be changed in the future ( and which can not be injected by a consumer as I understand ). In this situation would be correct to re-throw exactly AmazonS3Client.
Similar to this situation, SqlClient throws SqlException when network issues happen.

This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

What is the point to hurry to close a request from consumers? It's not necessary to work on unanswered requests, but closing the issue does not solve it.


Certain page causes crash

The program will crash if you try to search to or from "2023 Reddit API controversy"

Thanks for your bug report, this should now be fixed.


Custom Billing Provider: Route not found error.

Package
filament/filament
Package Version
v3.0
Laravel Version
v10.10
Livewire Version
v3
PHP Version
8.3
Problem description
When defining a custom billing provider, i get the error Route [the.route.name] not defined. Despite the route being available when running php artisan route:list
The route name is provided via the getRouteAction() method on the billing provider.
Expected behavior
Should load the view.
Steps to reproduce
## Setup

Start with a blank filament php project.
Add multi-tenancy
Install filament spark (otherwise you can't implement Filament\Billing\Providers\Contracts\Provider)
Create a middleware php artisan make:middleware RedirectIfOrganisationNotSubscribed
Create a custom billing provider by adding the below code to app/Providers/CustomBillingProvider.php

<?php

namespace App\Providers;

use App\Http\Middleware\RedirectIfOrganisationNotSubscribed;
use Filament\Billing\Providers\Contracts\Provider;

class CustomBillingProvider implements Provider
{
    public function getRouteAction(): string
    {
        return route('filament.admin.pages.subscription-management');
    }

    public function getSubscribedMiddleware(): string
    {
        return RedirectIfOrganisationNotSubscribed::class;
    }
}

Create a new filament page : php artisan make:filament-page don't select a resource. Call it SubscriptionManagement. You should now have a page that looks like this :

<?php

namespace App\Filament\Pages;

use Filament\Pages\Page;

class SubscriptionManagement extends Page
{
    protected static ?string $navigationIcon = 'heroicon-o-document-text';

    protected static string $view = 'filament.pages.subscription-management';
}

If you at this stage do a php artisan:route-list | grep "subscription-management" you will see your route

Recreate the error
In your panel provider add the following :
use App\Providers\CustomBillingProvider;

->requiresTenantSubscription()
->tenantBillingProvider(new CustomBillingProvider());

run php artisan route:list you will get the error :  Route [filament.admin.pages.subscription-management] not defined.

Reproduction repository
https://github.com/TheFrankman/custom-billing-provider-issue
Relevant log output
No response

You should not need to install Filament Spark, that interface is part of filament/filament
This is a route action. Imagine putting this into a Route::get(). Route::get('/billing', route('filament.admin.pages.subscription-management')) wouldnt work as it is run while routes are being registered.
Our docs have a good example: https://filamentphp.com/docs/3.x/panels/tenancy#writing-a-custom-billing-integration

public function getRouteAction(): string
{
    return function (): RedirectResponse {
        return redirect()->route('filament.admin.pages.subscription-management');
    };
}


Added strict_types to all php files

Fixed some type issues in tests, ReplaySubject, and Recorded
Fixes #116

Coverage decreased (-4.0e-05%) to 99.953% when pulling c0eb258e5a37285e57c526b22cf8bc9de381545f on davidwdan:strict into 9756162d74086967385bd9e47f64fa7e1a7fa497 on ReactiveX:2.x.

Coverage remained the same at 100.0% when pulling 0d8938754f453b8be1ea9e5a5ad7722176d3c5c2 on davidwdan:strict into f93f7dd7c80b19d4653232adf24551d70b38a46d on ReactiveX:2.x.

@asm89 I moved declare to a separate line and rebased on 2.x


Is this repo abandoned?

@jmcarp There are several outstanding PRs and the last commit was almost a year ago.

bump

I've had more time for this recently, and I'm happy to look at pull requests. I would also be open to sharing access on github and pypi to people who are interested in contributing--let me know if you want to help maintain the project.

Hi Joshua
I'd like to help.
Eddie
On Mon, Jan 16, 2017 at 10:33 PM, Joshua Carp<EMAIL_ADDRESS>wrote:

I've had more time for this recently, and I'm happy to look at pull
requests. I would also be open to sharing access on github and pypi to
people who are interested in contributing--let me know if you want to help
maintain the project.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jmcarp/betfair.py/issues/61#issuecomment-272977283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEASgq81d3rvX2m6-F72KkWl62ruoC2wks5rS_BPgaJpZM4IR9kb
.

Thanks @seriousdude, I just added you as a collaborator.


v1.11 Backports 2023-08-23

[ ] #25324 (@learnitall)

:warning: merge conflicts due to hive/cell refactoring.

[ ] #27184 (@pchaigno)

:warning: merge conflict due to file rename

[ ] #27168 (@learnitall)

:warning: merge conflict due to changed send_trace_notify call sites

[ ] #27365 (@mhofstetter)

:warning: merge conflict due to reduced list of k8s versions

Once this PR is merged, you can update the PR labels via:
for pr in 25324 27184 27168 27365; do contrib/backporting/set-labels.py $pr done 1.11; done

or with
make add-labels BRANCH=v1.11 ISSUES=25324,27184,27168,27365

/test-backport-1.11

/test-backport-1.11

/test-1.17-4.9


New docs structure

Docs structure overhaul as discussed in #179
This PR is meant to replace #179 and #182
What was done:

Created subpages for all major features (models/data/serving/building/deploy) in user-guide for each
Moved there hand-crafted documentation from extension docs in #179
index pages are from GS
Renamed Extension section into Object Reference
restructured it. was: <ext type>/<ext name>, now: <object group>/<ext name>. Now multipurpose extensions (eg docker has build & deploy) has two pages
Object Reference is now fully autogenerated
Added builtin implementations there too
Moved details about mlem abcs and mlem objects from UG

TODO:

[] Adjust moved GS texts to UG
[] Adjust same GS texts in GS: remove unnecessary explanations, make them more like "press this and watch"
[] Add/fix links to Object Reference

@madhur-tandon, in case you're looking for tasks: this PR have some pages that could be updated/rewritten. Like

/doc/user-guide/deploying/docker and other pages under /doc/user-guide/deploying/ basically
/doc/user-guide/remote-objects/dvc and other pages under /doc/user-guide/remote-objects
some pages in CLI and API reference needs updating as well

@madhur-tandon, this PR have some pages that could be updated/rewritten.

Thanks, will TAL

Sorry for late reply here (I'm still not feeling 100%).
I've been trying to review this and it makes sense in general but it's very hard to actually review such a large PR.
Could you split it? E.g. one for the GS changes, one for the user guide, one for automated pages, etc.

What does it mean that this PR is a draft. How much do we expect it to change? I'm a bit hesitant to perform a difficult review on something that may not be a solid proposal. I'll keep it super general for now ⏳ Thanks

OK nvmd my part of the review should be general/ high-level anyway. Here it is:

In general there's no consistency between nav entries, URL paths, and page titles. Prob not great for SEO. E.g. "Exporting models" (nav) vs. "Exporting models (builsing)" (title) vs. /doc/get-started/building (path) -- would address in a separate PR.
Get Started changes seem good 👍🏼 i.e. a good improvement based on the existing one (may eventually need complete rewrite but that's unrelated here)
User Guide:

Doesn't look like we need Basic concepts now since it only mentions MLEM Object and that has it's own reference section now.
Let's not re-use GS index pages. Nothing or short intro pages would be better. E.g. the /serving page could explain what we mean by "serving" and that in MLEM it can be done with mlem serve or the serve(); etc.
The pages under Exporting models (UG) feel very different to other guides since they're introductory tutorials taken form the GS. In general, UG pages lack unifying structure, format, and tone. (Refer to types of docs). We should make plans to address this separately as well.
Whats the difference between Exporting to Docker and Deploying to Docker? Another good thing to clarify in the related index pages.
Pages under Remote objects seem really short. You can probably make it a single section in the main guide page?
MLEM ABCs: this is indeed a reference, but even deeper than the objects section it's in. Probably we don't need this page in user docs (it doesn't seem for users but rather for developers of MLEM itself). Probably same for Extending. I don't think we need to target that kind of user in docs until a later phase of adoption of MLEM. Contributing to MLEM should be enough for now :)
Why are Models, etc. called "extensions" once you open the ref section? It's all built-into MLEM right? If not, should each section mention how to install MLEM to include them?

Important: There are still "TODO" and other misc. notes visible as well as incomplete sections. What's the plan? Hide them from nav or remove them from the PR for now, I think. We're trying to do too much in a single PR -- almost as if we expect that the PR will resolve everything and docs will be finished after that. Don't worry, docs are never complete 😋
TBH I would consider removing many pages that we're not sure about or are secondary and focus on what's most important for adoption and retention: the Get Started and basic but complete obj/cmd/api references. The rest of missing docs we can cover with good user support for some time.

Great improvement folks compared to what we have now!

Agreed, especially for the Get Started. It would be great to wrap up/ remove incomplete and temporary contents so we can merge some of this, or maybe extract the GS changes to another PR?


feat(api): drop tips in predetermined locations

Closes RQA-1007
Overview
Changes the drop tip randomization to drop tips in predetermined locations that it will alternate between. I've selected these two locations based on coverage area and the ability of pipettes to reach that location:

location along x-axis from well top-center, at a distance closer to left edge of labware well
location along x-axis from well top-center, at a distance closer to right edge of labware well

See comments and docstrings in the PR for detailed descriptions of these locations
Test Plan
Make sure the following tests succeed:

[ ] A single/8- channel pipette on LEFT mount is able to go through the predetermined locations without hitting the trash or walls when:

[ ] trash is in column 1
[ ] trash is in column 3

[ ] A single/8- channel pipette on RIGHT mount is able to go through the predetermined locations without hitting the trash or walls when:

[ ] trash is in column 1
[ ] trash is in column 3

[ ] A 96-channel pipette is able to go through the predetermined locations without hitting the trash or walls when:

[ ] trash is in column 1
[ ] trash is in column 3

[ ] Make sure that return_tip() behavior is not affected by this

Sample test protocol:
requirements = {
	"robotType": "Flex",
	"apiLevel": "2.15"
}

def run(protocol_context):
	# For Flex:
	tiprack1 = protocol_context.load_labware("opentrons_ot3_96_tiprack_1000ul", "D2")
	pipette = protocol_context.load_instrument("p1000_96", 'left', tip_racks=[tiprack1])
	# pipette = protocol_context.load_instrument("p50_single_gen3", "left", tip_racks=[tiprack1])

	# For OT-2
	# tiprack1 = protocol_context.load_labware("opentrons_96_tiprack_300ul", 2)
	# pipette = protocol_context.load_instrument("p300_single", "right", tip_racks=[tiprack1])

	for _ in range(10):
		pipette.pick_up_tip()
		pipette.drop_tip()

		# resets the tiprack so that we can use the same labware for testing w/ 96 channel
		# not needed if testing with other pipettes
		tiprack1.reset()
		protocol_context.pause(msg="Reload the tips in the tiprack")

	pipette.pick_up_tip()
	pipette.drop_tip(pipette.trash_container['A1'].top())	# Should only go to trash center. `alternateDropLocation` should be false

For QA & ABR testing, we only need to test 1, 8 & multi-channel pipettes with the OT3 trash bin in slot A3. Placing the trash in the left column will currently not calculate labware position on deck correctly so we cannot use that for testing.
Should also be tested for OT2 but is not a blocker for internal QA/ science testing for flex.
Changelog

removed total randomized drop tip
added next tip drop location getter to geometry view
other changes to facilitate fetching the correct locations

Review requests

Code review
Make sure the above points in test plan are tested and they cover all scenarios
I have tested all pipette combinations on OT3 for the fixed trash using engine commands and verified that the gantry or pipettes don't crash into anything anymore. We should also test running a python protocol that has a few tip drops.

Risk assessment

Less risky than dropping tip at total randomized location, which this replaces. There is still a decent risk that this would cause the pipette to go to an inaccessible location that could result in pipette/ tips bumping against the labware, but hopefully the check for fixed trash suffices for now.

@sfoster1 , true that it will probably create two piles of tips instead of one and will only mitigate the tip piling issue to a certain extent, but it will be an improvement. The main reason for deciding on two locations was that the 96 channel's tip piling would actually be best resolved when there's only two drop locations since the trash bin is slightly less than twice the width of the 96 channel. If we go for 3 locations, the fallen tips will overlap more number of times if there were only 2 locations. We could still have 2 locations only for 96 channel and more for the others but even with the other two pipettes, there's a dead zone in the trash that they can't reach (like the right half of the ot3 bin for left pipette). So the area for dropping tips reliably is much smaller than the big bin and we might be able to add maybe one or two more locations.
So all the above things considered, I concluded we could start with a blanket 2 locations for all pipettes and then add more for pipettes and situations that make more sense. And @SyntaxColoring has a good point above considering that plan, that calling them 'alternate' or 'alternating' locations is not a good idea. So I'm open to suggestions for naming this feature.


[BUG] The letters in a line can be set repeatedly

Description
Video shown below. After setting 5 letters you can set them again from the line start. The same applies to the case where numbers have been entered. Non-existent words won't be passed to the algorithm in this case, but it is possible to pass the wrong array.
Reproduce
Steps to reproduce the behavior:

Open the program
Type a valid word
Type another valid word without typing numbers first
See error

Expected behavior
Each word of the line can only be set once
Screenshots / videos
https://user-images.githubusercontent.com/40854260/156562282-61aab7f4-1db4-44c0-a08d-cca5650186b9.mp4
Environment

OS: Kubuntu 21.04
Java version: openjdk 11.0.15
WordleHelper version: 2.1.3

Additional context
The bug still exists in the latest version. I may fix it when I have time.

fixed in release 2.4.0


Re-publish & update old parsec manual

Extracted from #22.
@gbaz:

It would actually be very good if we could also pull the documentation from the homepage (as hosted by web.archive.org: http://web.archive.org/web/20140329210442/http://legacy.cs.uu.nl/daan/download/parsec/parsec.html) and ported the parts that aren't just haddocks into a new parsec documentation module or the like, and put some very simple "getting started" bits from them at the top of the main Text.Parsec module. (having updated them to work with the latest parsec).

Additionally there should be some top level documentation in the package indicating that that is the main entry point, and also which modules only remain for compatibility...

@aslatter:

I haven't heard from Daan Leijen that it would be okay to copy his text verbatim elsewhere, so anything pulled in to the package description or module documentation would need to be new text.

@gbaz:

did he just not reply to your email? did you try with a relatively recent address such as that in this paper (http://research.microsoft.com/pubs/210640/paper.pdf) ?

I hope we can get in touch with him, because it would be much easier to do things that way, and I can't imagine he would object, even if it is slow to get a response and get his approval...

@aslatter:

Yeah, that's the email I tried. It was a ways back.

I just spoke to Daan in person at ICFP and he signed off that A) copying his text vertabim is completely ok with him, and that updating and modernizing his text is also completely ok, but it should just be changed so the attribution reads that is based on his document but subsequently modified if this occurs, with a link perhaps back to the original documentation in the wayback machine.

He also apologized for being flaky about replying to email :-)

Where did the republished version end up?

It has not been republished -- the ticket is still open. The link was simply moved to the one available at archive.org: https://web.archive.org/web/20140529211116/http://legacy.cs.uu.nl/daan/download/parsec/parsec.html
It probably would be good if it was modernized and republished as above, but someone would need to do that :-)


[PerfSampleError] by <<renderer>> in (scanDomNode#workbench.desktop.main.js:131:56742)
at scanDomNode in out/vs/workbench/workbench.desktop.main.js:131:56742
at onContentsChanged in out/vs/workbench/workbench.desktop.main.js:135:3435
at onContentsChanged in out/vs/workbench/workbench.desktop.main.js:738:16414
at showAt in out/vs/workbench/workbench.desktop.main.js:738:16005
at u in src/vs/editor/contrib/hover/browser/contentHover.ts:247:10
at r in src/vs/editor/contrib/hover/browser/contentHover.ts:181:10
at t in src/vs/editor/contrib/hover/browser/contentHover.ts:229:10
at result in src/vs/editor/contrib/hover/browser/contentHover.ts:56:49
at invoke in out/vs/workbench/workbench.desktop.main.js:86:127
at deliver in out/vs/workbench/workbench.desktop.main.js:86:2004
at fire in out/vs/workbench/workbench.desktop.main.js:86:1588
at w in src/vs/editor/contrib/hover/browser/hoverOperation.ts:158:10
at s in src/vs/editor/contrib/hover/browser/hoverOperation.ts:106:10
at v in src/vs/editor/contrib/hover/browser/hoverOperation.ts:152:10
at <anonymous> in src/vs/editor/contrib/hover/browser/hoverOperation.ts:68:82
at h in src/vs/base/common/async.ts:890:12
at g in src/vs/base/common/async.ts:883:10

Go to Errors Site

As designed. The hover needs to do a sync layout to find out its content size such that the scrollbar can show/hide itself.