Fail when api token is missing

Which problem is this pull request solving?
If for some reason the api token is missing, we want to fail early.
List other issues or pull requests related to this problem
https://github.com/netlify/build/issues/1816
Describe the solution you've chosen
throws an error
Describe alternatives you've considered
n/a
Checklist

[x] The status checks are successful (continuous integration). Those can be seen below.

Thanks @mraerino!
Note: if the API token is missing in production, this should be a system error (most likely Netlify Build or buildbot).
In a local build (Netlify CLI), we currently require users to first run netlify init / netlify login.
https://github.com/netlify/cli/blob/8cb8f96606ef9d0cac64734ec03c476aa093000d/src/commands/build/index.js#L40-L43
So based on this, a missing token would also be a system error, i.e. throwing an error is appropriate (as opposed to using utils.build.failBuild() which would indicate a user error).


chore: bump update a package with Ref component

Fixes #4061.

A fix for #4061 was done in https://github.com/microsoft/fluentui/pull/15144. This PR simply bumps dependencies to pick the fix.

Codecov Report

Merging #4068 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4068   +/-   ##
=======================================
  Coverage   99.84%   99.84%
=======================================
  Files         183      183
  Lines        3280     3280
=======================================
  Hits         3275     3275
  Misses          5        5

Continue to review full report at Codecov.

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


Add swift support

Add basic support for Swift https://github.com/langston-barrett/treereduce/issues/13.
I've tested this and it seems to work. One problem is that it hangs on the latest revision after a few iterations https://github.com/langston-barrett/treereduce/issues/109. To work around this, I also have another branch based on an old revision https://github.com/ellishg/treereduce/tree/treereduce-swift, but I believe this is a different problem.

@ellishg Can you run cargo fmt? Looks like CI is failing on that step


Update aws-core, http-client-spi, ... to 2.17.258

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.17.104 to 2.17.258.
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 = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

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

Superseded by #252.


More than 32k concurrent queries may cause errors

If there happen to be more than 32 000 concurrent queries on a single connection we have no free stream ids for new queries and fail them with an error.
We could have an async sempahore with 32k permits to wait until a stream id is freed.
This could have a bad effect on performance, let's wait for some benchmarks to test different solutions.

Adding a semaphore would introduce nontrivial overhead. As no one ever complained about this in practice, I think we can close this. WDYT @Lorak-mmk?

I don't think we should close this becasue this is a potential problem which may come up in the future.
We could implement this and benchmark the effect - but it will have a very low priority.


WIP: Remove autocomplete and consume from separate package

Description
The search implementation in the library and service manual is very NHS.UK specific and makes the majority of our JS bundle size. Therefore I have removed it from the library and created a new NPM package which can be consumed by the NHS.UK applications which do need it.
The repository for the new package is here: https://github.com/nhsuk/nhsuk-header-search
The current NPM package is: https://www.npmjs.com/package/nhsuk-header-search--test
For now I have removed the old files from this branch and used the new NPM package to replicate the old functionality. This work would actually be done inside applications going forward.
Checklist

[x] Tested against our testing policy (Resolution, Browser & Accessibility)
[x] Follows our coding standards and style guide
[ ] CHANGELOG entry

Related issues #568 and #598


Components life cycle functions

His guys,
I am newbie with react.
Where should I write the component life cycle functions? (componentDidMount,componentWillUnmount, etc).
I have tried something like:
Counter.componentDidMount = function () {
alert('hi')
}
Inside the Counter.js, in Component folder, but it didn't work.

You cannot use lifecycle methods on a stateless functional component (see https://facebook.github.io/react/docs/reusable-components.html#stateless-functions). If you need to use them, use a regular React class.
class Counter extends React.Component {
  componentDidMount () {
  }
}

Closing this since it is not an issue with this project. Happy to answer questions, but you may have more luck on StackOverflow.

thanks. I got it.
In you opinion, what is the best way to implement a calling action looping using the start kit?
I want to call an update action every 3 seconds. I've tried though the route "index.js" using set interval. But on the second call it trow an error (i Think it lost the dispatch context).

Hi, thanks. I agree about pure tech questions should be posted on SO directly, but I think it's cool to answer project-specific questions like this one here ;) Thanks that was useful and not obvious the first time you look at the code (unless you are a React expert)
About the update, maybe i'm misunderstanding your question, but what prevents you to place "setInterval" in the componentDidMount? My code is as follow and works fine:
import './ViewerView.scss'
import React from 'react'

class ViewerView extends React.Component {

  componentDidMount () {
    console.log('componentDidMount: ViewerView')
    setInterval(()=>{
      console.log('update')
      this.props.refresh()
    }, 3000)
  }

  render() {

    const { viewerState }  = this.props

    return (

Viewer { viewerState.value }

    )
  }
}

export default ViewerView


Attempt to keep timestamps of the original Bear notes

This will allow users to still see the expected order of their files based on the modified date when migrating to Obsidian.
See #9

@coding-camel Do you have time to see if this fully (or partially) solves the timestamp issues? If so, I will adjust tests and merge the PR so everyone can enjoy a better migration process. :)

@bernardoamc
I tested this pr today, If a note was created at 12:40 and modified at 12:41.
Running the script at 12:43 makes it created at 12:41 and modified time of 12:41
So keeps the modified but loses the created date, which is the most important in my opinion.

@coding-camel Thanks for taking a look! I will spend some time playing with it to see what can be done, we are moving in the right direction. 😄

Hey there, hope no one minds me jumping in!
I ran into the same problem with the created timestamp when I tried to build a similar script in node.js. From my research it seems like you can't preserve or overwrite created value if we are copying the file over.
I sorta worked around it, but with a caveat:
To keep all of the original timestamps, I ended up storing the edited time first, then make all of the formatting changes directly to the original file in the Bear folder and move it over to preserve the files's created time. Lastly we write the original edited value back b/c we made those formatting changes directly to the original files.
The catch is that my solution requires the file itself to move. It only really worked because I only wanted the first tag to create the folder structure, instead of duplicating notes for each tag in a note. I'm not 100% sure how to implement that if we need to duplicate the notes for all of the tags within but hope it helps!

@DraconMarius Thank you for the insights, I really appreciate it! This is a fun problem to tackle.
I've been struggling to find time to make the necessary changes, but I'm totally open to incorporate those changes if anyone would like to take a stab at it. I also hope I can find more time soon to improve a few things in the code. 😄


Adds Crypto Support to Interactive Brokers

Expected Behavior
Be able to trade crypto in an IB account.
Actual Behavior
Not supported.
Potential Solution
Implement crypto support to IB:
https://interactivebrokers.github.io/tws-api/cryptocurrency.html
Reproducing the Problem
Deploy crypto algorithm to IB.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

Hi Alex, any updates on this? Thank you.


Try using withContiguousStorageIfAvailable in RangeReplaceableCollection.append(contentsOf:) before falling back to a slow element-by-element loop.

Fixes rdar://109059874
Should make a bunch of operations on naive RRC implementations much faster

@swift-ci please benchmark

@swift-ci please smoke benchmark

adding some benchmarks in https://github.com/apple/swift/pull/65802

@swift-ci please benchmark

Yup, new benchmarks detect the improvement, to say the least
IMPROVEMENT                                 OLD        NEW        DELTA     RATIO     NaiveRRC.init.largeContiguous               21.643     0.0        -100.0%   **21644.00x** NaiveRRC.append.largeContiguous             21.628     0.0        -100.0%   **21629.00x**

@swift-ci please smoke benchmark

Tests here https://github.com/apple/swift/pull/65953

@swift-ci please test and merge


Code example throws away all exceptions

https://docs.microsoft.com/en-us/power-bi/developer/embedded/embed-service-principal-certificate#step-4---get-the-certificate-from-azure-key-vault
    catch (Exception)
    {
        return null;
    }

Please don't ever put something like this in examples. People will copy paste it into production code making it extremely hard to troubleshoot & support. Not everyone knows just what incredibly bad practice this is.

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

ID: 236c57e5-a1ec-6244-d422-b40444e9050c
Version Independent ID: 2e83122b-755e-f888-d91e-d8af71fb47ef
Content: Embed Power BI content in an Power BI embedded analytics application with service principal and a certificate - Power BI
Content Source: powerbi-docs/developer/embedded/embed-service-principal-certificate.md
Service: powerbi
Sub-service: powerbi-developer
GitHub Login: @mberdugo
Microsoft Alias: monaberdugo

Thanks for pointing this out, @timabell . I asked the developers to provide an alternative code snippet. In the meantime, if you have any suggestions for what to put instead, I'd love to hear them.
Thanks again.

Thanks again, @timabell, for pointing out this problem. The code has been updated and should be live in a day or so.

Amazing, diff looks good to me :+1:  https://github.com/MicrosoftDocs/powerbi-docs/commit/29a731f1f3b6db47030e93d2be459de7a7cacf96


Grading instructions are only applied to the whole submission

Describe the bug
When assessing a text exercise in the Assessment editor on Artemis by using grading instructions the whole text is automatically selected for one grading instruction instead of only one sentence.
To Reproduce

I was only able to reproduce this in the EIST 21 course not in the test course at the Artemis production server.

Go to the assessment dashboard of EIST 21 and try to assess a text exercise submission with grading instructions by dragging and dropping a  grading instruction to the submission.
See that the whole submission is treated as one text block.
See that regardless of what you select the grading instruction is applied to the all parts of the submission without a grading instruction.

Expected behavior
The grading instruction should only be applied to one sentence as it was in previous versions.
Environment

 - OS: Windows 10
 - Browser : Chrome
 - Version: 91.0.4472.77 64 bit

@jpbernius I expect this issue was related to Athene, wasn't it? Was this resolved?

When Athene is enabled, we employ a different strategy to identify segments (see Bernius et al.) compared to the sentence strategy used otherwise.
This might result in the student answer being determined as one single segment (or block).
Generally speaking, this report sounds like intended behaviour.

So, the tutors cannot expect that this behavior changes in the near future?
Is there any workaround available besides manually selecting the desired text block? Manually selecting each sentence is not really beneficial for the grading workflow of the tutors.


msbuild v4 cannot reference newer versions of the build tools

Attempting to reference a newer build tools version gives a warning looking like this:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3258: The primary reference "Microsoft.CodeAnalysis.Workspaces.Desktop, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL" could not be resolved because it has an indirect dependency on the .NET Framework assembly "Microsoft.Build, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which has a higher version "<IP_ADDRESS>" than the version "<IP_ADDRESS>" in the current target framework. [C:\Users\kb\Documents\Visual Studio 2012\Projects\ExceptionSerializationCtorFixer\ExceptionSerializationCtorFixer\ExceptionSerializationCtorFixer.csproj]
It's the ResolveAssemblyReference task which generates this warning. The result is that the reference to the assembly which references the build tools assembly is simply ignored, resulting in the build failing later on. This issue has the consequence that Roslyn 1.0.0 cannot be used from VS2012. I have opened an issue at dotnet/roslyn#4166 with more details.
I'm not really sure how this issue can be resolved. Is it possible that an update could be made to the old build tools v4 in the .NET Framework and put into a KB update? Or distributed as part of the build tools v14 distribution?

Unfortunately, I don't think this is resolvable.  We can allow referring to lower versions of the assembly from a higher-versioned one through binding redirects, but that wouldn't work in reverse.  In your scenario we have to load Microsoft.Build v4 (to match MSBuild), and then we'd need to load Microsoft.Build v14 (required by Roslyn).
There might be some confusion here, because Microsoft.Build v14.0 is not a .NET Framework assembly, even though Microsoft.Build v4.0 is.  I'm not sure if that's resolvable on our side, though (especially from the 4.0 tools, which we're not updating).
I think we have to say that building projects that consume MSBuild 14 assemblies must be built with MSBuild 14.


Temporary URLs for the local filesystem do not work when a wildcard route is defined

Laravel Version
11.23.5
PHP Version
8.3
Database Driver & Version
No response
Description
Here is my filesystems.php config:
'local' => [
    'driver' => 'local',
    'root' => storage_path('app/private'),
    'serve' => true,
    'throw' => true,
]

And I have a wildcard route on web.php:
Route::get('{any?}', [HomeController::class, 'index'])->name('home')->where('any', '.*');

After that, when I access the generated temporary URL, it returns the content of the home route I defined above, instead of the content of the file in local storage.
Steps To Reproduce
Step1: Edit filesystems.php config:
'local' => [
    'driver' => 'local',
    'root' => storage_path('app/private'),
    'serve' => true,
    'throw' => true,
]

Step2: Add this line to the end of web.php:
Route::get('{any?}', [HomeController::class, 'index'])->name('home')->where('any', '.*');

Step3: Generate temporary url and open it.

I'm wondering if we will have any issues also when we use route fallback? 🤔

Haha, thank you. That’s a great solution. I almost forgot about route fallback. 😅
I would like to close this issue now.

Haha, thank you. That’s a great solution. I almost forgot about route fallback. 😅 I would like to close this issue now.

I'd suggest you to send a PR to the docs adding this as part of an alert on the Storage docs.


DEMO: Allow some Director attacks to run against a single vehicle

Allow some Director attacks to run against a single vehicle instead of always running on all of them. This speeds things up a bit during the demo and is written in such a way as to be completely backward compatible (for the web demo, for example).

Changes Unknown when pulling 885fabb2e659130bce6aeda1251811ed95934490 on awwad:demo_director_attack_vehicle_selection into ** on uptane:develop**.

Changes Unknown when pulling 885fabb2e659130bce6aeda1251811ed95934490 on awwad:demo_director_attack_vehicle_selection into ** on uptane:develop**.

Changes Unknown when pulling 885fabb2e659130bce6aeda1251811ed95934490 on awwad:demo_director_attack_vehicle_selection into ** on uptane:develop**.


fix(state): Retain state in chat.fullstack.cash

PR related to this trello task --> https://trello.com/c/7Y4Taodk

:tada: This PR is included in version 2.0.10 :tada:
Your semantic-release bot :package::rocket:


(BOLT-631) Support Hiera config for plan apply

When compiling catalogs for apply bolt should configure and use hiera. This data should by default come from the boltdir not the global or user specific puppet path.

My testing strategy so far:
Hiera data is configured in ~/.puppetlabs/bolt/
# /home/cas/.puppetlabs/bolt/hiera.yaml
---
version: 5

defaults:  # Used for any hierarchy level that omits these keys.
  datadir: /home/cas/.puppetlabs/bolt/hiera_data  # This path is relative to the environment -- <ENVIRONMENT>/data
  data_hash: yaml_data  # Use the built-in YAML backend.

hierarchy:
  - name: "Common"
    path: "common.yaml"

# /home/cas/.puppetlabs/bolt/hiera_data/common.yaml
---
cas_data: "cas"

This is the test plan
plan test (TargetSpec $nodes) {
  return apply($nodes) {
    notify { "hello ${hiera('cas_data')}": }
  }
}

Invocation and output
cas@cas-ThinkPad-T460p:~/working_dir/bolt$ bolt plan run test -n x6x9wezjmz9dbih.delivery.puppetlabs.net
Starting: apply catalog on x6x9wezjmz9dbih.delivery.puppetlabs.net
Finished: apply catalog with 0 failures in 1.31 sec
[
  {
    "node": "x6x9wezjmz9dbih.delivery.puppetlabs.net",
    "status": "success",
    "result": {
       *****ABBREVIATED******
      "logs": [
        {
          "level": "notice",
          "message": "hello cas",   <- got the hiera data
       *****ABBREVIATED******

This first iteration simply provides the path to the hiera.yaml supplied in either the default location(s) or specified in a configfile. I noticed in the ticket specification that there is mention of a default datadir if one is not provided. Does this imply that we should be parsing the hiera config and looking for a datadir?

CLA signed by all contributors.

I want to hold off briefly to see if we can get the config refactor merged first.


Icon Request: Medical Samples

Hi There
First off this icon set is great, such clean icons.  It really is great, thank you. It also happens to fit perfectly inline with an app I working on.  I would be really appreciative if you could add an icon that represents medical samples, I have looked through the set a bunch of times but none of the existing icons really fit my use case.  I have seen a few online that are nice an clean and would fit with the overall style of the icon set.

Many thanks
Steven

We recently added this to the collection. Thank you for your patience. https://healthicons.org/icon/filled/devices/medical_sample


[BUG] - Cancelling a flight leaves an unfinished pirep in phpvms which breaks the logbook

Describe the bug
In phpvms7, ongoing flights seem to create an incomplete pirep object with status pending which doesn't get deleted on cancellation.
This pirep also had a missing aircraft_id which breaks the logbook.
How do you reproduce this bug?

Bid on a flight in a phpvms7 instance
Start the flight
Cancel mid-flight
Observe a stale pirep object still being present in the database

Expected behavior
The pirep object gets deleted on flight cancellation by the user
Screenshots
No response
API Version
0.3.3
PHP Version
8
Database & version
Mysql
Webserver version
Apache 2
Browser
Any
Handler
Any
Additional context
No response

Related to #60. This will be resolved by adding a /flight/cancel to cancel an ongoing flight which will delete the data in the ongoing flights tables and also remove a PIREP in phpVMS 7

Related to #60. This will be resolved by adding a /flight/cancel to cancel an ongoing flight which will delete the data in the ongoing flights tables and also remove a PIREP in phpVMS 7

I would advise to use the phpVMS specific PIREP state and not delete the bid. This would solve the problem, and, keep it native to phpVMS 7 when a VA is running both vmsACARS and smartCARS 3.
class PirepState extends Enum
{
    public const IN_PROGRESS = 0;  // flight is ongoing
    public const PENDING = 1;  // waiting admin approval
    public const ACCEPTED = 2;
    public const CANCELLED = 3;
    public const DELETED = 4;
    public const DRAFT = 5;
    public const REJECTED = 6;
    public const PAUSED = 7;

    protected static array $labels = [
        self::IN_PROGRESS => 'pireps.state.in_progress',
        self::PENDING     => 'pireps.state.pending',
        self::ACCEPTED    => 'pireps.state.accepted',
        self::CANCELLED   => 'pireps.state.cancelled',
        self::DELETED     => 'pireps.state.deleted',
        self::DRAFT       => 'pireps.state.draft',
        self::REJECTED    => 'pireps.state.rejected',
        self::PAUSED      => 'pireps.state.paused',
    ];
}

Resolved in 0.3.5


404

http://<IP_ADDRESS>:8086/windows98_state.bin is returning 404

This happens when your browser (or HTTP client) doesn't support http compression. Compression is important because the file is rather big (it contains the whole memory) and compresses well (down to 10-15 MB).
What http client are you using?

I was on my work station, using chrome, it may been a problem on the proxy server we are using.
On my home station is all good

I was on my work station, using chrome, it may been a problem on the proxy server we are using.

That's probably it then. Could be fixed by letting users download the file uncompressed, but that's not great either.

No, it happens due to CORS (cross origin resource policy). That happens because either:

the host doesn't allow remote AJAX request on content
http and https is mixed


docs: add Hands-on tutorial

This pull request adds the following text to documentation after the line Getting Started Guides:
"Hands-on tutorial in a live environment to quickly get started with Cilium."

Signed-off-by: Van Le<EMAIL_ADDRESS>

On another note, can you please squash your commits into a single one, and add a Sign-off-by: tag to your commit description as explained in the automatic messages above?

Hello @qmonnet, thanks a lot for the comment!
I found out about Sign-off-by: after the first commit and couldn't figure out how to fix it. Squashing commits to the single one worked.
Also, it would be great if you can help with where this link should be placed.

Thanks for editing the commit!

Also, it would be great if you can help with where this link should be placed.

I was suggesting at the end of the same section, but below the list:

The changes look good to me, thank you.
Would you mind squashing your commits once more, please? Please also mind that the Signed-off-by tag is not correctly formatted: your email address should be enclosed between angle brackets, i.e. instead of this:
Signed-off-by: Van Le<EMAIL_ADDRESS>
it should be:
Signed-off-by: Van Le<EMAIL_ADDRESS>
This is what causes the Checkpatch action to fail with:
Error: ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Van Le<EMAIL_ADDRESS>

The changes look good to me, thank you.
Would you mind squashing your commits once more, please? Please also mind that the Signed-off-by tag is not correctly formatted: your email address should be enclosed between angle brackets, i.e. instead of this:
Signed-off-by: Van Le<EMAIL_ADDRESS>
it should be:
Signed-off-by: Van Le<EMAIL_ADDRESS>
This is what causes the Checkpatch action to fail with:
Error: ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Van Le<EMAIL_ADDRESS>

@qmonnet Thank you for the detailed comment on how to add Signed-off-by correctly!
The commits have been squashed with the correct commit message.

Looks all good, thank you!

Hi @qmonnet, I am wondering, is that possible to update this change to the stable version of documentation?

This means backporting the change to the latest stable branch. I have no objection with that, I'll add the relevant labels so we pick it up for the next round of backports.

This means backporting the change to the latest stable branch. I have no objection with that, I'll add the relevant labels so we pick it up for the next round of backports.

Thanks for the help!


[Feature request] Stricter keyword than extends for generics restricting excessive keys. Maybe is?

Search Terms
exact, generic, strict, keyword
Suggestion
I wish there is a way to enforce exact shape (same keys: no excessive keys allowed) of generic type.
new keyword is maybe?
Use Cases
Eliminate cases where excessive keys are supplied to generic object parameter and cause uncaught bugs.
Examples
const mapProperties = <
  T extends { [key: string]: any },
  U extends { [K in keyof T]: (v: T[K]) => any }
>(
  obj: T,
  mappers: U
): { [K in keyof T]: ReturnType<U[K]> } => {
  const res = {};
  Object.keys(mappers).forEach((key) => {
    res[key] = mappers[key](obj[key]);
  });
  return res;
};

// data to be transformed
const data = {
  a: 1,
  // b: 0, // used to exist but removed later
};

// in another file...
const mapper = {
  a: String,
  b: Boolean // not wanted anymore but forgot to remvoe
}

const res = mapProperties (data, mapper) // not throwing type error even if there is `b` in mapper and not in data.
// res = {
//   a: '1',
//   b: false // unwanted bug
// }

By using generics, res inherits return type from mapper

With new keyword
const mapProperties = <
  T extends { [key: string]: any },
  U is { [K in keyof T]: (v: T[K]) => any } // enforces exact keys
>(
  obj: T,
  mappers: U
) ...

mapProperties ({a: 1}, {a: String, b: Boolean}) // error because `b` does not exist in T.

Checklist
My suggestion meets these guidelines:

[ x ] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[ x ] This wouldn't change the runtime behavior of existing JavaScript code
[ x ] This could be implemented without emitting different JS based on the types of the expressions
[ x ] This isn't a runtime feature (e.g. new expression-level syntax)

@mattmccutchen It works for simple case, but it dosen't when the data has optional key.
For example,
interface Data {
a: number
b?: string
}

There's a hack for that, you may google "exact types". Copied from another issue:
export type Exactify<T, X extends T> = T &
  { [K in keyof X]: K extends keyof T ? X[K] : never }
``

@wkrueger I don't see how it can be applied to the above case. Could you explain?

Let's say you want no extra keys in U
//original
const mapProperties = <
  T extends { [key: string]: any },
  U extends { [K in keyof T]: (v: T[K]) => any }
>(
  obj: T,
  mappers: U
) { }

//changed
type Exactify<T, X extends T> = T &
  { [K in keyof X]: K extends keyof T ? X[K] : never }

const mapProperties = <
  T extends { [key: string]: any },
  U extends Exactify<{ [K in keyof T]: (v: T[K]) => any }, U>
>(
  obj: T,
  mappers: U
) { }

From https://github.com/Microsoft/TypeScript/issues/12936#issuecomment-368244671

@wkrueger
So I've tried your code and the following code compiles without error even though it should complain for missing 'c' in mapper functions.

// changed
type Exactify<T, X extends T> = T &
  { [K in keyof X]: K extends keyof T ? X[K] : never };

const mapProperties = <
  T extends { [key: string]: any },
  U extends Exactify<{ [K in keyof T]: (v: T[K]) => any }, U>
>(
  obj: T,
  mappers: U
): {
  [K in keyof U]: U[K] extends (a: any) => any ? ReturnType<U[K]> : never
} => {
  const res = {};
  Object.keys(mappers).forEach((key) => {
    res[key] = mappers[key](obj[key]);
  });
  return res as any;
};

const before: { a?: number; b: number; c?: string } = { b: 1 };
const after = mapProperties(before, {
  a: (x?: number): string => (x && x.toString()) || '',
  b: (x?: number): boolean => !!x,
  // c: missing => should throw an error, but doesn't
});

#14829 tracks a way to use type parameters without creating inference sites for them, which would be one approach.
#14520 tracks bounding generics from below rather than above, which may be an acceptable approach but probably not.
In general we're very unlikely to add features that completely eliminate subtyping and try to enforce an "exact" relationship - mapper in the OP should always be able to stand in for an object with fewer properties. Trying to nail down a definition of "the same type, not a subtype" is a trap because it prevents us from making new useful distinctions within extant type domains later on.

@RyanCavanaugh so why do you think that bug with new keys in the state is ok?
const changeState = <TState, TChanges extends Record<keyof TState, TState[keyof TState]>>(
  state: TState,
  changes: TChanges
) => {
  return {
    ...state,
    ...changes,
  }
}

changeState(
  { a: 1 },
  {
    b: 2, // should show error here because it is new key, but it doesn't
    a: 1,
  }
)

@RyanCavanaugh so why do you think that bug with new keys in the state is ok?
const changeState = <TState, TChanges extends Record<keyof TState, TState[keyof TState]>>(
  state: TState,
  changes: TChanges
) => {
  return {
    ...state,
    ...changes,
  }
}

changeState(
  { a: 1 },
  {
    b: 2, // should show error here because it is new key, but it doesn't
    a: 1,
  }
)

There's a hack for that, you may google "exact types". (Copied from another issue) use that in your extends clause.
export type Exactify<T, X extends T> = T &
  { [K in keyof X]: K extends keyof T ? X[K] : never }

Thanks, that helps, but unfortunately it produces a very strange error message that hardly anyone understands except who wrote that code.

There's a hack for that, you may google "exact types". (Copied from another issue) use that in your extends clause.
export type Exactify<T, X extends T> = T &
  { [K in keyof X]: K extends keyof T ? X[K] : never }

That helps, but unfortunately it produces a very strange error message that hardly anyone understands except who wrote that code.


Using mod on 1.18 with sodium causes new "simulation distance" to be swapped with brightness

I've found that using sodium on 1.18 alongside this mod causes the simulation distance and brightness settings to be swapped in the video settings, so the simulation distance can be adjusted from -100 to 1200, and the brightness from 0 to 100.

This has to do with the "old" sodium compatibility implementation which was selecting the slider by its position and not by its name. It was a pretty sketchy quick and dirty workaround bcs I didnt know better at that time, but I improved the sodium compatibilty a while ago and that should also fix this issue, its just that the owner hasn't merged that pullrequest yet.

mod on 1.18 doesn't work?

It should. Even for 1.18.1. It's just the bug mentioned above, for which there's already a fix, but the owner needs to merge and build himself to update the mod page. This will only affect you if you're using sodium and even then the mod should be usable, it might just be a bit complicated using the keybinds instead of the slider

It should. Even for 1.18.1. It's just the bug mentioned above, for which there's already a fix, but the owner needs to merge and build himself to update the mod page. This will only affect you if you're using sodium and even then the mod should be usable, it might just be a bit complicated using the keybinds instead of the slider

should I wait for the release for 1.18+?.. will he? and how soon?

Fixed! Sorry for the delay!


Disable viewport touchscreen navigation buttons on desktop by default

Godot version
Godot 4 Beta 8
System information
Windows 11/64, RTX 3070, Vulkan
Issue description
Desktop users without a touch screen have no need for these. They are now in the way for what I assume is the majority of users.

Unless touch screen & mobile platforms have taken over the majority of the user base, these buttons should either be:

disabled by default, or
disabled on detected desktop, non-touch screen, non-mobile systems by default, or
disabled on the desktop vulkan renderer by default

And the setting should not be buried deep in the editor settings where casual users will not find them (editors/3d/navigation/show_viewport_navigation_gizmo). They should be readily accessible in the menu, viewport settings, or viewport menu so that users can easily toggle them on or off. Since it's once per system, I suggest Editor menu, Viewport Settings or View, Gizmos.
Added by #69364, default by #69523
Steps to reproduce
Open the editor
Minimal reproduction project
n/a

#69523 should be setting the default to disabled for devices that don't have a touchscreen connected. However, it doesn't change the value that is currently set. Can you confirm if you are testing on a device that ran the engine after #69364 was merged but before #69523 was merged? If so, you have to set the setting to false manually. Any desktop device without a touchscreen should default to false after #69523
Cc @m4gr3d

Ah, I see. I've run master builds and b7 and b8, so likely have run before during and after the merges of all of those.
I do note that the editor defaults are:

I deleted my editor settings and opened an old project and the buttons were gone. With those defaults, I no longer feel so strongly about making the setting more visible.
So it may be fine, except for any advanced users who used builds between those PRs. I guess they'll just have to find this ticket. I'm fine closing this, unless you want to keep it open for adjusting the settings or forcing it off for desktop as @akien-mga wonders here (https://twitter.com/Akien/status/1601474727146819584?s=20&t=YK2am4wCsrMel7KzVfgGBA) ?

It's likely worth having a conversation, so let's leave this open for now to let others weigh in. As a lot of people are testing the betas this is likely to annoy a lot of people. And it's made worse by the fact that the issue doesn't go away on its own.

just to add an observation - I too had these appear (on a desktop non-touch device) and looked in the editor options without finding anything suitable to change to remove them. I believe I did change those Gizmo options but they had no effect until I restarted the editor or closed and reopened the scene I was editing, hence not realizing they were the correct options.
the odd thing is they kept magically appearing, even after I disabled them which is pretty frustrating. I discovered this appears to be caused by activating a camera as the preview in the viewport (select a camera, press Ctrl+P to preview, Ctrl+P again to exit)  Once you exit the preview they reappear once more and cannot be disabled without restarting/reopening the scene.

@akien-mga I also just observed what @ualac ualac reported. Preview a camera, turn it off, and the gizmos appear. I found I could switch to another scene and back to make them disappear. Perhaps we can follow up in https://github.com/godotengine/godot/issues/70269

Sorry never mind. The issue with the gizmos on camera preview has been fixed in the latest master build.


All re-processing of transactions if still in AWAITING_PAYMENT state

Coverage remained the same at 41.502% when pulling c0661ddf38a3a40ef3012b9c16604259c0227a9e on awaitingpayment into aa0fd469b1c63726c623b4066d65a7cb76938874 on master.


rust filetype: lifetime completion ends up with double single quotes

Lifetime completion triggers only after &' (using rust-analyzer), but ends up with &''lifetime, see below.

Is it possible to complete without extra single quote?

So far I'm using following workaround:
hook global WinSetOption filetype=rust %{
    hook window InsertCompletionHide .* %{
        try %{
            evaluate-commands -draft %{
                select %val{hook_param}
                execute-keys <a-k>'\w+<ret>
            }
            select %val{hook_param}
            execute-keys -with-hooks <esc><a-:><a-semicolon><semicolon><a-d>A
        }
    }
}


Flaky e2e test: open > Correctly handles an mpy file

This test regularly fails when run in GitHub actions. This wasn't an issue in CircleCI, or at the least not so frequent.
Running 100s of times in a loop locally, I can't get it to fail.
For example, this build.
    Evaluation failed: Error: Found multiple elements with the text: This version of the Python Editor doesn't currently support adding .mpy files.

    Here are the matching elements:

    <div
      class="chakra-alert__desc css-zycdy9"
    >
      This version of the Python Editor doesn't currently support adding .mpy files.
    </div>

    <div
      class="chakra-alert__desc css-zycdy9"
    >
      This version of the Python Editor doesn't currently support adding .mpy files.
    </div>

We dump a screenshot after the failure which only shows a single toast:

This is the only test that would trigger that error message.
Debugging the app when openg the test file locally, it inserts the alert, sets a timeout then removes the toast. At no point can I see another copy in the DOM, at least in the subtree the toast manager uses.
If we triggered the error twice then this could make sense, as the toasts stack. But to compound my confusion, we go out of our way to close any open notifications when we load a new file.
We could relax what's being asserted, but it makes no sense to me.

This post-fix job failed in a somewhat similar way (though a different test). I don't think it can be quite the same issue as of the two previous matches only one was actually role=alert.
https://github.com/microbit-foundation/python-editor-v3/actions/runs/4331196449/jobs/7562883041


No additional information popup when hover(mouseover) element

Issue Type: Bug
Hey All,
I have experienced some issue, that strongly decreased my productivity.
On Ubuntu 16.04 when I put mouse over some code after some time (300ms) it shows popup with additional info (e.g. type of variable).
Recently I have installed Ubuntu 18.04 and there is problem with this feature. It simply doesn't work.
I don't know if it can help, but when I install this new Ubuntu ditro I had some problems with Google Chrome and I need to disable GPU hardware acceleration.
I don't know if it is possible in VS Code. Maybe I can check if this can solve my problem.
Best regards,
Bartek
VS Code version: Code 1.30.2 (61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8, 2019-01-07T22:49:48.319Z)
OS version: Linux x64 4.15.0-44-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3429)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarewebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
31.32GB (24.26GB free)

Process Argv
--unity-launch

Screen Reader
no

VM
0%

Extensions: none

/duplicate https://github.com/microsoft/vscode/issues/15211


added JSDOM instead of Node support for elems as an experiment

Doing this makes it work for Deno, but absolutely breaks browser support. This was also refactored with Claude and I had to fix/patch some weird inconsistencies, so PLEASE DON'T MERGE THIS AS IS!
Probably the best way to do this is to have a third non-Node build that uses JSDOM instead of relying on Node types, which prevents it from working in Deno (https://news.ycombinator.com/item?id=41047445), but that's not what I did in this PR...

Hi @janzheng, thanks for following up and this sounds interesting!
My bad for not including a style guide / lint configuration.. Thing is, I can't really tell what changes have been made since your pull changed indentation of all sources.. Any chance for an easy fix on your side?

haha I guess that's the problem with using Claude. Thankfully Claude can help us diff... The only real changes are in this file, where I removed all references to Node:
htmlToMarkdownAST.ts: (Claude diff: https://claude.site/artifacts/7af5d198-2b1b-4900-a403-feea7b1dd132)

Changing childElement.nodeType === Node.TEXT_NODE to childElement.nodeType === childElement.TEXT_NODE so we're not dependent on Node
Claude also insisted on editing the table element to only prefer content: htmlToMarkdownAST(cell as Element, options, indentLevel + 1), — I quickly tested it but couldn't find any difference in output

domUtils.ts: ignore this one; none of the changes affect conversion
I noticed that in my outputs I get <-header-> tags, which is from markdownASTToString.ts:202 but for some reason your examples aren't showing these headers?
<-header->

<-nav->
 [Home](/) [Blog](/blog/) [About](/about/)

</-nav->
# SoftwareYoga

Articles on Coding and Architecture

</-header->

It's still hard to know what changes have been made :(
So please cleanup the pull request reverting unwanted changes..
Does this make sense? -
As I am not familiar with Deno, if we are looking for proper support for it in addition to Node (and as you say they are not compatible), please check out examples/cli where we build and publish the cli version n2m on every new version in addition to the NPM package in the root. Copy it and create examples/deno where you can make all the relevant changes to be able to publish and run a Deno compatible version.
Re- "<-header->", do you mean you are running some code from the examples and its producing a different output? Please let me know how to reproduce.

On my end, this worked just fine with Bun.
function setupDOMPolyfill() {
  const dom = new JSDOM("<!DOCTYPE html>");

  // Polyfill global objects if they don't exist
  if (typeof global.window === "undefined") global.window = dom.window as any;
  if (typeof global.document === "undefined")
    global.document = dom.window.document;
  if (typeof global.Node === "undefined") global.Node = dom.window.Node;
  if (typeof global.Element === "undefined")
    global.Element = dom.window.Element;
  if (typeof global.HTMLElement === "undefined")
    global.HTMLElement = dom.window.HTMLElement;
  if (typeof global.DOMParser === "undefined")
    global.DOMParser = dom.window.DOMParser;
}

// Call the polyfill setup function
setupDOMPolyfill();

worked for me with Next.js as well

I'm running these server-side on Deno, so I don't have access to global — but the issue I'm running into is Deno's lack of Node which means I can't compare Node.TEXT_NODE:
Uncaught (in promise) ReferenceError: Node is not defined
        } else if (childElement.nodeType === Node.TEXT_NODE) {

But apparently it's an easy fix (ignore my pull request). Apparently I can just replace any Node.TEXT_NODE with 3, and Node.ELEMENT_NODE with 1 (https://developer.mozilla.org/en-US/docs/Web/API/Node/nodeType) e.g. and it works.
} else if (childElement.nodeType === 3) {

instead of

} else if (childElement.nodeType === Node.TEXT_NODE) {

I also had to make a quick change to/src/index.ts: (added "type" after import, otherwise it wouldn't import properly)
import type {ConversionOptions, SemanticMarkdownAST} from './types/markdownTypes';

@janzheng following your example, I added the Node constants via library local _Node object and added the type import, if possible, please try the latest version and let me know if it works for you

Seems to still rely on Node; here's a live example: https://www.val.town/v/yawnxyz/denoDom2SemExample

@janzheng cool site!
Looks like it's working with a later version here's my fork: https://www.val.town/v/romansky/denoDom2SemExample

fantastic, thanks so much for your hard work!!

Thanks for the quick fix; this library works for cloudflare puppeter with linkedom as the DOM Parser now!


add ability to disable thread pool used to complete futures in async clients

This PR introduces a new config option available to all the AWS extensions, making it possible to disable the default 50 thread pool described here: https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/asynchronous.html#advanced-operations

going to reopen this from another branch so I can work on a few other ideas...


Bug. The child blocks of the custom Todo are not rendering properly.

Default Todo

Custom Todo

I have identified the cause of the issue and am currently working on a solution. @myjeong19


Can't push_back into a Vector2Array inside a Dictionary

Operating system or device - Godot version:
Linux 64bits, godot 2.1.3
Issue description:
I pushed a Vector2 into a Vector2Array but nothing was inserted.
Steps to reproduce:
 func _ready():
    var d = {}
    d["goo"] = Vector2Array()
    d["goo"].push_back(Vector2(0,0))
    assert(d["goo"][0]==Vector2(0,0))

Yes you cant, they are atomic. Also pushing back in those is slow. Just
resize to max size, set all elements and then ads it to the dictionary
On Jul 19, 2017 9:24 PM, "argent0"<EMAIL_ADDRESS>wrote:

Operating system or device - Godot version:
Linux 64bits, godot 2.1.3
Issue description:
I pushed a Vector2 into a Vector2Array but nothing was inserted.
Steps to reproduce:
func _ready():
var d = {}
d["goo"] = Vector2Array()
d["goo"].push_back(Vector2(0,0))
assert(d["goo"][0]==Vector2(0,0))
Link to minimal example project:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/9726, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z22EfsO7oJyMJmcmJ-eRnuYYUKUlvks5sPp5ZgaJpZM4OddYJ
.

Ok, thanks for the quick reply

Just curious, what does "atomic" mean here? Do you mean "immutable"? If so, should it generate an error if used incorrectly?

Related to https://github.com/godotengine/godot/issues/8409 ?

@voithos yes, i'm sorry, not sure of the right word. their reference is not shared when you pass them around.


[Bug]: Display package body even when there is no package body in the native Oracle package

ODC version
odc424
OB version

What happened?

What did you expect to happen?

How can we reproduce it (as minimally and precisely as possible)?
Create a package with only a header in native Oracle
Anything else we need to know?
No response
Cloud
No response

pass


Requires a blockjoin and layerjoin elements.

blockjoin would occur between all individual items within a block, but not before the start or after the end.
layerjoin would occur between all individual blocks within a layer, but not before the start or after the end.

The one sticking point with json output making invalid json was a trailing comma. after the blocks. This would allow that generic element to be covered. This is how ",".join() works in python, hence the analogy. The code here could then produce absolutely valid json.

Added in 0.5.0

Added in 0.5.0


fix(components): change components to be mobile first (WIP)

closes #1923

reverses max-width breakpoints to be min-width
table will continue to use max-width

Preview: https://patternfly-next-pr-2816.surge.sh

@christiemolloy what do you think about reversing these? https://github.com/patternfly/patternfly-next/blob/438890b5f67cb795aef3e01926f5e5d9208bd5b8/src/patternfly/sass-utilities/scss-variables.scss#L141-L143

Hmm... I'm having a hard time tracking down why I'm seeing style in the PR preview:
.pf-c-page__main-section.pf-m-no-padding,.pf-c-page__main-section.pf-m-no-padding-on-2xl,.pf-c-page__main-section.pf-m-no-padding-on-lg,.pf-c-page__main-section.pf-m-no-padding-on-md,.pf-c-page__main-section.pf-m-no-padding-on-sm,.pf-c-page__main-section.pf-m-no-padding-on-xl {
    padding: 0
}

I'm looking in your PR and don't see code that would generate that line. Also when I compile the CSS locally either using npm run build-patternfly or just sass patternfly.scss, I don't see those styles. @christiemolloy any idea what that might be?
The reason I mention that is, in all of the demos where we had .pf-m-no-padding-mobile, this PR changes it to .pf-m-no-padding-on-md, but that will still leave the padding on mobile since .pf-c-page__main-section has padding by default. We'll either need to add .pf-m-no-padding to the class list on those main sections we want to remove the mobile padding from, or leave .pf-m-no-padding-mobile and use that instead.


Extracting the core library for non Symphony usage?

Hi, Any chance to extract this library for regular PHP usage?

I have the same issue, I managed to do that with some kind of tricks.
$container = new ContainerBuilder();
$bundle = new RMSPushNotificationsBundle();
$bundle->build($container)
$extension = $bundle->getContainerExtension();
$container->registerExtension($extension);
$extensions = [$extension->getAlias()];
$container->getCompilerPassConfig()->setMergePass(new MergeExtensionConfigurationPass($extensions));
$loader = new YamlFileLoader($container, new FileLocator($pathToConfigFile));
$container->compile();
Small part of logic that implemented in Symfony kernel


'Clear all selections' button does not work after coming back from Preview

n/t

This, I can't replicate. It works fine for me. There must be something else going?

@jazzido: any help on replication?

Closed for inactivity :D
Obvi reopen if you're able to replicate.


401 unauthorized error building docker image

We are using py-cov-action/python-coverage-comment-action@v3. Just started getting this error in our workflows:
/usr/bin/docker build -t b5c86f:646c26769b564c28b3472eebdb5a7171 -f "/home/runner/work/_actions/py-cov-action/python-coverage-comment-action/v3/Dockerfile" "/home/runner/work/_actions/py-cov-action/python-coverage-comment-action/v3"
  #0 building with "default" instance using docker driver

  #1 [internal] load build definition from Dockerfile
  #1 transferring dockerfile: 245B done
  #1 DONE 0.0s

  #2 [auth] ewjoachim/python-coverage-comment-action-base:pull token for registry-1.docker.io
  #2 DONE 0.0s

  #[3](https://github.com/shadowpuppet/reloaded/actions/runs/11077471336/job/30782787497?pr=3028#step:3:3) [internal] load metadata for docker.io/ewjoachim/python-coverage-comment-action-base:v6
  #3 ERROR: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Aewjoachim%2Fpython-coverage-comment-action-base%3Apull&service=registry.docker.io: [4](https://github.com/shadowpuppet/reloaded/actions/runs/11077471336/job/30782787497?pr=3028#step:3:4)01 Unauthorized
  ------
   > [internal] load metadata for docker.io/ewjoachim/python-coverage-comment-action-base:v[6](https://github.com/shadowpuppet/reloaded/actions/runs/11077471336/job/30782787497?pr=3028#step:3:6):
  ------
  Dockerfile:2
  --------------------
     1 |     # See Dockerfile.build for instructions on bumping this.
     2 | >>> FROM ewjoachim/python-coverage-comment-action-base:v6
     3 |
     4 |     COPY coverage_comment ./coverage_comment
  --------------------
  ERROR: failed to solve: ewjoachim/python-coverage-comment-action-base:v6: failed to resolve source metadata for docker.io/ewjoachim/python-coverage-comment-action-base:v6: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Aewjoachim%2Fpython-coverage-comment-action-base%3Apull&service=registry.docker.io: 401 Unauthorized

It looks like the v6 tag (and v2-v5) are not present in docker hub: https://hub.docker.com/r/ewjoachim/coverage-comment-action/tags

@crimsonknave you're talking about hub.docker.com/r/ewjoachim/coverage-comment-action/tags instead of hub.docker.com/r/ewjoachim/python-coverage-comment-action-base/tags
I can imagine the whole thing being a transient Docker Hub issue, is it still happening? I'm not seeing in in any repository using this action. Note: seeing your message, it seems your project is private so I can only guess. Do you do special docker login stuff in your workflow ?

Whoops, you're right.
I can confirm that everything is working for me now. Does seem like some sort of transient issue.

https://www.dockerstatus.com/pages/history/533c6539221ae15e3f000031

September 27, 2024 13:47 PDT
September 27, 2024 20:47 UTC
[Investigating] Personal Access Tokens are failing to authenticate against Hub Registry., which includes pulls from GitHub Actions. Anonymous pulls and password auth continue to work.

September 27, 2024 14:10 PDT
September 27, 2024 21:10 UTC
[Identified] Issue identified and fix applied, error rates are slowly returning to normal.

September 27, 2024 14:20 PDT
September 27, 2024 21:20 UTC
[Monitoring] Access Tokens are working again, and error rates have returned to normal. Will continue to monitor.

September 27, 2024 17:27 PDT
September 28, 2024 00:27 UTC
[Resolved] Access Token authentication has continued to be functional and stable.


EVCC ValueError: too many values to unpack (expected 2)when parsing load points from MQTT

I'm trying to run BatControl with the EVCC connection:
Config is:
evcc:
  enabled: true
  broker: localhost
  port: 1883
  status_topic: evcc/status
  loadpoint_topic:
    - evcc/loadpoints/1/charging
    - evcc/loadpoints/2/charging
  tls: false

EVCC data in MQTT looks good to me:

But something seems to be wrong with parsing the load points data.
I'm getting the error:
ValueError: too many values to unpack (expected 2)

Any ideas?
I'm using the latest docker image for BatControl.

Latest is the last release and does support only one loadpoint.
the multiple loadpoint version is not released yet. I can build an intermediate testing image on the current development branch „main“.

Try using tag „main“ instead of latest. This was just built and is like a snapshot build. That should work.

Thanks, the main docker tag works! Very promising project.


Add OSGi Metadata

Fixes #125.
Adding metadata to the following modules:
google-oauth-client
google-oauth-client-java6
google-oauth-client-servlet
google-oauth-client-appengine
google-oauth-client-jetty
I skipped the following module, as it seems to be a special module for assembling a zip:
google-oauth-client-assembly

@briandealwis

I set the execution phase of org.apache.felix to compile instead of process-classes to maintain the same execution order: org.apache.felix (compile) --> maven-jar-plugin (compile) --> maven-datanucleus-plugin (process-classes).
I set Bundle-RequiredExecutionEnvironment to JavaSE-1.6, as I see there is google-oauth-client-java6.

Do they look good?

After investigation, I learned that mvn package will anyway re-package and re-write jars in the package phase that were created in the compile phase. Therefore, I removed all the <phase>compile</phase> setting for maven-jar-plugin, as I see no point of packaging twice (unless if it's for convenience for development).

@anthmgoogle @ejona86 @garrettjonesgoogle PTAL

LGTM although I don't have much context on this build configuration stuff. We should wait on a review by both @ejona86 and @garrettjonesgoogle, and potentially at-wonderfly if we still feel short on context.

LGTM, although like @anthmgoogle , I haven't worked with this packaging stuff much so I don't have any insight into it.

ping @ejona86

ping @ejona86

ping @ejona86

LGTM. Like the others, I don't think I would really be able to spot a bug, but it does appear sensible.

@anthmgoogle could you merge this?

ping @anthmgoogle Can you please merge this?


Lexer and parser overhaul

This is a WIP branch with a total overhaul of lexical analysis, source range tracking, diagnostics reporting, and much of the parser. It includes an AST model of custom character classes, comments, quotes, ranges, etc.
I don't know how long it will be before I have this merge-worthy (hopefully pretty soon), but I want to keep @hamishknight informed on the direction. @hamishknight another possibility is for me to start to pull stuff off into mergeable PRs, or you cn start working on top of this branch. Let me know what makes sense to you.

Ok, all but 2 tests are now passing. Those are some of the recent legacy tests over the new matching engine, and it seems like we parse it identically. So not sure what's going on there. We can comment/XFAIL and merge at any point.

@swift-ci please test linux platform

@hamishknight  I believe this is mergeable (even though there's still some fatal errors, existing tests don't hit them). WDYT?

I believe this is mergeable (even though there's still some fatal errors, existing tests don't hit them). WDYT?

Good with me!

@swift-ci please test linux platform

IMHO it would've make a cleaner commit history on main if these commits were squashed before merging. WDYT?


Tokenlist schema is missing

The JSON schema ID is https://uniswap.org/tokenlist.schema.json => gives

Eror😭

Seems to be back online. Closing the issue.


OSL-1189 Adding back buildkit for config-vaildator in main

Task linked: OSL-1189 Tekton configuration prevents CI from triggering on merges to main


error while start electron

is4800@IS-S1475 MINGW64 /d/projects/electron-quick-start-master/electron-quick-start-master
$ npm start
<EMAIL_ADDRESS>start D:\projects\electron-quick-start-master\electron-quick-start-master
electron main.js
fs.js:549
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: ENOENT: no such file or directory, open 'D:\projects\electron-quick-start-master\electron-quick-start-master\node_modules\electron-prebuilt\path.txt'
at Error (native)
at Object.fs.openSync (fs.js:549:18)
at Object.fs.readFileSync (fs.js:397:15)
at Object. (D:\projects\electron-quick-start-master\electron-quick-start-master\node_modules\electron-prebuilt\index.js:4:42)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v4.4.7
npm ERR! npm v2.15.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: electron main.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'electron main.js'.
npm ERR! This is most likely a problem with the electron-quick-start package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! electron main.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs electron-quick-start
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls electron-quick-start
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! D:\projects\electron-quick-start-master\electron-quick-start-master\npm-debug.log

i got this today, fresh clone

I got this last week, my solution is:

install electron global with command: npm install electron -g
2.cd my electron-quick-start direction to install application: npm install
start application:  npm start

Got the error pasted below while starting the quick-start app on Ubuntu 14.04:
><EMAIL_ADDRESS>start /home/talha/git/electron-quick-start
> electron .

sh: 1: electron: not found
npm ERR! weird error 127
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! not ok code 0

@talhakabakus

npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

Did you try upgrading your node version?

@MarshallOfSound Just installed the dependencies including nodejs; the version of nodejs is v0.10.25.

the version of nodejs is v0.10.25.

That version is very old, (as that log indicates).  Installing node.js from the system sources on Ubuntu fetches a really out of date version.  You want at least v4.x and probably v6.x.

@MarshallOfSound  just upgraded nodejs to v6.9.2, still getting error while starting the app:
><EMAIL_ADDRESS>start /home/talha/git/electron-quick-start
> electron .

sh: 1: electron: not found

npm ERR! Linux 4.4.0-53-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v6.9.2
npm ERR! npm  v3.10.9
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>start: `electron .`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'electron .'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the electron-quick-start package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     electron .
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs electron-quick-start
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls electron-quick-start
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR!     /home/talha/git/electron-quick-start/npm-debug.log

@talhakabakus Now that you have upgraded node versions you probably want to wipe out your node_modules directory and re-run the install.

Thanks @MarshallOfSound for all your help, now it works as it is expected.

I got this last week, my solution is:

install electron global with command: npm install electron -g
cd my electron-quick-start direction to install application: npm install
start application:  npm start

This worked for me as well.  Wtf is wrong with this company?

@Rademenes16 no need to be so toxic


Add official support for Buster

Make the script buster-aware.

Looks Good To me...
Merging into test.


PublishSymbols Task: Adding artifact record for artifact services symbol

@arunkm,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

ok makes sense. you will want to set the minAgentVersion demand in the task.json when the command is added to the agent and agent is released (task is still marked preview, right?)

Yes, the task is still marked preview.
What is the minimum agent version I can set ?

depends on when the command is added to the agent. its not added yet


Updating Kafta project to remove gradle

This PR removes the print_gradle_install function in dockerfile_function.sh and removes the gradle tag from Kafta project.
Part of #3510
Signed-off-by: Abeer Waheed<EMAIL_ADDRESS>

There should be some code which are calling the function print_gradle_install in the same file, which should be removed too.
Also please do a rebase to resolve the conflicts.


Remove dawn integration

The dawn integration is only present in the legacy backends which are going to be removed. dawn will also need to be removed as an extra dependency, and the results involving the integration also removed.

That should straight forward and can be done anytime. If someone picks this, please assign yourself that we don't duplicate the work.


CacheKeyResolver fromFieldArguments does not work

I have a cachekeyresolver that looks like:
class MyCacheKeyResolver : CacheKeyResolver() {
    override fun fromFieldArguments(field: ResponseField, variables: Operation.Variables): CacheKey {
        return if (field.arguments().containsKey("searchPhrase")) {
            if ((variables as? SearchQuery.Variables) != null) {
                val typeNameAndIDKey = field.fieldName() + "." + variables.filters().value?.nodeTypes() +
                        "." + variables.searchPhrase()?.value
                Log.d("ApolloCache", "cache_key: " + typeNameAndIDKey)
                CacheKey.from(typeNameAndIDKey)
            } else {
                CacheKey.NO_KEY
            }
        } else {
            CacheKey.NO_KEY
        }
    }

    override fun fromFieldRecordSet(field: ResponseField, recordSet: MutableMap<String, Any>): CacheKey {
        return if (recordSet.containsKey("id")) {
            val typeNameAndIDKey = recordSet["__typename"].toString() + "." + recordSet["id"]
            Log.d("ApolloCache", "cache_key: " + typeNameAndIDKey)
            CacheKey.from(typeNameAndIDKey)
        } else {
            CacheKey.NO_KEY
        }
    }
}

from fieldRecordSet it works perfectly, but the arguments one does not, it returns the proper key, but the response is still fetched from network and not from the cache

Are you sure that the key is returned by fromFieldArguments  returns correct cache key? As well could you pls set logger (com.apollographql.apollo.ApolloClient.Builder#logger) maybe you will find smth interesting there?

What do you mean correct cache key? it returns the key that I compose there every time.
And the logger only says that the key was not found in the cache:
"""
02-15 02:08:00.835 24204-24283/com.package.name I/System.out: Failed to read cache response Cache MISS: failed to find record in cache by reference
02-15 02:09:30.120 24204-24283/com.package.name I/System.out: Cache MISS for operation com.package.name.SearchQuery@7596ae0
"""

My concern is that the key that generated internally doesn't match with  your logic in fromFieldArguments. Could you please show the SearchQuery.graphql

I did try with CacheKey.NO_KEY, had no luck,
This is the query
'''
query SearchQuery($filters: Filters, $count: Int, $curs: Cursor, $searchPhrase: String) {
nodes(filters: $filters, first: $count, after: $curs, searchPhrase: $searchPhrase) {
totalCount
pageInfo {
...PageInfoFragment
}
edges {
cursor
node {
id
...EpisodeListFragment
...MovieListFragment
...ShowListFragment
}
}
}
}
'''
I thought that the cachekeyresolver's purpose was for me to set my own logic for how the key is composed and what it contains. What kind of key does it generate internally?

CacheKeyResolver#fromFieldRecordSet is used mostly when you have global id or like in your example, recordSet["__typename"].toString() + "." + recordSet["id"] that's absolutely correct.
CacheKeyResolver#fromFieldArguments is used to resolve root of the query, like for instance you fetch list of nodes and you have another query to fetch one node by id. Then you can provide different root for the query, so by default the root will be node(1234) but you want to have 1234.
In your case you shouldn't use CacheKeyResolver#fromFieldArguments and just return CacheKey.NO_KEY.
When this query is cached the key for the root will be quite complicated, like nodes(filters:SMTH, first:20,....).  Here is the code: https://github.com/apollographql/apollo-android/blob/master/apollo-api/src/main/java/com/apollographql/apollo/api/ResponseField.java#L240
Could you elaborate on why CacheKey.NO_KEY doesn't work for you?

It simply doesn't find the value: nodes
02-15 10:20:26.663 20281-20339/com.package.name I/System.out: Failed to read cache response Missing value: nodes
02-15 10:20:26.663 20281-20339/com.package.name I/System.out: Cache MISS for operation com.ownzones.androidnet.SearchQuery@fbf042a

it seems the call is made twice sometimes, when it is made once it doesn't return from cache, but when it is called twice once its from cache and once not. But the log i place at the start of the call appears only once, which indicates to be something internal from apollo?
02-15 10:39:12.191 21471-21471/com.package.name D/ApolloCache: StartCall
02-15 10:39:12.195 21471-21555/com.package.name D/ApolloCache: Failed to read cache response Missing value: nodes
02-15 10:39:12.196 21471-21555/com.package.name D/ApolloCache: Cache MISS for operation com.package.name.SearchQuery@3bdca8b
02-15 10:39:12.454 21471-21539/com.package.name D/ApolloCache: Response from cache: false
02-15 10:39:12.464 21471-21533/com.package.name D/ApolloCache: Cache HIT for operation com.package.name.SearchQuery@3bdca8b
02-15 10:39:12.464 21471-21533/com.package.name D/ApolloCache: Response from cache: true
02-15 10:39:12.508 21471-21471/com.package.name D/ApolloCache: onNext
02-15 10:39:12.508 21471-21471/com.package.name D/ApolloCache: onNext

Are you sure that the response was cached previously?
And arguments filters: $filters, first: $count, after: $curs, searchPhrase: $searchPhras were not changed for the query that you expect to be fetched from cache?
I think one take away from this conversation is that we need have the way to dump the cache, at least the mem cache. It will be easier to handle such issues

well I don't know how to check if it was cached, but if i make the same query twice in a row the second time should be from cache right? And yes nothing changes in the query, I thought the same and double and triple checked it, all the arguments are constructed the same with Input.fromNullable()
Also I agree that would be a useful feature to have. Till then i'm stuck on this issue

Is there any way I can try your query? Is GraphQL endpoint public exposed?

I've prepared PR https://github.com/apollographql/apollo-android/pull/825 to be able dump the content of normalized cache.

No unfortunately it is not public, so I can't give you access. I will wait till a snapshot of is up with that PR, and see what it turns out in it

This issue is still there


My PR was merged 2 days ago, yet the docs are still not updated

https://github.com/MicrosoftDocs/windows-itpro-docs/pull/4445
How long it takes from merging the changes till user sees the updated content?
Thanks!

@officedocsbot assign @jvsam

Please be patient. 2 days is not much waiting time
for your merged PR to migrate to
https://docs.microsoft.com/en-us/windows/client-management/mdm/assignedaccess-csp .
Just to give you an idea, I will mention that I have seen merged pull requests take up to a week
to migrate to the docs.microsoft.com site, which suggests that the wait time can be arbitrary.
Please also consider that vacation season could also play a role in the delay.
My recommendation is not to worry, unless you are part of a Microsoft team
needing the changes to be made public before you can post other changes.
As a rule of thumb, you don't need to make inquiries before a week has passed.

Hi @chandde I can now see the updates displayed on the following content pages:
https://docs.microsoft.com/windows/client-management/mdm/assignedaccess-csp
https://docs.microsoft.com/windows/configuration/kiosk-xml
https://docs.microsoft.com/windows/configuration/lock-down-windows-10-to-specific-apps
We will now close this issue. Thank you.

@officedocsbot close


'require' cannot load such file -- pry

There's an "require 'pry'" in the interactive_setup.rb
It's causing issues.

Thanks! Fixed in 7ba1bcb47d3759014460bd5b6f4dd83434d854bf, included in 0.8.2.


Suggestion: ability to turn on/off debug logging

Hi. Gulp-debug is one of the coolest things I've ever seen. I am absolutely in love. Thank you for building this.
One small suggestion. Could we provide the ability to turn on and off the debug logging with a flag like:
gulp -debug-off [task-name]

Nah, this task isn't meant to be used permanently, but rather for debugging. You can use gulp-if and check the cli flag yourself if you want this.


Minor issue: 1/1 in notification window

Minor issue: when Terra displays a single notification, it tells me that it's 1/1. This chews up real-estate that's better spent displaying the actual message.

Given that we have updated our notifications to fly-in banners, I believe this is resolved. @seanhorgan feel free to reopen if you still see this behavior.


Ghes no ssl verify

[x] Did you write/update appropriate tests
[ ] Release notes updated (if appropriate)
[ ] Appropriate logging output
[ ] Issue linked
[ ] Docs updated (or issue created)

Issue was  that when nossl was true it was not applied when querying repo data from GHES and that failed to validated SSL connection if self-signed certificate was used

Hi @madkoo thanks for finding (and fixing) this bug!
We have e2e integration tests that test GHES, but our test GHES server has SSL configured so we never caught this.
Before we can accept this PR we'll need a few things:

Unit test(s) for the change
We'll need a bug issue to track the problem
All the PR build/static analysis checks to pass

Let us know if you want to tackle these steps, if not I can have somebody on our team pick this up and finish off the work to get it merged in.

Hi @dylan-smith Will do the changes as requested. :)

This PR is related to issue #474

Sure, will do it right away :)


Can do, for the persistent damage links too?

Can do, for the persistent damage links too?

Don’t think they’re needed, as it’s automatically included in the damage roll.

Done!


After clusterrole/role is created, yaml shows resource item is uppercase

Rancher Server Setup

Rancher version: v2.6.5
Installation option (Docker install/Helm Chart): docker install

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s
Node Setup: 1 node
Version: v1.23.6+k3s1

Proxy/Cert Details:  self-signed

Information about the Cluster

Kubernetes version: v1.23.7+rke2r2
Cluster Type (Local/Downstream): Local

User Information

What is the role of the user logged in? Admin

Describe the bug
After clusterrole/role is created, yaml shows that resource item is uppercase, it should be lowercase.
eg:  Node is selected, yaml shows Node too
To Reproduce

create clusterrole/role page.
select any verbs and any resources, then click save.
click edit yaml.

Result
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  creationTimestamp: "2022-06-23T02:31:22Z"
  managedFields:
  - apiVersion: rbac.authorization.k8s.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:rules: {}
    manager: rancher
    operation: Update
    time: "2022-06-23T02:31:22Z"
  name: test
  resourceVersion: "2423173"
  uid: c53fa817-f06c-4670-bc07-395188ccd2fb
rules:
- apiGroups:
  - ""
  resources:
  - Node
  verbs:
  - list
  - update

Expected Result
resources item must comply with k8s rbac rules, eg: after Node is selected, yaml shows and requests to rancher is nodes.
Screenshots

Additional context

Possible duplicate of https://github.com/rancher/dashboard/issues/6090

Yes, it is a duplicate. Cody fixed it in his PR https://github.com/rancher/dashboard/pull/6163. The role creation forms add all resources in lowercase now.


v0.0.2

Changes

https://github.com/lifeomic/chromicons/pull/6

Just a heads up - I noticed the current gh actions prematurely published to npm, so when this PR merges they may fail.  PR to hopefully fix it coming up soon!


python311Packages.rich-rst: 1.3.0 -> 1.3.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.rich-rst is: A beautiful reStructuredText renderer for rich
meta.homepage for python311Packages.rich-rst is: https://github.com/wasi-master/rich-rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.1 with grep in /nix/store/hj36gkh3clmb302lsjf87i94y5h05s3a-python3.11-rich-rst-1.3.1
found 1.3.1 in filename of file in /nix/store/hj36gkh3clmb302lsjf87i94y5h05s3a-python3.11-rich-rst-1.3.1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.rich-rst
python312Packages.rich-rst
rich-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hj36gkh3clmb302lsjf87i94y5h05s3a-python3.11-rich-rst-1.3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.rich-rst https://github.com/r-ryantm/nixpkgs/archive/dc88b85084fda624276871fc76b96fc12f19eeb0.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/dc88b85084fda624276871fc76b96fc12f19eeb0#python311Packages.rich-rst

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hj36gkh3clmb302lsjf87i94y5h05s3a-python3.11-rich-rst-1.3.1
ls -la /nix/store/hj36gkh3clmb302lsjf87i94y5h05s3a-python3.11-rich-rst-1.3.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages failed to build:

rich-cli
rich-cli.dist

4 packages built:

python311Packages.rich-rst
python311Packages.rich-rst.dist
python312Packages.rich-rst
python312Packages.rich-rst.dist

Maintainer pings
cc @joelkoen for testing.

Result of nixpkgs-review pr 309457 run on x86_64-linux 1

2 packages failed to build:

rich-cli
rich-cli.dist

4 packages built:

python311Packages.rich-rst
python311Packages.rich-rst.dist
python312Packages.rich-rst
python312Packages.rich-rst.dist

Result of nixpkgs-review pr 309457 run on x86_64-linux 1

6 packages built:

python311Packages.rich-rst
python311Packages.rich-rst.dist
python312Packages.rich-rst
python312Packages.rich-rst.dist
rich-cli
rich-cli.dist


More description needed in blueprints

I don't mind succinct documentation but I can't find my way out of the box here:

what does /path/to/<name> refer to? I assumed it meant the route, component, etc. but when trying this it complained saying that the only valid names were the breakpoints. That's forcing me to think about things differently than I expected.
Are the templates only for the full page? I would have thought you could have templates on a per component basis.

Templates do work for components or routes, but the generators that are specific to component or route are unfinished (see #12 ).
This ember g layout works with either routes or components, the path/to part should be the path to the component or route including the name of the component or route, while /name should be the name of a breakpoint.  You can also convert existing templates to a layout using move:layoutormvl` if operating off of develop or the about to be released patch, I'll be adding documentation on this shortly.
ember move:layout <type> <name> [-b <breakpoint>] [-v]

example
ember mvl route foo/bar -b "desktop"

ember mvl component foo/bar -b "mobile"

If you define defaultBreakpoint in config/flexi.js it will be used for -b if none is provided
-v is verbose mode, will show you the paths being resolved
If you are moving a route template instead of component, or a pod component that's not within the components/ directory, you can do this (edited)
ember mvl foo/bar -b "desktop"

mvl is a shorthand alias for move:layout

Thanks Chris.

I have copied this documentation into the readme.io docs, which will be released as part of the 2.0 release, so I am closing this.


Gen feat build file fix

When a build file dependency change is detected, add an additional check to only call generateFeatures if there are class files to generate for.
Also include a minor improvement to the clean up logic in the dev integration tests.
See https://github.com/OpenLiberty/ci.maven/pull/1409

Updated the logic to detect dependency changes in the build.gradle, and run generateFeatures --optimize=true. If generateFeatures is successful, run libertyCreate and installFeature as well.
Tried to add a new integration test to cover this case, but altering the build.gradle through the integration tests results in the following error
Could not parse build.gradle org.gradle.api.ProjectConfigurationException: A problem occurred configuring root project 'basic-dev-project1643909649043'.

Opened a separate issue: https://github.com/OpenLiberty/ci.gradle/issues/708


Native Notebooks - Stop execution (cell and kernel level) don't work

Run any long running cell
Try to stop the execution (either at the cell level or notebook kernel level)

Nothing happens, have to close and reopen the notebook

@claudiaregio please could you provide a sample code to replicate this issue.
If possible, try to provide a simple sample so we can test/setup easily at our end.
Also, please confirm this is not an issue when you try the same in classic Jupyter (browser).

@claudiaregio please could you provide a sample code to replicate this issue.
If possible, try to provide a simple sample so we can test/setup easily at our end.
Also, please confirm this is not an issue when you try the same in classic Jupyter (browser).

This is expected (as evidenced here:)
https://github.com/ipython/ipython/issues/3400
However we can make native notebooks automatically restart if they take too long like we do for the old editor.
I'll also add more logging to make sure we're interrupting if this comes up again.

This is expected (as evidenced here:)
https://github.com/ipython/ipython/issues/3400
However we can make native notebooks automatically restart if they take too long like we do for the old editor.
I'll also add more logging to make sure we're interrupting if this comes up again.

Looks like this belongs in validate.

Looks like this belongs in validate.

I couldn't replicate the original issue, hence leaving for someone else to validate.

I couldn't replicate the original issue, hence leaving for someone else to validate.

To repro you have to run with debug bits and uninstall the json rpc stuff. Then the extra layer for interrupt doesn't work.

To repro you have to run with debug bits and uninstall the json rpc stuff. Then the extra layer for interrupt doesn't work.

I have had all diary study participants mention this same behavior so far and had it happen again during a wrap up interview. Can pull the footage to share on Monday.

I have had all diary study participants mention this same behavior so far and had it happen again during a wrap up interview. Can pull the footage to share on Monday.

This is still a problem at least on Windows

This is still a problem at least on Windows

Joyce, it looks you just validated it. That's the intended behavior when the interrrupt fails. Jupyter is not guaranteed to interrupt so we ask for a restart if it doesn't work.

Joyce, it looks you just validated it. That's the intended behavior when the interrrupt fails. Jupyter is not guaranteed to interrupt so we ask for a restart if it doesn't work.

For me this always happens with a sleep if you don't have the json rpc library installed (dev bits). But it can happen for other code as well. See the ipython bug:
ipython/ipython#3400

For me this always happens with a sleep if you don't have the json rpc library installed (dev bits). But it can happen for other code as well. See the ipython bug:
ipython/ipython#3400

Oh, good. Closing as validated then :)

Oh, good. Closing as validated then :)


[FLOC-2271] Backport ApplicationNodeDeployer volume size-related calculations fixes

Fixes https://clusterhq.atlassian.net/browse/FLOC-2271
Backport of #1598

Green as it gets I suppose.


Addition - Narrative info cache and users' display names

I'm going to close this PR as the cache stuff should go into develop. I just wound up adapting stuff from here rather than using the whole thing.


utility.py: add TDX_CMD_GET_QUOTE_V1_5

Add TDX definition for ioctl command TDX_CMD_GET_QUOTE_V1_5.
Also adjust the format of the related comments.

The definition of TDX_CMD_GET_QUOTE for TDX 1.5 is:
#define TDX_CMD_GET_QUOTE		_IOR('T', 4, struct tdx_quote_req)
And the struct tdx_quote_req is defined as:
`
/* struct tdx_quote_req: Request struct for TDX_CMD_GET_QUOTE IOCTL.

@buf: Address of user buffer in the format of struct tdx_quote_buf.
Upon successful completion of IOCTL, output is copied back to
the same buffer (in struct tdx_quote_buf.data).
@len: Length of the Quote buffer.
*/
struct tdx_quote_req {
__u64 buf;
__u64 len;
};
`

So "sizeof(struct tdx_quote_req)" is "0b00010000".

I will cleanup utility.py, could we move these type of definitions to the specific class like
https://github.com/cc-api/cc-trusted-api/blob/a9181eba6e5e726466f778bb34015dad3e9fd8b3/vmsdk/python/cctrusted/cvm.py#L171
?

Updated as suggestions. Please review the latest version. Thanks!


[BUG] when loading the server....

I had this issue. Fixed it by updating libs of an outdated plugin.


Ratings: allow user to deselect all ratings for an app within a specific category

e.g. remove all 'Product' ratings


[bug] Tauri 1.7.x breaks Command stdout/stderr

Describe the bug
Using Tauri v1.7.1 (and 1.7.0), my Command.execute() call does not return any events. Consider this example:
async function ytDlpCommand(args) {
	let cmd = new Command('yt-dlp', args);

	cmd.on('error', error => console.error(`command error: "${error}"`));
	cmd.on('close', line => console.log(`command close: "${line}"`));
	cmd.stdout.on('data', line => console.log(`command stdout: "${line}"`));
	cmd.stderr.on('data', line => console.log(`command stderr: "${line}"`));

	let output = await cmd.execute();
	return output;
}

which is basically the example code from the docs. I get no console output from any of the events. Did the syntax for events change? I couldn't find anything regarding api changes, only "speed up" changes in the v1.7.0 changelog.
Downgrading to Tauri v1.6.8, but keeping @tauri-apps/api at v1.6.0, I run into the error described in #9786. Downgrading @tauri-apps/api to v1.5.6 restores the functionality. This configuration works as I would expect:
[-] Packages
    - tauri [RUST]: 1.6.8
    - tauri-build [RUST]: 1.5.3
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.5.6 (outdated, latest: 1.6.0)
    - @tauri-apps/cli [NPM]: 1.4.0 (outdated, latest: 1.6.0)

Reproduction
No response
Expected behavior
See function above, basically any Command.execute() call with event listeners should reproduce this.
Full tauri info output
[✔] Environment
    - OS: Mac OS 13.5.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.72.0 (5680fa18f 2023-08-23)
    ✔ Cargo: 1.72.0 (103a7ff2e 2023-08-15)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 21.1.0
    - npm: 10.2.0

[-] Packages
    - tauri [RUST]: 1.7.1
    - tauri-build [RUST]: 1.5.3
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.4.0 (outdated, latest: 1.6.0)

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../build
    - devPath: http://localhost:5173/
    - framework: Svelte
    - bundler: Vite

Stack trace
No response
Additional context
No response

Looking at the example, you're using .execute() which will wait for the process to finish, collect all of its output and then returns it at one go. You're looking for .spawn() instead, to receive data as it arrives.


optimize FidelityQuantumKernel parameterization

Summary
This PR optimizes the way indices, right_parameters and left_parameters are created in _get_symmetric_parameterization and _get_parameterization of the FidelityQuantumKernel class.
Details and comments
The previous version used a heavy amount of dynamic memory allocation which resulted in a very long runtime. This new version runs way faster for bigger instances by not using dynamic memory allocation. I didn't add any additional tests, since this doesn't introduce any new functionality.
I'm happy to incorporate comments and hope this can be merged soon 😄

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 92.66%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
1843

Relevant Lines:
1989

💛  - Coveralls

Can you please measure how faster the implementation becomes with this PR?

This is the runtime of the respective functions in seconds as benchmarked with timeit with x_vec.shape==y_vec.shape==(100,2) and evaluate_duplicates=="all" and 100 executions:
get_parameterization            Old     11.828130300000339
get_parameterization            New     0.4398030000011204
get_symmetric_parameterization  Old     4.378354100001161
get_symmetric_parameterization  New     0.23957780000091589

Thanks, this is interesting. Can you please additionally measure an overall impact on qk.evaluate(), especially if there are more than 5 features/qubits?


Artifacts on recorded image

When I use "Make transparent: Use original image", weird artifacts apper on the recorded image.
The project files and the view used to render is attached.
effect.zip
And here is the result (notice the second sword with black color)

Update: It does not happen on my other pc, maybe a video card problem causes this.


Shortlink automation

What's your idea?
Similar to #54, we can create a workflow that creates a new pull request updating the shortlink data used by the website. Currently, if a user lands on https://acmcsuf.com/ with a pathname matching any of the names of the predefined shortlinks (in /lib/constants/links.ts), it is redirected to the assigned destination. For example, https://acmcsuf.com/discord redirects to the Discord server’s invite link.
This means each time we want to add a new shortlink or remove an old one from the website, we must manually create a PR for this change. However, this can be easily automated via issue form.

Closing with the intention to immediately reopen. More info: #776.

Status: blocked. Waiting on a stable version of codemod.

Resolved: https://oss.acmcsuf.com/shorter
More information: https://acmcsuf.com/shorter-handbook


refactor: improve log with the stream type omit space

Description
Remove the space in the stream type. This will result in a log that appears as follows:
time=2023-04-19T12:01:16.433+08:00 level=INFO msg="use credential" component=StreamFunction client_id=CwIH4_0rpO_faPDJy6lUB client_name=Noise credential_name=none

@woorui This really help a lot when reading logs in my debug life ...


requestTechnology Promise never completes

I just tried to implement the example for reading and writing ndef messages.
However await NfcManager.requestTechnology(NfcTech.Ndef); never completes.
It happens when reading and writing
I tried other technologies such as Nfca etc.
2023-08-29 17:44:56.976 26406-26781 ReactNativeNfcManager   com.unuclient                        D  start
2023-08-29 17:44:56.977 26406-26781 ReactNativeNfcManager   com.unuclient                        D  parseIntent Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.unuclient/.MainActivity }
2023-08-29 17:44:56.977 26406-26781 ReactNativeNfcManager   com.unuclient                        D  action android.intent.action.MAIN
2023-08-29 17:44:56.978 26406-26781 ReactNativeNfcManager   com.unuclient                        D  isSessionAvailable: false
2023-08-29 17:44:57.015 26406-26781 ReactNativeNfcManager   com.unuclient                        D  registerTagEvent

This is what Logcat from Android Studio says when trying to read or write messages.
Physical Device running Android 10
Tested also on a Samsung Galaxy S4 using LineageOS, same issue
<uses-permission android:name="android.permission.NFC" /> is added to the AndroidManifest.xml
I already tried to build the apk but the error occurs there too.
Thanks for help in advance, have a great day 😃

The request waits until it reads the other NFC tag. When it reads the NFC tag, it will resolve the promise. Can you provide more information?

Thanks for your response. However, currently i am not working on the project anymore and don't have the opportunity to start it again. Maybe I just wasn't holding them close enough to each other.
Have a great day!


Release 1.41.0

This issue is to track the 1.41.0 release.
I have successfully tested upgrading from 1.40.0 stable to the master development branch.
Next up is to release the next version with CHANGELOG release notes.

I know I am little bit late but it would be cool if we can add #637 and #664 into the release :) But we could also release in the next days again!:)


Move under MCP

Hi @aldeed, since collection2 is already under @Meteor-Community-Packages management would it be possible to do the same for this package and meteor-schema-index, so that they can all be updated for Meteor 3? Thank you!

Done

@aldeed thank you!


esy: "expected only version or source but both were provided"

When I run esy in the project directory as instructed, it returns the following error:
error: expected only version or source but both were provided
  reading package metadata from link-dev:./package.json
  loading root package metadata
esy: exiting due to errors above

It seems to work if all but the first "version" properties are deleted.

This is quite unexpected, since a commit targeting at fixing the dependencies (in particular, the duplicated version properties) should have been in place exactly around last week.
Would it be possible if you could post the exact commit hash you are trying to build, so we could look into it and check as well?

Closing this thread due to inactivity.
Summary of the response: it is likely that this issue is due to trying to build a different master branch, which is no longer maintained and should be archived. The current master branch was tested again, which compiled successfully in its current state.


Add pre-made validators.

Names are subject to change:

[ ] MatchesRegex (Pre/post; strings) - Ensures the string matches the given regex.
[ ] OneOf (post; any) -> Ensures that the value can be found within a predefined list.
[ ] MaxSize (post; any[]) -> Ensures that the array doesn't go beyond the given size.
[ ] InRange (post; numeric) -> Ensures that the number is within a certain range.
[ ] Contains (post; any[]) -> Ensures that the array contains a certain value.

Frankly speaking I see no point doing this (at least right now).

I don't care about this anymore, the user can make their own.


Meta: Add script for build+running Jakt programs

I thought the two commands to get a program built all the way was
somewhat unwieldy, so I added a little bash script to do it.
Much like Serenity, it's in a meta folder off the root. If there's anything that's super wrong please let me know, my bash scripting is rustier than I'd like to admit.

Since #299 has been merged, I think we can leverage that functionality instead of also mirroring it in this shell script

Since #299 has been merged, I think we can leverage that functionality instead of also mirroring it in this shell script

Agreed.


Improve code readability

[x] Add Doc strings
[x] Split code into functions
[x] Split code into modules
[x] Any other changes to enhance readability

[x]  Add Doc strings

Fixed in https://github.com/harry-7/P2P-Filesharing/commit/09731e1d21fea95778b42f59722c8c93fa26ead2

[x] Split code into functions
[x] Split code into modules
[x] Any other changes to enhance readability

Fixed in https://github.com/harry-7/P2P-Filesharing/commit/8fd932f937b3a4e37681d52ee25672d7d7da5455


UST liquidity pool

<!--
  Is this a bug report?
  If so, go back and select the "Bug report" option or your issue WILL be closed.
--!>
attempted to add small liquidity to new UST/RUNE pool.   UST tokens left my wallet but RUNE didn't.   UST tokens have disappeared.   Any support to retrieve this would be appreciated

attempted to add small liquidity to new UST/RUNE pool. UST tokens left my wallet but RUNE didn't. UST tokens have disappeared. Any support to retrieve this would be appreciated

https://finder.terra.money/mainnet/tx/DF4546E802854BCE98E12096CFE5D383BAA63F7ECECDC866A25A118BA798ECCB
TX for UST

ASGARDEX does not support UST (yet).


🎨 Home-Page-Educational-Section-Component

Description
Created the Home-Page-Educational-Section-Component
Fixes # (issue)  #5
Type of change.

[x] New feature (non-breaking change which adds functionality)

Screenshot (optional)
Laptop

Tablet

Mobile Phone

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

This is good work.But closing this pr as the issue is closed already


Android Basics: Shared ViewModel

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-shared-viewmodel?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-3-pathway-4%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-shared-viewmodel#7
In which task and step of the codelab can this issue be found?
Step: Format price with LiveData transformation 1.
Describe the problem
" In OrderViewModel class, change the backing property type to LiveData instead of LiveData.
private val _price = MutableLiveData()
val price: LiveData
"
Is the 'price' a backing property? As far as i know, the '_price' is a backing property, and 'price' is a regular one? Am I mistaken?

'price' is a backing property declared to access value of private property '_price'.


Change the HUD background color to clear

Now we have three styles JGProgressHUDStyleExtraLight, JGProgressHUDStyleLight and JGProgressHUDStyleDark.
How can I create a HUD with clear background color?

@expkzb , I am looking for the exact thing for my app too. Have you ever find any workaround for this? Also, are you able to clear the background color of HUD?

Please check attachment.

See #18

@JonasGessner , why you're not merging that PR?

Read the discussion on the PR.