PCFDev (pcfdev-v0.447.0) cf login failed

I have installed PCFDev successfully on a company laptop.
pcfdev-v0.447.0
I also set environment variables:

http_proxy=http://mycompany.com:80
https_proxy=http://mycompany.com:80
no_proxy=.local.pcfdev.io,localhost,.mycompany.com

Here was the info I got below ...
Any help will be greatly appreciated.
D:\>cf dev start
Using existing image.
Starting VM...
Provisioning VM...
Waiting for services to start...
9 out of 57 running
9 out of 57 running
9 out of 57 running
40 out of 57 running
57 out of 57 running
 _______  _______  _______    ______   _______  __   __
|       ||       ||       |  |      | |       ||  | |  |
|    _  ||       ||    ___|  |  _    ||    ___||  |_|  |
|   |_| ||       ||   |___   | | |   ||   |___ |       |
|    ___||      _||    ___|  | |_|   ||    ___||       |
|   |    |     |_ |   |      |       ||   |___  |     |
|___|    |_______||___|      |______| |_______|  |___|
is now running.
To begin using PCF Dev, please run:
   cf login -a https://api.local.pcfdev.io --skip-ssl-validation
Apps Manager URL: https://local.pcfdev.io
Admin user => Email: admin / Password: admin
Regular user => Email: user / Password: pass

D:\>cf login -a https://api.local.pcfdev.io --skip-ssl-validation
API endpoint: https://api.local.pcfdev.io
FAILED
Error performing request: Get https://api.local.pcfdev.io/v2/info: EOF

I was able to ping ...
D:\>ping api.local.pcfdev.io
Pinging api.local.pcfdev.io [<IP_ADDRESS>] with 32 bytes of data:
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64
Reply from <IP_ADDRESS>: bytes=32 time<1ms TTL=64

Ping statistics for <IP_ADDRESS>:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

It seems likely that the cf utility is not picking up your no_proxy env var, and attempting to connect to <IP_ADDRESS>:443 via your HTTP proxy. Can you confirm that you have no_proxy set in that shell? Can you try in PowerShell, as recommended in the docs?

sclevine: You're 100% correct, after I set http_proxy= and https_proxy= to "null" before cf login, it worked. It's not picking up "no_proxy" setting at all. I will give it a try in PowerShell tomorrow, and let you know.
Thanks,
Mike

Closing this for now, because it appears to have been addressed by the environment variable changes. Let us know if you're still experiencing this issue.


[question] Plugins vs Modules vs Vendor

Hello, this a probably a noob question but i still do not have a clear understating of the differences.
What i know is that vendor is used for things you need a lot and do not re include in every page.
On the official websites it says Modules is for nuxt modules what does that mean? If i want to use vue-notification or vue-select is that a module or plugin?
One more question: if in a plugin i do: Vue.use(pluginName) doesn't that mean that it is available in Vue globally and can be used in any page which means no need to add that plugin in build/vendor?

When you want to use someone else's code in your application, or some code that does not belong to your application, but is simply used as a library in your application, you should add it to the vendor, so the code will be added to vendor file and can be cached by browser and your application will be smaller.
Plugin is one of the ways to embed these libraries into your application. For example, to not include axios in the component of each page, you can write a plugin that imports axios and embeds it in the prototype Vue objects, context, storage, etc.
But the module it is an extension to your whole nuxt.js application. For example, you can write a module, that will add vue-notification to vendor and also will add the plugin that will import vue-notification and make Vue to use it. Read documentation there are very good examples

About last question - yes it will be available globally. But you still have to add it to vendor, because otherwise the code of this library will be like a part of your application, not like a library

I was quite confused by plugins and modules. Now I seems to have a better understanding and want to put my answer here.
It seems that one, maybe the most important, difference that neither the document nor this post properly addressed, is that:
Plugin is something be imported in client application. That means it's imported either in browser, or when server doing server side rendering.
Module is something be executed upon nuxt boot up, and is able to customize the nuxt application in almost any way. For example, module can add a plugin to the nuxt application.
However, can we skip the plugin and just let module do the work of plugin (like calling Vue.use)? No. Module is executed upon nuxt boot up, meaning it's executed on the nuxt server, or nuxt generate, but not on browser. So module can add a plugin to the nuxt application but cannot skip the plugin and just do something the plugin suppose to do.
I have just started working with nuxt so please correct me if I'm wrong.


Synthesis failed for Google.Cloud.AIPlatform.V1

Hello! Autosynth couldn't regenerate Google.Cloud.AIPlatform.V1. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the Google.Cloud.AIPlatform.V1 API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
git config push.default simple
2021-07-14 22:36:43,755 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.AIPlatform.V1
2021-07-14 22:36:43,758 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.AIPlatform.V1
Switched to branch 'autosynth-Google.Cloud.AIPlatform.V1'
2021-07-14 22:36:43,996 autosynth [DEBUG] > Running: git rev-parse --show-toplevel
2021-07-14 22:36:44,000 autosynth [DEBUG] > Running: git log -1 --pretty=%H
2021-07-14 22:36:44,004 autosynth [DEBUG] > Running: git remote get-url origin
2021-07-14 22:36:44,459 autosynth [DEBUG] > Running: git log 369fd2ade113e707ee29794fe558d7d25955032c..HEAD --pretty=%H --no-decorate
2021-07-14 22:36:44,463 autosynth [DEBUG] > Running: git log -1 --pretty=%at 369fd2ade113e707ee29794fe558d7d25955032c
2021-07-14 22:36:44,467 autosynth [DEBUG] > Running: git log -1 --pretty=%at 34b0ce6002f32dc7c05d081c1211458d2560c7d0
2021-07-14 22:36:44,471 autosynth [DEBUG] > Running: git log -1 --pretty=%at cc51e4818f5f928f34e801252cc11db73e097933
2021-07-14 22:36:44,475 autosynth [DEBUG] > Running: git log -1 --pretty=%at dddf5cb27fbda4f5a0badcd1af1fc328a83962c9
2021-07-14 22:36:44,479 autosynth [DEBUG] > Running: git log -1 --pretty=%at 83c372893a7ffd0a8b3ca8e3b4b49cfd2acd3145
2021-07-14 22:36:44,483 autosynth [DEBUG] > Running: git log -1 --pretty=%at ca5d91f77ca8c117452d3ccd48608427da506490
2021-07-14 22:36:44,486 autosynth [DEBUG] > Running: git log -1 --pretty=%at 56ffafc26996071e2166fdfec88c325fcb4d8ea4
2021-07-14 22:36:44,490 autosynth [DEBUG] > Running: git log -1 --pretty=%at 46bdf2303c232856a7009b5e788c2f4a12810944
2021-07-14 22:36:44,493 autosynth [DEBUG] > Running: git log -1 --pretty=%at 961b45b1a373ab61db99e0ea350580d0d25cf9fb
2021-07-14 22:36:44,497 autosynth [DEBUG] > Running: git log -1 --pretty=%at dd1d95a98a0bf119bb0356786a64ba047ece04fe
2021-07-14 22:36:44,500 autosynth [DEBUG] > Running: git log -1 --pretty=%at c376cadb2ac3ce18f3fa3215ea40aea8ba11893c
2021-07-14 22:36:44,504 autosynth [DEBUG] > Running: git checkout<PHONE_NUMBER>b76df9650a3609ecde4293fa74e3ab
Note: switching to '3169061745b76df9650a3609ecde4293fa74e3ab'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 316906174 Regenerate all metadata JSON files
2021-07-14 22:36:44,529 autosynth [DEBUG] > Running: git checkout c376cadb2ac3ce18f3fa3215ea40aea8ba11893c
Note: switching to 'c376cadb2ac3ce18f3fa3215ea40aea8ba11893c'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at c376cadb feat: Update the example for report v2 integration.
2021-07-14 22:36:44,546 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.AIPlatform.V1-11
2021-07-14 22:36:44,551 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.AIPlatform.V1-11
Switched to branch 'autosynth-Google.Cloud.AIPlatform.V1-11'
2021-07-14 22:36:44,577 autosynth [INFO] > Running synthtool
2021-07-14 22:36:44,577 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2021-07-14 22:36:44,577 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/Google.Cloud.AIPlatform.V1/11/sponge_log.log
2021-07-14 22:36:44,580 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-07-14 22:36:44,827 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.AIPlatform.V1/synth.py.
On branch autosynth-Google.Cloud.AIPlatform.V1-11
nothing to commit, working tree clean
Skipping microgenerator fetch/build: already built, and running on Kokoro
Building existing version of Google.Cloud.AIPlatform.V1 for compatibility checking
Generating Google.Cloud.AIPlatform.V1
Running pre-generation script for Google.Cloud.AIPlatform.V1
Running post-generation script for Google.Cloud.AIPlatform.V1
Updated 41 paths from the index
Building new version of Google.Cloud.AIPlatform.V1 for compatibility checking
ValueConverter.cs(43,64): error CS0117: 'Value' does not contain a definition for 'ForStruct' [/home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.AIPlatform.V1/Google.Cloud.AIPlatform.V1/Google.Cloud.AIPlatform.V1.csproj]
ValueConverter.cs(67,56): error CS1061: 'Value' does not contain a definition for 'KindCase' and no accessible extension method 'KindCase' accepting a first argument of type 'Value' could be found (are you missing a using directive or an assembly reference?) [/home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.AIPlatform.V1/Google.Cloud.AIPlatform.V1/Google.Cloud.AIPlatform.V1.csproj]
ValueConverter.cs(67,74): error CS0117: 'Value' does not contain a definition for 'KindOneofCase' [/home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.AIPlatform.V1/Google.Cloud.AIPlatform.V1/Google.Cloud.AIPlatform.V1.csproj]
ValueConverter.cs(70,45): error CS1061: 'Value' does not contain a definition for 'StructValue' and no accessible extension method 'StructValue' accepting a first argument of type 'Value' could be found (are you missing a using directive or an assembly reference?) [/home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.AIPlatform.V1/Google.Cloud.AIPlatform.V1/Google.Cloud.AIPlatform.V1.csproj]
2021-07-14 22:37:13,080 synthtool [ERROR] > Failed executing /bin/bash generateapis.sh --check_compatibility Google.Cloud.AIPlatform.V1:

None
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1137, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1062, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 763, in invoke
    return __callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/google-cloud-dotnet/apis/Google.Cloud.AIPlatform.V1/synth.py", line 26, in <module>
    hide_output = False)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '('/bin/bash', 'generateapis.sh', '--check_compatibility', 'Google.Cloud.AIPlatform.V1')' returned non-zero exit status 1.
2021-07-14 22:37:13,112 autosynth [ERROR] > Synthesis failed
2021-07-14 22:37:13,113 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 316906174 Regenerate all metadata JSON files
2021-07-14 22:37:13,191 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.AIPlatform.V1
Switched to branch 'autosynth-Google.Cloud.AIPlatform.V1'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 356, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 191, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 336, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 68, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


pkg/pbutil: add marshal-related tests

for #1467

all comments resolved.

@xiang90 refreshed

lgtm


Beta broken, likely due to firebase-compat CORS failure

Opening this in case it wasn't picked up.
Beta is broken on my machine (Firefox/Linux), in the sense that yew app doesn't even start.
For some reason an error in:
https://github.com/homotopy-io/homotopy-rs/blob/master/homotopy-web/static/index.html#L43
is stopping the yew app's main from running.
Console dump:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://www.gstatic.com/firebasejs/9.7.0/firebase-performance-compat.js. (Reason: CORS request did not succeed). Status code: (null)
Loading failed for the module with source “https://www.gstatic.com/firebasejs/9.7.0/firebase-app-compat.js”.
Loading failed for the module with source “https://www.gstatic.com/firebasejs/9.7.0/firebase-analytics-compat.js”
Module source URI is not allowed in this document: “https://www.gstatic.com/firebasejs/9.7.0/firebase-performance-compat.js”.
Loading failed for the module with source “https://www.gstatic.com/firebasejs/9.7.0/firebase-auth-compat.js”.
TypeError: error loading dynamically imported module

It works fine on my VM (Firefox/Linux). Could it be some Firefox extension that blocks the request (see this) ?

You are correct, site loads fine if I disable UBlock Origin.
I'd be happy to close this issue now, but Ublock is a rather popular extension, so it would result in the site being broken for a lot of potential users. Should we consider at least documenting this?

Yes we should definitely document this

It might be as easy as catching any (relevant) error in "firebase.js" and printing on the dom "Failure to load firebase, disable privacy-oriented web extensions."

This sounds like a really good idea.

It might be as easy as catching any (relevant) error in "firebase.js" and printing on the dom "Failure to load firebase, disable privacy-oriented web extensions."

It is a bit harder than I expect -- JS doesn't allow me to catch import errors easily. I'll leave this task later.


JetPack -> Modifiers -> Drawing: Modifier.indication(     interactionSource: InteractionSource,     indication: Indication? )

Doc: https://developer.android.com/reference/kotlin/androidx/compose/ui/Modifier#(androidx.compose.ui.Modifier).indication(androidx.compose.foundation.interaction.InteractionSource,androidx.compose.foundation.Indication)
Draws visual effects for this component when interactions occur.

Draws visual effects for this component when interactions occur.
An InteractionSource must returns a Flow<Interaction>.
And an Indication must return a IndicationInstance that provides a ContentDrawScope.
I honestly don't know why we should implement this modifier or even how could we do it.


Add conversion for v1 Pipeline

Changes

This commit adds conversion functions between v1beta1 and v1 Pipeline.
It does not handle fields deprecated in v1beta1 that will not be present in v1.
It implements ConvertTo and ConvertFrom for v1beta1 Pipeline, and leaves
these functions unimplemented for v1 Pipeline, since it is the highest known version.
Conversions for all types are basically deep copies, rather than using the same struct
definition for both API versions. This will allow us to iterate on v1 without making additional
changes to v1beta1, after v1 is the stored version.
Handle resources regarding #5253
Part of #4986
/kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[n/a] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/kind misc

/retest

/retest

/retest

/retest

/retest

/test pull-tekton-pipeline-build-tests

/test pull-tekton-pipeline-build-tests

/retest

/retest

/lgtm


Images: Differentiating WHAT and HOW

Sorry if this has been hashed to death, but it bothers me. Sort of a lot.
Including execution details (isolators like memory and CPU) is an "interesting" decision.  Docker has a pretty clean separation of "what" to run and "how" to run it, which makes containers very composable and useful in varying contexts.  E.g. the mysql image  for my 8GB laptop and my 128GB prod server is the same image.
Embedding the how (e.g. how much memory to allow) into an image sort of ties an image down to a specific use-case.  It also opens the door to scary spec statements like "Execution details specified in image dependencies are ignored".  This implies that the way to operate is to do the equivalent of Dockerfile's "FROM" on the reusable thing (e.g. mysql) into content-identical "laptop-mysql" and "prod-mysql" images, with different memory limits.  This means that the image you use to test is NOT the image you use in prod.  This is, IMO, an anti-pattern and should be discouraged strongly.  It also immediately creates two classes of images - those that provide "how" details (leaves) and those that don't (stems).
Images are the permanent artifact of WHAT.  Pods are the artifact of what+how.  What justifies keeping isolators in images as opposed to just in pods?

+1
Although the image should be able to specify its minimum requirements: e.g. 512MB is the minimum for mysql to run. This would be the same as specifying minimum set of capabilities the app needs (e.g. CAP_SYS_PTRACE for gdb app). It can be launched with more capabilities but not less.

is 0 more or less than 512M?  ;)
I am unconvinced that minimums are something the API should carry, as
opposed to docs, but I am not particularly against it.  I just want to make
sure we shave this thing down as much as possible to things we KNOW we NEED.
On Tue, May 5, 2015 at 8:48 PM, Eugene Yakubovich<EMAIL_ADDRESS>wrote:

+1
Although the image should be able to specify its minimum requirements:
e.g. 512MB is the minimum for mysql to run. This would be the same as
specifying minimum set of capabilities the app needs (e.g. CAP_SYS_PTRACE
for gdb app). It can be launched with more capabilities but not less.
—
Reply to this email directly or view it on GitHub
https://github.com/appc/spec/issues/365#issuecomment-99312885.

Isolators aren't just about resources but also things like capabilities, syscalls, etc. I am OK with saying particular isolators are not allowed inside of the image section like memory, cpu, etc.


add netty4 metrics.

What is the purpose of the change
增加netty相关指标，详情：#https://github.com/apache/dubbo/issues/12271
Brief changelog
监控指标类型

NettyAllocatorMetrics
NettyEventExecutorMetrics

指标详情

"netty.allocator.memory.used" - Size of memory used by the allocator, in bytes
Tags: "id" (unique id for the allocator), "allocator.type" (pooled, unpooled), "memory.type" (heap, direct)
"netty.allocator.memory.pinned" - Size of memory used by allocated buffers, in bytes.
Tags: "id" (unique id for the allocator), "allocator.type" (pooled, unpooled), "memory.type" (heap, direct)
"netty.allocator.pooled.arenas" - Number of Arenas for a pooled allocator.
Tags: "id" (unique id for the allocator), "allocator.type" (pooled, unpooled), "memory.type" (heap, direct)
"netty.allocator.pooled.cache.size" - Size of the cache for a pooled allocator, in bytes.
Tags: "id" (unique id for the allocator), "allocator.type" (pooled, unpooled), "cache.type" (normal, small)
"netty.allocator.pooled.threadlocal.caches" - Number of ThreadLocal caches for a pooled allocator.
Tags: "id" (unique id for the allocator), "allocator.type" (pooled, unpooled)
"netty.allocator.pooled.chunk.size" - Size of memory chunks for a pooled allocator, in bytes.
Tags: "id" (unique id for the allocator), "allocator.type" (pooled, unpooled)
"netty.eventexecutor.tasks.pending" - Number of pending tasks in the event executor.
Tags: "name" (unique name for the event executor)

Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

2023-07-19T14:25:16.4871621Z Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled.
2023-07-19T14:25:16.4872172Z 2023-07-19 14:22:01.284 ERROR 9 --- [           main] o.s.b.d.LoggingFailureAnalysisReporter   :
2023-07-19T14:25:16.4872403Z
2023-07-19T14:25:16.4872485Z ***************************
2023-07-19T14:25:16.4872706Z APPLICATION FAILED TO START
2023-07-19T14:25:16.4872918Z ***************************
2023-07-19T14:25:16.4873034Z
2023-07-19T14:25:16.4873118Z Description:
2023-07-19T14:25:16.4873243Z
2023-07-19T14:25:16.4873710Z An attempt was made to call the method io.netty.buffer.PooledByteBufAllocator.metric()Lio/netty/buffer/PooledByteBufAllocatorMetric; but it does not exist. Its class, io.netty.buffer.PooledByteBufAllocator, is available from the following locations:
2023-07-19T14:25:16.4874180Z
2023-07-19T14:25:16.4874530Z     jar:file:/usr/local/dubbo/app/dependency/netty-all-4.0.38.Final.jar!/io/netty/buffer/PooledByteBufAllocator.class
2023-07-19T14:25:16.4874798Z
2023-07-19T14:25:16.4874919Z It was loaded from the following location:
2023-07-19T14:25:16.4875080Z
2023-07-19T14:25:16.4875308Z     file:/usr/local/dubbo/app/dependency/netty-all-4.0.38.Final.jar
2023-07-19T14:25:16.4875502Z
2023-07-19T14:25:16.4875509Z
2023-07-19T14:25:16.4875583Z Action:
2023-07-19T14:25:16.4875697Z

please fix conflits

@AlbumenJ PTAL


Episode renaming and Downloading order

Hi,
I noticed when download an entire anime that the downloading order is reversed. It starts downloading the latest episode first and the first episode last.
Is there a way to reverse the order which monkey-dl downloads the anime?
Edit: Also, all the downloaded episodes are named in numbers. Is there a way to attach the anime name into them automatically?
I am currently using advanced renamer to rename them after downloading.
PS: Sorry for my bad english.

Hi @eslamsidereel ! Sorry for the late reply on the issue.
As for your first question, when collecting episodes from different websites, some of them are collected in descending order while some of them are arranged in ascending order and the whole episodes list is then passed to the relevant downloader to be downloaded.  I haven't come across this issue before but yes, since you have mentioned it, I think it would be better if I sort the downloads first :)
And as for the second question, yes, you can let monkey-dl to name your episodes as well. You just have to provide monkey-dl with the animefillerlist url for the anime you are trying to download (check the readme). If you do that, then monkey-dl will read the episode names from animefillerlist website and name your downloads accordingly

I followed the readme and started using animefillerlist. It looks great, but I noticed that it doesn't contain a wide range of anime. I was looking for some anime like Divine Gate and Prince Of Stride, both yielded no results.
I think this is something to do with the site itself I guess.
Anyway thank you.

Yes animefillerlist doesn't have some/most anime on it. I plan on adding more websites support to extract episode names (just that I've been busy lately so couldn't invest much time on this). Hopefully, with the next v2 update (upcoming one) I will try to add at least one more episode name extraction website support apart from animefillerlist  :D

I can add The Movie DB if you want me to, just point me to the file that handles the filenames.
(or we could add kitsu.io instead, but im not familiar with its api)


[PE-D] edit /idt command bug

Certain invalid date times are accepted by the command without producing an error message.
To reproduce:
Run "edit 10 idt/31-02-2022 13:45"
The application creates an interview with a modified date 28 Feb 2022 instead of producing an error.

Labels: severity.Low type.FeatureFlaw
original: manu2002g/ped#9

"Must fix" Bug. Would need to modify InterviewSlot#toLocalDateTime() method to reject "invalid dates".
Solution found: https://stackoverflow.com/questions/32823368/java-8-localdatetime-is-parsing-invalid-date
The argument passed into InterviewSlot#toLocalDateTime() include .withResolverStyle(ResolveStyle.STRICT).
Also, the pattern used can be changed to "dd-MM-uuuu HH:mm" instead.

Reason for "u" instead of "y": https://stackoverflow.com/questions/41177442/uuuu-versus-yyyy-in-datetimeformatter-formatting-pattern-codes-in-java

he command without producing an error message.
To reproduce: Run "edit 10 idt/31-02-2022 13:45" The application creates an interview with a modified date 28 Feb 2022 instead of producing an error.

This bug already flagged  in #101


VLAZ: Watch 1-(804)-587-5038

VLAZ requests the watch of the watch_number 1-(804)-587-5038. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Jeff Schaller in Charcoal HQ


Security Updates for PNPM

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
We have shipped support for PNPM version updates recently. However, we are still missing the proper logic to implement security update support.
In particular, we need to implement the proper logic to be able to propose updates to the minimum fixed version, given a security advisory.
In addition to that, some other internal changes will be needed to enable this feature, but this issue tracks the changes related to the update logic.
For reference, here is a previous PR implementing the same kind of thing for Github Actions.

Dependabot alerts and Security Updates to try and fix them have now been enabled for PNPM  :tada:
So let me close this ticket now. Feel free to report any issues you find separately.
Thanks!


CI failure Bundler::GemRequireError

https://travis-ci.org/sferik/rails_admin/jobs/107236882
Bundler::GemRequireError: There was an error while trying to load the gem 'rails_admin'.

@mshibuya do you know what this is about? Is it random?
 Someone help.

I'm getting this same error in my dev environment when trying to upgrade to ruby-2.2 from ruby-2.1. Even tried setting the bundle path to vendor/bundle instead of the default path and rebuilding, but to no avail.

@bashcoder Ok, all errors happen with ruby 1.9.3 or 2.0.0 (and consistently)
Other rubies are not impacted. Thanks for pointing in the right direction.
Wondering of we should continue testing those. 1.9.3 is ooold, 2.0.0 is sometimes used by people that have GC issues on heroku with 2.X, but other than that it was shortlived.
@mshibuya do you want to pull the plug?

I ran into this on:

rails_admin 0.6.2
rails 4.2.1
ruby 2.3.0

When I commented out the rescue/re-raise that Bundler does, I saw this error underneath:
/Users/ryan/.rvm/gems/ruby-2.3.0@ramen/gems/safe_yaml-1.0.3/lib/safe_yaml/load.rb:43:in `<module:SafeYAML>': undefined method `tagged_classes' for Psych:Module (NoMethodError)

Adding this to my Gemfile allowed tests to run:
gem 'safe_yaml', '1.0.4'

Same issue here. After upgrading to ruby 2.2.4 I get the same error when trying to load the Rails server.

I am also experiencing this on upgrade from Ruby 2.2.0 to 2.3.0

Hey I just realized this might not be clear, but my comment above https://github.com/sferik/rails_admin/issues/2552#issuecomment-185955912 is a possible solution to this.
Force safe_yaml to be version 1.0.4 and see if that solves the problem for you.

@ryana Unfortunately I can’t do that, as the app is still on Rails 3 the latest version of rails_sdmin I can use is 0.4.9, which depends on safe_yaml ~> 0.6
Does this mean there is no way to upgrade to a recent version of Ruby without having to upgrade Rails for rails_admin to work?

I wouldn't go so far as to say there's no way to upgrade but so far I don't know what it is. Sorry :disappointed:

@ryana no worries. Thanks!

had the same issue, fixed using
gem 'safe_yaml', '0.6.3'

RA no longer depends on safe_yaml.


Set is not defined

Has anyone encountered this error im not too sure what I'm looking for to fix
ERROR in SERVER PRERENDERING
Encountered error: "ReferenceError: Set is not defined"

Sounds like you need some debugging help. I'm the creator of React on Rails. We have a support plan to help you. See shakacode.com/work/shakacode-pro-support.pdf.

I just ran into this.
Try adding mini_racer to your bundle file as I think you may be using therubyracer which uses an old version of JS that doesn't defined "Set"


Add DWN endpoints to Agent DID and ensure they sync

Currently I believe Agent DIDs do not set endpoints when they are created, and should. We should set the endpoints and have them be capable of sync so any state change to their DID set or other data relevant to then can be synced across wallet instances.

@csuwildcat The Agent DID's private key can't be stored in the DWN because otherwise it has no way to get to it to be able to sign messages with the key (which is necessary to read from the DWN).  Additionally, because the Agent's DID is deterministically created from the 12 words, you will have to consider whether this is still a desirable characteristic, and if so how to handle the non-deterministic service object that the issue proposes adding.

Yeah, meant everything but the private key, which you'd presumably move via 12 word entry in the new wallet


Add codefix for --noImplicitThis

If there's no containing function, no fix.
If this is defined outside the containing function, convert the containing function to an arrow function, since that's the most likely error.
If not:

In TS: Add this: any.
In JS: Tag as a @class if this is an assignment. Else tag with @this {any}.

This PR is old enough that it's taking a while to bring up-to-date. Currently:

Merged from master.
Builds.
All tests passes except for the newly added test, plus a test for another codefix (infer from usage) that now interferes with it.


np.object was a deprecated alias for the builtin object

   > `np.object` was a deprecated alias for the builtin `object`. To avoid this error in existing code, use `object` by itself. Doing this will not modify any behavior and is safe.
   > The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
   >     https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
   >
   > ----------------------------------------------------------------------
   > Ran 37 tests in 1.683s
   >
   > FAILED (errors=1)
   > Test failed: <unittest.runner.TextTestResult run=37 errors=1 failures=0>
   > error: Test failed: <unittest.runner.TextTestResult run=37 errors=1 failures=0>

NVM this was addressed on https://github.com/deepmind/dm_env/commit/50c13e69fe1385d8ce408535652ff506bd902ef3
There just hasn't been a released since then.


Errors on python setup.py install

I install step by step but it gives me that

@zhangdi-trying What did you do for this error? Did you upgrade the numpy version or did you ignore it?

I have down nothing. After this error occurs, I try to update the numpy, but it give me this

@zhangdi-trying did u solve it?i miss the same problem

no

@zhangdi-trying did u solve it?i miss the same problem

I got it!  You should change the version of panda, such as pip install pandas=1.4.4. Then you can run python install setup


Fix help message via structopt

Fixes #1.
Structopt generates help messages from crate metadata so it won't be out of sync with the actual crate name and version etc.
Though its no problem if you don't want to pull in another dependency for this.

Thanks for this PR! Structopt seems very useful and it was on my to-do list to check it out. I just cloned your fork and checked out your changes.
(1) I'm not a big fan of the way structopt orders the help info by default. Can you remove the duplicate display of the name and version, and get it to resemble the order of the current hand-written help text a bit more? I.e.:

Description text (what the tool does)
Required args (paths)
Options / flags
Additional info text with links to the repository

(2) I've also added an additional --ignore command (pushed the result today) which should be compiled to a Regex, can you make sure that it's also included in the new struct?
(3) As for your fix for the compiler warning on stdout.flush(), flushing isn't strictly necessary so expecting may be slightly overkill. I've since solved it in my version by assigning the return value to _ (see here). If there's another reason to use expect here I don't mind using that, but I don't feel it's necessary to panic if flushing fails.
Once these things are resolved I'll gladly merge this 😃
I did fix #1 in the hand-written help text as well. But going forward using a library like structopt will make it easier to add options, so I'm not at all opposed to adding the dependency to the project.

(1),(2): Already made the changes (i.e. remove the duplicate output, include ignore regex etc) locally and that went without a hitch.
current help output (under windows) would look like this:
project-cleanup 0.5.1
Wouter Buckens<EMAIL_ADDRESS>(www.woubuc.be)
Clean up build artifacts and dependency directories in Rust, Java and NodeJS projects to free up disk space.

Report bugs and suggestions to https://github.com/woubuc/project-cleanup/issues

USAGE:
    project-cleanup [FLAGS] [OPTIONS] [PATH...]...

FLAGS:
    -a, --all
            Cleanup even recently used projects

    -f, --force
            Skip confirmation prompt

    -h, --help
            Prints help information

    -V, --version
            Prints version information

OPTIONS:
    -i, --ignore <ignore>
            Regex to specify project directories to be ignored

ARGS:
    <PATH...>...
            One or more directories where the project-cleanup should start searching for projects. Defaults to current
            working directory

output with -h is more compact.
Unfortunately i cannot change the order in which flags/options/args/subcommands are displayed because that is how clap does it and structopt can only build on top of that.
Another thing that breaks in structopt or the toml parser is the trailing url after your email address in Cargo.toml:
Apparently : is converted into ,  somewhere along the way. Omitting the https: may be the way to go there.
Wouter Buckens<EMAIL_ADDRESS>(https, //www.woubuc.be)

(3) I'd rather know if something fails and where it happens - that being said flushing those buffers is not essential as the OS should take care of it once project cleaner exits and the file descriptor gets freed, so not panicking certainly makes more sense from a user perspective.
btw: building in support for colours on windows is (relatively) futile as both powershell and command prompt have problems displaying colours via ANSI escape codes (c.f. this)
Searching for code projects
  ✔ Searched 74 directories
  i Found 0 projects
Analysing projects
  ✔ Analysed 0 projects
  0 B of source code and project files
No projects have directories that can be removed
  This is likely because your projects were recently modified
  Run the application with `--all` to disregard file age
  Try `--help` for more options

That help output looks alright to me. Nice work!
If you can remove the panics from stdout.flush(), and fix the remaining conflicts, I can merge this one 😃
Wrt the ansi colours on Windows, I just added a fix for that so it should be better in the next version.

Rebased in #6


DSC Resource manifest schema should allow for setting properties as "keys"

Summary of the new feature / enhancement
While we can use the schema to define the properties and their individual schemas, there is no way to specify that a particular property is a "key".  This is distinct from required/optional.  The set of all "key" property values given to a resource defines the identity of the data under management.  Thus, passing the same set of key values, while varying other values, will result in a potential overwrite of the managed data.
The goal is to be able take two sets of properties that are intended for the same resource and determine if they are in conflict.  As an example:
<config1 contains>
- name: A
  type: my/packages
  properties:
    id: foo
    version: [1.0-2.0)

<config2 contains>
- name: B
  type: my/packages
  properties:
    id: foo
    version: [3.0-]

With the resource my/packages having a property key set containing id, we can determine that config1:A and config2:B are potentially in conflict (they have matching key values and differing non-key values).  This can be reported to the user so that they may determine how to proceed.
Proposed technical implementation details (optional)
No response

This should be part of the JSON Schema that describes a resources' instances. We could define it as part of a JSON Schema dialect as an annotation keyword, like keyProperty:
type: my/package
schema:
  embedded:
    type: object
    properties:
      id:
        title:       Package ID
        description: The unique ID for the package.
        type:        string
        keyProperty: true
      version:
        title:       Package Version
        description: The exact version or version range for the package.
        type:        string

Annotation keywords are (relatively) easy to add to a JSON Schema dialect, and can be safely ignored by tools that don't need to care about them (that is, they don't change the processing of the instance itself, like the properties applicator keyword, they provide information about the instance).
I've been thinking about the dialect problem for a while and I think it more-likely-than-not that we'll eventually need a dialect for DSC Resource instance schemas - you need dialects for authoring meta schemas if you want to support authoring/processing for those schemas beyond the built-in keywords.

Aside on the value of a schema dialect for instance schemas
A schema dialect can also really improve the authoring experience by providing shorthand for otherwise complex requirements.
For example, instead of defining an ensurable resource that uses the well-known _ensure property like this:
schema:
  embedded:
    type: object
    properties:
      _ensure:
        $ref: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/resource/properties/ensure.json

You could do this:
schema:
  embedded:
    type: object
    ensurable: true

That's an applicator keyword rather than an annotation keyword, but extremely useful.

From this blog post (didn't find anything newer): https://json-schema.org/blog/posts/custom-annotations-will-continue.  It seems that the right way is using a x- prefix for custom annotations.  So we could go with x-keyProperty.

Thinking about this today the problem with x-keyProperty is the admin can't tell from reading a config what are keys without understanding the schema.  An alternative proposal is to have a _keys property which contains key/value pairs that define key properties for the resource.  This makes it easy to read a config to understand and also allow the engine to validate there aren't duplicated keys.  @michaeltlombardi @mgreenegit

If I understand correctly, @SteveL-MSFT, instead of using an extended vocabulary in the resource schema, we would add a new property to the resource instance object - but I'm not sure I see how that translates to the resource manifest advertising to users and integrating tools which properties are key properties - unless the idea is that the config author defines which properties they don't want to conflict?
I think enabling users to extend which properties to treat as keys could have some use cases, but without resources declaring which properties must not conflict in a given configuration, we shift the responsibility for figuring out and declaring key properties from the resource to the user and break the integration model for several higher order tools.
As for indicating which properties in the configuration are keys for resources, I think that might be better handled by the VS Code extension rather than altering the schema for how you define resource instances.

@michaeltlombardi v3 resources would explicitly have a property called _keys and define their keys as subproperties of this object.  Expectation is that conflict only exists if ALL keys match the same values so the engine can validate that across instances of the same resource.

That would make the proposed resource schema something like...
$schema:   https://json-schema.org/draft/2020-12/schema
type:      object
required: [_keys]
properties:
 _keys:
   type: object
   required: [keyPath]
   properties:
     keyPath:   { type: string }
     valueName: { type: string }
 valueData:
   type: object
   minProperties: 1
   maxProperties: 1
   properties:
     string:       { type: string }
     expandString: { type: string }
     binary:       { type: array, items: { type: integer } }
     dWord:        { type: integer }
     multiString:  { type: array, items: { type: string } }
     qWord:        { type: integer }

That could be fairly succinct (and is addressable in the manifest schema, we can require the properties definition for embedded schemas to define the _keys property as an object) - I'm not wholly opposed to it, but it is a large breaking change for prior resource design compared to using an annotation keyword.


[experimental] Symbols view with highlighting

[x] All compiled assets are included (atom packages are git tags and hence the built files need to be a part of the source control)

added highlighting to #1408
Additional noteworthy changes:

added CSS class atom-typescript to the root-element in simpleSelectView (for enabling specific/targeted styling of the SelectListView)
renamed file fileSymbolsTag.ts to symbolsTag.ts (since the Tag class is used for both file- and project-symbols)

OK, I think I did all the changes, could you review again?

Thanks. I'll just merge this right now. We don't really need itemsClassList to be configurable because a stylesheet kinda depends on it being atom-typescript, but it's easier to fix on my end.


Change to try out CLA hook in PR

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


Made the download of the logicappscript more readable

change at section "3. Run the following cmdlet to download the createazurelogicapp.ps1 script file on your local machine."
Made the download of the logicappscript more readable

@michawets : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ChristianMontoya , small update, bit the same as the Runbook script, should make it more readable

Hi @ChristianMontoya , a little ping 😊

@stgeorgi : Can you take a look?

approved

Hi @Heidilohr, could you merge the pull request😊 ? Thank you

Closed due to file-based merge conflict; updates submitted in new PR.


tiproxyctl: change --curls to --host and --port

What problem does this PR solve?

Issue Number: close #656
Problem Summary:
tiproxyctl --curls=<IP_ADDRESS>:3080
tidb-ctl --host=<IP_ADDRESS> --port 10080
They are inconsistent.
What is changed and how it works:
Change tiproxyctl arguments from --curls to --host and --port
Check List
Tests

[ ] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Try bin/tiproxyctl --help and bin/tiproxyctl --host localhost --port 3080 config get
Notable changes

[ ] Has configuration change
[ ] Has HTTP API interfaces change
[ ] Has tiproxyctl change
[ ] Other user behavior changes

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
- Change tiproxyctl arguments from --curls to --host and --port

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@ca75a82). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #664   +/-   ##
=======================================
  Coverage        ?   69.35%
=======================================
  Files           ?       95
  Lines           ?     9174
  Branches        ?        0
=======================================
  Hits            ?     6363
  Misses          ?     2341
  Partials        ?      470

Flag
Coverage Δ

unit
69.35% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


[Improve][Connector-V2][StarRocks] Delete the Mapper may not be used

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

Please change your title to [Improve][Connector-V2][StarRocks] Delete the Mapper may not be used

Please fix your code style.

https://github.com/apache/incubator-seatunnel/blob/dev/docs/en/contribution/setup.md#install-jetbrains-idea-checkstyle-idea-plugin
You can change your code style through this document.

 I’LL READ IT， THANKS FOR THE ADVICE.
---Original---
From: @.>
Date: Mon, Nov 28, 2022 01:52 AM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [apache/incubator-seatunnel] [Improve][Connector-V2][StarRocks]Delete the Mapper may not be used (PR #3579)
https://github.com/apache/incubator-seatunnel/blob/dev/docs/en/contribution/setup.md#install-jetbrains-idea-checkstyle-idea-plugin
You can change your code style through this document.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


added nakamura on LP

@erichin Hi bato, I want you to translate nakamura's profile in Chinese. I made it by google translator , so modified it as a correct chinese :)

@fiestared nakamura's profile translation has been finished and committed. Have a nice day ; )


False positive warning about different source settings

What happened?
A complex dependency hierarchy where the same repo are downloaded multiple times output a warning repeated (probably the same amount of times the repo is downloaded by devspace). Se below. But when i check the files, they are identical. I also checked the line endings in VS Code, they are also the same.
warn Seems like you have multiple dependencies with name hn-felleslogg, but they use different source settings (C:\Users\andre\.devspace\dependencies\https-dev-azure-com-REPLACED-REPLACED-git-hn-fellesl-3697925\devspace.yaml != C:\Users\andre\.devspace\dependencies\https-REPLACED-dev-azure-com-REPLACED-REPLACED-git--9489b9f\devspace.yaml). This can lead to unexpected results and you should make sure that the devspace.yaml name is unique across your dependencies or that you use the dependencies.overrideName option

warn Seems like you have multiple dependencies with name hn-felleslogg, but they use different source settings (C:\Users\andre\.devspace\dependencies\https-dev-azure-com-REPLACED-REPLACED-git-hn-fellesl-3697925\devspace.yaml != C:\Users\andre\.devspace\dependencies\https-REPLACED-dev-azure-com-REPLACED-REPLACED-git--9489b9f\devspace.yaml). This can lead to unexpected results and you should make sure that the devspace.yaml name is unique across your dependencies or that you use the dependencies.overrideName option

warn Seems like you have multiple dependencies with name hn-felleslogg, but they use different source settings (C:\Users\andre\.devspace\dependencies\https-dev-azure-com-REPLACED-REPLACED-git-hn-fellesl-3697925\devspace.yaml != C:\Users\andre\.devspace\dependencies\https-REPLACED-dev-azure-com-REPLACED-REPLACED-git--9489b9f\devspace.yaml). This can lead to unexpected results and you should make sure that the devspace.yaml name is unique across your dependencies or that you use the dependencies.overrideName option

What did you expect to happen instead?
No warnings
How can we reproduce the bug? (as minimally and precisely as possible)
Set up a complex dependency hierarchy, and use the files below?
Left
version: v2beta1
name: hn-felleslogg

imports:
- git<EMAIL_ADDRESS>  branch: master
  subPath: kubernetes/devspace/functions.yaml

dependencies:
  hn-oppsett:
    git<EMAIL_ADDRESS>    branch: master
    pipeline: deploy

pipelines:
  deploy: |-
    REPLACED_default_deploy
    ensure_hosts_file_localhost_entry felleslogg-internalapi.k8s.REPLACED.utvikling
  dev: |-
    REPLACED_default_dev

deployments:
  felleslogg:
    namespace: dev
    helm:
      chart:
        name: ./helm-chart
      valuesFiles:
        - helm-chart/values.common.yaml
        - helm-chart/values.dev.yaml

dev:
  felleslogg-internalapi:
    labelSelector:
      app.kubernetes.io/name: felleslogg-internalapi
    resources:
      limits:
        memory: 2Gi
      requests:
        cpu: 2000m
        memory: 512Mi
    devImage: mcr.microsoft.com/dotnet/sdk:6.0
    env:
      - name: NUGET_REPLACED_SOURCE_PAT
        value: ${NUGET_REPLACED_SOURCE_PAT}
    sync:
    - path: ./:/app
      excludeFile: .dockerignore
      startContainer: true
    command: ["dotnet"]
    args: ["watch", "run", "--launch-profile", "Felleslogg.InternalAPI.Kubernetes", "--project", "/app/Source/Felleslogg/Felleslogg.InternalAPI/", "--non-interactive"]
    open:
    - url: http://felleslogg-internalapi.k8s.REPLACED.utvikling:30080/swagger/index.html

Right
version: v2beta1
name: hn-felleslogg

imports:
- git<EMAIL_ADDRESS>  branch: master
  subPath: kubernetes/devspace/functions.yaml

dependencies:
  hn-oppsett:
    git<EMAIL_ADDRESS>    branch: master
    pipeline: deploy

pipelines:
  deploy: |-
    REPLACED_default_deploy
    ensure_hosts_file_localhost_entry felleslogg-internalapi.k8s.REPLACED.utvikling
  dev: |-
    REPLACED_default_dev

deployments:
  felleslogg:
    namespace: dev
    helm:
      chart:
        name: ./helm-chart
      valuesFiles:
        - helm-chart/values.common.yaml
        - helm-chart/values.dev.yaml

dev:
  felleslogg-internalapi:
    labelSelector:
      app.kubernetes.io/name: felleslogg-internalapi
    resources:
      limits:
        memory: 2Gi
      requests:
        cpu: 2000m
        memory: 512Mi
    devImage: mcr.microsoft.com/dotnet/sdk:6.0
    env:
      - name: NUGET_REPLACED_SOURCE_PAT
        value: ${NUGET_REPLACED_SOURCE_PAT}
    sync:
    - path: ./:/app
      excludeFile: .dockerignore
      startContainer: true
    command: ["dotnet"]
    args: ["watch", "run", "--launch-profile", "Felleslogg.InternalAPI.Kubernetes", "--project", "/app/Source/Felleslogg/Felleslogg.InternalAPI/", "--non-interactive"]
    open:
    - url: http://felleslogg-internalapi.k8s.REPLACED.utvikling:30080/swagger/index.html

Here is a screenshot of them diffed in VS Code

Local Environment:

DevSpace Version: 6.2.4
Operating System: windows
ARCH of the OS: AMD64
Kubernetes Cluster:
Cloud Provider: kind (local)
Kubernetes Version: not relevant

@Andrioden thanks for reporting this issue! We will investigate and fix this problem!

@FabianKramm - Could you look into at the same time if all dependencies are loaded, even when limiting what dependencies are used?
Se below. I get the warning 4 times.

Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Deleting outdated charts
deploy:tjenester-helsenorge Deploying chart ./helm-chart (tjenester-helsenorge) with helm...
deploy:tjenester-helsenorge Deployed helm chart (Release revision: 16)
deploy:tjenester-helsenorge Successfully deployed tjenester-helsenorge with helm

@Andrioden Hello! I'm looking into this issue. Based on the log output, it seems that different revisions are being used for the dependency hn-felleslogg. DevSpace will consider the dependency to be different if a different revision is used somewhere in the dependency tree, even if devspace.yaml is the same in both revisions.
This is based on the output from the log:
(C:\Users\andre\.devspace\dependencies\https-dev-azure-com-REPLACED-REPLACED-git-hn-fellesl-3697925\devspace.yaml != C:\Users\andre\.devspace\dependencies\https-REPLACED-dev-azure-com-REPLACED-REPLACED-git--9489b9f\devspace.yaml)

I'd be curious if you could provide more of the dependency tree configuration where hn-felleslogg is included as a dependency. It seems like revision is used, but with different values. What doesn't make sense to me is that the second path being compared doesn't include the substringgit-hn-fellesl-, and instead has git--. Seeing how the dependency is referenced in the overall graph would help determine if there is a bug.

@lizardruss - I took another look, and it looks like we messed up. We are using different git urls pointing to the same repo, within the same dependency hierarchy. Se below.
I will correct it later, will report back if it fixes it.
repo1
  hn-felleslogg:
    git: https://dev.azure.com/REPLACED/REPLACED/_git/HN-Felleslogg
    branch: master

repo2
  hn-felleslogg:
    git<EMAIL_ADDRESS>    branch: master

@lizardruss - I fixed all dependency git urls. Still have the same problem
PS C:\Projects\NHN\HN-Configuration> devspace deploy
warn Seems like you have multiple dependencies with name hn-configuration, but they use different source settings (C:\Projects\NHN\HN-Configuration\devspace.yaml != C:\Users\andre\.devspace\dependencies\https-nhnfelles-dev-azure-com-nhnfelles-helsenorge-git--50633e1\devspace.yaml). This can lead to unexpected results and you should make sure that the devspace.yaml name is unique across your dependencies or
that you use the dependencies.overrideName option

warn Seems like you have multiple dependencies with name hn-configuration, but they use different source settings (C:\Projects\NHN\HN-Configuration\devspace.yaml != C:\Users\andre\.devspace\dependencies\https-nhnfelles-dev-azure-com-nhnfelles-helsenorge-git--50633e1\devspace.yaml).  I think this might be working as expected.
While the files might be identical, that isn't really what the message is communicating. The sources are different (or might be different) because of how they're resolved. In this case, the dependency graph has created a circle, beginning and ending with hn-configuration, but the beginning is a local workspace (C:\Projects\NHN\HN-Configuration\devspace.yaml) and the end is a cloned git repository (C:\Users\andre\.devspace\dependencies\https-nhnfelles-dev-azure-com-nhnfelles-helsenorge-git--50633e1\devspace.yaml). DevSpace isn't comparing the contents of these devspace.yaml because those files could import other configuration using imports or local manifests from deployments, both of which could have different contents. Because of that possibility, it wouldn't always be correct to consider those the same, and could lead to a confusing scenario where one might be making changes to the local workspace and expect to see those changes in the dependency without pushing the changes to the git repository.
The suggestion here would be to use the dependencies.overrideName option to modify the name to something like hn-configuration-master, which should clear the warning.

@lizardruss - I see.
I tested by running devspace deploy for a repo that has several circulating dependencies, but the repo are not part of the circulation it self. That worked great, so your reasoning checks out.

DevSpace isn't comparing the contents of these devspace.yaml because those files could import other configuration using imports or local manifests from

Aah, damn, good point. I see how doing a devspace.yaml string content compare is not the way. I could ofc argue, "compare all locally references files then", but thats going to be a hellish work which needs coding the understanding of how manifest, helm chart files etc relate", so yea, i wouldnt suggest this.
Wouldnt the correct behavior be that when the top devspace deployed repo (hn-configuration here) is dependent on below in the dependency hierarchy, then that top devspace is assumed to be correct? And if anything, it should be logged as info?

The suggestion here would be to use the dependencies.overrideName option to modify the name to something like hn-configuration-master, which should clear the warning.

I cant seem to find documentation for this? Could you give an example?

Ah, sorry, the property is just the key used in dependencies, so you can try:
dependencies:
  ...
  hn-configuration-master:
    git<EMAIL_ADDRESS>    branch: master

The error message is a little misleading there. Let us know if that doesn't work.

I see, so the dependency name and the devspace name cant be the same if there is a circular dependency.
The following works
hn-configuration
version: v2beta1
name: hn-configuration-s # <- Changed to different

hn-sts
dependencies:
  hn-configuration:
    git<EMAIL_ADDRESS>    branch: master

I am not entirely happy about this solution. But i guess you can solve the issue if you dont see any better way to design this.

@lizardruss  - I had another take on this. Not completely happy with how DevSpace behave.
TLDR:

✔ DevSpace (the tool) should have a clear opinion on how things behave
✔ Ensure the local hn-configuration (service) is deployed singularly, priority over the dependent one
❌ Do not give a warning
❌ Changing the name should not affect wheter or not the warning happens

Long:
In the case described here, where i run devspace deploy from hn-configuration repo which is part of a circular chain, i expect the local devspace.yaml to be deployed to kubernetes, not any of the dependent versions of the same repo. The fact that the name: name: hn-configuration and the dependency name is equal is imo beside the point, even if the names are different i still want the local hn-configuration to be deployed, and not the dependent ones, as long as the service name is equal.
deployments:
  configuration: # <- Service name

Changing the name to hide the warning seems like bad design, why should what the name matter, its still a potential problem.
DevSpace should be opinionated on which (local hn-configuration vs dependent hn-configuration) wins and are actually deployed. As per the deployment sequence, i know the local wins.
So:

The name should not matter, the warning should not happen
If you still insist it does, what do you (DevSpace tool) interpret the names to mean? They are not unique names for deployments,
Also, why would renaming either of them matter, cant devspace resolve that internally? By prefix the name internally by "local-name" (local-hn-configuration) vs "dependency-name" (dependency-hn-configuration).

Or to ask in a different way, what am I the developer telling YOU DevSpace creators by giving it a different name?

I talked to the team and it's intended that DevSpace should use the local copy when the names match. The warning was a mistake.
I assumed that since the dependency was defined using git, that it should use the git copy in all scenarios (a very literal interpretation of the config), and that this was to avoid issues with uncommitted local changes.
Anyway, I'll be adding tests to verify the behavior and to verify that the warning is not displayed.


Testing

Please provide the code to test a single video and classify it according to your demo video!

It is an offline demo using extracted features rather than original videos, and we will consider end-to-end testing in the future.

how to get these extracted features to from a video to pass them to the model ?


[CAMEL-20989] camel-jbang: Improve label matching in kubernetes spring-boot

https://issues.apache.org/jira/browse/CAMEL-20989

Waiting on https://github.com/apache/camel/pull/14859

@tdiesler, could you rebase?

out-of-date


Download progress does not work using latest AzCopy binary

Download progress does not work using latest AzCopy binary

updated azcopy event args based on latest binary release 10.9.0
bumped minimum supported azcopy version to 10.9.0
added ability to cancel downloads when using azcopy

@khanaffan  can you take a look?

@khanaffan @GintV what's the status of this?  Did you two discuss it outside of this PR?  Last I heard there was some worry about compatibility but didn't catch the full details.

@calebmshafer I was out sick for the past week. We discussed this previously and the concern was that this minimum azcopy version update would silently break apps that won't be using latest azcopy version (it will start using http instead of azcopy for downloads). I think main concern was about Design Review Backend and General Purpose Backend. But I think you mentioned that both of them should be using azcopy 10.x on deployment, so in theory it pulls latest version. In that case, we could proceed with this PR as is. If not, I can strip out minimal version update and leave only download cancellation. What do you think @khanaffan?

This PR has been open for 23 days, rebuilding itself every time anyone else merges to master. Closing until it's ready to be merged (set auto-merge when that happens please).


also fall back to duckduckgo on in-text citations

accidentally missed this one the first time around

Snuck in a commit to clean up the README

Very fair, good changes. Still in the future it might be better to keep PRs single-purpose where possible, so the git history is more meaningful when using tooling.


DNS for Services and Pods

Kubernetes version: v1.14.10-gke.36
redis-cst1021                  autossl-redis            ClusterIP      <IP_ADDRESS>   <none>          6379/TCP                                                                                3d7h

# dig @<IP_ADDRESS> -x <IP_ADDRESS> +short
autossl-redis.redis-cst1021.svc.cluster.local.

# ;; ANSWER SECTION:
# <IP_ADDRESS>.in-addr.arpa. 30	IN	PTR	autossl-redis.redis-cst1021.svc.cluster.local.

The DNS for Services and Pods docs mention PTR records for pods, but does not mention PTR records for services. I see that they are created, can these documents be updated?

I don't understand why noone has acknowledged this visible lack in service PTR record documentation.


🚀 - Provide support for Kotlin language

Which @codeimage/* package(s) are relevant/releated to the feature request?
config
Description
Kotlin is fast growing language on JVM platform and millions of developers use it daily. Kindly provide Kotlin syntax highlighting support in codeimage.

Thanks for quick response @riccardoperra
I've tried Kotlin syntax on given webapp and satisfied with result as shown below.
Let me know when will you integrate it with main CodeImage webapp.


Restored SQL file windows don't always show the connection toolbar

Type: Bug
On occassion, maybe every month or so or perhaps after an update, when ADS opens, any previously opened SQL windows that are reopened at startup do not have the connection bar such that you can connect to SQL or run your queries.
There is no consistent repro in which it happens, it just suddenly starts having issues. Closing and reopening the same SQL file resolves the issue. Any other windows that are opened after ADS starts are fine as well. It is just when ADS is restoring previously opened windows.
Repro steps for when the problem replicates.

Open ADS
Open any SQL file and verify the connect toolbar is available
Close ADS
Open ADS again so that it restores the previously opened SQL file window

When the problem replicates the window will open without a connection toolbar. Any other windows you open will be fine. Closing and reopening the same SQL file also resolves the issue.

This has been happening for many releases now and is likely not related to any recent changes. Others have reported the same issue on StackOverflow I've noticed.
Azure Data Studio version: azuredatastudio 1.49.0 (6e6d22ddd74bbb4fbe344ed80b93b53489fe0239, 2024-08-01T05:19:02.202Z)
OS version: Windows_NT x64 10.0.22631
Restricted Mode: No
Preview Features: Enabled
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz (16 x 3600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.88GB (6.53GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Argh!!! This is just getting worse and worse with every update from the team. Please stop breaking this stuff!!!! Reloading document patterns have been around for decades, why is this so hard to get right?
Now, with version 1.49.1, not only does the last closed session not always reload with the connection toolbar but now we have the new query window also popping up in a completely separate window. So starting ADS results in 2 windows open - one containing an empty query I don't need and the query window that was open when I closed the session last time and may or may not be usable with the connection toolbar. If there is a setting available to change this then I cannot find it anywhere. Searched for session, startup and recent and nothing says stop opening query editor in separate window. The Window: Open Files in New Window is set to off.
Please stop adding features and fix the core bugs in this product. It is at the point I'm ready to switch back to SSMS and live with the broken Intellisense. I spend more time working around the bugs in ADS then I do using it to query data.


Add gochist to sig-docs-en-owners

This is a workaround for #14008. The power will be used only for the i18n/ and README-ko.md.

/cc @zacharysarah

/lgtm
/approve

The power will be used only for the i18n/ and README-ko.md.

👍


Update HardwareCompatList.md

Docs Build status updates of commit 0a7c3a5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/learn-about-hardware/HardwareCompatList.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.


Skewed page layout at /fundamentals/principles/?hl=ru

The layout of one section, when reading in Russian, got skewed because of an exceedingly multiline title.

The same section in English looks perfect:

Urgh,  Not sure how we are going to deal with this as there is a max
height.... Will have a think.
On Sun Jan 04 2015 at 19:37:44 Den Patin<EMAIL_ADDRESS>wrote:

The layout of one section, when reading in Russian
https://developers.google.com/web/fundamentals/principles/?hl=ru, got
skewed because of an exceedingly multiline title.
[image: screen shot 2015-01-04 at 10 32 41 pm]
https://cloud.githubusercontent.com/assets/1271040/5607193/b88c0dd6-9461-11e4-84e3-ffcbaa365b1b.png
The same section in English
https://developers.google.com/web/fundamentals/principles/?hl=en looks
perfect:
[image: screen shot 2015-01-04 at 10 33 00 pm]
https://cloud.githubusercontent.com/assets/1271040/5607194/bcb2a2ee-9461-11e4-9ebd-6080dc74d7db.png
—
Reply to this email directly or view it on GitHub
https://github.com/google/WebFundamentals/issues/1070.

if rename "Домашняя страница и навигация по сайту" to "Главная страница" and "Интерактивные формы" to "Удобные формы" - all will be nice. How you think?

@yuzver Are you sure there is a need to change the title of "Интерактивные формы"? The layout there is fine. Reducing the line to just "домашняя страница" is a bit rash because in this section menus are as well considered as the home page structure. Maybe "Домашняя страница и меню" could be a remedy?

@denpatin, according to my feelings: easier to cut two long title, which below is a description of the topic. Not the way to translate literally(!) from English or to change specifically the partition layout because of the long headers;)

Главная страница и меню: http://screencast.com/t/bZEOTgoyCbZx

Главная странца: http://screencast.com/t/0swPQD3gZfl
Section is devoted clearly the main page, so the extra mentioning about navigation I seem superfluous.

Интерактивные формы: http://screencast.com/t/or0qmzPQvqoU

Удобные формы: http://screencast.com/t/3m6e6HYgEL2
"icon-lessons" zooming in on the text and it doesn't look good. Or it's ok?

@yuzver Only "главная страница" looks, of course, more pleasant to eyes. However the meaning of this title is not full.
As for "удобные формы", I cannot say the word "удобный" anyhow correlates with "интерактивный". Moreover, on the same level with "интерактивные формы" there is a two-line title so I do believe there is no need in the change.

I believe this is now fixed.


implement sitemap

Hi Rehan
Your project is perfect but i have a problem with my test project that i am new user of your template
I create one controller and i would like to implement sitemap but i didnt see my urls in the sitemap.xml file what is the problem also İ didn't know how i will implement could you explain how will it
thank you

Hi, I'm not clear on what your problem is, can you give more information, even a code sample?
Adding items to the sitemap is as easy as adding the following code in SitemapService.cs:
var urlToControllerAction = urlHelper.AbsoluteRouteUrl("[Enter Controller Action Route Name Here]");
nodes.Add(
               new SitemapNode(url)
               {
                   Priority = 0.9
               });

I assume you've got things sorted. If not, re-open the issue.


circular dependency

found with pipdeptree

Version of wrapt_timeout_decorator : <IP_ADDRESS>
Python Version : 3.9
OS, OS Version : macOs 13.1

dear @yairVanti ,
thank You for the report - it is resolved.
yours sincerely
bitranox


Add missing word to README

Description
So, I just forgot how this syntax works 😅 I came back here to look it up, and I just noticed I missed "with" or "during", or basically any word that would make this a proper sentence.
Additional context
For my defense, I'm not a native English speaker :P

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[x] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Follow the Style Guide.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).

Haha thanks mate 🙏
(please could you rename the commit to chore: update README.md just so that it passes the semantic step?)

Sure thing, just ammended the commit! I can't believe I forgot about the semantic prefix again 🙈


make tre-destroy fails when keyvault has purge protection

Describe the bug
Run make tre-destroy when key vault has purge protection enabled
Deleting keyvault: kv-mrtredemo Warning! If you have soft-delete protection enabled on this key vault, you will not be able to reuse this key vault name until the key vault has been purged from the soft deleted state. Please see the following documentation for additional guidance. https://docs.microsoft.com/azure/key-vault/general/soft-delete-overview Purging keyvault: kv-mrtredemo (MethodNotAllowed) Operation 'DeletedVaultPurge' is not allowed. Code: MethodNotAllowed Message: Operation 'DeletedVaultPurge' is not allowed. make: *** [Makefile:183: tre-destroy] Error 1
Commenting out this step allowed me to continue.
cc @tamirkamara

@marrobi,

Were you using the latest version (I had something changed last Tuesday IIRC)?
Do you have the script output by any chance?


Is Lemma really syntactic sugar ?

Good morning,
I came across some problem with the syntax "Lemma". From the school and the tutorial, I thought that when we write:
val name_lemma :
    x_1:type_1{ refine_1 } ->
    ...
    x_n:type_n{ refine_n } ->
    Lemma (requires refine_req)
                 (ensures refine_ens)

It was just syntactic sugar for:
val name_lemma :
    x_1:type_1 ->
    ...
    x_{n-1}:type_{n-1} ->
   x_n:type_n{ refine_1 /\ .../\ refine_n /\ refine_req } ->
   u:unit{ refine_ens }

However, it does not seems to work exactly like this, specifically with the (requires refine_req). In the following exemple, I thought all the lemma_test 1 to 4, and 5 to 9 should be equivalent but I obtain some errors with lemmas 1, 5 and 6 (the ones with the refine_req different from True)
module MultiSet

assume type multiset: a:Type -> Type

assume val not_empty: multiset 'a -> Tot bool

assume val f: m:multiset 'a{not_empty m} -> Tot (multiset 'a)
assume val g: multiset 'a -> Tot (multiset 'a)

assume val lemma_test1 : m:multiset 'a ->
  Lemma (requires (not_empty m))
        (ensures (g m = f m))

assume val lemma_test2 : m:multiset 'a{not_empty m} ->
  Lemma (requires True)
        (ensures (g m = f m))

assume val lemma_test3 : m:multiset 'a{not_empty m} ->
  Lemma (ensures (g m = f m))

assume val lemma_test4 : m:multiset 'a{not_empty m} -> Tot (u:unit{g m = f m})

assume val lemma_test5 : m1:multiset 'a -> m2:multiset 'a ->
  Lemma (requires (not_empty m1 /\ not_empty m2))
        (ensures (f m1 = f m2))

assume val lemma_test6 : m1:multiset 'a -> m2:multiset 'a{not_empty m1} ->
  Lemma (requires (not_empty m2))
        (ensures (f m1 = f m2))

assume val lemma_test7 : m1:multiset 'a -> m2:multiset 'a{not_empty m1 /\ not_empty m2} ->
  Lemma (requires True)
        (ensures (f m1 = f m2))

assume val lemma_test8 : m1:multiset 'a{not_empty m1} -> m2:multiset 'a{not_empty m2} ->
  Lemma (requires True)
        (ensures (f m1 = f m2))

assume val lemma_test9 : m1:multiset 'a -> m2:multiset 'a{not_empty m1 /\ not_empty m2} -> Tot (u:unit{f m1 = f m2})
``````

What did I miss ?

By the way, in one of my previous message, some explained me the semantics for the error messages but it seems there is something strange with the calcul of the columns. I obtained the error message:
``````
pc14:FStarVersion vincentcheval$ fstarml test2.fst
Error test2.fst(10,212-12,0): The following problems were found:
	Subtyping check failed; expected type m:(multiset 'a){(not_empty m)}; got type (multiset 'a) (test2.fst(12,287-12,0))
Error test2.fst(23,104-25,215): The following problems were found:
	Subtyping check failed; expected type m:(multiset 'a){(not_empty m)}; got type (multiset 'a) (test2.fst(25,215-25,215))
Error test2.fst(27,257-29,0): The following problems were found:
	Subtyping check failed; expected type m:(multiset 'a){(not_empty m)}; got type m2:(multiset 'a){(not_empty m1)} (test2.fst(29,366-29,0))
Verified module: Prims
Verified module: MultiSet
Error: 3 errors were reported (see above)
``````

The lines are correct but not the columns.

Thank for your help.

Vincent

I think all problems with lemma will be solved if we fix #57, closing.


Best effort on loading Kaldi data dir into lhotse

I coded this up to get a better understanding on how the Kaldi data dir maps onto lhotse manifests, and which pieces might be missing on either side.
The resulting yamls for mini_librispeech look like the following.
AudioSet:
- duration_seconds: 10.885
  id: 1272-135031-0000
  num_samples: 174160
  sampling_rate: 16000
  sources:
  - channel_ids:
    - 0
    source: 'flac -c -d -s /Users/pzelasko/jhu/kaldi/egs/mini_librispeech/s5/corpus//LibriSpeech/dev-clean-2/1272//135031/1272-135031-0000.flac '
    type: command
- duration_seconds: 11.13
  id: 1272-135031-0001
  num_samples: 178080
  sampling_rate: 16000
  sources:
  - channel_ids:
    - 0
    source: 'flac -c -d -s /Users/pzelasko/jhu/kaldi/egs/mini_librispeech/s5/corpus//LibriSpeech/dev-clean-2/1272//135031/1272-135031-0001.flac '
    type: command

SupervisionSet:
- duration: 10.885
  id: 1272-135031-0000
  language: null
  recording_id: 1272-135031-0000
  speaker: 1272-135031
  start: 0.0
  text: BECAUSE YOU WERE SLEEPING INSTEAD OF CONQUERING THE LOVELY ROSE PRINCESS HAS
    BECOME A FIDDLE WITHOUT A BOW WHILE POOR SHAGGY SITS THERE A COOING DOVE
- duration: 11.13
  id: 1272-135031-0001
  language: null
  recording_id: 1272-135031-0001
  speaker: 1272-135031
  start: 0.0
  text: HE HAS GONE AND GONE FOR GOOD ANSWERED POLYCHROME WHO HAD MANAGED TO SQUEEZE
    INTO THE ROOM BESIDE THE DRAGON AND HAD WITNESSED THE OCCURRENCES WITH MUCH INTEREST

That looks great!
On Thu, Apr 30, 2020 at 8:41 AM Piotr Żelasko<EMAIL_ADDRESS>wrote:

I coded this up to get a better understanding on how the Kaldi data dir
maps onto lhotse manifests, and which pieces might be missing on either
side.
The resulting yamls for mini_librispeech look like the following.
AudioSet:

duration_seconds: 10.885
id: 1272-135031-0000
num_samples: 174160
sampling_rate: 16000
sources:

channel_ids:

0
source: 'flac -c -d -s /Users/pzelasko/jhu/kaldi/egs/mini_librispeech/s5/corpus//LibriSpeech/dev-clean-2/1272//135031/1272-135031-0000.flac '
type: command

duration_seconds: 11.13
id: 1272-135031-0001
num_samples: 178080
sampling_rate: 16000
sources:

channel_ids:

0
source: 'flac -c -d -s /Users/pzelasko/jhu/kaldi/egs/mini_librispeech/s5/corpus//LibriSpeech/dev-clean-2/1272//135031/1272-135031-0001.flac '
type: command

SupervisionSet:

duration: 10.885
id: 1272-135031-0000
language: null
recording_id: 1272-135031-0000
speaker: 1272-135031
start: 0.0
text: BECAUSE YOU WERE SLEEPING INSTEAD OF CONQUERING THE LOVELY ROSE PRINCESS HAS
BECOME A FIDDLE WITHOUT A BOW WHILE POOR SHAGGY SITS THERE A COOING DOVE
duration: 11.13
id: 1272-135031-0001
language: null
recording_id: 1272-135031-0001
speaker: 1272-135031
start: 0.0
text: HE HAS GONE AND GONE FOR GOOD ANSWERED POLYCHROME WHO HAD MANAGED TO SQUEEZE
INTO THE ROOM BESIDE THE DRAGON AND HAD WITNESSED THE OCCURRENCES WITH MUCH INTEREST

You can view, comment on, or merge this pull request online at:
https://github.com/pzelasko/lhotse/pull/9
Commit Summary

Best effort on loading Kaldi data dir into lhotse

File Changes

A lhotse/kaldi.py
https://github.com/pzelasko/lhotse/pull/9/files#diff-e6076ad75c552431efef41781049476f
(80)

Patch Links:

https://github.com/pzelasko/lhotse/pull/9.patch
https://github.com/pzelasko/lhotse/pull/9.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pzelasko/lhotse/pull/9, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFLO7XA3DSFACFFJBN6MTRPDCLBANCNFSM4MU4TKNQ
.

Once we merge the features PR, I will add a CLI mode for converting Kaldi data dir into lhotse manifests. It will be helpful for comparison when I start creating a pure-lhotse data prep scripts, and might help some people adopt lhotse more quickly.


Added nanomsg classes - DO NOT MERGE

new PR to just add a new queuenado pattern using nanomsg.
please review for design to ensure there is nothing out of the ordinary. you will not be able to build this unless you have nanomsg installed.
please check for typos/code style errors, but you only need to point them out once per file, as I have an editor that I can use to set the style for the entire file.
TODO:
integrate with research where we want to test perofrmance

In the packaging spec file you need to add a dependency to the nanomsg rpm.

@john-gress et. al. it's annoying but since Yannicks user is gone and his account is closed this is an orphaned pull request which cannot be pulled down by another user. It is very closely related to this old github bug which is still unresolved: https://github.com/isaacs/github/issues/168
The solution I'm going for here is that I have created a copy of our master master-nanomsg and I have edited this pull request to be directed to that branch instead.  I will merge it there and it is now available for us for pulling down and working with
(another approach could be to manually copy all the changes in this PR and do a new PR)


Remove build log from source control

Hello @MarkXA
Again, this is awesome that you're participating and submitting a pull request.  We can't thank you enough.  But you submitted it against Master again (but from your Development branch).  Can you please only submit PR's against our Development branch?  I'm sorry to have to ask you to do this again, but I want you to have the credit for this enhancement.  I'm not intentionally trying to make this difficult for you.
Background Info
Our Master branch is meant to be the cleanest part of source control that usually reflects the most recent release.  Our Development branch is the equivalent of daily development, merged from everyone that's working on the code base.


Not sure how to insert a video by following documentation

Hello!
While reading the documentation for this plugin:
import Reels from 'expo-instagram-reels';

...

// Pass the array of objects with _id and uri as props
<Reels videos={videos} />

I am not sure how to insert a list of videos here. What I have tried is
<Reels videos={['htttp://link-to-hls-manifest-video-here']} />

But definitely there is something I am missing.
If I have the video urls, can you help me with a sample code to be used?

Videos array should be in this form
[
    {
        _id: '1',
        uri: { uri: "https://raw.githubusercontent.com/kartikeyvaish/React-Native-UI-Components/main/src/Reels/config/videos/sample.mp4" },
    },
    {
        _id: '2',
        uri: { uri: "https://raw.githubusercontent.com/kartikeyvaish/React-Native-UI-Components/main/src/Reels/config/videos/sampleLandscape.mp4" },
    },
    {
        _id: '3',
        uri: { uri: "https://raw.githubusercontent.com/kartikeyvaish/React-Native-UI-Components/main/src/Reels/config/videos/samplePortrait.mp4" },
    }
]

This looks messy but will fix this in future.


Code cleanup and misc

js style lints

Added yarn lint - using semistandard. (feel free to switch to standard if desired, since there was an inconsistency of with and without semicolons)
Use switch case instead of if/else if
Use Array.forEach() instead of for const in
Consistency between functions and arrow functions
Only try parsing Redis response if it isn't parsed already (aka. type string)

Add string key support
Removed application/json setHeader due to redundancy (express already deals with this)
Misc inconsistencies fixed
Switched from node-redis to ioredis (probably better performance, lower size)
lock dependencies

@JeDaYoshi I had made the mistake of blindly merging this because I had assumed it was tested and mainly formatting changes, however I now get an error when accessing a hash:
redis-exposer_1  | TypeError: redisResp.forEach is not a function
redis-exposer_1  |     at /app/index.js:52:17
redis-exposer_1  |     at processTicksAndRejections (node:internal/process/task_queues:96:5)
redis-exposer_1  | Listening on port 3000
redis-exposer_1  | Connected to Redis!
redis-exposer_1  | { secret: 'YZrrVoXaXS7bzeCxcnAS3dtmqSaZ9jYP' }
redis-exposer_1  | hash
redis-exposer_1  | /app/index.js:52
redis-exposer_1  |       redisResp.forEach((value, index) => {
redis-exposer_1  |                 ^
redis-exposer_1  |
redis-exposer_1  | TypeError: redisResp.forEach is not a function
redis-exposer_1  |     at /app/index.js:52:17
redis-exposer_1  |     at processTicksAndRejections (node:internal/process/task_queues:96:5)

This kind of situation is sort of testament to why I dislike accepting major formatting/best practises PRs for my personal slapdash code, because I'm not familiar enough with the new code to immediately resolve this. Some of the contents were very welcome though, like freezing versions.
But it was absolutely on me for not testing before merging the PR. 😄
I have reverted the PR for now. Please open a new one if you get it working. Remember to test all the parsing cases covered in the README if you do.


TableService.insertOrReplaceEntity doesn't work

I'm using TableStorage for storing server access logs in my Azure CoffeeScript tutorial. I also have a worker process that calculates access counts per URL.
To make this idempotent, I'm using a modified URL as the RowKey, and tried to use insertOrReplaceEntity. That always failed so I had to rewrite my code as:
countRequests url, (total) ->
  key = "url-#{url.replace('/', '-')}"
  totalEntry =
    total: total
    RowKey: key
    PartitionKey: 'totals1'
  table.insertEntity 'requestTotal', totalEntry, (error) ->
    return unless error
    table.updateEntity 'requestTotal', totalEntry, (error) ->
      console.log "Failed to update request count for #{url} to #{total}", error if error

Hi Bergie,
Could you give me more detail about the issue ? The method does work, but you're probably hitting some limit with it. Are you sure the values you tried for RowKey / Partition key were unique and valid ?

Also, what error did you get ?

Sorry, I don't have access to a Windows computer anymore, so I can't get the error to you. But basically: with the code above (URL being /), using insertOrReplaceEntity failed always, while the combo of insertEntity and updateEntity worked reliably.

So... if url is '/' the resulting RowKey would be "url--" i assume. I just tried:
  var entity = {
    total: 1,
    RowKey: 'url--',
    PartitionKey: 'totals1'
  };

  tableService.insertOrReplaceEntity(tableName, entity, function (error2) {

and it worked fine...

Btw, as a side note, the libs should work just as well on a non-win machine. :)
If you get further details about this, with error information please reactivate the bug. I'll investigate a bit further but don't see anything obvious from your description... :-(

The issue came with the Azure emulator, with azure installed from NPM, if that affects this.


Invalid COM object for StudioRMPro

Hi,
I'm trying to set up the dmstudio module with Studio RM Pro (v1.11.300). The COM id appears to have changed (to "Datamine.StudioRMPro.Application") so I changed this in initialize.py:
...
# no version given, will try to find a valid version
        try:
            oScript = _scriptinit("Datamine.StudioRMPro.Application")
        except:
            try:
...

However, this results in an AssertionError on import:
AssertionError: No valid Studio version is active
I tried investigating the problem by running the underlying win32com.client.Dispatch command, which returns the following error:
----> 1 client.Dispatch("Datamine.StudioRMPro.Application")

File ~\anaconda3\envs\dmstudio\lib\site-packages\win32com\client\__init__.py:117, in Dispatch(dispatch, userName, resultCLSID, typeinfo, UnicodeToString, clsctx)
    115 """Creates a Dispatch based COM object."""
    116 assert UnicodeToString is None, "this is deprecated and will go away"
--> 117 dispatch, userName = dynamic._GetGoodDispatchAndUserName(dispatch, userName, clsctx)
    118 return __WrapDispatch(dispatch, userName, resultCLSID, typeinfo, clsctx=clsctx)

File ~\anaconda3\envs\dmstudio\lib\site-packages\win32com\client\dynamic.py:106, in _GetGoodDispatchAndUserName(IDispatch, userName, clsctx)
    103     ## ??? else userName remains None ???
    104 else:
    105     userName = str(userName)
--> 106 return (_GetGoodDispatch(IDispatch, clsctx), userName)

File ~\anaconda3\envs\dmstudio\lib\site-packages\win32com\client\dynamic.py:88, in _GetGoodDispatch(IDispatch, clsctx)
     86         IDispatch = pythoncom.connect(IDispatch)
     87     except pythoncom.ole_error:
---> 88         IDispatch = pythoncom.CoCreateInstance(
     89             IDispatch, None, clsctx, pythoncom.IID_IDispatch
     90         )
     91 else:
     92     # may already be a wrapped class.
     93     IDispatch = getattr(IDispatch, "_oleobj_", IDispatch)

com_error: (-2147024773, 'The filename, directory name, or volume label syntax is incorrect.', None, None)

Has anyone tried using the package with StudioRMPro and found a solution to this? Could it be related to the fact that RMPro is 64 bit?
Cheers

@seanhoran I contacted APAC support but they were not much help and referred me back to this page when I asked about the Python API... Through recording a JScript from the GUI I found out that JScript calls a COM object called "StudioCommon.ScriptHelper" to create an ActiveX object. e.g.:
var oDmApp= null;
var oScript = null;
function AutoConnect()
{
   try {
      oScript = new ActiveXObject("StudioCommon.ScriptHelper");
      oScript.initialize(window);
      oDmApp = oScript.getApplication();
      if (oDmApp == null || oDmApp.ActiveProject == null)    //Attempt to Use the Active Datamine Session
      {
         alert("There are no active projects open.\n Please open a project before continuing.");
         window.close();                                                     // Closes the script window
	 return false;
      }
      else
      {
         document.getElementById("logo").src = oDmApp.Options.HtmlFolder + "\\images\\Datamine_rgb_small.png";
	 return true;
      }
   }
   catch(e) {
      alert("Failed\nReason: " + e.description);
      if ( oDmApp) oDmApp.Quit(); // release the session to close it down
   }
   return false;
}
function btnExecute_onclick()

I have not worked with previous versions of studio so I'm not sure if this is the 'new' way to call the API for any programming language or if this has always been the JScript API. I'm pretty new to COM or ActiveX programming so was hoping someone here had bumped into the same problem. I can connect to StudioCommon.ScriptHelper using win32com.client.Dispatch and I tried basically following the same calls that JScript calls from CMD but that returns an error:
In [3]: import win32com.client as client
In [4]: c = client.Dispatch("StudioCommon.ScriptHelper")
In [5]: c.initialize("Window")
In [6]: c.getApplication()

@mathijsvdven Yeah the scripthelper is a routine in itself to initialize the underlying COM object. Its not going to work. Some other datamine users helped me define the COM objects - have no idea where they found it.

Right, I thought as much. Running the makepy.py script from the win32com package provides a list of COM objects with Type Libraries.

I tried a couple of those . "Datamine Studio RM 2.0 Type Library (1.0)" looks promising but fails to create a static proxy:
(dmstudio) ...\>python "...\envs\dmstudio\Lib\site-packages\win32com\client\makepy.py"
Generating to ...\AppData\Local\Temp\gen_py\3.10\28B3671B-894B-48F5-A773-ED04F71E75FEx0x1x0.py
Building definitions from type library...
Traceback (most recent call last):
  File "...\envs\dmstudio\Lib\site-packages\win32com\client\makepy.py", line 452, in <module>
    rc = main()
  File "...\envs\dmstudio\Lib\site-packages\win32com\client\makepy.py", line 439, in main
    GenerateFromTypeLibSpec(
  File "...\envs\dmstudio\Lib\site-packages\win32com\client\makepy.py", line 326, in GenerateFromTypeLibSpec
    gen.generate(fileUse, bForDemand)
  File "...\envs\dmstudio\lib\site-packages\win32com\client\genpy.py", line 1090, in generate
    self.do_generate()
  File "...\envs\dmstudio\lib\site-packages\win32com\client\genpy.py", line 1165, in do_generate
    oleItems, enumItems, recordItems, vtableItems = self.BuildOleItemsFromType()
  File "...\envs\dmstudio\lib\site-packages\win32com\client\genpy.py", line 1006, in BuildOleItemsFromType
    for type_info_tuple in self.CollectOleItemInfosFromType():
  File "...\envs\dmstudio\lib\site-packages\win32com\client\genpy.py", line 908, in CollectOleItemInfosFromType
    attr = info.GetTypeAttr()
pywintypes.com_error: (-2147312566, 'Error loading type library/DLL.', None, None)

Following up on this, I heard back from Datamine and it turns out there was an issue with the COM registration for RM Pro. They have sent me a registry fix that enables COM integration for Pro. This bug should be remedied in future releases. The fix depends on your Studio installation path so for anyone running into the issue prior to the next release, it is best to contact Support. I'll make a pull request that includes the RMPro ProgID in the initialize module.