default TEMPLATE_PATH error

spath = os.path.abspath(spath) + os.sep
need modify to:  spath = os.path.abspath(spath)
fname = os.path.abspath(os.path.join(spath, name))

Please describe why this is an error. The + os.path seems to have no effect, but it also does not cause wrong behavior.
Pull requests welcomed.

I can confirm. Some windows machines get confused with the '\\' at the end of the path.
I worked around the issue by inserting the the "./views" (without last slash) folder at the beginning of the bottle.TEMPLATE_PATH variable in order to make it find the templates.

I can confirm. Some windows machines get confused with the '\' at the end of the path.

Ahh interesting! The os.pth.join does not remove duplicate separators then?

It is difficult to reproduce. In most of windows computers I have seen it works fine, but for some reason I just saw it not working on one: Windows 10, fresh install from Python 3.7.2 and latest bottle from pip.

os.path.join returns the same output with or without a leading slashes, but I can only test this on Linux.
Can someone please run this on windows 10?
>>> for p1 in ("/foo", "/foo"+os.sep):
...   for p2 in ("bar", "./bar", "."+os.sep+"bar"):
...     print(p1, p2, os.path.join(p1, p2))
...
('/foo', 'bar', '/foo/bar')
('/foo', './bar', '/foo/./bar')
('/foo', './bar', '/foo/./bar')
('/foo/', 'bar', '/foo/bar')
('/foo/', './bar', '/foo/./bar')
('/foo/', './bar', '/foo/./bar')

On 5/28/2019 6:07 AM, Marcel Hellkamp wrote:

|os.path.join| returns the same output with or without a leading
slashes, but I can only test this on Linux.
Can someone please run this on windows 10?

for  p1in  ("/foo","/foo"+os.sep):
...    for  p2in  ("bar","./bar","."+os.sep+"bar"):
...      print(p1, p2, os.path.join(p1, p2))
...
('/foo','bar','/foo/bar')
('/foo','./bar','/foo/./bar')
('/foo','./bar','/foo/./bar')
('/foo/','bar','/foo/bar')
('/foo/','./bar','/foo/./bar')
('/foo/','./bar','/foo/./bar')

import os
for p1 in ("/foo", "/foo"+os.sep):
...     for p2 in ("bar", "./bar", "."+os.sep+"bar"):
...         print(p1, p2, os.path.join(p1, p2))
...
/foo bar /foo\bar
/foo ./bar /foo./bar
/foo .\bar /foo.\bar
/foo\ bar /foo\bar
/foo\ ./bar /foo./bar
/foo\ .\bar /foo.\bar


Poor rendering of Chinese characters in chat interface

I've noticed an issue with the rendering of Chinese characters in the chat interface. When Chinese text is generated, it doesn't appear visible on the frontend, despite being present in the backend response.
For example, when I input Chinese text, the response is generated but not displayed:
==========================================================================
==========================================================================
Settings:
contextLength: 1024
maxTokens: 512
temperature: 1
topP: 1
presencePenalty: 0
frequencyPenalty: 0
model: deepseek-chat
raw: true
stop:
,
,/src/,#- coding: utf-8,```
log: undefined
############################################
验的误解和误用，正像我们时常误解和误用世界上许多其它东西一样。
因此（）。
A. 我们应该取消测验
B. 使用测验能使我们解决生活中的一切难题
C. 还应不断地完善测验并引导人们正确地认识和使用测验
D. 测验是可有可无的东西
让我们来一步步==========================================================================
==========================================================================
Completion:
推理这个问题。

The frontend display looks like this:

However, when I input text in English, it appears immediately and correctly:
Criticism and even attacks against the use of tests are abundant. Sometimes, their use can even lead to unintended adverse consequences. The reasons for this situation lie not only in the imperfection of tests themselves, much like many other things in the world are imperfect, but more so in people's misunderstandings and misuse of tests, similar to how we often misunderstand and misuse many other things in the world.
Therefore, ().
A. we should abolish tests
B. using tests can solve all problems in our lives
C. tests should be continually improved and people should be guided to understand and use them correctly
D. tests are dispensable items
Let us ==========================================================================
==========================================================================
Completion:
analyze the options one by one:

The English text displays correctly:

Is it possible to fix this issue? Are there any other problems I might have overlooked that could be causing this?
Any assistance in resolving this would be greatly appreciated. Thank you!

I've noticed an issue with the rendering of Chinese characters in the chat interface. When Chinese text is generated, it doesn't appear visible on the frontend, despite being present in the backend response.
For example, when I input Chinese text, the response is generated but not displayed:
==========================================================================
==========================================================================
Settings:
contextLength: 1024
maxTokens: 512
temperature: 1
topP: 1
presencePenalty: 0
frequencyPenalty: 0
model: deepseek-chat
raw: true
stop:
,
,/src/,#- coding: utf-8,```
log: undefined
############################################
验的误解和误用，正像我们时常误解和误用世界上许多其它东西一样。
因此（）。
A. 我们应该取消测验
B. 使用测验能使我们解决生活中的一切难题
C. 还应不断地完善测验并引导人们正确地认识和使用测验
D. 测验是可有可无的东西
让我们来一步步==========================================================================
==========================================================================
Completion:
推理这个问题。

The frontend display looks like this:

However, when I input text in English, it appears immediately and correctly:
Criticism and even attacks against the use of tests are abundant. Sometimes, their use can even lead to unintended adverse consequences. The reasons for this situation lie not only in the imperfection of tests themselves, much like many other things in the world are imperfect, but more so in people's misunderstandings and misuse of tests, similar to how we often misunderstand and misuse many other things in the world.
Therefore, ().
A. we should abolish tests
B. using tests can solve all problems in our lives
C. tests should be continually improved and people should be guided to understand and use them correctly
D. tests are dispensable items
Let us ==========================================================================
==========================================================================
Completion:
analyze the options one by one:

The English text displays correctly:

Is it possible to fix this issue? Are there any other problems I might have overlooked that could be causing this?
Any assistance in resolving this would be greatly appreciated. Thank you!

It seems like when I wrote in Chinese, the appearance of autocompletion seems to be totally random. But in English there is a clear difference.  It just pops out so much easier.

Upon reviewing the logs, I discovered that the completions were indeed generated, so my question is: How can I ensure these generated responses are properly displayed on the frontend?

Here is my tabAutocomplete setting:
  "tabAutocompleteModel": [
    {
      "title": "DeepSeek-Tabcomplete",
      "model": "deepseek-chat",
      "apiKey": "sk-xxxxxx",
      "contextLength": 1024,
      "apiBase": "https://api.deepseek.com/beta",
      "completionOptions": {
        "maxTokens": 512,
        "temperature": 1.0,
        "topP": 1,
        "presencePenalty": 0,
        "frequencyPenalty": 0
      },
      "provider": "openai"
    },
    {
      "title": "GPT-3.5-Turbo",
      "provider": "openai",
      "model": "gpt-3.5-turbo",
      "apiKey": "sk-xxxxxx",
      "apiBase": "https://www.gptapi.us/v1",
      "useLegacyCompletionsEndpoint": false
    }
  ],
  "tabAutocompleteOptions": {
    "disable": false,
    "useCopyBuffer": false,
    "useSuffix": false,
    "maxPromptTokens": 512,
    "prefixPercentage": 0.85,
    "maxSuffixPercentage": 0.25,
    "debounceDelay": 350,
    "multilineCompletions": "always",
    "slidingWindowPrefixPercentage": 0.75,
    "slidingWindowSize": 350,
    "maxSnippetPercentage": 0.3,
    "recentlyEditedSimilarityThreshold": 0.3,
    "useCache": true,
    "onlyMyCode": true,
    "useOtherFiles": false,
    "useRecentlyEdited": false,
    "recentLinePrefixMatchMinLength": 7,
    "disableInFiles": ["*.csv", "*.json"],
    "useFileSuffix": false,
    "template": "Continue the following text, making it flow naturally. Provide only your continuation content, without adding any explanations, formatting, or extra outputs.  The auto-completion of Chinese characters may or may not appear on the code editing page, but the backend indicates that the final result has been generated.


How can I handle a deploy for a pull request?

Hi guys and thank you for all the goodness, I really enjoy using Caprover!
I was wondering if and how would it be possible to deploy every time there's a new pull request to a testing/staging environment that corresponds to a url like name-of-the-branch--caproverappname.myserver.com
Ideally I would need to be able to destroy the new created env once the PR gets merged or closed, but this is not a priority.
Is this something I can achieve with this action?

Hi @phaberest  - unfortunately this is not quite possible using the built in functionality. CapRover doesn't support automatic creation of apps on pull request. It's something that technically can be done via API and lots of scripting, but it's not a built in functionality.


Delete Sonar

The task is deprecated in this repo (moved). I'm not deleting from M112, so due to task-major locking it will still ship. Master doesn't have any changes from 112.


NamedQuery error when use PostgreSQL type cast ::int

When I use NamedQuery for PostgreSQL and use type cast ::int in query:
SELECT (d.categories->>0)::int AS category_id
FROM some_table d
WHERE id =:id

I get error:
error="pq: syntax error at or near \":\""

if I use CAST
SELECT CAST(d.categories->>0 AS integer) AS category_id
FROM some_table d
WHERE id =:id

query works fine

Just spooted this but I'm guessing it's because you're using a NamedStmt which requires you to double escape all :. Your generated query will only be providing one : to PostgreSQL and then failing.
Try changing to:
SELECT (d.categories->>0)::::int AS category_id

@kisamoto Thanks. Is this way to double-escape : documented?

@powerman I didn't find it in the docs, instead I noticed it searching for a similar problem that led me to #91

@kisamoto
Try changing to:
SELECT (d.categories->>0)::::int AS category_id


[Bug] Saving Python files trigger flake8 which is not installed

Is there an existing issue for this?

[X] I have searched the existing issues

What product(s) are you seeing the problem on?
OpenChallenges
Current behavior
Each time I'm saving a Python file of the OC API client, I get a popup in VS Code that says that there is an error when running flake8.

2023-10-20 20:53:44.439 [info] Linting with flake8 failed.
2023-10-20 20:53:44.439 [info] Error: Module 'flake8' not installed.

Expected behavior
I believe that we want to lint file with black so black should be used and not flake8.
The goal of this ticket is to:

prevent flake8 from being executed on save
format file on save with black

Anything else?
No response
Commit ID
No response
Are you developing inside the dev container?

[X] I am using the dev container

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The bundled black is only used if there is no installed version of black found in the selected python environment.

Source: https://marketplace.visualstudio.com/items?itemName=ms-python.black-formatter


Movingpandas for non-geo data?

Hi there,
I am trying to plot trajectories (of mice) using python and I found this great library (watched a couple of tutorials on youtube). I am wondering if I could use it on a different reference system (a mouse home cage) other than geo maps since I would like to do operations that this library already does, segment analysis, operations with ROIs, speed, interpolation, trajectory aggregation, etc.
I apologize if this question is out of place, I have no experience on GIS data.
THanks!
Edgar

Hi Edgar, the use case you describe is something I'd like to support with MovingPandas. So far, I haven't done extensive testing on the current limitations and potentially necessary improvements. Would you be able to share a mouse dataset and a few analysis examples that are relevant to your research? That would be extremely helpful to evaluate the suitability of MovingPandas and to develop a corresponding demo showcase.

Great! I am happy to share data and analysis. This would be a fantastic tool. I am also happy to contribute into the development.

You can use any file sharing you want to provide the most sample dataset. Eventually, I'd like to include it into the MovingPandas examples repo.

Closing for lack of feedback.


Update README.md

Update sample bindings to match. cmd+ctrl+f clashes with Chrome's full screen mode

I don't really see the need for this. Sample binds are just what I am personally using and is provided as a starting point. In my opinion, these should be looked at closely by any user, as it is probably the most personal part of a tiling setup.


release fixes

Codecov Report
Base: 87.19% // Head: 85.23% // Decreases project coverage by -1.96% :warning:

Coverage data is based on head (67316d9) compared to base (f28d20b).
Patch coverage: 69.03% of modified lines in pull request are covered.

:exclamation: Current head 67316d9 differs from pull request most recent head 8f55c01. Consider uploading reports for the commit 8f55c01 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #164      +/-   ##
==========================================
- Coverage   87.19%   85.23%   -1.96%
==========================================
  Files          82       82
  Lines        1382     1490     +108
  Branches      139      171      +32
==========================================
+ Hits         1205     1270      +65
- Misses        175      210      +35
- Partials        2       10       +8

Impacted Files
Coverage Δ

src/resources/bucket.ts
73.68% <0.00%> (-8.67%)
:arrow_down:

src/resources/collection.ts
76.74% <0.00%> (-7.88%)
:arrow_down:

src/resources/queue.ts
78.94% <0.00%> (-9.29%)
:arrow_down:

src/resources/secret.ts
77.77% <0.00%> (-9.73%)
:arrow_down:

src/resources/topic.ts
86.66% <0.00%> (-8.46%)
:arrow_down:

src/faas/v0/start.ts
32.50% <25.00%> (-1.13%)
:arrow_down:

src/faas/v0/context.ts
76.22% <50.00%> (ø)

src/api/storage/v0/storage.ts
96.66% <75.00%> (-1.07%)
:arrow_down:

src/resources/api.ts
79.61% <80.00%> (-3.88%)
:arrow_down:

src/resources/common.ts
96.29% <91.66%> (-1.38%)
:arrow_down:

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


pull request for e2e test at 01/22/2017 11:45:16

:white_check_mark: Validation status: passed
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.


Self-hosted Math

If you want a self-hosted MathJax instead of downloading the script everytime, why don't you try MathML? MathML has much cleaner syntax (depends on how you define 'clean'), and is included in the HTML5 standard. Though it's only supported by Firefox and Safari for now, Chrome is working hard on it. I expect Chrome to support it with in a year.

MathML will be a great solution once it is widely supported. Chrome once had MathML support, then it was removed for some reason. I'm glad that they're adding MathML support again.
Note that when I made Unidok, there was no indication that Chrome even wants to support MathML.


Sqlite json support failed after upgrade to laravel 5.6.26

Laravel Version: 5.6.26
PHP Version: 7.1.18
Database Driver & Version: Mysql5.7 / sqlite3

Description:
I just upgraded from 5.6.23 to 5.6.26 and some functionalities which work with json fields throw error on tests. On mysql all tests pass but with sqlite database i get this error:

This database engine does not support JSON operations

/vendor/laravel/framework/src/Illuminate/Database/Query/Grammars/Grammar.php:930)

Steps To Reproduce:
Use a json field on migration
try to fill it on controller
test it

Please post the controller code where you fill the JSON field.


Limit number of consul agent connections in consul_sd

Hello,
We have a pretty large consul catalog. In one of our bigger DCs, the Prometheus poller is opening 1000+ connections to the local consul agent when doing consul_sd.
I can increase this value with https://www.consul.io/docs/agent/options.html#http_max_conns_per_client but I'm wondering if it makes sense to be able to limit this on Prometheus' end.

This is a limitation of how Consul works, we need a connection per service to do watches efficiently and correctly. You'll have to adjust this on the Consul end.

Thanks.


Seperate paragraph into sntences

Very nice library.
I'm looking for a way to use this to seperate a paragraph into sentences.
How would it be possible?
Thank you

Thanks,

Take a look at node-sentence-tools, which uses parse-english to focus mainly on sentences;
If you’re going your own way, take a look at nlcst-to-string, which stringifies nodes back into english;
Also, maybe just try to look at the output generated by parse-english, it’s pretty straightforward :)

Hope that helps!


Fix test to fail on incorrect input

In 'Waypoint: Add Font Awesome Icons to our Buttons' challenge changed a test to check whether  element is within Like button (did it the same way as it is done in 'Waypoint: Add Font Awesome Icons to all of our Buttons' challenge).
closes #4981

Don't you need to do the prior test as well as the new test?  It looks like you're testing to make sure it's in a button, but now it could be any button, not just the like button.

I'm checking the button of a class .btn-primary, which is our like button's class.

Yes, but the example was someone creating a whole new button.  If they could do that, they could create a copy of the button's classes as well.
Maybe I'm being over sensitive.  @ltegman, @bugron ?

Agreed with @SaintPeter. We need both of these tests. You can combine them: $(\"i.fa-thumbs-up\").parent().text().match(/Like/gi) && $(\".btn-primary > i\").hasClass(\"fa fa-thumbs-up\") or just left first test case unchanged and add second one with $(\".btn-primary > i\").hasClass(\"fa fa-thumbs-up\"). Being more precise is better.

@LenaBarinova OK, but now your second test check for the Link text too. Remove $(\"i.fa-thumbs-up\").parent().text().match(/Like/gi) && from your second test, then run these commands:
git add .
git commit --amend

and then force push your branch to your fork: git push -f YOUR_BRANCH_NAME.

I've appended the test, didn't create new one, since we are checking the same logical thing - fa-thumbs-up icon should be located within the Like button.

@LenaBarinova oh, yes, sorry, my fault.

I've verified that this works. After you squash your commits into one I'm ready to merge your PR.

@bugron all done!

@bugron Thanks for the help! It was first commit, I hope further commits will go more smoothly :)


import/first and reexports

Currently, import/first seems to require that any import comes before any export, even if the export is an export..from. Reordering them, in this case, could be a potential logic error.
Though, arguably, if the module is capable of exporting, it should also be made side-effect free...
Also related is that import/first does not allow mixing import with export {}, and separating them actually hurts readability.
Consider the following:
// `export * as comment from './comment'` but that is not standard syntax
import * as comment from './comment'
export { comment }

import * as members from './members'
export { members }

The rule will complain about the second import, but moving so all the imports are grouped would actually make it harder to tell they are being reexported.

Why would that make it harder to tell?
You'd read the export { members, comment }, and then having already read the two imports, you'd know they were being re-exported.
Why is this situation any different from const foo = 3; export { foo }; const bar = 4; export { bar } (which should be const foo = 3; const bar = 4; export { foo, bar })?

This is a small snippet of a larger file with many reexports.
Overall, I don't see any reason, anywhere, ever, for considering export {} as code. It should never trigger use before define or other similar lint warnings. If you want to consolidate your exports, then an export-specific rule should be used.

Of course an export is code, as is an import - exports are conceptually like a return.
It seems like the sole purpose of the rule isn't something you want enforced; I'd suggest disabling the rule in that case.

Reordering them, in this case, could be a potential logic error.

Regrouping your import/export pairs such that imports are first, and then exports, can't possibly change the meaning of the code (assuming that the imports are all in the same order), so I'm not sure what you mean here.

@ljharb export { foo } from 'bar'

I've also bumped into this while linking packages generated by rollup for local testing purposes (yes - I could change rule settings to ignore those directories, but that's not the point). I agree with @Jessidhia that because reexports are imports they should just be allowed there. From my POV the purpose of this rule is to avoid confusion around this:
console.log('second')
import './i-will-log-first'

Reexports on the top won't confuse people like the given snippet can.
I've created a quick PR for this https://github.com/benmosher/eslint-plugin-import/pull/1522 , merge it or close it I guess, your call - just wanted to bring up my 2 cents into this.


Commit to private docker registry: connection refused

Description
When buildah push an error occurs in the end, though the image has been pushed to the private registry. Why does it happen? Is anything wrong? No error output from the docker registry.

The certificate for the registry used is not self-signed!

Steps to reproduce the issue:

buildah push --creds=username:passwd $name docker://hub.xxxxx.com:5000/$name

Describe the results you received:
I didn't expect any connection refused.
Describe the results you expected:
No error.
Output of rpm -q buildah or apt list buildah:
buildah-1.0-1.git1ab80bc.fc28.x86_64
Complete!
Getting image source signatures
Copying blob sha256:199dbc3127dde5e6a0e6b30a3bdd008a6ea79ae9b44dbdf8669655be0665f927
 47.78 MiB / 47.78 MiB [====================================================] 2s
Copying config sha256:3d6645f9adcd1e30cb61a96d12a257400e69c0a9e5d47d99dfa960d3ba60067c
 1.04 KiB / 1.04 KiB [======================================================] 0s
Writing manifest to image destination
Storing signatures
3d6645f9adcd1e30cb61a96d12a257400e69c0a9e5d47d99dfa960d3ba60067c
Getting image source signatures
Get https://hub.xxxxx.com:5000/v2/: dial tcp vv.xx.yy.zz:5000: connect: connection refused

Output of buildah version:
Version:       1.0
Go Version:    go1.10.1
Image Spec:    1.0.0
Runtime Spec:  1.0.0
Git Commit:    1ab80bc
Built:         Mon May  7 16:01:02 2018
OS/Arch:       linux/amd64

Output of cat /etc/*release:
Fedora release 28 (Twenty Eight)
NAME=Fedora
VERSION="28 (Workstation Edition)"
ID=fedora
VERSION_ID=28
PLATFORM_ID="platform:f28"
PRETTY_NAME="Fedora 28 (Workstation Edition)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:28"
HOME_URL="https://fedoraproject.org/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=28
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=28
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation
Fedora release 28 (Twenty Eight)
Fedora release 28 (Twenty Eight)

Output of uname -a:
Linux localhost.localdomain 4.16.11-300.fc28.x86_64 #1 SMP Tue May 22 18:29:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Output of cat /etc/containers/storage.conf:
# storage.conf is the configuration file for all tools
# that share the containers/storage libraries
# See man 5 containers-storage.conf for more information

# The "container storage" table contains all of the server options.
[storage]

# Default Storage Driver
driver = "overlay"

# Temporary storage location
runroot = "/var/run/containers/storage"

# Primary Read/Write location of container storage
graphroot = "/var/lib/containers/storage"

[storage.options]
# AdditionalImageStores is used to pass paths to additional Read/Only image stores
# Must be comma separated list.
additionalimagestores = [
]

# Size is used to set a maximum size of the container image.  Only supported by
# certain container storage drivers.
size = ""

# OverrideKernelCheck tells the driver to ignore kernel checks based on kernel version
override_kernel_check = "true"

@stefanand Thanks for the problem report.  Can you share the command(s) that you you used to setup and run the registry?  Are their any related errors in journalctl?

  The only thing that jumps out at me is the --restart-always param.  I don't think I've used that myself in my testing yet.  If you've a spare moment and could try removing that and see if you still have the problem, that would be an interesting data point to have.  If not, no worries, I'll try to run it myself in the near future to see if I can replicate.

@stefanand, you can push to this same registry using docker as the client? it's only when buildah is a client that it's an issue?
Is it a self signed cert running on the repository?

additionally, it worked before the last upgrade...no error message at that time!

@pixdrift I don't seem to get the error when using Docker as a client. Only when buildah is used as a client.
No self-cert! As you can see it is a LetsEncrypt certificate. It worked well before the update of buildah.

@pixdrift I don't seem to get the error when using Docker as a client. Only when buildah is used as a client.
No self-cert! As you can see it is a LetsEncrypt certificate. It worked well before the update of buildah.

@stefanand Do you recall by chance which version of Buildah you were on prior?  v0.16 perhaps?

Thanks for the responses @stefanand
+1 to @TomSweeneyRedHat's suggestion here, if you can get the buildah version from a previous working version, it would be an excellent help.

@mtrmac PTAL

Current version:
Name        : buildah
Version     : 1.0
Release     : 1.git1ab80bc.fc28
Architecture: x86_64
Previous version:
buildah-0.16-1.git82529cd.fc28.x86_64

Thanks for the older version @stefanand !

Wait and I will have to check one more thing and see if it leads me to a clue....before any further work!

This looks as if the registry server was crashing inside the container.
If you reproduce this without --restart=always, and after you get the
Get https://hub.xxxxx.com:5000/v2/: dial tcp vv.xx.yy.zz:5000: connect: connection refused

can you connect to the registry again (with any client) and use it?
If not, can you collect the logs of the registry server, both as it is serving requests successfully and most importantly when it stops to do so?

@stefanand as I've not been able to reproduce this and we've not heard anything further for quite a while, I'm going to close this issue.  Please reopen or create a new issue as you see appropriate if you continue to have problems with this.


Fix the empty last line may causes the session to exit directly

Why are the changes needed?
If the last line of the file is a blank line, there may be a cmd whose content is empty but the length is not 0 after split by ";". When running to this cmd, it will return false, causing the session to exit directly.
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible
vim test.sql and write :

then start beeline and source this file successfully and session won't exit：

[x] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #4575 (ff3fcb1) into master (824aba6) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #4575      +/-   ##
============================================
- Coverage     53.28%   53.27%   -0.01%
  Complexity       13       13
============================================
  Files           573      573
  Lines         31501    31502       +1
  Branches       4239     4239
============================================
- Hits          16786    16784       -2
- Misses        13135    13137       +2
- Partials       1580     1581       +1

Impacted Files
Coverage Δ

...n/java/org/apache/hive/beeline/KyuubiCommands.java
0.00% <0.00%> (ø)

... and 4 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks，merged to master and 1.7


Peer Review

:) Feel free to share your thoughts here, thanks!

Good work @ChesterAiGo!
Some thoughts:

The top Car Market Share % is a little bit visually overwhelming. I would consider condensing all of the smaller brands into an 'other' category (i.e. brands with less with 1%) as this would significantly reduce the number of labels. The smallest sections are almost impossible to differentiate as is. Condensing would also allow you to scale this widget slightly bigger (since the labels wouldn't extend down as far), which would further increase readability

For the secondary pie chart (top 10 models), the legend is ALMOST big enough to fully display without scrolling. Could this feature be upsized slightly to show the entire legend?

It is not immediately obvious what the bottom scale bar does for the bar chart widget without fiddling with it. Maybe add a label that says "number of models displayed"?

Good job!

Very interesting to play around with and compare the different manufacturers and models.
I can see this being useful for vehicle purchases in the future. Could add an option for direct comparisons between models for future development!

Awesome app! I really like how you can interactively choose which brands are/aren't included in the pie chart. A few suggestions:

You could separate the two charts onto separate pages, and then make the pie chart fill its entire page. This way the pie chart would be bigger and one could see more of the smaller slices.
You could add text labels and/or logos to the pie chart slices (for slices that are large enough, e.g. >5%).


add minijinja_contrib dependency

add minijinja_contrib dependency to support datetime filters.

Please also enable these new functions for the injection API over here: https://github.com/KumoCorp/kumomta/blob/ffc15f2f74e358c68701e7a947a8f95ca8033e70/crates/kumod/src/http_server/inject_v1.rs#L237
Thanks!

Thanks!


Image issue on IE

I tried rendering the sliders on IE11 and the images aren't showing, but it shows on emulator IE10 and other browsers like Chrome. The CSS is pretty much the same as the demo file.

{{lpurchase.name}}

{{ lpurchase.purchasedate }}

Please leave an url of your page that I can have a look.

Hi thanks, url is not up yet just developing it locally. the code above is basically what I have in my template nothing else.

Strange, I replicated my issue on plnkr but its working fine. Not sure what's wrong with the slider in my angular2 dev project. I exactly have the same code on my plnkr and dev project.
https://plnkr.co/edit/AEBpDCZgZBIv1AnMvgco?p=preview

here's a screenshot of the source code on IE11

Found the issue now, looks like it doesn't like position: absolute on the img element.

That's great!


Ubuntu Version

Standard support for Ubuntu 16.04 LTS ends in April 2021.
I'd like to

exclude Ubuntu 16.04 from the Build and Test Suite workflows.
change the Ubuntu version of the Dockerfile from 16.04 to 20.04.

I see that there are already some problems with ubuntu 16.04

I see that there are already some problems with ubuntu 16.04

@tdrozdovsky You're right. I noticed problems due to your PR #287 , #288.
Could you revise code in terms of workflows?
Regarding Dockerfile change, I'd like to give a chance for a new contributor.

@tdrozdovsky You're right. I noticed problems due to your PR #287 , #288.
Could you revise code in terms of workflows?

Yes of course I will do it

Regarding Dockerfile change, I'd like to give a chance for a new contributor.

@t25kim  What do you have in mind?

Regarding Dockerfile change, I'd like to give a chance for a new contributor.

@t25kim What do you have in mind?

I'm going to have a toy project with some university students and would like to guide them how to contribute to open source through HomeEdge. I think changing the ubuntu version in Dockerfile is one of good contributing points.

While the github->Actions under Ubuntu-16.04 are working. Therefore, this issue is suspended.
In case of problems with the github->Actions under Ubuntu-16.04, the PR #290 is ready and can be applied as soon as possible

While the github->Actions under Ubuntu-16.04 are working. Therefore, this issue is suspended.
In case of problems with the github->Actions under Ubuntu-16.04, the PR #290 is ready and can be applied as soon as possible

In my opinion, no matter if workflows run or not, it would be nice to exclude the os if it ends standard support period.


Prepare more small speaker image

Now speaker icon image size is so big.

Hmm, I'm thinking we can use glide's bitmap pool but...

@konifar Just to confirm.  Are you concerning about the size of .apk file or memory usage?

@hkurokawa I am concerning about memory usage and time to load.

I see.  Thank you.
Now I feel like preparing alternative image resources might be hard for Ver 1.0. And I am wondering adding a code like below resizing the image properly can reduce memory usage (though the loading time might not be changed...) and it might be acceptable for the Ver 1.0 release.  How do you think?
            Picasso.with(imageView.getContext())
                    .load(imageUrl)
                    .resizeDimen(imageWidth, imageHeight)
                    .placeholder(R.drawable.ic_speaker_placeholder)
                    .error(R.drawable.ic_speaker_placeholder)
                    .transform(new CropCircleTransformation())
                    .into(imageView);

I feel like preparing alternative image resources might be hard for Ver 1.0.

Hmm, I see.
And your suggestion .resizeDimen(imageWidth, imageHeight) sounds good!

Great! I created another issue #89 for that solution and will keep this issue for future as the context is slightly different from the original.

I think we can close this issue. It's so tough to prepare each speaker's img again...

@hotchemi I agree with you. OK! Close it!


page_service: add peer_addr span field, and set tenant_id / timeline_id fields earlier

Before this PR, during shutdown, we'd find naked logs like this one for every active page service connection:
2023-07-05T14:13:50.791992Z  INFO shutdown request received in run_message_loop

This PR

adds a peer_addr span field to distinguish the connections in logs
sets the tenant_id / timeline_id fields earlier

I'm wondering whether I can have tenant_id and timeline_id directly on the page_service_conn_main span (empty, initially), then set them at the top of process_query?

Applied your suggestions.
Before I merge, wdyt regarding:

I'm wondering whether I can have tenant_id and timeline_id directly on the page_service_conn_main span (empty, initially), then set them at the top of process_query?

Some more context. With this patch, the log lines look like this:
2023-07-05T17:06:55.632061Z  INFO page_service_conn_main{peer_addr=<IP_ADDRESS>:52706}:process_query{tenant_id=95144dc32ceea9a11bb86f4d0c3ab092 timeline_id=5359ccaff96843b105dca762b63dfc5b}:handle_basebackup_request{lsn=None prev_lsn=None full_backup=false}: taking basebackup lsn=0/16960E8, prev_lsn=0/1696070 (full_backup=false)

I'd prefer the tenant and timeline id were in the page_service_conn_main span:
2023-07-05T17:06:55.632061Z  INFO page_service_conn_main{peer_addr=<IP_ADDRESS>:52706 tenant_id=95144dc32ceea9a11bb86f4d0c3ab092 timeline_id=5359ccaff96843b105dca762b63dfc5b}:process_query:handle_basebackup_request{lsn=None prev_lsn=None full_backup=false}: taking basebackup lsn=0/16960E8, prev_lsn=0/1696070 (full_backup=false)

We could even leave out the process_query span
2023-07-05T17:06:55.632061Z  INFO page_service_conn_main{peer_addr=<IP_ADDRESS>:52706 tenant_id=95144dc32ceea9a11bb86f4d0c3ab092 timeline_id=5359ccaff96843b105dca762b63dfc5b}:process_query:handle_basebackup_request{lsn=None prev_lsn=None full_backup=false}: taking basebackup lsn=0/16960E8, prev_lsn=0/1696070 (full_backup=false)

It doesn't make strict sense at the protocol level though, because, tenant and timeline id are provided per request.
Any thoughts?

No objections to:

We could even leave out the process_query span [and record tenant_id and timeline_id to the page_service_conn_main]

Should be quite trivial to do:

just remove the #[instrument(...)] around process_query
then Span::record will target the page_service_conn_main

Just need to make sure we have the debug_assert_tenant_and_timeline_ids_... (or tenant_id only) however that was in all query handlers, in case something is changed on the pg-connection-handling-in-anonymous-inner-class abstraction.

Just need to make sure we have the debug_assert_tenant_and_timeline_ids_... (or tenant_id only) however that was in all query handlers, in case something is changed on the pg-connection-handling-in-anonymous-inner-class abstraction. These seem to be already in place.

Yeah, that's what I'm worried about.
Also the debug_assert_tenant_and...(): do they still trap if there's a field, but it's the empty tracing::Value?
Gonna play with this for 10min or so to find out.

    #[test]
    #[should_panic]
    fn empty_field_defined_in_span_macro_panics() {
        let setup = setup_current_thread();

        let span = tracing::info_span!("root", tenant_id = tracing::field::Empty);
        let _guard = span.enter();
        check_fields_present([&setup.tenant_extractor]).unwrap();
    }

    #[test]
    #[should_panic]
    fn empty_field_defined_by_instrument_macro_panics() {
        let setup = setup_current_thread();

        #[tracing::instrument(skip_all, fields(tenant_id))]
        fn child_fn(setup: &Setup) {
            check_fields_present([&setup.tenant_extractor]).unwrap();
        }

        let span = tracing::info_span!("root", tenant_id = tracing::field::Empty);
        let _guard = span.enter();
        child_fn(&setup);
    }

Adding these tests, they fail (libs/utils/src/tracing_span_assert.rs).
Thinking about it a bit more, even if we detect the empty value correctly, there's no way to assert that the value is not stale.
I.e., imagine
page_service_conn_main
  process_query
    it's a basebackup request for tenant_id=A, timeline_id=B
    sets tenant_id=A, timeline_id=B
  process_query
    it's a getpage request for tenant_id=C, timeline_id=D
    we forgot the Span::record() calls for this branch
    we'll log in the name of `tenant_id=A, timeline_id=B`

What is worse:

like it is now, with peer_addr in page_service_conn_main and tenant_id and timeline_id in the process_query span, where staleness risk isn't big because each process_query gets a new empty value
having all 3 in page_service_conn_main span, but the ids may be stale if there's a bug

Hm, the current state of this PR is an improvement, and it has near-zero chance of the staleness issue outlined above.
Merging it as is.

Regarding my observations about the debug assert not triggering on tracing::value::Empty.
I'll create a follow-up issue and report there why it's not easily fixable.


Add RFC: update buffer titles in guest

Add the following document to the RFC Docs as a solution to issue #147

Following the suggestion described in atom/text-buffer#292 (comment), we decided to add a new class called Buffer-File, which acts as a "dummy" File. This addition has been locally tested and found to work exceedingly well.

Changes look great, thanks! What are the next steps, or how else may I help out in the submission of this RFC?

What are the next steps, or how else may I help out in the submission of this RFC?

@CaptainJohnyAppleSeed: I've updated the status to "Accepted" and I'll merge this pull request shortly. The next step is for you to open the atom/teletype and atom/teletype-client pull requests to implement the changes described in the RFC.
Thanks for working on this! :zap::bow:


mapper for PDF to PNG

https://github.com/kazurayam/materialstore/issues/124

done v0.1.0-SNAPSHOT


release 1.29.0

🎉

I don't want to ruin the party, but I won't be physically able to build/sign/upload this before next Wednesday.

I got your back. I can do the release on Monday.

Rebased to include https://github.com/rkt/rkt/pull/3816


Add a publishTo operator that publishes mid-stream data to a cyclops-react async Adapter

Allows Stream data to be published in flight to Queue or Topic for further processing.
e.g.
Queue<Integer> myQueue = QueueFactories.<Integer>unboundedNonBlockingQueue()
                                       .build();
ReactiveSeq.of(1,2,3,4)
           .map(i->i*2)
           .publishTo(myQueue)
           .map(i->i*100)
           .forEach(e->{});

myQueue.stream().printOut();

Should result in
2
4
6
8

Available on push / pull and FutureStreams

Released in 2.0.0-MI3


CSS Grid layout goes wrong on chess.com

Hmmmmm:

Simplified reduction:
<!doctype html>

hello

I can fix this issue, can I submit a PR here?

I can fix this issue, can I submit a PR here?

Of course, if you have a fix, please submit it along with a layout test :)


Prefixes of dependencies in package.json are missing in fresh install

Steps

Follow "Getting Started":
npx react-native init Krelly --template react-native-template-cljs-krell-storybook

Go to the new project.

Look at package.json.

Result
package.json
{
  "name": "projectname",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "ios": "react-native run-ios",
    "storybook": "start-storybook -p 6006",
    "start": "react-native start",
    "android": "react-native run-android",
    "lint": "eslint .",
    "cljs:repl": "clj -M -m krell.main -co build.edn -c -r",
    "build-storybook": "build-storybook",
    "cljs:build": "clj -M -m krell.main -co build.edn -c",
    "test": "jest"
  },
  "dependencies": {
    "module-deps": "^1.1.1",
    "react": "18.1.0",
    "react-native": "0.68.2",
    "react-native-device-info": "8.1.2",
    "react-native-tcp-socket": "5.2.0"
  },
  "devDependencies": {
    "core": "^7.12.9",
    "metro-react-native-babel-preset": "^0.67.0",
    "react": "^6.5.6",
    "addon-interactions": "^6.5.6",
    "eslint-config": "^2.0.0",
    "react-test-renderer": "17.0.2",
    "addon-essentials": "^6.5.6",
    "babel-jest": "^26.6.3",
    "dashify": "^2.0.0",
    "testing-library": "^0.0.11",
    "runtime": "^7.12.5",
    "babel-plugin-react-native-web": "^0.17.7",
    "addon-actions": "^6.5.6",
    "eslint": "^7.32.0",
    "jest": "^26.6.3",
    "react-dom": "^18.1.0",
    "react-native-web": "^0.17.7",
    "nbb": "0.5.103",
    "addon-links": "^6.5.6",
    "addon-react-native-web": "^0.0.18"
  },
  "jest": {
    "preset": "react-native"
  }
}

Question
Shouldn't "core" under "devDependencies" actually be "@babel/core", etc.?
If I try to run yarn, I get the following:
zeniten@ztn2:~/repositories/Krelly$ yarn
yarn install v1.22.4
warning package.json: "dependencies" has dependency "react" with range "18.1.0" that collides with a dependency in "devDependencies" of the same name with version "^6.5.6"
warning<EMAIL_ADDRESS>"dependencies" has dependency "react" with range "18.1.0" that collides with a dependency in "devDependencies" of the same name with version "^6.5.6"
[1/4] Resolving packages...
Couldn't find any versions for "core" that matches "^7.12.9"
? Please choose a version of "core" from this list: (Use arrow keys)
❯ 2.0.14
  2.0.13
  2.0.12
  2.0.11
  2.0.9
  2.0.8
  2.0.6
  2.0.5
  2.0.4
  2.0.2
  2.0.1
  1.0.113
  1.0.112
  1.0.111
  1.0.110
  1.0.109
  1.0.108
  1.0.107
  1.0.106
  1.0.105
  1.0.104
  1.0.103
  1.0.102
  1.0.101
  1.0.100
  1.0.99
  1.0.98
  1.0.97
  1.0.96
  1.0.95
  1.0.94
  1.0.93
  1.0.92
  1.0.91
  1.0.89
  1.0.88
(Move up and down to reveal more choices)

This seems to work as intended, @joshuamiller:
(def package-json
  (-> (readFileSync "package.json")
      str
      js/JSON.parse
      js->clj
      (update "scripts" dissoc "postinstall")
      clj->js))

@Zeniten Good catch 👍. Fixed and pushed to NPM.


add vrrp_garp_master_refresh / vrrp_garp_lower_prio_delay params

This Pull Request (PR) fixes the following issues
Fixes https://github.com/voxpupuli/puppet-keepalived/issues/205

All spec tests pass.
Beaker tests do provide the expected keepalived config file.

Hi @a-dekker, thanks for the PR. Can you please take a look at the used email address in the commit? It isn't associated with your github account.

The email will be set to my work mail address and not my personal mail address.


app that displays the stats of a Fenecon solar system

This small app displays three values that are delivered from a Fenecon powered solar system.
On the left is a pie chart for the battery status. On the right is the consumption and the generated amount of energy.
Somehow the cli generated the fenecon.star file not under the apps/fenecon folder but instead on the root of the directory, which looks different in the documentation - should I change the location and make that directory myself?
Thanks!

I have read the CLA Document and I hereby sign the CLA

@raven-rwho Thanks for the PR. When CLA signing fails, it's usually due to commits being associated with an email address that's not on the Github account used to cut the PR. If that's the case here, opening a separate PR with the issue addressed might be the simplest path to a green build.

@matslina - I'm still wondering if it is correct that my code is not under the apps folder but in the root folder - as the cli generated it - is this correct?
Checks are all green now

Oh, good catch. Yes, the app needs to go into a separate directory under apps/, just like all the others.

@matslina - moved the code - now I have the problem that the endpoint can only be reached locally (192.168.x.x) and I get this error message - ca I somehow check if the config is non null to render a default message?

Closed, because internal sources can't be reached - would be great to update the docs accordingly


[WIP] CNV-20469: Apply activation key and organiztion ID to QuickCreate VM - part2

📝 Description
Apply activation key and organization ID to cloud-init config when creating RHEL VM with Quick Create VM flow.
🎥 Demo

/retest

/retest

Hey does it supporr config drive and also no cloud ?

Hey does it supporr config drive and also no cloud ?

Not sure, and is this relevant for this PR? if we will need to switch to a cloud drive or to the opposite, we will probably do it in a separate PR

Hey does it supporr config drive and also no cloud ?

Not sure, and is this relevant for this PR? if we will need to switch to a cloud drive or to the opposite, we will probably do it in a separate PR

Yes it does, we currently using both ways and its wrong, so we need to know which type it support

/retest


PolicyServer CR deletion delayed and blocked if associated policy in pending state

Behaviour
If a PolicyServer has a policy associated, and in pending state, then, it's not possible to delete the PolicyServer and associated policies just by deleting the CR. The controller says:
2021-10-07T13:46:41.192+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy server deletion since all cluster admission policies are not deleted yet        {"policyserver": "/reserved-instance-for-tenant-a2"}

Hence, the policy needs to be manually edited to remove finalizers.
Expected
Removing a PolicyServer removes all the policies associated with it, without manual intervention.
Reproducer
With a policy that will always fail to instantiate the policy-server pod because the spec.module is incorrect (and will be always in pending state):
apiVersion: policies.kubewarden.io/v1alpha2
kind: PolicyServer
metadata:
  name: reserved-instance-for-tenant-a2
spec:
  image: ghcr.io/kubewarden/policy-server:latest
  replicas: 1
  imagePullSecrets:
    - name: localregcred
  env:
    - name: KUBEWARDEN_LOG_LEVEL
      value: debug
    - name: KUBEWARDEN_LOG_FMT
      value: jaeger
  annotations:
    sidecar.jaegertracing.io/inject: default
---
apiVersion: policies.kubewarden.io/v1alpha2
kind: ClusterAdmissionPolicy
metadata:
  name: local-pod-privileged-policy
spec:
  policyServer: reserved-instance-for-tenant-a2
  module: registry://THIS-DOESNT-EXIST/pod-privileged-policy
  rules:
    - apiGroups: [""]
      apiVersions: ["v1"]
      resources: ["pods"]
      operations:
        - CREATE
        - UPDATE
  mutating: false

Controller logs:
2021-10-07T13:38:07.125+0200    DEBUG   controller-runtime.webhook.webhooks     received request        {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-policyserver", "UID": "14b69655-71ac-49e6-82e7-e1c379f16a10", "kind": "policies.kubewarden.io/v1alpha2, Kind=PolicyServer", "re
source": {"group":"policies.kubewarden.io","version":"v1alpha2","resource":"policyservers"}}
2021-10-07T13:38:07.126+0200    INFO    policyserver-resource   default {"name": "reserved-instance-for-tenant-a2"}
2021-10-07T13:38:07.127+0200    DEBUG   controller-runtime.webhook.webhooks     wrote response  {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-policyserver", "code": 200, "reason": "", "UID": "14b69655-71ac-49e6-82e7-e1c379f16a10", "allowed": true}
2021-10-07T13:38:07.144+0200    DEBUG   controller-runtime.webhook.webhooks     received request        {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-clusteradmissionpolicy", "UID": "f7214268-22de-4d1f-8d73-47a12eb4013d", "kind": "policies.kubewarden.io/v1alpha2, Kind=ClusterA
dmissionPolicy", "resource": {"group":"policies.kubewarden.io","version":"v1alpha2","resource":"clusteradmissionpolicies"}}
2021-10-07T13:38:07.145+0200    INFO    clusteradmissionpolicy-resource default {"name": "local-pod-privileged-policy"}
2021-10-07T13:38:07.145+0200    DEBUG   controller-runtime.webhook.webhooks     wrote response  {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-clusteradmissionpolicy", "code": 200, "reason": "", "UID": "f7214268-22de-4d1f-8d73-47a12eb4013d", "allowed": true}
2021-10-07T13:38:07.164+0200    INFO    controllers.policies.ClusterAdmissionPolicy     policy local-pod-privileged-policy pending
2021-10-07T13:38:08.559+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy registration since policy server is not yet ready       {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:08.589+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy registration since policy server is not yet ready       {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:13.604+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy registration since policy server is not yet ready       {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:18.641+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy registration since policy server is not yet ready       {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:23.684+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy registration since policy server is not yet ready       {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:28.723+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy registration since policy server is not yet ready       {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:33.759+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy registration since policy server is not yet ready       {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:38.798+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy registration since policy server is not yet ready       {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:43.295+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy server deletion since all cluster admission policies are not deleted yet        {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:43.304+0200    ERROR   controllers.policies.ClusterAdmissionPolicy     cannot update status of policy local-pod-privileged-policy      {"error": "failed to update ClusterAdmissionPolicy \"&ObjectMeta{Name:local-pod-privileged-policy,GenerateName:,Namespace:,SelfLink:
,UID:7b69acf6-8760-43ad-a86d-82a2ebc5f5d8,ResourceVersion:788,Generation:1,CreationTimestamp:2021-10-07 13:38:07 +0200 CEST,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{kubectl.kubernetes.io/last-applied-configuration
: {\\\"apiVersion\\\":\\\"policies.kubewarden.io/v1alpha2\\\",\\\"kind\\\":\\\"ClusterAdmissionPolicy\\\",\\\"metadata\\\":{\\\"annotations\\\":{},\\\"name\\\":\\\"local-pod-privileged-policy\\\"},\\\"spec\\\":{\\\"module\\\":\\\"registry://localhost:5000/pod-privileged-policy\\\",\\
\"mutating\\\":false,\\\"policyServer\\\":\\\"reserved-instance-for-tenant-a2\\\",\\\"rules\\\":[{\\\"apiGroups\\\":[\\\"\\\"],\\\"apiVersions\\\":[\\\"v1\\\"],\\\"operations\\\":[\\\"CREATE\\\",\\\"UPDATE\\\"],\\\"resources\\\":[\\\"pods\\\"]}]}}\\n,},OwnerReferences:[]OwnerReferenc
e{},Finalizers:[kubewarden],ClusterName:,ManagedFields:[]ManagedFieldsEntry{ManagedFieldsEntry{Manager:kubectl-client-side-apply,Operation:Update,APIVersion:policies.kubewarden.io/v1alpha2,Time:2021-10-07 13:38:07 +0200 CEST,FieldsType:FieldsV1,FieldsV1:{\\\"f:metadata\\\":{\\\"f:ann
otations\\\":{\\\".\\\":{},\\\"f:kubectl.kubernetes.io/last-applied-configuration\\\":{}}},\\\"f:spec\\\":{\\\".\\\":{},\\\"f:module\\\":{},\\\"f:mutating\\\":{},\\\"f:policyServer\\\":{},\\\"f:rules\\\":{}}},Subresource:,},ManagedFieldsEntry{Manager:kubewarden-controller,Operation:U
pdate,APIVersion:policies.kubewarden.io/v1alpha2,Time:2021-10-07 13:38:07 +0200 CEST,FieldsType:FieldsV1,FieldsV1:{\\\"f:status\\\":{\\\".\\\":{},\\\"f:policyStatus\\\":{}}},Subresource:,},},}\" status"}
sigs.k8s.io/controller-runtime/pkg/handler.(*enqueueRequestsFromMapFunc).Update
        /home/vic/code/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.0/pkg/handler/enqueue_mapped.go:63
sigs.k8s.io/controller-runtime/pkg/source/internal.EventHandler.OnUpdate
        /home/vic/code/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.0/pkg/source/internal/eventsource.go:94
k8s.io/client-go/tools/cache.(*processorListener).run.func1
        /home/vic/code/go/pkg/mod/k8s.io/client-go@v0.22.1/tools/cache/shared_informer.go:775
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1
        /home/vic/code/go/pkg/mod/k8s.io/apimachinery@v0.22.1/pkg/util/wait/wait.go:155
k8s.io/apimachinery/pkg/util/wait.BackoffUntil
        /home/vic/code/go/pkg/mod/k8s.io/apimachinery@v0.22.1/pkg/util/wait/wait.go:156
k8s.io/apimachinery/pkg/util/wait.JitterUntil
        /home/vic/code/go/pkg/mod/k8s.io/apimachinery@v0.22.1/pkg/util/wait/wait.go:133
k8s.io/apimachinery/pkg/util/wait.Until
        /home/vic/code/go/pkg/mod/k8s.io/apimachinery@v0.22.1/pkg/util/wait/wait.go:90
k8s.io/client-go/tools/cache.(*processorListener).run
        /home/vic/code/go/pkg/mod/k8s.io/client-go@v0.22.1/tools/cache/shared_informer.go:771
k8s.io/apimachinery/pkg/util/wait.(*Group).Start.func1
        /home/vic/code/go/pkg/mod/k8s.io/apimachinery@v0.22.1/pkg/util/wait/wait.go:73
2021-10-07T13:38:43.313+0200    INFO    controllers.policies.ClusterAdmissionPolicy     policy local-pod-privileged-policy pending
2021-10-07T13:38:43.331+0200    DEBUG   controller-runtime.webhook.webhooks     received request        {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-clusteradmissionpolicy", "UID": "eb735923-b2e2-4e03-b37d-90ffc8d80c3c", "kind": "policies.kubewarden.io/v1alpha2, Kind=ClusterA
dmissionPolicy", "resource": {"group":"policies.kubewarden.io","version":"v1alpha2","resource":"clusteradmissionpolicies"}}
2021-10-07T13:38:43.332+0200    INFO    clusteradmissionpolicy-resource default {"name": "local-pod-privileged-policy"}
2021-10-07T13:38:43.332+0200    DEBUG   controller-runtime.webhook.webhooks     wrote response  {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-clusteradmissionpolicy", "code": 200, "reason": "", "UID": "eb735923-b2e2-4e03-b37d-90ffc8d80c3c", "allowed": true}
2021-10-07T13:38:43.338+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy server deletion since all cluster admission policies are not deleted yet        {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:43.816+0200    DEBUG   controller-runtime.webhook.webhooks     received request        {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-clusteradmissionpolicy", "UID": "ef777572-f462-42de-856f-44a49acf447a", "kind": "policies.kubewarden.io/v1alpha2, Kind=ClusterA
dmissionPolicy", "resource": {"group":"policies.kubewarden.io","version":"v1alpha2","resource":"clusteradmissionpolicies"}}
2021-10-07T13:38:43.816+0200    INFO    clusteradmissionpolicy-resource default {"name": "local-pod-privileged-policy"}
2021-10-07T13:38:43.816+0200    DEBUG   controller-runtime.webhook.webhooks     wrote response  {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-clusteradmissionpolicy", "code": 200, "reason": "", "UID": "ef777572-f462-42de-856f-44a49acf447a", "allowed": true}
2021-10-07T13:38:43.822+0200    INFO    controllers.policies.ClusterAdmissionPolicy     delaying policy server deletion since all cluster admission policies are not deleted yet        {"policyserver": "/reserved-instance-for-tenant-a2"}
2021-10-07T13:38:48.843+0200    DEBUG   controller-runtime.webhook.webhooks     received request        {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-clusteradmissionpolicy", "UID": "a7d9958d-ea6a-41dc-bfda-ba89f53702bc", "kind": "policies.kubewarden.io/v1alpha2, Kind=ClusterA
dmissionPolicy", "resource": {"group":"policies.kubewarden.io","version":"v1alpha2","resource":"clusteradmissionpolicies"}}
2021-10-07T13:38:48.843+0200    INFO    clusteradmissionpolicy-resource default {"name": "local-pod-privileged-policy"}

I believe I know why the policies are not removed. The controller is sending the delete request to k8s. As we have a webhook configuration to mutate clusteradmissionpolicies resource the request is sent to to it (path /mutate-policies-kubewarden-io-v1alpha2-clusteradmissionpolicy). Which generates the logs that @viccuad mentioned in a previous comment:
2021-10-15T15:04:49.571+0200    DEBUG   controller-runtime.webhook.webhooks     wrote response  {"webhook": "/mutate-policies-kubewarden-io-v1alpha2-policyserver", "code": 200, "reason": "", "UID": "b78bd579-fda1-4e31-9ecf-7a2b2be45a1c", "allowed": true}

However, the code executed in this webhook adds the finalizer:
https://github.com/kubewarden/kubewarden-controller/blob/232f65fa694c41d9413aaebdbe8111574f27d9c3/apis/policies/v1alpha2/clusteradmissionpolicy_webhook.go#L52-L55
But I do not know why this request is being handled by this webhook. AFAICS, it should be trigger only for the create verb:
https://github.com/kubewarden/kubewarden-controller/blob/232f65fa694c41d9413aaebdbe8111574f27d9c3/apis/policies/v1alpha2/clusteradmissionpolicy_webhook.go#L47


fix: search for ldap users' name within an organization

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: anyidea:x: aidenluaidenlu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Project with composite: true fails to build if a dependency builds its .d.ts files in same directory as the .ts source files.

TypeScript Version:  3.5.0-dev.20190430

Search Terms:
composite "not in project file list"
Code
https://github.com/chriseppstein/reproduce-composite-build-issue
To reproduce:
git clone https://github.com/chriseppstein/reproduce-composite-build-issue.git
cd reproduce-composite-build-issue
yarn install
yarn compile

Building the project succeeds with the current configuration but by changing the project to "composite": true the build will fail with an error.
This simple project consumes a published npm module with a "types" property in package.json. The format of the project is such that the build results are colocated with the source *.ts files.
Expected behavior:
The build succeeds with composite: true
Actual behavior:
The build fails with this error:
error TS6307: File '/Users/ceppstei/Projects/tmp/repro-fs-tree-diff-issue/node_modules/fs-tree-diff/lib/entry.ts' is not in project file list. Projects must list all files or use an 'include' pattern.

Related Issues:
https://github.com/Microsoft/TypeScript/issues/25636 looks similar but the fix seems to be related to the fact it was a json file.

@sheetalkamat Thank you for fixing this!


Use master branch in the coveralls.io badge

Fixes #209

@rultor merge

@rultor merge

@suseika OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@suseika Done! FYI, the full log is here (took me 5min)


Fix namespace error on HeadsUpDirectionIndicator

#355
Change the bad namespace to the standard one

Hi @madvlad, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thanks for catching this!


[region-isolation] Treat as Sendable values that are meant to be ignored since they are marked with preconcurrency

rdar://133531625

@swift-ci smoke test


Improves the documentation on how to configure build.rs

Changes
Fixes #1742
Checklist

[x] An issue to be fixed by this PR is listed above.
[ ] New tests are added to ensure new features are working. Please refer to this page to see how to add a test.
[ ] ./frb_internal precommit --mode slow (or fast) is run (it internal runs code generator, does auto formatting, etc).
[x] If this PR adds/changes features, documentations (in the ./website folder) are updated.
[ ] CI is passing. Please refer to this page to see how to solve a failed CI.

@fzyzcjy please not that I took the liberty to change the md-file to have one sentence per line. In this way, future changes are easier to see in the diff. The output should not be affected by this reformatting.
Probably my description is a bit to verbose - feel free to reformulate or ask me to do so!

@fzyzcjy I guess all is fine (except for you to have an editorial look upon the proposed reformulation).
The CI fails two tasks:

Code coverage shrank -> not sure why, as even the report states that no file changed. I accidentally used a wrong comment sign in the cargo.toml, and fixed that - so maybe it complains about introducing and then removing a line. Though the report compares master with the last commit in this branch.
frb_example/flutter_via_create fails. I did not changed anything there, maybe a flaky run?

Code coverage shrank, frb_example/flutter_via_create fails

Just flaky, no worries!

@fzyzcjy thanks for the corrections!


Problem with protobuf generation when there is a multiline comments in the msg file

ROS2 Galactic.
Simple Example of the Bug.
Consider the file UUID.msg, identical with ros2/unique_identifier_msgs/msg/UUID.msg:
# A universally unique identifier (UUID).
#
#  http://en.wikipedia.org/wiki/Universally_unique_identifier
#  http://tools.ietf.org/html/rfc4122.html

uint8[16] uuid

Consider the file UUID.idl, generated by ROS2:
// generated from rosidl_adapter/resource/msg.idl.em
// with input from unique_identifier_msgs/msg/UUID.msg
// generated code does not contain a copyright notice

module unique_identifier_msgs {
  module msg {
    typedef uint8 uint8__16[16];
    @verbatim (language="comment", text=
      " A universally unique identifier (UUID)." "\n"
      "" "\n"
      "  http://en.wikipedia.org/wiki/Universally_unique_identifier" "\n"
      "  http://tools.ietf.org/html/rfc4122.html")
    struct UUID {
      uint8__16 uuid;
    };
  };
};

Consider the file UUID.proto, this is the file generated by rosidl_typesupport_protobuf/rosidl_adapter_proto/bin/rosidl_adapter_proto:
// generated from rosidl_adapter_proto/resource/idl.proto.em
// with input from unique_identifier_msgs:msg/UUID.idl
// generated code does not contain a copyright notice

syntax = "proto3";

package unique_identifier_msgs.msg.pb;

// A universally unique identifier (UUID).

 http://en.wikipedia.org/wiki/Universally_unique_identifier
 http://tools.ietf.org/html/rfc4122.html
message UUID
{

 bytes uuid = 293563397;
}

This is wrong and protoc will not compile it.
Lines 9-12 should instead be this:
// A universally unique identifier (UUID).
//
//  http://en.wikipedia.org/wiki/Universally_unique_identifier
//  http://tools.ietf.org/html/rfc4122.html

I think the problem is with this expression inside msg.proto.em: comment = "//" + re.sub(r"\\n", "\n//", annotation.value["text"]). However, I do not know why this ever worked, maybe re changed or an issue about different python versions. On my environment, if I change this line to comment = "//" + re.sub(r"\n", "\n//", annotation.value["text"]), then generation works OK.

@sebastian-freitag-pylot we were also hit by this bug. It also was not clear for me if smth changed in re behaviors or it never worked.


textcov_reports for Java projects

PR https://github.com/google/oss-fuzz/pull/9208 was incomplete in terms of placing correct files in textcov_reports for Java project.
We need coverage to place files in that directory which will be copied to the coverage bucket using cloud build, otherwise the Introspector build for Java fails.

@Navidem are you ablle to pick this up? Or is this something you can help with @DavidKorczynski ?

I think I got it:
This is how java coverage is loaded in FI:
https://github.com/ossf/fuzz-introspector/blob/54584d2846119b6aead7731e7ce49b8115b979fd/src/fuzz_introspector/code_coverage.py#LL658C76-L658C86
So, the coverage will copy that file into textcov_reports like this line:
https://github.com/google/oss-fuzz/blob/7efd35c1f23e804e4f707eb0b51c9498c810daa3/infra/base-images/base-runner/coverage#L382

This did the job: https://github.com/google/oss-fuzz/pull/9440/commits/9ba3411d3a5d46cec8ea7617a5e6e4e3e595139f


clash-mini: fix shortcuts

clash-mini: fix shortcuts
Creating shortcut for Clash.Mini (Clash.Mini.exe) failed: Couldn't find \scoop\apps\clash-mini\current\Clash.Mini.exe

[x] I have read the Contributing Guide.

/verify


Adding sleep in scripted test to make sure timestamp bumps

Fixes #2546. Ref #958/#965
scripted compiler-project/error-in-invalidated has been failing
frequently on Travis CI. It seems like incremental compiler is not
catching the change in source for changes/A2.scala.
Perhaps the machines are getting fast enough that we are doing three compilations within 1s?
/review @gkossakowski, @Duhemm

In https://github.com/sbt/sbt/pull/2523 I've been seeing flaky failures in the new test types-in-used-names-b, I wonder if that's the same issue. If so, it sure sounds like we need a better solution than randomly adding sleeps until the tests pass.

Assuming that the underlying issue is our way of change detection via last modified date, the two alternatives I can think of are:

checking hash of files to look for changes. (what's the overhead on calculating 1000s of hashes)
Java 7 file watching

I wonder if we can treat timestamp == timestamp case to be invalidated. This might also require another $ sleep 1000 for the reserve reason. For example, to test incremental compiler not doing additional compilation, we'd need to wait 1s.

I have never seen this problem on my Mac. Is time resolution on Travis filesystem lower?

@smarter, did you encounter the problem you describe on your local machine?

I didn't manage to get types-in-used-names-b to fail locally, but it still fails occasionally on travis with sleep 1000 so that's not it.


Contributions to repository directly via branching and pull requests?

Hi Jonas,
Do you accept contributions directly to this repository? I have given yxf the ability to translate XLSForm into JSON and back, and would love to send this up for inclusion in yxf.
My use case for yxf is making the numerous Survey123-based XLSForm 'apps' I have carriage of much easier to maintain and version control. JSON is much easier for me to work with because these apps are so large.
Many thanks!

This sounds great! Feel free to open a pull request.
JSON isn't very much different from YAML. You could think of YAML as an
extension of JSON, with some extra ways to quote strings and with a more
line-based structure. Given that YAML parsers exist for most programming
languages, I wonder if there really is a strong need for JSON? Could you
maybe explain a bit why you prefer it to YAML?
Anyway, please don't let these questions discourage you. I'm happy to
integrate your contributions.
On Sat, 6 Apr 2024, 09:26 Madeleine S, @.***> wrote:

Hi Jonas,
Do you accept contributions directly to this repository? I have given yxf
the ability to translate XLSForm into JSON and back, and would love to send
this up for inclusion in yxf.
My use case for yxf is making the numerous Survey123-based XLSForm 'apps'
I have carraige of much easier to maintain and version control. JSON is
much easier for me to work with because these apps are so large.
Many thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/Sjlver/yxf/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAARS6YPBU3QBQMOWKRSQDLY36WUJAVCNFSM6AAAAABF2HLXDWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDSMJSGE4DAMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


[Request] Random .nbs file

a feature to chose a .nbs file at random from a folder would also be amazing (so you get a different song each time you join or after a set amount of time has passed).
https://dev.bukkit.org/projects/joinmusic?comment=15

https://netjs.blogspot.com/2017/04/reading-all-files-in-folder-java-program.html?m=1

http://www.java2s.com/Code/CSharp/Development-Class/Givenadirectoryselectarandomfilefromit.htm


Rename all packages:

remove save and save-cloud prefixes completely for common modules. It can only be:  save/cosv-common (ONLY for SAVE/COSV specific common, in terms of Kotlin MPP for Native + JVM + JS), common (MPP for JS + JVM which are used EVERYWHERE), common-frontend (JS only code shared between COSV, SAVE, etc.) and common-backend (JVM only logic shared between COSV, SAVE, if needed). save-common should NOT be used in ANY COSV module as well as cosv-common cannot be used in SAVE.
we should have cosv-frontend, save-frontend and save-backend, cosv-backend. For save-specific components it is ok to have save-orchestrator, save-agent, etc.;
rename packages:

COSV and common packages should NOT have save in it's name
save-cloud-common packages should be renamed to com.saveourtool.common
cosv-backend instead of com.saveourtool.save.cosv.repository should be named as com.saveourtool.cosv.repository

Remove sandbox service (if someone wishes to have - can save in separate repository later);
After the removal of sandbox service - merge orchestrator-common with save-orchestrator;

@nulls if you will have any other ideas - welcome to share

@nulls if you will have any other ideas - welcome to share

Removing sandbox and merging save-orchestator-common with save-orchestrator can be done before renaming to reduce affected files
Suggestion to create a tag before renaming (or a branch at least)
We have save-cloud-charts, probably we need to split it too
What's about api-gateway and authentication-service? They are required for COSV and SAVE. Do we need to rename packages there?

What's about api-gateway and authentication-service? They are required for COSV and SAVE. Do we need to rename packages there?

Yeah, need to rename their packages as well! com.saveourtool.api-gateway

We also need to rename the paths for entities in save-cloud-common


AzSHOST1 : Extension AzureEdgeDeviceManagement and Extension AzureEdgeLifecycleManager are missing

Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?
https://azurearcjumpstart.io/azure_jumpstart_hcibox/cloud_deployment
Describe the issue or the bug
Second attempt to deploy the HCIBOX Env. Both times I receive these error messages and installation can't recover:
Waiting for extension installation to complete, sleeping for 2 minutes. Attempt 15 of 90
AzSHOST1 : Extension AzureEdgeTelemetryAndDiagnostics is in place and provisioned. Current state: Succeeded
AzSHOST1 : Extension AzureEdgeDeviceManagement is missing
AzSHOST1 : Extension AzureEdgeLifecycleManager is missing
To Reproduce
I followed steps as per documentation.
Expected behavior
Extension AzureEdgeDeviceManagement & Extension AzureEdgeLifecycleManager should be in place and provisioned automatically.
Environment summary
As per script part od the deployment.
Have you looked at the Troubleshooting and Logs section?

Screenshots

Additional context
I tried different Azure regions, same behaviour as far as this issue.

Further to this error, deployment now stops even earlier. I tried different regions: eastus2 and westeurope , same error ( see below).
INFO: Loaded Module 'Az.Accounts'
INFO: Loaded Module 'Az.ConnectedMachine'

TerminatingError(): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: A parameter cannot be found that matches parameter name 'AsPlainText'."
TerminatingError(): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: A parameter cannot be found that matches parameter name 'AsPlainText'."
TerminatingError(): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: A parameter cannot be found that matches parameter name 'AsPlainText'."
TerminatingError(): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: A parameter cannot be found that matches parameter name 'AsPlainText'."
TerminatingError(): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: A parameter cannot be found that matches parameter name 'AsPlainText'."
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: A parameter cannot be found that matches parameter name 'AsPlainText'.
A parameter cannot be found that matches parameter name 'AsPlainText'.
At C:\HCIBox\New-HCIBoxCluster.ps1:1443 char:9

    Invoke-Command -VMName $node.Hostname -Credential $localCred  ...

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidArgument: (:) [ConvertFrom-SecureString], ParameterBindingException
FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.ConvertFromSecureStringCommand
PSComputerName        : AzSHOST1

This seems like a similar issue as #2620 - see that issue for a temporary workaround.

Hi,
I've tried to deploy the environment again using azdhttps://azurearcjumpstart.io/azure_jumpstart_hcibox/deployment_azd.
Azure Arc Jumpstarthttps://azurearcjumpstart.io/azure_jumpstart_hcibox/deployment_azd
Extensive. Automated. Open-Source. Community Driven.
azurearcjumpstart.io
I'm getting the error below and can't continue:
[cid:5d97e8fc-4322-4f43-b585-233015b62ee6]
Luca Ottonari
Thank you and Kind Regards
AZURE CLOUD SOLUTION ARCHITECT
@.***
[Microsoft Logo]

From: Dale Kirby @.>
Sent: Thursday 25 July 2024 13:16
To: microsoft/azure_arc @.>
Cc: Author @.>; Comment @.>
Subject: Re: [microsoft/azure_arc] AzSHOST1 : Extension AzureEdgeDeviceManagement and Extension AzureEdgeLifecycleManager are missing (Issue #2614)
Closed #2614https://github.com/microsoft/azure_arc/issues/2614 as completed via #2627https://github.com/microsoft/azure_arc/pull/2627.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azure_arc/issues/2614 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKDQXCHEWX7QHWUKZD5UHP3ZODUCTBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLKRUGY4DCMJZGY2TIN5ENZQW2ZNJNBQXGX3MMFRGK3ECUV3GC3DVMWSHI4TVMWSG4YLNMWXHOYLUMNUF6YLDORUXM2LUPGWHG5LCNJSWG5C7OR4XAZNFJFZXG5LFUZ2G64DJMNZZHAVEOR4XAZNKOJSXA33TNF2G64TZUV3GC3DVMWUTENBRGIZDKMJSGKBKI5DZOBS2K2LTON2WLJLWMFWHKZNKGI2DCMJTGAYTIMRQQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRUGY4DCMJZGY2TIN5HORZGSZ3HMVZKMY3MN5ZWKZA.
You are receiving this email because you authored the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi again,
I then tried the Azure CLI deployment, still getting an error:
[cid:38760a95-1ff3-4850-802c-8b28faaad0de]
[cid:e870dc53-5a18-40be-8ee2-239d45898aa3]
[cid:7b0a7527-dbaa-4437-8abc-f4fcf6645786]
Luca Ottonari
Thank you and Kind Regards
AZURE CLOUD SOLUTION ARCHITECT
@.***
[Microsoft Logo]

From: Dale Kirby @.>
Sent: Thursday 25 July 2024 13:16
To: microsoft/azure_arc @.>
Cc: Author @.>; Comment @.>
Subject: Re: [microsoft/azure_arc] AzSHOST1 : Extension AzureEdgeDeviceManagement and Extension AzureEdgeLifecycleManager are missing (Issue #2614)
Closed #2614https://github.com/microsoft/azure_arc/issues/2614 as completed via #2627https://github.com/microsoft/azure_arc/pull/2627.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azure_arc/issues/2614 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKDQXCHEWX7QHWUKZD5UHP3ZODUCTBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLKRUGY4DCMJZGY2TIN5ENZQW2ZNJNBQXGX3MMFRGK3ECUV3GC3DVMWSHI4TVMWSG4YLNMWXHOYLUMNUF6YLDORUXM2LUPGWHG5LCNJSWG5C7OR4XAZNFJFZXG5LFUZ2G64DJMNZZHAVEOR4XAZNKOJSXA33TNF2G64TZUV3GC3DVMWUTENBRGIZDKMJSGKBKI5DZOBS2K2LTON2WLJLWMFWHKZNKGI2DCMJTGAYTIMRQQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRUGY4DCMJZGY2TIN5HORZGSZ3HMVZKMY3MN5ZWKZA.
You are receiving this email because you authored the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I opened a new issue , see Line | 214 | Throw "An error occurred creating the service principal. … | An error occurred creating the service principal. Error:Values of identifierUris property must use a verified domain | of the organization or its subdomain: 'http://admin-jumpstart-spn-2309' · Issue #2629 · microsoft/azure_arc (github.com)https://github.com/microsoft/azure_arc/issues/2629
[https://opengraph.githubassets.com/74f64c99acab2aa75365969e580129870e4522c0eda30a632987e6dd772c586c/microsoft/azure_arc/issues/2629]https://github.com/microsoft/azure_arc/issues/2629
Line | 214 | Throw "An error occurred creating the service principal. … | An error occurred creating the service principal. Error:Values of identifierUris property must use a verified domain | of the organization or its subdomain: 'http://admin-jumpstarthttps://github.com/microsoft/azure_arc/issues/2629
Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora? (https://azurearcjumpstart.io/azure_jumpstart_hcibox/deployment_azd) Describe the issue or the bug azd up fails to deploy th...
github.com
Luca Ottonari
Thank you and Kind Regards
AZURE CLOUD SOLUTION ARCHITECT
@.***
[Microsoft Logo]

From: Jan Egil Ring @.>
Sent: Friday 26 July 2024 12:04
To: microsoft/azure_arc @.>
Cc: Mention @.>; Author @.>; Comment @.***>
Subject: Re: [microsoft/azure_arc] AzSHOST1 : Extension AzureEdgeDeviceManagement and Extension AzureEdgeLifecycleManager are missing (Issue #2614)
@LucaOttohttps://github.com/LucaOtto The screenshots is not visible in the GitHub issue. Could you add them and either reopen this issue if the error is the same as the initial message or create a new one? Thanks!
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azure_arc/issues/2614#issuecomment-2252523465 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKDQXCEQDYFKOBBOFGTMJALZOIUMZBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI2DMOBRGE4TMNJUG6SG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJSGQYTEMRVGEZDFAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDENBRGEZTAMJUGIYIFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI2DMOBRGE4TMNJUG6TXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi,
I redeployed the HCI Stack env using the https://azurearcjumpstart.io/azure_jumpstart_hcibox/deployment_az guide.
I'm still seeing errors in the New-HCIBoxCluster logs, see below
INFO: Loaded Module 'Az.Storage'
[Build cluster - Step 10/11] Validate cluster deployment...
PS>TerminatingError(New-AzResourceGroupDeployment): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 4:41:54 PM - Error: Code=LocationNotAvailableForResourceType; Message=The provided location 'eastus2' is not available for resource type 'Microsoft.AzureStackHCI/clusters'. List of available regions for the resource type is 'australiaeast,southcentralus,eastus,westeurope,southeastasia,canadacentral,japaneast,centralindia'.
"

TerminatingError(New-AzResourceGroupDeployment): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 4:41:54 PM - Error: Code=LocationNotAvailableForResourceType; Message=The provided location 'eastus2' is not available for resource type 'Microsoft.AzureStackHCI/clusters'. List of available regions for the resource type is 'australiaeast,southcentralus,eastus,westeurope,southeastasia,canadacentral,japaneast,centralindia'.
"
TerminatingError(New-AzResourceGroupDeployment): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 4:41:54 PM - Error: Code=LocationNotAvailableForResourceType; Message=The provided location 'eastus2' is not available for resource type 'Microsoft.AzureStackHCI/clusters'. List of available regions for the resource type is 'australiaeast,southcentralus,eastus,westeurope,southeastasia,canadacentral,japaneast,centralindia'.
"
TerminatingError(New-AzResourceGroupDeployment): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 4:41:54 PM - Error: Code=LocationNotAvailableForResourceType; Message=The provided location 'eastus2' is not available for resource type 'Microsoft.AzureStackHCI/clusters'. List of available regions for the resource type is 'australiaeast,southcentralus,eastus,westeurope,southeastasia,canadacentral,japaneast,centralindia'.
"
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 4:41:54 PM - Error: Code=LocationNotAvailableForResourceType; Message=The provided location 'eastus2' is not available for resource type 'Microsoft.AzureStackHCI/clusters'. List of available regions for the resource type is 'australiaeast,southcentralus,eastus,westeurope,southeastasia,canadacentral,japaneast,centralindia'.
New-AzResourceGroupDeployment : 4:41:54 PM - Error:
Code=LocationNotAvailableForResourceType; Message=The provided location
'eastus2' is not available for resource type
'Microsoft.AzureStackHCI/clusters'. List of available regions for the
resource type is 'australiaeast,southcentralus,eastus,westeurope,southeastasi
a,canadacentral,japaneast,centralindia'.

At C:\HCIBox\New-HCIBoxCluster.ps1:1783 char:1

New-AzResourceGroupDeployment -Name 'hcicluster-validate' -ResourceGr ...

  + CategoryInfo          : NotSpecified: (:) [New-AzResourceGroupDeployme
 nt], Exception
  + FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdle
 ts.Implementation.NewAzureResourceGroupDeploymentCmdlet

PS>$global:?
False

Windows PowerShell transcript end
End time:<PHONE_NUMBER>4154

I'm also still seeing the same issue with the extensions, they are not installed at AzHOST1 / HOST2


High Contrast Color Ramp

Can we get a "High Contrast" color ramp as well?

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

ID: ab4100d3-1a06-29b9-dedc-d0eaed0b4718
Version Independent ID: 3c582b5e-e654-458d-62da-95706b3370fc
Content: Design Guidelines Reference - Teams
Content Source: msteams-platform/resources/design/components/color.md
Product: msteams
GitHub Login: @o365devx
Microsoft Alias: o365devx

Issue closed based on update received from Heath (03/16) about the  design team (Cristian) confirming that there are no plans to add this to any docs since the Teams client will handle the color changes automatically.


Find and Replace need a file limit cap

https://github.com/blue-jay/jay/commit/09500ebde6d847fa155c683d011f43d3f21adec3


Added test for replication policy

Signed-off-by: hessio<EMAIL_ADDRESS>Problem Statement

Added features from list https://seagate-systems.atlassian.net/wiki/spaces/PUB/pages/731021762/Patrick+s+Test+Script

@hessio , this is really old. You still want this?


Add 1.24 release channel

Proposed Changes

Types of Changes

Verification

Testing

Linked Issues

User-Facing Change

Further Comments

Don't forget to sign your commit for DCO!

Done.

Should I also bump stable to 1.23.7?

@brandond any thoughts?

Any update?

Sorry for the delay and we appreciate the PR; we're currently in a code freeze for release so we're just waiting for some final validations before we land any new PRs


Improve DropZone

refactor: improve src/components directory exports
refactor: put root layout around the entire app
refactor: remove useless div
fix: avoid DropZone leaking style to children
refactor: simplify DropZone API
refactor: use a single drop zone to load data
fix: improve DropZone layout and style

Closes: https://github.com/zakodium-oss/analysis-ui-components/issues/189
Closes: https://github.com/zakodium-oss/analysis-ui-components/issues/161
Closes: https://github.com/zakodium-oss/analysis-ui-components/issues/263
Closes: https://github.com/zakodium-oss/analysis-ui-components/issues/299

Which commit fixed #299?

I don't know. There's no point where I was able to reproduce the buggy behavior.


the sub pr of  javascript sdk

This PR exceeds the recommended size of 1200 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

This PR exceeds the recommended size of 1200 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

This PR exceeds the recommended size of 1200 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

This PR exceeds the recommended size of 1200 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

the generated code should not be added to the git version control


Testing buttons using tester.tap to show a dialog gives Framework Error

Steps to Reproduce

Have a method open an AlertDialog
Have a button execute the method
In a test, use await tester.tap(find.byKey(const Key('LoginBtnKey'))); to tap the button
Then verify that the dialog is shown using expect(find.byType(AlertDialog), findsOneWidget);
This gives a framework error.

Logs

══╡ EXCEPTION CAUGHT BY GESTURE ╞═══════════════════════════════════════════════════════════════════
The following assertion was thrown while handling a gesture:
'package:flutter/src/widgets/localizations.dart': Failed assertion: line 446 pos 12: 'context !=
null': is not true.

Either the assertion indicates an error in the framework itself, or we should provide substantially
more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=BUG.md

When the exception was thrown, this was the stack:
#2      Localizations.of (package:flutter/src/widgets/localizations.dart:446:12)
#3      debugCheckHasMaterialLocalizations.<anonymous closure> (package:flutter/src/material/debug.dart:88:23)
#4      debugCheckHasMaterialLocalizations (package:flutter/src/material/debug.dart:127:4)
#5      showDialog (package:flutter/src/material/dialog.dart:701:10)

Analyzing weekplanner...
No issues found! (ran in 6.1s; 157 public members lack documentation)

[✓] Flutter (Channel stable, v1.2.1, on Mac OS X 10.14.4 18E226, locale da-DK)
    • Flutter version 1.2.1 at /Users/Tricky/development/flutter
    • Framework revision 8661d8aecd (8 weeks ago), 2019-02-14 19:19:53 -0800
    • Engine revision 3757390fa4
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/Tricky/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    ✗ Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] iOS toolchain - develop for iOS devices (Xcode 10.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2, Build version 10E125
    • ios-deploy 1.9.4
    • CocoaPods version 1.6.1

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 33.3.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] IntelliJ IDEA Community Edition (version 2018.3.5)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 33.3.2
    • Dart plugin version 183.5912.23

[!] VS Code (version 1.29.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[!] Connected device
    ! No devices available

! Doctor found issues in 3 categories.

I'm looking for the same resolutions.

Hi @Tricky12321
Are you still experiencing this issue latest dev channel?
If yes,  can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


compiling failed on Ubuntu ARM64

I'm trying to compile a debug version of the contracts-node on Ubuntu ARM64, but got the following error.
Compiling contracts-node v0.17.0 (/home/parallels/Desktop/substrate-contracts-node/node)
error: linking with cc failed: exit status: 1
....
= note: collect2: fatal error: ld terminated with signal 9 [Killed]
compilation terminated.

I am not sure why following command: cargo install contracts-node --git https://github.com/paritytech/substrate-contracts-node.git --force --locked does not work on my machine, but following setups allows me to compile the repository:

clone substrate-contracts-node repository
execute cargo build --locked

On Debian machine works. Let me know if you have some issues with logs. Remember also to install all Substrate/Polkadot prerequisites.


Update array_api_version to 2023.12

Note that there are a few things that aren't fully covered in the test suite, namely tile and searchsorted aren't tested very well. I believe dask has some NotImplementedErrors there, but NumPy, CuPy, and Torch should (as far as I can see) be OK, since they just copied NumPy and the standard is based on NumPy. See https://github.com/data-apis/array-api-compat/issues/127

Defaulting to the most recent released version of the standard once test coverage for that version is (more or less) complete seems like a good idea to me, so +1 for this to go in when CI is happy.
If some users were relying on this in their CI without setting explicitly the version they're testing, that's easy enough to fix on their end.


Patch for #87

@jdegoes This is a band-aid for now. Could you please review?
A correct-by-construction approach is in the works.
Edit : I'm not sure my approach will work. We basically want to ensure that the action associated with the initializer doesn't return immediately, but is asynchronous, so that we don't try to rerender during the first render. I thought of using an indexed monad with the new custom do notation feature, but that won't work, since even if we label async and sync, there's no way to guarantee an Aff action wasn't constructed using, say, pure.

We could add a phantom type parameter to Aff to indicate whether or not the action is asynchronous. The problem with that is it inhibits composition, anytime you want to compose a sync with an async, you have to manually async the Aff to switch over the type param.
You can use later to make a sync action asynchronous, which may be a better way of solving this.

@paf31 ^^^

Sure, that sounds like a good way to address this.

I assume you want a merge on this, right?

Yes please if that's ok. I'll add a call to later in a separate PR if we want to go that route, but that seems like the simplest safe-by-construction approach.


How can I export PPTX

click the button, I can only export pdf. If I want to export pptx, what should I do?

Have you already installed Google Chrome?

I don't have chrome installed, can't edge work?

i have installed node.js

Edge will meet the requirements.
I don't know the cause, so I'll try to add a debug mode so that anyone can check the error log.

How to export pptx under normal circumstances? because readme.md is not very clear, I don't know how to do it.

Just click the button at the top of the preview window as you would with a pdf.

i have installed node.js

you need install npx .  $npm install -g npx ,then reboot ob and try export again ! good luck！


Adjusting default settings

Hello. I'm wondering if it's possible to adjust the default font-size, font-family, and text-alignment?

I am investigating this at the moment!

This library does not support styling of the cells. The underlying library used only allows styling in the paid version.