Explore contexts/interactions pre/post conditions and transitions

We should explore the concepts of pre and post conditions for contexts and interactions, as well as transitions between contexts.
Effectively, we should look at how to ensure a context is available (eg. install/launch an app ang give foreground), how one can transition from one context to another (eg. by switching tabs, launching/closing apps or windows, etc.), which context we're in after an interactions, and whether a given context should be cleaned up after use (eg. close an app when not used anymore).

We should explore the relation between Transitions and Interactions. My initial perspective is that a Transition can be triggered by one or many different Interactions (eg. On Windows, opening the Start menu can be done by clicking Start button in the Taskbar, or using the Win key). Similarly, an Interaction can result in multiple Transitions at once, or rather the Transition or different Contexts.
It could be useful to have the ability to list all Interactions that result in a given Transition. Naming Transitions could also be useful for cases where the specific Interaction is not relevant, or where you want to cycle through all Interactions (eg. in a test).
Syntax for standalone Transitions could look something like:
transition MyTransition { initial_state_condition } -> { end_state_condition }
transition OpenStart { StartMenu::IsAvailable } -> { not { StartMenu::IsAvailable } }

Syntaxt for Transition caused by a given interaction could look like:
interaction MyInteraction($myParam) -> { end_state_condition }
Where the initial state if infered by the context the interaction is defined in. Though it might be useful to allow for specifying the initial state as part of the interaction itself.
One could invoke a Transition like an interaction:
MyTransition()
MyTransition<any>()
MyTransition<*>()
MyTransition<>()
MyTransition<Context::Interaction>()

foreach Interaction in MyTransition::Interactions:
    Interaction()

Transitions could be used when trying to ensure a given state, by serving as directed edges in computed state machine / graph:
ensure { end_state_condition }
ensure Context
ensure Context::SubContext
ensure MyTransition::EndState


Use header includes on LocationIndexPage and BreadsIndexPage

Totally my fault, I forgot to use these despite having them from BlogIndexPage.

Noting this is a possible duplicate of #49. I suspect both can be closed at the same time.

@heymonkeyriot Close this if you think this is no longer relevant.


fix: error message for provider failure was not descriptive

What I did
fixed nondescriptive error message TypeError: Can't instantiate abstract class Infura with abstract methods chain_id
Related issue: #
https://github.com/ApeWorX/ape/issues/119
https://github.com/ApeWorX/ape-infura/issues/1
How I did it
wrapped the offending line in try... except
How to verify it
I run ape console --network ethereum:ropsten:infura but the infura plugin is broken
Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

I left it as Exception for consistency with the rest of the file, should I refactor it to Abort?

closing in favor of #121


feat(meta): record barrier latency in event table

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
part of #12826
Failed barrier doesn't write a event log.
Event log table only records latest 10 events for each type by default. We can customize it on demand.
dev=> select * from rw_catalog.rw_event_logs where event_type='BARRIER_COMPLETE';
              unique_id               |           timestamp           |    event_type    |                                                                                info
--------------------------------------+-------------------------------+------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 4be656b2-33c2-4e8d-970d-a4934ab51bd7 | 2023-11-24 03:43:31.623+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_BARRIER", "command": "Plain", "curEpoch": "5476333100859392", "durationSec": 0.000279333, "prevEpoch": "5476333035257856"}}
 4846bd92-34d1-4304-ae6d-47912abe90b7 | 2023-11-24 03:43:32.623+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_CHECKPOINT", "command": "Plain", "curEpoch": "5476333166395392", "durationSec": 0.000699541, "prevEpoch": "5476333100859392"}}
 db589497-764b-45eb-ab0c-d5ea03ab4cde | 2023-11-24 03:43:33.622+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_BARRIER", "command": "Plain", "curEpoch": "5476333231865856", "durationSec": 0.000150208, "prevEpoch": "5476333166395392"}}
 fac9942d-45de-42bd-b64d-a64ea088e105 | 2023-11-24 03:43:34.625+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_CHECKPOINT", "command": "Plain", "curEpoch": "5476333297598464", "durationSec": 0.00072525, "prevEpoch": "5476333231865856"}}
 a399701a-c8d9-4495-9712-20cf6271c12e | 2023-11-24 03:43:35.624+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_BARRIER", "command": "Plain", "curEpoch": "5476333363068928", "durationSec": 0.000285166, "prevEpoch": "5476333297598464"}}
 59adb71b-5219-4e04-a483-54cc73125120 | 2023-11-24 03:43:36.624+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_CHECKPOINT", "command": "Plain", "curEpoch": "5476333428604928", "durationSec": 0.00072925, "prevEpoch": "5476333363068928"}}
 bbcf96ca-37b9-414d-9825-88240a8b6768 | 2023-11-24 03:43:37.623+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_BARRIER", "command": "Plain", "curEpoch": "5476333494075392", "durationSec": 0.000203709, "prevEpoch": "5476333428604928"}}
 c90ec544-30bf-459d-b110-f1481c0c4a22 | 2023-11-24 03:43:38.623+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_CHECKPOINT", "command": "Plain", "curEpoch": "5476333559676928", "durationSec": 0.000251042, "prevEpoch": "5476333494075392"}}
 f1f65fc3-360f-4c44-a69b-9757ca996122 | 2023-11-24 03:43:39.625+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_BARRIER", "command": "Plain", "curEpoch": "5476333625278464", "durationSec": 0.000460625, "prevEpoch": "5476333559676928"}}
 9f8715ac-46fd-4034-808e-168dda20e0c7 | 2023-11-24 03:43:40.623+00:00 | BARRIER_COMPLETE | {"barrierComplete": {"barrierKind": "BARRIER_KIND_CHECKPOINT", "command": "Plain", "curEpoch": "5476333690748928", "durationSec": 0.000439125, "prevEpoch": "5476333625278464"}}
(10 rows)

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

I am a little bit suspicious about this PR. Because other event kinds are truely critical failures, while this one is more like a metric to me, even not worth a INFO-level log.

CreateStreamJobFail: the cleared tables and errors during foreground table creation.
DirtyStreamJobClear: the cleared tables during meta node recoveries.
BarrierComplete: the completed epoch, including latency collected in meta node.
InjectBarrierFail: the RPC error received by meta node.
CollectBarrierFail: the RPC error received by meta node.

Btw, I have once discussed with @BugenZhao about whether we can introduce a mini metrics store in Meta node, to keep some important metrics for dashboard without need of Prometheus.
If your motivation is to view the metrics without Prometheus, I think this might be better than recording BarrierComplete in event table.

Btw, I have once discussed with @BugenZhao about whether we can introduce a mini metrics store in Meta node, to keep some important metrics for dashboard without need of Prometheus.
If your motivation is to view the metrics without Prometheus, I think this might be better than recording BarrierComplete in event table.


Copying larger image files leads to errors when using versioning

I setup a new Jigsaw project and wanted my images to be versioned by Mix as well.
So I added a copy step to the webpack.mix.js as I have it in some of my Laravel projects:
const mix = require('laravel-mix');
require('laravel-mix-jigsaw');

mix.disableSuccessNotifications();
mix.setPublicPath('source/assets/build');

mix.copyDirectory('source/_assets/img', 'source/assets/build/img');
mix.jigsaw()
    .js('source/_assets/js/main.js', 'js')
    .css('source/_assets/css/main.css', 'css', [
        require('postcss-import'),
        require('tailwindcss'),
    ])
    .options({
        processCssUrls: false,
    })
    .version();

However, this leads to errors when I add image files to the img folder that are larger than a few KB.
When I remove the jigsaw() step from Mix, it works fine.

It also works fine with jigsaw when  I remove the versioning. So there seems to be some incompatibility.
I'm using:

Jigsaw 1.3.41
laravel-mix-jigsaw 1.5.0
laravel-mix 6.0.43

Can you update to laravel-mix-jigsaw v2 and let me know if you still have this issue?

Sorry for the late response.
Setting the version for laravel-mix-jigsaw to 2.0 actually breaks the build process. npm run watch will no longer start a server in that case.
Also I noticed 2.0 is not marked as released in GitHub. Is this production ready? If so, is there anything else I need to change to make 2.0 work?

v2 is tagged and production-ready, yes. Looking at your config I don't think you'd need to change anything no, what errors are you seeing now? The v2 updates were made in #21, maybe something in there will help you debug or figure out where the issue is coming from?


Mechanism for Handling Zero Width Joiners

Certain graphemes like "🙇♀" (which you might see as two separate graphemes) are comprised of three code points:

🙇 U+1F647 "Person Bowing Emoji"
U+200D "Zero Width Joiner"
♀ U+2640 "Female Sign"

So the single grapheme is the character sequence b"\xf0\x9f\x99\x87\xe2\x80\x8d\xe2\x99\x80".
Steps to Reproduce
If there is enough space in the buffer, everything is fine:
Cli { buffer_size: 10, reserve: 0, finish_with: None, truncate_with: None, debug: true, input: "🙇\u{200d}♀" }
🙇♀
+ version: 0.1.2
+ written_len: 10
+ truncated: false
+ output_bytes: [240, 159, 153, 135, 226, 128, 141, 226, 153, 128]
+ input: 🙇♀
+ input_bytes: [240, 159, 153, 135, 226, 128, 141, 226, 153, 128]

But shrinking the buffer to 9 is a bit odd:
Cli { buffer_size: 9, reserve: 0, finish_with: None, truncate_with: None, debug: true, input: "🙇\u{200d}♀" }
🙇
+ version: 0.1.2
+ written_len: 7
+ truncated: true
+ output_bytes: [240, 159, 153, 135, 226, 128, 141]
+ input: 🙇♀
+ input_bytes: [240, 159, 153, 135, 226, 128, 141, 226, 153, 128]

The output string is b"\xf0\x9f\x99\x87\xe2\x80\x8d", which includes the zero width joiner character, but it joins nothing.
Potential Fixes
It is not entirely clear what should happen here.
Option 1: Do Nothing
This might be perfectly okay. The output is still valid UTF-8 and every decoder should be able to read it. This library only guarantees UTF-8, not that the output is a sensible grapheme.
Option 2: Cut Off the Zero Width Joiner
Another option is to drop off the trailing ZWJ, leaving 🙇 b"\xf0\x9f\x99\x87\xe2". This leaves the idea of "person bowing," but drops the gender modifier.
Cli { buffer_size: 9, reserve: 0, finish_with: None, truncate_with: Some("..."), debug: true, input: "🙇\u{200d}♀" }
🙇...
+ version: 0.1.2
+ written_len: 7
+ truncated: true
+ output_bytes: [240, 159, 153, 135, 46, 46, 46]
+ input: 🙇♀
+ input_bytes: [240, 159, 153, 135, 226, 128, 141, 226, 153, 128]

This has the unfortunate side-effect of potentially changing the meaning of the written output. The family of 4 written by b"\xf0\x9f\x91\xa8\xe2\x80\x8d\xf0\x9f\x91\xa9\xe2\x80\x8d\xf0\x9f\x91\xa6\xe2\x80\x8d\xf0\x9f\x91\xa6" showing up as 👨👩👦 might change the interpretation. The cutoff of the second child is conveyed by the Err for truncation at least.
Option 3: Cut Off the Entire Trailing Emoji
If we assume the input to WriteBuf::write_str is meant to be a sequence of graphemes (which is probably a fair assumption), then the right choice is to remove the entire 🙇♀ as a unit.
Cli { buffer_size: 9, reserve: 0, finish_with: None, truncate_with: Some("..."), debug: true, input: "🙇\u{200d}♀" }
...
+ version: 0.1.2
+ written_len: 3
+ truncated: true
+ output_bytes: [46, 46, 46]
+ input: 🙇♀
+ input_bytes: [240, 159, 153, 135, 226, 128, 141, 226, 153, 128]

This is not an unreasonable ask if the only character of this nature is the zero width joiner. We can handle one of these funky characters, but we probably do not want to get into the business of handling arbitrary modifiers. My personal suspicion is that there are other such Unicode sequences that would fall into this category. For example: should the characters between the left-to-right mark U+200E and right-to-left mark U+200F be considered atomic? What about the opposite way?

Going with Option 1 here, since there isn't a good way to support truncation based on semantics. Maybe there is a way to have a user-provided hook here.


Object Overlapping and Self Overlapping Bug

when viewing shapes overlapping other shapes or even themselves at extreme angles, strange artifacts tend to occur. It's best explained with pictures.
Maybe I'm just misunderstanding and this is the nature of an acceptably fast step size, but it seems pretty strange, such as the exponential artifact on the cube.

This is an undersampling issue. Increase the total number of samples per ray to get a good result.

I'm closing this as @mmmovania's answer is correct.


Exclude INFORMATION_SCHEMA and information_schema from schemer.go

I am using clickhouse-operator 0.16.0 for test. And I got a question during the test.
Prerequisite: My CHI is using high version ClickHouse, altinity/clickhouse-server:latest
Result: Since the high version of clickhouse introduced database information_schema, I found that the operator would read the table in the information_schema and rebuild it under the default database.
Why does this happen？
Looking forward to your reply, Thanks.

Yes, it's a bug and should be fixed on 0.18.0

@su-houzhen , It is fixed in 0.17.0 already. See https://github.com/Altinity/clickhouse-operator/releases/tag/0.17.0


No option to delete a minister's issue available

Delete Requirements

[ ] delete issue option is available
[ ] prompt notes that all issue content - including associated actions - will be deleted
[ ] if confirmed the issue and associated actions is deleted

@calebissharp RAN099951

save draft -- no issues saving
added a minister's issue
filled required fields
no missing content identified in red
save draft = error saving
exited RUP
reoponed RUP
Save Draft = error

2nd time in added a minister's issue and got a "could not submit due to invalid fields" message...but it added the Issue on screen but I can't save
Deleted the existing issue = "could not submit due to invalid fields" = did not save draft --> exited RUP --> reopened RUP = Minister's Issue had been deleted.

@LisaMoore1 This may have just been caused by an error in the deployment. I can't reproduce this locally, so could you give this another try now that test is up-to-date?

@LisaMoore1 Actually hold on, I think I've found something broken. Let me try and fix it.

@calebissharp Could be unrelated but also got save error when deleting schedule row. In this case I tried to save multiple times (all with errors) and ended up with multiple copies of that year's schedule. This is one of those inconsistently reproducible problems. Kassia had it happen as well once but also couldn't make it happen again. I can make this one a separate issue if you'd like.

@LisaMoore1 Yes please.

@calebissharp No longer getting the error on delete row...or the other issues I was having above. Are you happy with where things are at with this one?

If you can delete minister issues without any problem, I'm good to close this issue.


Not working with VM Workstation on Windows

Really interested in this project so I tested on Windows 10 with the latest VM Workstation. I got this error
Traceback (most recent call last):
  File "C:\Python27\Scripts\mech-script.py", line 11, in <module>
    load_entry_point('mech==0.4.1', 'console_scripts', 'mech')()
  File "c:\python27\lib\site-packages\mech\__main__.py", line 92, in main
    operation(op='start', name=name, options={'gui':gui})
  File "c:\python27\lib\site-packages\mech\__main__.py", line 49, in operation
    method()
  File "c:\python27\lib\site-packages\mech\mech.py", line 43, in start
    vm = Vmrun(self.vmx)
  File "c:\python27\lib\site-packages\mech\vmrun.py", line 69, in __init__
    rh = _winreg.OpenKey( reg, r'SOFTWARE\VMware, Inc.\VMware Workstation' )
WindowsError: [Error 2] The system cannot find the file specified```

Hmm I actually wasn't able to reproduce this. What terminal emulator are you using?

I am using the Powershell terminal emulator that is now standard on Windows 10. I have tried running as an admin and as a regular user, same error.

Do you think you can check the registry for the key that VMWare Workstation installed?

Searching the registry I see these values when searching for vmware, there are more but figured I'd stop here to see if any of these are useful
Computer\HKEY_CLASSES_ROOT.nvram\VMware.VMBios\ShellNew
Computer\HKEY_CLASSES_ROOT\AppID\vmware-shell-ext-thunker.exe
Computer\HKEY_CLASSES_ROOT\Applications\vmplayer.exe
Computer\HKEY_CLASSES_ROOT\Applications\vmware.exe

I pulled a fix suggested in #9. Please reinstall and see if that fixes it for you.

I get past that error now, will continue testing, thanks for the prompt support and fix :)

Any updates here? Im going to install mech on my PC with windows 10 and hope it will work.

Well the issue is closed so I would hope that it's fixed. If it doesn't work for you, comment again and I'll reopen.


Replace pending dubbo-config-api hard coded value with constant and small refactoring

Replace pending dubbo-config-api hard coded values with constant and small refactoring to optimize code.

[ ] I have searched the issues of this repository and believe that this is not a duplicate.
[ ] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.0
Operating System version: xxx
Java version: xxx

Steps to reproduce this issue

xxx
xxx
xxx

Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps？
Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
Just put your stack trace here!

Merged to master.


Support in-repo addons and engines

With a config like:
stylelint: {
  syntax: 'scss',
  testFailingFiles: true,
  includePaths: [
    'lib/engine1/addon/styles',
    'lib/engine2/addon/styles',
    'lib/inrepoaddon1/app/styles',
    'lib/inrepoaddon2/app/styles'
  ]
}

I get this error
Error: Merge error: file addon.stylelint-test.js exists in tmp/broccoli_merge_trees-input_base_path-vQ7dMwvy.tmp/1 and tmp/broccoli_merge_trees-input_base_path-vQ7dMwvy.tmp/2
Pass option { overwrite: true } to mergeTrees in order to have the latter file win.
    at BroccoliMergeTrees._mergeRelativePath (node_modules/broccoli-merge-trees/index.js:278:17)
    at BroccoliMergeTrees.build (node_modules/broccoli-merge-trees/index.js:83:24)
    at node_modules/broccoli-plugin/read_compat.js:93:34
    at tryCatch (node_modules/rsvp/dist/rsvp.js:525:12)
    at invokeCallback (node_modules/rsvp/dist/rsvp.js:538:13)
    at publish (node_modules/rsvp/dist/rsvp.js:508:7)
    at flush (node_modules/rsvp/dist/rsvp.js:2415:5)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

ill take a look over the weekend to see how i can get it working for engines let you know

I've run into the same issue.  I have two in-repo engines and one in-repo addon that contains shared classes...
/lib
  /engine-one
  /engine-two
  /shared-classes

Without providing any configuration options, I noticed that the conditional check in lintTree passes twice, once for the main app and another for the in-repo-addon.  This is why it's presenting the error that everyone is seeing.  After making the following changes to index.js...
lintTree(type, true) {
  if (type === 'app' && tree.destDir === '/') {
    // unchanged code
    return mergeTrees(linted, { overwrite: true });
  }
}

And adding the following to the parent app's ember-cli-build.js file...
stylelint: {
  generateTests: true,
  includePaths: [
    'lib/engine-one/addon/styles',
    'lib/engine-two/addon/styles',
    'lib/shared-classes/app/styles'
  ]
}

...the build is now successful and all .scss files are linted correctly.
I don't know if this is the proper way to address this issue but it has fixed our build issues.  Figured I'd post this solution as an potential option and open it up to feedback.  I would be happy to submit a merge request as well.

ye would like to have a pull request for this, and/pr you able to write a
few unit tests as well/ make a demo app with this configuration working.
On Tue, Mar 20, 2018 at 5:16 AM Steve Bartnesky<EMAIL_ADDRESS>wrote:

I've run into the same issue. I have two in-repo engines and one in-repo
addon that contains shared classes...
/lib
/engine-one
/engine-two
/shared-classes
Without providing any configuration options, I noticed that the
conditional check in lintTree passes twice, once for the main app and
another for the in-repo-addon. This is why it's presenting the error that
everyone is seeing. After making the following changes to index.js...
lintTree(type, true) {
if (type === 'app' && tree.destDir === '/') {
// unchanged code
return mergeTrees(linted, { overwrite: true });
}
}
And adding the following to the parent app's ember-cli-build.js file...
stylelint: {
generateTests: true,
includePaths: [
'lib/engine-one/addon/styles',
'lib/engine-two/addon/styles',
'lib/shared-classes/app/styles'
]
}
...the build is now successful and all .scss files are linted correctly.
I don't know if this is the proper way to address this issue but it has
fixed our build issues. Figured I'd post this solution as an potential
option and open it up to feedback. I would be happy to submit a merge
request as well.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/billybonks/ember-cli-stylelint/issues/73#issuecomment-374380789,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABkGyOJI5So5dZkjAAyExNbenhxCDFgDks5tgCAugaJpZM4Pl92r
.

Just to update everyone on this thread, making some pull requests to ember-cli that will make styles first class citizens for linting that should resolve all quirks but at the same time it means i will depercate  includePaths

okay the easiest solution to this is to use this config
    stylelint: {
      includePaths: [
        'lib',
        ]
    }

@billybonks, I have multiple engines and addons under /lib.  Does it make a difference if you reference each directory directly instead of just the parent?
stylelint: {
  generateTests: true,
  includePaths: [
    'lib/engine01/addon/styles',
    'lib/engine02/addon/styles',
    'lib/engine03/addon/styles',
    'lib/addon/app/styles'
  ]
}

With this config, I still get the merge error during a build.

right now if you use lib/engine01/addon/styles and you have file style.scss the output will be
style.test.js, now if lib/engine02/addon/styles also has style.scss it will output the same file in the same virtual directory. so if you use the overwrite config you actually loose one of the tests.
but if you reference the parent lib then the above 2 files in the virtual directory will be
lib/engine01/addon/styles/style.test.js
lib/engine02/addon/styles/style.test.js
so they wont override. in theory i can move them after i generate the tests, but won't be able to work on that until 18april since i will be offline.
using the parent lib should be totally safe, the only thing i would look out for is if it increases your built times, because it broccoli will do a bit more processing but i think it shouldn't be very bad.

@billybonks, I confirmed this working on my end.  Specifying only the parent lib dir in the includePaths option showed a negligible difference in load times.  Thank you again for getting a workaround merged!  Hoping we get some traction in ember-cli repo for addressing this correctly 🤞

Howdy @billybonks! I ran into this today trying to upgrade from 2.2.0 to 4.0.0. I got the error in an internal addon that has scss files in both app/styles as well as tests/dummy/styles. The error was:
➜  yapp-ember-kit git:(chore/release-it) ✗ ember s
Build Error (BroccoliMergeTrees)

[BroccoliMergeTrees] error while merging the following:
  1.  [SimpleConcatConcat]
  2.  [SimpleConcatConcat]
Merge error: file true.stylelint-test.js exists in /var/folders/vs/8wls8rjn4gqd4m2ydxywp6v00000gn/T/broccoli-92843PN6bPkEhpOtY/out-039-simple_concat_concat and /var/folders/vs/8wls8rjn4gqd4m2ydxywp6v00000gn/T/broccoli-92843PN6bPkEhpOtY/out-043-simple_concat_concat
Pass option { overwrite: true } to mergeTrees in order to have the latter file win.

Stack Trace and Error Report: /var/folders/vs/8wls8rjn4gqd4m2ydxywp6v00000gn/T/error.dump.2d289c976fbaf6253f66e56347290ca4.log

Hey, will take a look at this again on the weekend.

@billybonks thanks. happy to remote pair on it if you want. you can ping me on discord.

Hallo @billybonks! I just wanted to add to this thread and state that this error is still prevalent in version 4.0.0, and also to add a quick workaround for anyone who is running into this issue.
While working on adding ember-cli-stylelint in an addon, I received the following error:
Build Error (BroccoliMergeTrees)

[BroccoliMergeTrees] error while merging the following:
  1.  [SimpleConcatConcat]
  2.  [SimpleConcatConcat]
  3.  [SimpleConcatConcat]
Merge error: file true.stylelint-test.js exists in /var/folders/cq/gz2xyllj2714wz0wtd96x7700000gp/T/broccoli-65859uoOyr5SOMprb/out-023-simple_concat_concat and /var/folders/cq/gz2xyllj2714wz0wtd96x7700000gp/T/broccoli-65859uoOyr5SOMprb/out-028-simple_concat_concat
Pass option { overwrite: true } to mergeTrees in order to have the latter file win.

As a workaround, I went to ./node_modules/ember-cli-stylelint/index.js and modified the line:
return mergeTrees(linted);
to:
return mergeTrees(linted, {overwrite: true});
which ultimately fixed the error. Hope this helps others who might run into this issue!

I've run into the same issue with an internal addon. I think the correct solution is to set group: false.
However this merge https://github.com/billybonks/ember-cli-stylelint/commit/33b63a832bce64487c759a584446319f0e4c3c41 seems to prevents anything but the default.
I assume the intention was to default only if undefined
this.styleLintOptions.group = this.styleLintOptions.group === undefined ? true : this.styleLintOptions.group;

vs always forcing true
this.styleLintOptions.group = true;

@billybonks can you confirm? Any chance this could be patched? 🙏


Install addon as devDependency in Readme

Hi,
react-storybook and all other addons document their install proccess as a devDependency.
I guess it's the right target.

Yep. Thanks.


Unexpected warnings about bit_rate when converting audio

Overview
Thanks for the great work on pyav! I'm using it to convert PCM audio to AAC in memory to convert a stream. It's working but I'm seeing unexpected warnings about bit_rate
Expected behavior
Default bit_rate would work or setting the bit_rate to an expected value would not give a warning
Actual behavior
The default gives this error:
Too many bits 16384.000000 > 6144 per frame requested, clamping to max

Then setting bit_rate to 128 gives this error (and setting it to 128 * 1024 gives the same error as above):
Bitrate 128 is extremely low, maybe you mean 128k

Build report:
Using av==10.0.0 in a requirements.txt file
Investigation
These warnings are printed in ffmpeg code
Reproduction
Here's a piece of sample code that's reading the data from files instead of a stream but it shows the issue:
import audioop
import sys
from fractions import Fraction

import av
import numpy
from av.audio.frame import AudioFrame

AUDIO_SAMPLE_RATE = 8000

def _main():
    print("Initializing")
    fake_output = av.open("/tmp/_alaw_to_aac.mp4", "w")
    audio_transcoder = fake_output.add_stream("aac", rate=AUDIO_SAMPLE_RATE, bit_rate=128, layout="mono")
    audio_data = AudioFrame(format="s16", layout="mono", samples=160)
    audio_data.rate = AUDIO_SAMPLE_RATE
    audio_data.time_base = Fraction(1, AUDIO_SAMPLE_RATE)

    for n in range(1000):
        data = open("{}/sample-{:03d}.alaw".format(sys.argv[1], n), "rb").read()
        linear = audioop.alaw2lin(data, 2)
        array = numpy.frombuffer(linear, "i2")
        audio_data.planes[0].update(array)
        audio_data.pts = 20 * n

        aac = b""
        pts = 0
        for p in audio_transcoder.encode(audio_data):
            pts = p.pts
            aac += bytes(p)
        if aac:
            print("Size:", pts, len(aac))

    print("Done")

if __name__ == "__main__":
    _main()

Versions

OS: Debian Bullseye
PyAV runtime: 3.9.16
PyAV build: 10.0.0 from pip
FFmpeg: N/A (doesn't output anything so I believe I'm using what's included in the wheel

Research
I have done the following:

[X] Checked the PyAV documentation
[X] Searched on Google
[X] Searched on Stack Overflow
[X] Looked through old GitHub issues
[x] Asked on PyAV Gitter
[x] ... and waited 72 hours for a response.

I tried running with older versions and they all had this same problem until version 8.1.0. I had to put in handling to make the pts in the input start at 0 (instead of 65), and then it output this message, but it worked:
Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
Encoder did not produce proper pts, making some up.

This is still an issue

This appears to be an issue with the underlying ffmpeg libraries


InternalServerException while deploying HuggingFace model on SageMaker

Background
We are working to deploy the AllenAI Cosmo XL model - https://huggingface.co/allenai/cosmo-xl for inference on SageMaker.
Our Approach
We are using a SageMaker notebook.
Instance: ml.p3.2xlarge
Kernel: conda_pytorch_p39
Code is directly from the HuggingFace website here: https://huggingface.co/allenai/cosmo-xl
We select Deploy -> Amazon SageMaker
Select Task=Conversational and Configuration=AWS
and copied the code into our notebook.
Error
The model is created and deployed.
But, when we run predictor.predict for model inference, we run into the following error
ModelError: An error occurred (ModelError) when calling the InvokeEndpoint operation: Received client error (400) from primary with message "{
  "code": 400,
  "type": "InternalServerException",
  "message": "Could not load model /.sagemaker/mms/models/allenai__cosmo-xl with any of the following classes: (\u003cclass \u0027transformers.models.auto.modeling_auto.AutoModelForSeq2SeqLM\u0027\u003e, \u003cclass \u0027transformers.models.auto.modeling_auto.AutoModelForCausalLM\u0027\u003e, \u003cclass \u0027transformers.models.t5.modeling_t5.T5ForConditionalGeneration\u0027\u003e)."
}

Relevant error messages from CloudWatch
2023-03-15T19:53:32,781 [INFO ] W-allenai__cosmo-xl-1-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Prediction error

2023-03-15T19:53:32,783 [INFO ] W-allenai__cosmo-xl-1-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle -   File "/opt/conda/lib/python3.8/site-packages/sagemaker_huggingface_inference_toolkit/handler_service.py", line 219, in handle

2023-03-15T19:53:32,784 [INFO ] W-allenai__cosmo-xl-1-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle -   File "/opt/conda/lib/python3.8/site-packages/transformers/pipelines/__init__.py", line 549, in pipeline

2023-03-15T19:53:32,785 [INFO ] W-allenai__cosmo-xl-1-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle -     raise ValueError(f"Could not load model {model} with any of the following classes: {class_tuple}."

2023-03-15T19:53:32,785 [INFO ] W-allenai__cosmo-xl-1-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - ValueError: Could not load model /.sagemaker/mms/models/allenai__cosmo-xl with any of the following classes: (<class 'transformers.models.auto.modeling_auto.AutoModelForSeq2SeqLM'>, <class 'transformers.models.auto.modeling_auto.AutoModelForCausalLM'>, <class 'transformers.models.t5.modeling_t5.T5ForConditionalGeneration'>)

Hello @KartikKannapur,
Thank you for opening the issue. The snippet ist current not up to date regarding the versions. Could you try with transformers version 4.26?

Hey @philschmid
Thank you for looking into this.
I updated the transformers version to 4.26
The SageMaker SDK version is 2.132.0
and I received the following error message

ValueError: Unsupported huggingface version: 4.26.0. You may need to upgrade your SDK version (pip install -U sagemaker) for newer huggingface versions. Supported huggingface version(s): 4.6.1, 4.10.2, 4.11.0, 4.12.3, 4.17.0, 4.6, 4.10, 4.11, 4.12, 4.17.

So, I updated the SageMaker SDK to version 2.140.1
and when I ran the predictor.predict for model inference, I ran into the same error as before.
Any suggestions?

Could you share your code how you deployed? i will try to reproduce it then.

from sagemaker.huggingface import HuggingFaceModel
import sagemaker

role = sagemaker.get_execution_role()
# Hub Model configuration. https://huggingface.co/models
hub = {
	'HF_MODEL_ID':'allenai/cosmo-xl',
	'HF_TASK':'conversational'
}

# create Hugging Face Model Class
huggingface_model = HuggingFaceModel(
	transformers_version='4.26.0',
	pytorch_version='1.13.1',
	py_version='py39',
	env=hub,
	role=role,
)

# deploy model to SageMaker Inference
predictor = huggingface_model.deploy(
	initial_instance_count=1, # number of instances
	instance_type='ml.m5.xlarge' # ec2 instance type
)

predictor.predict({
	'inputs': {
		"past_user_inputs": ["Which movie is the best ?"],
		"generated_responses": ["It's Die Hard for sure."],
		"text": "Can you explain why ?"
	}
})

Thanks @philschmid
Appreciate your support on this.

Ah i see. the task conversation is not correct here. Not sure why they added it manually. Can you switch the task to text2text-generation? then it should work.
Also from reading the model card: https://huggingface.co/allenai/cosmo-xl#how-to-use it might make sense if you create a custom infernece.py to get the "conversational" flow in to the generation method.

Understood. Thanks @philschmid
I'm going to go the custom inference.py route.


Fix build error for api generator on windows.

fix build error for api generator on windows:
APIGenerator.cpp.obj : error LNK2001: unresolved external symbol "public: static class QMap<class QString,class quick::TypeInfo::Enum *> quick::TypeInfo::List::EnumLookup" (?EnumLookup@List@TypeInfo@quick@@2V?$QMap@VQString@@PEAVEnum@TypeInfo@quick@@@@A)
build\API-Docs.exe : fatal error LNK1120: 1 unresolved externals`

Hey @maidamai0!
I spent some time on a bigger refactoring and was not able to merge your PR right away. The issue is now fixed (tested on macOS & windows). Unfortunately, I couldn't apply your PR since I had to change/cleanup the code quite a bit and there were just too many merge conflicts after that.. But still, thanks a lot for your time :)
Let me know if you have any issues with the latest commit!

It's good to hear you have fixed this issue, I'll close this.


Fix M/Date metadata

In addition to the MM field, out of curiosity does this also fix the DD field?
(Which appeared as "00" for January ZIM files, though the DD field should really be a number from 01 to 31.)

@holta fixed

@holta fixed

It should be getUTCDate() not getUTCDay()
(And does not need + 1!)


We are getting an Error while using the following Component for web.

This is the Error I am getting while trying to Run React-native-web in Website. I don't know, I thought this component is for Website. But I am facing many issues while Using the following Component with the Web Version. Please Go through the problem & Do the needful.
Thank you,
bundle.web.js:106913 Uncaught Error: Module parse failed: Unexpected token (107:12)
You may need an appropriate loader to handle this file type.
|     if (this.props.newWindow) {
|         return (
|
|
|
at Object. (bundle.web.js:106913)
at webpack_require (bundle.web.js:20)
at Object. (bundle.web.js:106201)
at webpack_require (bundle.web.js:20)
at Object.module.exports.createNavigationContainer (bundle.web.js:55481)
at webpack_require (bundle.web.js:20)
at Object. (bundle.web.js:32306)
at webpack_require (bundle.web.js:20)
at Object. (bundle.web.js:18089)
at webpack_require (bundle.web.js:20)
(anonymous) @ bundle.web.js:106913
webpack_require @ bundle.web.js:20
(anonymous) @ bundle.web.js:106201
webpack_require @ bundle.web.js:20
module.exports.createNavigationContainer @ bundle.web.js:55481
webpack_require @ bundle.web.js:20
(anonymous) @ bundle.web.js:32306
webpack_require @ bundle.web.js:20
(anonymous) @ bundle.web.js:18089
webpack_require @ bundle.web.js:20
(anonymous) @ bundle.web.js:63
(anonymous) @ bundle.web.js:66
bundle.web.js:18257 [WDS] Errors while compiling. Reload prevented.
errors @ bundle.web.js:18257
onmessage @ bundle.web.js:20204
EventTarget.dispatchEvent @ bundle.web.js:20384
(anonymous) @ bundle.web.js:21097
SockJS._transportMessage @ bundle.web.js:21095
EventEmitter.emit @ bundle.web.js:20300
WebSocketTransport.ws.onmessage @ bundle.web.js:23171
bundle.web.js:18263 ../node_modules/react-native-web-webview/src/index.js
Module parse failed: Unexpected token (107:12)
You may need an appropriate loader to handle this file type.
|     if (this.props.newWindow) {
|         return (
|
|
|
@ ../app/screens/PayTM.js 1:1101-1136
@ ../app/index.js
@ ../app/index.web.js
@ multi ../node_modules/webpack-dev-server/client?http://<IP_ADDRESS>:8082 babel-polyfill ../app/index.web.js
errors @ bundle.web.js:18263
onmessage @ bundle.web.js:20204
EventTarget.dispatchEvent @ bundle.web.js:20384
(anonymous) @ bundle.web.js:21097
SockJS._transportMessage @ bundle.web.js:21095
EventEmitter.emit @ bundle.web.js:20300
WebSocketTransport.ws.onmessage @ bundle.web.js:23171

Hello,
make sure to compile the lib through babel-preset-react-native. Is your webpack config correct ? See this example :)

Please try with v0.2.7.


Error in image bradrydzewski/php:5.*

In /etc/drone.d/phpenv.sh you add home variable '/home/ubuntu/phpenv/bin'. I think that should be '/home/ubuntu/.phpenv/bin' (note the . in phpenv), as I'm always getting the following error:
/etc/drone.d/phpenv.sh: line 21: phpenv: command not found

I'm still having this issue.   Anyone able to update the images?

closing because all images in github.com/drone/drone-images/* are being deprecated in favor of the official docker language stacks


Update aspnetcore runtime to Newtonsoft.Json 11

Tooling needs to stay at the version Visual Studio uses (currently 9), but could the runtime move up to 11? Thoughts @Eilon @JamesNK?
http://james.newtonking.com/archive/2018/02/22/json-net-11-0-release-1-net-standard-2-0-jsonconverters-json-path-and-more

Technically that'd be a breaking change because it'd bump up the major version of Json.NET in a minor version of ASP.NET Core.
@jamesnk - are there any serious breaking changes we'd need to be concerned about if we update?

These are the changes that I thought might be potentially breaking for people:

Change - Types that implement ISerializable but don't have [SerializableAttribute] are not serialized using ISerializable

Can change how types are serialized. Are people serializing/deserializing types that implement ISerializable with ASP.NET Core?

Change - Changed JsonProperty.MemberConverter to obsolete

Obsoleting a property that never did anything doesn't matter.

Change - Changed camel casing logic for all caps words to not leave last character capitalized

ASP.NET Core is using camel case by default so you should think about this - https://github.com/JamesNK/Newtonsoft.Json/pull/1467

Change - Changed enum serialization in dictionary keys to use EnumMemberAttribute

Devs could have dictionaries with enums as the key and the enum has the attribute on it.

@JamesNK thanks for the list. I don't think any of these are of very high concern to ASP.NET Core apps with regard to breaking changes.
@DamianEdwards - any thoughts on updating Json.NET? We have a few options:

Do nothing; we're using Json.NET 10.0.1 right now. Apps would need to update it themselves by lifting in their own csproj
Update the min-required Json.NET wherever we reference it (e.g. MVC's JSON formatter) to the latest 11.x release. This is a small breaking change for apps.
Update the templates (only) to use the latest Json.NET 11.x release. This is not a breaking change for anyone, but adds a line to the CSPROJ for all new projects.

With the new behavior of the default meta-package (Microsoft.AspNetCore.App) any direct hoisting of our dependencies beyond the exact version we close over causes a NuGet warning. A transitive lifting causes an error. This is in order to ensure customers are using a known good set when using our meta-package. This means option 3 is out of the question, as it would cause a warning. Option 1 means anyone wanting the new version will have to suppress the warning after adding the reference (by design). Option 2 means we get to state that 11 is the expected (and supported) version.
I'm inclined to go with a derivative of option 2, in that we update this dependency in the meta-package only. The versioning semantics of the meta-package are already special in that we apply a different set of rules when it comes to what constitutes a breaking change WRT to version changes, e.g. we drop TFMs in minors in the meta-package. I think it makes sense to update our (now) very small set of curated 3rd party dependencies (with sufficient testing of course) to help keep customers up to date in the default experience (i.e. using the meta-package).

Ah, so leave MVC/whatever referencing whatever, but change .App to use Json.NET 11.0.1?

Yep, exactly.

Lets just update to 11 across the board.

The reasoning to @davidfowl's comment is the nature of major changes in JSON.NET are generally incredibly minor anyway, plus only updating it in the meta-package adds a test burden that we don't really want to pay.

Let's add this to preview2 work please.

Fyi I'm going to release an 11.0.2 in less than a week with a couple of minor bug fixes for regressions.

@JamesNK should I wait for 11.0.2?

11.0.2 is out - https://github.com/JamesNK/Newtonsoft.Json/releases/tag/11.0.2
It undos one change in 11.0.1 that was causing backwards compat issues, two regressions, and fixes some random bugs. No new version planned for at least 6 months unless an urgent bug pops up.

Thanks @JamesNK ! I logged https://github.com/aspnet/Universe/issues/993 to track that update.


Add StateMachine property types to spec patching

Issue #, if available:
fix #1695
Description of changes:

Add StateMachine property types to spec patching to eu-west-2

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Ugh... you're right.  My fault. Let me fix this

ratio of PropertyTypes to ResourceTypes seems to roughly line up across the board now:
curl -s --compressed https://d1uauaxba7bl26.cloudfront.net/latest/gzip/CloudFormationResourceSpecification.json | jq '.ResourceTypes | length'
565
curl -s --compressed https://d1uauaxba7bl26.cloudfront.net/latest/gzip/CloudFormationResourceSpecification.json | jq '.PropertyTypes | length'
1549

grep 'ResourceTypes' src/cfnlint/data/ExtendedSpecs/*-*/06_ssm_service_removal.json | wc -l
     172
grep 'PropertyTypes' src/cfnlint/data/ExtendedSpecs/*-*/06_ssm_service_removal.json | wc -l
     527

grep 'ResourceTypes' src/cfnlint/data/ExtendedSpecs/*-*/07_ssm_service_addition.json | wc -l
     755
grep 'PropertyTypes' src/cfnlint/data/ExtendedSpecs/*-*/07_ssm_service_addition.json | wc -l
    1998


CI: Determine why using fallback cache breaks linting formfield

This only happens:
a) When the very last level of cache fallback is used:
      - name: "Cache deps"
        id: cache_deps
        uses: actions/cache@v2
        env:
          cache-name: cache-deps
        with:
          path: |
            **/node_modules
          key: ${{ runner.os }}-yarn-${{ env.cache-name }}-${{ hashFiles('**/yarn.lock') }}
          restore-keys: |
            ${{ runner.os }}-yarn-${{ env.cache-name }}-
            ${{ runner.os }}-yarn-
            ${{ runner.os }}-     # Fails when this line is present

b) Only fails linting for a single package:
> ng run ui-form-field:lint
$ node --max_old_space_size=8192 node_modules/eslint/bin/eslint.js 'libs/ui/form-field/**/*.{js,ts}'
$ npx stylelint 'libs/ui/form-field/**/!(*.spec).scss'
TypeError: Cannot read property 'type' of null
Occurred while linting /home/runner/work/terminus-oss/terminus-oss/libs/ui/form-field/src/lib/form-field/form-field-control.ts:76
    at isGetter (/home/runner/work/terminus-oss/terminus-oss/node_modules/eslint/lib/rules/getter-return.js:119:63)
    at onCodePathStart (/home/runner/work/terminus-oss/terminus-oss/node_modules/eslint/lib/rules/getter-return.js:150:34)
    at /home/runner/work/terminus-oss/terminus-oss/node_modules/eslint/lib/linter/safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (/home/runner/work/terminus-oss/terminus-oss/node_modules/eslint/lib/linter/safe-emitter.js:45:38)
    at processCodePathToEnter (/home/runner/work/terminus-oss/terminus-oss/node_modules/eslint/lib/linter/code-path-analysis/code-path-analyzer.js:377:30)
    at CodePathAnalyzer.enterNode (/home/runner/work/terminus-oss/terminus-oss/node_modules/eslint/lib/linter/code-path-analysis/code-path-analyzer.js:631:9)
    at /home/runner/work/terminus-oss/terminus-oss/node_modules/eslint/lib/linter/linter.js:936:32
    at Array.forEach (<anonymous>)
    at runRules (/home/runner/work/terminus-oss/terminus-oss/node_modules/eslint/lib/linter/linter.js:931:15)
error Command failed with exit code 2.
info Visit yarnpkg.com/en/docs/cli/run for documentation about this command.

It points to this line:
https://github.com/GetTerminus/terminus-oss/blob/56f4b31baf6b7bdaad5b89060f0efa3aace2a22e/libs/ui/form-field/src/lib/form-field/form-field-control.ts#L76
Possibly it's having trouble with the abstract property??

Fixed by busting old cache and syncing pr and release caches.


Add k8s auth plugins

Add "gcp" and "oidc" auth plugins. Verified that "gcp" plugin works for GKE. We still want to use client certs for testing since bazel does not allow invoking random commands from tests.

jenkins rebuild manager/presubmit

jenkins rebuild manager/presubmit

Jenkins job manager/presubmit passed

Jenkins job manager/e2e-smoketest passed


Introduce a new SILGenThunk.cpp

@gottesmm I hope this is not too disruptive for you. I have some PRs that will have conflicts in them as well now ;-) I'll be doing a lot of work on thunks for class resilience and inlineable, so having the relevant code in one file should help. I'm still not happy with some of the division of responsibility between SILGenThunk.cpp and SILGenPoly.cpp, but one step at a time.

@swift-ci Please smoke test

Also coming up soon, is gutting curry thunks. That should be nice...

@slavapestov No worries!


(feat) mat-timepicker

Bug, feature request, or proposal:
Feature request
What is the expected behavior?
Add a TimePicker like a DatePicker control, to allow users to enter a time through text input, or by choosing a time clock selector.
What is the current behavior?
Not possible
What are the steps to reproduce?
See examples here:
https://github.com/owsolutions/amazing-time-picker
http://www.material-ui.com/#/components/time-picker
https://codepen.io/alenaksu/pen/eNzbrZ
What is the use-case or motivation for changing an existing behavior?
Add a control to select a time with visual of material.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Latest version.
Is there anything else we should know?
Today is not available a beautiful control to select a time.

Duplicate of #5648

ok, my suggestion is a separated control to time, but is better if datepicker contemplate date, time or datetime.
thanks.

You can use amazing time picker (amazing-time-picker) for this purpose, and it is fully compatible with Angular 2-7 and Material design:
https://github.com/owsolutions/amazing-time-picker
Live demo:
https://owsolutions.github.io/amazing-time-picker
Thanks.


Add language tag and media type ABNF to grammar.abnf

This doesn't change the GEDCOM spec, only the grammar.abnf extracted file, to include ABNF extracted/derived from the RFCs referenced in the GEDCOM spec for language tags and media types.
This addresses the second bullet in the action item list at the bottom of issue #418
I filed issue #438 while working on this, but this PR could be merged without addressing that issue.

Agreed per meeting 22 FEB 2024


Сluster MapView.Markers on large scale

how to use marker clusters to display a large number of markers on a map ?
https://developers.google.com/maps/documentation/javascript/marker-clustering

@machard

I used https://github.com/mapbox/supercluster
Here is a great gist showing how to use with React-Native https://gist.github.com/i-tu/05e79737adfe36935ec869125a686f82

Duplicate #213


Support Pac4j 5

When booting this with Pac4J 5, we're getting org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: 'java.lang.Object org.pac4j.core.engine.SecurityLogic.perform

You can't use pac4j v5 with jax-rs-pac4j as it has not been upgraded yet.

yes, I'm aware of that. I have seen this in the pom. I was wondering when you're planning to upgrade jax-rs-pac4j to be usable with pac4j 5.

It's not planned yet. After this summer for sure.


Update readme

Can the commands be ordered same as the paper? For example the last command actually appears before some of the others in terms of paper order.

Of course.  I apparently missed a couple.


Support for Pimple 2+

I'm trying to use Silex with another library, that needs Pimple 2 or 3. Since Silex needs Pimple 1 I can't install Silex at all.
Any idea on fixing this?

Use v2.0.x-dev (the master branch), it uses Pimple 3.
Silex 1 won't be compatible with Pimple 2+ because of the API changes.

That is impossible as well, because the master branch requires PHP 5.5+ and I have PHP 5.4. Not sure which PHP version the users of app I'm trying to create will have.
For now I try to remove dependency from Pimple on the other library I'm trying to use to make Silex happy.

Well, you should update your PHP because PHP 5.4 reached end of life 2 month ago.

Yeah, I know. Unfortunately I have no idea what PHP versions people use on their development machines and that's why I keep PHP version requirements to the minimum to reach broader developer audience.

Any serious developer should not use an EOL version of PHP so simply ignore the audience that is not updating and require 5.5+. Lots of libraries require it too and relying on outdated packages is a huge security risk.

@aik099 we cannot support Pimple 2/3 in Silex 1.x because of changes in how shared services are defined. Shared services is the new default. Also ServiceProvider interface is different and requires Pimple\ServiceProviderInterface.

Closing as the whole point of Silex 2 is to support Pimple 2/3. And as said by @henrikbjorn, there is no way to support both Pimple 1 and Pimple 2/3 in the same code base.

I have a hack for this. Try specific commit, and exactly #bce2a5dc5931411ce319ebb470b1f4132cfddf08.
So it will be
  "silex/silex": "dev-master#bce2a5dc5931411ce319ebb470b1f4132cfddf08",

in your composer.lock. Probably does not work completely correct, but for the basic usage - it's perfect.

@fabpot Silex3 qui utilisera Pimple3 est prévu pour quand ?

@silverpark Silex 2 already supports Pimple 3 and is not out yet. I'm not sure there is any plan for Silex 3 yet (Silex 2 has yet to be released)

Yes but silex don't use pimple3, exemple :
class Application extends \Pimple

The best way I think is use pimple3 for exemple :
public function register(Application $app)

to
use Pimple\ServiceProviderInterface;

public function register(ServiceProviderInterface $app)

And we can use ServiceProviderInterface of Pimple3 and not Silex.
More, the service provider can be use for other framework who implements register idea from silex.

A concrete example, I have create a project with component symfony console, but I would like use the dependency injection with pimple3 in the case of implements silex in the futur in my project.
I have create a project wrapper symfony console for set the container pimple in all command, look this : https://github.com/silverpark/WrapperPimpleSymfony2Console

@silverpark you have to wait for Silex 2.0

Ok, when ?

Only Fabien knows.


Should mention needing the Beta Channel version of Word for CLI

According to the office-addin-dev-settings documentation (https://www.npmjs.com/package/office-addin-dev-settings#webview), it's required to be in the Beta Channel for the CLI functionality to work.
There is no mention of the Beta Channel on this page. Unfortunately, as I wasn't able to get the CLI version to work regardless, I don't know whether Beta is actually required or not.

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

ID: 47b7b417-12e6-193f-6b89-37e088b31dbc
Version Independent ID: df705bd2-5f2f-2c84-0519-fca9a3c45d71
Content: Internet Explorer 11 testing - Office Add-ins
Content Source: docs/testing/ie-11-testing.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

It looks like Office clients will not respect the reg key setting created by the office-addin-dev-settings command in main M365 delivery channels.  I remember seeing this explained in a no so obvious place, but I can't recall (or find) where that was or what specific channels (File=>Account=>Update Channel) the setting is honored in.  We should get this cleared up and documented better.

I found one place it was mentioned in documentation: https://learn.microsoft.com/en-us/office/dev/add-ins/testing/ie-11-testing.  This information should be explained in more places.

@sureshjoshi I'm not clear on what your issue is. The requirement for Beta is mentioned in the page where you raised this issue. Here is a screen shot.

@Rick-Kirkham I think the issue is solved. When I raised it (Dec 2021), that mention wasn't in the docs - but it looks like it was added Oct 2022: https://github.com/OfficeDev/office-js-docs-pr/commit/b0794feaf581616305d4bcd5d5480a13a3b077ac
I'm guessing this can be closed now?


Information on compiling addons on IBM PPC system, under Conda

I wanted to shared the steps to compile addons with a Conda environment that loads TF, CUDA, CUDNN
Cuda Driver and Hardware
Driver Version: 440.33.01
CUDA Version: 10.2
GPU: Tesla V100
Conda Environment
tensorflow                2.1.3
tensorflow-gpu            2.1.3
cudatoolkit               10.2.89
cudatoolkit-dev           10.2.89
cudnn                     7.6.5_10.2
bazel                     0.29.1
Process
to meet addons requirements based on versions of installed CUDA, Tensorflow versiosn, we need to install 0.9.1 version of addons
activate conda environment with proper versions of tensorflow, cuda, cudnn
git clone https://github.com/tensorflow/addons.git
cd addons
git checkout tags/v0.9.1
set environment variables
export TF_NEED_CUDA="1"
export TF_CUDA_PATHS=$CONDA_PREFIX/cuda      <---(this was the critical step)
export TF_CUDA_VERSION="10"
export TF_CUDNN_VERSION="7"
export CUDA_TOOLKIT_PATH=$CONDA_PREFIX
export CUDNN_INSTALL_PATH=$CONDA_PREFIX
python3 ./configure.py
The following applies for v0.9.1 of the build...
edit build_deps/toolchains/gpu/crosstool/BUILD.tpl
add the "ppc" line to the following block
cc_toolchain_suite(
name = "toolchain",
toolchains = {
"local|compiler": ":cc-compiler-local",
"ppc": ":cc-compiler-local",
"k8": ":cc-compiler-local",
},
)
run build and install
bazel build --enable_runfiles build_pip_pkg
bazel-bin/build_pip_pkg artifacts
pip install artifacts/tensorflow_addons-*.whl

Some other conda packages https://anaconda.org/search?q=Addons+tensorflow

I didn't know of those packaging channels that support Addons. Given our availability I think it's best we let the community handle Conda builds (same thing TF core does, but Anaconda does it). Closing this as we have no way to test CI for a power PC build.
Thanks for posting this though I'm sure it'll be helpful for others. I wouldn't be opposed to a PR which adds this either since it can't really hurt the existing builds. Closing for now but happy to review PR if there's community interest.


Please put a button to "Edit Account" on this page.... 😅

Next to that existing Creat Diagram button.  The buttons should fluidly or flex-boxedly wrap and stack in a responsive way for all screen sizes.
BSS heavy work
For the link-button's href use:
{% url 'edit_profile' %}
(note the single quotes there)
Before I was using internal links in BSS that get converted to django urls, but somethign fucked up with the export script, but this way works, these generic urls pass through the export script unchanged.

Done


Error setting mode as multi_process

Version: 3.0.2
OS: Android 14
Using new architecture
Error: Value is a number, expected a String

when using
import { MMKV, Mode } from "react-native-mmkv";
const database = new MMKV({ mode: Mode.MULTI_PROCESS });

Setting mode to MULTI_PROCESS (as a string) makes it work, but Mode enum is expected so Typescript complains.

Interesting. I'm guessing this is a codegen bug

fixed in https://github.com/mrousavy/react-native-mmkv/pull/754 🔥


Ruby [Final Steps]

BTW, in the same way you have pip available for python, you'll most likely want to have bundler available for ruby, which is just a gem you can install with $ gem install bundler. It's possible to specify where gems will be installed via the bundle config command.


Add conda auto build via CircleCI

Adding automatic conda package generation

Well that seemed to work, so I'll merge so I can get it to build a new package in the coecms channel https://anaconda.org/coecms


Testing new sumstats format - validation in Dev environ

I've had some intermittent issues when uploading submission template in Dev environment, testing new sumstats format.

30854688
template: https://app.zenhub.com/files/2995118/115bc6fd-1ef3-4881-8b5d-e6f223cdaccc/download
Error: No error. Just continually 'validating' over days.
note: genotyping technology is wrong in the template but this should return an error explaining as such.

PMID 30610198
63c94aced3c06e0001dc4191
template: https://app.zenhub.com/files/2995118/f1d009f6-006f-4952-96bf-8fa9bd125463/download
Error:
pvalue0_validtest-shouldpasswithtemplate.tsv: There is a problem on our side, please contact<EMAIL_ADDRESS>for further advice.

But I've validated the file offline and have also successfully submitted this file through other submissions.

@earlEBI Analysed both the submissions ,
for  Pmid -> '30854688' the sumstats submission was failing due to Pattern mismatch issue with regards to Read me text column , there was a non ascii character & the pattern validation which has been written to handle non ascii characters for Read me column is running in infinite loop , James will look to fix that pattern.
In order to continue your testing can you remove the non ascii value from the Read me text column in the row with GCST 'GCST007737'
for Pmid  '30610198' -> this has to be analysed from sumstats side @jdhayhurst can you please check for callbackId 'WGRtQrgD' what is the error in sumstats service

@sajo-ebi If you can reset PMID 30854688 / stop the ongoing validation, I'll remove the ascii value and reupload. Or I can just try with a new PMID.

Is this resolved @earlEBI ?


Openzeppelin vulnerability fixes

Vulnerability, CWE-502, CVSS 7.3, high, https://app.snyk.io/vuln/SNYK-JS-OPENZEPPELINCONTRACTS-2320176

Fixed in<EMAIL_ADDRESS>
Vulnerability, CWE-502, CVSS 7.3. high, https://app.snyk.io/vuln/SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-2320177

Fixed in<EMAIL_ADDRESS>
Vulnerability, CWE-686, CVSS 5.3, medium, https://app.snyk.io/vuln/SNYK-JS-OPENZEPPELINCONTRACTS-2336323

Fixed in<EMAIL_ADDRESS>
Vulnerability, CWE-686, CVSS 5.3, medium, https://app.snyk.io/vuln/SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-2336322

Fixed in<EMAIL_ADDRESS>
Vulnerability, CWE-189, CVSS 4.3, medium, https://app.snyk.io/vuln/SNYK-JS-OPENZEPPELINCONTRACTS-1921095

Fixed in<EMAIL_ADDRESS>
Vulnerability, CWE-189, CVSS 4.3, medium, https://app.snyk.io/vuln/SNYK-JS-OPENZEPPELINCONTRACTSUPGRADEABLE-1921094

Fixed in<EMAIL_ADDRESS>

Fixed in the merge https://github.com/KlimaDAO/klimadao-solidity/pull/6


CAN Driver: Allow user to configure acceptance filter

Currently when the driver is initialized it automatically configures the acceptance filter to accept ALL messages. This function needs to be expanded so it can let the user configure their own filtering scheme.

Will close this until this is requested as a feature of the driver.


eo:platform and eo:instrument may have multiple values

eo:platform and eo:instrument are not necessarily single-value fields. Eg, for MODIS MCD* datasets platform is MODIS Terra + MODIS Aqua, and for combined Sentinel-1 or -2 data the platform is both S1A/S1B etc. As for the instrument, Landsat 8 has both OLI and TIRS instruments, and the main L8 product has bands from both.

We have a similar problems with the licenses and tried to solve it by using SPDX license expressions which allows something like Apache-2.0 OR CC-BY-4.0. I'm not suggesting that we use exactly this, but I think both fields mentioned by you should somehow stick to be strings as they are used inside the Items properties as well, which are not allowed to hold arrays or objects. Therefore we may just add a recommendation how to generally separate fields with multiple values, e.g. | or / or ;.

I like @m-mohr's thinking on this. Having a single value field to search on makes things a lot easier / gives us a simpler spec.
Also I think 'constellation' in #169 was also supposed to somehow help S1A vs S1B, though I still need to see more concrete examples to really understand it.

By the way, the eo extension already has a paragraph on this:

eo:instrument is the name of the sensor used, although for Items which contain data from multiple sensors this could also name multiple sensors. For example, data from the Landsat-8 platform is collected with the OLI sensor as well as the TIRS sensor, but the data is distributed together and commonly referred to as OLI_TIRS.

This could be improved, for sure, e.g. by describing how multiple values should be separated.

For collections and catalogs it is solved with the summaries as proposed in #413. For Items, I think need further evaluation.

So the summaries now allow this for collections. The question here is whether there are really many Items that have multiple values for platform and instrument? Usually Sentinel-2A and Sentinel-2B images would be a separate items. And for "merged" imagery/mosaics/... I'm not sure whether it's worth the effort to change anything here. It could just be a string such as "Instrument1 + Instrument2" or so. Anyway, I think we should come to a decision before 1.0.


Reinstall command

[x] I have added an entry to docs/changelog.md

Summary of changes
Adds a reinstall command to only reinstall one venv.
Closes #256
Test plan

Tested by running
pipx install pycowsay
pipx reinstall pycowsay

It would be simple to make this take multiple argument for multiple venvs.  I kept it at one venv because that matched the other pipx sub-commands.

Adds a reinstall command to only reinstall one venv.

Any reason why just not make this the behaviour of pipx install -f or pipx install --overwrite?

Any reason why just not make this the behaviour of pipx install -f or pipx install --overwrite?

One difference would be that this completely reinstalls the venv, including re-injecting all of the injected packages, while install is currently only charged with affecting the main package of a venv.
This command also reuses all of the original options for the venv and installed packages like pip_args, venv_args, install_dependencies without forcing you to re-supply them on the command line, like install might imply you need to do.

I also just thought it would make sense to the user as an analog to upgrade / upgrade-all.


Does Ghidra tell apart local vars at the same stack offset? (with pdb info supplied)

Say I have this stack layout (from a pdb-generated XML)
        <function name="MY_FUNCTION" address="0x27600" length="0xc6f">
            <stack_variable name="this" kind="ObjectPointer" offset="0x0" datatype="MY_NICE_DATATYPE" length="0x0" />
            <stack_variable name="dwSize" kind="Parameter" offset="0x4" datatype="ulong" length="0x0" />
            <stack_variable name="CommBuff" kind="Parameter" offset="0x8" datatype="char *" length="0x0" />
            <stack_variable name="dcoFromID" kind="Parameter" offset="0xc" datatype="ulong" length="0x0" />
            <stack_variable name="dcoReceiveID" kind="Parameter" offset="0x10" datatype="ulong" length="0x0" />
            <stack_variable name="fromHold" kind="Parameter" offset="0x14" datatype="int" length="0x0" />
            <stack_variable name="msg_str" kind="Local" offset="0xffffff9c" datatype="char[100]" length="0x0" />
            <stack_variable name="InContent" kind="StaticLocal" offset="0x0" datatype="char *" length="0x0" />
            <stack_variable name="InContentSize" kind="StaticLocal" offset="0x0" datatype="ulong" length="0x0" />
            <stack_variable name="sack" kind="Local" offset="0xfffffe80" datatype="MSGFORMAT_ACKNOWLEDGE_GUARANTEED" length="0x0" />
            <stack_variable name="txpingpong" kind="Local" offset="0xfffffe80" datatype="MSGFORMAT_LATENCY" length="0x0" />
            <stack_variable name="msg" kind="Local" offset="0xfffffe9c" datatype="char[256]" length="0x0" />
            <stack_variable name="txpingpong" kind="Local" offset="0xfffffe80" datatype="MSGFORMAT_LATENCY" length="0x0" />
            <stack_variable name="msg" kind="Local" offset="0xfffffe9c" datatype="char[256]" length="0x0" />
            <stack_variable name="NextSerialNumber" kind="Local" offset="0xfffffe80" datatype="uint" length="0x0" />
            <stack_variable name="dropcount" kind="StaticLocal" offset="0x0" datatype="uint" length="0x0" />
            .... line numbers

As you can see, some local vars are at the same offset. They're pushed presumably in different points of the execution so they don't overlap.
My question is: can Ghidra figure out the order of pushes and create all the locals accordingly? Or it just chooses one and stick with it?

We cannot currently do what you are asking.  There are two parts to this.  One is understanding what is going on in the source through to compile.  The other is in the ability to model or incorporate what is going on.
My assumption was that there are local scope variables where the stack space is getting reused.  I had some source code where I was doing this with static locals but not with regular locals, so I modified my source to include this example.  I have yet to figure out appropriate compile options to cause the stack to be reused.  I had been using VS2012, but also just tried 2019.  However, I did find similar reuse of stack space in one of the linked libraries in my 2019 compile. I'll continue to investigate ways for me to see this happen with source and compile options that I control.  If anyone else knows what to do, I'd be interested.
The example I have shows:
        <function name="?type_case_c_tchar@?$output_processor@_WV?$stream_output_adapter@_W@__crt_stdio_output@@V?$positional_parameter_base@_WV?$stream_output_adapter@_W@__crt_stdio_output@@@2@@__crt_stdio_output@@AAE_N_W@Z" address="0x30597" length="0xad">
            <stack_variable name="this" kind="Local" offset="0x0" datatype="__crt_stdio_output::output_processor<wchar_t,__crt_stdio_output::stream_output_adapter<wchar_t>,__crt_stdio_output::positional_parameter_base<wchar_t,__crt_stdio_output::stream_output_adapter<wchar_t> > > *" length="0x0" />
            <stack_variable name="__formal" kind="Local" offset="0x8" datatype="wchar" length="0x0" />
            <stack_variable name="wide_character" kind="Local" offset="0xfffffffc" datatype="wchar" length="0x0" />
            <stack_variable name="local_buffer" kind="Local" offset="0xfffffffc" datatype="char[2]" length="0x0" />

The pdb.xml format does not currently contain the information necessary to see what is happening or pass this information along, but with information that I have from my current PDB work, I can see that there are defined ranges for each variable name.
wide_character 0x305ef - 0x30618
local_buffer 0x30619 - 0x30625

So we could have this information in the future.
Regarding applying this information in Ghidra, we do have the ability to do this for register variables, but currently cannot do this for stack variables.  If you find a place in the program Listing (disassembly) where a value is being assigned to a register, you can right-click on it, choose References -> Create Register Reference.  The option is only available on register assignment operations and should allow new reference names at each location where this reference can be created.
Presumably, there should be a way to also do this for stack variables, but they are handled a little differently than registers (which are treated as globals) and would also need to be handled by the decompiler.  I do not know how much work that could entail.

Thanks for the info! That's great to know


NormalizedAnchorPoint don't work in MapControl

if use maps:MapItemsControl.ItemTemplate, NormalizedAnchorPoint don't work.
If use without MapItemsControl - work correctly.

I had no problems with NormalizedAnchorPoint in MapItemsControl.ItemTemplate
                <maps:MapItemsControl x:Name="mapItems" ItemsSource="{Binding penNumberText}">

                       <maps:MapItemsControl.ItemTemplate>

                             <DataTemplate>

                                    <Border Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">

                                           <TextBlock x:Name="mapTextBlock" Text="{Binding PenNumber}"

                                                    FontSize="12"

                                                    maps:MapControl.Location="{Binding Location}"

                                                    maps:MapControl.NormalizedAnchorPoint="{Binding NormalizedAnchorPoint}">

                                           </TextBlock>

                                    </Border>

                             </DataTemplate>

                       </maps:MapItemsControl.ItemTemplate>

                </maps:MapItemsControl>

From: Dmitry<EMAIL_ADDRESS>Sent: Thursday, December 24, 2015 7:37 AM
To: Microsoft/Windows-universal-samples<EMAIL_ADDRESS>Subject: [Windows-universal-samples] NormalizedAnchorPoint don't work in MapControl (#252)
if use maps:MapItemsControlItemTemplate, NormalizedAnchorPoint don't work
If use without MapItemsControl - work correctly
—
Reply to this email directly or view it on GitHub https://github.com/Microsoft/Windows-universal-samples/issues/252 .  https://github.com/notifications/beacon/AJ8_d5GJ50WiSbuBPrO2oHVKB1I2WEoXks5pS-xhgaJpZM4G7FOX.gif

Example from official MapControl sample.
In scenario 3 I added NormalizedAnchorPoint binding.
public class PointOfInterest
{
public PointOfInterest()
{
this.MoreInfo = "At a glance info info about this Point of interest";
this.NormalizedAnchorPoint = new Point(0.5, 1);
}
public string DisplayName { get; set; }
public Geopoint Location { get; set; }
public Uri ImageSourceUri { get; set; }
public string MoreInfo { get; set; }
public Point NormalizedAnchorPoint { get; set; }
}

                                  </Image.Transitions>
                                        </Image>
                                    </StackPanel>
                                </Button>
                            </DataTemplate>

Screenshots before zooming

and after:

the image should not move when zooming

I experienced the same thing. I do not like that behavior as well. But, I do not think NormalizedAnchorPoint controls that behavior. I could be wrong though.   MapIcons seem to behave differently based on whether the map is 2D or 3D. Is it an Altitude issue?
David Blackburn

On Dec 24, 2015, at 9:30 AM, Dmitry<EMAIL_ADDRESS>wrote:
Example from official MapControl sample.
In scenario 3 I added NormalizedAnchorPoint binding.
public class PointOfInterest
{
public PointOfInterest()
{
this.MoreInfo = "At a glance info info about this Point of interest";
this.NormalizedAnchorPoint = new Point(0.5, 1);
}
public string DisplayName { get; set; }
public Geopoint Location { get; set; }
public Uri ImageSourceUri { get; set; }
public string MoreInfo { get; set; }
public Point NormalizedAnchorPoint { get; set; }
}
maps:MapControl.Location="{Binding Location}"
maps:MapControl.NormalizedAnchorPoint="{Binding Point}" >
                              </Image.Transitions>
                                    </Image>
                                </StackPanel>
                            </Button>
                        </DataTemplate>

Screenshots before zooming
and after:
the image should not move when zooming
—
Reply to this email directly or view it on GitHub.

NormalizedAnchorPoint is work correctly for me if don't use MapItemsControl. I don't use 3d.
This example is work correctly on 2d map:
<Maps:MapControl
    Center="{Binding MapCenter, Mode=TwoWay}"
    <Grid
        Maps:MapControl.Location="{Binding MapCenter}"
        Maps:MapControl.NormalizedAnchorPoint="0.5,1">
        <Image Source="/Assets/Images/GeoPointerA.png"></Image>
    </Grid>
 </Maps:MapControl>

Why NormalizedAnchorPoint  don't work with MapItemsControl? Is it bug?

Also, the points of interest drift around in 3D view, so it's seems like a bug in MapItemsControl.

I agree. Bug.
From: Jim Galasyn<EMAIL_ADDRESS>Sent: Saturday, December 26, 2015 3:40 PM
To: Microsoft/Windows-universal-samples<EMAIL_ADDRESS>Cc: myshiftzz<EMAIL_ADDRESS>Subject: Re: [Windows-universal-samples] NormalizedAnchorPoint don't work in MapControl (#252)
Also, the points of interest drift around in 3D view, so it's seems like a bug in MapItemsControl.
—
Reply to this email directly or view it on GitHub https://github.com/Microsoft/Windows-universal-samples/issues/252#issuecomment-167364598 .  https://github.com/notifications/beacon/AJ8_d4SqYBv7oDrDnxhFkT-HE1ARgwQtks5pTwCbgaJpZM4G7FOX.gif

It seems to work when binding but not when written static in xaml.
However it is a design element, not content, so it should not require binding...

This issue is not with the sample itself, but rather with extending the sample. It will require additional debugging to further isolate the problem you are experiencing. You can open a support case with our Developer Support team who can further help with the specific problem you are experiencing. Please use these steps below for further help:

Visit http://aka.ms/storesupport and sign-in with your Microsoft account.
Under the “App Development” section choose "Windows 10 universal app development", then choose the appropriate problem type and category to get engaged through a formal support channel.

Hi guys,
It's not MapControl issue. by default It render icon to right bottom of point .you need to set offset.
for ex. If MapIcon Image Height =40 and Width= 40 then set margin -20,0,0,-40. try it you will see changes.


Fixed scrollbars not moving when mouse leaves scroll bar bounds

This pull request fixes a quirk of the scroll bar widget.
Whenever a user is dragging on the scroll bar with the mouse, moving the mouse outside of the "track" will cause the scrolling to stop abruptly.
The behavior for most GUI applications is to continue the scrolling for as long as the mouse button is held, and it can be disruptive to the user for it not to be this way, since keeping the mouse within the scroll bar bounds can be difficult.
The implemented fix is to keep a global Vector2 "pin" that is set to the position the mouse first clicked on when scrolling starts. Then, a scrollbar can remain focused for as long as the Vector2 is within its range, but releasing the mouse resets the Vector2 to {NAN, NAN} so that it fails all collision checks.

I'm afraid I avoid control-specific globals, it's a limitation of imgui. I'm afraid your solution will fail if multiple scrollbars are used in an application.


container-common: remove centos extras repo task

This task just doesn't work when using the variable
ceph_docker_enable_centos_extra_repo to true.
fatal: [xxx]; FAILED! => {"changed": false, "msg": "Parameter 'baseurl', 'metalink' or 'mirrorlist' is required."}

The CentOS extras repository is enabled by default so it's pretty
safe to remove this task and the associated variable.
Signed-off-by: Dimitri Savineau<EMAIL_ADDRESS>

included in #4002


Add FermiSurface property

I left out the FermiSurface in #52. I will tackle it here, as even tho it is related with ElectronicEigenvalues and ElectronicBandStructure it is strictly a different property: Fermi surface value should be the k mesh points, and not the energy values.

This is already handled by a student of Claudia's.

Do you know something more about it?


How does this extension know where model files are located?

Hello! When I try going to the definition of a model, VS Code tries to open a file in a directory that's different from where the model is actually located. So I'm curious where the extension looks to find the root folder for my models, and if it's possible to customize that.
Thank you!

Are you using devcontainers? If so, I'm having the same issue.  I keep getting the message The editor could not be opened because the file was not found.
My container folder is oot@77295f50ed01:/workspaces/data-warehouse-2-dbt# , witi the file being in /models/example/
The file that the dbt power user extension is looking for is in /dbt/models/example/
I'm not sure how to align these 2 paths.

Hi @skwon615, did you ever end up finding out how it does so?

@CR-Lough no, unfortunately not yet :(

Hey @skwon615 I'm pretty sure this is an "us" issue. I see now that this extension was built to show parent/child/tests only for the file currently open. Not to show all models in the project.
Let me know if that works for you.

Ah, got it...thanks, I guess that means I can't use this extension, but good to know!


Confusion about Server Setup

Hi thre,
We have succesfully started using the 3rd party API, and it's working well. Now we have a need to start streaming data, so we need to setup fleet-telemetry as well. We have setup the CSR steps as it's required on 3rd party as well. It is hosted on tesla.ourdomain.com/.well-known/appspecific/com.tesla.3p.public-key.pem
I have some prior experience with K8s, but I'm finding the steps to setup the server a little confusing. If I want to try out setting this whole service up using a minikube cluster to make sure everything is sorted, how do I go about doing that? Is that possibe at all? I have installed the helmcharts, but I'm getting a http://<IP_ADDRESS>:8080/status <IP_ADDRESS>:8080: connect: connection refused error from the dashboard. What service is supposed to be hosted on port 8080 anyways?
I see that the README was updated to include more details on the previous steps, but I'd appreciate if you can please clarify/add more details to the actual server part.
For example, what is the docker-compose.yml file for? Is it possibel to test this locally at all, or we'd have to setup all the cloud infra first using K8s? Would appreciate some pointers!!

Still confused about the server setup, @patrickdemers6 perhaps we could get a diagram to visualize the system? Any pointers would be great :)

Hey @amirhmk, I'll be honest I'm not familiar with helmcharts. Maybe @aaronpkahn can help with that part?
You can't test a server locally since vehicles need a publicly accessible endpoint to access.
Personally, I would avoid using K8s initially as it adds complexity. To start simple, I'd recommend using Docker or even running the binary directly.
I have an article I wrote which describes steps for Docker: https://dev.to/patrickdemers6/fleet-telemetry-streaming-data-from-your-tesla-2i97. For running the binary, you'd have to build the go application. Then, run it and pass in -config=<path_to_config>.
Things to look out for:

The port the server attaches to needs to bind to the public network interface
Ensure mTLS connections are terminated at the server

For example, what is the docker-compose.yml file for?
Not sure if you're asking docker-compose.yml in general or as a part of helm charts?

Happy to answer more specific questions you have.

Great, thank you for the article above @patrickdemers6 , I think adding this to the README would help a lot of people!!
So I have setup all the steps, and was able to get The server certificate is valid message when trying out the tool you've provided.
However, when I now try to send the telemetry config to the vehicles, I get a 404 with an MY_VIN_ID not_found error. Now I want to make sure my setup is correct.
For our 3rd party APIs, we're using tesla.domain.com and have registered the CSR using the /register endpoint and that's working well.
For the Fleet Telemetry application, we're using tesla-fleet.domain.com (which I checked ther cerfificates above and it works), however, I'm not sure if we need to also call the /register endpoint in this case? Can we even have 2 different domains?

@amirhmk  Could you send an email to<EMAIL_ADDRESS>Include you client ID and VIN. Once we come to a conclusion, we can post the result here for the community.

Great point @patrickdemers6, I was told the following in the email:

Since you are not onboarded for T4B, all API calls interacting with your own vehicles need to use a third party token. https://developer.tesla.com/docs/fleet-api#third-party-token

I was then told to contact Tesla Fleet by visiting https://www.tesla.com/fleet, however, from first glance I was under the impression that one does not necessarily need to participate in the Tesla 4 Business program. There seems to be a discrepancy from this sentence from this repo's README

Owners can allow registered applications to receive telemetry securely and directly from their vehicles. This reference implementation can be used by individual owners as is or by fleet operators who can extend it to aggregate data accross their fleet.

Could you please clarify?

Great point @patrickdemers6, I was told the following in the email:

Since you are not onboarded for T4B, all API calls interacting with your own vehicles need to use a third party token. https://developer.tesla.com/docs/fleet-api#third-party-token

To me it sounds like you have created a partner token, but not authorised your own Tesla account to get a third party token.
Is your own application listed at https://accounts.tesla.com/account-settings/security?tab=tpty-apps
If not, you have missed the third party token step from the documentation, that they linked you in the email.

Yes, exactly @jordan-bonecutter, we have my company's app registered under developer.tesla.com and I am using my personal vehicle to do dev work. I had granted permission to my vehicle, but I thought the fleet_telemetry_config would use the partner_token and not the 3rd party token.
Anyways, I am waiting to see some logs on the fleet-telemetry server now to complete the loop. So far nothing (not even errors).

So far nothing (not even errors).

Did you check the fleet telemetry errors API? https://developer.tesla.com/docs/fleet-api#partner-endpoints

So far nothing (not even errors).

Did you check the fleet telemetry errors API? https://developer.tesla.com/docs/fleet-api#partner-endpoints

Yep, I used that but there's nothing. I tried emailing now to see if there is anything that I'm not catching.
I do see a log like this on the server, but I was getting these sort of requests before as well:
2024/04/04 02:43:10 http: TLS handshake error from xxxxxx:59065: read tcp xxxxx:443->xxxxxx:59065: read: connection reset by peer
2024/04/04 03:02:38 http: TLS handshake error from xxxxx:59048: EOF

Okay so I finally started getting data now. I wanted to share some of the details that made the setup work.

I wasn't getting any error logs from fleet_telemetry_errors or on the server initially. After following up with the tesla fleet email, they wanted my confirmation that I have in fact requested a new CSR (I'm not sure if this is gonna be the case for everyone if their first CSR is correct).
After confirming this, I had to make sure to use the 3rd party token (OWNER) to send the configs to the vehicle using POST /fleet_telemetry_config.
After seeing Client sent an HTTP request to an HTTPS server. errors and 502, I noticed that I was using an Application Load Balancer (ALB) listening on HTTPS 443, but I had to use a Network Load Balancer (NLB) on TCP 443. AWS's passthrough mTLS for ALB made me think it meets the requirements.

@Bre77 Okay I'm facing issues again, and I think I know why, but I'm not sure what the best way to set this up would be. Quick question, I can see in the tutorial above that we can use two different domains, one for server and one for public use.
Currently my public key is hosted at the same URL as my fleet server. telemetry-server.domain.com/.well-known/appspecific/com.tesla.3p.public-key.pem. However, I need to move it to a different subdomain as it's conflicting with LB settings. Before I had it on tesla.domain.com but when I submitted a CSR for telemetry-server it seems to have replaced the original tesla.domain.com one.
What's the correct setup here?

@amirhmk whats your "partner domain" on https://developer.tesla.com because I think your making this difficult for yourself.
This is an example of a working implementation:

Partner Domain: teslemetry.com
Public Key: teslemetry.com/.well-known/appspecific/com.tesla.3p.public-key.pem
API call made to register teslemetry.com (https://developer.tesla.com/docs/fleet-api#register)
CSR was created for teslemetry.com
Fleet Telemetry server: na-west.teslemetry.com & eu-west.teslemetry.com each with their own SSL cert signed by the private key

Your partner domain should probably be domain.com, but if you want it to be tesla.domain.com, then thats what you need to set in the portal, register with the API, and create a CSR for. I actually believe that the domain of your Fleet Telemetry server is entirely irrelevant to all of this, because there is no common name checks, only certificate chain checks.

Thanks for your message @Bre77. Indeed it does seem like I have complicated this setup a little bit.
I started separating these out now, and sent new configs, but I'm getting an error again.
So now my setups looks like:

Partner domain: tesla-fleet.matt3r.ai (public key hosted at https://tesla-fleet.matt3r.ai/.well-known/appspecific/com.tesla.3p.public-key.pem
Fleet Telemetry server: tesla-server.matt3r.ai with a cert and keys created accordingly and passed when starting up the server.
Both check_csr.sh and check_server_certs.sh pass.
When calling the errors endpoint, I see something like this:

webconnection error: x509: certificate is valid for tesla-fleet.matt3r.ai, not tesla-server.matt3r.ai\" cm_type=stream",
                "error_name": "cloud_manager_error",
                "hostname": "tesla-server.matt3r.ai",

Which makes me thing we do need to let Tesla know about the Telemetry Server hostname, as it's something we have to wait on Tesla from this in the README:

Wait for Tesla to process your CSR. This may take up to two weeks. Once complete, you will receive an email from Tesla. The generated certificate will not be sent back to you; it is attached to your account on the backend and is used internally when configuring a vehicle to stream data.

@patrickdemers6 Can you confirm this please?

Is the server certificate generated for tesla-server.matt3r.ai? The error indicates the car is trying to connect to tesla-server.matt3r.ai but the SSL cert the server is using is for tesla-fleet.matt3r.ai

Is the server certificate generated for tesla-server.matt3r.ai? The error indicates the car is trying to connect to tesla-server.matt3r.ai but the SSL cert the server is using is for tesla-fleet.matt3r.ai

Yes the certificate is set correctly I believe, I verified using the ./chek_server_cert. After looking at the logs again though, I noticed the following line:

url of the fleet-telemetry server, must match the root domain (second-level + first-level domain) of the registered application

I have kept tesla-fleet.matt3r.ai as is, and have switched the hostname for the server to be server.tesla-fleet.matt3r.ai now to match above. Still getting a similar error:
webconnection error: x509: certificate is valid for tesla-fleet.matt3r.ai, not server.tesla-fleet.matt3r.ai\" cm_type=stream"

I went to your fleet Telemetry server and it has the wrong common name, so you need to recreate your Fleet Telemetry server cert to match its domain.
Turns out Tesla is doing common name checking.

I went to your fleet Telemetry server and it has the wrong common name, so you need to recreate your Fleet Telemetry server cert to match its domain.
Turns out Tesla is doing common name checking.

Doesn't that mean server.tesla.domain.com (Server) and tesla.domain.com (partner domain, public key, etc.) would work?

What port is your fleet Telemetry server on, because https://server.tesla-fleet.matt3r.ai has a cert for tesla-fleet.matt3r.ai

Okay it's fully fixed now. When updating the DNS records I pointed server.tesla-fleet to the wrong ip, resulting in cert errors.
In hindsight, I know that the fleet_telemetry_config create endpoint does state config.hostname needs to be a subdomain of the partner_domain, it'd be good for it to explicitly check this and throw an error if not.
Thanks!!