Bug Report or Feature Request (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request

Versions.
@angular/cli: 1.0.0
node: 6.9.2
os: win32 x64
@angular/animations: 4.0.1
@angular/common: 4.0.1
@angular/compiler: 4.0.1
@angular/core: 4.0.1
@angular/forms: 4.0.1
@angular/http: 4.0.1
@angular/platform-browser: 4.0.1
@angular/platform-browser-dynamic: 4.0.1
@angular/router: 4.0.1
@angular/upgrade: 4.0.1
@angular/cli: 1.0.0
@angular/compiler-cli: 4.0.1
Repro steps.

Read the following: https://github.com/angular/angular-cli/blob/master/docs/documentation/stories/global-styles.md
In my .angular-cli.json file, add the following to the styles array:
"styles": [
"scss/style.scss",
{ "input": "scss/style.client-1.scss", "lazy": true },
{ "input": "scss/style.client-2.scss", "lazy": true }
],
What is next step to load either of these styles at runtime?

Desired functionality.
I need to provide different global styles for certain customers to my website and once they login, override certain bootstrap variables (colors, logo, etc). I have defined some client specific SCSS files and marked them as lazy load in the styles array.
Now I need to load them...help!
Docs in the link below mention "You can also rename the output and lazy load it by using the object format" - so how do I load them?
Mention any other details that might be useful.
https://github.com/angular/angular-cli/blob/master/docs/documentation/stories/global-styles.md

When looking at the cli output, the lazy loaded files are generated, so with:
"styles": [
        {"input": "../test-style.scss", "lazy": true, "output": "test-style"}
],

There will be a test-style.bundle.js generated:
chunk    {4} test-style.bundle.js, test-style.bundle.js.map (test-style) 9.88 kB {7} [initial]
However I didn't really manage to find a civil way of importing that bundle withing the app code. The bundle can be imported in the index.html via script tag, but importing it before inline.bundle.js will result in webpack error. Importing it afterwards will work - this can be done from the app code by appending the script tag with the bundle output name:
function loadScript(scriptUrl) {
  const script = document.createElement('script');
  script.src = scriptUrl;
  document.body.appendChild(script);
}

loadScript('test-style.bundle.js');

This will load the styles, but it is hardly an ideal solution. I as well would really like to know a proper way to load lazily both styles and scripts (as this is applicable to scripts as well). It should also be added to the docs I think.

Just tried this too. I Copy/Pasted styles.scss and called it lazy.scss then added it like in the story.

/styles.bundle.js // this is added eagerly
/lazy.bundle.js // I can add this manually to index.html or lazily programmatically

It would be great If someone describes .. how to programatically refer the lazy generated Script / Styles at runtime.. the bundles are generated at build time.. but couldn't find a proper way to load at it runtime.

@a5hik unfortunately the CLI doesn't support programmatically adding lazy scripts and styles because there isn't a way to tell when it should be loaded. You will have to do that yourself.

I actually ended up moving all the global scripts and styles to corresponding modules.. wanted to load everything lazily..

Closing as above.

I don't know why this was closed. The question still very much remains.
When I lazy load a css file, the production build process output includes a chuck hash that I can't know, making it impossible to know in my code the name of the file. Let me show. If I add the following to my angular-cli.json:
    "styles" : [
        { "input" : "foo.css", "lazy" : true }
    ]

then the build will output a file called foo.<some random hash>.bundle.js.
Because the file name is generated and not static, I can't lazy load it. How do I get either the name to be static... or what is the prescribed way to do this by the Angular CLI team?  How do I use it?

@filipesilva any idea about this?
Are there any specific documentation about how to properly use globally lazy loaded scripts?
https://github.com/angular/angular-cli/wiki/stories-global-scripts
docs written here is kinda vague that its hard to know how to properly use in the "real world"

@rafagsiqueira  i did everything that you did, then run npm start , but i don't see my bundles.
{
"input":"../src/assets/workflowengine/js/workflowdesigner.min.js",
"lazy":true,
"output": "lazy-wfdesigner"
}
I see all others bundles loaded in index.html which is fine. Where to look for lazy bundle?

This is what I use to create my lazy style bundle
{
    "input": "src/styles/lazy-styles.scss",
    "lazy": true,
    "bundleName": "lazy-style"
}

This is how I load the bundle in my app.component.ts' constructor
// Add lazy loaded css
if (environment.production) {
  const element = document.createElement('link');
  element.rel = 'stylesheet';
  /* Only works as stylesheet but not with preload
  element.rel = 'preload';
  element.as = 'style';
  */
  element.href = 'lazy-style.css';
  document.body.appendChild(element);
} else {
  const element = document.createElement('script');
  element.src = 'lazy-style.js';
  document.body.appendChild(element);
}

Why is there a .js file in development mode and it compiles to a .css file in production? Is there any reason for this or did I just configure it the wrong way?

@madmurl0c the JS file in dev builds is for faster CSS rebuild. You can make it always be css with --extractCss=true. If you set this on the build options in angular.json, it will always apply.

@filipesilva Thanks, extractCss did the trick :)
For anyone having issues with this, the following works fine for me:
angular.json
"styles": [
    "src/styles/styles.scss",
    {
        "input": "src/styles/lazy-styles.scss",
        "lazy": true,
        "bundleName": "lazy-style"
    }
],
"extractCss": true,

constructor in app.component.ts
const preloadElement = document.createElement('link');
preloadElement.rel = 'preload';
preloadElement.as = 'style';
preloadElement.href = 'lazy-style.css';
document.body.appendChild(preloadElement);

const lazyStyleElement = document.createElement('link');
lazyStyleElement.rel = 'stylesheet';
lazyStyleElement.href = 'lazy-style.css';
document.body.appendChild(lazyStyleElement);

Hi,
What's bothering me here with this approach, is that we do access DOM directly and not using abstraction. What should be the prefered way to do so ?
One other question: let's say i change my angular.json file to add { "input" : "myUrl", "lazy": true, "bundleName": "myBundle"} in the Builder configuration. This applies only for ng build , right ?
But what if i want those exact same file in my dev process, by doing ng serve ? For the dev process, it seems to me that I can't have a way to lazy load those same files.
Or am i missing something ?
Maybe I should open another issue ? I couldn't find any relevant information about this on the web & docs.

@johanchouquet neither Angular or Angular CLI provide an abstraction for lazy loading CSS. Angular CLI just creates CSS bundles that aren't automatically loaded. I don't think that Angular itself needs to provide an abstraction for it either, mostly because it's not Angular specific.
Since ng serve actually uses the build configuration, both will have the lazy CSS bundle.

@johanchouquet neither Angular or Angular CLI provide an abstraction for lazy loading CSS. Angular CLI just creates CSS bundles that aren't automatically loaded. I don't think that Angular itself needs to provide an abstraction for it either, mostly because it's not Angular specific.
Since ng serve actually uses the build configuration, both will have the lazy CSS bundle.

Thanks @filipesilva . That's clear for me for ng serve and ng build 👍 !
About the abstraction in Angular, I understand that the CLI provides the starting solution and this part of the job is done i believe. But I'm more interested in the 'How to use the JS scripts that have been lazy loaded' part ?
Because, to me, this solution would work only in a browser environment, right ? So what about server side, or in web worker etc ... ? Shouldn't we take car of this using for example Renderer2 at the very least ? But even doing so, we still would have to interact with the nativeElement and call some method to create the nodes. And that's what i think is discouraged by the Angular team.
Again, this may not be the best place to talk about it, but sure where it'd be better. Sorry for that.

Personally I haven't given much thought about how to use lazy loaded js/css in a server environment. But the default builder in Angular CLI is only mean to build browser apps, so I don't think that's something that should be covered there. The folks at https://github.com/angular/universal, who cover the server journey, would know more.

@filipesilva, this is true indeed. So, maybe this is not a big deal. I was just wondering about code portability there. So this makes sense to do inject those scripts in the DOM directly.


If dir=true and prevExist=true but the target node is a key it turns into a dir

If dir=true and prevExist=true PUT only if the target node is a directory. Otherwise return "Not a directory".
Via: https://github.com/coreos/go-etcd/issues/90
/cc @onsi

I'm doing some work to address this.

Thoughts on the PR?

@philips It seems like this does not really cause any issue in practice. Fixing this needs some effort (see https://github.com/coreos/etcd/pull/2147). I prefer to mark this won't fix.

Closed via https://github.com/coreos/etcd/blob/master/Documentation/v2/README.md#known-bugs.


🐛 Bug Report: Secrets are visible in browser address bar after pressing "Start Over" in Scaffolder wizard

📜 Description
Hi,
in Version 1.25.2 I created a scaffolder template, where I use a password.
After pressing "create" and waiting for the steps to end, I pressed "Start Over". Afterwards you can see my form values in the browser address bar. Passwords can easily be seen as URL parameters (see screenshot).
This could be a problem, if - for example - you make a screen share or record a training video.
Some ideas of how to fix that?
Thanks and greetings,
Josef
👍 Expected behavior
Passwords shouldn't be visible in the Browsers address bar.
👎 Actual Behavior with Screenshots

👟 Reproduction steps
Use a Secret field in Scaffolder template, fill out everything, Create and "Start Over". You will see all parameters, also the secret and its value, in the browser address bar.
Template snippet of the secret parameter:
        password:
          title: Password
          default: Password
          type: string
          description: Password of Service Account.
          ui:autofocus: true
          ui:field: password
          ui:widget: password

📃 Provide the context for the Bug.
No response
🖥 Your Environment
Recent Chrome Browser
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Hey @jomeier! Thanks for raising this!
I think if you're wanting to collect secrets from the frontend, you're going to be best off following this guide: https://backstage.io/docs/features/software-templates/writing-templates/#using-secrets
TLDR is you'll want to use ui:field: Secret in order to protect these secrets. We should probably look at overriding the default ui:widget: password and ui:field: password so that it's clear that these are not secure.

I wonder if we can make this clearer for users that the ui:widget: password is not secure. I'm thinking that there's two options:

We replace the ui:widget: password with the ui:field: Secret and it just works, or we render red text saying that this is not secure and you should use ui:field: Secret instead.
We reject templates in the processor that have ui:widget: password

We also discussed to option of simply overriding the password widget with a plain text one. Potentially with a warning somewhere to avoid confusion

One concern I have with that is, that the secret must be accessible in the form context to use it in custom ui field extensions:
https://backstage.io/docs/features/software-templates/writing-custom-field-extensions/#access-data-from-other-fields
With ui:widget: Secret passwords are secure, but can't be accessed in the form. I only get '****' characters instead of the secret in my code and not the secret value itself. Or did I miss the right spot, where I can get the value of fields marked with "ui:field: secret" ?

@jomeier no, with ui:widget passwords are unfortunately not treated as secure, they are not redacted in logs, and could be accessed / logged through API's. When you use ui:field: Secret you will need to use ${{ secrets.PARAM_NAME }} not ${{ parameters.PARAM_NAME }} instead.

I'm gonna whip up a PR to replace the ui:widget: password with our our own secret implementation, but I have some concerns that we're going to break existing templates by doing that as you have to use ${{ secrets }} instead. But maybe that's OK @Rugvip thoughts?

I've put together this: https://github.com/backstage/backstage/pull/24834 happy for some feedback to push it the other way if we think that's a better idea.

@jomeier no, with ui:widget passwords are unfortunately not treated as secure, they are not redacted in logs, and could be accessed / logged through API's. ~When you use ui:field: Secret you will need to use ${{ secrets.PARAM_NAME }} not ${{ parameters.PARAM_NAME }} instead.~
The stars that you see in the ui input gives the sense that these things are secure and they are not, it's just a mask, so we ant to make that more visible to people that using ui:widget: Password things aren't secure.
EDIT: sorry I realised you were talking about form context, I think that we'd rather encourage the use of ui:field: Secret and then you can use the hook useTemplateSecrets to grab the secrets context rather than using the formContext for this.

Can I use TemplateSecrets in a seperate custom UI field to access secrets from another ui field?

I'm gonna whip up a PR to replace the ui:widget: password with our our own secret implementation, but I have some concerns that we're going to break existing templates by doing that as you have to use ${{ secrets }} instead. But maybe that's OK @Rugvip thoughts?

I'm sure it would break templates :D

Can I use TemplateSecrets in a seperate custom UI field to access secrets from another ui field?

Yes, for sure!

I'm sure it would break templates :D

Yeah, but is that better than end users possibly using ui:widget: password and potentially leaking sensitive data through API's?

With a proper guidelines how to fix it, it shouldn't be a big burden how to update templates.
Especially if upgrade command will point which templates are affected

Think we can close this at this point. Should be covered by the ui:field: Secret instead.


Profil- og brukerinnstillinger | Ved å legge til fargekoding som skiller mellom privat og bedrift, forventer vi at brukerne vil raskt kunne identifisere og skille mellom ulike enheter, fordi fargekoding gir visuell klarhet og gjenkjennbarhet.

Description
a
Additional Information
No response
Tasks
No response
Acceptance Criterias
No response

Hello, I tried to solve the issue.
This is what I did:
Implement an unread status indicator in the InboxItem component to visually distinguish unread items from read ones.
You can review changes in this commit: https://github.com/jjyutm4532/digdir-dialogporten-frontend-1436/commit/86b3b3f96ac39757ca6e99bd59ee3ecb475add72.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.


Customize NavigationExperimental Transitioning Box Shadow?

I'm trying to customize the styles of the scene as it transitions in, similar to using the sceneStyles prop on the standard Navigator. Is there a way to do this? The scene has a heavy box shadow by default for iOS that I would like to customize (notice the slight render glitch as a scene pops off the screen):
https://cdn-images-1.medium.com/max/800/1*xuqhfIZCKL6xTaf2-zaO3A.gif
Thanks!

This is a known problem but I'm not sure there is an issue yet for it with regard to NavigationExperimental. There is one for the older Navigator: https://github.com/facebook/react-native/issues/2301
Looking at the iOS Settings app and playing around with its navigation, it appears like NavigationCard's shadowOpacity and/or shadowRadius should be animated in NavigationCardStackStyleInterpolator.
I haven't had a chance to play around with doing that but you could try it out by using an animated value for those style properties.
If you're using NavigationCardStack, you can use the cardStyle prop that was added in 0.30 (available today). If you're not using it, you can just use the style prop directly.
If it works out, it would be a great PR. I'll probably have a look at it when I next get a chance if you'r not able to.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/customize-navigationexperimental-transitioning-box-shadow
Product Pains has been very useful in highlighting the top bugs and feature requests:
https://productpains.com/product/react-native?tab=top
Also, if this issue is a bug, please consider sending a pull request with a fix.


Enhancement: Publish Houdini point cache through Deadline

Is there an existing issue for this?

[X] I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?
Hey! Can we have a option to publish point cache through deadline similar to the option we have in Arnold(Render)Rops. This feature can really a timesaving for the artists.
How would you imagine the implementation of the feature?
Publishing point cache through the deadline.
There should be two options:

Local publish
Farm publish

Are there any labels you wish to add?

[X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:
currently we publishing using local machine
Additional context:
No response

I think this PR already intends to solve that: https://github.com/ynput/OpenPype/pull/4903
Any chance you could try that out?


"Open in business manager" doesn't appear when selecting Content ID comments

Overview:
When selecting the Content ID comment, the SFCC window only shows the header "Content Slot", without the button to link to business manager.
Steps to Duplicate:
Open inspector and select the dwContentID comment.
System Info:
MacOS version: 10.15.3
Chrome version: 79.0.3945.130

@nathanhemesath any chance you can past the comment block you selected as a markdown comment to this thread?  Seems like it's possible that the parsing of the comment is failing, and if that is happening, it is because there is something different about that specific comment block.  Having the actual comment would show me whats going on pretty much immediately.

@manifestinteractive here's the markdown comment.

@manifestinteractive ,
I apologize, I didn't realize my initial comment with the markdown was hidden.

@manifestinteractive,
After speaking with someone on your team, I realized the issue is on our end and not with the extension.
Our code isn't pulling in the SlotUUID, the linking doesn't work with having just the dwContextID.

@nathanhemesath Glad you got that sorted, I was actually having a hard time duplicating this... though maybe I was missing a possible custom setup or something.
BTW, I just found out through Eric that you are with one of our RVW Clients !!!  Stoked to know this is getting used on your team.  I develop this stuff in my free time, so it means a lot to see them used in the wild ❤


Font size for books title

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
Hello
I have applied your recommendations for changing font sizes as follows:
<style>
.page-content h1 { font-size: 1.8rem; }
.page-content h2 { font-size: 1.6rem; }
.page-content h3 { font-size: 1.4rem; }
.page-content h4 { font-size: 1.2rem; }
.page-content h5 { font-size: 1.1rem; }
.page-content h6 { font-size: 1.0rem; }
</style>

However, I realized that it doesn't change the font for the book, chapters and may be shelves titles.
It's OK when you display the list of available books, but, for exemple, if you click on a book to see the chapters and pages listed in that book, then the book title is in very large, unmodified type.
Is there an option I forgot to add in my modifications?
Exact BookStack Version
v23.01.1
Log Content
No response
PHP Version
No response
Hosting Environment
Debian 11

There are no specific classes/ids to target for the desired titles, but you could generically target them via:
<style>
.content-wrap h1 {
 font-size: 1.8rem;
}
</style>

Note: this may affect other areas of the app also, not just those requested titles.

Hi
Thanks Dan, that's exactly what I wanted

Awesome! will therefore close this off.


tests(smi): add tests for traffic split check and GetMatchingServices helper

merge after #67 otherwise pod_test will fail


Failed to parse output.

Describe the bug
Local LLMs either raise Timeout error or Fails to parse output.
Ragas version: 0.1.15
Python version: 3.11.3
Code to Reproduce
from transformers import AutoTokenizer
tokenizer = AutoTokenizer.from_pretrained("mistralai/Mistral-7B-Instruct-v0.3")
import pandas as pd
df = pd.read_csv("output.csv", sep=";")

data_samples = {
    'question': df['question'].tolist(),
    'answer': df['answer'].tolist(),
    'contexts': df['contexts'].apply(lambda x: [x] if isinstance(x, str) else x).tolist(),
    'ground_truth': df['ground_truth'].tolist()
}

from datasets import Dataset
dataset = Dataset.from_dict(data_samples)

from ragas import evaluate
from ragas.metrics import (faithfulness,
                           answer_correctness,
                           answer_relevancy,
                           context_recall,
                           context_precision)

from langchain_community.llms.huggingface_endpoint import HuggingFaceEndpoint
end = HuggingFaceEndpoint(repo_id="mistralai/Mistral-7B-Instruct-v0.3", max_new_tokens=512)
huggingface_llm = ChatHuggingFace(llm=end, tokenizer=tokenizer)
huggingface_embeddings = HuggingFaceEmbeddings(model_name="nomic-ai/nomic-embed-text-v1.5")

metrics=[faithfulness,
        answer_correctness,
        answer_relevancy,
        context_recall,
        context_precision]

score = evaluate(dataset=dataset,
        metrics=metrics,
        llm=huggingface_llm,
        embeddings=huggingface_embeddings,
        raise_exceptions=False
)

Error trace
Failed to parse output. Returning None.
Failed to parse output. Returning None.
Failed to parse output. Returning None.
Exception raised in Job[304]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
__root__ -> 0 -> verdict
  field required (type=value_error.missing))
Failed to parse output. Returning None.
Exception raised in Job[444]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
__root__ -> 0 -> verdict
  field required (type=value_error.missing))
Exception raised in Job[169]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
Failed to parse output. Returning None.
Failed to parse output. Returning None..
Exception raised in Job[309]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
__root__ -> 0 -> verdict
  field required (type=value_error.missing))
Failed to parse output. Returning None.
Exception raised in Job[174]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
__root__ -> 0 -> verdict
  field required (type=value_error.missing))
Failed to parse output. Returning None.
Failed to parse output. Returning None.
Exception raised in Job[449]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
__root__ -> 0 -> verdict
  field required (type=value_error.missing))
Failed to parse output. Returning None.
Exception raised in Job[179]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
__root__ -> 0 -> verdict
  field required (type=value_error.missing))
Failed to parse output. Returning None.
Exception raised in Job[314]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
__root__ -> 0 -> verdict
  field required (type=value_error.missing))
Failed to parse output. Returning None.
Failed to parse output. Returning None.
Exception raised in Job[184]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
__root__ -> 0 -> verdict
  field required (type=value_error.missing))
Failed to parse output. Returning None.
Failed to parse output. Returning None.
Failed to parse output. Returning None.
Failed to parse output. Returning None.
Failed to parse output. Returning None.
Exception raised in Job[454]: ValidationError(2 validation errors for ContextPrecisionVerifications
__root__ -> 0 -> reason
  field required (type=value_error.missing)
__root__ -> 0 -> verdict
  field required (type=value_error.missing))
Failed to parse output. Returning None.
Exception raised in Job[461]: ClientResponseError(429, message='Too Many Requests', url=URL('https://api-inference.huggingface.co/models/mistralai/Mistral-7B-Instruct-v0.3'))
Exception raised in Job[196]: ClientResponseError(429, message='Too Many Requests', url=URL('https://api-inference.huggingface.co/models/mistralai/Mistral-7B-Instruct-v0.3'))
Exception raised in Job[462]: ClientResponseError(429, message='Too Many Requests', url=URL('https://api-inference.huggingface.co/models/mistralai/Mistral-7B-Instruct-v0.3'))

Additional context
it only evaluates for answer_correctness, other values are all NaN

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

https://docs.ragas.io/en/latest/getstarted/rag_evaluation/#choosing-evaluator-llm  mentioned choosing evaluator llm，but no further details were mentioned

@g-hano were you able to resolve this issue?

bithikaj No, I won't use Ragas anymore, I always get timeout or parse errors.

hey @bithikaj which version are you using - I would suggest you maybe upgrade to v0.2. we some improvements in the prompts to fix this
hey @g-hano, I'm really sorry to hear that. it's true we had many small bugs like this which hurt the experience but now we have fixed a few common ones in v0.2. If you check it out or need any help migrating let me know. Would love your feedback 🙂

@jjmachan I am using v0.2.1 - getting many timeout errors with aws bedrock

what rate-limits do you have with your AWS bedrock plan?
could you also checkout: https://docs.ragas.io/en/stable/howtos/customizations/_run_config
that should help reduce timeout error - to try it out and let me know if it works? else we'll explore more

@jjmachan already added run config -RunConfig(max_workers=16, timeout=180),  was getting error on 33% of my eval dataset. Would setting  timeout to None make the timeout infinite?

@bithikaj nope but I think the best way would be to reduce the max_workers - did you fix this?


Canonical URL naming

We currently have canonical_url and canonical_ssl_url.
To resolve the URLs, concrete5 only uses canonical_url: canonical_ssl_url is only used when the redirect_to_canonical_url option is set to true.
So, what about renaming canonical_ssl_url to other_canonical_url or secondary_canonical_url?
That way, we avoid confusion if someone wants https as the default one, and http only as fall-back.

I think we discussed this and agreed to do this at some point somewhere. :+1:

Yeah - I definitely have concerns about this so it needs further discussion. Don't recall any slack discussion. When I'm at a computer I'll write more.
Sent from my iPhone

On Jun 14, 2017, at 10:16 AM, Michele Locati<EMAIL_ADDRESS>wrote:
I read something on Slack (but I previously had the same feeling).
I thought to write here because Slack is so dispersive and volatile...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

It seems that what's really volatile is my memory: it wasn't on slack but in #5451

Again I have no idea where korvin got that from. It wasn't from me.
The entire idea and reason for the two urls stems from the original ecommerce addon and the fact that historically some sites have two separate urls for ssl and non ssl.
http://www.mysite.com
https://secure.mysite.com
You didn't want to serve the entire site through the slow ssl URL. But you needed to mandate the use of ssl during checkout.
In reality there really ought to be a global getSecureUrl method accessible though some class that would return either the canonical ssl URL (or secondary URL or whatever it's called) OR the primary canonical URL if it itself supports ssl. Then you code addons to use that method and if that method returns blank you complain that some kind of ssl URL is required.

On Jun 14, 2017, at 10:02 PM, Michele Locati<EMAIL_ADDRESS>wrote:
It seems that what's really volatile is my memory: it wasn't on slack but in #5451
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Consider this other use case: someone wants to use HTTPS as its primary URL (for security reasons, because of a better Google ranking, ...), but yet he wants to support HTTP.
In this case, he currently set the Canonical URL to HTTPS, and the Canonical SSL URL to HTTP, and that's really misleading.
This is the reason why in #5564 I renamed the Canonical SSL URL to Alternative Canonical URL.
In any case, I do agree that we need a method to get the HTTPS Canonical URL (for that it's enough to return the Canonical URL or the Alternative Canonical URL - just check their scheme).


Prepare SharePoint to host the MIM Portal Step 4 needs to be step 6

In the section "Prepare SharePoint to host the MIM Portal", Step 4 needs to be moved down between Steps 6 and 7.  Otherwise, the MIM Portal page does not load properly.  If, however Steps 5 and 6 are performed, then step 4, the MIM Portal loads.  Was able to reproduce this twice.

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

ID: 1bb5efc7-7c39-cf26-70ef-a324d215af76
Version Independent ID: add2ba42-a910-ce5f-3767-35834085c2fa
Content: Configure SharePoint for Microsoft Identity Manager 2016
Content Source: MIMDocs/prepare-server-sharepoint.md
Product: microsoft-identity-manager
GitHub Login: @billmath
Microsoft Alias: billmath

The following issue is being closed due to the age. If this is still an issue, please re-submit this. Thank you.
#please-close


Spaces clobbered in Firefox

Space characters seem to be clobbered in Firefox as you type, and it's impossible to make a space between words unless you do a bunch of backspacing and messing about.
This is live in simpla-text as well, and is badly breaking.
Screencap repro:

Seems like this is to do with CSS's white-space property. As per MDN docs by default white space characters will be collapsed. In contenteditable Chrome & Safari insert   characters instead of spaces which stops the collapse, but in firefox it's regular spaces which get collapsed.
Fix for this is using white-space: pre-wrap which is what's used in ProseMirror's default stylesheet. Given RichText doesn't touch styles, this has to be applied by the elements i.e. simpla-article and simpla-text.
Alternatively we could add inline styles to the given element, but that would obviously break specificity. I don't think we could use the injected style sheets hack like placeholder as the styles need to apply to the host when its an inline editor i.e. no wrapping. @seaneking any ideas?

Fixed in simpla-text in 14f33b5c34f4db86ac547dcadbe5e9b611333b41
Fixed in simpla-article in 8f0b0f60ce5addfa77468c347ca22a4cb125ee5f
Doesn't fix the bug here, unless we decide we won't fix at this level, but I'll remove breaking as it can be patched up on the elements.

I'd say inline styles for thia because you specifically wouldn't want this overwritten, if it breaks core functionality like typing text without it

Or, probably cleaner, why not add to injected stylesheet, and then if inline just set inline tyke on host?

Should only have one injected stylesheet for everything though, IMO, maybe as a separate plugin.
I don't understand what the li rules are for in that default sheet, but probably want them.

Can also move some of the resets from article to the injected sheet.
Though ideally we should only include the styles that are needed, based on plugins available. Which is easy enough, just have CSS strings in JS per plugin (including placeholder) and then write to style tag based on what's available, with extra rule for inline whitespace rule for inline editors.
That seems a pretty nice solution to me, what say you @bedeoverend

tl;dr Yeah I'm happy to group all plugin styles into some injected stylesheet

Yeah happy to go with an injected stylesheet. My only concern there would be:

if inline just set inline tyke on host?

Someone having to apply different specificity (i.e. an !important for inline ones) for their styles based on whether the element is inline or not feels pretty confusing, for what is essentially just us cleaning up our implementation.
Then again, that really is a massive edge case at that point, you're talking about inline editors that want a custom white-space value.
Still, just getting the element to apply the styles feels a lot cleaner. Is there some way this can cleanly export a stylesheet of styles that the consumer can apply, or would that be a nightmare?

It's not an opinionated style, it's fixing an implementation bug. There is no reason to override whitespace on a simpla-text element. Some of the others, like break-word, sure. But whitespace just fixes cross browser bugs and it's a good thing it's forced

Yup that's fair. Lets move to integrating all of these styles in the behaviour, rather than asking for the elements to do it. Will aim for an injected stylesheet, but fallback to inline.

Adding white-space: pre-wrap to block level host elements added a bad regression with the box model, so now all simpla-text (and simpla-article) have mega spacing that you can't get rid of, breaking any layout they were used in. I'll roll back and publish a new version for simpla-text. Did you test it in chrome etc?

And that makes this a breaking bug again

Now I see what you're talking about, I did notice the big padding but didn't realise what it meant / that it was a regression. Sorry - should have realised and caught that before pushing.
So given that white-space: pre-wrap (or pre the only two that preserve whitespace) cause this nasty bug, we can't use a CSS fix - checked and it doesn't matter how it's applied.

Ok so the issue was the Shadow Root had spaces either side of the <content></content> tags, which added the extra spaces. Given what we want to do here, it'll probably take some time, so I'll re-apply the pre-wrap styles to text / article, but remove the whitespace around <content></content>

So I attempted a purely JS solution to this - Essentially just replacing trailing spaces with non-breaking spaces (behavior in Chrome / Safari) - but it ended up with way too many edge cases. Maybe a solution in future if CSS is a really big problem, but not worth it.

Ok so another snag, pre-wrap works fine in simpla-text, but it doesn't in simpla-article because article includes a clearfix. The content: ''; in ::after rule seems to cause pre-wrap to add a hunk down beneath it.

@seaneking could you pull down the ff-nbsp branch and give that a test run? It seems to fix it, barring when you repeatedly enter spaces, but can work on that to fix it - it's not yet the same as Chrome's behavior.

So given that white-space: pre-wrap (or pre the only two that preserve whitespace) cause this nasty bug, we can't use a CSS fix - checked and it doesn't matter how it's applied.

What? Applying pre-wrap to the individual elements (ie simpla-article p, etc) fixes the issue perfectly on Firefox and doesn't cause any layout issues. Did you check that? The problem is only on hosts with block children.

 Should have taken more time in reading over your assessment. Alright I'll work on getting a stylesheet injection thing going tomorrow - could you list out the exact styles that'll need to be applied? Rather not attempt a generalised plugin to do this straight away.

Sure thang - for just this issue it'd be just white-space: pre-wrap on block leaf nodes (so just p and headings for now I think, since blockquote and list items wrap).

Then a conditional to apply it to the host only if it's an inline editor (and not inject the other styles).
And in that case maybe open a new issue for conditional stylesheets based on plugins available (including placeholder).
We would want:

This hack if not inline, for p and headings if available
Host hack if inline
List hack if lists available (until issue properly fixed)
Img styles from article if image available
Placeholder styles if placeholder set

Also should move the issue on simpla-text about unecessary stylesheets here, to be looked at as an enhancement after ^ is done.

So see attached PR. Worth noting that it appears firefox adds   instead of regular spaces for inline editor i.e. when inserting directly into the host rather than children, so shouldn't need any hack for inline styles.

Worth noting that it appears firefox adds   instead of regular spaces for inline editor

Of course it does 🙄


Improve using this library as a cmake subproject

This PR improves including this library as a cmake subproject. It allows using a provided cmake subproject SFML (checked out as a submodule alongside STP). It also allows to compile and link it as a static lib. Finally it fixes some issue with building in cygwin as a subproject.

Thanks for the contribution :smile:

np :)


BR: Port to lib/env

fixes #2223
fixes #2242

This change is

go/border/main.go, line 71 at r2 (raw file):
Previously, Oncilla wrote…
CleanupLog calls log.LogPanicAndExit() internally

Whoops. Stale comment.
Done.


Don't run Github Actions jobs on forks and down-stream repos

We should limit Github-Actions, esp the sonar, codecov and smoketests to only run on apache/cloudstack repo and not in any of its forks or downstream repos. (some basic jobs such as build and UI checks etc can still run).

@DaanHoogland can you help fix this? probably needs some kind of if checks on the workflow yamls?


lifecycle methods

We currently don't accept any custom version command, and we should. I think it makes sense that if version is just set to true, it uses the built in bump, and if it is a string then spawn the command and run it.
We should also add a pre and post option for each of the version and publish commands. This will let us do things such as run a build in each package that has a release., or add a git tag on success (postpublish).

Second half of this is complete in #58. Needed it for those git tags to tag the action.

I am going to close this one. Originally we suspected that version might want to be extended to support any custom commands, but the value of this has been diminished by the need to do dependency-related bumps. It is possible that if we can round trip every type of package file, that we don't even need a version command in the config.


Vim9: heredoc start may be recognized in string

Problem:  Vim9: heredoc start may be recognized in string.
Solution: Don't skip to closing bracket for invalid list assignment.

thanks!


Gated stores as IFs rewrite with beam fix

ref https://github.com/tinygrad/tinygrad/pull/5976 & https://github.com/tinygrad/tinygrad/pull/6376
Running BEAM=4 NV=1 HALF=1 IGNORE_BEAM_CACHE=1 DEBUG=2 python3 extra/gemm/simple_matmul.py:
this branch:
master:

so let's do: 6413's fix and the test_uops_stats fix in a different PR, then merge the final rewrite rules.


SAK-31402: Provide finer grained morpheus style variables

https://jira.sakaiproject.org/browse/SAK-31402

Great work indeed :+1:


Update writeup_template.md

Should not be committed in as this contains actual answers.  Why you folks are trying to submit pull requests is beyond me.

Though we are a little delayed in responding, this PR contains your personal work that cannot be added to Udacity's repository (starter-code).
Although, feel free to suggest an update to the starter code.
Happy Learning
Udacity


⚠ Processors has degraded performance

In a9957e3, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 81 ms

Resolved: Processors performance has improved in 3cb6968.


Allow mixing GPU and non-GPU partitions

Submission Checklist
Following blueprint:
      - id: debug_nodeset
        source: community/modules/compute/schedmd-slurm-gcp-v6-nodeset
        use: [network]
        settings:
          machine_type: n2d-standard-2

      - id: debug_nodeset2
        source: community/modules/compute/schedmd-slurm-gcp-v6-nodeset
        use: [network]
        settings:
          machine_type: g2-standard-8

      - id: debug_partition
        source: community/modules/compute/schedmd-slurm-gcp-v6-partition
        use:
          - debug_nodeset
          - debug_nodeset2
        settings:
          partition_name: debug

      - id: slurm_controller
        source: community/modules/scheduler/schedmd-slurm-gcp-v6-controller
        use:
          - network
          - debug_partition

Will throw an error:
╷
│ Error: Invalid value for input variable
│
│   on main.tf line 124, in module "debug_partition":
│  124:   nodeset        = flatten([module.debug_nodeset2.nodeset, flatten([module.debug_nodeset.nodeset])])
│
│ The given value is not suitable for module.debug_partition.var.nodeset declared at modules/embedded/community/modules/compute/schedmd-slurm-gcp-v6-partition/variables.tf:52,1-19: element types must all match for conversion to list.

This can be worked around by providing on non-GPU partitions:
      - id: debug_nodeset
        source: community/modules/compute/schedmd-slurm-gcp-v6-nodeset
        use: [network]
        settings:
          machine_type: n2d-standard-2
          guest_accelerator:
            - type: ""
              count: 0

With this change, one can mix gpu and non-gpu nodestes in one partition without extra steps.
This change was not tested with GKE or compute-vm

We can't take this approach as it pollutes template and affect bulkInsert requests.

Please feel free to re-open PR.


Implement the Python standard library

Python has a sizeable standard library. It is this standard library the provides a lot of the power of Python as a language.
Much of this standard library is implemented in Python, and could be converted into a Jar file using VOC. VOC's build system should be modified to perform this conversion.
Other parts of the standard library are implemented in C, and will require re-implementation in Java.
Even if there is a pure-python implementation, it may be desirable to re-implement a standard module in Java for efficiency purposes.
This may be dependent on completion of #36 and #38, as you won't be able to use the standard library unless the builtin data types are available.

Stubs of the sys and time modules already exist; they can be used as a template when adding new modules.

See also Ouroborous, a related project to develop a standalone, pure python version of the standard library. Ideally, it should be possible to use Ouroboros to generate the builtins and standard library.

@freakboy3742 I would like to work in the issue

@souravsingh Fantastic! Do you need any pointers or suggestions, or do you feel confident tackling this on your own?

@freakboy3742 I just wanted to ask- We have to create Python library similar to Ouroboros, right?

Ouroboros aims to be a full, pure-python version of the Python standard library (or, as much as is plausible), with a clearly delineated interface where platform-specific modules are required (e.g., to make system calls).
I know this ticket is on VOC; but the ideal contribution would be to improve Ouroboros, because then any Python implementation can use it. The VOC component will then be just the Java implementation of the system native portions necessary to support Ouroboros on Java.
At some point, we'll need to find a way to integrate Ouroboros into the VOC build chain.
So - as for what to do? Pick a standard library module that doesn't currently have an implementation in Ouroboros, and implement it.
Two places worth starting: datetime and httplib. Both of these have pure Python components; but they also have native components. Make sure the full library is available.
The code that is in Ouroboros is using Python 3.4 as the reference implementation, so try to keep the APIs aligned with that version.

I would like to attempt to solve this issue.

hey @freakboy3742 , is this issue still open?

@abhinavralhan Yes - there's still plenty to implement in the standard library.

@freakboy3742 I would totally like to help. This would be my first contribution. Could you give me some pointers to get started?

@abhinavralhan If this is your first contribution, I'd suggest starting somewhere else that will be a little easier. Our getting started guide for first time contributors lays out a suggested first contribution; once you've done that first exercise, more advanced issues like this one will make a lot more sense.

Hi @freakboy3742,
Is this bug assigned to anyone ?
thanks,

@hemanthsavasere This isn't a bug that is going to be assigned to a single person - there's a huge amount of work that needs to be done. This ticket is just for coordination purposes, so we don't end up with multiple people working on the same part.
So - pick a part of the standard library (i.e., a specific module, like collections or httplib), drop a comment here that says what you're doing, and implement it!

Would like to get started. Where to start from?

Hi , @freakboy3742 I have started working on time library, as most of it is not implemented.
After completing one of the function, I will put a Pull Request(For you to review).
By the way, I am a First Time Contribute.
Do I need to put an comment on #36 also, as requested in the starting guide.

I definitely want to help. Checking the guide :)

Hi @freakboy3742 I am Software Engineering student with a class assignment in which I have to contribute to an open source project. I am interested in contributing to VOC. I went through the tutorial and first timer guides. I have some experience with Python and Java.
I am looking to get started with some functions in the time.java library: gmtime(), localtime(), mktime() and strptime(). I am planning for 3-4 hours of design, development, testing and rework for each function. I wanted to get you opinion on my plan given the complexity of these functions.
Thank you

@amaarahj It's almost impossible for me to judge. I don't know you, your skills, or your experience level; as such, it's impossible for me to judge whether your estimates will be accurate.
However, the four methods you've proposed are reasonably standalone, and sound like a reasonable target for a short university assignment.

@gs-niteesh Absolutely - go right ahead!

Just having few issues. Do we have an exec function? and there are few functions like iskeyword which need to be implemented should I just continue with the implementation of namedtuple or implement the required one's?

@gs-niteesh Yes - there are a lot of features missing. That's the point - there's a lot of work that needs to be done.
NamedTuple in particular is a complex piece of code - and its native implementation in Python is a bit of a hack (as it is based on exec). It may turn out to be easier to implement in Java directly, rather than trying to execute the Python implementation.

Sorry for asking so many questions. But I don't understand what do you mean by implement it in java directly, can you explain it in brief.

Do you have any video or doc that explains VOC in detail. In detail I mean the internals and how things work.

Hi - I am interested in working on this issue but i just wanted to clarify it is still open?

@freakboy3742, I would also be interesting in contributing, it is my first time. would love to know where i can start. let me know what is still open for first-timers.
Thanks

I would love to contribute. However, I am a  first timer so I would love to get some advice on how to go about starting this!

@aritramullick At this point, I'd advise against starting with VOC as a project. We're in the process of removing it from use as part of our stack. If you're looking for project to contribute, I'd recommend Briefcase. Run through the BeeWare Tutorial to see Briefcase in action, then see if there's a ticket in the Briefcase ticket tracker that appeals to you.


system: TileEntity is already defined in that package

[PREINITIALIZATION][CLIENT][ERROR] system: TileEntity is already defined in that package
ContentTweaker-1.12.2-4.9.0
base-1.12.2-3.11.0
CraftTweaker2-1.12-4.1.13

I have the same text in chat when login in the world.

[CHAT] ERROR: system: TileEntity is already defined in that package

Note for Sky/devs:
api/CTObjects/TE/IMCTE and MCTE both have the signature of "... .TileEntity", hence the error.
Also, some types in Modules/Vanilla/TileEntity aren't properly registered, check that all the classes have the appropriate @ZenClass and @ZenRegister annotations ^^

Well done.


Future plans?

Now that the last functional commit is years back and the few pull requests are just hanging, does this mean the Apache v3 port has fallen out of grace? Is everybody using nginx?

I've come to the conclusion that ModSecurity-Apache isn't ready for production use. Its behaviour is different to ModSecurity 2.9.3 and seems to not work 100% yet. I feel like https://github.com/SpiderLabs/ModSecurity-apache/issues/77#issuecomment-714460096 sums it up perfectly, it's not ready for a release, no matter how many guides on the internet seem to suggest it is. I look forward to development continuing and a stable release being made in the future, for now, I'm stuck with ModSecurity 2.9.3 if I want to use it with Apache.

Yes, me too.
In fact, I am stucking at much of false-positive @ v2.9.3 and suffer debug.
In 3 years, can not know status of Modsecurity v3 @ apache, on-going/hibernate/discontinue??
I assume it was discontinue :(
I will give up Modsecurity nearly :(

Apologies to those in the community feeling vexed about slow/no responses in this repo's issues.  (Personally, since joining the team, it simply didn't occur to me to register for notifications for this repo.)
The citation in the second posting here is accurate.  ModSecurity-Apache is not considered production-ready.  Much of the functionality works correctly but enough does not, so v2.9.x is still the recommended choice for use with Apache HTTP Server.
Note that just because ModSecurity v2.9.x has a lower number does not mean that it is less good than libModSecurity (aka v3).
@Neko-Chang-Taiwan :  I'm not sure what problems you are experiencing with v2.9.  I couldn't find any open issues in the ModSecurity issue.  Keep in mind that many types of false positives have more to do with the rules you are using as opposed to what the engine is doing.  If there is a something the ModSecurity engine is doing that you believe is incorrect, or you believe could benefit from an enhancement, feel free to raise it on the ModSecurity repo.

It's been a while since last update on this project and the note says it's not ready for production use. Do you know if there are any plans for a production release?

@iplparm ,
There are no current plans for additional work on this connector over the coming months.
The recommended version for use with Apache continues to be ModSecurity v2.9.x.


The Order of @TaskAction

In a nutshell, the annotation @TaskAction doesn't guarantee the order of actions or indicate that it should be used only one time per task.
Expected Behavior
Some suggestions list below:

Provide a default sorting for those action methods that added with @TaskAction, ex: Alphabetical Order.
Optimize the API doc of @TaskAction and relevant user guides, to explicitly indicate what is the best practice for using this annotation.

https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/TaskAction.html
https://docs.gradle.org/current/userguide/custom_tasks.html
https://guides.gradle.org/writing-gradle-tasks/

Provide an annotation like @TaskAction(int priority) to support more flexible usage.

Current Behavior
Check the class DefaultTaskClassInfoStore and method createTaskClassInfo(Class<? extends Task> type), we can find how @TaskAction methods added to the actions list.
public class DefaultTaskClassInfoStore implements TaskClassInfoStore {
      ...
      private TaskClassInfo createTaskClassInfo(Class<? extends Task> type) {
        boolean cacheable = type.isAnnotationPresent(CacheableTask.class);
        boolean incremental = false;
        Map<String, Class<?>> processedMethods = Maps.newHashMap();
        ImmutableList.Builder<TaskActionFactory> taskActionFactoriesBuilder = ImmutableList.builder();
        for (Class current = type; current != null; current = current.getSuperclass()) {
            for (Method method : current.getDeclaredMethods()) {

                // The order of actions depends on what `getDeclaredMethods()` returns here,
                // however, JDK doesn't guarantee the order of the returning array from this method:
                //
                // > The elements in the returned array are not sorted and are not in any particular order.
                //
                // Thus if you have multiple `@TaskAction` methods, it will be very confusing.

                TaskActionFactory taskActionFactory = createTaskAction(type, method, processedMethods);
                if (taskActionFactory == null) {
                    continue;
                }
                if (taskActionFactory instanceof IncrementalTaskActionFactory) {
                    if (incremental) {
                        throw new GradleException(String.format("Cannot have multiple @TaskAction methods accepting an %s parameter.", IncrementalTaskInputs.class.getSimpleName()));
                    }
                    incremental = true;
                }
                taskActionFactoriesBuilder.add(taskActionFactory);
            }
        }

        return new TaskClassInfo(incremental, taskActionFactoriesBuilder.build(), cacheable);
      }

Context
I created an artifact uploading task with multiple assets, I just added more than one @TaskAction on several methods to complete the demonstrate. When I tried to improve it (to define the order and do error handler, etc.), I found that I can not use them anymore. I quite understood I should use "doLast{}" or annotate only one method and place all logic inside without using multiple @TaskAction. But I think it was because I'm writing something in buildSrc directory that I don't want to reuse them in any other project, it makes me be a lazy boy to do all things together in the task. That's why I had an idea to take more than one @TaskAction.
I don't know if Gradle should improve such this small issue, but it is quite an essential API, it may let people feel confused when they first encounter Gradle.
Steps to Reproduce (for bugs)
N/A.
Your Environment
Gradle 5.0 (But I suppose it exists since the beginning)

+1 for this.
Documentation on incremental tasks:

A task may only contain a single incremental task action

makes me to wonder: is it legal to have several non-incremental task actions, and how would they be ordered?

We should deprecate having more than one @TaskAction on a task class and remove it in the end.

Let's keep this open.


workbox-webpack-plugin > workbox-build ><EMAIL_ADDRESS>

Welcome! Please use this template for reporting bugs or requesting features. For questions about using Workbox, the best place to ask is Stack Overflow, tagged with [workbox]: https://stackoverflow.com/questions/ask?tags=workbox
Library Affected:
workbox-sw, workbox-build, etc.
Browser & Platform:
E.g. Google Chrome v51.0.1 for Android, or "all browsers".
Issue or Feature Request Description:
Your request here.
When reporting bugs, please include relevant JavaScript Console logs and links to public URLs at which the issue could be reproduced.

duplicate #3200


Update 1.20.2

I detected satin maven address changed, here is a notice.
https://github.com/Ladysnake/Satin

also update all deps compatable with 1.20.1
in-game tested, 100% works fine!

Thank you very much!


Invalid Actor / Failed to update tailnet settings

Describe the bug
Running a terraform apply the last 2-3x days generates an initial error of -
Error: Failed to update tailnet settings

  with tailscale_tailnet_settings.tailnet_settings,
  on tailnet-settings.tf line 1, in resource "tailscale_tailnet_settings" "tailnet_settings":
   1: resource "tailscale_tailnet_settings" "tailnet_settings" {

invalid actor (500)

This error does not occur during a plan.
To Reproduce
Run terraform apply.
Expected behaviour
The terraform to apply.
Desktop (please complete the following information):

OS: GitHub Actions
Terraform Version: latest as of Sep 28th
Provider Version latest as of Sep 28th (0.17.1)

Additional context
Full error with debug turned on -
2024-09-28T15:54:46.676Z [INFO]  Starting apply for tailscale_tailnet_settings.tailnet_settings
2024-09-28T15:54:46.677Z [DEBUG] tailscale_tailnet_settings.tailnet_settings: applying the planned Create change
Error: -28T15:54:47.410Z [ERROR] provider.terraform-provider-tailscale_v0.17.1: Response contains error diagnostic: tf_provider_addr=provider tf_resource_type=tailscale_tailnet_settings tf_rpc=ApplyResourceChange @module=sdk.proto diagnostic_detail="invalid actor (500)" diagnostic_severity=ERROR diagnostic_summary="Failed to update tailnet settings" tf_proto_version=5.6 tf_req_id=ed8301c8-6318-abff-d77d-6aef24ba97dd @caller=github.com/hashicorp/terraform-plugin-go@v0.23.0/tfprotov5/internal/diag/diagnostics.go:58 timestamp=2024-09-28T15:54:47.409Z
2024-09-28T15:54:47.415Z [DEBUG] State storage *statemgr.Filesystem declined to persist a state snapshot
Error: -28T15:54:47.415Z [ERROR] vertex "tailscale_tailnet_settings.tailnet_settings" error: Failed to update tailnet settings

Error: Failed to update tailnet settings

  with tailscale_tailnet_settings.tailnet_settings,
  on tailnet-settings.tf line 1, in resource "tailscale_tailnet_settings" "tailnet_settings":
   1: resource "tailscale_tailnet_settings" "tailnet_settings" {

invalid actor (500)
2024-09-28T15:54:47.582Z [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-09-28T15:54:47.583Z [INFO]  provider: plugin process exited: plugin=.terraform/providers/registry.terraform.io/tailscale/tailscale/0.17.1/linux_amd64/terraform-provider-tailscale_v0.17.1 id=1630
2024-09-28T15:54:47.583Z [DEBUG] provider: plugin exited

Full set of TF files being used -
provider.tf
terraform {
  required_providers {
    tailscale = {
      source  = "tailscale/tailscale"
    }
  }
}

provider "tailscale" {
  oauth_client_id = var.tailscale_oauth_client_id
  oauth_client_secret = var.tailscale_oauth_client_secret
  tailnet = var.tailscale_tailnet
}

tailnet-settings.tf
resource "tailscale_tailnet_settings" "tailnet_settings" {
  devices_approval_on                         = true
  devices_auto_updates_on                     = true
  devices_key_duration_days                   = 180
  users_approval_on                           = true
  users_role_allowed_to_join_external_tailnet = "member"
  posture_identity_collection_on              = false
}

Checks on the OAuth permissions have been tested, to no effect.
Only notable change to the TS side of things is me flipping the account from the business trial, to just a normal personal account.

Thank you for the detailed report @boomam! This looks to have been an issue with OAuth for the underlying endpoint in the control plane that should now be fixed.

Great! I will test this evening and report back!

I can confirm that the issue is now resolved.
Thanks for getting it fixed!


fix: adapt vercel cleanurls

quartz recommend use cleanurls=true in vercel deploy.
but cleanurls will cause current location is 'https://ip/tags' and not 'https://ip/tags/'
so the url which is './tag1' will convert to 'https://ip/tag1' , this is 404 error

emmm…something wrong with the pr?

this breaks urls for all other hosting, Vercel has abnormal URL handling behaviour

sorry, why this pr will break other hosting, can you explain it ?(my knowledge of front-end is less)
i try it in my local server, and it work well.

See this table: https://github.com/slorber/trailing-slash-guide?tab=readme-ov-file#summary
Vercel's redirect behaviour is different from every other provider

ok, i know this (Vercel's redirect behaviour is different from every other provider),
but this pr why break other hosting?
i just change from ./tag1 to ../tags/tag1.

because not all Quartz pages are hosted at the root (e.g. you can host on <username>.github.com/quartz so this can cause a redirect to the wrong page

let me try it to reproduce the issues, thanks

emmm, i try it in other host (etc. cloudflare and github), it works well
like the below video, i deploy a pages in github, the url is https://no365.github.io/quartz/tags/
https://github.com/jackyzha0/quartz/assets/19152476/650abe67-9b70-446d-a878-cd03c0ef5961
Perhaps I have made an error in one of my actions?

Oh I see, I misread your change. I didn't see that you added the /tag. I'll reopen and merge it

Oh, thanks
some knowledge like 'https://github.com/slorber/trailing-slash-guide?tab=readme-ov-file#summary' is usable.
hope Quartz continues to thrive and flourish!


Initial Commit

This is the initial commit for the rosetta-sdk-go repository. This will be released as version 0.0.1.

Review Error for almindor @ 2020-04-01 16:18:58 UTC
User failed mfa authentication, see go/mfa-help


9.27.0 Docker won't start on Aeotec Z-Stick Gen5+

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Z-Wave JS UI version
9.27.0.f3c4ac5
ZwaveJS version
14.3.1
Describe the bug
After upgrading to the 9.27.0 docker image, it is failing to start.  Rebooted the box, unplugged/replugged the dongle, nothing works
To Reproduce
Upgrade from 9.26.0 -> 9.27.0
Expected behavior
it starts up.
Additional context
Downgrading to 9.26.0 and it starts right up.
Log output isn't super helpful, even on "Silly"
2024-11-12T18:49:30.260Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2024-11-12T18:49:30.260Z DRIVER   version 14.3.1
2024-11-12T18:49:30.261Z DRIVER
2024-11-12T18:49:30.261Z DRIVER   starting driver...
2024-11-12T18:49:30.261Z DRIVER   opening serial port /dev/zwave
2024-11-12T18:49:30.263Z DRIVER   serial port opened
2024-11-12T18:49:30.264Z SERIAL » 0x15                                                                 (1 bytes)
2024-11-12T18:49:31.266Z DRIVER   loading configuration...
2024-11-12T18:49:31.269Z CONFIG   Using external configuration dir /usr/src/app/store/.config-db
2024-11-12T18:49:31.270Z CONFIG   version 14.3.1
2024-11-12T18:49:31.767Z DRIVER   beginning interview...
2024-11-12T18:49:31.768Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
                                  1 registered
2024-11-12T18:49:31.768Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
                                  1 registered
2024-11-12T18:49:31.769Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
                                  1 registered
2024-11-12T18:49:31.769Z DRIVER   added request handler for SetLearnMode (0x50)...
                                  1 registered
2024-11-12T18:49:31.769Z CNTRLR   querying Serial API capabilities...
2024-11-12T18:49:31.772Z SERIAL » 0x01030007fb                                                         (5 bytes)
2024-11-12T18:49:31.773Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-11-12T18:49:32.777Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2024-11-12T18:49:32.879Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-11-12T18:49:32.881Z SERIAL » 0x01030007fb                                                         (5 bytes)
2024-11-12T18:49:33.883Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2024-11-12T18:49:34.985Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-11-12T18:49:34.987Z SERIAL » 0x01030007fb                                                         (5 bytes)
2024-11-12T18:49:35.991Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
                                  from the controller (ZW0200)
                                      at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D
                                  river.ts:6071:23)
                                      at ZWaveController2.queryCapabilities (/usr/src/app/node_modules/zwave-js/
                                  src/lib/controller/Controller.ts:1144:37)
                                      at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js
                                  /src/lib/driver/Driver.ts:1677:46)
                                      at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive
                                  r/Driver.ts:1478:16)
2024-11-12T18:49:35.993Z DRIVER   destroying driver instance...
2024-11-12T18:49:35.994Z DRIVER   all queues idle
2024-11-12T18:49:36.028Z DRIVER   driver instance destroyed

I get the same error on 9.27:
2024-11-12T18:59:29.266Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
                                  from the controller (ZW0200)
                                      at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D
                                  river.ts:6071:23)
                                      at ZWaveController2.queryCapabilities (/usr/src/app/node_modules/zwave-js/
                                  src/lib/controller/Controller.ts:1144:37)
                                      at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js
                                  /src/lib/driver/Driver.ts:1677:46)
                                      at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1478:16)
2024-11-12T18:59:29.268Z DRIVER   destroying driver instance...

But it goes away and things work as expected when I go back to 9.26

Same issue on USB STICK ZOOZ ZST10 S 700:
2024-11-12T19:11:40.114Z DRIVER   Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK                                    from the controller (ZW0200)                                       at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D                                   river.ts:6071:23)                                       at ZWaveController2.queryCapabilities (/usr/src/app/node_modules/zwave-js/                                   src/lib/controller/Controller.ts:1144:37)                                       at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js                                   /src/lib/driver/Driver.ts:1677:46)                                       at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive                                   r/Driver.ts:1478:16)

Same here, and I needed to roll-back to restore working ZWave at home.
This is what I have as the error message in the UI:

Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:6071:23) at ZWaveController2.queryCapabilities /usr/src/app/node_modules/zwave-js/src/lib/controller/Controller.ts: 1144:37) at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1677:46) at Immediate. (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1478:16) (ZWO100)
Error: Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:6071:23) at ZWaveController2.queryCapabilities (/usr/src/app/node_modules/zwave js/src/lib/controller/Controller.ts:1144:37) at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1677:46) at Immediate. (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1478:16) (ZW0100)

Same error here... reverted to zwave2mqtt:9.26.0 and my system is back up

Also pulled sha256:6d36abbe92f950a6324cdfcc88e6a4fae7d08b91eca90454b5887c1885a399c2 since it was newer, did not work. Rolled back to 9.26.

Same for me. Same situation . Docker under Unraid. Rolled back to 9.26.0 up and running again

Same here. Reverting to 9.26.0 and everything is working back as before. SiliconLab / Usb Controller / 700/800 Series : https://devices.zwave-js.io/?jumpTo=0x0000:0x0004:0x0004:0.0

I think this should get fixed by https://github.com/zwave-js/zwave-js-ui/pull/4000 - at least I could access my stick in Docker on that branch.

9.27.1 should fix this

Can confirm this fixed the problem on my end. Thank you.

9.27.1 should fix this

Works for me, thanks for the quick turnaround

9.27.1 should fix this

So fast,
Thanks for everything 🙇

9.27.1 worked for me!
Thanks!


Verbose Error Logs

If the user does not have proper permissions to clone the GitHub repository, verbose error logs are generated when attempting to run the enumerate command

Thanks for the bug report! To make sure I understand the behavior correctly:
Are you running this with a token that does not have clone privileges?
OR
Are you running this with an appropriately scoped token, but that user does not have read access to the repository?

Actually, in this case, the user was unable to clone the repository due to SSH cert authentication requirements.

@AdnaneKhan It looks like the source of these messages is that we set the root logging level to DEBUG.
We have this in a few places, but we might want to rethink how we are using the logging package.
https://github.com/praetorian-inc/gato/blob/b347c55a9142944b4d9cd362ed01daeebb3938ab/gato/enumerate/enumerate.py#L19

DEBUG root level is no longer set.


Feature/switch hiking direction

We can now use a button to switch the hiking direction from within the route_preview page.
Furthermore a starting/ending Point is drawn onto the map.
Showing the hiking direction is done using green (start) and red (end) blurred lines on top of the path. This may be improved later on. Any ideas are very welcome. At the moment I think it will do the job just fine.

Changes have been applied. Doing the merge now


Feat: Scraping data from IPL Auctions

Describe the feature
I want to scrape data from Tata IPL Website to show all the auction stats of IPL 2024
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

@nikhil25803  could you please assign the issue to me


Generation should abort when manifest file cannot be written

Bug Report
Steps to Reproduce:

Run the generator in violation mode providing a missing output path

Expected Result:
Generation should abort early, neither data files nor manifest are created
Actual Result:
Message is printed stating that manifest file could not be created, generation continues and fails when writing to the first output file.

Investigate if this is still an issue since the #566 changes have been merged


Dependabot is not running

Dependabot has worked before with Actions, it has made #21 and #26, but it never seems to have picked up on Composer even when updates are available. My only guess would be the "prefer stable" i have set, but if i run composer update, it will update them just fine.

It seems the actions one is running fine, but the Composer one just does not seem to understand it needs to actually make a PR for the update. Not sure why. I will just leave it at this for now.


fix: build edr_napi with test profile when running hardhat tests

For some reason, stack traces test don't work when edr_napi is built with the debug profile. Since we were using the release profile before anyway, I think we can just continue using it to get this fixed.

Could you explain a bit? The tests in general seem to be working as per latest CI run: https://github.com/NomicFoundation/edr/actions/runs/10503186671/job/29096060736.
Do you mean that this may help catch the spurious errors in CI or something different?

For some reason, stack traces test don't work when edr_napi is built with the debug profile. Since we were using the release profile before anyway, I think we can just continue using it to get this fixed.

This is just in the feat/solidity-tests branch: https://github.com/NomicFoundation/edr/pull/524

Yes, what Agost said. This is something that broke in the solidity tests feature branch. main is working fine.

Could you explain a bit? The tests in general seem to be working as per latest CI run: https://github.com/NomicFoundation/edr/actions/runs/10503186671/job/29096060736.
Do you mean that this may help catch the spurious errors in CI or something different?

This is just in the feat/solidity-tests branch: #524

Ah, didn't see that. Thanks and sorry for the noise!