testng executes the @BeforeClass and every @Test at a different thread

TestNG Version
6.10
Expected behavior
The whole <test>name</test> should run on one thread
Actual behavior
each @Test inside the class is executed on a different thread
Is the issue reproductible on runner?

[ ] Shell
[ ] Maven
[ ] Gradle
[ ] Ant
[x] Eclipse
[ ] IntelliJ
[ ] NetBeans

Test case sample
So this is the test class. 1 @BeforeClass and 2 @Test:
public class SpacerDesignTest extends SpacerTestLogic {

	@BeforeClass
	public void init(){
		createSite();
		super.init();
		addWidgetByAPI(WidgetType.Spacer);
	}

	@Test()
	public void changeSpacerHeight(){
		String height = "150px";
		openDesignWindow();
		changeWidgetHeight(height);
		closeEditWindow();
		Assert.assertEquals(getWidgetHeightFromEmulator(), height, "button width shoud be " + height + " but it's " + getWidgetHeightFromEmulator());
	}

	@Test()
	public void changeSpacerHeight1(){
		String height = "150px";
		openDesignWindow();
		changeWidgetHeight(height);
		closeEditWindow();
		Assert.assertEquals(getWidgetHeightFromEmulator(), height, "button width shoud be " + height + " but it's " + getWidgetHeightFromEmulator());
	}

}

This is the xml with 3 <test> each with the previous class:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="D1 Tests" verbose="0" parallel="tests" thread-count="10" time-out="7200000">

	<listeners>
    	<listener class-name="com.duda.webdriver.core.SuiteListener" />
    	<listener class-name="com.duda.webdriver.core.TestNGListener" />
	</listeners>

	 <test name="test1">
  	<classes>
  		<class name="com.duda.webdriver.elduderino.tests.widgets.spacer.SpacerDesignTest"></class>
  	</classes>
  	</test>

  	<test name="test2">
  	<classes>
  		<class name="com.duda.webdriver.elduderino.tests.widgets.spacer.SpacerDesignTest"></class>
  	</classes>
  	</test>

  	<test name="test3">
  	<classes>
  		<class name="com.duda.webdriver.elduderino.tests.widgets.spacer.SpacerDesignTest"></class>
  	</classes>
  	</test>
</suite>

This is the log i created with the created threads in every @Test.
As you can see there are more threads created than expected by this example:
Thread is: 1
Thread is: 1
Thread is: 1
Thread is: 1
Thread is: 1
Thread is: 14
Thread is: 14
Thread is: 15
Thread is: 15
Thread is: 16
Thread is: 16
Thread is: 16
Thread is: 14
Thread is: 15
Thread is: 16
Thread is: 14
Thread is: 15
Thread is: 15
Thread is: 14
Thread is: 16
Thread is: 14
Thread is: 16
Thread is: 15
Thread is: 16
Thread is: 15
Thread is: 14
Thread is: 14
Thread is: 14
Thread is: 14
Thread is: 16
Thread is: 16
Thread is: 15
Thread is: 16
Thread is: 15
Thread is: 15
Thread is: 15
Thread is: 15
Thread is: 29
Thread is: 29
Thread is: 29
Thread is: 15
Thread is: 15
Thread is: 15
Thread is: 15
Thread is: 30
Thread is: 30
Thread is: 30
Thread is: 15
Thread is: 15
Thread is: 15
Thread is: 15
Thread is: 14
Thread is: 15
Thread is: 15
Thread is: 14
Thread is: 31
Thread is: 31
Thread is: 31
Thread is: 14
Thread is: 14
Thread is: 14
Thread is: 14
Thread is: 32
Thread is: 32
Thread is: 32
Thread is: 14
Thread is: 14
Thread is: 14
Thread is: 14
Thread is: 16
Thread is: 16
Thread is: 33
Thread is: 33
Thread is: 14
Thread is: 14
Thread is: 33
Thread is: 16
Thread is: 16
Thread is: 16
Thread is: 16
Thread is: 34
Thread is: 34
Thread is: 34
Thread is: 16
Thread is: 16
Thread is: 16
Thread is: 16
Thread is: 16
Thread is: 16
Thread is: 1
Thread is: 1
Thread is: 1
Thread is: 1
Thread is: 1
Thread is: 1

Duplicate of #1185
Feel free to reopen if you think it is a different issue.

Comment from #1335

The issue has nothing to do with dependsOn, it happens with the example test I've attached to issue #1333 And there is no dependsOn there

Ok. Do you think it is a duplicate of #1035 in that case?

@juherr
My case isn't dealing with dependsOn nor the @BeforeClass is not the issue.
Every @Test in the same class gets executed in a different Thread than the previous @Test before it.
In other words, every @Test creates a new thread id.
You can see it in the thread numberings i added to my sample.
This happend to me only after updating my TestNG version from 6.9.10 to 6.10.
It affects my logging mechanisms because it relies on every class is a single thread, on all of its @Tests
I think when in the testng.xml I specify  parallel="tests" not every @Test should create a new thread.

@juherr
Ok, so i found the source to this behavior.
Review this example:
public class Test{

	@BeforeClass
	public void init(){
		System.out.println(Thread.currentThread().getId());
	}

	@Test
	public void test1(){
		System.out.println(Thread.currentThread().getId());
	}

	@Test
	public void test2(){
		System.out.println(Thread.currentThread().getId());
	}

}

<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="D1 Tests" verbose="0" parallel="tests" thread-count="10" time-out="7200000">

	<listeners>
    	<listener class-name="com.duda.webdriver.core.SuiteListener" />
    	<listener class-name="com.duda.webdriver.core.TestNGListener" />
	</listeners>

	 <test name="test1">
  	<classes>
  		<class name="Test"></class>
  	</classes>
  	</test>

  	<test name="test2">
  	<classes>
  		<class name="Test"></class>
  	</classes>
  	</test>

  	<test name="test3">
  	<classes>
  		<class name="Test"></class>
  	</classes>
  	</test>
</suite>

I get a different thread id for every method although each  tag should be 1 thread.
The reason is the time-out="7200000". When I remove this parameter the tests exectute as expected.
Very strange behavior. Any idea why this happens?

@yardening2 Sure! The timeout feature is done by a thread pool on its own threads.
I'm pretty sure you issue, or a similar one, is already registered: https://github.com/cbeust/testng/issues?q=is%3Aopen+is%3Aissue+label%3A"Feature%3A+timeout"

Hi,
I am a newbie here.  I have a related question.
In my case, the @BeforeClass method is executed before every test in the class.  The testNG xml file looks like below.  I am trying testing on one device for now - but plan is to test on multiple devices at the same time.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite thread-count="2" configfailurepolicy="continue" name="Parallel Mobile Tests" parallel="tests" preserve-order="true">
  <listeners>
    <listener class-name="listeners.TestListener"/>
    <listener class-name="listeners.CustomReportListener"/>
  </listeners>
  <test name="IPHONE_6SPLUS : Parallel Tests">
    <parameter name="deviceOS" value="iOS"/>
    <parameter name="device" value="IPHONE_6SPLUS"/>
    <classes>
      <!-- <class name="tests.Install"/> -->
      <class name="tests.Class01"/>
      <class name="tests.Class02"/>
      <class name="tests.Class03"/>
      <class name="tests.Class04"/>
      <class name="tests.Class05"/>
     </classes>
  </test> <!-- IPHONE_6SPLUS : Parallel Tests -->
</suite> <!-- Parallel Mobile Tests -->

@juherr there will be a fix for this bug soon ?
when running tests in parallel as methods and had a setup on beforeClass, some test not getting started by the "beforeclass".
thanks

@selenUser - Does your scenario involve timeouts ? If not, then please try reproducing this issue using TestNG 7.0.0-beta3 and share a sample reproducible test, if the issue still exists.

as well as @BedoreMethod and @AfterMethod


Cannot set a DataFrame

This command runs fine on one PIN file (comet.pin.txt [too big to attach]), but not a second one (az.comet.mod.pin.txt [also too big to attach]), which is a subset of the first containing only lines pertaining to PSMs with a 471.1504 modification.
python -m percolator_RESET --seed 1 --get_psms T --reverse T --report_decoys T --output_dir output --file_root az.comet.mod --initial_dir Xcorr --overwrite T az.comet.mod.pin.txt
The error output by running this command on az.comet.mod.pin is below. Everything seems to run fine until the end when the following error is output:
Traceback (most recent call last):   File "/home/alex/anaconda3/envs/reset/lib/python3.10/runpy.py", line 196, in _run_module_as_main     return _run_code(code, main_globals, None,   File "/home/alex/anaconda3/envs/reset/lib/python3.10/runpy.py", line 86, in _run_code     exec(code, run_globals)   File "/home/alex/anaconda3/envs/reset/lib/python3.10/site-packages/percolator_RESET/__main__.py", line 405, in <module>     main()   File "/home/alex/anaconda3/envs/reset/lib/python3.10/site-packages/percolator_RESET/__main__.py", line 387, in main     uf.report_psms(df_new, PSMs, get_psms, dynamic_competition, scale, model, isolation_window, columns_trained, initial_dir, output_dir, file_root)   File "/home/alex/anaconda3/envs/reset/lib/python3.10/site-packages/percolator_RESET/utility_functions.py", line 426, in report_psms     df_extra = create_cluster(PSMs.copy(   File "/home/alex/anaconda3/envs/reset/lib/python3.10/site-packages/percolator_RESET/utility_functions.py", line 215, in create_cluster     targets["mass_plus"] = targets.groupby('original_target_sequence', group_keys=False).apply(   File "/home/alex/anaconda3/envs/reset/lib/python3.10/site-packages/pandas/core/frame.py", line 4301, in __setitem__     self._set_item_frame_value(key, value)   File "/home/alex/anaconda3/envs/reset/lib/python3.10/site-packages/pandas/core/frame.py", line 4459, in _set_item_frame_value     raise ValueError( ValueError: Cannot set a DataFrame with multiple columns to the single column mass_plus

Hi Alex!
Are you able to share with me a small subset of az.comet.mod.pin.txt that is uploadable?
Thanks!

Copying my comment from slack:
Ok i see the problem. its because az.comet.mod.pin.txt returns zero peptide discoveries, so when it tries to determine the PSMs associated to the zero discovered peptides, it bugs out. This should be obviously handled with a message of sorts, so ill make note of this in the github issue and get to a fix soon. It will be hard to discover peptides at the 1% FDR level in this file. Of the target and PSMs with XCorr score above 2, there is only 98 target and 72 decoy PSMs.

This has been kind of fixed for now...I just added an if statement to check if the dataframe is empty and it skips reporting the additional output files. Hope that suffices for now!


screenshot tool: selenium crops part of coverage report

need to increase window width just enough to make images look good

changed width from 800 to 1024 which shows good results


Updated styling on video poster button

Removed scaling of play button on hover.  The background color (black) still becomes more opaque as you hover.

👍


Rename SEP query param values

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
[TODO: Short statement about what is changing.]
Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]

Reference Server Preview is available here:https://anchor-ref-pr875.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr875.previews.kube001.services.stellar-ops.com/


todo: support zx shebang

https://github.com/google/zx

I couldn't find the proper way to distinguish with<EMAIL_ADDRESS>so I don't have any plan to work on this.
Feel free to reopen, recreate or comment with your idea or situations you know.


Improve GHSA-xwf4-88xr-hx2j

Updates

Affected products

Comments
Several other components are also affected as a result of cloning (copying source code) or shading (copying source code and renaming packages). Proof-of-Vulnerability projects with tests to verify the presence of the CVE can be found here: https://github.com/jensdietrich/xshady-release/.
See https://github.com/github/advisory-database/pull/2258, especially https://github.com/github/advisory-database/pull/2258#issuecomment-1569073245, for more details.

Given that this is in the same group id as the base package do you know if this has been fixed and if so do you know of a fix commit?

Hi @darakian,

do you know if this has been fixed and if so do you know of a fix commit?

Not as yet. There is one later version available in the Maven Central Repo (1.1.0), but I was not able to get the proof-of-vulnerability test code to run on it at all.
If it would help I can try harder to get this running? That would tell us whether there it's fixed there or not.

Hi @darakian,
We were able to confirm that the next (and only) version available on the Maven Central Repo, namely 1.1.0, is not vulnerable, so I've added a "fixed": "1.1.0" entry in b236a07. Is this PR now good to go?
We confirmed this by manually tweaking the PoV pom.xml -- I've put the working version at https://github.com/jensdietrich/xshady-release/tree/main/CVE-2016-5394/NOT-VULNERABLE/org.apache.sling__org.apache.sling.xss.compat__1.1.0. Gory details in https://github.com/jensdietrich/xshady-release/pull/2#issuecomment-1751576366 and later comments.

Well, I'd like to find a fix commit in the source code if possible, but looking at the commit log it seems like possibly this one
https://github.com/apache/sling-org-apache-sling-xss/commit/de32b144ad2be3367559f6184d560db42a220529
Does that align with what you're seeing?

@darakian Yes it does, based on eyeballing the diff for pom.xml -- thank you for that! Also we know that the version mentioned in the commit message, 1.0.18, is not vulnerable since the vulnerability was fixed in 1.0.12 of org.apache.sling:org.apache.sling.xss.
OTOH I notice your link shows me "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository". But if you're happy with that, we're happy!

I think the git issues stem from the github repo being a mirror of an svn repo
http://svn.apache.org/viewvc/sling/tags/org.apache.sling.xss.compat-1.1.0/
Comparing the 1.1.0 and 1.0.0 tags shows a single commit with no diff
https://github.com/apache/sling-org-apache-sling-xss/compare/org.apache.sling.xss.compat-1.1.0...org.apache.sling.xss.compat-1.0.0

@darakian I see the same empty diff as you, however if I manually look at the top-level pom.xml file at each revision, I see differences between them:

Tag org.apache.sling.xss.compat-1.0.0 is 8ea6e85

line 35 in 8ea6e85 says 1.0.0

Tag org.apache.sling.xss.compat-1.1.0 is 5d1d041

line 35 in 5d1d041 says 1.1.0

@darakian I just changed ... to .. in the comparison URL and now I can see the differences I was expecting: https://github.com/apache/sling-org-apache-sling-xss/compare/org.apache.sling.xss.compat-1.1.0..org.apache.sling.xss.compat-1.0.0
My guess is the SVN import means there's no well-defined "merge base" for the 3-dot form to use?

Oh interesting. Ya, that's a reasonable assumption. I'm not super familiar with the difference between the two forms, but that's an aside for sure. Thanks for digging into this with me 👍


Theming of Dropdown component

Bug Report
The dropdown component has following theming issues:
Dark Theme

Results have white background and text

High Contrast Theme

Input field has white text on light background
Results are shown as white text on white background

Version
0.27 - reproducible on doc site

We are picking up themeing/redlining of the Dropdown component next week

@codepretty Any update on this? Still seeing the same bug.


Added Paladins getqueuestatsbatch api endpoint to wrapper

your queue class is very weird guys

It's been a long time since I've touched this project. So I recognize that it has a lot of strange things and a strange pattern.

I do not intend to continue maintaining this project. I would definitely write better, but I don't have time for that.

all good, it helps us alot still!
i will probably then just take over and keep it up to date as long as we have a use for it :)


Aliases should be used if present

Currently, the time series shows up as metricName (entityName) in my panels. If the user has given an alias in the query I think the alias should have precedence. The current output is very crowded, especially in the new Table panel.
Eg.
select health_good_rate as "Hive" where entityName="HIVE-1"
now renders as
health_good_rate (HIVE-1)
but if the alias was respected it would render as just
Hive
I have modified here locally to the below and it took my table panels to the next level.
// Convert the metadata returned from Cloudera Manager into the timeseries name for Grafana.
ClouderaManagerDatasource.prototype._makeTimeseriesName = function(metadata) {
  if (metadata.alias) {
    return metadata.alias;
  } else if  (metadata.metricName && metadata.entityName) {
    return metadata.metricName + ' (' + metadata.entityName  + ')';
  } else if (metadata.metricName) {
    return metadata.metricName;
  } else if (metadata.entityName) {
    return metadata.entityName;
  } else {
    return 'UNKNOWN NAME';
  }
};

Merged https://github.com/foursquare/datasource-plugin-clouderamanager/pull/2


ex11_36 wrong answer

Q:
Our program does no checking on the validity of either input file. In particular, it assumes that the rules in the transformation file are all sensible. What would happen if a line in that file has a key, one space, and then the end of the line? Predict the behavior and then check it against your version of the program.
Wrong Answer:
If so, a key-value pair is going to be added into the map: {key, ""}. As a result, any key would be replaced with empty string.
Right Answer:
if a line has a key and a one space then the end of the line in the transform file, program will throw exception which says "no rule for " + key.
Thank you,
Sina

Agree.
Part of the original code is,
    ...
    while (...)
        if (value.size() > 1) // the length of value is checked here.
            tans_map[key] = value.substr(1);
        else
            throw runtime_error("no rule for " + key);
    ...

So if there are only a key, one space, and then the end of the line, a runtime_error will be thrown.

Agree.
If the line has a key and one space, value.size() is 1 and the else branch is taken which throws an exception.


oauth_callback missing

Hi,
I've fetched the latest version from here and when I try to connect to Xing api (https://dev.xing.com)
with oAuth 1.0 , I get the error below
Error starting OAuth flow: {"message":"Required parameter oauth_callback missing","error_name":"REQUIRED_PARAMETER_MISSING"} (line 330, file "Service", project "OAuth1")
I haven't modified the code just changed from 1.0a to 1.0 Oauth protocol ( .setOAuthVersion('1.0') )

It appears that the API is using OAuth 1.0a, contrary to their documentation. During testing I found there was a bug with the library, but I've just pushed a fix. I've also added a Xing sample, to get you started:
https://github.com/googlesamples/apps-script-oauth1/blob/master/samples/Xing.gs


Setup Github PR Route

[ ] Be able to GET request Github API

Only keep the data for the following

[ ] User

[ ] Reviewer

[ ] Podname

[ ] Created_at

[ ] Upated_at

cors error that I have in Sheet.jsx
what I've tried
I've tried adding headers to the axios, but it doesn't work
headers {      "Access-Control-Allow-Origin": "*"  }
`componentWillMount() {
axios.get("https://api.github.com/users/MLH-Fellowship/repos").then(res => {
for (var i = 0; i < res.data.length; i++) {
this.setState({ all_repos: this.state.all_repos.concat(res.data[i].name) })
}
        this.state.all_repos.map(repo => {
            axios.get(`https://api.github.com/repos/MLH-Fellowship/${repo}/pulls?state=open`).then(pull_res => {
                const repo_status = {
                    name: repo,
                    assignee: pull_res.assignee ? null : pull_res.assignees,
                    reviewers: pull_res.requested_reviewers,
                    created_at: pull_res.created_at,
                    updated_at: pull_res.updated_at
                }

                this.setState({ all_prs: this.state.all_prs.concat(repo_status) })
            })
        })
    })
}`

is the error still blocked by CORS policy: Request header field access-control-allow-origin is not allowed by Access-Control-Allow-Headers in preflight response.

yup i also got that as well

Try disable web security. Also make sure GitHub.com allows CORS request

Try serving through ngrok (gives your local host a domain name) and updated the GitHub application to use the ngrok domain: https://ngrok.com

closing the issue, atm not using github API (but thanks @ianjennings for pointing out the github rate error : )


All entities randomly, become unavailable.

Integration randomly becomes unavailable, so far I couldn't not isolate the cause.
Using the latest version 1.6.2
How can I help you troubleshoot this?

Hi, not sure if this related or if it hlps however I am having issues with three seperate integrations since upgrading to 2023.12 yesterday, this being one of them. The issue I am seeing states "Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble" for each of the integrartions that havev stopped working.
The other two integrations are:

Tesla Custom Integration
Tapo Custom Integration

Both of these are displaying the same error message as above.
Might just be coincidence but my HA Octopus Intelligent, Tesla and Tapo integrations all stopped working with the same error message on upgrading to 2023.12 after a restart.

Quick update, rolled back to a previous version of HA and all working again 😁

I also have this issue since upgrading HA to 2023.12.1.

I'm seeing the same, irregular dropouts. The following history chart shows the missing data over the past couple of days (the grey missing areas).

HA: 2023.12.3
Octopus Intelligent: v1.6.2
@megakid - Are you aware of any issues? Do you need us to take any logs etc?

Just to confirm I'm seeing the same on HA 2023.12.3. With debug on all I can see in logs is :
2023-12-18 17:39:56.895 DEBUG (MainThread) [custom_components.octopus_intelligent] Setting up Octopus Intelligent System component
2023-12-18 17:40:26.903 DEBUG (MainThread) [custom_components.octopus_intelligent.octopus_intelligent_system] Finished fetching Octopus Intelligent data in 30.004 seconds (success: False)
Tried removing and adding through HACS, but no joy.
Let me know if I can do anything to help.

Just doing my updates and came across same issue when trying to update home assistant to 2023.12.3 from 2023.10.1, although following a restore it still will not initialise the integration. Even before the update I did notice that there are a lot more gaps in the data shown as per @BadgerLoaf.
HA: 2023.10.1 (rollback from failed attempt on 2023.12.3) still not working
Octopus Intelligent: v1.6.2
I am seeing a few warnings in the logs relating to the integration:
Logger: py.warnings
Source: runner.py:186
First occurred: 16:47:27 (1 occurrences)
Last logged: 16:47:27

/usr/local/lib/python3.11/asyncio/base_events.py:1907: RuntimeWarning: coroutine 'OctopusIntelligentSystem.start' was never awaited handle = self._ready.popleft()

Logger: homeassistant.config_entries
Source: config_entries.py:441
First occurred: 16:47:57 (1 occurrences)
Last logged: 16:47:57

Config entry '' for octopus_intelligent integration not ready yet: Error communicating with Octopus GraphQL API: ; Retrying in background

Logger: py.warnings
Source: runner.py:186
First occurred: 16:47:27 (5 occurrences)
Last logged: 16:50:55

/usr/local/lib/python3.11/asyncio/base_events.py:1907: RuntimeWarning: coroutine 'OctopusIntelligentSystem.start' was never awaited handle = self._ready.popleft()
/usr/local/lib/python3.11/asyncio/base_events.py:1923: RuntimeWarning: coroutine 'OctopusIntelligentSystem.start' was never awaited handle = None # Needed to break cycles when an exception occurs.

Things attempted:

Reverted back to previous HA version 2023.10.1 - integration does not start
Re-downloaded the Octopus Intelligent integration - integration does not start
Deleted the integration at previous version 1.6.1 - full system reboot - integration does not start

Have Octopus changed something? or is the service down from them perhaps?

I've just noticed that my friends integration has been down since 1545 UK time 18th Dec today as well.... so seems a mere coincidence that it felt that HA 2023.12.3 broke this integration.
It seems that either:

Octopus have an outage
Octopus have made some changes their end which broke the integration ?

Thoughts?

@nickcj931 mine became unavailable at the same time. I suspect it’s an octopus issue.

Same boat here, went down at 15:44. I wonder if its a regional octopus intel server issue. I'm in the st7 are, where are you guys located.

Ditto. Seeing this, and has been working OK for the past week.
Logger: py.warnings
Source: runner.py:188
First occurred: 19:32:07 (3 occurrences)
Last logged: 19:33:59
/usr/local/lib/python3.11/asyncio/base_events.py:1926: RuntimeWarning: coroutine 'OctopusIntelligentSystem.start' was never awaited handle = None # Needed to break cycles when an exception occurs.
/usr/local/lib/python3.11/asyncio/base_events.py:1910: RuntimeWarning: coroutine 'OctopusIntelligentSystem.start' was never awaited handle = self._ready.popleft()

Same here although I've tried an alternative Octopus integration which is working, suggesting the API is working (although may have changed functionality?). https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy

I have that add-on also, from before it had Intelligent support. That's also failing for me.

I just tried to re-add the integration with my details which returned already configured and then re-initialised the integration which is now working again so perhaps a transient issue.

Yep it’s back up and I’d changed nothing.

Yes, that was the biggest drop for a while, but not sure if the cause will be any different that all the others seen recently.

Same boat here, went down at 15:44. I wonder if its a regional octopus intel server issue. I'm in the st7 are, where are you guys located.

Im in Powys Wales.
But didn't think they had regional servers since uk doesn't have that type of datacenter setup as we are that small. Maybe Lon and Man for example.
But the drop outs are getting worse and worse.
I wonder if they are hitting the API limits perhaps? Companies do this all the time, create and offer an API and don't actually think what happens when it needs to scale and it starts to cost serious ££ ....
I just hope the don't rug pull it as its been such a great service and I literally use Octopus because of it being so feature rich.

I've found this discussion over on the BottlecapDave /
HomeAssistant-OctopusEnergy that @drnichols mentioned.
Seems like they have introduced rate limit after all, although it seems they are talking about the Home Mini - I wonder if that is a platform wide rate limit on whole API Kraken or just for Home Mini related data? no idea
I wouldn't have a clue how to check the code on this integration, but wonder if its "gapping out" because of this limiter (yesterday being an odd ball where perhaps Octopus did maintenance), and a polling rate needs to be adjusted in the app?

Same issue here as above.

It seems that I'm also facing an issue with entities falling back to "unavailable" state - it's happening with the megakid/ha_octopus_intelligent integration entities:

But, interestingly, it's not happening with the equivalent BottlecapDave/HomeAssistant-OctopusEnergy integration entities:

So, if this was API throttling, then the other integration is somehow handling it.

I saw a new issue today with the entities showing particular times for the start of the next off-peak period, but the octopus app was showing different times.Sent from my Remington Rand UNIVACwww.g8ytz.com On 13 Jan 2024, at 21:07, MarkTarry @.***> wrote:
It seems that I'm also facing an issue with entities falling back to "unavailable" state - it's happening with the megakid/ha_octopus_intelligent integration entities:
image.png (view on web)
But, interestingly, it's not happening with the equivalent BottlecapDave/HomeAssistant-OctopusEnergy integration entities:
image.png (view on web)
So, if this was API throttling, then the other integration is somehow handling it.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Not only is there rate limiting in place, Octopus are now blocking requests that do not have a suitable request header.

Same issue here. Lots of drop outs which are causing my “end” automations to run multiple times.

I'm finding that, predominantly, octopus_intelligent_offpeak_end is unavailable for quite some time.  From the history, I find that the other entities do drop out but (as I write) they've all a value.  Fortunately, at 23:30:01 I more often than not (this week) octopus_intelligent_offpeak_end has a value and so my automations tend to run.  I'm hoping a tweak to my automation to be less sensitive to the entity being unavailable is a short term solution.  Ideally, I'd quite like it to be more stable / available.
My log has:
2024-01-14 07:26:48.674 ERROR (MainThread) [custom_components.octopus_intelligent.octopus_intelligent_system] Error fetching Octopus Intelligent data: Error communicating with Octopus GraphQL API:

2024-01-14 01:07:34.674 ERROR (MainThread) [custom_components.octopus_intelligent.octopus_intelligent_system] Error fetching Octopus Intelligent data: Error communicating with Octopus GraphQL API:

Hopefully that's (A) related and (B) some use?

I’m seeing the same issues too.
Is this being worked on or do we need to consider using a different integration? 1.6.2 came out June last year.

Hi, not sure if this related or if it helps however I am having issues with three seperate integrations since upgrading to 2023.12 yesterday, this being one of them. The issue I am seeing states "Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble" for each of the integrartions that have stopped working.
The other two integrations are:

Tesla Custom Integration
Tapo Custom Integration

Both of these are displaying the same error message as above.
Might just be coincidence but my HA Octopus Intelligent, Tesla and Tapo integrations all stopped working with the same error message on upgrading to 2023.12 after a restart.

Yes, I have see issues with other integrations, particularly the PowerWall, implying a "breaking change" has caused the issue. I don't use the Tesla car integration, though I have installed it and it is currently disabled. If you restart HA it fixes the issue (reload does not), it appears to be a process that stops randomly and occasionally restarts. I'm running HA on an Intel NUC Celeron.

I've been having issues with the entities becoming unavailable or just showing the incorrect values for the past couple of months. I've installed this integration too (https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/) which is not as rich but is not having the same issues. I've updated my sensors in HA to use the status of which ever integration is working at the time (using or logic).

@megakid any suggestions/workarounds?

Same issue here, was working fine on  Core 2024.1.5 ,Supervisor 2023.12.1
I get the impression that Octopus has realised that some people are creating automations which use their "car charging slots" to charge solar battery storage from grid and run high wattage appliances like the washing machine, tumble dryer etc etc... as their intelligent octopus tariff is 0.07 Kwh

Apologies for radio silence- I've not been available to look at this (new job and baby in the house). I'll try to take a look but this is a change on Octopus's end that I'll need to work with and/or around.
Thanks for your patience!

What's the default poll interval for this integration? I'm wondering if we need to be 'good API citizens' and make the polling less frequent? A small change here could help if Octopus are struggling with API load, and isn't likely to make a big difference to how well our automations work?

Not sure what the difference is between these integrations but I tried this instead (https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy) and it works well. Megakid is above and the new one is below. Had to adjust my automations etc but working again now.

Congrats on the new arrival.

Not sure what the difference is between these integrations but I tried this instead (https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy) and it works well. Megakid is above and the new one is below. Had to adjust my automations etc but working again now.

Congrats on the new arrival.

I didn't realise that the BottlecapDave integration had the intelligent smart charging in already. I just wonder why are there 2 different integrations doing similar things..

Not sure what the difference is between these integrations but I tried this instead (https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy) and it works well. Megakid is above and the new one is below. Had to adjust my automations etc but working again now.

Congrats on the new arrival.

I didn't realise that the BottlecapDave integration had the intelligent smart charging in already. I just wonder why are there 2 different integrations doing similar things..

I too have swapped over to BottlecapDave, but today that became unavailable too, so it must be an issue at the Octopus end or perhaps we are sending too many requests over? THE advantage of the Octopus Intelligent integration is it give you the 1, 2 and 3 hour slot indicators.

I didn't realise that the BottlecapDave integration had the intelligent smart charging in already. I just wonder why are there 2 different integrations doing similar things..
Yes for some reason the BottlecapDave integration doesn't have issues with sensors turning unavailable like this one does.

However, this one has 2 advantages: it has a "next offpeak start" sensor, and it updates dispatch slots way more accurately. I suspect the latter might be due to it polling the API more frequently, which could also be the cause of the constant "unavailable" issues?

This integration polls the API every 5 mins (see interval here https://github.com/megakid/ha_octopus_intelligent/blob/main/custom_components/octopus_intelligent/octopus_intelligent_system.py) which feels quite conservative but is obviously still a problem.
I did see someone say a header is required now which I need to research. I will try to get to it tonight

Hopefully this is fixed with https://github.com/megakid/ha_octopus_intelligent/releases/tag/v1.6.3


Does supecronic support crontab RANDOM_DELAY variable?

From man crontab
The RANDOM_DELAY variable allows delaying job startups by random amount of minutes with upper limit specified by the variable.  The random scaling factor is determined during the cron daemon startup so it remains constant for the whole run time of the daemon.

it does not, though we are open to contributions. Can I ask what were you hoping to accomplish with such a delay?

This delay is required when a bunch of backup jobs start in parallel at the same time, for example. Currently I'm using random delay in pre-start backup script.


[bug] tooltip: double tab index when wrapped around focusable element

Description of the issue
When pfe-tooltip is wrapped around a focusable element like anchor or button, there is an extra focus effect.
Impacted component(s)

pfe-tooltip

Steps to reproduce

Go to https://patternflyelements.com/components/tooltip/
Tab through the buttons on the demo page.
You'll see that there is a focusable item for the tooltip invoker AND one for the button

Expected behavior

I don't think tooltips should have there own tabindex.  They should only monitor focusin, focusout and similar events.
Reference:

A tooltip provides extra information about a form field, a link, a button, or other focusable element. It must be triggered by both focus and hover events and remains on the screen as long as the trigger has the focus. The focus does not move to the tooltip.

https://dequeuniversity.com/library/aria/tooltip
Screenshots
Bug:
https://user-images.githubusercontent.com/3428964/206749810-cacea7fb-4c37-4b51-a5e8-29c27df6d038.mp4
Expected behavior:
https://user-images.githubusercontent.com/3428964/206749890-c2b6dc85-c753-42fb-85e7-51ba524db913.mp4
Proposal
diff --git a/elements/pfe-tooltip/BaseTooltip.ts b/elements/pfe-tooltip/BaseTooltip.ts
index 8f5615919..24054fa27 100644
--- a/elements/pfe-tooltip/BaseTooltip.ts
+++ b/elements/pfe-tooltip/BaseTooltip.ts
@@ -63,7 +63,8 @@ export abstract class BaseTooltip extends LitElement {
   }

   #addListeners() {
-    this.addEventListener('focus', this.show);
+    this.addEventListener('focusin', this.show);
+    this.addEventListener('focusout', this.hide);
     this.addEventListener('blur', this.hide);
     this.addEventListener('tap', this.show);
     this.addEventListener('click', this.show);
@@ -74,7 +75,7 @@ export abstract class BaseTooltip extends LitElement {
   override render() {
     const { initialized } = this.#domController;
     return html`
-

+

         <slot></slot>

Agreed, the tooltip doesn't need a tabindex.  The browser should be able to handle the tabs through the lightdom or the elements themselves. I updated https://github.com/patternfly/patternfly-elements/pull/2257 with these changes too

Chiming in to agree. From: https://w3c.github.io/aria-practices/#tooltip

Keyboard Interaction
Escape: Dismisses the Tooltip.

NOTE
Focus stays on the triggering element while the tooltip is displayed.
If the tooltip is invoked when the trigger element receives focus, then it is dismissed when it no longer has focus (onBlur). If the tooltip is invoked with mouseIn, then it is dismissed with on mouseOut.

Additionally if they are a part of a toolbar, like in the audio-player, for example, they need to be dismissible with the ESC key


Backport to Python 3.9

I think it's fine to merge this. The CI tests use python 3.9 and this should let the CI tests run properly.


Item name set in various stage goals not working.

Under stages the following stage goals will not work and will not accept item names such as dirt stone or item id numbers.
These stages do not have a load item from hand option either and seemingly are asking for the item name as though you are setting the item goal.
Evidence of the issue is attempting to finish the sample quest "Stone miner" as the quest is asking one to break dirt?
The stages are:
--1 - Break blocks
--2 - Damage blocks
--3 - place blocks
--4 - Use blocks
--5 - Cut blocks
--8 - Enchant items
No errors in console

What response do you get in chat when submit an item name (do not use id numbers)? A screenshot would be perfect.

Alright got you

Response when attempting to set up enchantment item names

Response for set name on 1-5
(basically the same each time for break, damage, place, use, cut)
On a side note apologies for submitting so many things,
I'm just really excited to use this plugin to its fullest extent.
As well I wanted to ask about the command usage feature in events?
Limited to vanilla commands or a way to get it to fire off something from another plugin.
Apologies I know its not related to this but I didn't want to add another issue when its my issue not knowing, not the plugin.

Fixed in Quests 2.2.1. Thanks!


[BUG] unable to get crc configured on M1

Unable to get crc setup as it reads This version of CRC for AMD64/Intel64 CPUs is unsupported on Apple silicon
General information

OS:  macOS
Hypervisor: KVM / Hyper-V / hyperkit / vfkit
Did you run crc setup before starting it Yes
Running CRC on: Laptop

CRC version
CRC version: 2.37.1+36d451
OpenShift version: 4.15.14

CRC status
DEBU CRC version: 2.37.1+36d451
DEBU OpenShift version: 4.15.14
DEBU Running 'crc status'
DEBU Running 'sw_vers -productVersion'
crc does not seem to be setup correctly, have you run 'crc setup'?

CRC config
- consent-telemetry                     : yes

Host Operating System
ProductName:		macOS
ProductVersion:		13.5.2
BuildVersion:		22G91

Steps to reproduce

Following download link from https://www.redhat.com/sysadmin/install-openshift-local
Install crc-macos-installer.pkg for aarch64
Run crc setup

Expected
To build local OpenShift cluster
Actual
crc setup
INFO Using bundle path /Users/ana.medina1/.crc/cache/crc_vfkit_4.15.14_amd64.crcbundle
INFO Checking if running macOS version >= 13.x
INFO Checking if running as non-root
INFO Checking if crc-admin-helper executable is cached
INFO Checking if running on a supported CPU architecture
INFO Checking if crc executable symlink exists
INFO Checking minimum RAM requirements
INFO Check if Podman binary exists in: /Users/ana.medina1/.crc/bin/oc
INFO Checking if running emulated on Apple silicon
This version of CRC for AMD64/Intel64 CPUs is unsupported on Apple silicon

Logs
Before gather the logs try following if that fix your issue
$ crc delete -f
`Machine does not exist. Use 'crc start' to create it`
$ crc cleanup
INFO Unloading and removing the daemon plist file
INFO Removing /etc/resolver/testing file
INFO Stopping CRC vfkit process
INFO Removing CRC Specific entries from user's known_hosts file
INFO Removing hosts file records added by CRC
INFO Removing pull secret from the keyring
INFO Removing older logs
Cleanup finished
$ crc setup
INFO Using bundle path /Users/ana.medina1/.crc/cache/crc_vfkit_4.15.14_amd64.crcbundle
INFO Checking if running macOS version >= 13.x
INFO Checking if running as non-root
INFO Checking if crc-admin-helper executable is cached
INFO Checking if running on a supported CPU architecture
INFO Checking if crc executable symlink exists
INFO Creating symlink for crc executable
INFO Checking minimum RAM requirements
INFO Check if Podman binary exists in: /Users/ana.medina1/.crc/bin/oc
INFO Checking if running emulated on Apple silicon
This version of CRC for AMD64/Intel64 CPUs is unsupported on Apple silicon
$ crc start --log-level debug
DEBU CRC version: 2.37.1+36d451
DEBU OpenShift version: 4.15.14
DEBU Running 'crc start'
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
DEBU Unable to find out if a new version is available: Error unmarshaling JSON metadata: invalid character '}' looking for beginning of object key string
DEBU Checking file: /Users/ana.medina1/.crc/machines/crc/.crc-exist
DEBU Running 'sw_vers -productVersion'
Is 'crc daemon' running? Cannot reach daemon API: Get "http://unix/api/version": dial unix /Users/ana.medina1/.crc/crc-http.sock: connect: no such file or directory

Please consider posting the output of crc start --log-level debug  on http://gist.github.com/ and post the link in the issue.

You must be running crc in an "intel context", for example in a terminal which is an x86 binary running in rosetta. Or if you got crc through brew, your brew environment could be x86. Running the arch command in the terminal should tell you which arch is currently being used.

Ah, thanks for that insight. Was able to get it to work with arch -arm64 crc setup

Thanks for the help!


Default WasmLoader fails to build

Previously, contracts were built with the following command by WasmLoader:
cargo build --release --target wasm32-unknown-unknown

But in the newer versions, --lib parameter needs to be present as well.
So WasmLoader should use the following instead:
cargo build --lib --release --target wasm32-unknown-unknown

Actually most of the CosmWasm projects as well as the template projects provided by both us and CosmWasm make use of wasm alias. So I believe the best thing would be running cargo wasm by default so that it works regardless of the version.

no sure we need it. we able to build and upload contracts and run the. reopen if fixes are needed.


Add Client Status to Nomad Allocation monitoring.

It would also be great to see the client status in the monitoring data. Sorry for putting this in a separate PR :sweat_smile:

Sure, don't worry. What about the desired status, or the node, ...?

What about the desired status, or the node, ...?

The desired status is known as we check it specifically before adding or removing the allocation from the storage.
The node is a good catch and may simplify checking the Nomad logs if required :+1:


Fix Bullets in /properties/*/

I have added a checkmark icon. We should remove the bullet and make the checkmark icon green
https://github.com/natashafenech/holidaysinmalta.com/blob/1b8e79016a34145accc3087f31f5ed29b015bfa6/src/_layouts/property.html#L131

no


Replace all Console.X

Replace all Console.Write , Console.Read, Console.XXXX with interface like this
public interface IConsole
{
void WrilteLine(string line);
string ReadLine();
void SetForegroundColor(ConsoleColor color);
}
And implement ConsoleInterface , this make possible write and read in Socket , and its usefull for me
Sorry for my english

@shargon There are related tickets (#27, #37) which were closed. However, I will reconsider them. In particular, QuickLog (another library I wrote, not open source yet) seems like a viable option - it would use pretty much exactly the interface you described.

https://github.com/nerai/Unlog

Must be done without Unlog, would be too closely tied together. Instead, use hookable output events.


Hotfix server not working

fix webinspect list to allow passing in the server
list_scans(scan_name, server, username, password)
- was list_scans(server, scan_name, username, password)

sitting next to Hayley and she'll make a new branch/PR to fix my issue.


Listed tokens are not visible

Context information
application version:
device:
browser:
operating system:
Steps to reproduce
https://aescan.io/tokens
What is expected?
list of listed tokens
What is actually happening?
it has broke again

https://dex-backend-mainnet.prd.service.aepps.com/tokens/listed
is not working again
in https://dex-backend-mainnet.prd.service.aepps.com/tokens
there are no tokens labeled as listed

Seems to be fixed @michele-franchi . Thanks


Adds REUSE/SPDX license info

REUSE and the associated CLI tool (both from FSF),
allow to properly specify licensing i a thorough, machine-readable way, on a per-file basis.
These changes make crkbd use this way of specifying licenses.
NOTE: For the badge in the README to work, after accepting, you'd still have to register the project URL with REUSE , to get automatic evaluation of the current state reflected in the badge icon. You do that just by clicking on the badge. I would also do it, if you do not want. it is like creating an account somewhere, with email verification.

What does this solve?  Please specify the current issue and why we need to include it.

I gave some arguments, and it is better explained at https://reuse.software/
If that is not enough for you, then feel free to ignore this.
I am dealing with a lot of OSH projects (thousands) in an automated way, and I can tell you, that this solves licensing once and for all, for anyone who deals with lots of projects. It's a god-sent.
Our aim is to make OSH viable for the masses. There is much to do, but this helps.
For your project alone, looked at in isolation from the rest of the world, it is not functionally useful.

Thank you for your suggestion, however, I think it's enough to put LICENSE in the root directory.


run in Node.js

If the cli is given only the python input file, it should be run in Node.js after compiling it to Javascript instead of request an output file. This would allow to use PythonJS as a python interpreter. Add the -c argument would be good, too.
As a plus, if no input file is defined it should accept it from stdin, and maybe implement a REPL..

It may help to list current cli interface help and desired to speed up the process.


"IOError: [Errno 29] Illegal seek" when LOG_FILE = /dev/stdout

I've installed Security Monkey within a docker container. To ensure that I'm able to collect the logs, I've configured logging with:
LOG_LEVEL = "DEBUG"
LOG_FILE = "/dev/stdout"

When the scheduler is running, it throws the following error for every event it tries to write to the log (the python file triggering the bug is different, but the error is the same):
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/handlers.py", line 76, in emit
    if self.shouldRollover(record):
  File "/usr/lib/python2.7/logging/handlers.py", line 157, in shouldRollover
    self.stream.seek(0, 2)  #due to non-posix-compliant Windows feature
IOError: [Errno 29] Illegal seek
Logged from file auditor.py, line 273

Yeah I've seen this before as well when playing with dockerizing security_monkey.  I'm assuming it has something to do with the RotatingFileHandler or StreamHandler, but never really dug into it:
https://github.com/Netflix/security_monkey/blob/master/security_monkey/__init__.py#L39

You're right.
To test, I tried changing the maxBytes and backupCount parameters to zero (0). This caused the RotatingFileHandler to never try to rotate the log and didn't issue the illegal seek.
In my case, rather than changing the source, I was able to work around the error by specifying LOG_FILE = "/dev/null". The docker container running the scheduler was able to capture the scheduler's output without having to direct it to /dev/stdout. It's only missing the scheduler-generated timestamps which I don't need currently.
I'll close this ticket since there are workarounds available.


feat: add a new prop(adjustable) so that the drawer can adjust its width/height

3141

 Quality gate: Failed
12 Issues

 12 Code issues

Details


Fixed local deployment with Kind

All Submissions:
This PR fixes the local deployment with make deploy:

Fixed create_kind_cluster.sh script. Missed <IP_ADDRESS> in docker command

Removed set -eou pipefail for split_roles_yaml.sh as it breaks the Makefile

Changes to *.yaml files are autogenerated by controller-gen

[x ] Have you signed our CLA?

This PR resolves https://github.com/mongodb/mongodb-atlas-kubernetes/issues/371

qq: what inside tags directory?

That's from ctags (https://en.wikipedia.org/wiki/Ctags)


Provide function to get embedded kotlin dsl dependency info with the correct version.

Similar to how I can use implementation(embeddedKotlin("gradle-plugin")) to get the correct embedded version of kotlin.
I would like a function the gives the right version of kotlin-dsl that can be added to the classpath.
Expected Behavior
This should work to bring kotlin dsl plugin into the classpath:
dependencies {
    implementation(embeddedKotlinDsl())
    implementation(embeddedKotlin("gradle-plugin"))
}

Current Behavior
This works, but requires be to hard code the coordinate of the kotlin dsl plugin
dependencies {
    implementation("org.gradle.kotlin.kotlin-dsl:org.gradle.kotlin.kotlin-dsl.gradle.plugin:$expectedKotlinDslPluginsVersion")
    implementation(embeddedKotlin("gradle-plugin"))
}

Context
I want to apply the kotlin-dsl plugin from within a kotlin-dsl plugin.
Related: https://github.com/gradle/gradle/issues/22428

gradleKotlinDsl() already exists, but doesn't do what we need here.
This:
dependencies {
    implementation(gradleKotlinDsl())
    implementation(embeddedKotlin("gradle-plugin"))
}

gives this error:
> Task :meta:generatePrecompiledScriptPluginAccessors FAILED

FAILURE: Build failed with an exception.

* Where:
Precompiled script plugin 'repro/build-logic/meta/src/main/kotlin/my.kotlin-dsl.gradle.kts' line: 1

* What went wrong:
Plugin [id: 'org.gradle.kotlin.kotlin-dsl'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (plugin dependency must include a version number for this source)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 8s
4 actionable tasks: 4 executed

I filed a similar request a while back: https://github.com/gradle/gradle/issues/17825


spell error: "source" -> "license" in syntax guide

Screenshot

To Reproduce
Steps to reproduce the behavior:

Go to https://search.creativecommons.org/search-help
See error

can i take this up?

#583

This was fixed in #584


Rework AudioProcessor trait to look like AudioWorkletProcessor

Requirements:

no longer supertrait of Send
construct processor on the render thread, not control thread
preallocate a Box on the control thread, though
drop unsafe code around DelayNode and DynamicsCompressorNode - no longer needed

Superseeded with #453 which marks the AudioProcessor trait private


[BUG] Creating Logic App using the SDK is not behaving as expected

Library name and version
Azure.ResourceManager.Logic; 1.1.0
Describe the bug
We are facing following problems while trying to create Logic App using 'Microsoft Azure Logic management client' SDK. Version: '1.1.0'.
Problems:

Not able create Standard logic App resource, only Consumption logic apps are created.
Resource are created even if we are providing the invalid data(params). The errors are shown in Logic App Designer View.

The code we are using for this is provided in the reproduction steps section.
Expected behavior
The expectation is to be able to create standard plan logic apps and if the template Json is wrong, the SDK method should throw error.
Actual behavior
The code provided always creates consumption logic app irrespective of the SKU used. Also the logic app is getting created even though the logic app template used is not a valid logic app Json.
Reproduction Steps
Run the provided code by replacing parameters in '<>'
using Azure.Core;
using Azure.Identity;
using Azure.ResourceManager;
using Azure.ResourceManager.Logic;
using Azure.ResourceManager.Logic.Models;
using Azure.ResourceManager.Resources;

var client = new ArmClient(new DefaultAzureCredential());
var subscriptionId = "<subscription id>";
var rgName = "<rg name>>";
var logicAppName = "<logic app name>";

// Create a new logic app using arm template in a json file

var template = File.ReadAllText("template.json");

ResourceIdentifier rgIdentifier = ResourceGroupResource.CreateResourceIdentifier(subscriptionId, rgName);
ResourceGroupResource resourceGroup = client.GetResourceGroupResource(rgIdentifier);
try
{
    var bn_template = BinaryData.FromString(template);

    var plan = ArmLogicModelFactory.LogicResourceReference(rgIdentifier, "<ASP Name>");
    var logicAppSKu = ArmLogicModelFactory.LogicSku(LogicSkuName.Standard, plan: plan);
    var logicWorkflowData = ArmLogicModelFactory.LogicWorkflowData(definition: bn_template, sku: logicAppSKu, location: AzureLocation.EastUS);

    var resp = await resourceGroup.GetLogicWorkflows().CreateOrUpdateAsync(Azure.WaitUntil.Completed,
        logicAppName, logicWorkflowData, CancellationToken.None);
    Console.WriteLine(resp);
}
catch (Exception ex)
{
    throw ex;
}

Environment
OS: Windows
.Net version: net8.0
IDE: Visual Studio 2022 - 17.12.1

@welovej  please note that in logic's swagger, the sku property in workflow is marked as "readonly"
If the swagger is correct, there might be other ways that we could set the sku.
Or the swagger is incorrect.
We might should need to contact the service team and ask.

@welovej please note that in logic's swagger, the sku property in workflow is marked as "readonly" If the swagger is correct, there might be other ways that we could set the sku. Or the swagger is incorrect. We might should need to contact the service team and ask.

Hi @ArcturusZhang , Thanks for the kind note.
I set the sku poperty false to readonly property in rest-api-spec and regen the logic.  Then I tried to set the sku and app service plan .Then I got a payload and response like the screent shot below. It seems that: Usage of a hosting plan is deprecated since API version '2016-06-01'

Hi @welovej,
Thanks for the response. So isn't there any way to create standard plan logic apps through API?


[KeyVault] Fixed tests that measure the size of the backups

This size is variable, so it doesn't make sense to compare it to a
specific number other than just make sure that the result has a positive
length.
TODOS:

Merge #4871
Update all the tests (and samples?).
Ask for review.

Alternatively:
Merge all the pending PRs, then update the recordings.
Fixes: #4857

Seems okay - I don't think we want to track the actual size, in case Azure wants to optimize the serialized format


xDSCWebService: Adding Firewallrule without checking for existing one.

As part of the installation of the DSC WebService, the resources adds a new Firewall rule:

Allow Port 8080 for PSWS

I ran a configuration using that resource a few times and I now have 24 of the above rules, all with the same name.
Before adding this rule the code should check whether it already exists.

I'm happy to fix this

Thanks Peter!

Closed by #30


clarify why we allow multiple institution types

most institutions have only a singular type anyway, and in the cases which have multiple, it is not entirely clear what we are trying to express.
also, clarify if a national-coordination-institution can exist which is not also a partner-institution.

institution types cover several / parallel realities: for example an institution can be a partner-institution and the national-representative-institution (= a GA member belongs to an institution that is member of the national consortium) but it also possible for a national-representative-institution to not be a partner-institution (=a GA member belongs to an institution not member of the consortium).
So, that is at least one use case where several institution types can be needed.
And I don't think we have a use case of a national-coordination-institution that can exist which is not also a partner-institution.


RELEASE: v0.13.0

Release tracking issue for v0.13.0.
Cut-off time for commits is EOD Monday 4/06.

Closed by 7a0031372b01ccd7ce8dd240a6c19804ff7fe242.


Editor crashes on rendering while project folder is open.

I really like the editor, but it keeps crashing very often (every few seconds, or even crash on restart). Folder might be even empty - problem still occurs.
Checked similar issues.

VSCode Version: 1.17.2
OS Version: Windows 10 Pro 64-bit Version (10.0.15063)

Steps to Reproduce:

Launch VS Code
Open Folder with more than few files in it.

Reproduces without extensions: Yes
Reproduces on insider build: Yes
[main 18:51:59] [VS Code]: render process crashed!
full cmd console log: https://gist.github.com/pawel-majczyk/1bec9e2c3e44ca02d643dd093ce6b4c4
video with issue: https://imgur.com/a/7A1Rm

I can run code.exe with -n option and then open i.e. settings file - everything works until I open folder.
Presence of extensions has no effect on behaviour. Running as administrator doesn't help either.
Memory/CPU usages at normal level.
This is my Personal Computer and VS Code is the only application that has issues. I have installed Atom (heard it's also uses Electron) but no issues there.
Edit: When project folder loads completely it does not crash instantly, but any interaction with editor (especially selecting text with mouse) might crash application. Sometimes it does work for 10mins, but mostly it fails after few seconds of file editing.

It does reproduce why any folder. Even empty one. When the folder has plenty of files it just crashes even more often and as on attached video, crash occurs before it loads all the files. Presence of .git is not relevant. Disabling anti-virus/firewall has also no effect.

@pawel-majczyk can you try with some experiments: https://github.com/Microsoft/vscode/wiki/Performance-Issues#experiments

@bpasero Thanks
Did step-by-step testing from the list, here are results:
results

no.
Experiment name
does it reproduce?

1
--disable-extensionsname
yes

2
folder with less files
yes

3
folder that is not under source control
yes

4
open a single file
no

4b
open multiple files at once
no

5
insider version
no (1.18 only, yes for previous I've tried before)

6
no settings
no

Apparently the setting causing a crash is
"window.zoomLevel": 1
fiddled with it a bit — it does crash for the value of 1 and above. Looks stable for value of 0.5, or -1. Strange.
Workaround would be simply just not using it, or switching to insider version for development.
Since editing size of everything on the theme configuration seems like a lot of hassle I assume I can use nightly build for development, and problem will be obsolete by the time.
Thanks again for helping me locate source of problem.

@pawel-majczyk does it reproduce in stable when you run code --disable-gpu?

@bpasero No. It does not :)

/duplicate https://github.com/microsoft/vscode/issues/15211


Fixed broken link

Signed-off-by: arunkarthick<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Done :) @l5io

Hello @l5io , I checked the preview and it works fine now. Will you merge this PR please? 😀

Can anyone merge this PR please :)


--skip-nanopolish and --dry-run

I am looking to get the pipeline up and running before we sequence data. I have downloaded some publicly available fastqs to try it out.
The medaka part works fine, however for the artic minion, I cannot provide the fast5 required, as I have not found a dataset.
So I tried a --dry-run like so:
artic minion --normalise 200 --threads 4 --scheme-directory ~/primer_schemes/ --read-file  ~/reads/$sample.fastq --dry-run nCoV-2019/V3 $sample
Output: "Must specify FAST5 directory and sequencing summary for nanopolish mode."
Is it correct, that for artic minion, I always need a fast5? When I tried to --skip-nanopolish, I got the same output as above.
Are those two non-functioning flags or am I doing something wrong?
Thanks for advising!

Hi there,
To run nanopolish you must have FAST5. There is some FAST5 data available from https://community.artic.network/t/links-to-raw-fast5-fastq-data-for-artic-protocol/17 if that's of use.
If you want to try the experimental Medaka version, you don't need FAST5 but must specify --medaka on the command line.
Let me know if that helps.

Thanks for the swift response!
I will try the dataset from the CADDE project, thank you.
So just to confirm, the --dry-run and --skip-nanopolish are not functional yet or did I do something wrong?

--dry-run will just print out the commands
--skip-nanopolish isn't something you want to do! I might remove it.

Thanks for your answers!
Stay safe


Allow passing jupyterlite configuration files

We should allow passing custom jupyterlite configuration files

Fixed by https://github.com/martinRenou/jupyterlite-sphinx/commit/74a0b16699d1889d2311087d7439a4e9e5833375


Fix Rubocop violations in the legacy API adapter

This PR fixes the Rubocop violations in the legacy API adapter and reconfigures Rubocop not to ignore this file.
Summary
Removed the legacy API adapter file from the .rubocop-todo.yml file and then fixes the Rubocop violations that occur in that file.
Details
There were two method calls where the args needed to be enclosed in parentheses; I added parens to both.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] I've added tests for my code
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Actually, sorry @danascheider, if I remember correctly in cucumber codebase there is the convention to avoid parenthesis when the result of a method call is discarded. I wanted to write a custom cop for that, I will try to find some time for it.

@nodo An issue with precisely these parens missing is that they yield Ruby warnings. Perhaps the convention would opt for no-warnings, when there's no other way?

@nodo "I think", I should add.

Let's not waste any time on the (hopefully soon) to be removed legacy_api, see #1230.


Security: How to protect our metadata fields from code injection attacks?

I just realized (in talking about security in the other thread) that our metadata fields are likely currently subject to code injection attacks via a malicious theme.
From vim template:
" base16-vim (https://github.com/chriskempson/base16-vim)
" by Chris Kempson (http://chriskempson.com)
" {{scheme-name}} scheme by {{scheme-author}}

Example of the attack vector:
(this is using a YAML multi-line string)
scheme: |
  trojan-horsey-unicorn

  [here is a huge
  glob of evil and
  malicious vimscript]
base00: "090300" #  ----

I'd guess this is exploitable for any templates where the output is an executable file... we could start by not allowing multiple lines (perhaps make it an error case) but how would you handle protecting all the possible templates since we don't know which characters might be used to escape commenting?
The assumption of course being that these metadata fields are only for use in comments... and should NOT be allowed to escape those comments.

I think this is primarily a policy issue - we control the schemes repo, so we'll just have to watch for it.
The easiest way to handle it would be to limit what characters are allowed in color scheme fields. Only allow text and general sentence punctuation, no newlines (we could optionally require replacing newlines with spaces in the builder spec).

I'm closing this for now, even though we don't have a great answer - at the moment, we're just going to rely on making sure we don't provide any malformed schemes in any of the repos/systems we support. That means keeping values, even description, to a single line.


Warning : MapInstances/City_00_01/locations.lua is missing

Server boot up looks for two Lua files to load and spits out a warning if they aren't found.
Warning : MapInstances/City_00_01/locations.lua is missing

We should make those qDebug instead of qWarning, and modify the message to let the end user know that defaults will be used instead, or that those files aren't necessary.

So it seems that right now there is no formal implementation of the location_visited function inside locations.lua, but there is a formal implementation for the plaque_visited function inside plaques.lua.
This warning message appears when these files do not exist, but an attempt is made to load their contents into the scripting engine within MapInstance.cpp lines 78 and 79. Later in MapInstance.cpp, the location_visited and plaque_visited functions are called if their events are triggered. Both attempt to call their lua function equivalents, and if not possible they throw a warning. MapInstance::on_location_visited inlcludes the output message of the lua function call within its warning message, but MapInstance::on_plaque_visited does not (as far as I can tell, the val within on_plaque_visited is never used at all).
I'm opening a pull request that changes the qWarning to qDebug and edits the message, but it seems there are no defaults, and without the files warnings will be thrown, so this might be a further issue.


Fix syntax error in documentation

Just fixing a little typo I found while copying the code sample.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


ERR_CERT_AUTHORITY_INVALID certificate error

Despite after waiting for a lot of time I still see the screen that says 'Your connection is not private'.
I followed all the steps mentioned in the tutorial and the outputs were pretty much the same as given. The only difference was when I ran this command:
 helm dependency build .\deploy\teams-recording-bot\

I got this error:
Error: no repository definition for https://kubernetes.github.io/ingress-nginx. Please add the missing repos via 'helm repo add'

So then I ran this command successfully:
>>  helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
"ingress-nginx" has been added to your repositories

And after that my build was successfull like this:

PS C:\Users\osama\Desktop\MS_Bot\aks-sample\Samples\PublicSamples\RecordingBot> helm dependency build .\deploy\teams-recording-bot\
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ingress-nginx" chart repository
...Successfully got an update from the "jetstack" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading ingress-nginx from repo https://kubernetes.github.io/ingress-nginx
Deleting outdated charts

If you need output of anymore commands please let me know. Also, I'm using windows 11 so that shouldn't be an issue

Thanks, I will add the need to add nginx repo to our todos,
regarding your issue can you try run kubectl describe certificate ingress-tls-recordingbottutorial --namespace recordingbottutorial as described in the info box it is possible that let's encrypt reached a certificate limit for the azure region in that case you either have to wait until the limit resets or use a cname entry of a custom domain that points to the azure domain.

Thanks for reaching out. When cert-manager is installed, it creates a bunch of CRDs. Can you query those CRDs in your cluster?
Things like cluster issuer, certificate requests, challenges and so on? When you describe those resources, it might explain why it's unable to pull certificates.
I'm wondering if you have a ClusterIssuer resource

@1fabi0 I think you're right. Let's encrypt reached a limit for that region but I'm not sure why tho. This is what I see when I execute the command that you've given:
 Issuer Ref:
    Group:      cert-manager.io
    Kind:       ClusterIssuer
    Name:       recordingbottutorial-issuer
  Secret Name:  ingress-tls-recordingbottutorial
  Usages:
    digital signature
    key encipherment
Status:
  Conditions:
    Last Transition Time:    2024-05-14T19:41:47Z
    Message:                 Issuing certificate as Secret does not exist
    Observed Generation:     1
    Reason:                  DoesNotExist
    Status:                  False
    Type:                    Ready
    Last Transition Time:    2024-05-15T02:41:53Z
    Message:                 The certificate request has failed to complete and will be retried: Failed to wait for order resource "ingress-tls-recordingbottutorial-1-3163291491" to become ready: order is in "errored" state: Failed to create Order: 429 urn:ietf:params:acme:error:rateLimited: Error creating new order :: too many certificates already issued for "eastus.cloudapp.azure.com". Retry after 2024-05-16T05:00:00Z: see https://letsencrypt.org/docs/rate-limits/
    Observed Generation:     1
    Reason:                  Failed
    Status:                  False
    Type:                    Issuing
  Failed Issuance Attempts:  4
  Last Failure Time:         2024-05-15T02:41:53Z
Events:                      <none>

I tried after waiting as stated in the error message but I'm still getting the same behavior. Should I expect it to work or act differently if I deploy the bot to the different region?

If you have a DNS you can configure a CName entry that points to the azure domain of the aks cluster then update the bot service with your DNS name and redeploy to the cluster with your own DNS name as host. You could also try to delete the not signed certificate with kubectl delete certificate ingress-tls-recordingbottutorial, which you might need to do anyway if you change the DNS name.

And yes, a different region would result in a different FQDN sub-domain for your built-in domain of the IP. AFAWK, only eastus is currently experiencing rate-limit issues

So before working on the custom domain, I deployed everything in a new region i.e westus but I still see the same . If I execute kubectl describe certificate ingress-tls-recordingbottutorial --namespace recordingbottutorial I can see that the certifcate is created this time:
  Issuer Ref:
    Group:      cert-manager.io
    Kind:       ClusterIssuer
    Name:       recordingbottutorial-issuer
  Secret Name:  ingress-tls-recordingbottutorial
  Usages:
    digital signature
    key encipherment
Status:
  Conditions:
    Last Transition Time:  2024-05-21T16:23:55Z
    Message:               Certificate is up to date and has not expired
    Observed Generation:   1
    Reason:                Ready
    Status:                True
    Type:                  Ready
  Not After:               2024-08-19T15:23:51Z
  Not Before:              2024-05-21T15:23:52Z
  Renewal Time:            2024-07-20T15:23:51Z
  Revision:                1
Events:                    <none>

Any idea why this could be happening now?

Hard to tell. If the cert is there, then it should also utilize it during connection between browser and nginx. Can you see the certificate details in your browser?

This is what I see

Interesting, you got a staging certificate from let's encrypt. Did you change anything in the chart or did it just deliver the staging certificate to you... If you didn't change anything can you please run  kubectl describe clusterissuer recordingbottutorial-issuer

Yes you can, maybe you need to delete the certificate with kubectl delete certificate ingress-tls-recordingbottutorial --namespace recordingbottutorial

I delete the certificate like this:
kubectl delete certificate ingress-tls-recordingbottutorial --namespace recordingbottutorial
certificate.cert-manager.io "ingress-tls-recordingbottutorial" deleted

And then I deployed it again. When I run this  kubectl describe clusterissuer recordingbottutorial-issuer I get the following output:
Name:         recordingbottutorial-issuer
Namespace:
Labels:       app.kubernetes.io/managed-by=Helm
              helmAppVersion=1.3.1
              helmName=teams-recording-bot
              helmVersion=1.4.1
Annotations:  meta.helm.sh/release-name: recordingbottutorial
              meta.helm.sh/release-namespace: recordingbottutorial
API Version:  cert-manager.io/v1
Kind:         ClusterIssuer
Metadata:
  Creation Timestamp:  2024-05-21T15:22:43Z
  Generation:          2
  Resource Version:    620248
  UID:                 888e8e38-e91a-4419-8bcd-784320e69db0
Spec:
  Acme:
    Email<EMAIL_ADDRESS>    Private Key Secret Ref:
      Name:  recordingbottutorial-issuer
    Server:  https://acme-v02.api.letsencrypt.org/directory
    Solvers:
      http01:
        Ingress:
          Ingress Class Name:  recordingbottutorial-ingress-nginx
Status:
  Acme:
    Last Private Key Hash:  fr9Yby//pm+e/RxOAPFfqLlD+rNy5PS3BOgaIrDN5w8=
    Last Registered Email<EMAIL_ADDRESS>    Uri:                    https://acme-v02.api.letsencrypt.org/acme/acct/1739907162
  Conditions:
    Last Transition Time:  2024-05-21T15:22:44Z
    Message:               The ACME account was registered with the ACME server
    Observed Generation:   2
    Reason:                ACMEAccountRegistered
    Status:                True
    Type:                  Ready
Events:                    <none>

and if I run this: kubectl describe certificate ingress-tls-recordingbottutorial --namespace recordingbottutorial , I see this:
tutorial
Name:         ingress-tls-recordingbottutorial
Namespace:    recordingbottutorial
Labels:       app.kubernetes.io/managed-by=Helm
              helmAppVersion=1.3.1
              helmName=teams-recording-bot
              helmVersion=1.4.1
Annotations:  <none>
API Version:  cert-manager.io/v1
Kind:         Certificate
Metadata:
  Creation Timestamp:  2024-05-22T09:38:31Z
  Generation:          1
  Owner References:
    API Version:           networking.k8s.io/v1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Ingress
    Name:                  recordingbottutorial
    UID:                   22eb9988-b03e-42ab-bebc-72389ef0995a
  Resource Version:        618859
  UID:                     8b5ef662-b7a4-4e04-8bc4-761107248cf3
Spec:
  Dns Names:
    ppppppppppppppppp
  Issuer Ref:
    Group:      cert-manager.io
    Kind:       ClusterIssuer
    Name:       recordingbottutorial-issuer
  Secret Name:  ingress-tls-recordingbottutorial
  Usages:
    digital signature
    key encipherment
Status:
  Conditions:
    Last Transition Time:  2024-05-22T09:38:32Z
    Message:               Certificate is up to date and has not expired
    Observed Generation:   1
    Reason:                Ready
    Status:                True
    Type:                  Ready
  Not After:               2024-08-19T15:23:51Z
  Not Before:              2024-05-21T15:23:52Z
  Renewal Time:            2024-07-20T15:23:51Z
Events:                    <none>

That Looks good, if it still doesn't work you can try to delete the certificate again as you first deleted and then deployed your change, so it might have pulled from the staging in between again. Regarding the Windows pods you might need to restart them e.g. restart the cluster so they pull the correct certificate.
Also Thanks for working with our email address from the example 😂

haha I forgot to chage that.
also while trying to restart the windows pods, I've noticed one thing:
 kubectl get pods -n recordingbottutorial
NAME                                                             READY   STATUS             RESTARTS      AGE
recordingbottutorial-0                                           0/1     CrashLoopBackOff   8 (60s ago)   19m
recordingbottutorial-1                                           0/1     CrashLoopBackOff   8 (17s ago)   19m
recordingbottutorial-2                                           0/1     CrashLoopBackOff   8 (28s ago)   19m
recordingbottutorial-ingress-nginx-controller-5bc86dbdd5-xwngh   1/1     Running            0             17m

Is it expected? The pods are in CrashLoopBackOff state

It is not expected maybe you can describe a pod and see whats the issue is during start or even try to run kubectl logs for the pods. I could imagine that it does not have a certificate as you now maybe need to reopen the page with your browser, or that it also got the staging certificate now :expressionless:

Thanks a lot for your continous help. I really appreciate that.
This is what I see:
Setup: Starting VC_redist
Setup: Converting certificate
Setup: Installing certificate
Certificate "vintonbot.westus.cloudapp.azure.com" added to store.

CertUtil: -importPFX command completed successfully.
Setup: Deleting bindings
Setup: Adding bindings
Setup: Done
---------------------
RecordingBot: booting
fail: RecordingBot.Console[0]
      Unhandled exception in Boot()
      Status Code: 0
      Microsoft.Graph.Communications.Core.Exceptions.ServiceException: Media platform failed to initialize
       ---> System.InvalidOperationException: MediaPlatform needs a system with at least 2 cores for creation
         at Microsoft.Skype.Internal.Bots.Media.InternalMediaPlatform.Initialize(MediaPlatformSettings settings, IConfigurationManager configurationManager, Boolean isTest)
         at Microsoft.Skype.Bots.Media.MediaPlatform.Initialize(MediaPlatformSettings settings, IConfigurationManager configManager, Boolean isTest)
         at Microsoft.Skype.Bots.Media.MediaPlatform.Initialize(MediaPlatformSettings settings)
         at Microsoft.Graph.Communications.Calls.Media.MediaCommunicationsClientBuilderExtensions.SetMediaPlatformSettings(ICommunicationsClientBuilder statefulClientBuilder, MediaPlatformSettings mediaSettings)
         --- End of inner exception stack trace ---
         at Microsoft.Graph.Communications.Calls.Media.MediaCommunicationsClientBuilderExtensions.SetMediaPlatformSettings(ICommunicationsClientBuilder statefulClientBuilder, MediaPlatformSettings mediaSettings)
         at RecordingBot.Services.Bot.BotService.InitializeClient() in C:\src\RecordingBot.Services\Bot\BotService.cs:line 63
         at RecordingBot.Services.Bot.BotService.Initialize() in C:\src\RecordingBot.Services\Bot\BotService.cs:line 51
         at RecordingBot.Services.ServiceSetup.AppHost.Boot(String[] args) in C:\src\RecordingBot.Services\ServiceSetup\AppHost.cs:line 75

This also has my bot domain details

I think you need to delete your certificate again and restart your cluster, as it seems like you still got the staging certficate, and your windows pods also already pulled the certificate into the store. I don't believe that the nodes are too weak, but as the default replicaCount might be to big for the number of nodes deployed in the tutorial. So if certificate delete and cluster restart does not fix your problem you could also try to deploy only two replicas with the scale.replicaCount Option
helm upgrade recordingbottutorial .\deploy\teams-recording-bot\
   --install
   --namespace recordingbottutorial
   --set image.registry="recordingbotregistry.azurecr.io/recordingbottutorial"
   --set image.name="application"
   --set image.tag="latest"
   --set public.ip="<IP_ADDRESS>"
   --set host="recordingbottutorial.westeurope.cloudapp.azure.com"
   --set<EMAIL_ADDRESS>
   --set scale.replicaCount=2

I think the deletion is not working permannetly and it being created again automatically. I delete the certificate and immediately check it again like:
 kubectl get certificates -n recordingbottutorial
NAME                               READY   SECRET                             AGE
ingress-tls-recordingbottutorial   False   ingress-tls-recordingbottutorial   9s

Thanks @1fabi0 I need to remove that now :)
Also, I'm still seeing 503 Service Unavailable after waiting for quite a while. Is it becasue of the CrashLoopBackOff state of the pods?

Yes exactly, if you scale down the replica count to 2 instances please let me know, then I'll include that into the Tutorial

I update the help with this flag  --set scale.replicaCount=2 but still two pods are in the CrashLoopBackOff state. Would I need to delete them so that they can be restarted again?

You could try, what do you see if you describe the pods?

I see this error at the end of the describe log
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  certificate:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  ingress-tls-recordingbottutorial
    Optional:    false
  kube-api-access-xxt5b:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                           Age                    From     Message
  ----     ------                           ----                   ----     -------
  Warning  FailedToRetrieveImagePullSecret  2m3s (x624 over 132m)  kubelet  Unable to retrieve some image pull secrets (acr-secret); attempting to pull the image may not succeed.

I'm using standard_d2s_v3

And what do the logs say right now (kubectl logs)?


Update index.html hcaptcha js for base url support

Added a dot before the url to support base path for reverse proxying.

Have you tested this yet? I imagine the captcha flow would still have issues as this  doesn't take a base path into account. It would probably need to be changed to something like this (I think that worked before...)

Have you tested this yet? I imagine the captcha flow would still have issues as this  doesn't take a base path into account. It would probably need to be changed to something like this (I think that worked before...)

You are right

You are right


FluentValidation doesn't work on vnext

Not sure what the policy is for reporting vnext bugs as it's currently not supported, but going to open this anyway. Maybe you want to create a label for vnext specific issues?
When trying to use FluentValidation with Nancy on vnext an error is thrown when calling BindAndValidate:
'Nancy.Validation.ModelValidationException' occurred in Nancy.dll but was not handled in user code Additional information: No model validator factory could be located. Please ensure that you have an appropriate validation package installed, such as one of the Nancy.Validation packages.
I have Nancy.Validation.FluentValidation installed. I also have the appropriate registrations done in the Bootstrapper. You can see an example set of code in my Gist here: https://gist.github.com/awec/af94a240956b68e81e2b
Tried to debug this myself and couldn't figure it out cause I don't really know how Nancy works at that level. The modules window in Visual Studio suggests that Nancy.Validation.FluentValidation.dll is indeed loaded, but for some reason is not detected when the BindAndValidate method is called.

Ok, I've spent ages looking at this.
The problem is that when Nancy takes a cache of the loaded assemblies from AppDomain.Current during bootstrapping it doesn't contain Nancy.Validation.FluentValidation.dll (because it has had no reason to be loaded yet).
The DLL is eventually loaded after the TinyIOC Registrations occur.
However, AppDomainAssemblyTypeScanner will never load the correct types, because it works off the cached version of the assemblies that were loaded at bootstrap time. All the TypesOf methods in this class work off that cache.
We cannot rely on these dlls being loaded in time for them to be picked up by the AppDomainAssemblyTypeScanner on bootstrap.

Ran into this issue last night with SimpleValidator :( but at 2am I didn't start looking for a solution.

I have a PR that fixes it. Basically we need to call UpdateTypes() on the Assembly scanner after all the IOC registrations have happened.
Not sure it's the most efficient or best long term fix, but it works (as far as I can see).

It should load it as part of the scan that picks up assemblies that reference nancy - is that not working or are you saying it runs too late?

That method works off file paths and the .Location property of the assembly. Assemblies in vnext are loaded into memory, so the .Location property is always an empty string.
So it doesn't find the dll we need.


Why does the extracted-content field only return a maximum of 8 pieces of data after structuring the large model data

换了不同的大模型调用，生成的markdown数据是准确的，再由大模型生成结构化的数据后，数据缺失，最多只返回8条数据是为何？哪里可以设置吗？

After using different large model calls, the generated markdown data is accurate. However, when the large model generates structured data, the data is missing and only a maximum of 8 pieces of data are returned. What is the reason for this? Where can I set it up?

@sz0811 This is interesting, There's no limit in a library unless the large language model you used detected only the eight pieces of data. Please share the code snippet and the language model you are using. I tried on my end and will update you.


Pandas installation error when using pip

When doing a test release on TestPyPI
bertrand@laptop:/tmp$ python3 -m pip install --index-url
https://test.pypi.org/simple/ nistats_bthirion
Collecting nistats_bthirion
   Using cached
https://test-files.pythonhosted.org/packages/25/79/ec342dd4cde62d6cea16d424fe1a939cff0f203e2b08a4cd67679ba6dfa1/nistats_bthirion-0.0.1b0-py3-none-any.whl
Collecting pandas>=0.18.0 (from nistats_bthirion)
   Could not find a version that satisfies the requirement
pandas>=0.18.0 (from nistats_bthirion) (from versions: )
No matching distribution found for pandas>=0.18.0 (from nistats_bthirion)

@bthirion  Take a look at this: https://github.com/pandas-dev/pandas/issues/20697
Which python version are you using? 3.4? Does 3.5 have the same problem?
Does conda also have this problem?

When I do

I get
Could not find a version that satisfies the requirement nibabel>=2.0.2 (from nistats-bthirion) (from versions: )
No matching distribution found for nibabel>=2.0.2 (from nistats-bthirion)

Doing a
pip install git+https://github.com/nistats/nistats.git

does not give an error.

I built the wheels for the package and install that:
python setup.py sdist bdist_wheel --universal
pip install nistats-0.0.1b0-py2.py3-none-any.whl

No erros.

I created a brand new environment using venv+pip (which I installed using apt) and then redid the installation of the local wheel. It ultimately completed. However there was a point where it failed to build nibabel from the wheel, and seems to have installed from source instead.
The output log:
Building wheels for collected packages: nibabel
  Running setup.py bdist_wheel for nibabel ... error
  Complete output from command /home/kshitij/workspace/nistats-org/nistats-repo/nistats-pandas-3/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-yagttmtm/nibabel/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/tmpfqh6ik70pip-wheel- --python-tag cp36:
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Failed building wheel for nibabel
  Running setup.py clean for nibabel
Failed to build nibabel
Running setup.py install for nibabel ... done
Successfully installed nibabel-2.3.0 nilearn-0.4.2 nistats-0.0.1b0 numpy-1.15.2 pandas-0.23.4 patsy-0.5.0 python-dateutil-2.7.3 pytz-2018.5 scikit-learn-0.20.0 scipy-1.1.0 six-1.11.0

Also got the error with SciPy.
Could not find a version that satisfies the requirement scipy>=0.17 (from nistats-bthirion) (from versions: 0.1)
No matching distribution found for scipy>=0.17 (from nistats-bthirion)

Seems the error does not happen from the actual PyPI server, only from the test one.


Deprecation error on Alpha-2 that I’m trying to understand… failing

This is the code:
composer/ClassLoader.php

/**
 * Scope isolated include.
 *
 * Prevents access to $this/self from included files.
 */
function includeFile($file)
{
    include $file;
}

Twig calls it and I get the following:
Exception has occurred.
Deprecated: Optional parameter $callable declared before required parameter $arguments is implicitly treated as a required parameter

Not being a PHP expert, I know what the code does, just not what the error actually means or, better yet, how to fix it.

Set error_reporting in your php.ini to a value recommended for production servers, e.g. error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT.

I’m puzzled how this changes the fact that it is deprecated?


Allow disabling default NAT tables and chains

This patch adds a parameter to the main interface to prevent the module from including nftables::ip_nat and hence from configuring any of the default tables and chains dedicated to processing NATed traffic.
Closes #23.

This will won't merge well with #10  but LGTM

if you can rebase, would be great.

Rebased and conflicts resolved. Thanks for reviewing.


[CARBONDATA-4217] Fix rename SI table, other applications didn't get reflected issue

Why is this PR needed?
After one application rename SI table, other application cannot be reflected of this change, which leads to query on SI column failed.
What changes were proposed in this PR?
After update index info of parent table, persist schema info so that other applications can refresh table metadata in time.
Does this PR introduce any user interface change?

No

Is any new testcase added?

No Tested in cluster.

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5583/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3840/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3841/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5584/

LGTM

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5598/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3854/


Fixed mistake in meta.yaml which skipped building

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Was skipping py36+ builds by accident - fixed

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Translate configure-pod-configmap to Bahasa Indonesia

Hello, folks!
I've translated the page /docs/tasks/configure-pod-container/configure-pod-configmap/ to Bahasa Indonesia.
This PR addresses https://github.com/kubernetes/website/issues/20111.

@evanap seems like the build is failed, can you please check it again?

/cc

Yeah, it seems like it brings old commits. Let me check that.

I think the master branch on my fork is messed up :/
I'll try to fix it first.

/cc @danninov
/cc @qbl

/uncc @danninov
/uncc @qbl
/cc
/assign

Ah, sorry I missed that. Thanks for informing @girikuncoro! The _index.md should be there now.

@evanap all looking good now, please squash your commit first before we can merge this, thanks! I will hold the merge for now
/lgtm
/hold

Thank you @girikuncoro! Squashed them commits :+1:

@evanap thanks a lot, hope you learn something by localizing this page! feel free to pick other pages when you get time :)
/lgtm
/approve

/unhold

@girikuncoro Sure! There's always things too learn in this mountain of documentations :grin:
I'm picking up another page!


[Shared] Changes to column style padding to improve visual layout of content

Automatically generated task. Any updates to the title and body will be overwritten. Do NOT modify the labels.
Shared implementation of #2755

We have decided not to make this change as it has negative effects on some existing cards.


Network validation check

Current network validation check relies on user configured variable, which may be unreliable.  This can be changed to a more reliable check based on system configuration.
Should be able to check for connectivity by performing a PING of of the local network gateway.  #

Completed


Problem installing Isso

I don't know why I'm having issues installing isso via "pip," I am able to install other packages via "pip."
$ pip install isso
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: isso in ./.local/lib/python2.7/site-packages (0.12.2)
Requirement already satisfied: configparser; python_version == "2.7" in ./.local/lib/python2.7/site-packages (from isso) (4.0.2)
Requirement already satisfied: bleach in ./.local/lib/python2.7/site-packages (from isso) (3.1.1)
Requirement already satisfied: html5lib in ./.local/lib/python2.7/site-packages (from isso) (1.0.1)
Requirement already satisfied: itsdangerous in ./.local/lib/python2.7/site-packages (from isso) (1.1.0)
Requirement already satisfied: werkzeug>=0.9 in ./.local/lib/python2.7/site-packages (from isso) (1.0.0)
Requirement already satisfied: Jinja2 in ./.local/lib/python2.7/site-packages (from isso) (2.11.1)
Requirement already satisfied: ipaddr>=2.1; python_version == "2.7" in ./.local/lib/python2.7/site-packages (from isso) (2.2.0)
Requirement already satisfied: misaka<3.0,>=2.0 in ./.local/lib/python2.7/site-packages (from isso) (2.1.1)
Requirement already satisfied: six>=1.9.0 in ./.local/lib/python2.7/site-packages (from bleach->isso) (1.14.0)
Requirement already satisfied: webencodings in ./.local/lib/python2.7/site-packages (from bleach->isso) (0.5.1)
Requirement already satisfied: MarkupSafe>=0.23 in ./.local/lib/python2.7/site-packages (from Jinja2->isso) (1.1.1)
Requirement already satisfied: cffi>=1.0.0 in ./.local/lib/python2.7/site-packages (from misaka<3.0,>=2.0->isso) (1.14.0)
Requirement already satisfied: pycparser in ./.local/lib/python2.7/site-packages (from cffi>=1.0.0->misaka<3.0,>=2.0->isso) (2.20)

$ pip3 install isso
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: isso in ./.local/lib/python2.7/site-packages (0.12.2)
Requirement already satisfied: configparser; python_version == "2.7" in ./.local/lib/python2.7/site-packages (from isso) (4.0.2)
Requirement already satisfied: bleach in ./.local/lib/python2.7/site-packages (from isso) (3.1.1)
Requirement already satisfied: html5lib in ./.local/lib/python2.7/site-packages (from isso) (1.0.1)
Requirement already satisfied: itsdangerous in ./.local/lib/python2.7/site-packages (from isso) (1.1.0)
Requirement already satisfied: werkzeug>=0.9 in ./.local/lib/python2.7/site-packages (from isso) (1.0.0)
Requirement already satisfied: Jinja2 in ./.local/lib/python2.7/site-packages (from isso) (2.11.1)
Requirement already satisfied: ipaddr>=2.1; python_version == "2.7" in ./.local/lib/python2.7/site-packages (from isso) (2.2.0)
Requirement already satisfied: misaka<3.0,>=2.0 in ./.local/lib/python2.7/site-packages (from isso) (2.1.1)
Requirement already satisfied: six>=1.9.0 in ./.local/lib/python2.7/site-packages (from bleach->isso) (1.14.0)
Requirement already satisfied: webencodings in ./.local/lib/python2.7/site-packages (from bleach->isso) (0.5.1)
Requirement already satisfied: MarkupSafe>=0.23 in ./.local/lib/python2.7/site-packages (from Jinja2->isso) (1.1.1)
Requirement already satisfied: cffi>=1.0.0 in ./.local/lib/python2.7/site-packages (from misaka<3.0,>=2.0->isso) (1.14.0)
Requirement already satisfied: pycparser in ./.local/lib/python2.7/site-packages (from cffi>=1.0.0->misaka<3.0,>=2.0->isso) (2.20)

See #617


Bump temporal queue

Description
Context: https://dust4ai.slack.com/archives/C05F84CFP0E/p1726898784171909
Original PR: https://github.com/dust-tt/dust/pull/7590
Risk
Low
Deploy Plan

deploy connectors
restart notion workflows

PMRR


polynomial: upstream lowerings

After https://github.com/google/heir/issues/256, the polynomial dialect is now upstream. The remaining work is to upstream the passes

convert-polynomial-mul-to-ntt
polynomial-to-standard

Should start by giving our versions of these passes non-conflicting names with the upstream versions.

See also  #724 for how we might want to modify  --convert-polynomial-mul-to-ntt to be more accelerator friendly