Disable the use of configuration settings if tenant is modified

Currently you can edit a root tenant by disabling configuration settings. The problem is that you can then re-enable configuration settings after it has been edited. This will, at a minimum, cause the chargeback report to fail. The issue is that the tenant name will use the config settings if use_config_for_attributes is set to true.
t = Tenant.first

=> #<Tenant id: 1, domain: nil, subdomain: nil, name: "My Company", etc...>
=> t.name # -> "My Company"

=> t.name = "Some Company"
=> t.save!

=> t.name # "My Company" (surprise!)

=> t.use_config_for_attributes = false
=> t.name # -> "Some Company" (expected)

https://github.com/ManageIQ/manageiq/blob/master/app/models/chargeback_vm.rb#L183-L189
Steps to reproduce in the UI:

Turn off the "Use Configuration Settings"
Edit tenant
Turn on "Use Configuration Settings"

Workaround: Disable configuration settings for tenant
Original issue: https://bugzilla.redhat.com/show_bug.cgi?id=1866289

cc @kbrock since you know a bit about the use_config_for_attributes

@kbrock I thought you fixed this one?

I could have sworn this was fixed.
Either way, would be really nice to just delete use_config_for_attributes and have this work as normal

@kbrock Personally I think I would add created_at and updated_at fields to the table and use that.

@Fryguy do we still need to support ::Settings.server.company or Settings.server.custom_login_text?
These are part of the tenant but have overrides in settings.yml. company name has a default value but custom login text does not.
Looks like we have a few remnants in ui-classic.
https://github.com/ManageIQ/manageiq-ui-classic/blob/master/app/controllers/ops_controller/settings/common.rb#L434-L437
And the custom logo parts of _settings_custom_logos_tab.html.haml
But swapping session[:customer_name] with current_user.tenant#name looks to be simple enough.
Changing the custom login text may be a little more tricky since we won't know which tenant to use before the user logs in. (this was the main purpose of tenancy on first run but custom urls and that stuff have basically been all but dropped
Just noticed this issue and thought about all the complexity around allowing a database value to override a settings value. Would be nice to drop that complex feature.

Goal
remove logic for `use_config_for_attributes: i.e.: https://github.com/ManageIQ/manageiq/blob/master/app/models/tenant.rb#L336-L343
Current

The administrator can set the company name in settings.yml. It is accessible via ::Settings.server.company
The administrator alternatively can set the company name in Tenant#name.
The administrator uses Tenant#use_config_for_attributes to determine which one represents the company name

Proposed

The administrator can set the company name only in Tenant#name.
Tenant#use_config_for_attributes is ignored or it goes away. ( 🔥  )

Work

Delete extra logic from Tenant. ( 🔥  )
Modify haml and text helpers to ensure the company name is read from the current_tenant.
If there is no current tenant because no one is logged in, we will use the root tenant for company name an login text
Modify ops controller to not set extra variables in the session based upon changes to the company name in settings.yml.
Remove company name from the session. ( 🔥  )
Modify Tenant react component to remove use_config_for_attributes and to possibly simplify the logic around the field.

Note: The logic to determine a tenant for an unlogged in user based upon the hostname/url was removed from our app a few years ago. (tenancy v2? I think when we introduced quotas)

What would be the migration for existing installations?
Is API considered here as well?  I think /api currently has this information
Is this the current mechanism for appliance-specific branding (of the login screen and the subsequent screens)?  If so, how will that work after this change? Saw this: "we will use the root tenant for company name an login text", but I'm not sure that answer the appliance-specific part.

The administrator can set the company name only in Tenant#name.

For my edification, how is this set currently?  Is there a UI screen to set Tenant name?

What would be the migration for existing installations?

We would just stop using the value in Settings.yml.

Is API considered here as well? I think /api currently has this information
The API is currently using the Tenant model. This model holds the logic. I think there was some logic in the legacy ui-classic screens, but think that was lost 1 or 2 ui transitions ago.

Is this the current mechanism for appliance-specific branding (of the login screen and the subsequent screens)?

Yes, they use the Tenant model to display this.

If so, how will that work after this change? Saw this: "we will use the root tenant for company name an login text", but I'm not sure that answer the appliance-specific part.

There will no longer be appliance specific branding. It will be tenant specific. As I understood, the only real reason for appliance specific (and not region specific) was due to needing multiple LDAP servers, which never seemed fully thought through.

The administrator can set the company name only in Tenant#name.
How is this set currently? Is there a UI screen to set Tenant name?

We have a tenant screen to set the company. This is what I referred to as being introduced in 2015.

There will no longer be appliance specific branding. It will be tenant specific. As I understood, the only real reason for appliance specific (and not region specific) was due to needing multiple LDAP servers, which never seemed fully thought through.

How can you determine the tenant before logging in?  Part of the reason for appliance-specific branding was to have different entrypoints for service providers.  For example, a service provider might have coke.example.com and pepsi.example.com.  Each one would point to a different appliance, where the login screen is customized for that company.  I'm find with switching to tenant-based, but how do we know what tenant to show?

yea. the only real use case I know about was 2 different regions used a different LDAP server and they wanted to change the messaging on the login server to display a server name that let the users know it was in a different region (read: ldap server, not actual miq region)
Now in terms of different tenants being on different urls, we had that functionality in Tenancy 1.0, but we tore it out since PMs no longer wanted the functionality.


[AzureMonitorExporter] updating track activity events method to also track non-exception events

I would like to add activity events to the AppInsights "customEvents" collection. Currently this exporter only logs exception events. I have created this PR to add other events as well.

@microsoft-github-policy-service agree


Scenes inside tabs (switch) getting corrently unmounted and then incorrectly re-mounted

Version
Tell us which versions you are using:

react-native-router-flux v3.39.1
react-native v0.44

This is a clone of #1329. I am opening a new issue since I cannot reopen #1329. All relevant history is there.

can confirm it. all scenes do re rendering while clicking between tabs.

Can you test this PR? => #1386

I did. It did not help. I essentially used your fork of the repo. I still see the issue.

This is happening to us as well

(Also, this didn't start happening until we upgraded from React Native 0.42 to 0.44)

That's interesting. Did you do this comparison with the same version of react-native-router-flux?
Get Outlook for iOShttps://aka.ms/o0ukef

From: Luke Miles<EMAIL_ADDRESS>Sent: Tuesday, May 16, 2017 5:02:48 PM
To: aksonov/react-native-router-flux
Cc: Ujwal Setlur; Author
Subject: Re: [aksonov/react-native-router-flux] Scenes inside tabs (switch) getting corrently unmounted and then incorrectly re-mounted (#1870)
(Also, this didn't start happening until we upgraded from React Native 0.42 to 0.44)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/aksonov/react-native-router-flux/issues/1870#issuecomment-301947902, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFkMXSc4c5q-TKjwV7uJ93zhEPiSpdR0ks5r6jkogaJpZM4NboZ4.

i had to downgrade router-flux for now. my deps:
"react": "16.0.0-alpha.3",
"react-native": "v0.43.0-rc.3",
"react-native-router-flux": "3.37.0".
works for me

Thanks, downgrade to 3.37.0 resolve the issue.

@sarovin
thanks, I've tested your PR, and it fix the problem.

@ezha86 - confirmed that works. 0.43.3 comes with react 16.0.0-alpha.6 -- important to note becuase you have to downgrade to -alpha.3 for this to work.


Add method for optionally disabling EIP-3607 for eth_call and eth_estimateGas

Describe the feature
The hive test eth_call/call-simple-transfer sends an eth_call RPC with a from parameter of an account that has deployed code.
The call:
{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"from":"0xaa00000000000000000000000000000000000000","gas":"0x186a0","to":"0x0100000000000000000000000000000000000000"},"latest"]}

The account (0xaa00000000000000000000000000000000000000):
https://github.com/ethereum/execution-apis/blob/main/tests/genesis.json#L34-L44
This motivates a way to optionally disable EIP-3607.
EIP-3607 notes:

Clients might choose to disable this rule for RPC calls like eth_call and eth_estimateGas as some Multi-Sig contracts use these calls to create transactions as if they originated from the multisig contract itself.

Additional context
Once #1958 is in, it should be easy to test support by running the hive test:
./hive --client reth --sim ethereum/rpc-compat --sim.limit "/eth_call/call-simple-transfer"

Output:
>>  {"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"from":"0xaa00000000000000000000000000000000000000","gas":"0x186a0","to":"0x0100000000000000000000000000000000000000"},"latest"]}
<<  {"jsonrpc":"2.0","error":{"code":-32003,"message":"sender not an eoa"},"id":1}
response differs from expected:
 {
-  "error": {
-    "code": -32003,
-    "message": "sender not an eoa"
-  },
   "id": 1,
   "jsonrpc": "2.0"
+  "result": "0x"
 }

Here's how we did it in foundry https://github.com/search?q=repo%3Afoundry-rs%2Ffoundry eip-3607&type=code
Revm has an option called disable_eip3607 behind an optional_eip3607 feature flag.


Revert "Adding express route port authorization apis"

Reverts Azure/azure-rest-api-specs#10491

/azp run automation - sdk

/azp run unifiedPipeline

Reverting this as NRP changes are still not in.


Memory Usage when calling e.g. btalib.rsi(df) in a loop

I am running a MultiplexSocket on Binance API to get 5 minute klines of around 200 symbols. On every new completed candle I call a "run_technical_analysis" function. Inside that function I calculate indicators for each symbol like this:
period = 14
value = btalib.ema(candlesticks_df.tail(period + 1), period=period) ## Version A
#value = candlesticks_df.Close.tail(14).ewm(span=14).mean() ## Version B
After that I append value.df.tail(1) to a list. On Version A my RAM goes up almost 10 MB every 5 minutes. It seems like the allocated memory for 'value' is not beeing freed. When I use Version B instead there is no such issue.
What can I do to reduce that memory usage?

Same problem on my end!

with btalib.stochastic(df) same problem, memory leak very fast.

Every indicator with btalib inside a loop is filling memory, even if we use del to free variables returned. This is a big issue.


Regenerate road segments when material updated

If the user assigns a new material to the RoadNetwork, it should add an updated material. Right now, the user would have to trigger a full reload of segments manually (most easily right now by toggling the auto refresh button on and off).
Ideally, it can do this in a lightweight way - iterating through existing meshes and updating their material slot, vs completely regenerating geometry.

Please describe steps to recreate problem. I changed the road texture several times and it always updated instantly.
Steps that I followed:

Duplicate road_texture.png, invert colors, and rename new image to "road_texture_inverted.png"
Select RoadNetwork in Scene dock
Select "Material Resource" in Inspector dock
Expand "Albedo" to expose "Texture"
Drag/Drop road_texture_inverted.png or road_texture.png from FileSystem dock into "Texture" slot in Inspector dock
Outcome: New image is displayed on all Segments in 3D View

Also tried:

Duplicate road_texture.material and rename to road_texture2.material
Change albedo texture to road_texture_inverted.png in new material
Select RoadNetwork in Scene dock
Drag/Drop road_texture.material or road_texture2.material from FileSystem dock into "Material Resource" slot in Inspector dock
Outcome: New material is displayed on all Segments in 3D View

Hm, I've retried this myself now and can no longer replicate it. It must have been resolved with some of the other updates we made around how and when refreshing works. I checked out version 0.2.0 for comparison, it was definitely an issue still then, and now is not. Even if I drag and drop a new material onto the network slot now, it immediately updates the road. Closing this issue, apologies for that!


Boot failure on 05/05

Describe the bug
I'm using bcachefs and it fails to boot on 05/05 (latest as of right now). Stage 1 fails. Other generations boot fine.
Steps To Reproduce
Steps to reproduce the behavior:

update nixos

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.9.0-rc6, NixOS, 24.05 (Uakari), 24.05.20240503.e96601e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/store/3gcgx970vsz0h89kjm3nwixb74b03g7r-source`

Add a :+1: reaction to issues you find important.

❯ nix store diff-closures /nix/var/nix/profiles/system-72-link /nix/var/nix/profiles/system-7
5-link
bcachefs-tools: 1.4.1 → 1.7.0, -1554.5 KiB
btrfs-progs: 6.8 → 6.8.1
crun: 1.14.4 → 1.15, +14.5 KiB
extra: -903.2 KiB
fwupd: 1.9.18 → 1.9.19
initrd-linux: -345.6 KiB
javascript-grammar: ∅ → 0.0.0+rev=fff4560, +635.9 KiB
lua: ∅ → 5.1.5, +1004.3 KiB
lua5.1-luassert: ∅ → 1.9.0-1, +118.5 KiB
lua5.1-say-scm: ∅ → 1, +10.7 KiB
nix-grammar: ∅ → 0.0.0+rev=b3cda61, +106.2 KiB
nixos-system-nixos: 24.05.20240503.e96601e → 24.05.20240505.9f5a6d7
notmuch: +105.5 KiB
notmuch-vim: ∅ → ε
openfortivpn: 1.21.0 → 1.22.0
ruby3.1-date: ∅ → 3.3.4, +937.5 KiB
ruby3.1-mail: ∅ → 2.8.1, +3731.7 KiB
ruby3.1-mini_mime: ∅ → 1.1.5, +241.1 KiB
ruby3.1-net-imap: ∅ → 0.4.10, +594.4 KiB
ruby3.1-net-pop: ∅ → 0.1.2, +40.7 KiB
ruby3.1-net-protocol: ∅ → 0.2.2, +25.6 KiB
ruby3.1-net-smtp: ∅ → 0.5.0, +55.7 KiB
ruby3.1-timeout: ∅ → 0.4.1, +15.8 KiB
source: +121.4 KiB
typescript-grammar: ∅ → 0.0.0+rev=b00b8eb, +2285.3 KiB
vimplugin-gen.nvim: ∅ → 2024-05-03, +27.1 KiB
vimplugin-lua5.1-plenary.nvim-scm: ∅ → 1-unstable-2024-03-25, +443.6 KiB
vimplugin-nvim-treesitter: ∅ → 2024-04-20, +1860.1 KiB
vimplugin-treesitter-grammar: ∅ → ε
vte: 0.76.0 → 0.76.1
zfs-user: 2.2.3 → 2.2.4, +13.7 KiB

I believe it's an issue with the new bcachefs-tools

@davidak
@johnrtitor
@Madouura

Are you using systemd in initrd? (boot.initrd.systemd.enable)
Bcachefs as root won't boot with that.
Please provide logs so we can help further.

I'm not using boot.initrd.systemd.enable. Where do you want logs from?

The bcachefs error messages you see on the screen are normal though. You can see them by booting in a "working" generation, and running journalctl -b | grep bcachefs | less.
Also does this happen on 6.8 kernel?

I get the same error message on 6.8.9 about stage 1 failing

I am on 6.8.9 kernel and I have no trouble booting. Could be related to your specific configuration.
I'll recommend pinning bcachefs-tools to the previous version like this, and use an overlay to fetch system bcachefs-tools from that nixpkgs commit.

I'm using encryption on bcachefs so that could be it. I'll try using an overlay from that commit and see if it boots or not

I pinned bcachefs-tools to nixpkgs/668834f72c7a082bdb823d1367a9abea15ebfcad and it boots

Few tests I would like you to run, does it work using the latest commit from this https://github.com/koverstreet/bcachefs-tools
It has a flake, so you can use bcachefs-tools.packages.x86_64-linux.bcachefs after adding the flake in your flake.nix.
If it works, I'd like you to test the v1.7.0 branch.

The latest commit from master doesn't boot. I'll try v1.7.0

Could you share part of your configuration related to disks and encryption?
Just so we are clear you have been using the latest rc kernel between these tests?
Pinging @koverstreet for his input.

Yes I've been using rc6 for these tests. This is my entire configuration as of right now: https://github.com/codebam/nixos

This doesn't seem to be a packaging problem, and I don't see anything weird per say in your NixOS configuration.
But I'll have to redirect you to their GitHub or r/bcachefs as Kent is pretty active over there on Reddit.

I can confirm this happening on my machine updating today. Sadly lacking time to debug further but gonna watch this and possible upstream issues for when I've got more time.
Updated 6.8.8->6.8.9 kernel, nixos-unstable, also with bcache root fs with enabled encryption.
Possibly relevant configuration:
 boot.kernelPackages = pkgs.linuxPackages_latest;

  fileSystems."/" =
    { device = "UUID=...";
      fsType = "bcachefs";
      options = [ "compression=lz4" ];
    };

Note: Issue title should be updated to like "booting with bcachefs compression on is broken".

It looks like an issue with bcachefs-tools version 1.6.4 forward. Would it make sense to either downgrade the nixpkgs version to 1.6.3 or mark the package broken?

I am inclined to downgrade the version to 1.6.4 for 24.05 release unless a fix is provided in upstream within the NixOS 24.05 merge window (4th week of May).
Though, this only affects few chunk of users who are using this experimental filesystem, with encryption on.
Those who are facing this bug, please report it to the with logs in https://github.com/koverstreet/bcachefs-tools/issues/261. This will help Kent fix this faster.

@JohnRTitor: What kernel version is 24.05 expected to ship with?  I ask because the 1.6.x series of bcachefs-tools should match bcachefs disk format 1.6 (kernel 6.8.x); whereas 1.7.x matches the disk format in 6.9.x.
I know there's been thought put into making the tools cross-compatible so everything should be fine with version mismatches?  But at the same time, unless we're planning to take a 6.9 series kernel I'm not sure there's a pressing need to bump the tools to 1.7.x quite yet.

@JohnRTitor: What kernel version is 24.05 expected to ship with?

https://github.com/koverstreet/bcachefs-tools/issues/261#issuecomment-2103297285
TLDR: 6.9, I'm tracking this, and will downgrade at the end of the merge window for 24.05, if it comes to it.

Why wasn't this caught by bcachefsEncrypted?
https://github.com/NixOS/nixpkgs/blob/42a5d29b6f94f3f12ca13295cc10ce91d0a21c35/nixos/tests/installer.nix#L1161-L1202


browser.assert.url expected/actual values are changed

     AssertionError [ERR_ASSERTION]: Expected url to be "http://localhost:8001/a", "http://localhost:8001/b" found
      + expected - actual

      -http://localhost:8001/report/a
      +http://localhost:8001/report/b

Check if this problem happens with other assertions as well

Add tests for this


chef_client_config: ensure config property directories exist

Description
create the various directories defined in the properties if they are defined and don't exist
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

Signed-off by: Corey Hemminger<EMAIL_ADDRESS>

@Stromweld Can you change one of the properties in https://github.com/chef/chef/blob/main/kitchen-tests/cookbooks/end_to_end/recipes/_chef_client_config.rb#L1 so we can get a bit of testing for this in the kitchen tests?

@tas50 is this what you're looking for? Looks like tests are passing but the 1 centos6 had an error connecting to a yum repo during it's test run.

Thanks @Stromweld


[UI] Add disabled styling for buttons on :disabled attribute

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior

For all components (dropdowns, datagrid overflow menus etc) that use buttons inside of them, disabled styles should work just on :disabled attribute on the button.
Actual behavior

To disable a .dropdown-item, users have to add both .disabled class and the :disabled attribute on the button.
Reproduction of behavior

https://plnkr.co/edit/nWP7qu?p=preview
Environment details

Angular version: 2.0.X

Clarity version:

OS and version: All

Browser: [all]

Thanks for filing this issue.
currently, I add following styles to my top level component as a temporary shim
:host /deep/ .dropdown-item:disabled {
    cursor: not-allowed;
    opacity: 0.4;
    user-select: none;
}

Hope this comment will help those who also hit this.


Create single planning phase

The major problem we have right now, is that query execution model is not aware of the whole context of execute operation. This is particularly irritating in scenarios such as i.e. constructing SQL queries based on incoming GraphQL query.
Right now going deep into nested relations will either require using lazy collections all the way down (like IQueryable, which is not the case for integration with Relay.js connection data structures) or will cause N+1 selects in resulting SQL queries.
One of the ideas here is to introduce query planning (as presented in https://github.com/graphql/graphql-js/pull/304 ) before starting execution phase.
Why?
Having explicit execution plan before starting the value resolution process gives us some advantages:

This could help us, as we have the whole plan prepared up-front and we can make some contextual decisions (such as construction of SQL queries) based on that data.
It would be useful in pub/sub scenarios as we could potentially cache execution plans instead of queries and execute them directly, once new value needs to be published. This way we don't need to repeatedly reevaluate whole document AST into result set.
Potentially since we've got raw execution tree, we could optimize it.

Why not Document AST?
Well, there are some problems with document AST:

It's doesn't preserve any relations to actually executed tree. So you'll need to map it onto schema anyway using tree traversal.
It can contain fragments - fragments are not represented in schema. Moreover there are multiple tricks that can be done over over them, that should be optimized in resulting set, ie.:

query {
    users {
        ... userName
        ... userAge
    }
}

fragment userName on User { name }
fragment userName on User { age }

should not iterate over users twice, instead it should be optimized to:
query {
    users {
        name
        age
    }
}

How
We need to introduce an execution phase, in a very raw form the proposal would be:
type Reduce = FieldResolveContext -> obj -> obj
type ExecutionPlan =
    // reducer for leaf types, such as scalars and enums
    | ReduceLeaf * Reduce
    // reducer for selection sets materialized over output object type
    | ReduceSelection of (string * ExecutionPlan) []
    // reducer for list types
    | ReduceCollection of ExecutionPlan
    // reducer for union and interface types
    | ReduceAbstraction of Map<string, ExecutionPlan>

Execution phase itself should be splitted into two: 1) preparation of execution plan 2) evaluating execution plan. Additionally it should be able to extract execution plan separatelly (as mentioned in first two points of "Why?" paragraph.
Notes:

How to resolve condintioanlly included/excluded fields without introducing too much dynamism in result set (right now we have pretty good object allocation story thanks to reducing allocations of dynamic data structures like lists in favor of static arrays).

Closed by #56


Data submissions - when table is refreshed with a new task, buttons do not work

@abennici can you have a look this?


[AIRFLOW-2770] kubernetes: add support for dag folder in the docker i…

…mage
Make sure you have checked all steps below.
Jira

[ ] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2770
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description
this change will introduce a new config in kubernetes_executor, dags_in_docker, which means the dags already build in the docker image. thus doesn't need to mount a volume or sync the dags use git sync. the worker will search the dags from the dags_folder by default.

[ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[ ] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3683 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3683      +/-   ##
==========================================
+ Coverage   77.52%   77.53%   +<.01%
==========================================
  Files         205      205
  Lines       15771    15771
==========================================
+ Hits        12227    12228       +1
+ Misses       3544     3543       -1

Impacted Files
Coverage Δ

airflow/models.py
88.58% <0%> (+0.04%)
:arrow_up:

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 a4b9aa3...9401914. Read the comment docs.

@dimberman

Also fixes https://issues.apache.org/jira/browse/AIRFLOW-2728

anyone can help to review and merge this change? thanks.

@yeluolei Also apologies for the delay. For the last 2X days the CI build has been broken for the kubernetes builds (it has been defaulting back to the non-k8s tests) so we've basically been running blind/unable to properly test any k8s stuff. If you rebase the tests should work now.
Also, could you please put in some form of testing for this in the kubernetes CI?

@odracci please merge change #3770 first, I will try to rebase this commit if needed. if you can add this feature in your change, it will be better. thanks!

@yeluolei @Fokko @odracci can we merge this first since #3770 seems to be having some issues?

also @kaxil  with there being an open issue on the git mode, this would be pretty necessary/simplify a lot of small/medium sized builds for 1.10.2

thanks. I trust @dimberman's review on this k8s pr. Thanks @yeluolei .

@dimberman Definitely, I have added 1.10.2 tag on Jira. Will cherry-pick this on weekends as it has transitive dependencies on other commits

@yeluolei @dimberman , it seems the integration for airflow k8s starts to fail with this change (CI log: https://travis-ci.org/apache/incubator-airflow/jobs/467296257). Do you know if it is related or it is a transient error?

It's super weird. I noticed that too but the tests were passing when I checked this branch. Especially noticeable that the jobs are stuck in queued (which tell me the executor is not launching anything). I'm at Kubecon until tomorrow but should be around this weekend. Should we revert and I'll investigate further?
I apologize for the inconvenience. One of my short/medium term plans is to improve the test coverage for the k8s executor to catch these problems earlier.

thanks @dimberman , how about you do some investigations over the weekend? If you couldn't figure out, we could then revert the pr next week.

I'd like it if we reverted this before the weekend - it's not great to see tests failing on other PRs and I feel uneasy about "merging those PRs anyway".

@ashb  @dimberman revert branch is created(https://github.com/apache/incubator-airflow/pull/4318).  @dimberman , we could repush the change once the CI is fixed.

PR #4319 fixes the issues with failing CI tests from this PR.
I do have one concern with the fix, which may require further changes, called out here: https://github.com/apache/incubator-airflow/pull/4319#discussion_r241518434


Uploading dataset RDF is broken

Filling out the Uploader form for a dataset results in:

type, name and description are of course filled out.
format_version is not an option (as it should be set by the uploader)

after removing the colon from the name it fails slightly better:

the warning "loading future dataset RDF 0.4.8 as latest known" is caused by me uploading an rdf.yaml with this future format version (I wrongly specified the current model RDF format version).
What we can improve here is to show the additional rdf.yaml fields that were present in the uploaded rdf.yaml

@FynnBe Do you know what went wrong here?


Rejuvenation - Encounter Table missing for eastern chrysalis courtyard

apparently contains Pidgeotto, Herdier, Ariados

Closed in new PR


Include AWS Community Day, Chennai

Details of the conference: AWS Community Day, Chennai

Website: https://communityday.awsugchn.in
Date: 10th Aug, 2019
Venue: Hilton, Chennai
Description: The inaugural community day of AWS at Chennai

This repo only accepts conferences which have CFPs. I can't find a link to the CFP on the websites, but if you can paste a link for CFPs here (I might have missed it!), I'll glady merge it. :smile:

I think it is here: https://awsugcgn.typeform.com/to/kRG8ez

Closing since the PR needed a rebase but the conferences have already been over. Thanks anyway, @roommen!


Configurable update time option

Would be nice to have this option, because i don't start my pc at 6am so with -StartWhenAvailable used it will start at user logon even though i've not used -UpdatesAtLogon option when installing.

You can still edit the scheduled task once set. WAU update won't change any settings on the scheduled task.

Not stale

Not stale.

Not stale

@Romanitho thanks!

Let us know if it helps and if it works as expected 😊

Tested with -UpdatesAtTime 11AM, works as expected.


Fix example

Also, the docs mentioned in the README should be updated as it points to an older version.
But I don't see any CI for docs?

We should make this into a standard documenter documentation instead.

While you're at it, can you add a section that documents the interface, i.e. how to interact with an interpolation i(t) but also calculate derivatives and integrals? Then I think we're good to go.

When this gets merged in. Does this go into the SciML docs -> dev tools -> 3rd party num utils?

I would treat it as non-third party. It's really weird it's not in SciML.

Any reason we can't move this to SciML?

It should.


Simultaneous invocation can cause inconclusive results

In the function wait_for_workflow_to_finish we are getting the last/latest workflow run...
Imagine we have Repo A, B & C. A & C both invoke the workflow from B let's say almost @ the same time. With the current logic we will never know which run was initiated by which Repo.

Thanks for opening the issue. You are right, there is the potential for A pulling in the results from trigger of C. In terms of solution, we can capture the run_id when calling the trigger and watch till that specific run finishes.

Hey, thanks for the reply. I don't think the workflow dispatch returns a run_id so it might not be possible to wait for a specific run without knowing the run_id...
How I have solve this before is by waiting for a check_run...
The workflow name is a constant and cannot be changed but the job name can be dynamic... So u can pass some value to the workflow dispatch and concatenate the job name with it... Then u poll/wait for a check_run with that specific name i.e. job_name+input_value... Input could be a SHA so the job name will always be unique...

I think I've encountered something similar, but instead a race condition every so often the workflow ID returned matches a previously run job.
For instance, I was testing a workflow_dispatch yesterday that failed. I made modifications today and ran a new dispatch job which was successful when you view the dispatched repository, though the calling job says it failed and shows the workflow ID from yesterday's failed job. It's really weird.
Notice the workflow ID and triggered time stamp (and that it was triggered by a push):

Now here's the job run about 30 minutes ago (workflow ID matches:

Then there's the actual job that ran which was successful:

I actually saw this happed a few days ago and ignored it as some space anomaly, but now I feel as though I can't trust this. I don't know when it will give me a false negative/positive.

@djthornton1212 we need this PR to mitigate some of these issues https://github.com/convictional/trigger-workflow-and-wait/pull/37

Assuming this has been cleared :)


Update ru.coffee

Some more translations.

Coverage increased (+0.2%) to 56.805% when pulling cba66ee26e3809825e05afd600e4f7a5b00ac8dd on mithmith:patch-2 into e9b1c420e2771c052d76b647aef9cd21f1ce4d1d on codecombat:master.

Thank you!


Is there a way to show explain_local without resetting the index?

Hey again,
I'm looking at some explain_local for this model I'm working on and wondering if there's a way to get it to show without resetting the index. Mainly because the indexes are important.
ebm_local = ebm.explain_local(X, y) # These have indexes that mean something

show(ebm_local) # Shows 0,1,2,3,4 implying the indexes were reset

Thanks!

Hi @hexgnu,
Good idea! We reset the index right now for engineering simplicity, but we can look into preserving this in the future. Nice to hear that this would be useful for you!
-InterpretML Team

+1! The use case is pretty simple: I'm using interpretML to classify some datapoints, interpret the decisions of the model and take business decisions based on that. Since it resets the index I struggle going back to check with datapoint a certain prediction was for.
Have you done any progress on this?


Dropdown list cannot be selected

@camohub if the list contains dropdown list, we cannot select the option from the dropdown list,
below is the example:
https://jsfiddle.net/haiquan180/szmjhjok/
input also doesn't work.
could you help me? i really need dropdown, input to work.

You have at least two mistakes in the code. Look at documentation for the structure of items(there is one div not two on the first level) and also for ignoreClass option.


Optimized rendering performance for SoText2

Original pull request by Mario Koerner (Bitbucket: Renreok, GitHub: Renreok).

This pull request provides a performance optimized version of the SoText2 node.
The original implementation uses at least two GL calls per glyph: One call to glRasterPos3f() and one call to glDrawPixels() (for non-monochrome
fonts) or glBitmap (for monochrome fonts). These many GL calls are very inefficient with modern graphics cards and drivers, independent of whether
they are invoked directly or through a display list (using a SoSeparator with render caching enabled).
My optimization first constructs one bitmap with the whole text in main memory and displays it using a single set of GL calls, which turns out
to be much more efficient. So far my implementation only optimizes non-monochrome text, because this is the more important case for me.
Monochrome text still uses the old approach.
I used a SoText2 node with the first four strophes of Goethe's poem "Erlkoenig" with "Times New Roman" font in size 18 to
measure the performance on two different machines running Windows 10:

[Laptop] Intel i5-3317U CPU (2.38 GHz) with Intel HD Graphics 4000 onboard
[Workstation] Intel Xeon E5-1650 v3 (3.57 GHz) with Nvidia Quadro K5200

The results are as follows:

Version
[Laptop]
[Workstation]

Original version without render caching
57 ms
3.1 ms

Original version with render caching
56 ms
2.6 ms

Optimized version without render caching
1.7 ms
0.4 ms

Optimized version with render caching
1.2 ms
0.2 ms

The rendering results with the optimized version are similar, but not binary equal with the original version. In my optimized version I always
round the text position to align it with the pixel grid, because interpolated text always looks ugly, and I don't see a reason not to round it.
If I modify the original version to do the same rounding and compare the result with my optimized version, then the result is binay equal in many
scenarios.
However, there are still a few differences in some scenarios, but I think they are acceptable:

text with CENTER justification can be shifted by one pixel in horizontal direction, because my implementation rounds twice, once to draw
the glyph into the bitmap and once more to draw the bitmap on the screen
the "greater than 30%" alpha function is only applied to the whole text in my implementation, while it is applied to every glyph in
the original version. This can cause small differences in pixel values where the glyph bitmaps of two glyphs overlap in a non-trivial manner
(i.e. both are non-zero at a certain position)
order of alpha blending is different: while my implementation first blends all glyphs into one bitmap, the original implementation blended
every glyph directly over the background. Again this can make a few pixels appear slightly different where glyph bitmaps overlap in non-trivial
manner.

I found one more issue which is wrong in my implementation, but was also wrong in the original implementation. In some languages
(e.g. arabic) text should be printed right to left, but Coin always prints it left to right. Since this bug already existed, I did not fix
it with this pull request.
I have my version running in my application which dispays a lot of text for some time now. So far it seems to be stable, but it would
be nice if someone could try it in another application.

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

Sorry I just pulled pull request #253, which I think conflicts with this one. While you resolve the conflict, could you keep an eye on issue #126 in order not to regress that?
Unless @chrvetter wants to review this, I think you can just merge this when you feel confident. You have done a thorough job evaluating and the performance increase is worth it.

Original comment by Mario Koerner (Bitbucket: Renreok, GitHub: Renreok).

The images in issue #126 are not very meaningful, because it seems that the text was upscaled by a factor of about 3 (assuming that a font size of 16 was used for rendering), but with different Interpolation modes. @yangxy0723, @chrvetter maybe you can comment on how those Images were created.
However, I also do not understand .3 threshold for text rendering, and also created some Images with font "Times New Roman", size 16:

Even though I don't see a big difference, I would say that the right result is slightly better and will update my pull request accordingly.

Original comment by Xiaoyong Yang (Bitbucket: yangxy0723, GitHub: yangxy0723).

The original text was rendered by xipbuilder.  I did cut-paste the string rendering images using SnagIt.

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

@Renreok Do you still want to update this PR? Otherwise I'd say merge it, so we can merge the CMake branch into default. This PR is the only one remaining for this branch. We can restore pull request #253 in default if needed.

Original comment by Mario Koerner (Bitbucket: Renreok, GitHub: Renreok).

I will merge it now.
I already merged pull request #253 into this branch. However, pull request #253 is causing some problems in my application. If e.g. a shader is active that does not handle alpha blending,
then the text will now always be rendered with black background. Before the merge of pull request #253 the transparent pixels were simply rejected.
But since this is not directly related to the performance optimization, I'll merge my pull request now. We can fix that after the merge to the default branch.


prometheus-remote-write dashboard not importable in grafana

the prometheus-remote-write dashboard fails to load in Grafana. with the following error:
Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object with keys {type%2C uid} for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
changing
"current": {
"text": {
"selected": true,
"text": "All",
"value": "$__all"
},
"value": {
"selected": true,
"text": "All",
"value": "$__all"
}
},
to: makes it work again:
"current": {
"selected": true,
"text": "All",
"value": "$__all"
}

Successfully imported the latest dashboard prometheus-remote-write dashboard that had been updated 2 weeks ago to Grafana 11.3.


Create page and add its' link to the Repo description

Link to add: https://pug10rd.github.io/resume/

Can I get assigned and tell me how to start ?


i18n: p12s cn translations for white flame baits delay

It is very tricky to translate those 'time state' words, so that I think these translated words need to be reviewed. Also 3 secs, 6 secs and 9 secs can make me confused in game so thats not a very good option?

@YuzukiTsuru any opinions? I have tried other translations like 等待上一组 => 引导激光 (wait for last bait => bait laser in English), but it makes tts too long in this fast-paced mechanic and may not distinguish those 5 states as well.

Just updated the translations, I think it's better and more obvious to differentiate between those words now.

Sorry that this was tricky to translate. Even in English it's kind of ambiguous, but it's still helpful information too so I didn't want to not include it. Thanks!!

Sorry that this was tricky to translate. Even in English it's kind of ambiguous, but it's still helpful information too so I didn't want to not include it. Thanks!!

It's okay! This information also helps me a lot during my game play. Difficulty in translating this is how to let people know what those words are talking about. Thanks for the reply btw!


[BUG] PVC can be deleted mistakenly when reading stale deletionTimestamp information

Description
We find that in a HA k8s cluster, cass-operator could mistakenly delete the PVC of the cassandra pod after cass-operator experiencing a restart. After diagnosis and inspection, we find it is caused by potential staleness in some of the apiserver.
More concretely, if cass-operator receives a stale update event from an apiserver saying "CassandraDatacenter has non-nil deletion timestamp", the controller will delete the PVCs returned by listPVCs, and listPVCs will list PVCs using the name(space) instead of the UID. Note that the stale event actually comes from the deletion of a previous CassandraDatacenter sharing the same name (but with a different UID) as the currently running one, so the PVC of the existing CassandraDatacenter will be listed and deleted mistakenly.
One potential approach to fix this is to label each PVC the UID of the CassandraDatacenter when creating them, and list the PVC using the UID of the CassandraDatacenter in listPVCs to ensure that we always delete the right PVC.
Reproduction
We list concrete reproduction steps in a HA cluster as below:

Create a CassandraDatacenter cdc. PVC will be created in the cluster.
Delete cdc. Apiserver1 will send the update events with a non-nil deletion timestamp to the controller and the controller will trigger deletePVCs() to delete related PVC. Meanwhile, apiserver2 is partitioned so its watch cache stops at the moment that cdc is tagged with a deletion timestamp.
Create the CassandraDatacenter with the same name cdc again. Now the CassandraDatacenter gets back with a different uid, so as its PVC. However, apiserver2 still holds the stale view that cdc has a non-nil deletion timestamp and is about to be deleted.
The controller restarts after a node failure and talks to the stale apiserver2. Reading the stale update events from apiserver2 that cdc has a deletion timestamp, the controller lists all the PVC belonging to the currently running cdc (as mentioned above) and deletes them all.

Fix
We are willing to help fix this bug by issuing a PR.
As mentioned above, the bug can be avoided by tagging each PVC with the UID of the CassandraDatacenter and listing PVC with UID. Each CassandraDatacenter will always have a different UID even with the same name. So in this case the PVCs belonging to the newly created CassandraDatacenter will not be deleted by the stale events of the old one.

Hi @srteam2020
Thanks for the detailed issue. The fix you describe sounds reasonable.
Can the bug be reproduced consistently? (I assume the answer is no)
I would like to be able to reproduce the bug in order to properly verify the fix.

Hello @jsanda Thank you for the reply.
We send a PR for this https://github.com/datastax/cass-operator/pull/416

Can the bug be reproduced consistently? (I assume the answer is no)

We are currently developing a tool to detect/reproduce the bugs that require intricate timing to manifest. Our tool can consistently detect/reproduce this bug. The tool is still in development so we are not able to release it yet. I will definitely let you know when we open the tool.

I've gone ahead and recreated this issue at https://github.com/k8ssandra/cass-operator/issues/118.
Let's discuss how to get the PR re-created there as well to address it.
Thanks!


For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 378ead1:
:clock10: Preparing: average preparing time is 3 min(s) 13 sec(s)

OPS Build status updates of commit 378ead1:
:clock10: Incremental building: average incremental building time is 53 min(s) 59 sec(s)

OPS Build status updates of commit 378ead1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/showmodal-property.md
:white_check_mark:Succeeded
View

Library-Reference/Concepts/what-s-new-for-vba-in-office-2019.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix bug/typo for Dropout using axes

Description
Fix bug for a recent PR https://github.com/apache/incubator-mxnet/pull/9931
Checklist
Essentials

[ ] Passed code style checking (make lint)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@szha this should fix the problem of dropout using axes.

will create another one.


64bits integer property are lost

Some code to reproduce:
Create the class with rowid as an integer:

client = weaviate.Client("http://localhost:8080") # or another location where your Weaviate instance is running

schema = {
  "classes": [
    {
      "class": "Object",
      "vectorizer": "none",
      "properties": [
        {
          "dataType": [ "int" ],
          "name": "rowid"
        }
      ]
    }
  ]
}

print(client.schema.create(schema))

Add some content:
import requests

doc1 = {
    "class": "Object",
    "vector": [1.0, 2.0],
    "properties": { "rowid": 16040291 }
}
doc2 = {
    "class": "Object",
    "vector": [3.0, 4.0],
    "properties": { "rowid":<PHONE_NUMBER>751626752  }
}
data = { 'objects': [doc1, doc2] }
result = requests.post('http://localhost:8080/v1/batch/objects', json=data)
print(result.content)

b'[{"class":"Object","creationTimeUnix":1619548348443,"id":"1bf45658-037b-44db-a4d6-b338d214301b","properties":{"rowid":16040291},"vector":[1,2],"deprecations":null,"result":{}},{"class":"Object","creationTimeUnix":1619548348442,"id":"ae9aff5f-59ec-4a9f-86d8-cc48443b59dc","properties":{"rowid":1604029199751626752},"vector":[3,4],"deprecations":null,"result":{}}]\n'

Query the vector:
near_vec = {"vector": [1.0, 3.0] }

res = client \
    .query \
    .get("Object", ["rowid", "_additional {certainty}"]) \
    .with_near_vector(near_vec) \
    .with_limit(5) \
    .do()

results = res["data"]["Get"]["Object"]

for result in results:
    print(result)

will output:

{'_additional': {'certainty': 0.99497473}, 'rowid': 16040291}
{'_additional': {'certainty': 0.97434163}, 'rowid': None}

Thanks for discovering this issue. We'll investigate and get back to you.

I can confirm this is a bug in Weaviate itself, not in the client used. The long int value is present in the REST API, but not in GraphQL. Will investigate.

What we've learned so far:

The GraphQL Spec defines int as int32 and explicitly does not support int64
In line with the spec the graphql-go implementation ignores any int64 value that is outside the bounds of an int32. It simply returns nil in that case, which translates to the python client's None value, you're seeing.
It is possible to add custom Scalar Types to GraphQL, but we have yet to check what effect that has on standard-tooling which might not understand those custom types
A short-term workaround that I saw mentioned in many GraphQL issues is to use a string instead.

I can't seem to get this to work with pure REST API either:
curl -X POST -H 'Content-Type: application/json' -d '{
      "class": "Article",
      "properties": {
          "title": "Large int64",
          "wordCount":<PHONE_NUMBER>854775807
      }
  }' http://localhost:8080/v1/objects
{"class":"Article","creationTimeUnix":1669085839830,"id":"dc420c7f-8962-4ddf-a587-8ee5a873b1c2","lastUpdateTimeUnix":1669085839830,"properties":{"title":"Large int64","wordCount":9223372036854775807}}

curl http://localhost:8080/v1/objects/dc420c7f-8962-4ddf-a587-8ee5a873b1c2 | jq
{
  "class": "Article",
  "creationTimeUnix":<PHONE_NUMBER>830,
  "id": "dc420c7f-8962-4ddf-a587-8ee5a873b1c2",
  "lastUpdateTimeUnix":<PHONE_NUMBER>830,
  "properties": {
    "title": "Large int64",
    "wordCount":<PHONE_NUMBER>854776000
  },
  "vectorWeights": null
}

notice how storing<PHONE_NUMBER>854775807 became<PHONE_NUMBER>854776000 after doing a get REST API request. I suspect int isn't really stored as an int64 or somewhere along the road it becomes an float64?
This is my schema:
{
        "class": "Article",
        "description": "A description of this class, in this case, it is about authors",
        "properties": [
            {
                "dataType": [
                    "string"
                ],
                "name": "title"
            },
            {
                "dataType": [
                    "int"
                ],
                "name": "wordCount"
            },
            {
                "dataType": [
                    "string"
                ],
                "name": "content"
            }
        ]
    }

Thank @samos123 for reporting the issue and a reproducible example.
I can confirm that weaviate returns rounded numbers and your suspicion is correct. While int64 values are stored correctly, it is reading/unmarshalling process that converts them to float64. Those converted values are then marshalled (ending up being rounded) and send back in the responses.


chore: add issue comment github actions

For #373

It looks like very useful. But would you mind giving us a few examples of those projects which are using it?

Sure.

https://github.com/envoyproxy/gateway/blob/main/.github/workflows/issue-comment.yaml
https://github.com/kubernetes/kubernetes/issues/124407#issuecomment-2066737103

istio & k8s etc...

@LinuxSuRen https://github.com/yuluo-yx/deigmata-paideias/issues/2


[Bug] The autocompletion for prototype

Repeatable Link: https://ternjs.net/doc/demo/index.html#simple
Revision: 0.24.1
// Use ctrl-space to complete something
co
document.body.a

// Put the cursor in or after an expression, press ctrl-i to
// find its type

var foo = ["array", "of", "strings"]
var bar = foo.slice(0, 2).join("").split("a")[0]

// Works for locally defined types too.

function CTor() { this.size = 10 }
CTor.prototype.hallo = "hallo"
CTor.prototype.//====BUG====
CTor.prototype.//====NO BUG AFTER SECOND PROPERTY DEFINED====
var baz = new CTor
baz.

// You can press ctrl-q when the cursor is on a variable
// name to rename it. Try it with CTor...

// When the cursor is in an argument list, the arguments
// are shown below the editor.

[1].reduce(  )

Bug: (refer to the ====BUG==== tag in the code above)
When trying to do the autocompletion for defining the second property of the prototype, it always automatically insert the name of the first property that's defined. But after the second property is defined, this bug seems not going to happen anymore.

This is definitely not a bug in Tern, and probably not a bug generally. If you're planning to type a new property name, don't activate autocompletion. Tern correctly reports a single property here, and CodeMirror's autocompletion completes those immediately by default.

Still wondering if this is not a bug, why it wouldn’t happen when defining the first property or the third property and so on? Why it only happens on the second property? Thanks

As I mentioned, CodeMirror's autocompletion will by default complete right away when there's only one option. That's what you're seeing here.


Add to admin tasks

Proposal
Add manage task to admin tasks to include env variable so that testing/deploying is much simpler.

@sloria Improved, but couldn't find anything on how to handle a list of args since invoke can handle running commands sequentially on the same line.

@sloria Moved, good?

Looks good.
Re: the manage command, I think what you had before--a single, required argument for the command string--was preferred. You would just need to make sure you use quotes around the command.
inv manage 'runserver -p 9876'

That removes the need for the target argument, and allows any number of additional arguments to be passed to the management. commands.

I'll make the above change when I merge.

Sounds good. Thanks. (It will be inv admin.manage though ;)


PR - lowercase except values in star()

resolves https://github.com/dbt-labs/dbt-utils/issues/402
This is a:

[x] bug fix PR with no breaking changes — please ensure the base branch is master
[ ] new functionality — please ensure the base branch is the latest dev/ branch
[ ] a breaking change — please ensure the base branch is the latest dev/ branch

Description & motivation

This PR allows a user to put their except values in whatever case they want when calling them within dbt_utils.star()
{{ dbt_utils.star(from=ref('my_model', except=["col_a","col_b"]) == {{ dbt_utils.star(from=ref('my_model', except=["COL_A","Col_B"])
Checklist

[x] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[ ] BigQuery
[ ] Postgres
[ ] Redshift
[x] Snowflake

[x] I have "dispatched" any new macro(s) so non-core adapters can also use them (e.g. the star() source)
[x] I have updated the README.md (if applicable)
[x] I have added tests & descriptions to my models (and macros if applicable)
[x] I have added an entry to CHANGELOG.md

I recently ran into something similar when using include in union_relations - my lowercase field names were excluded from not matching the uppercase version.

Hi Reid - thank you so much for the fantastic PR!! I'm going to remove the comment that's no longer relevant than get this merged.

I think there's a bug here. I just upgraded and have a column missing.
Does except|lower convert a list to a string?
Before, I think something like this was running for me:
'seo_path' not in ['keywords', 'meta_description', 'seo_path_segment_keywords'] (True)
But now I think it may run as:
'seo_path' not in "['keywords', 'meta_description', 'seo_path_segment_keywords']" (False)
I was going to spend some more time looking at this tomorrow before filing an issue and repo as I'm pretty new to Python and Jinja, but wanted to share now in case this already sounds like this is the issue.

I think there's a bug here. I just upgraded and have a column missing.

We're noticing this too. I've written it up here.

Thanks for the heads up @wuservices @EPNickBosma
Can you check out https://github.com/dbt-labs/dbt-utils/pull/418 and let me know if this fixes the error you are seeing?


Attempt to fix Python on Travis being too old.

Neither Travis or AppVeyor passed yet. That's a pretty risky merge.

And it was indeed because it broke AppVeyor!


[Bug] fail to run docker-compose up

Bug report
fail to run docker-compose up
Relevant log output
2023-06-18 14:29:13 example-subgraph-graph-node-1  | Jun 18 06:29:13.647 INFO Pool successfully connected to Postgres, pool: main, shard: primary, component: Store
2023-06-18 14:29:13 example-subgraph-graph-node-1  | Jun 18 06:29:13.795 INFO Setting up fdw, pool: main, shard: primary, component: ConnectionPool
2023-06-18 14:29:13 example-subgraph-graph-node-1  | Jun 18 06:29:13.837 INFO Running migrations, pool: main, shard: primary, component: ConnectionPool
2023-06-18 14:29:13 example-subgraph-graph-node-1  | Jun 18 06:29:13.841 INFO Migrations finished, pool: main, shard: primary, component: ConnectionPool
2023-06-18 14:29:13 example-subgraph-graph-node-1  | Jun 18 06:29:13.886 CRIT Database does not use C locale. Please check the graph-node documentation for how to set up the database locale, error: database collation is `en_US.utf8` but must be `C`, pool: main, shard: primary, component: ConnectionPool
2023-06-18 14:29:13 example-subgraph-graph-node-1  | thread 'tokio-runtime-worker' panicked at 'Database does not use C locale. Please check the graph-node documentation for how to set up the database locale: database collation is `en_US.utf8` but must be `C`', store/postgres/src/connection_pool.rs:988:13
2023-06-18 14:29:13 example-subgraph-graph-node-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2023-06-18 14:29:13 example-subgraph-graph-node-1  | thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: JoinError::Panic(Id(18), ...)', /graph-node/store/postgres/src/connection_pool.rs:497:10
1970-01-01 08:00:00 example-subgraph-graph-node-1 exited with code 101```

### IPFS hash

_No response_

### Subgraph name or link to explorer

_No response_

### Some information to help us out

- [X] Tick this box if this bug is caused by a regression found in the latest release.
- [ ] Tick this box if this bug is specific to the hosted service.
- [X] I have searched the issue tracker to make sure this issue is not a duplicate.

### OS information

None

hi - you can add this line to your Docker Compose https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L47


Reduce the number of checks by merging some and disabling the redundant

This process will be more involved and require more discussion than initially though. For this reason, I will close this PR and open separate PRs for adapting Nuclei and deprecating each of the checks that will be replaced by Nuclei templates. Other checks that will be deprecated or merged for others not related to Nuclei will have their own separate PR.


Revert "Don't iterate over HashMap/HashSet (#1164)"

This reverts commit 4e1817be67211468fbdef57ed983ab7f30eb83c7.
The change in native_blockifier should be made more delicately, looks like Pyo3 has some issues with indexmap>1.9.3 (even though they stated that they support < 3.0.0.
Will reenable soon after sidestepping this issue.

This change is

Codecov Report
Attention: 10 lines in your changes are missing coverage. Please review.

Comparison is base (708b1d8) 67.38% compared to head (9f664c0) 67.38%.

Files
Patch %
Lines

...ates/native_blockifier/src/transaction_executor.rs
20.00%
4 Missing :warning:

crates/native_blockifier/src/storage.rs
0.00%
3 Missing :warning:

crates/native_blockifier/src/py_block_executor.rs
0.00%
2 Missing :warning:

crates/blockifier/src/state/cached_state.rs
83.33%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1184   +/-   ##
=======================================
  Coverage   67.38%   67.38%
=======================================
  Files          52       52
  Lines        6740     6740
  Branches     6740     6740
=======================================
  Hits         4542     4542
  Misses       1782     1782
  Partials      416      416

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


Is it possible to add webpage login password restrictions to prevent excessive misuse?

https://stackoverflow.com/questions/23616371/basic-http-authentication-with-node-and-express-4#:~:text=Example%3A,login dialog!
}))%3B

Follow above comment


Open Issue: Request for User Feedback on goMarkableStream

Hello goMarkableStream Users,
I initially developed goMarkableStream primarily for my own needs. However, I've been delighted to see that others have found value in it too. With the intention of refining and possibly expanding its capabilities, I'd love to understand how you're using the tool and what improvements you might desire.

Usage Context:

Could you describe the usual scenarios or contexts in which you employ goMarkableStream? Are there specific challenges it assists you with?

Usage Frequency:

Do you turn to goMarkableStream regularly, or is it more for distinct situations?

Feature Requests & Improvements:

Are there any features you believe, if added, would dramatically alter your experience with the tool?
Are there elements of goMarkableStream you think could be enhanced or further developed?

Your feedback means a lot to me. Whether it's aspects you appreciate, areas you feel could use refinement, or entirely new features you envision, I'm all ears.
Please respond to this issue with your insights.
Thank you for your commitment to the goMarkableStream community and for helping it evolve.
Warm wishes,
Olivier
Maintainer of goMarkableStream

Hi Olivier,
(1) my use case is for visualization / sketching in online training sessions or even on-site trainings where some participants are connected remotely and cannot see the flip chart or similar. Therefore always connected over USB and airplane mode enabled, no constraints on power consumption. Might be a bit of an edge case ;) (2) Usage would be somewhat regularly as a planned part of a training session or for illustrations in Q&A. (3) I opened issues for the things still missing / not working for my use case.
For me the main features are no reliance on network connectivity and no client installation which other offerings require. Thanks for doing this!

For me the usage seems similar to @fabianlupa .
I would like to stream the content of the remarkable to an online audience. For this, I use Zoom with screen-sharing. It is important that the remarkable is online connected over USB. Both because of potential bandwidth limit as well as the fact that often I am in an environment where the remarkable does not have access to the WiFi.
Thanks for the project!

I add my own (new) usage as I am also a user 😀
I wrote it on a blog post.
https://blog.owulveryck.info/2023/10/10/rethinking-presentations-beyond-static-slides.html

Good evening, @owulveryck! Thank you so much for this fantastic work!
Context
I was previously using rmView for the same use case. I'm a software developer and communicate best through illustration. In the most recent reMarkable update I could no longer connect to rmView, so I searched for another tool. That's when I came upon your solution, goMarkableStream. And I'm very happy I did.
Frequency
I made goMarkableStream a service and always have it running. I use the reMarkable every day and have the browser tab in the background.
Requests
Here are some features inspired by my usage of rmView:

Configuration to preserve rotation orientation. (I only use the reMarkable in landscape. This forces me to click Rotate every time I open the viewer.)
Potentially increase the default refresh rate? rmView felt a little more responsive, although, I'm not sure what factors led to that.
Some way to indicate where the pen is, even while hovering over the tablet. rmView had this feature and it let you "point" to something without leaving a mark. It was great for calling attention to something while presenting.

Again, thank you! This is a wonderful tool and I hope I can help moving forward.
Alex

Olivier, many thanks for that ! I was using different solutions in the past, but the way you implement it is so easy and straight forward, I really appreciate no need to install anything on a server side.
My main use case is when I have to draw something to explain complex network architecture or concepts to prospect or customers through Teams.
The way I am using it is very straight forward, using dnsmasq to give a static IP address based on Remarkable MAC address and a a name I can easily type in my browser !
The main area I would appreciate some guidance/improvement is how to get a proper systemd service as mine is working fine from a cold boot but seems to have issues when the tablet is going to sleep and wake up.
Many thanks !

@2Belette I'm not sure if this is the recommended approach, but I haven't had any issues keeping the service running through sleeps, restarts, running out of battery, etc.
First, write a systemd service file:
ssh remarkable
cd /etc/systemd/system
touch goMarkableStream.service

[Unit]
Description=Go Remarkable Stream Server

[Service]
ExecStart=/home/root/goMarkableStream
Restart=always

[Install]
WantedBy=multi-user.target

systemctl enable goMarkableStream.service
systemctl start goMarkableStream.service
systemctl status goMarkableStream.service

Thanks @ajmedeio ! I had almost the same but with some sleep hack and some Requires / Depends on and maybe this was the reason why it was failing time to time.. I tested, still not deeply, but your version seems to work so far, will see with the time

I recently found this application as due to company policy, I am not able to use reMarkable's own Screen Sharing feature (and frankly do not want to use their cloud for anything). It looks promising, however I have not been able to install/use goMarkableStream. I am on Windows and while the PC is managed, I do have access to admin rights. Would it be possible to add a guide for use on Windows?
To answer your question: my use case would be in teaching, presenting either live drawings or equations by connecting to a laptop over USB.

... however I have not been able to install/use goMarkableStream. I am on Windows and while the PC is managed, I do have access to admin rights. Would it be possible to add a guide for use on Windows?

The PC or Mac is just the "door" to your rM device. Nothing needs to be installed on the PC/Mac itself (great concept IMHO :-))
The only command you need on the PC is ssh - which doesn't come with Windows IIRC. Here https://github.com/mb1986/rm-hacks/wiki/Installation are great instructions on how to do that, also for Windows (you may need to follow the link to "SSH Access").
When you see the rM's "zero sugar" message, you'll not follow that guide any further (i.e. don't execute 'sh -c "$(wget ..."), but instead follow Olivier's Quick Start Guide, i.e. execute "export GORKVERSION=$(wget..."
This will install goMS on the rM (it needs internet access to download goMS).
After that the command "./goMarkableStream" will start goMs on the rM and you can open a browser on your PC as per instructions.
"easy fifty-two steps" ;-)

@RedTartan04 Thank you for the quick response! Connecting over ssh works. But then on step one the following occurs:
reMarkable: ~/ export GORKVERSION=$(wget -q -O - https://api.github.com/repos/owulveryck/goMarkableStream/releases/latest | grep tag_name | awk -F\" '{print $4}')
wget: note: TLS certificate validation not implemented
wget: got bad TLS record (len:0) while expecting handshake record
wget: error getting response: Connection reset by peer

I believe this might be the same issue as #102 but i did not manage their solution/workaround

:/ You could try downloading the .tar.gz release file from https://github.com/owulveryck/goMarkableStream/releases to you PC, unpack it, which give you the file 'goMarkableStream'.
Then you copy this to the rM using 'scp' (as suggested in#102).

Thank again, it required a software update on the reMarkable but I managed to make it work!
For good order, a step plan for Windows (firmware <IP_ADDRESS> & goMarkableStream 0.18):

Extract the goMarkableStream file from the .tar.gz release from https://github.com/owulveryck/goMarkableStream/releases
(file path \goMarkableStream_.tar.gz\goMarkableStream_.tar\goMarkableStream_\goMarkableStream )
Open a command window in the folder where the file is and copy it to the reMarkable using scp:
scp goMarkableStream root@<remarkable>: - it will now ask for the password, found in About/Copyrights and licenses
Then use ssh to connect to the reMarkable:
ssh root@<remarkable> - it will again ask for the password, afterwards you will see the 'zero sugar' message
Make the file executable by doing:
chmod +x goMarkableStream
And execute it:
./goMarkableStream
Now you should see the current time + listening on [::]:2001 which means it worked and you can open the browser window like in the quick start guide

In all cases you replace <remarkable> with the ip-adress of the tablet
Feel free to move or remove this comment if not useful!


How i can install this plugin from github.

Download/Clone this git then copy the AdvancedSessions and AdvancedSessionsSteam to your project/plugins folder.

Thank you .


Writing a guide how to declutter scenes and keep code compact

Complex animations often tend to have entangled code, and it would be amazing if we could provide a guide with some ideas to declutter scenes when writing manim animations in the tutorial section of the docs.
Therefore, I have an example on which we can discuss what organizing code could look like.
Here is a scene without extra classes:
class NoClass(Scene):
    def construct(self):
        im_hue = Circle(radius=1.4).set_color(RED)
        im_val = Circle(radius=1.4).set_color(WHITE)
        radius = im_hue.height/2
        self.add(im_hue, im_val)
        Group(*self.mobjects).arrange(DOWN, SMALL_BUFF*1.3).to_edge(RIGHT)
        t1= Text("Hue and Saturation").scale(0.3)
        t1.next_to(im_hue, UP, buff=SMALL_BUFF).rotate(35*DEGREES, about_point=im_hue.get_center())
        self.add(t1)
        t2= Text("Value").scale(0.3)
        t2.next_to(im_val, UP, buff=SMALL_BUFF).rotate(35*DEGREES, about_point=im_val.get_center())
        self.add(t2)

        CENTER_HUE = im_hue.get_center()
        CENTER_VAL = im_val.get_center()

        t1= Text("Hello world").move_to(2*UL)
        self.add(t1)

And here is the exact same scene, but this time the class MyWheels is defined
class MyWheels(Mobject):
    def __init__(self, **kwargs):
        Mobject.__init__(self, **kwargs)
        im_hue = Circle(radius=1.4).set_color(RED)
        im_val = Circle(radius=1.4).set_color(WHITE)
        radius = im_hue.height/2
        self.add(im_hue, im_val)
        Group(im_hue, im_val).arrange(DOWN, SMALL_BUFF*1.3).to_edge(RIGHT)
        t1= Text("Hue and Saturation").scale(0.3)
        t1.next_to(im_hue, UP, buff=SMALL_BUFF).rotate(35*DEGREES, about_point=im_hue.get_center())
        self.add(t1)
        t2= Text("Value").scale(0.3)
        t2.next_to(im_val, UP, buff=SMALL_BUFF).rotate(35*DEGREES, about_point=im_val.get_center())
        self.add(t2)
        CENTER_HUE = im_hue.get_center()
        CENTER_VAL = im_val.get_center()

class WithClass(Scene):
    def construct(self):
        wheels = MyWheels()
        self.add(wheels)
        t1= Text("Hello world").move_to(2*UL)
        self.add(t1)

Some questions that come to my mind:

of what type should these set up classes be? Should it be VMobject, VGroup, Mobject, Group?
E.g. here:
https://github.com/ManimCommunity/manim/blob/642b7683b28cbfd2cc27936a90bb6f6fd2d9294c/manim/mobject/logo.py#L16
We used VGroup.
next important point: What is a good practice of accessing coordinates then?
In this example there are CENTER_HUE and CENTER_VALwhich might be used from time to time.
Here I see three options: A) one could make them global variables. B) one could define them as self.CENTER_HUE and self.CENTER_VAL  MyWheels. C) one could define them in the main scene with CENTER_HUE= wheels.im_hue.get_center().

I'm not sure about this.
Perhaps we can give some smaller and more general / generic suggestions on how to structure code.
In your two examples, the bottom code does not seem any simpler than the top code.
I also wonder why you set radius via a keyword argument, but use the method for colour? Same for Text - the string is an argument but not scale=0.3. Why?
What I would much rather suggest is fore people to create functions that create mobjects they care about (rather than full derived classes). Perhaps something like this:
def myText(textstring):
    t = Text(textstring, color=YELLOW, size=5)
    t.method1(argument1)  // perhaps align to left edge of screen
    t.method2(argument2)  // and so on ...
    return t

and so on.
Besides, there are so many ways to make code more readable. It's often personal preference. For example, I'd have gone for something like this.
def myCircle(radius=1.4, color=WHITE)
    return Circle(radius=radius, color=color)

def LabelText(str):
    returnText(str).scale(0.3)

def LabelCircle(str,circle):
   text = LabelText(str)
   text.next_to(circle, UP, buff=SMALL_BUFF).rotate(35*DEGREES, about_point=circle.get_center())

class NoClass(Scene):
    def construct(self):
       // make circles
        im_hue = myCircle(color=RED)
        im_val = myCircle()

        //arrange circles along right edge  //perhaps make this another function?
       im_hue.to_edge(RIGHT)
       im_val.to_edge(RIGHT)
       im_val.next_to(im_hue, DOWN, 1.3*SMALL+BUFF)

       // add circles to scene
        self.add(im_hue, im_val)

        //label the circles
        self.add(LabelCircle("Hue and Saturation", im_hue), LabelCircle("Value", im_val))

        // say hello
        t3= Text("Hello world").move_to(2*UL)
        self.add(t3)


Fix test 21 - undefined symbol

The host code depends on a symbol generated by aiecc.py. It was not added by the makefile to the compilation and the linker complained with undefined symbol: air::segments::segment_0::mlir_aie_wr…ite_buffer_scratch_0_0(aie_libxaie_ctx_t*, int, int).

FWIW this is what it looks like when I run it. Maybe the clang command line can help debug the Makefile:
/work/build/air$ lit -av test/airhost/21_air_nd_memcpy_2d/
Running with PYTHONPATH /work/build/air/python:/work/build/aie/python:XRT_DIR-NOTFOUND/python
Found ROCm: /work/ROCm-air-platforms/rocm/lib/cmake/hsa-runtime64/../../..
xrt not found
-- Testing: 1 tests, 1 workers --
PASS: AIR_TEST :: airhost/21_air_nd_memcpy_2d/run.lit (1 of 1)
Script:
--
: 'RUN: at line 9';   /work/build/air/bin/aircc.py -row-offset=4 -col-offset=5 /work/air/test/airhost/21_air_nd_memcpy_2d/air.mlir -o /work/build/air/test/airhost/21_air_nd_memcpy_2d/Output/air.a
: 'RUN: at line 10';   clang++ -fuse-ld=lld -DLIBXAIENGINEV2 /work/air/test/airhost/21_air_nd_memcpy_2d/test.cpp -I/work/ROCm-air-platforms/rocm/lib/cmake/hsa-runtime64/../../../include -L/work/ROCm-air-platforms/rocm/lib/cmake/hsa-runtime64/../../../lib -lhsa-runtime64 -I/scratch/opt/xaiengine/include -L/scratch/opt/xaiengine/lib -lxaiengine -I/work/build/aie/runtime_lib/x86_64/test_lib/include -L/work/build/aie/runtime_lib/x86_64/test_lib/lib -ltest_lib  -I/work/build/air/runtime_lib/x86_64/airhost/include -L/work/build/air/runtime_lib/x86_64/airhost -Wl,--whole-archive -lairhost -Wl,-R/scratch/opt/xaiengine/lib -Wl,-rpath,/work/ROCm-air-platforms/rocm/lib/cmake/hsa-runtime64/../../../lib -Wl,--whole-archive -Wl,--no-whole-archive -lpthread -lstdc++ -lsysfs -ldl -lrt -lelf -Wl,--whole-archive /work/build/air/test/airhost/21_air_nd_memcpy_2d/Output/air.a -Wl,--no-whole-archive -rdynamic -o /work/build/air/test/airhost/21_air_nd_memcpy_2d/Output/test.elf
: 'RUN: at line 11';   sudo /work/build/air/test/airhost/21_air_nd_memcpy_2d/Output/test.elf
--
Exit Code: 0

Command Output (stdout):
--
 AIE Compilation: ━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00 0:00:00 2/2 4 Workers
air_init
Found 1 agents
Max AIE queue size: 64
loading aie_ctrl.so
Core [3, 3] status is 00000002, timer is 3019204, PC is 00000000, LR is 00000000, SP is 00000000, R0 is 00000001,R4 is 00000000
Core [3, 3] trace status is 00000000
Core [3, 3] AIE1 locks are 00000000
Core Status: In Reset
DMA [3, 3] mm2s_status/0ctrl/1ctrl is 00000000 00 00, s2mm_status/0ctrl/1ctrl is 00000000 00 00
DMA [3, 3] AIE1 s2mm0 IDLE
DMA [3, 3] AIE1 s2mm1 IDLE
DMA [3, 3] AIE1 mm2s0 IDLE
DMA [3, 3] AIE1 mm2s1 IDLE
PASS!

--
Command Output (stderr):
--
Runtime: found 1 AIE agents
Runtime: initializing memory pools
Runtime: found global segment

--

********************

Testing Time: 1.93s
  Passed: 1

reopen with requested changes if this is still a problem.


Accept integer inputs

With the current design, the user can only specify some of the parameters as floats. However, it would be helpful if the model accepted integers and converted them into floats.
Parameters: Volume, Clearance, Drug rate

Will get on with that now

I have updated the files, please test them @ala1705


Bootstrap undefined variable error on fresh install

Hello! I'm installing doks for the first time and am running into an error that I can't quite sort out (I'm new to Hugo's pipeline processes / mount stuff, likely something I'm missing)

Node version is 20.5.1
NPM is 10.1.0 (same error with npm 9.8.0 as well

Going through the default setup of:
npm create hyas@latest -- --template doks
cd project_name
npm install
npm run dev

Gives me this error about an undefined bootstrap variable (I've added `--verbose` to the command)
[ ~/project_name]$ npm run dev
><EMAIL_ADDRESS>dev
> exec-bin node_modules/.bin/hugo/hugo server --bind=<IP_ADDRESS> --verbose --disableFastRender --baseURL=http://localhost --noHTTPCache

WARN  --verbose is deprecated and will be removed in a future release. use --logLevel info
Watching for changes in /Users/me/project_name/{config,content,i18n,node_modules,package.json,static,themes}
Watching for config changes in /me/project_name/config/_default, /Users/me/project_name/config/_default/hyas, /Users/me/project_name/config/_default/menus
Start building sites …
hugo v0.118.2-da7983ac4b94d97d776d7c2405040de97e95c03d+extended darwin/amd64 BuildDate=2023-08-31T11:23:51Z VendorInfo=gohugoio

INFO  copy static: syncing static files to /
INFO  build: running step process duration 1.421547ms
INFO  build: running step assemble duration 4.235515ms
INFO  build: running step render duration 566.961223ms
INFO  build: running step postProcess duration 1.044299ms
Built in 575 ms
Error: error building site: TOCSS: failed to transform "scss/app.scss" (text/x-scss): "/Users/me/project_name/node_modules/bootstrap/scss/_root.scss:94:70": Undefined variable: "$mark-color".

I've also tried installing via the npm create hyas@latest command, and template: doks gives the same error
Though hyas does work with the template: bootstrap -> variant: recommended plugins options
Any help would be greatly appreciated!

Confirmed. Fix will follow shortly

Fixed — latest packages
Running npm create hyas@latest will ask you to install the latest version

Thank you!


Fixes #818

Corrections to sample code.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/extensibility/debugger/reference/disassemblydata.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@snalexp thanks for fixing this!


Fix resourceName in setup script and in README.md

The resource name should be resource-usage-score and not rcs-score.
Also, add numberOfClusters: 1 to spec.
https://github.com/dana-team/rcs-ocm-deployer/blob/861c65dca47b7d82d37700d311c12cde5c2d2545/hack/setup-rcs-deployer.sh#L46-L64

Fixed by #121


set_attr_graph_used

I'm not sure if I am misunderstanding this, but is it not possible to only pass node attributes or edge attributes, without necessarily having to pass both of them? From base.py I observe:
    def set_attr_graph_used(self, *args, **kwargs): # real signature unknown         """         Set graph attribute used by the algorithm to compare graphs.                 Parameters                 ----------                 node_attr_key : str                     key of the node attribute                 edge_attr_key: str                     key of the edge attribute         """         pass

It seems like you can just use None in order for it to ignore one of the attributes.


update url for FollowPlaylist/UnfollowPlaylist/IsFollowingPlaylist

update urls according changes in SpotifyAPI
https://developer.spotify.com/community/news/2018/06/12/changes-to-playlist-uris/

Thanks! :)

Did they ever release an update for the blog post tho? This is on the top:

Update: Due to technical issues, we have rolled back the change originally scheduled for 11th September 2018. We will communicate a new date for the change as soon as we have one.

I followed the changes back then, but found it weird that they never actually confirmed the change

according to their docs https://developer.spotify.com/console/put-playlist-followers/ they did :)


Fullscreen is fucked

Whenever i start the game in fullscreen this happens for some reason

i need a way to fix it

This is a base game issue


Refactor Any to support Trigger messages

Summary
Since moving to proto based messages, Any was introduced for handling "generic" serde issues. This creates a lot of complexity and the expand_as_any is not a very elegant way to handle it. It is especially obvious with the new Trigger module since it accepts any message type as the action.
Problem Definition

Proposal
Investigate other solutions with the macro and/or what effort is needed to finally fix wasmd so that responses from the protocol level are actual protos instead of json

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

this will be handled with #141


FP8 Support

This is an umbrella issue for allowing fp8 type(s) in shark, spanning all the required layers of the stack: Turbine, IREE, MLIR, LLVM, including backends of interest like ROCm.
Some initial research is required to scope this properly and divide into subtasks, but the main work items are roughly:

[x] Confirm the exact level of support for fp8 type(s) in the amdgpu backend in llvm
[x] Also check with the other target backends (cc @MaheshRavishankar)

Checked with the team and focus on gfx940 for now only

[x] Intersect the above with support in llvm::APFloat
[ ] Make sure we can lower simple kernels in the gpu/llvm dialect all the way to amdgpu
[ ] Make sure Turbine / input conversion supports the relevant fp8 type(s)
[ ] Make sure iree tooling can consume fp8 weights / inputs
[ ] Make sure iree runtime works with fp8 types
[ ] Add e2e correctness tests

This is just an umbrella issue to get started.
cc: @antiagainst @MaheshRavishankar @qedawkins @raikonenfnu @hanhanW @bjacob

The gfx940 ISA supports 2 fp8 formats: fp8 and bf8. You can see both format supported with mfma, including operands of mixed formats: https://llvm.org/docs/AMDGPU/AMDGPUAsmGFX940.html#vop3.
FP8 mfma is plumbed through the amdgpu llvm backend: https://reviews.llvm.org/D129906, for example:
// CHECK-GFX940-LABEL: @test_mfma_f32_32x32x16_fp8_bf8
// CHECK-GFX940: call <16 x float> @llvm.amdgcn.mfma.f32.32x32x16.fp8.bf8(i64 %a, i64 %b, <16 x float> %c, i32 0, i32 0, i32 0)
void test_mfma_f32_32x32x16_fp8_bf8(global v16f* out, long a, long b, v16f c)
{
  *out = __builtin_amdgcn_mfma_f32_32x32x16_fp8_bf8(a, b, c, 0, 0, 0);
}

The fp8 operands are packed as i64. The only other amdgcn intrinsic for fp8 types is cvt -- type conversions. https://github.com/llvm/llvm-project/blob/cd3942059eed7b7185f26bc583ac287a995db0d0/clang/include/clang/Basic/BuiltinsAMDGPU.def#L400-L407
FP8 is E4M3 (inference-focused) while BF8 is E5M2 (training-focused): https://www.amd.com/en/products/accelerators/instinct/mi300/mi300a.html.
The AMD CDNA 3 compute units support both variants of the FP8 data type as defined in the OCP 8-bit floating point specification.
OCP 8-bit Floating Point Specification (OFP8)
Related paper with an overview of fp8 types: FP8 FORMATS FOR DEEP LEARNING

FP8 support in LLVM/MLIR:
RFC from Sep '22 by @stellaraccident: https://discourse.llvm.org/t/rfc-add-apfloat-and-mlir-type-support-for-fp8-e5m2/65279.

e5m2 landed here: https://reviews.llvm.org/D133823, the MLIR syntax is f8E5M2

Since then, the other types plumbed all the way through MLIR are:
  Float8E4M3FNType f8E4M3FNTy;
  Float8E5M2FNUZType f8E5M2FNUZTy;
  Float8E4M3FNUZType f8E4M3FNUZTy;
  Float8E4M3B11FNUZType f8E4M3B11FNUZTy;

(https://github.com/llvm/llvm-project/blob/6af713ae170c34f0561f19e594266ce2a2af343b/mlir/lib/IR/MLIRContext.cpp#L223C27-L227)
      .Case<Float8E5M2Type>([&](Type) { os << "f8E5M2"; })
      .Case<Float8E4M3FNType>([&](Type) { os << "f8E4M3FN"; })
      .Case<Float8E5M2FNUZType>([&](Type) { os << "f8E5M2FNUZ"; })
      .Case<Float8E4M3FNUZType>([&](Type) { os << "f8E4M3FNUZ"; })
      .Case<Float8E4M3B11FNUZType>([&](Type) { os << "f8E4M3B11FNUZ"; })

(https://github.com/llvm/llvm-project/blob/6af713ae170c34f0561f19e594266ce2a2af343b/mlir/lib/IR/AsmPrinter.cpp#L2548C1-L2552C73)
func.func @float_attrs_pass() {
  "test.float_attrs"() {
    // CHECK: float_attr = 2.000000e+00 : f8E5M2
    float_attr = 2. : f8E5M2
  } : () -> ()
  "test.float_attrs"() {
    // CHECK: float_attr = 2.000000e+00 : f8E4M3FN
    float_attr = 2. : f8E4M3FN
  } : () -> ()
  "test.float_attrs"() {
    // CHECK: float_attr = 2.000000e+00 : f8E5M2FNUZ
    float_attr = 2. : f8E5M2FNUZ
  } : () -> ()
  "test.float_attrs"() {
    // CHECK: float_attr = 2.000000e+00 : f8E4M3FNUZ
    float_attr = 2. : f8E4M3FNUZ
  } : () -> ()
  "test.float_attrs"() {
    // CHECK: float_attr = 2.000000e+00 : f8E4M3B11FNUZ
    float_attr = 2. : f8E4M3B11FNUZ
  } : () -> ()
  "test.float_attrs

(https://github.com/llvm/llvm-project/blob/dd047c5b64944bae830b9fecf53f8d11ff41386e/mlir/test/IR/attribute.mlir#L38C1-L59C20)

Based on the representation table from OFP8 ('OFP8 exponent parameters'), amgcn's fp8 should map to f8E4M3FN while bf8 to f8E5M2.

FP8 is E4M3 (inference-focused) while BF8 is E5M2 (training-focused): https://www.amd.com/en/products/accelerators/instinct/mi300/mi300a.html.

If a model is trained with 2-bit mantissas (E5M2), how is the 3rd bit of mantissa in E3M4 going to be useful in inference?

Also https://docs.nvidia.com/deeplearning/transformer-engine/user-guide/examples/fp8_primer.html talks a bit about fp8 in NVIDIA GPUs, which is useful reference.
In general, fp8 right now are just used in a very ad-hoc way--with ISAs just do conversion and tensor/matrix core ops. For training we also have different fp8 scaling factors for different tensors and need model/framework level handling there, so also quite ad-hoc.
So as we've discussed in the meeting, getting a minimal matmul to excersise fp8 + tensor/matrix core in IREE/SHARK would be good start and foundation to everything else. We can then build other parts on top.

FP8 is E4M3 (inference-focused) while BF8 is E5M2 (training-focused): https://www.amd.com/en/products/accelerators/instinct/mi300/mi300a.html.

If a model is trained with 2-bit mantissas (E5M2), how is the 3rd bit of mantissa in E4M3 going to be useful in inference?

This is explained a bit in the NVIDIA doc as linked in my previous comment:

During training neural networks both of these types may be utilized. Typically forward activations and weights require more precision, so E4M3 datatype is best used during forward pass. In the backward pass, however, gradients flowing through the network typically are less susceptible to the loss of precision, but require higher dynamic range. Therefore they are best stored using E5M2 data format. H100 TensorCores provide support for any combination of these types as the inputs, enabling us to store each tensor using its preferred precision.

Support in MLIR/LLVM/AMDGPU already seems quite promising, so as discussed this morning the plan is to show a very simple example using fp8 in IREE first, something like
module {
  func.func @matmul_static(%arg0: tensor<32x32xi8>, %arg1: tensor<32x32xi8>, %arg2: tensor<32x32xf32>) -> tensor<32x32xf32> {
    %0 = tensor.bitcast %arg0 : tensor<32x32xi8> to tensor<32x32xf8E4M3FNUZ>
    %1 = tensor.bitcast %arg1 : tensor<32x32xi8> to tensor<32x32xf8E4M3FNUZ>
    %2 = linalg.matmul ins(%0, %1 : tensor<32x32xf8E4M3FNUZ>, tensor<32x32xf8E4M3FNUZ>) outs(%arg2 : tensor<32x32xf32>) -> tensor<32x32xf32>
    return %2 : tensor<32x32xf32>
  }
}

or, to avoid the need to also handle mfma at the same time, just something as simple as
#map = affine_map<(d0) -> (d0)>
module {
  func.func @extend_i8(%arg0: tensor<32xi8>) -> tensor<32xf32> {
    %0 = tensor.bitcast %arg0 : tensor<32xi8> to tensor<32xf8E4M3FNUZ>
    %1 = tensor.empty() : tensor<32xf32>
    %2 = linalg.generic {indexing_maps = [#map, #map], iterator_types = ["parallel"]} ins(%0 : tensor<32xf8E4M3FNUZ>) outs(%1 : tensor<32xf32>) {
    ^bb0(%in: f8E4M3FNUZ, %out: f32):
      %3 = arith.extf %in : f8E4M3FNUZ to f32
      linalg.yield %3 : f32
    } -> tensor<32xf32>
    return %2 : tensor<32xf32>
  }
}

Explanation of the LLVM fp semantics naming convention:

F is for "finite" (no infinities), N for with special NaN encoding, UZ for unsigned zero.
source: https://github.com/jax-ml/ml_dtypes?tab=readme-ov-file#float8_e5m2fnuz

Looking through support in MLIR and lowering into NVVM/ROCDL, seems to be already there as well..
MFMA to ROCLD intrinsics :

MFMA instruction lowering (link)
Convert instructions lowering ([link])(https://github.com/llvm/llvm-project/blob/d9a9872ec4760762fdc467ef283cea302a3742e5/mlir/lib/Conversion/AMDGPUToROCDL/AMDGPUToROCDL.cpp#L683))

Tensor core instructions lowering

WGMMA instruction support (link)
I didnt find support for conversion instructions. So thats strange.

So for the examples in this comment https://github.com/nod-ai/SHARK/issues/2054#issuecomment-1877842991 , the extension truncation should just pass through and compile on AMD. The mfma support, it would be great if we could just take a single matmul of the exact mfma shape and it would just lower to that operation. Like literally all tile sizes would be 1... it should vectorize to vector.contract, lower to amdgpu.mfma -> rocdl intrinsics...


[WIP] Design - Optional - Service Worker

[WIP] Scenario (Optional) ( #4 )
Fixture
webpack.config.js
const MultipageWebpackPlugin = require(multipage-webpack-plugin);

const config = {
  entry: {
    a: './src/a.js',
    b: './src/b.js'
  },
  output: {
    filename: '[name].chunk.js',
    path: path.join(__dirname, "dist")
  },
  module: {
    /* ... */
  },
  plugins: [
    new MultipageWebpackPlugin()
  ]
};

module.exports = config;

Service Workers
** How would service workers be implemented in a "default, out of the box way" for multi page applications (that do not use client routers)?**
What existing work can we leverage to help accomplish this behavior (offline-plugin / sw-precache-plugin (cc @nekr @addyosmani))
What are some possible defaults for server rendered applications in these regards that make sense?
Example derived from fixture above:
├── dist/
│   ├── a/
│   ├─── index.html
│   ├── b/
│   ├─── index.html
│   ├── a.js
│   ├── b.js
│   ├── shared.js
│   ├── inline.js
│   ├── vendors.js
│   ├── a.css (if applicable)

** a/index.html **
<!DOCTYPE html>
<html>
  <head>
    <meta charset="UTF-8">
    <title>Webpack App</title>
  </head>
  <body>
    <script type="text/javascript" src="../../inline.chunk.js"></script>
    <script type="text/javascript" src="../../shared.bundle.js"></script>
    <script type="text/javascript" src="../../vendor.chunk.js"></script>
    <script type="text/javascript" src="../../a.chunk.js"></script>
  </body>
</html>

@nekr I have created the issue "layout" for you to discuss the potential design. The questions in bold, that can be discussed or answered etc.


New package: WinsiderSS.SystemInformer version 3.0.11299.6772

Resolve #109907

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/111530&drop=dogfoodAlpha

I have no idea to resolve this

I have no idea to resolve this

Unfortunately, this might not be possible to fix. It would have to be reported as not malware.

Please retry one time.
If it still appears this, this PR should be blocked temporarily

Don't assign it to me, I have no idea to fix

/AzurePipelines run

Automatic Validation ended with:

Hi @CoolPlayLin,
Is there an installer switch to bypass the message box above, and complete the install automatically?

@stephengillie
Sorry, I haven't used this software yet. I don't how to bypass it.
CC @0xThiebaut

？

Currently OoO, will investigate/request the switch on Sept 26.

@stephengillie Add Blocking-issue temporarily

Blocked by https://github.com/winsiderss/systeminformer/issues/759 .

@stephengillie Could this be not marked as No-Recent-Activity ?

Why it added again?

Why it added again?

No adding :)

Stop

.

Stop


Provide an automatic setup for tox

kwT

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.529%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1646

Relevant Lines:
1763

💛  - Coveralls


[WIP] Async support for vector index creation

I think this works. It is a decent amount of redundant code which I'm wary of. The only other option I was going to suggest is if you just added async to build_index_from_document and not the embeddings part, but that would still introduce blocking embedding API calls, so speed gain probably wouldn't be as good.

Thanks for the thoughts. Yeah re the redundant code -- is there another way? Some other codebases I saw also had similar setups where the functions are essentially copy-pasted. JS makes this way easier but I didn't find a way around it.
Also, why would the embedding API calls be blocking? I switched to the OpenAI async API and then converted everything to async all the way.

Also 2 open questions:

How to get asyncio to work with pytest? Just mocking run_async_tasks doesn't work here

Tbh I don't really know, closest I found is this https://tonybaloney.github.io/posts/async-test-patterns-for-pytest-and-unittest.html

Not sure what we want to do with the aget_text_embedding class function in BaseEmbedding since only OpenAI has the async api

we can always just call the synchronous get_text_embedding function as a default right?

Also, why would the embedding API calls be blocking? I switched to the OpenAI async API and then converted everything to async all the way up.

No i meant in the hypothetical scenario i suggested where you async the outer function but the inside is still a synchronous call to OpenAI's API (which i said would be slow)

No i meant in the hypothetical scenario i suggested where you async the outer function but the inside is still a synchronous call to OpenAI's API (which i said would be slow)

I see -- yeah the gains are mainly from async-ing the Embedding API calls. Anyways, the current version should all be working! Added a ipynb demo'ing some big gains.
Also, I was able to fix the tests by rewriting run_async_tasks to what I think is the correct way? cc @Disiok