Level 4 - Doubt regarding KeyableMap implementation

Whats the difference between,
class KeyableMap implements Keyable {
...
}
and
class KeyableMap implements Keyable {
...
} ?
Why must KeyableMap implement Keyable and can't just be an independent class?
Why must V extend Keyable?
Thanks!

I am not sure if others can also not see it but the generic label is missing from my POV so I will just copy paste here the actual lines.
Whats the difference between,
class KeyableMap implements Keyable {
...
}
and
class KeyableMap implements Keyable {
...
} ?

Let's assume that V isn't a Keyable. Then, for the puts(V item) method, how would you implement it?
Keyable put(V item) {
    String key = item.getKey(); // <----- can't do this btw
    // call put(key, item)
    return this;
}

The main reasoning why V has the extends Keyable bounds is so that we have sufficient proof for the compiler to know that the .getKey() method exists on V - since it 'extends' Keyable. Otherwise, without it, the compiler can make no assumptions and will consider V to be of type Object (since this is the 'lowest bound' that all classes have).
(P.S. to put code in Github markdown, use the tilde character: ` <code> ` )

As for why KeyableMap itself must implement Keyable - usually, it's not a must. However, when you implement toString you will see that you require this.getKey().

As for why KeyableMap must implement Keyable
We are expected to do something like this:
class Module extends KeyableMap<Assessment>
class Student extends KeyableMap<Module>
Note that V in KeyableMap must extend from Keyable. So if KeyableMap does not implement Keyable,
class Student extends KeyableMap<Module> will give you a compile error because Module class does not implement/extend Keyable (since Module only extends Keyable<Assessment> and does not implement Keyable).

Ok thanks guys for the clear explanations!


Print Hotkey gets consumed by InnovatorAdmin

I use the "Print" Key to start greenshot to capture the screen with active context menus etc.
The latest release seems to consume this key press event. I have to give focus to some othe application to make it work again, but this makes any context menu etc. disappear ;-)
Maybe you could use CTRL+P instead of the Print key to print reports etc.?

I don't intentionally use that key for anything and am able to get screen captures using that key on my computer.  Out of curiosity, is it mapped any differently on a German keyboard?  (I wouldn't expect so, just curious.)


cpu - cpu version of gpu_specter should be 'plug and play' in current specter and desispec

Our version of gpu_specter (even in it's cpu form) should have the same connectivity as the current cpu versions of desisim and specter and be fully interchangeable with the cpu version.
This means that when Issues #4 #5 #6 have been addressed, it can be used directly in desi's standard pipeline. This would allow it to be used and tested in both a single frame extraction (https://github.com/desihub/desispec/blob/master/py/desispec/scripts/extract.py) and the full, multi-exposure desibenchmark suite (https://github.com/sbailey/desibenchmark).

Should have all the functionality that is in desispec/desi_extract_spectra

Note also that we'll need to make sure that Daniel's eigh batch contribution has been merged into master and we can point to a CuPy tag

Closing in the spirit of Closember.


Multi-Part file upload support for Post keyword

@bulkan
How to upload image file  along with data using post request

@swapnilpatne
can you please post a working sample/example.

Post Request With File
    [Tags]  post
    Create Session  httpbin  http://httpbin.org

    ${file_data}  Get Binary File  ${CURDIR}${/}data.json
    ${files}  Create Dictionary  file  ${file_data}
    ${resp}  Post  httpbin  /post  files=${files}

    ${jsondata}=  To Json  ${resp.content}
    ${file}  To Json  ${jsondata['files']['file']}
    Dictionary Should Contain Key  ${file}  one
    Dictionary Should Contain Key ${file} two

want to test file uload scenario by passing no file. How can a pass no file here .
I tries null and "" but getting pass response . I want to make my test fail . Please help me out !
Thanks

try ${EMPTY} It's a reserved keyword in RF


Remove new templates not referenced elsewhere

These new templates were merged as part of a backport effort, and never existed in the original Coopr 0.9.9 release. As such, I am removing them from this branch.

:+1: lgtm


Allow passing Channel.Event to off

This allows developers to call
channel.off(Channel.Event.REPLY, ref)

instead of
channel.off(Channel.Event.REPLY.value, ref)
// or
channel.off("phx_reply", ref)

Codecov Report

Merging #75 into master will decrease coverage by 0.34%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master      #75      +/-   ##
============================================
- Coverage     91.38%   91.04%   -0.35%
  Complexity      178      178
============================================
  Files             9        9
  Lines           534      536       +2
  Branches         71       71
============================================
  Hits            488      488
- Misses           12       14       +2
  Partials         34       34

Impacted Files
Coverage Δ
Complexity Δ

src/main/kotlin/org/phoenixframework/Channel.kt
93.82% <0%> (-1.18%)
53 <0> (ø)

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 f879632...7f8a664. Read the comment docs.


Discovery: Support OLM and operators via AppCatalog

Support OLM and operators via AppCatalog
Kubeapps has something as a beta feature
https://github.com/vmware-tanzu/kubeapps/blob/f41f0dd53ab1b4988342a4036c21659d05375397/docs/tutorials/operators.md
evaluate the idea, if it makes sense to adopt it

this is a very vendor specific component that does not add any value for anyone outside the vendor ecosystem so we are going to close this


parse error near `\n'

after install，i use clipper clip -u ，appear ：parse error near `\n'
help

Can you please share the exact command you used? Otherwise it is hard to reproduce your error.

clipper clip -u https://pinchlime.com/blog/2023-review/
like this

Thank you for me it worked. What is the error you see?
output.md

zsh: parse error near `\n'

myname@android-dhcp9 ~ % clipper clip -u https://pinchlime.com/blog/2023-review/
zsh: parse error near `\n'
myname@android-dhcp9 ~ %

Sorry, I cannot reproduce your error. What os and node version are you using?

Node.js v16.6.0.
macOS14.2.1 (23C71)
thank u
i also could not understand


hedera_format_amount is not safe

hedera_format_amount crashes (when compiling with -fsanitize=address) with the following inputs:
hedera_format_amount(-1u, 30);
hedera_format_amount(-1u, 31);
hedera_format_amount(0, 0);

The first two produce an out-of-bounds write of \x30 past the end of buf while the last one reads one byte before buf.
As this function is called with parameters coming from externally-controlled parameters transaction description (e.g. here ), it could lead to security problems.
Also, it seems the expected decimal value is parsed as an unsigned int whereas it is cast into an unsigned char when calling hedera_format_amount in the portion of code linked above.

Also, it seems the expected decimal value

Hedera supports setting decimals up to uint32_t but the largest feasible decimal amount is probably 16 as the total balance is only a 64-bit number in Hedera. I'm not sure the best idea here, maybe we reject accepting the transaction if a decimal value larger than say 20 is passed?

I'll get the safety issues fixed today.


chore: Copy signing keys to /etc/ only

Supplements main PR: https://github.com/blue-build/modules/pull/375
Need to test if it works properly

The changes look good, but it seems like the signing module is causing failures. I think that will have to be updated before this can be merged in.

Hmm, error implies that keys are not copied to /etc/pki/containers/.
Maybe that's only in Ublue image. I would like to know if that issue is gone in vanilla Fedora based images.

It would be good to use the signing module from my PR temporarily to test this, then revert it back.
Is that good?

It would be good to use the signing module from my PR temporarily to test this, then revert it back. Is that good?

I confirm it works now.

It would be good to use the signing module from my PR temporarily to test this, then revert it back. Is that good?

I confirm it works now, so it can be merged.

I'm not comfortable merging this in until https://github.com/blue-build/modules/pull/375 is merged. I run my builds of the main branch and this will fail them without the module changes.

It would be good to use the signing module from my PR temporarily to test this, then revert it back. Is that good?

I confirm it works now, so it can be merged.

I'm not comfortable merging this in until blue-build/modules#375 is merged. I run my builds of the main branch and this will fail them without the module changes.

Merged


[WIP] Add incremental compiling support

Purpose
This PR adds incremental compiling support.
Todo

[ ] Add a new test module to parse examples twice to verify the functionality of SymbolResetter

Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Closing this PR, Refer: https://github.com/ballerina-platform/ballerina-lang/pull/16993#issuecomment-520701870


Update the doc about a known issue

We find a know issue about "Importing search configuration". Update the doc about it.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@SerdarSoysal PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


fix: support uint8arrays as well as buffers

Relaxes the input check to accept Uint8Arrays instead of node Buffers as this module doesn't do anything Buffer-specific.
Repeats the tests for both Buffers and Uint8Arrays.
Updates deps and removes ones that aren't used after the above refactor.

Codecov Report

Merging #2 into master will decrease coverage by 0.90%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
- Coverage   90.90%   90.00%   -0.91%
==========================================
  Files           1        1
  Lines          11       10       -1
==========================================
- Hits           10        9       -1
  Misses          1        1

Impacted Files
Coverage Δ

src/index.js
90.00% <50.00%> (-0.91%)
:arrow_down:

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 9afb0f9...4b348af. Read the comment docs.


Possible Issue With Mod clashing/World Corruption

I built my house out of blocks from chisel, after a lot of mining and such I logged off for the night & looked at my world again and it wasn't there. Figured out that it was corrupted, fixed it & now this happened when there was none of this before, & the building I made my hut out of was all out of thaumcraft blocks, not sure if this was from thaumcraft or any other mod. This has also happened with my other world today. I also noticed a bug while I was messing around with thaumcraft alone, the essentia mirror, hand mirror do not have a icon in the thaumonomicon atm.
BETA-20
Will be attaching files of the house after the corruption/fix and what was new, any help or anything is appreciated.

Mod List (If its needed):
Advanced Combat
Astral Sorcery
AutoRegLib
BabyMobs
Backpacks (The one we usually use)
Baubles
BetterBedrockGenerator (Flatbedrock)
Bibliocraft
Biomes O Plenty
Botania
Creeper Confetti
cxlibrary (Idk what this is for)
Cyclops Core (Same as above)
Dailies (Bailey's Dailies)
Decocraft (You can take it out if u want xD)
EnderCore/EnderIO
EvilCraft
extrautils2
mrcrayfish's furniture mod
Galacticraft Core/Planets
Hwyla
Inventory Pets
JEI
J-Map
Just enough resources
MicDoodleCore
More-Planets
Optifine E2
PTRLib
Quark
Refined Storage
Reliquary
Roots
SimpleGrinder
Thaumcraft
Thaumcraft JEI
TreeCHopper
Twilight Forest
Veinminer
Wawla
Worldedit

1st pic:Gesyers/Blocks were not there to begin with.
2nd pic: The hut was all made of greatwood logs as well as the weird cluster of the logs in the background.
3rd pic:  my house after the corruption

The missing icons is already known as it has to do with something in forge that changed how blocks are displayed or something along those lines. You will notice that the icons (block renders) don't show in creative properly it is just an empty inv space with a name.


How to read table from Airtable and get proper data instead of record id reference?

I was trying to read table from airtable using below cmd:
table = api.table(base_id, table_name)
But I am getting reference id from another table as reference instead of actual data in multiple columns.
Below is the example of sample data I am getting:
{'id': 'rec00mAMFjd0m0urE',
'createdTime': '2024-03-27T20:14:28.000Z',
'Country': ['recADSUI26vTsE1']
}
Instead of actually getting the country column value we are getting record id which we will have to use to join with country table to get the actual value. Is there any better way to directly get the country name?

That's the default behavior of the Airtable API. You can pass cell_format='string' to methods like Table.all() or Table.first(), and the Airtable API will return all fields in string format (which means you'd get the name of the Country record, instead of the record ID). That's not always desirable behavior, though, especially if you need to deal with dates (parsing localized versions is hard) or if you need to look up additional properties of the joined records.
What we often do in our own code is to pre-fetch all records from those "supporting tables" (like a list of countries, for example) at the start of our job, and to store those in memory for easy lookup when iterating over records from other tables. It's usually far more efficient than getting the referenced records individually at the point where you need them. In the 3.0 release (coming soon) the ORM will contain some extra helpers for memoizing those referenced models so that they're already fetched when you interact with the records which reference them. (See #369)
I'm going to close this issue because this is just how the Airtable API works, rather than a bug in the library.


Implement simple Subscription Caching mechanism using UserDefaults

Required:
Task/Issue URL:  https://app.asana.com/0/1204099484721401/1206574474409573/f
iOS PR:  https://github.com/duckduckgo/iOS/pull/2556
macOS PR:  https://github.com/duckduckgo/macos-browser/pull/2345
What kind of version bump will this require?: Minor
Description:

Implements mechanism for caching subscription info
Caches entitlements
Cleans cache on signout.
Returns cached entitlements by default (if present)
Adds a skipCache parameter to fetchEntitlements to force fetching from the service
Posts a Notification only when entitlements change
Existing API remains the same.  This does not require changes on local implementation

Steps to test this PR:

Purchase a subscription
Confirm that entitlements are returned from cache after first use (Breakpoint here)

Internal references:
Software Engineering Expectations
Technical Design Template

@miasma13 @quanganhdo got some updates...

Made the cache generic so we can not initialize for a specific type
Implemented Apple-like cache policy methods for elegance :bowtie:
Removed cache cleanup on fetch failure
Added entitlements to notification object
Addressed small comments for vars and etc


Updates to comments of diverging hostnames

@caskroom/maintainers Need some feedback.

Slightly changed the rule for url.
Added a rule to add this comment to appcast (see also #17498).

Reasons for the rule change to url:

Only one comment is needed (instead of two: # URL_HOSTNAME is the official download host per the [vendor homepage/appcast feed]).
Serves to explain related but slightly different reasons (rare but they do occur, and we usually bend the definition a bit).
Makes it clear it was verified (i.e. someone did indeed check it) and it was done so only when first introduced (so users don’t think it’s verified regularly).
The same comment can be used for both appcast and url.

In case there are concerns with the word “introduced”, I’ll point out the final result in a cask will be something like: # amazonaws.com verified as official when first introduced to the cask so it should be clear we’re referring to when the hostname itself was introduced (in case it changes, at which point we’ll need to verify it once more, as usual), not the cask.
If agreed upon, will make the following changes:

[ ] Update all casks across all official repos.

[ ]  caskroom/cask.
[ ]  caskroom/versions.
[ ]  caskroom/fonts.

[ ] Add examples to documentation:

[ ] url.md.
[ ]  appcast.md.

LGTM

Closing in favour of https://github.com/caskroom/homebrew-cask/pull/18051.

(was never actually closed)


Update README.md

Punctuation errors corrected

I've seen both 'right-click' and 'right click' used. We shouldn't change stylistic choices.


Combinational Sum in Python

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
Yes, it is a new feature
Describe the solution you'd like
A clear and concise description of what you want to happen.
It is a backtracking problem and I would like to add my solution
Additional context
Please assign this issue to me

Sure @bhagyashree-06, you can go ahead !


[Container Publishing] Add to docs about container changes for 8.0.200

Type of issue
Missing information
Description
There are a few changes coming down the pipe for containers in 8.0.200:

The PublishContainer target is available for every project! This means no more need for the NuGet Package for most projects. The project must

be publishable (IsPublishable = true) and
have the SDK container support enabled (EnableSdkContainerSupport=true). For Web and Worker projects this property is set by their MSBuild SDK. For other project types, the property can be set in the project file

Improved ContainerBaseImage inference by the tools to optimize for size and security:

targeting linux-musl-x64 or linux-musl-arm64 Runtime Identifiers will automatically choose the alpine image variants to ensure your project runs
If the project uses PublishAot=true then the nightly/runtime-deps jammy-chiseled-aot variant of the base image for best size and security
If the project uses InvariantGlobalization=false then the -extra variants is used to ensure localization still works
We should point users towards https://github.com/dotnet/dotnet-docker/blob/main/documentation/sample-image-size-report.md to learn more about the image variants' sizes and characteristics.

Page URL
https://learn.microsoft.com/en-us/dotnet/core/docker/publish-as-container?pivots=dotnet-8-0#containerbaseimage
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/docker/publish-as-container.md
Document Version Independent Id
401bc84b-9410-3583-91f6-88968654b588
Article author
@IEvangelist
Metadata

ID: 19c28091-b3ad-affb-6343-47d7fa066d55
Product: dotnet-fundamentals
Technology: dotnet-docker

Hey @baronfel - when are we expecting 8.0.200 to come through?

It'll drop next month alongside the 17.9 release.

This should be good to go now, right? @baronfel

Go for it!


typeRoots is not finding custom declaration file

TypeScript Version:
Version 2.6.2

Search Terms:
declaration file for module exporting function, external module, npm package, third-party module
Code
src/testFile.ts:
import getFieldList = require('graphql-list-fields');

<EMAIL_ADDRESS>// Doing just this below (as suggested by the Typescript Handbook does not work
// and results in the tsc error under **Actual behavior** below
import { GraphQLResolveInfo } from 'graphql';
declare function getFieldList(info: GraphQLResolveInfo): string[];
export = getFieldList;

// The code below is what actually works instead of the above
/*
declare module 'graphql-list-fields' {
    import { GraphQLResolveInfo } from 'graphql';
    function getFieldList(info: GraphQLResolveInfo): string[];
    export = getFieldList;
}
*/

Expected behavior:
Compiling without errors.
Actual behavior:
Error when running tsc:
src/testFile.ts(1,31): error TS7016: Could not find a declaration file for module 'graphql-list-fields'. '/node_modules/graphql-list-fields/index.js' implicitly has an 'any' type.
Try `npm install @types/graphql-list-fields` if it exists or add a new declaration (.d.ts) file containing `declare module 'graphql-list-fields';`

graphql-list-fields is an NPM package that I'm trying to use, which currently has no published type declarations.
After reading through the Typescript Handbook's section on declaration files, I found that I am trying to write a declaration file for a modular library and should use the module-function.d.ts declaration file template. This is how I came up with the code in index.d.ts above, but the compiler still complains about not having the declaration file for the module 'graphql-list-fields'. After trial and error, we found that adding declare module 'graphql-list-fields' around everything worked without compiler errors.
We tried setting "typeRoots": ["./node_modules/@types", "./src/@types"] in tsconfig.json, as mentioned in the tsconfig docs but that still did not work without declare module 'graphql-list-fields'. This seems to be an issue because tsc is not finding the type declaration in the directories specified in typeRoots.
Related Issues:
3019, 8335

"typeRoots" is meant for global code. i.e. something that is declarated in the global namespace, and you want to include it. this is why your declare module 'graphql-list-fields' {.. works, since it just declares a module with that name in the global namespace.
For modules, they have thier own scope, all you need is path mappig..
somethign like:
{
    "compilerOptions": {
        "target": "es5",
        "baseUrl": "./",
        "paths": {
            "*" : ["src/@t`ypes/*"]
        }
    }
}`

Thanks for clearing that up @mhegazy. I think it would be helpful if this was explained more in the TypeScript docs, possibly under the declaration files section.

TypeRoots is really a support we have added for back compat with typings and to allow migration, so we tried to keep it out of the docs as much as possible to avoid confusion.
Not sure if this fits in the declaration file section. we do have a note about it in https://www.typescriptlang.org/docs/handbook/module-resolution.html#path-mapping
I can add a note in the declaration file section about module resolution section as a whole.
give that section a read and let us know if you still find docs in it lacking

Oh I see. Yeah, that is the page that I needed to begin with. I think it would be nice to have at least a brief mention of path mapping and maybe a link to that doc somewhere under https://www.typescriptlang.org/docs/handbook/declaration-files/introduction.html.

I still think it would be helpful to have the docs updated as stated in my previous comment @typescript-bot

TypeRoots is really a support we have added for back compat with typings and to allow migration, so we tried to keep it out of the docs as much as possible to avoid confusion.

Having a supported feature with little-to-no documentation is what drives confusion. Please properly document features like this but be liberal with your warning language. For example:

Note: This feature is provided for backwards compatibility with typings to support migration. See the release notes [here] for more information.

This would be vastly preferable to having to scan GitHub Issues, StackExchange, etc. for information.

 I spent days on this.

If you don't mind slow down your application starting process little, you can just add this to your package.json start script TS_NODE_FILES=true and all custom declaration file will be found.

I'm now getting:
The following changes are being made to your tsconfig.json file:
  - compilerOptions.paths must not be set (aliased imports are not supported)

and this option is being deleted.

@KrzysztofMadejski that's done by CRA, not TS itself.

This thread says that typeroots is really for backwards compatibility. I am trying to use it to author types for definitively typed. How else would I properly test these types without typeroots? I have generated types using dts-gen and added types to my type roots and still no luck :-(

@Roaders did you find the solution to use dts-gen generated types?

One thing I don't understand here is that:
tsconfig.base.json:
"typeRoots": ["node_modules/@types", "types"],

And a directory structure:
<EMAIL_ADDRESS>/types/something-else/index.d.ts

It won't get picked up at all in my nrwl/nx repository. I can try a million things but if I move that something-else folder into node_modules/@types it'll magically work and get picked up, which suggests the typeRoots does absolutely nothing as node_modules/@types is magically handled.
Marking typeRoots as deprecated and saying it works in a weird/quirky way would have at least stopped me trying to use it.

I kept getting bitten by this and forgetting about having to configure the paths option as well, so I created a simple repository with the proper settings. Hope it helps someone.

I'm being bit by this as well. I couldn't get custom types for a 3rd party project picked up no matter what I tried. It was working for a while by copying the folder into node_modules/@types, but tsc or another process validates that directory and deletes unexpected files.
    "paths": {
      "something": ["types/something"]
    },

This seems to work but it was extremely unintuitive and under-documented. It didn't occur to me to try paths until I found this thread after many hours of failures. I thought paths was for "A series of entries which re-map imports to lookup locations relative to the baseUrl" (https://www.typescriptlang.org/tsconfig#paths), and unrelated to resolving type declarations.

I have a library written in javascript, which exposes type declarations to external consumers.  These type declarations are generated automatically using the typescript compiler in a types folder. In the consumer, it works fine, but I would like to use the same declarations within the library as well for intellisense/autocomplete within the IDE
I initially thought that typeRoots would be the way to go, but as discussed above, it seems to be only applicable for global modules / types.
as @mhegazy suggested, I tried using paths to accomplish this.
I can't make it work with relative paths, though it works fine with aliased absolute paths.
The below does not work
// src/packageA
...some code

// src/@types/packageA
...generated type definitions

// usage within the library - does not work
import packageA from '../../packageA'

// tsconfig
paths: {
  "*" : ["@types/*", "*"]
}

but the below code works:
// src/packageA
...some code

// src/@types/packageA
...generated type definitions

// usage within the library - works, but this is not what I want
import packageA from 'packageA'

// tsconfig
paths: {
  "packageA" : ["@types/packageA/*", "*"] //notice the aliasing here
}

Am i missing something here, or is it generally not possible to make paths work with relative paths ?

In my case, the issue was that I've been using include and exclude. The issue is that I was trying to access the global types from a file that wasn't included.
so I just remove the include and kept only the exclude, and now works as expected

@gaurav5430's comment got me on the right track!
My original folder layout:
@types/
  index.d.ts
src/
  index.ts
package.json
tsconfig.json

My tsconfig.json:
{
  "compilerOptions": {
    "baseUrl": "./",
    "declaration": true,
    "esModuleInterop": true,
    "module": "commonjs",
    "outDir": "dist",
    "paths": {
      "*": [
        "@types/*"
      ]
    },
    "skipLibCheck": true,
    "sourceMap": true,
    "strict": true,
    "target": "es5",
    "typeRoots": [
      "node_modules/@types",
      "@types"
    ],
  },
  "include": [
    "src/**/*"
  ]
}

I was still getting errors and I could not understand why. Turns out, @types/index.d.ts should actually be named after the module that doesn't have types. So, for me I had to change: @types/index.d.ts to @types/csv-to-js-parser.d.ts.
(Contents of that file being declare module "csv-to-js-parser";)
FINALLY
Also, this issue is super annoying.

Has anyone succeeded in making this work with a target set to ES6?
For me it works with a target set to ES5 but not ES6 (or any other target).
I was wondering why the suggested strategy here didn't work for me and then tried out switching my target to from ES6 to ES5. But I don't want ES5.

@gaurav5430

for anyone finding this issue i was able to resolve this in my code base by adding custom types to the tsconfig.base.json after declaring them in the typeRoots
tsconfig.base.json
{
  "compileOnSave": false,
  "compilerOptions": {
    "rootDir": ".",
    "sourceMap": true,
    "declaration": false,
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "importHelpers": true,
    "target": "es2015",
    "module": "esnext",
    "lib": ["es2017", "dom"],
    "skipLibCheck": true,
    "skipDefaultLibCheck": true,
    "baseUrl": ".",
    "paths": {
      "@prisma-client": ["packages/libs/prisma-client/src/index.ts"],
      "@ui/meeting": ["packages/libs/ui/meeting/src/index.ts"],
      "@ui/shared": ["packages/libs/ui/shared/src/index.ts"],
      "@ui/util": ["packages/libs/ui/util/src/index.ts"]
    },
    "typeRoots": ["types", "node_modules/@types"],
    "types": ["@emotion-types", "@window-types"]
  },
  "exclude": ["node_modules", "tmp"],
  "files": [],
  "include": ["types/**/*.d.ts"]
}

type dir

SO post - second answer

for anyone finding this issue i was able to resolve this in my code base by adding custom types to the tsconfig.base.json after declaring them in the typeRoots

@ALFmachine big ups for the types after typeRoots.. can't believe the order matters :o

I have a library written in javascript, which exposes type declarations to external consumers. These type declarations are generated automatically using the typescript compiler in a types folder. In the consumer, it works fine, but I would like to use the same declarations within the library as well for intellisense/autocomplete within the IDE
I initially thought that typeRoots would be the way to go, but as discussed above, it seems to be only applicable for global modules / types.
as @mhegazy suggested, I tried using paths to accomplish this. I can't make it work with relative paths, though it works fine with aliased absolute paths.
The below does not work
// src/packageA
...some code

// src/@types/packageA
...generated type definitions

// usage within the library - does not work
import packageA from '../../packageA'

// tsconfig
paths: {
  "*" : ["@types/*", "*"]
}

but the below code works:
// src/packageA
...some code

// src/@types/packageA
...generated type definitions

// usage within the library - works, but this is not what I want
import packageA from 'packageA'

// tsconfig
paths: {
  "packageA" : ["@types/packageA/*", "*"] //notice the aliasing here
}

This also works:
// src/packageA
...some code

// src/@types/packageA
...generated type definitions

// usage within the library - works, but this is not what I want
import packageA from 'absolute/path/from/base/url/'

// tsconfig
paths: {
  "*" : ["@types/*", "*"]
}

Note that both of the working versions require some change in my webpack module resolution as well to work correctly, but at least typescript seems to be resolving them correctly.
Am i missing something here, or is it generally not possible to make paths work with relative paths ?

how to resolve?


DON-1108 – add Person recently_confirmed_tips_total property

Set too when getting pending tips info on Person Get

Codecov Report
Attention: Patch coverage is 83.33333% with 3 lines in your changes missing coverage. Please review.

Project coverage is 70.50%. Comparing base (b3670d6) to head (d7b7a94).

Files with missing lines
Patch %
Lines

src/Application/Actions/Person/Get.php
83.33%
3 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #182      +/-   ##
===========================================
+ Coverage    70.44%   70.50%   +0.05%
===========================================
  Files           40       40
  Lines          934      946      +12
===========================================
+ Hits           658      667       +9
- Misses         276      279       +3

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


Add scope validation tests

Follow up to https://github.com/aspnet/MetaPackages/pull/61

Fixed by: https://github.com/aspnet/AzureIntegration/pull/46


unable to use ng2-completer

I followed the example but it show this error :
Error: No value accessor for form control with name: 'searchStr'

@amirensit can you provide a plunker that reproduces the error?

@oferh It works.I forger to import in  the  module that uses  the ng2-completer.
Thanks


Add hint for oneshot property & warning when it will be updated continuously by Force Continuous in AnimationMixer

Closes https://github.com/godotengine/godot/issues/95684

These properties should not be continually updated, so that warnings are issued when they may occur unintentionally.
Ideally, FLAG_USAGE should be used, but I fear the int value limit as flag, so I append that to HINT;
As I remember only audio and partcle bool value properties should have these, but if there are non-bool value properties in other classes that should have this, they should be in USAGE. If there is such a thing, please let me know.

This should really be a property usage, but I think we can add just only one more usage value🤔
Then again, none of the current ONE_SHOT properties have problem with this being a hint, so we could treat it as temporary solution and think of a fix once an actual problem arises (i.e. conflict with another hint, as properties can't have more than 1 hint). To avoid breaking compatibility in the future, you can unexpose the new hint, with a comment that it shouldn't be exposed, because it's improper solution or something.

For now, note that there is comment that reduz's lgtm on contributors chat.
https://chat.godotengine.org/channel/animation?msg=eFmBbXF992AHvW5DM

Thanks!


UglifyJS Reserved configuration

Hey guys, is there anyway to use UglifyJS's reserved config without ejecting?
I want to give Uglify a mangle config with reserved because my build is breaking. Anyway to do this?
{
    mangle: {
        // mangle options
      reserved: ["CID"]
    },
}

Sorry, we do not allow this right now.
I have a feeling we won't allow this; but is there any reason it's absolutely required?
Can the code be restructured in such a way that you do not need to reserve an identifier?

it is possible actually.
solved it by using
npm run eject
then check config/webpack.config.prod.js for 'mangle'

@Timer
This is my case.

@davidqhr You could try to use a hidden identifier on the object instead and check that it exists.

@Timer in my case the library is a dependency of a dependency. The change is on the roadmap, but unlikely to be fixed in the near future. Is eject the only solution here?

Right now, yes @treygriffith. Sorry!


Updated synopsis.md

I updated the synopsis for SILK guide.

@Aini-Bashir , I updated the Synopsis, please go through it and suggest changes.

Alright...

Alright. Let me correct it


Added PG 12.3; Dropped 9.4

Description
Closes #2593 #2592
Also changed 11.3 to 1..8
Rationale
Let's users start projects with latest PG 12 which has a lot of new performance speedups
Use case(s) / visualization(s)
Changed 11.3 to 11.8 since 11.3 was last published a year ago.

Thanks again @Andrew-Chen-Wang


Error restarting application: Server error, status code: 500, error code: 170011, message: Stager error: Failed to open TCP connection to stager.service.cf.internal:8888 (getaddrinfo: Name or service not known) macbook08:spring-music tariq$ ping stager.service.cf.internal ping: cannot resolve stager.service.cf.internal: Unknown host

I am trying to deploy spring-music app to my bosh-lite environment on my mac. This is similar to this issue . but I have deigo release deployed.
https://github.com/cloudfoundry/diego-release/issues/192
Seems like all vms are up and running.
$bosh vms
Acting as user 'admin' on 'Bosh Lite Director'
Deployment 'cf-warden'
Director task 132
Task 132 done
+---------------------------------------------------------------------------+---------+-----+-----------+--------------+
| VM                                                                        | State   | AZ  | VM Type   | IPs          |
+---------------------------------------------------------------------------+---------+-----+-----------+--------------+
| api_z1/0 (d863d2f4-e26f-4d71-b96d-0929eb84e160)                           | running | n/a | medium_z1 | <IP_ADDRESS> |
| blobstore_z1/0 (4bb3a1c1-e34d-4ce4-8661-e726173a3363)                     | running | n/a | medium_z1 | <IP_ADDRESS> |
| consul_z1/0 (c1aa2a25-7fdf-4b02-8934-8e8b104d778f)                        | running | n/a | small_z1  | <IP_ADDRESS>  |
| doppler_z1/0 (5ef67712-5be7-4edc-b6af-96a9236b01cc)                       | running | n/a | medium_z1 | <IP_ADDRESS> |
| etcd_z1/0 (16f2c590-0f16-4217-aab2-b97828d00e08)                          | running | n/a | medium_z1 | <IP_ADDRESS>  |
| ha_proxy_z1/0 (f1b15921-1853-405f-bb8f-3db74b36dec1)                      | running | n/a | router_z1 | <IP_ADDRESS>  |
| loggregator_trafficcontroller_z1/0 (58a557ab-322b-4ade-b7e4-22c6746956d5) | running | n/a | small_z1  | <IP_ADDRESS> |
| nats_z1/0 (b2e983ce-fd10-43cc-bae3-26c9ce9972d1)                          | running | n/a | medium_z1 | <IP_ADDRESS>   |
| postgres_z1/0 (244c5615-f9f3-447f-9b5a-212df17d5305)                      | running | n/a | medium_z1 | <IP_ADDRESS>  |
| router_z1/0 (a85da289-fc93-4f09-84b6-373a6d31a119)                        | running | n/a | router_z1 | <IP_ADDRESS>  |
| uaa_z1/0 (3d8ce7b8-1869-4417-a85b-a2c0b38f22ee)                           | running | n/a | medium_z1 | <IP_ADDRESS> |
+---------------------------------------------------------------------------+---------+-----+-----------+--------------+
VMs total: 11
Deployment 'cf-warden-diego'
Director task 133
Task 133 done
+-----------------------------------------------------------+---------+-----+------------------+-------------+
| VM                                                        | State   | AZ  | VM Type          | IPs         |
+-----------------------------------------------------------+---------+-----+------------------+-------------+
| access_z1/0 (a0cd3fc2-d792-4b1e-ab08-1f71276f6a19)        | running | n/a | access_z1        | <IP_ADDRESS> |
| brain_z1/0 (7e1110a4-e333-49a3-9c67-8a781cb60f1f)         | running | n/a | brain_z1         | <IP_ADDRESS> |
| cc_bridge_z1/0 (2ba39529-a066-4a91-9c19-683365041722)     | running | n/a | cc_bridge_z1     | <IP_ADDRESS> |
| cell_z1/0 (49425f4c-5c75-4bb0-943b-d1812ca10b5e)          | running | n/a | cell_z1          | <IP_ADDRESS> |
| database_z1/0 (6b5d66a1-ae4f-45d5-abc7-b8cd0875d6b7)      | running | n/a | database_z1      | <IP_ADDRESS> |
| route_emitter_z1/0 (5bf09fb4-8ab2-4f98-b791-eccce4e7ec52) | running | n/a | route_emitter_z1 | <IP_ADDRESS> |
+-----------------------------------------------------------+---------+-----+------------------+-------------+
VMs total: 6
Deployment 'garden-runc'
Director task 134
Task 134 done
+-------------------------------------------------+---------+-----+---------+-------------+
| VM                                              | State   | AZ  | VM Type | IPs         |
+-------------------------------------------------+---------+-----+---------+-------------+
| garden/0 (22d0ba10-4bc4-48e2-8ce4-ea21c09a5d3d) | running | n/a | garden  | <IP_ADDRESS> |
+-------------------------------------------------+---------+-----+---------+-------------+
VMs total: 1
$cf apps
Getting apps in org tariq-org / space dev as admin...
OK
name           requested state   instances   memory   disk   urls
spring-music   started           ?/1         512M     1G     spring-music-subclavian-queenliness.bosh-lite.com

Hi, @tariqsiddiqui,
Apologies for not responding earlier. Are you still seeing this issue? From the error you reported, it looks like the Cloud Controller on the api_z1/0 instance in the CF deployment is unable to resolve the stager component that should be running on the cc_bridge_z1/0 instance in the Diego deployment. I would suggest first checking whether the stager job and the consul_agent jobs on those two instances are all functioning correctly.
Best,
Eric, CF Diego PM

Any update on this issue, @tariqsiddiqui ? If not, the Diego team will close it out soon.
Thanks,
Eric

I am looking into it now.

Hi, @tariqsiddiqui, I'll close this out for lack of activity. If you're still having problems, please feel free to file a new issue with the versions of CF, Diego, and related releases you have deployed as well as how you generated your manifests. You may also be interested in trying out cf-deployment on BOSH-Lite as an easier way to deploy a Diego-backed CF installation than the separate manifests from cf-release and diego-release.
Best,
Eric


Implement custom versioned auro components

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: # (issue, if applicable)
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.

Implement custom versioned auro components where appropriate
Refactor some color/styling logic
Update dependencies

Type of change:
Please delete options that are not relevant.

[ ] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[ ] My update follows the CONTRIBUTING guidelines of this project
[ ] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: jordanjones243:white_check_mark: jason-capsule42:x: semantic-release-botYou have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in version 1.2.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add new file based catalog as sqlite based catalog is deprecated

Sqlite-based catalogs and their related subcommands are deprecated.
Support for them will be removed in a future release of opm.
This catalog is built with the ocs-operator bundle and the nooba
operator bundle. The make target is also flexible to support different
build cmd, target host & arch.

/cc @iamniting

/hold

File based catalog is still in alpha and shouldn't be used. For now we'll continue using sqlite based catalog.

@umangachapagain I don't think so, They are supported as far as I know.

@umangachapagain @iamniting PTAL, I am waiting on this PR to merge to start work on the upcomming refactors

/test latest-upstream-ci-index-latest-upstream-bundle

@umangachapagain PTAL


document subplots and helpers in vision.data

I didn't see a dropdown menu to request reviewers. Sorry this is my first time.
In https://docs.fast.ai/vision.data.html#BBoxBlock I documented get_grid, clip_remove_empty, and bb_pad.
since get_grid delegated to subplots in https://docs.fast.ai/torch_core.html, I also documented that.

@muellerzr @warner-benjamin
Ok I have included the types and return types and deleted extra spaces. I did not include return types in clip_remove_empty' or bb_pad` because they return the same types as the input types as per the style guide.

LG2M, awaiting final review from @warner-benjamin

LG2M, awaiting final review from @warner-benjamin

But wait, it is not passing the CI. Sorry I did not see this. There was a problem with my tuple typing. I needed to replace tuple[..., ...] with typing.Tuple[..., ...]. I am fixing that now

Ok I have removed typing library and added document for return types.

@ChrisRichardMiles I added a commit removing a local env setup error message from both notebooks. Please don't check those messages in.
Everything else looks good and ready to merge. Thanks!

@warner-benjamin
Thank you very much for catching that and fixing it. I didn't notice it. I will look for stuff like that in the future.


Update magic_wan_ipsec_tunnel.md

Documentation shows health_check_enabled default as true, but in my testing, the default is actually false

thanks for the PR! unfortunately, the file you've edited is a generated artifact of the documentation process. to see how to make changes to the documentation, you're best to check out https://github.com/cloudflare/terraform-provider-cloudflare/blob/master/contributing/registry-documentation.md


Binding to wildcard "<IP_ADDRESS>" then connecting throws ConnectException on macOS

Reproducer in https://github.com/armanbilge/epollcat/commit/6c3ea7e77bf9ddb901983d434655546ce1ac414a.
https://github.com/armanbilge/epollcat/blob/6c3ea7e77bf9ddb901983d434655546ce1ac414a/tests/shared/src/test/scala/epollcat/TcpSuite.scala#L244-L254

On my macOS 11 machine the println above gives met this:
/0:0:0:0:0:0:0:0:60833

(the port number varies per-run)
Furthermore, if I change the connect(...) to this:
connect(new InetSocketAddress("<IP_ADDRESS>", addr.asInstanceOf[InetSocketAddress].getPort))

Then the test passes.
@LeeTibbert could this be another case of getting an IPv4-compatible address instead of an IPv4-mapped address?

could this be another case of getting an IPv4-compatible address instead of an IPv4-mapped address?

Arman,  I think you have it exactly!
I will have to trace through the code.   When I did the PR to the similar issue I let
::0 pass without conversion because that is the IPv6 wildcard.   I have to dive
into the InetSocketAddress("<IP_ADDRESS>", 0) construction path to see how it
picks up its interior InetAddress.

Arman,
I've spent a long morning tracing this and think I have an understanding of two of the things, plural,
going wrong.  I need to write some C to track down a third. I also need to check how SN handles
a translation.
Overnight I will work on coming up with a good description of "what", then we can work out
possible solutions.   Not to keep you hanging but any description I write now would be gibberish
and cause more confusion.

Progress but no solution, then again, one can progress around a ring and not
get to the end.
I ratted around and found a python IPv6 client/server pair that I had been using
last Summer (2022).  Adapted them to this Issue and fired them up on Linux. All worked.
I then fired them up on macOS 13.0.mumble. Everything worked. Rats! I had been
expecting a connection to ::0 to fail on macOS.  The both server programs reported
that the connection came in on ::1, which is sensible.
Thinking that python might be "helping" me under the covers, I cobbled together
a C client/server pair which suits this issue.  Ran on Linux, everything passed, as expected.
Ran on macOS, and everything passed. Double Rats!!   Strange situation where something
working is cause for dismay.
I think the code thru the server is doing a sensible thing (but plenty of room for discussion later).
I need to look more closely at the connect code and trace through, knowing that connecting
to ::0, strange as it might be, works in python and C.
More as I discover it.  Time consuming as it is, I am glad you discovered this issue.

Thanks for the update :) I also ratted around in Node.js and libuv, and am hitting the same wall. Surely some other implementation has encountered these "quirks" and taken defensive measures, but I'm yet to stumble on it.
However, being unable to reproduce in a C implementation ... is interesting and unexpected 😅  is there any possibility that Scala Native is doing something during startup/initialization that could lead to this? It would explain why a vanilla C implementation behaves differently.

I believe the simple C programs worked and epollcat revealed the underlying OS failure/behavior
is because the former were written to block until the connect() completed and epollcat is async.
More next sprint, when my mind has untangled.

Thanks for the detailed write-up. Suffice to say, it's taken me more than a few passes for all most of it to sink in :)
I think we can all agree that a large part of the problem is the early allocation of the socket file descriptor, before we know whether we want AF_INET or AF_INET6. I blame the poor design of the JDK in this area which leaves us in a bad position. I am not sure if either of proposals has semantics that match the JDK, which would make it difficult to use in cross-compiling code. The real answer is, implement a different (better) API.
Something that bugs me is what feels like an  "asymmetry": specifically, that you can bind a socket to <IP_ADDRESS>/::0, but if you get the local address of said socket and attempt to connect to it, it is undefined behavior. What good is a local address if you cannot connect to it?

Linux & macOS IPv4 obviously agree with you (as do I).
A lot turns on "get the local address of said socket".
The situation comes about because of the interaction of two "magic" items: "Any" address & bind changing
its own socket address.  IPv6 is pretty strict about ::0 "Any" only making sense as an object for a server bind.
There is some room for discussion that "get local socket address" on a socket bound to ::0 should return
::1. (and that bind() should be changing its InetSocketAddress() to the same -- injecting mutability).
Rolling the discussion way back, connect(<IP_ADDRESS>) & connect(::0) should both be rejecting the connection
as "connect to any address" makes no sense.  That horse left the gate a long time ago.
Life in network land.


"Flight mode" enabled when teleport down stairs or any decline

Somehow the Warp tool needs to detect the floor (or navmesh) when warping down declines (Stairs for example).  It seems to handle inclines fine.  Allow warp tool to land below character root position Y value.
You can compound this once you're airborn for fun.

.

Oh you also see the following warning when you are airborn "Failed to create agent because it is not close enough to the NavMesh"  Not sure if it matters.

For now use the movement tool + grip to pull yourself back down.  Duh!


Need to uncheck "Release" option in Azure Key Vault Access Policy

Module: 03
Lab/Demo: 10
Task: 01
Step: 09
Description of issue
During the Access Policy creation, selecting all minus Rotation Policy Operations leaves 17 total options checked. When trying to connect SQL Server to the Azure Key Vault later in the lab, Exercise 3 - Task 5 - Step 14, it throws an "invocation" error for "Release". Unchecking the "Release" option resolves this issue in SQL Server.
Repro steps:

Follow lab instructions as normal through Exercise 3 - Task 5- Step 14
Authenticate to the Azure Key Vault during this step,
An error will pop up that reads, "Exception has been thrown by the target of an innvocation. Release (Microsoft.SQLServer.Management.ServiceManagement)."

Yup, this works. Had the same error too.

Note: While performing the encryption if any error thrown like Exception has been thrown by the target of an innvocation related to Rotary(Microsoft.SQLServer.Management.ServiceManagement) then make sure the Key Permission's values of Rotation Policy Operations are unchecked, if not in the Azure portal navigate to the Key Vault >> Access Policies >> Key Permissions >> Uncheck all the values under the Rotation Policy Operations .

Not to be rude, but did you even read my issue? This is not related to a
"Rotary" error but a "Release" error. If you follow my repro steps, you'll
find that there is a new option in the key permissions category that is not
detailed in the lab.
On Mon, May 23, 2022, 5:44 AM serling1962 @.***> wrote:

Closed #254
https://github.com/MicrosoftLearning/AZ500-AzureSecurityTechnologies/issues/254
as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftLearning/AZ500-AzureSecurityTechnologies/issues/254#event-6659939679,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXL7CCPDIWQ42BDVE4M2ZDTVLNOPRANCNFSM5WPVY7ZQ
.
You are receiving this because you authored the thread.Message ID:
<MicrosoftLearning/AZ500-AzureSecurityTechnologies/issue/254/issue_event/6659939679
@github.com>

I was looking at reports that this workaround worked for some students, but a didnt for a small subset.  I ran my own test instance, verified the above, and yet still ran into the issue.  Uncertain what might lead to the intermittency, but here is yet another alternate workaround:
After Step 11, but before Step 12, run the following query in SSMS.  Be sure to replace the value in KEY_PATH below with the proper value for your instance, which can be found in Key Vault >> Keys >> MyLabKey >> Current version >> Key Identifier:
CREATE COLUMN MASTER KEY [CMK_Auto1]
WITH
(
KEY_STORE_PROVIDER_NAME = N'AZURE_KEY_VAULT',
KEY_PATH = N'https://<keyvaultname>.vault.azure.net/keys/MyLabKey/<keyid>'
)
GO

After running this query successfully, continue with the lab steps, replacing Step 15 with the following:

On the Master Key Configuration page, in the Select generate column master key dropdown, select CMK_Auto1 and then select Next.


Allow generic restrictions upon credentials

This is a superset of #33 (make usernames more restrictive).  The premise is that we want to tell the Authenticator that passwords (or usernames, or X.509 certificates, or ...) need to have certain criteria before they can be accepted.

Ideally, the Username should have a trait associated with each store type and presumably a method to convert usernames between backing store types.

The trivial way to do this is to implement a trait where the default implementation is to accept the value, and it can be overridden with an implementation that knows better.

I would like to fluff and fold so that we could provide overlapping sets of traits, maybe a Vec of rules that must be satisfied, and the library enumerates them, but the lower-hanging fruit is to allow the consumer of the library to implement the trait in whole cloth.


chore: #[allow(clippy::large_enum_variant)] on Node and ProposalOrRef.

This PR silences two (remaining) Clippy warnings about the large size difference in Nodes and ProposalOrRefs enum variants.
Should we already Box the large variants? Or would it be sufficient for now to file an issue that reminds us to re-evaluate later?
Edit: Boxing might become obsolete later given more spec changes. Not sure if Clippy lints the other way around. So maybe allow + file issue is best for now.
With these changes, CI should be green again on, e.g., https://github.com/openmls/openmls/pull/1146 (when updated).

It seems that Clippy would also be happy when https://github.com/openmls/openmls/pull/1136 is merged. So maybe the best thing to do is to ignore Clippy for a bit :-)

This can be closed because Clippy already seems to be happy on main.


Pluto zoning tweaks

A couple things were discovered in #972 for ztl that are the same for pluto

Bug in special districts - sorting wrong order. This changes about 60 lots - outside of the lots that have their ordering manually set for the specific combo of special districts, there are luckily very few that are in multiple
Use grouping logic in commercial overlay just like we do for zoning districts. This ends up only affecting a few rows as well

Running build here to compare to nightly_qa. Differences are

40 sp dist flips (expected). I need to confirm with GIS about these (and ordering in ztl)
12 commercial dist changes (expected) - due to grouping by commercial overlay (so if there are two smaller C-2 overlays, that's captured)
1 splitzone change (due to a commercial overlay change)
25 lottype changes - unexpected. See #1012

Got go-ahead from GIS on these changes

No, I used Pluto's QA queries. So

checking total row counts
checking total number of changes per column (changes identified by bbl)
investigating changed rows for rows with changes in columns found above (1 column at a time)

merge?

Going over one more time with Casey today (who was out previously), so figured I'd hold off. Will get this merged as-is or with tweaks today!


Suggestion: Allow the Kata Kyu to evolve after publication

Currently I think the Kata Kyu level is pretty much cast-in-stone at time of publication.
But sometimes this means there are differences between the Kyu and the actual level of difficulty. There are regularly comments like "This was an easy 5Kyu" or "I really struggled with this 7Kyu" etc.
Some reasons for this include:

Since power users are often 1st to complete the Beta so they are unintentionally biased towards thinking it is easy (just because for them it is easy doesn't mean it is for everybody else)

Some Kata (esp math ones) require knowledge of special "tricks". Anybody who knows the trick may think a Kata is trivial (7Kyu) but unless you know that trick it is not

The Kata might be easy/hard in the initial language but not for others.

~~
I suggest that maybe the Kata Kyu can be allowed to "evolve" to a different value even after publication.

Only people who have solved they Kata should be rate the Kyu, but I suggest allow all solvers to rate the Kata Kyu (even after publication) by clicking a button to say:

This Kata was harder than its current rating. (Kyu should be higher)
This Kata was easier than its current rating. (Kyu should be lower)

After publication the effect of the rating would need to be minimal (e.g a rating after publication might have 1/25th value it would have had before publication) but it would mean if enough (e.g. 50) people thought a 7Kyu should have been a 6Ky then it would eventually become one... the idea is to have it tend towards the majority consensus.

So in time CW Kyu would evolve to have more consistency across all Kata

Or if > 50% of all solvers think the Kyu is wrong then it changes...

You can't satisfy everyone about the level of difficulty. Inevitably some people will think a kata is too hard/easy. Just see what happens to Advent of Code this year.
Opening the can of worms and let kata ranking be flexible is bad though, because once you do it it's like opening pandora's box; chaos will ensue and the situation is guaranteed to be uncontrollable. Since the kata ranking over-estimation are from early katas, so just deal with them. Don't make every kata malleable.

You can't satisfy everyone about the level of difficulty. Inevitably some people will think a kata is too hard/easy.

There is no expectation/goal here to satisfy everyone. I only suggested that a "majority rules" approach might help gravitate to a more accurate Kyu than something that a handful of power users set on a whim.
If lots of people think it is harder/easier then the current Kyu is probably about right.
However, if a significant majority of people think the Kata is harder/easier than its kyu then  just maybe the masses are right, and the 5 people that set that kyu in the first place were wrong.

chaos will ensue and the situation is guaranteed to be uncontrollable

Really? Or you might decide to control it simply by a rule that kyu can only vary +/- 1kyu from its original ranking.

There is no expectation/goal here to satisfy everyone. I only suggested that a "majority rules" approach might help gravitate to a more accurate Kyu than something that a handful of power users set on a whim.

How should we measure the "majority"? This seems to only work if every user who solved the kata also reevaluates the ranking. I think it's difficult to collect enough votes to be meaningful.
Also, kata rank is tied to honor points and internal score. The change must be propagated to thousands of users' statuses. When is the right timing to trigger the change?
Kata rank is subjective, it'll be never perfect because it's derived from votes. There's no right or wrong. Even those users who thought the kata rank is "wrong" might disagree with themselves later after solving more kata.

Maybe there can be a separate section showing what users think about the kata rank?
<8 kyu> Multiply
[318] [27] [75% of 2,983] [288,771 of 1,063,845] [<8 kyu> 3] <- most voted kyu with count

I've seen something like this in some websites doing reviews, having their own reviews and users' votes separate.

Hi @kazk. This was just a thought bubble. A statistician could maybe come up with better rules.

How should we measure the "majority"?

e.g. "75% of all solvers".

This seems to only work if every user who solved the kata also reevaluates the ranking. I think it's difficult to collect enough votes to be meaningful.

A lack of a vote is same as a vote for the status quo isn't it?

When is the right timing to trigger the change?

At the time that the majority tips the scales. eg if 75% people say the 7ku should be 6Kyu then trigger happens when that majority is reached. Now that it is changed to 6kyu and would require 75% people to vote it to be something else to change it again (it gets less and less easy to change - it will reach a stability where the majority think it should be)

Kata rank is subjective, it'll be never perfect because it's derived from votes. There's no right or wrong.

Of course. Nothing is perfect. But regardless CW still expects that 6kyu is "harder" than 7ku and 5ky is "harder" than 6kyu. So perfect-or-not there is required to be a proper progression of difficulty. This means any Kata which are graded poorly are messing up that fundamental CW assumption.

Even those users who thought the kata rank is "wrong" might disagree with themselves later after solving more kata.

If you change your mind later then just change your vote 😉

Actually, given how CW consists of majority of newbie programmers I wouldn't be surprised if everything ended up getting a +1 rank.
That's why I don't like this whole proposal at all, there's an overwhelmingly vocal (to the point of being a red herring) opinion that expert users often under-ranks a problem's difficulty, when in fact the opposite happens far more often (think of the numbers). If you're a newbie, how are you going to know how hard a problem is? The context that gives a problem its appropriate relative ranking does not exist in a newbie's head. By this kind of logic, the entry test would be 6kyu since obviously some people don't even know what a program is! Or even elementary maths! Hence I often feel that the whole fuss about this is based on a shaky and probably false premise.
Not to mention that you won't have enough for anything other than the easiest katas where lots of people will solve them (hint: it's white). So in the end you're just adjusting the white and yellow katas. This amplifies the effect I mentioned above.
(That's also why I said we need to freeze the ranking and stick to that: Anything movable is fiddly, and you don't want a moving part to hit you months or years ahead when you're not watching it anymore. It's just like immutable states, easier to reasons, harder to backstab you in the dark ;-))


Update pom.xml (dependencies for Win10 with JDK9)

Hi! I added 3 dependencies to make Analyzer run on Win10 with JDK9
Cheers
o/

Hi whoeza, there will be a new version of clarity-analyzer soon, which sets a new baseline to JDK 17 and will switch to gradle as a build system. (Check out the CSGO branch if you already want to give it a try)


Add route53resolver to label and prow jobs

Add route53resolver to label and prow jobs.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


Tx Id

Changes
Use the transaction id supplied to bind logger against if it exists.
How to test
Check unit tests pass and have been modified correctly.
Who can test
Anyone but @iwootten

👍


Fix Deprecated Import from docs/agents/quick_start.mdx

This import is deprecated.
import { createRetrieverTool } from "langchain/agents/toolkits";
Should be:
import { createRetrieverTool } from "langchain/tools/retriever";

You are correct, thank you!


Example wrong on front page?

Doesn't i32 overflow after the max value - or am I reading the specification wrong?

Yes you’re correct in that the addition can overflow. As a simple default we’ve chosen to elide this important point. However for places where you really want to be sure there are no over flows, there are several ways to deal with that with refinement types, see this for example
https://ucsd-progsys.github.io/liquidhaskell-blog/2017/03/20/arithmetic-overflows.lhs/


Update README.md

I think we need this feature.

For todo's, it would be better to create issues.


Microseconds on :utc_datetime probably should tolerate {0, _}

Updating a :utc_datetime field like this
change(%{field: DateTime.utc_now |> Timex.beginning_of_day})

will raise (ArgumentError) :utc_datetime expects microseconds to be empty, got: #DateTime<2019-07-02 00:00:00.000000Z>
The reason is that Timex truncates the (correct, I suppose) fields of the DateTime, while keeping the 2nd elem of the microseconds field as-is. This "precision" value bears no meaning when the first tuple value is zero.
I hope I got that right!

This "precision" value bears no meaning when the first tuple value is zero

That's not true. If I saw the digit is 0 with precision of 1, i am implying I know it is 1.0 within a range of 0.05. For a precision of 6, that's your guarantee is much higher. You have to use _usec types or you have to truncate it. :)

From the typespec doc (https://github.com/elixir-lang/elixir/blob/v1.9.0/lib/elixir/lib/calendar.ex#L55) I have a different understanding. It does not talk about ranges (intervals), but about numbers of digits.
For %{seconds: 0, microseconds: {500_001, 1}} I interpreted that a representation is allowed as "0.5", but not as "0.500001".
Is that typespec documentation wrong?

I would say the documentation is imprecise because I have a different understanding than yours.

That would probably imply that the implementation of Timex.beginning_of_day is wrong.

change(%{field: DateTime.utc_now |> Timex.beginning_of_day})

with DateTime.utc_now you got microsecond precision, I'd expect that without |> Timex.beginning_of_day you'd get the same error you had. If not, that's unexpected and in that case:  what's your ecto and timex version?

WIth Timex 3.4.1 I did not see the error. It appeared when  upgrading to 3.6.0
My ecto version is 3.0.6.

My point was with:
change(%{field: DateTime.utc_now})

you should have been getting the error already. You do, right? So I dont think the issue is with Timex per se. If anything, its seems like newer Timex maintains precision (as opposed to possible truncating) which is good.

I never did something similar to change(%{field: DateTime.utc_now}).
I expected Timex.beginning_of_day to, semantically, erase milliseconds, so using this with change should not be a problem.
It looks very much like bitwalker interpreted the :milliseconds field like I did above, and changed the implementation recently to leave the second tuple position ("precision") unchanged. This breaks my expectation just stated.
The question is, what exactly is the meaning of the two tuple positions? The Elixir documentation, the Timex implementation and the casting exception in Ecto are at odds with this.


rest: Add pagination support

Upgrade tests due to NIPAP not properly restarting after the upgrade. I'm working on that one... LGTM!


SNAP-1841

Changes proposed in this pull request
Added methods to check auth-provider value and get the authservice.
Patch testing
Manual testing
ReleaseNotes changes
NA
Other PRs
snappydata: https://github.com/SnappyDataInc/snappydata/pull/737
spark-jobserver: https://github.com/SnappyDataInc/spark-jobserver/pull/14

LGTM


Fixed summary in TDMSReader.nuspec

Doh, thx! That was some copy+paste development there.... :O

Can't blame you, I just copy pasted the description field...

:+1:


In-page anchors on GitHub pages don't work

For example:
percollate pdf https://github.com/danburzo/percollate

Will result in a PDF where the links in the Table of Contents doesn't work:
danburzopercollate.pdf
(produced on macOS /<EMAIL_ADDRESS>I may be dense, but I can't tell how the anchors work in browsers in the first place 😰 (Later edit: the behavior is dependent on JavaScript — of course 😄 )

It works correctly, however, if the pages are published on GH Pages, e.g. https://danburzo.github.io/toolbox/
So the bug seems to be related to the weird way GitHub works with anchors; let's treat this as low-priority.


BluetoothControl: Remove devices from list before scan.

Remove devices that are not connected and not bonded
before new scan is started.

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


Add SEO metadata to Hour of Code

Adding in image for twitter/facebook previews as well.

@pelikhan will this get localized? should be included in webstrings, right?

None of this is localized.

From: Galen Nickel<EMAIL_ADDRESS>Sent: Tuesday, December 8, 2020 3:28:18 AM
To: microsoft/pxt-arcade<EMAIL_ADDRESS>Cc: Peli de Halleux<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/pxt-arcade] Add SEO metadata to Hour of Code (#2677)
@ganicke approved this pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpxt-arcade%2Fpull%2F2677%23pullrequestreview-546697446&data=04|01|jhalleux%40microsoft.com|7dfe89617d394f2a8fbb08d89b20ecda|72f988bf86f141af91ab2d7cd011db47|1|1|637429912993159448|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=WLxu1XDXOW1HcOk2N5yztErAXjchEtEfwY1znHK%2FOZc%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA73QKNYZVOZEOZVJ3EKUGLSTWFMFANCNFSM4URDNZKQ&data=04|01|jhalleux%40microsoft.com|7dfe89617d394f2a8fbb08d89b20ecda|72f988bf86f141af91ab2d7cd011db47|1|1|637429912993169444|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=m7qMC9shZaJD%2BzF6GmAjQl5kbWegjemxo0Kj9X5DWOQ%3D&reserved=0.


Added Kubernetes validation for Tinkerbell hardware name field

Description of changes:
Added Kubernetes validation for Tinkerbell hardware name field for the generate hardware and create cluster command.
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Sema: Allow calls to @_unavailableInEmbedded functions in compatible contexts

Treat @_unavailableInEmbedded as if it were @available(Embedded, unavailable) and apply platform compatibility logic in the availability checker. Revert back to disallowing calls to universally unavailable functions (@available(*, unavailable)) in all contexts.
Unblocks https://github.com/swiftlang/swift/pull/77258.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


KPI Status Graphic drop-down values incompatible with Power BI

Some of the pre-populated drop-down values for Status Graphic in the KPI properties work with Excel, but not Power BI (Power BI displays integer values).
The issue appears to be the hyphen - for example using "Traffic Light - Single", Tabular Editor populates "Traffic Light – Single" (long hypen) but Power BI appears only to work with "Traffic Light - Single" (short hyphen).
Can these be changed to pre-populate with the short hyphens?

Fixed in 2.9.3


Add docs for flex, photon and cinder volume sources. Closes #https://…

…github.com/koki/short/issues/147
@ublubu

also added docs for job to this PR

lgtm, needs a rebase

added docs for daemon_set and rebased. Should be good to go now


flutter run does not show logs on iOS

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
void main() {
  print("Log from dart");
  runApp(const MyApp());
}

flutter run -d iphone

Expected results
Should show logs.
Actual results
Doesn't show logs.
Code sample
Code sample
void main() {
  print("Log from dart");
  runApp(const MyApp());
}

Screenshots or Video
No response
Logs
Logs
No logs from terminal:
eseidel@erics-mbp ios_test % flutter run -d iphone
Launching lib/main.dart on iPhone in Pocket in debug mode...
Automatically signing iOS for device deployment using specified development team
in Xcode project: 8R83HS5GZ2
Running Xcode build...
 └─Compiling, linking and signing...                      1,879ms
Xcode build done.                                            5.8s
(lldb) 2023-05-18 10:04:50.359884-0700 Runner[1136:55318] [VERBOSE-2:FlutterDarwinContextMetalImpeller.mm(35)] Using the Impeller rendering backend.
flutter: Log from dart
Installing and launching...                                        11.0s
Syncing files to device iPhone in Pocket...                         29ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

A Dart VM Service on iPhone in Pocket is available at:
http://<IP_ADDRESS>:55530/RoespouBheY=/
The Flutter DevTools debugger and profiler on iPhone in Pocket is available at:
http://<IP_ADDRESS>:9101?uri=http://<IP_ADDRESS>:55530/RoespouBheY=/

They show up in XCode fine:
2023-05-18 09:51:27.536411-0700 Runner[1037:45700] Metal API Validation Enabled
2023-05-18 09:51:27.708781-0700 Runner[1037:45700] [VERBOSE-2:FlutterDarwinContextMetalImpeller.mm(35)] Using the Impeller rendering backend.
2023-05-18 09:51:27.760726-0700 Runner[1037:46008] flutter: The Dart VM service is listening on http://<IP_ADDRESS>:60534/ZpThp0psw04=/
2023-05-18 09:51:27.818336-0700 Runner[1037:45988] flutter: Log from dart

Flutter Doctor output
Doctor output
eseidel@erics-mbp ios_test % flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.1, on macOS 13.2.1 22D68 darwin-arm64, locale
    en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] VS Code (version 1.78.2)
[✓] Connected device (3 available)
    ! Error: Eric’s Apple Watch has recently restarted. To use Eric’s
      Apple Watch with Xcode, unlock it and its companion iPhone (code 19)
[✓] Network resources

• No issues found!

eseidel@erics-mbp ios_test %  flutter devices
3 connected devices:

iPhone in Pocket (mobile) • 00008120-0011315A2290C01E • ios            • iOS
16.4.1 20E252

If I add a log to _incrementCounter() those show up:
  void _incrementCounter() {
    setState(() {
      print("incrementing counter");
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

flutter: incrementing counter
flutter: incrementing counter
flutter: incrementing counter
flutter: incrementing counter
flutter: incrementing counter
flutter: incrementing counter
flutter: incrementing counter
flutter: incrementing counter

cc @vashworth @christopherfujino Guessing that prints near app startup might be getting dropped if the debugger isn't attached yet?

@vashworth do we not start the main isolate paused until the debugger attaches?

@vashworth do we not start the main isolate paused until the debugger attaches?

Looks like we do not start it paused (assuming that's what this flag is for).
https://github.com/flutter/flutter/blob/2d6c67f4a4b73ce406587d8a06755d31ce5fc97b/packages/flutter_tools/lib/src/commands/run.dart#L409
https://github.com/flutter/flutter/blob/2d6c67f4a4b73ce406587d8a06755d31ce5fc97b/packages/flutter_tools/lib/src/commands/run.dart#L94-L97

ahhh

The flutter: Log from dart log message is shown in the tool's output (as seen in the logs captured in https://github.com/flutter/flutter/issues/127121#issue-1715970602)
But the log message is printed midway through the Installing and launching phase, so it's easy to miss.
The flutter_tools iOS device could buffer the debugger log stream until the tool has finished launching the app and printing the tool usage instructions.  But that might hide potentially useful logs if something goes wrong during the tool's app launch flow.

The flutter: Log from dart log message is shown in the tool's output (as seen in the logs captured in #127121 (comment))
But the log message is printed midway through the Installing and launching phase, so it's easy to miss.
The flutter_tools iOS device could buffer the debugger log stream until the tool has finished launching the app and printing the tool usage instructions. But that might hide potentially useful logs if something goes wrong during the tool's app launch flow.

wow, eagle eye

Oh. If it’s printed and I just missed it then that’s my bad and we can just
close this.
On Thu, May 18, 2023 at 3:50 PM Christopher Fujino @.***>
wrote:

The flutter: Log from dart log message is shown in the tool's output (as
seen in the logs captured in #127121 (comment)
https://github.com/flutter/flutter/issues/127121#issue-1715970602)
But the log message is printed midway through the Installing and launching
phase, so it's easy to miss.
The flutter_tools iOS device could buffer the debugger log stream until
the tool has finished launching the app and printing the tool usage
instructions. But that might hide potentially useful logs if something goes
wrong during the tool's app launch flow.
wow, eagle eye
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/127121#issuecomment-1553753986,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADU2TO45VFMUN4RQRIT7A3XG2RULANCNFSM6AAAAAAYGW5WUQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I think we closed this prematurely?  Unless I misunderstood.  When I add a log in the engine, from within xcode I get:
flutter build ios --config-only --local-engine-src-path=$HOME/Documents/GitHub/ios_engine/src --local-engine ios_debug_unopt_arm64
2023-05-25 14:43:17.095278-0700 Runner[35905:3750023] [VERBOSE0:FlutterViewController.mm(232)] sharedSetupWithProject
2023-05-25 14:43:17.095494-0700 Runner[35905:3750023] Metal API Validation Enabled
2023-05-25 14:43:17.273696-0700 Runner[35905:3750023] [VERBOSE-2:FlutterDarwinContextMetalImpeller.mm(39)] Using the Impeller rendering backend.
2023-05-25 14:43:17.329845-0700 Runner[35905:3750345] flutter: The Dart VM service is listening on http://<IP_ADDRESS>:56867/OTrtAg28Ux8=/
2023-05-25 14:43:17.409185-0700 Runner[35905:3750321] flutter: Log from dart

But from flutter run I get:
eseidel@erics-mbp ios_test % flutter run -d iphone --local-engine-src-path=$HOME/Documents/GitHub/ios_engine/src --local-engine ios_debug_unopt_arm64
Launching lib/main.dart on iPhone in Pocket in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode
project: 8R83HS5GZ2
Running Xcode build...
 └─Compiling, linking and signing...                      2,256ms
Xcode build done.                                            9.3s
Installing and launching...                                        18.5s
Syncing files to device iPhone in Pocket...                         46ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

A Dart VM Service on iPhone in Pocket is available at: http://<IP_ADDRESS>:62201/H4-c8GRdgCA=/
The Flutter DevTools debugger and profiler on iPhone in Pocket is available at:
http://<IP_ADDRESS>:9101?uri=http://<IP_ADDRESS>:62201/H4-c8GRdgCA=/

This is with:
eseidel@erics-mbp ios_test % flutter --version
Flutter 3.11.0-14.0.pre.15 • channel main • https://github.com/flutter/flutter.git
Framework • revision 8576da53c5 (45 minutes ago) • 2023-05-25 14:01:18 -0700
Engine • revision 6ff02c1726
Tools • Dart 3.1.0 (build 3.1.0-146.0.dev) • DevTools 2.23.1

And then flutter/engine@6ff02c17268ff8d0dc0cf33c7df0ef76c66cecff, with a slightly modified dart_lang/sdk of the correct version.

For clarity, the log I added was:
2023-05-25 14:43:17.095278-0700 Runner[35905:3750023] [VERBOSE0:FlutterViewController.mm(232)] sharedSetupWithProject

Maybe I have to turn up the verbosity to see the log?

Yup, I see the log when I turn on -v.  OK.


Bug with timed event when no other events scheduled

The following should not execute the scheduled event until t=10, but it gets executed when @run! is called:

julia> using DiscreteEvents

julia> c=Clock()
Clock 1: state=:idle, t=0.0, Δt=0.01, prc:0
  scheduled ev:0, cev:0, sampl:0

julia> f(c)=println(tau(c))
f (generic function with 1 method)

julia> @event f(c) at 10

julia> @run! c 1
10.0
"run! finished with 1 clock events, 0 sample steps, simulation time: 1.0"

However, if other events are scheduled before t=10, the event doesn't trigger when running up to t=1.

It seems that the issue is at:
https://github.com/JuliaDynamics/DiscreteEvents.jl/blob/4a9fab45a9af19c7d940a48714afb707b2e7598d/src/clock.jl#L291-L295
In the example above, c.time = 0.0 and c.end_time = 1.0. Since there is no sampling, c.tn = 0, which triggers the while loop. Triggering the while loop results in running _step!(c) which steps to the next event in the schedule. This corner case occurs because we are at c.time = 0. The logic needs to be fixed here so that _step!(c) is not triggered.

In a local branch, I substituted the while condition
while any(i->(c.time ≤ i < c.end_time), (c.tn, c.tev))

with the following
    while c.time ≤ c.tev < c.end_time || (c.time <= c.tn < c.end_time && c.tn != 0) ||
(c.time <= c.tn < c.end_time && _sampling(c))

It's pretty verbose but I think it works.
Actually it isolates the case where c.tn == 0 and when there is some other sort of sampling taking place.
If you like I can make PR from my branch. I also added a couple of tests.

A PR would be great. Thanks.